Patent ID: 12261761

DETAILED DESCRIPTION

FIG.1is a diagram of an illustrative communications system38. Communications system38(sometimes referred to herein as communications network38, network38, system38, satellite communications system38, or satellite communications network38) may include a ground-based (terrestrial) gateway system that includes one or more gateways14and one or more user equipment (UE) devices10. Gateways14and UE devices10may form a part of a terrestrial network34on Earth. Terrestrial network34may include terrestrial-based wireless communications equipment22and network portion18. Terrestrial-based wireless communications equipment22may include one or more wireless base stations (e.g., for implementing a cellular telephone network) and/or wireless access points (e.g., for implementing a wireless local area network).

Communications system38may also include a constellation32of one or more communications satellites12(sometimes referred to herein simply as satellites12). Constellation32may sometimes be referred to herein as satellite constellation32or space network32. Communications satellites12are located in space (e.g., in orbit above Earth). While communications system38may include any desired number of gateways14, any desired number of communications satellites12, and any desired number of UE devices10, only a single gateway14, a single communications satellite12, and a single UE device10are illustrated inFIG.1for the sake of clarity. Each gateway14in communications system38may be located at a different respective geographic location on Earth (e.g., across different regions, states, provinces, countries, continents, etc.).

Network portion18may be communicably coupled to terrestrial-based wireless communications equipment22and each of the gateways14in communications system38. Gateway (GW)14may include a satellite network ground station and may therefore sometimes also be referred to as ground station (GS)14or satellite network ground station14. Each gateway14may include one or more antennas (e.g., electronically and/or mechanically adjustable antennas), modems, transceivers, amplifiers, beam forming circuitry, control circuitry (e.g., one or more processors, storage circuitry, etc.) and other components that are used to convey communications data. The components of each gateway14may, for example, be disposed at a respective geographic location (e.g., within the same computer, server, data center, building, etc.). Gateways14may convey communications data between terrestrial network34and UE devices10via satellite constellation32.

Network portion18may include any desired number of network nodes, terminals, and/or end hosts that are communicably coupled together using communications paths that include wired and/or wireless links. The wired links may include cables (e.g., ethernet cables, optical fibers or other optical cables that convey signals using light, telephone cables, etc.). Network portion18may include one or more relay networks, mesh networks, local area networks (LANs), wireless local area networks (WLANs), ring networks (e.g., optical rings), cloud networks, virtual/logical networks, the Internet, combinations of these, and/or any other desired network nodes coupled together using any desired network topologies (e.g., on Earth). The network nodes, terminals, and/or end hosts may include network switches, network routers, optical add-drop multiplexers, other multiplexers, repeaters, modems, servers, network cards, wireless access points, wireless base stations, UE devices such as UE devices10, and/or any other desired network components. The network nodes in network portion18may include physical components such as electronic devices, servers, computers, user equipment, etc., and/or may include virtual components that are logically defined in software and that are distributed across (over) two or more underlying physical devices (e.g., in a cloud network configuration).

Network portion18may include one or more satellite network operations centers such as network operations center (NOC)16. NOC16may control the operation of gateways14in communicating with satellite constellation32. NOC16may also control the operation of the satellites12in satellite constellation32. For example, NOC16may convey control commands via gateways14that control positioning operations (e.g., orbit adjustments), sensing operations (e.g., thermal information gathered using one or more thermal sensors), and/or any other desired operations performed in space by satellites12. NOC16, gateways14, and satellite constellation32may be operated or managed by a corresponding satellite constellation operator.

Communications system38may also include a satellite communications (satcom) network service provider (e.g., a satcom network carrier or operator) for controlling wireless communications between UE devices10and terrestrial network34via satellite constellation32. The satcom network service provider may be a different entity than the satellite constellation operator that controls/operates NOC16, gateways14, and satellite constellation32or, if desired, may be the same entity as the satellite constellation operator. Terrestrial-based wireless communications equipment22in terrestrial network34may be operated by one or more terrestrial network carriers or service providers. The terrestrial network carriers or service providers may be different entities than the satcom network service provider or, if desired, may be the same entity as the satcom network service provider.

Gateway14may control the operations of satellite constellation32over corresponding radio-frequency communications links. Satellite constellation32may include any desired number of satellites (e.g., two satellites, four satellites, ten satellites, dozens of satellites, hundreds of satellites, thousands of satellites, etc.), one of which is shown inFIG.1. If desired, two or more of the satellites12in satellite constellation32may convey radio-frequency signals between each other using satellite-to-satellite (e.g., relay) links.

Satellites12may include low earth orbit (LEO) satellites at orbital altitudes of less than around 8,000 km (e.g., satellites in low earth orbits, inclined low earth orbits, low earth circular orbits, etc.), geosynchronous satellites at orbital altitudes of greater than around 30,000 km (e.g., satellite in geosynchronous orbits), medium earth orbit (MEO) satellites at orbital altitudes between around 8,000 km and 30,000 km (e.g., satellite in medium earth orbits), sun synchronous satellites (e.g., satellites in sun synchronous orbits), satellites in tundra orbits, satellites in Molniya orbits, satellites in polar orbits, and/or satellites in any other desired orbits around Earth. Communications system38may include satellites in any desired combination of orbits or orbit types.

Each satellite12may communicate with one or more UE devices10on Earth using one or more radio-frequency communications links (e.g., satellite-to-user equipment links). Satellites12may also communicate with gateways14on Earth using radio-frequency communications links (e.g., satellite-to-gateway links). Radio-frequency signals may be conveyed between UE devices10and satellites12and between satellites12and gateways14in IEEE bands such as the IEEE C band (4-8 GHz), S band (2-4 GHz), L band (1-2 GHz), X band (8-12 GHz), W band (75-110 GHz), V band (40-75 GHz), K band (18-27 GHz), Kaband (26.5-40 GHz), Kuband (12-18 GHz), and/or any other desired satellite communications bands. If desired, different bands may be used for the satellite-to-user equipment links than for the satellite-to-gateway links.

Communications may be performed between gateways14and UE devices10in a forward (FWD) link direction and/or in a reverse (REV or RWD) link direction. In the forward link direction (sometimes referred to simply as the forward link), wireless data is conveyed from gateways14to UE device(s)10via satellite constellation32. For example, a gateway14may transmit forward link data to one of the satellites12in satellite constellation32(e.g., using radio-frequency signals28). Satellite12may transmit (e.g., relay) the forward link data received from gateway14to UE device(s)10(e.g., using radio-frequency signals26). Radio-frequency signals28are conveyed in an uplink direction from gateway14to satellite12and may therefore sometimes be referred to herein as uplink (UL) signals28, forward link UL signals28, or forward link signals28. Radio-frequency signals26are conveyed in a downlink direction from satellite12to UE device(s)10and may therefore sometimes be referred to herein as downlink (DL) signals26, forward link DL signals26, or forward link signals26.

In the reverse link direction (sometimes referred to simply as the reverse link), wireless data is conveyed from UE device(s)10to gateways14via satellite constellation32. For example, one of the UE devices10may transmit reverse link data to satellite12using radio-frequency signals24and satellite12may transmit (e.g., relay) the reverse link data received from UE device10to a corresponding gateway14using radio-frequency signals30. Radio-frequency signals24are conveyed in an uplink direction from UE device10to satellite12and may therefore sometimes be referred to herein as uplink (UL) signals24, reverse link UL signals24, or reverse link signals24. Radio-frequency signals30are conveyed in a downlink direction from satellite12to gateway14and may therefore sometimes be referred to herein as downlink (DL) signals30, reverse link DL signals30, or reverse link signals30. Gateway14may forward wireless data between UE device(s)10and network portion18. Network portion18may forward the wireless data to any desired network nodes or terminals of terrestrial network34.

If desired, UE devices10may also convey radio-frequency signals with terrestrial-based wireless communications equipment22over terrestrial network wireless communication links36when available. UE devices10may sometimes be referred to herein as being “online” or “on-grid” when the UE devices are within range of terrestrial-based wireless communications equipment22and when terrestrial-based wireless communications equipment22provides access (e.g., communications resources) to network portion18for the UE devices. When the UE devices are online, the UE devices may communicate with other network nodes or terminals in network portion18via terrestrial network wireless communications links36. Conversely, UE devices10may sometimes be referred to herein as being “offline” or “off-grid” when the UE devices are out of range of terrestrial-based wireless communications equipment22or when terrestrial-based wireless communications equipment22does not provide access to network portion18for the UE devices (e.g., when terrestrial-based wireless communications equipment22is disabled due to a power outage, natural disaster, traffic surge, or emergency, when terrestrial-based wireless communications equipment22denies access to network portion18for the UE devices, when terrestrial-based wireless communications equipment22is overloaded with traffic, etc.). If desired, UE devices10may include separate antennas for handling communications over the satellite-to-user equipment link and one or more terrestrial network wireless communication links36or UE devices10may include a single antenna that handles both the satellite-to-user equipment link and the terrestrial network wireless communications links. The terrestrial network wireless communications links may be, for example, cellular telephone links (e.g., links maintained using a cellular telephone communications protocol such as a 4G Long Term Evolution (LTE) protocol, a 3G protocol, a 3GPP Fifth Generation (5G) New Radio (NR) protocol, etc.), wireless local area network links (e.g., Wi-Fi® and/or Bluetooth links), etc.

The wireless data conveyed in DL signals26may sometimes be referred to herein as DL data, forward link DL data, or forward link data. UL signals28may also convey the forward link data (e.g., forward link data that is routed by satellite12to UE device(s)10in DL signals26). The wireless data conveyed in UL signals24may sometimes be referred to herein as UL data, reverse link UL data, or reverse link data. The reverse link data may be generated by UE device(s)10. DL signals30may also convey the reverse link data. The forward link data may be generated by any desired network nodes or terminals of terrestrial network34. The forward link data and the reverse link data may include text data such as email messages, text messages, web browser data, an emergency or SOS message, a location message identifying the location of UE device(s)10, or other text-based data, audio data such as voice data (e.g., for a bi-directional satellite voice call) or other audio data (e.g., streaming satellite radio data), video data (e.g., for a bi-directional satellite video call or to stream video data transmitted by gateway14at UE device(s)10), cloud network synchronization data, data generated or used by software applications running on UE device(s)10, and/or any other desired data. UE devices10may only receive forward link data, may only transmit reverse link data, or may both transmit reverse link data and receive forward link data. Each satellite12may communicate with the UE devices10located within its coverage area (e.g., UE devices10located within cells on Earth that overlap the signal beam(s) producible by the satellite).

The satcom network service provider for communications system38may operate, control, and/or manage a satcom control network such as satcom network region20in network portion18. Satcom network region20(sometimes referred to herein as satcom controller20, satcom network20, or satcom service provider equipment20) may be implemented on one or more network nodes and/or terminals of network portion18(e.g., one or more servers or other end hosts). In some implementations, satcom network region20may be formed from a cloud computing network distributed over multiple underlying physical network nodes and/or terminals distributed across one or more geographic regions. Satcom network region20may therefore sometimes also be referred to herein as satcom cloud region20, satcom cloud network20, or satcom cloud network region20.

Satcom network region20may control and coordinate wireless communications between terminals of terrestrial network34and UE devices10via satellite constellation32. For example, gateways14may receive reverse link data from UE devices10via satellite constellation32and may route the reverse link data to satcom network region20. Satcom network region20may perform any desired processing operations on the reverse link data. For example, satcom network region20may identify destinations for the reverse link data and may forward the reverse link data to the identified destinations. Satcom network region20may also receive forward link data for transmission to UE devices10from one or more terminals (end hosts) of terrestrial network34(e.g., network portion18). Satcom network region20may process the forward link data to schedule the forward link data for transmission to UE devices10via satellite constellation32. Satcom network region20may schedule the forward link data for transmission to UE devices10by generating forward link traffic grants for each of the UE devices that are to receive forward link data. Satcom network region20may provide the forward link data and the forward link traffic grants to gateways14. Gateways14may transmit the forward link data to UE devices10via satellite constellation32according to the forward link traffic grants (e.g., according to a forward link communications schedule that implements the forward link traffic grants).

