US8166207B2

Querying a device for information

Summary by NHIP

Processor write query handling

The apparatus receives a write query from a peripheral device requesting vendor specific information and transmits that information via a second write query. Ordering rules of the interconnect protocol terminate upon receiving the initial query, rendering the response independent of those rules.

Claim Score by NHIP

Read claim 9, the broadest

Abstract

In one embodiment, the present invention includes a method for receiving in a processor complex a first write request from a peripheral device, obtaining information of the processor complex responsive to the first write request, and transmitting a second write request from the processor complex to the peripheral device including the information. Other embodiments are described and claimed.

US8166207B2, drawing sheet 1 — Sheet 1 of 7

Term

2.7 yearsleft in the term

Expires 27 May 2029, including 240 days of term adjustment.

14 claims: 3 independent, 11 dependent

1
An apparatus comprising:a processor complex including: an interface to communicate with a peripheral device via an interconnect, the interface to receive a write query from the peripheral device to perform a write operation to a first location of the processor complex, wherein the write query includes an indicator to request vendor specific information of the processor complex;a logic coupled to the first location, wherein the logic is to access the vendor specific information responsive to the write query and to generate a second write query to transmit the vendor specific information to the peripheral device, wherein ordering rules of a communication protocol of the interconnect terminate with respect to the write query when it is received in the logic, and the second write query is independent of the write query with respect to the ordering rules;a plurality of cores coupled to the logic to perform operations responsive to instructions;and a memory controller coupled to the logic to communicate with a memory.
9
Broadest claimClaim Score 65, broad(NHIP)A system comprising:a processor complex including an interface to communicate with a peripheral device via an interconnect, a plurality of cores to perform operations responsive to instructions, and a memory controller to communicate with a memory, the interface to receive a write request from the peripheral device to write information to the processor complex, wherein the write request is to be handled by the processor complex as if it were a read request such that the processor complex is to transmit a second write request to the peripheral device that includes vendor specific information of the processor complex;the peripheral device coupled to the processor complex via the interconnect, wherein the peripheral device is to generate the write request on initialization of the system;and the memory coupled to the processor complex.
12
A system comprising:a processor complex including: an interface to couple to a peripheral device via an interconnect, the interface to receive a first write query from the peripheral device to perform a write operation to a first location of the processor complex, the first write query to request vendor specific information of the processor complex;a logic coupled to the first location to access the vendor specific information responsive to the first write query and to generate a second write query to transmit the vendor specific information to the peripheral device, wherein the first and second write queries avoid data dependency and ordering rules of a communication protocol of the interconnect for a read request;and a plurality of cores coupled to the logic to perform operations responsive to instructions;a memory controller coupled to the logic to communicate with a memory;and the memory coupled to the processor complex.

Independent claims3

29 paragraphs in 3 sections, as filed

BACKGROUND

In modern computer systems, various components communicate with each other according to a given communication protocol. For example, a peripheral device may communicate with a processor of a system via an intermediate interface such as a controller hub coupled between the device and processor. An example form of such communication is according to a so-called Peripheral Component Interconnect Express (PCI Express™ (PCIe™)) communication protocol.

Typical transactions include write and read transactions, interrupts and so forth. Typically, read transactions are used by a peripheral device to obtain data from a memory. However, such devices generally do not communicate read transactions directly to a processor, such as to query information regarding the processor. This is so, as it is unnatural and difficult to allow such a query, as an in-out dependency would occur and further would raise ordering issues in the processor. Thus while a processor may include various identification information such as processor identifier (ID) information, fusing information, state information or configuration information regarding its capabilities and so forth, it is generally difficult or impossible for devices coupled to the processor to obtain such information.

BRIEF DESCRIPTION OF THE DRAWINGS

<figref idrefs="DRAWINGS">FIG. 1</figref> is a flow diagram of a method in accordance with one embodiment of the present invention.

