HYBRID WIRELESS LINK EMPLOYING FREE-SPACE OPTICAL COMMUNICATION, RADIO FREQUENCY COMMUNICATION, AND INTELLIGENT FRAME AND PACKET SWITCHING

Abstract

A node in a hybrid wireless link includes a free space optical (FSO) terminal and a radio frequency (RF) terminal. The FSO terminal is configured to transmit data over an FSO link, and the RF terminal is configured to transmit data over a free space RF link. The node also includes a switch/controller coupled to the FSO terminal and the RF terminal. The switch/controller is configured to receive data and determine at the data link layer whether to transmit data frames of the data over the FSO link, the RF link, or both. The determination is based on the content of the data frames, and, once the determination is made, the switch/controller steers the data frames to the FSO terminal, the RF terminal, or both. In some embodiments, the switch/controller makes the determination at the network layer.

Claims

1. A local node that provides a hybrid wireless link to a remote node, the local node comprising: a free space optical (FSO) terminal configured to transmit data to the remote node over a free space optical link; a radio frequency (RF) terminal configured to transmit data to the remote node over a free space RF link, wherein the free space optical link and the free space RF link together form the hybrid wireless link between the local node and the remote node; and a switch/controller coupled to the FSO terminal and to the RF terminal, the switch/controller configured to receive data, to determine at the data link layer whether to transmit data frames of the data over the free space optical link and/or over the free space RF link wherein the determination is based on a content of the data frames, and to steer the data frames to the FSO terminal and/or to the RF terminal based on the determination.

2. The local node of claim 1, wherein the switch/controller implements a data link protocol for hybrid wireless links.

3. The local node of claim 1, wherein the switch/controller determines at the data link layer whether to transmit data frames over the free space optical link and/or over the free space RF link based on at least one of: ingress port, egress port, MAC source address, MAC destination address, EtherType, outer 802.1Q tag VLAN ID, outer 802.1Q tag PCP, outer 802.1Q tag DEI, inner 802.1Q tag VLAN ID, inner 802.1Q tag PCP, inner 802.1Q tag DEI, IPv4 source address, IPv4 destination address, IPv4 DSCP, IPv4 ECN, IPv4 protocol field, IPv6 source address, IPv6 destination address, IPv6 traffic class, IPv6 Next Header, IPv6 flow label, IPv6 SRH, outer MPLS tag label, outer MPLS tag EXP (QoS or ECN), one or more inner MPLS tag labels, or one or more inner MPLS tags EXP (QoS or ECN).

4. The local node of claim 1, wherein the switch/controller determines at the data link layer whether to transmit data frames over the free space optical link and/or over the free space RF link based on a condition of the hybrid wireless link, the condition of the hybrid wireless link including at least one of: instantaneous or time averaged throughput; frame loss ratio; latency; jitter; link utilization; expected or calculated link availability; link state (link up or down); predicted link performance based on link location, time of day, time of year; or measured, reported, or estimated atmospheric conditions.

5. The local node of claim 1, wherein the switch/controller is configured to steer individual data frames alternately to the free space optical link and to the free space RF link.

6. The local node of claim 1, wherein the switch/controller comprises: a switching component configured to receive the data frames and perform data link layer functions on the data frames; and a data link protocol component configured to receive the data frames from the switching component and steer the data frames to the FSO terminal and/or to the RF terminal.

7. The local node of claim 6, wherein none of the data link layer functions performed by the switching component are specific to hybrid wireless links.

8. The local node of claim 6, wherein the switching component determines a class of service and/or a quality of service for data frames based on the content of the data frames, and whether to transmit the data frames over the free space optical link and/or over the free space RF link is based on the class of service and/or the quality of service.

9. The local node of claim 6, wherein the switching component determines a traffic treatment for data frames based on the content of the data frames, and whether to transmit the data frames over the free space optical link and/or over the free space RF link is based on the traffic treatment.

10. The local node of claim 6, wherein the switch/controller implements a data link protocol for hybrid wireless links, and the data link protocol component implements an entirety of the data link protocol.

11. The local node of claim 10, wherein the data link protocol implements a plurality of traffic treatments assigned to the data frames, and the data link protocol component steers the data frames to the FSO terminal and/or to the RF terminal based on the traffic treatment assigned to the data frame.

12. The local node of claim 11, wherein traffic treatments are assigned to data frames based on at least one of VLAN tag, port number, and traffic type.

13. The local node of claim 6, wherein the switching component produces tags for the data frames based on their content, and the data link protocol component steers the data frames to the FSO terminal and/or to the RF terminal based on a lookup table that maps the tags to the FSO terminal and/or the RF terminal.

14. The local node of claim 6, wherein the data link protocol component manages retransmission of data frames in an event of lost data.

15. The local node of claim 1, wherein the hybrid wireless link is bidirectional.

16. The local node of claim 15, wherein the local node and the remote node are part of a network with additional other nodes.

17. The local node of claim 1, wherein the free space optical link has a nominal data rate of at least 10 Gbps and the local node and the remote node are located at least 4 km apart.

18. The local node of claim 1, wherein the free space optical link operates in an infrared wavelength range and the free space RF link operates in an E-band.

