WO2022237562A1 - 一种路径计算方法、装置、存储介质及电子装置 - Google Patents

一种路径计算方法、装置、存储介质及电子装置 Download PDF

Info

Publication number
WO2022237562A1
WO2022237562A1 PCT/CN2022/089969 CN2022089969W WO2022237562A1 WO 2022237562 A1 WO2022237562 A1 WO 2022237562A1 CN 2022089969 W CN2022089969 W CN 2022089969W WO 2022237562 A1 WO2022237562 A1 WO 2022237562A1
Authority
WO
WIPO (PCT)
Prior art keywords
path
forwarding
controller
pce
delay
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2022/089969
Other languages
English (en)
French (fr)
Inventor
熊泉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 Corp filed Critical ZTE Corp
Priority to US18/275,647 priority Critical patent/US12237992B2/en
Priority to EP22806531.4A priority patent/EP4277424A4/en
Publication of WO2022237562A1 publication Critical patent/WO2022237562A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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/42—Centralised routing
    • 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/12—Shortest path evaluation
    • H04L45/121—Shortest path evaluation by minimising delays
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0852—Delays
    • 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/56—Routing software
    • H04L45/566—Routing instructions carried by the data packet, e.g. active networks
    • 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/34—Source routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/28—Flow control; Congestion control in relation to timing considerations