<figref idrefs="DRAWINGS">FIG. 2</figref> is a block diagram of a portion of a system in accordance with one embodiment of the present invention.

<figref idrefs="DRAWINGS">FIG. 3</figref> is a block diagram of a processor complex in accordance with an embodiment of the present invention.

<figref idrefs="DRAWINGS">FIG. 4</figref> is a block diagram of a processor complex in accordance with another embodiment of the present invention.

<figref idrefs="DRAWINGS">FIG. 5</figref> is a block diagram of a system in accordance with one embodiment of the present invention.

<figref idrefs="DRAWINGS">FIG. 6</figref> is a block diagram of a system in accordance with another embodiment of the present invention.

DETAILED DESCRIPTION

In various embodiments, in order to enable devices coupled to a processor complex to obtain information directly from the processor complex, a data flow including write-write transactions may be accommodated. Specifically, register access vendor defined messages (RAVDMs, or in short VDMs) of a write transaction from a device such as a peripheral device may be used to request information from the processor complex. Responsive to this write request, the processor complex may obtain and provide the requested information back to the peripheral device, using a similar write request transaction. In this way, complexities associated with a read request can be avoided. Such complexities include data dependency issues, as well as ordering issues. Still further, such reads to a processor generally do not occur, as a memory controller or other controller device do not provide for peer cycles to allow reads to internal devices of a processor complex. Historically, upstream configuration read/write (R/W) accesses from a peripheral device to a root (e.g., processor) complex have not been supported.

In one embodiment, such write-write transactions may be used with usage models to obtain configuration information regarding a processor complex, such as may occur during power up or initialization of a system. Specifically, in one such implementation a peripheral controller hub (PCH) may request so-called stock keeping unit (SKU) information that is associated with the processor complex. Such SKU information may provide details regarding a processor's configuration as it is configured at the factory. That is, certain processors may be manufactured having various features such as a number of cores, available operating frequencies, additional functional units, modes of operation and so forth. However, during manufacture different processors may be configured differently. For example, programmable fuses may be used to have only certain portions of a given processor's functionality enabled. In this way, a manufacturer can easily fabricate many lots of devices having the same semiconductor processing operations (e.g., masks and so forth) and then in the factory, each processor may be individually programmed to enable/disable various features. In this way, the commonly manufactured devices can be sold at different price levels depending on the enabled features.

Thus in some use models, a PCH or other peripheral device coupled to such a processor may, upon startup, seek to determine the processor's capabilities. Thus using write-write transactions in accordance with an embodiment of the present invention, the peripheral device can obtain the configuration and capability information, which may include ID information, such as processor vendor, processor type (i.e., segment targeted), processor generation (i.e., year produced), features enabled/disabled, maximum power dissipated, typical latencies, and so forth.

Referring now to <figref idrefs="DRAWINGS">FIG. 1</figref>, shown is a flow diagram of a method in accordance with one embodiment of the present invention. As shown in <figref idrefs="DRAWINGS">FIG. 1</figref>, method 100 may be performed by a processor complex to receive a write request and handle it accordingly. As shown in <figref idrefs="DRAWINGS">FIG. 1</figref>, method 100 may begin by receiving a write query to a predetermined location (block 110). For example, an interface of the processor complex may receive the write request from an interconnect that is coupled between the processor complex and a peripheral device such as a PCH. This write request may be a RAVDM write to a predetermined bus/device/function (BDF & BAR) along with an offset. Still further, in addition to this address information for the write request, the request may further include data, which may or may not be used, as described further below. As one example, the BDF/Bar and offset may be used to identify a queue within the processor complex in which the request is to be stored, for example, a vendor defined message (VDM) queue.

Still referring to <figref idrefs="DRAWINGS">FIG. 1</figref>, based on this location information the write request may be routed to that location (block 120). Thus for example the write request may be forwarded through various circuitry of the processor complex to the write queue.

