Interface configuration system and method
Summary by NHIP
Interface Configuration System
The method designs electrical interconnect devices by entering instrument IDs, slot numbers, and interface component identifiers into a computer. It determines compatibility by checking manufacturer websites or local storage and displays errors if components are incompatible.
Claim Score by NHIP
Abstract
A computer-implemented method for designing an electrical interconnect device. The method comprises the steps of entering an instrument ID into a computer through an input device, entering a slot number corresponding to the instrument ID into the computer through the input device, entering an interface component identifier into the computer through the input device, associating the interface component identifier with the instrument ID and the slot number in a database in the computer, generating and displaying on a computer display a preview of a configuration of an electrical interconnect device, wherein the preview comprises a table showing the instrument ID, the slot number, the interface component identifier and an association between the interface component ID and the instrument ID, and wherein the interface component ID shown in the preview comprises a link to data associated with the interface component, and displaying in a separate window on the computer display the data associated with the interface component.

Term
Projected expiry 1 March 2031.
- Priority
- Filed
- Granted
- Today
- Projected expiry
13 claims: 2 independent, 11 dependent
- 1Broadest claimClaim Score 33, narrow(NHIP)A computer-implemented method for designing an electrical interconnect device, said method comprising the steps of:entering an instrument ID into a computer through an input device;entering a slot number corresponding to said instrument ID into said computer through said input device;entering an interface component identifier into said computer through said input device;determining whether data associated with said interface component identifier is available from a website of a manufacturer of an interface component identified by said interface component identifier;if data associated with said interface component identifier is available from said website, determining whether an interface component identified by said interface component identifier is compatible with an instrument identified by said instrument ID using said data from said website;if data associated with said interface component identifier is not available from said website, determining whether an interface component identified by said interface component identifier is compatible with an instrument identified by said instrument ID using said data retrieved from local storage;if said interface component identified by said interface component identifier is not compatible with said instrument identified by said instrument ID, displaying an error message on a display;if said interface component identified by said interface component identifier is compatible with said instrument identified by said instrument ID, associating said interface component identifier with said instrument ID and said slot number in a database, wherein said association comprises a result of said determination of whether an interface component identified by said interface component identifier is compatible with an instrument identified by said instrument ID;and generating and displaying on said display a preview of a configuration of an electrical interconnect device, wherein said preview comprises a table showing said instrument ID, said slot number, said interface component identifier and an association between said interface component ID and said instrument ID, and wherein said interface component ID shown in said preview comprises a link to data associated with said interface component.
- 10A computer-implemented method for designing an electrical interconnect device, said method comprising the steps of:displaying on a display connected to a computer a request form requesting a plurality of instrument ID's from a user;providing a plurality of instrument ID's entered on said request form to a server;retrieving data associated with a first of said plurality of instrument ID's from a website of a manufacturer of an instrument associated with said first instrument ID;retrieving data associated with a second of said plurality of instrument ID's from a local storage connected to said server;determining whether a plurality of instruments identified by said plurality of instrument ID's are compatible with each other using said data associated with said first instrument ID and said data associated with said second instrument ID;generating on said server a configuration database corresponding to said plurality of instrument ID's entered on said request form, wherein said database comprises results of said determining whether a plurality of instruments identified by said plurality of instrument ID's are compatible with each other;associating a slot number with each of said plurality of instrument ID's in said configuration database;populating said configuration database in said server with a plurality of component identifiers;associating each of said plurality of component identifier with one of said instrument ID's and a slot number in said configuration database;generating and displaying on a display a preview of a configuration based upon data in said configuration database;and providing on said preview a link to data associated with a displayed instrument ID.
Independent claims2
37 paragraphs in 6 sections, as filed
CROSS-REFERENCE TO RELATED APPLICATIONS
0001The present application claims the benefit of the filing date of U.S. Provisional Patent Application Ser. No. 61/230,973 filed by the present inventors on Aug. 3, 2009.
0002The aforementioned provisional patent application is hereby incorporated by reference in its entirety.
STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT
0003None.
BACKGROUND OF THE INVENTION
00041. Field of the Invention
0005The present invention relates to a systems and methods for configuring interface systems for automatic test equipment.
00062. Brief Description of the Related Art
0007Interface systems for automatic test equipment are typically composed of many different items potentially from many different manufacturers integrated together into a system. A typical interface system would have one or more card chassis, receivers, test adapters (also known as “ITA's”), instrument connections, terminal block cables, modules, patchcords and pins. The system also could include various external instruments.
0008In the past, the various component parts or pieces of an interface system commonly were selected and perhaps assembled by a service provider sometimes referred to as an “integrator.” The integrator would perform research to ensure that selected component parts of an interface system were compatible.
0009In recent years, a new XML-based standard for automatic test equipment, referred to as “Automatic Test Markup Language” or “ATML,” has emerged in the test and measurement industry. See, “ATML—The Standard for Interfacing Test System Components Using XML,” National Instruments (2006); “Draft Trial-Use Standard for Automatic Test Markup Language (ATML) for Exchanging Automatic Test Equipment and Test Information via XML,” IEEE P1671/D2 (December, 2005); and “AML (Automatic Test Markup Language),” The Test Savvy Engineer, (Oct. 1, 2007). ATML is a cooperative effort to define a collection of XML schemes to represent test information such as test programs, test asset interoperability, and unit under test (“UUT”) test data.
SUMMARY OF THE INVENTION
0010In a preferred embodiment, the present invention is a computer-implemented method for designing an electrical interconnect device. The method comprises the steps of entering an instrument ID into a computer through an input device, entering a slot number corresponding to the instrument ID into the computer through the input device, entering an interface component identifier into the computer through the input device, associating the interface component identifier with the instrument ID and the slot number in a database in the computer, generating and displaying on a computer display a preview of a configuration of an electrical interconnect device, wherein the preview comprises a table showing the instrument ID, the slot number, the interface component identifier and an association between the interface component ID and the instrument ID, and wherein the interface component ID shown in the preview comprises a link to data associated with the interface component; and displaying in a separate window on the computer display the data associated with the interface component. In various embodiments, the displayed data associated with the interface component may be retrieved from a database in a storage or from a website or server of, for example, a manufacturer or distributor of the interface component.
0011The method may further comprise steps of generating, displaying on the computer, and/or printing a price quotation for the configuration. Still further, the method may have means, such as the generation and sending of an electronic mail message, to provide the generated price quotation for the configuration to a customer.
0012In another embodiment, the present invention is a computer-implemented method for designing an electrical interconnect device. The method comprises the steps of displaying on a display connected to a computer a request form requesting a plurality of instrument ID's from a user, providing a plurality of instrument ID's entered on the request form to a server, generating on the server a configuration database corresponding to the plurality of instrument ID's entered on the request form, associating a slot number with each of the plurality of instrument ID's in the configuration database, populating the configuration database in the server with a plurality of component identifiers, associating each of the plurality of component identifier with one of the instrument ID's and a slot number in the configuration database and generating and displaying on a computer display a preview of a configuration based upon data in the configuration database. The method may further comprise the step of providing on the preview a link to data associated with a displayed instrument ID. Still further, the method may comprise the step of displaying as an overlay on the preview the data associated with a displayed instrument ID.
0013Still other aspects, features, and advantages of the present invention are readily apparent from the following detailed description, simply by illustrating a preferable embodiments and implementations. The present invention is also capable of other and different embodiments and its several details can be modified in various obvious respects, all without departing from the spirit and scope of the present invention. Accordingly, the drawings and descriptions are to be regarded as illustrative in nature, and not as restrictive. Additional objects and advantages of the invention will be set forth in part in the description which follows and in part will be obvious from the description, or may be learned by practice of the invention.
BRIEF DESCRIPTION OF THE DRAWINGS
0014For a more complete understanding of the present invention and the advantages thereof, reference is now made to the following description and the accompanying drawings, in which:
0015<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram of an exemplary system of a preferred embodiment of the present invention;
0016<figref idref="DRAWINGS">FIG. 2</figref> is a flow chart of the method of an interface system configurator in accordance with a preferred embodiment of the present invention.
0017<figref idref="DRAWINGS">FIG. 3</figref> is a diagram of a blank user interface of an interface system configurator in accordance with a preferred embodiment of the present invention.
0018<figref idref="DRAWINGS">FIG. 4</figref> is a diagram of an interface configuration preview in accordance with a preferred embodiment of the present invention.
0019<figref idref="DRAWINGS">FIG. 5</figref> is a diagram of an interface configuration preview with an instrument data link opened in accordance with a preferred embodiment of the present invention.
0020<figref idref="DRAWINGS">FIG. 6</figref> is a diagram of an interface configuration preview with a receiver data link opened in accordance with a preferred embodiment of the present invention.
0021<figref idref="DRAWINGS">FIG. 7</figref> is a diagram of a request form open in accordance with a preferred embodiment of the present invention.
0022<figref idref="DRAWINGS">FIG. 8</figref> is a diagram of a display provided to a Configuration Administrator during generation of a quotation in accordance with a preferred embodiment of the present invention.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
0023The interface configuration system of the present invention provides for a web-based approach to interface configuration and design in which a configuration request can be configured and displayed in a user-friendly layout for the customer. A preferred embodiment of the present invention provides for a request to be submitted via an on-line form and then configuring a system meeting the request and providing a display showing horizontal and vertical relationships between various components in the configuration. The present invention provides many benefits, including but not limited to, allowing organization of part numbers to assemble and communicate a desired configuration, keyword hinting to assist in developing a configuration request, displaying a product information window to show additional information about a product or component and linking a configuration to other configurations or other software.
0024A preferred embodiment of the present invention will be discussed with reference to <figref idref="DRAWINGS">FIGS. 1-6</figref>. <figref idref="DRAWINGS">FIG. 1</figref> shows the system architecture in which a preferred embodiment of the present invention may be used. The system and method of the present invention may be run on a local system <b>110</b> that may, for example, have a server <b>112</b>, a storage <b>114</b>, a local area network <b>116</b>, and one or many terminals or PC's <b>118</b>, each of which may be used to access the computer-implemented configurator of the present invention. The local system <b>112</b> preferably has access to websites of various other manufacturers <b>130</b>, <b>140</b> and customers <b>150</b>, for example, through the internet <b>120</b>. The server <b>112</b> and/or the one or many terminals or PC's <b>118</b> may access the internet and thereby retrieve data. Additionally, the server <b>112</b> and the one or many terminals or PC's may access data, such as in a database, stored in storage <b>114</b> or in a memory.
0025The system and method of the present invention may be implemented in many different ways and may use various levels of security. For example, system configurations may be designed using the present system and method by an individual that may be referred to as “Configuration Administrator,” who may have the right to design and amend a particular configuration and perhaps be given the ability to authorize others, such as customers, to amend a particular configuration.
0026A method of a preferred embodiment of the present invention will be described with reference to <figref idref="DRAWINGS">FIG. 2</figref>. Beginning at step <b>210</b>, the configurator is opened on a terminal or PC <b>118</b>. The user interface of a preferred embodiment is shown in <figref idref="DRAWINGS">FIG. 3</figref>. In the example shown in <figref idref="DRAWINGS">FIG. 3</figref>, the user interface includes locations for the configuration administrator to enter identifying information such as a customer name <b>302</b>, company name <b>304</b>, configuration name <b>306</b>, an engineer or other assignee <b>308</b>, a sales rep <b>310</b>, and an e-mail address <b>312</b>. The fields, of course, are merely exemplary as fewer or more fields may be used and different layouts of the fields may be used. The system further may include the ability to customize the user interface. Similarly, the steps for entering various information described below may be performed in various different sequences and do not necessarily need to be entered in the sequence described with respect to the preferred embodiment.
0027The Configuration Administrator may, for example, begin with a preliminary step of entering a manufacturer and make of a particular card chassis <b>320</b> for which the interface is being configured. The Configuration Administrator similarly may enter a recommended receiver <b>322</b> and ITA <b>324</b> as preliminary steps.
0028At step <b>220</b>, the Configuration Administrator begins by entering an instrument ID <b>330</b>. Once the instrument ID <b>320</b> is entered, the system finds instrument data regarding the instrument corresponding to that ID. The instrument data may include compatibility data, pictures, or any other data that may be relevant. The data may be retrieved automatically from any of a variety of sources, such as a database stored locally on storage <b>114</b>, from a manufacturer's website <b>130</b> or from both. For example, a database located on local storage <b>114</b> may include website information or links associated with particular manufacturers or particular part numbers such that when an instrument number is entered at step <b>220</b>, the system (step <b>222</b>) retrieves a link from the database and then proceeds to the linked website to retrieve specific data. In another embodiment, rather than retrieving a link or web address from the database, the system may automatically search for the manufacturer and/or part number through the internet and, once found, proceed to the manufacturer's website to retrieve the data. If the website is not found, data may be retrieved from a database and perhaps a note would be added to the instrument entry indicating that the data must be verified. To retrieve data from a manufacture's website, one may use, for example, Automated Test Markup Language (“ATML”). See “IEEE P1671/D2 Draft Trial-Use Standard for Automatic Test Markup Language (ATML) for Exchanging Automatic Test Equipment and Test Information via XML,” (2005) and “ATML—The Standard for Interfacing Test System Components Using XML,” National Instruments (2006).
0029At step <b>224</b>, the Configuration Administrator enters a slot number <b>332</b> corresponding to the instrument ID entered at step <b>220</b>. The method may include error-preventing techniques to prevent a user from entering incorrect or incompatible part numbers. At step <b>224</b>, for example, the system may use data retrieved in step <b>222</b> for the particular instrument to ensure that the Configuration Administrator enters the correct number of slots for the particular instrument. The error-prevention techniques could include displaying a warning to a user that incorrect data may have been entered, may simply prohibit entry of incorrect data, or may initially prohibit such entry but permit a Configuration Administrator to override the protection. At any of the data retrieval steps, the local system <b>110</b> may store or update information regarding manufacturers, parts or websites in a database. In this manner, a local database of information may be compiled. Such a local database may be used, for example, in a situation in which a configuration is being made at a time when a manufacturer's website is unavailable. The system and method could further include means to tag entries pulled from a local database such that the system may access a manufacturer's database at a later time to confirm the accuracy of the data retrieved locally.
0030Next, at step <b>230</b> the Configuration Administrator enters a component ID <b>334</b>. The system then retrieves data regarding the component associated with the component ID at step <b>232</b>. As with step <b>222</b>, the system may retrieve the component data in any of a variety of ways. The system then checks at step <b>234</b> whether the component entered at step <b>230</b> is compatible with the instrument entered at step <b>220</b>. If the component is not compatible, the system may, for example, display an error message to the Configuration Administrator and request correction (step <b>236</b>). The system may or may not provide the Configuration Administrator with the ability to override the error message and continue to step <b>240</b>. This may be useful, for example, if the Configuration Administrator is aware the incorrect compatibility data exists for a particular component. If the entered component is compatible with the instrument entered at step <b>220</b>, the system then associates the two locally as part of the interface system configuration.
0031The user then has a choice <b>250</b> of entering more components by returning to step <b>230</b> or proceeding to save the configuration in storage <b>114</b> at step <b>260</b>. The user similarly may enter additional instruments and components for such additional instruments. When the configuration is saved, the system may for example assign a configuration number <b>340</b> to later identify this particular configuration. The configuration number <b>340</b> may be assigned automatically, such as with a random 7-digit number, or may be chosen by the user. Similarly, the date <b>350</b> on which the configuration was designed or modified may be entered automatically or manually.
0032The Configuration Administrator then may preview the configuration or provide access to such a preview to a customer or manufacturer so they may review and possibly amend the configuration (step <b>270</b>). If a preview is selected, at step <b>280</b> the system finds links to manufacturer's websites for as many of the instruments, components and cards as possible and at step <b>282</b> generates and displays a preview of the configuration, such as is shown in <figref idref="DRAWINGS">FIG. 4</figref>. The preview includes the links found by the system, which are displayed at step <b>286</b> at the selection of the user at step <b>284</b>. For example, <figref idref="DRAWINGS">FIG. 5</figref> shows a preview with an instrument data link <b>510</b>. Similarly, <figref idref="DRAWINGS">FIG. 6</figref> shows a preview with a receiver data link <b>610</b> opened. The data may be displayed in a call-out such as is shown in <figref idref="DRAWINGS">FIGS. 5 and 6</figref> or by other means such as by opening a new window for the data or opening the manufacturer's website directly. If links are not found for particular instruments or components data from a database may or may not be displayed in place of data from a manufacturer's website.
0033After reviewing the data, the user may be given the option of amending the configuration (step <b>288</b>), in which case the system would return to step <b>220</b>. If the user does not wish to amend the system, the preview would be closed and ultimately, at step <b>290</b>, the configurator would be closed.
0034The system and method further include the ability of a user to later access the configuration and if they so desire, amend the configuration. At such a time, the system may include automated methods to re-check or confirm the accuracy and compatibility of the data for various instruments and components in the configuration. The Configuration Administrator may receive a customer's request by any number of means. In one embodiment, a request form may be presented to a user via an electronic display. In FIG. <b>7</b>, a request form <b>710</b> is shown superimposed over a configuration designer with the standard screen obscured. The request form <b>710</b> may include keyword hinting to assist the customer in selecting appropriate instrumentation. Default settings, such as a quantity of 1, may be used. A user's information may appear at the bottom of the request form and may be pre-populated based upon, for example, login data entered by a user. Once a user completes a request form, the user submits the request and a confirmation notice such as an electronic mail message or test message may be sent to the user by the system. The system may further include the ability to display a summary of various configurations submitted, for example, by a particular user or customer. Such summary may be presented in table form or may, for example, be produced on an Excel worksheet. Furthermore, information from a particular request may be downloaded into, for example, an Excel spreadsheet for display.
0035Once a request is submitted, the local system may generate and display a quote for purchase of the configuration. The generation of the quotations may include steps in which a summary <b>810</b> or summaries of the various components in the configuration are displayed to the Configuration Administration, such as is shown in <figref idref="DRAWINGS">FIG. 8</figref>. During such a display step, the Configuration Administrator may select and deselect various items and modify quantities.
0036In other embodiments, various pieces of information may be entered automatically by the system. For example, if the system is being run by a particular receiver manufacturer, that manufacturer's receiver product information may be entered automatically by the system once the user enters an instrument identification or part number. Variations in which additional or other information is entered automatically by the system will be apparent to those of skill in the art.
0037The foregoing description of the preferred embodiment of the invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed, and modifications and variations are possible in light of the above teachings or may be acquired from practice of the invention. The embodiment was chosen and described in order to explain the principles of the invention and its practical application to enable one skilled in the art to utilize the invention in various embodiments as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the claims appended hereto, and their equivalents. The entirety of each of the aforementioned documents is incorporated by reference herein.
Contents6
10 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2004034497A1 | Cites | United States of America | Search report |
| US2004205514A1 | Cites | United States of America | Search report |
| US2005114228A1 | Cites | United States of America | Search report |
| US2007033572A1 | Cites | United States of America | Search report |
| US2007288445A1 | Cites | United States of America | Search report |
| US2010058188A1 | Cites | United States of America | Search report |
| US2010064763A1 | Cites | United States of America | Search report |
| US5867382A | Cites | United States of America | Search report |
| US6629008B2 | Cites | United States of America | Search report |
| US6678877B1 | Cites | United States of America | Search report |
| US6877033B1 | Cites | United States of America | Search report |
| US7017138B2 | Cites | United States of America | Search report |
| US7188333B1 | Cites | United States of America | Search report |
| US7240319B2 | Cites | United States of America | Search report |
| US7458055B2 | Cites | United States of America | Search report |
| US7613729B2 | Cites | United States of America | Search report |
| US7738985B2 | Cites | United States of America | Search report |
| US20040034497A1 | Cites | United States of America | Search report |
| US20040205514A1 | Cites | United States of America | Search report |
| US20050114228A1 | Cites | United States of America | Search report |
| US20070033572A1 | Cites | United States of America | Search report |
| US20070288445A1 | Cites | United States of America | Search report |
| US20100058188A1 | Cites | United States of America | Search report |
| US20100064763A1 | Cites | United States of America | Search report |
| “Excel 2003—Tutorial 1” @Jan. 18, 2006. | Non-patent | – | Search report |
| “ATML—The Standard for Interfacing Test System Components Using XML,” National Instruments (2006). | Non-patent | – | Applicant |
| “Draft Trial-Use Standard for Automatic Test Markup Language (ATML) for Exchanging Automatic Test Equipment and Test Information via XML,” IEEE P1671/D2 (Dec. 2005). | Non-patent | – | Applicant |
| “AML (Automatic Test Markup Language),” The Test Savvy Engineer, (Oct. 1, 2007). | Non-patent | – | Applicant |
| "Excel 2003-Tutorial 1" @Jan. 18, 2006. | Non-patent | – | Search report |
| "ATML-The Standard for Interfacing Test System Components Using XML," National Instruments (2006). | Non-patent | – | Applicant |
| "Draft Trial-Use Standard for Automatic Test Markup Language (ATML) for Exchanging Automatic Test Equipment and Test Information via XML," IEEE P1671/D2 (Dec. 2005). | Non-patent | – | Applicant |
| "AML (Automatic Test Markup Language)," The Test Savvy Engineer, (Oct. 1, 2007). | Non-patent | – | Applicant |
2 members in 1 office; this record represents the family
Priority claims1
| Document | Office | Kind | Date |
|---|---|---|---|
| 23097309 | United States of America | P |
Members2
| Document | Office | Kind | |
|---|---|---|---|
| US2011055787A1 | United States of America | A1 | |
| US8707243B2This record | United States of America | B2 |
61 transactions on the USPTO file
Allowed after 1 non-final rejection, 1 final rejection and 1 RCE.
- Non-final rejections
- 1
- Final rejections
- 1
- RCEs
- 1
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Expire PatentEXP. | EXP. | |
| Maintenance Fee Reminder MailedREM. | REM. | |
| Payment of Maintenance Fee, 8th Yr, Small EntityM2552 | M2552 | |
| Surcharge for late Payment, Small EntityM2554 | M2554 | |
| Payment of Maintenance Fee, 4th Yr, Small EntityM2551 | M2551 | |
| Maintenance Fee Reminder MailedREM. | REM. | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Examiner's Amendment CommunicationEX.A | EX.A | |
| Interview Summary - Examiner Initiated - TelephonicEXET | EXET | |
| Interview Summary - Examiner InitiatedEXIE | EXIE | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Mail Post CardPST_CRD | PST_CRD | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Email NotificationEML_NTR | EML_NTR | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Application Is Now CompleteCOMP | COMP | |
| Email NotificationEML_NTR | EML_NTR | |
| Filing Receipt - UpdatedFLRCPT.U | FLRCPT.U | |
| Sent to Classification ContractorPGPC | PGPC | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Applicant has submitted new drawings to correct Corrected Papers problemsCORRDRW | CORRDRW | |
| Additional Application Filing FeesADDFLFEE | ADDFLFEE | |
| A statement by one or more inventors satisfying the requirement under 35 USC 115, Oath of the ApplicOATHDECL | OATHDECL | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTR | EML_NTR | |
| Email NotificationEML_NTF | EML_NTF | |
| Notice Mailed--Application Incomplete--Filing Date AssignedINCD | INCD | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
10 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Lapsed due to failure to pay maintenance feeLapsedFP | FP | |
| Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITYLAPS | LAPS | |
| Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH | STCH | |
| Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITYFEPP | FEPP | |
| Maintenance fee paymentMAFP | MAFP | |
| Fee payment procedureSURCHARGE FOR LATE PAYMENT, SMALL ENTITY (ORIGINAL EVENT CODE: M2554)FEPP | FEPP | |
| Maintenance fee paymentMAFP | MAFP | |
| Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.)FEPP | FEPP | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication
- 8707243
- Application
- 12849781
Titles
- English
- Interface configuration system and method
Patent term adjustment
- A delay
- +291 daysthe office missed an examination deadline
- B delay
- +106 dayspendency past three years
- Applicant delay
- −187 days
- Net adjustment
- 210 days
Classification
- CPC, 6
- G06F30/00
- G06Q30/0621
- G06Q10/10
- G06Q30/06
- G06F2111/02
- G06Q10/087
- IPC, 2
- G06F11 22
- G06F17 50