Dynamically provisioned mobile station and method therefor

• US 20040116140A1
• Filed: 07/09/2003
• Published: 06/17/2004
• Est. Priority Date: 12/20/2002
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Michaelis, Oliver, Abrol, Nischal, Lioy, Marcello, Babbar, Uppinder S.
• Granted Patent: US 7,430,602 B2
• Time in Patent Office: Days
• US Class Current: 455/517
• CPC Class Codes: H04W 4/18 Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
• CPC Class Codes: H04W 76/10 Connection setup
• CPC Class Codes: H04W 76/20 Manipulation of established connections
• CPC Class Codes: H04W 8/245 from a network towards a terminal
• CPC Class Codes: H04W 8/26 Network addressing or numbering for mobility support
• CPC Class Codes: H04W 88/02 Terminal devices
• CPC Class Codes: H04W 88/06 adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
• CPC Class Codes: H04W 92/02 Inter-networking arrangements
• CPC Class Codes: H04W 92/08 between user and terminal device
• CPC Class Codes: H04W 92/18 between terminal devices

Abstract

Multimode mobile station includes mobile configuration manager, device interface, and network interface to dynamically provision network configuration for mobile TE2-type mobile terminals and accomodates multiple protocols over multiple carrier access methods over U_m interface and multiple access methods over R_m interface. A method for communicating between endpoints, where a mobile node obtains a unique configuration from a network for a managed device. The mobile node dynamically provisions the configuration for the connected managed device, in response to device request or network notice. The node adapts messages over R_m interface for TE2 signals and over U_m interface for a wireless protocol.

Claims

1. A method for communicating between a first communication,endpoint coupled to an R_m interface and a second communication endpoint coupled to a network, the method comprising:

a. receiving a provisioning request for a resource by a mobile station manager from one of the first communication endpoint and the second communication endpoint;

b. provisioning the resource for the connected entity in response to the provisioning request,

wherein the resource uniquely identifies the first communication endpoint on the communication network;

c. establishing a predetermined communication state between the first communication endpoint and the second communication endpoint through the mobile system manager in response to the provisioning request,

wherein the first communication endpoint communicates messages over the R_m interface with the mobile system manager as TE2-type signals; and

wherein the second communication endpoint communicates messages with the mobile system manager as network protocol signals; and

d. adapting the communicated messages between TE2-type signals and network protocol signals.

2. The method of claim 1, further comprising adapting messages for communication between the mobile station manager and the first communication endpoint over an R_m interface using one of an asynchronous, a synchronous, a isochronous, and a variable-rate physical interface protocol, wherein the messages are communicated across one of a wired physical interface and a wireless physical interface, and wherein the R_m interface is substantially ISDN-incompatible physical interface.

3. The method of claim 1, further comprising adapting messages for communication between the mobile station manager and the second communication endpoint over an U_m interface using one of a CDMA carrier access method, a TDMA carrier access method, a FDMA carrier access method, and an operable combination thereof.

4. The method of claim 2, further comprising adapting messages for communication between the mobile station manager and the second communication endpoint over an U_m interface using one of a CDMA carrier access method, a TDMA carrier access method, a FDMA carrier access method, and an operable combination thereof.

5. A method for provisioning a mobile configuration, comprising:

a. sending an ALLOCATE request for the mobile configuration from a mobile terminal to a mobile station address server (ASVR) connected with the mobile terminal, wherein the mobile configuration comprises a unique network configuration;

b. sending the ALLOCATE request from the ASVR to an available communication network;

c. receiving the unique network configuration from the available network by the ASVR; and

d. sending the unique network configuration from the ASVR to the mobile terminal.

6. The method of claim 5, wherein sending the ALLOCATE request from the mobile terminal to the ASVR further comprises:

a. sending the ALLOCATE request from the mobile terminal to a client interface connected with the mobile terminal; and

b. sending the ALLOCATE request from the client interface to the ASVR connected with the client interface.

7. The method of claim 5, wherein sending the ALLOCATE request from the ASVR to the available communication network further comprises:

a. selecting by the ASVR of an available server interface connected between the ASVR and the available communication network;

b. sending the ALLOCATE request from the ASVR to the available server interface; and

c. sending the ALLOCATE request from the available server interface to the available communication network.

8. The method of claim 5, wherein receiving the unique network configuration from the available network by the ASVR further comprises:

a. receiving the unique network configuration from the available network by a server interface connected between the ASVR and the available network; and

b. sending the unique network configuration from the server interface to the ASVR.

