Method and system for network entity configuration

CROSS-REFERENCE TO RELATED APPLICATIONS

p-0002This application claims the benefit of priority to U.S. Provisional Application Ser. No. 60/863,616, filed 31 Oct. 2006.

BACKGROUND OF THE INVENTION

p-00031. Field of the Invention

p-0004The present invention relates to packet switched networks, and more particularly to configuring network entities with the requisite settings in order to participate within a network.

p-00052. Description of the Related Art

p-0006IP Telephony (VoIP) is a converged voice/data technology 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.

p-0007Another 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 endpoints 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 network, and proxy or redirect servers in a SIP network.

p-0008One significant difference between a POTS (plain old telephone service) network and a VoIP network is that some architectures and intelligent subscriber gateways 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 configuration of subscriber gateways, or end points becomes important as the network scales up. In a hosted PBX or IP Centrex environment users simply plug their IP phone <b>12</b><i>a </i>into the LAN, and the IP phone <b>12</b><i>a </i>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 customer end point 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 settings. 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.

p-0009Therefore, 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 frustrated 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 dramatically impact its profitability. Also, slower deployment leads to fewer subscriptions, lost market share, decreased ARPU, and customer churn.

p-0010For 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. Typically, 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 firewall/NAT issues.

p-0011It is an object of the present invention to mitigate or obviate at least one of the above-mentioned disadvantages.

SUMMARY OF THE INVENTION

p-0012In 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:

p-0013assigning an identifier to the at least one network entity;

p-0014associating the identifier with at least one service provider;

p-0015providing a central server having a reference table for mapping the identifiers to at least one of the service providers,

p-0016providing a configuration server associated with each of the service providers, the configuration server having configuration settings data for the at least one network entity;

p-0017including in a computer-readable medium of the at least one network entity instructions for communicating with the central server or the configuration server;

p-0018causing the at least one network entity to automatically request configuration settings data from the central server when coupled to the network, the request including the network entity's identifier;

p-0019receiving the request at the central server and determining which of the at least one of the service providers is associated with the identifier;

p-0020the central server redirecting the request to an appropriate configuration server having the configuration settings data specific to the identifier;

p-0021the configuration server providing the configuration settings data to the at least one network entity; and

p-0022whereby the at least one network entity is automatically 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.

p-0023In another of its aspects, the present invention provides a system for configuring a plurality of network entities for implementation in a network with minimal end-user intervention, 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:

p-0024a computer-readable medium of each of the network entities having a program for executing instructions to communicatively 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 configuration server associated with each of the service providers, the configuration server including a second mapping table comprising a list of the identifiers and the configuration settings data associated therewith.

p-0025In another of its aspects, the present invention provides 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:

p-0026a 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 configuration settings data associated with the identifier and specific to the network entity.

p-0027In another of its aspects, the present invention provides 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:

p-0028a 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 identifier;

p-0029a second sub-program coded to redirect each of the requests to an appropriate service provider based on the identifier; the configuration server including a second mapping table comprising a list of the identifiers and the configuration settings data associated therewith.

p-0030In another of its aspects, the present invention provides 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 comprising:

p-0031a 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:

p-0032a 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;

p-0033a second sub-program coded to redirect each of the requests to an appropriate service provider based on the identifier; the configuration server including a second mapping table comprising a list of the identifiers and the configuration settings data associated therewith.

p-0034Advantageously, 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, service providers are presented with a competitive time-to market and a service cost advantage. Additionally, service providers 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

p-0035Several preferred embodiments of the present invention will now be described, by way of example only, with reference to the appended drawings in which:

p-0036<figref idrefs="DRAWINGS">FIG. 1</figref> shows a schematic diagram of a system for configuring an IP device, in a preferred embodiment.

p-0037<figref idrefs="DRAWINGS">FIG. 2</figref> is a flowchart outlining exemplary steps in a method for configuring an IP device; and

