TWI872364B - Electronic apparatus for providing information of item and method thereof - Google Patents

Abstract

Disclosed is a method of providing item information in a first database, the method including acquiring first information including information on a group for grouping a plurality of items, acquiring second information including item information on a main item included in the group and a sub-item set to be grouped with the main item, generating third information including the first information and the second information, and providing the third information to a controller of an electronic apparatus, wherein, based on the third information, a page including information associated with the main item and at least a portion of the sub-item set is provided in the controller.

Description

Electronic device and method for providing item information

The present invention relates to an electronic device and method for providing item information. More specifically, the present invention relates to a method for obtaining first information including information about an item group and second information including information about an item included in the group, generating third information including the first information and the second information, and providing the third information to a controller, and an electronic device using the method.

With the development of electronic technology, e-commerce has become a part of shopping. Customers can buy items online without going to a shopping mall or market in person, and the items purchased online can be delivered to the destination requested by the customer.

On a page for providing information about an item for sale online, various methods may be used to promote a customer to purchase an item. Such methods for promoting item purchases may include a method of providing benefits based on item purchases or a method of suggesting the purchase of an item related to an item that the user is interested in or requests to purchase.

Related items can be managed as a group based on a benefit of purchasing an item or a correlation between other items. To this end, a method for classifying items into groups and managing the groups can be proposed.

In this regard, reference may be made to previous documents such as KR20130033506A, KR101506374B1 and the like.

[Technical objectives]

One aspect provides a method for obtaining first information including information about a group for grouping a plurality of items, obtaining second information including item information about a main item included in the group and a group of accessory items grouped together with the main item, generating third information including the first information and the second information, and providing the third information to a controller of an electronic device, and an electronic device using the method.

However, the objectives to be achieved by the exemplary embodiments of the present invention are not limited to the above-mentioned technical aspects, but other objectives can be inferred from the following exemplary embodiments. [Technical Solution]

According to one aspect, a method for providing item information in a first database is provided, the method comprising: obtaining first information comprising information about a group for grouping a plurality of items; obtaining second information comprising item information about a main item included in the group and a group of accessory items grouped together with the main item; generating third information comprising the first information and the second information; and providing the third information to a controller of an electronic device, wherein based on the third information, a page comprising information associated with at least a portion of the main item and the group of accessory items is provided in the controller.

The first information may include a first table including the information about the group and the second information may include a second table including the item information.

Generating the third information may include: generating a third table based on the first table included in the first information and the second table included in the second information; and generating the third information based on the third table.

At least one of the first information and the second information may be received from a second database corresponding to a relational database (RDB) in which a relationship between a key and a value is stored in the form of a table.

The first database may be a scalable non-SQL (NoSQL) database.

The method may further include obtaining inventory information about at least a portion of the main item and the set of subsidiary items based on at least one of the first information and the second information.

The method may further include providing the inventory information to the controller, and may further provide the page in the controller based on the inventory information.

The method may further include: obtaining priority information of a plurality of accessory items included in the accessory item set based on the inventory information; and providing the priority information to the controller. In the controller, a representative accessory item may be selected from the plurality of accessory items based on the priority information and the page may be provided based on the selected representative accessory item.

The page may be provided in response to receiving a user input from a user related to the primary item.

The user input may include at least one of: a search input related to the main item, an add input for adding the main item to a shopping cart, a purchase request input for the main item, and a payment input for an item price of the main item.

The method may further include: obtaining detailed information associated with the main item and the set of attached items; and providing the detailed information to the controller. The detailed information includes at least one of the following: item name information corresponding to the main item and the set of attached items, item price information corresponding to the main item and the set of attached items, image information corresponding to the main item and the set of attached items, and benefit information about the main item.

The benefit information includes at least one of the following: price discount information associated with the main item and the accessory item group, a condition for applying the price discount information, and limit information of a price discount applicable to the main item.

According to another aspect, an electronic device for providing item information is also provided, the electronic device comprising: a first database configured to obtain first information comprising information about a group for grouping a plurality of items, obtain second information comprising item information about a main item included in the group and a group of accessory items grouped together with the main item, generate third information comprising the first information and the second information, and provide the third information to a controller of the electronic device; and a controller configured to provide a page comprising information associated with at least a portion of the main item and the group of accessory items based on the third information.

Details of other exemplary embodiments are included in the following detailed description and accompanying drawings. [Effect]

According to an exemplary embodiment, an electronic device for providing item information and a method thereof can integrate item group information and item information and provide the integrated information to a controller, thereby efficiently managing item-related information and, in particular, efficiently managing item-related welfare information. In addition, according to an exemplary embodiment, the scalability of stored information can be ensured by integrating item group information and item information in a relational database (RDB) and managing the integrated information in a non-SQL (NoSQL) database.

The effects of the present invention are not limited to the above effects and a person skilled in the art can understand other effects from the following description.

