Enterprise mobility user

• US 20080039080A1
• Filed: 08/09/2006
• Published: 02/14/2008
• Est. Priority Date: 08/09/2006
• Status: Active Grant

• Current Assignee: Arlington Technologies, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: Avaya Technology LLC (Avaya Incorporated)
• Inventors: Chavez, David L., Bertagnole, Albert G., Meis, Jeffrey, Crowley, Jennifer L., Rolfs, Mark T.
• Granted Patent: US 8,060,071 B2
• Time in Patent Office: Days
• US Class Current: 455/433
• CPC Class Codes: H04M 3/42238 in systems with telephone lines with multiple users
• CPC Class Codes: H04M 3/42272 whereby the subscriber registers to the terminals for personalised service provision

Abstract

In one embodiment, an enterprise network is provided that includes a mobility agent 150 associated with a switch/server 100 or 104. The mobility agent creates a visitor application record 172 associated with a second communication device 140b. The visitor application record is associated with a first subscriber. A second subscriber is normally associated with the second communication device, and the first subscriber with a first communication device 136a. In response to creating the visitor application record, the native communication device record is associated with a virtual communication device having the same public and/or private numbers as the second communication device 140b.

Claims

1. A method, comprising:

(a) providing a native communication device record for a second communication device associated with a second subscriber;

(b) thereafter creating a visitor application record associated with the second communication device, the visitor application record being associated with a first subscriber different from the second subscriber, wherein the first subscriber is normally associated with a first communication device; and

(c) in response to step (b), associating the native communication device record with a virtual communication device, the virtual communication device having the same public and/or private numbers as the second communication device.

2. The method of claim 1, further comprising:

(d) while the first subscriber is associated with the second communication device, maintaining a home communication device record for the first communication device, the home communication device record configuring the first communication device for the first subscriber; and

(e) while the first subscriber is associated with the second communication device, maintaining a home application record to redirect incoming calls for the first communication device to the second communication device.

3. The method of claim 1, further comprising:

(d) maintaining the native communication device and visitor application records independent of one another while the first subscriber is associated with the second communication device.

4. The method of claim 1, wherein the first and second communication devices are at least one of circuit-switched and time division multiplexed, wherein at least most of the following features are available to the first subscriber while the first subscriber is associated with the second communication device:

bridging an incoming call to the first subscriber onto the first communication device, call coverage, speed-dialing, ringing patterns, customized button labels, abbreviated dial list, automatic call back, automatic message waiting, automatic intercom, busy indication for another extension or trunk, call appearance, call forwarding, call forward (busy/do not answer), dial intercom, extension to cellular, exclusion, personal Central Office-line, send all calls, internal extension group, priority calling, and attendant calling, wherein, for outgoing calls from the second subscriber device, a number of the first communication device is sent as calling party information while the first subscriber is associated with the second communication device, and wherein, when an outgoing call to a universal emergency number is made from the second communication device, the first subscriber is disassociated automatically with the second communication device.

5. The method of claim 1, wherein the visitor application record comprises at least the following information:

the first subscriber'"'"'s name, the first communication device'"'"'s number, the second communication device'"'"'s number, the first subscriber'"'"'s home security information, the first and second communication device types, call state information, and a second communication device button record having a set of a plurality of buttons identical to a set of a plurality of buttons on the first communication device and wherein the native communication device record comprises at least the following information;

second subscriber'"'"'s name, second communication device'"'"'s private number, second communication device'"'"'s public number, second subscriber'"'"'s home security information, second communication device type, second communication device'"'"'s button record configured for the second subscriber, class of service for the second communication device, and call state information.

6. The method of claim 5, wherein the home communication record comprises at least the following information:

first subscriber'"'"'s name, first communication device'"'"'s private number, first communication device'"'"'s public number, first subscriber'"'"'s home security information, first communication device type, first communication device button record configured for the first subscriber, class of service for the first communication device, and call state information and wherein the home application record comprises at least the following information;

the number of the second communication device and the second communication device type, a pointer to the home station record for the first station, and wherein the home communication device record and home application record are associated with one another.

7. The method of claim 1, wherein the first communication device is controlled by a first switch/server and the second communication device is controlled by a second switch/server, wherein, while the first subscriber is associated with the second communication device, incoming calls to the second subscriber are processed as defined in the native communication device record and not directed to the second communication device, and incoming calls to the first subscriber are directed by the first switch/server to the second switch/server and by the second switch/server to the second communication device, and outgoing button origination calls from the first subscriber initiated using the second communication device are directed by the second switch/server to the first switch/server setup with called destination.

