EP2098014A2 - Procédé et dispositif d'échange de données - Google Patents

Procédé et dispositif d'échange de données

Info

Publication number
EP2098014A2
EP2098014A2 EP07846677A EP07846677A EP2098014A2 EP 2098014 A2 EP2098014 A2 EP 2098014A2 EP 07846677 A EP07846677 A EP 07846677A EP 07846677 A EP07846677 A EP 07846677A EP 2098014 A2 EP2098014 A2 EP 2098014A2
Authority
EP
European Patent Office
Prior art keywords
access system
network access
customer
network
ethernet
Prior art date
Legal status (The legal status 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 status listed.)
Withdrawn
Application number
EP07846677A
Other languages
German (de)
English (en)
Inventor
Jürgen HEILES
Matthias Schnitter
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Solutions and Networks GmbH and Co KG
Original Assignee
Nokia Siemens Networks GmbH and Co KG
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
Application filed by Nokia Siemens Networks GmbH and Co KG filed Critical Nokia Siemens Networks GmbH and Co KG
Publication of EP2098014A2 publication Critical patent/EP2098014A2/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access
    • H04L12/2869—Operational details of access network equipments
    • H04L12/2878—Access multiplexer, e.g. DSLAM
    • H04L12/2879—Access multiplexer, e.g. DSLAM characterised by the network type on the uplink side, i.e. towards the service provider network
    • H04L12/2881—IP/Ethernet DSLAM
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2854—Wide area networks, e.g. public data networks
    • H04L12/2856—Access arrangements, e.g. Internet access
    • H04L12/2869—Operational details of access network equipments
    • H04L12/2898—Subscriber equipments
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0876—Network utilisation, e.g. volume of load or congestion level
    • H04L43/0888—Throughput

Definitions

  • the present invention relates to methods and apparatus for exchanging data between a customer network access system and a provider network access system.
  • a broadband access network such as digital subscriber line (DSL) or passive optical network (PON) subscriber access technologies
  • DSL digital subscriber line
  • PON passive optical network
  • a provider-side network access system has as its primary task to enable a connection to a customer network access system.
  • the provider-side network access system is a device that can be connected directly to the customer network access system via layer 2 of the OSI model.
  • the provider-side network access system can be, for example, a network node
  • the provider-side network access system is normally located in the premises of a network operator.
  • the customer network access system has as a primary task to enable a connection to a provider-side network access system. It is usually housed and usually owned by a customer. It primarily serves to connect electronic devices or electronic components of the customer to the access network of the provider.
  • the term "customer network access system” therefore includes in particular the terms “network work termination device, modem, switch, bridge and router.
  • Tasks to be solved by the monitoring of the provider are, for example, the determination of whether the connection is working and to identify or exclude certain cases of error in the case of customer complaints, or to act preventively.
  • ATM Asynchronous Transfer Mode
  • ATM supports appropriate operation, administration and maintenance (OAM) functions that allow end-to-end connection monitoring.
  • OAM functions for ATM are disclosed, for example, in the ITU-T Standard 1.610.
  • ATM is used as Layer 2 protocol, where Ethernet can then be transmitted over ATM.
  • Ethernet frames are segmented at the transmitter, packaged and transmitted in ATM cells and unpacked at the receiver from the ATM cells and reassembled into Ethernet frames.
  • ATM is increasingly being replaced by Ethernet, or new Ethernet-based ones are being introduced
  • Ethernet is then transmitted directly over layer 1.
  • DSL physical layer
  • Ethernet is used on layer 2, an end-to-end monitoring of the connection should still be possible.
  • OAM functions for Ethernet (Ethernet OAM) have already been defined, for example in the ITU-T standard Y.1731 and the IEEE Draft Standard 802. These allow end-to-end monitoring on the Ethernet MAC Layer (Layer 2).
  • Ethernet OAM OAM functions for Ethernet
  • Layer 2 In order to use standardized Ethernet OAM functions, however, their implementation in the customer-side network access system and in the provider-side network access system is necessary.
  • the customer's network access system is normally owned by the customer and thus can not be readily exchanged and / or configured for Ethernet OAM. For this reason, there is a need to adapt the interface of a provider network access system to which a customer network access system is connected to the configuration of the customer network access system. For this, the provider-side network access system must have knowledge of any support for Ethernet OAM by the customer's network access system.
  • the provider network access system would receive misleading information and draw a wrong conclusion. Furthermore, it is possible that the special layer 2 connection to be monitored with Ethernet OAM is faulty. Then the ETH-LBM and / or the ETH-LBR frame may not be transmitted over the connection. Although the customer network access system may support Ethernet OAM, the provider-side network access system incorrectly assumes that it does not support it.
  • the present invention has for its object to exchange data between a customer network access system and a provider network access system.
  • a message is sent from the provider network access system to the customer network access system.
  • the message uses a multicast address in its destination MAC address field, which is not forwarded by the customer's network access system. By this is meant that a frame sent to this address will not be forwarded by the customer's network access system.
  • the customer network access system sends a response relating to an Ethernet OAM function. In a preferred embodiment, it can be determined in this way whether the Ethernet OAM function is supported by the customer network access system.
  • the provider-side network access system Message from the provider-side network access system does not go beyond the customer's network access system into the network the customer can be forwarded. This ensures that devices in the customer's network, which are behind the customer's network access system, can not answer the message with a response to the provider network access system and so the provider-side network access system can not draw a false conclusion regarding the customer network access system.
  • the solution can be used with Ethernet OAM implementations according to ITU-T standard Y.1731 as well as according to IEEE Draft Standard 802. lays. Also, it is not necessary that the provider side
  • Network access system before sending the message knows the MAC address of the customer network access system, because the message does not use a unicast MAC address, but a multicast MAC address. Furthermore, the
  • MAC addresses that are not forwarded by the customer network access system are, for example, slow-protocol multicast addresses (Annex 43B from IEEE Standard 802.3-2005) or group MAC addresses (Table 7.10 and Chapter 7.12.6 from IEEE Standard 802.1D -2004).
  • a slow protocol For a slow protocol, a maximum of 10 frames per second are normally sent. However, several slow protocols can run in parallel, then the rate of frames per unit time is greater. In addition, frames of a slow protocol are untagged, i. the frames do not run in a VLAN.
  • a slow protocol in the Length / Type field of the Ethernet frame uses the value (Ethertype) "88-09". This value tells the receiver that the frame belongs to a slow protocol.
  • the information contained in the response indicates whether an Ethernet OAM Function supported by the customer network access system or not. If, for example, the customer-side network access system is newly connected to an interface of the provider-side network access system, then in this way the provider-side network access system is informed that the Ethernet OAM function is supported. As a result, the provider-side network access system can configure the interface for the Ethernet OAM function.
  • the response can be transmitted directly to the provider-side network access system.
  • the answer may also use a multicast address in its destination MAC address field which is not forwarded by the provider-side network access system.
  • the response includes information about multiple Ethernet OAM functions supported by the customer's network access system. In a particularly preferred embodiment, the response includes information about all Ethernet OAM functions supported by the customer's network access system.
  • each partial response may contain a value of "true” or "false", the value indicating whether a particular Ethernet OAM function is supported by the customer network access system.
  • Ethernet OAM functions include the loopback protocol, the link trace protocol and the continuity check protocol defined in ITU-T Y.1731 and IEEE 802. lag.
  • Other examples defined in ITU-T Y.1731 include the Ethernet Alarm Indication Signal Protocol, the Ethernet Remote Defect Indication Protocol, the Ethernet Locked Signal Protocol, the Ethernet Test Signal Protocol, and the Ethernet Automatic Protection Switching Protocol, the Ethernet Maintenance Communication Channel Protocol, the Ethernet Experimental OAM Protocol, the Ethernet Vendor Specific OAM Protocol, the Frame Loss Measurement Protocol, the Frame Delay Measurement Protocol, and the Throughput Measurement Protocol.
  • a provider-side network access system which comprises means which are adapted for carrying out a method according to the invention.
  • the invention will be explained in more detail with reference to the drawing, for example. Showing:
  • FIG. 1 shows a network, which comprises a provider-side network access system and a customer-side network access system, in an embodiment of the invention
  • FIG. 2 shows a network in a further embodiment
  • FIG. 3 shows a network in a further embodiment
  • FIG. 4 shows a network in a further embodiment
  • FIG. 5 shows a network in a further embodiment.
  • FIG. 1 shows a network N, which comprises a provider-side network access system PN and a customer-side network access system KN.
  • the customer network access system KN includes a customer-side logic KL and a customer-side interface KS.
  • the customer logic KL has an Ethernet OAM function ETH OAM.
  • the provider-side network access system PN includes a provider-side logic PL and a provider-side interface PS.
  • a message M is sent from the provider-side network access system PN to the customer-side network access system KN.
  • the message M uses in a destination MAC address field a multicast address MD, which is not forwarded by the customer network access system KN.
  • the customer network access system KN On the basis of the message M, the customer network access system KN generates a response A which includes information about the customer network access system KN and sends it to the provider network access system PN.
  • the message M in a source MAC address field MS preferably uses the MAC address of the provider network access system which is used by the customer network access system in the destination MAC address field AD of the response A.
  • the source MAC address field AS of the response preferably comprises the MAC address of the customer network access system KN.
  • the response A includes the information that the customer network access system has implemented the Ethernet OAM function. This information is particularly useful if the customer network access system has been connected to the provider network access system PN immediately before the message is sent, because this can inform the provider network access system PN that it is the provider side interface PS to which the customer network access system KN has been connected for which Ethernet OAM function is to be configured.
  • the message M comprises a write command and at least one value for a parameter, which is set in the customer network access system KN.
  • the answer A in this case contains a confirmation that the parameter has been set.
  • the written parameters can also be supplied with the answer A.
  • the message M comprises a read command.
  • FIG. 2 shows an embodiment of a network N, which comprises a customer network KNW and a provider network PNW.
  • the provider network PNW comprises a Broadband Network Gateway BNG and an Access Node AN, which may be implemented, for example, as a DSL Access Multiplexer (DSLAM).
  • DSL Access Multiplexer DSL Access Multiplexer
  • the access node AN assumes the function of the provider-side network access system PN.
  • the Broadband Network Gateway BNG and the Access Node AN are interconnected via an Ethernet aggregation network EAN.
  • the provider network PNW may contain further network nodes, which are included for example by the Ethernet aggregation network EAN.
  • the customer network KNW comprises a customer-side network access system, which is designed as a network termination device NT.
  • the customer network KNW may contain other devices that are connected to the network termination device NT and here by a terminal, such as a personal computer PC, symbolized.
  • the provider network PNW uses Ethernet as layer 2 technology. It can therefore be monitored by means of Ethernet OAM functions. This monitoring is indicated in FIG. 2 as monitoring of the provider network UPN. This means that, for example, the BNG in regular
  • Intervals sends monitoring messages to the access node AN. From the arrival of a monitoring message, the access node AN can conclude that the data transmission from the broadband network gateway BNG to the access node AN works.
  • the monitoring messages are advantageously transmitted within the same logical Ethernet channels in which other data are transmitted. This ensures that the monitoring messages are subject to the same possible error conditions as the other data. For example, if a data transfer by an error is interrupted, so the transmission of the monitoring messages is interrupted.
  • the monitoring messages can also be transmitted in the opposite direction, from the access node AN to the broadband network gateway BNG. This checks, for example, the function of the data transmission from the AN to the BNG. It is also possible to monitor only individual sections in this way, for example the route from the Broadband Network Gateway BNG to a network node located in the Ethernet aggregation network EAN.
  • the network section from the access node AN to the network termination device NT is referred to below as the subscriber interface TS.
  • Subscriber interface TS can only be checked with Ethernet OAM functions if the
  • Network termination device NT Ethernet OAM supported. However, since this may not be known to the operator, either a recognition of the Ethernet OAM functionality must be performed in the network termination device NT or omit Ethernet OAM and this route be monitored by other methods. Common methods for monitoring the subscriber interface TS are, for example, monitoring by means of "Ethernet in the First MiIe" EFM OAM in accordance with IEEE Standard 802.3-2005 and the monitoring of layer 1 without monitoring the layer 2. When monitoring the subscriber interface TS by means of EFM OAM Although it is possible to check whether Ethernet frames can ever be transmitted between the access node AN and the network termination device NT, there is no possibility of individually checking the logical channels within the layer 2.
  • the access node AN has a means for sending a message via the subscriber interface to the network termination device NT.
  • the message uses in its destination MAC address field a special multicast address, due to which the immediately next layer 2 device receives the message but does not forward it.
  • An example of such a special multicast address is, for example, a slow protocol multicast address.
  • the message also includes the request to return an answer, which indicates whether the network termination device has implemented NT Ethernet OAM, to the access node AN.
  • the message can be from the
  • Access Node be triggered autonomously or on command of a network management system MGMT. If the network termination device has implemented NT Ethernet OAM, it will understand the request and send an affirmative answer. If it has not implemented the Ethernet OAM function, it will either understand the request and send a negative reply or it will not understand the request and will not send a response.
  • the use of the special multicast address prevents devices located in the customer network behind the network termination device NT from sending an incorrect response to the access node AN. As a result, the access node AN can reliably judge whether it can monitor the monitoring link UTS up to the network termination device NT by means of Ethernet OAM. Such automatic detection is particularly useful when the network termination device NT is newly connected to the access node AN. For this purpose, it can be provided that the access node AN repeatedly sends the message to the specific multicast address at predefined time intervals.
  • FIG. 3 shows a further embodiment, which is based on the embodiment of FIG. 2 described above.
  • the network termination device NT supports the Ethernet OAM function.
  • the network termination device NT will therefore return to the access node AN the answer that Ethernet OAM is supported.
  • the subscriber interface TS can be monitored by means of Ethernet OAM.
  • all partial routes between the network termination device NT and the broadband network gateway BNG would then be monitored: between the network termination device NT and the access node AN on the one hand and between the access node AN and the broadband network gateway BNG on the other hand.
  • an error could still occur within the access node AN, which would not be detected because one monitoring link would already be over, but the next would not have started.
  • Node through to the BNG be sent back. This is possible, for example, by the network termination device NT writing its own MAC address in the source MAC address field. This is forwarded to the Broadband Network Gateway BNG together with the information that the network termination device NT has implemented the Ethernet OAM function. Conversely, the broadband network gateway BNG can subsequently transmit its own MAC address with a message addressed to the network termination device NT.
  • monitoring messages between the network termination device NT and the Broadband Network Gateway BNG can be sent specifically, so that the entire route from BNG to NT can be monitored by means of Ethernet OAM functions.
  • This monitoring is indicated by an Ethernet loopback message frame ETH-LBM, which is sent from the BNG to the NT and the one with a Ethernet loopback reply frame ETH-LBR is answered by the NT to the BNG.
  • the monitoring therefore represents an end-to-end monitoring ETE.
  • FIG. 4 shows a further embodiment, which is based on the embodiment of FIG. 2 described above.
  • the network termination device NT is designed to use technology on the subscriber interface ATM as layer 2. This means that no Ethernet frames are packed in the ATM cells, but the user data are packed directly into ATM cells. Since the network termination device supports NT ATM, it is expected to support ATM OAM functions, but not Ethernet OAM functions. The network termination device NT will therefore not send a response to the access node which contains the
  • the network termination device will return an error message to the access node, which it uses as an indication that the network termination device NT does not support Ethernet OAM functionality. It should also be mentioned that the access node AN can already determine when connecting the NT device to the subscriber line and during the subsequent startup of the layer 1 technology that the network termination device supports ATM. It can be concluded that the network termination device NT also supports ATM OAM and therefore the subscriber interface can be monitored by means of ATM OAM functions.
  • Ethernet the provider network can be monitored using Ethernet OAM functions. End-to-end monitoring is limited because the messages used by Ethernet OAM to monitor the provider network are on-premises
  • Ethernet loopback message frame ETH-LBM which the BNG sends to the AN
  • ETH-LBM is converted in the AN into one or more ATM loopback message cells ATM-LBM and sent to the NT.
  • the NT responds to the incoming ATM loopback cell with another ATM loopback reply cell, ATM-LBR, which sends it back to the access node AN.
  • ATM-LBR another ATM loopback reply cell
  • the access node AN Upon receipt of the ATM loopback reply cell ATM-LBR, the access node AN generates an Ethernet loopback reply frame ETH-LBR, which it sends back to the BNG. It can be concluded from the received ETH-LBR framework that the data transmission from the BNG to the NT and from the NT to the BNG works.
  • FIG. 5 shows a further embodiment, which is based on the embodiment of FIG. 2 described above.
  • the network termination device NT is designed to use technology as Layer 2 technology on the subscriber interface TS Ethernet.
  • the Ethernet frames are transmitted directly through the layer 1 technology, ie they are not previously packaged in ATM cells.
  • the NT network termination device does not support Ethernet OAM functions.
  • the network termination device NT uses Ethernet as layer 2 technology but does not support Ethernet OAM functions, monitoring of the subscriber interface TS by means of Ethernet OAM functions is not possible.
  • the network termination device NT notifies this to the access node AN in the response. However, for example, it remains possible to dispense with monitoring of the layer 2 and to monitor only the layer 1.
  • the monitoring of the network N then runs, for example, such that the BNG sends an Ethernet loopback message frame ETH-LBM to the access node AN, the access node AN then checks the layer 1 on the subscriber interface, for example by changing its status Ll queries for layer 1 and the access node AN returns an Ethernet loopback reply frame ETH-LBR to the BNG in case the layer 1 test has returned a positive result. in the In the event of a negative test result, the Access Node AN does not send an ETH-LBR frame to the BNG.
  • FIG. 2 also shows a network management system MGMT of the provider network PNW.
  • the network operator can do that
  • Control provider network PNW with the network management system MGMT. It can, for example, make or read out settings on the network elements in the provider network, for example on the access node AN or the broadband network gateway BNG, via the network management system MGMT.
  • the network management system MGMT sends a request to the access node AN, a message containing a write or
  • Read command involves sending to the network termination device NT.
  • the request contains, for example, the information as to whether the message should contain a write command or a read command.
  • the request additionally includes, for example
  • the request contains additional information about one or more parameters to be read.
  • the information contained in the response of the network termination device NT for example the read values of the parameter (s) in the case of a read command, for example a confirmation in the case of a write command, is sent from the access node AN to the network management system MGMT.
  • the present invention is independent of which layer 1 technology is used.
  • an access network for example, DSL (Digital Subscriber)
  • DSL Digital Subscriber
  • PNW provider network PNW provider-side network access system

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)