The terms used in the exemplary embodiments are selected from the currently widely used general terms as much as possible, while considering the functions realized according to the present invention, but these terms can be replaced by other terms based on the intention of skilled persons, conventions, the emergence of new technologies or the like. In addition, in a specific case, the terms arbitrarily selected by the applicant of the present invention can be used. In this case, the meanings of these terms can be described in the corresponding description part of the present invention. Therefore, it should be noted that the terms used in this article should be interpreted based on their actual meanings and the overall content of this specification, rather than just based on the names of the terms.

Throughout the specification, when an element is referred to as "including" or "comprising" another element, as long as there is no special contradictory description, the element should not be understood to exclude other elements, and the element may include at least one other element. In addition, for example, the terms "component" and "module" may refer to a component that applies at least one function or operation and can be implemented in hardware or software or can be implemented by a combination of hardware and software.

Throughout the specification, the expression “at least one of a, b, and c” may include “only a,” “only b,” “only c,” “a and b,” “a and c,” “b and c,” or “all of a, b, and c.”

In the present invention, a "terminal" may be implemented as a computer or a portable terminal capable of accessing a server or another terminal through a network. Here, the computer may include, for example, a laptop, a desktop, and a notebook equipped with a web browser. The portable terminal may be a wireless communication device that ensures portability and mobility, and includes any type of handheld wireless communication device, such as a tablet PC, a smart phone, a communication-based terminal such as International Mobile Telecommunications (IMT), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (W-CDMA), and Long Term Evolution (LTE).

In the following description, exemplary embodiments of the present invention will be described in detail with reference to the drawings so that a person skilled in the art can easily implement the present invention. The present invention can be embodied in many different forms and is not limited to the embodiments described herein.

Hereinafter, exemplary embodiments of the present invention will be described with reference to the drawings.

When describing the exemplary embodiments, the description of the technical contents that are well known in the art to which the present invention belongs and are not directly related to the present invention will be omitted. This is to convey more clearly and not make the subject of the present specification unclear by omitting unnecessary descriptions.

For the same reason, some components are enlarged, omitted or schematically shown in the drawings. In addition, the size of each component does not fully reflect the actual size. The same or corresponding components in each figure are given the same element symbol.

The advantages and features of the present invention and its implementation methods will be understood from the following exemplary embodiments, which will be described in more detail with reference to the accompanying drawings. However, it should be noted that the present invention is not limited to the following exemplary embodiments, but can be implemented in various forms. Therefore, the exemplary embodiments are only provided to disclose the present invention and to make those skilled in the art aware of the category of the present invention. In the drawings, the exemplary embodiments of the present invention are not limited to the specific examples provided herein and are enlarged for clarity. The same element symbols or the same reference indicators mark the same elements in this specification.

At this point, it should be understood that each block of the flowchart and flowchart combination can be executed by computer program instructions. Since these computer program instructions can be installed on a processor of a general-purpose computer, special-purpose computer or other programmable data processing device, the instructions executed by the processor of the computer or other programmable data processing device can produce a component for performing the functions described in the (several) flowchart blocks. These computer program instructions can be stored in a computer-usable or computer-readable memory that can be targeted to a computer or other programmable data processing device to implement the functions in a specific manner and thus implement the computer-usable or computer-readable memory. The stored instructions can also produce an article of manufacture containing instruction components for performing the functions described in the (several) flowchart blocks. Computer program instructions may also be installed on a computer or other programmable data processing device so that a series of operating steps can be executed on the computer or other programmable data processing device to produce a computer-implemented program to produce a computer or other programmable data. Instructions for executing the processing device may also provide steps for executing the functions described in the flowchart block(s).

In addition, each block may represent a module, segment, or portion of code that includes one or more executable instructions for performing one (or more) specified logical functions. It should also be noted that in some alternative implementations, the functions mentioned in the blocks may occur out of order. For example, depending on the corresponding functions, two blocks shown in succession may actually be executed substantially simultaneously or the blocks may sometimes be executed in reverse order.

FIG. 1 is a block diagram illustrating an electronic device for providing item information according to an exemplary embodiment.

According to various exemplary embodiments, an electronic device 100 for providing item information includes a controller 110 and a first database 120. In addition, the electronic device 100 may further include a second database 130. In some cases, the electronic device 100 for providing item information may further include a network that supports data transmission and reception between at least a portion of the controller 110, the first database 120, the second database 130 and other external devices.

Meanwhile, even if the first database 120 and the second database 130 exist, at least some of the databases may exist as a separate device distinct from the electronic device 100 or be included in a separate device distinct from the electronic device 100 so as to exist in a form not included in the electronic device 100. However, even in this case, an item information providing method performed through data transmission and reception between the controller 110, the first database 120, and the second database 130 may be performed similarly or identically. Hereinafter, for ease and convenience, description is made based on the electronic device 100 including the first database 120 and the second database 130 according to an exemplary embodiment. The following description may also be applied to a case in which at least part of the first database 120 and the second database 130 are not included in the electronic device 100.

