WO2018153314A1 - Procédé destiné au positionnement de lsp avec erreur, pcc et pce - Google Patents

Procédé destiné au positionnement de lsp avec erreur, pcc et pce Download PDF

Info

Publication number
WO2018153314A1
WO2018153314A1 PCT/CN2018/076592 CN2018076592W WO2018153314A1 WO 2018153314 A1 WO2018153314 A1 WO 2018153314A1 CN 2018076592 W CN2018076592 W CN 2018076592W WO 2018153314 A1 WO2018153314 A1 WO 2018153314A1
Authority
WO
WIPO (PCT)
Prior art keywords
lsp
error
pcc
path
pce
Prior art date
Application number
PCT/CN2018/076592
Other languages
English (en)
Chinese (zh)
Inventor
祝沈财
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2018153314A1 publication Critical patent/WO2018153314A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery

Definitions

  • the present disclosure relates to the field of communications technologies, and in particular, to a method for locating an errored Label Switched Path (LSP), a Path Computation Client (PCC), and a Path Computation Element (PCE). ).
  • LSP errored Label Switched Path
  • PCC Path Computation Client
  • PCE Path Computation Element
  • the PCC is used to process all path calculation requests in one router, or to coordinate path calculation requests of multiple routing domains by PCEs of multiple domains.
  • the PCE is generally referred to as a path computation server.
  • the requester of the path calculation is called a path computation client.
  • the PCE receives the PCC request (PCE Request, PCReq)
  • the PCE calculates the existing network topology information. An end-to-end path that satisfies the constraints and policies, and returns the path calculation result to the PCC, thereby completing a path calculation.
  • RFC 5440 states that PCE is a new computing technology that deploys one or several devices with computing functions in a network domain, dedicated to computing paths.
  • the PCC resides in the module to calculate the path, and is used to send the calculation request message and the processing result.
  • the PCC and the PCE implement the interaction through the Path Computation Element Communication Protocol (PCEP).
  • PCEP Path Computation Element Communication Protocol
  • the peer is notified by a transmission path calculation unit communication protocol error (PCEP Error, PCErr) message.
  • PCEP Error PCErr
  • PCErr transmission path calculation unit communication protocol error
  • PCEP-ERROR PCEP Error object
  • the embodiments of the present disclosure provide a method for locating an LSP that has an error, and a PCC and a PCE, which can locate an erroneous LSP when an LSP error occurs.
  • An embodiment of the present disclosure provides a method for locating an erroneous label switched path LSP, where the method includes:
  • the path calculation client PCC receives at least one PCErr message; the PCErr message carries at least one identification information of the label switched path LSP that has an error;
  • the PCC determines an LSP that has an error according to the received PCErr message.
  • the PCErr message includes an additional type-length-valued TLV in at least one PCEP-ERROR, and the TLV carries identification information of an LSP that has an error.
  • the identifier information of the LSP that is in error includes: a path name of the LSP that has an error;
  • the PCC Determining, by the PCC, the LSP that is in error according to the received PCErr message, the PCC acquiring the error according to the TLV corresponding to the at least one LSP that has an error included in the received PCErr message.
  • the path name of the LSP, and the LSP with the error is determined according to the path name of the LSP where the error occurs.
  • the method further includes: deleting, by the PCC, the LSP that is in error.
  • the embodiment of the present disclosure further provides another method for locating an error-prone label switched path LSP, where the method includes:
  • the path calculation unit PCE receives the state information of the label switching path LSP reported by the path calculation client PCC;
  • the PCE After the PCE determines that the LSP is in error based on the status information of the LSP, sends at least one path calculation unit communication protocol error PCErr message to the PCC; the PCErr message carries at least one identifier of the LSP that is in error. .
  • the PCErr message includes an additional type-length-value TLV in the at least one path calculation unit communication protocol error object PCEP-ERROR, and the TLV carries identification information of an LSP with an error.
  • the method further includes: the PCE modifying the LSP with an error.
  • the embodiment of the present disclosure further provides a path calculation client PCC, where the PCC includes: a first receiving module and a determining module;
  • the first receiving module is configured to receive at least one path calculation unit communication protocol error PCErr message; the PCErr message carries at least one identification information of the label switching path LSP that has an error;
  • the determining module is configured to determine an LSP in which the error occurred based on the received PCErr message.
  • the PCErr message includes an additional type-length-value TLV in the at least one path calculation unit communication protocol error object PCEP-ERROR, and the TLV carries identification information of an LSP with an error.
  • the identifier information of the LSP that is in error includes: a path name of the LSP that has an error;
  • the determining module is configured to obtain, according to the received TLV corresponding to the at least one LSP that is in error, the path name of the LSP that is in error, according to the path name of the LSP that is in error , determining the LSP with the error.
  • the PCC further includes: a first processing module
  • the first processing module is configured to delete or modify the LSP that has an error after the determining module determines the LSP that has an error.
  • the embodiment of the present disclosure further provides a path calculation unit PCE, where the PCE includes: a second receiving module and a second processing module;
  • the second receiving module is configured to receive the path information of the label switching path LSP reported by the client PCC.
  • the second processing module is configured to: after determining that the LSP is faulty based on the status information of the LSP, send, to the PCC, at least one path calculation unit communication protocol error PCErr message; the PCErr message carries at least one LSP with an error Identification information.
  • the PCErr message includes an additional type-length-value TLV in the at least one path calculation unit communication protocol error object PCEP-ERROR, and the TLV carries identification information of an LSP with an error.
  • the second processing module is further configured to modify the LSP with an error after determining that the LSP has an error.
  • Embodiments of the present disclosure also provide a computer readable storage medium storing computer executable instructions that, when executed by a processor, implement any of the methods described above.
  • the embodiment of the present disclosure provides a method for locating an erroneous label switched path LSP, and a PCC and a PCE, where the PCC receives at least one PCErr message; the PCErr message carries at least one identifier of the LSP that has an error; The PCC determines an LSP that has an error according to the received PCErr message. In this way, the wrong LSP can be located when an LSP error occurs.
  • Figure 1 is a schematic diagram of a PCEP-ERROR object format
  • FIG. 2 is a flow chart of a first example of a method for locating an erroneous LSP according to an embodiment of the present disclosure
  • FIG. 3 is a schematic diagram of a path name TLV format in an embodiment of the present disclosure
  • FIG. 4 is a flow chart of a second example of a method for locating an erroneous LSP according to an embodiment of the present disclosure
  • FIG. 5 is a flowchart of a third example of a method for locating an LSP that has an error according to an embodiment of the present disclosure
  • FIG. 6 is a schematic structural diagram of a path calculation client PCC according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of a path calculation unit PCE according to an embodiment of the present disclosure.
  • FIG. 1 is a schematic diagram of a PCEP-ERROR object format.
  • the PCEP-ERROR object format may include: reserved bits Reserved, flagged Flags, error type Error-Type, error value Error-value, and additional TLV Optional TLVs.
  • Reserved reserves a bit that will not be used temporarily for expansion and other operations;
  • Flags is used to record some status flag bits;
  • Error-Type is used to indicate between PCC and PCE carried in the current PCEP-ERROR object.
  • the error type; Error-value further refers to the type of error between PCC and PCE as special error, general error, etc.;
  • Optional TLVs are used to carry additional error information.
  • PCE can be divided into stateless mode and stateful mode.
  • the Internet Engineering Task Force (IETF) standard protocol [RFC8231] describes stateful PCE as PCC and PCE.
  • the PCC sends a Path Computation LSP State Report (PCRpt) real-time synchronization LSP status to the PCE through the Label Switched Path (LSP) information.
  • LSP Label Switched Path
  • PCUpd Path Computation LSP Update Request
  • the error response of the Open message is implemented by carrying the OPEND object in the PCErr;
  • the error response of the PCReq message is implemented by carrying the RP object in the PCErr;
  • the error response of the PCUpd message is implemented by carrying the SRP object in the PCErr.
  • the existing PCErr message will not accurately indicate the specific LSP corresponding to the error.
  • the PCC cannot receive the error message for the LSP.
  • FIG. 2 is a flowchart of a first example of a method for locating an LSP that has an error according to an embodiment of the present disclosure. As shown in FIG. 2, the method includes:
  • Step 200 The PCE receives status information of the LSP reported by the PCC.
  • the PCE first uses the existing network topology information to create an end-to-end path for the PCC that satisfies the constraints and policies. For example, the PCE creates an SR tunnel for the PCC. The PCE sends a message to the PCC to establish an SR tunnel through the PCInitiate message. The PCE records the current LSP status and the path attribute is the SR type. The PCC receives the PCInitiate message and processes it, but the PCC creates the LSP for the PCE. It is understood to be an ordinary RSVP tunnel. After the PCC creates an RSVP tunnel, it reports the LSP status created by the current PCC through the PCRpt message and the label tunnel type is RSVP in the PCRpt message.
  • Step 201 After the PCE determines that the LSP is in error based on the status information of the LSP, send, to the PCC, at least one PCErr message; the PCErr message carries at least one identifier information of an LSP that has an error.
  • the PCE may further include: the PCE modifying the LSP with the error.
  • the PCErr message may include an additional type-length-value TLV in the at least one PCEP-ERROR object, where the TLV carries identification information of an LSP that has an error.
  • the identifier information of the LSP that has an error may include: a path name of the LSP where the error occurs.
  • the LSP information can be carried by the PCEP-ERROR object included in the PCErr message defined in the RFC5440 communication protocol.
  • the RFC5440 communication protocol defines that the PCEP-ERROR object can carry an additional TLV to further indicate the error information. However, the protocol does not further define how the PCEP-ERROR object in the PCErr message carries the LSP information when an LSP error occurs.
  • the Path-Name (Symbolic Path Name) TLV is defined in the protocol [RFC8231] to describe the unique name of the LSP, and the path name Path-Name is used to indicate the identification information of an LSP.
  • the Path-Name TLV carrying the error LSP in the PCEP-ERROR object may be used to indicate the LSP in which the error occurs, and the Path-Name is used as the identifier information of the LSP in which the error occurs.
  • the error object list ⁇ error-obj-list> is used in the PCErr message to carry the error information between the PCC and the PCE.
  • the ⁇ error-obj-list> in a PCErr message can carry the error information of multiple different LSPs at the same time, or carry different error information of the same LSP. Therefore, when an LSP error is indicated by an additional TLV carried by the PCEP-ERROR object, each PCEP-ERROR object in the ⁇ error-obj-list> carries the Path-Name TLV of the LSP, which is used to indicate an LSP error message.
  • the PCEP-ERROR object may be extended to carry additional TLV (Optional TLVs) information for information supplementation of error information, and the embodiment of the present disclosure defines PCEP.
  • the -ERROR object describes the specific LSP information corresponding to the erroneous LSP by carrying the Path-Name TLV shown in FIG.
  • the LSP information may be encoded into a Path-Name TLV format, including: Type Type, Length Length, and Path Name Path-Name;
  • the error type indicating the LSP that currently has an error;
  • Length is used to indicate the size of the current TLV, and the size of the Length is variable according to the TLV to be expressed, and the specific case;
  • Path-Name is used to identify an error. LSP.
  • the PCErr message carries the Path-Name of the LSP with the error.
  • the PCE modifies the LSP with the local error.
  • Step 202 After receiving the at least one PCErr message, the PCC determines an LSP that has an error according to the received PCErr message.
  • the identification information of the LSP in which the error occurs may include: the path name of the LSP in which the error occurred.
  • the PCC obtains the path name of the LSP in which the error occurred according to the TLV corresponding to the LSP that is in error, and the PCC determines the LSP that is in error according to the path name of the LSP where the error occurred.
  • the method may further include: deleting, by the PCC, the LSP that is in error.
  • the error type carried in the message is an LSP type error according to the error type of the message type included in the PCEP-ERROR object, and then the error LSP carried in the message can be correspondingly
  • the Path-Name TLV obtains the Path-Name of the LSP and locates the error LSP according to the obtained Path-Name.
  • the PCC discards the PCErr message; when the corresponding LSP is found according to the obtained Path-Name, the PCC deletes Or modify the local LSP. For example, when the LSP type (RSVP type) created by the PCC does not match the LSP type (SR type) created by the PCE, the PCC may delete the locally created LSP (that is, delete the RSVP tunnel) or according to the error information carried in the PCErr message. Modify the corresponding LSP status information.
  • LSP type RSVP type
  • SR type LSP type
  • the PCC cannot accurately locate the specific LSP corresponding to the error from the received PCErr message.
  • the PCCrr message cannot be processed by the PCC for the specific LSP.
  • it is not necessary to locate the LSP in the case of some LSP errors, it is not necessary to locate the LSP.
  • the LSP error types defined in the current protocol are common. For example, the Explicit Route Object (ERO) is missing. Generally, all LSPs are used. None, it is not necessary to locate the wrong LSP at this time.
  • ERO Explicit Route Object
  • the protocol [RFC8281] describes that the PCE can send a Path Computation LSP Initiate message to the PCC as needed to actively trigger the establishment of a tunnel. For example, if an application wants to create a new tunnel with a specific constraint, or if the existing tunnel bandwidth cannot meet the requirements, create a new tunnel for load sharing.
  • the draft [draft-ietf-pce-segment-routing-11] describes the path routing (SR) between the PCC and the PCE by extending the ERO information and the path setup type (PST) information. Type tunnel creation and status escalation.
  • the LSP error notified by the PCErr is specific to which LSP error.
  • the specific error information includes the LSP information in which the error occurred, and then the corresponding corrective action is taken.
  • the path calculation client PCC receives at least one path calculation unit communication protocol error PCErr message; the PCErr message carries at least one identification information of the label switching path LSP that has an error; the PCC according to the received The PCErr message determines the LSP where the error occurred.
  • the PCC interaction mode defined by the communication protocol can only know that an LSP type error occurs, but the PCC cannot locate which LSP is faulty, and it is impossible to further process the LSP with the error.
  • the PCC may modify or re-localize the local LSP error after the faulty LSP is located according to the identifier information of the LSP that is carried in the PCErr message.
  • FIG. 4 is a flowchart of a second example of a method for locating an LSP that has an error according to an embodiment of the present disclosure. As shown in FIG. 4, the method includes:
  • Step 400 The PCC receives at least one PCErr message; the PCErr message carries identifier information of at least one LSP that has an error.
  • the PCErr message may include an additional type-length-value TLV in the at least one PCEP-ERROR object, where the TLV carries identification information of an LSP that has an error.
  • the identifier information of the LSP that is in error may include: a path name of the LSP that has an error.
  • Step 401 The PCC determines an LSP that has an error according to the received PCErr message.
  • the PCC when the identifier information of the LSP that is in error includes the path name of the LSP in which the error occurs, the PCC obtains the path of the LSP in which the error occurs according to the TLV corresponding to the LSP that is in error of the LSP that is included in the received PCErr message. Name, the PCC determines the LSP with the error based on the path name of the LSP where the error occurred.
  • the method may further include: deleting, by the PCC, the LSP that is in error.
  • FIG. 5 is a flowchart of a third example of a method for locating an LSP that has an error according to an embodiment of the present disclosure. As shown in FIG. 5, the method includes:
  • Step 500 The PCE receives status information of the LSP reported by the PCC.
  • Step 501 After the PCE determines that the LSP is in error based on the LSP status information, the PCErr message is sent to the PCC.
  • the PCErr message carries the identifier information of the at least one LSP that is in error.
  • the PCErr message may include an additional type-length-value TLV in the at least one PCEP-ERROR object, where the TLV carries identification information of an LSP that has an error.
  • the PCE may further include: the PCE modifying the LSP with the error.
  • FIG. 6 is a schematic structural diagram of a path calculation client PCC according to an embodiment of the present disclosure.
  • the client includes: a first receiving module 600 and a determining module 601; wherein
  • the first receiving module 600 is configured to receive at least one PCErr message; the PCErr message carries identifier information of at least one LSP that has an error.
  • the determining module 601 is configured to determine an LSP in which an error occurs based on the received PCErr message.
  • the PCErr message may include an additional type-length-value TLV in the at least one PCEP-ERROR object, where the TLV carries identification information of an LSP that has an error.
  • the identifier information of the LSP that is in error may include: a path name of the LSP that has an error.
  • the determining module 601 is configured to obtain, according to the received TLV corresponding to the at least one LSP that is in error in the PCErr message, the path name of the LSP that is in error, and the PCC is faulty according to the The path name of the LSP to determine the LSP with the error.
  • the path calculation client may further include: a first processing module
  • the first processing module is configured to delete or modify the LSP that has an error after the determining module determines the LSP that has an error.
  • the first receiving module 600 and the determining module 601 can be configured by a central processing unit (CPU), a microprocessor (Micro Processor Unit, MPU), and a digital signal processor (Digital Signal Processor) located in the PCC. , DSP), or Field Programmable Gate Array (FPGA) implementation.
  • CPU central processing unit
  • MPU Micro Processor Unit
  • DSP Digital Signal Processor
  • FPGA Field Programmable Gate Array
  • FIG. 7 is a schematic structural diagram of a path calculation unit PCE according to an embodiment of the present disclosure. As shown in FIG. 7, the path calculation is performed.
  • the unit includes: a second receiving module 700 and a second processing module 701; wherein
  • the second receiving module 700 is configured to receive status information of the LSP reported by the PCC.
  • the second processing module 701 is configured to: after determining that the LSP is faulty based on the status information of the LSP, send at least one PCErr message to the PCC; the PCErr message carries identifier information of at least one LSP that has an error.
  • the PCErr message may include an additional type-length-value TLV in the at least one PCEP-ERROR object, where the TLV carries identification information of an LSP that has an error.
  • the second processing module 701 may be further configured to modify the LSP that has an error after determining that the LSP has an error.
  • the second receiving module 700 and the second processing module 701 can be implemented by a CPU, an MPU, a DSP, an FPGA, or the like located in the PCE.
  • Embodiments of the present disclosure also provide a computer readable storage medium storing computer executable instructions that, when executed by a processor, implement any of the methods described above.
  • computer storage medium includes volatile and nonvolatile, implemented in any method or technology for storing information, such as computer readable instructions, data structures, program modules or other data. Sex, removable and non-removable media.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridge, magnetic tape, magnetic disk storage or other magnetic storage device, or may Any other medium used to store the desired information and that can be accessed by the computer.
  • communication media typically includes computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and can include any information delivery media. .
  • the embodiment of the present disclosure provides a method for locating an erroneous label switched path LSP, and a PCC and a PCE, where the PCC receives at least one PCErr message; the PCErr message carries at least one identifier of the LSP that has an error; The PCC determines an LSP that has an error according to the received PCErr message. In this way, the wrong LSP can be located when an LSP error occurs.

