Decentralized satellite constellations

Abstract

Systems and methods for supporting a decentralized satellite constellation are disclosed. A gateway satellite may use a first communication protocol to route communications to and from an auxiliary satellite. The auxiliary satellite may be orbitally coupled to the gateway satellite and may be equipped with a corresponding payload type that provides corresponding functionality. The auxiliary satellite may also use a corresponding communication protocol that is different from one another and from the first communication protocol. Routing communications to and from the auxiliary satellite may include relaying communications between multiple auxiliary satellites. Relaying communications between the auxiliary satellites may include relaying communications between multiple gateway satellites. Routing communications to and from the auxiliary satellite may also include relaying communications between a commercial satellite and the auxiliary satellite.

Description

Background Art

[0001] The following relates generally to satellite communications and, more particularly, to using dispersed satellite constellations.

[0002] Satellites currently orbiting the Earth collectively provide a wide variety of functions to user devices (e.g., communication services, imaging services, positioning services, navigation services, timing services, etc.). A subset of currently deployed satellites may each provide a large number of functions, while other deployed satellites may each provide a small number of functions (e.g., one function). In some cases, satellites that provide a large number of functions may be more expensive, complex, and larger than satellites that provide a small number of functions.

[0003] To reduce manufacturing and deployment costs, satellite operators may launch one or more specialized satellites, each configured to provide a limited number of functions. In some cases, a dedicated satellite may use different communication protocols and include radio components that support different communication schemes than other dedicated satellites. As a result, the dedicated satellites may not be able to communicate with each other, and user equipment may not be able to communicate with multiple dedicated satellites unless it is configured to include radio components that support the communication protocols and schemes of the multiple dedicated satellites. Summary of the Invention

[0004] The technology relates to improved methods, systems, devices, and apparatus for supporting a decentralized satellite constellation. A gateway satellite may be orbitally coupled to one or more dedicated satellites (which may also be referred to as "tactical data link (TDL) satellites" or "auxiliary satellites"), each of which provides a limited number of functions. The gateway satellite may be configured to route communications between the one or more dedicated satellites. Thus, the gateway satellite may extend the capabilities of the dedicated satellite to network with additional functionality provided by other dedicated satellites, thereby providing user devices with access to additional equipment and / or communication links that may be incompatible with the communications supported by the user device.

[0005] The gateway satellite may be further configured to route communications between the one or more dedicated satellites and other satellites (e.g., other gateway satellites, commercial communications satellites). Thus, a user device configured for a commercial network may access a dedicated satellite via a gateway satellite. In some cases, another gateway satellite may be orbitally coupled to another set of one or more dedicated satellites. And these gateway satellites may be configured to route communications between a first set of one or more dedicated satellites orbitally coupled to a first gateway satellite and another set of one or more dedicated satellites orbitally coupled to another gateway satellite by relaying communications between these gateway satellites. Thus, a user device may reach other user devices located in a different coverage area from the user device via one or more gateway satellites or other satellites. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Figure 1An example of a satellite communication system supporting a dispersed satellite constellation as disclosed herein is shown.

[0007] Figure 2 Aspects of a satellite communication subsystem supporting a decentralized satellite constellation as disclosed herein are shown.

[0008] Figure 3 and Figure 4 Aspects of the processes for supporting and utilizing a decentralized satellite constellation as disclosed herein are shown.

[0009] Figure 5 Aspects of a satellite communication subsystem supporting a decentralized satellite constellation as disclosed herein are shown.

[0010] Figures 6 to 8 Aspects of the processes for supporting and utilizing a decentralized satellite constellation as disclosed herein are shown.

[0011] Figure 9 Aspects of a satellite communication subsystem supporting a decentralized satellite constellation as disclosed herein are shown.

[0012] Figure 10 and Figure 11 Aspects of the processes for supporting and utilizing a decentralized satellite constellation as disclosed herein are shown.

[0013] Figure 12 A block diagram of a satellite controller supporting a decentralized satellite constellation as disclosed herein is shown.

[0014] Figure 13 A block diagram of an exemplary gateway satellite supporting a decentralized satellite constellation as disclosed herein is shown.

[0015] Figure 14 A block diagram of an exemplary auxiliary satellite supporting a decentralized satellite constellation as disclosed herein is shown.

[0016] Figure 15 and Figure 16 Flowcharts are shown that illustrate methods of supporting recovery from a primary node link failure as disclosed herein. DETAILED DESCRIPTION

[0017] A satellite communication system may include satellites (which may also be referred to as "tactical data link (TDL) satellites") that each provide a different but limited (e.g., one) function (or capability) to a connected user device. In some cases, different TDL satellites may be configured with different payload types that support corresponding functions and / or are used to meet the corresponding mission objectives of the TDL satellites. For example, one TDL satellite may be equipped with a single payload type that provides a single capability, and another TDL satellite may be equipped with a different payload type that provides different capabilities. In some cases, the TDL satellites may also use different communication protocols from each other. In order to enable a user device to access the multiple functions provided by multiple TDL satellites, the user device may be configured with instructions for executing multiple communication protocols and / or be configured with multiple sets of radio equipment to support communication with multiple TDL satellites. However, configuring a user device to support communication with multiple TDL satellites may increase the cost and / or complexity of the user device. In addition, in some cases, concurrent communication with multiple TDL satellites may be prevented due to interference between TDL satellites or lack of availability of a given TDL satellite.

[0018] Alternatively, to provide multiple functions to user devices, satellites with more functionality can be installed in orbit. However, configuring satellites to provide more functionality can increase the cost, complexity, and / or size of the satellites. Furthermore, in some cases, power limitations or interference between signaling used to support different functions can prevent satellites from providing concurrent functionality. Furthermore, installing more complex satellites may prevent user devices from utilizing existing TDL satellites already in orbit.

[0019] In order to increase the number of functions available to user devices without increasing or minimizing the cost, complexity and / or size of the user devices and the satellites, a decentralized satellite constellation as described herein may include a gateway satellite that routes communications between auxiliary satellites (that cannot communicate with each other). The auxiliary satellites may be satellites with limited or dedicated functions. In some cases, the auxiliary satellites may include existing or newly launched TDL satellites. In some cases, the gateway satellite may be orbitally coupled (or co-orbital) with one or more auxiliary satellites. That is, the gateway satellite and the auxiliary satellites may orbit in a coordinated manner so that the gateway satellite and the auxiliary satellites may remain within direct communication range of each other throughout the orbit. For example, the gateway satellite and the auxiliary satellites may orbit in a manner so as to maintain an inter-satellite distance of less than 1 km, less than 10 km, less than 100 km, less than 1,000 km, or some other range in which the communication protocol for communication between satellites can operate effectively.

[0020] In some examples, the gateway satellite may be configured to route communications received from one auxiliary satellite to another auxiliary satellite. For example, an auxiliary satellite may relay communications received from a user device to a gateway satellite, and the gateway satellite may route the communications to another auxiliary satellite. In some cases, the auxiliary satellite may respond to the communications using information generated by the functions of the auxiliary satellite. In some cases, the auxiliary satellite may relay the communications to another user device that uses a different communication protocol than the user device. By routing communications between auxiliary satellites, the user device may gain access to functions provided by the auxiliary satellites (e.g., other payload types) that would not otherwise be accessible to the user device—for example, if the auxiliary satellites used a different communication protocol than the user device. Additionally, by routing communications between auxiliary satellites, the user device may connect to other user devices that use a different communication protocol than the user device.

[0021] Additionally or alternatively, the gateway satellite can be configured to relay communications between the commercial satellite and the ancillary satellite. For example, the gateway satellite can receive communications intended for the ancillary satellite from the commercial satellite and can relay the communications to the ancillary satellite. The ancillary satellite can respond to the communications or relay the communications to a connected user device. By configuring the gateway satellite to relay communications between the ancillary satellite and the commercial satellite, user devices and the ancillary satellite that are not configured to communicate on the commercial network can connect to and access the commercial network. Furthermore, user devices configured for the commercial network can be enabled to access functionality of the ancillary satellite that would otherwise be inaccessible to the user device and / or user devices not configured to communicate directly with the user device.

[0022] In some examples, another gateway satellite may be orbitally coupled with one or more additional auxiliary satellites. In some cases, a gateway satellite configured to route communications between auxiliary satellites may be further configured to relay communications between gateway satellites. For example, a gateway satellite that receives communications from an auxiliary satellite intended for another auxiliary satellite (e.g., a user served by another auxiliary satellite) that is orbitally coupled with another gateway satellite may relay the communications to another gateway satellite. The other gateway satellite may then relay the communications to the intended auxiliary satellite, for example, using the techniques discussed above and the corresponding techniques discussed herein. By deploying multiple gateway satellites, the communication range of a user device may be extended to other coverage areas in order to communicate with user devices using the same and / or different communication protocols as the user device. In addition, the user device may be enabled to access non-communication-based functions (e.g., satellite imaging services) provided by auxiliary satellites covering other coverage areas.

[0023] Aspects of the present disclosure are first described in the context of a satellite communication system. Specific examples of satellite communication subsystems and processes for supporting and utilizing a distributed satellite constellation are then described. Aspects of the present disclosure are further illustrated by and described with reference to device diagrams, system diagrams, and flow charts associated with a distributed satellite constellation.

[0024] Figure 1 An example of a satellite communication system 100 supporting a decentralized satellite constellation as disclosed herein is shown. The satellite communication system 100 may include a gateway satellite 105, an auxiliary satellite 110, a commercial satellite 115, a user device 120, and a commercial gateway 125.

[0025] The gateway satellite 105 may be configured to route communications between other satellites within the satellite communication system 100 (e.g., other gateway satellites 105, auxiliary satellites 110, and commercial satellites 115). In some cases, the gateway satellite 105 is configured to support one or more communication protocols. Each communication protocol may be associated with packetization, encryption, and transmission techniques. Packetization techniques may include techniques for packaging (e.g., framing, segmenting, formatting, encoding) data to be transmitted, which may include breaking the data into data portions and assembling data packets including header information and one or more data portions. Encryption techniques may include techniques for encrypting data, such as using a pre-shared key (e.g., public key cryptography). And transmission techniques may include techniques for transmitting data, which may include selecting a power and frequency range for the transmission. In some cases, encryption techniques and transmission techniques are combined—for example, a transmission may be transmitted over multiple frequency ranges in an order known only to the transmitting and receiving devices.

[0026] In some examples, gateway satellites 105 may be configured with a first communication protocol (which may also be referred to as a “gateway communication protocol”) to communicate with other gateway satellites 105, auxiliary satellites 110, and / or commercial satellites 115. In other examples, gateway satellites 105 may be configured with a first gateway communication protocol (which may also be referred to as a “gateway / gateway (GW / GW) communication protocol”) to communicate with other gateway satellites 105, a second gateway communication protocol (which may also be referred to as a “gateway / TDL (GW / TDL) communication protocol”) to communicate with auxiliary satellites 110, and a third gateway communication protocol (which may also be referred to as a “gateway / commercial (GW / CL) communication protocol”) to communicate with commercial satellites 115. In some cases, the GW / GW communication protocol and the GW / CL communication protocol use a wide area network (WAN) communication protocol or a protocol that can support WAN protocol communications (e.g., a protocol that can support Transmission Control Protocol (TCP), User Datagram Protocol (UDP), Frame Relay, Integrated Services Digital Network (ISDN), or Point-to-Point Protocol (PPP)). Furthermore, the GW / TDL communication protocol may use a local area network (LAN) communication protocol or a protocol that can support LAN communication (e.g., a protocol that can support Ethernet, media access control (MAC) layer data link signaling, or a wireless LAN protocol such as Wi-Fi). In some cases, these three communication protocols have common features (e.g., they may use the same packetization technology) and may all be collectively referred to as gateway communication protocols.

[0027] In some examples, the gateway satellite 105 may include multiple sets of radios and radio components to communicate with different types of satellites. In some cases, the gateway satellite 105 may include a solar panel array to generate power for the gateway satellite 105 (e.g., to charge a battery power source at the gateway satellite 105). Figure 12 and Figure 13 Additional details regarding the configuration of gateway satellite 105 are described.

[0028] The auxiliary satellite 110 may be configured to provide functionality (e.g., communication services, global positioning services, imaging services, etc.) to the user equipment 120. For example, different auxiliary satellites 110 may have different payload types (e.g., communication payloads that support communication protocols, imaging payloads, positioning payloads, navigation payloads, timing synchronization payloads). In some cases, the auxiliary satellite 110 is configured to support one or more communication protocols. In some examples, the auxiliary satellite 110 may be configured with a first communication protocol (which may also be referred to as a "TDL communication protocol") for communicating with other auxiliary satellites 110 using the first communication protocol, user equipment 120 using the first communication protocol, and / or gateway satellite 105. In some examples, the auxiliary satellite 110 may include a set of radios and radio components for communicating with different types of satellites. In other examples, the auxiliary satellite 110 may be configured with a TDL communication protocol for communicating with other auxiliary satellites 110 and user equipment 120 using the TDL communication protocol and a second communication protocol (e.g., a GW / TDL communication protocol) for communicating with the gateway satellite 105. In some examples, an auxiliary satellite 110 may include a set of radios and radio components for communicating with different types of satellites, such as with other auxiliary satellites 110 and gateway satellites 105 that share a common communication protocol. In some cases, an imaging payload may include, for example, an optical camera, an infrared camera, hyperspectral imaging, synthetic aperture radar (SAR) imaging, etc.

[0029] In some cases, the auxiliary satellite 110 may provide a TDL to the user device 120. The auxiliary satellite 110 providing the TDL may be a limited function (or dedicated) satellite that provides a limited number (e.g., one) functions to the user device 120. In some cases, a first auxiliary satellite 110 providing a first TDL may communicate using a first waveform and cryptographic scheme, and a second auxiliary satellite 110 may communicate using a second waveform and cryptographic scheme. In some cases, the auxiliary satellite 110 may include a solar panel array that generates power for the auxiliary satellite 110 (e.g., to charge a battery power supply at the auxiliary satellite 110). References herein Figure 12 and Figure 14 Additional details regarding the configuration of the auxiliary satellite 110 are described.

