Forums - Middleware Android Operator specific.

4 posts / 0 new
Last post
Middleware Android Operator specific.
david.rupprecht
Join Date: 11 Dec 19
Posts: 3
Posted: Sun, 2020-03-29 08:34

Dear all,

My goal is to display  video which is broadcasted via embms broadcasted in an app. I would like to you my own LTE setup, eg., srsLTE or Amarisoft.  To do so, I got some questions:

- Is there any good possibility to determine if an Android phone has the middleware installed? I have currently access to a Xiaomi Mix 3 5G.

- Is the OEM middleware provider specific? If the middleware is installed, does it work if I use my own LTE config. In particular, set my own PLMN ID?

- With the example app (msdc_sdk_4.3.00.00.zip)  an example is provided to recieve a streamed video. What is needed to not use the SDK Stub on the network side? I have seen that no RTP streaming is supported. What else is supported is supported besided the DASH protocol.

- BTW: is it possible to access the raw data of the embms channels?

Thanks a lot in advance,

David

  • Up0
  • Down0
vikrsing
Join Date: 29 Jan 20
Posts: 6
Posted: Sun, 2020-03-29 10:57

Hi David,

Wwe provide QAS_DVC_MSP.apk which will be installed as a system app. Also com.qualcomm.ltebc or com.qti.ltebc will be visible in the same.

This apk is our core solution on the APP side. On top of this, we also provide MSDC_UI to all the OEM's who would like to see run time functionality of the same.

Also the SDK is for the parties who want to develop their own UI to sit on top of our middleware solution.

 

The MW is generic except for VZW and RJIL who had some of their own API's .For rest all OPR our generic MW soln is fine.

For PLMN , we provide config files inside our MSDC package namely provisionin and config_params.xml. They can be modified accordingly suited for operators.

Regarding protocol, for streaming there are UDP packets received from the nw which are ALC encoded. MSDC provides these pakets to DASH client(QCT impl.) for streaming. The received packets are .mp4 files which are received in fragements from RRC/nw.MW captures and segregates them and provide them to upper layer depending upon fetch from the UI. This depends upon a framework of the FDT and the MPD files received from the nw.

Thanks,

Vikrant

  • Up0
  • Down0
david.rupprecht
Join Date: 11 Dec 19
Posts: 3
Posted: Mon, 2020-03-30 11:39

Dear Vikrant,

thank you for your fast reply.  Just for my understanding some follow-up questions.

Does the QAS_DVC_MSP.apk represent the middleware? And the SDK access the com.qualcomm.ltebc or com.qti.ltebc API of the QAS_DVC_MSP.apk system app. Thus the QAS_DVC_MSP.apk is the requiered middleware for using the LTE embms solution on the UE side.

What does nw stand for?

Thanks a lot,

David

  • Up0
  • Down0
vikrsing
Join Date: 29 Jan 20
Posts: 6
Posted: Thu, 2020-04-02 05:36

Hi David,

Yes, you understanding is correct. Our SDK API's sits and communicate on top of ur QAS_DVC_MSP.apk(our middle ware).-->LTE Broadcast solution for the App side.

By nw I meant network.

Thanks,

Vikrant

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.