fiveg_gnb_identity

Relevant links

  Submit a bug

  Specification archive

Help us improve this page

Most of this content can be collaboratively discussed and changed in the respective README file.

Contribute

Discuss this interface

Share your thoughts on this interface with the community on discourse

Join the discussion

No charms found that Provide or Require fiveg_gnb_identity

Developer documentation

Usage

Within 5G, the gNodeB (a 5G base station) identity needs to be known by other components.

The fiveg_gnb_identity relation interface describes the expected behavior of any charm claiming to be able to provide or consume the gNodeB identity information.

In a typical 5G network, the provider of this interface would be a gNodeB. The requirer of this interface would be the NMS (Network Management System).

Direction

gNodeB Name, TAC

Provider

Requirer

As with all Juju relations, the fiveg_gnb_identity interface consists of two parties: a Provider and a Requirer.

Behavior

Both the Requirer and the Provider need to adhere to criteria to be considered compatible with the interface.

Provider

  • Is expected to provide the name of the gNodeB and TAC (Traking Area Code).

Requirer

  • Is expected to use the name of the gNodeB name and TAC (Traking Area Code).

Relation Data

[Pydantic Schema]

Last updated 13 days ago. Help us improve this page.