NEF RDS Port Reservation With Terminal Confirmation Control

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing methods for managing Reliable Data Service (RDS) ports in non-Internet Protocol (IP) data delivery face challenges such as failed reservations or releases due to terminal devices being in a sleep state or HTTP timeouts, and issues with notifying Application Functions (AFs) about RDS port status.

Innovation Solution

A method and network node that include an indication in requests for reserving or releasing RDS ports, specifying whether confirmation with the terminal device is required, allowing the Network Exposure Function (NEF) to manage RDS ports dynamically and notify AFs of current reservations, thereby improving efficiency and flexibility.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Use of energy by moving object

If the terminal device is in a sleep state, then power consumption is reduced, but RDS port reservation or release operations fail

Engineering Contradiction:

Improvepower consumptionVSAvoidRDS port reservation reliability

Core Design Contradiction:

Use of energy by moving objectVSReliability

Solution Approach 1:

The system performs preliminary actions by buffering RDS port reservation or release requests when the terminal device is in sleep state, and executes these buffered operations when the device becomes active, ensuring operations are not lost due to device unavailability

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The network side acts as an intermediary by maintaining buffered requests and managing the timing of operation execution, decoupling the request initiation from the actual execution to bridge the gap between network operations and terminal device availability

Inventive Principle:

Principle #24Intermediary (Mediator)

2Device complexity

If HTTP client timer is used for RDS protocol messages, then communication timing is simplified, but processing timeouts occur due to longer RDS processing time

Engineering Contradiction:

Improvecommunication timing complexityVSAvoidmessage processing reliability

Core Design Contradiction:

Device complexityVSReliability

Solution Approach 1:

The system dynamically adjusts the timer mechanism by introducing configurable timers on both network side and terminal side, allowing flexible timing adjustments based on actual processing requirements rather than fixed HTTP client timer constraints

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The patent changes the timing parameters by allowing configurable timer values that can be adapted to different processing scenarios, enabling the system to handle longer RDS processing times without timeout errors

Inventive Principle:

Principle #35Parameter changes

3Productivity

If RDS port reservation is implemented without terminal device confirmation, then operation speed is improved, but incorrect reservations may occur

Engineering Contradiction:

Improveport reservation speedVSAvoidreservation accuracy

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The system implements a two-stage approach where reservation is partially confirmed immediately for speed, followed by terminal device confirmation for accuracy, allowing the process to proceed without waiting for full confirmation while still ensuring correctness

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentEP4158927B1Port management

Publication Date: 2026.04.08 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

Figure 1~2
Figure 3~4
Figure 5

AI summary

The present disclosure provides a method (100) in a Network Exposure Function, NEF. The method (100) includes: receiving (110), from an Application Function, AF, a request for dynamically reserving a Reliable Data Service, RDS, port resource in association with a Non -Internet Protocol 'IP' Data Delivery, NIDD, configuration, the request containing an indication indicating whether the reserving of the RDS port resource requires confirmation with the terminal device; and transmitting (120), to the AF, a response to the request.