KR20220115547A - Story product service management server and serving method of story product - Google Patents

Abstract

A story product service-providing method according to an embodiment of the present invention comprises the steps of: accessing a story product service server through a user device; receiving a selection input for one of story products; receiving order information for the selected story product; issuing a unique code and certificate for the selected story product; paying for the selected story product and setting a password corresponding to the unique code; progressing a story product service for the selected story product; confirming completion of the story product service; and delivering the selected story product, wherein the story product service includes transmitting a designated number of designated questions from the story product service server to the user device based on a specified time interval, and the story product service may be completed when an answer to the last question among the designated questions is received. A purchaser can assign various meanings and values to products to be manufactured and store the meanings and values.

Description

STORY PRODUCT SERVICE MANAGEMENT SERVER AND SERVING METHOD OF STORY PRODUCT

The present invention relates to a product sales method, and more particularly, to a story product service management server and a story product service method.

Products produced in the traditional way are unilaterally priced according to the intentions, ideas, and philosophies of manufacturers, designers, artists, etc., and the buyer understands the meaning and purchases. However, in modern society, through the development of high-speed communication, changes in storage methods such as cloud storage methods, and the development of encryption technologies such as block chains, it has become an era in which various values such as digital works can be purchased and given meaning. However, the price of manufactured goods is still determined simply by the materials of the goods and the cost of manufacturing the goods.

Republic of Korea Patent Publication No. 10-2013527 (2019-08-16)

The present invention is to solve the above problems, and an object of the present invention is to give a unique recognition symbol to the product to be manufactured, and the purchaser can give and store various meanings and values to the product to be manufactured and a story product service management server and to provide a story product service method.

A story product service providing method according to an embodiment of the present invention includes the steps of accessing a story product service management server through a user device; receiving a selection input for one of the story products; receiving order information for the selected story product; issuing a unique code and certificate for the selected story product; performing payment for the selected story product and setting a password corresponding to the unique code; performing a story product service for the selected story product; confirming completion of the story product service; and delivering the selected story product, wherein the story product service includes sending a specified number of specified questions based on a specified time interval from the story product service management server to the user device, wherein the story product service includes: The service may be completed when an answer to the last question among the specified questions is received.

In addition, the unique code may include at least one of a combination of letters or numbers, a barcode or a QR code, and may be displayed, attached, or engraved on a part of the selected story product.

In addition, when the unique code and the password are received through the user device, the story product service may be provided.

The story product service management server according to an embodiment of the present invention includes: a communication unit for receiving member information and order information for a story product selected from among the story products from a user device; a storage unit for storing the member information and the order information input through the communication unit; and a controller for issuing a unique code and a certificate based on the order information stored in the storage unit, receiving a password corresponding to the unique code from the user device, and storing the password in the storage unit. When the unique code and the password are received through the user device, the control unit provides a story product service that transmits a specified number of questions from the story product service server to the user device based on a specified time interval based on a specified time interval, , when an answer to the last question among the specified questions is received and the story product service is completed, the selected story product may be set to be delivered.

According to the present invention, the purchaser can give and store various meanings and values to the article to be manufactured.

1 is a configuration diagram exemplarily showing a story product service management system according to an embodiment of the present invention.
FIG. 2 is a block diagram for exemplarily explaining the story product service management system shown in FIG. 1 .
FIG. 3 is a block diagram exemplarily showing the first user device shown in FIG. 2 .
4 is a block diagram exemplarily showing the story product service management server shown in FIG. 2 .
FIG. 5 is a flowchart for exemplarily explaining a member registration and authentication method among operations of the member information management unit shown in FIG. 4 .
FIG. 6 is a flowchart illustrating an operation method of the application management unit illustrated in FIG. 4 .
7 is a flowchart illustrating a method of providing a story product service according to an exemplary embodiment.
8 is a diagram illustrating a story product selection screen according to an exemplary embodiment.
9 is a diagram illustrating an order information input screen according to an exemplary embodiment.
10 is a diagram illustrating a certificate confirmation screen according to an embodiment.
11 is a diagram illustrating a payment information input screen according to an exemplary embodiment.
12 is a diagram illustrating a user authentication information input screen according to an exemplary embodiment.
13 is a flowchart illustrating a method of performing a story product service according to an embodiment.
14 is a diagram illustrating an initial screen of a story product service according to an exemplary embodiment.
15 is a diagram illustrating a unique code recognition screen of a story product service according to an embodiment.
16 is a diagram illustrating a story product login screen according to an exemplary embodiment.
17 is a diagram illustrating an example of a story product service according to an embodiment.
18 is a diagram illustrating another example of a story product service according to an embodiment.
19 is a diagram illustrating another example of a story product service according to an embodiment.
20 is a diagram illustrating a certificate of a story product service according to an embodiment.
21 is a diagram illustrating another example of a story product service according to an embodiment.
22 is a diagram illustrating another example of a story product service according to an embodiment.