19. A local node that provides a hybrid wireless link to a remote node, the local node comprising: a physical layer comprising: a free space optical (FSO) terminal configured to transmit data to a remote node over a free space optical link; and a radio frequency (RF) terminal configured to transmit data to the remote node over a free space RF link, wherein the free space optical link and the free space RF link together form a hybrid wireless link between the local node and the remote node; and a data link layer that determines whether data frames of the data are transmitted to the remote node over the free space optical link and/or over the free space RF link.

20. A local node that provides a hybrid wireless link to a remote node, the local node comprising: a free space optical (FSO) terminal configured to transmit data to a remote node over a free space optical link; a radio frequency (RF) terminal configured to transmit data to the remote node over a free space RF link, wherein the free space optical link and the free space RF link together form a hybrid wireless link between the local node and the remote node; and a controller coupled to the FSO terminal and to the RF terminal, the controller configured to receive data, to determine at the data link layer and/or the network layer whether to transmit data frames and/or network packets of the data over the free space optical link and/or over the free space RF link wherein the determination is based on a content of the data frames and/or network packets, and to steer the data frames and/or network packets to the FSO terminal and/or to the RF terminal based on the determination.

Description

BRIEF DESCRIPTION OF DRAWINGS

[0049] Embodiments of the disclosure have other advantages and features which will be more readily apparent from the following detailed description and the appended claims, when taken in conjunction with the examples in the accompanying drawings, in which:

[0050] FIG. 1 is a block diagram of a local node and a remote node communicating via an optical channel and a radio frequency channel, according to an embodiment.

[0051] FIG. 2 is a block diagram of a switch/controller unit, according to an embodiment.

[0052] FIG. 3 is a block diagram of a free-space optical (FSO) terminal, according to an embodiment.

[0053] FIG. 4 is a block diagram of the E-Band terminal, according to an embodiment.

[0054] FIG. 5 is a block diagram of a local node and a remote node, wherein the switch/controller units for each node are installed in sheltered locations and the FSO and E-Band terminals for each node are mounted on external structures, according to an embodiment.

[0055] FIG. 6 is a block diagram of a local node and a remote node, wherein the switch/controller units for each node are installed on external structures, according to an embodiment.

DETAILED DESCRIPTION

[0056] The figures and the following description relate to preferred embodiments by way of illustration only. It should be noted that from the following discussion, alternative embodiments of the structures and methods disclosed herein will be readily recognized as viable alternatives that may be employed without departing from the principles of what is claimed.

[0057] This description relates to a method of wireless digital communication. Particularly, this description relates to communication between two wireless digital communication nodes. More particularly, this description relates to communication between two digital communication nodes, each consisting of a switch/controller and two wireless communication terminals. More particularly, this description relates to communication between two digital communication nodes, each employing two different wireless digital communications technologies, operating in parallel for improved weather tolerance. More particularly, this description relates to wireless communication. More particularly, this description relates to wireless communication between nodes that are mounted on building sides, towers, other structures, ships, or airborne platforms such as airplanes, balloons, dirigibles, and other fixed- or non-fixed-wing aircraft. Specifically, the description relates to a technique for wireless digital communication between two nodes, each including a switch/controller, a millimeter wave (mm Wave) radio frequency terminal transmitting and receiving at frequencies in the millimeter wave frequency band, and a free space optics (FSO) terminal transmitting and receiving optically.

[0058] FIG. 1 is a block diagram of a local node 12 and a remote node 14 communicating via a hybrid wireless link 10 that includes an optical channel 16 and a radio frequency channel 18, according to an embodiment. The local node 12 and remote node 14 may be a part of high capacity wireless communication networks such as cellular networks, broadband networks, air-to-ground networks, air-to-air networks, and other data networks employing high capacity wireless links. The hybrid wireless link 10 employs two free-space communications technologies, free-space optical (FSO) communication and radio frequency (RF) communication. Each technology is capable of transmitting and receiving data between two sets of apparatus (nodes) without the use of wired communication media such as copper wire, coaxial cable, or fiber optic cable. In alternative configurations, different, and/or additional components may be included in FIG. 1. Furthermore, the components in the block diagram may be deployed in one or more physical devices and embodied in software, firmware, hardware, or any combinations thereof.

[0059] FSO communication and RF communication are each effected by weather, which can cause transmission errors (bit errors) and/or halt communication. FSO communication is generally affected by weather that causes reduced visibility (e.g., weather which disturbs or absorbs light waves), and RF communication is generally affected by weather that causes absorption or scattering of RF waves, especially as the transmission frequency increases.

[0060] When employed together, FSO communication and RF communication provide improved tolerance to the effects of weather on the communication link than either technology alone.

[0061] The hybrid wireless link 10 also employs data frame switching (layer 2) and/or network packet routing (layer 3) to allocate the traffic flow between the optical channel 16 and the radio frequency channel 18. Data frame switching and network packet routing allows data to be delivered between two nodes in a network across one or more links. Data frame switching and network packet routing, features delivery of variable bit rate data streams, realized as sequences of data frames or network packets, over a computer or data network which allocates transmission resources as desired using statistical multiplexing or dynamic bandwidth allocation techniques. The treatment of these data frames or network packets is based on their content, traffic type, priority, and other attributes of the data carried within the data frame or network packet. This switching applies different rules to different data frames or network packets, based on those attributes, to deliver the data frames or network packets with appropriate latency, priority, and protection. As a result, the combination of FSO communication, RF communication, and data frame switching and/or network packet routing provides significant advantages in wireless communication.

