Discover and Reconciliation Interface Guide

Discover and Reconciliation interface Guide Overview

In this guide, we explore how to use the Discover and Reconciliation interface API to enrich Topology & Inventory with geographical data.

Geographical enrichment

Discover and Reconciliation is the adding, modifying, and removing of geographical entities that supports geographical information. Geographical entities are associated to topology data. The following geographical entities support geographical enrichment:

  • Sector

  • AntennaModule

  • Site

For information on the entity types and their supported relationships, see the Data Models.

The format of the geographical enrichment message is CloudEvents. Topology & Inventory uses CloudEvents Kafka® version 2.5.x. The link provides a sample CloudEvents implementation in Java®. CloudEvents SDKs also supports other languages. See CloudEvents.

The “data” element consists of the actual topology and inventory data. It contains all the geographical entities and their associated relationships in application/json format, and each entity and relationships are represented in application/yang-data+json format.

CloudEvents attributes are validated against the Data Models. If there is an unknown attribute in the CloudEvents, Topology & Inventory does not drop the whole event but parses and persists only valid attributes, and unknown parts are logged and ignored. If an empty or bad payload is sent, the data is not persisted.

The value of non-mandatory fields can be deleted by sending a merge request to set it to null. Null means that the value is not set.

Example of enrich Topology & Inventory with geographical data

This example creates a new topology Site entity and a relationship between the Site and an AntennaModule. Using the create schema the data producer can create entities that support geographical enrichment. Attributes with null means not set.

{
    "ce_specversion": "1.0",
    "ce_id": "a30e63c9-d29e-46ff-b99a-b63ed83fd233",
    "ce_source": "dmi-plugin:nm-1",
    "ce_type": "topology-inventory-ingestion-create",
    "ce_time": "2023-06-12T09:05:00Z",
    "content-type": "application/json",
    "ce_dataschema": "topology-inventory-ingestion:events:create:1.0.0",
    "data": {
      "entities": [
        {
          "o-ran-smo-teiv-equipment:Site": [
            {
              "id": "urn:o-ran:smo:teiv:sha512:Site=1F137533843657E9E9DBE60DBD86B045A057DB6D04B6A07AC153",
              "attributes": {
                "name": "Dublin",
                "location": {
                  "geo-location": {
                    "latitude": 41.73297,
                    "longitude": -73.007696
                  }
                }
              }
            }
          ]
        },
        {
          "o-ran-smo-teiv-equipment:AntennaModule": [
            {
              "id": "urn:o-ran:smo:teiv:sha512:AntennaModule=1FEBF137533843657E9E9DBE60DBD86B045A057DB6D04B6A07AC15323F1906228E93CFA4A1DB37D50252B3AFE6AEC9860E2CEA4A77BB3A25C9EA45DEDA87E765",
              "attributes": {
                "geo-location": {
                  "latitude": 41.73297,
                  "longitude": -73.007696
                }
              }
            }
          ]
        }
      ],
      "relationships": [
        {
          "o-ran-smo-teiv-equipment:ANTENNAMODULE_INSTALLED_AT_SITE": [
            {
              "id": "urn:o-ran:smo:teiv:sha512:ANTENNAMODULE_INSTALLED_AT_SITE=TlJDZWxsRFU6U3ViTmV0d29yaz1FdXJvcGUsU3ViTmV0d29yaz1JcmVs=",
              "aSide": "urn:o-ran:smo:teiv:sha512:AntennaModule=1FEBF137533843657E9E9DBE60DBD86B045A057DB6D04B6A07AC15323F1906228E93CFA4A1DB37D50252B3AFE6AEC9860E2CEA4A77BB3A25C9EA45DEDA87E765",
              "bSide": "urn:o-ran:smo:teiv:sha512:Site=1F137533843657E9E9DBE60DBD86B045A057DB6D04B6A07AC153"
            }
          ]
        }
      ]
    }
}

Example of modify enriched Topology & Inventory with geographical data

This example updates an existing Site entity. Using the merge schema the data producer can update entities that support geographical enrichment.