p-0038<figref idrefs="DRAWINGS">FIG. 3</figref><i>a </i>is an exemplary first mapping table comprising IP device information and associated service provider.

p-0039<figref idrefs="DRAWINGS">FIG. 3</figref><i>b </i>is an exemplary second mapping table comprising IP device information and associated configuration parameters.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

p-0040The 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.

p-0041Moreover, it should be appreciated that the particular implementations shown and described herein are illustrative 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 networking, application development and other functional aspects of the systems may not be described in detail herein. Furthermore, the connecting lines shown in the various figures 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.

p-0042The 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 components configured to perform to specified functions. For example, the present invention may employ various integrated circuit components (e.g., memory elements, processing 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 programming 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.

p-0043As 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, incorporated herein by reference. However, the present invention is not limited to IP data interfaces and other data interfaces can also be used.

p-0044<figref idrefs="DRAWINGS">FIG. 1</figref> illustrates a system <b>10</b> for configuring a plurality of network entities <b>12</b><i>a</i>, <b>12</b><i>b</i>, <b>12</b><i>c </i>via a central server <b>14</b> with minimal end-user intervention, wherein minimal user intervention involves powering on and connecting the network entity <b>12</b><i>a</i>, <b>12</b><i>b</i>, or <b>12</b><i>c </i>to a network <b>16</b>. The network entities <b>12</b><i>a</i>, <b>12</b><i>b</i>, <b>12</b><i>c </i>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 <b>12</b><i>a</i>, <b>12</b><i>b</i>, <b>12</b><i>c </i>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 computer-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 contemplated, 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, barcodes, punch cards, and the like are all examples of computer-readable media.

p-0045The network <b>16</b> 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 communication 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 dissimilarities 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 virtual), and/or physical link (such as, optical fiber, coaxial cable, twisted pair, wireless, etc.) between the correspondents within the network.

p-0046Generally, the network entities <b>12</b><i>a</i>, <b>12</b><i>b</i>, <b>12</b><i>c </i>are vended to a plurality of service providers <b>18</b><i>a</i>, <b>18</b><i>b</i>, <b>18</b><i>c </i>by a manufacturer or a distributor. The network entities <b>12</b><i>a</i>, <b>12</b><i>b</i>, <b>12</b><i>c </i>are provisioned with a unique resource identifier (URI) of the central server <b>14</b> 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 <b>14</b> is preferably remotely based and serves as a central depository of configuration information related to the network entities <b>12</b><i>a</i>, <b>12</b><i>b</i>, <b>12</b><i>c</i>, and may be communicatively coupled to a plurality of configuration servers <b>20</b><i>a</i>, <b>20</b><i>b</i>, <b>20</b><i>c</i>, or other entities on the network <b>16</b>. The central server <b>14</b> and configuration servers <b>20</b><i>a</i>, <b>20</b><i>b</i>, <b>20</b><i>c</i>, 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 <b>14</b> and configuration servers <b>20</b><i>a</i>, <b>20</b><i>b</i>, <b>20</b><i>c </i>are scalable, robust and include failover capabilities and built-in redundancies.

p-0047After the network entities <b>12</b><i>a</i>, <b>12</b><i>b</i>, <b>12</b><i>c </i>are first powered on and communicatively coupled to the network via a network interface, the network entities <b>12</b><i>a</i>, <b>12</b><i>b</i>, <b>12</b><i>c </i>automatically execute a program to contact the central server <b>14</b>, 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 <b>12</b><i>a</i>, <b>12</b><i>b</i>, <b>12</b><i>c</i>, and other network devices within the network <b>16</b>, such as the central server <b>14</b>, configuration servers <b>20</b><i>a</i>, <b>20</b><i>b </i>or <b>20</b><i>c</i>, or other servers, gateways, routers, switches, and so forth. Thus, for example, communicatively coupled network entities <b>12</b><i>a</i>, <b>12</b><i>b</i>, <b>12</b><i>c </i>can be coupled either directly or indirectly via electromagnetic signals, such as electrically coupled, optically coupled, wirelessly coupled; and/or physically coupled. The network entities <b>12</b><i>a</i>, <b>12</b><i>b</i>, <b>12</b><i>c </i>thus send a request for configuration settings from the central server <b>14</b>. As each of the network entities <b>12</b><i>a</i>, <b>12</b><i>b </i>or <b>12</b><i>c </i>may be procured from different manufacturers (OEMs), the configuration settings thus tend to be manufacturer-specific.