[0062] The hybrid wireless link 10 includes two nodes, one designated as the local node 12 and one designated as the remote node 14. The two nodes are connected by an optical channel 16 and a radio frequency channel 18. Digital data is transmitted between the local node 12 and the remote node 14 and from the remote node 14 to the local node 12 across both the optical channel 16 and the radio frequency channel 18. Data transmitted between the nodes includes a combination of user data and overhead data. Overhead data includes various management data that allows communication between subsystems within each node.

[0063] In an embodiment, the RF communication technology operates at frequencies between 71 gigahertz (GHz) and 86 GHz. In an embodiment, the RF communication technology of the local node 12 transmits at a center frequency between (transmit frequency) 71 GHz and 76 GHz and receives at a center frequency (receive frequency) between 81 GHz and 86 GHz while the remote node 14 operates with a receive frequency matched to the local nodes transmit frequency and a transmit frequency matched to the local nodes receive frequency.

[0064] In alternate embodiments, the RF communication technology can operate at frequencies between 40 GHz and 71 GHz. In alternate embodiments, the RF communication technology can operate at frequencies between 71 GHz and 110 GHz.

[0065] In an embodiment, both the FSO communication technology (the FSO link) and the RF communication technology (the E-Band link or the RF link) operate at a nominal data rate of 10 gigabits per second (Gbps). In these embodiments, the data transmitted across a link is typically at or above 10 Gbps (e.g., within 2 Gbps). However, because the data includes overhead data, the data rate for user data may be slightly below 10 Gbps (e.g., within 2 Gbps). In another embodiment, the FSO link operates at a nominal data rate of 10 Gbps and the E-Band link operates at a nominal data rate between 2.5 Gbps and 5 Gbps. In some embodiments, the FSO link operates in an infrared wavelength range and the RF link operates in an E-Band range.

[0066] The local node 12 includes a network interface 19 and a management interface 20. Similarly, the remote node 14 includes a network interface 22 and a management interface 24. Both network interfaces serve to a) accept digital data to be transmitted across the hybrid link, and b) deliver digital data that has successfully been transmitted across the hybrid link. The management interfaces allow the nodes and the link to be configured and monitored by a management channel. For example, the management interfaces provide information, such as timing signals, necessary to operate as part of a larger network. Since overhead data can be communicated between the nodes, a management channel between the two nodes allows both the local node 12 and remote node 14 to be configured and monitored (managed) via the management interface 20 at the local node 12 and the management interface 24 at the remote node 14.

[0067] The local node 12 includes a switch/controller subsystem 30, an FSO terminal 32, an E-Band terminal 34, a terminal mount for the FSO terminal 36, and a terminal mount for the E-Band terminal 38. The switch/controller 30 is communicatively coupled to the FSO terminal 32 and the E-Band terminal 34, and the terminal mounts physically connect the terminals to the building or structure on which the terminals are installed.

[0068] The switch/controller 30 accepts user data to be transmitted to the remote node across the hybrid link and delivers data that has been successfully received by the local node via the network interface 19. The switch/controller 30 accepts configuration commands, timing signals, and other information and provides status, alarms, and other information, via the management interface 20. The switch/controller 30 also accept similar communication information via the management channel, conveyed over both the FSO link and the E-Band link between the two nodes. This allows the local node 12 to be managed via the local node's management interface 20 or the remote node's management interface 24.

[0069] The switch/controller 30 communicates with the FSO terminal 32 over a terminal interface 40. The switch/controller 30 communicates with the E-Band terminal 34 over a second terminal interface 42. A combination of user data and management data is transferred, in both directions, between the switch/controller 30 and both the FSO terminal 32 and the E-Band terminal 34, across the terminal interfaces 40 and 42.

[0070] The switch/controller 30 is configured to receive data (e.g., from the network interface 19 and the management interface 20) to be transmitted to the remote node 14. The switch/controller 30 determines at layer 2 whether frames of the data will be transmitted over the optical channel 16, the RF channel 18, or both. The determination is based on the content of the data frames, and, in some implementations, the determination may be made separately for each individual frame of the data. Once the determination is made, the switch/controller 30 provides the data frames assigned to the optical channel 16 to the FSO terminal and the individual frames assigned to the RF channel 18 to the E-Band terminal. In some embodiments, the switch/controller 30 determines at layer 3 how each network packet of the data will be transmitted. In these embodiments, the determination is made based on the content of the packets.

[0071] The content of the data frames or network packets that may affect the layer 2 or layer 3 determination may include user data and overhead data. For example, the determination is based on ingress port, egress port, MAC source address, MAC destination address, EtherType, outer 802.1Q tag VLAN ID, outer 802.1Q tag PCP, outer 802.1Q tag DEI, inner 802.1Q tag VLAN ID, inner 802.1Q tag PCP, inner 802.1Q tag DEI, IPv4 source address, IPv4 destination address, IPv4 DSCP, IPv4 ECN, IPv4 protocol field, IPv6 source address, IPv6 destination address, IPv6 traffic class, IPv6 Next Header, IPv6 flow label, IPv6 SRH, outer MPLS tag label, outer MPLS tag EXP (QoS or ECN), any inner MPLS tag label, any inner MPLS tag EXP (QoS or ECN), or higher layer protocol information. Additional examples include customer defined link priority, overhead link management data, and whether the data frames or network packets have already been transmitted and need to be retransmitted.

