# Patent

## Title
Secure fallback network device

## Abstract

A network device and method may provide secure fallback operations. The device includes a port allowing the device to communicate with a network and a processor to generate a security credential, provide the security credential to a call manager during initialization, and provide the security credential to a secondary device during fallback operations. The network device may include a memory to store the security credential and routing information for fallback operations.

## Background
CROSS REFERENCE TO RELATED APPLICATIONS DATA
This application is a continuation under 35 U.S.C. §120, of U.S. patent application Ser. No. 12/981,385, filed Dec. 29, 2010, and entitled “Secure Fallback Network Device,” which is a continuation of copending U.S. application Ser. No. 10/940,105, filed Sep. 13, 2004, and entitled “Secure Fallback Network Device,” now U.S. Pat. No. 7,886,344, issued Feb. 8, 2011 herein incorporated by reference.


BACKGROUND
It is becoming more common for enterprises to employ a wide area network (WAN) to connect several smaller or branch offices to the main office. This is true for both data networks and voice networks. The smaller offices may rely upon the WAN connection to the main office for many types of services, including call management, routing and directory services. Typically, the call management, routing and directory service may be controlled by a central entity, referred to here as a call manager.
There may be several call managers coordinating different regions of the WAN, based upon enterprise function, geography, size, etc. In addition, the call manager functions may be distributed across several different network devices. No limitation upon implementation or configuration of a call management function is implied or intended by the use of the term ‘call manager.’
Issues may arise at the branch offices if the WAN becomes inoperative or loses communication. With the loss of the call manager, the branch office may not be able to make phone calls, in addition to losing their connections to the data networks. This is unacceptable for stable operations.
A solution to these issues may be referred to as ‘fallback’ operations. In fallback operations, a fallback device or devices have been designated to assume the functions of call manager during WAN failure. Secondary devices may contact the fallback device during fallback operations, and the fallback device will need to verify its identity. The secondary device may be a secondary call manager that is assuming operations from the primary call manager, or a network phone desiring fallback services. The phones or data network devices that will rely upon this fallback device are configured with this information by the call manager during normal WAN operation.
However, fallback operations have not previously encompassed secure operations, in which secure phones are listed in a list of trusted devices, on a scale broad enough to provide secure operations for larger operations.



BRIEF DESCRIPTION OF THE DRAWINGS
Embodiments of the invention may be better understood when reviewed in conjunction with the following drawings, in which:
FIG. 1 shows an example of a WAN having several smaller branch offices or LANs.
FIG. 2 shows an embodiment of a method of providing an authentication of a secure fallback device during initialization.
FIG. 3 shows an embodiment of a method of receiving an authentication of a secure fallback device during initialization.
FIG. 4 shows an embodiment of a method of authenticating a fallback device.
FIG. 5 shows an embodiment of a method of providing authentication to a secondary device.
FIG. 6 shows an embodiment of a secure fallback network device.



