Section | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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 TAPI topology).
- Add following attributes to "p-interface":
i. "network-interface-type" : To indicate if that p-interface is a UNI, NNI or ENNI.
...
ii. "available-capacity" : To indicate the overall current capacity of the p-interface. The existing "speed-value" could be used to indicate the total capacity.
iii. "bandwidth-attributes" : Only for ENNI type p-interface. To capture the available bandwidth in terms of the composition of ODUs along with used and available time slots per ODU type. It consists of:
a. available-bandwidth: An array that indicates the number of available ODUs per ODU type
b. otn-label-restriction: Based on existing TE-Link resource type "label-restriction" to indicate Tributary Slots usage of available ODUs, per ODU type.
- Add following attributes to "logical-link":
i. "available-capacity" : To indicate the current capacity of the logical-link. The existing "speed-value" could be used to indicate the total capacity.
- Add following attributes to "esr-thirdparty-sdnc":
i. "domain-type" : To indicate the domain type of 3rd party domain controller. This will be updated by SDNC during topology discovery.
Add following attributes to "physical-link":
i. "available-capacity" : To indicate the current capacity of the physical-link. The existing "speed-value" could be used to indicate the total capacity.
ii. "admin-state" : To indicate the state of the physical-link. It could be "in-service , out-of-service" .
- For "service-instance" following attributes are added :
i. "due-date": To indicate the due-date of the service.
iii. "end-date" : To indicate the end date of the service.
iiii. . "service-rate" : To indicate the service-rate.Eg 10GE.
iiv. "service-layer" : To indicate the service-layer OTN. 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).
- 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)
Interested Parties
Viewtracker Report |
---|
...