Interface for accessing evolved multimedia broadcast multicast services (eMBMS) middleware services

Patent metadata

Field	Value
Publication number	US-9397848-B2
Application number	US-201414220612-A
Country	US
Kind code	B2
Filing date	Mar 20, 2014
Priority date	Mar 20, 2014
Publication date	Jul 19, 2016
Grant date	Jul 19, 2016

Abstract

A device provides, to another device, a start request for an evolved multimedia broadcast multicast services (eMBMS) session, and receives eMBMS session traffic from the other device based on the start request. The device determines track information from the eMBMS session traffic, and decodes the eMBMS session traffic into a format understood by the device. The device determines quality information associated with the eMBMS session traffic, and presents, for display, the decoded eMBMS session traffic, the track information, and the quality information associated with the eMBMS session traffic.

First claim

What is claimed is:

1. A method, comprising:
providing, by a first device and to a second device, a start request for an evolved multimedia broadcast multicast services (eMBMS) session;
receiving, by the first device, eMBMS session traffic from the second device based on the start request;
determining, by the first device, track information associated with the eMBMS session traffic;
decoding, by the first device, the eMBMS session traffic into a format understood by the first device;
determining, by the first device, quality information associated with the eMBMS session traffic,
where determining the quality information includes:
determining a service quality indication based on a failure rate associated with the eMBMS session traffic,
the service quality indication indicating a first service quality, associated with the eMBMS session traffic, when the failure rate satisfies a particular threshold, and
the service quality indication indicating a second service quality, associated with the eMBMS session traffic, when the failure rate fails to satisfy the particular threshold; and

presenting, by the first device and for display, the decoded eMBMS session traffic, the track information, and the quality information associated with the eMBMS session traffic.

2. The method of claim 1 , further comprising:
generating a stop request for the eMBMS session;
stopping receipt of the eMBMS session traffic from the second device based on the stop request; and
stopping determination of the quality information associated with the eMBMS session traffic based on the stop request.

3. The method of claim 1 , where, prior to providing the start request for the eMBMS session to the second device, the method further comprises:
executing an eMBMS application provided on the first device;
generating a registration request for the eMBMS application based on execution of the eMBMS application;
verifying an authentication of the eMBMS application based on the registration request; and
registering the eMBMS application when the authentication of the eMBMS application is verified.

4. The method of claim 3 , where providing the start request for the eMBMS session to the second device comprises:
providing a request to start a multicast service to the second device;
presenting, for display, a service announcement associated with the multicast service and a current location of the first device; and
utilizing the eMBMS application to provide the start request for the eMBMS session to the second device.

5. The method of claim 1 , where the eMBMS session traffic includes live streaming content provided by the second device.

6. A device, comprising:
one or more memory devices to store an application, multicast middleware, and a media player; and
one or more processors to:
cause the application to:
generate a start request for an evolved multimedia broadcast multicast services (eMBMS) session, and
provide the start request to the multicast middleware;

cause the multicast middleware to:
establish the eMBMS session with another device based on the start request,
receive eMBMS session traffic, from the other device, via the eMBMS session and based on the start request,
decode the eMBMS session traffic into a format understood by the device,
determine quality information associated with the eMBMS session traffic,
the quality information including a service quality indication based on a failure rate associated with the eMBMS session traffic,
 the service quality indication indicating a first service quality, associated with the eMBMS session traffic, when the failure rate satisfies a particular threshold, and
 the service quality indication indicating a second service quality, associated with the eMBMS session traffic, when the failure rate fails to satisfy the particular threshold;

provide the decoded eMBMS session traffic and the quality information associated with the eMBMS session traffic to the media player; and

cause the media player to:
present, for display, the decoded eMBMS session traffic and the quality information associated with the eMBMS session traffic.

7. The device of claim 6 , where the one or more processors are further to:
cause the application to:
generate a stop request for the eMBMS session, and
provide the stop request to the multicast middleware; and

cause the multicast middleware to:
stop receiving the eMBMS session traffic from the other device based on the stop request, and
stop determining the quality information associated with the eMBMS session traffic based on the stop request.

8. The device of claim 6 , where, prior to generating the start request for the eMBMS session, the one or more processors are further to:
cause the application to:
initialize the multicast middleware,
generate a registration request for the application, and
provide the registration request to the multicast middleware; and

cause the multicast middleware to:
verify an authentication of the application based on the registration request, and
register the application when the authentication of the application is verified.

9. The device of claim 6 , where the application and the multicast middleware communicate via an application programming interface (API).

10. The device of claim 6 , where the eMBMS session traffic includes live streaming content provided by the other device.

11. A method, comprising:
providing, by a first device and to a second device, a start request for an evolved multimedia broadcast multicast services (eMBMS) file download;
setting, by the first device, a timer for the eMBMS file download based on the start request;
establishing, by the first device, an eMBMS session with the second device based on the start request;
receiving, by the first device and via the eMBMS session, the file from the second device, based on the start request and the setting of the timer;
decoding, by the first device, the file into a format understood by the first device;
determining, by the first device, quality information associated with the eMBMS session,
the quality information including a service quality indication based on a failure rate associated with the eMBMS session,
the service quality indication indicating a first service quality, associated with the eMBMS session, when the failure rate satisfies a particular threshold, and
the service quality indication indicating a second service quality, associated with the eMBMS session, when the failure rate fails to satisfy the particular threshold;

repairing, by the first device, the decoded file to replace missing information in the file; and
storing, by the first device, the decoded and repaired file and the quality information.

12. The method of claim 11 , further comprising:
generating a notification associated with the eMBMS file download; and
presenting, for display, the notification associated with the eMBMS file download.

13. The method of claim 11 , where, prior to providing the start request for the eMBMS file download to the other device, the method further comprises:
executing an eMBMS application provided on the first device;
generating a registration request for the eMBMS application based on execution of the eMBMS application;
verifying an authentication of the eMBMS application based on the registration request; and
registering the eMBMS application when the authentication of the eMBMS application is verified.

14. The method of claim 13 , where providing the start request for the eMBMS file download to the other device comprises:
providing a request to start a multicast service to the second

Assignees

• Cellco Partnership Dba Verizon

Inventors

• Andrada Mauricio Pati Caldeira De
• Gu John
• Kaphan Robert
• Lui Danny C

Classifications

• H04W76/002

  Electricity · mapped topic

• H04L51/38

  Electricity · mapped topic

• H04W4/06

  Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services · CPC title

• H04L12/189 Primary

  in combination with wireless systems (selective distribution or broadcast in wireless communication networks H04W4/06) · CPC title

• H04L51/58

  Message adaptation for wireless communication · CPC title