Versions Compared


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


    1. The heartbeat/healthcheck need to be much faster for telco app compared to regular non-telco microservices.
    2. Kubernetes supports the liveness/readiness which are in the orders of 10s of seconds. However, telco app needs sub second heartbeat check.
    3. Dynamic injections of configuration to the telco network functions required without restarting network functions.
    4. Typical network functions contains multiple smaller microservices to realize overall telco functionality. Health checks and monitoring should be across the components of the network function instead of individual PODs.
    5. Topology of a network function consisting of multiple microservices, how the traffic flowing across services is critical for the monitoring.
    6. Opportunities to generalize certain Telco specific functions such as subscriber tracing, Lawful Intercept (LI), CDR (Call Data Records), etc.

    7. The fault management service implements 3GPP compliant fault and alarm management model and provides interfaces for application µService to publish and subscribe to various events.

    8. Kubernetes does not meet fast HA requirements needed for certain Telco stateful services, whereas it provides overlay HA capability by supporting Active-Standby model in a distributed scalable fashion.

Gliffy Diagram