Content for TS 26.501 Word version: 18.6.0
1…
4…
4.0.6…
4.1…
4.2…
4.2.2…
4.3…
4.4
4.5…
4.6…
4.7…
4.7.4…
4.8
4.9…
4.10…
5…
5.2…
5.2.4
5.2.5…
5.3…
5.3.2…
5.4…
5.5…
5.6…
5.7…
5.7.4…
5.7.8
5.8…
5.10…
5.10.5…
5.10.6…
5.11…
5.12…
5.12.4…
5.12.5…
6…
6.2…
6.2.2.2…
6.2.3…
6.3…
6.4…
6.8…
6.9…
6.9.5…
6.9.7
7…
8…
9…
A…
A.4…
A.8
A.9
A.10
A.11
A.12
A.13
A.14
A.15…
A.15.3…
B…
B.3
C…
C.3
C.4
C.5
D…
E…
A.4 Downlink media streaming with AF deployed in the trusted Data Network and AS deployed in an external Data Network
A.5 Downlink media streaming with AS deployed in an external Data Network, provisioned by AF deployed in the trusted Data Network
A.6 Downlink media streaming with AS deployed in the trusted Data Network, provisioned by AF deployed in an external Data Network
A.7 Downlink media streaming with both AF and AS deployed in the trusted Data Network and AF interaction with PCF
...
...
A.4 Downlink media streaming with AF deployed in the trusted Data Network and AS deployed in an external Data Network p. 195
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.
A.5 Downlink media streaming with AS deployed in an external Data Network, provisioned by AF deployed in the trusted Data Network p. 196
The collaboration scenario shown in Figure A.5-1 is similar to that depicted in clause A.4 with the difference that the external content hosting function (5GMSd AS) is provisioned from a 5GMSd AF which is located in a trusted Data Network. It is expected that a 5GMSd AF and 5GMSd AS from different providers are interconnected using an M3d interface. The Ingest API (M2d') may follow 5GMS specifications.
Figure A.5-1: Downlink media streaming with AS in external Data Network, provisioned by AF in the trusted Data Network
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
Interface M2d' may be similar to interface M2d. All other interfaces depicted follow 3GPP specifications.
A.6 Downlink media streaming with AS deployed in the trusted Data Network, provisioned by AF deployed in an external Data Network p. 197
The collaboration scenario shown in Figure A.6-1 is similar to those depicted in clauses A.4 and A.5 with the difference that the trusted content hosting function (5GMSd AS) is provisioned from an external 5GMSd AF. It is expected that a 5GMSd AF and 5GMSd AS from different providers are interconnected using an M3d interface. The Provisioning API (M1d') may follow 5GMS specifications. Interactions between the externally-deployed 5GMSd AF and the PCF are proxied via the NEF at reference point N33.
Figure A.6-1: Downlink media streaming with AS in the trusted Data Network, provisioned by AF in external Data Network
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
The interface at reference point M1d' may be similar to that defined at reference point M1d. All other interfaces depicted follow 3GPP specifications.
A.7 Downlink media streaming with both AF and AS deployed in the trusted Data Network and AF interaction with PCF p. 197
The collaboration scenario shown in Figure A.7-1 represents a MNO CDN scenario (similar to that in clause A.2) where the CDN is used for ingest and delivery of the content. Additional 5GMS features are used which require interaction with the PCF.
Figure A.7-1: Downlink media streaming with AF and AS in the trusted Data Network
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