p-0048Upon receipt of the configuration settings request, the central server <b>14</b> identifies the querying network entity <b>12</b><i>a</i>, <b>12</b><i>b</i>, or <b>12</b><i>c</i>, and the central server <b>14</b> responds with a URI to an appropriate configuration server <b>20</b><i>a</i>, <b>20</b><i>b</i>, or <b>20</b><i>c </i>associated with one of the service providers <b>18</b><i>a</i>, <b>18</b><i>b</i>, <b>18</b><i>c</i>, holding the actual configuration for the network entity <b>12</b><i>a</i>, <b>12</b><i>b</i>, or <b>12</b><i>c</i>. Alternatively, the central server <b>14</b> forwards the query to the appropriate configuration server <b>20</b><i>a</i>, <b>20</b><i>b</i>, <b>20</b><i>c </i>based on the identity of the network entity <b>12</b><i>a</i>, <b>12</b><i>b</i>, or <b>12</b><i>c</i>. As such, the central server <b>14</b> redirects any configuration related queries from the network entity <b>12</b><i>a</i>, <b>12</b><i>b</i>, or <b>12</b><i>c </i>to the configuration server <b>20</b><i>a</i>, <b>20</b><i>b</i>, <b>20</b><i>c</i>, therefore the central server <b>14</b> may be also be termed a “redirect server”. In either case, the configuration settings are provided to the network entity <b>12</b><i>a</i>, <b>12</b><i>b</i>, or <b>12</b><i>c</i>, and so each of the network entities <b>12</b><i>a</i>, <b>12</b><i>b</i>, or <b>12</b><i>c </i>is automatically configured without requiring any manual input of settings by the user.

p-0049Referring to <figref idrefs="DRAWINGS">FIG. 2</figref>, the flowchart shows exemplary steps for automatically configuring a network entity, such as an IP phone <b>12</b><i>a </i>supplied by a manufacturer or a network equipment provider. For convenience the ensuing description will focus on an IP phone <b>12</b><i>a </i>for participation within the packet-switched network <b>16</b>. In one exemplary situation, service providers <b>18</b><i>a</i>, <b>18</b><i>b</i>, <b>18</b><i>c</i>, may purchase the same IP phone <b>12</b><i>a</i>, having identical functions and capabilities, from one manufacturer or network equipment provider, for deployment within their own sub-network, or network <b>16</b>. Oftentimes each of the service providers <b>18</b><i>a</i>, <b>18</b><i>b</i>, or <b>18</b><i>c </i>requires different configurations settings for the same IP phone <b>12</b><i>a </i>for full functionality on their own sub-network, or to access the service provider's resources or services. Therefore, the configuration settings are typically service provider-specific, as well as manufacturer-specific, and so there is a lack of interoperability between the service providers <b>18</b><i>a</i>, <b>18</b><i>b</i>, and <b>18</b><i>c</i>. This is often frustrating to an end-user desiring to seamlessly switch between service providers <b>18</b><i>a</i>, <b>18</b><i>b </i>or <b>18</b><i>c</i>, while using the same IP phone <b>12</b><i>a. </i>