DETAILED DESCRIPTION OF THE EMBODIMENTS
FIG. 1 shows an example of a wide-area network (WAN) having several smaller, local-area networks (LANs). The WAN 10 provides the network devices, such as servers and routers, access to the call manager 12. As mentioned before, the entity performing the functions of the call manager may not be designated as such, and may even be merely a process or service running on an existing device central to the WAN. The call manager provides routing information, directory services and other network-related services to the network devices for the WAN.
The LANs 14a and 14b may represent smaller, branch offices of the overall enterprise, or may be other types of organizations within the enterprise. The phone 18a is a network phone, which may be device that appears similar to a traditional telephone, but uses a data network connection for voice data, or it may be a computer or workstation having a microphone, a sound card and a voice encoder, as examples. The phone allows users to place voice calls over the data network.
Voice over data network calls generally involve a user speaking into a handset or microphone that captures the audio signals digitally and then packetizes the signals and transmits them over a data network. This is far different than a public switched transmission network telephone call, but allows users to place calls using existing infrastructure of the enterprise and use available bandwidth on the data network, saving money.
As discussed above, a problem occurs when the connection between the LANs and the WAN fails, or the call manager goes off line. The network devices in the LAN that rely upon the call manager for operations no longer have the ability to function without the call manager. This is generally the scenario in which fallback operations commence. In fallback operations, a fallback device, such as a local network device picks up some of the functionality of the call manager to allow the local offices to remain functional. The fallback device has been configured with the necessary information to allow it to provide fallback operations.
For example, if either the call manager 12 failed, or the WAN 10 went down, the phone 18a would be disabled unless the fallback device 16a could provide fallback operations temporarily. This device, whether it is a fallback router, server or other device, will be referred to as the fallback device. The fallback device, up to this point, has not been able to handle large volumes of secure calls.
A secure call is one made between two endpoints that are both on a ‘trusted’ list, where both of them have been identified as secure devices. In some instances, the trusted list does not list all of the secure devices and in the volume of transactions that may occur, more secure devices than are on the list may be needed.
It is possible to configure network devices for fallback operations to include security elements, allowing secure calls to be made during fallback operations. A flowchart of an embodiment of a method for providing a security credential from a candidate secondary device is shown in FIG. 2. The network device that is capable of providing secure fallback operations is initialized at 20. Initialization may be at launching of a network, or addition of a new device to an existing network. The newly-initialized device connects with the call manager at 22 and authenticates communications at 24. These two processes may occur simultaneously or separately, depending upon the security protocol used for authenticating communications. An example is a security handshake with server authentication, such as under the Transport Layer Security (TLS) protocol promulgated by the Internet Engineering Task Force (IETF).
During the authentication process, or immediately after general authentication, the network device provides a security credential or certificate to the call manager at 26. The security credential could be one of many different types of credentials or certificates, including a digital signature, platform token, etc.
Referring now to FIG. 3, it can be seen that the call manager has processes that mirror those of the network device. The call manager detects initialization at 30, which may involve the network device contacting the call manager with a request for directory services, or another device in the network informing the call manager that there is a new network device. The call manager performs its portions of connecting and authenticating communications with the network device at 32 and 34. Once the call manager has received the certificate from the network device at 36, it now provides it to the relevant secondary device, where the secondary device may be a network phone or a secondary call manager, or any device that will contact the fallback device during fallback operations.
This process has assumed that the phones already exist in the network and that the network device is new. However, the process would be generally the same for new phones being configured with the certificate of an existing fallback device, the process of retrieving the certificate from the fallback device by the call manager would just occur at network start up. When new phones are added to the network that will use the network device for fallback operations, the call manager configures them with the certificate. Similarly, any secondary call managers that are added to the network and designated as the secondary call manager for the fallback operations will be updated with the certificates of fallback devices.
The secondary devices will store the certificate locally, so that upon failure of the WAN or the call manager, the secondary devices will have a way to ensure that the network device is secure. An embodiment of such a method for verifying a fallback device is shown in FIG. 4. At 40, the secondary detects the commencement of fallback operations. This may be the secondary device making this determination or the secondary device being notified of this by the fallback device, as examples. At 42, the secondary device retrieves the certificate from the fallback device. This may involve the secondary device actively retrieving it from the device, such as connecting to a particular port, or being provided the certificate from the fallback device.
At 44, the secondary device authenticates the certificate. Generally, this will involve the secondary device accessing the previously stored certificate and comparing it with the newly-provided certificate. The previously stored certificate may be in the configuration file of the phone, for example, or in the database of the secondary call manager. If the two certificates match, the secondary device can verify that the device presenting itself as the fallback device is indeed the fallback device designated for secure calls and may begin secure operations at 46.
The fallback device, for its part, will provide the certificate to the phones that have the fallback device designated for their secure operations, and any secondary call managers, to verify its identity. An embodiment of this is shown in FIG. 5. At 50, the fallback device detects commencement of fallback operations. As the fallback device is generally a router or other network device that interacts with the WAN, this would seem to be easily detectable. The fallback device may detect the commencement of fallback operations because it has received a secure routing or other traffic request from one of the phones assigned to it for fallback operations. Alternatively, if the onset of fallback communications is due to failure of the primary call manager, the fallback device may detect the onset of fallback operations when it is notified of such by the secondary call manager.
At 52, the fallback device provides its certificate to the secondary devices that request it. These secondary devices are generally identified to the fallback device, and the fallback device is generally designated as such for selected secondary devices, during normal network operations. The fallback device may provide its certificate as part of the initial contact between the secondary device and the fallback device.
The secondary device verifies the certificate and then acknowledges the authenticity at 54. There may be no explicit acknowledgement, but merely the start of secure routing or other traffic requests from the phone. In either case, the fallback device provides secure fallback operations at 56.
As mentioned previously, the fallback device may be a local device, such as fallback device 16a of FIG. 1. During normal network operations, the fallback device performs its functions as a normal network device, such as routing, providing services, etc. Upon the commencement of fallback operations, the network device would begin to provide some limited call manager-like services during fallback operations.
An example of such a network device is shown in FIG. 6. The network device 60 typically will have at least one port 70 to allow the device to communicate with the network. It may have more than one port, for example, if it is a routing device, there may be multiple ports allowing multiple devices to connect to it. There may also be a port designated for WAN operations and a port for LAN operations.
The network device will also generally have a processor 66 that will provide the credentialing service. The credentialing service 68 may generate a security credential, which may be the generation of the security credential upon configuration, or it may be retrieving a security credential provided in the device at manufacture. The processor may also handle communications with the call manager and ensure that the call manager is provided the security credential to a call manager during initialization.
In addition, the processor will also provide the security credential to the secondary device during fallback operations, where the secondary device is a network phone, or a secondary call manger as discussed above.
The network device may also comprise a memory 62 in which is stored the certificate. It must be noted that the certificate as stored or provided may be any type of security token, or representations of tokens. For example, it may be a platform token, a hash or shortened version of a platform token, a shared credential, a certificate, etc.
The fallback device may be an existing network device that has instructions executed by a processor. The fallback device may be implemented by instructions contained on an article of machine-readable media that, when executed, cause the machine to perform the methods of the invention. In this instance, the machine would be the fallback device, and the machine-readable instructions may be firmware or other software updates to the existing processor.
Thus, although there has been described to this point a particular embodiment for a method and apparatus to provide secure fallback operations, it is not intended that such specific references be considered as limitations upon the scope of this invention except in-so-far as set forth in the following claims.

