US20110213823A1 - Dynamic Creation Of Content Channels - Google Patents

Dynamic Creation Of Content Channels Download PDF

Info

Publication number
US20110213823A1
US20110213823A1 US13/102,724 US201113102724A US2011213823A1 US 20110213823 A1 US20110213823 A1 US 20110213823A1 US 201113102724 A US201113102724 A US 201113102724A US 2011213823 A1 US2011213823 A1 US 2011213823A1
Authority
US
United States
Prior art keywords
fragment
expression
interest
change
channel
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
Application number
US13/102,724
Inventor
David Schmidt
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
BlackBerry Ltd
Original Assignee
Research in Motion Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Research in Motion Ltd filed Critical Research in Motion Ltd
Priority to US13/102,724 priority Critical patent/US20110213823A1/en
Assigned to RESEARCH IN MOTION LIMITED reassignment RESEARCH IN MOTION LIMITED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: SCHMIDT, DAVID
Publication of US20110213823A1 publication Critical patent/US20110213823A1/en
Assigned to BLACKBERRY LIMITED reassignment BLACKBERRY LIMITED CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: RESEARCH IN MOTION LIMITED
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00Digital computers in general; Data processing equipment in general
    • G06F15/16Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/951Indexing; Web crawling techniques
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/266Channel or content management, e.g. generation and management of keys and entitlement messages in a conditional access system, merging a VOD unicast channel into a multicast channel
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/41Structure of client; Structure of client peripherals
    • H04N21/414Specialised client platforms, e.g. receiver in car or embedded in a mobile appliance
    • H04N21/41407Specialised client platforms, e.g. receiver in car or embedded in a mobile appliance embedded in a portable device, e.g. video client on a mobile phone, PDA, laptop
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47End-user applications
    • H04N21/472End-user interface for requesting content, additional data or services; End-user interface for interacting with content, e.g. for content reservation or setting reminders, for requesting event notification, for manipulating displayed content
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47End-user applications
    • H04N21/482End-user interface for program selection
    • H04N21/4821End-user interface for program selection using a grid, e.g. sorted out by channel and broadcast time
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/61Network physical structure; Signal processing
    • H04N21/6106Network physical structure; Signal processing specially adapted to the downstream path of the transmission network
    • H04N21/6131Network physical structure; Signal processing specially adapted to the downstream path of the transmission network involving transmission via a mobile phone network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/643Communication protocols
    • H04N21/64322IP
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/60Subscription-based services using application servers or record carriers, e.g. SIM application toolkits

