(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2009/0201830 A1
`Angelot et al.
`(43) Pub. Date:
`Aug. 13, 2009
`
`US 2009020 1830A1
`
`(54) METHOD & SYSTEM FOR NETWORK
`ENTITY CONFIGURATION
`
`tOrS:
`76) I
`(76) Inventors
`
`Stephane Angelot, (US): David
`S E. age ot, (US); Davi
`
`Correspondence Address:
`GROOVER & Associates
`BOX802889
`DALLAS, TX 75380-2889 (US)
`
`(21) Appl. No.:
`
`11/925,632
`
`(22) Filed:
`
`Oct. 26, 2007
`
`Related U.S. Application Data
`(60) Provisional application No. 60/863,616, filed on Oct.
`31, 2006.
`Publication Classification
`
`(51) Int. Cl.
`(2006.01)
`H04L 2/28
`(52) U.S. Cl. ........................................................ 370/254
`(57)
`ABSTRACT
`A system for configuring a plurality of network entities by a
`central server, each of the network entities being associated
`with a unique identifier, and each of the network entities being
`associated with at least one service provider having configu
`ration settings data therefor.
`
`14
`
`101.144.4.220
`
`22
`
`
`
`12a
`
`00-A1-B2-B3-C4-D5
`
`2b
`
`00-54-11-A2-33-F6
`
`18a
`
`18)
`
`00-54-11-A2-33-F6
`
`
`
`69.85. 101.2
`
`Exhibit 1006
`IPR2023-00581
`U.S. Patent 8,886,772
`
`Page 1 of 12
`
`

`

`Patent Application Publication
`
`Aug. 13, 2009 Sheet 1 of 3
`
`US 2009/02O1830 A1
`
`
`
`22
`
`G
`
`<C>
`
`Cao
`
`|
`
`Page 2 of 12
`
`

`

`Patent Application Publication
`
`Aug. 13, 2009 Sheet 2 of 3
`
`US 2009/02O1830 A1
`
`Assign identifier to network entity 12a
`
`include in a Computer readable medium of the network
`entity 12a URI to the central server 14a, and program.
`COde for requesting Configuration settings
`
`ASSOciate identifier With a Service provider 18a
`
`Provide a mapping table having the identifier and the
`associated Service provider 18aata central server 14
`
`Provide a COInfiguration server 20a With Configuration
`Settings for network entity 12a to Service provider 18a
`
`CauSe the network entity 72a to automatically request
`Configuration Settings from the Central server 14 via the URI
`
`Determine the Service provider 18a matching the identifier
`
`Redirect request to appropriate Configuration server 20a
`
`Cause the configuration server to provide the
`Configuration settings to the identified network entity 12a
`
`100
`
`102
`
`104
`
`106.
`
`108
`
`1 10
`
`112
`
`114
`
`116
`
`End
`
`FIG. 2
`
`Page 3 of 12
`
`

`

`Patent Application Publication
`
`Aug. 13, 2009 Sheet 3 of 3
`
`US 2009/02O1830 A1
`
`
`
`
`
`89
`
`| ||
`
`88 50H
`
`90/M001 dl /0}
`
`Page 4 of 12
`
`

`

`US 2009/020 1830 A1
`
`Aug. 13, 2009
`
`METHOD & SYSTEM FOR NETWORK
`ENTITY CONFIGURATION
`
`CROSS-REFERENCE TO RELATED
`APPLICATIONS
`0001. This application claims the benefit of priority to
`U.S. Provisional Application Ser. No. 60/863,616, filed 31
`Oct. 2006.
`
`BACKGROUND OF THE INVENTION
`0002 1. Field of the Invention
`0003. The present invention relates to packet switched
`networks, and more particularly to configuring network enti
`ties with the requisite settings in order to participate within a
`network.
`0004 2. Description of the Related Art
`0005 IP Telephony (VoIP) is a converged voice/data tech
`nology that uses the data network to carry Voice (telephone)
`traffic, and is rapidly revolutionizing the world of enterprise
`communications. Some benefits of IP telephony include the
`ability to manage individual phone systems, access to a
`plethora of features and applications, improved reliability,
`improved performance, Substantial cost savings and unified
`messaging.
`0006. Another key benefit of VoIP technology is that it
`allows networks to be built using either a centralized or a
`distributed architecture. In general, centralized architectures
`are associated with H.248 and MGCP. These protocols were
`designed for a centralized device called a media gateway
`controller or call agent that handles Switching logic and call
`control. The centralized device communicates with the media
`gateways, which route and transmit the audio/media portion
`of the voice calls. In centralized architectures, the network
`intelligence is centralized and endpoints are relatively dumb
`with limited or no native features. Distributed architectures
`are associated with H.323 and SIP protocols. These protocols
`allow network intelligence to be distributed between end
`points and call-control devices. Intelligence in this instance
`refers to call state, calling features, call routing, configuring,
`billing, or any other aspect of call handling. The endpoints
`can be VoIP gateways, IP phones, media servers, or any
`device that can initiate and/or terminate a VoIP call. The
`call-control devices are called gatekeepers in an H.323 net
`work, and proxy or redirect servers in a SIP network.
`0007. One significant difference between a POTS (plain
`old telephone service) network and a VoIP network is that
`Some architectures and intelligent Subscribergateways and/or
`IP phones now reside on the customer premises. These
`devices may be very complex and require to be configured
`before use, unlike a POTS phone. Therefore easier configu
`ration of Subscriber gateways, or end points becomes impor
`tant as the network scales up. In a hosted PBX or IP Centrex
`environment users simply plug their IP phone 12a into the
`LAN, and the IP phone 12a is auto-configured. However, to
`date, the issue of auto-configuration of IP endpoints in a
`non-hosted PBX, or non-IP centrex environment, has not
`been adequately or satisfactorily addressed. Typically, in a
`non-hosted PBX, or non-IP centrex environment, each cus
`tomer endpoint must be configured, managed and maintained
`individually, and so the user is often tasked to manually enter
`the configuration settings for the device, such as the service
`provider's configuration server address or other network set
`tings. Also, the user must usually prearrange IP telephony
`
`services with an Internet or VoIP service provider in order to
`select the configuration or services options.
`0008. Therefore, the user is burdened with the task of
`reviewing the installation guide, or other documentation in
`order to correctly connect the device to the network. The
`installation process is often not successful, as a certain level
`of knowledge of networking is assumed. Inevitably, the frus
`trated end-user contacts the service provider for Support, and
`the service provider is faced with higher costs during the
`installation process as well as the ongoing Support, operation,
`and upgrades. These costs are significant and can dramati
`cally impact its profitability. Also, slower deployment leads to
`fewer subscriptions, lost market share, decreased ARPU, and
`customer churn.
`0009 For carriers delivering residential VoIP and other IP
`services, mass deployment represents a challenge, as a large
`number of devices have to be configured and Supported. Typi
`cally, the devices are bought from different vendors, and so
`the devices generally require vendor-specific configuration
`settings which must be enabled in the phones for the end-user
`to enjoy the full functionality of the device. Also, mass
`deployment over the Internet is often impeded by lack of
`interoperability and complexity of configurations, and fire
`wall/NAT issues.
`0010. It is an object of the present invention to mitigate or
`obviate at least one of the above-mentioned disadvantages.
`
`SUMMARY OF THE INVENTION
`0011. In one of its aspects, the present invention provides
`a method for automatically configuring at least one network
`entity for participation in a network, the at least one network
`entity being associated with at least one service provider, the
`method comprising the steps of
`0012 assigning an identifier to the at least one network
`entity;
`0013 associating the identifier with at least one service
`provider;
`00.14
`providing a central server having a reference table
`for mapping the identifiers to at least one of the service
`providers,
`00.15
`providing a configuration server associated with
`each of the service providers, the configuration server having
`configuration settings data for the at least one network entity;
`0016 including in a computer-readable medium of the at
`least one network entity instructions for communicating with
`the central server or the configuration server,
`0017 causing the at least one network entity to automati
`cally request configuration settings data from the central
`server when coupled to the network, the request including the
`network entity's identifier;
`0018 receiving the request at the central server and deter
`mining which of the at least one of the service providers is
`associated with the identifier,
`0019 the central server redirecting the request to an
`appropriate configuration server having the configuration set
`tings data specific to the identifier,
`0020 the configuration server providing the configuration
`settings data to the at least one network entity; and
`0021 whereby the at least one network entity is automati
`cally configured without user intervention except to power-on
`and connect the at least one network entity to the network in
`order to contact the central server.
`0022. In another of its aspects, the present invention pro
`vides a system for configuring a plurality of network entities
`
`Page 5 of 12
`
`

`

`US 2009/020 1830 A1
`
`Aug. 13, 2009
`
`for implementation in a network with minimal end-user inter
`vention, each of the network entities being associated with an
`identifier, and each of the network entities being associated
`with at least one service provider, the system having:
`0023 a computer-readable medium of each of the network
`entities having a program for executing instructions to com
`municatively couple each of the network entities to a central
`server to request configuration settings data matching the
`network entity's identifier, the central server including a first
`mapping table comprising a list of the identifiers associated
`with each of the service providers, the first mapping table
`being used to redirect the request to a appropriate configura
`tion server associated with each of the service providers, the
`configuration server including a second mapping table com
`prising a list of the identifiers and the configuration settings
`data associated therewith.
`0024. In another of its aspects, the present invention pro
`vides a network entity for participating in a packet Switched
`network, the network entity having a identifier and being
`configured automatically via a central server, the network
`entity being associated with at least one service provider, the
`network entity having:
`0025 a computer-readable medium comprising URI data
`for the central server and a program for executing instructions
`to communicatively couple the network entity to the central
`server via the network, and to request configuration settings
`data matching the network entity's identifier, the request
`being redirected to an appropriate configuration server based
`on the identifier, the configuration server having configura
`tion settings data associated with the identifier and specific to
`the network entity.
`0026. In another of its aspects, the present invention pro
`vides a machine-readable medium having embodied thereon
`a computer program for processing by a central server, the
`computer program for providing instructions to configure a
`plurality of network devices associated with a plurality of
`service providers, each network device having an identifier,
`the instructions being provided in response to requests for
`configuration settings data from the network devices, the
`request including the identifier, the machine-readable
`medium comprising:
`0027 a first sub-program coded to associate the identifier
`to at least one of the service providers to form a first mapping
`table for each service provider, the first sub-program coded to
`analyze the requests from each of the network devices, and to
`determine whether the first mapping table comprises the iden
`tifier;
`0028 a second sub-program coded to redirect each of the
`requests to an appropriate service provider based on the iden
`tifier; the configuration server including a second mapping
`table comprising a list of the identifiers and the configuration
`settings data associated therewith.
`0029. In another of its aspects, the present invention pro
`vides a redirect server to be implemented within a network
`having at least one network device, the redirect server for
`auto-configuring the network devices, the network devices
`being associated with different service providers, and at least
`one of the service providers requiring specific configuration
`settings data for each of the network devices, each of the
`network devices having an identifier, the redirect server com
`prising:
`0030 a machine-readable medium having embodied
`thereon a computer program for processing by the redirect
`server, the computer program coded to provide instructions
`
`for configuring the network devices, the instructions being
`provided in response to requests for configuration settings
`data from the network devices, each of the requests including
`the identifier, the machine-readable medium comprising:
`0031 a first sub-program coded to associate the identifier
`with at least one of the service providers to form a first
`mapping table; the first Sub-program coded to analyze each of
`the requests from the network devices, and to determine
`whether the first mapping table comprises the identifier;
`0032 a second sub-program coded to redirect each of the
`requests to an appropriate service provider based on the iden
`tifier; the configuration server including a second mapping
`table comprising a list of the identifiers and the configuration
`settings data associated therewith.
`0033 Advantageously, by facilitating substantially
`hassle-free installations or configuration of IP endpoints for
`end-users, the operational burden of service activation,
`requests for Support for installation or technical assistance are
`Substantially diminished or eliminated. Consequently, Ser
`Vice providers are presented with a competitive time-to mar
`ket and a service cost advantage. Additionally, service pro
`viders have the freedom to choose any number of IP endpoints
`from numerous manufacturers without being concerned
`about the resources normally required to provision the IP
`endpoints using prior art methods.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`0034 Several preferred embodiments of the present
`invention will now be described, by way of example only,
`with reference to the appended drawings in which:
`0035 FIG. 1 shows a schematic diagram of a system for
`configuring an IP device, in a preferred embodiment.
`0036 FIG. 2 is a flowchart outlining exemplary steps in a
`method for configuring an IP device; and
`0037 FIG. 3a is an exemplary first mapping table com
`prising IP device information and associated service provider.
`0038 FIG.3b is an exemplary second mapping table com
`prising IP device information and associated configuration
`parameters.
`
`DETAILED DESCRIPTION OF EXEMPLARY
`EMBODIMENTS
`0039. The detailed description of exemplary embodiments
`of the invention herein makes reference to the accompanying
`block diagrams and schematic diagrams, which show the
`exemplary embodiment by way of illustration and its best
`mode. While these exemplary embodiments are described in
`sufficient detail to enable those skilled in the art to practice the
`invention, it should be understood that other embodiments
`may be realized and that logical and mechanical changes may
`be made without departing from the spirit and scope of the
`invention. Thus, the detailed description herein is presented
`for purposes of illustration only and not of limitation. For
`example, the steps recited in any of the method or process
`descriptions may be executed in any order and are not limited
`to the order presented.
`0040. Moreover, it should be appreciated that the particu
`lar implementations shown and described herein are illustra
`tive of the invention and its best mode and are not intended to
`otherwise limit the scope of the present invention in any way.
`Indeed, for the sake of brevity, certain sub-components of the
`individual operating components, conventional data net
`working, application development and other functional
`
`Page 6 of 12
`
`

`

`US 2009/020 1830 A1
`
`Aug. 13, 2009
`
`aspects of the systems may not be described in detail herein.
`Furthermore, the connecting lines shown in the various fig
`ures contained herein are intended to represent exemplary
`functional relationships and/or physical couplings between
`the various elements. It should be noted that many alternative
`or additional functional relationships or physical connections
`may be present in a practical system.
`0041. The present invention may also be described herein
`in terms of Screen shots and flowcharts, optional selections
`and various processing steps. Such functional blocks may be
`realized by any number of hardware and/or software compo
`nents configured to perform to specified functions. For
`example, the present invention may employ various inte
`grated circuit components (e.g., memory elements, process
`ing elements, logic elements, look-up tables, and the like),
`which may carry out a variety of functions under the control
`of one or more microprocessors or other control devices.
`Similarly, the software elements of the present invention may
`be implemented with any programming or Scripting language
`such as C, C++, Java, COBOL, assembler, PERL, extensible
`markup language (XML), Smart card technologies with the
`various algorithms being implemented with any combination
`of data structures, objects, processes, routines or other pro
`gramming elements. Further, it should be noted that the
`present invention may employ any number of conventional
`techniques for data transmission, signaling, data processing,
`network control, and the like.
`0042. As is known in the art, Internet Protocol (IP) is a
`routing protocol designed to route traffic within a network or
`between networks. IP is described in IETF RFC-791, incor
`porated herein by reference. However, the present invention is
`not limited to IP data interfaces and other data interfaces can
`also be used.
`0043 FIG. 1 illustrates a system 10 for configuring a plu
`rality of network entities 12a, 12b, 12c via a central server 14
`with minimal end-user intervention, wherein minimal user
`intervention involves powering on and connecting the net
`work entity 12a, 12b, or 12c to a network 16. The network
`entities 12a, 12b, 12c may be any IP device or endpoint (end
`node) for participating in a packet Switched network, such as,
`but not limited to, IP phones, H.323 phones, DECT phones,
`SIP-DECT phones, ATAs, mobile phones, IPTVs, projectors,
`PDAs, digital cameras, PC, MP3 players, set-top boxes, game
`consoles, gateways, Soft phones, firewalls, access-points,
`modems, network appliances, or any combination(s) thereof.
`These exemplary network entities 12a, 12b, 12c include a
`data processing means comprising a processor (which may be
`referred to as a central processor unit or CPU, logic means, or
`controller) that is in communication with a machine-readable
`medium (computer-readable medium), input/output (I/O)
`devices, a network interface, and other interfaces. A com
`puter-readable medium is any physical object that can store
`information in a form directly readable by a computer. Thus,
`magnetic, optical, and electrical storage devices are all con
`templated, as well as any other method of storing information
`directly accessible to a computer. Hard disks, floppy disks,
`CD/DVD ROM drives, RAM chips, magnetic tapes, bar
`codes, punch cards, and the like are all examples of computer
`readable media.
`0044. The network 16 can include a series of network
`nodes (e.g., the clients and servers) that can be interconnected
`by network devices and wired and/or wireless communica
`tion lines (such as, public carrier lines, private lines, satellite
`lines, etc.) that enable the network nodes to communicate.
`
`The transfer of data between network nodes can be facilitated
`by network devices, such as routers, Switches, multiplexers,
`bridges, gateways, etc., that can manipulate and/or route data
`from an originating node to a server node regardless of dis
`similarities in the network topology (such as, bus, star, token
`ring, mesh, or hybrids thereof), spatial distance (such as,
`LAN, MAN, WAN, Internet), transmission technology (such
`as, TCP/IP. Systems Network Architecture), data type (such
`as, data, Voice, video, multimedia), nature of connection
`(such as, Switched, non-Switched, dial-up, dedicated, or Vir
`tual), and/or physical link (Such as, optical fiber, coaxial
`cable, twisted pair, wireless, etc.) between the correspondents
`within the network.
`0045 Generally, the network entities 12a, 12b, 12c are
`vended to a plurality of service providers 18a, 18b, 18c by a
`manufacturer or a distributor. The network entities 12a, 12b,
`12care provisioned with a unique resource identifier (URI) of
`the central server 14 already embedded in the firmware,
`including other instruction codes/software programs stored in
`the computer-readable medium. The Software application
`code may also be implemented in hardware via a dedicated
`device incorporating control logic or a controller, for
`example. The Software application code includes Software
`instructions to be executed by the processor. Alternatively, the
`Software may be executed by a controller, or control logic on
`the device. The central server 14 is preferably remotely based
`and serves as a central depository of configuration informa
`tion related to the network entities 12a, 12b, 12c, and may be
`communicatively coupled to a plurality of configuration serv
`ers 20a, 20b, 20c, or other entities on the network 16. The
`central server 14 and configuration servers 20a, 20b, 20c, also
`include data processing means comprising a processor
`(which may be referred to as a central processor unit or CPU,
`logic means, or controller) that is in communication with a
`computer-readable medium having data and/or program
`code, input/output (I/O) devices, a network interface, and
`other interfaces. The central server 14 and configuration serv
`ers 20a, 20b, 20c are scalable, robust and include failover
`capabilities and built-in redundancies.
`0046. After the network entities 12a, 12b, 12c are first
`powered on and communicatively coupled to the network via
`a network interface, the network entities 12a, 12b, 12c auto
`matically execute a program to contact the central server 14,
`out of the box. The term “communicatively coupled' is used
`in its broadest sense to mean coupling in any fashion that
`allows information to be passed between network entities
`12a, 12b, 12c, and other network devices within the network
`16, Such as the central server 14, configuration servers 20a,
`20b or 20c, or other servers, gateways, routers, switches, and
`So forth. Thus, for example, communicatively coupled net
`work entities 12a, 12b, 12c can be coupled either directly or
`indirectly via electromagnetic signals, such as electrically
`coupled, optically coupled, wirelessly coupled; and/or physi
`cally coupled. The network entities 12a, 12b, 12c thus send a
`request for configuration settings from the central server 14.
`As each of the network entities 12a, 12b or 12c may be
`procured from different manufacturers (OEMs), the configu
`ration settings thus tend to be manufacturer-specific.
`0047 Upon receipt of the configuration settings request,
`the central server 14 identifies the querying network entity
`12a, 12b, or 12c, and the central server 14 responds with a
`URI to an appropriate configuration server 20a, 20b, or 20c
`associated with one of the service providers 18a, 18b. 18c,
`holding the actual configuration for the network entity 12a.
`
`Page 7 of 12
`
`

`

`US 2009/020 1830 A1
`
`Aug. 13, 2009
`
`12b, or 12c. Alternatively, the central server 14 forwards the
`query to the appropriate configuration server 20a, 20b. 20c
`based on the identity of the network entity 12a, 12b, or 12c.
`AS Such, the central server 14 redirects any configuration
`related queries from the network entity 12a, 12b, or 12c to the
`configuration server 20a, 20b, 20c, therefore the central
`server 14 may be also be termed a “redirect server'. In either
`case, the configuration settings are provided to the network
`entity 12a, 12b, or 12c, and so each of the network entities
`12a, 12b, or 12c is automatically configured without requir
`ing any manual input of settings by the user.
`0048 Referring to FIG. 2, the flowchart shows exemplary
`steps for automatically configuring a network entity, such as
`an IP phone 12a supplied by a manufacturer or a network
`equipment provider. For convenience the ensuing description
`will focus on an IP phone 12a for participation within the
`packet-switched network 16. In one exemplary situation, Ser
`vice providers 18a, 18b. 18c, may purchase the same IP
`phone 12a, having identical functions and capabilities, from
`one manufacturer or network equipment provider, for deploy
`ment within their own sub-network, or network 16. Often
`times each of the service providers 18a, 18b, or 18c requires
`different configurations settings for the same IP phone 12a for
`full functionality on their own sub-network, or to access the
`service provider's resources or services. Therefore, the con
`figuration settings are typically service provider-specific, as
`well as manufacturer-specific, and so there is a lack of
`interoperability between the service providers 18a, 18b, and
`18c. This is often frustrating to an end-user desiring to seam
`lessly switch between service providers 18a, 18b or 18c,
`while using the same IP phone 12a.
`0049. A method for automatically configuring the IP
`phone 12a for use with at least one service provider 18a, 18b
`or 18d, is thus desirable to an end-user. An exemplary method
`for configuring the IP phone 12 comprises the step(s) of
`assigning an identifier to the IP phone 12a, the identifier may
`be a unique identifier, or a class identifier. One form of unique
`identification is provided by a globally unique network inter
`face identifier (media access control (MAC) address). The
`unique MAC address is assigned to the IP phone 12a by the
`manufacturer or the network equipment provider (step 100).
`The MAC address is associated with the IP phone 12a's
`network interface adapter for coupling to the network 16, and
`includes an encoding comprising six groups of two hexadeci
`mal digits, for example 00-a1-b2-b3-c4-d5. The first three
`octets (in transmission order) 00-a1-b2 identify the manufac
`turer (or organization) that issued the identifier (and hence the
`network interface adapter) and are known as the Organiza
`tionally Unique Identifier (OUI). The next three octets, b3-c4
`d5, are assigned by that organization in any suitable manner
`but Subject to the constraint of uniqueness.
`0050. The computer-readable medium of the IP phone 12a
`is included with factory-set default configuration data, Such
`as, DHCP settings (enabled), a URI to a central server 14
`having information related to the IP phone 12a's configura
`tion settings. The URI of the central server 14 may be a public
`name/IP address, for example, connect.aastra.com, however,
`the URI may be customized as part of the branding for a
`partner/customer in an OEM agreement. Also, the computer
`readable medium, or firmware, is coded to execute instruc
`tions for communicatively coupling the IP phone 12a to the
`central server 14 (step 102). The IP phone 12a automatically
`initiates a discovery process, in which it sends messages over
`any suitable transport protocol, such as UDP, TCP, TLS,
`
`HTTP(S), FTP or TFTP in order to retrieve its settings from
`a remote central server 14. The instructions are simply steps
`to be carried out by a processor, and may be provided by
`hardware, software, firmware, or any suitable combination
`thereof.
`0051. As part of the provisioning process the MAC
`address of the IP phone 12a, is associated with at least of the
`service providers 18a, 18b, or 18c (step 104), at the central
`server 14. Preferably, a central server 14 includes a database
`22 for storing the records of the MAC addresses and the
`associated service provider 18a, 18b, or 18C, such as a first
`mapping table which is maintained in a memory associated
`with the central server 14 (step 106), as shown in FIG.3a. For
`each customer or service provider 18a, 18, or 18C, a password
`protected account is created on the central server 14. The
`database 22 may be populated through a web portal acces
`sible to the service providers 18a, 18b, 18c, or via a suitable
`API. The central server 14 includes an admin web portal via
`certain administrative tasks may be performed. Such as: Cre
`ate/Modify/Delete a customer account, Create/Modify/De
`lete a record. For example, when a customer account is
`deleted, all the records linked to this account are deleted. The
`customer accounts are stored in the database 22, and may
`include the following fields: Name, Password, Company,
`Contact name, Email address, Phone number, and Last login.
`As stated above, every MAC address added to the central
`server database 22a is linked to one customer account.
`0052 Each service provider 18a, 18b, or 18c is provided
`with a configuration server 20a, 20b or 20c having configu
`ration settings for the IP phone 12a (step 108). The configu
`ration servers 20a, 20b. 20c are coupled to the central server
`14a, such that queries for configuration settings may be redi
`rected thereto based on the first mapping table. The configu
`ration server 20a, 20b or 20c includes configuration settings
`specific to the IP phone 12a with specific MAC addresses.
`Each service provider 18a, 18b or 18c thus includes a second
`mapping table with MAC addresses and associated configu
`ration settings data in a database associated with each of the
`configuration servers 20a, 20b or 20c. As each IP phone 12a
`is typically identified by its MAC address, the configuration
`files on the configuration server 20a may be named using this
`information, for example, a configuration file named
`iphone 12a-mac-00-a1-b2-b3-c4-d5.cfg would correspond to
`the IP phone 12a having 00-a1-b2-b3-c4-d5 as its MAC
`address. The configuration settings may include phone spe
`cific configuration information, and platform specific con
`figuration information, Such as, but not limited to, the type of
`phone, carrier, service, or enterprise system information, cen
`tral server(s) URIs, configuration server(s) URI, port assign
`ments, registration information, dial plan, NTP time settings,
`soft-keys, XML services and applications, SIP registration
`information, usernames and passwords, phone book direc
`tory, speaker Volume settings and so forth. Firmware
`upgrades/downgrades may also be provided to the IP phone
`12a based on the MAC address. An exemplary second map
`ping configuration table includes: MAC address, AccountD.
`Date and time of last update, Transport Mechanism, Param
`eter 1, Parameter 2, Parameter 3, Parameter n, as shown in
`FIG. 3b.
`0053. The central server 14 includes a user Web portal to
`allow the customers or service providers 18a, 18b, 18c to
`configure the MAC address of the IP phones 12a and the
`associated configuration parameters. The customers or ser
`vice providers 18a, 18b, 18c access the Web portal using an
`
`Page 8 of 12
`
`

`

`US 2009/020 1830 A1
`
`Aug. 13, 2009
`
`account name and password, and may perform a number of
`administrative operations, such as, adding a record, modify
`ing a record, deleting a record, change the account password,
`or upload an excel file or a csv file with a plurality of MAC
`addresses when configuring a large number of IP phones 12a.
`Alternatively, an XML API may be used to add such records.
`The central sever 14 verifies that each MAC address to be
`added is unique before inclusion in the database 22.
`0054. In execution, the IP phone 12a software application
`code causes the processor to transmit a first signal to request
`configuration settings associated with the IP phone 12a (Step
`110) from the central server 14. In step 112, the central server
`14 receives a request for configuration settings from the IP
`phone 12a. The request includes the identity data of the IP
`phone 12a, Such as the unique MAC address. Upon receipt of
`the request, the central server 14 processes the request to
`determine whether the first mapping table comprises the
`unique MAC address associated with the request, and also
`determines which of the plurality of service provi