## Claims

1. A fallback network device, comprising:
a port allowing the fallback device to communicate with a network; and
a processor to:
generate a security credential certificate;
authenticate with a call manager under a security protocol by providing the security credential certificate to the call manager; and
provide secure fallback operations when the call manager is unavailable,
wherein the fallback device is able to detect the commencement of the fallback operations.

2. The fallback device of claim 1, the fallback device further comprising a memory to store the security credential certificate and routing information for the secure fallback operations.

3. The fallback device of claim 1, the processor operable to generate a security credential certificate further comprising a processor to generate one selected from the group comprised of: a platform token and a shared credential.

4. The fallback device of claim 1, the fallback device further comprising a second port, wherein the port allowing communications with a network is a wide-area network port and the second port is a local area network port.

5. The fallback device of claim 1, wherein the fallback device is configured to detect commencement of the fallback operations by receiving a notification from the secondary call manager.

6. The fallback device of claim 1, wherein the fallback device is configured to provide the security credential certificate to the secondary call manager responsive to an initial contact between the fallback device and the secondary call manager.

7. The fallback device of claim 1, wherein the fallback device is configured to provide routing and network services during normal network operations.

8. The fallback device of claim 7, wherein the fallback device is configured to provide call manager-like services during the fallback operations.

9. A method of providing secure fallback operations, the method comprising:
authenticating a call manager under a security protocol by receiving a security credential certificate from a fallback network device phone;
assigning a network phone to the fallback device for fallback operations;
providing the security credential certificate to the network; and
storing the security credential certificate locally on the network phone.

10. The method of claim 9, further comprising performing secure fallback operations using the fallback device when the call manager is unavailable.

11. The method of claim 9, further comprising detecting commencement of fallback operations by receiving a traffic request from the network phone.

12. The method of claim 9, wherein the security credential certificate comprises a previously stored certificate on the network phone, the method further comprising:
retrieving a second security credential certificate from the fallback device;
comparing the second security credential certificate with the previously stored certificate; and
when the second security credential certificate matches the previously stored certificate, beginning secure fallback operations using the fallback device.

13. The method of claim 12, further comprising providing the second security credential certificate to the network phone during the fallback operations for comparison with the previously stored security credential certificate.

14. The method of claim 9, further comprising detecting commencement of fallback operations by detecting loss of connection with a wide-area network.

15. The method of claim 9, further comprising detecting commencement of fallback operations by receiving a message from the fallback device.