The present invention relates to mobile communications, and more particularly to tailoring the content delivered to a mobile device based upon the features of the mobile device.
In the marketplace, there are currently numerous different types of mobile devices. Mobile devices include mobile or cellular phones, smart phones, personal digital assistants (“PDAs”), palmtop computers, laptop computers and the like. These mobile devices function as wireless communication devices via a wireless communication link (GSM, GRPS, 3G, CSMA and the like) and access content over a wireless network infrastructure.
Each of these mobile devices may include different variations and features, such as web browser(s), as part of their platform. As a result, there may be difficulty in delivering content in an appropriate format to a great number of these mobile devices due to their varying features, such as varying mobile web browsers. For example, the content may not be able to be rendered appropriately on some of these mobile devices since the content provider may not be transmitting content in a format compliant with their web browsers.
The World Wide Web Consortium (“W3C”) has attempted to address this problem by adopting the Composite Capabilities/Preference Profile (“CC/PP”). The CC/PP is a specification for defining capabilities and preferences of user agents, where a user agent may refer to a client application implementing a network protocol used in communications within a client-server distributed computing system. With the CC/PP, a repository is created that maps the user agent to a set of features that are supported for that mobile device. However, the repository must be constantly updated in order to ensure that the mapping is up-to-date.
An additional attempt to address the difficulty in delivering content in an appropriate format to a great number of mobile devices with varying features is to have the mobile devices contain all of the possible libraries for the various mobile browser vendors thereby ensuring that the content is rendered on the mobile device appropriately. However, requiring the mobile devices to contain all of the possible libraries for the various mobile browser vendors is burdensome. Furthermore, the libraries would constantly need to be updated to ensure they are up-to-date.
Hence, there has not been an effective solution to delivering content in an appropriate format to a great number of mobile devices due to their varying features, such as varying mobile web browsers.
In one embodiment of the present invention, a method for delivering tailored specific content to a mobile device comprises providing a shim application to the mobile device, where the shim application detects capabilities of the mobile device. The method further comprises receiving a request for content, where the request comprises header information providing the capabilities of the mobile device. Additionally, the method comprises generating the content in a format compliant to the mobile device based on the header information. In addition, the method comprises transmitting, by a processor, the generated content to the mobile device.
The foregoing has outlined rather generally the features and technical advantages of one or more embodiments of the present invention in order that the detailed description of the present invention that follows may be better understood. Additional features and advantages of the present invention will be described hereinafter which may form the subject of the claims of the present invention.
A better understanding of the present invention can be obtained when the following detailed description is considered in conjunction with the following drawings, in which:
The present invention comprises a method, system and computer program product for delivering tailored specific content to a mobile device. In one embodiment of the present invention, a shim application is provided to the mobile device by a content server after the mobile device visits the content server for the first time. The shim application detects the capabilities of the mobile device, such as the screen size, screen resolution, memory size, browser capabilities, etc. The shim application then includes such information in the header of the requests, such as a request for content, sent from the mobile device to the content server. The content server then generates the requested content in the appropriate format based on the information provided in the header. In this manner, the content server will now be able to ensure that the content provided by the content server for a particular mobile device will be appropriately displayed on the mobile device.
In the following description, numerous specific details are set forth to provide a thorough understanding of the present invention. However, it will be apparent to those skilled in the art that the present invention may be practiced without such specific details. In other instances, well-known circuits have been shown in block diagram form in order not to obscure the present invention in unnecessary detail. For the most part, details considering timing considerations and the like have been omitted inasmuch as such details are not necessary to obtain a complete understanding of the present invention and are within the skills of persons of ordinary skill in the relevant art.
Referring now to the Figures in detail,
Mobile devices 101 are in wireless communication with a content server 102 via a network 103, which may be, for example, a wireless wide area network, a circuit-switched telephone network, a Global System for Mobile Communications (GSM) network, Wireless Application Protocol (WAP) network, a WiFi network, an IEEE 802.11 standards network, various combinations thereof, etc. Other networks, whose descriptions are omitted here for brevity, may also be used in conjunction with system 100 of
Content server 102 is configured to receive and provide services and information to mobile devices 101. In particular, content server 102 is configured to receive a request for content from mobile device 101 and to ensure that the content is formatted in a format compliant for mobile device 101 based on header information provided by a shim application as discussed further below. A description of one embodiment of the hardware configuration of content server 102 is provided below in connection with
While
Referring now to
Referring again to
Mobile device 101 may further include a communications adapter 209 coupled to bus 202. Communications adapter 209 interconnects bus 202 with an outside network (network 103) thereby enabling mobile device 101 to communicate with content server 102.
I/O devices may also be connected to mobile device 101 via a user interface adapter 210 and a display adapter 211. Keyboard 212, mouse 213 and speaker 214 may all be interconnected to bus 202 through user interface adapter 210. Data may be inputted to mobile device 101 through any of these devices. A display monitor 215 may be connected to system bus 202 by display adapter 211. In this manner, a user is capable of inputting to mobile device 101 through keyboard 212 or mouse 213 and receiving output from mobile device 101 via display 215 or speaker 214.
As stated above,
Referring again to
Content server 102 may further include a communications adapter 309 coupled to bus 302. Communications adapter 309 interconnects bus 302 with an outside network (network 103) thereby allowing content server 102 to communicate with mobile devices 101.
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the C programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the present invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to product a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the function/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the function/acts specified in the flowchart and/or block diagram block or blocks.
As stated in the Background section, mobile devices may include different variations and features, such as web browser(s), as part of their platform. As a result, there may be difficulty in delivering content in an appropriate format to a great number of these mobile devices due to their varying features, such as varying mobile web browsers. For example, the content may not be able to be rendered appropriately on some of these mobile devices since the content provider may not be transmitting content in a format compliant with their web browsers. Currently, there has not been an effective solution to delivering content in an appropriate format to a great number of mobile devices due to their varying features, such as varying mobile web browsers.
The principles of the present invention provide an improved technique for delivering content in an appropriate format to various mobile devices with varying platforms by having the content server deliver specifically tailored content to each mobile device as discussed below in connection with
As stated above,
Referring to
In step 402, a determination is made by server 102 as to whether the visit by mobile device 101 is a first time visit. If the visit is not a first time visit, then content sever 102 continues to monitor a visit by a subsequent mobile device 101 in step 401.
If, however, content server 102 detects a first time visit by mobile device 101, then, in step 403, content server 102 provides a shim application to mobile device 101. A shim application refers to a small library which transparently intercepts an application programming interface of mobile device 101, changes the parameters passed, handles the operation itself or redirects the operation elsewhere. “Providing the shim application,” as used herein, includes any means for the shim application to be provided to mobile device 101, including having content server 102 directly transmit the shim application to mobile device 101 as well as having content server 102 transmit a link to a website to download the shim application. In one embodiment, the shim application will be specific to mobile device 101 and will act as a client side proxy application. In one embodiment, the shim application will be configured as part of the installation.
In step 404, the user of mobile device 101 installs the shim application on mobile device 101. Once installed, in step 405, the shim application will detect the capabilities of mobile device 101. For example, the shim application can detect one or more of the following capabilities: screen size, screen resolution, memory size, browser capabilities, and the like. This list is not intended to be limiting but to provide examples of information that may be used to determine the capabilities of mobile device 101 so that content server 102 appropriately formats the content to be appropriately displayed on mobile device 101. Embodiments of the present invention cover any such information regarding the capabilities of mobile device 101 that may be used by content server 102 to appropriately format the content to be appropriately displayed on mobile device 101.
In step 406, the information regarding the capabilities of mobile device 101 detected by the shim application is stored in a cache (not shown in
In step 407, content server 102 receives a request for content from mobile device 101, where the request includes header information that provides content server 102 with the features or capabilities mobile device 101 supports, such as the capabilities detected in step 405. In one embodiment, the shim application adds the header information to the beginning of the data (i.e., request) being transmitted to content server 102, where the header information is obtained from the cache of mobile device 101.
In step 408, content server 102 processes the request. In step 409, content server 102 generates specific content to be delivered to mobile device 101 based on the received header information thereby ensuring that the content is formatted in a manner so that it will be appropriately displayed on mobile device 101. By content server 102 receiving information regarding the capabilities of mobile device 101 via the header information, content server 102 will now be able to ensure that the content provided by content server 102 for a particular mobile device 101 will be appropriately displayed on mobile device 101.
In step 410, content server 102 transmits the content generated in step 409 to mobile device 101.
In some implementations, method 400 may include other and/or additional steps that, for clarity, are not depicted. Further, in some implementations, method 400 may be executed in a different order presented and that the order presented in the discussion of
An example of a program using the principles of the present invention includes a program for generating charts and gauges which can be generated either on the client-side or on the server-side. The determination as to whether the program generates the charts and gauges on either the client-side or on the server-side can be determined based on the memory capabilities of mobile device 101, which is obtained from the shim application.
The descriptions of the various embodiments of the present invention have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
The present application is a continuation application of pending U.S. patent application Ser. No. 13/193,810, which was filed on Jul. 29, 2011, which is assigned to the assignee of the present invention. The present application claims priority benefits to U.S. patent application Ser. No. 13/193,810.
Number | Name | Date | Kind |
---|---|---|---|
6112246 | Horbal et al. | Aug 2000 | A |
6791586 | Baker | Sep 2004 | B2 |
6871236 | Fishman et al. | Mar 2005 | B2 |
7103668 | Corley et al. | Sep 2006 | B1 |
7113776 | Minear et al. | Sep 2006 | B2 |
7222306 | Kaasila et al. | May 2007 | B2 |
7284061 | Matsubayashi et al. | Oct 2007 | B2 |
7603106 | Aaltonen et al. | Oct 2009 | B2 |
7734663 | DeAnna et al. | Jun 2010 | B2 |
7853593 | Serdy, Jr. et al. | Dec 2010 | B2 |
7908315 | Parkinson | Mar 2011 | B2 |
7911966 | Yoo et al. | Mar 2011 | B2 |
7974988 | Nandiwada et al. | Jul 2011 | B2 |
7995994 | Khetawat et al. | Aug 2011 | B2 |
8081954 | Aaltonen et al. | Dec 2011 | B2 |
8099490 | Deakin | Jan 2012 | B2 |
8213333 | Greel et al. | Jul 2012 | B2 |
20030023427 | Cassin et al. | Jan 2003 | A1 |
20030033377 | Chatterjee et al. | Feb 2003 | A1 |
20030095135 | Kaasila et al. | May 2003 | A1 |
20030140089 | Hines | Jul 2003 | A1 |
20030210776 | Sollee | Nov 2003 | A1 |
20040016002 | Handelman et al. | Jan 2004 | A1 |
20040024867 | Kjellberg | Feb 2004 | A1 |
20040133657 | Smith et al. | Jul 2004 | A1 |
20040143656 | Okada et al. | Jul 2004 | A1 |
20040153712 | Owhadi et al. | Aug 2004 | A1 |
20050078638 | Xue et al. | Apr 2005 | A1 |
20050091311 | Lund et al. | Apr 2005 | A1 |
20050096016 | Tervo et al. | May 2005 | A1 |
20050149564 | Jain et al. | Jul 2005 | A1 |
20050154787 | Cochran et al. | Jul 2005 | A1 |
20060067295 | Lehotsky et al. | Mar 2006 | A1 |
20060165040 | Rathod et al. | Jul 2006 | A1 |
20060168101 | Mikhailov et al. | Jul 2006 | A1 |
20060198359 | Fok et al. | Sep 2006 | A1 |
20060274869 | Morse | Dec 2006 | A1 |
20070183435 | Kettering et al. | Aug 2007 | A1 |
20080003991 | Sievers et al. | Jan 2008 | A1 |
20080016533 | Rothschild | Jan 2008 | A1 |
20080139112 | Sampath et al. | Jun 2008 | A1 |
20080147592 | Nandiwada et al. | Jun 2008 | A1 |
20080192684 | Tervonen | Aug 2008 | A1 |
20080222621 | Knight et al. | Sep 2008 | A1 |
20080253311 | Jin | Oct 2008 | A1 |
20080263139 | Martin | Oct 2008 | A1 |
20080298447 | Yoo et al. | Dec 2008 | A1 |
20090063267 | Dubinko et al. | Mar 2009 | A1 |
20090149162 | Tenny | Jun 2009 | A1 |
20090177770 | Jeong | Jul 2009 | A1 |
20090213771 | Celentano et al. | Aug 2009 | A1 |
20090233587 | Muhonen et al. | Sep 2009 | A1 |
20090265763 | Davies et al. | Oct 2009 | A1 |
20090300685 | Easter | Dec 2009 | A1 |
20100121975 | Sinha et al. | May 2010 | A1 |
20100153583 | Harris et al. | Jun 2010 | A1 |
20100174607 | Henkin et al. | Jul 2010 | A1 |
20100191835 | Mehta et al. | Jul 2010 | A1 |
20100223324 | Kawai | Sep 2010 | A1 |
20100271992 | Wentink et al. | Oct 2010 | A1 |
20100273462 | Thorn et al. | Oct 2010 | A1 |
20100299338 | Aarni et al. | Nov 2010 | A1 |
20110045847 | Roin et al. | Feb 2011 | A1 |
20110161409 | Nair | Jun 2011 | A1 |
20110208822 | Rathod | Aug 2011 | A1 |
20120158396 | Douceur et al. | Jun 2012 | A1 |
20120206259 | Gassaway | Aug 2012 | A1 |
20130031198 | Jemiolo et al. | Jan 2013 | A1 |
20130070655 | Nishida et al. | Mar 2013 | A1 |
Entry |
---|
Hyvarinen, Tuuli, “Browsing and Navigating Web Applications with Mobile Devices,” University of Jyvaskyla, Master's Thesis in Information Systems Science, Dec. 14, 2004. |
Fu et al., “A Framework for Device Capability on Demand and Virtual Device User Experience,” IBM Journal Research and Development, vol. 48, No. 5/6, Sep./Nov. 2004, pp. 635-648. |
Mahmoud et al., “Toward a Framework for the Discovery and Acquisition of Mobile Applications,” ICMB-GMR 9th Inter. Conf. on Jun. 13-15, 2010, pp. 58-65. |
Cheng et al., “A Novel Design of Behavioral Analysis Capability in Mobile SNS,” ICCTA IEEE Inter. Conf. on Oct. 16-18, 2009, pp. 907-913. |
Office Action for U.S. Appl. No. 13/193,810 dated Nov. 5, 2013, pp. 1-19. |
Office Action for U.S. Appl. No. 13/193,810 dated Sep. 16, 2014, pp. 1-15. |
Office Action for U.S. Appl. No. 13/193,810 dated May 22, 2014, pp. 1-15. |
Office Action for U.S. Appl. No. 13/193,810 dated Mar. 11, 2015, pp. 1-14. |
Number | Date | Country | |
---|---|---|---|
20130031205 A1 | Jan 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13193810 | Jul 2011 | US |
Child | 13405311 | US |