Content for TS 23.246 Word version: 18.0.0

1… 4… 4.4… 4.4.3… 5… 6… 7… 8… 8.3… 8.4 8.5… 8.6… 8.7 8.8… 8.9… 8.10… 8.11… 8.16… 9… C D… E…

...

C (Normative) TV services delivery using unicast mode & switching between broadcast & unicast modes for E-UTRAN |R18| p. 70

To enable TV services delivery using unicast mode of transport, the applicable functions need to be enabled in the operator's network:

UE:

Able to support TV services as required including:

For Unicast support, there needs to be additional PDN connection via dedicated APN for TV services delivery.

NOTE:
It can require explicit connection towards TV Content Provider for Unicast reachability information (e.g. IP addresses, ports, etc.). UE should be configured with appropriate APN to facilitate easy access to TV services via unicast.
Ability to support Consumption Reporting and MooD feature for enabling switching between broadcast and unicast operation on demand, if required.

Content Provider/Packet Streaming Server needs to provide the required functions for MBMS Broadcast services as defined in this specification. The operator needs to enable access to the transport and MBMS user services towards TV content providers, if required, as described in clause 7.5.

MME:

If APN is configured in the HSS for enabling unicast delivery for TV services for the user, then MME checks when UE provides an APN and verifies that the user has subscription for that APN against the HSS provided APN, using existing procedures.

HSS:

Shall be configured well known dedicated APN in the user's subscription for Unicast TV services support when dedicated PDN connectivity for TV services is required.

The main deployment options for TV services are, but not limited to :

Deployment Option 1:

Joint broadcast + unicast TV service through BM-SC and PDN GW via SGi.

Scenario A:

The Content Provider has a Service Level Agreement with an operator. The dedicated TV service includes a TV Service subscription associated with the operator subscription, which allows tuning to TV unicast and MBMS broadcast for transport.

In case popularity based switching according to MBMS operations on Demand (MooD, TS 26.346) is supported, then:

The operator monitors the TV service consumption per channel in areas and decide to use unicast or MBMS broadcast usage.

According to the agreement between the Content Provider and the operator, the operator may provide usage information to the Content Provider.

Scenario B:

This Scenario enables the realization for multi-purpose devices, where the managing operator provides all functionality.

In case popularity based switching according to MBMS operations on Demand (MOOD, TS 26.346) is supported, then:

The operator monitors the TV service consumption per channel in areas and decide to use unicast or MBMS broadcast transport.

According to the agreement between the Content Provider & the operator, the operator may provide usage information to the Content Provider.

Deployment option 2:

Separate direct broadcast service through BM-SC and direct unicast service via SGi through PDN GW.

For Unicast TV transport, the Content Provider uses regular unicast data connectivity. For MBMS broadcast, the Content Provider provides the content of the TV channel via user plane.

In case popularity based switching according to MBMS operations on Demand (MooD, TS 26.346) is supported, then:

The Content Provider monitors the popularity of the TV service over Unicast, for each operator individually.
When unicast TV service usage of a channel is high in a certain area, the Content Provider interacts with operator in order to activate MBMS Broadcast in the identified area.

In order to monitor popularity in the MBMS Broadcast Areas, the operator can expose popularity information (derived from HTTP Consumption Reporting, TS 26.346) to the Content Provider via dedicated provisioning interface (see TS 26.348).