Methods and apparatus are provided for registering an unanticipated node into an ad-hoc network. A communication channel is dedicated as the link between a registry within the network and unanticipated nodes. The dedicated communication link typically comprises primary and secondary frequencies in the RF spectrum. An unanticipated node can be registered “on-the-fly” via the dedicated communication link by identification, authentication, and non-repudiation. The unanticipated node can then interoperate with the network via a standard communication protocol.

TECHNICAL FIELD

The present invention generally relates to network interoperability, and more particularly relates to “on the fly” registration of nodes in an ad-hoc network environment.

BACKGROUND

The interoperability of computer systems and devices is generally a prerequisite for successful communication between systems and devices within a network, and also within a system of networks. Communication networks are currently used in a wide range of applications, including consumer, commercial, government and military, among others, and can range in complexity from relatively simple to highly complex. A few examples of complex communication networks are the Internet, Homeland Security, and military command and control systems.

As computer technology continues to evolve, the perceived ideal of universal interoperability between systems and devices becomes an increasingly desirable objective. The ongoing proliferation of communication devices, such as Personal Digital Assistants (PDAs), robotics, software-defined radios, unmanned aerial vehicles and the like, offers numerous opportunities and challenges for communication interoperability applications. In a battlefield environment, for example, a soldier equipped with a PDA could benefit significantly from target-related information supplied by a remote source such as an unmanned aerial vehicle, or from instructions relayed from a command and control center, in addition to other relevant information from a communication network. In order for this type of coordinated information gathering and distribution to be successful, however, the diverse categories of systems and devices within a communication network must be generally compatible with interoperability standards.

An information based network with a high degree of interoperability between remote assets (nodes) and one or more command and control nodes can be designated a network-centric operation (NCO). In general, an NCO represents the ability of geographically separated entities (nodes) to share information efficiently, to collaborate on tasks, and to synchronize actions within a network-centric environment. For a mobile NCO environment, as for example in a battlefield situation, the ability of a command and control node to interoperate with diverse remote nodes is typically enabled by an a-priori registration in a local network registry of anticipated remote nodes. For a truly dynamic (ad-hoc) mobile network capability, however, it would be advantageous to enable a remote node to enter the NCO environment without an a-priori arrangement. That is, the overall flexibility of an NCO could be significantly enhanced if an unanticipated remote node could enter the NCO environment by registering with the network “on the fly”.

Accordingly, it is desirable to provide methods and apparatus to enable a node to enter a network without a-priori registration. In addition, it is desirable that an “on the fly” registration include identification, authentication, and non-repudiation of the entering node during the registration process. Furthermore, other desirable features and characteristics of the present invention will become apparent from the subsequent detailed description and the appended claims, taken in conjunction with the accompanying drawings and the foregoing technical field and background.

BRIEF SUMMARY

According to various exemplary embodiments, devices and methods are provided for entering a node into a network environment without a-priori registration. One exemplary method comprises the steps of allocating a communication channel to act as a dedicated link between the entering node and the network registry, registering the node via the dedicated communication channel link, and deploying the node to interoperate within the network environment. In this embodiment, the allocating step typically comprises dedicating selected primary and secondary frequency channels within the Radio Frequency (RF) spectrum, such as in the Ultra High Frequency (UHF) band. The registering step in this embodiment typically comprises identification, authentication, and non-repudiation of the entering node. Moreover, the deploying step typically comprises scanning, detecting and negotiating the node services via a standard communication protocol such as TCP/Ipv4, for example.

An exemplary embodiment of a network for accommodating the “ad-hoc” registration of an unanticipated node typically comprises a registry within the network and a dedicated communication channel configured to link the network registry with the unanticipated node. In this embodiment, an unanticipated node is registered “on-the-fly” via the dedicated communication channel link, and the unanticipated node is thereafter deployed to interoperate within the network. The dedicated communication channel is typically comprised of a primary frequency and a secondary frequency selected within the Radio Frequency (RF) spectrum, such as in the Ultra High Frequency (UHF) band. The primary frequency is typically used to facilitate connectivity, discovery, routing, registration, and service negotiation. The secondary frequency is typically configured to facilitate overflow and back-up functions.

The “on-the-fly” registration of the unanticipated node with the exemplary network typically comprises identification, authentication, and non-repudiation of the unanticipated node. The subsequent deployment of the unanticipated node to interoperate with the other nodes in the network typically comprises scanning, detecting and negotiating the node services via a standard communication protocol such as TCP/IPv4, for example.

DETAILED DESCRIPTION

Various embodiments of the present invention pertain to the area of interoperability of computer systems and devices in a network environment. In a typical network-centric operation (NCO), for example, the anticipated remote nodes are generally pre-registered in a local network registry in order to be authenticated before communicating with other nodes (e.g., command and control) in the network: In the case of a dynamic mobile NCO such as a complex military network, the pre-registration requirement can be cumbersome and time-consuming, and will typically limit the flexibility of an ad-hoc type of communication network. Therefore, a scheme for “on-the-fly” node registration is disclosed herein that can enable an unanticipated node to enter an NCO type of network environment without a-priori registration.

One example of a conventional NCO configuration100is illustrated inFIG. 1. In this example, a headquarter node102can be designated as the command and control center for NCO100. Headquarter (HQ) node102can be in direct communication with a satellite104that is typically configured to provide target and/or other types of surveillance information to headquarter node102, and to suitably interlink with other ground and/or air-based nodes such as an unmanned aerial vehicle (UAV) node106. UAV node106may be configured as a domain services node in order to provide a common domain pre-registration directory service for the known (anticipated) nodes in the network. Such anticipated nodes can include, for example, an unmanned ground vehicle (UGV) node108, a group collaboration node110in the form of a suitably equipped HUMVEE, and a soldier in the field with a personal digital assistant (PDA), as represented by node112. In theFIG. 1example, UGV node108is in direct communication with UAV node106, while PDA node112is in indirect communication with UAV node106via HUMVEE node110. In a conventional network such as NCO100, all anticipated nodes are typically pre-registered by the network manager(s) in a common domain registry, as provided by UAV node106in this example.

In general, the pre-registration process involves communication connectivity, frequency coordination, mission planning, and interoperability. For example, in a typical stovepipe communications network such as SATCOM, which can include fixed and mobile nodes, there is generally a known network topology and there are typically network management systems that require a-priori planning before deploying a mission. The a-priori (pre-registration) process can be lengthy and tedious, since it can involve the predetermination of numerous factors, such as frequency coordination, route planning, orbit planning, encryption, time synchronization, and node addressing, as well as others.

In an NCO network operational environment, however, the conventional pre-registration process may not be suitable for a rapidly changing network topology. For example, the dynamic mobility of certain types of nodes can make it difficult to maintain their respective addresses and locations. Any last-minute changes among wireless communication devices in a network can adversely affect the maintainability of frequency coordination and connectivity, for example, and may necessitate communication of last-minute changes to all participants in the network. As communications networks become more complex and more dynamic, the limitations of the conventional pre-registration process can become unacceptable for applications such as a military theater of operation.

A simplified functional scenario can serve to illustrate the interoperability of the pre-registered nodes in NCO100, as depicted inFIG. 1. In this scenario example, Command and Control (HQ node102) receives data from satellite node104via a suitable wireless link114regarding the location of a ground-based target (not shown). Since HQ node102can communicate with UAV node106via satellite node104and a suitable wireless communication link116, HQ node102can access the registry in UAV node106to determine the identity, location, mission capability, availability, and/or other characteristics of the pre-registered assets (nodes) in NCO100. In this example, HQ node102may determine that UGV node108has the mission capability and location to engage the ground-based target with a relatively high degree of success. For a conventional network such as NCO100as noted above, UGV node108can be assumed to have pre-registered with UAV106via a suitable communication link118. Similarly, it can be assumed that HUMVEE node110has pre-registered with UAV node106via a suitable communication link120, and that PDA node112has pre-registered with UAV node106via a suitable communication link122to HUMVEE node110and via communication link120to UAV node106.

In the illustrative scenario of NCO100, UGV node108is typically controlled remotely by PDA node112via HUMVEE node110and UAV node106in order to take advantage of the ground observation capability of the soldier at PDA node112. HQ node102can then send mission instructions to PDA node112via satellite node104, UAV node106and HUMVEE node110. In accordance with the received mission instructions, the soldier at PDA node112can activate an appropriate weapon on UGV node108by communicating via HUMVEE node110and UAV node106. Moreover, UGV node108may be equipped with sensors (e.g., video cameras) that can provide image or other types of data back to the soldier at PDA node112(via UAV node106and HUMVEE node110). Similarly, UGV node108may provide image or other types of data back to HQ102via UAV106and satellite104.

The scenario described above encompasses a group of interoperable, pre-registered nodes functioning interactively in one type of network-centric application; that is, in a military/battlefield environment. The network-centric concept, however, can also be implemented in many other types of network applications, such as homeland security, commercial, industrial, medical, academic, and the like. For some types of network-centric applications, however, the a-priori registration of all anticipated nodes can be a significant limitation to network flexibility. As noted above, in a mobile battlefield NCO, for example, it may not be feasible to anticipate and pre-register every potentially useful asset. Moreover, the typically time-consuming a-priori registration process may not be compatible with the ad-hoc type of dynamic environment envisioned for optimal interoperability. Therefore, a mechanism for entering a node into an NCO environment without a-priori registration can significantly expand the flexibility and versatility of the network.

