Component-based data management method and device

Abstract

A component-based data management method and device are disclosed. A component-based data management method according to an embodiment may comprise the steps of: obtaining a component configuration request for a design element applicable to a fashion item; configuring the design element as a component on the basis of whether a component corresponding to the design element exists; and assigning an identifier of a new version to the component.

Description

Component-based data management method and device

[0001] The following embodiments relate to a component-based data management method and apparatus.

[0002] In the fashion industry, virtual fashion item creation tools that allow for the design and simulation of fashion items in a virtual environment are being widely utilized for production and design. These tools enable designers to input information such as the shape, fabric, color, pattern, and materials of a fashion item, allowing them to visually verify the design before actual production. Consequently, there is a growing demand for technologies that can systematically organize, manage, and utilize digital-based fashion item data.

[0003] A component-based data management method for a fashion item design according to one embodiment includes the steps of: obtaining a request to set a component for a design element applicable to a fashion item; setting the design element as a component based on whether a component corresponding to the design element exists; and assigning a new version of an identifier to the component.

[0004] The above method may further include the step of creating an instance of the component to which the identifier of the new version is assigned; and the step of inserting the instance into a fashion item file to which the design element is applied.

[0005] The above method may further include the step of identifying an instance of the component mapped to an identifier of the component in at least one fashion item file based on a version update of the component; and the step of updating the identified instance in the at least one fashion item file based on the latest version of the component.

[0006] The step of identifying an instance of the above component may include identifying an instance of the above component that is mapped to an identifier of the above component based on a version update of the above component and corresponds to the extension of the latest version of the above component.

[0007] The step of setting the above design element as a component may include the step of setting the above design element as a new component in response to determining that there is no component corresponding to the above design element.

[0008] The step of assigning a new version identifier to the above component may include: a step of generating a unique identifier for the new component in response to a determination that there is no component corresponding to the design element; and a step of assigning a new version identifier to the new component based on the unique identifier.

[0009] The step of setting the above design element as a component may include the step of updating the component based on the design element in response to determining that a component corresponding to the above design element exists.

[0010] The step of assigning a new version of an identifier to the above component may include the step of assigning the new version of an identifier to the above component based on the identifier of the existing version of the above component in response to determining that a component corresponding to the above design element exists.

[0011] The above method may further include the step of changing a design element set to a specific version of the component; and the step of updating the component based on the changed design element.

[0012] The step of changing a design element set to a specific version of the above component may include the step of changing a design element set to a specific version of the above component based on the acquired fashion item specifications.

[0013] The step of changing a design element set to a specific version of the above component may include the step of changing a design element set to a specific version of the above component based on the user's settings.

[0014] A component-based data management method for a fashion item design according to one embodiment includes: identifying a modified instance within a fashion item file; identifying a component corresponding to the instance based on an identifier of a component mapped to the modified instance; obtaining an identifier of a new version of the component; and updating the modified instance to the new version of the component in correspondence with the obtained identifier.

[0015] The step of identifying a component corresponding to the above instance may include: receiving a request for a component update based on the modified instance; and responding to the request, identifying a component corresponding to the instance.

[0016] The step of identifying a component corresponding to the instance in response to the above request may include: a step of verifying the component change authority of the user account that requested the component update; and a step of identifying a component corresponding to the instance based on the result of verifying the change authority.

[0017] An electronic device according to one embodiment comprises at least one processor including processing circuitry; and a memory for storing instructions, wherein, when executed by the at least one processor, the instructions cause the electronic device to perform the following operations: obtaining a request to set a component for a design element applicable to a fashion item; setting the design element as a component in response to determining that no component corresponding to the design element exists; and assigning a new version identifier to the component.

[0018] An electronic device according to one embodiment comprises at least one processor including processing circuitry; and a memory storing instructions, wherein, when executed by the at least one processor, the instructions cause the electronic device to perform the following operations: identifying a modified instance within a fashion item file; identifying a component corresponding to the instance based on an identifier of a component mapped to the modified instance; obtaining an identifier of a new version of the component; and updating the modified instance to the new version of the component in correspondence with the obtained identifier.

[0019] FIG. 1 is an operation flowchart of a component-based data management method according to one embodiment.

[0020] FIG. 2 is a diagram illustrating an overview of a system for a fashion item data management service according to one embodiment.

[0021] FIG. 3 is a diagram illustrating the operation of a system for a fashion item data management service according to one embodiment.

[0022] FIG. 4 is a diagram illustrating the operation of a system for a fashion item data management service according to one embodiment.

[0023] FIG. 5 is an operation flowchart of a component-based data management method according to one embodiment.

[0024] FIG. 6 is a diagram illustrating the operation of a system for a fashion item data management service according to one embodiment.

[0025] FIG. 7 is a drawing for explaining components and instances corresponding to design elements according to one embodiment.

[0026] FIG. 8 is a diagram illustrating the operation of updating an instance based on a version update of a component according to one embodiment.

[0027] FIG. 9 is an example diagram of the configuration of an electronic device according to one embodiment.

[0028] Specific structural or functional descriptions of the embodiments are disclosed for illustrative purposes only and may be modified and implemented in various forms. Accordingly, actual implementations are not limited to the specific embodiments disclosed, and the scope of this specification includes modifications, equivalents, or substitutions included in the technical concept described by the embodiments.

[0029] In relation to the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of the noun corresponding to an item may include one or more of said items unless the relevant context clearly indicates otherwise.

[0030] In this document, each of the phrases such as "A or B", "at least one of A and B", "at least one of A or B", "A, B or C", "at least one of A, B and C", and "at least one of A, B, or C" may include any one of the items listed together in the corresponding phrase, or all possible combinations thereof.

[0031] Terms such as “first,” “second,” or “first” or “second” may be used simply to distinguish a component from another component and do not limit the components in other aspects (e.g., importance or order). For example, a first component may be named a second component, and similarly, a second component may be named a first component.

[0032] Where any (e.g., 1st) component is referred to as “coupled” or “connected” to another (e.g., 2nd) component, with or without the terms “functionally” or “communicationly,” it means that said any component may be connected to said other component directly (e.g., via a wire), wirelessly, or through a third component.