The network performance of communications system38in conveying wireless data between UE device(s)10and gateway(s)14may vary over time. This variation can be due to variations in the performance of one or more components on UE device(s)10, satellite constellation32, and/or gateway(s)14, as well as changes in the radio-frequency propagation conditions between UE device(s)10and satellite constellation32and/or between satellite constellation32and gateway(s)14(e.g., due to changes in weather or other radio-frequency obstacles). It can be particularly difficult to monitor network performance in communications system38given that satellite constellation32is located in space and is generally unreachable for physical repair or in-person diagnostics, satellites12and UE devices10frequently or constantly move relative to Earth and each other over time, satellite constellation32might be operated by a satellite constellation operator that is different from the satcom network service provider, and different users may have/operate UE devices10having different hardware capabilities or conditions.

It would therefore be desirable for the satcom network service provider to be able to reliably monitor the (wireless) performance of communications system38in conveying wireless data via satellite constellation32in real-time. This may, for example, allow the satcom network service provider to identify errors or problems in the conveyance of wireless data between gateway(s)14and UE device(s)10via satellite constellation32, to provide information identifying the errors or problems to an operator of gateway(s)14and/or NOC16, to perform adjustments to one or more components in communications system38to correct the errors or problems, and/or to ensure that NOC16or the satellite constellation operator is in compliance with any guarantee, contract, or agreement (e.g., a Service Level Agreement (SLA)) in place with the satcom network service provider regarding wireless communications capabilities that are to be provided to UE device(s)10via satellite constellation32.

Communications system38may therefore include one or more network performance monitoring devices40that monitor the performance of communications system38in conveying wireless data via satellite constellation32in real-time. Network performance monitoring device(s)40may be associated with (e.g., owned, operated, and/or controlled by) the satcom network service provider associated with satcom network region20. Network performance monitoring devices40may be distributed across different locations on Earth (e.g., in different regions, states, countries, cities, or areas that are to be provided with communications capacity by satellite constellation32).

Network performance monitoring device(s)40may help to monitor the network performance of satellite constellation32and/or gateway(s)14in conveying wireless data for UE device(s)10based on forward link signals and/or reverse link signals conveyed by satellite constellation32. Network performance monitoring device(s)40may, for example, receive the DL signals26transmitted to UE device(s)10by satellite constellation32(e.g., forward link data in DL signals26) and/or may transmit some of the UL signals24to satellite constellation32(e.g., reverse link data in UL signals24). Network performance monitoring device(s)40may transmit information about the received forward link data (which may include the received forward link data itself) and/or information about the transmitted reverse link data (which may include the transmitted reverse link data itself) to satcom network region20(e.g., via the terrestrial network). While conveying wireless data with UE device(s)10via satellite constellation32, gateway(s)14may also transmit information about reverse link data received in DL signals30(which may include the received reverse link data itself) to satcom network region20(e.g., via the terrestrial network).

Satcom network region20may process the information about the forward link data received by network performance monitoring device(s)40, the information about the reverse link data transmitted by network performance monitoring device(s)40, and/or the information about the reverse link data received by gateway(s)14to monitor (e.g., detect, sense, identify, characterize, and/or analyze) the performance of communications system38in conveying wireless data between gateway(s)14and UE device(s)10via satellite constellation32. This may include, for example, identifying (e.g., detecting) errors, problems, or other non-idealities in satellite constellation32and/or gateway(s)14that limit, deteriorate, or otherwise impact the performance of communications system38in conveying wireless data between gateway(s)14and UE device(s)10via satellite constellation32. This may, if desired, include identifying one or more points in communications system38that produced or are likely to have produced the identified errors, problems, or other non-idealities and/or may include transmitting information (e.g., reports) to NOC16and/or an operator of gateway(s)14identifying the errors, problems, or other non-idealities and/or the points in communications system38that produced or are likely to have produced the identified errors. This monitoring may also include, if desired, generating commands or control signals that instruct NOC16, gateway(s)14, and/or satellite constellation32to perform one or more adjustments in conveying wireless data with UE device(s)10.

UE device10may be a computing device such as a laptop computer, a desktop computer, a computer monitor containing an embedded computer, a tablet computer, a cellular telephone, a media player, or other handheld or portable electronic device, a smaller device such as a wristwatch device, a pendant device, a headphone or earpiece device, a device embedded in eyeglasses or other equipment worn on a user's head, or other wearable or miniature device, a television, a computer display that does not contain an embedded computer, a gaming device, a navigation device, an embedded system such as a system in which electronic equipment with a display is mounted in a kiosk or automobile, a wireless internet-connected voice-controlled speaker, a home entertainment device, a remote control device, a gaming controller, a peripheral user input device, a wireless base station or access point, equipment that implements the functionality of two or more of these devices, or other electronic equipment.

As shown inFIG.2, UE device10may include components located on or within an electronic device housing such as housing42. Housing42, which may sometimes be referred to as a case, may be formed of plastic, glass, ceramics, fiber composites, metal (e.g., stainless steel, aluminum, metal alloys, etc.), other suitable materials, or a combination of these materials. In some situations, parts or all of housing42may be formed from dielectric or other low-conductivity material (e.g., glass, ceramic, plastic, sapphire, etc.). In other situations, housing42or at least some of the structures that make up housing42may be formed from metal elements.

UE device10may include control circuitry44. Control circuitry44may include storage such as storage circuitry46. Storage circuitry46may include hard disk drive storage, nonvolatile memory (e.g., flash memory or other electrically-programmable-read-only memory configured to form a solid-state drive), volatile memory (e.g., static or dynamic random-access-memory), etc. Storage circuitry46may include storage that is integrated within UE device10and/or removable storage media.

Control circuitry44may include processing circuitry such as processing circuitry48. Processing circuitry48may be used to control the operation of UE device10. Processing circuitry48may include on one or more processors (e.g., microprocessors, microcontrollers, digital signal processors, host processors, baseband processor integrated circuits, application specific integrated circuits, central processing units (CPUs), graphics processing units (GPUs), etc.). Control circuitry44may be configured to perform operations in device10using hardware (e.g., dedicated hardware or circuitry), firmware, and/or software. Software code for performing operations on UE device10may be stored on storage circuitry46(e.g., storage circuitry46may include non-transitory (tangible) computer readable storage media that stores the software code). The software code may sometimes be referred to as program instructions, software, data, instructions, or code. Software code stored on storage circuitry46may be executed by processing circuitry48.

Control circuitry44may be used to run software on UE device10such as satellite navigation applications, internet browsing applications, voice-over-internet-protocol (VOIP) telephone call applications, email applications, media playback applications, operating system functions, etc. To support interactions with external equipment, control circuitry44may be used in implementing communications protocols. Communications protocols that may be implemented using control circuitry44include internet protocols, wireless local area network (WLAN) protocols (e.g., IEEE 802.11 protocols—sometimes referred to as Wi-Fi®), protocols for other short-range wireless communications links such as the Bluetooth® protocol or other wireless personal area network (WPAN) protocols, IEEE 802.11ad protocols (e.g., ultra-wideband protocols), cellular telephone protocols (e.g., 3G protocols, 4G (LTE) protocols, 5G protocols, etc.), antenna diversity protocols, satellite navigation system protocols (e.g., global positioning system (GPS) protocols, global navigation satellite system (GLONASS) protocols, etc.), antenna-based spatial ranging protocols (e.g., radio detection and ranging (RADAR) protocols or other desired range detection protocols for signals conveyed at millimeter and centimeter wave frequencies), satellite communications protocols, or any other desired communications protocols. Each communications protocol may be associated with a corresponding radio access technology (RAT) that specifies the physical connection methodology used in implementing the protocol.

UE device10may store satellite information associated with one or more of the satellites12in satellite constellation32on storage circuitry46. The satellite information may include a satellite almanac identifying the position (e.g., orbit information, elevation information, altitude information, inclination information, eccentricity information, orbital period information, trajectory information, right ascension information, declination information, ground track information, etc.) and/or the velocity of satellites12(e.g., relative to the surface of Earth). This information may include a two-line element (TLE), for example. The TLE may identify (include) information about the orbital motion of one or more of the satellites12in satellite constellation32(e.g., satellite epoch, first and/or second derivatives of motion, drag terms, etc.). The TLE may, for example, be used by control circuitry44as an input for calculating, predicting, or identifying the location of satellites12at a given point in time. The TLE may be in the format of a text file having two lines or columns that include the set of elements forming the TLE, for example.

UE device10may also include wireless circuitry to support wireless communications. The wireless circuitry may include one or more antennas54and one or more radios52. Each radio52may include circuitry that operates on signals at baseband frequencies (e.g., baseband processor circuitry), signal generator circuitry, modulation/demodulation circuitry (e.g., one or more modems), radio-frequency transceiver circuitry (e.g., radio-frequency transmitter circuitry, radio-frequency receiver circuitry, mixer circuitry for downconverting radio-frequency signals to baseband frequencies or intermediate frequencies between radio and baseband frequencies and/or for upconverting signals at baseband or intermediate frequencies to radio-frequencies, etc.), amplifier circuitry (e.g., one or more power amplifiers and/or one or more low-noise amplifiers (LNAs)), analog-to-digital converter (ADC) circuitry, digital-to-analog converter (DAC) circuitry, control paths, power supply paths, signal paths (e.g., radio-frequency transmission lines, intermediate frequency transmission lines, baseband signal lines, etc.), switching circuitry, filter circuitry, and/or any other circuitry for transmitting and/or receiving radio-frequency signals using antenna(s)54. The components of each radio52may be mounted onto a respective substrate or integrated into a respective integrated circuit, chip, package, or system-on-chip (SOC). If desired, the components of multiple radios52may share a single substrate, integrated circuit, chip, package, or SOC.

Antenna(s)54may be formed using any desired antenna structures. For example, antenna(s)54may include antennas with resonating elements that are formed from loop antenna structures, patch antenna structures, inverted-F antenna structures, slot antenna structures, planar inverted-F antenna structures, helical antenna structures, monopole antennas, dipoles, hybrids of these designs, etc. If desired, one or more antennas54may include antenna resonating elements formed from conductive portions of housing42(e.g., peripheral conductive housing structures extending around a periphery of a display on UE device10). Filter circuitry, switching circuitry, impedance matching circuitry, and/or other antenna tuning components may be adjusted to adjust the frequency response and wireless performance of antenna(s)54over time. If desired, multiple antennas54may be implemented as a phased array antenna (e.g., where each antenna forms a radiator or antenna element of the phased array antenna, which is sometimes also referred to as a phased antenna array). In these scenarios, the phased array antenna may convey radio-frequency signals within a signal beam. The phases and/or magnitudes of each radiator in the phased array antenna may be adjusted so the radio-frequency signals for each radiator constructively and destructively interfere to steer or orient the signal beam in a particular pointing direction (e.g., a direction of peak signal gain). The signal beam may be adjusted or steered over time.

Transceiver circuitry in radios52may convey radio-frequency signals using one or more antennas54(e.g., antenna(s)54may convey the radio-frequency signals for the transceiver circuitry). The term “convey radio-frequency signals” as used herein means the transmission and/or reception of the radio-frequency signals (e.g., for performing unidirectional and/or bidirectional wireless communications with external wireless communications equipment). Antenna(s)54may transmit the radio-frequency signals by radiating the radio-frequency signals into free space (or to free space through intervening device structures such as a dielectric cover layer). Antenna(s)54may additionally or alternatively receive the radio-frequency signals from free space (e.g., through intervening devices structures such as a dielectric cover layer). The transmission and reception of radio-frequency signals by antenna(s)54each involve the excitation or resonance of antenna currents on an antenna resonating element in the antenna by the radio-frequency signals within the frequency band(s) of operation of the antenna.

Each radio52may be coupled to one or more antennas54over one or more radio-frequency transmission lines. The radio-frequency transmission lines may include coaxial cables, microstrip transmission lines, stripline transmission lines, edge-coupled microstrip transmission lines, edge-coupled stripline transmission lines, transmission lines formed from combinations of transmission lines of these types, etc. The radio-frequency transmission lines may be integrated into rigid and/or flexible printed circuit boards if desired. One or more of the radio-frequency lines may be shared between radios52if desired. Radio-frequency front end (RFFE) modules may be interposed on one or more of the radio-frequency transmission lines. The radio-frequency front end modules may include substrates, integrated circuits, chips, or packages that are separate from radios52and may include filter circuitry, switching circuitry, amplifier circuitry, impedance matching circuitry, radio-frequency coupler circuitry, and/or any other desired radio-frequency circuitry for operating on the radio-frequency signals conveyed over the radio-frequency transmission lines.

