Method and system for transferring content from the web to mobile devices

[0001] This application is a continuation-in-part of U.S. patent application Ser. No. 11/674,081 filed Feb. 12, 2007 and entitled “Method and System for a Hosted Mobile Management Service Architecture” which is hereby incorporated by reference.

[0002] The present invention relates generally to an architecture for “mobilizing” web content and, more specifically, techniques for moving multimedia content from the web onto one's mobile device while browsing the web.

[0003] Current solutions for transferring content from the web to a cell phone while browsing the web focus on extending the capabilities of currently existing web browsers through plug-in technologies or by requiring web sites to edit the source code of their web pages. In one current solution, depicted in FIG. 1, a web browser plug-in is downloaded and installed into a user's web browser. The user can then activate a console window 105 on the left side of the browser and drag and drop picture files on a visited web page into a staging area 110 in the console window. Once a file has been dragged into the staging area 110, the user can instruct the plug-in to transmit the file to the user's cell phone by pressing the “Send” button 115. The plug-in then utilizes one of several known delivery mechanisms as selected by the user (i.e., WAP Push, MMS Notification, SMS or MMS) to send a message to the user's cell phone. Once the message arrives at the user's phone, the user can view the message on the phone, retrieve the file (e.g., via a WAP page) and view and/or save it to his cell phone.

[0004] A similar solution is depicted in FIG. 2. A web browser plug-in is also downloaded and installed in the solution of FIG. 2; however, this plug-in provides a menu option 205 rather than a console window as provided in FIG. 1. When a user visits a web page and right-clicks his mouse on an image, the context menu 210 appears with the menu option 205 to send the image to the phone. If the user selects menu option 205, a new web page 215 originating from the solution's own web server appears and requests the user to enter his cell phone number 220. Once the user enters his cell phone number, he can press the “Send” button 225 which causes an SMS message to be sent from to the user's cell phone. The SMS message contains a link to a WAP page where the image can be viewed and/or saved to the cell phone.

[0005] An alternative solution is depicted in FIG. 3 which provides web sites a method to enable visitors to send photos from the web site to their cell phones. By embedding a small segment of JavaScript code 305 into the pages of the web site, the web site enables visitors to Alt-Click 310 on an image embedded in a web page to transfer a copy of the photo to the visitors' cell phone. Upon performing an Alt-Click on an image, a new web page 315 originating from the solution's own servers appears and requests the visitor to enter his cell phone number 320. Once the visitor enters his cell phone number, he can press the “Send SMS” link 325 which causes an SMS message to be sent to the user's cell phone. Similar to FIGS. 1 and 2, the SMS message contains a link to a WAP page where the image can be viewed and/or saved to the cell phone.

[0006] While the foregoing solutions provide a simple and easy method for web visitors to move multimedia content from the web to their phones, they have certain limitations that make them more difficult to achieve widespread adoption. For example, plug-in solutions similar to those depicted in FIG. 1 and FIG. 2 utilize a cumbersome download and installation process that often requires the closing of all web browsers and the rebooting of the user's personal computer. Because different web browsers such as Internet Explorer and Firefox offer different APIs, different plug-ins are needed to support different web browsers thereby increasing development and maintenance costs. Furthermore, the plug-ins themselves may need to be upgraded (i.e., subsequent downloads and installations) in order to extend and enhance the offered services. Embedded JavaScript solutions similar to FIG. 3 eliminate the disadvantages of the plug-in solutions, but remain cumbersome because they require web sites to edit the source code of their web pages. What is needed is a hosted solution that provides the user conveniences of plug-in solutions without the cumbersome installation processes or upgrade issues and without the requirement of requesting each web site to incorporate code into their own web pages to enable such functionality.