Definitions

  • Embodiments of the present disclosure relate to the communication field, and in particular, relate to a path calculation method, device, storage medium, and electronic device.
  • RFC4655 describes a structure based on Path Computation Element (PCE) for Multi-Protocol Label Switching (MPLS) and Generalized Multi-Protocol Label Switching, referred to as GMPLS) traffic engineering (Traffic Engineer, referred to as TE) label switched path (Label Switched Paths, referred to as LSP) path calculation.
  • PCE Path Computation Element
  • GMPLS Generalized Multi-Protocol Label Switching
  • TE Traffic Engineer
  • LSP Label Switched Paths
  • a PCE is an entity, component, application or network node that can calculate a network path or route based on a network graph and apply calculation constraints.
  • the Path Computation Client PCC for short
  • the PCE can request the PCE to perform path calculation.
  • PCE can actively initiate the path calculation and issue a path establishment request to the head node.
  • PCE can also be used as a controller (PCE-based Central Controller, referred to as PCECC) to actively issue path establishment, which carries centralized control objects (Central Control Instructions, referred to as CCI) to carry path establishment information to all nodes that the path passes through.
  • PCECC Central Controller
  • CCI Central Control Instructions
  • the IEEE 802.1 standard organization defines Time-Sensitive Networking (TSN for short), which mainly provides services such as low latency, low packet loss rate, and high reliability for L2 layer services.
  • TSN Time-Sensitive Networking
  • the IETF standard organization also proposed Deterministic Networking (Deterministic Networking, referred to as DetNet), in which RFC8655 defines the technical architecture of DetNet to provide deterministic services for Layer 2 bridges and Layer 3 routing networks.
  • DetNet Deterministic Networking
  • RFC8655 defines the technical architecture of DetNet to provide deterministic services for Layer 2 bridges and Layer 3 routing networks.
  • QoS Quality of Service
  • Embodiments of the present disclosure provide a path calculation method, device, storage medium, and electronic device to at least solve the problem in the related art that calculating network paths or routes based on network graphs cannot meet service requirements.
  • a path calculation method including:
  • the controller calculates the forwarding path and forwarding delay information according to the end-to-end delay requirement
  • the controller issues the forwarding path and the forwarding delay information to the device side.
  • the controller delivering the forwarding path and the forwarding delay information to the device side includes:
  • the controller sends the forwarding path and the forwarding delay information to the device side by using the path computation unit communication PCEP protocol, wherein the controller is a path computation unit PCE.
  • the method before the controller calculates the forwarding path and the forwarding delay according to the end-to-end delay requirement, the method further includes:
  • the controller obtains the end-to-end delay requirement
  • the controller receives a path computation request sent by the head node PCC.
  • the path computation request is a path computation request message PCReq based on the path computation element communication protocol PCEP protocol;
  • the extended T bit in the LSP-EXTENDED-FLAG TLV carrying the label switched path LSP object in the PCReq message of the path computation request is used to indicate the path computation request based on time scheduling;
  • the path calculation request PCReq message carries the extended TIME-SCHEDULING TLV in the Label Switched Path LSPA (Label Switched Paths Attribute) object to carry the constraint condition of the end-to-end delay, wherein the constraint condition includes a maximum End-to-end delay, minimum end-to-end delay and maximum end-to-end delay variation.
  • the constraint condition includes a maximum End-to-end delay, minimum end-to-end delay and maximum end-to-end delay variation.
  • the controller delivering the forwarding path and the forwarding delay information to the device side includes:
  • the device side is a head node PCC, and the controller sends the forwarding path and the forwarding delay information to the head node PCC;
  • the device side is a node passed by the forwarding path, and the controller delivers the forwarding path and the forwarding delay information to the node passed by the forwarding path.
  • the forwarding path and the forwarding delay information are carried by extending the delay field in the ERO object;
  • the forwarding path and the forwarding delay are carried by extending the delay field in the source routing display path object (Segement routing Explicit Routing Object, referred to as SR-ERO) object information;
  • the delay field extended in the SRv6-ERO object carries the forwarding path and the forwarding delay information.
  • the forwarding path and the forwarding delay information are carried by the newly added time table type length value TIME-SCHEDULING TLV (Type Length Value) in the centralized control object CCI object .
  • the method before the controller calculates the forwarding path and the forwarding delay information according to the end-to-end delay requirement, the method further includes:
  • the controller serving as the PCE negotiates with the device side serving as the PCC on a path calculation capability based on time scheduling.
  • the bit T of the OPEN object extension of the OPEN message in the PCEP protocol indicates whether there is time-based scheduling path computation capability
  • the bit T extended in SR-PCE-CAPABILITY Sub-TLV indicates whether it has the path calculation capability based on time scheduling
  • the bit T extended in SRv6-PCE-CAPABILITY Sub-TLV indicates whether it has the path calculation capability based on time scheduling.
  • the extended bit T in the PCECC CAPABILITY sub-TLV of the OPEN message indicates whether to have the path calculation capability based on time scheduling.
  • a path calculation method including:
  • the device side receives forwarding path and forwarding delay information delivered by the controller, wherein the forwarding path and the forwarding delay information are calculated by the controller according to end-to-end delay requirements.
  • the method before the device side receives the forwarding path and forwarding delay information issued by the controller, the method further includes:
  • the device side sends a path computation request to the controller by using the path computation element communication PCEP protocol, wherein the controller is a path computation element PCE.
  • the path computation request is a path computation request message PCReq based on the path computation element communication protocol PCEP protocol;
  • the extended T bit in the LSP-EXTENDED-FLAG TLV carrying the label switched path LSP object in the PCReq message of the path computation request is used to indicate the path computation request based on time scheduling;
  • the path calculation request PCReq message carries the extended TIME-SCHEDULING TLV in the LSPA object to carry the constraints of the end-to-end delay, wherein the constraints include the maximum end-to-end delay, the minimum end-to-end delay, and the minimum end-to-end delay. End delay and maximum end-to-end delay variation.
  • the device side in PCC-initiate mode or PCE-initiate mode, is the head node PCC;
  • the device side is a node through which the forwarding path passes.
  • the forwarding path and the forwarding delay information are carried through the extended delay field in the ERO object;
  • the forwarding path and the forwarding delay information are carried through the extended delay field in the SRv6-ERO object.
  • the forwarding path and the forwarding delay information are carried through the newly added TIME-SCHEDULING TLV in the centralized control object CCI object.
  • the method before the device side receives the forwarding path and the forwarding delay issued by the controller, the method further includes:
  • the device side serving as the PCC negotiates with the controller serving as the PCE on a path calculation capability based on time scheduling.
  • the bit T of the OPEN object extension of the OPEN message in the PCEP protocol indicates whether there is time-based scheduling path computation capability
  • the bit T of the SR-PCE-CAPABILITY Sub-TLV extension in the PCEP protocol indicates whether it has the path calculation capability based on time scheduling;
  • the bit T of the SRv6-PCE-CAPABILITY Sub-TLV extension in the PCEP protocol indicates whether it has the path calculation capability based on time scheduling.
  • the extended bit T in the PCECC CAPABILITY sub-TLV of the OPEN message indicates whether to have the path calculation capability based on time scheduling.
  • a path calculation device applied to a controller including:
  • a computing module configured to calculate forwarding paths and forwarding delay information according to end-to-end delay requirements
  • the sending module is configured to send the forwarding path and the forwarding delay information to the device side.
  • the sending module is also set to
  • the device also includes:
  • An acquisition module configured to enable the controller to acquire the end-to-end delay requirement in PCE-initiate mode or PCECC mode;
  • the request receiving module is configured to receive the path computation request sent by the head node PCC under the path computation client PCC-initiate mode.
  • the path computation request is a path computation request message PCReq based on the path computation element communication protocol PCEP protocol;
  • the extended T bit in the LSP-EXTENDED-FLAG TLV carrying the label switched path LSP object in the PCReq message of the path computation request is used to indicate the path computation request based on time scheduling;
  • the path calculation request PCReq message carries the extended TIME-SCHEDULING TLV in the LSPA object to carry the constraints of the end-to-end delay, wherein the constraints include the maximum end-to-end delay, the minimum end-to-end delay, and the minimum end-to-end delay. End delay and maximum end-to-end delay variation.
  • the delivery module is further configured to deliver the forwarding path and the forwarding delay information in PCC-initiate mode or PCE-initiate mode, where the device side is the head node PCC to the first node PCC;
  • the device side is a node passed by the forwarding path, and delivers the forwarding path and the forwarding delay information to the node passed by the forwarding path.
  • the forwarding path and the forwarding delay information are carried by extending the delay field in the ERO object;
  • the forwarding path and the forwarding delay information are carried through the extended delay field in the SRv6-ERO object.
  • the forwarding path and the forwarding delay information are carried through the newly added TIME-SCHEDULING TLV in the centralized control object CCI object.
  • the device also includes:
  • the first negotiating module is configured to perform time-scheduled-based path calculation capability negotiation with the device side as the PCC as the PCE.
  • the bit T of the OPEN object extension of the OPEN message in the PCEP protocol indicates whether there is time-based scheduling path computation capability
  • the bit T extended in SR-PCE-CAPABILITY Sub-TLV indicates whether it has the path calculation capability based on time scheduling
  • the bit T extended in SRv6-PCE-CAPABILITY Sub-TLV indicates whether it has the path calculation capability based on time scheduling.
  • the extended bit T in the PCECC CAPABILITY sub-TLV of the OPEN message indicates whether to have the path calculation capability based on time scheduling.
  • a path calculation apparatus which is applied to the device side, including:
  • the receiving module is configured to receive the forwarding path and the forwarding delay information issued by the controller, wherein the forwarding path and the forwarding delay information are calculated by the controller according to the end-to-end delay requirement.
  • the device also includes:
  • the sending module is configured to send a path computation request to the controller by using the path computation element communication PCEP protocol, wherein the controller is a path computation element PCE.
  • the path computation request is a path computation request message PCReq based on the path computation element communication protocol PCEP protocol;
  • the extended T bit in the LSP-EXTENDED-FLAG TLV carrying the label switched path LSP object in the PCReq message of the path computation request is used to indicate the path computation request based on time scheduling;
  • the path calculation request PCReq message carries the extended TIME-SCHEDULING TLV in the LSPA object to carry the constraints of the end-to-end delay, wherein the constraints include the maximum end-to-end delay, the minimum end-to-end delay, and the minimum end-to-end delay. End delay and maximum end-to-end delay variation.
  • the device side in PCC-initiate mode or PCE-initiate mode, is the head node PCC;
  • the device side is a node through which the forwarding path passes.
  • the forwarding path and the forwarding delay information are carried through the extended delay field in the ERO object;
  • the forwarding path and the forwarding delay information are carried through the extended delay field in the SRv6-ERO object.
  • the forwarding path and the forwarding delay information are carried through the newly added TIME-SCHEDULING TLV in the centralized control object CCI object.
  • the device also includes:
  • the second negotiating module is configured to perform time-scheduled-based path calculation capability negotiation with the controller as the PCE as the PCC.
  • the bit T of the OPEN object extension of the OPEN message in the PCEP protocol indicates whether there is time-based scheduling path computation capability
  • the bit T of the SR-PCE-CAPABILITY Sub-TLV extension in the PCEP protocol indicates whether it has the path calculation capability based on time scheduling;
  • the bit T of the SRv6-PCE-CAPABILITY Sub-TLV extension in the PCEP protocol indicates whether it has the path calculation capability based on time scheduling.
  • the extended bit T in the PCECC CAPABILITY sub-TLV of the OPEN message indicates whether to have the path calculation capability based on time scheduling.
  • a computer-readable storage medium where a computer program is stored in the storage medium, wherein the computer program is set to execute any one of the above method embodiments when running in the steps.
  • an electronic device including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to perform any of the above Steps in the method examples.
  • the controller calculates the forwarding path and forwarding delay information according to the end-to-end delay requirement; the controller sends the forwarding path and the forwarding delay information to the device side, which can solve the The network diagram to calculate the network path or route cannot meet the business needs, so that the determined target path can meet the business needs.
  • FIG. 1 is a block diagram of a hardware structure of a mobile terminal of a path calculation method according to an embodiment of the present disclosure
  • FIG. 2 is a first flowchart of a path calculation method according to an embodiment of the present disclosure
  • FIG. 3 is a second flowchart of a path calculation method according to an embodiment of the present disclosure.
  • Fig. 4 is a schematic diagram of the extended format of T bits in the LSP-EXTENDED-FLAG TLV according to the present embodiment
  • Fig. 5 is a schematic diagram of the extended format of the TIME-SCHEDULING TLV in LSPA according to the present embodiment
  • FIG. 6 is a schematic diagram of the extended format of T bits in the OPEN object according to the present embodiment.
  • Fig. 7 is a schematic diagram of the extended format of the time scheduling information in the IPv4ERO object according to the present embodiment
  • Fig. 8 is a schematic diagram of the extended format of the time scheduling information in the IPv6 ERO object according to the present embodiment
  • Fig. 9 is a schematic diagram of the extended format of T bits in SR-PCE-CAPABILITY Sub-TLV according to this embodiment.
  • FIG. 10 is a schematic diagram of an extended format of time scheduling information in an SR-ERO object according to this embodiment.
  • FIG. 11 is a schematic diagram of the extended format of T bits in SRv6-PCE-CAPABILITY Sub-TLV according to this embodiment.
  • FIG. 12 is a schematic diagram of the extended format of T bits in SRv6-PCE-CAPABILITY Sub-TLV according to this embodiment
  • Fig. 13 is a schematic diagram of the extended format of T bits in PCECC CAPABILITY sub-TLV according to the present embodiment
  • FIG. 14 is a schematic diagram of the TIME-SCHEDULING TLV format according to the present embodiment.
  • Fig. 15 is a structural diagram of the DetNet network based on time scheduling path calculation according to the present embodiment
  • FIG. 16 is a first block diagram of a path calculation device according to this embodiment.
  • FIG. 17 is a second block diagram of the path calculation device according to this embodiment.
  • FIG. 1 is a block diagram of the hardware structure of the mobile terminal according to the path calculation method of the embodiment of the present disclosure.
  • the mobile terminal may include one or more (only one is shown in FIG. 1 ) processor 102 (processor 102 may include but not limited to processing devices such as microprocessor MCU or programmable logic device FPGA, etc.) and memory 104 for storing data, wherein the above-mentioned mobile terminal may also include a communication function Transmission device 106 and input and output device 108 .
  • processor 102 may include but not limited to processing devices such as microprocessor MCU or programmable logic device FPGA, etc.
  • memory 104 for storing data
  • the above-mentioned mobile terminal may also include a communication function Transmission device 106 and input and output device 108 .
  • the structure shown in FIG. 1 is only for illustration, and it does not limit the structure of the above mobile terminal.
  • the mobile terminal may also include more or fewer components than those shown in FIG. 1 , or have a different configuration from that
  • the memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as computer programs corresponding to the path calculation method in the embodiments of the present disclosure, and the processor 102 executes various This kind of functional application and service chain address pool slicing processing is to realize the above-mentioned method.
  • the memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory.
  • the memory 104 may further include a memory that is remotely located relative to the processor 102, and these remote memories may be connected to the mobile terminal through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • the transmission device 106 is used to receive or transmit data via a network.
  • the specific example of the above network may include a wireless network provided by the communication provider of the mobile terminal.
  • the transmission device 106 includes a network interface controller (NIC for short), which can be connected to other network devices through a base station so as to communicate with the Internet.
  • the transmission device 106 may be a radio frequency (Radio Frequency, referred to as RF) module, which is used to communicate with the Internet in a wireless manner.
  • RF Radio Frequency
  • FIG. 2 is a flow chart of the path calculation method according to an embodiment of the present disclosure. As shown in FIG. 2 , the process includes the following steps :
  • Step S202 the controller calculates the forwarding path and forwarding delay information according to the end-to-end delay requirement
  • Step S204 the controller delivers the forwarding path and the forwarding delay information to the device side.
  • the path computation unit communication under the PCEP protocol may be used to
  • the controller is a path computation unit PCE.
  • the controller calculates the forwarding path and forwarding delay information according to the end-to-end delay requirement; the controller sends the forwarding path and the forwarding delay information to the device side, which can solve the problem of related technologies
  • the calculation of network paths or routes based on network graphs cannot meet business needs, so that the determined target path can meet business needs.
  • the controller before the controller calculates the forwarding path and the forwarding delay according to the end-to-end delay requirement, in PCE-initiate mode or PCECC mode, the controller acquires the End-to-end delay requirements; in the PCC-initiate mode of the path calculation client, the controller receives the path calculation request sent by the head node PCC.
  • the path computation request is a path computation request message PCReq message based on the path computation element communication protocol PCEP protocol; the path computation request PCReq message carries the LSP-EXTENDED- The extended T bit in the FLAG TLV is used to indicate the path calculation request based on time scheduling; the path calculation request PCReq message carries the extended TIME-SCHEDULING TLV in the LSPA object to carry the constraints of the end-to-end delay, Wherein, the constraints include maximum end-to-end delay, minimum end-to-end delay and maximum end-to-end delay variation.
  • step S204 may specifically include:
  • the device side is a head node PCC, and the controller sends the forwarding path and the forwarding delay information to the head node PCC;
  • the device side is the node through which the forwarding path passes, and the controller sends the forwarding path and the forwarding delay information to the node through which the forwarding path passes.
  • the forwarding path and the forwarding delay information are carried by extending the delay field in the ERO object; if for an SR network, carry the forwarding path and the forwarding delay information by extending the delay field in the SR-ERO object; for an SRv6 network, carry the forwarding path and the forwarding delay information by extending the delay field in the SRv6-ERO object The forwarding delay information described above.
  • the forwarding path and the forwarding delay information are carried through the newly added TIME-SCHEDULING TLV in the centralized control object CCI object.
  • the controller before the controller calculates the forwarding path and the forwarding delay information according to the end-to-end delay requirement, the controller serving as the PCE and the controller serving as the PCC On the device side, the negotiation of the path calculation capability based on time scheduling is performed.
  • the bit T of the OPEN object extension of the OPEN message in the PCEP protocol indicates whether there is time-based scheduling path computing capability; if it is an SR network, use the bit T extended in SR-PCE-CAPABILITY Sub-TLV to indicate whether it has the path computing capability based on time scheduling; if it is an SRv6 network, pass The extended bit T indicates whether to have the path calculation capability based on time scheduling.
  • the extended bit T in the PCECC CAPABILITY sub-TLV of the OPEN message indicates whether it has the path calculation capability based on time scheduling.
  • FIG. 3 is a flowchart 2 of the method for calculating a path according to an embodiment of the present disclosure. As shown in FIG. 3 , the process includes the following steps:
  • Step S302 the device side receives forwarding path and forwarding delay information delivered by the controller, wherein the forwarding path and the forwarding delay information are calculated by the controller according to the end-to-end delay requirement.
  • step S302 specifically, the forwarding path and forwarding delay information sent by the controller may be received through the PCEP protocol.
  • step S302 the problem in the related art that calculating the network path or route based on the network graph cannot meet the service requirement can be solved, so that the determined target path can meet the service requirement.
  • the device side before the device side receives the forwarding path and forwarding delay information delivered by the controller, the device side sends a path calculation request to the controller by using the path calculation unit communication PCEP protocol, Wherein, the controller is a path computation unit PCE.
  • the path computation request is a path computation request message PCReq message based on the path computation unit communication protocol PCEP protocol; the path computation request PCReq message carries the LSP-EXTENDED-FLAG TLV of the label switched path LSP object
  • the extended T bit is used to indicate the path calculation request based on time scheduling; the path calculation request PCReq message carries the extended TIME-SCHEDULING TLV in the LSPA object to carry the constraints of the end-to-end delay, where the The constraints mentioned above include maximum end-to-end delay, minimum end-to-end delay and maximum end-to-end delay variation.
  • the device side in the PCC-initiate mode or the PCE-initiate mode, the device side is the head node PCC; in the PCECC mode, the device side is the node through which the forwarding path passes.
  • the forwarding path and the forwarding delay information are carried through the extended delay field in the ERO object; If it is an SR network, carry the forwarding path and the forwarding delay information through the extended delay field in the SR-ERO object; if it is an SRv6 network, carry the forwarding path through the extended delay field in the SRv6-ERO object with the forwarding delay information.
  • the forwarding path and the forwarding delay information are carried through the newly added TIME-SCHEDULING TLV in the centralized control object CCI object.
  • the device side before the device side receives the forwarding path and the forwarding delay issued by the controller, the device side serving as the PCC and the controller serving as the PCE Negotiate the path calculation capability based on time scheduling.
  • the bit T of the OPEN object extension of the OPEN message in the PCEP protocol indicates whether there is time-based scheduling path computing capability; if it is an SR network, the bit T in the SR-PCE-CAPABILITY Sub-TLV extension in the PCEP protocol indicates whether it has the path computing capability based on time scheduling; if it is an SRv6 network, through the PCEP protocol The bit T of the SRv6-PCE-CAPABILITY Sub-TLV extension in the protocol indicates whether it has the path calculation capability based on time scheduling.
  • the extended bit T in the PCECC CAPABILITY sub-TLV of the OPEN message indicates whether it has the path calculation capability based on time scheduling.
  • PCE and the extended Path Computation Element Protocol can be used to implement path calculation based on time scheduling.
  • the present invention proposes a calculation method based on time queue scheduling, which realizes path calculation information interaction between equipment and controllers (such as PCE) by extending the PCEP protocol.
  • the method is applicable to IP/MPLS, SR and SRv6 networks.
  • the first is PCC-initiate mode.
  • the head node can act as a PCC to actively initiate a time-scheduled path calculation request to the PCE or controller, and the PCE or controller sends a response message to the head node after calculating the path. .
  • the second is PCE-initiate mode or PCECC mode.
  • the PCE or controller can also actively calculate the path based on time scheduling. If it is PCE-initiate mode, the PCE or controller sends the path result to the head node. If it is PCECC mode, The PCE or the controller delivers the path result to all nodes that the path passes through.
  • the first node sends a path calculation request to the PCE or controller, requesting to calculate a path that satisfies the end-to-end delay, where:
  • Figure 4 is a schematic diagram of the extended format of T bits in the LSP-EXTENDED-FLAG TLV according to the present embodiment.
  • the path calculation request message PCReq of the extended PCEP protocol extends the LSP-EXTENDED-FLAG in the LSP object , extending a new flag bit, which is used to indicate the path calculation request based on time scheduling.
  • FIG. 5 is a schematic diagram of the extended format of the TIME-SCHEDULING TLV in LSPA according to the present embodiment. As shown in Figure 5, the time-based constraints in the extended PCEP protocol are extended to a new TLV in the LSPA object for carrying Path calculation constraints based on time scheduling, end-to-end maximum, minimum delay and delay jitter, etc.
  • the PCE calculates the path result and the delay of each node according to the delay information, including IP/MPLS, SR, SRv6 network and other path calculation results, and sends them to the PCC.
  • the delay information including IP/MPLS, SR, SRv6 network and other path calculation results
  • FIG. 6 In the IP/MPLS network, the time-scheduling-based path calculation capability negotiation in the extended PCEP protocol is shown in FIG. 6, Fig. 7 is a schematic diagram of the extended format of the time scheduling information in the IPv4ERO object according to the present embodiment, and Fig. 8 is a schematic diagram of the extended format of the time scheduling information in the IPv6 ERO object according to the present embodiment, in the extended PCEP protocol Figure 7 and Figure 8 show the distribution of path calculation results.
  • FIG. 9 is a schematic diagram of the extended format of T bits in the SR-PCE-CAPABILITY Sub-TLV according to this embodiment, and the OPEN object of the extended OPEN message
  • the T bit ratio is shown in Figure 9
  • Figure 10 is a schematic diagram of the extended format of the time scheduling information in the SR-ERO object according to this embodiment, and the delivery of the path calculation result based on SR-TE in the extended PCEP protocol is shown in Figure 10 .
  • Figure 11 is a schematic diagram of the extended format of T bits in SRv6-PCE-CAPABILITY Sub-TLV according to this embodiment
  • Figure 12 is a schematic diagram according to this embodiment Schematic diagram of the extended format of T bits in SRv6-PCE-CAPABILITY Sub-TLV, the OPEN object of the extended OPEN message carrying T bits is shown in Figure 11, and the path calculation results based on SRv6 in the extended PCEP protocol are delivered as shown in Figure 12 Show.
  • the PCE or the controller can also actively calculate the path based on time scheduling, and send the path result to the head node.
  • the path result extension is the same as the PCC-initiate mode, and the PCEP path result extension of IP/MPLS, SR, and SRv6 networks is shown in Figures 7, 8, 10, and 12.
  • the PCE or the controller can also actively calculate the path based on time scheduling, and deliver the path result to all nodes that the path passes through.
  • This extension is applicable to IP/MPLS, SR, SRv6 networks.
  • Fig. 13 is a schematic diagram of the extended format of T bits in PCECC CAPABILITY sub-TLV according to this embodiment, as shown in Fig. 13 , in PCECC mode, through the PCECC CAPABILITY sub-TLV in the OPEN message of the PCEP protocol
  • the extended bit T indicates whether to have the path calculation capability based on time scheduling.
  • FIG 14 is a schematic diagram of the TIME-SCHEDULING TLV format according to this embodiment, as shown in Figure 14, in the PCECC mode, the target is carried by the newly added TIME-SCHEDULING TLV in the PCECC centralized control object CCI object The path and the delay information of each node.
  • the information related to time-based scheduling in the path result is not limited to a specific time delay, and may also include information such as time delay, queue, and scheduling.
  • the head node applies to the controller or PCE to calculate the path satisfying the end-to-end delay, and the request message carries relevant constraints such as the delay queue;
  • the controller or PCE calculates the path result and the delay of each node according to the delay information, including IP/MPLS, SR, SRv6 network and other path calculation result extensions, and sends a response message to the PCC.
  • the delay information including IP/MPLS, SR, SRv6 network and other path calculation result extensions
  • the PCE or the controller actively calculates the time-based scheduling path that satisfies the end-to-end delay
  • the PCE or the controller sends the path result based on the time scheduling information to the device side.
  • Fig. 15 is the structural diagram of the DetNet network based on time scheduling path calculation according to the present embodiment, as shown in Fig. 15, in the DetNet IP/MPLS network, the controller (such as PCE) interacts with the DetNet network through the PCEP protocol, and needs to calculate A path that satisfies the end-to-end delay, and the path result includes path forwarding and time scheduling information.
  • the present invention proposes a calculation method based on time queue scheduling. By extending the PCEP protocol, the path calculation information interaction between the device and the controller (such as PCE) is realized.
  • PCC-initiate mode The specific process is as follows:
  • the head node acting as the PCC, applies to the controller or PCE to calculate a path that satisfies the end-to-end delay, where the T bit in the LSP_EXTENDED_LSP in the request message is set to 1, and the TIME-SCHEDULING TLV in the LSPA object carries relevant constraints such as the delay queue;
  • the controller or PCE calculates the path forwarding result and the time delay information of each node according to the delay information, carries them in the ERO object, and sends a response message to the PCC.
  • the controller (such as PCE) interacts with the DetNet network through the PCEP protocol, and needs to calculate the path that meets the end-to-end delay, and the path result includes path forwarding and time scheduling information.
  • the path calculation information interaction between the device and the controller (such as PCE) is realized.
  • the head node applies to the controller or PCE to calculate a path that satisfies the end-to-end delay, where the T bit in the LSP_EXTENDED_LSP in the request message is set to 1, and the TIME-SCHEDULING TLV in the LSPA object carries relevant constraints such as the delay queue;
  • the controller or PCE calculates the path forwarding result and the time delay information of each node according to the delay information, carries them in the SR-ERO object, and sends a response message to the PCC.
  • the controller (such as PCE) interacts with the DetNet network through the PCEP protocol, and needs to calculate the path that meets the end-to-end delay, and the path result includes path forwarding and time scheduling information.
  • the path calculation information interaction between the device and the controller is realized by extending the PCEP protocol.
  • the head node applies to the controller or PCE to calculate a path that satisfies the end-to-end delay, where the T bit in the LSP_EXTENDED_LSP in the request message is set to 1, and the TIME-SCHEDULING TLV in the LSPA object carries relevant constraints such as the delay queue;
  • the controller or PCE calculates the path forwarding result and the time delay information of each node according to the delay information, carries them in the SRv6-ERO object, and sends a response message to the PCC.
  • the exchange of path calculation information between the device and the controller (such as PCE) is realized.
  • This method is applicable to IP/MPLS, SR and SRv6 networks.
  • the device side applies to the controller (such as PCE) for path calculation based on time scheduling.
  • the PCE calculates the forwarding path and the delay of each node according to the delay information.
  • it issues the path forwarding and Scheduling information.
  • FIG. 16 is a block diagram 1 of the path calculation device according to this embodiment. As shown in FIG. 16 , it includes:
  • the calculation module 162 is configured to calculate forwarding paths and forwarding delay information according to end-to-end delay requirements
  • the sending module 164 is configured to send the forwarding path and the forwarding delay information to the device side.
  • the sending module 164 is further configured to
  • the device also includes:
  • An acquisition module configured to enable the controller to acquire the end-to-end delay requirement in PCE-initiate mode or PCECC mode;
  • the request receiving module is configured to receive the path computation request sent by the head node PCC under the path computation client PCC-initiate mode.
  • the path computation request is a path computation request message PCReq message based on the path computation element communication protocol PCEP protocol;
  • the extended T bit in the LSP-EXTENDED-FLAG TLV carrying the label switched path LSP object in the PCReq message of the path computation request is used to indicate the path computation request based on time scheduling;
  • the path calculation request PCReq message carries the extended TIME-SCHEDULING TLV in the LSPA object to carry the constraints of the end-to-end delay, wherein the constraints include the maximum end-to-end delay, the minimum end-to-end delay, and the minimum end-to-end delay. End delay and maximum end-to-end delay variation.
  • the sending module 164 is further configured to send the forwarding path and the forwarding delay in PCC-initiate mode or PCE-initiate mode, the device side being the first node PCC information to the first node PCC;
  • the device side is a node passed by the forwarding path, and delivers the forwarding path and the forwarding delay information to the node passed by the forwarding path.
  • the forwarding path and the forwarding delay are carried by extending the delay field in the ERO object information
  • the forwarding path and the forwarding delay information are carried through the extended delay field in the SRv6-ERO object.
  • the forwarding path and the forwarding delay information are carried through the newly added TIME-SCHEDULING TLV in the centralized control object CCI object.
  • the device also includes:
  • the first negotiating module is configured to perform time-scheduled-based path calculation capability negotiation with the device side as the PCC as the PCE.
  • the bit T of the OPEN object extension of the OPEN message in the PCEP protocol indicates whether there is Path calculation capability based on time scheduling;
  • the bit T extended in SR-PCE-CAPABILITY Sub-TLV indicates whether it has the path calculation capability based on time scheduling
  • the bit T extended in SRv6-PCE-CAPABILITY Sub-TLV indicates whether it has the path calculation capability based on time scheduling.
  • the extended bit T in the PCECC CAPABILITY sub-TLV of the OPEN message indicates whether to have the path calculation capability based on time scheduling.
  • FIG. 17 is a block diagram 2 of the path calculation device according to this embodiment. As shown in FIG. 17 , it includes:
  • the receiving module 172 is configured to receive the forwarding path and the forwarding delay information issued by the controller, wherein the forwarding path and the forwarding delay information are calculated by the controller according to the end-to-end delay requirement .
  • the device also includes:
  • the sending module is configured to send a path computation request to the controller by using the path computation element communication PCEP protocol, wherein the controller is a path computation element PCE.
  • the path computation request is a path computation request message PCReq message based on the path computation element communication protocol PCEP protocol;
  • the extended T bit in the LSP-EXTENDED-FLAG TLV carrying the label switched path LSP object in the PCReq message of the path computation request is used to indicate the path computation request based on time scheduling;
  • the path calculation request PCReq message carries the extended TIME-SCHEDULING TLV in the LSPA object to carry the constraints of the end-to-end delay, wherein the constraints include the maximum end-to-end delay, the minimum end-to-end delay, and the minimum end-to-end delay. End delay and maximum end-to-end delay variation.
  • the device side in PCC-initiate mode or PCE-initiate mode, is the head node PCC;
  • the device side is a node through which the forwarding path passes.
  • the delay field extended in the ERO object carries the forwarding path and the forwarding time extension information
  • the forwarding path and the forwarding delay information are carried through the extended delay field in the SRv6-ERO object.
  • the forwarding path and the forwarding delay information are carried through the newly added TIME-SCHEDULING TLV in the centralized control object CCI object.
  • the device also includes:
  • the second negotiating module is configured to perform time-scheduled-based path calculation capability negotiation with the controller as the PCE as the PCC.
  • the bit T of the OPEN object extension of the OPEN message in the PCEP protocol indicates whether there is Path calculation capability based on time scheduling;
  • the bit T of the SR-PCE-CAPABILITY Sub-TLV extension in the PCEP protocol indicates whether it has the path calculation capability based on time scheduling;
  • the extended bit T of SRv6-PCE-CAPABILITY Sub-TLV in the PCEP protocol indicates whether it has the path calculation capability based on time scheduling.
  • the extended bit T in the PCECC CAPABILITY sub-TLV of the OPEN message indicates whether to have the path calculation capability based on time scheduling.
  • Embodiments of the present disclosure also provide a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps in any one of the above method embodiments when running.
  • the above-mentioned computer-readable storage medium may include but not limited to: U disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM) , mobile hard disk, magnetic disk or optical disk and other media that can store computer programs.
  • ROM read-only memory
  • RAM random access memory
  • mobile hard disk magnetic disk or optical disk and other media that can store computer programs.
  • Embodiments of the present disclosure also provide an electronic device, including a memory and a processor, where a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.
  • the electronic device may further include a transmission device and an input and output device, wherein the transmission device is connected to the processor, and the input and output device is connected to the processor.
  • each module or each step of the above-mentioned disclosure can be realized by a general-purpose computing device, and they can be concentrated on a single computing device, or distributed in a network composed of multiple computing devices In fact, they can be implemented in program code executable by a computing device, and thus, they can be stored in a storage device to be executed by a computing device, and in some cases, can be executed in an order different from that shown here. Or described steps, or they are fabricated into individual integrated circuit modules, or multiple modules or steps among them are fabricated into a single integrated circuit module for implementation. As such, the present disclosure is not limited to any specific combination of hardware and software.

Landscapes

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

Abstract

本公开实施例提供了一种路径计算方法、装置、存储介质及电子装置，该方法包括：控制器根据端到端时延需求计算转发路径及转发时延信息；所述控制器下发所述转发路径及所述转发时延信息到设备侧，可以解决相关技术中基于网络图来计算网络路径或路由无法满足业务需求的问题，使得确定的目标路径能够满足业务需求。

Description

一种路径计算方法、装置、存储介质及电子装置
相关申请的交叉引用
本公开基于2021年05月08日提交的发明名称为“一种路径计算方法、装置、存储介质及电子装置”的中国专利申请CN202110502498.1，并且要求该专利申请的优先权，通过引用将其所公开的内容全部并入本公开。
技术领域
本公开实施例涉及通信领域，具体而言，涉及一种路径计算方法、装置、存储介质及电子装置。
背景技术
RFC4655中描述了一种基于路径计算单元(Path Computation Element，简称为PCE)的结构，用于多协议标签交换(Multi-Protocol Label Switching，简称为MPLS)和通用多协议标签交换(Generalized Multi-Protocol Label Switching，简称为GMPLS)流量工程(Traffic Engineer，简称为TE)标签交换路径(Label Switched Paths，简称为LSP)的路径计算。其中，PCE是能够基于网络图来计算网络路径或路由，并应用计算约束条件的实体、部件、应用程序或网络节点。在PCC-initiate模式下，路径计算客户端(Path Computation Client，简称为PCC)可以请求PCE执行路径计算，在PCE-initiate模式下，PCE可以主动发起路径计算并且下发路径建立请求到首节点。同时PCE也可以作为控制器(PCE-based Central Controller，简称为PCECC)主动下发路径建立，其中携带集中控制对象(Central Control Instructions，简称为CCI)携带路径建立信息到路径经过的所有节点。
为了满足确定性服务等的业务需求，IEEE 802.1标准组织定义了时间敏感网络(Time-Sensitive Networking，简称为TSN)，主要为L2层业务提供低时延，低丢包率，高可靠性等服务。同时，为了在L3层实现确定性技术，IETF标准组织也提出确定性网络技术(Deterministic Networking，简称为DetNet)，其中RFC8655定义DetNet相关技术架构，为二层桥和三层路由网络提供确定性服务，服务等级(Quality of Service，简称为QoS)要求包括确定性时延上限，低丢包率，降低抖动和高可靠性等。
针对相关技术中基于网络图来计算网络路径或路由无法满足业务需求的问题，尚未提出解决方案。
发明内容
本公开实施例提供了一种路径计算方法、装置、存储介质及电子装置，以至少解决相关技术中基于网络图来计算网络路径或路由无法满足业务需求的问题。
根据本公开的一个实施例，提供了一种路径计算方法，包括：
控制器根据端到端时延需求计算转发路径及转发时延信息；
所述控制器下发所述转发路径及所述转发时延信息到设备侧。
在一示例性实施例中，所述控制器下发所述转发路径及所述转发时延信息到设备侧包括：
所述控制器采用路径计算单元通信PCEP协议下发所述转发路径及所述转发时延信息到设备侧，其中，所述控制器为路径计算单元PCE。
在一示例性实施例中，在所述控制器根据端到端时延需求计算所述转发路径及所述转发时延之前，所述方法还包括：
在PCE-initiate模式或PCECC模式下，所述控制器获取所述端到端时延需求；
在路径计算客户端PCC-initiate模式下，所述控制器接收首节点PCC发送的路径计算请求。
在一示例性实施例中，所述路径计算请求为基于路径计算单元通信协议PCEP协议的路径计算请求消息PCReq消息；
所述路径计算请求PCReq消息中携带有标签交换路径LSP对象的LSP-EXTENDED-FLAG TLV中扩展T比特用于指示基于时间调度的路径计算请求；
所述路径计算请求PCReq消息中携带有标签交换路径LSPA(Label Switched Paths Attribute)对象中扩展的TIME-SCHEDULING TLV用于携带所述端到端时延的约束条件，其中，所述约束条件包括最大端到端时延，最小端到端时延及最大端到端时延变化。
在一示例性实施例中，所述控制器下发所述转发路径及所述转发时延信息到所述设备侧包括：
在PCC-initiate模式或PCE-initiate模式下，所述设备侧为首节点PCC，所述控制器下发所述转发路径及所述转发时延信息到所述首节点PCC；
在PCECC模式下，所述设备侧为所述转发路径经过的节点，所述控制器下发所述转发路径及所述转发时延信息到所述转发路径经过的节点。
在一示例性实施例中，在PCC-initiate模式或PCE-initiate模式下，若为IP/MPLS网络，通过在ERO对象中扩展delay字段携带所述转发路径及所述转发时延信息；
若为源路由(Segement routing，简称为SR)网络，通过在源路由显示路径对象(Segement routing Explicit Routing Object，简称为SR-ERO)对象中扩展delay字段携带所述转发路径及所述转发时延信息；
若为源路由版本6(SRv6)网络，通过在SRv6-ERO对象中扩展的delay字段携带所述转发路径及所述转发时延信息。
在一示例性实施例中，在PCECC模式下，通过在集中控制对象CCI对象中新增的时间表类型长度值TIME-SCHEDULING TLV(Type Length Value)携带所述转发路径及所述转发时延信息。
在一示例性实施例中，在所述控制器根据所述端到端时延需求计算所述转发路径及所述转发时延信息之前，所述方法还包括：
作为PCE的所述控制器与作为PCC的所述设备侧进行基于时间调度的路径计算能力的协商。
在一示例性实施例中，在PCC-initiate模式或PCE-initiate模式下，若为IP/MPLS网络，通过在所述PCEP协议中OPEN消息的OPEN对象扩展的比特T指示是否具有基于时间调度的路径计算能力；
若为SR网络，通过在SR-PCE-CAPABILITY Sub-TLV扩展的比特T指示是否具有基于时间调度的路径计算能力；
若为SRv6网络，通过在SRv6-PCE-CAPABILITY Sub-TLV扩展的比特T指示是否具有基于时间调度的路径计算能力。
在一示例性实施例中，在PCECC模式下，通过在OPEN消息的PCECC CAPABILITY sub-TLV中扩展的比特T指示是否具有基于时间调度的路径计算能力。
根据本公开的另一个实施例，还提供了一种路径计算方法，包括：
设备侧接收控制器下发的转发路径与转发时延信息，其中，所述转发路径与所述转发时延信息是所述控制器根据端到端时延需求计算得到的。
在一示例性实施例中，在所述设备侧接收控制器下发的转发路径与转发时延信息之前，所述方法还包括：
所述设备侧采用路径计算单元通信PCEP协议向所述控制器发送路径计算请求，其中，所述控制器为路径计算单元PCE。
在一示例性实施例中，所述路径计算请求为基于路径计算单元通信协议PCEP协议的路径计算请求消息PCReq消息；
所述路径计算请求PCReq消息中携带有标签交换路径LSP对象的LSP-EXTENDED-FLAG TLV中扩展T比特用于指示基于时间调度的路径计算请求；
所述路径计算请求PCReq消息中携带有LSPA对象中扩展的TIME-SCHEDULING TLV用于携带所述端到端时延的约束条件，其中，所述约束条件包括最大端到端时延，最小端到端时延及最大端到端时延变化。
在一示例性实施例中，在PCC-initiate模式或PCE-initiate模式下，所述设备侧为首节点PCC；
在PCECC模式下，所述设备侧为所述转发路径经过的节点。
在一示例性实施例中，在PCC-initiate模式或PCE-initiate模式下，若为IP/MPLS网络，通过在ERO对象中扩展的delay字段携带所述转发路径与所述转发时延信息；
若为SR网络，通过在SR-ERO对象中扩展的delay字段携带所述转发路径与所述转发时延信息；
若为SRv6网络，通过在SRv6-ERO对象中扩展的delay字段携带所述转发路径与所述转发时延信息。
在一示例性实施例中，在PCECC模式下，通过在集中控制对象CCI对象中新增的TIME-SCHEDULING TLV携带所述转发路径与所述转发时延信息。
在一示例性实施例中，在所述设备侧接收所述控制器下发的所述转发路径与所述转发时延之前，所述方法还包括：
作为PCC的所述设备侧与作为PCE的所述控制器进行基于时间调度的路径计算能力的协商。
在一示例性实施例中，在PCC-initiate模式或PCE-initiate模式下，若为IP/MPLS网络，通过在所述PCEP协议中OPEN消息的OPEN对象扩展的比特T指示是否具有基于时间调度的路径计算能力；
若为SR网络，通过在所述PCEP协议中SR-PCE-CAPABILITY Sub-TLV扩展的比特T指示是否具有基于时间调度的路径计算能力；
若为SRv6网络，通过在所述PCEP协议中SRv6-PCE-CAPABILITY Sub-TLV扩展的比特T 指示是否具有基于时间调度的路径计算能力。
在一示例性实施例中，在PCECC模式下，通过在OPEN消息的PCECC CAPABILITY sub-TLV中扩展的比特T指示是否具有基于时间调度的路径计算能力。
根据本公开的另一个实施例，还提供了一种路径计算装置，应用于控制器，包括：
计算模块，设置为根据端到端时延需求计算转发路径及转发时延信息；
下发模块，设置为下发所述转发路径与所述转发时延信息到设备侧。
在一示例性实施例中，所述下发模块，还设置为
采用路径计算单元通信PCEP协议下发所述转发路径及所述转发时延信息到设备侧，其中，所述控制器为路径计算单元PCE。
在一示例性实施例中，所述装置还包括：
获取模块，设置为在PCE-initiate模式或PCECC模式下，所述控制器获取所述端到端时延需求；
接收请求模块，设置为在路径计算客户端PCC-initiate模式下，所述控制器接收首节点PCC发送的路径计算请求。
在一示例性实施例中，所述路径计算请求为基于路径计算单元通信协议PCEP协议的路径计算请求消息PCReq消息；
所述路径计算请求PCReq消息中携带有标签交换路径LSP对象的LSP-EXTENDED-FLAG TLV中扩展T比特用于指示基于时间调度的路径计算请求；
所述路径计算请求PCReq消息中携带有LSPA对象中扩展的TIME-SCHEDULING TLV用于携带所述端到端时延的约束条件，其中，所述约束条件包括最大端到端时延，最小端到端时延及最大端到端时延变化。
在一示例性实施例中，所述下发模块，还设置为在PCC-initiate模式或PCE-initiate模式下，所述设备侧为首节点PCC，下发所述转发路径及所述转发时延信息到所述首节点PCC；
在PCECC模式下，所述设备侧为所述转发路径经过的节点，下发所述转发路径及所述转发时延信息到所述转发路径经过的节点。
在一示例性实施例中，在PCC-initiate模式或PCE-initiate模式下，若为IP/MPLS网络，通过在ERO对象中扩展delay字段携带所述转发路径及所述转发时延信息；
若为SR网络，通过在SR-ERO对象中扩展delay字段携带所述转发路径及所述转发时延信息；
若为SRv6网络，通过在SRv6-ERO对象中扩展的delay字段携带所述转发路径及所述转发时延信息。
在一示例性实施例中，在PCECC模式下，通过在集中控制对象CCI对象中新增的TIME-SCHEDULING TLV携带所述转发路径及所述转发时延信息。
在一示例性实施例中，所述装置还包括：
第一协商模块，设置为作为PCE与作为PCC的所述设备侧进行基于时间调度的路径计算能力的协商。
在一示例性实施例中，在PCC-initiate模式或PCE-initiate模式下，若为IP/MPLS网络，通过在所述PCEP协议中OPEN消息的OPEN对象扩展的比特T指示是否具有基于时间调度的路径计算能力；
若为SR网络，通过在SR-PCE-CAPABILITY Sub-TLV扩展的比特T指示是否具有基于时间调度的路径计算能力；
若为SRv6网络，通过在SRv6-PCE-CAPABILITY Sub-TLV扩展的比特T指示是否具有基于时间调度的路径计算能力。
在一示例性实施例中，在PCECC模式下，通过在OPEN消息的PCECC CAPABILITY sub-TLV中扩展的比特T指示是否具有基于时间调度的路径计算能力。
根据本公开的另一个实施例，还提供了一种路径计算装置，应用于设备侧，包括：
接收模块，设置为接收控制器下发的转发路径与所述转发时延信息，其中，所述转发路径与所述转发时延信息是所述控制器根据端到端时延需求计算得到的。
在一示例性实施例中，所述装置还包括：
发送模块，设置为采用路径计算单元通信PCEP协议向所述控制器发送路径计算请求，其中，所述控制器为路径计算单元PCE。
在一示例性实施例中，所述路径计算请求为基于路径计算单元通信协议PCEP协议的路径计算请求消息PCReq消息；
所述路径计算请求PCReq消息中携带有标签交换路径LSP对象的LSP-EXTENDED-FLAG TLV中扩展T比特用于指示基于时间调度的路径计算请求；
所述路径计算请求PCReq消息中携带有LSPA对象中扩展的TIME-SCHEDULING TLV用于携带所述端到端时延的约束条件，其中，所述约束条件包括最大端到端时延，最小端到端时延及最大端到端时延变化。
在一示例性实施例中，在PCC-initiate模式或PCE-initiate模式下，所述设备侧为首节点PCC；
在PCECC模式下，所述设备侧为所述转发路径经过的节点。
在一示例性实施例中，在PCC-initiate模式或PCE-initiate模式下，若为IP/MPLS网络，通过在ERO对象中扩展的delay字段携带所述转发路径与所述转发时延信息；
若为SR网络，通过在SR-ERO对象中扩展的delay字段携带所述转发路径与所述转发时延信息；
若为SRv6网络，通过在SRv6-ERO对象中扩展的delay字段携带所述转发路径与所述转发时延信息。
在一示例性实施例中，在PCECC模式下，通过在集中控制对象CCI对象中新增的TIME-SCHEDULING TLV携带所述转发路径与所述转发时延信息。
在一示例性实施例中，所述装置还包括：
第二协商模块，设置为作为PCC与作为PCE的所述控制器进行基于时间调度的路径计算能力的协商。
在一示例性实施例中，在PCC-initiate模式或PCE-initiate模式下，若为IP/MPLS网络，通过在所述PCEP协议中OPEN消息的OPEN对象扩展的比特T指示是否具有基于时间调度的路径计算能力；
若为SR网络，通过在所述PCEP协议中SR-PCE-CAPABILITY Sub-TLV扩展的比特T指示是否具有基于时间调度的路径计算能力；
若为SRv6网络，通过在所述PCEP协议中SRv6-PCE-CAPABILITY Sub-TLV扩展的比特T 指示是否具有基于时间调度的路径计算能力。
在一示例性实施例中，在PCECC模式下，通过在OPEN消息的PCECC CAPABILITY sub-TLV中扩展的比特T指示是否具有基于时间调度的路径计算能力。
根据本公开的又一个实施例，还提供了一种计算机可读的存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
根据本公开的又一个实施例，还提供了一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行上述任一项方法实施例中的步骤。
本公开实施例，控制器根据端到端时延需求计算转发路径及转发时延信息；所述控制器下发所述转发路径及所述转发时延信息到设备侧，可以解决相关技术中基于网络图来计算网络路径或路由无法满足业务需求的问题，使得确定的目标路径能够满足业务需求。
附图说明
图1是本公开实施例的路径计算方法的移动终端的硬件结构框图；
图2是根据本公开实施例的路径计算方法的流程图一；
图3是根据本公开实施例的路径计算方法的流程图二；
图4是根据本实施例的T比特在LSP-EXTENDED-FLAG TLV中的扩展格式的示意图；
图5是根据本实施例的TIME-SCHEDULING TLV在LSPA中的扩展格式的示意图；
图6是根据本实施例的T比特在OPEN对象中的扩展格式的示意图；
图7是根据本实施例的时间调度信息在IPv4ERO对象中的扩展格式的示意图；
图8是根据本实施例的时间调度信息在IPv6ERO对象中的扩展格式的示意图；
图9是根据本实施例的T比特在SR-PCE-CAPABILITY Sub-TLV中的扩展格式的示意图；
图10是根据本实施例的时间调度信息在SR-ERO对象中的扩展格式的示意图；
图11是根据本实施例的T比特在SRv6-PCE-CAPABILITY Sub-TLV中的扩展格式的示意图；
图12是根据本实施例的T比特在SRv6-PCE-CAPABILITY Sub-TLV中的扩展格式的示意图；
图13是根据本实施例的T比特在PCECC CAPABILITY sub-TLV中的扩展格式的示意图；
图14是根据本实施例的TIME-SCHEDULING TLV格式的示意图；
图15是根据本实施例的基于时间调度路径计算的DetNet网络的结构图；
图16是根据本实施例的路径计算装置的框图一；
图17是根据本实施例的路径计算装置的框图二。
具体实施方式
下文中将参考附图并结合实施例来详细说明本公开的实施例。
需要说明的是，本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
本公开实施例中所提供的方法实施例可以在移动终端、计算机终端或者类似的运算装置中执行。以运行在移动终端上为例，图1是本公开实施例的路径计算方法的移动终端的硬件结构框图，如图1所示，移动终端可以包括一个或多个(图1中仅示出一个)处理器102(处 理器102可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置)和用于存储数据的存储器104，其中，上述移动终端还可以包括用于通信功能的传输设备106以及输入输出设备108。本领域普通技术人员可以理解，图1所示的结构仅为示意，其并不对上述移动终端的结构造成限定。例如，移动终端还可包括比图1中所示更多或者更少的组件，或者具有与图1所示不同的配置。
存储器104可用于存储计算机程序，例如，应用软件的软件程序以及模块，如本公开实施例中的路径计算方法对应的计算机程序，处理器102通过运行存储在存储器104内的计算机程序，从而执行各种功能应用以及业务链地址池切片处理，即实现上述的方法。存储器104可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器104可进一步包括相对于处理器102远程设置的存储器，这些远程存储器可以通过网络连接至移动终端。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输装置106用于经由一个网络接收或者发送数据。上述的网络具体实例可包括移动终端的通信供应商提供的无线网络。在一个实例中，传输装置106包括一个网络适配器(Network Interface Controller，简称为NIC)，其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中，传输装置106可以为射频(Radio Frequency，简称为RF)模块，其用于通过无线方式与互联网进行通讯。
在本实施例中提供了一种运行于上述移动终端或网络架构的路径计算方法，图2是根据本公开实施例的路径计算方法的流程图一，如图2所示，该流程包括如下步骤：
步骤S202，控制器根据端到端时延需求计算转发路径及转发时延信息；
步骤S204，所述控制器下发所述转发路径及所述转发时延信息到设备侧。
在一示例性实施例中，上述步骤S204中，具体可以采用路径计算单元通信PCEP协议下
发所述转发路径及所述转发时延信息到设备侧，其中，所述控制器为路径计算单元PCE。
通过上述步骤S202至S204，控制器根据端到端时延需求计算转发路径及转发时延信息；所述控制器下发所述转发路径及所述转发时延信息到设备侧，可以解决相关技术中基于网络图来计算网络路径或路由无法满足业务需求的问题，使得确定的目标路径能够满足业务需求。
在一示例性实施例中，在所述控制器根据端到端时延需求计算所述转发路径及所述转发时延之前，在PCE-initiate模式或PCECC模式下，所述控制器获取所述端到端时延需求；在路径计算客户端PCC-initiate模式下，所述控制器接收首节点PCC发送的路径计算请求。
在一示例性实施例中，所述路径计算请求为基于路径计算单元通信协议PCEP协议的路径计算请求消息PCReq消息；所述路径计算请求PCReq消息中携带有标签交换路径LSP对象的LSP-EXTENDED-FLAG TLV中扩展T比特用于指示基于时间调度的路径计算请求；所述路径计算请求PCReq消息中携带有LSPA对象中扩展的TIME-SCHEDULING TLV用于携带所述端到端时延的约束条件，其中，所述约束条件包括最大端到端时延，最小端到端时延及最大端到端时延变化。
在一可选的实施例中，上述步骤S204具体可以包括：
在PCC-initiate模式或PCE-initiate模式下，所述设备侧为首节点PCC，所述控制器下发所述转发路径及所述转发时延信息到所述首节点PCC；
在PCECC模式下，所述设备侧为所述转发路径经过的节点，所述控制器下发所述转发路 径及所述转发时延信息到所述转发路径经过的节点。
本实施例中，在所述PCC-initiate模式或所述PCE-initiate模式下，若为IP/MPLS网络，通过在ERO对象中扩展delay字段携带所述转发路径及所述转发时延信息；若为SR网络，通过在SR-ERO对象中扩展delay字段携带所述转发路径及所述转发时延信息；若为SRv6网络，通过在SRv6-ERO对象中扩展的delay字段携带所述转发路径及所述转发时延信息。
本实施例中，在所述PCECC模式下，通过在集中控制对象CCI对象中新增的TIME-SCHEDULING TLV携带所述转发路径及所述转发时延信息。
在另一可选的实施例中，在所述控制器根据所述端到端时延需求计算所述转发路径及所述转发时延信息之前，作为PCE的所述控制器与作为PCC的所述设备侧进行基于时间调度的路径计算能力的协商。
本实施例中，在所述PCC-initiate模式或所述PCE-initiate模式下，若为IP/MPLS网络，通过在所述PCEP协议中OPEN消息的OPEN对象扩展的比特T指示是否具有基于时间调度的路径计算能力；若为SR网络，通过在SR-PCE-CAPABILITY Sub-TLV扩展的比特T指示是否具有基于时间调度的路径计算能力；若为SRv6网络，通过在SRv6-PCE-CAPABILITY Sub-TLV扩展的比特T指示是否具有基于时间调度的路径计算能力。
本实施例中，在PCECC模式下，通过在OPEN消息的PCECC CAPABILITY sub-TLV中扩展的比特T指示是否具有基于时间调度的路径计算能力。
根据本公开的另一个实施例，还提供了一种路径计算方法，图3是根据本公开实施例的路径计算方法的流程图二，如图3所示，该流程包括如下步骤：
步骤S302，设备侧接收控制器下发的转发路径与转发时延信息，其中，所述转发路径与所述转发时延信息是所述控制器根据端到端时延需求计算得到的。
上述步骤S302中，具体可以通过PCEP协议接收控制器下发的转发路径与转发时延信息。
通过上述步骤S302，可以解决相关技术中基于网络图来计算网络路径或路由无法满足业务需求的问题，使得确定的目标路径能够满足业务需求。
在一可选的实施例中，在所述设备侧接收控制器下发的转发路径与转发时延信息之前，所述设备侧采用路径计算单元通信PCEP协议向所述控制器发送路径计算请求，其中，所述控制器为路径计算单元PCE。
本实施例中，所述路径计算请求为基于路径计算单元通信协议PCEP协议的路径计算请求消息PCReq消息；所述路径计算请求PCReq消息中携带有标签交换路径LSP对象的LSP-EXTENDED-FLAG TLV中扩展T比特用于指示基于时间调度的路径计算请求；所述路径计算请求PCReq消息中携带有LSPA对象中扩展的TIME-SCHEDULING TLV用于携带所述端到端时延的约束条件，其中，所述约束条件包括最大端到端时延，最小端到端时延及最大端到端时延变化。
本实施例中，在PCC-initiate模式或PCE-initiate模式下，所述设备侧为首节点PCC；在PCECC模式下，所述设备侧为所述转发路径经过的节点。
本实施例中，在所述PCC-initiate模式或所述PCE-initiate模式下，若为IP/MPLS网络，通过在ERO对象中扩展的delay字段携带所述转发路径与所述转发时延信息；若为SR网络，通过在SR-ERO对象中扩展的delay字段携带所述转发路径与所述转发时延信息；若为 SRv6网络，通过在SRv6-ERO对象中扩展的delay字段携带所述转发路径与所述转发时延信息。
本实施例中，在所述PCECC模式下，通过在集中控制对象CCI对象中新增的TIME-SCHEDULING TLV携带所述转发路径与所述转发时延信息。
在另一可选的实施例中，在所述设备侧接收所述控制器下发的所述转发路径与所述转发时延之前，作为PCC的所述设备侧与作为PCE的所述控制器进行基于时间调度的路径计算能力的协商。
本实施例中，在所述PCC-initiate模式或所述PCE-initiate模式下，若为IP/MPLS网络，通过在所述PCEP协议中OPEN消息的OPEN对象扩展的比特T指示是否具有基于时间调度的路径计算能力；若为SR网络，通过在所述PCEP协议中SR-PCE-CAPABILITY Sub-TLV扩展的比特T指示是否具有基于时间调度的路径计算能力；若为SRv6网络，通过在所述PCEP协议中SRv6-PCE-CAPABILITY Sub-TLV扩展的比特T指示是否具有基于时间调度的路径计算能力。
本实施例中，在PCECC模式下，通过在OPEN消息的PCECC CAPABILITY sub-TLV中扩展的比特T指示是否具有基于时间调度的路径计算能力。
为了实现端到端时延队列调度的计算，可以使用PCE，扩展路径计算单元通信协议(Path Computation Element Protocol，PCEP)实现基于时间调度的路径计算。本发明提出一种基于时间队列调度的计算方法，通过扩展PCEP协议，实现设备与控制器(如PCE)之间的路径计算信息交互，该方法适用于IP/MPLS,SR及SRv6网络。路径计算交互有多种方式，第一种，PCC-initiate模式，首节点可以作为PCC向PCE或控制器主动发起基于时间调度的路径计算请求，PCE或控制器计算路径后发送应答消息给首节点。第二种，PCE-initiate模式或PCECC模式，PCE或控制器也可以主动计算基于时间调度的路径，如果是PCE-initiate模式，PCE或控制器下发路径结果到首节点，如果是PCECC模式，PCE或控制器下发路径结果到路径所经过的所有节点。
PCC-initiate模式下，首先首节点向PCE或控制器发送路径计算请求，申请计算满足端到端时延的路径，其中：
图4是根据本实施例的T比特在LSP-EXTENDED-FLAG TLV中的扩展格式的示意图，如图4所示，扩展PCEP协议的路径计算请求消息PCReq，扩展LSP对象中的LSP-EXTENDED-FLAG，扩展一个新的flag位，用于指示基于时间调度的路径计算请求。
图5是根据本实施例的TIME-SCHEDULING TLV在LSPA中的扩展格式的示意图，如图5所示，扩展PCEP协议中基于时间的约束条件，在LSPA对象中扩展一个新的TLV，用于携带基于时间调度的路径计算约束条件，端到端最大，最小时延及时延抖动等。
PCC-initiate模式下，其次PCE根据时延信息计算路径结果及每个节点的时延，包括IP/MPLS,SR,SRv6网络等路径计算结果扩展，下发到PCC。
IP/MPLS网络时，扩展PCEP协议中基于时间调度的路径计算能力协商，图6是根据本实施例的T比特在OPEN对象中的扩展格式的示意图，扩展OPEN消息的OPEN对象携带T比特如图6所示，图7是根据本实施例的时间调度信息在IPv4ERO对象中的扩展格式的示意图，图8是根据本实施例的时间调度信息在IPv6ERO对象中的扩展格式的示意图，扩展PCEP协议中的路径计算结果下发如图7和图8所示。
SR网络时，扩展PCEP协议中基于时间调度的路径计算能力协商，图9是根据本实施例的T比特在SR-PCE-CAPABILITY Sub-TLV中的扩展格式的示意图，扩展OPEN消息的OPEN对象的T比特比如图9所示，图10是根据本实施例的时间调度信息在SR-ERO对象中的扩展格式的示意图，扩展PCEP协议中基于SR-TE的路径计算结果下发如图10所示。
SRv6网络时，扩展PCEP协议中基于时间调度的路径计算能力协商，图11是根据本实施例的T比特在SRv6-PCE-CAPABILITY Sub-TLV中的扩展格式的示意图，图12是根据本实施例的T比特在SRv6-PCE-CAPABILITY Sub-TLV中的扩展格式的示意图，扩展OPEN消息的OPEN对象携带T比特如图11所示，扩展PCEP协议中基于SRv6的路径计算结果下发如图12所示。
PCE-initiate模式时，PCE或控制器也可以主动计算基于时间调度的路径，并下发路径结果到首节点。路径结果扩展与PCC-initiate模式相同，IP/MPLS，SR，SRv6网络的PCEP路径结果扩展如图7，8，10，12所示。
PCECC模式时，PCE或控制器也可以主动计算基于时间调度的路径，并下发路径结果到路径所经过的所有节点。在OPEN消息中PCECC CAPABILITY sub-TLV中扩展T比特用于协商支持基于时延调度的能力，在PCECC的CCI对象中新增TIME-SCHEDULING TLV用于下发路径计算结果。该扩展适用于IP/MPLS，SR，SRv6网络。
图13是根据本实施例的T比特在PCECC CAPABILITY sub-TLV中的扩展格式的示意图，如图13所示，在PCECC模式下，通过在所述PCEP协议的OPEN消息的PCECC CAPABILITY sub-TLV中扩展的比特T指示是否具有基于时间调度的路径计算能力。
图14是根据本实施例的TIME-SCHEDULING TLV格式的示意图，如图14所示，在所述PCECC模式下，通过在PCECC的集中控制对象CCI对象中新增的TIME-SCHEDULING TLV携带所述目标路径与所述每个节点的时延信息。
其中路径结果中的基于时间调度相关的信息，如扩展delay等，不限于具体的时延，还可以包括时延，队列，调度等信息。
本实施例，通过扩展PCEP协议，实现设备与控制器(如PCE)之间的路径计算信息交互，该方法适用于IP/MPLS，SR及SRv6网络。PCC-initiate模式时具体步骤如下：
首节点作为PCC向控制器或PCE申请计算满足端到端时延的路径，其中请求消息中携带时延队列等相关约束条件；
控制器或PCE根据时延信息计算路径结果及每个节点的时延，包括IP/MPLS，SR，SRv6网络等路径计算结果扩展，下发应答消息到PCC。
PCE-initiate及PCECC模式时具体步骤如下：
PCE或控制器主动计算满足端到端时延的基于时间调度的路径；
PCE或控制器下发基于时间调度信息的路径结果到设备侧。
图15是根据本实施例的基于时间调度路径计算的DetNet网络的结构图，如图15所示，DetNet IP/MPLS网络中，控制器(如PCE)通过PCEP协议与DetNet网络进行交互，需要计算满足端到端时延的路径，且该路径结果包括路径的转发及时间调度信息。本发明提出一种基于时间队列调度的计算方法，通过扩展PCEP协议，实现设备与控制器(如PCE)之间的路径计算信息交互，当DetNet域为IP/MPLS网络时，PCC-initiate模式下具体流程如下：
首节点作为PCC向控制器或PCE申请计算满足端到端时延的路径，其中请求消息中的LSP_EXTENDED_LSP中的T比特置1，LSPA对象中的TIME-SCHEDULING TLV携带时延队列等相 关约束条件；
控制器或PCE根据时延信息计算路径转发结果及每个节点的时间时延信息，携带于ERO对象中，下发应答消息到PCC。
DetNet SR网络中，控制器(如PCE)通过PCEP协议与DetNet网络进行交互，需要计算满足端到端时延的路径，且该路径结果包括路径的转发及时间调度信息。通过扩展PCEP协议，实现设备与控制器(如PCE)之间的路径计算信息交互，当DetNet域为SR网络时，PCC-initiate模式下具体流程如下：
首节点作为PCC向控制器或PCE申请计算满足端到端时延的路径，其中请求消息中的LSP_EXTENDED_LSP中的T比特置1，LSPA对象中的TIME-SCHEDULING TLV携带时延队列等相关约束条件；
控制器或PCE根据时延信息计算路径转发结果及每个节点的时间时延信息，携带于SR-ERO对象中，下发应答消息到PCC。
DetNet SRv6网络中，控制器(如PCE)通过PCEP协议与DetNet网络进行交互，需要计算满足端到端时延的路径，且该路径结果包括路径的转发及时间调度信息。本实施例通过扩展PCEP协议，实现设备与控制器(如PCE)之间的路径计算信息交互，当DetNet域为SRv6网络时，PCC-initiate模式下具体流程如下：
首节点作为PCC向控制器或PCE申请计算满足端到端时延的路径，其中请求消息中的LSP_EXTENDED_LSP中的T比特置1，LSPA对象中的TIME-SCHEDULING TLV携带时延队列等相关约束条件；
控制器或PCE根据时延信息计算路径转发结果及每个节点的时间时延信息，携带于SRv6-ERO对象中，下发应答消息到PCC。
本实施例，通过扩展PCEP协议，实现设备与控制器(如PCE)之间的路径计算信息交互，该方法适用于IP/MPLS,SR及SRv6网络。设备侧向控制器(如PCE)申请基于时间调度的路径计算，PCE根据时延信息计算转发路径及每个节点的时延，通过扩展PCEP协议，下发满足端到端时延的路径转发及调度信息。
根据本公开的另一个实施例，还提供了一种路径计算装置，应用于控制器，图16是根据本实施例的路径计算装置的框图一，如图16所示，包括：
计算模块162，设置为根据端到端时延需求计算转发路径及转发时延信息；
下发模块164，设置为下发所述转发路径与所述转发时延信息到设备侧。
在一示例性实施例中，所述下发模块164，还设置为
采用路径计算单元通信PCEP协议下发所述转发路径及所述转发时延信息到设备侧，其中，所述控制器为路径计算单元PCE。
在一示例性实施例中，所述装置还包括：
获取模块，设置为在PCE-initiate模式或PCECC模式下，所述控制器获取所述端到端时延需求；
接收请求模块，设置为在路径计算客户端PCC-initiate模式下，所述控制器接收首节点PCC发送的路径计算请求。
在一示例性实施例中，所述路径计算请求为基于路径计算单元通信协议PCEP协议的路径 计算请求消息PCReq消息；
所述路径计算请求PCReq消息中携带有标签交换路径LSP对象的LSP-EXTENDED-FLAG TLV中扩展T比特用于指示基于时间调度的路径计算请求；
所述路径计算请求PCReq消息中携带有LSPA对象中扩展的TIME-SCHEDULING TLV用于携带所述端到端时延的约束条件，其中，所述约束条件包括最大端到端时延，最小端到端时延及最大端到端时延变化。
在一示例性实施例中，所述下发模块164，还设置为在PCC-initiate模式或PCE-initiate模式下，所述设备侧为首节点PCC，下发所述转发路径及所述转发时延信息到所述首节点PCC；
在PCECC模式下，所述设备侧为所述转发路径经过的节点，下发所述转发路径及所述转发时延信息到所述转发路径经过的节点。
在一示例性实施例中，在所述PCC-initiate模式或所述PCE-initiate模式下，若为IP/MPLS网络，通过在ERO对象中扩展delay字段携带所述转发路径及所述转发时延信息；
若为SR网络，通过在SR-ERO对象中扩展delay字段携带所述转发路径及所述转发时延信息；
若为SRv6网络，通过在SRv6-ERO对象中扩展的delay字段携带所述转发路径及所述转发时延信息。
在一示例性实施例中，在所述PCECC模式下，通过在集中控制对象CCI对象中新增的TIME-SCHEDULING TLV携带所述转发路径及所述转发时延信息。
在一示例性实施例中，所述装置还包括：
第一协商模块，设置为作为PCE与作为PCC的所述设备侧进行基于时间调度的路径计算能力的协商。
在一示例性实施例中，在所述PCC-initiate模式或所述PCE-initiate模式下，若为IP/MPLS网络，通过在所述PCEP协议中OPEN消息的OPEN对象扩展的比特T指示是否具有基于时间调度的路径计算能力；
若为SR网络，通过在SR-PCE-CAPABILITY Sub-TLV扩展的比特T指示是否具有基于时间调度的路径计算能力；
若为SRv6网络，通过在SRv6-PCE-CAPABILITY Sub-TLV扩展的比特T指示是否具有基于时间调度的路径计算能力。
在一示例性实施例中，在PCECC模式下，通过在OPEN消息的PCECC CAPABILITY sub-TLV中扩展的比特T指示是否具有基于时间调度的路径计算能力。
根据本公开的另一个实施例，还提供了一种路径计算装置，应用于设备侧，图17是根据本实施例的路径计算装置的框图二，如图17所示，包括：
接收模块172，设置为接收控制器下发的转发路径与所述转发时延信息，其中，所述转发路径与所述转发时延信息是所述控制器根据端到端时延需求计算得到的。
在一示例性实施例中，所述装置还包括：
发送模块，设置为采用路径计算单元通信PCEP协议向所述控制器发送路径计算请求，其中，所述控制器为路径计算单元PCE。
在一示例性实施例中，所述路径计算请求为基于路径计算单元通信协议PCEP协议的路径 计算请求消息PCReq消息；
所述路径计算请求PCReq消息中携带有标签交换路径LSP对象的LSP-EXTENDED-FLAG TLV中扩展T比特用于指示基于时间调度的路径计算请求；
所述路径计算请求PCReq消息中携带有LSPA对象中扩展的TIME-SCHEDULING TLV用于携带所述端到端时延的约束条件，其中，所述约束条件包括最大端到端时延，最小端到端时延及最大端到端时延变化。
在一示例性实施例中，在PCC-initiate模式或PCE-initiate模式下，所述设备侧为首节点PCC；
在PCECC模式下，所述设备侧为所述转发路径经过的节点。
在一示例性实施例中，在所述PCC-initiate模式或所述PCE-initiate模式下，若为IP/MPLS网络，通过在ERO对象中扩展的delay字段携带所述转发路径与所述转发时延信息；
若为SR网络，通过在SR-ERO对象中扩展的delay字段携带所述转发路径与所述转发时延信息；
若为SRv6网络，通过在SRv6-ERO对象中扩展的delay字段携带所述转发路径与所述转发时延信息。
在一示例性实施例中，在所述PCECC模式下，通过在集中控制对象CCI对象中新增的TIME-SCHEDULING TLV携带所述转发路径与所述转发时延信息。
在一示例性实施例中，所述装置还包括：
第二协商模块，设置为作为PCC与作为PCE的所述控制器进行基于时间调度的路径计算能力的协商。
在一示例性实施例中，在所述PCC-initiate模式或所述PCE-initiate模式下，若为IP/MPLS网络，通过在所述PCEP协议中OPEN消息的OPEN对象扩展的比特T指示是否具有基于时间调度的路径计算能力；
若为SR网络，通过在所述PCEP协议中SR-PCE-CAPABILITY Sub-TLV扩展的比特T指示是否具有基于时间调度的路径计算能力；
若为SRv6网络，通过在所述PCEP协议中SRv6-PCE-CAPABILITY Sub-TLV扩展的比特T指示是否具有基于时间调度的路径计算能力。
在一示例性实施例中，在PCECC模式下，通过在OPEN消息的PCECC CAPABILITY sub-TLV中扩展的比特T指示是否具有基于时间调度的路径计算能力。
本公开的实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序，其中，该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
在一个示例性实施例中，上述计算机可读存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本公开的实施例还提供了一种电子装置，包括存储器和处理器，该存储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
在一个示例性实施例中，上述电子装置还可以包括传输设备以及输入输出设备，其中， 该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
本实施例中的具体示例可以参考上述实施例及示例性实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本公开的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开不限制于任何特定的硬件和软件结合。
以上所述仅为本公开的优选实施例而已，并不用于限制本公开，对于本领域的技术人员来说，本公开可以有各种更改和变化。凡在本公开的原则之内，所作的任何修改、等同替换、改进等，均应包含在本公开的保护范围之内。

