Service-Based Architecture for Network Flexibility and QoS

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current communication networks face challenges in efficiently managing and optimizing the communication protocols and network architecture, particularly in supporting multiple technologies and releases, ensuring quality of service, and handling roaming scenarios and network slicing effectively.

Innovation Solution

The proposed solution involves a service-based architecture within the core network, utilizing network functions such as user plane and control plane functions, and implementing advanced protocol stacks and quality of service models to manage communication efficiently across different technologies and scenarios.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a service-based architecture is implemented to support multiple technologies and releases, then network flexibility and adaptability are improved, but device complexity and architectural complexity increase

Engineering Contradiction:
Improvenetwork flexibilityVSAvoidarchitectural complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The network architecture is segmented into distinct service-based functional units (user plane functions, control plane functions) that can be independently deployed, managed, and scaled. This segmentation allows different technologies and releases to coexist while maintaining clear boundaries and interfaces, thereby improving flexibility without proportionally increasing overall complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The service-based architecture implements universal service interfaces and protocols that enable a single architectural framework to support multiple technologies and releases (e.g., 5G, 4G, future releases). This multi-functionality approach allows the same infrastructure to adapt to different requirements without requiring completely separate systems for each technology.

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

2Reliability

If advanced protocol stacks and quality of service models are implemented, then quality of service is improved, but device complexity and processing requirements increase

Engineering Contradiction:
Improvequality of serviceVSAvoidprocessing complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Quality of service parameters, protocol configurations, and service level agreements are pre-configured and established during network setup and service registration phases. This preliminary action ensures that when services are executed, the complex QoS management is already in place, reducing real-time processing complexity while maintaining high service quality.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The architecture introduces intermediary service management functions that mediate between service requests and underlying network resources. These intermediaries handle complex protocol translation, QoS enforcement, and resource allocation, thereby improving service quality while shielding core network elements from excessive processing complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If network slicing and roaming scenario handling are enhanced, then service diversity and reliability are improved, but device complexity and management overhead increase

Engineering Contradiction:
Improveservice diversityVSAvoidmanagement overhead
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The network is divided into multiple virtual slices, each optimized for specific service types (e.g., enhanced mobile broadband, ultra-reliable low-latency communication, massive machine type communication). This segmentation allows diverse services to run in isolated environments with dedicated resources, improving service diversity while managing complexity through clear slice boundaries and independent management planes.

Inventive Principle:
Principle #1Segmentation

4Reliability

If multiple user plane functions are deployed, then network resilience and service continuity are improved, but device complexity and resource requirements increase

Engineering Contradiction:
Improveservice continuityVSAvoidresource requirements
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

Multiple user plane function instances are deployed and logically combined to provide redundant service paths and load sharing. When one user plane function fails or becomes overloaded, traffic is automatically redirected to other instances, ensuring service continuity. This merging approach distributes resource requirements across multiple instances rather than concentrating them in a single point, improving reliability while managing resource utilization efficiently.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS20240267858A1Time Resiliency Service
Publication Date: 2024.08.08 OFINNO LLC
  • US20240267858A1 patent drawing
  • US20240267858A1 patent drawing
  • US20240267858A1 patent drawing

AI summary

A central unit (CU) of a base station sends, to a distributed unit (DU) of the base station, a first message indicating that a wireless device supports a traceability to Coordinated Universal Time (UTC). The CU receives, from the DU, a second message indicating whether the DU provides the traceability to UTC. The CU sends, to the wireless device, an indication whether the base station provides traceability to UTC.