WO2015067827A1 - Procédé et appareil de configuration du plan de commande d'éléments du réseau dans un réseau de télécommunications et produit programme d'ordinateur - Google Patents

Procédé et appareil de configuration du plan de commande d'éléments du réseau dans un réseau de télécommunications et produit programme d'ordinateur Download PDF

Info

Publication number
WO2015067827A1
WO2015067827A1 PCT/ES2013/070766 ES2013070766W WO2015067827A1 WO 2015067827 A1 WO2015067827 A1 WO 2015067827A1 ES 2013070766 W ES2013070766 W ES 2013070766W WO 2015067827 A1 WO2015067827 A1 WO 2015067827A1
Authority
WO
WIPO (PCT)
Prior art keywords
configuration
control plane
network
interface
dcpcm
Prior art date
Application number
PCT/ES2013/070766
Other languages
English (en)
Spanish (es)
Inventor
Victor Lopez Alvarez
Luis Miguel Contreras Murillo
Fernando Muñoz Del Nuevo
Original Assignee
Telefonica, S.A.
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 Telefonica, S.A. filed Critical Telefonica, S.A.
Priority to PCT/ES2013/070766 priority Critical patent/WO2015067827A1/fr
Publication of WO2015067827A1 publication Critical patent/WO2015067827A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements

Definitions

  • the present invention relates generally to the configuration parameters of computer networks and, more particularly, to a method, an apparatus and a computer program product for the configuration of the control plane of the network elements in a telecommunications network .
  • the Central Transportation Networks comprise a control, a management and a data plane.
  • the data plane is the network used for the transmission of information, while the management plane handles global operations, including accounting, security assessment, monitoring reports, etc.
  • the control plane is in charge of the management of decentralized management problems such as the exchange of routing information, monitoring the state of the link and establishing and breaking down connections. Additionally, the control plane manages the Agreements at the Service Level (SLA) and supervises the QoS offered to the connections.
  • Fig. 1 illustrates a reference of network that summarizes the main functionalities of each plane for an optical network.
  • the optical nodes are connected through Physical Interfaces (Pl). These interfaces are those that are part of the data plane.
  • the Optical Connection Controllers (OCC) are capable of managing the optical node through the Connection Control Interface (CCI). This CCI is normally internal to the optical node, because the OCC and the optical node are in the same rack. If OCCs wish to exchange information with each other, they must use the Network-Network Interface (NNI).
  • NNI Network-Network Interface
  • the NNI interfaces are part of the control plane and, consequently, the NNI exchanges information only from the control plane. This mechanism is called "out-of-band" signaling, because the information is sent using a different network than the data plane.
  • the interconnection between the entities of the control and management plane is done through the Network Management Interface for the ASON Control Plane (NMI-A), while the connection with the data plane uses the Network Management Interface Network for the Transportation Network (NMI-T).
  • NMI-A Network Management Interface for the ASON Control Plane
  • NMI-T Network Management Interface Network for the Transportation Network
  • UNI User Network Interface
  • client computer In the case of central networks, these client nodes are IP / MPLS routers. Any optical node uses this control-data architecture, regardless of OTN technology, Wavelength Switched Optical Networks (WSON) or Elastic Optical Networks (EON).
  • WSON Wavelength Switched Optical Networks
  • EON Elastic Optical Networks
  • the GMPLS is not a protocol but a control plane framework that includes the following protocols:
  • RSVP-TE Resource Reserve Protocol-Traffic Engineering
  • CR-LDP Label Distribution Protocols based on Restrictions
  • a discovery and monitoring protocol such as the Link Management Protocol (LMP). This protocol is able to discover the interconnection of the interfaces and it is checked if the interfaces are still working.
  • LMP Link Management Protocol
  • PCEP Path Calculation Element Protocol
  • a path computation element PCE
  • PCE path computation element
  • the PCE is useful for interconnection of multi-domain and multi-layer scenarios.
  • IP / MPLS routers have a configuration to execute routing and reservation protocols.
  • the main difference compared to optical nodes is that IP / MPLS routers use "in-band" signaling. The same interface is used to send user packets and to send the status information of routing or reservation protocols.
  • the control plane may exist in the routers. Later in this document, we will refer to the network elements like any device in the core network: optical device or router. It is also assumed that there is an interface in the control plane on IP / MPLS routers.
  • the main parameters of the control are configured once the device has an IP address. This setting depends on the settings defined by the operator.
  • An example of this configuration is PCE activation, routing selection (OSPF or ISIS) and resource reservation protocols (RSVP or LDP).
  • Network Elements (NE) interface identifiers These are unique identifiers for the ports in the data plane. These unique identifiers can be numbered or unnumbered interfaces that use IPv4 or IPv6. When using numbered interfaces each NE interface has a unique IP address. When there are unnumbered interfaces, each controller in the control plane has a unique IP and each port has an internal number as an identifier.
  • CP TE links represent the connections between the NE neighbors. To configure these parameters, it is required to have a Local_Link_ID and a Remote_Link_ID, which represent the interfaces in each NE, and an ID for this connection. These Local_Link_ID and Remote_Link_ID correspond to the interface of the CP defined in 1.
  • a technical problem to be solved is to deploy an integrated and coherent control plane configuration (through the nodes involved in the network) that can lead to an optimal network configuration.
  • the network cannot function because there is no action to signal any network process.
  • the main problem of the current approach is that an incorrect configuration of the control plane cannot be corrected in real time, instead of the current independent approach, in which each node is configured individually and manually.
  • US-B1-8054855 'Dynamic interface configuration for supporting multiple versions of a communication protocol' provides a configuration mechanism capable of configuring different protocol versions over a certain interface depending on the traffic received from a user terminal.
  • the essence of this control manager is the automatic decision node by node, without coordination with the rest of the network elements.
  • the present invention proposes to consider a centralized system capable of coordinating the sharing of the network elements under its control. Additionally it is a separate element, which then simplifies the behavior and process needs of each single node.
  • the solution proposed in US-B1-8054855 works on the configuration of data plane interfaces based on user behavior, while the present invention is within the scope of control plane technologies and the configuration required for a network operator on demand.
  • the present invention proposes a mechanism that minimizes the configuration procedures of the elements of the central network to avoid a bad configuration by delegating the tasks of planning the addressing and configuration of the control plane.
  • a method for the configuration of the control plane of the network elements in a telecommunications network which comprises, as common in the field, the configuration or periodic activation of a configuration of the control plane of at least one network element (NE) that has been previously inserted into at least one layer of a telecommunications network such as an IP / MPLS network or an optical network.
  • NE network element
  • said NE uses an apparatus called as Configuration Manager in the Dynamic Control Plane (DCPCM) physically connected to it to dynamically and automatically execute said configuration or periodic activation, performing said NE the following stages:
  • DCPCM Dynamic Control Plane
  • a pair of said NEs can also be inserted into two different network layers of said telecommunications network.
  • step c) further activates said information of control plane configuration requested by at least the use of an internal self-configuration process.
  • the configuration information of the requested control plane can be carried out by means of an NE Configuration Module of said DCPCM.
  • said TE link configuration can be performed through two different alternatives.
  • the topology server can send the configuration of the TE link to the NE and the latter can activate the configuration of the TE link using an internal self-configuration process.
  • the topology server can remotely configure the TE link. In this case, the configuration can be done using standard NetConf or CLI protocols.
  • an apparatus for the configuration of the control plane of the network elements in a telecommunications network, said apparatus as the Configuration Manager in the Dynamic Control Plane (DCPCM), being physically connected at least to a network element (NE) of a telecommunications network such as an IP / MPLS network or an optical network, said NE being inserted into at least one layer of said telecommunications network, including the apparatus:
  • DHCP server configured to at least receive an address request
  • I P for a control plane port (CP interface) of said NE and to respond to the latter with said IP address;
  • an NE configuration module configured to configure the control plane of said NE
  • DHCP interface that connects said DHCP server with said NE and a provisioning interface that connects said NE configuration module with said NE.
  • a topology server configured to assign identifiers for a data plane port (NE interface) of said NE, for said control plane port (CP interface) and for a TE link;
  • DCPCP controller configured to at least exchange information with the rest of said modules or elements of said DCPCM
  • -a CP configuration module configured to store the plane of configured control of said NE
  • connection interfaces that includes at least:
  • DCPCP interface
  • I C TS interface
  • the proposed device or DCPCM is able to automatically set the control plane configuration based on the profile defined by a network operator. Moreover, the DCPCM can also inform the network operator if a new configuration of said control plane parameters is to be made. In this way, human intervention is avoided and a form of automatic, simultaneous and centralized configuration and activation of several and dispersed NEs is provided.
  • the NEs Once the NEs are properly connected, they can communicate with the DCPCM to obtain the control plane information and automatically load the appropriate control plane configuration based on the input from the DCPCM. If self-configuration is not possible on the NE (or is disabled), the DCPCM can connect to the NE and update its configuration.
  • the DCPDM allows an instantaneous and simultaneous configuration of a variety of NE avoiding multiple and incremental stages of configuration common in the current networks.
  • the DCPDM can check the integrity of the configuration to be deployed even before sending said configuration to the nodes (NE).
  • This one-step configuration through the network accelerates the establishment of the network and prevents configuration errors or bad configurations, reducing the number of direct manual interventions on the NE.
  • a computer program product which has instructions executable by the computer stored therein for the dynamic and automatic configuration of the control plane of at least one network element (NE) inserted in at least one layer of a telecommunications network, producing the instructions executable by computer, when executed by a processor of said NE, steps a) to e) of claim 1 to be performed.
  • NE network element
  • Fig. 1 is an example of the architecture and functionalities of a central transport network.
  • Fig. 2 is an example of the control and data plane blocks in the network elements.
  • Fig. 3 is an example that illustrates how the Dynamic Control Plane Configuration Manager (DCPDM) can be connected to a plurality of network elements (NE).
  • DCPDM Dynamic Control Plane Configuration Manager
  • Fig. 4 is an illustration of the detailed description of the proposed DCPDM according to a second aspect of the present invention.
  • Fig. 5 is a flow chart illustrating the workflow followed by the DCPDM to configure the control plane for an NE when said NE has been inserted into a telecommunications network.
  • Fig. 6 is a flow chart illustrating the workflow for defining the configuration or addressing of the control plane so that a network operator is able to establish the configuration or addressing rules that the DCPDM will use.
  • Fig. 7 is an example of a possible network architecture when the present invention can be deployed in accordance with one embodiment.
  • Fig. 8 illustrates the interaction between the DCPDM modules and the NEs involved in an IP router configuration.
  • Fig. 9 is a flow chart illustrating the steps for an IP router configuration.
  • the DCPCP controller is not shown to simplify the figure, but It is in architecture.
  • Fig. 10 is an example of a multilayer network in which the present invention can be deployed in accordance with one embodiment. Detailed description of the invention and description of various embodiments
  • the present invention proposes a method and an apparatus capable of configuring the control plane parameters of the network elements (NE). These control plane parameters can be configured in a holistic way, allowing an additional network expansion (in terms of new nodes entering the network, or new functionalities that are deployed on them) and to be gently configured in a way Automated and consistent.
  • Fig. 3 illustrates how the proposed DCPDM 100 can be connected to a plurality of network elements (NE) to configure the control plane of said NE.
  • NE network elements
  • Fig. 4 the different modules or elements that may be part of the proposed DCPDM 100 are illustrated. There are some components of the state of the art that are outside the scope of the patent (dashed lines in the figure), but that are related to the architecture:
  • NE Network Element
  • the NE can be (but not limited to) routers, switches, OSC, ROAD, etc.
  • This module is capable of configuring the NE.
  • solutions in the state of the art such as SDN controllers or ML managers that can configure the NE.
  • This module is in charge of the execution of the dynamic configuration protocol of the control plane and the exchange of information with the rest of the modules in the DCPDM 100 and external elements.
  • This module conveys the intelligence of the DCPDM 100 and consequently, the workflows of the procedures are defined therein by coordinating the operation of the complete DCPDM 100 to achieve the addressing of the network control plane in an automated manner.
  • This module assigns the network identifiers for the CP interface, for the NE interface and for the TE links of the CP. This module stores information about the identifiers used in the current network for the control plane.
  • the DCPCP controller 104 is able to define an addressing set to configure the network entities on the topology server 102, as a result of a network operation task.
  • This module stores the control plane configuration for the domain. This configuration defines the protocols to be used in the control plane as well as the parameters (for example, type of numbered or unnumbered interfaces).
  • the DCPDM 100 may also consist of the following interfaces: - DHCP. This interface is based on the standard DHCP protocol and connects a
  • This interface transmits information to configure the control plane configuration in the NE.
  • This interface connects the Control Plane Controller of each NE and the DCPCP Controller 104. This interface is not based on any protocol and is part of the proposal of the present invention.
  • This interface connects the DCPCP Controller 104 and the DHCP Server 101.
  • IDCPC- This interface connects the DCPCP controller 104 and the configuration module 103 of the CP.
  • This interface connects the DCPCP controller 104 and the configuration module 105 of the NE.
  • the workflow can be executed when a new physical configuration of the NE is performed or the status of the device is checked periodically Control Plane
  • the NE obtains an IP address for its control plane interface through DHCP 101.
  • the NE sends a request to the DHCP server 101, which connects to Topology Server 102 to obtain an IP address for this new NE inserted through the DCPCP 104 controller.
  • the NE Control Plane Controller can therefore activate the Control Plane configuration using said physical internal self-configuration process. Alternatively, if this is not possible, the Configuration Module 105 of the NE will perform the configuration at this stage.
  • the NE Control Plane Controller requests identifiers for its NE interface from the Topology Server 102 through the DCPCP 104 controller.
  • the NE Control Plane Controller checks whether there are new neighbors running a discovery and monitoring protocol, that is, a link management protocol (LMP), to correlate the NE interface.
  • LMP link management protocol
  • the Control Plane Controller of the NE checks if new interfaces are discovered in the previous stage 7. If there are any, go to the next stage 9, otherwise it goes through A meaning the end of the process.
  • Fig. 6 the workflow for defining the configuration or addressing of the control plane is described so that a network operator is able to establish the configuration or addressing rules that the DCPCM 100 will use.
  • the network operator defines the new network dimensioning to be used in the telecommunications network in the DCPCM 100.
  • the DCPCP 104 will be in charge of coordinating the configuration of the new address since it is the central element.
  • DCPCP 104 asks Topology Server 102 about the new address to see if there is an inconsistency with the equipment already configured and installed.
  • DCPCP 104 will ask the network operator for permission to proceed.
  • DCPCP 104 will start the configuration procedure.
  • the DCPCM 100 is supposed to solve the sizing and configuration in the control plane in a telecommunications network.
  • Fig. 7 illustrates a possible architecture in which the DCPCM 100 can operate.
  • a network domain is defined with a dimensioning of the control plane configured from an addressing set.
  • the DCPCM 100 is installed and ready to communicate with the NEs and has learned the control plane addresses already used. He has also decided on the addressing set from which he will choose the addresses to be given to the new NE.
  • the Control Plane process starts when a generic NE is inserted into the network.
  • the NE obtains an IP address for its Control Plane interface through the DHCP 101 server. To do this, the NE sends a request to the DHCP server 101, which connects to the Topology Server 102 to obtain an IP address for this new NE through the DCPCP 104 controller.
  • the Control Plane controller requests the general configuration of the Control Plane from the Control Module. Configuration 103 of the CP.
  • the NE Control Plane controller activates the Control Plane configuration. This can be done through two different alternatives.
  • Control Plane configuration module can send the Control Plane configuration to the Control Plane controller and subsequently the Control Plane controller activates the Control Plane configuration using the internal self-configuration process.
  • the configuration module 105 of the NE remotely performs the configuration. This configuration can be done using the NetConf or CLI standard, for example.
  • the NE Control Plane controller requests identifiers for its NE interface from the Topology Server 102 through the DCPCP controller 104.
  • the NE Control Plane controller then 7) checks for new neighbors running by example the Link Management Protocol (LMP) to correlate the NE interface.
  • the NE Control Plane controller 8) tests whether new interfaces were discovered in the previous stage 7. If there is one, go to step 9, otherwise it goes through A. An exchange of information is made, 9) between the controller of the NE Control Plane and the Topology Server 102 to obtain the configuration information for The new TE Link.
  • the TE Link configuration is done. Two different alternatives can be used. For example, Topology Server 102 may send the TE Link configuration to the NE Control Plane controller.
  • Control Plane controller activates the TE Link configuration using the internal self-configuration process. Or, alternatively, if auto-configuration is not supported on the computer, Topology Server 102 would remotely perform the configuration. This configuration can be done using NetConf or CLI standard.
  • Fig. 8 illustrates the interaction between the different modules of the DCPCM 100 and the elements of the NE involved in said NE IP or router configuration.
  • Fig. 9 illustrates the steps for said configuration of the IP router.
  • the DCPCP controller 104 in this case has not been illustrated to simplify the figure, but it is in the architecture.
  • the DCPCM 100 can also be applied in a multilayer network for an IP / MPLS or a transport node to address and configure the control plane.
  • the same procedure described in Fig. 7 would be applied in this case.
  • each node it is from a different network layer so that the DCPDM 100 is able to configure the control plane addresses from two separate addressing sets.
  • the routing sets to use are 172.16.1.x for nodes of the transport layer and 192.168.1.x for IP / MPLS nodes.
  • the stages for the configuration are similar for each layer, but with different configurations.
  • the present invention in comparison with the current control plane configuration procedures (including sizing, port identification, etc.) where an addressing plan has to be defined by a human and must also be manually included in the network nodes for to make them capable of operating in the telecommunications network, it improves the current solutions by: avoiding a bad configuration due to human failure when defining the address of the control plane and other parameters for the network nodes; avoid bad configuration due to human failure when addressing and other configuration parameters are entered in the network nodes; decrease of the period of time required for an NE to be operational in a network since the proposed solution can allow it automatically at a time of node installation; in the case of multiple control plane addressing changes, you can solve this problem in an automated way and in multiple NEs at the same time by preventing the network from being activated node by node when this procedure has to be performed by human intervention; better network reliability since any node can be recovered from a total stop immediately from the configuration manager.