Abstract

L'invention concerne un procédé et des dispositifs pour l'échange de données entre un système d'accès au réseau côté client (KN, NT) et un système d'accès au réseau côté fournisseur (PN, AN). Un message (M) est envoyé du système d'accès au réseau côté fournisseur (PN, AN) au système d'accès au réseau côté client (KN, NT). Ce message déclenche une réponse (A) qui contient une information (I) sur le système d'accès au réseau côté client (KN, NT) et qui est envoyée du système d'accès au réseau côté client (KN, NT) au système d'accès au réseau côté fournisseur (PN, AN). Le message (M) utilise dans un champ d'adresse MAC de destination (MD) une adresse de multidiffusion caractérisée en ce que les messages qui lui sont adressés ne sont pas retransmis par le système d'accès au réseau côté client (KN, NT) et l'information (I) concerne une fonction OAM Ethernet (ETH OAM). Si, par exemple, le message est une demande pour savoir si la fonction OAM Ethernet est prise en charge par le système d'accès au réseau côté client (KN, NT), le système d'accès au réseau côté fournisseur (PN, AN) peut ainsi être automatiquement adapté à la configuration du système d'accès au réseau côté client (KN, NT).
EP07846677A 2006-11-24 2007-11-20 Procédé et dispositif d'échange de données Withdrawn EP2098014A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102006055959A DE102006055959B3 (de) 2006-11-24 2006-11-24 Verfahren und Vorrichtung zum Austausch von Daten
PCT/EP2007/010006 WO2008061691A2 (fr) 2006-11-24 2007-11-20 Procédé et dispositif d'échange de données

Publications (1)

Publication Number Publication Date
EP2098014A2 true EP2098014A2 (fr) 2009-09-09

Family

ID=39364051

Family Applications (1)

Application Number Title Priority Date Filing Date
EP07846677A Withdrawn EP2098014A2 (fr) 2006-11-24 2007-11-20 Procédé et dispositif d'échange de données

Country Status (5)

Country Link
US (1) US20100017539A1 (fr)
EP (1) EP2098014A2 (fr)
CN (1) CN101554019A (fr)
DE (1) DE102006055959B3 (fr)
WO (1) WO2008061691A2 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102143055B (zh) * 2010-11-26 2013-10-09 华为技术有限公司 接入节点的业务控制方法和装置
CN102025569B (zh) * 2010-12-15 2016-03-30 中兴通讯股份有限公司 点到点的远端环回测试方法及系统及装置
JP6391839B2 (ja) * 2015-07-30 2018-09-19 三菱電機株式会社 空気調和装置の室内機

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050099954A1 (en) * 2003-11-10 2005-05-12 Nortel Networks Limited Ethernet OAM network topography discovery

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO2008061691A2 *

Also Published As

Publication number Publication date
WO2008061691A2 (fr) 2008-05-29
CN101554019A (zh) 2009-10-07
WO2008061691A3 (fr) 2008-07-17
US20100017539A1 (en) 2010-01-21
DE102006055959B3 (de) 2008-07-24

Similar Documents

Publication Publication Date Title
DE60216221T2 (de) Verfahren und Vorrichtung zur automatischen Erkennung von logischen Verbindungen zwischen Netzvorrichtungen
DE60035830T2 (de) Netzwerkgeräteverwaltungsvorrichtung und - verfahren
DE60207368T2 (de) Verfahren und Vorrichtung zur automatischen Erkennung von Netzelementen mit Datenübertragungsfähigkeiten
DE69828600T2 (de) Steuerung in einem datenzugriffsübertragungsdienst
DE69737150T2 (de) System zur parameteranalyse und verkehrsüberwachung in atm-netzen
DE60012913T2 (de) Kabelintegritätsprüfungstechnik für entfernte haussicherheitsüberwachung
DE60131615T2 (de) Topologiebestimmung in atm-netzen
EP1869839B1 (fr) Procédös, progiciel et element de noeuds de röseau pour identifier plus rapidement des defaillances sur des voies de transmission et/ou dans des noeuds
DE602004008726T2 (de) Dynamisches System zur Übertragung von Netzwerküberwachungsdaten an Knoten ausserhalb des Management Systems
DE69816026T2 (de) Verfahren zur Erzeugung eines Verwaltungskanals in einem optischen Netzwerk, ein Leitungsabschluss, eine erste Netzabschlusskarte und eine zweite Netzabschlusskarte zur Durchführung des Verfahrens
EP0993714A2 (fr) Procede et systeme pour commander l'utilisation de la capacite de transmission de satellites dans des reseaux terrestres
DE102006055959B3 (de) Verfahren und Vorrichtung zum Austausch von Daten
DE602005002418T2 (de) Verwaltungsverfahren und -system für Netzverwaltungssysteme
EP2938004B1 (fr) Tête de bus et système et procédé de liaison résistante à la défaillance d'appareils d'extrémité de ligne de transport d'énergie - large bande à l'aide de ladite de tête de bus dans un réseau principal
EP2028791A1 (fr) Reconnaissance de configurations erronées sur des appareils d'infrastructure en réseau
DE102012020140B3 (de) Verfahren und Datenübertragungsgerät zur Datenübertragung innerhalb eines xDSL-Datenübertragungssystems, welches wenigstens zwei Ethernet-Netzwerke mittels xDSL Verbindungen miteinander verbindet
DE102006056517B4 (de) Verfahren und Vorrichtung zum Konfigurieren einer OAM-Einstellung
DE102005003059B4 (de) Verfahren zum Betreiben einer Netzwerkmanagementstation
EP1371236B1 (fr) Procede de reacheminement selectif et collectif de messages dans un reseau de gestion de telecommunications
DE10343796B4 (de) Verfahren zur Verwaltung einer Gruppe von Netzzugangsservern
EP2854345A1 (fr) Procédé et appareil de communication couplé pour la transmission de messages dans un réseau de communication industriel à fonctionnement redondant
DE60206259T2 (de) Mehrfach-Brücke für eine Vielzahl gegenseitig unterschiedlichen Teilnetzwerken
EP2311240B1 (fr) Procédé d'adressage de points terminaux ainsi que réseau aménagé pour ce procédé et n ud d'accès
EP1313261A1 (fr) Appareil et procédé pour la gestion d' un système de télécommunication consistant de multiples réseaux
DE19946534A1 (de) System zum Austausch von Daten

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20090624

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC MT NL PL PT RO SE SI SK TR

DAX Request for extension of the european patent (deleted)
17Q First examination report despatched

Effective date: 20101022

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20110503