Switching Between Connectivity Types to Maintain Connectivity

Abstract

Techniques are provided for leveraging narrowband connectivity (such as dial-up communications or other types of low bandwidth communications) to provision or configure broadband connectivity between a broadband access provider and a broadband device, such as a DSL modem or a cable modem. Specifically, because narrowband connectivity does not require advance configuration or provisioning by the host system of connectivity parameters for an access-seeking device, a modem at an access-seeking device may be leveraged to establish a narrowband connection between that device and a host system and to enable an exchange or negotiation of connectivity parameters necessary to enable future broadband connectivity. Thus, once established, the narrowband connection may be used as a conduit for communicating required provisioning information between the broadband-enabling host and the access-seeking device to enable broadband connectivity by the device in the future.

1 . A method for enabling communications between a user system and an accessible system, the method comprising:
 detecting a communications failure in a communications session between a user system and an accessible system, the communications session leveraging a first connectivity type; and   establishing a second communications session between the user system and the accessible system, the second communications session leveraging a second connectivity type that differs from the first connectivity type, automatically in response to the detected communication failure on the session leveraging the first connectivity type.   
     
     
         2 . The method of  claim 1  wherein establishing the second communications session leveraging the second connectivity type, automatically in response to the detected communication failure comprises establishing a second communications session leveraging the second connectivity type, without requiring user manipulation in response to the detected communications failure on the session leveraging the first connectivity type. 
     
     
         3 . The method of  claim 1  wherein the first connectivity type comprises broadband connectivity. 
     
     
         4 . The method of  claim 1  wherein the second connectivity type comprises narrowband connectivity. 
     
     
         5 . The method of  claim 1  further comprising enabling the receipt, using the second communications session leveraging the second connectivity type, of connectivity information regarding one or more of the detected communications failure, status or problem of the first connectivity type, status or problem of the user system, and status or problem of the accessible system and status or problem of a communication pathway between the user system and the accessible system leveraging the first connectivity type. 
     
     
         6 . The method of  claim 1  wherein the accessible system comprises a secure system, the method further comprising enabling the receipt of authentication information from the user system when establishing the second communications session. 
     
     
         7 . The method of  claim 1  further comprising using a token to transparently establish the second communications session leveraging the second connectivity type such that at least one of the applications making use of the first communications session is unaffected by the interruption of the first communications session and the establishment of the second communications session. 
     
     
         8 . The method of  claim 1  further comprising:
 detecting availability of the first connectivity type for communications between the user system and the accessible system; and 
 establishing a third communications session between the user system and the accessible system, the third communication session leveraging the first connectivity type, automatically in response to the detected availability of the first connectivity type. 
 
     
     
         9 . The method of  claim 1  further comprising using a token to transparently establish the third communications session leveraging the first connectivity type such that at least one of the applications making use of the second communications session is unaffected by the interruption of the second communications session and the establishment of the third communications session. 
     
     
         10 . A method for enabling communications between a user system and an accessible system, the method comprising:
 using a communications session of a first connectivity type, between the user system and the accessible system; and   leveraging a second connectivity type to enable communication of connectivity information to the accessible system regarding the first connectivity type.   
     
     
         11 . The method of  claim 10  wherein the communications session is established automatically in response to a detected communication failure of another communications session leveraging the first connectivity type. 
     
     
         12 . The method of  claim 11  wherein the connectivity information comprises connectivity information relating to one or more of the one or more of the detected communications failure, status or problem of the first connectivity type, status or problem of the user system, and status or problem of the accessible system and status or problem of a communication pathway between the user system and the accessible system leveraging the first connectivity type. 
     
     
         13 . A computer-readable medium or propagated signal having embodied thereon a computer program configured to enable communications between a user system and an accessible system, the medium or signal comprising one or more code segments configured to:
 detect a communications failure in a communications session between a user system and an accessible system, the communications session leveraging a first connectivity type; and   establish a second communications session between the user system and the accessible system, the second communications session leveraging a second connectivity type that differs from the first connectivity type, automatically in response to the detected communication failure on the session leveraging the first connectivity type.   
     
     
         14 . The medium of  claim 13  wherein the one or more code segments configured to establish the second communications session leveraging the second connectivity type, automatically in response to the detected communication failure comprise one or more code segments configured to establish a second communications session leveraging the second connectivity type, without requiring user manipulation in response to the detected communications failure on the session leveraging the first connectivity type. 
     
     
         15 . The medium of  claim 13  wherein the first connectivity type comprises broadband connectivity. 
     
     
         16 . The medium of  claim 13  wherein the second connectivity type comprises narrowband connectivity. 
     
     
         17 . The medium of  claim 13  wherein the one or more code segments are further configured to enable the receipt, using the second communications session leveraging the second connectivity type, of connectivity information regarding one or more of the detected communications failure, status or problem of the first connectivity type, status or problem of the user system, and status or problem of the accessible system and status or problem of a communication pathway between the user system and the accessible system leveraging the first connectivity type. 
     
     
         18 . The medium of  claim 13  wherein:
 the accessible system comprises a secure system, and 
 the one or more code segments are further configured to enable the receipt of authentication information from the user system when establishing the second communications session. 
 
     
     
         19 . The medium of  claim 13  wherein the one or more code segments are further configured to use a token to transparently establish the second communications session leveraging the second connectivity type such that at least one of the applications making use of the first communications session is unaffected by the interruption of the first communications session and the establishment of the second communications session. 
     
     
         20 . The medium of  claim 13  wherein the one or more code segments are further configured to:
 detect availability of the first connectivity type for communications between the user system and the accessible system; and 
 establish a third communications session between the user system and the accessible system, the third communication session leveraging the first connectivity type, automatically in response to the detected availability of the first connectivity type. 
 
     
     
         21 .- 30 . (canceled)