[0030] Commercial satellite 115 may be configured to provide broadband services (e.g., internet services, audio or video broadcast services, etc.) to user device 120. In some cases, commercial satellite 115 is configured to support one or more communication protocols. In some examples, commercial satellite 115 may be configured with a first communication protocol (which may also be referred to as a "commercial communication protocol") for communicating with gateway satellite 105, user device 120, and commercial gateway 125. In some examples, commercial satellite 115 may include a set of radios and radio components for communicating with different types of satellites. In other examples, commercial satellite 115 may be configured with a commercial communication protocol for communicating with user device 120 and commercial gateway 125 and a second communication protocol (e.g., a GW / CL communication protocol) for communicating with gateway satellite 105. In some examples, commercial satellite 115 may include multiple sets of radios and radio components for communicating with different types of satellites. In some cases, commercial satellite 115 may include a solar panel array that generates electricity for commercial satellite 115 (e.g., to charge a battery power supply at commercial satellite 115).

[0031] User devices 120 may be configured to provide functionality to or for a user (e.g., a human user, a sensor, etc.). User devices 120 may include cellular phones, personal assistants, televisions, computers, land vehicles (such as cars, tanks, etc.), aircraft (such as airplanes, helicopters, drones, etc.). In some cases, user devices 120 may include remote sensing equipment, surveillance equipment, and military instruments. User devices 120 may also include computer servers that store information for a network of user devices.

[0032] Business gateway 125 may be configured to route communications between commercial satellites 115 and an Earth-based commercial information network (e.g., the Internet). In some cases, the commercial information network may be an information network supported by significant infrastructure (e.g., commercial satellites 115, big data servers, and miles of network cables). Business gateway 125 may be land-based or space-based. In some cases, business gateway 125 may include a satellite dish configured to transmit signals to and receive signals from commercial satellites 115. In some cases, business gateway 125 may be configured to support one or more communication protocols. In some examples, business gateway 125 may be configured with a first communication protocol (which may also be referred to as a "business gateway communication protocol") for communicating with commercial satellites 115 and user devices 120. In other examples, business gateway 125 may be configured with a business gateway communication protocol for communicating with commercial satellites 115 and a second communication protocol (which may also be referred to as a "network protocol") for communicating with user devices 120 (such as a network server that may be used to relay communications to individual user devices 120).

[0033] Satellites can be launched into different orbits. For example, satellites can be launched into geosynchronous orbit (GEO), medium Earth orbit (MEO), low Earth orbit (LEO), or highly elliptical orbit (HEO). GEO satellites can orbit the Earth at a speed that matches the Earth's rotational speed, thereby maintaining a single position relative to a point on the Earth. LEO satellites can orbit the Earth at a speed that exceeds the Earth's rotational speed, so the satellite's position relative to a point on the Earth can change as the satellite travels through LEO. LEO satellites can be launched at low inclinations (e.g., equatorial low Earth orbit (ELEO)) or high inclinations (e.g., polar orbits) to provide different types of coverage and revisit times for a given area of the Earth. MEO satellites can also orbit the Earth at speeds that exceed the Earth's rotational speed, but can be at higher altitudes than LEO satellites. HEO satellites can orbit the Earth in an elliptical pattern, in which the satellite moves closer to and farther from the Earth throughout the HEO. In some examples, gateway satellites 105 and auxiliary satellites 110 can be placed in LEO, and commercial satellites 115 can be placed in GEO.

[0034] Satellites can communicate with user devices located within a corresponding geographic coverage area 135. A satellite's geographic coverage area 135 can be based on whether the satellite has a direct communication path to the user device 120 (which can also be referred to as "line-of-sight" coverage). In some cases, satellites in different orbits can provide different levels of coverage. For example, due to the closer proximity of LEO satellites to the Earth, satellites in LEO can cover a smaller geographic area at any one time than satellites in GEO. In addition, because the position of a satellite in LEO relative to a point on the Earth changes as the satellite orbits, the satellite's current geographic coverage area 135 also changes as the satellite orbits—that is, the geographic area of the Earth over which the user device 120 can communicate with the satellite can move with the satellite.

[0035] In some cases, a satellite is limited to communicating with user devices 120 located within the satellite's current geographic coverage area 135 (which may also be referred to as line-of-sight operation). For example, a LEO satellite providing communication services may be limited to connecting to user devices 120 within the satellite's current geographic coverage area 135. In some cases, to provide constant coverage across the Earth, multiple satellites (or satellite constellations) may be strategically deployed within LEOs and communicatively linked together (e.g., via cross-links) so that the combined geographic coverage area 135 of the multiple satellites consistently covers most or all of the service area. In some cases, multiple satellites may be deployed using different LEOs (e.g., different altitudes, different inclinations) and / or deployed in different time / position slots of the same LEO (e.g., same altitude, same inclination). In some examples, a first gateway satellite 105 and an auxiliary satellite 110 within a cluster 130 may be located in a first LEO, and a second gateway satellite 105 and an auxiliary satellite 110 within another cluster 130 may be located in a second LEO. In some cases, cluster 130 may also be referred to as a mini-constellation. The first LEO and the second LEO may have different altitudes or inclinations, or may have the same altitude and inclination but at different time / position locations within their orbits. A service area may be associated with the entire geographic area served by a satellite or satellite constellation, even if the service is currently being provided to only a portion of the geographic area at a particular time.

[0036] Satellites may be used to provide a variety of functionalities (e.g., global positioning services, earth sensing services, satellite imaging services, voice communication services, data communication services, etc.) to user device 120. In some cases, satellites in certain orbits may be more suitable for providing certain functionalities to user device 120—for example, satellites in LEO may be used to provide low-latency communication services to satellite phones, while satellites in GEO may be used to monitor weather patterns in a particular area.

[0037] In some cases, a single satellite (e.g., an auxiliary satellite 110 configured as a TDL) may be used to provide a single function to a user device 120. In other cases, a single satellite may be used to provide multiple functions to a user device—for example, a single satellite may be used to provide global positioning services, communication services, and potentially additional services to a user device. In some cases, a satellite capable of providing multiple functions to a user device may be larger, heavier, and / or more complex (e.g., mechanically and electrically) than a satellite capable of providing fewer (e.g., one) functions. In addition, the costs associated with launching a satellite that provides multiple functions may increase relative to a satellite that provides fewer functions (e.g., if the size and weight of the satellite are increased to support the multiple functions). In addition, in some cases, a satellite may not be able to provide certain combinations of functions (e.g., if signaling for one function would interfere with signaling for another function).

[0038] In some cases, user device 120 may communicate with a satellite using a single communication protocol (e.g., if the satellite provides a single function or uses the same communication protocol for multiple functions). A communication protocol may include methods for packaging data (e.g., methods for breaking data into smaller parts, generating header information, etc.), methods for encrypting data, and / or methods for transmitting data (e.g., methods for transmitting within a frequency within a specific frequency range). In other cases, user device 120 may communicate with a satellite using multiple communication protocols (e.g., if the satellite uses multiple communication protocols for multiple functions).

[0039] In some cases, a network of dedicated satellites can be used to provide multiple functionalities to user device 120. That is, multiple functionalities can be distributed across multiple dedicated satellites—for example, a first satellite can provide a first functionality to user device 120, a second satellite can provide a second and a third functionality to user device 120, a third satellite can provide a fourth functionality to user device 120, and so on. In some cases, the first dedicated satellite can transmit within a first frequency range, and the second dedicated satellite can transmit within a second frequency range. In some cases, the network of dedicated satellites can be formed in a coordinated manner—for example, the network of dedicated satellites can include multiple satellites deployed by a single operator. In other cases, the network of satellites can be formed in an uncoordinated manner—for example, the network of dedicated satellites can include multiple satellites deployed by multiple operators. By distributing functionalities across multiple dedicated satellites rather than including all functionalities on a single satellite, a wide variety of functionalities can be provided to user device 120, while keeping the size and complexity of the satellites serving user device 120 to a reasonable level.

[0040] In some cases, user device 120 may use a single communication protocol to communicate with a network of dedicated satellites (e.g., if a single operator deploys dedicated satellites). In other cases, user device 120 may use multiple communication protocols to communicate with a network of dedicated satellites (e.g., if different operators independently deploy dedicated satellites). For example, if user device 120 uses multiple communication protocols to communicate with a network of dedicated satellites, user device 120 may use a first communication protocol to communicate with a first dedicated satellite providing global positioning services and a second communication protocol to communicate with a second dedicated satellite providing communication services.

[0041] Using multiple communication protocols to communicate with a single satellite or a network of dedicated satellites can increase the cost, size, and / or complexity of the satellite and user device 120. That is, the satellite may include additional circuitry and be programmed with additional instructions to support multiple communication protocols—for example, a satellite may have a first set of components and instructions to support communication with a first dedicated satellite and a second set of components and instructions to support communication with a second dedicated satellite. Similarly, user device 120 may include additional circuitry and programming to support multiple communication protocols.

[0042] Additionally, in some cases, the number of functions that user device 120 can access from a dedicated satellite's network may be limited by the capabilities of user device 120—e.g., a user device 120 limited to supporting two communication protocols may be limited to accessing functions provided by satellites that also use those two communication protocols. Consequently, user device 120 may not be able to access desired functions of satellites that are within communication range of user device 120 but that use unsupported communication protocols or incompatible radio equipment—e.g., user device 120 may not be able to access previously or recently launched satellites that provide different or enhanced functions that would benefit user device 120.

[0043] Additionally, dedicated satellites using different communication protocols may not be able to communicate with each other. Thus, a user device 120 using a first function (e.g., a communication service) provided by a first dedicated satellite may not be able to communicate with another user device 120 also using the first function provided by a second dedicated satellite—for example, because the first dedicated satellite and the second dedicated satellite may not be able to communicate with each other. In some cases, the first dedicated satellite and the second dedicated satellite may be deployed by different operators. In other cases, the first dedicated satellite and the second dedicated satellite may be deployed by the same operator.

[0044] To increase the number of satellite functions available to user equipment 120 without increasing or only slightly increasing the complexity and / or size of the satellite or user equipment, a satellite constellation (which may also be referred to as a cluster) may be used that includes satellites that provide dedicated functions and satellites that route communications between incompatible satellites (e.g., satellites that use different communication protocols).

[0045] For example, to reduce the complexity and size of dedicated satellites in a satellite network, gateway satellites 105 may provide routing services to and between auxiliary satellites 110 included in cluster 130. In some cases, gateway satellites 105 and auxiliary satellites 110 included in cluster 130 may be orbitally coupled to each other. That is, gateway satellites 105 and auxiliary satellites 110 may remain within direct communication range of each other throughout their orbits—exemplary direct communication may include communication transmitted via signals from auxiliary satellite 110 to gateway satellite 105. In some examples, auxiliary satellites 110 within cluster 130 may only communicate directly with gateway satellite 105. In some cases, auxiliary satellites 110 may communicate with other auxiliary satellites 110 within cluster 130 (e.g., may serve as relays between gateway satellite 105 and other auxiliary satellites 110). In some examples, the communication path between gateway satellite 105 and auxiliary satellite 110 may be represented by GW / TDL communication link 140. In some cases, GW / TDL communication link 140 may also be referred to as an intra-cluster communication link.

[0046] In some cases, the gateway satellite and the auxiliary satellite are deployed so that their orbits remain within a certain distance of each other—for example, within a few kilometers, tens of kilometers, or hundreds of kilometers. In some cases, the gateway satellite 105 can use an omnidirectional antenna or one or more directional antennas to maintain a connection with the auxiliary satellite 110 spatially arranged around the gateway satellite 105. Thus, the orbitally coupled satellites can orbit within range of each other to communicate at power levels suitable for satellite applications. In some cases, the auxiliary satellite is oriented in a certain position so that a directional communication link can be maintained with the gateway satellite 105. In some cases, multiple clusters 130 can be configured to form a constellation of clusters 130. In some cases, the orbitally coupled satellites within a cluster 130 are positioned in the same orbital plane.

[0047] In some cases, the gateway satellite 105 may be configured to route communications between a first auxiliary satellite 110 providing a first functionality (e.g., a communication service) and using a first communication protocol, and a second auxiliary satellite 110 providing a second functionality (e.g., a different communication service or a satellite imaging service) and using a second communication protocol. In some cases, the gateway satellite 105 may not provide direct functionality to the user device 120. In some cases, the first auxiliary satellite 110 may transmit using a first frequency range, and the second auxiliary satellite 110 may transmit using a second frequency range. In some examples, the first auxiliary satellite 110 and the second auxiliary satellite may be deployed in the same constellation 130 associated with the gateway satellite 105. In some cases, the current geographic coverage area 135 of the first auxiliary satellite 110 and the current geographic coverage area 135 of the second auxiliary satellite 110 may completely or substantially overlap. In some examples, both geographic coverage areas 135 may include a particular user device 120 using the first communication protocol.

[0048] For example, a user device 120 connected to a first auxiliary satellite 110 may seek to obtain information from a second auxiliary satellite 110. The user device 120 may transmit the communication to the first auxiliary satellite 110 via a first TDL communication link 160 according to a first communication protocol. Transmitting the communication according to the first communication protocol may include constructing a data packet conforming to the first communication protocol, encrypting the data in the data packet using the encryption scheme used by the first communication protocol, and transmitting the data packet within certain frequency resources according to the physical layer specified by the first communication protocol. In some cases, the communication may be intended for another user device 120 using a different communication protocol or may request functionality not provided by the first auxiliary satellite 110. The first auxiliary satellite 110 may determine that the first auxiliary satellite 110 is unable to complete the communication and may relay the communication or data included in the communication to the gateway satellite 105 via the GW / TDL communication link 140. In some cases, the communication or data may be relayed using the first communication protocol and / or the gateway communication protocol connecting the gateway satellite 105 to the auxiliary satellite 110.

[0049] The gateway satellite 105 may decode all or a portion of the relayed communication to determine the destination of the communication. For example, the gateway satellite 105 may determine that the second auxiliary satellite 110 is the destination of the communication based on determining that the second auxiliary satellite 110 is in communication with the user equipment 120, which is the intended recipient of the communication. In another example, the gateway satellite 105 may determine that the second auxiliary satellite 110 is the destination of the communication based on determining that the second auxiliary satellite 110 provides the functionality requested in the communication. The gateway satellite 105 may then relay (or forward) the communication or data from the communication to the second auxiliary satellite 110 via the GW / TDL communication link 140—e.g., by transmitting the communication or data using the second communication protocol and / or the gateway communication protocol.

[0050] The second auxiliary satellite 110 may receive and process the relayed communication. In some examples, the second auxiliary satellite 110 may complete the relayed communication by identifying the intended user and relaying the communication to the intended user device 120 via the second TDL communication link 165. In some examples, the second auxiliary satellite 110 may perform the requested function (e.g., may identify an image of the identified area) and transmit a second communication including the requested information back to the gateway satellite 105 via the GW / TDL communication link 140. The gateway satellite 105 may then relay the second communication to the first auxiliary satellite 110 via the GW / TDL communication link 140, which may relay the second communication to the original user device 120 via the first TDL communication link 160. By using the gateway satellite 105 to route communications between the first and second auxiliary satellites 110, the user device 120 may be able to access the second function of the second auxiliary satellite 110 via the first and gateway satellites 105. That is, the gateway satellite 105 may provide interoperability between incompatible auxiliary satellites 110.

[0051] In some cases, the gateway satellite 105 can be used to route communications between a first auxiliary satellite 110 that provides a first function (e.g., a communication service) and uses a first communication protocol, and a second auxiliary satellite 110 that provides the first function and uses the first communication protocol but is outside of communication range with the first auxiliary satellite 110. In some examples, the first auxiliary satellite 110 can be deployed in a first constellation 130 centered around the first gateway satellite 105, and the second auxiliary satellite 110 can be deployed in a second constellation 130 centered around the second gateway satellite 105. In some cases, the current geographic coverage area 135 of the first auxiliary satellite 110 and the current geographic coverage area 135 of the second auxiliary satellite 110 may not overlap completely or substantially. In some examples, only one of these geographic coverage areas 135 may include a particular user device 120.

[0052] For example, a user device 120 connected to a first auxiliary satellite 110 may seek to send a communication to a second user device 120 connected to a second auxiliary satellite 110. The user device 120 transmits the communication to the first auxiliary satellite 110 via a first TDL communication link 160 according to a first communication protocol. In some cases, the first auxiliary satellite 110 may not be able to relay the communication to the second auxiliary satellite 110 (e.g., due to transmission constraints). Therefore, the first auxiliary satellite 110 may relay the communication to a first gateway satellite 105 (e.g., a gateway satellite 105 associated with the cluster of the first auxiliary satellite 110) via a GW / TDL communication link 140. The first gateway satellite 105 may relay the communication to a second gateway satellite 105 serving the second auxiliary satellite 110 via a GW / GW communication link 145. The second gateway satellite 105 may relay the communication to the second auxiliary satellite 110 via the GW / TDL communication link 140. And the second auxiliary satellite 110 may send the communication to the second user device 120 via the first TDL communication link 160. In some examples, user device 120 may similarly access a second functionality (eg, satellite imaging) of a second auxiliary satellite 110 connected to a second gateway satellite 105 .

[0053] By using multiple gateway satellites 105 to relay communications between ancillary satellites 110, user devices 120 may be able to obtain previously unavailable beyond-horizon information. That is, the geographic coverage area 135 for the services provided by an ancillary satellite 110 (which itself is limited to providing such services to the current geographic coverage area 135) may be expanded to include additional geographic coverage areas 135 currently covered by other ancillary satellites 110. Additionally, user devices 120 may be able to access functionality (e.g., satellite imaging services) of an ancillary satellite 110 that currently covers a different geographic coverage area 135 than another ancillary satellite 110 that is connected to or within communication range of the user device 120—e.g., a user device 120 configured for communication services may obtain satellite imaging of a geographic area that is not within the geographic coverage area 135 of an ancillary satellite 110 providing communication services to the user device 120 and / or an ancillary satellite 110 providing imaging services to the geographic coverage area 135.

[0054] In some cases, the gateway satellite 105 may be used to route communications between a first auxiliary satellite 110 that provides a first function (e.g., communication services) and uses a first communication protocol and a commercial satellite 115 that provides access to a commercial information network (e.g., the Internet) and uses a second communication protocol (e.g., the Internet Protocol).

[0055] For example, a user device 120 connected to a first auxiliary satellite 110 may seek access to a commercial information network. The user device 120 may transmit a communication to the first auxiliary satellite 110 via a first TDL communication link 160 according to a first communication protocol. The first auxiliary satellite 110 may not have a direct connection to the commercial information network and may therefore relay the communication to the gateway satellite 105 via a GW / TDL communication link 140. After determining that the communication is destined for a commercial information network (e.g., according to a routing table, the next hop for the communication is a commercial communication satellite), the gateway satellite 105 may relay the communication to the commercial satellite 115 via a GW / CL communication link 150. The commercial satellite 115 may relay the communication to the commercial gateway 125 via a commercial gateway communication link 155. The commercial gateway 125 may then relay the communication to the requesting user device 120 (e.g., a server or personal device) via a network communication link 170. The network communication link 170 may be a wired or wireless communication link and may span one or more networks (e.g., an intranet or the Internet). In some cases, business gateway 125 may relay the communication to a server, which may process the communication or relay the communication to individual user device 120. In some examples, user device 120 may similarly access the functionality of an auxiliary satellite 110 that is not configured for a business information network by transmitting the communication to auxiliary satellite 110 via business gateway 125, business satellite 115, and gateway satellite 105. In some examples, business satellite 115 may be configured to route communications between gateway satellites 105.

[0056] By routing communications to and from the auxiliary satellite 110 using the commercial satellite 115 and the gateway satellite 105, the auxiliary satellite 110, which would not otherwise be able to access the commercial information network, can be connected to the commercial information network. Thus, any user device 120 connected to the commercial information network can gain access to information obtained by the auxiliary satellite 110, regardless of the location of the auxiliary satellite 110.

[0057] The use of the constellation 130 associated with the gateway satellite 105 may also enable additional functionality to be provided to the user device 120 over time—for example, by adding an auxiliary satellite 110 to the constellation 130 associated with the gateway satellite 105 after the gateway satellite 105 is launched and / or operational. In some cases, the auxiliary satellite 110 is added to the constellation 130 by launching the auxiliary satellite 110 into a position for orbital coupling with the gateway satellite 105. In some cases, the gateway satellite 105 may use a gateway communication protocol to identify the newly launched auxiliary satellite 110. In some cases, the added auxiliary satellite 110 may provide functionality that is different from that currently provided by the auxiliary satellite 110 connected to the gateway satellite 105. In some cases, the added auxiliary satellite 110 may also use a different communication protocol than the currently connected auxiliary satellite 110 and / or user device 120. However, the added auxiliary satellite may be able to communicate with the gateway satellite 105 using the gateway communication protocol. Thus, the gateway satellite 105 may be able to route communications between the newly added auxiliary satellite 110 and the previously connected auxiliary satellite 110. By using the gateway satellite 105 to route communications between incompatible auxiliary satellites 110 , the user equipment 120 may access new functionality from the otherwise incompatible auxiliary satellites 110 .

[0058] In some cases, an auxiliary satellite 110 added to a cluster 130 associated with a gateway satellite 105 may provide redundant functionality to the auxiliary satellite 110 previously connected to the gateway satellite 105. By launching an auxiliary satellite 110 providing redundant functionality into a cluster 130, the cluster 130 may become more robust to failures of the auxiliary satellite 110 or be able to support additional user devices 120 or higher data rates.

[0059] Thus, by deploying a cluster 130 comprising auxiliary satellites 110 and gateway satellites 105 (which provide connectivity between incompatible satellites providing common or different functionality), a collection of independent satellites can be transformed into an interconnected network of satellites. Consequently, the functionality available to a user device 120 that has access to one of the auxiliary satellites 110 can be expanded to include access to otherwise inaccessible functionality provided by other auxiliary satellites 110. Furthermore, a wide variety of functionality can be provided to user devices 120 while utilizing low-complexity satellites that each provide a limited number of functions, without requiring the configuration of multiple communication protocols at the satellites or user devices 120.

[0060] In some cases, the gateway satellite 105 may be configured to provide command and control to the auxiliary satellites 110 within the cluster 130. For example, the auxiliary satellites 110 may not support direct communication with a ground station for command and control, and therefore the gateway satellite 105 may support a single command and control interface for the auxiliary satellites 110. In some examples, the gateway satellite 105 may determine commands for the auxiliary satellites (e.g., based on determining an orbital change, a positioning change, or a change in antenna pointing, a communication parameter change). For example, the gateway satellite 105 may include sensors or other equipment for determining when to modify the settings or orbital characteristics of the auxiliary satellites 110. Additionally or alternatively, the gateway satellite 105 may receive commands for the auxiliary satellites 110 from a control center (e.g., via a ground link or a link to a commercial communications satellite). In some cases, the command and control is associated with instructions to maintain the orbit of the auxiliary satellites 110 within the cluster 130. In some examples, the gateway satellite 105 may send commands instructing one or more auxiliary satellites 110 to modify the orbital path (e.g., to correct the orbit of the auxiliary satellite 110 or avoid debris). In some examples, gateway satellite 105 may send a command instructing one or more auxiliary satellites 110 to deorbit.

[0061] Figure 2 200. Aspects of a satellite communication subsystem 200 supporting a decentralized satellite constellation as disclosed herein are shown. The satellite communication subsystem 200 may include a gateway satellite 205, which may be a reference satellite. Figure 1 An example of a gateway satellite is described. The gateway satellite 205 can be a LEO satellite.

[0062] The satellite communication subsystem 200 may include a first auxiliary satellite 210, a second auxiliary satellite 215, and a third auxiliary satellite 220, which may be reference satellites. Figure 1 The first auxiliary satellite 210, the second auxiliary satellite 215 and the third auxiliary satellite 220 can be orbitally coupled with the gateway satellite 205, as shown in FIG. Figure 1 Thus, the gateway satellite 205, the first auxiliary satellite 210, the second auxiliary satellite 215, and the third auxiliary satellite 220 may be arranged within the cluster 235 and may communicate with each other using the first GW / TDL communication link 245, the second GW / TDL communication link 250, and the third GW / TDL communication link 255, as described with reference to FIG. Figure 1 Described generally.

[0063] In some cases, the first auxiliary satellite 210 can be configured for a first TDL communication protocol, the second auxiliary satellite 215 can be configured for a second TDL communication protocol, and the third auxiliary satellite 220 can be configured for a third TDL communication protocol. In some cases, additional auxiliary satellites can be added to the cluster 235—for example, by launching an auxiliary satellite into a position to be orbitally coupled with the gateway satellite 205. In some cases, the gateway satellite 205 can identify the auxiliary satellites in orbital coupling with the gateway satellite 205 by transmitting a discovery message according to the gateway communication protocol.

[0064] The satellite communication subsystem 200 may include a first user device 225 and a second user device 230, which may be reference Figure 1 An example of a user device is described. A first user device 225 and a second user device 230 may be located within a geographic coverage area 240 of a cluster 235. The first user device 225 may communicate with the second auxiliary satellite 215 using a first TDL communication link 260, and the second user device 230 may communicate with the second auxiliary satellite 215 using a second TDL communication link 265, as described with reference to FIG. Figure 1 Generally described. In some cases, the first user device 225 can be configured for a first TDL communication protocol, and the second user device 230 can be configured for a second TDL communication protocol.

[0065] As discussed above and herein, a first auxiliary satellite (e.g., the first auxiliary satellite 210) may be configured with a first TDL communication protocol and provide first functionality, and a second auxiliary satellite (e.g., the second auxiliary satellite 215) may be configured with a second TDL communication protocol and provide second functionality. The first auxiliary satellite and the second auxiliary satellite may also currently cover substantially overlapping geographic areas. In some cases, a user device located within the substantially overlapping geographic areas may be able to access only one of the auxiliary satellites—for example, if the user device is configured for only one of the first TDL communication protocol and the second TDL communication protocol. Thus, the user device may be prevented from communicating with other user devices within the substantially overlapping geographic areas. Additionally, the user device may be prevented from accessing functionality of other auxiliary satellites (e.g., the third auxiliary satellite 220) that were otherwise within the user device's communication range.

[0066] To increase the number of functions available to user devices and / or to connect user devices that use incompatible TDL communication protocols, a gateway satellite (e.g., gateway satellite 205) may be orbitally coupled with auxiliary satellites (e.g., first auxiliary satellite 210, second auxiliary satellite 215, and third auxiliary satellite 220) to form a satellite cluster 235. The gateway satellite may be configured to route communications between the auxiliary satellites, for example, using protocol conversion and waveform normalization techniques.

[0067] By orbitally coupling the gateway satellite with multiple auxiliary satellites, the functionality of all auxiliary satellites can be provided to user devices (e.g., the first user device 225 and the second user device 230) within the geographical coverage area of the cluster. Similarly, a user device (e.g., the first user device 225) using a first TDL communication protocol may be able to communicate with another user device (e.g., the second user device 230) using a second TDL communication protocol via the gateway satellite. Figure 3 and Figure 4 Exemplary communications utilizing a gateway satellite to provide additional functionality and connect otherwise incompatible user devices are discussed in greater detail.

[0068] Figure 3 Aspects of a process flow 300 for supporting and utilizing a decentralized satellite constellation as disclosed herein are shown. The process flow 300 may be referenced by Figure 2 The depicted gateway satellite 205, first auxiliary satellite 210, third auxiliary satellite 220, and first user device 225 perform. In some examples, process flow 300 illustrates aspects of a process for enabling a user device to access functionality of auxiliary satellites that would otherwise be inaccessible to the user device by using a gateway satellite.

[0069] At block 303, the gateway satellite 205 may identify one or more auxiliary satellites (including the first auxiliary satellite 210 and the third auxiliary satellite 220) that are in orbital coupling with the gateway satellite 205. In some cases, the gateway satellite 205 discovers the one or more auxiliary satellites by broadcasting a discovery message. In some examples, the gateway satellite 205 may discover the first auxiliary satellite 210 after receiving a discovery response message. In some cases, the gateway satellite 205 may discover a first set of auxiliary satellites during a first discovery procedure and may discover a second set of auxiliary satellites during a subsequent procedure. In some examples, the first set of auxiliary satellites may be launched together with the gateway satellite 205, and the second set of auxiliary satellites may be launched after the first set of auxiliary satellites. In some examples, the discovery and response messages are transmitted according to a gateway communication protocol. After identifying the auxiliary satellites, the gateway satellite 205 may establish a connection with the auxiliary satellites.

[0070] At block 305, the first user device 225 may generate a communication. In some cases, the communication may include a request for information associated with functionality provided by the third auxiliary satellite 220. As discussed above, the first user device 225 may be unable to communicate directly with the third auxiliary satellite 220—e.g., due to incompatible communication protocols and / or transmission failures.

[0071] At arrow 310, the first user device 225 may transmit the communication to the first auxiliary satellite 210 via the first TDL communication link 260 using the first TDL communication protocol. Transmitting the communication using the first TDL communication protocol may include encrypting a request included in the communication, packaging the encrypted request into a data packet, and transmitting the data packet as a waveform according to the first TDL communication protocol.

[0072] At block 315, the first assistive satellite 210 may identify the intended destination of the communication. In some cases, identifying the intended destination includes identifying that the communication is not directed to a user device currently in communication with the first assistive satellite 210. In some cases, the first assistive satellite 210 determines that the intended user device is not currently in communication with the first assistive satellite 210 by decoding a receiver address included in the communication and failing to match the receiver address with a list of addresses of active user devices (e.g., a list of user devices currently within communication range of the first assistive satellite 210).

[0073] At arrow 320, the first assisting satellite 210 may relay the communication to the gateway satellite 205 via the first GW / TDL communication link 245 based on a determination that the communication is not directed to a user device currently communicating with the first assisting satellite 210. In some cases, the first assisting satellite 210 relays the communication by transmitting the communication using the GW / TDL communication protocol. Transmitting the communication using the GW / TDL communication protocol may include extracting data from the communication, encrypting the data, repackaging the data into data packets, and transmitting the data packets in a waveform according to the GW / TDL communication protocol. In some cases, the extracted data is encrypted according to the standards of a second TDL communication protocol. In other cases, transmitting the communication using the GW / TDL communication protocol includes encapsulating the communication in data packets composed according to the GW / TDL communication protocol without extracting data from the communication. In other cases, the first assisting satellite 210 relays the communication by relaying the communication using the first TDL communication protocol without extracting data from the communication.

[0074] At block 325, the gateway satellite 205 may determine a destination node for the communication. In some cases, determining the destination node includes decrypting data in the communication and / or identifying a receiver address included in the communication. In some cases, the gateway satellite 205 may compare the decoded receiver address with a list of addresses of auxiliary satellites included in the cluster 235 and / or a list of addresses of active user devices currently within communication range of the cluster 235 (e.g., within the geographic coverage area 240). In some examples, the gateway satellite 205 may determine that the communication is intended for the third auxiliary satellite 220, for example, based on matching the decoded address with an address stored for the third auxiliary satellite 220.

[0075] In some examples, the gateway satellite 205 can maintain a LAN for communicating with the secondary satellites of the cluster 235. For example, the gateway satellite 205 can serve as an access point (AP) for the LAN of the cluster 235 and can perform NAT between the LAN of the cluster 235 and WAN addresses. The gateway satellite 205 can assign LAN addresses to the secondary satellites within the cluster 235 (e.g., the secondary satellites can be given LAN addresses on the same subnet). The gateway satellite 205 can perform NAT so that the gateway satellite 205 can route communications to and from each secondary satellite via other gateway satellites or commercial communications satellites (e.g., using WAN routing or public IPv4 or IPv6 addresses). The gateway satellite 205 can perform static or dynamic NAT and can push updates to the routing table of neighboring hops on the WAN (e.g., other gateway satellites 205, commercial communications satellites).

[0076] In some examples, the gateway satellite 205 may include a routing table for determining a communication path from the gateway satellite 205 to the intended auxiliary satellite or user device. In some cases, the routing table indicates a communication path for reaching the intended auxiliary satellite or user device via one or more intermediate satellites (e.g., intermediate auxiliary satellites, gateway satellites, and / or commercial satellites). For example, after determining the receiver address, the gateway satellite 205 may determine that the associated auxiliary satellite or user device is currently covered by the gateway satellite 205 and may relay the communication to the auxiliary satellite or the auxiliary satellite connected to the user device. In another example, after determining the receiver address, the gateway satellite 205 may determine that the associated auxiliary satellite or user device is not served by the gateway satellite 205 and may consult its routing table to find the next communication hop of the communication path to the receiver address. The gateway satellite 205 may transmit the communication to a network node (e.g., another gateway satellite, a commercial communication satellite) determined as the next hop based on the routing table. For example, the network node may be an intermediate gateway satellite, which may then transmit the communication to a gateway satellite serving the auxiliary satellite associated with the receiver address based on a routing table stored at the intermediate gateway satellite, and the gateway satellite may transmit the communication to the intended auxiliary satellite.

[0077] At arrow 330, the gateway satellite 205 may relay the communication to the third auxiliary satellite 220 via the third GW / TDL communication link 255 based on determining that the third auxiliary satellite 220 is the next network hop for the communication (e.g., based on a routing table). In some cases, relaying the data extracted from the communication to the third auxiliary satellite 220 includes packaging, encrypting, and / or transmitting the communication according to the GW / TDL communication protocol. In other cases, the gateway satellite 205 relays the communication without extracting the data by encapsulating the request included in the communication in a data packet composed according to the GW / TDL communication protocol. In other cases, the gateway satellite 205 relays the communication without extracting the data by relaying the communication using the third TDL communication protocol used by the third auxiliary satellite 220.

[0078] At arrow 335, the third auxiliary satellite 220 may transmit a response to the request included in the communication to the gateway satellite 205 via the third GW / TDL communication link 255. In some cases, the response may include data acquired using functionality provided by the third auxiliary satellite 220. For example, the third auxiliary satellite 220 may be configured to acquire satellite imaging and may transmit a response including an image of a specific location based on decoding the request for an image of the specific location. The third auxiliary satellite 220 may transmit the response using the GW / TDL communication protocol or the third TDL communication protocol.

[0079] At arrow 340, the gateway satellite 205 may determine the destination node for the response, as similarly described with reference to block 325. In some cases, the gateway satellite 205 may determine that the first auxiliary satellite 210 is the destination node.

[0080] At arrow 345 , the gateway satellite 205 may relay the response received from the third auxiliary satellite 220 to the first auxiliary satellite 210 via the first GW / TDL communication link 245 , for example, using the GW / TDL or first TDL communication protocol.

[0081] At arrow 350, the first auxiliary satellite 210 may relay the response to the first user device 225 via the first TDL communication link 260, for example, using the first TDL communication protocol. After receiving the response, the first user device 225 may decode the data packet. Thus, the first user device 225 may access functionality of an auxiliary satellite that uses a different communication protocol or is outside the communication range of the first user device 225.

[0082] Figure 4 1 shows aspects of a process flow 400 for supporting and utilizing a decentralized satellite constellation as disclosed herein. The process flow 400 may be performed by a process flow as described in reference to FIG. Figure 2The depicted gateway satellite 205, first auxiliary satellite 210, second auxiliary satellite 215, first user device 225, and second user device 230 perform the process described. In some examples, process flow 400 illustrates aspects of a process of enabling a user device to communicate with another user device configured with an incompatible communication protocol.

[0083] At block 403, the gateway satellite 205 may identify one or more auxiliary satellites, such as reference satellites. Figure 3 Block 303 is similarly described.

[0084] At block 405, the first user device 225 may generate a communication. In some cases, the communication may include a message (e.g., a voice or data message) for the second user device 230. As discussed above, the first user device 225 may not be able to communicate directly with the second user device 230—e.g., due to incompatible communication protocols and / or transmission failures.

[0085] At arrow 410, the first user device 225 may transmit the communication to the first auxiliary satellite 210 via the first TDL communication link 260, as shown in FIG. Figure 3 At block 415, the first auxiliary satellite 210 may identify the intended destination of the communication, as described with reference to FIG. Figure 3 At arrow 420, the first auxiliary satellite 210 may relay the communication to the gateway satellite 205 via the first GW / TDL communication link 245, as described with reference to FIG. Figure 3 At block 425, the gateway satellite 205 may determine the destination node for the communication, as described with reference to FIG. Figure 3 At block 430, the gateway satellite 205 may relay the communication to the second auxiliary satellite 215 via the second GW / TDL communication link 250, as described with reference to FIG. Figure 3 The arrow 330 is similarly described.

[0086] At arrow 435, the second auxiliary satellite 215 may relay the communication to the second user device 230. In some cases, the second auxiliary satellite 215 may relay the communication to the second user device 230 using a second communication protocol. Thus, the first user device 225 may communicate with another user device that uses a different communication protocol than the first user device 225. In some cases, the second user device 230 may similarly transmit a message (e.g., a response) to the first user device 225.

[0087] Figure 51 shows aspects of a satellite communication subsystem 500 supporting a decentralized satellite constellation as disclosed herein. The satellite communication subsystem 500 may include a first gateway satellite 505 and a second gateway satellite 510, which may be reference satellites. Figures 1 to 4 1 and 1 . In some cases, the first gateway satellite 505 may be positioned in a first LEO and the second gateway satellite 510 may be positioned in a second LEO. For example, the second LEO may be located in the same orbital plane and have a phase offset (e.g., 90 degrees) from the first LEO. In other cases, the first gateway satellite 505 may be positioned in a LEO orbit in a different orbital plane.

[0088] The satellite communication subsystem 500 may include a first auxiliary satellite 515, a second auxiliary satellite 520, a third auxiliary satellite 525, and a fourth auxiliary satellite 530, which may be reference satellites. Figures 1 to 4 The first auxiliary satellite 515 can be orbitally coupled with the first gateway satellite 505, as shown in FIG. Figure 1 Thus, the first gateway satellite 505 and the first auxiliary satellite 515 may be arranged within a first cluster 550 and may communicate with each other using a first GW / TDL communication link 570, as described with reference to FIG. Figures 1 to 4 The second auxiliary satellite 520, the third auxiliary satellite 525 and the fourth auxiliary satellite 530 can be orbitally coupled with the second gateway satellite 510, as shown in FIG. Figure 1 Thus, the second gateway satellite 510, the second auxiliary satellite 520, the third auxiliary satellite 525, and the fourth auxiliary satellite 530 may be arranged within a second cluster 555 and may communicate with each other using a second GW / TDL communication link 575, a third GW / TDL communication link 580, and a fourth GW / TDL communication link 585, as described with reference to Figure 1 Described generally.

[0089] In some cases, the first auxiliary satellite 515 and the second auxiliary satellite 520 may be configured for a first TDL communication protocol, the third auxiliary satellite 525 may be configured for a second TDL communication protocol, and the fourth auxiliary satellite 530 may be configured for a third TDL communication protocol.

[0090] The satellite communication subsystem 500 may include a first user device 535, a second user device 540, and a third user device 545, which may be referenced Figures 1 to 45. A first user device 535 may be located within a first geographic coverage area 560 of a first cluster 550. The first user device 535 may communicate with a first auxiliary satellite 515 using a first TDL communication link 595. A second user device 540 and a third user device 545 may be located within a second geographic coverage area 565 of a second cluster 555. The second user device 540 may communicate with a second auxiliary satellite 520 using a second TDL communication link 597, and the third user device 545 may communicate with a third auxiliary satellite 525 using a third TDL communication link 599, as described with reference to FIG. Figures 1 to 4 Described generally.

[0091] In some cases, the first user device 535 and the second user device 540 can be configured for a first TDL communication protocol, and the third user device 545 can be configured for a second TDL communication protocol. In some cases, the second user device 540 can communicate with the fourth auxiliary satellite 530 and / or the third user device 545 within the second geographic coverage area 565, as described with reference to FIG. Figures 2 to 4 Similarly, in some cases, the first user device 535 can communicate with secondary satellites within the first constellation 550 and user devices within the first geographic coverage area 560, as described with reference to FIG. Figures 2 to 4 Similar description.

[0092] As discussed above and herein, a first auxiliary satellite (e.g., the first auxiliary satellite 515) can be configured to provide communication services to user devices using a first TDL communication protocol within a current coverage area of the first auxiliary satellite. In some cases, the user devices may be unable to communicate with other user devices located within the current coverage area of a second auxiliary satellite (e.g., the second auxiliary satellite 520)—for example, if the first auxiliary satellite cannot reach the second auxiliary satellite.

[0093] To extend the communication range of user devices within a first coverage area to reach user devices located in a different coverage area, a first gateway satellite (e.g., first gateway satellite 505) may be orbitally coupled with a first auxiliary satellite (e.g., first auxiliary satellite 515) to form a first satellite constellation (e.g., second constellation 555), and a second gateway satellite (e.g., second gateway satellite 510) may be orbitally coupled with a second auxiliary satellite (e.g., second auxiliary satellite 520) to form a second satellite constellation (e.g., second constellation 555). The first gateway satellite may be configured to route communications from the first auxiliary satellite to the second gateway satellite, for example, via a GW / GW communication link 590. The second gateway satellite may relay the communications to the second auxiliary satellite, which may transmit the communications to a second user device located in a different coverage area than the first user device.

[0094] In some cases, commercial satellites (not shown) may be used with Figure 5 The systems shown are used in combination and for relaying communications between gateway satellites. For example, a commercial satellite can be configured to route communications between a first gateway satellite 505 and a second gateway satellite 510 if a GW / GW communication link 590 between the first gateway satellite 505 and the second gateway satellite 510 is absent or fails.

[0095] By forming multiple interconnected clusters, the communication range of the user device can be extended to other coverage areas. Similarly, the user device may be able to communicate with other user devices that use a different TDL communication protocol than the user device or are located in a different coverage area. In addition, the user device can access the functions of auxiliary satellites that use a different TDL communication protocol than the user device and currently cover a different coverage area. Figures 6 to 8 Exemplary communications utilizing a gateway satellite constellation to extend the communication range of user equipment, provide additional functionality to user equipment, and connect user equipment to otherwise incompatible user equipment located in different coverage areas are discussed in greater detail.

[0096] Figure 6 Aspects of a process flow 600 for supporting and utilizing a decentralized satellite constellation as disclosed herein are shown. The process flow 600 may be referenced by Figure 5 The process flow 600 is described as being performed by the first gateway satellite 505, the second gateway satellite 510, the first auxiliary satellite 515, the fourth auxiliary satellite 530, and the first user device 535. In some examples, the process flow 600 illustrates aspects of a process that enables a user device to access functionality of an auxiliary satellite that uses a different communication protocol than the user device and has a current coverage area that does not substantially overlap with the auxiliary satellite currently connected to the user device.