p-0050A method for automatically configuring the IP phone <b>12</b><i>a </i>for use with at least one service provider <b>18</b><i>a</i>, <b>18</b><i>b </i>or <b>18</b><i>c</i>, is thus desirable to an end-user. An exemplary method for configuring the IP phone <b>12</b> comprises the step(s) of assigning an identifier to the IP phone <b>12</b><i>a</i>, the identifier may be a unique identifier, or a class identifier. One form of unique identification is provided by a globally unique network interface identifier (media access control (MAC) address). The unique MAC address is assigned to the IP phone <b>12</b><i>a </i>by the manufacturer or the network equipment provider (step <b>100</b>). The MAC address is associated with the IP phone <b>12</b><i>a</i>'s network interface adapter for coupling to the network <b>16</b>, and includes an encoding comprising six groups of two hexadecimal digits, for example 00-a1-b2-b3-c4-d5. The first three octets (in transmission order) 00-a1-b2 identify the manufacturer (or organization) that issued the identifier (and hence the network interface adapter) and are known as the Organizationally 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.

p-0051The computer-readable medium of the IP phone <b>12</b><i>a </i>is included with factory-set default configuration data, such as, DHCP settings (enabled), a URI to a central server <b>14</b> having information related to the IP phone <b>12</b><i>a</i>'s configuration settings. The URI of the central server <b>14</b> 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 instructions for communicatively coupling the IP phone <b>12</b><i>a </i>to the central server <b>14</b> (step <b>102</b>). The IP phone <b>12</b><i>a </i>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 <b>14</b>. 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.

p-0052As part of the provisioning process the MAC address of the IP phone <b>12</b><i>a</i>, is associated with at least of the service providers <b>18</b><i>a</i>, <b>18</b><i>b</i>, or <b>18</b><i>c </i>(step <b>104</b>), at the central server <b>14</b>. Preferably, a central server <b>14</b> includes a database <b>22</b> for storing the records of the MAC addresses and the associated service provider <b>18</b><i>a</i>, <b>18</b><i>b</i>, or <b>18</b><i>c</i>, such as a first mapping table which is maintained in a memory associated with the central server <b>14</b> (step <b>106</b>), as shown in <figref idrefs="DRAWINGS">FIG. 3</figref><i>a</i>. For each customer or service provider <b>18</b><i>a</i>, <b>18</b>, or <b>18</b><i>c</i>, a password protected account is created on the central server <b>14</b>. The database <b>22</b> may be populated through a web portal accessible to the service providers <b>18</b><i>a</i>, <b>18</b><i>b</i>, <b>18</b><i>c</i>, or via a suitable API. The central server <b>14</b> includes an admin web portal via certain administrative tasks may be performed, such as: Create/Modify/Delete a customer account, Create/Modify/Delete 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 <b>22</b>, 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 <b>22</b><i>a </i>is linked to one customer account.

p-0053Each service provider <b>18</b><i>a</i>, <b>18</b><i>b</i>, or <b>18</b><i>c </i>is provided with a configuration server <b>20</b><i>a</i>, <b>20</b><i>b </i>or <b>20</b><i>c </i>having configuration settings for the IP phone <b>12</b><i>a </i>(step <b>108</b>). The configuration servers <b>20</b><i>a</i>, <b>20</b><i>b</i>, <b>20</b><i>c </i>are coupled to the central server <b>14</b><i>a</i>, such that queries for configuration settings may be redirected thereto based on the first mapping table. The configuration server <b>20</b><i>a</i>, <b>20</b><i>b </i>or <b>20</b><i>c </i>includes configuration settings specific to the IP phone <b>12</b><i>a </i>with specific MAC addresses. Each service provider <b>18</b><i>a</i>, <b>18</b><i>b </i>or <b>18</b><i>c </i>thus includes a second mapping table with MAC addresses and associated configuration settings data in a database associated with each of the configuration servers <b>20</b><i>a</i>, <b>20</b><i>b </i>or <b>20</b><i>c</i>. As each IP phone <b>12</b><i>a </i>is typically identified by its MAC address, the configuration files on the configuration server <b>20</b><i>a </i>may be named using this information, for example, a configuration file named iphone12a-mac-00-a1-b2-b3-c4-d5.cfg would correspond to the IP phone <b>12</b><i>a </i>having 00-a1-b2-b3-c4-d5 as its MAC address. The configuration settings may include phone specific configuration information, and platform specific configuration information, such as, but not limited to, the type of phone, carrier, service, or enterprise system information, central server(s) URIs, configuration server(s) URI, port assignments, registration information, dial plan, NTP time settings, soft-keys, XML services and applications, SIP registration information, usernames and passwords, phone book directory, speaker volume settings and so forth. Firmware upgrades/downgrades may also be provided to the IP phone <b>12</b><i>a </i>based on the MAC address. An exemplary second mapping configuration table includes: MAC address, AccountID, Date and time of last update, Transport Mechanism, Parameter 1, Parameter 2, Parameter 3, Parameter n, as shown in <figref idrefs="DRAWINGS">FIG. 3</figref><i>b. </i>

