Automatic network node relay link configuration tool

The implementation of the relay configuration tool may lead to the rapid deployment of relay links between network nodes. The tool may receive identification information of a donor network node that provides backhaul access to a core network, as well as identification information of a remote network node that is to use the backhaul. The tool may further obtain node information on the donor network node and the remote network node from a node information database based on the identification information. The tool may additionally receive link specifications for a relay link to be established between the network nodes. Accordingly, the tool may determine the communication frequencies and a power level for the relay link based at least on the node information and the link specifications. The communication frequencies and the power level, along with other configuration parameters, may be used by the tool to establish the relay link.

BACKGROUND

A wireless telecommunication carrier may deploy network nodes to multiple locations to provide continuous network coverage and communication services to customers. A network node may be linked to the core network of the wireless telecommunication carrier by a backhaul. The backhaul is a wired connection, such as a fiber optics link, that transports telecommunication and data communication traffic between the network node and the core network. However, in some instances, it may be infeasible to equip a network node with a wired backhaul to the core network as a result of geographical features, distance to the core network, or the cost of deploying a wired connection. In such instances, a wireless relay link may be established between a network node that is without a wired backhaul and a network node that is equipped with the wired backhaul to the core network. In this way, the network node with the wired backhaul may leverage the wired backhaul of the other network node to exchange telecommunication and data communication traffic with the core network.

The wireless relay link between two network nodes may be implemented with the installation of microwave communication equipment at both network nodes. The microwave equipment for a network node may include an outdoor unit (ODU) and/or an indoor unit (IDU). The ODU may be connected to a microwave antenna, and is responsible for radio frequency (RF) signal processing, the conversion of intermediate frequency (IF) signals to RF signals, and vice versa. The IDU may be responsible for performing dispatch, multiplex/demultiplex, and modulation/demodulation of communication signals. The configuration of a wireless relay link between two network nodes may be a time consuming and difficult task. For example, the configuration may involve the manual input of multiple configuration parameters into the IDUs and/or ODUs of two network nodes in order to establish the relay link between two network nodes.

DETAILED DESCRIPTION

This disclosure is directed to techniques for implementing a relay configuration tool that automatically generates configuration settings for the network nodes of a wireless telecommunication carrier. The network nodes may include a donor network node that is able to access a wired backhaul connecting to a core network of the wireless telecommunication carrier. For example, the donor network node may be a network node that is directly connected to a core network via the wired backhaul or an intermediate relaying network node that is one or more network node links away from the network node with the wired backhaul to the core network. The network nodes may further include a remote network node that lacks wired backhaul access to the core network. The configuration settings generated by the relay configuration tool may configure the wireless communication equipment of each network node to establish a relay link between the remote network node and the donor network node. Accordingly, the relay link may enable the remote network node to use the wired backhaul access of the donor network node to exchange telecommunication and data communication traffic with the core network.

In various embodiments, the relay configuration tool may automatically determine the communication frequencies and the power level of the relay link to be established. The determination may be made based on the node information of the donor network node and the remote network node, as well as the frequency information for the relay link that is to be established. In at least one embodiment, the node information may be retrieved from a node information database. The relay configuration tool may further determine the configuration settings for the donor and remote network nodes based on inputted configuration parameters for the relay link. The determined communication frequencies, power level, and configuration settings may serve as the basis for the generation of configuration files for the donor and remote network nodes by the relay configuration tool. Accordingly, the relay configuration tool may transmit the configuration files to the donor and remote network nodes. In turn, the configuration files may be implemented by the donor and remote network nodes to establish the relay link, such as a microwave communication link, between the network nodes.

The implementation and use of the relay configuration tool may automate the configuration of a relay link between a donor network node and a remote network node. The automatic determination of communication frequency and the power level for the relay link to be established, as well as the configuration settings for the network nodes that implement the relay link, may enable the configuration of the relay link in near real time. In contrast, conventional techniques for configuring a relay link between a network node and a recipient node may be a time consuming and procedurally complicated task. For example, the average time for configuring a relay link via the relay configuration tool is in the neighborhood of five minutes. In contrast, the average time for the manual configuration of a relay link between network nodes without the benefit of the relay configuration tool may be as long as nearly an hour.

Accordingly, the implementation of the relay configuration tool may lead to the rapid deployment of relay links between donor network nodes and remote network nodes. Such rapid deployment may lead to faster wireless communication network expansion to geographical locations that are previously unserved or underserved by a wireless telecommunication carrier. As such, the implementation of the relay configuration tool may help to decrease in the amount of network coverage problems that are experienced by subscribers, as well as reduce the number of calls to customer care of the wireless telecommunication carrier. The implementation of the relay configuration tool may also reduce the labor cost associated with the expansion or improvement of the wireless telecommunication network. The techniques described herein may be implemented in a number of ways. Example implementations are provided below with reference to the following figures.

Example Network Architecture

FIG. 1illustrates an example architecture100for deploying a network node relay link configuration tool. The architecture100may include a wireless communication network102. The wireless communication network102may include a core network104, as well as multiple network nodes, such as the network nodes106(1) and106(2). The network nodes are responsible for handling voice and data traffic between user devices, such as a user device108, and the core network104. The user device108may be a smart phone, a feature phone, a tablet computer, or another portable communication device. The core network104may provide telecommunication and data communication services to the user devices. For example, the core network104may connect the user device108to other telecommunication and data communication networks (including but not limited to the Internet).

The network node106(1) may be connected to the core network104via a wired backhaul110. However, the network node106(2) may have no wired backhaul connection with the core network104. Each of the network nodes106(1) and106(2) may be equipped with wireless communication equipment for the wireless exchange of communication data between the network nodes. In some embodiments, the wireless communication equipment may be microwave communication equipment. There may be two models for the deployment of wireless communication equipment at the network nodes. In a split mount deployment model, the wireless communication equipment of a network node may include an outdoor unit (ODU) and an indoor unit (IDU). The ODU may be connected to a microwave antenna, and is responsible for radio frequency (RF) signal processing, the conversion of intermediate frequency (IF) signals to RF signals, and vice versa. The IDU may be responsible for performing dispatch, multiplex/demultiplex, and modulation/demodulation of communication signals. For example, the network node106(1) may be equipped with an ODU112and an IDU114, while the network node106(2) may be equipped with an ODU116and an IDU118. However, in an all-outdoor deployment model, a network node may have an ODU but lacks an IDU. In such a deployment model, the ODU may additionally provide the same functionalities as an IDU, and no IDU is present in the network node.