Landscapes

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

Abstract

L'invention concerne un procédé, un appareil et un produit programme d'ordinateur pour la configuration du plan de commande d'éléments du réseau dans un réseau de télécommunications, le procédé consistant en la configuration ou en l'activation périodique de la configuration du plan de commande d'au moins un élément de réseau (NE) préalablement installé dans au moins une couche d'un réseau de télécommunications, ledit NE utilisant un DCPCM physiquement relié à ce dernier pour l'exécution dynamique et automatique de ladite configuration ou activation périodique. L'appareil est configuré pour établir dynamiquement et automatiquement la configuration du plan de commande sur la base de préférence d'un profil défini par un opérateur.
PCT/ES2013/070766 2013-11-06 2013-11-06 Procédé et appareil de configuration du plan de commande d'éléments du réseau dans un réseau de télécommunications et produit programme d'ordinateur WO2015067827A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/ES2013/070766 WO2015067827A1 (fr) 2013-11-06 2013-11-06 Procédé et appareil de configuration du plan de commande d'éléments du réseau dans un réseau de télécommunications et produit programme d'ordinateur

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/ES2013/070766 WO2015067827A1 (fr) 2013-11-06 2013-11-06 Procédé et appareil de configuration du plan de commande d'éléments du réseau dans un réseau de télécommunications et produit programme d'ordinateur

