Case Study: Operational 4G/5G Cell Management
A controlled operational interface around a network-management API
The client's network operations team needed to find, inspect, lock, and unlock 4G and 5G cells through an established network-management platform. Its REST API exposed the underlying operations, but using it directly required locating cells within a telecoms managed-object hierarchy and interpreting responses where only part of a batch had succeeded. We built a domain-specific TypeScript API client and an Express interface around those behaviours.
Cell operations required more than direct REST requests
The client manages shared indoor 4G and 5G infrastructure across multiple mobile network operators. Routine maintenance and troubleshooting required selected cells to be placed out of service or returned to operation through the existing network-management platform.
Using the API directly required knowledge of its managed-object model. Cells had to be found within a hierarchy of network contexts and subnetworks. The 5G structure separated distributed-unit and central-unit cell objects, and a batch request could report that only some requested changes had succeeded.
The interface had to handle hierarchy and partial success
- Site-based searches had to resolve the network context and subnetworks before the relevant 4G or 5G cells could be addressed.
- Partial-success responses had to identify failed cells so they could be retried individually without repeating confirmed successes.
- 5G lock and unlock operations had to account for both distributed-unit and central-unit cell objects.
- Operations staff needed a web interface for search, current status, operator filtering, and cell actions rather than constructing API requests directly.
The API client kept platform-specific behaviour in one place
We built a TypeScript API client around the network-management platform's REST API. It encapsulated the platform's managed-object model, accepting a site identifier and resolving the corresponding network context, subnetworks and cell objects.
For batch responses marked as partially successful, the API client parsed the result, separated failed cells from successful ones, and retried the failed cells individually. This avoided treating a mixed result as either complete success or complete failure and retained the outcome of each requested cell operation.
An Express.js interface exposed site search, current administrative state, operator filtering, and lock or unlock controls. Keeping the hierarchy and response handling in the TypeScript API client meant the interface routes did not have to reconstruct platform-specific requests for each operation.
Routine cell operations through a production interface
The interface is used routinely in production for 4G and 5G cell search, status, lock, and unlock. Operations staff can work from a site and operator context while the TypeScript API client handles the platform-specific lookups needed to reach the relevant cells.
Partial-success handling keeps batch outcomes explicit. Confirmed changes are retained, while cells that were not changed are isolated for individual retry. The UI can then present the operation result without assuming that one API response represents one uniform outcome.
The same API client was later reused by the configuration-reporting pipeline to retrieve 5G cell attributes. Managed-object navigation and response handling remained within the integration rather than being rebuilt in the reporting application.
The same API client supported cell management and reporting
The project reduced reliance on the operational tools supplied with the network-management platform without replacing it or duplicating its responsibilities. Search and cell actions remained backed by its API. The purpose-built API client added the domain behaviour required by the client's cell-management workflow.
Reusing the API client for configuration reporting also kept the platform-specific hierarchy logic in one place. The reporting pipeline could request the attributes it needed without reproducing the complete cell-management workflow.
Related case studies:
- Network Performance Dashboards and Reporting over Sybase Data explains the production PostgreSQL access layer used for network-performance data.
- Automated Multi-Operator Report Delivery covers the reporting workflow that later reused this API client for configuration attributes.
Client names and identifying details have been withheld to protect confidentiality.
Need an operational interface around an existing platform?
Tell us which actions the platform exposes and what the operational workflow needs around them.