Landscapes

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

Abstract

La présente invention concerne un procédé destiné au positionnement d'un trajet à commutation par étiquette (LSP) avec une erreur et le procédé comprend les étapes suivantes : un client de calcul de trajet (PCC) reçoit au moins une erreur de protocole de communication d'élément de calcul de chemin (PCErr); le message PCErr portant au moins une information d'identification concernant un trajet à commutation par étiquette (LSP) avec une erreur; et le PCC déterminant, en fonction du message PCErr reçu, le LSP avec une erreur. L'invention concerne en outre un PCC et un élément de calcul de trajet (PCE).
PCT/CN2018/076592 2017-02-22 2018-02-13 Procédé destiné au positionnement de lsp avec erreur, pcc et pce WO2018153314A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710097321.1 2017-02-22
CN201710097321.1A CN108462641A (zh) 2017-02-22 2017-02-22 一种对出现错误的lsp定位的方法及pcc和pce

Publications (1)

Publication Number Publication Date
WO2018153314A1 true WO2018153314A1 (fr) 2018-08-30

Family

ID=63220113

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/076592 WO2018153314A1 (fr) 2017-02-22 2018-02-13 Procédé destiné au positionnement de lsp avec erreur, pcc et pce

Country Status (2)

Country Link
CN (1) CN108462641A (fr)
WO (1) WO2018153314A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111431807B (zh) * 2019-01-09 2022-08-12 中国移动通信有限公司研究院 一种路径更新方法、装置、设备及存储介质

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101945035A (zh) * 2009-07-10 2011-01-12 中兴通讯股份有限公司 基于路径计算元的跨域路径恢复方法和装置
CN103155499A (zh) * 2010-10-15 2013-06-12 华为技术有限公司 用于计算点到多点标签交换路径的备份出口的系统和方法

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8131873B2 (en) * 2004-11-05 2012-03-06 Cisco Technology, Inc. Technique for selecting a path computation element
CN101459535A (zh) * 2007-04-12 2009-06-17 华为技术有限公司 进行业务恢复的装置和方法
CN102036129B (zh) * 2009-09-29 2013-06-05 中兴通讯股份有限公司 一种基于路径计算单元的路径保护方法及系统
WO2012109566A2 (fr) * 2011-02-11 2012-08-16 Huawei Technologies Co., Ltd. Système d'élément de calcul de trajet et procédé de routage et d'attribution de longueur d'onde dans réseau optique à commutation de longueur d'onde

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101945035A (zh) * 2009-07-10 2011-01-12 中兴通讯股份有限公司 基于路径计算元的跨域路径恢复方法和装置
CN103155499A (zh) * 2010-10-15 2013-06-12 华为技术有限公司 用于计算点到多点标签交换路径的备份出口的系统和方法

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
LE ROUX, J.L. ET AL.: "OSPF Protocol Extensions for Path Computation Element (PCE) Discovery", RFC 5088, 31 January 2008 (2008-01-31), XP015055160 *
VASSEUR, J.P . , ED. ET AL.: "Path Computation Element (PCE) Communication Protocol (PCEP", RFC 5440, 31 March 2009 (2009-03-31), XP055131169 *

