Content for TS 26.510 Word version: 18.0.2
1 Scope
2 References
3 Definitions of terms, symbols and abbreviations
3.1 Terms
3.2 Symbols
3.3 Abbreviations
...
...
1 Scope p. 18
The present document specifies:
- The operations and corresponding APIs used by a Media Application Provider to interact with a Media AF component to provision the delivery of media in a Media Delivery System.
- The operations and corresponding APIs used by a Media Session Handler component to interact with a provisioned Media AF for the purpose of managing media delivery sessions ("media session handling").
- The operations and corresponding APIs used by a Media-aware Application running in a UE or by a Media Access Client component to interact with a Media Session Handler for the purpose of initiating a media delivery session and for controlling it.
2 References p. 18
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.501: "System architecture for the 5G System (5GS)".
[3]
TS 23.502: "Procedures for the 5G System (5GS); Stage 2".
[4]
TS 26.501: "5G Media Streaming (5GMS); General description and architecture".
[5]
TS 26.506: "5G Real-time Media Communication Architecture (Stage 2)".
[6]
TS 26.512: "5G Media Streaming (5GMS); Protocols".
[7]
TS 26.113: "Real-Time Media Communication; Protocols and APIs".
[8]
TS 26.247: "Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)".
[9]
TS 26.118: "Virtual Reality (VR) profiles for streaming applications".
[10]
ITU-T Recommendation X.509 (2005) | ISO/IEC 9594-8:2005: "Information Technology - Open Systems Interconnection - The Directory: Public-key and attribute certificate frameworks".
[11]
RFC 5280: "Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile", May 2008.
[12]
RFC 7468: "Textual Encodings of PKIX, PKCS, and CMS Structures", April 2015.
[13]
TS 23.558: "Architecture for enabling edge applications".
[14]
TS 24.558: "Enabling Edge Applications; Protocol specification".
[15]
TS 29.558: "Enabling Edge Applications; Application Programming Interface (API) specification; Stage 3".
[16]
TS 23.003: "Numbering, addressing and identification".
[17]
TS 23.503: "Policy and charging control framework for the 5G System (5GS); Stage 2".
[18]
TS 29.514: "5G System; Policy Authorization Service; Stage 3".
[19]
TS 29.522: "5G System. Network Exposure Function Northbound APIs; Stage 3".
[20]
TS 29.122: "T8 reference point for Northbound APIs".
[21]
TS 27.007: "AT Command set for User Equipment (UE)".
[22]
TS 38.321: "NR; Medium Access Control (MAC) protocol specification".
[23]
TS 36.321: "Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification".
[24]
RFC 9110: "HTTP Semantics", June 2022.
[25]
RFC 9111: "HTTP Caching", June 2022.
[26]
RFC 9112: "HTTP/1.1", June 2022.
[27]
RFC 9113: "HTTP/2", June 2022.
[28] Reserved for future use.
[29]
RFC 8446: "The Transport Layer Security (TLS) Protocol Version 1.3", August 2018.
[30]
TS 29.500: "5G System; Technical Realization of Service Based Architecture; Stage 3".
[31]
TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[32]
OpenAPI: "OpenAPI 3.0.0 Specification", https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md .
[33]
TS 29.571: "Common Data Types for Service Based Interfaces; Stage 3".
[34]
RFC 3339: "Date and Time on the Internet: Timestamps", July 2002.
[35]
RFC 3986: "URI Generic Syntax", June 2005.
[36]
Standard ECMA-262, 5.1 Edition: "ECMAScript Language Specification", June 2011.
[37]
RFC 8259: "The JavaScript Object Notation (JSON) Data Interchange Format", December 2017.
[38]
draft-bhutton-json-schema-validation: "JSON Schema Validation: A Vocabulary for Structural Validation of JSON", June 2022.
[39]
TS 29.517: "5G System; Application Function Event Exposure Service; Stage 3".
[40]
TS 26.532: "Data Collection and Reporting; Protocols and Formats".
[41]
ISO 3166-1: "Codes for the representation of names of countries and their subdivisions - Part 1: Country codes".
[42]
ISO 3166-2: "Codes for the representation of names of countries and their subdivisions - Part 2: Country subdivision code".
[43]
RFC 2474: "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers", December 1998.
[44]
RFC 3246: "An Expedited Forwarding PHB (Per-Hop Behavior)", March 2022.
[45]
RFC 2597: "Assured Forwarding PHB Group", June 1999.
[46]
TS 29.554: "5G System; Background Data Transfer Policy Control Service; Stage 3".
[47]
RFC 6749: "The OAuth 2.0 Authorization Framework", October 2012.
[48]
TS 29.222: "Common API Framework for 3GPP Northbound APIs; Stage 3".
[49]
RFC 7230: "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing", June 2014.
[50]
OASIS: "MQTT Version 5.0", https://docs.oasis-open.org/mqtt/mqtt/v5.0/mqtt-v5.0.html
[51]
RFC 7519: "JSON Web Token (JWT)", May 2015.
3 Definitions of terms, symbols and abbreviations p. 20
3.1 Terms p. 20
For the purposes of the present document, the terms given in TR 21.905, TS 26.501, TS 26.506 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905, TS 26.501 or TS 26.506.
Media EAS:
Media Application Server deployed as an Edge Application Server.
Media Delivery System:
A deployment of a 5GMS System or RTC System.
media delivery session:
the time interval during which media is delivered between a Media AS and one or more Media Client participants via reference point M4 at the initiation of an application (which may be a Media-aware Application) associated with each participating Media Client.
media delivery session identifier:
a string that uniquely identifies a media delivery session in a Media Delivery System for the purpose of collating information from different system functions.
3.2 Symbols p. 20
Void.
3.3 Abbreviations p. 20
For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
5GC
5G Core
AF
Application Function
ANBR
Access Network Bit rate Recommendation
API
Application Programming Interface
AS
Application Server
BDT
Background Data Transfer
CHEM
Coverage and Handoff Enhancements using Multimedia error robustness
DN
Data Network
DS
Differentiated Services
DSCP
DS Code Point
EAS
Edge Application Server
EEC
Edge Enabler Client
EES
Edge Enabler Server
FQDN
Fully Qualified Domain Name
GPSI
Generic Public Subscription Identifier
ICE
Interactive Connectivity Establishment
JSON
JavaScript Object Notation
MFBR
Maximum Flow Bit Rate
NEF
Network Exposure Function
OAM
Operations, Administration and Maintenance
PCC
Policy Control and Charging
PCF
Policy Control Function
PDR
Packet Detection Rule
PHB
Per-Hop Behaviour
QoE
Quality of Experience
QoS
Quality of Service
QFI
QoS Flow Identifier
RTC
Real-Time (media) Communication
STUN
Session Traversal Utilities for NAT, Simple Traversal of User Datagram Protocol (UDP) through Network Address Translators
SWAP
Simple WebRTC Application Protocol
TCP
Transmission Control Protocol
TOS
Type of Service
TURN
Traversal Using Relays around NAT
UE
User Equipment
URI
Uniform Resource Identifier
URL
Uniform Resource Locator