The architecture100may further include a relay link configuration engine120. The relay link configuration engine120may execute on one or more computing devices122. The computing devices122may include general purpose computers, such as desktop computers, tablet computers, laptop computers, servers, and so forth. However, in other embodiments, the computing devices122may include smart phones, game consoles, or other electronic devices that are capable of receiving inputs, processing the inputs, and generating output data. In various embodiments, the computing devices122may be operated by a wireless telecommunication carrier or a third-party entity that is working with the wireless telecommunication carrier.

The relay link configuration engine120may generate configuration settings for the network nodes106(1) and106(2). The configuration settings may be generated based on data that is received from one or more information databases124and user inputs126from a user. The user inputs126may include network node identification information, relay link configuration parameters, frequency information, network node configuration parameters, and/or so forth. The configuration settings may configure the wireless communication equipment of the network nodes to establish a relay link128between the network nodes. The relay link128may enable the network node106(1) to act as a donor network node and the network node106(2) to act as a remote network node. Accordingly, the network node106(2) may use the wired backhaul110of the network node106(1) to exchange telecommunication and data communication traffic with the core network104.

In various embodiments, the relay link configuration engine120may determine the communication frequencies and the power level of the relay link128to be established. The determination may be made based on the node information of the network nodes106(1) and106(2), as well as the inputted frequency information for the relay link128that is to be established. In at least one embodiment, the node information may be retrieved from a node information database. The node information database may be a proprietary database that is controlled by a wireless communication carrier that operates the wireless communication network102. The relay link configuration engine120may further determine the configuration settings for the network nodes106(1) and106(2) based on configuration parameters for the relay link. In various embodiments, the configuration parameters may include site classification information for the network nodes, link protection information for the relay link, frequency polarization information, communication slot prioritization information, port setting information, relay link identification information, wayside (in-band management) information, and/or so forth.

Subsequently, the relay link configuration engine120may generate configuration files for the network nodes106(1) and106(2) based on the determined communication frequency, power level, and configuration settings. For example, the relay link configuration engine120may generate the configuration file130for the network node106(1), and the configuration file132for the network node106(2). The configuration files130and132, respectively, are then transmitted by the relay link configuration engine120to the network nodes106(1) and106(2) via a network134. The network134may include a local area network (LAN), a larger network such as a wide area network (WAN), the wireless communication network102, and/or the Internet. Upon receiving a corresponding configuration file, each of the network nodes106(1) and106(2) may configure its wireless communication equipment according to the settings in the configuration file. The configuration files130and132may enable the network nodes106(1) and106(2) to establish the relay link128between the nodes.

Each configuration file may provide configuration updates to a network node. In at least some embodiments, the configuration updates may be real-time configuration updates. The configuration updates may comprise command line interface (CLI) scripts, simple network management protocol (SNMP) put statements, and/or other programming inputs. The configuration updates may be implemented by an IDU or an ODU of a network node using software-defined networking (SDN) features and/or functions. For example, the real-time configuration updates may be performed via orchestration using technologies such as ConfD, Tail-f, network configuration protocol (NETCONF), and/or so forth. In an instance in which the network node is a split mount network node, the configuration file may be implemented by the IDU of the network node. However, in an instance in which the network node is an all-outdoor network node, the configuration file may be implemented by the ODU of the network node.

In alternative embodiments, the network node106(2) may act as a relay node for another network node, such as network node106(N), that also lack wired backhaul access to the core network104. The network node106(N) may be an all-outdoor network node that is equipped with an ODU136but lacks an IDU. In such embodiments, the relay link configuration engine120may generate configuration files138and140that enable the establishment of a relay link142between the network node106(2) and the network node106(N). The relay link configuration engine120may transmit the configuration file138to the network node106(2) for implementation, and the configuration file140to the network node106(N) for implementation, in order to establish the relay link142. In this way, the network node106(N) may use the relay link142and the relay link128to leverage the wired backhaul110. Accordingly, the network node106(N) may exchange telecommunication and data communication traffic with the core network104without a dedicated wired backhaul to the core network104. Other alternative embodiments may enable the establishment of a relay link between two relay nodes in a similar manner, in which the relay nodes are intermediate nodes in a node chain that connects a remote network node to a donor network node.

Example Computing Device Components

FIG. 2is a block diagram showing various components of one or more illustrative computing devices that implement the network node relay link configuration tool. The one or more computing devices122may include a communication interface202, one or more processors204, memory206, and hardware208. The communication interface202may include wireless and/or wired communication components that enable the computing devices to transmit data to and receive data from other networked devices. The hardware208may include additional hardware interface, data communication, or data storage hardware. For example, the hardware interfaces may include a data output device (e.g., visual display, audio speakers), and one or more data input devices. The data input devices may include, but are not limited to, combinations of one or more of keypads, keyboards, mouse devices, touch screens that accept gestures, microphones, voice or speech recognition devices, and any other suitable devices.

The processors204and the memory206of the computing devices122may implement an operating system210and the relay link configuration engine120. The operating system210may include components that enable the computing devices122to receive and transmit data via various interfaces (e.g., user controls, communication interface, and/or memory input/output devices), as well as process data using the processors204to generate output. The operating system210may include a presentation component that presents the output (e.g., display the data on an electronic display, store the data in memory, transmit the data to another electronic device, etc.). Additionally, the operating system210may include other components that perform various additional functions generally associated with an operating system.

The relay link configuration engine120may include a data input module212, a database interface module214, a configuration module216, a script module218, and a data output module220. The modules may include routines, program instructions, objects, and/or data structures that perform particular tasks or implement particular abstract data types. The memory206may also include a data store222that is used by the relay link configuration engine120. In various embodiments, the relay link configuration engine120may be a standalone application or a web-based application.