Also Published As

Publication number Publication date
CN108462641A (zh) 2018-08-28

Similar Documents

Publication Publication Date Title
CN110870260B (zh) IPv6分段路由隧道建立方法
US11528220B2 (en) Method and device for creating bi-directional segment routing tunnel and storage medium
US9401858B2 (en) Loop avoidance during network convergence in switched networks
US10218592B2 (en) Method, device and system for performing bidirectional forwarding detection on aggregated link
US9843502B2 (en) Routing of point-to-multipoint services in a multi-domain network
US11588725B2 (en) Method and apparatus for path computation
KR101050681B1 (ko) 라벨 스위칭된 네트워크에서의 경로 계산 방법 및 장치
WO2021022944A1 (fr) Procédé de calcul d'itinéraire impliquant une contrainte de profondeur d'empilement, et dispositif
US10320682B2 (en) Maintaining information of TE link
US10666562B2 (en) Network path computation method, apparatus, and system
WO2020244550A1 (fr) Procédé de calcul de chemin, support d'informations et dispositif électronique
US10554543B1 (en) Migrating data traffic between label switched paths (LSPs) based on per-LSP protocol priority value
WO2018153314A1 (fr) Procédé destiné au positionnement de lsp avec erreur, pcc et pce
WO2016095699A1 (fr) Procédé et appareil pour acquérir un état d'un chemin à commutation d'étiquette
EP3276889B1 (fr) Procédé et appareil de commande de rapport d'état
WO2018219298A1 (fr) Procédé et dispositif de traitement de défaillance de calcul de trajet demandé par un client de calcul de trajet (pcc)
US20120230330A1 (en) Method for controlling area boundary, method and system for establishing connection in multilayer network
WO2018113793A1 (fr) Procédé et appareil de calcul de chemin, pcc, pce et système de calcul de chemin
WO2018086552A1 (fr) Procédé et dispositif d'ajustement d'une bande passante planifiée
WO2018113460A1 (fr) Procédé et appareil de commande lsp multicouche
CN115022240A (zh) 路径建立方法、装置、存储介质及电子装置
WO2018205887A1 (fr) Procédé et appareil de collecte de retard
CN107645447A (zh) 一种 lsp 创建方法和装置
WO2016061967A1 (fr) Procédé et dispositif de traitement de calcul de chemin

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: 18756579

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: 18756579

Country of ref document: EP

Kind code of ref document: A1