5G SCP Retry-After Propagation Across Multiple Producer NFs

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In 5G telecommunications networks, the Service Communication Proxy (SCP) can only communicate a single Retry-After header field value when multiple producer Network Functions (NFs) fail to process a service request, leading to inefficient retry attempts by consumer NFs due to missing Retry-After header field values from other failed NFs.

Innovation Solution

The SCP propagates multiple Retry-After header field values by encoding them in custom headers or JSON information elements within the error response message, ensuring consumer NFs receive all necessary retry timing information for each failed producer NF.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If the SCP communicates only a single Retry-After header field value to the consumer NF, then the error response message structure remains simple and easy to process, but the consumer NF cannot obtain complete retry timing information from all failed producer NFs, leading to inefficient retry attempts

Engineering Contradiction:

ImproveRetry-After header field values from multiple producer NFsVSAvoidError response message structure

Core Design Contradiction:

Loss of informationVSDevice complexity

Solution Approach 1:

The patent segments the Retry-After header field values from multiple producer NFs into individual JSON information elements, each containing the NF instance ID and corresponding Retry-After value. This segmentation allows the SCP to preserve all retry timing information while organizing it in a structured, parseable format that the consumer NF can process efficiently.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces a custom header format as an intermediary structure between the multiple Retry-After header field values from different producer NFs and the consumer NF. This intermediary JSON structure acts as a container that holds segmented retry information, enabling the SCP to communicate complete retry timing data without directly modifying the fundamental error response message structure.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If the consumer NF reattempts service requests without proper Retry-After header field value guidance from all producer NFs, then processing continues without waiting, but unnecessary retries occur leading to increased network traffic and processing resource consumption

Engineering Contradiction:

ImproveService request processing efficiencyVSAvoidProcessing resources and network bandwidth

Core Design Contradiction:

ProductivityVSLoss of energy

Solution Approach 1:

The patent implements feedback by providing the consumer NF with complete Retry-After header field values from all failed producer NFs through the custom header structure. This feedback enables the consumer NF to make informed retry decisions, waiting the appropriate amount of time before reattempting requests to specific NFs, thereby avoiding unnecessary retries and reducing network traffic and processing resource consumption.

Inventive Principle:

Principle #23Feedback

3Loss of information

If the SCP forwards error responses from multiple producer NFs with different Retry-After header field values, then complete retry information is available, but the error response message size increases

Engineering Contradiction:

ImproveComplete retry timing informationVSAvoidError response message data volume

Core Design Contradiction:

Loss of informationVSQuantity of substance

Solution Approach 1:

The patent changes the format parameter of retry information from traditional header fields to JSON information elements within a custom header. This parameter change allows the SCP to include multiple Retry-After values in a compact, structured format that is more space-efficient than including multiple separate headers, thereby providing complete retry timing information while minimizing the increase in error response message size.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS12413479B1Methods, systems, and computer readable media for communicating retry-after header field values to consumer network functions (NFs) via service communication proxies (SCPs)

Publication Date: 2025.09.09 ORACLE INT CORP

AI summary

A method for multi-NF Retry-After header field value propagation includes receiving, by an SCP and from a consumer NF, an SBI request message and determining that the SBI request message requests a service that can be provided by first and second producer NFs. The method further includes forwarding the SBI request message to a first producer NF and receiving a response message indicating that the first producer NF failed to process the SBI request message and including a first Retry-After header field value. The method further includes forwarding the SBI request message to the second producer NF and receiving a response message from the second producer NF indicating that the second producer NF failed to process the SBI request message and including a second Retry-After header field value. The method further includes communicating, by the SCP and to the consumer NF, the first and second Retry-After header field values.