[0007] The present invention provides a method and system for embedding a web browser into a web page in order to transfer content residing on web pages rendered in such an embedded web browser to mobile devices through drag and drop functionality. In particular, an inline frame is embedded into the web page and renders third party web pages. Client side code (such as JavaScript) implements a drag and drop functionality on the web content rendered in the inline frame to provide a user the capability to drag content rendered in the inline frame into a staging area to ultimately be transferred the user's cell phone. In order to achieve such drag and drop functionality, web pages rendered in the inline frame are proxied through the web server serving the web page containing the inline frame. Because the act of dragging and dropping content rendered in the inline frame into the staging area occurs within a single web page architecture, the present invention eliminates the need for a plug-in. Once content is dragged into the staging area, an SMS message (or other known mobile delivery mechanism) may then be transmitted to the cell phone of the user wherein such SMS message contains a link to a dynamically generated WAP page that contains links to various content selected by the user.

[0008] More generally, a method is disclosed for enabling a user to drag and drop multimedia content from web pages into a mobile device. Performed at the web server, such a method comprises the steps of (a) serving a web page to the web browser wherein the web page comprises code for (i) an inline frame for rendering web pages, (ii) a receiving panel to receive dragged content rendered in the inline frame, (iii) a click handler for directing user clicks in the inline frame to the web server, and (iv) a drag and drop handler for enabling content in the inline frame to be dragged into the receiving panel, (b) receiving from the web browser a web page request containing a URL for a third party web page, (c) transmitting an HTTP request for the URL to the web site of the URL, (d) receiving from the web site of the URL an HTTP response containing HTML code payload for the third party web page, (e) generating a response containing the HTML code payload of the HTTP response; and (f) transmitting the response to the web browser in response to the web page request.

[0009] When the user drags multimedia content into the receiving panel, in one embodiment of the present invention, the web server then receives from the web browser a URL for such multimedia content rendered in the inline frame, retrieves the multimedia file associated with the URL from the web site of the URL, and associates the retrieved file with a group identifier. The group identifier may be used by the web server to identify that content which has been dragged into the receiving panel by the user during a particular web browsing session. When the user desires to transmit the dragged content to his mobile device, he clicks on a “Send” button on the web page and the web server receives a request from the web browser to transmit the multimedia content associated with the group identifier to the user's mobile device and in turn transmits an SMS message to the mobile device that includes a link (e.g., a URL) containing an address of the web server (e.g., the domain name) and the group identifier. When the user receives the SMS message and selects the link in the SMS message, the web server receives a request from the mobile device for the link, dynamically generates HTML code including a hypertext reference for the retrieved file (and any other hypertext references for other retrieved files associated with the group identifier) to download, and transmits the HTML code back to the mobile device for rendering in the mobile device's WAP browser. The HTML code may either render the multimedia content on the mobile device's WAP browser or contain links to fetch such content.

[0010] Similarly, a corresponding system is disclosed herein for enabling a user to drag and drop multimedia content from web pages into a mobile device. The system comprises (a) a web page configured to (i) embed other web pages into an inline frame, (ii) enable a user to drag and drop multimedia content from the inline frame into a receiving panel, and (iii) enable a user to request that dragged multimedia content be transmitted to the user's cell phone, and (b) a web server component configured to (i) serve the web page to a web browser, (ii) receive web page requests for third party web pages from a web browser rendering the web page, (iii) generate HTTP requests to fetch the third party web pages, and (iv) embed HTML code into responses to the web page requests, wherein the HTML code is received in HTTP responses received from third party web servers serving the third party web pages.

A. Web Page Architecture