[0033] The singular expression includes the plural expression unless the context clearly indicates otherwise. In this specification, terms such as "comprising" or "having" are intended to specify the existence of the described features, numbers, steps, actions, components, parts, or combinations thereof, 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.

[0034] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as generally understood by those skilled in the art. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and should not be interpreted in an ideal or overly formal sense unless explicitly defined in this specification.

[0035] Hereinafter, embodiments will be described in detail with reference to the attached drawings. In the description with reference to the attached drawings, identical components are given the same reference numeral regardless of the drawing number, and redundant descriptions thereof will be omitted.

[0036] FIG. 1 is an operation flowchart of a component-based data management method according to one embodiment.

[0037] The operations of steps (110) to (130) included in the component-based data management method described in FIG. 1 may be performed sequentially, but are not necessarily performed sequentially. For example, the order of steps (110) to (130) may be changed, and at least two of the operations may be performed in parallel.

[0038] The component-based data management method described in FIG. 1 may be performed in an electronic device. The component-based data management method described in FIG. 1 may include a component-based data management method for designing fashion items or a fashion item data management method. An electronic device performing the component-based data management method described in FIG. 1 may include at least one of a server providing a fashion item data management service and a terminal utilizing the fashion item data management service. A fashion item is an item such as clothing and accessories related to fashion in a digital form, and may include, for example, at least one of a virtual fashion item, a hat, a scarf, a belt, gloves, socks, shoes, a bag, and accessories. The fashion item data management service is a data management service for designing, creating, producing, or simulating a virtual fashion item, and for example, the fashion item data management service may include a service that creates, edits, and stores data for a virtual fashion item and provides a function to visually simulate the created fashion item.

[0039] A user may use the fashion item data management service provided by the server through a terminal. For example, a user may use the fashion item data management service provided by the server through an application (hereinafter referred to as "app") regarding the fashion item data management service running on the terminal or through a web regarding the fashion item data management service. In the following, "app" or "web" refers to the app regarding the fashion item data management service or the web regarding the fashion item data management service.

[0040] Referring to FIG. 1, a component-based data management method according to one embodiment may include the step (110) of obtaining a component setting request for a design element.

[0041] A design element is an element applicable to a fashion item and may be data (or a file) containing information necessary for the production of the fashion item or information indicating at least one of the physical, visual, and functional characteristics of the fashion item. For example, a design element may include a file containing information indicating at least one of the fabric type of the fashion item (e.g., cotton, polyester, nylon, leather, etc.), the color of the fabric, auxiliary materials included in the fashion item (e.g., buttons, zippers, hooks, etc.), and internal materials. As an example, a design element may indicate a virtual raw material file used for the creation and / or modification of fashion item data. Specifically, a design element may include at least one of a virtual fabric file, a virtual button file, a virtual trim file, a virtual zipper file, and / or a virtual stitch file. For example, a virtual raw material file may include information indicating at least one of the physical properties, texture, and color of the raw material. Meanwhile, for convenience of explanation in this disclosure, the word "virtual" preceding the terms "clothing," "fashion," "fabric," "button," "trim," "zipper," and / or "stitch" is omitted. Accordingly, the terms "clothing," "fashion," "fabric," "button," "trim," "zipper," and / or "stitch" used in this disclosure may be interpreted as including "virtual."

[0042] A component is a management unit of design elements that can be referenced or applied for the design of one or more fashion items, and may serve as a standard file for design elements. For example, a component may be an independent object managed as master data that allows design elements with identical attributes to be applied or included in multiple fashion item files, containing a unique identifier and version information corresponding to the change history of the attributes. An instance may be a derived object of a component created from a component. In other words, an instance may be an object that inherits information contained in a component. Since an instance is an object that inherits the information contained in a component exactly as it is, the instance is an object dependent on the component, and a dependency relationship can be established between the component and the instance. An instance may be a duplicate file of a design element configured as a component.

[0043] For example, an electronic device can obtain a request for component configuration for a design element from user input. In other words, the user can request component configuration for a design element. For example, a server can obtain a request for component configuration for a design element from a terminal.

[0044] A component-based data management method according to one embodiment may include a step (120) of setting a design element as a component based on whether there is a component corresponding to the design element.

[0045] At least some of the design elements can be configured as components. Configuring a design element as a component may mean identifying, storing, or managing the design element as a component. For example, a user's device can configure a loaded or generated design element (or design element file) as a component. For instance, the device can send a request to configure a design element as a component to a server, and in response to this request, the server can configure the design element as a component. The component configuration request can be sent to the server via an app or the web.

[0046] For example, an electronic device can determine whether a component corresponding to a design element exists. For example, a server can determine whether a component corresponding to a design element exists and can transmit the result of determining the existence of the component corresponding to the design element to a terminal. For example, a server can determine whether a component corresponding to a design element exists and can control the terminal to set the design element as a component according to the result of the determination.

[0047] At least one of the cases where the design element is a newly created design element and the case where the design element has never been set as a component prior to step (120) may correspond to a case where there is no component corresponding to the design element.

[0048] At least one of the following cases may correspond to a case where a design element is loaded as a component or a specific version of a component prior to step (120), a case where a design element is modified as a component or a specific version of a component prior to step (120), and a case where a design element is an instance of a component set prior to step (120) may correspond to a case where a component corresponding to the design element exists.

[0049] According to one embodiment, the existence of a component corresponding to a design element can be determined by whether the design element is mapped to the identifier of the component. For example, an electronic device can determine the existence of a component corresponding to a design element by whether the design element is mapped to the identifier of the component. For example, a server can determine the existence of a component corresponding to a design element by whether the design element is mapped to the identifier of the component, and can transmit the result of determining the existence of the component corresponding to the design element to a terminal. For example, a server can determine the existence of a component corresponding to a design element and can control the terminal to set the design element as a component according to the result of the determination.

[0050] If a design element is mapped to a component's identifier, the design element may be an instance of a component that was created before step (120), or may correspond to a component that was created before step (120). If a design element is mapped to a component's identifier, it may be determined that a component corresponding to the design element exists. For example, if the component's identifier is stored as metadata in the design element, the design element may be determined to be mapped to the component's identifier. For example, if an instance is created from a component, the mapping relationship between the component's identifier and the instance may be stored in a mapping relationship database. It may be determined whether a design element is mapped to a component's identifier by referring to the mapping relationship database.

[0051] A design element can be set as a new component or as an already created component. Setting a design element to an already created component may correspond to updating a component that has already been created as a design element.

[0052] According to one embodiment, the step (120) of setting a design element as a component may include the step of setting the design element as a new component in response to determining that there is no component corresponding to the design element.

[0053] According to one embodiment, the step (120) of setting a design element as a component may include the step of updating a component based on the design element in response to determining that a component corresponding to the design element exists. The component corresponding to the design element may be updated to reflect the design element.

[0054] A component-based data management method according to one embodiment may include the step (130) of assigning a new version identifier to a component.

[0055] When a design element is configured as a component, a new version of the identifier corresponding to the component may be generated for version management of the component. For example, an electronic device may generate a new version of the identifier corresponding to the component to configure a design element as a component. For example, a server may generate a new version of the identifier corresponding to the component to configure a design element as a component, and a terminal may receive the new version of the identifier generated by the server.

[0056] According to one embodiment, the step (130) of assigning a new version of an identifier to a component may include the step of generating a unique identifier for a new component in response to determining that there is no component corresponding to a design element, and the step of assigning a new version of an identifier to a new component based on the unique identifier.

[0057] According to one embodiment, the step (130) of assigning a new version identifier to a component may include the step of assigning a new version identifier to the component based on the identifier of an existing version of the component in response to determining that a component corresponding to a design element exists. For example, if there is an existing version of the component, an identifier obtained by changing the version number from the identifier of the existing version of the component may be assigned as the identifier of the new version of the component.

[0058] A unique identifier may be assigned to each version of a component. The identifier for each version of a component is a value used to uniquely distinguish each version of the component corresponding to a design element. For example, the identifier for each version of a component may include the component's unique identifier (e.g., ID) and a content identifier (e.g., ID). The component's unique identifier is an identifier unique to the component to distinguish it from other components, and it may be an identifier that remains the same between different version(s) of the same component. The content identifier is an identifier assigned to each version of the component and may include identifiers to distinguish and indicate each version, such as a version number. For example, if a component corresponding to a design element does not exist, the design element may be set as a new component, and a new unique identifier for the new component may be generated and assigned as the identifier for the new version of the new component, along with a content identifier indicating the initial version. For example, if a component is newly created, 'aaa' may be generated as the component's unique identifier. The first version of a component is assigned a content identifier '01', so the identifier of the first version of the component can be determined as 'aaa_01'. For example, if a component corresponding to a design element exists, a content identifier indicating the next version of the existing version is generated based on the identifier of the component's existing version, and this can be determined as the identifier of the new version along with the unique identifier included in the identifier of the component's existing version. For example, the second version of a component whose unique identifier is 'aaa' is assigned a content identifier '02', so the identifier of the component's second version can be determined as 'aaa_02'.

[0059] Components assigned a new version identifier corresponding to a design element may be stored on an electronic device or in external memory accessible from the electronic device (e.g., a cloud server). The component's previous version(s) may be stored as the component's version history. Through the component's version history, design elements corresponding to the component's previous version(s) as well as the latest version may be stored.

[0060] A component-based data management method according to one embodiment may include the step of creating an instance of a component to which an identifier of a new version of the component is assigned. The instance of the component may correspond to a replica of the latest version of the component. In other words, the instance of the component may contain the information of the design element, which is the latest version of the component, exactly as it is.

[0061] An instance of a component can be mapped to a component identifier. For example, a component instance mapping to a component identifier may mean that the component identifier is embedded or stored as the instance's metadata. As an example, a component instance may be mapped to the component's unique identifier included in the component's latest version identifier, or it may be mapped to the entire component's latest version identifier, which includes the unique identifier and the content identifier. The component of the instance can be referenced through the component identifier mapped to the instance.

[0062] An instance of a generated component may be updated based on a version update of the component. A version update of the component may refer to a case where the latest version of the component is replaced. In other words, if a design element is saved as a new version of the component while an existing version of the component exists, it may constitute a version update of the component. For example, if steps (110) to (130) are performed while a component corresponding to a design element exists, and a new version of the component is saved, this may constitute a version update of the component. If an instance of the component is an instance generated from an existing version of the component before step (110) is performed, the instance of the component may be updated when a new version of the component is set (or saved) according to steps (110) to (130).

[0063] A component-based data management method according to one embodiment may include the step of inserting an instance into a fashion item file to which a design element is applied. The fashion item file may be a file containing information about a fashion item having characteristics indicated by the design element. Specifically, the information about the fashion item included in the fashion item file may include detailed information about physical properties and / or materials defined for each of one or more design elements applied to (or included in) the fashion item. The detailed information about physical properties may include at least one of, for example, stretch, bending stiffness, density, thickness, and friction coefficient, as parameters for simulating the physical form and movement of the design element. The detailed information about the material may include at least one of, for example, a texture map, normal map, color, opacity, reflection, and surface roughness, as parameters for rendering the surface texture and visual features of the design element. For example, a fashion item file may include one or more design elements. For example, a fashion item file may include instances corresponding to one or more design elements. For example, a fashion item file may include at least one of information required for the production of a fashion item, information for shaping a fashion item, and information for simulating a fashion item. The terminal (210) can simulate a virtual fashion item shape based on the fashion item file and output the simulation result through an output device such as a display.

[0064] For example, if a design element set to a specific version of a component is changed, a version update of the component may be performed. Changing a design element set to a specific version of a component may mean modifying the component. In other words, a component-based data management method may include a step of changing a design element set to a specific version of a component and a step of updating the component based on the changed design element.

[0065] According to one embodiment, the step of changing a design element set to a specific version of a component may include the step of changing a design element set to a specific version of a component based on a user's settings. The user may access a design element set to a specific version of a component through a terminal and change the design element. For example, the version of the component to be changed may be selected by user input. The design element of the selected version may be modified by user input.