{
  "ce_specversion": "1.0",
  "ce_id": "a30e63c9-d29e-46ff-b99a-b63ed83fd234",
  "ce_source": "dmi-plugin:nm-1",
  "ce_type": "topology-inventory-ingestion-merge",
  "ce_time": "2023-06-12T09:05:00Z",
  "content-type": "application/json",
  "ce_dataschema": "topology-inventory-ingestion:events:merge:1.0.0",
  "data": {
    "entities": [
      {
        "o-ran-smo-teiv-equipment:Site": [
          {
            "id": "urn:o-ran:smo:teiv:sha512:Site=1F137533843657E9E9DBE60DBD86B045A057DB6D04B6A07AC153",
            "attributes": {
              "name": "Dublin",
              "location": {
                "geo-location": {
                  "latitude": 52.73297,
                  "longitude": -84.007696
                }
              }
            }
          }
        ]
      },
      {
        "o-ran-smo-teiv-equipment:AntennaModule": [
          {
            "id": "urn:o-ran:smo:teiv:sha512:AntennaModule=1FEBF137533843657E9E9DBE60DBD86B045A057DB6D04B6A07AC15323F1906228E93CFA4A1DB37D50252B3AFE6AEC9860E2CEA4A77BB3A25C9EA45DEDA87E765",
            "attributes": {
              "geo-location": {
                "latitude": 52.73297,
                "longitude": -84.007696
              }
            }
          }
        ]
      }
    ],
    "relationships": [
      {
        "o-ran-smo-teiv-equipment:ANTENNAMODULE_INSTALLED_AT_SITE": [
          {
            "id": "urn:o-ran:smo:teiv:sha512:ANTENNAMODULE_INSTALLED_AT_SITE=TlJDZWxsRFU6U3ViTmV0d29yaz1FdXJvcGUsU3ViTmV0d29yaz1JcmVs=",
            "aSide": "urn:o-ran:smo:teiv:sha512:AntennaModule=1FEBF137533843657E9E9DBE60DBD86B045A057DB6D04B6A07AC15323F1906228E93CFA4A1DB37D50252B3AFE6AEC9860E2CEA4A77BB3A25C9EA45DEDA87E765",
            "bSide": "urn:o-ran:smo:teiv:sha512:Site=1F137533843657E9E9DBE60DBD86B045A057DB6D04B6A07AC153"
          }
        ]
      }
    ]
  }
}

Example of delete enriched data from Topology & Inventory

This example deletes a topology Site entity and its relationship to an AntennaModule entity. Using the delete schema the data producer can delete entities that support geographical enrichment.

{
    "ce_specversion": "1.0",
    "ce_id": "a30e63c9-d29e-46ff-b99a-b63ed83fd235",
    "ce_source": "dmi-plugin:nm-1",
    "ce_type": "topology-inventory-ingestion-delete",
    "ce_time": "2023-06-12T09:05:00Z",
    "content-type": "application/json",
    "ce_dataschema": "topology-inventory-ingestion:events:delete:1.0.0",
    "data": {
        "entities" : [
          {
            "o-ran-smo-teiv-equipment:Site": [
                {
                    "id": "urn:o-ran:smo:teiv:sha512:Site=1F137533843657E9E9DBE60DBD86B045A057DB6D04B6A07AC153"
                }
            ]
          }
        ],
        "relationships": [
          {
            "o-ran-smo-teiv-equipment:ANTENNAMODULE_INSTALLED_AT_SITE": [
                {
                    "id" : "urn:o-ran:smo:teiv:sha512:ANTENNAMODULE_INSTALLED_AT_SITE=TlJDZWxsRFU6U3ViTmV0d29yaz1FdXJvcGUsU3ViTmV0d29yaz1JcmVs="
                }
            ]
          }
        ]
    }
}

How to create and produce an event

To create and produce an event, you can use the CloudEventBuilder.v1 and KafkaProducer. The link provides a sample CloudEvents implementation in Java. CloudEvents SDKs also supports other languages. See CloudEvents.

Understanding Topology & Inventory id

When performing geographical enrichment of entities, the id value of the data, that is being enriched in Topology & Inventory, must match the id value for the entity or the relationship within the CloudEvent data element.

There are two types of entities:

  • Entities that can be derived directly from CM. In the Topology & Inventory, these entities have only one instance with the prefix urn:3gpp:dn: within the sourceIds list. Use this value as the entity id value within the CloudEvents data element.

  • Composite entities are entities that cannot be derived directly from CM. These entities have multiple instances of urn:3gpp:dn: within the sourceIds list. The entity id value must be constructed from the list of elements in the sourceIds list.

The following is a sample CloudEvent for enriching an entity with geographical location information.

Sample data for geographical enriching CloudEvent

  1. The list values for sourceIds is used to create the entity id.

  2. The id is used to identify the correct entity.

  3. Geographical information enriches the entity.

  4. The relationship id is created from the aSide and bSide values which are the entity id’s.