[0097] At block 603, the first gateway satellite 505 may identify one or more auxiliary satellites (including the first auxiliary satellite 515) that are in orbital coupling with the first gateway satellite 505, and the second gateway satellite 510 may identify one or more auxiliary satellites (e.g., the fourth auxiliary satellite 530) that are in orbital coupling with the second gateway satellite 510. In some cases, the first gateway satellite 505 and the second gateway satellite 510 discover the one or more auxiliary satellites based on broadcasting discovery messages and receiving response messages. In some examples, the discovery and response messages are transmitted according to a gateway communication protocol. After identifying the auxiliary satellites, the first gateway satellite 505 may establish a connection with the auxiliary satellites.

[0098] At block 605, the first user device 535 may generate a communication. In some cases, the communication may include a request for information associated with functionality provided by the fourth auxiliary satellite 530. As discussed above, the first user device 535 may be unable to communicate directly with the fourth auxiliary satellite 530—e.g., due to incompatible communication protocols and / or transmission failures.

[0099] At arrow 610, the first user device 535 may transmit the communication using the first TDL communication protocol to the first auxiliary satellite 515 via the first TDL communication link 595. Transmitting the communication using the first TDL communication protocol may include encrypting a request included in the communication, packaging the encrypted request into a data packet, and transmitting the data packet as a waveform according to the first TDL communication protocol.

[0100] At block 615, the first auxiliary satellite 515 may identify the intended destination of the communication. In some cases, identifying the intended destination includes identifying that the communication is not directed to a user device currently in communication with the first auxiliary satellite 515. In some cases, the first auxiliary satellite 515 determines that the intended user device is not currently in communication with the first auxiliary satellite 515 by decoding a receiver address included in the communication and failing to match the receiver address with a list of addresses of active user devices (e.g., a list of user devices currently within communication range of the first auxiliary satellite 515).

[0101] At arrow 620, the first auxiliary satellite 515 may relay the communication to the first gateway satellite 505 via the first GW / TDL communication link 570 based on a determination that the communication is not directed to a user device currently communicating with the first auxiliary satellite 515. In some cases, the first auxiliary satellite 515 may relay the communication by transmitting the communication or data from the communication using the GW / TDL communication protocol. Transmitting the communication using the GW / TDL communication protocol may include extracting data from the communication, encrypting the data, repackaging the data into data packets, and transmitting the data packets in a waveform according to the GW / TDL communication protocol. In some cases, the extracted data is encrypted according to the standards of a second TDL communication protocol. In other cases, transmitting the communication using the GW / TDL communication protocol includes encapsulating the communication in data packets composed according to the GW / TDL communication protocol without extracting data from the communication. In other cases, the first auxiliary satellite 515 relays the communication by relaying the communication using the first TDL communication protocol without extracting data from the communication.

[0102] At block 625, the first gateway satellite 505 may determine a destination node for the communication. In some cases, determining the destination node includes decrypting data in the communication and / or identifying a receiver address included in the communication. In some cases, the first gateway satellite 505 may compare the decoded receiver address with a list of addresses of auxiliary satellites included in the first constellation 550 (e.g., included in a routing table) and / or a list of addresses of active user devices currently within communication range of the first constellation 550. In some examples, the first gateway satellite 505 may determine that the intended destination node is not within the first constellation 550 or is not within the first geographic coverage area 560 of the first constellation 550. In some examples, the first gateway satellite 505 may include a routing table indicating a communication path from the first gateway satellite 505 to the intended auxiliary satellite or user device. In some cases, the communication path includes one or more intermediate satellites.

[0103] In some examples, the first gateway satellite 505 may maintain a LAN for communicating with the secondary satellites of the cluster 550. For example, the first gateway satellite 505 may act as an AP for the LAN of the cluster 550 and may perform NAT between the LAN of the cluster 550 and a WAN address. The gateway satellite 505 may assign LAN addresses to the secondary satellites within the cluster 550 (e.g., the secondary satellites may be given LAN addresses on the same subnet). The first gateway satellite 505 may perform NAT so that the first gateway satellite 505 can route communications to and from each secondary satellite via other gateway satellites (e.g., the second gateway satellite 510) or a commercial communications satellite (e.g., using WAN routing or public IPv4 or IPv6 addresses). For example, the first gateway satellite 505 may determine that a communication is directed to another gateway satellite and may translate the source address included in the communication based on the WAN address of the first gateway satellite 505 and a specific port (e.g., associated with a secondary satellite of the cluster 550). Additionally or alternatively, the first gateway satellite 505 may translate, based on its corresponding port address, communications received with a destination address that matches the WAN address of the first gateway satellite to the secondary satellites of the cluster 550. The first gateway satellite 505 may perform static or dynamic NAT and may push updates to routing tables of neighboring hops on the WAN (e.g., other gateway satellites, commercial communications satellites).

[0104] At arrow 630, the first gateway satellite 505 can relay the communication to the second gateway satellite 510 via the GW / GW communication link 590 based on determining that the communication is intended for a node currently covered by the second constellation 555 (e.g., based on the identified receiver address and / or routing table). In some examples, the first gateway satellite 505 can relay the communication to the second gateway satellite 510 based on determining that the communication is intended for the fourth auxiliary satellite 530 (e.g., based on matching the decoded address with the address stored for the fourth auxiliary satellite 530 and the routing table). In some cases, the first gateway satellite 505 relays the communication to the second gateway satellite 510 by transmitting the communication according to the GW / GW communication protocol. Transmitting the communication according to the GW / GW communication protocol can include encapsulating the communication in a data packet composed according to the GW / GW communication protocol. In some cases, the first gateway satellite 505 may relay the communication to an intermediate gateway satellite, which relays the communication to the second gateway satellite 510 , for example, based on a routing table stored at the first gateway satellite 505 and / or a failure of the GW / GW communication link 590 .

[0105] At block 635, the second gateway satellite 510 may determine a destination node for the communication, as similarly described with reference to block 625. In some cases, the second gateway satellite 510 may determine that the communication is intended for the fourth auxiliary satellite 530, for example, based on matching the decoded address with an address stored for the fourth auxiliary satellite 530. In other cases, the second gateway satellite 510 may determine that the communication is intended for a node not included in the second cluster 555 and may similarly relay the communication to a third gateway satellite via a GW / GW communication link.

[0106] In some examples, the second gateway satellite 510 may maintain a LAN for communicating with the secondary satellites of the cluster 555. For example, the second gateway satellite 510 may serve as an AP for the LAN of the cluster 555 and may perform network address translation (NAT) between the LAN of the cluster 555 and WAN addresses. The second gateway satellite 510 may assign LAN addresses to the secondary satellites within the cluster 555 (e.g., the secondary satellites may be given LAN addresses on the same subnet). The second gateway satellite 510 may perform NAT so that the second gateway satellite 510 can route communications to and from each secondary satellite via other gateway satellites (e.g., the first gateway satellite 505) or a commercial communications satellite (e.g., using WAN routing or public IPv4 or IPv6 addresses). For example, the second gateway satellite 510 may determine that a communication is directed to another gateway satellite and may translate the source address included in the communication based on the WAN address and a specific port of the second gateway satellite 510 (e.g., associated with the secondary satellites of the cluster 555). Additionally or alternatively, the second gateway satellite 510 may translate, based on its corresponding port address, communications received with a destination address that matches the WAN address of the second gateway satellite 510 to the secondary satellites of the cluster 555. The second gateway satellite 510 may perform static or dynamic NAT and may push updates to routing tables of neighboring hops on the WAN (e.g., other gateway satellites, commercial communications satellites).

[0107] At arrow 640, the second gateway satellite 510 may relay the communication to the fourth auxiliary satellite 530 via the fourth GW / TDL communication link 585 based on determining that the fourth auxiliary satellite 530 is the intended destination of the communication (e.g., based on the received address and / or the routing table stored at the second gateway satellite 510). In some cases, relaying the data extracted from the communication to the first auxiliary satellite includes packaging, encrypting, and / or transmitting the communication according to the GW / TDL communication protocol. In other cases, the second gateway satellite 510 relays the communication without extracting the data by encapsulating the request included in the communication in a data packet composed according to the GW / TDL communication protocol. In other cases, the second gateway satellite 510 relays the communication without extracting the data by relaying the communication using the third TDL communication protocol used by the fourth auxiliary satellite 530.

[0108] At arrow 645, the fourth auxiliary satellite 530 may transmit a response to the request included in the communication to the second gateway satellite 510 via the fourth GW / TDL communication link 585. In some cases, the response may include data acquired using functionality provided by the fourth auxiliary satellite 530. For example, the fourth auxiliary satellite 530 may be configured to acquire satellite imaging and may transmit a response including an image of a specific location based on decoding the request for an image of the specific location. The fourth auxiliary satellite 530 may transmit the response using the GW / TDL communication protocol or the third TDL communication protocol.

[0109] At block 650, the second gateway satellite 510 may determine a destination node for the response, as similarly described with reference to block 635. At arrow 655, the second gateway satellite 510 may relay the response to the first gateway satellite 505, as similarly described with reference to arrow 630.

[0110] At block 660, the first gateway satellite 505 may determine a destination node for the response, as similarly described with reference to block 625. In some cases, the first gateway satellite 505 may determine that the first auxiliary satellite 515 is the destination node.

[0111] At arrow 665 , the first gateway satellite 505 may relay the response generated by the fourth assisting satellite 530 to the first assisting satellite 515 via the first GW / TDL communication link 570 , for example, using the GW / TDL or first TDL communication protocol.

[0112] At arrow 670, the first auxiliary satellite 515 may relay the response to the first user device 535 via the first TDL communication link 595, for example, using the first TDL communication protocol. After receiving the response, the first user device 535 may decode the data packet. Thus, the first user device 535 may access the functionality of an auxiliary satellite that uses a different TDL communication protocol and is outside the communication range of the first user device 535. In some cases, the first user device 535 may obtain imaging from the fourth auxiliary satellite 530 that reflects imaging beyond the line of sight of the auxiliary satellites included in the first constellation 550.

[0113] Figure 7 Aspects of a process flow 700 for supporting and utilizing a decentralized satellite constellation as disclosed herein are shown. The process flow 700 may be referenced by Figure 5The process flow 700 is described as being performed by a first gateway satellite 505, a second gateway satellite 510, a first auxiliary satellite 515, a second auxiliary satellite 520, a first user device 535, and a second user device 540. In some examples, the process flow 700 illustrates aspects of a process that enables a user device to perform extended range communications when an auxiliary satellite connected to the user device cannot reach the user device outside of the current coverage area of the auxiliary satellite.

[0114] At block 703, the first gateway satellite 505 and the second gateway satellite 510 may identify one or more auxiliary satellites, such as reference satellites. Figure 6 Block 603 is similarly described.

[0115] At block 705, the first user device 535 may generate a communication. In some cases, the communication may include a message (e.g., a voice or data message) for the second user device 540. As discussed above, the first user device 535 may not be able to communicate directly with the second user device 540—e.g., because the second user device 540 is outside of the communication range of the first user device 535.

[0116] At arrow 710, the first user device 535 may transmit the communication to the first auxiliary satellite 515 via the first TDL communication link 595, as shown in FIG. Figure 6 At block 715, the first auxiliary satellite 515 may identify the intended destination of the communication, as described with reference to FIG. Figure 6 At arrow 720, the first auxiliary satellite 515 may relay the communication to the first gateway satellite 505 via the first GW / TDL communication link 570, as described with reference to FIG. Figure 6 At block 725, the first gateway satellite 505 may determine the destination node for the communication, as described with reference to FIG. Figure 6 At arrow 730, the first gateway satellite 505 may relay the communication to the second gateway satellite 510 via the GW / GW communication link 590, as described in reference to FIG. Figure 6 At block 735, the second gateway satellite 510 may determine the destination node for the communication, as described with reference to arrow 630. Figure 6 At arrow 740, the second gateway satellite 510 may relay the communication to the second auxiliary satellite 520 via the second GW / TDL communication link 575, as described with reference to FIG. Figure 6 Arrow 640 is similarly described.

[0117] At arrow 745, the second auxiliary satellite 520 may relay the communication to the second user device 540 via the second TDL communication link 597. In some cases, the second auxiliary satellite 520 may relay the communication to the second user device 540 using the first TDL communication protocol used by the first user device 535. Thus, the first user device 535 may communicate with another user device that is located in a different coverage area than the first user device 535. In some cases, the second user device 540 may similarly transmit a message (e.g., a response) to the first user device 535.

[0118] Figure 8 Aspects of a process flow 800 for supporting and utilizing a decentralized satellite constellation as disclosed herein are shown. The process flow 800 may be referenced by Figure 5 The process flow 800 is described as being performed by a first gateway satellite 505, a second gateway satellite 510, a first auxiliary satellite 515, a third auxiliary satellite 525, a first user device 535, and a third user device 545. In some examples, the process flow 800 illustrates aspects of a process that enables a user device to perform extended range communications when an auxiliary satellite connected to the user device cannot reach the user device outside of the current coverage area of the auxiliary satellite.

[0119] At block 803, the first gateway satellite 505 and the second gateway satellite 510 may identify one or more auxiliary satellites, such as reference satellites. Figure 6 and Figure 7 Blocks 603 and 703 are similarly described.

[0120] At block 805, the first user device 535 may generate a communication. In some cases, the communication may include a message (e.g., a voice or data message) for the third user device 545. As discussed above, the first user device 535 may not be able to communicate directly with the third user device 545—e.g., because the third user device 545 uses a different communication protocol than the first user device 535 and / or is outside the communication range of the first user device 535.

[0121] At arrow 810, the first user device 535 may transmit the communication to the first auxiliary satellite 515 via the first TDL communication link 595, as shown in FIG. Figure 6 and Figure 7 At block 815, the first auxiliary satellite 515 may identify the intended destination of the communication, as described with reference to FIG. Figure 6 and Figure 7 At arrow 820, the first auxiliary satellite 515 may relay the communication to the first gateway satellite 505 via the first GW / TDL communication link 570, as described with reference to FIG. Figure 6 and Figure 7 The arrow 620 and the arrow 720 are similarly described. At block 825, the first gateway satellite 505 may determine the destination node of the communication, as shown in FIG. Figure 6 and Figure 7 At arrow 830, the first gateway satellite 505 may relay the communication to the second gateway satellite 510 via the GW / GW communication link 590, as described with reference to FIG. Figure 6 and Figure 7 The arrow 630 and the arrow 730 are similarly described. At block 835, the second gateway satellite 510 may determine the destination node of the communication, as shown in FIG. Figure 6 and Figure 7 At arrow 840, the second gateway satellite 510 may relay the communication to the third auxiliary satellite 525 via the third GW / TDL communication link 580, as described with reference to FIG. Figure 6 and Figure 7 Arrow 640 and arrow 740 are similarly described.

[0122] At arrow 845, the third auxiliary satellite 525 may relay the communication to the third user device 545 via the third TDL communication link 599. In some cases, the third auxiliary satellite 525 relays the communication to the third user device 545 using a second TDL communication protocol that is different from the first TDL communication protocol used by the first user device 535. Thus, the first user device 535 may communicate with another user device that uses a different communication protocol and is located in a different coverage area than the first user device 535. In some cases, the third user device 545 may similarly transmit a message (e.g., a response) to the first user device 535.

[0123] Figure 9 900. Aspects of a satellite communication subsystem 900 supporting a decentralized satellite constellation as disclosed herein are shown. The satellite communication subsystem 900 may include a gateway satellite 905, which may be a reference satellite. Figures 1 to 8 An example of a gateway satellite is described. Gateway satellite 905 can be positioned in LEO.

[0124] The satellite communication subsystem 900 may include a first auxiliary satellite 910 and a second auxiliary satellite 915, which may be reference satellites. Figures 1 to 8 The first auxiliary satellite 910 and the second auxiliary satellite 915 can be orbitally coupled with the gateway satellite 905, as shown in FIG. Figure 1Thus, the gateway satellite 905, the first auxiliary satellite 910, and the second auxiliary satellite 915 may be arranged within a cluster 940 and may communicate with each other using a first GW / TDL communication link 950 and a second GW / TDL communication link 955, as described with reference to FIG. Figures 1 to 8 In some cases, the first auxiliary satellite 910 can be configured for a first TDL communication protocol, and the second auxiliary satellite 915 can be configured for a second TDL communication protocol. In some cases, the gateway satellite 905 can be configured to relay communications between the auxiliary satellite and another gateway satellite, as described with reference to FIG. Figures 2 to 8 Described generally.

[0125] The satellite communication subsystem 900 may include a first user device 925 and a second user device 930, which may be reference Figures 1 to 8 An example of a user device is described. A first user device 925 may be located outside of the geographic coverage area 945—although in some cases, the first user device 925 may be located within the geographic coverage area. A second user device 930 may be located within the geographic coverage area 945 of the cluster 940. The second user device 930 may communicate with the second auxiliary satellite 915 using a TDL communication link 960, as described with reference to FIG. Figures 1 to 8 In some cases, the first user device 925 can be configured for a network communication protocol, and the second user device 930 can be configured for a second TDL communication protocol. In some cases, the second user device 930 can communicate with secondary satellites within the cluster 940 and user devices within the geographic coverage area 945, as described with reference to FIG. Figures 2 to 4 The second user equipment 930 can also communicate with auxiliary satellites in different clusters and devices in different geographical coverage areas, as described in reference Figures 5 to 8 Similar description.

[0126] The satellite communication subsystem 900 may include a commercial satellite 920, which may be a satellite such as the one shown in FIG. Figure 1 Examples of commercial satellites described herein. In some cases, commercial satellite 920 may be located in GEO. Commercial satellite 920 may communicate with gateway satellite 905 using GW / CL communication link 965, as described in reference Figure 1 Commercial satellite 920 may communicate with commercial gateway 935 using commercial gateway communication link 970, as described in reference Figure 1 Described generally.

[0127] The satellite communication subsystem 900 may include a business gateway 935, which may be a commercial gateway such as the one described in the reference Figure 1 The business gateway 935 can use the network communication link 975 to communicate with the first user device 925, as shown in FIG. Figure 1Generally described. In some cases, the business gateway 935 communicates with the first user device 925 via an intermediary device, such as a network server.

[0128] As discussed above and herein, the secondary satellite may not be configured with a connection to a commercial information network. Therefore, the user device may not be able to access the commercial network via the secondary satellite.

[0129] To connect the auxiliary satellites (e.g., the first auxiliary satellite 910 and / or the second auxiliary satellite 915) to the commercial information network, a gateway satellite (e.g., the gateway satellite 905) may be orbitally coupled to the auxiliary satellite and may be configured to communicate with the commercial satellite (e.g., the commercial satellite 920). The gateway satellite may be configured to route communications between the auxiliary satellite and the commercial satellite, for example, using protocol conversion and waveform normalization techniques.

[0130] By orbitally coupling a gateway satellite and an auxiliary satellite configured to communicate with a commercial satellite, any user device (e.g., first user device 925) connected to the commercial information network may be able to access functionality of the auxiliary satellite that would otherwise be inaccessible to the user device—e.g., due to incompatible communication protocols and / or connection failures. Figure 10 and Figure 11 Exemplary communications utilizing a gateway satellite to provide additional functionality and connect otherwise incompatible user devices through a commercial information network are discussed in greater detail.

[0131] Figure 10 1000 for supporting and utilizing a decentralized satellite constellation as disclosed herein. Figure 9 10. The process flow 1000 is described as being performed by a gateway satellite 905, a first auxiliary satellite 910, a commercial satellite 920, a first user device 925, and a commercial gateway 935. In some examples, process flow 1000 illustrates aspects of a process that enables a user device to access functionality of an auxiliary satellite using a network communication protocol, wherein the auxiliary satellite may not be configured for the network communication protocol and the user device may be located within or outside communication range of the auxiliary satellite.

[0132] At block 1003, the gateway satellite 905 may identify one or more auxiliary satellites (including the first auxiliary satellite 910) that are in orbital coupling with the gateway satellite 905. In some cases, the gateway satellite 905 discovers the one or more auxiliary satellites based on broadcasting a discovery message and receiving a response message. In some examples, the discovery and response messages are transmitted according to a gateway communication protocol. After identifying the auxiliary satellite, the gateway satellite 905 may establish a connection with the auxiliary satellite.

[0133] At block 1005, the first user device 925 may generate a communication. In some cases, the communication may include a request for information associated with functionality provided by the first auxiliary satellite 910. As discussed above, the first user device 925 may be unable to communicate directly with the first auxiliary satellite 910—e.g., due to incompatible communication protocols and / or transmission failures.

[0134] At arrow 1010, first user device 925 may transmit the communication to business gateway 935 via network communication link 975, for example, using a network communication protocol. In some cases, first user device 925 transmits the communication to business gateway 935 via an intermediary business server that is configured to route communications from personal devices to business gateway 935. In other cases, first user device 925 may transmit the communication directly to business gateway 935. Transmitting the communication using the network communication protocol may include encrypting a request included in the communication, packaging the encrypted request into a data packet, and transmitting the data packet as a waveform according to the network communication protocol.

[0135] At arrow 1015, business gateway 935 may relay the communication to business satellite 920 via business gateway communication link 970. In some cases, transmitting the communication may include encapsulating a data packet within another data packet to communicate with the business satellite according to a business satellite communication protocol.

[0136] At block 1020, commercial satellite 920 may identify the intended destination of the communication. In some cases, determining the intended destination includes decoding a receiver address included in the communication. In some cases, commercial satellite 920 determines a communication path to the intended destination based on a routing table stored at commercial satellite 920. In some cases, the communication path includes one or more intermediate gateway satellites and / or auxiliary satellites.

[0137] At arrow 1025, commercial satellite 920 may relay the communication to gateway satellite 905 via GW / CL communication link 965 based on identifying the intended destination of the communication and / or the communication path. In some cases, commercial satellite 920 relays the communication to gateway satellite 905 after determining that the intended destination of the communication is a secondary satellite within cluster 940 or a user device within geographic coverage area 945. In some cases, commercial satellite 920 relays the communication to gateway satellite 905 using a commercial network communication protocol configured at commercial satellite 920. In some cases, commercial satellite 920 may relay the communication to all gateway satellites within communication range of the commercial satellite—e.g., if commercial satellite 920 has not determined the intended destination of the communication.

[0138] At block 1030, the gateway satellite 905 may determine a destination node for the communication. In some cases, determining the destination node includes decrypting the data in the communication and / or identifying a receiver address included in the communication. In some cases, the gateway satellite 905 may compare the decoded receiver address with a list of addresses of auxiliary satellites included in the cluster 940 and / or a list of addresses of active user devices currently within communication range (e.g., within the geographic coverage area 945) of the cluster 940. In some examples, the gateway satellite 905 may determine that the communication is intended for the first auxiliary satellite 910, for example, based on matching the decoded address with an address stored for the first auxiliary satellite 910. In some examples, the gateway satellite 905 may include a routing table indicating a communication path from the gateway satellite 905 to the intended auxiliary satellite or user device. In some cases, the communication path includes one or more intermediate satellites.

[0139] At arrow 1035, the gateway satellite 905 may relay the communication to the first auxiliary satellite 910 via the first GW / TDL communication link 950 based on determining that the first auxiliary satellite 910 is the intended destination of the communication and / or the routing table. In some cases, relaying the data extracted from the communication to the first auxiliary satellite 910 includes packaging, encrypting, and / or transmitting the communication according to the GW / TDL communication protocol. In other cases, the gateway satellite 905 relays the communication without extracting the data by encapsulating the request included in the communication in a data packet composed according to the GW / TDL communication protocol. In other cases, the gateway satellite 905 relays the communication without extracting the data by relaying the communication using a third TDL communication protocol used by the first auxiliary satellite 910. In some cases, the gateway satellite 905 may relay the communication to another gateway satellite based on the identified receiver address and the routing table (e.g., based on determining that the destination node is an auxiliary satellite in orbital coupling with another gateway satellite or a user device connected to an auxiliary satellite).

[0140] At arrow 1040, the first assisting satellite 910 may transmit a response to the request included in the communication to the gateway satellite 905 via the first GW / TDL communication link 950. In some cases, the response may include data acquired using functionality provided by the first assisting satellite 910. For example, the first assisting satellite 910 may be configured to acquire satellite imaging and may transmit a response including an image of a specific location based on decoding the request for an image of the specific location. The first assisting satellite 910 may transmit the response using the GW / TDL communication protocol or the third TDL communication protocol.

[0141] At block 1045, the gateway satellite 905 may determine a destination node for the response, as similarly described with reference to block 1030. In some cases, the gateway satellite 905 may determine that the commercial satellite 920 is the destination node.

[0142] At arrow 1050 , the gateway satellite 205 may relay the response received from the first auxiliary satellite 910 to the commercial satellite 920 via the GW / CL communication link 965 , for example, using a GW / CL or commercial communication protocol.

[0143] At block 1055 , the commercial satellite 920 may determine a destination node for the response, as similarly described with reference to block 1020 .

[0144] At arrow 1060 , commerce satellite 920 may relay the response to commerce gateway 935 via commerce gateway communication link 970 .

[0145] At arrow 1065, the business gateway 935 may relay the response to the first user device 925 via the network communication link 975. In some cases, the business gateway 935 may transmit the response directly to the first user device 925. In other cases, the business gateway 935 may transmit the response to a business server, which may relay the response to the first user device 925. Thus, the first user device 925 may access the functionality of the auxiliary satellite by connecting to the business network. Additionally, the first auxiliary satellite 910, although not configured to support communications on the business network, may also be integrated into the business network.

[0146] Figure 11 1 shows aspects of a process flow 1100 for supporting and utilizing a decentralized satellite constellation as disclosed herein. The process flow 1100 may be performed by a process flow as described in reference to Figure 9 11. The process flow 1100 is performed by the depicted gateway satellite 905, the second auxiliary satellite 915, the commercial satellite 920, the first user device 925, the second user device 930, and the commercial gateway 935. In some examples, process flow 1100 illustrates aspects of a process that enables a user device connected to a commercial network to perform communications (including extended range communications) with another user device that is not configured to support direct communications with the user device or communications over the commercial network.

[0147] At block 1103, the gateway satellite 905 may similarly identify one or more auxiliary satellites, such as those described in reference to FIG. Figure 10 Block 1003 is similarly described.

[0148] At block 1105, the first user device 925 may generate a communication. In some cases, the communication may include a message (e.g., a voice or data message) for the second user device 930. As discussed above, the first user device 925 may not be able to communicate directly with the second user device 930—e.g., because the second user device 930 uses a different communication protocol and / or is outside the communication range of the first user device 925.

[0149] At arrow 1110, the first user device 925 may transmit the communication to the business gateway 935 via the network communication link 975, as shown in FIG. Figure 10 At arrow 1115, the commercial gateway 935 may relay the communication to the commercial satellite via the commercial gateway communication link 970, as described with reference to Figure 10 At block 1120, the commercial satellite 920 may identify the intended destination of the communication, as described with reference to FIG. Figure 10 At arrow 1125, the commercial satellite 920 may relay the communication to the gateway satellite 905 via the GW / CL communication link 965, as described with reference to FIG. Figure 10 At block 1130, the gateway satellite 905 may determine the destination node for the communication, as described with reference to FIG. Figure 10 At arrow 1135, the gateway satellite 905 may relay the communication to the second auxiliary satellite 915 via the second GW / TDL communication link 955, as described in reference to FIG. Figure 10 Arrow 1035 is similarly described.

[0150] At arrow 1140, the second auxiliary satellite 915 can relay the communication to the second user device 930 via the TDL communication link 960, for example, using a second TDL communication protocol. Thus, the first user device 925 can communicate with another user device that is not configured for the commercial network by connecting to the commercial network. In some cases, the second user device 930 can similarly transmit a message (e.g., a response) to the first user device 925.

[0151] Figure 12 A block diagram of a satellite controller 1200 supporting a decentralized satellite constellation as disclosed herein is shown. The satellite controller 1200 may be configured to cause a satellite to perform one or more of the processes discussed herein. All or aspects of the satellite controller may be implemented in a gateway satellite or an auxiliary satellite. The satellite controller 1200 may include a processor 1210, a memory 1215, an actuator controller 1245, a satellite communication manager 1230, and a communication interface 1240. Each of these components may communicate with each other, directly or indirectly, via one or more buses, such as bus 1235.

[0152] Memory 1215 may include random access memory (RAM) and / or read-only memory (ROM). Memory 1215 may store an operating system (OS) 1220 (e.g., built on a Linux or Windows kernel). Memory 1215 may also store computer-readable, computer-executable code 1225 including instructions that, when executed, are configured to cause processor 1210 to perform the various functions described herein related to providing communication services based on different local antenna modes. Alternatively, code 1225 may not be directly executable by processor 1210, but may be configured to cause satellite controller 1205 (e.g., when compiled and executed) to perform one or more of the functions described herein.