9. The method of claim 5, wherein sending the unique network configuration from the ASVR to the mobile terminal further comprises:

a. identifying, by the ASVR, the client interface to which to send the unique network configuration;

b. sending the unique network configuration from the ASVR to a client interface connected between the ASVR and the mobile terminal; and

c. sending the unique network configuration from the client interface to the mobile terminal.

10. The method of claim 6, wherein sending the ALLOCATE request from the ASVR to the available communication network further comprises:

a. selecting by the ASVR of an available server interface connected between the ASVR and the available communication network;

b. sending the ALLOCATE request from the ASVR to the available server interface; and

c. sending the ALLOCATE request from the available server interface to the available communication network.

11. The method of claim 10, wherein receiving the unique network configuration from the available network by the ASVR further comprises:

a. receiving the unique network configuration from the available network by the server interface connected with the ASVR; and

b. sending the unique network configuration from the server interface to the ASVR.

12. The method of claim 11, wherein sending the unique network configuration from the ASVR to the mobile terminal further comprises:

a. identifying, by the ASVR, the client interface to which to send the unique network configuration;

b. sending the unique network configuration from the ASVR to the client interface, connected between the ASVR and the mobile terminal; and

c. sending the unique network configuration from the client interface to the mobile terminal.

13. The method of claim 6, wherein sending the unique network configuration from the ASVR to the mobile terminal further comprises:

a. identifying, by the ASVR, the client interface to which to send the unique network configuration;

b. sending the unique network configuration from the ASVR to the client interface, connected between the ASVR and the mobile terminal; and

c. sending the unique network configuration from the client interface to the mobile terminal.

14. The method of claim 7, wherein receiving the unique network configuration from the available network by the ASVR further comprises:

a. receiving the unique network configuration from the available network by the server interface connected with the ASVR; and

b. sending the unique network configuration from the server interface to the ASVR.

15. The method of claim 8, wherein sending the unique network configuration from the ASVR to the mobile terminal further comprises:

a. identifying, by the ASVR, the client interface to which to send the unique network configuration;

b. sending the unique network configuration from the ASVR to the client interface, connected between the ASVR and the mobile terminal; and

c. sending the unique network configuration from the client interface to the mobile terminal.

16. The method of claim 6, wherein the client interface is in a DOWN state, and wherein sending the ALLOCATE request from the client interface to the ASVR further comprises:

a. sending a private ALLOCATE request for a client interface configuration from the client interface to the ASVR;

b. allocating the client interface configuration by the ASVR;

c. sending the client interface configuration to the client interface by the ASVR;

d. configuring the client interface with the client interface configuration, creating a configured client interface and coming UP thereby; and

e. sending the ALLOCATE request for a unique network configuration for the mobile terminal by the configured client interface to the ASVR.

17. The method of claim 7, wherein sending the ALLOCATE request from the available server interface to the available communication network further comprises:

a. setting up a network connection between the available server interface and the available communication network using a preselected wireless communication protocol over a preselected carrier access medium; and

b. sending the ALLOCATE request for the unique network configuration from the available server interface to the available communication network over the network connection.

18. The method of claim 8, wherein the available server interface is in a DOWN state, and wherein receiving the unique network configuration from the available network by the available server interface further comprises:

a. receiving the unique network configuration from the available network;

b. configuring the available server interface with the unique network configuration, creating a configured available server interface and coming UP thereby;

c. requesting a second unique network configuration from the available network by the available server interface;

d. receiving the second unique network configuration from the available network by the available server interface; and

e. sending the second unique network configuration to the ASVR from the available server interface.

19. The method of claim 9, wherein sending the unique network configuration from the client interface to the mobile terminal further comprises:

a. receiving the unique network configuration by the mobile terminal; and

b. configuring the mobile terminal with the unique network configuration, wherein the mobile terminal includes a TE2 device.

20. The method of claim 9, wherein sending the unique network configuration from the client interface to the mobile terminal further comprises:

a. receiving the unique network configuration by an interface controller connected with the mobile terminal; and

b. configuring the mobile terminal with the unique network configuration by the interface controller, wherein the mobile terminal includes a TE2 device.

21. A method for provisioning a mobile configuration, comprising:

a. sending a RELEASE request for the mobile configuration from a mobile terminal to a mobile station address server (ASVR) connected with the mobile terminal, and effecting mobile terminal deconfiguration thereby, wherein the mobile configuration comprises a unique network configuration;

b. sending the RELEASE request from the ASVR to a connected communication network corresponding to the unique network configuration; and

c. receiving a RELEASE response from the connected network by the ASVR.

22. The method of claim 21, wherein sending the RELEASE request from the mobile terminal to the ASVR, further comprises:

a. sending the RELEASE request for the unique network configuration from the mobile terminal to a client interface connected between the mobile terminal and the ASVR;

b. identifying, by the client interface, the mobile terminal corresponding to the unique network configuration;

c. deconfiguring the mobile terminal identified by the client interface, responsive to the RELEASE request;

d. updating client interface routing information in response to deconfiguring the mobile terminal; and

e. sending the RELEASE request from the client interface to the ASVR connected with the client interface.

23. The method of claim 21, wherein sending the RELEASE request from the ASVR to the connected communication network further comprises:

a. identifying, by the ASVR, a server interface coupled to the connected network;

b. sending the RELEASE request from the ASVR to the server interface, and releasing the unique network configuration thereby;

c. updating server interface routing information in response to releasing the unique network configuration; and

d. sending the RELEASE request from the server interface to the connected communication network.

24. The method of claim 22, wherein receiving the RELEASE response from the connected network by the ASVR further comprises:

a. receiving the RELEASE response from the connected network by a server interface connected between the ASVR and the connected network;

b. sending the RELEASE response from the server interface to the ASVR; and

c. sending the RELEASE response from the ASVR to the client interface.

25. The method of claim 23, wherein receiving the RELEASE response from the connected network by the ASVR further comprises:

a. receiving the RELEASE response from the connected network by the server interface;

b. sending the RELEASE response from the server interface to the ASVR; and

c. sending the RELEASE response from the ASVR to the client interface.

26. The method of claim 25, wherein sending the RELEASE response from the ASVR to the client interface further comprises:

a. identifying a unique client interface network configuration for the client interface;

b. sending a RELEASE request to the ASVR relative to the unique client interface network configuration;

c. releasing the unique client interface network configuration by the ASVR;

d. receiving a RELEASE response from ASVR responsive to the releasing by the ASVR; and

e. bringing DOWN the client interface.

27. A method for provisioning a mobile configuration, comprising:

a. receiving a REVOKE request by a mobile station address server (ASVR) that a connected network is unavailable, the connected network being associated with the mobile configuration, and wherein the mobile configuration corresponds to a unique network configuration;

b. sending a REVOKE request to a mobile terminal associated with the unique network configuration by the ASVR; and

c. deconfiguring the mobile terminal.

28. The method of claim 27, wherein receiving the REVOKE request by the ASVR that the connected network is unavailable further comprises:

a. receiving the REVOKE request by a server interface in an UP state that the connected network is unavailable;

b. transitioning the server interface from the UP state to the DISABLED state;

c. updating tables of the server interface indicative of one of network unavailability and of the server interface in the DISABLED state;

d. notifying the ASVR connected with the server interface of the unique network configuration that is to be revoked; and

e. identifying the mobile terminal for which the unique network configuration is to be revoked, and preparing the REVOKE request.

29. The method of claim 27, wherein sending the REVOKE request to the mobile terminal further comprises:

a. sending the REVOKE request for the unique network configuration to a client interface associated with the unique network configuration and connected with the ASVR;

b. identifying, by the client interface, the mobile terminal associated with the unique network configuration;

c. sending a REVOKE response from the client interface to the ASVR; and

d. notifying the mobile terminal of the REVOKE request.

30. The method of claim 29, wherein sending the REVOKE request for the unique network configuration to the client server further comprises:

a. sending an ALLOCATE request for the second unique network configuration to the ASVR;

b. if the ASVR identifies a second server interface through which the second unique network configuration can be obtained, then;

(1) sending the ALLOCATE request for the second unique network configuration to the second server interface by the ASVR,

(2) sending the second unique network configuration to the ASVR by the second server interface,

(3) sending the second unique network configuration to the client interface by the ASVR, and

(4) configuring the mobile terminal with the second unique network configuration; and

c. if the ASVR does not identify a second server interface through which the second unique network configuration can be obtained, then;

(1) sending an ALLOCATE FAILURE notice to the client interface by the ASVR,

(2) deconfiguring the mobile terminal, and

(3) if no additional mobile terminals are to be deconfigured, then;

(a) identifying a unique client interface network configuration for the client interface,

(b) sending a RELEASE request to the ASVR relative to the unique client interface network configuration,

(c) releasing the unique client interface network configuration by the ASVR;

(d) receiving a RELEASE response from ASVR responsive to the releasing by the ASVR; and

(e) transitioning the client interface to the DOWN state.

31. A method for provisioning a mobile configuration, comprising:

