Patent Description:
Advances in telecommunications technologies are increasing the availability of voice, data, entertainment, infotainment services to consumers. These technological developments are enabling consumers to transmit and receive increasingly larger amounts of multimedia digital content, such as texts, streaming audio or video, social media or web content, digital entertainment, interactive gaming, or other digital content.

Satellite communication systems may be used to provision voice and data services to customers (end users). In order to serve more customers and provide higher and affordable quality service to multiple customers at remote locations, very-small-aperture terminals (VSATs) may be deployed in satellite communication systems. However, managing a higher volume of satellite communication components to ensure quality service is becoming more and more challenging.

<CIT> relates to a conference control station is arranged to transmit signals on a first allocated satellite communication channel, wherein a number of conference stations form a group. Each conference station of the group is arranged to transmit signals on one or more further communication channels allocated to the group with the number of further communication channels allocated to the group being small compared to the number of conference stations.

<CIT> relates to determining an outdoor electronic unit (ODU)-type based upon a signal analysis. A device identifies one or more properties of a signal received from an ODU, including a peak frequency of the signal. The device then compares the identified signal properties to one or more properties of one or more predetermined spectral configurations, each spectral configuration being associated with an ODU-type.

<CIT> relates to a devices that samples a converter signal (e.g., input to a block up converter or output from a low noise block) at a very small aperture terminal site and identifies, as between a site converter and a site modem, a more likely faulty component to aid site diagnosis and repair.

Features of the systems and methods are illustrated by way of example and not limited in the following Figure(s), in which like numerals indicate like elements, in which:.

For simplicity and illustrative purposes, the disclosed systems and methods is described by referring mainly to examples and embodiments thereof. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the disclosed systems and methods. It will be readily apparent, however, that the disclosed systems and methods may be practiced without limitation to these specific details. In other instances, some methods and structures readily understood by one of ordinary skill in the art have not been described in detail so as not to unnecessarily obscure the disclosed systems and methods. As used herein, the terms "a" and "an" are intended to denote at least one of a particular element, the term "includes" means includes but not limited to, the term "including" means including but not limited to, and the term "based on" means based at least in part on.

As described above, there are many challenges to ensure quality service for satellite communications systems that employ VSATs. A VSAT is a two-way satellite ground station that may be in form of a satellite dish including an outdoor unit (ODU), and an indoor unit (IDU). The ODU may include a reflector, a feed horn that both transmits and receives signals back from the reflector, a block-up converter (BUC) that may be used for transmission, and a low noise block converter (LNB) that may be used to receive signals. VSATs may require a reference frequency to operate the BUCs and LNBs, which may be provided by the IDU of the corresponding VSATs, The IDU may include a network device that is any of a satellite modem, satellite transceiver, or a satellite router, which may operate the VSAT in various bands. Depending on the design and function of the BUCs and LNBs, any one of the external reference frequencies ranging from <NUM>, <NUM>, or <NUM>, and the likes, may be provided to the BUCs/LNBs.

Network devices are typically designed to provide only one fixed reference frequency for a single set of BUC/LNB. In order to operate a different set of BUC/LNB requiring a different reference frequency, another network device/satellite modem of a different variant and design may be required. This limits the ability for customers to switch between different BUCs/LNBs without changing the satellite modem. Although multiple variants or designs of network device/satellite modem may be deployed in a single network to provide a wide range of reference frequencies for the different sets of BUCs/LNBs as per the requirement, however, this may cause a corresponding increase in the number of backend components required in the communication network or VSATs. Further, each network device may require a different clock frequency or clock. The increased number of network devices/satellite modems may tend to further exacerbate the problems as they may increase the complexities in the operation and usage of the network and corresponding equipment. Managing a higher volume of backend components, however, may be more challenging, especially when it comes to tending to potentially more malfunctions or defects in any of these components of the VSAT or network devices.

A single IDU or network device, for example, may provide only a fixed reference frequency for a single set of BUC/LNB. In order to operate a different set of BUC/LNB requiring a different reference frequency, another network device of a different variant and design may be required. This limits the ability for customers to switch between different BUCs/LNBs without changing the network device, as the same network device may not be compatible with other sets of BUCs/LNBs requiring different reference frequencies and also functionally incapable of generating a variable set of reference frequencies as per the requirement of other sets of BUCs/LNBs.

To address these issues, some satellite communication systems may employ multiple variants or designs of the network device in a single system to provide different sets of BUC/LNB requiring different reference frequencies in order to achieve a wider range and higher quality and more reliable satellite communication services to a variety of customers. However, in order to support the larger number of a different set of BUC/LNB requiring a different reference frequency, the VSATs and network device may require an increase in the number of components, such as oscillators, switches, amplifiers, divider circuits, splitters, etc. This increase in components may generally correspond with a rise in system complexity and may therefore lead to a greater probability of malfunction or defects. The added complexities may therefore give rise to more challenges in managing or troubleshooting all the issues associated with the various components of satellite communication systems.

However, employing a dedicated network device/satellite modem for generating different sets of reference frequencies may be highly expensive, and therefore cost-prohibitive for many service providers. For instance, the cost for using VSATs becomes increasingly more expensive as the number of the network device and associated components grows. Furthermore, systems requiring multiple sets of a dedicated network device may require customers to change the connection of a required network device to a given BUCs/LNBs to operate the VSAT in a dedicated band, which in turn may require extensive manual control to be exercised at all the different services and service paths available in the satellite communication system. Consequently, satellite system operators may use different network devices to generate a required reference frequency only after proper inspection of the required reference frequencies for the BUCs/LNBs and as per band requirements of the VSAT. Additionally, deploying different types and variants of network devices may be structurally impractical for some network configurations in terms of size and complexity of the overall system as the overall number of components and space required may correspondingly increase with the increase in the number of network devices.

Furthermore, the increased number of network devices and associated backend components may further generate a lot of heat, thereby requiring additional or enhanced cooling systems to keep the overall system in a controlled temperature environment. Network device and their associated components typically employ semiconductor devices that work optimally under a given temperature range, else the semiconductor devices may start working inefficiently and may also fail if the temperature goes beyond a safe range. This inefficient working or failure of the semiconductor devices may affect the working of the network devices, leading to inefficient working or overall failure of the network device as well as the satellite communication systems. Additionally, the cooling systems/requirement may further make the overall system complex, expensive, and bulky, requiring frequent maintenance and servicing.

Accordingly, customizable and flexible devices, systems and methods for providing configurable reference frequencies may be needed. Satellite communication systems may benefit from solutions or approaches that are capable of scaling with less cost, as well as those that are more efficient and proactive in providing configurable reference frequencies.

The devices, systems, and methods described herein, however, may opportunistically use a single customizable and flexible network device, rather than multiple dedicated network devices, to provide different sets of reference frequencies for various applications. For example, to operate the VSAT in a required band, the IDU may provide a plurality of configurable frequencies including radio transmitter (TX) and radio receiver (RX) reference frequencies to be used with different combinations of BUCs and LNBs.

The devices, systems, and methods described herein may utilize a single low noise oscillator and one or more digital to analog converters (DACs) to generate the plurality of configurable reference frequencies, which may be interoperable with Commercially Off-the-Shelf (COTS) BUCs and LNBs that require different reference frequencies. In addition, the devices, systems, and methods described herein may provide a more simplistic and efficient approach and design all that while maintaining lower expense and operating cost. In the examples described herein, a design, process, or technique may be employed to generate configurable reference frequencies based on the type of ODU, where the low noise oscillator and one or more DACs may be employed to generate the plurality of configurable reference frequencies as per the network requirement, rather than using a large number of backend components as used in existing/conventional techniques.

In this manner, the devices, systems and methods for providing a plurality of configurable reference frequencies, as described herein may provide solutions and designs that are more proactive, simple, cost-efficient, scalable, and amenable to broader satellite communication. These and other benefits and advantages may be apparent in the examples outlined below.

As described herein, the term "network device" may refer to a device or system that may be implemented in VSAT to generate reference frequencies based on the type of ODU of the VSATs, where the generated reference frequencies may be used with the LNBs and BUCs associated with the IDU of the corresponding VSAT. "Network device" is used to individually or collectively refer to devices including but not limited to a satellite modem, a satellite transceiver, or a satellite router.

<FIG> illustrates a system <NUM> for establishing satellite communication, according to an example. In some examples, the system <NUM> may depict a satellite communication system capable of providing at least voice and/or data services. In some examples, the satellite communication may be a high throughput satellite (HTS) system. The system <NUM> may include any number of terminals <NUM>, a satellite <NUM>, a gateway <NUM>, a network data center <NUM>, a network management system (NMS) <NUM>, a business system <NUM>, or other various system elements or components. The system <NUM> may also include a private network <NUM> and/or public network <NUM>. It should be appreciated that the system <NUM> depicted in <FIG> may be an example. Thus, the system <NUM> may or may not include additional features and some of the features described herein may be removed and/or modified without departing from the scopes of the system <NUM> outlined herein.

The terminals <NUM> may be any variety of terminals. For example, the terminals <NUM> may be customer terminals, such as very small aperture terminals (VSATs). It should be appreciated that VSATs may be terminals that are mounted on a structure, habitat, or other object or location. Depending on the application, terminals <NUM> may include or incorporate any number of antenna dishes, which may be provided in various sizes, depths, or dimensions (e.g., small, medium, large, etc.). Although the terminals <NUM> may typically remain in the same location once mounted, the terminals <NUM> may be removed from their mounts, relocated to another location, and/or may be configured to be mobile terminals. For instance, the terminals <NUM> may be mounted on mobile platforms that facilitate transportation thereof from one location to another. Such mobile platforms may include, for example, any number of mobile vehicles, such as cars, buses, boats, planes, etc. It should be appreciated that such terminals <NUM> may generally be operational when still and not while being transported. That said, there may be scenarios where the terminals <NUM> may be transportable (mobile) terminals that remain operational during transit. As used herein, the terms "terminal," "customer terminal," "satellite terminal," and/or "VSAT" may be used interchangeably to refer to these terminal types.

It should be appreciated that any number of customer premise equipment (CPE) (not shown) may be communicatively coupled to the terminals <NUM>. In some examples, the customer premise equipment (CPE) may include any number of computing or mobile devices. For example, such a computing or mobile device may include a laptop, a tablet, a mobile phone, an appliance, a camera, a sensor, a thermostat, a vehicle, a display, etc. In general, the customer premise equipment (CPE) may include, without limitation, any number of network-enabled computing devices, elements, or systems. It should be appreciated that a network of such devices may be commonly referred to as the "Internet of Things" (IoT).

As shown in <FIG>, there may be a plurality of groups of terminals <NUM> (e.g., customer VSATs). For example, there may be a first group 110A of terminals <NUM> and a second group 110B of terminals <NUM>. In some examples, the first group 110A may be "pre-qualified" terminals. The second group 110B may be "disqualified" terminals. The process and mechanism in providing configurable reference frequencies by the terminals <NUM> will be described in greater detail below. That said, it should be noted that categorizing the terminals <NUM> into at least a first group 110A and a second group 110B may be an important aspect of monitoring system health. In some examples, the devices, systems, and methods described herein may recognize that there are terminals <NUM> (e.g., VSATs including network devices such as satellite modem, a satellite transceiver, or satellite router, and the likes) that are deployed and not actively in use by customers. By identifying and leveraging these particular terminals <NUM>, the devices, systems, and methods described herein may provide configurable reference frequencies to be used with different combinations of low noise block converters (LNBs) and block-up converters (BUCs) associated with the terminals <NUM> in a satellite communication network, as described below. These and other benefits will be apparent in the examples presented below.

The satellite <NUM> may be an object intentionally placed into orbit. In some examples, the satellite <NUM> may be an artificial satellite that is configured to transmit and receive data signals. For example, the satellite <NUM> may form one or more beams and provide connectivity between at least the terminals <NUM> and the gateway <NUM>. More specifically, the satellite <NUM> may communicate data signals using these beams with the terminals <NUM> via a terminal return channel 115a and a terminal forward channel 115b, and with the gateway <NUM> via a gateway return channel 125a and a gateway forward channel 125b. It should be appreciated that the satellite <NUM> may form any number of beams to communicate data signals with any number of components, even beyond the terminals <NUM> or the gateway <NUM> as shown.

In some examples, the satellite <NUM> may be a communication satellite, such as a high-throughput satellite, which may include any satellite that is capable of providing at least twice (e.g., <NUM>+ times, <NUM>+ times, etc.) the total amount of throughput as a classic fixed-satellite service (FSS) satellite. In some examples, the satellite <NUM> may include, but not limited to, a transponder satellite, a regenerative satellite, and/or other similar satellite that may generate one or more spot beams. Furthermore, in some examples, the satellite <NUM> may operate in geosynchronous, mid-earth, low-earth, elliptical, or some other orbital configuration.

The gateway <NUM> may include or be communicatively coupled to a transceiver <NUM>, such as a radio frequency transceiver (RFT). The transceiver <NUM> may include an antenna unit of any type (e.g., transmitter, receiver, communication element, etc.), which may transmit and receive signals. In some examples, the transceiver <NUM> may be useable, by the gateway <NUM> of system <NUM>, to transmit and receive data from the terminals <NUM>, via communications from the satellite <NUM>, and may be configured to route data and traffic from these terminals <NUM> to any other element or component in the system <NUM>, such as the network data center <NUM> and/or network management system (NMS) <NUM>. The gateway <NUM> may be further configured to route traffic to and from the public internet <NUM> and/or private network <NUM> across the satellite communication channels 115a, 115b, 125a, or 125b to any terminal <NUM>, which would then provide data communications or route traffic to any customer premise equipment (CPE) (not shown) associated with the terminal <NUM>. Although depicted as a single element, the gateway <NUM> may include a single gateway, multiple gateways residing locally or remotely, in full or in part, relative to the other system components. As described in more detail below, the gateway <NUM>, the network data center <NUM>, and/or the network management system (NMS) <NUM> may provide operations associated with system health monitoring and fault detection.

The network data center <NUM> may be communicatively coupled to the gateway <NUM>, as well as other system components, such as the network management system (NMS) <NUM>, private network <NUM>, and/or public network <NUM>. In some examples, the network data center <NUM> may be a satellite network data center that is configured to perform protocol processing and bandwidth allocation for gateway traffic and/or VSAT communications in the served beams. Although depicted in <FIG> as a separate and distinct element, the network data center <NUM>, in some examples, may be collocated and/or integrated, fully or partially, with the gateway <NUM>, or may be positioned at some other location. Furthermore, although shown as a single element, the network data center <NUM>, in some examples, may include a plurality of network data centers that are local or remote, in full or in part, relative to the other system components.

The network management system (NMS) <NUM>, maintains, in full or in part, various information (configuration, processing, management, etc.) for the gateway <NUM>, and terminals <NUM> and beams supported by the gateway <NUM>. It should be appreciated that the network management system (NMS) <NUM> may or may not be co-located within the same physical structure as the gateway <NUM>. Furthermore, the network management system (NMS) <NUM> may be single or a plurality distributed components that may be communicatively coupled to each other and/or with other system elements, such as the gateway <NUM> (e.g., using the previously described hardware and external networks). The network management system (NMS) <NUM> may, among other things, include a configuration manager or other similar management unit. The network management system (NMS) <NUM> may also include any number of reporting systems. As will be discussed in greater detail below, each of these multiple reporting systems may be configured to receive different information (e.g., reports) from the terminals <NUM>. External reporting systems may also be configured to receive information (e.g., reports) from the terminals <NUM> by establishing a communication link with the network management system (NMS) <NUM>.

The business system <NUM>, or other various system elements or components, may also be communicatively coupled to the network management system (NMS) <NUM> and/or gateway <NUM>. In some examples, the business system <NUM> may include a virtual network operator (VNO), which may be configured to communicate with the gateway <NUM> and/or the network management system (NMS) <NUM> in order to monitor the status of its own terminals <NUM>. More particularly, a virtual network operator (VNO), in some scenarios, may be a business or government entity, that may have access (by purchase or license) to a managed service and associated capacity from a satellite network operator in order to provide communication connectivity and/or communication for a privately-owned set of terminals <NUM>. The virtual network operator (VNO) may therefore manage various aspects of such terminals <NUM> via the gateway <NUM> and/or the network management system (NMS) <NUM>.

