System and method for managing and using electronic widgets
A small control and user-friendly technology, applied to electrical components, input/output process of data processing, hardware monitoring, etc., can solve problems such as personal network access fees
Inactive Publication Date: 2009-09-09
0 Cites 6 Cited by
AI-Extracted Technical Summary
Problems solved by technology
This may be annoying to the individual and/or may result in substant...
 Referring to FIG. 8, a system for storing and providing web page information to users is illustrated. The system may include a server 810 , a database 880 , a fetcher 830 and a web page 890 . Database 880 may store text 885 included in web page 890 while storing links 886 to images associated with the text and/or displayed in web page 890 . They can save space in the database 880 and allow the user to at least view the text while the image can be downloaded or transferred. If the user requests...
Widgets may generally be used to convey information from one or more content sources to a user device. The widgets may operate on the user device and be configured to detect and receive new information feeds. The new information feeds may be filtered according to various factors including user preferences. When new information is received for a widget, the widget may include a new information indicator. Further, widget clients may be used to manage the widgets including the setting of various options and modes. A widget client may also be configured to receive widget recommendations from one or more widget providers as well as to provide traffic information for one or more widgets. Additionally, widgets may be sent from one device to another device through a widget service provider.
Hardware monitoringComputer security arrangements +4
Service providerService provision +2
- Experimental program(1)
 In the following description of the various embodiments, reference is made to the accompanying drawings that form a part of the specification and illustrate by way of example various embodiments in which the present invention can be implemented. It will be understood that other embodiments may be utilized and structural and functional modifications may be made without departing from the scope and spirit of the present invention.
 figure 1 Illustrated is a user interface for managing widgets and widget groups on a communication device such as a personal data assistant (PDA) mobile terminal. The widgets as used herein refer to interface units and/or applications that provide and transmit information such as advertisements, weather information or other limited information from one or more content sources based on various factors. The user interface 100 may include various options 105, such as widget 105a, client 105b, mode option 105d, and exit option 105c. Options 105 may be presented to the user as a list of menu structures. Instead, option 105 may be displayed as multiple independent buttons (not shown). The widget option 105a may include one or more optional actions or options, such as reloading and removing. The user of the device may select a reload action or option to load the widget from the web server where the user has registered his device to obtain the selected widget and/or content associated with the widget. Instead or in addition, the user can also use the reload option to re-download (eg refresh) the widget or the content associated with the widget. For example, if a new version of the widget is available, the user can reload the widget to obtain the new version. In another example, if the content of the widget is out of date due to various circumstances, the user may request to reload the widget to restore the normal operation of the widget. On the other hand, users use the removal option to delete widgets from their device and/or their account. In one or more configurations, if the user has not yet accessed the widget (for example, accessing or opening the content of the widget), only options for sending, reloading, and/or removing can be provided.