a. receiving an UPDATE request by a mobile station address server (ASVR) from a connected network of a network change for the ASVR and a mobile terminal connected with the ASVR, the connected network being associated with the mobile configuration, wherein the mobile configuration corresponds to a first unique network configuration;

b. receiving, by the ASVR, a second unique network configuration from the connected network;

c. sending the second unique network configuration from the ASVR to the mobile terminal, the second unique network configuration replacing the first unique network configuration as the mobile configuration; and

d. reconfiguring the mobile terminal with the second unique network configuration.

32. The method of claim 31, wherein receiving the UPDATE request by the ASVR further comprises:

a. receiving the UPDATE request by a server interface connected between the ASVR and the connected network;

b. receiving the second unique network configuration from the connected network by the server interface;

c. updating server interface tables indicative of the second unique network configuration replacing the first unique network configuration; and

d. sending the second unique network configuration with an UPDATE request to the ASVR by the server interface.

33. The method of claim 31, wherein sending the second unique network configuration from the ASVR to the mobile terminal further comprises:

a. updating tables of the ASVR indicative of the second unique network configuration replacing the first unique network configuration;

b. identifying a client interface associated with the first unique network configuration by the ASVR;

c. sending to the client interface an UPDATE request of the first unique network configuration with the second unique network configuration by the ASVR;

d. identifying the mobile terminal associated with the first unique network configuration by the client interface;

e. updating tables of the client interface indicative of the second unique network configuration replacing the first unique network configuration;

f. reconfiguring the mobile terminal with the second unique network configuration;

g. sending an UPDATE response from the client interface to the ASVR, responsive to the reconfiguring; and

h. sending the UPDATE response to the server interface by the ASVR, responsive to the client interface sending the UPDATE response to the ASVR.

34. The method of claim 32, wherein sending the second unique network configuration from the ASVR to the mobile terminal further comprises:

a. updating tables of the ASVR indicative of the second unique network configuration replacing the first unique network configuration;

b. identifying a client interface associated with the first unique network configuration by the ASVR;

c. sending an UPDATE request to the client interface for the first unique network configuration with the second unique network configuration by the ASVR;

d. identifying the mobile terminal associated with the first unique network configuration by the client interface;

e. updating tables of the client interface indicative of the second unique network configuration replacing the first unique network configuration;

f. reconfiguring the mobile terminal with the second unique network configuration;

g. sending an UPDATE response from the client interface to the ASVR, responsive to the reconfiguring; and

h. sending the UPDATE response to the server interface by the ASVR, responsive to the client interface sending to the ASVR.

35. The method of claim 31, wherein the UPDATE request is comprises a network handoff.

36. The method of claim 34, wherein the UPDATE request is comprises a network handoff.

37. A method for communicating across a network with a remote host, the method comprising:

a. receiving a provisioning request for a resource by a mobile station manager coupled to at least one mobile terminal, wherein the at least one mobile terminal communicate messages as TE2-type signals through a respective R_m interface with the mobile system manager;

b. provisioning the resource in response to the provisioning request, wherein the resource uniquely identifies the at least one mobile terminal relative to the communication network;

c. establishing a predetermined communication state between the mobile station manager and a selected available communication network using a selected wireless communication protocol over a selected carrier access method; and

d. establishing a predetermined communication state between the at least mobile terminal and the remote host through the mobile system manager in response to the provisioning request, wherein the remote host communicates messages with the mobile system manager as network protocol signals; and

e. adapting the communicated messages between TE2-type signals and network protocol signals.

38. The method of claim 37, further comprising adapting messages for communication between the mobile station manager and the at least one mobile terminal over an R_m interface using one of an asynchronous, a synchronous, a isochronous, and a variable-rate physical interface protocol, wherein the messages are communicated across one of a wired physical interface and a wireless physical interface, and wherein the R_m interface is a substantially ISDN-incompatible physical interface.

39. The method of claim 38, further comprising adapting messages for communication between the mobile station manager and the second communication endpoint over an U_m interface using one of a CDMA carrier access method, a TDMA carrier access method, a FDMA carrier access method, and an operable combination thereof.

40. The method of claim 39, wherein the provisioning request comprises one of an ALLOCATE request, a RELEASE request, a REVOKE request, an UPDATE request, and a combination thereof.

41. The method of claim 40, wherein the provisioning request is an ALLOCATE request, further comprising:

a. sending the ALLOCATE request for the resource to a client interface in the mobile station manager from the at least one mobile terminal to which the client interface is connected;

b. sending the ALLOCATE request to a mobile station address server (ASVR) from the client interface to which the ASVR is connected;

c. selecting by the ASVR of an available server interface connected between the ASVR and the selected available communication network;

d. sending the ALLOCATE request from the ASVR to the available server interface; and

e. sending the ALLOCATE request from the available server interface to the available communication network.

42. The method of claim 41, further comprising:

a. receiving the resource for the at least one mobile terminal from the selected available network by the ASVR, in response to the ALLOCATE request;

b. sending the resource from the server interface to the ASVR;

c. sending the resource from the ASVR to the client interface;

d. sending the resource from the client interface to the at least one mobile terminal; and

e. configuring the at least one mobile terminal with the resource wherein the at least one mobile terminal is operable as a local host, responsive to the configuring.

43. The method of claim 42, wherein the client interface is in a DOWN state, and wherein sending the ALLOCATE request from the client interface to the ASVR further comprises:

a. sending a private ALLOCATE request for a client interface configuration from the client interface to the ASVR;

b. allocating the client interface configuration by the ASVR;

c. sending the client interface configuration to the client interface by the ASVR;

d. configuring the client interface with the client interface configuration, creating a configured client interface and coming UP thereby; and

e. sending the ALLOCATE request for the resource for the at least one mobile terminal by the configured client interface to the ASVR.

44. The method of claim 40, wherein the provisioning request is an RELEASE request, further comprising:

a. sending the RELEASE request for the resource to a client interface in the mobile station manager from the at least one mobile terminal to which the client interface is connected;

b. sending the RELEASE request from the client interface to the ASVR, effecting deconfiguration of the at least one mobile terminal;

c. selecting, by the ASVR, a server interface connected to the selected available communication network corresponding to the resource;

d. sending the RELEASE request from the ASVR to the server interface; and

e. sending the RELEASE request from the server interface to the selected available communication network.

45. The method of claim 44, further comprising:

a. receiving a RELEASE request response by the server interface from the selected available communication network connected to the server interface, the RELEASE request response corresponding to the resource released by the at least one mobile terminal;

b. sending the RELEASE request response to the ASVR from the server interface to which the ASVR is connected; and

c. sending the RELEASE request response from the ASVR to the client interface to which the ASVR is connected.

46. The method of claim 45, wherein sending the RELEASE response from the ASVR to the client interface further comprises:

a. identifying a unique client interface network configuration for the client interface;

b. sending a RELEASE request to the ASVR relative to the unique client interface network configuration;

c. releasing the unique client interface network configuration by the ASVR;

d. receiving a RELEASE response from ASVR responsive to the releasing by the ASVR; and

e. bringing DOWN the client interface.

47. The method of claim 40, wherein the provisioning request is an REVOKE request, further comprising:

a. receiving the REVOKE request by a server interface in the mobile station manager indicative of the unavailability of the selected available communication network, wherein the resource corresponds to the selected available communication network;

b. sending the REVOKE request to the ASVR from the server interface to which the server interface is connected;

c. sending the REVOKE request to the ASVR from the client interface to which the ASVR is connected;

d. identifying, by the client interface, the at least one mobile terminal to which the resource corresponds;

e. sending a REVOKE request response from the client interface to the ASVR; and

f. deconfiguring the at least one mobile terminal.

48. The method of claim 47, wherein receiving the REVOKE request by the ASVR further comprises:

a. receiving the REVOKE request indicative of the unavailability of the selected available communication network by a server interface in an UP state;

b. transitioning the server interface from the UP state to the DISABLED state;

c. updating tables of the server interface indicative of one of the selected available communication network unavailability and of the server interface in the DISABLED state;

d. notifying the ASVR connected with the server interface of the resource that is to be revoked;

e. identifying, by the ASVR, the at least one mobile terminal for which the resource is to be revoked.

49. The method of claim 47, wherein the identifying the at least one mobile terminal to which an original resource corresponds further comprises:

a. prior to deconfiguring the at least one mobile terminal, sending an ALLOCATE request for a second resource to the ASVR, wherein the second resource comprises a unique network configuration corresponding to another selected available communication network resource;

b. identifying, by the ASVR, whether the second resource can be obtained;

c. if the second resource can be obtained, obtaining and sending the second resource to the client interface, wherein the client interface substitutes the second resource for the first resource and wherein the at least one mobile terminal is not deconfigured; and

d. if the second resource can not be obtained, sending an ALLOCATE FAILURE notice to the client interface, wherein the client interface continues to deconfigure the at least one mobile terminal.

50. The method of claim 47, further comprising