The private network <NUM> and/or public network <NUM> may include any variety of networks. For example, the private network <NUM> may be a local area network (LAN), and the public network <NUM> may be a wide area network (WAN). That said, the private network <NUM> and/or public network <NUM> may each also be a local area network (LAN), wide area network (WAN), the Internet, a cellular network, a cable network, a satellite network, or other network that facilitates communication between the components of system <NUM> as well as any external element or system connected to the private network <NUM> and/or public network <NUM>.

The private network <NUM> and/or public network <NUM> may further include one, or any number, of the exemplary types of networks mentioned above operating as a stand-alone network or in cooperation with each other. For example, the private network <NUM> and/or public network <NUM> may utilize one or more protocols of one or more clients or servers to which they are communicatively coupled. The private network <NUM> and/or public network <NUM> may facilitate the transmission of data according to a transmission protocol of any of the devices and/or systems in the private network <NUM> and/or public network <NUM>. Although each of the private network <NUM> and/or public network <NUM> is depicted as a single network in <FIG>, it should be appreciated that in some examples, each of the private network <NUM> and/or public network <NUM> may include a plurality of interconnected networks as well.

While the processors, components, elements, systems, subsystems, and/or other computing devices may be shown as single components or elements, one of ordinary skill in the art would recognize that these single components or elements may represent multiple components or elements and that these components or elements may be connected via one or more networks. Also, middleware (not shown) may be included with any of the elements or components described herein. The middleware may include software hosted by one or more servers. Furthermore, it should be appreciated that some of the middleware or servers may or may not be needed to achieve functionality. Other types of servers, middleware, systems, platforms, and applications not shown may also be provided at the front-end or back-end to facilitate the features and functionalities of the system <NUM>, system component <NUM>, and their components, as shown in <FIG>.

<FIG> illustrates a system <NUM> requiring multiple VSATs or terminals <NUM>-<NUM> to <NUM>-N, each capable of providing one fixed reference frequency in order to provide/generate different reference frequencies to be used with different combinations of block-up converters (BUCs) <NUM>-<NUM> to <NUM>-N (collectively designated as <NUM>) and low noise block converters (LNBs) <NUM>-<NUM> to <NUM>-N (collectively designated as <NUM>) associated with the terminals or VSATs <NUM> in the network. As depicted, in a conventional implementation, the conventional system <NUM> may include one or more network devices or satellite routers or satellite modems <NUM>-<NUM> to <NUM>-N (collectively referred to as network devices or routers or modems <NUM>, herein). Each router <NUM> may be interfaced with different sets of BUCs and LNBs <NUM>, <NUM>. For example, as shown in <FIG>, a first router <NUM>-<NUM> may be interfaced with the first set of BUCs <NUM>-<NUM> and LNBs <NUM>-<NUM>, a second router <NUM>-<NUM> may be interfaced with the second set of BUCs <NUM>-2and LNBs <NUM>-<NUM>, and an Nth router <NUM>-N may be interfaced with an Nth set of BUCs <NUM>-N and LNBs <NUM>-N. Each of the routers <NUM> may be designed and selected to provide at least one set of reference frequencies for the corresponding set of BUCs and LNBs <NUM>, <NUM>. For example, as shown in <FIG>, the first router <NUM>-<NUM> may provide <NUM> of reference frequency to the first BUC <NUM>-<NUM>, and <NUM> of reference frequency to the first LNB <NUM>-<NUM>. Further, the Nth router <NUM>-N may provide <NUM> of reference frequency to the Nth BUC <NUM>-N, and <NUM> of reference frequency to the Nth LNB <NUM>-N, where N represents any integer greater than one.

<FIG> illustrates a block diagram of a conventional/typical network device/modem/router <NUM> for providing/generating fixed reference frequencies to a single set of BUC and LNB. In an example, a typical network device <NUM> may include an oscillator <NUM> operable to generate an output reference frequency of a first value. The oscillator <NUM> may be connected to a divider circuit <NUM> that processes the output reference frequency of the oscillator <NUM> to generate a reference frequency of a second value. The second value or the reference frequency generated by the divider circuit <NUM> may be <NUM>/Nth times the first value or the reference frequency generated by the oscillator <NUM> depending on the type of the divider circuit <NUM>, where N represents any integer greater than one. For example, the oscillator <NUM> may generate <NUM> as output reference frequency, and the divider circuit <NUM> may be a <NUM>/<NUM>th divider that may receive and process the reference frequency of <NUM> from the oscillator <NUM> to generate the reference frequency of <NUM>. The divider circuit <NUM> may be connected to the output of the oscillator <NUM> through a first switch <NUM>-<NUM>. Further, the outputs of the divider circuit <NUM> and the first switch <NUM>-<NUM> may be connected to a radio frequency (RF) splitter <NUM> through a second switch <NUM>-<NUM> such that based on the actuation of the first and second switches <NUM>-<NUM>, <NUM>-<NUM>, two different sets of reference frequencies may be generated and provided to the splitter <NUM>. The splitter <NUM> may include two outputs, which may be connected to a first amplifier <NUM>-<NUM> and a second amplifier <NUM>-<NUM>, respectively. The splitter <NUM> may split and transfer the two reference frequencies to the first and second amplifier <NUM>-<NUM>, <NUM>-<NUM>. The network device <NUM> may further include a third switch <NUM>-<NUM> connected to the first amplifier <NUM>-<NUM> and a fourth switch <NUM>-<NUM> connected to the second amplifier <NUM>-<NUM>. The third switch <NUM>-<NUM>, based on a transmitter (Tx) reference control signal, may actuate the first amplifier <NUM>-<NUM> to process one of the two output signals of the splitter <NUM> to generate a given value of Tx reference signals. Further, the fourth switch, based on a receiver (Rx) reference control signal, may actuate the second amplifier <NUM>-<NUM> to process the other output signal of the splitter <NUM> to either generate a given value of Rx reference signals or no Rx reference signals. In an example, as shown in <FIG>, the Rx reference control signal may disable the second amplifier <NUM>-<NUM> if the <NUM> path is directly chosen for the first and second switches <NUM>-<NUM>, <NUM>-<NUM> of the network device <NUM>.