Radios52may use antenna(s)54to transmit and/or receive radio-frequency signals within different frequency bands at radio frequencies (sometimes referred to herein as communications bands or simply as a “bands”). The frequency bands handled by radios52may include satellite communications bands (e.g., the C band, S band, L band, X band, W band, V band, K band, Kaband, Kuband, etc.), wireless local area network (WLAN) frequency bands (e.g., Wi-Fi® (IEEE 802.11) or other WLAN communications bands) such as a 2.4 GHz WLAN band (e.g., from 2400 to 2480 MHz), a 5 GHz WLAN band (e.g., from 5180 to 5825 MHz), a Wi-Fi® 6E band (e.g., from 5925-7125 MHz), and/or other Wi-Fi® bands (e.g., from 1875-5160 MHz), wireless personal area network (WPAN) frequency bands such as the 2.4 GHz Bluetooth® band or other WPAN communications bands, cellular telephone frequency bands (e.g., bands from about 600 MHz to about 5 GHz, 3G bands, 4G LTE bands, 5G New Radio Frequency Range 1 (FR1) bands below 10 GHz, 5G New Radio Frequency Range 2 (FR2) bands between 20 and 60 GHz, 6G bands, etc.), other centimeter or millimeter wave frequency bands between 10-300 GHz, near-field communications (NFC) frequency bands (e.g., at 13.56 MHz), satellite navigation frequency bands (e.g., a GPS band from 1565 to 1610 MHz, a Global Navigation Satellite System (GLONASS) band, a BeiDou Navigation Satellite System (BDS) band, etc.), ultra-wideband (UWB) frequency bands that operate under the IEEE 802.15.4 protocol and/or other ultra-wideband communications protocols, communications bands under the family of 3GPP wireless communications standards, communications bands under the IEEE 802.XX family of standards, and/or any other desired frequency bands of interest.

While control circuitry44is shown separately from radios52in the example ofFIG.2for the sake of clarity, radios52may include processing circuitry that forms a part of processing circuitry48and/or storage circuitry that forms a part of storage circuitry46of control circuitry44(e.g., portions of control circuitry44may be implemented on radios52). As an example, control circuitry44may include baseband circuitry or other control components that form a part of radios52. The baseband circuitry may, for example, access a communication protocol stack on control circuitry44(e.g., storage circuitry46) to: perform user plane functions at a PHY layer, MAC layer, RLC layer, PDCP layer, SDAP layer, and/or PDU layer, and/or to perform control plane functions at the PHY layer, MAC layer, RLC layer, PDCP layer, RRC, layer, and/or non-access stratum layer.

UE device10may include input-output devices50. Input-output devices50may be used to allow data to be supplied to UE device10and to allow data to be provided from UE device10to external devices. Input-output devices50may include user interface devices, data port devices, and other input-output components. For example, input-output devices50may include touch sensors, displays (e.g., touch-sensitive and/or force-sensitive displays), light-emitting components such as displays without touch sensor capabilities, buttons (mechanical, capacitive, optical, etc.), scrolling wheels, touch pads, key pads, keyboards, microphones, cameras, buttons, speakers, status indicators, audio jacks and other audio port components, digital data port devices, motion sensors (accelerometers, gyroscopes, and/or compasses that detect motion), capacitance sensors, proximity sensors, magnetic sensors, force sensors (e.g., force sensors coupled to a display to detect pressure applied to the display), temperature sensors, etc. In some configurations, keyboards, headphones, displays, pointing devices such as trackpads, mice, and joysticks, and other input-output devices may be coupled to device10using wired or wireless connections (e.g., some of input-output devices50may be peripherals that are coupled to a main processing unit or other portion of device10via a wired or wireless link). UE device10may be owned and/or operated by an end user.

FIG.3is a diagram of an illustrative satellite12in communications system38. As shown inFIG.3, satellite12may include satellite support components56. Support components56may include batteries, solar panels, sensors (e.g., accelerometers, gyroscopes, temperature sensors, light sensors, etc.), guidance systems, propulsion systems, and/or any other desired components associated with supporting satellite12in orbit above Earth.

Satellite12may include control circuitry58. Control circuitry58may be used in controlling the operations of satellite12. Control circuitry58may include processing circuitry such as processing circuitry48ofFIG.2and may include storage circuitry such as storage circuitry46ofFIG.2. Control circuitry58may also control support components56to adjust the trajectory or position of satellite12in space.

Satellite12may include antennas62and one or more radios60. Radios60may use antennas62to transmit DL signals26and DL signals30and to receive UL signals24and UL signals28ofFIG.1(e.g., in one or more satellite communications bands). Radios60may include transceivers, modems, integrated circuit chips, application specific integrated circuits, filters, switches, up-converter circuitry, down-converter circuitry, analog-to-digital converter circuitry, digital-to-analog converter circuitry, amplifier circuitry (e.g., multiport amplifiers), beam steering circuitry, etc.

Antennas62may include any desired antenna structures (e.g., patch antenna structures, dipole antenna structures, monopole antenna structures, waveguide antenna structures, Yagi antenna structures, inverted-F antenna structures, cavity-backed antenna structures, combinations of these, etc.). In one suitable arrangement, antennas62may include one or more phased array antennas. Each phased array antenna may include beam forming circuitry having a phase and magnitude controller coupled to each antenna element in the phased array antenna. The phase and magnitude controllers may provide a desired phase and magnitude to the radio-frequency signals conveyed over the corresponding antenna element. The phases and magnitudes of each antenna element may be adjusted so that the radio-frequency signals conveyed by each of the antenna elements constructively and destructively interfere to produce a radio-frequency signal beam (e.g., a spot beam) in a desired pointing direction (e.g., an angular direction towards Earth at which the radio-frequency signal beam exhibits peak gain). Radio-frequency lenses may also be used to help guide the radio-frequency signal beam in a desired pointing direction. Each radio-frequency signal beam also exhibits a corresponding beam width. This allows each radio-frequency signal beam to cover a corresponding cell on Earth (e.g., a region on Earth overlapping the radio-frequency signal beam such that the radio-frequency signal beam exhibits a power greater than a minimum threshold value within that region/cell). Satellite12may convey radio-frequency signals over multiple concurrently-active signal beams if desired. If desired, satellite12may offload some or all of its beam forming operations to gateway14.

If desired, radios60and antennas62may support communications using multiple polarizations. For example, radios60and antennas62may transmit and receive radio-frequency signals with a first polarization (e.g., a left-hand circular polarization (LHCP)) and may transmit and receive radio-frequency signals with a second polarization (e.g., a right-hand circular polarization (RHCP)). Antennas62may be able to produce a set of different signal beams at different beam pointing angles (e.g., where each beam overlaps a respective cell on Earth). The set of signal beams may include a first subset of signal beams that convey LHCP signals (e.g., LHCP signal beams) and a second subset of signal beams that convey RHCP signals (e.g., RHCP signal beams). The LHCP and RHCP signal beams may, for example, be produced using respective multiport power amplifiers (MPAs) on satellite12. Each MPA may include a number of solid state power amplifiers (SSPAs) (e.g., each MPA may include one SSPA for each signal beam producible using that MPA). This may allow LHCP and RHCP signal beams to be active simultaneously. For example, if radios60and antennas62can produce 16 different signal beams, the 16 signal beams may include a first MPA having 8 SSPAs for producing 8 LHCP signal beams and may include a second MPA having 8 SSPAs for producing 8 RHCP signal beams. This is merely illustrative and, in general, satellite12may produce any desired number of signal beams having any desired polarizations.

FIG.4is a diagram of an illustrative network performance monitoring device40in communications system38. Network performance monitoring device40may sometimes be referred to herein as network performance monitor40, network performance monitoring equipment40, monitor40, performance monitor40, network monitor40, network device40, electronic device40, network diagnostic device40, network monitoring device40, SLA compliance monitoring device40, monitoring device40, or simply as device40. Monitoring device40may include one or more electronic devices that are used in monitoring, tracking, assessing, identifying, and/or analyzing the performance (e.g., wireless or radio-frequency performance) of communications system38in conveying wireless data between UE device(s)10and gateway(s)14via satellite constellation32.

As shown inFIG.4, monitoring device40may be enclosed within a housing (enclosure)84. Housing84, which may sometimes be referred to as a case, may be formed of plastic, glass, ceramics, fiber composites, metal (e.g., stainless steel, aluminum, metal alloys, etc.), other suitable materials, or a combination of these materials. In some situations, part or all of housing84may be formed from dielectric or other low-conductivity material (e.g., glass, ceramic, plastic, sapphire, etc.). In other situations, housing84or at least some of the structures that make up housing84may be formed from metal elements.

Monitoring device40may include control circuitry such as control circuitry66. Control circuitry66may include storage such as storage circuitry70. Storage circuitry70may include hard disk drive storage, nonvolatile memory (e.g., flash memory or other electrically-programmable-read-only memory configured to form a solid-state drive), volatile memory (e.g., static or dynamic random-access-memory), etc. Storage circuitry70may include storage that is integrated within monitoring device40and/or removable storage media.

Control circuitry66may include processing circuitry such as processing circuitry68. Processing circuitry68may be used to control the operation of monitoring device40. Processing circuitry68may include one or more processors (e.g., microprocessors, microcontrollers, digital signal processors, host processors, baseband processor integrated circuits, application specific integrated circuits, central processing units (CPUs), graphics processing units (GPUs), etc.). Control circuitry66may be configured to perform operations in monitoring device40using hardware (e.g., dedicated hardware or circuitry), firmware, and/or software. Software code for performing operations on monitoring device40may be stored on storage circuitry70(e.g., storage circuitry70may include non-transitory (tangible) computer readable storage media that stores the software code). The software code may sometimes be referred to as program instructions, software, data, instructions, or code. Software code stored on storage circuitry70may be executed by processing circuitry68.

Monitoring device40may include one or more communications interfaces such as terrestrial network communications interface64. Terrestrial network communications interface64may allow monitoring device40to communicate with terrestrial network34(FIG.1) via one or more communications links82(e.g., terrestrial communications link to network portion18ofFIG.1). Communications links82may include wired link and/or wireless links. Terrestrial network communications interface64may include one or more radios, one or more antennas, one or more data ports (e.g., Ethernet ports), cabling (e.g., coaxial cabling, Ethernet cabling, etc.) and/or any other desired equipment for communicating with terrestrial network34(e.g., without passing information through satellite constellation32). If desired, terrestrial network communications interface64and/or control circuitry66may be integrated into a single device78within monitoring device40. Device78may be a standalone device such as a desktop computer, laptop computer, cellular telephone, server, or other portable electronic device. Device78may be enclosed within a housing that is disposed within housing84if desired.

Monitoring device40may also include a space network communications interface86for communicating with gateway(s)14via satellite constellation32. Space network communications interface86may include one or more radios. The radios may, if desired, include a software-defined radio such as software-defined radio (SDR)76. SDR76may be implemented within device78or external to device78(as shown in the example ofFIG.4). SDR76may be coupled to control circuitry66over control path75. Control path75may convey control signals and/or data between control circuitry66and SDR76. SDR76is a radio that performs one or more functions of a hardware radio (e.g., mixing functions, amplification functions, modulation functions, demodulation functions, detection functions, synthesizer functions, filtering functions, etc.) using software (e.g., as executed by one or more processors such as processing circuitry68or other processing circuitry within SDR76). SDR76may, for example, function similar to a modem that allows a computing device (e.g., device78) to create radio-frequency energy to absorb/decode received radio-frequency energy via antenna(s)80.

Space network communications interface86may also include radio-frequency hardware components such as radio-frequency circuitry74and one or more antennas80. SDR76may be coupled to antenna(s)80over one or more radio-frequency transmission line path72. Radio-frequency circuitry74may be disposed on radio-frequency transmission line path(s)72between SDR76and antenna(s)80. SDR76may include one or more analog-to-digital converter (ADC) and/or one or more digital-to-analog converter (DAC) coupled to radio-frequency transmission line path(s)72. Antenna(s)80may include any desired antennas (e.g., antennas such as antennas54ofFIG.2or antennas62ofFIG.3). Two or more antennas80may be antenna elements of one or more phased array antennas if desired.

