US9048827B2

Flexible logic unit

Summary by NHIP

Flexible Logic Unit

The flexible logic unit arranges programmable tiles in a matrix where latch banks accept configuration data sequentially down columns. Odd and even non-recovering clocks drive alternating latch and lock flip-flop banks to prevent data overwriting during tile-by-tile programming.

Claim Score by NHIP

Read claim 4, the broadest

Abstract

A flexible logic unit (FLU) is targeted to be primarily, but not exclusively, used as an embedded field programmable gate array (EFPGA). The unit is comprised of a plurality of programmable building block tiles arranged in an array of columns and rows of tiles, and programmed by downloading a bit stream, done tile by tile and column by column, using latches that are sequentially programmed and locked using a lock bit as part of the bit stream provided. A scheme of odd and even clocks prevent latch transparency and ensures that once data has arrived at its destination it is properly locked, not to be unintentionally overwritten.

US9048827B2, drawing sheet 1 — Sheet 1 of 7

Term

7.3 yearsleft in the term

Expires 13 January 2034.

12 claims: 5 independent, 7 dependent

1
A flexible logic unit comprising:a first clock and a second clock, the first clock and the second clock being non-recovering clocks;a matrix having a plurality of tiles arranged in columns and rows, each tile having at least one latch bank therein, each latch bank within any one column having an identical number of one or more latches therein, each tile having configurable logic configurable responsive to configuration data stored in the respective latch bank, the latches in each latch bank being clocked in unison for that latch bank, each of the latch banks being arranged to accept configuration data from an immediately previous latch bank in that column, such that one latch bank is clocked by the first clock if an immediately previous latch bank in the same column is clocked by the second clock or by the second clock if an immediately previous latch bank in the same column is clocked by the first clock, each column of the matrix being configured to accept configuration data in a first configuration data flow direction within the column;a plurality of lock flip-flops arranged in columns, each lock flip-flop corresponding to a respective latch bank of a respective column of the matrix, the plurality of lock flip-flops configured to accept a lock bit in a lock bit flow direction that is opposite to the configuration data flow direction, one lock flip-flop being clocked by the first clock if an immediately previous lock flip-flop in the same column is clocked by the second clock or by the second clock if an immediately previous lock flip-flop in the same column is clocked by the first clock;and a control interface to accept at least a configuration word for each latch bank and associated lock flip-flop, the interface configured to separate, for each column, configuration data and lock bits data from the configuration words.
3
An integrated circuit comprising a plurality of electronic circuits where at least one of the electronic circuits is a flexible logic unit comprising:a first clock and a second clock, the first clock and the second clock being non-recovering clocks;a matrix having a plurality of tiles arranged in columns and rows, each tile having at least one latch bank therein, each latch bank within any one column having an identical number of one or more latches therein, each tile having configurable logic configurable responsive to configuration data stored in the respective latch bank, the latches in each latch bank being clocked in unison for that latch bank, each of the latch banks being arranged to accept configuration data from an immediately previous latch bank in that column, such that one latch bank is clocked by the first clock if an immediately previous latch bank in the same column is clocked by the second clock or by the second clock if an immediately previous latch bank in the same column is clocked by the first clock, each column of the matrix being configured to accept configuration data in a first configuration data flow direction within the column;a plurality of lock flip-flops arranged in columns, each lock flip-flop corresponding to a respective latch bank of a respective column of the matrix, the plurality of lock flip-flops configured to accept a lock bit in a lock bit flow direction that is opposite to the configuration data flow direction, one lock flip-flop being clocked by the first clock if an immediately previous lock flip-flop in the same column is clocked by the second clock or by the second clock if an immediately previous lock flip-flop in the same column is clocked by the first clock;and a control interface to accept at least a configuration word for each latch bank and associated lock flip-flop, the interface configured to separate, for each column, configuration data and lock bits data from the configuration words.
4
Broadest claimClaim Score 42, average(NHIP)A method for loading data in a flexible logic unit, the flexible logic unit comprising at least a column having at least two tiles therein, each tile comprising at least one latch bank and a corresponding lock bit, the method comprising:receiving a configuration word comprising configuration data and a lock bit data;selecting one column from the at least a column to provide the configuration data thereto;providing the configuration data to the selected column from one end of the column such that the configuration data flows in a direction from a first tile of the at least two tiles to a second tile of the at least two tiles;providing the lock bit data to a lock bit column associated with the selected column such that the lock bit flows with respect to the at least two tiles in an opposite direction to the flow of the configuration data;and providing a first clock and a second clock, the first clock and the second clock being non-recovering clocks, such that the first clock is provided to at least a first latch bank and the second clock is provided to a second latch bank, the data of the first latch bank being provided to the second latch bank.
5
A flexible logic unit comprising:a plurality of latch banks for storing configuration data for at least one field programmable gate array, the plurality of latch banks being arranged in at least one column;a plurality of lock flip-flops equal in number to the plurality of latch banks, each lock flip-flop being configured to lock configuration data in a respective latch bank responsive to a lock bit therein;first and second non-recovering clocks for clocking configuration data into the at least one column in a first direction and clocking lock bits into the at least one column in a second direction opposite the first direction;the first and second non-recovering clocks clocking configuration data to alternate latch banks, respectively, until locked therein by a lock bit;and the first and second non-recovering clocks clocking lock bits through alternate lock flip-flops, respectively.
9
A method of configuring a flexible logic unit comprising:providing a plurality of latch banks for storing configuration data for at least one field programmable gate array, the plurality of latch banks being arranged in at least one column;a plurality of lock flip-flops equal in number to the plurality of latch banks, each lock flip-flop being configured to lock configuration data in a respective latch bank responsive to a lock bit therein;providing first and second non-recovering clocks for clocking configuration data into the at least one column in a first direction and clocking lock bits into the at least one column in a second direction opposite the first direction;using first and second non-recovering clocks, to clock configuration data to alternate latch banks, respectively, until locked therein by a lock bit;and using the first and second non-recovering clocks, to clock lock bits through alternate lock flip-flops, respectively.

