HK1180053A - Dynamic browser icons - Google Patents

Description

Dynamic browser icons

Technical Field

The present application relates generally to icons and more particularly to icons that may be dynamically updated.

Background

Push technology describes a type of internet-based communication in which a publisher or central server initiates a request for a given transaction. In contrast, pull techniques are of the type in which a recipient or client initiates a request for information transfer. Push services are often based on information preferences expressed in advance, which is often referred to as a publish/subscribe model. In this model, clients subscribe to various channels of information. The server pushes information out to the user as long as new content is available on one of those channels.

Synchronous conferencing and instant messaging are typical examples of push services. Chat messages and sometimes files are pushed to the user when received by the messaging service. Email is also a well known push system. In a typical email configuration, the SMTP protocol is used as the push protocol. However, the last step from the mail server to the desktop computer typically uses a pull protocol such as POP3 or IMAP. Modern email clients make this step appear to be instant by repeatedly polling the mail server to frequently check the server for new mail. Icons are small graphical symbols (usually simple pictures) that represent programs, commands, data files, etc. in a graphical user interface. For example, the icon may be used to launch an application (e.g., open)). Dynamic icons are also known. For example, a dynamic icon is an icon that can be updated, changed, or animated. However, dynamic icons are typically associated with applications stored on the client device. Thus, there is a need to develop applications specifically designed for client devices (e.g., "mobile phone applications"). One example is a weather application that can be downloaded onto a mobile phone. An icon associated with the weather application displays an update of the local weather. Selection of the icon launches the weather application. The weather icon is updated by the push service as long as the update is available.

Greater accessibility to dynamic icons is desirable. In particular, it is desirable to allow dynamic icons without the need to develop client-specific applications.

Disclosure of Invention

The present application allows for dynamic icons that are readily available to third party websites. One advantage of some of the embodiments is that the user is not required to download third party specific applications. Instead, multiple dynamic icons may be implemented using a standard browser.

In one embodiment, a dynamic icon is displayed on the client device. The dynamic icon is associated with a third party website and may have an address of the associated website. The client device may receive information representing an update to the dynamic icon and this information may be displayed in association with the dynamic icon. If selected, the browser is launched and the address is passed to the browser as an input parameter. The browser may use the address to access a third-party website and display a content page associated with the website. The message may include a change to an address to be accessed when the browser is launched.

In another embodiment, information such as the geographic location of the client device may be dynamically communicated from the client to the third party website. The third-party website may then select information to be sent to the client device for updating the dynamic icon, and the update may depend on the geographic location. In a simple example, the third-party website may determine that the client device is within a particular proximity of the store, and may update the dynamic icon with store-specific sales to entice the user to the store.

In various embodiments, the client device may pull information from the third party site to receive the dynamic update, or the third party server may push information to the client device. In a pull embodiment, the information used to update the dynamic icon may be stored in metadata located on the third-party website. For example, HTML tags (e.g., div tags) may be used to store information to be pulled.

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

The foregoing and other objects, features and advantages of the invention will become more apparent from the following detailed description, which proceeds with reference to the accompanying figures.

Drawings

FIG. 1 is an example mobile phone that may be used to update a dynamic browser icon.

Fig. 2 is an example mobile phone displaying a home screen including a dynamic browser icon.

FIG. 3 is an embodiment of a system for displaying a dynamic browser icon on a client device.

FIG. 4 is another embodiment of a system for displaying dynamic browser icons.

FIG. 5 is a flow chart of a method for updating a dynamic browser icon.

FIG. 6 is a specific exemplary flow chart illustrating how a dynamic icon may be used with a third party website.

FIG. 7 is a flow diagram of an embodiment in which a client device pulls information from a third party website.

FIG. 8 is a flow diagram of an embodiment for updating a dynamic browser icon.

FIG. 9 is a detailed flow diagram of an embodiment for displaying content from a third party website using a dynamic browser icon.

FIG. 10 is an embodiment illustrating that a dynamic browser icon may be updated across different client platforms.

Detailed Description