Publications (1)

Publication Number Publication Date
WO2015067827A1 true WO2015067827A1 (fr) 2015-05-14

Family

ID=53040943

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/ES2013/070766 WO2015067827A1 (fr) 2013-11-06 2013-11-06 Procédé et appareil de configuration du plan de commande d'éléments du réseau dans un réseau de télécommunications et produit programme d'ordinateur

Country Status (1)

Country Link
WO (1) WO2015067827A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001086908A1 (fr) * 2000-05-10 2001-11-15 Nokia Corporation Procede d'allocation automatique d'adresses ip
WO2003001397A1 (fr) * 2001-06-22 2003-01-03 Elematics, Inc. Procede et appareil d'approvisionnement d'une voie de communication
US20030163555A1 (en) * 2001-02-28 2003-08-28 Abdella Battou Multi-tiered control architecture for adaptive optical networks, and methods and apparatus therefor
EP2341661A1 (fr) * 2010-01-04 2011-07-06 Alcatel Lucent Découverte de voisinage pour ligne Ethernet privée sur des interfaces de réseau d'utilisateur

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001086908A1 (fr) * 2000-05-10 2001-11-15 Nokia Corporation Procede d'allocation automatique d'adresses ip
US20030163555A1 (en) * 2001-02-28 2003-08-28 Abdella Battou Multi-tiered control architecture for adaptive optical networks, and methods and apparatus therefor
WO2003001397A1 (fr) * 2001-06-22 2003-01-03 Elematics, Inc. Procede et appareil d'approvisionnement d'une voie de communication
EP2341661A1 (fr) * 2010-01-04 2011-07-06 Alcatel Lucent Découverte de voisinage pour ligne Ethernet privée sur des interfaces de réseau d'utilisateur