According to an exemplary embodiment of an ad-hoc implementation (NCO200) of NCO environment100, as depicted inFIG. 2, an unanticipated node202can be entered into NCO200without a-priori registration. Node202may be a manned aircraft, a satellite, a joint services command, or any other type of asset capable of communicating with the other nodes in NCO200, which are shown inFIG. 2as the same pre-registered nodes as inFIG. 1. To enable node202to register “on-the-fly”, a dedicated communication channel204is typically configured as an ad-hoc registration link between an unanticipated entering node such as202and the network registry in UAV node106. That is, communication channel204enables the network registry to perform identification, authentication, and non-repudiation of an entering node (202) during the ad-hoc registration process. The exemplary embodiment of communication channel204described herein will be designated as “Net-Centric Coordination Channel” (NCC).

One exemplary embodiment of NCC204can be configured as a coordination channel configured with primary and secondary communication frequencies within the Radio Frequency (RF) spectrum. This coordination channel (NCC204) is typically an open channel that is dedicated within NCO200to accommodate only mobile ad-hoc (on-the-fly) node registrations in an analogous manner to the use of VHF/UHF radio guard channels for emergency communications. For example, in certain types of military NCO applications, the NCC204coordination channel primary and secondary frequencies would generally be fixed within the UHF spectrum, since the UHF band is commonly used by the military for communicating between various platforms, such as handheld, vehicular, airborne, and maritime. Moreover, future planning for the software-defined radio technology typically includes the UHF band as an embedded waveform for communication. The UHF band is usually well suited for military applications because the behavior of radio signals in this frequency spectrum is generally well understood. However, it will be appreciated that the NCC concept described herein can be applied to other frequency spectra as well, depending on the criteria for a particular application.

In one exemplary embodiment, the primary frequency (f1) of NCC204can be used to facilitate initial connectivity, discovery, routing, registration, and service negotiation of an ad-hoc node, and the secondary frequency (f2) of NCC204can be used to facilitate overflow and back-up functions. That is, if there are many nodes trying to log on in a mobile ad-hoc environment, primary frequency f1may become temporarily unavailable. In this case, an entering node could automatically switch over to secondary frequency f2as a back-up. This type of redundancy feature can be particularly useful in a mission-critical situation such as a battlefield.

An exemplary NCC204may be configured to use various data rates and standard communication protocols as appropriate for the application. For example, a vehicular node might gain access using a 64 kbps data rate while a handheld operator node may only have the capability of a 10 kbps throughput. As such, it is desirable for an exemplary NCC204to be configured for a broad range of data rates. Similarly, with regard to network communication protocols, an exemplary NCC204can be configured to use the current Transmission Control Protocol/Internet Protocol v4 (TCP/IPv4), and can be further configured to have a migration capability for emerging systems such as IPv6, where nodes can generally communicate across a network independent of the types of physical links present in the network. Moreover, an exemplary NCC204will generally support a Best Effort level of Quality of Service (QoS).

Typically, the NCC204concept disclosed herein will impact the physical and data link layers of a standard communication model such as OSI. That is, the interfacing of an exemplary NCC204will typically occur within the physical and data link layers, including the establishment of connectivity, an initial data link, registry, discovery, authentication, and the like. Once an initial registration is achieved using NCC204, an ad-hoc entering node such as202can begin to interoperate with other nodes in NCO200by switching over to an operational frequency and using a matching communication standard. This type of ad-hoc registration process is more fully described below in conjunction with the flow diagram ofFIG. 3.

InFIG. 3, an “on-the-fly” registration process300begins in step302with a decision by a node (e.g.,202) to join an existing network (e.g.,200) in which the node had not been anticipated or pre-registered. It is assumed that node202has a specific IP address, has the appropriate communications frequency capability (e.g., UHF), and also possesses the security and authentication features required to access network200. If the decision in step302is “yes”, node202initializes the appropriate characteristics for joining the network (step304), such as those noted above. Node202can then make contact with network200by switching to the primary frequency of NCC204(step306) and connecting with the network registry (e.g., UAV node106). As noted above, if primary frequency f1of NCC204is unavailable, node202can switch to secondary frequency f2.

In step308, node202enters the registration process by discovering the necessary mission logon information, as well as the authentication, security, and configuration requirements of the network registry. In step310, node202completes the registration process by communicating the required authentication and security information to the network registry (e.g., to UAV node106via NCC204). Finally, in step312, node202can be deployed by switching over to the operational frequency of NCO200to enable communication interoperability with the other nodes in NCO200. This communication interoperability can be implemented through scanning, detecting and negotiating node202services via a standard communication protocol.

Accordingly, the shortcomings of the prior art have been overcome by providing an improved registration procedure for nodes connecting with a network. A Net-Centric Coordination Channel (NCC) concept is disclosed herein that provides a mobile ad-hoc network environment with a mechanism to allow nodes that were previously not included in pre-planned missions to join the network in a truly ad-hoc manner. That is, unanticipated nodes can be enabled to register with a network “on-the-fly”. As such, these nodes (assets) can be deployed without requiring pre-registration with the network manager. The disclosed NCC concept can provide a dedicated communication link between an entering node and a network registry in order to allow the registry to perform identification, authentication, and non-repudiation of the node during the registration process.