Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The distributed nature of model and data access raises the question of how will a data user know what data is available and where to get permission to access it.

This was driven from a 5G use case need: Model & Access Flows

Decision

Details

  1. µService A provides its model to the CPS
  2. µService A registers its model with the 'Registry Service'. The registration includes details of the owning service and meta data that can be used in queries for models
  3. µService A retrieves data from an xNF (e.g. PNF#106)
  4. µService A stores data related to the xNF (and compliant to the model) in the CPS
  5. µService B queries the registry to determine if (a) matching models exist and (b) which µServices own them
  6. 'Registry Service', provides a list of matching µServices
  7. µService B requests access to model and data from µService A
  8. µService A grants (or denies) access to models and data – E.g. permission in the form of a secure token
  9. µService B uses the permission (e.g. token) to access the CPS
  10. The CPS provides data related to the xNF compliant with the model

...