Claims (23)

  1. 一种路径计算方法，包括：
    控制器根据端到端时延需求计算转发路径及转发时延信息；
    所述控制器下发所述转发路径及所述转发时延信息到设备侧。
  2. 根据权利要求1所述的方法，其中，所述控制器下发所述转发路径及所述转发时延信息到设备侧包括：
    所述控制器采用路径计算单元通信PCEP协议下发所述转发路径及所述转发时延信息到设备侧，其中，所述控制器为路径计算单元PCE。
  3. 根据权利要求1所述的方法，其中，在所述控制器根据端到端时延需求计算所述转发路径及所述转发时延信息之前，所述方法还包括：
    在PCC发起PCE-initiate模式或PCE作为控制器PCECC模式下，所述控制器获取所述端到端时延需求；
    在路径计算客户端PCC-initiate模式下，所述控制器接收首节点PCC发送的路径计算请求。
  4. 根据权利要求3所述的方法，其中，
    所述路径计算请求为基于路径计算单元通信协议PCEP协议的路径计算请求消息PCReq消息；
    所述路径计算请求PCReq消息中携带有标签交换路径LSP对象的LSP扩展标志LSP-EXTENDED-FLAG TLV中扩展T比特用于指示基于时间调度的路径计算请求；
    所述路径计算请求PCReq消息中携带有标签交换路径属性LSPA对象中扩展的时间表类型长度值TIME-SCHEDULING TLV用于携带所述端到端时延的约束条件，其中，所述约束条件包括最大端到端时延，最小端到端时延及最大端到端时延变化。
  5. 根据权利要求1所述的方法，其中，所述控制器下发所述转发路径及所述转发时延信息到所述设备侧包括：
    在PCC发起PCC-initiate模式或PCC发起PCE-initiate模式下，所述设备侧为首节点PCC，所述控制器下发所述转发路径及所述转发时延信息到所述首节点PCC；
    在PCECC模式下，所述设备侧为所述转发路径经过的节点，所述控制器下发所述转发路径及所述转发时延信息到所述转发路径经过的节点。
  6. 根据权利要求1所述的方法，其中，
    在PCC发起PCC-initiate模式或PCC发起PCE-initiate模式下，若为互联网协议/多协议标签交换IP/MPLS网络，通过在显示路径对象ERO对象中扩展delay字段携带所述转发路径及所述转发时延信息；
    若为源路由SR网络，通过在SR-ERO对象中扩展delay字段携带所述转发路径及所述转发时延信息；
    若为SRv6网络，通过在SRv6-ERO对象中扩展的delay字段携带所述转发路径及所述转发时延信息。
  7. 根据权利要求1所述的方法，其中，
    在PCE作为控制器PCECC模式下，通过在集中控制对象CCI对象中新增的时间表类型长 度值TIME-SCHEDULING TLV携带所述转发路径及所述转发时延信息。
  8. 根据权利要求1所述的方法，其中，在所述控制器根据所述端到端时延需求计算所述转发路径及所述转发时延信息之前，所述方法还包括：
    作为PCE的所述控制器与作为PCC的所述设备侧进行基于时间调度的路径计算能力的协商。
  9. 根据权利要求8所述的方法，其中，
    在PCC发起PCC-initiate模式或PCE发起PCE-initiate模式下，若为互联网协议/多协议标签交换IP/MPLS网络，通过在路径计算单元通信PCEP协议中OPEN消息的OPEN对象扩展的比特T指示是否具有基于时间调度的路径计算能力；
    若为源路由SR网络，通过在SR-PCE-CAPABILITY Sub-TLV扩展的比特T指示是否具有基于时间调度的路径计算能力；
    若为SRv6网络，通过在SRv6-PCE-CAPABILITY Sub-TLV扩展的比特T指示是否具有基于时间调度的路径计算能力。
  10. 根据权利要求8所述的方法，其中，
    在PCE作为控制器PCECC模式下，通过在OPEN消息的PCECC CAPABILITY sub-TLV中扩展的比特T指示是否具有基于时间调度的路径计算能力。
  11. 一种路径计算方法，包括：
    设备侧接收控制器下发的转发路径与转发时延信息，其中，所述转发路径与所述转发时延信息是所述控制器根据端到端时延需求计算得到的。
  12. 根据权利要求11所述的方法，其中，在所述设备侧接收控制器下发的转发路径与转发时延信息之前，所述方法还包括：
    所述设备侧采用路径计算单元通信PCEP协议向所述控制器发送路径计算请求，其中，所述控制器为路径计算单元PCE。
  13. 根据权利要求11所述的方法，其中，
    所述路径计算请求为基于路径计算单元通信协议PCEP协议的路径计算请求消息PCReq消息；
    所述路径计算请求PCReq消息中携带有标签交换路径LSP对象的LSP扩展标志LSP-EXTENDED-FLAG TLV中扩展T比特用于指示基于时间调度的路径计算请求；
    所述路径计算请求PCReq消息中携带有标签交换路径属性LSPA对象中扩展的时间表类型长度值TIME-SCHEDULING TLV用于携带所述端到端时延的约束条件，其中，所述约束条件包括最大端到端时延，最小端到端时延及最大端到端时延变化。
  14. 根据权利要求11所述的方法，其中，
    在PCC发起PCC-initiate模式或PCE发起PCE-initiate模式下，所述设备侧为首节点PCC；
    在PCE作为控制器PCECC模式下，所述设备侧为所述转发路径经过的节点。
  15. 根据权利要求11所述的方法，其中，
    在PCC发起PCC-initiate模式或PCE发起PCE-initiate模式下，若为互联网协议/多协议标签交换IP/MPLS网络，通过在显示路径对象ERO对象中扩展的delay字段携带所述转发路径与所述转发时延信息；
    若为源路由SR网络，通过在SR-ERO对象中扩展的delay字段携带所述转发路径与所述转发时延信息；
    若为SRv6网络，通过在SRv6-ERO对象中扩展的delay字段携带所述转发路径与所述转发时延信息。
  16. 根据权利要求11所述的方法，其中，
    在PCE作为控制器PCECC模式下，通过在集中控制对象CCI对象中新增的TIME-SCHEDULING TLV携带所述转发路径与所述转发时延信息。
  17. 根据权利要求11所述的方法，其中，在所述设备侧接收所述控制器下发的所述转发路径与所述转发时延信息之前，所述方法还包括：
    作为PCC的所述设备侧与作为PCE的所述控制器进行基于时间调度的路径计算能力的协商。
  18. 根据权利要求17所述的方法，其中，
    在PCC发起PCC-initiate模式或PCE发起PCE-initiate模式下，若为互联网协议/多协议标签交换IP/MPLS网络，通过在路径计算单元通信PCEP协议中OPEN消息的OPEN对象扩展的比特T指示是否具有基于时间调度的路径计算能力；
    若为源路由SR网络，通过在所述PCEP协议中SR-PCE-CAPABILITY Sub-TLV扩展的比特T指示是否具有基于时间调度的路径计算能力；
    若为SRv6网络，通过在所述PCEP协议中SRv6-PCE-CAPABILITY Sub-TLV扩展的比特T指示是否具有基于时间调度的路径计算能力。
  19. 根据权利要求17所述的方法，其中，
    在PCE作为控制器PCECC模式下，通过在OPEN消息的PCECC CAPABILITY sub-TLV中扩展的比特T指示是否具有基于时间调度的路径计算能力。
  20. 一种路径计算装置，应用于控制器，包括：
    计算模块，设置为根据端到端时延需求计算转发路径及转发时延信息；
    下发模块，设置为下发所述转发路径与所述转发时延信息到设备侧。
  21. 一种路径计算装置，应用于设备侧，包括：
    接收模块，设置为接收控制器下发的转发路径与所述转发时延信息，其中，所述转发路径与所述转发时延信息是所述控制器根据端到端时延需求计算得到的。
  22. 一种计算机可读的存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行所述权利要求1至10、11至19任一项中所述的方法。
  23. 一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行所述权利要求1至10、11至19任一项中所述的方法。
