Solution for MNOs and MVNOs

3GPP architecture evolution, especially for IoT, offers Mobile Network Operators and Mobile Virtual Network Operators (MNOs and MVNOs) opportunities for revenue growth. The key to new revenue growth is to provide services, and charging Enterprises for use of the services. This new revenue is in addition to device subscription revenues.

Services can most effectively and efficiently be deployed as part of a Service Core, as illustrated below.

The operations/functions of the Packet Core and Service Core are quite different.

Packet Core:

  • 3GPP protocols
  • 3GPP connectivity
  • UE mobility
  • UE subscriptions

Service Core:

  • API management, API service, API routing
  • Services and applications
  • Device management and servers (e.g., LWM2M, MQTT Broker)
  • Policy enforcement (Enterprise SLAs)
  • Connectivity (3GPP and non-3GPP)
  • Data acquisition and storage

The SCEF (and 5G NEF) uses its 3GPP protocols to connect the Service Core to the necessary Packet Core nodes.

Standardization has provided great benefit to the Packet Core and the network nodes within the Packet Core. Standardization is lacking in the Service Core, and so integrating the Service Core network nodes provides a comprehensive solution.

By comparing the previous two illustrations, we see that the Integrated Solution includes these functions:

  • API Management, API Services, API Routing and CAPIF
  • SCEF and NEF
  • IoT Platform(s) and SCS(es)

Besides these functions, the Integrated Solution includes features that improve upon the services, such as, Traffic Flow Management and IoT Protocol Adaptation. These additional features allow service enablement without causing impact to the Operator’s network or adversely affecting the Enterprise applications and devices.

This Integrated Solution provides many benefits:

  • Centralized API solution, including SLAs with the Enterprise
  • Standard and custom interfaces with the Enterprise
  • 3GPP and non-3GPP access
  • Carrier-class services
  • New services, simple to add/modify without impacting the Enterprise or Packet Core

Moreover, the Integrated Solution is able to support a variety of business models, depending on the Operator requirements and deployed services. Models range from traditional licensing to subscription or usage-based models. In addition, capital expenditure by the Operator can be avoided, by deploying a revenue-share business model to divide the revenue between the Operator and the provider of the Integrated Solution.

Below, we illustrate how new or improved services can be rapidly deployed.

Above, we show how a new service instance can be easily added by the Operator. The Operator uses the Integrated Solution to route specific Enterprises to use the new service instance, and the Integrated Solution automatically converts the original APIs for the service to use the format required by the new service instance.

Quick link to jump back to the Definition Networks Home.