Transport Protocol Selection for Cloud-Native 3GPP Network Nodes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current telecommunication systems lack an efficient and flexible mechanism for automatic configuration of service endpoints based on required capabilities and event subscription filters, particularly in 3GPP networks, complicating protocol stacks in cloud-based deployments and limiting support for SCTP-based solutions.

Innovation Solution

A method and apparatus for selecting a supported transport layer protocol by obtaining and utilizing information about the supported protocols of a second network node, enabling efficient protocol coordination through a centralized repository or registry, and supporting enhanced Service-Based Architecture (SBA) with HTTP/3 and QUIC protocols to simplify and modernize the protocol stack.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If current procedures based on NG-AP and Xn-AP protocols are used, then communication between network nodes is established, but the system lacks efficient automatic configuration of service endpoints based on required capabilities

Engineering Contradiction:
Improveautomatic configuration of service endpointsVSAvoidprotocol stack complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The patent enables network nodes to automatically discover and select supported transport layer protocols through self-service mechanisms. Network nodes publish their protocol capabilities in a registry and can autonomously configure service endpoints based on required capabilities without manual intervention, thereby improving automation while managing complexity through standardized self-configuration procedures

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent introduces a centralized registry or repository as an intermediary that stores information about supported transport layer protocols of network nodes. This intermediary enables automatic configuration by mediating between network nodes, allowing them to discover and select compatible protocols without direct complex negotiation, thus improving automation while the registry manages the complexity centrally

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple transport layer protocols (TCP, UDP, SCTP) are supported, then versatility of communication is improved, but device complexity increases

Engineering Contradiction:
Improveprotocol support versatilityVSAvoidprotocol stack complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal registry mechanism that handles multiple transport layer protocols (TCP, UDP, SCTP) through a single standardized interface. Network nodes can publish and discover support for various protocols through this universal system, achieving protocol versatility without proportionally increasing complexity, as the registry provides a unified management layer for all protocol types

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The centralized registry acts as an intermediary that manages the complexity of supporting multiple protocols. Instead of each node directly handling complex multi-protocol negotiations, the registry mediates by storing and providing information about supported protocols, allowing nodes to select appropriate protocols (TCP for reliability, UDP for speed, SCTP for specialized needs) without direct complexity exposure

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If cloud-based deployments with container-based architectures are used, then scalability is improved, but protocol stack complexity increases due to PFCP on N4 interface

Engineering Contradiction:
Improvedeployment scalabilityVSAvoidprotocol stack complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent extends the universal registry mechanism to cloud-based container deployments, enabling the same protocol discovery and selection process to work across diverse deployment environments. The registry provides a unified approach that works for both traditional and cloud-native architectures, allowing scalable container-based deployments while managing protocol complexity through the standardized registry interface

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The registry serves as an intermediary that simplifies protocol stack management in cloud deployments. By centralizing protocol capability information, it reduces the complexity burden on individual containerized network functions, enabling scalable deployments where each node can automatically configure itself based on registry information without requiring complex local protocol negotiation logic

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP4712452A1Method, computer program, and apparatus for choosing a supported transport layer protocol for communicating in a telecommunication system
Publication Date: 2026.03.18 DEUTSCHE TELEKOM AG
  • EP4712452A1 patent drawingFigure 1
  • EP4712452A1 patent drawingFigure 2
  • EP4712452A1 patent drawingFigure 3

AI summary

Examples relate to a method, a computer program, and an apparatus for choosing a supported transport layer protocol at a first network node of a telecommunication system for communicating with a second network node of the telecommunication system. The method (10) for choosing a supported transport layer protocol at a first network node (200) of a telecommunication system (300) for communicating with a second network node (220) of the telecommunication system (300) comprises obtaining (12), at the first network node (200), information about one or more supported transport layer protocols of the second network node (220). The method (10) further comprises selecting (14) a supported transport layer protocol, which is supported by the first network node (200) and the second network node (220), based on the information about the sup-ported transport layer protocols of the second network node (220). The method (10) also comprises communicating (16) messages between the first network node (200) and the second net-work node (220) based on the supported transport layer protocol.