PCT/CN2022/089969 2021-05-08 2022-04-28 一种路径计算方法、装置、存储介质及电子装置 Ceased WO2022237562A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US18/275,647 US12237992B2 (en) 2021-05-08 2022-04-28 Path computation method and apparatus, storage medium, and electronic device
EP22806531.4A EP4277424A4 (en) 2021-05-08 2022-04-28 PATH CALCULATION METHOD AND APPARATUS, STORAGE MEDIUM AND ELECTRONIC DEVICE

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110502498.1A CN115396360A (zh) 2021-05-08 2021-05-08 一种路径计算方法、装置、存储介质及电子装置
CN202110502498.1 2021-05-08

Publications (1)

Publication Number Publication Date
WO2022237562A1 true WO2022237562A1 (zh) 2022-11-17

Family

ID=84027999

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/089969 Ceased WO2022237562A1 (zh) 2021-05-08 2022-04-28 一种路径计算方法、装置、存储介质及电子装置

Country Status (4)

Country Link
US (1) US12237992B2 (zh)
EP (1) EP4277424A4 (zh)
CN (1) CN115396360A (zh)
WO (1) WO2022237562A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116016280A (zh) * 2022-12-26 2023-04-25 天翼安全科技有限公司 一种网络时延误差确定方法及装置
CN118474825A (zh) * 2023-02-08 2024-08-09 中兴通讯股份有限公司 卫星网络通信方法、装置、设备及介质
CN120455358A (zh) * 2024-02-08 2025-08-08 中兴通讯股份有限公司 业务路径建立方法、设备和存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108989065A (zh) * 2017-05-31 2018-12-11 中兴通讯股份有限公司 一种pcc请求算路失败的处理方法及装置
CN110677918A (zh) * 2018-07-03 2020-01-10 中国电信股份有限公司 链路状态信息转发方法、系统及装置
US10757012B2 (en) * 2014-12-23 2020-08-25 Telefonaktiebolaget Lm Ericsson (Publ) Path computation in a segment routing network
CN111970759A (zh) * 2019-05-20 2020-11-20 中兴通讯股份有限公司 端到端业务的时延调整方法及装置、存储介质和电子装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10581723B2 (en) * 2016-04-01 2020-03-03 Futurewei Technologies, Inc. PCEP extension for PCECC support of distributed computing, multiple services, and inter-domain routing
CN107547393B (zh) * 2016-06-29 2021-06-01 华为技术有限公司 一种计算转发路径的方法及网络设备
CN110474853B (zh) * 2018-05-11 2022-10-18 华为技术有限公司 一种报文发送的方法、网络节点和系统
CN112491709B (zh) * 2020-10-21 2025-06-20 中兴通讯股份有限公司 交叉SR/SRv6路径下发方法和装置、存储介质及电子装置
CN112532520B (zh) * 2020-10-28 2022-04-05 中盈优创资讯科技有限公司 基于pce的te-lsp的实现方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10757012B2 (en) * 2014-12-23 2020-08-25 Telefonaktiebolaget Lm Ericsson (Publ) Path computation in a segment routing network
CN108989065A (zh) * 2017-05-31 2018-12-11 中兴通讯股份有限公司 一种pcc请求算路失败的处理方法及装置
CN110677918A (zh) * 2018-07-03 2020-01-10 中国电信股份有限公司 链路状态信息转发方法、系统及装置
CN111970759A (zh) * 2019-05-20 2020-11-20 中兴通讯股份有限公司 端到端业务的时延调整方法及装置、存储介质和电子装置

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
CN115396360A (zh) 2022-11-25
US12237992B2 (en) 2025-02-25
EP4277424A4 (en) 2024-06-26
US20240297841A1 (en) 2024-09-05
EP4277424A1 (en) 2023-11-15

Similar Documents

Publication Publication Date Title
US12401569B2 (en) Network slicing including modeling, distribution, traffic engineering and maintenance
CN109257278B (zh) 用于非分段路由启用的路由器的分段路由标签交换路径方法
US8885463B1 (en) Path computation element communication protocol (PCEP) extensions for stateful label switched path management
EP3373530B1 (en) System and method for computing a backup egress of a point-to-multi-point label switched path
US20160006614A1 (en) Source Routing Using Path Computation Elements
CN102771096B (zh) 用于计算点到多点标签交换路径的备份入节点的系统和方法
US10382341B2 (en) Label switched path preemption avoidance
US20240314065A1 (en) Deterministic flow forwarding method and apparatus, storage medium and electronic apparatus
US9571381B2 (en) System and method for inter-domain RSVP-TE LSP load balancing
US9571387B1 (en) Forwarding using maximally redundant trees
WO2022237562A1 (zh) 一种路径计算方法、装置、存储介质及电子装置
EP4252399B1 (en) Methods, apparatus and system for creating sr policy using path computation element protocol
US8570871B2 (en) Signaling extension for a label switched path over a composite link
US20080144641A1 (en) Method and Device for Creating a Tunnel in a Label-Switched Telecommunication Network
US10547543B2 (en) Elegant temporal label switched path tunnel service controller
US20160308786A1 (en) Temporal Tunnel Services
CN106603412A (zh) 流规则发送的方法、路径计算单元和路径计算客户端
US9967179B2 (en) Constrained shortest path first for temporal tunnel services
CN108881017B (zh) 改变多路径标签交换路径中每跳带宽约束的方法及路由器
US9398553B2 (en) Technique for improving LDP-IGP synchronization
US9294416B2 (en) Method of and apparatus for configuring quality of service
WO2022083422A1 (zh) 交叉SR/SRv6路径下发方法和装置、存储介质及电子装置
US10554543B1 (en) Migrating data traffic between label switched paths (LSPs) based on per-LSP protocol priority value
WO2018054197A1 (en) Method and apparatus for path selecting
CN101094168A (zh) 路径计算单元的发现方法

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 18275647

Country of ref document: US

ENP Entry into the national phase

Ref document number: 2022806531

Country of ref document: EP

Effective date: 20230808

NENP Non-entry into the national phase

Ref country code: DE

WWG Wipo information: grant in national office

Ref document number: 18275647

Country of ref document: US