Using hyperbolic trees to visualize data generated by patent-centric and group-oriented data processing (24-Dec-2002)
US Patent Publication
(Source: USPTO)
Abstract (English)
A system, method, and computer program product for processing data are described herein. The system maintains first databases of patents, and second databases of non-patent information of interest to a corporate entity. The system also maintains one or more groups. Each of the groups comprises any number of the patents from the first databases. The system, upon receiving appropriate operator commands, automatically processes the patents in one of the groups in conjunction with non-patent information from the second databases. Accordingly, the system performs patent-centric and group-oriented processing of data. A group can also include any number of non-patent documents. The groups may be product based, person based, corporate entity based, or user-defined. Other types of groups are also covered, such as temporary groups. The processing automatically performed by the system relates to (but is not limited to) patent mapping, document mapping, patent citation (both forward and backward), patent aging, patent bracketing/clustering (both forward and backward), inventor patent count, inventor employment information, patent claim tree analysis, and finance. Other functions and capabilities are also covered, including the ability to utilize hyperbolic trees to visualize data generated by the system, method, and computer program product.
Inventors/Applicants
Rivette, Kevin G.
[+10]
Palo Alto, CA, US
Rappaport, Irving S.
Palo Alto, CA, US
Hohmann, Luke
Mountain View, CA, US
Puglia, David
Los Gatos, CA, US
Goretsky, David
Sunnyvale, CA, US
Jackson, Adam
Sunnyvale, CA, US
Rabb, Jr., Charles
Sunnyvale, CA, US
Smith, David W.
Mountain View, CA, US
Park, Brian
Palo Alto, CA, US
Thornthwaite, Warren
Menlo Park, CA, US
Navarette, Jorge A.
Menlo Park, CA, US
Assignees
Aurigin Systems, Inc.
Cupertino, CA, US
Patent References
Other References
A Few Facts About MicroPatent, at http://www.micropat.com/info/facts.htm, 1 page (last visited Dec. 6, 1996).
[+233]
About CHI Research, at http://www.chiresearch.com/htabout.html, 6 pages (last updated Aug. 6, 1996).
Agent Searching, at http://www.cris.com/˜eti/agent.html, 1 page (last updated Jan. 12, 1996).
Alexander, M., “Visualizing cleared-off desktops”, Computerworld, Computerworld, Inc., vol. XXV, No. 18, p. 20 (May 6, 1991).
Alexander, S., “Users find tangible rewards digging into datamines,” Infoworld, Infoworld Media Group, Inc., vol. 19, Issue 27, pp. 61-62 (Jul. 7, 1997).
Alpert, M., “CD-Rom: The Next PC Revolution,” Fortune, Time, Inc., 1 page (Jun. 29, 1992).
Asian MicroPatent® Representatives, at http://www.micropat.com/info.asreps.htm, 3 pages (last visited Dec. 6, 1996).
Banet, B., “Creating a CD-ROM: Overview of the Product Field,” The Seybold Report on Desktop Publishing, vol. 7, No. 6, pp. 3-31 (Feb. 1, 1993).
Becker, L.E. Jr., “Voyager kit: Ticket to books on-line,” MacWeek, vol. 7, No. 8, p. 57(2) (Feb. 22, 1993).
Berk, E. and Devlin J. (ed.), Hypertext/Hypermedia Handbook, McGraw-Hill, pp. 209-224, 285-297, 329-355, 529-533, (Feb. 1991).
Bermant, C., “Finding It Fast: New Software Features That Search Your System,” Personal Computing, pp. 125-127, 129 and 131 (Nov. 1987).
Bertelsmann Portrait, at http://www.bertelsmann.de/bag/englisch/portrait/, 1 page (n.d.).
Bish, R.C., “An essential ingredient: Post recognition processing,” Imaging World, vol. 5, Issue 3, 2 pages (Mar. 1996).
Blatt, J.J., “A Primer on User Interface Software Patents,” The Computer Lawyer, Prentice Hall Law & Business, vol. 9, No. 4, pp. 1-6 (Apr. 1992).
Boedeker, T. R. and Kashi, J.L., “Choosing Imaging Software,” Law Office Computing, vol. 5, Issue 3, pp. 50-55 (Jun./Jul. 1995).
Boolean Searching, at http://www.cris.com/˜eti/boolean.html, 1 page (last updated Jan. 12, 1996).
Bradbury, J., “Expanded Book Toolkit,” MacUser, vol. 9, No. 3, p. 85 (Mar., 1993).
Briggs, G., “CD-ROM publishing boom is Dataware's delight,” MIS Week, vol. 10, No. 38, pp. 40-41 (Sep. 25, 1989).
Briggs, G., “Dataware Comes to U.S. With CD-ROM Publishing,” MIS Week, vol. 10, No. 5, p. 21 (Jan. 30, 1989).
Brockschmidt, K., What OLE Is Really About, at http://www.microsoft.com/oledev/olecom/aboutole.htm, 59 pages (Jul. 1996).
“BRS/Search: An Indusrial Strength Document Warehouse Solution—Profile,” AberdeenGroup Profile, Aberdeen Group, Inc., 12 pages (May 1996).
BRS/SEARCH, Dataware Technologies, Inc., 4 pages (Mar. 1995).
Business Objects Announces Data Mining Partnership With DataMind Corporation, at http://www.datamindcorp.com/dmpr0520.html, DataMind Corp., 2 pages (May 20, 1996).
Business Objects to Offer Data Mining for the Masses, at http://www.businessobjects.com/company/pr/bizminprl.htm, Business Objects S.A., 2 pages (Nov. 18, 1996).
Canadian MicroPatent® Representatives, at http://www.micropat.com/info/canreps.htm, 1 page (Dec. 6, 1996).
Catchings, B. and Van Name, M.L., “Price Delineates Text-Retrieval Software,” PC Week, vol. 8, No. 20, pp. 120-123 (May 20, 1991).
Catlin, T. et al., “InterNote: Extending A Hypermedia Framework to Support Annotative Collaboration,” Hypertext '89 Proceedings, ACM, pp. 365-378, (Nov. 1989).
CD Author/CD Answer, Dataware Technologies, Inc., 2 pages (Nov. 1994).
Chan, P.P., Learning Considerations In User Interface Design: The Room Model, Master's Thesis to the Dept. of Computer Science, Faculty of Mathematics, University of Waterloo, Ontario, Canada, 52 pages (Jul. 1984).
Chapter 1: Component Object Model Introduction, at http://www.microsoft.com/oledev/olecom/Ch01.htm, Microsoft Corporation, 37 pages (1997).
CHI Research, Inc.: “Tracking the World's Technology”, at http://www.chiresearch.com, 1 page (n.d.).
CHI Research, Inc.: Technology Indicators Consulting Services and Products, at http://www.chiresearch.com/service.html, CHI Research, Inc., 2 pages (last updated Feb. 29, 1996).
Christodoulakis, S. and Graham, S., “Browsing Within Time-Driven Multimedia Documents”, ACM, pp. 219-227 (1988).
Classified Search and Image Retrieval Student Manual for the Automated Patent System (APS), U.S. Department of Commerce and U.S. Patent and Trademark Office, pp. iii-vii, 1-1—1-9, 2-1—2-23, 3-1—3-6 and 8-1—8-7 (May 7, 1991).
Cohen, R., “Browsers get BookWorm for Mac,” MacWeek, p. 4 (Oct. 4, 1993).
Competitor Assessments, at http://www.chiresearch.com/compet.html, 2 pages (last updated Feb. 29, 1996).
Conklin, J., “Hypertext: An Introduction and Survey,” Computer, IEEE, pp. 17-41 (Sep. 1987).
Cooper, D. and Clancy, M., Oh! Pascal!, W.W. Norton & Company, pp. 389-399 (1982).
Corporate Brain Mapping (R), at www.chiresearch.com/brainmap.html, 2 pages, (n.d.).
Côté, R.G. and Diehl, S., “Searching for Common Threads,” Byte, vol. 17, No. 6, pp. 290-294, 296, 298,300 and 302-305 (Jun. 1992).
Creating Value Through Knowledge Management, Conference Handout, San Francisco, California, ICM (Feb. 20-21, 1997).
“Creation/Modification of the Audio Signal Processor Setup for a PC Audio Editor”, IBM Technical Disclosure Bulletin, IMB Corp., vol. 30, No. 10, pp. 367-376 (Mar. 1988).
Curran, C., “Growing company changes data entry,” Imaging World, vol. 4, Issue 3, 2 pages (Mar. 1995).
Dataware Products and Services, at http://www.dataware.com/site/prodserv/prodserv.htm, Dataware Technologies, 1 page (1996).
Derwent Patents Citation Index, at http://www.derwent.com/products/database/pcidesc.html. 2 pages (n.d.).
DIALOG® Pocket Guide, Knight-Ridder Information, Inc., pp. 1-63, (1995).
The Digital Patent Office, SmartPatents, Inc., 4 pages (n.d.).
Dintzner, J.P. and Van Thielen, J., “Image Handling at the European Patent Office: Bacon and First Page,” World Patent Information, vol. 13, No. 3, pp. 152-154 (1991).
Doherty, “New Op-Disk Peripherals Displayed at Conference,” Electronic Engineering Times, No. 339, p. 15 (Jul. 22, 1985).
Duncan, T., “ZyIMAGE's Use of Windows Interface Falls Short of Mark,” LAN Times, pp. 70 and 79 (May 24, 1993).
Eastern Electricity: BRS/Search Customer Profile, Dataware Technologies, 1 page (Dec. 1995).
“Easy Access to Patents,” Fortune, Time, Inc., 1 page (Jun. 29, 1992).
Edvinsson, L. and Malone, M.S., Intellectual Capital: Realizing Your Compnay's True Value by Finding Its Hidden Brainpower, HarperBusiness, Feb. 15, 2002.
Essentials for Mapping Your Intellectual Property: Annuities Master Data Center, Prentice Hall Legal Practice Management, 38 pages (1993).
European MicroPatent® Representatives, at http://www.micropat.com/info/epreps.htm, 2 pages (last visited Dec. 6, 1996).
EZ-C + DE2 Images: The New Standard in Data Capture, Textware Corporation, 8 pages (1994).
Fersko-Weiss, H., “3-D Reading with the Hypertext Edge,” PC Magazine, pp. 241-242, 244, 247, 254, 257-258, 260, 263-264, 267-269, 272-273, 275 and 280-282 (May 28, 1991).
Fish, R.S. et al., “Quilt: a collaborative tool for cooperative writing,” Conference on Information Systems '88, ACM, pp. 30-37 (1988).
Forms Processing Products & Services, at http://www.textware.com/formspro.html, Textware Corporation, 3 pages (n.d.).
FormWare for Windows 95/NT, TextWare Corporation, 4 pages (1996).
Free White Paper, URL not shown, Vantive Corporation, 2 pages (n.d.).
Full Write Professional—A User's Guide, Ashton-Tate Corp., pp. 99-122 (1988).
Fuzzy Searching, at http://www.cris.com/˜eti/fuzzy.html, Executive Technologies, Inc., 1 page (last updated Jan. 12, 1996).
Gerber, C., “Lotus rolls out gateway for Notes, cc: Mail,” InfoWorld, vol. 14, No. 46, p. 1(2) (Nov. 1992).
Halasz, F. and Conklin, J., Issues in the Design of Hypermedia Systems, 67 pages (1990).
Harney, J. (ed.) “TextWare's FormWare—Complex Data Capture that Puts Simplicity First,” Imaging Magazine, 1 page (Apr. 1996).
Haskin, D., “Textware 4.0: Text Retrieval for Electronic Documents,” Computer Shopper, vol. 13, No. 8, pp. 334-335 (Aug. 1993).
Haskin, D., “ZyImage Finds Images And Text,” PC Computing, vol. 6, No. 5, p. 60 (May 1993).
Help Yourself! With PCT Patent Search On CD-ROM, MicroPatent, 4 pages (appears to be before Jul. 1, 1993).
Hip Products, at http://www.zylab.nl/zylab/p2/prods.html, ZyLAB Europe BV, 1 page (1996).
The History of MicroPatent, at http://www.micropat.com/info/history.htm, 1 page (n.d.).
Holtz, M., Mastering Ventura, Sybex, Second Edition, pp. 360-375, (1989).
How to Install and Use the USAPat Demonstration Disc, USPTO Office of Information Products Development, 4 pages (appears to be 1994).
HyperCard Basics, Apple Computer, Inc., pp. iii-iv and 1-31 (1990).
Iandiorio, J.S., “From Start to Finish: Protecting Ideas and Inventions with Intellectual Property,” Electro/95 International Professional Program Proceedings, IEEE, pp. 141-149 (Jun. 21-23, 1995).
IBM Announces Free On-Line Patent Info Service, at http://www.cmcnyls.edu/public/Bulletins,IBMPatWS.HTM, 1 page (Mar. 9, 1997).
IBM Selects RSS's Royalties Payable Solution: Real Software Systems Provides IBM with Worldwide Software Royalty Payments Solution: Application to Track 100,000 Royalty-Bearing Products, at http://www.elcamino.com/rss/7b.htm, 2 pages (Nov. 18, 1996).
“IDI brings Basis plus down to workgroups,” The Seybold Report on Publishing Systems, vol. 22, No. 14, p. 16(2) (Apr. 5, 1993).
InnerView for Windows 3.0, TMS, Inc., Version 2.2, Pre-Release #6, 129 pages (1991).
Intellectual Property Management Issues, at http://www.elcamino.com/rss/2.htm, 2 pages (1995).
Introduction to Dataware's CD-ROM Product and Services, at http://www.dataware.com/site/prodserv/cdintro.htm, 12 pages (n.d.).
Ishii, H. and Arita, K., “Clearface: Translucent Multiuser Interface for Team Work Station,” Proceedings of the Second European Conference on Computer—Supported Cooperative Work, pp. 163-174 (Sep. 25-27, 1991).
Ishii, H. and Miyake, N., “Toward an Open Shared Workspace: Computer And Video Fusion Approach Of Teamworkstation,” Communications of the ACM, ACM, vol. 34, No. 12, pp. 37-50 (Dec. 1991).
Jonckheere, C., “EPOQUE (EPO QUEry service) the Inhouse Host Computer of the European Patent Office,” World Patent Information, CEC/WIPO, vol. 12, No. 3, pp. 155-157 (1990).
Kahaner, L., Competitive Intelligence: From Black Ops to Boardrooms—How Businesses Gather, Analyze, and Use Information to Succeed in the Global Marketplace, Simon & Schuster, (1996).
Karraker, R., “Voyager Toolkit stretches Expanded Book concept to let users pen their own,” MacWeek, vol. 6, No. 11, p. 9, (Mar. 16, 1992).
Kim, W.D. and Lee, K.R., “Patent Technology Portfolio for SAW Filters,” 1994 IEEE Ultrasonics Symposium Proceedings , IEEE, vol. 1, pp. 139-142 (Nov. 1-4, 1994).
Knibbe, W., “ZyImage 2 boosts OCR, batch duties,” InfoWorld, vol. 15, Issue 51, p. 20 (Dec. 20, 1993).
Knibbe, W., “ZyImage 3.0 will facilitate distribution on CD-ROMs: Boasts integration with WordScan OCR software,” InfoWorld, vol. 16, No. 38, p. 22 (Sep. 19, 1994).
Kramer, J., “An Evaluation of the Internet as a Searching Tool for Patents and Intellectual Property: Alternative or Complementary?”, at http://www.fplc.edu/ipmall/ipcorner/evals97/ipsi97/internetpatsearch.htm, 18 pages (last visited May 8, 1998).
Kumamoto, K., “Commercial databases: the keypoints and practical use. 10. Patent and Trademark,” Joho Kanri, vol. 36, No. 10, pp. 914-938 (Jan. 1994).
Lamping, J. et al. A Focus+Context Technique Based on Hyperbolic Geometry for Visualizing Large Hierarchies, at http://www.acm.org/sigchi/chi95/electronic/—documnts/papers/jl_bdy.html, ACM, 13 pages (last visited Mar. 15, 2000).
Lougher, R. and Rodden, T., “Supporting Long-term Collaboration in Software Maintenance,” Conference on Organizational Computing Systems, ACM, pp. 228-238 (1993).
Lucas, J., “The Progress of Automation at the U.S. Patent and Trademark Office,” World Patent Information, CEC/WIPO, vol. 14, No. 3, pp. 167-172 (1992).
Lucena, J.J., Merlot Design Specification, Version 1.0—D2, 81 pages (last modified Jun. 24, 1996).
Mallory, J., “New for Mac: text/graphics retrieval software from TMS,” Newsbytes, 1 page (Jul. 2, 1992).
Manning & Napier Information Services, at http://www.mnis.net, 1 page (last visited Apr. 6, 1998).
Manning & Napier Information Services: AFCEA Intelligence Professionals Adopt New Paradigm For Information Analysis, at http://www.mnis.net/press10.shtml, 3 pages (Jun. 11, 1997).
Manning & Napier Information Services: Breakthrough in Intelligent Information Analysis From Software That Thinks Like Humans, at http://www.mnis.net/press2.shtml, 2 pages (Sep. 16, 1996).
Manning & Napier Information Services: Competitive Intelligence, at http://www.mnis.net/compete.shtml, 2 pages (last visited Mar. 23, 1998).
Manning & Napier Information Services: Competitive Intelligence Tools Migrating from Government Labs to Corporations, at http://www.mnis.net/press8.shtml, 3 pages (May 15, 1997).
Manning & Napier Information Services: Crawler Technology (Trygon), at http://www.mnis.net/trygon.shtml, 4 pages (last visited Mar. 23, 1998).
Manning & Napier Information Services: Innovative Technology Tool Unveiled: Advanced Patent Data Mining and Visualization Capabilities for Information Users, at http://www.mnis.net/press4.shtml, 2 pages (Dec. 3, 1996).
Manning & Napier Information Services: Intellectual Property,“New Standard for Patent Prior Art Searches of Computer and Software Technology,” at http://www.mnis.net/intellect.shtml, 3 pages (last visited Mar. 23, 1998).
Manning & Napier Information Services: Manning & Napier Information Services, “Turning Information into Sight,” http://www.mnis.net/press7.shtml, 4 pages (Apr. 25, 1997).
Manning & Napier Information Services: Manning & Napier Offers Broad Coverage of Computer and Software Technology Databases, at http://www.mnis.net/press5.shtml, 2 pages (Dec. 3, 1996).
Manning & Napier Information Services: Manning & Napier and RTI announce alliance for corporate information market, at http://www.mnis.net/press9.shtml, 2 pages (May 15, 1997).
Manning & Napier Information Services: MNIS Announces System for Improving Software Patents—At ABA Conference, at http://www.mnis.net/press.shtml, 3 pages (Jun. 28, 1996).
Manning & Napier Information Services: Patent Licensing Made Easier With MNIS Data Mining Tools, at http://www.mnis.net/press6.shtml, 2 pages (Jan. 30, 1997).
Manning & Napier Information Services: Turning Information Into Insight, at http://www.mnis.net/pr/press7.htm, 3 pages (Apr. 25, 1997).
Manning & Napier Information Services: Zolowizc To Head Intellectual Property Unit at Manning & Napier Information Services, at http://www.mnis.net/press3.shtml, 2 pages (Nov. 18, 1996).
MAPit: Prevent Patent Infringement with the Virtual Patent Advisor, at http://www.mnis.net/mapitdemo/, 1 page (last visited Mar. 23, 1998).
Marshall, P., “ZyImage is ZyIndex plus a scan interface integrated,” InfoWorld, vol. 15, Issue 10, p. 100 (Mar. 8, 1993).
Marshall, P., “Text retrieval alternatives: 10 more ways to pinpoint important information,” Inforworld, vol. 14, No. 12, pp. 88-89 (Mar. 23, 1992).
Marshall, P., “ZyImage adds scanning acess to ZyIndex,” InfoWorld, vol. 16, No. 15, pp. 73 and 76-77 (Apr. 11, 1994).
Marshall, P. and Watt, P., “ZyIndex for Windows, Version 5.0,” InfoWorld, vol. 15, No. 21, p. 127(4) (May 1993).
Master Data Center: PC Master Patent Lite for Windows, 9 pages (n.d.).
Master Data Center: PC Master Trademark Lite for Windows, 10 pages (n.d.).
MasterView for Microsoft Windows, TMS, Inc., 4 pages (1993).
Matazzoni, J., “Expanded Book Toolkit 1.0.1,” Macworld, vol. 10, No. 6, p. 158 (Jun. 1993).
MDC Patent Rules Update, Master Data Center, Inc., 3 pages (May 1996).
MDC Trademark Rules Update, Master Data Center, Inc., 4 pages (Apr. 1996).
Mendelson, E., “HyperWriter for Windows,” PC Magazine, vol. 14, No. 3, pp. 140 and 142-143 (Feb. 7, 1995).
Merger & Acquisition Technological Due Diligence, at http://www.chiresearch.com/due_dil.html, 2 pages (last updated Feb. 29, 1996).
MicroPatent PatentWEB and Trademark WEB Service Agreement, at http://www.micropat.com/cgi-bin/servagree, 3 pages (last visited Dec. 6, 1996).
MicroPatent: Providers of Patent and Trademark Information, at http://www.micropat.com/info/mission.htm, 1 page (last visited Dec. 6, 1996).
MicroPatent World, MicroPatent, pp. 1-4 (Spring 1991).
MicroPatent's CD-ROM Products, at http://www.micropat.com/info/about.htm, MicroPatent, 3 pages (1996).
Mogee Research and Analysis Associates: Competitive Technology Reports, at http://www.mogee.com/ctr.htm, 3 pages (1996).
Mogee Research and Analysis Associates: Competitive Technology Report: Global Positioning System (GPS) Technology, at http://www.mogee.com/gps.htm, 3 pages (1996).
Moore, A., “The Forms Processing Paradigm Shift,” Imaging Magazine, 2 pages (Mar. 1995).
Moore, J., “Dataware lands $6.6M GPO pact,” Federal Computer Week,, vol. 9, No. 27, pp. 84 and 86 (Sep. 11, 1995).
Narin, F., Presentation Figures: In the Realm of Technology, Asia Looms Ever Larger: Patent Citation as Measures of Corporate and National Strength, Presented at Stanford University, Asia/Pacific Research Center, Stanford, California, 22 pages (Oct. 29, 1992).
NetAnswers: Organizations Worldwide Take Content Onto the Web with NetAnswer, Dataware Technologies, pp. 1-4 (Spring 1996).
NetAnswer™ Hosting Service, Dataware Technologies, Inc., 4 pages (Oct. 1995).
NetAnswer™: Information Super Server for the World Wide Web, Dataware Technologies, Inc., 4 pages (Oct. 1995).
Mogee Research and Analysis Associates: Competitive Technology Report: Medical Implants, at http://www.mogee.com/mi.htm, 3 pages (1996).
Mogee Research and Analysis Associates: Consulting Services, at http://www.mogee.com/consult.htm, 6 pages (1996).
Mogee Research and Analysis Associates: Data Resources, at http://www.mogee.com/data.htm, 5 pages (1996).
Mogee Research and Analysis Associates: “International Technology Monitoring and Competitive Assessment,” at http://www.mogee.com, 2 pages (1996).
Mogee Research and Analysis Associates: Who We Are: Company Information, at http://www.mogee.com/whower_1.htm, 3 pages (1996).
Mogee Research and Analysis Associates: Who We Are: Personnel Biographies, at http://www.mogee.com/whower_2.htm, 3 pages (1996).
“‘New Wave’ MetricsWare—Metrics Software You Just Gotta Have”, IT Metrics Strategies (Reprint), Cutter Information Corp™, vol. II, No. 10, pp. 1-4 (1996).
OmniPage Professional Reference: Windows Version 5, Caere Corporation, pp. 1-1 to 1-70, 3-1 to 3-20, 6-1 to 6-8 and Glossary pp. 1-8 (1988-1993).
OmniPage Professional Tutorials: Windows Version 5, Caere Corporation, pp. 1-1 to 1-34, 2-1 to 2-26, and 3-1 to 3-14 (1988).
Ores, P., “Hypertext Publishing: Edit Trail,” PC Magazine, vol. 14, No. 3, pp. 132, 134, 136, and 138 (Feb. 7, 1995).
Otake, Y., “Information each department in corporate needs from the standpoint of R&D department,” Joho Kanri, vol. 34, No. 7, pp. 635-646 (Oct. 1991).
Patent Abstracts of Japan—Now on CDROM, at http://www.netaxs.com/˜aengel/PAJ/PAJInfo.html, 2 pages (last updated Dec. 22, 1995).
Patent Searching and Document Delivery Resources, at http://www.micropat.com/info/websrch.htm, MicroPatent, 1 page (1996).
PatentQuery: Search & Deliver, at http://www.micropat.com/info/prelegal.htm, 1 page last visited (Dec. 6, 1996).
Patents on CD-ROM, MicroPatent USA, 10 pages (appears to be before Sep. 1, 1992).
PC Master Lite . . . The Affordable Solution!, Master Data Center Intellectual Property Software and Services, 8 pages (1996).
Pelham,, A., “A Wave of the Wand for Litigators, Tools of the Trade Go High-Tech,” Legal Times, 2 pages (Jan. 24, 1994).
Perenson, M.J., “Retrieving Text on the Net,” PC Magazine, vol. 14, No. 20, p. 61 (Nov. 21, 1995).
Performance Management: The Way It Should Be . . . , Panorama Business Views, Inc., 19 pages (n.d.).
“Personal Text-Retrieval Software Works with Calera's WordScan,” PC Magazine, vol. 14, No. 2, p. 68 (Jan. 24, 1995).
Platinum technology and Sybase Inc. Expand Partnership to Deliver Wider Selection of Data Warehouse Solutions, at http://www.platinum.com/press/1996/dw_sybas.htm, Platinum Technology, Inc., 3 pages (Jun. 11, 1996).
Quattro® Pro User's Guide, Borland International, Inc., pp. 240-245 (1987).
Rappaport, I., “Time To Count Your Patents The Way You Would Beans”, PCWeek, vol. 14, No. 2, 2 pages (Jan. 13, 1997).
“re: Search V. 2.6,” Computer Select, 1 page (Nov. 1993).
REAL Software Systems, Inc.: Alliant Participation Management & Accounting, at http://www.elcamino.com/rss/3b.htm, Real Software Systems, Inc., 4 pages (1995).
REAL Software Systems, Inc.: Home Video & Title Based Distribution, at http://www.elcamino.com/rss/3d.htm, Real Software Systems, Inc., 3 pages (1995).
REAL Software Systems, Inc.: Rights Licensing, at http://www.elcamino.com/rss/3c.htm, REAL Software Systems, Inc., 3 pages (1995).
REAL Software Systems, Inc.: Royalties Payable, at http://www.elcamino.com/rss/3a.htm, REAL Software Systems, Inc., 4 pages (1995).
REAL Software Systems, Inc.: Solutions for Managing Intellectual Property, at http://www.elcamino.com/rss/, REAL Software Systems, Inc., 2 pages (1995).
Rooney, P., “Text-retrieval veterans prepare Windows attach,” PC Week, vol. 9, No. 24, p. 46 (Jun. 15, 1992).
Rooney, P., “ZyLab partners with Calera: firms roll out document-image system,” PC Week, vol. 10, No. 3, p. 22 (Jan. 25, 1993).
Samtani, R., Following the Money: Managing Intellectual Property in the Digital Age, at http://www.elcamino.com/rss/7a.htm, REAL Software Systems, Inc., 5 pages (1995).
Schroeder, E., “Low Price Point Is Key for Buyers Of Text Databases,” PC Week, vol. 8, No. 20, pp. 120 and 122 (May 20, 1991).
Schroeder, E., “Multimedia offerings target expanded platform support,” PC Week, vol. 10, No. 13, pp. 59 and 73 (Apr. 5, 1993).
Schwartz, E., “Dataware Plants CD-ROM Seeds,” Computer Systems News, p. 33 (Feb. 6, 1989).
Search Results from Dialog Search for MicroPatent for News Releases and Corporate Announcements Relating to APS, FullText, PatentImages, Espace, Dialog Files: 148, 479 and 648, 13 pages (1989-1991).
Sibley, J.F., “STN,” World Patent Inforamtion, Elsevier Publishing, vol. 19, No. 1, pp. 73-75 (Nov., 1996).
Sibley, J.F., “The EPOQUE Suite of Applications,” World Patent Information, Elsevier Science Ltd., vol. 18, No. 3, pp. 141-148 (1996).
Simon, B., “ZyImage: A Winning Combination of OCR And Text Indexing,” PC Magazine, vol. 12, No. 6, p. 56 (Mar. 30, 1993).
Simpson, A., Mastering WordPerfect 5.1 & 5.2 for Windows, SYBEX Inc., pp. 58-60 (1993).
SmartPatent Quarterly Newsletter, SmartPatents, Inc., vol. 2, No. 3, pp. 1-6 (Winter 1996-1997).
SmartPatent Quarterly Newsletter, SmartPatents, Inc., vol. 2, No. 4, pp. 1-6 (Spring/Summer 1997).
Solutions For Managing Intellectual Property, at http://www.elcamino.com/rss/3.htm, REAL Software Systems, Inc., 2 pages (1995).
Specialized Services, at http://www.elcamino.com/rss/4.htm, REAL Software Systems, Inc., 2 pages (1995).
Spencer, H., “Tijuana data entry shop logs 500K forms/day,” Imaging World, vol. 4, Issue 4, 2 pages (Apr. 1995).
Spitzer, T., “Needles in Document Haystacks” DBMS, Miller Freeman, vol. 9, No. 1, pp. 84-87 (Jan. 1996).
Stewart, T.A., “Getting Real About Brainpower”, Fortune, vol. 132, No. 11, pp. 201-203 (Nov. 27, 1995).
Stewart, T.A., Intellectual Capital: The New Wealth of Organizations, Doubleday, (1997).
Stewart, T.A., “Mapping Corporate Brainpower”, Fortune, vol. 132, No. 9, pp. 209, 210 and 212 (Oct. 30, 1995).
Stewart, T.A., “Trying To Grasp the Intangible,” Fortune, vol. 132, No. 7, pp. 157-159 (Oct. 2, 1995).
Stewart, T.A., “Your Company's Most Valuable Asset: Intellectual Capital,” Fortune, vol. 130, No. 7, pp. 68-72 and 74 (Oct. 3, 1994).
Tech-Line CD: Indicators of Technologies Excellence Manual including Introduction to Company Evaluation Using Technology Indicators, Bertelsmann Informations Service, CHI Research Inc., TT-Technologie-Transfer GmbH, 68 pages (34 pages copied double sided) (1994).
Sullivan, K.B., “Dataware's CD Author System To Boast Hypertext Capability,” PC Week, vol. 8, No. 31, pp. 31-32 (Aug. 5, 1991).
Tech-Line® CD User Manual: Abridged Version for the World Wide Web, at http://www.chiresearch.com/httlusel.html#overview, CHI Research, Inc. and Technologie-Transfer GmbH, 3 pages (1995).
Text Retrieval Products & Services, at http://www.textware.com/txtrtrvl.html, TextWare Corporation, 2 pages (last visited Oct. 29, 1996).
Textware Corporation, at http://www.textware.com, TextWare Corporation, 1 page (1996).
TextWare: Instant Information Access, TextWare Corporation, 2 pages (1995).
TextWare: Pricing, TextWare Corporation, 2 pages (Mar. 26, 1996).
“TMS Announces Contract With Major Insurance Information Provider,” Business Wire, Business Wire Inc., 2 pages (Feb. 11, 1991).
“TMS Announces Easy View Available for CD-ROM Publishers,” Business Wire, Business Wire Inc., 1 page (Mar. 9, 1992).
“TMS Announces Release of Inner View 2.1 Software,” Business Wire, Business Wire Inc., 2 pages (Mar. 18, 1991).
Torgan, E.A., “ZyImage: Document Imaging and Retrieval System,” PC Magazine, vol. 12, No. 3, p. 62 (Feb. 9, 1993).
Toshiba America Information Systems: CD-ROM Customer Profile, Dataware Technologies, 1 page (Sep. 1995).
Total Recall®, Dataware Technologies, 2 pages (Jun. 1995).
Tredennick, Jr., J.C., “Full-Text Search and Retrieval_Winning Big With Computers,” Law Practice Management, American Bar Association, vol. 19, No. 8, pp. 33-37 (Nov./Dec., 1993).
Tribute, A., “Searching CeBit for publishing products; Power Mac draws the crowds at Hannover show,” The Seybold Report on Publishing Systems, vol. 23, No. 15, pp. 5-8 (Apr. 22, 1994).
Ueda, H., et al., “Impact: An Interactive Natural-Motion-Picture Dedicated Multi-Media Authoring System,” ACM, pp. 343-350 (Mar. 1991).
United States MicroPatent® Representatives, at http://www.micropat.com/info.usreps.htm, 2 pages (last visited Dec. 6, 1996).
Universal Selects RSS To Provide Worldwide Television Licensing Solution: Application to Track All Domestic Network, Syndication and International Sales Agreements, at http://www.elcamino.com/rss/7c.htm, 2 pages (Apr. 30, 1997).
Voyager: cd-rom catalog, Voyager, pp. 1-79 (42 pages) (1996-1997).
Voyager cd-roms, Voyager, 68 pages (Spring 1996).
ISTA, at http://www.netaxs.com/˜aengel/ista.htm, 1 page (last visited Dec. 31, 1996).
Welcome to MicroPatent's PatentWEB™. . . for Patent Information, at http://www.micropat.com/info/welcom.htm, 1 page (last visited Dec. 6, 1996).
Welcome to the MicroPatent PatentWEB, at http://www.micropat.com/patentwebindex.htm, MicroPatent, 1 page (1996).
What our customers say about us., at http://www.elcamino.com/rss/5.htm, REAL Software Systems, Inc., 2 pages (1995).
Where will we be?, at http://www.micropat.com/info/shows.htm, MicroPatent, 1 page (1996).
Why should YOU be interested in Patent Information?, at http://www.micropat.com/info/interested.htm, MicroPatent, 1 page (last visited Dec. 6, 1996).
Wiggins, R.W., “Networked Hypermedia: The World-Wide Web and NCSA Mosaic”, The Internet for Everyone—A Guide for Users and Providers, McGraw-Hill, Inc., pp. 245-290 (1995).
Williams, J. and Ebe, T., “STN Easy: point-and-click patent searching on the World Wide Web,” World Patent Information, Elsevier Publishing, vol. 19, No. 3, pp. 161-166 (1997).
WorldPerfect Workbook for IBM Personal Computers, WordPerfect Corporation, Version 5.0, pp. 24 and 108-109 (1998).
WORLDOX™: The Complete Document Profiling and Retrieval System for Windows, World Software Corporation, 8 pages (1992).
“WorldView (V. 1.1) and WorldView Press (V. 1.0.2),” Computer Select, 2 pages (Nov. 1993).
Young, M., “UK Police Put Criminals On-Line With New National Computer,” Imaging Magazine, TextWare Corporation, 2 pages ( Aug. 1995).
ZyIMAGE: Archive Text Fast, at http://www.zylab.nl/zylab/p2/zyimage.html, ZyLAB International, Inc., 1 page (1996).
ZyIMAGE: Common Questions Asked About ZyIMAGE, at http://www.zylab.nl/zylab/p2/zyimagefaq.html#input, ZyLAB Europe BV, 6 pages (1996).
ZyIMAGE Web Server: Powerful Imaging and Full Text Retrieval for Publishing On-Line, at http://www.zylab.nl/zylab/p2/zyimageweb.html, ZyLAB Europe BV, 1 page (1996).
ZyINDEX 5.2 for Windows, ZyLAB, 4 pages (1994).
ZyINDEX Developer's Toolkit Version 5.0 for Windows: Programmers Guide, Information Dimensions, 38 pages, (1992).
ZyINDEX for Windows: User's Guide, Information Dimensions, Inc., pp. ii-v, 1-5, 8-13, 15-20 and 22, 23, 25-262 (Jul. 1992).
ZyLAB: The Full Text Retrieval & Publishing Experts, ZyLAB Europe BV, 2 pages (1996).
“ZyLab Retrieval engine optimized for CD-ROM; Zylag, Progressive Technologies merge,” Seybold Report on Desktop Publishing, vol. 8, No. 10, p. 40 (Jun. 6, 1994).
English Language Abstract of ‘Kumamoto, K., “Commercial databases: the keypoints and practical use. 10. Patent and Trademark,” Joho Kanri, vol. 36, No. 10, pp. 914-938 (Jan. 1994),’ 1 page, printed from Dialog Inspec database.
English Language Abstract of ‘Otake, Y., “Information each department in corporate needs from the standpoint of R&D department,” Joho Kanri, vol. 34, No. 7, pp. 635-646 (Oct. 1991,’ 1 page, printed from Dialog Inspec database.
English Language Abstract of Japanese Publication No. 08-221435, 1 page, printed from the JPO PAJ webpage at http://wwwl.ipdl.jpo.go.jp (Aug. 30, 1996—date of publication of application).
English Language Abstract of Japanese Publication No. 05-135109, 1 page, printed from the JPO PAJ webpage at http://www1.ipdl.jpo.go.jp (Jun. 1, 1993—date of publication of application).
English Language Abstract of Japanese Publication No. 06-231141, 1 page, printed from the JPO PAJ webpage at http://www1.ipdl.jpo.go.jp (Aug. 19, 1994—date of publication of application).
Narin et al., “Technological performance assessments based on patent and patent citations”, IEEE, vol. (EM-31), No. 4, pp. 172-183, (Nov. 1994).
Stefanov, V., “Some Possibilities of a ‘Patents’ Database in Determining a Firm's Policy,” World Patent Information, vol. 17, No. 3, pp. 201-204 (Sep. 1995).
Related Documents
Continuation of application No. US 08/921369 00, filed on 29-Aug-1997, now Pat. No. US 6339767 A.
Examiners
Primary:
Robinson, Greta L.
Attorney, Agent or Firm
Sterne, Kessler, Goldstein & Fox, PLLC
Supplemental Information (Source: DOCDB)
Inventors
RIVETTE KEVIN G
[+10]
US
RAPPAPORT IRVING S
US
HOHMANN LUKE
US
PUGLIA DAVID
US
GORETSKY DAVID
US
JACKSON ADAM
US
RABB JR CHARLES
US
SMITH DAVID W
US
PARK BRIAN
US
THORNTHWAITE WARREN
US
NAVARETTE JORGE A
US
Assignees/Applicants
AURIGIN SYSTEMS INC
US
Classifications
International (2006.01):
G06Q 10/00; G06F 17/30
International:
G06F 17/30
European:
G06F 17/30T6C
Also Published As
| CA 2292500 A1 | application | System, method and computer program product for patent-centric and group-oriented data processing, including using hyperbolic trees to visualize data |
| EP 0986789 A1 | application | System, method, and computer program product for patent-centric and group-oriented data processing, including using hyperbolic trees to visualize data |
| JP 2002-502529 A | application | [JP 2002-502529 A] |
| US 2002/0007373 | application | System, method, and computer program product for knowledge management |
| EP 0986789 B1 | patent | System, method, and computer program product for patent-centric and group-oriented data processing |
| EP 0986789 B2 | patent | System, method, and computer program product for patent-centric and group-oriented data processing |
| US 7797336 | patent | System, method, and computer program product for knowledge management |
Preview up to the first 8 page images of this publication.
--- Page 1 ---
--- Page 2 ---
--- Page 3 ---
--- Page 4 ---
--- Page 5 ---
--- Page 6 ---
--- Page 7 ---
--- Page 8 ---
(Source: USPTO)
CROSS-REFERENCE TO RELATED APPLICATIONS
The present Application is a Continuation Application of U.S. Utility patent appl. Ser. No. 08/921,369, filed on Aug. 29, 1997 now U.S. Pat. No. 6,339,767 (pending), titled “Using Hyperbolic Trees to Visualize Data Generated by Patent-Centric and Group-Oriented Data Processing,” which is a Continuation-in-Part Application of appl. Ser. No. 08/867,392, filed on Jun. 2, 1997 now U.S. Pat. No. 5,991,751 (patented), titled “System, Method, and Computer Program Product for Patent-Centric and Group-Oriented Data Processing,” (incorporated herein by reference in its entirety).
BACKGROUND OF THE INVENTION
1. Field of the Invention
The present invention is generally related to tools for data processing, and more particularly related to tools for patent-centric and group-oriented data processing. These tools comprise diverse capabilities for data presentation and processing, including data presentation and processing using hyperbolic trees.
2. Related Art
Patents are becoming more and more important to a business's success, especially in today's global economy. Patents can be viewed as a new type of currency in this global economy because they grant the holder with a right to exclude others from making, using, or selling the patented technology. In some industries, product turnover is fairly rapid. However, core technology, product features, and markets change at a much slower rate. Accordingly, even in fast-moving industries, patents which cover core technology are very valuable at protecting a company's research and development investment for an extended period of time.
Patents are also valuable as revenue generators. In 1993, for example, the revenue generated from patents by U.S. companies was over $60 billion. Fred Warshofsky, The Patent Wars, John Wiley & Sons, Inc., New York, 1994. These patent revenue dollars are rising each year.
Patents are further valuable because they collectively represent a vast technological database. Much of this database is only available as issued patents (i.e., it is not released in any other form). According to Larry Kahaner's book, Competitive Intelligence, Simon & Schuster, 1996, “More than 75 percent of the information contained in U.S. patents is never released anywhere else.”
If corporations searched this database before developing and releasing new products they might be able to avoid costly patent infringement litigation. Often, however, corporations do not conduct such patent searches. One significant reason for this is the difficulty in identifying relevant patents, and the difficulty in analyzing patents. Computerized search tools are becoming available to the public, such as web sites on the Internet, that can be used to conduct patent searches. Many companies and practitioners are reluctant to use such tools, however, due to the concern that their highly sensitive patent searches will not be maintained in confidence when using such tools.
More and more corporations are recognizing the value of patents. The number of patents applied for and issued to U.S. companies is increasing every year, especially in fast moving industries such as computer software and biotechnology. Many international companies have also recognized the value of patents. In fact, foreign companies regularly rank among the leaders in issued U.S. patents.
Of course, not all patents are as valuable to the patent owner or patent licensees as others. Some owned or licensed patents provide little or no value to the corporate entity. These patents become a drain on corporate resources, both in obtaining the patents, paying maintenance fees, and paying license fees. It is difficult for corporations to assess the value of their patents because automated tools for patent analysis do not exist.
Yet, for all the heightened awareness being paid to patents in some quarters, patents remain one of the most underutilized assets in a company's portfolio. This is due, at least in significant part, to the fact that patent analysis, whether for purposes of licensing, infringement, enforcement, freedom to operate, technical research, product development, etc., is a very difficult, tedious, time consuming, and expensive task, particularly when performed with paper copies of patents.
Software providers have been slow in developing software tools for aiding in the patent analysis process. As a result, there are few automated tools for patent analysis currently available. There are software tools available for managing corporate patent prosecution and payment of maintenance fees, such. as products from Master Data Corporation. The patent analysis capabilities of these tools are limited. These tools, for example, cannot be used to facilitate the analysis and development of business strategies to increase corporate shareholder value through the strategic and tactical use of patents.
A number of patent searching tools are available, such as the United States Patent and Trademark Office (USPTO) Automated Patent System (APS), and the on-line search services offered by Lexis and Westlaw. Other providers of patent information and patent search tools include Derwent, MicroPatent, Questel, Corporate Intelligence, STN, IFI/Plenum, The Shadow Patent Office (EDS), IBM, and CAS. These tools are not analysis tools. Instead, they are search tools. These tools enable a user to identify patents that satisfy a specified key word search criteria. In essence, these tools provide the user with the ability to possibly find “the needle-in-the-haystack.” However, these tools have limited, if any, automated functions to aid a user in analyzing the patents, whether the company's own patents or those of competitors, for the purpose of making tactical and strategic business decisions based on the patents.
SmartPatents Inc. (SPI) of Mountain View, Calif., provides electronic tools for analyzing patents. These tools, collectively called the SmartPatent Workbench, are very useful for analyzing patents. With the SmartPatent Workbench, a user can view the text and image of a patent, conduct text searches in the patent, copy and paste portions of the patent to other documents, build a case of patents, annotate the case and the patents in the case, import and export patents and cases, etc. The SmartPatent Workbench is commercially available from SPI, and is described in a number of publicly available documents, such as U.S. Pat. No. 5,623,679 and U.S. Pat. No. 5,623,681, incorporated by reference herein.
The SmartPatent Workbench is a patent analysis tool. The SmartPatent Workbench is primarily designed to assist a user in working with a single patent or a small collection of patents at a time. However, there are many instances when it would be very beneficial to be able to automatically and simultaneously analyze, correlate, or otherwise process multiple patents.
For example, in some instances it would be beneficial to automatically analyze the inventorship of a collection of patents. More particularly, it would be beneficial to identify the persons who are named most frequently on a collection of patents. It would be very useful if this task could be performed automatically. However, no existing software tools can perform this task automatically.
For the most part, existing patent-related tools can process only the information contained in patents. (It is noted, however, that the SmartPatent Workbench has functions to annotate patents with any information, whether or not patent related, and has additional functions to search within annotations.) These tools do not have functions for correlating, analyzing, and otherwise processing patent-related information with non-patent related information, including but not limited to corporate operational data, financial information, production information, human resources information, and other types of corporate information. Such non-patent information is critically important when evaluating the full strategic and tactical value and applicability of any given patent, or developing a corporate patent business strategy for gaining competitive advantage and increasing shareholder value based on patents.
Consider, for example, FIG. 1. A typical corporation 102 includes a research and development (R&D) department 104, a finance department 112, a manufacturing department 108, and a legal department 116 (that includes a licensing department 122 and a patent department 124). In the course of performing their respective duties, these departments generate, collect, and maintain information, such as R&D information 106, financial information 114, manufacturing information 110 (such as bill of material information), licensing information 118, and patent information 120 (that includes the patents obtained by the company, and perhaps patents obtained by competitors).
A business analyst 126 may be assigned the job of evaluating the value of the corporation's patent portfolio (represented as part of the patent information 120). In order to fully and accurately analyze the value and applicability of the corporation's patent portfolio, the analyst 126 should ideally take into account non-patent information, such as R&D information 106, financial information 114, manufacturing information 110, and licensing information 118.
For example, a patent's value may be linked to whether it covers technology that the corporation is currently using, or that the corporation may use in the future. Thus, an analysis of the patent should include an analysis of and correlation with manufacturing information 110 and R&D information 106. Also, a patent's value may be linked to whether it has generated licensing revenue. Thus, an analysis of the patent should include an analysis of and correlation with licensing information 118. Further, a patent's value may be linked to the degree of success of the corporation's commercial products that correspond to the patent (i.e., the commercial embodiments of the patented technology). Thus, an analysis of the patent should include an analysis of and correlation with financial information 114.
The processing described above, however, is usually not done (or it is done in an ad hoc, unorganized, incomplete, inefficient, and/or ineffective manner) because it is difficult or, in many cases, impossible to manually collect, organize, correlate, and process all of the information pertinent to the patents under study. Often times, it is a difficult or even impossible task to simply identify the relevant patents. Accordingly, it would be very beneficial to have automated tools that automatically process patent-related information and non-patent related information for making corporate business decisions. Existing patent-related tools do not have this capability.
SUMMARY OF THE INVENTION
Briefly stated, the present invention is directed to a system, method, and computer program product for processing data. The present invention maintains first databases of patents, and second databases of non-patent information of interest to a corporate entity.
The present invention also maintains one or more groups. Each of the groups comprises any number of patents from the first databases. The present invention, upon receiving appropriate operator commands, automatically processes the patents in one or more of the groups in conjunction with non-patent information from the second databases. Accordingly, the present invention performs patent-centric and group-oriented processing of data.
A group can also include any number of non-patent documents.
The groups may be defined by the business practices of the corporation and could include groupings that are product based, person based, corporate entity based, or user-defined. Other types of groups also fall within the scope of the invention. For example, the invention supports temporary groups that are automatically generated in the course of the automatic processing performed by the invention.
The processing automatically performed by the invention relates to (but is not limited to) patent mapping, document mapping, document/patent citation (both forward and backward), document/patent aging, patent bracketing/clustering (both forward and backward), inventor patent count, inventor employment information, and finance. Other functions also fall within the scope of the invention.
The present invention includes the ability to display data in a wide range of formats, including the ability to display and process data using hyperbolic trees.
Further features and advantages of the invention, as well as the structure and operation of various embodiments of the invention, are described in detail below with reference to the accompanying drawings. In the drawings, like reference numbers generally indicate identical, functionally similar, and/or structurally similar elements. The drawing in which an element first appears is indicated by the leftmost digit(s) in the corresponding reference number.
BRIEF DESCRIPTION OF THE FIGURES
The present invention will be described with reference to the accompanying drawings, wherein:
FIG. 1 represents the generation and maintenance of documents in a conventional corporate entity;
FIG. 2 illustrates the document-centric and patent-centric operation of the present invention;
FIG. 3 is a block diagram of a system according to a preferred embodiment of the present invention;
FIG. 4 is a block diagram of an enterprise server according to a preferred embodiment of the present invention;
FIG. 5 illustrates a potential deployment of the enterprise server of FIG. 4;
FIG. 6 is a block diagram of the databases of the present invention;
FIG. 7 is a block diagram of a network client (and potentially a web client) according to an embodiment of the invention;
FIG. 8 is a block diagram of a web server according to an embodiment of the invention;
FIG. 9 is a block diagram and a data transfer diagram illustrating the searching features of the present invention;
FIG. 10 is a block diagram of the analysis modules which form a part of the enterprise server of FIG. 4;
FIG. 11 is a block diagram of a computer useful for implementing components of the invention;
FIG. 12A illustrates the orientation of FIGS. 12B-12M relative to one another;
FIGS. 12B-12M illustrates the tables and attributes in the databases of FIG. 6 according to an embodiment of the invention;
FIGS. 13-17 illustrate example document databases;
FIG. 18 illustrates an example display format depicting the hierarchical organization of groups according to the present invention;
FIGS. 19-21 illustrates example group tables;
FIGS. 22 and 23A illustrate example bill of materials (BOM) data structures (also called BOM structures, or BOMs);
FIG. 23B, when considered in conjunction with FIG. 23A, illustrate the concept of shared groups;
FIGS. 24-26 illustrate example BOM groups;
FIGS. 27-31 illustrate example security tables;
FIG. 32 illustrates an example corporate organizational structure;
FIGS. 33-36 illustrate example corporate entity databases;
FIG. 37 illustrates an example person table;
FIG. 38 illustrates an example employee table;
FIG. 39 illustrates an example validated inventor table;
FIGS. 40-43, 44A and 44B illustrate example patents used to describe the patent bibliographic databases;
FIG. 45 is a dataflow diagram illustrating a generic extract and load operation;
FIG. 46 is a dataflow diagram illustrating an exemplary extract and load process for the patent bibliographic databases;
FIG. 47 is a dataflow diagram illustrating an exemplary extract and load process for the BOM databases;
FIG. 48 illustrates an alternative process for obtaining corporate BOM data;
FIG. 49 is a dataflow diagram representing an exemplary process for extract and load of the person databases and the employee databases;
FIG. 50 is a dataflow diagram illustrating an exemplary process for extract and load of the validated inventor table;
FIG. 51 is a dataflow diagram illustrating an exemplary process for extract and load of the corporate entity databases;
FIG. 52 is a dataflow diagram illustrating an exemplary process for extract and load of other corporate entity databases;
FIGS. 53-57 illustrate example user interface display formats pertinent to the searching features of the present invention;
FIG. 58 is an example user interface display format pertinent to display of group information;
FIGS. 59-60 are examples of patent mapping display formats;
FIGS. 61-65 are examples of patent citation report display formats;
FIGS. 66-70 are examples of patent aging display formats;
FIGS. 71A, 71B, and 72-Θare examples of patent clustering/bracketing display formats;
FIGS. 74-77 are examples of inventor patent count display formats;
FIGS. 78-80 are examples of employment information display formats;
FIG. 81 illustrates the interaction between the enterprise server and a client;
FIG. 82 illustrates the interaction between the enterprise server and a network client;
FIG. 83 illustrates the interaction between the enterprise server and a web client;
FIG. 84 is a flowchart depicting the operation of the patent mapping module according to the embodiment of the invention;
FIG. 85 is a flowchart depicting the operation of the patent/document mapping module according to an embodiment of the invention;
FIG. 86 is a flowchart depicting the operation of the patent citation module when conducting a backward patent citation search according to an embodiment of the invention;
FIG. 87 is a flowchart depicting the operation of the patent citation module when performing a forward patent citation search according to an embodiment of the invention;
FIGS. 88A and 88B collectively illustrate a flowchart representing the operation of the patent aging module according to an embodiment of the invention;
FIG. 89 is a flowchart representing the operation of the patent bracketing/clustering module when performing a backward patent bracketing/clustering function according to an embodiment of the invention;
FIG. 90 is a flowchart illustrating the operation of the patent bracketing/clustering module when performing a forward patent bracketing/clustering function according to an embodiment of the invention;
FIG. 91 is a flowchart depicting the operation of the inventor patent count module according to an embodiment of the invention;
FIG. 92 is a flowchart depicting the operation of the inventor employment information module according to an embodiment of the invention;
FIG. 93 is a flowchart depicting the operation of the importing patent data module according to an embodiment of the invention;
FIG. 94 is a flowchart depicting the operation of the exporting patent data module according to an embodiment of the invention;
FIG. 95 is a flowchart representative of a generic extract and load process according to an embodiment of the invention;
FIG. 96 is a flowchart of a extract and load process for the patent bibliographic databases;
FIG. 97 is a flowchart of a extract and load process for the BOM databases;
FIG. 98 is a flowchart of a extract and load process for an employee databases;
FIG. 99 is a flowchart of a extract and load process for the validated inventor databases;
FIG. 100 is an extract and load flowchart for the corporate entity databases;
FIG. 101 is a flowchart representative of the interaction between a client and the enterprise server;
FIG. 102 is a flowchart representative of a patent mapping and mining process;
FIG. 103 is a flowchart representative of a situation assessment process;
FIG. 104 is a flowchart representative of a competitive analysis process;
FIG. 105 is a flowchart representative of a clustering and/or bracketing process;
FIG. 106 is a flowchart representative of an inventor analysis process;
FIG. 107 is a flowchart representative of a financial analysis process;
FIG. 108 is a flowchart representative of a strategic planning process;
FIG. 109 is a flowchart representative of an example methodology process involving patent mapping and mining, situation assessment, and strategic planning process;
FIG. 110 is a flowchart depicting the operation of the security module;
FIG. 111 is an example display format showing the display of patent text in a first window and notes in a second window;
FIG. 112 is an example display format showing the display of patent text in a first window and patent image in a second window;
FIG. 113 illustrates a block diagram of the virtual patent system of the present invention;
FIG. 114 is a architecture block diagram of the network client (and in some embodiments the web client);
FIG. 115 is used to describe a generic group import function of the present invention;
FIG. 116 is an example user login screen shot;
FIGS. 117 and 118 represent an example console screen shot;
FIGS. 119 and 120 are screen shots for creating a new group;
FIGS. 121 and 122 are example screen shots for searching through the databases;
FIGS. 123 and 124 are example screen shots for displaying text and images of documents;
FIG. 125 is an example screen shot for creating a document note;
FIGS. 126 and 127 are example screen shots for editing group properties;
FIGS. 128 and 129 are example screen shots for invoking patent-centric and group-oriented functions;
FIG. 130 is an example screen shot for adding a document to a group;
FIG. 131 is an example screen shot for importing data;
FIG. 132 is an example screen shot for exporting data;
FIG. 133 is another example console screen shot;
FIG. 134 is an example screen shot for creating a group note;
FIGS. 135-137 illustrate example tools bars from the console screen display;
FIG. 138 illustrates a search hierarchy used to describe the searching algorithm according to a preferred embodiment of the present invention;
FIG. 139 is a flowchart depicting the operation of the present invention when performing searches according to an embodiment of the invention;
FIG. 140 illustrates an example Patent Search screen according to an embodiment of the invention;
FIGS. 141-143 illustrate example Search Result screens according to an embodiment of the invention;
FIG. 144 illustrates an example display screen that shows bibliographic and abstract information on a document that is not stored in the repository;
FIGS. 145A, 145B, and 145C illustrate an example display screen that shows information on a document that is stored in the repository;
FIG. 146 illustrates an example display screen used to illustrate the hyperlinking capabilities of the present invention;
FIG. 147 illustrates an example “Patents In Repository” screen;
FIG. 148 illustrates an example display screen corresponding to the Skim Images function of the present invention;
FIG. 149 is a flowchart depicting a demand paging algorithm according to an embodiment of the invention;
FIG. 150 illustrates a URL message format;
FIG. 151 illustrates the commands that are transferred between a browser in the web client and the Enterprise server;
FIG. 152 illustrates the interaction between the browser in a web client and the Enterprise server;
FIG. 153 illustrates a stacked folder icon used to represent shared groups;
FIG. 154 illustrates an example console used to describe shared groups;
FIG. 155 illustrates an example console used to describe temporary groups;
FIG. 156 illustrates a group links tab that lists a group's links in the group hierarchy;
FIGS. 157-160 are flowcharts representing the operation of the patent citation tree function when performed by a network client interacting with the enterprise server;
FIG. 161 is an example console used to illustrate the operation of the patent citation tree function;
FIG. 162 is an example drop-down menu used to illustrate the manner in which an operator selects the citation analysis function;
FIG. 163 is an example dialog box used to indicate how an operator defines a citation analysis command;
FIG. 164 illustrates an example patent citation tree;
FIG. 165 illustrates an example display that is generated when an operator selects a patent represented in the patent citation tree of FIG. 164;
FIGS. 166 and 167 are flowcharts representing the operation of the patent citation tree function when performed by a web client interacting with the enterprise server via the web server;
FIGS. 168-170 are flowcharts illustrating the operation of the patent claims tree function;
FIG. 171 illustrates an example patent claims tree;
FIGS. 172 and 173 illustrate example displays which are presented when the operator selects a claim represented in the patent claims tree of FIG. 171;
FIGS. 174 and 175 are additional patent citation visualizations according to embodiments of the invention;
FIG. 176 is a flowchart representing additional operation related to the patent citation tree function;
FIGS. 177 and 178 illustrate example hyperbolic trees;
FIG. 179 represents the mapping from a graph to a tree;
FIG. 180 represents an example parent/child table;
FIG. 181 illustrates a citation analysis graph corresponding to the patent/child table of FIG. 180;
FIG. 182 illustrates an example patent bibliographic information table;
FIG. 183 illustrates an example tree corresponding to the citation analysis graph of FIG. 181;
FIG. 184 illustrates an example claims dependency graph;
FIG. 185 illustrates an example claims dependency tree corresponding to the claims dependency graph of FIG. 184; and
FIG. 186 illustrates a web client in greater detail.
In the following text, reference is sometimes made to existing U.S. patents. Also, some of the figures reference or illustrate existing U.S. patents. For illustrative purposes, information from and/or about these patents has sometimes been modified or created in order to support the particular examples being discussed. Accordingly, the information provided herein about these existing U.S. patents should be considered to be fictional unless verified through comparison with copies of the actual U.S. patents that are available from the U.S. Patent and Trademark Office.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
Table of Contents
Overview of the Invention
Components of the Invention
Customer Corporate Entity
Databases
Document Databases
Document Bibliographic Databases
Patent Bibliographic Databases
Other Document Bibliographic Databases
Notes Database
Groups Databases
Predefined Groups Databases
Bill of Materials (BOM) Databases
Corporate Entity Databases
Inventor Databases (and Employees and Person
Databases)
User-Defined Group Databases
Financial Databases
Security Database
Enterprise Server
Document Storage and Retrieval Module
Notes Module
Searching Module
Automatic Searches Related to Groups
Searching Algorithm
Grouping Module
Analysis Modules
Server Administration Module
Server Configuration Module
Command Dispatch Module
Clients
Network Clients
Web Clients
Enterprise Server API (Application Programming Interface)
Commands Processed by the Server Administration Module 418
Commands Processed by the Document Storage and Retrieval Module 408
Commands Processed by the Grouping Module 412
Commands Processed by the Notes Module 414
Commands Processed by the Analysis Modules 416
Client/Server Interaction
Patent-Centric URL Commands
Translation
Client Architecture
Databases
Document Bibliographic Databases
Group Databases
User Defined Groups
Predefined Group Databases
Bill of Materials (BOM) Databases
Corporate Entity Databases
Inventor, Employee, and Person Databases
Financial Databases
Security Databases
Enterprise Server and Client Functional Modules
Patent Mapping Module
Patent Citation Module
Patent Aging Module
Patent Clustering and Bracketing Module
Financial Module
Inventor Patent Count Module
Inventor Employment Information Module
Exporting Patent Data Module
Importing Patent Data Module
Methodology Embodiments
Patent Mapping and Mining
Situation Assessment
Competitive Analysis
Clustering and/or Bracketing
Inventor Analysis
Financial Analysis
Strategic Planning
Integrated Methodology Embodiment
User Interface
User Login
Console
Console Tool Bars
Creating a New Group
Editing Group Properties
Shared Groups
Invoking Patent-Centric and Group-Oriented Analysis Functions
Adding Documents to a Group
Adding a Document Note
Adding a Group Note
Searching
Web Searching
Importing Data
Exporting Data
Data Presenting and Processing Using Hyperbolic Trees
General Description of Hyperbolic Trees
Patent Citation Tree
Patent Citation Tree (Network Client)
Patent Citation Tree (Web Client)
Additional Patent Citation Visualizations
Patent Claims Tree
Conclusion
Overview of the Invention
The present invention is directed to a system, components of the system, a method, components of the method, and a computer program product for patent-centric and group-oriented data processing. Such processing includes, but is not limited to, reporting, analyzing, and planning.
The present invention is intended to aid a corporate entity in developing business-related strategies, plans, and actions. Accordingly, the present invention is also referred to herein as a business decision system and method.
FIG. 2 is a conceptual representation of the invention. The present invention processes patent information 204, which is herein defined to include (but not limited to) U.S. and non-U.S. patents (text and/or images) and post issuance documents (such as Certificates of Correction), and patent-related information, which includes information about patents (herein called patent bibliographic information). Accordingly, the processing performed by the invention is said to be “patent-centric” or “patent-specific.”
More generally, the present invention processes any documents, some of which are related to patents, and others which are unrelated to patents. These documents are preferably of interest to a business entity, and include contracts, licenses, leases, notes, commercial papers, other legal and/or financial papers, etc., as well as patents.
For illustrative purposes, the invention is often described herein with respect to patents. However, it should be understood that the invention is also applicable to all types of documents, and the structures, functions, and operations described herein are applicable to all types of documents, whether patent or non-patent.
The present invention also processes other information, preferably business-related information, including (but not limited to) research and development (R&D) information 206, financial information 216, patent licensing information 214, manufacturing information 208, and other relevant business information 210 (which may, for example, include human resources information). This other information is generally called non-patent information (since it includes documents other than patents and may further include information from operational and non-operational corporate databases).
The present invention is adapted to maintain and process massive amounts of documents (several hundred thousand or more). It is often necessary to maintain and process this large number of documents in order to develop strategic, patent-related business plans for the customer.
According to the present invention, processing of the patent information 204 can be conducted either with or without consideration of any of the other information 206, 216, 214, 210, 208.
For example, a user 212 (who may be a business analyst) may be assigned the job of evaluating the value of the corporation's patent portfolio (represented as part of the patent information 204). In order to fully analyze the value and applicability of the corporation's patent portfolio, the user 212 must take into account other information, such as R&D information 206, financial information 216, manufacturing information 208, and licensing information 214, for both the corporation and its competitors.
For example, a patent's value may be linked to whether it covers technology that the corporation is currently using, or that the corporation may use in the future. For this and other purposes, the present invention includes functions for automatically analyzing the patent information 204 in conjunction with manufacturing information 208 and/or R&D information 206. Also, a patent's value may be linked to whether it has generated licensing revenue. For this and other purposes, the present invention includes functions. for automatically analyzing the patent information 204 in conjunction with the licensing information 214. Further, a patent's value may be linked to the degree of success of the corporation's commercial products related to the patent (i.e., the commercial embodiments of the patented technology). For this and other purposes, the present invention includes functions for automatically analyzing the patent information 204 in conjunction with the financial information 216.
The invention could also be used to determine the value of a corporate entity's patent portfolio for purposes of a merger or acquisition. The invention could also be used in a merger or acquisition context to determine a corporate entity's business direction. For example, if Company A is interested in acquiring Company B, Company A could use the invention to categorize all of Company B's patents into groups. The nature of these groups would be an indication of the types of work that Company B is involved in. Other uses of the invention are described below. Further uses of the invention will be apparent to persons skilled in the relevant art(s) based on the discussion contained herein.
The present invention is group enabled. According to the present invention, a group is a data structure that includes a collection of patents. The patents in a group typically follow a common theme or characteristic (although this is not a mandatory requirement of groups). For example, a first group may include patents that map to a product being manufactured and sold by a company. A second group may include patents that map to a product or product feature being considered for future manufacture and sale by a company. A third group may include patents owned by a corporate entity. A fourth group may include patents each having a particular person named as an inventor. A fifth group may include patents owned by a competitor. A sixth group may include patents related to a research project. A seventh group may include licensed patents. An eighth group may include patents and/or non-patent documents related to a litigation in which the customer is involved or has an interest (such a group is also herein called a case). A ninth group may include patents and other documents arbitrarily selected by a customer.
The present invention is capable of automatically processing the patents in a group, or the patents in multiple groups (alternatively, the invention can automatically process a single patent). Accordingly, the present invention is said to support “group-oriented” data processing.
Being able to automatically process information on a group basis is a very important feature of the invention, and proves to be very valuable and useful. Consider the above example of FIG. 2, where the user 212 has the task of evaluating the value of the corporation's patent portfolio. Suppose that the corporation has two products on the market, Product A and Product B. Product A generated $10 million in revenue, and Product B generated $30 million in revenue. The corporation has 5 patents that map to Product A, and 3 patents that map to Product B. If the user 212 analyzes this data without regard to groups, then the user 212 will find that the corporation's revenue per patent is $5 million. That is, for every $5 million in revenue, the corporation obtains a patent. Suppose that a relevant industry benchmark indicates that a company should obtain a patent for every $6 million of revenue. According to this scenario, the user 212 will conclude that the corporation is potentially seeking greater patent protection than the industry benchmark with respect to its technology.
Consider, now, the scenario where the user 212 analyzes the data with regard to groups, in this case a first group composed of patents that map to Product A, and a second group composed of patents that map to Product B. The user 212 will find that corporation's revenue per patent is $2 million for the first group (i.e., patents that map to Product A), and $10 million for the second group (i.e., patents that map to Product B). According to this scenario, the user 212 will conclude that the corporation is potentially devoting too much of its patent-related resources with respect to its technology related to Product A (it is “overpatenting” technology related to Product A), and potentially devoting too little of its patent-related resources with respect to its technology related to Product B (it is “underpatenting” technology related to Product B).
In addition, an analysis of the patents relative to a product may indicate that the core features or technology of the product are not patented and, thus, could be freely and legally copied by a competitor. This could adversely affect the product's price floor and revenue stream. With this information in hand, the company could then take steps to more comprehensively patent its technology (or make a conscious and knowledgeable decision to not seek further patent protection). Without group-oriented processing of the patents related to the product, this information is unavailable. Without this information, the company is more likely to make unwise and costly business decisions.
As indicated by the above example, group-oriented processing yields information on a scale whose granularity is defined by the definition of the group. The information produced by group-oriented processing is specific to the patents in the group. Accordingly, as with the above example, group-oriented processing is often more useful and more illuminating than non-group-processing.
Also, the invention supports hierarchically structured groups. The invention, in performing a function requested by the operator, may identify a particular group. Such identification of this group may yield very useful information, as apparent from the above example. This group, however, may have a number of parent and/or child groups. The operator may be able to uncover additional useful data by viewing, analyzing, and/or processing these parent and child groups, either with or without the original group.
Accordingly, the invention supports and facilitates “data drilling” and/or “data mining.”
As noted above, according to the present invention, processing of the patent information 204 is conducted with consideration of other information 206, 216, 214, 210, 208, called non-patent information. The process of assigning patents to groups is an example of processing patent information with non-patent information. This is the case, because groups are often created according to non-patent considerations. Accordingly, any subsequent processing of the patents in a group involve, by definition, non-patent considerations.
For example, the customer may create groups to represent its products. In this case, the groups are created according to the customer's production information. In another example, the customer may create groups to represent persons of interest. In this case, the groups are created according to HR (human resources) information. In another example, the customer may create groups to represent its competitors. In this case, the groups are created according to business information or practices. In another example, the customer may create groups based on its future products or feature requirement. In this case, the groups are created according to its R&D information.
All of these groups are created based on or in consideration of non-patent information, not patent information. Accordingly, any subsequent group processing of the patents contained in any of these groups represents, by definition, processing of the patent information 204 with consideration of, or in conjunction with, or based on non-patent information 206, 216, 214, 210, 208. This is the case, even if such subsequent group processing involves only, for example, patent bibliographic information (i.e., patent information), such as group processing based on patent issue dates or group processing based on patent references, since the groups being processed were created based on or in consideration of non-patent information, including non-patent information 206, 216,214,210,208.
A group may also contain non-patent documents. In fact, a group may contain only non-patent documents. Accordingly, a group is more generally defined as a collection of documents (such as patent documents only, non-patent documents only, or a combination of patent and non-patent documents). The documents in a group typically follow a common theme or characteristic (although this is not a mandatory requirement of groups). Referring to FIG. 2, the invention processes document information 204 alone, or in conjunction with other information 206, 216, 214, 210, 208 (which may or may not be related to the documents). Accordingly, the processing performed by the present invention is more generally described as being document-centric and group-oriented.
Components of the Invention
FIG. 3 is a block diagram of a system 302 according to an embodiment of the invention. The system 302 includes a plurality of databases 316 that store patent information and other information, such as R&D (research and development) information, financial information, licensing information, manufacturing information, HR (human resources) information, and any other information that may be pertinent to the analysis of the patent information. The terms “database” and “table” are used synonymously herein.
An enterprise server 314 accesses and processes the information in the databases 316. In particular, the enterprise server 314 includes modules that are capable of automatically accessing and processing the information in the databases 316 in a patent-centric (or document-centric) and group-oriented manner. These modules are also capable of automatically accessing and processing the information in the databases on a patent by patent basis (“one patent at a time”). Such processing includes, but is not limited to, reporting, analyzing, and planning.
The enterprise server 314 may be a single physical server, or may be a hierarchy of multiple servers 502, 504, 506, 508. An example of this multiple server embodiment is illustrated in FIG. 5. A given client 304, 306 may also connect to one or multiple servers. As is well known, in a client/server environment, some work is done by the client, some work is done by the server, and data flows between the client and the server.
The system 302 preferably includes two types of clients, network clients 306 and web clients 304. These clients 304, 306, pursuant to instructions from human operators or users (not shown), interact with the enterprise server 314 to access and process the information in the databases 316. For example, the clients 304, 306 may request that the enterprise server 314 retrieve certain information, or automatically analyze certain information. The enterprise server 314 performs the requested tasks, and sends the results to the requesting clients 304, 306. The clients 304, 306 present these results to their respective operators, and enable the operators to process the results.
Clients 304, 306 may also perform additional processing of data, such as creating a visualization of the data obtained from the enterprise server 314.
Generally speaking, the network clients 306 preferably communicate with the enterprise server 314 using the enterprise server 314's natural language, which is called the enterprise server API (described in detail below). Accordingly, the network clients 306 communicate directly with the enterprise server 314 via a communication network 312, which is preferably a network that uses the well known HTTP (hypertext transport) protocol. Other protocols could alternatively be used. This network 312 may be of any size, such as (but not limited to) a local area network or a wide area network (it can even be a global network).
The web clients 304 do not preferably utilize the enterprise server 314's natural language. Accordingly, the web clients 304 communicate with the enterprise server 314 via a web server 310, which translates between the language of the web clients 304 and the language of the enterprise server 314. This translation is described below.
In an embodiment of the present invention, the components of the present invention shown in FIG. 3 are implemented using well known computers, such as a computer 1102 shown in FIG. 11. The computer 1102 can be any commercially available and well known computer capable of performing the functions described herein, such as computers available from International Business Machines, Apple, Silicon Graphics Inc., Sun, HP, Dell, Compaq, Digital, Cray, etc.
The computer 1102 includes one or more processors (also called central processing units, or CPUs),. such as a processor 1106. The processor 1106 is connected to a communication bus 1104. The computer 1102 also includes a main or primary memory 1108, preferably random access memory (RAM). The primary memory 1108 has stored therein control logic 1110 (computer software), and data 1112.
The computer 1102 also includes one or more secondary storage devices 1114. The secondary storage devices 1114 include, for example, a hard disk drive 1116 and/or a removable storage device or drive 1118. The removable storage drive 1118 represents a floppy disk drive, a magnetic tape drive, a compact disk drive, an optical storage device, tape backup, ZIP drive, JAZZ drive, etc.
The removable storage drive 1118 interacts with a removable storage unit 1120. As will be appreciated, the removable storage unit 1120 includes a computer usable or readable storage medium having stored therein computer software (control logic) and/or data. The removable storage drive 1118 reads from and/or writes to the removable storage unit 1120 in a well known manner.
Removable storage unit 1120, also called a program storage device or a computer program product, represents a floppy disk, magnetic tape, compact disk, optical storage disk, ZIP disk, JAZZ disk/tape, or any other computer data storage device. Program storage devices or computer program products also include any device in which computer programs can be stored, such as hard drives.
In an embodiment, the present invention is directed to computer program products or program storage devices having software that enables the computer 1102 to perform any combination of the functions described herein.
Computer programs (also called computer control logic) are stored in main memory 1108 and/or the secondary storage devices 1114. Such computer programs, when executed, enable the computer 1102 to perform the functions of the present invention as discussed herein. In particular, the computer programs, when executed, enable the processor 1106 to perform the functions of the present invention. Accordingly, such computer programs represent controllers of the computer 1102.
The modules of the invention discussed herein, such as the grouping module 412, the analysis modules 416, etc., preferably represent software executing in the computer 1102.
The computer 1102 also includes a display unit 1122, such as a computer monitor, and one or more input devices 1124, such as a keyboard, a mouse, other pointing devices (such as a light pen and trackball), etc.
The computer 1102 further includes a communication or network interface 1126. The network interface 1126 enables the computer 1102 to communicate over communication networks, such as networks 308 and 312, which preferably use the well known HTTP communication protocol.
The components of the invention (shown in FIG. 3) are described in greater detail below. It should be understood that any specific software, hardware, or operating system implementations described herein are provided for purposes of illustration, and not limitation. The invention can work with software, hardware, and operating system implementations other than those described herein. Any software, hardware, and operating system implementations suitable for performing the functions described herein can be used.
Customer Corporate Entity
Preferably, the system 302 is adapted for use by a particular customer. Typically, the customer is a corporate entity. Accordingly, the customer is also called herein the customer corporate entity.
It should be understood, however, that the customer can be any organization or individual, such as an academic institution, a research organization, a non-profit or for-profit organization, or any person. Generally, the customer is any entity having an interest in patents.
The customer is an entity (such as a company) that has arranged to have use of the system 302 (by purchasing, leasing, or renting the system 302, for example).
The databases 316 and data contained therein are specific to the customer. For example, the databases 316 may contain information on the patents that the customer owns and/or licensees, and information on the patents that the customer's competitors owns and/or licenses. Also, the databases 316 may contain the customer's and the customer's competitors' R&D information, financial information, licensing information, manufacturing information, and HR information.
Also, the methodology functions supported by the enterprise server 314 may be specialized or augmented to meet the needs of the customer.
Implementation and use of the present invention may involve a number of persons associated with the customer corporate entity, such as employees, consultants, associates, and persons retained by the customer, such as attorneys. When interacting with the invention, these people are called operators or users. Table 1 lists some of such persons and their respective responsibilities according to an embodiment of the invention. These persons may be involved in all aspects of the invention for the customer, or may be involved in only some phases of the invention for the customer, such as the extract and load of the databases 316. It should be noted that the set up and use of the invention may also involve other people with different knowledge, skills, and/or abilities.
In the discussion contained herein, reference is often made to a user or an operator associated with the customer. It should be understood that the terms “user” and “operator” are synonymous, and refer to one or more persons from Table 1.
| TABLE 1 |
|
| Role/Function | Responsibilities |
| Executive, PL, or | Ensure strategy meets short and long term |
| Division Managers | business goals and plans |
| Intellectual Property | Analysis of patents as related to mapping, |
| (IP) Attorneys | licensing, infringement, non-renewal, cross- |
| licensing etc. | |
| Technical Personnel | Analysis of patents and how they relate to given |
| product functions and features. Also domain | |
| R&D experts as needed for specific competitive | |
| technology assessment | |
| MIS personnel | Help in data extraction from operational systems |
| Marketing personnel | Product Strategy, Features, Target Markets, |
| Competitive Analysis | |
| Business and | Economic implications, profit, loss, tax, market |
| Financial Analysts | share, etc. |
Databases
FIG. 6 illustrates the databases 316. According to the present invention, the databases 316 store document information (that includes patent information) and information pertinent to the analysis of the document information.
FIG. 6 illustrates a particular embodiment of the databases 316, and also illustrates a particular embodiment of the types of tables that the databases 316 contain, and the attributes in the tables. It should be understood, however, that the invention is not limited to the particular database embodiment of FIG. 6. Instead, the invention is adapted and intended to cover other database structures and organizations that are capable of storing document information and information pertinent to the analysis of the document information. The particular information that is stored in the databases is implementation dependent and varies based on a number of factors, including the type of analysis that is desired, the specific needs of the customer, the type and content of the information that the customer maintains, etc.
The databases 316 of FIG. 6 are collectively called methodology databases, and the data within them are called methodology data, because they support the functions and features, or the methodology, of the present invention. These functions and features (generically called methodology functions and features) are described in sections below.
Many of the databases 316, such as the BOM databases 626, the inventor databases 628, and corporate entity databases 630, the financial databases 638, the person databases 632, and the employee databases 634, are initially loaded using information provided by the customer. Such information includes R&D (research and development) information, financial information, licensing information, manufacturing information, HR (human resources) information, and any other information that may be pertinent to the analysis of the customer's patents and other relevant documents. After initial loading, these databases 316 are updated as necessary to reflect changes in the customer's information.
Other information, such as information for the patent bibliographic databases 604 and the patent database 614, may be loaded using information provided by a third party provider, such as a third party provider that specializes in the provision of patent information in electronic form. One such third party provider is SmartPatents Inc. (SPI) of Mountain View, Calif. The patent bibliographic databases 604. may be periodically updated through a subscription service from such third party providers. Similarly, the patent database 614 may be augmented through as-needed orders to the third party providers. It should be understood that the present invention works equally well with data provided by any party as long as the data's format matches the formats of the patent bibliographic databases 604 and the patent database 614.
The databases 316 are described in greater detail below.
Document Databases
The document databases 612 preferably include electronic representations of documents of interest to the customer. The document databases 612 represent the customer's repository of documents, and are thus also called the customer's document repository. (The “repository” could alternatively represent all documents represented in the databases 316, whether represented in the document databases 612 or the bibliographic databases 602.)
For example, the patent database 614 includes electronic representations of U.S. and foreign patents of interest to the customer. These patents may be patents owned and/or licensed by the customer, patents owned and/or licensed by competitors of the customer, patents that the customer is considering acquiring, patents that, for whatever reason, the customer is studying, etc. The patent database 614 represents the customer's repository of patents, and is thus also called (in some embodiments) the customer's patent repository.
The patent database 614 preferably has stored therein an image file and a text file for each patent represented in the patent database 614, where the image file and the text file are representations of the patent. Details of an embodiment of the image file and the text file are described in U.S. Pat. No. 5,623,681 and U.S. Pat. No. 5,623,679, which are both incorporated herein by reference in their entireties.
The document databases 612 also include electronic representations of other documents of interest to the customer, such as depositions, pleadings, and prior art references. These documents are respectively stored in a deposition database 618, a pleadings database 616 (generally, pleadings are papers filed with a court), and a prior art database 620. Text and/or image representations of these documents may be stored. These documents may be pertinent to a patent litigation that the customer is involved in.
The documents in the document databases 612 may be text, images, graphics, audio, video, multimedia, and/or any other information representation that can be stored in electronic form.
It should be understood that the document databases 612 of FIG. 6 are shown for purposes of illustration, and not limitation. As mentioned above, the document databases 612 store electronic representations of documents that are of interest to the customer. Accordingly, the types of document databases 612 and the contents of the document databases 612 are, by definition, customer and implementation specific.
Document Bibliographic Databases
The document bibliographic databases 602 store information about documents (as opposed to the documents themselves). More particularly, the document bibliographic databases 602 store bibliographic information about documents.
Patent Bibliographic Databases
The patent bibliographic databases 604 store bibliographic data about U.S. and non-U.S. patents. Such patent bibliographic data includes, but is not limited to, the information on the front page of patents, such as: the patent number, the issue date, the inventors, the title, the assignee, the serial number, the filing date, the U.S. and international classifications, the fields of search, the references cited, the primary examiner, the assistant examiner, the attorney, the agent, the law firm, priority information, related application information, the number of claims, the number of drawing pages, the patent term, the expiration date, etc. The patent bibliographic databases 604 can also include one or more user defmed fields that can store large amounts of data, such as 32 Kbytes or more of data.
Operators can extend the bibliographic databases 602 in patent-centric ways. For example, a “current licensee” field can be added to the patent bibliographic databases 604. This could be accomplished, for example, by defining one of the user defined fields to be a current licensee field.
In an embodiment of the invention, the patent bibliographic databases 604 store bibliographic information on all U.S. patents. In other embodiments of the invention, the patent bibliographic databases 604 store patent bibliographic information on a subset of all U.S. patents, such as all U.S. patents that are available in electronic form from the U.S. Patent Office, or all U.S. patents that issued after a certain date.
Generally, there is not a one-to-one relationship between the patents in the patent database 614, and the patents represented in the patent bibliographic databases 604. That is, the patent database 614 does not generally include a copy of each patent represented in the patent bibliographic databases 604. Instead, the patent database 614 includes only those patents that are of interest to the customer. In contrast, the patent bibliographic databases 604 store bibliographic information on all U.S. patents and/or foreign patents (or, alternatively, all U.S. patents that issued after a certain date, and/or a subset of foreign patents). Of course, if the customer has an interest in all U.S. patents, such that electronic copies of all U.S. patents are stored in the patent database 614, then there would be a one-to-one relationship between the patents in the patent database 614, and the patents represented in the patent bibliographic databases 604.
Other Document Bibliographic Databases
The document bibliographic databases 602 include store bibliographic information on other types of documents that are of interest to the customer. For example, if the customer is interested in depositions, pleadings, or prior art references, then the document bibliographic databases 602 would store bibliographic information on depositions, pleadings, or prior art references in deposition bibliographic databases 606, pleadings bibliographic databases 608, and prior art bibliographic databases 610, respectively.
The bibliographic information may include the parties or persons involved, the date of creation, the date of modification, the subject, the number of pages, the number of figures, etc. Such bibliographic information may be generated manually, and/or may be generated automatically during the generation of the source document. For example, word processing tools often automatically generate bibliographic information about a document as the document is being created. Such information may include the creator, the typist, the date of creation, the date of modification, the subject, the title, the type of document, the storage format, etc. This automatically-created bibliographic information could be loaded into the document bibliographic databases 602.
Notes Database
The present invention supports annotation of the documents in the document databases 612. More particularly, the present invention allows users to create and link annotations (also called notes) to any portions of the documents in the document databases 612. Such annotations can include text, graphics, images, video, audio, and/or any other information representation that can be stored in electronic form.
The present invention also allows various information to be stored with annotations, such as the date of creation, the creator, the date of modification, a note title and/or subject, access rights, etc.
The annotations, linkage information (i.e., information that specifies the link between a note and a portion of a document), and information related to the annotations and/or the linkage information (such as the position of the linked portion in the document, the date of creation, the creator, the date of modification, a note title and/or subject, access rights, etc.) are stored in the notes databases 640. Embodiments of the notes databases 640 are described in U.S. Pat. No. 5,623,679 and U.S. Pat. No. 5,623,681, incorporated by reference herein, and in pending U.S. application Ser. No. 08/590,082, which is herein incorporated by reference in its entirety.
Groups Databases
Information on groups is stored in the group databases 621. Generally, a group is a data structure that includes any number of documents that typically follow a common theme or characteristic (although this is not a mandatory requirement of groups). More particularly, a group is a data structure that includes any number of patents that typically follow a common theme or characteristic (although, again, this is not a mandatory requirement of groups). Groups are document-centric, or in many cases, patent-centric.
There are two classes of groups: predefined groups (also called system defined groups) and user-defined groups (also called arbitrary groups).
However, the invention also supports other types of groups. For example, the invention supports temporary groups. A temporary group is automatically created by the invention in the course of processing a command. One application of temporary groups involves search operations. Specifically, when conducting a search for documents, a new temporary group is created, and the search results are stored in the temporary group. The invention permits operators to convert temporary groups to predefined groups or user-defmed groups.
Patents (and/or documents) in predefined groups follow a predefined theme or characteristic. Database tables, fields, and attributes of a predefined group are specific to the predefined theme/characteristic of the predefined group. Accordingly, different predefined groups have different database tables, different database fields, and different database attributes. Information on predefined groups is stored in the predefined or system defined group databases 622.
Patents (and/or documents) in user-defined groups may or may not follow a common theme or characteristic. Any theme or characteristic that they do follow is defined by the user. Accordingly, user-defined groups are also called arbitrary groups.
All user-defined groups have the same, generic database tables, fields, and attributes. However, users may elect to use these database tables, fields and attributes differently for different user-defmed groups. Information on user-defined groups is stored in the user-defined group databases 624.
Predefined groups can be more powerful than user-defined groups for at least two reasons. First, the databases associated with a predefined group store information that is specific to the predefined characteristics of the predefined group. As a result, more useful and specific information can be stored in predefined groups. Second, since the data attributes and characteristics of predefined groups are known in advance, specific functions can be generated in advance to automatically process the information associated with predefined groups. As a result, the information associated with predefined groups can be automatically processed in powerful and diverse ways that are useful given the attributes and characteristics of the predefined groups.
The tables and attributes of predefined groups are typically not applicable to other types of groups. In contrast, the tables and attributes of user-defined groups are generic, and are applicable to all groups. Thus, user-defined groups are more flexible than predefined groups.
Accordingly, in practice, a user-defined group is used by a customer until its attributes, characteristics, and functions are well defined. Once they are well defined, a new predefined group is created to replace the user-defined group. This new predefined group is designed to encompass and take advantage of the specific attributes, characteristics, and functions of the group. In other words, this new predefined group is designed to encompass and take advantage of the well defined structure of the group. Then, analysis and reporting modules are created which automatically analyze and report on the data in the new predefined group. It is possible to create such analysis and reporting modules specific to the new predefined group because of the well defined structure of the new predefined group. The new predefined groups and their reporting and analysis modules can then be distributed (i.e., its databases and functional modules can then be distributed) to interested customers of the invention.
The scope of the present invention includes the creation of new predefined groups and their reporting and analysis functions in the manner described above. The scope of the present invention also includes such new predefined groups and their reporting and analysis functions. The structure and operation of such new predefined groups and their reporting and analysis functions are implementation dependent, but would be apparent to persons skilled in the relevant art(s) based on the discussion contained herein.
In the present invention, groups are structured. Specifically, groups are organized into a directed, acyclic graph, where a group can have multiple children groups and multiple parent groups.
The system of the invention discourages or prevents non-sensical organizations of groups. Such non-sensical organizations of groups is at least partially discouraged or prevented by the automatic functions performed by the invention. For example, the system discourages or prevents making a corporate entity group a child of a BOM group, since running an analysis report on all of the subassemblies of the BOM group would yield questionable or undefined results since a corporate entity does not have subassemblies. In an embodiment of the invention, such non-sensical organization of groups is prevented by computer programming.
Also, when a specialized (predefined) group is created to perform specialized analysis functions, new restrictions regarding the rules that govern the inter-relationships between groups are also created. The rules manifest themselves in the database schema. The database schema of the invention prevents the creation of non-sensical group relationships.
Predefined Groups Databases
Various predefined groups are described below. It should be understood that the following represents examples of predefined groups supported by the invention. The invention is adapted and intended to include other predefined groups. As described above, predefined groups are often created from user-defined groups once the attributes, characteristics, and functions of the user-defined groups are well defined. The invention is adapted and intended to include these types of predefined groups. Accordingly, the following is provided for purposes of illustration, and not limitation.
Bill of Materials (BOM) Databases
A BOM (bill of materials) group is a group that contains patents (and perhaps other documents) that map to a product, or that map to parts of a product. More particularly, a BOM group is a group that contains patents that map to an assembly, a subassembly, or a part, where an assembly is composed of one or more subassemblies, and a subassembly is composed of other subassemblies and/or parts.
The phrase “a patent maps to a product” means that the patent includes claims that appear to read on the product or process of making and/or using the product, and/or includes claims that are related to or relevant to the product or process of making and/or using the product, and/or that the patent discloses subject matter than encompasses the product or process of making and/or using the product, and/or that the patent discloses subject matter than is related to or relevant to the product or process of making and/or using the product.
Information on BOM groups is stored in the BOM databases 626. BOM groups and the BOM databases 626 are discussed in greater detail in sections below.
Corporate Entity Databases
A corporate entity group is a group that contains patents (or other documents) that are owned, licensed, or otherwise of interest to a corporate entity. Information on corporate entity groups is stored in corporate entity databases 630. The corporate entity databases 630 can include information on any number of corporate entity groups. Such corporate entity groups can correspond to any corporate entities that are of interest to the customer, such as the customer itself, affiliates of the customer, competitors of the customer, etc. Corporate entity groups and the corporate entity databases 630 are discussed in greater detail in sections below.
Inventor Databases (and Employees and Person Databases)
An inventor group is a group that contains patents each of which name as inventor a particular person. Information on inventor groups is stored in inventor databases 628. The inventor databases 628 are supported by person databases 632, which include information on people of interest to the customer (people who play a role in the processing of the invention, such as an inventor or employee), and employee databases 634, which include information on employees of interest to the customer. Inventor groups, the inventor databases 628, the employee databases 634, and the person databases 632 are discussed in greater detail in sections below.
User-Defined Group Databases
A user-defined group is a data structure that contains documents that follow some user-defined theme or characteristic. Information on user-defined groups is stored in the user-defined group databases 624.
These user-defined group databases 624 are common to all user-defined groups. In particular, the attributes in these user-defined group databases 624 are the same for all user-defined groups. However, the customer can choose to utilize these attributes differently for each user-defined group. For example, the customer may choose to store different types of data in these attributes for different user-defined groups. User-defined groups and the user-defined group databases 624 are discussed in greater detail in sections below.
Financial Databases
The financial databases 638 store financial information pertaining to the customer's business. The financial databases 638 may also include financial information on competitors' businesses (to the extent that such information is publicly known, or can be determined or estimated based on publicly known information or business practices). Such financial information may include money spent on R&D on a product line basis, gross and net revenue on a product line basis, patent licensing revenue, patent acquisition costs, etc. The invention correlates and analyzes the information in the financial databases 638 with patent information to determine, among other things, the financial impact of patents on the customer's and competitors' respective businesses. The financial databases 638 are discussed in greater detail in sections below.
Security Database
The present invention includes multileveled security features for limiting access to data stored in the databases 316. Security is defined herein as privilege levels associated with operators and data objects, and a security methodology for applying the privilege levels so as to restrict access to the data objects to operators having the appropriate privilege levels.
The invention is capable of supporting security for all data items, including security for notes (stored in the notes databases 640), groups (stored in the group databases 621), financial information (stored in the financial databases 638), personal information (stored in the person databases 632 and the employee databases 634), and documents (stored in the document databases 612 and the document bibliographic databases 602). Information for implementing these security features is stored in the security databases 636, which are discussed in greater detail in sections below.
Enterprise Server
The enterprise server 314 is preferably implemented as one or more computers (such as the computer 1102 shown in FIG. 11) each having at least 128 MBytes of main memory 1108 and running Microsoft Windows NT. The enterprise server 314 could, alternatively, be implemented using other memory configurations, and other operating systems, such as (but not limited to) UNIX, Windows 95, MS-DOS, the Apple Operating System, etc. Accordingly, the specific hardware and software implementations discussed herein are provided for purposes of illustration, not limitation (this applies to all specific hardware and software implementations discussed herein, both for the enterprise server 314 and for other components of the invention). The invention can utilize any hardware, software, and operating system capable of performing the functions described herein.
The enterprise server 314 can be a single computer, or a hierarchy of multiple computers (FIG. 5). Logically, however, the enterprise server 314 is preferably a single computer.
FIG. 4 is a logical block diagram of the enterprise server 314. The enterprise server 314 has a number of modules (collectively called the enterprise server modules). Note that a number of the modules interact with the databases 316. A SQL server 426 (such as the Microsoft SQL Server) and/or other well known database servers 428 interact directly with the databases 316. The enterprise server modules interact with these servers 426 and 428 and the databases 316 via a database interface module 420, which preferably represents an ODBC (object database connectivity) layer.
The Network transport layer or interface 401 is used to receive command request objects from the client 304, 306 based on a specific network protocol, preferably HTTP. On the enterprise server 314 these network command objects are reconstructed from a stream of bits received from the client 304, 306. Once the command objects have been reconstructed the specific operations (described herein) defined in this object are performed by the appropriate enterprise server modules. The command objects represent enterprise server API commands, discussed below.
According to an embodiment of the invention, command objects include autonomous intelligent agents that perform appropriate operations at the enterprise server 314 on behalf of the operator (i.e., the client 304, 306). In this embodiment, the command objects sent to the enterprise server 314 represent computer programs that are executed in the enterprise server 314. These executing computer programs preferably represent threads each having an address space. These computer programs, when executing in the enterprise server 314, perform the functions discussed herein, such as patent mapping, patent aging, inventor count, inventor information, financial functions, etc.
The enterprise server 314 is a highly secure business decision system. The specific operations in each command object are checked against the security information maintained about each user in the system. This is logically done through a comprehensive security layer or module 402. (The specific implementation of security requires the interaction with ODBC 420, as all security information is stored in the databases 316). Alternatively, the security module 402 could logically be shown as being under the server configuration module 404 and the command dispatch module 406.
As described elsewhere herein, the document storage and retrieval module 408 is part of a Virtual Patent System 11304 (FIG. 113) that presents a consistent, unified view of an arbitrary number of patent and patent-related documents.
The Searching subsystem or module 410 provides for patent searching using a search language (syntax) described below, an extensible language for searching patent and other patent-related documents. The search layer 410 also encapsulates the specific search engine 424 used in the implementation of the system, which can and will vary based on available search technologies.
The other layers shown in FIG. 4 work together to form the heart of the business decision system of the present invention. The Groups layer or grouping module 412 is responsible for managing all groups created by a user in support of patent analysis. The Notes layer or module 414 is responsible for managing all forms of annotations made by the user. The Analysis Queries layer or analysis modules 416 perform analysis queries in support of specific requests made by various modules in the decision support system. Finally, the server administration layer or module 418 provides services to manage the configuration of the enterprise server 314, such as adding or changing the security permissions associated with a specific user.
Each of these layers provides a mechanism to further decouple the operation of the enterprise server 314 from the specific implementation of the databases 316. Each of these layers also interact with ODBC (Open Database Connectivity) 420, a Microsoft defined industry standard mechanism for manipulating relational databases (other software for interacting with and manipulating databases could alternatively be used). ODBC 420 provides a final layer of decoupling and enables the enterprise server 314 to transparently connect to different relational databases 316.
The enterprise server modules are further described below.
Document Storage and Retrieval Module
The document storage and retrieval module 408 in the enterprise server 314 stores and retrieves documents from the document databases 612. Preferably, especially with respect to patent documents, the document storage and retrieval module 408 stores and retrieves text files and image files representative of documents in the document databases 612. The document storage and retrieval module 408 performs such data storage and retrieval operations pursuant to commands that conform to the enterprise server API, described below.
The document storage and retrieval module 408 preferably interacts directly with the operating system 422 of the enterprise server 314, where such direct interaction primarily pertains to data retrieval and storage.
As just noted, the document storage and retrieval module 408 operates to access data in the document databases 612, such as the customer's repository of patents represented by the patent database 614. Preferably, the patent database 614 stores electronic representations of all patents which are of interest to the customer. Additional electronic patents can be added to the patent database 614 at any time as the customer's interests change. The patent database 614 is capable of storing electronic representations of all U.S. patents, or any subset of all U.S. patents, and of any number of foreign patents as required by the customer's needs and interests. Accordingly, the document storage and retrieval module 408, in combination with the patent database 614 and the patent bibliographic databases 604, provide the customer with the ability to quickly, efficiently, and effectively access, display, and process any patent of interest. Accordingly, from the perspective of the client, the document storage and retrieval module 408, in combination with the patent database 614 and the patent bibliographic databases 604, represent a virtual patent system. FIG. 113 graphically depicts this virtual patent system 11304.
The client document storage and retrieval module 708 in the clients 304, 306 (FIG. 7) displays the text and images received from the document storage and retrieval module 408 in the enterprise server 314. As shown in FIG. 112, the client document storage and retrieval module 708 is capable of simultaneously displaying the text of a document in a first window 11202, and the image of a document in a second window 11204.
The client document storage and retrieval module 708 has features and functions for enabling a user to manipulate and otherwise process the displayed data. For example, the client document storage and retrieval module
The remainder of this text has been abbreviated because it is either very complex or very long and may not be displayed properly or efficiently by your web browser. Even with this precaution, certain browsers may display odd behaviors when rendering this document. Please download the document to view it in its entirety.
(Source: USPTO)
What is claimed is:
1. A method of displaying data, comprising the steps of:
(1) accessing patent-related documents;
(2) accessing one or more groups each comprising any number of said patent-related documents;
(3) automatically generating a hyperbolic tree containing data from any of said patent-related documents; and
(4) allowing a user to selectively focus on at least some of said data that is displayed in a portion of said hyperbolic tree.
2. The method of claim 1 further comprising the steps of:
(5) enabling said user to traverse to another portion of said hyperbolic tree; and
(6) dynamically presenting, responsive to step (5), said data in said another portion of said hyperbolic tree.
3. The method of claim 1, wherein said patent related documents in step (3) is comprised of at least one pre-selected patent-related document.
4. The method of claim 3, wherein said data in step (3) is comprised of at least one type of data that has been pre-selected by a user.
5. A method of processing and presenting data, comprising the steps of:
(1) retrieving patent citation information pertaining to a user-selected patent;
(2) constructing a patent citation hyperbolic tree using said retrieved patent citation information; and
(3) displaying said patent citation hyperbolic tree.
6. The method of claim 5, wherein step (2) comprises the step of:
generating a citation analysis graph using said retrieved patent citation information.
7. The method of claim 6, wherein step (2) further comprises the step of:
constructing said patent citation hyperbolic tree from said citation analysis graph.
8. The method of claim 6, wherein step (2) further comprises the steps of:
mapping said citation analysis graph to a citation analysis tree; and
constructing said patent citation hyperbolic tree from said citation analysis tree.
9. The method of claim 5, wherein step (3) comprises the step of:
(a) modifying display properties of nodes of said patent citation hyperbolic tree according to user-selected criteria.
10. The method of claim 9, wherein step (a) comprises the step of:
(I) modifying display properties of nodes of said patent citation hyperbolic tree according to assignees of patents corresponding to said nodes.
11. The method of claim 10, wherein step (I) comprises the steps of:
upon receipt of appropriate operator command, toggling between:
(i) modifying display properties of said nodes of said patent citation hyperbolic tree according to original patent assignee information; and
(ii) modifying display properties of said nodes of said patent citation hyperbolic tree according to current patent assignee information.
12. The method of claim 9, wherein step (a) comprises the step of:
modifying display properties of nodes of said patent citation hyperbolic tree according to time-based criteria.
13. The method of claim 9, wherein step (a) comprises the step of:
modifying display properties of nodes of said patent citation hyperbolic tree according to user-defined criteria.
14. The method of claim 9, further comprising the step of:
displaying a legend that describes said user-selected criteria.
15. The method of claim 5, further comprising the steps of:
(4) receiving an operator command to display a patent represented in said patent citation hyperbolic tree; and
(5) displaying said represented patent.
16. The method of claim 15, wherein step (5) comprises the steps of:
displaying bibliographic information of said represented patent if said represented patent is not stored in a local repository; and
displaying any combination of bibliographic information, text, and images of said represented patent if said represented patent is stored in a local repository.
17. The method of claim 5, wherein said patent citation information in step (2) is comprised
of at least one type of information that has been pre-selected by a user.
18. The method of claim 5, wherein said step (3) comprises displaying data in said patent citation hyperbolic tree such that at least some of said data is displayed in a portion of said patent citation hyperbolic tree, the method further comprising the steps of:
(4) enabling a user to traverse to another portion of said patent citation hyperbolic tree; and
(5) dynamically presenting, responsive to step (4), said data in said another portion of said patent citation hyperbolic tree.
19. The method of claim 9, wherein step (a) comprises the step of:
(I) modifying display properties of nodes of said patent citation hyperbolic tree according to at least one of issue date, patent number, inventors, title, serial number, U.S. classification, international classification, fields of search, references cited, primary examiner, assistant examiner, attorney, agent, law firm, priority information, related application information, number of claims, number of drawing pages, patent term, patent aging, and expiration date of patents corresponding to said nodes.
20. The method of claim 19, wherein said display properties consist of at least one of a preselected color scheme, a preselected case sensitive scheme, a preselected typeface scheme, a preselected font scheme, a preselected underlining scheme, a preselected bolding scheme, a preselected italics scheme and a preselected type size scheme.
21. The method of claim 19, wherein said display properties consist of at least one of a user-defined color scheme, a user-defined case sensitive scheme, a user-defined typeface scheme, a user-defined font scheme, a user-defined underlining scheme, a user-defined bolding scheme, a user-defined italics scheme and a user-defined type size scheme.
22. The method of claim 10, wherein said display properties consist of at least one of a preselected color scheme, a preselected case sensitive scheme, a preselected typeface scheme, a preselected font scheme, a preselected underlining scheme, a preselected bolding scheme, a preselected italics scheme and a preselected type size scheme.
23. The method of claim 10, wherein said display properties consist of at least one of a user-defined color scheme, a user-defined case sensitive scheme, a user-defined typeface scheme, a user-defined font scheme, a user-defined underlining scheme, a user-defined bolding scheme, a user-defined italics scheme and a user-defined type size scheme.
24. A system of processing and presenting data, comprising:
information retrieving means for retrieving patent citation information pertaining to a user-selected patent;
tree constructing means for constructing a patent citation hyperbolic tree using said retrieved patent citation information; and
tree displaying means for displaying said patent citation hyperbolic tree.
25. The system of claim 24, further comprising:
means for receiving a backward patent citation command or a forward patent citation command; and
means for receiving an indication of a number of levels to cite.
26. The system of claim 25, wherein said information retrieving means comprises:
means for retrieving information identifying patents that are cited in said user-selected patent for said number of levels if a backward patent citation command was received; and
means for retrieving information identifying patents that cite said user-selected patent for said number of levels if a forward patent citation command was received.
27. The system of claim 24, wherein said tree constructing means comprises:
means for generating a citation analysis graph using said retrieved patent citation information.
28. The system of claim 27, wherein said tree constructing means comprises:
means for constructing said patent citation hyperbolic tree from said citation analysis graph.
29. The system of claim 27, wherein said tree constructing means comprises:
means for mapping said citation analysis graph to a citation analysis tree; and
means for constructing said patent citation hyperbolic tree from said citation analysis tree.
30. The system of claim 24, wherein said tree displaying means comprises:
modifying display properties means for modifying display properties of nodes of said patent citation hyperbolic tree according to user-selected criteria.
31. The system of claim 30, wherein said modifying display properties means comprises:
assignee modifying display properties means for modifying display properties of nodes of said patent citation hyperbolic tree according to assignees of patents corresponding to said nodes.
32. The system of claim 31, wherein said assignee modifying display properties means comprises:
means, upon receipt of appropriate operator command, for toggling between:
(i) modifying display properties of said nodes of said patent citation hyperbolic tree according to original patent assignee information; and
(ii) modifying display properties of said nodes of said patent citation hyperbolic tree according to current patent assignee information.
33. The system of claim 30, wherein said modifying display properties means comprises:
means for modifying display properties of nodes of said patent citation hyperbolic tree according to time-based criteria.
34. The system of claim 30, wherein said modifying display properties means comprises:
means for modifying display properties of nodes of said patent citation hyperbolic tree according to user-defined criteria.
35. The system of claim 30, further comprising:
means for displaying a legend that describes said user-selected criteria.
36. The system of claim 24, further comprising:
means for receiving an operator command to display a patent represented in said patent citation hyperbolic tree; and
patent displaying means for displaying said represented patent.
37. The system of claim 36, wherein said patent displaying means comprises:
means for displaying bibliographic information of said represented patent if said represented patent is not stored in a local repository; and
means for displaying any combination of bibliographic information, text, and images of said represented patent if said represented patent is stored in a local repository.
38. The system of claim 24, wherein said tree displaying means comprises displaying data in said patent citation hyperbolic tree such that at least some of said data is displayed in a portion of said patent citation hyperbolic tree, the system further comprising:
user enabling means for enabling a user to traverse to another portion of said patent citation hyperbolic tree; and
dynamic presentation means, responsive to said user enabling means, for dynamically presenting said data in said another portion of said patent citation hyperbolic tree.
39. The system of claim 30, wherein said modifying display property means comprises:
issue date modifying display properties means for modifying display properties of nodes of said patent citation hyperbolic tree according to at least one of issue date, patent number, inventors, title, serial number, U.S. classification, international classification, fields of search, references cited, primary examiner, assistant examiner, attorney, agent, law firm, priority information, related application information, number of claims, number of drawing pages, patent term, patent aging, and expiration date of patents corresponding to said nodes.
40. The system of claim 39, wherein said display properties consist of at least one of a preselected color scheme, a preselected case sensitive scheme, a preselected typeface scheme, a preselected font scheme, a preselected underlining scheme, a preselected bolding scheme, a preselected italics scheme and a preselected type size scheme.
41. The system of claim 39, wherein said display properties consist of at least one of a user-defined color scheme, a user-defined case sensitive scheme, a user-defined typeface scheme, a user-defined font scheme, a user-defined underlining scheme, a user-defined bolding scheme, a user-defined italics scheme and a user-defined type size scheme.
42. The system of claim 31, wherein said display properties consist of at least one of a preselected color scheme, a preselected case sensitive scheme, a preselected typeface scheme, a preselected font scheme, a preselected underlining scheme, a preselected bolding scheme, a preselected italics scheme and a preselected type size scheme.
43. The system of claim 31, wherein said display properties consist of at least one of a user-defined color scheme, a user-defined case sensitive scheme, a user-defined typeface scheme, a user-defined font scheme, a user-defined underlining scheme, a user-defined bolding scheme, a user-defined italics scheme and a user-defined type size scheme.
44. A computer program product comprising a computer useable medium having computer program logic stored therein, wherein said computer program logic comprises:
information retrieving means for enabling a computer to retrieve patent citation information pertaining to a user-selected patent;
tree constructing means for enabling the computer to construct a patent citation hyperbolic tree using said retrieved patent citation information; and
tree displaying means for enabling the computer to display said patent citation hyperbolic tree.
45. The computer program product of claim 44, further comprising:
means for enabling the computer to receive a backward patent citation command or a forward patent citation command; and
means for enabling the computer to receive an indication of a number of levels to cite.
46. The computer program product of claim 45, wherein said information retrieving means comprises:
means for enabling the computer to retrieve information identifying patents that are cited in said user-selected patent for said number of levels if a backward patent citation command was received; and
means for enabling the computer to retrieve information identifying patents that cite said user-selected patent for said number of levels if a forward patent citation command was received.
47. The computer program product of claim 44, wherein said tree constructing means comprises:
means for enabling the computer to generate a citation analysis graph using said retrieved patent citation information.
48. The computer program product of claim 47, wherein said tree constructing means comprises:
means for enabling the computer to construct said patent citation hyperbolic tree from said citation analysis graph.
49. The computer program product of claim 47, wherein said tree constructing means comprises:
means for enabling the computer to map said citation analysis graph to a citation analysis tree; and
means for enabling the computer to construct said patent citation hyperbolic tree from said citation analysis tree.
50. The computer program product of claim 44, wherein said tree displaying means comprises:
modifying display properties means for enabling the computer to modify display properties of nodes of said patent citation hyperbolic tree according to user-selected criteria.
51. The computer program product of claim 50, wherein said modifying display properties means comprises:
assignee modifying display properties means for enabling the computer to modify display properties of nodes of said patent citation hyperbolic tree according to assignees of patents corresponding to said nodes.
52. The computer program product of claim 51, wherein said assignee modifying display properties means comprises:
means, upon receipt of appropriate operator command, for enabling the computer to toggle between:
(i) modifying display properties of said nodes of said patent citation hyperbolic tree according to original patent assignee information; and
(ii) modifying display properties of said nodes of said patent citation hyperbolic tree according to current patent assignee information.
53. The computer program product of claim 50, wherein said modifying display properties means comprises:
means for enabling the computer to modify display properties of nodes of said patent citation hyperbolic tree according to time-based criteria.
54. The computer program product of claim 53, wherein said time-based criteria includes one of filing date, priority date, length of pendency, effective filing date, invention date, critical date, on-sale date, public disclosure date, and public use date.
55. The computer program product of claim 50, wherein said modifying display properties means comprises:
means for enabling the computer to modify display properties of nodes of said patent citation hyperbolic tree according to user-defined criteria.
56. The computer program product of claim 50, further comprising:
means for enabling the computer to display a legend that describes said user-selected criteria.
57. The computer program product of claim 44, further comprising:
means for enabling the computer to receive an operator command to display a patent represented in said patent citation hyperbolic tree; and
patent displaying means for enabling the computer to display said represented patent.
58. The computer program product of claim 57, wherein said patent displaying means comprises:
means for enabling the computer to display bibliographic information of said represented patent if said represented patent is not stored in a local repository; and
means for enabling the computer to display any combination of bibliographic information, text, and images of said represented patent if said represented patent is stored in a local repository.
59. The computer program product of claim 44, wherein said tree displaying means comprises displaying data in said patent citation hyperbolic tree such that at least some of said data is displayed in a portion of said patent citation hyperbolic tree, wherein said computer program logic further comprises:
user enabling means for enabling the computer to allow a user to traverse to another portion of said patent citation hyperbolic tree; and
dynamic presentation means, responsive to said user enabling means, for enabling the computer to dynamically present said data in said another portion of said patent citation hyperbolic tree.
60. The computer program product of claim 50, wherein said modifying display properties means comprises:
issue date modifying display properties means for enabling the computer to modify display properties of nodes of said patent citation hyperbolic tree according to at least one of issue date, patent number, inventors, title, serial number, U.S. classification, international classification, fields of search, references cited, primary examiner, assistant examiner, attorney, agent, law firm, priority information, related application information, number of claims, number of drawing pages, patent term, patent aging, and expiration date of patents corresponding to said nodes.
61. The computer program product of claim 60, wherein said display properties consist of at least one of a preselected color scheme, a preselected case sensitive scheme, a preselected typeface scheme, a preselected font scheme, a preselected underlining scheme, a preselected bolding scheme, a preselected italics scheme and a preselected type size scheme.
62. The computer program product of claim 60, wherein said display properties consist of at least one of a user-defined color scheme, a user-defined case sensitive scheme, a user-defined typeface scheme, a user-defined font scheme, a user-defined underlining scheme, a user-defined bolding scheme, a user-defined italics scheme and a user-defined type size scheme.
63. The computer program product of claim 51, wherein said display properties consist of at least one of a preselected color scheme, a preselected case sensitive scheme, a preselected typeface scheme, a preselected font scheme, a preselected underlining scheme, a preselected bolding scheme, a preselected italics scheme and a preselected type size scheme.
64. The computer program product of claim 51, wherein said display properties consist of at least one of a user-defined color scheme, a user-defined case sensitive scheme, a user-defined typeface scheme, a user-defined font scheme, a user-defined underlining scheme, a user-defined bolding scheme, a user-defined italics scheme and a user-defined type size scheme.
65. A system of displaying data, comprising:
means for accessing patent-related documents; means for accessing one or more groups each comprising any number of said patent-related documents;
means for automatically generating a hyperbolic tree containing data from any of said patent-related documents;
means for presenting said data in said hyperbolic tree such that at least some of said data is displayed in a portion of said hyperbolic tree;
means for enabling a user to traverse to another portion of said hyperbolic tree; and
means for dynamically presenting, responsive to said means for enabling a user to traverse, said data in said another portion of said hyperbolic tree.
66. The system of claim 65, wherein said patent related documents is comprised of at least one pre-selected patent-related document.
67. The system of claim 66, wherein said data is comprised of at least one type of data that has been pre-selected by a user.
68. A computer program product comprising a computer useable medium having computer program logic recorded thereon, said computer program logic comprising:
means for enabling a processor to access patent-related documents;
means for enabling a processor to access one or more groups each comprising any number of said patent-related documents;
means for enabling a processor to automatically generate a hyperbolic tree containing data from any of said patent-related documents;
means for enabling a processor to present said data in said hyperbolic tree such that at least some of said data is displayed in a portion of said hyperbolic tree;
means for enabling a processor to allow a user to traverse to another portion of said hyperbolic tree; and
means for enabling a processor to dynamically present, responsive to said means for enabling a processor to allow a user to traverse, said data in said another portion of said hyperbolic tree.
69. The computer program product of claim 68, wherein said patent related documents is comprised of at least one pre-selected patent-related document.
70. The computer program product of claim 69, wherein said data is comprised of at least one type of data that has been pre-selected by a user.
71. A method of displaying data, comprising the steps of:
(1) accessing patent-related documents;
(2) automatically generating a hyperbolic tree containing data from one or more of said patent-related documents;
(3) presenting said data in said hyperbolic tree such that at least some of said data is displayed in a portion of said hyperbolic tree;
(4) enabling a user to traverse to another portion of said hyperbolic tree; and
(5) dynamically presenting, responsive to step (4), said data in said another portion of said hyperbolic tree.
72. The method of claim 71, wherein said patent related documents in step (2) is comprised of at least one pre-selected patent-related document.
73. The method of claim 72, wherein said data in step (2) is comprised of at least one type of data that has been pre-selected by a user.
74. A system of displaying data, comprising:
means for accessing patent-related documents;
means for automatically generating a hyperbolic tree containing data from one or more of said patent-related documents;
means for presenting said data in said hyperbolic tree such that at least some of said data is displayed in a portion of said hyperbolic tree;
means for enabling a user to traverse to another portion of said hyperbolic tree; and
means for dynamically presenting said data in said another portion of said hyperbolic tree.
75. The system of claim 74, wherein said patent related documents is comprised of at least one pre-selected patent-related document.
76. The system of claim 75, wherein said data is comprised of at least one type of data that has been pre-selected by a user.
77. A computer program product comprising a computer useable medium having computer program logic recorded thereon, said computer program logic comprising:
means for enabling a processor to access patent-related documents;
means for enabling a processor to automatically generate a hyperbolic tree containing data from one or more of said patent-related documents;
means for enabling a processor to present said data in said hyperbolic tree such that at least some of said data is displayed in a portion of said hyperbolic tree;
means for enabling a processor to enable a user to traverse to another portion of said hyperbolic tree; and
means for enabling a processor to dynamically present said data in said another portion of said hyperbolic tree.
78. The computer program product of claim 77, wherein said patent related documents is comprised of at least one pre-selected patent-related document.
79. The system of claim 78, wherein said data is comprised of at least one type of data that has been pre-selected by a user.
80. A method of displaying data, comprising the steps of:
(1) accessing patent-related documents;
(2) accessing one or more groups each comprising any number of said patent-related documents;
(3) automatically generating a hyperbolic tree containing data from any of said patent-related documents;
(4) presenting said data in said hyperbolic tree such that at least some of said data is displayed in a portion of said hyperbolic tree;
(5) enabling a user to traverse to another portion of said hyperbolic tree; and
(6) dynamically presenting, responsive to step (5), said data in said another portion of said hyperbolic tree.
81. The method of claim 80, wherein said patent related documents in step (3) is comprised of at least one pre-selected patent-related document.
82. The method of claim 81, wherein said data in step (3) is comprised of at least one type of data that has been pre-selected by a user.
83. A system of displaying data, comprising:
means for accessing patent-related documents;
means for automatically generating a hyperbolic tree containing data from any of said patent-related documents; and
means for allowing a user to selectively focus on at least some of said data that is displayed in a portion of said hyperbolic tree.
84. The system of claim 83, further comprising:
means for enabling said user to traverse to another portion of said hyperbolic tree; and
means for dynamically presenting, responsive to said means for enabling, said data in said another portion of said hyperbolic tree.
85. The system of claim 83, wherein said patent related documents is comprised of at least one pre-selected patent-related document.
86. The system of claim 85, wherein said data is comprised of at least one type of data that has been pre-selected by a user.
87. A computer program product comprising a computer useable medium having computer program logic recorded thereon, said computer program logic comprising:
means for enabling a processor to access patent-related documents;
means for enabling a processor to automatically generate a hyperbolic tree containing data from any of said patent-related documents; and
means for enabling a processor to allow a user to selectively focus on at least some of said data that is displayed in a portion of said hyperbolic tree.
88. The computer program product of claim 87, wherein said computer program logic further comprises:
means for enabling a processor to enable said user to traverse to another portion of said hyperbolic tree; and
means for enabling a processor to dynamically present, responsive to said means for enabling processor to enable said user, said data in said another portion of said hyperbolic tree.
89. The computer program product of claim 87, wherein said patent related documents is comprised of at least one pre-selected patent-related document.
90. The computer program product of claim 89, wherein said data is comprised of at least one type of data that has been pre-selected by a user.
91. A method of displaying data, comprising the steps of:
(1) accessing documents related to one or more of patents, contracts, licenses, leases, notes, commercial papers, legal papers and financial papers;
(2) accessing one or more groups each comprising any number of said documents;
(3) automatically generating a hyperbolic tree containing data from any of said documents, wherein said hyperbolic tree illustrates one or more relationships between said documents; and
(4) allowing a user to selectively focus on at least some of said data that is displayed in a portion of said hyperbolic tree by performing a tree function.
92. The method of claim 91, further comprising the step of enabling said user to traverse to another portion of said hyperbolic tree.
93. A method of processing data, comprising the steps of:
(1) accessing at least one database of information representative of documents;
(2) accessing one or more groups, each of said one or more groups comprising any number of said documents represented in said at least one database;
(3) automatically processing at least one of said documents in at least one of said one or more groups;
(4) automatically creating a new temporary group during processing of a command;
(5) maintaining said new temporary group for future processing by converting said new temporary group to a permanent group; and
(6) automatically generating a hyperbolic tree containing data from any of said documents in said permanent group.
94. The method of claim 93, wherein at least one of said documents is related to one or more of patents, contracts, licenses, leases, notes, commercial papers, legal papers and financial papers.
95. The method of claim 93, further comprising the steps of:
(7) allowing a user to selectively focus on at least some of said data that is displayed in a portion of said hyperbolic tree by performing a tree function; and
(8) enabling said user to traverse to another portion of said hyperbolic tree.
96. A method of maintaining groups to facilitate in processing and presenting data, comprising the steps of:
(1) maintaining a group of a permanent type, wherein said permanent type can be either system defined or user defined, wherein said group of permanent type is comprised of any number of documents from at least one database;
(2) generating a group of a temporary type during processing of a command by automatically processing one or more of said documents in said group of permanent type in conjunction with information from at least one second database;
(3) allowing a user to maintain said group of temporary type for future processing by converting said group of temporary type to a group of permanent type; and
(4) automatically generating a hyperbolic tree containing data from any of said documents in said permanent group.
97. The method of claim 96, wherein one or more of said documents is related to one or more of patents, contracts, licenses, leases, notes, commercial papers, legal papers and financial papers.
98. The method of claim 96, further comprising the steps of:
(5) allowing a user to selectively focus on at least some of said data that is displayed in a portion of said hyperbolic tree by performing a tree function; and
(6) enabling said user to traverse to another portion of said hyperbolic tree.
99. A system of processing and presenting data, comprising:
means for accessing documents related to one or more of patents, contracts, licenses, leases, notes, commercial papers, legal papers and financial papers;
means for accessing one or more groups each comprising any number of said documents;
means for automatically generating a hyperbolic tree containing data from any of said documents, wherein said hyperbolic tree illustrates one or more relationships between said documents; and
means for allowing a user to selectively focus on at least some of said data that is displayed in a portion of said hyperbolic tree by performing a tree function.
100. The system of claim 99, further comprising means for enabling said user to traverse to another portion of said hyperbolic tree.
101. A system of processing and presenting data, comprising:
means for accessing at least one database of information representative of documents;
means for accessing one or more groups, each of said one or more groups comprising any number of said documents represented in said at least one database;
means for automatically processing at least one of said documents in at least one of said one or more groups;
means for automatically creating a new temporary group during processing of a command;
means for maintaining said new temporary group for future processing by converting said new temporary group to a permanent group; and
means for automatically generating a hyperbolic tree containing data from any of said documents in said permanent group.
102. The system of claim 101, wherein at least one of said documents is related to one or more of patents, contracts, licenses, leases, notes, commercial papers, legal papers and financial papers.
103. The system of claim 101, further comprising:
means for allowing a user to selectively focus on at least some of said data that is displayed in a portion of said hyperbolic tree by performing a tree function; and
means for enabling said user to traverse to another portion of said hyperbolic tree.
104. A system for maintaining groups to facilitate in processing and presenting data, comprising:
means for maintaining a group of a permanent type, wherein said permanent type can be either system defined or user defined, wherein said group of permanent type is comprised of any number of documents from at least one database;
means for generating a group of a temporary type during processing of a command by automatically processing one or more of said documents in said group of permanent type in conjunction with information from at least one second database;
means for allowing a user to maintain said group of temporary type for future processing by converting said group of temporary type to a group of permanent type; and
means for automatically generating a hyperbolic tree containing data from any of said documents in said permanent group.
105. The system of claim 104, wherein one or more of said documents is related to one or more of patents, contracts, licenses, leases, notes, commercial papers, legal papers and financial papers.
106. The system of claim 104, further comprising:
means for allowing a user to selectively focus on at least some of said data that is displayed in a portion of said hyperbolic tree by performing a tree function; and
means for enabling said user to traverse to another portion of said hyperbolic tree.
107. A computer program product comprising a computer useable medium having computer program logic stored there, wherein said computer program logic comprises:
means for enabling a computer to access documents related to one or more of patents, contracts, licenses, leases, notes, commercial papers, legal papers and financial papers;
means for enabling a computer to access one or more groups each comprising any number of said documents;
means for enabling a computer to automatically generate a hyperbolic tree containing data from any of said documents, wherein said hyperbolic tree illustrates one or more relationships between said documents; and
means for enabling a computer to allow a user to selectively focus on at least some of said data that is displayed in a portion of said hyperbolic tree by performing a tree function.
108. The computer program product of claim 107, wherein said computer program logic further comprises means for enabling a computer to allow said user to traverse to another portion of said hyperbolic tree.
109. A computer program product comprising a computer useable medium having computer program logic stored there, wherein said computer program logic comprises:
means for enabling a computer to access at least one database of information representative of documents;
means for enabling a computer to access one or more groups, each of said one or more groups comprising any number of said documents represented in said at least one database;
means for enabling a computer to automatically process at least one of said documents in at least one of said one or more groups;
means for enabling a computer to automatically create a new temporary group during processing of a command;
means for enabling a computer to maintain said new temporary group for future processing by converting said new temporary group to a permanent group; and
means for enabling a computer to automatically generate a hyperbolic tree containing data from any of said documents in said permanent group.
110. The computer program product of claim 109, wherein at least one of said documents is related to one or more of patents, contracts, licenses, leases, notes, commercial papers, legal papers and financial papers.
111. The computer program product of claim 109, wherein said computer program logic further comprises:
means for enabling a computer to allow a user to selectively focus on at least some of said data that is displayed in a portion of said hyperbolic tree by performing a tree function; and
means for enabling a computer to allow said user to traverse to another portion of said hyperbolic tree.
112. A computer program product comprising a computer useable medium having computer program logic stored therein, wherein said computer program logic comprises:
means for enabling a computer to maintain a group of a permanent type, wherein said permanent type can be either system defined or user defined, wherein said group of permanent type is comprised of any number of documents from at least one database;
means for enabling a computer to generate a group of a temporary type during processing of a command by automatically processing one or more of said documents in said group of permanent type in conjunction with information from at least one second database;
means for enabling a computer to allow a user to maintain said group of temporary type for future processing by converting said group of temporary type to a group of permanent type; and
means for enabling a computer to automatically generate a hyperbolic tree containing data from any of said documents in said permanent group.
113. The computer program product of claim 112, wherein one or more of said documents is related to one or more of patents, contracts, licenses, leases, notes, commercial papers, legal papers and financial papers.
114. The computer program product of claim 112, wherein said computer program logic further comprises:
means for enabling a computer to allow a user to selectively focus on at least some of said data that is displayed in a portion of said hyperbolic tree by performing a tree function; and
means for enabling a computer to allow said user to traverse to another portion of said hyperbolic tree.
115. A method of displaying data, comprising the steps of:
(1) accessing documents related to one or more of patents, contracts, licenses, leases, notes, commercial papers, legal papers and financial papers;
(2) accessing one or more groups each comprising any number of said documents;
(3) automatically generating a hyperbolic tree containing data from any of said documents, wherein said hyperbolic tree illustrates one or more relationships between said documents;
(4) receiving an operator command to display a document represented in said hyperbolic tree; and
(5) displaying said represented document.
116. The method of claim 115, wherein said data from any of said documents contain information related to characteristics or features of said documents.
117. A system of displaying data, comprising:
means for accessing documents related to one or more of patents, contracts, licenses, leases, notes, commercial papers, legal papers and financial papers;
means for accessing one or more groups each comprising any number of said documents;
means for automatically generating a hyperbolic tree containing data from any of said documents, wherein said hyperbolic tree illustrates one or more relationships between said documents;
means for receiving an operator command to display a document represented in said hyperbolic tree; and
means for displaying said represented document.
118. The system of claim 117, wherein said data from any of said documents contain information related to characteristics or features of said documents.
119. A method of displaying data, comprising the steps of:
(1) allowing a user to select a patent from a listing of patents;
(2) allowing said user to issue a citation analysis function command on said selected patent to a network client;
(3) representing a dialog box, by said network client, wherein said user identifies request specifics for said citation analysis function, wherein said request specifics comprise said selected patent and whether to perform a forward citation function or a backward citation function on said selected patent;
(4) operating, by an enterprise server, on said request specifics to generate a parent/child table;
(5) generating a citation analysis DAG, by said network client, corresponding to patent/child relationships in said parent/child table;
(6) automatically generating a hyperbolic tree, by said network client, that is based on said citation analysis DAG; and
(7) allowing said user to selectively focus on at least some of said data that is displayed in a portion of said hyperbolic tree.
120. The method of claim 119, further comprising the steps of:
(8) allowing said user to select a second selected patent by selecting a node in said hyperbolic tree;
(9) allowing said user to identify second request specifics for a second citation analysis function on said second selected patent to said network client;
(10) automatically generating a second hyperbolic tree, by said network client, that is based on said second selected patent, said citation analysis DAG, and said second request specifics; and
(11) allowing said user to selectively focus on at least some of said data that is displayed in a portion of said second hyperbolic tree.
121. The method of claim 119, wherein step (2) said user issues said command via a context-sensitive pop-up menu, a toolbar button or a menu bar.
122. The method of claim 119, wherein step (3) said request specifics further comprises a number of levels that should be cited in said forward citation function or said backward citation function .
123. The method of claim 119, wherein step (4) said enterprise server further generates a patent bibliographic information table.
124. The method of claim 123, wherein step (7) said data includes data from said patent bibliographic information table.
125. A method of displaying data, comprising the steps of:
(1) allowing a user to select a document from a listing of documents, wherein said selected document is related to one or more of patents, contracts, licenses, leases, notes, commercial papers, legal papers and financial papers;
(2) allowing said user to issue a relationship function command on said selected document to a network client;
(3) representing a dialog box, by said network client, wherein said user identifies request specifics for said relationship function, wherein said request specifics comprise said selected document;
(4) operating, by an enterprise server, on said request specifics to generate a relationship table;
(5) generating a DAG, by said network client, corresponding to relationships in said relationship table;
(6) automatically generating a hyperbolic tree, by said network client, that is based on said DAG; and
(7) allowing said user to selectively focus on at least some of said data that is displayed in a portion of said hyperbolic tree.
126. The method of claim 125, further comprising the steps of:
(8) allowing said user to select a second selected document by selecting a node in said hyperbolic tree;
(9) allowing said user to identify second request specifics for a second relationship function on said second selected document to said network client;
(10) automatically generating a second hyperbolic tree, by said network client, that is based on said second selected document, said DAG, and said second request specifics; and
(11) allowing said user to selectively focus on at least some of said data that is displayed in a portion of said second hyperbolic tree.
(Source: USPTO)
Find More Documents Like This
Download a PDF of this Document
We are pleased to offer a PDF download of this document free of charge. It may take a moment to prepare your download, so please be patient with longer documents.
Copyright © 2009-2012 IP.com. All Rights Reserved.
