EP2399209A1 - Plate-forme d'accès à un contenu et procédés et appareil fournissant un accès à un contenu internet pour des dispositifs hétérogènes - Google Patents

Plate-forme d'accès à un contenu et procédés et appareil fournissant un accès à un contenu internet pour des dispositifs hétérogènes

Info

Publication number
EP2399209A1
EP2399209A1 EP10708579A EP10708579A EP2399209A1 EP 2399209 A1 EP2399209 A1 EP 2399209A1 EP 10708579 A EP10708579 A EP 10708579A EP 10708579 A EP10708579 A EP 10708579A EP 2399209 A1 EP2399209 A1 EP 2399209A1
Authority
EP
European Patent Office
Prior art keywords
content
web
request
requestor
device type
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP10708579A
Other languages
German (de)
English (en)
Inventor
Samson Yeung
Hoi Shuen Chau
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Aceplan Investments Ltd
Original Assignee
Aceplan Investments Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Aceplan Investments Ltd filed Critical Aceplan Investments Ltd
Publication of EP2399209A1 publication Critical patent/EP2399209A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/957—Browsing optimisation, e.g. caching or content distillation
    • G06F16/9577—Optimising the visualization of content, e.g. distillation of HTML documents

Definitions

  • the Internet has made vast amounts of information available to computer users, as well as large numbers of applications such as games and other content.
  • advances in telecommunications and data processing technologies have enabled Websites to be viewed on mobile devices, almost all of the available content is designed for the screen size and processing capability of desktop and laptop computers.
  • Most Website providers only consider mobile Web content as an afterthought, rather than as a parallel development and distribution medium, and many consider it prohibitively expensive to customize all of their content for mobile device users.
  • Website content is displayable to users, there is a high overhead inherent in modifying Web pages to create a mobile- friendly version for access by a large number of users of heterogeneous mobile devices, and in maintaining that modified set of pages.
  • Another solution is for mobile-friendly WML pages to be generated dynamically when requested by a mobile device user.
  • Such run-time transcoding of site content can avoid the Website provider having to pre-generate and maintain separate WAP pages for mobile devices, but the run-time transcoding introduces other problems.
  • the additional processing may contribute to unsatisfactory latency, regardless of whether this is implemented on the user's device or elsewhere in the network.
  • not all Web page content can be converted to a format that can be displayed via a WAP browser, and not all devices are WAP-enabled.
  • the inventors of the present invention have determined that an improved user experience is achievable for users of communication devices, by providing selected content in an optimized manner according to different device types, different content provider preferences, different user group preferences and/or for different categories of Web site and Web content.
  • the invention provides a solution for customizing the displayed content and format and for creating new versions of Web content (including 'mini page' versions of Web pages) for a communications device that combines selected content from a number of different sources such as from multiple original Web pages.
  • the present invention provides a solution for use in a communications network, in which multimedia content such as Website content needs to be accessed from many heterogeneous devices such as mobile telephones and PDAs, as well as desktop and laptop computers.
  • multimedia content such as Website content needs to be accessed from many heterogeneous devices such as mobile telephones and PDAs, as well as desktop and laptop computers.
  • a content access platform and methods and apparatus according to various embodiments of the invention are provided to mitigate the problems identified above.
  • embodiments of the invention enable elements of Web content to be combined in accordance with user-specific requirements and content-provider specifications, to provide a customized user experience.
  • suitable versions of Web pages can be performed preemptively in advance of a request being received, or in response to a request being received.
  • suitable versions of Web pages ('mini pages') and/or suitable templates for generating 'mini pages' are generated and stored so as to be available for use when required. Any number of pre-formatted 'mini page' versions may be generated and stored, according to the number of different device types that may request access to this content.
  • the invention is also useful in providing improved access to suitable versions of downloadable application programs such as games, to ensure that a request for an application from a particular end user device is responded to by providing a version of the application that is suitable for the device type.
  • One aspect of the invention provides a content access platform comprising at least one content server for storing one or more versions of items of content (such as 'mini page' versions of Web pages), and a router for redirecting content requests (e.g. HTTP Web page requests) to a selected content server or repository in response to identifying the content request as having come from a particular requestor device type.
  • the content server stores one or more versions of the content that are suitable for display on one or more specific types of requestor devices.
  • the router identifies attributes of the request that are representative of the requestor device type, and redirects the request to an appropriate content server at which an appropriate version of the content is stored, or redirects requests to a plurality of content servers to retrieve each of a plurality of elements of a desired mini page.
  • the appropriate version of the content is retrieved (or is generated by combining a number of elements of content) and is sent to the requestor device, and the end user can then view the appropriate version of the media content.
  • the analyzer performs an analysis of the text on a page, such as a statistical analysis of high frequency words on the page or Website, to identify representative key words or to determine whether the site is a sports site, a retail site, a news site, and so on. Category information and/or identified keywords may then be stored in association with the Web page or Website.
  • the analyzer also identifies the separate building blocks of the site and their layout (e.g. parsing the source HTML to determine the hierarchical HTML document structure of a page and the page hierarchy within a Website, and identifying major 'assets' that users of the site will require access to).
  • the analyzer may perform its operations pre-emptively, for example when prompted by an operator of the content access platform, to generate mini pages in readiness for later retrieval by device users when users request access to the respective Web content.
  • New versions of Web contents referred to as 'mini pages' in the context of this patent specification include both minor changes to an original Web page (such as a scaled down and re-ordered pages including substantially the same content as the original page) as well as simplified pages that omit a proportion of the original Web page content for simplified display on a resource-constrained device.
  • a 'mini page' may also include components that were not included in a single original page, resulting in a new combination of content.
  • device-type-specif ⁇ c mini pages is especially advantageous for users of resource-constrained devices that have either small screen sizes or constraints on download speeds or memory, but no limitation is implied by the phrase 'mini page' which is intended to encompass any replacement Web pages that are created for display on a particular type of device or created for a particular set of users.
  • device-type-specific templates can be generated and stored for reconfiguring Web page content for display on devices of that type.
  • the use of device-type- specific templates that encapsulate device characteristics and/or user requirements for generation of the mini-pages enables Web content to be presented in a manner that is optimised for the particular user, especially when combined with the intelligent modelling of a Website to categorize and model the site and to use that site model to guide the selection or generation of a suitable template.
  • a content server of the content access platform provides a repository into which many different Website providers and other content providers can save mobile-device-compatible 'mini page' versions of their Websites or selected content.
  • Web content providers can benefit from the media access platform as a distribution channel for Web content, and content distribution may be a fee-based service to enable the media access platform provider to recover costs.
  • the storage provided by the content access platform ensures that Website providers are not required to maintain additional storage for their different versions of Web content, as this and the labour-intensive processes of creating and maintaining a mobile-device-friendly version of a Website can be outsourced to the content access platform's template-based generation and content servers. This lowers the cost barrier for Web content providers who would like to provide a mobile-device-friendly version of their content.
  • the original Web servers can be shielded from the problems of potentially very high network traffic arising from mobile devices sending media content requests, as requests from such devices will be redirected to the respective content servers of the content access platform that hold suitable mini pages or hold content for building a mini page.
  • Website providers responsibility for maintaining a satisfactory response to requests from mobile devices can be outsourced from the Website providers to the provider of the content access platform.
  • This can be very beneficial to a Website provider, especially during periods of very high numbers of requests such as during popular sporting events. Many Web servers will be unable to manage the high workload that arises if requests from every different device type are competing for service from that server.
  • the Website providers can rely on the router to achieve efficient routing of requests to the content server that holds the relevant mini pages or elements of mini pages, since the router has the requisite knowledge of where each version of the content is stored. This knowledge can help to avoid network bottlenecks.
  • particular desired combinations of media content may be specified within a new configuration file such that a customized combination of content is available for retrieval by some device users.
  • the specification of a desired content combination may be by the original content provider or by another special interest group. End users may register their devices with the content access platform with an indication of which device-type ⁇ and user- group they correspond to. This could involve users specifying language requirements, such that their content requests are routed to one or more content servers holding video and associated Mandarin text and audio, whereas another user may wish to access the same video with English text and audio.
  • the customized content combinations are achieved by the user specifying content requirements, which requirements data is then used (for example by a Website provider) to generate a template that captures the content requirements as an XML configuration file that includes one or more URLs for retrieval of desired content.
  • requirements data is then used (for example by a Website provider) to generate a template that captures the content requirements as an XML configuration file that includes one or more URLs for retrieval of desired content.
  • Some users may desire to have a combination of applications such as a news feed component providing latest sports scores in combination with a small video screen area showing live action, additional images and games.
  • the content identifiers can be defined in a template or configuration file and can be used to combine the desired Web assets within a new mini page. The mini page can then be stored for access by the requesting user, and potentially by other users.
  • This embodiment of the invention provides opportunities for placing advertisements with popular content for maximum visibility.
  • One embodiment of the invention includes a router that cooperates with a proxy service to enable more efficient route determination to be carried out for sending content requests across the network, using knowledge of the locations of device-type-specific versions of content to enable improved resolution of routing questions.
  • the route determination will enable network bottlenecks to be bypassed in many cases. In a conventional system, it is common for bottlenecks to arise when requests from large numbers of mobile telecommunication devices are directed at the same Web server during a short period of time.
  • an efficient route to the desired network location can be determined.
  • One aspect of the invention provides apparatus for use in a communications network, comprising: a template repository storing a set of template files that each specify information for determining how Web content is to be displayed on a particular type of user device that is associated with the respective template file;
  • a router that is responsive to identification of a requestor device type to retrieve a respective template file from the template repository and, in response to the template specifying a plurality of separate sources of Web content, to send a plurality of Web content requests to the separate sources, thereby to retrieve required Web content from the plurality of separate sources;
  • a content generator for combining the retrieved Web content and providing the combined content to the requestor device.
  • a further aspect of the invention provides a router system, for use in a communications network, wherein the router system is arranged for receipt of content requests from content requestor devices, which content requests include information enabling identification of the requestor device type, the router system comprising:
  • a repository storing network location information for a plurality of sources of content, the repository also including an identification of respective device types with which each of the plurality of content sources is associated;
  • a request analyzer for analyzing received content requests from requestor devices to identify the respective requestor device type
  • a request redirection component that is responsive to identification of a requestor device type to redirect the request to a selected plurality of the content sources.
  • a further aspect of the invention provides a method for automated generation of a displayable version of Web content, the method comprising: analyzing Web content to detect a set of identifiers of content types within the content;
  • Figure 2 represents a directory access request and mini page access via the directory, according to an embodiment of the invention, and shows example screen shots including an example mini page and example MiniSite directory pages that can be used to link to the mini page;
  • Figure 8 shows an example mini page representation of an article module
  • Figure 9 shows an example visual list module and its corresponding DOM structure
  • Figure 10 shows an example visual component and the way it is specified in the example DOM structure
  • Figure 11 shows an example article module and its subdomain tree
  • Figure 12 shows an exemplary snippet of a list module definition
  • Figure 13 shows an example of two modules with matching DOM structures
  • Figure 14 shows the structure of a configuration file according to one embodiment of the invention.
  • Figure 15 shows compression and other transformations for resource handling, according to an embodiment of the invention.
  • requestor devices 100,110,120,130 including desktop and laptop personal computers and a range of PDAs and high-functionality mobile telephones ('smart phones') and low-end mobile telephones.
  • requestor devices 100,110,120,130 including desktop and laptop personal computers and a range of PDAs and high-functionality mobile telephones ('smart phones') and low-end mobile telephones.
  • the Web content requests may comprise conventional HTTP requests or an alternative form of Web content request such as described below.
  • the Web content access platform 10 of this embodiment hosts 'mini pages' in a content repository 60 and hosts a MiniSite directory in directory repository 140.
  • the MiniSite directory comprises a list of available mini pages, and can be provided as a set of alternative versions of the directory pages, with each version being suitable for presentation on a different type of device.
  • Example screen shots showing a MiniSite Directory screen display are included in Figure 2, but the displayed representation can vary greatly between devices.
  • the router 20 within the content access platform 10 includes a mechanism for intercepting directory requests and Web content requests. This mechanism is provided by the request analyzer 30, and its operations are described in detail below.
  • user agent header attributes (such as HTTP request headers) are analyzed on receipt of a Web content request, and are compared with a device database that can match the user agent (UA) header attributes to a set of characteristics and capabilities of the requestor device. This is described below.
  • end users devices have pre-installed user agents that are configured to specify their device type explicitly within non-standard requests sent to the content access platform 10. This is especially advantageous if the communication network includes other communication gateway servers that do not pass on UA header attributes when routing requests.
  • a directory-reference URL is embedded in a user device for use by the device browser.
  • the device type is specified by means of a subdomain name within the URL.
  • a mobile telephone's Web browser is configured to send standard requests that include a unique resource identifier comprising a domain name pref ⁇ xe.d by a device type identifier such as: 'e71.url23.com' f where 'e71 ' identifies a specific device type such as a Nokia e71 mobile phone, and 'url23.com' identifies the domain name associated with a MiniSite directory
  • intuitive identifiers for device types (such as this example 'e71 ') are desirable, it is known in the art that there can be many levels within the hierarchy of labels within a domain name and each label can include up to 63 ASCII characters up to a total of 253 characters for the domain name, and so the simple example given above is just one simple example of use of a subdomain name as
  • the content access platform of this embodiment allows for both request types to be used.
  • Other implementations of the non-standard resource request can be used, as long as this is predefined for the requestor devices 100,110,120,130 and the request analyzer 30 of the router 20 such that any such non-standard requests can be interpreted correctly.
  • the use of device-type identifiers in subdomain names is advantageous because this can easily be extracted from requests and compared with a device type database.
  • the device type prefix defining a subdomain e.g. the prefix 'e71 ' of subdomain 'e71.url23.com' of domain 'url23.com'
  • the device database can be searched for the request and compared with a device database, to retrieve device characteristics or display requirements, and/or to determine which pre-stored MiniSite directory page 210,220,230 or mini pages 240 are suitable for the type of device.
  • the device-type identifier within the request can be directly matched with a stored directory page that is associated with that device type. This process is described in more detail below with reference to Figures 3A, 3B, 4A and 4B.
  • the analyzer If there is no identified match for the subdomain name, the analyzer also obtains 322 HTTP header attributes from the request and checks 323 for a device-identifier within HTTP header attributes, if such device attributes are received (some countries have communication infrastructures that do not pass on such header attributes, so it is advantageous that another mechanism, such as the use of subdomain names, is also implemented). Having identified a device-type-identifying subdomain name or HTTP header attribute, the analyzer compares 320 the identifier with entries in a device database 50 that maps device type identifiers to device model numbers.
  • a standard directory page is served 390 and an alternative mechanism is provided to determine an appropriate version of the directory page. This is achieved by sending 370 to the requestor device a request device information - preferably in the form of a user prompt, although this could be automated if communication devices are configured to automatically respond to requests for device information.
  • the device model and retrieved information obtained in this way can then be added 380 to the device" database. Thereafter, devices of their type will be recognizable and can be matched to a respective device-compatible directory page. This provides a self-learning mechanism, such that the content access platform will support more devices over time.
  • the served directory pages enable easy user selection of mini pages that are available via the content access platform, via the known mechanism of browser activation when a user selects a hyperlink within a displayed Web page.
  • Described below is the analysis and processing of content requests, other than directory requests, when received by the router 20 of the content access platform 10. This includes requests that are sent from a user's device when a user interacts with a displayed MiniSite directory page, as well as other requests for mini pages and conventional Web page requests.
  • the request analyzer 30 determines 310, from the domain name, that it is not a MiniSite directory request.
  • the requestor device type and a user preference token are included in the request.
  • user agent information in HTTP request header attributes can be obtained 401 (when these attributes are available) and analyzed 402 and compared with a device profile database by the request analyzer 30 to determine 400 the device type. This can provide a specific device model number that has known screen size, processing power and browser capability. A check is carried out
  • HTTP header attributes can include additional explicit device characteristics
  • the device model number is extracted from the HTTP header for non-PC-originated requests and this number is used as a search key for accessing device capabilities from a device profile database 50.
  • the device profile database 50 contains detailed characteristics for each of a large number of mobile device types, and is updateable as new devices come onto the market. Such device profile databases are known in the art (for example, open source lists of device capabilities are maintained in a publicly accessible manner). If user agent information is not available (e.g. is blocked within a communication network), a query page can be sent 450 to the requestor device to invite users to specify device characteristics (screen size, manufacturer, supported media types, etc). The user can insert information into the query page and submit this to the content access platform. This device information can then be permanently stored (e.g. using cookies or a user account database).
  • the main additional information held in the device profile database 50 of the present embodiment is a device type identifier that can be used to represent the characteristics of the requestor device.
  • device type A all requestor devices having a particular range of screen dimensions (i.e. similar sized screens), memory within a defined range and communication bandwidth within a defined range
  • device type B devices having an alternative screen layout
  • device type C devices having an alternative screen layout
  • a device with an identical screen size to device type A, but with less processing power, memory and colour depth may be device type D, and so on.
  • the model number of a current requestor device is held in the database 50 with device capability information and an associated device type identifier.
  • the device type identifier is retrieved from the device profile database and combined with the
  • the combined device type identifier and Web content identifier is compared 520 with an index of Web content versions stored in a content repository 60 of a content server.
  • the router forwards 550 the content request to the content server holding the required version of the requested Web contents, and this version is served 530,560 to the requestor.
  • each of the content versions stored within a repository of the access server 10 is a 'mini page' comprising an alternative version of the original target Web page, or is a device-type-specific version of a content component - such as an image, a video clip, a game or another application program.
  • the mini pages and stored content versions will have a smaller data size than the original Web page contents, and will be more suitable for display on a small display screen or execution within a mobile device.
  • 'mini pages' in the context of this patent specification include both minor changes to an original Web page (such as a scaled down and re-ordered pages including substantially the same content as the original page) as well as simplified pages that omit a proportion of the original Web page content for simplified display on a resource-constrained device.
  • a 'mini page' may also include components that were not included in a single original page, resulting in a new combination of content, and no limitation is implied by the word 'mini' which is intended to encompass any replacement Web pages that are created for display on a particular type of device or created for a particular set of users.
  • a request that requires access to Web content as a mini-page is routed to a Web site (or ⁇ to a plurality of content sources) that includes suitable content.
  • the request may be routed to the same Web server as holds the original Web page, if the mini-page and original web page are held on the same server.
  • the requests are typically re-routed to a different content server that holds mini-page versions of Web pages.
  • This is implemented by means of a proxy service 70 that re-routes requests (that request content from an original site) to an alternative network location at which is held an alternative version of the requested content.
  • the proxy service is implemented using the Domain Name System (DNS) and uses knowledge of the location of different versions of particular requested content ('mini page' versions).
  • DNS Domain Name System
  • a 'List module' is a reference to content that is available on a separate Web page, and mainly contains the following elements:
  • Figure 5 provides examples of list modules (represented as Module- 1, Module-2, etc) in a conventional Web page.
  • Figure 7 shows a mini page representation 710 of a list module.
  • An 'Article module' contains actual Web page content, and mainly contains
  • An example article module is shown in Figure 6, with a set of separately identifiable components title 600, metadata 610, picture 620 and text 630, as well as some related links 640.
  • a mini page article module 720 is shown in Figure 8.
  • Module content may be static or dynamic, with a different analysis procedure required for dynamic contents.
  • HTML elements within the Web page source file can be analyzed using an html parser to extract the component-identifying HTML headers.
  • an article title and the body of a text article can be identified as separate elements.
  • client side script i.e. java-script, AJAX
  • the content components can be identified by a script engine that creates the Web page DOM tree at execution time. An example is user comments on a news Web site.
  • the module identification process includes a pattern recognition step.
  • pattern recognition can be iteratively improved by means of an adaptive learning process as new pattern are identified and stored.
  • List module specify the outer-most enclosing HTML element (i.e. ⁇ DIV>, ⁇ TABLE>, etc)
  • Figure 11 provides an example of an article module 1110, showing the association between the visual components within that module and their details in the subdomain tree.
  • a snippet of a list module definition is provided in Figure 12.
  • module identification can be automated, as described below.
  • the analysis method involves downloading the page source file (e.g. using a traditional crawler) and parsing the HTML file to generate a DOM tree (using an html parser). The DOM tree is then traversed and, for every node N traversed, the following steps are performed:
  • a respective device-type-suitable configuration file is retrieved 570 from a content server and information within this file is used to identify components of interest.
  • the components can be retrieved from respective content servers and processed and combined 290 as specified in the configuration file.
  • the proxy server that re-routes requests to specific content servers can invoke the Web site analyzer program (described above) to retrieve 540 required Web content over the Internet.
  • the retrieved page content can be decomposed into its component parts using analysis functions within the Web site analyzer, and content components can be extracted as specified within the configuration file.
  • the customized configuration file (template) structure of Figure 14 is implemented as an XML file.
  • the tree structure illustrated is part of the Document Type Definition (DTD) of these XML templates and various nodes within the DTD tree structure are explained below.
  • DTD Document Type Definition
  • 'Web page analyzer' 807 - defines crawling properties, including a content server IP address 808 at which the template may be applied to Web content.
  • the analyzer node also specifies page content 809 to be crawled (i.e. portions or parts of the target page to be retrieved and stored, such as specific HTML elements to be discarded and elements to be retained, and whether original style tags should be retained or not).
  • an analyzer bean 810 which is a specific Java bean for extracting data from a source Web page.
  • the creation of a template for use to create and serve mini pages involves the following steps:
  • the contents included in the mini page must be specified within the XML configuration file, for example by specifying: URLs of original Web pages, whose contents will be used in the mini page; and, for each original Web page, a definition of which part(s) need to be included (the content components or "assets" of a Web page).
  • a component can be specified using an HTML element ID, or using the position in the
  • the cache is organized in two layers, comprising a first cache layer in volatile memory (e.g. RAM of the content server) forstoring frequently access mini pages and templates, and a second cache layer in non- volatile storage (e.g. disk storage) for less-frequently accessed mini pages and templates.
  • volatile memory e.g. RAM of the content server
  • non- volatile storage e.g. disk storage
  • the content access platform of the present embodiment also provides support for generation of mini pages using a default template, and support for the generation of new templates, in order to cater for new device types that become available in the future.
  • a requestor device type cannot be identified from a device model number within the HTTP header attributes or a received request, two options exist.
  • the HTTP header details are investigated more fully to identify characteristics of the requestor device type, and these characteristics are compared with the device capabilities information in the device profile database to identify similar device types.
  • a device type identifier corresponding to the best fit device type is then used to select a template that is likely to be suitable for the new device type.
  • this template is used to generate a suitable mini page for the requested Web page, and the mini page is returned to the device user, but this mini page can be returned with a user prompt asking for further details of the device type.
  • the content access platform makes use of resource compression and other transformations, to ensure that the size and format requirements of different devices (e.g. different mobile handset models) are matched by the mini pages that are served to those devices.
  • Figure 15 comprises an example table of multimedia resources and the compression and format transformations that are applied to them in one embodiment of the invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

Une plate-forme, des procédés et un appareil d'accès à un contenu permettent un meilleur accès à un contenu Internet pour des utilisateurs de dispositifs hétérogènes, tels que des téléphones mobiles et des assistants électroniques personnels. La plate-forme présente un mécanisme de distribution pour le contenu requis qui est adapté aux capacités du type de dispositif demandeur, à l'aide de mini-pages spécifiques au type de dispositif qui remplacent les pages Web d'origine et à l'aide de modèles mis en œuvre sous forme de fichiers de configuration XML pour générer les mini-pages. La plate-forme présente également un support pour les combinaisons personnalisées de contenu à fournir en fonction des exigences spécifiées dans les modèles stockés, de sorte que les fournisseurs de site Web et autres peuvent offrir une expérience utilisateur personnalisée aux différents utilisateurs en fonction de leurs préférences ou de leur type de dispositif. Les mini-pages sont générées en se référant à une analyse et à une catégorisation de la page ou du site Web d'origine ainsi qu'aux capacités des dispositifs demandeurs. L'invention concerne également des pages de répertoire compatibles avec le dispositif, en réponse à des demandes de répertoire comprenant un identifiant de type de dispositif pour s'assurer qu'une page de répertoire appropriée est fournie.
EP10708579A 2009-02-19 2010-02-19 Plate-forme d'accès à un contenu et procédés et appareil fournissant un accès à un contenu internet pour des dispositifs hétérogènes Withdrawn EP2399209A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GBGB0902834.1A GB0902834D0 (en) 2009-02-19 2009-02-19 Content access platform and methods and apparatus providing access to internet content for heterogeneous devices
PCT/GB2010/000295 WO2010094927A1 (fr) 2009-02-19 2010-02-19 Plate-forme d'accès à un contenu et procédés et appareil fournissant un accès à un contenu internet pour des dispositifs hétérogènes

Publications (1)

Publication Number Publication Date
EP2399209A1 true EP2399209A1 (fr) 2011-12-28

Family

ID=40565401

Family Applications (1)

Application Number Title Priority Date Filing Date
EP10708579A Withdrawn EP2399209A1 (fr) 2009-02-19 2010-02-19 Plate-forme d'accès à un contenu et procédés et appareil fournissant un accès à un contenu internet pour des dispositifs hétérogènes

Country Status (4)

Country Link
EP (1) EP2399209A1 (fr)
GB (1) GB0902834D0 (fr)
IL (1) IL214766A0 (fr)
WO (1) WO2010094927A1 (fr)

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011026223A1 (fr) * 2009-09-02 2011-03-10 Andrew Echenberg Distribution de contenu sur un réseau
GB2486393B (en) 2010-09-08 2016-12-28 Saffron Digital Ltd Delivering a file from a content provider to a client
GB2483655A (en) * 2010-09-14 2012-03-21 Thunderhead Ltd Device capability modelling and automatic content assembly
US8645491B2 (en) * 2010-12-18 2014-02-04 Qualcomm Incorporated Methods and apparatus for enabling a hybrid web and native application
CN102622381B (zh) * 2011-03-14 2013-11-13 小米科技有限责任公司 一种网页重排版的方法和系统
US8627204B2 (en) 2011-10-18 2014-01-07 Microsoft Corporation Custom optimization of web pages
US10346867B2 (en) 2012-06-11 2019-07-09 Retailmenot, Inc. Intents for offer-discovery systems
US9563713B2 (en) 2012-10-10 2017-02-07 Microsoft Technology Licensing, Llc Automatic mobile application redirection
CN102932452B (zh) * 2012-10-31 2015-11-25 北京奇虎科技有限公司 网站类型识别系统
US9386119B2 (en) 2013-07-30 2016-07-05 International Business Machines Corporation Mobile web adaptation techniques
US9967316B2 (en) 2014-01-30 2018-05-08 Google Llc Accessing media item referenced in application
US9450824B2 (en) 2014-02-04 2016-09-20 Wipro Limited Systems and methods for smart request processing
US20160344831A1 (en) * 2015-05-21 2016-11-24 Google Inc. Proxy service for content requests
CN110263238B (zh) * 2019-06-21 2021-10-15 浙江华坤道威数据科技有限公司 一种基于大数据的舆情聆听系统
CN110688530B (zh) * 2019-08-19 2022-04-26 天津开心生活科技有限公司 一种json数据的处理方法及装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020143821A1 (en) * 2000-12-15 2002-10-03 Douglas Jakubowski Site mining stylesheet generator
WO2002087135A2 (fr) 2001-04-25 2002-10-31 Novarra, Inc. Systeme et procede permettant d'adapter un contenu d'informations pour un dispositif electronique
US8181107B2 (en) 2006-12-08 2012-05-15 Bytemobile, Inc. Content adaptation

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO2010094927A1 *

Also Published As

Publication number Publication date
WO2010094927A1 (fr) 2010-08-26
GB0902834D0 (en) 2009-04-08
IL214766A0 (en) 2011-11-30

Similar Documents

Publication Publication Date Title
WO2010094927A1 (fr) Plate-forme d'accès à un contenu et procédés et appareil fournissant un accès à un contenu internet pour des dispositifs hétérogènes
US9686374B2 (en) System and method for fragment level dynamic content regeneration
KR100490734B1 (ko) 주석기반 문서 자동 생성장치 및 방법
US7353246B1 (en) System and method for enabling information associations
US7505978B2 (en) Aggregating content of disparate data types from disparate data sources for single point access
US7933917B2 (en) Personalized search method and system for enabling the method
US7996754B2 (en) Consolidated content management
US20090006338A1 (en) User created mobile content
US20070067305A1 (en) Display of search results on mobile device browser with background process
US20090083232A1 (en) Search results with search query suggestions
US20160234330A1 (en) System and method for mobile application deep linking
US20070208704A1 (en) Packaged mobile search results
US20070192674A1 (en) Publishing content through RSS feeds
US20070192683A1 (en) Synthesizing the content of disparate data types
WO2005104759A2 (fr) Systeme, procede et appareil de selection, affichage, gestion, suivi et transfert d'acces dans le contenu de pages web et d'autres sources
CN104025084B (zh) 历史浏览会话管理
KR20170038793A (ko) 동적 컨텐츠 및 스테일 컨텐츠를 포함하는 웹사이트들의 고속 렌더링
CN106528657A (zh) 浏览器跳转至应用程序的控制方法及装置
WO2008141424A1 (fr) Système et procédé de navigation de contenu
CN101681229A (zh) 输入候选提供装置、输入候选提供系统、输入候选提供方法以及输入候选提供程序
CN114528510A (zh) 网页数据处理的方法、装置、电子设备及介质
US20080172396A1 (en) Retrieving Dated Content From A Website
US10104196B2 (en) Method of and server for transmitting a personalized message to a user electronic device
US20080297521A1 (en) System and method for providing skins for a web page
RU2739720C2 (ru) Способ и сервер для передачи персонализированного сообщения на пользовательское электронное устройство

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20110915

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO SE SI SK SM TR

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN

18W Application withdrawn

Effective date: 20120412