This documentation is currently under development and subject to change. It reflects outcomes elaborated by 5G-MAG members. If you are interested in becoming a member of the 5G-MAG and actively participating in shaping this work, please contact the Project Office
Network Capabilities (Network Services) for Content Production & Contribution
This is a list of network capabilities required to realize the scenarios described in Network Capability Exposure and APIs for Content Production and Contribution Scenarios.
Media delivery with Quality of Service (QoS)
| Requirement | API |
|---|---|
| Ability to request different QoS profiles for individual data flows coming from the same production device node | |
| Ability to separate media/data flows coming from the same production device node | |
| Delivery to endpoint (Application Media Server) may be identified by security/protocol/IP/port | |
| Ability to configure new or re-configure existing QoS profiles to be selected during runtime | |
| Ability to select at runtime a QoS profile for a media flow | |
| Ability to receive ACK (success/fail) |
Information monitoring, logging and/or Network assistance
| Requirement | API |
|---|---|
| Ability to receive information from the network | |
| Real-time information for QoS profile re-selection and/or e.g. codec reconfiguration, bitrate reconfiguration | |
| Information during runtime for troubleshooting | |
| Information after the session (logging information) for post-processing |
Time Synchronization
| Requirement | API |
|---|---|
| Ability to enable distribution of timing information |
Voice service for Intercom
| Requirement | API |
|---|---|
| Ability to establish a voice service across the intercom devices deployed at the production location or between the production center and the production location |
Focus on the QoS for Intercom - a voice service offered by the network may not be so relevant (alternative solutions, WebRTC). But multicast, MCPTT may be of use.
Considerations on Devices
Identification of devices
Requirement | API – | – Devices should be uniquely identifiable during operation | Devices should be dynamically added or deleted during operation and attachable to given network capabilities | Each device should only access the network capabilities which have been assigned during booking |
Device on-boarding and API consumer on-boarding
Requirement | API – | – TBD How to obtain credentials |
Discovery of network capabilities
Requirement | API – | – TBD How to discover network capabilities |