Some imaging material supply cartridges include a memory for storing data. Existing schemes for identifying attributes of data stored in the memory occupy valuable memory space.
Printer 22 comprises a printing, marking or imaging device configured to mark, print or otherwise deposit or form patterns or images of imaging material upon a substrate or print media. As schematically shown by
Interface 30 comprises a mechanism by which printer 22 communicates with imaging material supply cartridge 24. In one embodiment, interface 30 may comprise a wired connection using one or more electrical traces, electrical wires, electrical contact pads, electrical plugs and the like. While printer 22 and supply 24 are shown spaced apart, in operation, interface 30 may contact interface 40. In another embodiment, interface 30 may facilitate a wireless communication between printer 22 and cartridge 24.
Controller 32 comprises one or more processing units configured to generate control signals directing the printing or marking being performed by printing elements, such as print heads, of imaging material supply cartridge 24 or being performed using imaging material from imaging material supply cartridge 24. Controller 32 is further configured to read data stored on imaging material supply cartridge 24 and to write data to cartridge 24.
For purposes of this application, the term “processing unit” shall mean a presently developed or future developed processing unit that executes sequences of instructions contained in a memory. Execution of the sequences of instructions causes the processing unit to perform steps such as generating control signals. The instructions may be loaded in a random access memory (RAM) for execution by the processing unit from a read only memory (ROM), a mass storage device, or some other persistent storage. In other embodiments, hard wired circuitry may be used in place of or in combination with software instructions to implement the functions described. For example, controller 32 may be embodied as part of one or more application-specific integrated circuits (ASICs). Unless otherwise specifically noted, the controller is not limited to any specific combination of hardware circuitry and software, nor to any particular source for the instructions executed by the processing unit. Although controller 32 is illustrated as part of printer 22, and other embodiments, controller 32 may be provided in a separate electronic device, such as a separate computer.
Imaging material supply cartridge 24 comprises a device configured to supply imaging material for the printing or marking upon a substrate or printed medium. In the example illustrated, imaging material supply cartridge 24 comprises body 34, imaging material supply 36, image forming device 38, interface 40 and memory 42. Body 34 comprises a framework or housing at least partially enclosing or supporting the remaining components of imaging material supply cartridge 24. Body 34 encloses or forms the imaging material supply 36. Body 34 may have a variety of different shapes and configurations.
Imaging material supply 36 comprises a volume, cavity or chamber formed within body 34 and containing imaging material. In one embodiment, imaging material supply 36 contains a liquid imaging material. Examples of liquid imaging material include, but are not limited to, chromatic inks, non-chromatic inks, chromatic toners, non-chromatic toners, fixers, embossing materials or solutions containing solutes which may be printed or marked to form mechanical, chemical or electrical structures such as transistors, chemical or electrical sensing devices, micro machines, nano-machines and the like. In one embodiment, imaging material supply 36 may contain a dry imaging material, such as a dry toner. In one embodiment, imaging material supply 36 may comprise such a chamber that is substantially enclosed or sealed, wherein upon exhaustion of the imaging material from supply 36, cartridge 24 is removed and disposed of or is refurbished with new imaging material. In another embodiment, imaging material supply 36 may alternatively be configured to be periodically or continuously replenished while connected to printer 22 from a separate imaging material supply.
Image forming device 38 comprises one or more device configured to print, mark, deposit or otherwise apply the imaging material received from supply 36 onto a substrate or printed medium. In one embodiment, image forming device 38 may comprise one or more print heads having fluid or liquid nozzles through which liquid imaging material is ejected. Examples of such liquid ejecting print heads include drop-on-demand inkjet print heads such as thermoresistive inkjet print heads and piezo resistive inkjet print heads. In another embodiment, image forming device 38 may include one or more drums or rollers configured to apply an electrostatically formed pattern or image of the imaging material onto a substrate or printed medium. In such an embodiment, the imaging material may be in a dry toner form or a liquid toner form.
In the example illustrated, image forming device 38 is embodied as part of cartridge 24 so to be carried and transported as part of cartridge 24. In other embodiments, image forming device 38 may alternatively be provided as part of printer 22 instead of cartridge 24. In such an alternative embodiment, imaging material supply cartridge 24 supplies imaging material from supply 36 to the image forming device 38 of printer 22.
Interface 40 comprises a mechanism by which printer 22 communicates with imaging material supply cartridge 24. In one embodiment, interface 40 may comprise a wired connection using one or more electrical traces, electrical wires, electrical contact pads, electrical plugs and the like. In another embodiment, interface 40 may facilitate a wireless communication between printer 22 and cartridge 24. In some embodiments, imaging material supply cartridge 24 may, itself, include a processor or controller which further communicates with the processor or controller of printer 22 or a separate processor or controller associated with or in communication with printer 22.
Memory 42 (schematically shown) comprises one or more persistent storage devices supported by body 34, physically attached to body 34, physically enclosed or contained within the body 34 or coupled to body 34 so as to be carried by body 34. In other words, memory 42 remains a part of cartridge 24 when cartridge 24 is separated from printer 22. Memory 42 comprises an electronic or computer readable memory. Examples of memory 42, include, but are not limited to, magnetic memory, optical memory, an integrated circuit or memory card and the like.
As shown by
For example, in one embodiment, all the data fields 56 having a same access mode are grouped together in one or more partitions designated or assigned for the particular access mode. Examples of different access modes include read only, read/write, or read/write-or. The read only access mode merely allows reading of the data fields 56 in the particular partition. The read/write access mode permits both reading of data from and writing of data to the data fields 56 in the particular partition. The read/write-or mode permits data fields to be altered in one direction. For example, a read/write-or mode performs a logical OR function on input. By way of example, an input of 1 will not change an existing bit value of 1. An input of 0 will not change an existing bit value of 1. An input of 1 will change an existing bit value of 0. In one embodiment, all data fields 56 in which data is already written and which is not to be altered, but only read, maybe grouped in one partition. In such an embodiment, all data fields 56 in which data may be written or which may be read may be grouped together in another partition.
All the data fields 56 having a same encryption attribute are grouped together in one or more partitions designated for the particular encryption attribute. For example, in one embodiment, an encryption attribute may be simply (1) encrypted or (2) not encrypted (plain text). In some embodiments, the date fields 56 that are encrypted may additionally be separately grouped based upon the mode or method by which they are encrypted.
The grouping of data fields 56 based upon their access mode and based upon their encryption attribute is collectively done at a same grouping level. In other words, all data fields having both the same access mode and the same encryption attribute are grouped together in one or more designated partitions. No single partition includes data fields of more than one access mode or more than one encryption attribute.
For example, in one embodiment, partitions 50 may include six different groupings of data fields. A first partition 50 may be read-only accessible and include only encrypted data fields. A second partition 50 may be read-only accessible and include only unencrypted data fields. A third partition 50 may be read/write accessible and include encrypted data fields. A fourth partition 50 may be read/write accessible and include unencrypted data fields. A fifth partition 50 may be read/write-or accessible and include encrypted data fields. A sixth partition 50 may be read/write-or accessible and include unencrypted data fields.
In one embodiment, each byte of a particular partition 50 may have a single data field 56, wherein excess bits of the byte are merely padded. In other embodiments, data fields 56 may be stacked end-to-end within one or more data bytes, wherein only the unused data bits of the set of one or more data bytes is padded or unused. In another embodiment, the data fields 56 may be grouped in other fashions within their associated partitions 50.
Partition map/table 52 comprises a portion of memory 42 mapping, outlining, indexing or otherwise providing information or data regarding the attributes of the partitions 50 contained within memory 42 as well as the address or location of each of partitions 50 in memory 42. In one embodiment, partition map 52 is provided in a predetermined or preset unalterable portion of memory 42, whereas partitions 50 are contained in a user accessible portion of memory 42. Partition map 52 is configured to be initially read by controller 32 prior to the accessing of partitions 50.
Partition ID portions 62 provide the actual attributes of the partition addressed by the partition address portion 60. Partition ID portions 62 identify both the access mode and the encryption attribute for the particular partition 50 addressed in partition address portion 60 of the partition map 52. Because each of partition ID portions 62 of partition map 52 identify both the access mode and the encryption mode, both pieces of data (the access mode and encryption mode data) can be concurrently associated with a single partition address rather than having one map that utilizes memory to associate an access mode with a certain identified range of data fields and which uses an additional map which must use additional memory space to once again identify a certain identified range of data fields for data having a selected encryption attribute. Said in another way, because each partition address corresponds to all data fields grouped according to both access mode and encryption attribute, a single partition address is associated and stored with such data rather than to storing and associating a first address for data with a same access mode and a second address for data with the same encryption attribute. As a result, valuable space within memory 42 is conserved.
Data bit 78 indicates or identifies with a zero or one whether all the data 56 within a particular partition 50 are encrypted. Data bits 80-83 may be used for other purposes to identify other characteristics or attributes of the data fields 56 group in the particular partition 50. For example, different data fields 56 may have different levels or degrees of encryption. In some embodiments, the data fields may also be additionally grouped based upon their different levels of encryption, wherein one or more of data bits 80-83 may indicate the particular encryption level of all of the data fields grouped into the particular partition 50 or encryption key identifier that is needed for all of the data fields grouped into the particular partition 50. In other embodiments, partition address portions 60 and partition ID portions 62 may have other bit lengths or may map a greater or fewer of such access modes with the data field groupings or partitions 50.
As indicated by steps 108 and 110, controller 32 uses the access modes and encryption attribute data read from partition map 52 to assist in reading data fields in memory 42. In particular, as indicated by step 106, if controller 32 determines that particular data to be read from memory 42 is contained in a particular partition 50 identified as being encrypted, controller 32 reads such data fields and decodes or decrypts data taken from such fields before such data is used. As indicated by step 110, if controller 32 determines that the particular data to be read from memory 42 is contained in a particular partition 50 identified as not being encrypted, controller 32 may directly use such data taken from such data fields 56. Examples of data that may be stored in particular data field 56 or written to particular data fields 56 include, but is not limited to, manufacturing date, imaging material type, imaging material quantity, printing instructions, printing suggestions, print quality settings, image forming material conservation modes, authentication data, internet, web or network authorization data, authorization request information, authorization or access keys and the like.
As indicated by step 112, controller 32 uses the data accessed or read from the encrypted and unencrypted data fields to generate control signals directing image forming device 38 in the formation of images using image forming device 38. In particular embodiments, controller 32 may use the data read from data fields 56 to generate control signals communicating additional information to a person using printer 22. For example, using data from memory 42 indicating the level of imaging material left in image material supply 36, controller 32 may generate control signals causing a display or other visual or audible communication device to inform the person of the current level of imaging material within supply 36 or whether or not cartridge 24 may be running low on imaging material or need replacement in the near future.
As indicated by step 114, controller 32 may write data to writable data fields 56 within memory 42. In doing so, controller 32 uses information read from partition map 52 indicating whether particular partition 50 have access modes that permit writing of data. Although method 100 is illustrated in
Although the present disclosure has been described with reference to example embodiments, workers skilled in the art will recognize that changes may be made in form and detail without departing from the spirit and scope of the claimed subject matter. For example, although different example embodiments may have been described as including one or more features providing one or more benefits, it is contemplated that the described features may be interchanged with one another or alternatively be combined with one another in the described example embodiments or in other alternative embodiments. Because the technology of the present disclosure is relatively complex, not all changes in the technology are foreseeable. The present disclosure described with reference to the example embodiments and set forth in the following claims is manifestly intended to be as broad as possible. For example, unless specifically otherwise noted, the claims reciting a single particular element also encompass a plurality of such particular elements.
The present application is a continuation of co-pending PCT/US2008/080054 filed on Oct. 15, 2008 by Brian L. Helterline, Jefferson P. Ward, Stephen D. Panshin, and Joseph H. Bauman and entitled PARTITION MAP, the full disclosure of which is hereby incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
5907856 | Estakhri | May 1999 | A |
6488352 | Helterline et al. | Dec 2002 | B1 |
6694106 | Yoshimura | Feb 2004 | B2 |
6738903 | Haines | May 2004 | B1 |
7177552 | Koike | Feb 2007 | B2 |
20080187345 | Sorihashi | Aug 2008 | A1 |
Number | Date | Country | |
---|---|---|---|
20110187771 A1 | Aug 2011 | US |
Number | Date | Country | |
---|---|---|---|
Parent | PCT/US2008/080054 | Oct 2008 | US |
Child | 13087619 | US |