Control circuitry66may transmit control signals to SDR76that control/adjust one or more of the operations of SDR76. The control signals may control SDR76to generate radio-frequency signals and to transmit the radio-frequency signals over radio-frequency transmission line path(s)72, radio-frequency circuitry74, and antenna(s)80. The control signals may control SDR76to generate wireless data such as reverse link data that is conveyed using the radio-frequency signals (e.g., that is modulated onto the radio-frequency signals). Antenna(s)80may transmit the radio-frequency signals to satellite constellation32in IEEE bands such as the IEEE C band (4-8 GHz), S band (2-4 GHz), L band (1-2 GHz), X band (8-12 GHz), W band (75-110 GHz), V band (40-75 GHz), K band (18-27 GHz), Kaband (26.5-40 GHz), Kuband (12-18 GHz), and/or any other desired satellite communications bands (e.g., as reverse link signals or uplink signals24as shown inFIG.1). Control circuitry66may also transmit the transmitted reverse link data and/or information about the transmitted reverse link data to satcom network region20via terrestrial network communications interface64and communication link(s)82.

The wireless data may include reverse link data such as one or more reverse link data packets. The reverse link data may convey messages to satcom network region20via satellite constellation32and gateway(s)14. The reverse link data may include a unique identifier associated with monitoring device40. The unique identifier may identify that the reverse link data was transmitted by a network performance monitoring device rather than a UE device10. If desired, the reverse link data may be encoded or encrypted based on (using) the unique identifier. Satcom network region20may have knowledge of the unique identifier (or a decryption key associated with the unique identifier). This may allow satcom network region20to identify that the reverse link data was transmitted by a network performance monitoring device rather than a UE device10and to decrypt the reverse link data. At the same time, this may shield other network nodes from decrypting the reverse link data or detecting that the reverse link data was transmitted by a network performance monitoring device (e.g., the reverse link data may be indistinguishable from reverse link data transmitted by a UE device10and/or may be unencryptable to network nodes other than (outside of) satcom network region20). The reverse link data may be transmitted by monitoring device40to allow satcom network region20to monitor the network performance of satellite constellation32and/or gateway(s)14.

Antenna(s)80may also receive forward link signals (e.g., DL signals26ofFIG.1) from satellite constellation32. Antenna(s)80may pass the received forward link signals to SDR76via radio-frequency transmission line(s)72and radio-frequency circuitry74. SDR76may demodulate the received signals to obtain (receive) wireless data from the received radio-frequency signals. The received wireless data may include forward link data. SDR76may pass the forward link data to control circuitry66for subsequent processing. Control circuitry66may transmit the received forward link data and/or information about the received forward link data to satcom network region20via terrestrial network communications interface64and communication link(s)82. Satcom network region20may process the forward link data or the information about the forward link data to monitor the network performance of satellite constellation32and/or gateway(s)14.

Multiple monitoring devices40may be distributed across different locations or regions on Earth (e.g., regions that are provided with satellite communications capacity and coverage by the satellites12in satellite constellation32). These regions may be regions where UE devices are expected to be present. This may allow monitoring devices40to transmit reverse link data and/or to receive forward link data similar to as would be handled by UE devices10in communicating with gateway(s)14via satellite constellation32. Whereas UE devices10transmit full-stack wireless data to and receive wireless data from end hosts of terrestrial network34via satellite constellation32and gateway(s)14(e.g., email data, internet browser data, streaming video data, streaming music data, messaging data, gaming data, cloud computing data, distributed processing data, etc.), monitoring devices40may, for example, transmit simplified data to and/or may receive data from gateway(s)14via satellite constellation32solely for the purpose of allowing satcom network region20to monitor the network performance of gateway(s)14and/or satellite constellation32. The network performance monitoring functions may be transparent to satellite constellation32, gateway(s)14, NOC16, and any other network nodes not associated with or a part of satcom network region20(e.g., the data conveyed by monitoring devices40via satellite constellation32may be indistinguishable to satellite constellation32, gateway(s)14, NOC16, and any other network nodes not associated with or a part of satcom network region20from data conveyed by UE devices10).

FIG.5is a diagram showing how information may be conveyed between monitoring device40, a given gateway14, and satcom network region20for use by satcom network region in monitoring the network performance of satellite constellation32and/or gateway(s)14. The signals conveyed by UE devices10(FIG.1) have been omitted fromFIG.5for the sake of clarity.

As shown inFIG.5, monitoring device40may transmit reverse link signals REVSIG to gateway14via one or more satellites12in satellite constellation32, as shown by arrow88. Reverse link signals REVSIG may include reverse link data (e.g., fully qualified packets/datagrams) generated by SDR76(FIG.4). Conversely, gateway14may transmit forward link signals FWDSIG to satellite constellation32, as shown by arrow90. Satellite constellation32may transmit or broadcast forward link signals FWDSIG within a corresponding signal beam that overlaps a geographic region on Earth (e.g., a spot beam on Earth). Any UE devices10that are within this region may receive forward link signals FWDSIG. Monitoring device40may also receive forward link signals FWDSIG when monitoring device40is within this region. Forward link signals FWDSIG may include broadcast data, reference signals, synchronization signals (e.g., timer signals transmitted at a broadcast interval), and/or forward link data to be received by one or more UE devices10.

Gateway14may receive reverse link signals from satellite constellation32. The received reverse link signals may include the reverse link signals REVSIG generated by monitoring device40. The received reverse link signals may also include reverse link signals generated by UE devices10. Gateway14may forward (received) reverse link signal information REVRXINFO to satcom network region20as shown by path96(e.g., via one or more communications links in terrestrial network34). Reverse link signal information REVRXINFO may include reverse link data from the reverse link signals received by gateway14. The reverse link data may include the reverse link data generated by monitoring device40and included in reverse link signals REVSIG and/or reverse link data generated by UE devices10and included in the other reverse link signals received at gateway14. Reverse link signal information REVRXINFO may also include information about the received reverse link signals.

Satcom network region20may process the reverse link signals received by gateway14and identified by (included in) reverse link signal information REVRXINFO (e.g., in accordance with communications services provided to UE devices10by the communications network service provider associated with satcom network region20). For example, satcom network region20may forward reverse link data generated by UE device(s)10to its intended destination(s) (e.g., server(s), UE device(s)10, or other end host(s) of terrestrial network34).

As shown inFIG.5, satcom network region20may transmit control signals (commands) CMD and may transmit controls signals CMD to monitoring device40, as shown by arrow98. Control signals CMD may control one or more operations of monitoring device40. As an example, control signals CMD may control monitoring device40to transmit particular reverse link data in reverse link signals REVSIG, may instruct monitoring device40when to transmit reverse link signals REVSIG, may instruct monitoring device40when not to transmit reverse link signals REVSIG, may transmit payload information for the reverse link data to be transmitted by monitoring device40, etc. Monitoring device40may generate (transmitted) reverse link signal information REVTXINFO that is associated with the reverse link signals REVSIG transmitted to gateway14. Reverse link signal information REVTXINFO may include the reverse link data included in reverse link signal REVSIG itself and/or information about the transmitted reverse link data and/or reverse link signals.

Monitoring device40may receive the forward link signals FWDSIG transmitted by gateway14via satellite constellation32. Monitoring device40may generate (received) forward link signal information FWDRXINFO in response to the received forward link signals FWDSIG. Forward link signal information FWDRXINFO may include the forward link data included in forward link signals FWDSIG and/or information about the received forward link signals FWDSIG and/or the forward link data. Monitoring device40may transmit forward link signal information FWDRXINFO to satcom network region20, as shown by arrow94, and may transmit reverse link signal information REVTXINFO to satcom network region20, as shown by arrow92(e.g., via communications link(s)82ofFIG.4and terrestrial network34without routing the information via satellite constellation32).

Satcom network region20may use the unique identifier associated with monitoring device40to identify reverse link data generated by monitoring device40in the reverse link signals received by gateway14(e.g., to distinguish the reverse link data generated by monitoring device40for monitoring network performance from reverse link data generated by UE devices10). Satcom network region20may process the reverse link data generated by monitoring device40and/or the information about the reverse link signals REVSIG received at gateway14as included in reverse link signal information REVRXINFO, the forward link signal information FWDRXINFO received from monitoring device40, and/or the reverse link signal information REVTXINFO received from monitoring device40to monitor (e.g., identify, assess, analyze, track, detect, sense, determine, etc.) the network performance of satellite constellation32and gateway(s)14in providing communications capacity to UE devices10.

As part of monitoring the network performance, satcom network region20may identify one or more errors, non-idealities, or other network performance issues associated in satellite constellation32and/or gateway(s)14that impact, limit, deteriorate, or otherwise affect the wireless communications provided to UE device(s)10(e.g., that introduce or produce unexpected, unpredicted, or otherwise non-nominal values or results in the signals or data conveyed along the corresponding communications path). Satcom network region20may also identify one or more sources or locations of the errors, non-idealities, or other network performance issues. If desired, satcom network region20may generate network error information ERRORINFO based on reverse link signal information REVRXINFO, forward link signal information FWDRXINFO, and/or the reverse link signal information REVTXINFO. Satcom cloud region20may transmit network error information ERRORINFO to gateway(s)14, an operator, administrator, or technician of gateway(s)14, satellite constellation32, an operator, administrator, or technician of satellite constellation32(e.g., NOC16or an operator of NOC16ofFIG.1), and/or any other desired entities or parties. Network error information ERRORINFO may include information identifying location(s) or likely location(s) of one or more errors, non-idealities, or problems in the communications path(s) between gateway(s)14and UE device(s)10via satellite constellation32. Network error information ERRORINFO may also include one or more adjustment commands that instruct gateway(s)14, NOC16, and/or satellite constellation32to alter how communications are performed (e.g., in a manner that alleviates or mitigates the identified errors, non-idealities, or other network performance issues).

FIG.6is a flow chart of illustrative operations that may be performed by communications system38to monitor the network performance of satellite constellation32and/or gateway(s)14in real-time using at least one monitoring device40. While a single monitoring device40is described herein as an example, similar operations may be performed across many monitoring devices40distributed across Earth (e.g., to fully assess the performance of all the gateways14and satellites12associated with NOC16).

At operation102, satcom network region20may predict properties (e.g., expected properties) of forward link signals FWDSIG and/or reverse link signals REVSIG that are to be transmitted between monitoring device40and gateway14via satellite constellation32at one or more predetermined times. The predetermined times may be given by a communications schedule generated by or known to satcom network region20. The predicted properties may include predicted wireless performance metric data such as predicted received power levels, signal-to-noise ratio values, sensitivity values, timing information, etc. Satcom cloud region20may predict the expected properties based on the known future location of monitoring device40, gateway14, and/or the satellites12in satellite constellation32at the one or more predetermined times. Satcom cloud region20may know the future location of satellites12based on satellite location information received from NOC16. The satellite information may include a satellite almanac identifying the position (e.g., orbit information, elevation information, altitude information, inclination information, eccentricity information, orbital period information, trajectory information, right ascension information, declination information, ground track information, etc.) and/or the velocity of each of the satellites12in satellite constellation32(e.g., relative to the surface of Earth). Operation102may, if desired, be performed concurrently with one or more of the other operations shown inFIG.6.

At operation104, monitoring device40and gateway14may convey forward link signals FWDSIG and/or reverse link signal REVSIG via satellite constellation32. Monitoring device40may receive forward link signals FWDSIG and/or gateway14may receive reverse link signals REVSIG (e.g., at the one or more predetermined times). These signals may be signals having the properties as predicted by satcom network region20while processing operation102.

Monitoring device40may transmit reverse link signal information REVTXINFO to satcom network region20via terrestrial network34. Reverse link signal information REVTXINFO may include information associated with the transmitted reverse link signals REVSIG. Reverse link signal information REVTXINFO may include, for example, the reverse link data (e.g., payload data) transmitted in reverse link signals REVSIG, information identifying one or more properties of the transmitted reverse link signals REVSIG (e.g., timing information identifying when the reverse link signals REVSIG were transmitted, frequency information, duty cycle information, position information, header information, etc.).