Definitions

  • a user may wish to have content pushed to them via a channel.
  • Each channel is specific to the type of content. Examples of content delivered by a channel are updates on stock market prices, sports scores or news.
  • the prior art requires that a channel be established by a software developer familiar with the programming needed to create a channel and determine which content should be pushed to the user of a computing device.
  • FIG. 1 is a block diagram of a system comprising components of an embodiment of the present invention
  • FIG. 2 a flowchart of the function of a page fragment selection tool
  • FIG. 3 is a flowchart of the function of a change target selection tool
  • FIG. 4 a flowchart of the function of a PCM site
  • FIG. 5 is a flowchart of the function of a selection analyzer
  • FIGS. 6 a and 6 b are flowcharts of the processes of a push channel monitor.
  • FIG. 7 is a screen mockup of a channel management interface.
  • Embodiments of the invention described herein provide the ability for a user to simply create a channel and select the content to be pushed.
  • System 10 comprises a mobile browser 12 , a channel manager 14 and two persistent database sources.
  • the first database source is shown as feature 16 and indicates data available on the World Wide Web.
  • Push Channel Manager (PCM) database 18 is a repository for channel and access information stored by Push Channel Manger (PCM) site 32 .
  • Mobile browser 12 resides on a computing device utilizing wireless technology and comprises a memory cache 20 , a page fragment selection tool 22 , a change target selection tool 24 and a user interface 25 .
  • Cache 20 is a memory cache to store information provided by channel manager 14 to be viewed by a user.
  • Page fragment selection tool 22 provides a user with the functionality to select the information on a website for which they wish to establish a channel to provide updates should the information change, the selected information hereinafter referred to as a fragment.
  • Change target selection tool 24 allows the user to select what information on the website they wish to be pushed on the channel should a change occur. In one case it would be the Uniform Resource Locator (URL) of the page selected by page fragment selection tool 22 . In another case it would be a specific area of the website, for example the text only, excluding such features as menu items, graphics or sidebars.
  • URL Uniform Resource Locator
  • User interface 25 allows the user of mobile browser 12 to invoke and utilize page fragment selection tool 22 and change target selection tool 24 .
  • user interface 25 may provide the user with a channel manager interface to allow the user to directly create channels or to modify the information on a channel provided they have the authority to do so. This additional functionality is discussed in more detail with reference to FIG. 7 .
  • Channel manager 14 comprises a plurality of components that may reside on a single computing device or be distributed.
  • IP Proxy 26 is responsible for pushing content on the channel defined by the user. Modules such as IP Proxy 26 that are able to push updated information to mobile devices are known in the art. What information to push is determined by a Change Target Transcoder (CTT) 26 a which takes information indicating a change on a website has occurred from push channel monitor 28 and scans PCM database 18 for a definition of what information should be pushed. When a change target is less than the complete URL, CTT 26 a ensures that only the content of the change target is pushed to subscribers of the channel.
  • CTT Change Target Transcoder
  • Push Channel Monitor 28 is responsible for detecting changes in the content selected by the user and informing IP Proxy 26 of the changes so they may be pushed to the channel defined by the user.
  • Webserver 30 is where the Push Channel Manager site 32 resides.
  • PCM site 32 receives a request to define a channel from change target selection tool 24 or user interface 25 and in turn stores this request information in PCM database 18 as channel definition information.
  • Channel definition information stored in PCM database 18 may include:
  • a short name of the channel for example “weathcam”.
  • a longer name for example “Cambridge Weather Forecast”.
  • a category for example “weather”.
  • a link to an icon to be displayed on user interface 25 indicating that information from the channel is unread.
  • a link to an icon to be displayed on user interface 25 indicating that all information from the channel has been read.
  • Security, administration and policy manager 34 is responsible for ensuring secure access to the modules of channel manager 14 . Examples would include storing rules in PCM database 18 on who can access a channel, who can modify channel definition information and how a channel may be deleted.
  • Page fragment selection tool 22 permits the user to select a page fragment on a website that they wish to have monitored for changes and passes information to identify the page fragment to PCM site 32 .
  • Change target selection tool 24 permits the user to select what information they wish to receive once the page fragment selected through the use of page fragment selection tool 22 has changed and passes that information to PCM site 32 .
  • PCM site 32 maintains user registration, subscriptions and channel definition information in PCM database 18 .
  • Push channel monitor 28 scans both databases 16 and 18 and sends directives on any changes relative to a channel to IP Proxy 26 .
  • a flowchart of the function of page fragment selection tool 22 is shown.
  • a user selects a website containing information for which they wish to create a channel.
  • the user through user interface 25 scrolls to a page fragment of interest to be monitored for changes. Examples of page fragments include text such as a headline on a news site, an image or any other content on the site the user wishes to monitor for changes.
  • the user through user interface 25 highlights the page fragment of interest. Step 44 obtains all related HTML tags such as: ⁇ a>, ⁇ div>, ⁇ td>, ⁇ tr>, and others to identify the page fragment.
  • the user may optionally select two icons, to serve as read and unread icons for the new channel to be displayed on user interface 25 .
  • a single icon could be selected with the checkmark or other indicia to indicate read or unread status.
  • the user wishes to select an icon processing moves to step 48 where the user selects a website containing the icons to be used, and picks the icons this may be same website selected when creating the channel or could be another website, for example a page containing a set of icons.
  • step 50 If at step 46 the user declines to select icons processing a default icon is created and processing moves to step 50 .
  • information regarding the page fragment of interest and icon(s) are sent to PCM site 32 .
  • step 52 the user scrolls to a change target area on the website of interest that they wish to have pushed to mobile browser 12 .
  • the change target area defines the information that the user wishes to receive on mobile browser 12 .
  • step 54 the change target is selected through the use of user interface 25 , this step allows the user to select specific text or images, for example a change target may be the text in the body of a website, not the images, sidebars or menu items.
  • the change target will include immediately surrounding HTML tags and embedded tags in the change target and the URL of the change target. Alternatively it may simply be a URL.
  • the information defining the change target is sent to PCM site 32 .
  • the user is prompted by user interface 25 to provide a name and category for the new channel.
  • the name is a user defined name for the channel and the category may be unique or selected from a list such as “weather”, “news”, “technology” or others.
  • the name and categorization information provided at step 58 is sent to PCM site 32 .
  • step 62 the output of step 50 of FIG. 2 is received.
  • the URL of the website containing the page fragment of interest and the page fragment of interest is stored in PCM database 18 .
  • step 64 any icons selected to indicate if information remains read or unread in the channel is processed to reformat it to the desired size for user interface 25 and stored in PCM database 18 .
  • the target selected at step 56 of FIG. 3 is received and stored in PCM database 18 .
  • the information defining the URL of the website containing the target information and the target information is stored in PCM database 18
  • step 68 the name and categorization of the new channel provided by step 60 of FIG. 3 is stored in PCM database 18 .
  • step 70 is invoked and is described with reference to FIG. 5 .
  • a test is made to determine if the fragment of interest matches a regular expression (regex).
  • regular expression is well known in the computing arts and can take on many forms. In essence it is a string of characters that describes or matches a set of strings, depending upon the syntax used.
  • a set of regular expressions is stored in an HTML pattern dictionary (not shown).
  • the HTML pattern dictionary is stored in PCM database 18 and comprises entries for regular expressions (regexs) that match dynamic content between static demarcation tags or content. Examples would be:
  • regexs that match a variety of standard, common and previously encountered date/time text strings such as “last updated Thurs. Jan. 11, 2007”.
  • regexs of typical HTML tag sequences such as ⁇ a>, ⁇ div>, ⁇ tr>, ⁇ td> and others.
  • computed regexs created by the selection analyzer as shown beginning at step 86 of FIG. 5 .
  • step 80 processing moves to step 82 where a change expression is built utilizing the text in the fragment of interest that precedes the regex located, the regex located, and text in the target selection that follows the regex located. Processing then moves to step 84 where the change expression is stored in PCM database 18 for use by Push Channel Monitor 28 .
  • step 86 the fragment of interest is monitored on a regular basis while polling the website on which it resides at a user configurable rate, for example every 30 minutes.
  • a temporary icon is created on the user interface 25 of mobile device 12 such as an unread icon with a question mark on it. When the icon is selected a message such as “Channel Activation Not Complete” would be displayed.
  • step 88 After each polling attempt a test is made at step 88 to determine if a change has occurred in the fragment of interest. If a certain number of detected changes have been found (perhaps two to three) and they are of the same format, processing moves to step 90 .
  • This step involves comparing samples with a constant prefix and suffix to the substrings contained between them. The substrings are then compared to create a regex substring including “match any” operators in the regex.
  • a regex is built based upon the changes identified in step 86 , keeping the static information in the page fragment and utilizing wildcards such as “.*” to match changing information.
  • the newly created regex is stored in the pattern dictionary in PCM database 18 . Over time regex entries will build up in the pattern dictionary thus saving time in creating a change expression. Processing then moves to step 82 where utilizing the new regex a change expression is created. Processing then moves to step 84 where the change expression is stored in PCM database 18 for use by Push Channel Monitor 28 .
  • FIGS. 6 a and 6 b flowcharts of the processes of a push channel monitor are shown.
  • PCM database 18 contains information defining a channel.
  • the definitions of the channels the last time the process was run are compared with the current definitions stored in PCM database 18 . If a new channel is found, processing moves to step 102 where a new channel driver is created. Each channel has a channel driver associated with it for the purpose of monitoring changes on that channel in order to instruct IP Proxy 26 to push information. This process of determining what to push is described in FIG. 6 b . If a channel has been deleted processing moves to step 104 where the channel driver is deleted.
  • a channel definition comprises the channel definition data stored in PCM database 18 which is copied to a memory resident object instantiated by the channel and controlled by the channel driver.
  • Step 100 runs continually looking at the list of channels and determining the appropriate action to take.
  • each channel has its own channel driver.
  • the channel driver for a channel scans for any changes to content on a web page as found in WWW database 18 (a URL of the WWW), utilizing the change expression stored in PCM database 18 .
  • a test is made to determine if a change has occurred. If not processing returns to step 110 . If a change has been detected processing moves to step 114 where the change activity for the channel is tracked. The purpose of this is to determine if content changes for this channel may be exceeding thresholds that indicate the changes being pushed may be utilizing too many system and network resources.
  • a test is made to determine if the change rate is beyond a desired threshold. If this is the case processing moves to step 118 where the channel driver is disabled. An example of disabling a channel driver would include abnormal amounts of traffic to a channel that could be interpreted as a Denial of Service (DOS) attack by the change target website. After step 118 no changed content is pushed and processing returns to step 110 . If at step 116 it is determined that the change rate is not beyond a desired threshold, processing moves to step 120 . At step 120 a test is made to determine if the channel driver has been disabled. If not, processing moves to step 124 where an indication of the changed content is sent to IP Proxy 26 to have the content pushed to all subscribers of the channel. If at step 120 it is determined that the channel has been disabled, it is reenabled at step 122 and processing moves to step 124 . From step 124 processing returns to step 110 .
  • DOS Denial of Service
  • Channel management interface 130 may be accessible to a user through user interface 25 or to a system administrator via security, administration and policy manager 34 .
  • FIG. 7 serves as an example of the type of information that may be presented in creating or modifying a channel.
  • Feature 132 indicates a portion of the screen that may be used to add a new channel as an alternative to having the user select a page fragment and change target by selecting text.
  • a name for the new channel is entered.
  • a title for the channel is entered.
  • a channel category is entered or selected from a set provided.
  • the URL of an icon to indicate unread items is entered.
  • the URL of an icon to indicate read items is entered.
  • the URL of the page to monitor for changes is entered.
  • the change expression to determine if changes of interest have occurred is entered.
  • the fields of feature 132 correspond to the information entered by the user or generated by the system as described in FIGS. 2 through 5 .
  • Feature 148 illustrates a table of the information on channels, the information being modifiable with the correct security authority.
  • Column 150 contains the name field
  • column 152 contains the title field
  • column 154 contains the category field
  • column 156 contains the URL of the unread icon
  • column 158 contains the URL of the read icon
  • column 160 contains the URL of the page to monitor for changes
  • column 162 contains the change expression.
  • the information displayed in feature 148 is provided to aid the reader in understanding the information stored in PCM database 18 to define a channel.

