SCP Feedback and Rerouting for Failed NF Requests

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing service request handling systems in networks, particularly in 5G networks, face failures due to connectivity issues with service communication proxies (SCPs) despite available and operational network function (NF) nodes, leading to redundant SCP deployments and failed requests.

Innovation Solution

Implementing a method where a service communication proxy (SCP) node initiates transmission of information indicative of a 504 Gateway Timeout if no response is received from a NF node, allowing for SCP reselection and checking the status of the NF node or alternative SCPs to ensure connectivity, and a network function (NF) node initiates a request through a different SCP if the initial connection fails.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If indirect communication via a service communication proxy (SCP) node is used, then service request routing and NF node selection are simplified, but connectivity failures between SCP and NF nodes cause service request failures even when NF nodes are operational

Engineering Contradiction:
Improveservice request routingVSAvoidservice request delivery
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent implements a feedback mechanism where the SCP node sends a notification to the NF consumer node when a service request fails due to connectivity issues. This feedback enables the NF consumer to detect that the NF producer is actually operational and to retry the request through an alternative SCP node, thereby resolving the reliability issue while maintaining the routing simplicity provided by indirect communication.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent employs preliminary action by having the NF consumer node maintain a list of alternative SCP nodes in advance. When the primary SCP connection fails, the NF consumer can immediately retry through a pre-identified alternative SCP without needing to perform discovery or selection procedures at the moment of failure, thus quickly restoring service request delivery.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If multiple SCP nodes are deployed to ensure connectivity, then service request delivery reliability improves, but network complexity and deployment costs increase

Engineering Contradiction:
Improveservice request deliveryVSAvoidnetwork architecture
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies self-service by enabling the NF consumer node to autonomously manage connectivity failures through alternative SCP selection. The NF consumer monitors service request outcomes, detects connectivity issues, and independently retries requests through alternative SCP nodes from its pre-configured list, eliminating the need for complex centralized management or additional infrastructure beyond what already exists.

Inventive Principle:
Principle #25Self-service

3Productivity

If the NF consumer node performs discovery and selection of NF producer nodes, then service request routing is optimized, but the NF consumer must continuously monitor and update NF node status, increasing operational complexity

Engineering Contradiction:
Improveservice request routing efficiencyVSAvoidNF node management
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent extracts the NF node discovery and selection functionality from the NF consumer node and places it in the SCP node. The SCP node now performs discovery of available NF producer nodes and manages the selection process, while the NF consumer simply sends requests to the SCP. This extraction reduces the operational complexity of the NF consumer while maintaining routing efficiency through the SCP's centralized management.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentEP4412186B1Service request handling
Publication Date: 2025.07.30 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • EP4412186B1 patent drawingFigure 1A~1D
  • EP4412186B1 patent drawingFigure 2A
  • EP4412186B1 patent drawingFigure 2B

AI summary

There is provided a method for handling a service request. The method is performed by a first service communication proxy (SCP) node. If no response is received from a second network function (NF) node of a service producer to a first request transmitted towards the second NF node via the first SCP node, where the first request is for the second NF node to execute a service requested by a first NF node of a service consumer, transmission of information is initiated (102) towards the first NF node. The information is indicative that no response is received from the second NF node to the first request.