Accordingly, the typical network device <NUM> or modem <NUM> of <FIG> may provide only one fixed reference frequency for a single set of BUC/LNB. This limits the ability of typical system <NUM> or network device <NUM> to switch between different BUCs/LNBs without changing the satellite modem. However, in order to operate multiple sets of BUC/LNB requiring different reference frequencies as shown in <FIG>, multiple network devices <NUM> (as shown in <FIG>) of different variants and designs may be required. Although multiple variants or designs of network device/modem/router may be deployed in a single network to provide a wide range of reference frequencies for the different sets of BUCs/LNBs as per the requirement, however, this may cause a corresponding increase in the number of backend components such as switches, amplifiers, splitters, and divider circuits required in the system. Further, each network device may require a different oscillator for generating different clock frequencies. The increased number of network devices and associated backend components may tend to further exacerbate the problems as they may increase the complexities in the operation and usage of a typical system and network devices. Further, managing a higher volume of backend components, however, may be more challenging, especially when it comes to tending to potentially more malfunctions or defects in any of these components of the VSAT or network devices.

The devices, systems, and methods described herein may overcome the above-mentioned drawbacks, limitations, and drawbacks associated with a typical system and network device, and may provide a single flexible and customizable network device for providing configurable reference frequencies to be used with different combinations of BUCs and LNBs associated with the terminals or VSATs <NUM> in the network.

<FIG> illustrates a VSAT <NUM> with a configurable network device <NUM> to provide different reference frequencies to be used with different combinations of BUCs <NUM> and LNBs <NUM>. In an example, a single network device <NUM> (or satellite modem or satellite router) described herein may be connected to one or more sets of BUCs <NUM> and LNBs <NUM>. The network device <NUM> receives information pertaining to a type of the ODU. Based on the type of the ODU associated with the VSAT <NUM>, the network device <NUM> is programmed/configured to generate configurable reference frequencies that are used with different combinations of BUCs <NUM> and LNBs <NUM>. In some examples, the network device <NUM> may be programmed/configured to generate configurable reference frequencies that may be used by a single set of BUC <NUM> and LNB <NUM> requiring different sets of reference frequency during the course of operation. In some examples, the plurality of configurable reference frequencies generated by the network device <NUM> may include radio transmitter (TX) and radio receiver (RX) reference frequencies that may be used by the VSAT <NUM>. For example, the Tx reference frequencies may be for the BUCs <NUM>, and the Rx reference frequencies may be for the LNBs <NUM> associated with the VSAT <NUM>. In an example, the network device/satellite rter <NUM> may generate Tx reference frequencies ranging from <NUM> to <NUM> for the BUC <NUM>. At the same time, the network device may generate Rx reference frequencies ranging from <NUM> to <NUM> for the LNB <NUM>. Further, the network device <NUM> also may generate Rx reference frequencies as an internal reference for the LNB <NUM>.

In another example, a single network device <NUM> described herein may be connected to an electronic device or a communication device (not shown) that may operate at a given or variable reference frequency. The network device <NUM> may receive details pertaining to a type and requirement of the electronic device or communication device. Based on the type and requirement of the electronic device or communication device, the network device may be configured to generate the required reference frequencies that may be used by the electronic device or communication device. For example, the network device <NUM> described herein may have application in timing generators that are used in Gateway NOC's (network operating center) equipment.

