5G Notification Subscriptions with Pre-Specified Encoding Formats

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The existing 5G networks lack a standardized and efficient method for encoding negotiation in the notification of events between network functions, leading to increased signaling volume and maintenance complexity, as well as potential rejection of notifications due to unsupported encoding formats.

Innovation Solution

A method for subscribing a first communicating entity to a second entity, where the subscription request indicates supported encoding formats, allowing the second entity to send notifications encoded in those formats, optimizing latency and bandwidth by adapting to the capabilities of the entities involved.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a standardized encoding negotiation method is implemented in 5G networks, then notification reliability is improved, but device complexity increases

Engineering Contradiction:

Improvenotification reliabilityVSAvoidencoding negotiation complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies preliminary action by having the consumer network function specify its supported encoding formats in advance during the subscription request phase. This pre-specification eliminates the need for complex real-time negotiation protocols, as the producer network function can directly use the pre-stated supported formats without requiring additional signaling exchanges to determine encoding compatibility.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent changes the parameter approach by moving from a fixed encoding format to a configurable parameter system where encoding formats are dynamically selected based on the subscription request. The system allows flexible parameter selection (encoding formats) while maintaining standardized interaction protocols, thus improving reliability without proportionally increasing complexity.

Inventive Principle:

Principle #35Parameter changes

2Loss of energy

If encoding formats are standardized for notifications, then bandwidth efficiency is improved, but ease of operation deteriorates

Engineering Contradiction:

Improvebandwidth usageVSAvoidencoding format configuration

Core Design Contradiction:

Loss of energyVSEase of operation

Solution Approach 1:

The patent applies self-service by enabling the consumer network function to autonomously specify its encoding format preferences in the subscription request. The producer network function automatically adapts its notification encoding based on this pre-stated information without requiring manual configuration or complex operational intervention. This maintains ease of operation while achieving bandwidth efficiency through standardized encoding.

Inventive Principle:

Principle #25Self-service

3Adaptability or versatility

If multiple encoding formats are supported, then adaptability is improved, but device complexity increases

Engineering Contradiction:

Improveencoding format flexibilityVSAvoidencoding negotiation logic

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies universality by designing a multi-functional subscription mechanism that handles multiple encoding formats through a single standardized interface. The consumer network function can specify multiple supported encoding formats in one subscription request, and the producer network function universally handles all requested formats through a consistent notification process, eliminating the need for separate negotiation logic for each encoding type.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS20250274424A1Subscription and notification methods, and entities configured for implementing these methods

Publication Date: 2025.08.28 ORANGE SA

AI summary

A method for subscribing a first communicating entity to a second communicating entity. The method is implemented by the first entity and includes: transmitting a subscription request to the second communicating entity requesting subscription to notifications sent by the second communicating entity on at least one event monitored by the second communicating entity. The subscription request indicates at least one encoding format supported by the first communicating entity for receiving the notifications.