NIDD RDS Port Management for Sleep-State Reservation Reliability

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 (NIDD) face challenges such as failed reservations or releases due to device sleep states or HTTP timeouts, and issues with improper AF notifications when RDS ports are not created by the AF or UE.

Innovation Solution

A method and network node that include an indication in the request for reserving or releasing RDS port resources, specifying whether confirmation with the terminal device is required, allowing the Network Exposure Function (NEF) to manage RDS ports dynamically and notify the AF accordingly, with interactions and notifications based on this indication.

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 consumptionVSAvoidport 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 operations when the terminal device is in sleep state, and executes these buffered operations when the device becomes available, ensuring both power savings and operational reliability

Inventive Principle:

Principle #10Preliminary action

2Loss of time

If HTTP client timer is used for port management, then communication timeout is controlled, but processing time for RDS protocol messages is insufficient

Engineering Contradiction:

Improvecommunication timeoutVSAvoidprocessing time

Core Design Contradiction:

Loss of timeVSDuration of action of moving object

Solution Approach 1:

The system dynamically adjusts the timeout mechanism by introducing a buffer that decouples the HTTP client timer from the actual RDS protocol message processing, allowing the processing time to extend beyond the original timeout period while maintaining controlled communication timing

Inventive Principle:

Principle #15Dynamics

3Ease of operation

If AF notifies UE about RDS port reservation, then port management is coordinated, but notification may be improper when port is not created by AF or UE

Engineering Contradiction:

Improveport management coordinationVSAvoidnotification accuracy

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The system implements feedback mechanisms where the AF receives confirmation responses from the NEF about the actual port reservation status, and only notifies the UE when the port was successfully created by either the AF or UE, ensuring accurate and appropriate notifications

Inventive Principle:

Principle #23Feedback

4Ease of operation

If RDS port management is simplified, then operation complexity is reduced, but flexibility in handling different scenarios is lost

Engineering Contradiction:

Improveoperation simplicityVSAvoidscenario handling flexibility

Core Design Contradiction:

Ease of operationVSAdaptability or versatility

Solution Approach 1:

The system creates a universal port management mechanism where the NEF acts as an intermediary that handles multiple scenarios (AF-initiated reservation, UE-initiated reservation, sleep state handling, timeout management) through a single standardized interface, maintaining both simplicity and flexibility

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS20250254739A1Method and network node for port management

Publication Date: 2025.08.07 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

AI summary

The present disclosure provides a method in a Network Exposure Function, NEF. The method includes: receiving, 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, to the AF, a response to the request.