Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 26.502  Word version:  17.3.0

Top   Top   Up   Prev   None
1…   4…   4.3…   4.5…   4.5.2   4.5.3…   4.6…   4.9   5…   5.3   5.4   5.5   5.6   6…   7…   A…   B…   C…   C.3…   C.4…

 

C.4  Location-dependent Object Distribution Method using push-based ingestp. 67

C.4.1  Location-dependent DASH content distribution using push-based ingestp. 67

A location-dependent MBS Serivce allows regional content variants to be distributed to different MBS Service Areas within the scope of a common MBS Session. The UE receives the content variant appropriate to its current location. This feature allows realization of MBS User Services such as local traffic information.
Copy of original 3GPP image for 3GPP TS 26.502, Fig. C.4.1-1: Location-dependent DASH content distribution using push-based ingest
Up
Two MBS Distribution Sessions with different Target service areas are provisioned. Each MBS Distribution Session has a different Object ingest base URL so that two content sources can push different media objects to the two MBS Distribution Sessions. Each content source uses a different DASH presentation manifest.
The MBSF provisions a different MBS Session in the MB-SMF for each MBS Distribution Session and arranges for the user plane traffic of each one to be distributed to the correct MBS Service Area.
The MBSTF uses a separate tunnel to inject the MBS data for each MBS Distribution Session into the MB-UPF.
The MB-UPF listens on two separate UDP ports (port#A and port#B) for the location-specific MBS data streams.
Up

C.4.2  Location-dependent generic object distribution with push-based ingestp. 68

The location-dependent MBS Serivce described in this clause is very similar to that in clause C.4.1. The difference is the distribution of a generic object stream which is not described by a manifest.
Copy of original 3GPP image for 3GPP TS 26.502, Fig. C.4.2-1: Location-dependent generic object distribution with push-based ingest
Up
As in clause C.2.3, no Object acquisition identifiers are provisioned. Any object pushed to one of the Object ingest base URLs nominated by the MBSF is distributed to the corresponding MBS Distribution Session by the MBSTF after substituting the relevant Object ingest base URL prefix with the corresponding Object distribution base URL.

$  Change historyp. 69


Up   Top