JP7627325B2 - Instant messaging service method and apparatus - Google Patents

Description

The following embodiments relate to an instant messaging service method and device.

Recently, with the development of mobile smart devices, the use of online platform services for interacting with other users via networks is increasing. Representative examples of online platform services for interacting with other users include social networking services (SNS), which are online platforms that create and strengthen social relationships through communication between users, information sharing, and networking expansion, and instant messaging services (IMS), which are online platforms for real-time content communication between two or more users. As communication through such mobile devices increases, online platform services support not only one-on-one communication with other users but also the function of exchanging gifts between users by combining with e-commerce platforms.

The following embodiment provides a wishlist-related function that allows a user to request, anonymously or with their real name, to add a desired gift item to their wishlist using an instant message.

The following embodiment provides a wishlist-related function that uses instant messaging to receive notifications that gift items have been added to the wishlists of other user accounts.

However, the technical challenges are not limited to those mentioned above, and further technical challenges exist.

The operation method of the server providing the instant messaging service relating to one side includes the steps of determining whether the wish request message sent to the recipient account is sent anonymously, sending the anonymously sent wish request message to the terminal of the recipient account via a first type of chat room, sending the wish request message sent to the real name to the terminal of the recipient account via a second type of chat room, and if registration of a wish list of the recipient account through the wish request message is detected, sending a message notifying the registration of the wish list to the terminal of the sender account of the wish request message.

The first type of chat room may include a chat room for a channel related 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.

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

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

The server operation method may further include a step of providing information on the number of wish request messages sent to the terminal of the recipient account.

The number information of the wish request message can be initialized by registering the wish list of the recipient account through the wish request message.

The wish request message may include a gift list including at least one item selected by the sender account.

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

The message notifying the registration of the wish list may include a link connected to the wish list corresponding to the recipient account.

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

An operating method of a server providing an instant messaging service according to one embodiment 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 wish list registration through at least one wish request message stored in the wish request list; sending a message to a terminal of a 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.

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

The first type of chat room may include a chat room for a channel related 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.

The operation of the server may further include providing information on the number of wish request messages stored in the wish request list to the terminal of the recipient account.

In one embodiment, a method of operating a terminal using an instant messaging service includes the steps of requesting transmission of a wish request message requesting the registration of an item in a wish list corresponding to a recipient account, selecting whether or not to send the wish request message anonymously, receiving a message notifying the registration of the wish list via a first type of chat room if the wish request message is sent anonymously, and receiving a message notifying the registration of the wish list via a second type of chat room if the wish request message is sent using a real name.

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

The wish request message can be generated based on at least one of a predefined template and text entered by the user.

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 sent anonymously, sends the wish request message sent anonymously to a terminal of the recipient account via a first type of chat room, sends the wish request message sent to a real name to a terminal of the recipient account via a second type of chat room, and, if registration of a wish list of the recipient account through the wish request message is detected, sends a message to a terminal of a sender account of the wish request message notifying the registration of the wish list.

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

A terminal using an instant messaging service according to one embodiment includes at least one processor that requests the sending of a wish request message requesting the registration of an item in a wish list corresponding to a recipient account, selects whether or not the wish request message is to be sent anonymously, receives a message notifying the registration of the wish list via a first type of chat room if the wish request message is sent anonymously, and receives a message notifying the registration of the wish list via a second type of chat room if the wish request message is sent using a real name.

In the following embodiment, a wishlist-related feature can be provided that allows users to request anonymously or with their real name to add functional gift items to their wishlist using instant messaging.

In the following embodiment, a wishlist-related function can be provided that uses instant messaging to receive notifications that gift items have been added to the wishlists of other user accounts.

FIG. 1 illustrates an overview of a system for instant messaging services according to one embodiment. 4 is a flowchart of a method of operating a server providing an instant messaging service according to an embodiment. 4 is a flowchart of a method of operating a server providing an instant messaging service according to an embodiment. 11A and 11B are diagrams illustrating a method for transmitting a wish request message and a message notifying registration of a wish list using a wish request list according to an embodiment. 4 is a flowchart of a method of operating a terminal using an instant messaging service according to an embodiment. FIG. 13 is a diagram illustrating an example of a screen for requesting transmission of a wish request message output to a terminal of a sender account. FIG. 13 is a diagram illustrating an example of a screen for requesting transmission of a wish request message output to a terminal of a sender account. FIG. 13 is a diagram illustrating an example of a screen for selecting a transmission type of a wish request message output to a terminal of a sender account. FIG. 13 is a diagram illustrating an example of a screen for selecting a transmission type of a wish request message output to a terminal of a sender account. FIG. 13 is a diagram illustrating an example of a screen of a chat room to which a wish request message is sent, which is output to a terminal of a recipient account. FIG. 13 is a diagram illustrating an example of a screen of a chat room to which a wish request message is sent, which is output to a terminal of a recipient account. FIG. 13 is a diagram illustrating an example of a screen for registering an item in a wish list output to a terminal of a recipient account. FIG. 13 is a diagram illustrating an example of a chat room screen in which a message notifying the registration of a wish list is sent, the message being output to the terminal of the sender's account. FIG. 13 is a diagram illustrating an example of a chat room screen in which a message notifying the registration of a wish list is sent, the message being output to the terminal of the sender's account. FIG. 13 is a diagram for explaining a wish request message including a gift candidate list. FIG. 13 is a diagram for explaining a wish request message including a gift candidate list. FIG. 13 is a diagram for explaining a wish request message including a gift candidate list. FIG. 13 is a diagram illustrating an example in which a message notifying registration of a wish list is transmitted. FIG. 13 is a diagram illustrating an example in which a message notifying registration of a wish list is transmitted. 1 is a diagram illustrating a hardware configuration of a system for an instant messaging service according to an embodiment;