<FIG> illustrates a block diagram of a first embodiment of the network device <NUM> for generating configurable radio transmitter (Tx) and radio receiver (Rx) reference frequencies. In an example, the network device <NUM> described herein may include a single low noise oscillator <NUM> that may be operatively coupled with a sampling clock <NUM>. The sampling clock <NUM> may be operatively one or more Digital-to-Analog converters (DACs) <NUM>-<NUM>, <NUM>-<NUM> such that the sampling clock <NUM> upon actuation by the oscillator may generate and transmit a set of clock signals to the one or more DACs <NUM>-<NUM>, <NUM>-<NUM>, which results in the generation of a plurality of Tx reference frequencies and Rx reference frequencies by the one or more DACs <NUM>-<NUM>, <NUM>-<NUM>. Further, the output of each DAC <NUM>-<NUM>, <NUM>-<NUM> may be amplified by an amplifier <NUM>-<NUM><NUM>-<NUM>. For example, as depicted in <FIG>, a first amplifier <NUM>-<NUM> may be connected to a first DAC <NUM>-<NUM>, and a second amplifier <NUM>-<NUM> may be connected to a second DAC <NUM>-<NUM>. The first amplifier <NUM>-<NUM> corresponding to the first DAC <NUM>-<NUM> may receive a Tx reference control frequency as an input through a first switch <NUM>-<NUM> to generate Tx reference frequencies. Further, the second amplifier <NUM>-<NUM> corresponding to the second DAC <NUM>-<NUM> may receive RX reference control frequency as an input through a second switch <NUM>-<NUM> to generate RX reference frequencies. For example, as shown in <FIG>, the oscillator <NUM> may provide <NUM> frequency, and the first amplifier <NUM>-<NUM> of the network device <NUM> may either generate no reference, or <NUM> or <NUM> or <NUM> as Tx reference frequencies, and the second amplifier <NUM>-<NUM> of the network device <NUM> may either generate no reference or <NUM>, <NUM>, <NUM>, or <NUM> as Rx reference frequencies. The first amplifier <NUM>-<NUM> may either generate <NUM> or <NUM> or <NUM> as Tx reference frequencies when the first switch <NUM>-<NUM> is activated (switched ON) upon receiving a reference switching signal. Further, the first amplifier <NUM>-<NUM> may generate no reference when the first switch <NUM>-<NUM> is de-activated (switched OFF). Similarly, the second amplifier <NUM>-<NUM> may either generate <NUM> or <NUM> or <NUM> or <NUM> as Rx reference frequencies when the second switch <NUM>-<NUM> is activated (switched ON) upon receiving a reference switching signal. Further, the second amplifier <NUM>-<NUM> may generate no reference when the second switch <NUM>-<NUM> is de-activated (switched OFF). Each of the DACs <NUM>-<NUM>, <NUM>-<NUM> may enable the corresponding amplifiers <NUM>-<NUM>, <NUM>-<NUM> to generate the Tx and Rx reference frequencies, upon receiving an enabled (EN) signal at EN pin of the DACs <NUM>-<NUM>, <NUM>-<NUM>. For example, the first DAC <NUM>-<NUM> may receive the DAC1 EN signal at EN pin, and the second DAC <NUM>-<NUM> may receive the DAC2 EN signal at EN pin.

It should be appreciated that at a time of installation, the ODU configuration (e.g., BUC and LNB) may be entered by an installer or technician. In this example, power may not be applied to the ODU until this is done. Once the modem software is informed of the ODU configuration, the overall circuitry may then be enabled to output the proper Tx and Rx reference frequencies for the LNBs/BUCs. Other various examples may also be provided.

<FIG> illustrates a block diagram of a second embodiment of the network device <NUM> for generating configurable radio transmitter (Tx) and radio receiver (Rx) reference frequencies. In an example, the network device <NUM> described herein may include a single low noise oscillator <NUM> that may be operatively coupled with a sampling clock <NUM>. The sampling clock <NUM> may then be operatively a single DAC <NUM> such that the sampling clock <NUM> upon actuation by the oscillator <NUM> may generate and transmit a clock signal to the DAC <NUM>, which results in the generation of a reference frequency by the DAC <NUM>. The DAC <NUM> may be operatively coupled with an RF splitter <NUM> such that one of the outputs of the RF splitter <NUM> may be processed by a first amplifier <NUM>-<NUM> to generate RX reference frequencies. The first amplifier <NUM>-<NUM> may receive an input from a first switch <NUM>-<NUM> that in turn may process the first amplifier <NUM>-<NUM> to provide the Rx reference control frequency. The network device <NUM> may further comprise a second switch <NUM>-<NUM> that may receive an input from the RF splitter <NUM> and may provide an output to a second amplifier <NUM>-<NUM> that may generate Tx reference frequencies. The second amplifier <NUM>-<NUM> may receive an input from a third switch <NUM>-<NUM> that in turn processes the second amplifier <NUM>-<NUM> to provide the TX reference control frequency. The second switch <NUM>-<NUM> may additionally receive one or more desired TX reference frequencies as input from a set of switches <NUM>-<NUM>, <NUM>-<NUM> and a divider circuit <NUM>, where the one or more desired TX reference frequencies are generated by division of an initial frequency input being generated by the oscillator <NUM>. For example, as shown in <FIG>, the oscillator may generate a <NUM> frequency, which may be processed by the set of switches <NUM>-<NUM>, <NUM>-<NUM>, and divider circuit <NUM> to provide <NUM> or <NUM> frequency to the second switch <NUM>-<NUM>. Further, one of the outputs of the RF splitter <NUM> may provide <NUM> frequency to the first amplifier <NUM>-<NUM>, which may correspondingly provide either no frequency or <NUM> as Rx reference frequencies. The other output of the splitter <NUM> may provide <NUM> frequency to the second switch <NUM>-<NUM>. Based on the frequencies received by the second switch <NUM>-<NUM> from the RF splitter <NUM> and the set of switches <NUM>-<NUM>, <NUM>-<NUM>, and divider circuit <NUM>, the second switch <NUM>-<NUM> may actuate the second amplifier <NUM>-<NUM> to correspondingly provide <NUM> or <NUM> or <NUM> or no reference as Tx reference frequencies depending on the second switch <NUM>-<NUM> and the third switch <NUM>-<NUM>. In some examples, the generated Tx reference frequencies may be for the BUCs and the generated Rx reference frequencies may be for the LNBs.

Those skilled in the art would appreciate that while various examples and figures of the devices, systems, and methods described herein have been elaborated and illustrated for a network device <NUM>, <NUM> including one or two DACs and two amplifiers, which is providing only one set of two outputs from the network device <NUM>, <NUM> for a set of BUC and LNB <NUM>, <NUM>, however, the network device <NUM>, <NUM> may also involve more DACs and switches, but only one oscillator, to provide multiple sets of outputs for providing configurable Tx and Rx reference frequencies to multiple sets of BUCs and LNBs based on customer requirements, and all such examples are also within the scope of the devices, systems, and methods described herein.