[0023] FIG. 4 depicts one exemplary embodiment of a web page 405 user interface in accordance with the present invention. A user navigates to a web site by entering the URL into the address text field 410 of the web browser and logs into an account by providing his username and password. The user's account is established through a prior enrollment process whereby the user provided information including, for example, his cell phone number, cell phone manufacturer and model and carrier. Upon successful login, the user is presented with a set of tab panels, including a “Web” panel 415. Selection of Web panel 415 presents the user with a web browser like interface that includes a URL text field 420, a web browser toolbar 425 and an inline frame 430 for embedding other web pages from other sites into web page 405. When the user types a URL for a web site or web page into the URL text field 420, the web site or web page is retrieved and displayed in inline frame 430. Adjacent to Web panel 415 is a receiving panel that contains a drag and drop panel 435 into in which the user is able to drag and drop multimedia content (e.g., picture, video and audio files, etc.) that is displayed in the web page embedded in inline frame 430. The receiving panel also contains a staging panel 440 below the drag and drop panel 435 where a visual representation of various multimedia files that have been dragged into the drag and drop panel 435 during a session can be kept track of. As used herein, the term “receiving panel” may be considered to be the combination of the drag and drop panel 435 and the staging panel 440 or each such panel individually, as the context requires). Above the drag and drop panel 435 is a submission panel 445 with a “Send” button 450 to initiate a transfer of the files dragged into the staging panel 440 to the user's cell phone. Those with ordinary skill in the art will recognize that that FIG. 4 is merely exemplary of numerous ways to provide a web user interface for embedding a web browser within a web page that remain consistent with the spirit and scope of the present invention. For example, rather than presenting a drag and drop panel 435 into which multimedia content is dragged into and visualized in staging panel 440, an alternative user interface may utilize a tree structure panel with folder nodes including a “My Phone” node wherein the user can drag multimedia content into such folders before pressing the “Send” button 450 to initiate transfer.

[0024] FIG. 5 depicts one embodiment of a network architecture supporting a web page user interface similar to that of FIG. 4 in accordance with the present invention. Web server 505 (for example, an Apache Tomcat server) serves web page 405 to the user when the user logs into his account using an Internet connected terminal with a web browser such as 510 (e.g., laptop, personal computer, etc.). As further discussed below, web servers 515 that serve the actual web pages rendered in inline frame 430 are proxied through web server 505 as a result of interaction between client side JavaScript code implemented in web page 405 for Web panel 415, a filter 520 listening to all HTTP requests received at web server 505, and a proxy servlet 525 that handles communication between web servers 515 and the web server 505. Specifically, because of certain security limitations of inline frames, the DOM, or Document Object Model, of the web pages that are rendered in inline frame 430 cannot be programmatically accessed when those web pages are not received through web server 505, which serves the web page 405 to the web browser, itself. As such, without the proxy services of web server 505, hypertext references for multimedia content such as picture, video and audio files present in the HTML source code for any web page rendered in inline frame 430 cannot be readily obtained and parsed by client side JavaScript code in order to implement the drag and drop capability described in conjunction with FIG. 4. In order to create the user experience described in FIG. 4, web server 505 that serves web page 405 to the user's web browser also serves as a proxy web server (via proxy servlet 525) through which all HTTP requests that are either entered by the user into URL text field 420 or selected by the user as a hypertext reference in a web page in inline frame 420 are proxied. Because all web page HTTP requests are proxied through web server 505, client side JavaScript code is then able to access the DOM of the web pages rendered in inline frame 430 and therefore implement the drag and drop capability by accessing the hyperlink references associated with the pictures, audio and video and other multimedia content present in the rendered web pages. Those with ordinary skill in the art will recognize that although FIG. 5 and other portions of the exemplary embodiments discussed herein utilize servlets and JavaScript code as the underlying web technologies used to implement aspects of the present invention, many other alternative and substantially equivalent technologies may be utilized without departing from the spirit and scope of the invention. For example, rather than utilizing Java servlet technology, alternative non-Java dynamic Web content technologies such as PHP, CGI and ASP.NET may be used in other embodiments. Similarly and without limitation, rather than utilizing JavaScript code to implement functionality on the client side, JScript, JScript.NET, VBScript, ActionScript and other implementations of the ECMAScript standard may be used in other embodiments.