[0153] The actuator controller 1245 can be configured to control one or more actuators of the satellite, the one or more actuators being used to change the position and / or orientation of the satellite or its communication antenna. The actuator controller 1245 can generate various control signals that are delivered to the one or more actuators in response to pre-programmed instructions (e.g., operating configuration, control algorithm, controller gain, offset, deadband, multiplier, etc.) and / or received signals.

[0154] The communication interface 1240 may be configured to support communications between multiple types of satellites using multiple communication protocols. The communication interface 1240 may be configured to transmit and receive signals 1250. In some cases, the communication interface 1240 may include one or more radio frequency (RF) chains for receiving communications from one or more satellites. In some examples, the communication interface is configured with a radio and gateway communication protocol for communicating between a gateway satellite and an auxiliary satellite. In some examples, the communication interface is configured with a radio and gateway communication protocol for communicating between a gateway satellite and a commercial satellite. In some examples, the communication interface is configured with a radio and gateway communication protocol for communicating between a gateway satellite and another gateway satellite. In some examples, the communication interface is configured with a radio and TDL communication protocol for communicating between an auxiliary satellite and a user device.

[0155] Satellite communication manager 1230 may be configured to relay and / or route communications between satellites. In some cases, satellite communication manager 1230 may be configured to determine a destination node for a communication. In some examples, satellite communication manager 1230 may be configured to relay the communication to a gateway satellite after determining that the communication is destined for another satellite. In some examples, satellite communication manager 1230 may be configured to route communications between auxiliary satellites. In some cases, routing the communication between auxiliary satellites may include relaying the communication to other gateway satellites.

[0156] The satellite controller 1200 (including the processor 1210, memory 1215, actuator controller 1245, satellite communication manager 1230, and / or communication interface 1240) may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The satellite controller 1200 may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors in conjunction with a DSP core, integrated memory, discrete memory, or any other such configuration.

[0157] Figure 13 A block diagram of an exemplary gateway satellite 1300 supporting a decentralized satellite constellation as disclosed herein is shown. Gateway satellite 1300 can be configured to route communications to, from, and between auxiliary satellites, other gateway satellites, or commercial communications satellites. Gateway satellite 1300 can include a processor 1310, a GW / TDL communications manager 1315, a GW / GW communications manager 1320, a GW / CL communications manager 1325, a cryptographic component 1330, and a protocol converter 1335. Gateway satellite 1300 can also include a first antenna 1340, a second antenna 1345, and a third antenna 1350.

[0158] Processor 1310 may be configured to process communications received from or intended for one or more satellites. In some cases, processor 1310 may include a red processor and a black processor. The red processor may be configured to perform cryptographic functions (such as authentication and protection). And the black processor may be configured to perform communication-specific functions (such as packetizing data and determining the destination node of the communication). In some cases, processor 1310 may be a reference processor. Figure 12 An example of processor 1210 is described.

[0159] The cryptographic component 1330 may be configured to perform cryptographic functions not performed by the RED processor (e.g., decryption, encryption, storage, and maintenance of cryptographic keys). The protocol converter 1335 may be configured to convert received communications from one communication protocol (e.g., a first TDL communication protocol used to transmit the communication) to another communication protocol (e.g., a second TDL communication protocol associated with a determined destination node for the communication). In some cases, the RED processor or the cryptographic component 1330 may be located in a trusted execution environment of the processor 1310. In some cases, the cryptographic component 1330 and the protocol converter 1335 may be included in a Figure 12 The satellite communication manager 1230 is configured to:

[0160] The GW / TDL communication manager 1315 can be configured to manage communications received from and transmitted to the secondary satellite (e.g., over a TDL cross-link). In some cases, the GW / TDL communication manager 1315 can be configured to support communications constructed in accordance with the GW / TDL communication protocol. Additionally or alternatively, the GW / TDL communication manager 1315 can be configured to support communications constructed in accordance with one or more TDL communication protocols. In some cases, the GW / TDL communication manager 1315 can use the first antenna 1340 to receive communications from and transmit communications to the secondary satellite.

[0161] The GW / GW communication manager 1320 can be configured to manage communications between gateway satellites (e.g., on GW / GW cross links). In some cases, the GW / GW communication manager 1320 can be configured to support communications constructed according to the GW / GW communication protocol. In some cases, the GW / GW communication manager 1320 can use a second antenna 1345 to receive communications from the gateway satellite. In some cases, the second antenna 1345 can be configured differently than the first antenna 1340. For example, the second antenna 1345 can be configured to receive on a different set of frequencies than the first antenna 1340.

[0162] The GW / CL communication manager 1325 can be configured to manage communications between the gateway satellite and the commercial satellite (e.g., over a GW / CL cross link). In some cases, the GW / CL communication manager 1325 can be configured to support communications constructed in accordance with the GW / CL communication protocol. Additionally or alternatively, the GW / CL communication manager 1325 can also be configured to support communications constructed in accordance with the CL communication protocol. In some cases, the GW / CL communication manager 1325 can use a third antenna 1350 to receive communications from the commercial satellite. In some cases, the third antenna 1350 can be configured differently than the first antenna 1340 and / or the second antenna 1345. For example, the third antenna 1360 can be configured to receive on a different set of frequencies than the first antenna 1340 and / or the second antenna 1345.

[0163] In some cases, the GW / TDL communication manager 1315, the GW / GW communication manager 1320, the GW / CL communication manager 1325, the first antenna 1340, the second antenna 1345, and the third antenna 1350 may be included in a communication interface such as Figure 12 communication interface 1240).

[0164] Figure 14A block diagram of an exemplary auxiliary satellite 1400 supporting a decentralized satellite constellation as disclosed herein is shown. The auxiliary satellite 1400 can be configured to provide functionality to user equipment and utilize the TDL communication protocol. The auxiliary satellite 1400 can include a processor 1410, a TDL communication manager 1415, a GW / TDL communication manager 1420, a cryptographic component 1425, a first antenna 1430, and a second antenna 1435.

[0165] Processor 1410 may be configured to process communications received from or intended for a user device. In some cases, processor 1410 may be a reference Figure 12 An example of processor 1210 is described.

[0166] The TDL communication manager 1415 may be configured to manage communications received from and transmitted to the user equipment (e.g., over a TDL communication link). In some cases, the TDL communication manager 1415 may be configured to support communications constructed in accordance with a TDL communication protocol. The TDL communication manager 1415 may provide received communications to the processor 1410. In some cases, the TDL communication manager 1415 may use the first antenna 1430 to receive communications from and transmit communications to the user equipment and / or the secondary satellite using the TDL communication protocol configured at the secondary satellite 1400.

[0167] The GW / TDL communication manager 1420 can be configured to manage communications received from and transmitted to the gateway satellite (e.g., over a GW / TDL cross-link). In some cases, the GW / TDL communication manager 1420 can be configured to support communications constructed in accordance with the GW / TDL communication protocol. Additionally or alternatively, the GW / TDL communication manager 1420 can be configured to support communications constructed in accordance with the TDL communication protocol configured at the secondary satellite 1400. In some cases, the GW / TDL communication manager 1420 can use a second antenna 1435 to receive communications from and transmit communications to the gateway satellite—e.g., using the gateway communication protocol or the TDL communication protocol configured at the secondary satellite 1400. In some cases, the second antenna 1435 is configured differently than the first antenna 1430—e.g., the second antenna 1435 can be configured to receive on a different set of frequencies than the first antenna 1430.

[0168] In some cases, the TDL communication manager 1415 and the GW / TDL communication manager 1420, the first antenna 1430, and the second antenna 1435 may be included in a communication interface such as Figure 12 communication interface 1240).

[0169] The cryptographic component 1425 may be configured to perform cryptographic functions (including decryption, encryption, authentication, and protection). In some cases, the cryptographic component 1425 may include Figure 12 The satellite communication manager 1230 is configured to:

[0170] Figure 15 FIG1 shows a flow chart illustrating a method 1500 for supporting a decentralized satellite constellation according to aspects of the present disclosure. The operations of the method 1500 may be implemented by a gateway satellite or components thereof as described herein. For example, the method 1500 may be implemented by a gateway satellite or components thereof as described herein. Figure 12 and Figure 13 The gateway satellite described herein may be used to perform the operations of method 1500. Additionally or alternatively, the gateway satellite may use dedicated hardware to perform aspects of the functionality described below.

[0171] At 1505, the gateway satellite may receive communications using a first communication protocol from a first auxiliary satellite that is orbitally coupled to the first gateway satellite and provides a first function. The operations of 1505 may be performed according to the methods described herein. In some examples, the communication protocol may be received by a first auxiliary satellite as described in reference to Figure 13 The GW / TDL communications manager is described to perform various aspects of the operation of 1505.

[0172] At 1510, the gateway satellite may select a destination node for routing the communication from among a plurality of destination nodes, the plurality of destination nodes including a second auxiliary satellite that is orbitally coupled to the first gateway satellite and provides a second function, a second gateway satellite having a second orbit, and a commercial communication satellite having a third orbit. The operation of 1510 may be performed according to the methods described herein. In some examples, the operation may be performed by a method such as that described in reference to Figure 13 The processor 1310 is described to perform various aspects of the operations of 1510 .

[0173] At 1515, the gateway satellite may transmit information associated with the communication to the destination node. The operations of 1515 may be performed according to the methods described herein. In some examples, the gateway satellite may be configured as described in reference to Figure 13 Aspects of the operations of 1515 may be performed by the described GW / TDL communication manager, GW / GW communication manager, and / or GW / CL communication manager.

[0174] Figure 16 FIG1 shows a flow chart illustrating a method 1600 for supporting a decentralized satellite constellation according to aspects of the present disclosure. The operations of the method 1600 may be implemented by an auxiliary satellite or components thereof as described herein. For example, the operations of the method 1600 may be implemented by an auxiliary satellite or components thereof as described herein. Figure 12 and Figure 14 The auxiliary satellite described herein may be used to perform the operations of method 1600. Additionally or alternatively, the auxiliary satellite may use dedicated hardware to perform aspects of the functionality described below.

[0175] At 1605, the auxiliary satellite may establish a connection with the gateway satellite using a first communication protocol, wherein the first auxiliary satellite is in orbital coupling with the gateway satellite. The operation of 1605 may be performed according to the methods described herein. In some examples, the operation may be performed by a method such as that described in reference to Figure 14 The GW / TDL communications manager is described to perform various aspects of the operation of 1605.

[0176] At 1610, the secondary satellite may receive the communication using the second communication protocol. The operations of 1610 may be performed according to the methods described herein. In some examples, the secondary satellite may receive the communication using the second communication protocol. Figure 14 The TDL communications manager is described to perform various aspects of the operation of 1610.

[0177] At 1615, the auxiliary satellite may determine that the communication is directed to a second auxiliary satellite or a device served by the second auxiliary satellite. The operation of 1615 may be performed according to the methods described herein. In some examples, the communication may be directed to a second auxiliary satellite or a device served by the second auxiliary satellite. Figure 14 Aspects of the processor used to perform the operations of 1615 are described.

[0178] At 1620, the auxiliary satellite may transmit data from the communication to a gateway satellite using the first communication protocol based at least in part on the determination, the gateway satellite being configured to route the communication directly to a second auxiliary satellite or indirectly to a second auxiliary satellite via a second gateway satellite having a second orbit. The operations of 1620 may be performed according to methods described herein. In some examples, the communication may be performed by a method as described in reference to Figure 14 The GW / TDL communications manager is described to perform various aspects of the operation of 1620.

[0179] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified, and that other implementations are possible. Furthermore, aspects from two or more of the described methods may be combined.

[0180] The detailed descriptions described above in conjunction with the accompanying drawings describe examples and do not merely represent examples that can be implemented or within the scope of the claims. When used in this specification, the term "example" means "used as an example, instance, or illustration" and not "preferred" or "better than other examples." The detailed description includes specific details to provide an understanding of the described technology. However, these technologies can be practiced without these specific details. In some cases, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0181] Information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0182] The various exemplary blocks and components described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, a microprocessor combined with a DSP core, or any other such configuration.

[0183] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored as instructions or code on or transmitted via a computer-readable medium. Other examples and embodiments are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or a combination of any of these. Features that implement the functions can also be physically located in a variety of locations, including in a distributed manner so that functional portions are implemented at different physical locations. As used herein, including in the claims, when used in relation to a list of two or more items, the term "and / or" means that any of the listed items can be used alone, or any combination of two or more of the listed items can be used. For example, if a composition is described as comprising components A, B, and / or C, the composition can comprise A alone; B alone; C alone; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B, and C. Additionally, as used herein (including in the claims), “or” used in a list of items (e.g., a list of items prefixed by a phrase such as “at least one of…” or “one or more of…”) indicates a disjunctive list so that, for example, a list “at least one of A, B, or C” means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

[0184] Computer-readable media includes both computer storage media and communication media, and the computer-readable media includes any medium that helps to transfer a computer program from one place to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example and not limitation, computer-readable media can include RAM, ROM, EEPROM, flash memory, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices or any other medium that can be used to carry or store the desired program code device in the form of instructions or data structures and can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Moreover, any connection is appropriately referred to as computer-readable media. For example, if coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology (such as infrared, radio and microwave) is used to transmit software from a website, server or other remote source, coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology (such as infrared, radio and microwave) are included in the definition of medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with a laser. Combinations of the above are also included within the scope of computer-readable media.

[0185] As used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an exemplary step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0186] The preceding description of the present disclosure is provided to enable one skilled in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A communication system, comprising: a first gateway satellite having a first orbit and providing intra-cluster communication links using a first communication protocol for a plurality of auxiliary satellites in orbital coupling with the first gateway satellite; a first auxiliary satellite of the plurality of auxiliary satellites, the first auxiliary satellite configured to communicate with the first gateway satellite using the first communication protocol, wherein the first auxiliary satellite includes a first payload type and processes information according to an associated first packetization scheme, a first cryptographic scheme, and a first encoding scheme; as well as a second auxiliary satellite from the plurality of auxiliary satellites, the second auxiliary satellite configured to communicate with the first gateway satellite using the first communication protocol, wherein the second auxiliary satellite includes a second payload type different from the first payload type and processes information according to an associated second packetization scheme, a second cryptographic scheme, and a second encoding scheme, wherein the first gateway satellite routes intra-cluster communications over the intra-cluster communication link between the first auxiliary satellite and the second auxiliary satellite using the first communication protocol, and wherein the first gateway satellite converts between at least one of the first packetization scheme, the first cryptographic scheme, or the first encoding scheme and a corresponding one of the second packetization scheme, the second cryptographic scheme, or the second encoding scheme to route communications for the first auxiliary satellite or the second auxiliary satellite.