[0072] In addition to content of the data frames or network packets, the determination to transmit each frame or packet over the optical channel 16, the RF channel 18, or both may be based on a condition of the hybrid wireless link 10, such as instantaneous or time averaged throughput; data frame loss ratio; latency; jitter; link utilization; expected or calculated link availability; link state (link up or down); predicted link performance based on link location, time of day, time of year; and measured, reported, or estimated atmospheric conditions. Additional examples include RF link and FSO link quality status updates. These may be based on remote or local indicators of transmit quality and retransmission queues. For example, if the atmospheric conditions indicate that heavy fog is between the local and remote node, the data may be transmitted over the RF channel 18. In another example, if the RF channel 18 consistently has a low throughput during sunrise, data may be transmitted over the optical channel 16 during sunrise.

[0073] The remote node 14 includes the same major subsystems, including a switch/controller 50, an FSO terminal 52 and its terminal mount 56, an E-band terminal 54 and its terminal mount 58. Similar to the local node 12, the switch/controller 50 in the remote node 14 communicates with the FSO terminal 52 and the E-Band terminal 54, via terminal interfaces 60 and 62.

[0074] A block diagram of the switch/controller 30 is shown in FIG. 2, according to an embodiment. The switch/controller 30 includes a node controller 70, a switching component 72, a data link protocol component 74, and a power unit 76. Data to be transmitted by the local node 12 to the remote node 14 over the hybrid link 10 is accepted by the switch/controller 30 via the network interface 19. Data received by the local node 12 from the remote node 14 is delivered via the network interface 19. Configuration commands are accepted by the switch/controller 30 and status, performance, and alarms are provided via the management interface 20. The switch/controller 30 interfaces with the FSO terminal 32 via a terminal interface 40 and the E-Band terminal 34 via a second terminal interface 42. In alternative configurations, different, and/or additional components may be included in FIG. 2. Furthermore, the components in the block diagram may be deployed in one or more physical devices and embodied in software, firmware, hardware, or any combinations thereof.

[0075] The node controller 70 also functions as the control plane processor, and control plane frames or packets can be received or transmitted over interface 19, transferred to or from the node controller over 78, and processed in the node controller 70.

[0076] The node controller 70 is responsible for configuration and control of the local node. The node controller 70 also communicates with the node controller in the remote node 14 via a node-to-node management channel multiplexed into the data stream transmitted across the hybrid link 10. Communication information, such as management commands and status, performance, and alarm information, are received and transmitted by the node controller 70 via the local management interface 20. The node controller 70 may also receive and transmit communication information from/to the remote node 14 via the node-to-management channel. Interfaces provided by the node controller 70 include: Network Configuration Protocol (NETCONF), as defined by the Internet Engineering Task Force (IETF) for status and configuration of the node; Simple Network Management Protocol (SNMP), for status, performance and alarms; and a command line interface (CLI). The node controller 70 also provides a web-based graphical user interface (GUI) over the management interface 20.

[0077] The node controller 70 sends configuration commands to and receives status, performance and alarms from the FSO terminal 32 via the terminal interface 84. Similarly, the node controller 70 sends configuration commands to and receives status, performance and alarms from the E-Band terminal 34 via the terminal interface 90. In an embodiment, the management interfaces 84 and 90 operate at data rates of at least 1 Gbps. Further, in an embodiment, the management interfaces 84 and 90 GigE interfaces with power-over-Ethernet (PoE).

[0078] The node controller sends command to and receives status, performance and alarms from the switching component 72 over a dedicated interface 78. The node controller sends commands to, and receives status, performance and alarms from, the data protocol processor over a dedicated interface 80. The node-to-node management channel from the local node controller 70 to the node controller in the remote node 14 is also delivered/received via the interface 80.

[0079] In an embodiment, the node controller 70 is implemented as a plurality of software entities executing on a standard central processing unit (CPU) application specific standard part (ASSP).

[0080] The switching component 72 may be configured to perform a variety of data frame switching and network packet routing functions (e.g., layer 2, layer 2.5, and layer 3 functions). These functions may not be specific to hybrid wireless links. For example, the functions may include: identification of traffic flows by port number or VLAN identifier; traffic policing on those traffic flows; switching traffic flows to and from the data link protocol processor; and traffic shaping. The switching component 72 accepts configuration commands from and delivers status, performance, and alarm information to the node controller 70 via a dedicated interface 78. In some embodiments, the switching component 72 is implemented as a layer 2 and layer 3 ASSP. In some embodiments, the switching component 72 determines whether to transmit the data frames over the FSO link, the RF link, or both. Alternatively, the data link protocol component 74 may make this determination.

[0081] The switching component 72 may calculate and assign a class of service, a quality of service, and/or a traffic treatment for one or more data frames based on the content of the frames. If so, the determination whether to transmit the data frames over the FSO link, the RF link, or both may be based on the class of service, quality of service, and/or the traffic treatment determinations. For example, if the FSO link has a higher reliability than the RF link, data frames assigned with higher priorities are transmitted via the FSO link (or via both links) and data frames assigned with lower priorities are transmitted via the RF link.

