WO2013136347A2 - Data management system - Google Patents

Abstract

Document engine of present invention provide for selecting a portion of a document within a document viewer and uploading the portion to a database from the document viewer. The selection of database, table and/or field may be made through a menu of the document viewer. Uploading the portion of the document is made to the selected field. The portion may be text. The document may be a patent document and the plurality fields may comprise related art, embodiment 1, embodiment 2, background, claims, expert comment, figure description. The document viewer may comprise at least one of web browser, text editor. A database with fields ' to store the different context data is provided. A search engine searches the key word in the different context field and provides the result based on the presence of the key word in the different context field.

Description

The patent Act 1970

(39 of 1970)

AND

Patent Rules 2003

Complete Specification

(Sec 10 and Rule 13)

The following specification particularly describes the invention and manner in which it is to be performed

Description

FIELD OF INVENTION

[001] The present invention relates generally to Data management system, particularly to Management of document data in a system.

RELATED ART

[002] Often a document contains information in sections with different relevance's. Patent is an example document in which information contains bibliographic data, patent specification and other data related to prosecution, assignments etc. Each of this data reveals specific information to determine the strength, utility and value of the patent. These data are available in different formats like images, pdf, word documents, etc. Patent specifications provided details on the patented technology. The patent specifications are written by following the format guidelines of the country of patent. Though, patent specifications exhibit common format like background, claim, abstract, etc., the manner in which the information is laid out in the patent specification differ significantly from patent to patent. Thus, it generally requires reading through sections of patent specification to understand patented technology, its strength, weakness applicability, scope etc. In a similar way, often the prosecution information and other details are studied (may be in addition) to further understand the scope of the patented technology.

[003] Another example of document is a technical product specification or data sheets. In that the information is spread in various sections providing different details of the products, technology used, performance, comparison etc., often these documents are accessed using a document engine such as document reader or editors. One example document engine is a text editor.

[004] A text editor is a program that allows user to open, view, and edit plain text files. Text editors are used by wide variety of people, for a wide variety of purposes. Software programmers and web developers use text editors to write and edit, in programming and markup languages. This is one of the primary purposes, of text editors, and many of the features of text editing software are built to help these users read and write code. However, text editors are ideal tools for anyone who needs to write quickly and simply, read source code, or create text files. With more advanced text editors come more advanced and useful features. Some of the features that the Existing Editors provided are as below: [005] Ability to cut, copy and paste which enables the duplication of the text within the file or between files. Ability to format the text with the help of formatting tools, indentation tools etc. Ability to undo and redo, which enables user to change or bring back to the last edit. Ability to highlight a piece of text in the editor to read it for further reference. Ability to insert hyperlink, look up synonyms, etc. when user right clicks mouse button.

[006] Interactive Text Editors: Some interactive text editors allow the manipulation of a set of files stored on the host machine by means of a terminal device such as a teletypewriter or a display-keyboard combination. The files may contain natural language text, computer programs, or alphanumeric data. Because editors frequently constitute the primary means of interaction of a person with the computer, they tend to subsume all kinds of secondary functions as well.

[007] The Editor's role in creating documents: Editors serve a variety of roles in preparing documents, including helping to plan the document, coordinating the work of writers, and supervising production; however, their fundamental and defining role is to improve the document by marking change in the draft they receive from the_*author. These changes include making large- -scale_organizational changes and rewriting whole passages, but editors unlike reviewers are responsible for style, grammar, usage, and mechanics, and so they mark a large number of small- grained changes.

SUMMARY

[008] A method for managing document data such as patent document and technology document is provided. Document data management segregates the data into different categories and saves the segregated information in the corresponding categories in the database. When there is a query for a particular keyword or context, the system analyzes the query and with the association of a technology library fetches the relevant data from the database and presents the query results in the order of relevancy of data. The Technology Data Management segregates the information related to a product or company into different categories and saves the segregated information in the corresponding categories in the database.

[009] The present invention also provides a text editor that enable user to select portion of the document and upload the selected portion to desired field in the database. The present invention also provides centralized client relation management system to manage patent services rendered to the client. [010] Text Editors of the present invention enables display of text information from one or more document format enables selection of text portion from the document, mapping selected text to relevant fields of database table and saving them to the fields in a database table. In one embodiment, user may select an appropriate database and a table. Certain portions of the displayed document that the user thinks to be saved as the information for respective fields of the database table can be selected from the document and just by right clicking on the selected portion, the user can map it to the relevant fields of the table. The user then selects the suitable menu items for uploading selected data into the respective database. This text editor also serves as a mini web browser for opening HTML files, where user enters the URL of the HTML files to be opened. The contents of the html document opened can be mapped to database table fields and saved.

[Oi l] According to another aspect of the present invention document Management System manages the organization's unstructured Patent Information which is available in diverse formats and location into a structured repository for easy administration, management, security and information retrieval. This will streamline access, eliminate bottleneck during patent searches, optimize security and maintain integrity. The system provides interfaces to upload patent data information into a central repository in a predefined data format for easy retrieval and analysis. It also provides ability to classify patents based on country, class and product areas for report generation and analysis. It also provides interface for case workers and/or analysts to document their understanding and upload analysis and supporting research documents. It also allows them to add keywords and further classify their analysis for easy retrieval in future. The system provides user management features along with authentication and authorization to secure patent information.

[012] According to another aspect, the data management system provides an integrated text based search engine to support indexing of patent information based on keywords, patent title, patent claims. The search engine will support indexing information from raw patent files and also from patent information repository; The search engine will support ranked searching, wildcard queries, proximity queries and fielded searching (e.g. Title, Patent Assignee). The search engine will support multiple index building, multi index searching and merging of results, the system also enables to upload Fields like Comments, Figure Description, Embodiments, and Perceived Background can be uploaded and saved in the patent database as Patent Analysis record. [013] Several embodiments of the present disclosure are described below with reference to examples for illustration. It should be understood that numerous specific details, relationships, and methods are set forth to provide a full understanding of the embodiments. One skilled in the relevant art, however, will readily recognize that the techniques can be practiced without one or more of the specific details, or with other methods, etc.

BRIEF DESCRIPTION OF DRAWINGS