Later, the information of the write query may then be read from the targeted location (block 130). For example, the entry of the VDM queue for the write request may be processed when it reaches the top of the queue. This information may be used to handle the write request from the peripheral device as if it were a read request to access desired information of the processor complex. For example, the offset information that is in the entry may be used to indicate from where the requested information is to be obtained. Accordingly, the desired information may be obtained from that location based on the information requested (block 140). While the scope of the present invention is not limited in this regard, as one example, this offset may predetermine the information to be obtained. In such implementations, the offset may operate to trigger microcode or other hardware, software or firmware to obtain the desired information. This information may correspond to one or more of a set of configuration registers present in the processor complex. Such configuration registers may include a processor ID register, one or more capabilities registers that include information regarding the enabling or disabling of various processor features, bus speeds or so forth. As will be discussed below, other manners of obtaining information may be implemented using data received with the write query.

Next, when this request information has been obtained, a write request that is thus responsive to the incoming write request may be formed (block 150). As one example, this write request may be a similar RAVDM message to write the obtained information back to the peripheral device. Thus, at block 160 the write request may be output from the processor complex to the requesting device. Alternatively, at block 160 the write request may be output from the processor complex to a different device determined via a CPU complex register. Accordingly, this write request acts as a response to the incoming write query. Thus the multiple write-write transactions have the same effect as an incoming read request and associated completion message back to requesting device, without the complexities of ordering requirements, dependencies, additional internal datapath complexities and so forth of a given communication protocol. While described with this particular implementation in the embodiment of <figref idrefs="DRAWINGS">FIG. 1</figref>, the scope of the present invention is not limited in this regard.

Embodiments can be implemented in many different systems and processor types. However, certain implementations may be used in connection with a platform having a processor complex, which may be a single die integrated circuit including multiple processor cores, caches, associated logic, memory controller, interface controller and so forth.

Referring now to <figref idrefs="DRAWINGS">FIG. 2</figref>, shown is a block diagram of a portion of a system in accordance with one embodiment of the present invention. As shown in <figref idrefs="DRAWINGS">FIG. 2</figref>, system 200 includes a processor complex 210 that is coupled to a memory 260 which, in one embodiment may be dynamic random access memory (DRAM), and a PCH 280. As shown in <figref idrefs="DRAWINGS">FIG. 2</figref>, processor complex 210 may include a plurality of cores 220a-220d (generically core 220). Each core may be associated with a corresponding cache memory 225a-225d (generically cache 225). In addition, processor complex 210 includes uncore logic 230, which may include various logic of the processor that is not resident in the cores such as certain interface and control logic. Also present within processor complex 210 is an input/output (I/O) interface 240 that provides an interface to an interconnect 245, which in one embodiment may be a direct media interface (DMI) or another point-to-point interconnect that is coupled between processor complex 210 and PCH 280. In addition, processor complex 210 further includes a memory controller 250 that provides an interface between the complex and memory 260. While shown with these limited components for ease of illustration understand that additional components may be present within processor complex 210, such as fixed function units, other processing units and so forth.

As further shown in <figref idrefs="DRAWINGS">FIG. 2</figref>, uncore logic 230 may include various components that may aid in handling of write-write transactions. More specifically, information that may be requested by a peripheral device may be present in a set of configuration or memory mapped registers 232. As described above, such registers may include various information regarding the identification and capabilities of processor complex 210. When a request that is received by uncore logic 230 via an arbiter 234, it is stored in a vendor defined message (VDM) queue 235. When this entry of the queue reaches the top or head of the queue, uncore logic 230 obtains the information from registers 232 and sends it through a multiplexer 236, after which it is then queued for storage in a VDM queue 238. When output to an arbiter 239, a write request message including the desired information is arbitrated with other outgoing requests. Note that in the illustration of <figref idrefs="DRAWINGS">FIG. 2</figref>, only a single input to arbiters 234 and 239 is shown. However understand that in various implementations these arbiters may be configured to arbitrate among various incoming requests received from different cores, logic, interfaces and so forth.