[0082] In some embodiments, the switching component 72 tags data frames according to their content. In these embodiments, the data link protocol component 74 steers the data frames to the FSO link, the RF link, or both based on a lookup table that maps the tags to one or more links.

[0083] The switching component 72 accepts user traffic to be transmitted over the hybrid wireless link to the remote node 14 via the network interface 19. The switching component 72 also delivers user traffic received over the hybrid wireless link from the remote node 14 via the network interface 19. The network interface 19 includes a plurality of bi-directional data ports. In an embodiment, the network interface 19 includes a plurality of Gigabit Ethernet (GigE) data ports and a plurality of 10 Gbps Ethernet data ports (10 GigE) data ports. In an embodiment, the aggregate capacity of the network interface 19 data ports is greater than the total combined capacity of 20 Gbps available over the FSO link and E-Band link.

[0084] The switching component 72 delivers data (e.g., data frames or network packets) to the data link protocol component 74 via a dedicated interface 82 in order for that data to be transmitted over the hybrid link to the remote node 14. The switching component 72 also receives data from the data link protocol component 74 over the same dedicated link 82, after the data was received over the hybrid link from the remote node 14. In some embodiments, the interface 82 between the switching component 72 and the data link protocol component 74 operates at 20 Gbps or more in each direction (e.g., full duplex).

[0085] The data link protocol component 74 implements a data link protocol to orchestrate the traffic flows across both the FSO link and the E-Band link. The data link protocol may be a proprietary protocol. By executing the protocol, the data link protocol component 74 may steer individual data frames (or network packets) to the FSO terminal 32 and the E-Band terminal 34. When transmitting data, the data link protocol component 74 implement a number of traffic treatments assigned to the data frames (e.g., frame priority). Based on the assigned traffic treatments, the data frames may be steered to the FSO link, RF link, or both links. For example, data frames assigned to a higher priority traffic treatment are given precedence over frames assigned to a lower priority traffic treatment. The data link protocol component 74 considers many factors to assign a traffic treatment to each frame. These factors may include VLAN tag, port number, and traffic type, among others. When receiving data, the data link protocol considers the assigned traffic treatment to assure timely and accurate delivery of the received frames.

[0086] The data link protocol component 74 sends data, including the user data and management channel data, to be transmitted over the FSO link to the FSO terminal 32 via the terminal interface 86 and sends data to be transmitted over the E-Band link to the E-Band terminal 34 via the terminal data interface 92. In an embodiment, interfaces 86 and 92 operate at peak data rates of at least 10 Gbps. Further, in an embodiment, the interfaces 86 and 92 are 10 GigE interfaces.

[0087] In an embodiment, the data link protocol component 74 is implemented as a plurality of software entities executing on a multi-core network processor unit (NPU) ASSP. In a different embodiment, the data link protocol component 74 is implemented in a field programmable gate array (FPGA). In a different embodiment, the data link protocol component 74 is implemented in silicon as an application specific integrated circuit (ASIC). In other embodiments, the data link protocol component 74 is implemented as a combination of software entities running on an NPU or CPU together with an FPGA or an ASIC.

[0088] The power unit 76 accepts power from a power source and provides power to both the FSO terminal 32 via a dedicated power interface 88 and to the E-Band terminal 34 via a second dedicated power interface 94. In an embodiment, the power unit 76 accepts power from either an alternating current (AC) power source operating at voltages between 100 volts and 240 volts or a direct current (DC) power sources operate at a nominal voltage of negative 48 volts. In an embodiment, the power unit 76 provides power at a nominal voltage of positive 48 volts to the both the FSO terminal 32 via the PoE equipped GigE management interface 84 and to the E-Band terminal 34 via the PoE equipped GigE management interface 90.

[0089] FIG. 3 shows a block diagram of the FSO terminal 32, according to an embodiment. The FSO terminal 32 includes a terminal controller 100, an FSO modulator/demodulator (modem) 102, an optical processor 104, an optical transmit aperture 106, an optical receive aperture 108, and a terminal power unit 110. The FSO terminal 32 interfaces with the switch/controller 30 via the terminal interface 40. The FSO terminal 32 transmits a modulated FSO signal 122 over the free space optical channel 16 to the remote node 14. It also receives a modulated FSO signal 124 over the free space optical channel 16 that was sent from the remote node 14. In alternative configurations, different, and/or additional components may be included in FIG. 3. Furthermore, the components in the block diagram may be deployed in one or more physical devices and embodied in software, firmware, hardware, or any combinations thereof.

[0090] The FSO terminal controller 100 is responsible for configuring and monitoring the FSO terminal. It receives configuration commands from and provides status, performance, and alarm information to the node controller 70 via the management interface 84 portion of the terminal interface 40. The terminal controller 100 delivers configuration commands to and receives status, performance, and alarm information from the FSO modem 102 via a dedicated interface 112. The terminal controller 100 also provides FSO management data, to be multiplexed into the transmitted data, to the FSO modem 102 and receives FSO management data, demultiplexed from the received data, from the FSO modem 102 over the same dedicated interface 112. The terminal controller 100 delivers configuration commands to and receives status, performance, and alarm information from the optical processor 104 via another dedicated interface 114.