Fig. 1 is a system diagram depicting an exemplary mobile device 100 including various optional hardware and software components, shown generally at 102. Any component 102 in the mobile device may communicate with any other component, but not all connections are shown for ease of illustration. The mobile device can be any of a variety of computing devices (e.g., a cellular telephone, a smart phone, a handheld computer, a Personal Digital Assistant (PDA), etc.) and can allow wireless two-way communication with one or more mobile communication networks 104, such as a cellular or satellite network.

The illustrated mobile device 100 may include a controller or processor 110 (e.g., signal processor, microprocessor, ASIC, or other control and processing logic circuitry) for performing tasks such as signal coding, data processing, input/output processing, power control, and/or other functions. The operating system 112 can control the allocation and usage of the components 102 and support one or more application programs 114. The application programs may include common mobile computing applications (e.g., email applications, calendars, contact managers, web browsers, messaging applications), or any other computing application.

The illustrated mobile device 100 may include memory 120. Memory 120 may include non-removable memory 122 and/or removable memory 124. The non-removable memory 122 may include RAM, ROM, flash memory, a hard disk, or other well-known memory storage technologies. The removable memory 124 may comprise flash memory or a Subscriber Identity Module (SIM) card as is well known in GSM communication systems, or other well known memory storage technologies such as "smart cards". The memory 120 may be used to store data and/or code for running the operating system 112 and applications 114. Example data may include web pages, text, images, sound files, video data, or other data sets sent to and/or received from one or more network servers or other devices via one or more wired or wireless networks. The memory 120 can be used to store a subscriber identifier, such as an International Mobile Subscriber Identity (IMSI), and an equipment identifier, such as an International Mobile Equipment Identifier (IMEI). These identifiers may be transmitted to a network server to identify the user and equipment.

The mobile device 100 may support one or more input devices 130, such as a touch screen 132, microphone 134, camera 136, physical keyboard 138, and/or trackball 140, and one or more output devices 150, such as a speaker 152 and a display 154. Other possible output devices (not shown) may include piezoelectric or other haptic output devices. Some devices may provide more than one input/output function. For example, the touch screen 132 and the display 154 may be combined in a single input/output device. The touch screen 132 may support dynamic browser icons. The dynamic browser icon may be displayed on a home screen, which is typically the screen displayed when the phone is turned on. The home screen is a reference screen that generally cannot be further minimized and contains icons representing applications. As described further below, a dynamic browser icon is an icon whose image may change based on updates generated by a third-party website. In addition, a dynamic browser icon is an icon that launches a browser when selected. The address is then passed to the browser for use as a launch page.

The wireless modem 160 may be coupled to an antenna (not shown) and may support bi-directional communication between the processor 110 and external devices, as is well understood in the art. The modem 160 is shown generically and may include a cellular modem and/or other radio-based modem (e.g., bluetooth or Wi-Fi) for communicating with the mobile communications network 104. The wireless modem 160 is typically configured for communication with one or more cellular networks, such as a GSM network for data and voice communication within a single cellular network, between cellular networks, or between a mobile device and a Public Switched Telephone Network (PSTN).

The mobile device may also include at least one input/output port 180, a power supply 182, a satellite navigation system receiver 184 such as a Global Positioning System (GPS) receiver, an accelerometer 186, and/or a physical connector 190, which may be a USB port, an IEEE 1394 (firewire) port, and/or an RS-232 port. The illustrated components 102 are not required or all-inclusive, and any components can be deleted and other components can be added.

Fig. 2 depicts a front view 210 of an example mobile device 200 displaying a Graphical User Interface (GUI) on a touch screen display 205. The mobile device 200 may also include several hardware buttons, including a camera shutter button 220 located on a side surface of the mobile device, and a search button 222, a main interface button 224, and a back button 226, which may be located on a front surface of the mobile device. These hardware buttons may be used to invoke and/or perform various operations using mobile device 200. However, these buttons may be eliminated or other buttons may be added. The camera shutter button 220 may be used to invoke and/or execute an image capture application, as well as control functions within the image capture application such as auto-focusing and/or operating a camera shutter. Search button 222 may be used to invoke and/or execute a user interface for searching data. Main interface button 224 may be used to navigate software functions on mobile device 300 by, for example, setting the mobile device as a home screen or invoking other assigned functions. The back button 226 may be used to navigate software functions by, for example, requesting browsing of previously requested objects using the mobile device 200.

