Content for TS 26.501 Word version: 16.6.1
A Usage Guidelines for collaboration scenarios
A.0 General
A.1 Collaboration 1
A.2 Collaboration 2
A.3 Collaboration 3
A.4 Collaboration 4
A.5 Collaboration 5
A.6 Collaboration 6
A.7 Collaboration 7
A.8 Collaboration 8
A.9 Collaboration 9
A Usage Guidelines for collaboration scenarios Word‑p. 69
A.0 General
This annex describes a set of collaboration scenarios and deployment options of the 5G Media Streaming architecture. The intention is to illustate different deployment options.
Note that the scenarios focus on the ownership of the functions. Scalability realizations such as a CDN are not illustrated. As result of the scalability considerations, the M4d-serving 5GMSd AS and/or M5d-serving 5GMSd AF may:
-
Consist of multiple (physical) servers, which may be addressed using a single FQDN. A load balancer forwards client requests to one of these servers. Forwarding may be via HTTP redirects or transparent towards the client.
-
Consist of multiple (physical) servers, where different servers, or different groups of servers, may be addressed with different FQDNs. The client may be made aware of this via the manifest (i.e. listing multiple base URLs).
-
Be addressed with a single FQDN. For example, the MNO AS is mostly transparent and acts as a proxy/cache.
A.1 Collaboration 1
This collaboration scenario represents a typical OTT collaboration scenario, where the 5GMSd AF and 5GMSd AS are deployed in an external Data Network.
(not reproduced yet)
Figure A.1-1: Collaboration 1
The interfaces M1d' and M2d' may be similar to interfaces M1d and M2d respectively. Interface M4d follows 3GPP specifications.
A.2 Collaboration 2 Word‑p. 70
This collaboration scenario represents a MNO CDN scenario, where the CDN is used for ingest and delivery of the content.
(not reproduced yet)
Figure A.2-1: Collaboration 2
A.3 Collaboration 3
This collaboration scenario 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.
(not reproduced yet)
Figure A.3-1: Collaboration 3
A.4 Collaboration 4 Word‑p. 71
This collaboration scenario 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.
(not reproduced yet)
Figure A.4-1: Collaboration 4
Interfaces M1d' and M2d' may be similar to interfaces M1d and M2d respectively. Interface M4d follows 5GMS specifications.
A.5 Collaboration 5
This collaboration scenario is similar to Collaboration 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.
(not reproduced yet)
Figure A.5-1: Collaboration 5
Interface M2d' may be similar to interface M2d. All other interfaces depicted follow 3GPP specifications.
A.6 Collaboration 6 Word‑p. 72
This collaboration scenario is similar to Collaboration 4 and Collaboration 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.
(not reproduced yet)
Figure A.6-1: Collaboration 6
Interface M1d' may be similar to interface M1d. All other interfaces depicted follow 3GPP specifications.
A.7 Collaboration 7
This collaboration scenario represents a MNO CDN scenario (like in Collaboration 2) where the CDN is used for ingest and delivery of the content. Additional 5GMS features are used which require interaction with the PCF.
(not reproduced yet)
Figure A.7-1: Collaboration 7
A.8 Collaboration 8 Word‑p. 73
This collaboration scenario represents a multi-MNO distribution scenario where an external CDN (5GMSd AS) is used to deliver content through multiple 5GMSd capable PLMNs. Additional 5GMSd features are used from the serving 5GMS System which need interactions with the PCF of the serving PLMN.
(not reproduced yet)
Figure A.8-1: Collaboration 8
A.9 Collaboration 9 Word‑p. 74
This collaboration scenario represents a multi-MNO distribution scenario where an external CDN (5GMSd AS) is used to deliver content through multiple 5GMSd-capable PLMNs. Additional 5GMSd features are used from the serving 5GMSd system which need interactions with the NEF of the serving PLMN.
(not reproduced yet)
Figure A.9-1: Collaboration 9
A.0 General
This annex describes a set of collaboration scenarios and deployment options of the 5G Media Streaming architecture. The intention is to illustate different deployment options.
Note that the scenarios focus on the ownership of the functions. Scalability realizations such as a CDN are not illustrated. As result of the scalability considerations, the M4d-serving 5GMSd AS and/or M5d-serving 5GMSd AF may:
- Consist of multiple (physical) servers, which may be addressed using a single FQDN. A load balancer forwards client requests to one of these servers. Forwarding may be via HTTP redirects or transparent towards the client.
- Consist of multiple (physical) servers, where different servers, or different groups of servers, may be addressed with different FQDNs. The client may be made aware of this via the manifest (i.e. listing multiple base URLs).
- Be addressed with a single FQDN. For example, the MNO AS is mostly transparent and acts as a proxy/cache.
A.1 Collaboration 1
This collaboration scenario represents a typical OTT collaboration scenario, where the 5GMSd AF and 5GMSd AS are deployed in an external Data Network.
(not reproduced yet)
Figure A.1-1: Collaboration 1
The interfaces M1d' and M2d' may be similar to interfaces M1d and M2d respectively. Interface M4d follows 3GPP specifications.
A.2 Collaboration 2 Word‑p. 70
This collaboration scenario represents a MNO CDN scenario, where the CDN is used for ingest and delivery of the content.
(not reproduced yet)
Figure A.2-1: Collaboration 2
A.3 Collaboration 3
This collaboration scenario 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.
(not reproduced yet)
Figure A.3-1: Collaboration 3
A.4 Collaboration 4 Word‑p. 71
This collaboration scenario 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.
(not reproduced yet)
Figure A.4-1: Collaboration 4
Interfaces M1d' and M2d' may be similar to interfaces M1d and M2d respectively. Interface M4d follows 5GMS specifications.
A.5 Collaboration 5
This collaboration scenario is similar to Collaboration 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.
(not reproduced yet)
Figure A.5-1: Collaboration 5
Interface M2d' may be similar to interface M2d. All other interfaces depicted follow 3GPP specifications.
A.6 Collaboration 6 Word‑p. 72
This collaboration scenario is similar to Collaboration 4 and Collaboration 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.
(not reproduced yet)
Figure A.6-1: Collaboration 6
Interface M1d' may be similar to interface M1d. All other interfaces depicted follow 3GPP specifications.
A.7 Collaboration 7
This collaboration scenario represents a MNO CDN scenario (like in Collaboration 2) where the CDN is used for ingest and delivery of the content. Additional 5GMS features are used which require interaction with the PCF.
(not reproduced yet)
Figure A.7-1: Collaboration 7
A.8 Collaboration 8 Word‑p. 73
This collaboration scenario represents a multi-MNO distribution scenario where an external CDN (5GMSd AS) is used to deliver content through multiple 5GMSd capable PLMNs. Additional 5GMSd features are used from the serving 5GMS System which need interactions with the PCF of the serving PLMN.
(not reproduced yet)
Figure A.8-1: Collaboration 8
A.9 Collaboration 9 Word‑p. 74
This collaboration scenario represents a multi-MNO distribution scenario where an external CDN (5GMSd AS) is used to deliver content through multiple 5GMSd-capable PLMNs. Additional 5GMSd features are used from the serving 5GMSd system which need interactions with the NEF of the serving PLMN.
(not reproduced yet)
Figure A.9-1: Collaboration 9
This collaboration scenario 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.
(not reproduced yet)
Figure A.4-1: Collaboration 4
Interfaces M1d' and M2d' may be similar to interfaces M1d and M2d respectively. Interface M4d follows 5GMS specifications.
A.5 Collaboration 5
This collaboration scenario is similar to Collaboration 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.
(not reproduced yet)
Figure A.5-1: Collaboration 5
Interface M2d' may be similar to interface M2d. All other interfaces depicted follow 3GPP specifications.
A.6 Collaboration 6 Word‑p. 72
This collaboration scenario is similar to Collaboration 4 and Collaboration 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.
(not reproduced yet)
Figure A.6-1: Collaboration 6
Interface M1d' may be similar to interface M1d. All other interfaces depicted follow 3GPP specifications.
A.7 Collaboration 7
This collaboration scenario represents a MNO CDN scenario (like in Collaboration 2) where the CDN is used for ingest and delivery of the content. Additional 5GMS features are used which require interaction with the PCF.
(not reproduced yet)
Figure A.7-1: Collaboration 7
A.8 Collaboration 8 Word‑p. 73
This collaboration scenario represents a multi-MNO distribution scenario where an external CDN (5GMSd AS) is used to deliver content through multiple 5GMSd capable PLMNs. Additional 5GMSd features are used from the serving 5GMS System which need interactions with the PCF of the serving PLMN.
(not reproduced yet)
Figure A.8-1: Collaboration 8
A.9 Collaboration 9 Word‑p. 74
This collaboration scenario represents a multi-MNO distribution scenario where an external CDN (5GMSd AS) is used to deliver content through multiple 5GMSd-capable PLMNs. Additional 5GMSd features are used from the serving 5GMSd system which need interactions with the NEF of the serving PLMN.
(not reproduced yet)
Figure A.9-1: Collaboration 9
This collaboration scenario represents a multi-MNO distribution scenario where an external CDN (5GMSd AS) is used to deliver content through multiple 5GMSd capable PLMNs. Additional 5GMSd features are used from the serving 5GMS System which need interactions with the PCF of the serving PLMN.
(not reproduced yet)
Figure A.8-1: Collaboration 8
A.9 Collaboration 9 Word‑p. 74
This collaboration scenario represents a multi-MNO distribution scenario where an external CDN (5GMSd AS) is used to deliver content through multiple 5GMSd-capable PLMNs. Additional 5GMSd features are used from the serving 5GMSd system which need interactions with the NEF of the serving PLMN.
(not reproduced yet)
Figure A.9-1: Collaboration 9