[014] Figure 1 is a block diagram of an example environment in which patent data may be stored advantageously to extract the desired information.

[015] Figure 2 is a block diagram of patent data storage system in an embodiment.

[016] Figure 3 depicts manner in which patent data may be extract into database in an embodiment.

[017] Figure 4 shows the functional look of the editor with Database Interface.

[018] Figure 5 is a block diagram depicting the Architecture of Text editor for Database

Interface.

[019] Figure 6 is a user interface diagram showing the Main menu items of the text editor.

[020] Figure 7 is a user interface diagram illustrating the display of Database List from the Text Editor.

[021] Figure 8 is a user interface diagram showing the Login Form that appears when a specific database is selected.

[022] Figure 9 is a user interface diagram showing the Table list of selected Database.

[023] Figure 10 is a user interface diagram showing the Field list of selected table.

[024] Figure 11 is a user interface window showing Opening of a document.

[025] Figure 12 is a user interface diagram depicting the Mini Browser functionality in Text

Editor.

[026] Figure 13 is a user interface diagram showing the Selection of appropriate content and adding to the respective field.

[027] Figure 14 is a user interface diagram showing the Information Message displayed after the selected data is uploaded.

[028] Figure 15 is a user interface diagram showing the uploaded data in the MySQL editor.

[029] Figure 16 is a Screenshot of Text Editor's User Interface. ' [030] Figure 17 is a user interface window showing the saving a document. [031] Figure 18 is a user interface window showing the search feature in the text editor.

[032] Figure 19 is a flowchart illustrating the manner in which patents in the database may be fetched and presented based on search criteria.

[033] Figure 20A and 20B are examples result format.

[034] Figure 21 is a block diagram illustrating manner in which data related to product or technology can be stored in an embodiment.

[035] Figure 22 shows the components of the existing text editors.

[036] Figure 23 shows the components of the text editor with database interface.

[037] Figure 24 is a block diagram showing the overall architecture of a search engine.

[038] Figure 25 is a block diagram illustrating the architecture of the proposed methodology.

[039] Figure 26 is a screen shot of the login screen.

[040] Figure 27 is a screen shot of admin's home page.

[041] Figure 28 is a screen shot where a user can be created.

[042] Figure 29 is a screen shot showing the list of patents that have been stored in the database after analysis.

[043] Figure 30 is a screen shot of creating a new patent entry in the database by entering its bibliographic data.

[044] Figure 31 is a screen shot showing the editing of already saved patent information of a particular patent.

[045] Figure 32 is a screen shot for creating patent analysis entry for saved patents.

[046] Figure 33 is a screen shot of the webpage that is used to edit the patent information stored in the database.

[047] Figure 34 is a screenshot of webpage of PIMS for uploading bulk patent data.

[048] Figure 35 is a screen shot to search patent related data in patent database.

[049] Figure 36 is a screen shot for searching patent analysis related data based on keyword in the patent document.

[050] Figure 37 is a screen shot for editing the Patent Analysis data for the selected Patent that has been searched based on the keyword.

[051] Figure 38 is a screen shot showing other fields of the selected Patent when a search is made based on the keyword. [052] Figure 39 is a screen shot of webpage where analyzed files for the selected patent based on the keyword searched is uploaded.

[053] Figure 40 is a screen shot of the Text Editor's User Interface.

[054] Figure 41 is a block diagram illustrating CRM system architecture.

[055] Figure 42 shows the status tab.

DETAILED DESCRIPTION OF THE PREFERRED EXAMPLES

[056] The detailed description is provided with reference to patent and patent documents as an example environment in which various aspect of the present invention may be applied however the techniques described here may be extended to other environment by reading the disclosure provided herein. Accordingly, the example embodiments may not be construed to limit the scope of the present disclosure.

[057] The document data management, in case of patent data management in one embodiment, while analyzing the patent, segregates the patent data into different categories and saves the segregated information in the corresponding categories in the database. When there is a query for a particular keyword or context, the system analyzes the query and with the association of a technology library fetches the relevant data from the database and presents the query results in the order of relevancy of data. The system also provides a mechanism for going through the query results to understand the relevancy of data. In the example of Technology Data Management, the system segregates the information related to a product or company into different categories and saves the segregated information in the corresponding categories in the database. Another aspect of the present invention provides a text editor that enable user to select portion of the data and upload the selected portion to desired field in the database. Another aspect of the present invention provides centralized client relation management system to manage patent services rendered to the client.

[058] Figure 1 is a block diagram of an example environment in which patent data may be stored advantageously to extract the desired information. Block diagram is shown containing Patent 110, Segregation Engine 120, Database 130, Query Engine 140, Analysis and Presentation Module 150 and Technology Library 160. Each block is described below in further detail.

[059] Patent 110 represents patent data such as copy of the published patent, patent specifications, prosecution details, assignment details, licensing details, bibliographic data, citation details, litigation details (if the patent is litigated), patent owner details, activities of the patent owner and other details pertinent to determine the patent utility, strength, weakness, values, and factors influencing a particular business.

[060] Copy of the published patent may be in pdf, image, word, text, Html or any other format. The patent specification may corresponds to part of the patent information often referred to as "patent specification" in the art and/or any description about the invention being protected or details of such invention provided by the applicant to the patent office for grant of patent. Prosecution details may represent information related transaction made during the time Period between filing of application and the grant of patent. An example of prosecution details data is information file wrapper (IFW) made available by US patent office. Similarly other data referred above like bibliographic data, assignment details etc represents the piece of information identified by similar names/terminology in the art.

[061] Segregation Engine 120 extracts information in each data and assigns to a particular group of data. The particular group of data may be predefined and defined as such to serve a particular analysis purpose. Thus the segregation engine further separates the data content and also may add additional supporting information derived either manually or derived through application of logics and keywords. Database 130 stores the patent and technology data and also provides the interface to store and access the data.

[062] Query Engine 140 receives the search strategy on path 145 from analysis and presentation module 150 and generates appropriate query sentences using the syntax corresponding to implementation e of database 130. The query engine interacts with the database 130 through interface 134 to access the database. Interface 134 may be database interface consisting of set of directives, functions, logics, and other guidelines defined by database vendors or by database technology or program developers.