Abstract

A system and method are provided for allowing a user to define and subscribe to channels of information to be pushed to a wireless device. In defining a channel a specific area of a web page is selected by the user to be monitored for change. The user may also select data to be pushed should a change be detected. A regular expression is created to match the area of interest for changes and if changes occur to push the desired content to the wireless device. Icons on the wireless device alert the user to any unread pushed content. Users may also subscribe to predefined channels, or modify predefined channels should they have the security authorization to do so.

Description

    CROSS-REFERENCE TO RELATED APPLICATIONS
  • This is a continuation of U.S. patent application Ser. No. 11/677,844, titled “Community-based Method and System for Creating and Subscribing to Dynamic Push Channels,” filed on Feb. 22, 2007, the entirety of which is hereby incorporated by reference.
  • BACKGROUND
  • In using wireless computing devices, a user may wish to have content pushed to them via a channel. Each channel is specific to the type of content. Examples of content delivered by a channel are updates on stock market prices, sports scores or news. The prior art requires that a channel be established by a software developer familiar with the programming needed to create a channel and determine which content should be pushed to the user of a computing device.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • Embodiments are illustrated by way of example and without limitation in the figures of the accompanying drawings, in which like reference numerals indicate corresponding, analogous or similar elements, and in which:
  • FIG. 1 is a block diagram of a system comprising components of an embodiment of the present invention;
  • FIG. 2 a flowchart of the function of a page fragment selection tool;
  • FIG. 3 is a flowchart of the function of a change target selection tool;
  • FIG. 4 a flowchart of the function of a PCM site;
  • FIG. 5 is a flowchart of the function of a selection analyzer;
  • FIGS. 6 a and 6 b are flowcharts of the processes of a push channel monitor; and
  • FIG. 7 is a screen mockup of a channel management interface.
  • DETAILED DESCRIPTION
  • Embodiments of the invention described herein provide the ability for a user to simply create a channel and select the content to be pushed.
  • Referring first to FIG. 1, a block diagram of a system comprising components of an embodiment of the present invention is shown generally as 10. System 10 comprises a mobile browser 12, a channel manager 14 and two persistent database sources. The first database source is shown as feature 16 and indicates data available on the World Wide Web. Push Channel Manager (PCM) database 18 is a repository for channel and access information stored by Push Channel Manger (PCM) site 32.
  • Mobile browser 12 resides on a computing device utilizing wireless technology and comprises a memory cache 20, a page fragment selection tool 22, a change target selection tool 24 and a user interface 25.
  • Cache 20 is a memory cache to store information provided by channel manager 14 to be viewed by a user. Page fragment selection tool 22 provides a user with the functionality to select the information on a website for which they wish to establish a channel to provide updates should the information change, the selected information hereinafter referred to as a fragment. Change target selection tool 24 allows the user to select what information on the website they wish to be pushed on the channel should a change occur. In one case it would be the Uniform Resource Locator (URL) of the page selected by page fragment selection tool 22. In another case it would be a specific area of the website, for example the text only, excluding such features as menu items, graphics or sidebars. User interface 25 allows the user of mobile browser 12 to invoke and utilize page fragment selection tool 22 and change target selection tool 24. In addition user interface 25 may provide the user with a channel manager interface to allow the user to directly create channels or to modify the information on a channel provided they have the authority to do so. This additional functionality is discussed in more detail with reference to FIG. 7.
  • Channel manager 14 comprises a plurality of components that may reside on a single computing device or be distributed. In the embodiment shown, IP Proxy 26 is responsible for pushing content on the channel defined by the user. Modules such as IP Proxy 26 that are able to push updated information to mobile devices are known in the art. What information to push is determined by a Change Target Transcoder (CTT) 26 a which takes information indicating a change on a website has occurred from push channel monitor 28 and scans PCM database 18 for a definition of what information should be pushed. When a change target is less than the complete URL, CTT 26 a ensures that only the content of the change target is pushed to subscribers of the channel.
  • Push Channel Monitor 28 is responsible for detecting changes in the content selected by the user and informing IP Proxy 26 of the changes so they may be pushed to the channel defined by the user. Webserver 30 is where the Push Channel Manager site 32 resides. PCM site 32 receives a request to define a channel from change target selection tool 24 or user interface 25 and in turn stores this request information in PCM database 18 as channel definition information. Channel definition information stored in PCM database 18 may include:
  • a) A short name of the channel, for example “weathcam”.
    b) A longer name, for example “Cambridge Weather Forecast”.
    c) A category, for example “weather”.
    d) A link to an icon to be displayed on user interface 25 indicating that information from the channel is unread.
    e) A link to an icon to be displayed on user interface 25 indicating that all information from the channel has been read.
    f) The URL of the page to monitor.
    g) A change expression utilized to determine when changes have occurred in the fragment to be monitored.
  • Examples of values of this information are shown in FIG. 7.
  • Security, administration and policy manager 34 is responsible for ensuring secure access to the modules of channel manager 14. Examples would include storing rules in PCM database 18 on who can access a channel, who can modify channel definition information and how a channel may be deleted.
  • For the reader to better understand the interactions of the above referenced features we provide the following overview.
  • 1) Page fragment selection tool 22 permits the user to select a page fragment on a website that they wish to have monitored for changes and passes information to identify the page fragment to PCM site 32.
    2) Change target selection tool 24 permits the user to select what information they wish to receive once the page fragment selected through the use of page fragment selection tool 22 has changed and passes that information to PCM site 32.
    3) PCM site 32 maintains user registration, subscriptions and channel definition information in PCM database 18.
    4) Push channel monitor 28 scans both databases 16 and 18 and sends directives on any changes relative to a channel to IP Proxy 26.
  • We will now discuss how each of the above referenced features accomplishes the functions described in points 1) to 4) above.
  • Referring now to FIG. 2 a flowchart of the function of page fragment selection tool 22 is shown. At step 40 through the use of user interface 25, a user selects a website containing information for which they wish to create a channel. At step 42 the user through user interface 25 scrolls to a page fragment of interest to be monitored for changes. Examples of page fragments include text such as a headline on a news site, an image or any other content on the site the user wishes to monitor for changes. At step 44 the user through user interface 25 highlights the page fragment of interest. Step 44 obtains all related HTML tags such as: <a>, <div>, <td>, <tr>, and others to identify the page fragment. At step 46 the user may optionally select two icons, to serve as read and unread icons for the new channel to be displayed on user interface 25. Alternatively a single icon could be selected with the checkmark or other indicia to indicate read or unread status. If the user wishes to select an icon processing moves to step 48 where the user selects a website containing the icons to be used, and picks the icons this may be same website selected when creating the channel or could be another website, for example a page containing a set of icons. After step 48 is complete, processing then moves to step 50. If at step 46 the user declines to select icons processing a default icon is created and processing moves to step 50. At step 50 information regarding the page fragment of interest and icon(s) are sent to PCM site 32.
  • Referring now to FIG. 3 a flowchart of the function of the change target selection tool 24 is shown. Beginning at step 52 though the use of user interface 25 the user scrolls to a change target area on the website of interest that they wish to have pushed to mobile browser 12. The change target area defines the information that the user wishes to receive on mobile browser 12. At step 54 the change target is selected through the use of user interface 25, this step allows the user to select specific text or images, for example a change target may be the text in the body of a website, not the images, sidebars or menu items. In this case the change target will include immediately surrounding HTML tags and embedded tags in the change target and the URL of the change target. Alternatively it may simply be a URL. At step 56 the information defining the change target is sent to PCM site 32. At step 58 the user is prompted by user interface 25 to provide a name and category for the new channel. The name is a user defined name for the channel and the category may be unique or selected from a list such as “weather”, “news”, “technology” or others. At step 60 the name and categorization information provided at step 58 is sent to PCM site 32.
  • Referring now to FIG. 4 a flowchart of the PCM site 32 is shown. At step 62 the output of step 50 of FIG. 2 is received. The URL of the website containing the page fragment of interest and the page fragment of interest is stored in PCM database 18. At step 64 any icons selected to indicate if information remains read or unread in the channel is processed to reformat it to the desired size for user interface 25 and stored in PCM database 18.
  • At step 66 the target selected at step 56 of FIG. 3 is received and stored in PCM database 18. The information defining the URL of the website containing the target information and the target information is stored in PCM database 18
  • At step 68 the name and categorization of the new channel provided by step 60 of FIG. 3 is stored in PCM database 18.
  • As can be appreciated by one skilled in the art if the information required to complete steps 62, 64, 66 and 68 is not provided to PCM site 32 processing will end and a channel will not be created. If all information is provided step 70 is invoked and is described with reference to FIG. 5.
  • Referring now to FIG. 5 a flowchart of the function of a selection analyzer is shown, this corresponds to the function implemented by step 70 of FIG. 4. Beginning at step 80 a test is made to determine if the fragment of interest matches a regular expression (regex). A regular expression is well known in the computing arts and can take on many forms. In essence it is a string of characters that describes or matches a set of strings, depending upon the syntax used. A set of regular expressions is stored in an HTML pattern dictionary (not shown). The HTML pattern dictionary is stored in PCM database 18 and comprises entries for regular expressions (regexs) that match dynamic content between static demarcation tags or content. Examples would be:
  • a) regexs that match a variety of standard, common and previously encountered date/time text strings such as “last updated Thurs. Jan. 11, 2007”.
    b) regexs of typical HTML tag sequences such as <a>, <div>, <tr>, <td> and others.
    c) computed regexs created by the selection analyzer as shown beginning at step 86 of FIG. 5.
  • If a matching regex is found at step 80, processing moves to step 82 where a change expression is built utilizing the text in the fragment of interest that precedes the regex located, the regex located, and text in the target selection that follows the regex located. Processing then moves to step 84 where the change expression is stored in PCM database 18 for use by Push Channel Monitor 28.
  • Returning to step 80 if a regex is not found in the HTML pattern dictionary, processing moves to step 86. At step 86 the fragment of interest is monitored on a regular basis while polling the website on which it resides at a user configurable rate, for example every 30 minutes. At this step, in order to provide feedback to the user that a channel is being created, a temporary icon is created on the user interface 25 of mobile device 12 such as an unread icon with a question mark on it. When the icon is selected a message such as “Channel Activation Not Complete” would be displayed.
  • After each polling attempt a test is made at step 88 to determine if a change has occurred in the fragment of interest. If a certain number of detected changes have been found (perhaps two to three) and they are of the same format, processing moves to step 90. This step involves comparing samples with a constant prefix and suffix to the substrings contained between them. The substrings are then compared to create a regex substring including “match any” operators in the regex.
  • At step 90 a regex is built based upon the changes identified in step 86, keeping the static information in the page fragment and utilizing wildcards such as “.*” to match changing information. At step 92 the newly created regex is stored in the pattern dictionary in PCM database 18. Over time regex entries will build up in the pattern dictionary thus saving time in creating a change expression. Processing then moves to step 82 where utilizing the new regex a change expression is created. Processing then moves to step 84 where the change expression is stored in PCM database 18 for use by Push Channel Monitor 28.
  • Referring now to FIGS. 6 a and 6 b flowcharts of the processes of a push channel monitor are shown. Beginning with FIG. 6 a a process for maintaining channels is shown. As discussed earlier PCM database 18 contains information defining a channel. Beginning at step 100 the definitions of the channels the last time the process was run are compared with the current definitions stored in PCM database 18. If a new channel is found, processing moves to step 102 where a new channel driver is created. Each channel has a channel driver associated with it for the purpose of monitoring changes on that channel in order to instruct IP Proxy 26 to push information. This process of determining what to push is described in FIG. 6 b. If a channel has been deleted processing moves to step 104 where the channel driver is deleted. If the channel is an existing channel, processing moves to step 106 where the channel definition in the driver is reloaded (as it may have changed) and any subscriber information is updated. A channel definition comprises the channel definition data stored in PCM database 18 which is copied to a memory resident object instantiated by the channel and controlled by the channel driver. Step 100 runs continually looking at the list of channels and determining the appropriate action to take.
  • Referring now to FIG. 6 b a process for pushing content to a channel is shown. As described earlier each channel has its own channel driver. Beginning at step 110 the channel driver for a channel scans for any changes to content on a web page as found in WWW database 18 (a URL of the WWW), utilizing the change expression stored in PCM database 18. At step 112 a test is made to determine if a change has occurred. If not processing returns to step 110. If a change has been detected processing moves to step 114 where the change activity for the channel is tracked. The purpose of this is to determine if content changes for this channel may be exceeding thresholds that indicate the changes being pushed may be utilizing too many system and network resources. At step 116 a test is made to determine if the change rate is beyond a desired threshold. If this is the case processing moves to step 118 where the channel driver is disabled. An example of disabling a channel driver would include abnormal amounts of traffic to a channel that could be interpreted as a Denial of Service (DOS) attack by the change target website. After step 118 no changed content is pushed and processing returns to step 110. If at step 116 it is determined that the change rate is not beyond a desired threshold, processing moves to step 120. At step 120 a test is made to determine if the channel driver has been disabled. If not, processing moves to step 124 where an indication of the changed content is sent to IP Proxy 26 to have the content pushed to all subscribers of the channel. If at step 120 it is determined that the channel has been disabled, it is reenabled at step 122 and processing moves to step 124. From step 124 processing returns to step 110.
  • Referring now to FIG. 7 a screen mockup of a channel management interface is shown generally as 130. Channel management interface 130 may be accessible to a user through user interface 25 or to a system administrator via security, administration and policy manager 34. FIG. 7 serves as an example of the type of information that may be presented in creating or modifying a channel.
  • Feature 132 indicates a portion of the screen that may be used to add a new channel as an alternative to having the user select a page fragment and change target by selecting text. In field 134 a name for the new channel is entered. In field 136 a title for the channel is entered. In field 138 a channel category is entered or selected from a set provided. In field 140 the URL of an icon to indicate unread items is entered. In field 142 the URL of an icon to indicate read items is entered. In field 144 the URL of the page to monitor for changes is entered. In field 146 the change expression to determine if changes of interest have occurred is entered. The fields of feature 132 correspond to the information entered by the user or generated by the system as described in FIGS. 2 through 5.
  • Feature 148 illustrates a table of the information on channels, the information being modifiable with the correct security authority. Column 150 contains the name field, column 152 contains the title field, column 154 contains the category field, column 156 contains the URL of the unread icon, column 158 contains the URL of the read icon, column 160 contains the URL of the page to monitor for changes and column 162 contains the change expression. The information displayed in feature 148 is provided to aid the reader in understanding the information stored in PCM database 18 to define a channel.
  • Although embodiments of the invention have been described as being implemented in software, one skilled in the art will recognize that embodiments may be implemented in hardware as well. Further, it is the intent of the inventor to include computer readable forms of the invention. Computer readable forms meaning any stored format that may be read by a computing device.
  • Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the following claims.

