Page History

...

Service handler logic

proposal ongoing...

• service creation

  
  

  Image Added

  Brief explanation:

  • Upon receipt of service-create RPC, service header and sdnc-request header compliancy are verified.
  • If compliant, service-request parameters are verified in order to check if there is no missing parameter that prevents calculating a path and implement a service.
  • If OK, common-id is verified in order to see if there is no routing policy provided. If yes, the routing constraints of the policy are recovered and coherency with hard/soft constraints provided in the input of the RPC.
  • If OK, service due-time is verified. For any service to be activated later on, it is proposed to store them and wait for due-time to become equal to immediate (see xx). This behavior shall be improved in further release.
  • Before sending the PCE request, input data need to be formatted according to the Service Handler - PCE interface data model.
  • Once PCE request is being sent to the PCE on interface B, PCE reply is expected until a timer expires.
  • If PCE reply is received before timer expiration with a positive result, a service is created with admin and operational status 'down'.
  • A service implementation request is sent to the render on interface C.
  • If a positive message is received from the renderer, service admin / operational status is changed to 'up'.
  • For any case of failure, response-code, response message and ack-final-indicator shall be provided.

• service feasibility check

  Image Added

• service delete
  Image Added

• service modify:

one or several technical parameters are modified in service description

• service restore:

service has been reported to be down (for network issue) and a restoration is being requested

• service reversion:

return to nominal path is requested for a service previously rerouted/restored. This still requires to store nominal path. For a service being restored, only the new path path is stored (in the service model).

• non-permanent services management

• in-life service management

  :

services can be disturbed because of some network events. An OAM function in ODL controller is in charge of collecting network events, SLA measurements and updates services accordingly. Service notfications are then sent to any external function having subscribed to these notifications. However, OAM function is out of the scope of transportpce project.

• ...

Optical validation

This section gives an overview of how optical validation function is invoked in different implementations of the PCE.

...