When mobile device 200 powers up or selects main interface button 224, the touch screen display returns to the home screen shown. The home screen is a reference screen that generally cannot be minimized and displays the icon shown generally at 230. Any number of icons may be located on the home screen, but only three are shown for purposes of illustration. The icon may represent an application that is stored locally and launched upon selection of the icon. For example, a browser icon 232 is shown that launches a browser when selected. Launching the browser causes a window, typically including a button or menu for the user to enter commands, to open. The browser can be automatically opened to a predetermined page based on settings associated with the browser. Browser icon 232 is generally considered a static icon because it does not change appearance. Another static icon 234 is also shown. Static icon 234 represents an internet site and can be stored as an icon in the same manner as a "favorite" stored in a conventional browser. Thus, the static icon 234 is used to launch the browser and open the page associated with the static icon (in this example, the Bing page). Icon 240 is a dynamic icon. The dynamic icon may change appearance based on information provided from the third-party website. For example, icon 240 corresponds to a store called "The Home Depot" that is currently shown selling smoke alarms. Thus, the icon has been changed to reflect the current sale. Other forms may be used to display the dynamic icons. The internet address associated with the icon may also be dynamically updated. Thus, if the user selects icon 240, the browser is launched and parameters associated with the sale are passed to the browser. A web page associated with the sale may then be opened. Although not shown, additional dynamic icons for launching a browser application may be used. Thus, multiple dynamic icons may be linked to a single browser application, each representing a potentially different launch page.

FIG. 3 is an embodiment of a system for implementing dynamic browser icons. There are a variety of techniques that may be used to implement dynamic browser icons, and FIG. 3 is merely one example. The mobile phone 310 is coupled to a third party server 320 via a network 330. The mobile phone 310 includes an operating system 340, a browser application 342, and a dynamic icon 350 that is displayed on the user interface of the mobile phone. The dynamic icon may be associated with an address parameter 352. The dynamic icon is a link for launching the browser 342, but has a particular internet address associated with an address parameter. Thus, the internet address is passed to the browser so that the browser knows the launch page to download. In this way, multiple dynamic icons may be located on the home screen, and each dynamic icon may be used to launch the same browser application, but with a different internet address for launching the page. Thus, multiple dynamic icons may be created using the same application.

To obtain the updates, the mobile phone links to the third party server 320 through a network, shown generally at 330. The home page 360 may be associated with an internet address in the address parameter 352. The home page may be written in a markup language such as HTML and may include presentation content 362 for generating content visible to the user and metadata not for generating visible content. In some embodiments, the metadata may be used to communicate dynamic information to the mobile phone 310 to update the dynamic icon. For example, a tab (e.g., div tab) may be searched on the home page to determine whether dynamic content is available. An example of using a div identifier is as follows:

using div ID

A Cascading Style Sheet (CSS) may alternatively be used. Examples are as follows:

using CSS style

Other techniques such as RSS feeds may alternatively be used.

The main page 360 may have a link located thereon that, when selected, displays a sub-page 366, as is well known in the art. The sub-page 366 may also include presentation content 368 and metadata 370 that may be used to update the dynamic icon 350. When updating the dynamic icon 350, the address parameter 352 may be modified to change the launch page used by the browser 342. For example, if a third party server wishes to redirect the user of the mobile phone 310 to a sub-page 366 due to a sales item, the address parameter 352 may be modified to point to a pointer to the sales and the image associated with the dynamic icon may be modified to make the user aware of the sales.

Fig. 4 is an alternative embodiment in which a mobile phone 410 may communicate with a third party server 420 over a network 430. The operating system 440 can be used to launch the browser 442 in response to selection of the dynamic icon 450. When a selection is made of a dynamic icon 450, the operating system 440 accesses a database 452 that includes parameters associated with the dynamic icon. For example, the address parameters may be stored and passed to the browser by the operating system. Updates to the dynamic icon may be made via the operating system, which may update the database 452. The remaining aspects of fig. 4 may operate similarly to what has been described with reference to fig. 3.

In either of the embodiments of fig. 3 or fig. 4, the mobile device may pull updates from a third party server. In one example, such pulling is performed by: the web site page is searched for the appropriate HTML tag (e.g., div tag) and the data associated with such tag is used as a dynamic update upon finding such tag. The timing of when to pull may depend on a number of factors. For example, to conserve battery life, the pull may be dependent on a connection to a power source, upon exiting sleep mode, upon connecting to Wi-Fi, or upon the user connecting to a third party site. The update may be modified based on the mobile device. For example, the mobile device may pass browser type or other information to a third party server through a header (e.g., user agent). In response to this information, the third-party website may modify the updates, such as making the updates best suited for the particular browser type. Push-type updates may be made by a third-party website actively pushing data to a mobile client to update an address associated with a dynamic icon. Alternatively, although a mobile phone is disclosed, various platforms may be used instead, such as a laptop computer, desktop computer, tablet, and the like.

FIG. 5 is a flow chart of a method for updating a dynamic browser icon. At process block 510, a dynamic icon for launching a browser is displayed. At process block 520, information associated with the dynamic icon is received. The information may come from a third party server and include updates to the dynamic icon, including image updates and/or address updates. At process block 530, the update is displayed in association with the dynamic icon.

FIG. 6 is a flow diagram of a particular embodiment where the third party website is "Home Depot" for purposes of illustration. At process block 610, the Home Depot site 620 is accessed using the phone browser. The user then executes a command to pin (pin) the station 620 to the user's home screen. The phone (e.g., operating system) searches the website for a div tag with a "mobile tile" div. If such a div tag is not found at decision block 630, a browser icon displaying a simple static thumbnail image is generated (process block 640). If a div tag is found, a dynamic icon is generated using data obtained from mobile div (process block 650). Image and/or text data may be pulled from the div segment and used to generate a dynamic icon. If geographic location is also used, the generated dynamic icon may incorporate location-related information provided from a third-party server. Subsequently, when the user selects the dynamic icon, the browser is launched and the data associated with the dynamic icon is passed to the browser. In this case, a sub-page of the Home Depot site is passed to the browser to enable the site to be downloaded at startup (process block 660).

An example code snippet is shown below and may be used to update metadata on a third-party site. Specifically, the current location of the phone is communicated to the third party site. The third party site can use the location information to determine if the phone location is equal to the store location. If so, the metadata used to update the dynamic icon can be customized for that phone to provide specific details about the store location. The metadata may include a browser identifier obtained from user agent information received from the phone.

MobileTile.js

FIG. 7 is a flow chart of a method for updating a dynamic icon. At process block 710, the dynamic icon may include an associated address parameter. The dynamic icon may have associated code that responds to simple requests from the operating system using a browser application. For example, at process block 720, the operating system may request that the dynamic icon be updated. In response to the request, the dynamic icon may control the browser to navigate to an address in the address parameters and retrieve metadata associated with the dynamic icon. The address may be a third party website that includes metadata and content for display. At process block 730, the dynamic icon may be updated using metadata including the new address stored as an address parameter. The new address may be, for example, a sub-page associated with the website. If the user selects the dynamic icon, the browser is launched with a new address as a parameter (which may be provided from the dynamic icon or the operating system). The browser then displays the contents of the sub-page of the website (process block 740).

Fig. 8 is a flow chart of a method for updating a client device using a dynamic icon. At process block 810, a dynamic icon is displayed, such as on a home screen of the user device. At process block 812, the dynamic icon is automatically modified based on pushing or pulling information from a third-party website hosted by a third-party server. At process block 814, the browser is launched using the address parameters passed to the browser in response to the user's selection of the icon. The address parameter may be passed using code associated with the icon itself, or alternatively the operating system may pass the address parameter to the browser. In any case, the browser is launched with the parameters passed to the browser in association with the dynamic icon. The browser may be launched using a plurality of different dynamic icons, and each dynamic icon may send a different address (e.g., a URL) to the browser to serve as the first launch page to be displayed.