Independent claims5

23 paragraphs in 4 sections, as filed

0001This application claims the benefit of U.S. Provisional Patent Application No. 61/883,443 filed Sep. 27, 2013.

BACKGROUND OF THE INVENTION

00021. Field of the Invention

0003The invention generally relates to field programmable gate arrays (FPGAs) and more particularly to the programming of FPGAs, and even more particularly with programming of embedded FPGAs (EFPGAs).

00042. Prior Art

0005In today's world the use of integrated circuits (ICs) is ubiquitous, and they can be found in practically every device, even in the regular household. A particular branch of ICs is that of field programmable gate arrays (FPGAs) which are designed to be configured in the field, using some kind of a hardware description language (HDL). The language describes the specific configuration of components of the FPGA so that it is operated as desired by a user making use of the IC. One of the main advantages of FPGAs is the ability to perform partial or full reconfiguration of the device even when it is already connected as part of a system, if such capabilities are kept enabled for the device. In certain cases, reconfiguration takes place as part of the normal operation of the device as it may be necessary to perform different functions at different times.

0006In some cases FPGAs have therein embedded components such as microprocessors, and other peripheral devices to provide enhanced functionality. This integration leads to lower costs and reduced failures of the system. In other cases, certain ICs integrate therein features of FPGAs, creating embedded FPGAs (EFPGAs) to allow a certain degree of flexibility to a user to customize a component in a way that fits specific user design needs. Regardless of which FPGA is used, the challenge of the FPGA is in its programming that is a combination of a program and hardware support to allow the FPGA to be configured as desired. Such programming support in the prior art has a significant overhead associated thereto, which is a problem, especially in the case of EFPGAs where the overhead may become prohibitive for implementation or being cost effective. Implementations typically use D-type flip flops (DFFs) which require word lines and bit lines for a sequential approach, as well as row and column decoders.

0007Therefore, in view of the deficiencies of the prior art it would be advantageous to provide a solution for FPGAs in general, and EFPGAs in particular, that would reduce the overhead associated with the presence of programming support for the configurations of such FPGAs and EFPGAs.

BRIEF DESCRIPTION OF THE DRAWINGS

0008The subject matter that is regarded as the invention is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other objects, features and advantages of the invention will be apparent from the following detailed description taken in conjunction with the accompanying drawings.

0009<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram of a tiled field programmable gate array (FPGA) of a flexible logic unit (FLU) having a configuration lock signal according to an embodiment.

0010<figref idref="DRAWINGS">FIG. 2</figref> is an illustrative diagram of the programming of the tiled FPGA having a configuration lock signal according to an embodiment.

0011<figref idref="DRAWINGS">FIG. 3</figref> is a block diagram of latches of the tiled FPGA clocked by two non-recovering clocks according to an embodiment.

0012<figref idref="DRAWINGS">FIG. 4</figref> is a block diagram of the locking mechanism of the tiled FPGA clocked by two non-recovering clocks according to an embodiment.

0013<figref idref="DRAWINGS">FIG. 5</figref> is an illustrative timing diagram of the programming of the tiled FPGA clocked by two non-recovering clocks and having a configuration lock signal according to an embodiment.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

0014It is important to note that the embodiments disclosed by the invention are only examples of the many advantageous uses of the innovative teachings herein. In general, statements made in the specification of the present application do not necessarily limit any of the various claims. Moreover, some statements may apply to some inventive features but not to others. In general, unless otherwise indicated, singular elements may be in plural and vice versa with no loss of generality. In the drawings, like numerals refer to like parts through several views.

0015A flexible logic unit (FLU) is targeted to be primarily, but not exclusively, used as an embedded field programmable gate array (EFPGA). The unit is comprised of a plurality of programmable building block tiles comprising configurable logic (e.g., 114 in <figref idref="DRAWINGS">FIG. 1</figref>) arranged in an array of columns and rows of tiles, and programmed by downloading configuration data, done tile by tile and column by column, using latches organized in latch banks (e.g., 112 in <figref idref="DRAWINGS">FIG. 1</figref>) that are sequentially programmed, each from the immediately previous latch. The latches are locked from being further written to using a lock bit, for example in the form of a flip flop (FF) as part of the configuration words provided. A scheme of odd and even clocks prevent latch transparency racing conditions and ensures that once configuration data has arrived at its destination it is properly locked, not to be unintentionally overwritten.

0016Therefore, according to the principles of the invention a FPGA is partitioned to multiple tiles, which may or may not be identical, containing elements that may be programmed with a configuration word. Instead of D-type flip flops (DFFs), i.e., devices that propagate an input D to its output Q on the edge of the clock, latches are organized in latch banks, where a latch propagates its input D to its output Q when the clock is, for example, at a logical high. This configuration allows for the relaxation of the clock skew constraints typically associated with the use of DFFs, and further provides for a smaller area of the latch in comparison to a DFF. However, the nature of a latch requires the use of a non-overlapping clock to avoid races, as well as a lock mechanism to ensure that once data arrived at a latch it remains there until the latch is unlocked. A latch bank may contain one or more latches. The use of latches further eliminates the need, according to an embodiment, for word lines and bit lines for the sequential approach and further eliminates the need for row and column decoders.

0017Reference is now made to <figref idref="DRAWINGS">FIG. 1</figref> that shows an exemplary and non-limiting block diagram 100 of a tiled field programmable gate array (FPGA) 110 of a flexible logic unit (FLU) having a configuration lock signal 120-31 according to an embodiment. Each tile 110-c-r of the tiled FPGA 110, where ‘c’ is an integer having values from 1 to C and where ‘r’ is an integer having values from 1 to R, comprises one or more latch banks, for example latch banks 112-1 through 112-4, of latch bank element 112 as shown in the enlargement of tile 110-1-1. A latch bank may contain one or more latches, however the number of latches in a latch bank of any one of the latch bank elements 112 in a column has to be identical, i.e., 31 latches in latch bank 112-1 requires that all other latches in element 112 of 110-1-1 as well as any of the latch bank elements 112 of that particular column have the same number of latches in each latch bank. Control interface 120 receives, for example, a configuration word of 32 bits, of which 31 bits 120-30-0 are used to provide configuration data to the latches and one bit as a locking bit. As can be seen, the locking bits flow within a column ‘c’ in an opposite direction to that of the configuration data of the same column, according to an embodiment. Specifically, according to an embodiment, the tiles, each containing configurable FPGA elements 114 of the partitioned FPGA, are programmed within a column, tile by tile, and only once one column has been completely programmed, another column may be programmed. This simplifies the requirements on the programming overhead circuitry. It should be further noted that each column of tiles is programmed independently of any other column of tiles, that is, only the selected column for programming is programmed. Moreover, if a single latch bank is to be reprogrammed, it is necessary to program the entire column of latch banks of the column of tiles as no random access to any latch bank is provided according to the embodiments.

