Network Exposure Function Chaining for 5G IoT Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current 5G communication systems face challenges in efficiently exposing network exposure functions (NEFs) to third-party application servers, particularly in managing mobility events and session changes, and providing necessary information to the core network, which hinders effective integration with IoT environments.

Innovation Solution

A method for discovering, chaining, and managing network exposure functions (NEFs) using a control function that interacts with the core network and third-party application servers, allowing for the detection of connections between NEFs and enabling direct communication for terminal information acquisition and data transmission.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If network exposure functions are exposed to third-party application servers in 5G systems, then service capabilities and network efficiency are improved, but device complexity and integration difficulty increase

Engineering Contradiction:
Improveservice capabilitiesVSAvoidintegration difficulty
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces a service capability exposure function (SCEF) as an intermediary component that mediates between the core network and third-party application servers. The SCEF receives service capability exposure requests from external ASs, processes them through appropriate network functions, and returns results. This intermediary architecture simplifies the integration process for third parties while maintaining improved service capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the network exposure architecture into distinct functional components: the service capability exposure function (SCEF), network functions (NFs), and external application servers. This segmentation allows each component to be independently managed and configured, reducing overall system complexity while enabling enhanced service capabilities through modular integration.

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If network exposure functions are configured for specific APIs, network slices, and areas, then adaptability and service capabilities are improved, but device complexity increases

Engineering Contradiction:
Improveservice capabilitiesVSAvoidconfiguration complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic configuration of the service capability exposure function, allowing the SCEF to be flexibly configured for different APIs, network slices, and geographic areas based on service requirements. The configuration can be adjusted in real-time without requiring system redesign, enabling high adaptability while managing complexity through parameter-based configuration rather than structural changes.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The service capability exposure function is designed as a universal component that can handle multiple types of requests across different APIs, network slices, and areas through a single standardized interface. This multi-functional design allows the same SCEF instance to serve diverse service requirements, improving adaptability without proportionally increasing device complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentEP3429129B1Method and apparatus for discovering and chaining network exposure functions
Publication Date: 2022.05.04 SAMSUNG ELECTRONICS CO LTD
  • EP3429129B1 patent drawingFigure 1
  • EP3429129B1 patent drawingFigure 2
  • EP3429129B1 patent drawingFigure 3

AI summary

First and second network nodes and methods thereof are provided. The method for the first network node to manage a second network node in a mobile communication system includes receiving, from a plurality of second network nodes, application programming interface (API) information related to each of the plurality of second network nodes, composing a plurality of second network node chainings based on the API information, selecting, when an API request is received from an external server, one of the plurality of second network node chainings for supporting the API request, and transmitting the API request to a second network node included in the selected second network node chaining.