Thus when an incoming RAVDM write query is received from PCH 280 (and more particularly from a manageability engine 285 within), the requests may be provided through I/O interface 240 to uncore logic 230 for handling. Then, responsive to this query a corresponding write query may be transmitted from uncore logic 230 with requested information for transmission through I/O interface 240 back to PCH 280. While shown with this limited detail in the embodiment of <figref idrefs="DRAWINGS">FIG. 2</figref> for ease of illustration, understand the scope of the present invention is not limited in this aspect.

Referring now to <figref idrefs="DRAWINGS">FIG. 3</figref>, shown is a further illustration of a processor complex in accordance with an embodiment of the present invention. As shown in <figref idrefs="DRAWINGS">FIG. 3</figref>, further details regarding uncore logic 230 are provided. Specifically, <figref idrefs="DRAWINGS">FIG. 3</figref> shows a data flow of write-write transactions in accordance with an embodiment of the present invention. The initiation of a RAVDM write query (1) from PCH 280 is received in processor complex 210 through I/O interface 240 (2) that causes writing of the query into VDM queue 235 (3). Note that at this point in the transactions, the write query from the PCH has been consumed and thus ordering rules with respect to a communication protocol (e.g., a PCIe protocol) are terminated. When the requested information of the write query is retrieved, a second write query (4) is formed that is then transmitted from uncore logic 230 (5) and through I/O interface 240 to PCH 280 (6). It is noted that this second write request is an independently generated and ordered transaction such that no dependencies or ordering issues exist with respect to the previous write transaction.

In other implementations, rather than receiving a write request that causes obtaining and sending of responsive data from a predetermined location (based on bus/device/function/bar and offset), other implementations may provide a more flexible manner for handling write-write transactions. For example, a RAVDM write with data may be received. As described above, this data may be stored, e.g., in a VDM queue. When accessed from the VDM queue, the data may be used as an index for information to be written back to the peripheral device. Note that this index may directly access information or may be used in connection with a doorbell mechanism, further described below. In yet other embodiments, the data received with a write query can be used, operated on (e.g., incremented, encrypted or so forth) and returned in the response write query. For example, in one such implementation a processor complex may receive a ping signal with a first value (e.g., a value of one). Then when transmitting the corresponding write query, this data value may be incremented and returned with a value of two to a requesting peripheral device. Note that in some implementations such process may occur in reverse, namely where the processor complex sends the ping signal and the peripheral device sends a ping return with the updated data value.

Still further, in some embodiments it is possible to receive multiple write requests from a peripheral device and based on these requests obtain data from locations indicated by the write requests themselves. That is, instead of the predetermined transfer of specific configuration or other information responsive to a single write request to a predetermined BDF/BAR and offset, other implementations may use a so-called doorbell register to access information indicated by one or more write requests. As one such example, a first write request from a peripheral device may include a BDF/BAR and offset to this doorbell register which is written with data that may contain information regarding the desired response from the processor complex. For example, the data may include information regarding a response BDF/Bar and offset, information source (e.g., fuses, registers, hidden registers or so forth), an indication of the amount of data to return, attributes such as routing hints and action to be taken or so forth. Such actions may be to take an action on triggering write data. For example, the return data may be encrypted, a data value sent with the write request may be incremented and returned with the corresponding reply write request, or another action may be performed, e.g., a requested processor action, which upon completion may cause the reply write request to be sent. Such information may be sent in multiple write requests, where the second or later request triggers the doorbell register in which the data of an earlier write request is stored.

