Technical Field
The present disclosure generally relates to the field of computerized systems. More particularly, the disclosure relates to computerized systems and methods for analyzing patent-related documents.
Background Information
Various databases and tools exist for patent-related documents, such as ones provided by the U.S. Patent and Trademark Office and some foreign patent agencies. Other search tools exist as well, such as, MicroPatent™, PatBase™, and Delphian™. These search tools typically permit users to search for patent-related documents using search terms and other criteria.
Traditional search tools are often limited in their ability to search, filter, and analyze large numbers of patent-related documents. Traditional search tools may locate large numbers of patent-related documents responsive to a query, but do not provide a convenient user interface for filtering and analyzing the patent-related documents to find relevant patent-related documents that are interesting to a user. Accordingly, there exists a need for improved search and analysis tools for patent-related documents.
Consistent with a disclosed embodiment, a method analyzes patent-related documents having at least one property type. The method includes displaying, in a first graphical element, identifiers of the patent-related documents. The method analyzes, by at least one processor, the patent-related documents to determine at least one property value for the property type. The property value comprises a string of one or more words describing subject matter associated with the patent-related documents and occurring in a subset of the patent-related documents. The method further includes displaying a second graphical element associated with the property type, the second graphical element including the property value. The method also receives, at the second graphical element, a user selection of the property value. The method further displays, in the first graphical element, identifiers of the subset of the patent-related documents in which the property value occurs.
Consistent with a disclosed embodiment, a computer-readable medium is provided. The computer-readable medium comprises program instructions which, when executed by at least one processor, cause the processor to perform a method that analyzes patent-related documents having at least one property type. The method includes displaying in a first graphical element, identifiers of the patent-related documents. The method analyzes the patent-related documents to determine at least one property value for the property type. The property value includes a string of one or more words describing subject matter associated with the patent-related documents and occurring in a subset of the patent-related documents. The method displays a second graphical element associated with the property type, the second graphical element including the property value. The method further includes receiving, at the second graphical element, a user selection of the property value. The method further displays, in the first graphical element, identifiers of the subset of the patent-related documents in which the property value occurs.
Consistent with a disclosed embodiment, a method analyzes of patent-related documents having at least one property type. The method includes retrieving, from a storage, the patent-related documents. The method analyzes, by at least one processor, the patent-related documents to determine at least one property value for the property type. The property value includes a string of one or more words describing subject matter associated with the patent-related documents and occurring in a first subset of the patent-related documents. The method analyzes a corpus of patent-related documents to determine at least one variant of the property type. The variant is used in the corpus of patent-related documents to refer to the subject matter described by the property value. The variant comprises another string of one or more words occurring in a second subset of the patent-related documents. The method further displays, in a first graphical element, identifiers of the patent-related documents element. The method displays a second graphical element associated with the property type, the second graphical element including the property value. The method receives, at the second graphical element, a user selection of the property value. In response to the user selection, the method displays a third graphical element with the variant. The method further includes receiving a user selection of the variant. The method further displays, in the first graphical element, identifiers of the first subset in which the property value occurs and identifiers of the second subset in which the variant occurs.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the embodiments, as claimed.
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate disclosed embodiments and together with the description, serve to explain the principles of the disclosed embodiments.
The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the following description to refer to the same or similar parts. While several exemplary embodiments are described herein, modifications, adaptations and other implementations are possible, without departing from the spirit and scope of the disclosed embodiments. For example, substitutions, additions or modifications may be made to the components illustrated in the drawings, and the exemplary methods described herein may be modified by substituting, reordering, or adding steps to the disclosed methods. Accordingly, the following detailed description is not limiting. Instead, the proper scope is defined by the appended claims.
Embodiments disclosed herein provide computer-implemented systems and methods for filtering and/or analyzing documents. Although the following discussion may refer to various legal documents, such as patents and published patent applications, one of ordinary skill in the art will understand that systems and methods consistent with the disclosed embodiments may analyze any kind of document.
In the context of patents or published patent applications, as used herein, a “claim element” shall mean a component of an invention that is found in a claims section of a patent application and a “part” shall mean a component of an invention found in a description section of a patent application. The “part” may be a component of a drawing reference, which may include both the part and an identifier, such as a reference number. A “term” shall constitute a word used in a document in a specific way to mean a certain thing. As used herein, a “phrase” may include a string of one or more elements, parts, or terms. In the context of documents, in general, the terms “element,” “part,” and “phrase” may refer to any word or words in a document.
With reference to
CPU 104 may execute computer program instructions to perform various processes and methods. CPU 104 may read the computer program instructions from memory 106 or from any computer-readable storage medium included in device 102, external to device 102, or accessible to device 102 over network 112. Memory 106 may include random access memory (RAM) and/or read only memory (ROM) configured to access and store information and computer program instructions. Memory 106 may also include additional memory to store data and computer program instructions, and/or one or more internal databases (not shown) to store tables, lists, or other data structures. Moreover, user interface 108 may access user data, such as a user input for filtering patent-related documents. In some embodiments, user interface 108 may be separate from device 102. User interface 108 may also include a visual display, keyboard, mouse, or touch screen, for example. Furthermore, I/O unit 110 may access data over network 112.
Network 112 may facilitate communications between the various devices in system 100, such as device 102 and database 114. In addition, device 102 may access legacy systems (not shown) via network 112, or may directly access legacy systems, databases, or other network applications. Network 112 may be a shared, public, or private network, may encompass a wide area or local area, and may be implemented through any suitable combination of wired and/or wireless communication networks. Furthermore, network 112 may comprise a local area network (LAN), a wide area network (WAN), an intranet, or the Internet. In some embodiments, network 112 may be substituted with a direct wired or wireless connection between device 102 and database 114.
Database 114 may include documents 116. Documents 116 may be associated with any subject matter, such as legal, scientific, financial, and/or political. In disclosed embodiments, documents 116 may be patent-related documents, such as U.S. patents and/or Published U.S. applications. Documents 116 may also include patents and published applications from other jurisdictions, such as Japan, Europe, China, etc., or under the Patent Cooperation Treaty, for example.
Moreover, although shown as separate components in
Memory 106 may include a Result Component 202, a Data Extraction Component 204, a Bibliographic Data Filtering Component 206, a Subject Matter Data Filtering Component 208, a Variation Determining Component 210, and a Summarizing Component 212.
Result Component 202 may identify a body of patent-related documents. For example, Results Component 202 may enable a user to input general search terms and retrieve patent-related documents meeting the search terms, from, for example database 114, as shown in
Data Extraction Component 204 may extract different types of data occurring in the body of patent-related documents, such as bibliographic data and subject matter data. Bibliographic data may relate to information describing the background or history of a patent-related document. For example, bibliographic data for a patent or published patent application may include: assignee, inventor, legal representative, examiner, U.S. class, international patent classification (IPC), date, and/or citations. Subject matter data, by contrast, may relate to information describing technical aspects or concepts being described or explained in a patent-related document. For example, subject matter data for a patent or published patent application may include: part, term, phrase, or claim element, as defined above.
Bibliographic Data Filtering Component 206 may display property types of the extracted bibliographic data. For example, Bibliographic Data Filtering Component 206 may display different graphical elements for each of the following bibliographic data of: assignee, inventor, legal representative, examiner, U.S. class, international patent classification (IPC), date, and/or citations. Moreover, Bibliographic Data Filtering Component 206 may filter the body of patent-related documents according to a selection of one or more property values associated with the extracted bibliographic data. For example, a user may select a listed law firm as a property value from a graphical element of bibliographic property type “legal representative.” Bibliographic Data Filtering Component 206 may then filter the body of patent-related documents and display only those having the selected law firm as its “legal representative.” Moreover, in addition to filtering based on bibliographic data, exemplary embodiments may additionally or alternatively filter based on subject matter data.
Subject Matter Data Filtering Component 208 may display property types of the extracted subject matter data. Subject Matter Data Filtering Component 208 may display different graphical elements for each of the following subject matter data of: part, term, phrase, and/or claim element. In each of the different graphical elements, Data Extraction Component 204 may display property values extracted from the body of patent-related documents that correspond to the property type. For example, in a graphical element of a bibliographic property type “legal representative,” Data Extraction Component 204 may list all the different law firms occurring as legal representatives within the body of patent-related documents. A user may be able to select one or more of the property values to filter the body of patent-related documents. Subject Matter Data Filtering Component 208 may filter the body of patent-related documents according to a selection of one or more property values associated with the extracted subject matter data. For example, a user may select a part as a subject matter property value from a graphical element of property type “parts.” Subject Matter Data Filtering Component 206 may then filter the body of patent-related documents and display only those having the selected part.
Variation Determining Component 210 may determine one or more variants for a subject matter property value. For a subject matter property value (e.g., a particular part, term, phrase, or claim element) used in the body of patent-related documents, a variant may be a different corresponding part, term, phrase, or claim element that is used to represent the same technical aspect or concept. Variation Determining Component 210 may determine the variants by analyzing a corpus of patent-related documents to determine if the variant is used interchangeably with the subject matter property value. The corpus of patent-related documents may be the same, smaller, larger, overlapping, or completely different from the body of patent-related documents determined by Results Component 202. After determining the variants, Variation Determining Component 210 may display the variants in one or more graphical elements for user selection. Variation Determining Component 210 may filter the body of patent-related documents according to the selection of the one or more displayed variants.
Accordingly, in disclosed embodiments, a user may have filtered the body of patent-related documents by selected multiple bibliographic property values, subject matter property values, and/or variants. In some embodiments, these filter values may be combined by logical AND (intersection). In other embodiments, these filter values may be combined by logical OR (union). In other embodiments some of the filter values may be combined by logical AND while others may be combined by logical OR. Any of these logical combinations may be set by a user in an options menu or may be preprogrammed. In some embodiments, in a default setting, filter values within a graphical element may be combined by a logical OR, while filter values among different graphical elements may be combined with a logical AND.
A Summarizing Component 212 may aggregate and display the previously selected bibliographic and subject matter property values. At this stage, Summarizing Component 212 may permit de-selection of any previously selected property value. Moreover, Summarizing Component 212 may display a claim listing and/or full text of the filtered patent-related documents and highlight selected property values and variants within the displayed claim listing or full text.
For example, a user may have previously filtered the body of patent-related documents according to a particular law firm, a particular part, and a variant of the part. Summarizing Component 212 may display a filtered subset of the body patent-related documents that contain those selected property values. For each patent-related document in the subset, Summarizing Component 212 may enable a user to view the full text patent-related document. Within the full text, Summarizing Component 212 may highlight the particular law firm used as the filter value in a first color. Summarizing Component 212 may further highlight the particular part in a second color, which may be different from the first color. Moreover, in some embodiments, Summarizing Component 212 may highlight the variant of the particular part in a common (i.e., the same) second color as the part, in order to indicate that the part and the variant are used interchangeably and represent the same technical aspect or concept. One of ordinary skill will appreciate that any other visual representation or identifier may be used instead of color, such as highlighting, shading, hatching, etc.
At block 306, Bibliographic Data Filtering Component 206 may filter the body of patent-related documents according to selected bibliographic data. In particular, a user may have selected one or more displayed bibliographic property values and Bibliographic Data Filtering Component 206 may filter the body of patent-related documents into a subset that includes the selected one or more bibliographic property values.
At block 308, Subject Matter Data Filtering Component 208 may filter the body of patent-related documents according to selected subject matter data. In particular, a user may have selected one or more displayed subject matter property values, and Subject Matter Data Filtering Component 208 may filter the body of patent-related documents into a subset that includes the selected one or more subject matter property values.
At block 310, Variation Determining Component 210 may determine variants for the subject matter data, for example, the subject matter property values selected in block 308. As discussed, for a subject matter property value (e.g., a particular part, term, phrase, or claim element) used in the body of patent-related documents, a variant may be a different corresponding part, term, phrase, or claim element that is used to represent the same technical aspect or concept. Variation Determining Component 210 may filter the body of patent-related documents into a second subset that includes selected variants.
At block 312, Summarizing Component 212 may display a summary of the filter values selected in blocks 306-310 and may enable a user to view a claim listing and/or full text of the filtered patent-related documents. When the full text of a document is displayed, Summarizing Component 212 may highlight selected property values with a visual representation.
Graphical interface 400 may include a search term area 402, a search result area 404, and a search summary area 406. Search term area 402 may enable a user to enter general search terms for identifying a body of patent-related documents. Search result area 404 may list the body of patent-related documents. Search summary area 406 may summarize information about the body of patent-related documents.
In particular, search term area 402 may include the following search terms: Maximum Patents 408, Class 410, IPC 412, Assignee 414, Legal Representative 416, Inventor 418, References Cited 420, and Date 422. Maximum Patents 408 may specify the maximum number of patents to be returned in the search. Class 410 may refer to a particular class in the U.S. patent classification system. In graphical interface 400, the value of Class 410 is 249, which refers to “Static Molds” in the U.S. patent classification system. In some embodiments, Class 410 may refer to a particular class in a foreign or other classification system. Moreover, IPC 412 may refer a class in the International Patent Classification system.
Assignee 414 may relate to assignee information listed on one or more patent-related documents. In disclosed embodiments, the assignee information may be recorded by the U.S. Patent and Trademark Office or other foreign patent office, and may be available via an online resource or other resource. Alternatively, the assignee information may be stored in any other location or may be made available by any other means.
Legal representative 416 may relate to an attorney or law firm, which prosecuted one or more patent-related documents. Inventor 418 may relate to an inventor of one or more patent-related documents. References Cited 420 may relate to references cited by one or more patent-related documents. Date 422 may relate to a date or date range of one or more patent-related documents.
Moreover, search result area 404 may list the body of patent-related documents identified by the search terms in search term area 402. Search result area 404 may identify the body of patent-related documents by number (e.g., U.S. patent number) and/or title.
In some embodiments, the body of patent-related documents may be loaded from a client-side storage location, or any other database. Moreover, in some embodiments, a user may enter a list of patents to be included in the body of patent-related documents. Furthermore, in some embodiments, one or more patent-related lists may be received from a search tool and processed to determine the body of patent related documents.
Search summary area 406 may summarize information about the body of patent-related documents. Search summary area may include item field 424, average field 426, and total field 428. Item field 424 may provide a feature about the patent-related documents. For example, item field 424 includes “Patents,” “Claims,” “Independent Claims,” “Claim Elements,” and “References.” Average field 426 provides average values corresponding to the features in item field 424. For example, average field 426 indicates that there are an average of 13 claims in each patent-related document in the body, with an average of 2 independent claims. Average field 426 further indicates that there is an average of 46 claim elements in each of the patent-related documents in the body and 75 cited references.
For one or more of the items in item field 424, total field 428 may provide the total number of items. For example, for “References” in item field 424, total field 428 indicates that there are 7591 references cited in the body of patent related documents. In some embodiments, total field 428 may count references (or other items) multiple times. In some embodiments, search summary area 406 may include another field (not shown) including the unique number of items associated with an item in item field 426. The unique number of items may not include duplicates.
Graphical interface 500 includes graphical elements 502-508, each of which is associated with a bibliographic property type. Moreover, each of the graphical elements may list property values corresponding to the property type of the graphical element.
For example, the property type of graphical element 502 is “Assignee” and the property values may be different assignees extracted from the body of patent-related documents. Similarly, the property type of graphical element 504 is “Inventor” and the property values may be different inventor names extracted from the body of patent-related documents. Also, the property type of graphical element 506 is “Legal Representative” and the property values may be different attorney or law firm names that were extracted from the body of patent-related documents. Finally, the property type of graphical element 508 is “Examiner” and the property values may be different patent examiner names that were extracted from the body of patent-related documents.
In disclosed embodiments, property values for a particular property type may be ranked and ordered in their associated graphical element. For example, in graphical element 502, each of the listed assignees (i.e., property values) include a count value (“Cnt”). The count value may indicate the number of patent-related documents in which the particular assignee (i.e., property value) occurs throughout the body of patent-related documents. For graphical element 502, the assignee “Husky” occurs in 4 different patent-related documents in the body, while the assignee “Gillespie” occurs in 2 different patent-related documents in the body. Accordingly, “Husky” may be ranked higher than “Gillespie” and in the order of property values listed in graphical element 502, the assignee “Husky” may be displayed higher or before “Gillespie.” Bibliographic Data Filtering Component 206 may perform and display similar ranking and ordering for graphical elements 504-508 as well.
Moreover, each of graphical elements 502-508 may permit a user to select one or more of the listed property values to filter the body of patent-related documents. The filtered patent-related documents may be identified and listed in citations list 510. The filtered patent-related documents may be a subset of the body of patent-related documents, depending on the property values selected by the user in graphical elements 502-508. Citation list 510 may display identifiers and metadata of the filtered patent-related documents. For example, citation list 510 may display a publication number, title, IPC, assignee, and date for each of the filtered patent-related documents. In some embodiments, citation list may display the total number of claims, number of independent claims, and/or number of dependent claims for each of the filtered patent-related documents.
Moreover, in response to receiving a user selection of a property value at graphical elements 502-508, Bibliographic Data Filtering Component 206 may render unselectable those property values that do not coexist in the body of patent-related documents with the selected property value. For example, if a user selects the property value “Husky” from graphical element 502, Bibliographic Data Filtering Component 206 may render unselectable the remaining property values in graphical element 502. This may be because other assignees do not occur together with “Husky” in the same patent-related document from the body of patent-related documents. Indeed, patent-related documents typically have a single assignee. If there existed a patent-related document from the body of patent-related documents, which did include another assignee besides “Husky,” then Bibliographic Data Filtering Component 206 would not render unselectable this another assignee.
In other embodiments, Bibliographic Data Filtering Component 206 may not render unselectable the remaining property values in graphical element 502, after selection of “Husky.” This may broaden the results of the filtering. Indeed, by permitting further selections of property values from graphical element 502, Bibliographic Data Filtering Component 206 may include additional patent-related documents from the body of patent-related documents. For example, a user may select both “Husky” and “Gillespie” from graphical element 502, which may return patent-related documents having an assignee of either “Husky” or “Gillespie.” This is because selected property values within a graphical element may be combined with a logical OR operation.
Bibliographic Data Filtering Component 206 may render unselectable certain property values in different graphical elements, if those property values do not occur in the body of patent-related documents together with a selected property value. This is because selected property values among different graphical elements may be combined with a logical AND operation. For example, if “Husky” is selected in graphical element 502, Bibliographic Data Filtering Component 206 may render unselectable certain inventor property values in graphical element 504, if certain inventor names do not coexist with the assignee “Husky” in the same patent-related document, from the body of patent-related documents. Similarly, Bibliographic Data Filtering Component 206 may also render unselectable certain property values in graphical elements 506 and 508.
Bibliographic Data Filtering Component 206 may render unselectable property values by removing them, graying them out, highlighting them, highlighting the remaining selectable property values, or by any other indication. Moreover, Bibliographic Data Filtering Component 206 may reorder the property values that remain selectable in graphical elements 502-508.
Patent-related documents may be selected from citation list 510. In some embodiments, a selection of a patent-related document from citation list 510 may cause reordering and/or highlighting of property values in graphical elements 502-508. For example, if U.S. Pat. No. 7,682,143 is selected in citation list 510, then the assignee associated with this selected patent may be highlighted in graphical element 502 and/or placed at the top of graphical element 502. This selection and/or reordering may also occur for property values in one or more of graphical elements 504-508.
For example, the property type of graphical element 602 is “U.S. Class” and the property values may be different U.S. Classes extracted from the body of patent-related documents. Similarly, the property type of graphical element 604 is “IPC” and the property values may be different international patent classifications extracted from the body of patent-related documents. Also, the property type of graphical element 606 is “Date” and the property values may be different dates (e.g., filing dates or publication dates) extracted from the body of patent-related documents. Some embodiments may include separate tabs (not shown) for the filing date and grant date of a patent-related document. Finally, the property type of graphical element 608 is “Citations” and the property values may be different document citations extracted from the body of patent-related documents.
In disclosed embodiments, property values for a particular property type may be ranked and ordered in their associated graphical element, in a manner similar to that discussed above with respect to graphical interface 500. Moreover, each of graphical elements 602-608 may permit a user to select one or more of the listed property values to filter the body of patent-related documents. The filtered patent-related documents may be identified and listed in citations list 610, in a manner similar to that discussed above with respect to graphical interface 500.
Moreover, in response to receiving a user selection of a property value at graphical elements 602-608, Bibliographic Data Filtering Component 206 may render unselectable those property values that do not coexist in the body of patent-related documents with the selected property value, in a manner similar to that discussed above with respect to graphical interface 500.
For example, the property type of graphical element 702 is “Part” and the property values may be different parts (as defined previously) extracted from the body of patent-related documents. Similarly, the property type of graphical element 704 is “Term” and the property values may be different terms (as defined previously) extracted from the body of patent-related documents. Also, the property type of graphical element 706 is “Phrase” and the property values may be different phrases (as defined above) extracted from the body of patent-related documents.
In disclosed embodiments, property values for a particular property type may be ranked and ordered in their associated graphical element, in a manner similar to that discussed above with respect to graphical interface 500. Moreover, each of graphical elements 702-706 may permit a user to select one or more of the listed property values to filter the body of patent-related documents. The filtered patent-related documents may be identified and listed in citations list 708, in a manner similar to that discussed above with respect to graphical interface 500.
Moreover, in response to receiving a user selection of a property value at graphical elements 702-706, Subject Matter Data Filtering Component 208 may render unselectable those property values that do not coexist in the body of patent-related documents with the selected property value, in a manner similar to that discussed above with respect to graphical interface 500.
Fourth graphical interface 700 may also include graphical element 710, which may include definitions. In some embodiments, graphical element 710 may be included as a separate tab. In the body of patent-related documents, certain terms or phrases may be explicitly defined. Disclosed embodiments may employ regular expression algorithms and/or pattern matching to identify definitions occurring in the body of patent-related documents. Accordingly, graphical element 710 may include terms, definitions of the terms, and locations of the definitions.
This feature may be useful for determining, for example, a standard grammar used by a legal representative, assignee, or applicant. For example, a user may specify the body of patent-related document for a particular assignee, and then view the definitions in the body of patent-related documents, which are used by the particular assignee. In this way, definitions typically used by the assignee may be identified.
In some embodiments, similar (but different) definitions may be nevertheless grouped together and counted. For example, multiple similar definitions may be determined for a term, but only one of the similar definitions may be shown in graphical element 710 as associated with the term. In some embodiments, graphical element 710 may include a count, indicating a number of times the term is defined in the body of patent-related documents. The count may include the similar definitions, even though there may be differences among the similar definitions.
In disclosed embodiments, property values for a particular property type may be ranked and ordered in their associated graphical element, in a manner similar to that discussed above with respect to graphical interface 500. Moreover, graphical element 802 may permit a user to select one or more of the property values to filter the body of patent-related documents. The filtered patent-related documents may be identified and displayed in citations list 804, in a manner similar to that discussed above with respect to graphical interface 500.
Moreover, in response to receiving a user selection of a property value at graphical element 802, Subject Matter Data Filtering Component 208 may render unselectable those property values that do not coexist in the body of patent-related documents with the selected property value, in a manner similar to that discussed above with respect to graphical interface 500.
At block 902, CPU 104 may display identifiers of the body of patent-related documents. As discussed, the body of patent-related documents may be identified by Result Component 202 after searching for patent-related documents based on search terms entered in screen shot 400 (
At block 904, CPU 104 may analyze the body of patent-related documents to determine property values for property types, by executed Data Extraction Component 204. At block 906, CPU 104 may cause the display of the property values. For example, graphical elements 502-508 (
At block 908, CPU 104 may receive a selection of one or more the displayed property values. At block 910, CPU 104 may determine a subset of the body of patent-related documents, in which the selected property value occurs. For example, CPU 104 may filter the body of patent-related documents so that only the subset remain. At block 912, CPU 104 may cause a display of the subset of patent-related documents. For example, CPU 104 may replace the previously displayed body of the patent-related documents with the subset of the patent-related documents. This may involve removing the patent-related documents from the body that are not in the subset. In exemplary embodiments, the subset of patent-related documents may be displayed in citations list 510 (
Graphical interface 1000 may also include graphical element 1004, which may list variants for a claim element listed in graphical element 1002. Generally, for a subject matter property type (e.g., part, term, phrase, or claim element) used in the body of patent-related documents, a variant may be a different corresponding part, term, phrase, or claim element that is used to represent the same technical aspect or concept.
For example, in graphical element 1002, it is seen that the claim element property value “mold” is selected, as shown by the check box. When this selection occurs, Variation Determining Component 210 may update graphical element 1004 to show variants of “mold.” Variants of “mold” displayed in graphical element 1004 include “surface,” “mold cavity,” “mold cavities,” etc. In this example, these variants are claim elements that may be used synonymously in place of “mold.” A user may select any of the variants in graphical element 1004 to filter the body of patent-related documents.
Claim elements selected from graphical element 1002 may be logically ORed with their associated variants selected in graphical element 1004. In this way, the filtered patent-related documents displayed in citation list 1006 includes both patent-related documents that include the selected claim element(s), and patent-related documents that include the selected variant(s). In this way, patent-related documents that describe the same conceptual ideas, but use slightly different language are not missed in the filtering.
Graphical interface 1000 also includes graphical element 1008 for defining a corpus of patent-related documents in which to search for variants. Specifically, when determining variants for a claim element, Variation Determining Component 210 may analyze a corpus of patent-related documents to see which terms are commonly used interchangeably with the claim element. These terms may then be identified and displayed to the user as variants, Graphical element 1008 may enable a user to select the corpus to be analyzed in order to determine the variants.
In graphical interface 1000, graphical element 1008 allows the user to select between “Current Variants,” “Class Variants,” and “All Variants.” By selecting “Current Variants,” the user may direct Variation Determining Component 210 to analyze the body of patent-related documents initially determined by Results Component 202. In alternate embodiments, the selection of “Current Variants” may direct Variation Determining Component 210 to analyze the patent-related documents filtered thus far by Bibliographic Data Filtering Component 206 and/or Subject Matter Data Filtering Component 208.
Alternatively, by selecting “Class Variant”, the user may direct Variation Determining Component 210 to analyze patent-related documents belonging to one or more classes. In some embodiments, the class may include a class from the U.S. Classification System. In other embodiments, the class may be any other type of categorization of classification system, such as an international or other jurisdiction classification. In some embodiments, this may include all U.S. patents and/or published U.S. patent applications.
By selecting “All Variants,” the user may direct Variation Determining Component 210 to analyze patent-related documents that are available. This may be a significantly larger corpus of patent-related documents that the ones selected by “Current Variants” or “Class Variant.”
Moreover, by checking the box “Limit Elements to Current,” the user may direct Variation Determining Component 210 to calculate variants from the filtered patent-related document in citation list 1006, provided that the patent-related document is listed in citation list 1006.
Graphical interface 1000 also includes graphical element 1010 for defining a group of claims in which claim elements can occur. If the selected claim elements all occur in the defined group of claims for a patent-related document, then the patent-related document may be included in citation list 1006. In particular, after determining selected claim elements, Variation Determining Component 210 may identify and display patent-related documents that include the selected claim elements (or their associated variants) in a certain document section. The document sections are listed in graphical element 1010 as “All Claims,” “Claim Threads,” and “Independent Claims.”
By selecting “All Claims,” the user may direct Variation Determining Component 210 to display a patent-related document in citation list 1006, provided that the patent relate document includes the selected claim elements (or their selected variants) in the claims. In other words, for display, the selected claim elements (or their selected variants) should occur in any claim of the patent-related document.
Alternatively, by selecting “Claim Threads,” the user may direct Variation Determining Component 210 to display a patent-related document in citation list 1006, provided that the patent-related document includes the selected claim elements (or their selected variants) in any single claim thread. In other words, for display, the selected claim elements (or their selected variants) should all occur within a claim thread of the patent-related document. In disclosed embodiments, a claim thread is a set of claims including a single independent claim and all of its dependent claims.
By selecting “Independent Claims,” the user may direct Variation Determining Component 210 to display a patent-related document in citation list 1006, provided that the patent-related document includes the selected claim elements (or their selected variants) in any independent claim. In other words, for display, the selected claim elements (or their selected variants) should all occur in an independent claim of the patent-related documents.
In disclosed embodiments, property values for a particular property type may be ranked and ordered in their associated graphical element, in a manner similar to that discussed above with respect to graphical interface 500. Moreover, graphical elements 1002 and 1004 may permit a user to select one or more of the listed property values to filter the body of patent-related documents. The filtered patent-related documents may be identified and listed in citations list 1006, in a manner similar to that discussed above with respect to graphical interface 500.
Moreover, in response to receiving a user selection of a property value at graphical element 1002, Subject Matter Data Filtering Component 208 may render unselectable those property values that do not coexist in the body of patent-related documents with the selected property value, in a manner similar to that discussed above with respect to graphical interface 500.
In some embodiments, Subject Matter Data Filtering Component 208 may determine antecedent basis for selected claim elements. In particular, Subject Matter Data Filtering Component 208 may determine a part or phrase in the description (and a location of the part or phrase), which provides antecedent basis for a selected claim element. In some embodiments, Subject Matter Data Filtering Component 208 may use “fuzzy matching” to determine a part or phrase similar to the selected claim element, which may not match exactly with the selected claim element. The fuzzy matching may identify locations of variants of the selected claim elements in the description. In some embodiments, Subject Matter Data Filtering Component 208 may also similarly identify antecedent basis for means plus function limitations.
When identifying antecedent basis, Subject Matter Data Filtering Component 208 may also identify drawing references. For example, if a particular part is associated with a selected claim element (or its variant), then the drawing reference associated by the part may be identified in an appropriate figure as providing antecedent basis for the selected claim term.
At block 1102, Variation Determining Component 210 may identify a claim element. For example, as shown in
At block 1106, Variation Determining Component 210 may analyze the corpus of patent-related documents to determine variants of “mold.” To do this, Variation Determining Component 210 may analyze the corpus of patent-related documents to determine word(s) that coexist with “mold,” and which are used synonymously with “mold” in the corpus.
This analysis may be done in different ways. In exemplary embodiments, Variation Determining Component 210 may identify a part occurring in a patent-related document. As discussed, a part may be a component of a drawing reference, which include both the part and an identifier, such as a reference number. For example, a patent-related document may have a drawing reference “hollow tube 10.” The same patent-related document may also have drawing references “cylindrical body 10” and “empty tube 10.” Because the same identifier (i.e., “10”) is being used to refer to a number of different parts (i.e., “hollow tube,” “cylindrical body,” and “empty tube”), Variation Determining Component 210 determines that these different parts may be used interchangeably. In other words, the different parts may be variants of each other.
Variation Determining Component 210 may also determine variants across different patent-related documents. For example, as discussed, Variation Determining Component 210 may identify “hollow tube,” “cylindrical body,” and “empty tube” as a first set of variants of each other because they all have the identifier “10” in the first patent-related document. Variation Determining Component 210 may also identify the following drawing references in a second patent-related document: “hollow body 24,” U Shaped body 24, “hollow tube 24,” and “empty tube 24.” Variation Determining Component 210 may determine that the parts of these drawing references are a second set of variants of one another, because the drawing references all have the same identifier (i.e., 24).
Variation Determining Component 210 may also link the first set of variants with the second set of variants. For example, the first set of variants includes the drawing reference “hollow tube 10,” while the second set of variants includes the drawing reference “hollow tube 24.” These drawing references have the same part (i.e., “hollow tube”) but different identifiers “(i.e., “10” and “24.”) Different patent-related documents may use different identifiers when referring to the same part. Accordingly, Variation Determining Component 210 classifies “hollow tube 10,” and “hollow tube 24” as referring to the same part. Variation Determining Component 210 may then further determine that the first set of variants are also variants with the second set of variants. In other words, the parts “hollow tube,” “cylindrical body,” “empty tube,” “hollow body,” U Shaped body,” and “empty tube” are all variants of each other. Table 1 below summarizes this example:
hollow tube 10
hollow tube 24
Table 1 illustrates the drawing references and parts from the first patent-related document and the second patent-related document. Table 1 also indicates that “hollow tube 10” and “hollow tube 24” (both shown in bold) link together the variants of the first patent-related document with the variants from the second patent-related document.
In this way, variants for parts in drawing elements may be determined. The extracted parts and their variants may be stored in a parts database, which may be stored, for example, in memory 106 in
At block 1108, Variation Determining Component 210 may cause the display of these determined variants. For example, as shown in
At block 1112, Variation Determining Component 210 may receive a user selection identifying a document section. For example, in graphical element 1010 in
The variants listed in graphical element 1202 have associated numbers in parentheses. These numbers may indicate the number of patent-related documents in which the variant and the selected term/phrase coexist. For example, the term/phrase “mold” and the variant “surface” may coexist (e.g., as determined in Table 1) in 20 patent related documents. In some embodiments, these numbers of coexisting patent-related documents may define a variant rank. In other embodiments, rank may be determined in a different way.
Using a rank, variants may be displayed in rank order for a particular term/phrase. For example, in graphical element 1202, the variants for “mold” are displayed in the order in which they are ranked by the numbers in parentheses. In disclosed embodiments, ranking may also be employed for claim element variants or any other type of variants.
Graphical interface 1200 also includes graphical element 1204, which lists the variants for user selection. For example, for the selected subject matter property value in graphical element 1202 (i.e., “mold”), graphical element 1204 lists its variants (e.g., “surface,” “mold cavity,” and “mold cavities”) in selectable form. If a user selects subject matter property values from graphical element 1202 and variants from graphical element 1204, then Variant Determining Component 210 may display patent-related documents from the body in citation list 1206, which include either the selected subject matter property values or variants.
For example, graphical interface 1300 includes property value summary 1302, which lists the property values selected by a user in previous graphical interfaces, such as graphical interfaces 500, 600, 700, 800, 1000, and 1200. In particular, property value summary 1302 may include the following selected property types: Inventor (from graphical element 504 in
In disclosed embodiments, property value summary 1302 may permit a user to de-select any of the listed property values. In some embodiments, this de-selection may cause the patent-related documents listed in citation list 1304 to change accordingly. In other embodiments, the de-selection may not cause the patent-related documents listed in citation list 1304 to change. Moreover, Summarizing Component 212 may permit a user to select patent-related documents listed in citation list 1304.
Graphical interface 1300 may also include claims tab 1306 and full text tab 1308. Claims tab 1306 may permit a user to see claims of the patent-related documents selected in citation list 1304. And full text tab 1308 may permit a user to see full text for the patent-related documents selected in citation list 1304. Claims tab 1306 and full text tab 1308 may also be selectable in other graphical interfaces, such as graphical interfaces 600, 700, 800, 1000, and 1200.
Graphical interface 1400 includes citation list 1402 and claims listing 1404. Citation list 1402 may list filtered patent-related documents, and claims listing 1404 may list the claims of the patent-related documents. In some embodiments, claims listing 1404 may only include independent claims, for example, according to an options setting.
Claim elements previously selected by a user may be highlighted in claims listing 1404. In particular, a claim element displayed in property value summary 1302 (
As a user selects or de-selects property values from, for example, property value summary 1302 (
Graphical interface 1406 includes citation list 1408 and full text 1410. Citation list 1408 may list filtered patent-related documents, and full text 1410 may display the full text of the patent-related documents.
Property values (either bibliographic or subject matter) previously selected by a user may be highlighted in full text 1410. For example, a part, claim element, or inventor displayed in, for example, property value summary 1302 (
As a user selects or de-selects property values from, for example, property value summary 1302 (
The foregoing descriptions have been presented for purposes of illustration and description. They are not exhaustive and do not limit the disclosed embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practicing the disclosed embodiments. For example, the described implementation includes software, but the disclosed embodiments may be implemented as a combination of hardware and software or in hardware alone. Additionally, although disclosed aspects are described as being stored in a memory on a computer, one skilled in the art will appreciate that these aspects can also be stored on other types of computer-readable media, such as secondary storage devices, like hard disks, floppy disks, a CD-ROM, or other forms of RAM or ROM.
Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.
Number | Name | Date | Kind |
---|---|---|---|
5144679 | Kakumoto et al. | Sep 1992 | A |
5159552 | Van Gasteren et al. | Oct 1992 | A |
5588149 | Hirose | Dec 1996 | A |
5623679 | Rivette et al. | Apr 1997 | A |
5623681 | Rivette et al. | Apr 1997 | A |
5754840 | Rivette et al. | May 1998 | A |
5774833 | Newman | Jun 1998 | A |
5799325 | Rivette et al. | Aug 1998 | A |
5806079 | Rivette et al. | Sep 1998 | A |
5809318 | Rivette et al. | Sep 1998 | A |
5845301 | Rivette et al. | Dec 1998 | A |
5991751 | Rivette | Nov 1999 | A |
6002798 | Palmer et al. | Dec 1999 | A |
6014663 | Rivette et al. | Jan 2000 | A |
6038561 | Snyder et al. | Mar 2000 | A |
6457004 | Nishioka et al. | Sep 2002 | B1 |
6574645 | Petruzzi et al. | Jun 2003 | B2 |
6793429 | Arrison | Sep 2004 | B2 |
6823331 | Abu-Hakima | Nov 2004 | B1 |
6871174 | Dolan | Mar 2005 | B1 |
7162465 | Jenssen | Jan 2007 | B2 |
7194406 | Ejerhed | Mar 2007 | B2 |
7194693 | Cragun et al. | Mar 2007 | B2 |
7254773 | Bates | Aug 2007 | B2 |
7296015 | Poltorak | Nov 2007 | B2 |
7398210 | Valdes | Jul 2008 | B2 |
7412441 | Scott et al. | Aug 2008 | B2 |
7444589 | Zellner | Oct 2008 | B2 |
7516492 | Nisbet et al. | Apr 2009 | B1 |
7533096 | Rice et al. | May 2009 | B2 |
7716581 | Tran | May 2010 | B2 |
7801909 | Poltorak | Sep 2010 | B2 |
7853572 | Lundberg et al. | Dec 2010 | B2 |
7881937 | Hasan | Feb 2011 | B2 |
7890851 | Milton, Jr. | Feb 2011 | B1 |
7904453 | Poltorak | Mar 2011 | B2 |
7941468 | Zellner et al. | May 2011 | B2 |
7949728 | Rivette | May 2011 | B2 |
8037075 | Millett | Oct 2011 | B2 |
8065307 | Haslam | Nov 2011 | B2 |
8160306 | Neustel | Apr 2012 | B1 |
8739032 | Walsh | May 2014 | B2 |
20010049707 | Tran | Dec 2001 | A1 |
20020120647 | Amano | Aug 2002 | A1 |
20030033295 | Adler | Feb 2003 | A1 |
20030115115 | Ouchi | Jun 2003 | A1 |
20030212527 | Moore et al. | Nov 2003 | A1 |
20030220897 | Lee et al. | Nov 2003 | A1 |
20030229470 | Pejic | Dec 2003 | A1 |
20040059994 | Fogel et al. | Mar 2004 | A1 |
20040068453 | Duan et al. | Apr 2004 | A1 |
20040068529 | Pai | Apr 2004 | A1 |
20040078192 | Poltorak | Apr 2004 | A1 |
20040078361 | Hu | Apr 2004 | A1 |
20040078365 | Poltorak | Apr 2004 | A1 |
20040083422 | Duan | Apr 2004 | A1 |
20040083432 | Kawamura et al. | Apr 2004 | A1 |
20040098380 | Dentel et al. | May 2004 | A1 |
20040098673 | Riddoch et al. | May 2004 | A1 |
20040113916 | Ungar et al. | Jun 2004 | A1 |
20040123235 | Yeh et al. | Jun 2004 | A1 |
20040176115 | Atkin et al. | Sep 2004 | A1 |
20040194032 | Liu | Sep 2004 | A1 |
20050005239 | Richards | Jan 2005 | A1 |
20050010863 | Zernik | Jan 2005 | A1 |
20050065920 | He et al. | Mar 2005 | A1 |
20050097464 | Graeber | May 2005 | A1 |
20050108652 | Beretich et al. | May 2005 | A1 |
20050125744 | Hubbard et al. | Jun 2005 | A1 |
20050144206 | Baumann | Jun 2005 | A1 |
20050210009 | Tran | Sep 2005 | A1 |
20050210042 | Goedken | Sep 2005 | A1 |
20050234685 | Tanigawa | Oct 2005 | A1 |
20050261891 | Chan et al. | Nov 2005 | A1 |
20060004730 | Chan | Jan 2006 | A1 |
20060047676 | Ouchi | Mar 2006 | A1 |
20060156222 | Chi et al. | Jul 2006 | A1 |
20060190807 | Tran | Aug 2006 | A1 |
20060271522 | Scott et al. | Nov 2006 | A1 |
20070011154 | Musgrove et al. | Jan 2007 | A1 |
20070055485 | Kierzenka et al. | Mar 2007 | A1 |
20070078886 | Rivette et al. | Apr 2007 | A1 |
20070198578 | Lundberg et al. | Aug 2007 | A1 |
20070208764 | Grisinger | Sep 2007 | A1 |
20070239706 | Zhang et al. | Oct 2007 | A1 |
20070276796 | Sampson | Nov 2007 | A1 |
20070288448 | Datta | Dec 2007 | A1 |
20070288449 | Datta et al. | Dec 2007 | A1 |
20070294232 | Gibbs | Dec 2007 | A1 |
20080016445 | Dykes et al. | Jan 2008 | A1 |
20080033736 | Bulman | Feb 2008 | A1 |
20080086450 | Bittenson | Apr 2008 | A1 |
20080114668 | Peters et al. | May 2008 | A1 |
20080124050 | Deschamp et al. | May 2008 | A1 |
20080183518 | Jiang et al. | Jul 2008 | A1 |
20080243979 | Cherkauer et al. | Oct 2008 | A1 |
20080247532 | Schulz | Oct 2008 | A1 |
20080281860 | Elias et al. | Nov 2008 | A1 |
20090019355 | Jiang | Jan 2009 | A1 |
20090070301 | McLean et al. | Mar 2009 | A1 |
20090077124 | Spivack et al. | Mar 2009 | A1 |
20090138466 | Henry et al. | May 2009 | A1 |
20090157679 | Elias et al. | Jun 2009 | A1 |
20090177656 | Carter | Jul 2009 | A1 |
20090210828 | Kahn | Aug 2009 | A1 |
20090228777 | Henry et al. | Sep 2009 | A1 |
20090276694 | Henry et al. | Nov 2009 | A1 |
20100131513 | Lundberg et al. | May 2010 | A1 |
20100153405 | Johnson et al. | Jun 2010 | A1 |
20100191748 | Martin et al. | Jul 2010 | A1 |
20100287478 | Avasarala et al. | Nov 2010 | A1 |
20110072342 | Tran | Mar 2011 | A1 |
20110093449 | Belenzon et al. | Apr 2011 | A1 |
20110191310 | Liao et al. | Aug 2011 | A1 |
20110307499 | Elias et al. | Dec 2011 | A1 |
20120078979 | Ghimire | Mar 2012 | A1 |
20130124515 | Ghimire | May 2013 | A1 |
Number | Date | Country |
---|---|---|
2156271 | Sep 2011 | EP |
2003-308318 | Oct 2003 | JP |
2003-323322 | Nov 2003 | JP |
2006-065882 | Mar 2006 | JP |
2010-527067 | Aug 2010 | JP |
WO 2008140721 | Nov 2008 | WO |
WO 2009079357 | Jun 2009 | WO |
WO 2011156134 | Dec 2011 | WO |
Entry |
---|
Computer Sciences Corporation, User's Manual for the Examiner's Automated Search Tool (EAST) 2.1, pp. 1-256; especiallly, p. 6-89, Figure 6-78; p. 6-90, Figure 6.79; p. 6-91, Figure 6-80; p. 7.1, Figure 7.1; p. 7.14, Figure 7.14; p. 7.25, Figure 7.25; p. 7.27, Figure 7.27, May 5, 2006. |
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority in International Application No. PCT/US 11/37863 dated Aug. 30, 2011 (14 pages). |
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority in International Application No. PCT/US2008/086540 dated Mar. 9, 2009 (13 pages). |
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority in International Application No. PCT/US/08/05859 dated Oct. 23, 2008 (13 pages). |
Brian K. Elias et al., U.S. Appl. No. 12/314,592, filed Dec. 12, 2008, entitled “Method and Computer Program Product for Analyzing Documents.” |
Brian K. Elias et al., U.S. Appl. No. 12/149,784, filed May 8, 2008, entitled “Systems and Methods for Analyzing Documents.” |
Canadian Intellectual Property Office, Office Action dated Mar. 14, 2017 in Canadian Patent Application No. 2,802,155. |
Notice of Rejection, dated Feb. 22, 2213, for Japanese Application No. 2010-507444 (13 pages). |
Novak, “Conversion of Units of Measurement,” IEEE Transaction on Software Engineering, vol. 21, No. 8, Aug. 1995, pp. 651-661. |
Communication, in European Application No. 08 754 231.2-1238, dated Aug. 23, 2011 (1 page). |
Supplementary European Search Report, in European Application No. 08 754 231.2-1238, dated Jul. 28, 2011 (5 pages). |
International Preliminary Report on Patentability for International Application No. PCT/US2008/005859, dated Nov. 19, 2009 (2 pages). |
International Preliminary Report on Patentability for International Application No. PCT/US2008/086540, dated Jun. 24, 2010 (7 pages). |
International Preliminary Report on Patentability for International Application No. PCT/US2008/086540, dated Mar. 9, 2009 (13 pages). |
International Preliminary Report on Patentability for International Application No. PCT/US2011/37863, dated Aug. 30, 2011 (9 pages). |
Office Action, dated Aug. 8, 2011, in U.S. Appl. No. 12/314,592, filed Dec. 12, 2008. |
Office Action, dated Dec. 13, 2011, in U.S. Appl. No. 12/314,592, filed Dec. 12, 2008. |
Office Action, dated Mar. 3, 2011, in U.S. Appl. No. 12/314,592, filed Dec. 12, 2008. |
Kazuya Konishi et al., “A Support Function of Understanding Patent Claims for Efficient Patent Investigation,” Jun. 2006 (10 pages). |
Office Action, dated May 23, 2012, in U.S. Appl. No. 12/149,784, filed May 8, 2008. |
Office Action, dated Dec. 13, 2011, in U.S. Appl. No. 12/149,784, filed May 8, 2008. |
Office Action, dated May 11, 2011, in U.S. Appl. No. 12/149,784, filed May 8, 2008. |
Office Action, dated Dec. 3, 2010, in U.S. Appl. No. 12/149,784, filed May 8, 2008. |
Number | Date | Country | |
---|---|---|---|
20110307499 A1 | Dec 2011 | US |