Instant messaging service method and apparatus

Abstract

To provide a method, program, server, and terminal that are related to wish lists and request the addition of desired gift items to the wish lists using instant messages, either anonymously or with real names.SOLUTION: An operation method of a server providing an instant messaging service includes the steps of: determining whether a wish request message sent to a recipient account is sent anonymously; sending the wish request message anonymously sent to a terminal of the recipient account to a first type of chat room; and notifying a terminal of a sender account of the wish request message of registration of the wish list, when the registration of the wish list of the recipient account is detected via the wish request message.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The following embodiments relate to an instant messaging service method and apparatus.

Background Art

[0002] Recently, due to the development of mobile smart devices, the use of online platform services for communicating with other users via a network has been increasing. Representative examples of online platform services for communicating with other users include social networking services (SNS), which are online platforms that generate and strengthen social relationships through communication between users, information sharing, and expansion of personal networks, and instant messaging services (IMS), which are online platforms for real-time content communication between two or more users. Such communication through mobile devices has been increasing, and online platform services support not only one-to-one communication with other users but also a function of exchanging presents between users by combining with an e-commerce platform.

Summary of the Invention

Problems to be Solved by the Invention

[0003] An object of the following embodiments is to provide a function related to a wish list that requests, anonymously or by name, to add a desired present product to the wish list using an instant message.

[0004] An object of the following embodiments is to provide a function related to a wish list that receives a notification that a present product has been added to the wish list of another user account using an instant message.

[0005] However, the technical challenges are not limited to those mentioned above, and further technical challenges exist. [Means for solving the problem]

[0006] The operation method of a server providing an instant messaging service on one side includes the steps of: determining whether a wish request message sent to a recipient account was sent anonymously; sending the anonymously sent wish request message to the recipient account's terminal via a first type of chat room; sending the wish request message sent with a real name to the recipient account's terminal via a second type of chat room; and, if registration of the recipient account's wish list through the wish request message is detected, sending a message to the terminal of the sender account of the wish request message notifying them of the registration to the wish list.

[0007] The first type of chat room may include a chat room for a channel relating to the service, and the second type of chat room may include a chat room in which the recipient account and the sender account participate.

[0008] The step of sending via the first type of chat room may include the steps of counting the number of wish request messages anonymously sent to the recipient account, and sending a message notifying the recipient account of the receipt of the wish request messages via the first type of chat room based on the number of wish request messages anonymously sent to the recipient account.

[0009] The step of sending a message notifying the registration of the wish list may include, if the wish request message is sent anonymously, sending a message notifying the registration of the wish list to the sender account's terminal via the first type of chat room, and if the wish request message is sent with a real name, sending a message notifying the registration of the wish list to the sender account's terminal via the second type of chat room.

[0010] The operation method of the server may further include the step of providing information on the number of wish request messages sent to the recipient account's terminal.

[0011] The number information of the wish request messages can be initialized by registering the recipient account's wish list through the wish request messages.

[0012] The wish request message may include a gift suggestion list containing at least one item selected by the sender account.

[0013] The wish request message may include a link that connects to a wish list corresponding to the recipient account.

[0014] The message notifying the registration of the wishlist may include a link that connects to the wishlist corresponding to the recipient account.

[0015] The operation method of the server may further include the step of receiving a request to send the wish request message from the terminal of the sender account that has accessed the wish list corresponding to the recipient account.

[0016] One embodiment of the operation method of a server providing an instant messaging service includes the steps of: storing at least one wish request message sent to a recipient account in a wish request list corresponding to the recipient account; detecting the registration of a wish list through at least one wish request message stored in the wish request list; sending a message to the terminal of the sender account of at least one wish request message stored in the wish request list to notify the registration of the wish list; and initializing the wish request list.

[0017] The step of sending a message notifying the registration of the wish list may include the steps of determining whether each of the at least one wish request message was sent anonymously, sending a message notifying the registration of the wish list via a first type of chat room to the terminal of the sender account of the anonymously sent wish request message, and sending a message notifying the registration of the wish list via a second type of chat room to the terminal of the sender account of the wish request message sent with a real name.

[0018] The first type of chat room may include a chat room for a channel relating to the service, and the second type of chat room may include a chat room in which the recipient account and the sender account participate.

[0019] The server's operation method may further include the step of providing the recipient account's terminal with information on the number of wish request messages stored in the wish request list.

[0020] A method for operating a terminal using an instant messaging service according to one embodiment includes the steps of: requesting the sending of a wish request message that requests the registration of an item to a wish list corresponding to a recipient account; selecting whether or not to send the wish request message anonymously; if the wish request message is sent anonymously, receiving a message notifying the registration to the wish list via a first type of chat room; and if the wish request message is sent with a real name, receiving a message notifying the registration to the wish list via a second type of chat room.

[0021] The first type of chat room may include a chat room for a channel relating to the service, and the second type of chat room may include a chat room in which the recipient account and the account logged into the terminal participate.

[0022] The aforementioned wish request message can be generated based on at least one of a predetermined template and text entered by the user.

[0023] A server providing an instant messaging service according to one embodiment includes at least one processor that determines whether a wish request message sent to a recipient account is anonymously sent, sends the anonymously sent wish request message to the recipient account's terminal via a first type of chat room, sends the wish request message sent with a real name to the recipient account's terminal via a second type of chat room, and if registration of the recipient account's wish list through the wish request message is detected, sends a message to the terminal of the sender account of the wish request message notifying them of the registration to the wish list.

[0024] A server that provides an instant messaging service according to an embodiment stores at least one wish request message sent to a recipient account in a wish request list corresponding to the recipient account, detects registration of a wish list through at least one wish request message stored in the wish request list, and sends a message notifying registration of the wish list to a terminal of the sender account of at least one wish request message stored in the wish request list, and includes at least one processor that initializes the wish request list.

[0025] A terminal that uses an instant messaging service according to an embodiment requests transmission of a wish request message that requests item registration in a wish list corresponding to a recipient account, selects whether to send the wish request message anonymously, and when the wish request message is sent anonymously, receives a message notifying registration of the wish list via a first type of chat room, and when the wish request message is sent with the real name, receives a message notifying registration of the wish list via a second type of chat room, and includes at least one processor.

Advantages of the Invention

[0026] According to the following embodiments, it is possible to provide a function related to a wish list that requests, anonymously or with the real name, to add a present product that functions in the wish list using an instant message.

[0027] According to the following embodiments, it is possible to provide a function related to a wish list that receives a notification that a present product has been added to the wish list of another user account using an instant message.

