U.S. patent application number 11/839385 was filed with the patent office on 2008-01-31 for method and apparatus for configuring a voice over ip client connection.
This patent application is currently assigned to SYMBOL TECHNOLOGIES, INC.. Invention is credited to Patrick M. BROWN, Luis F. LLAMAS, Jovan D. MILOSAVLJEVIC, Charles P. UBRIACO.
Application Number | 20080026789 11/839385 |
Document ID | / |
Family ID | 34678321 |
Filed Date | 2008-01-31 |
United States Patent
Application |
20080026789 |
Kind Code |
A1 |
LLAMAS; Luis F. ; et
al. |
January 31, 2008 |
METHOD AND APPARATUS FOR CONFIGURING A VOICE OVER IP CLIENT
CONNECTION
Abstract
A method for configuring a connection comprises receiving a
request to connect a mobile device having a mobile device type to a
communications network including a private branch exchange (PBX)
system having a PBX type. Identification information including at
least one of the mobile device type and the PBX type is provided. A
PBX binding layer is selected based on the identification
information. The selected PBX binding layer is provided to the
mobile device for interfacing with the PBX system.
Inventors: |
LLAMAS; Luis F.;
(Manorville, NY) ; MILOSAVLJEVIC; Jovan D.;
(Staten Island, NY) ; UBRIACO; Charles P.;
(Northport, NY) ; BROWN; Patrick M.; (Holbrook,
NY) |
Correspondence
Address: |
INGRASSIA FISHER & LORENZ, P.C.
7150 E. CAMELBACK, STE. 325
SCOTTSDALE
AZ
85251
US
|
Assignee: |
SYMBOL TECHNOLOGIES, INC.
One Symbol Plaza
Holtsville
NY
11742
|
Family ID: |
34678321 |
Appl. No.: |
11/839385 |
Filed: |
August 15, 2007 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
10741971 |
Dec 19, 2003 |
7272414 |
|
|
11839385 |
Aug 15, 2007 |
|
|
|
Current U.S.
Class: |
455/555 |
Current CPC
Class: |
H04M 7/1235 20130101;
H04Q 3/62 20130101; H04Q 2213/1322 20130101; H04Q 2213/13389
20130101; H04M 1/72406 20210101; H04Q 2213/13109 20130101; H04M
3/4234 20130101; H04M 3/58 20130101; H04Q 2213/13034 20130101; H04W
84/16 20130101; H04L 65/1053 20130101; H04M 3/42314 20130101; H04M
2207/18 20130101; H04M 1/2535 20130101; H04L 29/06027 20130101 |
Class at
Publication: |
455/555 |
International
Class: |
H04B 1/38 20060101
H04B001/38 |
Claims
1. A mobile device, comprising: a library of PBX binding layers;
and a processing unit adapted to issue a request to connect to a
communications network including a PBX system having a PBX type,
receive identification information including at least the PBX type
responsive to the request, and select one of the PBX binding layers
from the library for interfacing with the PBX system based on the
identification information.
2. The device of claim 1, wherein the mobile device has a type, and
the processing unit is further adapted to select one of the PBX
binding layers from the library for interfacing with the PBX system
based on the PBX type and the mobile device type.
3. The device of claim 1, further comprising a user interface,
wherein the user interface remains substantially unchanged
following a transfer from the communications network to a different
communications network having a different PBX type.
4. The device of claim 1, wherein the PBX binding layer includes
instructions for configuring access to services on the
communications network based on a user profile associated with the
mobile device.
5. The device of claim 1, wherein the processing unit is configured
to employ a voice over internet protocol (VOIP) for interfacing
with the PBX system.
6. The device of claim 1, further comprising a storage device that
stores the library of PBX binding layers.
7. The device of claim 1, wherein the library of PBX binding layers
is received from a gateway in the communications network.
8. The device of claim 7, wherein the library of PBX binding layers
is wirelessly received from the gateway.
9. A mobile device comprising: a storage device configured to store
a first PBX binding layer that facilitates communication between
the mobile device and a first PBX system in a communications
network, and to store a second PBX binding layer that facilitates
communication between the mobile device and a second PBX system in
the communications network; and a processing unit coupled to the
storage device, the processing unit being adapted to receive
information indicative of a PBX type, select the first PBX binding
layer if the PBX type identifies the first PBX system, and select
the second PBX binding layer if the PBX type identifies the second
PBX system.
10. The mobile device of claim 9, the processing unit being adapted
to reconfigure the mobile device to load the second PBX binding
layer when the mobile device roams from a first area corresponding
to the first PBX system to a second area corresponding to the
second PBX system.
11. The mobile device of claim 9, the processing unit being adapted
to reconfigure the mobile device to load the first PBX binding
layer when the mobile device roams from a second area corresponding
to the second PBX system to a first area corresponding to the first
PBX system.
12. The mobile device of claim 9, further comprising a user
interface, wherein the user interface remains substantially
unchanged following a transfer from the first PBX system to the
second PBX system, and following a transfer from the second PBX
system to the first PBX system.
13. The mobile device of claim 9, wherein the processing unit is
configured to employ a voice over internet protocol (VOIP) for
interfacing with the first PBX system and for interfacing with the
second PBX system.
14. The mobile device of claim 9, wherein the storage device is
configured to receive the first PBX binding layer and the second
PBX binding layer from a gateway in the communications network.
15. The device of claim 14, wherein the first PBX binding layer and
the second PBX binding layer are wirelessly received from the
gateway.
Description
CROSS-REFERENCE TO RELATED APPLICATION
[0001] This application is a continuation of U.S. patent
application Ser. No. 10/741,971, filed Dec. 19, 2003.
TECHNICAL FIELD
[0002] This invention relates generally to communications systems,
and, more particularly, to a method and apparatus for configuring a
voice over internet protocol (VOIP) client connection.
BACKGROUND
[0003] Public switched telephone networks have been used for many
years for voice communication. A typical telephone converts sound
waves into analog signals, which are then transmitted through the
public switched telephone network (PSTN) to another telephone,
which converts the analog audio signals back into sound waves. In
recent years, wireless and cellular telephones have been rising in
popularity, due to their mobility. Users are no longer tied to a
stationary telephone, but are free to carry their telephones with
them.
[0004] Increasingly, users are using mobile devices for data
transfer, as well as for voice communication. Portable digital
devices have been developed that facilitate both data and voice
communication over a network. Such voice communication is commonly
referred to as voice over internet protocol (VOIP) communication.
Voice data is compressed into packets and delivered to the
destination in a manner that is similar to the handling of data
packets.
[0005] There are various types of networks to which connectivity
may be desired. For example, a mobile device may connect over a
network to establish voice connections with the PSTN. However, many
businesses are equipped with private branch exchange (PBX) or
private automatic branch exchange (PABX) systems to handle internal
communication. A PBX system allows a certain number of direct lines
(e.g., connections to the PSTN) to be distributed to other
telephones via the use of extensions. For example a business may
install a PBX system and have 5 direct lines coming into the
business. Through the PBX, the five lines may be linked to 20
telephones to the system using extension lines. Calls within the
business may be transferred and lines may be linked for
teleconferencing. Typically, a PBX system also allows for other
features such as call forwarding, call diversion, etc. While
networks such as the PSTN are heavily governed by standards to
insure consistency, PBX systems have no such oversight or
consistency. Each PBX manufacturer typically has its own
proprietary codes for performing functions such as call forwarding,
transferring, etc.
[0006] Systems implementing a wide area network (WAN) using
wireless data communications techniques have been generally
available for many years. Implementations exist which employ
radio-frequency (RF) communication systems and frequency-modulated
(FM) radio communications. Frequency-modulated communication
techniques include both conventional point-to-point radio and
broadcast. These systems include RAM Mobile Data Service using the
Mobitex protocol; the Advanced Radio Data Information Service
(ARDIS), manufactured by ARDIS Company, Lincolnshire, Ill.; and the
Cellular Digital Packet Data (CDPD) service.
[0007] Wireless local area networks (WLANs) are used in a variety
of business and other settings. Wireless local area networks use
infrared or radio frequency communications channels to communicate
between stationary, portable, or mobile computer units and
stationary access points or base stations. These access points are
in turn connected by a wired or wireless communication channel to a
network infrastructure which connects groups of access points
together to form a local area network, including, optionally, one
or more host computer systems.
[0008] Wireless infrared and radio frequency (RF) protocols are
known which support the logical interconnection of mobile devices
having a variety of types of communication capabilities to host
computers. The logical interconnections are based upon an
infrastructure in which at least some of the remote terminals are
capable of communicating with at least two of the access points
when located within a predetermined range therefrom, each terminal
unit being normally associated with and in communication with a
single one of such access points. Based on the overall spatial
layout, response time, and loading requirements of the network,
different networking schemes and communication protocols have been
designed so as to most efficiently regulate the association of the
mobile unit with specific access points, and the availability of
the communication channel to individual mobile units for
broadcasting.
[0009] One such protocol is described in U.S. Pat. Nos. 5,029,183;
5,142,550; 5,280,498; and 5,668,803 each assigned to Symbol
Technologies, Inc. and incorporated herein by reference. Another
such protocol is described in U.S. Pat. No. 5,673,031. Still
another protocol is set forth in the IEEE Standard 802.11 entitled
"Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)
Specifications" available from the IEEE Standards Department,
Piscataway, N.J. (hereinafter the "IEEE 802.11 Standard"). Various
iterations of the 802.11 standard (e.g., 802.11b) define protocols
for different data rates and capabilities. The term 802.11 is
intended to cover the entire family of such specifications. The
IEEE 802.11 Standard permits either infrared or RF communications,
a medium access technique similar to carrier sense multiple
access/collision avoidance (CSMA/CA), a power-save mode
particularly important for battery-operated mobile units, seamless
roaming in a full cellular network, high throughput operation,
diverse antennae systems designed to eliminate "dead spots," and an
easy interface to existing network infrastructures.
[0010] The basic specifications for the communication of audio,
video and multimedia that are applicable to the networks pertaining
to the present invention are set forth in the International
Telecommunications Union Telecommunication Standards Section
(ITU-T) standards H.321-323. The H.321 recommendation relates to
asynchronous transfer mode (ATM) channels, H.322 to guaranteed
Quality of Service LANs, and H.323 to packet based systems. Other
exemplary protocols include session initiation protocol (SIP),
Megaco, multimedia gateway control protocol (MGCP), and other
proprietary protocols.
[0011] In VOIP systems data packets are created from a compressed
data stream of digital voice samples. The data packets are
formatted for transmission over a data network. Since network
latency and packet transmission delays can hamper to the
intelligibility and quality of real-time phone conversations, a
variety of approaches of giving priority for voice packets (or
other real-time multimedia packets) over data packets in the
network have been proposed, thus allowing delay-sensitive packets
to supercede data packets across any network node in any traffic
situation. The H.323 recommendation also provides for call
establishment and control, including determining the sequencing and
timing of establishing and disconnect procedures, as well as the
control of the H.323 session after it is established.
[0012] To the extent the Internet Protocol or "IP" (as set forth in
IETF RFC 791) is used as the network layer protocol, the
recommendations of the International Multimedia Teleconferencing
Consortium's Voice over IP Forum may also be applicable to such a
Voice over IP (VOIP) network. In a VOIP network, the voice signal
is digitized, encapsulated into IP packets, and then routed between
VOIP capable devices in an IP network. These packets of voice may
then be delivered in real time as voice communications, or stored
as voice mail.
[0013] Communications between a local area network (LAN) and a wide
area network or telephone network are generally performed by
communications controller known as a gateway or proxy. In the H.323
standard, for example, a gateway generally refers to an endpoint
which provides for real-time, two-way communications between H.323
terminals on an IP network and other ITU terminals, telephones on a
PSTN or PBX, and terminals on other networks.
[0014] For a mobile device to communicate through a gateway to a
PBX system, it must be configured with the commands that the PBX
expects to receive to access its functions. One problem associated
with connecting a mobile device to a PBX lies in the various PBX
systems and their differing internal protocols. It is not uncommon
for a single business to have more than one type of PBX system
installed. Hence, a device configured to interface with a
particular type of PBX will not operate properly if it is connected
to a network using a different PBX protocol. This problem is
compounded in a wireless environment, where it is not uncommon for
a user to move locations and interface with different wireless
access points or gateways in the facility depending on which access
point is handling the user's calls. If a user roams from one access
point to another, the mobile device may cease to operate properly
as it no longer knows the proper PBX commands.
[0015] The present invention is directed to overcoming, or at least
reducing the effects of, one or more of the problems set forth
above.
BRIEF SUMMARY
[0016] One aspect of the present invention is seen in a method for
configuring a connection. The method includes receiving a request
to connect a mobile device having a mobile device type to a
communications network including a private branch exchange (PBX)
system having a PBX type. Identification information including at
least one of the mobile device type and the PBX type is provided. A
PBX binding layer is selected based on the identification
information. The selected PBX binding layer is provided to the
mobile device for interfacing with the PBX system.
[0017] Another aspect of the present invention is seen in a system
including a first communications network. The communications
network includes an interface unit and a PBX system. The interface
agent is adapted to receive a request for connecting a mobile
device having a mobile device type to the communications network.
The private branch exchange (PBX) system has a PBX type and is
connected to the interface agent. At least one of the mobile device
and the interface agent is adapted to provide identification
information including at least one of the mobile device type and
the PBX type. The interface agent is adapted to select a PBX
binding layer based on the identification information and provide
the selected PBX binding layer to the mobile device for interfacing
with the PBX system.
BRIEF DESCRIPTION OF THE DRAWINGS
[0018] The invention may be understood by reference to the
following description taken in conjunction with the accompanying
drawings, in which like reference numerals identify like elements,
and in which:
[0019] FIG. 1 is a simplified block diagram of a communications
system in accordance with one exemplary embodiment of the present
invention;
[0020] FIGS. 2A-2C illustrate exemplary entries in a library of
binding layers used in the system of FIG. 1;
[0021] FIG. 3 is an alternative embodiment of a communication
system that allows roaming between networks with different PBX
types;
[0022] FIG. 4 is a simplified block diagram of a method for
configuring a mobile device in accordance with another exemplary
embodiment of the present invention; and
[0023] FIG. 5 is a simplified block diagram of the mobile device of
FIG. 1 in accordance with yet another exemplary embodiment of the
present invention.
[0024] While the invention is susceptible to various modifications
and alternative forms, specific embodiments thereof have been shown
by way of example in the drawings and are herein described in
detail. It should be understood, however, that the description
herein of specific embodiments is not intended to limit the
invention to the particular forms disclosed, but on the contrary,
the intention is to cover all modifications, equivalents, and
alternatives falling within the spirit and scope of the invention
as defined by the appended claims.
DETAILED DESCRIPTION
[0025] Illustrative embodiments of the invention are described
below. In the interest of clarity, not all features of an actual
implementation are described in this specification. It will of
course be appreciated that in the development of any such actual
embodiment, numerous implementation-specific decisions must be made
to achieve the developers' specific goals, such as compliance with
system-related and business-related constraints, which will vary
from one implementation to another. Moreover, it will be
appreciated that such a development effort might be complex and
time-consuming, but would nevertheless be a routine undertaking for
those of ordinary skill in the art having the benefit of this
disclosure.
[0026] FIG. 1 shows one exemplary embodiment of a communication
system 100 in accordance with one exemplary embodiment of the
present invention. A mobile device 110 connects to a network 120
through a gateway 130 or an access point 140 using a wireless
connection (e.g., an 802.11 type connection) or wired network
connection. The term "mobile" is not intended to be limited to
wireless connections. For example, the mobile device 110 may be a
device that may be plugged into the network 120 at various
locations within a facility. The mobile device 110 employs a voice
over internet protocol (VOIP) protocol for interfacing with a
private branch exchange (PBX) system 150 on the network 120. The
PBX system 150 interfaces with a public switched telephone network
(PSTN) 160.
[0027] Unless otherwise noted, the components of the communication
system 100 are commercially available, and those of ordinary skill
in the art are well versed in their construct and operation.
Accordingly, these components are not described in detail herein.
The communication mechanism employed in the illustrated embodiment
is an open standard communication protocol, such as, but not
limited to a Simple Access Object Protocol (SOAP) developed by
Microsoft Corporation of Redmond, Washington and IBM Corporation of
White Plains, NY.
[0028] To facilitate communication with the PBX system 150, the
mobile device 110 employs a PBX binding layer 170 (e.g.,
implemented in software) that specifies the appropriate commands
for interfacing with the PBX system 150 in accordance with its
proprietary protocol. The PBX binding layer 170, in some
embodiments, is also tailored to the particular requirements of the
mobile device 110. For example, the mobile device 110 in accordance
with its software (not otherwise shown) may generate a command
(e.g., TR1, to implement a call transfer). The PBX system 150 may
expect a different command (e.g., a TR2) to implement a call
transfer in accordance with its internal protocol. The PBX binding
layer 170 includes instructions that specify that an incoming TR1
command from the software of the mobile device should be converted
to an outgoing TR2 command for the PBX system 150. A different type
of mobile device may use a different incoming command, and a
different type of PBX system may use a different outgoing command.
In another embodiment, the mobile device may issue a generic
transfer command, and the PBX binding layer 170 need only define
the particular requirements of the particular PBX system 150
implementation.
[0029] Those of ordinary skill in the art are familiar with the
commands used by the commercially available mobile devices and PBX
systems, and are thus fully able to construct a PBX binding layer
170 compatible with the particular devices chosen. Accordingly, for
clarity and to avoid obscuring the instant invention, further
details are not provided as to this aspect of implementing the
illustrated embodiment.
[0030] In various alternative embodiments, the mobile device 110
may be a VOIP telephone, a personal data assistant (PDA), a
portable computer, a desktop computer, etc. Voice and/or data
signals may be transmitted between the mobile device 110 and the
gateway 130 and/or AP 140. In one embodiment, the voice and/or data
signals may be transmitted between mobile device 110 and the
gateway 130 and/or AP 140 using a modulated radio signal having a
common frequency, such as a 2.4 GHz modulated carrier radio signal.
Although a separate gateway 130 and AP 140 are illustrated, both
need not be present in all embodiments. Also, an AP 140 may be
configured to act as both a gateway and an AP. Hence, in the
following examples, when the mobile device 110 is said to be
connecting to the gateway 130, it is meant to include the situation
where an AP 140 functions as a gateway 130. Although the following
description describes communication through the gateway 130 or AP
140, the invention is not so limited, and other interface agents
may be used. For example, the mobile device 110 may connect to the
network 120 through interface agents, such as, but not limited to,
the gateway 130, the AP 140, a wired or wireless switch (not
shown), a server (not shown), etc.
[0031] When the mobile device 110 establishes a connection to the
network 120 through the gateway 130, the gateway 130 first
establishes the identity of the user using the mobile device 110 by
an exchange of user and password information. Upon identifying the
user, the gateway 130 determines if the user has access to voice
functions (i.e., access to the PBX system 150) in accordance with
their account. The gateway 130 then provides PBX identity
information specifying the identity of the PBX system 150. The PBX
identity information may specify both the identity of the PBX
system 150 and its associated PBX protocol, or simply just the
manufacturer and model information for the PBX system 150.
[0032] Based on the PBX identity information, the gateway 130 or
the mobile device 110 accesses a library of binding layers 180 to
determine the appropriate PBX binding layer 170 with which to
configure the mobile device 110. Note that the "appropriate" PBX
binding layer 170 will be one that converts between the commands
issued by the software of the mobile device 110 and those employed
by the PBX system 150. Potential locations for the library 180 and
how the appropriate PBX binding layer 170 is provided to the mobile
device 110 are discussed in greater detail below. Although FIG. 1
illustrates multiple libraries 180, it is not required that each of
the individual libraries 180 be present in all embodiments. For
example, if the gateway 130 is tasked with identifying the
appropriate PBX binding layer 170, the libraries 180 on the mobile
device 110 and the network 120 may be omitted.
[0033] Upon receiving the appropriate PBX binding layer 170, the
mobile device 110 is configured to access the PBX system 150 and
the gateway 130 specifies the particular features the user is
authorized to access on the PBX system 150 based on the user's
profile information. For example, different users may have
different profiles that define their respective abilities to access
local or long distance services over the PSTN 160, internal
extensions within the PBX system 150, voice mail, call forwarding,
call waiting, etc.
[0034] FIG. 2A illustrates a simplified diagram of entries 200 in
the library of binding layers 180. Note that the library 180 may be
implemented using any suitable data structure known to the art. In
the illustrated embodiment of FIG. 2A, each entry 200 includes a
binding layer 210 indexed by a mobile device type field 220 and a
PBX type field 230. Upon determining the type of mobile device 110
accessing the PBX system 150 and the type of PBX system 150 being
accessed, the appropriate binding layer 210 may be selected. As
will be described in greater detail below, depending on the
particular implementation, one of the type fields 220, 230 may be
omitted.
[0035] In a first illustrative embodiment, the gateway 130 is
tasked with providing the mobile device 110 with the appropriate
PBX binding layer 170. The library of binding layers 180 may be
resident on the gateway 130 (e.g., on a computer functioning as the
gateway 130). In this case, the gateway 130 would know the PBX type
information ahead of time. As shown in FIG. 2B, the entries 200 in
the library 180 need only be for that particular PBX type, and the
PBX type field 230 (seen in FIG. 2A) may be omitted. When the
mobile device 110 connects with the gateway 130 it provides the
gateway 130 with identity information specifying its device type
(e.g., model X wireless phone, model Y PDA, or model Z notebook
computer). The gateway 130 accesses the library 180 based on the
mobile device type and selects the corresponding entry 200 and
binding layer 210 to provide to the mobile device 110.
[0036] In another embodiment, the gateway 130 may access the
library 180 over the network 120. The library 180 may be stored in
another location on the network 120 or in another location
accessible through, for example, an Internet connection. For
instance, a PBX or mobile device manufacturer or some other entity
may provide a library 180 accessible through a web site storing
various binding layers 210. The gateway 130, may access the library
180 based on its knowledge of the PBX system type and the mobile
device type to secure the appropriate binding layer 210 for
providing to the mobile device 110.
[0037] In yet another embodiment, the mobile device 110 may store
the library 180 and configure itself based on PBX type information
provided by the gateway 130 about the PBX system 150. As seen in
FIG. 2C, the mobile device type field 220 may be omitted, because
the mobile device 110 need only store binding layers 210 for its
particular device type. In this embodiment, the gateway 130
provides the mobile device 110 with the PBX type information when
the mobile device 110 initiates a connection. Based on the PBX type
information, the mobile device 110 accesses the PBX type field 230
to identify the appropriate binding layer 210 to use as its PBX
binding layer 170.
[0038] The communication system 100 may have one or more libraries
180 installed, depending on the particular implementation. For
example, if the mobile device 110 is unable to locate a proper
binding layer 210 in its library 180, the gateway 130 may access
its own internal library 180 and attempt to locate a proper binding
layer 210. If the gateway 130 is still unable to locate a proper
binding layer 210, it may access an external library 180 on the
network 120 or accessible through the Internet to find the proper
binding layer 210 for the particular mobile device 110. This
multi-tier arrangement may be useful in a situation where new types
or generations of mobile devices 110 are expected, and the library
180 is not expected to remain static.
[0039] Turning now to FIG. 3, an alternative embodiment of a
communication system 300 is provided. In the embodiment of FIG. 3,
multiple systems 310, 320 on separate networks 330, 340 are
provided. Each system 310, 320 has a respective gateway 350, 360
that interfaces with a respective PBX system 370, 380. Again,
although a gateway 350, 360 is illustrated, access points (not
shown may be provided for performing similar functions). In the
illustrated embodiment, the PBX systems 370, 380 are of a different
type (e.g., manufacturer or model number) and employ different
internal protocols.
[0040] In the embodiment of FIG. 3, the wireless device 110 roams
such that the gateway 350 passes responsibility for the mobile
device 110 to the gateway 360. Those of ordinary skill in the art
are familiar with such hand-off operations and the appropriate
steps necessary to complete the transition. However, since the PBX
systems 370, 380 are of different types, the mobile device 110 may
need to reconfigure its PBX binding layer 170 during the
transition. The mobile device 110 may become the hand-over agent in
this case.
[0041] As the mobile device 110 comes into range of the system 320
from the range of the system 310, the gateway 360 initiates the
hand-off procedure and informs the gateway 350 that it will be
taking over responsibility for the mobile device 110. The gateway
360 and mobile device 110 then perform a configuration procedure
similar to that described above in reference to FIG. 1. Either the
gateway 360 or the mobile device 110 will identify a PBX binding
layer 170 for the mobile device 110 based on the type of the mobile
device 110 and the type of the PBX system 380. Then when the
gateway 360 and the mobile device 110 are ready to complete the
transition, the mobile device 110 can load the appropriate PBX
binding layer 170 and operation may continue. Either the gateways
350, 360 may coordinate the hand-over, or alternatively, the mobile
device 110 may coordinate the hand-over.
[0042] Turning now to FIG. 4, a simplified block diagram of a
method for configuring a mobile device 110 in accordance with
another exemplary embodiment of the present invention is provided.
In block 400, a request for connecting a mobile device 110 having a
mobile device type to a communications network 100 including a
private branch exchange (PBX) system 150 having a PBX type is
received. In block 410, identification information including at
least one of the mobile device type and the PBX type is provided.
In block 420, a PBX binding layer 170 is selected based on the
identification information. In block 430, the selected PBX binding
layer 170 is provided to the mobile device 110 for interfacing with
the PBX system 150.
[0043] Referring briefly to FIG. 5, a simplified block diagram of
the mobile device 110 is provided. The mobile device 110 includes a
processing unit 112 (e.g., a microprocessor and associated memory
and bus circuitry) and a storage device 114 (e.g., a hard disk,
floppy disk, programmable memory, CR-ROM disk, etc.) adapted to
store the library of binding layers 180. In the embodiment,
described above where the mobile device 110 houses the library of
binding layers 180, the processing unit 112 is adapted to contact
the gateway 130, receive the PBX type, and select the PBX binding
layer 170 from the library of binding layers 180 based on at least
the PBX type.
[0044] The automatic loading and updating of the PBX binding layer
170, as described herein, allows seamless connectivity through
various VOIP and PBX systems. The user of the mobile device 110 is
thus provided with a consistent user interface regardless of the
underlying PBX system. If the user migrates to a different service
point, the PBX binding layer 170 will be automatically updated, but
the user will have substantially the same interface for interacting
with the new system. The user interface may indicate that a
transfer of networks has occurred, but the manner in which the user
accesses the services on the new network should be essentially the
same as the manner used for the previous network. The user profile
and communication information is managed by the network, so an
administrator may control the user profile from a centralized
location. Also, the user ID and network address provided to the
network during initialization will link to the user profile, thus
allowing a user to use different devices and access the appropriate
services.
[0045] The ease of system administration is increased, as the
user's available services may be controlled based on the user
profile regardless of the protocol used to connect to the PBX
system. The PBX binding layer 170 may include instructions for
enabling the services for which the user is authorized to use based
on the profile. For example, the PBX binding layer 170 will only
provide the instructions for accessing voice mail on the network
120 if the user is authorized to use the voice mail service. Also,
current PBX binding layers may be stored in a centralized location
on the network (i.e., in some embodiments) obviating the need to
update distributed system versions and maintenance levels. A user's
updated binding layer will be automatically loaded upon connection.
In embodiments where the library of binding layers 180 is not
stored on the mobile device 110, the storage space demands on the
mobile device 110 are reduced.
[0046] The particular embodiments disclosed above are illustrative
only, as the invention may be modified and practiced in different
but equivalent manners apparent to those skilled in the art having
the benefit of the teachings herein. Furthermore, no limitations
are intended to the details of construction or design herein shown,
other than as described in the claims below. It is therefore
evident that the particular embodiments disclosed above may be
altered or modified and all such variations are considered within
the scope and spirit of the invention. Accordingly, the protection
sought herein is as set forth in the claims below. following
detailed description is merely illustrative in nature and is not
intended to limit the embodiments of the invention or the
application and uses of such embodiments. Furthermore, there is no
intention to be bound by any expressed or implied theory presented
in the preceding technical field, background, brief summary or the
following detailed description.
* * * * *