a. subsequent to deconfiguring the at least one mobile terminal, identifying a unique client interface network configuration for the client interface;

b. sending a RELEASE request to the ASVR relative to the unique client interface network configuration;

c. releasing the unique client interface network configuration by the ASVR;

d. receiving a RELEASE response from ASVR responsive to the releasing by the ASVR; and

e. bringing DOWN the client interface.

51. The method of claim 40, wherein the provisioning request is an UPDATE request, further comprising:

a. receiving the UPDATE request including a second respective resource for the at least one mobile terminal from the selected available communication network by a server interface connected thereto;

b. sending the second respective resource representative of the UPDATE request from the server interface to the ASVR connected to thereto;

c. identifying, by the ASVR, the client interface connected to the at least one mobile terminal to which the the second respective resource corresponds;

d. sending the second respective resource to the client interface;

e. receiving the second respective resource by the client interface and updating tables of the client interface representative of the second respective resource replacing an original resource;

f. reconfiguring the at least one mobile terminal with the second resource; and

g. sending an UPDATE response from the client interface to the ASVR.

52. The method of claim 40, further comprising receiving multiple provisioning requests by the mobile station manager, wherein the mobile station manager is connected with multiple mobile terminals and is connectable to multiple selected available communication networks, and wherein the mobile station manager disposes the multiple mobile terminals to communicate messages substantially simultaneously across the multiple selected available communication networks employing selected combinations of an ALLOCATE request, a RELEASE request, a REVOKE request, and an UPDATE request.

53. A mobile station for communicating with a mobile service provider across a U_m interface, comprising:

a. a mobile terminal coupled to, and configured to communicate messages across, an R_m interface, using a selected configuration; and

b. a wireless communication device coupled between the R_m interface and the U_m interface,

wherein the wireless communication device provides the selected configuration to the mobile terminal,

wherein the wireless communication device cooperates with the mobile terminal to configure the mobile terminal to communicate the messages across the R_m interface, and

wherein the wireless communication device is adapted to communicate the messages with the mobile service provider across the U_m interface.

54. The mobile station of claim 53, further comprising mobile terminals coupled to, and configured to communicate messages across, the R_m interface, each mobile terminal using a respective selected configuration;

wherein the wireless communication device provides the respective selected configuration to each mobile terminal,

wherein the wireless communication device cooperates with the mobile terminals to configure the mobile terminals to communicate messages from the mobile terminals across the R_m interface, and

wherein the wireless communication device is adapted to communicate the messages from the mobile terminals with the mobile service provider across the U_m interface.

55. The mobile station of claim 54, further comprising mobile terminals coupled to, and configured to communicate messages across, predetermined R_m interfaces, each mobile terminal using a respective selected configuration to communicate respective messages across a respective selected one of the predetermined R_m interfaces;

wherein the wireless communication device provides the respective selected configuration to each mobile terminal,

wherein the wireless communication device cooperates with the mobile terminals to configure the mobile terminals to communicate messages from the mobile terminals across the respective selected one of the predetermined R_m interfaces, and

wherein the wireless communication device is adapted to communicate the messages from the mobile terminals with the mobile service provider across the U_m interface.

56. The mobile station of claim 55, wherein the wireless communication device is adapted to communicate with mobile service providers across U_m interfaces, is adapted to communicate the messages from a selected one of the mobile terminals with a selected one of the mobile service providers across a respective one of the U_m interfaces.

57. The mobile station of claim 55, wherein the U_m interface is representative of a carrier access method comprising one of a digital carrier access method, an analog carrier access method, and an operable combination thereof.

58. The mobile station of claim 57, wherein the carrier access method further comprises one of a CDMA carrier access method, a TDMA carrier access method, a FDMA carrier access method, and an operable combination thereof.

59. The mobile station of claim 58, wherein the carrier access method is a carrier access method conforming at least in part to International Telecommunications Union (Radio) Recommendation ITU-R M.1457.

60. The mobile station of claim 58, wherein a first U_m interface is representative of a first carrier access method, and a second U_m interface is representative of a second carrier access method, and wherein the first carrier access method is different from the second carrier access method.

61. The mobile station of claim 58, wherein a first U_m interface is representative of a first carrier access method, wherein a second U_m interface is representative of a second carrier access method, wherein the first carrier access method is different from the second carrier access method, and wherein one of the first and second carrier access method conforms at least in part to International Telecommunications Union (Radio) Recommendation ITU-R M.1457.

62. A mobile station communicating with a communication network over a wireless communication link, comprising:

a. a managed device having a selected network configuration, the managed device communicating messages of TE2-type physical layer signals; and

b. a mobile station manager communicating coupled between the wireless communication link and the managed device, and adapted to render TE2-type physical layer signals suitable for exchanging with the communication network over the wireless communication link,

wherein the mobile station manager dynamically provisions a selected network configuration on behalf of the managed device and cooperates to apply the selected network configuration to the managed device, the selected network configuration rendering the managed device capable of communicating the messages over the communication network.

63. The mobile station of claim 62, wherein the mobile station manager further comprises:

a. a device-related interface connected with the managed device, and adapted to transform the messages of TE2-type physical layer signals over the R_m interface into messages conforming to a network protocol;

b. a network protocol interface connected with the wireless communication, and adapted to transform the messages conforming to the network protocol into messages suitable for communicating with the communication network over the U_m interface; and

c. a mobile configuration manager adapted to manage the managed device and to communicate the messages conforming to the network protocol between the device-related interface and the network protocol interface.

64. The mobile station of claim 63, wherein the managed device comprises a non-ISDN compatible mobile terminal.

65. The mobile station of claim 63, wherein TE2-type physical layer signals comprise signals conforming at least in part to one of an ITU Recommendation, an IEEE standard, an ISO standard, an ANSI standard, an IETF standard, an EIA standard, a TIA standard, an IEC standard, an ETSI standard, an AIAA standard, an ARINC standard, a SAE standard, a serial interface standard, a parallel interface standard, and an interface standard representative of a selective combination thereof.

66. The mobile station of claim 63, wherein the U_m interface is representative of a carrier access method, and the carrier access method comprises one of a digital carrier access method, an analog carrier access method, and an operable combination thereof.

67. The mobile station of claim 66, wherein the carrier access method further comprises one of a CDMA carrier access method, a TDMA carrier access method, a FDMA carrier access method, and an operable combination thereof.

68. The mobile station of claim 67, wherein the carrier access method is a carrier access method conforming at least in part to International Telecommunications Union (Radio) Recommendation ITU-R M.1457.

69. The mobile station of claim 63, wherein the mobile configuration manager is adapted to communicate over first and second U_m interfaces using respective first and second network protocol interfaces;

wherein a first U_m interface is representative of a first carrier access method, and a second U_m interface is representative of a second carrier access method.

70. The mobile station of claim 69, wherein the mobile configuration manager is adapted to communicate over first and second R_m interfaces using respective first and second device related interfaces;

and. wherein the first R_m interface is connected with a first managed device, and the second R_m interface is connected with a first managed device.

71. The mobile station of claim 63, wherein the mobile configuration manager selects between the first network protocol interface for communicating across the first U_m interface using the first carrier access method and the second network protocol interface for communicating across the second U_m interface using the the second carrier access method, responsive to a Quality-of-Service input signal.

72. The mobile station of claim 71, wherein the managed device is a non-ISDN compatible mobile terminal and wherein TE2-type physical layer signals communicated across the R_m interface comprise signals conforming at least in part to one of an ITU Recommendation, an IEEE standard, an ISO standard, an ANSI standard, an IETF standard, an EIA standard, a TIA standard, an IEC standard, an ETSI standard, an AIAA standard, an ARINC standard, a SAE standard, a serial interface standard, a parallel interface standard, and an interface standard representative of a selected combination thereof.

73. The mobile station of claim 72, wherein each of the U_m interfaces is representative of a carrier access method, and the carrier access method comprises one of a digital carrier access method, an analog carrier access method, and an operable combination thereof, and wherein the carrier access method further comprises one of a CDMA carrier access method, a TDMA carrier access method, a FDMA carrier access method, and an operable combination thereof.

74. The mobile station of claim 73, wherein the carrier access method comprises a carrier access method conforming at least in part to International Telecommunications Union (Radio) Recommendation ITU-R M.1457.

75. A mobile communication device, comprising:

a. an interface configured as a device-related interface (DRIF), the DRIF being connectable to a managed device communicating with a first physical signal format, and configured to adapt messages communicated with the managed device between the first physical format and a network communication format;

b. an interface configured as a network protocol interface (NPIF), the NPIF being connectable to a communication network communicating with a second physical signal format, and configured to adapt messages communicated with the communication network between the network communication format and a second physical format; and

c. a mobile configuration manager coupled between the DRIF and the NPIF,

wherein the mobile configuration manager receives a provisioning resource request in the network communication format from one of the DRIF and the NPIF,

wherein the provisioning resource request includes selected combinations of an ALLOCATE request, a RELEASE request, a REVOKE request, and an UPDATE request, and