[0025] In an exemplary embodiment of web page 405, client side JavaScript code may be utilized to implement a rich user interactive experience such as, but not limited to, the drag and drop functionality from the web pages rendered in the inline frame 430 into the drag and drop panel 435. As detailed in FIG. 6, when the user inputs a URL address of a new web page into the URL text field 420 of Web panel 415 (Step 600), client side JavaScript code instructs the web browser to submit an HTTP POST message to the domain name (e.g., www.oomble.com) of web server 505 (Step 605). The HTTP POST message contains two name-value data parameters to indicate to web server 505 that the HTTP POST request is originating from Web panel 415 of web page 405. For example, if the user entered “www.espn.com” into URL text field 420, the JavaScript code would transmit an HTTP POST request to the domain name (www.oomble.com) of web server 505 including the data parameters: “serviceProxy=true&targetHost=www.espn.com”. The filter 520 at web server 505 receives the HTTP POST request from the web browser and because serviceProxy=true, the filter 520 passes the HTTP POST request to proxy servlet 525 (Step 610). Those with ordinary skill in the art will also recognize that the request sent to the proxy server 505 may take one of several forms alternative to the HTTP POST request, such as an HTTP GET with data parameters appended to the URL in the normal fashion. Upon receiving the HTTP POST request, web server 505 may then allocate a session identifier to the HTTP POST request (e.g., directing the web browser to set a cookie with the session identifier in the subsequent HTTP Response transmitted later in Step 645) in order to maintain state for tracking the user's browsing session with web server 505. Proxy servlet 525 then saves www.espn.com as the true web server that the session identifier is associated with (Step 615) Proxy servlet 525 then takes the targetHost value, www.espn.com, and generates and transmits an HTTP GET request for www.espn.com (Step 620). Once proxy servlet 525 receives ESPN's HTTP Response containing the HTML code for its home page (Steps 625 and 630) in response to the HTTP GET request, it extracts the HTML code from ESPN's HTTP Response (Step 635) and generates its own HTTP Response for the web browser's original HTTP POST request and embeds the ESPN's HTML code as payload in such an HTTP Response (Step 640). Proxy server 525 then transmits the generated HTTP Response to the web browser which then renders ESPN's HTML code in inline frame 430 (Steps 645 to 655). Any file source attributes for HTML tags (e.g., src attributes for img or script tags) in the HTML code are either directly fetched if the src URL is absolute (i.e., shows the entire path to the file, including the scheme, server name, the complete path and the file name itself) or, if the src URL is relative (i.e., describes the location of the desired file with reference to the location of the file that contains the URL itself), fetched through proxy server 505 in a manner similar to resolving relative hypertext references or links as further detailed in conjunction with FIG. 7. By positioning proxy web server 505 in between the web browser and a server 515 that serves the actual HTML content, from the perspective of the web browser, the contents of inline frame 430 originate from proxy server 505 rather than the true server 515 thereby enabling client side JavaScript code to access the elements of the DOM of inline frame 430 and implement the drag and drop functionality described in FIG. 4.

[0026] As detailed in FIG. 7, when a user desires to navigate the web through Web panel 415 by clicking on web page links in inline frame 430 (Step 700), new web pages that load into inline frame 430 through navigation should be able to be dragged and dropped into the drag and drop panel 435. To maintain such drag and drop functionality, the proxy web server 505 should continue to proxy communications between the user's web browser and web servers 515. To achieve this, a click handler written in client side JavaScript code monitors the user's clicks on hypertext references or links in inline frame 430 (Step 705). When the click handler receives a click action for a link that is a relative URL, the click handler is able to pass the HTTP request related to the click action directly to proxy server 505 (i.e., from the perspective of the user's web browser, the web page rendered in inline frame 430 was served by proxy server 505 rather than its true origin, web server 515) (Step 710). The HTTP request may also include the cookie that contains the session identifier set by the proxy server 505 in Step 615 of FIG. 6. Upon receiving the HTTP request, filter 520 passes the request to proxy servlet 525 (Step 720). Proxy servlet 525 is able to extract the session identifier from a session identifier cookie in the HTTP request (Step 725) and obtain the true web server address for which the HTTP request is intended (i.e., the true web server address was associated with the session identifier in Step 615) (Step 730). Proxy servlet 525 then generates its own HTTP request (Step 740), directing the HTTP request to true web server 515 and receives the HTTP Response (Steps 750 and 755). When it receives the HTTP Response from the true web server 515, it generates a new HTTP Response with the HTML code payload and transmits it to the waiting web browser (Steps 760 to 780). When the click handler encounters a link that is an absolute URL, the click handler utilizes a process similar to that described in FIG. 6 by generating an HTTP POST request to proxy server 505 with the data values serviceproxy equal to true and targetHost equal to the absolute URL (Step 715). Once the HTTP POST request is received by the filter 520 and forwarded to the proxy servlet 525, the web server identity that is associated with the session identifier (as set in Step 615) is updated to be the server name in the absolute URL (Step 735). An HTTP GET request is then generated by proxy servlet 525 containing the absolute URL. The process then continues onward through Step 750 in a manner similar to dealing with a relative URL.

[0027] When a user drags a picture or other multimedia content rendered in the web page of inline frame 430 into the drag and drop panel 435, client side JavaScript code obtains the source URL of the dragged content and transmits it to proxy server 505 which stores it in a queue. If the source URL is relative rather than absolute, client side JavaScript code converts the relative URL into an absolute URL by extracting and adding the server name from the URL displayed in the URL text field 420 to the path of the relative URL. Once the user has completed his session, he clicks on the “Send” button 450 which instructs the server 505 to initiate a delivery mechanism to the user's phone. Those with ordinary skill in the art will recognize that certain programmatic choices as described herein in conjunction with FIGS. 6 and 7 can be substituted with substantially equivalent alternatives. For example, alternative embodiments may not utilize HTTP requests and responses for Steps 605 and 645 but rather an alternative and possibly proprietary TCP/IP request and response protocol for the HTML contents for the URL in URL text field 420. Similarly, alternative embodiments may not utilize the same number or types of data parameters as those utilized in the HTTP POST message of Step 610 or Step 715. Rather than using cookie technology to maintain state (i.e., session identifiers), alternative embodiments may also utilize other state maintaining technologies such as methods include server side sessions, hidden variables, and URL encoded parameters. Similarly, alternative embodiments may use alternative HTTP requests (e.g., GET as opposed to POST, POST as opposed to GET, etc.) than those used in FIG. 6 or 7 and achieve the same results.

B. Delivery Architecture

[0028] FIG. 8 sets forth one exemplary embodiment of an architecture for delivery of the user's selected web content to his mobile cellular device such as cell phone 820. An underlying digital cellular wireless network system 815 in this environment may be a 3.5G network such as HSDPA/UMTS (High Speed Downlink Packet Access/Universal Mobile Telephone System). Other possible digital cellular wireless network systems would include, without limitation, all other forms of 2.5G (e.g., GPRS, EDGE, etc.), 3G (e.g., TD-SCDMA, CDMA2000, etc.), 3.5G and future generations of packet-switched cellular wireless technologies. Because the underlying digital cellular wireless network system 815 supports packet-switching capabilities, it is able to implement an IP-based network that supports TCP/IP based communications by cell phone 820. Additionally, the digital cellular wireless network system 815 also supports text messaging services such as SMS 810. The digital cellular wireless network system 815 may also provide cell phone 820 access to the Internet through its IP-based network capabilities. By obtaining an IP address from the underlying digital wireless network system 815, cell phone 820 is able to communicate through the digital cellular wireless network system 815 through the Internet and ultimately to a server 505. In addition to communicating with cell phone 820, server 505 may also be coupled to an SMS gateway 805 in order to send SMS messages to cell phone 820. As used hereinafter, the term and reference number “server 505,” may be used generally to refer to the server side capabilities (as opposed to the client side capabilities) and therefore may include functionality resident in the SMS gateway 805 as the context requires.

[0029] FIG. 9 details one exemplary embodiment of a delivery mechanism in accordance with the present invention. In such a delivery mechanism, once the user clicks on the “Send” button 450 (Step 900), the queued source URLs of all dragged content in staging area 440 are fetched by server 505, saved locally in the user's account and assigned a group identifier (Step 905). Server 505 (via SMS gateway 805) then delivers an SMS message to the user's cell phone 820 containing a URL back to the server 505 (Step 910). For example, if the domain name of server 505 is www.oomble.com, the URL in the SMS message may be: http://www.oomble.com/itemList.mob?id=12345 in which 12345 is the group identifier for the dragged content and itemList.mob is a handle to a servlet 530 at server 505 that handles a request from cell phone 820 for the URL. When the user selects the URL in the SMS message (Step 915), the WAP browser on his cell phone 820 transmits an HTTP GET request to server 505 for the URL (Step 920). Server 505 forwards the HTTP request to the itemList.mob servlet 530 (Step 925) which then identifies the locally saved content files associated with the group identifier 12345 and dynamically generates a simple web page containing URL links to the locally saved content associated with the group identifier. The HTML code for the web page is then packaged into a HTTP Response by server 505 and transmitted back to the WAP browser of the cell phone 820 (Step 930) which then renders the web page on the WAP browser of the cell phone (Step 935). When the user selects a link to dragged content from the web page (Step 940), an HTTP request is transmitted to server 505 which delivers the content to the cell phone's WAP browser to be viewed (Steps 945 to 960). FIG. 10 depicts an exemplary embodiment of the various user interfaces on the user's cell phone 820 during the delivery mechanism of FIG. 9. In one exemplary embodiment, the SMS message of Step 910 may be similar to 1000, the web page generated in Step 930 may be similar to 1005 and the rendering of content in Step 960 may be similar to 1010. Those with ordinary skill in the art will recognize that the URL path examples presented in conjunction with FIG. 9 are merely exemplary and that path names and servlet names (e.g., itemList.mob) may vary in accordance with an implementer's programmatic design decisions. Similarly, those with ordinary skill in the art will recognize that certain programmatic choices as depicted in FIGS. 9 and 10 may be altered without changing the spirit and scope of the present invention. In an alternative embodiment, rather than SMS messaging, similar technologies such as WAP Push, MMS Notification, or MMS may be used instead. In an alternative embodiment, multimedia content may not necessarily be locally saved by server 505 as in Step 905. Instead, the links to the content generated in Step 930 could be links directly to the content as stored at its original web server 515. The SMS messaging and WAP browser interaction with the user's cell phone can also be altered without departing from the spirit of the invention. For example, rather than sending the a link to a WAP page containing links to the content in the SMS message as in 1000, the links to content may be sent directly in the SMS message itself. Similarly, rather than providing text links to image content in the a WAP web page such as in 1005, the actual images themselves may be embedded and rendered in the WAP web page itself. Those with ordinary skill in the art will also recognize that additional features and enhancements may be added to a delivery mechanism in accordance with the present invention with departing from the spirit of the present invention. For example, server 505 may perform conversion or data manipulation processes on multimedia content to be transferred to a user's cell phone in order to customize such content to be viewed on the particular make and model of the user's cell phone. For example, photos may be cropped or resized to better fit the screen of the cell phone and audio files may be re-sampled or compressed to minimize network transfer time to the cell phone.

[0030] An alternative exemplary embodiment in accordance with the present invention utilizes a thin client application this is installed on the user's cell phone 820 similar to the thin client application 235 described in U.S. patent application Ser. No. 11/674,081 filed Feb. 12, 2007, entitled “Method and System for a Hosted Mobile Management Service Architecture” (hereinafter “Parent Application”) which is hereby incorporated by reference. In such an embodiment, when the user clicks on the “Send” button, the queued source URLs of all dragged content in staging area 440 are fetched by server 505 and transmitted to the cell phone 820. Specifically, as further detailed in the Parent Application, the thin client application receives communications from server 505 through the cellular network and interacts with the cell phone's file system. Depending upon the user's cell phone model and carrier, server 505 transmits to the thin client application the correct sequence of “primitives” or file system operations that enables the thin client application to store the dragged content in the correct location in the file system of the cell phone 820 to be consumed by the phone's native applications. In particular, when the user completes a web navigation session using inline frame 430, having dragged certain content from the web into the staging area 440, server 505 pushes all new additions of content made by the user to the cell phone. By transmitting an SMS push message to the push registry of the cell phone 820, server 505 activates the thin client application which then initiates communication back to server 505 to receive and perform all the changes to content on the cell phone 820 made by the user when navigating the web in inline frame 430. Once the thin client completes its activities, the user is able to access the native applications of the cell phone in order to view new photos, listen to new songs, or watch new videos transferred onto the cell phone from the web pages in inline frame 430.

C. Traditional Web Page and Fee Generation Enhancements

[0031] In addition to providing the capability for users to navigate the web through an inline frame 430 in a single web page 405 hosted by server 505 (e.g., www.oomble.com) and drag content into their cell phones, the present invention may also support the capability for users to navigate the web through traditional web browsers (e.g., Internet Explorer, Firefox, Safari, etc.) and drag content onto the phone after navigating through such traditional means. Web sites can place a small link, button or “widget” in the footer, header or other area of their web pages which when clicked will lead to web page 405 and automatically populate URL text field 420 with the address of the visited web page. In particular, JavaScript code can be provided to such websites such that when a user clicks on such a link, button or widget in a particular web page, the URL of the web page is extracted from the web browser and transmitted to server 505. For example, if a user is currently visiting the web page http://sports.espn.go.com/nba/index at the ESPN web site and clicks on such a link, button or widget in the web page, client side JavaScript code extracts the URL and inserts it into an HTTP GET request that is transmitted to server 505 such as http://oomble.com/oomble-site/oomblize.do?referer=http://sports.espn.go.com/nba/index). When server 505 receives the HTTP GET request, a servlet for oomblize.do may extract a user identifying cookie from the HTTP GET request and if the user has enabled auto-login features on his account, the servlet may redirect the request to a web page with Web panel 415 displayed and http://sports.espn.go.com/nba/index populated the URL in URL text field 420 and displayed in inline frame 430. From that point, the user will be able to drag content from the ESPN web page into his cell phone as previously taught herein. If the auto-login feature has not been enabled, the servlet will redirect the request to the login page and, if login is successful, to the Web panel 415 page.

[0032] In an exemplary embodiment, a revenue generation system may be built on top of the service described herein for transferring content from the web to user's cell phone. For example, third party web sites and/or content providers can choose to charge a fee for each item of content originating from their site (or owned by the content owner) that a user drags from the web to his cell phone through use of server 505. An automated fee management platform may be offered by server 505 that allows third party web sites and/or content owners to customize the amount of such fees and/or the particular content on the web sites that are to be assessed such a fee. In one embodiment, such an automated fee management platform is offered through the web such that third party web sites and content owners may log onto their accounts on the web and customize their profile with the desired fee structure (e.g., $1.00 charged for any photo dragged from the web site into the user's cell phone). Such profiles may be stored in a database coupled to server 505 such that when a user then visits the web site through inline frame 430 (or by clicking a widget in the web site as described herein) and drags a photo from the web site into his cell phone, server 505 can extract the fee structure profile from the database and assess the appropriate fee to the user for the transfer of such content to his cell phone. Additionally, such a fee management platform may also be used to enable third party web sites and/or content providers who do not desire their content to be dragged into user cell phones through server 505 to set their profile as such. In such a situation, server 505 shall prevent such content from being dragged onto users' cell phones.

