Content for TS 26.501 Word version: 18.0.0
1…
4…
4.2…
4.2.2…
4.3…
4.5…
4.6…
4.7…
5…
5.2…
5.3…
5.3.2
5.4…
5.5…
5.5.3…
5.6…
5.7…
5.7.3
5.7.4…
5.8
5.9…
5.10…
5.10.5
5.10.6
5.11…
6…
6.2…
6.3…
6.5…
6.8…
7…
8…
8.2
A…
A.3…
A.5…
A.7…
A.9
A.10
A.11
A.12
A.13
A.14
A.15
B…
B.3
C…
C.3
C.4
C.5
D…
A.3 Downlink media streaming with both AF and AS deployed in an external Data Network (OTT)
A.4 Downlink media streaming with AF deployed in the trusted Data Network and AS deployed in an external Data Network
...
...
A.3 Downlink media streaming with both AF and AS deployed in an external Data Network (OTT) p. 110
The collaboration scenario shown in Figure A.3-1 represents a typical OTT collaboration scenario, where the 5GMSd AF and 5GMSd AS are deployed in an external Data Network. The 5GMSd AF interacts with the NEF via N33. The Provisioning API (M1d') and Ingest API (M2d') may follow 5GMS specifications.
Figure A.3-1: Downlink media streaming with AF and AS in an external Data Network (OTT)
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
A.4 Downlink media streaming with AF deployed in the trusted Data Network and AS deployed in an external Data Network p. 110
This collaboration scenario shown in Figure A.4-1 depicts a content hosting function in the external Data Network, e.g. using a third-party CDN in collaboration with MNO offered assistance and network services. The Provisioning API (M1d') and Ingest API (M2d') may follow 5GMS specifications.
Figure A.4-1: Downlink media streaming with AF in the trusted Data Network and AS in external Data Network
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
Interfaces M1d' and M2d' may be similar to interfaces M1d and M2d respectively. Interface M4d follows 5GMS specifications.