At operation106, monitoring device40may gather information associated with received forward link signals FWDSIG. The gathered information may include wireless performance metric data associated with the reception of forward link signals FWDSIG. The wireless performance metric data may include received power level values, sensitivity values, frequency information, noise values (e.g., noise floor values), signal-to-noise ratio (SNR) values, error rate values, signal quality values, other wireless performance metric values characterizing the received forward link signals. The gathered information may also include radio-frequency timing information such as timestamp(s) at which the forward link signals were received and/or transmitted, identification information from the forward link data in the forward link signals, information associated with the satellite(s)12in satellite constellation32that transmitted the received forward link signals, information associated with the gateway14that transmitted the received forward link signals, and/or any other desired information. Monitoring device40may generate forward link signal information FWDRXINFO. Forward link signal information FWDRXINFO may include the gathered information (e.g., the gathered wireless performance metric data) and/or forward link data from the received forward link signals. Monitoring device40may transmit forward link signal information FWDRXINFO to satcom network region20via terrestrial network34.

Similarly, gateway14may gather information associated with received reverse link signals REVSIG. The gathered information may include wireless performance metric data associated with the reception of reverse link signals REVSIG. The wireless performance metric data may include received power level values, sensitivity values, noise values (e.g., noise floor values), signal-to-noise ratio (SNR) values, frequency information, error rate values, signal quality values, other wireless performance metric values characterizing the received reverse link signals. The gathered information may also include radio-frequency timing information such as timestamp(s) at which the reverse link signals were received and/or transmitted, information associated with the satellite(s)12in satellite constellation32that transmitted the received reverse link signals, and/or any other desired information. Gateway14may generate reverse link signal information REVRXINFO. Reverse link signal information REVRXINFO may include the gathered information (e.g., the gathered wireless performance metric data) and/or reverse link data from the received reverse link signals. Gateway14may transmit reverse link signal information REVRXINFO to satcom network region20via terrestrial network34.

At operation108, satcom network region20may identify (e.g., detect, compute, calculate, determine, generate, sense, measure, etc.) one or more differences between the predicted properties of the signals conveyed between monitoring device40and gateway14via satellite constellation32and the signals as actually received at gateway14or monitoring device based on the reverse link signal information REVRXINFO transmitted by (received from) monitoring device40, the forward link signal information FWDRXINFO transmitted by (received from) monitoring device40, and/or the reverse link signal information REVRXINFO transmitted by (received from) gateway14. The differences may include differences between the predicted wireless performance metric data and the wireless performance metric data generated by gateway14and/or monitoring device40, differences between the predicted and actual times at which the signals are received by gateway14and/or monitoring device40, and/or any other desired differences between one or more predicted properties of the conveyed signals and the actual (measured) properties of conveyed signals.

The one or more differences need not be only between predicted properties and measured signals and, more generally, may be one or more differences or deviations from any expected, desired, or nominal performance of one or more nodes components of nodes along the communications path. This may include, for example, accounting of an intent to transmit from a system that is fed time slices (e.g., times when to send) by a scheduler on satcom network region where the system then feeds the MAC PHY at gateway14to act and PHY log events for acknowledgement at satcom network region20. Other examples of differences that may be identified by satcom network region20may include, for example, differences between actual and predicted gateways14, actual and predicted antennas, actual and predicted signal beams, failure of a datagram, excessive SNR, excessive noise, excessive power differences, excessive latency between monitoring device40and gateway14, excessive decoding or processing time, other timing errors, insufficient data rate, etc.

Satcom network region20may store the one or more identified differences and may compare the one or more identified differences to one or more predetermined thresholds (or to ranges of differences as defined or bound by one or more predetermined thresholds). If desired, satcom network region20may compare differences over a given time period, differences accumulated from many monitoring devices40and/or gateways14, and/or statistics associated with the differences as tracked over time to the one or more predetermined threshold values.

If the identified difference(s) do not exceed the predetermined threshold(s) (or fall within a range of acceptable difference values), processing may proceed to operation112via path110. This may be indicative of satellite constellation32and/or gateway(s)14operating nominally and with satisfactory levels of wireless performance in conveying wireless data with UE device(s)10. At operation112, satellite constellation12and gateway(s)14may continue to convey wireless data with UE device(s)10(e.g., without satcom network region20transmitting error information ERRORINFO).

If the identified difference(s) exceed the predetermined threshold(s) (or fall outside the range of acceptable difference values), processing may proceed from operation108to operation116via path114. This may be indicative of satellite constellation32and/or gateway(s)14operating with unsatisfactory, non-ideal, deteriorated, or limited levels of wireless performance in conveying wireless data with UE device(s)10.

At operation116, satcom network region20may take suitable action based on the identified difference(s) (e.g., by generating and transmitting error information ERRORINFO). For example, at operation118, satcom network region20may detect, identify, diagnose, and/or debug one or more errors, problems, or other non-idealities in satellite constellation32and/or gateway(s)14that limit, deteriorate, or otherwise impact the performance of communications system38in conveying wireless data between gateway(s)14and UE device(s)10via satellite constellation32. Error information ERRORINFO may include information identifying the errors, problems, or other non-idealities. If desired, at operation118, satcom network region20may identify one or more points in communications system38that produced or are likely to have produced the identified errors, problems, or other non-idealities based on the identified difference(s). How the received signals differ from the predicted signals may be indicative of where faults or errors occurred between gateway14and monitoring device40, for example. Error information ERRORINFO may include information identifying these one or more points in communications system38that produced or are likely to have produced the identified errors, problems, or other non-idealities.

In other words, satcom network region20may analyze, examine, or otherwise process the signals and/or data transmitted by monitoring device40and/or gateway14at each major component in the corresponding communications path to identify a point of failure (error) or likely failure. Error information ERRORINFO may, if desired, include information identifying this point or that can be used to identify this point. As an example, satcom network region20may predict that the system should transmit a signal at a power level P and may discover, through processing the operations ofFIG.6, that the scheduler failed to transmit, that an FPGA on monitoring device40or gateway14failed to encode the signal, that an antenna on gateway14failed to track, that servers or compute circuitry on gateway14never received a signal or were overloaded, etc. Through the comparison and processing as described herein, satcom network region20may detect not only the presence of an error or missed signal, but may detect where the signal was dropped along the communications path between the transmitting device and satcom network region20(e.g., anywhere from monitoring device40to satellite constellation32, to the antenna at gateway14, to a server or processor in gateway14, through the terrestrial network, and to communications circuitry or storage at or within satcom network region20itself, etc.).

If desired, at operation120, satcom cloud network20may generate commands or control signals that direct satellite constellation32, gateway14, and/or the operator(s) of satellite constellation32and/or gateway14to adjust one or more components on satellite constellation32and/or gateway14based on (e.g., in a manner that mitigates) the identified difference(s). Error information ERRORINFO may include these commands or control signals. Satcom network region20may transmit error information ERRORINFO to gateway14, NOC16, satellite constellation32, and/or an operator, technician, service provider, administrator, and/or any other entity associated with gateway14, NOC16, and/or satellite constellation32. The operator, technician, service provider, administrator, and/or any other entity associated with gateway14, NOC16, and/or satellite constellation32may, for example, use the information about the identified difference(s) in error information ERRORINFO (e.g., as generated at operation118) to diagnose, debug, correct, and/or repair any errors in satellite constellation32and/or gateway14that produced the identified difference(s) (e.g., to maximize the wireless performance and capacity provided to UE device(s)10, to ensure that the operator, technician, service provider, administrator, and/or any other entity is in compliance with an SLA with the service provider associated with satcom network region20, etc.). The commands or control signals may additionally or alternatively adjust other portions of the communications network such as a system data rate and/or a load of compute within gateway14.

FIG.7is a flow chart of illustrative operations that may be performed by monitoring device40to monitor the network performance of satellite constellation32and gateway14in conveying wireless data with UE device(s)10. The operations ofFIG.7may, for example, be performed while processing operations104-106ofFIG.6.

At operation130, monitoring device40(e.g., control circuitry66and/or SDR76ofFIG.4) may generate reverse link data. The reverse link data may include one or more reverse link signal packets. Each reverse link signal packet may include payload data and one or more headers. Monitoring device40may generate the reverse link signal packet using a unique identifier associated with monitoring device40(e.g., that uniquely identifies monitoring device as a monitoring device40instead of a UE device10and/or that uniquely identifies which monitoring device40generated the packet). Monitoring device40may include the unique identifier in a header or payload field of the reverse link signal packet or may, if desired, encode or encrypt some or all of the reverse link signal packet using (based on) the unique identifier. Satcom network region20may have knowledge of the unique identifier (or a corresponding key associated with the unique identifier). Other portions of communications system38may have no knowledge of the unique identifier.

At operation132, space network communications interface86on monitoring device40may transmit the generated reverse link data in reverse link signals REVSIG. Antenna(s)80may transmit reverse link signals REVSIG to one or more satellites12in satellite constellation32. Satellite constellation32may relay reverse link signals REVSIG to one or more gateways14on Earth. If desired, space network communications interface86may boost the transmit power of reverse link signals REVSIG (e.g., to a maximum transmit power level of monitoring device40) to stress test satellite constellation32and/or gateway(s)14. Boosting the power in this way may produce more signal noise at gateway(s)14, making it more difficult for gateway(s)14to detect and decode reverse link signals (e.g., reverse link data) in the electromagnetic energy received by the antennas on gateway(s)14. This may help monitoring device40and satcom network region20to periodically test the network performance of gateway(s)14for a potential future scenario in which the network is stressed by an unusually high load or an unusually high number of UE devices10(e.g., to simulate a disaster scenario in which terrestrial-based wireless communications equipment22is unavailable before such a scenario actually arises).

At operation134, monitoring device40may transmit reverse link signal information REVTXINFO to satcom cloud region20(e.g., using terrestrial network communications interface64and communications link(s)82ofFIG.4). Reverse link signal information REVTXINFO may include information about the transmitted reverse link signals REVSIG such as a copy of the reverse link data that was transmitted in reverse link signals REVSIG and/or information identifying one or more properties of the transmitted reverse link signals REVSIG (e.g., timing information identifying when the reverse link signals REVSIG were transmitted, frequency information, duty cycle information, position information, transmit power level information, header information, etc.). Operation134may be performed concurrently with operation132if desired.

Operations130-134are associated with the transmission of reverse link data at monitoring device40. Operations136-140are associated with the reception of forward link data at monitoring device40. Operations130-134may be omitted or operations136-140may be omitted if desired. Operations136-140may be performed prior to operations130-134or may be performed concurrently with one or more of operations130-134(e.g., may be interleaved using a time division duplexing scheme).

At operation136, space network communications interface86on monitoring device40may receive forward link signals FWDSIG from satellite constellation32. SDR76may decode/demodulate the forward link signals to recover forward link data from the forward link signals. SDR76may pass the forward link data to control circuitry66. If desired, control circuitry66and/or SDR76may adjust the received forward link signals or forward link data to help ensure that monitoring device40receives the forward link signals at a steady state over time. This may include, for example, adding or subtracting power to the received signal to ensure that the power level remains steady or constant over time. This may help monitoring device40to mitigate the effects of a variable ambient temperature (e.g., temperature changes in the geographic region where monitoring device40is located) on how monitoring device40receives forward link signals. If desired, the transmitted reverse link signals REV may be periodically measured by radio-frequency circuitry such as a radio-frequency power meter (e.g., at monitoring device40) and compared with thermal information against a transmit power (gain) threshold table, where subsequent processing is performed against the thermal table (e.g., in a test mode of a telemetry system). This may allow transmission to be normalized against thermal variance of a UE device10itself. Both compensated and non-compensated values may be saved to a central database. The forward link signals FWD may undergo similar but more checks to normalized ingested signal (e.g., against thermal drift). Satcom network region20may, for example, be able to distinguish or designate when the telemetry system is in test mode or non-test mode (e.g., to mask undesired data). If desired, multiple telemetry systems may be deployed in clusters to determine if behavior is “in family” as another part of validation.

