throbber
(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2003/0023755A1
`(43) Pub. Date:
`Jan. 30, 2003
`Harris et al.
`
`US 2003OO23755A1
`
`(54)
`
`SYSTEMAND METHOD FOR DELIVERING
`CONTENT TO MOBILE DEVICES
`
`(75)
`
`Inventors: Michelle Harris, New York, NY (US);
`Peter DeLucia, Freehold, NJ (US);
`Dan Jethanamest, Palisades Park, NJ
`(US); Corey Tripp, New York, NY
`(US); Tom LeRoux, New York, NY
`(US); Lin Hsu, South Windsor, CT
`(US); Lee Boyle, Emerson, NY (US);
`Dan Liu, Washington Crossing, PA
`(US); Rocio Katsanis, Shreveport, LA
`(US); George Yi, New York, NY (US);
`Harry Kargman, New York, NY (US);
`Evan Herbst, Baldwin, NY (US)
`
`Correspondence Address:
`LAHIVE & COCKFIELD
`28 STATE STREET
`BOSTON, MA 02109 (US)
`
`(73)
`(21)
`(22)
`
`Assignee: Kargo, Inc., Boston, MA (US)
`Appl. No.:
`10/024,432
`
`Filed:
`
`Dec. 18, 2001
`
`Related U.S. Application Data
`(60) Provisional application No. 60/256,589, filed on Dec.
`18, 2000.
`
`Publication Classification
`
`(51) Int. Cl. ................................................. G06F 15/16
`(52) U.S. Cl. .............................................................. 709/246
`(57)
`ABSTRACT
`The illustrative embodiment of the present invention pro
`vides a platform that enables a content developer to distrib
`ute uniform content to multiple types of requesting mobile
`devices. By authoring content in a generic markup language
`and using the technologies included in the Mobile Content
`Framework(MCF), the content developer is able to provide
`content to multiple types devices without providing different
`versions of the content. The content may be authored
`originally in the generic markup language or translated from
`other languages into the generic markup language by the
`MCF. The MCF exploits the capabilities and accommodates
`the limitations of different types of wireless devices by
`converting generic markup language content to device
`specific content. The MCF interacts with device registries
`holding records of the device attributes in order to provide
`the device-specific content. The MCF handles these issues
`for current mobile devices while also being extensible for
`future mobile devices.
`
`|
`
`Web Server Accepts Device
`Request Servlet Engine
`Directs Request to Appropriate
`Page
`60
`
`Header of Request Examined to
`identify Device
`62
`
`F.
`Device Registry Consulted
`84
`
`-
`Session Stated
`66
`
`&
`
`Content Generated
`68
`
`--
`Content Translated
`70
`
`
`— Y -
`Dyanamic image and Text
`Processing
`
`-
`
`XSL Processing
`fa.
`
`--....
`
`-
`Y
`Content Returned to Device
`76
`
`-
`
`Netflix v. GoTV
`IPR2023-00757
`Netflix Ex. 1007
`
`

`

`Patent Application Publication
`Patent Application Publication
`
`Jan. 30, 2003 Sheet 1 of 4
`Jan. 30, 2003 Sheet 1 of 4
`
`US 2003/0023755 A1
`US 2003/0023755 Al
`
`|ounbl4
`
`
`
`
`
`|-----------—
`Zad/ASQD1U0I}99e/9
`
`tod
`}UBUODIIGOW
`
`8ytomawel
`Qyua}U0D
`
`
`
`qIe|N||aD
`
`BUOY
`
`OL
`
`
`
`

`

`Patent Application Publication
`Patent Application Publication
`
`Jan. 30, 2003 Sheet 2 of 4
`Jan. 30, 2003 Sheet 2 of 4
`
`US 2003/0023755 A1
`US 2003/0023755 Al
`
`Zaunbl4
`Z ?un61-I
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`ad1Aeq
`
`0@
`
`6ul6607
`
`Joupue
`
`Bul|pueyy
`
`82
`
`
`
`9E
`
`
`
`jua}UuOD
`
`Jayoyedsiq
`
`BL
`
`uoissas
`
`juawabeueyy
`
`92
`
`eBbeuw|
`
`Ansibay
`
`ve
`
`TWO
`
`sjeaysalAls
`
`ev
`
`
`
`
`
`
`
`
`
`
`
`uoyoajasebeu|
`
`JoyejsuenyKYA
`BuiyeosaBeu|
`
`JoyejsuewXVMS]99yYse|AIS
`
`
`
`
`11Meo1neq
`ylomawel4
`
`
`gYOMaWeI}UB}UOD|IGoW
`OFbv
`
`
`
`
`JaziuBooey
`|—––------------—
`
`Lo
`
`
`
`pueaa1neq
`
`Ayiqedeo
`
`Ansibey
`
`ve
`
`o1lweUuAg
`
`Ze
`
`
`
`0}TWLH
`
`SP
`
`Or
`
`olueUuAq
`
`
`
`
`
`
`
`
`Ayuiqedeg1opuep
`
`Japeoy
`
`oo
`
`aseqeyeq
`
`oe
`
`Se
`
`
`
`ia03v1reas
`
`
`
`
`
`

`

`Patent Application Publication Jan. 30, 2003 Sheet 3 of 4
`Patent Application Publication
`Jan. 30,2003 Sheet 3 of 4
`
`US 2003/0023755 A1
`US 2003/0023755 Al
`
`
`
`Web Server Accepts Device
`Web Server Accepts Device
`Request / Servlet Engine
`Request / Serviet Engine
`Directs Request to Appropriate
`Directs Request to Appropriate
`Page
`Page
`60
`Figure 3
`60 Figure 3
`
`
`
`
`Header of Request Examined to
`Header of Request Examined to
`identify Device
`Identify Device
`62
`62
`
`
`l
`
`
`
`Device Registry Consulted
`Device Registry Consulted
`64
`64
`
`fT
`
`Session Started
`Session Started
`66
`66
`
`esee
`
`Content Generated
`Content Generated
`68
`68
`
`————
`
`Content Translated
`Content Translated
`70
`70
`
`
`
`
`
`
`Dyanamic Image and Text
`Dyanamic Image and Text
`
`Processing
`Processing
`72
`72
`
`XSL Processing
`XSL Processing
`74
`74
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Content Returned to Device
`Content Returned to Device
`
`76
`76
`
`

`

`Patent Application Publication Jan. 30, 2003 Sheet 4 of 4
`Patent Application Publication
`Jan. 30,2003 Sheet 4 of 4
`
`US 2003/0023755 A1
`US 2003/0023755 Al
`
`Figure 4
`Figure 4
`
`MCF Receives Page Request From
`MCF Receives Page Request From
`Mobile Device
`Mobile Device
`80
`80
`
`
`
`
`
`Content Dispatcher Receives
`Content Dispatcher Receives
`Request / Determines Data
`Request / Determines Data
`Source
`Source
`82
`82
`
`86
`
`Data Retrieved From WAX or
`Data Retrieved From WAX or
`Non-WAX Source
`Non-WAX Source
`84
`84
`
`
`
`
`
`WAX Data Stream Saved To Cache
`WAX Data Stream Saved To Cache
`86
`
`

`

`US 2003/0023755 A1
`US 2003/0023755 Al
`
`Jan. 30, 2003
`Jan. 30, 2003
`
`SYSTEM AND METHOD FOR DELIVERING
`SYSTEMAND METHOD FOR DELIVERING
`CONTENT TO MOBILE DEVICES
`CONTENT TO MOBILE DEVICES
`
`RELATED APPLICATION
`RELATED APPLICATION
`0001. This application claims priority to co-pending U.S.
`[0001] This application claimspriority to co-pending U.S.
`Provisional Application No. 60/256,589 filed Dec. 18, 2000,
`Provisional Application No. 60/256,589 filed Dec. 18, 2000,
`for all Subject matter common to both applications. The
`for all subject matter common to both applications. The
`disclosure of Said provisional application is hereby incor
`disclosure of said provisional application is hereby incor-
`porated by reference in its entirety.
`porated by reference in its entirety.
`FIELD OF THE INVENTION
`FIELD OF THE INVENTION
`0002 The illustrative embodiment of the present inven
`[0002]
`Theillustrative embodiment of the present inven-
`tion relates generally to the delivery of content to mobile
`tion relates generally to the delivery of content to mobile
`devices, and more particularly to the delivery of the same
`devices, and more particularly to the delivery of the same
`content to multiple mobile devices using different device
`content to multiple mobile devices using different device
`protocols.
`protocols.
`
`BACKGROUND
`BACKGROUND
`Delivering easy to use content to mobile devices
`0.003
`[0003] Delivering easy to use content to mobile devices
`today is difficult for the content provider. There are many
`today is difficult for the content provider. There are many
`different mobile devices which have different functions, and
`different mobile devices which havedifferent functions, and
`many more are expected to Surface over the near term. There
`many moreare expected to surface over the near term. There
`are many content variables which must be taken into account
`are many content variables which must be taken into account
`when delivering content to a mobile device. Enterprises and
`whendelivering content to a mobile device. Enterprises and
`content providers must deliver the “right” content for each
`content providers must deliver the “right” content for each
`requesting device by taking into account content variables
`requesting device by taking into account content variables
`asSociated with the requesting mobile device. Typically,
`associated with the requesting mobile device. Typically,
`mobile devices have fewer resources available (compared
`mobile devices have fewer resources available (compared
`with a personal computer) with which to render content for
`with a personal computer) with which to render content for
`a user. Content variables include differences in device lan-
`a user. Content variables include differences in device lan
`guages, device display characteristics, device input methods,
`guages, device display characteristics, device input methods,
`character encoding methods, and user preferences. WireleSS
`character encoding methods, and user preferences. Wireless
`devices use different types of languages Such as WMIL,
`devices use different types of languages such as WML,
`HDML, HTML, compact-HTML and Palm webClippings.
`HDML, HTML, compact-HTML and Palm webClippings.
`Additionally, even when two devices employ the same
`Additionally, even when two devices employ the same
`language, there is no guarantee that they each interpret and
`language, there is no guarantee that they each interpret and
`render content the same way. For example, the way WML is
`render content the same way. For example, the way WMLis
`rendered on Nokia devices is very different from the way it
`rendered on Nokia devicesis very different from the wayit
`is rendered on devices from other manufacturers. Device
`is rendered on devices from other manufacturers. Device
`displays represent another content variable.
`displays represent another content variable.
`0004. There is a large variation in the way content is
`[0004] There is a large variation in the way content is
`displayed acroSS different handheld devices. Some displayS
`displayed across different handheld devices. Some displays
`are long and Some are wide. Some browsers can display
`are long and some are wide. Some browsers can display
`images and Some can not display images. Some displayS
`images and some can not display images. Some displays
`Support color in various depths, Some displayS Support
`support color in various depths, some displays support
`grayScale images, and Some displayS Support only black and
`grayscale images, and somedisplays support only black and
`white images. Moreover, resolution and legibility vary dif
`white images. Moreover, resolution and legibility vary dif-
`ferently from display size. Content geared for mobile
`ferently from display size. Content geared for mobile
`devices must be able to overcome these content variables
`devices must be able to overcome these content variables
`while delivering relevant content.
`while delivering relevant content.
`0005 Another content variable is the method used by the
`[0005] Another content variable is the method used by the
`wireless device for device input. Mobile phones usually only
`wireless device for device input. Mobile phonesusually only
`have a numeric keypad, while PDAs have stylus input. Some
`have a numeric keypad, while PDAs havestylus input. Some
`devices like the RIM Blackberry have a full keyboard while
`devices like the RIM Blackberry have a full keyboard while
`other devices Support Voice commands. Character encoding
`other devices support voice commands. Character encoding
`represents an addition content variable that content provid
`represents an addition content variable that content provid-
`erS must take into account when delivering content to
`ers must
`take into account when delivering content
`to
`wireleSS devices. Some devices require content to be deliv
`wireless devices. Some devices require content to be deliv-
`ered using a special character encoding. For example,
`ered using a special character encoding. For example,
`i-mode phones require content in Shift-JIS encoding in order
`i-mode phonesrequire content in Shift-JIS encoding in order
`for Japanese characters to appear correctly. An additional
`for Japanese characters to appear correctly. An additional
`type of content variable is caused by the accommodation of
`type of content variable is caused by the accommodation of
`
`user preferences. User may specify a particular language in
`user preferences. User may specify a particular language in
`which they wish to receive the content, Such as French.
`which they wish to receive the content, such as French.
`Alternatively, users may prefer to See only text content in
`Alternatively, users may prefer to see only text content in
`order to Speed up content delivery, or prefer to See graphics
`order to speed up content delivery, or prefer to see graphics-
`rich content on their color PDA display.
`rich content on their color PDA display.
`0006 Conventional methods used by web site developers
`[0006] Conventional methods used by web site developers
`to deal with content variables have been inadequate. Typi
`to deal with content variables have been inadequate. Typi-
`cally, web site developerS have attempted to provide content
`cally, web site developers have attempted to provide content
`to multiple types of wireleSS devices by providing multiple
`to multiple types of wireless devices by providing multiple
`versions of web sites, Stripping down content into a lowest
`versions of web sites, stripping down content into a lowest
`common denominator approach, or by utilizing Web Scrap
`common denominator approach, or by utilizing web scrap-
`ing technology (explained below) to create content for the
`ing technology (explained below) to create content for the
`requesting wireleSS device out of content appearing on a
`requesting wireless device out of content appearing on a
`regular HTML web site. All of the approaches produce
`regular HTML web site. All of the approaches produce
`inadequate results. Maintaining multiple versions of a web
`inadequate results. Maintaining multiple versions of a web
`site for different wireless devices is costly from both a time,
`site for different wireless devices is costly from both a time,
`human capital and monetary perspective. Presenting only
`human capital and monetary perspective. Presenting only
`basic content, Such as text-only content, on a web site
`basic content, such as text-only content, on a web site
`deprives requesting users of full featured wireleSS devices of
`deprives requesting users of full featured wireless devices of
`features present in their devices. Additionally, the approach
`features present in their devices. Additionally, the approach
`will Still will not present content that all devices can accept
`will still will not present content that all devices can accept
`(i.e.: there is no lowest common denominator that works for
`(.e.: there is no lowest common denominator that works for
`all devices). Web scraping is a technique by which useful
`all devices). Web scraping is a technique by which useful
`information, either regarding the content, the layout, or the
`information, either regarding the content, the layout, or the
`appearance of a web page, is obtained from the page
`appearance of a web page,
`is obtained from the page
`received by the browser rather than using the content Source
`received by the browserrather than using the content source
`(possibly a JSP or ASP) or an interface link to the application
`(possibly a JSP or ASP) or aninterface link to the application
`that generated the content. However, HTML content from a
`that generated the content. However, HTMLcontent from a
`Standard web site is not readily adaptable for mobile devices,
`standard website is not readily adaptable for mobile devices,
`a fact which often results in a translation of HTMLcontent
`a fact which often results in a translation of HTML content
`that is often imperfect and difficult to navigate on a request
`that is often imperfect and difficult to navigate on a request-
`ing mobile device (possibly producing gibberish or unintel
`ing mobile device (possibly producing gibberish or unintel-
`ligible text).
`ligible text).
`SUMMARYOF THE INVENTION
`SUMMARY OF THE INVENTION
`0007. The illustrative embodiment of the present inven
`Theillustrative embodiment of the present inven-
`[0007]
`tion provides a mobile content framework (MCF) that
`tion provides a mobile content framework (MCF)
`that
`facilitates abstracting content and behavior from the render
`facilitates abstracting content and behavior from the render-
`ing of content on a requesting device. Content is abstracted
`ing of content on a requesting device. Content is abstracted
`in a manner Specifically tailored to take into account the
`in a manner specifically tailored to take into account the
`limited resources of certain devices such as mobile devices
`limited resources of certain devices Such as mobile devices
`(although the process works for devices not under resource
`(although the process works for devices not under resource
`restrictions). The abstraction process allows the distribution
`restrictions). The abstraction process allows the distribution
`of uniform content to multiple types of requesting devices.
`of uniform content to multiple types of requesting devices.
`Content is generated Specifically for each device, both from
`Content is generated specifically for each device, both from
`a display Standpoint and a content navigation Standpoint.
`a display standpoint and a content navigation standpoint.
`The interface may be dynamically personalized to the taste
`The interface may be dynamically personalized to the taste
`of the individual. The MCF includes a generic markup
`of the individual. The MCF includes a generic markup
`language, referred to as Wireless Abstract XML (hereafter
`language, referred to as Wireless Abstract XML(hereafter
`WAX) that is easily extended and can be translated into a
`WAX) that is easily extended and can be translated into a
`variety of different mobile device markup languages (WAX
`variety of different mobile device markup languages (WAX
`is referred to as KGML in related provisional 60/256,589).
`is referred to as KGMLin related provisional 60/256,589).
`Content is first translated into WAX from the original
`Content
`is first
`translated into WAX from the original
`language of the content provider, or is created in WAX
`language of the content provider, or is created in WAX
`originally, and then converted into a device appropriate
`originally, and then converted into a device appropriate
`language for a requesting mobile device. WAX is designed
`language for a requesting mobile device. WAX is designed
`to enable the content developer to describe content at a more
`to enable the content developer to describe content at a more
`abstract level than that used in individual protocols. The
`abstract level than that used in individual protocols. The
`greater level of abstraction enables the Subsequent conver
`greater level of abstraction enables the subsequent conver-
`Sion of WAX into the languages used by the requesting
`sion of WAX into the languages used by the requesting
`mobile devices such as WML, HDML and HTML. Typical
`mobile devices such as WML, HDML and HTML.Typical
`markup languages focus on how content is rendered on the
`markup languages focus on how content is rendered on the
`device, while WAX focuses on generic but Smart objects
`device, while WAX focuses on generic but smart objects
`whose transformation is tailored to Specific devices. During
`whose transformation istailored to specific devices. During
`
`

`

`US 2003/0023755 A1
`US 2003/0023755 Al
`
`Jan. 30, 2003
`Jan. 30, 2003
`
`this transformation process, the MCF ensures the best type
`this transformation process, the MCF ensures the best type
`and length of text is used, the best type and size of image is
`and length of text is used, the best type and size of image is
`used, and that the content is well Suited and customized for
`used, and that the content is well suited and customized for
`the device attributes. The customization process uses device
`the device attributes. The customization process uses device
`attribute records Stored in databases to choose appropriate
`attribute records stored in databases to choose appropriate
`content for the requesting device.
`content for the requesting device.
`0008. In one embodiment, an electronic device is inter
`[0008]
`In one embodiment, an electronic device is inter-
`faced with a content location. The electronic device has
`faced with a content location. The electronic device has
`access to at least one registry holding device information for
`access to at least one registry holding device information for
`multiple mobile devices. The device information includes a
`multiple mobile devices. The device information includes a
`programming language used by each type of mobile device.
`programming language used by each type of mobile device.
`Upon receiving a request for content from a mobile device,
`Upon receiving a request for content from a mobile device,
`the electronic device retrieves device information from at
`the electronic device retrieves device information from at
`least one registry. The requested content is converted from
`least one registry. The requested content is converted from
`a generic markup language into device-Specific content
`a generic markup language into device-specific content
`using the retrieved device information.
`using the retrieved device information.
`0009. In another embodiment, an electronic device is
`[0009]
`In another embodiment, an electronic device is
`interfaced with a content location. The electronic device has
`interfaced with a content location. The electronic device has
`access to multiple registries holding device information for
`access to multiple registries holding device information for
`different types of wireless devices. The device information
`different types of wireless devices. The device information
`includes a programming language used by each type of
`includes a programming language used by each type of
`wireleSS device. The content is converted into a generic
`wireless device. The content is converted into a generic
`markup language. Upon receiving a request for content from
`markup language. Uponreceiving a request for content from
`a wireleSS device, the electronic device retrieves device
`a wireless device,
`the electronic device retrieves device
`information from at least one of the registries. The requested
`information from atleast one of the registries. The requested
`content is converted from the generic markup language into
`content is converted from the generic markup language into
`device-specific content using the retrieved device informa
`device-specific content using the retrieved device informa-
`tion.
`tion.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`BRIEF DESCRIPTION OF THE DRAWINGS
`0.010
`FIG. 1 depicts an environment suitable for prac
`[0010] FIG. 1 depicts an environment suitable for prac-
`ticing an illustrative embodiment of the present invention;
`ticing an illustrative embodiment of the present invention;
`0.011
`FIG. 2 depicts a block diagram of components
`[0011] FIG. 2 depicts a block diagram of components
`included in the Mobile Content Framework (MCF);
`included in the Mobile Content Framework (MCF);
`0012 FIG. 3 is a flow chart of the sequence of steps
`[0012] FIG. 3 is a flow chart of the sequence of steps
`performed by the Mobile Content Framework to process a
`performed by the Mobile Content Framework to process a
`content request; and
`content request; and
`0013 FIG. 4 is a flow chart of the generation of content.
`[0013] FIG. 4 isa flow chart of the generation of content.
`DETAILED DESCRIPTION
`DETAILED DESCRIPTION
`0.014. The illustrative embodiment of the present inven
`[0014]
`Theillustrative embodiment of the present inven-
`tion provides a platform that enables a content developer to
`tion provides a platform that enables a content developer to
`build an effective wireless web site. By authoring content in
`build an effective wireless web site. By authoring content in
`WAX and using the technologies included in the Mobile
`WAX and using the technologies included in the Mobile
`Content Framework(MCF), the content developer is able to
`Content Framework(MCF), the content developer is able to
`quickly and easily build wireleSS web applications that target
`quickly and easily build wireless web applicationsthat target
`wireleSS devices. The content may be authored originally in
`wireless devices. The content may be authored originally in
`WAX or translated from other languages into WAX by the
`WAX ortranslated from other languages into WAX by the
`MCF. The MCF exploits the capabilities and accommodates
`MCF. The MCFexploits the capabilities and accommodates
`the limitations of different types of wireless devices by
`the limitations of different
`types of wireless devices by
`converting WAX content to device-specific content. The
`converting WAX content to device-specific content. The
`MCFhandlesthese issues for current wireless devices while
`MCF handles these issues for current wireless devices while
`also being extensible for future wireleSS devices.
`also being extensible for future wireless devices.
`0.015
`FIG. 1 depicts an environment suitable for prac
`[0015] FIG. 1 depicts an environment suitable for prac-
`ticing the illustrative embodiment of the present invention.
`ticing the illustrative embodimentof the present invention.
`An electronic device 2 is interfaced with a network 4. The
`An electronic device 2 is interfaced with a network 4. The
`electronic device 2 includes content 6 and the MCF8. The
`electronic device 2 includes content 6 and the MCF 8. The
`content 6 may be content in written in WAX, a non-WAX
`content 6 may be content in written in WAX, a non-WAX
`wireleSS language format, or a non-wireleSS language for
`wireless language format, or a non-wireless language for-
`mat. Also interfaced with the network 4 are a plurality of
`mat. Also interfaced with the network 4 are a plurality of
`
`mobile devices 10, 12, and 14. The plurality of mobile
`mobile devices 10, 12, and 14. The plurality of mobile
`devices, a cellular phone 10, a PDA 12 and set-top box 14,
`devices, a cellular phone 10, a PDA 12 andset-top box 14,
`request the content 6 from the electronic device 2. The
`request the content 6 from the electronic device 2. The
`mobile devices may be cellular phones, PDAs, cable TV or
`mobile devices may be cellular phones, PDAs, cable TV or
`satellite TV set-top boxes, and other similar devices with
`satellite TV set-top boxes, and other similar devices with
`limited resources including Stationary devices (i.e.: a wired
`limited resources including stationary devices (i.e.: a wired
`Set-top box). Although the term wireless device is used
`set-top box). Although the term wireless device is used
`herein interchangeably with the term mobile device, those
`herein interchangeably with the term mobile device, those
`skilled in the art will realize that both wireless and wired
`skilled in the art will realize that both wireless and wired
`devices are within the Scope of present invention and
`devices are within the scope of present
`invention and
`examples using the term wireleSS are intended as illustrative
`examples using the term wireless are intendedas illustrative
`embodiments. The MCF8 translates the content 6 into WAX
`embodiments. The MCF 8 translates the content 6 into WAX
`if the content is in a non-WAX format and then converts the
`if the content is in a non-WAX format and then converts the
`content into So that it is appropriate for the requesting
`content
`into so that
`it
`is appropriate for the requesting
`wireless device 10.12 and 14 from both a language and
`wireless device 10,12 and 14 from both a language and
`device attribute perspective.
`device attribute perspective.
`0016. The MCF 8 uses its own brand of markup language
`[0016] The MCF8 usesits own brand of markup language
`known as Wireless Abstract XML (WAX) with which to
`known as Wireless Abstract XML (WAX) with which to
`describe content. This language is geared exclusively to
`describe content. This language is geared exclusively to
`mobile devices, and combines features of the most common
`mobile devices, and combines features of the most common
`markup languages like WML, HDML and HTML. WAX is
`markup languages like WML, HDML and HTML. WAX is
`designed at a level above other content markup languages
`designed at a level above other content markup languages
`such as WML, HDML and HTML. WAX focuses on “logical
`such as WML, HDMLand HTML. WAXfocuseson “logical
`widgets” that are translated to device-specific content. WAX
`widgets” that are translated to device-specific content. WAX
`is designed to overcome the challenges of graphics and
`is designed to overcome the challenges of graphics and
`user-input on Small devices. For example, a good paradigm
`user-input on small devices. For example, a good paradigm
`for delivering content on mobile phones is a “9-grid” format.
`for delivering content on mobile phonesis a “9-grid” format.
`On a mobile phone, a graphic may be displayed and broken
`On a mobile phone, a graphic may be displayed and broken
`up into 9 Segments (like a tic-tac-toe board), with each
`up into 9 segments (like a tic-tac-toe board), with each
`number on the keypad of the mobile phone acting as an input
`number on the keypad of the mobile phoneacting as an input
`link to each Segment of the grid. This paradigm works well
`link to each segmentof the grid. This paradigm works well
`when navigating and Zooming maps. This paradigm, how
`when navigating and zooming maps. This paradigm, how-
`ever, does not hold true with PDAS since they do not have
`ever, does not hold true with PDAs since they do not have
`numeric keypads. Instead, a PDA displays the “9-grid” using
`numeric keypads. Instead, a PDA displaysthe “9-grid” using
`a set of anchored images that can be clicked on using the
`a set of anchored images that can be clicked on using the
`PDA's stylus.
`PDA’s stylus.
`0017. WAX has been developed such that it is “device
`[0017] WAX has been developed such that it is “device-
`Smart” in that it detects the idiosyncrasies of each device.
`smart” in that it detects the idiosyncrasies of each device.
`For example, the WAP browser on Nokia's phones does not
`For example, the WAP browser on Nokia’s phones does not
`display lists in the same fashion as the browsers on phones
`display lists in the same fashion as the browsers on phones
`from other manufacturers. In addition to running different
`from other manufacturers. In addition to running different
`Software protocols, Some devices which are running the
`software protocols, some devices which are running the
`Same Software may be running different Software versions.
`same software may be running different software versions.
`Some devices have two programmable “soft-keys”, while
`Some devices have two programmable “soft-keys”, while
`others have one. WAX adjusts to the limitations and features
`others have one. WAX adjusts to the limitations and features
`of each device. WAX is also extensible so that as new
`of each device. WAX is also extensible so that as new
`devices becomes available, new translation sheets can be
`devices becomes available, new translation sheets can be
`added easily. For example, if a new device Supports a
`added easily. For example,
`if a new device supports a
`brand-new markup language, a translator for this new device
`brand-new markup language,a translator for this new device
`can be added Seamlessly, without changing any piece of the
`can be added seamlessly, without changing any piece of the
`core WAX architecture.
`core WAX architecture.
`0018. The WAX language may be dynamically translated
`[0018] The WAX language may be dynamically translated
`to a requesting device's native language. The MCF 8
`to a requesting device’s native language. The MCF 8
`dynamically translates WAX into other markup languages
`dynamically translates WAX into other markup languages
`using XML-based technologies. Content is translated from
`using XML-based technologies. Content is translated from
`WAX to languages like WML, HDML and HTML. The
`WAX to languages like WML, HDML and HTML. The
`content is not only translated into a specific language
`content
`is not only translated into a specific language
`appropriate for the device, but also (unlike traditional XSL
`appropriate for the device, but also (unlike traditional XSL
`stylesheets) is tailored based upon the attributes of the
`stylesheets) is tailored based upon the attributes of the
`requesting device. The attributes may involve device fea
`requesting device. The attributes may involve device fea-
`tures, memory, Storage capacity, communication Speed, type
`tures, memory, storage capacity, communication speed, type
`of operating System, and other attributes related to the
`of operating system, and other attributes related to the
`device. Some devices require their own special translation
`device. Some devices require their own special translation
`
`

`

`US 2003/0023755 A1
`US 2003/0023755 Al
`
`Jan. 30, 2003
`Jan. 30, 2003
`
`Source while maintaining a separate registry for application
`rules. For example, a WAX “Date-Chooser” renders one
`source while maintaining a separate registry for application-
`rules. For example, a WAX “Date-Chooser” renders one
`Specific device groupings and capabilities.
`way on the limited Screen sizes of mobile phones (possibly
`way on the limited screen sizes of mobile phones (possibly
`specifi

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket