How openairinterface/oai-cn5g-sepp works
This repository implements the OpenAirInterface Security Edge Protection Proxy (SEPP), a 5G Core network element. Its main workflow is to accept N32-c handshake and N32-f forwarding requests over its SBI/NBI HTTP servers, dispatch them through the SEPP application, and perform handshake, forwarding, or mapping work; it also maintains SEPP profile/NRF lifecycle functions. Startup wiring and key API dispatch are visible in excerpts, while several capability links rely on documented handlers or remain unverified because their implementations were not sampled.
Main entry points: sepp_app.cpp Application dispatch · sepp-http2-nbi-server.cpp NBI HTTP/2 · main.cpp Process startup · sepp-http2-sbi-server.cpp SBI HTTP/2
Components 21
Runtime and HTTP
- Process startup
src/oai_sepp/main.cpp - SEPP configuration
src/sepp_app/sepp_config.hpp - NBI HTTP/2
src/api-server/sepp-http2-nbi-server.cpp - SBI HTTP/2
src/api-server/sepp-http2-sbi-server.cpp - HTTP/1 API
src/api-server/sepp-api-server.cpp - Application dispatch
src/sepp_app/sepp_app.cpp - Event handling
src/sepp_app/sepp_event.cpp - Task scheduler
src/sepp_app/task_manager.cpp - Runtime options
src/oai_sepp/options.cpp
N32 Procedures
- N32-c handshake
src/sepp_app/sepp_n32c_handshake.cpp - N32-f forwarding
src/sepp_app/sepp_n32f_forward.cpp - JOSE security
src/sepp_app/sepp_JOSE.cpp - Context termination API
src/api-server/api/N32FContextTerminateApi.cpp - Error reporting API
src/api-server/api/N32FErrorReportApi.cpp - Capability exchange API
src/api-server/api/SecurityCapabilityNegotiationApi.cpp - Parameter exchange API
src/api-server/api/ParameterExchangeApi.cpp - Mapping document API
src/api-server/api/TelescopicMappingDocumentApi.cpp
SEPP Operations
- NRF integration
src/sepp_app/sepp_nrf.cpp - SEPP profile
src/sepp_app/sepp_profile.cpp - Telescopic FQDN mapping
src/sepp_app/sepp_telescopic_fqdn_mapping.cpp
Other components
- Network peer
Connections 26
- Network peer → NBI HTTP/2: sends requests
- Network peer → SBI HTTP/2: sends requests
- Process startup → Runtime options: parses options
src/oai_sepp/main.cpp - Process startup → SEPP configuration: initializes
src/oai_sepp/main.cpp - Process startup → Application dispatch: creates
src/oai_sepp/main.cpp - Process startup → NBI HTTP/2: starts
src/oai_sepp/main.cpp - Process startup → SBI HTTP/2: starts
src/oai_sepp/main.cpp - Process startup → HTTP/1 API: starts when HTTP/1
src/oai_sepp/main.cpp - Process startup → Task scheduler: starts
src/oai_sepp/main.cpp - NBI HTTP/2 → Application dispatch: dispatches handlers
src/api-server/sepp-http2-nbi-server.cpp - SBI HTTP/2 → Application dispatch: dispatches handlers
src/api-server/sepp-http2-sbi-server.cpp - HTTP/1 API → Application dispatch: uses application
- Application dispatch → N32-c handshake: delegates handshake
- Application dispatch → N32-f forwarding: delegates forwarding
- Application dispatch → NRF integration: uses NRF lifecycle
- Application dispatch → SEPP profile: maintains profile
- Application dispatch → Telescopic FQDN mapping: queries mappings
- N32-f forwarding → JOSE security: uses JOSE
src/sepp_app/sepp_n32f_forward.cpp - Task scheduler → Event handling: ticks events
src/sepp_app/task_manager.cpp - NBI HTTP/2 → Context termination API: handles termination
- NBI HTTP/2 → Error reporting API: handles error reports
- NBI HTTP/2 → Capability exchange API: handles capability exchange
- NBI HTTP/2 → Parameter exchange API: handles parameter exchange
- NBI HTTP/2 → Mapping document API: serves mapping document
- Context termination API → Application dispatch: invokes operation
- Mapping document API → Application dispatch: requests mapping