Skip to content
Telecom · Platform

Service Broker

One call may invoke an existing IN service, an IMS application and a business-system API. OVOO Service Broker coordinates their order, timeouts and fallback, so the applications work as one service chain.

SIP & SS7 mediationCarrier-grade

Control how applications share a call

Each application can make a valid decision on its own. The broker determines how those decisions combine in the complete call flow.

Compose the service chain

Define which TAS, IN and HTTP services a call invokes and in what order. Timeouts, retries and fallbacks belong to that chain rather than being left to each integration.

Resolve interactions between applications

A forwarding decision can conflict with a barring rule. Ordered rule sets determine which result takes precedence when several applications influence the call.

Coordinate policy and charging triggers

Place PCF/PCRF and OCS requests at the required decision points, including mid-call changes. The broker coordinates the sequence while those systems supply their own policy or charging decisions.

Connect signalling and IT interfaces

SIP/IMS and IN/CAMEL interfaces bring existing network services into the chain. HTTP and gRPC APIs connect the applications on the IT side.

Locate the rule behind an outcome

Trace a call through its chain and inspect the rules that ran. Per-chain logs, indicators and dashboards give operations a service-level view of the orchestration.

Test a chain before wider rollout

Shadow, canary and blue/green modes support controlled introduction of a new chain. Retain the audit trail and rollback path when promoting a change.

Connect the services your network already runs

The broker coordinates applications. Service execution, subscriber call services and charging remain with the platforms that own those functions.

JSLEE

JSLEE executes service logic through SBBs and resource adaptors. The broker can invoke those services or expose their flows as part of a wider chain; runtime migration is a separate JSLEE workstream.

TAS

TAS applies subscriber call services over SIP. The broker places TAS alongside other applications and resolves interactions at the service-chain level.

OCS / PCF

PCF/PCRF and OCS supply policy and charging decisions. The broker invokes the required hooks in the order defined for the service, including mid-call decision points.

Follow a request through the broker

A request enters through its network or application interface, runs through the configured chain and returns results to the consuming systems. Kubernetes hosts the broker; its APIs and events expose what happened.

Ingress & adaptors

Network-side SIP/IMS and IN/CAMEL meet application-side HTTP/gRPC adaptors. TLS, mTLS and token scopes define access to those interfaces.

Orchestration & FIR

The orchestration layer invokes each application, applies the interaction rules and follows the configured timeout or fallback path.

Exposure & ops

Northbound APIs and events expose the result. Traces and dashboards let the operations team follow the chain across its application boundaries.

Discuss a service chain