Patent document creation device, method, computer program, computer-readable recording medium, server and system

Abstract

To provide a patent document creation device that reduces a time taken for creating a patent document.SOLUTION: A processor 100 for a patent document creation device includes: a screen constitution unit that provides a user with a claim creation screen through an input / output interface; a constituent management unit that manages information for constituents constituting an invention; a text input element management unit that manages a constituent explanation input element as a text input element to which an explanation and a restriction relating to the constituent are input, and extracts a part of a text input to the constituent explanation input element in response to user's input as an automatic completion keyword, and then replaces the automatic completion keyword with a constituent item generated based on the information for the constituent corresponding to the automatic completion keyword to output it to the constituent explanation input element; and a claim input processing unit that receives and manages through the claim creation screen a number of a claim, a type of a claim, a number of a cited claim, a category of an invention and an explanation relating to the constituent input by the constituent explanation input element.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to a patent document drafting device, a method, a computer program, a computer-readable recording medium, a server, and a system. [Background technology]

[0002] Patent documents can be understood to include patent specifications, arguments, amendments, etc., as documents that should be prepared based on the description requirements set forth in the Patent Act.

[0003] For example, a patent specification is a document that expresses the technical idea that an inventor seeks to protect based on the description requirements stipulated in the Patent Act, and may be prepared to include the title of the invention, background art, a brief description of the drawings, a detailed description of the invention, and the scope of claims, etc. Generally, patent specifications are prepared by patent attorneys or other writers with a high level of understanding of technology and patent law using a predetermined document preparation program.

[0004] In most countries, including the United States, Europe, Korea, Japan, and China, the Microsoft® Office product family, Word, is the primary document creation program. In Korea, for example, the Korean Intellectual Property Office's Electronic Document Creation Software (KIPDS) is used. The KIPDS provides a structure window, allowing documents to be created in accordance with the requirements of the Patent Act and its subordinate laws.

[0005] Although these document creation programs have functions for inserting symbols, figures, and tables, they are basically text-based programs, and the creator must enter all content related to the invention directly by typing on a keyboard, which results in the problem that it takes a long time to create a single patent specification.

[0006] In addition, because a huge amount of paperwork is required, relying solely on the preparer's memory and typing, the prepared patent specifications often contain various types of deficiencies that do not meet the description requirements set forth in the Patent Act, and the invention is not clearly explained. This must be addressed as a loss of time and cost for both the preparer and the Patent Office that examines the patent specifications.

[0007] To prevent this, proposals have been made to provide a separate program (e.g., a Word add-in program) or a function in a document creation program (e.g., the "claim error check" function in the Patent Office's electronic document creation software) that checks for incomplete descriptions in patent specifications.

[0008] However, such programs or functions perform post-processing after the patent specification has been fully prepared, which requires the writer to first prepare and complete the patent specification and then fix any problems discovered during the checking process, which is a hassle, and further increases the time required to complete the patent specification.

[0009] Meanwhile, the patent laws of each country require that patent documents be prepared and submitted in a designated language. Therefore, patent documents prepared in a language other than the designated language must be translated into the language designated by the patent law of the country where they are to be submitted. For example, if a U.S. patent application is filed in Korea claiming priority under the Paris Convention, a translation from English to Korean is required, and if a Korean patent application is filed in Japan claiming priority under the Paris Convention, a translation from Korean to Japanese is required.

[0010] Patent documents to be translated, such as patent specifications, are documents that protect technical ideas and are composed of descriptions of the latest technology. Furthermore, because patent specifications are both technical documents and rights documents, if an incorrect translation later affects the scope of patent rights, it can lead to irreparable problems. Therefore, patent documents must be translated very accurately and faithfully to the original text.

[0011] However, due to various practical limitations such as cost and time, such translation work is often carried out by translators who lack sufficient knowledge and experience of technology and patent law. For example, when the task of translating patent specifications and filing applications is delegated to an agent such as a patent office, the translation of the patent specification is not carried out by the agent, but is usually outsourced to a third party, a freelance translator or translation agency. As a result, problems often arise where the technical content of the patent document is not translated accurately or the translation does not conform to the strict description requirements required by patent law. Summary of the Invention [Problem to be solved by the invention]

[0012] The embodiments of the present invention are proposed to solve the above problems, and aim to provide a patent document drafting device, method, computer program, computer-readable recording medium, server, and system that can reduce the time required to draft patent documents.

[0013] The present invention also aims to provide a patent document drafting device, method, computer program, computer-readable recording medium, server, and system that can prevent incomplete descriptions that violate the description requirements required by the Patent Act when drafting patent documents. [Means for solving the problem]

[0014] A patent document drafting device according to one embodiment of the present invention may include: a screen configuration unit that provides a user, via an input / output interface, with a claim drafting screen for drafting claims included in the scope of claims, which are provided as items in the content of a patent document; a component management unit that receives, via the input / output interface, information on components that constitute an invention as specific objects that can be included in the content of a patent document and that can be described in text, and manages the information on the components; a text input element management unit that manages component description input elements, which are text input elements that are provided on the claim drafting screen and into which the user inputs descriptions and limitations on components that constitute the invention as part of the content of a claim, and that extracts, in response to the user's input via the input / output interface, a portion of the text input into the component description input element as an auto-complete keyword, and then replaces the auto-complete keyword with a component item generated based on the information on the component that corresponds to the auto-complete keyword, and outputs the extracted text to the component description input element; and a claim input processing unit that receives, via the claim drafting screen, and manages the data that constitutes the claim, including the claim number, the claim type, the cited claim number, the invention category, and descriptions on the components input by the component description input element. [Effects of the Invention]

[0015] The patent document drafting apparatus, method, computer program, computer-readable recording medium, server, and system according to one aspect of the present invention have the advantage of reducing the time required to draft a patent document.

[0016] Furthermore, when preparing patent documents, it is possible to prevent incomplete descriptions that violate the description requirements required by the Patent Act. [Brief explanation of the drawings]

[0017] [Figure 1] FIG. 1 is a diagram showing a patent document drafting system according to an embodiment of the present invention. [Figure 2]FIG. 2 is a diagram showing a schematic configuration of the patent document drafting device and the patent document drafting server shown in FIG. [Figure 3] FIG. 3 is a diagram showing an example of a processor configuration of the patent document preparation device and the patent document preparation server in FIG. [Figure 4] FIG. 4 is a diagram showing an example of the memory configuration of the patent document preparation device and the patent document preparation server in FIG. [Figure 5] FIG. 5 is a diagram showing an example of a case management screen of a patent document preparation application according to an embodiment of the present invention for providing the first service. [Figure 6] FIG. 6 is a diagram showing an example of the patent document creation screen of the patent document creation application in FIG. [Figure 7] FIG. 7 is a diagram showing an example of the component management screen of the patent document creation application in FIG. [Figure 8] FIG. 8 is a diagram showing an example of the auto-completion function realized by the patent document creation application in FIG. [Figure 9] FIG. 9 is a diagram showing an example of a change in the auto-complete block due to a change in the element information realized by the patent document creation application in FIG. [Figure 10] FIG. 10 is a diagram showing an example of the basic description creation screen of the patent document creation application in FIG. [Figure 11] FIG. 11 is a diagram showing an example of a screen for creating a brief description of drawings in the patent document creation application in FIG. [Figure 12] FIG. 12 is a diagram showing an example of a claims display screen on the patent document creation screen of the patent document creation application in FIG. [Figure 13] FIG. 13 is a diagram showing an example of creating an independent claim on the claim creation screen of the patent document creation application in FIG. [Figure 14] FIG. 14 is a diagram showing an example of creating new claims and dependent claims on the claim creation screen of the patent document creation application in FIG. [Figure 15] FIG. 15 is a diagram showing an example of a claim correction screen of the patent document creation application in FIG. [Figure 16] FIG. 16 is a diagram showing an example of a description requirement examination result screen of the patent document creation application in FIG. [Figure 17] FIG. 17 is a diagram showing an example of a detailed description creation screen of the patent document creation application in FIG. [Figure 18] FIG. 18 is a diagram showing an example of the insertion character string selection screen of the patent document creation application in FIG. [Figure 19] FIG. 19 is a diagram showing an example of the element description creation screen of the patent document creation application in FIG. [Figure 20] FIG. 20 is a diagram showing an example of the drawing management screen of the patent document creation application in FIG. [Figure 21] FIG. 21 is a diagram showing an example of an idiomatic expression management screen of the patent document preparation application in FIG. [Figure 22] FIG. 22 is a diagram showing an example of a setting management screen of the patent document creation application in FIG. [Figure 23] FIG. 23 is a diagram showing an example of a download file that can be downloaded after a patent document is created via the patent document creation application in FIG. [Figure 24] FIG. 24 is a diagram showing an example of a case management screen and an original file registration screen of a patent document preparation application according to an embodiment of the present invention for providing the second service. [Figure 25] FIG. 25 is a diagram showing an example of the original data editing screen of the patent document creation application in FIG. [Figure 26] FIG. 26 is a diagram showing an example of the component selection screen of the patent document creation application in FIG. [Figure 27] FIG. 27 is a diagram showing an example of the patent document creation screen of the patent document creation application in FIG. [Figure 28]FIG. 28 is a diagram showing an example of a component management screen and a component translation registration screen of the patent document creation application in FIG. [Figure 29] FIG. 29 is a diagram showing an example of a component selection screen called up on the component management screen of the patent document drafting application in FIG. [Figure 30] FIG. 30 is a diagram showing an example of the automatic completion function realized by the patent document creation application in FIG. [Figure 31] FIG. 31 is a diagram showing an example of the translation creation screen of the patent document creation application in FIG. [Figure 32] FIG. 32 is a diagram showing an example of a screen in which the translation creation screen in FIG. 31 provides a machine translation service. [Figure 33] FIG. 33 is a diagram showing an example of the translation result screen and the first translation example search screen of the patent document creation application in FIG. [Figure 34] FIG. 34 is a diagram showing an example of a search screen of the patent document creation application in FIG. [Figure 35] FIG. 35 is a diagram showing an example of a download file that can be downloaded after a patent document is created via the patent document creation application in FIG. DETAILED DESCRIPTION OF THE INVENTION

[0018] The present invention can be modified in various ways and can have various embodiments, and specific embodiments will be illustrated in the drawings and described in detail. The advantages and features of the present invention, as well as methods for achieving them, will become clearer with reference to the following detailed embodiments in conjunction with the drawings. However, the present invention is not limited to the embodiments disclosed below, and can be realized in various forms.

[0019] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the description with reference to the drawings, the same or corresponding components are designated by the same reference numerals, and redundant description thereof will be omitted. In addition, when describing the present invention, if it is determined that a detailed description of related known configurations or functions may obscure the gist of the present invention, the detailed description thereof will be omitted.

[0020] In the following examples, terms such as "first," "second," etc. are not limiting but are used to distinguish one component from another. In the following examples, singular terms include plural terms unless the context clearly indicates otherwise. In the following examples, terms such as "comprise" or "have" mean the presence of a feature or component described in the specification and do not preclude the possibility that one or more other features or components may be added. In the drawings, the size of components may be exaggerated or reduced for ease of explanation. For example, the size, shape, and thickness of each component shown in the drawings are arbitrarily depicted for ease of explanation, and the present invention is not necessarily limited to the illustrated examples.

[0021] In the following description, "patent document" may be understood to include a patent specification, written argument, written amendment, etc., which are documents to be prepared in accordance with the description requirements set forth in the Patent Act. Patent documents may also be understood to include documents prepared by translating a patent document prepared in a language (e.g., English or Japanese in the case of the Korean Intellectual Property Office, hereinafter referred to as the "second language") other than the language designated by the patent office to which the patent document is to be submitted (e.g., Hangul in the case of the Korean Intellectual Property Office, hereinafter referred to as the "first language"). Patent documents may also be understood to include translations of documents issued by the patent office (e.g., Office Actions, Notices of Refusal, Notices of Decision of Refusal, etc.), review opinions regarding such actions, and translations of review opinions.

[0022] In addition, in the following description, "creating" a patent document can be understood as the act of a user inputting the necessary content into a patent document and completing the patent document, and includes all acts such as inputting, modifying, and deleting data necessary to complete a patent document, such as text, symbols, images, etc. related to the generation and editing of a patent document.

[0023] In the following description, "management" of data or information can be understood as a concept that includes input, storage, modification, deletion, etc. of data or information. In the following description, "management" of a specific object can be understood to include not only control of the object, but also management of the data or information contained in the object.

[0024] In the following description, a user interface (UI) may be understood as a physical or virtual medium for temporary or permanent access that allows a user to interact with a patent document preparation application. The UI may be understood to include all physical hardware and logical software that allows a user to interact with a patent document preparation application.

[0025] FIG. 1 is a diagram showing a patent document drafting system 1 according to an embodiment of the present invention.

[0026] 1, a patent document drafting system 1 according to an embodiment of the present invention may include a patent document drafting device 10 and a patent document drafting server 20. The patent document drafting device 10 and the patent document drafting server 20 may be connected to each other via a network 30 so as to be able to transmit and receive data to and from each other.

[0027] In this embodiment, the patent document drafting system 1 is provided to enable a user to prepare a patent document, and the user can quickly and accurately prepare a patent document using the patent document drafting system 1. The patent document drafting system 1 can provide the user with various functions for preparing a patent document via the patent document drafting device 10, and such functions can be realized by either the patent document drafting device 10 or the patent document drafting server 20, or by the interaction between the patent document drafting device 10 and the patent document drafting server 20.

[0028] For example, the patent document drafting system 1 may provide a service that allows a user to create a patent document in a first language or a second language in a format specified by a patent office, a service that allows a user to translate a patent document created in a second language or the first language into the first language or the second language, or both services. As a specific example, the patent document drafting system 1 may provide a user with one or more services from a service that creates a patent specification in a first language, a service that creates a patent specification in a second language, a service that creates a translated specification by translating a patent specification created in a first language into a second language, and a service that creates a translated specification by translating a patent specification created in a second language into the first language.

[0029] In the following description, a "patent document drafting service" may be understood to be provided by one or more of the patent document drafting system 1, the patent document drafting device 10, and the patent document drafting server 20. For example, a "patent document drafting service" may be understood as a function or a set of functions provided to a user via the input / output interface 19 (FIG. 2) of the patent document drafting device 10 so that the user can draft a patent document.

[0030] In the following description, a "case" may be understood as a unit of object created by a user to create a patent document. "Case information" may be understood to include basic information related to the patent document and information entered during the process of creating the patent document. For example, a user may create a case for creating a patent specification using the patent document drafting system 1 and enter basic information such as the case's control number, client, deadline, etc., as well as data to be entered as the content of the patent specification.

[0031] Meanwhile, the patent document drafting system 1 can provide the created patent document to the user as a file that can be read by the client who requested the creation of the patent document using a predetermined program or that can be submitted directly to the Patent Office. For example, the patent document drafting system 1 can provide a function that allows the user to download the created patent document as a file with a doc or docx extension that can be read by Microsoft's Word program, a file in a specific format that can be submitted to the Patent Office (for example, an XML-based file with an hlt or hlz extension that can be read by the Korean Patent Office's electronic document drafting software), a PDF file, an html file, etc.

[0032] In this embodiment, the patent document drafting system 1 will be described as providing a service for preparing patent specifications and patent translations. For ease of explanation, the service for preparing patent specifications will be referred to as the first service, and the service for preparing patent translations will be referred to as the second service. That is, the patent document drafting system 1 according to this embodiment may provide both the first service and the second service. However, the concept of the present invention is not limited thereto, and the patent document drafting system 1 may provide only the first service or only the second service. The patent document drafting system 1 may also provide services for preparing patent documents other than patent specifications and patent translations, such as written opinions and written amendments. As another example, the patent document drafting system 1 may translate documents issued by the Patent Office (e.g., notices of reasons for refusal, notices of decision of refusal, etc.), prepare review opinions for such documents, and provide services for translating review opinions.

[0033] Furthermore, the patent document drafting system 1, the patent document drafting device 10, and the patent document drafting server 20 may selectively include only the necessary components from among the components described below depending on the services to be provided.

[0034] The patent document drafting device 10 is a device provided to allow a user to input the content of a patent document, and may be a fixed or mobile terminal implemented as a computing device. For example, the patent document drafting device 10 may be a computer, laptop, tablet PC, smartphone, mobile phone, wearable device, etc. The concept of the present invention is not limited to these examples, and the patent document drafting device 10 may be any terminal that allows a user to input information necessary for the preparation of a patent document and has the function of displaying the information to the user. In the following, content described with the user as the subject may be understood as content described with the patent document drafting device 10 as the subject.

[0035] The patent document drafting server 20 enables a user to draft a patent document by communicating with the patent document drafting device 10 via the network 30. The patent document drafting server 20 may be a computing device that receives commands, code, files, data, content, services, etc. from the patent document drafting device 10 or provides them to the patent document drafting device 10. The patent document drafting server 20 may be implemented as either a virtual server or a physical server, or a combination thereof, and the type of server does not limit the scope of the present invention. For example, the patent document drafting server 20 may be implemented as a virtual server host (Virtual Private Server).

[0036] The patent document drafting server 20 can store, process, and manipulate data sent from the patent document drafting device 10 and send the results to the patent document drafting device 10. The patent document drafting server 20 can also perform a predetermined operation based on the data sent from the patent document drafting device 10 and send the results to the patent document drafting device 10. The patent document drafting server 20 can also provide data, content, services, etc. requested by the patent document drafting device 10. The patent document drafting server 20 can also perform a predetermined function requested by the patent document drafting device 10 or send commands to the patent document drafting device 10 to cause the patent document drafting device 10 to perform a predetermined function. The patent document drafting server 20 can also communicate with other servers provided by third parties at the request of the patent document drafting device 10 and send the results to the patent document drafting device 10.

[0037] The patent document drafting device 10 and the patent document drafting server 20 may communicate with each other via a network 30 using a wireless or wired communication method. Furthermore, the patent document drafting device 10 may be provided so as to be able to communicate with other patent document drafting devices 10 or other patent document drafting servers 20 via the network 30. Furthermore, the patent document drafting server 20 may be provided so as to be able to communicate with other patent document drafting devices 10 or other patent document drafting servers 20 via the network 30. In this embodiment, the network 30 serves to connect the patent document drafting device 10 and the patent document drafting server 20 so that they can transmit and receive data, and the communication method and type of the network 30 are not limited. For example, the network 30 may provide a connection path so that the patent document drafting device 10 can connect to the patent document drafting server 20 and then transmit and receive data.

[0038] Meanwhile, the patent document drafting device 10 may include or run an application (hereinafter referred to as a "patent document drafting application") that is provided to enable a user to create a patent document. That is, the patent document drafting device 10 may provide a patent document drafting service to a user via the patent document drafting application. The patent document drafting application may be provided as an operating system provided in the patent document drafting device 10, as a function of the operating system, or as an application that can be driven by the operating system, or as a function of an application that can be driven by the operating system.

[0039] For example, the patent document drafting application may be installed from a computer-readable recording medium or downloaded and installed from the patent document drafting server 20. In this case, the patent document drafting server 20 may store files and program source for installing the patent document drafting application and provide them to the patent document drafting device 10 upon request from the patent document drafting device 10. Alternatively, the patent document drafting application may not be installed independently, but may be realized as one operating mode of an application that can be installed on the patent document drafting device 10.

[0040] For example, the patent document drafting application may be any application capable of displaying a web page implemented based on a web browser or HTML, and may output a screen for providing the patent document drafting service to a user. As an example, the patent document drafting application may be a web application. In this case, the patent document drafting server 20 may provide the patent document drafting device 10 with a static web page and / or a dynamically generated web page in a format that can be output by the patent document drafting application in response to a request from the patent document drafting device 10. The web page output by the patent document drafting device 10 may include a script for providing the patent document drafting service.

[0041] As another example, the patent document preparation application may be a word processor, and the patent document preparation function may be built into the word processor or provided in the form of an add-in program. In the latter case, the patent document preparation server 20 may store an add-in program that can be installed on the patent document preparation device 10 and provide it to the patent document preparation device 10 upon request from the patent document preparation device 10.

[0042] The functions of the patent document drafting device 10 or functions related to patent document drafting described below can be understood to be realized by a patent document drafting application unless otherwise specified.

[0043] In this embodiment, the patent document drafting device 10 is a communications terminal capable of using web services in a wired or wireless communication environment, and the patent document drafting server 20 is a server running a web server program that allows the patent document drafting device 10 to connect via a specific URL in a wired or wireless communication environment. In this embodiment, the patent document drafting application is a web application that can be executed via a web browsing application, such as a web browser. Specifically, a user can connect to the patent document drafting server 20 via a specific URL assigned to the patent document drafting server 20 using a web browser installed in the patent document drafting device 10. The patent document drafting device 10 can load a web page for patent document drafting provided by the web server installed in the patent document drafting server 20 and provide it to the user as the patent document drafting application. In other words, a web browser can function as the patent document drafting application. Therefore, in this embodiment, the patent document drafting application can be understood as a web browser that loads a specific web page provided by the patent document drafting server 20.

[0044] The above example is merely one embodiment of the present invention. As described above, the patent document drafting device 10, the patent document drafting server 20, and the patent document drafting application may be configured in various ways, and the scope of the present invention is not limited to the above embodiment. For example, the patent document drafting application of the patent document drafting device 10 uses a web browser, but it may also be implemented as an application that can be run offline by storing data in the patent document drafting device 10. The patent document drafting server 20 provides a web page that functions as the patent document drafting application. The web page may include a responsive web page or an adaptive web page that can display a corresponding screen when connected to various types of devices. The patent document drafting server 20 may also provide the patent document drafting application in the form of a mobile native application or a hybrid application. The patent document drafting device 10 may also be configured to run a patent document drafting application provided by desktop application software. Depending on the embodiment, the patent document drafting device 10 may operate independently without communicating with the patent document drafting server 20. The patent document drafting device 10 may simply perform the function of displaying a screen, with data storage and processing all performed by the patent document drafting server 20. As described above, the patent document drafting device 10, the patent document drafting server 20, and the patent document drafting application can be configured in various ways within the scope of maintaining the characteristic concept of the present invention.

[0045] FIG. 2 is a diagram showing a schematic configuration of the patent document drafting device and the patent document drafting server shown in FIG.

[0046] Referring to FIG. 2, the patent document drafting device 10 and the patent document drafting server 20 may include processors 100, 200, memories 14, 24, communication modules 18, 28, and input / output interfaces 19, 29.

[0047] The processors 100, 200 may be configured to process computer program instructions by performing basic arithmetic, logic, and input / output operations. The instructions may be provided to the processors 100, 200 from the memories 14, 24 or the communication modules 18, 28. Alternatively, the instructions may be provided to the processors 100, 200 via a bus, which is a communication channel between the components of the patent document production device 10 and the patent document production server 20.

[0048] The processors 100 and 200 can perform various functions necessary for patent document creation, such as input / output of data, data processing, data management, and communication using the network 30, and specific components of the processors 100 and 200 for this purpose will be described below with reference to the drawings. The components of the processors 100 and 200 can be functional modules implemented by program code stored in the memories 14 and 24.

[0049] The memories 14, 24 may include computer-readable storage media, such as volatile storage devices like random access memory (RAM) and non-volatile permanent mass storage devices like read-only memory (ROM) and disk drives. The memories 14, 24 may store at least one program code that may function as an operating system or a patent document drafting application. The processors 100, 200 may load the program code stored in the memories 14, 24 to implement the patent document drafting service. Such program code may be loaded from another computer-readable storage medium (e.g., a DVD, a memory card, etc.) or transmitted from another device via the communication modules 18, 28 and stored in the memories 14, 24.

[0050] The memories 14 and 24 may also be provided with databases 140 and 240 that can store data necessary for providing patent document preparation services. In other words, the memories 14 and 24 may be understood to include the databases 140 and 240. The databases 140 and 240 may be databases independently constructed using software, or may be any type of storage location capable of storing data. For example, the databases 140 and 240 may be data storage locations that are installed as part of an application or linked to a specific application. Specifically, in the case of the patent document preparation device 10, the database 140 may be a database provided by a web browser, and may be, for example, one or more of web storage, web SQL database, and indexed database (hereinafter referred to as "web DB") provided as HTML5 functions. The database 140 of the patent document preparation device 10 may also include additional data storage locations other than the web DB. The databases 140 and 240 may also be provided in independent file formats, and data management may be possible only through a specific application or a specific protocol.

[0051] In this embodiment, the database 140 of the patent document drafting device 10 will be described as including a web database. Such a web database can store at least several megabytes (MB) and at most several tens of megabytes, allowing it to store sufficient data necessary for patent document drafting. This allows the patent document drafting device 10 to effectively manage confidential technical features to be included in a patent document within the patent document drafting device 10, without transmitting them to the patent document drafting server 20 via the network 30. In this embodiment, confidential data can be understood as data that may affect the patent registration of a patent document. For example, it can be understood as data that, if made public, may affect the determination of the novelty and inventive step of a patent specification.

