FAQ

What is LTE Broadcast and what services does it provide?
LTE Broadcast is a technology specified as part of 3GPP LTE standards and it provides streaming and file download services. As an example, at a sporting venue, providing streaming video and real-time sport statistics.

What is the purpose of LTE Broadcast SDK?
The LTE Broadcast SDK enables Android developers to create Android applications for streaming and file delivery services using Evolved Multimedia Broadcast Multicast Service (eMBMS), a technology specified as part of 3GPP LTE standards.

Who can use the LTE Broadcast SDK?
Android developers who design and develop eMBMS applications in conjunction with carriers providing LTE Broadcast service.

What kind of application can be built using LTE Broadcast SDK?
You can build Android applications which uses LTE Broadcast for providing streaming or file download services.

What is included in the LTE Broadcast SDK package?
The LTE Broadcast SDK package contains two components Multicast Services Device Client (MSDC) API and DASH Player API with the following contents:

  • MSDC API
    • API Specification
    • API library: This library has the implementation of the API
    • Test tool: API Stub tool generates notifications for testing the application which uses the API
      • API Stub User Guide
      • API Stub library: This library includes the implementation of API Stub tool
      • Stub_config.xml : This file includes a sample configuration for the Stub tool
  • DASH Player API
    • API Specification
    • API library: This library has the implementation of the API

Is there any tool to test the API usage in the application?
Yes. The API Stub is a tool included in the SDK which facilitates testing of the API by generating the notifications based on the calls from the application for specific use cases using a configuration file.

Which mobile devices support LTE Broadcast?
The Android application developers can use Stub tool to test their application on any Android device. However the developers need to work with their carrier or handset manufacturer to determine the target device which has been LTE Broadcast enabled.

How can the LTE Broadcast application be tested end-to-end on a network?
The Android application developers need to work with their carrier or handset manufacturer to obtain access to a test network.

What are the differences between LTE Broadcast SDK version 3.6 and 4.0?
Service Continuity feature: The Service Continuity feature enables the MBMS middleware to provide DASH streaming services for applications while the UE is in or out of broadcast coverage for the service, as specified in Multimedia Broadcast/Multicast Service (MBMS); Protocols and codec (3GPP TS 26.346).

DASH SDK streaming playback will leverage reception via unicast and broadcast with the reception transitions across the two being transparent to the application.

The application can know via the service availability flag whether the service is being consumed via unicast or broadcast, or whether the service is not available at the current UE location.

What are the differences between LTE Broadcast SDK version 3.6.1 and 3.6?
DASH Player API: The LTE Broadcast SDK now also includes a DASH player for optional use which allows developers to build applications for playback of DASH encoded content with the media player on Android-based devices.

What are the differences between LTE Broadcast SDK version 3.5 and 3.6?

  • Connection to remote MSDC middleware running on mobile broadband product – The MSDC API supports discovering and connecting to a remote MSDC middleware running on mobile broadband product per app request. If the MSDC middleware is also installed on the local device where the UI client is running, the MSDC API can switch between the local and remote MSDC when remote connection is lost or a remote MSDC is discovered.
  • File download progress report – Provides the app with download progress notifications while a requested file is being downloaded. The UI application can signal its interest in receiving file download progress reports when calling the start file capture API.
  • Added serviceAnnouncementServiceAreaIdList to serviceInfo. “serviceAnnouncementServiceAreaIdList” contains the list of SAIs defined in the Service Announcement file received by the MSDC middleware.
  • Added a copyDownloadedFiles option to the file delivery initialization API. When set to true, the MSDC API copies the files or fetches them from the HTTP server to the app internal storage.
  • Added file delivery warning, WARNING_FD_STORAGE_LOCATION_COPY_FAILED, to notify the UI when copying a file to the specified storage location fails.
  • Added MSDC error, ERROR_MSDC_EMBMS_SERVICE_NOT_AVAILABLE to MSDC API. The UI application receives this when there is no EMBMS service (embms.apk) installed on the device.

How can I get support for my technical questions regarding API usage?
For support information, please check out the LTE Broadcast SDK forum.