Referring now to <figref idrefs="DRAWINGS">FIG. 4</figref>, shown is a block diagram of a processor complex in accordance with another embodiment of the present invention. As shown in <figref idrefs="DRAWINGS">FIG. 4</figref>, system 400 includes a processor complex 410. Processor complex 410 may include similar components to that of <figref idrefs="DRAWINGS">FIG. 2</figref>, namely cores 420a-420d, caches 425a-425d, uncore logic 430, an I/O interface 440, and an MCH 450. However, in this implementation uncore logic 430 includes a doorbell register 435 that is configured to receive an incoming write request from PCH 480 through arbiter 434. After storage of the initial data from the first write request, a second write transaction from PCH 480 may access this information and use it as an index to obtain information from a particular one or more configuration registers 432. In turn, the information may be sent through multiplexer 436 and stored in VDM queue 438, until it is sent from arbiter 439 to interface 440.

Embodiments may be implemented in many different system types. Referring now to <figref idrefs="DRAWINGS">FIG. 5</figref>, shown is a block diagram of a system in accordance with an embodiment of the present invention. As shown in <figref idrefs="DRAWINGS">FIG. 5</figref>, multiprocessor system 500 is a point-to-point interconnect system, and includes a processor complex 571 including a first processor 570 and a chipset 590. As shown in <figref idrefs="DRAWINGS">FIG. 5</figref>, first processor 570 and a second processor 580 are coupled via a point-to-point interconnect 550. As shown in <figref idrefs="DRAWINGS">FIG. 5</figref>, each of processors 570 and 580 may be multicore processors, including first and second processor cores (i.e., processor cores 574a and 574b and processor cores 584a and 584b). Each processor may further include uncore logic 575 and 585, which may handle an incoming write request from a peripheral device as if it were a read request to obtain and provide configuration information of the processor.

Still referring to <figref idrefs="DRAWINGS">FIG. 5</figref>, first processor 570 further includes a memory controller 572 and point-to-point (P-P) interfaces 576 and 578. Similarly, second processor 580 includes a memory controller 582 and P-P interfaces 586 and 588. As shown in <figref idrefs="DRAWINGS">FIG. 5</figref>, memory controllers 572 and 582 couple the processors to respective memories, namely a memory 532 and a memory 534, which may be portions of main memory (e.g., a dynamic random access memory (DRAM)) locally attached to the respective processors. First processor 570 and second processor 580 may be coupled to a chipset 590 via P-P interconnects 552 and 554, respectively. As shown in <figref idrefs="DRAWINGS">FIG. 5</figref>, chipset 590 includes P-P interfaces 594 and 598.

Furthermore, chipset 590 includes an interface 592 to couple chipset 590 with a high performance graphics engine 538. In turn, chipset 590 may be coupled to a first bus 516 via an interface 596. As shown in <figref idrefs="DRAWINGS">FIG. 5</figref>, various I/O devices 514 may be coupled to first bus 516, along with a bus bridge 518 which couples first bus 516 to a second bus 520. Various devices may be coupled to second bus 520 including, for example, a keyboard/mouse 522, communication devices 526 and a data storage unit 528 such as a disk drive or other mass storage device which may include code 530, in one embodiment. Further, an audio I/O 524 may be coupled to second bus 520.

Referring now to <figref idrefs="DRAWINGS">FIG. 6</figref>, shown is a block diagram of a system in accordance with another embodiment of the present invention. As shown in <figref idrefs="DRAWINGS">FIG. 6</figref>, system 400′ may be a front side bus (FSB) system, or other processor interconnect-based system in which a processor 420 is coupled to a chipset 410 including uncore logic 430 via a processor interconnect 415. In other respects system 400′ may be adapted similar to that of <figref idrefs="DRAWINGS">FIG. 4</figref>. Note however the presence of an external graphics card 465, also coupled to chipset 410.

Embodiments may be implemented in code and may be stored on a storage medium having stored thereon instructions which can be used to program a system to perform the instructions. The storage medium may include, but is not limited to, any type of disk including floppy disks, optical disks, compact disk read-only memories (CD-ROMs), compact disk rewritables (CD-RWs), and magneto-optical disks, semiconductor devices such as read-only memories (ROMs), random access memories (RAMs) such as dynamic random access memories (DRAMs), static random access memories (SRAMs), erasable programmable read-only memories (EPROMs), flash memories, electrically erasable programmable read-only memories (EEPROMs), magnetic or optical cards, or any other type of media suitable for storing electronic instructions.