The data input module212may receive data that are inputted by a user via application user interfaces. The application user interfaces may be presented via the standalone application or a web browser executing on a computing device. The data may include manually inputted information that are used to by the relay link configuration engine120to establish a relay link between two network nodes. For example, the data may include relay link configuration parameters, frequency information, site classification information for the network nodes, link protection information for the relay link, frequency polarization information, communication slot prioritization information, port setting information, relay link identification information, wayside (in-band management) information, and/or so forth. The two network nodes may include a donor network node and a remote network node, such as the network node106(1) and the network node106(2).

The database interface module214may interface with one or more information databases124. The information databases124may include a node information database that store node information regarding each network node. The node information for a network node may include network node site information, a network node address, virtual local area network (VLAN) identifier, Internet protocol (IP) address, subnet mask, gateway IP, IDU count, site type, any other VLAN identifiers, and/or so forth. The network node site information may include identification of a cluster donor, an immediate donor, a primary VLAN port number, etc., for the network node. The IDU count may indicate the number of IDUs at the network node. The information databases124may further include databases that store regulatory information that govern wireless telecommunication, such as rules governing the provisions of frequencies, channels, power levels for the establishment of relay links between network nodes.

The configuration module216may use algorithms to analyze the relevant user inputs126and the data obtained from the information databases124in order to generate configurations for the relay links. The algorithms may include logical statements, data arrays, lookup tables, validation routines, and/or other application code. In various embodiments, the algorithms may enable the configuration module216to determine communication frequencies and a power level for a relay link based on node information retrieved from a node information database and link specifications that are inputted by a user. The configuration module216may further use the algorithms to determine the configuration settings for a pair of network nodes that establish the relay link based on configuration parameters that are inputted by the user.

In various embodiments, the inputted configuration parameters may include site classification information for the network nodes, link protection information for the relay link, frequency polarization information, communication slot prioritization information, port setting information, relay link identification information, wayside (in-band management) information, and/or so forth. Accordingly, the configuration module216may use such information to populate RF specifications, enable and or disable Ethernet ports, select IP addresses, as well as determine other configuration settings for the network nodes that are involved in the establishment of the relay link. The configuration module216may use the data input module212and the database interface module214to query and receive the appropriate data at each stage of analysis.

Accordingly, the configuration module216may generate configurations for a remote network node and a donor node that is directly connected by a wired backhaul to the core network. In other embodiments, the configuration module216may generate configurations for one or more intermediate devices, such as intermediate network node or intermediate routers, in order to automate the implementation of a node chain that provide an end-to-end communication path for a remote network and the core network. In such embodiments, the configuration module216may generate updates to routing tables, VLAN databases, ports, and/or so forth. The port updates may include updates to port speed, port duplexing settings, port auto-negotiation settings, port descriptions, and/or so forth.

The script module218may generate configuration files for the implementation of a relay links between network nodes based on configurations provided by the configuration module216. A configuration file for a network node may include frequency and power link settings of a relay link to be established, configuration settings for the network node, and/or other relay link-related settings that are generated by the configuration module216. Each configuration file may provide configuration updates to a network node. In at least some embodiments, the configuration updates may be real-time configuration updates. The configuration updates may comprise CLI scripts, SNMP put statements, and/or other programming inputs. The configuration updates may be implemented by an IDU or an ODU of network node using SDN features and/or functions. For example, the real-time configuration updates may be performed via orchestration using technologies such as ConfD, Tail-f, NETCONF, and/or so forth. Accordingly, the configuration files may be processed by the IDUs or ODUs of the network nodes to implement the relay links. For example, an application program interface (API) provided by a command execution application of an IDU may be called by the script module218to receive a configuration file and implement the configuration updates that are in the configuration file.

The data output module220may generate the various application user interfaces that are configured to receive data inputs and display information to a user. The application user interfaces may include interfaces that request identification information of network nodes, link specifications of relay links to be established, configuration parameters of the network nodes that are involved in the establishment of relay links, and/or so forth. The application user interfaces may also include user interfaces that present information retrieved from the information databases124, verification dialogue boxes, relay link configuration results, configuration error messages, help information, configuration file management menus, and/or so forth. The configuration file management menus may enable a user to create, save, modify, and delete configuration files, as well as transmit the configuration files to the various network nodes for implementation.

The data store222may store data that are processed or generated by the relay link configuration engine120. The data store222may include one or more databases, such as relational databases, object databases, object-relational databases, and/or key-value databases that store data. For example, data stored in the data store222may include node information224, link specifications226, frequency and power settings228, configuration parameters230, configuration settings232, configuration files234, and/or other information. Additional details regarding the functionalities of the modules in the relay link configuration engine120are discussed in view ofFIGS. 3-8. Further, the relay link configuration engine120may include other modules that perform the functionalities described in the context of these figures.

Example User Interfaces

FIGS. 3-6illustrate user interfaces that may be presented by the relay link configuration engine120for the implementation of a relay link between two network nodes. For the purpose of this illustration, the implementation of the relay link is discussed in the context of wireless communication equipment that are manufactured by Ceragon Networks, Ltd. of Tel Aviv, Israel. Such wireless equipment may include the FibeAir IP-10 series of high capacity wireless backhaul equipment. However, the relay link configuration engine120may provide similar user interface for the configuration of other types of wireless backhaul equipment, including ODUs and/or IDUs, as manufactured by Ceragon Networks Ltd., as well as manufactured by other companies.

FIG. 3is an illustrative user interface300presented by a network node relay link configuration tool for obtaining information on network nodes that are involved in the establishment of a relay link. The user interface300may include a “Site A ID” field302and a “Site Info” button304. A user may enter a network node identifier of a network node that is closest to the core network (104) hub site, also may be known as an alternative access vendor hub site, into “Site A ID” field302. In various embodiments, the AAV hub site may be a network node that has a dedicated wired backhaul that connects to the core network104of the wireless communication network102. The user interface300may further include a “Remote Site ID” field306and a ‘Site Info” button308. A user may enter a network node identifier of a network node that is the remote network node into the “Remote Site ID” field306. The user interface300may further include a VLAN information section310and a RF link specifications section312.

Upon entry of a network node identifier in the “Site A ID” field302, the user may select the “Site Info” button304to cause the configuration module216to validate the identifier, as well as retrieve node information associated with the identifier from a node information database. Accordingly, the configuration module216may generate the illustrative dialogue box402shown inFIG. 4.

As shown inFIG. 4, the illustrative dialogue box402may include Site A information404, microwave donor information406, the microwave recipient information408, cluster donor information410, immediate donor information412, primary VLAN information414, and a record status416. The site A information404may show a street address at which the network node is located. The microwave donor information406may indicate whether the network node is a donor network node. In various embodiments, only AAV hub sites may be set as donor network nodes. The cluster donor information410may indicate the AAV hub site identifier for a network node cluster that includes the network node having the identifier entered in the “Site A ID” field302.

The immediate donor information412may indicate the immediate upstream donor network node for the network node having the identifier entered in the “Site A ID” field302. For example, as shown in the dialogue box402, the network node “6FM1020A” may be the cluster donor as well as the immediate donor, which means that the network node “6FM1168B” is one hop away from an AAV hub site. The primary VLAN information414may indicate the primary access VLAN for the network node having the identifier entered in the “Site A ID” field302. This information may be populated into the VLAN information section310of the user interface300.

The record status416may indicate a status of the information as retrieved from node information database and displayed in the dialogue box402. For example, the statuses of the information may include “Current,” “Proposed Complete”, “Proposed Incomplete,” these statuses may indicate that the retrieved information is ready for use by the relay link configuration engine120. However, a status of “Historical” may indicate that the retrieved information is outdated and unsuitable for use by the relay link configuration engine120. The user may use the acknowledgment button420to acknowledge the validation and dismiss the dialogue box402.

Returning toFIG. 3, upon entry of a network node identifier in the “Remote Site ID” field306, the user may select the “Site Info” button308to cause the configuration module216to validate the identifier, as well as retrieve node information associated with the identifier from a node information database. Accordingly, the configuration module216may generate the illustrative dialogue box422shown inFIG. 4.

Once again, as shown inFIG. 4, the illustrative dialogue box422may present information for the recipient donor network node in a similar manner as described with respect to the dialogue box402. However, the immediate donor information424indicates a network node identifier that is identical to the identifier of the network node shown in the site A information404of the dialogue box402. For example, as shown in the dialogue box422, the immediate donor is “6FM1168B,” which matches the information that is shown in the site A information404. The user may use the acknowledgment button426to acknowledge the validation and dismiss the dialogue box422.

Returning toFIG. 3, following the validation of the identifiers of the two network nodes that are entered into the “Site A ID” field302and the “Remote Site ID” field306, respectively, the user may activate the load site data button314of the user interface300. In response, the configuration module216may query the node information database in order to perform a multitude of functions. The functions may include confirming that the two network nodes are directly connected while identifying the network node types of network node, such as AAV hub, relay node, recipient node, and/or so forth. The number of IDUs installed at each network node, as well as the number of existing relay links that are sourced or terminated at each network node may be determined. The functions may further include the identification of VLANs for the “Site A” network node and all downstream network nodes. For example, the primary access VLAN identifiers may be automatically populated into the VLAN information section310of the user interface300. Further, in some instances, algorithms may be used to identify additional VLANs to be created automatically by the configuration module216when the configurations are exported to fulfill the relay link design criteria of a wireless communication carrier. However, in additional instances, VLANs with other port assignment values may be created automatically by the configuration module216to fulfill the relay link design criteria of other wireless communication carriers.

Additionally, the local access VLANs for each of the two network nodes may be identified. In at least one instance, the identified local access VLANs may be tailored to meet the relay link design criteria of a wireless communication carrier. In one example, the identified local access VLANs may be assigned to specific port, such as port 3, of the IDUs of the two network nodes. In other examples, the identified local access VLANs may be assigned to other ports of the IDUs of the two network nodes, such as port 4. Accordingly, the network node IDUs IPs, subnet mask, gateway IPs, IDU counts, node type, VLAN identifiers, as well as other data, may be auto-populated into the individual IDU user interfaces, such as the IDU user interfaces illustrated inFIGS. 5 and 6.

In one illustrative example, the functions performed by the configuration module216may generate the following commands:a. adding in all VLANs into the IDUs:cd/interfaces/ethernet/bridgevlan <WXYZ> addvlan <XYZ> addb. remove all VLANs from all Ethernet ports:set-allowed-vlans remove <WXYZ>set-allowed-vlans remove <XYZ>c. adding appropriate VLANs to the clodu service router (CSR) facing interface port 3:cd/interfaces/ethernet/bridge/eth-port[3]set-allowed-vlans add <WXYZ>set-allowed-vlans add <XYZ>d. add system location and link information (some information may be updated later):cd/platform/set system-name <SITE_ID NODAL IDENTIFIER>set slot-label <SITE A ID-REMOTE SITE ID_NODE NAME>set system-location <SITE ID>e. add system trap information (some information may be updated later and each radio may have unique values):cd/management/mng-protocols/snmp/set trap-clli[1]<SITE_ID NODE NAME>set trap-clli[2]<SITE_ID NODE NAME>f. add system location and link information (some information may be updated later and the information may vary based upon if network node has nodal enclosures):cd/platform/set system-name <SITE ID NODAL IDENTIFIER>set slot-label <SITE A ID-REMOTE SITE ID NODE NAME>set system-location <SITE ID>

The RF link specifications section312may include controls for specifying the configuration parameters for the relay link between the two network nodes identified in the “Site A ID” field302and the “Remote Site ID” field306. In various embodiments, the RF link specifications section312may include a RF link band control316, a multi-rate multi-channel (MRMC) script profile control318, an adaptive coding and modulation (ACM) mode control320, a maximum ACM profile control322, a reference class control324, a minimum ACM profile326, a radio frequency unit (RFU) type control328, and a maximum transmission level control330. As shown, the controls may be in the form of dropdown boxes. However, the controls may be implemented using alternative forms in other embodiments, such as via radio buttons, checkboxes, etc.

The RF link band control316may include options such as 6 GHz, 11 GHz, 18 GHz and 23 GHz, and/or so forth. Typically, the further the distance between the IDUs of the two network nodes, the lower the frequency band that is employed. For example, a 30-miles separation between two IDUs may correlate with frequency band deployment in the 6 GHz range, whereas a one-mile separation may correlate with frequency band deployment in the 23 GHz range.

