5G Network Function Validation Gateway Against HTTP/2 Threats

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current 5G network function (NF) infrastructure based on HTTP/2 is susceptible to cyber threats such as SQL injection attacks, Cross-Site Scripting (XSS), Denial of Service (DoS), and other vulnerabilities, despite TLS encryption, which compromises network security and integrity.

Innovation Solution

Implementing additional layers of input validation and a centralized API gateway to filter messages, including cross-site scripting detection, SQL injection detection, and protection against DoS attacks, with a gateway function acting as an initial checkpoint to validate and forward valid requests.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If HTTP/2 protocol is used for NF communications, then protocol flexibility and resilience are improved, but network security and integrity deteriorate due to susceptibility to cyber threats

Engineering Contradiction:
Improveprotocol flexibilityVSAvoidcyber security threats
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces an intermediary validation layer between HTTP/2 protocol operations and network functions. This intermediary validates all input parameters, messages, and data before processing, blocking malicious content such as SQL injection attempts, XSS scripts, and other cyber threats while allowing legitimate HTTP/2 communications to proceed. The intermediary acts as a security gateway that preserves protocol flexibility while filtering harmful factors.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If TLS encryption is implemented, then message confidentiality is improved, but protection against source-modified messages deteriorates as encrypted messages can still be manipulated before encryption

Engineering Contradiction:
Improvemessage confidentialityVSAvoidmessage integrity
Core Design Contradiction:
Loss of informationVSReliability

Solution Approach 1:

The patent applies preliminary validation actions before TLS encryption occurs in the communication flow. Input validation, parameter sanitization, and message structure verification are performed on plaintext data before it enters the encryption pipeline. This preliminary action prevents malicious modification of messages at the source, ensuring that only validated, clean data is encrypted and transmitted, thereby maintaining both confidentiality and integrity.

Inventive Principle:
Principle #10Preliminary action

3Object-affected harmful factors

If additional input validation layers are added, then network security is improved, but system complexity increases

Engineering Contradiction:
Improvesecurity threatsVSAvoidvalidation system complexity
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The patent segments the validation process into distinct, modular layers: parameter validation, message structure validation, content-type validation, SQL injection detection, XSS detection, and rate-limiting. Each validation layer operates independently and can be configured separately. This segmentation reduces overall system complexity by making each component manageable and maintainable while collectively providing comprehensive security protection.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12634334B25G network functions to prevent cyber security threats
Publication Date: 2026.05.19 VERIZON PATENT & LICENSING INC
  • US12634334B2 patent drawing
  • US12634334B2 patent drawing
  • US12634334B2 patent drawing

AI summary

In some implementations, the techniques described herein relate to a method including: receiving a network request from a second network function, the network request including a parameter; validating the parameter upon receipt of the network request to determine a status of the network request, the status indicating a valid or invalid request; processing, by a first network function, a resource managed by the first network function based on the network request and returning a network response when the status indicates a valid request; and denying the network request and returning an error code when the status indicates an invalid request.