5G PDU Session Discovery via SMF Events for Device App Reachability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing enterprise applications struggle to connect with server applications on devices connected via a 5G wireless transceiver due to the 'chicken-and-egg' problem where the device application expects to be connected by the enterprise application, but the enterprise application does not know the UE's IP address, leading to challenges in establishing a PDU session.

Innovation Solution

An automated method enables enterprise communication systems to contact device applications by subscribing to PDU session updates from the 5G network, using a unique device identifier, and leveraging a Generic Public Subscription Identifier (GPSI) or IPv6 address to ensure a one-to-one relation, allowing the enterprise application to infer and contact the device application through SMF event notifications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If the enterprise application requests a PDU session to the device application, then connectivity is established, but the enterprise application does not know the UE's IP address and cannot initiate the connection

Engineering Contradiction:
Improveconnection establishmentVSAvoidUE IP address information
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

Instead of the enterprise application initiating the connection request to the device application, the patent inverts the approach by having the device application (via the UE) request the PDU session to the enterprise application. The SMF then notifies the enterprise application about the established session, providing the UE's IP address information indirectly through the notification mechanism.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The Session Management Function (SMF) acts as an intermediary between the UE and the enterprise application. It receives the PDU session request from the UE, establishes the session, and then notifies the enterprise application about the established connection, thereby mediating the information exchange without requiring the enterprise application to directly query for UE IP addresses.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If manual configuration or off-line mechanisms are used to provide enterprise application address to UE, then connectivity can be established, but device complexity and operational burden increase

Engineering Contradiction:
Improveconnection reliabilityVSAvoidconfiguration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The UE performs self-service by autonomously requesting the PDU session to the enterprise application without requiring manual configuration of the enterprise application address. The UE uses its own identifier (such as GPSI or IPv6 address) to initiate the session request, and the network automatically handles the connection establishment and notification processes.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent employs preliminary action by having the UE pre-configure its own identifier (GPSI or IPv6 address) before connection establishment. This identifier is used during the PDU session request phase, eliminating the need for manual configuration of enterprise application addresses while ensuring reliable connection establishment.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If discovery mechanisms like mDNS are used to resolve hostname to local IP address, then connectivity can be established without DNS server, but the solution is limited to local network scenarios and does not work for 5G wireless networks

Engineering Contradiction:
Improvenetwork adaptabilityVSAvoidconnection reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent creates a universal solution that works across different network types (including 5G wireless networks) by using the 5G core network's session management capabilities. The SMF-based mechanism provides multi-functionality by handling both the PDU session establishment and the notification of session details to the enterprise application, eliminating the need for network-specific discovery mechanisms like mDNS.

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

Solution Approach 2:

The patent replaces mechanical/discovery-based systems (like mDNS that require local network broadcast) with a 5G network-based messaging system. The SMF sends notifications to the enterprise application through the 5G core network, substituting the need for local network discovery mechanisms with a centralized network-managed communication approach that is more reliable for wireless scenarios.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS20250392565A1Establishment and Discovery of an Application-Related Default Protocol Data Unit Session in 5G Networks
Publication Date: 2025.12.25 SIEMENS AG
  • US20250392565A1 patent drawing
  • US20250392565A1 patent drawing
  • US20250392565A1 patent drawing

AI summary

Various embodiments of the teachings herein include a method for enabling an enterprise communication system to contact a device application of a device with a transceiver connected to a 5G communication network. An example includes: requesting a PDU session from the 5G communication network; creating the requested session; adding information about the new session to a data base; informing the enterprise application about the new session; inferring the device identifier from the information provided; if the identifier matches a list of identifiers or application types, contacting the device application using the information; if the identifier is an IPv6 address provided to the wireless transceiver by the device application or a device middleware, the IPv6 address containing the device application identifier to ensure a one-to-one relation between the IPv6 address and the device application identifier.