The controller 110 of the electronic device 100 may include a transceiver, a memory, and a processor. The first database 120 and the second database 130 may each include at least a portion of the transceiver, the memory, and the processor. In addition, each of the controller 110, the first database 120, and the second database 130 may be a unit that processes at least one function or operation, which may be implemented by hardware or software or a combination of hardware and software. At the same time, in all exemplary embodiments, the controller 110, the first database 120, and the second database 130 refer to separate devices or servers, but they may be logically divided structures and implemented as separate functions in a single server.

According to an exemplary embodiment, the controller 110, the first database 120, and the second database 130 may include a plurality of computer systems implemented as a network server or computer software. For example, at least a portion of the controller 110, the first database 120, and the second database 130 may refer to a computer system and computer software connected to a lower-level device, and the lower-level device can communicate with another network server through a computer network such as an intranet or the Internet to receive a request to execute a task, execute the task, and provide a result of the task. In addition, at least a portion of the controller 110, the first database 120, and the second database 130 can be understood as a broad concept including a series of applications that can operate on a network server and various databases built in the network server. At least part of the controller 110, the first database 120, and the second database 130 may be implemented using a network server program provided in various ways based on an operating system such as, for example, DOS, Windows, Linux, UNIX, or MacOS.

The electronic device 100 is a device for constructing and providing various information on a web page. The electronic device 100 may be a device for providing a user with product sales information and service provision information, but the function of the electronic device 100 is not limited thereto. At the same time, in all exemplary embodiments, a service may also refer to an item, providing a service may also refer to providing an item or selling an item, and a user may purchase an item through a service provided by the electronic device 100.

The controller 110 is a functional unit for controlling the electronic device 100. The controller 110 can read and interpret instructions and determine a sequence of data processing. The controller 110 provides a page containing information related to at least a part of the main item and the accessory item group based on information provided from the first database 120. The main item and the accessory item can be mutually related items.

Providing a page by the controller 110 may be interpreted as covering various operations of the user receiving the provided page. For example, an operation of the controller 110 providing a page may include an operation of the controller 110 outputting a page on a screen and the like by directly controlling an output device for providing information to the user, and may also include an operation of the controller 110 controlling the transceiver of the electronic device 100 to transmit data to provide the page to an external device such as a user terminal.

In some cases, the controller 110 may further provide the page based on information including at least one of benefit information associated with the main item and a result obtained by applying the benefit information associated with the main item to the main item and the set of subsidiary items.

The first database 120 may store data, and transmit and receive data to and from the controller 110 and the second database 130. Specifically, the first database 120 may obtain first information including information on a group for grouping a plurality of items and obtain second information including item information on a main item included in the group and an accessory item group grouped with the main item. For example, the first information and the second information may be received from the second database 130, but are not limited thereto.

In addition to transmission and reception, the first database 120 may further perform data processing, handling, generation, and calculation based on data. Specifically, the first database 120 may generate third information including the first information and the second information and provide the generated third information to the controller 110. The first database 120 may be a non-SQL (NoSQL) database that receives data from the second database 130 corresponding to a relational database (RDB), reconstructs the received data through data processing and handling, and stores the reconstructed data therein (the relevant content will be described in detail later). The first information may include a first table containing information about a group and the second information may include a second table containing item information. The first database 120 may generate a third table based on the first table and the second table and generate third information based on the third table.

According to an exemplary embodiment, the first database 120 may be a NoSQL database. In this case, the first database 120 may have relatively higher scalability than a relational database because the first database 120 uses a distributed hardware cluster and thus the capacity may be easily changed. In addition, the first database 120 may operate without a plan and thus there is no need to predefine a data structure. In addition, due to the flexible change of the data structure, the first database 120 may store informal data and achieve rapid development. Thus, the first database 120 may have the characteristics of a NoSQL database.

The second database 130 may store data, and transmit and receive data to and from the controller 110 and the first database 120. For example, the second database 130 may transmit first information and second information to the first database 120. According to an exemplary embodiment, the second database 130 may be an RDB in which a relationship between a key and a value is stored in the form of a table.

FIG. 2 illustrates an example 200 of an RDB. In an RDB, a set of data consisting of columns and rows is called a table. Each data constituting a table has a unique value. For example, in the data constituting a table, a horizontally grouped data set corresponds to a column and can be referred to as a tuple in the RDB. In addition, in the data constituting a table, a vertically grouped data set corresponds to a row and can be referred to as an attribute in the RDB. Furthermore, in an RDB, a table (which is a basic unit for distinguishing and storing information) can refer to a relationship. A set of attributes used to distinguish tuples can refer to a "key" (i.e., each column can have a unique key). Thus, a feature of an RDB can be that a set of data is stored as a table therein.

RDB has the advantages of being stable and ensuring data consistency. However, in RDB, a procedure for establishing a relationship between tables may be complicated, which may lead to performance degradation when inputting or searching a large amount of data. To prevent this, according to an exemplary embodiment of the present invention, the first database 120 may generate and store new information based on the data in the second database 130.

The operations of the controller 110, the first database 120, and the second database 130 will be described in more detail with reference to FIG. 3 and the like.