Specific structural or functional descriptions of the embodiments are disclosed for illustrative purposes only and may be modified in various forms. Therefore, the embodiments are not limited to the specific disclosed forms, and the scope of this specification includes modifications, equivalents, or alternatives within the technical concept.

Although terms such as first or second may be used to describe multiple components, such terms should be construed as being only for the purpose of distinguishing one component from the other components. For example, a first component may be named a second component, and similarly, a second component may be named a first component.

When a component is referred to as being "coupled" or "connected" to another component, it should be understood that the component is directly coupled or connected to the other component, but that there may be other components in between.

Singular expressions include plural expressions unless the context clearly indicates otherwise. In this specification, terms such as "include" or "have" indicate the presence of features, numbers, steps, operations, components, parts, or combinations thereof described in the specification, and should be understood as not precluding the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.

Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the art to which the present invention belongs. Terms commonly used and predefined should be interpreted to have a meaning consistent with the meaning they have in the context of the relevant art, and should not be interpreted as having an ideal or overly formal meaning unless expressly defined in this specification.

Hereinafter, the embodiments will be described in detail with reference to the accompanying drawings. When describing the embodiments with reference to the drawings, the same components are given the same reference numerals regardless of the drawing numerals, and duplicate descriptions thereof will be omitted.

FIG. 1 is a diagram illustrating an overview of a system for an instant messaging service according to one embodiment.

Referring to FIG. 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 configurations of the server 120 and the terminal 110 are described in detail below.

The server 120 according to one embodiment includes a server that provides an instant messaging service via the network 130. As an example, the server 120 may include a server that provides an instant messaging service related to a wishlist. 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, media files, etc. in real time via the network 130 such as the wireless Internet or a wireless communication network, and related services.

The server 120 may be linked to an application (hereinafter, an app) related to the instant messaging service or a web related to the instant messaging service executed on the terminal 110 for a user interface (UI), function, operation, or service, etc. Hereinafter, the app related to the instant messaging service or the web related to the instant messaging service will be referred to as an instant messenger.

The terminal 110 may include, for example, a personal computer (PC), a netbook, a notebook, a personal digital appliance (PDA), a smartphone, a wearable device, and various other devices that perform similar functions.

The terminal 110 may be driven by an instant messenger provided by the server. A user may run the instant messenger on the terminal 110 and use an instant messaging service provided by the server 120. A user may subscribe to an instant messaging service via the instant messenger to create a user account. A user may use the instant messaging service via a terminal 110 of an account subscribed to the instant messaging service. A terminal 110 of an account subscribed to an instant messaging service refers to a terminal logged in with an account subscribed to the instant messaging service.

The server 120 according to an embodiment may be linked to a gift service or a gift server. The server 120 may provide a gift service linked to an instant messaging service, or may provide a gift service linked to a gift server that provides a gift service. The gift service refers to a service that purchases a product based on a social commerce platform, designates a recipient of the product, and transmits the product to the recipient. For example, information that a product has been purchased through the "gift" service and information that a gift has been sent may be shared between the purchaser and the recipient through a chat room provided by the instant messaging service. For example, a user may connect to the "gift" service through an instant messenger. The user may use the "gift" service using an account subscribed to the instant messaging service. Alternatively, the user may use the instant messaging service using an account subscribed to the "gift" service.

According to one embodiment, the "Gift" service may provide a wish-list function for storing desired products. A wish-list may be generated corresponding to an account subscribed to the "Gift" service or the instant messaging service. A wish-list corresponding to a particular account may be shared with other user accounts registered with the particular account (e.g., accounts registered as friends). In other words, a terminal logged in with a user's account may access wish-lists corresponding to other user accounts registered as friends. Accessing a wish-list means accessing a wish-list interface that provides information about items included in the wish-list and provides functions related to the wish-list (e.g., a function for adding an item to the wish-list, a function for "gifting" an item included in the wish-list, etc.).

According to one embodiment, the server 120 provides an instant messaging service for wishlists, and a user can use the instant messaging service for wishlists through a terminal logged in with an account subscribed to the instant messaging service. The instant messaging service for wishlists is described in more detail below.

Figure 2 is a flowchart of a method of operation of a server providing an instant messaging service according to one embodiment.

Referring to FIG. 2, the operation method of the server includes step S210 of determining whether the wish request message sent to the recipient account is sent anonymously. The wish request message is a message requesting to register a product in 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 called the sender account, and the account designated as the recipient of the wish request message is called the recipient account.

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

According to an embodiment, the wish request message may be determined to have a transmission type. The transmission type may be selected when requesting transmission of the wish request message. The transmission type of the wish request message may be determined by the sender account. The transmission type may include an anonymous transmission type and a real name transmission type. Determining whether the wish request message is anonymously transmitted means determining whether the transmission type of the wish request message is an anonymous transmission type or a real name transmission type. If the wish request message is transmitted anonymously or is of the anonymous transmission type, the wish request message transmitted to the terminal of the recipient account may not include information of the sender account. The information of the sender account may include, for example, an identifier of the sender account as information for identifying the sender account. If the wish request message is transmitted to a real name or is of the real name transmission type, the wish request message transmitted to the terminal of the recipient account may include information of the sender account.

