Operating method of electronic device for configuring information, and electronic device supporting same
The electronic device method effectively manages service module settings through a structured platform, addressing the complexity of e-commerce service delivery by establishing a scalable and accurate service module management system with regional standardization and dependency monitoring, enhancing service satisfaction and operational efficiency.
Patent Information
- Application Number
- PCT/KR2023/007073
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-15
- Filing Date
- 2023-05-24
- Publication Date
- 2024-11-21
AI Technical Summary
Existing electronic devices lack an efficient method to manage and set up service module settings for providing services through a platform, particularly in e-commerce, where detailed and accurate information is crucial for service satisfaction, and existing solutions do not effectively address the complexity of module layer structures, regional standardization, and dependency relationships.
An electronic device method that sets service module management information, including a module layer structure, domain execution, and regional standardization settings, to manage and initialize modules based on layer hierarchy relationships, allowing for easy reuse and expansion of the platform, with tools for monitoring dependency relationships and providing notification for incorrect configurations.
This method enables a modular and scalable service platform with standardized and region-specific settings, ensuring accurate service delivery and preventing conflicts, thereby enhancing service satisfaction and operational efficiency.
Smart Images

Figure KR2023007073_21112024_PF_FP_ABST
Abstract
Description
Method of operation of an electronic device for setting information and an electronic device supporting the same
[0001] The present invention relates to a method and device for setting information, and more particularly, to a method and electronic device for setting information for managing the settings of a module for providing a service through a platform.
[0002] With the advancement of electronic technology, e-commerce has become a prominent part of the shopping experience. Customers can purchase items online without having to visit a physical shopping mall or market, and items purchased online are delivered to the customer's requested delivery address.
[0003] In the case of e-commerce, providing detailed and accurate product information significantly impacts customer satisfaction, so various methods for providing more detailed and accurate information are being discussed.
[0004] In this regard, reference may be made to prior literature such as KR101756594B1 or KR101500849B1.
[0005] According to the method of the present invention, an electronic device can set information for managing the settings of a module for providing a service through a platform.
[0006] The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present invention belongs from the description below.
[0007] Various embodiments may provide an operating method of an electronic device for setting information and an electronic device supporting the same.
[0008] In accordance with various embodiments, a method for setting information in an electronic device comprises: a step of confirming a platform on which a service related to the electronic device is provided; and a step of setting service module management information for managing settings of a module for providing the service through the platform, wherein the service module management information may include first management information for managing settings for a module included in each layer of a module layer structure including one or more layers, second management information for managing operation settings for a domain execution module and a domain interface implementation module included in a domain layer related to a domain for an app of the service in the module layer structure, third management information for managing regional standardization settings and regional specificity settings for a module included in the domain layer, and fourth management information for managing initialization settings for the app based on module dependency relationship information determined according to a layer hierarchical relationship of the module layer structure.
[0009] In an exemplary embodiment, the platform may be a platform configured for a mobile operating system.
[0010] In an exemplary embodiment, the module layer structure included in the first management information may include an app layer including a module for a function related to execution of the app, a domain layer including a domain execution layer including a domain execution module and a domain interface layer including a domain interface implementation module, a common layer including a module for a function applied singly to the app, and a shared layer including a module for a function applied commonly to one or more apps of the service including the app.
[0011] In an exemplary embodiment, the method for setting information further includes a step of setting information about the layer hierarchical relationship, wherein the information about the layer hierarchical relationship may include information about a relationship between an upper layer and a lower layer identified between the one or more layers.
[0012] In an exemplary embodiment, the app layer may correspond to a higher layer of the domain layer, the domain layer may correspond to a higher layer of the common layer, and the common layer may correspond to a higher layer of the shared layer.
[0013] In an exemplary embodiment, the domain execution layer may correspond to a layer above the domain interface layer.
[0014] In an exemplary embodiment, based on information about the layer hierarchical relationship, a dependency relationship between modules included in a lower layer and modules included in an upper layer can be established.
[0015] In an exemplary embodiment, a module included in an upper layer may be set to be able to call a module included in a lower layer, and a module included in a lower layer may be set to be unable to call a module included in an upper layer.
[0016] In an exemplary embodiment, the second management information may include information for setting up a functional linking framework for recording source code of a domain execution module, and information for managing the domain execution module and domain interface implementation module included in the domain layer to operate based on the functional linking framework.
[0017] In an exemplary embodiment, each source code of each domain execution module included in the domain layer may be recorded in the functional linking framework, and each domain interface implementation module included in the domain layer may be set to call the source code of the domain execution module from the functional linking framework to implement an interface for the domain.
[0018] In an exemplary embodiment, the third management information may include information for setting a domain interface implementation module that is standardized and applied to the entire regions where the service is provided in the domain layer, and information for setting a domain execution module that is standardized and applied to the entire regions where the service is provided in the domain layer.
[0019] In an exemplary embodiment, the third management information may further include information for managing that flag information for specifying the execution method of each region is set for the first domain execution module when the first domain execution module, which is set to be standardized and applied, applies the same execution content to each region included in the regions where the service is provided while having different execution methods in each region, and information for setting the execution method of each region.
[0020] In an exemplary embodiment, the third management information may further include information for setting a second domain execution module in the domain layer that is specifically applied only to a certain region where the service is provided, and information for identifying the second domain execution module.
[0021] In an exemplary embodiment, the third management information may include information for managing the second domain execution module so that it does not have a dependency with a module applied for a region other than the predetermined region.
[0022] In an exemplary embodiment, the fourth management information may include information for setting an initialization order for modules for an app of the service based on a dependency relationship between modules for an app of the service included in the module dependency relationship information, and information for managing an app of the service to be initialized based on the initialization order.
[0023] In an exemplary embodiment, the fourth management information may include multidimensional image information indicating the dependency relationship and the initialization order.
[0024] In an exemplary embodiment, the service module management information may further include fifth management information for managing settings of a tool for monitoring the suitability of dependency relationships between modules for the app of the service included in the module dependency relationship information.
[0025] In an exemplary embodiment, the fifth management information may include information for managing to provide notification information indicating the incorrect dependency relationship when modules having an incorrect dependency relationship are identified.
[0026] In accordance with various embodiments, an electronic device for setting information comprises a processor; and one or more memories for storing one or more instructions, wherein the one or more instructions, when executed, control the processor to perform: a step of identifying a platform on which a service related to the electronic device is provided; and a step of setting service module management information for managing settings of a module for providing the service through the platform, wherein the service module management information may include first management information for managing settings for a module layer structure including one or more layers and each layer of the module layer structure, second management information for managing operation settings for a domain execution module and a domain interface implementation module included in a domain layer related to a domain for an app of the service in the module layer structure, third management information for managing regional standardization settings and regional specificity settings for a module included in the domain layer, and fourth management information for managing initialization settings for the app based on module dependency relationship information determined according to a layer hierarchical relationship of the module layer structure.
[0027] The various embodiments of the present disclosure described above are only some of the preferred embodiments of the present disclosure, and various embodiments reflecting the technical features of the various embodiments of the present disclosure can be derived and understood by a person having ordinary skill in the art based on the detailed description to be described below.
[0028] The present invention provides a method for setting information for managing the settings of a module for an electronic device to provide a service through a platform, thereby having a technical effect in that it is possible to set up a module structure that is easy to reuse and expand for the platform.
[0029] The effects that can be obtained from the present invention are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by a person having ordinary skill in the art to which the present invention belongs from the description below.
[0030] FIG. 1 is a drawing for explaining an information setting system in which an operation method of an electronic device for setting information according to various embodiments can be implemented.
[0031] FIG. 2 is a diagram illustrating the configuration of a server device (100) and a user device (200) according to various embodiments.
[0032] FIG. 3 is a diagram illustrating an operation method of a server device (100) for setting information according to various embodiments.
[0033] Figure 4 is a diagram illustrating an example of a module layer structure set up to provide services through a platform.
[0034] Figure 5 is a diagram illustrating an example of a layer hierarchical relationship by a module layer structure.
[0035] Figure 6 is a diagram illustrating an example of how a domain execution module and a domain interface implementation module included in a domain layer operate based on a functional linking framework.
[0036] Figure 7 is a diagram illustrating an example of multidimensional image information that displays dependency relationships and initialization sequences for modules included in a service app.
[0037] Figures 8 and 9 are diagrams illustrating an example of managing initialization settings for an app of a service.
[0038] Figure 10 is a diagram illustrating an example of how notification information indicating incorrect dependency relationships between modules may be provided.
[0039] The following embodiments combine components and features of various embodiments in a predetermined form. Each component or feature may be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, various embodiments may be formed by combining some components and features. The order of operations described in various embodiments may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment.
[0040] In the description of the drawings, procedures or steps that may obscure the gist of various embodiments are not described, and procedures or steps that can be understood by a person with ordinary skill in the art are also not described.
[0041] Throughout the specification, when a part is said to "comprising" (or including) a certain component, this does not mean that other components are excluded, but rather that other components can be included, unless specifically stated otherwise. In addition, terms such as "...part," "...unit," and "module" described in the specification mean a unit that processes at least one function or operation, which may be implemented by hardware, software, or a combination of hardware and software. In addition, the words "a" or "an," "one," "the," and similar related words may be used in the singular and plural sense in the context of describing various embodiments (especially in the context of the claims below) unless otherwise indicated herein or clearly contradicted by context.
[0042] Hereinafter, preferred embodiments according to various embodiments will be described in detail with reference to the attached drawings. The detailed description set forth below, together with the attached drawings, is intended to explain exemplary embodiments of various embodiments and is not intended to represent the only embodiments.
[0043] Additionally, specific terms used in various embodiments are provided to aid understanding of the various embodiments, and the use of such specific terms may be changed in other forms without departing from the technical spirit of the various embodiments.
[0044] FIG. 1 is a drawing for explaining an information setting system in which an operation method of an electronic device for setting information according to various embodiments can be implemented.
[0045] Referring to FIG. 1, the information setting system according to various embodiments may be implemented in various types of electronic devices. For example, the information setting system may be implemented in the server device (100) and the user device (200). In other words, the server device (100) and the user device (200) may perform operations according to various embodiments of the present disclosure based on the information setting system implemented in each device. For example, in various embodiments according to the present disclosure, the server device (100) may set service module management information that manages the settings of a module for providing a service through a platform, and the user device (200) may receive and output various information generated during the service module management information setting process of the server device (100). Meanwhile, the information setting system according to various embodiments is not limited to that illustrated in FIG. 1, and may be implemented in a wider variety of electronic devices and servers.
[0046] According to various embodiments, a server device (100) may be a device that performs wireless and wired communication with a plurality of user devices (200) and includes storage with a large storage capacity. For example, the server device (100) may be a cloud device that is linked with a plurality of user devices (200).
[0047] The user device (200) according to various embodiments may be a device that can be used by individual users, such as a desktop PC, tablet PC, or mobile terminal. In addition, other electronic devices that perform similar functions may be used as the user device (200).
[0048] An information setting system according to various embodiments may include various modules for operation. The modules included in the information setting system may be computer codes or one or more instructions implemented so that a physical device (e.g., a server device (100) and a user device (200)) in which the information setting system is implemented (or included in a physical device) can perform a specified operation. In other words, a physical device in which the information setting system is implemented stores a plurality of modules in a memory in the form of computer codes, and when the plurality of modules stored in the memory are executed, the plurality of modules can cause the physical device to perform specified operations corresponding to the plurality of modules.
[0049] FIG. 2 is a diagram illustrating the configuration of a server device (100) and a user device (200) according to various embodiments.
[0050] Referring to FIG. 2, the server device (100) and the user device (200) may include an input / output unit (210), a transceiver (or communication unit) (220), storage (230), and a processor (240).
[0051] The input / output unit (210) may be various interfaces or connection ports that receive user input or output information to the user. The input / output unit (210) may include an input module and an output module, and the input module receives user input from the user. The user input may be in various forms, including key input, touch input, and voice input. Examples of input modules that can receive such user input include not only a traditional keypad, keyboard, or mouse, but also a touch sensor that detects the user's touch, a microphone that receives a voice signal, a camera that recognizes gestures through image recognition, a proximity sensor including at least one of an illuminance sensor or an infrared sensor that detects the user's approach, a motion sensor that recognizes the user's movement through an acceleration sensor or a gyro sensor, and various other forms of input means that detect or receive various forms of user input, and the input module according to an embodiment of the present disclosure may include at least one of the devices listed above. Here, the touch sensor can be implemented as a piezoelectric or electrostatic touch sensor that detects touch through a touch panel or touch film attached to the display panel, an optical touch sensor that detects touch by an optical method, etc. In addition, the input module can be implemented in the form of an input interface (USB port, PS / 2 port, etc.) that connects an external input device that receives user input instead of a device that detects user input on its own. In addition, the output module can output various types of information. The output module can include at least one of a display that outputs an image, a speaker that outputs a sound, a haptic device that generates vibration, and various other forms of output means. In addition, the output module can be implemented in the form of a port-type output interface that connects the individual output means described above.
[0052] For example, an output module in the form of a display can display text, still images, and moving images. The display can include at least one of a liquid crystal display (LCD), a light emitting diode (LED) display, an organic light emitting diode (OLED) display, a flat panel display (FPD), a transparent display, a curved display, a flexible display, a 3D display, a holographic display, a projector, and various other devices capable of performing an image output function. Such a display can also be in the form of a touch display that is integrated with a touch sensor of the input module.
[0053] The transceiver (220) can communicate with other devices. Accordingly, the server device (100) and the user device (200) can transmit and receive information with other devices via the transceiver (220). For example, the server device (100) and the user device (200) can communicate with each other or with other devices using the transceiver (220).
[0054] Here, communication, i.e., transmission and reception of data, can be performed wired or wirelessly. To this end, the transceiver (220) may include a wired communication module that connects to the Internet, etc., via a LAN (Local Area Network), a mobile communication module that connects to a mobile communication network via a mobile communication base station and transmits and receives data, a short-range communication module that uses a WLAN (Wireless Local Area Network) series communication method such as Wi-Fi or a WPAN (Wireless Personal Area Network) series communication method such as Bluetooth or Zigbee, a satellite communication module that uses a GNSS (Global Navigation Satellite System) such as a GPS (Global Positioning System), or a combination thereof.
[0055] Storage (230) can store various types of information. Storage (230) can store data temporarily or semi-permanently. For example, the storage (230) of the server device (100) can store an operating program (OS: Operating System) for operating the server device (100), data for hosting a website, a program for generating Braille, or data related to an application (e.g., a web application). In addition, the storage (230) can store modules in the form of computer code, as described above.
[0056] Examples of storage (230) may include a hard disk drive (HDD), a solid state drive (SSD), flash memory, read-only memory (ROM), random access memory (RAM), etc. This storage (230) may be provided as a built-in type or a detachable type.
[0057] The processor (240) controls the overall operation of the server device (100) and the user device (200). To this end, the processor (240) may perform calculations and processing of various types of information and control the operation of components of the server device (100). For example, the processor (240) may execute a program or application for setting information. The processor (240) may be implemented as a computer or a similar device according to hardware, software, or a combination thereof. In terms of hardware, the processor (240) may be implemented in the form of an electronic circuit that processes electrical signals to perform control functions, and in terms of software, it may be implemented in the form of a program that drives the hardware processor (240). Meanwhile, unless otherwise specified in the following description, the operations of the server device (100) and the user device (200) may be interpreted as being performed under the control of the processor (240). That is, when the modules implemented in the above-described information setting system are executed, the modules can be interpreted as controlling the processor (240) to perform the following operations on the server device (100) and the user device (200).
[0058] In summary, the various embodiments may be implemented through various means. For example, the various embodiments may be implemented through hardware, firmware, software, or a combination thereof.
[0059] In the case of hardware implementation, the methods according to various embodiments may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc.
[0060] When implemented via firmware or software, the methods according to various embodiments may be implemented in the form of modules, procedures, or functions that perform the functions or operations described below. For example, software code may be stored in memory and executed by a processor. The memory may be located within or external to the processor and may exchange data with the processor via various known means.
[0061] Below, various embodiments are described in more detail based on the above technical concepts. The previously described concepts may be applied to the various embodiments described below. For example, operations, functions, terms, etc. not defined in the various embodiments described below may be performed and explained based on the previously described concepts.
[0062] The following description describes various embodiments assuming that the server device (100) performs an operation of setting service module management information that manages the settings of a module for providing a service through a platform.
[0063] FIG. 3 is a diagram illustrating an operation method of a server device (100) for setting information according to various embodiments.
[0064] According to FIG. 3, the server device (100) can confirm the platform on which the service is provided (301) and set service module management information for managing the settings of a module for providing the service through the platform (303). At this time, the service module management information may include first management information for managing settings for a module layer structure including one or more layers and modules included in each layer of the module layer structure, second management information for managing operation settings for a domain execution module and a domain interface implementation module included in a domain layer related to a domain for an app of the service in the module layer structure, third management information for managing regional standardization settings and regional specificity settings for a module included in the domain layer, and fourth management information for managing initialization settings for an app based on module dependency relationship information determined according to the layer hierarchical relationship of the module layer structure.
[0065] According to FIG. 3, the operation of setting service module management information by the server device (100) may be performed for a service provided by the server device (100) or a service related to the server device (100), and the service may correspond to a service in which multiple users using the service can order and purchase multiple items sold in the service. The multiple items sold in the service are not limited to the type or type of the items, and may include various types or types of items registered by sellers to sell the items.
[0066] Additionally, a module for providing a service can refer to a functional unit within a service that bundles data and functions processed through a program, as an element that sets up a program for the service. Individual modules can be set up for each function within the service, and a program containing various modules set up for various functions of the service can be utilized for the service.
[0067] According to various embodiments, in operation 301, the server device (100) can check the platform on which the service is provided.
[0068] For example, the platform that the server device (100) checks according to operation 301 may be a platform set for a mobile operating system. That is, the server device (100) may check a mobile operating system such as an Android platform or an iOS (iPhone Operating System) platform for providing a service on a mobile, and the service module management information that the server device (100) sets according to operation 303, which will be described later, may also correspond to information set in response to the mobile operating system. For example, the server device (100) may check an iOS platform among various mobile operating system platforms according to operation 301, and set service module management information according to operation 303, which will be described later, to provide a service through the iOS platform.
[0069] According to various embodiments, in operation 303, the server device (100) may set service module management information that manages settings of a module for providing a service through the platform.
[0070] For example, the service module management information set by the server device (100) according to operation 303 may include a module layer structure including one or more layers and first management information that manages settings for modules included in each layer of the module layer structure. At this time, the module layer structure set through the first management information may be set to include 1) an app layer including a module for a function related to the execution of an app of the service, 2) a domain layer including a domain execution layer including a domain execution module and a domain interface layer including a domain interface implementation module, 3) a common layer including a module for a function that is applied singly to an app of the service, and 4) a shared layer including a module for a function that is applied commonly to multiple apps of the service.
[0071] Here, 1) a module for a function related to the execution of an app of a service may refer to a module for performing a function required to start a service, 2) a domain execution module may refer to a module for performing a function on a domain included in a service, and a domain interface implementation module may refer to a module for implementing a function on a domain on an interface. In addition, 3) a module for a function uniquely applied to an app of a service may refer to a module for performing a function utilized only for the app among various apps of the service, and 4) a module for a function commonly applied to multiple apps of a service may refer to a module for a function that is basically or commonly utilized for multiple apps regardless of the type of app. An example of a module layer structure set through the first management information may be as shown in FIG. 4.
[0072] Figure 4 is a diagram illustrating an example of a module layer structure set up to provide services through a platform.
[0073] The module layer structure of FIG. 4 may include an app layer (401, "App") that includes modules for functions related to the execution of an app of a service, a domain layer (403, "Domain") that includes domain execution modules and domain interface implementation modules, a common layer (405, "Common pack") that includes modules for functions that are uniformly applied to an app of a service, and a shared layer (407, "Shared Pack") that includes modules for functions that are commonly applied to multiple apps of a service.
[0074] In Figure 4, modules included in each layer are depicted in a rectangular shape. For example, the domain layer of 403 may include modules that perform functions for each domain of the service, such as a gateway ("GW"), a product search results page ("SRP"), and a brand detail page ("PLP").
[0075] For example, the server device (100) can set information about the layer hierarchical relationship, including the hierarchical relationship between each layer, for one or more layers included in the module layer structure. That is, information about the relationship between upper layers and lower layers confirmed between one or more layers included in the module layer structure can be set by the server device (100). Specifically, the app layer can be set as the upper layer of the domain layer, the domain layer can be set as the upper layer of the common layer, and the common layer can be set as the upper layer of the shared layer. That is, a hierarchical relationship from the upper layer to the lower layer can be set in the order of app layer-domain layer-common layer-shared layer. In addition, between the domain execution layer and the domain interface layer included in the domain layer, the domain execution layer can be set as the upper layer of the domain interface layer.
[0076] For example, when information about the layer hierarchical relationship is set, a dependency relationship can be set between modules that depend on modules included in the upper layer. Specifically, when a hierarchical relationship between upper and lower layers is set between layers included in the module layer structure, modules included in the upper layer can be set to be able to call modules included in the lower layer, and modules included in the lower layer can be set to be unable to call modules included in the upper layer. In other words, by setting a dependency relationship between modules so that only modules included in the upper layer can call modules included in the lower layer in a top-down format, conflicts that occur due to discrepancies in the scope or order of application of modules when one module calls another module can be prevented. For example, a module included in the app layer can call modules included in all other layers, but a module included in the domain layer cannot call modules included in the app layer and can only call modules included in the common layer or shared layer, and a module included in the shared layer can be set to be unable to call modules included in other layers.
[0077] Figure 5 is a diagram illustrating an example of a layer hierarchical relationship by a module layer structure.
[0078] The module layer structure of FIG. 5 may include an app layer (501), a domain layer (503), a common layer (505), and a shared layer (507), similar to FIG. 4, and at this time, a layer hierarchy relationship may be determined in which the app layer is set as a higher layer of the domain layer, the domain layer is set as a higher layer of the common layer, the common layer is set as a higher layer of the shared layer, and the domain execution layer is set as a higher layer of the domain interface layer within the domain layer.
[0079] Depending on the layer hierarchical relationship, modules included in each layer may have a dependency relationship between modules based on a top-down method. Specifically, a dependency relationship may be formed in which modules included in an upper layer are set to be able to call modules included in a lower layer, but modules included in a lower layer are set to be unable to call modules included in a higher layer.
[0080] For example, the service module management information set by the server device (100) according to operation 303 may include second management information that manages specific operation settings for the domain execution module and domain interface implementation module included in the domain layer. In particular, the second management information may manage operation settings for the domain execution module and the domain interface implementation module so that an operation of implementing the domain function as a service interface can be performed by calling the source code of the domain execution module by the domain interface implementation module.
[0081] The domain execution module can be set as the source code for various functions executed in the domain on the service, and at this time, the server device (100) can set the function linking framework for recording the source code of the domain execution module, and manage the domain execution module and domain interface implementation module included in the domain layer to operate based on the function linking framework. Here, the function linking framework can also be understood as a library that can record the source code of the domain execution module for various functions executed in the domain on the service.
[0082] Specifically, the server device (100) can set the source codes of all domain execution modules included in the domain layer to be recorded in the function linking framework through the second management information. In addition, from the function linking framework including the source codes of the domain execution modules, a specific domain interface implementation module corresponding to a specific interface in which a certain function of a domain on a service is executed can be set to call the source code of the domain execution module for the certain function to implement the certain function on the specific interface. Here, the source code that the domain interface implementation module calls from the function linking framework is not limited to the source code of the domain execution module for performing a function in one domain to which the domain interface implementation module corresponds, and can also be set to call the source code of the domain execution module for performing a function related to a domain other than the domain to which the domain interface implementation module corresponds. For example, the GW domain interface implementation module corresponding to the gateway (GW) domain of a service can, if necessary, call the source code of the domain execution module for performing a function of the shopping cart (Cart) domain of the service to implement a function required in relation to the shopping cart on the gateway interface of the service.
[0083] Figure 6 is a diagram illustrating an example of how a domain execution module and a domain interface implementation module included in a domain layer operate based on a functional linking framework.
[0084] Figure 6 illustrates the domain layer and the functional wiring framework. The domain layer includes domain execution modules, categorized by domain, for executing functions for each domain of the service, such as the gateway ("GW"), brand detail page ("PLP"), product detail page ("SDP"), and shopping cart ("Cart"). Domain interface implementation modules, categorized by domain, for implementing functions for each domain as interfaces on the domain, are also included ("Module interface").
[0085] In Fig. 6, the source code of all domain execution modules included in the domain layer can be recorded in the function linking framework (601). That is, all source codes for all functions executed corresponding to each domain of the service can be recorded in the function linking framework. In this way, for the function linking framework including the source code for the functions executed corresponding to each domain, the domain interface implementation module can call the source code corresponding to the function of the domain to be implemented from the function linking framework to implement the function on the interface of the service (603). As described above, the source code called by the domain interface implementation module from the function linking framework is not limited to the source code of the domain execution module for performing the function of the domain to which the domain interface implementation module corresponds, and can also be set to call the source code of the domain execution module for performing the function of another domain as needed.
[0086] For example, the service module management information set by the server device (100) according to operation 303 may include third management information that manages regional standardization settings and regional specific settings for modules included in the domain layer. Specifically, the third management information may standardize and set the domain execution module and the domain interface implementation module included in the domain layer so that the domain execution module and the domain interface implementation module can be commonly applied regardless of the region in which the service is provided, or may set the domain execution module for a service function utilized only for a specific region among the regions in which the service is provided so that it can be applied in a specific manner only for the specific region.
[0087] First, through the third management information, the server device (100) can manage the domain interface implementation module that is standardized and applied to the entire region where the service is provided so that it is set and included in the domain layer, and also the domain execution module that is standardized and applied to the entire region where the service is provided can also be managed so that it is set and included in the domain layer. That is, the server device (100) can set the domain interface implementation module or domain execution module that is standardized and applied to the entire region where the service is provided through the third management information, and the module of the domain layer set in this way can basically correspond to the same module that can be commonly utilized for the entire region where the service is provided. For example, if the service is provided to Korea (KR) and Taiwan (TW) and the shopping cart interface and shopping cart function are the same in the service provided to each country, the domain interface implementation module for the shopping cart and the domain execution module for the shopping cart function can be set to be standardized and included in the domain layer. In this case, a standardized single domain execution module for the shopping cart function is recorded in the function linking framework, so that the domain interface implementation module for the shopping cart can call and utilize the standardized single domain execution module for the shopping cart function regardless of the country in which the service is provided, Korea or Taiwan.
[0088] At this time, some of the domain execution modules set to be standardized and applied may have different execution methods depending on the region, even if the same execution content is applied to the entire region where the service is provided. In other words, the source code for the domain execution modules set to be standardized and applied may be commonly utilized in the entire region where the service is provided, but the method of executing the function of the service corresponding to the domain execution module may differ depending on the region. To this end, source code for different execution methods for each region may be additionally added and managed for each region.
[0089] The third management information set by the server device (100) may include information on additional source codes applied to each region as described above, as well as regional flag information indicating that additional source codes are set and applied for each region. In other words, the third management information may include, for a first domain execution module set to be applied in a standardized manner, information on additional source codes that set the execution method for each region and flag information for designating the execution method for each region corresponding to each region, when the first domain execution module applies the same execution contents to the entire region where the service is provided but has different execution methods for each region.
[0090] For example, if the first domain execution module corresponding to the shopping cart function is commonly applied to services in Korea and Taiwan, but the execution methods are different in each country, the third management information may include 1) information additionally setting the Korean shopping cart function execution method required for the first domain execution module to be executed in Korea and flag information for designating Korea, and 2) information additionally setting the Taiwanese shopping cart function execution method required for the first domain execution module to be executed in Taiwan and flag information for designating Taiwan. By setting the above information, the third management information can manage the execution of the shopping cart function on the service according to the country in which the service is provided, among Korea and Taiwan. In this case, various information required for the first domain execution module to be executed in Korea and various information required for the first domain execution module to be executed in Taiwan may be recorded in the function linking framework together with the first domain execution module as information regarding the first domain execution module.
[0091] In addition, the third management information may also include information for setting up a region-specific domain execution module that is utilized only in a specific region, as opposed to a domain execution module that is standardized to be utilized commonly in the entire region. In other words, the third management information may include information for setting up a region-specific domain execution module in the domain layer that is specifically applied only to a certain region where the service is provided, and may also include module identification information for separately identifying the region-specific domain execution module and region identification information for identifying the region to which the region-specific domain execution module is applied. Similarly, the module identification information and region identification information for the region-specific domain execution module may be recorded in the functional linkage framework together with the region-specific domain execution module as being related to the region-specific domain execution module.
[0092] Additionally, the server device (100) may set third management information to further include information for managing that the region-specific domain execution module does not have dependencies on modules applied for other regions, in order to prevent the region-specific domain execution module from conflicting with modules utilized in other regions.
[0093] For example, the service module management information set by the server device (100) according to operation 303 may include fourth management information for managing initialization settings for apps based on module dependency relationship information determined according to the layer hierarchical relationship of the module layer structure. The fourth management information may include information for setting an initialization order for modules based on a dependency relationship between modules for an app of a service included in the module dependency relationship information, and information for managing the app of the service to be initialized according to the set initialization order. In addition, for the convenience of the administrator, the fourth management information may be set to include multidimensional image information for indicating the dependency relationship between modules and the initialization order of the modules.
[0094] Figure 7 is a diagram illustrating an example of multidimensional image information that displays dependency relationships and initialization sequences for modules included in a service app.
[0095] In Figure 7, five modules are simply illustrated as being included in a service app. The five modules illustrated can be configured to have a dependency relationship among themselves as modules within each layer. Once the dependency relationship between modules is confirmed, the initialization order of the app can be determined to begin with the initialization of modules within the upper layer and end with the initialization of modules within the lower layer, so as to avoid conflicts between modules during app initialization.
[0096] The arrows between the five modules illustrated in Fig. 7 represent dependency relationships between each module. The module indicated at the starting point of the arrow may correspond to a module in the upper layer, and the module indicated at the ending point of the arrow may correspond to a module in the lower layer. Based on such dependency relationships, the initialization order of each module may be determined. In Fig. 7, the lower the number of each module, the higher the number corresponds to a module in the upper layer, and the faster the initialization order may be set. On the other hand, the higher the number corresponds to a module in the lower layer, and the later the initialization order may be set.
[0097] Figures 8 and 9 are diagrams illustrating an example of managing initialization settings for an app of a service.
[0098] In Fig. 8, in order to initialize the app of the service, "Initializer(s)" can be set to manage information on one or more modules to be initialized (801), and based on the "Initializer(s)", an "InitGraph" can also be set to specify which logic should be initialized for each stage of the initialization process and, accordingly, which dependency relationship one or more modules should have and in which order they should be initialized (803). Afterwards, multidimensional image information indicating the initialization order and dependency relationship for one or more modules set in the "InitGraph" can be set (805), and such multidimensional image information can be transferred to the "InitManager" that manages the initialization to facilitate the manager's app initialization management (807).
[0099] FIG. 9 shows that initialization can be performed on a per-app basis for the service. Specifically, a different "InitGraph" is set for each app of the service based on an "Initializer" that includes information about modules included in each app of the service, and initialization for each app can be performed according to the determined dependency relationship and initialization order for the modules included in each app according to the "InitGraph." In FIG. 9, "InitGraph A" is set for app A to check the dependency relationship for the modules included in app A, determine the initialization order, and perform initialization (901), and "InitGraph B" is set for app B to check the dependency relationship for the modules included in app B, determine the initialization order, and perform initialization (903).
[0100] For example, the service module management information set by the server device (100) according to operation 303 may further include fifth management information for managing the settings of a tool for monitoring the suitability of dependency relationships between modules included in the module dependency relationship information. That is, if a dependency relationship is incorrectly determined, a conflict may occur in a call between modules, so a tool for monitoring the suitability of dependency relationships between modules may be set to prevent such conflicts, and the fifth management information for managing the operation of the tool may be included in the service module management information set by the server device (100) according to operation 303. In this case, the fifth management information may also include information for managing to provide notification information indicating the incorrect dependency relationship to an administrator when modules having an incorrect dependency relationship are identified.
[0101] Figure 10 is a diagram illustrating an example of how notification information indicating incorrect dependency relationships between modules may be provided.
[0102] FIG. 10 may be an example of a dependency relationship between modules being monitored through a tool that monitors suitability of the dependency relationship between modules (1000). In this case, if a conflict is identified, such as the inability to call each other between some modules, and the dependency relationship is incorrectly determined, notification information indicating that the dependency relationship is incorrectly determined may be provided (1001).
[0103] It is obvious that each piece of information can be combined in various forms during the process of performing the operation method of setting service module management information by the server device (100) according to FIGS. 3 to 10.
[0104] The embodiments of the present invention disclosed in this specification and drawings are merely specific examples to easily explain the technical content of the present invention and to facilitate understanding of the present invention, and are not intended to limit the scope of the present invention. In other words, it will be apparent to those skilled in the art that other modifications based on the technical concept of the present invention are possible. Furthermore, the above-described embodiments can be combined and operated as needed. For example, all embodiments of the present invention can be implemented as a system by combining parts with each other.
[0105] In addition, the method according to the system or the like according to the present invention may be implemented in the form of program commands that can be executed through various computer means and recorded on a computer-readable medium.
[0106] As such, various embodiments of the present invention can be implemented as computer-readable code on a computer-readable recording medium in certain aspects. A computer-readable recording medium is any data storage device capable of storing data that can be read by a computer system. Examples of computer-readable recording media can include read-only memories (ROMs), random access memories (RAMs), compact disk-read-only memories (CD-ROMs), magnetic tapes, floppy disks, optical data storage devices, and carrier waves (such as data transmission over the Internet). A computer-readable recording medium can also be distributed across network-connected computer systems, so that the computer-readable code is stored and executed in a distributed manner. Additionally, functional programs, codes, and code segments for achieving various embodiments of the present invention can be easily interpreted by programmers skilled in the field to which the present invention is applied.
[0107] It will also be appreciated that devices and methods according to various embodiments of the present invention can be implemented in the form of hardware, software, or a combination of hardware and software. Such software may be stored in a volatile or non-volatile storage device, such as a ROM, for example, regardless of whether it is erasable or rewritable, or in a memory, such as a RAM, a memory chip, a device, or an integrated circuit, or in a storage medium that is optically or magnetically recordable and machine-readable (e.g., a computer), such as a compact disk (CD), a DVD, a magnetic disk, or a magnetic tape. It will be appreciated that methods according to various embodiments of the present invention can be implemented by a computer including a control unit and a memory, or a vehicle including such a memory or a computer, and such a memory is an example of a machine-readable storage medium suitable for storing a program or programs including commands for implementing embodiments of the present invention.
[0108] Accordingly, the present invention encompasses a program containing code for implementing the devices or methods described in the claims of this specification, and a machine-readable storage medium (e.g., a computer) storing such a program. Furthermore, such a program may be transmitted electronically via any medium, such as a communication signal transmitted via a wired or wireless connection, and the present invention appropriately encompasses equivalents thereof.
[0109] Although the present invention has been described above with reference to embodiments, the embodiments of the present invention disclosed in this specification and drawings are merely specific examples to easily explain the technical content of the present invention and assist in understanding the present invention, and are not intended to limit the scope of the present invention. Furthermore, the embodiments of the present invention described above are merely exemplary, and those skilled in the art will understand that various modifications and equivalent embodiments are possible. Therefore, the true technical protection scope of the present invention should be defined by the following claims.
Claims
1. In the method of setting information by an electronic device, A step of confirming a platform on which a service related to the electronic device is provided; and A step of setting service module management information for managing the settings of a module for providing the service through the platform is included, The above service module management information is: A module layer structure including one or more layers and first management information for managing settings for modules included in each layer of the module layer structure; Second management information that manages operation settings for the domain execution module and domain interface implementation module included in the domain layer related to the domain for the app of the service in the above module layer structure; Third-party management information that manages regional standardization settings and regional specificity settings for modules included in the above domain layer, and Based on the module dependency relationship information determined according to the layer hierarchical relationship of the above module layer structure, including the fourth management information for managing the initialization settings for the app. How to set information.
2. In paragraph 1, The above platform is a platform set up for the mobile operating system. How to set information.
3. In paragraph 1, The module layer structure included in the above first management information is, An app layer that includes modules for functions related to the execution of the above app; The domain layer including a domain execution layer including a domain execution module and a domain interface layer including a domain interface implementation module, A common layer containing modules for functions that are applied singly to the above app, and A shared layer including a module for a function that is common to one or more apps of the service including the app, How to set information.
4. In paragraph 3, The method of setting the above information is: Further comprising a step of setting information about the above layer hierarchical relationship, Information about the layer hierarchical relationship includes information about the relationship between the upper layer and the lower layer identified between one or more layers. How to set information.
5. In paragraph 4, The above app layer corresponds to the upper layer of the above domain layer, The above domain layer corresponds to the upper layer of the above common layer, The above common layer corresponds to the upper layer of the above shared layer, How to set information.
6. In paragraph 4, The above domain execution layer corresponds to the upper layer of the above domain interface layer. How to set information.
7. In paragraph 4, Based on the information about the above layer hierarchical relationship, a dependency relationship is established between modules that have dependencies on modules included in the upper layer. How to set information.
8. In paragraph 7, Modules included in the upper layer are set to be able to call modules included in the lower layer, Modules included in lower layers are set to be unable to call modules included in upper layers. How to set information.
9. In paragraph 1, The above second management information is, Information on setting up a functional linking framework for recording the source code of domain execution modules, and Including information for managing the domain execution module and domain interface implementation module included in the above domain layer to operate based on the above functional connection framework. How to set information.
10. In paragraph 9, Each source code of each domain execution module included in the above domain layer is recorded in the above functional linking framework, Each domain interface implementation module included in the above domain layer is set to implement an interface for the domain by calling the source code of the domain execution module from the above function linking framework. How to set information.
11. In paragraph 1, The above third management information is: Information on setting up a domain interface implementation module that is standardized and applied to the entire region where the above service is provided in the domain layer, and Includes information on setting up a domain execution module in the domain layer that is standardized and applied to the entire region where the above service is provided. How to set information.
12. In paragraph 11, The above third management information is: When the first domain execution module, which is set to be standardized and applied, applies the same execution content to each region included in the regions where the service is provided, but has different execution methods in each region, information for managing flag information for specifying the execution method in each region is set for the first domain execution module, and Further including information setting the execution method for each of the above regions, How to set information.
13. In paragraph 11, The above third management information is: Information for setting a second domain execution module in the domain layer that is specifically applied only to a certain area where the above service is provided, and Further comprising information for identifying the second domain execution module, How to set information.
14. In paragraph 13, The above third management information is: Including information for managing that the second domain execution module does not have a dependency with a module applied for a region other than the specified region. How to set information.
15. In paragraph 1, The above 4th management information is, Information for setting the initialization order for modules for the app of the service based on the dependency relationship between modules for the app of the service included in the module dependency relationship information, and Including information for managing the initialization of the app of the service based on the initialization order. How to set information.
16. In paragraph 15, The above 4th management information is, including multidimensional image information indicating the above dependency relationship and the above initialization order, How to set information.
17. In paragraph 1, The above service module management information is: Further comprising fifth management information for managing the settings of a tool for monitoring the suitability of dependency relationships between modules for the app of the service included in the above module dependency relationship information. How to set information.
18. In paragraph 17, The above fifth management information is: Including information that manages to provide notification information indicating incorrect dependency relationships when modules with incorrect dependency relationships are identified. How to set information.
19. In an electronic device that sets information, processor; and Contains one or more memories that store one or more instructions, The one or more instructions, when executed, cause the processor to: A step of confirming a platform on which a service related to the electronic device is provided; and Controlling the processor to perform a step of setting service module management information for managing the settings of a module for providing the service through the platform; The above service module management information is: A module layer structure including one or more layers and first management information for managing settings for modules included in each layer of the module layer structure; Second management information that manages operation settings for the domain execution module and domain interface implementation module included in the domain layer related to the domain for the app of the service in the above module layer structure; Third-party management information that manages regional standardization settings and regional specificity settings for modules included in the above domain layer, and Based on the module dependency relationship information determined according to the layer hierarchical relationship of the above module layer structure, including the fourth management information for managing the initialization settings for the app. Electronic devices.
Citation Information
Patent Citations
Mobile Terminal Comprising Layered Architecture
KR1020040103925A
Supporting system for unification processing data based on cloud
KR1020170087224A
Method, apparatus, computer program for appoving offer
KR1020180057433A
Operating method for configuring data serving structure and electronic apparatus supporting thereof
KR102403609B1
System and method for extracting a business rule embedded in an application source code
US9875098B2