0018<figref idref="DRAWINGS">FIG. 2</figref> depicts an exemplary and non-limiting illustrative diagram 200 of the programming of the tiled FPGA 110 having a configuration lock signal according to an embodiment. The configuration data, shown on the left, may be stored, for example, in a memory, and is contained, merely for example purposes, in a 32-bit configuration word comprising 31 bits of configuration data and one lock bit. As noted with respect of <figref idref="DRAWINGS">FIG. 1</figref>, one column of bits, 220, is used for the lock signal purposes while the other bits 230 of the configuration word are used as configuration data to load a latch of a tile in a sequential order. Hence, configuration words 240-1-1 are used for the programming purposes of tile 110-1-1 (the first ‘-1’ designating the column the tile is in and the second ‘-1’ designating the row the tile is in); configuration words 240-1-r are used for the programming purposes of tile 110-1-r; configuration words 240-1-r+1 are used for the programming purposes of tile 110-1-r+1; configuration words 240-1-R is used for the programming purposes of tile 110-1-R, i.e., the last tile of the first column; configuration words 240-2-1 is used for the programming purposes of tile 110-2-1, i.e., the first tile of the second column; and, configuration words 240-C-R is used for the programming purposes of tile 110-C-R, i.e., the last tile of the last column. Furthermore, the flow of the lock bits 220 is opposite to that of the configuration words 240. It should be noted that the values of a lock bit in a particular configuration word is independent of the content of the particular configuration word and does not correspond thereto. It should be further noted that though the example shows that each tile has four latch banks in a tile, this should not be viewed as limiting on the invention. Each latch bank element 112 of a tile may have one or more latch banks therein, independent of the number of latch banks in any other tile of the column, as long as the number of latches in each of the latch banks is the same within a column of tiles. It should be noted that the lock bit needs to be changed from ‘0’ to ‘1’ when configuration data destined for the latch bank at the top of the column reaches its destination. From there on the lock bit data remains at a value of ‘1’ until all configuration data is locked in its respective latch bank. Furthermore, as the clocks continue clocking the lock bits continue down the column until the final lock bit is set to ‘1’ corresponding to the time where the last configuration data of the column is loaded into the respective latch bank.

0019In order to prevent the phenomenon of latch transparency (also known as a race condition) a scheme of two non-recovering clocks are used. <figref idref="DRAWINGS">FIG. 3</figref> describes an exemplary and non-limiting diagram 300 of latches of the tiled FPGA clocked by two non-recovering clocks 310, 320 according to an embodiment. Non-recovering clocks are two or more clocks where there at no times there is more than one clock which is in its active state. Such clocks are also known as non-overlapping clocks. The clocks are designed such that data moves from one latch bank, comprising one of more latches, to an immediately subsequent latch, for example from the output of latch bank 334 into latch bank 332 responsive to clock signal clk_odd 320. Latch bank 334 gets updated with data responsive to clock signal clk_even 310. The clocks clk_even 310 and clk_odd 320 being non-recovering clocks ensure that data does not race through the plurality of latch banks of column ‘c’ impacted solely by the delay characteristics of the latches. It should be understood that the latch bank elements, for example latch bank element 330-c-r, contains configuration data for its respective configurable FPGA elements 114 of the respective tile, for example, the tile in column ‘c’ and row ‘r’. Overall, the operation is such that the writing into the sequence of latch banks that is done by moving data in one direction (as shown upwards) in the column. It should be noted that though four latch banks are shown, any number of latch banks may be used with respect of each tile as long as a subsequent latch bank receives a different clock, e.g. clk_odd 320, if the immediately previous latch bank received the other clock, e.g., clk_even 310. When connecting tiles within a column of tiles, which also requires connecting of the last latch bank of a previous tile to the first latch bank of a current tile, the same requirement exists, i.e., if the latch bank of the pervious tile received one clock, for example, clk_even 310, then the first latch bank of the current tile must be connected to the other clock, for example, clk_odd 320, and vice versa. This will ensure proper operation within the column. Moreover, according to an embodiment, it is not necessary that each column has the same number of latch banks and it is possible that each column will hold a different number of latch banks, or for that matter, have the same number of latch banks, but distributed in any desired way between the tiles of the column, for as long as each tile has at least one such latch bank.

0020<figref idref="DRAWINGS">FIG. 4</figref> depicts an exemplary and non-limiting block diagram 400 of the locking mechanism for a single column of tiles of the tiled FPGA clocked by two non-recovering clocks, clk_even 440 and clk_odd 430, according to an embodiment. In the exemplary case a column of six latch banks 420-0 through 420-5 is shown. In this exemplary case, latch_bank_0 is part of latch bank element 330-c-r-1, latch_bank_1 through latch_bank_4 are part of latch bank element 330-c-r, and latch_bank_5 is part of latch bank element 330-c-r+1, where each such latch bank element 330 used for the configuration of FPG elements 114 of a corresponding tile in a column. The latch banks are so connected that data from one latch bank is provided to the immediately following latch bank such that the content of each of the latches of one latch bank are transferred to the immediately preceding corresponding latches of the preceding latch bank using the clocking scheme of the non-recovering clocks. For each latch bank of latch_bank_0 through latch_bank_5 there is a corresponding DFF 410, for example DFF 410-0 for latch_bank_0. The DFFs 410 are used to transfer the lock bit corresponding to each latch bank, that enables or disables, as the case may be, the latching capability of data into a corresponding latch bank. While the configuration data is fed in one direction of the column, in the case shown data flows from, for example, latch_bank_1 to latch_bank_0, the lock bits move in an opposite direction, in the case shown from DFF 410-0 to DFF 410-1. This ensures proper locking of the data in the latch banks and avoids the need of word and row lines in the implementation, thereby saving on decoding circuitry. It should be further understood that the lock bits have to be reset (i.e., receive a value of ‘0’) to initialize the circuit, using reset signal 450, as they have to begin at a known value that leaves the latch banks unlocked as a starting point.

0021Reference is now made to <figref idref="DRAWINGS">FIG. 5</figref> where an exemplary and non-limiting illustrative timing diagram 500 depicting the programming of a portion of a column of a tiled FPGA clocked by two non-recovering clocks and having a configuration lock signal according to an embodiment. According to this example it is necessary to load the latch bank elements 310, having a latch element 310-c-r containing four latch banks latch_bank_1 through latch_bank_4, where latch_bank_4 receives configuration data from latch_bank_5 of a previous latch bank element, and where latch_bank_1 provides data to latch_bank_0 of an immediately subsequent latch bank element. In this way an even numbered latch bank overrides the content of the subsequent odd numbered latch bank and an odd numbered latch bank overrides the content of an even numbered latch bank. This process continues until such time that a latch bank is locked by setting its lock flip-flop to ‘1’ thereby preventing any future override by content from a previous latch bank, and as further explained herein. The data loaded, in this example, is designated for simplicity by ‘a’, ‘b’, . . . ‘f’ respectively, which represent, for example, the 31 bits of data previously discussed. Hence the timing diagram 500 illustrates the content of a column of latch banks and lock bits at different points in time. The values shown as ‘x’ stand for either meaningful data that has not yet reached its designated latch bank or don't care values of latch banks that are going to be overwritten by valid data, as the case may be.