Claims (9)

1. A method in a server, the method comprising:
receiving, from a wireless device, information about a fragment of interest from a web page to be monitored for changes;
receiving, from the wireless device, information about a change target area, the change target area defining what content is to be pushed should a change occur in the fragment of interest;
building a change expression based on static content in the fragment of interest and a matching pattern expression from a pattern dictionary; and
creating a new content channel based on the change expression, wherein when changes in the web page are detected using the change expression said content is pushed to at least one subscriber of the new content channel.
2. The method of claim 1, further comprising:
prior to building the change expression, comparing the fragment of interest to the pattern dictionary to determine if the matching pattern expression exists in the pattern dictionary; and
if the matching pattern expression does not exist in the pattern dictionary:
monitoring the fragment of interest for a predetermined number of detected changes;
building a pattern expression based on the detected changes, wherein the pattern expression includes wildcards for detected changes of the same format and static information from the monitored fragment of interest; and
adding the pattern expression to the pattern dictionary.
3. The method of claim 1, wherein the matching pattern expression is a regular expression and the regular expression matches dynamic content and static content of the fragment of interest.
4. The method of claim 1, further comprising:
receiving, from the wireless device, a name and categorization for the new content channel.
5. The method of claim 1, further comprising:
storing the change expression in a content channel manager database, wherein the content channel manager database includes information about subscriptions to various content channels.
6. The method of claim 1, wherein building the change expression includes text in the fragment of interest that precedes the matching pattern expression, the matching pattern expression, and text in the fragment of interest that follows the matching pattern expression.
7. The method of claim 1, further comprising:
scanning for changes to content of the web page utilizing the change expression; and
pushing changed content to subscribers of the new content channel.
8. A method in a wireless device, the method comprising:
receiving, via a user interface of a mobile browser, a selection of a fragment of interest from a web page to be monitored for changes;
receiving, via the user interface, a selection of a change target area, the change target defining what content is to be pushed to the wireless device should a change occur in the fragment of interest; and
sending information about the fragment of interest and information about the change target area to a server configured to create a new content channel based on the fragment of interest and the change target area.
9. The method of claim 8, further comprising:
subscribing to the new content channel; and
receiving changed content via the new content channel, when changes occur to the fragment of interest.
US13/102,724 2007-02-22 2011-05-06 Dynamic Creation Of Content Channels Abandoned US20110213823A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US13/102,724 US20110213823A1 (en) 2007-02-22 2011-05-06 Dynamic Creation Of Content Channels

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US11/677,844 US7941497B2 (en) 2007-02-22 2007-02-22 Community-based method and system for creating and subscribing to dynamic push channels
US13/102,724 US20110213823A1 (en) 2007-02-22 2011-05-06 Dynamic Creation Of Content Channels

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US11/677,844 Continuation US7941497B2 (en) 2007-02-22 2007-02-22 Community-based method and system for creating and subscribing to dynamic push channels

