5G Media Service Entry Discovery for Unified Uplink and Downlink
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing 5G media streaming architecture lacks defined service entries for uplink and downlink streaming, particularly in the 3GPP TS26.512 specifications, which limits protocol flexibility and entry points for media content delivery.
Innovation Solution
The proposed solution involves extending the Streaming Access object to include an array of entries with protocol identifiers and URLs, allowing multiple service entry points and defining a priority order, ensuring compatibility with the 5GMS M5 interface for both uplink and downlink streaming.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the existing 3GPP TS26.512 specification is used for uplink streaming, then the basic streaming function is provided, but no service entry is defined limiting protocol flexibility
Solution Approach 1:
The StreamingAccess object is extended to serve both uplink and downlink streaming functions universally. The same object structure with protocolIdentifier and URL fields is used for both streaming directions, eliminating the need for separate service entry definitions and enabling multi-protocol support (RTSP, RTP, HTTP, HTTPS) through a unified interface.
Solution Approach 2:
The specification is enhanced by adding new parameters (protocolIdentifier enum with RTSP, RTP, HTTP, HTTPS options and URL field) to the existing StreamingAccess object. This parameter extension allows the same object to accommodate multiple protocols and service entry types without fundamentally changing the object structure or creating new complex data models.
2Adaptability or versatility
If the existing downlink streaming service entry is used, then basic access is provided, but entry point availability is limited
Solution Approach 1:
The StreamingAccess object is designed to universally handle both uplink and downlink service entries. By using the same object structure for both directions with protocol-specific identifiers and URLs, the system achieves broader entry point availability without duplicating service entry structures or increasing overall system complexity.
3Adaptability or versatility
If multiple protocols are supported through extended StreamingAccess object, then protocol flexibility is enhanced, but specification complexity increases
Solution Approach 1:
Instead of creating separate data structures for each protocol, the solution extends the existing StreamingAccess object by adding protocolIdentifier (with enum values for RTSP, RTP, HTTP, HTTPS) and URL fields. This parameter-based approach allows multi-protocol support while maintaining a simple, unified object structure that does not significantly increase specification complexity.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Systems, devices, and methods for managing capabilities of a 5G media streaming (5GMS) network, including obtaining a streaming access object corresponding to 5GMS media content; obtaining a media service entry based on the streaming access object, wherein the media service entry includes a protocol identifier corresponding to the media service entry, and a service entry uniform resource locator (URL) corresponding to the media service entry; and performing at least one of uplink streaming or downlink streaming of the 5GMS media content based on the media service entry, wherein the media service entry is consistent with a 5GMS M5 interface regardless of whether the media service entry is used for uplink streaming or downlink streaming of the 5GMS media content.