Micro UPF Identifier Allocation via Service Templates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current cellular communications systems lack a flexible and generic method for allocating identifiers to users when the user plane is distributed and decomposed into small micro User Plane Functions (UPFs), and they have limited means to introduce new services without lengthy standardization processes.

Innovation Solution

The introduction of 'assign objects' in service templates allows for flexible allocation of identifiers and the extension of the Session Management Function (SMF) to support flexible service requests, enabling the decomposition of UPFs into micro UPFs and dynamic service configuration through the Chain Controller (CC).

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the User Plane Function (UPF) is decomposed into multiple micro UPFs, then flexibility and adaptability to support diverse 5G use cases is improved, but the complexity of the system architecture increases

Engineering Contradiction:
Improveflexibility to support diverse use casesVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the monolithic UPF into multiple independent micro UPFs that can be deployed as separate network functions. Each micro UPF can be independently configured and managed, enabling flexible deployment for different use cases while maintaining overall system functionality through coordinated interaction between the micro UPFs and the Chain Controller.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If service templates with assign objects are introduced for flexible identifier allocation, then ease of service configuration is improved, but the complexity of service management increases

Engineering Contradiction:
Improveease of service configurationVSAvoidservice management complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces assign objects as intermediary elements within service templates that mediate between the service configuration and identifier allocation. These assign objects automatically handle identifier assignment based on service template definitions, abstracting the complexity of identifier management from the service configuration process and enabling simpler, more flexible service deployment.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If dynamic service reconfiguration is enabled through the Chain Controller, then adaptability to changing requirements is improved, but the overhead of service management increases

Engineering Contradiction:
Improvedynamic reconfiguration capabilityVSAvoidservice management overhead
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent implements dynamics by enabling the Chain Controller to dynamically configure and reconfigure service chains based on changing network conditions and requirements. Service templates can be dynamically instantiated, modified, and terminated without requiring manual intervention or extensive reconfiguration processes, allowing the system to adapt to varying traffic patterns and service demands efficiently.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11917509B2Requesting flexible user-plane services in a service-based architecture
Publication Date: 2024.02.27 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US11917509B2 patent drawing
  • US11917509B2 patent drawing
  • US11917509B2 patent drawing

AI summary

Embodiments of a method of operation of a service requestor to request a service from a chain controller in a cellular communications network in which a user plane function is decomposed into a plurality of micro user plane functions are disclosed. In some embodiments, the method comprises sending, to the chain controller, a service description or a request to update a service description. The service description comprises one or more service template instances having respective service template definitions. Each service template definition of the respective service template definitions being data that defines a set of micro user plane functions that realize a service or a part of a service. Each service template instance of the one or more service template instances comprises data that defines a reference to the respective service template definition. The method further comprises receiving a reply from the chain controller.