Multi-Slice Streaming Service Latency Reduction in 5G Wireless Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current 5G mobile communication systems face challenges in reducing latency for streaming services, particularly in game streaming, where high waiting times and limited bandwidth lead to suboptimal user experiences, especially with the increasing demand for low-latency and high-quality content delivery.

Innovation Solution

The proposed solution involves configuring a multi-slice connection between a service provider and a user, utilizing Enhanced Mobile Broadband (eMBB) for high-quality video content and Ultra Reliable Low Latency Communication (URLLC) for metadata transfer, enabling the production of a data stream even if the primary data stream is not successfully received, thereby reducing latency and maintaining a stable connection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a single network slice is used for streaming service, then device complexity is reduced, but reliability and latency performance deteriorate

Engineering Contradiction:
Improveconnection reliabilityVSAvoidnetwork slice configuration
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent divides the network connection into two separate network slices: a primary slice for main data transmission and a secondary slice for backup and metadata. This segmentation allows each slice to be optimized for specific functions, improving overall reliability while maintaining manageable complexity through functional separation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different network slices are assigned different quality characteristics tailored to their specific functions. The primary slice is optimized for high bandwidth data transmission, while the secondary slice is optimized for low latency metadata and backup communication. This local quality optimization ensures each component performs optimally for its purpose.

Inventive Principle:
Principle #3Local quality

2Productivity

If high data speeds are prioritized, then productivity is improved, but latency increases

Engineering Contradiction:
Improvedata transmission speedVSAvoidwaiting time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent segments data transmission into two parallel paths: the primary path for high-speed data delivery and the secondary path for low-latency metadata and backup. This allows the system to simultaneously achieve high productivity through the optimized data path while maintaining low latency through the dedicated metadata path.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Different network slices are configured with different transmission parameters optimized for their specific functions. The primary slice uses parameters optimized for maximum data throughput, while the secondary slice uses parameters optimized for minimum latency, allowing both objectives to be achieved simultaneously.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If backup communication channel is added, then reliability is improved, but device complexity increases

Engineering Contradiction:
Improvedata stream availabilityVSAvoidmulti-slice management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The backup communication channel is implemented as a separate network slice with distinct functional responsibilities. This segmentation isolates the backup function from the primary data transmission, simplifying management by allowing each slice to operate independently with well-defined roles.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The secondary network slice acts as an intermediary backup channel that activates only when needed. This intermediary structure provides reliability through redundancy while maintaining simplicity through conditional activation, avoiding the complexity of continuously managing multiple active paths.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Loss of time

If parallel network slices are configured, then latency is reduced, but ease of operation deteriorates

Engineering Contradiction:
Improvestreaming latencyVSAvoidconnection configuration
Core Design Contradiction:
Loss of timeVSEase of operation

Solution Approach 1:

The patent segments the connection into primary and secondary slices with automated failover capabilities. This segmentation enables low latency through parallel paths while simplifying operation through automatic management, reducing the need for manual intervention in slice selection and switching.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system incorporates feedback mechanisms that automatically monitor the status of both network slices and switch between them based on real-time conditions. This automated feedback-driven operation maintains low latency while improving ease of operation by eliminating manual configuration requirements.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20230336605A1Method and apparatus for reducing latency of streaming service by network slices parallel in wireless communication system
Publication Date: 2023.10.19 SAMSUNG ELECTRONICS CO LTD
  • US20230336605A1 patent drawing
  • US20230336605A1 patent drawing
  • US20230336605A1 patent drawing

AI summary

The disclosure relates to the 5th generation (5G) or 6th generation (6G) communication system to support a high data transmission rate than before. A method of operating a streaming service client (SSC) node in a wireless communication system is provided. The method includes an operation of establishing a connection to a streaming service provider (SSP) via two types of services that are enhanced mobile broadband (eMBB) and ultra reliable low latency communication (URLLC), an operation of receiving first data from the SSP via the eMBB, and simultaneously receiving second data via the URLLC, wherein the second data is metadata of the first data, and operation of determining whether the first data is successfully received, and an operation of producing a data stream using the second data in a case in which the first data is not successfully received.