Source: http://www.google.com/patents/US20060031411?dq=6,208,537
Timestamp: 2017-06-26 22:40:45
Document Index: 96172348

Matched Legal Cases: ['arts 44', 'arts 44', 'art 1', 'arts 44', 'art3', 'art3', 'art3', 'art3', 'art3', 'art3', 'art3', 'art3', 'art3', 'art3', 'art3', 'art1']

Patent US20060031411 - Document delivery - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsA server has a memory 16 arranged to have a document 17 having a number of parts stored in it. The server is arranged to: receive a request including a URI having a document identifier which identifies both the whole and a part of the document; determine capabilities of the device; and deliver an appropriate...http://www.google.com/patents/US20060031411?utm_source=gb-gplus-sharePatent US20060031411 - Document deliveryAdvanced Patent SearchTry the new Google Patents, with machine-classified Google Scholar results, and Japanese and South Korean patents.Publication numberUS20060031411 A1Publication typeApplicationApplication numberUS 11/059,339Publication dateFeb 9, 2006Filing dateFeb 17, 2005Priority dateJul 10, 2004Also published asUS7555564Publication number059339, 11059339, US 2006/0031411 A1, US 2006/031411 A1, US 20060031411 A1, US 20060031411A1, US 2006031411 A1, US 2006031411A1, US-A1-20060031411, US-A1-2006031411, US2006/0031411A1, US2006/031411A1, US20060031411 A1, US20060031411A1, US2006031411 A1, US2006031411A1InventorsRoger Gimson, Stuart WilliamsOriginal AssigneeHewlett-Packard Development Company, L.P.Export CitationBiBTeX, EndNote, RefManPatent Citations (16), Referenced by (103), Classifications (6), Legal Events (4) External Links: USPTO, USPTO Assignment, EspacenetDocument delivery
[0025] Referring to FIG. 4, an internet based system for storing and downloading documents comprises a server 10 connected to the internet 11, a small screen user device, in this case a PDA 12, and a large screen user device, in this case a PC 14. The user devices 12, 14 have wireless internet connections, and the server 10 has a wired internet connection. [0026] Referring to FIG. 5 a, the server 10 comprises a memory 16, a processor 18 and an input/output device 20. The memory 16 is arranged to store documents 17, and the processor 18 is arranged to receive requests for delivery of documents 17 over the internet via the I/O device 20, to interpret those requests, and to control the delivery of documents from the memory over the internet via the I/O device 20. Referring to FIG. 5 b, the pocket PC 12 comprises a memory 22, processor 21, and I/O devices generally indicated at 22 which are linked to the screen 23, input buttons 24, both of which act as user inputs, and an RF transceiver 25. The screen 23 is a touch screen arranged to detect user inputs made using a stylus 26. The pocket PC runs various software packages including a browser package. As shown in FIG. 5 c the PC 14 comprises a memory 27, processor 28, and I/O devices generally indicated as 29 which are linked to the PC screen 30, a keyboard 31 and mouse 32 which act as user inputs, and an RF transceiver 33. The PC also runs various software packages including a browser package. The RF transceivers 25, 33 are arranged to be in contact with internet access points to provide internet access to the pocket PC 12 and the PC 14. [0027] Referring to FIGS. 6 to 10, a document called ‘example’ is stored in the memory 16 of the server. The document is stored in two formats, that is as a complete document including all of its four parts, suitable for delivery to a large screen device, and as four separate parts, each of which is suitable for delivery to a small screen device. Referring specifically to FIG. 6, the HTML source of the complete document comprises a title 40 which in this case is ‘Example document’, and a document body 42 that is divided into four parts 44, 46, 48, 50. Each of the parts 44, 46, 48, 50 includes a name 52, for example ‘part 1’ for the first part, and a body 54 comprising the main text or other content of the document. The beginning and end of the whole document body 42 are marked by HTML tags 55. The source document also includes a number of links, 56 at the top of the document to the various parts 44, 46, 48, 50. These links are in the form ‘example!partn#partn’, where n is 1 to 4 for each of the respective parts. This copy of the whole document is stored as a file named ‘example’ on the server 10 at a location ‘/B/ . . . ’ and can therefore be located by a URL of the form ‘http://A/B/ . . . /example’, where ‘http://A’ identifies the server 10. [0028] Referring specifically to FIGS. 7 to 10, the document is also stored on the server in separate parts suitable for delivery to a small screen device such as the PDA 12. Each of these part sources comprises the title of the document 60, the name 62 of the part in the form ‘partn’ where n is 1, 2, 3 or 4, and the body 64 of the part. The beginning and end of each part is marked by an HTML tag 65. The source for each part also includes links to each of the other parts in the format ‘example!partn#partn’, where n is 1 to 4 for each of the respective parts. [0029] The server stores the document parts with file names ‘example.partn’ at the same location in its memory as the whole document, in this case at location ‘/B/ . . .’. Each document part can therefore be located using a URL of the format ‘http://A/B/ . . . /example!partn’, which can be mapped by the server onto the corresponding file name. Different mappings may be used on the server to allow the name used in the URL to be syntactically different from the local file name, so that each can be separately chosen if necessary. The identity mapping, in which the URL name is identical to the file name could also be used. [0030] Links to document parts, such as those used in the index 56, take the form ‘example!partn#partn’ Here the suffix after the separator ! and the fragment identifier after the separator # are both the same, and both identify the document part, and ‘example’ is the document name. This means that each part of the document has a full URL in the format ‘http://A/B/ . . . /example!partn#partn’, where ‘//A’ identifies the server 10, ‘/B/ . . . ’ identifies the document relative to the server, ‘example’ is the name of the document and ‘partn’ identifies the part of the document, with n being 1 to 4 for each of the respective parts. The whole document has a URL ‘http://A/B/ . . . /example’. [0031] The server 10 is arranged to receive requests for either the whole of the document ‘example’ or parts of it, to determine from the request the display capabilities of the user device making each request, and to respond by delivering either the whole document, using the source of FIG. 6, or a part of the document using the source of one of FIGS. 7 to 10. In particular the server is arranged to receive requests including a URL in the format ‘http://A/B/ . . . /example!partn’ where ‘//A’ identifies the server 10, ‘/B/ . . . ’ identifies the document relative to the server, ‘example’ is the name of the whole document and ‘partn’ identifies a part of the document, with n being 1 to 4 for each of the respective parts. It will be noted that this is the format in which the links are embedded in the document source as shown in FIGS. 6 to 10, except that it does not include the fragment identifier that is present in the links. The HTTP server protocol strips the fragment identifiers from the operation request line so that they are not communicated to the origin server. [0032] The server is therefore arranged to interpret the URL in requests of this format in different ways, depending on the capabilities of the user device that makes the request, and in particular on whether it is suitable to display the whole document of only part of it. [0033] In particular the server 10 is arranged to interpret a component of a URL in a document request of the form ‘example!partn’ as referring to the document ‘example.partn’ for a Pocket PC and as ‘example’ for any other user device. This is done by the well-known technique of identifying a particular character string in the HTTP user agent string forming part of the header of the request from the user device to the server. FIG. 11 shows code arranged to configure an Apache web server to recognise a Pocket PC from the substring “Windows CE” in the user agent string, and FIG. 12 shows an example of a user agent string from the Pocket PC 12. The result of this is that if a request for a document part is received by the server in the format ‘http://A/B/ . . . /example!partn’, then, if the request comes from a Pocket PC, the server will interpret this as a request for the document ‘example.partn’, and deliver the source of just the requested document part, ‘example.partn’, as shown in FIGS. 7 to 10. On the other hand, if the request comes from any other user device, the server 10 will interpret the request as a request for the document ‘example’, i.e. the whole document, and deliver the whole of the document ‘example’. [0034] It will be appreciated that other methods of determining the display capabilities, or other relevant capabilities, of the user device could also be used. For example mobile devices may use UAProf (User Agent Profile), as defined by the Open Mobile Alliance. [0035] Referring to FIGS. 13 and 14, if the web browser on the PC 14 is used to request a copy of the document ‘example’ from the server 10, then this could be done using the URL ‘http://A/B/ . . . /example’, or by using the URL or any of its parts. If such a request is sent to the server 10 from the PC 14, then the server checks the user agent string and determines that the user agent is not a Pocket PC, and sends the source for the whole of the document, as illustrated in FIG. 6, to the PC 14, together with a header that contains the URL of the whole document. The URL is then displayed on the address bar 60 on the PC screen, while the various parts of the document are also displayed on the PC screen. If the user moves about the document using the links 56, the browser will make the appropriate part of the document visible and show its full URL as shown in FIG. 14. For example if the top of the document is displayed as shown in FIG. 13, and the user clicks on the link 56 for the third part, using user inputs 31, 32, then the browser will display a different part of the document including the third part, as shown in FIG. 14. This is possible because a fragment identifier #partn is associated with each part of the document, and the browser is configured to interpret fragment identifiers in this way to move between different parts or fragments of a document using the fragment identifiers. [0036] If, while viewing the document, the user wants to bookmark the current view, the browser saves the bookmark in the full URL format, for example ‘http://A/B/ . . . /example!part3#part3’ if the third part of the document is currently being viewed. [0037] If subsequently the browser on the PC 14 is used to retrieve the document using the bookmarked URL ‘http://A/B/ . . . /example!part3#part3’, then the browser is arranged to send a request to the server 10 containing the URL in the format ‘http://A/B/ . . . /example!part3’, having first removed the fragment identifier. The server 10 identifies this as referring to the document ‘example’ that can be delivered complete or in parts, checks the user agent string in the request from the PC, determines from the string that the PC is not a Pocket PC, and interprets the request be for the whole document ‘example’. The ‘part3’ component of the URL is treated as being redundant, and the server therefore delivers the document at http://A/B/ . . . /example, i.e. the whole document ‘example’ including all four parts. When this document is received by the browser, the browser uses the original fragment identifier to select which part to display. In this case as the original request was for the fragment #part3, the browser selects the third part of the document and positions the document in the display as shown in FIG. 14. [0038] Referring to FIG. 15, if the browser on the Pocket PC 12 sends a request to the server 10 for the document ‘example’ using the bookmarked URL ‘http://A/B/ . . . /example!part3#part3’, then the server 10 again receives this request including the URL ‘http://A/B/ . . . /example!part3’, checks the user agent string in the request, identifies the requesting user device as a Pocket PC, and interprets the request as being for delivery of the document at ‘http://A/B/ . . . /example.part3’, and delivers the source for the third part of the document as shown in FIG. 9. This is then displayed on the screen 23 of the Pocket PC 12 in the form shown in FIG. 17. [0039] If the browser on the Pocket PC 12 sends a request to the server 10 including a URL of the format ‘http://A/B/ . . . /example’, then the server 10 determines from the user agent string of the request that the request is from a Pocket PC. Since no part of the document is identified in the request, the server is arranged to interpret this as a request for the first part of the document, and therefore delivers the document ‘example.part1’ i.e. the first part of the requested document. The server rules shown in FIG. 11 do not specifically support this behaviour, but it will be appreciated that they can be modified to do so. This ensures that the whole document ‘example’ is not sent to the Pocket PC 12, which could overload its presentation capabilities. Since this part of the document as delivered includes links to the other parts of the document, the user can easily request other parts of the document as necessary. [0040] In a modification to the system described above the server can be arranged to deliver the document at three or more levels of granularity. For example for a large screen PC, the server can deliver the whole document, for a PDA or similar device, the server can deliver more than one of the parts, but not the whole document, and for a mobile phone or similar device with a very small screen, the server can deliver just one part of the document. The mechanisms for achieving this would be the same as described above, but with the server arranged to provide the extra level(s) of granularity selection. [0041] In a further modification, the server is arranged to have the document stored in only one format, either as a single file having the complete document in it, or as separate files each having a respective part of the document in it. The server can then be arranged to actively modify the stored document if required on receipt of a request, either to extract a part of the whole document for a small screen device, or to combine the parts into a single document for a large screen device. Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS6476833 *Mar 30, 1999Nov 5, 2002Koninklijke Philips Electronics N.V.Method and apparatus for controlling browser functionality in the context of an applicationUS6665659 *Feb 1, 2000Dec 16, 2003James D. LoganMethods and apparatus for distributing and using metadata via the internetUS6956308 *Jul 15, 2003Oct 18, 2005Nikon CorporationDual flow circulation system for a moverUS6970869 *Aug 31, 2000Nov 29, 2005Sun Microsystems, Inc.Method and apparatus to discover services and negotiate capabilitiesUS7200585 *Sep 11, 2003Apr 3, 2007Ntt Docomo, Inc.Identifier generating method, identity determining method, identifier transmitting method, identifier generating apparatus, identity determining apparatus, and identifier transmitting apparatusUS7337910 *Oct 4, 2001Mar 4, 2008Verisign, Inc.Methods and devices for responding to request for unregistered domain name to indicate a predefined type of serviceUS20010034771 *Jan 12, 2001Oct 25, 2001Sun Microsystems, Inc.Network portal system and methodsUS20020055915 *Feb 28, 2001May 9, 2002Greg ZhangSystem and method for high speed string matchingUS20020062398 *Nov 18, 2001May 23, 2002William Ho ChangController for mobile and pervasive outputUS20020138649 *Oct 4, 2001Sep 26, 2002Brian CartmellProviding services and information based on a request that includes a unique identifierUS20030158969 *Jan 23, 2003Aug 21, 2003Gimson Roger BrianAuthoring of media content and dissemination via an information technology networkUS20040024867 *Oct 28, 2002Feb 5, 2004Openwave Systems Inc.Method and apparatus for determination of device capabilities on a networkUS20040221079 *May 27, 2004Nov 4, 2004Microsoft CorporationMethod and system for locking multiple resources in a distributed environmentUS20040249951 *Apr 8, 2003Dec 9, 20043Com CorporationMethod and system for providing directory based servicesUS20050060381 *Oct 26, 2004Mar 17, 2005H2F Media, Inc.Adaptive electronic messagingUS20060020631 *Jul 15, 2005Jan 26, 2006Canon Kabushiki KaishaMethod for evaluating xpath-like fragment identifiers of audio-visual content* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS7865827 *Sep 29, 2006Jan 4, 2011Brainloop AgMethod for operating a data processing systemUS7920101Sep 22, 2005Apr 5, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device display standardizationUS7934217Jul 29, 2005Apr 26, 2011Sharp Laboratories Of America, Inc.Methods and systems for providing remote file structure access to an imaging deviceUS7941743Aug 18, 2006May 10, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device form field managementUS7969596Oct 8, 2004Jun 28, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device document translationUS7970813Sep 30, 2005Jun 28, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device event notification administration and subscriptionUS7978618Nov 21, 2006Jul 12, 2011Sharp Laboratories Of America, Inc.Methods and systems for user interface customizationUS8001183Sep 30, 2005Aug 16, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device related event notificationUS8001586Jul 29, 2005Aug 16, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential management and authenticationUS8001587Jul 29, 2005Aug 16, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential managementUS8006176Oct 21, 2005Aug 23, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging-device-based form field managementUS8006292Jul 29, 2005Aug 23, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential submission and consolidationUS8006293Jul 29, 2005Aug 23, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential acceptanceUS8015234Sep 30, 2005Sep 6, 2011Sharp Laboratories Of America, Inc.Methods and systems for administering imaging device notification access controlUS8018610Oct 8, 2004Sep 13, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device remote application interactionUS8023130Jul 29, 2005Sep 20, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device accounting data maintenanceUS8024792Jul 29, 2005Sep 20, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential submissionUS8032579Sep 30, 2005Oct 4, 2011Sharp Laboratories Of America, Inc.Methods and systems for obtaining imaging device notification access controlUS8032608Sep 30, 2005Oct 4, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device notification access controlUS8035831Oct 8, 2004Oct 11, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device remote form managementUS8049677Sep 22, 2005Nov 1, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device display element localizationUS8051125Sep 30, 2005Nov 1, 2011Sharp Laboratories Of America, Inc.Methods and systems for obtaining imaging device event notification subscriptionUS8051140Oct 21, 2005Nov 1, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device controlUS8060921Jul 29, 2005Nov 15, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential authentication and communicationUS8060930Jul 29, 2005Nov 15, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential receipt and authenticationUS8065384Sep 30, 2005Nov 22, 2011Sharp Laboratories Of America, Inc.Methods and systems for imaging device event notification subscriptionUS8106922Aug 18, 2006Jan 31, 2012Sharp Laboratories Of America, Inc.Methods and systems for imaging device data displayUS8115944Jul 29, 2005Feb 14, 2012Sharp Laboratories Of America, Inc.Methods and systems for local configuration-based imaging device accountingUS8115945Aug 31, 2005Feb 14, 2012Sharp Laboratories Of America, Inc.Methods and systems for imaging device job configuration managementUS8115946Aug 31, 2005Feb 14, 2012Sharp Laboratories Of America, Inc.Methods and sytems for imaging device job definitionUS8115947Sep 30, 2005Feb 14, 2012Sharp Laboratories Of America, Inc.Methods and systems for providing remote, descriptor-related data to an imaging deviceUS8120793Jul 29, 2005Feb 21, 2012Sharp Laboratories Of America, Inc.Methods and systems for displaying content on an imaging deviceUS8120797Jul 29, 2005Feb 21, 2012Sharp Laboratories Of America, Inc.Methods and systems for transmitting content to an imaging deviceUS8120798Sep 30, 2005Feb 21, 2012Sharp Laboratories Of America, Inc.Methods and systems for providing access to remote, descriptor-related data at an imaging deviceUS8120799Sep 30, 2005Feb 21, 2012Sharp Laboratories Of America, Inc.Methods and systems for accessing remote, descriptor-related data at an imaging deviceUS8125666Oct 8, 2004Feb 28, 2012Sharp Laboratories Of America, Inc.Methods and systems for imaging device document managementUS8156424Sep 22, 2005Apr 10, 2012Sharp Laboratories Of America, Inc.Methods and systems for imaging device dynamic document creation and organizationUS8171404Mar 12, 2007May 1, 2012Sharp Laboratories Of America, Inc.Methods and systems for disassembly and reassembly of examination documentsUS8181107 *Dec 8, 2006May 15, 2012Bytemobile, Inc.Content adaptationUS8201077Aug 18, 2006Jun 12, 2012Sharp Laboratories Of America, Inc.Methods and systems for imaging device form generation and form field data managementUS8213034Jul 29, 2005Jul 3, 2012Sharp Laboratories Of America, Inc.Methods and systems for providing remote file structure access on an imaging deviceUS8237946Jul 29, 2005Aug 7, 2012Sharp Laboratories Of America, Inc.Methods and systems for imaging device accounting server redundancyUS8270003Aug 18, 2006Sep 18, 2012Sharp Laboratories Of America, Inc.Methods and systems for integrating imaging device display contentUS8345272Sep 28, 2006Jan 1, 2013Sharp Laboratories Of America, Inc.Methods and systems for third-party control of remote imaging jobsUS8384925Jul 29, 2005Feb 26, 2013Sharp Laboratories Of America, Inc.Methods and systems for imaging device accounting data managementUS8428484Mar 4, 2005Apr 23, 2013Sharp Laboratories Of America, Inc.Methods and systems for peripheral accountingUS8943608Jul 18, 2013Jan 27, 2015Workiva LlcDocument server and client device document viewer and editorUS9275167May 14, 2012Mar 1, 2016Citrix Systems, Inc.Content adaptationUS9292618May 14, 2012Mar 22, 2016Citrix Systems, Inc.Content adaptationUS9325756Dec 29, 2011Apr 26, 2016Comcast Cable Communications, LlcTransmission of content fragmentsUS20060036641 *Jul 28, 2005Feb 16, 2006Antony BrydonSystem and method for using social networks for the distribution of communicationsUS20060077119 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for receiving content at an imaging deviceUS20060077411 *Oct 8, 2004Apr 13, 2006Rono MathiesonMethods and systems for imaging device document translationUS20060077414 *Oct 21, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device controlUS20060077422 *Oct 8, 2004Apr 13, 2006Rono MathiesonMethods and systems for imaging device remote form managementUS20060077423 *Oct 8, 2004Apr 13, 2006Rono MathiesonMethods and systems for imaging device remote application interactionUS20060077426 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential receipt and authenticationUS20060077427 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for local configuration-based imaging device accountingUS20060077428 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for displaying content on an imaging deviceUS20060077429 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential management and authenticationUS20060077430 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential submissionUS20060077431 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device concurrent account useUS20060077432 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device accounting data managementUS20060077433 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device accounting data maintenanceUS20060077435 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device accounting server redundancyUS20060077438 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential managementUS20060077439 *Sep 22, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for distributing localized display elements to an imaging deviceUS20060077442 *Sep 22, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device display element localizationUS20060077443 *Sep 22, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device display coordinationUS20060077444 *Sep 22, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device display standardizationUS20060077445 *Sep 30, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for providing remote, descriptor-related data to an imaging deviceUS20060077446 *Sep 30, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for obtaining imaging device event notification subscriptionUS20060077448 *Sep 30, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device event notification subscriptionUS20060077449 *Sep 30, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for administering imaging device notification access controlUS20060077450 *Sep 30, 2005Apr 13, 2006Reddy Amarender R KMethods and systems for accessing remote, descriptor-related data at an imaging deviceUS20060077451 *Sep 30, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for obtaining imaging device notification access controlUS20060077453 *Sep 30, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device related event notificationUS20060077454 *Sep 30, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device event notification administration and subscriptionUS20060077464 *Oct 8, 2004Apr 13, 2006Rono MathiesonMethods and systems for imaging device document managementUS20060080123 *Aug 31, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device job configuration managementUS20060080124 *Aug 31, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and sytems for imaging device job definitionUS20060080129 *Sep 30, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for providing access to remote, descriptor-related data at an imaging deviceUS20060080731 *Jul 29, 2005Apr 13, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential acceptanceUS20060085430 *Jul 29, 2005Apr 20, 2006Sharp Laboratories Of America, Inc.Methods and systems for accessing a remote file structure from an imaging deviceUS20060090128 *Jul 29, 2005Apr 27, 2006Sharp Laboratories Of America, Inc.Methods and systems for providing remote file structure access to an imaging deviceUS20060095536 *Oct 8, 2004May 4, 2006Rono MathiesonMethods and systems for imaging device remote location functionsUS20060095542 *Oct 21, 2005May 4, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device document modificationUS20060103588 *Sep 22, 2005May 18, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device dynamic document creation and organizationUS20060103873 *Jul 29, 2005May 18, 2006Sharp Laboratories Of America, Inc.Methods and systems for providing remote file structure access on an imaging deviceUS20060119883 *Jul 29, 2005Jun 8, 2006Sharp Laboratories Of America, Inc.Methods and systems for imaging device credential consolidationUS20060198653 *Mar 4, 2005Sep 7, 2006Sharp Laboratories Of America, Inc.Methods and systems for peripheral accountingUS20060279474 *Aug 18, 2006Dec 14, 2006Lum Joey PMethods and Systems for Imaging Device Data DisplayUS20060279475 *Aug 18, 2006Dec 14, 2006Lum Joey PMethods and Systems for Integrating Imaging Device Display ContentUS20070023447 *Jul 26, 2005Feb 1, 2007Jeong Min YoonDischarger for tabletsUS20070146823 *Mar 12, 2007Jun 28, 2007Borchers Gregory EMethods and Systems for Document ManipulationUS20070156738 *Sep 29, 2006Jul 5, 2007Brainloop AgMethod for Operating a Data Processing SystemUS20080079974 *Sep 28, 2006Apr 3, 2008Andrew Rodney FerlitschMethods and Systems for Third-Party Control of Remote Imaging JobsUS20080139191 *Dec 8, 2006Jun 12, 2008Miguel MelnykContent adaptationUS20100107058 *Oct 23, 2008Apr 29, 2010Yahoo! Inc.Query aware processingUS20130046848 *Aug 18, 2011Feb 21, 2013Comcast Cable Communications, LlcMulticasting ContentUS20130163872 *Dec 27, 2012Jun 27, 2013Peking University Founder Group Co., Ltd.Method, Server, Reading Terminal and System for Processing Electronic DocumentUS20160078144 *Sep 16, 2014Mar 17, 2016International Business Machines CorporationExposing Fragment IdentifiersWO2014133580A1 *Aug 8, 2013Sep 4, 2014WebFilings LLCDocument server and client device document viewer and editor* Cited by examinerClassifications U.S. Classification709/219, 707/E17.121International ClassificationG06F15/16, G06F17/30Cooperative ClassificationG06F17/30905European ClassificationG06F17/30W9VLegal EventsDateCodeEventDescriptionFeb 17, 2005ASAssignmentOwner name: HEWLETT-PACKARD DEVELOPMENT COMPANY, LP., TEXASFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HEWLETT-PACKARD LIMITED;REEL/FRAME:016313/0411Effective date: 20050111Feb 16, 2011ASAssignmentOwner name: CPI INTERNATIONAL INC., CALIFORNIAFree format text: RELEASE;ASSIGNOR:UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT;REEL/FRAME:025810/0162Effective date: 20110211Owner name: COMMUNICATIONS & POWER INDUSTRIES LLC, CALIFORNIAFree format text: RELEASE;ASSIGNOR:UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT;REEL/FRAME:025810/0162Effective date: 20110211Owner name: COMMUNICATIONS & POWER INDUSTRIES ASIA INC., CALIFFree format text: RELEASE;ASSIGNOR:UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT;REEL/FRAME:025810/0162Effective date: 20110211Owner name: COMMUNICATIONS & POWER INDUSTRIES INTERNATIONAL INFree format text: RELEASE;ASSIGNOR:UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT;REEL/FRAME:025810/0162Effective date: 20110211Owner name: CPI MALIBU DIVISION (FKA MALIBU RESEARCH ASSOCIATEFree format text: RELEASE;ASSIGNOR:UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT;REEL/FRAME:025810/0162Effective date: 20110211Owner name: CPI ECONCO DIVISION (FKA ECONCO BROADCAST SERVICE,Free format text: RELEASE;ASSIGNOR:UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT;REEL/FRAME:025810/0162Effective date: 20110211Owner name: CPI SUBSIDIARY HOLDINGS INC. (NOW KNOW AS CPI SUBSFree format text: RELEASE;ASSIGNOR:UBS AG, STAMFORD BRANCH, AS COLLATERAL AGENT;REEL/FRAME:025810/0162Effective date: 20110211Oct 18, 2012FPAYFee paymentYear of fee payment: 4Sep 26, 2016FPAYFee paymentYear of fee payment: 8RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services