Open APIs

Hi,

I have read some marerials like gb922 product, service, and ig1228 use cases. So, what I understood about CFS, it is just abstraction layer that covers multiple RFSs in order to give intangible products. So, I need to confirm my understanding about it. RFSs are real service applications, cfs is just abstract expression to be given to customer. Is it right? Or can cfs be real service?

Hi Myagaa,
You are right. Basically, a CFS is an abstraction of a service that you give to your customers. It is technology-agnostic and related to products of the core commerce layer.
An RFS is a technical implementation for a service. A CFS can be realized by one or more RFSs. In turn, each RFS can use several resources for its implementation.
As you mentioned, IG1228 is a very good place to find many examples of catalog configurations that use this approach.
Hope it helps.
Best regards,

Hi,

I have read some marerials like gb922 product, service, and ig1228 use cases. So, what I understood about CFS, it is just abstraction layer that covers multiple RFSs in order to give intangible products. So, I need to confirm my understanding about it. RFSs are real service applications, cfs is just abstract expression to be given to customer. Is it right? Or can cfs be real service?

Hi Abel,

In service catalog, service spec (resource facing service spec) points array of resource spec. In my opinion, rfs can choose what resources will be used in order to activate the service. So, any rule is needed to choose the resources. Service spec contains constraint reference. Constraint can be policy. If I use policy as rule to choose what resources will be used, I can point the policy in the service spec. Because connections between service spec and resource spec has no policy reference, I couldn't point any policy on the resources. If service spec's reference of resource spec contains policy ref, I can set policy to choose the resource. How can I point the policy? Also, when specific rfs points policy to choose which resources will be used, if I add new resource reference in the service reference, the policy need to be handle the added resource. When I add resource spec ref in the service spec, I need to add logic. So how can it be catalog-driven?

Hi Myagaa,
You are right. Basically, a CFS is an abstraction of a service that you give to your customers. It is technology-agnostic and related to products of the core commerce layer.
An RFS is a technical implementation for a service. A CFS can be realized by one or more RFSs. In turn, each RFS can use several resources for its implementation.
As you mentioned, IG1228 is a very good place to find many examples of catalog configurations that use this approach.
Hope it helps.
Best regards,

Hi,

I have read some marerials like gb922 product, service, and ig1228 use cases. So, what I understood about CFS, it is just abstraction layer that covers multiple RFSs in order to give intangible products. So, I need to confirm my understanding about it. RFSs are real service applications, cfs is just abstract expression to be given to customer. Is it right? Or can cfs be real service?

Hi Myagaa,

You are correct. To the best of my knowledge, there is currently no standard method for defining policies within the relationships between specifications (e.g., RFS Spec to R Spec, or others). I can tell you that in the Alvatross service catalog, we have developed a method for defining decomposition rules tailored to the purposes you've described. This, however, is a custom extension we implemented.

It's possible that future versions of SID and APIs might include such features. Does anyone have further information or updates regarding this?

Best regards,

Hi Abel,

In service catalog, service spec (resource facing service spec) points array of resource spec. In my opinion, rfs can choose what resources will be used in order to activate the service. So, any rule is needed to choose the resources. Service spec contains constraint reference. Constraint can be policy. If I use policy as rule to choose what resources will be used, I can point the policy in the service spec. Because connections between service spec and resource spec has no policy reference, I couldn't point any policy on the resources. If service spec's reference of resource spec contains policy ref, I can set policy to choose the resource. How can I point the policy? Also, when specific rfs points policy to choose which resources will be used, if I add new resource reference in the service reference, the policy need to be handle the added resource. When I add resource spec ref in the service spec, I need to add logic. So how can it be catalog-driven?

Hi Myagaa,
You are right. Basically, a CFS is an abstraction of a service that you give to your customers. It is technology-agnostic and related to products of the core commerce layer.
An RFS is a technical implementation for a service. A CFS can be realized by one or more RFSs. In turn, each RFS can use several resources for its implementation.
As you mentioned, IG1228 is a very good place to find many examples of catalog configurations that use this approach.
Hope it helps.
Best regards,

Hi,

I have read some marerials like gb922 product, service, and ig1228 use cases. So, what I understood about CFS, it is just abstraction layer that covers multiple RFSs in order to give intangible products. So, I need to confirm my understanding about it. RFSs are real service applications, cfs is just abstract expression to be given to customer. Is it right? Or can cfs be real service?

Hi,

I have read some marerials like gb922 product, service, and ig1228 use cases. So, what I understood about CFS, it is just abstraction layer that covers multiple RFSs in order to give intangible products. So, I need to confirm my understanding about it. RFSs are real service applications, cfs is just abstract expression to be given to customer. Is it right? Or can cfs be real service?

Hi,

I have read some marerials like gb922 product, service, and ig1228 use cases. So, what I understood about CFS, it is just abstraction layer that covers multiple RFSs in order to give intangible products. So, I need to confirm my understanding about it. RFSs are real service applications, cfs is just abstract expression to be given to customer. Is it right? Or can cfs be real service?

Hi,

I have read some marerials like gb922 product, service, and ig1228 use cases. So, what I understood about CFS, it is just abstraction layer that covers multiple RFSs in order to give intangible products. So, I need to confirm my understanding about it. RFSs are real service applications, cfs is just abstract expression to be given to customer. Is it right? Or can cfs be real service?

Hi,

I have read some marerials like gb922 product, service, and ig1228 use cases. So, what I understood about CFS, it is just abstraction layer that covers multiple RFSs in order to give intangible products. So, I need to confirm my understanding about it. RFSs are real service applications, cfs is just abstract expression to be given to customer. Is it right? Or can cfs be real service?

Hi Myagaa,

Customer Facing Service(CFS) Spec describes the Service as understood by the customer.

CFS Spec characteristics comproises of:

·       Product characteristics needed to establish what needs to be delivered/fulfilled. e.g., Bandwidth of Internet Service, number of Static IP.

·       Resources assigned to Customer. e.g., Static IPs assigned to Customer. Configurations the customer might be able to do to use the Service per their needs. e.g., BGP

CFS is made up of one or more RFS.

Resource Facing Service(RFS) Spec describes the Service as in the network. RFS Spec abstracts/hides the technology details that are not relevant to customer. Reuse of the model and processes is also one of the consideration while modelling the RFS Spec, with-out compromising on the RFS Spec still depicting a Service.

RFS Spec characteristics comprises:

·       CFS characteristics to be provisioned/configured in the network. e.g., Bandwidth of Internet Service, Static IPs to be provisioned in the network, and BGP configuration. Any technical attributes needed to manage the resources and services in the network. e.g., Circuit ID

Hi,

I have read some marerials like gb922 product, service, and ig1228 use cases. So, what I understood about CFS, it is just abstraction layer that covers multiple RFSs in order to give intangible products. So, I need to confirm my understanding about it. RFSs are real service applications, cfs is just abstract expression to be given to customer. Is it right? Or can cfs be real service?

hi Srinivasa,

Based on your description it almost seems like 

1. The Customer Facing Service(CFS) Spec can be based on IETF's RFC 8299, YANG Data Model for L3VPN Service Delivery -where what how many (no technology)
2. The Resource Facing Service (RFS) Spec can be based on IETF's RFC 9182, YANG Network Data Model for Layer 3 VPNs -technology, but still vendor agnostic higher level -can be further transformed/mapped to individual vendor/openconfig config models

Would the above be correct please?

Hi Myagaa,

Customer Facing Service(CFS) Spec describes the Service as understood by the customer.

CFS Spec characteristics comproises of:

·       Product characteristics needed to establish what needs to be delivered/fulfilled. e.g., Bandwidth of Internet Service, number of Static IP.

·       Resources assigned to Customer. e.g., Static IPs assigned to Customer. Configurations the customer might be able to do to use the Service per their needs. e.g., BGP

CFS is made up of one or more RFS.

Resource Facing Service(RFS) Spec describes the Service as in the network. RFS Spec abstracts/hides the technology details that are not relevant to customer. Reuse of the model and processes is also one of the consideration while modelling the RFS Spec, with-out compromising on the RFS Spec still depicting a Service.

RFS Spec characteristics comprises:

·       CFS characteristics to be provisioned/configured in the network. e.g., Bandwidth of Internet Service, Static IPs to be provisioned in the network, and BGP configuration. Any technical attributes needed to manage the resources and services in the network. e.g., Circuit ID

Hi,

I have read some marerials like gb922 product, service, and ig1228 use cases. So, what I understood about CFS, it is just abstraction layer that covers multiple RFSs in order to give intangible products. So, I need to confirm my understanding about it. RFSs are real service applications, cfs is just abstract expression to be given to customer. Is it right? Or can cfs be real service?

Hi Adam,

Agree with your view, very nicely articulated and thank you for sharing the RFCs. Not sure the term "Delivery" would mean in "L3VPN Service Delivery". Service Models CFS/RFS are also meant to be used to assure(support service assurance processes) the Service in addition to deliver or fulfill the Service.

hi Srinivasa,

Based on your description it almost seems like 

1. The Customer Facing Service(CFS) Spec can be based on IETF's RFC 8299, YANG Data Model for L3VPN Service Delivery -where what how many (no technology)
2. The Resource Facing Service (RFS) Spec can be based on IETF's RFC 9182, YANG Network Data Model for Layer 3 VPNs -technology, but still vendor agnostic higher level -can be further transformed/mapped to individual vendor/openconfig config models

Would the above be correct please?

Hi Myagaa,

Customer Facing Service(CFS) Spec describes the Service as understood by the customer.

CFS Spec characteristics comproises of:

·       Product characteristics needed to establish what needs to be delivered/fulfilled. e.g., Bandwidth of Internet Service, number of Static IP.

·       Resources assigned to Customer. e.g., Static IPs assigned to Customer. Configurations the customer might be able to do to use the Service per their needs. e.g., BGP

CFS is made up of one or more RFS.

Resource Facing Service(RFS) Spec describes the Service as in the network. RFS Spec abstracts/hides the technology details that are not relevant to customer. Reuse of the model and processes is also one of the consideration while modelling the RFS Spec, with-out compromising on the RFS Spec still depicting a Service.

RFS Spec characteristics comprises:

·       CFS characteristics to be provisioned/configured in the network. e.g., Bandwidth of Internet Service, Static IPs to be provisioned in the network, and BGP configuration. Any technical attributes needed to manage the resources and services in the network. e.g., Circuit ID

Hi,

I have read some marerials like gb922 product, service, and ig1228 use cases. So, what I understood about CFS, it is just abstraction layer that covers multiple RFSs in order to give intangible products. So, I need to confirm my understanding about it. RFSs are real service applications, cfs is just abstract expression to be given to customer. Is it right? Or can cfs be real service?

Folks we do have some general guidance about Product Service model published in: 

IG1233 Product & Service Modelling Best Practices update to support B2B Use Cases v3 (E2E-167) - End to end ODA - TM Forum Confluence

There is also an unpublished document on RFS resource modelling available to members 

ODA Solution Design: "vertical" Product / Service Resource /Guideline: How to model sellable product offerings including service and resource specification with ODA and the TM Forum Information Framework - End to end ODA - TM Forum Confluence

We do also have some document publishing modelling proposal for specific technologies such as:

IG1211 ODA 5G Management Implementation Guidelines v1.0.1 – TM Forum

For members there is a updated discussion of this specific technology at:

Modelling for 3GPP Network Slice Use Case - Components and Canvas - TM Forum Confluence

 
what I am wondering is if we could do with public web page where we can published worked examples of extensions?

Hi Adam,

Agree with your view, very nicely articulated and thank you for sharing the RFCs. Not sure the term "Delivery" would mean in "L3VPN Service Delivery". Service Models CFS/RFS are also meant to be used to assure(support service assurance processes) the Service in addition to deliver or fulfill the Service.

hi Srinivasa,

Based on your description it almost seems like 

1. The Customer Facing Service(CFS) Spec can be based on IETF's RFC 8299, YANG Data Model for L3VPN Service Delivery -where what how many (no technology)
2. The Resource Facing Service (RFS) Spec can be based on IETF's RFC 9182, YANG Network Data Model for Layer 3 VPNs -technology, but still vendor agnostic higher level -can be further transformed/mapped to individual vendor/openconfig config models

Would the above be correct please?

Hi Myagaa,

Customer Facing Service(CFS) Spec describes the Service as understood by the customer.

CFS Spec characteristics comproises of:

·       Product characteristics needed to establish what needs to be delivered/fulfilled. e.g., Bandwidth of Internet Service, number of Static IP.

·       Resources assigned to Customer. e.g., Static IPs assigned to Customer. Configurations the customer might be able to do to use the Service per their needs. e.g., BGP

CFS is made up of one or more RFS.

Resource Facing Service(RFS) Spec describes the Service as in the network. RFS Spec abstracts/hides the technology details that are not relevant to customer. Reuse of the model and processes is also one of the consideration while modelling the RFS Spec, with-out compromising on the RFS Spec still depicting a Service.

RFS Spec characteristics comprises:

·       CFS characteristics to be provisioned/configured in the network. e.g., Bandwidth of Internet Service, Static IPs to be provisioned in the network, and BGP configuration. Any technical attributes needed to manage the resources and services in the network. e.g., Circuit ID

Hi,

I have read some marerials like gb922 product, service, and ig1228 use cases. So, what I understood about CFS, it is just abstraction layer that covers multiple RFSs in order to give intangible products. So, I need to confirm my understanding about it. RFSs are real service applications, cfs is just abstract expression to be given to customer. Is it right? Or can cfs be real service?