[0052] In addition, the patent document drafting application can store data in the patent document drafting device 10 without using the network 30, and can therefore provide users with security features that are substantially the same as those of conventional word processors such as Microsoft's "WORD." Furthermore, the patent document drafting device 10 can encrypt and store technical features that require confidentiality in a web DB, in which case it can provide users with security features that are even better than those of a word processor.

[0053] The databases 140 and 240 may have various configurations capable of storing data necessary for patent document creation, and may be implemented as one or more tables or a combination of tables in one or more databases. Depending on the embodiment, the databases 140 and 240 may also be implemented in a form in which data is stored as a combination of key data and value data. Specific components of the databases 140 and 240 will be described below with reference to the accompanying drawings.

[0054] Meanwhile, the memories 14, 24 may be provided physically in multiple locations, or may be provided as a physical device integrated with the processors 100, 200. Furthermore, the memories 14, 24 may be provided as physically or logically independent devices and connected to a device in which the processors 100, 200 are installed to form a single device 10, 20 as a whole. The patent document creation device 10 and the patent document creation server 20 are not limited to the physical or logical configuration of the processors 100, 200, the memories 14, 24, and other devices.

[0055] The communication modules 18 and 28 may provide a function for the patent document production device 10 and the patent document production server 20 to communicate with each other and with other devices or servers via the network 30. For example, data input by a user via the patent document production device 10, a request generated by the processor 100 of the patent document production device 10, a response to a request sent from the patent document production server 20, etc. may be transmitted to the patent document production server 20 via the communication module 18. In addition, data generated by the processor 200 of the patent document production server 20, a request generated by the processor 200 of the patent document production server 20, a response to a request sent from the patent document production device 10, etc. may be transmitted to the patent document production device 10 via the communication module 28.

[0056] The input / output interfaces 19, 29 may be understood to include both a physical hardware interface and a logical software interface as components that input data from a user and output data provided by the processors 100, 200, memories 14, 24, communication modules 18, 28, etc. to the user. For example, the input / output interfaces 19, 29 may include input devices such as a keyboard, mouse, microphone, camera, etc., and output devices such as a speaker, display, etc. As another example, the input / output interfaces 19, 29 may include a device that integrates input and output into one, such as a touchscreen, or an input tool such as a touch pen.

[0057] A user can input data for patent document preparation through the input / output interfaces 19, 29, particularly the input / output interface 19 of the patent document preparation device 10, while checking the data he or she has input or checking data provided by the processor 100 or the memory 14. In other words, the input / output interfaces 19, 29 can receive data input for patent document preparation from the user and output data for patent document preparation to the user.

[0058] FIG. 3 is a diagram showing an example of the configuration of the processor 100 of the patent document drafting device 10 and the patent document drafting server 20 in FIG.

[0059] Referring to FIG. 3, the processor 100 may include a common processing unit 100a that provides functions commonly required for the first service and the second service, a first processing unit 100b that provides functions for the first service, and a second processing unit 100c that provides functions for the second service. In this embodiment, the processor 100 is described as being divided into the common processing unit 100a, the first processing unit 100b, and the second processing unit 100c. However, the concept of the present invention is not limited to a configuration in which the common processing unit 100a, the first processing unit 100b, and the second processing unit 100c are physically or logically separated. For example, the processor 100 may be realized as a single integrated control unit rather than being divided into the common processing unit 100a, the first processing unit 100b, and the second processing unit 100c. Furthermore, depending on the embodiment, if the patent document creation device 10 provides only the first service or the second service, the second processing unit 100c or the first processing unit 100b may be omitted. In this case, the common processing unit 100a is not provided separately, and the components of the common processing unit 100a and the components of the first processing unit 100b or the second processing unit 100c may be realized as a single integrated control unit. Also, the common processing unit 100a, the first processing unit 100b, and the second processing unit 100c may be understood as being conceptually separated, and components belonging to any of the common processing unit 100a, the first processing unit 100b, and the second processing unit 100c may be understood as being included in another set or as being included in multiple sets depending on the embodiment.

[0060] The common processing unit 100a may include one or more of a screen configuration unit 101, a data management unit 102, a case management unit 103, a component management unit 104, an auto-completion list generation unit 105, a text input element management unit 106, a drawing management unit 107, a description requirement review unit 108, a download file generation unit 109, a setting management unit 110, an external service collaboration unit 111, a user management unit 112, a data communication unit 113, and a change content management unit 114.

[0061] The screen configuration unit 101 may configure the structure and content of a screen displayed to a user via the patent document preparation application. The screen configured by the screen configuration unit 101 may be provided to the user via the input / output interface 19. The screen structure may be understood as a web page divided into multiple regions, and the content may be understood as multimedia information and web components, such as text, images, and video, displayed on the entire screen or in each region. The content may also provide multimedia information to the user, allow the user to input data or commands, and include a UI that allows the user to perform predetermined operations on the screen. In this embodiment, the UI may be understood to include components provided so that the user can recognize information via the patent document preparation application and input data or issue commands via the patent document preparation application. When the patent document preparation application is provided as a web application, as in this embodiment, the UI may be understood as any component that can be included in a web page, such as a GUI (Graphic User Interface), a TUI (Text User Interface), or a WUI (Web User Interface).

[0062] The screen composition unit 101 may be provided as one function of a web browser. The screen composition unit 101 may be provided with files and data from the patent document creation server 20, or may compose a screen by reading files or data stored in the memory 14. The screen composed by the screen composition unit 101 may be a static web page or a dynamic web page, and the screen composition unit 101 may refer to files and resources necessary to realize the web page.

[0063] The function and role of each area included in the screen displayed by the screen configuration unit 101 may be predefined. For example, the screen configuration unit 101 may configure the screen in a predefined structure in which a navigation area, a sidebar area, a main area, etc. are arranged. The content included in each area may be predefined or may be generated by input from the user. For example, the content displayed in the navigation area and the sidebar area may be predefined, and the main area may display both predefined information and information input by the user.

[0064] Furthermore, the web page configured by the screen configuration unit 101 may include a script that provides a UI that allows the user to adjust the screen structure or set or change the type, content, position, shape, etc. of content displayed on the screen. That is, the screen configuration unit 101 may be provided so that the user can change the configuration of the web page. For example, the web page provided by the screen configuration unit 101 may include multiple areas, and a UI may be provided that allows the user to select an area to be displayed on the screen or adjust one or more of the position and size of the area. Such UI functions may be realized by a programming language such as JavaScript that can dynamically control the web page.

[0065] The screen configuration unit 101 can basically configure a "patent document creation screen" where a user can input the contents of a patent document using the input / output interface 19. The structure and content of the patent document creation screen can be configured differently depending on the service provided. In other words, the patent document creation screen for the first service and the patent document creation screen for the second service can be configured differently. Specific details regarding this will be described later.

[0066] In either case, the patent document creation screen configured by the screen configuration unit 101 may include one or more text input components into which a user can input information, including text, as the content of a patent document. A "text input element" may be understood as a UI provided to a user via a patent document creation application so that the user can input text. When the patent document creation application is implemented as a web application, as in this embodiment, the text input element may be an HTML form component or a tag that allows data input. For example, the text input element may be configured with an input, textarea, div tag, etc.

[0067] In this case, some text input elements may be provided to allow non-text data input such as tables, figures, etc. For example, a web page may include a text input element in which a UI capable of performing functions such as creating a table, inserting special characters, inputting mathematical formulas, inputting chemical formulas, inputting sequence information, and inserting figures is provided on one side of a text input area window in the form of a toolbar. Of course, such a UI may be located separately from the text input element.

[0068] The data management unit 102 manages data necessary for patent document creation and can function as a data input / output interface for the database 140. For example, the data management unit 102 can provide functions such as saving data in the database 140, reading saved data, modifying saved data, and deleting saved data.

[0069] The data management unit 102 may be provided as a function of a web browser, or may be a program source, file, library, or the like that can be loaded or referenced and used by a web browser.

[0070] As described above, database 140 is a web DB provided by a web browser and may include one or more of a web storage, a web SQL DB, and an index DB. Such web DBs vary in characteristics, such as support and storage capacity, depending on the type and version of the web browser. To enable a user to use the patent document preparation function using any web browser desired by the user, the data management unit 102 may check information about the web browser used to run the patent document preparation application and use one or more web DBs normally supported by the web browser. To this end, the type of web DB to be used for each web browser may be preset and stored in the web page or script. For example, if the web browser used is Internet Explorer 11, which does not normally support index DBs, the data management unit 102 may use web storage as database 140. However, if the web browser used is Chrome, which normally supports index DBs, the data management unit 102 may use an index DB with a larger storage capacity as database 140.

[0071] Furthermore, if the database 140 further includes a storage location of another type other than a web DB, the data management unit 102 may be provided so as to be able to cooperate with the storage location of the other type.

[0072] The components included in the patent document drafting device 10 can perform data management by the data management unit 102 in cooperation with the database 140. Of course, depending on the embodiment, one or more of the components included in the patent document drafting device 10 can also independently cooperate with the database 140. In this embodiment, it can be understood that the components of the patent document drafting device 10 are cooperated with the database 140 by the data management unit 102, even if no special explanation is added.

[0073] Furthermore, the data management unit 102 may encrypt and process data when interacting with the database 140. Specifically, the data management unit 102 may encode data entered by a user using a preset encryption algorithm and store the encoded data in the database 140, and may read data stored in the database 140, decode the data using the same encryption algorithm, and output the data to the user via the input / output interface 19. In this case, the encryption algorithm used by the data management unit 102 may use a key value that depends on user account information, thereby further improving the security of patent documents created by the patent document creation application.

[0074] Meanwhile, the data management unit 102 may be provided to cooperate with not only the database 140 of the patent document production device 10 but also the database 240 of the patent document production server 20. In this case, the data management unit 102 may transmit a predetermined data processing request to the patent document production server 20 via the data communication unit 113 described below, and may receive processing results provided by the patent document production server 20. The above-described method of cooperation between the data management unit 102 and the database 140 may be substantially similarly applied between the data management unit 102 and the database 240. Depending on the embodiment, the data management unit 102 may be provided to cooperate with either or both of the database 140 of the patent document production device 10 and the database 240 of the patent document production server 20.

[0075] The case management unit 103 may manage cases created by users to prepare patent documents. Case information managed by the case management unit 103 may be input by the user or generated based on preset rules. For example, case information may include information such as a case management number, case name, deadline, client, technical field, document format, storage method, and translation language information depending on the associated service. The screen configuration unit 101 may configure a screen (hereinafter referred to as a "case management screen") for managing such information and provide it to the user. The case management screen may be provided as an independent webpage, a partial area of ​​a webpage, a hidden or foldable area of ​​a webpage, or a pop-up page or window.

[0076] The management number is a value set to distinguish the case from other cases, and can be input by the user via the case management screen or automatically assigned by the case management unit 103 based on pre-set rules. In this case, the management number is managed and used as a unique value for each case, and the case management unit 103 can execute a process to verify the uniqueness of the management number.

[0077] The case name can be understood as a value that can be entered arbitrarily by the user to distinguish the case from other cases, the deadline as the date by which the work for the case should be completed, the client as the person who requested the case from the user, and the technology field as the type of technology that is highly relevant to the case (e.g., information and communications, machinery, chemistry, etc.).

[0078] A document format may be understood as a basic structure that a patent document to be created should have. Specifically, in the case of patent specifications, since different patent offices in different countries have different formats designated for patent specifications, a case management screen may be configured to allow a user to select the format of the patent specification to be created. For example, document formats may be exemplified as "KR," "US," "JP," "PCT," etc., and if a user selects "KR," a screen corresponding to the patent specification format designated by the Korean Intellectual Property Office may be provided to the user. Database 140 stores required input information and file templates corresponding to each document format, and processor 100 may provide the user with a corresponding screen or file.

[0079] The storage method can be understood as selecting whether to store and manage the information entered for the case in the patent document production device 10 or in the patent document production server 20. For example, the case management screen may provide the user with options such as "Local Database" and "Cloud Database." If the user selects the former, the case information is stored in database 140. If the user selects the latter, the case information is transmitted to the patent document production server 20 via the network 30 and stored in database 240. In the former case, since the patent document information does not pass through the network 30, security features at or above the level of a word processor independently operated by the patent document production device 10 may be provided. In some embodiments, only some of the information may be stored in database 140, and the remaining information may be stored in database 240 of the patent document production server 20.

[0080] The translation language information is the language of the original text to be translated (second language) and the language of the translation text (first language), and can be used when the case is a case for the second service.

[0081] The element management unit 104 may manage elements included in the content of a patent document. In this embodiment, an "element" may be understood to refer to a specific object that may be included in the content of a patent document and described in text. Depending on the embodiment, an element may not constitute an invention, but may be a part of text that represents or describes a specific object. Furthermore, "element information" may be understood to include one or more pieces of information related to the element (e.g., the name of the element, an identification number corresponding to the element (e.g., a drawing number), a translation of the element, whether the element is used, the number of times the element is used, etc.).

[0082] For example, a patent document may include content describing multiple components that make up an invention, and such components that make up an invention may be managed by the component management unit 104. Specifically, in the case where an invention includes components such as a motor, a shaft, and a gear, and the identification numbers for these components are set to 10, 20, and 30, respectively, "motor," "shaft," "gear," "10," "20," and "30" may be managed as component information. In addition, if the patent document is a translation created by a second service, the translation of the information for each component may also be managed as component information. In the above example, if the second language is English and the first language is Korean, the following may be managed for "motor": About TIFF2025163151000002.tif514 "shaft" About TIFF2025163151000003.tif518 "gear" TIFF2025163151000004.tif412 can be managed as information on each component.

[0083] In addition, depending on the embodiment, the components managed by the component manager 104 may not be included in the invention, but may refer to specific objects used to explain the content of the invention. In the above example, if the term "driving" is to be used to describe the characteristics of the "motor," "driving" may also be managed by the component manager 104.

[0084] Meanwhile, the component management unit 104 may manage multiple pieces of information describing a single component as a single collection. For example, if the component information includes the name of the component and an identification number identifying the component, the component management unit 104 may assign a unique key value corresponding to the collection of the component name and identification number and manage the component information based on the assigned key value. In the above example, the component management unit 104 may manage each of "motor," "10," "motor," "shaft," "20," "rotating shaft," and "gear," "30," as a single collection, and assign a unique key value to each collection. Furthermore, the component management unit 104 may prevent duplicate component information from being stored in a collection of components to create a unique key value. In other words, the component management unit 104 may prevent the creation of multiple component collections containing the same component information.

[0085] The screen configuration unit 101 may configure a screen for managing information about elements (hereinafter referred to as an "element management screen") and provide it to a user. The element management screen may be provided as an independent web page, provided in a partial area of ​​a web page, provided in a hidden or foldable area of ​​a web page, or provided as a pop-up page or window.

[0086] Meanwhile, when the user changes information of a component, the component management unit 104 may transmit the component information before and after the change to the auto-completion list generation unit 105 and the text input element management unit 106 so that the auto-completion list or the auto-completion text or auto-completion block described below is updated. Note that, changing information of a component may be understood to include inputting information of a new component, updating information of an already input component, and deleting information of an already input component.

[0087] The auto-completion list generator 105 may generate an auto-completion list to minimize the time required for text typing when creating a patent document. The auto-completion list generated by the auto-completion list generator 105 may be provided to the text input element manager 106 for use.

[0088] The auto-completion list may include one or more items generated based on the text entered by the user. Some of the items in the auto-completion list may be managed by unique key values ​​set by the auto-completion list generator 105. The items with unique key values ​​may be subject to functions such as bulk update by the text input element manager 106, which will be described later.

[0089] Specifically, the auto-completion list generator 105 may load data from a pre-defined data source to generate a data set containing all items that can be included in the auto-completion list, and then extract items corresponding to the text entered by the user from the generated data set to construct the auto-completion list to be displayed on the screen. For example, the auto-completion list generator 105 may search for items within a data source using the text entered by the user as a search term, and then construct the auto-completion list using the search results. Alternatively, the auto-completion list generator 105 may extract data corresponding to the entered text from a pre-defined data source after the user enters text, and then construct the auto-completion list using the extracted data.

[0090] Here, the data source may include components managed by the component management unit 104. For example, each of the components managed by the component management unit 104 may be included in the auto-completion list as an item. In this case, all or part of the information included in one set of components may be used as one item in the auto-completion list. Referring to the above example, if the auto-completion list includes "motor," "shaft," "gear," "motor10," "shaft20," "gear30," TIFF2025163151000005.tif5129, etc. may be included as an item. When creating an item that includes an identification code such as a drawing code, the format for including the identification code in the item (e.g., enclosing the identification code in parentheses or using spaces) may be preset, or in some embodiments, the patent document creation application may provide a screen for the user to directly set the format for including the identification code in the item.

[0091] Furthermore, if the patent document creation screen is for a second service of creating a patent translation, the auto-completion list generation unit 105 may generate a data source by extracting only those components for which translations have been input from among the components managed by the component management unit 104. In other words, only those components for which translations have been input from among the components managed by the component management unit 104 may be included as items in the auto-completion list. In this case, if a component for which a translation has been input also includes information about an identification code, the auto-completion list generation unit 105 may include both an item consisting of only the translation of the component and an item displaying both the translation and the identification code in the auto-completion list.

[0092] When the components managed by the component management unit 104 are included as items in the auto-complete list, each item may have a unique key value that is a combination of component information extracted from a set of corresponding component information. Referring to the above example, "motor10," "shaft20," "gear30," etc. may be used as unique key values ​​for the corresponding item.

[0093] The data source may also include data stored in the database 140 or provided by the patent document creation server 20. For example, expressions frequently used in patent document creation may be stored in the database 140 or the database 240, and the auto-completion list generation unit 105 may load them or receive them from the patent document creation server 20 via the data communication unit 113 to include them as items in the auto-completion list. In this case, the auto-completion list generation unit 105 may generate the auto-completion list by combining information about elements managed by the element management unit 104 and data provided from the database 140 or the patent document creation server 20.

[0094] An item included in the auto-completion list generated by the auto-completion list generator 105 may have an attribute value indicating an attribute of the item. The attribute of the item may include the source of data generating the item (e.g., whether the data is provided from the database 140 or the database 240), the purpose of using the item (e.g., whether to auto-complete a component or an idiom word), the type of data included in the item (e.g., the type of language used, whether numbers are included, whether special characters are included, etc.), the structure of the data included in the item (e.g., whether a reference symbol is included, the format in which the reference symbol is displayed, whether a translation is included, etc.), etc.

[0095] As an example of an attribute value of an item, a value corresponding to an item used to automatically complete information about a component of an invention and a value corresponding to an item used to automatically complete repeated expressions regardless of the component may be set and used differently. Hereinafter, an item having the former value will be referred to as a "component item," and an item having the latter value will be referred to as an "idiomatic expression item." In other words, a component item may be understood to be used to automatically complete a component of an invention, and an idiomatic expression item may be understood to be used to automatically complete expressions that are likely to be used repeatedly. Furthermore, in this embodiment, an "idiomatic expression" may be understood to include not only a single word but also a phrase or clause containing multiple words.

[0096] In this case, the component items can be generated from the components managed by the component management unit 104, and the idiomatic term items can be generated from data provided by the patent document creation server 20. As a result, security can be enhanced by managing the component items that are related to the central content of the invention and can be used only in a specific case by the patent document creation device 10. Also, usability can be improved by managing the idiomatic term items that are not related to the central content of the invention and can be used generally in all cases by the patent document creation server 20.

[0097] Meanwhile, when information about a component managed by the component management unit 104 is changed, the auto-completion list generation unit 105 may update the information and identification value of an item generated based on the component to the changed information. In the above example, if the user changes the identification number of "motor" from "10" to "100" using the component management unit 104, the auto-completion list generation unit 105 may change the information about the corresponding component included in the data resource and the item from "10" to "100." As a result, the auto-completion list may include "motor100" as an item instead of "motor10," and the identification value of the item may also be changed from "motor10" to "motor100."

[0098] Furthermore, when information about a new component is added by the component management unit 104, the auto-completion list generation unit 105 can add the component as a component item in the component list. Furthermore, when information about a component managed by the component management unit 104 is deleted, the auto-completion list generation unit 105 can delete an item generated based on the component.

[0099] When generating a component list, the auto-completion list generator 105 may sort the component items in ascending or descending order of the component name text or in ascending or descending order of the identification number text. In particular, the auto-completion list generator 105 may sort the component items in the component list in ascending order of the identification number text. This may improve usability by allowing the component item corresponding to the number of identification numbers entered by the user to be selected first. Specifically, if the component management unit 104 inputs "main body, 100," "mobile phone, 1," and "motor, 10" as the component names and identification numbers, the auto-completion list generator 105 may generate a component list in ascending order of the identification number text in the order of "mobile phone 1," "motor 10," and "mainbody 100." In this case, a user trying to input "mobile phone" would only enter "1." Although all three components would be displayed in the auto-complete list, "mobile phone1" would be displayed first, allowing the user to immediately select "mobile phone1" for auto-complete. If "mobile phone1" were not displayed first, the user would have to perform an additional step to select "mobile phone1," reducing usability. Similarly, a user trying to input "motor" would enter "10." In this case, the auto-complete list would be displayed with "motor10" displayed first, excluding "mobile phone1." The user would immediately select "motor10" for auto-complete.

[0100] The dataset and auto-completion list generated by the auto-completion list generator 105 may have a structured text document format such as json or xml.

[0101] The text input element management unit 106 can manage text input elements included in a web page. As described above, the screen configuration unit 101 can configure a screen so that the patent document creation screen includes one or more text input elements, and the text input element management unit 106 can control the text input elements included in the patent document creation screen by the screen configuration unit 101.

[0102] The text input element management unit 106 may manage the format of text entered into a text input element. For example, the text input element management unit 106 may manage commonly known text attributes, such as the size, font family, and color of the text entered into the text input element, as well as effects that may be added to the text, such as underline, bold, and italic. Such format management may be performed collectively on all text entered into the text input element, or on only a portion of the text selected by the user. Furthermore, format management may be performed automatically by the text input element management unit 106 according to preset conditions, or may be performed manually by the user. In the latter case, the text input element may include a UI that allows the user to change the format.

[0103] In this embodiment, editing text can be understood to include not only changing the content of the text, but also modifying or changing the formatting applied to the text.

[0104] On the other hand, the text input element manager 106 may allow one text input element to have a different format than other text input elements.

[0105] The text input element manager 106 can detect events occurring in text input elements and execute a set action accordingly. Events occurring in text input elements can include keyboard events (e.g., key down, key press, key up, input, etc.), mouse events (e.g., click, double click, mouse down, etc.), and other events occurring in a web browser or operating system. Events occurring in text input elements can also be understood to include changes (addition, modification, deletion, etc.) in data values. In the following description, when an "event" is simply mentioned without any particular detailed explanation, it can be understood to include all keyboard events, mouse events, other events, and data changes.

[0106] The text input element management unit 106 may edit all or part of the text entered into the text input element based on preset rules in response to an event occurring in the text input element. For example, when a specific keyboard event occurs, the text input element management unit 106 may extract a portion of the text entered into the text input element and determine whether the extracted text satisfies preset conditions. This operation may also be performed by a mouse event that operates in a preset manner (e.g., displaying a pop-up menu by right-clicking the mouse and selecting a preset item from the pop-up menu by left-clicking). The text input element management unit 106 may edit the extracted text based on the determination result in accordance with preset rules, and then replace the extracted text with the edited text and output it to the text input element.

[0107] For example, when English is input into a text input element, if the input key is the space bar and the input word is the first word of a sentence and the first letter is not capitalized, the text input element management unit 106 may change the first letter of the input word to capital letters and output it to the text input element instead of the input word. Specifically, if the user inputs "this" as the first word of a sentence into the text input element and then presses the space bar on the keyboard, the text input element management unit 106 may extract "this" and change it to "This" and output it to the text input element.

[0108] As another example, when Hangul is input into a text input element, if the input key is the space bar, the text input element management unit 106 checks whether the postpositional particle of the input word is used correctly in accordance with the batchim (final consonant) of the last character of the word preceding the postpositional particle, and if the postpositional particle is not used correctly, it may change to the correct postpositional particle and output it to the text input element instead of the input word. In this case, if the word preceding the postpositional particle includes a portion that displays a drawing symbol, the text input element management unit 106 may check whether the postpositional particle is used correctly based on the batchim of the last character excluding the portion that displays the drawing symbol. Specifically, when a user inputs Hangul into a text input element, After entering TIFF2025163151000006.tif569, if you press the space bar key on the keyboard, the text input element management unit 106 TIFF2025163151000007.tif5139 can be modified and output to a text input element.

[0109] The above-mentioned functions such as capitalization and particle change can also be applied to the auto-completion block described later.

[0110] The text input element management unit 106 may provide an auto-completion function when a user inputs text using a text input element. In this embodiment, the "auto-completion" may be understood as inputting the entire phrase by performing a preset key input or mouse input after the user inputs only a part of a word or phrase (hereinafter referred to as the "entire phrase") that the user wishes to input.