p-0054The central server <b>14</b> includes a user Web portal to allow the customers or service providers <b>18</b><i>a</i>, <b>18</b><i>b</i>, <b>18</b><i>c </i>to configure the MAC address of the IP phones <b>12</b><i>a </i>and the associated configuration parameters. The customers or service providers <b>18</b><i>a</i>, <b>18</b><i>b</i>, <b>18</b><i>c </i>access the Web portal using an account name and password, and may perform a number of administrative operations, such as, adding a record, modifying 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 <b>12</b><i>a</i>. Alternatively, an XML API may be used to add such records. The central sever <b>14</b> verifies that each MAC address to be added is unique before inclusion in the database <b>22</b>.

p-0055In execution, the IP phone <b>12</b><i>a </i>software application code causes the processor to transmit a first signal to request configuration settings associated with the IP phone <b>12</b><i>a </i>(step <b>110</b>) from the central server <b>14</b>. In step <b>112</b>, the central server <b>14</b> receives a request for configuration settings from the IP phone <b>12</b><i>a</i>. The request includes the identity data of the IP phone <b>12</b><i>a</i>, such as the unique MAC address. Upon receipt of the request, the central server <b>14</b> 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 providers <b>18</b><i>a</i>, <b>18</b><i>b</i>, <b>18</b><i>c </i>the MAC address belongs to. Once such a determination has been established, the central server <b>14</b> then redirects the request to an appropriate service provider <b>18</b><i>a</i>, <b>18</b><i>b </i>or <b>18</b><i>c</i>, as per first mapping table (step <b>114</b>). In step <b>116</b>, a configuration server <b>20</b><i>a</i>, <b>20</b><i>b </i>or <b>20</b><i>c</i>, associated with the appropriate service provider <b>20</b><i>a</i>, <b>20</b><i>b </i>or <b>20</b><i>c</i>, selects the configuration settings for the IP phone <b>12</b><i>a </i>with that specific MAC address as per second mapping table, and forwards the relevant configuration settings data to the IP phone <b>12</b><i>a</i>. As is apparent from the above-noted exemplary steps, the IP phone <b>12</b><i>a </i>is configured for use with at least one service provider <b>18</b><i>a</i>, <b>18</b><i>b </i>or <b>18</b><i>c</i>, without the requirement for any user intervention, except to power-on the IP phone <b>12</b><i>a </i>and connect it to the network. Therefore, the service provider <b>18</b><i>a</i>, <b>18</b><i>b </i>or <b>18</b><i>c</i>, or the end-user is required to enter the configuration settings manually, thus mitigating against human error. The service providers <b>18</b><i>a</i>, <b>18</b><i>b</i>, <b>18</b><i>c </i>may thus drop ship the IP phone <b>12</b><i>a </i>at the user location, and the IP phone <b>12</b><i>a </i>is ready for use out of the box, as the IP phone <b>12</b><i>a </i>is auto-configured in the background and without user input.

