WO2007012223A1 - Procede automatique de calcul d'acheminement hierarchise dans un reseau optique commute et d'etablissement de connexion - Google Patents

Procede automatique de calcul d'acheminement hierarchise dans un reseau optique commute et d'etablissement de connexion Download PDF

Info

Publication number
WO2007012223A1
WO2007012223A1 PCT/CN2005/001140 CN2005001140W WO2007012223A1 WO 2007012223 A1 WO2007012223 A1 WO 2007012223A1 CN 2005001140 W CN2005001140 W CN 2005001140W WO 2007012223 A1 WO2007012223 A1 WO 2007012223A1
Authority
WO
WIPO (PCT)
Prior art keywords
domain
routing
connection
controller
node
Prior art date
Application number
PCT/CN2005/001140
Other languages
English (en)
Chinese (zh)
Inventor
Peng Gao
Original Assignee
Zte Corporation
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 Zte Corporation filed Critical Zte Corporation
Priority to CN2005800493120A priority Critical patent/CN101147348B/zh
Priority to PCT/CN2005/001140 priority patent/WO2007012223A1/fr
Publication of WO2007012223A1 publication Critical patent/WO2007012223A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062—Network aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062—Network aspects
    • H04Q2011/0073—Provisions for forwarding or routing, e.g. lookup tables
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q11/00—Selecting arrangements for multiplex systems
    • H04Q11/0001—Selecting arrangements for multiplex systems using optical switching
    • H04Q11/0062—Network aspects
    • H04Q2011/0088—Signalling aspects

