I 1111111111111111 11111 lllll 111111111111111 111111111111111 IIIIII IIII IIII IIII
`US008886772B2
`
`c12) United States Patent
`Visser et al.
`
`(IO) Patent No.:
`(45) Date of Patent:
`
`US 8,886, 772 B2
`Nov. 11, 2014
`
`(54) METHOD AND SYSTEM FOR REMOTE
`DEVICE MANAGEMENT
`
`(75)
`
`Inventors: Robert Visser, Amsterdam (NL); Harm
`Mulder, Katwijk (NL)
`
`2008/0133717 Al*
`2008/0215668 Al*
`2009/0150977 Al *
`2009/0219820 Al *
`2009/0292794 Al
`
`6/2008 Bouchat et al. ............... 709/220
`9/2008 Hu ................................ 709/202
`6/2009 Carley .............................. 726/3
`9/2009 Acke et al. .................... 370/241
`11/2009 Ding et al.
`
`(73) Assignee: Koninklijke KPN N.V., The Hague (NL)
`
`( *) Notice:
`
`Subject to any disclaimer, the term ofthis
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 932 days.
`
`EP
`EP
`EP
`
`FOREIGN PATENT DOCUMENTS
`
`1940077 Al
`2106079 Al
`2106079 Bl
`
`7/2008
`9/2009
`12/2012
`
`OTHER PUBLICATIONS
`
`(21) Appl. No.: 12/512,242
`
`(22) Filed:
`
`Jul. 30, 2009
`
`(65)
`
`Prior Publication Data
`
`US 2010/0030875 Al
`
`Feb. 4, 2010
`
`(30)
`
`Foreign Application Priority Data
`
`Jul. 31, 2008
`Aug. 5, 2008
`
`(EP) ..................................... 08013735
`(EP) ..................................... 08161850
`
`(51)
`
`(2006.01)
`(2006.01)
`(2006.01)
`
`Int. Cl.
`G06F 151177
`H04L 12/24
`H04L 29/12
`(52) U.S. Cl.
`CPC ......... H04L 4110856 (2013.01); H04L 41/0206
`(2013.01); H04L 4110806 (2013.01); H04L
`61/35 (2013.01); H04L 29/12783 (2013.01)
`USPC ........... 709/220; 709/202; 709/223; 370/241;
`370/254
`
`( 58) Field of Classification Search
`USPC . ... ... ... .. ... ... ... ... ... .. ... ... ... ... ... .. ... ... ... ... 709/220
`See application file for complete search history.
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`Valcourt, Scott A., "DSL-From A to V and Back Again (Invited
`Paper)", Access Networks & Workshops, 2007, Accessnets '07, Sec(cid:173)
`ond International Conference ON, IEEE, PI, Aug. 1, 2007, pp. 1-5.
`
`(Continued)
`
`Primary Examiner - Arvin Eskandamia
`(74) Attorney, Agent, or Firm - McDonnell Boehnen
`Hulbert & Berghoff LLP
`
`ABSTRACT
`(57)
`A system for remote device management includes in a net(cid:173)
`work an auto-configuration server managing device, at least
`one database, and a plurality of auto-configuration servers.
`The auto-configuration server managing device and the data(cid:173)
`base are coupled in a communicative connection. The data(cid:173)
`base holds information for identification of electronic
`devices. The auto-configuration server managing device is
`arranged for communication with a manageable electronic
`device over the network. The auto-configuration server man(cid:173)
`ager is further being arranged for:
`receiving a request from the manageable electronic device
`for configuration data,
`determining an identification of the manageable electronic
`device by comparing the request with the information
`for identification of electronic devices of the database,
`determining an identification of an auto-configuration
`server from the plurality of auto-configuration servers in
`accordance with the identification of the manageable
`electronic device.
`
`5,852,722 A * 12/1998 Hamilton ...................... 709/221
`2007/0011301 Al
`1/2007 Ong et al.
`
`16 Claims, 6 Drawing Sheets
`
`