p-0056In another exemplary embodiment, similar steps may be followed for automatically configuring different IP devices, such as an IP phone <b>12</b><i>a </i>from manufacturer A, an IP phone <b>12</b><i>b </i>from manufacturer B, an IP phone <b>12</b><i>a </i>from manufacturer C, and all to be provisioned by a single service provider <b>18</b><i>a</i>, wherein each phone <b>12</b><i>a</i>, <b>12</b><i>b</i>, or <b>12</b><i>c </i>includes require different configuration settings. As an example, all IP phones <b>12</b><i>a </i>from manufacturer A, e.g. Aastra Telecom, Canada, comprise the OUI 00-10-BC, and phone <b>12</b><i>b </i>from manufacturer C, e.g. MATRA, France comprise the OUI 08-00-71, and IP phones <b>12</b><i>c </i>from manufacturer C, e.g. DeTeWe-Deutsche Telephonwerke, Germany, comprise the OUI 00-30-42. The central server <b>14</b> thus includes a centralized repository having a master table associating all MAC address starting with 00-10-BC, 08-00-71 and 00-30-42, and/or including a range of remaining octets assigned by the manufacturer, to service provider <b>18</b><i>b</i>. Therefore, the service provider A includes a similar table (Table A) having a list of the resources for IP phones <b>12</b><i>a</i>, <b>12</b><i>b</i>, <b>12</b><i>c </i>OUIs starting with 00-10-BC, 08-00-71 and 00-30-42, as part of the configuration server <b>20</b><i>a </i>associated with service provider <b>18</b><i>a</i>. Therefore, a single set of resources or configuration settings may be applied to particular OUIs and/or a range of trailing octets, or for a range of MAC addresses, or for a certain class of devices <b>12</b><i>a</i>, <b>12</b><i>b</i>, and <b>12</b><i>c</i>. This arrangement thus allows for all IP phones <b>12</b><i>a </i>from manufacturer A with OUI 00-10-BC to receive the same configuration settings, while all IP phones <b>12</b><i>b </i>from manufacturer B with OUI 08-00-71 to receive the same configuration settings. Such an arrangement may be desirable to reduce the processing load on the central redirect server <b>14</b>, and may improve robustness and allows for considerable network scalability. Thus, when an end user powers on a phone <b>12</b><i>b </i>and connects it to the network <b>16</b>, the phone <b>12</b><i>b </i>immediately connects to the central server <b>14</b>, which captures the OUI part of the MAC address (08-00-71) and the trailing octets, and refers to the master table to determine whether the MAC address falls within the range of MAC addresses for any of the service providers <b>18</b><i>a</i>, <b>18</b><i>b</i>, or <b>18</b><i>c</i>. The request is subsequently forwarded to the appropriate service provider <b>18</b><i>b </i>with configuration server <b>20</b><i>b </i>which selects the appropriate configuration settings for the IP phone <b>12</b><i>b </i>using the second mapping table, and the configuration settings data is subsequently sent to the IP phone <b>12</b><i>b </i>via a suitable protocol. Mass deployment for a hosted environment may thus be substantially simplified, and service providers may offer enhanced centralized value added services.