[0111] When a keyboard event (e.g., input events such as a, b, c, 1, and 2) for inputting text into a text input element occurs, the text input element management unit 106 outputs an auto-completion list to the screen and provides an auto-completion function by allowing the user to select a desired item. Each item included in the auto-completion list can be used as a whole phrase.

[0112] As described above, the auto-completion list output by the text input element management unit 106 may be generated and provided by the auto-completion list generation unit 105. The auto-completion list generated by the auto-completion list generation unit 105 may include multiple items, and the multiple items may include component items and idiomatic term items, so that a user may utilize the auto-completion function to reduce the time required to create a patent document.

[0113] For example, when a keyboard event for inputting text within a text input element occurs, the text input element management unit 106 may extract the cursor position where the event occurred. Then, the text input element management unit 106 may extract text surrounding the extracted cursor position (hereinafter referred to as the “extraction position”) based on preset conditions. For example, the text input element management unit 106 may extract text corresponding to a word located before the extraction position. As an example, the extracted text may be a string extending from the extraction position to the preceding identifier (e.g., a line feed character, tag, space bar, or other text or code that is configured to be recognized as a word according to a language-specific text input method provided by the operating system and patent document creation application). As an example, the text input element management unit 106 may extract the cursor position and text using a selection object of a window object in a web browser. Hereinafter, a “string” is understood to be a set of one or more consecutive letters, numbers, symbols, or whitespace characters, and each unit constituting a string may be collectively referred to as a character.

[0114] In this case, the text input element management unit 106 may provide an auto-completion function even when text is input between consecutive character strings. To this end, the text input element management unit 106 may store the text written before the extracted text (hereinafter referred to as "forward text") and the text written after the extracted text (hereinafter referred to as "backward text"), respectively. The forward text and backward text may be text up to HTML tags located before and after the extracted text. The forward text and backward text may be independently and explicitly stored within a function or method that implements the function of the text input element management unit 106, or may be automatically generated and managed by a library or script referenced by the text input element management unit 106.

[0115] The text extracted by the text input element management unit 106 may be used as a keyword for generating an auto-completion list. In other words, the auto-completion list generation unit 105 may use the text extracted by the text input element management unit 106 as a search term, search for data that includes or corresponds to the extracted text from a pre-defined data source or dataset, and generate items to be included in the auto-completion list. Hereinafter, the text extracted by the text input element management unit 106 and used by the auto-completion list generation unit 105 for generating an auto-completion list will be referred to as an "auto-completion keyword."

[0116] The auto-completion list generation unit 105 may create an auto-completion list based on an auto-completion keyword and provide it to the text input element management unit 106. The text input element management unit 106 may output the auto-completion list provided by the auto-completion list generation unit 105 to the cursor position where the corresponding event occurred. The auto-completion list output by the text input element management unit 106 may include one or more items and may be configured so that the user can change the selected item using a mouse or keyboard. For example, the auto-completion list may be generated by the text input element management unit 106 as a block with a preset size on an independent layer and provided in a format that is displayed on the screen when called by the text input element management unit 106. In this case, the display direction of the auto-completion list may be set so that the auto-completion list, which has a set size based on the cursor position, fits neatly on the screen. To this end, the text input element management unit 106 may determine the direction in which the auto-completion list is output by reading the size and position of the text input element provided by the web browser, the cursor position, etc. As an example, if the cursor position is offset to the left of the text input element, the auto-completion list may be output to the right of the cursor, and if offset to the right, the auto-completion list may be output to the left of the cursor.

[0117] When the user selects a desired item from the output auto-completion list and then performs a preset key input (e.g., tab key or enter key) or mouse input, the text input element management unit 106 may change the auto-completion keyword to the content of the item selected by the user and output it to the text input element. In other words, the selected item may be output to the text input element as an auto-completion complete phrase. Hereinafter, the complete phrase output to the text input element instead of the auto-completion keyword will be referred to as "auto-completion text."

[0118] In this case, multiple key inputs may be required to output the auto-completed text, and the text input element management unit 106 may configure the auto-completed text in different formats depending on the input key value. For example, auto-complete is performed by a first key input and a second key input different from the first key input. When the first key input is received, the text input element management unit 106 may output the entire phrase as auto-completed text, and when the second key input is received, the text input element management unit 106 may change the first letter of the entire phrase to a capital letter and output the auto-completed text. As another example, when the second key input is received, the text input element management unit 106 may change the entire phrase to a singular or plural expression and output the auto-completed text. As another example, when the second key input is received, the text input element management unit 106 may output only the names of the elements, excluding the drawing symbols included in the entire phrase, as auto-completed text. Note that a key input may be understood to include not only a single key input but also a combination of key inputs.

[0119] When a user inputs text between consecutive character strings, the text input element management unit 106 may combine the preceding text before the item selected from the auto-completion list and the following text after the selected item, thereby maintaining other content entered in the text input element as is. This allows the auto-completion function to be provided even if text is entered at any position in the text input element.

[0120] Furthermore, the text input element manager 106 may position the cursor immediately after the auto-completed text, allowing the user to smoothly continue entering text. This function may also be realized by extracting the cursor position and text using a selection object of a window object of the web browser, and then replacing the auto-completed keyword with the auto-completed text using a range object.

[0121] In addition, the text input element management unit 106 may apply a preset format to the auto-completed text so that the auto-completed text is recognized as distinct from other text, and output the formatted text to the text input element. For example, the text input element management unit 106 may surround the auto-completed text with tags that can format the text within the text input element (for example, span tags or div tags with different colors, fonts, sizes, etc.) and then output the text to the text input element. This allows the text input element management unit 106 to recognize the auto-completed text as distinct from other text within the text input element. The setting value or tag itself for applying the formatting may already be included as the content of the auto-completed list item or may be set as an attribute value of the auto-completed list item.

[0122] In this case, the text input element management unit 106 may apply different formats depending on the attributes of the item selected from the auto-completion list. As described above, the auto-completion list generation unit 105 may cause items included in the auto-completion list to have attribute values, and the text input element management unit 106 may apply different formats depending on the attribute values ​​of the corresponding items when applying a format to the auto-completion text. For example, if the selected item is a component item, the text input element management unit 106 may specify a format so that the auto-completion text is displayed in a first color that can be distinguished from other text. Furthermore, if the selected item is an idiom item, the text input element management unit 106 may specify a second color that is different from the color of other text and the first color, or may specify a color that is the same as the color of other text. As another example, the text input element management unit 106 may omit a format specification for the idiom item so that the auto-completion text is displayed in the same format as the other text.

[0123] Furthermore, the text input element management unit 106 may prevent the user from arbitrarily editing the auto-completed text. That is, the content of the auto-completed text may be set to be uneditable. For example, the text input element management unit 106 may surround the auto-completed text with a predetermined tag such as a span tag, and specify the ContentEditable attribute of the tag as false. This prevents the user from arbitrarily modifying the area surrounded by the tag, thereby preventing the user from arbitrarily changing the auto-completed text.

[0124] Whether the auto-completed text is editable may be set differently depending on the attributes of the item selected from the auto-complete list. For example, the text input element management unit 106 may set the auto-completed text to be uneditable if the selected item is a component item, and editable if the selected item is an idiomatic term item. This prevents errors that would be considered incomplete under the Patent Act due to incorrect or arbitrary changes to components that require consistent expression in patent documents, and allows the user to freely edit unrelated idiomatic terms, thereby improving usability.

[0125] In addition, the text input element management unit 106 may detect an event and, upon detecting a deletion event for the auto-completed text (e.g., a keystroke such as backspace or delete), delete the auto-completed text in one go. That is, the auto-completed text may be deleted with a single event. For example, the text input element management unit 106 may enclose the auto-completed text in a predetermined identifier or tag, and upon inputting a delete event, delete the entire portion enclosed by the identifier or tag, thereby realizing the operation of deleting the auto-completed text with a single keystroke. In addition, the text input element management unit 106 may use a selection object of a windows object in a web browser to specify the auto-completed text as a range, and then delete the specified range in one go when a delete event occurs. This may further reduce the time required for editing text, thereby further improving the productivity of patent document creation.

[0126] Whether or not to provide a function to delete auto-completed text with a single event can be configured differently depending on the attributes of the item selected from the auto-complete list. For example, the text input element management unit 106 can be configured to delete the auto-completed text with a single event if the selected item is a component item, or to delete individual characters that make up the auto-completed text if the selected item is an idiomatic term item. This can prevent errors in description under the Patent Act caused by incorrect or arbitrary changes to components that require consistency in expression within a patent document, and can also improve usability by allowing the user to freely edit unrelated idiomatic terms.

[0127] When the patent document creation application is provided as a web application, as in this embodiment, the auto-complete text may be managed by being enclosed in HTML tags, and functions such as specifying text formatting, disabling editing, and deleting with a single event may be provided based on this. In the following description, the auto-complete text enclosed in tags is referred to as an "auto-complete block." In other words, the text input element management unit 106 can provide the auto-complete function by adding an auto-complete block when a user enters text into a text input element.

[0128] On the other hand, the patent document preparation application may not be a web application based on HTML, but may be an independent application software implemented in any programming language. In this case, the auto-complete text may be displayed in a format distinct from other parts of the text input element, managed so as not to be arbitrarily edited, or deleted by a single event. The auto-complete text implemented in this way may be understood as an auto-complete block.

[0129] The text input element manager 106 can assign an identification value to the auto-complete block and manage the auto-complete block based on the identification value. For example, if the auto-complete block uses a span tag, the identification value assigned by the text input element manager 106 can be set with the id value of the span tag, and the text input element manager 106 can control the auto-complete block based on the id value.

[0130] In this case, the identification value assigned to the auto-complete block by the text input element management unit 106 may be determined according to the item in the auto-complete list that generates the auto-complete block. That is, auto-complete blocks generated by a certain item in the auto-complete list may have the same identification value. For example, the identification value of the auto-complete block generated by the text input element management unit 106 may be a unique key value of the item corresponding to the auto-complete block. According to an embodiment, the text input element management unit 106 may generate a different identification value based on the data of the corresponding item, rather than the unique key value of the item in the auto-complete list.

[0131] Referring to the above example, if the auto-complete list includes items "motor10," "shaft20," and "gear30," and the key values ​​of each item are set to "motor10," "shaft20," and "gear30," the auto-complete blocks generated when the user selects "motor10" from the auto-complete list will all have an identification value of "motor10," and the auto-complete blocks generated when the user selects "shaft20" will all have an identification value of "shaft20."

[0132] When information of a specific component managed by the component management unit 104 is changed, the text input element management unit 106 may automatically change the value of an auto-complete block generated based on an item corresponding to the component. That is, a user may change the information of the component through the component management unit 104 to change the text corresponding to the component that has been auto-completed in the text input element at once. This function is called a "batch update." Specifically, when a user changes the information of a specific component through the component management unit 104, the component management unit 104 may request the text input element management unit 106 to update the auto-complete block corresponding to the component whose information has been changed. The request transmitted by the component management unit 104 to the text input element management unit 106 may include information before and after the change of the component. When the text input element management unit 106 receives a request to update the auto-complete block, the text input element management unit 106 may query the identification value of the corresponding auto-complete block based on the information before the change and update the data of the auto-complete block to the changed information based on the retrieved identification value. At this time, the identification value of the auto-complete block may also be changed based on the changed information, if necessary.

[0133] In the above example, if the user changes the identification number of “motor” from “10” to “100” via the element management unit 104, the text input element management unit 106 may query all auto-complete blocks that have the unique value of the corresponding item, “motor10”, set as their identification value, and then change the auto-complete text of the queried auto-complete blocks to “motor100” and update the identification value to the changed “motor100”.

[0134] When updating the information of the auto-complete block, the text input element management unit 106 may change only the text included in the auto-complete block within the text input element. In the above example, if "motor10" is entered as an auto-complete block in some parts of the text input element and as general text that is not an auto-complete block in other parts, when the user changes the identification number of "motor" from "10" to "100" in the element management unit 104, the general text "motor10" will not be changed, but the auto-complete block "motor10" may be changed to "motor100." This embodiment indirectly forces the user to manage element information via the element management unit 104 and create patent documents using the auto-complete function, thereby improving the user's proficiency with the system.

[0135] Depending on the embodiment, when information about a component managed by the component management unit 104 is changed, the text input element management unit 106 may reflect the changed component information in the text input element by replacing the pre-change string with the changed string for the entire text input in the text input element or only the auto-complete block. In addition, the text input element management unit 106 may, as necessary, display the part of the text input element to be changed in advance to the user, and execute the entire change after obtaining the user's confirmation for the entire change, or may change only the part selected by the user.

[0136] Meanwhile, when information of a specific component managed by the component management unit 104 is deleted, the text input element management unit 106 may change an auto-complete block generated based on an item corresponding to the component to simple auto-complete text. For example, the text input element management unit 106 may delete tag information that assigns formatting and attributes from the auto-complete block corresponding to the information of the deleted component, leaving only the simple text information. As another example, when information of a specific component managed by the component management unit 104 is deleted, the text input element management unit 106 may delete the corresponding auto-complete block included in the text input element.

[0137] In addition, when information about a new component is added by the component management unit 104, the text input element management unit 106 can determine whether text corresponding to the information about the component is included in the text input element, and then change the corresponding text to an auto-complete block.

[0138] As described above, the text input element management unit 106 can provide functions for specifying formatting, disabling editing, deleting with a single event, and bulk updating on an auto-completion block basis, so that the user can create documents while more clearly understanding the contents of the patent document they are creating, and can edit quickly and accurately, so that patent documents can be created more accurately and quickly.

[0139] Meanwhile, according to an embodiment, the text input element management unit 106 may output an auto-completion list only when a pre-defined trigger character is input and a character is input following the trigger. For example, if “@” is set as the trigger character, the text input element management unit 106 may provide the auto-completion function described above only when a character is input following “@” in the text input element. In this case, the text input element management unit 106 may delete the trigger character when the auto-completion keyword is replaced with the auto-completion text and output it in the text display area. Specifically, in the above example, if the user simply inputs “mot,” no auto-completion list is output. However, if the user inputs “@mot,” an auto-completion list including “motor10” is output. If the user selects this, “motor10” may be input as the auto-completion text instead of “@mot.” In this way, when a trigger character is used, the user can select whether or not to display the auto-completion list.

[0140] In addition, when a component item is input using the auto-completion function, the text input element management unit 106 may add an antecedent to indicate the component item to be auto-completed. For example, if the component item to be auto-completed has already been used in the corresponding text input element or another pre-defined text input element, the text input element management unit 106 may automatically add an antecedent such as "the" or "the" when the component item is auto-completed. In this case, the added antecedent may be included as part of the auto-completion text and placed in the auto-completion block.

[0141] Whether or not to automatically add an antecedent when automatically completing a constituent item can be managed by a setting value, and can be provided so that the user can select it on a setting management screen described later.

[0142] The text input element management unit 106 may provide a string insertion function for adding a preset string to a text input element. The preset string input by the string insertion function (hereinafter referred to as an "inserted string") may not include any element managed by the element management unit 104, but may be a string previously input by a user in connection with the creation of a patent document and stored in database 140 or database 240.

[0143] For example, the inserted string may be content related to the case, such as the title of the invention, background art, the problem to be solved, the effect of the invention, a brief description of the drawings, claims, etc., entered by the user when creating the case. Such case-related content may be stored in the database 140.

[0144] Furthermore, the insertion string may be case-independent, and may include idiomatic content, such as sentences or expressions that can be repeatedly used regardless of the case type in the creation of patent documents, or explanatory text that can be repeatedly used regardless of the case type to explain specific technical terms. In this embodiment, such repeatedly used sentences or expressions and idiomatically used explanatory text are referred to as "idiomatic phrases" to distinguish them from the aforementioned idiomatic terms. That is, idiomatic terms can be understood as idiomatic expressions used as items in an auto-complete list, and idiomatic phrases can be understood as idiomatic expressions used as insertion strings. Idiomatic phrases may be stored in the database 240, and the stored idiomatic phrases may be provided to the text input element management unit 106 via the data communication unit 113. Furthermore, case-related content of the insertion string may be stored in the database 140 of the patent document creation device 10, and idiomatic phrases may be stored in the database 240 of the patent document creation server 20. The location and method for storing such idiomatic phrases are presented as examples, and the concept of the present invention is not limited thereto.

[0145] Idiomatic phrases may include expressions commonly used to describe technical fields, expressions commonly used to describe prior art, expressions commonly used to describe problems to be solved, expressions commonly used to describe the advantages of an invention, expressions commonly used in the brief description of drawings, and expressions commonly used to indicate references in claims. Such idiomatic phrases may include replacement portions that can be replaced with other text. Specifically, the replacement portion may include boundary identifiers (e.g., characters that can indicate the beginning and end of the replaced region) that indicate the boundaries of the replacement portion and a reference identifier that indicates the text to be inserted. For example, the reference identifier may indicate the title of the invention, the claim number, etc., in the text to be replaced.

[0146] The replacement portion may be inserted by replacing other pre-set text when the idiomatic phrase is automatically inserted into the text input element by the text input element management unit 106. Specifically, when inserting the idiomatic phrase into the text input element, the text input element management unit 106 may determine whether the idiomatic phrase includes a replacement portion or whether the text input element into which the idiomatic phrase is input is a text input element including a replacement portion. If it is determined that replacement of the replacement portion is necessary, the text input element management unit 106 may read text already input into another text input element according to the content of the instruction identifier, or may change the replacement portion with information provided by the user or text configured according to the user's selection, and then output the changed text to the text input element.

[0147] In this case, the replaced part output to the text input element is configured like the auto-complete block described above, and may have functions such as block-by-block formatting, non-editability, deletion by a single event, and bulk update functions.

[0148] The screen configuration unit 101 may configure and provide to the user a screen (hereinafter referred to as an "insertion string selection screen") for allowing the user to select a string to be added to a text input element. The insertion string selection screen may be provided as an independent web page, provided in a partial area of ​​the web page, provided in a hidden or foldable area of ​​the web page, or provided as a pop-up page or window. In this case, the insertion string selection screen may be configured independently depending on the type of insertion string. For example, the insertion string selection screen may be called up by a UI such as a button provided around the text input element.

[0149] When a user selects a string on the insertion string selection screen, the text input element management unit 106 may insert the selected string into a text input element. At this time, the position where the selected string is inserted may be the position of the cursor when the user invokes the insertion string selection screen. For this reason, the text input element management unit 106 may store the cursor position when an event invoking the insertion string selection screen occurs. If the cursor is not positioned on a text input element, control may be performed so that the insertion string selection screen is not invoked.

[0150] The text input element management unit 106 may store text information input into the text input element in the database 140 in real time. In this embodiment, "real time" may be understood to mean that when an event related to a data change occurs, processing is performed immediately or at very short time intervals. Specifically, when an event occurs in a text input element and data input into the text input element is changed, the text input element management unit 106 may input data into the database 140 via the data management unit 102 or update the data stored in the database 140. For example, the data management unit 102 may match text input elements managed by the text input element management unit 106 with data storage units formed in the database 140, and when an event in the matched text input element is detected by the text input element management unit 106, the data storage unit of the database 140 may be automatically updated. In this case, data input into the text input element may be safely managed without the user having to take any special action to save the data. Depending on the embodiment, the text input element manager 106 may be provided so that data entered into the text input element is saved at a preset time interval or saved in the database 240 .

[0151] Meanwhile, the text input element management unit 106 may allow data entered into one text input element to be used as is in other text input elements. Specifically, when data "A" is entered into one text input element, the text input element management unit 106 may set data for the other text input elements so that "A" is included as part of the data in the other text input elements. In this case, if the user changes "A" to a different value, for example, "AA," the text input element management unit 106 may change the "A" entered in the other text input element to "AA."

[0152] The text input element management unit 106 may provide such a function in the same manner as the auto-completion function described above. Specifically, the text input element management unit 106 may surround "A" with a tag, assign a unique key value to the tag, and then add it as data for another text input element. Thereafter, when an event occurs in which "A" is changed to "AA," the text input element management unit 106 may search for tags corresponding to the unique key value included in the other text input elements and change the content of the tags from "A" to "AA." In this case, the text input element management unit 106 may provide formatting, non-editing, deletion with a single event, and bulk update functions, similar to the auto-completion block described above, using tags surrounding "A" entered in the other text input elements.

[0153] Meanwhile, data input to the text input elements controlled by the text input element management unit 106 may be provided by other input / output interfaces 19 in addition to a keyboard or a mouse. For example, the patent document drafting device 10 may further include a microphone as the input / output interface 19, and the text input element management unit 106 may convert voice data collected via the microphone into text data and then input the converted text data into the corresponding text input element. For this purpose, the text input element management unit 106 may have a function for converting voice data into text data. The external service linkage unit 111 may be utilized for converting voice information into text. Specifically, the text input element management unit 106 may provide voice data collected via the microphone to a third party via the external service linkage unit 111 and receive text data converted by a service provided by the third party via the external service linkage unit 111.

[0154] In this case, if the content of the converted text contains an item that corresponds to the auto-completion list, the text input element management unit 106 may convert it into an auto-completion block and output it to the text input element. In the above example, if the content converted from voice to text data contains "motor" or "motor10," the text input element management unit 106 may convert the text into a corresponding auto-completion block and output it to the text input element. This function allows users to input the content of patent documents by voice without using a keyboard, and the auto-completion function can be used as is, greatly improving usability.

[0155] Meanwhile, the text input element management unit 106 can also control other text input elements based on an event occurring in one text input element. For example, data entered into one text input element can be referenced as the content of another text input element, and when the data of the referenced text input element is changed, the text input element management unit 106 can automatically update the content of the other text input element related to the referenced text input element. As a specific example, when data of a category input element of an independent claim provided on the claim creation screen described below is changed, the text input element management unit 106 can change data of a category input element of a dependent claim that cites the independent claim.

[0156] The drawing management unit 107 can manage drawings that can be referenced when creating a patent document. When working on a patent document, drawings are often essential references for the user to understand the content of the invention. The patent document creation application according to this embodiment is provided so that the user can refer to drawings while creating the content of the patent document. To this end, the drawing management unit 107 can store drawings in the database 140 of the patent document creation device 10 or the database 240 of the patent document creation server 20, or store access paths to the drawings.

[0157] In this embodiment, an example will be described in which the drawing management unit 107 stores drawing files registered by a user in the database 140. The drawing management unit 107 may receive file input in a preset file format, such as PDF, JPG, or TIFF, and store the file in the database 140. In this case, the drawing management unit 107 may encode the drawing file into a format that can be immediately displayed in a web browser (e.g., base64 encoding) and store the encoded file in the database 140. The screen configuration unit 101 may then retrieve the drawing data encoded and stored by the drawing management unit 107 and output it on the screen. As a result, drawing files stored in the patent document creation device 10 can be provided to a user via a patent document creation application without being transmitted to the patent document creation server 20, thereby maintaining the security of the drawing files.

[0158] In another embodiment, the drawing management unit 107 may convert the drawing file into a Blob (Binary Large Object) instead of directly storing the drawing file in the database 140, and then receive a Blob URL assigned to the converted drawing file and store the Blob URL in the database 140. In this case, the screen composition unit 101 may read the Blob URL stored in the database 140 and include the Blob URL in a web page, thereby outputting the drawing file on the screen.

[0159] On the other hand, since the Blob URL may change each time it is accessed, the drawing management unit 107 can store the absolute path of the drawing file together with the Blob URL, and can update the Blob URL and provide it to the screen composition unit 101 each time the Blob URL of the drawing file is requested (for example, when a new session of the web page is started).

[0160] For the sake of convenience, the following description will hereinafter refer to the direct saving of a drawing file by the drawing management unit 107 and the saving of the access path of the drawing file as "saving a drawing."

[0161] The drawing management unit 107 can store a drawing containing multiple images, or can store multiple files as a drawing for one case.

[0162] The screen configuration unit 101 may register drawing files and configure a screen (hereinafter referred to as a "drawing management screen") on which the contents of the registered drawings can be confirmed and managed, and provide the screen to the user. The drawing management screen may be provided as an independent web page, a part of a web page, a hidden or foldable area on a web page, or a pop-up page or window.

[0163] The drawing management screen may include a UI that allows you to switch between images and view them if the registered drawing contains multiple images (multiple images in one file or multiple image files).

[0164] Additionally, the order of images may need to be changed when creating a patent document, and the drawing management screen may include a UI that allows the order in which images are displayed to be changed.

[0165] Meanwhile, depending on the embodiment, the drawing management unit 107 may store the drawings in the patent document creation server 20. In this case, the drawing management unit 107 may upload the drawing file registered by the user to the patent document creation server 20 via the data communication unit 113. Then, the drawing management screen may receive an access pass for accessing the drawing file from the patent document creation server 20 and output it on the screen.

[0166] The description requirement examination unit 108 examines whether the contents of the patent document created by the patent document creation application conform to the description requirements required by the Patent Act. Patent laws are established for each country, and the required description requirements are set differently accordingly. Therefore, the description requirements examined by the description requirement examination unit 108 are also set differently for each country, and can be stored in the database 140 of the patent document creation device 10 or the database 240 of the patent document creation server 20.

[0167] For example, the written requirements examination unit 108 may examine, as written requirements, whether the content that should be included in a patent application is included, whether the brief description of the drawings is properly prepared, whether the detailed description of the invention is properly written, and whether the claims are properly written. Whether the claims are properly written may include one or more of the following: whether the cited claims are accurately described when drafting the claims; whether the cited claims are properly referenced when drafting the claims; whether impermissible expressions are used when drafting the claims; whether the relationship between the content of the claims and the content of the detailed description of the invention is properly defined; whether previously mentioned expressions or elements are properly referenced when drafting the claims; and whether drawing symbols are properly written in the claims. The written requirements examination unit 108 may also examine, as written requirements, whether antecedents are properly used in the content of the patent document.

[0168] Various forms of text input elements may be provided on the patent document creation screen, and the description requirement review unit 108 can read the description requirements from database 140 or database 240 when the patent document creation screen is loaded, so that the corresponding description requirements can be checked for each text input element.

[0169] In addition, the description requirements examination unit 108 can examine the description requirements even when the content of the patent document is changed by a UI provided on the patent document creation screen. For example, even when the user changes the order of claims without editing the text contained in the claims via the claim creation screen described below, the description requirements examination unit 108 can examine the description requirements regarding the method of describing the claims.

[0170] The description requirement review unit 108 may provide the user with the description requirement review results via a web page. For example, the screen configuration unit 101 may set an area on the patent document creation screen where the description requirement review results are output to the user. The description requirement review results may also be provided to the user via a warning message, a pop-up, or the like. Hereinafter, the portion where the description requirement review results by the description requirement review unit 108 are output will be referred to as the "description requirement review result screen" regardless of the output method. In other words, the patent document creation screen may include the description requirement review result screen.

[0171] On the other hand, the description requirement examination unit 108 may present to the user, via the description requirement examination result screen, a method for correcting the detected description requirement violations. Furthermore, the description requirement examination unit 108 may automatically correct the detected description requirement violations and then present the correction results on the description requirement examination result screen.

[0172] Depending on the embodiment, the description requirement review unit 108 may be provided to review not only the description requirements stipulated in the Patent Act, but also the user's settings or pre-set conditions in the system so that the contents of the patent document can be written clearly and concisely.

[0173] The description requirement review result screen may include the review results for all description requirements reviewed while creating the relevant patent document, but depending on the embodiment, the review results for a specific part may be displayed in an independent area. For example, a separate area may be formed to display the review results for the description requirements of the claims reviewed by the claim input processing unit 122, which will be described later. In this embodiment, the description requirement review result screen may be understood to refer to such an independently displayed area as well.

[0174] The download file generation unit 109 can generate a download file and provide it to the user so that the user can check the patent document created via the patent document creation application via software other than the patent document creation application.

[0175] As described above, a user can create a patent document through the patent document creation screen configured by the screen configuration unit 101, and a plurality of text input elements into which the contents of the patent document can be input may be provided on the patent document creation screen. In this case, the plurality of text input elements may be divided according to the description items of the patent document, or may be divided and generated in units of sentences, paragraphs, etc.

[0176] Generally, patent documents are created in a single file, transmitted to the client, and submitted to the Patent Office as a single file. Therefore, when providing a patent document created through a patent document creation application to a third party, the content entered in multiple text input elements must be integrated and provided as a single document.

[0177] To this end, the download file generation unit 109 can integrate the contents written in multiple text input elements based on the document format specified for the relevant case and generate a file (hereinafter referred to as the "download file") that can be downloaded via a web browser.

[0178] At this time, the download file generation unit 109 may add preset data to the content of the download file in addition to the data entered through the text input elements so that the download file meets the description requirements of the document format specified for the case. The preset data may be classified according to the document format and stored in the database 140, or may be stored as a variable in a function or method corresponding to the download file generation unit 109. For example, the text input elements displayed on the patent document creation screen may omit the title of the invention and identification symbols indicating background art, and the download file generation unit 109 may include such identification symbols in the document content when generating the download file.

[0179] Meanwhile, the download file generation unit 109 may create a download file by applying one or more of the formats applied to the text input element, particularly a format in which the auto-complete block is displayed so as to be distinguished from other text, to the auto-completed text. For example, if the text input element management unit 106 displays the auto-complete block in the text input element in italics with a first color that distinguishes it from other text, the download file generation unit 109 may apply a format to the auto-completed text so that the auto-completed text is displayed in the first color, italics, or italics with the first color when generating the download file. This may improve readability not only for the user creating the patent document but also for the client who has requested the creation of the patent document, thereby improving user satisfaction.

[0180] Alternatively, the download file generating unit 109 may not apply some of the formats applied to the text input elements when generating the download file. For example, if a specific font (e.g., "Arial") is applied to the text input elements, the download file generating unit 109 may generate the download file so that a pre-set specific font (e.g., "Time New Roman") is applied. The font applied to the download file may be provided so that it can be changed by the user through an environment setting screen, etc.

[0181] The text input elements managed by the text input element management unit 106 may manage input text in the form of HTML tags, and the download file generation unit 109 may generate a download file based on data to which the HTML tags managed by the text input elements are applied. For example, the download file generation unit 109 may be implemented using JavaScript capable of generating files in formats such as "Word" or "PDF." Libraries capable of generating Word files or PDF files in a web environment are well-known technologies, and therefore a detailed description of a method for generating such files will be omitted.

[0182] In this case, the download file generation unit 109 may generate a download file by operating independently in the patent document creation device 10 without transmitting the data entered in the text input element to the patent document creation server 20. As a result, the contents of the patent document are not transmitted via the network 30, so the security of the created patent document can be maintained.

[0183] Meanwhile, the download file generation unit 109 may include additional information about the case in addition to the content required by the document format specified for the case. For example, the download file generation unit 109 may include a list of elements created by the element management unit 104 in the download file so that a user or client who opens and views the download file can see at a glance the elements included in the patent document. The download file generation unit 109 may also include information about the case managed by the case management unit 103 in the download document.

[0184] Depending on the embodiment, if the content of the patent document includes values ​​of form elements or needs to be inserted in different formats depending on the values ​​of the form elements, the download file generation unit 109 may take this into account when configuring the content of the download file.

[0185] The setting management unit 110 can manage setting values ​​required for patent document creation using a patent document creation application. The screen configuration unit 101 can configure a screen for managing setting values ​​(hereinafter referred to as a "setting management screen") and provide it to a user. The setting management screen can be provided as an independent web page, a partial area of ​​a web page, a hidden or foldable area of ​​a web page, or a pop-up page or window.

[0186] For example, the setting values ​​managed by the setting management unit 110 may include the type of language used throughout the UI of the patent document creation application, the design theme and text formatting applied throughout the UI of the patent document creation application, the format of downloaded files, etc.

[0187] The external service linking unit 111 may transmit data to external services provided by third parties that provide services not provided by the patent document creation device 10 or the patent document creation server 20, or may receive the results of processing the data. For example, services provided by third parties may include patent-related information inquiry services, voice-to-text conversion services, translation example provision services, machine translation services, dictionary services, card payment services, and account transfer services. The external service linking unit 111 may call service APIs (Application Programming Interfaces) provided by third parties to send data to the third parties, receive processing results, and provide them on the patent document creation screen.

[0188] The user management unit 112 manages account information and usage history information for users who use the patent document preparation application, and can perform member registration / cancellation processing, login processing, session management, usage history management, etc. In particular, the user management unit 112 can manage session information to prevent a single user from logging in to the patent document preparation application simultaneously using different web browsers. This can prevent the problem of case information and patent document content being overwritten by the user.

[0189] The data communication unit 113 may play a role in transmitting and receiving data when the patent document creation device 10 communicates with the patent document creation server 20 or a third party system via the network 30. If the patent document creation application is provided as a web application, as in this embodiment, the data communication unit 113 may be provided as a function of a web browser, and each of the aforementioned components may query the database 140 to see if it has route information to connect to via the data communication unit 113.

[0190] The change content management unit 114 may compare data at a first time point with data at a second time point for data stored by the data management unit 102 and manage the difference therebetween. The data for which changes are recorded by the change content management unit 114 may include text data managed by the text input element management unit 106. The data at the first time point may be compared with the data at the second time point, and added content and deleted content may be separated and stored. In this case, the added content and deleted content may be managed as separate, independent data, or may be managed as data included in a preset format within the text data. For example, added text within a text input element may be represented by an underline, and deleted text may be represented by a strikethrough. The change content management unit 114 may store data with the underline format as added data and data with the strikethrough format as deleted data together with the data before the change. Various methods for the change content management unit 114 to manage data changed based on two time points may be provided depending on the embodiment.

[0191] The first processing unit 100b may include one or more of an idiomatic expression management unit 121, a claim input processing unit 122, an element description input processing unit 123, and a drawing brief description input processing unit .

[0192] In creating the above-mentioned patent documents, idiomatic expressions such as idiomatic words and phrases that are repeatedly used can be managed by the idiomatic expression management unit 121. In the following description, idiomatic words and idiomatic phrases are collectively referred to as "idiomatic expressions."

[0193] The idiomatic expression management unit 121 can manage one or more of idiomatic expressions that are pre-set in the system as idiomatic expressions and idiomatic expressions that are set by the user, and can store and manage such idiomatic expressions in database 140 or database 240.

[0194] The screen configuration unit 101 may configure a screen for managing idiomatic expressions (hereinafter referred to as an "idiomatic expression management screen") and provide it to a user. The idiomatic expression management screen may be provided as an independent web page, as a partial area of ​​a web page, as a hidden or foldable area of ​​a web page, or as a pop-up page or window. In this embodiment, an example will be described in which both idioms and idiomatic phrases are managed on a single idiomatic expression management screen. However, in some embodiments, a screen for managing idioms and a screen for managing idiomatic phrases may be provided separately. In this case, each screen can be referred to as an idiom management screen and an idiomatic phrase management screen.

[0195] The idiomatic expression management screen may be provided with an idiom management area and an idiom phrase management area separated so that the user can explicitly distinguish and manage idioms used for auto-completion from idioms used as insertion strings. In this case, the idiom phrase management area may have an area for managing idioms including replacement parts, which may be arranged separately from other idiom phrase management areas. The idiomatic expression management unit 121 may output the text input element including the replacement part to the idiomatic expression management screen so that the user can compose an idiom including the replacement part.

[0196] The user can add a desired idiomatic expression on the idiomatic expression management screen, or modify or delete an idiomatic expression that has already been input.

[0197] In addition, idiomatic expressions can be set according to the language or document style, and multiple sets of idiomatic expressions can be provided for one language or document style, allowing the user to select and use any one of the sets of idiomatic expressions.

[0198] In this embodiment, the idiomatic expression management unit 121 is described as a component of the first processing unit 100b, but depending on the embodiment, the patent document creation application may be configured so that idiomatic expressions are also used in the second service, in which case the idiomatic expression management unit 121 may be provided as a component of the common processing unit 100a or the second processing unit 100c.

[0199] The claim input processing unit 122 can manage data constituting claims input by a user according to preset conditions so that the user can easily and accurately create claims. The claim input processing unit 122 can receive input of claim numbers, claim types (independent claims or dependent claims), cited claim numbers, invention categories (titles of inventions), and descriptions of elements as data constituting claims. The creation, addition, modification, deletion, movement, etc. of claims by the claim input processing unit 122, as described below, can be understood as managing such data constituting claims.

[0200] The screen configuration unit 101 can configure a screen for creating claims (hereinafter referred to as a "claim creation screen") and provide it to a user. The claim creation screen can be provided as an independent web page, a partial area of ​​a web page, a hidden or foldable area of ​​a web page, or a pop-up page or window.

[0201] The claim creation screen may include multiple text input elements or form elements for receiving data input constituting a claim, and the claim input processing unit 122 may manage the text input elements or form elements provided on the claim creation screen and manage the data input therethrough. For example, the claim creation screen may provide a text input element or form element for inputting a claim number (hereinafter referred to as a "claim number input element"), a text input element or form element for inputting a claim type (hereinafter referred to as a "claim type input element"), a text input element or form element for inputting a cited claim number (hereinafter referred to as a "cited claim input element"), a text input element or form element for inputting an invention category (hereinafter referred to as a "category input element"), and a text input element or form element for inputting a description and limitations of an element (hereinafter referred to as an "element description input element"). Depending on the embodiment, these text input elements or form elements may be provided integrated with each other or separated into more detailed components. As form elements used on the claim creation screen, various HTML tags such as buttons, radios, checkboxes, and selects may be used appropriately according to their characteristics, and the type of form element does not limit the concept of the present invention.

[0202] Specifically, the claim input processing unit 122 may receive a claim number to be created from the user via a claim number input element. In this case, the claim input processing unit 122 may automatically generate a claim number using a preset method and present it to the user. For example, when the user attempts to add a claim, the claim input processing unit 122 may add 1 to the highest claim number among the claims already input and output the result to the claim number input element. Alternatively, when no claim has been created, the claim input processing unit 122 may output 1 to the claim number input element and set the claim type input element to independent claim.

[0203] The user may input a previously entered claim number into the claim number input element. In this case, the claim input processing unit 122 may prompt the user as to whether to replace the content of the previously entered claim with the entered claim number or to insert a new claim with the entered claim number, and may execute a preset operation according to the user's selection. In some embodiments, if a number identical to the claim number of a claim already created is entered into the claim number input element, the claim input processing unit 122 may display an error message to the user. In this embodiment, a UI such as a button for explicitly adding or inserting a claim is provided on the claim creation screen, and the claim input processing unit 122 will output an error message and take no action if a number identical to the claim number of a previously created claim is entered into the claim number input element.

[0204] The claim input processor 122 may receive input from the claim type input element as to whether the claim to be created is an independent claim or a dependent claim, and may control other input elements on the claim creation screen accordingly. Specifically, when a user selects an independent claim as the claim type, the claim input processor 122 may deactivate the cited claim input element and activate the category input element. Conversely, when a user selects a dependent claim as the claim type, the claim input processor 122 may activate the cited claim input element and deactivate the category input element. Note that deactivation may be understood as preventing the user from selecting the corresponding input element (disable) or preventing the input content from being edited (read only). Depending on the embodiment, the claim input processor 122 may be configured to activate the cited claim input element even when an independent claim is selected as the claim type.

[0205] The claim input processing unit 122 can also allow the user to intuitively recognize the type of claim to be created by changing the format or pattern applied to the claim number displayed on the screen or the UI of the claim creation screen depending on the type of claim selected by the user.

[0206] The cited claim input element may be activated when the selected claim type is a dependent claim. The method for writing cited claim numbers is generally regulated by patent law, so when a user creates a claim, the cited claim number must be entered accurately and in accordance with the regulations. While a simple text input element may be provided as the cited claim input element, this embodiment will be described by taking as an example the case where the claim input processing unit 122 provides the user with a "cited claim selection screen" to allow for accurate input of the cited claim number.

[0207] The cited claim selection screen has a UI that allows a user to select a claim having a number earlier than the number of the claim being created as a cited claim, and may be configured by the screen configuration unit 101. The cited claim selection screen may be provided as an independent web page, provided in a partial area of ​​the web page, provided in a hidden or foldable area of ​​the web page, or provided as a pop-up page or window. The cited claim selection screen may be provided to a user when the user selects an activated cited claim input element or through an event such as clicking a preset button.

[0208] Specifically, the cited claim selection screen may be configured to allow the user to select the number of the claim they wish to cite. Each time the user selects a claim number, the claim input processing unit 122 may review whether citing the selected claim satisfies the written requirements of the patent law of the country corresponding to the case. The written requirements reviewed may include not only the method of claim citation but also deficiencies that may arise due to the citation relationship of the claims. For example, when preparing a Korean patent specification, the claim input processing unit 122 may review whether a claim citing two or more claims cites another claim that cites two or more claims, whether the cited claims are of the same invention category, etc. Hereinafter, the review of whether a cited claim satisfies the written requirements of the patent law of the country corresponding to the case is referred to as "cited claim review." The cited claim review function may be executed each time a claim is selected. Alternatively, the cited claim review may be performed by the aforementioned written requirements review unit 108, and the claim input processing unit 122 may receive and process the results. That is, the cited claim review may be performed by either or both of the written requirement review unit 108 and the claim input processing unit 122, and the results may be shared between them. In this embodiment, an example will be described in which the cited claim review is performed by the claim input processing unit 122, but the idea of ​​the present invention is not limited to this.

[0209] The cited claim review results may be provided to the user by the claim input processing unit 122. The claim input processing unit 122 may not generate any particular event if there is no problem, and may provide the review results to the user only if there is a problem. In this case, the review results may include an explanation of what description requirements the selection of the claim in question violates. The claim input processing unit 122 may output a review result message and deactivate the selection of the claim in question, so that a cited claim that violates a description requirement is not selected.

[0210] In this case, the cited claim selection screen may examine in advance claims that may have description deficiencies, and then not display or deactivate the problematic claims on the cited claim selection screen so that the problematic claims cannot be selected.

[0211] The citation claim selection screen may also provide a full claim citation selection function that allows the user to cite all claims having a claim number earlier than the claim number of the claim being created.The citation claim selection screen may also provide a multi-selection function that allows the user to simultaneously select multiple claims.

[0212] In addition, the claim input processing unit 122 may output the content of a claim on a citation claim selection screen or another screen when the user clicks on a claim number or places the mouse cursor over the claim number so that the user can clearly recognize and select the content of the claim they wish to cite. For example, the claim input processing unit 122 may output the content of the claim on which the mouse cursor is placed using a tooltip tag or on a claims display screen, which will be described later.

[0213] When the user selects a claim to be cited on the citation claim selection screen, the claim input processor 122 may generate a claim citation to be displayed in the citation claim input element according to the claim citation type. To this end, the claim input processor 122 may determine which claim citation type the selected claim corresponds to. The claim citation may be generated based on idiomatic phrases, particularly idiomatic phrases including substitution portions.

[0214] Specifically, the claim citation type may be classified by one or more of the following: the number of cited claims (single citation or multiple citation), the manner in which the claims are cited (selective citation or simultaneous citation), whether the cited claims are consecutively numbered, or whether the cited claims include consecutively numbered portions. The idiomatic phrases used to generate claim citations may be set differently depending on the claim citation type. Furthermore, the claim input processor 122 may determine the claim citation type based on the selected claim, and generate claim citations by reading the corresponding idiomatic phrases from the database 140 or 240.

[0215] In this case, the idiomatic phrase that generates the claim citation may include a part indicating the claim number as a replacement part. For example, when only one claim is cited, the idiomatic phrase may include a replacement part corresponding to one claim number (e.g., "<", ">" as a boundary indicator, and "N" as a designator). <n>"). When referencing more than one claim, the idiom may include substitutions corresponding to more than one claim number (e.g., "<", ">" used as boundary indicators, and "N1", "N2", "N3", etc. used as designation indicators). <n1> 」、「 <n2> 」、「 <n3>", etc.) The claim input processor 122 may generate a claim citation by replacing the replacement portion with the corresponding claim number according to the claim citation type.

[0216] The claim citations generated by the claim input processor 122 may be output to the cited claim input element. In this case, the claim input processor 122 may further display an area for graphically displaying the claims selected as cited claims in addition to the claim citations. For example, the claim input processor 122 may generate badges or buttons with claim numbers and patterns that can distinguish the types of claims, and display them on the screen as part of the cited claim input element.

[0217] The category input element may be activated to allow the user to edit data when the selected claim type is an independent claim. When the user inputs data into the category input element, the claim input processing unit 122 may determine whether the input data corresponds to the title of the invention of the corresponding case, and may output a warning message to the user if the data input into the category input element does not correspond to or does not include the title of the invention.

[0218] If the type of the selected claim is a dependent claim, the claim input processing unit 122 sets the claim citation in the cited claim input element, and at the same time, reads the category of the independent claim or any one of the dependent claims among the cited claims and sets it directly in the category input element. In other words, the claim input processing unit 122 can automatically set the category input element according to the category of the cited claim selected by the user. This can prevent incomplete descriptions that may occur due to differences in the categories of claims in a cited relationship. When selecting a cited claim, if the category data of the selected claims differs, the claim input processing unit 122 can output an error message to the user and cancel the selection of the claim that caused the error.

[0219] A user can input the components that constitute the invention and limitations on those components using the component description input element. The component description input element can be configured based on a text input element and can also be managed by the text input element management unit 106. Therefore, a user can create the content of the component description input element while automatically completing component items and idiomatic term items.

[0220] When a user utilizes the auto-completion feature to enter data into a component description input element, the auto-completion text may be inserted into the component description input element in an auto-completion block.

[0221] The claim input processing unit 122 can receive a user input indicating whether or not to include an identification symbol, such as a drawing symbol, in the auto-complete text. To this end, a UI for selecting whether or not to include an identification symbol during auto-complete may be provided on the claim creation screen or the setting management screen. For example, if the user selects to include an identification symbol, the auto-complete text and auto-complete block are generated with the identification symbol included. Conversely, the auto-complete text and auto-complete block may be generated without the identification symbol. In this case, the component items in the auto-complete list provided via the text input element management unit 106 may always be displayed with the identification symbol included. Even in the latter case, the auto-complete block may have the same identification value as the auto-complete block with the identification symbol included. Therefore, the auto-complete block without the identification symbol may also be updated by a batch update. Furthermore, the claim input processing unit 122 can switch the identification symbol inclusion state of the auto-complete text of the auto-complete block displayed on the screen depending on the user's selection of whether or not to include the identification symbol.

[0222] In addition, when a component item is input via the auto-completion function, the claim input processing unit 122 may add an antecedent to indicate the component item to be auto-completion. Specifically, the claim input processing unit 122 determines whether the component item to be auto-completion is stated earlier in a claim (hereinafter referred to as a "cited claim") that the claim (hereinafter referred to as a "claim currently being drafted") cites and in the claim currently being drafted, and if stated earlier, may add an antecedent to the auto-completion text or auto-completion block to perform auto-completion. Depending on the embodiment, the antecedent may be added as general text outside the auto-completion block.

[0223] Whether to automatically add an antecedent when entering data into the element description input element may be managed by a setting value, which may be provided for user selection on the claim creation screen or the setting management screen. Depending on the embodiment, the setting value applied to the entire patent document and the setting value for the claim creation screen may be managed separately.

[0224] Meanwhile, the claim input processing unit 122 may examine whether an antecedent is used correctly when data is input into the element description input element. The term "correct antecedent use" may be understood to mean that if an antecedent is used for a certain element, the element has been used in a cited claim or a claim currently being drafted before the element. The term "correct antecedent use" may also be understood to mean that if an antecedent is not used for a certain element, the element has never been used in a cited claim or a claim currently being drafted before the element. The antecedent examination results may be provided to the user by outputting them to the description requirement examination results screen, outputting them to a description requirement examination results area separately provided on the claim preparation screen, outputting them as a pop-up message, or by highlighting the auto-complete blocks examined within the element description input element.

[0225] Hereinafter, the process of examining whether antecedents entered into the claim element description input element are used correctly is referred to as "claim antecedent review." Such claim antecedent review may be performed for each claim or for the entire scope of claims. In some embodiments, the claim antecedent review may be performed by the description requirement review unit 108, and the claim input processing unit 122 may receive and process the results. In other words, the claim antecedent review may be performed by either or both of the description requirement review unit 108 and the claim input processing unit 122, and the results may be shared between them. In this embodiment, the claim antecedent review is described using the claim input processing unit 122 as an example, but the concept of the present invention is not limited thereto.

[0226] Claim antecedent review can be performed when a pre-defined event occurs, such as when an auto-complete block is entered into a component description input element, when an component description input element loses focus, or when the data of the relevant claim is saved.

[0227] In addition, the review of claim antecedents can be performed not only on the auto-complete block but also on the parts entered in general text, and the results of the review as to whether the antecedents used in the general text are used correctly can also be output to a description requirement review result screen, etc.

[0228] Meanwhile, the claim input processing unit 122 may automatically correct the part where the antecedent is used incorrectly based on the result of the claim antecedent review, and then output the corrected part to the element description input element. In some embodiments, the claim input processing unit 122 may display the content to be corrected to the user in advance in a pop-up window or the like, and perform the correction operation only when an explicit correction command is received from the user.

[0229] Meanwhile, the claim creation screen may include an element name display area that displays only the names of elements entered in the element description input elements. When a user adds or deletes an element item using the auto-complete function, the claim input processing unit 122 may add or delete the name of the element in the element name display area. According to an embodiment, the claim input processing unit 122 may identify the name of the entered element by comparing the names in the element list managed by the element management unit 104 with the text data entered in the element description input elements, and manage the element name display area accordingly. Through this element name display area, a user can intuitively recognize the elements included in the corresponding claim, thereby making it easier and more accurate to create claims.

[0230] A user can create a new claim via the claim creation screen, and the new claim can be added to the end of already created claims (hereinafter referred to as "adding a new claim") or inserted between already created claims (hereinafter referred to as "inserting a new claim"). The screen configuration unit 101 can include a UI, such as a button, on the claim creation screen that allows the user to explicitly add a new claim or cause a new claim insertion event.

[0231] When the user generates an event for adding or inserting a new claim via the claim creation screen, the claim input processing unit 122 can initialize each of the input elements described above to prepare for the input of new data.

[0232] When a user requests the addition of a new claim, the claim input processing unit 122 may set the highest claim number plus 1 to the claim number input element. When a user requests the insertion of a new claim, the claim input processing unit 122 may receive input from the user of the position where the claim to be created is to be inserted, for example, the number of the claim to be inserted, and may generate a corresponding claim number and set it to the claim number input element. Thereafter, the claim input processing unit 122 may receive input of the claim type, cited claim, category, element description, etc. of the new claim.

[0233] When a new claim is inserted, the claim input processing unit 122 may adjust the claim number of a claim (with a higher claim number) located after the position where the claim is inserted. Specifically, the claim input processing unit 122 may store the claim number as data constituting the claim, and when a new claim is inserted, may store a value obtained by adding 1 to the claim number of the claim located after the position where the new claim is inserted as the new claim number of the claim. For example, if claims 1 to 5 have been created, and the user inserts a new claim with claim number 4, the existing claim 4 may be renumbered to claim 5, and the existing claim 5 may be renumbered to claim 6. Hereinafter, the claim number before the change will be referred to as the "old number," and the claim number after the change will be referred to as the "new number."

[0234] Furthermore, when a new claim is inserted, the claim input processing unit 122 may update the claim numbers of claims cited by subsequent claims relative to the insertion position. Specifically, the claim input processing unit 122 may examine the cited claim number data of subsequent claims relative to the insertion position and determine whether the old number is included in the cited claim number. If the old number is included in the cited claim number, the claim input processing unit 122 may update the old number to the corresponding new number. For example, if claims 1 through 5 have been created and claim 5 cites claim 4, when the user inserts a new claim with claim number 4, the claim input processing unit 122 may update the cited claim number of claim 6 from claim 4 to claim 5 in addition to the aforementioned claim number change. In this case, if the claim with the new number cites all of the previous claims or a certain range of claims including the insertion position, the claim input processing unit 122 may include the inserted new claim among the cited claims of the claim with the new number.

[0235] Hereinafter, the change of claim numbers and cited claim numbers by the claim input processor 122 will be referred to as "claim number reorganization." The claim input processor 122 can perform claim number reorganization when inserting a new claim.

[0236] The claim input processing unit 122 can also perform claim antecedent review for claims whose claim numbers are changed due to the insertion of new claims, that is, claims whose claim numbers are updated to new numbers.

[0237] Operations such as claim number sorting and claim antecedent review can be automatically performed by the claim input processor 122 when a command to save the claims to be inserted by the user is input. In this case, the claim input processor 122 can review whether or not adding and inserting new claims will cause errors such as incomplete descriptions in the claims already input, and if an error occurs, it can display the review results including the error contents to the user, and then execute an operation to save the data of the new claims after the user inputs an explicit save command.

[0238] On the other hand, the user can also modify data for created claims via the claim creation screen. In other words, the claim creation screen may also have a function for amending claims. When the claim creation screen is displayed for claim amendment, each input element on the claim creation screen may be provided to the user with the claim data pre-set. Hereinafter, the state in which data is set on the claim creation screen for claim amendment is referred to as the "claim amendment screen." Depending on the embodiment, the claim amendment screen may use the UI of the claim creation screen as is, or may have an independent UI.

[0239] Various methods for displaying the claim amendment screen may be provided. For example, a patent document creation screen may be provided with a claims display screen that displays the content of created claims, and amendment buttons may be provided on the claims display screen corresponding to each claim. In this case, when a user clicks the amendment button for one of the claims, a claim amendment screen filled with the data for that claim may be displayed. If the claim creation screen or claim amendment screen is already displayed, the data for each input element may be changed to the content of the claim corresponding to the clicked amendment button. In addition, various UIs may be provided for setting the content of the claims to be amended on the claim amendment screen, and the concept of the present invention is not limited thereto.

[0240] On the claim modification screen, the user can change the claim type using the claim type input element, change the claim to be cited using the cited claim input element, change the invention category using the category input element, and change the description and limitations of the elements using the element description input element, in the same manner as described above. Depending on the embodiment, claim number changes may also be permitted using the claim number input element. In this embodiment, we will explain an example in which a change in claim number is handled by claim movement, and we will explain that such claim movement is performed through an explicit claim movement UI rather than by modifying the data in the claim number input element. Specific details regarding claim movement will be described later.

[0241] Specifically, when the user changes the claim type from an independent claim to a dependent claim, the claim input processor 122 may activate the cited claim input element and deactivate the category input element. Conversely, when the user changes from a dependent claim to an independent claim, the claim input processor 122 may deactivate the cited claim input element and activate the category input element.

[0242] Even when a user changes the number of a cited claim using the cited claim input element on the claim correction screen, the claim input processing unit 122 may perform the cited claim review described above and execute a set operation depending on the result. For example, when a user changes the number of a cited claim, the claim input processing unit 122 may examine whether such a change satisfies the description requirements required by the patent law of the country corresponding to the case. The cited claim review and the execution of the resulting operation by the claim input processing unit 122 during claim correction may be performed when the user selects a claim to be cited using the cited claim input element.

[0243] Furthermore, if the category of the invention is changed due to a change in a cited claim, i.e., if the category data of the invention of the cited claim before the change differs from the category data of the invention of the newly selected cited claim, the claim input processing unit 122 may notify the user that the category of the invention will be changed and may request confirmation of the category change. If a cited claim of a different category is newly selected, the claim input processing unit 122 may read the category data of the invention of the newly selected cited claim and set it in the category input element.

[0244] The claim input processing unit 122 may also examine whether antecedents are used correctly when a user changes data for element description input elements on the claim correction screen. In this case, the claim input processing unit 122 may perform claim antecedent examination not only for the claim currently being corrected on the claim correction screen (hereinafter referred to as the "claim under correction") but also for the data of claims citing the claim under correction, and provide the results to the user. Specifically, during claim correction, new elements may be added as elements of the invention, or existing elements may be removed. In this case, if a claim citing the claim under correction includes a newly added or removed element, the antecedent for that element must be changed. To this end, the claim input processing unit 122 may detect the addition or deletion of elements during claim correction and, accordingly, determine whether the antecedent in the claim citing the claim under correction needs to be corrected. Furthermore, the claim input processing unit 122 may automatically correct the antecedent included in the data of claims citing the claim under correction based on the results of this determination. When a claim is modified, the claim input processing unit 122 examines the claim antecedents and performs the associated operations when a preset event occurs, such as when the user issues a command to save the modified content (e.g., clicking the Save button) or when the focus leaves the component description input element.

[0245] In this case, the claim input processing unit 122 may output a warning message to the user if the user deletes an already entered element through a data change of the element description input element and the element to be deleted is included in the data of a claim that cites the claim being amended.

[0246] In this way, the operation performed by the claim input processing unit 122 when a user changes data in an element description input element on the claim revision screen can also be performed when a cited claim is changed on the claim revision screen. That is, when a cited claim number is changed, the claim input processing unit 122 can review not only the cited claim but also the claim antecedents for the element description input element, and can execute a set operation based on the results. For example, if a cited claim number is changed, the presence or absence of a specific element's prior appearance may change. Accordingly, if the presence or absence of an antecedent for the element entered in the element description input element of the claim being revised, or the presence or absence of an antecedent for the element in a claim citing the claim being revised, needs to be changed, the claim input processing unit 122 can automatically add or delete an antecedent for the element in the claim being revised or in a claim citing the claim being revised. Of course, depending on the embodiment, the claim input processing unit 122 can display the review results to the user and then perform data revision operations in response to an explicit command input by the user.

[0247] The claim creation screen or claim amendment screen may also have a function for deleting a claim. Claim deletion may be performed only upon the user's explicit consent, such as by clicking a delete button. In this case, the claim input processing unit 122 may expose a UI, such as a delete button, while displaying the content of the claim so that the user can issue a claim deletion command after recognizing the content of the claim to be deleted. For example, the claim deletion button may be displayed together with buttons such as "Edit" or "Save" that are displayed when amending a claim. In other words, the claim amendment screen may be configured to allow the user to enter a claim deletion command. Depending on the embodiment, a UI may be provided that allows the user to directly delete a claim on the patent document creation screen or the claim display screen.

[0248] When a claim deletion command is input by the user, the claim input processing unit 122 can determine whether there is a claim citing the claim to be deleted and whether the data of the claim contains the elements of the claim to be deleted. The claim input processing unit 122 can output the determination result (e.g., the number of the claim citing the claim to be deleted and information on the elements contained therein) to the user, and can receive commands from the user such as whether to proceed with claim deletion or whether to modify the data of the claim citing the claim to be deleted, and can perform operations in response to the commands.

[0249] When deleting a claim, the claim input processing unit 122 may rearrange the claim numbers of the claims following the claim to be deleted, examine cited claims, and examine antecedents. Specifically, the claim input processing unit 122 may decrement the claim numbers of the claims following the claim to be deleted by one, thereby updating the old numbers of the cited claims to new numbers. The claim input processing unit 122 may also examine the description requirements under the Patent Act due to changes in cited claims, examine whether antecedents were used correctly, and perform any corrections required.

[0250] Meanwhile, the claim amendment screen may provide a claim movement function. To this end, the claim amendment screen may provide a UI, such as a claim movement button, that allows the user to input an explicit command to move a claim. In this embodiment, the claim amendment screen includes a claim movement button, and the user clicks the claim movement button to input the desired movement location. However, the UI for issuing a claim movement command on the patent document creation screen is not limited to this, and the concept of the present invention is not limited to the method of issuing a claim movement command. For example, claim movement may be performed by dragging and dropping a claim on the claim display screen or by moving the position via keyboard input. Furthermore, if a tree view showing the claim structure is provided, claims may also be moved by dragging and dropping a claim on the tree view or by moving the position via keyboard input.

[0251] The user can click the claim movement button and input the position to which the relevant claim is to be moved (hereinafter referred to as the "destination"), such as after another claim, between two claims, or before another claim. Hereinafter, the claim that the user wishes to move will be referred to as the "claim to be moved." The claim input processing unit 122 receives the movement position input by the user and can simultaneously or sequentially perform an operation to insert the claim to be moved into the movement destination and an operation to delete the claim to be moved. In other words, the claim input processing unit 122 can move a claim by inserting and deleting a claim. In this case, the order in which the insertion and deletion of claims are processed can be set differently depending on the embodiment.

[0252] The claim input processing unit 122 may also perform the same operations as those performed when inserting or deleting a new claim as described above when inserting or deleting a claim due to a claim movement. Specifically, the claim input processing unit 122 may perform cited claim review, claim number reorganization, antecedent review, etc. when inserting a claim to be moved into a new location, and may perform cited claim review, claim number reorganization, antecedent review, etc. when deleting a claim to be moved. The claim input processing unit 122 may provide the user with the results of such review, and if an error occurs due to the claim movement as a result of the review, the claim input processing unit 122 may prevent the claim movement. Alternatively, after providing the review results, the claim input processing unit 122 may execute the actual insertion or deletion of a new claim after receiving an explicit move command from the user or automatically correcting the error. Alternatively, after providing the review results, the claim input processing unit 122 may provide the user with a screen including input elements for editing the problematic claim and problematic data so that the user can correct the error.

[0253] The claim input processing unit 122 can provide the user with the results of the review performed when a claim is requested to be moved or after a claim is moved by outputting the results of the review on a description requirements review result screen, outputting the results in a description requirements review result area provided separately on the claim creation screen, outputting the results in a pop-up message, or highlighting the auto-completion block that has been reviewed within the component description input element.

[0254] The claim input processing unit 122 allows users to create claims more conveniently and intuitively, and can create claims that meet various description requirements required by the Patent Act. In addition, it can prevent incomplete descriptions caused by adding, inserting, amending, deleting, and moving claims, which frequently occur in practice, thereby reducing opportunity costs for subsequent office actions from the Patent Office and improving client satisfaction.

[0255] The element description input processing unit 123 may receive and manage preset themes for describing elements of an invention so that the user can easily and accurately create a description of the elements. The preset themes may be one or more of the definition of the element, the organic relationship with other elements, the function of the element, the action of the element, the effect of the element, and a specific example of the element.

[0256] The screen configuration unit 101 may configure a screen for creating a description of a component (hereinafter referred to as a "component description creation screen") and provide it to a user. The component description creation screen may be provided as an independent web page, a partial area of ​​a web page, a hidden or foldable area of ​​a web page, or a pop-up page or window.

[0257] The element description input processing unit 123 may provide the user with an element description creation screen for inputting a specific description of a specific element in response to a user request. A UI for generating an event for calling the element description creation screen may be provided in the form of a button or the like on the patent document creation screen.

[0258] The component description creation screen may include one or more text input elements that can receive data input related to a preset theme. One text input element may correspond to one preset theme. Depending on the embodiment, the component description input processing unit 123 may input multiple preset themes as one text input element, or one preset theme as multiple text input elements. Furthermore, when the component description creation screen is initially displayed, only one text input element for receiving input for one preset theme is provided. When a text input element addition event is generated by a user clicking a button, for example, the component description input processing unit 123 may add a text input element for receiving input for the same preset theme to the component description creation screen. For example, the component description creation screen may be configured to input the function, action, and effect of a component as one text input element. Furthermore, the text input elements for receiving input of specific embodiments may be provided separately for receiving input of a basic embodiment and input of an additional embodiment.

[0259] The component description input processing unit 123 may integrate data related to preset themes input for a specific component to generate one description for the component. The description generated by the component description input processing unit 123 may be output to one text input element for the description. In this case, the text input element for the description may be provided so that it can be edited by the user. This allows the user to edit the automatically generated description as desired.

[0260] The component description input processing unit 123 may automatically generate a description and display it in a text input element for the description when the user inputs data into a text input element corresponding to a preset theme. Depending on the embodiment, the component description creation screen may include an explicit UI for receiving input of a command for generating the description, and the component description input processing unit 123 may generate the description only after the command is input from the user. The text input element for the description may be displayed together on the component description creation screen. Depending on the embodiment, when the user edits the description, the automatic description generation function by the component description input processing unit 123 may be stopped.

[0261] The component description input processing unit 123 can automatically generate a complete sentence based on data input into a text input element corresponding to a certain preset theme, and can generate a description for the corresponding component by concatenating one or more completed sentences. In this case, the user can input data in the form of a phrase or clause into the text input element, and the component description input processing unit 123 can complete the sentence based on the data. To this end, the component description creation screen can be configured to provide a guide phrase alongside the text input element for receiving data input in the form of a phrase or clause from the user. For example, the portion of the component description creation screen where a definition of a component is input can be configured such that a guide phrase such as “[the name of the component] is,” a text input element, and a guide phrase such as “can be defined as” are arranged side by side. This allows the user to intuitively recognize that they only need to input the remaining portion of the completed sentence, excluding the guide phrase, into the text input element.

[0262] A sentence that has been completed or will be completed by the component description input processing unit 123 may be displayed in the description text input element. This allows the user to recognize the process in which the data they input is being finalized into a sentence. Depending on the embodiment, guide phrases may not be provided on the component description creation screen. In this case, the user can refer to the content displayed in the description text input element to recognize how the text they are inputting is used in the sentence, and can input data using appropriate expressions.

[0263] Meanwhile, when a preset theme includes multiple text input elements, as in the specific embodiment described above, the component description input processing unit 123 may generate different types of completed sentences based on the respective text input elements. For example, when a specific embodiment includes text input elements for a base embodiment and an additional embodiment, the component description input processing unit 123 may generate a sentence such as "In this embodiment, [the name of the component] may be [the data of the text input element for the base embodiment], but the concept of the present invention is not limited thereto" based on data input into the text input element for the base embodiment. Also, the component description input processing unit 123 may generate a sentence such as "For example, [the name of the component] may be [the data of the text input element for the additional embodiment]" based on data input into the text input element for the additional embodiment.

[0264] The component description creation screen may include a UI such as a button that can insert the component description or completed sentence created in this way into a preset position of a preset text input element included in the patent document creation screen (e.g., the cursor position in the text input element that was being created when the component description creation screen was called up). When an insert command is input via such a UI, the component description input processing unit 123 can insert data that was input into the text input element for the description or data such as the completed sentence generated by the component description input processing unit 123 into the preset text input element on the patent document creation screen.

[0265] At this time, the component description input processing unit 123 can save the data that was entered into the text input elements and the data that was entered into the text input elements for the description, corresponding to each pre-set theme, via the data management unit 102. Thereafter, when the component description creation screen for the component is called up again, the component description creation screen can be displayed with the saved data loaded and set in each text input element.

[0266] The drawing brief description input processing unit 124 can manage user-inputted description phrases for drawings so that users can easily and conveniently create drawing brief descriptions for patent specifications. In patent specifications, drawing brief descriptions can consist of one or more sentences. Some users create drawing brief descriptions using clauses instead of sentences. For ease of explanation, the sentences and clauses used in drawing brief descriptions will be collectively referred to as sentences below. Each sentence can include drawing numbers and corresponding description phrases to describe the contents of one or more drawings.

[0267] The screen configuration unit 101 may configure a screen for creating a brief description of a drawing (hereinafter referred to as a "drawing brief description creation screen") and provide it to a user. The drawing brief description creation screen may be provided as an independent web page, a partial area of ​​a web page, a hidden or foldable area of ​​a web page, or a pop-up page or window.

[0268] The drawing description creation screen may be configured to include one or more drawing information input units that allow a user to input data related to the drawing sentence by sentence. One drawing information input unit may include a text input element for inputting a drawing number (hereinafter referred to as a "drawing number text input element") and a text input element for receiving input of a description of the drawing (hereinafter referred to as a "drawing description text input element"). One drawing information input unit may include one drawing number text input element and one drawing description text input element. In this case, a user may input one or more drawing numbers into the drawing number text input element. If a user attempts to input multiple drawing numbers into the drawing number text input element, the drawing description input processor 124 may enforce input in a preset format for normal operations such as adding, inserting, deleting, and moving drawing information input units. For example, the drawing description input processor 124 may require multiple drawing numbers to be separated by characters or used with text such as "Figure" or "FIG.", and may request the user to re-enter data if data that does not conform to this is entered.

[0269] In addition to the drawing number text input element and the drawing description text input element, the drawing information input unit may also include guide phrases including commonly used particles and predicates. The guide phrases of the drawing information input unit are displayed together with the drawing number text input element and the drawing description text input element to guide the user to complete a sentence including the data of the drawing number text input element, the data of the drawing description text input element, and the guide phrase. For example, a drawing information input unit may include the guide phrase "Figure," a drawing number text input element and the guide phrase "is," and a drawing description text input element and the guide phrase "is." As a result, a sentence such as "Figure [1] is [a perspective view of one embodiment of the present invention]" may be displayed in the drawing information input unit. Depending on the embodiment, the drawing brief description input processing unit 124 may automatically change the particles, verbs, etc. of the guide phrase depending on the data input into the drawing number text input element. For example, the drawing brief description input processing unit 124 may input the following in response to the data input into the drawing number text input element when creating a Korean patent specification: TIFF2025163151000008.tif433 may be displayed as the guide phrase. In addition, when creating an English patent specification, if multiple drawing numbers are entered in the drawing number text input element, the drawing brief description input processing unit 124 may change the guide phrase from "is" to "are" and display it.

[0270] The drawing brief description input processing unit 124 can manage the data input into the drawing number text input element and the drawing description text input element for each drawing information input unit, as well as the completed sentence including the guide phrase.

[0271] In this case, when loading the drawing brief description creation screen, the drawing brief description input processing unit 124 may automatically generate and provide to the user a number of drawing information input units corresponding to the number of pages of the drawing file, the number of drawing files, or the number of drawings registered by the drawing management unit 107. Alternatively, the drawing brief description input processing unit 124 may recognize text included in the drawing file registered by the drawing management unit 107, extract a drawing number from the recognized text, and generate a drawing information input unit corresponding to each drawing based on the extracted text. In this case, the drawing brief description input processing unit 124 may automatically set the recognized drawing number to a drawing number text input element of each drawing information input unit.

[0272] On the other hand, if a drawing is related to another drawing, the description of the drawing may require the number of the other drawing (hereinafter referred to as the "related drawing number") to be entered. That is, the related drawing number may be entered in the drawing description text input element, and there may be one or more related drawing numbers. According to an embodiment, the drawing brief description creation screen may include a related drawing number input element, such as a cited claim input element, in the claim creation screen, and the drawing brief description input processing unit 124 may generate and input a related drawing number into the drawing description text input element based on the related drawing selected here. In this case, the drawing brief description input processing unit 124 may provide the user with a related drawing selection screen, such as a cited claim selection screen, to input the accurate related drawing number. The related drawing selection screen, like the cited claim selection screen, may have a UI that allows the user to select a drawing number that precedes the drawing number being created. When selecting a related drawing in the related drawing selection screen or entering a related drawing number in the drawing description text input element, the drawing brief description input processing unit 124 may examine whether the selection or input of such related drawing satisfies the corresponding description requirements under the Patent Act. The drawing brief description input processing unit 124 may perform a preset operation so that the user can select an appropriate related drawing according to the review result.

[0273] The drawing description creation screen may include a UI for adding a drawing information input unit. For example, a button for adding a new drawing information input unit may be provided on one side of the drawing description creation screen, and when a user clicks this button, the drawing description input processing unit 124 may add a drawing information input unit to the drawing description creation screen. Depending on the embodiment, the function of adding a drawing information input unit may be implemented separately as adding new drawing information and inserting new drawing information, similar to adding a claim on the claim creation screen described above.

[0274] In addition, the drawing brief description creation screen may include a UI for deleting a drawing information input unit. For example, a button for deleting a drawing information input unit may be provided on one side of the drawing brief description creation screen, and when a user selects any drawing information input unit and clicks the delete button, the drawing brief description input processing unit 124 may delete the data of the selected drawing information input unit and then remove the selected drawing information input unit from the drawing brief description creation screen.

[0275] The drawing brief description creation screen may also include a UI for moving the position of a drawing information input unit. For example, the drawing information input unit may be provided as a drag-and-drop HTML object, and a user may select the drawing information input unit to be moved, drag it, and drop it to the desired location to input a command to move the selected drawing information input unit. Depending on the embodiment, the function of moving the drawing information input unit may be implemented by inputting the desired position, as in the above-described claim movement on the claim creation screen, and the method of moving the drawing information input unit does not limit the concept of the present invention.

[0276] The drawing description input processing unit 124 may manage drawing numbers and related drawing numbers in the same manner as the claim input processing unit 122 manages claim numbers and cited claim numbers. That is, the drawing description input processing unit 124 may treat drawing numbers like claim numbers, and related drawing numbers like cited claim numbers. Specifically, when a command to add or insert a new drawing information input unit, a command to delete a drawing information input unit, or a command to move a drawing information input unit is input, the drawing description input processing unit 124 may modify the drawing numbers and related drawing numbers in the same manner as the claim number reorganization in which the claim input processing unit 122 changes claim numbers and cited claim numbers when a command to add or insert a new claim, a command to delete a claim, or a command to move a claim is input.

[0277] For example, when a command to add a new drawing information input unit is input, the drawing brief description input processing unit 124 may automatically set the drawing number text input element of the drawing information input unit to the largest drawing number plus 1. When a command to insert or delete a new drawing information input unit is input, the drawing brief description input processing unit 124 may organize the drawing number and related drawing numbers according to the drawing number of the drawing information input unit to be inserted or deleted. When a command to move a drawing information input unit is input, the drawing brief description input processing unit 124 may process the move command by simultaneously or sequentially performing operations corresponding to the insertion and deletion of the drawing number information input unit.

[0278] In this case, the drawing brief description input processing unit 124 determines whether the correction of the drawing number and related drawing number meets the description requirements of the relevant patent law, and if there is a problem, it outputs a warning message to the user and asks the user to confirm whether to execute the command entered by the user. According to an embodiment, after executing the command entered by the user, the drawing brief description input processing unit 124 may continue to display the generated problem in a pre-set area such as the description requirements review result screen on the patent document creation screen until the problem is resolved.

[0279] Meanwhile, drawing numbers may not only be simple numbers, but may also have a form in which letters are added to numbers, such as 1A, 1B, and 1C. In this case, drawing number input units having drawing numbers each having a combination of one number and a regular letter, such as 1A, 1B, and 1C (hereinafter referred to as "series drawing numbers"), may be treated as a single group by the drawing brief description input processing unit 124. Specifically, when a movement command is input for any of the drawing number input units having series drawing numbers, the drawing brief description input processing unit 124 may simultaneously move all of the drawing number input units having the corresponding series drawing numbers.

[0280] In addition, when a new drawing number input unit is inserted between drawing number input units having a series drawing number, or when a drawing number input unit that was in a different position is moved, the drawing brief description input processing unit 124 sets the drawing number data of the inserted or moved drawing number input unit in accordance with the regularity of the series drawing numbers, and can adjust other series drawing numbers and other drawing numbers accordingly.

[0281] In addition, when any drawing information input unit of a drawing number input unit having a series drawing number is deleted, the drawing brief description input processing unit 124 may update the drawing number data of drawing number input units having other series drawing numbers in accordance with the regularity of the series drawing numbers.

[0282] In addition, when a drawing number other than the series drawing number is changed, the drawing brief description input processing unit 124 can update only the numerical portion of the series drawing number from the data of the drawing number input unit in which the series drawing number is included as the drawing number and related drawing number. For example, if the series drawing numbers are 4A, 4B, and 4C and the user deletes the drawing information input unit with drawing number 2, the drawing brief description input processing unit 124 can update 4A, 4B, and 4C to 3A, 3B, and 3C by changing only the numerical portion, respectively.

[0283] The second processing unit 100c may include one or more of an original data management unit 131, a component extraction unit 132, a component display switching unit 133, a first translation example search unit 134, a second translation example search unit 135, and a machine translation providing unit 136.

[0284] The second service, which can create patent translations, basically requires the original data of the patent specification to be translated. Hereinafter, "original data" may be understood to mean the text data contained in the patent specification to be translated. The original data management unit 131 may manage the original data of the patent specification to be translated, input by the user. Specifically, the user may input the original data of the patent specification to be translated via a patent document preparation application, and the original data management unit 131 may process a series of processes to store and manage the original data input via the patent document preparation application in the memory 14, 24.

[0285] The user may input the original data of the patent specification to be translated by registering a pre-defined format file (e.g., a Word file with a doc or docx extension, a PDF file, etc.) in the patent document creation application, or by directly inputting the original data of the patent specification in text format into the patent document creation application. Depending on the embodiment, the original data management unit 131 may access a network or a route on the Internet specified by the user or a pre-defined network or route on the Internet via the data communication unit 113 to receive a file or text corresponding to the original data of the patent specification.

[0286] In this embodiment, an example will be described in which a user inputs an original file of a patent specification (hereinafter referred to as "original file") that he or she wishes to translate into a preset format via a patent document creation application, and the original data management unit 131 extracts original data from the original file and inputs it into the database 140. There are various well-known techniques for extracting text data from the original file, so a detailed description will be omitted here.

[0287] On the other hand, in this embodiment, the translation of a patent specification will be explained as an example, but as mentioned above, the subject of translation is not limited to patent specifications, but can also be documents such as a notice of opinion submission (notice of reasons for refusal) issued by the Patent Office.

[0288] To this end, the screen configuration unit 101 may configure and provide to a user a screen (hereinafter referred to as an "original data management screen") that allows the user to select and register an original file from the patent document creation device 10 and extract and manage original data from the registered original file. The original data management screen may be provided as a screen for the user to register an original file and a screen for the user to review and edit the original data, and these screens may be configured to be displayed sequentially. Hereinafter, the screen for registering an original file will be referred to as the "original file registration screen," and the screen for reviewing and editing the original data will be referred to as the "original data editing screen." In other words, the original data management screen may be understood to include the original file registration screen and the original data editing screen. The original data management screen may be provided as an independent webpage, as a part of a webpage, as a hidden or foldable area of ​​a webpage, or as a pop-up page or window.

[0289] However, the concept of the present invention is not limited thereto, and the original data management screen may be configured to allow a user to input text data of a patent specification using pre-defined text input elements. Depending on the embodiment, the original data management screen may also be configured to allow a user to selectively input an original file or text data. Furthermore, the original data management unit 131 may send data to the patent document creation server 20 via the data communication unit 113 and store the original data in the database 240. Depending on the embodiment, all data may be stored in the database 140 and the database 240 and managed synchronously.

[0290] On the other hand, the original data management unit 131 may receive language information and document format information that can be input as case information in the case management unit 103 via the original data management screen.

[0291] The original data management unit 131 may manage the original data by dividing it into sentence units. In the original data, a sentence may be understood to include not only a complete sentence having a subject and a predicate, but also a phrase or clause that can express a complete meaning. In addition, the original data management unit 131 may manage the original data by dividing it into paragraph units, each of which includes one or more sentences. For example, a sentence may be divided based on a preset punctuation mark or sentence mark, and a paragraph may be divided based on a line break character.

[0292] Depending on the embodiment, the original data may include data indicating paragraph numbers such as "

[0001] ", ""

[0002] ", etc. The original data management unit 131 examines whether the original data includes data corresponding to such paragraph numbers, and if it determines that the original data includes data corresponding to the paragraph numbers, it may use the data as an identifier for distinguishing paragraphs.

[0293] In addition, the original data management unit 131 can use data indicating claims, such as "Claim 1" and "Claim 2," as identifiers for distinguishing paragraphs, and can treat one claim as one paragraph.

[0294] The patent document creation screen for the second service may be configured to display source data to the user in preset translation units and allow the user to input translation data in the same translation units. In this embodiment, an example will be described in which a sentence unit is used as the minimum translation unit. Depending on the embodiment, a paragraph unit may be used as the translation unit, or a combination of sentence and paragraph units may be used. In addition, the patent document creation screen may manage some items constituting a patent specification in sentence units and other items in paragraph units.

[0295] In order for a user to conveniently input translation data by sentence or paragraph, it is necessary to accurately divide sentences and paragraphs according to the user's intention. To this end, the original data management unit 131 may allow a user to clearly edit the boundaries between sentences and paragraphs of the original data through an original data editing screen. To this end, the original data editing screen may provide a text input element into which original data is input (hereinafter referred to as a "text input element for editing original data").

[0296] The original data management unit 131 may display markers for indicating sentence boundaries and paragraph boundaries when displaying original data in the text input element for editing original data. That is, the original data management unit 131 may preprocess the original data to identify the boundary positions of sentences and paragraphs based on preset conditions, and edit data at the identified boundary positions or add preset marker data to the identified boundary positions, thereby displaying the original data together with the markers.

[0297] In this case, the original data management unit 131 may treat one claim of the original data as one paragraph, and a phrase or clause included in the claim as one sentence. Alternatively, the original data management unit 131 may treat one claim of the original data as one sentence. Alternatively, the original data management unit 131 may treat one independent claim of the original data as one paragraph, a phrase or clause included in the independent claim as a sentence, and one dependent claim as one sentence. Such combinations may be performed in various ways within the scope of the present invention.

[0298] In addition, when a user edits data using a text input element for editing original data, thereby changing the boundary of a sentence or paragraph, the original data management unit 131 may automatically add or remove a corresponding division element. For example, the original data management unit 131 may detect an event occurring in a text input element for editing original data, and if the detected event corresponds to the creation or deletion of a sentence or paragraph, the original data management unit 131 may add a division element to the corresponding position or remove a division element that was present at the corresponding position.

[0299] Any data that allows a user to recognize the boundaries of sentences or paragraphs can be used as a separator. For example, a line feed character, which is not explicitly displayed in the text input element but separates text data so that it is output on the next line, can also be used as a separator. One line feed character can indicate the boundary of a sentence, and two consecutive line feed characters can indicate the boundary of a paragraph. Alternatively, a separator for a sentence can include a predetermined first string, and a separator for a paragraph can include a predetermined second string different from the first string. In this case, the first string and the second string can also include one or more line feed characters. There are no limitations on the type of separator as long as it can be used to allow a user to distinguish between sentences or paragraphs.

[0300] This allows the user to clearly recognize the boundaries of sentences or paragraphs, which are units into which translation data can be input, through the division elements, and the text input element for editing source data allows the user to conveniently edit sentences or paragraphs for translation in the format desired by the user.

[0301] When editing of data using the text input element for editing original data is completed, the original data management unit 131 may extract data input into the text input element for editing original data in response to a user command, and then parse the data to generate original sentence data and original paragraph data. In this case, the original data management unit 131 may assign a unique identification code to each original paragraph data and also to each piece of original sentence data constituting a paragraph. Thus, each piece of original sentence data may have a unique identification value formed by a combination of a paragraph identification code and a sentence identification code. The method of assigning a unique identification value to the extracted original sentence data does not limit the concept of the present invention. For example, the original sentence data may be assigned an identification value unrelated to the paragraph. The original sentence data, paragraph identification code, and sentence identification code generated by the original data management unit 131 may be stored and managed in the database 140.

[0302] As described above, the component management unit 104 can include component names and their translations as component information, and therefore ease of use can be improved if the components that need to be translated can be extracted from the source data all at once and registered and managed by the component management unit 104. To this end, the component extraction unit 132 can extract components that can be managed by the component management unit 104 from the source data.

[0303] Specifically, the component extraction unit 132 may extract data that can be used as the name of a component from the source data based on preset rules. The preset rules may be set differently depending on the language used in the patent specification to be translated or the document format that is the standard for creating the patent specification. Here, the language information and document format that are the standards for the component extraction unit 132 to select the preset rules may be input via the case management unit 103 or the source data management unit 131, or may be the result of the component extraction unit 132 reading out the source data.

[0304] Before applying the preset rules, the source data may undergo text preprocessing by the component extraction unit 132. Examples of text preprocessing include tokenization, cleaning, normalization, stemming, lemmatization, stopword removal, regular expression processing, data splitting, integer encoding, one-hot encoding, and word segmentation. Such text preprocessing may be applied as part of the preset rules.

[0305] As an example of a preset rule, the component extraction unit 132 may first extract a string that can be used as a drawing code from the original data (hereinafter referred to as a "drawing code string"), and then extract a string that appears before the drawing code string as the name of the component. Specifically, the component extraction unit 132 may extract, as the drawing code string, a string consisting of one or more numeric strings or a combination of numeric and alphabetic characters that is written in parentheses or distinguishably written as a space in the original data. According to an embodiment, the component extraction unit 132 may extract, as the drawing code string, a string consisting of one or more numeric strings or a combination of numeric and alphabetic characters without checking the parentheses or space, or in parallel with checking the parentheses or space. In this case, the component extraction unit 132 may determine whether to use the data extracted as the drawing code string as the drawing code string based on the number of times the data appears in the original data.

[0306] The component extraction unit 132 may extract the name of a component by analyzing a string of characters of a predetermined length or less that is placed before a drawing code string. As an example, the component extraction unit 132 may extract the name of a component based on the number of times that a string of characters of a predetermined length or less that is placed before a drawing code string appears in the original data. Note that a string of characters of a predetermined length or less may be understood to include a set of characters classified as blank characters that is equal to or less than a predetermined number. As another example, the component extraction unit 132 may extract the name of a component based on whether a string of characters of a predetermined length or less that is placed before a drawing code string appears in the original data corresponding to the claims. As yet another example, the component extraction unit 132 may extract the name of a component based on whether a string of characters of a predetermined length or less that is placed before a drawing code string is used together with an antecedent in the original data.

[0307] As another example of a preset rule, the component extraction unit 132 may extract a continuous string of characters of a preset length or less from the source data, and extract the name of a component based on the number of times the extracted string appears in the entire source data. For example, if the extracted string appears two or more times in the source data, the component extraction unit 132 may extract it as the name of a component. Alternatively, the component extraction unit 132 may extract the name of a component based on whether the extracted string appears in the source data corresponding to the claims or the number of times it appears.

[0308] As another example of a preset rule, the component extraction unit 132 may extract a continuous string of characters of a preset length or less from the source data, and extract the name of the component based on whether the extracted string is used together with an antecedent in the source data.

[0309] As another example of a preset rule, the component extraction unit 132 performs a morpheme analysis or a part-of-speech analysis of each word or character string of each source sentence data included in the source data, and if a combination of morphemes or a combination of parts of speech meets a preset condition, the component extraction unit 132 may extract a combination of words or character strings that meets the condition as the name of a component. In this case, a combination of morphemes or a combination of parts of speech may be composed of one morpheme or one part of speech.

[0310] In the above-mentioned string extraction process, the component extraction unit 132 may ignore exceptional strings such as antecedents, articles, particles, conjunctions, and predicates. A set of exceptional strings may be preset and stored depending on the language or document format. For example, the component extraction unit 132 may extract strings after removing data corresponding to exceptional strings from the source data, or may make a determination after excluding exceptional strings from comparison targets if the exceptional strings are included in a string of a length less than a preset length.

[0311] On the other hand, when comparing strings, component extraction unit 132 can treat them as the same string if there are differences in case, such as between uppercase and lowercase letters, between singular and plural expressions, etc. To this end, component extraction unit 132 may have a function for switching between uppercase and lowercase letters and between singular and plural expressions.

[0312] The component extraction unit 132 may extract components from source data using one or more of the predefined rules described above. When multiple rules are applied, the component extraction unit 132 may assign a priority or apply a weight to each rule. Alternatively, the component extraction unit 132 may extract data that satisfies two or more of the multiple rules as a component.

[0313] Meanwhile, the component extraction unit 132 can transmit the extracted components to the component management unit 104, and the component management unit 104 can manage the data transmitted from the component extraction unit 132 as components and can be provided to input a translation for the data received as component information. Thus, the user can quickly register multiple components without having to register each main component to be translated in the component management unit 104.

[0314] In this case, the elements extracted using the above method may include elements that are not actually elements that constitute the invention. For example, the extracted elements may include parts of text that express or explain elements that constitute the invention, rather than the names of elements that actually constitute the invention. Since it would be inefficient to transmit all of this data to the element management unit 104 and manage it as elements, the element extraction unit 132 may provide the user with a "element selection screen" so that the user can select data that they wish to manage as elements.

[0315] The screen configuration unit 101 configures an element selection screen and can provide it to a user when the user saves original data on the original data editing screen or when a preset event occurs on the patent document creation screen. The element selection screen can be provided as an independent web page, a partial area of ​​the web page, a hidden or foldable area on the web page, or a pop-up page or window.

[0316] The component selection screen may include a candidate component area and a saved component area. The candidate component area may display components extracted by the component extraction unit 132, and the saved component area may display components selected in the candidate component area. The component extraction unit 132 may basically output the extracted character string as the component name in the candidate component area, and may also further display the corresponding drawing code character string and one or more of the number of times the extracted character string appears in the source data.

[0317] When a user selects one or more pieces of data displayed in the candidate component area or generates an event to move the selected pieces of data to the saved component area after selection, the selected pieces of data can be moved directly to the saved component area and displayed. Conversely, when a user selects one or more pieces of data displayed in the saved component area or generates an event to move the selected pieces of data to the candidate component area after selection, the selected pieces of data can be moved directly to the candidate component area and displayed.

[0318] The element selection screen may include a UI such as a button for generating an event to transmit data included in the saved element area to the element management unit 104 and register it as an element, and when the user generates the event, the element extraction unit 132 may transmit the data included in the saved element area to the element management unit 104. In this case, the element extraction unit 132 may basically transmit a character string corresponding to the name of the element to the element management unit 104, and if there is a corresponding drawing code character string, may also transmit it to the element management unit 104.

[0319] In this manner, the user can easily select the components that he / she wishes to manage and facilitate translation through the component management unit 104 from among the components extracted by the component extraction unit 132, and register them in the component management unit 104 all at once.

[0320] In this case, the component extraction unit 132 may register the translation of the extracted component as component information in the component management unit 104. Specifically, the component extraction unit 132 may directly inquire about the translation of the extracted component from the first translation storage unit 172, the second translation storage unit 174, and the translation vocabulary list storage unit 175, which will be described later, or may inquire about the translation through the first translation example search unit 134, the second translation example search unit 135, and the machine translation providing unit 136. If a translation corresponding to the extracted component exists, the translation may be stored in the component management unit 104 as component information.

[0321] Meanwhile, the element selection screen can also be called up on the patent document creation screen, and in this case, the saved element area may include elements that have already been selected and managed by the element management unit 104. In this case, if the user moves any element from the saved element area to the candidate element area and then saves it, the element may also be deleted from the elements managed by the element management unit 104.

[0322] The patent document creation screen displays the original data to be translated, and provides a UI that allows input of translation data for the original data. When translation data is input in sentence units as in this embodiment, the original data may be divided and displayed in units of original sentence data generated by the original data management unit 131. Meanwhile, in the second service, the component management unit 104 may manage the names of components and their translations as component information, and the component names may be part of the original data. In other words, the original data displayed on the patent document creation screen may include the names of the components managed by the component management unit 104. Hereinafter, the names of the components included as part of the original data will be referred to as "component displays."

[0323] The component display switching unit 133 can switch the component display of the original data displayed on the patent document creation screen to a corresponding translation, or switch the switched translation to a component display. Hereinafter, the component display switched to a corresponding translation and displayed as part of the original data will be referred to as a "translation display." In other words, the component display switching unit 133 can switch between the component display and the translation display on the patent document creation screen.

[0324] The patent document creation screen may be provided with a UI such as a button that generates a switching event that switches between the component display and the translation display by the component display switching unit 133. For example, the button that generates the switching event may be a toggle button that displays the current state and allows the user to clearly recognize the state switch.

[0325] When a switching event occurs, the component display switching unit 133 determines whether the original data output on the patent document creation screen includes a component display or a translation display. If the original data includes a component display or a translation display, the component display switching unit 133 may query the translation or name of the corresponding component via the component management unit 104, and then change the component display or translation display included in the original data to the translation or name of the previously-queried component. According to an embodiment, the component display switching unit 133 may query the translation or name of the component via the component management unit 104 in advance and store it in a variable before use.

[0326] In this case, the component display switching unit 133 may format the component display or translation display so that it can be recognized as distinct from other text portions of the original data that includes it. For example, the component display or translation display may be output in a font color different from that of other text portions of the original data.

[0327] Depending on the embodiment, the element display switching unit 133 may provide a function of switching between element display and translation display, as well as a function of switching to simultaneous original-translation display in which the element name and the corresponding translation are output together.

[0328] The user can perform translation work more conveniently by using the component display switching unit 133 to display, as source data, a component display or translation display based on the language the user is more familiar with.

[0329] The patent document creation screen is provided to display source text data to the user in translation units so that the user can input corresponding translation data. In this case, the patent document creation screen may provide translation examples so that the user can translate while referring to translation results similar to the source text data to be translated, and the translation examples provided may also be provided to correspond to the translation units applied to the patent document creation screen. In this embodiment, the patent document creation screen provides source text data so that translation can be performed sentence by sentence, and the translation examples may also be provided sentence by sentence.

[0330] The translation examples may include a first translation example, which is the translation result of the source text data currently being worked on, and a second translation example, which is the translation result of another patent document. The first translation example and the second translation example each consist of a pair of source text data and its corresponding translation data, and the first translation example and the second translation example may be stored and managed in one or more of databases 140 and 240. Depending on the embodiment, the second translation example may be provided by a third party and provided to the patent document creation device 10 via the external service linkage unit 111. The first translation example and the second translation example may be managed as translation unit data in databases 140 and 240. For example, the source text data and translation data included in the first translation example and the second translation example may be generated on a sentence-by-sentence basis and stored in one row of a single table so as to match each other, or may be stored in different tables but with corresponding key values.

[0331] The patent document creation screen can provide one or more of the first translation example and the second translation example in response to a user request, and therefore can include one or more of a first translation example display area in which the first translation example is displayed and a second translation example display area in which the second translation example is displayed. Depending on the embodiment, the first translation example display area can also be a translation result display area to be switched, as described below. In this embodiment, an example will be described in which the patent document creation screen provides both the first translation example and the second translation example.

[0332] The patent document creation screen may be provided with UIs such as a first translation example search button that generates an event requesting the display of a first translation example similar to the source text data the user is trying to translate, and a second translation example search button that generates an event requesting the display of a second translation example. The first translation example search button and the second translation example search button may be provided for each source text data provided in a translation unit, and when the button is clicked, translation example search results based on the corresponding source text data may be output in the first translation example display area and the second translation example display area. The first translation example display area and the second translation example display area may be switched between hidden and visible states depending on whether the first translation example search button and the second translation example search button are clicked.

[0333] The first translation example search unit 134 may search for a first translation example having original text data similar to the original text data requested by the user and provide it to the user. The data requested by the user and the corresponding first translation example may be set in translation units. That is, in this embodiment, the first translation example search unit 134 may search for similar data in sentence units, and the search results and corresponding translation data may also be provided in sentence units. For example, the first translation example search unit 134 may inquire whether there is original text data stored in the first original text storage unit 171 (described later) that is similar to the original text data requested by the user, and then load translation data corresponding to the original text data determined to be similar from the first translation text storage unit 172 (described later) and output it to the first translation example display area. If there is no translation data corresponding to the original text data determined to be similar, the first translation example search unit 134 may output only the original text data determined to be similar.

[0334] Whether the original text data requested for search by the user and the original text data of the first translation example are similar may be determined as a result of comparison of the entire translation unit. In other words, in this embodiment, the first translation example search unit 134 may determine whether the sentence requested for search by the user and the sentence saved as the first translation example are similar by comparing them as a whole.

[0335] The second translation example search unit 135 may search for second translation examples having original text data similar to the original text data requested by the user and provide the second translation examples to the user. The data requested by the user and the corresponding second translation examples may be set in translation units. That is, in this embodiment, the second translation example search unit 135 may search for similar data in sentence units, and the search results and corresponding translation data may also be provided in sentence units. For example, the second translation example search unit 135 may inquire whether there is original text data stored in the second original text storage unit 173 (described later) that is similar to the original text data requested by the user, and may load translation data corresponding to the original text data determined to be similar from the second translation text storage unit 174 (described later) and output the translation data to the second translation example display area.

[0336] Whether the original text data requested for search by the user and the original text data of the second translation example are similar to each other may be determined as a result of comparison of the entire translation unit. In other words, in this embodiment, the second translation example search unit 135 may determine whether the sentence requested for search by the user and the sentence stored as the second translation example are similar to each other by comparing them as a whole.

[0337] The first translation example search unit 134 and the second translation example search unit 135 may digitize the similarity of both data to be compared, and may determine that both data are similar if the similarity falls within a preset range. For example, the similarity may be calculated based on the number of matching characters or words between both source text data, or may be calculated using the edit distance.

[0338] Furthermore, the similarity may be calculated based on natural language processing. As an example, the first translation example search unit 134 and the second translation example search unit 135 may determine the similarity by using a statistical language model (SLM) such as N-gram, or a count-based word representation such as a term-document matrix or TF-IDF (Term Frequency-Inverse Document Frequency).

[0339] In addition, the similarity may be calculated using a result of learning based on a machine running or deep running model for natural language processing. For example, the first translation example search unit 134 and the second translation example search unit 135 may utilize a result of learning using a model such as a recurrent neural network (RNN), a long short-term memory (LSTM), or a gated recurrent unit (GRU).

[0340] The similarity can also be calculated using word embedding, which expresses words in the form of dense vectors, and the resulting embedding vector. For example, the first translation example search unit 134 and the second translation example search unit 135 can generate embedding vectors (which can be understood as including data calculated from the embedding vectors for determining similarity) for each word and sentence using a word embedding model such as Word2Vec or FastText, and can use the cosine similarity value calculated based on this as the similarity value to determine whether the two sentences to be compared are similar.

[0341] In this case, the embedding vectors of the original data or translated data belonging to the first translation example and the second translation example may be stored together with corresponding data in the first original text storage unit 171, the first translated text storage unit 172, the second original text storage unit 173, and the second translated text storage unit 174. In this case, the first translation example search unit 134 and the second translation example search unit 135 may load and use only the embedding vectors, rather than the original text data or translated data, when comparing similarities, thereby reducing the time required for determining similarity. Specifically, when a translation example search request event occurs, the first translation example search unit 134 and the second translation example search unit 135 may generate an embedding vector of the data requested by the user and compare it with the embedding vectors of pre-calculated translation examples to extract translation examples with high similarity.

[0342] In addition to the cosine similarity mentioned above, the similarity can also be calculated using the Euclidean distance, the Jaccard index, the Manhattan distance, and the like.

[0343] Meanwhile, the first translation example search unit 134 and the second translation example search unit 135 may use different similar data determination methods. For example, the first translation example search unit 134 may determine similar sentences based on a similarity value calculated using a simple N-gram, and the second translation example search unit 135 may determine similar sentences based on a cosine similarity value of an embedding vector generated using word embedding. Also, the first translation example search unit 134 and the second translation example search unit 135 may use the same similar data determination method, but may apply different specific variable values. For example, both the first translation example search unit 134 and the second translation example search unit 135 may calculate similarity using N-gram, but the first translation example search unit 134 may calculate similarity based on two characters, and the second translation example search unit 135 may calculate similarity based on three characters.

[0344] Furthermore, the first translation example search unit 134 and the second translation example search unit 135 can use a combination of multiple similarity calculation methods. For example, the first translation example search unit 134 and the second translation example search unit 135 can use a method such as applying a priority order to multiple similarity calculation methods or adding up and sorting the similarities.

[0345] The first translation example search unit 134 and the second translation example search unit 135 can output the first translation example and the second translation example queried by the similarity judgment as described above to the first translation example display area and the second translation example display area of ​​the patent document creation screen, respectively.

[0346] Similar to the provision of translation examples described above, the patent document creation screen can provide machine translation results for original data at the user's request, and for this purpose may include a machine translation display area in which the machine translation results are displayed.

[0347] The patent document creation screen may be provided with a UI such as a machine translation button that generates an event requesting the machine translation results of the source text data that the user wishes to translate. A machine translation button may be provided for each source text data provided in translation units, and when the button is clicked, the machine translation results based on the corresponding source text data may be output in the machine translation display area. In other words, a machine translation display area may be provided for each source text data. The machine translation display area may be switched between hidden and visible states depending on the click of the machine translation button.

[0348] The machine translation providing unit 136 may perform machine translation of source data requested by a user into a target language to be translated and then output the result to a machine translation display area. In this case, the machine translation providing unit 136 may treat the second language input via the case management unit 103 or the source data management unit 131 as the language of the source data and perform machine translation using the first language as the target language to be translated. The machine translation providing unit 136 may receive source data in translation units, perform machine translation, and provide the translated results in translation units.

[0349] The machine translation providing unit 136 may be a machine translation engine that can independently perform machine translation, or may be configured to provide original data to a third party and receive and provide the results. In the latter case, the machine translation providing unit 136 may cooperate with the external service cooperation unit 111, or may independently use a machine translation service provided by a third party.

[0350] In this embodiment, the components of the processor 100 are described as being included in the common processing unit 100a, the first processing unit 100b, and the second processing unit 100c, respectively. However, the concept of the present invention is not limited thereto. For example, a component included in the common processing unit 100a may be included in the first processing unit 100b or the second processing unit 100c depending on the embodiment, and a component included in the first processing unit 100b or the second processing unit 100c may be included in the common processing unit 100a depending on the embodiment. Furthermore, a component included in the first processing unit 100b or the second processing unit 100c may be included in the second processing unit 100c or the first processing unit 100b depending on the embodiment. Furthermore, it may be understood that any component is simultaneously included in two or more of the common processing unit 100a, the first processing unit 100b, and the second processing unit 100c.

[0351] Furthermore, the components of the processor 100 described above are provided as examples. The components included in the processor 100 may be physically and logically separated from each other or integrated in a manner that can be implemented as program code, and implemented as new components. In this case, a new component that performs the same function as any component of the processor 100 may be understood to correspond to any of the components.

[0352] Meanwhile, the functions executed by the components of the processor 100 in the aforementioned patent document production device 10 can also be executed by the processor 200 of the patent document production server 20. Specifically, the processor 200 of the patent document production server 20 can include a common processing unit 200a, a first processing unit 200b, and a second processing unit 200c that can correspond to the common processing unit 100a, the first processing unit 100b, and the second processing unit 100c of the patent document production device 10, respectively, and the common processing unit 200a, the first processing unit 200b, and the second processing unit 200c of the patent document production server 20 can have technical features corresponding to the common processing unit 100a, the first processing unit 100b, and the second processing unit 100c of the aforementioned patent document production device 10.

[0353] Specifically, the common processing unit 200a of the patent document creation server 20 includes a screen configuration unit 101, a data management unit 102, a case management unit 103, a component management unit 104, an auto-completion list generation unit 105, a text input element management unit 106, a drawing management unit 107, a description requirement examination unit 108, a download file generation unit 109, a setting management unit 110, an external service cooperation unit 111, a user management unit 112, a data communication unit 113, and the like in the patent document creation device 10. The first processing unit 200b of the patent document creation server 20 may include one or more of a screen configuration unit 201, a data management unit 202, a case management unit 203, a component management unit 204, an auto-completion list generation unit 205, a text input element management unit 206, a drawing management unit 207, a description requirement examination unit 208, a download file generation unit 209, a setting management unit 210, an external service cooperation unit 211, a user management unit 212, a data communication unit 213, and a change content management unit 214, which may correspond to the idiomatic expression management unit 121, the claim input processing unit 122, the component description input processing unit 123, and the drawing brief description input processing unit 124 in the patent document creation device 10, respectively. In addition, the second processing unit 200c of the patent document creation server 20 may include one or more of an original data management unit 231, a component extraction unit 232, a component display switching unit 233, a first translation example search unit 234, a second translation example search unit 235, and a machine translation providing unit 236, which may correspond to the original data management unit 131, the component extraction unit 132, the component display switching unit 133, the first translation example search unit 134, the second translation example search unit 135, and the machine translation providing unit 136, respectively, in the patent document creation device 10.

[0354] In this regard, in the above description of the components of the processor 100 of the patent document drafting device 10, the description of transmitting data to the patent document drafting server 20 or receiving data from the patent document drafting server 20 and using it may be understood that the corresponding components of the processor 200 transmit data to the patent document drafting device 10, receive data from the patent document drafting device 10, or use data stored in the patent document drafting server 20. Also, in the above description of the components of the processor 100 of the patent document drafting device 10, the description of using data stored in the patent document drafting server 20 may be understood that the corresponding components of the processor 200 receive and use data stored in the patent document drafting device 10, or use data stored in the patent document drafting server 20.

[0355] Each of the components corresponding to each other in the processor 100 of the patent document production device 10 and the processor 200 of the patent document production server 20 may be provided in either the processor 100 of the patent document production device 10 or the processor 200 of the patent document production server 20, or may be selectively provided in either the processor 100 of the patent document production device 10 or the processor 200 of the patent document production server 20. When any component is provided in both the processor 100 of the patent document production device 10 and the processor 200 of the patent document production server 20, the function of the component may be executed in either the processor 100 of the patent document production device 10 or the processor 200 of the patent document production server 20, or some functions may be executed by the processor 100 of the patent document production device 10 and other functions by the processor 200 of the patent document production server 20. For example, each component of processor 100 of patent document drafting device 10 may collect data from a patent document drafting application or a patent document drafting screen, transmit it to the corresponding component of processor 200 of patent document drafting server 20, and output the data transmitted from the corresponding component of processor 200 of patent document drafting server 20 to the patent document drafting application or the patent document drafting screen. Each component of processor 200 of patent document drafting server 20 may perform the function of the corresponding component of processor 100 of patent document drafting device 10 based on the data transmitted from the corresponding component of processor 100 of patent document drafting device 10, and may transmit the execution result to the corresponding component of processor 100 of patent document drafting device 10. In this case, each component of processor 200 of patent document drafting server 20 may use not only memory 14 and database 140 of patent document drafting device 10, but also memory 24 and database 240 of patent document drafting server 20 for data management.

[0356] Furthermore, any of the components may be provided only in the processor 100 of the patent document drafting device 10 or only in the processor 200 of the patent document drafting server 20. In this case, the component can independently perform its function. For example, a component provided only in either the processor 100 of the patent document drafting device 10 or the processor 200 of the patent document drafting server 20 can perform the data management and data processing functions required by the component without transmitting or receiving data to or from other devices via the network 30.

[0357] The components provided to the processor 200 of the patent document creation server 20 may receive and process data required to perform their functions from the patent document creation device 10. For example, the processor 200 of the patent document creation server 20 may receive and process data entered via a patent document creation application or a patent document creation screen from the patent document creation device 10. Furthermore, the components provided to the processor 200 of the patent document creation server 20 may transmit data provided to a user via the patent document creation application or the patent document creation screen, or data required to perform the functions of the patent document creation application or the patent document creation screen, to the patent document creation device 10.

[0358] The data sent by the processor 100 of the patent document drafting device 10 to the processor 200 of the patent document drafting server 20 may be data entered via a patent document drafting application or a patent document drafting screen, or data processed by the processor 100 of the patent document drafting device 10. The processor 100 of the patent document drafting device 10 may transmit data stored in the memory 14 or processed data to the processor 200 of the patent document drafting server 20. The processor 100 of the patent document drafting device 10 may also provide data from the patent document drafting device 10 requested by the processor 200 of the patent document drafting server 20. The processor 100 of the patent document drafting device 10 may also provide data provided by a third party or processed data to the processor 200 of the patent document drafting server 20. The processor 100 of the patent document drafting device 10 may also provide the results of processing the above data collectively to the processor 200 of the patent document drafting server 20.

[0359] The data transmitted from the processor 200 of the patent document production server 20 to the processor 100 of the patent document production device 10 may be the result of the processor 200 of the patent document production server 20 processing or modifying data received from the processor 100 of the patent document production device 10. The processor 200 of the patent document production server 20 may also transmit data stored in the memory 24 or modified data to the processor 100 of the patent document production device 10. The processor 200 of the patent document production server 20 may also provide data from the patent document production server 20 requested by the processor 100 of the patent document production device 10. The processor 200 of the patent document production server 20 may also provide data provided by a third party or modified data to the processor 100 of the patent document production device 10. The processor 200 of the patent document production server 20 may also provide the processor 100 of the patent document production device 10 with the result of processing the above data collectively.

[0360] The data exchange between the patent document drafting device 10 and the patent document drafting server 20 is performed via the communication module 18 of the patent document drafting device 10 and the communication module 28 of the patent document drafting server 20, and can be controlled by the data communication unit 113 of the patent document drafting device 10 and the data communication unit 213 of the patent document drafting server 20. In addition, each component can send and receive data directly or by using the data communication unit 113 of the patent document drafting device 10 and the data communication unit 213 of the patent document drafting server 20.

[0361] FIG. 4 is a diagram showing an example of the memory configuration of the patent document preparation device and the patent document preparation server shown in FIG.

[0362] Referring to FIG. 4, the database 140 may include a common storage unit 140a for managing data commonly required for the first and second services, a first storage unit 140b for managing data for the first service, and a second storage unit 140c for managing data for the second service. In this embodiment, the configuration of the database 140 is described as being divided into the common storage unit 140a, the first storage unit 140b, and the second storage unit 140c. However, the concept of the present invention is not limited to the common storage unit 140a, the first storage unit 140b, and the second storage unit 140c being physically or logically separate. For example, the database 140 may be realized as a single integrated database rather than being divided into the common storage unit 140a, the first storage unit 140b, and the second storage unit 140c. Furthermore, depending on the embodiment, if the patent document creation device 10 provides only the first service or the second service, the second storage unit 140c or the first storage unit 140b may be omitted. In this case, the common storage unit 140a may not be provided separately, and the elements of the common storage unit 140a and the elements of the first storage unit 140b or the second storage unit 140c may be implemented as a single integrated database. Also, the common storage unit 140a, the first storage unit 140b, and the second storage unit 140c may be understood as being conceptually separate, and elements belonging to any of the common storage unit 140a, the first storage unit 140b, and the second storage unit 140c may be understood as being included in another set or as being included in duplicate, depending on the embodiment.

[0363] As described above, each component of database 140 and database 240 may be realized as a web DB, and may perform functions such as storing data, providing stored data, modifying stored data, and deleting stored data in response to requests from components of processor 100 of patent document creation device 10 or processor 200 of patent document creation server 20. However, the concept of the present invention is not limited thereto, and other data storage locations, files, etc. may be used as a means for storing data.

[0364] Each component of the processor 100 mentioned in the following description of database 140 and database 240 can be understood as a component of the processor 200 of the corresponding patent document creation server 20, and can be understood to involve data exchange between the patent document creation device 10 and the patent document creation server 20.

[0365] 140a may include one or more of a screen configuration information storage unit 141, a case information storage unit 142, a component information storage unit 143, an auto-completion dataset storage unit 144, a drawing storage unit 145, a description requirement storage unit 146, a setting storage unit 147, an external service information storage unit 148, a user information storage unit 149, and a change content storage unit 150.

[0366] The screen configuration information storage unit 141 stores configuration information of a screen configured by the screen configuration unit 101, specifically, the structure and content of the screen configured by the screen configuration unit 101. The screen configuration information storage unit 141 may be understood to store all data required for screen configuration by the screen configuration unit 101, and the manner in which the screen configuration information storage unit 141 stores data does not limit the concept of the present invention. For example, the screen configuration information storage unit 141 may be implemented as a web DB or a part of a web DB as described above, and may include a file, a part of a file, or content stored in a file that is stored in memory 14 and directly output via a patent document preparation application, or a file or resource that can be referenced by the file. For example, the screen configuration information storage unit 141 may include HTML, CSS, JavaScript files, etc.

[0367] The screen configuration information storage unit 141 may include different screen configuration information depending on the service provided by the patent document creation screen. For example, the screen configuration information storage unit 141 may include first screen configuration information constituting the patent document creation screen for a first service and second screen configuration information constituting the patent document creation screen for a second service. Such first screen configuration information and second screen configuration information may include various UI components, including the arrangement of one or more text input elements, for providing each service.

[0368] The screen configuration information storage unit 141 may also include screen configuration information that varies depending on the language environment of the user using the patent document creation application, so that different screens can be provided depending on the language environment of the user.The screen configuration information storage unit 141 may also include screen configuration information according to the document format, so that different screens can be provided depending on the document format of the case information managed by the case management unit 103.

[0369] As a specific example, the screen configuration information storage unit 141 may include data or script files corresponding to each language so that a screen configuration for a Korean user and a screen configuration for an English user can be different, and the screen configuration unit 101 may configure a screen by loading the corresponding data or script file from the screen configuration information storage unit 141 according to the user environment sent from the web browser or the language used determined based thereon. Also, the screen configuration information storage unit 141 may include data or script files for outputting patent document creation screens corresponding to Korean patent document formats and U.S. patent document formats, respectively, and the screen configuration unit 101 may configure a screen by loading the corresponding data or script file from the screen configuration information storage unit 141 based on case information input via the case management unit 103.

[0370] Meanwhile, a user may adjust the structure of a screen output via the patent document creation application, or set or change the type, content, position, shape, etc. of content displayed on the screen, and the data for this may be stored in the screen configuration information storage unit 141 as environmental variables for the patent document creation application or the patent document creation screen. For example, a user may switch the display state of one of multiple areas provided on the patent document creation screen using the patent document creation application, and this display state may be recorded in the screen configuration information storage unit 141. Then, when the user subsequently accesses the patent document creation screen again, the screen configuration unit 101 may configure a screen with the same structure as the existing one based on the data stored in the screen configuration information storage unit 141 and provide it to the user.

[0371] The case information storage unit 142 may store case information managed by the case management unit 103. For example, the case information storage unit 142 may store a management number, a case name, a deadline, a client, a technical field, a document format, a storage method, translation language information, etc. as case information. The case information stored in the case information storage unit 142 may be managed through a case management screen.

[0372] As described above, the screen configuration unit 101 can configure a patent document creation screen by loading a screen structure for each document format stored in the screen configuration information storage unit 141 based on the document format, which is case information stored in the case information storage unit 142.

[0373] In addition, the translation language information stored in the case information storage unit 142 may be used by the components of the second processing unit 100c to provide an appropriate translation service. Specifically, the first language information stored in the case information storage unit 142 may be used as the language of a translation by the first translation example search unit 134, the second translation example search unit 135, the machine translation providing unit 136, etc., and the second language information may be used as the language of an original text by the original text data management unit 131, the component extraction unit 132, the first translation example search unit 134, the second translation example search unit 135, the machine translation providing unit 136, etc. More specifically, the original text data management unit 131 may apply different criteria for dividing original text data into translation units based on the second language information, and the component extraction unit 132 may apply different criteria for extracting components based on the second language information. The first translation example search unit 134 and the second translation example search unit 135 apply different similar sentence search algorithms or models depending on the first language information and the second language information, and the machine translation providing unit 136 may use a corresponding machine translation engine based on the first language information and the second language information, or may transmit the translation language information together with the original text data to a service provided by a third party.

[0374] The component information storage unit 143 may store information about the components managed by the component management unit 104. For example, the component information storage unit 143 stores multiple components, and the information about each component may include the name of the component, an identification number corresponding to the component, a translation of the component, an identification number of the translation of the component, whether the component is used, and the number of times it is used. In addition, the component information storage unit 143 may set a unique key value for each component and manage multiple pieces of information about one component as one data set corresponding to the key value. The component information stored in the component information storage unit 143 may be managed using a component management screen.

[0375] The component information storage unit 143 may store component information separately and independently for each case. For example, data stored in the component information storage unit 143 may have a management number in the case information as an identification value. As a result, component information for different cases may be managed independently within the component information storage unit 143, and a component in one case may not be used in another case. Hereinafter, the characteristic of being stored or managed independently for each case will be referred to as "case-dependent."

[0376] The auto-completion dataset storage unit 144 may store a dataset for generating an auto-completion list. The dataset stored in the auto-completion dataset storage unit 144 may also vary depending on the case. As described above, a dataset for auto-completion may include one or more auto-completion items, and each item may be generated based on data provided from a predefined data source, such as the component information storage unit 143 or the idiomatic expression storage unit 161 (described later). When data in a data source is changed, the auto-completion dataset storage unit 144 may automatically update the dataset to correspond to the changed data. The auto-completion list generator 105 may create an auto-completion list that matches the text entered by the user from the dataset stored in the auto-completion dataset storage unit 144 and provide it to the text input element manager 106. For example, the auto-completion dataset storage unit 144 may store an auto-completion dataset as part of a web database, as a file directly accessed via a patent document drafting application, as part of a file, as content stored in a file, or as a file or resource that can be referenced by the file.

[0377] The drawing storage unit 145 may store one or more drawings managed by the drawing management unit 107. The drawings stored in the drawing storage unit 145 may also be case-dependent. The drawing storage unit 145 may directly store drawing files, store an access path for accessing the drawing files, or store the drawing files after converting them into a preset format. The drawing information stored in the drawing storage unit 145 may be managed using a drawing management screen.

[0378] The description requirements storage unit 146 may store description requirements that can be used by one or more of the description requirements review unit 108 and the claim input processing unit 122. As mentioned above, patent laws are enacted in each country, and the description requirements required therefor are set differently. Therefore, the description requirements storage unit 146 may also include description requirements based on the document format so that different standards can be applied depending on the document format in the case information managed by the case management unit 103. For example, the description requirements storage unit 146 may store data as description requirements, such as the types of data that must be included in patent applications depending on the document format, the correct way to write the brief description of the drawings, the correct way to write the detailed description of the invention, the correct way to write claim numbers and cited claim numbers, whether drawing symbols should be included in the elements of claims, whether duplicate claim citations are permitted, and expressions that are not permitted when drafting claims. Such description requirements may be stored in a web database, or may be a file, part of a file, or content stored in a file, or a file or resource that can be referenced by the file, stored in memory 14 and directly accessed via a patent document drafting application.

[0379] The description requirements stored in the description requirement storage unit 146 can only be modified by an administrator of the patent document creation system 1 or the patent document creation server 20. For example, if the description requirements need to be changed due to amendments to the patent law or related laws of a particular country, the patent document creation server 20 transmits the updated description requirement data to the description requirement review unit 108, and the substrate requirement review unit 108 can change the data stored in the description requirement storage unit 146 to the received new data before using it.

[0380] The setting storage unit 147 may store setting information required for patent document creation by the patent document creation application managed by the setting management unit 110. For example, the setting storage unit 147 may store the type of language used in the overall UI of the patent document creation application, the design theme and text format applied to the overall UI of the patent document creation application, the format of downloaded files, etc. At least a portion of the setting information stored in the setting storage unit 147 may be managed by a setting management screen.

[0381] The external service information storage unit 148 may store information necessary for accessing an external service provided by a third party so that the external service cooperation unit 111 can use the external service. For example, the external service information storage unit 148 may store information such as an access path to the external service, authentication information necessary for using the external service, and variables necessary for using the external service.

[0382] The external service information stored in the external service information storage unit 148 can only be modified by an administrator of the patent document creation system 1 or the patent document creation server 20. For example, if the URL of an API provided by a third party is changed, the patent document creation server 20 transmits the updated URL to the external service collaboration unit 111, and the external service collaboration unit 111 can change the data stored in the external service information storage unit 148 to the received new data before using it.

[0383] The user information storage unit 149 may store user information managed by the user management unit 112. The user information may include account information and usage history information, and the user management unit 112 may execute user login processing, session management, and the like based on the information stored in the user information storage unit 149.

[0384] The change content storage unit 150 may store the changes managed by the change content management unit 114. Specifically, the change content storage unit 150 may store data at a first time point, data at a second time point, and the difference between the two data. As described above, the change content storage unit 150 may store the difference between the two data by classifying it into added content and deleted content, or may store it as text data to which a preset format is applied. The data stored in the change content storage unit 150 may be case-dependent.

[0385] The first storage unit 140b may include one or more of an idiomatic expression storage unit 161, a basic description storage unit 162, a detailed description storage unit 163, a claim storage unit 164, an element description storage unit 165, and a brief description storage unit 166 of drawings.

[0386] The idiomatic expression storage unit 161 may store idiomatic expressions managed by the idiomatic expression management unit 121. As described above, idiomatic expressions include both idioms and idiomatic phrases, and the idiomatic expression storage unit 161 may store idioms and idiomatic phrases by assigning distinguishable identification codes to them. The idiomatic phrases stored in the idiomatic expression storage unit 161 may include replacement parts as described above, and in this case, a separate identification code may be assigned to the idiomatic phrases including the replacement parts. The idiomatic expressions stored in the idiomatic expression storage unit 161 may be managed using an idiomatic expression management screen. Depending on the embodiment, the idiomatic expression storage unit 161 may be configured separately into an idiom storage unit that stores idioms and an idiomatic phrase storage unit that stores idioms, and separate idiomatic expression management screens may be provided accordingly.

[0387] In this embodiment, the idiomatic expression storage unit 161 is described as a component of the first storage unit 140b, but in some embodiments, the patent document creation application may be configured so that idiomatic expressions can also be used in the second service, in which case the idiomatic expression storage unit 161 may be provided as a component of the common storage unit 140a or the second storage unit 140c.

[0388] Depending on the embodiment, the data stored in idiomatic expression store 161 may also be case-dependent.

[0389] The basic description storage unit 162 may store data on items constituting a patent specification, excluding the detailed description of the invention, the claims, and the brief description of drawings. Hereinafter, items constituting a patent specification, excluding the detailed description of the invention, the claims, and the brief description of drawings, are referred to as the "basic description." For example, the basic description may include the title of the invention, background art, the problem to be solved, the effects of the invention, a summary, and a means for solving the problem. However, the concept of the present invention is not limited thereto, and the items included in the basic description may be configured differently depending on the document format, the settings of the patent document preparation system 1, or the user's settings. The basic description storage unit 162 may also be configured as separate storage units for each detailed item included in the basic description.

[0390] The data stored in the basic description storage unit 162 is configured case-dependently, and the basic description storage unit 162 may store data entered into text input elements provided on the patent document creation screen to input basic items. The data stored in the basic description storage unit 162 may be updated in real time as a user enters or edits data using the text input elements on the patent document creation screen. The patent document creation screen includes one or more text input elements corresponding to each basic item, and the basic description storage unit 162 may store data by assigning an identification code corresponding to each text input element, thereby storing data in a manner that allows for distinction by each item.

[0391] The detailed description storage unit 163 may store the contents of items corresponding to the detailed description of the invention among the items constituting the patent specification. Hereinafter, the contents corresponding to the detailed description of the invention among the items constituting the patent specification will be referred to as the "detailed description." The data stored in the detailed description storage unit 163 may also be configured case-dependently, and the detailed description storage unit 163 may store data entered into text input elements provided on the patent document creation screen to enter the detailed description. The data stored in the detailed description storage unit 163 may be updated in real time as a user enters or edits data through the text input elements on the patent document creation screen. One or more text input elements corresponding to the detailed description may be provided on the patent document creation screen. If multiple text input elements are provided, the detailed description storage unit 163 may store the data by assigning an identification code corresponding to each text input element.

[0392] The claim storage unit 164 can store one or more claim data constituting the scope of a patent claim among the items constituting a patent specification. The claim data can include a claim number, a claim type, a cited claim number, an invention category, and a description of an element, and such data can be input using a claim number input element, a claim type input element, a cited claim input element, a category input element, an element description input element, etc., included in the claim creation screen.

[0393] The data stored in the claim storage unit 164 is configured case-dependently, and the claim storage unit 164 may store data entered into each input element provided on the claim creation screen. The data stored in the claim storage unit 164 may be updated in real time as the user enters or edits data through each input element on the claim creation screen. The claim storage unit 164 may store data by assigning an identification code corresponding to each input element, and may store data separately for each claim.

[0394] The component description storage unit 165 may store component descriptions managed by the component description input processing unit 123. The component descriptions may be configured with a plurality of preset themes. For example, the preset themes may include a definition of the component, an organic relationship with other components, a function of the component, an action of the component, an effect of the component, and a specific example of the component. Such data may be input using a text input element provided on the component description creation screen, and the data stored in the component description storage unit 165 may be managed by the component description creation screen. In addition, the component description storage unit 165 may also store a description of the component generated by the component description input processing unit 123 or input via the component description creation screen.

[0395] The data stored in the element description storage unit 165 is configured case-dependently, and the element description storage unit 165 may store data input into each text input element provided on the element description creation screen. The data stored in the element description storage unit 165 may be updated in real time as a user inputs or edits data into each text input element on the element description creation screen. The element description storage unit 165 may store data by assigning an identification code corresponding to each text input element, and may store data separately for each element. In this case, information about the element stored in the element description storage unit 165 may correspond to information stored by the element information storage unit 143.

[0396] The drawing brief description storage unit 166 may store data constituting the drawing brief description among the items constituting the patent specification. Since the drawing brief description creation screen may be provided with a drawing number text input element and a drawing description text input element on a drawing information input unit basis, the data stored in the drawing brief description storage unit 166 may also be formed on a drawing basis or a drawing information input unit basis. In addition, the drawing brief description storage unit 166 may also store completed text information generated based on the data input into the drawing number text input element and the drawing description text input element.

[0397] The data stored in the drawing description storage unit 166 is configured case-dependently, and the drawing description storage unit 166 may store data entered into each text input element provided on the drawing description creation screen. The data stored in the drawing description storage unit 166 may be updated in real time as the user enters or edits data through each text input element on the drawing description creation screen. The drawing description storage unit 166 may store data by assigning an identification code corresponding to each text input element, and may store data separately for each drawing or for each drawing information input unit.

[0398] The second storage unit 140c may include one or more of a first original text storage unit 171, a first translation text storage unit 172, a second original text storage unit 173, a second translation text storage unit 174, and a translation vocabulary book storage unit 175.

[0399] The first original text storage unit 171 stores original text data generated by the original text data management unit 131, and the first translation storage unit 172 may store translation data input as a translation of the original text data via the patent document creation screen. The data stored in the first original text storage unit 171 and the first translation storage unit 172 is configured case-dependently, and the first original text storage unit 171 and the first translation storage unit 172 may store original text data and translation data in translation units. For example, the first original text storage unit 171 and the first translation storage unit 172 may store data in sentence units, and may store unique identification values ​​assigned to each sentence together with the original text data.

[0400] The data stored in the first original text storage unit 171 and the first translation storage unit 172 may be updated in real time as the user inputs or edits data using the respective text input elements on the patent document creation screen. Specifically, the patent document creation screen may provide text input elements for original text data in translation units and may include text input elements into which corresponding translation data may be input. The first original text storage unit 171 and the first translation storage unit 172 may store the above-mentioned identification value along with the data input into each corresponding pair of text input elements.

[0401] Meanwhile, in this embodiment, an example will be described in which both the first original text storage unit 171 and the first translation text storage unit 172 are provided to the database 140, but the idea of ​​the present invention is not limited to this. For example, the original text data and the translation data may be stored in the database 240 of the patent document preparation server 20, or may be provided separately in the database 140 of the patent document preparation device 10 and the database 240 of the patent document preparation server 20.

[0402] The second original storage unit 173 may store original data of other patent documents that can be used as translation examples, and the second translation storage unit 174 may store corresponding translation data of other patent documents. The data stored in the second original storage unit 173 and the second translation storage unit 174 may be generated by using a patent document actually filed in a second language as original data and a patent document translated into a first language and filed as translation data. The second original storage unit 173 and the second translation storage unit 174 may share key values ​​to match corresponding original data and translation data. One or more of the second original storage unit 173 and the second translation storage unit 174 may store information on the source of the data, such as information on patent documents filed in a second language and information on patent documents filed in a first language. The patent document information may include the application number, publication number, registration number, applicant, language used, country of filing, or whether or not an international application has been filed.

[0403] The second original text storage unit 173 and the second translation text storage unit 174, like the first original text storage unit 171 and the first translation text storage unit 172, can store original text data and translation data in translation units, and as described above, key values ​​can be set to match each original text data and translation data.

[0404] Meanwhile, the second original text storage unit 173 and the second translated text storage unit 174 may further include separate tables for processing and storing the original text data and the translated data so that the original text data and the translated data can be quickly referenced. For example, the second original text storage unit 173 and the second translated text storage unit 174 may include original text data divided into sentences and an inverted index table generated based on the translated data.

[0405] In addition, the second original text storage unit 173 and the second translated text storage unit 174 can also store the embedding vectors described above together with the original text data and the translated data, so that similarity comparisons between the respective original text data and translated data can be performed quickly.

[0406] On the other hand, the second original text storage unit 173 and the second translated text storage unit 174 may be provided in the database 240 of the patent document creation server 20 rather than in the database 140, or may be provided separately in the database 140 of the patent document creation device 10 and the database 240 of the patent document creation server 20.

[0407] The translation vocabulary book storage unit 175 may store translation vocabulary book data that allows a user to refer to translation examples for words or specific expressions, like a dictionary, when translating. The translation vocabulary book data may be configured to enable matching between languages ​​supported by the patent document preparation application, and source data and translation data may be matched and stored in a single table. For example, if the patent document preparation application supports services for Korean, English, Japanese, and Chinese, the translation vocabulary books may be configured to support Korean-English, Korean-Japanese, Korean-Chinese, English-Japanese, English-Chinese, and Japanese-Chinese, respectively. The patent document preparation screen may include a vocabulary book management screen that allows a user or administrator to add new words or modify existing words, thereby managing the data stored in the translation vocabulary book storage unit 175. In this case, the vocabulary book management screen may provide a function that allows a user to upload large amounts of translation data as data in the translation vocabulary book storage unit 175.

[0408] In this embodiment, the components of the database 140 are described as being included in the common storage unit 140a, the first storage unit 140b, and the second storage unit 140c, but the concept of the present invention is not limited thereto. For example, a component included in the common storage unit 140a may be included in the first storage unit 140b or the second storage unit 140c, and a component included in the first storage unit 140b or the second storage unit 140c may be included in the common storage unit 140a, depending on the embodiment. Furthermore, a component included in the first storage unit 140b or the second storage unit 140c may be included in the second storage unit 140c or the first storage unit 140b, depending on the embodiment. Furthermore, any component may be understood to be simultaneously included in two or more of the common storage unit 140a, the first storage unit 140b, and the second storage unit 140c.

[0409] Furthermore, the components of database 140 described above are provided as examples. The components included in database 140 may be physically and logically separated from each other as components of memory 14 or integrated and realized as new components. In this case, a new component that performs the same function as any component of database 140 may be understood to correspond to any of the components.

[0410] Meanwhile, the data stored by the components of the database 140 of the patent document production device 10 may be stored in the database 240 of the patent document production server 20. Specifically, the database 240 of the patent document production server 20 may include a common storage unit 240a, a first storage unit 240b, and a second storage unit 240c that may correspond to the common storage unit 140a, the first storage unit 140b, and the second storage unit 140c of the patent document production device 10, respectively, and the common storage unit 240a, the first storage unit 240b, and the second storage unit 240c of the patent document production server 20 may have technical features corresponding to the common storage unit 140a, the first storage unit 140b, and the second storage unit 140c of the patent document production device 10.

[0411] Specifically, the common storage unit 240a of the patent document creation server 20 may include one or more of the screen configuration information storage unit 241, case information storage unit 242, component information storage unit 243, auto-completion dataset storage unit 244, drawing storage unit 145, description requirement storage unit 146, setting storage unit 247, external service information storage unit 148, user information storage unit 249, and change content storage unit 250, which may correspond to the screen configuration information storage unit 141, case information storage unit 142, component information storage unit 143, auto-completion dataset storage unit 144, drawing storage unit 145, description requirement storage unit 146, setting storage unit 247, external service information storage unit 148, user information storage unit 149, and change content storage unit 150, respectively, of the patent document creation device 10. In addition, the first storage unit 240b of the patent document creation server 20 may include one or more of the idiomatic expression storage unit 261, the basic description storage unit 262, the detailed description storage unit 163, the claim storage unit 164, the element description storage unit 165, and the brief description storage unit of the drawings 266, which may correspond to the idiomatic expression storage unit 161, the basic description storage unit 162, the detailed description storage unit 163, the claim storage unit 164, the element description storage unit 165, and the brief description storage unit of the drawings 166, respectively, of the patent document creation device 10. In addition, the second storage unit 240c of the patent document creation server 20 may include one or more of the first original text storage unit 271, the first translated text storage unit 272, the second original text storage unit 273, the second translated text storage unit 274, and the translation vocabulary book storage unit 275, which may correspond to the first original text storage unit 171, the first translated text storage unit 172, the second original text storage unit 173, the second translated text storage unit 174, and the translation vocabulary book storage unit 175 of the patent document creation device 10, respectively.

[0412] Corresponding components of database 140 of the patent document production device 10 and database 240 of the patent document production server 20 may be provided in both database 140 of the patent document production device 10 and database 240 of the patent document production server 20, or may be selectively provided in either database 140 of the patent document production device 10 or database 240 of the patent document production server 20. When a component is provided in both database 140 of the patent document production device 10 and database 240 of the patent document production server 20, the data stored in the component may be synchronized with each other. That is, when one piece of data is changed, the corresponding other piece of data may also be changed. This synchronization function may be performed by a component of processor 100 of the patent document production device 10 or processor 200 of the patent document production server 20 that manages the corresponding storage location. Furthermore, depending on the embodiment, some data may be stored in a component of database 140 of the patent document production device 10, and other data may be stored in a corresponding component of database 240 of the patent document production server 20. For example, among idiomatic expressions, idiomatic terms used to generate an auto-complete list may be stored and managed in database 140 of the patent document creation device 10, and idiomatic phrases may be stored and managed in database 240 of the patent document creation server 20.

[0413] Furthermore, a certain component may be provided only to the database 140 of the patent document production device 10 or only to the database 240 of the patent document production server 20. In this case, the component may store data independently. For example, data related to a document currently being translated may be stored in the database 140 of the patent document production device 10, and translation examples of other documents that have already been translated may be stored in the database 240 of the patent document production server 20. Note that storing data independently may be understood to mean that data is stored in a component provided only to either the database 140 of the patent document production device 10 or the database 240 of the patent document production server 20, and that the data is not shared with other devices via the network 30.

[0414] In this embodiment, each function of the patent document creation application for creating a patent document may be executed by either the patent document creation device 10 or the patent document creation server 20, or may be executed simultaneously by the patent document creation device 10 and the patent document creation server 20, or may be executed in cooperation with the patent document creation device 10 and the patent document creation server 20, depending on the specific embodiment. In other words, for the operation of the patent document creation application in the patent document creation device 10, each component that may be included in the patent document creation device 10 and the patent document creation server 20 described above may be appropriately selected or combined for use. The combination of components may be changed depending on the program type of the patent document creation application and the services provided by the patent document creation application.

[0415] For example, the patent document drafting device 10 and the patent document drafting server 20 may be configured so that confidentiality-required patent document content is not transmitted from the patent document drafting device 10 to the patent document drafting server 20 via the network 30 but is instead processed internally within the patent document drafting device 10. This eliminates security risks associated with transmitting confidentiality-required patent document content via the network 30. The confidentiality-required patent document content may include one or more of the following: the title of the invention, the technical field, the background art, related literature information, the problem to be solved, the means for solving the problem, the abstract, the effects of the invention, the detailed description of the invention, the claims, a brief description of the drawings, and drawings. Such data may be considered case-dependent. In this regard, data that can be prepared and used in advance as case-independent content, such as idiomatic expressions and inserted strings, may be considered to be excluded from the confidentiality-required patent document content. Hereinafter, such confidentiality-required patent document content may be referred to as "security data."

[0416] Specifically, in this embodiment, the security data is stored in the element information storage unit 143, the auto-completion data set storage unit 144, the drawing storage unit 145, the change content storage unit 150, the idiomatic expression storage unit 161, the basic description storage unit 162, the detailed description storage unit 163, the claim storage unit 164, the element description storage unit 165, the brief description of the drawings storage unit 166, the first original text storage unit 171, and the first translation storage unit 172 of the database 140. The element management unit 104 manages the security data, and the auto-completion list generator 105 manages the security data. The description unit 105, text input element management unit 106, drawing management unit 107, description requirement review unit 108, download file generation unit 109, change content management unit 114, idiomatic expression management unit 121, claim input processing unit 122, component description input processing unit 123, brief drawing description input processing unit 124, original data management unit 131, component extraction unit 132, component display switching unit 133, and first translation example search unit 134 are provided to the processor 100 and will be explained as an example, operating on the patent document creation device 10 side.

[0417] However, this embodiment should not be understood to exclude corresponding components that may be provided to the patent document creation server 20. In this embodiment, too, the patent document creation application may transmit data from the patent document creation device 10 to the patent document creation server 20 and store it, or transmit data from the patent document creation device 10 to the patent document creation server 20 and then receive the processed results, based on a user request and settings. For this purpose, the patent document creation server 20 may be provided with components corresponding to the components provided to the patent document creation device 10. In addition, some of the idiomatic expression data that may be included as part of the security data but that may be managed by the auto-completion list generation unit 105, the idiomatic expression management unit 121, etc. may be transmitted from the patent document creation server 20, and the transmitted data may be managed by the auto-completion dataset storage unit 144 and the idiomatic expression storage unit 161 of the patent document creation device 10.

[0418] Furthermore, in this embodiment, data other than security data (hereinafter referred to as "non-security data"), such as screen configuration information, case information, and various setting values, may be stored in the database 240 of the patent document creation server 20, and therefore the patent document creation device 10 and corresponding components provided in the patent document creation server 20 are described as interoperating with each other. Similarly, this embodiment should not be understood to exclude corresponding components that may be provided in the patent document creation device 10. In this embodiment, the patent document creation application may also store and utilize a portion of the data stored in the patent document creation server 20 in the patent document creation device 10 for faster processing. For example, data such as case information and description requirements can be stored and managed in the case information storage unit 242 and description requirements storage unit 246 provided to the patent document creation server 20, and the patent document creation application can receive this information from the patent document creation server 20 and store it in the case information storage unit 142 and description requirements storage unit 146 for use.When data on the patent document creation server 20 is updated, the patent document creation application can update the data stored in the case information storage unit 142 and description requirements storage unit 146 to correspond to the updated data and use it.

[0419] In this embodiment, more specific details regarding the operation of each component of the patent document creation device 10 and the patent document creation server 20 for processing and managing security data and processing and managing non-security data will be described later with reference to a drawing showing the screen of the patent document creation application.

[0420] The combinations of the above elements are presented as examples and may have technical meaning in the present embodiment, but do not limit the spirit of the present invention.

[0421] Furthermore, since the present embodiment describes an example in which the patent document drafting application is provided as a web application, the components of the patent document drafting device 10 and the patent document drafting server 20 can be understood to operate based on the cooperation of a web browser or other web-browsing application and a web server program. Therefore, the corresponding components of the patent document drafting device 10 and the patent document drafting server 20 can be understood to be provided separately as the application of the patent document drafting device 10 and the server program of the patent document drafting server 20. Furthermore, the corresponding components of the patent document drafting device 10 and the patent document drafting server 20 can be understood as a single component. When the corresponding components of the patent document drafting device 10 and the patent document drafting server 20 are understood as a single component, they can also be understood as components of the patent document drafting system 1. This understanding of the components can be commonly applied when the patent document drafting application operates in a client-server application program mode.

[0422] In another aspect, the patent document drafting application of the patent document drafting device 10 can be understood as loading one or more web pages that can realize any of the components of the patent document drafting system 1 stored on the patent document drafting server 20. Depending on the content of the loaded web page and the processing modules assigned to that web page by the web server program, some functions may be executed by the patent document drafting device 10 and other functions may be executed by the patent document drafting server 20. In this case, the physical and logical modules that execute the functions assigned to the patent document drafting device 10 may be understood as the components on the patent document drafting device 10 side of the components, and the physical and logical modules that execute the functions assigned to the patent document drafting server 20 may be understood as the components on the patent document drafting server 20 side of the components.

[0423] In another aspect, the components of the patent document creation device 10 can be understood as physical and logical modules of the front-end stage that operate based on web pages transmitted from the patent document creation server 20 to a web browsing-enabled application, and the components of the patent document creation server 20 can be understood as physical and logical modules of the back-end stage that can operate on the web server program side based on data transmitted from the patent document creation device 10 and data stored in the database 240.

[0424] As described above, in this embodiment, the patent document preparation application is described as a web application. Therefore, the components of the patent document preparation device 10 and the patent document preparation server 20 are described as being implemented as a web application. However, the concept of the present invention is not limited to this. For example, the patent document preparation application may be run by the patent document preparation device 10, but may also be a client-server application program capable of data communication with the patent document preparation server 20. In this case, the components of the patent document preparation device 10 and the patent document preparation server 20 may be modified accordingly. For example, components described as configuring a web page or using a database built into a web browser may be understood as configuring the screen of an independently run form-based application, or as such a program accessing an independently provided database and performing data processing. As another example, the patent document preparation application may be a program installed as an extension program for other software and dependently run by that other software. As a specific example, the patent document preparation application may be an add-in program for Word. As another example, the patent document creation application may be a program installed in the patent document creation device 10 that operates in a stand-alone manner. In this case, all components of the patent document creation server 20 may be omitted, and the patent document creation application may be driven only by the components provided in the patent document creation device 10.

[0425] The following describes in detail the patent document drafting device, method, computer program, computer-readable recording medium, server, and system according to the present embodiment, with reference to screens provided by the patent document drafting application to provide the first and second services. As described above, in this embodiment, the patent document drafting application is provided as a web application, and therefore the screens described below can be understood as being output on the screen of a web browser via the display device of the input / output interface 19.

[0426] Furthermore, the screens described below may have their structure and content configured by the screen configuration unit 101 and output to a web browser. To this end, the screen configuration unit 101 may load a web page provided by the patent document creation server 20 and then configure the screen structure and content according to the content of the loaded web page. In this case, the web page provided from the patent document creation server 20 to the patent document creation device 10 may be configured in advance by the screen con...

Claims

1. a screen configuration unit that provides a user with a claim creation screen via an input / output interface for creating claims included in the scope of claims provided as an item of the contents of the patent document; a component management unit that receives, via the input / output interface, information on components that constitute the invention as specific objects that can be included in the content of a patent document and that can be described in text, and manages the information on the components; a text input element management unit that manages element description input elements, which are provided on the claim creation screen and into which a user inputs descriptions and limitations relating to elements that constitute the invention as part of the content of the claim, extracts a part of the text input into the element description input element as an auto-completion keyword in response to a user input via the input / output interface, replaces the auto-completion keyword with an element item generated based on information about the element corresponding to the auto-completion keyword, and outputs the result to the element description input element; a claim input processing unit that manages data constituting a claim, such as a claim number, a claim type, a cited claim number, an invention category, and a description of an element input by the element description input element, input via the claim creation screen; A patent document preparation device including:

2. The claim creation screen includes: a claim number input element for inputting the claim number; a claim type input element for inputting the claim type; a cited claim input element for inputting the cited claim number; 2. The patent document drafting apparatus according to claim 1, further comprising a category input element for inputting a category of the invention.

3. The patent document creation device of claim 1, wherein the claim creation screen is provided with a cited claim input element that can display a cited claim selection screen having a UI (user interface) that allows the user to select a claim having a number earlier than the number of the claim being created as a cited claim.

4. The claim creation screen further provides a claim type input element for inputting the type of the claim, 4. The patent document drafting device according to claim 3, wherein the cited claim input element or the cited claim selection screen is activated when a dependent claim is input using the claim type input element.

5. The cited claim selection screen displays citable claims in a manner that allows the user to recognize the type of each claim, The patent document creation device of claim 3, wherein the cited claim selection screen includes an all-claims selection UI that can cite all claims having a claim number earlier than the number of the claim being created, and has a multiple selection function that can select multiple claims from the displayed claims.

6. 4. The patent document drafting device according to claim 3, wherein the claim input processing unit reviews the cited claims each time the user selects a claim number to be cited on the cited claim selection screen, and provides the review results to the user.

7. The patent document creation device of claim 3, wherein the claim input processing unit preliminarily examines claims that may have description deficiencies, and then does not display or deactivates the problematic claims on the cited claim selection screen so that the claims cannot be selected.

8. The patent document creation device of claim 3, wherein the claim input processing unit automatically generates and displays a claim citation phrase to be displayed on the claim creation screen according to the claim citation type when selection of a cited claim is completed on the cited claim selection screen.

9. the claim input processing unit classifies the claim citation type according to one or more of the number of claims, the method of citing claims, whether the cited claims have consecutive numbers, and whether the cited claims include a part with consecutive numbers; the claim input processing unit reads out a pre-stored idiomatic phrase according to the citation type of the claim to generate the claim citation; 9. The patent document drafting device according to claim 8, wherein the idiomatic phrase includes a portion representing a claim number as a replacement portion, and the claim input processing unit generates the claim citation by replacing the replacement portion with the corresponding claim number.

10. 10. The patent document drafting device according to claim 9, wherein the claim input processing unit outputs the claim citation to the cited claim input element.

11. The claim creation screen is provided with a category input element for inputting a category of the invention, The patent document creation device of claim 3, wherein the claim input processing unit sets the data of the category input element of the cited claim as category data of the selected claim when the user selects the claim to be cited on the cited claim selection screen.

12. The claim creation screen is provided with a claim type input element for inputting the type of the claim, and a category input element for inputting the category of the invention, 2. The patent document creation device according to claim 1, wherein the category input element is activated when an independent claim is selected as the type of the claim by the claim type input element, and the category input element is deactivated when a dependent claim is selected.

13. The claim creation screen is provided with a category input element for inputting a category of the invention, The patent document creation device according to claim 1, wherein when the category of one claim invention is changed by the category input element on the claim creation screen, the claim input processing unit changes the category data of other claim inventions that cite that claim.

14. 2. The patent document drafting device according to claim 1, wherein the screen construction unit further provides a claim display screen that displays the contents of one or more claims prepared on the claim preparation screen.

15. The claim display screen is provided with a claim creation screen calling UI that can call the claim creation screen, The patent document drafting device according to claim 14, wherein the display of the claim drafting screen can be switched on or off by operating the claim drafting screen calling UI.

16. The claim display screen is provided with a claim correction screen calling UI that can call a claim correction screen that can correct data of any one claim, 15. The patent document drafting device according to claim 14, wherein the claim correction screen is provided with data of the claim to be corrected set in each input element of the claim drafting screen.

17. By operating the claim creation screen calling UI, the claim creation screen is displayed adjacent to the claim display screen, The patent document creation device according to claim 15, wherein the content of the claim creation screen is set to the content of a claim selected by selecting a claim correction screen call UI for any one of the claims displayed on the claim display screen.

18. The screen configuration unit provides a drawing symbol display switching UI on the patent document creation screen, The patent document creation device of claim 1, wherein the inclusion state of an identification code, which is information about a component included in the component item input into the component description input element, is switched by operating the drawing symbol display switching UI.

19. 2. The patent document drafting device according to claim 1, wherein the claim input processing unit switches the inclusion state of the identification code in the automatically completed text displayed on the screen in response to a user's selection of whether or not to include the identification code.

20. the screen configuration unit provides a UI for inputting commands for adding, inserting, deleting, and moving claims on the patent document creation screen; 2. The patent document drafting device according to claim 1, wherein said claim input processing section rearranges claim numbers in response to commands to add, insert, delete or move claims, and changes data of other claims.

21. 2. The patent document creation device according to claim 1, wherein when the component item is replaced and input into the text input element, the claim input processing unit determines whether the component item to be replaced is already described in the cited claim and the claim being created, and if it is already described, adds a predicate before the component item to be replaced and outputs it.

22. The screen configuration unit provides a description requirement review result screen that outputs the results of reviewing description requirements stipulated in the Patent Act to the patent document creation screen, 2. The patent document drafting device according to claim 1, wherein the claim input processing unit outputs results of the claim antecedent review and the cited claim review to the description requirement review result screen.

23. The patent document creation device of claim 22, wherein the claim input processing unit performs the claim antecedent review and the cited claim review when the claim data is changed on the claim creation screen or when a claim is added, inserted, deleted, or moved, and outputs the results to the description requirement review result screen.

24. A patent document drafting method using a patent document drafting device that provides a user with a screen for drafting a patent document configured by a screen configuration unit via an input / output interface, comprising: a step in which the screen configuration unit provides a component management screen capable of managing information on components constituting an invention as specific objects that can be included in the content of a patent document and that can be described in text, and a claim creation screen that is a screen for creating claims included in the scope of claims provided as an item of the content of the patent document, and that includes a component description input element that is a text input element into which a user inputs descriptions and limitations on components constituting an invention as part of the content of the claim; receiving a command from a user to register, delete, or modify information about the component by the component management unit, and storing, deleting, or modifying the component information in the component information storage unit in response to the command; a text input element management unit receiving a description and a limitation of a component from a user through the component description input element in text form, extracting a part of the text input to the component description input element as an auto-completion keyword, and then replacing the extracted auto-completion keyword with a component item generated based on information of the component corresponding to the auto-completion keyword and outputting the result to the component description input element; a claim input processing unit managing, as data constituting the claim input via the claim creation screen, the claim number, the claim type, the cited claim number, the invention category, and the description and limitation regarding the element input via the element description input element; A method for preparing patent documents, including:

25. A computer-readable recording medium storing a computer program, 25. A computer readable recording medium storing a computer program comprising instructions for causing a processor to carry out the patent document drafting method of claim 24.

26. A computer program stored on a computer-readable recording medium, A computer program stored on a computer-readable recording medium containing instructions for performing the patent document drafting method of claim 24, when coupled to an apparatus including a memory for storing instructions and a processor for executing the instructions stored in the memory.

Images