Tech-invite  3GPPspace  IETFspace
◀  ▶  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:  19.2.0

Top   Top   Up   Prev   Next
1…   4…   4.1…   4.2…   4.3…   4.4   4.5…   4.6…   4.7…   4.8   4.9…   4.10…   4.11…   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.7.9…   5.8…   5.10…   5.10.3   5.10.4   5.10.5…   5.10.6…   5.10.7   5.11…   5.12…   5.12.3   5.12.4…   5.12.5…   5.13…   5.14…   6…   6.2…   6.2.2.2…   6.2.3…   6.3…   6.4…   6.8…   6.9…   6.9.5…   6.9.7   6.9.8…   7…   8…   8.2   9…   A…   A.4…   A.8…   A.11…   A.13…   A.15…   A.16…   B…   C…   D…   E…   F…   G…   G.2…   G.3…   H… 
5.10.7 Service URL handling procedures for 5GMSd via eMBMS in Receive-Only Mode (ROM) 
...

 

5.10.7  Service URL handling procedures for 5GMSd via eMBMS in Receive-Only Mode (ROM) |R18|  p. 159

In an extension to the procedures provided in clauses 5.10.2 and 9.1, this clause defines a call flow in order to initiate a 5GMSd streaming session delivered via eMBMS without needing to contact the network, for example as done in Receive-Only Mode (ROM).
The call flow in Figure 5.10.7-1 extends those defined in clauses 5.10.2 and 9.1 to address 3GPP Service URL handling. Aspects specific to this use-case are indicated in bold.
Copy of original 3GPP image for 3GPP TS 26.501, Fig. 5.10.7-1: High-level procedure for DASH content delivery via eMBMS with 3GPP Service URL
Figure 5.10.7-1: High-level procedure for DASH content delivery via eMBMS with 3GPP Service URL
(⇒ copy of original 3GPP image)
Up
Prerequisites (step 0):
  • The 5GMSd Application Provider has provisioned the 5GMSd System, including content ingest and the authorization to distribute 5GMSd content via eMBMS.
  • The 5GMSd AF has informed the BM-SC about the availability of 5GMSd content by provisioning an MBMS service and has obtained relevant information from the eMBMS Service Announcement (such as the MBMS service identifier).
  • Based on the information, the 5GMSd Application Provider has generated a 3GPP Service URL with sufficient information for the Media Session Handler and MBMS Client to access the service.
  • The BM-SC is ingesting content from the 5GMSd AS.
  • The BM-SC has broadcast the MBMS Service Announcement, including an indication that the content is 5GMSd content.
Steps:
Step 1.
The 5GMSd-Aware Application triggers the Service Announcement procedure and the 5GMS Service and Content Discovery procedure at reference point M8. The information returned to the 5GMSd-Aware Application includes a 3GPP Service URL indicating a 5GMS-based service and also includes relevant information from the eMBMS Service Announcement (such as the MBMS service identifier).
Step 2.
A media content item is selected.
Step 3.
The 5GMSd-Aware Application triggers the 5GMSd Client to start media playback. The 3GPP Service URL describing the service is requested and the Media Session Handler handles it.
Step 4.
The Media Session Handler uses the Service URL information to extract relevant information from the eMBMS Service Announcement (such as the MBMS service identifier) in order to bootstrap reception of the MBMS service.
Step 5.
The Media Session Handler provides the Service Access information to the MBMS Client.
Finally, the MBMS Service is launched as defined in steps 5-25 of clause 5.10.2.
Up

Up   Top   ToC