Hereinafter, embodiments of the present invention will be described clearly and in detail to the extent that those skilled in the art can easily practice the present invention.

1 is a configuration diagram exemplarily showing a story product service management system according to an embodiment of the present invention. Referring to FIG. 1 , a story product service management system 1000 may include first and second user devices 1100 and 1200 and a story product service management server 2000 .

The user may access the story product service management server 2000 using the first and second user devices 1100 and 1200 . Here, the first user device 1100 may be an APP-based device such as a smart phone or a tablet PC, and the second user device 1200 may be a web-based device such as a laptop PC or a desktop PC. . The first and second user devices 1100 and 1200 and the story product service management server 2000 may communicate by wire or wirelessly. By accessing the story product service management server 2000 using the first or second user device 1100 or 1200, the user obtains the story product information provided by the operator of the story product service management server 2000, or product service can be provided.

FIG. 2 is a block diagram for exemplarily explaining the story product service management system shown in FIG. 1 . Referring to FIG. 2 , the story product service management system 1000 may include a first user device 1100 , a second user device 1200 , and a story product service management server 2000 . The first user device 1100 may be a smart phone, and the second user device 1200 may be a desktop PC. For example, the first user device 1100 may be an APP-based terminal, and the second user device 1200 may be a web-based terminal.

The first and second user devices 1100 and 1200 may be connected to each other through a communication network. Also, each of the first and second user devices 1100 and 1200 may be connected to the story product service management server 2000 through a communication network. The first and second user devices 1100 and 1200 may transmit data for a story product service to the story product service management server 2000 or receive data from the story product service management server 2000 . The first and second user devices 1100 and 1200 may receive information provided by the user through the story product service program, and provide the story product service to the user.

The first user device 1100 may include a screen unit 1110 and a driving unit 1120 . The driving unit 1120 of the first user device 1100 may execute a story product service application. Similarly, the driving unit 1220 of the second user device 1200 may provide a story product service on the screen unit 1210 using a web service such as a homepage. The first and second user devices 1100 and 1200 may include hardware or software for running a story product service application or a web service.

Continuing to refer to FIG. 2 , the story product service management server 2000 may include a communication unit 2100 , a storage unit 2200 , and a control unit 2300 . The story product service management server 2000 stores the data input from the first and second user devices 1100 and 1200, calculates the story product data desired by the user from the stored data, and uses the calculated data for the first and second 2 may be transmitted to the user devices 1100 and 1200 .

The communication unit 2100 may receive member information, authentication information, or story information from the first and second user devices 1100 and 1200 . To this end, the communication unit 2100 is, for example, a 3G module, an LTE module, an LTE-A module, a Wi-Fi module, a WiGig module, an Ultra Wide Band (UWB) module, or a long-distance network such as a LAN card. It may include interfaces. In addition, the communication unit 2100 includes a short-distance network interface such as a Magnetic Secure Transmission (MST) module, a Bluetooth module, an NFC module, an RFID module, a ZigBee module, a Z-Wave module, or an infrared module. can do.

The communication unit 2100 may receive member information from the first and second user devices 1100 and 1200 . The communication unit 2100 may approve or block membership registration under the control of the control unit 2300 . In addition, the communication unit 2100 may approve, block, or limit the use of the story product service according to member information upon login. The communication unit 2100 may provide member information to the storage unit 2200 .

The storage unit 2200 may store member information, product information, story information, certificate information, cost information, etc. necessary for managing the story product service. Member information may be classified into service users and service operators according to users of the first and second user devices 1100 and 1200 and stored. The product information may be classified and stored into a first product and a second product according to products sold in the story product service. The story information may include a user's story written in response to the story product. The certificate information may include information about the story product and the story product service ordered by the user. The cost information may include a price of a story product, and the like.

The controller 2300 may control each component included in the story product service management server 2000 and operations of the story product service management server 2000 . The controller 2300 may provide various story product services to the user. The control unit 2300 provides the story product service of the story product service management server 2000 using member information, product information, story information, certificate information, and cost information received from the first and second user devices 1100 and 1200 . can be done Also, the controller 2300 may perform an operation of managing and updating member information and story product data. To this end, the control unit 2300 may include a central processing unit (CPU), a graphic processing unit (GPU), a micro controller unit (MCU), or a microprocessor. can