The client options 105b may also include optional actions or options, such as offline, setting, and marking read all. Specifically, select Offline to terminate the connection to the network. In addition, the setting options can include modifiable setting attributes, such as connection type, allowable alarms, connection and mode at startup. The connection type can define the way the device connects to one or more content servers. Options for connection type can include socket and http. The allow alarm attribute can provide the user with options to activate and deactivate the alarm. Alarms can include audio, video, and/or tactile components and can be set based on user needs and preferences. For example, if new content is available and if the new content contains a specific phrase, the user can set an alert. In another example, the user can create an alert for new content associated with specified subject content. In one or more configurations, if the user activates an alert, the user can be alerted to changes in the server source. For example, if a change is found in the content stored on the server, an alarm signal can be sent to the user through the network connection to which the device and the server are connected. If the user's device includes multiple network interfaces (e.g., multiple air interfaces), the user can select an interface for receiving server content and/or sources. Instead or in addition, only changes in the following content can cause an alarm to be sent to the user's device, that is, the content is part of the server source to the user's device.
 In addition, the user can also choose whether or not the device will be online immediately upon startup (such as establishing a connection with the content server). The online option at startup allows the user to choose yes, no, and ask. For example, if the user selects the option to go online at the beginning, the device can establish a connection with one or more servers from which the user wants to receive content sources. Selecting the query setting can cause the device to ask the user to determine whether the device should be online when it is started. Various types of network interfaces and network protocols include Bluetooth (BLUETOOTH TM ), wireless local area network (WLAN), cellular network, etc.
 The mode option 105d may allow the user to choose between the full mode and the reduced mode. The full mode may include client or widget user interface options and/or features not provided in the condensed mode. In addition, the full mode may involve more processing power than the reduced mode and therefore more battery power (for mobile devices). Therefore, if the user's device is low on power, the user can choose to enable the lite mode instead of the full mode to save battery life. The compact mode also specifies the maximum number of widgets to be displayed on the interface and/or the maximum number of data to receive and process from the content server. The option 105c of the exit option may allow the user to exit the menu screen and/or return to the previous user interface. Instead or in addition, the user can also manually select (ie customize) the features and/or options associated with his or her interface. For example, the user may be given the option to download images automatically or only when requested. If the user's network connection has limited bandwidth, he may wish to download images only when requested. This option may be, for example, an option named "download/show image".
 In one or more arrangements, the user may use one or more soft keys associated with the communication device to select options. For example, each option can correspond to a different number key on the number keypad of the mobile phone. In another embodiment, the software may be located adjacent to a display screen (not shown) that displays the user interface 100. The soft key may correspond to one of the options 105 based on the alignment between the key and the options 105. The user can also interact with option 105 using voice commands and/or input through the touch-sensitive display surface.
 figure 2 The user interface associated with the selection widget or widget group is illustrated. For example, when a widget or widget group is opened by selecting a chart, the following user interface may be displayed, the user interface showing selectable options 205 for viewing and/or selecting new widgets, and selectable options for accessing the inbox 210. An optional option 215 for monitoring services and/or an optional option 220 for viewing user information. The option 205 for viewing and/or selecting new widgets can provide the user with new and/or popular widgets that are available on the server associated with the currently opened widget or widget group and have not been downloaded by the user or user device. Information associated with the control. This allows the user to retrieve new and/or popular content back to the user's device. In one or more instances, the popularity of content or widgets can be determined based on the number of downloads by other users of the service. Demographics can also be used when suggesting new and/or popular content to users.
 The inbox option 210 provides the user with the following information and messages, which may be related to the service/system from which the user is obtaining widgets or otherwise associated with one or more widgets. For example, when registering with a specific widget service, the user may receive a welcome message (for example, "Welcome you have successfully registered the widget from WidgetService in your phone"). Messages related to widgets may include information related to widgets or possibly available related widgets. On the other hand, the business monitoring option 215 can be used to access information related to the widgets downloaded to the user's device and the size associated with those downloaded widgets. For example, each widget can be identified by the content name and content size recorded during download. You can also record or monitor business information for specific widgets. For example, you can track the amount of content downloaded through widgets. In one or more arrangements, business information can be monitored and stored in the content server. In this way, business information can be loaded from the content server to the user's device through the existing interface in the user's device. In one example, the content server may store the content name and content size associated with the user's device or the user's account. When there is a request from the user, the content server can retrieve the business information from the storage and send the information to the user's device. Instead or in addition, the user's device can store business information locally.
 image 3 Illustrated is a user interface displaying a list of widgets 300 that can be downloaded to the user's device. The widgets displayed in the list 300 can be selected for inclusion on the list 300 based on the user's activity, the user's preference, and/or the user profile. Instead or in addition, the widgets displayed in the list 300 may be identified based on their popularity among other users registered with the service. The user can select one or more widgets from the displayed widgets from the list 300 to download. When selecting one or more widgets included in the list 300, the content server may add the widgets to one or more sources that the device has established or registered. According to one or more aspects, the selected widget can be synchronized with one or more other widgets that already exist on the user's device and are receiving content through one or more sources. Synchronization may involve the timing of updating the content displayed by the widgets and/or the order in which the widgets are displayed to the user.
 Figure 15 It is a flowchart illustrating a method for determining a list of new widgets or additional widgets for the user or the user's device. In step 1500, the widget service provider may determine that a new widget or additional widget is available for the subscriber's device. For example, the widget service provider can be notified of new widgets from the content source. In another example, the widget service provider may periodically or irregularly search for widgets that have not been downloaded to various devices or user accounts. In step 1505, the widget service provider may formulate one or more widget lists according to the new widget or the parent list of additional widgets to notify the user. In other words, the widget service provider can send a list of new widgets or additional widgets that users may be interested in. The formulation of the list may include selecting widgets from the parent list based on user preferences (such as widgets that the user has downloaded in the past), demographics, and popularity of widgets. In step 1510, the widget service provider may send the list to the user's device. In step 1515, the widget service provider may receive a request for one or more widgets in the list. The widget service provider can then register the widget with the user's account in steps 1520 and 1525, and send the widget to the user's device. In addition, the widget service provider may in step 1530 update or send data to the selected widget to synchronize with one or more other widgets already on the user's device.
 For example in Figure 4a with Figure 4b , The clock widget 405 is selected by the user and added to the user's device. Gizmos may include functions such as changing from a digital clock to an analog reader during user interaction. For example, if the user clicks or selects the clock widget 405 in FIG. 4A, the display of the widget 405 can be changed from the analog in FIG. 4A to the number in FIG. 4B. The clock widget 405 can be implemented using an application protocol interface such as JAVA Mobile Information Device Profile (MIDP). Specifically, the clock widget 405 may be coupled to the JAVA MIDP service running on the user's device when downloading.
 Figure 5a with Figure 5b A series of user interfaces 500 and 501 for displaying widgets such as widget 505 are illustrated. Selection boxes such as boxes 510 and 511 can be used to select widgets in interfaces 500 and 501. When focusing on a specific widget, the frame can be displayed and/or used as the border of the widget. The box can be further colored to distinguish it from the color of the widget. Instead or in addition, the shape and size of the box can also be automatically modified to fit the shape and size of the small control on which the box is focused. in Figure 5a In the middle, the widget 505 is partially separated from the user interface 500 and not in the selection box 510. The device may allow the user to navigate the selection box 510 to an area without widgets to show that the widgets are not currently focused. If the widget is not visible in the user interface 500, the selection box 511 may display the following arrow, which indicates the direction in which the widget can be found. For example in Figure 5b In, the selection box 511 includes the following arrow, which indicates that a small control can be found to the left of the box 511.
 The widget interface may allow the user to choose to send, reload, and/or remove the widget through the user's device. Figure 6a with Figure 6b Two communication systems that can be used to perform widget transfer are illustrated. in Figure 6a If the user wants to share widgets such as widget X 640 with others, such as friends, the user can use the send option on the user's device 660 to send widget X 640 to other people's device 670. When the user selects the sending option, the device 660 may prompt the user to enter the phone number of the destination (ie, the device 670) to which the widget X 640 will be sent. The user can manually enter the phone number into the user's device 660 or instead can access the phone book to identify and select the friend's number. After inputting the phone number and sending the sending request to the server 610, the user can receive a confirmation on the user's device 660 that another party (ie, a friend) sends and/or receives the widget X 640.
Various networking protocols can be used and the request message can be sent through various types of network connections. In addition, a message containing the widget identification information corresponding to the widget X 640 can be sent instead of the widget X 640 itself. Instead or in addition, the message can include a widget X 640. In one example, the embedded TCP/IP stack may be used to send messages from the user's device 660 to the remote server 610 via a GPRS connection. When the server 610 receives the message, the server 610 may check whether the destination phone number sent in the message corresponds to a pre-existing user in the user registration database 620. If the phone number is unknown in the server 610, a new account 630 for the friend to whom the widget X 640 is sent can be created. The server 610 may also identify a widget (such as widget X 640) that is being sent to a friend. The server 610 may then send a message including information such as a user ID and/or password associated with the new account 630 and/or an address where a friend or other user can obtain the widget X 640. For example, a short messaging service (SMS) provided by the SMS aggregator 650 may be used to send a message from the server 610. The server 610 may also send an SMS message that includes download and/or installation information associated with the widget client that can be used to view and/or manage the widget X 640. Therefore, other users or friends can access the server 610 to obtain the widget client and/or widget X 640 when receiving the SMS message. In one or more arrangements, the widgets that are being shared can be included in the client download.
 Instead, if the server 610 identifies the destination friend or other user registered in the registration database 620, then Figure 6b As shown in, the server 610 can send the widget X 640 to the device 670 of the target friend by placing the widget X 640 or associating the widget X 640 with the target user/friend's account (not shown). The account of the target friend can refer to a part of the database of the server 610, where updates and widget information are stored for a specific user. Therefore, when the device 670 of the target friend is updated and/or synchronized with the server 610, the widget X 640 can be downloaded to the device 670. Instead, the target friend or user may be initially notified of the widget X 640 and allowed the target friend or user to decide whether they want the widget X 640. For example, the target user may receive a message that the user 660 wishes to share a new widget in their widget inbox. It is also possible to use short-range messaging to send a message to the device 670 to notify the device 670 of the target user of the new widget. In response to the message, the widget client running on the device 670 can automatically update and/or synchronize with the server 610. Instead, the target user can manually update the widget information and synchronize with the server 610.
 Figure 7 The illustration shows the teletext page that can be broadcast in the vertical blanking interval in the signal sent to the TV. However, according to one or more embodiments, it may also be on a web page (e.g. www.yle.fi/tekstitv ) To access the image and text information part of the TV signal. Generally speaking, different broadcast channels have different content on their pages. For example, CNN text TV may include different content from yle (Finnish radio and television) text TV. Therefore, the user's device can allow the user to view the graphic content provided by various broadcast channels. For example, in the interface 700, a list of available content pages such as weather information on page 101, NHL season information on page 201, and yesterday's results on page 230 may be displayed to the user. In one or more arrangements, the page can be used as a title or content listing page to display the currently available pages and content to the user. You can also classify pages based on one or more attributes such as subject content. So in one example, all entertainment news can be located on the 400 series page, and sports news can be found on the 200 series page.
 The user can access other or additional pages by using the navigation option 710. Options 710 may include next page, last page, next downpage, home page, jump, and channel. In addition to the navigation option 710, the user may, for example, use the keypad or touch-sensitive UI of the device to input a page number to read and display a specified page. The user can, for example, input the channel number 201 to read the content of the NHL season page, for example. The jump option may present the user with a list 715 of existing pages that include content that the user may find interesting or relevant. The list 715 may be generated based on pages that the user has previously visited, user profile information, and/or manual selections made by the user. The list 715 may be constructed as a root index type structure. The user can then select one of the pages listed in the list 715. In response, the content associated with the selected page can be displayed to the user. The next and last page options can allow users to navigate the next and previous pages, while the home page can provide users with direct access to the home page. The next section can be used to navigate to the next story or content section in the series page. For example, a 5-page report about hockey can be followed by a report about stocks. If the user finishes reading page 2 of the hockey report and decides that they want to continue reading the next report (ie, the stock report), they can select the next section option.
 In one or more embodiments, the channel selection option allows the user to view the page based on the channel category. For example, the pages can be grouped according to whether they are associated with channels such as YLE, MTV3, CNN, BBC, and TV4. Therefore, if users prefer one news station to another news station, they can directly access the page associated with the more attractive news station.
 Examples of graphic addresses:
 http://www.yle.fi/cgi-bin/tekstitv/ttv.cgi/html? PAGE=100
 http://www.mtv3.fi/cgi-bin/mtv3tekstikanava get? sivu=200 (Search page 200)
 http://www.mtv3tekstikanava.fi/tekstikanava/automated/200.htm (Page 200)
 The channel information can be configured according to the configuration of the widget client. The script function can be executed based on the channel information (for example, the channel name is MTV3). The logic and algorithms used to process the information and selection of the graphic channel can be stored in the middleware server, which aggregates the selected graphic services (for example, Figure 7 In YLE, MTV3, etc.) and output them to the user device when requested.
 Reference Figure 8 , Illustrates a system for storing and providing web page information to users. The system may include a server 810, a database 880, an obtainer 830, and a web page 890. The database 880 can store the text 885 included in the web page 890 and in turn store links 886 to images associated with the text and/or displayed in the web page 890. They can save space in the database 880 and allow the user to view at least the text while the image can be downloaded or transferred. If the user requests access to the page, the image of the linked page 890 can be retrieved and displayed to the user. In one or more configurations, the fetcher 830 can check the selected web page, such as the page of the web page 890 (for example, in XML format), and if the web page has changed, the fetcher 830 can update with the updated or changed information Server 810. That is, the getter 830 can replace the old content stored in the database 880 with the new content published on the page 890. The acquirer 830 can verify the change of the text and image associated with the web page 890.
 In one or more arrangements, when retrieving data from the web page 890 for storage in the database 880, the fetcher 830 can verify the data source, such as an XML source, and separate the text and the image by adding tags to the text where the image is located. The acquirer 830 can also record the image link to the database 880. The position of the image in the text can be recorded in the text (for example, using tags such as image 1, image 2, image 3 or image links with progressive numbers), so that when the image and text are combined and presented to the user, the image and text are displayed in the text. Their intended location. In one example, in response to a user's request for a web page 890, the server 810 may retrieve text from the database 880 and download an image from the web page 890 using the stored link. When receiving text and images, the server 810 may use tags in the text to combine the text and the image to place the image. Then send and display the combined page to the user. In one or more arrangements, the fetcher 830 can be used to fetch the page from the web page 890. In addition or instead, the information stored in the database 880 can be automatically updated at regular intervals or in response to a user's request. If several download requests are made for the same page (for example, page 890), an agent can be provided to download page data (ie, text and images) for a limited number of times. For example, the agent can download the image associated with the requested page, eliminating the need to download the image multiple times from the page.
 According to one or more embodiments, content can be downloaded and displayed without displaying and/or downloading the images contained therein. If the link (ie image 1 or text link) is selected, then the image can be downloaded and displayed on the user interface in such an embodiment. The user can also be given the option to download images automatically or download images only when requested or approved. This allows devices and users to save bandwidth and potentially save costs related to data transmission. Likewise, such an option may be a "download/show image" option.
 Figure 9a The rich site summary (RSS) widget 905 displayed in the user interface 901 of the device is illustrated. The widget 905 may include symbols or indicators to indicate that the new source is available. For example, if a new source is available, widget 905 may include indicator 910 such as the symbol'+'. The symbol can be ‘+’ or any other character, image, text, etc. In addition, the notification of new content or additional content (for example, source information) may include images, audio, video, tactile feedback, and the like. When the user selects or clicks the widget 905 and/or the indicator 910, the widget client (not shown) of the device and the server (for example, Figure 8 Server 810) and with the database such as Figure 8 The information stored in the database 880 is synchronized to retrieve the new source information. The server or client can also use a timestamp to identify when the last update occurred. Use timestamps to limit downloads to new content or updated content (from timestamps). The server can also enforce other restrictions, such as only downloading the information of the day, in order to limit the download bandwidth. According to one or more embodiments, when the user selects a web page or other content, the user may initially only receive Figure 9b Title 920 of the downloadable object in the source shown in. When the user requests more information (such as the full text of the article), the server can provide such as Figure 9c The text 925 and one or more images 930 shown in. When multiple images are linked in text, the image and text can be parsed and presented according to the order in which the text and image are recorded by the getter.
 Figure 10-Figure 14 Illustrated are communication devices that display user interfaces for viewing, accessing, and managing widgets, widget clients, and various aspects thereof. For example in Picture 10 , The user can access various options by selecting the option button 1005. When the option button 1005 is selected, a menu 1010 may be displayed, which includes an option for accessing the widget (ie, option 1015), an option for accessing the widget client (ie, option 1020), and an exit option (ie, option 1025). Various small controls can be displayed in the background 1030. The scroll arrow 1035 can be used to browse various small controls available on the device.
