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/9574—Browsing optimisation, e.g. caching or content distillation of access to content, e.g. by caching
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F15/00—Digital computers in general; Data processing equipment in general
  • G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
• • 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
• • 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
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F17/00—Digital computing or data processing equipment or methods, specially adapted for specific functions
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F40/00—Handling natural language data
  • G06F40/10—Text processing
  • G06F40/12—Use of codes for handling textual entities
  • G06F40/123—Storage facilities
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F40/00—Handling natural language data
  • G06F40/10—Text processing
  • G06F40/12—Use of codes for handling textual entities
  • G06F40/151—Transformation
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
  • G06Q50/10—Services

Definitions

• Productivity application programs such as word processing applications, spreadsheet applications, and presentation applications, enable users to create different types of documents. These documents may include data that is native to a particular document type and even to a particular application program. In order to view this native data, a user may view the document through the productivity application program that created the document. For example, a user may rely on a particular word processing application to view a word processing document that was created by the word processing application.
• a problem can arise when documents are shared across the World Wide Web (hereinafter referred to as "web") through web browsers.
• web World Wide Web
• typical web browsers may not be capable of reading a given document in its native format.
• a web server can be implemented to execute code that is capable of rendering a document from its native format into a web-compatible format that can be viewed through the web browser.
• An application server is provided for rendering documents and other content from a native document format into a web-compatible format capable of being viewed through a web browser or other suitable application.
• the application server includes a rendering module, which is operative to incrementally render documents. Through incremental rendering, the application server can provide portions of rendered documents to the web browser while the native documents are still being rendered.
• Other example implementations of the technologies described herein include converting a document from one format into another format (e.g., transforming a document from a binary file format into an Office Open XML format, a Portable Document Format ("PDF”), and the like).
• PDF Portable Document Format
• a download manager is also provided in order to increase the throughput of the rendering module.
• the download manager may begin retrieving other documents to be rendered at a later time. These other documents may be downloaded from a storage server and stored in a rendering queue on the application server. Once the rendering module becomes available, the rendering module can immediately begin rendering these other documents directly from the rendering queue without any downtime while waiting for documents to be retrieved.
• One or more caches are also provided in order to reduce the amount of work utilized to retrieve documents and other content. Examples of caches include a document cache, an authorization cache, and a location cache. The document cache may be operative to store rendered documents in the front end, thereby eliminating the need to retrieve the rendered documents from other storage units in the back end.
• the authorization cache may be operative to store authorization and authentication data, thereby eliminating the need to re-authorize or re-authenticate a user who later accesses the same document.
• the location cache may be operative to store the location of a rendered document. Through the use of the location cache, the rendered document can be efficiently retrieved from the relevant storage unit without the need to query multiple storage units.
• a method for rendering content for viewing through a web browser operating on a computer. Portions of the content are transformed into portions of rendered content. While the portions of the content are being transformed into portions of the rendered content, at least one of the portions of the rendered content can be provided to an application program.
• FIGURE 1 is a block diagram showing an illustrative system architecture operative to render documents for viewing through a web browser, in accordance with embodiments;
• FIGURE 2 is a block diagram showing an illustrative implementation of an application manager from the system architecture of FIGURE 1, in accordance with embodiments;
• FIGURE 3 is a block diagram showing an illustrative implementation of a front end from the system architecture of FIGURE 1, in accordance with embodiments;
• FIGURE 4A is a flow diagram showing an illustrative process for rendering content for viewing through a web browser, in accordance with embodiments;
• FIGURE 4B is a flow diagram showing an illustrative process for fetching a portion of the rendered content, in accordance with embodiments; and
• FIGURE 5 is a computer architecture diagram showing an illustrative computer hardware architecture for a computing system capable of implementing the embodiments presented herein.
• an application server is provided that is operative to incrementally render a document or other content from its native format into another format, such as a web- compatible format.
• another format such as a web- compatible format.
• pre-rendering as content is being incrementally rendered, each discrete portion of the document or other content that has been rendered can be made available to the user.
• One or more caches may also be provided in order to reduce the amount of work utilized to retrieve rendered content.
• Embodiments described herein may refer to pages and slides as discrete portions of documents and rendered documents. However, it should be appreciated that pages and slides are merely examples of discrete portions and are not intended to be limiting. Other kinds of discrete portions, as contemplated by those skilled in the art, may be similarly implemented.
• embodiments described herein primarily refer to documents and document rendering. However, it should be appreciated that the embodiments described herein may be similarly applied to any suitable content which can be rendered from a native format into another format. Such content may include any multimedia, such as text, images, audio, video, and combinations thereof. Further, embodiments described herein primarily refer to the rendered format as a web-compatible format capable of being viewed through a web browser. However, it should be appreciated that the rendered format may be other suitable formats as contemplated by those skilled in the art.
• program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types.
• program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types.
• program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types.
• the subject matter described herein may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor- based or programmable consumer electronics, minicomputers, mainframe computers, and the like.
• FIGURE 1 is a block diagram showing a system architecture 100 operative to render documents and to retrieve rendered documents according to embodiments.
• the architecture 100 includes a front end 102 that is operative to communicate with a computer 104.
• the front end 102 may receive and process requests from a web browser 106 over a network 108, such as the Internet.
• the front end 102 may receive a Hypertext Transfer Protocol ("HTTP") message with a request for a specific document, such as document HOA, stored in a document store 112.
• HTTP Hypertext Transfer Protocol
• the components of the architecture 100 may reside on the same server, according to further embodiments. Splitting the architecture 100 into the front ends and application servers is merely an implementation design choice and is not intended to be limiting.
• the web front end 102 may attempt to retrieve, from an output store 114, a web-compatible rendered document HOB corresponding to the requested document HOA.
• the rendered document HOB may be stored in the output store 114 if the document 11OA was recently rendered. If the output store 114 contains the rendered document HOB corresponding to the document 11OA, then the output store 114 may return the rendered document 11OB to the front end 102.
• the application server 116 may retrieve the document 11OA from the document store 112.
• a rendering module 118 in the application server 116 is operative to render (i.e., convert, transform) the document 11OA into the rendered document HOB.
• the rendering module 118 may generate the rendered document 11OB in any format capable of being displayed by a suitable web browser.
• Example formats may include an image format (e.g., Portable Network Graphics ("PNG”), Joint Photographic Experts Group (“JPEG”), etc.),
• the rendering module 118 may also generate the rendered document HOB into a web-ready rendition that may include Extensible Markup Language (“XML”), scripts, Hypertext Markup Language (“HTML”), images, and/or the like, such that individual data types in the web-ready rendition can be understood collectively by the web browser. Each of these data types may be made available to the user upon being generated by the incremental rendering process described herein.
• the rendering module 118 may also be operative to concurrently render multiple documents.
• the application server 116 may store the rendered document 11OB in the output store 114 and return the rendered document 11OB to the front end 102.
• the front end 102 may respond to the HTTP request by providing the rendered document 11OB to the web browser 106 via the HTTP protocol.
• the web browser 106 can then display the rendered document HOB, which is a full-fidelity representation of the corresponding document 11OA.
• the full- fidelity representation contains the same formatting (e.g., layout, resolution, content, etc.) found in the original representation.
• the full-fidelity representation can be contrasted against a lower- fidelity representation in which, for example, the layout may be changed or the resolution and content may be reduced.
• the rendered document HOB may be utilized for non-viewing scenarios, such as converting binary files to another document type for editing.
• a MICROSOFT OFFICE binary file may be rendered into an OPEN OFFICE EXTENSIBLE MARKUP LANGUAGE ("OOXML”) file.
• the architecture 100 may include additional front ends and/or additional application servers. Further, multiple front ends and/or multiple application servers may reside on the same server. For example, additional front ends may be utilized to handle a greater quantity of requests from web browsers. In one embodiment, the additional application servers are deployed to handle the rendering of heavier loads. In another embodiment, additional application servers are deployed to render different types of documents. For example, one application server may be dedicated to rendering word processing documents, while another application server may be dedicated to rendering presentations. In yet another embodiment, additional application servers are deployed to render different elements of a given document.
• the rendered elements can then be combined to create the rendered document.
• one application server may render video in a presentation, while another application server may render the text in the presentation.
• the front end 102 may be operative to combine the results of the two application servers to form the rendered presentation.
• the front end 102 in response to a single request to render a document in a given format, the front end 102 may direct the application server 116 to render the document into multiple formats in order to support multiple uses across multiple device types and web client configurations.
• the web browser 106 may request from the front end 102 a given document rendered in ADOBE FLASH.
• the front end 102 may determine, through a user profile associated with the user operating the web browser 106, that the user frequently accesses documents in ADOBE FLASH, MICROSOFT SILVERLIGHT, Portable Network Graphics ("PNG”), mobile, and full versions.
• the front end 102 may also determine, through the user profile that the user frequently accesses documents in a web-ready rendition including a combination of XML, scripts, HTML, images, and/or the like. In this case, the front end 102 may fulfill the request by rendering the document in one or more of these versions.
• Other suitable data may be similarly utilized to determine whether the front end 102 directs the application server 116 to render a document into multiple formats in response to a single render request.
• the application server 116 further includes an application manager 120.
• the application manager 120 is operative to manage incremental rendering of the document HOA into the rendered document HOB.
• incremental rendering refers to providing portions of the rendered document 11OB as the document 11OA is being rendered by the rendering module 118.
• the rendered first page of a word processing document or a rendered first slide of a presentation may be provided to the front end 102, which can then provide the rendered first page or the rendered first slide to the web browser 106 for display.
• Other embodiments may render any particular page or slide in the document. Other embodiments may also render other portions of content besides pages or slides. As the remainder of the word processing document or presentation is being rendered by the rendering module 118, the application manager 120 may provide the additional rendered pages and rendered slides to the web browser 106.
• the application manager 120 may make available portions of the rendered document 11OB as the document 11OA is being rendered by the rendering module 118.
• the front end 102 can then retrieve these portions of the rendered document 11OB, as necessary, from the application server 116.
• the portions of the rendered document HOB are stored in a backend cache 122 in the application server 116.
• the pages or slides of a document may be rendered in any predefined order. The rendered pages or slides are then made available to the front end 102 in the same order as they were rendered.
• the documents are rendered from the beginning of the document to the end of the document.
• incremental rendering reduces the amount of rendering time before a user can view a portion, such as the beginning or some other portion, of the document. For example, in conventional pre-rendering, a user desiring to view a first page of a word processing document or a first slide of a presentation would need to wait until the entire word processing document or presentation is rendered. In an illustrative implementation of incremental rendering, the user can more quickly view the first page or the first slide prior to the remainder of the word processing document or the presentation being rendered.
• the user may request a page N or a slide N of a document where the variable N represents any page or slide within the document.
• the request may occur prior to or while the document is being rendered.
• the application manager 120 may direct the rendering module 118 to render the page N or the slide N by seeking the particular page or slide within the document.
• the rendered page N or slide N can then be made available to the front end 102.
• the application manager 120 may proceed with rendering the remainder of the document.
• the rendering module 118 is operative to incrementally render a document even when the document has yet to be fully downloaded. That is, the rendering module 118 may begin rendering the document while it is being downloaded from the document store 112, rather than wait until the entire file has been downloaded. This approach to rendering a document before it has fully downloaded may reduce the amount of time it takes for the rendering module 118 to render a document, especially if the document is relatively large.
• FIGURE 2 is a block diagram showing the application manager 120 according to embodiments.
• the application manager 120 includes a download manager 202 and a rendering queue 204.
• the download manager 202 is operative to download documents from the document store 112 prior to the rendering module 118 rendering the documents.
• the download manager 202 may then store the downloaded documents in the rendering queue 204 until the rendering module 118 is available to render the documents.
• the rendering queue 204 may operate without the download manager 202.
• the download manager 202 may be utilized to speed processing through the rendering queue 204. Further, even when the download manager 202 is present, the rendering queue 204 may operate independently of the download manager 202 to handle instances when the application manager 120 is overloaded.
• the download manager 202 may download the first document 206A from the document store 112, and the rendering module 118 may begin rendering the first document 206A.
• the download manager 202 may concurrently download the second document 206B from the document store 112 and store the second document 206B in the rendering queue 204.
• the rendering module 118 can then immediately proceed to rendering the second document 206B from the rendering queue 204 without waiting for the second document 206B to be downloaded.
• the rendering queue 204 may be configured to store any number of documents, as contemplated by those skilled in the art.
• the download manager 202 may be configured by a user to adjust the number of documents being downloaded simultaneously and the maximum number of documents stored in the rendering queue 204 that are awaiting rendering. In this way, the user can ensure that the number of documents being downloaded and/or stored at any given time does not place an excessive burden on system resources.
• FIGURE 3 is a block diagram showing the front end 102 according to embodiments.
• the front end 102 includes a request merge module 302 and several caches 304, including a document cache 304A, an authorization cache 304B, and a location cache 304C.
• the request merge module 302 maintains tracking data identifying a particular application server that is currently rendering a given document.
• the request merge module 302 may utilize this tracking data to direct additional requests for the same document to the same application server. By directing additional requests for the same document to the same application server, redundant work between application servers is reduced, and other application servers are free to render other documents.
• the system architecture 100 of FIGURE 1 may include multiple front ends and multiple application servers. These front ends may or may not be capable of communicating with each other.
• the request merge module 302 may be configured to perform consistent hashing in order to identify a particular application server for a particular document request.
• consistent hashing one or more aspects of a given document request may be analyzed in order to map these aspects to a particular application server.
• An example of an aspect of a document request is the name of the document being requested.
• the caches 304 may improve performance of the front end 102 by reducing the need for the front end 102 to access other parts of the system architecture 100, such as the output store 114 and the application server 116.
• the document cache 304 A is operative to cache at least portions of rendered documents according to popularity.
• the authorization cache 304B is operative to store authorization or authentication information associated with users. Access to the documents and the rendered documents may be restricted based on an authorization process whereby a user enters identification information, such as a username and password. For example, when a user attempts to access a particular document, the front end 102 may access an authorization module (not shown), which requests information, such as a login identifier and password, identifying the user. The authorization module may then determine whether the user has permission to access the document. The authorization module may be configured to permit access to the document only when the authorization module verifies that the user has permission.
• the authorization cache 304B may store state information indicating that the user has been verified.
• the front end 102 may utilize this state information to verify that the user has or does not have permission to access the document without the need for accessing the authorization module. In this way, the front end 102 is not required to send credentials to an remote authorization service, thereby optimizing performance of the front end 102. Further, the user does not have to re-enter identification information for additional requests to access the same document.
• the state information stored in the authorization cache 304B may be particularly useful when a user requests only a portion of a given document at a time. For example, a user may initially request only a first page of a multi-page document.
• the user may be required to enter identification information (i.e., credentials) in order to view the first page. If the user subsequently requests additional pages of the document, the front end 102 can expeditiously authorize the user based on the credentials stored in the authorization cache 304B. Thus, each authentication of the user does not necessarily result in the user being prompted for credentials. Further, the need to re-query other servers to authenticate and authorize the user can be eliminated.
• the authorization cache 304B may be configured to store the state information for any amount of time after which the state information may be deleted.
• the location cache 304C which may also be referred to as a "dictionary", is operative to store the location of a given rendered document.
• the location cache 304C may indicate the particular storage unit that stores a particular rendered document.
• Examples of storage units may include the output store 114 and the backend cache 122.
• the storage units may be part of the system architecture 100 or separate from the system architecture 100.
• FIGURE 4A is a flow diagram illustrating one method for rendering content for viewing through a web browser operating on a computer.
• FIGURE 4B is a flow diagram illustrating one method for fetching a rendered portion of the content. The method of FIGURE 4B may be performed concurrently or after the method of FIGURE 4A is performed.
• the logical operations described herein are implemented (1) as a sequence of computer implemented acts or program modules running on a computing system and/or (2) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance and other requirements of the computing system.
• a routine 400 begins at operation 402, where the front end 102 receives a request from the web browser 106 for a document, such as the document HOA. The routine 400 then proceeds to operation 404, where the front end 102 directs the rendering module 118 to begin incrementally rendering the document HOA.
• the rendering module 118 may retrieve the document 11OA from the document store 112. Upon retrieving the document 11OA from the document store 112, the rendering module 118 may render the first page or the first slide of the document 11OA. In some embodiments, the request may specify a particular slide or page of the document 11OA. In this case, the rendering module 118 may render the particular page or the particular slide instead of the first page or the first slide. Upon generating the first page or the first slide of the rendered document HOB, the routine proceeds to operation 406. [0045] At operation 406, the rendering module 118 determines whether the document
• a routine 400B begins at operation 408, where the front end 102 receives a request from the web browser 106 for a document, such as the document 11OA. The routine 400B then proceeds to operation 410, where as pages or slides of the rendered document HOB are rendered by the rendering module 118, the application manager 120 may make available these pages or slides of the rendered document 11OB to the front end 102.
• the application manager 120 may also make available that particular page or particular slide.
• the rendering module 118 may make available the pages or slides of the rendered document HOB through the backend cache 122.
• the front end 102 may then retrieve the pages or slides of the rendered document HOB from the backend cache 122 and transmit the pages or slides of the rendered document 11OB to the web browser 106 for display.
• the routine 400B may be performed while the document 11OA is being incrementally rendered according to the routine 400A. That is, while the rendering module 118 is rendering pages or slides of the document 11OA according to routine 400A, the application manager 120 may fulfill requests for those rendered pages or slides according to routine 400B.
• the front end 102 can continue to retrieve the additional pages or slides of the rendered document HOB without waiting for the entire rendered document 11OB to be generated. Further, while the application manager 120 is fulfilling requests for pages or slides of the rendered document HOB, the rendering module 118 may continue to render additional pages or slides from the document 11OA.
• additional requests for other documents may be received by the front end 102.
• the download manager 202 may retrieve the other documents from the document store 112 and store the documents in the rendering queue 204 while the rendering module 118 is still rendering the document 11OA.
• the rendering module 118 can begin rendering these other documents without waiting for them to be retrieved from document store 112.
• additional requests for the document 11OA may be directed to the same application server 116. In this way, other application servers can be available to render other documents. Further, according to some embodiments, the rendering module 118 may render the document 11OA into multiple formats in response to a single request.
• the computer 500 includes a processing unit 502 ("CPU"), a system memory 504, and a system bus 506 that couples the memory 504 to the CPU 502.
• the computer 500 further includes a mass storage device 512 for storing one or more program modules 514, such as the rendering module 118, and one or more databases 516, such as the document store 112.
• Other program modules 514 may include the web browser 106, the download manager 202, and the request merge module 302.
• Other databases 516 may include the output store 114, the rendering queue 204, and the caches 304.
• the mass storage device 512 is connected to the CPU 502 through a mass storage controller (not shown) connected to the bus 506.
• the mass storage device 512 and its associated computer-readable media provide non-volatile storage for the computer 500.
• computer-readable media can be any available computer storage media that can be accessed by the computer 500.
• computer-readable media may include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data.
• computer-readable media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, digital versatile disks ("DVD”), HD-DVD, BLU-RAY, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer 500.
• the computer 500 may operate in a networked environment using logical connections to remote computers through a network, such as the network 108.
• the computer 500 may connect to the network 108 through a network interface unit 510 connected to the bus 506.
• the network interface unit 510 may also be utilized to connect to other types of networks and remote computer systems.
• the computer 500 may also include an input/output controller 508 for receiving and processing input from a number of input devices (not shown), including a keyboard, a mouse, a microphone, and a game controller. Similarly, the input/output controller 508 may provide output to a display or other type of output device (not shown).

Landscapes

• Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Databases & Information Systems (AREA)
• General Engineering & Computer Science (AREA)
• Data Mining & Analysis (AREA)
• Health & Medical Sciences (AREA)
• General Health & Medical Sciences (AREA)
• Artificial Intelligence (AREA)
• Audiology, Speech & Language Pathology (AREA)
• Computational Linguistics (AREA)
• Business, Economics & Management (AREA)
• Software Systems (AREA)
• Computer Hardware Design (AREA)
• Tourism & Hospitality (AREA)
• General Business, Economics & Management (AREA)
• Human Resources & Organizations (AREA)
• Marketing (AREA)
• Primary Health Care (AREA)
• Strategic Management (AREA)
• Economics (AREA)
• Mathematical Physics (AREA)
• Information Transfer Between Computers (AREA)
• Digital Computer Display Output (AREA)
• Image Generation (AREA)
• Processing Or Creating Images (AREA)
• Auxiliary Devices For Music (AREA)
• Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Priority Applications (11)

Applications Claiming Priority (2)

Publications (2)

Family

ID=42679330

Family Applications (1)

Country Status (17)

Families Citing this family (41)

Family Cites Families (69)

• 2009
  • 2009-03-04 US US12/397,351 patent/US8347208B2/en not_active Expired - Fee Related
• 2010
  • 2010-02-05 TW TW099103550A patent/TWI493441B/zh not_active IP Right Cessation
  • 2010-02-26 CA CA2749683A patent/CA2749683C/en active Active
  • 2010-02-26 AU AU2010221620A patent/AU2010221620B2/en not_active Ceased
  • 2010-02-26 SG SG2011050549A patent/SG172952A1/en unknown
  • 2010-02-26 BR BRPI1007813A patent/BRPI1007813A2/pt not_active Application Discontinuation
  • 2010-02-26 CN CN201080010824.7A patent/CN102341823B/zh active Active
  • 2010-02-26 MX MX2011009158A patent/MX2011009158A/es active IP Right Grant
  • 2010-02-26 KR KR1020117020549A patent/KR101626639B1/ko active Active
  • 2010-02-26 MY MYPI2011003913A patent/MY163751A/en unknown
  • 2010-02-26 RU RU2011136691/08A patent/RU2571512C2/ru active
  • 2010-02-26 WO PCT/US2010/025678 patent/WO2010101790A2/en not_active Ceased
  • 2010-02-26 JP JP2011552998A patent/JP5537571B2/ja active Active
  • 2010-02-26 EP EP10749134.2A patent/EP2404276A4/en not_active Ceased
• 2011
  • 2011-07-13 IL IL214057A patent/IL214057A/en active IP Right Grant
  • 2011-07-14 ZA ZA2011/05214A patent/ZA201105214B/en unknown
  • 2011-08-26 CL CL2011002084A patent/CL2011002084A1/es unknown
• 2012
  • 2012-09-07 US US13/606,704 patent/US20120331377A1/en not_active Abandoned

Also Published As

Similar Documents

Legal Events