FIG. 3 is a block diagram exemplarily showing the first user device shown in FIG. 2 . 3 , a smart phone is illustrated as an example. Referring to FIG. 3 , the first user device 1100 includes a screen unit 1110 , a wireless communication unit 1111 , an input/output interface unit 1112 , an operating system 1113 , a story product service application 1114 , and a memory ( 1115) may be included. Hereinafter, although the first user device 1100 will be mainly described, the second user device 1200 may also provide a story product service through a web-based story product service program in a similar manner.

The wireless communication unit 1111 allows the first user device 1100 to wirelessly connect with the story product service management server (refer to FIG. 2 , 2000). Also, the first user device 1100 may exchange data with an external device such as the second user device 1200 or the story product service management server 2000 through the wireless communication unit 1111 . The wireless communication unit 1111 may include a wireless Internet module such as a 3G module, an LTE module, an LTE-A module, and a Wi-Fi module.

The input/output interface 1112 may be used to input letters or numbers to the first user device 1100 or to provide content to a user. The input/output interface unit 1112 may be connected to an internal input device such as an on-screen keyboard or an external input device (eg, a keyboard or an electronic pen) using wired or Bluetooth. Also, the input/output interface unit 1112 may be connected to an internal output device such as the screen unit 1110 or an external output device (eg, a monitor or a printer) using wired or Bluetooth.

The operating system 1113 may provide an environment in which the story product service application 1114 may be executed. The story product service application 1114 may provide a user interface (UI) for setting and managing service use through a user's membership registration or login. In addition, the story product service application 1114 may provide a user interface through which the first user device 1100 can access the story product service management server 2000 to exchange story product data. The story product service application 1114 may transmit and receive data through the input/output interface 1112 and the operating system 1113 .

The memory 1115 may store member information (eg, a user ID or password, etc.) of a user who uses the story product service application 1114 . The memory 1115 may store not only a password, but also a program such as an operating system 1113 or a story product service application 1114 .

4 is a block diagram exemplarily showing the story product service management server shown in FIG. 2 . Referring to FIG. 4 , the story product service management server 2000 may include a communication unit 2100 , a storage unit 2200 , and a control unit 2300 . The story product service management server 2000 receives user data from the first and second user devices 1100 and 1200, calculates the story product data desired by the user in response to the information request, and provides the calculated data to the user can do.

The communication unit 2100 may include an input unit 2110 and an output unit 2120 . The input unit 2110 receives data related to member information, product information, story information, certificate information, and cost information from the first and second user devices 1100 and 1200 , and sends it to the storage unit 2200 or the control unit 2300 . data can be transmitted. When the story product service request is received from the first and second user devices 1100 and 1200 , the output unit 2120 directly obtains the story product data from the storage unit 2200 or the story product data through the control unit 2300 . can be calculated and provided to the user. The story product data may include product information purchased by the user, story information related to the purchased product, user page information in which the story is stored, or certificate information about the purchased product, and the like.

Storage unit 2200 stores the story product data received from the input unit 2110, member information DB (2210), product information DB (2220), story DB (2230), certificate DB (2240), and cost information DB (2250). The member information DB 2210 may store user information about service users and service operators according to users. The service user may use the story product service by using the first or second user device (refer to FIG. 2 , 1100 or 1200 ). A service user may sign up for membership as described in FIG. 5 . The service operator may be a service provider of the story product service. The service operator may be a server operating entity that manages the story product service management server 2000 . The product information DB 2220 may store information about story products (eg, rings, wallets, bags, shoes, etc.) provided by the story product service. The product information DB 2220 may store a product type, a product size, and a product color. Story information related to a story product purchased by the user may be stored in the story DB 2230 . Also, the story DB 2230 may store information on a service date and service method, and the like. In the service date and time, the time of using the story product service, such as when the service user purchases the story product, the date and start and end times of the story product service use, may be stored. The cost of the story product service may be determined according to the provision time and use time of the story product service. In the service method, a method by which the service user uses the story product service may be stored. As an example, the service method may include checking the service period of a story product, checking a certificate, accumulating time or recording a library. The certificate DB 2240 may store information related to a user-related unique code, a certificate, a user-specific page, and the like. The cost information DB 2250 may store information on story product price, service cost, service class, service score, payment method, and the like. In the service level, a general level or a premium level may be stored. The story product service management unit 2350 and the cost management unit 2370 allow the user to use the general story product service for free, or provide a premium service to the user who has paid a predetermined fee or accumulated a certain point to provide an advanced story product service. can make use of The payment method may store a method of using cash, card, or point payment when there is a cost for using the story product service.

The control unit 2300 includes a processor 2310, an application management unit 2320, a member information management unit 2330, a product information management unit 2340, a story product service management unit 2350, a certificate management unit 2360, and A cost management unit 2370 may be included. The controller 2300 may be implemented as hardware or software. For example, the processor 2310 is implemented in hardware, and the application management unit 2320, the member information management unit 2330, the product information management unit 2340, the story product service management unit 2350, the certificate management unit ( 2360), and the cost management unit 2370 may be implemented as an algorithm or software.

The processor 2310 may control the overall operation of the story product service management server 2000 . For example, the processor 2310 accesses the member information DB 2210, the product information DB 2220, the story DB 2230, the certificate DB 2240, and the cost information DB 2250 of the storage unit 2200. (access), and an algorithm or program constituting the member information management unit 2330, the product information management unit 2340, the story product service management unit 2350, the certificate management unit 2360, and the cost management unit 2370 By executing the command, the controller 2300 may be driven. In addition, the processor 2310 may include controllers, interfaces, a graphic engine, and the like for controlling various components of the story product service management server 2000 . The processor 2310 may be provided in the form of a system-on-chip (SoC), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or the like.

The application management unit 2320 may provide the story product service application 1114 to the first user device 1100 or cause the second user device 1200 to execute the story product service program. Alternatively, the application management unit 2320 may connect the first and second user devices 1100 and 1200 to the story product service web. The application management unit 2320 may receive story product data or provide a story product service from the story product service management server 2000 through the first and second user devices 1100 and 1200 . The application management unit 2320 may provide a user interface (UI) for providing or receiving story product data to the first and second user devices 1100 and 1200 .

The member information management unit 2330 may access the member information DB 2210 of the storage 2200 to manage member information. Here, the member information may be information about a service user, a service operator, and the like. When new member information is input through the first user device 1100 , the member information management unit 2330 assigns a new member ID and controls the member information DB 2210 to store the new member ID and name. can do. The member information management unit 2330 may update member information stored in the member information DB 2210 when information of an existing member is changed. The member information management unit 2330 may provide a comment or an online consultation means for smooth communication between a service operator of the story product service management server 2000 and a service user accessing the same. In addition, when the user (or service user) purchases a product, the member information management unit 2330 may give the user a unique code (eg, a combination of letters or numbers, a barcode, a QR code, etc.). The unique code can be matched one-to-one with the user (or purchaser).

The product information management unit 2340 may access the product information DB 2220 of the storage unit 2200 to manage products sold in the story product service. The product information management unit 2340 may update the product list stored in the product information DB 2220 when a product provided by the story product service is changed.

The story product service management unit 2350 may provide the story product service to the first and second user devices 1100 and 1200 . The story product service management unit 2350 may guide the time remaining until delivery according to the story product purchased by the user. The story product service management unit 2350 may store and update the user's story data input from the first and second user devices 1100 and 1200 in the story DB 2230 . The story product service management unit 2350 may provide story data stored in the story DB 2230 upon request from the first and second user devices 1100 and 1200 . The story product service management unit 2350 may guide the delivery process of the story product to the first and second user devices 1100 and 1200 upon completion of the story product service.

When a unique code is assigned to the first and second user devices 1100 and 1200 , the certificate management unit 2360 may issue a certificate corresponding to the unique code and store the issued certificate in the certificate DB 2240 . . The certificate management unit 2360 may provide the certificate stored in the certificate DB 2240 when there is a request from the first and second user devices 1100 and 1200 .

The cost management unit 2370 may manage cost information according to the story product service to be provided to the user. For example, the cost management unit 2370 may allow a user to use a general story product service for free, or a user who has paid a predetermined cost or accumulated certain points to use an advanced story product service through a premium service. . The cost management unit 2370 may access the cost information DB 2250 of the storage unit 2200 to manage product prices, service costs, payment methods, and the like. The cost management unit 2370 may store and manage data related to product prices, service costs, and payment methods in the cost information DB 2250 .

FIG. 5 is a flowchart for exemplarily explaining a member registration and authentication method among operations of the member information management unit shown in FIG. 4 . Referring to FIG. 5 , the member information management unit 2330 of the story product service management server 2000 may manage to register as a member through a self-authentication procedure.

In step S110 , a user (eg, a service user, etc.) may sign up for membership using the first user device 1100 or the second user device 1200 . The user may access the story product service management server 2000 or register as a member through the story product service application. The member information management unit 2330 may request personal information such as a user's name, date of birth, resident number, phone number, e-mail address, and the like, when registering for membership. In addition, the member information management unit 2330 may request the user's occupation, main work, interests, etc. in addition to personal information. The user may register as a member in a manner in response to a request provided by the member information management unit 2330 . Alternatively, the member information management unit 2330 may proceed with membership registration when the user requests a purchase. The member information management unit 2330 may assign a unique code to the first user device 1100 or the second user device 1200 when the user requests a purchase. The member information management unit 2330 may receive a password corresponding to the unique code from the first user device 1100 or the second user device 1200 . Later, the user may log in to the story product service management server 2000 by inputting a unique code and password.

In step S120 , the user may perform an identity authentication procedure using the first user device 1100 or the second user device 1200 . Identity authentication may be simply performed by a mechanical method of inputting personal information such as a user name, resident number, phone number, or the like, or may be performed through an authorized authentication method used in a bank or the like. In addition, user authentication may be performed through biometric authentication such as iris or fingerprint or electronic authentication such as mobile phone authentication.

In step S130, based on the authentication information input by the user, it may be determined whether the authentication is successful. The member information management unit 2330 may determine whether authentication succeeds by comparing the authentication information input by the user with the authentication information stored in the member information DB 2210 (eg, public authentication). If the identity authentication is successful, step S140 may be performed, and if it fails, step S132 may be performed.

In step S132, when authentication is not successful in step S130 (NO), the number of authentication failures may be determined. The member information management unit 2330 may determine whether the number of authentication failures of the user is repeated N times. If the number of authentication failures is not repeated N times, step S120 is performed. That is, the member information management unit 2330 may guide the user to perform the user authentication procedure again. However, if the number of authentication failures is repeated N times, step S134 is performed.

In step S134 , the member information management unit 2330 may guide authentication failure. When the user repeatedly fails to authenticate the user N times, the member information management unit 2330 may notify the user that the authentication has failed and end the identity authentication procedure. In this case, the user may request the operator of the story product service management server 2000 to perform user authentication again. Depending on the embodiment, the steps (S130, S132, and S134) of determining whether the authentication is successful may be omitted.

In step S140 , the member information management unit 2330 may provide the member ID to the user through the first user device 1100 or the second user device 1200 . The member ID may be used when using the story product service program. Member ID can be issued in the following order. Referring to the example of FIG. 5 , in step S141 , the user may access the story product service management server 2000 using the first user device 1100 or the second user device 1200 . In step S142, the member information management unit 2330 may request member information. The user may input member information (eg, e-mail address, etc.) using the first user device 1100 or the second user device 1200 . In step S143, the user may input a password. Here, the member information and the password may be the same information as the information input in the member registration step (S110). Alternatively, the member information management unit 2330 may log in through a unique code instead of a member ID. The member information management unit 2330 checks the unique code and password received through the first user device 1100 or the second user device 1200 to determine the Login can be approved.

FIG. 6 is a flowchart illustrating an operation method of the application management unit illustrated in FIG. 4 . Referring to FIG. 6 , the application management unit 2320 may provide a story product service application to the first user device 1100 or support to install and execute the story product service program through the second user device 1200 .

In step S210 , the application management unit 2320 may install or execute the story product service program in the first user device 1100 or the second user device 1200 . The story product service program can be stored and installed in the memory 1115 of the first user device 1100 through a removable storage medium (eg, USB or memory card) or by downloading from the story product service management server 2000. have. The story product service program may include authentication data for identity authentication described with reference to FIG. 5 .

In step S220 , the application management unit 2320 may determine whether the installation of the program is successful. If the installation of the program fails (NO), the application management unit 2320 may guide the program installation failure through the first user device 1100 or the second user device 1200 ( S225 ). If the program installation is successful (YES), the application management unit 2320 may perform step S230.

In step S230 , the application management unit 2320 may check whether the communication unit 2100 , the storage unit 2200 , and the control unit 2300 of the story product service management server 2000 operate normally. The application management unit 2320 allows the user to normally use the story product service application or the story product service program provided by the story product service management server 2000 by using the first user device 1100 or the second user device 1200 . You can check if you can.

In step S231 , the application management unit 2320 may check the operation of the communication unit 2100 of the story product service management server 2000 . First, the application management unit 2320 may check whether the story product service management server 2000 is smoothly connected to the first user device 1100 or the second user device 1200 .

In step S232 , the application management unit 2320 may check the operation of the storage unit 2200 of the story product service management server 2000 . The application management unit 2320 stores information received from the communication unit 2100 by the storage unit 2200, the member information DB 2210, the product information DB 2220, the story DB 2230, the certificate DB 2240, and the cost. It can be checked whether the information is normally stored in the DB 2250 .

In step S233 , the application management unit 2320 may check the operation of the control unit 2300 of the story product service management server 2000 . The application management unit 2320 determines whether the processor 2310 of the control unit 2300 operates normally, and determines whether the member information management unit 2330, the product information management unit 2340, the story product service management unit 2350, and the certificate management unit Operation 2360 and the cost management unit 2370 may be checked. The application management unit 2320 may check whether it operates according to the story product service program command.

7 is a flowchart illustrating a method of providing a story product service according to an exemplary embodiment. 8 is a diagram illustrating a story product selection screen according to an exemplary embodiment. 9 is a diagram illustrating an order information input screen according to an exemplary embodiment. 10 is a diagram illustrating a certificate confirmation screen according to an embodiment. 11 is a diagram illustrating a payment information input screen according to an exemplary embodiment. 12 is a diagram illustrating a user authentication information input screen according to an exemplary embodiment. Referring to FIG. 7 , a user may purchase a story product through the story product service management server 2000 and receive a story product service.

In step S310 , the first user device 1100 or the second user device 1200 may access the story product service management server 2000 using the story product service application, the story product service program, or the story product service web. That is, a user (or a service user, a purchaser) may access the story product service management server 2000 through the first user device 1100 or the second user device 1200 . For example, in step S310, the story product service program installation process of FIG. 6 may be performed together.

In step S320 , the story product service management server 2000 may receive a story product selection input. Referring to FIG. 8 , the story product service management server 2000 may provide the product selection screen 100 through the first user device 1100 or the second user device 1200 . The product selection screen 100 may display currently sold story products (eg, the first product 110 , the second product 120 , and the third product 130 ). The product selection screen 100 may display a name 111 , a price 112 , or a color 113 of the story product (eg, the first product 110 ). The user may select a desired product on the product selection screen 100 , and the first user device 1100 or the second user device 1200 may transmit a story product selection input to the story product service management server 2000 .

In step S330 , the story product service management server 2000 may receive order information. Referring to FIG. 9 , the story product service management server 2000 may provide the order information input screen 200 through the first user device 1100 or the second user device 1200 . The order information input screen 200 may include a size selection object 210 , a color selection object 220 , a user information object 230 , an additional information object 240 , or a certificate view object 250 . The user may select (or click) the size selection object 210 to select the size of the story product. The user may select (or click) the color selection object 220 to select the color of the story product. The user may select (or click) the user information object 230 to select a sender (eg, a gift recipient), a recipient (eg, a gift recipient), a relationship between a sender and a recipient, and the like. The user may select (or click) the additional information object 240 to select a gift purpose and a message to be delivered (eg, a dream to support). The user may check the certificate by selecting (or clicking) the certificate view object 250 . When the certificate view object 250 is selected, the story product service management server 2000 may perform step S340.

In step S340 , the story product service management server 2000 may provide certificate information. Referring to FIG. 10 , the story product service management server 2000 may provide a certificate confirmation screen 300 through the first user device 1100 or the second user device 1200 . The certificate confirmation screen 300 may include a certificate 310 , a unique code 320 , and a certificate information confirmation object 330 . The certificate 310 may include a user corresponding to the unique code 320 , a story product, a story product service period, and order details. When a user purchases a story product, the member information management unit 2330 may assign a unique code 320 to the corresponding user. The unique code 320 may be transmitted to the user through the first user device 1100 or the second user device 1200 or displayed (eg, attached or engraved) on a part of the purchased story product. The unique code 320 may be generated in the form of a combination of letters or numbers, a barcode, a QR code, and the like. When an input for the certificate information verification object 330 is received from the first user device 1100 or the second user device 1200 , the story product service management server 2000 may perform step S350 . For example, in steps S340 and S350, the membership registration procedure described in FIG. 5 may be performed together.

In step S350, the story product service management server 2000 may proceed with payment and identity authentication. Referring to FIG. 11 , the story product service management server 2000 may provide a payment information input screen 400a through the first user device 1100 or the second user device 1200 . The payment information input screen 400 may include order history confirmation information 410 and a delivery information input object 420 . The order history confirmation information 410 may display order details input through the first user device 1100 or the second user device 1200 in steps S320 to S340 . The user may input delivery information into the delivery information input object 420 through the first user device 1100 or the second user device 1200 . The delivery information input object 420 may include recipient information, a delivery address, and a delivery memo.

Referring to FIG. 12 , the story product service management server 2000 may provide the user authentication information input screen 400b through the first user device 1100 or the second user device 1200 . The user authentication information input screen 400b may include a user authentication object 430 , a password setting object 440 , and a payment object 450 . The identity authentication object 430 may include various agreement agreement objects and purchaser authentication objects. The user can perform user authentication through various authentication methods (eg, telecommunication company authentication, mobile phone text authentication, ARS authentication, etc.) by inputting (or clicking) into the purchaser authentication object. The user may set a password using the password setting object 440 . The password set through the password setting object 440 may be used later when logging in to the story product service using the unique code 320 . When an input for the payment object 450 is received from the first user device 1100 or the second user device 1200 , the story product service management server 2000 may perform step S360 .

In step S360 , the story product service management server 2000 may provide a story product service. For example, the story product service may provide a space for the user to register a story about the story product while the story product is being produced. A method of providing the story product service will be described in detail with reference to FIG. 13 .

In step S370 , the story product service management server 2000 may deliver the story product for which the story product service is completed to the user.

13 is a flowchart illustrating a method of performing a story product service according to an embodiment. 14 is a diagram illustrating an initial screen of a story product service according to an exemplary embodiment. 15 is a diagram illustrating a unique code recognition screen of a story product service according to an embodiment. 16 is a diagram illustrating a story product login screen according to an exemplary embodiment. 17 is a diagram illustrating an example of a story product service according to an embodiment. 18 is a diagram illustrating another example of a story product service according to an embodiment. 19 is a diagram illustrating another example of a story product service according to an embodiment. 20 is a diagram illustrating a certificate of a story product service according to an embodiment. 21 is a diagram illustrating another example of a story product service according to an embodiment. 22 is a diagram illustrating another example of a story product service according to an embodiment. Referring to FIG. 13 , the user may log in to the story product service management server 2000 through the first user device 1100 or the second user device 1200 to receive the story product service.

In step S410 , the story product service management server 2000 may provide the story product service through the first user device 1100 or the second user device 1200 . The user may log in to the story product service management server 2000 through the first user device 1100 or the second user device 1200 . Referring to FIG. 14 , the story product service management server 2000 may provide a unique code scan object 501 on the story product service initial screen 500a. Referring to FIG. 15 , when receiving an input for the unique code scan object 501 , the story product service management server 2000 may provide a unique code recognition screen 500b. The unique code recognition screen 500b may include a unique code scan box 511 , a scan object 512 , and a direct input object 513 . The user may scan the unique code displayed on the story product through the unique code scan box 511 (eg, using the camera of the first user device 1100 or the second user device 1200 ). The user may place the unique code displayed on the story product in the unique code scan box 511 , and touch (or click) the scan object 512 to scan the unique code. Alternatively, the user may directly input a unique code by touching (or clicking) the direct input object 513 . Referring to FIG. 16 , when an input for the scan object 512 or direct input object 513 of FIG. 15 is received, the story product service management server 2000 may provide a story product login screen 500c. have. The story product login screen 500c may include a unique number input object 521 , a user input object 522 , a password input object 523 , a login object 524 , and a cancellation object 525 . When the unique code is scanned in FIG. 15 , the unique number input object 521 may display the scanned unique code. When an input for the direct input object 513 is received in FIG. 15 , the user may directly input a unique code into the unique number input object 521 . The user input object 522 may include a sender or a recipient. The user may select one of the user input objects 522 . The user must input the password entered in FIG. 12 into the password input object 523 to complete the story product login. The user may touch (or click) the login object 524 to execute the story product login, or touch (or click) the cancel object 525 to cancel the story product login. Referring to FIG. 17 , the story product service management server 2000 may provide a story product service period screen 600 . The story product service period screen 600 may include a story product service period 610 and an invitation object 620 . Users can experience various story product services during the story product service period. The user may invite the recipient to experience the story product service together through the invitation object 620 .