wherein the mobile configuration manager provisions the resource in response thereto, such that the resource uniquely identifies the managed device on the communication network.

76. The mobile communication device of claim 75, wherein the the managed device exchanges messages with DRIF over an R_m interface using a first physical signal format comprising ISDN-incompatible, TE2-type physical layer signals conforming at least in part to one of an ITU Recommendation, an IEEE standard, an ISO standard, an ANSI standard, an IETF standard, an EIA standard, a TIA standard, an IEC standard, an ETSI standard, an AIAA standard, an ARINC standard, a SAE standard, a serial interface standard, a parallel interface standard, and an interface standard representative of a selected combination thereof.

77. The mobile communication device of claim 76, wherein the NPIF exchanges messages over a U_m interface in the second physical signal format representative of a carrier access method, and the carrier access method comprises one of a digital carrier access method, an analog carrier access method, and an operable combination thereof, and wherein the carrier access method further comprises one of a CDMA carrier access method, a TDMA carrier access method, a FDMA carrier access method, and an operable combination thereof.

78. The mobile communication device of claim 77, wherein the carrier access method comprises a carrier access method conforming at least in part to International Telecommunications Union (Radio) Recommendation ITU-R M.1457.

79. A portable communication adaptor coupled between a TE2 communication terminal and a communication network, wherein the TE2 communication terminal exchanges messages with a remote host over the communication network, the adaptor comprising:

a. an first interface coupled with the TE2 communication terminal;

b. a second interface coupled with the communication network;

c. an address server linked to the first interface and the second interface,

wherein the address server cooperates with the second interface to exchange the messages with the communication network,

wherein the address server acts on a unique resource to the TE2 communication terminal,

wherein the address server cooperates with the first interface to configure the TE2 communication terminal with the unique resource,

wherein the address server cooperates with the first interface to compel the TE2 communication terminal to respond as a local host relative to the remote host,

wherein the address server cooperates with the first interface to exchange messages with the TE2 communication terminal, and

wherein the address server causes the portable communication adaptor to respond substantially as a communication router.

80. The portable communication adaptor of claim 79, wherein the address server acts on the unique resource by transmitting to at least one of the first interface and the second interface a provisioning signal including one of an ALLOCATE provisioning signal, a RELEASE provisioning signal, a REVOKE provisioning signal, an UPDATE provisioning signal, and a selected combination thereof.

81. The portable communication adaptor of claim 80, wherein the TE2 communication terminal exchanges the messages with the first interface through an R_m interface using a TE2-type physical layer signal format conforming at least in part to one of an ITU Recommendation, an IEEE standard, an ISO standard, an ANSI standard, an IETF standard, an EIA standard, a TIA standard, an IEC standard, an ETSI standard, an AIAA standard, an ARINC standard, a SAE standard, a serial interface standard, a parallel interface standard, and an interface standard representative of a selected combination thereof.

82. The portable communication adaptor of claim 81, wherein the second interface exchanges the messages with the communication network through a U_m interface using a carrier access method, and the carrier access method comprises at least one of a digital carrier access method, an analog carrier access method, and an operable combination thereof, and wherein the carrier access method further comprises one of a CDMA carrier access method, a TDMA carrier access method, a FDMA carrier access method, and an operable combination thereof.

83. The mobile communication device of claim 82, wherein the carrier access method comprises a carrier access method conforming at least in part to International Telecommunications Union (Radio) Recommendation ITU-R M.1457.

84. The portable communication adaptor of claim 82, further comprising multiple first interfaces each selectably coupled with a respective one of multiple TE2 communication terminals, the TE2-type physical layer signal format of one of the multiple TE2 communication terminals being different from the TE2-type physical layer signal format of another of the multiple TE2 communication terminals.

85. The portable communication adaptor of claim 84, further comprising multiple second interfaces each selectably coupled with a respective one of multiple communication networks, one of the multiple communication networks exchanging messages with one of the multiple second interfaces using a first carrier access method, and another of the multiple communication networks exchanging messages with a another of the multiple second interfaces using a second carrier access method, wherein the first carrier access method is different from the second carrier access method.

86. The portable communication adaptor of claim 85, wherein the multiple second interfaces are selectably coupled with a respective one of multiple communication networks responsive to a Quality-of Service signal.

87. The portable communication adaptor of claim 82, wherein the address server cooperates with the first interface and the second interface to exchange the messages using one of an asynchronous service, a synchronous service, an isochronous service, a variable-rate service, and a combination thereof.