TR255 Resource Function Activation and Configuration Suite

The TR255 series contains requirements, uses cases and protocol neutral models for an activation and configuration API concerning resource functions. Resource functions are a generalization and abstraction of various industry concepts including the ETSI NFV concepts of VNF, PNF VNF Forwarding Graph and Network Service, and the SDN concepts of Service Function and Service Function Chain. TR255 supports intent-based and detailed-based requests (as well as mixtures of intent-based and detailed-based).

TMF664 is an API based on the TR255 series. TMF664 is a key component in the Hybrid Infrastructure Platform (HIP) defined in TMF070B. HIP, in turn, is based on principles defined in TR262 Management Platform Blueprint and application to Hybrid Infrastructure R17.5.0. TR262 defines a platform-based model, supporting autonomic closed control loop resource managers. In order to support the principles in TR262, both intent-based and detailed-based options are defined in TR255 and realized in TMF664.

TR255 Entity Provisioning for Network Functions and Network Services:

  • TR255 includes use cases and requirements for the activation and configuration of Resource Functions (RF). Examples of RFs are VNFs and Network Services (as defined in ETSI NFV), Service Functions and Service Function Chains (as defined in IETF), and physical network functions such as routers and Content Delivery Networks (CDNs). The use cases and requirements where used to drive the definition of an associated TM Forum API, i.e., TMF664 Resource Function Activation and Configuration.
    • The use cases and requirements are divided into two basic kinds, i.e., intent-based and detailed-based. In the case of intent-based, the consumer does not have a view or the ability to directly affect the components of a given entity. For the detailed-based, the opposite is true.

There are several documents that support and further detail TR255, i.e.,

  • TR255A Connectivity Patterns for Virtualization Management – This document provides an analysis of several Resource Function (RF) examples from the perspective of connectivity needs. Recommendations are made concerning how to represent the details of connectivity for an RF. Adjacency graphs are used to model connectivity among RFs. The main target for this representation is the Resource Function Activation and Configuration API in TMF664.
  • TR255B Specification Requirements for Resource Functions – Using TR255 and TR255A as a basis, this document provides requirements for the specifications (descriptors) needed to support the activation and configuration of Resource Functions (RFs). The RF specification attributes are defined and a detailed example is provided (including a JSON representation in Appendix A).
  • TR255C TOSCA Representation of Virtual Firewall v2.0.1 – Using the Firewall example defined in TR255B as a basis, this document specifies the descriptors needed to support the provisioning of Resource Functions (RFs). The RF specification is defined using a TOSCA representation.

RN361 Release Notes for TR255 Resource Function Activation and Configuration v5.0 series provides the overview content of the TR255 series and will identify the specific changes introduced in this current release.