To get the id values for composite entities, the advised method is to query the entities for matching sourceIds elements, see Topology & Inventory API. This can result in several matches where the same source entity participates in multiple topology entities. Otherwise, the entity id value and relationship id value are created as follows:

How to create a composite entity id

Composite entities are derived from multiple source domain elements.

  1. Get sourceIds of the composite entity.

Example:

"sourceIds": [
   "urn:3gpp:dn:SubNetwork=Europe,SubNetwork=Ireland,MeContext=NR004,ManagedElement=me04,Equipment=1,AntennaUnitGroup=1,AntennaUnit=1",
   "urn:3gpp:dn:SubNetwork=Europe,SubNetwork=Ireland,MeContext=NR004,ManagedElement=me04,Equipment=1,AntennaUnitGroup=1,AntennaUnit=1,AntennaSubunit=1",
   "urn:3gpp:dn:SubNetwork=Europe,SubNetwork=Ireland,MeContext=NR004,ManagedElement=me04,Equipment=1,AntennaUnitGroup=1,AntennaNearUnit=1,RetSubUnit=12"
]

  1. In the given order, combine each id with the prefix urn:3gpp:dn only. Separate the id’s with ;.

Format:

<urn:3gpp:dn:Entity1>;<urn:3gpp:dn:Entity2>;...;<urn:3gpp:dn:EntityN>

Example:

urn:3gpp:dn:SubNetwork=Europe,SubNetwork=Ireland,MeContext=NR004,ManagedElement=me04,Equipment=1,AntennaUnitGroup=1,AntennaUnit=1;
urn:3gpp:dn:SubNetwork=Europe,SubNetwork=Ireland,MeContext=NR004,ManagedElement=me04,Equipment=1,AntennaUnitGroup=1,AntennaUnit=1,AntennaSubunit=1;
urn:3gpp:dn:SubNetwork=Europe,SubNetwork=Ireland,MeContext=NR004,ManagedElement=me04,Equipment=1,AntennaUnitGroup=1,AntennaNearUnit=1,RetSubUnit=12

  1. SHA-512 hash the combined id’s.

Example:

1FEBF137533843657E9E9DBE60DBD86B045A057DB6D04B6A07AC15323F1906228E93CFA4A1DB37D50252B3AFE6AEC9860E2CEA4A77BB3A25C9EA45DEDA87E765

  1. Add the prefix urn:o-ran:smo:teiv:sha512: and the composite entity name = SHA-512 hashed id’s.

Format:

urn:o-ran:smo:teiv:sha512:<CompositeEntityName>=<SHA-512 hashed IDs>

Example:

urn:o-ran:smo:teiv:sha512:AntennaModule=1FEBF137533843657E9E9DBE60DBD86B045A057DB6D04B6A07AC15323F1906228E93CFA4A1DB37D50252B3AFE6AEC9860E2CEA4A77BB3A25C9EA45DEDA87E765

How to create a relationship id

  1. Combine the id of aSide and the id of bSide, split by the relationshipType, in the format:

<aSideID>:<relationshipType>:<bSideID>

Example:

urn:3gpp:dn:SubNetwork=Europe,SubNetwork=Ireland,SubNetwork=ERBS01,ManagedElement=me01:
MANAGEDELEMENT_MANAGES_ENODEBFUNCTION:
urn:3gpp:dn:SubNetwork=Europe,SubNetwork=Ireland,SubNetwork=ERBS01,ManagedElement=me01,ENodeBFunction=1

  1. SHA-512 hash the previous format.

Example:

6D7E2A09E0F10C09548F86519084FDF1F021561FF07E116136D118E93568A0B4EA968A4B1E02B2CA4E057E00E582273DBE5A8CA1BF910FC65A9101117A0E9D7F

  1. Add the prefix urn:o-ran:smo:teiv:sha512: and the relationship type = the SHA-512 hashed as follows:

urn:o-ran:smo:teiv:sha512:<RelationshipType>=<SHA-512 hash>

Example:

urn:o-ran:smo:teiv:sha512:MANAGEDELEMENT_MANAGES_ENODEBFUNCTION=6D7E2A09E0F10C09548F86519084FDF1F021561FF07E116136D118E93568A0B4EA968A4B1E02B2CA4E057E00E582273DBE5A8CA1BF910FC65A9101117A0E9D7F

Troubleshooting

If CloudEvents were sent but no data was persisted, check validation failures and logs. Update the CloudEvent based on the logs and send it again.