NSP Generation of PCInitiate

  1. When the PCEP session is established from the PCC to PCE, the PCC and PCE exchange the Open object and both set the new ‟I flag, LSP-INSTANTIATION CAPABILITY” flag, in the STATEFUL-PCE-CAPABILITY TLV flag field.
  2. The operator, using the north-bound REST interface, the NSD or another interface, makes a request to the NSP to initiate an LSP.
    The following parameters are specified:

    1. source address

    2. destination address

    3. LSP type (SR-TE)

    4. bandwidth value

    5. include/exclude admin-group constraints

    6. optional PCE path profile ID for the path computation at the PCE

    7. optional PCE-initiated LSP template ID for use by the PCC to complete the instantiation of the LSP

  3. The NSP crafts the PCInitiate message and sends it to the PCC using PCEP.
    The message contains the LSP object with PLSP-ID=0, the SRP object, the ENDPOINTS object, the computed SR-ERO (SR-TE) object, and the list of LSP attributes (bandwidth object, one or more metric objects, and the LSPA object). The LSP path name is inserted into the Symbolic Path Name TLV in the LSP object.
  4. The PCE-initiated LSP template ID to be used at the PCC, if any, is included in the PATH-PROFILE-ID TLV of the Path Profile object.
    The Profile ID matches the PCE-initiated LSP template ID at the PCC and is not the same asThe Path Profile ID is used on the PCE to compute the path of this PCE-initiated LSP.
  5. The Path Profile ID is used on the PCE to compute the path of this PCE-initiated LSP.
Parent topic: LSP Instantiation Using PCEP