At operation138, radio-frequency circuitry74and/or SDR76may gather (e.g., generate, measure, sense, detect, produce, calculate, compute, etc.) information about the received forward link signals FWDSIG. The gathered information may include wireless performance metric data associated with the reception of forward link signals FWDSIG. The wireless performance metric data may include received power level values, sensitivity values, frequency information, noise values (e.g., noise floor values), signal-to-noise ratio (SNR) values, error rate values, signal quality values, other wireless performance metric values characterizing the received forward link signals. The gathered information may also include radio-frequency timing information such as timestamp(s) at which the forward link signals were received and/or transmitted, identification information from the forward link data in the forward link signals, information associated with the satellite(s)12in satellite constellation32that transmitted the received forward link signals, information associated with the gateway14that transmitted the received forward link signals, and/or any other desired information. Operation138may be performed concurrently with operation136if desired.

At operation140, monitoring device40may transmit forward link signal information FWDRXINFO to satcom cloud region20(e.g., using terrestrial network communications interface64and communications link(s)82ofFIG.4). Forward link signal information FWDRXINFO may include a copy of the forward link data that was received in forward link signals FWDSIG (e.g., one or more forward link signal packets) and/or the gathered information about the received forward link signals FWDSIG (e.g., as gathered while processing operation138). Operation134may be performed concurrently with operation132if desired.

FIG.8is a flow chart of illustrative operations that may be performed by gateway14while monitoring device40and satcom network region20are monitoring the network performance of satellite constellation32and gateway14in conveying wireless data with UE device(s)10. Operations150-156ofFIG.8may, for example, be performed while processing operations104-106ofFIG.6.

At operation150, gateway14may transmit forward link signals FWDSIG to UE device(s)10via satellite constellation32(e.g., based on a forward link grant scheduled for gateway14by satcom network region20). Forward link signals FWDSIG may include forward link data (e.g., destined for one or more UE devices10), broadcast signals, timing signals, synchronization signals, etc. Forward link signals FWDSIG may be received by monitoring device40when monitoring device40is in a region that receives forward link signals FWDSIG from one of the satellites12in satellite constellation32.

At operation152, gateway14may receive, via satellite constellation32, the reverse link signals REVSIG transmitted by monitoring device40. Gateway14may extract, demodulate, or decode the reverse link data (e.g., reverse link signal packets) in the received reverse link signals REVSIG. The reverse link data may appear to gateway14as indistinguishable from reverse link data transmitted by UE devices10.

At operation154, gateway14may gather information associated with received reverse link signals REVSIG. The gathered information may include wireless performance metric data associated with the reception of reverse link signals REVSIG. The wireless performance metric data may include received power level values, sensitivity values, noise values (e.g., noise floor values), signal-to-noise ratio (SNR) values, frequency information, error rate values, signal quality values, other wireless performance metric values characterizing the received reverse link signals. The gathered information may also include radio-frequency timing information such as timestamp(s) at which the reverse link signals were received and/or transmitted, information associated with the satellite(s)12in satellite constellation32that transmitted the received reverse link signals, and/or any other desired information. Operation154may be performed concurrently with operation152if desired.

At operation156, gateway14may transmit reverse link signal information REVRXINFO to satcom cloud region20(e.g., via a terrestrial network link). Reverse link signal information REVRXINFO may include a copy of the reverse link data that was received in reverse link signals REVSIG (e.g., one or more reverse link signal packets) and/or the gathered information about the received reverse link signals REVSIG (e.g., as gathered while processing operation154). Gateway14may also receive other reverse link signals from satellite constellation32that were transmitted by UE device(s)10. Gateway14may extract reverse link data from these reverse link signals and may include the reverse link data an information about the reverse link data in reverse link signal information REVRXINFO. Satcom network region20may forward the reverse link data generated by UE device(s)10and included in reverse link signal information REVRXINFO to corresponding destination end host(s) in the terrestrial network.

At operation158, gateway14may receive error information ERRORINFO from satcom network region20(e.g., via the terrestrial network). Operation158may, for example, be performed while processing operation116ofFIG.6. Error information ERRORINFO may include information identifying the errors, problems, or other non-idealities in the conveyance of wireless data with UE device(s)10using satellite constellation32and/or gateway14(e.g., as identified by satcom cloud region20based on reverse link signal information REVTXINFO, reverse link signal information REVRXINFO, and/or forward link signal information FWDRXINFO). Error information ERRORINFO may, for example, identify one or more points in gateway14and/or satellite constellation32that produced the identified errors, problems, or other non-idealities. This information may allow an operator, technician, administrator, or service provider associated with gateway14to debug, diagnose, repair, and/or adjust the operation of gateway14and/or satellite constellation32(e.g., in a way that mitigates the identified errors, problems, or other non-idealities).

Additionally or alternatively, error information ERRORINFO may include commands or control signals that adjust the operation of one or more components of gateway14and/or satellite constellation32. Gateway14may adjust the operation of one or more of its components (e.g., power supplies, antennas, amplifiers, transmitters, receivers, active signal beams, etc.) based on the received commands or control instructions. In examples where error information ERRORINFO includes commands or control signals that adjust the operation of satellite constellation32, gateway14may use uplink signals to transmit the commands or control signals to satellite constellation32. The commands or control signals may adjust the operation of one or more components on one or more satellites12in satellite constellation32(e.g., power supplies, antennas, amplifiers, transmitters, receivers, active signal beams, etc.). One or more of operations152-158may be performed prior to or concurrently with operation150.

Satcom network region20may use the reverse link signals transmitted by monitoring device40and/or the forward link signals received by monitoring device40to monitor the network performance of satellite constellation32and gateway14in providing communications services to UE device(s)10.FIG.9is a flow chart of illustrative operations that may be performed by satcom cloud region20to monitor the network performance of satellite constellation32and gateway14based on (using) reverse link signals transmitted by monitoring device40.

At operation160, satcom network region20may receive reverse link signal information REVTXINFO from monitoring device40. Satcom network region20may also receive reverse link signal information REVRXINFO from gateway14. Operation160may be performed while processing operation106ofFIG.6, for example.

At operation162, satcom network region20may route (forward) reverse link data in the reverse link signal information REVRXINFO that was transmitted by UE device(s)10to corresponding destination end host(s) in the terrestrial network. In this way, satcom network region20may provide communication services to UE device(s)10. Conversely, satcom network region20may receive wireless data from source end host(s) in the terrestrial network bound for destination UE device(s)10. Satcom network region20may convey this wireless data to UE device(s)10via terrestrial network34when terrestrial network wireless communication links36(FIG.1) are available to the UE device(s)10. When the UE device(s)10are unreachable via the terrestrial network (e.g., when terrestrial network wireless communication links36are unavailable), satcom network region20may transmit the wireless data to gateway(s)14, which transmit the wireless data as forward link data in forward link signals FWDSIG transmitted to the UE device(s)10via satellite constellation32.

When the reverse link signal information REVRXINFO received from gateway14includes reverse link data generated by monitoring device40, processing may proceed to operation164. This reverse link data may include, be encrypted/encoded with, and/or may otherwise be associated with the unique identifier associated with the monitoring device40that transmitted the reverse link data. At operation164, satcom network region20may identify the particular monitoring device40that transmitted the reverse link data (e.g., the monitoring device40that is associated with the unique identifier in the reverse link data).

At operation166, satcom network region20may compare reverse link signal information REVRXINFO to reverse link signal information REVTXINFO to identify (e.g., detect, measure, determine, compute, flag, generate, calculate, etc.) one or more differences between reverse link signal information REVRXINFO and reverse link signal information REVTXINFO (e.g., while processing operation108ofFIG.6). Satcom network region20may, for example, compare the reverse link data in reverse link signal information REVRXINFO that was transmitted by monitoring device40to the corresponding reverse link data in reverse link signal information REVTXINFO to identify the difference(s). Additionally or alternatively, satcom network20may compare the information about the transmitted reverse link signals in reverse link signal information REVTXINFO (e.g., wireless performance metric data or other information as generated while processing operation134ofFIG.7) to the information about the received reverse link signals in reverse link signal information REVRXINFO (e.g., wireless performance metric data or other information as generated while processing operation154ofFIG.7) to identify the difference(s).

If desired, satcom network20may store the identified difference(s) in storage (memory). Satcom network20may continue to store, accumulate, and/or track the identified differences generated over time and/or may generate statistical information about the identified differences (at operation168). Satcom network20may identify (e.g., calculate, compute, determine, measure, detect, generate, etc.) statistical trends in the differences over time. If desired, satcom network20may accumulate the differences associated with reverse link signals generated by multiple (e.g., each) monitoring device40in communications system38over time (e.g., may identify statistical trends across two or more monitoring devices40over time). Satcom network20may compare the identified difference(s) produced by reverse link signals REVSIG transmitted by monitoring device40over any desired time period (e.g., from one or more transmitted reverse link packets) and/or produced by reverse link signals transmitted by any additional monitoring devices40over any desired time period, and/or statistical information associated with these difference(s) to one or more threshold values (e.g., at operation108ofFIG.6). When the identified difference(s) and/or the statistical information exceeds one of the threshold values (or falls outside a predetermined range of difference values bound by two or more threshold values), processing may proceed to operation116ofFIG.6. Otherwise, processing may proceed to operation112ofFIG.6.

FIG.10is a flow chart of illustrative operations that may be performed by satcom cloud region20to monitor the network performance of satellite constellation32and gateway14based on (using) forward link signals received by monitoring device40.

At operation170, satcom network region20may receive forward link signal information FWDRXINFO from monitoring device40. Operation170may be performed while processing operation106ofFIG.6, for example.

At operation172, satcom network region20may identify the forward link data (e.g., forward link data packets) in forward link signal information FWDRXINFO. Satcom network region20may also identify information about the received forward link signals FWDSIG (e.g., signal properties) as generated by monitoring device40(e.g., while processing operation138ofFIG.7). If desired, satcom network region20may also identify information about the signal properties of forward link signals FWDSIG as transmitted by gateway14.

At operation174, satcom network region20may compare forward link signal information FWDRXINFO to one or more predicted (expected) properties of the corresponding forward link signals FWDSIG received at monitoring device40(e.g., as predicted while processing operation102ofFIG.6) to identify (e.g., detect, measure, determine, compute, flag, generate, calculate, etc.) one or more differences between forward link signal information FWDRXINFO and the predicted properties.

Satcom network region20may, for example, predict (e.g., while processing operation102ofFIG.6) wireless performance metric data or other information that should be gathered by monitoring device40in receiving forward link signals FWDSIG at one or more predetermined times (e.g., that should be or is expected to be gathered by monitoring device40while processing operation138ofFIG.7). Satcom network region20may then compare the predicted wireless performance metric data or other information to the wireless performance data or other information that was actually gathered by monitoring device40(e.g., while processing operation138ofFIG.7) to identify the difference(s).

If desired, satcom network20may store the identified difference(s) in storage (memory). Satcom network20may continue to store, accumulate, and/or track the identified differences generated over time and/or may generate statistical information about the identified differences (at operation176). Satcom network20may identify (e.g., calculate, compute, determine, measure, detect, generate, etc.) statistical trends in the differences over time. If desired, satcom network20may accumulate the differences associated with forward link signals received by multiple (e.g., each) monitoring device40in communications system38over time (e.g., may identify statistical trends across two or more monitoring devices40over time). Satcom network20may compare the identified difference(s) produced by the forward link signals FWDSIG received by monitoring device40over any desired time period (e.g., from one or more received forward link packets) and/or produced by forward link signals received by any additional monitoring devices40over any desired time period, and/or statistical information associated with these difference(s) to one or more threshold values (e.g., at operation108ofFIG.6). When the identified difference(s) and/or the statistical information exceeds one of the threshold values (or falls outside a predetermined range of difference values bound by two or more threshold values), processing may proceed to operation116ofFIG.6. Otherwise, processing may proceed to operation112ofFIG.6. The comparisons of operation176may act either immediately or over time depending on statistical trends in the measurements (e.g., allowing satcom network region20to respond near real time to issues or errors, or in response to trends over time).

FIG.11is a diagram showing examples of information that may be included in the forward link signal information FWDRXINFO. This information may be included in forward link signal information FWDRXINFO upon generation of forward link signal information FWDRXINFO by monitoring device40in response to receiving forward link signals FWDSIG and transmitted to satcom network region20(e.g., while processing operation140ofFIG.7). Satcom network region may identify this information while processing forward link signal information FWDRXINFO received from monitoring device40.