The MRMC script profile control318may enable the selection of predetermined RF design options that specify the allocation of transmission rates and transmission channels for the relay link. In at least one embodiment, the profiles may include profiles for performing adaptive modulation. Accordingly, if an ACM profile is selected, the ACM mode control320may become available for use. The RFU type control328may be used to select the RF unit type. For example, RFU-C may be selected for typical microwave deployments, while RFU-HP may be selected for longer range microwave deployments that use higher powers to establish relay links. The maximum transmission level control330may be used to control the maximum transmission power level for the relay link between the two network nodes. In various embodiments, the maximum transmission power level may be changed to suit the frequency band of the relay link, the quadrature amplitude modulation (QAM) type of the relay link, the RFU type, and/or other factors.

The ACM mode control320may be used to select either “acm-fixed-mode” or “acm-adaptive-mode”. If the “adaptive” mode is selected, the reference class control324, the minimum ACM profile326, and the maximum transmission level control330may become available for use. In various embodiments, the reference class control324, the minimum ACM profile326, and the maximum transmission level control330may enable settings to be designated per the RF design chosen via the MRMC script profile control318. Subsequently, assuming all information is entered correctly, the user may activate the next button332.

The configuration module216may perform various functions based on the configuration parameters inputted via the RF link specifications section312of the user interface300. In some embodiments, the transmit frequency and the receive frequency on the user interface500shown inFIG. 5may be dynamically updated based on the configuration parameters. In such embodiments, the configuration module216may build an array of paired transmit and receive frequencies based on a RF link band and a MRMC script file that are selected. The transmit frequencies and the receive frequencies may be paired together according to Federal Communications Commission (FCC) rules. Accordingly, when a user selects a transmit frequency on the user interface500, the receive frequency may be automatically populated based on the array. Further, the configuration module216may use an algorithm to defined the available maximum transmit powers that are available for a user to select based on the RF band, ODU type, and the modulations for the relay link. The algorithm may include if/then statements that match particular power settings to particular parameters. For instance, the maximum transmit power for a 6 GHz relay link using a HP ODU at 16 QAM may be different than a 23 GHz link using RFU-C at 256 QAM. Additionally, the radios of the two network nodes may be automatically configure for media access control (MAC) header compression. Thus, the following example RF radio settings may be configured by the configuration module216:/radio/mrmc/change-script-cmd <ACM PROFILE-LINK CAPACITY-RF CHANNEL SIZE-ADAPTIVE MODE-MAXIMUM PROFILE-ADAPTIVE POWER-REFERENCE CLASS-MINIMUM PROFILE>cd/radio/rfuset tx-freq <TRANSMIT FREQUENCY>set rx-freq <RECEIVE FREQUENCY>set max-tx-level <TRANSMIT POWER OUTPUT>cd/radio/framerset link-id<LINK PASSWORD>cd/radioset mhc-admin enable
Additionally, the configuration module216may present the user interface500following the configuration of the RF radio settings.

FIG. 5is an illustrative user interface500presented by a network node relay link configuration tool for configuring parameters for a IDU at a network node that is closest to an AAV hub site. The IDU at the network node that is closest to the AAV hub site may be referred to as “IDU A”. In various instances, the network node that is equipped with the IDU A may be a donor network node. The user interface500may include a site type control502, a link protection control504, an IDU order control506, a polarization control508, an element ID field510, a site ID field512, an IP address control514, trap manager controls516, a transmit frequency control518, port type controls520, a port assignment control522, and a wayside control524. In the context of the user interface500, controls in the form of dropdown menus may be substituted with other functionally equivalent controls in other embodiments.

The configuration module216may determine the site type via a query to node information database and pre-populate the site type control502. Accordingly, the site type control502may be greyed out since the control selection may be sourced from an analysis of the node information database. In one example, the site types may include the following:i. core access service site —a site router will be installed at the network node;ii. core site —no site router or cell service will be installed at the network node;iii. relay service site—a site router will be installed at the network;iv. relay site —no site router or cell service will be installed at this network node.

If the site type is “core site”, the user may select an AAV network interface device (NID) termination port on an initial IDU. Regardless of whether such an IDU is the first or the last IDU being installed at the network node, the user may select which port the AAV is terminated into on the initial IDU. Such information may asset the configuration module216to determine which ports are to be enabled on the new IDU for this network node.

For the link protection control504, the user may select the type of link that the network nodes will employ to interconnect. Link protection refers to providing a radio link with redundancy, such that the failure of one radio component does not cause the failure of the radio link. The “1+1” and “2+0” options may call for multiple IDU IPs to be assigned via the node information database. For example, the “1+1” option refers to a radio configuration in which each IDU involved in a relay link has two separate modems, and each modem is connected to its own independent ODU. In other words, the relay link actually uses two sub-links in a single radio spectrum which one link is considered active and the second link is in standby mode. The “2+0” option refers to a similar configuration in which both of the two sub-links are active. If there is an insufficient number of IDU IPs in the node information database, then the configuration module216may prevent the user from setting the link protection for the network node. If the user selects “2+0” for the link protection, the configuration module216may automatically pre-check the remote network node to confirm that a sufficient number of IDU IPs are available in node information database. If there is an insufficient number of IDU IPs, the user may be prompted to update the node information database so that additional IDU IPs are assigned.

In at least one scenario, the link protection options may include: (1) 1+0; (2) 1+1; (3) 1+0 with nodal; (4) 1+1 with nodal; and (5) 2+0 with nodal, in which “1+0” is an option for no link redundancy/link protection. However, the link protection options may include any option up to an “8+0” link in other embodiments. For example, the relay link may further include a “2+2” link, a “4+0” link, “4+4” link, or a “8+0” link with or without a nodal The “with nodal” refers to a configuration in which the multiple radios of a network cell are interconnected with a backplane link. For example, a nodal may be an enclosure that is equipped with a backplane, such that the radios are interconnected by the backplane when they are mounted into the enclosure. In another example, the nodal that provides the backplane link between the radios may be pre-built into a modular chassis that houses the radios.

Accordingly, the link protection control504may be used to determine the type of RF link between two network nodes. Such a determination by the configuration module216may also automatically update the link protection for a remote IDU, such as an IDU at the remote network node. For instance, a “2+0” link on IDU A will remove all link protection menu options except for “2+0” while a “1+x” type link on the IDU A may remove the “2+0” option at the remote IDU.

