Wan Connection
| R2+ Attributes | Qualifier | Cardinality | Content | label | Producer | Consumer |
|---|
| uuid | M | 1 | String(Identifier) | Identifier of Wan descriptor. | SDC | SDC/UUI/SDNC |
| name | O | 1 | String | Human readable name. | SDC | SDC/UUI/SDNC |
| label | O | 1..N | String | Additional infomation for Wan Descriptor. | SDC | SDC/UUI/SDNC |
| _fcDId | O | 1..N | String | References the end ports of FC. | SDC | SDC/UUI/SDNC |
| _fdDId | O | 1..N | String | References the Fds. | SDC | SDC/UUI/SDNC |
| _linkDId | O | 1..N | String | References the Links. | SDC | SDC/UUI/SDNC |
| _specificationDId | O | 1..N | String | References the specifications. | SDC | SDC/UUI/SDNC |
Forwarding Construct (FC)
| R2+ Attributes | Qualifier | Cardinality | Content | label | Producer | Consumer |
|---|
| uuid | M | 1 | String(Identifier) | Identifier of Fowarding Construct | SDC | SDC/UUI/SDNC |
| name | O | 1 | String | Human readable name for FC | SDC | SDC/UUI/SDNC |
| label | O | 1..N | String | Additional infomation for FC label | SDC | SDC/UUI/SDNC |
| _fcPortDId | M | 2..N | String | References the end ports of FC. Each end point is described by FC Port. | SDC | SDC/UUI/SDNC |
| _fcRouteDId | M | 0..N | String | References the fc route which describes the routing relationships within FC. | SDC | SDC/UUI/SDNC |
| _supportedLink | M | 0..N | String | An FC that spans between LTPs that terminate the LayerProtocol usually supports one or more links in the client layer. | SDC | SDC/UUI/SDNC |
| _specificationDId | M | 0..N | String | References the specify specification | SDC | SDC/UUI/SDNC |
FC Port
| R2+ Attributes | Qualifier | Cardinality | Content | label | Producer | Consumer |
|---|
| uuid | M | 1 | String(Identifier) | Identifier of Fowarding Construct Point | SDC | SDC/UUI/SDNC |
| name | O | 1 | String | Human readable name for FC Port | SDC | SDC/UUI/SDNC |
| label | O | 1..N | String | Additional infomation for FC Port label | SDC | SDC/UUI/SDNC |
| address | O | 0..N | String | One or more labels of the location. Such as Ip address or mac address or geo address. | SDC | SDC/UUI/SDNC |
| role | O | 1 | String | Each FcPort of the FC has an assigned role (e.g., working, protection, protected, symmetric, hub, spoke, leaf, root) in the context of the FC with respect to the FC function. | SDC | SDC/UUI/SDNC |
| fcPortDirection | O | 1 | String | The orientation of the defined flow at the FcPort. | SDC | SDC/UUI/SDNC |
| _ltpDId | M | 0..2 | String | References the ltp. The FcPort may be associated with more than one LTP when the FcPort is bidirectional and the LTPs are unidirectional. | SDC | SDC/UUI/SDNC |
| _specificationDId | M | 0..N | String | References the specify specification. | SDC | SDC/UUI/SDNC |
Forwarding Domain (FD)
| R2+ Attributes | Qualifier | Cardinality | Content | label | Producer | Consumer |
|---|
| uuid | M | 1 | String(Identifier) | Identifier of FD | SDC | SDC/UUI/SDNC |
| name | O | 1 | String | Human readable name for FD | SDC | SDC/UUI/SDNC |
| label | O | 1..N | String | Additional infomation for FD label | SDC | SDC/UUI/SDNC |
| address | O | 0..N | String | One or more labels of the location. | SDC | SDC/UUI/SDNC |
| _lowerLevelFd | M | 0..N | String | FD can be exposed as multiple lower level FDs. | SDC | SDC/UUI/SDNC |
| _ltpDId | M | 0..N | String | An instance of FD is associated with zero or more LTP objects. The LTPs that bound the FD provide capacity for forwarding. | SDC | SDC/UUI/SDNC |
| _specificationDId | M | 0..N | String | References the specify specification | SDC | SDC/UUI/SDNC |
FC Route
| R2+ Attributes | Qualifier | Cardinality | Content | label | Producer | Consumer |
|---|
| uuid | M | 1 | String(Identifier) | Identifier of FC Route | SDC | SDC/UUI/SDNC |
| name | O | 1 | String | Human readable name for FC Route | SDC | SDC/UUI/SDNC |
| label | O | 1..N | String | Additional infomation for FC Route label | SDC | SDC/UUI/SDNC |
| _fcDId | M | 0..N | String | References the lower level FCs which are internal construction of an FC. Lower level FC could belong to different domain. | SDC | SDC/UUI/SDNC |
| _link | M | 0..N | String | References the link which adjacency between two or more FD. | SDC | SDC/UUI/SDNC |
| _specificationDId | M | 0..N | String | References the specify specification | SDC | SDC/UUI/SDNC |
Logical Termination Point (LTP)
| R2+ Attributes | Qualifier | Cardinality | Content | label | Producer | Consumer |
|---|
| uuid | M | 1 | String(Identifier) | Identifier of LTP | SDC | SDC/UUI/SDNC |
| name | O | 1 | String | Human readable name for LTP | SDC | SDC/UUI/SDNC |
| label | O | 1..N | String | Additional infomation for LTP label | SDC | SDC/UUI/SDNC |
| physicalPortReference | O | 1 | String | The associated physical interface | SDC | SDC/UUI/SDNC |
| ltpDirection | O | 1 | String | The overall directionality of the LTP. | SDC | SDC/UUI/SDNC |
| _serverLtpDId | O | 0..N | String | References contained LTPs representing servers of this LTP in an inverse multiplexing specification. | SDC | SDC/UUI/SDNC |
| _clientLtpDId | O | 0..N | String | References contained LTPs representing client traffic of this LTP for normal cases of multiplexing. | SDC | SDC/UUI/SDNC |
| _specificationDId | M | 0..N | String | References the specify specification | SDC | SDC/UUI/SDNC |
Link
| R2+ Attributes | Qualifier | Cardinality | Content | label | Producer | Consumer |
|---|
| uuid | M | 1 | String(Identifier) | Identifier of Link | SDC | SDC/UUI/SDNC |
| name | O | 1 | String | Human readable name for Link | SDC | SDC/UUI/SDNC |
| label | O | 1..N | String | Additional infomation for Link label | SDC | SDC/UUI/SDNC |
| _fcDid | M | 0..1 | String | References FC which support the link | SDC | SDC/UUI/SDNC |
| _linkPortDId | M | 2..N | String | The association of the Link to LTPs is made via LinkPort. | SDC | SDC/UUI/SDNC |
| _specificationDId | M | 0..N | String | References the specify specification | SDC | SDC/UUI/SDNC |
LinkPort
| R2+ Attributes | Qualifier | Cardinality | Content | label | Producer | Consumer |
|---|
| uuid | M | 1 | String(Identifier) | Identifier of LinkPort | SDC | SDC/UUI/SDNC |
| name | O | 1 | String | Human readable name for LinkPort | SDC | SDC/UUI/SDNC |
| label | O | 1..N | String | Additional infomation for LinkPort label | SDC | SDC/UUI/SDNC |
| role | M | 1 | String | Each LinkPort of the Link has a role (e.g., symmetric, hub, spoke, leaf, root) in the context of the Link with respect to the Link capability. | SDC | SDC/UUI/SDNC |
| _ltpDId | M | 0..2 | String | References ltp. The LinkPort may be associated with more than one LTP when the LinkPort is bidirectional and the LTPs are unidirectional. | SDC | SDC/UUI/SDNC |
| _specificationDId | M | 0..N | String | References the specify specification | SDC | SDC/UUI/SDNC |
Specification Base
| R2+ Attributes | Qualifier | Cardinality | Content | label | Producer | Consumer |
|---|
| uuid | M | 1 | String(Identifier) | Identifier of specification | SDC | SDC/UUI/SDNC |
| name | O | 1 | String | Human readable name for specification | SDC | SDC/UUI/SDNC |
| label | O | 1..N | String | Additional infomation for specification label | SDC | SDC/UUI/SDNC |
| paras | M | 0..N | String | Specify parameters of the specification | SDC | SDC/UUI/SDNC |
| deployOrder | O | 1 | integer | Deploy order of the specification, smaller number means deploy first | SDC | SDC/UUI/SDNC |
| _subspecificationDId | M | 0..N | String | References the sub specification | SDC | SDC/UUI/SDNC |
Class Explain:
Wan Connection IM proposal
5 Comments
Andrei Kojukhov
Hello Maopeng,
Are you aware of ETSI GR NFV-IFA022 document defining the Use cases and Info Models for Multi-site WAN -based connectivity services?
Andrei
Zhuoyao Huang
Hi Andrei,
ETSI GR NFV-IFA22 presents multiple use cases about WAN, and I believe ONF CIM could cover all of them. According ETSI GR NFV-IFA22
6.4.5.3.2, new information elements are needed to specify the detail connectivity information on the WAN, and according NFV-IFA024, ONF CIM might be a good choice to fill the gap. So the proposal on this page is based on ONF CIM.
Jessie S Jewitt
Where can I find the class diagram with these classes in it? Also, where does this model come from? You have many concepts that are in the ONF Core model, though you define them differently.
Zhuoyao Huang
Hello Jessie,
Class diagram is in Wan Connection IM proposal.
Jessie S Jewitt
Regarding requested "call for comments", I repeat that this is not a "service" model and is a "resource" model, as confirmed by Nigel. It belongs in the RM project.