You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

The xApp descriptor is provided by the xApp writer. xApp Descriptor includes all the basic and essential information for the RIC platform to manage the life cycle of the xApp. Information and configuration included in the xApp descriptor will be used to generate the xApp helm charts and define the data flows to the north and south bound traffics. xApp developer can also include self-defined internal parameters that will be consumed by the xApp in the xApp descriptor.

The xApp descriptor comes with its JSON schema file that validates it. Please see the schema section about the details.

Structure:

The xApp descriptor follows a JSON structure. The following are the key sections that defines an xApp.

  • xapp_name: this is the unique identifier to address an xApp. A valid xApp descriptor must includes the xapp\_name attribute. The following is an example.

    xapp_name
    "xapp_name": "example_xapp",
  • ssd
  • ds



Layout: Describes how to present the xApp configurable parameters to the operator (in dashboard):

Hypothetical example:

"layout": [
      {
        "key": "controls.active",
        "title": "Active"
      },
      {
        "key": "controls.interfaceId.globalENBId",
        "title": "Global ENB Id"
      },
      {
        "type": "flex",
        "flex-flow": "row wrap",
        "items": [
          {
            "key": "controls.interfaceId.globalENBId.plmnid",
            "title": "Plmn Id"
          },
          {
            "key": "controls.interfaceId.globalENBId.id",
            "title": "Id"
          },
          {
            "key": "controls.interfaceId.globalENBId.bits",
            "title": "Bits“




  • No labels