Similar Documents

Publication Publication Date Title
EP2717526B1 (fr) Système et procédé de réseau définis sur logiciel par l'intermédiaire d'un élément de commande et de calcul de trajet
US9621969B2 (en) Management and control of software defined networking enabled open transport networks
US9621968B2 (en) Multi layer, multi vendor, multi domain, applications for software defined networking enabled networks
US11240145B2 (en) Shared risk representation in networks for troubleshooting, assignment, and propagation across layers
EP3384640B1 (fr) Communication entre des contrôleurs de réseau
US8824461B2 (en) Method and apparatus for providing a control plane across multiple optical network domains
US10187152B2 (en) Control plane extensions for optical broadcast networks
WO2015042824A1 (fr) Procédé et dispositif d'établissement de chemin inter-domaine
US10374935B2 (en) Link discovery method, system, and device
WO2002015442A1 (fr) Systeme, dispositif et procede de gestion de services de communication dans un systeme de communication optique
CN107735989B (zh) 用于传输网络上站点互连的方法和系统
US8290367B2 (en) OSS support for control plane technology
US20080205262A1 (en) Node controller and node system
US9391842B2 (en) Self-configuring transport network
US10778562B2 (en) Path computation in a multi-tenant network
US20150163094A1 (en) Method of and apparatus for configuring a link in a label switching communication network
US20160057010A1 (en) Method and system for mapping different layouts
WO2015067827A1 (fr) Procédé et appareil de configuration du plan de commande d'éléments du réseau dans un réseau de télécommunications et produit programme d'ordinateur
US20200374212A1 (en) Method of automatic setup by a first device of a session complying with a dynamic routing protocol with a second device
Zhao et al. Experimental demonstration of bandwidth on demand (BoD) provisioning based on time scheduling in software-defined multi-domain optical networks
Xu et al. Multicarrier-collaboration-based emergency packet transport network construction in disaster recovery
Santuari et al. Policy-based restoration in IP/optical transport networks
Bahnasy et al. Software-defined DWDM optical networks: OpenFlow and GMPLS experimental study
EP3007393B1 (fr) Procédé et système pour traiter une signalisation rsvp-te
US20240073125A1 (en) Dynamic path computation in networks based on automatically detected unavoidable risks

Legal Events

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

Ref document number: 13896953

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13896953

Country of ref document: EP

Kind code of ref document: A1