In various embodiments, the configuration module216may automatically determine the number of IDUs at a network using the node information database. Further, the configuration module216may also identify the number of IDU IPs assigned in the node information database. The IDU order control506may enable a user to select the placement of a new IDU into the site. For nodal installations, “1+1” and “2+0” installations may be restricted to slots 1 and 2, 3 and 4, or 5 and 6, with the constraint that the lower IDU slot is to be an odd number. Once these controls are configured, the ports 1-7 may be enabled and disabled automatically by the configuration module216.

The polarization control508may be used for 2+0 links, in which the polarizations are listed by lower/upper IDU slot placements. For example, a 2+0 link using “H/V” equates to a non-XPIC link, with the lower slotted IDU using horizontal polarization and the upper slotted IDU using vertical polarization. Since the link is non-XPIC, each IDU/ODU pair may have its own separate transmit and receive frequency configurations. The element ID field510may enable the input of a microwave element ID for the network node. For example, the element ID may include eight characters with the characters “MW.” The configuration module216may automatically populate the site ID information into the site ID field512.

The IP address control514may enable the user to select an IP address via a drop down menu. Further, the default gateway and subnet mask information may be pre-populated by the configuration module216. However, for IDUs in nodal slots 3-6, the IP fields (e.g., IP address, subnet, gateway, etc.) may be greyed out because no IP configurations are required for these slots. The trap manager controls516may enable the user to modify the order of the trap managers.

The transmit frequency control518may enable a user to select a suitable transmit frequency, which may be a high value or a low value. In turn, the corresponding receive frequency may be dynamically updated to match the frequency pair. Accordingly, the transmit frequency and receive frequency drop down menus may be pre-populated with RF link specific data from the RF link specifications section312. As such, the user is not permitted to independently modify the receive frequency. In order to change the receive frequency, the user may change the transmit frequency via the transmit frequency control518.

The port type controls520may enable the specification of port type on ports 1 and 2, which may be either optical or electrical, such as a RJ45 port. For distributed antenna system (DAS) network nodes, the user may manually enable the ports based on network node design, despite the fact that by default all of the interfaces are disabled. The port assignment control522may enable the setting of ports based on relay link design. For example, ports 1, 2, and 8 are essentially VLAN trunked ports. In most cases, the user may configure more than one VLAN to those ports if the ports are enabled. For the port connecting to a router, the user may configure one drop down VLAN for this port. For ports 1, 2 and 8, there may be multiple drop down options that correlate to the VLAN options in the VLAN information section310. Accordingly, the configuration module216may automatically determine the Ethernet ports that are enabled for modification by the user and the ports that are disabled, thus preventing improper modification or use in the field. The wayside control524may be configured according to the type of IDU connection at the remote network node. For example, if the IDU connects to a relay only IDU (i.e., no cellular or router at the remote network node), the user may change the wayside control524to enabled.

Accordingly, the configuration module216may perform the following example tasks based on the parameters inputted at the user interface500of the relay link configuration engine120. For instance, for all “1+1” and “2+0” type links, the configuration module216may create IDU configuration settings for the individual network nodes associated with the relay link. The configuration settings may include the information below as well as information to synchronize each pair of IDUs into a protected link pair. An example for a “2+0” link in a nodal enclosure may be as follows:cd/platform/mate-idu/set protection-admin 2+0-hsbcd/platform/shelf-manager/logon-unit 2cd/platform/mate-idu/set protection-admin 2+0-hsbcd/platform/mate-idu/copy-to-mate-cmd

For a “2+0” link, if cross-polarization interference cancellation (XPIC) is used, then the configuration module216may implement a XPIC MRMC script to inform the radios of the network nodes of the XPIC usage. Accordingly, the updated MRMC script may be the following:/radio/mrmc/change-script-cmd XPIC <ACM PROFILE-LINK CAPACITY-RF CHANNEL SIZE-ADAPTIVE MODE-MAXIMUM PROFILE-ADAPTIVE POWER-REFERENCE CLASS-MINIMUM PROFILE>

The configuration module216may configure each individual port with the required VLAN, Ethernet, and QoS settings. For example, with respect to Ceragon IP-10s that have T1 time-division multiplexing (TDM) ports, the configuration module216may disable all T1 ports. Further, if a wayside channel is enabled, the configuration module216may automatically enable Ethernet ports 4 and 5 configured the ports for the wayside cross-connect. The configuration module216may automatically determine the number of management ports for the implementation of the relay link. Additionally, the network time protocol (NTP) Server IP address may be determined automatically by a SQL query depending upon odd or even site VLANs. In one example, the determination may be made by performing an initial parsing, performing a mathematical calculation with respect to the VLANs, and parsing additional information to get the actual NTP Server IP address as follows:“Select (SELECT CASE WHEN ([Primary_vlan] % 2)< >0 THEN ‘51.’+(CAST((PARSENAME([default_gateway_CSR_IP],3)−128) AS varchar(10)))+‘0.255.1’ ELSE ‘51.’+(CAST((PARSENAME([default_gateway_CSR_IP],3)−128) AS varchar(10)))+‘0.255.2’ END) AS NTPaddress FROM [S_DATA].[dbo].[vw_S_DATA_MICROWAVE_DATA] WHERE Sites_in_cluster=”+siteIDquery”
wherein S_DATA is a reference to the node information database. Thus, the configuration module216may create the following example configuration settings in the form of CLI commands:set/management/networking/ip-address/ip-address <IP ADDRESS>cd/management/networking/ip-address/set subnet-mask <SUBNET MASK>set default-gateway <GATEWAY ADDRESS>cd/management/networking/set number-of-ports <NUMBER OF MANAGEMENT PORTS>cd/management/mng-protocols/snmp/set version v2cset trap-admin[1] enableset trap-manager[1]<TRAP MANAGER #1 IP ADDRESS>set trap-heartbeat[1] 0set trap-clli[1]<SITE ID NODE NAME>set trap-community[1] PolyviewTraps01set trap-admin[2] enableset trap-manager[2]<TRAP MANAGER #2 IP ADDRESS>set trap-heartbeat[2] 0set trap-clli[2]<SITE ID NODE NAME>set trap-community[2] PolyviewTraps02cd/management/mng-services/time-service/ntpset admin enableset server 51.54.255.1cd/interfaces/ethernet/bridge/eth-port[<PORT NUMBER>]set connector-type <CONNECTOR TYPE>set admin <PORT STATUS>set auto-negotiation <OFF/ON>set interface-alias <INTERFACE DESCRIPTION>set-allowed-vlans remove <REMOVE ALL UNNECESSARY VLANS IDS>set-allowed-vlans add <ADD ALL NECESSARY VLAN IDS>set qos-classify-initial vlan-pbitsset qos-classify-default 1stset qos-scheduling-scheme all-queues-strictcd/interfaces/pdh/port-group/disable-all-portscd/interfaces/pdh/trails/del-all-trailscd/interfaces/wayside/setadmin <DISABLE/ENABLE>set capacity wide

