IP Library Granted Patent US 8,255,929
Granted Patent B2
US 8,255,929 · App. 12/626,282 · Granted Aug 28, 2012

Method and server for providing content to a handset

Assignee: AT&T Mobility II LLC
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,255,929
App. No.
12/626,282
Granted
Aug 28, 2012
Kind
B2
Abstract

A system and method for providing time-sensitive information to a handset using a scrolling ticker. The method includes receiving the time-sensitive information at a server, determining the time period before the next update for a second set of information, and if less than a pre-determined value, then streaming the time sensitive information at the end of the time period to the handset. If the time period is greater that than the pre-determined value, then streaming the time-sensitive information immediately. In an alternative embodiment, a method is provided which includes determining a base schedule for periodically streaming the information to a handset via a scrolling ticker, receiving time-sensitive information relating to an event, determining a second schedule for periodically streaming time-sensitive information related to the event, and streaming the time-sensitive information in accordance with the second schedule during a time period associated with the event.

Claims (40)

1. A method, for providing content to a handset, comprising:

determining, at a non-event content scheduler of an application server, a non-event content delivery schedule by which non-event content is to be delivered to the handset;

determining, at an event content scheduler of the application server, an event content delivery schedule by which event content is to be delivered to the handset;

receiving, at an input interface of the application server, input data comprising non-event content or event content;

determining, at a scheduling logic component of the application server, that the input data is non-event content if a time of receipt of the input data is not within the event content delivery schedule and that the input data is event content if the time of receipt is within the event content delivery schedule;

if the time of receipt is within the event content delivery schedule:

the scheduling logic component causing an output interface of the application server to deliver the event content to the handset in accordance with the event content delivery schedule; and

the output interface delivering the event content to the handset in accordance with the event delivery schedule; and

if the time of receipt is not within the event content delivery schedule:

the scheduling logic component causing the application server to deliver the non-event content to the handset in accordance with the non-event content delivery schedule; and

the output interface delivering the non-event content to the handset in accordance with the non-event content delivery schedule.

2. The method if claim 1 , wherein the output interface delivering the event content to the handset comprises the output interface delivering the event content to the handset using a really simple syndication protocol.

3. The method of claim 1 , wherein the output interface delivering the non-event content to the handset comprises the output interface delivering the non-event content to the handset using a really simple syndication protocol.

4. The method of claim 3 , wherein the output interface delivering the non-event content to the handset comprises the output interface delivering the non-event content to the handset using a really simple syndication 2.0 standard protocol.

5. The method of claim 1 , wherein the non-event content is not time-sensitive and the event content is time-sensitive.

6. The method of claim 1 , wherein the non-event content comprises stock information, sports scores, news, or weather content.

7. The method of claim 1 , wherein the event content comprises stock information, sports scores, news, or and weather content.

8. The method of claim 1 , wherein determining, at the input interface of the application server, the event content delivery schedule includes processing a modification for the event content delivery schedule, wherein the modification is provided by a user of the handset.

9. The method of claim 1 , wherein determining, at the input interface of the application server, the event content delivery schedule includes processing a modification for the event content delivery schedule, wherein the modification is provided by an administrator.

10. The method of claim 1 , wherein the output interface delivering the event content to the handset comprises the output interface delivering the event content to the handset periodically according to the event content delivery schedule.

11. The method of claim 1 , wherein the output interface delivering the event content to the handset comprises the output interface delivering the event content to the handset a-periodically according to the event content delivery schedule.

12. The method of claim 1 , wherein the output interface delivering the event content to the handset comprises the output interface delivering the event content to the handset a-periodically according to the event content delivery schedule based upon an action that occurs during an event associated with the event content.

13. The method of claim 1 , further comprising, if the time of receipt is within the event content delivery schedule, the scheduling logic component suspending delivery of the non-event content to the handset.

14. An application server, for providing content to a handset, comprising:

at least one processor; and

a non-transitory computer-readable medium comprising instructions which, when executed by the at least one processor, cause the at least one processor to perform acts comprising:

determining a non-event content delivery schedule by which non-event content is to be delivered to the handset;

determining an event content delivery schedule by which event content is to be delivered to the handset;

receiving, via an input interface in communication with the processor, input data comprising non-event content or event content;

determining that the input data is non-event content if a time of receipt of the input data is not within the event content delivery schedule and that the input data is event content if the time of receipt is within the event content delivery schedule;

causing an output interface in communication with the processor to deliver the event content to the handset in accordance with the event content delivery schedule if the time of receipt is within the event content delivery schedule; and

causing the output interface to deliver the non-event content to the handset in accordance with the non-event content delivery schedule if the time of receipt is not within the event content delivery schedule.

15. The application server of claim 14 , wherein the the acts further comprise:

causing the output interface to deliver the event content to the handset in accordance with the event content delivery schedule using a really simple syndication protocol if the time of receipt is within the event content delivery schedule; and

causing the output interface to deliver the non-event content to the handset in accordance with the non-event content delivery schedule using the RSS protocol if the time of receipt is not within the event content delivery schedule.

16. The application server of claim 14 , wherein the instructions which, when executed by the at least one processor, cause the processor to determine the event content delivery schedule by which event content is to be delivered to the handset, causes the processor to process a modification for the event content delivery schedule, wherein the modification is provided by a user of the handset.

17. The application server of claim 14 , wherein the instructions which, when executed by the at least one processor, cause the processor to determine the event content delivery schedule, causes the processor to process a modification for the event content delivery schedule, wherein the modification is provided by an administrator.

18. The application server of claim 14 , wherein the instructions which, when executed, cause the at least one processor to cause the output interface to deliver the event content to the handset in accordance with the event content delivery schedule, cause the at least one processor to cause the output interface to deliver the event content to the handset periodically according to the event content delivery schedule.

19. The application server of claim 14 , wherein the instructions which, when executed, cause the at least one processor to cause the output interface to deliver the event content to the handset in accordance with the event content delivery schedule, cause the at least one processor to cause the output interface to deliver the event content to the handset a-periodically according to the event content delivery schedule.

20. The application server of claim 14 , wherein the instructions which, when executed, cause the at least one processor to cause the output interface to deliver the event content to the handset in accordance with the event content delivery schedule, cause the at least one processor to cause the output interface to deliver event content to the handset a-periodically according to the event content delivery schedule based upon an action that occurs during an event associated with the event content.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 9, 2016
From: LUU, ADRIANNE BINH; MIKAN, JEFFREY
To: CINGULAR WIRELESS II, LLC
Reel/Frame 037930/0336 →
CHANGE OF NAME Recorded Mar 9, 2016
From: CINGULAR WIRELESS II, LLC
To: AT&T MOBILITY II, LLC
Reel/Frame 038043/0439 →
CHANGE OF NAME Recorded Mar 9, 2016
From: AT&T MOBILITY II, LLC
To: AT&T MOBILITY II LLC
Reel/Frame 038043/0469 →
Continuity (2)
Continuation 11616593 · Dec 27, 2006
Related Publication 20100077407A1 · Mar 25, 2010