[0091] The FSO modem 102 is responsible for modulating and amplifying light emitted from a laser source. In an embodiment, the FSO modem 102 performs data processing functions, including framing, interleaving, and forward error correction (FEC) coding, prior to modulating the laser light. Further, in an embodiment, the FSO modem 102 employs on-off-keying (OOK) modulation to modulate the laser light. In an alternate embodiment, the FSO modem 102 employs coherent, quadrature amplitude modulation (QAM) instead of OOK modulation. In an embodiment, the FSO modem 102 modulates the laser light at a data rate sufficient to transmit at least 10 Gbps of user data plus overhead data including management channel data and FEC overhead.

[0092] The amplified, modulated laser light is delivered to the optical processor via an optical interface 116.

[0093] In an embodiment, the FSO modem 102 modulates light characterized by a wavelength within the 1550 nanometers (nm) region (1530 nm to 1565 nm). More particularly, in an embodiment, the FSO modem 102 modulates light characterized by a wavelength specified by the International Telecommunications Union (ITU) as one of the wavelengths on the DWDM grid with 100 GHz spacing. In an alternate embodiment, the FSO modem 102 operates at a wavelength of 850 nm, 980 nm, or within the 1300 nm region (1280 nm to 1310 nm).

[0094] In an embodiment, the FSO modem 102 employs an erbium doped fiber amplifier (EDFA) to amplify the modulated laser light.

[0095] The FSO modem 102 is also responsible for amplifying, detecting, and demodulating light received by the FSO Terminal 32. The received signal is provided by the optical processor 104 to the FSO modem 102 via the optical interface 116.

[0096] In some embodiments, the FSO modem 102 employs an erbium doped fiber amplifier (EDFA) to amplify the received light, prior to detection and demodulation. In some embodiments, the FSO modem 102 employs an avalanche photo diode (APD) to detect the amplified received light, prior to demodulation. In some embodiments, the FSO modem 102 performs data processing functions, including de-framing, de-interleaving, and forward error correction (FEC) decoding, after demodulating the received light. Further, in some embodiments, FSO modem 102 employs on-off-keying (OOK) demodulation to demodulate the received light. In an alternate embodiment, the FSO modem 102 employs coherent, quadrature amplitude demodulation (QAM) instead of OOK demodulation. In some embodiments, the FSO modem 102 demodulates the laser light at a data rate sufficient to transmit at least 10 Gbps of user data plus overhead data including management channel data and FEC overhead.

[0097] The FSO modem 102 accepts data to be transmitted from the switch/controller unit 30 via the data interface 86 portion of the terminal interface 40. It also accepts FSO management data from the terminal controller 100 and then multiplexes the management data into the transmit data stream prior to modulation.

[0098] The optical processor 104 prepares the amplified and modulated laser light (transmit signal) for transmission and prepares the received light (receive signal) prior to amplification, detection, and demodulation by the FSO modem 102. The optical processor 104 accepts the transmit signal from the FSO modem 102 and delivers the receive signal to the FSO modem 102 via optical interface 116. After preparation, the transmit signal is sent by the optical processor 104 through the optical transmit aperture 106 toward the remote node 14 via an optical interface 118. Similarly, the optical processor 104 first accepts the receive signal from the remote node 14 through the optical receive aperture 108 via an optical interface 120.

[0099] In some embodiments, the optical transmit aperture 106 and the optical receive aperture 108 are the same (e.g., the FSO terminal 32 is co-boresighted). Further, in some embodiments, the optical processor 104 performs active pointing and tracking to maintain accurate pointing between the FSO terminal 32 and the remote node 14.

[0100] In some embodiments, the FSO terminal 32 generates and transmits single optical signals to the remote node 14 (and similarly receives and processes single optical signals from the remote node 14). In another embodiment, the FSO terminal 32 generates and transmits multiple optical signals to the remote node 14 (and similarly receives and processes multiple optical signs from the remote node 14). In these embodiments, as described above, the FSO terminal 32 may use multiplexing (and demultiplexing) techniques such as wavelength division multiplexing (WDM) or dense wavelength division multiplexing (DWDM).

[0101] FIG. 4 shows a block diagram of the E-Band terminal 34, according to an embodiment. The E-Band terminal 34 includes a terminal controller 130, an E-Band modulator/demodulator (modem) 132, an E-Band RF processor 134, an E-Band antenna 136, and a terminal power unit 138. The E-Band terminal 34 interfaces with the switch/controller 30 via the terminal interface 42. It transmits a modulated E-Band signal over the RF channel 18 to the remote node 14. It also receives a modulated E-Band signal over the RF channel 18 that was sent from the remote node 14. In alternative configurations, different, and/or additional components may be included in FIG. 4. Furthermore, the components in the block diagram may be deployed in one or more physical devices and embodied in software, firmware, hardware, or any combinations thereof.