D. Messaging and Sharing Enhancements

[0033] In addition to providing the capability to drag contents from the web into a user's cell, the present invention may also provide the capability to keep track of such transfers from the web to the user's cell phone. As detailed in FIG. 11, in one exemplary embodiment utilizing SMS messaging (FIG. 9) as the delivery mechanism, a “Messages” tab panel 1105 may be available in web page 405. The contents of the Messages panel 1105 may be similar in layout to a standard email system layout. The main messages panel 1110 maintains a historical list of SMS messages sent by the user using server 505 to his cell phone 820. Selection of any particular entry in the main messages panel causes the message preview panel 1115 to display those items of content that were dragged by the user into the drag panel 440 and sent to the user's cell phone 820. The user is also able to organize the various SMS messages sent to his cell phone in folders 1120 in the explorer panel 1125. Utilizing the toolbar 1130, a user can also forward such SMS messages to friends in his contact list 1135 or by entering such friends cell phone numbers.

[0034] Similarly, FIG. 12 depicts another exemplary embodiment with an “Email” tab panel 1205. In such an embodiment, a user may receive emails from third parties or forward his own emails from a different account to an email account managed at server 505. Such emails will appear in Email panel 1205 such that any multimedia content presented in email preview panel 1210 can be dragged into the drag and drop panel 435. For example, HTML encoded emails may be rendered appropriately in email preview panel 1210 and client side JavaScript code shall enable multimedia content such as 1215 to be dragged and staged in staging panel 440 for delivery to the user's cell phone. Similarly, multimedia content that is attached to an email as a MIME attachment may be extracted from the email, stored locally and rendered in Email panel 1205 to enable drag and drop of such content into drag and drop panel 435 for transfer to the user's cell phone.

E. Integration with Parent Application

[0035] Those with ordinary skill in the art will further recognize that the teachings herein can be integrated with those teachings in the Parent Application. For example and without limitation, additional photo and music tabs similar to those discussed in the Parent Application can be added to the tab panels in an exemplary embodiment of the present invention where the delivery mechanism is the SMS delivery mechanism of FIGS. 9 and 10 rather than a thin client delivery mechanism. Similarly, an exemplary embodiment of a hosted management platform as described in the Parent Application can be enhanced to provide both the SMS delivery mechanism as well as the thin client delivery mechanism.

[0036] While the present invention has primarily utilized images as the primary example of multimedia content being dragged into cell phones, those of ordinary skill in the art will recognize that alternative media and embodiments may be implemented without departing from the spirit and scope of the claimed invention. As previously discussed, other forms of media and data such as video and music may also be transferred to a user's cell phone from the web in accordance with the techniques described herein. Similarly, while the present invention has been focused on cell phone, those with ordinary skill in the art will recognize the system and methods disclosed herein can also be applied to other networked mobile devices that have limited user interfaces, similar to cell phones. For example, a similar system may be implemented with respect to a mobile MP3 playing device (with cellular networking capability) in order to wirelessly transfer music found on the web onto such a device. Those of ordinary skill in the art will additionally recognize that the programmatic design decisions, client-server functionality and selected technologies and standards as described in the foregoing specification are merely illustrative and may be implemented in alternative but functionally equivalent designs and technologies without departing from the scope or spirit of the described embodiments. For example and without limitation, the present invention has been described using HTTP, JavaScript, servlet, cookie and WAP based technologies, but those of ordinary skill in the art will recognize that numerous other alternative web based technology choices may be made to achieve results consistent with the present invention. Terminology used in the foregoing description is for the purpose of describing the particular versions or embodiments only, and is not intended to limit the scope of the present invention which will be limited only by the appended claims. As used herein and in the appended claims, the singular forms “a,” “an,” and “the” include plural references unless the context clearly dictates otherwise. Similarly, the words “for example”, “such as”, “include,” “includes” and “including” when used herein shall be deemed in each case to be followed by the words “without limitation.” Unless defined otherwise herein, all technical and scientific terms used herein have the same meanings as commonly understood by one of ordinary skill in the art. All publications mentioned herein are incorporated by reference. Nothing herein is to be construed as an admission that the embodiments disclosed herein are not entitled to antedate such disclosure by virtue of prior invention. Thus, various modifications, additions and substitutions and the like can be made without departing from the spirit of the invention and these are therefore considered to be within the scope of the invention as defined in the following claims.