Nokia logo
DocumentationBlogPricing
Request access

Network as Code architecture and terminology

Architecture overview

Network as Code (NaC) platform consists of two main parts. Developer experience portal (where you are now) and runtime, which includes API transaction management and Network-as-Code services. Developers, like you, register through the portal, install the SDK and then integrate Network-as-Code capabilities and application keys into their applications. As a result, in runtime, those applications, wherever they are deployed, are able to communicate with networks (Network Operators and private networks) through Network-as-Code runtime and services, and that way change how networks handle application traffic and respective devices.

Right below, you will find some acronyms and terms that are commonly related to the Network as Code environment and its enablers.

Developer ecosystems and Edge

Network as Code abstracts the complex architecture behind the Edge Cloud and Network Operators, so that developers only need to worry about what really matters: fresh ideas to make the best out of their code!

  • Edge Cloud Cloud computing capabilities must be distributed across the network to meet the needs of 5G and Internet-of-Things (IoT) devices. With their ever-growing importance, low latency and high-bit rates have become vital in a competitive environment. Several cloud-based networks are already in service right now. That is why, Nokia Edge Cloud places computer resources where the traffic is: at the edge of the network.

  • Network Operators

    The owners of networks that can be used through NaC SDKs, which call APIs. Individuals or companies that provide support for their products, services and can help their customers with issues related to these.

  • Business to Customers and Business to Business (B2C and B2B) applications

    The different applications that can use Network as Code natively.

Network Exposure Function (NEF)

The relation between NEF and Network as Code is simple: NEF is a NaC enabler, it complements the Network-as-Code by providing Mobile as Code. Its main task is to expose information to applications in a reliable and safe way. It does that by abstracting capabilities from your core Network and allowing the creation of innovative services to address the needs of connected industries, smart cities, public safety and enterprises. Click here to learn more.

Slice orchestration and assurance

Although it is not necessary to detail these concepts deeply in order to use Network as Code, here is part of our enabling technology behind it:

  • Communication Service Management Function (CSMF)
  • Network Slice Management Function (NSMF)
  • Network Slice Subnet Management Function (NSSMF) for radio, transportation and 5G Core.

Last updated on July 31, 2023

On this page
Architecture overviewRelated acronyms and terminologyDeveloper ecosystems and EdgeNetwork Exposure Function (NEF)Slice orchestration and assurance