0022Accordingly at T0 the value ‘a’ is provided at the input end of the configuration data with a ‘0’ lock value at the lock bit input. At T1, the value ‘a’ is latched into latch_bank_5. At T2, the value at the data input changes to ‘b’, and the lock bit value provided is ‘0’, while the value ‘a’ provided from latch_bank_5 is latched into latch_bank_4. In T3 the value ‘b’ is latched into latch_bank_5 and the value ‘a’ is latched into latch_bank_3. This continues until at T6 the data value is changed to ‘d’ and lock bit supplied is ‘1’ as it is time to lock the latch_bank_0 with the value ‘a’, which subsequently happens at T7. Thereafter, data from a previous latch bank, in this case data from latch_bank_1, does not get latched into the latch of latch_bank_0, as it is now locked. Eventually, all data gets locked at its respective latch bank. In the diagram 500, bold cells depicted cell having locked values therein. For further non-limiting illustration one may consider the lock bit providing a value ‘1’ at T7 to the column, i.e., position 510-T7, where the lock bit of latch_bank_0 becomes ‘1’, thereby locking configuration word(s) ‘a’ in that latch bank, while adding configuration word(s) ‘e’ into latch_bank_5. Similarly, at the lock bit providing a value ‘1’ at T9 to a subsequent column, i.e., position 510-T9, where the lock bit of latch_bank_0 is also ‘1’ being pushed down the column, thereby locking configuration word(s) ‘c’ in latch_bank_2, while maintaining the latch_bank_0 and latch_bank_1 locked with their respective data ‘a’ and ‘b’. From the other side, i.e., at the bottom of the column, adding configuration word(s) ‘e’ into latch_bank_5. While moving configuration word(s) ‘d’ further up the column. Hence, the flow of the lock bit data down the lock bit column successively locks the correct configuration data in each respective latch bank. In order to function properly, the lock bit value has to be set to ‘1’ in the sequence of configuration words when the configuration data for the top latch bank is reached, and thereafter remain set at ‘1’ until the entire column of latch banks is properly locked.

0023All examples and conditional language recited herein are intended for pedagogical purposes to aid the reader in understanding the principles of the invention and the concepts contributed by the inventor to furthering the art, and are to be construed as being without limitation to such specifically recited examples and conditions. Moreover, all statements herein reciting principles, aspects, and embodiments of the invention, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future, i.e., any elements developed that perform the same function, regardless of structure. Specifically, in one embodiment the disclosed FLU may be implemented as a stand-alone integrated circuit (IC) containing one or more FLUs. In another embodiment the IC may contain one or more FLUs as well as other circuitry may it be analog, digital or any combination thereto.

Contents4

Every citation, both ways

Citations
Document	Relation	Office	Cited during
US10116311B2	Cited by	United States of America	Applicant
US10454480B2	Cited by	United States of America	Applicant
US2003128050A1	Cites	United States of America	Applicant
US2003212940A1	Cites	United States of America	Applicant
US2005040850A1	Cites	United States of America	Applicant
US2005084076A1	Cites	United States of America	Applicant
US2005121698A1	Cites	United States of America	Applicant
US2006006904A1	Cites	United States of America	Search report
US2007247189A1	Cites	United States of America	Search report
US2012213268A1	Cites	United States of America	Applicant
US2014111247A1	Cites	United States of America	Search report
US6191613B1	Cites	United States of America	Applicant
US6502050B1	Cites	United States of America	Applicant
US6675306B1	Cites	United States of America	Applicant
US6825690B1	Cites	United States of America	Applicant
US6981167B2	Cites	United States of America	Applicant
US7049846B1	Cites	United States of America	Applicant
US7159204B2	Cites	United States of America	Applicant
US7203842B2	Cites	United States of America	Applicant
US7375553B1	Cites	United States of America	Applicant
US7545168B2	Cites	United States of America	Applicant
US20030128050A1	Cites	United States of America	Applicant
US20030212940A1	Cites	United States of America	Applicant
US20050040850A1	Cites	United States of America	Applicant
US20050084076A1	Cites	United States of America	Applicant
US20050121698A1	Cites	United States of America	Applicant
US20060006904A1	Cites	United States of America	Search report
US20070247189A1	Cites	United States of America	Search report
US20120213268A1	Cites	United States of America	Applicant
US20140111247A1	Cites	United States of America	Search report