8. The method of claim 7, wherein, when an incoming call is directed by the first switch/server to the second switch/server, the first switch/server sends to the second switch/server a call appearance selected for the call and wherein, when an outgoing call is directed by the second switch/server to the first switch/server, the second switch/server sends to the first switch/server a call appearance selected for the call.

9. A computer readable medium comprising processor executable instructions to perform the steps of claim 1.

10. A method, comprising:

(a) a second switch/server receiving a request from a first subscriber to be associated with a second communication device controlled by the second switch/server, wherein the first subscriber is also associated with a first communication device controlled by a first switch/server different from the second switch/server;

(b) the second switch/server notifying the first switch/server of the request; and

(c) the second switch/server associating the second communication device with the first subscriber, whereby the first subscriber is able to make outgoing calls from and receive incoming calls at the second communication device and to access at least some features accessible by the first subscriber at the first communication device.

11. The method of claim 10, wherein the second communication device is normally associated with a second subscriber, wherein the request notification in step (b) comprises a number of the second communication device, a number of the first communication device, and the first communication device type and wherein the associating step (c) comprises the substeps:

(c1) the first switch/server creating a home application record and a button map of the first communication device;

(c2) the first switch/server forwarding the first communication device type, button map, message waiting state indicator, first communication device number, and first subscriber'"'"'s name to the second switch/server;

(c3) using information received in substep (c2), the second switch/server creating a visitor application record associating the first subscriber with the second communication device; and

(c4) the second switch/server reconfiguring the second communication device as defined in the visitor application record.

12. The method of claim 10, wherein the second communication device is normally associated with a second subscriber, wherein the second switch/server comprises a native communication device record for the second communication device, wherein the first switch/server comprises a visitor application record for the second communication device, wherein the native communication device record is associated with the second subscriber, and the visitor application record is associated with the first subscriber, wherein the native communication device record is, while the first subscriber is associated with the second communication device, associated with a virtual communication device, and wherein the virtual communication device and second communication device have a common number.

13. The method of claim 12, wherein the first switch/server comprises a home communication device record for the first communication device, the home communication device record configuring the first communication device for the first subscriber and a home application record to redirect incoming calls for the first communication device to the second communication device, wherein the first and second communication devices are at least one of circuit-switched and time division multiplexed, wherein at least most of the following features are available to the first subscriber while the first subscriber is associated with the second communication device:

bridging an incoming call to the first subscriber onto the first communication device, call coverage, speed-dialing, ringing patterns, customized button labels, abbreviated dial list, automatic call back, automatic message waiting, automatic intercom, busy indication for another extension or trunk, call appearance, call forwarding, call forward (busy/do not answer), dial intercom, extension to cellular, exclusion, personal Central Office-line, send all calls, internal extension group, priority calling, and attendant calling, wherein, for outgoing calls from the second subscriber device, a number of the first communication device is sent as calling party information while the first subscriber is associated with the second communication device, and wherein, when an outgoing call to a universal emergency number is made from the second communication device, the first subscriber is disassociated automatically with the second communication device.

14. The method of claim 13, wherein the visitor application record comprises at least the following information:

the first subscriber'"'"'s name, the first communication device'"'"'s number, the second communication device'"'"'s number, the first subscriber'"'"'s home security information, the first and second communication device types, call state information, and a second communication device button record having a set of a plurality of buttons identical to a set of a plurality of buttons on the first communication device and wherein the native communication device record comprises at least the following information;

second subscriber'"'"'s name, second communication device'"'"'s private number, second communication device'"'"'s public number, second subscriber'"'"'s home security information, second communication device type, second communication device'"'"'s button record configured for the second subscriber, class of service for the second communication device, and call state information, wherein the home communication record comprises at least the following information;

first subscriber'"'"'s name, first communication device'"'"'s private number, first communication device'"'"'s public number, first subscriber'"'"'s home security information, first communication device type, first communication device button record configured for the first subscriber, class of service for the first communication device, and call state information and wherein the home application record comprises at least the following information;

the number of the second communication device and the second communication device type, a pointer to the home station record for the first station, and wherein the home communication device record and home application record are associated with one another.

15. The method of claim 10, wherein, while the first subscriber is associated with the second communication device, incoming calls to the second subscriber are processed as defined in the native communication device record and not directed to the second communication device, and incoming calls to the first subscriber are directed by the first switch/server to the second switch/server and by the second switch/server to the second communication device, and outgoing calls from the first subscriber initiated using the second communication device are directed by the second switch/server to the first switch/server setup with called destination.