In an example, at the time of installation of the network device <NUM>, <NUM>, <NUM> described herein, the ODU configuration (i.e. BUC and LNB Make and Model, or their reference frequency requirements) may be entered into the network device by an installer. Once the ODU configuration is installed in the network device, the network device (modem/router) may be operatively connected to the ODU and powered ON. The network device software may configure the network device to provide the required reference control signals to each switch associated with the network device and also provide the enable signals at the enable pins of each DACs of the network device, thereby controlling the overall circuitry of the network device to generate a specific set of Tx and Rx reference frequencies for the LNBs/BUCs.

<FIG> illustrates a method <NUM> for providing configurable reference frequencies to be used with different combinations of low noise block converters (LNBs) and block-up converters (BUCs) in a satellite communication network, according to an embodiment. The method <NUM> is provided by way of example, as there may be a variety of ways to carry out the method described herein. Although the method <NUM> is primarily described as being performed by the terminals/VSAT <NUM> or network devices <NUM>, <NUM> of <FIG>, the method <NUM> may be executed or otherwise performed by one or more processing components of another system or a combination of systems. Each block shown in <FIG> may further represent one or more processes, methods, or subroutines, and one or more of the blocks may include machine-readable instructions stored on a non-transitory computer-readable medium and executed by a processor or other type of processing circuit to perform one or more operations described herein. The VSAT/terminals, for example, may provide or generate configurable reference based on the type of outdoor unit (ODU) of the VSAT/terminal such that the plurality of configurable reference frequencies may be used with different combinations of LNBs and BUCs associated with an indoor unit (IDU) of the VSAT/terminal. In some examples, this may be an automated sequence of actions, as described below and shown in <FIG>.

At <NUM>, a network device associated with the terminal or the satellite communication network is configured by a processor in communication with the network device or VSATs. For example, the processor may be programmed as per customers' requirements or based on the type of outdoor unit (ODU) associated with the VSAT/terminal. This may correspondingly configure the network device to provide/generate configurable reference frequencies of predefined values as configured through the processor. At <NUM>, the network device receives information pertaining to a type and requirement of the ODU. The network device also determines the type of ODU based on the received information. In an example, details/information about the ODU may be retrieved by communicating with the ODU via a protocol such as <NUM>-way DiSEqC, assuming the ODU does not first need a clock source from the modem/router. The make and model of the ODU (or the reference frequency requirement of the BUC and LNB) may be entered by the customer/installer at install time and network device (modem/router) software may configure the network device to provide the reference frequencies accordingly. Further, at <NUM>, the network device provides a plurality of configurable reference frequencies to IDU of the terminal or to other telecommunication networks or systems as required. A plurality of configurable reference frequencies based on the type of ODU such that the configurable reference frequencies are used with different combinations of LNBs and BUCs associated with IDU of the terminal/VSAT, without changing the network device. In some examples, the plurality of configurable reference frequencies generated at block <NUM> may comprise radio transmitter (TX) and radio receiver (RX) reference frequencies.

<FIG> illustrates a block diagram of a computer system for providing configurable reference frequencies, according to an example. The computer system <NUM> may be part of or any one of the terminals <NUM>, the gateway <NUM>, the network data center <NUM>, the network management system (NMS) <NUM>, the business system <NUM>, as shown in system <NUM> and/or <NUM> to perform the functions and features described herein. The computer system <NUM> may include, among other things, an interconnect <NUM>, a processor <NUM>, a multimedia adapter <NUM>, a network interface <NUM>, a system memory <NUM>, and a storage adapter <NUM>.

The interconnect <NUM> may interconnect various subsystems, elements, and/or components of the computer system <NUM>. As shown, the interconnect <NUM> may be an abstraction that may represent any one or more separate physical buses, point-to-point connections, or both, connected by appropriate bridges, adapters, or controllers. In some examples, the interconnect <NUM> may include a system bus, a peripheral component interconnect (PCI) bus or PCI-Express bus, a Hyper Transport or industry standard architecture (ISA) bus, a small computer system interface (SCSI) bus, a universal serial bus (USB), IIC (I2C) bus, or an Institute of Electrical and Electronics Engineers (IEEE) standard <NUM> bus, or "firewire," or other similar interconnection element.

In some examples, the interconnect <NUM> may allow data communication between the processor <NUM> and system memory <NUM>, which may include read-only memory (ROM) or flash memory (neither shown), and random access memory (RAM) (not shown). It should be appreciated that the RAM may be the main memory into which an operating system and various application programs may be loaded. The ROM or flash memory may contain, among other code, the Basic Input-Output system (BIOS) which controls basic hardware operation such as the interaction with one or more peripheral components.

The processor <NUM> may be the central processing unit (CPU) of the computing device and may control overall operation of the computing device. In some examples, the processor <NUM> may accomplish this by executing software or firmware stored in system memory <NUM> or other data via the storage adapter <NUM>. The processor <NUM> may be, or may include, one or more programmable general-purpose or special-purpose microprocessors, digital signal processors (DSPs), programmable controllers, application specific integrated circuits (ASICs), programmable logic device (PLDs), trust platform modules (TPMs), field-programmable gate arrays (FPGAs), other processing circuits, or a combination of these and other devices.

The multimedia adapter <NUM> may connect to various multimedia elements or peripherals. These may include devices associated with visual (e.g., video card or display), audio (e.g., sound card or speakers), and/or various input/output interfaces (e.g., mouse, keyboard, touchscreen).

The network interface <NUM> may provide the computing device with an ability to communicate with a variety of remove devices over a network (e.g., private network <NUM> or public network <NUM> of <FIG>) and may include, for example, an Ethernet adapter, a Fiber Channel adapter, and/or other wired- or wireless-enabled adapter. The network interface <NUM> may provide a direct or indirect connection from one network element to another, and facilitate communication and between various network elements.

The storage adapter <NUM> may connect to a standard computer-readable medium for storage and/or retrieval of information, such as a fixed disk drive (internal or external).

Many other devices, components, elements, or subsystems (not shown) may be connected in a similar manner to the interconnect <NUM> or via a network (e.g., private network <NUM> or public network <NUM> of <FIG>). Conversely, all of the devices shown in <FIG> need not be present to practice the disclosed systems and methods. The devices and subsystems can be interconnected in different ways from that shown in <FIG>. Code or computer-readable instructions to implement the dynamic approaches for payment gateway selection and payment transaction processing of the disclosed systems and methods may be stored in computer-readable storage media such as one or more of system memory <NUM> or other storage. Code or computer-readable instructions to implement the dynamic approaches for payment gateway selection and payment transaction processing of the disclosed systems and methods may also be received via one or more interfaces and stored in memory. The operating system provided on computer system <NUM> may be MS-DOS®, MS-WINDOWS®, OS/<NUM>®, OS X®, IOS®, ANDROID®, UNIX®, Linux®, or another operating system.

As mentioned above, what is shown and described with respect to the systems and methods above are illustrative. While examples described herein are directed to configurations as shown, it should be appreciated that any of the components described or mentioned herein may be altered, changed, replaced, or modified, in size, shape, and numbers, or material, depending on application or use case, and adjusted for monitoring system health and/or detecting faults.

It should be appreciated that the devices, systems and methods described herein may facilitate more reliable use of terminals to monitor system health and/or detect system faults. It should also be appreciated that the systems and methods, as described herein, may also include or communicate with other components not shown. For example, these may include external processors, counters, analyzers, computing devices, and other measuring devices or systems. This may also include middleware (not shown) as well. The middleware may include software hosted by one or more servers or devices. Furthermore, it should be appreciated that some of the middleware or servers may or may not be needed to achieve functionality. Other types of servers, middleware, systems, platforms, and applications not shown may also be provided at the back-end to facilitate the features and functionalities of the testing and measurement system.

Moreover, single components may be provided as multiple components, and vice versa, to perform the functions and features described herein. It should be appreciated that the components of the system described herein may operate in partial or full capacity, or it may be removed entirely. It should also be appreciated that analytics and processing techniques described herein with respect to the optical measurements, for example, may also be performed partially or in full by other various components of the overall system.

It should be appreciated that data stores may also be provided to the devices, systems, and methods described herein, and may include volatile and/or nonvolatile data storage that may store data and software or firmware including machine-readable instructions. The software or firmware may include subroutines or applications that perform the functions of the measurement system and/or run one or more application that utilize data from the measurement or other communicatively coupled system.

The various components, circuits, elements, components, and interfaces, may be any number of mechanical, electrical, hardware, network, or software components, circuits, elements, and interfaces that serves to facilitate communication, exchange, and analysis data between any number of or combination of equipment, protocol layers, or applications. For example, the components described herein may each include a network or communication interface to communicate with other servers, devices, components or network elements via a network or other communication protocol.

Although examples are directed to network devices, satellite modems, and methods, for providing configurable reference frequencies to be used with different combinations of low noise block converters (LNBs) and block-up converters (BUCs), it should be appreciated that the devices, systems and methods described herein may also be used for providing reference frequencies or signals having specific frequency in various other systems and other implementations. In fact, there may be numerous applications in cable or optical communication networks including fiber sensor systems that could employ the systems and methods as well. For example, the network device herein may be used in timing generators in Gateway NOC's (network operating center) equipment.

It should be appreciated that the devices, systems, and methods described herein may also be used to operate multiple electronic and telecommunication devices or circuitries together, using a single flexible and customizable terminal/network device, without changing the hardware or design of the network device/terminals.

By leveraging existing customer terminals/VSATs/network devices, the devices, system and methods described herein may provide efficient reference frequency generation techniques and a cost-effective approach that may be readily integrated into various and existing network equipment. The devices, systems and methods described herein may provide mechanical simplicity and adaptability to small or large satellite communication systems. Ultimately, the devices, systems and methods described herein may increase efficiency, reduce cost, maximize existing equipment, minimize adverse effects, drawbacks, and limitations of traditional VSATs and terminal devices, and improve the reference frequency generation capability and flexibility.

Claim 1:
A network device for a satellite communication network, the network device being any of a satellite modem, satellite transceiver, or a satellite router, the network device comprising:
a processor (<NUM>); and
a memory (<NUM>) having instructions, which when executed by the processor, causes the processor to:
receive (<NUM>) information pertaining to a type of an outdoor unit, ODU;
determine the type of ODU based on the received information;
and
provide (<NUM>) a plurality of configurable reference frequencies based on the type of the ODU such that the plurality of configurable reference frequencies are used with different combinations of low noise block converters, LNBs, and block-up converters, BUCs, associated with the ODU.