Subsequently, for a relay link deployment that is a microwave deployment, the user may activate the next button526. However, if the deployment is a DAS deployment, the user may activate the export file button528. Following the activation of the export file button528, the script module218may generate a configuration file that encapsulates the configuration settings for each IDU at a network node that is closest to an AAV hub site.

FIG. 6is an illustrative user interface600presented by a network node relay link configuration tool for configuring an indoor unit (IDU) of a remote network node to establish a relay link. The configuration module216of the relay link configuration engine120may present the user interface600. In various embodiments, the user interface600may be presented in response to the activation of the next button526. The user interface600may be used to configure a remote network node, such as a remote network node that is to benefit from the establishment of a relay link with a network node that is closest to an Alternative Access Vendor (AAV) hub site. In the context of the user interface600, controls in the form of dropdown menus may be substituted with other functionally equivalent controls in other embodiments.

The user interface600may include a site type control602, a link protection control604, an IDU number field606, an IDU order control608, a polarization control610, an element ID control612, a site ID field614, an IP address control616, the trap manger control618, frequency fields620, the port type controls622, the port assignment control624, and the wayside control626. The site type control602may enable a user to select the site type of the remote network node. In one example, the site types may include the following:i. recipient site —a site router will be installed at siteii. relay service site —a site router will be installed at siteiii. relay site —no site router or cell service will be installed at this siteiv. DAS site —a high density site with multiple separate sites local to the IDU.

The link protection control604enables the selection of the type of link that the two network nodes may employ to interconnect. The “1+1” and “2+0” options may require that multiple IDU IPs to be assigned via the node information database. If there is an insufficient number of IDU IPs in the node information database, then the configuration module216may not allow the user to set the site for the link protection. If the user selects “2+0” for the link protection, the configuration module216may automatically pre-check the remote site to confirm that enough IDU IPs are available in the node information database. If there is an insufficient number of IDU IPs, the user may update the node information database so that additional IDU IPs are assigned. For example, the link protection options may include: (1) 1+0; (2) 1+1; (3) 1+0 with nodal; (4) 1+1 with nodal; and (5) 2+0 with nodal, in which “1+0” is an option for no link redundancy/link protection. However, the link protection options may include any option up to an “8+0” link in other embodiments.

The number of IDUs that are listed in the IDU number field606may be determined automatically by the configuration module216via the node information database. Additionally, the configuration module216may identify the number of IDU IPs assigned via node information database. The IDU order control608may enable a user to select the placement of the new IDU into the site. For example, with respect to nodal installations, “1+1” and “2+0” installations may be restricted to the use of slots 1 and 2, 3, and 4, or 5 and 6 with the constraint that the lower IDU slot is to be an odd number. Once these controls are configured, the ports 1-7 may be enabled and disabled automatically by the configuration module216.

The polarization control610may be automatically populated by the configuration module216based on the polarization that was selected via the polarization control508of the user interface500. The element ID control612may enable the input of a microwave element ID for the network node. For example, the element ID may include eight characters with the characters “MW.” The site ID field614may be pre-populated by the configuration module216. The IP address control616may be enable the selection of an IP address. The selection may be made via a drop down menu or another functionally equivalent user interface control. However, for IDUs in nodal slots 3-6, the IP fields (IP, subnet, gateway, etc.) may be greyed out because no IP configurations are required for these slots. Further, the default gateway and subnet mask information may be pre-populated by the configuration module216. The trap manager controls516may enable the user to modify the order of the trap managers.

The transmit frequency and the receive frequency in the frequency fields620may be pre-populated by the configuration module216based on the frequency input entered into the transmit frequency control518of the user interface500. Accordingly, any changes to the frequency values in the frequency fields620may only be performed via the transmit frequency control518of the user interface500.

The port type controls622may enable the specification of port type on ports 1 and 2, which may be either optical or electrical, such as a RJ45 port. The port assignment control624may enable the setting of ports based on relay link design. For example, ports 1, 2, and 8 are essentially VLAN trunked ports. In most cases, more than one VLAN is to be configured to those ports if the ports are enabled. For the port connecting to a router, only one VLAN may be configured for such a port. For ports 1, 2 and 8, there may be multiple drop down options that correlate to the VLAN options in the VLAN information section310. The wayside control626may be configured according to the type of IDU connection at the remote network node. For example, if the IDU connects to a relay only IDU (i.e., no cellular or router at the remote network node), the wayside control524may be configured automatically so that the associated ports are enabled.

The configuration module216may generate configuration settings for the remote network node based on the configuration parameters inputted and/or displayed on the user interface600. In various embodiments, the configuration settings may be in the form of CLI commands. Following the activation of the export file button628, the script module218may generate a configuration file that encapsulates the configuration settings for each IDU at the remote network node.

Example Processes

FIGS. 7 and 8present illustrative processes700and800for using a network node relay link configuration tool to configure a relay link between two network nodes. Each of the processes700and800is illustrated as a collection of blocks in a logical flow chart, which represents a sequence of operations that can be implemented in hardware, software, or a combination thereof. In the context of software, the blocks represent computer-executable instructions that, when executed by one or more processors, perform the recited operations. Generally, computer-executable instructions may include routines, programs, objects, components, data structures, and the like that perform particular functions or implement particular abstract data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described blocks can be combined in any order and/or in parallel to implement the process. For discussion purposes, the processes700and800are described with reference to the architecture100ofFIG. 1.