Fig. 9 is a detailed flowchart of a method for generating and updating a dynamic icon. At process block 910, a request to add a dynamic icon to a home screen is received. With many client devices, it is possible to navigate to or otherwise access a website and then generate an icon using a simple command, such as a pin command. Icons associated with the web site are generated and placed in one position on the home screen along with other icons. At process block 912, the website address is associated with the dynamic icon. The website address may be stored in code associated with the dynamic icon itself, or in a database accessible by the icon or operating system. At process block 914, the update is obtained using the website address. Typically, a web site is searched for special commands regarding dynamic icon updates, such as by using markup language tags. At process block 916, the dynamic icon image is updated to display the update. A typical update is to change the website address associated with the dynamic icon so that selection of the icon accesses the changed address. At process block 918, in response to user selection of the dynamic icon now characterizing the update, a content page associated with the website address is displayed.

FIG. 10 illustrates a general example of a suitable implementation environment 1100 in which described embodiments, processes, and techniques may be implemented.

In the example environment 1100, various types of services (e.g., computing services) are provided by the cloud 1110. For example, the cloud 1110 can include a collection of computing devices, which can be centrally located or distributed, that provide cloud-based services to various types of users and devices connected via a network, such as the internet. The implementation environment 1100 may be used in different ways to implement computing tasks. For example, some tasks (e.g., processing user input and presenting a user interface) may be performed on local computing devices (e.g., connected devices 1130, 1140, 1150), while other tasks (e.g., storing data to be used in subsequent processing) may be performed in the cloud 1110.

In the example environment 1100, the cloud 1110 provides services to connected devices 1130, 1140, 1150 having various screen capabilities. Connected device 1130 represents a device having a computer screen 1135 (e.g., a mid-sized screen). For example, connected device 1130 may be a personal computer such as a desktop computer, laptop computer, notebook, netbook, or the like. Connected device 1140 represents a device having a mobile device screen 1145 (e.g., a small screen). For example, connected device 1140 may be a mobile phone, a smart phone, a personal digital assistant, a tablet computer, or the like. The connected device 1150 represents a device with a large screen 1155. For example, connected device 1150 may be a television screen (e.g., a smart television) or another device connected to a television (e.g., a set-top box or game console), and so on. One or more of the connected devices 1130, 1140, 1150 may include touch screen capabilities. Touch screens can accept input in different ways. For example, capacitive touch screens detect touch input when an object (e.g., a fingertip or stylus) distorts or interrupts a current flowing through the surface. As another example, a touch screen may use an optical sensor that detects a touch input when a light beam from the optical sensor is interrupted. Physical contact with the surface of the screen is not necessary for input to be detected by some touch screens. Devices without screen capabilities may also be used in the example environment 1100. For example, the cloud 1110 can provide services to one or more computers (e.g., server computers) that do not have displays.

Services may be provided by cloud 1110 through service provider 1120, or through other providers of online services (not depicted). For example, the cloud services may be customized to the screen size, display capabilities, and/or touch screen capabilities of a particular connected device (e.g., connected devices 1130, 1140, and 1150).

In example environment 1100, cloud 1110 uses, at least in part, service provider 1120 to provide the techniques and solutions described herein to various connected devices 1130, 1140, 1150. For example, service provider 1120 may provide a centralized solution for various cloud-based services. Service provider 1120 can manage service subscriptions for users and/or devices (e.g., connected devices 1130, 1140, 1150, and/or their respective users).

The dynamic icon may be integrated across devices 1130, 1140, and 1150 such that any updates to the dynamic icon on one device can be propagated to other devices of users having a common account across the devices.

Although some of the operations of the disclosed methods are described in a particular, sequential order for convenient presentation, it should be understood that this method of description encompasses rearrangement, unless a particular ordering is required by specific language set forth below. For example, in some cases, operations described sequentially may be rearranged or performed concurrently. Moreover, for the sake of brevity, the attached figures may not show the various ways in which the disclosed methods can be used in conjunction with other methods.

