US20080185772A1 - Systems and methods for a graceful push handling user interface - Google Patents
Systems and methods for a graceful push handling user interface Download PDFInfo
- Publication number
- US20080185772A1 US20080185772A1 US11/702,736 US70273607A US2008185772A1 US 20080185772 A1 US20080185772 A1 US 20080185772A1 US 70273607 A US70273607 A US 70273607A US 2008185772 A1 US2008185772 A1 US 2008185772A1
- Authority
- US
- United States
- Prior art keywords
- push
- electronic device
- mobile electronic
- push feed
- feed
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
Definitions
- the present invention relates to push handling user interfaces and specifically to the removal of expired push feeds.
- Push feeds or push media refer to any mechanism for distributing media or feeds where content is provided at the request of the content provider and not the user. Push feeds are advantageous in that the information is sent as soon as it is available without requiring action from the recipient.
- Push feeds are used in mobile electronic devices to instantly send information and web links to users. Since the push feeds are automatically sent to the user, unless they are deleted, the push feeds will typically accumulate on the user's mobile electronic device. The user has to manually delete unwanted push feeds, which can be time consuming and frustrating. Some mobile electronic devices permit the user to set preferences related to the deletion of push feeds. Although the user does not have delete each individual push feed, setting up preferences can be time consuming. Therefore, a method and system is needed to automatically manage push feeds on a mobile electronic device that does not require any input from the user.
- embodiments of the present invention systems and methods for the graceful removal of push feeds from a mobile electronic
- the claimed invention relates to a method for the graceful handling of push feeds in a mobile electronic device including sending a push feed to a mobile electronic device, waiting a predetermined amount of time, and instructing the mobile electronic device to delete the push feed.
- the method may further include sending a new push feed to the mobile electronic device, identifying the push feed as new to the user, and/or providing notification to the user as to when the push feed will be deleted.
- the notification may include altering the graphical look of the push feed or applying a timestamp to the new push feed.
- the predetermined amount of time may be, for example, thirty seconds, sixty seconds, five minutes, or sixty minutes.
- the push feed is a channel.
- Another aspect of the invention relates to a method for the graceful handling of push feeds in a mobile electronic device including receiving a push feed, displaying the push feed, and after a predetermined amount of time, deleting the push feed.
- the predetermined amount of time may be included with the push feed as received.
- the method may further include receiving a new push feed, identifying the push feed as new to the user, and/or providing notification to the user as to when the push feed will be deleted.
- the notification may include altering the graphical look of the push feed or applying a timestamp to the new push feed.
- a clock internal to the mobile electronic device determines the predetermined amount of time.
- the system includes a server for transmitting data having a first CPU and a first interface and a mobile electronic device having a second CPU and a display for receiving data from a server.
- the mobile electronic device is configured to receive a push feed, display the push feed, and after a predetermined amount of time, delete the push feed.
- the predetermined amount of time may be included with the push feed as received.
- the system may be further configured to receive a new push feed.
- the system includes a server for transmitting data having a first CPU and a first interface, and a mobile electronic device having a second CPU and a display for receiving data from the server.
- the server is configured to send a push feed, wait a predetermined amount of time, and instruct the mobile electronic device to delete the push feed.
- the system may be further configured to send a new push feed.
- FIG. 1 is a high level flow chart of a method for gracefully removing push feeds from a mobile electronic device according to one embodiment of the present invention.
- FIG. 2 is a high level flow chart of a method for gracefully removing push feeds from a mobile electronic device according to another embodiment of the present invention.
- FIG. 3 is a diagram of system for gracefully removing push feeds from a mobile electronic device according various embodiments of the present invention.
- Push feeds are headlines or links to more information that may be sent to a mobile electronic device.
- the push feeds may be customizable or may have mass appeal. Examples of push feeds include breaking news headlines, stock information, web links that are updated periodically, small images such as thumbnails, video files, audio files, and the weather. Since these push feeds are sent automatically and are time sensitive, i.e. headlines, stocks, and the weather change from day to day and even from hour to hour, the push feeds need to be refreshed and the outdated or stale push feeds need to be removed. For example, a weather report is sent to a mobile electronic device on day 1 . On day 2 , the weather report for day 1 is outdated and inaccurate. Thus, a new weather report must be sent on day 2 . Since the weather report from day 1 is stale, it can be deleted from the mobile electronic device.
- the claimed invention generally relates to a system and method whereby push feeds are removed from a mobile electronic device without the involvement of the user of the mobile electronic device.
- the push feeds may be expunged from the mobile electronic device gracefully or automatically by either the mobile electronic device or a server that provides the push feeds.
- FIG. 1 is a high level flow chart of a method for gracefully removing push feeds from a mobile electronic device according to an embodiment of the present invention. This embodiment of the invention relates to the graceful removal of push feeds from the perspective of a server providing the push feeds.
- the server provides a push feed to the mobile electronic device (Step 100 ).
- the push feed may be provided wirelessly through a communication network.
- the server identifies the push feed as new to the user of the mobile electronic device (Step 102 ).
- the push feed may be identified as new to the user by altering the graphical look of the push feed or applying a timestamp to the push feed.
- the user may be alerted by an audio signal, vibration, or other perceptible signal.
- Altering the graphical look of the push feed may involve modifying the color of the push feed based on its age. For example, when the push feed is new, the text of the push feed or the background of the push feed is a different color than when it is about to be removed from the mobile electronic device. For example, a new push feed may be pink, an old push feed may be green, and a push feed that is about to be deleted may be blue.
- a timestamp may also be applied to the push feed.
- the timestamp may indicate when the push feed will be deleted or when the push feed was added to the mobile electronic device.
- the server waits a predetermined amount of time (Step 104 ).
- the predetermined amount of time is the time that the push feed is to remain on the mobile electronic device.
- the predetermined amount of time may be any amount of time, for example, thirty seconds, sixty seconds, five minutes, or may be one hour or more.
- the server measures the predetermined amount of time.
- the user is notified that the push feed will be deleted (Step 106 ).
- the notification of deletion may be similar to the notification that the push feed is new.
- the push feed may have a timestamp or the push feed may change color to notify the user that the push feed is going to expire.
- an audio signal may be used to alert the user of the pending push feed expiration.
- the server instructs the mobile electronic device to delete the push feed (Step 108 ).
- the server sends the mobile electronic device a new push feed (Step 110 ).
- the arrival of the new push feed may trigger the deletion of an old push feed from the mobile electronic device.
- the push feed may be a channel.
- the server may send the channel with multiple push feeds to the user instead or in conjunction with the transmission of an individual push feed.
- the channel may be a plurality of push feeds, grouped according to topic or format.
- the channel may contain push feeds that are simultaneously sent and expire together or the channel may contain multiple push feeds that are accumulated in the channel, but are sent and expire individually and not as group.
- a server may send a baseball channel, a news channel, a weather channel, a business channel, a channel of thumbnails, a channel of video files, a channel of audio files, or any other group of individual push feeds clustered according to their content.
- the server may automatically send the channel as it does with an individual push feed.
- the whole channel may expire in a similar manner as an individual push feed would expire.
- Step 200 Another embodiment of the invention relates to the graceful removal of push feeds from the perspective of the mobile electronic device.
- this embodiment includes receiving a push feed (Step 200 ).
- the mobile electronic device may receive the push feed from the server. Then the mobile electronic device displays the push feed to the user (Step 202 ) and identifies the push feed as new to the user (Step 204 ).
- the push feed may be identified in a manner to similar to that disclosed above.
- the mobile electronic device notifies that the user that the push feed will be deleted (Step 206 ). The user is notified in a similar manner as disclosed above.
- the mobile electronic device deletes the push feed (Step 208 ).
- the predetermined amount of time may be included with the push feed as received.
- the mobile electronic device may use an internal clock to determine whether or not the predetermined amount of time has elapsed.
- the mobile electronic device receives a new push feed (Step 210 ).
- Such a system 300 may include a server 302 and a mobile electronic device 310 .
- the server 302 has a CPU 304 and an interface 306 .
- the server's CPU 304 creates a push feed 308 and sends the push feed 308 to the mobile electronic device 310 based upon inputs provided to the server's interface 306 .
- the inputs to the interface 306 may include the rate at which one or more push feeds 308 should be sent, the content of the push feeds and/or the predetermined amount of time that the push feed will be displayed on the mobile electronic device.
- the server's CPU 304 calculates the predetermined amount of time and may instruct the mobile electronic device 310 to delete the push feed 308 when it has expired.
- the CPU of the server 302 may then create a new push feed (not shown) and send the new push feed to the mobile electronic device 310 .
- the mobile electronic device 310 may include a CPU 312 and a display 316 .
- the mobile electronic device's CPU 312 processes the receipt of the push feed 308 and presents the push feed on the mobile electronic device's display 316 .
- the server 302 may send multiple push feeds 308 to the mobile electronic device 310 .
- the predetermined amount of time may be included with the push feed 308 as received by the mobile electronic device 310 .
- the mobile electronic device's CPU 312 calculates the predetermined amount of time for expiration of the push feed and deletes the push feed 308 when it has expired.
- an old push feed 308 is deleted upon receipt of a specific instruction from the server, or arrival of a new push feed.
- the mobile electronic device 301 may then receive a new push feed (not shown).
- this process may be implemented in either a single-threaded or multi-fashion. threaded fashion. Receipt of a new push feed does not necessarily result in the deletion of an old push feed. Thus, feeds may arrive and be deleted independently and asynchronously.
Abstract
Description
- The present invention relates to push handling user interfaces and specifically to the removal of expired push feeds.
- Push feeds or push media refer to any mechanism for distributing media or feeds where content is provided at the request of the content provider and not the user. Push feeds are advantageous in that the information is sent as soon as it is available without requiring action from the recipient.
- Push feeds are used in mobile electronic devices to instantly send information and web links to users. Since the push feeds are automatically sent to the user, unless they are deleted, the push feeds will typically accumulate on the user's mobile electronic device. The user has to manually delete unwanted push feeds, which can be time consuming and frustrating. Some mobile electronic devices permit the user to set preferences related to the deletion of push feeds. Although the user does not have delete each individual push feed, setting up preferences can be time consuming. Therefore, a method and system is needed to automatically manage push feeds on a mobile electronic device that does not require any input from the user.
- In satisfaction of this need and others, embodiments of the present invention systems and methods for the graceful removal of push feeds from a mobile electronic
- In one aspect, the claimed invention relates to a method for the graceful handling of push feeds in a mobile electronic device including sending a push feed to a mobile electronic device, waiting a predetermined amount of time, and instructing the mobile electronic device to delete the push feed. The method may further include sending a new push feed to the mobile electronic device, identifying the push feed as new to the user, and/or providing notification to the user as to when the push feed will be deleted. The notification may include altering the graphical look of the push feed or applying a timestamp to the new push feed. The predetermined amount of time may be, for example, thirty seconds, sixty seconds, five minutes, or sixty minutes. In one embodiment, the push feed is a channel.
- Another aspect of the invention relates to a method for the graceful handling of push feeds in a mobile electronic device including receiving a push feed, displaying the push feed, and after a predetermined amount of time, deleting the push feed. The predetermined amount of time may be included with the push feed as received. The method may further include receiving a new push feed, identifying the push feed as new to the user, and/or providing notification to the user as to when the push feed will be deleted. The notification may include altering the graphical look of the push feed or applying a timestamp to the new push feed. A clock internal to the mobile electronic device determines the predetermined amount of time.
- Another aspect of the invention relates to a system for the graceful handling of push feeds in a mobile electronic device. The system includes a server for transmitting data having a first CPU and a first interface and a mobile electronic device having a second CPU and a display for receiving data from a server. The mobile electronic device is configured to receive a push feed, display the push feed, and after a predetermined amount of time, delete the push feed. The predetermined amount of time may be included with the push feed as received. The system may be further configured to receive a new push feed.
- Another aspect of the invention relates to a system for the graceful handling of push feeds in a mobile electronic device. The system includes a server for transmitting data having a first CPU and a first interface, and a mobile electronic device having a second CPU and a display for receiving data from the server. The server is configured to send a push feed, wait a predetermined amount of time, and instruct the mobile electronic device to delete the push feed. The system may be further configured to send a new push feed.
- These embodiments and other aspects of this invention will be readily apparent from the detailed description below and the appended drawings, which are meant to illustrate and not to limit the invention, and in which:
-
FIG. 1 is a high level flow chart of a method for gracefully removing push feeds from a mobile electronic device according to one embodiment of the present invention. -
FIG. 2 is a high level flow chart of a method for gracefully removing push feeds from a mobile electronic device according to another embodiment of the present invention. -
FIG. 3 is a diagram of system for gracefully removing push feeds from a mobile electronic device according various embodiments of the present invention. - The present invention will be more completely understood through the following detailed description, which should be read in conjunction with the attached drawings. In this description, like numbers refer to similar elements within various embodiments of the present invention. Within this detailed description, the claimed invention will be explained with respect to preferred embodiments. However, the skilled artisan will readily appreciate that the methods and systems described herein are merely exemplary and that variations can be made without departing from the spirit and scope of the invention.
- Push feeds are headlines or links to more information that may be sent to a mobile electronic device. The push feeds may be customizable or may have mass appeal. Examples of push feeds include breaking news headlines, stock information, web links that are updated periodically, small images such as thumbnails, video files, audio files, and the weather. Since these push feeds are sent automatically and are time sensitive, i.e. headlines, stocks, and the weather change from day to day and even from hour to hour, the push feeds need to be refreshed and the outdated or stale push feeds need to be removed. For example, a weather report is sent to a mobile electronic device on day 1. On day 2, the weather report for day 1 is outdated and inaccurate. Thus, a new weather report must be sent on day 2. Since the weather report from day 1 is stale, it can be deleted from the mobile electronic device.
- The claimed invention generally relates to a system and method whereby push feeds are removed from a mobile electronic device without the involvement of the user of the mobile electronic device. Specifically, the push feeds may be expunged from the mobile electronic device gracefully or automatically by either the mobile electronic device or a server that provides the push feeds.
-
FIG. 1 is a high level flow chart of a method for gracefully removing push feeds from a mobile electronic device according to an embodiment of the present invention. This embodiment of the invention relates to the graceful removal of push feeds from the perspective of a server providing the push feeds. - First, the server provides a push feed to the mobile electronic device (Step 100). The push feed may be provided wirelessly through a communication network.
- Second, the server identifies the push feed as new to the user of the mobile electronic device (Step 102). The push feed may be identified as new to the user by altering the graphical look of the push feed or applying a timestamp to the push feed. In addition, the user may be alerted by an audio signal, vibration, or other perceptible signal.
- Altering the graphical look of the push feed may involve modifying the color of the push feed based on its age. For example, when the push feed is new, the text of the push feed or the background of the push feed is a different color than when it is about to be removed from the mobile electronic device. For example, a new push feed may be pink, an old push feed may be green, and a push feed that is about to be deleted may be blue.
- A timestamp may also be applied to the push feed. The timestamp may indicate when the push feed will be deleted or when the push feed was added to the mobile electronic device.
- Third, the server waits a predetermined amount of time (Step 104). The predetermined amount of time is the time that the push feed is to remain on the mobile electronic device. The predetermined amount of time may be any amount of time, for example, thirty seconds, sixty seconds, five minutes, or may be one hour or more. The server measures the predetermined amount of time.
- Fourth, the user is notified that the push feed will be deleted (Step 106). As explained with respect to Step 102, the notification of deletion may be similar to the notification that the push feed is new. For example, the push feed may have a timestamp or the push feed may change color to notify the user that the push feed is going to expire. Alternatively, an audio signal may be used to alert the user of the pending push feed expiration.
- Sixth, the server instructs the mobile electronic device to delete the push feed (Step 108). Seventh, the server sends the mobile electronic device a new push feed (Step 110). In an alternate embodiment, the arrival of the new push feed may trigger the deletion of an old push feed from the mobile electronic device.
- In one embodiment of the invention, the push feed may be a channel. The server may send the channel with multiple push feeds to the user instead or in conjunction with the transmission of an individual push feed. The channel may be a plurality of push feeds, grouped according to topic or format. The channel may contain push feeds that are simultaneously sent and expire together or the channel may contain multiple push feeds that are accumulated in the channel, but are sent and expire individually and not as group.
- For example, a server may send a baseball channel, a news channel, a weather channel, a business channel, a channel of thumbnails, a channel of video files, a channel of audio files, or any other group of individual push feeds clustered according to their content. The server may automatically send the channel as it does with an individual push feed. When a user fails to view the channel, the whole channel may expire in a similar manner as an individual push feed would expire.
- Another embodiment of the invention relates to the graceful removal of push feeds from the perspective of the mobile electronic device. Referring to
FIG. 2 , this embodiment includes receiving a push feed (Step 200). The mobile electronic device may receive the push feed from the server. Then the mobile electronic device displays the push feed to the user (Step 202) and identifies the push feed as new to the user (Step 204). The push feed may be identified in a manner to similar to that disclosed above. Before the push feed is deleted, the mobile electronic device notifies that the user that the push feed will be deleted (Step 206). The user is notified in a similar manner as disclosed above. - Once a predetermined amount of time has elapsed, the mobile electronic device deletes the push feed (Step 208). The predetermined amount of time may be included with the push feed as received. The mobile electronic device may use an internal clock to determine whether or not the predetermined amount of time has elapsed. After the push feed is deleted, the mobile electronic device receives a new push feed (Step 210).
- The two methods described previously are preferably implemented as part of a client-server or peer-to-peer computer system. As shown in
FIG. 3 , such asystem 300 may include aserver 302 and a mobileelectronic device 310. - The
server 302 has aCPU 304 and aninterface 306. The server'sCPU 304 creates a push feed 308 and sends the push feed 308 to the mobileelectronic device 310 based upon inputs provided to the server'sinterface 306. The inputs to theinterface 306 may include the rate at which one or more push feeds 308 should be sent, the content of the push feeds and/or the predetermined amount of time that the push feed will be displayed on the mobile electronic device. In one embodiment, the server'sCPU 304 calculates the predetermined amount of time and may instruct the mobileelectronic device 310 to delete the push feed 308 when it has expired. The CPU of theserver 302 may then create a new push feed (not shown) and send the new push feed to the mobileelectronic device 310. - The mobile
electronic device 310 may include aCPU 312 and adisplay 316. The mobile electronic device'sCPU 312 processes the receipt of the push feed 308 and presents the push feed on the mobile electronic device'sdisplay 316. Theserver 302 may send multiple push feeds 308 to the mobileelectronic device 310. The predetermined amount of time may be included with the push feed 308 as received by the mobileelectronic device 310. In one embodiment, the mobile electronic device'sCPU 312 calculates the predetermined amount of time for expiration of the push feed and deletes the push feed 308 when it has expired. In another embodiment, an old push feed 308 is deleted upon receipt of a specific instruction from the server, or arrival of a new push feed. The mobile electronic device 301 may then receive a new push feed (not shown). - However, this process may be implemented in either a single-threaded or multi-fashion. threaded fashion. Receipt of a new push feed does not necessarily result in the deletion of an old push feed. Thus, feeds may arrive and be deleted independently and asynchronously.
- Variations, modification, and other implementations of what is described herein will occur to those of ordinary skill in the art without departing from the spirit and scope of the invention as claimed. Accordingly, the invention is to be defined not by the preceding illustrative description but instead by the spirit and scope of the following claims.
Claims (21)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/702,736 US20080185772A1 (en) | 2007-02-06 | 2007-02-06 | Systems and methods for a graceful push handling user interface |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/702,736 US20080185772A1 (en) | 2007-02-06 | 2007-02-06 | Systems and methods for a graceful push handling user interface |
Publications (1)
Publication Number | Publication Date |
---|---|
US20080185772A1 true US20080185772A1 (en) | 2008-08-07 |
Family
ID=39675492
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/702,736 Abandoned US20080185772A1 (en) | 2007-02-06 | 2007-02-06 | Systems and methods for a graceful push handling user interface |
Country Status (1)
Country | Link |
---|---|
US (1) | US20080185772A1 (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9264944B1 (en) | 2015-07-06 | 2016-02-16 | Peerless Network, Inc. | SBC-localized handoff |
US9497606B1 (en) | 2016-03-24 | 2016-11-15 | Peerless Network, Inc. | Native dialer fall-back |
US9706351B1 (en) | 2016-04-29 | 2017-07-11 | Peerless Network, Inc. | Emergency call over a data network |
US11188396B2 (en) | 2019-09-09 | 2021-11-30 | International Business Machines Corporation | Pending notification deletion through autonomous removal triggering |
US11856060B2 (en) | 2020-08-04 | 2023-12-26 | International Business Machines Corporation | Planned message notification for IoT device based on activity |
Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020087643A1 (en) * | 2000-10-30 | 2002-07-04 | Parsons Eric W. | Method and system for providing unified WAP alerts |
US20020108115A1 (en) * | 2000-12-11 | 2002-08-08 | The Associated Press | News and other information delivery system and method |
US20040015562A1 (en) * | 2002-06-18 | 2004-01-22 | Harper David Walker | Method, apparatus and system for management of information content for enhanced accessibility over wireless communication networks |
US20050193341A1 (en) * | 2004-02-27 | 2005-09-01 | Hayward Anthony D. | System for aggregating, processing and delivering video footage, documents, audio files and graphics |
US20060155698A1 (en) * | 2004-12-28 | 2006-07-13 | Vayssiere Julien J | System and method for accessing RSS feeds |
US20060173985A1 (en) * | 2005-02-01 | 2006-08-03 | Moore James F | Enhanced syndication |
US20060179115A1 (en) * | 2005-02-09 | 2006-08-10 | Nokia Corporation | Controlling push operation in a communication system |
US20070094346A1 (en) * | 2005-10-23 | 2007-04-26 | Bill Nussey | Individualized rss feeds with archives and automatic cleanup |
US20080091796A1 (en) * | 2006-09-29 | 2008-04-17 | Guy Story | Methods and apparatus for customized content delivery |
US7412534B2 (en) * | 2005-09-30 | 2008-08-12 | Yahoo! Inc. | Subscription control panel |
US20090193097A1 (en) * | 2008-01-30 | 2009-07-30 | Alcatel Lucent | Method and apparatus for targeted content delivery based on RSS feed analysis |
-
2007
- 2007-02-06 US US11/702,736 patent/US20080185772A1/en not_active Abandoned
Patent Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020087643A1 (en) * | 2000-10-30 | 2002-07-04 | Parsons Eric W. | Method and system for providing unified WAP alerts |
US20020108115A1 (en) * | 2000-12-11 | 2002-08-08 | The Associated Press | News and other information delivery system and method |
US20040015562A1 (en) * | 2002-06-18 | 2004-01-22 | Harper David Walker | Method, apparatus and system for management of information content for enhanced accessibility over wireless communication networks |
US20050193341A1 (en) * | 2004-02-27 | 2005-09-01 | Hayward Anthony D. | System for aggregating, processing and delivering video footage, documents, audio files and graphics |
US20060155698A1 (en) * | 2004-12-28 | 2006-07-13 | Vayssiere Julien J | System and method for accessing RSS feeds |
US20060173985A1 (en) * | 2005-02-01 | 2006-08-03 | Moore James F | Enhanced syndication |
US20060179115A1 (en) * | 2005-02-09 | 2006-08-10 | Nokia Corporation | Controlling push operation in a communication system |
US7412534B2 (en) * | 2005-09-30 | 2008-08-12 | Yahoo! Inc. | Subscription control panel |
US20070094346A1 (en) * | 2005-10-23 | 2007-04-26 | Bill Nussey | Individualized rss feeds with archives and automatic cleanup |
US20080091796A1 (en) * | 2006-09-29 | 2008-04-17 | Guy Story | Methods and apparatus for customized content delivery |
US20090193097A1 (en) * | 2008-01-30 | 2009-07-30 | Alcatel Lucent | Method and apparatus for targeted content delivery based on RSS feed analysis |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9264944B1 (en) | 2015-07-06 | 2016-02-16 | Peerless Network, Inc. | SBC-localized handoff |
US9473992B1 (en) | 2015-07-06 | 2016-10-18 | Peerless Network, Inc. | SBC-localized handoff |
US9497606B1 (en) | 2016-03-24 | 2016-11-15 | Peerless Network, Inc. | Native dialer fall-back |
US9706351B1 (en) | 2016-04-29 | 2017-07-11 | Peerless Network, Inc. | Emergency call over a data network |
US11188396B2 (en) | 2019-09-09 | 2021-11-30 | International Business Machines Corporation | Pending notification deletion through autonomous removal triggering |
US11856060B2 (en) | 2020-08-04 | 2023-12-26 | International Business Machines Corporation | Planned message notification for IoT device based on activity |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10466884B2 (en) | Notifying a user of an available media object | |
US9172622B2 (en) | Methods, systems and computer products for download status notification | |
US10009659B2 (en) | System and method for hybrid push-based streaming | |
US8819194B2 (en) | System for an open architecture deployment platform with centralized synchronization | |
JP4851135B2 (en) | Differential update of data broadcasting | |
US8813162B2 (en) | Information receiving apparatus, data downloading method, and information receiving system | |
JP3970777B2 (en) | Video distribution system and video distribution method | |
MX2007002056A (en) | Apparatus, and associated method, for facilitating delivery and processing of push content . | |
US20080185772A1 (en) | Systems and methods for a graceful push handling user interface | |
EP1895424A1 (en) | Content relaying device and content relaying method | |
JP2007286790A (en) | Application management program, application management method, and application management device | |
US9807447B2 (en) | Intelligent scheduling of DVR commands and DVR client status updates | |
CA2275058A1 (en) | Method of discrete interactive multimedia list broadcasting | |
KR20080091978A (en) | Contents download method and apparatus of mobile device | |
US20110010430A1 (en) | Systems And Methods For Scheduling And Delivering Messages Based On Recipient's Time Zone | |
CA2741191A1 (en) | Always ready client/server data synchronization | |
CN111787404A (en) | Live stream playing method and device | |
CN116346794A (en) | Method, apparatus and non-volatile computer readable storage medium for receiving media data | |
US20020147827A1 (en) | Method, system and computer program product for streaming of data | |
KR101057231B1 (en) | Method for creating a content list in a device connected to a domestic network and a device related to the method | |
JP2002183019A (en) | Cache device | |
KR20060012633A (en) | Method for adapting service location placement based on recent data received from service nodes and actions of the service location manager | |
KR20070003902A (en) | Hierarchical broadcast of ui assets | |
US20110225268A1 (en) | Combined rendering of digital media objects | |
JP2008048113A (en) | Dynamic image data distribution system, dynamic image data distribution method, dynamic image data providing method, dynamic image data distribution program, dynamic image data providing program, and computer-readable recording medium recorded with these programs |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: HELIO, LLC, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:DUARTE, MATIAS;FORD, PETER;REEL/FRAME:019095/0376;SIGNING DATES FROM 20070118 TO 20070130 |
|
AS | Assignment |
Owner name: SK TELECOM USA HOLDINGS, INC., KOREA, DEMOCRATIC P Free format text: SECURITY AGREEMENT;ASSIGNOR:HELIO LLC;REEL/FRAME:021314/0795 Effective date: 20080724 Owner name: SK TELECOM USA HOLDINGS, INC.,KOREA, DEMOCRATIC PE Free format text: SECURITY AGREEMENT;ASSIGNOR:HELIO LLC;REEL/FRAME:021314/0795 Effective date: 20080724 |
|
AS | Assignment |
Owner name: HELIO LLC, CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:SK TELECOM USA HOLDINGS, INC.;REEL/FRAME:021428/0001 Effective date: 20080822 Owner name: VIRGIN ENTERTAINMENT HOLDINGS, INC., CALIFORNIA Free format text: SECURITY AGREEMENT;ASSIGNOR:HELIO LLC;REEL/FRAME:021429/0824 Effective date: 20080822 Owner name: SK TELECOM USA HOLDINGS, INC., KOREA, DEMOCRATIC P Free format text: SECURITY AGREEMENT;ASSIGNOR:HELIO LLC;REEL/FRAME:021429/0824 Effective date: 20080822 Owner name: JPMORGAN CHASE BANK, N.A. AS COLLATERAL AGENT, TEX Free format text: SECURITY AGREEMENT;ASSIGNOR:HELIO LLC;REEL/FRAME:021432/0080 Effective date: 20080821 Owner name: HELIO LLC,CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:SK TELECOM USA HOLDINGS, INC.;REEL/FRAME:021428/0001 Effective date: 20080822 Owner name: VIRGIN ENTERTAINMENT HOLDINGS, INC.,CALIFORNIA Free format text: SECURITY AGREEMENT;ASSIGNOR:HELIO LLC;REEL/FRAME:021429/0824 Effective date: 20080822 Owner name: SK TELECOM USA HOLDINGS, INC.,KOREA, DEMOCRATIC PE Free format text: SECURITY AGREEMENT;ASSIGNOR:HELIO LLC;REEL/FRAME:021429/0824 Effective date: 20080822 Owner name: JPMORGAN CHASE BANK, N.A. AS COLLATERAL AGENT,TEXA Free format text: SECURITY AGREEMENT;ASSIGNOR:HELIO LLC;REEL/FRAME:021432/0080 Effective date: 20080821 |
|
AS | Assignment |
Owner name: VIRGIN MOBILE USA, L.P., NEW JERSEY Free format text: CHANGE OF CONTROL OF ASSIGNEE;ASSIGNOR:HELIO LLC;REEL/FRAME:021719/0749 Effective date: 20080822 Owner name: VIRGIN MOBILE USA, L.P.,NEW JERSEY Free format text: CHANGE OF CONTROL OF ASSIGNEE;ASSIGNOR:HELIO LLC;REEL/FRAME:021719/0749 Effective date: 20080822 |
|
AS | Assignment |
Owner name: HELIO LLC, CALIFORNIA Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL 021432, FRAME 0080;ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT AND COLLATERAL AGENT;REEL/FRAME:023563/0943 Effective date: 20091124 Owner name: HELIO LLC, CALIFORNIA Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL 021429, FRAME 0824;ASSIGNORS:VIRGIN ENTERTAINMENT HOLDINGS, INC.;SK TELECOM CO., LTD. (AS SUCCESSOR TO SK TELECOM USA HOLDINGS, INC.);REEL/FRAME:023567/0623 Effective date: 20091124 Owner name: HELIO LLC,CALIFORNIA Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL 021432, FRAME 0080;ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT AND COLLATERAL AGENT;REEL/FRAME:023563/0943 Effective date: 20091124 Owner name: HELIO LLC,CALIFORNIA Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL 021429, FRAME 0824;ASSIGNORS:VIRGIN ENTERTAINMENT HOLDINGS, INC.;SK TELECOM CO., LTD. (AS SUCCESSOR TO SK TELECOM USA HOLDINGS, INC.);REEL/FRAME:023567/0623 Effective date: 20091124 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |