Aarna Networks Multi Cluster Orchestration Platform (AMCOP) version 3.3 is now available. Through orchestration, lifecycle management, real-time policy, and closed-loop automation capabilities, AMCOP provides zero touch edge orchestration and solves management complexity at scale. In this post, I’ll highlight the new features, improvements, and additions in the release.
SMO: Topology View for RAN Elements
For O-RAN deployment use cases, AMCOP provides Service Management and Orchestration (SMO) solutions. For the O-RAN Centralized Unit (CU), Distributed Unit (DU), and Open FH M-Plane specification for Radio Unit (RU), respectively, AMCOP SMO uses the O1 interface to perform FCAPS operations..
The new feature in 3.3 is to show the topology of disaggregated RAN elements (CU/DU/RU) in a graphical manner.
SMO: Configurable Colors for Alarm Notifications
AMCOP O-RAN SMO now supports alarm status color codes for different types of alarms.
There are 4 severity levels for the notifications defined in o-ran-fm.yang:
The AMCOP UI retrieves data and modifies the color schemes based on their priority, which enables the Operators to take appropriate actions accordingly (open loop).
ETSI SOL005 API Support for Fault Management
AMCOP now supports ETSI SOL005 implementation using a REST API. The resource representations are made in JSON and resource manipulation is made through CRUD(*) operations. Resources can be created using POST, read using GET, updated using PATCH/PUT, and deleted using DELETE.
This enables the users of AMCOP (especially at higher layer applications, such as OSS/BSS) to interface using the ETSI SOL005 standard.
SMO: Workflows for Configuration, RU Activation, and Cell Setup
AMCOP SMO now supports workflows that perform additional automation of RAN configuration, which needed to be done manually in earlier releases.
Once a session is established between an SMO and an O-RU (Radio Unit), a configuration push is done in order for the RU to be operational immediately, without any manual configuration. The following configuration is now handled automatically:
On receipt of sync status as LOCKED from an O-RU, the SMO triggers a cell setup request to the CU/DU automatically. On receipt of sync status as ERROR from O-RU, the SMO triggers a cell deactivate request to the CU/DU automatically. The SMO fetches the CU/DU based on the cell status and it triggers an activation request to the RU. If the cell is down and then comes up, the SMO activates the O-RU.
The latest version supports E2E testing of RU startup config push with SMO workflow yang modules. It also supports E2E testing of cell setup/active/inactive and E2E testing of RU active/inactive status.
Network Slicing Support (Non-shared Slices)
AMCOP network slicing solution supports 3GPP release v18 for various attributes involved in slicing solutions, as per the specifications TS 28.531 and TS 28.541.
This new feature of AMCOP supports the Network Slicing across all the 3 domains -- 5G Core, RAN, Transport -- and includes a sample BSS implementation that uses a REST API to drive the slice management logic in AMCOP. The feature is already integrated with open source implementations of 5GC and RAN, but it can be integrated with other vendors’ core and RAN implementations (commercial as well as open source).
In conclusion, the latest release of AMCOP v3.3 includes several new features, enhancements and bug fixes that enable it to orchestrate and manage multiple network elements and non-shared network slices with ease.