Service Controller Instance Set Selection for 5G Data Consistency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In the 5G communication network, the management of services with shared data across multiple service instances is challenging due to the need for independent management, which is often hindered by implementation-dependent interfaces, and there is a lack of efficient methods to access and maintain shared data resources across different service instances.

Innovation Solution

A service controller is introduced to manage service instance sets, allowing for the registration of instances within sets rather than the Network Repository Function (NRF), enabling selection of available sets for operations and ensuring access to fresh data, while a shared service storage resource node provides standardized context data access across multiple vendors and data centers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If service instances are managed independently with implementation-dependent interfaces, then service autonomy is improved, but data sharing and consistency across instances deteriorates

Engineering Contradiction:
Improveservice autonomyVSAvoiddata consistency
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a service instance set as an intermediary layer between individual service instances and the NRF. This set manages shared data resources and coordinates access across multiple instances, allowing each instance to maintain independence while ensuring data consistency through centralized management of the shared resource

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent combines multiple service instances into a service instance set that shares common data resources. By merging the management of these instances under a single set identifier, the system achieves both service autonomy (each instance can operate independently) and data consistency (shared resources are managed collectively)

Inventive Principle:
Principle #5Merging (Combining)

2Reliability

If service instances share common data resources, then data consistency is improved, but management complexity increases

Engineering Contradiction:
Improvedata consistencyVSAvoidmanagement complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The service instance set serves multiple functions: it manages shared data resources, coordinates instance operations, and provides a unified interface to the NRF. This multi-functionality reduces management complexity by consolidating various management tasks into a single entity rather than requiring separate mechanisms for each function

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

3Reliability

If a load balancer is used to expose service instance sets, then service availability is improved, but system complexity increases

Engineering Contradiction:
Improveservice availabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The service instance set implementation includes mechanisms to monitor the availability and status of individual service instances. When instances become unavailable, the system automatically adjusts routing or activates backup instances, providing feedback-driven load balancing that improves availability without requiring complex external load balancer infrastructure

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20240340338A1Methods of Operating Service Control Nodes
Publication Date: 2024.10.10 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US20240340338A1 patent drawing
  • US20240340338A1 patent drawing
  • US20240340338A1 patent drawing

AI summary

A service controller receives an operation request for a service for a consumer node of a communication network, the operation request including a context identifier referring to a context related to the operation request. The service controller forwards the operation request to a first service instance set being identified by the service controller as handling the context related to the operation request. Responsive to determining that the first service instance set is unreachable or unavailable, the service controller selects a second service instance set as a candidate to handle the context related to the operation request. The operation request for the service is then forwarded to the second service instance set.