Two important aspect of eMBMS services, setting the paradigm of verticalization in concept.
xMB interface: To simplify the access to eMBMS system functionalities content providers and broadcasters can now establish the TV service through the standardized xMB (broadcasting application programming) interface, which has two aspects: xMB-C for control, and xMB-U for delivery of media content to the BM-SC. See 3GPP TS 29.116 xMB Interface and TS 33.246 Security of Multimedia Broadcast/Multicast Service (MBMS) for details.3GPP allows the inclusion of unicast distribution as a mobile system service, for example using eMBMS-operation-on-Demand (MooD) or unicast fallback (see TS 26.346 MBMS User Service Protocols and Codecs since Rel-12).
API: A new eMBMS Application Programming Interface (MBMS-API) was introduced primarily for developers of web and user applications to simplify access to complex eMBMS procedures. The API exists in the UE (the mobile system user equipment) from the eMBMS client to the Content Receiver application and is fed through xMB with relevant information to expose services to Applications (see Table 1.) This does not preclude typical mobile applications and OTT (over the top) service approaches, in which the content provider establishes a direct connection apart from any eMBMS/broadcast distribution, e.g. for service configuration and updates. Furthermore, to simplify access to the service by 3rd party applications, an MBMS URL scheme has been defined to serve as the entry point to trigger reception of an MBMS service. See 3GPP TS 26.347 MBMS APIs and URL for details.
xMB interface: To simplify the access to eMBMS system functionalities content providers and broadcasters can now establish the TV service through the standardized xMB (broadcasting application programming) interface, which has two aspects: xMB-C for control, and xMB-U for delivery of media content to the BM-SC. See 3GPP TS 29.116 xMB Interface and TS 33.246 Security of Multimedia Broadcast/Multicast Service (MBMS) for details.3GPP allows the inclusion of unicast distribution as a mobile system service, for example using eMBMS-operation-on-Demand (MooD) or unicast fallback (see TS 26.346 MBMS User Service Protocols and Codecs since Rel-12).
API: A new eMBMS Application Programming Interface (MBMS-API) was introduced primarily for developers of web and user applications to simplify access to complex eMBMS procedures. The API exists in the UE (the mobile system user equipment) from the eMBMS client to the Content Receiver application and is fed through xMB with relevant information to expose services to Applications (see Table 1.) This does not preclude typical mobile applications and OTT (over the top) service approaches, in which the content provider establishes a direct connection apart from any eMBMS/broadcast distribution, e.g. for service configuration and updates. Furthermore, to simplify access to the service by 3rd party applications, an MBMS URL scheme has been defined to serve as the entry point to trigger reception of an MBMS service. See 3GPP TS 26.347 MBMS APIs and URL for details.