Release of Magma 1.2.0, platform for rapid deployment of LTE networks

Available platform release magma 1.2.0, designed for rapid deployment of components to ensure the operation of cellular networks 2G, 3G, 4G and 5G. The platform was originally developed by Facebook as part of initiatives to provide global network availability, but then turned into a separate project, transferred under the auspices of the independent non-profit organization OpenStack Foundation. The code is written in C, C++, Go and Python, and spreads under the BSD license.

The platform offers a new approach in the work of telecom operators based on the use of open software and allows you to create new types of networks that use a fast update cycle and continuous integration of software components. A key development goal of Magma was to attempt to create a platform for building efficient modern mobile networks that are compatible with existing LTE base station implementations and centrally managed through components running in private or public cloud environments.

The platform also provides automation tools that make deploying a core infrastructure as easy as running a Wi-Fi hotspot. Magma can be used in conjunction with traditional existing core networks (LTE core network) to expand their functionality in terms of launching new services and organizing a federation of different networks. With Magma, carriers limited to a licensed frequency range can expand network capacity or increase coverage in hard-to-reach areas using Wi-Fi and CBRS. For example, Magma can accelerate the deployment of a cellular network in rural areas, and can also be used to create private LTE networks or corporate wireless systems.

Magma includes tools for automating network deployment, management software, and core network components for packet delivery. To reduce the complexity of mobile network management, Magma offers tools to automate configuration, software updates, and adding new devices. The open nature of the project allows telecom operators to create solutions that are not tied to one equipment supplier, provides greater flexibility and predictability, and also provides more opportunities to add new services and applications.

Key Components Magma:

  • AGW (Access Gateway) is an access gateway that provides implementations of PGW (Packet Data Network Gateway), SGW (Serving Gateway), MME (Mobility Management Entity) and AAA (Authentication, Authorization and Accounting). The SGW processes and routes packets for base stations. PGW provides subscriber connection to external networks, performs packet filtering and billing. MME provides mobility, tracks the movement of the subscriber and performs migration between base stations. AAA provides network services for authentication, authorization and accounting of subscribers. Work with the existing equipment for cellular networks is supported.
  • Federation Gateway is a gateway for integration with the core network of mobile operators, using standard 3GPP interfaces to interact with existing network components. It acts as a proxy between the access gateway (AGW) and the network of the telecom operator, providing the operation of functions such as authentication, debiting funds, accounting and application of tariff plan restrictions.
  • Orchestrator is a cloud management service for configuring and monitoring a wireless network, including network performance analysis and traffic flow monitoring. A web interface is offered for management. Orchestrator can run in typical cloud environments. To interact with the AGW and the Federation Gateway, the protocol is used gRPC, running on top of HTTP/2.

Release of Magma 1.2.0, platform for rapid deployment of LTE networks

In the new release:

  • Significantly redesigned and expanded NMS (Network Management Station), a web interface for managing networks and deploying new networks. Many features in NMS now require Elasticsearch.
    Release of Magma 1.2.0, platform for rapid deployment of LTE networks

  • In the implementation of the AGW (Access Gateway) in the "Bridged Mode" expanded number of strategies for allocating IP addresses to users. Allocating IP from the pool, using DHCP and static IP assignment are available. Added experimental support for running multiple APN-SGi.
  • Added by support for customizable quality of service (QoS) management profiles to set traffic restriction policies. QoS settings can be configured for each APN that allows connections.

Source: opennet.ru

Add a comment