In one or more embodiments, a widget client option 1020 to create, modify, and/or customize widgets can be selected. For example, users can specify colors, shapes, sizes, and images that are applicable to widgets. The user can also specify the specific source and content to be downloaded through the widget. Picture 11 Illustrated is a customization interface 1100 for customizing widget properties. For example, you can select or specify the alarm tone and volume settings used to alert the user when new content is received. The alarm can be specified through the input field 1110 and the volume can be specified in the field 1115. The field 1110 and the field 1115 may be a drop-down menu, a text input field, a radio button selection list, and the like. A search tag can be specified for the content and in the tag field 1120, so that an alert is given if the content matches the specified search tag. When customizing widgets, users can be given options to test alarms. This can include testing the selected sound as well as the specified volume. Scroll option 1125 can be used to access additional options that are not currently in the display screen (ie, customize the overflow portion of the screen).
 Figure 12-14 Illustrated is a series of interfaces in which a symbol 1210 is used on the user interface 1200 to indicate new content for a widget (for example, widget 1205). Symbols can include various characters, words and/or images, including a ‘+’ sign, the word "more..." and/or an arrow image. For example, when you click or select the widget 1205 or the symbol 1210 associated with it in another way, you can: Figure 13 The content shown in the interface 1300 is displayed. The option bar 1310 provides various options including an option menu 1315, a return option 1320, and a scroll control 1305. If the content of the widget (such as widget 1205) cannot fit on one screen, the scroll control 1305 can be displayed. Even if the document does not fit, the scroll control 1305 still allows the user to scroll through the entire document. Figure 14 The interface 1400 with additional content after scrolling the content is illustrated.
 Figure 16 It is a flowchart illustrating a method for receiving new content information or additional information through a widget. In step 1600, the communication device may receive a notification of new information content or additional information (for example, a new information source) corresponding to the widget. You can receive notifications as part of regular or irregular synchronization/updates with the widget service provider. Instead, the user can order the communication device to check for updates. In step 1605, the new content information or additional information may be downloaded by a widget running on the communication device. Once downloaded, the communication device can display a widget with an indicator that indicates that new information is available for the widget in step 1610. Indicators can include symbols, text, images, and so on. In an example, the symbol may include a'+' sign. In step 1615, the communication device may receive an input corresponding to an interaction with the indicator. In response, the communication device may display new information or additional information in step 1620. If the new information or additional information is too large for one screen, the communication device may also include one or more scroll controls for viewing all content.
 Figure 17 It is a flowchart illustrating a method for filtering and sending information to a communication device. For example, in step 1700, the service provider may receive new content (for example, a new information source) for the widget. In step 1705, the service provider may identify one or more accounts that have downloaded or are using the widget. The service provider can keep track of which widgets have been downloaded to which account/device through the user account database, etc. In step 1710, the service provider may determine account preferences for receiving content. Account preferences can include whether to include images, the type of information to be sent, restrictions on content size, support for videos, and so on. In step 1715, the service provider may filter new content for sending to devices associated with the identified one or more accounts according to the determined account preferences. Filtering can be, for example, stripping image content and replacing images with image links and replacing videos with video links. This can help some devices reduce the amount of bandwidth (and in some cases the cost) associated with receiving new content. Filtering may also include determining whether the content type or category is within the user's expectation or preferred category, and in some cases removing parts of the content that do not satisfy the user's preference. In step 1720, the filtered content may then be sent to the user's device.
 Describing an embodiment of the invention Figure 18 It is a block diagram of a communication device that includes a processor 1828 connected to a user interface 1830, a memory 1834 and/or other storage, and a display 1836. The communication device 1812 may also include a battery 1850, one or more speakers 1853, and an antenna 1854. The user interface 1830 may also include a keypad, a touch screen, a voice interface, one or more arrow keys, a joystick, a data glove, a mouse, a rolling ball, a touch screen, and the like. The mobile terminal 1812 may include a computer, a PDA, a mobile phone, and so on.
 Computer-executable instructions and data used by the processor 1828 and other components in the communication device 1812 may be stored in the computer-readable memory 1834. The memory can be implemented with any combination of read-only memory modules or random access memory modules (optionally including volatile and non-volatile memories). The software 1840 may be stored in the memory 1834 and/or storage to provide instructions to the processor 1828 to enable the communication device 1812 to perform various functions. Instead, some or all of the computer-executable instructions of the communication device 1812 may be implemented in hardware or firmware (not shown).
 The communication device 1812 may be configured to receive, decode, and process, for example, digital radio or television broadcast transmission based on the DVB standard through a specific DVB (Digital Video Broadcasting) receiver 1841. Mobile devices can also be used for digital broadcast transmission such as MediaFLO, DMB (Digital Multimedia Broadcasting), ISDB (Integrated Services Digital Broadcasting), HDTV (High Definition Television), DAM (Digital Audio Broadcasting), DRM (Digital Radio Broadcasting), etc. Other types of receivers. In addition, the communication device 1812 may also be configured to receive, decode, and process transmission through the FM/AM radio receiver 1842, the WLAN transceiver 1843, and the wireless communication transceiver 1844. The transceivers 1843 and 1844 may instead be separated into separate transmitter and receiver components (not shown). In one example, the transceiver 1844 may include a broadcast receiver (not shown) and a reverse channel receiver (not shown) for communicating through a broadcast channel and a reverse channel, respectively. In one aspect of the invention, the communication device 1812 may receive radio data system (RDS) messages. Other sending and receiving systems can also be used, these systems include WiMAX (Worldwide Interoperability for Microwave Access), the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard and/or UWB (Ultra Wide Band) transceiver. In one or more examples, signals can be sent to and received from another mobile terminal (not shown). For example, various transmission protocols such as wireless local area network (WLAN), general packet radio service (GPRS), third-generation mobile system technology (3G), Bluetooth and/or universal plug and play (UPnP) can be used in two communication devices Send audio, video and other signals between. Such networks can be used to access or support local networks or remote networks such as the Internet.
 Figure 19 Is a block diagram of a server according to one or more aspects described here. The server 1900 includes various components, including a widget database 1905, a user account database 1910, a processor 1915, a network interface 1920, a recommendation generation component 1925, and a filter module 1930. The functions performed by the server 1900 may be at least partially processed by the processor 1915. The widget database 1905 can store widgets and/or information associated with them. For example, the widget database 1905 may store the widget itself or the address or location used to access the widget, or both. On the other hand, the account database 1910 stores information related to users, their devices, and/or activities of users or devices. For example, the database 1910 may store widget download history for each user account and/or store the limitations or capabilities of the user equipment.
 In addition, the network interface 1920 can facilitate communication to and from the server 1900. The network interface 1920 can coordinate communications from multiple transmitters and to multiple receivers. For example, a content source can send information updates through interface 1920, which can then be used to send information updates to one or more devices. The recommendation generating component 1925 may be configured to formulate a list of recommended widgets for a given user or device according to the methods and aspects described herein. On the other hand, the filter module 1930 may be configured to filter content before sending to the receiving device as discussed herein. The components of the server 1900 may include firmware, software, hardware, and/or a combination thereof. Various other components may also be used in combination with or in place of the components. In addition, the server 1900 may be a distributed computing system in which components are dispersed in multiple locations. Instead, the server 1900 may be a single integrated unit.
 The methods and features described herein can also be implemented by any number of computer readable media capable of storing computer readable instructions. Examples of computer readable media that can be used include RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, DVD or other optical disk storage, cassette tape, magnetic tape, magnetic storage, and the like.
 In addition or instead, in at least some embodiments, the methods and features described herein may be implemented by one or more integrated circuits (ICs). The integrated circuit may be, for example, a microprocessor that accesses programming instructions and/or other data stored in a read-only memory (ROM). In some such embodiments, the ROM stores programming instructions that cause the IC to perform operations according to one or more of the methods described herein. In at least some other embodiments, one or more of the methods described herein are hardwired into the IC. In other words, the IC in this case is an application specific integrated circuit (ASIC) with gates and other logic dedicated to the calculations and other operations described herein. In more other embodiments, the IC may perform some operations based on the execution of programming instructions read from ROM and/or RAM while other operations are hard-wired into the gates and other logic of the IC. In addition, the IC can output image data to the display buffer.
 The present invention includes any novel feature or combination of features explicitly disclosed herein or any summary thereof. Although the present invention has been described with reference to specific examples including currently preferred embodiments for implementing the present invention, those skilled in the art will recognize that there are many variations and permutations of the above-mentioned systems and techniques. Therefore, the spirit and scope of the present invention should be understood broadly as set forth in the appended claims.
Description & Claims & Application Information
We can also present the details of the Description, Claims and Application information to help users get a comprehensive understanding of the technical details of the patent, such as background art, summary of invention, brief description of drawings, description of embodiments, and other original content. On the other hand, users can also determine the specific scope of protection of the technology through the list of claims; as well as understand the changes in the life cycle of the technology with the presentation of the patent timeline. Login to view more.