Any of the disclosed methods may be implemented as computer-executable instructions stored on one or more computer-readable media (e.g., non-transitory computer-readable media, such as one or more optical media discs, volatile memory components (such as DRAM or SRAM), or non-volatile memory components (such as hard drives)) and executed on a computer (e.g., any commercially available computer, including smart phones or other mobile devices that include computing hardware). Any of the computer-executable instructions for implementing the disclosed techniques, as well as any data created and used during implementation of the disclosed embodiments, can be stored on one or more computer-readable media (e.g., non-transitory computer-readable media). The computer-executable instructions may be part of a dedicated software application or a software application that is accessed or downloaded, for example, via a web browser or other software application, such as a remote computing application. For example, such software can be executed on a single local computer (e.g., any suitable commercially available computer) or in a network environment (e.g., via the internet, a wide area network, a local area network, a client-server network (such as a cloud computing network), or other such network) using one or more network computers.

For clarity, only certain selected aspects of software-based implementations are described. Other details known in the art are omitted. For example, it should be understood that the disclosed technology is not limited to any particular computer language, or program. For example, the disclosed technology may be implemented by software written in C + +, Java, Perl, JavaScript, AdobeFlash, or any other suitable programming language. Also, the disclosed techniques are not limited to any particular computer or type of hardware. Certain details of suitable computers and hardware are well known and need not be set forth in detail in this disclosure.

Further, any of the software-based embodiments (including, for example, computer-executable instructions for causing a computer to perform any of the disclosed methods) may be uploaded, downloaded, or accessed remotely via suitable communication means. Such suitable communication means include, for example, the internet, the world wide web, an intranet, software applications, electrical cables (including fiber optic cables), magnetic communication, electromagnetic communication (including RF, microwave, and infrared communication), electronic communication, or other such communication means.

The disclosed methods, apparatus, and systems should not be considered limiting in any way. Rather, the invention is directed to all novel and non-obvious features and aspects of the various disclosed embodiments, alone or in various combinations and subcombinations with one another. The disclosed methods, apparatus, and systems are not limited to any specific aspect or feature or combination thereof, nor do the disclosed embodiments require that any one or more specific advantages be present or problems be solved.

In view of the many possible embodiments to which the principles of the disclosed invention may be applied, it should be recognized that the illustrated embodiments are only preferred examples of the invention and should not be taken as limiting the scope of the invention. Rather, the scope of the invention is defined by the appended claims. Accordingly, all that comes within the scope of these claims is claimed as the invention.

Claims (10)

1. A method of updating a client device, comprising:

displaying a dynamic icon on the client device, wherein the dynamic icon is used to launch a browser stored on the client device and to access a third-party website associated with the dynamic icon;

receiving, on the client device, information associated with the dynamic icon from the third-party website; and

using the information to update the dynamic icon by displaying the information on the client device in association with the dynamic icon.

2. The method of claim 1, further comprising retrieving the information from metadata stored on the third-party website.

3. The method of claim 2, wherein retrieving the information comprises searching the third-party website for a markup language tag and retrieving information associated with the markup language tag.

4. The method of claim 1, wherein displaying the dynamic icon is on a home screen of the client device, the home screen being a reference screen from which other applications can be launched, and the dynamic icon is associated with an address parameter passed to the browser to launch the browser.

5. The method of claim 1, wherein the dynamic icon comprises code to access the third-party website to receive the information.

6. The method of claim 1, further comprising sending a browser type to the third-party website, and in response thereto, the third-party website updating information for the dynamic icon.

7. The method of claim 1, further comprising sending a geographic location of the client device to the third-party website, and the third-party website updating information based on the geographic location.

8. The method of claim 1, further comprising accessing the third-party website and generating an icon associated with the third-party website on the client device in response to a user request.

9. One or more computer-readable storage media having stored thereon computer-executable instructions for causing a mobile computing device to perform a method, comprising:

displaying a dynamic icon associated with a third-party website;

dynamically modifying the dynamic icon based on an update from the third-party website; and

in response to receiving user input selecting the dynamic icon, launching a browser on the mobile computing device and using the browser to access a website address associated with the dynamic icon.

10. A method of presenting dynamic information on a phone, comprising:

receiving a request to add a dynamic icon to a home screen on a phone;

associating a website address with the dynamic icon;

using the website address to access a website and obtain an update of information associated with the dynamic icon;

displaying the update on the phone in association with the dynamic icon; and

in response to receiving a selection of the dynamic icon, launching a browser and displaying a content page associated with the website address.