Publications (1)

Publication Number Publication Date
US20110213823A1 true US20110213823A1 (en) 2011-09-01

Family

ID=39717168

Family Applications (2)

Application Number Title Priority Date Filing Date
US11/677,844 Expired - Fee Related US7941497B2 (en) 2007-02-22 2007-02-22 Community-based method and system for creating and subscribing to dynamic push channels
US13/102,724 Abandoned US20110213823A1 (en) 2007-02-22 2011-05-06 Dynamic Creation Of Content Channels

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US11/677,844 Expired - Fee Related US7941497B2 (en) 2007-02-22 2007-02-22 Community-based method and system for creating and subscribing to dynamic push channels

Country Status (1)

Country Link
US (2) US7941497B2 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110093789A1 (en) * 2009-10-16 2011-04-21 Yahoo! Inc. Method and system for completing an edit area of a web page
US9466027B2 (en) 2013-12-31 2016-10-11 International Business Machines Corporation Using ontologies to comprehend regular expressions
US9471700B2 (en) 2010-05-18 2016-10-18 Tksn Holdings, Llc System and method for monitoring changes in databases and websites

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2249529B1 (en) * 2004-03-23 2019-01-16 NDS Limited Optimally adapting multimedia content for mobile subscriber device playback
MX2009010456A (en) * 2007-03-30 2009-11-09 Research In Motion Ltd System and method for managing delivery of internet content.
US8806328B2 (en) * 2007-04-23 2014-08-12 Korss Advanced Solutions Ltd. Client application for identification of updates in selected network pages
US20110022680A1 (en) * 2009-04-24 2011-01-27 Moses Johnson Content distribution systems and methods
US20160014057A1 (en) * 2014-07-08 2016-01-14 Samsung Electronics Co., Ltd. Method and system for providing dynamically customized web push messages in a wireless network
US11895138B1 (en) * 2015-02-02 2024-02-06 F5, Inc. Methods for improving web scanner accuracy and devices thereof
US10924570B2 (en) * 2018-05-04 2021-02-16 Microsoft Technology Licensing, Llc Notification updates for saved sites
CN110417920B (en) * 2019-09-06 2022-11-01 浙江大搜车软件技术有限公司 Message pushing method, device, equipment and storage medium

