Tech-invite  3GPPspace  IETF RFCs  SIP
Quick  21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 26.501  Word version:  17.3.0

Top   Top   Up   Prev   Next
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.3…   6.5…   6.8   7…   8…   8.2   A…   A.3…   A.5…   A.7…   A.9   B…   B.3   C…   C.3   C.4   C.5   D… 
A.3 Collaboration 3  A.4 Collaboration 4 
...

 

A.3  Collaboration 3  p. 102

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.
Copy of original 3GPP image for 3GPP TS 26.501, Fig. A.3-1: Collaboration 3
Figure A.3-1: Collaboration 3
(⇒ copy of original 3GPP image)
Up

A.4  Collaboration 4  p. 103

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.
Copy of original 3GPP image for 3GPP TS 26.501, Fig. A.4-1: Collaboration 4
Figure A.4-1: Collaboration 4
(⇒ copy of original 3GPP image)
Up
Interfaces M1d' and M2d' may be similar to interfaces M1d and M2d respectively. Interface M4d follows 5GMS specifications.

Up   Top   ToC