[063] Analysis and presentation module 150 receives the inputs on interface 180. Interface 180 may be a user interface provided to user for feeding the input. Interface 180 may receive input such as keyword, business strategy, sentences, technology phrases, documents and/or logic expressions that are fed using forms designed to receive various data needed for searching the database 130. Analysis and presentation module 150 performs analysis of the received input on the interface 180 and provides a search strategy to the query engine 140. Module 150 may consult technology library 160 to derive additional keywords and other factors to perform the analysis of the input received on interface 180. Technology Library 160 may maintain list of key words and its associations and relation with the corresponding technology. It may also store technology document such as white papers, product data sheets, user manuals etc.

[064] Analysis and presentation module 150 receives the search results and arranges the result based on the search strategy to provide a result in suitable form on the interface 190. Thus the result on the interface 190 may represents the order of relevance of the patent to the input received on interface and may include other information such as reason for assigning such order, the factors that are in favor and against to the desired feature provided as input on interface 180 etc. In order to make appropriate analysis of the search result and to provide a result suitable to make a business decision requires the database to be effectively designed to store the data along with the context. Accordingly, manner in which the data are stored along with the varying context are described below.

[065] Figure 2 is a block diagram illustrating the manner in which patent data may be separated and stored under different categories in an embodiment. Block diagram is shown comprising preliminary Data 210, abstract or front page 220, background 230, figure description 240, embodiments 250, claims 260, other documents 270, patent data dissector 280, patent data 290, claim keyword 295A, embodiment keyword 295B, background keyword 295C, and other keyword 295D. Each block is described below in further detail.

[066] Blocks 210, 220, 230, 240, 250, 260, and 270 represents data in the database tagged or indexed by categories accordingly in an embodiment. These categories may be selected such that information pertaining to the presence or absence of a keyword in the data of one or more categories may be used to determine the relevance of the patent to the search strategy.

[067] Blocks 295A-295D represents the categories in which keywords extracted from the sections of the patent data are stored in the Keyword Database 295. These keywords may also be generated and stored based on some of the keywords and its context in the patent data.

[068] Preliminary data 210 may represent category under which preliminary data about the patent may be stored. For example, bibliographic data (such title, patent number, citations, inventor name etc), list of forward citation, backward citation, reference recited in the patent, inventor name, Transaction history, etc.

[069] Abstract or FrontPage 220 represents the category under which abstract and other details generally published as front page may be stored. Background 230 may represents category of data under which the background information derived from the patent specification, such as motivation, prior art recognized etc may be stored. Figure description 240 represents the category under which description of the figures may be stored. Embodiments 250 may represent the category of the data in which example embodiments may be stored. Claims 260 may represent the category of data under which claims may be stored. Other documents 270 may represent the category of data under which data derived from other documents such as IFW, child patent, references recited in the patent, white paper by the owner of the patent pertaining to the patented technology, technical papers by inventors etc. Each category may be further subcategorized and the data may be stored accordingly.

[070] Patent data 290 corresponds to one or more data pertaining to the patent including patent copy, specification, analysis report of the patent by an analyst, legal opinion on the patent, related technology papers, white papers, product description etc. Patent data dissector 280 receives patent data and extract different contents and assigns to one or more categories. When a particular content is assigned to more than one category the content is store under respective more than one category. Patent dissector may receive patent data in the form of documents, images, pictures, web pages, codes etc. Patent data dissector 280 may rely on the keywords and its location in the document to determine the extent of the content to be extracted and also may determine the target category for storing the content based on the same keyword and relative location with other keywords.

[071] Editing is the process of selecting and preparing written, visual, audible, and film media used to convey information through the processes of correction, condensation, organization, and other modifications in various media, performed with an intention of producing a correct, consistent, accurate, and complete output. Editors are preferably used worldwide because of its extensive features to allow the users to modify and customize the document as per their needs. Existing Text Editors provide just the ability to edit, manipulate text information but they do not provide the ability to connect to the database on fly and upload the text data to the database.

[072] Editors are basically used to view, edit and read any kind of documents or text files. The editors are used by users worldwide for wide variety of purposes. These editors allow the users not only to view the document but also to modify them and with the help of the various editing tools that the editor provides.

[073] Existing editors enable users to cut copy and paste which enables the duplication of the text within the file or between files. It also allows the user to format the text with the help of formatting tools, indentation tools, but do not allow users to save the contents onto the database. This paves way to link the database to the editor making the user to perform a single action of viewing, selecting and saving the necessary contents onto the database.

[074] The text editor, with respect to present invention, enables extraction of image, text and any other data and placing them in the database, with user friendly menus and tools .And also to enable^'the user to customize menus and tools based on parameters such as type of contents being extracted, the database structure, and database interface and to view the database structures and database field for creating a workspace in which the contents are being extracted.

[075] Figure 3 represents an example user interface of an editor that enables reading and extracting patent content into the desired category while a patent analyst reads through the patent. The user interface 300 is shown containing a selection box 320, selection characters 360 and 370, and Menu 350. Each item is described below in further details.

[076] The selection characters 360 and 370 (in this case [ ]) determine start and end of the content that can be defined by the reader for extraction. The user may place these characters at —t-he-desired- _^locations,—D.ifIerent-charac.ter_se s_rriay be defined for different categories. For example, start and end of content defined by "["and"]" may be assigned to category claims. Similarly, the start and end defined by "{"and"}" may be assigned to abstracts. Thus, for each category a pair of distinct characters may be defined.

[077] Selection box 320 selects the content within the box for extraction. The selection box 320 is presented and the size of the selection box may be varied on the editor using combination of keys or mouse buttons.

[078] Menu 350 enable user to select the category to which the content with in the selection box may be stored. The menu 350 may be presented on the editor upon use of any predefined keys or mouse button. In one embodiment, a right click on the mouse may provide the menu 350.

