Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Schema Proposal

  • For "network-resource", add string "network-type" attribute. (This has already been proposed for the CCVPN use case, we can reuse it to determine if its a OpenRoadM topology or OTN topology).
  • Add following attributes to "p-interface":

              i.  "network-interface-type" :   To indicate if that p-interface is a UNI, NNI or ENNI.

  • Add Edge Rule to represent "service-instance" to "p-interface" relationship to indicate the p-interfaces associated with that particular service. (Note: If we use the "service-instance" to "pnf" relationship, it becomes unclear as to which p-interface is used for that service, as a pnf can have many p-interfaces).

  • For "service-instance" following attributes are added :

              i.  "due-date": To indicate the due-date of the service.

              ii. "end-date" : To indicate the end date of the service.

              iii.  "service-rate" :  To indicate the service-rate.Eg 10GE.

              iv.  "service-layer" :  To indicate the service-layer. Eg: OTN.

  • Add Edge Rule to represent "esr-thirdparty-sdnc" to "network-resource" relationship to relate a group of network resources to a particular third party controller. For eg (Openroad topology and OTN topology could be related to a SDNC controller).

           




  • No labels