Citations (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5983268A (en) * 1997-01-14 1999-11-09 Netmind Technologies, Inc. Spreadsheet user-interface for an internet-document change-detection tool
US6029175A (en) * 1995-10-26 2000-02-22 Teknowledge Corporation Automatic retrieval of changed files by a network software agent
US6076109A (en) * 1996-04-10 2000-06-13 Lextron, Systems, Inc. Simplified-file hyper text protocol
US6094681A (en) * 1998-03-31 2000-07-25 Siemens Information And Communication Networks, Inc. Apparatus and method for automated event notification
US20020010760A1 (en) * 2000-04-13 2002-01-24 Anthony Armenta Apparatus for and method of providing user notification and connectivity
US20020059457A1 (en) * 2000-07-06 2002-05-16 Ballard Glenn Wesley System and method for the remote creation of notification agents for wireless devices
US20020143813A1 (en) * 2001-03-28 2002-10-03 Harald Jellum Method and arrangement for web information monitoring
US6763388B1 (en) * 1999-08-10 2004-07-13 Akamai Technologies, Inc. Method and apparatus for selecting and viewing portions of web pages
US7076244B2 (en) * 2001-07-23 2006-07-11 Research In Motion Limited System and method for pushing information to a mobile device
US20070124693A1 (en) * 2005-11-29 2007-05-31 Microsoft Corporation Unlimited history store for navigational web applications
US20070204022A1 (en) * 2006-02-24 2007-08-30 Acer Inc. Method for acquiring information, and hand-held mobile communications device for implementing the method
US7433685B2 (en) * 1999-09-07 2008-10-07 Swisscom Mobile Ag Order method
US7512897B2 (en) * 2000-07-21 2009-03-31 Microsoft Corporation Integrated method for creating a refreshable web query
US7680810B2 (en) * 2005-03-31 2010-03-16 Microsoft Corporation Live graphical preview with text summaries
US7689667B2 (en) * 2002-02-21 2010-03-30 International Business Machines Corporation Protocol to fix broken links on the world wide web
US7873965B2 (en) * 2000-12-12 2011-01-18 Citrix Systems, Inc. Methods and apparatus for communicating changes between a user-interface and an executing application, using property paths
US20110035401A1 (en) * 2001-01-11 2011-02-10 Truelocal Inc. Method for Providing an Attribute Bounded Network of Computers
US8069407B1 (en) * 1998-12-08 2011-11-29 Yodlee.Com, Inc. Method and apparatus for detecting changes in websites and reporting results to web developers for navigation template repair purposes
US8131825B2 (en) * 2005-10-07 2012-03-06 Citrix Systems, Inc. Method and a system for responding locally to requests for file metadata associated with files stored remotely

Patent Citations (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6029175A (en) * 1995-10-26 2000-02-22 Teknowledge Corporation Automatic retrieval of changed files by a network software agent
US6076109A (en) * 1996-04-10 2000-06-13 Lextron, Systems, Inc. Simplified-file hyper text protocol
US5983268A (en) * 1997-01-14 1999-11-09 Netmind Technologies, Inc. Spreadsheet user-interface for an internet-document change-detection tool
US6094681A (en) * 1998-03-31 2000-07-25 Siemens Information And Communication Networks, Inc. Apparatus and method for automated event notification
US8069407B1 (en) * 1998-12-08 2011-11-29 Yodlee.Com, Inc. Method and apparatus for detecting changes in websites and reporting results to web developers for navigation template repair purposes
US6763388B1 (en) * 1999-08-10 2004-07-13 Akamai Technologies, Inc. Method and apparatus for selecting and viewing portions of web pages
US7433685B2 (en) * 1999-09-07 2008-10-07 Swisscom Mobile Ag Order method
US20020010760A1 (en) * 2000-04-13 2002-01-24 Anthony Armenta Apparatus for and method of providing user notification and connectivity
US20020059457A1 (en) * 2000-07-06 2002-05-16 Ballard Glenn Wesley System and method for the remote creation of notification agents for wireless devices
US7512897B2 (en) * 2000-07-21 2009-03-31 Microsoft Corporation Integrated method for creating a refreshable web query
US7873965B2 (en) * 2000-12-12 2011-01-18 Citrix Systems, Inc. Methods and apparatus for communicating changes between a user-interface and an executing application, using property paths
US20110035401A1 (en) * 2001-01-11 2011-02-10 Truelocal Inc. Method for Providing an Attribute Bounded Network of Computers
US20020143813A1 (en) * 2001-03-28 2002-10-03 Harald Jellum Method and arrangement for web information monitoring
US6915482B2 (en) * 2001-03-28 2005-07-05 Cyber Watcher As Method and arrangement for web information monitoring
US7076244B2 (en) * 2001-07-23 2006-07-11 Research In Motion Limited System and method for pushing information to a mobile device
US7689667B2 (en) * 2002-02-21 2010-03-30 International Business Machines Corporation Protocol to fix broken links on the world wide web
US7680810B2 (en) * 2005-03-31 2010-03-16 Microsoft Corporation Live graphical preview with text summaries
US8131825B2 (en) * 2005-10-07 2012-03-06 Citrix Systems, Inc. Method and a system for responding locally to requests for file metadata associated with files stored remotely
US20070124693A1 (en) * 2005-11-29 2007-05-31 Microsoft Corporation Unlimited history store for navigational web applications
US20070204022A1 (en) * 2006-02-24 2007-08-30 Acer Inc. Method for acquiring information, and hand-held mobile communications device for implementing the method

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110093789A1 (en) * 2009-10-16 2011-04-21 Yahoo! Inc. Method and system for completing an edit area of a web page
US9690769B2 (en) * 2009-10-16 2017-06-27 Excalibur Ip, Llc Method and system for completing an edit area of a web page
US9471700B2 (en) 2010-05-18 2016-10-18 Tksn Holdings, Llc System and method for monitoring changes in databases and websites
US9466027B2 (en) 2013-12-31 2016-10-11 International Business Machines Corporation Using ontologies to comprehend regular expressions
US9471875B2 (en) 2013-12-31 2016-10-18 International Business Machines Corporation Using ontologies to comprehend regular expressions
US10452703B2 (en) 2013-12-31 2019-10-22 International Business Machines Corporation Using ontologies to comprehend regular expressions

Also Published As

Publication number Publication date
US7941497B2 (en) 2011-05-10
US20080209000A1 (en) 2008-08-28

Similar Documents

Publication Publication Date Title
US7941497B2 (en) Community-based method and system for creating and subscribing to dynamic push channels
US7512569B2 (en) User defined components for content syndication
US9756068B2 (en) Blocking domain name access using access patterns and domain name registrations
US8407482B2 (en) User session dependent URL masking
US6789201B2 (en) Anti-virus toolbar system and method for use with a network browser
US8074162B1 (en) Method and system for verifying the appropriateness of shared content
RU2522103C2 (en) Update notification method and browser
US6606525B1 (en) System and method of merging static data in web pages
EP1020804B1 (en) A system for managing user-characterizing network protocol headers
US8914355B1 (en) Display-content alteration for user interface devices
US20070130327A1 (en) Browser system and method for warning users of potentially fraudulent websites
US20100169472A1 (en) Web Access Monitoring Method and Associated Program
EP1641211A2 (en) Web server and method for dynamic content.
US20050108363A1 (en) Web page update notification method and web page update notification device
US20180239794A1 (en) Caching of updated network content portions
WO2010094927A1 (en) Content access platform and methods and apparatus providing access to internet content for heterogeneous devices
US20060069714A1 (en) System enhancement using client context information
EP3080722B1 (en) Web page rendering on wireless devices
KR20080077019A (en) Improper communication program restriction system and program
US20090037741A1 (en) Logging Off A User From A Website
CA2626168C (en) Community-based method and system for creating and subscribing to dynamic push channels
US10104196B2 (en) Method of and server for transmitting a personalized message to a user electronic device
US8819049B1 (en) Frame injection blocking
KR101891300B1 (en) Method and apparatus for providing secure internet connection
CN113391855A (en) Information processing method and device and storage medium

Legal Events

Date Code Title Description
AS Assignment

Owner name: RESEARCH IN MOTION LIMITED, CANADA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SCHMIDT, DAVID;REEL/FRAME:026239/0426

Effective date: 20070222

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION

AS Assignment

Owner name: BLACKBERRY LIMITED, ONTARIO

Free format text: CHANGE OF NAME;ASSIGNOR:RESEARCH IN MOTION LIMITED;REEL/FRAME:034179/0923

Effective date: 20130709