US20140379388A1 - Systems and methods for patent portfolio management - Google Patents
Systems and methods for patent portfolio management Download PDFInfo
- Publication number
- US20140379388A1 US20140379388A1 US14/483,903 US201414483903A US2014379388A1 US 20140379388 A1 US20140379388 A1 US 20140379388A1 US 201414483903 A US201414483903 A US 201414483903A US 2014379388 A1 US2014379388 A1 US 2014379388A1
- Authority
- US
- United States
- Prior art keywords
- patent owner
- contact details
- database
- owner
- user
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/93—Document management systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/08—Insurance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
- G06Q50/10—Services
- G06Q50/18—Legal services; Handling legal documents
- G06Q50/184—Intellectual property management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2358—Change logging, detection, and notification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2457—Query processing with adaptation to user needs
- G06F16/24578—Query processing with adaptation to user needs using ranking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/248—Presentation of query results
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/33—Querying
- G06F16/3331—Query processing
- G06F16/334—Query execution
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/33—Querying
- G06F16/338—Presentation of query results
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/35—Clustering; Classification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/35—Clustering; Classification
- G06F16/355—Class or cluster creation or modification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/36—Creation of semantic tools, e.g. ontology or thesauri
- G06F16/367—Ontology
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/38—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/951—Indexing; Web crawling techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
- G06F16/9535—Search customisation based on user profiles and personalisation
-
- G06F17/30289—
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
- G06Q50/01—Social networking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/211—Schema design and management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/903—Querying
- G06F16/90335—Query processing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Human Resources & Organizations (AREA)
- Economics (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Computational Linguistics (AREA)
- Marketing (AREA)
- Tourism & Hospitality (AREA)
- Entrepreneurship & Innovation (AREA)
- Technology Law (AREA)
- Operations Research (AREA)
- Development Economics (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Finance (AREA)
- Primary Health Care (AREA)
- Accounting & Taxation (AREA)
- Educational Administration (AREA)
- Game Theory and Decision Science (AREA)
- Quality & Reliability (AREA)
- Computing Systems (AREA)
- Library & Information Science (AREA)
- Life Sciences & Earth Sciences (AREA)
- Animal Behavior & Ethology (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
Systems and methods for patent portfolio management are proposed. In one example embodiment, a system or method includes maintaining or accessing a database including data relating to patent maintenance fees and due dates. An interactive interface is presented to a user, the interface including a display of a maintenance fee and a due date for at least one patent in the database. The interactive interface allows a user to request a maintenance-fee cost projection for a selected group or portfolio of patents in the database. A notification selection element allows a user to request notification of maintenance fee payments coming due.
Description
- This application is a divisional of U.S. application Ser. No. 13/573,804, entitled “Systems and Methods for Patent Portfolio Management” to Lundberg et al filed Oct. 3, 2012 (Attorney Docket No. 3431.002US1), which application is incorporated herein in its entirety.
- U.S. application Ser. No. 13/573,804 claims the benefit of priority, under 35 U.S.C. Section 119(e), to Lundberg et al, U.S. Provisional Patent Application Ser. No. 61/691,182, entitled “System And Method For Patent Portfolio Management” filed on Aug. 20, 2012 (Attorney Docket No. 3431.033PRV), which is hereby incorporated by reference herein in its entirety.
- U.S. application Ser. No. 13/573,804 also claims the benefit of priority, under 35 U.S.C. Section 119(e), to Lundberg et al, U.S. Provisional Patent Application Ser. No. 61/561,502, entitled “Systems, Methods And User Interfaces In A Patent Management System” filed on Nov. 18, 2011 (Attorney Docket No. 3431.009PRV), which is hereby incorporated by reference herein in its entirety.
- U.S. application Ser. No. 13/573,804 also claims the benefit of priority, under 35 U.S.C. Section 119(e), to Lundberg et al, U.S. Provisional Patent Application Ser. No. 61/542,515, entitled “System and Method for Patent Portfolio Management” filed on Oct. 3, 2011 (Attorney Docket No. 3431.002PRV), which is hereby incorporated by reference herein in its entirety.
- The management of a patent portfolio involves multiple stages. Initially, a decision is made as to what inventions are worth the investment of filing a patent application. Then, each filed patent application goes through prosecution with the patent office. Finally, for each patent that is allowed, maintenance fees must be paid at a variety of intervals to keep the patent in force.
- Some embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings in which:
-
FIG. 1 is a system component diagram, according to an example embodiment. -
FIG. 2 is a block diagram of a patent management system, according to an example embodiment. -
FIG. 3 is a user interface, according to an example embodiment. -
FIG. 4 is a block diagram of machine in the example form of a computer system within which a set instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed. -
FIGS. 5-8 show aspects of methods according to example embodiments. - The life cycle of a patent may include multiple stages. These stages generally include invention, filing a patent application on the invention, prosecuting the patenting application to allowance or abandonment, determining whether to file any continuing applications, and paying maintenance fees on the allowed patent.
- At each stage, one or more parties determine the best course of action to take with respect to the invention. For example, when determining whether or not to file a patent, the inventor may know what products are out in the technology area of the invention, a business manager may know how the invention fits in with a company's goals, and a patent attorney may have researched existing patents or application in the technology area of the patent. These parties will ultimately make the decision whether it is worth the initial investment of filing an application on the invention and then at each future stage determine the next course of action.
- In various embodiments, a patent management system includes tools to help the parties involved in the patenting process make decisions at each stage of a patent's life. These tools may also be used for general research by parties not immediately involved with the patenting of the invention. Additionally, these tools may be used as standalone tools, in combination with other tools, and in combination with other patent management systems. Examples of tools include, but are not limited to prosecution analytics, reference management, prior art analytics, docketing management, claim mapping, claim analytics, portfolio analytics, annuity management, market analysis, user interfaces, and strategic monitoring.
-
FIG. 1 is a schematic view ofcomputer network system 100 according to various embodiments. Thecomputer network system 100 includespatent management system 102 anduser terminal 104 communicatively coupled vianetwork 106. In an embodiment,patent management system 102 includesweb server 108,application server 110, database management server 114, which may be used to manage at leastoperations database 116 andfile server 118.Patent management system 102 may be implemented as a distributed system, for example one or more elements of thepatent management system 102 may be located across a wide-area network from other elements ofpatent management system 102. As another example, a server (e.g.,web server 108,file server 118, database management server 114) may represent a group of two or more servers, cooperating with each other, provided by way of a pooled, distributed, or redundant computing model. -
Network 106 may include local-area networks (LAN), wide-area networks (WAN), wireless networks (e.g., 802.11 or cellular network), the Public Switched Telephone Network (PSTN) network, ad hoc networks, personal area networks (e.g., Bluetooth) or other combinations or permutations of network protocols and network types. Thenetwork 106 may include a single local area network (LAN) or wide-area network (WAN), or combinations of LAN's or WAN's, such as the Internet. The various devices/systems coupled tonetwork 106 may be coupled tonetwork 106 via one or more wired or wireless connections. -
Web server 108 may communicate withfile server 118 to publish or serve files stored onfile server 118.Web server 108 may also communicate or interface with theapplication server 110 to enable web-based applications and presentation of information. For example,application server 110 may consist of scripts, applications, or library files that provide primary or auxiliary functionality to web server 108 (e.g., multimedia, file transfer, or dynamic interface functions). Applications may include code, which when executed by one or more processors, run the tools ofpatent management system 102. In addition,application server 110 may also provide some or the entire interface forweb server 108 to communicate with one or more of the other servers in patent management system 102 (e.g., database management server 114). -
Web server 108, either alone or in conjunction with one or more other computers inpatent management system 102, may provide a user-interface touser terminal 104 for interacting with the tools ofpatent management system 102 stored inapplication server 110. The user-interface may be implemented using a variety of programming languages or programming methods, such as HTML (HyperText Markup Language), VBScript (Visual Basic® Scripting Edition), JavaScript™, XML® (Extensible Markup Language), XSLT™ (Extensible Stylesheet Language Transformations), AJAX (Asynchronous JavaScript and XML), Java™, JFC (Java™ Foundation Classes), and Swing (an Application Programming Interface for Java™). -
User terminal 104 may be a personal computer or mobile device. In an embodiment,user terminal 104 includes a client program to interface withpatent management system 102. The client program may include commercial software, custom software, open source software, freeware, shareware, or other types of software packages. In an embodiment, the client program includes a thin client designed to provide query and data manipulation tools for a user ofuser terminal 104. The client program may interact with a server program hosted by, for example,application server 110. Additionally, the client program may interface with database management server 114. -
Operations database 116 may be composed of one or more logical or physical databases. For example,operations database 116 may be viewed as a system of databases that when viewed as a compilation, represent an “operations database.” Sub-databases in such a configuration may include a matter database a portfolio database, a user database, a mapping database and an analytics. In various embodiments, additional databases are utilized for one or more of the patent tools.Operations database 116 may be implemented as a relational database, a centralized database, a distributed database, an object oriented database, or a flat database in various embodiments. - In various embodiments, the tools of the patent management system share a common framework. The framework may have a base organization unit of a matter. In various embodiments, a matter is an issued patent or patent application that includes one or more patent claims. In an embodiment, a matter is generally identified by its patent number or publication number. Identification may mean either identification as it relates to a user of the patent management system or within the patent management system. Thus, a user may see a matter listed as its patent number while internally a database of the patent management system may identify it by a random number. One or more matters may be associated with prior art or cited references stored in a reference or prior art database.
- One or more matters may be grouped together to form a portfolio. A matter may also be associated with one or more other matters in a family. A family member may be a priority matter, a continuing (e.g., continuation, divisional) matter, or foreign counter-part member. Family members may be determined according to a legal status database such as INPADOC.
- Data stored in a first database may be associated with data in a second database through the use of common data fields. For example, consider entries in the matter database formatted as [Matter ID, Patent Number] and entries in the portfolio database formatted as [Portfolio ID, Matter ID]. In this manner, a portfolio entry in the portfolio database is associated with a matter in the matter database through the Matter ID data field. In various embodiments, a matter may be associated with more than one portfolio by creating multiple entries in the portfolio database, one for each portfolio the matter is associated with. In other embodiments, one or more patent reference documents may be associated with a patent by creating multiple entries in the patent database, for example. The structure of the database and format and data field titles are for illustration purposes and other structures, names, formats may be used. Additionally, further associations between data stored in the databases may be created as discussed further herein.
- During operation of
patent management system 102, data from multiple data sources (internal and external) is imported into or accessed by theoperations database 116. Internal sources may include data from the various tools of the patent management system.External sources 120 may include websites or databases associated with foreign and domestic patent offices, assignment databases, WIPO, INPADOC, and law firm databases. In various embodiments, the data is scraped and parsed from the websites if it is unavailable through a database. The data may be gathered using API calls to the sources when available. The data may be imported and stored in the operations database on a scheduled basis, such as weekly, monthly, quarterly, or some other regular or periodic interval. Alternatively, the data may be imported on-demand. - After data importation, the data may be standardized into a common format. For example, database records from internal or external sources may not be in a compatible format with the operations database. Data conditioning may include data rearrangement, normalization, filtering (e.g., removing duplicates), sorting, binning, or other operations to transform the data into a common format (e.g., using similar date formats and name formats).
-
FIG. 2 is a block diagram ofpatent management system 102, according to an example embodiment. Illustrated areuser database 202,matter database 204, portfolio database 206,mapping database 208,analytics database 210,display module 212,input module 214,mapping module 216, andanalytics module 218. Additional or fewer modules may be utilized in implementing functionality of one or more of the patent tools. In various embodiments, the data stored indatabases patent management system 102 mirrors databases stored in other locations. In an embodiment, when a request is made to access data stored in the databases,patent management system 102 determines where the data is located and directs the request to the appropriate location. Similarly, modules 212-218 may be executed across multiple computer systems. - In an example
embodiment user database 202 stores data representing users ofpatent management system 102. The data may include data fields of user credentials including a user ID and password and access rights with respect topatent management system 102. The user ID may be a common across the tools of the patent management system. In this manner, access rights of the user with respect to the tools of the patent management system may follow across the various tools of the patent management system. In an example embodiment, different access rights are granted to a user ID between the various tools. - In various embodiments, each user ID has access rights to one or matters. Similarly, a user ID may have portfolio level access rights. Access rights may be defined according to at least two parameters: read access and write access. Thus, when a user logs into
patent management system 102, the user is presented with access only to the matters/portfolios that have been associated with the user ID. More (e.g., additional contact information) or fewer data fields associated with a user may be included in a user entry stored inuser database 202. - In an embodiment,
matter database 204 stores data representing matters. Each matter may be associated with one or more portfolios as well. In some embodiments, a matter is associated with no portfolios. In various embodiments, a matter is a foreign or domestic patent or application. Matters may also be inventions that have not yet been filed (e.g., as may be the case within a docketing system). In an embodiment, a matter entry includes data fields representing a matter ID, patent number, publication number, serial number, docketing number, title (e.g., the name of the patent or application), type of the matter (e.g., application, issued patent, PCT application), status of the matter (e.g., issued, abandoned, allowed), a link to the patent office where the matter was filed, a link to a PDF download of the matter, abstract of the matter, inventors of the matter, current owner of the matter, cited references on the face of the matter, filed date, issue date, docket number, and annuity information (e.g., due date, country, and amount due). In some embodiments, other patent reference documents or prior art in any form may be stored and associated with one or more matters. More or fewer data fields associated with a patent may be included in a matter entry stored inmatter database 204. In an example embodiment,matter database 204 may store a patent matter database, wherein this database includes data about the patent matters. The data may include for at least one patent matter a claim set or statement of invention and a priority date for the claim set or statement of invention.Matter database 204 may also store a database of prior art documents (also known as “references”), wherein the prior art database includes data about the prior art documents. The data may include for at least one prior art document a priority date or publication date of the document. One or more of the prior art documents may be associated with a first patent matter in the patent matter database. - In various embodiments, a matter is associated with one or more other matters as a family with a family ID. Family members may be priority documents, continuation patents/applications, divisional patents/applications, and foreign patent/application counterparts. In an embodiment, family information is determined according to an external source such as INPADOC. Patent reference documents and/or other prior art may be manually or automatically stored, cross-cited and associated with related family matters, for example.
- Portfolio database 206, in an example embodiment, stores data representing portfolios of one or more matters. Data stored in portfolio database 206 may have been previously generated by a tool of
patent management system 102. In various embodiments, a portfolio may be generated by a user usingpatent management 102. For example, a user interface may be presented to the user requesting a name for the portfolio and identifiers of matters to be included in the portfolio. In an embodiment, a portfolio entry in portfolio database 206 includes data fields of portfolio ID and portfolio name. Additionally, a data field for matter ID may also be included in an entry in the portfolio database. Thus, each portfolio may be associated with one or more matters through the use of the matter ID data field. More or fewer data fields associated with a portfolio may be included in a portfolio entry of portfolio database 206. - In an example embodiment,
mapping database 208 includes mappings of scope concepts, technology categories, and keywords to one or more matters. In an embodiment, a scope concept is a textual description of what a patent claim is at least limited to. Thus, if a claim comprises A, B, & C a scope concept may be A. In various embodiments, a scope concept for the claim may be broader than A because the claim will still be limited to the broader scope concept. In an embodiment, the mapping database stores mappings between claims and scope concepts. A technology category mapping may indicate a claim is in a certain technology area. A keyword mapping indicates may indicate that there is an exact match between the keyword and a subset of the claim language. - In various embodiments,
analytics database 210 stores data representing calculated analytics on data stored withinpatent management system 102 or external data sources. In various embodiments, analytics are organized according to an individual matter, a portfolio, or family. The calculated analytics may be based on information gathered from multiple sources such as databases ofpatent management system 102 and PAIR. - In various embodiments, information for an individual matter may include status (e.g., disclosure received, drafting, filed, completed-waiting examination, in prosecution, allowed, issued), cited prior art, list and type of rejections (e.g., 35 U.S.C. §101, 102, 103) number of claims allowed, office action count, interviews held, IDS statements filed, attorney fees to date, and PTO fees to date. Further metrics for an individual matter stored in
analytics database 210 may include, time waiting for examiner, total time in examination, time waiting for PTO while in examination, time on appeal. Additional prosecution details formatter may include an upcoming docket dates (e.g., due dates for office action, IDS due dates, etc.). A claim prosecution history chart may also be stored inanalytics database 210 for each matter. The prosecution history may include a history of claim amendments and arguments made in prosecution. - In various embodiments, portfolio and family analytics information may be stored in
analytics database 210 based on aggregating the metrics for an individual matter. In an embodiment, the analytics of a family may differ from those in a portfolio as not all family member matters may be part of a portfolio. Additionally, the analytics may be stored for multiple time periods such that comparisons may be made between metrics currently and metrics a year ago (or other time period). - Aggregated metrics may include a total patents and applications, pending and waiting for examination, in prosecution with no claims allowed, in prosecution with some claims allowed, appealed, notice of allowance received, and issued. These metrics may be compiled for both US and international matters in the portfolio. Additional information may include the international portfolio distribution by country. An age distribution of the portfolio may also be compiled. For example the portfolio may be broken down by less than one year old, 1 to 3 years old, 3 to 5 years old, 5 to 10 years old, 10 to 20 years old, and 20 or more years old. Recent filing and issue activity as well as upcoming Ford filing deadlines may be stored in
analytics database 210. - In various embodiments, prosecution metrics across a portfolio or family are determined and stored in
analytics database 210. This data may include matters waiting for examination, matters in examination, matters appealed, and cases allowed but not yet issued. Analytics with respect office actions may also be compiled and stored. For example success of allowance after a first office action response, a second response, etc., may be stored inanalytics database 210. Additional prosecution analytics may include allowance rate (e.g., 10%) after a telephone interview, allowance after an in-person interview, percentage of interviews with response, number and type of rejection, average time in prosecution (e.g., in months), average time to file a response, and average time to next office action. Further, the list of recently allowed cases, recently appeal cases, stalled cases, and recently abandoned cases may also be stored for each portfolio and family inanalytics database 210. - In various embodiments, the results of keyword analysis on one or more matters and/or prior art references may be stored in
analytics database 210. The keyword analysis may be based on the occurrences of the keywords in the matter or references to derive a score or keyword overlap. - In various embodiments, data stored in the database for group of matters in a portfolio or family is analyzed to determine the top (e.g., ten) most cited patents, the top most cited inventors, top most cited prior art owners (e.g., according to assignment documents or the face of the patent), newly (e.g., within the last 60 days) cited prior art owners, and top most cited prior art inventors. This information may be stored in
analytics database 210. - In an embodiment,
display module 212 is configured to display user interfaces and information retrieved from one or more databases 202-210. If a user is accessingpatent management system 102 remotely (e.g., through a web browser)display module 212 may be configured to transmit data representing a user-interface through a network to a user terminal. In various embodiments,display module 212 is configured to generate one or more charts of data stored in databases 202-210. For example,display module 212 may generate a pie chart of the top 10 inventors within a portfolio. - In various embodiments,
input module 214 receives data from multiple sources where it may be further processed by one or more other modules and stored in one or more of databases 202-210. For example,input module 214 may be configured to utilize one or more APIs to data from one or more patent data stores (e.g., public PAIR, private PAIR, INPADOC, foreign patent offices, patent docketing systems, portfolio management systems, etc). The data may include published patent documents, patent applications, office actions or other patent office correspondence, prior art references, claim mappings, dockets dates, and annuity payment data. - In various embodiments,
input module 214 is configured to receive input from one or more user interface elements. For examplepatent management system 102 may present multiple user interfaces to a user. These user interfaces may enable users to input data directly into databases 202-210, instruct the patent management system to retrieve data from patent data stores, and instruct the patent management system to perform various operations (e.g., analysis) on the data in databases 202-210. - Additionally,
input module 214 may be configured to determine the selection of one or more user interface elements by a user and initiate the action associated with the selected user interface element. For example, a user interface element may include a drop-down menu to select a portfolio.Input module 214 may be configured to receive the selection of the portfolio by the user. Then,input module 214 may pass the selection to one or more other modules for further processing. For example,display module 214 may update the drop-down menu to indicate the selection of the portfolio. - In various embodiments,
input module 214 processes the data that has been inputted and formats it according to the data fields of databases 202-210 as discussed above. Is various embodiment processing is completed using a parsing module (not shown). For example, consider a patent publication that a user has directed to be inputted into one or more of the databases. The processing module may use a combination of automatic image recognition and text analysis to determine the filing date, issue date, title, abstract, and claims of the patent. In some embodiments, the parsing module may flag certain pieces of data that had been determined to be potentially inaccurate (e.g., a number could not be read). A user ofpatent management system 102 may then examine the flagged data and manually enter the information which is then stored in the appropriate database. - The resulting data that has been parsed by the parsing module may then be entered as an entry in one or more of databases 202-210. This may be accomplished by, for example, formulating an insert SQL query with the parsed information. In various embodiments the parsing module may parse multiple piece of information before generating a database entry. For example,
input module 214 may receive a docket number for an issued patent. The docket number may be combined with the information parses from the issued patent to form an entry inmatter database 204. - In various embodiments,
mapping module 216 is configured to facilitate mappings of scope concept, technology categories, and keywords to patent claims of a matter. In an embodiment, mapping signifies association. For example, in conjunction withdisplay module 212 andinput module 214,mapping module 216 may present a user interface of patent claims stored inmatter database 204 and scope concepts stored inmapping database 208.Input module 214 may receive a selection of one or more patent claims and one or more scope concepts and pass them tomapping module 216.Mapping module 216 may then formulate an SQL query to associate the one or more patents claims with the one or more scope concepts. When executed, the SQL query, may update themapping database 208 with the associations. In various embodiments,mapping module 216 also allows the creation of new scope concepts, technology categories, and keywords that may be mapped to one or more patent claims. Furthermore, mapping module may present user interfaces that allow a user to rank and rate matters stored inmatter database 204. -
Mapping module 216 may also allow the generation of claim charts of a plurality of cells. A claim chart may include one or more scope concepts, technology categories, and keywords on one axis and claims of matters in a portfolio on the other axis. The claim chart may include a variety of levels of granularity of scope concepts. Some claims may be mapped to all of the scope concepts while others may not be mapped to any scope concepts. At the cell intersection between a scope concept (or technology category or keyword) and a claim an indication of the mapping may be presented by changing the format of the cell. For example, the cell may be colored blue when a scope concept is mapped and red when not mapped. - In various embodiments,
analytics module 218 is configured to examine and run calculations on the data stored in the databases 202-210 to generate the analytics discussed previously. For example,analytics module 218 may formulate an SQL query that retrieves the number of times that a prior art reference has been cited within a portfolio. This query may be run for each prior art cited within the portfolio to determine a list of the most cited (e.g., the top ten) prior art references with a portfolio. In an embodiment, the queries are formulated and run as requested by a user. In an embodiment, once the analytics information has been determined, it is stored withinanalytics database 210. In various embodiments, queries are formulated and run on a periodic basis (e.g., nightly) and entries inanalytics database 210 may be updated to reflect any changes. - In various embodiments, the
analytics module 218 is configured to receive input identifying a pool of keywords for a first patent matter in matter database 206 and associated prior art documents in matter database 206. The term keyword is intended to include individual keywords as well as a number of keywords grouped together making up a key phrase, for example. Themodule 218 may be further configured to perform a keyword analysis on the first patent matter and associated prior art documents based on occurrences of the keywords in the first patent matter and associated prior art documents. Themodule 218 may be further configured to identify, based on the analysis, keywords occurring uniquely in the first patent matter. In view of their uniquely occurring nature, these keywords may be regarded as claim elements potentially differentiating the claim set or statement of invention over the disclosures contained in the one or more prior art documents. - In various embodiments, a filtering module is configured to filter a set of matters according to a user preference. For example, a user may activate a check box that indicates only pending matters should be shown in a user interface. The filtering module may formulate a query consistent with retrieving only pending matters. The results of the query may then be shared with
display module 212 where the user interface may be updated. - In various embodiments, a payment module is configured to receive selections by the user of which annuities to pay for matters in a portfolio. Additionally, the payment module may receive user preferences related to the payment of the annuities. The payment module may receive payment information from a user and forward the payment information to the appropriate agency/office. In some embodiments,
annuity management system 102 organizes payment of the annuity on behalf of the user and the user paysannuity management system 102. -
FIG. 3 is anexample user interface 300 ofpatent management system 102 which may be used to facilitate the methods, tools and systems described herein.User interface 300 is illustrated with multiple user interface elements. In an example embodiment, a user interface element is a graphical or textual element that a user may interact with to cause an application to perform an assigned action for the interface element. Data representinguser interface 300 may be transmitted vianetwork 106 and presented on a display ofuser terminal 104 through the use of a web browser. A user (e.g., manager of a patent portfolio) may interact with the user interface elements ofuser interface 300 through the use of an input device (e.g., stylus, cursor, mouse, finger) of the user terminal. In an embodiment, a user selection is based on the coordinates of the input device as it makes contact with the display or where a user “clicks” the mouse. The coordinates are compared to the coordinates of the user input element to determine the selection. The type of user elements, names, and layout depicted inFIG. 3 are intended to be an illustration of an example user interface ofpatent management system 100. Other types of user elements, names, and layouts may be used. - The user interface elements may include my
matters 302, patent watches 304, and company watches 306. These elements may be used to select a context/view of the patent management system. For example, my matters lists the patents included within a portfolio of a user, patent watches lists information on patents that the user has indicated the patent management system is to watch, and company watches lists information on companies that the user has indicated the system should watch. Further details of each of these included herein. -
Date boxes box 312 displays the amount due with respect to annuities for patents in the portfolio of the user within the period indicated bydate boxes - Drop-
down menu 314 includes a list of portfolios that a user of the patent management system is authorized to view. For example, beforeuser interface 300 is displayed, a login screen may be presented to the user which requests a user ID and password. In various embodiments, the user ID is associated with one or more portfolios. In turn, each portfolio is associated with one or more matters. Matters may include US and foreign issued patents, pending patents, abandoned patents, and not yet filed applications. Thus, upon selection of a portfolio using drop-down menu 314,user interface 300 is populated with matters associated with the portfolio. -
Checkbox 316 is an option to only display matters that currently have an annuity due. Drop-down menu 318 allows further filtering of matters. For example the matters may be filtered by US patents only, US patent applications, and foreign only. - In various embodiments, activation of
button 320updates user interface 300 to reflect the choices made by the user with respect todate boxes checkbox 316, and drop-down menu 318. For example, amount duebox 312 will be updated to reflect the amount due within the new period and the matters listed undercolumn headings 322 may be filtered. In various embodiments,user interface 300 is updated as the user selections are made with respect toelements 308 to 318 without activatingbutton 320. - Prosecution Analytics
- Various tools may be implemented using the system described above. Some of the tools are described below.
- In various embodiments, a software tool to collect and present prosecution analytics may be used with
patent management system 102. For example, a dashboard may be displayed for each matter in a user's portfolio to give specific information for the matter or overall portfolio metrics. For each matter the dashboard may include docket dates as well as analytics listed below. - In various embodiments, analytics including success rate(s) of responses based on the following:
-
- a. Probability a response will result in allowance or other event;
- i. Responses of different types, e.g. non-final, final, after final;
- ii. Based on class/subclass;
- iii. Based on examiner;
- iv. Based on art unit;
- v. Based on number of prior responses;
- vi. Based on how long the case has been in active prosecution;
- b. Analytics—success rates based on USPTO statistics or Attorney or Attorney Organization data;
- i. Probabilities of 2 for each—USPTO vs. Attorney vs. Attorney Org;
- ii. Compare both;
- c. Analytics—success rates based on Owner of Patent/Invention;
- d. Analytics—success rate based on type of owner—e.g., small or large entity;
- e. Analytics—success rates based on Prior Art Owners;
- f. Analytics—success rates based on length of claim;
- g. Analytics—success rates based on number of words added to claim;
- h. Analytics—success rates based on length of arguments;
- i. Analytics—success rates based on type of rejection;
- j. Analytics—success rates based on effective date of prior art; and
- k. Analytics—success rate based on keyword/key phrase overlap between prior art and application specifications
- a. Probability a response will result in allowance or other event;
- In an embodiment, additional analytics are displayed to a user based on analytics in PAIR like system (sometimes referred to as PAIR Plus): statistics for examiner; supervisor; statistics for art unit; statistics for class/subclass; and analytics on the prior art.
- In various embodiments, prosecution Analytics are generated from PAIR and combined with information in an existing file management (e.g., docketing) system. The analytics may be combined to generate portfolio prosecution Analytics. Success rates may be checked based on results (e.g., correlate to attorneys and examiners).
- Reference Management
- In various embodiments, tools for prior art management are used in
patent management system 102. In an embodiment, in a matter management system (e.g., patent management system 102), there us a cross-citation control panel for citing prior art between cases. In various embodiments, the control panel: -
- i. shows all cases to “send” art to or “receive” art from or both;
- ii. allows user to set rules for sending or receiving based on;
- a. Number of time art has hopped already to get to the matter;
- b. Type of citation—102(b)/103;
- iii. Cases to send or receive from can be automatically populated by family matters or other matters.
The tool may also show citations pathway for each reference: - a. Where it started;
- b. What it flowed through;
- In various embodiments, a prior management portfolio may be created by that has features of:
-
- a. Loading Matters (pending or issued apps) into special “prior art management” portfolios;
- b. Art automatically flow between Matters in a portfolio;
- c. Art flows between portfolios via Matters listed in more than one portfolio;
- d. Art is kept in list in Portfolio;
- e. Not based on patent family or related cases necessarily—any arbitrary cases can be added;
- f. Art displayed in each Matter can be filtered by:
- i. Cross-cited art (art arriving from other Matters);
- 1. Number of hops to get to list;
- 2. Type of rejection (102/103);
- 3. Other analytics—see e.g., prior art analytics;
- 4. New art added to Portfolio;
- i. Cross-cited art (art arriving from other Matters);
- g. Art can be added to Portfolio, in the Prior Art (called “references”) list;
- i. This art is not cross cited to other Matters in other portfolios until it is added first to a Matter to be cited or as cited;
- ii. This art is displayed for each Matter to be considered, as “new art” not yet cross-cited”
- In various embodiments, PAIR Plus may include:
-
- a. Pair data;
- b. Uncited art cross-reference;
- c. Links to cases beyond PAIR;
- d. Scanned docs;
- e. Art analysis;
- f. Art highlights;
- g. Analytics with Actions;
- h. Foreign cases;
- i. Docket Dates for Matter—calculated by PAIR PLUS;
- j. PAIR Process Options—process options for any given point in a case
- k. Foreign PAIR; a. Aggregate of US and foreign PAIR
- In various embodiments, PAIR Plus may also automatically proof claims, scan amendments, assemble most recent claims, compare to issued patent, scan prior art, make a list of prior art, and compare it to the issued patent. Differences may be determined between the filed specification and issued specification. The differences may be presented to a user for review.
- Prior Art Analytics
- In various embodiments, a tool for analytics of prior Art includes:
-
- a. Automatic keyword/key phrase differentiation;
- i. Create pool of keyword/key phrases for prior art and for pending application;
- ii. Note differentiating keyword/key phrases;
- b. Automatic prior art ranking based on keyword/key phrase overlap;
- i. Art with most keyword/key phrase overlap is highest ranked;
- ii. Allow manual addition of synonyms to enhance analysis;
- c. Prior art timeline graphs;
- i. Show timeline with dates of prior art vs. application;
- ii. Show timeline of all patents or applications in class/subclass, in comparison to pending application;
- d. Keyword/key phrase timeline graphs;
- i. Show timeline of when keyword/key phrases of application first appeared in prior art;
- ii. Could be table/chart with keyword/key phrases listed by order of appearance by year, with representation of each year; and
- e. Dominance of owners by keyword/key phrase—show which owners own most art with matching terminology (also for payment analytics).
- a. Automatic keyword/key phrase differentiation;
- In various embodiments, an analytics tool may be used to determine prior art overlap. For example, for example competitor overlap for single patent, portfolio, or family may be include:
-
- a. prior art citation overlap;
- b. overlap of prior art cited against Target Company's patent or portfolio, and prior art cited against Competitor Company or Companies, identified by user;
- c. analytic result may include a list of prior art cited against both the Target and the Competitors;
- d. analytic result may include list of companies that own prior art cited against Target and Competitors (e.g., show the number of references cited against both owned by Target).
- In various embodiments, a process is used that: 1) looks at US patent and if it shows a reference was applied, get name of company it was cited against and highlight that company as a target for the applied reference; 2) for applied references, crawl PAIR and OCR or otherwise reverse engineer the reason reference was cited, and pull comments by PTO or attorney; and 3) take note if it was a §102 reference or §103. Then, In various embodiments, do the same for foreign references of PCT search. For example, determining if an applied reference was a 102/103 a tool may determine the name of the applied reference from the face of patent and then look for text “102” or “103” near the reference in the ocrd text, or like in foreigns.
- An output may include a chart with headings of Prior Art Reference, # Cited against Target, and #Cited against Competitor 1, 2, 3 with example entries:
-
- Reference A, [x], [y, z, a . . . ]
- Reference B, [e], [b, c, d]
- In various embodiments, a tool is used for prior art and forward reference citation analysis. The tool may generate a continuing stream of “watch results” for a single patent (or a group of patents). In an embodiment, there is a problem if an inventor or company sets up a watch to see if their patent is being cited by later-issued patents, many times no such cites occur for a long time, if at all. The tool helps produce a steady stream of watch results, on a daily/weekly/monthly basis. The tool may for: a. Forward cites of prior art: i. take the pool of all prior art cited on patent; ii. watch for forward cites of any of this art; iii. report these forward cites; b. Forward cites of applied prior art only: i. take pool of applied art cited on patent (USPTO puts asterisk on these); ii. watch for forward cites; iii. report these forward cites; c. Forward cites of patent being watched; i. this is prior art; d. Forward cites of forward cites; i. here we look at the forward cites of patent being watched; ii. report any forward cites of those references; e. forward cites of forward cites of prior art. In various embodiments, the display of these results can be dynamically determined based on the number of results available by: a. for example, may want to suppress presentation of more remotely relevant watch results if there are plenty of more pertinent watch results; b. or, list results in order of perceived pertinence; i. forward cites of watched patent of course most relevant; ii. perhaps forward cites of applied art next most relevant; iii. then, perhaps, forward cites of forward cites; iv. then, perhaps, forward cites of any prior art reference; F) Also, the tool can filter watch results from the company that owns the patent—so if the owner of the watched patent cites back to it, the tool may provided an option to ignore those results.
- In various embodiments, a prior art date analyzer is used to: a) In PAIR, using patent number, pull priority dates from PAIR or other source for US patent/application; and b) apply prior art rules to determine likely effective date of reference.
- Docketing Management
- In various embodiments, the PAIR Plus tool may include a docket verification-docket built in. For example: a) PAIR or portions thereof may be scraped or copied; b) in particular, transaction log or log of office actions; c) a docket engine that may be part of the tool; d) the docket engine may determine a set of docket dates—response due dates etc., e) due dates may also be for foreign filing or prior art cross citation; f) those dates are associated with or embedded into a PAIR document; g) user may download the PAIR document and the due dates are either on a PDF or on an Excel or XML or other form with document; h) or, user can synchronize their Outlook calendar with PAIR due dates; i) If the tool does not know the date, the tool may flag that and add to calendar or list of exceptions as an exception that needs to be looked at; j) or, there may be a PAIR docket system that users may subscribe to and get a docket that is driven directly off of PAIR—(e.g., the tool can check things off as done once filed in PAIR); ii. and the tool can docket a date that is not a response date (e.g., foreign filing or as noted above, IDS cross cites); k) the PAIR docket can also check other related matters, and docket for prior art cross-citation if system sees references cited in related case.
- In various embodiments, to obtain some of the data above the tool may scrape or download PTO actions from foreign patent offices (either selectively or in bull( ) OCR to get electronic data or reformat electronic other data downloaded, provide that electronic data to a user/operator of a docket system, and provide an import mechanism for the docket system, either as a BOT or through an API, to load docket information.
- In various embodiments, another tool of PAIR plus may include automatically OCR of all PAIR docs and provide word or PDF text doc versions of PTO docs to PAIR plus user and/or using automatic text analysis, the tool may extract details/types of PTO actions as well as references. This then is added to the data set for the patent, and delivered in PAIR plus. In an embodiment, PAIR plus looks similar to the traditional USPTO site but with extra metadata.
- In various embodiment, a tool is used to verify the accuracy of information for transferred in files as well as automating some of the entry of information for those files. For example the tool may search for an owner's name in international data, then picking additional matters to open from there, and automating the file entry. For example, the file type could be determined (e.g., PRV, ORG—which may or may not actually claim priority to another country—EPPAT, Non-PRV, CON/DIV. The tool may select the file type and automate the data entry after that. For example, the tool could also scan paperwork and OCR to extract key identifying information. The tool may get owner's name, pull a report from public PTO data that shows all of that owners files, and then have a user pick the file that matches the one they are opening. Additional data verification may include serial numbers and priority and filing dates from international patent databases, or US databases for US cases, in order to verify or even semi-automate entry of data for matter openings.
- In various embodiments, a tool is used to set up goals and display progress towards those goals for a given period (e.g., quarter, year). The goals may include, number of new patent applications, number to issue, number of disclosures and, and number of defensive publications. The goals may also be separated out by country. A dashboard interface may display the goal and the current status (e.g., how m any patent applications have been filed). The interface may also include how many patent applications (or other goal metric) need to be filed per day/week in order to achieve the goals.
- In various embodiments, a docketing management system may be improved in the following manner: 1) in the activity view, include a link that launches a calendar view of all milestone dates, with final dates highlighted, for example yellow for 5 months response date and red on 6 month response dates it red on foreign filing dates; 2) one of the above can be displayed for all activities or just one; 3) calendar can either be a monthly calendar with each day represented as a square, or monthly, with each month as a square but no daily detail, or yearly; 4) the other display mode may be a timeline mode; 5) for the timeline mode, each activity (process) can be represented as an individual horizontal line that has milestones and due dates for milestones and the corresponding dates of each horizontal line can be vertically aligned; 6) each activity/process can have a cost associated with it and the cost may be dependent on choices to be made for the process, like foreign filing, there can be a wizard that might for example launch process timelines for each contemplated foreign filing and the costs associated therewith; 7) projected costs for all processes are totaled on timeline to show timing of costs in the aggregate.
- In an example implementation activity tasks/due dates are read and translated to Timeline format, and aligned in a timeline view of the case processes. Cost data for each activity can be kept and read to supply budget information. Activities may also be tagged as optional or essential, and if optional their costs could be suppressed to see how total budget is affected.
- In various embodiments, a visual process manager tool is implemented. It may include the following features: 1) Each Process (e.g., draft application, office action report, response, etc.) has a timeline (or calendar). Timeline is visual of process due dates and milestones; 2) each process has it's own Process Options or Decisions; 3) each process has a messaging area that attorneys/paralegals can post messages regarding the process. These messages can then be sent to client via one or more or all of media: e-mail, text, written letter, telephone call (recorded); 4) each process has messaging area that can store and retain key client messages or instructions, either in the form of a recorded telephone call or message, a saved e-mail, a saved text message, an image of a document; 5) process can require client verification of key processes by either: automated telephone call with dtmf of voice response; automated e-mail with reply or click through to page with verification options.
- In various embodiments, for a process (e.g., foreign filing in and maintenance fee decisions), a process verification engine may obtain verification of key decisions from client and if no such verification is obtained, an alarm may be triggered. The process may include the following: 1) foreign filing paralegal obtains client instructions; 2) paralegal tells client they will be required to provide us verification. Verification may be obtained from a known/approved phone number or using an approved e-mail or fax or using some other authentication (at customer option perhaps); 3) client then, for example, gets telephone call to verify instructions that are recorded in the system (for example from a menu of options—“no filing”, file in PCT, file in (pick countries), or they receive an email and have to reply “confirmed” or click through. In an embodiment, the verification is offered as an option to one or more templates for a process. In another embodiment, this may be a separate key process verification engine that ran verification separate from a main docketing engine. In various embodiments, verification may require a bulk process.
- In various embodiments, a tool of a docketing system may offer possible procedures available for an attorney or client for each activity. The possible procedures may be based on milestones and advantages/disadvantages for each procedure and cost.
- In various embodiments, a docketing management tool may keep standardized instructions, or instructions customized for particular clients. These instructions can them be readily associated with processes or reporting procedures so they are consistently delivered to clients. For example, if a client views a dashboard or gets a report out email.
- Claim Mapping
- In various embodiments, a tool may run analytics on scope concepts or claim keyword Google Search using: a. Scope Concepts are fed into Google, or otherwise used to search Internet, to generate a list of search results; b. Differences in Search Results from one day to the next, or one week to the next, is displayed as “new results”; c. Search is done either on all Internet or is executed only to look for appearance of hits on specific competitors; d. new search results are shown each day or periodically; e. Same thing can be done as above, but instead of using scope concept, the tool takes the keywords from the claim and use those keywords (keywords from claims can either be just all non-routine words or can be determined by looking to see which keywords are unique compared to cited prior art); f. generate search results from web for informational purposes; and g. can use linguistic analysis to find matches.
- In various embodiments, a tool may organize concepts within Panoramic Claim Charts. The process may include: a) meta-label sort to organize concepts under meta-labels; b) meta-labels are like Scope Concept groups; c) have Scope Concept groups that are added by mapper, and can organize map output by the groups; d) ability to direct/specify the order Scope Concepts are displayed, and be able to store for later reuse as well as be able to hide concepts too.
- In various embodiments, concepts from independent claims may be applied to dependent claims by: a) rolling down of mapping from independent claims to dependent claims; b) Optional reporting on that—so show in panoramic map, make roll down optional, (i.e., treat independent claim limitations as if they were part of dependent claims, or not, optionally); c) relationship may be calculated on the fly.
- In various embodiments a tool is used to determine a claim similarity and uses a claim similarity index to identify claims to map scope concepts to. The similarity of paragraph of claims or total claim may be measured by: a) keyword similarity—roots of words are compared after throwing out unimportant words; b) linguistic analysis—how similar based on other approaches. In one implementation, a mapping system may suggest to users mapping claims which claims are most similar to one another, or what parts of claims are most similar to one another. In another implementation, claims are just flagged as similar for later use. In an embodiment, claims are determined to be similar based on keyword similarity
- In various embodiments a tool is used when mapping claims allowing a user to highlight the claim terms associated with a scope concept across a number of claims, storing those associations, and then when subsequently displaying those claims. For example, showing which claim terms have already been mapped (e.g., by highlighting those terms, perhaps in different colors for better visualization). This may be helpful in those cases where you move to another patent and have already mapped portions of claims. This would make it easier to see what you've mapped. In an embodiment the system automatically identifies common claim terms or elements and displays this so a user could map them more quickly. The user may define common claim terms or set a filter them based on unique words or phrases of a certain number of words.
- In various embodiments a tool is used to aid in mapping claims to a product. For example, instead of using claim map, the tool show claims parsed by paragraph. Next to each paragraph, a user can indicate if the product includes the technology described in the claim.
- In an embodiment, a tool is implemented for use in mapping and product analysis. The tool may: 1) grab Field of Invention and present with claim map; 2) grab claim segment or segments, maybe one or two per claim, that look to define point of novelty or at least help position scope of claim—optionally link to specification segment; 3) indicate how much of claim percentage wise is in limitations; 4) display mapped claim elements in chart that user can designate “relevant” or “not relevant,”; 5) optionally calculate relevance to a product or technology; 6) optionally keyword map the chosen claim segment and show keyword chart; 7) optionally allow user to designate relevance of keywords and optionally automatically calculate relevance to product; 8) optionally add more keyword as synonyms; and 9) use keywords, synonyms, field of invention and/or mapped segments, or other patent-related information to find related products on web sites or to find similar patents that are later issued.
- In an embodiment, the technical field of a matter is issued as a claim mapping concept. The technical field may then be used as fuzzy scoring technique to score the relevancy to a technology or product.
- In an embodiment, a tool is used to use keywords of a claim to rate its relevance to a product. For example, claim keywords or phrases are isolated from claims and associated with claims. Users may rate the applicability of the isolated keywords or phrases to a target technology/product. The ratings may be used to determine score of relevance of claim to technology/product. The result may be an indication of relevance, where relevance is determined by exclusion like in claim mapping.
- Portfolio Analytics
- In various embodiments, a tool for portfolio analytics may be used that has the following features: a. Keep cases organized by; i. List of all Individual Matters; ii. For each Matter, a list of family matters; iii. For each Matter, a list of prior art; iv. Matters can be organized into Portfolios; 1. For each portfolio, there is a “roll-up”; a. A group of matters; b. A group of prior art references (from all matters); c. A superset group of family members (from all matters) (note, all family matters may be in portfolio so in that case it would be redundant); b. Generate analytics for individual matters; i. Matter itself; ii. For family group; iv. For prior art group for the matter; c. Generate analytics for Portfolio; i. For aggregate of Matters in portfolio; ii. For aggregate of Prior Art in portfolio; iii. For aggregate of Family members for portfolio; d. Add list of competitors; i. Generate comparisons between patents owned by competitors and Matters in portfolio; 1. By technology—class/subclass/other; 2. By other groupings; e. Add list of technologies—e.g. by class/subclass or by other criterial; i. Generate comparisons based on technologies.
- In an embodiment, a tool may rate importance of a US continuation by automatically determining the amount of overlap with a prior case. For example, 1) are claims longer or shorter? 2) what is the keyword overlap or uniqueness between cases? More or less keywords? 3) What are the common and unique claim limitations?
- In an embodiment, a tool is used to compare issued patent claims with published claims to generate “novelty” material. Here the tool may look for words or word roots or phrases found in issued claims but not in published patent. These changes may represent the most novel portions of the claims. This can be used for various purposes. For mapping, it may be used to help identify a novelty scope concept. For just understanding patent, or potential FWE, it may show what was added to claims. One output may be patent claims showing which words were not in application claims as published. A map be generated with automated patent mapping to identify interesting material to map.
- In an embodiment, a tool is used to look at abandonment rate for class/subclass or prior art family. Also, the rate of abandonment for the prior art for a case, and particular art, may be determined. In various embodiments, the tool may look at 102/x reference rate and display the rate to a user. Abandonment suggestions may be based on the same analysis.
- In various embodiments, a tool is used to look at the internal versus external ratings of a patent. For example, the tool may create a rating for a patent that is based on relevance to the company's own key technologies/patents and a rating for external companies—relevance to the other companies key technologies/patents.
- In an embodiment, for the internal rating for Subject Company:
- 1. Identify automatically or manually the best patents a company has; a. For example by company picking them; b. Or by looking at how many times patent is cited; 2. Rate any given patent of the Subject Company by its relevance to the best patents a company has, 3. Other parameters.
- In an embodiment, for the external rating for the Subject Company: 1. For any given Competitor company, figure out the one or more best patents that the company has; and 2. Rate the relevance of any give patent of the Subject Company to the Competitor Company. In other words, for external ratings, the relevance of any given patent of the Subject Company (one for example you may need to pay an annuity on) to each Competitor is rated Competitors can be used picked, or determined by which companies have patents in same class/subclass or cited against Subject Patent.
- In various embodiments, a tool is implemented to determine what classes/technologies a company has the best position in. This may be based on percent of a class/subclass and total number of citations. The tool may determine open areas for a company based on existing filings. For example, it may show the areas with the most promise for patenting based on a number of patents and timeline for the class (e.g., how close to the beginning of filings for a particular area).
- Annuity Management
- In various embodiments, a tool for annuity payment architecture has: a. Have master US patent database, and foreign patent database; b. Allow subscribers to identify their patents in this pre-populated database; and c. Set up payment option for them.
- In various embodiments, a tool is used for annuity follow me tracking. For example, the tool may track owners of patents so that when it is time to pay annuity, they can be found. Features may include: a) track patent requiring annuity; b) add contact for patent-name, physical address, emails, text message address, mobile, land line; c) add second or third backup contacts—names, physical address, emails, phones, employers, social security number if possible; d) contact is pinged periodically, automatically; e) if no reply, ping goes to backups to find owner; f) lack of contact info for owner is identified early; g) This functionality may be tied to either: 1) a single patent; 2) a group of patents; h) UI—user sees list of patent(s). User can choose “follow me” service for reminders on these patents; i) reminders can come multiple ways—as noted above; j) add reminders to LinkedIn or to Facebook—social network tie-in. these are places that someone would likely stay connected to; k) connect to LinkedIn or Facebook, or other SN, and monitor if the person is present, and if the person disappears from there, flag them as “missing” to invoke follow up tracking; l) have application in LinkedIn or Facebook that keeps track of patent maintenance fee due dates, and notifies user when due; m) have iPhone/smart phone app that keeps track of dates, they could be embedded in App not only downloaded, and generates alerts for payment—while fee may change, typically date due will not; n) create a “remind me” hierarchy—start with automated e-mail/call/text to first person on list. If they don't reply, go to the second person, and so on, till you exhaust list, trying to reach someone.
- In an embodiment, a tool for Maintenance Fee Portfolio Optimizer may look at variables that can be controlled for maintenance fee payment (e.g., a service provider, exchange rate, payment date) across a number of countries and makes recommendations for savings and the estimated amount of savings.
- In various embodiments, a User Interface for a Maintenance Fee Analyzer Site may be implemented. The site may: A) provides access to the Maintenance Fee database; B) User Interface Features may include: i. Look up any patent or application in database; ii. show user the annuity fee for that case; a. how user currency conversion based on two or more dates that currency would be purchased; —within a range, say default 6 months prior to payment date, show highest and lowest currency conversion quotes; b. allow user to specify “pricing date” used to price the currency conversion; iii. show user if agent fee is required; iv. show user typical annuity provider fees; v. allow user to price out a cost to pay fee; vi. Allow user to configure annuity provider charge profile—a) amount of provider fee; b) amount of currency mark-up; c) use reasonable agent fee (or none); d) estimate cost of payment, based on today's currency conversion rates; C) Allow user to “find family” for any given case they are looking at and show the family; a) a) provide maintenance fee estimates for those cases; b) b) estimate total cost of family.
- In an embodiment, a tool for Credit-based Annuity Payment Processing is implemented. The features may include: a) In annuity payment system, credit score may be deemed important to getting paid; b) score the credit risk for all annuity payments made in the patent management system; c) credit scores based on owners would be pulled into system; d) credit risk may be judged by prior history of paying PTO fees or WIPO cases—abandonment of these cases would indicate poor credit; e) Using score, the tool may adjust pricing and/or flag high risk payments; f) the tool may help implement the purchase of credit-insurance for each risky payment, from an outside funding source; g) Secondarily, the tool may offer credit option for some customers based on risk, but finance the credit option with an outside funding source; h) Credit risky owners may be flagged and correlate to patent holdings, so patent purchasing agents and trolls could see who was in need of financing.
- In various embodiments, a tool is used for an international patent registry architecture. The architecture may be implemented in a variety of ways such as: 1. For each country, there is a maintenance fee registry or database that is synchronized with, mirrored or is actual integrated with a country's equivalent of a PAIR/maintenance fee system. a. In one embodiment, this registry or database simply reflects the actual due dates kept on the PAIR system—i.e, the registry database does not calculate due dates, but simply reflects the due dates presented by the PAIR system. b. Similarly, the registry database also simply reflects the amounts due showing on the PAIR system, as opposed to keeping a separate database of them. 2. This registry could be one computer system/database that spans all the patent offices it serves, or be split. 3. There may be no docket maintained separate from the PAIR system—so the tool helps to eliminate the possibility of errors of keeping docket dates. (note, most if not all docket systems keep due dates for annuity payments based on a set of docket rules, not based on what is in PAIR itself) 4. Separately from the Registry database, there may be a database that keeps track of patents/apps owned by a particular company (e.g., an external database that may also keep track of due dates for annuities, separately from the PAIR system). 5. This external system may talk to the Registry database, and register with the Registry database to have the Registry make a payment on a particular patent a. the tool may allow various heterogeneous (e.g, systems from different vendors like) docket or matter management systems to register with it to pay annuities. This may be different than current architecture in that some of the patent maintenance payment providers pay only fees for customers they handle, and only pay through their own database systems. In the offered architecture, there may be a payment engine/registry that can be shared by all the vendors or patent owners to make sure payments are made on patents they tag in the database, and also various extra features can be effected through this architecture. As these registries grow to represent more and more patent offices, the principle function of annuity payment providers today may shift to simply tracking what patents a particular company owns, with the dates/costs/payment pipelines being provided by the registry.
- In an embodiment, a direct pay conduit tool is used for the registry:
- a. The Registry may provide a verifiable direct payment conduit.
- b. I.e., a corporation could provide an account/letter of credit/other payment facility, that can be drawn down by patent office authority, and such that only patents registered for payment through the Registry can be paid using the payment facility.
- 6. Payment authorization options:
- a. In one architecture, Registry provides the payment information to the docketing/Matter management vendor (such as CPI/CPA), and that vendor get approval from the Owner to pay the fees
- b. Docketing/Matter management Vendor authorizes Registry to draw down on Owner's payment facility.
- c. Registry verifies with Owner that it is ok to drawn down on the total $$, with an itemized report of what they plan on paying if desired. Owner can verify electronically, or Registry can get paper or voice approval
- d. Authorization keys are provided to run system.
- 7. Themes of the architecture may be:
- a. Distributed—
- i. For any given owner, the tracking of ownership of patents done in one system.
- 1. routine docketing done in this system, but
- 2. maintenance fee docket dates are extracted from a different system.
- ii. the amounts due and dates due for annuities/maintenance fees kept in another system—the patent registry.
- b. Payment pipeline is different—
- i. Instead of patent owners paying the docket/matter management system vendor for payment of annuities, annuities are paid through the Patent Registry.
- ii. Payments are made to the registry entity, electronically orchestrated or tracked by registry.
- iii. System vendor does not touch money paid to PTO, that money is routed through registry system or entity
- iv. System vendor gets paid for tracking ownership of patents and registering for payment, but not for paying fee itself.
- v. Payment could be made by patent owner directly to PTO through conduit provided by Registry
- vi. Registry may provide an electronic exchange to pay annuities in any currency, either directly into PTO system or through a banking/financial system
- In an embodiment, a tool is implemented as a Patent Office Payment Registry. Some annuity payment services may rely on keeping a proprietary database of patent information, where the annuity payment service has a client, and the client tells the annuity payment service which patent matters (patents or applications outside US) that the client wants the annuity payment service to handle for the purpose of annuity payment. As such, various different Annuity payment services may keep track of various different clients to handle payments for those clients and their matters. The tool change this paradigm. In the new paradigm, the tool may provide a single payment registry, where there is just one representation of each matter in any particular patent office like the USPTO and all the issued patents.) Customers of the registries are the patent owners or their agents.
- In an embodiment, the tool functions as follows: 1. Customers of the patent registry become registered users with the registry site. 2. Registered users can tag any patent as a patent they want paid. Tagging can take place in a variety of ways: a. Pick a patent one at a time; b. Upload a list of patents; c. Search for patents that the owner is record owner of; 3. Registered users can specify payment options: a. Always pay; b. Pay only if instructed to pay; c. Pay under certain other circumstances. 4. Registered users can specify different funding mechanisms: a. Paypal; b. Credit card; c. Bank account; d. Back up payment methods; e. Apply for credit. 5. Registered users can request “forward contract” pricing for payment of fees in other currencies. 6. Registered users can get quotes for currency conversion rates on a real time basis. 7. System provides various features: a. Cost projections; b. Analytics; c. Claim maps; d. Title verification. 8. Database is secure, and all tagging can be encrypted. 9. Users can be notified if: a. Someone else tags the same patent; b. They seek to remove a tag before another entity adds one; c. A payment was not made; d. Various other situations. 10. Users can pay for “track me” feature that collects back up contact information and follows the registered user to make sure they are available to authorize payments. 11. Users can pre-pay fees, held in escrow, to make sure payments are made. 12. Patent families can be registered at one time, both US families or international families. In an embodiment, pricing for annuity payment is dynamically quoted during payment authorization process. And price locked with order to pay annuity. Card is charged later on due date or date before that.
- In various embodiments, a tool is used to help eliminate the mark up for currency conversion. For example a payment infrastructure may be used that can support a more economical way to price/convert currency using forward contracts. Generally, the price of a forward contract is the cost of the currency on the day the contract is purchased, plus the cost of interest to hold the currency till it is delivered. This could be as little as 1% in interest cost, as compared to 6% to 20% mark up. The tool may work as follows: 1) track annuity payments due for an owner like a large European company with payments in US. 2) the tool may have a docket of due date for each patent. 3) at a specified date in advance of the due date, for example 3 or 6 months, the tool prices out how much it would cost to buy a forward contract of currency equal to the total amount of fees due on all patents being tracked that are coming due on that particular date, or due within a date range, like all fees due in a calendar month. In an alternate embodiment this can be done for one patent at a time. The cost of the forward contract is then apportioned to all the patents pro-rata based on the actual annuity fee, for the purpose of showing how much it will cost to pay each maintenance fee. The tool may provide the pricing infrastructure to support this transaction.
- In an embodiment: 1) a European company (EC) may sign up to use the tool and; 2) the tool synchronizes/receives tracking data from the EC's annuity payment service (e.g., Computer Patent Annuities); 3) on a specified day in advance of when a batch of payments are due in the USPTO, the tool prices a forward contract for that batch of patents using forward contract rates we get from a participating bank; 4) the price of the currency is provided to annuity payment company (APC), which in turn uses it to send upcoming payment reports to it's EC with a list of annuities due and an amount for each; 5) EC instructs APC to make payments in US; 6) APC notifies system/bank on how much to send to USPTO to cover cost of payment for list of annuities to be paid; 7) bank wire transfers money to uspto account—this could be automated. In this model, EC pays bank directly for cost of annuities. Or, APC could pay bank and APC collect from annuity provider.
- In an embodiment, a tool is used that uses claim tracking data for annuity management. By using detailed rejection data or composite claims the tool can gauge how close a patent is to prior art. For example the tool might see exactly what was added to claims to gain allowance.
- In an embodiment, an annuity site reports on maintenance fees not paid and sets alerts for nonpayment. Alerts may be carry over when ownership changes.
- In an embodiment, a tool is used for prosecution history to help make annuity decision or as rating metric. To determine value of claims, the tool may look at number of novelty or other rejections in US prosecution or in PCT or EPO search reports.
- In an embodiment, a tool is used so that any payment agent could quote a forward contract amount for any patent, and owner can commit to using the forward payment in advance of forward date and the tool will track it all. Each user could either have a default forward date or pick a specific date dynamically on the day of before it. The interface may be integrated into the PTO payment system.
- In various embodiments, a maintenance fee payments tool may be used. The tool may be implemented as a website and the site may show maintenance fees due for US and foreign and due dates. Users may follow certain matters and receive free cost projections. Users can get free quotes for payment from vendors. The site may use US and Inpadoc and other data. A User can get quote for owner-based group/portfolio. Users can view payment status and look up on app. The site may also feature “follow me” feature and other options to assure notice of fee due or payment of fee. Site may feature fee schedules for annuities for all countries and docket could show recovery options for lapsed patents due to nonpayment. The site may give fees for each case, due date, term remaining, sales of similar technology products, enforcement information. It may also shows family data, cost projections, measures of value. It may also mark patents that are in litigation and mark patents in the orange book.
- In an embodiment, a tool is implanted as a web site hosted by a payment agent. The payment web site may be linked/integrated with USPTO payment interfaces and feature:
- 1. User identifies patents they want maintenance fees paid for
- a. these patents would have payments due at various times
- 2. User provides a credit card to use to pay the maintenance fees
- 3. Payment web site pre-authorizes card for upcoming weeks/months payments
- a. any issues, it notifies owner of card there is an issue
- 4. Payment web site uses card to go online at USPTO and execute payment for Patent Owner
- 5. Later, payment web site downloads AMEX/Visa transactions from web site (and other transaction data from AMEX/Visa) and reconciles payments automatically (or semi-automatically)
- Payment Interface:
- 1. Can be integrated with Annuity docket date system, and take information from annuity.
- Market Analysis
- In an embodiment, a tool is used for white space indicators for Analytics. This may indicate when an invention/patent is in a crowded space or is in a “white space”. The concept is to give the User an idea of which areas they are working in are most fertile. Also, it may help create a strategy for filing. Potential ways to indicate include: 1. For the class/subclass of the invention, how many patents are in the class/subclass (fewer is less crowded); 2. For the class/subclass, how old is the earliest patent in the class/subclass (newer is less crowded); 3. How old is the applied prior art cited against the patent? How old is unapplied art cited?; 4. What is the distribution of age of patents cited as prior art in the class/subclass (newer is less crowded); 5. Using keywords, determine how many patents each competitor has, or how many patents there are, in key technology areas; 6. Specific design: a) User creates a “Technology” to be added to a Technology list; b) For a Technology, user can do one or more of the following: i. Specify Representative Patents or Applications; ii. Specify Representative Keywords; iii. Specify Representative Classes/Subclasses; c) System uses one or more of these to calculate a parameter or graph showing if the Technology area is crowded or has white space; 7. 2nd Specific design: a) For any given patent or patent application, system uses keywords from the patent/application/claims and the classes/subclasses and other parameters like prior art, to determine if patent is crowded or open Technology area.
- User Interfaces
- In various embodiments, for the tools discussed herein a user interface may be used to determine which services a user may elect. For example: 1) User loads list of US patent/app cases into Portfolio manager, 2) each patent/app may have the following button options: a) sign up/select option to find foreign equivalents or US family, and load if desired. A-1) sign up for title guard—a tool monitors title changes, b) sign up for maintenance fee payment alerts—a tool monitors for either payments due and/or send an alert if payment not made, c) a tool offers to make payment if one is due—this is done with multiple payment options; d) sign up for basic citation alerts—any forward cite, e) sign up for advanced citation alert—a tool looks at forward citations of related patents like citation of an applied or unapplied prior art reference, or a forward cite of a forward cited patent, or a forward cite of a sibling patent, e-1) sign up for PTO Pair alerts, e-2) sign up to look for cites to the patent in pending apps, f) sign up for advanced metrics—a package of advanced analytics metrics, g) sign up for Internet watch for patent—set parameters to generate web hits that are related to patent, h) sign up for troll/patent trading activity alert—a tool detects how many patents in the same class/subclass or in other related group have changed owners in a time period.
- Strategic Monitoring
- In various embodiments, a tool is used to track ownership changes. This tool may be implemented as is a web site that shows daily list of changes in patent owners; assignments to newly formed companies; assignments to LLC's; assignments to corporations; assignments between existing companies; assignment of patents/applications older than a certain age; assignments that are anticipated could be filtered out, like: assignments of new patent applications to an existing patent holder; show interesting new assignments that may be suspicious; and assignments could be filtered by technology type/class/subclass.
- In an embodiment, a tool is used for patent activity profiling. The tool may include the following features; a) build a patenting profile for a particular applicant/owner, or a type of owner, and then flag deviances from that profile; b) the profile may include foreign filing patterns, US filing patterns (e.g., does the owner typically file provisional first, then PCT, or PCT, US, etc. . . . , abandonments—e.g., what are they giving up on?; c) Show deviances from the profile, send out notifications; d) display filing profile for others to look at; e) this data would be assembled from public data.
- In an embodiment, a tool is used to watch a competitor's prosecution. The tool may allow a user to set up an account on a web server/asp system that can pull in public PAIR files; Pick cases one at a time to add; Load cases for entire portfolio for owner and remove as desired; Specify owner, and have system automatically add new cases for owner; Automatically add related cases that are filed; Keep a list of suggested new cases to add based on: Locations of inventors; Patent counsel named on case; Class/subclass; Keywords; Cited art—i.e., if the case cites a patent from the user's company; PCT filings or other national stage claiming priority; Notify owner of account each time new suggested cases are added; Owner can keep or dismiss suggested accounts to watch; With respect to any PAIR file, user can: get notified each time there is a change; Get notified if case goes abandoned; If there is an office action; If prior art is filed.
- In an embodiment, every time a US patent issues, or app publishes, a fan page is automatically set up on Facebook/social network. A tool may then search for owners of patent on Facebook/linkedin, and invite them to become a fan. An app on the Fan page can quote fees for payment of annuities or other services. Patent or app status may be updated from public data. Updates could be forward cites of patent. Updates could be allowance, grant, rejection. Updates could be payment of maintenance fees.
- In an embodiment, a tool may look at abandonment for competitor patents in same area respecting any particular maintenance fee decision. This may also be determined by: Class/subclass; Standard Industry Codes correlated to patents; Keywords; Semantic analysis.
- In an embodiment, a tool is used for finding relevant web hits for watching patents. For a given watched patent the system may:
- a. Keep a list of forward-cites
- b. From the list of forward-cites, identify all the IP owners of the forward cites
- c. Send watch notice each time new material is posted to the web site of an IP Owner that is relevant to the patent, based for example on keywords or a class/subclass concordance
- d. Do the above for owners of the cited prior art.
- In an embodiment, a tool is used for protect ownership of a patent and keep a patent in force, The tool may be implemented as website and include features of:
- 1. User goes to web site
- 2. User can pick any US (or where possible) any foreign patent/application. User can choose any one of the following automated protections
- a. No assignment filed monitor:
- i. Automatically check and report if no Assignment is filed for application within a given time frame
- b. Assignment changed monitor:
- i. Automatically check and report if Assignment is changed
- c. Patent fee not paid—
- i. automatically notify user if fee not paid
- ii. kick in revival process if fee not paid
- 1. process might be notifying one or more law firms
- 2. process might include notifying agent for user
- d.
- “Troll Monitor/Metric
- Owner Change Metric
- This concept is to:
- 1. For any given patent/application
- a. provide a rating/metric that indicates if ownership of related patents is changing
- i. at a frequency above normal
- ii. if there are any changes at all
- iii. for prior art patents
- iv. for forward cited patents
- v. for patents in class/subclass, as compared to other classes/subclasses
- b. using a list of known trolls, or suspected trolls
- i. determine level of troll activity in an area
- ii. report level of activity
- iii. use as metric to determine potential value of patent
- In an embodiment, a tool is used to determine the what classes/technologies a company has the best position in (e.g. By percent of class or subclass or by number of total cites). The tool may determine most open areas for a company based on existing filings—which areas show the most promise for patenting based on number of patents, timeline for class—e.g., how close to beginning of filings in the area.
-
FIGS. 5-8 illustrateexample methods - In one example embodiment, the processing logic resides at the
analytics module 218, illustrated inFIG. 2 . Some portions of the methods may be performed by the various example modules discussed above with reference toFIG. 2 . Each of these modules may comprise processing logic. - As shown in
FIG. 5 , themethod 500 commences atoperation 502, maintaining or accessing a database including data relating to patent maintenance fees and due dates; at 504, presenting an interactive interface to a user, the interface including a display of a maintenance fee and a due date for at least one patent in the database; at 506, allowing, in the interactive interface, the user to request a maintenance-fee cost projection for a selected group or portfolio of patents in the database; at 508, providing, in the interactive interface, a notification selection element allowing a user to request notification of maintenance fee payments coming due; at 510, receiving maintenance fee payment instructions from the user via the interactive interface; and at 512, presenting a maintenance payment status to the user in the interactive interface. - As shown in
FIG. 6 , themethod 600 commences atoperation 602, maintaining or accessing a database including patent-related data; at 604, presenting an interactive interface to a user, the interface including a display, for at least one patent in the database included in a technology class or sub-class, of one or more of the following elements: a maintenance fee; a maintenance fee due date; a remaining patent term; sales of at least one product having technology related to the class or sub-class; patent enforcement information; patent family data; maintenance fee cost projections; at least one measure of patent value; a patent litigation status; a claim analyzer; and atoperation 606, receiving, via the interactive interface, from the user, instructions to pay the maintenance fee for the at least one patent in the database. - As shown in
FIG. 7 , themethod 700 commences atoperation 702, maintaining or accessing a database including data relating to patent families; atoperation 704, analyzing at least one patent family in the database to identify patent continuation and divisional cases in the family; atoperation 706, identifying any method claims in the at least one patent family; atoperation 708, presenting any identified continuation, divisional or method claims to a user in an interactive interface; and atoperation 710, receiving, via the interactive interface, instructions to renew at least one patent in the patent family. - As shown in
FIG. 8 , themethod 800 commences atoperation 802, monitoring at least one patent requiring annuity payments to remain in force; atoperation 804, maintaining a database including contact details for an owner of the patent, the contact details including at least one or more of the following elements: owner name, employer details, physical address, postal address, email address, text message address, mobile number, land line number, social security number; atoperation 806, including in the database details for at least one back-up contact for the patent owner, the back-up contact details including, for each back up, at least one or more of the following elements: back up name, postal address, email address, text message address, mobile number, land line number, social security number; atoperation 808, using one or more of the patent owner contact details, automatically pinging the patent owner on a periodic basis and monitoring for receipt of a reply within a first predetermined time period; atoperation 810, flagging the absence of a reply being received within the first predetermined time period; and atoperation 812, automatically pinging at least one of the back-up contacts for a predetermined second time period, or until the patent owner is found. - Certain embodiments are described herein as including logic or a number of components, modules, or mechanisms. Modules may constitute either software modules (e.g., code embodied (1) on a non-transitory machine-readable medium or (2) in a transmission signal) or hardware-implemented modules. A hardware-implemented module is tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. In example embodiments, one or more computer systems (e.g., a standalone, client or server computer system) or one or more processors may be configured by software (e.g., an application or application portion) as a hardware-implemented module that operates to perform certain operations as described herein.
- In various embodiments, a hardware-implemented module may be implemented mechanically or electronically. For example, a hardware-implemented module may comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC)) to perform certain operations. A hardware-implemented module may also comprise programmable logic or circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. It will be appreciated that the decision to implement a hardware-implemented module mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.
- Accordingly, the term “hardware-implemented module” should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired) or temporarily or transitorily configured (e.g., programmed) to operate in a certain manner and/or to perform certain operations described herein. Considering embodiments in which hardware-implemented modules are temporarily configured (e.g., programmed), each of the hardware-implemented modules need not be configured or instantiated at any one instance in time. For example, where the hardware-implemented modules comprise a general-purpose processor configured using software, the general-purpose processor may be configured as respective different hardware-implemented modules at different times. Software may accordingly configure a processor, for example, to constitute a particular hardware-implemented module at one instance of time and to constitute a different hardware-implemented module at a different instance of time.
- Hardware-implemented modules can provide information to, and receive information from, other hardware-implemented modules. Accordingly, the described hardware-implemented modules may be regarded as being communicatively coupled. Where multiple of such hardware-implemented modules exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) that connect the hardware-implemented modules. In embodiments in which multiple hardware-implemented modules are configured or instantiated at different times, communications between such hardware-implemented modules may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware-implemented modules have access. For example, one hardware-implemented module may perform an operation, and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware-implemented module may then, at a later time, access the memory device to retrieve and process the stored output. Hardware-implemented modules may also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information).
- The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented modules that operate to perform one or more operations or functions. The modules referred to herein may, in some example embodiments, comprise processor-implemented modules.
- Similarly, the methods described herein may be at least partially processor-implemented. For example, at least some of the operations of a method may be performed by one or processors or processor-implemented modules. The performance of certain of the operations may be distributed among the one or more processors, not only residing within a single machine, but deployed across a number of machines. In some example embodiments, the processor or processors may be located in a single location (e.g., within a home environment, an office environment or as a server farm), while in other embodiments the processors may be distributed across a number of locations.
- The one or more processors may also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., Application Program Interfaces (APIs).)
- Example embodiments may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Example embodiments may be implemented using a computer program product, e.g., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable medium for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers.
- A computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, subroutine, or other unit suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.
- In example embodiments, operations may be performed by one or more programmable processors executing a computer program to perform functions by operating on input data and generating output. Method operations can also be performed by, and apparatus of example embodiments may be implemented as, special purpose logic circuitry, e.g., a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC).
- The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. In embodiments deploying a programmable computing system, it will be appreciated that that both hardware and software architectures require consideration. Specifically, it will be appreciated that the choice of whether to implement certain functionality in permanently configured hardware (e.g., an ASIC), in temporarily configured hardware (e.g., a combination of software and a programmable processor), or a combination of permanently and temporarily configured hardware may be a design choice. Below are set out hardware (e.g., machine) and software architectures that may be deployed, in various example embodiments.
-
FIG. 4 is a block diagram of machine in the example form of acomputer system 400 within which instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed. In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine may be a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein. - The
example computer system 400 includes a processor 402 (e.g., a central processing unit (CPU), a graphics processing unit (GPU) or both), amain memory 404 and astatic memory 406, which communicate with each other via a bus 408. Thecomputer system 400 may further include a video display unit 410 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)). Thecomputer system 400 also includes an alphanumeric input device 412 (e.g., a keyboard), a user interface (UI) navigation device 414 (e.g., a mouse), adisk drive unit 416, a signal generation device 418 (e.g., a speaker) and anetwork interface device 420. - The
disk drive unit 416 includes a machine-readable medium 422 on which is stored one or more sets of instructions and data structures (e.g., software) 424 embodying or utilized by any one or more of the methodologies or functions described herein. Theinstructions 424 may also reside, completely or at least partially, within themain memory 404 and/or within theprocessor 402 during execution thereof by thecomputer system 400, themain memory 404 and theprocessor 402 also constituting machine-readable media. - While the machine-
readable medium 422 is shown in an example embodiment to be a single medium, the term “machine-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more instructions or data structures. The term “machine-readable medium” shall also be taken to include any tangible medium that is capable of storing, encoding or carrying instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present invention, or that is capable of storing, encoding or carrying data structures utilized by or associated with such instructions. The term “machine-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media. Specific examples of machine-readable media include non-volatile memory, including by way of example semiconductor memory devices, e.g., Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. - The
instructions 424 may further be transmitted or received over acommunications network 426 using a transmission medium. Theinstructions 424 may be transmitted using thenetwork interface device 420 and any one of a number of well-known transfer protocols (e.g., HTTP). Examples of communication networks include a local area network (“LAN”), a wide area network (“WAN”), the Internet, mobile telephone networks, Plain Old Telephone (POTS) networks, and wireless data networks (e.g., WiFi and WiMax networks). The term “transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine, and includes digital or analog communications signals or other intangible media to facilitate communication of such software. - Although an embodiment has been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the invention. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof, show by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.
- Such embodiments of the inventive subject matter may be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description.
Claims (12)
1. A method comprising:
monitoring at least one patent requiring an annuity payment to remain in force;
maintaining a database including patent owner contact details for a patent owner of the at least one patent, the patent owner contact details including at least one of the following elements with respect to the patent owner: owner name, employer details, physical address, postal address, email address, text message address, mobile number, land line number, or social security number;
including in the database, back-up contact details for at least one back-up contact for the patent owner, the back-up contact details including at least one of the following elements with respect to the at least one back-up contact: name, postal address, email address, text message address, mobile number, land line number, or social security number;
using one or more of the patent owner contact details, automatically pinging the patent owner on a periodic basis by sending a communication via at least one of an e-mail, telephone call, or text message and monitoring for receipt of a reply to the communication within a first predetermined time period; and
in response to not receiving a reply to the communication from the patent owner within the first predetermined time period, using one or more of the back-up contact details of at least one back-up contact to automatically ping at least one of the back-up contacts by sending at least one of an e-mail, telephone call, or text message to the at least one back-up.
2. The method of claim 1 , further comprising communicating a reminder of the annuity payment to the patent owner via at least one social media site.
3. The method of claim 1 , further comprising communicating a reminder of the annuity payment to the patent owner via an application on a mobile device.
4. The method of claim 1 , further comprising:
identifying a lack of at least one of the elements of the patent owner contact details; and
using one or more of the back-up contact details of at least one back-up contact, automatically pinging at least one of the back-up contacts until the at least one of the elements of the patent owner contact details is identified.
5. A system comprising:
a database including database entries that include:
patent owner contact details for an owner of a patent, the patent owner contact details including at least one or more of the following elements: owner name, employer details, physical address, postal address, email address, text message address, mobile number, land line number, or social security number; and
back-up contact details for at least one back-up contact for the patent owner, the back-up contact details including at least one or more of the following elements: name, postal address, email address, text message address, mobile number, land line number, or social security number;
a storage device with computer-readable instructions stored thereon;
at least one processor, wherein when the instructions are executed by the at least one processor the at least on processor configured to:
monitor at least one patent requiring an annuity payment to remain in force;
use one or more of the patent owner contact details, to automatically ping the patent owner on a periodic basis by sending a communication via at least one of an e-mail, telephone call, or text message and monitor for receipt of a reply of the communication within a first predetermined time period; and
in response to not receiving a reply to the communication from the patent owner within the first predetermined time period, use one or more of the back-up contact details of at least one back-up contact to automatically ping at least one of the back-up contacts by sending at least one of an e-mail, telephone call, or text message to the at least one back-up.
6. The system of claim 5 , wherein the at least one processor is further configured, when executing the instructions to:
communicate a reminder of the annuity payment to the patent owner via at least one social media site.
7. The system of claim 5 , wherein the at least one processor is further configured, when executing the instructions to:
communicate a reminder of the annuity payment to the patent owner via an application on a mobile device.
8. The system of claim 5 , wherein the at least one processor is further configured, when executing the instructions to:
identify a lack of at least one of the elements of the patent owner contact details; and
use one or more of the back-up contact details of at least one back-up contact, to automatically ping at least one of the back-up contacts until the at least one of the elements of the patent owner contact details is identified.
9. A non-transitory machine-readable medium, including instructions, which when executed by at least one processor, causing the at least one processor to perform the operations of:
monitoring at least one patent requiring an annuity payment to remain in force;
maintaining a database including patent owner contact details for a patent owner of the at least one patent, the patent owner contact details including at least one of the following elements with respect to the patent owner: owner name, employer details, physical address, postal address, email address, text message address, mobile number, land line number, or social security number;
including in the database, back-up contact details for at least one back-up contact for the patent owner, the back-up contact details including at least one of the following elements with respect to the at least one back-up contact: name, postal address, email address, text message address, mobile number, land line number, or social security number;
using one or more of the patent owner contact details, automatically pinging the patent owner on a periodic basis by sending a communication via at least one of an e-mail, telephone call, or text message and monitoring for receipt of a reply of the communication within a first predetermined time period; and
in response to not receiving a reply to the communication from the patent owner within the first predetermined time period, using one or more of the back-up contact details of at least one back-up contact to automatically ping at least one of the back-up contacts by sending at least one of an e-mail, telephone call, or text message to the at least one back-up.
10. The machine-readable medium of claim 9 , further comprising communicating a reminder of the annuity payment to the patent owner via at least one social media site.
11. The machine-readable medium of claim 9 , further comprising communicating a reminder of the annuity payment to the patent owner via an application on a mobile device.
12. The machine-readable medium of claim 9 , further comprising:
identifying a lack of at least one of the elements of the patent owner contact details; and
using one or more of the back-up contact details of at least one back-up contact, automatically pinging at least one of the back-up contacts until the at least one of the elements of the patent owner contact details is identified.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/483,903 US20140379388A1 (en) | 2011-10-03 | 2014-09-11 | Systems and methods for patent portfolio management |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201161542515P | 2011-10-03 | 2011-10-03 | |
US13/573,804 US20130282409A1 (en) | 2011-10-03 | 2012-10-03 | Systems and methods for patent portfolio management |
US14/483,903 US20140379388A1 (en) | 2011-10-03 | 2014-09-11 | Systems and methods for patent portfolio management |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/573,804 Division US20130282409A1 (en) | 2011-10-03 | 2012-10-03 | Systems and methods for patent portfolio management |
Publications (1)
Publication Number | Publication Date |
---|---|
US20140379388A1 true US20140379388A1 (en) | 2014-12-25 |
Family
ID=47993599
Family Applications (17)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/253,825 Active US8972385B2 (en) | 2011-10-03 | 2011-10-05 | System and method for tracking patent ownership change |
US13/253,931 Abandoned US20130086080A1 (en) | 2011-10-03 | 2011-10-05 | System and method for information disclosure statement management and prior art cross-citation control |
US13/253,846 Abandoned US20130086044A1 (en) | 2011-10-03 | 2011-10-05 | System and method for patent activity profiling |
US13/253,936 Active US10860657B2 (en) | 2011-10-03 | 2011-10-05 | Patent mapping |
US13/253,941 Abandoned US20130086070A1 (en) | 2011-10-03 | 2011-10-05 | Prior art management |
US13/253,801 Active US8892547B2 (en) | 2011-10-03 | 2011-10-05 | System and method for prior art analysis |
US13/253,811 Abandoned US20130086042A1 (en) | 2011-10-03 | 2011-10-05 | System and method for information disclosure statement management and prior art cross-citation control |
US13/275,707 Active US9201966B2 (en) | 2011-10-03 | 2011-10-18 | System and method for prior art analytics and mapping |
US14/483,903 Abandoned US20140379388A1 (en) | 2011-10-03 | 2014-09-11 | Systems and methods for patent portfolio management |
US14/540,346 Active US9396274B2 (en) | 2011-10-03 | 2014-11-13 | System and method for prior art analysis |
US14/608,520 Abandoned US20150149368A1 (en) | 2011-10-03 | 2015-01-29 | System and method for tracking patent ownership change |
US14/628,941 Abandoned US20150169777A1 (en) | 2011-10-03 | 2015-02-23 | System and method for tracking patent ownership change |
US14/826,006 Abandoned US20150347604A1 (en) | 2011-10-03 | 2015-08-13 | System and method for information disclosure statement management and prior art cross-citation control |
US14/952,699 Active US9652546B2 (en) | 2011-10-03 | 2015-11-25 | System and method for prior art analytics and mapping |
US15/211,917 Abandoned US20170075929A1 (en) | 2011-10-03 | 2016-07-15 | System and method for prior art analysis |
US15/595,629 Active 2032-07-28 US10671574B2 (en) | 2011-10-03 | 2017-05-15 | System and method for prior art analytics and mapping |
US17/103,870 Pending US20210149969A1 (en) | 2011-10-03 | 2020-11-24 | Patent mapping |
Family Applications Before (8)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/253,825 Active US8972385B2 (en) | 2011-10-03 | 2011-10-05 | System and method for tracking patent ownership change |
US13/253,931 Abandoned US20130086080A1 (en) | 2011-10-03 | 2011-10-05 | System and method for information disclosure statement management and prior art cross-citation control |
US13/253,846 Abandoned US20130086044A1 (en) | 2011-10-03 | 2011-10-05 | System and method for patent activity profiling |
US13/253,936 Active US10860657B2 (en) | 2011-10-03 | 2011-10-05 | Patent mapping |
US13/253,941 Abandoned US20130086070A1 (en) | 2011-10-03 | 2011-10-05 | Prior art management |
US13/253,801 Active US8892547B2 (en) | 2011-10-03 | 2011-10-05 | System and method for prior art analysis |
US13/253,811 Abandoned US20130086042A1 (en) | 2011-10-03 | 2011-10-05 | System and method for information disclosure statement management and prior art cross-citation control |
US13/275,707 Active US9201966B2 (en) | 2011-10-03 | 2011-10-18 | System and method for prior art analytics and mapping |
Family Applications After (8)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/540,346 Active US9396274B2 (en) | 2011-10-03 | 2014-11-13 | System and method for prior art analysis |
US14/608,520 Abandoned US20150149368A1 (en) | 2011-10-03 | 2015-01-29 | System and method for tracking patent ownership change |
US14/628,941 Abandoned US20150169777A1 (en) | 2011-10-03 | 2015-02-23 | System and method for tracking patent ownership change |
US14/826,006 Abandoned US20150347604A1 (en) | 2011-10-03 | 2015-08-13 | System and method for information disclosure statement management and prior art cross-citation control |
US14/952,699 Active US9652546B2 (en) | 2011-10-03 | 2015-11-25 | System and method for prior art analytics and mapping |
US15/211,917 Abandoned US20170075929A1 (en) | 2011-10-03 | 2016-07-15 | System and method for prior art analysis |
US15/595,629 Active 2032-07-28 US10671574B2 (en) | 2011-10-03 | 2017-05-15 | System and method for prior art analytics and mapping |
US17/103,870 Pending US20210149969A1 (en) | 2011-10-03 | 2020-11-24 | Patent mapping |
Country Status (1)
Country | Link |
---|---|
US (17) | US8972385B2 (en) |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9286351B2 (en) | 2011-10-03 | 2016-03-15 | Black Hills Ip Holdings, Llc | System and method for patent and prior art analysis |
US9396274B2 (en) | 2011-10-03 | 2016-07-19 | Black Hills Ip Holdings, Llc | System and method for prior art analysis |
US9659071B2 (en) | 2005-07-27 | 2017-05-23 | Schwegman Lundberg & Woessner, P.A. | Patent mapping |
US9911094B1 (en) * | 2017-05-11 | 2018-03-06 | International Business Machines Corporation | Intelligent key performance indicator catalog |
WO2018136747A1 (en) * | 2017-01-23 | 2018-07-26 | Tete-A-Tete, Inc. | Systems, apparatuses, and methods for extracting inventory from unstructured electronic messages |
US10546273B2 (en) | 2008-10-23 | 2020-01-28 | Black Hills Ip Holdings, Llc | Patent mapping |
US10832224B2 (en) * | 2015-05-06 | 2020-11-10 | Vmware, Inc. | Calendar based management of information technology (IT) tasks |
US11080807B2 (en) | 2004-08-10 | 2021-08-03 | Lucid Patent Llc | Patent mapping |
US20230047250A1 (en) * | 2021-08-13 | 2023-02-16 | Black Hills Ip Holdings, Llc | Document splitting tool |
US11714839B2 (en) | 2011-05-04 | 2023-08-01 | Black Hills Ip Holdings, Llc | Apparatus and method for automated and assisted patent claim mapping and expense planning |
US11798111B2 (en) | 2005-05-27 | 2023-10-24 | Black Hills Ip Holdings, Llc | Method and apparatus for cross-referencing important IP relationships |
Families Citing this family (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080216013A1 (en) * | 2006-08-01 | 2008-09-04 | Lundberg Steven W | Patent tracking |
US9799040B2 (en) * | 2012-03-27 | 2017-10-24 | Iprova Sarl | Method and apparatus for computer assisted innovation |
US9542449B2 (en) | 2012-04-09 | 2017-01-10 | Search For Yeti, LLC | Collaboration and analysis system for disparate information sources |
US11461862B2 (en) | 2012-08-20 | 2022-10-04 | Black Hills Ip Holdings, Llc | Analytics generation for patent portfolio management |
US20140279583A1 (en) * | 2013-03-14 | 2014-09-18 | Lex Machina, Inc. | Systems and Methods for Classifying Entities |
US9767190B2 (en) | 2013-04-23 | 2017-09-19 | Black Hills Ip Holdings, Llc | Patent claim scope evaluator |
US9916383B1 (en) | 2013-07-12 | 2018-03-13 | Aplix Research, Inc. | Systems and methods for document analytics |
US20150046443A1 (en) * | 2013-08-11 | 2015-02-12 | International Business Machines Corporation | Document-based search with facet information |
CA2953776A1 (en) * | 2014-07-01 | 2016-01-07 | Piazza Technologies, Inc. | Computer systems and user interfaces for learning, talent discovery, relationship management, and campaign development |
US11429609B2 (en) * | 2015-04-15 | 2022-08-30 | Microsoft Technology Licensing, Llc | Geo-scale analytics with bandwidth and regulatory constraints |
TWI584217B (en) * | 2015-08-24 | 2017-05-21 | 雲拓科技有限公司 | A verification method of patent searching analysis result |
US10832360B2 (en) * | 2015-10-20 | 2020-11-10 | International Business Machines Corporation | Value scorer in an automated disclosure assessment system |
EP3211573A1 (en) * | 2016-02-23 | 2017-08-30 | Tata Consultancy Services Limited | Systems and methods for generating strategic competitive intelligence data relevant for an entity |
CN105843866A (en) * | 2016-03-17 | 2016-08-10 | 畅捷通信息技术股份有限公司 | Data searching method and system based on cloud searching platform |
US9607058B1 (en) | 2016-05-20 | 2017-03-28 | BlackBox IP Corporation | Systems and methods for managing documents associated with one or more patent applications |
CN107463565B (en) * | 2016-06-02 | 2020-05-15 | 索意互动(北京)信息技术有限公司 | Document data processing, searching and analyzing method and corresponding device |
CN106227755A (en) * | 2016-07-14 | 2016-12-14 | 上海超橙科技有限公司 | Patent statute monitoring system and method |
US10606821B1 (en) | 2016-08-23 | 2020-03-31 | Microsoft Technology Licensing, Llc | Applicant tracking system integration |
US20180189909A1 (en) * | 2016-12-30 | 2018-07-05 | At&T Intellectual Property I, L.P. | Patentability search and analysis |
KR20180107707A (en) | 2017-03-22 | 2018-10-02 | (주)광개토연구소 | Mapping Device and Method on between Patent Drawings Including Figure Numbers and Descriptions of the Figure Numbers Using Machine Learning Methodology Based on Using Artificial Intelligence Technology |
CN108595703A (en) * | 2018-05-09 | 2018-09-28 | 深圳市华慧品牌管理有限公司 | The Chinese priority data library method for building up and device of foreign patent application |
CN108764363A (en) * | 2018-06-05 | 2018-11-06 | 河北工程大学 | A kind of patented technology Life Cycle Analysis |
WO2020012116A1 (en) | 2018-07-09 | 2020-01-16 | Arkyan | Method, device and information medium for estimating the chances and/or probable date of granting a patent application |
US11226996B2 (en) | 2018-08-03 | 2022-01-18 | Kilpatrick Townsend & Stockton Llp | Identifying and graphically representing multiple parent nodes of a child node |
US11222050B2 (en) * | 2018-08-03 | 2022-01-11 | Kilpatrick Townsend & Stockton Llp | Graphically representing related patent families using a phantom parent node |
US11392627B2 (en) | 2018-08-03 | 2022-07-19 | Kilpatrick Townsend & Stockton Llp | Identifying missing nodes within a graphically represented family |
FI20185865A1 (en) * | 2018-10-13 | 2020-04-14 | Iprally Tech Oy | Method of training a natural language search system, search system and corresponding use |
EP3871073A4 (en) * | 2018-10-23 | 2022-07-20 | Yext, Inc. | Knowledge search system |
US11132412B1 (en) * | 2020-03-31 | 2021-09-28 | Black Hills Ip Holdings, Llc | User interface for providing docketing data |
US20220084089A1 (en) * | 2020-08-05 | 2022-03-17 | Erich Lawson Spangenberg | System and method for information disclosure statements for patent pooling aggregation |
US11822561B1 (en) | 2020-09-08 | 2023-11-21 | Ipcapital Group, Inc | System and method for optimizing evidence of use analyses |
CN113704600A (en) * | 2021-06-18 | 2021-11-26 | 诺正集团股份有限公司 | Information processing method, device and equipment based on data interaction and storage medium |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20010007977A1 (en) * | 2000-01-06 | 2001-07-12 | Geary Stuart Lloyd | Reminder and actioning system |
US20110099084A1 (en) * | 2009-04-20 | 2011-04-28 | Mpeg La L.L.C. | Systems and methods for managing patent licenses |
Family Cites Families (272)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2156112A (en) | 1984-03-20 | 1985-10-02 | Brian Ledwith | Data processing system and method |
US5404506A (en) | 1985-03-27 | 1995-04-04 | Hitachi, Ltd. | Knowledge based information retrieval system |
US5696916A (en) | 1985-03-27 | 1997-12-09 | Hitachi, Ltd. | Information storage and retrieval system and display method therefor |
JPS61220027A (en) | 1985-03-27 | 1986-09-30 | Hitachi Ltd | Information memory system |
US5553226A (en) | 1985-03-27 | 1996-09-03 | Hitachi, Ltd. | System for displaying concept networks |
US6182062B1 (en) | 1986-03-26 | 2001-01-30 | Hitachi, Ltd. | Knowledge based information retrieval system |
US4807154A (en) | 1987-01-29 | 1989-02-21 | International Business Machines Corporation | Method for developing automatic replies in an interactive electronic calendaring system |
US5557515A (en) | 1989-08-11 | 1996-09-17 | Hartford Fire Insurance Company, Inc. | Computerized system and method for work management |
JP2943447B2 (en) | 1991-01-30 | 1999-08-30 | 三菱電機株式会社 | Text information extraction device, text similarity matching device, text search system, text information extraction method, text similarity matching method, and question analysis device |
JPH05303531A (en) | 1991-01-31 | 1993-11-16 | Fields Software Group Inc | Electronic system and method for processing format |
US5592664A (en) | 1991-07-29 | 1997-01-07 | Borland International Inc. | Database server system with methods for alerting clients of occurrence of database server events of interest to the clients |
GB2260007A (en) | 1991-09-20 | 1993-03-31 | Hitachi Ltd | Information storage/retrieval system and display method |
US5329447A (en) | 1992-03-12 | 1994-07-12 | Leedom Jr Charles M | High integrity computer implemented docketing system |
JPH06176081A (en) | 1992-12-02 | 1994-06-24 | Hitachi Ltd | Hierarchical structure browsing method and device |
US5799325A (en) | 1993-11-19 | 1998-08-25 | Smartpatents, Inc. | System, method, and computer program product for generating equivalent text files |
US6963920B1 (en) * | 1993-11-19 | 2005-11-08 | Rose Blush Software Llc | Intellectual asset protocol for defining data exchange rules and formats for universal intellectual asset documents, and systems, methods, and computer program products related to same |
US5623681A (en) | 1993-11-19 | 1997-04-22 | Waverley Holdings, Inc. | Method and apparatus for synchronizing, displaying and manipulating text and image documents |
US6339767B1 (en) | 1997-06-02 | 2002-01-15 | Aurigin Systems, Inc. | Using hyperbolic trees to visualize data generated by patent-centric and group-oriented data processing |
US5623679A (en) | 1993-11-19 | 1997-04-22 | Waverley Holdings, Inc. | System and method for creating and manipulating notes each containing multiple sub-notes, and linking the sub-notes to portions of data objects |
US5548506A (en) | 1994-03-17 | 1996-08-20 | Srinivasan; Seshan R. | Automated, electronic network based, project management server system, for managing multiple work-groups |
US5745745A (en) | 1994-06-29 | 1998-04-28 | Hitachi, Ltd. | Text search method and apparatus for structured documents |
US5548753A (en) | 1994-09-14 | 1996-08-20 | Johnson Service Company | Automatic electronic mail notification of database events |
US5664063A (en) | 1994-12-01 | 1997-09-02 | International Business Machines Corporation | Automatic user notification of certain meeting attributes of a posted calendar event |
US5530852A (en) | 1994-12-20 | 1996-06-25 | Sun Microsystems, Inc. | Method for extracting profiles and topics from a first file written in a first markup language and generating files in different markup languages containing the profiles and topics for use in accessing data described by the profiles and topics |
US5664714A (en) | 1995-01-18 | 1997-09-09 | Navarro; Jose | Vehicular entertainment component stand |
US5694523A (en) | 1995-05-31 | 1997-12-02 | Oracle Corporation | Content processing system for discourse |
US5768580A (en) | 1995-05-31 | 1998-06-16 | Oracle Corporation | Methods and apparatus for dynamic classification of discourse |
US5907837A (en) | 1995-07-17 | 1999-05-25 | Microsoft Corporation | Information retrieval system in an on-line network including separate content and layout of published titles |
WO1997008604A2 (en) | 1995-08-16 | 1997-03-06 | Syracuse University | Multilingual document retrieval system and method using semantic vector matching |
US5699528A (en) | 1995-10-31 | 1997-12-16 | Mastercard International, Inc. | System and method for bill delivery and payment over a communications network |
US5754840A (en) | 1996-01-23 | 1998-05-19 | Smartpatents, Inc. | System, method, and computer program product for developing and maintaining documents which includes analyzing a patent application with regards to the specification and claims |
US5659729A (en) | 1996-02-01 | 1997-08-19 | Sun Microsystems, Inc. | Method and system for implementing hypertext scroll attributes |
US6076088A (en) | 1996-02-09 | 2000-06-13 | Paik; Woojin | Information extraction system and method using concept relation concept (CRC) triples |
US5758328A (en) | 1996-02-22 | 1998-05-26 | Giovannoli; Joseph | Computerized quotation system and method |
US5794236A (en) | 1996-05-29 | 1998-08-11 | Lexis-Nexis | Computer-based system for classifying documents into a hierarchy and linking the classifications to the hierarchy |
US5721910A (en) | 1996-06-04 | 1998-02-24 | Exxon Research And Engineering Company | Relational database system containing a multidimensional hierachical model of interrelated subject categories with recognition capabilities |
US5850520A (en) | 1996-07-01 | 1998-12-15 | Electronic Data Systems Corporation | Method and system for electronic publication distribution including return receipt |
US5870745A (en) | 1996-09-26 | 1999-02-09 | Mciworldcom, Inc. | Automated system and method for processing and tracking requests and responses required for repetitive tasks |
US5895468A (en) | 1996-10-07 | 1999-04-20 | Whitmyer, Jr.; Wesley W. | System automating delivery of professional services |
US6049801A (en) | 1996-10-07 | 2000-04-11 | Whitmyer, Jr.; Wesley W. | Web site providing professional services |
US6038561A (en) * | 1996-10-15 | 2000-03-14 | Manning & Napier Information Services | Management and analysis of document information text |
US6415319B1 (en) | 1997-02-07 | 2002-07-02 | Sun Microsystems, Inc. | Intelligent network browser using incremental conceptual indexer |
US5940821A (en) | 1997-05-21 | 1999-08-17 | Oracle Corporation | Information presentation in a knowledge base search and retrieval system |
US5903881A (en) | 1997-06-05 | 1999-05-11 | Intuit, Inc. | Personal online banking with integrated online statement and checkbook user interface |
US6363361B1 (en) | 1997-07-22 | 2002-03-26 | Patent & Trademark Fee Management, Llc | Computerized patent and trademark fee payment method and system for law firms |
US7680733B1 (en) | 1997-07-22 | 2010-03-16 | Patent And Trademark Fee Management, Llc | Computerized patent and trademark fee payment method and system |
US6216128B1 (en) | 1997-10-09 | 2001-04-10 | Telcordia Technologies, Inc. | System and method for private information retrieval from a single electronic storage device using commodities |
US5991756A (en) | 1997-11-03 | 1999-11-23 | Yahoo, Inc. | Information retrieval from hierarchical compound documents |
US5953726A (en) | 1997-11-24 | 1999-09-14 | International Business Machines Corporation | Method and apparatus for maintaining multiple inheritance concept hierarchies |
US6055538A (en) | 1997-12-22 | 2000-04-25 | Hewlett Packard Company | Methods and system for using web browser to search large collections of documents |
US6766315B1 (en) * | 1998-05-01 | 2004-07-20 | Bratsos Timothy G | Method and apparatus for simultaneously accessing a plurality of dispersed databases |
US6226792B1 (en) | 1998-10-14 | 2001-05-01 | Unisys Corporation | Object management system supporting the use of application domain knowledge mapped to technology domain knowledge |
US6453312B1 (en) | 1998-10-14 | 2002-09-17 | Unisys Corporation | System and method for developing a selectably-expandable concept-based search |
US6574632B2 (en) | 1998-11-18 | 2003-06-03 | Harris Corporation | Multiple engine information retrieval and visualization system |
US6327593B1 (en) | 1998-12-23 | 2001-12-04 | Unisys Corporation | Automated system and method for capturing and managing user knowledge within a search system |
US8095581B2 (en) * | 1999-02-05 | 2012-01-10 | Gregory A Stobbs | Computer-implemented patent portfolio analysis method and apparatus |
US7716060B2 (en) | 1999-03-02 | 2010-05-11 | Germeraad Paul B | Patent-related tools and methodology for use in the merger and acquisition process |
US7966328B2 (en) | 1999-03-02 | 2011-06-21 | Rose Blush Software Llc | Patent-related tools and methodology for use in research and development projects |
US6711585B1 (en) | 1999-06-15 | 2004-03-23 | Kanisa Inc. | System and method for implementing a knowledge management system |
US6981007B1 (en) | 1999-07-09 | 2005-12-27 | Whitmyer Jr Wesley W | Onsite backup for internet-based data processing |
CA2381460A1 (en) | 1999-08-06 | 2001-02-15 | James S. Wiltshire, Jr. | System and method for classifying legal concepts using legal topic scheme |
US6556992B1 (en) | 1999-09-14 | 2003-04-29 | Patent Ratings, Llc | Method and system for rating patents and other intangible assets |
US20090259506A1 (en) * | 1999-09-14 | 2009-10-15 | Barney Jonathan A | Method and system for rating patents and other intangible assets |
US7016852B1 (en) | 1999-09-30 | 2006-03-21 | Eugene M. Lee | Fee transaction system and method for intellectual property acquisition and/or maintenance |
US20040103112A1 (en) | 1999-10-08 | 2004-05-27 | Colson Thomas J. | Computer based method and apparatus for mining and displaying patent data |
US6789092B1 (en) * | 1999-11-01 | 2004-09-07 | Oppedahl & Larson, Llp | Status monitoring system |
JP3754253B2 (en) | 1999-11-19 | 2006-03-08 | 株式会社東芝 | Structured document search method, structured document search apparatus, and structured document search system |
US7127405B1 (en) | 1999-12-30 | 2006-10-24 | Bellsouth Intellectual Property Corp. | System and method for selecting and protecting intellectual property assets |
US7634415B2 (en) | 1999-12-30 | 2009-12-15 | At&T Intellectual Property I, L.P. | Systems and processes for technology asset management |
US6751621B1 (en) | 2000-01-27 | 2004-06-15 | Manning & Napier Information Services, Llc. | Construction of trainable semantic vectors and clustering, classification, and searching using trainable semantic vectors |
US6640098B1 (en) | 2000-02-14 | 2003-10-28 | Action Engine Corporation | System for obtaining service-related information for local interactive wireless devices |
EP1272912A2 (en) | 2000-02-25 | 2003-01-08 | Synquiry Technologies, Ltd | Conceptual factoring and unification of graphs representing semantic models |
US20010049707A1 (en) | 2000-02-29 | 2001-12-06 | Tran Bao Q. | Systems and methods for generating intellectual property |
WO2001067225A2 (en) | 2000-03-06 | 2001-09-13 | Kanisa Inc. | A system and method for providing an intelligent multi-step dialog with a user |
US6542884B1 (en) * | 2000-03-14 | 2003-04-01 | Microsoft Corporation | Methods and systems for updating an inheritance tree with minimal increase in memory usage |
US6970842B1 (en) | 2000-03-21 | 2005-11-29 | Halo Management, Llc | Project docket management apparatus and method |
US7757168B1 (en) | 2000-04-07 | 2010-07-13 | Xerox Corporation | Meta-document and method of managing |
US20020022974A1 (en) * | 2000-04-14 | 2002-02-21 | Urban Lindh | Display of patent information |
US6879990B1 (en) * | 2000-04-28 | 2005-04-12 | Institute For Scientific Information, Inc. | System for identifying potential licensees of a source patent portfolio |
US20020163541A1 (en) | 2000-05-04 | 2002-11-07 | Williams G. Thomas | System and method for organizing and presenting information relating to the interpretation of multiple information elements, such as patent claim elements, in at least one reference source and graphical user interface incorporating the same |
US6885999B1 (en) | 2000-05-10 | 2005-04-26 | Cisco Technology, Inc. | Digital identifiers and digital identifier control systems for intellectual properties |
US20020091541A1 (en) * | 2000-06-16 | 2002-07-11 | Seekip.Com | Method and apparatus for intellectual property management on the internet |
US6678692B1 (en) | 2000-07-10 | 2004-01-13 | Northrop Grumman Corporation | Hierarchy statistical analysis system and method |
US6675159B1 (en) | 2000-07-27 | 2004-01-06 | Science Applic Int Corp | Concept-based search and retrieval system |
US6823331B1 (en) | 2000-08-28 | 2004-11-23 | Entrust Limited | Concept identification system and method for use in reducing and/or representing text content of an electronic document |
WO2002021337A1 (en) | 2000-09-06 | 2002-03-14 | Daryl Craig Josephson | Data gathering and distribution apparatus and methods |
US20040260569A1 (en) | 2000-09-07 | 2004-12-23 | Cyber Legal Solutions, Inc. | Expert legal task management |
US20020035571A1 (en) | 2000-09-15 | 2002-03-21 | Coult John H | Digital patent marking method |
US20020042784A1 (en) | 2000-10-06 | 2002-04-11 | Kerven David S. | System and method for automatically searching and analyzing intellectual property-related materials |
US7487114B2 (en) | 2000-10-23 | 2009-02-03 | Costar Group, Inc. | System and method for associating aerial images, map features, and information |
US20040073443A1 (en) * | 2000-11-10 | 2004-04-15 | Gabrick John J. | System for automating and managing an IP environment |
US6999956B2 (en) | 2000-11-16 | 2006-02-14 | Ward Mullins | Dynamic object-driven database manipulation and mapping system |
US20020161733A1 (en) | 2000-11-27 | 2002-10-31 | First To File, Inc. | Method of creating electronic prosecution experience for patent applicant |
US20020111953A1 (en) | 2000-11-27 | 2002-08-15 | First To File, Inc. | Docketing system |
US20020065675A1 (en) | 2000-11-27 | 2002-05-30 | Grainger Jeffry J. | Computer implemented method of managing information disclosure statements |
US20020111824A1 (en) | 2000-11-27 | 2002-08-15 | First To File, Inc. | Method of defining workflow rules for managing intellectual property |
US20020065677A1 (en) | 2000-11-27 | 2002-05-30 | First To File, Inc. | Computer implemented method of managing information disclosure statements |
US7653551B2 (en) | 2000-12-05 | 2010-01-26 | Ipwealth.Com, Inc. | Method and system for searching and submitting online via an aggregation portal |
US6678677B2 (en) | 2000-12-19 | 2004-01-13 | Xerox Corporation | Apparatus and method for information retrieval using self-appending semantic lattice |
US20030220891A1 (en) | 2000-12-22 | 2003-11-27 | Fish Robert D | Matter management computer software |
US6839707B2 (en) | 2001-01-17 | 2005-01-04 | General Electric Company | Web-based system and method for managing legal information |
US20020107896A1 (en) | 2001-02-02 | 2002-08-08 | Abraham Ronai | Patent application drafting assistance tool |
US6694331B2 (en) | 2001-03-21 | 2004-02-17 | Knowledge Management Objects, Llc | Apparatus for and method of searching and organizing intellectual property information utilizing a classification system |
US8484177B2 (en) | 2001-03-21 | 2013-07-09 | Eugene M. Lee | Apparatus for and method of searching and organizing intellectual property information utilizing a field-of-search |
EP1386262A4 (en) | 2001-03-29 | 2007-12-19 | Schwegman Lundberg Woessner & | Internet-based patent and trademark application management system |
US20020184234A1 (en) | 2001-06-01 | 2002-12-05 | Lundberg Steven W. | Internet-based patent and trademark applicaton management system |
JP3842577B2 (en) | 2001-03-30 | 2006-11-08 | 株式会社東芝 | Structured document search method, structured document search apparatus and program |
JP3842573B2 (en) | 2001-03-30 | 2006-11-08 | 株式会社東芝 | Structured document search method, structured document management apparatus and program |
US6665670B2 (en) | 2001-03-30 | 2003-12-16 | M.Cam, Inc. | Method and system for graphical representation of multitemporal, multidimensional data relationships |
US6976016B2 (en) | 2001-04-02 | 2005-12-13 | Vima Technologies, Inc. | Maximizing expected generalization for learning complex query concepts |
US20020147738A1 (en) | 2001-04-06 | 2002-10-10 | Reader Scot A. | Method and appratus for finding patent-relevant web documents |
US6839564B2 (en) * | 2001-04-25 | 2005-01-04 | Nokia Corporation | Synchronization of database data |
US6970881B1 (en) | 2001-05-07 | 2005-11-29 | Intelligenxia, Inc. | Concept-based method and system for dynamically analyzing unstructured information |
US6980984B1 (en) | 2001-05-16 | 2005-12-27 | Kanisa, Inc. | Content provider systems and methods using structured data |
US8326851B2 (en) | 2001-06-29 | 2012-12-04 | Grune Guerry L | Simultaneous intellectual property search and valuation system and methodology (SIPS-VSM) |
GB2377047A (en) | 2001-06-29 | 2002-12-31 | Nokia Corp | Intellectual property rights contract |
EP1276059A3 (en) * | 2001-07-11 | 2006-06-07 | Rohm And Haas Company | Data processing system |
KR20030009704A (en) | 2001-07-23 | 2003-02-05 | 한국전자통신연구원 | System for drawing patent map using technical field word, its method |
KR100436356B1 (en) * | 2001-08-01 | 2004-06-18 | (주) 위즈도메인 | A method for analyzing and providing inter-citation relationship between patents related to a subject patent |
US9460414B2 (en) | 2001-08-28 | 2016-10-04 | Eugene M. Lee | Computer assisted and/or implemented process and system for annotating and/or linking documents and data, optionally in an intellectual property management system |
US8078545B1 (en) | 2001-09-24 | 2011-12-13 | Aloft Media, Llc | System, method and computer program product for collecting strategic patent data associated with an identifier |
US20030084066A1 (en) | 2001-10-31 | 2003-05-01 | Waterman Scott A. | Device and method for assisting knowledge engineer in associating intelligence with content |
US20040006594A1 (en) | 2001-11-27 | 2004-01-08 | Ftf Technologies Inc. | Data access control techniques using roles and permissions |
US20030115191A1 (en) | 2001-12-17 | 2003-06-19 | Max Copperman | Efficient and cost-effective content provider for customer relationship management (CRM) or other applications |
AU2003210789A1 (en) | 2002-02-01 | 2003-09-02 | John Fairweather | A system and method for managing dataflows |
US20030154085A1 (en) | 2002-02-08 | 2003-08-14 | Onevoice Medical Corporation | Interactive knowledge base system |
US20030167181A1 (en) | 2002-03-01 | 2003-09-04 | Schwegman, Lundberg, Woessner & Kluth, P.A. | Systems and methods for managing information disclosure statement (IDS) references |
US8589413B1 (en) | 2002-03-01 | 2013-11-19 | Ixreveal, Inc. | Concept-based method and system for dynamically analyzing results from search engines |
US20030187874A1 (en) * | 2002-03-20 | 2003-10-02 | Andreas Peschel | Computer & Internet software application for global portfolio management system method & apparatus |
DE10215495A1 (en) | 2002-04-09 | 2003-10-30 | Bayer Ag | Computer system and method for research, statistical evaluation and analysis of documents |
US6847966B1 (en) | 2002-04-24 | 2005-01-25 | Engenium Corporation | Method and system for optimally searching a document database using a representative semantic space |
US20030212706A1 (en) | 2002-05-07 | 2003-11-13 | Shih Yu Li | Patent management system |
US7085771B2 (en) | 2002-05-17 | 2006-08-01 | Verity, Inc | System and method for automatically discovering a hierarchy of concepts from a corpus of documents |
US20040015481A1 (en) | 2002-05-23 | 2004-01-22 | Kenneth Zinda | Patent data mining |
US20030229470A1 (en) * | 2002-06-10 | 2003-12-11 | Nenad Pejic | System and method for analyzing patent-related information |
WO2003106747A2 (en) * | 2002-06-13 | 2003-12-24 | Milliken & Company | Multiple-component magnetic mat |
US7016895B2 (en) | 2002-07-05 | 2006-03-21 | Word Data Corp. | Text-classification system and method |
US7024408B2 (en) | 2002-07-03 | 2006-04-04 | Word Data Corp. | Text-classification code, system and method |
US7181451B2 (en) | 2002-07-03 | 2007-02-20 | Word Data Corp. | Processing input text to generate the selectivity value of a word or word group in a library of texts in a field is related to the frequency of occurrence of that word or word group in library |
US20040006547A1 (en) | 2002-07-03 | 2004-01-08 | Dehlinger Peter J. | Text-processing database |
US7003516B2 (en) | 2002-07-03 | 2006-02-21 | Word Data Corp. | Text representation and method |
US20040006459A1 (en) | 2002-07-05 | 2004-01-08 | Dehlinger Peter J. | Text-searching system and method |
KR100490725B1 (en) | 2002-07-11 | 2005-05-24 | 한국전자통신연구원 | Method for constructing database of technique classification patent map |
US7493253B1 (en) | 2002-07-12 | 2009-02-17 | Language And Computing, Inc. | Conceptual world representation natural language understanding system and method |
US20060225000A1 (en) | 2005-04-01 | 2006-10-05 | Paul Albrecht | Graphical application interface using browser |
US20040044688A1 (en) | 2002-08-30 | 2004-03-04 | Brudz John Jason | Patent asset management systems and methods |
US7158983B2 (en) | 2002-09-23 | 2007-01-02 | Battelle Memorial Institute | Text analysis technique |
US20040059994A1 (en) | 2002-09-23 | 2004-03-25 | Ronny Fogel | Method of checking patent claims |
US6886010B2 (en) | 2002-09-30 | 2005-04-26 | The United States Of America As Represented By The Secretary Of The Navy | Method for data and text mining and literature-based discovery |
US7801909B2 (en) | 2002-10-17 | 2010-09-21 | Poltorak Alexander I | Apparatus and method for identifying and/or for analyzing potential patent infringement |
US7904453B2 (en) * | 2002-10-17 | 2011-03-08 | Poltorak Alexander I | Apparatus and method for analyzing patent claim validity |
US7296015B2 (en) | 2002-10-17 | 2007-11-13 | Poltorak Alexander I | Apparatus and method for identifying and/or for analyzing potential patent infringement |
EP1411448A3 (en) | 2002-10-17 | 2007-12-05 | Matsushita Electric Industrial Co., Ltd. | Data searching apparatus |
US20040186738A1 (en) | 2002-10-24 | 2004-09-23 | Richard Reisman | Method and apparatus for an idea adoption marketplace |
WO2004042493A2 (en) | 2002-10-24 | 2004-05-21 | Agency For Science, Technology And Research | Method and system for discovering knowledge from text documents |
US7142713B1 (en) | 2002-10-24 | 2006-11-28 | Foundationip, Llc | Automated docketing system |
US7231384B2 (en) | 2002-10-25 | 2007-06-12 | Sap Aktiengesellschaft | Navigation tool for exploring a knowledge base |
EP1562570A4 (en) | 2002-11-06 | 2007-09-05 | Sinai School Medicine | Treatment of amyotrophic lateral sclerosis with nimesulide |
US6947950B2 (en) * | 2002-11-06 | 2005-09-20 | Oracle International Corporation | Techniques for managing multiple hierarchies of data from a single interface |
US7739240B2 (en) * | 2002-12-09 | 2010-06-15 | Hewlett-Packard Development Company, L.P. | Replication and replica management in a wide area file system |
US20040199400A1 (en) | 2002-12-17 | 2004-10-07 | Lundberg Steven W. | Internet-based patent and trademark application management system |
US20040122841A1 (en) | 2002-12-19 | 2004-06-24 | Ford Motor Company | Method and system for evaluating intellectual property |
US20040167875A1 (en) | 2003-02-20 | 2004-08-26 | Eriks Sneiders | Information processing method and system |
US8694504B2 (en) | 2003-03-05 | 2014-04-08 | Spore, Inc. | Methods and systems for technology analysis and mapping |
US20040181417A1 (en) | 2003-03-14 | 2004-09-16 | Gunther Piller | Managing the definition of a product innovation |
EP1623339A2 (en) | 2003-05-01 | 2006-02-08 | Axonwave Software Inc. | A method and system for concept generation and management |
US20050004806A1 (en) | 2003-06-20 | 2005-01-06 | Dah-Chih Lin | Automatic patent claim reader and computer-aided claim reading method |
US20050005239A1 (en) | 2003-07-03 | 2005-01-06 | Richards James L. | System and method for automatic insertion of cross references in a document |
US7171618B2 (en) | 2003-07-30 | 2007-01-30 | Xerox Corporation | Multi-versioned documents and method for creation and use thereof |
EP1673702A4 (en) | 2003-09-11 | 2008-11-05 | Ipx Inc | System for software source code comparison |
TW200511048A (en) | 2003-09-12 | 2005-03-16 | Hon Hai Prec Ind Co Ltd | Patent family analysis system and method |
US7555441B2 (en) | 2003-10-10 | 2009-06-30 | Kronos Talent Management Inc. | Conceptualization of job candidate information |
US9922383B2 (en) | 2003-11-07 | 2018-03-20 | Spore, Inc. | Patent claims analysis system and method |
US10198478B2 (en) | 2003-10-11 | 2019-02-05 | Magic Number, Inc. | Methods and systems for technology analysis and mapping |
US9483551B2 (en) | 2003-10-11 | 2016-11-01 | Spore, Inc. | Methods and systems for technology analysis and mapping |
US20050234738A1 (en) | 2003-11-26 | 2005-10-20 | Hodes Alan S | Competitive product intelligence system and method, including patent analysis and formulation using one or more ontologies |
US20050120011A1 (en) | 2003-11-26 | 2005-06-02 | Word Data Corp. | Code, method, and system for manipulating texts |
US20050144177A1 (en) * | 2003-11-26 | 2005-06-30 | Hodes Alan S. | Patent analysis and formulation using ontologies |
US20060106793A1 (en) | 2003-12-29 | 2006-05-18 | Ping Liang | Internet and computer information retrieval and mining with intelligent conceptual filtering, visualization and automation |
US7281008B1 (en) * | 2003-12-31 | 2007-10-09 | Google Inc. | Systems and methods for constructing a query result set |
US7702516B2 (en) | 2004-01-13 | 2010-04-20 | International Business Machines Corporation | Payment control to inventors in patent tracking system |
US8868405B2 (en) | 2004-01-27 | 2014-10-21 | Hewlett-Packard Development Company, L. P. | System and method for comparative analysis of textual documents |
US20050198026A1 (en) | 2004-02-03 | 2005-09-08 | Dehlinger Peter J. | Code, system, and method for generating concepts |
US20050182755A1 (en) | 2004-02-14 | 2005-08-18 | Bao Tran | Systems and methods for analyzing documents over a network |
US20050210008A1 (en) | 2004-03-18 | 2005-09-22 | Bao Tran | Systems and methods for analyzing documents over a network |
US20050210009A1 (en) | 2004-03-18 | 2005-09-22 | Bao Tran | Systems and methods for intellectual property management |
US20050246194A1 (en) | 2004-04-06 | 2005-11-03 | Lundberg Steven W | System and method for information disclosure statement management |
US20050228684A1 (en) | 2004-04-13 | 2005-10-13 | Pavel Pogodin | Integrated computerized system and method for management of intellectual property |
US20050234881A1 (en) | 2004-04-16 | 2005-10-20 | Anna Burago | Search wizard |
US20070067297A1 (en) | 2004-04-30 | 2007-03-22 | Kublickis Peter J | System and methods for a micropayment-enabled marketplace with permission-based, self-service, precision-targeted delivery of advertising, entertainment and informational content and relationship marketing to anonymous internet users |
EP2487601A1 (en) | 2004-05-04 | 2012-08-15 | Boston Consulting Group, Inc. | Method and apparatus for selecting, analyzing and visualizing related database records as a network |
US7447665B2 (en) | 2004-05-10 | 2008-11-04 | Kinetx, Inc. | System and method of self-learning conceptual mapping to organize and interpret data |
US7996753B1 (en) | 2004-05-10 | 2011-08-09 | Google Inc. | Method and system for automatically creating an image advertisement |
US20050256734A1 (en) | 2004-05-14 | 2005-11-17 | Clikeman Richard R | Method and data structure for augmenting invention and analysis of intellectual property |
WO2006002234A2 (en) | 2004-06-22 | 2006-01-05 | Coras, Inc. | Systems and methods for software based on business concepts |
US20060026174A1 (en) * | 2004-07-27 | 2006-02-02 | Lundberg Steven W | Patent mapping |
US20060036451A1 (en) | 2004-08-10 | 2006-02-16 | Lundberg Steven W | Patent mapping |
EP1774432A4 (en) | 2004-07-27 | 2009-04-22 | Schwegman Lundberg Woessner & | Patent mapping |
US7840460B2 (en) | 2004-08-11 | 2010-11-23 | Allan Williams | System and method for patent portfolio evaluation |
US8145640B2 (en) | 2004-08-11 | 2012-03-27 | Allan Williams | System and method for patent evaluation and visualization of the results thereof |
US8161049B2 (en) | 2004-08-11 | 2012-04-17 | Allan Williams | System and method for patent evaluation using artificial intelligence |
US20060036453A1 (en) | 2004-08-11 | 2006-02-16 | Allan Williams | Bias compensated method and system for patent evaluation |
US8145639B2 (en) | 2004-08-11 | 2012-03-27 | Allan Williams | System and methods for patent evaluation |
US20060074836A1 (en) | 2004-09-03 | 2006-04-06 | Biowisdom Limited | System and method for graphically displaying ontology data |
US7433884B2 (en) * | 2004-09-29 | 2008-10-07 | Chi Research, Inc. | Identification of licensing targets using citation neighbor search process |
US20060074980A1 (en) | 2004-09-29 | 2006-04-06 | Sarkar Pte. Ltd. | System for semantically disambiguating text information |
US20060173903A1 (en) | 2004-09-30 | 2006-08-03 | Zimmerman Mark C | Methods and apparatus to automatically generate claim charts |
US20060085478A1 (en) | 2004-10-18 | 2006-04-20 | Michael Landau | Third-party automated tracking, analysis, and distribution of registry status information |
US20080077570A1 (en) | 2004-10-25 | 2008-03-27 | Infovell, Inc. | Full Text Query and Search Systems and Method of Use |
US7783619B2 (en) * | 2004-10-27 | 2010-08-24 | Elsevier B.V. | Methods and software for analysis of research publications |
US20060149720A1 (en) * | 2004-12-30 | 2006-07-06 | Dehlinger Peter J | System and method for retrieving information from citation-rich documents |
US7444589B2 (en) | 2004-12-30 | 2008-10-28 | At&T Intellectual Property I, L.P. | Automated patent office documentation |
US8229905B2 (en) | 2005-01-14 | 2012-07-24 | Ricoh Co., Ltd. | Adaptive document management system using a physical representation of a document |
US20060190449A1 (en) | 2005-02-18 | 2006-08-24 | Lundberg Steven W | System and method for prior art cross citation |
US20060212402A1 (en) | 2005-03-21 | 2006-09-21 | Lundberg Steven W | System and method for export control of technical documents |
US20060212471A1 (en) * | 2005-03-21 | 2006-09-21 | Lundberg Steven W | System and method for intellectual property information management using configurable activities |
US20060212480A1 (en) | 2005-03-21 | 2006-09-21 | Lundberg Steven W | System and method for matter clusters in an IP management system |
US7853629B2 (en) | 2005-03-23 | 2010-12-14 | Executive Data Systems, Inc. | Document imaging and management system for paperless workflow |
US20060218491A1 (en) | 2005-03-25 | 2006-09-28 | International Business Machines Corporation | System, method and program product for community review of documents |
US20060258397A1 (en) | 2005-05-10 | 2006-11-16 | Kaplan Mark M | Integrated mobile application server and communication gateway |
US20080195601A1 (en) | 2005-04-14 | 2008-08-14 | The Regents Of The University Of California | Method For Information Retrieval |
US20110153509A1 (en) * | 2005-05-27 | 2011-06-23 | Ip Development Venture | Method and apparatus for cross-referencing important ip relationships |
US8805781B2 (en) | 2005-06-15 | 2014-08-12 | Geronimo Development | Document quotation indexing system and method |
US7472119B2 (en) * | 2005-06-30 | 2008-12-30 | Microsoft Corporation | Prioritizing search results by client search satisfaction |
US20070130112A1 (en) | 2005-06-30 | 2007-06-07 | Intelligentek Corp. | Multimedia conceptual search system and associated search method |
US20070057967A1 (en) | 2005-07-13 | 2007-03-15 | Armstrong Orin R | System and method for the display of versioned documents and amendments |
WO2007014341A2 (en) | 2005-07-27 | 2007-02-01 | Schwegman, Lundberg & Woessner, P.A. | Patent mapping |
US7716226B2 (en) | 2005-09-27 | 2010-05-11 | Patentratings, Llc | Method and system for probabilistically quantifying and visualizing relevance between two or more citationally or contextually related data objects |
US20070220041A1 (en) * | 2005-10-14 | 2007-09-20 | Leviathan Entertainment, Llc | Prior Art Notes Associated with Patent Applications |
US20080015968A1 (en) * | 2005-10-14 | 2008-01-17 | Leviathan Entertainment, Llc | Fee-Based Priority Queuing for Insurance Claim Processing |
US8386350B2 (en) * | 2006-04-04 | 2013-02-26 | International Buisness Machines Corporation | System and method for extracting value from a portfolio of assets |
US20080005103A1 (en) | 2006-06-08 | 2008-01-03 | Invequity, Llc | Intellectual property search, marketing and licensing connection system and method |
US20080021900A1 (en) | 2006-07-14 | 2008-01-24 | Ficus Enterprises, Llc | Examiner information system |
US20080216013A1 (en) | 2006-08-01 | 2008-09-04 | Lundberg Steven W | Patent tracking |
US8392174B2 (en) | 2006-08-07 | 2013-03-05 | International Characters, Inc. | Method and apparatus for lexical analysis using parallel bit streams |
US20090282054A1 (en) | 2006-09-29 | 2009-11-12 | Casey Michael R | IDS Reference Tracking System |
US20080097931A1 (en) * | 2006-10-23 | 2008-04-24 | Ipie Mae Corporation | Computer assisted process for providing liquidity to an enterprise by utilizing intellectual property assets |
US8065307B2 (en) * | 2006-12-20 | 2011-11-22 | Microsoft Corporation | Parsing, analysis and scoring of document content |
US20080183518A1 (en) * | 2007-01-30 | 2008-07-31 | Herb Jiang | Method and system for analyzing patent flow |
US20080195604A1 (en) * | 2007-02-08 | 2008-08-14 | Christopher Nordby Sears | Synthesis-based approach to draft an invention disclosure using improved prior art search technique |
US7881937B2 (en) * | 2007-05-31 | 2011-02-01 | International Business Machines Corporation | Method for analyzing patent claims |
US8160306B1 (en) * | 2007-06-06 | 2012-04-17 | Neustel Michael S | Patent analyzing system |
US8230458B2 (en) * | 2007-06-29 | 2012-07-24 | At&T Intellectual Property I, L.P. | System and method of providing video content commentary |
WO2009018223A1 (en) * | 2007-07-27 | 2009-02-05 | Sparkip, Inc. | System and methods for clustering large database of documents |
US20090030713A1 (en) * | 2007-07-27 | 2009-01-29 | Venkatachalam A R | System and method of reviewing ownership of and encumbrances on intellectual property assets |
EP2193462A2 (en) * | 2007-08-28 | 2010-06-09 | Lexisnexis Group | Document search tool |
US20090083049A1 (en) | 2007-09-24 | 2009-03-26 | Sciarrino David M | Claim chart creation system |
US7836048B2 (en) * | 2007-11-19 | 2010-11-16 | Red Hat, Inc. | Socially-derived relevance in search engine results |
US20090150326A1 (en) * | 2007-12-10 | 2009-06-11 | Foundationip, Llc | Smart agent for examination of an application |
US20090158186A1 (en) | 2007-12-17 | 2009-06-18 | Bonev Robert | Drag and drop glads |
US20100023386A1 (en) | 2008-07-23 | 2010-01-28 | Sol Avisar | Social networking platform for intellectual property assets |
US9003474B1 (en) * | 2008-08-22 | 2015-04-07 | Taser International, Inc. | Systems and methods for managing disclosure of protectable information |
US20100077007A1 (en) * | 2008-09-18 | 2010-03-25 | Jason White | Method and System for Populating a Database With Bibliographic Data From Multiple Sources |
US20100082395A1 (en) * | 2008-09-29 | 2010-04-01 | Anthony Bernard De Andrade | Systems and methods for analyzing a portfolio of intellectual property assets |
US20100131513A1 (en) | 2008-10-23 | 2010-05-27 | Lundberg Steven W | Patent mapping |
US20100174698A1 (en) * | 2009-01-06 | 2010-07-08 | Global Patent Solutions, Llc | Method for a customized and automated forward and backward patent citation search |
US20110029476A1 (en) * | 2009-07-29 | 2011-02-03 | Kas Kasravi | Indicating relationships among text documents including a patent based on characteristics of the text documents |
US10013726B1 (en) * | 2009-08-26 | 2018-07-03 | Edward Jung | Acquiring intellectual property assets |
US20110246473A1 (en) * | 2009-09-16 | 2011-10-06 | John Stec | Computerized method for analyizing innovation interrelationships within and between large patent portfolios |
WO2011056557A2 (en) * | 2009-10-26 | 2011-05-12 | View2Gether Inc. | System and method for providing a user terminal with supplemental information to a search result |
US8209349B2 (en) * | 2010-02-01 | 2012-06-26 | Rockmelt, Inc. | Integrated saved search results |
US20110231449A1 (en) | 2010-03-17 | 2011-09-22 | Ashley William B | System, Method, and Apparatus for Managing Patent Reference Reporting |
US20110320582A1 (en) | 2010-06-23 | 2011-12-29 | Lewis George C | Online presence management system |
US20130282599A1 (en) * | 2010-11-02 | 2013-10-24 | Kwanggaeto Co., Ltd. | Method of generating patent evaluation model, method of evaluating patent, method of generating patent dispute prediction model, method of generating patent dispute prediction information, and method and system for generating patent risk hedging information |
US8712894B2 (en) * | 2010-11-04 | 2014-04-29 | National Yunlin University Of Science And Technology | Method and system for evaluating/analyzing patent portfolio using patent priority approach |
US8316030B2 (en) * | 2010-11-05 | 2012-11-20 | Nextgen Datacom, Inc. | Method and system for document classification or search using discrete words |
US20120174017A1 (en) * | 2010-12-29 | 2012-07-05 | Verisign, Inc. | Systems, methods and computer software for innovation management |
US20120240026A1 (en) * | 2011-03-14 | 2012-09-20 | Anaqua, Inc. | Method and system for related art citation management |
US8996506B2 (en) * | 2011-03-28 | 2015-03-31 | Red Hat Israel, Ltd. | Duplicate search optimization |
US8972385B2 (en) | 2011-10-03 | 2015-03-03 | Black Hills Ip Holdings, Llc | System and method for tracking patent ownership change |
US20130282409A1 (en) | 2011-10-03 | 2013-10-24 | Black Hills Ip Holdings, Llc | Systems and methods for patent portfolio management |
US9418083B2 (en) * | 2012-04-20 | 2016-08-16 | Patterson Thuente Pedersen, P.A. | System for computerized evaluation of patent-related information |
-
2011
- 2011-10-05 US US13/253,825 patent/US8972385B2/en active Active
- 2011-10-05 US US13/253,931 patent/US20130086080A1/en not_active Abandoned
- 2011-10-05 US US13/253,846 patent/US20130086044A1/en not_active Abandoned
- 2011-10-05 US US13/253,936 patent/US10860657B2/en active Active
- 2011-10-05 US US13/253,941 patent/US20130086070A1/en not_active Abandoned
- 2011-10-05 US US13/253,801 patent/US8892547B2/en active Active
- 2011-10-05 US US13/253,811 patent/US20130086042A1/en not_active Abandoned
- 2011-10-18 US US13/275,707 patent/US9201966B2/en active Active
-
2014
- 2014-09-11 US US14/483,903 patent/US20140379388A1/en not_active Abandoned
- 2014-11-13 US US14/540,346 patent/US9396274B2/en active Active
-
2015
- 2015-01-29 US US14/608,520 patent/US20150149368A1/en not_active Abandoned
- 2015-02-23 US US14/628,941 patent/US20150169777A1/en not_active Abandoned
- 2015-08-13 US US14/826,006 patent/US20150347604A1/en not_active Abandoned
- 2015-11-25 US US14/952,699 patent/US9652546B2/en active Active
-
2016
- 2016-07-15 US US15/211,917 patent/US20170075929A1/en not_active Abandoned
-
2017
- 2017-05-15 US US15/595,629 patent/US10671574B2/en active Active
-
2020
- 2020-11-24 US US17/103,870 patent/US20210149969A1/en active Pending
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20010007977A1 (en) * | 2000-01-06 | 2001-07-12 | Geary Stuart Lloyd | Reminder and actioning system |
US20110099084A1 (en) * | 2009-04-20 | 2011-04-28 | Mpeg La L.L.C. | Systems and methods for managing patent licenses |
Cited By (38)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11776084B2 (en) | 2004-08-10 | 2023-10-03 | Lucid Patent Llc | Patent mapping |
US11080807B2 (en) | 2004-08-10 | 2021-08-03 | Lucid Patent Llc | Patent mapping |
US11798111B2 (en) | 2005-05-27 | 2023-10-24 | Black Hills Ip Holdings, Llc | Method and apparatus for cross-referencing important IP relationships |
US9659071B2 (en) | 2005-07-27 | 2017-05-23 | Schwegman Lundberg & Woessner, P.A. | Patent mapping |
US10546273B2 (en) | 2008-10-23 | 2020-01-28 | Black Hills Ip Holdings, Llc | Patent mapping |
US11301810B2 (en) * | 2008-10-23 | 2022-04-12 | Black Hills Ip Holdings, Llc | Patent mapping |
US11714839B2 (en) | 2011-05-04 | 2023-08-01 | Black Hills Ip Holdings, Llc | Apparatus and method for automated and assisted patent claim mapping and expense planning |
US20230019161A1 (en) * | 2011-10-03 | 2023-01-19 | Black Hills Ip Holdings, Llc | Patent claim mapping |
US11256706B2 (en) | 2011-10-03 | 2022-02-22 | Black Hills Ip Holdings, Llc | System and method for patent and prior art analysis |
US11803560B2 (en) * | 2011-10-03 | 2023-10-31 | Black Hills Ip Holdings, Llc | Patent claim mapping |
US11797546B2 (en) | 2011-10-03 | 2023-10-24 | Black Hills Ip Holdings, Llc | Patent mapping |
US10242066B2 (en) | 2011-10-03 | 2019-03-26 | Black Hills Ip Holdings, Llc | Systems, methods and user interfaces in a patent management system |
US9396274B2 (en) | 2011-10-03 | 2016-07-19 | Black Hills Ip Holdings, Llc | System and method for prior art analysis |
US10585904B2 (en) | 2011-10-03 | 2020-03-10 | Black Hills Ip Holdings, Llc | System and method for patent and prior art analysis |
US10614082B2 (en) | 2011-10-03 | 2020-04-07 | Black Hills Ip Holdings, Llc | Patent mapping |
US10628429B2 (en) | 2011-10-03 | 2020-04-21 | Black Hills Ip Holdings, Llc | Patent mapping |
US10803073B2 (en) | 2011-10-03 | 2020-10-13 | Black Hills Ip Holdings, Llc | Systems, methods and user interfaces in a patent management system |
US11789954B2 (en) | 2011-10-03 | 2023-10-17 | Black Hills Ip Holdings, Llc | System and method for patent and prior art analysis |
US10860657B2 (en) | 2011-10-03 | 2020-12-08 | Black Hills Ip Holdings, Llc | Patent mapping |
US11048709B2 (en) | 2011-10-03 | 2021-06-29 | Black Hills Ip Holdings, Llc | Patent mapping |
US9679019B2 (en) | 2011-10-03 | 2017-06-13 | Black Hills Ip Holdings, Llc | System and method for patent and prior art analysis |
US11775538B2 (en) | 2011-10-03 | 2023-10-03 | Black Hills Ip Holdings, Llc | Systems, methods and user interfaces in a patent management system |
US10268731B2 (en) | 2011-10-03 | 2019-04-23 | Black Hills Ip Holdings, Llc | Patent mapping |
US11294910B2 (en) | 2011-10-03 | 2022-04-05 | Black Hills Ip Holdings, Llc | Patent claim mapping |
US9858319B2 (en) | 2011-10-03 | 2018-01-02 | Black Hills IP Holdings, LLC. | Patent mapping |
US11360988B2 (en) | 2011-10-03 | 2022-06-14 | Black Hills Ip Holdings, Llc | Systems, methods and user interfaces in a patent management system |
US11372864B2 (en) | 2011-10-03 | 2022-06-28 | Black Hills Ip Holdings, Llc | Patent mapping |
US9286351B2 (en) | 2011-10-03 | 2016-03-15 | Black Hills Ip Holdings, Llc | System and method for patent and prior art analysis |
US11714819B2 (en) | 2011-10-03 | 2023-08-01 | Black Hills Ip Holdings, Llc | Patent mapping |
US10832224B2 (en) * | 2015-05-06 | 2020-11-10 | Vmware, Inc. | Calendar based management of information technology (IT) tasks |
US11138648B2 (en) | 2017-01-23 | 2021-10-05 | Stitch Fix, Inc. | Systems, apparatuses, and methods for generating inventory recommendations |
WO2018136747A1 (en) * | 2017-01-23 | 2018-07-26 | Tete-A-Tete, Inc. | Systems, apparatuses, and methods for extracting inventory from unstructured electronic messages |
US11798052B2 (en) | 2017-01-23 | 2023-10-24 | Stitch Fix, Inc. | Systems, apparatuses, and methods for extracting inventory from unstructured electronic messages |
US9911094B1 (en) * | 2017-05-11 | 2018-03-06 | International Business Machines Corporation | Intelligent key performance indicator catalog |
US10586196B2 (en) | 2017-05-11 | 2020-03-10 | International Business Machines Corporation | Intelligent key performance indicator catalog |
US10304024B2 (en) | 2017-05-11 | 2019-05-28 | International Business Machines Corporation | Intelligent key performance indicator catalog |
US10304023B2 (en) | 2017-05-11 | 2019-05-28 | International Business Machines Corporation | Intelligent key performance indicator catalog |
US20230047250A1 (en) * | 2021-08-13 | 2023-02-16 | Black Hills Ip Holdings, Llc | Document splitting tool |
Also Published As
Publication number | Publication date |
---|---|
US20150347604A1 (en) | 2015-12-03 |
US20130086070A1 (en) | 2013-04-04 |
US20160154863A1 (en) | 2016-06-02 |
US20130086050A1 (en) | 2013-04-04 |
US20130086042A1 (en) | 2013-04-04 |
US10860657B2 (en) | 2020-12-08 |
US20150169777A1 (en) | 2015-06-18 |
US20170075929A1 (en) | 2017-03-16 |
US20130086043A1 (en) | 2013-04-04 |
US20130086045A1 (en) | 2013-04-04 |
US20130086044A1 (en) | 2013-04-04 |
US9201966B2 (en) | 2015-12-01 |
US20150066842A1 (en) | 2015-03-05 |
US20210149969A1 (en) | 2021-05-20 |
US9396274B2 (en) | 2016-07-19 |
US20130086032A1 (en) | 2013-04-04 |
US20150149368A1 (en) | 2015-05-28 |
US10671574B2 (en) | 2020-06-02 |
US20170316036A1 (en) | 2017-11-02 |
US9652546B2 (en) | 2017-05-16 |
US8892547B2 (en) | 2014-11-18 |
US8972385B2 (en) | 2015-03-03 |
US20130086080A1 (en) | 2013-04-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20210407025A1 (en) | System and method for patent portfolio management | |
US20210027405A1 (en) | System and method for management of a patent portfolio | |
US20140379388A1 (en) | Systems and methods for patent portfolio management | |
US11256706B2 (en) | System and method for patent and prior art analysis | |
US20130346116A1 (en) | Mobile applications in patent portfolio management and annuity payments | |
US20230018572A1 (en) | Analytics generation for patent portfolio management | |
US20130132302A1 (en) | Systems, methods and interfaces in a patent portfolio management system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |