An inkjet printing system, as one example of a fluid ejection system, may include a printhead, an ink supply which supplies liquid ink to the printhead, and an electronic controller which controls the printhead. The printhead, as one example of a fluid ejection device, ejects drops of ink through a plurality of nozzles or orifices and toward a print medium, such as a sheet of paper, so as to print onto the print medium. In some examples, the orifices are arranged in at least one column or array such that properly sequenced ejection of ink from the orifices causes characters or other images to be printed upon the print medium as the printhead and the print medium are moved relative to each other.
In the following detailed description, reference is made to the accompanying drawings which form a part hereof, and in which is shown by way of illustration specific examples in which the disclosure may be practiced. It is to be understood that other examples may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure. The following detailed description, therefore, is not to be taken in a limiting sense, and the scope of the present disclosure is defined by the appended claims. It is to be understood that features of the various examples described herein may be combined, in part or whole, with each other, unless specifically noted otherwise.
Fluid ejection dies, such as thermal inkjet (TIJ) dies may be narrow and long pieces of silicon. The silicon area used by a die is related to the cost of the die so that any functionality that can be removed from the die should be removed or modified to have multiple purposes if possible. Non-volatile memory (NVM) may be used on the die to transfer information from the die to a printer, such as thermal behavior, offsets, region information, a color map, the number of nozzles, etc. In addition, NVM may also be used to transfer information from the printer to the die, such as an ink usage gauge, nozzle health information, etc. Memories may be composed of storage elements, read/write multiplexers, and enable/address circuitry. For small memories, the non-storage circuitry may be a large percentage of the overall area used by the memory, making small memories very area inefficient.
Accordingly, disclosed herein are integrated circuits (e.g., fluid ejection dies) including memory cells corresponding to fluid actuation devices. The same circuit logic is used to activate either selected fluid actuation devices or access selected corresponding memory cells based on received addresses and nozzle data. The data stored in each memory cell may be read out of the integrated circuit through a single contact pad. The memory cells may be distributed along the length of the integrated circuit adjacent to the corresponding fluid actuation devices.
As used herein a “logic high” signal is a logic “1” or “on” signal or a signal having a voltage about equal to the logic power supplied to an integrated circuit (e.g., between about 1.8 V and 15 V, such as 5.6 V). As used herein a “logic low” signal is a logic “0” or “off” signal or a signal having a voltage about equal to a logic power ground return for the logic power supplied to the integrated circuit (e.g., about 0 V).
In one example, each fluid actuation device 1020 to 102N includes a nozzle or a fluidic pump to eject fluid drops. Each memory cell 1040 to 104N corresponds to a fluid actuation device 1020 to 102N, respectively. In one example, each memory cell 1040 to 104N includes a non-volatile memory cell (e.g., a floating gate transistor, a programmable fuse, etc.). The select circuit 106 selects fluid actuation devices 1020 to 102N and memory cells 1040 to 104N corresponding to the selected fluid actuation devices 1020 to 102N. Select circuit 106 may include an address decoder, activation logic, and/or other suitable logic circuitry for selecting fluid actuation devices 1020 to 102N and corresponding memory cells 1040 to 104N in response to an address signal and a nozzle data signal. Configuration logic 110 enables or disables access to the plurality of memory cells 1040 to 104N. Configuration logic 110 may include a memory device or other suitable logic circuitry for enabling or disabling access to the plurality of memory cells 1040 to 104N.
Control logic 108 either activates the selected fluid actuation devices 1020 to 102N or accesses the memory cells 1040 to 104N corresponding to the selected fluid actuation devices based on a state of the configuration logic 110. Control logic 108 may include a microprocessor, an application-specific integrated circuit (ASIC), or other suitable logic circuitry for controlling the operation of integrated circuit 100. While select circuit 106, control logic 108, and configuration logic 110 are illustrated in separates blocks in
In this example, select circuit 106 includes an address decoder 122 and activation logic 124. Address decoder 122 receive addresses and data through a data interface 126. Address decoder 122 is electrically coupled to activation logic 124. Activation logic 124 receives a fire signal through a fire interface 128. Each memory cell 1040 to 104N is electrically coupled to write circuit 130 through a sense interface 134. Sensor 132 is electrically coupled to control logic 108 through a signal path 131 and to sense interface 134.
Address decoder 122 selects fluid actuation devices 1020 to 102N and memory cells 1040 to 104N corresponding to the selected fluid actuation devices 1020 to 102N in response to an address. The address may be received through data interface 126. The activation logic 124 activates selected fluid actuation devices 1020 to 102N and memory cells 1040 to 104N corresponding to the selected fluid actuation devices 1020 to 102N based on a data signal and a fire signal. The data signal may include nozzle data indicating which fluid actuation device(s) for the provided address are to be selected. The data signal may be received through the data interface 126. The fire signal indicates when the selected fluid actuation devices are to be activated (i.e., fired) or when the corresponding memory cells are to be accessed. The fire signal may be received through the fire interface 128. Each of the data interface 126, fire interface 128, and sense interface 134 may be a contact pad, a pin, a bump, a wire, or another suitable electrical interface for transmitting signals to and/or from integrated circuit 120. Each of the interfaces 126, 128, and 134 may be electrically coupled to a fluid ejection system (e.g., a host print apparatus such as fluid ejection system 500, which will be described below with reference to
The configuration register 136 stores data to enable or disable access to the plurality of memory cells 1040 to 104N. The control logic 108 either activates the selected fluid actuation devices 1020 to 102N or accesses the memory cells 1040 to 104N corresponding to the selected fluid actuation devices 1020 to 102N based on the data stored in the configuration register 136. In one example, the configuration register 136 also stores data to enable write access or read access to the plurality of memory cells 1040 to 104N. In another example, the configuration register 136 also stores data to enable or disable the sensor 132.
Configuration register 136 may be a memory device (e.g., non-volatile memory, shift register, etc.) and may include any suitable number of bits (e.g., 4 bits to 24 bits, such as 12 bits). In certain examples, configuration register 136 may also store configuration data for testing integrated circuit 120, detecting cracks within a substrate of integrated circuit 120, enabling timers of integrated circuit 120, setting analog delays of integrated circuit 120, validating operations of integrated circuit 120, or for configuring other functions of integrated circuit 120.
Data stored in memory cells 1040 to 104N may be read through sense interface 134 when the selected memory cells 1040 to 104N have been accessed by control logic 108. In addition, write circuit 130 may write data to selected memory cells when the selected memory cells 1040 to 104N have been accessed by control logic 108. Sensor 132 may be a junction device (e.g., thermal diode), a resistive device (e.g., crack detector), or another suitable device for sensing a state of integrated circuit 120. Sensor 132 may be read through sense interface 134.
Circuit 200 includes a plurality of fluid actuation devices 2020 to 20215, a plurality of memory cells 2040 to 20415, an address decoder including logic gates 2220 to 22215, activation logic including logic gates 227 and 2240 to 22415, a write circuit including a memory write voltage regulator 230, transistors 238 and 240, and a contact (i.e., sense) pad 241. A first input of logic gate 227 receives nozzle data through a nozzle data signal path 226. A second input of logic gate 227 receives a fire signal through a fire signal path 228. The output of logic gate 227 is electrically coupled to a first input of each logic gate 2240 to 22415 through a signal path 229. The input of each logic gate 2220 to 22215 receives an address signal through an address signal path 221. The output of each logic gate 2220 to 22215 is electrically coupled to a second input of each logic gate 2240 to 22415 through a signal path 2230 to 22315, respectively. The output of each logic gate 2240 to 22415 is electrically coupled to a fluid actuation device 2020 to 20215 and to a memory cell 2040 to 20415 through a signal path 2250 to 22515, respectively.
Each fluid actuation device 2020 to 20215 includes a logic gate 208, a transistor 210, and a firing resistor 212. While fluid actuation device 2020 is illustrated and described herein, the other fluid actuation devices 2021 to 20215 include a similar circuit. A first input of the logic gate 208 is electrically coupled to signal path 2250. A second input (inverting) of the logic gate 208 receives a memory enable signal through a memory enable signal path 207. The output of logic gate 208 is electrically coupled to the gate of transistor 210 through a signal path 209. One side of the source-drain path of transistor 210 is electrically coupled to a common or ground node 214. The other side of the source-drain path of transistor 210 is electrically coupled to one side of firing resistor 212 through a signal path 211. The other side of firing resistor 212 is electrically coupled to a supply voltage node (e.g., VPP) 215.
Each memory cell 2040 to 20415 includes transistors 216 and 218 and a floating gate transistor 220. While memory cell 2040 is illustrated and described herein, the other memory cells 2041 to 20415 include a similar circuit. The gate of transistor 216 is electrically coupled to signal path 2250. One side of the source-drain path of transistor 216 is electrically coupled to a common or ground node 214. The other side of the source-drain path of transistor 216 is electrically coupled to one side of the source-drain path of transistor 218 through a signal path 217. The gate of transistor 218 receives a memory enable signal through a memory enable signal path 207. The other side of the source-drain path of transistor 218 is electrically coupled to one side of the source-drain path of floating gate transistor 220 through a signal path 219. The other side of the source-drain path of floating gate transistor 220 is electrically coupled to memory write voltage regulator 230 and one side of the source-drain path of transistor 238 through a signal path 234.
Memory write voltage regulator 230 receives a memory write signal through a memory write signal path 232. The gate of transistor 238 and the gate of transistor 240 receive a memory read signal through a memory read signal path 236. The other side of the source-drain path of transistor 238 is electrically coupled to one side of the source-drain path of transistor 240 through a signal path 239. The other side of the source-drain path of transistor 240 is electrically coupled to sense pad 241.
The nozzle data signal on nozzle data signal path 226, the fire signal on fire signal path 228, and the address signal on address signal path 221 are used to activate a fluid actuation device 2020 to 20215 or a corresponding memory cell 2040 to 20415. The memory enable signal on memory enable signal path 207 determines whether a fluid actuation device 2020 to 20215 is activated or whether a corresponding memory cell 2040 to 20415 is accessed. In response to a logic high memory enable signal, transistor 218 is turned on to enable access to memory cells 2040 to 20415. In addition, in response to a logic high memory enable signal, logic gate 208 outputs a logic low signal to turn off transistor 210 to prevent any fluid actuation devices 2020 to 20215 from firing in response to a fire signal passed to signal paths 2250 to 22515. In response to a logic low memory enable signal, transistor 218 turns off to disable access to memory cells 2040 to 20415. In addition, in response to a logic low memory enable signal, logic gate 208 allows fire signals passed to signal paths 2250 to 22515 to fire fluid actuation devices 2020 to 20215. In one example, the memory enable signal is based on a data bit stored in a configuration register, such as configuration register 136 of
The nozzle data signal indicates whether fluid actuation devices 2020 to 20215 or corresponding memory cells 2040 to 20415 will be selected. In one example, the nozzle data signal includes a logic high signal to select fluid actuation devices 2020 to 20215 or corresponding memory cells 2040 to 20415 and a logic low signal to deselect fluid actuation devices 2020 to 20215 or corresponding memory cells 2040 to 20415. In response to a logic high nozzle data signal, logic gate 227 passes a logic high signal to signal path 229 in response to a logic high fire signal. In response to a logic low nozzle data signal or a logic low fire signal, logic gate 227 passes a logic low signal to signal path 229.
The address signal selects one of the fluid actuation devices 2020 to 20215 or corresponding memory cells 2040 to 20415. In response to the address signal, one of the logic gates 2220 to 22215 passes a logic high signal to a corresponding signal path 2230 to 22315. The other logic gates 2220 to 22215 pass a logic low signal to the corresponding signal paths 2230 to 22315.
Each logic gate 2240 to 22415 passes a logic high signal to the corresponding signal path 2250 to 22515 in response to a logic high signal on signal path 229 and a logic high signal on the corresponding signal path 2230 to 22315. Each logic gate 2240 to 22415 passes a logic low signal to the corresponding signal path 2250 to 22515 in response to a logic low signal on signal path 229 or a logic low signal on the corresponding signal path 2230 to 22315. Accordingly, in response to a logic low memory enable signal and a logic high signal on a signal path 2250 to 22515, the corresponding fluid actuation device 2020 to 20215 fires by activating the corresponding firing resistor 212. In response to a logic high memory enable signal and a logic high signal on a signal path 2250 to 22515, the corresponding memory cell 2040 to 20415 is selected for access.
With a memory cell 2040 to 20415 selected for access, memory write voltage regulator 230 may be enabled by a memory write signal on memory write signal path 232 to apply a voltage to signal path 234 to write a data bit to floating gate transistor 220. In addition, with a memory cell 2040 to 20415 selected for access, transistors 238 and 240 may be turned on in response to a memory read signal on memory read signal path 236. With transistors 238 and 240 turned on, the data bit stored in floating gate transistor 220 may be read through sense pad 241 (e.g., by a host print apparatus coupled to sense pad 241). In one example, the memory write signal and the memory read signal are based on data stored in a configuration register, such as configuration register 136 of
In one example, each memory cell 3040 to 304N includes a non-volatile memory cell (e.g., a floating gate transistor, a programmable fuse, etc.). Address decoder 322 selects memory cells 3040 to 304N in response to an address, which may be received through data interface 326. Activation logic 324 activates selected memory cells 3040 to 304N based on a data signal on data interface 326 and a fire signal on fire interface 328. Configuration logic 310 enables or disables access to the plurality of memory cells 3040 to 304N.
Configuration register 336 may store data to enable or disable access to the plurality of memory cells 3040 to 304N. In addition, configuration register 336 may store data to enable write access or read access to the plurality of memory cells 3040 to 304N. Sense interface 334 provides a single interface coupled to each of the plurality of memory cells 3040 to 304N to connect to a single contact of a host print apparatus. In one example, sense interface 334 includes a single contact pad.
Data stored in memory cells 3040 to 304N may be read through sense interface 334 when the selected memory cells 3040 to 304N have been accessed by address decoder 322 and activation logic 324. In addition, write circuit 330 may write data to selected memory cells 3040 to 304N when the selected memory cells 3040 to 304N have been accessed by address decoder 322 and activation logic 324.
In one example, the first column 402 of contact pads includes six contact pads. The first column 402 of contact pads may include the following contact pads in order: a data contact pad 410, a clock contact pad 412, a logic power ground return contact pad 414, a multipurpose input/output (i.e., sense) contact pad 416, a first high voltage power supply contact pad 418, and a first high voltage power ground return contact pad 420. Therefore, the first column 402 of contact pads includes the data contact pad 410 at the top of the first column 402, the first high voltage power ground return contact pad 420 at the bottom of the first column 402, and the first high voltage power supply contact pad 418 directly above the first high voltage power ground return contact pad 420. While contact pads 410, 412, 414, 416, 418, and 420 are illustrated in a particular order, in other examples the contact pads may be arranged in a different order.
In one example, the second column 404 of contact pads includes six contact pads. The second column 404 of contact pads may include the following contact pads in order: a second high voltage power ground return contact pad 422, a second high voltage power supply contact pad 424, a logic reset contact pad 426, a logic power supply contact pad 428, a mode contact pad 430, and a fire contact pad 432. Therefore, the second column 404 of contact pads includes the second high voltage power ground return contact pad 422 at the top of the second column 404, the second high voltage power supply contact pad 424 directly below the second high voltage power ground return contact pad 422, and the fire contact pad 432 at the bottom of the second column 404. While contact pads 422, 424, 426, 428, 430, and 432 are illustrated in a particular order, in other examples the contact pads may be arranged in a different order.
Data contact pad 410 (e.g. data interface 126 of
First high voltage power supply contact pad 418 and second high voltage power supply contact pad 424 may be used to supply high voltage (e.g., about 32 V) to die 400. First high voltage power ground return contact pad 420 and second high voltage power ground return contact pad 422 may be used to provide a power ground return (e.g., about 0 V) for the high voltage power supply. The high voltage power ground return contact pads 420 and 422 are not directly electrically connected to the semiconductor substrate 440 of die 400. The specific contact pad order with the high voltage power supply contact pads 418 and 424 and the high voltage power ground return contact pads 420 and 422 as the innermost contact pads may improve power delivery to die 400. Having the high voltage power ground return contact pads 420 and 422 at the bottom of the first column 402 and at the top of the second column 404, respectively, may improve reliability for manufacturing and may improve ink shorts protection.
Logic reset contact pad 426 may be used as a logic reset input to control the operating state of die 400. Logic power supply contact pad 428 may be used to supply logic power (e.g., between about 1.8 V and 15 V, such as 5.6 V) to die 400. Mode contact pad 430 may be used as a logic input to control access to enable/disable configuration modes (i.e., functional modes) of die 400. Fire contact pad 432 (e.g., fire interface 128 of
Die 400 includes an elongate substrate 440 having a length 442 (along the Y axis), a thickness 444 (along the Z axis), and a width 446 (along the X axis). In one example, the length 442 is at least twenty times the width 446. The width 446 may be 1 mm or less and the thickness 444 may be less than 500 microns. The fluid actuation devices 408 (e.g., fluid actuation logic) and contact pads 410-432 are provided on the elongate substrate 440 and are arranged along the length 442 of the elongate substrate. Fluid actuation devices 408 have a swath length 452 less than the length 442 of the elongate substrate 440. In one example, the swath length 452 is at least 1.2 cm. The contact pads 410-432 may be electrically coupled to the fluid actuation logic. The first column 402 of contact pads may be arranged near a first longitudinal end 448 of the elongate substrate 440. The second column 404 of contact pads may be arranged near a second longitudinal end 450 of the elongate substrate 440 opposite to the first longitudinal end 448.
In one example, each nozzle 408 of the plurality of nozzles has a corresponding memory cell 462. In another example, every other nozzle 408 of the plurality of nozzles has a corresponding memory cell 462. In another example, the plurality of memory cells may include a single memory cell 462 corresponding to each nozzle 408. In another example, the plurality of memory cells includes at least two memory cells 462 corresponding to each nozzle 408. The plurality of memory cells 462 may be arranged in a plurality of groups 460, where each group 460 includes at least two memory cells 462. The plurality of groups 460 are spaced apart from each other along the length of the elongate substrate 440.
As illustrated in
In one example, the plurality of memory cells includes three memory cells 472 corresponding to each nozzle 408a and/or 408b. A first memory cell (e.g., memory cell 4721-0) corresponding to each nozzle is arranged in a first bank (e.g., bank 4821) of memory cells, a second memory cell (e.g., memory cell 4722-0) corresponding to each nozzle is arranged in a second bank (e.g., bank 4822) of memory cells, and a third memory cell (e.g., memory cell 4723-0) corresponding to each nozzle is arranged in a third bank (e.g., bank 4823) of memory cells. The fluid actuation logic either ejects fluid from the selected nozzles 408a and/or 408b or accesses memory cells 472 corresponding to the selected nozzles and a selected bank of memory cells.
In one example, the bank one, bank two, and bank three enable signals are based on data stored in a configuration register, such as configuration register 136 of
Printhead assembly 502 includes at least one printhead or fluid ejection die 400 previously described and illustrated with reference to
Ink supply assembly 510 supplies ink to printhead assembly 502 and includes a reservoir 512 for storing ink. As such, in one example, ink flows from reservoir 512 to printhead assembly 502. In one example, printhead assembly 502 and ink supply assembly 510 are housed together in an inkjet or fluid-jet print cartridge or pen. In another example, ink supply assembly 510 is separate from printhead assembly 502 and supplies ink to printhead assembly 502 through an interface connection 513, such as a supply tube and/or valve.
Carriage assembly 516 positions printhead assembly 502 relative to print media transport assembly 518, and print media transport assembly 518 positions print media 524 relative to printhead assembly 502. Thus, a print zone 526 is defined adjacent to nozzles 408 in an area between printhead assembly 502 and print media 524. In one example, printhead assembly 502 is a scanning type printhead assembly such that carriage assembly 516 moves printhead assembly 502 relative to print media transport assembly 518. In another example, printhead assembly 502 is a non-scanning type printhead assembly such that carriage assembly 516 fixes printhead assembly 502 at a prescribed position relative to print media transport assembly 518.
Service station assembly 504 provides for spitting, wiping, capping, and/or priming of printhead assembly 502 to maintain the functionality of printhead assembly 502 and, more specifically, nozzles 408. For example, service station assembly 504 may include a rubber blade or wiper which is periodically passed over printhead assembly 502 to wipe and clean nozzles 408 of excess ink. In addition, service station assembly 504 may include a cap that covers printhead assembly 502 to protect nozzles 408 from drying out during periods of non-use. In addition, service station assembly 504 may include a spittoon into which printhead assembly 502 ejects ink during spits to ensure that reservoir 512 maintains an appropriate level of pressure and fluidity, and to ensure that nozzles 408 do not clog or weep. Functions of service station assembly 504 may include relative motion between service station assembly 504 and printhead assembly 502.
Electronic controller 520 communicates with printhead assembly 502 through a communication path 503, service station assembly 504 through a communication path 505, carriage assembly 516 through a communication path 517, and print media transport assembly 518 through a communication path 519. In one example, when printhead assembly 502 is mounted in carriage assembly 516, electronic controller 520 and printhead assembly 502 may communicate via carriage assembly 516 through a communication path 501. Electronic controller 520 may also communicate with ink supply assembly 510 such that, in one implementation, a new (or used) ink supply may be detected.
Electronic controller 520 receives data 528 from a host system, such as a computer, and may include memory for temporarily storing data 528. Data 528 may be sent to fluid ejection system 500 along an electronic, infrared, optical or other information transfer path. Data 528 represent, for example, a document and/or file to be printed. As such, data 528 form a print job for fluid ejection system 500 and includes at least one print job command and/or command parameter.
In one example, electronic controller 520 provides control of printhead assembly 502 including timing control for ejection of ink drops from nozzles 408. As such, electronic controller 520 defines a pattern of ejected ink drops which form characters, symbols, and/or other graphics or images on print media 524. Timing control and, therefore, the pattern of ejected ink drops, is determined by the print job commands and/or command parameters. In one example, logic and drive circuitry forming a portion of electronic controller 520 is located on printhead assembly 502. In another example, logic and drive circuitry forming a portion of electronic controller 520 is located off printhead assembly 502.
Although specific examples have been illustrated and described herein, a variety of alternate and/or equivalent implementations may be substituted for the specific examples shown and described without departing from the scope of the present disclosure. This application is intended to cover any adaptations or variations of the specific examples discussed herein. Therefore, it is intended that this disclosure be limited only by the claims and the equivalents thereof.
This application is a Continuation Patent Application of U.S. patent application Ser. No. 17/471,844, filed Sep. 10, 2021, entitled “INTEGRATED CIRCUITS INCLUDING MEMORY CELLS”, which is a Continuation Patent Application of U.S. National Stage patent application Ser. No. 16/956,316, filed Jun. 19, 2020, entitled “INTEGRATED CIRCUITS INCLUDING MEMORY CELLS” which claims benefit and priority of PCT Patent Application No. PCT/US2019/016732, filed Feb. 6, 2019, entitled “INTEGRATED CIRCUITS INCLUDING MEMORY CELLS”, the entireties of which are incorporated by reference herein.
Number | Name | Date | Kind |
---|---|---|---|
6161916 | Gibson et al. | Dec 2000 | A |
6685289 | Anderson et al. | Feb 2004 | B2 |
6948789 | Imanaka et al. | Sep 2005 | B2 |
7448712 | Hatasa et al. | Nov 2008 | B2 |
7802858 | Kasai | Sep 2010 | B2 |
10232615 | Giusti et al. | Mar 2019 | B2 |
11141973 | Linn | Oct 2021 | B2 |
20020126168 | Anderson | Sep 2002 | A1 |
20020140751 | Imanaka et al. | Oct 2002 | A1 |
20070081842 | Ehrhardt, Jr. | Apr 2007 | A1 |
20080055366 | Benjamin et al. | Mar 2008 | A1 |
20100124329 | Lyman | May 2010 | A1 |
20100188448 | Kida | Jul 2010 | A1 |
20100302293 | Torgerson et al. | Dec 2010 | A1 |
20140320558 | Ge et al. | Oct 2014 | A1 |
20160009080 | Akune | Jan 2016 | A1 |
20160332439 | Ge et al. | Nov 2016 | A1 |
20170120590 | Chen et al. | May 2017 | A1 |
20170259568 | Dodd et al. | Sep 2017 | A1 |
20180050901 | Neo et al. | Feb 2018 | A1 |
20180236762 | Negishi et al. | Aug 2018 | A1 |
20200055309 | Martin et al. | Feb 2020 | A1 |
20220063262 | Ng et al. | Mar 2022 | A1 |
Number | Date | Country |
---|---|---|
2008003128 | Mar 2009 | CL |
2008003388 | Mar 2009 | CL |
1320521 | Nov 2001 | CN |
101213531 | Jul 2008 | CN |
107073940 | Aug 2017 | CN |
2000-198202 | Jul 2000 | JP |
2001-096869 | Apr 2001 | JP |
2002-086728 | Mar 2002 | JP |
2010-173098 | Aug 2010 | JP |
2020-507496 | Mar 2020 | JP |
2020-508896 | Mar 2020 | JP |
0125016 | Apr 2001 | WO |
0125017 | Apr 2001 | WO |
2018190863 | Oct 2018 | WO |
2019009903 | Jan 2019 | WO |
2019009904 | Jan 2019 | WO |
2020162916 | Aug 2020 | WO |
2020162919 | Aug 2020 | WO |
2020162920 | Aug 2020 | WO |
Number | Date | Country | |
---|---|---|---|
20230356524 A1 | Nov 2023 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 17471844 | Sep 2021 | US |
Child | 18222354 | US | |
Parent | 16956316 | US | |
Child | 17471844 | US |