Skip to content

Signaling

Probe

Signaling Probe Unit 5G

built by slicce

Multi-protocol Real-time Monitoring on Cloud native environments

Signaling Probe Unit (SPU) delivers real-time, high-performance, high-density protocol monitoring in 5G mobile networks. The SPU enables applications to interrogate traffic between active signaling points in the network and trigger intelligent actions.

  • Monitor IPv4 and IPv6 links
  • Supports HTTP2, PFCP and SIP protocols
  • Built-in filtering mechanisms
  • Generate CDRs or webhooks

Create applications based on passive network monitoring

The SPU enables HTTP2, PFCP or SIP messages carried over IPv4 or IPv6 to be monitored. SCTP/TCP/UDP messages from one or more Ethernet ports can be selectively passed to a user application in real time.

Real-time monitoring: 

The advantage of the SPU is its powerful real-time monitoring capabilities. The SPU can monitor multiple Ethernet ports ports simultaneously. Users can choose which types of protocols to monitor, such as HTTP2, PFCP or SIP. The probe is configurable to immediately perform certain actions or send certain alerts to the user application in case it detects certain patterns of traffic, allowing networks to instantly react to issues in the network requiring immediate attention.

System Architecture

The SPU is a software probe, which can be installed on any standard physical server running linux or on any popular cloud service (virtual server).

System features

  • Monitors traffic over a kubernetes cluster, a virtual switch, a managed switch or a tapping device as defined by simple configuration settings.
  • Monitors multiple Ethernet ports simultaneously.
  • Monitors user-selected types from HTTP2, PFCP and SIP messages as well as those from specific network nodes.
  • Messages are delivered to user applications in configurable formats – with or without IP headers.
  • Detects traffic congestion and defers sending monitored messages until congestion abates.
  • Software solution installable on any system with Ethernet connectivity.
  • Various capacities are available to meet network density and throughput demands.
  • Can filter unwanted traffic, such as duplicated data chunks, management and traffic messages, to provide a clean information stream in real time.
Signaling Routing Service Communication Proxy Diameter Routing Engine Signaling Transfer Point Security Edge Protection Diameter Firewall SS7 Firewall Signaling Probe Unit Camel Gateway

Monitor critical traffic in a single kubernetes clusters

SPU is a monitoring tool designed to enhance security and observability within a Kubernetes cluster. It primarily monitors network traffic to track and analyze interactions between microservices, containers, and other components within the cluster.

One instance is deployed in each worker node of the cluster and an API is expose to interact with the microservices instances to execute packet captures, collect key performance indicators or generate call data records.

Collected data can be streamed to an external source, stored locally or be retreived via API.

SIngle SPU instance per worker node. SIngle SPU instance per worker node.

Monitor critical traffic accross kubernetes clusters

An API Gateway (CAPIF) can be used to aggregate multiple kubernetes clusters running SPU instances.

This bring the ability with a single API call to collect information accross all serving kubernetes clusters.

Here’s how it works and why it’s beneficial:

  • Aggregation Across Multiple Clusters: With CAPIF acting as a centralized gateway, it allows a single API call to pull information from all the Kubernetes clusters running SPU instances. This eliminates the need for individual services to query or interact with each cluster separately.
  • Simplified Troubleshooting: By centralizing access to all the Kubernetes clusters, CAPIF helps resolve the issue of applications needing to be aware of the location of specific subscribers or services. If troubleshooting is needed, CAPIF simplifies the process by providing an interface that can aggregate logs, metrics, and other relevant data from all clusters, regardless of where the issues are occurring.
  • Seamless Integration: CAPIF helps decouple the application logic from the infrastructure specifics, meaning applications don’t need to handle the complexity of interacting with multiple clusters. It also reduces the overhead of configuring and maintaining cross-cluster communication for tasks like troubleshooting or data collection.

This setup improves the efficiency and scalability of managing multiple Kubernetes clusters while also enabling a streamlined way of handling inter-cluster communication.

Aggregated SPU instance control with CAPIF-CF discovery. Aggregated SPU instance control with CAPIF-CF discovery.

functional specs

SIP stackRFC 3261 | SIP: Session initiation protocol RFC 3262 | SIP reliability (PRACK) RFC 3263 | SIP: locating SIP servers RFC 3264 | SDP offer/answer RFC 3265 | SIP-Specific event notification RFC 1321 | MD5: message digest algorithm RFC 2617 | HTTP authentication RFC 2806 | URLs for telephone calls RFC 2833 | RTP payload for DTMF & tones RFC 2915 | NAPTR: naming authority pointer RFC 2976 | SIP INFO method RFC 3204 | MIME objects for ISUP and QSIG RFC 3310 | HTTP digest authentication – AKA RFC 3311 | SIP update method RFC 3329 | Security mechanism for SIP RFC 3428 | SIP extension for IM RFC 3489 | STUN: Simple traversal UDP - NATs RFC 3515 | SIP refer method RFC 3581 | Symmetric response routing ext’n RFC 3665 | SIP basic call flow examples RFC 3711 | SRTP secure RTP RFC 3891 | SIP replaces header RFC 3903 | SIMPLE SIP for IM and presence RFC 4028 | Session timers in SIP RFC 4346 | TLS transport layer security RFC 4566 | SDP session descrip’n protocol/IPv6 RFC 4568 | SDP security for media streams
PFCP stackTS 129 244
API InterfaceHTTP/1.1, HTTPS, HTTP/2.0 or files

Let'sconnect

Telecom is our expertise