16. The method of claim 15, wherein, when an incoming call is directed by the first switch/server to the second switch/server, the first switch/server sends to the second switch/server a call appearance selected for the call and wherein, when an outgoing call is directed by the second switch/server to the first switch/server, the second switch/server sends to the first switch/server a call appearance selected for the call.

17. A computer readable medium comprising processor executable instructions to perform the steps of claim 10.

18. An enterprise network, comprising:

a mobility agent associated with a switch/server, the mobility agent being operable to;

(a) provide a native communication device record for a second communication device associated with a second subscriber;

(b) create a visitor application record associated with the second communication device, the visitor application record being associated with a first subscriber different from the second subscriber, wherein the first subscriber is normally associated with a first communication device; and

(c) in response to the creation of the visitor application record, associate the native communication device record with a virtual communication device, the virtual communication device having the same public and/or private numbers as the second communication device.

19. The enterprise network of claim 18, wherein the mobility agent is further operable to:

(d) while the first subscriber is associated with the second communication device, maintain a home communication device record for the first communication device, the home communication device record configuring the first communication device for the first subscriber; and

(e) while the first subscriber is associated with the second communication device, maintain a home application record to redirect incoming calls for the first communication device to the second communication device.

20. The enterprise network of claim 18, wherein the mobility agent is further operable to:

(d) maintain the native communication device and visitor application records independent of one another while the first subscriber is associated with the second communication device.

21. The enterprise network of claim 19, wherein the first switch/server comprises a home communication device record for the first communication device, the home communication device record configuring the first communication device for the first subscriber and a home application record to redirect incoming calls for the first communication device to the second communication device, wherein the first and second communication devices are at least one of circuit-switched and time division multiplexed, wherein at least most of the following features are available to the first subscriber while the first subscriber is associated with the second communication device:

bridging an incoming call to the first subscriber onto the first communication device, call coverage, speed-dialing, ringing patterns, customized button labels, abbreviated dial list, automatic call back, automatic message waiting, automatic intercom, busy indication for another extension or trunk, call appearance, call forwarding, call forward (busy/do not answer), dial intercom, extension to cellular, exclusion, personal Central Office-line, send all calls, internal extension group, priority calling, and attendant calling, wherein, for outgoing calls from the second subscriber device, a number of the first communication device is sent as calling party information while the first subscriber is associated with the second communication device, and wherein, when an outgoing call to a universal emergency number is made from the second communication device, the first subscriber is disassociated automatically with the second communication device.

22. The enterprise network of claim 21, wherein the visitor application record comprises at least the following information:

the first subscriber'"'"'s name, the first communication device'"'"'s number, the second communication device'"'"'s number, the first subscriber'"'"'s home security information, the first and second communication device types, call state information, and a second communication device button record having a set of a plurality of buttons identical to a set of a plurality of buttons on the first communication device and wherein the native communication device record comprises at least the following information;

second subscriber'"'"'s name, second communication device'"'"'s private number, second communication device'"'"'s public number, second subscriber'"'"'s home security information, second communication device type, second communication device'"'"'s button record configured for the second subscriber, class of service for the second communication device, and call state information, wherein the home communication record comprises at least the following information;

first subscriber'"'"'s name, first communication device'"'"'s private number, first communication device'"'"'s public number, first subscriber'"'"'s home security information, first communication device type, first communication device button record configured for the first subscriber, class of service for the first communication device, and call state information and wherein the home application record comprises at least the following information;

the number of the second communication device and the second communication device type, a pointer to the home station record for the first station, and wherein the home communication device record and home application record are associated with one another.

23. The enterprise network of claim 18, wherein, while the first subscriber is associated with the second communication device, incoming calls to the second subscriber are processed as defined in the native communication device record and not directed to the second communication device, and incoming calls to the first subscriber are directed by the first switch/server to the second switch/server and by the second switch/server to the second communication device, and outgoing calls from the first subscriber initiated using the second communication device are directed by the second switch/server to the first switch/server setup with called destination.

24. The enterprise network of claim 23, wherein, when an incoming call is directed by the first switch/server to the second switch/server, the first switch/server sends to the second switch/server a call appearance selected for the call and wherein, when an outgoing call is directed by the second switch/server to the first switch/server, the second switch/server sends to the first switch/server a call appearance selected for the call.