An operating method of the server according to one embodiment includes step S220 of sending a wish request message sent anonymously to a terminal of the recipient account via a first type of chat room, and step S230 of sending a wish request message sent to a terminal of the recipient account via a second type of chat room, the wish request message sent to the real name.

A channel is an official account for a company or service, and is an account type that is distinct from general accounts. A channel chat room is a chat room in which official accounts and general user accounts participate, and is distinct from general chat rooms in which general user accounts participate. As an example, a channel chat room is a chat room in which official accounts send informational or advertising messages about a company or service. On the other hand, a general chat room is a chat room in which chats are exchanged between participating user accounts via messages.

The first type of chat room includes a chat room of a channel related to a service. For example, the first type of chat room may include a chat room of a channel related to an instant messaging service or a channel related to a "gift-giving" service. The anonymously submitted wish request message is sent to the first type of chat room as a message originating from an official account related to the instant messaging service or the "gift-giving" service.

The second type of chat room includes a chat room in which the recipient account and the sender account participate. For example, the second type of chat room may include a 1:1 chat room in which the recipient account and the sender account participate, or a group chat room in which the recipient account and the 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 that makes the sender account the sender.

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

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

As an example, a message notifying the receipt of another type of wish request message may be sent depending on the number of wish request messages sent anonymously to the recipient account. For example, if the number of wish request messages sent anonymously to the recipient account is 1 or more and 5 or less, a first type of message for notifying the receipt of the wish request message may be sent, and if the number of wish request messages sent anonymously to the recipient account is 6 or more and 10 or less, a second type of message for notifying the receipt of the wish request message may be sent. The second type of message for notifying the receipt of the wish request message may include text and/or visual symbols to more strongly encourage the recipient account to register for a wish list than the first type of message.

According to one embodiment, the wish request message may include a link connected to a wish list corresponding to the recipient account. A terminal of the recipient account may access the wish list corresponding to its account via the wish request message. A user of the recipient account may add items to the wish list via the terminal.

An operation method of the server according to an embodiment includes a step S240 of sending a message to the terminal of the sender account of the wish request message notifying the registration of the wish list when the registration of the wish list of the recipient account through the wish request message is detected. The server may detect that an item is added to the wish list corresponding to the recipient account. The server may detect a case where the terminal of the recipient account accesses the wish list through the wish request message and adds an item to the wish list, and a case where the terminal of the recipient account accesses the wish list through a different route and adds an item to the wish list. When the server detects that the terminal of the recipient account accesses the wish list through the wish request message and adds an item to the wish list, it sends a message to the terminal of the sender account of the wish request message notifying the registration of the wish list.

According to one embodiment, when the server detects the registration of a wish list of a recipient account through a wish request message, the server transmits a message notifying the registration of the wish list to the terminal of one or more sender accounts that sent a wish request message to the terminal of the recipient account before the detection time. As an example, when multiple wish request messages including a first wish request message and a second wish request message are sent to the recipient account, the user of the recipient account may access the wish list through the first wish request message and add an item. The server may transmit a message notifying 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 a wish request message to the recipient account at the detection time. A method of transmitting a message notifying the registration of a wish list when multiple wish request messages are sent to the recipient account will be described in detail below.

The message notifying the registration of the wish list includes a message notifying the recipient account that an item has been added to the wish list corresponding to the recipient account. According to one embodiment, the message notifying the registration of the wish list may include a link connected to the wish list corresponding to the recipient account. The terminal of the sender account may access the wish list corresponding to the recipient account via the message notifying the registration of the wish list. The user of the sender account may view the item that has been added to the wish list corresponding to the recipient account.

In one embodiment, step S240 of sending a message notifying the registration of a wish list includes a step of sending a message notifying the registration of a wish list to a terminal of the sender account via a chat room of a first type if the wish request message is sent anonymously, and a step of sending a message notifying the registration of a wish list to a terminal of the sender account via a chat room of a second type if the wish request message is sent using a real name.

According to one embodiment, the method of operating the server includes a step of providing information on the number of wish request messages sent to the terminal of the recipient account. As an example, only information on the number of wish request messages sent anonymously may be provided to the terminal of the recipient account, or only information on the number of wish request messages sent to real names may be provided. As an example, information on the number of wish request messages sent anonymously and information on the number of wish request messages sent to real names may be provided to the terminal of the recipient account. As an example, the total number of wish request messages sent anonymously and the number of wish request messages sent to real names may be provided to the terminal of the recipient account.

According to one embodiment, the wish request message quantity information may be initialized by registering the wish list of the recipient account through the wish request message.

Figure 3 is a flowchart of a method of operation of a server providing an instant messaging service according to one embodiment.

Referring to FIG. 3, the operation method of the server includes a 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 the wish request message. The wish request list may store information regarding the sender account of the wish request message and the sending type of the wish request message.

An operating method of the server according to one embodiment includes providing information on the number of wish request messages stored in the wish request list to the terminal of the recipient account. If the number of wish request messages stored in the wish request list is n, the server provides information that n wish request messages have been received to the terminal of the recipient account.

An operating method of the server according to one embodiment includes a step S320 of detecting wish list registration through at least one wish request message stored in the wish request list.

The operation method of the server according to one embodiment includes a step S330 of sending a message notifying the registration of the wish list to a terminal of a 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 a terminal of the sender account of each of at least one wish request message stored in the wish request list at the time the registration of the wish list is detected.