In step S420 , the story product service management server 2000 may receive an input for the first story product service (eg, time accumulation). The story product service management server 2000 may receive an input of a user story for the story product. 18 and 19 , the story product service management server 2000 may provide screens 700a and 700b for the first story product service. In the first story product service, the story product service management server 2000 sends questions specified to the first user device 1100 or the second user device 1200 for a specified number of times (eg, 10 times) at a specified time interval (eg: 1 week, 2 weeks or 1 month). The user may store a story (eg, a memory or a story) about the story product in the story product service management server 2000 while answering specified questions. 18 may show an initial screen 700a of the first story product service. As an example, the initial screen 700a of the first story product service may include a specified number of times count object 701 and specified questions (eg, a first question 711 and a second question 712 ). 19 may show a completion screen 700b of the first story product service in which answers to specified questions have been completed. The completion screen 700b of the first story product service may display completed questions and answers (eg, a first question and answer 721 , a second question and answer 722 , and a third question and answer 723 ). can When the user completes the first story product service during the story product service period, the story product may be delivered.

According to an embodiment, when there is a request from the first user device 1100 or the second user device 1200 (eg, when there is a user's request), the story product service management server 2000 may provide a certificate screen 800 . can be provided at any time. The certificate screen 800 may include a certificate 810 and a certificate storage object 820 . When receiving an input for the certificate storage object 820 , the story product service management server 2000 may transmit the certificate 810 to the first user device 1100 or the second user device 1200 , and the first The user device 1100 or the second user device 1200 may store the certificate 810 .

In step S430 , the story product service management server 2000 may receive an input for the second story product service (eg, library, record). When the first story product service is completed (eg, when all answers to specified questions of time accumulation are completed), the story product service management server 2000 may provide the second story product service. 21 and 22 , the story product service management server 2000 may provide screens 900a and 900b for the second story product service. 21 may show an initial screen 900a of the second story product service before the first story product service is completed. The initial screen 900a may include a content creation object 911 . After the first story product service is completed, the user may create content related to the story product through the content creation object 911 . Referring to FIG. 22 , when the first story product service is completed, the story product service management server 2000 may provide a service screen 900b of the second story product service. The service screen 900b may include a first content 921 , a second content 922 , or a third content 923 . One content may be matched with one story product. For example, the first content 921 , the second content 922 , or the third content 923 may show that a plurality of story products have been purchased by the user. The user may remember and give meaning to story products purchased in the past through the second story product service.

According to various embodiments, before the story product is delivered, the user may log in to the story product service management server 2000 using a unique code given when purchasing the story product and receive the first story product service. After the story product is delivered, the user logs in to the story product service management server 2000 using the unique code given when purchasing the story product or the unique code displayed on the story product, and provides the first story product service and the second story product service can be provided. The user may share the first story product service and the second story product service with other users (eg, the recipient of the story product) through the invitation object 620 . As described above, the story product service management server 2000 may not simply sell a product to a user, but may provide and store a meaning, value, or story (eg, memories, memories) associated with the story product only to the user.

The above descriptions are specific embodiments for carrying out the present invention. In addition to the above-described embodiments, the present invention may include simple design changes or easily changeable embodiments. In addition, the present invention will include techniques that can be easily modified and implemented using the embodiments. Therefore, the scope of the present invention should not be limited to the above-described embodiments, but should be defined by the claims described below as well as the claims and equivalents of the present invention.

1000: story product service management system
1100: first user device
1200: second user device
2000: Story Product Service Management Server
2100: communication department
2200: storage
2300: control unit

Claims (4)

In the story product service providing method,
accessing the story product service management server through the user device;
receiving a selection input for one of the story products;
receiving order information for the selected story product;
issuing a unique code and certificate for the selected story product;
performing payment for the selected story product and setting a password corresponding to the unique code;
performing a story product service for the selected story product;
confirming completion of the story product service; and
including delivering the selected story product,
the story product service includes sending a specified number of specified questions from the story product service management server to the user device based on a specified time interval;
The story product service is completed when an answer to the last question among the specified questions is received. The method of claim 1,
The unique code includes at least one of a combination of letters or numbers, a barcode or a QR code, and is displayed, attached or engraved on a part of the selected story product. The method of claim 1,
When the unique code and the password are received through the user device, the story product service is provided, the story product service providing method. In the story product service management server,
a communication unit for receiving member information and order information for a story product selected from among the story products from the user device;
a storage unit for storing the member information and the order information input through the communication unit; and
A control unit for issuing a unique code and a certificate based on the order information stored in the storage unit, receiving a password corresponding to the unique code from the user device, and storing the password in the storage unit,
The control unit is
When the unique code and the password are received through the user device, a story product service is provided for transmitting a specified number of specified questions from the story product service server to the user device based on a specified time interval, and the specified question A story product service management server configured to deliver the selected story product when an answer to the last question among them is received and the story product service is completed.

Images