A series of operations associated with a method for processing information according to various exemplary embodiments may be implemented by a single physical device or may be implemented by a plurality of physical devices that are organically combined. For example, some components included in the electronic device 100 for providing item information may be implemented by one physical device, and the remaining components may be implemented as another physical device. For example, one physical device may be implemented as a part of the controller 110, and another physical device may be implemented as a part of the first database 120, a part of the second database 130, or a part of an external device. In some cases, the components included in the electronic device 100 for providing item information may be distributed and configured in different physical devices. Distributed components may be organically combined to perform the functions and operations of the electronic device 100 for providing item information. For example, the first database 120 of the present invention may include at least one sub-device. Some operations described as being performed by the first database 120 may be performed by a first sub-device, and some other operations may be performed by a second sub-device.

FIG. 3 is a flow chart illustrating a method of processing information in an electronic device for providing item information according to an exemplary embodiment.

3 , according to an exemplary embodiment, the first database 120 obtains first information including information about a group for grouping a plurality of items in operation 301 and obtains second information including item information about a main item and a group of subsidiary items grouped together with the main item in operation 302. The first information and the second information may be received from the second database 130.

In operation 303, the first database 120 generates third information based on the first information and the second information. When the first information and the second information are received from the second database 130 and when the second database is a relational database (RDB), the first information may include a first table containing information about the group and the second information may include a second table containing item information. In this case, the first database 120 may generate a third table based on the first table and the second table and generate the third information based on the third table. In other words, according to an exemplary embodiment, the third information may include an integrated table generated by integrating at least a portion of the contents of a plurality of tables.

Specifically, the first table may be Table 1 and the second table may be Table 2, as shown below. In this case, the third table according to an exemplary embodiment may be Table 3 (the last row of Table 1 and Table 2 corresponds to information used to help understand the description of each column and may not actually be included in the first table and the second table). [Table 1] OK Data Type index describe Id long Unique1 PK of the table used by the DBA requesterService varchar (32) Unique2 Mapped services requesterServiceProvidedId varchar (64) Unique2 ID provided by the requester as a reference ID requesterOwnerId varchar (64) The owner ID of the mapping group. According to an exemplary embodiment, this can be a vendor ID used to allow external systems to perform multiple logins. mapping Type varchar (32) Mapping type Ex) BUNDLE_PROMOTION, CONTRACT, RECOMMENDATION, RELATED_ITEM, INSURANCE, etc. Mapping Properties Word Map<String, String> to a string (e.g. a JSON string). By providing the mapping attribute to the CDS, the behavior can be changed at the front end or CSP. For example, determine whether part of a grouped item can be canceled (disablePartialCancellation→true/false), determine whether grouped items must be purchased together (mustBuyTogether→true/false), etc. priority int Mapping group priorities effectiveDate Timestamp Time associated with group activation expiryDate Timestamp Time associated with group termination status varchar (16) The status of the mapping group (available, deleted, etc.) createdAt Timestamp Time to generate the mapping createdBy Varchar (32) Generate mapping requester updatedAt Timestamp Update mapping time updatedBy varchar (32) Update Mapping Requester bidirectionalMapping int(1) A value indicating whether the mapping is performed unidirectionally (source to target) or bidirectionally (source to target and target to source) metadata Word Metadata Mapping [Table 2] OK Data Type index describe id long Table PK requesterService varchar (32) FK1 Requester Services requesterServiceProvidedId varchar (64) FK1 The ID provided by the requester in the service sourceItemId varchar (32) Idx1 ID of main item sourceItemType varchar (32) Idx1 Main item types targetItemId varchar (32) Idx2 Accessory ID targetItemType varchar (32) Idx2 Accessory Type status varchar (16) Idx1, Idx2 The status of the mapping (available, deleted, etc.) priority int Idx1, Idx2 Mapping priority [Table 3] Row Name Row Type source_item_id Text (PK) source_item_type Text (PK) mapping_type Text (CK) requester_service Text (CK) requester_service_provided_id Text (CK) effective_date Timestamp expiry_date Timestamp status Word title Word description Word priority int item_mappings Word mapping_properties map＜text, text＞ version bigint

According to an exemplary embodiment, in the third table, the source_item_id and source_item_type rows may be associated with the information contained in the second table, and the mapping_type row, the requester_service row, the requester_service_provided_id row, the effective_date row, the expiry_date row, the status row, and the priority row may be associated with the information contained in the first table.

In addition, according to an exemplary embodiment, the third table may include a portion of the information not included in the first table and the second table. For example, in the third table, the row title may include a title of a mapping group, the row description may include a description of the mapping group, the row mapping_properties may include additional properties for supporting specific business use cases, and the row version may include a version of a row for locking.

In addition, according to an exemplary embodiment, part of the information in the third table can be generated based on the first table and the second table. For example, the row item_mappings of the third table can include information about the mapping between a main item and an auxiliary item, which is generated based on the group information in the first table and the item information in the second table.