2. The system according to claim 1, wherein the intra-cluster communication link is a first intra-cluster communication link, the system further comprising: a second gateway satellite having a second orbit and providing a second intra-cluster communication link using the first communication protocol to a different plurality of auxiliary satellites in orbital coupling with the second gateway satellite; wherein the first gateway satellite routes inter-cluster communications of the first auxiliary satellite or the second auxiliary satellite to the second gateway satellite, and wherein the second gateway satellite routes the inter-cluster communication to an auxiliary satellite of the different plurality of auxiliary satellites via the second intra-cluster communication link.

3. The system according to claim 2, further comprising: a third auxiliary satellite from the different plurality of auxiliary satellites, the third auxiliary satellite being orbitally configured to communicate with the second gateway satellite using the first communication protocol, wherein the third auxiliary satellite includes a third payload type, Wherein the first gateway satellite routes communications between the first auxiliary satellite and the third auxiliary satellite via the second gateway satellite.

4. The system of claim 1, wherein the first payload type provides a first communication service to an aerial device, a ground device, or both according to a second communication protocol.

5. The system of claim 4 , wherein the second payload type provides a second communication service for the airborne equipment, the ground equipment, or both according to a third communication protocol, and wherein the first gateway satellite routes the intra-cluster communication between the first auxiliary satellite and the second auxiliary satellite using the first communication protocol.

6. The system of claim 5, wherein: The second communication protocol is associated with a first frequency range; and The third communication protocol is associated with a second frequency range.

7. The system of claim 5, wherein: the second communication protocol is associated with the first packetization scheme, the first cryptographic scheme, and the first encoding scheme; and The third communication protocol is associated with the second packetization scheme, the second cryptographic scheme, and the second encoding scheme.

8. The system of claim 1 , wherein the second payload type is configured to collect information using a first sensor type, and wherein the second auxiliary satellite communicates the information with the first gateway satellite using the first communication protocol.

9. The system of claim 1, wherein the first gateway satellite routes communications between the first auxiliary satellite or the second auxiliary satellite and a commercial communications satellite having a third orbit.

10. The system of claim 1, wherein the first gateway satellite communicates with the first and second auxiliary satellites via omnidirectional antennas using the first communication protocol.

11. The system of claim 1 , wherein after the first gateway satellite is installed in the first orbit, at least one of the first auxiliary satellite or the second auxiliary satellite is orbitally coupled with the first gateway satellite.

12. A communication method performed at a first gateway satellite, the first gateway satellite having a first orbit and using a first communication protocol to provide intra-cluster communication links for a plurality of auxiliary satellites in orbital coupling with the first gateway satellite, the method comprising: receiving communications using the first communications protocol from a first auxiliary satellite of the plurality of auxiliary satellites including a first payload type, wherein the first auxiliary satellite processes information according to an associated first packetization scheme, a first cryptographic scheme, and a first encoding scheme; selecting a second auxiliary satellite of the plurality of auxiliary satellites including a second payload type to route the communication as a destination node of a plurality of destination nodes, the plurality of destination nodes including the plurality of auxiliary satellites and a second gateway satellite having a second orbit, wherein the second auxiliary satellite processes information according to the associated second packetization scheme, second cryptographic scheme, and second encoding scheme; as well as Transmitting information associated with the communication to the destination node, wherein transmitting the information comprises converting between at least one of the first packetization scheme, the first cryptographic scheme, or the first encoding scheme and a corresponding one of the second packetization scheme, the second cryptographic scheme, or the second encoding scheme.

13. The method according to claim 12, further comprising: determining, based at least in part on the receiving, that the communication includes a request to access the second payload type, Wherein selecting the destination node comprises selecting the second auxiliary satellite based at least in part on the determining.

14. The method according to claim 13, further comprising: In response to the transmitted information, a second communication associated with the second payload type is received from the second auxiliary satellite using the first communication protocol.

15. The method according to claim 12, further comprising: determining, based at least in part on the receiving, that the communication includes a request for a third payload type to access a third auxiliary satellite orbitally coupled to the second gateway satellite, Wherein selecting the destination node comprises selecting the second gateway satellite based at least in part on the determination.

16. The method according to claim 12, further comprising: determining, based at least in part on the receiving, that the communication is directed to a device provided communications service by the second auxiliary satellite, Wherein selecting the destination node comprises selecting the second auxiliary satellite based at least in part on the determining.

17. The method according to claim 12, further comprising: determining, based at least in part on the receiving, that the communication is directed to a device serviced by a third auxiliary satellite in orbital coupling with the second gateway satellite, Wherein selecting the destination node comprises selecting the second gateway satellite based at least in part on the determination.

18. The method of claim 12, wherein the first auxiliary satellite is configured for a second communication protocol and the second auxiliary satellite is configured for a third communication protocol.

19. The method according to claim 12, further comprising: receiving a second communication from the second gateway satellite using a second communication protocol; determining, based at least in part on the receiving, that the communication is directed to the second auxiliary satellite; as well as Based at least in part on the determination, the second auxiliary satellite is selected as a second destination node.

20. The method of claim 12, wherein the plurality of destination nodes comprises a commercial communications satellite having a third orbit, the method further comprising: receiving a second communication from the commercial communications satellite using a second communications protocol; determining, based at least in part on the receiving, that the communication is directed to the second auxiliary satellite; as well as Based at least in part on the determination, the second auxiliary satellite is selected as a second destination node.

21. The method according to claim 12, further comprising: A command is transmitted to the plurality of auxiliary satellites instructing the plurality of auxiliary satellites to modify orbital paths.

22. The method according to claim 12, further comprising: identifying, using the first communication protocol, a first set of auxiliary satellites in orbital coupling with the first gateway satellite, wherein the first set of auxiliary satellites includes the first auxiliary satellite and the second auxiliary satellite; as well as A second set of auxiliary satellites that become orbitally coupled to the first gateway satellite after the first set of auxiliary satellites are identified is discovered using the first communication protocol, wherein the second set of auxiliary satellites includes at least a third auxiliary satellite that includes a third payload type different from the first payload type and the second payload type.

23. The method of claim 12, wherein the communication comprises a data packet constructed according to a second communication protocol, the method further comprising: converting data from the data packet from the second communication protocol to a third communication protocol used by the second auxiliary satellite, Wherein selecting the destination node comprises selecting the second auxiliary satellite based at least in part on the transition.

24. A method performed at a first auxiliary satellite providing communication services, the method comprising: establishing a connection with a gateway satellite using a first communication protocol, wherein the first auxiliary satellite is orbitally coupled to the gateway satellite and processes information according to an associated first packetization scheme, a first cryptographic scheme, and a first encoding scheme; receiving a communication using a second communication protocol; determining that the communication is directed to a second auxiliary satellite in orbital coupling with the gateway satellite or a device served by the second auxiliary satellite, wherein the second auxiliary satellite processes information according to the associated second packetization scheme, second cryptographic scheme, and second encoding scheme; as well as Based at least in part on the determination, transmitting data from the communication to the gateway satellite using the first communication protocol, the gateway satellite being configured to route the data from the communication directly to the second auxiliary satellite and convert between at least one of the first packetization scheme, the first cryptographic scheme, or the first encoding scheme and a corresponding one of the second packetization scheme, the second cryptographic scheme, or the second encoding scheme to route the communication for the first auxiliary satellite.

25. The method according to claim 24, further comprising: At least a portion of the communication is decoded according to the first communication protocol, wherein the determination is based at least in part on the decoded portion of the communication.

26. The method according to claim 25, further comprising: A first address associated with the second auxiliary satellite is obtained based at least in part on the decoding, wherein the determining includes determining that the first address is different than a second address associated with the first auxiliary satellite.

27. A first gateway satellite having a first orbit and using a first communication protocol to provide intra-cluster communication links for a plurality of auxiliary satellites in orbital coupling with the first gateway satellite, the first gateway satellite comprising: processor; a memory coupled to the processor; as well as instructions stored in the memory and executable by the processor to cause the first gateway satellite to: receiving communications using the first communications protocol from a first auxiliary satellite of the plurality of auxiliary satellites including a first payload type, wherein the first auxiliary satellite processes information according to an associated first packetization scheme, a first cryptographic scheme, and a first encoding scheme; selecting a second auxiliary satellite of the plurality of auxiliary satellites including a second payload type to route the communication as a destination node of a plurality of destination nodes, the plurality of destination nodes including the plurality of auxiliary satellites and a second gateway satellite having a second orbit, wherein the second auxiliary satellite processes information according to the associated second packetization scheme, second cryptographic scheme, and second encoding scheme; and Transmitting information associated with the communication to the destination node, wherein transmitting the information comprises converting between at least one of the first packetization scheme, the first cryptographic scheme, or the first encoding scheme and a corresponding one of the second packetization scheme, the second cryptographic scheme, or the second encoding scheme.

28. The first gateway satellite of claim 27, wherein the instructions are further executable by the processor to cause the first gateway satellite to: A determination is made based at least in part on the receiving that the communication includes a request to access the second payload type.

29. The first gateway satellite of claim 27, wherein the processor is further executable to cause the first gateway satellite to: In response to the transmitted information, a second communication associated with the second payload type is received from the second auxiliary satellite using the first communication protocol.

30. The first gateway satellite of claim 27, wherein the processor is further executable to cause the first gateway satellite to: A determination is made based at least in part on the receiving that the communication includes a request for a third payload type to access a third auxiliary satellite orbitally coupled to the second gateway satellite.

31. The first gateway satellite of claim 27, wherein the processor is further executable to cause the first gateway satellite to: The communication is determined to be directed to a device provided with communication service by the second auxiliary satellite based at least in part on the receiving.

32. The first gateway satellite of claim 27, wherein the processor is further executable to cause the first gateway satellite to: The communication is determined to be directed to a device serviced by a third auxiliary satellite orbitally coupled to the second gateway satellite based at least in part on the receiving.

33. A first auxiliary satellite providing communication services, the first auxiliary satellite comprising: processor; a memory coupled to the processor; as well as instructions stored in the memory and executable by the processor to cause the first auxiliary satellite to: establishing a connection with a gateway satellite using a first communication protocol, wherein the first auxiliary satellite is orbitally coupled to the gateway satellite and processes information according to an associated first packetization scheme, a first cryptographic scheme, and a first encoding scheme; receiving a communication using a second communication protocol; determining that the communication is directed to a second auxiliary satellite in orbital coupling with the gateway satellite or a device served by the second auxiliary satellite, wherein the second auxiliary satellite processes information according to the associated second packetization scheme, second cryptographic scheme, and second encoding scheme; and Based at least in part on the determination, transmitting data from the communication to the gateway satellite using the first communication protocol, the gateway satellite being configured to route the data from the communication directly to the second auxiliary satellite and convert between at least one of the first packetization scheme, the first cryptographic scheme, or the first encoding scheme and a corresponding one of the second packetization scheme, the second cryptographic scheme, or the second encoding scheme to route the communication for the first auxiliary satellite.

34. The first auxiliary satellite of claim 33, wherein the processor is further executable to cause the first auxiliary satellite to: At least a portion of the communication is decoded according to the first communication protocol.

35. The first auxiliary satellite of claim 34, wherein the processor is further executable to cause the first auxiliary satellite to: A first address associated with the second auxiliary satellite is obtained based at least in part on the decoding.

36. The method of claim 24, further comprising: receiving a second communication using the second communication protocol; Determining that the communication is directed to a third auxiliary satellite orbitally coupled to a second gateway satellite having a second orbit or a second device provided with a second service by the third auxiliary satellite; as well as Based at least in part on the determination, data from the second communication is transmitted to the gateway satellite using the first communication protocol, the gateway satellite being configured to indirectly route the data from the second communication to the third auxiliary satellite via the second gateway satellite.

37. The first auxiliary satellite of claim 33, wherein the processor is further executable to cause the first auxiliary satellite to: receiving a second communication using the second communication protocol; determining that the communication is directed to a third auxiliary satellite orbitally coupled to a second gateway satellite having a second orbit or to a second device provided with a second service by the third auxiliary satellite; and Based at least in part on the determination, data from the second communication is transmitted to the gateway satellite using the first communication protocol, the gateway satellite being configured to indirectly route the data from the second communication to the second auxiliary satellite via the second gateway satellite.

38. The system of claim 1 , wherein converting between at least one of the first subpackaging scheme, the first cryptographic scheme, or the first encoding scheme and a corresponding one of the second subpackaging scheme, the second cryptographic scheme, or the second encoding scheme comprises: Converting between a second communication protocol used by the first auxiliary satellite and a third communication protocol used by the second auxiliary satellite, wherein routing the intra-cluster communication using the first communication protocol is based at least in part on the converting.

39. The method of claim 12, wherein converting between at least one of the first subpackaging scheme, the first cryptographic scheme, or the first encoding scheme and a corresponding one of the second subpackaging scheme, the second cryptographic scheme, or the second encoding scheme comprises: Converting between a second communication protocol used by the first auxiliary satellite and a third communication protocol used by the second auxiliary satellite.

40. The method of claim 24, wherein To convert between at least one of the first packetization scheme, the first cryptographic scheme, or the first encoding scheme and a corresponding one of the second packetization scheme, the second cryptographic scheme, or the second encoding scheme, the gateway satellite is configured to: Converting between the second communication protocol used by the first auxiliary satellite and a third communication protocol used by the second auxiliary satellite.

41. The first gateway satellite of claim 27, wherein: To convert between at least one of the first subpackaging scheme, the first cryptographic scheme, or the first encoding scheme and a corresponding one of the second subpackaging scheme, the second cryptographic scheme, or the second encoding scheme, the instructions are further executable by the processor to cause the first gateway satellite to: Converting between a second communication protocol used by the first auxiliary satellite and a third communication protocol used by the second auxiliary satellite.

42. The first auxiliary satellite according to claim 33, wherein: To convert between at least one of the first subpackaging scheme, the first cryptographic scheme, or the first encoding scheme and a corresponding one of the second subpackaging scheme, the second cryptographic scheme, or the second encoding scheme, the gateway satellite is further configured to: Converting between the second communication protocol used by the first auxiliary satellite and a third communication protocol used by the second auxiliary satellite.

Images