6 priority claims, no other members on record

This recordMember, by publication datePriority claim

Priority claims6

Priority claims
Document	Office	Kind	Date
201361883443	United States of America	P	2013-09-27
201361883443	United States of America	P	2013-09-27
201414153760	United States of America	A	2014-01-13
61883443	–	–	–
US201361883443P	–	–	–
US201414153760	–	–	–

31 transactions on the USPTO file

Allowed without a rejection on record.

Non-final rejections: 0
Final rejections: 0
RCEs: 0
Appeals: 0

Over time

Point at a mark for the transaction

Transactions

Prosecution transactions, newest first
	Event	Code
2015-08-31	Application ready for PDX access by participating foreign officesCCRDY	CCRDY
2015-06-02	Recordation of Patent Grant MailedPGM/	PGM/
2015-06-02	Patent Issue Date Used in PTA CalculationAllowedPTAC	PTAC
2015-05-13	Issue Notification MailedAllowedWPIR	WPIR
2015-05-05	Dispatch to FDCD1935	D1935
2015-05-04	Application Is Considered Ready for IssuePILS	PILS
2015-04-30	Issue Fee Payment VerifiedN084	N084
2015-04-30	Issue Fee Payment ReceivedIFEE	IFEE
2015-04-02	PG-Pub Issue NotificationPG-ISSUE	PG-ISSUE
2015-01-30	Mail Notice of AllowanceAllowedMN/=.	MN/=.
2015-01-29	Notice of Allowance Data Verification CompletedAllowedN/=.	N/=.
2015-01-16	Reasons for AllowanceEX.R	EX.R
2014-10-27	Information Disclosure Statement consideredIDSC	IDSC
2014-08-29	Case Docketed to Examiner in GAUDOCK	DOCK
2014-07-29	Case Docketed to Examiner in GAUDOCK	DOCK
2014-05-12	Application Dispatched from OIPEOIPE	OIPE
2014-05-12	FITF set to YES - revise initial settingFTFS	FTFS
2014-01-28	Application Is Now CompleteCOMP	COMP
2014-01-28	Change in Power of Attorney (May Include Associate POA)PA..	PA..
2014-01-28	Sent to Classification ContractorPGPC	PGPC
2014-01-28	Filing ReceiptFLRCPT.O	FLRCPT.O
2014-01-27	Applicant Has Filed a Verified Statement of Small Entity Status in Compliance with 37 CFR 1.27SMAL	SMAL
2014-01-14	Cleared by OIPE CSRL194	L194
2014-01-13	Reference capture on IDSRCAP	RCAP
2014-01-13	Information Disclosure Statement (IDS) FiledM844	M844
2014-01-13	Patent Term Adjustment - Ready for ExaminationPTA.RFE	PTA.RFE
2014-01-13	Applicants have given acceptable permission for participating foreignAPPERMS	APPERMS
2014-01-13	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2014-01-13	IFW Scan & PACR Auto Security ReviewSCAN	SCAN
2014-01-13	Entity status set to undiscounted (initial default setting or status change)BIG.	BIG.
2014-01-13	Initial Exam Team nnIEXX	IEXX

6 legal events, as the office reported them to INPADOC

Over the term

Point at a mark for the event

Events

Legal events, newest first
	Event	Code
2024-03-28	Fee payment procedureENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP	FEPP
2022-12-02	Maintenance fee paymentMAFP	MAFP
2018-12-03	Maintenance fee paymentMAFP	MAFP
2016-01-29	AssignmentAS	AS
2015-05-13	Information on status: patent grantGrantedPATENTED CASESTCF	STCF
2014-01-14	AssignmentAS	AS

Flexible logic unit

Summary by NHIP

Claim Score by NHIP

Abstract