[0102] The terminal controller 130 is responsible for configuring and monitoring the E-Band terminal. It receives configuration commands from and provides status, performance, and alarm information to the node controller 70 via the management interface 90 portion of the terminal interface 42. The terminal controller 130 delivers configuration commands to and receives status, performance and alarm information from the E-Band modem 132 via a dedicated interface 140. The terminal controller 130 also provides E-Band management data, to be multiplexed into the transmitted data, to the E-Band modem 132 and receives E-Band management data, demultiplexed from the received data, from the E-Band modem 132 over the same dedicated interface 140. The terminal controller 130 delivers configuration commands to and receives status, performance and alarm information from the E-Band RF processor 134 via another dedicated interface 142.

[0103] The E-Band modem 132 is responsible for modulating a digital baseband carrier. In some embodiments, the E-Band modem 132 performs data processing functions, including framing, interleaving, and forward error correction (FEC) coding, prior to modulating the digital baseband carrier. Further, in some embodiments, the E-Band modem 132 employs quadrature amplitude modulation (QAM) to modulate digital baseband carrier. Further, in some embodiments, the E-Band modem 132 employs QAM of order ranging from 2 BPSK (one bit per symbol) to 128 QAM (7 bits per symbol). Further, in some embodiments, the E-Band modem performs adaptive coding, modulation and baud (ACMB) techniques to automatically adjust to link degradations due to weather. In some embodiments, the E-Band modem 132 modulates the baseband carrier at a data rate sufficient to transmit at least 10 Gbps of user data plus overhead data including management channel data and FEC overhead. In a second embodiment, the E-Band modem 132 modulates the baseband carrier at a data rate sufficient to transmit between 2.5 Gbps and 5 Gbps of user data plus overhead data including management channel data and FEC overhead. Further in the second embodiment, the E-Band modem 132 employs orthogonal frequency division multiplexing (OFDM) modulation techniques to improve the E-Band links' tolerance to multipath effects.

[0104] The modulated digital baseband carrier is delivered to the E-Band RF processor 134 via a digital baseband interface 146.

[0105] The E-Band modem 132 is also responsible for equalizing and demodulating the received digital baseband signal provided by the E-Band RF processor 134. The received digital baseband signal is provided by the E-Band RF processor 134 to the E-Band modem 132 via interface 146.

[0106] In some embodiments, the E-Band modem 132 performs data processing functions, including de-framing, de-interleaving, and forward error correction (FEC) decoding, after demodulating the digital baseband signal. Further, in some embodiments, the E-Band modem 132 employs quadrature amplitude modulation (QAM) to demodulate the digital baseband signal. Further, in some embodiments, the E-Band modem 132 employs QAM demodulation of order ranging from 2 BPSK (one bit per symbol) to 128 QAM (7 bits per symbol). Further, in some embodiments, the E-Band modem performs adaptive coding, modulation and baud (ACMB) techniques to automatically adjust to link degradations due to weather. In some embodiments, the E-Band modem 132 demodulates the digital baseband signal at a data rate sufficient to receive at least 10 Gbps of user data plus overhead data including management channel data and FEC overhead. In a second embodiment, the E-Band modem 132 demodulates the baseband carrier at a data rate sufficient to receive between 2.5 Gbps and 5 Gbps of user data plus overhead data including management channel data and FEC overhead. Further in the second embodiment, the E-Band modem 132 employs orthogonal frequency division multiplexing (OFDM) demodulation techniques to improve the E-Band links' tolerance to multipath effects.

[0107] The E-Band modem 132 accepts data to be transmitted from the switch/controller unit 30 via the data interface of the terminal interface 42. It also accepts E-Band management data from the terminal controller 130 and then multiplexes the management data into the transmit data stream prior to modulation.

[0108] The E-Band RF processor 134 up-converts the digital baseband signal provided by the E-Band modem 132 via interface 146, shifting the signal from baseband to a high center frequency and then amplifies the result prior to transmission (E-band transmit signal). The E-Band RF processor also amplifies and down-converts the receive E-Band signal from a high center frequency to baseband (baseband receive signal) prior before passing it to the E-Band modem 132. The E-Band RF processor 134 accepts the baseband transmit signal from the E-Band modem 132 and delivers the baseband receive signal to the E-Band modem 132 via digital baseband interface 146. After amplification, the E-Band transmit signal is sent by the E-Band RF processor 134 through the E-Band antenna 136 toward the remote node 14 via an RF interface 148. Similarly, the E-Band RF processor 134 first accepts the receive E-Band signal from the remote node 14 through the E-Band antenna 136 via the RF interface 148.

[0109] In some embodiments, the E-Band RF processor 134 up-converts the baseband transmit signal to a center frequency between 71 GHz and 86 GHz (the E-Band). Further, in some embodiments, the E-Band RF processor 134 down-converts the receive signal from a center frequency between 71 GHz and 86 GHz (the E-Band) to baseband. Further, in some embodiments, either the E-Band RF processor 134 up-converts the baseband transmit signal to center frequency between 71 GHz and 76 GHz and down-converts the receive signal from a center frequency between 81 GHz and 86 GHz, or the E-Band RF processor 134 up-converts the baseband transmit signal to center frequency between 81 GHz and 86 GHz and down-converts the receive signal from a center frequency between 71 GHz and 76 GHz to baseband. The local node 12 and the remote node 14 are configured such that they each receive signals with center frequencies matching that of the other's transmit center frequency.

[0110] In some embodiments, transmit and receive frequencies are programmable.

[0111] In some embodiments, the E-Band Terminal 34 generates and transmits a single E-Band signal (an E-Band transmit signal) on the vertical polarization. In that embodiment, the E-Band Terminal 34 receives and processes a single E-Band signal (an E-Band receive signal) on the vertical polarization.

[0112] In another embodiment, the E-Band Terminal 34 generates and transmits a single E-Band signal (an E-Band transmit signal) on the horizontal polarization. In that embodiment, the E-Band Terminal 34 receives and processes a single E-Band signal (an E-Band receive signal) on the horizontal polarization.

[0113] In another embodiment, the E-Band Terminal 34 generates and transmits a single E-Band signal (an E-Band transmit signal) on the clockwise circular polarization. In that embodiment, the E-Band Terminal 34 receives and processes a single E-Band signal (an E-Band receive signal) on the clockwise circular polarization.

[0114] In another embodiment, the E-Band Terminal 34 generates and transmits a single E-Band signal (an E-Band transmit signal) on the counter-clockwise circular polarization. In that embodiment, the E-Band Terminal 34 receives and processes a single E-Band signal (an E-Band receive signal) on the counter-clockwise circular polarization.

[0115] In another embodiment, the E-Band Terminal 34 generates two independent E-Band transmit signals, as described above, each operating at up to 10 Gbps. The first of the two E-Band transmit signals is transmitted via the antenna on the horizontal polarization while the second of the two E-Band transmit signals is transmitted via the antenna on the vertical polarization. In this embodiment, the E-Band Terminal 34 receives and processes two E-Band receive signals, as described above, each operating at up to 10 Gbps. The first of the two E-Band receive signals is received via the antenna on the horizontal polarization while the second of the two E-Band receive signals is received via the antenna on the vertical polarization.

[0116] In another embodiment, the E-Band Terminal 34 generates two independent E-Band transmit signals, as described above, each operating at up to 10 Gbps. The first of the two E-Band transmit signals is transmitted via the antenna on the clockwise circular polarization while the second of the two E-Band transmit signals is transmitted via the antenna on the counter-clockwise circular polarization. In this embodiment, the E-Band Terminal 34 receives and processes two E-Band receive signals, as described above, each operating at up to 10 Gbps. The first of the two E-Band receive signals is received via the antenna on the clockwise circular polarization while the second of the two E-Band receive signals is received via the antenna on the counter-clockwise circular polarization.

[0117] FIG. 5 is a block diagram of the local node 12 and the remote node 14, in which the switch/controller units 30 and 50 are installed in sheltered locations 154 and 156 and the FSO terminals 32 and 53 and the E-Band terminals 34 and 54 are mounted on external structures 150 and 152, according to an embodiment. FIG. 6 is a block diagram similar to FIG. 5 except that the switch/controller units 30 and 50 are installed on the external structures 150 and 152, according to an embodiment. In alternative configurations, different, and/or additional components may be included in FIGS. 5 and 6.

[0118] The switch/controller 30 is a stand-alone integrated subsystem. In some embodiments, the switch/controller is a rack-mountable device that can be installed in a telecommunications equipment rack in a sheltered environment 154, such as an equipment room, equipment cabinet, or equipment hut, in or near the structure 150 on which the terminals are installed, as shown in FIG. 5. In another embodiment, the switch/controller 12 is enclosed in a weather-proof enclosure and mounted on the structure 150 near the two terminals, as shown in FIG. 6.

[0119] The FSO terminal 32 and the E-Band terminal 34 are each a stand-alone integrated subsystem. Each is enclosed in a weather-proof enclosure and mounted, using terminal mounts 36 and 38, on a structure 150 with a clear line-of sight to the remote node 14 installed on the remote structure 152. The structures 150 and 152 may be buildings, telecommunication towers, or other structures suitable for such use. The remote structure 152 may be of the same type as or may differ from the local structure 150.

[0120] In some embodiments, the FSO terminal 32 and the E-Band terminal 34 are co-located to each other. For example, the terminals may be up to 10 feet apart from each other. Furthermore, while the FSO terminal 32 and the E-Band terminal 34 are mounted to the same structure 150 in FIGS. 5 and 6, the terminals may be mounted to separate structures.

[0121] The terminal mounts 36 and 38 provide azimuth and elevation adjustment to allow each terminal to be accurately pointed at the remote node 14 during installation. In some embodiments, the terminal mount 36 used for the FSO terminal 32 is identical to the terminal mount 38 used for the E-Band terminal 34. In an alternate embodiment, the terminal mount 38 used for the E-Band terminal 34 includes an active, automatic pointing and tracking system to maintain accurate pointing at the remote node 14.

[0122] While embodiments described with reference to FIGS. 1-5 only include the local node 12 and a remote node 14, the nodes may be integrated into a network of nodes. For example, the remote node 14 may be coupled to a third node that receives data from the remote node 14 and transmits the data to a fourth node. For example, the management interface 24 and the network interface 22 of the remote node 14 are connected to a switch controller of the third node. Alternatively, the remote node 14 and the third node are integrated together such that the switch controller 50 is a switch controller for the remote node 14 and the third node. In these embodiments the switch controller 50 may be coupled to another FSO terminal and E-Band terminal that are directed towards the fourth node.