Brief Description of the Drawings

[0028] [Figure 1]This figure illustrates an overview of a system for an instant messaging service according to one embodiment. [Figure 2] This is a flowchart illustrating the operation method of a server providing an instant messaging service according to one embodiment. [Figure 3] This is a flowchart illustrating the operation method of a server providing an instant messaging service according to one embodiment. [Figure 4] This diagram illustrates a method for sending a wish request message and a message notifying the registration of a wish list using a wish request list according to one embodiment. [Figure 5] This is a flowchart illustrating the operation method of a terminal using an instant messaging service according to one embodiment. [Figure 6A] This diagram illustrates the screen for requesting the sending of a wish request message, which is output to the sender's account terminal. [Figure 6B] This diagram illustrates the screen for requesting the sending of a wish request message, which is output to the sender's account terminal. [Figure 7A] This diagram illustrates a screen for selecting the type of wish request message to be sent to the sender's account terminal. [Figure 7B] This diagram illustrates a screen for selecting the type of wish request message to be sent to the sender's account terminal. [Figure 8A] This diagram illustrates the screen of the chat room where the wish request message, which is output to the recipient account's device, was sent. [Figure 8B] This diagram illustrates the screen of the chat room where the wish request message, which is output to the recipient account's device, was sent. [Figure 9] This diagram illustrates a screen used to register an item to a wish list displayed on the recipient's account device. [Figure 10A]This diagram illustrates the screen of a chat room where a message notifying the sender of registration to their wish list has been sent to their device. [Figure 10B] This diagram illustrates the screen of a chat room where a message notifying the sender of registration to their wish list has been sent to their device. [Figure 11A] This is a diagram illustrating a wish request message that includes a list of gift options. [Figure 11B] This is a diagram illustrating a wish request message that includes a list of gift options. [Figure 11C] This is a diagram illustrating a wish request message that includes a list of gift options. [Figure 12A] This diagram illustrates an example of a message being sent to notify users that they have registered on the wish list. [Figure 12B] This diagram illustrates an example of a message being sent to notify users that they have registered on the wish list. [Figure 13] This is an illustrative diagram of the hardware configuration of a system for an instant messaging service according to one embodiment. [Modes for carrying out the invention]

[0029] The specific structural or functional descriptions of the embodiments are disclosed for illustrative purposes only and can be modified in various ways. Therefore, the embodiments are not limited to the specific disclosure, and the scope of this specification includes modifications, equivalents, or substitutions that are part of the technical idea.

[0030] Terms such as "first" or "second" may be used to describe multiple components, but such terms should be interpreted solely for the purpose of distinguishing one component from others. For example, the first component may be named the second component, and similarly, the second component may also be named the first component.

[0031] When it is mentioned that one component is “linked” or “connected” to another component, it should be understood that it is directly linked to or connected to the other component, but that other components may be present in between.

[0032] A singular expression includes plural expressions unless the context clearly indicates otherwise. In this specification, terms such as “includes” or “has” indicate the presence of features, figures, steps, actions, components, parts, or combinations thereof described in the specification, and should be understood not to presuppose the existence or addition of one or more other features, figures, steps, actions, components, parts, or combinations thereof.

[0033] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as those generally understood by a person of ordinary skill in the art to which this embodiment belongs. Commonly used, predefined terms should be interpreted as having the meaning consistent with their meaning in the context of the relevant art, and not as ideal or overly formal unless expressly defined herein.

[0034] The embodiments will be described in detail below with reference to the attached drawings. When describing with reference to the drawings, the same components will be given the same reference numerals regardless of the reference numerals used in the drawings, and redundant explanations will be omitted.

[0035] Figure 1 is a diagram illustrating an overview of a system for an instant messaging service according to one embodiment.

[0036] Referring to Figure 1, a system 100 for a groupware service according to one embodiment includes a terminal 110, a server 120, and a network 130. The specific hardware configuration of the server 120 and terminal 110 will be described in detail below.

[0037] In one embodiment, server 120 includes a server that provides an instant messaging service via network 130. For example, server 120 may include a server that provides an instant messaging service related to a wish list. The instant messaging service may include a service that enables multiple users to chat in real time by sending instant messages such as text messages, voice messages, and media files in real time via network 130, such as the wireless internet or a wireless communication network, and related services.

[0038] Server 120 may be linked to an application (hereinafter referred to as "app") or a web related to an instant messaging service that runs on terminal 110 for the purpose of providing a user interface (UI), function, operation, or service. Hereinafter, the app or web related to the instant messaging service will be referred to as an instant messenger.

[0039] Terminal 110 may include, for example, personal computers (PCs), netbooks, notebooks, PDAs (Personal Digital Appliances), smartphones, wearable devices, and various other devices that perform similar functions.

[0040] Terminal 110 may be driven by an instant messenger provided by the server. A user can run the instant messenger on terminal 110 and use the instant messaging service provided by server 120. A user may subscribe to the instant messaging service via the instant messenger and create a user account. A user can use the instant messaging service through terminal 110 of the account that has subscribed to the instant messaging service. Terminal 110 of the account that has subscribed to the instant messaging service means a terminal logged in with the account that has subscribed to the instant messaging service.

[0041] In one embodiment, the server 120 may be linked to a gifting service or a gifting server. The server 120 may provide a gifting service linked to an instant messaging service, or it may provide a gifting service linked to a gifting server that provides a gifting service. The gifting service means a service that allows users to purchase goods based on a social commerce platform, specify a recipient for the goods, and ensure that the goods are delivered to the recipient. For example, information that a goods have been purchased through the "gifting" service and information that a gift has been sent may be shared with the purchaser and recipient via a chat room provided by the instant messaging service. For example, a user may connect to the "gifting" service via an instant messenger. A user uses the "gifting" service using an account that has been subscribed to the instant messaging service. Alternatively, a user may use the instant messaging service using an account that has been subscribed to the "gifting" service.

[0042] According to one embodiment, the “Give a Gift” service may provide a wish-list function for storing desired items. The wish-list may be generated in relation to an account that has subscribed to the “Give a Gift” service or an instant messaging service. The wish-list corresponding to a particular account may be shared with the accounts of other users registered to that particular account (for example, accounts registered as friends). In other words, a device logged in with a user's account may access the wish-lists corresponding to the accounts of other users registered as friends. Accessing the wish-list means accessing a wish-list interface that provides information about the items included in the wish-list and provides functions related to the wish-list (for example, a function to add items to the wish-list, a function to “gift” items included in the wish-list, etc.).

