WO2007086026A2 - Établissement automatique d'une connexion réseau pour une configuration automatisée d'un élément réseau - Google Patents

Établissement automatique d'une connexion réseau pour une configuration automatisée d'un élément réseau Download PDF

Info

Publication number
WO2007086026A2
WO2007086026A2 PCT/IB2007/050274 IB2007050274W WO2007086026A2 WO 2007086026 A2 WO2007086026 A2 WO 2007086026A2 IB 2007050274 W IB2007050274 W IB 2007050274W WO 2007086026 A2 WO2007086026 A2 WO 2007086026A2
Authority
WO
WIPO (PCT)
Prior art keywords
network element
connection
address
configuration
bts
Prior art date
Application number
PCT/IB2007/050274
Other languages
English (en)
Other versions
WO2007086026A3 (fr
Inventor
Markus Hauenstein
Andreas Wannenwetsch
Original Assignee
Nokia Siemens Networks Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US11/657,102 external-priority patent/US20070211649A1/en
Application filed by Nokia Siemens Networks Oy filed Critical Nokia Siemens Networks Oy
Publication of WO2007086026A2 publication Critical patent/WO2007086026A2/fr
Publication of WO2007086026A3 publication Critical patent/WO2007086026A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management

Definitions

  • the invention relates to a network element and a method for configuring the network element, and in particular to an automatic establishment of a network connection for automated commissioning and/or recovery of network elements.
  • BTS Base Transceiver Stations
  • a visit of e.g. a BTS site is usually required during network rollout after the BTS installation, in order to perform commissioning tasks.
  • site visits are sometimes necessary when the remote management connection has been lost for some reason, e.g. because of an unintended misconfiguration leading to the breakup of the DCN (data communication network used for remote management of the network elements) connection, or because of a software malfunction .
  • the commissioning of a new BTS must currently be done locally at the BTS site because the BTS has initially no DCN connectivity.
  • a network element which requires connectivity to another external network element, comprising configuration unit configured to automatically configure a connection by probing different connection settings.
  • the above object is solved by a method for configuring a network element, which requires connectivity to another external network element, comprising configuring a connection by automatically probing different connection settings.
  • connection setting may be carried out upon configuring the network element: selecting a connection setting, using the connection setting via an interface of the network element, and deciding, based on a failure/success indication of the interface, whether the connection setting is usable or not .
  • connection to be probed may be a connection on a physical layer. Then, in case the failure/success indication from the interface indicates a failure, it is decided that the connection setting is not usable. However, if the failure/success indication indicates success (this may be an indication that no longer failure messages are sent) , it is decided that the connection setting is usable.
  • connection to be probed may be a data link connection.
  • connection settings may comprise asynchronous transfer mode (ATM) and/or inverse multiplexing over ATM (IMA) .
  • ATM synchronous transfer mode
  • IMA inverse multiplexing over ATM
  • an address may be borrowed from a connected upstream network element in order to use it as the address of the network element to be configured.
  • a network element which requires connectivity to another external network element in order to receive certain configuration information, comprising a configuration unit which is configured to borrow an address from a connected upstream network element in order to use it as the address of the network element to be configured.
  • the invention also proposes a network element for configuring a network element connected downstream, which requires connectivity to another external network element in order to receive certain configuration information, comprising a configuration unit which is adapted to lend an address to the connected downstream network element.
  • the above object is solved by a method for configuring a network element, which requires connectivity to another external network element in order to receive certain configuration information, comprising the step of borrowing an address from a connected upstream network element in order to use it as the address of the network element to be configured.
  • a method for configuring a network element connected downstream comprises the step of lending an address to the connected downstream network element .
  • an address from the subnet of the upstream BTS is lent to the network element to be configured.
  • it can be avoided to update routing tables of intermediate routers in order to be aware of the new network element, which would be necessary in case only a new IP address would be assigned. If such a subnet address is lent, this is not needed, because all IP packets addressed to the new network element in the subnet are automatically routed to the upstream BTS "owning" the subnet.
  • the borrowing of the address may be performed by using a dynamic host configuration protocol
  • DHCP Dynamic Hosk Configuration Protocol
  • DHCP DHCP server functionality in the network element connected upstream.
  • the network element to be configured may be a base station in a cellular network, and also the network element connected upstream of the network element to be configured may be a base station or a radio network controller (RNC) in a cellular network.
  • RNC radio network controller
  • the procedure according to the present invention may be carried out in order to receive certain configuration information using the connectivity.
  • Such certain configuration information may comprise a configuration file, which can be downloaded by using the lending address described above.
  • the invention also proposes a network, and a program for carrying out the steps of the invention.
  • Fig. IA shows a basic flow chart of probing a layer-1 and/or layer-2 connection according to the an embodiment of the present invention
  • Fig. IB shows a basic flow chart of borrowing an IP address from an upstream BTS according to the embodiment
  • Fig. 2A and 2B show a hierarchical topology of a plurality of base stations including a base station to be commissioned in accordance with the embodiment.
  • the invention relates to a simplified way how to configure a new network element in a network, e.g. in a 3G radio access network.
  • a new installed network element e.g. in a 3G radio access network.
  • a BTS connects automatically to the network management system or a dedicated server in order to download its configuration from there.
  • a BTS is used as an example for a network element to be configured.
  • IP connectivity The prerequisite for automated BTS commissioning is IP connectivity.
  • layer- 1 physical layer
  • layer-2 IP data link layer
  • layer-3 IP layer
  • this can be accomplished.
  • the following processes are carried out: • Probing (i.e. trying out) of different layer-1 and layer-2 settings, and
  • Fig. IA the probing of different layer-1 or layer-2 connection is shown.
  • step Sl a connection setting is selected and actually used, i.e., tried or probed.
  • step S2 it is checked whether there are failure indications or not. If a failure indication is present (YES) , it is decided that the connection setting does not work and the process returns to step Sl in order to try another connection setting. In case no failure indication is present (NO in step S2), it is decided that the connection setting works, and this connection setting is set as the operational connection setting of the network element (e.g., BTS).
  • the network element e.g., BTS
  • step S4 an IP address from an upstream network element (e.g., BTS) is borrowed, and in step S5, a configuration file can be downloaded, since now the BTS to be configured has an IP address.
  • BTS upstream network element
  • step S5 a configuration file can be downloaded, since now the BTS to be configured has an IP address.
  • a hierarchical topology as depicted in Fig. 2A and 2B is assumed.
  • the base stations directly connected to the RNC will be configured first.
  • the base stations immediately connected to them will be configured next, and so on.
  • a BTS2 is to be configured, whereas BTSl is already configured.
  • the further shown BTS3 is also already configured.
  • BTSl is on top in the hierarchy of the BTS2 and BTS3 and is connected to the radio network controller (RNC) .
  • the RNC acts as IP router and is connected via an IP network with the OSS (operating support system) site as shown in Fig. 2A and 2B.
  • the OSS site contains a configuration server which the BTSs can contact to download their planned configuration.
  • each BTS in Fig. 2A and 2B comprises a management agent, which serves to carry out the configuration processes as described below, and is an example for a configuration means of a network element. Further details of Fig. 2A and 2B will be explained in the following.
  • cabling rules exist.
  • the first interface of a downstream BTS shall always be connected to the upstream BTS. Then there is always a network path towards RNC and further on towards the core network. It can be assumed that a configuration server is located in the core network. With this cabling rule, it can be ensured that a not-configured BTS will always try to communicate with an already configured BTS, and not with a BTS even deeper in the hierarchy.
  • the first problem to be solved is physical layer connectivity, i.e., to configure the layer-1 connection (physical layer connection) .
  • Solution The new base station probes different physical layer settings
  • step Sl and S2 of Fig. IA e.g. El or Tl, line codes, framing options
  • the correct set of physical layer settings is detected when physical layer alarms disappear (e.g. loss-of-signal, loss-of- frame, as examples for a failure indication) and the operational state of the physical interface is up (step S3 of Fig. IA) .
  • ATM cell transmission will start in order to configure the layer-2 connection (IP Data Link Layer connection) .
  • layer-2 connection IP Data Link Layer connection
  • these are only special ATM cells.
  • ICP IMA Control Protocol
  • Filler cells When no IMA group is configured, it will send idle cells.
  • OAM service for operating, managing and maintaining networks
  • the upstream BTS will also send OAM cells. Since IMA and OAM are not yet configured in the new BTS, the new BTS will initially always send only idle cells.
  • the loss-of-cell-delineation alarm (as an example for a failure indication) will disappear, and the interface specific transmission convergence sublayer will be operational on the physical interface.
  • the next problem for the new BTS is to find out whether IMA is configured or not. Monitoring the received ATM cells can theoretically do this. With IMA, the new BTS will receive ICP and Filler cells, without IMA not. Furthermore, when IMA is configured, all necessary information to set up a corresponding IMA group is already contained in the received ICP cells. In practical implementations, this information might however not be easily accessible, and it might not be possible to directly derive a working configuration from the received cells. As a solution to this problem, the probing approach can then again be applied to get IMA connectivity. This is explained in the next paragraph.
  • the sufficient-links parameter in the already configured upstream base station is always set to 1.
  • the upstream BTS can have an IMA group with several physical links, and the new downstream BTS with just one link, as it is assumed.
  • the downstream BTS only needs to try out trivial IMA groups of size 1, i.e. consisting of a single link.
  • the downstream BTS does not need to try out all of its interfaces but only the first one.
  • the BTS can thus probe different IMA settings as e.g. IMA version and IMA frame length.
  • IMA e.g. IMA version and IMA frame length.
  • the operational state of the IMA group will get up. Since the usage of IMA is however not mandatory, the new base station might not find a working IMA configuration when the upstream BTS does not use IMA.
  • the downstream BTS will assume an ATM configuration without IMA, and should nevertheless get connectivity via its first physical interface. After this phase, the downstream BTS has an operational ATM interface connecting it to the upstream BTS.
  • VCC virtual channel connection
  • VPI virtual path identifier
  • VCI virtual channel identifier
  • AAL5 ATM adaptation layer 5
  • LLC/SNAP logical link control/subnetwork access protocol
  • each BTS has its own IP subnet and not only a single IP address.
  • intermediate IP routers will have subnet routes instead of host specific routes and can route IP packets for all IP hosts in the subnet without requiring a routing table update .
  • BTSl has the IP Subnet 10.1.2.0/24, and the IP address 10.1.2.1.
  • a new downstream BTS (e.g., BTS 2 in Fig. 2A and 2B) borrows an IP address from the upstream BTS subnet and becomes temporarily a member of the subnet of the upstream BTS (steps S4 and S5 of Fig. IB) .
  • DHCP dynamic host configuration protocol
  • a base station must therefore implement both DHCP client (in case it acts as the new downstream BTS) and server (in case it acts as the already configured upstream BTS).
  • the upstream BTS e.g., BTSl in Fig. 2A and 2B
  • the new downstream BTS e.g., BTS2 in Fig. 2A and 2B
  • the new BTS sends then a DHCP request via the temporary DCN channel, requesting IP configuration parameters.
  • the DHCP server in the configured BTS receives this request.
  • IP address pool configured containing just one IP address (the "lending address") from the internal subnet of the upstream BTS.
  • this lending address of the IP address pool is 10.1.1.99.
  • This lending address is now granted (with a short lease time) to the new base station (if another new BTS appears, it will have to wait until the first one is commissioned and the IP address is released again) . Also, the new BTS will have the same subnet mask as the configured BTS, and it will use the configured BTS as its default router (these parameters are also transmitted via DHCP) . Effectively, the new BTS becomes thus a host in the configured base station's subnet.
  • Both base stations run also InATMARP (inverse ATM address resolution protocol) on the DCN channel (because of LLC/SNAP encapsulation, InATMARP and IP packets can be differentiated) , so their IP routing tables are automatically updated with host-specific direct routes to each other, in both cases pointing to the temporary DCN VCC.
  • InATMARP inverse ATM address resolution protocol
  • the new BTS has now full IP connectivity to the IP DCN. Configuration download can therefore start. If the process takes longer, the DHCP client will renew its lease of the lending address via the temporary DCN channel.
  • the upstream network element would be the RNC. As shown in Fig. 2A and 2B, also the RNC contains the DHCP server functionality described above.
  • the configuration file for the downstream BTS can be downloaded manually or automatically.
  • the scenarios for this are manifold, and some examples are described in the following.
  • the upstream BTS may notify the management system about the new downstream BTS.
  • This notification may contain:
  • Some identifier e.g. serial number
  • the downstream BTS has then passed this identifier to the upstream BTS before via some IP-based protocol.
  • Topology information i.e. the physical interface (s) of the upstream BTS at which the new downstream BTS appeared.
  • the management system can then select the correct configuration file for the new downstream BTS and download it remotely (no site visit required) .
  • the new downstream BTS will get the address of a configuration server from the upstream BTS (this may have been contained in the DHCP response) .
  • the downstream BTS will then contact this server and download its specific configuration file.
  • the specific configuration file may be identified based on an identifier of the new BTS.
  • the new BTS will apply this configuration. Depending on the implementation, this might include a restart or not.
  • the IMA group in the downstream BTS will contain the planned number of links.
  • the downstream BTS will use its own planned IP address, which is contained in the configuration file, and no longer the lending address from the upstream BTS subnet.
  • the upstream base station learns that the IP address on the other end has changed, and updates its routing table accordingly.
  • the downstream base station might start its routing protocol (e.g. OSPF or IS-IS) and distribute reachability information to the IP DCN. After a while, the reachability information has traversed the whole DCN, and full IP connectivity of the downstream BTS with the planned IP address is established.
  • OSPF OSPF
  • IS-IS IS-IS
  • the lease of the lending address will expire in the upstream BTS at some point in time, and can again be used by another new base station connected to different interfaces .
  • the new formerly not-configured BTS is now running with its planned configuration, and it can now become an upstream BTS for new downstream base stations, which are located one level deeper in the network hierarchy.
  • a BTS may get screwed up and loose its DCN connection.
  • the BTS may detect this.
  • the BTS may fall back into the not-commissioned state, and the whole process as described above may take place again.
  • a chain reaction should be avoided: Because of the misconfiguration of some upstream BTS, the connected downstream base stations may also loose their DCN connection. These downstream BTS should then not fall back into the not-commissioned state.
  • the BTS pings a server in the OSS, e.g. every minute. When this works, the BTS assumes that its DCN configuration is correct. When this does not work (after a number of retries), the BTS enters the recovery state.
  • the layer-l/layer-2 configuration before probing is tried out again, and if this works, this old configuration is used, otherwise the configuration found by probing is used. Thus, the configuration will not change, when a problem in the transmission network (e.g. a cable cut) leading to a temporary connection loss has been repaired.
  • the BTS attempts to ping the server again. If this works, the current BTS configuration is not changed. If this does not work, address borrowing from the upstream BTS is done to regain DCN connectivity.
  • the BTS can then ping the OSS server again, using the lending address. If this works now, the BTS can assume that its own IP configuration is corrupt. Using the lending address, the BTS can then send a notification to management requesting reconfiguration, or even download and apply the configuration file again.
  • the RNC should have the same functionality as a configured BTS, so that unconfigured base stations can also be directly connected to the RNC.
  • DHCP is especially tailored for broadcast networks as Ethernet and not for the point-to-point structure as found in the RAN. DHCP software must be adapted to this environment.
  • the invention is not limited to specific protocols described above.
  • the BTS described in the above embodiment is only an example for a network element to be configured.
  • any kind of network element which needs some kind of connectivity can be configured in the way as described above.
  • the BTS as an example for a network element probes the connection in order to receive certain configuration information such as a configuration file.
  • the network element may also be some kind of network element which only needs connectivity, so that no further configuration information is necessary.
  • such a network element may be some kind of simple network element only notifying alarms and/or sending reports and the like. Hence, it is only necessary for such a network element to send data and not to receive data. Therefore, it is not necessary to receive configuration files or the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention concerne une manière simplifiée utilisée pour configurer un nouvel élément réseau dans un réseau d'accès radio 3G. Selon l'invention, un élément réseau qui nécessite une connectivité à un autre élément réseau externe, effectue automatiquement l'exploration d'une connexion en vue d'établir une connexion pour un système de gestion de réseau ou autre.
PCT/IB2007/050274 2006-01-27 2007-01-26 Établissement automatique d'une connexion réseau pour une configuration automatisée d'un élément réseau WO2007086026A2 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
EP06001748 2006-01-27
EP06001748.0 2006-01-27
US11/657,102 US20070211649A1 (en) 2006-01-27 2007-01-24 Automatic establishment of a network connection for automated network element configuration
US11/657,102 2007-01-24

Publications (2)

Publication Number Publication Date
WO2007086026A2 true WO2007086026A2 (fr) 2007-08-02
WO2007086026A3 WO2007086026A3 (fr) 2008-11-06

Family

ID=38309590

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2007/050274 WO2007086026A2 (fr) 2006-01-27 2007-01-26 Établissement automatique d'une connexion réseau pour une configuration automatisée d'un élément réseau

Country Status (1)

Country Link
WO (1) WO2007086026A2 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101931970A (zh) * 2009-06-18 2010-12-29 中兴通讯股份有限公司 E1/t1接入方式下ip化基站收发信台开通方法及装置
EP2947907A4 (fr) * 2013-02-07 2016-02-24 Huawei Tech Co Ltd Procédé de configuration de démarrage dans une station de base, station de base et serveur

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010034759A1 (en) * 2000-03-17 2001-10-25 Chiles David Clyde Home-networking
WO2004014101A2 (fr) * 2002-08-05 2004-02-12 Roamware, Inc. Procede et systeme de reacheminement du trafic d'un reseau cellulaire
WO2004040881A1 (fr) * 2002-10-31 2004-05-13 Nokia Corporation Procede et systeme destines a lancer une amorce
EP1526682A2 (fr) * 2003-10-24 2005-04-27 Microsoft Corporation Choix de réseau et d'interface dans un dispositif de calcul

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20010034759A1 (en) * 2000-03-17 2001-10-25 Chiles David Clyde Home-networking
WO2004014101A2 (fr) * 2002-08-05 2004-02-12 Roamware, Inc. Procede et systeme de reacheminement du trafic d'un reseau cellulaire
WO2004040881A1 (fr) * 2002-10-31 2004-05-13 Nokia Corporation Procede et systeme destines a lancer une amorce
EP1526682A2 (fr) * 2003-10-24 2005-04-27 Microsoft Corporation Choix de réseau et d'interface dans un dispositif de calcul

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SAITO T ET AL: "HOME GATEWAY ARCHITECTURE AND ITS IMPLEMENTATION" IEEE TRANSACTIONS ON CONSUMER ELECTRONICS, IEEE SERVICE CENTER, NEW YORK, NY, US, vol. 46, no. 4, 1 November 2000 (2000-11-01), pages 1161-1166, XP001093610 ISSN: 0098-3063 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101931970A (zh) * 2009-06-18 2010-12-29 中兴通讯股份有限公司 E1/t1接入方式下ip化基站收发信台开通方法及装置
EP2947907A4 (fr) * 2013-02-07 2016-02-24 Huawei Tech Co Ltd Procédé de configuration de démarrage dans une station de base, station de base et serveur
US9838221B2 (en) 2013-02-07 2017-12-05 Huawei Technologies Co., Ltd. Base station deployment configuration method for base station, base station, and server

Also Published As

Publication number Publication date
WO2007086026A3 (fr) 2008-11-06

Similar Documents

Publication Publication Date Title
US7729284B2 (en) Discovery and configuration of devices across an Ethernet interface
US9344333B2 (en) Automating network build-out in self building networks
JP3850391B2 (ja) ＶＲＲＰ（ＶｉｒｔｕａｌＲｏｕｔｅｒＲｅｄｕｎｄａｎｃｙＰｒｏｔｏｃｏｌ）によるルータ・インターフェース・バックアップ実行方法
JP4620527B2 (ja) パケット通信装置
JP7292427B2 (ja) Ｔｓｎ内のコントローラ間の通信のための方法、装置、およびシステム
JP2006013827A (ja) パケット転送装置
US20100309812A1 (en) Method for logical deployment, undeployment and monitoring of a target ip network
CN108259215B (zh) 一种设备管理方法及装置
US20080225699A1 (en) Router and method of supporting nonstop packet forwarding on system redundant network
WO2009021981A2 (fr) Appareil d'intégration, réseau de communication et procédé permettant d'intégrer un noeud de réseau dans un réseau de communication
US20100271937A1 (en) Network-based dedicated backup service
JP2006135970A (ja) ＳｏｆｔＲｏｕｔｅｒ動的バインディング・プロトコル
CA2585683A1 (fr) Methode de configuration d'un reseau pour parc eolien
TW200907697A (en) System and method for providing multi-protocol access to remote computers
WO2009059505A1 (fr) Procédé et système d'initialisation à distance
US20120269092A1 (en) Auto-configuration of network devices
JP7119174B2 (ja) ネットワークトポロジディスカバリ方法、ネットワークトポロジディスカバリ装置及びネットワークトポロジディスカバリシステム
US20070211649A1 (en) Automatic establishment of a network connection for automated network element configuration
CN101404594B (zh) 热备份性能的测试方法与装置、通信设备
CN104125079A (zh) 一种确定双机热备份配置信息的方法及装置
JP4644221B2 (ja) ネットワークシステム
WO2007086026A2 (fr) Établissement automatique d'une connexion réseau pour une configuration automatisée d'un élément réseau
JP3692114B2 (ja) 監視制御ネットワークシステム
KR101625297B1 (ko) 언더레이 네트워크와 연동하여 오버레이 네트워크를 제공하는 방법 및 이를 수행하는 시스템
JP5304200B2 (ja) ネットワーク管理システム、ネットワーク管理方法、マネージャおよびエージェント

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07705714

Country of ref document: EP

Kind code of ref document: A2

122 Ep: pct application non-entry in european phase

Ref document number: 07705714

Country of ref document: EP

Kind code of ref document: A2