Management Plane

gRPC is the operator and local-service transport. It is used for diagnostics, operator actions, web UI integration, HLR/SMSC/packet service boundaries, and the MSC-controlled voice gateway streams. Standards interfaces such as Abis, A1, A2p, A8/A9, and A10/A11 do not ride on gRPC.

Management plane diagram

Current Topology

Today there is one primary management facade at 127.0.0.1:17016 for 1xbts-web and compatibility tooling. The MSC runtime hosts its own management listener at 127.0.0.1:17017; HLR, SMSC, and packet services also run behind local gRPC boundaries that the facade/runtime proxies reach as clients.

Service	Current Endpoint	Role
`management.v1.ManagementFacadeService`	`:17016`	system overview and aggregated event stream
`bts_management.v1.BtsManagementService`	`:17016`	radio metrics, IQ capture, local radio resources, reverse power-control diagnostics
`bsc_management.v1.BscManagementService`	`:17016`	mobiles, channels, access/paging/traffic event streams, BSC status
`msc_management.v1.MscManagementService`	MSC `:17017` with facade compatibility on `:17016`	initiate/list calls and SMS submission; MSC owns SMS coordination via A1 ADDS to BSC
`pcf_management.v1.PcfManagementService`	`:17016`	packet-data radio-edge sessions and data-call actions
`pdsn_management.v1.PdsnManagementService`	`:17016`	packet-core sessions and packet trace capture
`bsc.v1.BscService`	`:17016`	compatibility API for existing web routes
`hlr.v1.HlrService`	HLR `:17019` with facade compatibility on `:17016`	subscriber and registration persistence API
`smsc.v1.SmscService`	SMSC `:17020` with facade compatibility on `:17016`	SMS submission and delivery persistence API
`packet.v1.PacketService`	packet `:17021` with facade compatibility on `:17016`	packet session service

The target state is one node-owned management or service endpoint per node, with the facade aggregating them for 1xbts-web.

Management Ownership

Feature	Owning API
IQ capture and radio metrics	`BtsManagementService`
mobile list, channel list, access/paging/traffic streams	`BscManagementService`
MT call initiation, call listing, SMS submission, and MSC-owned voice gateway policy	`MscManagementService`
packet-data call initiation and PCF sessions	`PcfManagementService`
packet-core sessions and packet trace capture	`PdsnManagementService`
subscriber CRUD and identity resolution	`HlrService` on `:17019`, proxied by compatibility routes
SMS history and submissions	`SmscService` on `:17020` for storage; `MscManagementService` on `:17017` for new submissions

Dashboard Integration

1xbts-web talks to the management endpoint from Next.js API routes. Browser clients receive SSE streams from the web server; they do not open raw gRPC connections.

Browser -> 1xbts-web (:3000) -> management facade (:17016)
                         \-> MSC management (:17017) for MSC-owned actions
                         \-> HLR/SMSC/packet services (:17019/:17020/:17021) through facade/runtime clients
      <- SSE metrics/events  <- aggregated node events

Set MANAGEMENT_GRPC_ADDRESS for the facade endpoint. BSC_GRPC_ADDRESS remains a compatibility fallback in the web client.

Common grpcurl Calls

grpcurl -plaintext localhost:17016 management.v1.ManagementFacadeService/GetSystemOverview
grpcurl -plaintext localhost:17016 bts_management.v1.BtsManagementService/GetRadioMetrics
grpcurl -plaintext localhost:17016 bsc_management.v1.BscManagementService/ListMobiles
grpcurl -plaintext localhost:17017 msc_management.v1.MscManagementService/ListCalls
grpcurl -plaintext localhost:17019 hlr.v1.HlrService/ListSubscribers
grpcurl -plaintext localhost:17020 smsc.v1.SmscService/ListSmsSubmissions