In one embodiment, step S330 of sending a message notifying the registration of a wish list includes a step of determining whether or not each of at least one wish request message stored in the wish request list is sent anonymously, a step of sending a message notifying the registration of a wish list to a terminal of a sender account of the anonymously sent wish request message via a first type of chat room, and a step of sending a message notifying the registration of a wish list to a terminal of a sender account of the wish request message sent to a real name via a second type of chat room.

The operation method of the server according to one embodiment includes a step S340 of initializing a wish request list. When a message notifying the registration of a wish list is sent to a terminal of a 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 store wish request messages sent to a recipient account after the registration of a wish list through a wish request message is detected.

For example, referring to FIG. 4, a first wish request message sent by a first sender account, a second wish request message sent by a second sender account, and a third wish request message sent by a third sender account may be received at a terminal of a recipient account. A wish request list 410 corresponding to the recipient account may store the three received wish request messages.

When the registration of a wish list of the recipient account through at least one of the three wish request messages is detected 420, a message notifying the registration of the wish list is sent to the terminal of the first sender account, the terminal of the second sender account, and the terminal of the third sender account. Depending on the sending type of each of the three wish request messages, the type of chat room to which the message notifying the registration of the wish list is sent can be determined. As an example, if the first wish request message is sent anonymously, the terminal of the first sender account may be sent a message notifying the registration of the wish list via a first type of chat room. As an example, if the second wish request message is sent to a real name, the terminal of the second sender account may be sent a message notifying the registration of the wish list via a second type of chat room.

When a message notifying the registration of a wish list is sent to the terminal of the sender account, the wish request list 430 corresponding to the recipient account is initialized.

Figure 5 is a flowchart of a method of operating a terminal using an instant messaging service according to one embodiment.

As an example, a terminal using an instant messaging service may include a terminal of the sender account of the wish request message or a terminal logged in with the sender account.

Referring to FIG. 5, the method of operating the terminal includes step S510 of requesting transmission of a wish request message requesting registration of an item in a wish list corresponding to a recipient account.

