Multi-port memory devices and methods
8 claims: 1 independent, 7 dependent
- 1A memory device, comprising:a plurality of ports (12, 14, 16, 18);a plurality of memory banks (20, 22), wherein each of the plurality of memory banks is coupled to its respective one of the plurality of ports, referred to as native memory banks (20, 22);and a plurality of bank/port circuits (40), wherein each of the plurality of bank/port circuits is coupled to a respective one of the plurality of ports and to the other ports of the plurality of ports and each bank/port circuit is configured to selectively map at least one native memory bank coupled to its respective one of the plurality of ports to another of the ports, wherein the at least one native memory bank mapped to the another of the ports is referred to as a non-native memory bank, wherein each bank/port circuit comprises a programmable configuration register coupled to receive from said respective one of the plurality of ports configuration data indicative of a manner in which each of the native memory banks coupled to said respective one of the plurality of ports should be mapped as a non-native memory bank to the another of the ports, the programmable configuration register being configured to store the received configuration data.
26 paragraphs in 5 sections, as filed
TECHNICAL FIELD
0001Embodiments of this invention relate to memory devices, and, more particularly, to a multi-port memory device.
BACKGROUND OF THE INVENTION
0002<patcit id="pcit0001" dnum="US6334175B1"><text>US6334175B1</text></patcit> relates to a switchable memory system and memory allocation method. <patcit id="pcit0002" dnum="US2008049536A1"><text>US2008049536A1</text></patcit> relates to a semiconductor memory device and semiconductor device comprising the same.
0003<patcit id="pcit0003" dnum="WO9711419A2"><text>WO9711419A2</text></patcit> relates to a synchronous multi-port random access memory having a plurality of memory arrays.
0004<patcit id="pcit0004" dnum="US4930066A"><text>US4930066A</text></patcit> relates to a multiport memory system.
0005<patcit id="pcit0005" dnum="US2007055810A1"><text>US2007055810A1</text></patcit> relates to a memory access control device and processing system having the same.
0006<patcit id="pcit0006" dnum="US5515523A"><text>US5515523A</text></patcit> relates to a method and apparatus for arbitrating conflicts by monitoring number of access requests per unit of time in multiport memory systems. <patcit id="pcit0007" dnum="US2002194424A1"><text>US2002194424A1</text></patcit> relates to a multiport memory, data processor and data processing system.
0007A wide variety of memory devices are in common use. One type of memory device that is becoming increasingly popular are memory devices that have a plurality of input/output ("I/O") ports. Prior art multi-port memory devices normally have a fixed memory capacity that is accessible through each port. For example, a 1Gb memory device having 4 ports would normally have 256Mb of storage accessible through each port. The fixed capacity per port approach is satisfactory for many applications. However, many applications require a memory device in which different memory access devices coupled to the memory device through respective ports having different data storage requirements. In such case, the tradeoff is either to have insufficient capacity available to some memory access devices or to have excessive capacity available to other memory access devices. Either approach results in some performance or cost disadvantages.
0008One solution to the above limitations of the fixed capacity per port approach may be to provide different fixed capacities for each of several ports. For example, in the above-described 1 Gb memory device having 4 ports, a processor may require 512Mb of capacity and would thus access the memory device through a port with 512Mb available, a baseband processor may require 256Mb of capacity and would thus access the memory device through a port with 256Mb available, and two other memory access devices may each require 128Mb of capacity and would thus access the memory device through respective ports with 128Mb accessible through each port. While this approach might be ideal for some applications, it may not be acceptable for other applications. For example, another user of the memory device might need a memory device with 256Mb accessible through each of the 4 ports or a memory device with 512Mb accessible through one port, 256Mb accessible through 2 ports, and no capacity accessible through the 4<sup>th</sup> port. While this approach could be alleviated to some extent by manufacturing memory devices having a wide variety of port configurations, this approach would require memory device manufacturers to design, manufacture, stock and sell a large number of different memory devices. The cost of this approach would undoubtedly result in such memory devices being relatively expensive.
0009There is therefore not an entirely acceptable solution for the need for multi-port memory devices having a wide variety of port configurations.
SUMMARY OF THE INVENTION
0010The present invention is defined in the appended claims to which reference should be made. Advantageous features are set out in the appended dependent claims. An embodiment of the invention is described in association with <figref idref="f0005">figure 4</figref>.
BRIEF DESCRIPTION OF THE DRAWINGS
0011<ul id="ul0001" list-style="none" compact="compact"><li><figref idref="f0001 f0002">Figures 1A-C</figref> are schematic drawings showing a multi-port memory device in which banks can be mapped to another port by bank consolidation.</li><li><figref idref="f0003">Figures 2A and 2B</figref> are schematic drawings showing a multi-port memory device in which banks can be mapped to another port by port consolidation.</li><li><figref idref="f0004">Figures 3A and 3B</figref> are schematic drawings showing a multi-port memory device in which banks can be mapped to another port by port consolidation.</li><li><figref idref="f0005">Figure 4</figref> is a block diagram of a multi-port memory device according to an embodiment of the invention.</li><li><figref idref="f0006">Figure 5</figref> is a block diagram of an embodiment of a Bank/Port circuit that may be used in the memory device of <figref idref="f0005">Figure 4</figref>.</li><li><figref idref="f0006">Figure 6</figref> is a block diagram of an embodiment of a Bank/Port consolidation control circuit that may be used in the Bank/Port circuit of <figref idref="f0006">Figure 5</figref>.</li><li><figref idref="f0007">Figure 7</figref> is a block diagram of another embodiment of a Bank/Port circuit that may be used in the memory device of <figref idref="f0005">Figure 4</figref>.</li></ul>
DETAILED DESCRIPTION
0012A memory device is shown in <figref idref="f0001 f0002">Figures 1A- 1C</figref>. As shown in <figref idref="f0001">Figure 1A</figref>, a memory device 10 includes 4 ports 12, 14, 16, 18 each of which can access two 128Mb banks 20, 22 of memory cells, which can be dynamic random access memory ("DRAM") cells, static random access memory ("SRAM") memory cells, flash memory cells, or any other type of presently existing or hereafter developed memory cells. The memory device 10 thus has a capacity of 1 Gb, and each port 12-18 can access 256Mb. The banks 20, 22 that are accessible from their respective port 12-18 are referred to herein as "native" banks.
0013As explained in greater detail below, the memory device is configurable by a user to alter the memory capacity that may be accessible through each of the ports 12-18. As shown in <figref idref="f0002">Figure 1B</figref>, the memory bank 22 native to port 14 can be mapped to the port 12, and the memory bank 20 native to the port 18 can be mapped to the port 16. The banks that have been mapped to another port are referred to herein as "non-native" banks. After the memory device 10 has been reconfigured, 384Mb are accessible to the ports 12, 16, and 128Mb of capacity are accessible to the ports 14, 18, as shown in <figref idref="f0002">Figure 1C</figref>. Thus, two native banks 20, 22 and one non-native bank 22 can be accessed through the port 12, two native banks 20, 22 and one non-native bank 20 can be accessed through the port 16, one native bank 20 can be accessed through the port 14, and one native bank 22 can be accessed through the port 18. Other configurations are, of course, possible. Mapping of a bank from one port to another is referred to herein as "bank consolidation."
0014As further shown in <figref idref="f0003">Figure 2A</figref>, both banks 20, 22 native to the port 12 can be mapped to the port 14, and both banks 20, 22 native to the port 18 can be mapped to the port 16. As a result, two native banks 20, 22 and two non-native banks 20, 22 can be accessed through the port 14, and two native banks 20, 22 and two non-native banks 20, 22 can be accessed through the port 16, as shown in <figref idref="f0003">Figure 2B</figref>. After the memory device 10 has been reconfigured, no memory cells can be accessed through the ports 12, 18. Thus, the memory device 10 may be reconfigured to be a two-port memory device having 512Mb accessible through each of the ports 14, 16. Mapping of all of the banks 20, 22 native to one port to a different port is referred to herein as "port consolidation."
0015Another example of port consolidation is shown in <figref idref="f0004">Figure 3A</figref>. As shown therein, both banks 20, 22 native to each of the ports 14-18 can be mapped to the port 12. As a result, two native banks 20, 22 and six non-native banks 20, 22 can be accessed through the port 12, as shown in <figref idref="f0004">Figure 3B</figref>. Thus, bank consolidation results in the memory device being a single-port memory device having 1Gb accessible through the port 12.
0016Although the memory device 10 shown in <figref idref="f0001 f0002 f0003 f0004">Figures 1A-3B</figref> has the same number ports and the same number of native banks for each port, different numbers of ports may be provided, and different numbers of banks are native to each port. Alternatively or in addition, the memory capacity of the banks native to each of several ports can vary from port to port. For example, one 64 Mb bank may be native to a first port, one 128 Mb bank may be native to a second port, one 256 Mb bank and one 32 Mb bank are native to a third port, one 256 Mb bank, one 128 Mb bank, and one 64 Mb bank are native to a fourth port, and one 64 Mb bank and one 32 Mb bank are native to a fifth port. Other native configurations, of course, may be used.
0017The reconfiguration of the memory device 10 may be accomplished using a variety of techniques. For example, in one embodiment, port consolidation may be accomplished by controlling all banks, both native and non-native, accessible through each port by a register (not shown) associated with the port to which the banks have been mapped. In contrast, in one embodiment, bank consolidation may be accomplished by controlling banks mapped to another port by a register (not shown) associated with the port from which the banks are mapped. However, in another embodiment, bank consolidation may be accomplished by controlling banks mapped to another port by a register (not shown) associated with the port to which the bank is mapped.
0018The mapping of banks to provide bank and port consolidation may also be accomplished by using devices other than a programmable register in examples which are useful for understanding the invention. For example, bank or port consolidation may be accomplished by selecting which banks to map by altering the manner in which bonding wires are connected to contact pads on a semiconductor substrate. However, the mapping of banks may be controlled by blowing a fuse or anti-fuse. The selection of which bank to map and the port to which it should be mapped may be controlled by tying an externally accessible terminal to a pre-defined voltage, such as V<sub>cc</sub> or ground. Other selection means can also be used.
0019One example showing the manner in which banks can be addressed after bank or port consolidation from port 1 into port 2 is shown in Table A, below: <tables id="tabl0001" num="0001"><table frame="all"><title><u>Table A</u></title><tgroup cols="3"><colspec colnum="1" colname="col1" colwidth="27mm" /><colspec colnum="2" colname="col2" colwidth="24mm" /><colspec colnum="3" colname="col3" colwidth="25mm" /><thead><row><entry align="center" valign="top"><b>Bank Address</b></entry><entry align="center" valign="top"><b>Bank</b></entry><entry align="center" valign="top"><b>Bank Source</b></entry></row></thead><tbody><row><entry align="center">0</entry><entry align="center">Native 0</entry><entry align="center">Port 0, Bank 0</entry></row><row><entry align="center">1</entry><entry align="center">Native 1</entry><entry align="center">Port 0, Bank 1</entry></row><row><entry align="center">2</entry><entry align="center">Non-Native 0</entry><entry align="center">Port 1, Bank 0</entry></row><row><entry align="center">3</entry><entry align="center">Non-Native 1</entry><entry align="center">Port1, Bank 1</entry></row></tbody></tgroup></table></tables>
0020As shown in Table A, when the banks of port 1 are mapped to port 0, the port 0 banks still maintain their port 0 and port 1 addresses. Thus, a bank address of 0 may still be used to address bank 0 of port 0, and a bank address of 1 may still be used to address bank 1 of port 0. However, if a bank address of 2 or 3 is applied to port 0, the banks of port 1 may be addressed. Specifically, as also shown in Table A, a bank address of 2 may be used to address bank 0 of port 1, and a bank address of 3 may be used to address bank 1 of port 1. A similar addressing scheme can be used for bank or port consolidation from any port to any other port.
0021A multi-port memory device 30 according to an embodiment of the invention is shown in <figref idref="f0005">Figure 4</figref>. The memory device 30 has 4 ports A-D, although other embodiments may have a number of ports less than or greater than 4. The ports A-D each have a combined unidirectional command/address ("C/A") 34 bus and a bidirectional data bus ("DATA") 36 coupled between its port and a switching circuit or a mapping circuit, such as respective Bank/Port circuits 40a-d. Each Bank/Port circuit is coupled not only to its respective native port, but also to each of the other ports. Thus, for example, the Bank/Port circuit 40a for Bank A is coupled not only to the C/A[A] and DATA [A] buses, but also to the C/A[B], DATA[B], C/A[C], DATA[C], C/A[D] and DATA[D] buses.
0022The Bank/Port circuits 40a-d are, in the embodiment shown in <figref idref="f0005">Figure 4</figref>, substantially identical to each other. An embodiment of the Bank/Port circuits 40a-d used as a switching circuit or mapping circuit is shown in <figref idref="f0006">Figure 5</figref>. The Bank/Port circuit 40 includes a respective Bank/Port consolidation control circuit 50 coupled to its respective Port[n] through a C/A[n] bus 52 and a DATA[n] bus 54 as well as to all of the ports, as explained above. The Bank/Port circuit 40 also includes two banks 56, 58 of memory cells, which may be referred to as Bank[n][0] and Bank[n][1], respectively, where the letter "n" designates the port to which the bank is native. The banks 56, 58 are coupled to the Bank/Port consolidation control circuit 50 through a DATA_native bus 60. Although the Bank/Port circuit 40a embodiment shown in <figref idref="f0006">Figure 5</figref> uses two banks for each port, a number of banks greater than or less than 2 may be used in other embodiments. The Bank/Port circuit 40a also includes a respective command decoder 62 and a respective address decoder 64, both of which are coupled to the Bank/Port consolidation control circuit 50 through a C/A_native bus 66.
0023The Bank/Port consolidation control circuit 50 according to one embodiment is shown in <figref idref="f0006">Figure 6</figref>. The Bank/Port consolidation control circuit 50 includes configuration registers 70 that store configuration data indicative of the manner in which any port or bank consolidation is to be accomplished. The configuration registers 70 generate a code indicative of consolidation data, which is passed to control/decode logic 74. The control/decode logic 74 decodes the configuration data from the configuration registers and generates control signals on bus 76 that cause steering logic 80 to map the banks 56, 58 (<figref idref="f0006">Figure 5</figref>) that are native to that port to the respective port to which they are to be mapped. In some embodiments, the configuration registers 70 can be dynamically programmed by the control/decode logic 74 receiving data through the C/A[n] bus indicative of how the configuration registers should be programmed (which is why the connection of the C/A[n] bus to the logic 74 is shown in dashed lines). The control/decode logic 74 can then program the configuration registers 70 accordingly. However, in other embodiments the programming of the configuration registers 70 is static, which the configuration registers 70 being formed by anti-fuses, fuses or other programmable elements that are programmed either during fabrication by a manufacturer or afterwards by a user.
0024With further reference to <figref idref="f0006">Figure 6</figref>, the steering logic 80 responds to the control signals generated by the control/decode logic 74 to couple the commands from either the native C/A[n] bus or one of the non-native C/A[n] buses to the C/A_native bus, and the data to and from either the native DATA[n] bus or one of the non-native DATA[n] buses to the DATA_native bus. The steering logic 80 can be implemented, for example, as sets of multiplexers. As explained above, the DATA native bus is coupled to the native banks 56, 58 (<figref idref="f0006">Figure 5</figref>) of memory cells, and the C/A_native bus 66 is coupled to the command decoder 62 and the address decoder 64. The steering logic 80 can therefore effectively map either or both of the native banks 56, 58 to any of the four ports depending on the needs of each port.
0025Another embodiment of the Bank/Port circuits 40a-d is shown in <figref idref="f0007">Figure 7</figref>. The Bank/Port circuit 40 includes a respective Bank/Port consolidation control circuit 100 coupled to its respective Port[n] through the C/A[n] bus 52 and the DATA[n] bus 54. The Bank/Port consolidation control circuit 100 is also coupled to all of the ports, as explained above with reference to <figref idref="f0005">Figure 4</figref>. The Bank/Port circuit 40 also includes two banks 104, 106 of memory cells, which again may be referred to as Bank[n][0] and Bank[n][1], respectively. The Bank/Port consolidation control circuit 100 is somewhat similar to the Bank/Port consolidation control circuit 50 of <figref idref="f0006">Figure 6</figref>. Specifically, the Bank/Port consolidation control circuit 100 also includes the configuration registers 70 that store configuration data as well as the control/decode logic 74 that decodes the configuration data from the configuration registers 70 and generates control signals on bus 76 that cause steering logic 110 to map the banks 104, 106 that are native to that port to the respective port. The Bank/Port consolidation control circuit 100 also includes the command decoder 62 and the address decoder 64 coupled to the steering logic 110 through the C/A_native bus 66. The steering logic 110 also selectively couples the C/A bus 54 to the C/A_native bus 66 or to the non-native C/A buses. However, the steering logic 110 differs from the steering logic 80 shown in <figref idref="f0006">Figure 6</figref> in that it selectively couples the DATA[n] bus 54 only to the DATA_native bus 60. The steering logic 110 also generates 2-bit Sel[n+1][1:0], Sel[n+2][1:0], Sel[n+3][1:0] signals that cause data to be coupled from one of the non-native banks to the DATA[n] bus 54. Specifically, the Bank/Port circuits 40 includes a data switch 120 that includes a first set of pass gates 124a,b,c and a second set of pass gates 126a,b,c. The pass gates 124, 126 may be in the native banks 104, 106, respectively, and may be coupled to global I/O buses 134, 136 in the banks 104, 106, respectively. As understood by one skilled in the art, global I/O buses or lines are commonly found in memory arrays for coupling all of the data in the array to a circuit that outputs the data from the memory device. Each of the pass gates 124a-c is switched by the "0" bit of a respective Sel signal to selectively couple a global I/O bus 140a-c of a respective non-native Bank[0] to the global I/O bus 134, which is coupled to the DATA_native bus. For example, in response to the Sel[n+2] signal, the pass gate 124b couples the global I/O[n+2][0] bus from Bank[n+1][0] to the native global I/O bus[n][0], which is, in turn, coupled to the DATA[n] port through the Bank/Port consolidation control circuit 100. In a similar manner, each of the pass gates 126a-c is switched by the "1" bit of a respective Sel signal to selectively couple a global I/O bus 140a-c of a respective non-native Bank[1] to the global I/O bus 136, which is coupled to the DATA_native bus. Although the pass gates 124, 126 of the switch 120 are located in the banks in the embodiment of <figref idref="f0007">Figure 7</figref>, it will be understood that the bass gates 124, 126 or other switching circuits can be at other locations in other embodiments.
0026Although the present invention has been described with reference to the disclosed embodiments, persons skilled in the art will recognize that changes may be made in form and detail without departing from the scope of the appended claims. Such modifications are well within the skill of those ordinarily skilled in the art. Accordingly, the invention is not limited except as by the appended claims.
Contents5
7 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2007055810A1 | Cites | United States of America | Examiner |
| WO9711419A2 | Cites | World Intellectual Property Organization (WIPO) | – |
| US4930066A | Cites | United States of America | – |
| US5515523A | Cites | United States of America | – |
| US2002194424A1 | Cites | United States of America | – |
| US2007055810A1 | Cites | United States of America | – |
| US2008049536A1 | Cites | United States of America | – |
| US6334175B1 | Cites | United States of America | – |
16 members in 7 offices
Priority claims7
| Document | Office | Kind | Date |
|---|---|---|---|
| 43261009 | United States of America | A | |
| 432610 | United States of America | – | |
| 2010027867 | United States of America | W | |
| WO2010US27867 | – | – | – |
| US20090432610 | – | – | – |
| 432610 | – | – | – |
| US2010027867 | – | – | – |
Members16
| Document | Office | Kind | |
|---|---|---|---|
| US2010281227A1 | United States of America | A1 | |
| WO2010126658A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2010126658A3 | World Intellectual Property Organization (WIPO) | A3 | |
| TW201115588A | Taiwan Province of China | A | |
| KR20120002553A | Republic of Korea | A | |
| EP2425346A2 | European Patent Office (EPO) | A2 | |
| CN102414669A | China | A | |
| US8250312B2 | United States of America | B2 | |
| JP2012525662A | Japan | A | |
| US2012314523A1 | United States of America | A1 | |
| EP2425346A4 | European Patent Office (EPO) | A4 | |
| KR101417240B1 | Republic of Korea | B1 | |
| US8930642B2 | United States of America | B2 | |
| TWI484498B | Taiwan Province of China | B | |
| CN102414669B | China | B | |
| EP2425346B1This record | European Patent Office (EPO) | B1 |
77 legal events, as 9 offices reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | Office | |
|---|---|---|---|
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed because of non-payment of the annual feeLapsedMM | MM | BE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent ceasedCeasedPL | PL | CH | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| No opposition filedOpposition26N | 26N | EP | |
| No opposition filed within time limitOppositionORIGINAL CODE: 0009261PLBE | PLBE | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: NO OPPOSITION FILED WITHIN TIME LIMITSTAA | STAA | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| No opposition filed against granted patent, or epo opposition proceedings concluded without decisionGrantedR097 | R097 | DE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Deletion acc. to par. 5 (withdrawal of the translation of the ep patent)MK05 | MK05 | AT | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent invalid in the netherlands as no translation has been filedMP | MP | NL | |
| Invalidated european patentMG4D | MG4D | LT | |
| European patents granted designating irelandGrantedFG4D | FG4D | IE | |
| Dpma publication of mentioned ep patent grantGrantedR096 | R096 | DE | |
| European patent takes effect as a national patent in ch/liEP | EP | CH | |
| Reference to at number (ep patent validated in austria)REF | REF | AT | |
| Designated contracting statesAK | AK | EP | |
| European patent grantedGrantedFG4D | FG4D | GB | |
| (expected) grantORIGINAL CODE: 0009210GRAA | GRAA | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: THE PATENT HAS BEEN GRANTEDSTAA | STAA | EP | |
| Intention to grant announcedINTG | INTG | EP | |
| Intention to grant announced (deleted)INTC | INTC | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| Grant fee paidORIGINAL CODE: EPIDOSNIGR3GRAS | GRAS | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: GRANT OF PATENT IS INTENDEDSTAA | STAA | EP | |
| Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deletedORIGINAL CODE: EPIDOSDIGR1GRAJ | GRAJ | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: EXAMINATION IS IN PROGRESSSTAA | STAA | EP | |
| Intention to grant announcedINTG | INTG | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: GRANT OF PATENT IS INTENDEDSTAA | STAA | EP | |
| First examination report despatched17Q | 17Q | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: EXAMINATION IS IN PROGRESSSTAA | STAA | EP | |
| Supplementary search report drawn up and despatchedA4 | A4 | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Request for extension of the european patent (deleted)DAX | DAX | EP | |
| Request for examination filed17P | 17P | EP | |
| Designated contracting statesAK | AK | EP | |
| Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI | PUAI | EP |
Numbers
- Publication
- 2425346
- Publication, DOCDB
- 2425346
- Publication, EPODOC
- EP2425346
- Application
- 10770092
- Application, DOCDB
- 10770092
- Application, EPODOC
- EP20100770092
Titles3
- German
- SPEICHERVORRICHTUNGEN MIT MEHREREN ANSCHLÜSSEN UND VERFAHREN
- English
- MULTI-PORT MEMORY DEVICES AND METHODS
- French
- DISPOSITIFS ET PROCÉDÉS DE MÉMOIRE À PORTS MULTIPLES
Classification
- CPC, 5
- G06F12/0646
- G06F12/02
- G06F13/1668
- G06F2212/1041
- G11C7/1075
- IPC, 6
- G06F12 02
- G06F12 06
- G06F12 08
- G06F13 16
- G06F13 40
- G11C7 10
Designated states36
- Contracting states, 36
- Austria
- Belgium
- Bulgaria
- Switzerland
- Cyprus
- Czechia
- Germany
- Denmark
- Estonia
- Spain
- Finland
- France
- United Kingdom
- Greece
- Croatia
- Hungary
- Ireland
- Iceland
- Italy
- Liechtenstein
- Lithuania
- Luxembourg
- Latvia
- Monaco
and 12 moreShow fewer
- North Macedonia
- Malta
- Netherlands (Kingdom of the)
- Norway
- Poland
- Portugal
- Romania
- Sweden
- Slovenia
- Slovakia
- San Marino
- Türkiye