p-0057In yet another exemplary embodiment, when booting, the IP phone <b>12</b><i>a </i>initiates the discovery process automatically to look for a configuration server <b>20</b><i>a </i><b>20</b><i>b </i>or <b>20</b><i>c </i>to retrieve its configuration data and/or its firmware. The boot process includes checking whether DHCP option <b>66</b> (bootp) is enabled to automatically push the TFTP server address to the IP phone <b>12</b><i>a</i>, and running an auto-discovery process using mDNS. If a local configuration server can not be located or does not include the settings for that particular IP phone <b>12</b><i>a</i>, then after a predefined period (on timeout), the IP phone <b>12</b><i>a </i>initiates a search for one or more public/enterprise servers on a WAN or the Internet. These public/enterprise servers may be maintained by individuals, or groups of individuals, corporations, network equipment providers, manufacturers, organisations, and include information related to configuration settings for a plurality of OUIs, MAC addresses, class identifiers, or other identifiers. For example, configuration settings for a plurality of OUIs, MAC addresses, class identifiers, or other identifiers may be uploaded to these public/enterprise servers, and updated periodically with configuration settings or pointers to the appropriate configuration servers, which may also be public or enterprise servers a WAN or the Internet. Typically, in a managed enterprise LAN, or SOHO network, environment with DHCP being enabled, the configuration settings are provided using Option <b>66</b>/Option <b>67</b>. In addition to its IP address, the DHCP server could provide the IP phone <b>12</b><i>a </i>with a DNS server, a default gateway. It can also be configured to provide the IP address of the central server <b>14</b>. If the URI of the central server <b>14</b> is specified, the IP phone <b>12</b><i>a </i>uses any suitable protocol to contact the central server <b>14</b> on the network <b>16</b>.

p-0058In yet another exemplary embodiment, the IP phone <b>12</b><i>a </i>can be automatically configured out of the box by connecting it to the network <b>16</b>, and allowing the user to select and/or set up services via an integrated selection mechanism. The end-user may choose a plan, value-added features or quality of service. For example, based on the identifier (MAC address) contained in the configuration request, the central server <b>14</b> directs the request to the appropriate service provider <b>18</b><i>a </i>with configuration server <b>20</b><i>a</i>. Having received the request from the central server <b>14</b>, the configuration server <b>20</b><i>a </i>may require authentication of the IP phone <b>12</b><i>a</i>, and thus sends an acknowledgment of receipt to the IP phone, along with a request for a Username and/or Password, or other credentials (as provided by the service provider <b>18</b><i>a</i>). After validation of the user credentials, the configuration settings data is then sent to the IP phone <b>12</b><i>a</i>. Alternatively, the process of authentication may be performed at the central server <b>14</b>, or in conjunction with the configuration server <b>20</b><i>a</i>, if so designed. The central server <b>14</b> can also serve as a portal to partner services.

p-0059In yet another exemplary embodiment, the IP phone <b>12</b><i>a </i>includes a default “home” location, similar to a home page for an Internet browser, as part of is factory-set default configuration settings. Thus, at boot-up the IP phone <b>12</b><i>a </i>automatically seeks this default page, or when it is in an environment that does not present the IP phone <b>12</b><i>a </i>with configuration or service options. The home page presents information such as links, portals, menus, or other network connections or information to the device <b>12</b><i>a</i>. Alternatively, if the IP phone <b>12</b><i>a </i>is coupled to the network <b>16</b> and the MAC address (or other identifier/address) is not recognized by the central server <b>14</b> as being associated with a service provider <b>18</b><i>a</i>, <b>18</b><i>b</i>, or <b>18</b><i>c</i>, a menu may be presented on the IP phone <b>12</b><i>a</i>, via at least one of the I/O devices, with a choice of suitable service providers <b>20</b><i>a</i>, <b>20</b><i>b</i>, or <b>20</b><i>c</i>. These options can be extended to include not only the service provider <b>20</b><i>a</i>, <b>20</b><i>b</i>, or <b>20</b><i>c</i>, but other options and configurations within each service provider <b>20</b><i>a</i>, <b>20</b><i>b</i>, or <b>20</b><i>c</i>, such as plan, value-added features or quality of service.

p-0060In yet another exemplary embodiment, the network entity <b>12</b><i>a </i>includes a class identifier, such that the service provider/VOIP provider dictates its service offering in terms of both quality of service and value-added features based on class identifier. Therefore, the central server <b>14</b><i>a </i>and/or configuration server <b>20</b><i>a</i>, <b>20</b><i>b</i>, <b>20</b><i>c</i>, provides configuration settings for that particular class of device <b>12</b><i>a</i>. For example, certain network entities <b>12</b><i>a</i>, <b>12</b><i>b </i>may be used only in enterprise environments, therefore the settings may include priority paths for voice over IP, such that the network connection is managed and optimized for voice traffic to allow for superior quality of service. Other features may include call transcription or enhanced privacy for voice traffic, such as Secure VoIP using suitable cryptographic schemes. Other network entities <b>12</b><i>c </i>may be classified as consumer devices, and may include default settings that allow call monitoring, linking to home alarm systems, compatibility with TiVo™ from TIVO, USA.