[079] Figure 4 shows a possible functional look of the editor with Database Interface. Figure 4B shows highlighter tool that allows the user to select or highlight a portion of document that is needed for their future review. Figure 4C shows Find tool that allows the user to search for a string in the document. Figure 4D shows Save tool that allows the user to save the editing document that is currently in use. Figure 4E shows Underline tool that allows the user to underline a sentence or a portion of string in the document. Figure 4F shows Select tool that allows the user to select a certain image or a portion of the document. Figure 4G shows Copy tool that allows a user to copy a certain portion of the string or sentence in the document. Figure 4H shows the Zoom- in tool that allows the user to maximize the size of the document. Figure 41 shows the Zoom-out tool allows the user to minimize the size of the document. Figure 4J shows Spelling and Grammar tool that allows the user to verify the spellings and the grammar in the sentences of the document in use. Other than the above mentioned tools there may be other menus which provide various other functionalities.

[080] The "Basic file handling Menu" options may include File, Edit, and Review and Help options. The File option allowing, opening a file, printing a file, saving a file and some other basic operations like import etc. The Edit option allows one to copy, paste and other operations. The Review option allows adding a comment to the document. The Help option enables the user with some assisted documentation or guidance about the usage of the editor. Other than the mentioned tools there may be other menus that are on the editor which provides exclusive feature of connecting to the database,^' placing or uploading the contents to the database i.e., the "Database Configuration Menu".

[081 ] In an embodiment, proposed text editor provides the necessary menu options for selecting a relational database to connect to, selecting a table to upload information to, performing the basic actions of opening a document, editing, manipulating, mapping selected text portion to database table field and saving the contents of the mapped portions of the document to database table..

[082] The Software Architecture of text editor for database interface is as shown in Figure. 5. Text editor serves as a medium for user to open a text file or a HTML document and also serves as database interface providing a link to database using JDBC connectivity as shown in Figure. 5. Thus user can upload the contents from the document to the database available in the server with the help of suitable buttons like Upload and Update that are provided in the text editor.

[083] As an example for this application, Patent Database is used for uploading data. The patent database is a repository of patent information. The patent document in context is read, viewed and selected. Selected contents are uploaded to the selected table and fields in the Patent database.

[084] This software package thus reduces the time that the user was taking to upload contents of the patent document to the patent database via sql inserts since only the upload or update button will connect and then save the mapped document contents to the table fields in the database. Also, this text editor enables the user to open HTML files through a mini web browser, map content to database table field and upload the content to database.

[085] Example working of Proposed Text Editor: In one of the embodiment, technologies used for implementing the text editor are:

[086] Java Swing: Swing is used for creating the user interface.

[087] MySQL: MySQL is used as database.

[088] JDBC: Java Database Connectivity is used for connecting to the database.

[089] Detailed description of the proposed Text Editor:

[090] Apart from other important menus, text editor contains three main menu items, i.e. DBList, TableList and FieldList as shown in Figure. 6. In one embodiment, how the menu items are populated with the appropriate values and working of text editor is described in this section.

[091] Example Database List: When the text editor is opened for use databases available in database server are first listed by making use of the JDBC API:

getMetaData() . getCatalogs();

[092] The database list will be populated into DBList menu item provided in the menu bar of the text editor.

[093] The databases available in the server can be viewed via DBList menu item provided in the text editor as shown in Figure. 7. User selects appropriate patent database for a particular session for uploading relevant patent data to respective fields of that patent database.

[094] Display of login dialog when a specific database is selected:

[095] In one of the embodiments, once user selects a particular database, Login dialog as shown in Figure. 8 appears where the text editor validates the user's credentials against the database user list. If login is unsuccessful, an error message will be displayed indicating that username and password is incorrect. If login is successful, database connection will be established between the selected database and text editor by using the below code:

Conn = DBConnectionManager.getconnection(DBURL, username, password);

[096] Where DBURL is the URL of the database selected, username is the name of the database user that is retrieved from the login form, password is the password retrieved from the login form. For example:

Conn = DBConnectionManager.getconnection (jdbc:mysql://localhost:3306/patentdb, root, pwd); [097] The DBConnectionManager class loads the JDBC database driver and returns a database connection. MySql JDBC driver is loaded by calling Class.forName() which accepts name of the driver class - com.mysql.jdbc.Driver as a String parameter. Then DriverManager class getConnection(DBURL, username, password) method is called, which returns a connection object indicating the database connection is successful. After connection is established, the method getMetaData() retrieves a DatabaseMetaData object that contains metadata about the database to which this Connection object represents a connection, along with list of tables, procedures, triggers etc.

[098] Granting privileges to user: The GRANT statement grants privileges to MySQL user accounts. GRANT also serves to specify other account characteristics such as use of secure connections and limits on access to server resources.

[099] Normally, a database administrator first uses CREATE USER to create an account, then GRANT to define its privileges and characteristics. For example:

CREATE USER 'root' IDENTIFIED BY 'pwd';

GRANT ALL ON patentdb.* TO 'root^'localhosf;

"^"[0100] Table list of selected Database: After connection . is established successfully, TableList menu item provided in the menu bar of the text editor is populated with the tables of the selected database using the method:

getTables(DBname, null, "%", null);

[0101] For example: getTables(patentdb, null, "%", null);

[0102] This method retrieves a description of the tables available in the given catalog. Only table descriptions matching the catalog, schema, table name and type criteria are returned. They are ordered by TABLE_TYPE, TABLE_CAT, TABLE_SCHEM and TABLE_NAME. Each table description has the following columns:

[0103] TABLE CAT => table catalog (may be null).

[0104] TABLE SCHEM => table schema (may be null).

[0105] TABLE_NAME => table name.

[0106] TABLE TYPE => table type.

[0107] User selects appropriate table from TableList menu item for a particular session which is as shown in Figure. 9. [0108] Field list of selected table: After table is selected from the TableList menu by the user,

FieldList menu item provided in the menu bar of the text editor is populated with the fields of the selected table using the below method:

getColumns(DBname, null, Tablename, "%");

[0109] For example: getColumns(patentdb, null, patent, "%");

[01 10] This method retrieves a description of table columns available in the specified catalog. Only column descriptions matching the catalog, schema, table and column name criteria are returned. They are ordered by TABLE_CAT, TABLE_SCHEM, TABLE_NAME, and ORDINAL_POSITION. Each column description has the following columns:

[011 1] TABLE_CAT => table catalog (may be null).

[0112] TABLE SCHEM => table schema (may be null).

[01 13] TABLE_NAME => table name.

[0114] COLUMN_NAME => column name.

[01 15] The mandatory fields are identified by checking whether the database column is nullable. The mandatory fields in the selected table are marked with an icon (*) placed next to it in FieldList menu as shown in Figure. 10.

[01 16] The mandatory fields are automatically loaded into popup menu item which appears when right click mouse event is triggered by user. The non mandatory fields may be selected by user from the FieldList menu if specific data is to be uploaded to those fields. All the selected non mandatory fields will be appended into popup menu item along with the mandatory fields.

[0117] Thus, user can easily map the patent data to the respective fields of the relational database table. Initially, user selects the patent data from the document. Selected patent data is mapped to relevant fields when the right button of mouse is fired.

[01 18] Opening a Document: In an embodiment, Figure. 11 shows the dialog window that is enabled when user selects the Open option in the text editor. User uses this dialog window to browse files. User selects either a text file or a HTML file and opens it.

[01 19] Mini Browser functionality in Text Editor: Mini Browser functionality in Text Editor is shown in Figure. 12. The basic components needed for creating a mini browser are as follows:

[0120] A text field for entering new HTTP URLs and three buttons namely Back, Forward and Go. A JTextPane for displaying the current page. [0121] User enters the HTTP URL of the HTML files to be opened in the text field and selects Go button. The HTML file corresponding to that URL will be opened in the text editor's JTextPane. The user can navigate between the pages by just clicking on the Hyperlink in the document. The Back button and Forward button are used to go back and forward to the HTTP URLs.

[0122] Hyperlink Events: JTextPanes fire a type of event called a HyperlinkEvent. Typically, this event is fired when the user clicks on a hyperlink in the currently displayed document; the program normally responds by loading a new page. To support this event type, a related event class and a listener interface are available in the javax.swing.event package.

[0123] Selecting appropriate content and adding to the respective field: In another embodiment, as shown in Figure. 13, user selects certain portion of the patent data to be loaded into specific fields. Once the right click mouse event is triggered by user, popup menu containing the fields of the patent database appears. User then selects appropriate field from the popup menu to which the selected patent data is to be stored.

[0124] After loading all the mandatory field data and other non-mandatory field data in to a buffer, user can then upload all the patent data to the respective fields in the patent database via Upload button in toolbar of the text editor.

[0125] Information Message obtained after the selected data is uploaded: After user selects Upload button in toolbar of the text editor, an information message indicating that the data is uploaded successfully is displayed as shown in Figure. 14.

[0126] Viewing uploaded data through MySQL editor: After information message indicating that the data is uploaded successfully is displayed, user can log into MySQL console and can check the uploaded data in the respective database as shown in Figure. 15.

[0127] If user wants to update patent data for the non mandatory fields from the text editor, user short lists the non mandatory fields from the FieldList menu item for a particular session to which the patent data is to be updated. These short listed menu items will appear when user selects the right click mouse button. User selects certain portion of the patent data to be loaded into specific fields by firing left click mouse button and dragging the mouse till required data is highlighted. Once the right click mouse event is triggered by user, popup menu containing user selected fields of the patent database appears. User then selects appropriate field from the popup menu to which the selected data is to be stored. After loading all the data in to a buffer, user can then update all the data to the respective fields in the patent database via Update button in toolbar of the text editor.

[0128] Screenshot of Text Editor's Graphical User Interface: In yet another embodiment, the user interface of Text Editor is shown in Figure. 16.

[0129] The text editor supports the following features: Opening and saving a text file or a HTML file via menu bar items or toolbar buttons.

[0130] Cut, copy, and paste via toolbar buttons.

[0131] Searching for a word in the document.

[0132] Mini web browser functionality for opening HTML files, where user enters the URL of the_HTML_files-to.-be_opened—

[0133] Ability to view database structures via menu bar items.

[0134] Ability to upload or update patent data to respective fields of the patent database.

[0135] Saving a document:

[0136] In another embodiment, Figure. 17 shows the dialog window that is enabled when user selects the Save option in the text editor. User uses this dialog window to save the files. User enters the file name to be saved and selects the location where the file should be saved.

[0137] Finding a word in a document: In another embodiment, when user selects the Find option in the text editor a Find dialog will be displayed as shown in Figure. 18. User has to enter the word to search. If the word does not exist in the document, a small window pops up indicating no string found. If the search is successful, the document window highlights each and every occurrence of the searched word in the document as shown in Figure. 18.

[0138] Here, a text editor with database interface is implemented. This text editor enables the user to view the database structures through the text editor itself. It also enables the user to extract the necessary contents from the document and upload the contents onto the database by providing database interface which is unique of its kind. This application may be used in areas where extensive document analyses are performed.

[0139] Figure 22 shows the components of the existing system. The Editor serves as a medium to view, review and highlight certain portions of the document, in the current scenario, a patent. The user is thus provided only the ability to view the patent or other documents via editor. User can then make use of the Patent Manager, where the user enters the necessary details or information and finally can save the data entered onto the database. Thus the user performs two steps: one to view the contents of the patent document and the other to perform the data entry in and then save it onto the database through Patent Manager.

[0140] Figure 23 shows the components of the text editor with database interface according to present invention. The Editor serves a medium for the user to view, modify, highlight and select certain portions of the any document, a patent document. These functions can be performed by the various menu options available. Certain portions of the data that the user wants to save, the patent information for the Patent in the current scenario, may be selected from the document and just by right clicking on the selected portion, the user can send it to the respective field on the record in the database. Thus reducing the time the user would take to save the contents to the database via various tools, in the absence of the above invention.

[0141] Some of the features of the invention include, text editor providing the user the ability to view, edit and extract information from files such as Word documents, Pdf files or basic text files. This ability is provided with the help of "Basic File handling Menus", "Database Configuration Menus" and a set of editing tools, enabling the user to connect to the available database on the server, from the editor and also enabling the user to customize menus and tools based on parameters such as type of contents being extracted. The text editor described above may be integrated with the document data management system in one embodiment.

[0142] Figure 19 is a flowchart illustrating the manner in which patents in the database may be fetched and presented based on search criteria in an embodiment. Flowchart begins with step 1901 and control passes to step 1910. In step 1910, patent data management system receives input. The input may contain, key words or concepts defined using a paragraphs, or any other input that may be received and the intention of the user may be derived. The control then passes to step 1920. In step 1920, the patent data management system checks if the input contains keyword. If the input contains keyword, the system searches for the relative keywords which might relate to the keyword that the system has received as an input and flow moves to step to 1940.

[0143] In step 1930, the patent data management system checks if the input contains a context. If the input contains context, the system generates a keyword list that matches the context and the flow moves to step 1940. The steps^ 1920 and 1930 represent few examples of the input that might be received by the patent data management system. [0144] In step 1940, the patent data management system searches the patent sub-sections based on the keywords. The patent data management system might search for the patent data stored in different categories for the input keyword.

[0145] In step 1950, based on the search, the list of results may be generated. The list might include the patent details like patent number, patent abstract, patent description and claim. In step 1960, the patent data management system, in association with the analysis engine, determines the relevance of the result to the context or keyword. In step 1970, the list of patents based on the relevance to context/keyword might be fetched by the presentation engine. The flow chart ends in step 1999.

[0146] Figure 20A and 20B illustrates an example format of result. In one embodiment, the presentation module displays the Patent No_. as the first column, Relevance (based on the location of the input) as the second column, different sections of the patent (Expert comments, embodiment, Claim etc.) where the input keyword might be found as shown by 2010 in the figure. The example result format might also provide different options for going through the section of the patent to understand the relevancy of data. In one embodiment, the click of mouse or the scroll of the mouse on the data fetched 2080 might open a pop up window 2020 or a separate window displaying few lines or paragraphs of fetched data containing the highlighted keyword 2040.

[0147] Figure 21 is a block diagram illustrating the manner in which the product/company data may be separated and stored under different categories in an embodiment. Block diagram comprises of Company 2110, Products 2120, Catalogues 2130, Data sheets 2140, Expert comments and analysis reports 2150, Keywords 2160, other documents 2170, Product/Company data dissector 2180, Product/company data 2190.Each block is described below in further detail.

[0148] Blocks 2110, 2120, 2130, 2140, 2150, 2160, and 2170 represents data in the database tagged or indexed by categories accordingly in an embodiment. These categories may be selected such that information pertaining to the presence or absence of a keyword in the data of one or more categories may be used to determine the relevance of the product/company to the search strategy.

[0149] Company 2110 may represent the company details like name of the company. Product 2120 may represent the product details like name of the product, version of the product. Catalogues 2130 may represent the product catalogue with details like product features, the prerequisites for the product etc. Datasheets 2140 may represent the technical characteristics of the product. Expert Comments/ Analysis report 2150 may represent the feedback about the product by the people who might have been using the product. Keywords 2160 may represent the keywords which might lead to the product listing.

[0150] Other Documents 2170 may represent the external links which might provide additional information about the product. Product Company data 2190 corresponds to data pertaining to the product/company including company details, product details like its version, specification, technical requirements.

[0151] Product/Company data dissector 2180 receives Product/Company data and extracts different contents and assigns to one or more categories. When a particular content is assigned to more than one category the content is stored under respective more than one category. Product/Company data dissector 2180 may rely on the keywords and its location in the document to determine the extent of the details to be extracted and also to determine the target category for storing based on the same keyword and relative location with other keywords.

[0152] As described in above paragraphs, present invention provides editor enabling extraction of data and placing them on the appropriate fields in the database. The text editor aspect of the present invention is further described below in contrast to existing text editor.

[0153] The Software Architecture of Patent data (information) management system in one embodiment of the present invention is shown in Figure 24. In one embodiment, the example architecture Struts implementation of Model 2 is used and it employes a specific type of servlet, called on action servlet, and one or more actions and action mappings to implement the controller. It also uses a specific type of Java bean, called a form bean. As illustrated in figure 25, the Web server at run time contains both the view and controller components of a Model 2 Web application, while a third tier (which is usually outside of the Web server) contains the model.

[0154] Example Search Engine core: Modern search applications have wonderful diversity. Some run quietly, as a small component deeply embedded inside an existing tool, searching a very specific set of content (local files, email messages, calendar entries, etc). Others run on a remote Web site, on a dedicated server infrastructure, interacting with many users via Web browser or mobile device, perhaps searching a product catalog or known and clearly scoped set of documents. Some run inside a company's intranet and search a massive collection of varied documents visible inside the company. Still others index a large subset of the entire web and must deal with unbelievable scale both in content and in simultaneous search traffic. Despite all this variety, search engines generally share a common overall architecture, as shown in figure 24.

[0155] Example Login Screen: Login screen is the initial page of the application as shown in figure 26. The Patent Analyst/ PIMS Admin use this page to key-in the login credentials and gain access to the application. The password which is entered as plain text is encrypted using one way hash function provided by java.security.MessageDigest using SHA-512 algorithm. The generated cipher text is compared to the previously stored password. If there is a match then the user is deemed authenticated and the landing page is displayed.

[0156] Example Admin's home page: Figure 27 shows admin's home page when the login is successful. Admin can perform the operations like creating a new user, Create/List patents, Search through the Patents, Search through the Patent Analysis and edit the patents/patent analysis.

[0157] Example Create User Screen: Figure 28 shows the screenshot for creating a user with Patent Analyst role. It takes a user id and plain text password. While persisting the password to the database the plain text is encrypted using one way hash function provided by ^"java.security.MessageDigest using SHA-512 algorithm and stored in the database.

[0158] Example List Patents screen: This is used to fetch all patent information from the database and display 10 patents per page as shown in figure 29. The user can navigate to the rest of the list using the 'Next' / 'Previous' links. The patent list can also be sorted based on Patent Number, Filing Date and Last Updated columns. Only the patent metadata is displayed in the table and to view detailed information the user has to click on the Patent Number hyper link. The details regarding that patent will be displayed in the edit patent page.

[0159] Example Create Patent Screen: This is used to key in the patent information manually by the Patent Analyst and save this information into the system. Mandatory fields like patent number, patent title, application number, filing date, priority date, first inventor, assignee and US class should be keyed in along with abstract, background and claims as shown in the figure 30. This information is then saved to the patent database.

[0160] Example Edit Patent Information Screen: This is used to edit previously stored patent information. Except for the patent number all the other fields are editable as shown in the figure 31. [0161] Example Create Patent Analysis Screen: Figure 32 is a screen shot of a web page that is used to key in the patent analysis information manually by the Patent Analyst and save this information into the system. Fields like Comments, Figure Description, Embodiments, and Perceived Background should be keyed in along with other fields as shown. This information is then saved to the patent database.

[0162] Example Edit Patent Analysis Screen: Figure 33 is a screen shot of the web page that is used to edit previously stored patent analysis information. Except for the patent number all the other fields are editable as shown.

[0163] Example Patent Bulk Data Upload Screen: Figure 34 is a screen shot of webpage that can be used to upload bulk patent information from an xlsx/xls file. The patent information in the spreadsheet may be in the following format: The first row is skipped since this will typically have the header fields. The second row will be processed based on the assumption that: column A will contain the Patent Number; column B will contain Patent Title; Column C will contain Filing Date; Column D will contain Publication Date; Column E will contain Inventors; Column F will contain Assignee; Column G will contain Application Number; Column H will contain US Class; Column I will contain International Class; Column J will contain Field of Search; Column K will contain Abstract and Column L will contain Claim 1

[0164] Example Patent Database Search: Figure 35 is a screen shot that illustrates how Patents can be searched that has been keyed-in by the Patent Analyst. User selects any of the search fields and the search conditions that are shown in figure 35 and enters the keyword to be searched in the patent database.

Example algorithm for indexing newly added patent records into Search Index:

Precondition: Newly added patent records will have LAST_INDEXED_TSP as 0

OPEN SEARCH Index in CREATE OR APPEND mode

Get Index Writer

startLimit = 0

endLimit = 10

totalRecordCount = getMaxRecord Count of newly added records from Patent Table

WHILE(TRUE)

{ Get Patent Number, Title, Abstract Information from Patent Table where LAST_INDEXED_TSP = 0 LIMIT startLimit, endLimit

WHILE (records ! = NULL)

{

CREATE NEW Search Document doc

Add New Field - Patent Number to doc

Add New Field - Title to doc

Add New Fields - Abstract to doc

Add doc to Index Writer

Update LAST_INDEXED_TSP = CURRENT_TSP

}

IF (endLimit > totalRecordCount)

{

BREAK

}

ELSE

{

startLimit = endLimit

endLimit = endLimit + 10

}

}

Algorithm for indexing updated patent records into Search Index:

Precondition: Updated patent records will have LASTJJPDATED TSP > LASTJNDEXED_TSP

OPEN Search Index in CREATE OR APPEND mode

Get Index Writer

startLimit = 0

endLimit = 10

totalRecordCount = getMaxRecord Count of updated records from Patent Table

WHILE(TRUE)

{ Get Patent Number, Title, Abstract Information from Patent Table where LAST UPDATED TSP > LAST_INDEXED_TSP LIMIT startLimit, endLimit

WHILE (records != NULL)

{

CREATE SEARCH TERM T for Patent Number

Delete documents containing TERM T using Writer from the index

CREATE NEW SEARCH Document doc

Add New Field - Patent Number to doc

Add New Field - Title to doc

Add New Fields -Abstract to doc

Add doc to Index Writer

Update LAST_INDEXED_TSP = CURRENT TSP

}

IF (endLimit > totalRecordCount)

{

BREAK

}

ELSE

{

startLimit = endLimit

endLimit = endLimit + 10

}

}

[0165] Example Patent Analysis Search: Figure 36 is a screen shot of the webpage of PIMS illustrating how stored Patent Analysis is searched which has been keyed in by the Patent Analyst after spending hours of study and analysis. User selects any of the search fields and the search conditions that are shown in figure 35 and enters the keyword to be searched in the patent analysis. The patents that have the keyword entered will be displayed.

[0166] Example fields involved are as follows: Embodiments: A specific, disclosed example of how an inventive concept that is more generally stated elsewhere in the disclosure of a patent application or patent can be put into practice. [0167] Embodiments Keyword: These are the keywords that are related to the embodiments section of the patent being analyzed. Perceived Background: It includes the background of the patent document as well as the user's understanding about the analyzed patent data. PB Keyword: These are the keywords that are related to the Perceived Background section of the patent being analyzed. Applicable Field: It contains the areas/fields in which the patent currently being analyzed can be applied to. AF Keyword: These are the keywords that are related to the Applicable Field of the patent being analyzed.

[0168] Figure 37 is a screen shot that shows the fields of the patent when a user selects any patent from the displayed list. User can also update any infonnation regarding the patent in the relevant fields.

[0169] Figure 38 shows some other fields of the patent that has been selected by the user from the displayed list. User can update any information regarding the patent in the relevant fields and can save that information onto the database.

[0170] Figure 39 is a screen shot of web page where users can upload the analyzed patent files. These analyzed patent files are uploaded into the database by making use of this application. The features supported in PIMS are:

• Improved internal operations:

> Reduce time to complete patent procedures.

> Improves the day to day operations of case workers and Analysts.

Improves flow of information in organization.

• Improved, faster and more flexible search:

Retrieve files by any word or phrase in the document - full text search (a capability impossible with paper documents).

• Improved Security - flexible control over sensitive information and auditing.

• No lost files:

All patent information is centrally stored when being viewed.

• Disaster Recovery:

> The central repository will be backed up on disk and tape drives.

• Productivity Improvement and competitive edge over other competitors.

[0171] Uploading Patent data through Text Editor: Text Editors are basically used to display, edit documents or text files. Editors are widely used because of their ready to use, easy to use features. In the current context, a text editor is defined to be an editor capable of at least selecting a text part in the document as text. Existing text editors allow the user to view the document in context, read the document and modify the document. Existing text editors do not interface to the relational database and do not provide the ability to save the contents of the document onto the relational database as and when the user is reading through the document.

[0172] This paves way to interface the relational database through the text editor itself making the user to perform a single action of viewing, selecting and by suitable menu items saving the necessary contents onto the relational database.

[0173] Text editor software package integrated with the database management, enables display of text information from one or more document format (html, ASCII text file), selection of text portion from the document, mapping selected text to relevant fields of relational database table and saving them to the fields in a relational database table. Initially the user selects an appropriate relational database and a table. Certain portions of the displayed document that the user thinks to be saved as the information for respective fields of the relational database table can be selected from the document and just by right clicking on the selected portion, the user can map it to the relevant fields of the table. The user then selects the suitable menu items for uploading selected data into the respective relational database. The text editor also serves as a mini web browser for opening HTML files, where user enters the URL of the HTML files to be opened. The contents of the html document opened can be mapped to relational database table fields and saved.

[0174] Screenshot of Text Editor's Graphical User Interface: The user interface of Text Editor is shown in Figure 40. The text editor supports the following features:

• Opening and saving a text file or a HTML file via menu bar items or toolbar buttons.

• Searching for a word in the document.

• Mini web browser functionality for opening HTML files, where user enters the URL of the HTML files to be opened.

• Ability to view database metadata via menu bar items.

• Ability to upload or update patent data to respective fields of the patent database.

[0175] Manner in which Features of the present invention may be incorporated as CRM for Patent Service is described below in further detail. In CRM system in the current invention for patent servicing, clients can access all his previous works, submit draft, check invalidity and patentability, search for patents using keywords with and/or conditions, review the service that is currently being rendered to him. Separate space is given to each client in the huge database, which can be accessed by him anytime.

[0176] In this system the client should be able to log in and carry out his work. A robust authentication technique may be included to specify the access rights. Client's access to the available information in the CRM system has to depend upon the access rights given. The architecture of the CRM with respect to the above invention is as shown in figure 41 and is explained subsequently.

[0177] Client Layer: The system is developed by using Browser/ Server structure as shown in figure 10. In this structure, the user interface is fully realized through the web browser, and some business logic is achieved in the front-end, but the main business logic is implemented on the server side implementation. The whole client layer of this system is based on Web browser, it can accesses middle layer of the system via Https protocol.

[0178] Presentation Layer: The main purpose of this layer is to provide logical view for business data. This layer is mainly of the routines of the language using which the entire system is developed. Business Layer: This layer is mainly responsible for business logic implementation of the system. This involves providing various services. Management of all the services provided by the patent servicing company such as Invalidity, Patentability, Drafting, Evidence of Use, Freedom to Operate, Mining, Portfolio and others will be implemented here.

[0179] System Data Layer: It stores the system's business data and supporting data. A separate database is maintained for each and every customer, so that he can view his work or the previously rendered services.

[0180] Login page may open first where user id and password is furnished by the client. Various robust authentication techniques may be implemented in this regard. The landing page may contain various tabs such as, home tab, work submit tab, status tab, search tab. Home tab displays user name, client organization associated to, client entity details, and other details. Work submit tab contains multiple sections: searching, drafting, India patent office, Non generic, dropdown for each section, corresponding to the service type. Each of these sections have various forms, with various information going into them. Status tab contains Client Id, our Id etc as shown in figure 42. [0181] Each action of the client triggers an event, for which an automated email may be sent to all the concerned persons in the client company. For example, if the client files a patent, an email is sent to them automatically with the details of the deadlines. Each client can take a look at their work anytime they want to and can check the status of the work i.e. the service being provided. This is achieved by maintaining a separate database for each and every client. The search tab contains searching of the patents or any work done previously to that client, by using patent number or name or keywords.

[0182] Further, functionality of any of the existing CRM system may also be enhanced to include the feature of the present inventions described in above paragraphs. Accordingly some of the existing CRM systems are briefly introduced below. Further, manner in which such existing CRM system may be used for implementing the features of the present invention is described subsequently.

[0183] While various embodiments of the present invention have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of the present invention should not be limited by any of the above described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.

Claims

Claims

I/We Claim,

1) A method comprising:

selecting a first part of a document within a document viewer: and

uploading the first part of the document to a first database from the document viewer;

2) The method of claim 1 further comprising:

selecting the first database from a plurality of databases from a menu of the document viewer;

selecting a first table from a plurality of table in the first database;

selecting a field in the first table from a plurality of fields in the first table; and uploading the first part of the document into the first field.

3) The method of claim 2, wherein the first part of the document is a text.

4) The method of claim 3, wherein the document is a patent document and the plurality fields comprise, related art, embodiment 1, embodimenetn2, background, claims, expert comment, figure description.

5) Method of claim 4, wherein the document viewer comprise at least one of web browser, -text-editor-:—

6) A document engine comprising:

a database selector for selecting a database;

a document viewer displaying a document;

a part selector selecting a part of the document; and

a upload mechanism configured to upload the part of the document to the database.

7) The document engine of claim 6, wherein the part selector further comprising:

a visual indicator enabling the selection of the part; and

a buffer to store the part, wherein the upload mechanism uploads the part upon a event trigger.

8) The document engine of claim 7, wherein the document comprise one of text, HTML, pdf.

9) The document engine of claim 8, wherein the database selector further comprising;

a first menu comprising plurality of databases;

a second menu comprising plurality of tables in the database; and

a third menu comprising plurality of fields of the database, wherein the selecting the database comprise selecting the database from the plurality of databases, selecting a table from the plurality of the tables and sleeting a field from the plurality of fields. 10) The document engine of claim 9, wherein the plurality of fields comprise at least one of related art, embodimentl , embodimenetn2, background, claims, expert comment, figure description.

11) A patent management system comprising;

a database comprising plurality of fields to store patent data, wherein each filed representing a context of the patent document;

a document editor displaying the patent document, wherein the document editor configured to select the content of the patent document and upload to one or more fields; a search engine configured to search a key word in each plurality of the fields;

a report generator providing a list of patent comprising the keyword ranked based on the field in which the key word is determined to be present.

12) The patent management system of claim 11, wherein the plurality of field comprises at least related art, embodimentl , embodimenetn2, background, claims, expert comment, figure description.

Date: 13-03-2013

(Omprakash N Sringeri)