[0066] According to one embodiment, the step of changing a design element set to a specific version of a component may include the step of changing a design element set to a specific version of a component based on acquired fashion item specifications. The fashion item specifications may be data indicating the attributes of a fashion item to be manufactured. When fashion item specifications are input, the electronic device may change a design element set to a specific version of a component to include the attributes of the fashion item indicated by the fashion item specifications.

[0067] When a design element set to a specific version of a component is changed, an identifier for the new version of the component may be generated. The electronic device may store the changed design element as the new version of the component corresponding to the identifier. Instances created from the component before the design element set to a specific version of the component was changed may be updated based on the new version of the component.

[0068] A component-based data management method according to one embodiment may include the steps of identifying an instance of a component mapped to an identifier of a component in at least one fashion item file based on a version update of the component, and updating the instance based on the latest version of the identified component in at least one fashion item file.

[0069] An instance created from a specific version of a component may be mapped to the component's unique identifier assigned to the component, or to an identifier of a specific version of the component that includes the unique identifier and the content identifier. For example, among the instances stored in an electronic device, an instance of a component mapped to the component's unique identifier included in the component's identifier may be identified. For example, among the instances stored in an electronic device, an instance of a component mapped to the identifier of an existing version of the component may be identified.

[0070] An instance of an identified component can be updated based on the latest version of the component. An instance of an identified component can be updated to include the information of the latest version of the component exactly as it is. For example, when the latest version of the component includes first color information and an instance created from an existing version of the component includes second color information, the color information of the instance can be changed to the first color information.

[0071] For example, an instance of an identified component may be updated to map to the identifier of the latest version of the component. For example, if an instance of a component is mapped to the unique identifier of the component assigned to the component, the mapping information of the instance may not be changed.

[0072] According to one embodiment, the step of identifying an instance of a component may include identifying an instance of a component that is mapped to an identifier of a component based on an update of the component's version and corresponds to an extension of the latest version of the component.

[0073] The file extension of a design element corresponding to a component may change due to a version update of the component. For example, a design element of an existing version of the component may correspond to a file with a first extension, and a design element of the latest version of the component may correspond to a file with a second extension. Instances with a different extension from the latest version of the component may not be updated in response to the latest version of the component. In this case, if the extension of the component changes, the dependency relationship between the component and the instance may be released. In other words, only instances with the same extension as the latest version of the component may be updated based on the latest version of the component.

[0074] According to one embodiment, when a design element of a specific version of a component is changed, whether to update the version of the component based on the changed design element can be determined by user input. For example, when a user requests to save a changed design element through a terminal, the user may choose whether to update the version of the component based on the changed design element or to set the changed design element as a new component. If it is selected to update the version of the component based on the changed design element, an identifier for the new version of the component may be generated, and the changed design element may be saved as the new version of the component corresponding to the identifier. If it is selected to set the changed design element as a new component, a new component corresponding to the changed design element may be generated. An identifier may be assigned to the new component, and the changed design element may be saved as the initial version of the new component.

[0075] FIG. 2 is a diagram illustrating an overview of a system for a fashion item data management service according to one embodiment.

[0076] Referring to FIG. 2, a system for a fashion item data management service according to one embodiment may include a terminal (210), a server (220), and a cloud server (230). As an example, a component-based data management method may be performed as an operation of the system for a fashion item data management service.

[0077] A terminal (210) according to one embodiment may be a terminal implemented as a computer device. For example, the terminal (210) may refer to any device capable of installing and running apps or running the web, such as a computer, a portable computer, a wireless phone, a mobile phone, a smartphone, a PDA (Personal Digital Assistants), a tablet, and a wearable device. The terminal (210) may communicate with a server (220) and / or other electronic devices via a network using a wireless or wired communication method. The terminal (210) may correspond to an electronic device that performs the component-based data management method described in FIG. 1.

[0078] A server (220) according to one embodiment may be implemented as a computer device or a plurality of computer devices that communicate with a terminal (210) and / or a cloud server (230) via a network to provide commands, code, files, content, services, etc. The communication method is not limited and may include a communication method utilizing a communication network that the network may include (e.g., mobile communication network, wired internet, wireless internet, broadcasting network), and a short-range wireless communication method between devices.

[0079] A server (220) according to one embodiment may include a server that provides a fashion item data management service. The server (220) may correspond to an electronic device that performs the component-based data management method described in FIG. 1.

[0080] According to one embodiment, the server (220) may be linked with an app or web related to a fashion item data management service executed on a terminal (210) for a user interface (UI), function, operation, or service.

[0081] For example, a server (220) can provide a web regarding a fashion item data management service to a terminal (210) connected via a network. The terminal (210) can receive the service or content provided by the server (220) through the web.

[0082] For example, the server (220) can provide a file for installing an app to a terminal (210) connected via a network. In this case, the terminal (210) can install an app for a fashion item data management service using the file provided by the server (220).

[0083] The terminal (210) can run an app or web related to the fashion item data management service provided by the server (220). The user can use the fashion item data management service provided by the server (220) by running the app or web related to the fashion item data management service on the terminal (210). For example, the terminal (210) can connect to the server (220) and receive services or content provided by the server (220) under the control of an operating system (OS) included in the terminal (210) and at least one program (e.g., a browser or an installed app).

[0084] The terminal (210) can perform overall operations of the fashion item data management service, such as configuring the fashion item data management service screen, inputting data, transmitting and receiving data, and storing data, under the control of an app or web. For example, when the terminal (210) transmits a service request message to the server (220) via a network under the control of the app, the server (220) can transmit a code corresponding to the service request message to the terminal (210), and the terminal (210) can provide content to the user by configuring and displaying a screen according to the code under the control of the app. For example, the terminal (210) can process a user interface or user interaction through a processor, and can output or transmit the processing result through the output device of the terminal (210).

[0085] For example, a user can create a user account by subscribing to the fashion item data management service through an app or web related to the fashion item data management service. The user can use the fashion item data management service through a terminal (210) of the user account subscribed to the fashion item data management service. The terminal (210) of the account subscribed to the fashion item data management service may refer to a terminal logged in with the user account subscribed to the fashion item data management service.