`

`US 8,886,772 B2
`Page 2
`
`(56)
`
`References Cited
`
`OTHER PUBLICATIONS
`
`DSLhome-Technical Working Group, "Appendix C. Signed Vouch(cid:173)
`ers", CPE WAN Management Protocol, Internet Citation, [Online],
`XP002316355, Chapter 3.1, pp. 91-109.
`The DSL Home Technical Working Group in DSL Forum, TR-069
`Amendment 1, the CPE WAN Management Protocoal (Nov. 2006).
`Charles E. Perkins, "Mobile IP: Design Principles and Practices"
`(1998), Addison Wesley, Reading (MA), ISBN 0-201-63469-4.
`A.S. Tanenbaum, and D.J. Wetherall, "Computer Networks," 5th
`edition (2011), Pearson, Boston (MA), ISBN-13: 978-0-13-212695-
`3.
`ServerWatch Tutorial, "Back to Basics: The DHCP Relay Agent"
`(Feb. 29, 2008) at http://www.serverwatch.com/tutorials/article.php/
`2193031.
`Wimer, W., "Clarifications and extensions on the bootstrap protocol,"
`RFC 1542, Internet Engineering Task Force (IETF) Standard, Oct.
`1993, at http://www.ietf.org/rfc/rfc1542.txt.
`"Definition of: Proxy Server," PC Magazine Encyclopedia, at http://
`www.pcmag.com/encyclopedia/term/49892/proxy-server, as of Jul.
`29, 2014.
`
`"Relay Channel," Wikipedia webpage, http://en.wikipedia.org/wiki/
`Relay_channel, 2014.
`Thomas M. Cover and Abbas El Gama!, "Capacity theorems for the
`relay channel," IEEE Transactions on Information Theory ( 1979), pp.
`572-584.
`Kitamura, H., "A SOCKS-based IPv6/IPv4 Gateway Mechanism,"
`RFC 3089, Internet Engineering Task Force (IETF) Standard, Apr.
`2001, at http://www.ietf.org/rfc/rfc3089.txt.
`"Application layer gateways and protocol translation," IBM Knowl(cid:173)
`edge Center, at http://www 0 l.ibm.com/support/knowledgecenter/
`SSLTBW _2. l .0/com.ibm.zos.v2rl .hale00 l/ipv6d0021034306.htrn
`as of Jul. 29, 2014.
`"IP Details," Manual for Olicom Crossfire 8720 Fast Ethernet
`Switch
`(1999),
`at
`http://www.lard.net/olicom/CD_l.05/
`Help%20files/ipdetail.htrnl, as of Jul. 29, 2014.
`"SMTP Relay vs. forwarding," Oracle Community forum website
`Jan.
`14,
`2005,
`at
`http://www.lard.net/olicom/CD_l.05/
`Help%20files/ipdetail.htrnl.
`"CPE WAN Management Protocol," TR-069 amendment 4, Jul.
`2011,
`at
`http://www.lard.net/olicom/CD_l.05/Help%20files/
`ipdetail.htrnl.
`
`* cited by examiner
`
`

`

`U.S. Patent
`U.S. Patent
`
`Nov.11, 2014
`Nov. 11, 2014
`
`Sheet 1 of 6
`Sheet 1 of 6
`
`US 8,886,772 B2
`US 8,886,772 B2
`
`N
`
`N
`(f)
`
`~
`
`Figure1 PriorArt
`
`t::
`sr-
`~ <(
`::::s
`s...
`.Q> -~
`LL 0...
`
`(,0
`Cl..
`
`
`WAN
`
`...-
`Cl..
`
`N
`Cl..
`
`("')
`Cl..
`
`'q"
`Cl..
`
`Xiaomi Exhibit 1001, Page 3 of 14
`
`

`

`U.S. Patent
`
`Nov. 11, 2014
`
`Sheet 2 of 6
`
`US 8,886,772 B2
`
`Figure 2
`
`ISP
`
`SADM
`
`ACS1
`
`ACS2
`
`ACS3
`
`IP
`
`ISPID
`
`26a
`
`27a
`
`25
`
`ACSID
`
`28a
`
`DNS
`
`DSLAM, 15
`
`WAN
`
`CPE,1
`
`-
`
`-
`
`-
`
`-
`
`LAN
`
`2
`
`3
`
`4
`
`

`