The information contained in the row item_mappings of the third table may be, for example, Table 4. [Table 4] [ { itemId: "1234", itemType: "VENDOR_ITEM", groupedItems: [ "1234", "1235", "1236" ] }, { itemId: "2345", itemType: "VENDOR_ITEM", groupedItems: [ "2343", "2344", "2345" ] }, { itemId: "5678" // VENDOR_ITEM without grouped items } ... ]

The information contained in the row item_mappings may include a main item and a group of accessory items mapped to the main item. For example, the information of Table 4 may include information indicating that a group including a main item corresponding to itemId "1234" includes accessory items corresponding to itemID "1235" and itemID "1236" and information indicating that a group including a main item corresponding to itemId "2345" includes accessory items corresponding to itemID "2343" and itemID "2344". An order in which multiple items contained in groupedItems are displayed may be determined based on a mapping priority, but this is only an example.

According to an exemplary embodiment, in order to reduce a burden of effective load, the information contained in the row item_mappings of the third table can be constructed as shown in Table 5. [Table 5] [ { itemId: "1234", itemType: "VENDOR_ITEM", groupId: "123", }, { itemId: "2345", groupId: "123", } { itemId: "5678" // VENDOR_ITEM without grouping } ... ]

According to an example of Table 5, information included in the row item_mappings may include a main item and a set of accessory items mapped to the main item. In this example, the accessory items may not be specified individually, and an item group further including the set of accessory items or the main item may be specified. For example, the information in Table 5 may include information indicating that an ID of a group including a main item corresponding to itemId "1234" is "123" and information indicating that an ID of a group corresponding to itemId "2345" is "234".

According to an exemplary embodiment, a priority of mapping between accessory items may be used to determine an accessory item displayed on a page provided in the controller 110 and may be used to determine a method of displaying the accessory item. For example, an accessory item grouped into a predetermined main item may include five accessory items, and a page provided in the controller 110 may display a representative accessory item and an additional accessory item. In this example, the page may be provided so that, among the five accessory items, an accessory item having a highest priority is displayed as a representative accessory item and an accessory item having a second highest priority is displayed as an additional accessory item.

For example, Table 2 corresponds to an example of the second information including a priority. However, the second table may not necessarily include the priority, and the priority may be directly set in the first database 120 based on at least a portion of the first information and the second information. Alternatively, even if the second information includes the priority, the priority may be verified and changed in the first database 120.

For example, the first database 120 may obtain inventory information about at least a portion of the main item and the accessory item group based on at least one of the first information and the second information and obtain priority information based on the obtained inventory information. For example, an accessory item grouped into a predetermined main item may include five accessory items, and among the five accessory items, an inventory quantity of an accessory item having a highest priority included in the second information may be less than a preset threshold value. In this example, the priority of the corresponding accessory item may be reset to be lower than the priority of at least one other accessory item determined to have a sufficient inventory quantity.

The first database 120 may provide priority information obtained based on the inventory information to the controller 110. The controller 110 may select a representative accessory item based on the received priority information and provide a page based on the selected representative accessory item.

In some cases, the first database 120 may perform selection of representative accessory items and provide the selected representative items together with priority information to the controller 110. In some cases, the first database 120 may determine a display order of accessory items including the representative accessory items and provide the determined display order to the controller 110 together with or in place of the priority information.

In contrast, in some cases, the first database 120 may obtain the inventory information without obtaining the priority information and provide the inventory information to the controller 110, so that the controller 110 provides a page based on the inventory information.

An example related to the third information will be described with reference to FIG. 5 .

In operation 304, the first database 120 may provide the generated third information to the controller 110. In operation 305, the controller 110 may provide a page including information associated with at least a portion of the main item and the set of attached items based on the third information. The page may be provided in response to a user input related to the main item being received from the user. That is, the main item may be an item corresponding to the user input. For example, the main item may be an item corresponding to a search input of the user, an item corresponding to an add to cart input of the user, an item corresponding to a purchase request input of the user, or an item corresponding to a payment input of an item price.

Ancillary items may include, but are not limited to, additional items and services related to the purchase of one of the primary items. For example, the primary item and the ancillary items may be related items, whether a hierarchy or a master-slave relationship. For example, when the primary item is chocolate milk, the ancillary items may include strawberry flavored milk, banana flavored milk, coffee flavored milk, and the like.

According to an exemplary embodiment, the first database 120 may obtain detailed information associated with the main item and the accessory item set and provide the obtained detailed information to the controller 110. In this case, the detailed information may be received from the second database 130, but it is only an example. In addition, the detailed information may be provided by being included in the third information. However, it is only an example, and the detailed information may also be provided as information separated from the third information.

The detailed information may include at least one of the following: item name information corresponding to the main item and the accessory item group, item price information corresponding to the main item and the accessory item group, image information corresponding to the main item and the accessory item group, and benefit information associated with the main item. For example, the detailed information may include information indicating that an item name of the main item is "Company A's PC", information indicating that the item price is 900,000 Korean Won, and information indicating that when the main item and the accessory item are purchased together, a 2% discount is applied to the main item for each accessory item purchased.

In an exemplary embodiment, the detailed information may include item ID information used in a service of the electronic device 100, item manufacturer information, manufacturing date information, serial number information (eg, serial number information is identification information used by a manufacturer), and the like.

The benefit information associated with the main item included in the detailed information may include at least one of the following: price discount information associated with the main item and the accessory item set, a condition for applying the price discount information, and a limit information for a price discount applicable to the main item. For example, the benefit information may include information indicating: i) a 10% discount is provided on the price of the main item and a 5% discount is provided on the price of the accessory item; ii) when the main item and the accessory item set are purchased together, the discount application condition is satisfied; iii) an upper limit of the discount price is 100,000 Korean Won.

When the controller 110 receives the detailed information, the controller 110 may provide a page including information associated with at least a portion of the main item and the accessory item set based on the detailed information.

In addition, according to an exemplary embodiment, at least one of inventory information, priority information, and representative accessory item information may be provided to the controller 110, as described above. The controller 110 may further provide a page containing information associated with at least a portion of the main item and the accessory item set based on the acquired inventory information, priority information, or representative accessory item information.

An example related to pages will be described with reference to FIG. 6 .

FIG. 4 is a diagram illustrating an example of a method of operating a database according to an exemplary embodiment.

FIG4 shows an example of a method of operating a database including a first database 120 and a second database 130 according to an exemplary embodiment. In the figure, an inter-satellite 403 is a function, component or device (hereinafter described as "function" for convenience of explanation) that handles data transmission and reception between a front end and a back end in a service and is specifically involved in providing services to a user at the front end, and can be understood as a function included in the controller 110 or a function that directly communicates with the controller 110.

A client 407 may include at least a portion of Backoffice, RCC, Supplier Hub, and Wing, but is not limited thereto. The client 407 may include various entities that provide raw data for page layout of the controller 110. The client 407 may provide information to the product_bundle_web 406. The corresponding information may be converted into a standard data structure in the product_bundle_web 406 and transmitted to the product_bundle_api 404. Thereafter, the product_bundle_api 404 may transmit the information received from the product_bundle_web 406 to the welfare layer 401. The information received in the welfare layer 401 may include at least a portion of the first information and the second information. Alternatively, the welfare layer 401 may obtain at least a portion of the first information and the second information based on the received information.

A CDS 402 is a database corresponding to the first database 120. The CDS 402 can obtain the first information and the second information, generate the third information based on the first information and the second information, and transmit the generated third information to the interstellar 403. The welfare layer 401 is a database corresponding to the second database 130 and can transmit the first information and the second information to the CDS 402. For example, an information movement path includes product_bundle_api 404, and specifically, can include at least a part of a Datasource part, a CRUD operation part, a Queue producer part, a Kafka-bnp connection part, and a Queue consumer part.

A PMS 405 may be a database containing benefit information about a plurality of items corresponding to a service provided by the electronic device 100 and group information of the items. In addition, based on a request transmitted from the interstellar 403, the PMS 405 may calculate benefits applied to items selected by a user and provide the calculated benefits to the interstellar 403. For example, the PMS 405 may receive detailed information about an item from the interstellar 403 and perform a calculation based on the received detailed information, or perform a calculation based on the group information and the benefit information without using detailed information about an individual item. Alternatively, detailed information about an item may be stored in the PMS 405. In this case, PMS 405 may not receive detailed information of each item from Interstellar 403.

According to an exemplary embodiment, when PMS 405 receives detailed information about an item from interstellar 403, the detailed information transmitted by interstellar 403 may correspond to the detailed information provided by first database 120.

FIG5 is a diagram illustrating an example of third information according to an exemplary embodiment.

FIG. 5 illustrates an example 500 of at least a portion of the third information according to an exemplary embodiment. The first database 120 is a NoSQL database and may not necessarily include information in the form of a table. For ease and convenience, the following description is based on an example in which the first database 120 generates a third table based on a first table and a second table.

According to an exemplary embodiment, a third table included in the third information may include at least a portion of the following: a service request entity 501 (e.g., requester_service), a service request ID 502 (e.g., requester_servie_provided_id), a main item ID 503 (e.g., source_item_id), a main item type 504 (e.g., source_item_type), a mapping type 505 (e.g., mapping_type), and accessory item set information 506 (e.g., item_mappings) of an accessory item set mapped to a main item. For example, the service request ID 502 may be an ID generated for each request of the first database 120 or an ID received from the second database 130 or the controller 110. In addition, the accessory item set information 506 of the accessory item set mapped to the main item may include at least one of an accessory item ID and an accessory item type. In addition, according to an exemplary embodiment, the main item type 504 or the accessory item type may be a value for verifying whether a corresponding item is an item sold by an individual seller or an item directly sold by a service provider, but is not limited thereto. In addition, according to an exemplary embodiment, the mapping type 505 may be a value for classifying benefit information provided with respect to a group or main item and may include group item purchase related benefit information (BUNDLE_PROMOTION), insurance purchase related benefit information (CE_INSURANCE), and subsidy payment related benefit information (SUBSIDY_PROMOTION), but it is only an example. The mapping type 505 is not limited to a value for classifying benefit information provided with respect to a group or main item.

FIG. 6 is a diagram illustrating an example of a page provided in a controller based on third information according to an exemplary embodiment.

FIG6 shows an example 600 of a page provided in the controller 110 according to an exemplary embodiment. The page may include main item information 602 and accessory item information about accessory items grouped together with a main item, indicated by reference numerals 603 and 604. The main item information and the accessory item information may include at least one of item name information, item price information, image information corresponding to an item, and benefit information about the main item. In addition, the page may include final order amount information to which benefit information is applied, indicated by reference numeral 605.

The page may display benefit information as well as accessory item information. For example, as indicated by element symbol 603, a text "Automatically apply 30,000 won set discount" may be displayed, and as indicated by element symbol 604, a text "Automatically apply 40,000 won set discount" may be displayed. This benefit information does not necessarily have to be displayed together with the accessory item information, but may be displayed as a separate text or image. In addition, such discount benefits may not necessarily be added to the accessory items, and a discount may be applied to the main item when one of the conditions for applying the benefit is met (such as purchasing the accessory item together).

As described above, the controller 110 may further provide a page including information associated with the main item and at least a portion of a group of accessory items based on the obtained inventory information, priority information, representative accessory item information, or the like. In example 600, one of the accessory items grouped with the main item (e.g., an FHD IPS monitor) having a highest priority is a wired keyboard. One of the accessory items having a high priority is a monitor cable and thus the wired keyboard may be displayed first, as indicated by element symbol 603. In addition, as indicated by element symbol 604, the monitor cable may be displayed below it.

FIG. 7 is a flow chart illustrating a method of processing information in a first database according to an exemplary embodiment.

7 , according to an exemplary embodiment, the first database 120 obtains first information including information about a group for grouping a plurality of items in operation 710 and obtains second information including item information about a main item included in the group and a subsidiary item grouped together with the main item in operation 720.

In operation 730, the first database 120 generates third information based on the first information and the second information. In operation 740, the first database 120 provides the generated third information to the controller 110. The controller 110 may provide a page including information associated with at least a portion of the main item and the accessory item set based on the third information.

FIG8 is a block diagram illustrating an example of a first database according to an example embodiment.

8 , the first database 120 includes a transceiver 810, a processor 820, and a memory 830. The first database 120 is connected to the controller 110, the second database 130, and other external devices through the transceiver 810 to perform data exchange.

The processor 820 may include at least one of the devices described above with reference to Figures 1 to 7, or may execute at least one of the methods described above with reference to Figures 1 to 7. The memory 830 may store information for executing at least one of the methods described above with reference to Figures 1 to 7. The memory 830 may be a volatile memory or a non-volatile memory.

The processor 820 may execute a program and control the controller 110 to provide information. The program code executed by the processor 820 may be stored in the memory 830.

Additionally, in an exemplary embodiment, the controller 110 may further include an interface for providing information to a user.

This specification and drawings have been described with respect to exemplary embodiments of the present invention. Although specific terms are used, they are only used in a general sense to easily explain the technical content of the present invention and help understand the present invention, and are not intended to limit the scope of this specification. Those skilled in the art will understand that in addition to the embodiments disclosed herein, other modifications based on the technical spirit of the present invention may also be implemented.

The electronic device or terminal according to the above embodiment may include a processor, a memory for storing and executing program data, a permanent storage such as a disk drive, a communication port for communicating with an external device, and a user interface device such as a touch screen, a key and a button. The method implemented by the software module or algorithm can be stored in a computer-readable recording medium as a computer-readable code or program command that can be executed by the processor. Here, the computer readable recording medium may be a magnetic storage medium (e.g., a read-only memory (ROM), a random access memory (RAM), a floppy disk, or a hard disk) or an optical readable medium (e.g., a CD-ROM or a digital versatile disc (DVD)). The computer readable recording medium may be distributed to computer systems connected via a network so that the computer readable code may be stored and executed in a distributed manner. The medium may be read by a computer, may be stored in a memory, and may be executed by a processor.

Embodiments of the present invention may be represented by functional blocks and various processing steps. Such functional blocks may be implemented by various hardware and/or software configurations that perform specific functions. For example, embodiments of the present invention may employ a through circuit configuration that can perform various functions by controlling one or more microprocessors or other control devices, such as a memory, a processor, a logic circuit, and a lookup table. Similar to components that can be executed by software programming or software components, embodiments of the present invention may be implemented by programming or script languages such as C, C++, Java, and assembly languages, which include various algorithms implemented by a combination of data structures, procedures, routines, or other programming configurations. Functional aspects may be implemented by algorithms executed by one or more processors. In addition, embodiments of the present invention may employ related technologies for, for example, electronic environment settings, signal processing, and/or data processing. The terms "mechanism", "component", "component" and "configuration" may be used broadly and are not limited to mechanical and physical components. These terms may include the meaning of a series of software routines associated with, for example, a processor.

The above embodiments are examples only and other embodiments may be implemented within the scope of the following claims.

100: electronic equipment 110: controller 120: first database 130: second database 200: instance 301: operation 302: operation 303: operation 304: operation 305: operation 401: welfare layer 402: CDS 403: interstellar 404: product_bundle_api 405: PMS 406: product_bundle_web 407: client 500: instance 501: service request entity 502: service request ID 503: main item ID 504: main item type 505: mapping type 506: accessory item group information 600: instance 601: Discounted items purchased according to settings 602: Main item information 603: Accessory item information 604: Accessory item information 605: Final order amount information 710: Operation 720: Operation 730: Operation 740: Operation 810: Transceiver 820: Processor 830: Memory

FIG. 1 is a block diagram illustrating an electronic device for providing information about an item according to an exemplary embodiment.

FIG. 2 is a diagram illustrating an example of a relational database (RDB) according to an example embodiment.

FIG. 3 is a flow chart illustrating a method of processing information in an electronic device for providing item information according to an exemplary embodiment.

FIG. 4 is a diagram illustrating an example of a method of operating a database according to an exemplary embodiment.

FIG5 is a diagram illustrating an example of third information according to an exemplary embodiment.

FIG. 6 is a diagram illustrating an example of a page provided in a controller based on third information according to an exemplary embodiment.

FIG. 7 is a flow chart illustrating a method of processing information in a first database according to an exemplary embodiment.

FIG8 is a block diagram illustrating an example of a first database according to an example embodiment.

110: Controller

120: First database

130: Second database

301: Operation

302: Operation

303: Operation

304: Operation

305: Operation

Claims (8)

A method for providing item information contained in a first database of an electronic device, the method comprising: obtaining first information including a first table from a second database through the first database, the first table including information about a group for grouping a plurality of items; obtaining second information including a second table from the second database through the first database, the second table including item information about a main item contained in the group and a group of accessory items grouped together with the main item; generating a third table through the first database based on the first table and the second table; and providing third information including the third table to a controller of the electronic device through the first database, wherein the first database is a scalable non-SQL (NoSQL) database, and the second database is a relational database (RDB) in which a key and a value are associated with each other. The relationship between the main item and the accessory item group is stored in the form of a table, and based on the third information, a page containing information associated with at least a part of the main item and the accessory item group is provided in the controller, wherein generating the third table includes: based on the information of the group contained in the first table and the item information contained in the second table, the ID of the main item and the IDs of the multiple accessory items contained in the accessory item group are listed by the first database, wherein an order of listing the multiple IDs of the accessory items is determined based on the priority information contained in at least one of the first table and the second table and the inventory information contained in at least one of the first table and the second table, and at least one accessory item displayed on the page is determined based on the order of listing the IDs of the multiple accessory items and a method of displaying the at least one accessory item. The method of claim 1, wherein in the controller, a representative accessory item is selected from the plurality of accessory items based on the order in which the IDs of the plurality of accessory items are listed, and the page is provided based on the selected representative accessory item. The method of claim 1, wherein the page is provided in response to receiving a user input related to the primary item from a user. The method of claim 3, wherein the user input includes at least one of the following: a search input related to the main item, an add input for adding the main item to a shopping cart, a purchase request input for the main item, and a payment input for an item price of the main item. The method of claim 1 further comprises: obtaining detailed information associated with the main item and the accessory item group through the first database; and providing the detailed information to the controller through the first database, wherein the detailed information includes at least one of the following: item name information corresponding to the main item and the accessory item group, item price information corresponding to the main item and the accessory item group, image information corresponding to the main item and the accessory item group, and benefit information about the main item. The method of claim 5, wherein the benefit information includes at least one of the following: price discount information associated with the main item and the set of ancillary items; a condition for applying the price discount information; and limit information for a price discount applicable to the main item. A non-transitory computer-readable recording medium comprising a computer program for executing a method as claimed in claim 1. An electronic device for providing item information, the electronic device comprising: a first database configured to obtain first information including a first table from a second database, the first table including information about a group for grouping a plurality of items, obtain second information including a second table from the second database, the second table including item information about a main item included in the group and a group of subsidiary items grouped with the main item, generate a third table based on the first table and the second table; and provide third information including the third table to a controller of the electronic device; wherein the first database is a scalable non-SQL (NoSQL) database, and the second database is a relational database (RDB), wherein a relationship between a key and a value is stored in the form of a table; and the controller is configured to provide a page containing information associated with at least a portion of the main item and the accessory item group based on the third information, wherein generating the third table includes: Based on the information of the group contained in the first table and the item information contained in the second table, the ID of the main item and the IDs of the plurality of accessory items contained in the accessory item group are listed by the first database, wherein an order of listing the plurality of accessory item IDs is determined based on priority information contained in at least one of the first table and the second table and inventory information contained in at least one of the first table and the second table, and at least one accessory item displayed on the page and a method of displaying the at least one accessory item are determined based on the order of listing the plurality of accessory item IDs.