As shown inFIG.11, forward link signal information FWDRXINFO may include the forward (FWD) link data182. Forward link data182may include the forward link data (e.g., forward link data packets or payloads) from forward link signals FWDSIG (e.g., as transmitted by gateway14). Additionally or alternatively, forward link signal information FWDRXINFO may include timing information such as receive times184. Receive times184may identify the time(s) at which forward link signals FWDSIG were received at monitoring device40.

If desired, forward link signal information FWDRXINFO may include wireless performance metric data such as a receive (RX) power levels186, noise floor values188, and/or SNR values190. Receive power levels186may indicate the power levels with which monitoring device40received forward link signals FWDSIG. Noise floor values188may identify noise floor levels of the received forward link signals FWDSIG. SNR values190may identify signal-to-noise ratios of the received forward link signals FWDSIG. Received power levels186, noise floor values188, and SNR values190may be generated by sensor circuitry in radio-frequency circuitry74and/or may be generated by SDR76ofFIG.4, for example. Forward link signal information FWDRXINFO may include values of any desired wireless performance metrics as measured by monitoring device40and/or may include information identifying the frequency at which forward link signals FWDSIG were received. As other examples, forward link signal information FWDRXINFO may include latency to the receiving device by virtue of a slot transmitting device and/or the RF channel used for transmission.

Additionally or alternatively, forward link signal information FWDRXINFO may include gateway information192and/or satellite information194. Gateway information192may identify the gateway14that transmitted forward link signals FWDSIG. Gateway information192may also identify other parameters associated with the transmission of forward link signals FWDSIG by gateway14such as information identifying the transmit power level of forward link signals FWDSIG, a transmit duty cycle of forward link signals FWDSIG, a transmit frequency of forward link signals FWDSIG, information identifying which antenna(s) on gateway14transmitted forward link signals FWDSIG, information identifying which signal beam (e.g., a signal beam having a corresponding beam pointing direction) of the antenna(s) was used to transmit forward link signals FWDSIG, etc.

Satellite information194may identify the satellite(s)12in satellite constellation32that transmitted forward link signals FWDSIG to monitoring device40. Satellite information194may also identify other parameters associated with the transmission of forward link signals FWDSIG by satellite(s)12such as information identifying which antenna(s) on satellite(s)12transmitted forward link signals FWDSIG, information identifying which signal beam(s) of the antenna(s) were used to transmit forward link signals FWDSIG, information identifying the position (e.g., orbit information, elevation information, altitude information, inclination information, eccentricity information, orbital period information, trajectory information, right ascension information, declination information, ground track information, etc.) and/or the velocity of the satellite(s)12when the satellite(s)12transmitted forward link signals FWDSIG, etc.

Some or all of gateway information192and/or satellite information194may be appended to forward link signals FWDSIG upon transmission of the forward link signals by gateway14and/or satellite constellation32(e.g., in one or more header fields, a payload field, etc.) and/or upon receipt of the forward link signals by monitoring device40. Additionally or alternatively, some or all of gateway information192and/or satellite information194may be predetermined, known to, or deduced by satcom network region20based on the timing of the transmission and/or reception of forward link signals FWDSIG in conjunction with the communication schedule governing wireless communications using gateway14and satellite constellation32. The communication schedule may be generated by or otherwise known to satcom network region20itself.

As an example, satcom network region20may generate a communications schedule for use in providing communications services for UE device(s)10using satellite constellation32and gateway(s)14. The communications schedule assigns the radio-frequency resources of gateway(s)14and satellite constellation32(e.g., time resources, frequency resources, different antennas, different signal beams, etc.) to different UE device(s)10that are to provided with communications capacity via satellite constellation32. Satcom network region20may provide the communications schedule to gateway(s)14or may otherwise control wireless data transfer by gateway(s)14in based on the communications schedule. Gateway(s)14may transmit forward link signals, UE device(s)10may transmit reverse link signals, and satellite constellation32may route the forward and reverse link signals within different signal beams in accordance with the communications schedule generated by satcom network region20. Satcom network region20therefore has a priori knowledge of which gateway(s)14, which antennas and signal beams of gateway(s)14, which satellite(s)12, and/or which antennas and signal beams of satellite(s)12were used to transmit the forward link signals FWDSIG received by monitoring device40. The position of each of the monitoring devices40are also known to satcom network region20(e.g., because satcom network region20manages or operates monitoring devices40). Further, the position and/or velocity of each of the satellites12in satellite constellation32are known to satcom network region20and monitoring device40at all points in time (e.g., based on satellite information such as a satellite almanac received from NOC16). If desired, monitoring device40may generate satellite information194in forward link signal information FWDRXINFO identifying the position of the satellite(s)12that transmitted the received forward link signals FWDSIG based on the time(s) at which the forward link signals are received at monitoring device40(since monitoring device40has knowledge of the position and velocity of satellites12at all times).