`U.S. Patent
`
`Nov. 11, 2014
`
`Sheet 3 of 6
`
`US 8,886,772 B2
`
`Figure 3a
`
`Begin
`
`100
`
`Receive request
`
`101
`
`Compare IP
`address with IP
`database
`
`102
`
`103
`
`Find ISPID
`matching IP
`address
`
`Find ACSID
`based on at least
`one of ISPID and
`IP address
`
`Transmit ACSID
`to manageable
`electronic device
`(redirect)
`
`104
`
`105
`
`106
`
`End
`
`107
`
`Terminate
`actions
`
`108
`
`

`

`U.S. Patent
`
`Nov. 11, 2014
`
`Sheet 4 of 6
`
`US 8,886,772 B2
`
`Figure 3b
`
`Begin
`
`100
`
`Receive request 101
`
`Compare IP
`address with IP
`database
`
`102
`
`Find ISPID
`matching IP
`address
`
`104
`
`Find ACSID
`based on at least
`one of ISPID and 105
`IP address
`
`Relay request to
`ACSID and relay
`reply to
`manageable
`electronic device
`
`106a
`
`End
`
`107
`
`Terminate
`actions
`
`108
`
`

`

`U.S. Patent
`
`Nov. 11, 2014
`
`Sheet 5 of 6
`
`US 8,886,772 B2
`
`Figure 4
`
`25
`
`.,..i-,.._
`
`/C,..
`
`M1
`
`M2
`
`M3
`
`M4
`
`CPE, 1
`
`to
`
`time
`
`~
`
`~
`
`Figure 5
`
`CPE, 1
`
`25
`
`to
`
`Time
`
`M1
`
`M7
`
`M5
`
`M6
`
`ACS1
`
`;:.
`
`ACS1
`
`~
`
`

`

`U.S. Patent
`
`Nov. 11, 2014
`
`Sheet 6 of 6
`
`US 8,886,772 B2
`
`129
`
`132
`
`Processor
`
`Tape unit
`
`119
`
`130
`
`Hard disk
`
`118
`
`11@
`0
`
`120
`
`ROM
`
`124
`
`EEPROM
`
`123
`
`RAM
`
`122
`
`127
`
`.., ·126
`
`Figure 6
`
`

`