Definitions

  • the present invention relates to the field of Intelligently Switched Optical Network (ASON), and particularly relates to a method for routing calculation and connection establishment in a hierarchical optical network.
  • ASON Intelligently Switched Optical Network
  • optical network intelligence in a protocol that adds automatic control, this network combines IP efficiency, DWDM capacity, and SDH/SONET robustness with advanced control software to give optical networks unprecedented flexibility and Upgradeability.
  • ASON is one of the best solutions.
  • the distributed connection establishment in the ASON network replaces the centralized connection establishment in the traditional optical network.
  • Each node has the connection routing calculation and selection capability, which requires the use of routing protocols to propagate network topology information.
  • RA Routing Area
  • a hierarchical routing scheme is proposed, that is, the network is divided into different levels of routing domains.
  • G.8080 drafted by ITU-T gives the relationship between routing domain hierarchy and subnet point pool (SNPP), and G.7715 illustrates the path of ASON.
  • OIF Optical Interconnection Forum
  • OSPF Open Shortest Path First
  • the technical problem to be solved by the present invention is to provide a method for automatically calculating the hierarchical routing calculation and connection establishment of an optical network, and calculating a route in a hierarchical manner for an optical network having a hierarchical structure, and establishing an optical marking channel.
  • Node Control point with control plane routing controller (RC), connection controller (CC), and more.
  • Ingress node A node in a domain that receives connection establishment requests from users, other routing domains, or other nodes in the domain to complete intra-domain routing calculations.
  • the ingress node corresponds to a specific connection establishment request, and different services may have different ingress nodes.
  • the routing controller (RC) of the endorsement point is responsible for the general routing protocol tasks in addition to other nodes. Corresponding routing controller communication at a routing level.
  • the connection controller (CC) of the endorsement point is responsible for receiving the upper layer connection request and returning the connection establishment result. If the endorsement point is not the ingress node of the connection request, it needs to be received.
  • the connection request of the upper domain is sent to the corresponding ingress node of the domain.
  • the present invention provides a method for automatically routing optical network hierarchical routing calculation and connection establishment, which is applied to an optical network having a hierarchical structure, including the following steps:
  • the ingress network element After receiving the connection establishment request of the user, the ingress network element sends the connection controller CC1 corresponding to the ingress node in the routing domain RA1, and the domain RA1 includes the routing domain in which the service source network element and the destination network element are located;
  • Each routing domain that receives the connection request queries the routing controller of the ingress node to obtain the intra-domain route, and initiates the connection establishment process in the domain. If the domain is the underlying domain, the establishment of the intra-area optical marking channel is completed. Perform step (e), if the domain also contains the underlying domain, perform step (d);
  • connection controller of each node on the route in the domain sends a connection establishment request of the subnet to the connection controller of the end point of the corresponding next layer domain, and returns to step (c);
  • Each routing domain that receives the connection request returns the connection establishment result to the connection controller CC1 of the routing domain RA1 through the connection controller of its end point, and then returns to the ingress network element that initiated the connection establishment. .
  • the foregoing method may further have the following features:
  • the interaction of the inter-layer routing information is performed by a routing controller of the endorsement point in each domain and a routing controller of the corresponding node of the upper layer domain, the layer The routing controller understands the network topology in the domain through the "flooding" process in the domain, so that the routing controllers of each node in the routing domain have the routing information of the local domain and all the lower routing domains included in the domain.
  • the ingress network element determines the routing domain RA1 to which the connection request should be sent according to the domain inclusion relationship obtained from the directory server.
  • Step (c) In the connection establishment process in the routing domain, after the connection controller of the node on the route receives the connection establishment message, negotiates to allocate the link connection, and then goes to the domain.
  • the connection controller of the next node sends a connection establishment message, if the routing controller of the node corresponds to a next layer domain and the next layer domain is covered by the subnet connection In the routing domain, the connection controller of the node also sends a subnet connection establishment request to the connection controller of the next layer domain endorsement point.
  • connection establishment process in the routing domain adopts an RS VP signaling process.
  • the above method may further have the following features: the node in the step (d) is connected to the controller of the next layer domain, and the routing controller of the same node as the connection controller is configured. The corresponding end point of the next level domain.
  • the foregoing method may further have the following features: in the step (d), after the connection controller of the endorsement point receives the subnet connection establishment request, if the endorsement point is not the ingress node of the connection request, the The subnet connection establishment request is sent to the ingress node corresponding to the domain.
  • the connection controller of each node in each intra-domain route receives the connection establishment result returned by the next node on the route, and corresponds to the next layer domain.
  • the connection establishment result returned by the domain end point connection controller is also received, and then the connection establishment result is returned to the previous node, and the connection is received.
  • the result of the establishment is successful, the result of the successful connection establishment is returned. Otherwise, the result of the failure is returned, and the resource release processing is performed on the established connection.
  • the foregoing method may also have the following features:
  • the signaling interaction process between different routing domains without a relationship is a parallel process.
  • FIG. 1 is a schematic structural diagram of a hierarchical optical network according to an embodiment of the present invention.
  • FIG. 2 is a corresponding diagram of a routing controller and a lower layer network domain according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of signaling interaction of connection establishment in an embodiment of the present invention.
  • the network consists of four layers, each layer consisting of a number of routing domains.
  • Each routing domain consists of a control plane component and a transport plane resource, and is physically associated with a certain number of network elements including a control plane logic processing board, each control plane logic processing board including a connection controller (CC), routing control Control plane processing functions such as RC and Link Resource Management (LRM) logically refer to control points with functions such as control plane routing controller (RC) and connection controller (CC) as nodes.
  • the routing controllers and connection controllers of the same number mentioned below refer to different control function modules of the same node at the physical level. For example, the routing controller N123 and the connection controller N123 refer to different control functions of the same node. Only some of the nodes in the domain are shown in the figure.
  • the bottom layer of the hierarchical optical network structure of Figure 1 contains seven routing domains: L1RAK L1RA2, L1RA3, L1RA4, L3RA2, L2RA3, L2RA4, where the bottom layer refers to the layer closest to the transport plane, and L3RA2 and L2RA3, L2RA4 are logically three. Layer and second layer, but belong to the bottom layer.
  • the network element nodes N1 ll, N112, N121, N122, N13, N132, N141, N142, N321, N322, N23, N232, N241, and N242 are transport layer network elements that physically have optical connections, and the routing domain L1RA1 is composed of network elements N111.
  • N112 and control plane logic processing functions are implemented, and other underlying routing domains are similar to routing domain L1RA1.
  • the routing domain L2 A1, L2RA2, L2RA3, and L2RA4 form a logical second layer.
  • the routing domains L3RA1, L3RA2, and L3 A3 form a logical third layer, and the routing domain L4RA constitutes a logical fourth layer.
  • routing domain L4RA Relationship between routing domain L4RA and routing domains L3RA1, L3RA2, L3RA3, relationship between routing domain L3RA1 and routing domain L2RA1, L2RA2, relationship between routing domain L3RA3 and routing domain L2RA3.
  • L2RA4 routing domain L2RA1 and routing domain
  • the relationship between L1RA1 and L1RA2 and the relationship between the routing domain L2RA2 and the routing domains L1RA3 and L1RA4 satisfy the inclusion policy recommended by ITU-T G.8080.
  • the routing domains L3RA1, L3RA2, and L3RA3 are referred to as the routing domain L4RA.
  • the next layer domain, the next layer domain L2RA1, L2RA2 included in the domain L3RA1 is referred to as the routing domain included in the upper layer domain L4RA, and so on.
  • the user first configures the optical network hierarchy and domain endorsement points through the management plane.
  • the black filled network element node in Figure 1 is the endorsement point specified by the management plane.
  • a corresponding routing controller is configured in the upper layer routing domain.
  • nodes N111, N12, N131, and N141 are the endorsement points of the routing domains L1RA1, L1RA2, L1RA3, and L1RA4, respectively.
  • Nodes N211, N212, N221, and N222 are the endorsement points N1ll, N121, N131, and N141, respectively.
  • Nodes N212 and N221 are the endorsement points of the routing domains L2RA1 and L2RA2, respectively.
  • Nodes N311 and N312 are the nodes where the corresponding routing controllers on the third layer are the endorsement points N212 and N221, respectively.
  • Node N311 is the end point of the routing domain L3RA1, and node N411 is the node where the routing controller corresponding to the N311 on the fourth layer is located.
  • Node N321 is the end point of the routing domain L3RA2, and node N412 is the node where the corresponding routing controller of the third layer on the fourth layer.
  • the nodes N231 and N241 are the endorsement points of the routing domains L2RA3 and L2RA4, respectively, and the nodes N331 and N332 are the nodes where the routing controllers corresponding to the third layer and the N231 and N241 are respectively located.
  • Node N331 is the end point of the routing domain L3RA3, and node N413 is the node where the routing controller N331 corresponds to the routing controller on the fourth layer.
  • the L4RA domain is the top-level routing control domain and has no endorsement points.
  • the routing controller of the local layer learns the network topology in the domain through the "flooding" process in the domain. Some routing controllers in the local domain are also responsible for communicating with the corresponding lower-layer routing domain, and knowing the routing information of the corresponding lower-layer routing domain. And distributed in the routing domain "flooding", forming a stable hierarchical relationship that can be used for routing calculation.
  • the routing controller of each node in each routing domain has this routing domain and all the lower-layer routes included in the routing domain.
  • the routing information of the domain, each node can respond to the routing query request and calculate the intra-domain route.
  • Figure 2 shows the correspondence between the routing controller and the routing control domain of the underlying network. For example, the routing controller of node N211 corresponds to routing control domain L1RA1, the routing controller of node N212 corresponds to routing control domain L1RA2, and so on.
  • FIG. 3 is a schematic diagram of signaling interaction for establishing a hierarchical routing connection in the embodiment.
  • a line marked with S+ digits indicates a forwarding process of signaling, and hundreds and ten digits of the number indicate a sequence number of the process, and the number of digits indicates Different processing examples.
  • the single digits of the signaling procedure within the same domain indicate the order of the signaling procedures, excluding the processing time of the connection setup signaling. It should be noted that although the following process involves signaling interaction between different domains. The process is written in one step, but only for the sake of simplicity. The signaling interaction process between different domains is a parallel process, and there is no order relationship.
  • the user requests the optical network to establish a connection from the network element Ni1 to the network element N242.
  • the user specifies the label of the network element N111 and the outgoing label of the network element N242, where
  • the tag refers to the point of the upper and lower business, the corresponding physical concept, which can be a port on the device. This process is shown in process 11 in Figure 3.
  • Step 1 The ingress network element N111 receives the connection request of the user, and according to the domain inclusion relationship, determines to directly send the connection establishment request to the corresponding ingress connection controller N411 in the fourth layer routing domain L4RA, and the process is in FIG. S11 shows;
  • connection establishment request needs to be sent to the upper routing domain, which needs to span several layers, and the domain inclusion relationship can be obtained according to various methods such as "directory server".
  • directory server To determine that the upper-layer domain needs to include the domain where the network elements at both ends of the service are located.
  • Step 2 The connection controller N411 queries the routing controller of the node, and the routing controller N411 calculates the routing result in the domain L4RA as N411 ⁇ N412 ⁇ ->N413, and then connects the controller N411 to the connection controller N412, and the connection control
  • the device N412 sequentially initiates a connection establishment process to the connection controller N413, which is illustrated in FIG. 3 by process S21 and process S22;
  • the connection establishment process in the domain may adopt the RSVP signaling process.
  • the connection controller of the node N412 negotiates to allocate the link connection, and sends a Path message to the connection controller of the next node N413 in the domain, if the route control of the node
  • the device (or other corresponding routing controller) corresponds to the included lower layer domain, and the connection controller also needs to send a subnet connection establishment request to the connection controller of the next layer domain end point.
  • Step 3 After receiving the connection establishment request, the connection controllers N411, N412, and N413 in the domain L4RA determine the inbound and outbound NEs of the next-layer routing domain covered by the subnet connection based on the inclusion relationship of the routing domain, and establish the subnet connection.
  • the request is sent to the endorsement points N311, N321, and N331 of the lower layer network corresponding to the routing controller of the same node (which can also be specifically designated). This process is shown in FIG.
  • the processes S31, S32 and S33 show that if the routing controller of the node on the route does not have a corresponding routing layer of the next layer or the routing domain of the next layer is not covered by the subnet connection, there is no need to send a subnet connection establishment request. ;
  • Step 4 The end points N311 and N331 of the domain L3RA1 and L3RA3 are also the ingress nodes of the connection.
  • the intra-domain routes are respectively calculated in the domains L3RA1 and L3RA3, and the endorsement point N311 is calculated in the domain L3RA1.
  • the routing result is N311 ⁇ ->N312, and the routing result calculated by the end point N331 in the domain L3RA3 is N331 ⁇ ->N332, and the end point N311 and the endorsement point N331 respectively initiate a connection establishment process to N312 and N332 according to the routing calculation result.
  • This process is illustrated in Figure 3 by process S41 and process S42;
  • Step 5 The connection controllers N311 and N312 in the domain L3RA1 send the subnet connection establishment request to the endorsement points N212 and N221 of the lower layer network corresponding to the routing controller of the same node according to the inclusion relationship of the routing domain; likewise, in the domain L3RA3
  • the connection controllers N331 and N332 send subnet connection establishment requests to the endorsement points N231 and N241 of the lower layer network corresponding to the routing controller of the same node. This process is illustrated in Figure 3 by processes S51, S52, S53 and S54;
  • Step 6 after the domain L2RA1 and L2RA2 endorsement points N212 and N221 receive the subnet connection establishment request, in the domain L2RA1, the endorsement point N212 is not the ingress node of the subnet connection, and the subnet connection establishment request needs to be sent to the domain.
  • the ingress node N211 the process is shown in the process S55 in FIG.
  • the end point (also the ingress node) N221 in the node N211 and the domain L2RA2 in the domain L2RA1 respectively calculate the intra-domain route, and the route result calculated by the node N211 in the domain L2RA1 is N211 ⁇ ->N212, the routing result calculated by the end point N221 in the domain L2RA2 is N221 ⁇ N222, and the node N211 and the endorsement point N221 initiate a connection establishment process to N212 and N222 according to the routing calculation result.
  • This process is illustrated in Figure 3 by process S61 and process S62;
  • Step 7 according to the inclusion relationship of the routing domain, the connection controllers N211 and N212 in the domain L2RA1 send the subnet connection establishment request to the endorsement points N1 11 and N121 of the lower layer network corresponding to the routing controller of the same node; likewise, the domain L2RA2 The connection controllers N221 and N222 send the subnet connection establishment request to the endorsement points N131 and N141 of the lower layer network corresponding to the routing controller of the same node, and the process is shown in FIG. 3 by processes S71, S72, S73, and S74;
  • Step 8 the underlying routing domains L1RA1, L1RA2, L1RA3, L1RA4, L3RA2, L2RA3,
  • the underlying domain performs the actual data path establishment process. Each of the underlying domains is successfully established, and the entire service is successfully created.
  • the data flow will pass through the ingress NE N111 through the NEs N112, N12 N122, N13 N132, N141 of each underlying domain.
  • N142, N32 N322, N23 N232, and N241 arrive at the egress network element N242.
  • connection controller of each intra-domain node returns the connection establishment result to the connection controller of the endorsement point in the domain (if the endorsement point is not the ingress node, each node first returns the connection establishment result to the connection controller of the ingress node, and then sends it to the connection controller
  • the connection controller of the domain end point the connection controller of the endorsement points N1 ll, N12K N13 N141, N321, N23 N241 returns the connection establishment result to the upper layer routing domain nodes N211, N212 to which the connection establishment request is sent. , N22 N222, N412, N331, N332 connection controller. This process is illustrated in Figure 3 by processes S81, S82, S83, S84, S85, S86, S87;
  • Step 9 The connection controllers N212 and N222 that receive the connection establishment result returned by the next layer in the domain L2RA1 and L2RA2 respectively return the connection establishment result to the connection controllers of the local node entry nodes N211 and N221, and the process is as follows: Processes S88 and S92 in 3. Since the N211 is not an endorsement point, the connection establishment result is sent to the connection controller of the domain end point N212, and the process is as shown in process S91 in FIG. 3;
  • Step 10 The connection controllers of the domains L2RA1 and L2RA2
  • the connection controllers of N212 and N221 return the connection establishment result to the connection controller of the upper-layer routing domain nodes N311 and N312 to which the connection establishment request is sent. This process is shown in processes S101 and S102 in FIG. 3;
  • Step 11 The connection controllers N311 and N312 that receive the connection establishment result in the next layer of the domain L3RA1 and L3RA3 respectively return the connection establishment result to the connection controller of the local access nodes N311 and N331, as shown in FIG. Processes S11, S112;
  • Step 12 The connection controllers of the end points N311 and N331 of the domains L3RA1 and L3RA3 return the connection establishment result to the upper-layer routing domain nodes N411 and N413 to which the connection establishment request is sent. Connection controller. As shown in processes S121 and S122 in FIG. 3;
  • step 13 the connection controller N413 in the domain L4RA that receives the connection establishment result of the next layer returns the connection establishment result to the connection controller of the N412, and the connection controller of the N412 returns the connection establishment result to the local node.
  • a connection controller of the N411 as shown in processes S131 and S132 in FIG. 3;
  • Step 14 After receiving the connection establishment result in the intra-domain and the inter-layer, the connection controller of the node N411 returns the result to the node Nl l l that initially initiates the connection establishment. As shown in process N141 in Figure 3.
  • the inter-layer subnet connection establishment request is a connection controller sent to the next layer domain end point. If the endorsement point is not an ingress node of the subnet connection, the subnet connection establishment request is also forwarded to the domain.
  • the connection controller of the ingress node performs route calculation and initiates the connection establishment process. The calculation by the ingress node is a "source route" mode, which can simplify the signaling interaction process.
  • connection controller of each node on the intra-domain route receives the connection establishment result returned by the next node on the route, and corresponds to the next-layer domain, and also receives the connection establishment result returned by the domain end point connection controller. And return the connection establishment result to the previous node.
  • the received connection establishment result is successful, the result of the successful connection establishment is returned. Otherwise, the failed result is returned. In this way, as long as the route calculation or connection establishment failure of any routing domain that receives the connection establishment request fails, the entire connection establishment failure is considered, the failure information is returned to the entry network element, and the resource release processing is performed on the established connection.
  • the interaction process of the hierarchical routing query information used by the present invention provides a hierarchically well-defined route calculation query method when the network scale is large.
  • the method for hierarchical routing calculation and connection establishment of the automatic switched optical network of the present invention can be applied to an intelligent optical network, so that the interaction process of the route calculation and the connection establishment signaling is hierarchical and organized, and the hierarchical route connection establishment is performed in parallel for fast connection.
  • the establishment provides the foundation.

Abstract

Procédé automatique de calcul de routage hiérarchisé dans un réseau optique commuté et d'établissement de connexion, comprenant les opérations suivantes:(a) configuration de chaque zone de routage du réseau optique et de son haut-parleur, établissement d'une relation topologique hiérarchisée permettant de calculer le routage au moyen de l'interaction entre les diverses hiérarchies et de diffuser au sein de la zone d'acheminement; (b) après réception par l'élément d'entrée du réseau de la demande d'établissement de connexion, envoi de cette demande au contrôleur de connexion d'entrée CC1 de la zone de routage RA1; (c) chaque zone de routage qui reçoit la demande de connexion cherche le routage dans la zone de routage commandée par le contrôleur de connexion d'entrée et entreprend d'établir une connexion s'il s'agit d'une zone de routage hiérarchique inférieure, achève la mise en oeuvre du canal à repère optique dans la zone de routage, puis passe soit à l'opération (e), soit à l'opération (d); (d) chaque contrôleur de connexion de noeud sur la voie d'acheminement envoie une demande de d'établissement de connexion de sous-réseau au contrôleur de connexion correspondant du haut-parleur de zone de la routage hiérarchique suivant, et revient à l'opération (c); (e) chaque zone de routage retourne la hiérarchie résultant de l'établissement de la connexion à l'élément d'entrée de réseau. Le procédé de l'invention permet une mise en oeuvre hiérarchique et consécutive du processus d'interaction de signalisation et d'établissement de connexions, ce qui offre l'avantage d'accélérer l'établissement de la connexion.
PCT/CN2005/001140 2005-07-28 2005-07-28 Procede automatique de calcul d'acheminement hierarchise dans un reseau optique commute et d'etablissement de connexion WO2007012223A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN2005800493120A CN101147348B (zh) 2005-07-28 2005-07-28 自动交换光网络层次路由计算和连接建立的方法
PCT/CN2005/001140 WO2007012223A1 (fr) 2005-07-28 2005-07-28 Procede automatique de calcul d'acheminement hierarchise dans un reseau optique commute et d'etablissement de connexion

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2005/001140 WO2007012223A1 (fr) 2005-07-28 2005-07-28 Procede automatique de calcul d'acheminement hierarchise dans un reseau optique commute et d'etablissement de connexion

Publications (1)

Publication Number Publication Date
WO2007012223A1 true WO2007012223A1 (fr) 2007-02-01

Family

ID=37682979

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2005/001140 WO2007012223A1 (fr) 2005-07-28 2005-07-28 Procede automatique de calcul d'acheminement hierarchise dans un reseau optique commute et d'etablissement de connexion

Country Status (2)

Country Link
CN (1) CN101147348B (fr)
WO (1) WO2007012223A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009056054A1 (fr) * 2007-10-26 2009-05-07 Huawei Technologies Co., Ltd. Procédé relatif à un élément de calcul de trajet permettant d'assurer le routage et assignation de longueur d'onde dans des réseaux optiques à commutation de longueur d'onde
WO2016061778A1 (fr) * 2014-10-23 2016-04-28 华为技术有限公司 Système d'interconnexion optique, nœud, dispositif de commande de réseau optique et procédé de transmission de données

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102571433B (zh) 2012-01-11 2014-07-30 华为技术有限公司 呈现网络路径的方法和装置
CN102811170B (zh) * 2012-07-25 2018-03-23 中兴通讯股份有限公司 一种实现域间路由洪泛的方法及代言节点
CN105282025A (zh) * 2014-07-11 2016-01-27 中兴通讯股份有限公司 一种确定端到端路由的方法及装置
CN110474788B (zh) * 2018-05-11 2022-04-15 中兴通讯股份有限公司 一种数据处理方法、终端及计算机可读存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003067835A1 (fr) * 2002-02-01 2003-08-14 Tellabs Operations, Inc. Procede et appareil relatifs a un reseau multicouche dans un reseau sonet/sdh (reseau optique synchrone a hierarchie numerique synchrone)
CN1529429A (zh) * 2003-09-30 2004-09-15 ���ͨ�ſƼ��ɷ����޹�˾ 确定光网络层次式路由的抽象拓扑链路属性的方法
CN1588920A (zh) * 2004-09-17 2005-03-02 清华大学 层次光网络中的并行层次光标记交换通道的建立方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2003067835A1 (fr) * 2002-02-01 2003-08-14 Tellabs Operations, Inc. Procede et appareil relatifs a un reseau multicouche dans un reseau sonet/sdh (reseau optique synchrone a hierarchie numerique synchrone)
CN1529429A (zh) * 2003-09-30 2004-09-15 ���ͨ�ſƼ��ɷ����޹�˾ 确定光网络层次式路由的抽象拓扑链路属性的方法
CN1588920A (zh) * 2004-09-17 2005-03-02 清华大学 层次光网络中的并行层次光标记交换通道的建立方法

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009056054A1 (fr) * 2007-10-26 2009-05-07 Huawei Technologies Co., Ltd. Procédé relatif à un élément de calcul de trajet permettant d'assurer le routage et assignation de longueur d'onde dans des réseaux optiques à commutation de longueur d'onde
US8059960B2 (en) 2007-10-26 2011-11-15 Futurewei Technologies, Inc. Path computation element method to support routing and wavelength assignment in wavelength switched optical networks
US8666246B2 (en) 2007-10-26 2014-03-04 Futurewei Technologies, Inc. Path computation element method to support routing and wavelength assignment in wavelength switched optical networks
WO2016061778A1 (fr) * 2014-10-23 2016-04-28 华为技术有限公司 Système d'interconnexion optique, nœud, dispositif de commande de réseau optique et procédé de transmission de données
CN105830368A (zh) * 2014-10-23 2016-08-03 华为技术有限公司 光互联系统、节点、光网络控制器和传输数据的方法
CN105830368B (zh) * 2014-10-23 2018-04-20 华为技术有限公司 光互联系统、节点、光网络控制器和传输数据的方法

Also Published As

Publication number Publication date
CN101147348A (zh) 2008-03-19
CN101147348B (zh) 2011-05-18

Similar Documents

Publication Publication Date Title
US7593340B2 (en) Method and system for multi-domain route computation
CN104426766B (zh) 跨多个网络层的动态端到端网络路径建立
US8737394B2 (en) Route computation method and system, and path computation element
US10516478B2 (en) Controller based path estimation and path provisioning using optical impairment data
US9769054B2 (en) Network topology discovery method and system
CN102959910B (zh) 通过通信信道将网元的分组转发配置的更改通知控制器
US11463313B2 (en) Topology-aware controller associations in software-defined networks
Farrel et al. GMPLS: architecture and applications
US6418139B1 (en) Mechanism to guarantee quality of service to real-time traffic on IP networks
US7570594B2 (en) Methods, systems, and computer program products for multi-path shortest-path-first computations and distance-based interface selection for VoIP traffic
US7995569B2 (en) Virtual routers for GMPLS networks
US9948696B2 (en) Cloud service control and management architecture expanded to interface the network stratum
US8948051B2 (en) System and method for efficient MVPN source redundancy with S-PMSI
JP2004537881A (ja) ネットワーク管理のための方法とシステム
WO2007012223A1 (fr) Procede automatique de calcul d'acheminement hierarchise dans un reseau optique commute et d'etablissement de connexion
WO2007062608A1 (fr) Procede pour la realisation d'acheminements separes reliant des domaines
WO2021004213A1 (fr) Procédé et appareil pour déterminer une étiquette de chemin de réseau de fusion, support de stockage et dispositif électronique
US9883264B2 (en) Systems and methods for multilayer peering
CN111226422B (zh) 在光域中建立路径的方法以及通信网络中的网络节点
WO2012159442A1 (fr) Procédé et dispositif de mise en œuvre d'une inondation de liaison interne
WO2015093478A1 (fr) Système de réseau, dispositif de commande, procédé de commande et programme associé
AU2003294254A1 (en) System and method for provisioning connections as a distributed digital cross-connect over a packet network
CN105791110A (zh) 一种建立流路径的方法及装置
WO2015093476A1 (fr) Système de réseau, dispositif de commande, procédé de commande et programme associé
KR101006804B1 (ko) Ａｔｍ 망관리시스템에서의 소프트-ｐｖｃ정보 관리방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 200580049312.0

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 05771657

Country of ref document: EP

Kind code of ref document: A1