[0043] According to one embodiment, the server 120 provides an instant messaging service related to the wish list, and the user can use the instant messaging service related to the wish list via a terminal logged in with an account that has subscribed to the instant messaging service. The instant messaging service related to the wish list will be described in detail below.

[0044] Figure 2 is a flowchart illustrating the operation method of a server providing an instant messaging service according to one embodiment.

[0045] Referring to Figure 2, the server operation includes step S210, which determines whether the wish request message sent to the recipient account was sent anonymously. A wish request message is a message requesting that an item be added to a wish list, and may be sent by the account that requested the sending of the wish request message to an account designated as the recipient of the wish request message. The account that requested the sending of the wish request message is the sender account, and the account designated as the recipient of the wish request message is referred to as the recipient account.

[0046] According to one embodiment, the server's operation includes receiving a request to send a wish request message from a terminal of a caller account that has accessed a wish list corresponding to a recipient account. The terminal of the caller account can access the wish list corresponding to the recipient account. For example, the caller account and the recipient account are accounts that are registered as friends with each other. The terminal of the caller account may request the server to send the wish request message to the recipient account via the wish list corresponding to the recipient account.

[0047] According to one embodiment, the sending type of a wish request message can be determined. The sending type may be selected when the wish request message is requested to be sent. The sending type of a wish request message may be determined by the sender account. The sending types may include anonymous sending and real-name sending. Determining whether a wish request message is sent anonymously means determining whether the sending type of the wish request message is anonymous or real-name sending. If a wish request message is sent anonymously, or is of the anonymous sending type, the wish request message sent to the recipient account's terminal does not have to include sender account information. Sender account information may include, for example, a sender account identifier as information to identify the sender account. If a wish request message is sent with a real name, or is of the real-name sending type, the wish request message sent to the recipient account's terminal may include sender account information.

[0048] One embodiment of the server operation method includes step S220 of sending an anonymously sent wish request message to the recipient account terminal via a first type of chat room, and step S230 of sending a real-named wish request message to the recipient account terminal via a second type of chat room.

[0049] A channel is an official account for a company or service, and is a distinct account type from general accounts. A channel chat room is a chat room in which both official accounts and general user accounts participate, and is distinct from general chat rooms in which only general user accounts participate. For example, a channel chat room is a chat room in which informational or advertising messages about a company or service are sent by an official account. On the other hand, a general chat room is a chat room in which participating user accounts exchange messages via chat.

[0050] Type 1 chat rooms include chat rooms for service-related channels. For example, Type 1 chat rooms may include chat rooms for channels related to instant messaging services or "gift" services. Anonymous wish request messages are sent to Type 1 chat rooms as messages originating from official accounts related to instant messaging services or "gift" services.

[0051] The second type of chat room includes chat rooms in which both a recipient account and a sender account participate. For example, the second type of chat room may include a one-to-one chat room in which both a recipient account and a sender account participate, or a group chat room in which both a recipient account and a sender account participate. A wish request message sent to a real name may be sent to the second type of chat room as a message with the sender account as the sender.

[0052] According to one embodiment, step S220, which is sent via a first type chat room, includes the steps of counting the number of wish request messages anonymously sent to the recipient account and sending a message notifying the recipient of the receipt of wish request messages via the first type chat room based on the number of wish request messages anonymously sent to the recipient account.

[0053] For example, each time the number of anonymously sent wish request messages reaches n (for example, n is a natural number greater than or equal to 1), a message notifying the recipient account of the receipt of a wish request message may be sent to the recipient account's terminal via a first type of chat room. According to one embodiment, if the registration of a wish request message to the recipient account is detected via the message notifying the receipt of a wish request message, the number of anonymously sent wish request messages may be initialized to 0 and then counted again.

[0054] For example, depending on the number of anonymous wish request messages sent to the recipient account, messages notifying the receipt of other types of wish request messages may be sent. For instance, if the number of anonymous wish request messages sent to the recipient account is between one and five, a first type message notifying the receipt of wish request messages may be sent, and if the number of anonymous wish request messages sent to the recipient account is between six and ten, a second type message notifying the receipt of wish request messages may be sent. The second type message notifying the receipt of wish request messages may include text and / or visual symbols that more strongly encourage the recipient account to add the wish request message to their wish list than the first type message.

[0055] According to one embodiment, a wish request message may include a link that connects to a wish list corresponding to the recipient account. The recipient account's terminal can access the wish list corresponding to its account via the wish request message. Users of the recipient account can add items to the wish list via their terminal.

[0056] One embodiment of the server's operation method includes step S240, when it detects that a recipient account has registered a wishlist via a wish request message, sending a message to the terminal of the sender account of the wish request message to notify them of the wishlist registration. The server may also detect that an item has been added to the wishlist corresponding to the recipient account. The server may also detect whether the recipient account's terminal accessed the wishlist via the wish request message and added an item to it, or whether it accessed the wishlist via a different route and added an item to it. When the server detects that the recipient account's terminal accessed the wishlist via the wish request message and added an item to it, it sends a message to the terminal of the sender account of the wish request message to notify them of the wishlist registration.

[0057] According to one embodiment, when the server detects that a recipient account has registered an item on its wish list via a wish request message, it sends a message notifying the recipient account's terminal of the registration of the wish list to one or more sender accounts that sent the wish request message to the recipient account's terminal prior to the detection point. For example, if a recipient account receives multiple wish request messages, including a first wish request message and a second wish request message, the user of the recipient account may access the wish list via the first wish request message and add an item. The server may send a message notifying the recipient account of the registration of the wish list not only to the terminal of the sender account of the first wish request message, but also to the terminal of the sender account of the second wish request message that sent the wish request message to the recipient account at the time of detection. The method for sending a message notifying the recipient account of the registration of the wish list when multiple wish request messages are sent to the recipient account will be described in detail below.

[0058] A message notifying a wishlist addition includes a message notifying the recipient that an item has been added to the wishlist corresponding to their account. According to one embodiment, the message notifying a wishlist addition may include a link to the wishlist corresponding to the recipient's account. The sender's account's terminal may access the wishlist corresponding to the recipient's account via the message notifying a wishlist addition. The user of the sender's account can then verify the item added to the wishlist corresponding to the recipient's account.