p-0061In yet another exemplary embodiment, an IP phone <b>12</b><i>a </i>is coupled to a network <b>16</b>, and at least central server <b>14</b><i>a </i>or configuration server <b>20</b><i>a</i>, <b>20</b><i>b </i>or <b>20</b><i>c </i>automatically detects that the IP device <b>12</b><i>a </i>is coupled to the network <b>16</b>, and provides the relevant configuration information related to automatically configuring the IP phone <b>12</b><i>a. </i>

p-0062In yet another exemplary embodiment, the IP endpoint <b>12</b><i>a </i>may be programmed (firmware and/or software program) to contact the redirect server <b>14</b>, or a plurality of redirect servers, each time it is powered on, rebooted or reset, or relocated within the same network or another network, in order receive settings data for auto-configuration, or firmware updates/downgrades.

p-0063In yet another exemplary embodiment, the redirect server <b>14</b> serves as a proxy or intermediary, by communicating with one of the configuration servers <b>20</b><i>a</i>, <b>20</b><i>b </i>or <b>20</b><i>c </i>to directly request and acquire the configuration settings data, and then forwarding the configuration setting data to the network entity <b>12</b><i>a</i>. Alternatively, the network entity <b>12</b><i>a </i>is programmed (firmware and/or software program) to contact the central server <b>14</b> to request configuration information, and the redirect server <b>14</b> responds to the network entity <b>12</b><i>a </i>with the URI to a suitable configuration server <b>20</b><i>a </i>that the network entity <b>12</b><i>a </i>should contact directly to request the configuration settings data. The configuration server <b>20</b><i>a </i>responds with the configuration information specific for that network entity <b>12</b><i>a</i>, based on the second mapping table.

p-0064In yet another exemplary embodiment, the computer-readable medium of the network entity <b>12</b><i>a </i>is included with a plurality of URIs to different redirect servers <b>14</b> and/or different configuration servers <b>20</b><i>a</i>, <b>20</b><i>b</i>, <b>20</b><i>c </i>associated with a plurality of service providers <b>18</b><i>a</i>, <b>18</b><i>b</i>, <b>18</b><i>c </i>or ITSPs, commercial voice over IP network providers, carriers, and so forth. For example, the network entity <b>12</b><i>a </i>includes URIs to all the configuration servers <b>20</b><i>a</i>, <b>20</b><i>b</i>, <b>20</b><i>c </i>associated with most of the major carriers or service providers, such as AT&amp;T CallVantage, Verizon, bellshare, BT Group, Vonage, Skype, Packet8, Time Warner, Qwest or Comcast. As such, the program code causes the network entity <b>12</b><i>a </i>to send, or broadcast, at least one request for information related to its configuration settings, and at least one of the service providers <b>18</b><i>a</i>, <b>18</b><i>b</i>, or <b>18</b><i>c</i>, ITSPs, commercial voice over IP network providers or carriers responds with the requisite configuration information.

p-0065Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments. However, the benefits, advantages, solutions to problems, and any element(s) that may cause any benefit, advantage, or solution to occur or become more pronounced are not to be construed as critical, required, or essential features or elements of any or all the claims. As used herein, the terms “comprises,” “comprising,” or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Further, no element described herein is required for the practice of the invention unless expressly described as “essential” or “critical.”

p-0066The preceding detailed description is presented for purposes of illustration only and not of limitation, and the scope of the invention is defined by the preceding description, and with respect to the attached claims.