While the present invention has been described with respect to a limited number of embodiments, those skilled in the art will appreciate numerous modifications and variations therefrom. It is intended that the appended claims cover all such modifications and variations as fall within the true spirit and scope of this present invention.

Contents3

Every citation, both waysCites: the store holds 8 of 9

Citations
Document	Relation	Office	Cited during
US8896560B2	Cited by	United States of America	Applicant
US8884906B2	Cited by	United States of America	Applicant
JP2002358251A	Cites	Japan	Applicant
US2004028199A1	Cites	United States of America	Search report
JP2006215873A	Cites	Japan	Applicant
US2009210637A1	Cites	United States of America	Search report
US2010122009A1	Cites	United States of America	Search report
US7464207B2	Cites	United States of America	Search report
JPH0749855A	Cites	Japan	Applicant
JPH10207812A	Cites	Japan	Applicant
United Kingdom Intellectual Property Office, Examination Report Under Section 18(3) issued on Dec. 6, 2010 in U.K. patent application No. GB0916679.4.	Non-patent	–	Applicant
Japanese Patent Office, Office Action mailed Jul. 16, 2011 in Japanese application No. 2009-222876.	Non-patent	–	Applicant

26 members in 9 offices

This recordMember, by publication datePriority claim

Priority claims2

Priority claims
Document	Office	Kind	Date
28618708	United States of America	A	2008-09-29
US20080286187	–	–	–

Members26

Family members, oldest first
Document	Office	Kind
US4821211A	United States of America	A	1989-04-11
EP0317480A2	European Patent Office (EPO)	A2	1989-05-24
JPH01144117A	Japan	A	1989-06-06
BR8806005A	Brazil	A	1989-08-08
EP0317480A3	European Patent Office (EPO)	A3	1990-10-10
CA1306066C	Canada	C	1992-08-04
EP0317480B1	European Patent Office (EPO)	B1	1994-06-08
DE3850051D1	Germany	D1	1994-07-14
DE3850051T2	Germany	T2	1994-12-01
GB0916679D0	United Kingdom	D0	2009-11-04
GB2463781A	United Kingdom	A	2010-03-31
US2010082852A1	United States of America	A1	2010-04-01
JP2010086536A	Japan	A	2010-04-15
DE102009043263A1	Germany	A1	2010-04-29
CN101714127A	China	A	2010-05-26
TW201025014A	Taiwan Province of China	A	2010-07-01
GB2463781B	United Kingdom	B	2011-03-02
US8166207B2This record	United States of America	B2	2012-04-24
JP4964931B2	Japan	B2	2012-07-04
US2012179842A1	United States of America	A1	2012-07-12
CN101714127B	China	B	2012-07-18
US2012185615A1	United States of America	A1	2012-07-19
US8386668B2	United States of America	B2	2013-02-26
US8396996B2	United States of America	B2	2013-03-12
TWI421691B	Taiwan Province of China	B	2014-01-01
DE102009043263B4	Germany	B4	2016-11-17

54 transactions on the USPTO file

Allowed after 2 non-final rejections, 1 final rejection and 1 appeal.

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

Over time

Point at a mark for the transaction

Transactions

Prosecution transactions, newest first
	Event	Code