[0059] Step S240 of sending a message notifying the registration of a wishlist according to one embodiment includes the steps of sending a message notifying the registration of the wishlist to the sender account's terminal via a first type of chat room if the wish request message was sent anonymously, and sending a message notifying the registration of the wishlist to the sender account's terminal via a second type of chat room if the wish request message was sent with a real name.

[0060] According to one embodiment, the server's operation method includes the step of providing information on the number of wish request messages sent to the recipient account's terminal. For example, only information on the number of wish request messages sent anonymously to the recipient account's terminal may be provided, or only information on the number of wish request messages sent to a real name may be provided. For example, information on the number of wish request messages sent anonymously and information on the number of wish request messages sent to a real name may be provided separately. For example, the sum of the number of wish request messages sent anonymously and the number of wish request messages sent to a real name may be provided.

[0061] According to one embodiment, the number of wish request messages can be initialized by registering the recipient account's wish list through the wish request messages.

[0062] Figure 3 is a flowchart illustrating the operation method of a server providing an instant messaging service according to one embodiment.

[0063] Referring to Figure 3, the server operation includes step S310 of storing at least one wish request message sent to a recipient account in a wish request list corresponding to the recipient account. The wish request list may include, for example, a queue, a stack, or an array as a storage space for wish request messages. The wish request list may also store information about the sender account of the wish request message and the type of wish request message sent.

[0064] One embodiment of the server's operation method includes the step of providing the recipient account's terminal with information about the number of wish request messages stored in the wish request list. If the number of wish request messages stored in the wish request list is n, the server provides the recipient account's terminal with information that n wish request messages have been received.

[0065] One embodiment of the server operation method includes step S320, which detects the registration of a wish list through at least one wish request message stored in the wish request list.

[0066] One embodiment of the server operation method includes step S330, which sends a message notifying the registration of a wish list to the terminal of the sender account of at least one wish request message stored in the wish request list. The terminal of the sender account to which the message notifying the registration of the wish list is sent may include the terminal of the sender account of each of the at least one wish request message stored in the wish request list at the time the registration of the wish list is detected.

[0067] Step S330 of sending a message notifying the registration of a wish list according to one embodiment includes the steps of determining whether each of the at least one wish request message stored in the wish request list was sent anonymously, sending a message notifying the registration of the wish list via a first type of chat room to the terminal of the sender account of the anonymously sent wish request message, and sending a message notifying the registration of the wish list via a second type of chat room to the terminal of the sender account of the wish request message sent with a real name.

[0068] One embodiment of the server's operation method includes a step S340 for initializing the wish request list. When a message notifying the registration of a wish request to the wish list is sent to the terminal of the sender account of at least one wish request message stored in the wish request list, the server initializes the wish request list. Initializing the wish request list means deleting all data stored in the wish request list. The wish request list may also store wish request messages sent to the recipient account after the registration of a wish request to the wish list via a wish request message has been detected.

[0069] For example, referring to Figure 4, the recipient account's terminal may receive a first wish request message sent by the first sender account, a second wish request message sent by the second sender account, and a third wish request message sent by the third sender account. The wish request list 410 corresponding to the recipient account may store the three received wish request messages.

[0070] If a recipient account is found to have registered for the wishlist through at least one of the three wish request messages, a message notifying the registration of the wishlist is sent to the terminals of the first, second, and third sender accounts. Depending on the type of each of the three wish request messages, the type of chat room to which the message notifying the registration of the wishlist is sent can be determined. For example, if the first wish request message is sent anonymously, the terminal of the first sender account may receive a message notifying the registration of the wishlist via a chat room of type 1. For example, if the second wish request message is sent with a real name, the terminal of the second sender account may receive a message notifying the registration of the wishlist via a chat room of type 2.

[0071] When a message notifying the sender account of the registration to the wishlist is sent to the sender's account's device, the corresponding wish request list 430 is initialized in the recipient account.

[0072] Figure 5 is a flowchart illustrating the operation method of a terminal using an instant messaging service according to one embodiment.

[0073] For example, devices using the instant messaging service may include the device of the sender account of the wish request message or a device logged in with the sender account.

[0074] Referring to Figure 5, the operation method of the terminal includes step S510, which requests the sending of a wish request message that requests the registration of an item in the wish list corresponding to the recipient account.

[0075] According to one embodiment, a wish request message is generated based on at least one of a predetermined template and text entered by the user. The predetermined template may include at least one of predetermined text, predetermined visual symbols, the arrangement of text and / or visual symbols, and a predetermined message style (e.g., font, font color, font size, background color, background pattern, etc.). As an example, at least one template may be provided, and a wish request message composed of templates selected by the user from among the provided templates may be generated. The templates may be edited by the user. For example, predetermined text included in a template may be changed by the user. As an example, a wish request message including text entered by the user may be generated.

[0076] The operation of the terminal includes step S520, which involves selecting whether or not to send the wish request message anonymously. Depending on the selection of whether or not to send anonymously, the wish request message may be sent anonymously or to the user account's terminal.

[0077] The operation method of the terminal includes, if the wish request message is sent anonymously, step S530 receiving a message notifying registration to the wish list via a first type of chat room, and if the wish request message is sent to a real name, step S540 receiving a message notifying registration to the wish list via a second type of chat room.

[0078] Figures 6A and 6B illustrate the screens for requesting the sending of a wish request message, which are output to the sender account's terminal.

[0079] According to one embodiment, the sender account's terminal executes the "Gift" function by specifying the recipient account. By executing the "Gift" function for the specified recipient account, an interface for sending a gift to the recipient account may be provided to the sender account's terminal, as shown in screen 601 in Figure 6A and screen 602 in Figure 6B.

[0080] Referring to screen 601 shown in Figure 6A, the interface for sending a gift to a recipient account includes a wishlist 610 corresponding to the recipient account. In other words, the sender account's terminal may access the wishlist 610 corresponding to the recipient account by executing the “gift” function to the recipient account. The wishlist 610 includes an interface object 611 for requesting the sending of a wish request message. For example, the input for selecting the interface object 611 corresponds to the input requesting the server to send a wish request message to the recipient account.

[0081] Referring to screen 602 shown in Figure 6B, the wishlist 620 corresponding to the recipient account includes the items 622 registered by the recipient account. Even if at least one item 622 is registered in the wishlist 620, an interfacing object 621 may be provided to request the sending of a wish request message via the wishlist 620.

[0082] As described above, wish request messages can be sent anonymously or with a real name. Depending on the type of wish request message sent, it may be sent to the recipient account's terminal via a first-type or second-type chat room. For example, if input is received to select an interface object 611,621 to request the sending of a wish request message, a screen for selecting the type of wish request message to be sent (e.g., screen 701 shown in Figure 7A or screen 702 shown in Figure 7B) may be displayed to the sender account's terminal.

[0083] Figures 7A and 7B illustrate the screens used to select the type of wish request message to be sent to the sender account's terminal.

[0084] According to one embodiment, the terminal of the sender account that requested the sending of the wish request message may select the type of wish request message to send. As described above, the types of wish request message to send include an anonymous sending type and a real-name sending type.

[0085] Referring to screen 701 shown in Figure 7A, the sending type of the wish request message may be determined as a real-name sending type by input to select an interface object 710 for selecting the sending type of the wish request message. The real-name sending type wish request message is displayed via a preview window 720 that shows the wish request message to be sent to the recipient account. The preview window 720 includes an interface object 721 for editing the message template. If interface object 721 is selected, the text or visual symbols included in the template may be modified by input from the terminal.

[0086] Referring to screen 701 shown in Figure 7A, it may include an interfacing object 730 for requesting the sending of a wish request message with a determined sending type. As described above, a wish request message with a real name sending type may be sent via a second type of chat room in which the recipient account and the sender account participate. The interfacing object 730 for requesting the sending of a wish request message with a real name sending type includes information indicating the type of chat room to which the wish request message will be sent. For example, the interfacing object 730 may include information indicating that the type of chat room to which the wish request message will be sent is a 1:1 chat room. By selecting the interfacing object 730, the wish request message generated in the form displayed in the preview window 720 can be sent to the recipient account's terminal.

[0087] Referring to screen 702 shown in Figure 7B, the sending type of the wish request message may be determined as an anonymous sending type by the input for selecting the interface object 740 for selecting the sending type of the wish request message. The anonymous sending type wish request message is displayed via a preview window 750 that shows the wish request message to be sent to the recipient account.

[0088] According to one embodiment, the preview window 750 displaying an anonymous wish request message does not need to provide a function to edit the message template. The template for a wish request message corresponding to a predetermined anonymous sending type is not changed by user input, and an anonymous wish request message can be generated using the predetermined template. By not providing a function to edit the anonymous wish request message, the risk of abusing using anonymously sent wish request messages can be prevented.

[0089] Referring to screen 702 shown in Figure 7B, an interfacing object 760 is included for requesting the sending of a wish request message with a determined sending type. As described above, a wish request message of anonymous sending type may be sent via a chat room of type 1 on a channel related to the service. The interfacing object 760 for requesting the sending of an anonymous wish request message may include information indicating the type of chat room to which the wish request message will be sent. For example, the interfacing object 760 may include information indicating the type of chat room to which the wish request message will be sent is a chat room on a channel related to the "Gift" service. By selecting the interfacing object 760, the wish request message generated in the form shown in the preview window 750 can be sent to the terminal of the recipient account.

[0090] Figures 8A and 8B illustrate the screen of the chat room where the wish request message, which is output to the recipient account's terminal, was sent.

[0091] Referring to screen 801 shown in Figure 8A, a wish request message 810 of the real name sending type may be sent to the recipient account's terminal via a 1:1 chat room with the sender account. A wish request message 810 sent to a real name may also be sent as a message to the sender account. For example, in the chat window corresponding to the 1:1 chat room with the sender account, the sender account identifier 820 is displayed adjacent to the wish request message 810 sent to a real name. The display of the sender account identifier 820 indicates that the wish request message 810 sent to a real name is a message sent by the sender account.

[0092] Referring to screen 802 shown in Figure 8B, an anonymous wish request message 830 of the sending type is sent to the recipient account's terminal via a chat room in a channel related to the "Give a Gift" service. The anonymously sent wish request message 830 may also be sent to a message from an official account related to the "Give a Gift" service. For example, the identifier 840 of the official account may be displayed adjacent to the anonymously sent wish request message 830 in the chat window corresponding to the chat room in the channel related to the "Give a Gift" service. Information about the sender account that requested the anonymously sent wish request message 830 does not need to be exposed to the recipient account's terminal.

[0093] Wish request messages 810, 830 sent to the terminal of a recipient account according to one embodiment include a link to a wish list corresponding to the recipient account. Wish request messages 810, 830 include interfacing objects 811, 831 corresponding to the link to the wish list. By selecting an interfacing object 811, 831 as input, the terminal of the recipient account can access the wish list corresponding to the recipient account. For example, a screen for registering an item in the wish list (e.g., screen 901 shown in Figure 9) may be output to the terminal of the recipient account that has accessed the wish list corresponding to the recipient account.

[0094] Figure 9 illustrates a screen for registering items to the wish list displayed on the recipient's account terminal.

[0095] According to one embodiment, the recipient account's terminal can access the wishlist corresponding to the recipient account and register or add items to the wishlist. The recipient account's terminal may access the wishlist via a received wish request message, or it may access the wishlist via another route.

[0096] Referring to screen 901 shown in Figure 9, the wish list 910 is displayed on the recipient account's terminal. Items selected as wish items by the recipient account may be registered in the wish list 910. If there are no items registered in the wish list 910, an indication that there are no items registered in the wish list 910 will be displayed.

[0097] According to one embodiment, information on the number of wish request messages sent to the recipient account's terminal can be provided. For example, a guidance message 930 may be provided indicating the number of sender accounts that sent wish request messages to the recipient account. When registration of the recipient account's wish list via a wish request message is detected, the information on the number of wish request messages is initialized. When the information on the number of wish request messages is initialized, the guidance message 930 is modified to indicate that the number of sender accounts that sent wish request messages to the recipient account is 0.

[0098] Referring to screen 901 shown in Figure 9, a recommended item list 920 is provided to the recipient account's terminal. The recommended item list 920 may include an interfacing object 921 for adding items to the wish list. By selecting an interfacing object 921, the item corresponding to the interfacing object 921 can be added to the wish list 910.

[0099] According to one embodiment, the recommended item list 920 may include multiple recommended item lists corresponding to various types. For example, recommended item lists may be provided based on characteristics such as the age of the user to whom the gift is given (e.g., 20s, 30s), gender, and relationship to the person receiving the gift (e.g., friend, girlfriend, boyfriend, parents). For example, recommended item lists may be provided based on the purpose of the gift, such as wedding gifts, housewarming gifts, birthday gifts, small gifts, and holiday gift sets.

[0100] According to one embodiment, the recommended item list 920 may include a user-defined recommended item list. The recommended item list 920 may include items that are likely to be added to the user's wish list based on an analysis of data collected from the user. For example, a user-defined recommended item list 920 may be generated using a deep learning model that recommends items based on the user's search history, a breakdown of items added to the wish list, and characteristic data such as the user's age, gender, and place of residence.

[0101] According to one embodiment, if registration of a recipient account to the wish list via a wish request message is detected, a message notifying the sender account of the wish request message of the registration to the wish list may be sent.

[0102] Figures 10A and 10B illustrate the screen of a chat room where a message notifying the sender of registration to the wish list has been sent to the sender's account terminal.

[0103] Referring to screen 1001 shown in Figure 10A, if a wish request message 1010 is sent to the real name by the sender account, a message 1020 notifying the registration of the wish list is sent to the sender account's terminal via a 1:1 chat room with the recipient account. The message 1020 notifying the registration of the wish list may be sent via the same chat room from which the wish request message 1010 sent to the real name was sent. The message 1020 notifying the registration of the wish list may also be sent as a message to the recipient account of the wish request message 1010. For example, the recipient account identifier 1030 may be displayed adjacent to the message 1020 notifying the registration of the wish list in the chat window corresponding to the 1:1 chat room with the recipient account. The display of the recipient account identifier 1030 indicates that the message 1020 notifying the registration of the wish list was sent by the recipient account.

[0104] Referring to screen 1002 shown in Figure 10B, if a wish request message is sent anonymously by a sender account, the message 1040 notifying the registration of the wish list may be sent to the sender account's terminal via a chat room in the channel related to the "Give a Gift" service. The message 1040 notifying the registration of the wish list may be sent via a different chat room than the one in which the anonymously sent wish request message was sent. The wish request message sent anonymously by a sender account may be sent via a chat room in the channel related to the "Give a Gift" service in which the recipient account participates. On the other hand, the message 1040 notifying the registration of the wish list may be sent via a chat room in the channel related to the "Give a Gift" service in which the sender account participates. The message 1040 notifying the registration of the wish list may be sent via a message to an official account related to the "Give a Gift" service. For example, the identifier 1050 of the official account may be displayed adjacent to the anonymously sent message 1040 notifying the registration of the wish list in the chat window corresponding to the chat room in the channel related to the "Give a Gift" service.

[0105] Messages 1030 and 1040, which notify the registration of a wishlist sent to the terminal of the caller account according to one embodiment, include a link to the wishlist corresponding to the recipient account. Messages 1030 and 1040, which notify the registration of a wishlist, include interfacing objects 1021 and 1041 corresponding to the link to the wishlist. By selecting an interfacing object 1021 or 1041, the terminal of the caller account may access the wishlist corresponding to the recipient account. For example, a wishlist containing items registered by the recipient account can be output to the terminal of the caller account that has accessed the wishlist corresponding to the recipient account.

[0106] Figures 11A to 11C illustrate a wish request message that includes a list of gift options.

[0107] According to one embodiment, a wish request message includes a gift suggestion list containing at least one item selected by the sender account. The terminal of the sender account that requested the sending of the wish request message may request the generation of the gift suggestion list provided via the wish request message. The terminal of the sender account may select items to be included in the gift suggestion list.

[0108] Referring to screen 1101 shown in Figure 11A, the input to select an interface object 1110 for requesting the generation of a gift candidate list provides the caller account's terminal with screen 1102 shown in Figure 11B for generating the gift candidate list.

[0109] According to one embodiment, the gift candidate list may be included in the wish request message regardless of the type of wish request message sent, or it may be configured so that the gift candidate list is included only in wish request messages sent with a real name. For example, to prevent the risk of abusing using anonymously sent wish request messages, the provision of the gift candidate list may be restricted to anonymously sent wish request messages.

[0110] Referring to screen 1102 shown in Figure 11B, the sender account's terminal can select at least one item from the gift candidate list. The server generates a gift candidate list containing at least one item selected from the sender account's terminal. A wish request message containing the generated gift candidate list may be sent to the recipient account's terminal. For example, the wish request message may include a link to the gift candidate list.

[0111] Referring to screen 1103 shown in Figure 11C, the recipient account's terminal accesses the gift candidate list 1120 via a wish request message containing the gift candidate list. The recipient account's terminal may register at least one item from the gift candidate list 1120 as a wish list. For example, by selecting an interface object 1121 for selecting an item from the gift candidate list 1120, the selected item may be registered as a wish list corresponding to the recipient account.

[0112] Figures 12A and 12B illustrate an example of a message being sent to notify a user of their wishlist registration.

[0113] The screen 1201 shown in Figure 12A corresponds to the wishlist interface displayed on a device that has accessed the wishlist corresponding to the user's account. The wishlist corresponding to the user's account refers to the wishlist corresponding to the account logged into the device. The account logged into the device on which screen 1201 is displayed is referred to as the first account, and so on.

[0114] Referring to screen 1201, an interfacing object 1210 may be provided for requesting the server to send a message notifying the server of the registration of a wishlist via the wishlist interface. By selecting the interfacing object 1210, a message notifying the registration of a wishlist may be sent to the terminal of another account.

[0115] For example, other accounts to which a message notifying the registration of a wishlist may be sent may include the account that requested the first account to send a wish request message. The server may, by input selecting an interfacing object 1210 received from the terminal, send a message notifying the registration of the wishlist to the terminal of the sender account of the wish request message received by the first account. As described above, if the server detects a wishlist registration via a wish request message, it may automatically send a message to the terminal of the sender account of the wish request message. According to one embodiment, if the server detects a wishlist registration via a wish request message, it can send a message notifying the registration of the wishlist to the sender account's terminal at the time the first account's terminal leaves screen 1201.

[0116] For example, other accounts to which a message notifying of a wishlist registration is sent may include accounts selected by the first account as recipients of the message notifying of the wishlist registration.

[0117] According to one embodiment, the interfacing object 1210 can be activated when one or more items are registered in the wishlist. If there are no items registered in the wishlist, it may be deactivated. In other words, only when one or more items are registered in the wishlist, an input selecting the interfacing object 1210 sends a signal requesting the server to send a message notifying it of the registration in the wishlist.

[0118] According to one embodiment, a terminal can access the wish list corresponding to its own account through a route other than a wish request message. For example, referring to Figure 12B, a message 1220 notifying the first account of an anniversary (e.g., birthday) set for the first account may be sent via the chat room of the channel related to the gift service. The server stores the anniversary information corresponding to the first account. The anniversary information corresponding to the first account may be set by the user of the first account, or it may be extracted from information entered when subscribing to the service (e.g., date of birth information). The server may send the anniversary notification message 1220 to the first account's terminal via the chat room of the channel related to the "Give a Gift" service at a predetermined time before the time set as the anniversary (e.g., 10 minutes before, 1 day before, 1 week before, etc.). The anniversary notification message 1220 includes a link to the wish list. The first account's terminal can access the wish list of its own account via the anniversary notification message 1220. Alternatively, for example, the terminal may perform the gift service function via an instant messenger. The device can execute the "Give Gift" service function and access the wish list.

[0119] Even if an item is added to a wishlist by accessing it through a route other than a wish request message, a message notifying the addition to the wishlist may be sent to the terminal of another account based on a request received from the terminal (for example, an input selecting interfacing object 1210).

[0120] Figure 13 is an illustrative diagram of the hardware configuration of a system for an instant messaging service according to one embodiment.

[0121] Referring to Figure 13, a system according to one embodiment (for example, system 100 shown in Figure 1) includes terminals 110 (for example, terminal 110 shown in Figure 1) and a server 120 (for example, server 120 shown in Figure 1) connected via a network 130.

[0122] In one embodiment, terminal 110 may be a mobile terminal implemented by a computer device. For example, terminal 110 may communicate with server 120 and / or other electronic devices via network 130 using wireless or wired communication methods.

[0123] In one embodiment, the server 120 can be embodied as a computer device or a group of computer devices that communicate with terminals 110 and / or other servers via the network 130 and provide commands, codes, files, content, services, etc. The communication method is not limited and may include a communication method that utilizes a communication network including the network 130 (e.g., a mobile communication network, wired internet, wireless internet, broadcasting network), or a short-range wireless communication method between devices. For example, the network 130 may include one or more of the following networks: PAN (personal area network), LAN (local area network), CAN (campus area network), MAN (metropolitan area network), WAN (wide area network), BN (broadband network), or the internet.

[0124] According to one embodiment, the server 120 can provide a terminal 110 connected via the network 130 with files for installing an application. In this case, the terminal 110 may install an application (e.g., an instant messenger) using the files provided by the server 120. Furthermore, the operating system (OS) and at least one program (e.g., a browser or an installed application) included in the terminal 110 can control the connection to the server 120 and provide services and content provided by the server 120. For example, if the terminal 110 sends a service request message to the server 120 via the network 130 under the control of an application, the server 120 sends a code corresponding to the service request message to the terminal 110, and the terminal 110 can provide content to the user by configuring and displaying a screen based on the code under the control of an application.

[0125] According to one embodiment, the terminal 110 and server 120 include memory 1311, 1321, processor 1313, 1323, communication modules 1315, 1325, and input / output interfaces 1317, 1327.

[0126] A processor 1313, 1323 according to one embodiment can perform at least one of the operations described above with reference to Figures 1 to 12B. For example, processor 1313 may perform at least one of the operations included in the operation method of a terminal 110 using the instant messaging service described above with reference to Figure 5. Processor 1323 may perform at least one of the operations included in the operation method of a server 120 providing the instant messaging service described above with reference to Figures 2 to 4. Processors 1313, 1323 can be configured to process computer program instructions by performing basic arithmetic, logic, and input / output operations. Instructions are provided to processors 1313, 1323 by memory 1311, 1321 or by communication modules 1315, 1325.

[0127] The memories 1311 and 1321 may be volatile or non-volatile memory as a recording medium readable by a computer. In one embodiment, the memories 1311 and 1321 may store information related to the instant messaging service described above, with reference to Figures 1 to 12B. For example, the memory 1321 of the server 120 may store account information of users who have subscribed to the instant messaging service and wishlist information corresponding to those accounts.

[0128] In one embodiment, the memory 1311 may include code for an instant messenger that is installed and driven on the terminal 110 by a file provided by the server 120 via the network 130.

[0129] According to one embodiment, the memory 1321 can store a program that embodies the operation for providing an instant messaging service, which is executed on the server described above, with reference to Figures 1 to 12B.

[0130] One embodiment of the communication modules 1315 and 1325 provides functions for terminals 110 and server 120 to communicate with each other via network 130, and can also provide functions for communicating with other electronic devices or other servers.

[0131] For example, a request generated by the processor 1313 of terminal 110 in accordance with program code related to an instant messenger stored in a recording device such as memory 1311 may be transmitted to server 120 via network 130 under the control of communication module 1315.

[0132] For example, control signals, instructions, content, files, etc., provided by the control of the processor 1323 of the server 120 may be received by the terminal 110 via the communication module 1325 and the network 130, through the communication module 1315 of the terminal 110.

[0133] The input / output interfaces 1317 and 1327 may also be means for interfacing with the input / output device 1319. For example, the input device may include a device such as a keyboard or mouse, and the output device may include a device such as a display for displaying the application's communication session. In a different example, the input / output interface 1317 may be means for interfacing with a device that combines input and output functions into one, such as a touchscreen. In a more specific example, in processing instructions for a computer program loaded into memory 1311, the processor 1313 of the terminal 110 may display a service screen or content, which is composed of data provided by the server 120, via the input / output interface 1317. Input received from the user through the input / output device 1319 may be provided via the input / output interface 1317 in a form that can be processed by the processor 1313 of the terminal 110.

[0134] According to one embodiment, the terminal 110 and the server 120 may include other components not shown in Figure 13. For example, the terminal 110 may be implemented including at least a portion of the input / output device 1319 described above, or it may further include other components such as a transceiver, a GPS (Global Positioning System) module, a camera, various sensors, a database, etc.

[0135] The embodiments described above can be embodied in hardware components, software components, and / or combinations of hardware and software components. For example, the adaptive supersampling apparatus, methods, and components described in the embodiments can be embodied using a general-purpose computer or a special-purpose computer, such as a processor, controller, ALU (arithmetic logic unit), digital signal processor, microcomputer, FPGA (Field Programmable Gate Array), PLU (Programmable Logic Unit), microprocessor, or other adaptive supersampling apparatus capable of executing commands and responding. The processing adaptive supersampling apparatus can execute an operating system (OS) and software applications that run on the OS. The processing adaptive supersampling apparatus may also access, store, manipulate, process, and generate data in response to the execution of the software. For convenience of understanding, the processing adaptive supersampling apparatus has sometimes been described as being used as a single unit, but a person with ordinary skill in the art will see that the processing adaptive supersampling apparatus may include multiple processing elements and / or multiple types of processing elements. For example, a processing-adaptive supersampling system may include multiple processors or one processor and one controller. Other processing configurations, such as a parallel processor, are also possible.

[0136] The software may include computer programs, code, instructions, or any combination thereof, and may configure or instruct a processing adaptive supersampling device as desired, independently or collectively. The software and / or data may be permanently embodied in any type of machine, component, physical adaptive supersampling device, virtual adaptive supersampling device, computer storage medium, or adaptive supersampling device, or transmitted signal waves, in order to be interpreted by the processing adaptive supersampling device or to provide instructions or data to the processing adaptive supersampling device. The software may be distributed on a networked computer system and stored or executed in a distributed manner. The software and data may be stored on a computer-readable recording medium.

[0137] The method according to this embodiment is embodied in the form of program instructions that are implemented via various computer means and recorded on a computer-readable recording medium. The recording medium includes program instructions, data files, data structures, etc., individually or in combination. The recording medium and program instructions may be specifically designed and configured for the purposes of the present invention, or they may be known and usable by those skilled in the art who have technology in the field of computer software. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks and magnetic tapes, optical recording media such as CD-ROMs and DVDs, magneto-optical media such as floppy disks, and hardware devices specifically configured to store and execute program instructions, such as ROMs, RAMs, and flash memory. Examples of program instructions include not only machine code generated by a compiler, but also high-level language code executed by a computer using an interpreter or the like.

[0138] The hardware adaptive supersampling device described above may be configured to operate as one or more software models to perform the operations shown in the present invention, and vice versa.

[0139] As described above, although embodiments have been illustrated with limited drawings, a person with ordinary skill in the art can apply various technical modifications and variations based on the above description. For example, the described technique may be performed in a different order than described, and / or the described system, structure, apparatus, circuit, and other components may be combined or assembled in a different manner than described, or replaced or substituted by other components or equivalents, and still achieve the desired results.

[0140] Therefore, other embodiments, other embodiments, and claims equivalent to those described below also fall within the scope of the claims.

Claims

1. A method for operating a server that provides instant messaging services, The steps include determining the type of wish request message sent to the recipient account, If the sending type of the wish request message is anonymous, the step of sending the wish request message, which does not include the sender account information, to the recipient account's terminal, If the sending type of the wish request message is not anonymous, the step of sending the wish request message, including the sender account information, to the recipient account's terminal, If the registration of an item to the recipient account's wish list is confirmed via the wish request message, the steps include notifying the terminal of the sender account of the wish request message of the registration of the item to the wish list, Methods that include...

2. The method according to claim 1, wherein the wish request message is sent to the recipient account's terminal via the chat room.

3. The aforementioned chat room is The chat room of the channel related to the aforementioned instant messaging service, The chat room in which the recipient account and the sender account participate, The method according to claim 2, comprising at least one of the above.

4. The wish request message, which does not include the sender account information, is sent to the recipient account's terminal via the first chat room. The method according to claim 1, wherein the wish request message, which includes the information of the sender account, is sent to the recipient account's terminal via the second chat room. method.

5. The method according to claim 1, wherein the anonymous transmission type wish request message is generated based on a template corresponding to the anonymous transmission type, and the template corresponding to the anonymous transmission type is not modified by user input.

6. The step of sending the wish request message, which includes the information of the sender account, The steps include counting the number of anonymous send type wish request messages sent to the recipient account, Based on the counted number of anonymously sent wish request messages, the recipient account's terminal is notified of the receipt of the wish request message. The method according to claim 1, including the method described in claim 1.

7. The step of notifying the registration of an item on the wish list is: If the sending type of the wish request message is anonymous, the steps include sending a message via the first chat room to the sender account's terminal notifying them of the registration of the item on the wish list, If the sending type of the wish request message is not anonymous, the steps include sending a message to the sender account's terminal via the second chat room notifying them of the registration of the item on the wish list, The method according to claim 1, including the method described in claim 1.

8. The method according to claim 1, further comprising the step of providing information on the number of wish request messages sent to the recipient account's terminal.

9. The method according to claim 8, wherein the number information of the wish request messages is initialized by the registration of an item in the recipient account's wish list via the wish request messages.

10. The method according to claim 1, wherein the wish request message includes a gift suggestion list containing at least one item selected by the sender account.

11. The method according to claim 1, wherein the wish request message includes a link that connects to a wish list corresponding to the recipient account.

12. The method according to claim 1, further comprising the step of receiving a request to send the wish request message from a terminal of the sender account that has accessed the wish list corresponding to the recipient account.

13. A method for operating a device that uses an instant messaging service, The steps include selecting the type of wish request message to send, which requests the registration of an item to a wish list corresponding to the recipient account, and requesting the sending of the wish request message, If the sending type of the wish request message is anonymous, the steps include receiving a notification of item registration on the wish list via the first chat room, If the sending type of the wish request message is not anonymous, the step is to receive a notification of item registration on the wish list via the second chat room. Methods that include...

14. The anonymous transmission type wish request message is: It is generated based on a predetermined template. The wish request message that is not of the anonymous transmission type is: The method according to claim 13, which is generated based on at least one of a predetermined template and user input.

15. A computer program stored in a medium for use in conjunction with hardware to perform the method according to any one of claims 1 to 14.

16. A server that provides instant messaging services, One or more processors, Memory for storing instructions, Includes, When the instruction is executed by one or more processors, the server will: Steps to determine the type of message sent to the recipient account for the wish request message, If the sending type of the wish request message is anonymous, the step of sending the wish request message, which does not include the sender account information, to the recipient account's terminal, If the sending type of the wish request message is not anonymous, the step of sending the wish request message, including the sender account information, to the recipient account's terminal, If the registration of an item to the recipient account's wish list is confirmed via the wish request message, the steps include notifying the terminal of the sender account of the wish request message of the registration of the item to the wish list, The server on which it is executed.

17. A device that uses an instant messaging service, One or more processors, Memory for storing instructions, Includes, When the instruction is executed by one or more processors, the terminal will: The steps include selecting the type of wish request message to send, which requests the registration of an item to a wish list corresponding to the recipient account, and requesting the sending of the wish request message, If the sending type of the wish request message is anonymous, the steps include receiving a notification of item registration on the wish list via the first chat room, If the sending type of the wish request message is not anonymous, the step is to receive a notification of item registration on the wish list via the second chat room. A terminal that includes this.

Images