`US 8,886,772 B2
`
`1
`METHOD AND SYSTEM FOR REMOTE
`DEVICE MANAGEMENT
`
`CROSS REFERENCE TO RELATED
`APPLICATIONS
`
`The present application claims priority to European Patent
`Application EP 08013735.9, filed in the European Patent
`Office on Jul. 31, 2008, and to European Patent Application
`EP 08161850.6, filed in the European Patent Office onAug. 5,
`2008, the entire contents of both of which are incorporated
`herein by reference.
`
`FIELD OF THE INVENTION
`
`The present invention relates to a method for remote device
`management. Also, the present invention relates to a system
`for remote device management.
`
`BACKGROUND OF THE INVENTION
`
`Digital communication is well established by virtue of the
`Internet protocol (IP) that allows an electronic device to com(cid:173)
`municate to other electronic devices over a potentially world(cid:173)
`wide network.
`In such a network, the electronic device ( often referred to
`as Customer Premises equipment, CPE) is typically coupled
`to the wide area network (WAN) ( e.g., over digital subscriber
`line DSL), either directly or via a local area network (LAN).
`CPE may be any type of electronic device capable of digital
`communication. For example, it may be a personal computer,
`a gateway or router, an electronic appliance such as a set-top
`box, a television set, an IP based telephone, etc.
`Many CPE devices allow remote management over the
`wide area network, which relates to auto-configuration and
`dynamic service provisioning, software management, status
`and performance monitoring and diagnostics. The DSL
`Home-Technical Working Group describes in DSL Forum,
`TR-069 amendment l, the CPE WAN management protocol
`(November 2006), an end-to-end architecture for remote 40
`device management. (Recently, DSL-Foruni has been
`renamed to BroadBand-Forum). In this architecture, a CPE
`device in a local network connects to an auto-configuration
`server (ACS) that is capable of providing service level set(cid:173)
`tings for services available to the CPE.
`Typically, the ACS is dedicated either to a certain level of
`services (e.g. premium, best effort), a type of device (e.g.
`Home Gateway, Voice over IP telephone, Set TopBox) or a
`specific customer group ( e.g. business or residential). For that
`reason, it is adversely required that each CPE must be pre- 50
`configured before installation at the location of the customer
`to specifically address the proper ACS in dependence of the
`combination of options above available to the customer. To
`address the proper ACS, it will be required to pre-program the
`CPE with either a specific IP address or a specific URL 55
`(uniform resource locator) for the dedicated ACS. Alterna(cid:173)
`tively to pre-configuration of the CPE, configuration of the
`CPE may be done during installation either by service per(cid:173)
`sonnel or by the customer, but this may be time-consuming
`and/or may be sensitive to errors and mistakes.
`
`SUMMARY OF THE INVENTION
`
`It is an object of the present invention to provide a method
`that overcomes or reduces the problems of the prior art.
`According to an aspect of the invention, there is provided a
`system for remote device management comprising in a net-
`
`5
`
`15
`
`20
`
`2
`work an auto-configuration server managing device, at least
`one database, and a plurality of auto-configuration servers;
`the auto-configuration server managing device and the at least
`one database being coupled in a communicative connection;
`the at least one database being arranged for holding informa(cid:173)
`tion for identification of electronic devices; the auto-configu(cid:173)
`ration server managing device being arranged for communi(cid:173)
`cation with a manageable electronic device over the network,
`the manageable electronic device capable of sending a
`10 request for configuration data, the auto-configuration server
`manager further being arranged for:
`receiving the request from the manageable electronic
`device for configuration data,
`determining an identification of the manageable electronic
`device by comparing the request with the information
`for identification of electronic devices of the at least one
`database,
`determining an auto-configuration server from the plural(cid:173)
`ity of auto-configuration servers in accordance with the
`identification of the manageable electronic device.
`Advantageously, the method allows to configure any type
`of manageable electronic device at any given location and
`within any level of service or group specification without
`25 pre-configuring a dedicated address for configuration. The
`method will determine which specific auto-configuration
`server (ACS) is available for a given manageable electronic
`device, which allows to reduce the complexity of pre-instal(cid:173)
`lation and installation of devices. Also, the method allows a
`30 simpler manner to set up dedicated auto-configuration serv(cid:173)
`ers, since the addresses of the auto-configuration servers only
`need to be maintained in a central database.
`Also, the method allows a separation of access networks
`35 and the services provider via the possibility of rerouting as
`defined in the invention.
`According to an aspect of the invention, there is provided a
`method for remote device management of a manageable elec(cid:173)
`tronic device in a network, the network comprising an auto(cid:173)
`configuration server managing device, at least one database,
`and a plurality of auto-configuration servers; the auto-con(cid:173)
`figuration server managing device and the at least one data-
`base being coupled in a communicative connection; the at
`least one database being arranged for holding information for
`45 identification of electronic devices; the auto-configuration
`server managing device being arranged for communication
`with the manageable electronic device over the network, the
`manageable electronic device capable of sending a request for
`configuration data, wherein the method comprises:
`receiving the request;
`determining an identification of the manageable electronic
`device using a comparison of the request with the infor(cid:173)
`mation for identification of electronic devices of the at
`least one database,
`determining an identification of an auto-configuration
`server from the plurality of auto-configuration servers in
`accordance with the identification of the manageable
`electronic device.
`Furthermore, the present invention relates to a computer
`60 system for remote device management, the computer com(cid:173)
`prising a processing unit and memory, the memory being
`connected to the processing unit, the computer being
`arranged in a network, the network comprising at least one
`database, and a plurality of auto-configuration servers; the
`65 computer and the at least one database being coupled in a
`communicative connection; the at least one database being
`arranged for holding information for identification of elec-
`
`

`

`US 8,886,772 B2
`
`3
`tronic devices; wherein the computer is arranged for commu(cid:173)
`nication with a manageable electronic device over the net(cid:173)
`work and for
`receiving a request from the manageable electronic device
`for configuration data,
`determining an identification of the manageable electronic
`device by comparing the request with the information
`for identification of electronic devices of the at least one
`database,
`determining an identification of an auto-configuration 10
`server from the plurality of auto-configuration servers in
`accordance with the identification of the manageable
`electronic device.
`Additionally, the present invention relates to a computer
`program on a computer-readable medium to be loaded by a 15
`computer, the computer comprising a processing unit and
`memory, the processing unit being connected to the memory;
`the computer being arranged in a network, the network com(cid:173)
`prising at least one database, and a plurality of auto-configu(cid:173)
`ration servers; the computer and the at least one database 20
`being coupled in a communicative connection; the at least one
`database being arranged for holding information for identifi(cid:173)
`cation of electronic devices; wherein the computer is
`arranged for communication with a manageable electronic
`device over the network, the manageable electronic device 25
`capable of sending a request for configuration data, and
`wherein the computer program product after being loaded
`allows the processing unit to carry out:
`receiving the request from the manageable electronic
`device for configuration data,
`determining an identification of the manageable electronic
`device by comparing the request with the information
`for identification of electronic devices of the at least one
`database,
`determining an identification of an auto-configuration 35
`server from the plurality of auto-configuration servers in
`accordance with the identification of the manageable
`electronic device.
`
`30
`
`4
`more electronic devices 2, 3, 4 which are in a communicative
`connection with the interfacing device 1. One or more of the
`electronic devices 2, 3, 4 may also be a manageable electronic
`device.
`The local area network LAN may be a home network or an
`office network, i.e., a network located at a specific geographic
`location. Also, the local area network LAN may be a logical
`network which is distributed over a number of geographic
`locations.
`The wide area network WAN provides connectivity to a
`plurality of interfacing devices in a wide area. For example,
`the wide area network is the global network arrangement
`known as the Internet.
`In the local area network LAN and the wide area network
`WAN, electronic devices are arranged to have an address for
`identification on the respective network (i.e., communication
`is address based). A well known address scheme is the Inter(cid:173)
`net Protocol address system that provides a so-called IP
`address to each electronic device coupled to the network. The
`methods for an electronic device to obtain an IP address for
`identification are known in the art.
`Coupled to the wide area network are at least a first auto-
`configuration server ACSl, which comprises configuration
`data for a particular manageable electronic device, for
`example, the interfacing device 1 in the local area network
`LAN. A second auto-configuration server ACS2 is shown
`which comprises configuration data for another particular
`manageable electronic device, for example the manageable
`electronic device 2 in the local area network LAN.
`Configuration data for the auto-configuration server ACSl
`or ACS2 is delivered from some provisioning systems (Pl,
`P2, P3; P4, PS, P6), which may relate to equipment specific,
`service level specific and/or customer specific configuration
`data.
`Both the first and second auto-configuration serversACSl,
`ACS2 connect over the wide area network WAN to the local
`area network LAN (schematically shown by a respective
`dashed arrow-line) through the interfacing device 1, which
`may be a so-called router.
`In the method from the prior art, a manageable electronic
`device requires configuration data from a dedicated auto(cid:173)
`configuration server, for example, as an initialization of the
`level of service available to the manageable electronic device
`after installation or as an update during operation. In that
`45 event the manageable electronic device needs to request con(cid:173)
`figuration data from the specific auto-configuration server
`dedicated to the level of service or to the type of the manage(cid:173)
`able electronic device. As a consequence a specific (IP)
`address or URL must be 'known' to the manageable elec-
`50 tronic device before contacting the auto-configuration server.
`The request will be handled in a well-known manner. The
`manageable electronic device sends a request to the address
`of the auto-configuration server. The auto-configuration
`server sends a reply to the manageable electronic device, in
`55 which the reply contains the requested data. In this case, the
`specific address or URL must be pre-configured for the device
`before installation at the local area network, which may
`depend on one or more parameters chosen from at least the
`level of service; the type of the device; the type of access
`60 network and/or a costumer specific parameter. As a result,
`pre-configuration can be complex.
`FIG. 2 schematically shows an architecture for remote
`device management in accordance with an embodiment.
`In FIG. 2 entities with the same reference number as shown
`65 in the preceding figure refer to corresponding entities.
`Within the wide area network WAN, the architecture com(cid:173)
`prises a DSL access multiplexer (DSLAM), a domain name
`
`40
`
`BRIEF DESCRIPTION OF DRAWINGS
`
`Embodiments will now be described, by way of example
`only, with reference to the accompanying schematic drawings
`in which corresponding reference symbols indicate corre(cid:173)
`sponding parts, and in which:
`FIG. 1 schematically shows an end-to-end architecture for
`remote device management from the prior art;
`FIG. 2 schematically shows an architecture for remote
`device management in accordance with an embodiment;
`FIGS. 3a, 3b show a flow diagram in accordance with a
`respective embodiment of a method of the present invention;
`FIG. 4 schematically shows a signal flow in accordance
`with an embodiment;
`FIG. 5 shows a further signal flow in accordance with an
`embodiment, and
`FIG. 6 shows an auto-configuration server manager in an
`embodiment of the invention.
`
`DETAILED DESCRIPTION OF EMBODIMENTS
`
`FIG. 1 schematically shows an end-to-end architecture for
`remote device management from the prior art.
`The end-to-end architecture relates to a network arrange(cid:173)
`ment for remote device management. A local area network
`LAN is coupled to a wide area network WAN through an
`interfacing device 1 which is typically a manageable elec(cid:173)
`tronic device. The local network LAN may comprises one or
`
`

`

`US 8,886,772 B2
`
`5
`server DNS, an auto-configuration server manager 25, data(cid:173)
`bases 26, 27, 28, a plurality of auto-configuration servers
`ACSl, ACS2, ACS3.
`The DSL access multiplexer (DSLAM) is communica(cid:173)
`tively coupled to the domain name server DNS. The domain
`name server DNS is communicatively coupled to the auto(cid:173)
`configuration server manager 25.
`The auto-configuration server manager 25 is arranged for
`controlling access to the auto-configuration servers ACSl,
`ACS2, ACS3 as is indicated by the dotted lines. an embodi- 10
`ment of the auto-configuration server manager 25 is
`described below with reference to FIG. 6. The access control
`function ( of the auto-configuration server manager 25) will
`be described below in more detail.
`The auto-configuration server manager 25 is communica(cid:173)
`tively coupled to databases 26, 27, 28 for receiving informa(cid:173)
`tion signals 26A, 27 A, 28A. The databases may be located in
`one or more database servers, which may be located remotely
`from one another, as is known to persons skilled in the Art.
`The databases 26, 27, 28 and information signals 26A, 27A,
`28A will be described below in more detail.
`In an embodiment, the architecture further comprises a
`SADM (Service Activation Device Manager) which provides
`an interface to service providers such as ISP, CPE manufac(cid:173)
`turers for accessing the auto-configuration servers ACSl, 25
`ACS2, ACS3 in a uniform marmer.
`The interfacing device 1, such as a router, connects the
`local area network LAN to the wide area network WAN over
`a connection device 15. In many occasions, the connection
`will be implemented using digital subscriber line (DSL) tech(cid:173)
`nology, but in the present invention other alternative signal
`carriers capable of IP based communication such as optical
`fiber ( e.g., fiber to the home, fiber to the curb), cable TV
`network(s), powerline or radio loops (e.g. UMTS) are con(cid:173)
`sidered applicable. In case ofDSL technology, the interfacing 35
`device 1 is coupled to the DSL access multiplexer (DSLAM),
`which establishes a connection between the interfacing
`device 1 (and the local network LAN) and a WAN network
`switch (not shown).
`In the wide area network WAN the domain name server
`DNS is arranged for resolving domain name requests from
`the (manageable) electronic devices in the local network
`LAN ( or any electronic device in the wide area network).
`FIG. 3a shows a flow diagram 100 in accordance with an
`embodiment of a method of the present invention.
`A manageable electronic device in the local area network
`LAN requires configuration data from a dedicated auto-con(cid:173)
`figuration server, for example the interfacing device 1
`requires configuration data for auto-configuration server
`ACSl.
`In the present invention an (IP) address or URL is provided
`in a memory of the manageable electronic device 1 as default
`address for the auto-configuration server ACSl, which
`default (IP) address or URL actually points to the auto-con(cid:173)
`figuration server manager 25.
`The requesting manageable electronic device 1 sends its
`request to the wide area network WAN. In case the request
`comprises the IP address of the auto-configuration server
`manager, the DSLAM transmits the request to the network
`switch (not shown) that will relay the request to the auto(cid:173)
`configuration server manager (as known in the art). In the
`alternative case that the request comprises an URL, the
`DSLAM transmits the request to the domain name server
`DNS which resolves the address of the request into an IP
`address. Based on the IP address the request can be relayed by
`the network switch. Alternatively, the in IANA (Internet
`Assigned Numbers Authority) defined port for device man-
`
`6
`agement applications may be used to intercept the request
`independent of the IP address the request is issued on.
`In a first action 101, the auto-configuration server manager
`receives the request from the manageable electronic device 1.
`5 Typically, the request comprises the IP address of the man(cid:173)
`ageable electronic device 1 and information on the type or
`function of the manageable electronic device 1. Optionally,
`the request may comprise information on the manufacturer or
`supplier of the manageable electronic device.
`In a second action 102, the auto-configuration server man-
`ager 25 compares the received IP address of the manageable
`electronic device with a first database 26 ( or IP address data(cid:173)
`base) that comprises IP address information on IP addresses
`that are valid for allowing access to (the service of) the auto-
`15 configuration server manager 25. It can either do this directly
`or via a set of additional translations using the identification
`of the access line (or SIM card in case of wireless access), for
`linking a communication line to a customer.
`Next, in action 103, the auto-configuration server manager
`20 25 checks (indicated by information signal 26A) if the
`received IP address is a valid address in the first database 26.
`If the match is successful, the method continues in action 104,
`else the method continues in action 108, that terminates the
`method.
`In action 108, the auto-configuration server manager 25
`may optionally transmit a message to the requesting manage(cid:173)
`able electronic device that no server is available. After action
`108, the method ends in action 107.
`In action 104, the auto-configuration server manager 25
`30 resolves (by information signal 27 A) an identity of the service
`provider ISPID from the IP address by means of a second
`database 27 which comprises information that associates the
`identity of the service provider ISPID with the IP address of
`the manageable electronic device.
`In a next action 105, the auto-configuration server manager
`25 resolves (by information signal 28A) an IP address ACS ID
`of the dedicated auto-configuration server from at least one of
`the identity of the service provider ISPID and the received IP
`address of the manageable electronic device 1 by means of a
`40 third database 28 which comprises information that associ(cid:173)
`ates the IP address of the dedicated auto-configuration server
`with at least one of the identity of the service provider ISPID
`and the IP address of the manageable electronic device.
`Advantageously, as a function of at least one of the identity of
`45 the service provider ISPID and the IP address of the manage(cid:173)
`able electronic device the auto-configuration server manager
`25 is capable of selecting an identity ACS ID for the dedicated
`auto-configuration server in relation to a pre-determined level
`of service. Typically, the identity ACSID comprises an IP
`50 address or an URL for the respective auto-configuration
`server ACSl; ACS2; ACS3.
`Then in a further action 106, the auto-configuration server
`manager 25 transmits the identity ACSID of the dedicated
`auto-configuration server to the manageable electronic
`55 device 1 that made the request. For example, the transmission
`may use a redirection mechanism which comprises instruc(cid:173)
`tions for the manageable electronic device 1 to re-transmit the
`request to the dedicated auto-configuration server identified
`by ACSID. In an embodiment, the redirection mechanism is
`60 based on the HyperText Transfer Protocol (HTTP) redirect
`function.
`In action 107, the method ends.
`In an alternative embodiment, shown in FIG. 3b, an alter(cid:173)
`native action 106a ( as alternative to action 106) provides that
`65 the auto-configuration server manager 25 functions as an
`intermediate and relays the request from the requesting man(cid:173)
`ageable electronic device 1 to the dedicated auto-configura-
`
`

`

`US 8,886,772 B2
`
`7
`tion server as identified by ACS ID, receives the reply from the
`dedicated auto-configuration server and transmits that reply
`to the manageable electronic device 1.
`The information of the first, second and third databases 26,
`27, 28 may be provided by a service provider of the DSL
`network and/or DSLAM.
`FIG. 4 schematically shows a signal flow in accordance
`with an embodiment.
`In FIG. 4 the manageable electronic device is represented
`by a line CPE, the auto-configuration server manager 25 by a
`second line AM and the dedicated auto-configuration server
`by a third line ACSl. Time t is represented in the downward
`direction.
`At a time t0, the manageable electronic device CPE; 1
`sends a first message Ml to the default IP address or URL 15
`provided in the memory of the manageable electronic device
`1 as address for a dedicated auto-configuration server, which
`default (IP) address or URL points to the auto-configuration
`server manager 25. The first message comprises the request
`for configuration data from the dedicated auto-configuration 20
`server. Further the first message Ml comprises at least the IP
`address (or URL) of the manageable electronic device as
`identification on the wide area network WAN, an identifica(cid:173)
`tion of the type or function of the manageable electronic
`device and optionally additional identification, for example 25
`the identity of the supplier/manufacturer of the device.
`The first message Ml is received by the auto-configuration
`server manager 25. The auto-configuration server manager 25
`carries out the actions 101-107 of the method as described
`above with reference to FIG. 3, and sends a second message
`M2 to the manageable electronic device CPE; 1.
`The second message M2 comprises the reply which may be
`negative (after action 108) or confirmative (after action 106).
`In case the second message M2 is confirmative, the second
`message M2 comprises an IP address or URL for the dedi(cid:173)
`cated auto-configuration server identified by ACSID.
`Next, the manageable electronic device CPE; 1 re-trans(cid:173)
`mits a third message M3 to the IP address or URL associated
`with the dedicated auto-configuration server ACSl identified
`by ACSID. The third message M3 comprises at least the 40
`request for configuration data from the dedicated auto-con(cid:173)
`figuration server identified by ACSID.
`The dedicated auto-configuration server ACSl receives the
`third message M3 and transmits in response a fourth message
`M4 to the manageable electronic device CPE; 1. The fourth 45
`message M4 comprises the configuration data requested by
`the manageable electronic device. The manageable electronic
`device receives the fourth message and uses the configuration
`data within the fourth message for any configuration purposes
`as described above.
`FIG. 5 shows a further signal flow in accordance with an
`alternative embodiment.
`In FIG. 5 the manageable electronic device is represented
`by a line CPE, the auto-configuration server manager 25 by a
`second line AM and the dedicated auto-configuration server
`by a third line ACSl. Time t is represented in the downward
`direction.
`At a time t0, the manageable electronic device CPE; 1
`sends a first message Ml to the default IP address or URL
`provided in the memory of the manageable electronic device
`1 as address for a dedicated auto-configuration server, which
`(IP) address or URL points to the auto-configuration server
`manager 25. The first message comprises a request for con(cid:173)
`figuration data from the dedicated auto-configuration server.
`Further the first message Ml comprises at least the IP address
`(or URL) of the manag