Device For Processing Using Drawing File
Patent Information
- Authority / Receiving Office
- KR · KR
- Patent Type
- Applications
- Current Assignee / Owner
- LG ELECTRONICS INC
- Filing Date
- 2025-01-22
- Publication Date
- 2026-07-29
Smart Images

Figure PAT00006_ABST
Abstract
Description
Technology Field
[0001] The present invention relates to a device for processing user requests regarding a drawing file, and more specifically, to a device configured to detect user input related to the artist or creator of a drawing file, the time of creation or modification, or the main content thereof, and to search for a drawing file or process a searched drawing file according to the user input. Background Technology
[0003] Drawing apps refer to software or applications that allow users to draw and create in a digital environment. These apps are designed for professional artists, designers, beginners, or simply those who enjoy drawing as a hobby. Drawing apps provide various features and tools to help users unleash their creativity.
[0004] The drawing app provides a variety of brush and pen tools with diverse textures and effects, such as pencils, ink pens, markers, and watercolor brushes. Additionally, the app allows you to create multiple layers to independently modify or manage specific elements of your drawing. It offers an extensive color selection feature and customizable palettes, and allows you to zoom in, out, and rotate the canvas for detailed work. Furthermore, the app supports various filters to add textures or lighting effects to your drawings, and allows you to save your work in formats such as PNG, JPG, and PSD, or share it to other platforms.
[0005] This specification proposes a method to further enhance a drawing app to search for or process drawing results (i.e., drawing files) based on the user (painter or creator) and / or the time of creation (modification). The problem to be solved
[0007] The present invention proposes a device for searching or processing heterogeneous drawing files.
[0008] The problems to be solved by the present invention are not limited to the problems to be solved above, and other problems not mentioned will be clearly understood by those skilled in the art to which the present invention belongs from the description below. means of solving the problem
[0010] According to one embodiment of the present invention, a device configured to process a user request for a drawing result is proposed, wherein the device includes: a memory configured to detect a user request for a drawing result input through a human-machine interface and to store code configured to process the user request; and a processor configured to execute the code for an operation to process the user request, wherein the operation includes determining a user request keyword corresponding to the user request, performing processing on a previously stored drawing result according to the determined user request keyword, and outputting the processed result to a display, wherein the user request keyword may include metadata for the drawing result and a type of the user request.
[0011] Additionally or alternatively, the metadata may include at least one of the creator of the drawing result, the time of creation or modification, or keywords regarding the drawing result.
[0012] Additionally or alternatively, the type of the above user request may include any one of a search request for a drawing result, a drawing event request using a drawing result, or a system configuration request using a drawing result.
[0013] Additionally or alternatively, the operation may include outputting a user interface component for entering keywords to search for the drawing result on the display, depending on whether the user's request is a search request for the drawing result.
[0014] Additionally or alternatively, the operation may include detecting a drawing result corresponding to the metadata as the determined user request keyword corresponds to a search request for a drawing result, and outputting at least one of the detected drawing results to the display.
[0015] Additionally or alternatively, the operation may include detecting a drawing result corresponding to the metadata as the determined user request keyword corresponds to a drawing event request using a drawing result, and outputting a result of processing a drawing event using any one of the detected drawing results to the display.
[0016] Additionally or alternatively, the operation may include detecting a drawing result corresponding to the metadata as the determined user request keyword corresponds to a system configuration request using a drawing result, and executing a system configuration using any one of the detected drawing results.
[0017] Additionally or alternatively, the metadata may include a voice ID or face ID for the creator of the drawing result.
[0018] Additionally or alternatively, the metadata may include information indicating the relationship between the creator of the drawing result and other creators.
[0019] Additionally or alternatively, the operation includes generating metadata for the drawing result and storing it together with the drawing result whenever the drawing result is generated or saved, and the metadata may include at least one of the creator of the drawing result, the time of creation or modification, or keywords regarding the drawing result.
[0020] The above-mentioned problem-solving methods are merely some of the embodiments of the present invention, and various embodiments reflecting the technical features of the present invention can be derived and understood by those skilled in the art based on the detailed description of the present invention to be described below. Effects of the invention
[0021] The present invention has the following effects.
[0022] The present invention enables users to easily and quickly search for drawing files.
[0023] Furthermore, the present invention does not stop at merely serving as a drawing tool, but enables the drawn result to be utilized in various ways.
[0024] The effects obtainable from the present invention are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art from the description below. Brief explanation of the drawing
[0025] The accompanying drawings, which are included as part of the detailed description to aid in understanding the present invention, provide embodiments of the present invention and explain the technical concept of the present invention together with the detailed description. FIGS. 1 and 2 illustrate a drawing result (file) of a user (painter or creator) and related drawing metadata according to the present invention. FIG. 3 is a figure for explaining the drawing result (file) search function according to the present invention. FIG. 4 shows a flowchart of a method for searching or processing drawing results according to the present invention. FIG. 5 is a diagram illustrating the function of creating or editing a drawing result using a previously generated drawing result (file) according to the present invention. FIG. 6 illustrates a block diagram of a device for searching or processing drawing results according to the present invention. Specific details for implementing the invention
[0026] Hereinafter, embodiments disclosed in this specification will be described in detail with reference to the attached drawings. Identical or similar components regardless of drawing symbols will be assigned the same reference number, and redundant descriptions thereof will be omitted. The suffixes "module" and "part" used for components in the following description are assigned or used interchangeably solely for the ease of drafting the specification and do not inherently possess distinct meanings or roles. Furthermore, in describing embodiments disclosed in this specification, if it is determined that a detailed description of related prior art could obscure the essence of the embodiments disclosed in this specification, such detailed description will be omitted. Additionally, the attached drawings are intended only to facilitate understanding of the embodiments disclosed in this specification; the technical concept disclosed in this specification is not limited by the attached drawings, and it should be understood that they include all modifications, equivalents, and substitutions that fall within the spirit and technical scope of the present invention.
[0027] Terms including ordinal numbers, such as first, second, etc., may be used to describe various components, but said components are not limited by said terms. These terms are used solely for the purpose of distinguishing one component from another.
[0028] When it is stated that one component is "connected" or "connected" to another component, it should be understood that while it may be directly connected or connected to that other component, there may also be other components in between. On the other hand, when it is stated that one component is "directly connected" or "directly connected" to another component, it should be understood that there are no other components in between.
[0029] A singular expression includes a plural expression unless the context clearly indicates otherwise.
[0030] In this application, terms such as “comprising” or “having” are intended to specify the existence of the features, numbers, steps, actions, components, parts, or combinations thereof described in the specification, and should be understood as not precluding the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.
[0031] In this specification, the term "drawing file or result" means a file or result created by a drawing app or service.
[0033] FIGS. 1 and 2 illustrate a drawing result (file) of a user (painter or creator) and related drawing metadata according to the present invention.
[0034] FIG. 1(a) and FIG. 2(a) illustrate a scene in which a user (1, 2) performs a drawing event (e.g., drawing, modifying, deleting, etc.) through a drawing app or a user interface (1000, 1100) of a drawing app. The drawing app or a user interface (1000, 1100) of a drawing app is configured to be displayed on a screen.
[0035] When the drawing event of the user (1, 2) is completed, the drawing result (file) can be saved to a storage medium of the device or a cloud server, etc. When the drawing result (file) is saved, drawing metadata is proposed as information to be saved together.
[0036] FIG. 1(b) and FIG. 2(b) illustrate a user interface (2000, 2100) that displays a thumbnail of a drawing file stored in a storage medium of a user device or a storage such as a cloud server.
[0037] FIG. 1(b) and FIG. 2(b) store drawing metadata (hereinafter simply referred to as “metadata”) in a JSON format file, and, for example, the creator, the creator’s face ID, the creation style (also known as “art style”), the date of creation, the creator’s age, and keywords related to the drawing result are presented. The metadata according to the present invention may include at least one of these or other information.
[0038] According to FIG. 1(b) and FIG. 2(b), the creator (i.e., the user) must be identified. To this end, the device according to the present invention may be equipped with means for identifying the creator. For example, the creator may be identified through facial recognition by being equipped with a camera.
[0039] As another example, the creator can be identified based on the creative style of the drawing result. However, creator identification based on creative style may be possible when saving or modifying metadata for a newly saved or modified drawing result while creator information for a previously saved drawing result is already stored.
[0040] As another example, when an app or service for drawing is started or is in operation, a user account is required, and the creator can be identified based on user information entered by the user.
[0041] As another example, when an app or service for drawing is started or in operation, the user's voice utterance is requested, and the creator can be identified through the voice recognition results.
[0042] For example, metadata for drawing results can be generated and structured as follows.
[0043] Creator Information User ID (Voice ID, Face ID) Creative Style ID Creation time information Creation date Save date correction Creator's age Creative Work Content Information Main Keywords
[0044] Here, the creator's age can be set based on the creation date of the drawing result.
[0046] FIG. 3 is a figure for explaining the drawing result (file) search function according to the present invention.
[0047] As illustrated in FIG. 1 (a) and FIG. 2 (b), if metadata for a drawing result is generated and stored together with the drawing result, searching using the metadata can be supported.
[0048] When a user's touch input selection input for a user interface component (2200-1) of the drawing app's user interface (2200) is detected, a user interface component (2200-2) for search keyword input can be output as illustrated.
[0049] The user interface component (2200-2) is illustrated as being capable of inputting or selecting a creator, a save date, and keywords, but the invention is not limited thereto.
[0051] FIG. 4 shows a flowchart of a method for searching or processing drawing results according to the present invention. The method according to the present invention may be performed by a user device (10) and may be performed by a processor of the user device (10). The user device (10) will be described later with reference to FIG. 6. Hereinafter, the user device (10) will be described as performing the method of FIG. 6.
[0052] The user device (10) can detect a user request (S410). The user request can be input via the user's voice input. That is, S410 can be performed by detecting the user uttering a request for a drawing result. However, the user's voice input is merely an example, and various user inputs can be provided as inputs for user requests.
[0053] In FIG. 4, three types of user requests are shown to be supported, but the present invention is not limited thereto. The user requests shown in FIG. 4 may include any one of a search request for a drawing file, a drawing event request using a drawing file, or a system configuration request using a drawing file.
[0054] The user device (10) can check whether the user request is a drawing file search request (S420).
[0055] If the user request is a drawing file search request, the user device (10) can determine a search request keyword from the user request (S421). In this specification, the search request keyword may include metadata for the drawing file and the type of the user request.
[0056] The user device (10) extracts or determines search request keywords from a user request, and may extract keywords belonging to the category of metadata of the drawing file described above. Additionally, the user device (10) may extract the type of the user request as a search request keyword.
[0057] For example, a user request such as “find the drawing that User A drew last year” may be input, and in this case, the user device (10) may determine ‘User A’ and ‘last year (=2024)’ as search request keywords. Additionally, the user device (10) may extract ‘find it’ and thereby determine that the type of the user request is a ‘search request’.
[0058] The user device (10) can search for previously stored drawing files using a determined search request keyword (S422). Since metadata such as Table 1 is generated for each drawing file on the storage medium or cloud server of the user device (10), the user device (10) can find drawing files that have metadata corresponding to the search request keyword.
[0059] The user device (10) can output a list of drawing files corresponding to the search request keyword (S423).
[0060] Meanwhile, if there is no drawing file corresponding to the search request keyword, the user device (10) may select a drawing file having metadata closest to the search request keyword and provide it as a search result. At this time, the user device (10) may provide a user interface to confirm whether the user will use the selected drawing file.
[0062] If the user request is not a drawing file search request, the user device (10) can check whether the user request is a drawing event request (S430).
[0063] If the user request is a drawing event request, the user device (10) can determine a drawing event request keyword from the user request (S421). In this specification, the drawing event request keyword may include metadata for a drawing file and the type of the user request.
[0064] The user device (10) extracts or determines a drawing event request keyword from a user request, and can extract a keyword belonging to the category of metadata of the drawing file described above. In addition, the user device (10) can extract the type of the user request as a drawing event request keyword.
[0065] For example, a user request such as “find the rabbit drawing that User A drew last year and draw User A as if standing next to the rabbit” may be input, and in this case, the user device (10) can determine ‘User A’, ‘last year (=2024)’, and ‘rabbit’ as keywords for the drawing event request. Additionally, the user device (10) can extract ‘draw User A as if standing next to the rabbit’ as a user request and determine that the type of the user request is a ‘drawing event request’.
[0066] The user device (10) can search for previously stored drawing files using a determined drawing event request keyword. Since metadata such as Table 1 is generated for each drawing file on the storage medium or cloud server of the user device (10), the user device (10) can find a drawing file having metadata corresponding to the drawing event request keyword.
[0067] Then, the user device (10) can process drawing events according to a determined drawing event request keyword for the found drawing file (S432). For example, from a user request, 'Draw User A as if next to a rabbit,' the user device (10) can extract a drawing event of 'drawing' or 'modifying' (adding to the canvas of an image file), and accordingly, can add a previously saved image for User A to a previously saved drawing file (rabbit drawing).
[0068] The user device (10) can output a drawing result corresponding to a drawing event request keyword (S433).
[0069] Meanwhile, if there are multiple drawing files corresponding to the drawing event request keyword, the user device (10) can select one of them or provide a user interface to the user to select one of the multiple drawing files.
[0070] If there is no drawing file corresponding to the drawing event request keyword, the user device (10) may select a drawing file having metadata closest to the request keyword. At this time, the user device (10) may provide a user interface to confirm whether the user will use the selected drawing file.
[0071] In addition, one saved image for User A may be set in advance, but a user interface may be provided to the user to select one of multiple images for User A.
[0073] If the user request is not a drawing event request, the user device (10) can check whether the user request is a system setting related request (S440).
[0074] If the user request is a request related to system settings, the user device (10) can determine a request keyword related to system settings from the user request (S441). In this specification, the request keyword related to system settings may include metadata for a drawing file and the type of the user request.
[0075] The user device (10) extracts or determines request keywords related to system settings from a user request, and can extract keywords belonging to the category of metadata of the drawing file described above. In addition, the user device (10) can extract the type of the user request as a request keyword related to system settings.
[0076] For example, a user request such as “Set the rabbit drawing that User A drew last year as the wallpaper” may be input, and in this case, the user device (10) may determine ‘User A’, ‘last year (=2024)’, and ‘rabbit’ as system setting related request keywords. Additionally, the user device (10) may extract ‘set as wallpaper’ as a user request and determine that the type of the user request is a ‘system setting related request’.
[0077] The user device (10) can search for previously stored drawing files using a request keyword related to a determined system setting.
[0078] Since metadata such as Table 1 is generated for each drawing file on the storage medium or cloud server of the user device (10), the user device (10) can find a drawing file having metadata corresponding to a request keyword related to system settings.
[0079] Then, the user device (10) can execute system settings according to the system setting related request keywords determined for the found drawing file (S442).
[0080] As such, the present invention can search for or edit a previously stored drawing file (execute a drawing event) in response to a user request, or execute system settings using a previously stored drawing file. This has the effect of expanding the scope of user request processing of the drawing app and providing more diverse drawing app functions.
[0082] FIG. 5 is a diagram illustrating the function of creating or editing a drawing result using a previously generated drawing result (file) according to the present invention.
[0083] According to the present invention, a user device can search for a drawing result using metadata of the drawing result and output the searched drawing result on a canvas. Additionally, the user device can perform a drawing event to output another drawing result or image, etc., of the user on the canvas together with other drawing results.
[0084] The drawing app or user interface (1200) of the drawing app illustrated in FIG. 5 can output a previously stored drawing file (a) and a user image (b) on a single canvas. This represents the processing result when the user request mentioned earlier, “Find the rabbit drawing that User A drew last year and draw User A as if he is next to the rabbit,” is input.
[0086] Meanwhile, it is obvious that the order of S420, S430, and S440 described above may be performed in a different order than that illustrated. Furthermore, the identification of user requests (S420, S430, S440) and the determination of keywords for search requests, drawing event requests, and system setting-related requests (S421, S431, S441) may also be performed in a different order than illustrated, that is, by swapping the order of each other (i.e., swapping the order of S420 and S421).
[0088] In addition, user requests may include information indicating the relationships between creators, in addition to user information corresponding to the 'creator information' in Table 1. For example, a user request may be entered as “Find the drawing my dad drew.” To support processing for this, the metadata of the drawing file proposed in this specification may be modified as follows.
[0089] Creator Information User ID (Voice ID, Face ID) Creative Style ID Creation time information Creation date Save date correction Creator's age Creative Work Content Information Main Keywords Creator Relationship Information Relationship Information Official ID
[0090] 'Relationship Information' represents the relationship information of the creator associated with the drawing file, and can correspond, for example, to information regarding family relationships (father, mother, husband, wife, etc.). 'Relationship ID' can represent the user ID of the creator information corresponding to that relationship. For example, if the creators indicated by ID A and ID B are in a father-daughter relationship, ID B may be stored as the relationship information 'Father' in the creator relationship information within the metadata where ID A is included as creator information.
[0091] Through this metadata, user requests containing information on relationships between creators can be processed. This has the effect of expanding the drawing app's user request processing and providing a wider range of drawing app features.
[0093] FIG. 6 illustrates a block diagram of a device for searching or processing drawing results according to the present invention.
[0094] A device (10) configured to perform a search or processing of drawing results may be configured to include a memory (100) and a processor (101).
[0095] The memory (100) may be configured to detect a user request for a drawing result input through a human-machine interface and to store code configured to process the user request.
[0096] The processor (101) may be configured to execute the code for an operation to process a user request. More specifically, the processor (101) may be configured to determine a user request keyword corresponding to the user request, perform processing on a previously stored drawing result according to the determined user request keyword, and output the processed result to a display.
[0097] Here, the user request keyword may include metadata for the drawing result and the type of the user request. The metadata may include at least one of the creator of the drawing result, the time of creation or modification, or keywords regarding the drawing result. The type of the user request may include any one of a search request for the drawing result, a drawing event request using the drawing result, or a system configuration request using the drawing result.
[0098] The processor (101) may be configured to output a user interface component for inputting keywords to search for drawing results on a display, depending on whether the user request is a search request for drawing results.
[0099] The processor (101) may be configured to detect a drawing result corresponding to metadata as the determined user request keyword corresponds to a search request for a drawing result, and to output at least one of the detected drawing results to a display.
[0100] The processor (101) may be configured to detect a drawing result corresponding to metadata as the determined user request keyword corresponds to a drawing event request using a drawing result, and to output to the display a result of processing a drawing event using one of the detected drawing results.
[0101] The processor (101) may be configured to detect a drawing result corresponding to metadata as the determined user request keyword corresponds to a system setting request using a drawing result, and to execute a system setting using any one of the detected drawing results.
[0102] Additionally, the metadata may include a voice ID or a face ID for the creator of the drawing result. The voice ID may be used for user identification when the user request is input via voice. Additionally, the face ID may be used for user identification when the user device (10) includes a camera or when the user device (10) is connected to a camera.
[0103] Additionally, metadata may include information indicating the relationship between the creator of the drawing result and other creators.
[0104] Additionally, the processor (101) may be configured to generate metadata for the drawing result and store it together with the drawing result whenever the drawing result is generated or stored. In this case, the metadata may include at least one of the creator of the drawing result, the time of creation or modification, or keywords for the drawing result.
[0105] A device (10) configured to perform drawing result retrieval or processing may be configured to additionally include a human-machine interface (HMI) (102).
[0106] The human-machine interface (HMI) (102) includes means to provide visual or auditory notifications to a user or administrator, and may include, for example, a display. A user interface may be output to the HMI (102).
[0107] As such, the present invention can provide processing of user requests linked to drawing results, thereby expanding the scope of application of drawing apps or services.
[0109] Even if not described with reference to FIG. 6, a device (10) configured to process a user request for a drawing result of the present invention may perform the operation according to the present invention as described above in FIG. 1 to FIG. 5.
[0111] In addition, as another aspect of the present invention, the operation of the above-described proposal or invention may be provided as code that can be implemented, practiced, or executed by a "computer" (a comprehensive concept including a system on chip (SoC) or (micro)processor, etc.), or as a computer-readable storage medium or computer program product that stores or contains said code, and the scope of the present invention may be extended to said code or as a computer-readable storage medium or computer program product that stores or contains said code.
[0113] The detailed description of the preferred embodiments of the present invention disclosed above is provided to enable those skilled in the art to implement and practice the present invention. Although the present invention has been described with reference to preferred embodiments, those skilled in the art will understand that various modifications and changes can be made to the present invention as described in the following claims. Accordingly, the present invention is not intended to be limited to the embodiments shown herein, but to be given the broadest scope consistent with the principles and novel features disclosed herein.
Claims
Claim 1 A device configured to process a user request for a drawing result, comprising: a memory configured to detect a user request for a drawing result input through a human-machine interface and to store code configured to process said user request; and a processor configured to execute said code for an operation to process said user request, wherein the operation includes: determining a user request keyword corresponding to said user request, performing processing on a previously stored drawing result according to said determined user request keyword, and outputting the processed result to a display, wherein said user request keyword includes metadata for the drawing result and a type of user request. Claim 2 A device according to claim 1, wherein the metadata comprises at least one of the creator of the drawing result, the time of creation or modification, or keywords regarding the drawing result. Claim 3 A device according to claim 1, wherein the type of user request includes any one of a search request for a drawing result, a drawing event request using a drawing result, or a system setting request using a drawing result. Claim 4 A device according to paragraph 3, wherein the operation includes outputting a user interface component for inputting a keyword to search for the drawing result on the display, as the user request is a search request for the drawing result. Claim 5 A device according to paragraph 3, wherein the operation comprises detecting a drawing result corresponding to the metadata as the determined user request keyword corresponds to a search request for a drawing result, and outputting at least one of the detected drawing results to the display. Claim 6 A device according to paragraph 3, wherein the operation includes detecting a drawing result corresponding to the metadata as the determined user request keyword corresponds to a drawing event request using a drawing result, and outputting a result of processing a drawing event using any one of the detected drawing results to the display. Claim 7 A device according to paragraph 3, wherein the operation includes detecting a drawing result corresponding to the metadata as the determined user request keyword corresponds to a system setting request using a drawing result, and executing a system setting using any one of the detected drawing results. Claim 8 In claim 1, the device wherein the metadata includes a voice ID or face ID for the creator of the drawing result. Claim 9 A device according to claim 1, wherein the metadata includes information indicating the relationship between the creator of the drawing result and another creator. Claim 10 A device according to claim 1, wherein the operation comprises, whenever a drawing result is generated or saved, generating metadata for the drawing result and saving it together with the drawing result, and wherein the metadata includes at least one of the creator of the drawing result, the time of creation or modification, or keywords for the drawing result.