Tech-invite3GPPspaceIETFspace
idxwho21222324252627282931323334353637384‑5x

Content for  TS 26.501  Word version:  18.0.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.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…

 

C  Collaboration Models for 5GMS via eMBMS |R17|p. 136

C.1  Introductionp. 136

For 5GMS via eMBMS as introduced in clauses 4.6 and 5.10, different deployment collaboration scenarios of the architecture as provided in clause 4.6 may be considered. In all cases, the same UE architecture is used, but different network side operation modes are considered, including the following parties:
  • 5G Mobile Network Operator: A party that offers 5G System reference points to a content provider.
  • 5G Broadcast Network Operator: A party that offers eMBMS reference points to a third party.
  • 5GMS Content Provider: A party that provides 5GMS content.
  • 5GMS Network Operator: A party that offers 5GMS System reference points to a content provider.
  • 5G Broadcast Service Provider: A party that offers 5GMS content via eMBMS and also provides the same content to a 5G Mobile Network Operator.
  • 5GMS Service Provider: A party that distributes 5GMS content via a 5G System and via eMBMS.
Up

C.2  Collaboration 5GMS-MBMS 1: 5GMS Content Provider uses different delivery networksp. 136

Figure C.2-1 illustrates a collaboration in which the 5GMS Content Provider uses different delivery networks.
Copy of original 3GPP image for 3GPP TS 26.501, Fig. C.2-1: Collaboration 5GMS-MBMS 1: 5GMS Content Provider uses different delivery networks
Up

Up   Top   ToC