5G Cloud Nokia HEP3 Support
Note: CMM Solution is now available as an Early Access feature, giving you the opportunity to explore its capabilities before the general availability (GA).
Nokia HEP3 (Homer Encapsulation Protocol Version 3) method is supported by Nokia for network functions across 3G,4G, 5G and the IMS core. HEP3 efficiently organizes and encodes data for various network protocols and enhances the functionality of Nokia's core network solutions by accommodating diverse packet requirements.
The 5G-Cloud application supports processing the Nokia HEP3 format from the IMS network functions and 3G, 4G network functions. Non-SBI traffic is received as a TCP stream with HEP3 encoding by the 5G Cloud application. The 5G-Cloud application receives encapsulated traffic from the IMS vTAP in HEP3 over TCP, using either clear text or mTLS. Non-SBI control traffic is decoded from HEP3, emphasizing data handling without IP translation.
Nokia Cloud Mobility Manager (CMM), including AMF and MME, generates SBI and Non-SBI traffic over HTTP2 using clear text / TLS. The gvHTTP2 application receives this traffic and forwards it to the 5G-Cloud application. The 5G-Cloud synthesizes SBI payloads into L2GRE/VXLAN packets, enabling seamless monitoring across 5G core interfaces.
In Nokia SCP mode, the traffic is mirrored between the 5G control functions using HTTP2 protocol, which is mirrored from a service called SCP (Service Communication Proxy). The 5G-Cloud application receives the JSON encoded data from the VXLAN ingress TEPs. Refer to Nokia SCP.
The system supports the following types of traffic:
Supportability Table
The supportability table provides a quick reference to the supported Nokia functions:
|
Traffic Type |
Source Functions |
Protocols |
Reference |
|
Non-SBI |
3G, 4G, IMS |
HEP3 over TCP with Clear Text / mTLS |
|
|
SBI |
CMM (AMF, MME) |
HEP3 over HTTP2 over TCP with Clear Text / TLS |
