We need to define service characteristics for 3rd party services and many of the characteristics are of object type with child nodes for child attributes. 

e.g. 

bandwidth attribute can have child nodes upstream_speed, downstream_speed, unit and those child nodes can be of type enum will multiple values. see attached file

In SDC payload, we define the service specification in a single hierarchy. We would need a logic to map the child nodes to the parent node

Please refer attached jsons for an example. The JSONs are explained below:

1 - sampleObjPayload.json -

This json sample shows one service specification "bandwidth" of a service "access"

Datamodel:

bandwidth

        -type

        -downstream

        -upstream

        -units

The sample payload is in TMF633 service specification format depicting "bandwidth" as the ServiceSpecCharacteristic of type object. It has serviceSpecCharacteristicAttributes 'type', 'upstream', 'downstream' and 'units'. These attributes are of type enum in this sample. (they can be of type object too which will make it further complex)

2 - createService-samplePayload.json

This json sample shows the payload generated for creating a service in SDC for the above payload.

In this all the attributes are created as bandwidth_type, bandwidth_upstream, bandwidth_downstream and bandwidth_units. Once SDC receives these attributes, there will be logic needed to map the child attributes to their parent. Today there is no logic in SDC to map parent child relationship of such properties. So we will need introduce a logic to group these parameters under their parent bandwidth.

The existing classes for PropertyDefinition and ProperyDataDefinition do not allow us to create a mapping of properties between and child properties. The property types available in the SDC UI dropdown also do not have any type that can allow defining a property of type object composed of child properties in it