2023-09-20	Payment of Maintenance Fee, 12th Year, Large EntityM1553	M1553
2019-10-10	Payment of Maintenance Fee, 8th Year, Large EntityM1552	M1552
2012-04-24	Recordation of Patent Grant MailedPGM/	PGM/
2012-04-24	Patent Issue Date Used in PTA CalculationAllowedPTAC	PTAC
2012-04-04	Issue Notification MailedAllowedWPIR	WPIR
2012-03-27	Dispatch to FDCD1935	D1935
2012-03-26	Application Is Considered Ready for IssuePILS	PILS
2012-03-23	Response to Reasons for AllowanceREAS	REAS
2012-03-23	Issue Fee Payment VerifiedN084	N084
2012-03-23	Issue Fee Payment ReceivedIFEE	IFEE
2012-02-15	Mail PUB Notice of non-compliant IDSMM327-B	MM327-B
2012-02-14	PUB Notice of non-compliant IDSM327-B	M327-B
2012-02-09	Information Disclosure Statement consideredIDSC	IDSC
2012-02-09	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2012-01-11	Mail Notice of AllowanceAllowedMN/=.	MN/=.
2012-01-04	Notice of Allowance Data Verification CompletedAllowedN/=.	N/=.
2012-01-03	Reasons for AllowanceEX.R	EX.R
2011-12-28	Date Forwarded to ExaminerFWDX	FWDX
2011-12-28	Mail Appeals conf. Reopen Prosec.MAPCR	MAPCR
2011-12-21	Pre-Appeal Conference Decision - Reopen ProsecutionAPCR	APCR
2011-10-04	Information Disclosure Statement consideredIDSC	IDSC
2011-10-04	Information Disclosure Statement (IDS) FiledM844	M844
2011-10-04	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2011-09-02	Request for Pre-Appeal Conference FiledAP.C	AP.C
2011-09-02	Notice of Appeal FiledN/AP	N/AP
2011-06-06	Mail Final Rejection (PTOL - 326)Final rejectionMCTFR	MCTFR
2011-06-03	Final RejectionFinal rejectionCTFR	CTFR
2011-03-21	Date Forwarded to ExaminerFWDX	FWDX
2011-03-11	Response after Non-Final ActionA...	A...
2011-01-21	Information Disclosure Statement consideredIDSC	IDSC
2011-01-21	Information Disclosure Statement (IDS) FiledM844	M844
2011-01-21	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2010-12-23	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF
2010-12-20	Non-Final RejectionNon-final rejectionCTNF	CTNF
2010-10-13	Date Forwarded to ExaminerFWDX	FWDX
2010-10-12	Response after Non-Final ActionA...	A...
2010-07-21	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF
2010-07-19	Non-Final RejectionNon-final rejectionCTNF	CTNF
2010-07-09	Date Forwarded to ExaminerFWDX	FWDX
2010-07-02	Response to Election / Restriction FiledELC.	ELC.
2010-06-04	Mail Restriction RequirementMCTRS	MCTRS
2010-06-03	Restriction/Election RequirementCTRS	CTRS
2010-05-24	Case Docketed to Examiner in GAUDOCK	DOCK
2010-04-01	PG-Pub Issue NotificationPG-ISSUE	PG-ISSUE
2009-08-28	Case Docketed to Examiner in GAUDOCK	DOCK
2009-08-27	Case Docketed to Examiner in GAUDOCK	DOCK
2009-01-29	IFW TSS Processing by Tech Center CompleteTSSCOMP	TSSCOMP
2008-11-18	Application Dispatched from OIPEOIPE	OIPE
2008-10-27	Sent to Classification ContractorPGPC	PGPC
2008-10-27	Filing ReceiptFLRCPT.O	FLRCPT.O
2008-10-14	Cleared by OIPE CSRL194	L194
2008-10-09	IFW Scan & PACR Auto Security ReviewSCAN	SCAN
2008-09-30	Initial Exam Team nnIEXX	IEXX
2008-09-09	Oath or Declaration Filed (Including Supplemental)C602	C602

7 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
2023-09-20	Maintenance fee paymentMAFP	MAFP
2019-10-10	Maintenance fee paymentMAFP	MAFP
2015-10-07	Fee paymentFPAY	FPAY
2012-04-04	Information on status: patent grantGrantedPATENTED CASESTCF	STCF
2011-11-01	Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP	FEPP
2009-01-22	AssignmentAS	AS
2009-01-22	AssignmentAS	AS