According to one embodiment, the wish request message is generated based on at least one of a predetermined template and a text input by the user. The predetermined template may include at least one of a predetermined text, a predetermined visual symbol, an arrangement of the text and/or visual symbol, and a predetermined style of the message (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 may be generated that is configured from a template selected by the user from among the provided templates. The template may be edited by the user. For example, the predetermined text included in the template may be changed by the user. As an example, a wish request message may be generated that includes text input by the user.

The method of operating the terminal includes step S520 of selecting whether or not to transmit the wish request message anonymously. Depending on the selection of whether or not to transmit anonymously, the wish request message may be transmitted anonymously or to the terminal of the user account using the user's real name.

The method of operating the terminal includes step S530 of receiving a message notifying the registration of the wish list through a first type of chat room if the wish request message is sent anonymously, and step S540 of receiving a message notifying the registration of the wish list through a second type of chat room if the wish request message is sent using a real name.

Figures 6A and 6B are diagrams illustrating examples of screens for requesting the sending of a wish request message that are output to the terminal of the sender account.

According to one embodiment, the terminal of the sender account executes a "send present" function by designating a recipient account. By executing the "send present" function for the designated recipient account, an interface for sending a present to the recipient account may be provided on the terminal of the sender account, as shown in screen 601 in FIG. 6A and screen 602 in FIG. 6B.

Referring to the screen 601 shown in FIG. 6A, the interface for sending a gift to a recipient account includes a wish list 610 corresponding to the recipient account. In other words, the terminal of the sender account may access the wish list 610 corresponding to the recipient account by executing a "send gift" function for the recipient account. The wish list 610 includes an interfacing object 611 for requesting the sending of a wish request message. As an example, an input for selecting the interfacing object 611 corresponds to an input for requesting the server to send a wish request message to the recipient account.

Referring to the screen 602 shown in FIG. 6B, a wish list 620 corresponding to a recipient account includes items 622 registered by the recipient account. When at least one item 622 is registered in the wish list 620, an interfacing object 621 may also be provided for requesting transmission of a wish request message via the wish list 620.

As described above, the wish request message can be sent as a transmission type, either anonymously or to a real name. Depending on the transmission type of the wish request message, the wish request message can be sent to the terminal of the recipient account via a first type chat room or a second type chat room. As an example, when an input is received to select the interfacing object 611, 621 for requesting the sending of the wish request message, a screen for selecting the transmission type of the wish request message (e.g., screen 701 shown in FIG. 7A or screen 702 shown in FIG. 7B) can be output to the terminal of the sender account.

Figures 7A and 7B are diagrams illustrating examples of screens for selecting the sending type of the wish request message to be output to the sender account terminal.

According to one embodiment, the terminal of the originator account that requested the transmission of the wish request message may select a transmission type for the wish request message. As described above, the transmission types for the wish request message include an anonymous transmission type and a real-name transmission type.

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

Referring to the screen 701 shown in FIG. 7A, the screen 701 may include an interfacing object 730 for requesting the transmission of a wish request message whose transmission type has been determined. As described above, the wish request message of the real-name transmission type may be transmitted through a second type of chat room in which the recipient account and the sender account participate. The interfacing object 730 for requesting the transmission of the wish request message of the real-name transmission type includes information indicating the type of chat room in which the wish request message is transmitted. For example, the interfacing object 730 may include information indicating the type of chat room in which the wish request message is transmitted to a 1:1 chat room. By inputting to select the interfacing object 730, the wish request message generated in the form displayed in the preview window 720 can be transmitted to the terminal of the recipient account.

Referring to the screen 702 shown in FIG. 7B, the sending type of the wish request message may be determined as an anonymous sending type by inputting a selection of an interfacing object 740 for selecting a sending type of the wish request message. The wish request message of anonymous sending type is displayed via a preview window 750 that previews the wish request message to be sent to the recipient account.

According to one embodiment, the preview window 750 in which the wish request message of anonymous transmission type is displayed may not provide an editing function for the message template. The template of the wish request message corresponding to a predetermined anonymous transmission type is not changed by user input, and the wish request message of anonymous transmission type may be generated based on the predetermined template. By not providing an editing function for the wish request message of anonymous transmission type, the risk of abusing using the wish request message sent anonymously can be prevented.

Referring to the screen 702 shown in FIG. 7B, the screen 702 includes an interfacing object 760 for requesting the transmission of a wish request message whose transmission type has been determined. As described above, the wish request message of the anonymous transmission type may be transmitted through a chat room of the first type of the channel related to the service. The interfacing object 760 for requesting the transmission of the wish request message of the anonymous transmission type may include information indicating the type of the chat room to which the wish request message is transmitted. For example, the interfacing object 760 may include information indicating the type of the chat room to which the wish request message is transmitted to a chat room of the channel related to the "gift" service. By inputting the selection of the interfacing object 760, the wish request message generated in the form displayed in the preview window 750 can be transmitted to the terminal of the recipient account.

Figures 8A and 8B are diagrams illustrating examples of chat room screens to which a wish request message is sent, which are output to the terminal of the recipient account.

Referring to the screen 801 shown in FIG. 8A, a wish request message 810 of the send type of real name may be sent to a terminal of a recipient account through a 1:1 chat room with the sender account. The wish request message 810 sent to a real name may be sent as a message with the sender account as the sender. For example, in a chat window corresponding to the 1:1 chat room with the sender account, an identifier 820 of the sender account is displayed adjacent to the wish request message 810 sent to the real name. Through the display of the identifier 820 of the sender account, it is indicated that the wish request message 810 sent to the real name is a message sent by the sender account.

Referring to the screen 802 shown in FIG. 8B, a wish request message 830 of anonymous transmission type is sent to a terminal of a recipient account via a chat room of a channel related to the "Give as a Gift" service. The anonymously sent wish request message 830 may be sent to a message with an official account related to the "Give as a Gift" service as the sender. For example, an official account identifier 840 may be displayed adjacent to the anonymously sent wish request message 830 in a chat window corresponding to a chat room of a channel related to the "Give as a Gift" service. Information of the sender account that requested the sending of the anonymously sent wish request message 830 may not be exposed to the terminal of the recipient account.

In one embodiment, a wish request message 810, 830 sent to a terminal of a recipient account includes a link connected to a wish list corresponding to the recipient account. The wish request message 810, 830 includes an interfacing object 811, 831 corresponding to the link connected to the wish list. An input selecting the interfacing object 811, 831 may cause the terminal of the recipient account to access the wish list corresponding to the recipient account. As an example, a screen for registering an item to the wish list (e.g., screen 901 shown in FIG. 9) may be output to the terminal of the recipient account that has accessed the wish list corresponding to the recipient account.

Figure 9 shows an example of a screen for registering an item to a wish list that is output to the recipient account's terminal.

According to one embodiment, the terminal of the recipient account can access a wish list corresponding to the recipient account and register or add an item to the wish list. The terminal of the recipient account can access the wish list via a received wish request message or can access the wish list via another path.

Referring to screen 901 shown in FIG. 9, a wish list 910 is displayed on the terminal of the recipient account. Items selected as wish items by the recipient account may be registered in wish list 910. If there are no items registered in wish list 910, an indication is displayed that there are no items registered in wish list 910.

According to one embodiment, information on the number of wish request messages sent to the terminal of the recipient account may be provided. For example, a notification message 930 may be provided indicating the number of sender accounts that have sent wish request messages to the recipient account. If registration of a wish list of the recipient account through 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 notification message 930 is modified to indicate the number of sender accounts that have sent wish request messages to the recipient account as 0.

Referring to the screen 901 shown in FIG. 9, a recommended item list 920 is provided to the terminal of the recipient account. The recommended item list 920 may include an interfacing object 921 for registering an item to a wish list. An input to select the interfacing object 921 may cause an item corresponding to the interfacing object 921 to be registered to the wish list 910.

According to one embodiment, the recommended item list 920 may include a plurality of recommended item lists corresponding to various types. For example, recommended item lists may be provided according to characteristics such as the age (e.g., 20s, 30s) of the user to whom the gift is to be provided, gender, and relationship to the person giving the gift (e.g., friend, girlfriend, boyfriend, parents). For example, recommended item lists may be provided according to the purpose of the gift, such as wedding gifts, housewarming gifts, birthday gifts, light gifts, and holiday gift sets.

According to one embodiment, the recommended item list 920 may include a user-customized recommended item list. The recommended item list 920 may include items that are expected to be registered in the user's wishlist by analyzing data collected from the user. For example, the user-customized 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 registered in the wishlist, and characteristic data such as the user's age, gender, and place of residence.

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

Figures 10A and 10B are diagrams illustrating examples of chat room screens in which a message notifying a wishlist registration is sent and output to the sender's account terminal.

Referring to the screen 1001 shown in FIG. 10A, when a wish request message 1010 is sent to a real name by a sender account, a message 1020 notifying the wish list registration is sent to the terminal of the sender account through a 1:1 chat room with the recipient account. The message 1020 notifying the wish list registration may be sent through the same chat room as the chat room in which the wish request message 1010 sent to the real name was sent. The message 1020 notifying the wish list registration may be sent in a message with the recipient account of the wish request message 1010 as the sender. For example, a recipient account identifier 1030 may be displayed adjacent to the message 1020 notifying the wish list registration in a chat window corresponding to the 1:1 chat room with the recipient account. Through the display of the recipient account identifier 1030, it is indicated that the message 1020 notifying the wish list registration is a message sent by the recipient account.

Referring to the screen 1002 shown in FIG. 10B, when a wish request message is sent anonymously by a sender account, a message 1040 notifying the registration of a wish list may be sent to the terminal of the sender account through a chat room of a channel related to the “Give as a Gift” service. The message 1040 notifying the registration of a wish list may be sent through a chat room different from the chat room in which the anonymously sent wish request message was sent. The wish request message sent anonymously by the sender account may be sent through a chat room of a channel related to the “Give as a Gift” service in which the recipient account participates. On the other hand, the message 1040 notifying the registration of a wish list may be sent to a message whose sender is an official account related to the “Give as a Gift” service. For example, an identifier 1050 of the official account may be displayed adjacent to the message 1040 notifying the registration of a wish list sent anonymously in a chat window corresponding to a chat room of a channel related to the “Give as a Gift” service.

In one embodiment, a message 1030, 1040 notifying the registration of a wish list sent to a terminal of a sender account includes a link connected to a wish list corresponding to a recipient account. The message 1030, 1040 notifying the registration of a wish list includes an interfacing object 1021, 1041 corresponding to a link connected to the wish list. By inputting to select an interfacing object 1021, 1041, the terminal of the sender account may access the wish list corresponding to the recipient account. As an example, a wish list including items registered by the recipient account may be output to the terminal of the sender account that has accessed the wish list corresponding to the recipient account.

Figures 11A to 11C are diagrams illustrating a wish request message that includes a gift candidate list.

According to one embodiment, the wish request message includes a gift candidate list including 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 candidate list provided via the wish request message. The terminal of the sender account may select items to be included in the gift candidate list.

Referring to screen 1101 shown in FIG. 11A, upon input of selecting interfacing object 1110 for requesting the generation of a gift candidate list, screen 1102 shown in FIG. 11B for generating a gift candidate list is provided on the sender account terminal.

According to one embodiment, the gift candidate list may be included in the wish request message regardless of the transmission type of the wish request message, or may be set to include the gift candidate list only in wish request messages of the real name transmission type. As an example, in order to prevent the risk of abusing using wish request messages transmitted anonymously, the provision of the gift candidate list may be restricted for wish request messages of the anonymous transmission type.

Referring to screen 1102 shown in FIG. 11B, the sender account terminal can select at least one item to be included in the gift candidate list. The server generates a gift candidate list including at least one item selected from the sender account terminal. A wish request message including the generated gift candidate list may be sent to the recipient account terminal. As an example, the wish request message may include a link connected to the gift candidate list.

Referring to screen 1103 shown in FIG. 11C, the terminal of the recipient account accesses the gift candidate list 1120 via a wish request message including the gift candidate list. The terminal of the recipient account may register at least one item included in the gift candidate list 1120 as a wish list. For example, by inputting a selection of an interfacing object 1121 for selecting an item included in the gift candidate list 1120, the selected item may be registered as a wish list corresponding to the recipient account.

Figures 12A and 12B are diagrams illustrating an example of sending a message notifying a user of a wishlist registration.

Screen 1201 shown in FIG. 12A corresponds to a wishlist interface that is output to a terminal that has accessed a wishlist corresponding to a personal account. A wishlist corresponding to a personal account means a wishlist corresponding to an account logged in to a terminal. An account logged in to a terminal on which screen 1201 is output is referred to as a first account.

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

As an example, the other accounts to which the message notifying the registration of the wish list is sent may include the account that requested the first account to send a wish request message. The server may send a message notifying the registration of the wish list to the terminal of the sender account of the wish request message received by the first account by an input of selecting the interfacing object 1210 received from the terminal. As described above, the server may automatically send a message to the terminal of the sender account of the wish request message when wish list registration through the wish request message is detected. According to one embodiment, the server may send a message notifying the registration of the wish list to the terminal of the sender account at the time when the terminal of the first account leaves the screen 1201 when wish list registration through the wish request message is detected.

As an example, the other accounts to which the message notifying the wishlist registration is sent may include accounts selected by the first account as recipients of the message notifying the wishlist registration.

According to one embodiment, the interfacing object 1210 may be activated when one or more items are added to the wish list. If there are no items added to the wish list, the interfacing object 1210 may be deactivated. In other words, only if one or more items are added to the wish list, an input selecting the interfacing object 1210 sends a signal to the server requesting transmission of a message notifying the server of the addition of a wish list.

According to one embodiment, the terminal can access the wish list corresponding to the personal account from a route other than the wish request message. For example, referring to FIG. 12B, a message 1220 notifying the first account of an anniversary (e.g., birthday) set may be sent via a chat room of a channel related to the gift service. The server stores anniversary information corresponding to the first account. Anniversary information corresponding to the first account may be set by the user of the first account or may be extracted from information (e.g., date of birth information) entered when subscribing to the service. The server may send the message 1220 notifying the anniversary to the terminal of the first account via a chat room of a channel related to the "gift" service a preset time before the time set as the anniversary (e.g., 10 minutes before, one day before, one week before, etc.). The message 1220 notifying the anniversary includes a link to the wish list. The terminal of the first account can access the wish list of the personal account via the message 1220 notifying the anniversary. Also, for example, the terminal may perform the function of the gift service via an instant messenger. The device can execute the functions of the "Gift" service and access the wish list.

Even if an item is registered to a wish list by accessing the wish list via a route other than a wish request message, a message notifying the registration of the wish list may be sent to the terminal of another account in response to a request received from the terminal (e.g., an input to select interfacing object 1210).

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

Referring to FIG. 13, a system according to one embodiment (e.g., system 100 shown in FIG. 1) includes a terminal 110 (e.g., terminal 110 shown in FIG. 1) and a server 120 (e.g., server 120 shown in FIG. 1) connected via a network 130.

The terminal 110 according to one embodiment may be a mobile terminal implemented by a computer device. As an example, the terminal 110 may communicate with the server 120 and/or other electronic devices via the network 130 using a wireless or wired communication method.

The server 120 according to one embodiment may be embodied as a computer device or multiple computer devices that communicate with the terminal 110 and/or other servers via the network 130 and provide instructions, code, files, content, services, and the like. The communication method is not limited and may include a communication method that utilizes a communication network (e.g., a mobile communication network, a wired Internet, a wireless Internet, a broadcasting network) that includes the network 130, and a short-range wireless communication method between devices. For example, the network 130 may include any one or more of a personal area network (PAN), a local area network (LAN), a campus network (CAN), a metropolitan area network (MAN), a wide area network (WAN), a broadband network (BN), the Internet, and the like.

According to one embodiment, the server 120 may provide a file for installing an application to the terminal 110 connected via the network 130. In this case, the terminal 110 may install an application (e.g., an instant messenger) using the file provided by the server 120. In addition, the terminal 110 may connect to the server 120 and be provided with services and content provided by the server 120 under the control of an operating system (OS) and at least one program (e.g., a browser or an installed application) included in the terminal 110. For example, if the terminal 110 transmits a service request message to the server 120 via the network 130 under the control of an application, the server 120 transmits 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 the application.

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

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

The memories 1311 and 1321 may be volatile or non-volatile memories that are computer-readable recording media. According to an embodiment, the memories 1311 and 1321 may store information related to the instant messaging service described above with reference to FIGS. 1 to 12B. As an example, the memory 1321 of the server 120 may store account information subscribed to the instant messaging service and wish list information corresponding to the account.

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

In one embodiment, the memory 1321 may store a program that embodies operations for providing an instant messaging service executed by the server described above with reference to Figures 1 to 12B.

The communication modules 1315, 1325 in one embodiment provide the functionality for the terminal 110 and the server 120 to communicate with each other via the network 130, and can provide the functionality for communicating with other electronic devices or other servers.

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

As an example, control signals, instructions, content, files, etc. provided under the control of the processor 1323 of the server 120 may be received by the terminal 110 via the communication module 1315 of the terminal 110 via the communication module 1325 and the network 130.

The input/output interfaces 1317 and 1327 may be means for interfacing with the input/output device 1319. For example, the input device may include a device such as a keyboard or a mouse, and the output device may include a device such as a display for displaying a communication session of an application. As a different example, the input/output interface 1317 may be means for interfacing with a device in which functions for input and output are integrated into one, such as a touch screen. As a more specific example, when the processor 1313 of the terminal 110 processes the instructions of the computer program loaded in the memory 1311, a service screen or content configured using data provided by the server 120 may be displayed on the display via the input/output interface 1317. An input received from a user through the input/output device 1319 may be provided in a form processable by the processor 1313 of the terminal 110 via the input/output interface 1317.

According to an embodiment, the terminal 110 and the server 120 may include other components not shown in FIG. 13. For example, the terminal 110 may be implemented to include at least some of the input/output devices 1319 described above, or may further include other components such as a transceiver, a GPS (Global Positioning System) module, a camera, various sensors, a database, etc.

The embodiments described above may be embodied with hardware components, software components, and/or a combination of hardware and software components. For example, the adaptive supersampling devices, methods, and components described in the embodiments may be embodied using a general-purpose or 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 device capable of executing and responding to commands. The processing adaptive supersampling device may execute an operating system (OS) and software applications that run on the operating system. The processing adaptive supersampling device may also access, store, manipulate, process, and generate data in response to the execution of software. For ease of understanding, the processing adaptive supersampling device may be described as being one in use, but those skilled in the art will appreciate that the processing adaptive supersampling device may include multiple processing elements and/or multiple types of processing elements. For example, the processing adaptive supersampling device may include multiple processors or a processor and a controller. Other processing configurations, such as parallel processors, are also possible.

The software may include computer programs, codes, instructions, or any combination thereof, and may configure or independently or collectively instruct the process adaptive supersampling device as desired. 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 signal wave transmitted to be interpreted by the process adaptive supersampling device or to provide instructions or data to the process adaptive supersampling device. The software may be distributed over networked computer systems and stored or executed in a distributed manner. The software and data may be stored on a computer readable recording medium.

The method according to the present invention is embodied in the form of program instructions to be executed by various computer means and recorded on a computer-readable recording medium. The recording medium includes program instructions, data files, data structures, and the like, either alone or in combination. The recording medium and program instructions may be specially designed and constructed for the purposes of the present invention, or may be known and available to those skilled in the art of computer software technology. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical recording media such as CD-ROMs and DVDs, magneto-optical media such as floptical disks, and hardware devices specially configured to store and execute program instructions, such as ROMs, RAMs, flash memories, and the like. Examples of program instructions include not only machine language code, such as that generated by a compiler, but also high-level language code executed by a computer using an interpreter, etc.

The hardware adaptive supersampling devices 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.

Although the embodiments have been described above with reference to limited drawings, a person having ordinary skill in the art may apply various technical modifications and variations based on the above description. For example, the described techniques may be performed in a different order than described, and/or the components of the described systems, structures, devices, circuits, etc. may be combined or combined in a different manner than described, and may be replaced or substituted with other components or equivalents to achieve suitable results.

Therefore, other realizations, other embodiments, and equivalents to the claims are also within the scope of the claims described below.

Claims (21)

1. A method of operating a server providing an instant messaging service, comprising:
determining whether the wish request message sent to the recipient account is sent anonymously;
sending the anonymously sent wish request message to a terminal of the recipient account via a chat room of a first type;
Sending the wish request message sent to the real name to a terminal of the recipient account through a chat room of a second type;
when detecting a registration of a wish list of the recipient account through the wish request message, sending a message to a terminal of a sender account of the wish request message notifying the registration of the wish list;
A method comprising: the first type of chat room includes a chat room for a channel related to the service;
The method of claim 1 , wherein the second type of chat room includes a chat room in which the recipient account and the originator account participate. The step of transmitting via the first type chat room includes:
counting the number of said wish request messages sent anonymously to said recipient account;
sending a message acknowledging receipt of the wish request message through the first type chat room based on the number of the wish request messages sent anonymously to the recipient account;
The method of claim 1 , comprising: The step of sending a message notifying the registration of the wish list includes:
If the wish request message is sent anonymously, sending a message notifying the registration of the wish list to a terminal of the sender account via the first type chat room;
sending a message notifying the registration of the wish list to a terminal of the sender account through the second type chat room if the wish request message is sent to a real name;
The method of claim 1 , comprising: The method of claim 1, further comprising providing information on the number of wish request messages sent to the recipient account terminal. The method of claim 5, wherein the wish request message count information is initialized by registration of a wish list of the recipient account through the wish request message. The method of claim 1, wherein the wish request message includes a gift wish list that includes at least one item selected by the sender account. The method of claim 1, wherein the wish request message includes a link connected to a wish list corresponding to the recipient account. The method of claim 1, wherein the message notifying the registration of the wish list includes a link connected to a wish list corresponding to the recipient account. The method of claim 1, further comprising receiving a request to send the wish request message from a terminal of the sender account that has accessed a wish list corresponding to the recipient account. 1. A method of operating a server providing an instant messaging service, comprising:
storing at least one wish request message sent to a recipient account in a wish request list corresponding to said recipient account;
detecting a wish list registration through at least one wish request message stored in the wish request list;
sending a message to a terminal of a sender account of at least one wish request message stored in the wish request list to notify the registration of the wish list;
initializing said wish request list;
A method comprising: The step of sending a message notifying the registration of the wish list includes:
determining whether each of said at least one wish request message is sent anonymously;
sending a message notifying the registration of the wish list to a terminal of a sender account of the anonymously sent wish request message via a first type chat room;
sending a message notifying the registration of the wish list to a terminal of a sender account of the wish request message sent to the real name through a second type chat room;
The method of claim 11 , comprising: the first type of chat room includes a chat room for a channel related to the service;
The method of claim 12 , wherein the second type of chat room includes a chat room in which the recipient account and the originator account participate. The method of claim 11, further comprising providing information on the number of wish request messages stored in the wish request list to the terminal of the recipient account. A method of operating a terminal using an instant messaging service, comprising:
requesting transmission of a wish request message requesting the item to be added to a wish list corresponding to the recipient account;
selecting whether or not to transmit the wish request message anonymously;
receiving a message notifying the registration of the wish list via a chat room of a first type if the wish request message is sent anonymously;
receiving a message notifying the registration of the wish list via a second type chat room if the wish request message is sent to a real name;
A method comprising: the first type of chat room includes a chat room for a channel related to the service;
The method of claim 15 , wherein the second type of chat room includes a chat room in which the recipient account and an account logged into the terminal participate. The method of claim 15, wherein the wish request message is generated based on at least one of a predefined template and user-entered text. A computer program stored on a medium for executing the method according to any one of claims 1 to 17 in combination with hardware. A server providing an instant messaging service,
Determine whether the wish request message sent to the recipient account is anonymous;
Sending the anonymously transmitted wish request message to a terminal of the recipient account via a chat room of a first type;
Sending the wish request message sent to the real name to a terminal of the recipient account via a chat room of a second type;
when detecting a registration of a wish list of the recipient account through the wish request message, sending a message to a terminal of a sender account of the wish request message notifying the registration of the wish list;
A server comprising at least one processor. A server providing an instant messaging service,
storing at least one wish request message sent to a recipient account in a wish request list corresponding to said recipient account;
Detecting a wish list registration through at least one wish request message stored in the wish request list;
Sending a message to a terminal of a sender account of at least one wish request message stored in the wish request list to notify the registration of the wish list;
initializing the wish request list;
A server comprising at least one processor. A terminal using an instant messaging service, comprising:
requesting the sending of a wish request message requesting the addition of the item to a wish list corresponding to the recipient account;
Select whether or not to send the wish request message anonymously;
receiving a message notifying the registration of the wish list via a chat room of a first type if the wish request message is sent anonymously;
receiving a message notifying the registration of the wish list via a second type of chat room if the wish request message is sent to a real name;
A terminal including at least one processor.

Images