FIG. 7is a flow diagram of an example process700for generating configuration files for a donor network node and a remote network node. At block702, the relay link configuration engine120may receive identification information of a donor network node that provides backhaul access to a core network of a wireless communication carrier. In various embodiments, the donor network node may be a network node that is closest to an Alternative Access Vendor (AAV) hub site. For example, the donor network node may be a core access service site, a core site, a relay service site, or a relay site.

At block704, the relay link configuration engine120may receive identification information of a remote network node that is to use the backhaul access provided by the donor network node. In various embodiments, the remote network node may use the backhaul access to exchange telecommunication and data communication traffic with the core network. For example, the remote network node may be a recipient site, a relay service site, a relay site, or a DAS site.

At block706, the relay link configuration engine120may obtain node information on the donor network node and the remote network node from a node information database based on the identification information of the nodes. The node information of a network node that is retrieved from the node information database may include network node site information, a network node address, virtual local area network (VLAN) identifier, Internet protocol (IP) address, subnet mask, gateway IP, an IDU count, any other VLAN identifiers, and/or so forth.

At block708, the relay link configuration engine120may receive link specifications for a relay link that is to be established between the donor network node and the remote network node. In various embodiments, the link specifications may include a link frequency band, a MRMC script profile to be applied, ACM mode parameters, a RFU type setting, and a maximum transmission level parameter. The MRMC script profile may be a predetermined RF design option that specifies the allocations of transmission rates and transmission channels for the relay link.

At block710, the relay link configuration engine120may determine communication frequencies and a power level for the relay link based on the node information on the network nodes and the link specification. The communication frequencies may include a transmit frequency and a receive frequency. The transmit frequency and the receive frequency may be paired together according to FCC rules. Further, the power level may be defined based on the RF band, ODU type, and modulations for the relay link.

At block712, the relay link configuration engine120may receive configuration parameters for the donor network node and the remote network node. In various embodiments, the configuration parameters may include site classification information for the network nodes, link protection information for the relay link, frequency polarization information, communication slot prioritization information, port setting information, relay link identification information, wayside information, and/or so forth. The configuration parameters may include parameters that are inputted by a user and/or parameters that are automatically pre-populated by the relay link configuration engine120based on previously received configuration settings.

At block714, the relay link configuration engine120may determine the configuration settings for the donor network node and the remote network node based on the configuration parameters. In various embodiments, the relay link configuration engine120may perform the determination by processing the configuration parameters via logical statements, data arrays, lookup tables, validation routines, and/or other application code. In some embodiments, the configuration settings as generated by the relay link configuration engine120may include CLI commands. The configuration settings for a network node may be generated for the IDU of the network node when the network node is a split mount network node. Alternatively, the configuration settings for the network node may be generated for the ODU of the network node when the network node is an all-outdoor network node.

At block716, the relay link configuration engine120may generate configuration files for the donor network node and the recipient network node. Each of the configuration files may include the communication frequencies and the power level for the relay link to be established, as well as the configuration settings for the IDU or the ODU of a network node.

At block718, the relay link configuration engine120may provide the configuration files to the donor network node and the remote network node. In turn, the IDU or the ODU at each of the donor network node and the remote network node may implement the configuration files to establish the relay link.

FIG. 8is a flow diagram of an example process800for determining the configuration settings for a network node. The process800may further illustrate block714of the process700. At block802, the relay link configuration engine120may store site classification information for a network node. In various embodiments, the network node may be a donor network node or a remote network node. Accordingly, for a donor network node, the site classification may include a core access service site, a core site, a relay service site, or a relay site. For a remote network node, the site classification may include a recipient site, a relay service site, a relay site, or a DAS site.

At block804, the relay link configuration engine120may store link protection information for the relay link to be established between the network node and the additional network node. Link protection refers to providing a radio link with redundancy, such that the failure of one radio component does not cause the failure of the radio link. In various embodiments, the link protection setting for the relay link may include: (1) 1+0; (2) 1+1; (3) 1+0 with nodal; (4) 1+1 with nodal; or (5) 2+0 with nodal.

At block806, the relay link configuration engine120may store the frequency polarization information for the relay link that is to be established between the network node and the additional network node. For example, a 2+0 link using “H/V” equates to a non-XPIC link, with the lower slotted IDU using horizontal polarization and the upper slotted IDU using vertical polarization.

At block808, the relay link configuration engine120may store information on the communication slot prioritization for an IDU of the network node. For example, with respect to nodal installations at the network node, “1+1” and “2+0” installations may be restricted to the use of slots 1 and 2, 3, and 4, or 5 and 6 with the constraint that the lower IDU slot is to be an odd number.

At block810, the relay link configuration engine120may store port setting information that configures the network node to establish the relay link. For example, ports may be set as either optical or electrical. Further, ports 1, 2, and 8 may be VLAN trunked ports. In most cases, more than one VLAN is to be configured to those ports if the ports are enabled. For the port connecting to a router, only one VLAN may be configured for such a port. For ports 1, 2 and 8, there may be multiple drop down options.

At812, the relay link configuration engine120may store the identification information for the relay link to be established between the network node and the additional network node. In various embodiments, the identification information may include one or more identifiers that uniquely identifies the relay link. For example, each of the identifiers may be in the format of an eight character string.

At block814, the relay link configuration engine120may store the wayside (in-band management) information for the network node. Wayside may be configured according to the type of IDU connection at the remote network node. For example, if the IDU connects to a relay only IDU (i.e., no cellular or router at the remote network node), wayside may be configured automatically so that the associated ports are enabled. At block816, the relay link configuration engine120may determine the configuration settings for the network node based on the stored information regarding the network node. In various embodiments, the configuration settings may be determined for the IDU or the ODU of the network node.

The implementation of the relay configuration tool may lead to the rapid deployment of relay links between donor network nodes and remote network nodes. Such rapid deployment may lead to faster wireless communication network expansion to geographical locations that are previously unserved or underserved by a wireless telecommunication carrier. As such, the implementation of the relay configuration tool may help to decrease in the amount of network coverage problems that are experienced by subscribers, as well as reduce the number of calls to customer care of the wireless telecommunication carrier. The implementation of the relay configuration tool may also reduce the labor cost associated with the expansion or improvement of the wireless telecommunication network.

CONCLUSION