[0086] The cloud server (230) can be linked with the server (220). The cloud server (230) can store data generated from the use of the fashion item data management service and / or data required for the use of the fashion item data management service. For example, the cloud server (230) can allocate storage space for each user account subscribed to the fashion item data management service. Data generated through an app or web logged in with the user account can be stored in the storage space allocated to the user account. The terminal (210) can download data from the cloud server (230) and upload data to the cloud server (230). Data stored in the cloud server (230) can be synchronized with the terminal (210). For example, data stored in the storage space allocated to the user account within the cloud server (230) can be synchronized with the terminal (210) running the app or web logged in with that user account.

[0087] For example, the terminal (210) can use the fashion item data management service based on data stored in the local storage space of the terminal (210) by running an app related to the fashion item data management service. Some functions of the fashion item data management service may be provided locally on the terminal (210) through the app related to the fashion item data management service without real-time communication with the server (220). The terminal (210) can download data stored on the cloud server (230) by running an app related to the fashion item data management service.

[0088] For example, the terminal (210) can use the fashion item data management service based on data stored in the cloud server (230) by running a web related to the fashion item data management service. The terminal (210) can also upload data stored in the terminal (210) to the cloud server (230) by running a web related to the fashion item data management service, and can download data stored in the cloud server (230) to the terminal (210).

[0089] According to one embodiment, an interface for creating and editing a fashion item dataset (or file) may be provided to the terminal (210) via an app or the web. The interface for creating and editing fashion item files may provide functions for designing fashion items or functions for creating, editing, and simulating virtual fashion item files. For example, through the interface for creating and editing fashion item files, the user may input information regarding the characteristics of the fashion item, such as the shape of the fashion item, the raw materials of the fashion item, and auxiliary materials included in the fashion item. The input information may be stored in the terminal (210) or a cloud server (230) in the form of design elements. Based on the design elements, a fashion item file may be created.

[0090] As described above, storage space of the cloud server (230) corresponding to the user account may be allocated. For example, a fashion item file created and edited through the terminal (210) of the user account may be stored in the storage space of the cloud server (230). For example, a design element set as a component through the terminal (210) of the user account may be stored in the cloud server (230) and may be synchronized with the terminal (210). An instance of the component may be stored in the cloud server (230) corresponding to the user account and may also be stored in the local storage space of the terminal (210).

[0091] FIG. 3 is a diagram illustrating the operation of a system for a fashion item data management service according to one embodiment.

[0092] The terminal, server, and cloud server depicted as the subjects of operation in FIG. 3 may correspond to the terminal (210), server (220), and cloud server (230) of FIG. 2, respectively.

[0093] Referring to FIG. 3, the terminal can perform the operation (310) of loading a design element. The terminal may load a design element stored in the terminal's local storage space, or may download a design element stored on a cloud server and load the downloaded design element.

[0094] The terminal can perform an operation (320) to modify a loaded design element. The operation (320) to modify a design element may be performed optionally, and the operation (320) to modify a design element may not be performed.

[0095] The terminal can send a request (330) for component setting for a design element to the server. For example, when saving a design element at the terminal, whether the design element is set as a component can be input through an interface. If an input to set the design element as a component is received, a request (330) for component setting for the design element can be sent to the server. Meanwhile, if an input to set the design element as a component is not received, the design element is not set as a component, and the design element can be saved to the terminal or cloud server.

[0096] The server may receive a request (330) for component configuration for a design element from a terminal. The server may perform an operation (340) to determine whether there is a component corresponding to the design element. As described above, for example, the existence of a component corresponding to the design element may be determined by whether there is an identifier of the component mapped to the design element.

[0097] According to one embodiment, the server can determine whether the identifier of the component mapped to the design element is valid by querying (350) the identifier of the component mapped to the design element from the cloud server. The server may request the cloud server to query the identifier of the component mapped to the design element, and the cloud server may transmit the query result of the identifier of the component mapped to the design element to the server. If the identifier of the component mapped to the design element is not queried from the cloud server, the identifier of the component mapped to the design element may be determined to be invalid. If the identifier of the component mapped to the design element is invalid, it may be determined that an existing version of the component does not exist. If the identifier of the component mapped to the design element is queried from the cloud server, the identifier of the component mapped to the design element may be determined to be valid. If the identifier of the component mapped to the design element is valid, it may be determined that an existing version of the component exists.

[0098] The server may perform an operation (360) of generating an identifier for a new version of a component based on whether there is a component corresponding to a design element. If there is no component corresponding to a design element, a new identifier for a new version of the component including a unique identifier for the component may be generated. If there is a component corresponding to a design element, an identifier for a new version of the component may be generated based on the identifier of an existing version of the component. For example, a new identifier for a new version of the component may be generated by adding a new content identifier corresponding to the new version to the unique identifier of the component included in the identifier of the existing version.

[0099] The server can transmit the generated identifier and design element (370) to the cloud server. In other words, the server can control the cloud server so that the design element is set (or saved) as a new version of the component in correspondence with the generated identifier.

[0100] The cloud server can perform an operation (380) of updating the version of a component based on a design element. The design element can be stored in the cloud server as the latest version of the component. If an existing version of the component exists, the latest version of the component can be updated with the design element. If an existing version of the component does not exist, a new component corresponding to the design element is created, and the design element can be stored as the initial version of the new component.

[0101] The terminal may send a request (390) to the server to create an instance of the component. In response to the terminal's request (390) to create an instance, the server may query (3100) the latest version of the component from the cloud server. The server may create an instance that is an object of the latest version of the component. The created instance may contain information included in the latest version of the component. In other words, the created instance may correspond to a replica of the design element of the latest version of the component.

[0102] The server can transmit the instance (3110) created on the terminal. The terminal can output the instance through the interface.

[0103] According to one embodiment, the terminal may request the server to create an instance of a specific version of the component. For example, the request to create an instance of the component (390) may include information indicating the version of the component. If the version of the component is specified, the server may query the cloud server for the specific version of the component, and an instance of the specific version of the component may be created. The instance may correspond to a replica of the design element of the specific version of the component. If the request to create an instance (390) does not include information indicating the specific version of the component, the instance may be created as an instance of the latest version of the component.

[0104] FIG. 4 is a diagram illustrating the operation of a system for a fashion item data management service according to one embodiment.

[0105] The terminal, server, and cloud server depicted as the subjects of operation in FIG. 4 may correspond to the terminal (210), server (220), and cloud server (230) of FIG. 2, respectively.

[0106] FIG. 4 illustrates the operation of a system for a fashion item data management service after the operation (380) of updating the version of a component based on the design element of FIG. 3.

[0107] Referring to FIG. 4, based on a version update of a component, the server can perform an operation (410) of identifying an instance of a component mapped to an identifier of the component for which a version update occurred. For example, when a fashion item file is loaded on a terminal, the server can identify an instance of a component included in the fashion item file based on the fashion item file (420) loaded on the terminal.

[0108] The server can perform an operation (430) of updating an identified instance based on the latest version of the component. An instance of the identified component can be updated to include the information of the latest version of the component as is. The updated instance (440) can be transmitted to a terminal and / or cloud server.

[0109] FIG. 5 is an operation flowchart of a component-based data management method according to one embodiment.

[0110] The operations of steps (510) to (540) included in the component-based data management method described in FIG. 5 may be performed sequentially, but are not necessarily performed sequentially. For example, the order of steps (510) to (540) may be changed, and at least two of the operations may be performed in parallel.

[0111] The component-based data management method described in FIG. 5 can be performed in an electronic device. The electronic device performing the component-based data management method described in FIG. 5 may include at least one of a server providing a fashion item data management service and a terminal using the fashion item data management service. The electronic device performing the component-based data management method described in FIG. 5 may correspond to the electronic device described above in FIG. 1.

[0112] Referring to FIG. 5, a component-based data management method according to one embodiment may include the step (510) of identifying modified instances within a fashion item file. A fashion item file may contain one or more instances. As described above, an instance may be an object created from a component. A fashion item file may contain one or more instances created from one or more components. Different instances included in a fashion item file may be created from different components or may be created from the same component. For example, a fashion item file may include a first instance created from a first component and a second instance created from a second component. For example, a fashion item file may include a third instance created from a third component and a fourth instance created from the third component.

[0113] A component-based data management method according to one embodiment may include the step (520) of identifying a component corresponding to an instance based on an identifier of a component mapped to a modified instance. As described above, an instance may be mapped to an identifier of a component. For example, an instance created from a specific component may include the identifier of the specific component as metadata. For example, if an instance is created from a first version of a first component, the instance may be mapped to the identifier of the first version of the first component, or it may be mapped to the component unique ID of the first component.

[0114] A component-based data management method according to one embodiment may include a step (530) of obtaining an identifier for a new version of a component. The step (530) of obtaining an identifier for a new version of a component may correspond to the step (120) described above in FIG. 1. The step (530) may correspond to the step (120) in the case where an existing version of the component of FIG. 1 exists.

[0115] A component-based data management method according to one embodiment may include a step (540) of updating a modified instance corresponding to an acquired identifier to a new version of the component. The step (540) of updating a modified instance corresponding to an acquired identifier to a new version of the component may correspond to the step (130) described above in FIG. 1. The step (540) may correspond to the step (130) in the case where the design element of FIG. 1 is a modified instance.

[0116] According to one embodiment, the step (520) of identifying a component corresponding to an instance may include receiving a request for a component update based on a modified instance and, in response to the request, identifying a component corresponding to the instance. The request for a component update based on a modified instance may be a request to save the modified instance as a new version of the component. If there is a request for a component update based on a modified instance, steps (520) through (540) may be performed. In other words, if there is a request for a component update based on a modified instance, the modified instance may be saved as a new version of the component identified as corresponding to the instance.

[0117] According to one embodiment, the step of identifying a component corresponding to the instance in response to a request may include the step of verifying the component change authority of the user account that requested the component update, and the step of identifying the component corresponding to the instance based on the result of verifying the change authority.

[0118] A component may be configured to be available to one or more user accounts. In other words, access rights to the component may be granted to one or more user accounts. A terminal of a user account with access rights to the component may acquire an instance of the component. Access rights to modify the component may be granted to at least some of the user accounts with access rights to the component.

[0119] If a request for a component update based on an instance modified by a user account with verified change permissions is received, the modified instance may be saved as a new version of the component identified as corresponding to the instance.

[0120] Meanwhile, if a request for a component update based on an instance modified by a user account whose change permissions have not been verified is received, the component update may not be performed. In other words, the modified instance may not be saved as a new version of the component.

[0121] According to one embodiment, the dependency relationship between a component and an instance can be released by user input. When the dependency relationship between an instance and a component is released by user input, the component of the instance may not be updated even if the instance is modified.

[0122] FIG. 6 is a diagram illustrating the operation of a system for a fashion item data management service according to one embodiment.

[0123] The terminal, server, and cloud server depicted as the subjects of operation in FIG. 6 may correspond to the terminal (210), server (220), and cloud server (230) of FIG. 2, respectively.

[0124] Referring to FIG. 6, the terminal can perform an operation (610) to modify an instance. The terminal may load and modify an instance stored in the terminal's local storage space, or download an instance stored on a cloud server and load and modify the downloaded instance.

[0125] The terminal can transmit modified instance information (620) to the server. The modified instance information (620) may be a design element corresponding to the modified instance. The modified instance information (620) may be a design element containing information indicated by the modified instance. Based on the modified instance information (620), the server can query (630) the component corresponding to the modified instance in the cloud server. Based on the identifier of the component mapped to the modified instance, the server can query (630) the component corresponding to the modified instance in the cloud server.

[0126] The server may perform the operation (640) of generating an identifier for a new version of a component corresponding to the modified instance. An identifier for a new version of a component may be generated based on the identifier of an existing version of a component. For example, an identifier for a new version of a component may be generated by adding a new content ID corresponding to the new version to the component unique ID included in the identifier of the existing version.

[0127] The server can transmit the generated identifier and modified instance information (650) to the cloud server. In other words, the server can control the cloud server so that the modified instance corresponding to the generated identifier is saved as a new version of the component.

[0128] The cloud server can perform an operation (660) of updating the version of the component based on the modified instance information. The modified instance information can be stored in the cloud server as the latest version of the component. The latest version of the component can be updated with the modified instance information.

[0129] FIG. 7 is a drawing for explaining components and instances corresponding to design elements according to one embodiment.

[0130] As described above, an interface for creating and editing fashion item files may be provided on a terminal through an app or web related to a fashion item data management service. Hereinafter, the interface for creating and editing fashion item files may be briefly referred to as the interface.

[0131] FIG. 7 illustrates a design element (710), an interfacing object (720), and an instance (730) displayed on the screen of a terminal through a user interface.

[0132] A design element (710) regarding the fabric of a fashion item can be generated through an interface. The design element regarding the fabric of a fashion item may include information indicating the type of fabric (e.g., cotton, polyester, nylon, leather, etc.) and color.

[0133] A design element (710) can be configured as a component by user settings. For example, an interfacing object (720) for configuring the component of a design element (710) may be provided through an interface. When an input to configure the design element (710) as a component is received through the interfacing object (720), a request to configure the component of the design element may be sent to the server.

[0134] The server can generate an identifier for a new version of the component and save the design element (710) as a new version of the component corresponding to the generated identifier.

[0135] The terminal may request the server to create an instance of the component through an interface. If there is a request for instance creation, the server may create an instance (730) of the component and transmit it to the terminal. The instance (730) of the component may be a replica of the design element (710) which is the latest version of the component. In other words, the instance (730) of the component may correspond to a design element regarding a fabric of the type and color indicated by the design element (710) which is the latest version of the component. The instance (730) may include the identifier (731) of the component as metadata. One or more instances (730) of the component may be created. For example, an instance (730) of the component may be created by a request from a terminal of a user account that has access rights to the component.

[0136] FIG. 8 is a diagram illustrating the operation of updating an instance based on a version update of a component according to one embodiment.

[0137] Referring to FIG. 8, fashion item files (800) may be stored on a cloud server and / or a terminal of a user account in correspondence with the user account. For example, some of the fashion item files (800) may include one or more instances.

[0138] If the version of a specific component corresponding to a user account is updated, an instance of that specific component can be identified among the instances corresponding to the user account. The specific component corresponding to the user account may refer to a component created or configured through the app or web application logged in with the user account.

[0139] For example, a fashion item file (810, 820) containing an instance of a specific component among fashion item files may be identified. The fashion item file (810, 820) containing an instance of a specific component may be marked to distinguish it from other fashion item files. For example, a marker indicating that there is an instance to be updated may be displayed adjacent to the name of the fashion item file (810, 820) containing an instance of a specific component.

[0140] For example, a user can load a fashion item file onto a device and determine whether to update an instance of a specific component included in the fashion item file. If it is determined to update the instance, the instance of the specific component included in the fashion item file may be modified to reflect the latest updated version of the component.

[0141] For example, instances of a specific component included in a fashion item file can be batch updated to reflect the latest updated version of that component.

[0142] For example, when attempting to change the color of a fabric applied to multiple fashion item files, multiple design elements created as instances of the component can be changed in bulk by modifying the color information of the component related to the fabric.

[0143] FIG. 9 is an example diagram of the configuration of an electronic device according to one embodiment.

[0144] Referring to FIG. 9, the electronic device (900) includes a processor (901), a memory (903), and a communication device (905). The electronic device (900) may correspond to an electronic device that performs the component-based data management method described above through FIG. 1 to FIG. 8. For example, the electronic device (900) may correspond to a server and / or terminal of a system for the fashion item data management service described above through FIG. 1 to FIG. 8.

[0145] A processor (901) according to one embodiment may perform at least one operation described above through FIGS. 1 to 8. For example, the processor (901) may perform the operation of the component-based data management method described above through FIG. 1. For example, the processor (901) may perform the operation of the component-based data management method described above through FIG. 5. For example, the processor (901) may perform the operation of a terminal using the fashion item data management service described above through FIGS. 1 to 8. For example, the processor (901) may perform the operation of a server providing the fashion item data management service described above through FIGS. 1 to 8. The processor (901) may be configured to process instructions of a computer program by performing basic arithmetic, logic, and input / output operations. Instructions may be provided to the processor (901) by a memory (903) or a communication device (905).

[0146] The memory (903) according to one embodiment may be a volatile memory or a non-volatile memory. For example, the memory (903) may store data regarding the component-based data management method described above through FIGS. 1 to 8. For example, the memory (903) may store data regarding the fashion item data management service described above through FIGS. 1 to 8.

[0147] According to one embodiment, the memory (903) can store a program in which the component-based data management method described above through FIGS. 1 to 8 is implemented. The processor (901) can execute the program stored in the memory (903) and control the electronic device (900). The code of the program executed by the processor (901) can be stored in the memory (903).

[0148] A memory (903) according to one embodiment may store commands. For example, when the commands are executed by the processor (901), the electronic device (900) may perform the operation of obtaining a request to set a component for a design element applicable to a fashion item, the operation of setting the design element as a component in response to determining that there is no component corresponding to the design element, and the operation of assigning a new version identifier to the component. For example, when the commands are executed by the processor (901), the electronic device (900) may perform the operation of identifying a modified instance within a fashion item file, the operation of identifying a component corresponding to the instance based on the identifier of the component mapped to the modified instance, the operation of obtaining an identifier of a new version of the component, and the operation of updating the modified instance to the new version of the component in response to the obtained identifier.

[0149] A communication device (905) according to one embodiment may provide a function for an electronic device (900) to communicate with another electronic device or another server through a network. In other words, the electronic device (900) may be connected to an external device (e.g., a cloud server, a terminal, a server, or a network) through the communication device (905) and exchange data.

[0150] An electronic device (900) according to one embodiment may further include other components not illustrated. For example, the electronic device (900) may further include an input / output interface including an input device and an output device as a means for interfacing with a communication device (905). Also, for example, the electronic device (900) may further include other components such as a transceiver, various sensors, a database, etc.

[0151] The embodiments described above may be implemented as hardware components, software components, and / or combinations of hardware and software components. For example, the devices, methods, and components described in the embodiments may be implemented using a general-purpose computer or a special-purpose computer, such as, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a programmable logic unit (PLU), a microprocessor, or any other device capable of executing and responding to instructions. The processing unit may execute an operating system (OS) and software applications executed on said operating system. Additionally, the processing unit may access, store, manipulate, process, and generate data in response to the execution of the software. For ease of understanding, the processing unit may be described as being used as a single unit, but those skilled in the art will understand that the processing unit may include multiple processing elements and / or multiple types of processing elements. For example, the processing unit may include multiple processors or one processor and one controller. In addition, other processing configurations, such as parallel processors, are also possible.

[0152] Software may include computer programs, code, instructions, or a combination of one or more of these, and may configure a processing unit to operate as desired or instruct the processing unit independently or collectively. Software and / or data may be stored on any type of machine, component, physical device, virtual equipment, computer storage medium, or device so as to be interpreted by the processing unit or to provide instructions or data to the processing unit. Software may be distributed over networked computer systems and stored or executed in a distributed manner. Software and data may be stored on computer-readable recording media.

[0153] The method according to the embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer-readable medium. The computer-readable medium may store program instructions, data files, data structures, etc., either individually or in combination, and the program instructions recorded on the medium may be those specifically designed and configured for the embodiment or those known and available to those skilled in the art of computer software. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tapes; optical recording media such as CD-ROMs and DVDs; magneto-optical media such as floptical disks; and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, and flash memory. Examples of program instructions include machine code, such as that generated by a compiler, as well as high-level language code that can be executed by a computer using an interpreter, etc.

[0154] The hardware device described above may be configured to operate as one or more software modules to perform the operation of the embodiment, and vice versa.

[0155] Although the embodiments have been described above with reference to the limited drawings, those skilled in the art can apply various technical modifications and variations based thereon. For example, suitable results may be achieved even if the described techniques are performed in a different order than described, and / or if the components of the described system, structure, device, circuit, etc. are combined or assembled in a form different from described, or replaced or substituted by other components or equivalents.

[0156] Therefore, other implementations, other embodiments, and equivalents to the claims also fall within the scope of the claims set forth below.

Claims

1. In a component-based data management method for fashion item design, A step of obtaining a component configuration request for a design element applicable to a fashion item; A step of setting the design element as a component based on whether there is a component corresponding to the design element; and Step of assigning a new version identifier to the above component including, method.

2. In Paragraph 1, The step of creating an instance of the component to which the identifier of the new version is assigned; and Step of inserting the above instance into a fashion item file to which the above design element is applied including, method.

3. In Paragraph 1, Based on a version update of the above component, identifying an instance of the above component mapped to an identifier of the above component in at least one fashion item file; and A step of updating the identified instance within the at least one fashion item file based on the latest version of the above component. including, method.

4. In Paragraph 3, The step of identifying an instance of the above component A step of identifying an instance of the component that maps to an identifier of the component and corresponds to the extension of the latest version of the component, based on a version update of the component. including, method.

5. In Paragraph 1, The step of setting the above design element as a component is A step of setting the design element as a new component in response to determining that there is no component corresponding to the above design element. including, method.

6. In Paragraph 5, The step of assigning a new version of the identifier to the above component A step of generating a unique identifier for the new component in response to determining that there is no component corresponding to the above design element; and A step of assigning a new version of the identifier to the new component based on the unique identifier above. including, method.

7. In Paragraph 1, The step of setting the above design element as a component is A step of updating the component based on the design element in response to determining that a component corresponding to the design element exists. including, method.

8. In Paragraph 7, The step of assigning a new version of the identifier to the above component In response to determining that a component corresponding to the above design element exists, a step of assigning the identifier of the new version to the component based on the identifier of the existing version of the component. including, method.

9. In Paragraph 7, A step of changing a design element set to a specific version of the above component; and A step of updating the component based on the above-mentioned changed design element including, method.

10. In Paragraph 9, The step of changing a design element set to a specific version of the above component A step of changing a design element set to a specific version of the above component based on the acquired fashion item specifications. including, method.

11. In Paragraph 9, The step of changing a design element set to a specific version of the above component A step of changing a design element set to a specific version of the above component based on user settings including, method.

12. In a component-based data management method for fashion item design, Step of identifying modified instances within a fashion item file; A step of identifying a component corresponding to the instance based on the identifier of a component mapped to the modified instance; A step of obtaining an identifier for a new version of the above component; and A step of updating the modified instance to a new version of the component in correspondence with the acquired identifier. including, method.

13. In Paragraph 12, The step of identifying the component corresponding to the above instance Receiving a request for a component update based on the above modified instance; and A step of identifying a component corresponding to the instance in response to the above request including, method.

14. In Paragraph 13, The step of identifying a component corresponding to the instance in response to the above request A step of verifying the component change authority of the user account that requested the above component update; and A step of identifying a component corresponding to the instance based on the result of verifying the above change authority. including, method.

15. A computer program stored on a computer-readable medium in combination with hardware to execute the method of claim 1.

16. In electronic devices, At least one processor including processing circuitry; and Memory that stores instructions Includes, When the above commands are executed by the at least one processor, the electronic device, An action of obtaining a component configuration request for a design element applicable to a fashion item; An operation to set the design element as a component in response to determining that there is no component corresponding to the design element; and The operation of assigning a new version of the identifier to the above component causing to perform, Electronic device.

17. In electronic devices, At least one processor including processing circuitry; and Memory that stores instructions Includes, When the above commands are executed by the at least one processor, the electronic device, Action to identify modified instances within a fashion item file; An operation to identify a component corresponding to the instance based on the identifier of a component mapped to the modified instance; An operation to obtain an identifier for a new version of the above component; and The operation of updating the modified instance to a new version of the component in correspondence with the acquired identifier. causing to perform, Electronic device.

Images