Satcom network region20may use some or all of this information to predict one or more properties of the forward link signals FWDSIG that are to be received at monitoring device40at the time(s) when monitoring device40receives forward link signals FWDSIG. Satcom network region20may then compare some or all of this information as predicted to some or all of this information as generated by monitoring device40based on the forward link signals FWDSIG that were actually received at monitoring device40to identify differences between the predicted information and the actual information (e.g., while processing operation174ofFIG.1fexcessive differences between the predicted and actual information are present, this may be indicative of the presence of one or more errors, problems, or other non-idealities in satellite constellation32and/or gateway(s)14that limit, deteriorate, or otherwise impact the performance of communications system38in conveying wireless data between gateway(s)14and UE device(s)10via satellite constellation32.

Consider one example in which a first satellite12is scheduled to route forward link signals FWDSIG from a first gateway14to a geographic region that includes monitoring device at a first time (e.g., according to the communications schedule generated by or known to satcom network region20). Satcom network region20may have knowledge of the position, velocity, and power of the first satellite in the sky and relative to monitoring device40at the first time (e.g., from the satellite almanac and the known position of monitoring device40). Satcom network region20may predict (calculate) that for a satellite at the position and velocity of the first satellite, forward link signals transmitted by the first satellite at the scheduled first time will arrive at the known location of monitoring device40on Earth at a second time subsequent to the first time. Satcom network region20may additionally or alternatively predict (calculate), based on the known position, velocity, and power of the first satellite and monitoring device40, the power level, SNR, or other properties (characteristics or wireless performance metrics) of the forward link signals FWDSIG as received by monitoring device40at the second time. This calculation may, for example, account for free space loss between the position of the first satellite and monitoring device40, atmospheric loss between position of the first satellite and monitoring device40, the transmit power level of the first satellite, etc. Satcom network region may, for example, perform these predictions while processing operation102ofFIG.6.

The first satellite12may then actually transmit (route) the scheduled forward link signals FWDSIG to the geographic region that includes monitoring device40at the first time. Monitoring device40may receive forward link signals FWDSIG at a third time. The third time may be the same as the second time or may be different from the second time. Monitoring device40may generate (e.g., measure, identify, calculate, compute, sense, etc.) information about the received forward link signals FWDSIG such as the time at which the signals were received (e.g., the third time), the actual received power level, the actual SNR, or other properties (e.g., wireless performance metric data) associated with the received signals (e.g., at operation138ofFIG.7). Monitoring device40may include this information in forward link signal information FWDRXSIG and may transmit forward link signal information FWDRXSIG to satcom network region20(e.g., at operation140ofFIG.7). Satcom network region20may compare this information in forward link signal information FWDRXSIG to the predicted information (e.g., at operation174ofFIG.10and operation108ofFIG.6) to identify one or more differences between the properties of the forward link signals that monitoring device40was predicted to receive (e.g., at operation102ofFIG.6) and the properties of the forward link signals that monitoring device40actually received (e.g., at operation136ofFIG.7). Similar comparisons may be made between the transmitted and received reverse link signal information (e.g., REVTXINFO and REVRXINFO) to detect one or more errors, problems, or other non-idealities in satellite constellation32and/or gateway(s)14that limit, deteriorate, or otherwise impact the performance of communications system38in conveying wireless data between gateway(s)14and UE device(s)10via satellite constellation32(e.g., while processing operations164-168ofFIG.9). If the difference(s) exceed a threshold value (e.g., if the differences are excessively large), satcom network region20may generate and transmit error information ERRORINFO (e.g., at operation116ofFIG.6). If the difference(s) are less than the threshold value (e.g., if the differences are sufficiently small), satcom region20may forego transmission of error information ERRORINFO (e.g., at operation112ofFIG.6).

FIG.12is a diagram showing examples of information that may be included in the error information ERRORINFO that may be generated by satcom network region20(e.g., while processing operation116ofFIG.6). In general, error information ERRORINFO may include information identifying one or more errors, problems, or other non-idealities in satellite constellation32and/or gateway(s)14that limit, deteriorate, or otherwise impact the performance of communications system38in conveying wireless data between gateway(s)14and UE device(s)10via satellite constellation32. The information may include information identifying one or more points in and/or between monitoring device40, satellite constellation32, and gateway(s)14that generated, were likely to have generated, or are otherwise associated with the identified one or more errors, problems, or other non-idealities in satellite constellation32and/or gateway(s)14that limit, deteriorate, or otherwise impact the performance of communications system38in conveying wireless data between gateway(s)14and UE device(s)10via satellite constellation32.

For example, error information ERRORINFO may indicate or identify that a first antenna X1 on a first gateway14has lost Y % of its reverse link packets within a time period Z. As another example, error information ERRORINFO may indicate or identify that a second antenna X2 on a second gateway14has been down or inactive for a period of W minutes. As yet another example, error information ERRORINFO may indicate or identify that a third signal beam of a fifth satellite12has produced an excessive amount of signal loss (e.g., insufficient SNR at monitoring device40) over a period of T months in conveying forward link signals within its footprint on Earth. These are just examples of the types of information that may be conveyed in error information ERRORINFO. This information may, for example, be used by an operator, technician, administrator, or service provider of gateway(s)14, satellite constellation32, and/or NOC16to identify, diagnose, or debug errors, problems, or non-idealities in gateway(s)14and/or satellite constellation32that arise over time.

Satcom network region20may identify any desired errors, problems, or non-idealities in gateway(s)14and/or satellite constellation32in providing wireless communications capacity to UE device(s)10using monitoring device40. These errors, problems, or non-idealities may be explicitly identified or indicated in error information ERRORINFO or may be deduced by an operator, technician, administrator, or service provider of gateway(s)14, satellite constellation32, and/or NOC16based on error information ERRORINFO. These errors, problems, or non-idealities may include, as examples, antenna failures on gateway(s)14, antenna failures or unavailability on satellite(s)12, timing errors or errors where part of the software running on gateway(s)14does not send a scheduled message, power outages or undesirably low power levels at gateway(s)14, power errors on satellite(s)12(e.g., power failures, undesirably low power levels, undesirable power spikes, etc.), software on gateway(s)14being configured with an incorrect data rate, software stack protocol changes, signal power drops exceeding a predetermined margin (e.g., where all gateway(s)14in a given region suffer a signal power loss of X dB), a congested network state (e.g., when there is an excessively heavy load on satellite constellation32or an excessive number of UE devices10attempting to communicate via satellite constellation32), a UE device10on Earth that produces undesirable signal interference, excessive delays, errors associated with system saturation, errors in one or more components of the terrestrial network, errors in one or more components of satcom network20, errors associated with monitoring device40expecting to receive a signal or data and then not receiving the signal or data, an error where satcom network region20did not see a network node transmit data that was received, an error where a node transmitted data on the MAC layer but not on the PHY layer, an error where a node did not transmit data because there was no available antenna but there should have been one (e.g., across all gateways14), an error where data is lost in the air, etc.

More generally, as shown inFIG.12, error information ERRORINFO may include gateway identification information202. Gateway identification information202may include information identifying which gateway(s)14in communications system38transmitted the forward link signals FWDSIG and/or received the reverse link signals REVSIG associated with the identified difference(s) that exceeded the threshold value(s) (e.g., the gateway(s)14that produced or are statistically likely to have produced the identified errors, problems, or other non-idealities). If desired, error information ERRORINFO may also include gateway antenna identification information204. Gateway antenna identification information204may include information identifying which antenna(s) on the gateway(s)14identified by gateway identification information202transmitted the forward link signals FWDSIG and/or received the reverse link signals REVSIG associated with the identified difference(s) that exceeded the threshold value(s) (e.g., the particular antenna(s) on gateway(s)14that produced or are statistically likely to have produced the identified errors, problems, or other non-idealities). If desired, error information ERRORINFO may also include gateway beam identification information208. Gateway beam identification information208may include information identifying which signal beams(s) of the antenna(s) identified by gateway antenna identification information204transmitted the forward link signals FWDSIG and/or received the reverse link signals REVSIG associated with the identified difference(s) that exceeded the threshold value(s) (e.g., the particular signal beam(s) of the antenna(s) on gateway(s)14that produced or are statistically likely to have produced the identified errors, problems, or other non-idealities). The signal beams may be identified by corresponding beam indices (e.g., as stored on codebook(s) for gateway(s)14). Each signal beam corresponds to a respective set of phase and magnitude settings for the antennas that causes the antennas to transmit/receive radio-frequency signals in a corresponding beam pointing direction (e.g., a direction of peak signal gain).

Additionally or alternatively, error information ERRORINFO may include satellite identification information208. Satellite information208may include information identifying which satellite(s)12in satellite constellation12conveyed the forward link signals FWDSIG and/or the reverse link signals REVSIG associated with the identified difference(s) that exceeded the threshold value(s) (e.g., the satellites(s)12that produced or are statistically likely to have produced the identified errors, problems, or other non-idealities). If desired, error information ERRORINFO may also include satellite antenna identification information210. Satellite antenna identification information210may include information identifying which antenna(s)62(FIG.3) on the satellite(s)12identified by satellite identification information208conveyed the forward link signals FWDSIG and/or the reverse link signals REVSIG associated with the identified difference(s) that exceeded the threshold value(s) (e.g., the particular antenna(s)62on satellite(s)12that produced or are statistically likely to have produced the identified errors, problems, or other non-idealities). If desired, error information ERRORINFO may also include satellite beam identification information212. Satellite beam identification information212may include information identifying which signal beams(s) of the antenna(s) identified by satellite antenna identification information210conveyed the forward link signals FWDSIG and/or the reverse link signals REVSIG associated with the identified difference(s) that exceeded the threshold value(s) (e.g., the particular signal beam(s) of the antenna(s) on satellite(s)12that produced or are statistically likely to have produced the identified errors, problems, or other non-idealities). The signal beams may be identified by corresponding beam indices (e.g., as stored on codebook(s) for satellite(s)12).

Additionally or alternatively, error information ERRORINFO may include wireless performance metric data214. Wireless performance metric data214may include wireless performance metric data gathered by monitoring device40(e.g., as included in reverse link signal information REVTXINFO and/or forward link signal information FWDRXINFO) and/or gathered by gateway(s)14(e.g., as included in reverse link signal information REVRXINFO).

Additionally or alternatively, error information ERRORINFO may include statistical (trend) information216. Statistical information216may include or identify one or more trends in the wireless performance metric data gathered by monitoring device40and/or gateway14, the identified differences, and/or the identified errors, problems, or other non-idealities as gathered using forward link signals FWDSIG received by and/or reverse link signals REVSIG transmitted by one or more (e.g., all) monitoring devices40in communications system38over any desired time period (e.g., a single instance, a few seconds, a few minutes, a few hours, a few days, a few weeks, a few months, etc.).

Additionally or alternatively, error information ERRORINFO may include policy compliance information220. Policy compliance information220may identify one or more policies (e.g., SLAs) between the service provider associated with satcom network region20and the service provider associated with NOC16, satellite constellation32, and/or gateway(s)14. If desired, policy compliance information220may include information identifying if and how the wireless communications capacity provided to UE device(s)10via satellite constellation32and gateway(s)14does or does not comply with the one or more policies.

Additionally or alternatively, error information ERRORINFO may include one or more adjustment commands222. Adjustment commands222may instruct gateway(s)14, NOC16, and/or satellite constellation32to alter how communications are performed. If desired, adjustment commands222may instruct gateway(s)14, NOC16, and/or satellite constellation32on how to alter communications (e.g., in a manner that alleviates or mitigates the identified errors, non-idealities, or other network performance issues).

The example ofFIG.12is illustrative and non-limiting. Error information ERRORINFO may sometimes also be referred to herein as an error report, monitoring report, compliance report, network performance report, audit report, or error signal. One or more of elements202-222may be omitted from error information ERRORINFO if desired. Error information ERRORINFO may include any other desired information associated with the performance of satellite constellation32and gateway(s)14in conveying wireless data for UE device(s)10. Additional examples of such information that may be included in error information ERRORINFO includes information identifying a polarization of the forward or reverse link signals associated with the identified error (e.g., a left-hand or right-hand circular polarization), information identifying a particular server or software on the server associated with the identified error, information identifying a modem or modem link associated with the error, etc.

Satcom network region20may generate some or all of the information in error information ERRORINFO based on reverse link signal information REVTXINFO, reverse link signal information REVRXINFO, forward link signal information FWDRXINFO, the communications schedule generated by satcom network region20for UE device(s)10, satellite constellation32, and gateway(s)14, and/or the known positions and velocities of the satellites12in satellite constellation32(e.g., while processing operation116ofFIG.6). Satcom network region20may transmit error information ERRORINFO to gateway(s)14, NOC16, satellite constellation32, and/or an operator of, administrator of, technician of, or other entity associated with gateway(s)14, NOC16, and/or satellite constellation32.

Gateway(s)14, NOC16, satellite constellation32, and/or the operator, administrator, or technician of gateway(s)14, NOC16, and/or satellite constellation32may use some or all of the information in error information ERRORINFO to diagnose, debug, and/or repair the one or more errors, problems, or non-idealities identified by satcom network region20(e.g., to mitigate the identified difference(s) and to optimize the performance of gateway(s)14and satellite constellation32in conveying wireless data for UE device(s)10). For example, information202-212may pinpoint where in the communications chain between gateway14and monitoring device40there is an error, problem, or non-ideality that limits radio-frequency performance, wireless performance metric data214may identify the error or the severity of the error, statistical information216may identify how long the error has occurred (e.g., errors that occur for longer times may be more severe than errors that occur for shorter times), etc. Additionally or alternatively, adjustment commands222may provide instructions on how to adjust operations to mitigate the errors.

FIG.13is a diagram showing examples of adjustment commands222that may be included in error information ERRORINFO to help mitigate errors, problems, or other non-idealities in satellite constellation32and/or gateway(s)14that limit, deteriorate, or otherwise impact the performance of communications system38in conveying wireless data between gateway(s)14and UE device(s)10via satellite constellation32.

As shown inFIG.13, adjustment commands222(sometimes referred to herein as commands222, adjustments222, or control signals222) may include an adjustment (change)230to the transmit power level of gateway(s)14. Adjustment230may, for example, control gateway14(e.g., the gateway identified by gateway identification information202ofFIG.12) to adjust (e.g., increase) transmit power level to help boost the performance of UE device(s)10in receiving forward link signals.

Additionally or alternatively, adjustment commands222may include an adjustment (change)232to the receiver sensitivity of gateway(s)14. Adjustment232may, for example, control gateway14(e.g., the gateway identified by gateway identification information202ofFIG.12) to adjust (e.g., increase) its receiver sensitivity to help boost the performance of the gateway in receiving reverse link signals transmitted by UE device(s)10.

Additionally or alternatively, adjustment commands222may include an adjustment (change)234to the active antenna(s) of gateway(s)14. Adjustment234may, for example, control gateway14to disable a faulty antenna (e.g., an antenna that transmitted forward link signals FWDSIG or received reverse link signals REVSIG that produced excessive differences as identified by satcom network region at operation108ofFIG.6) and/or to switch a different or better-performing antenna into use.

Additionally or alternatively, adjustment commands222may include an adjustment (change)236to the active signal beam(s) of gateway(s)14. Adjustment236may, for example, control gateway14to disable a poorly-performing signal beam (e.g., a signal beam that transmitted forward link signals FWDSIG or received reverse link signals REVSIG that produced excessive differences as identified by satcom network region at operation108ofFIG.6) and/or to switch a different or better-performing signal beam into use.

Additionally or alternatively, adjustment commands222may include an adjustment (change)240to the active gateway(s)14. Adjustment240may, for example, disable a faulty or poorly-performing gateway14from continuing to route wireless data for UE device(s)10(e.g., a gateway14that transmitted forward link signals FWDSIG or received reverse link signals REVSIG that produced excessive differences as identified by satcom network region at operation108ofFIG.6). If desired, adjustment240may serve to switch a different or better-performing gateway14into use.

Additionally or alternatively, adjustment commands222may include an adjustment (change)238to the active signal beam(s) of satellite(s)12. Adjustment236may, for example, control gateway(s)14to instruct satellite(s)12to disable a poorly-performing signal beam (e.g., a signal beam that conveyed forward link signals FWDSIG or reverse link signals REVSIG that produced excessive differences as identified by satcom network region at operation108ofFIG.6) and/or to switch a different or better-performing signal beam into use.

Additionally or alternatively, adjustment commands222may include an adjustment (change)242to the active satellite(s)12. Adjustment242may, for example, control gateway(s)14to disable a poorly-performing satellite12from continuing to route wireless data for UE device(s)10(e.g., a satellite12that conveyed forward link signals FWDSIG or reverse link signals REVSIG that produced excessive differences as identified by satcom network region at operation108ofFIG.6) and/or to switch a different or better-performing satellite12into use.

If desired, adjustment commands222may include adjustments to the power level(s) of satellite(s)12. In some examples, adjustment commands222may include an assignment244of more communications resources to a selected geographic region. The selected geographic region may be a region having poor performance (e.g., as measured by a monitoring device40in that region). The selected region may, for example, be a region having an unexpected heavy traffic load. The unexpected heavy traffic load may, for example, occur when a relatively or unusually large number of UE devices10attempt to communicate via satellite constellation32rather than via the terrestrial network. The unexpected heavy traffic load may exceed the communications capacity currently being provided by satellite constellation32in the geographic area, may strain the resources of satellite constellation32, may create traffic bottlenecks via satellite constellation32, and/or may cause satellite constellation32to exhibit poor performance in conveying wireless data. This may occur, for example, when the geographic region is subjected to a power outage, government action, natural disaster, or other event that blocks or prevents UE devices10from being able to access network portion18via terrestrial-based wireless communications equipment22(FIG.1).

When such an unexpected heavy traffic load occurs, assignment244may allocate more space-based communications resources to the geographic region to help meet demand. This may include, for example, assigning more satellites12to serve the geographic region, assigning satellites12to direct more signal beams towards the geographic region, controlling the satellites12to increase dwell time in the geographic region, controlling the satellites12to boost power levels, changing which satellites12serve the geographic region (e.g., assigning satellites in different or additional types of orbits to serve the geographic region, assigning satellites with more resources or capacity to the geographic region, repositioning or orienting the satellites, etc.), increasing the transmit power level and/or receiver sensitivity of the gateway(s)14that serve the geographic region, changing the data rate with which satellites12serve the geographic region (e.g., reducing the data rate so the satellites transmit in shorter bursts that allow the satellite to serve a greater number of users), activating and using some or all standby antennas on gateway(s)14that serve the geographic region (e.g., to track additional satellites12covering the geographic area to boost reverse link message throughput), etc. The example ofFIG.13is merely illustrative. One or more of adjustments230-244may be omitted. In general, adjustment commands222may include any desired adjustments to gateway(s)14and/or satellite constellation32.

In general, monitoring device40does not act as a UE device10in communications system38(e.g., does not perform the same full stack end-to-end communications as a UE device) and is not operated by an end user (e.g., monitoring device40is instead operated by satcom network region20or an operator of satcom network region20). Monitoring device40may, for example, transmit UL signals at significantly higher power levels (gain) than a UE device10(e.g., for stress-testing the network, whereas a UE device need only communicate via the network). If desired, a UE device10may be configured to perform one or more (e.g., all) of the operations of monitoring device40as described herein (e.g., in addition to being operated by an end user and performing the full stack end-to-end communications of a UE device).

One or more elements described herein (e.g., UE devices10, network performance monitoring devices40, satcom network region20, etc.) may gather and/or use personally identifiable information. It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

The foregoing is merely illustrative and various modifications can be made to the described embodiments. The foregoing embodiments may be implemented individually or in any combination.