Method of displaying profile view in instant messaging service

Abstract

The method of operation of the terminal may include the step of displaying a profile item associated with a status message object registered in correspondence with the account in a profile view of the account—the profile item comprising at least one of a first item for transmitting product data to the account or a second item for interacting with the account—when receiving input associated with the first item, the step of displaying a product purchase view; and the step of transmitting first product data corresponding to a product determined based on user input received through the product purchase view to a server.

Description

Technology Field

[0001] The following embodiments relate to a method and apparatus for displaying a profile view in an instant messaging service. Background Technology

[0002] With the emergence of various smart devices, including smartphones, diverse forms of Social Network Services (SNS) utilizing these devices are being used. In particular, instant messaging applications, where multiple users create chat rooms and exchange messages in real time, are widely used. Chat services provided through these instant messaging applications are evolving to offer a wider range of features to meet user demands. Specifically, as the scope of services available through instant messaging applications expands, the potential for utilizing profile views to represent each user—going beyond simply providing profile images—is also increasing. As the potential for profile views grows, it becomes possible to provide services that allow users to interact with other users through these profile views.

[0003] In addition, as communication through smart devices increases, SNS services can support not only 1:1 communication with other users but also the function of exchanging gifts between users by combining with e-commerce platforms. means of solving the problem

[0005] A terminal according to one embodiment may display a profile item applied to the profile view of an account—the profile item includes at least one of a first item for transmitting product data to the account or a second item for interacting with the account.

[0006] A terminal according to one embodiment may display a product purchase view when it receives input related to a first item.

[0007] A terminal according to one embodiment can transmit first product data corresponding to a product determined based on user input received through a product purchase view to a server.

[0008] A product purchase view according to one embodiment includes recommended products, and the recommended products may be products determined based on at least one of a status message displayed in the account's profile view, a wish list of another account distinct from the account, or the account's product purchase history.

[0009] A profile item according to one embodiment may further include at least one of a third item displaying D-day date information or a fourth item displaying text.

[0010] According to one embodiment, the product purchase view may be displayed over the entire screen area of ​​the terminal or at least in a portion of the screen of the terminal with the profile view as the background.

[0011] The step of transmitting first product data to a server according to one embodiment may include: generating payment information corresponding to a product determined based on user input received through a product purchase view; and transmitting first product data to a server including at least one of information related to the product, gift message information, or payment information.

[0012] A terminal according to one embodiment can receive from a server second product data corresponding to the first product data—including at least one of information related to a determined product, account information of the terminal that transmitted the first product data, or gift message information.

[0013] A terminal according to one embodiment can display second product data in a chat room with a service provider account.

[0014] When a terminal according to one embodiment receives input related to a first item, it can determine whether the account corresponding to the terminal can purchase the product based on product purchase constraints.

[0015] A product purchase constraint according to one embodiment may include at least one of an age constraint, a country constraint, or an account activation status condition of an account corresponding to a terminal.

[0016] A terminal according to one embodiment can receive a record related to at least one second product data stored in a product holding database.

[0017] When a terminal according to one embodiment receives an input related to a second item, it can display a visual effect corresponding to the input on the screen.

[0018] A visual effect according to one embodiment may include an effect in which an emoticon is displayed at predetermined coordinates on the screen.

[0019] When a terminal according to one embodiment receives input related to a second item, it may display an emoticon input means on a screen in response to the input.

[0020] A terminal according to one embodiment can display an emoticon determined based on user input among the emoticons displayed on the emoticon input means at predetermined coordinates on the screen.

[0021] A terminal according to one embodiment can display an emoticon reception record received through a second item.

[0022] A server according to one embodiment can transmit product data to a second user terminal corresponding to an account through the account's profile view.

[0023] A server according to one embodiment can receive first product data corresponding to a product determined through a first item applied to the profile view of an account—the first item being a profile item for transmitting product data to the account—from a first user terminal.

[0024] A server according to one embodiment can generate second product data based on first product data.

[0025] A server according to one embodiment can transmit second product data to a second user terminal.

[0026] A server according to one embodiment can determine a product based on user input received through a product purchase view displayed on the screen of a first user terminal in response to an input related to a first item.

[0027] A server according to one embodiment can receive first product data corresponding to a determined product from a first user terminal.

[0028] According to one embodiment, the first product data may include at least one of information related to the determined product, gift message information, or payment information.

[0029] According to one embodiment, the second product data may include at least one of information related to the determined product, account information of the first user terminal, or gift message information. Brief explanation of the drawing

[0031] FIG. 1 is a flowchart illustrating a method of operation of a terminal for transmitting product data to another account through an account profile view according to one embodiment. FIG. 2 is a flowchart illustrating a method of operation of a server for transmitting product data to another account through an account profile view according to one embodiment. FIGS. 3a to 3d are drawings for explaining the process of transmitting product data according to one embodiment. FIG. 4 is a diagram illustrating the screen of a terminal that has received product data according to one embodiment. FIGS. 5a to 5c are drawings for explaining a method for sending emoticons to another account through a profile view according to one embodiment. FIGS. 6a and 6b are drawings for illustrating a screen displaying an emoticon reception record or a product data reception record according to one embodiment. FIG. 7 is a block diagram of an electronic device according to one embodiment. Specific details for implementing the invention

[0032] Specific structural or functional descriptions of the embodiments are disclosed for illustrative purposes only and may be modified and implemented in various forms. Accordingly, actual implementations are not limited to the specific embodiments disclosed, and the scope of this specification includes modifications, equivalents, or substitutions included in the technical concept described by the embodiments.

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

[0034] In this document, each of the phrases such as "A or B", "at least one of A and B", "at least one of A or B", "A, B or C", "at least one of A, B and C", and "at least one of A, B, or C" may include any one of the items listed together in the corresponding phrase, or all possible combinations thereof.

[0035] When it is stated that a component is "connected" to another component, it should be understood that it may be directly connected to or joined to that other component, or that there may be other components in between.

[0036] The singular expression includes the plural expression unless the context clearly indicates otherwise. In this specification, terms such as "comprising" or "having" are intended to specify the existence of the described features, numbers, steps, actions, components, parts, or combinations thereof, and should be understood as not precluding the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.

[0037] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as generally understood by those skilled in the art. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and should not be interpreted in an ideal or overly formal sense unless explicitly defined in this specification.

[0038] Hereinafter, embodiments will be described in detail with reference to the attached drawings. In the description with reference to the attached drawings, identical components are given the same reference numeral regardless of the drawing number, and redundant descriptions thereof will be omitted.

[0040] A server according to one embodiment may be, for example, a server that provides an Instant Messaging Service. The server may create accounts for a first user and a second user, respectively, and provide the Instant Messaging Service to the first user and the second user through a messenger application installed on the terminal of the first user and the terminal of the second user. The accounts may include, for example, at least one type among an official account and a personal account. A personal account is an account for general individual users. An official account is an account for utilizing additional functions associated with the Instant Messaging Service, and may include, for example, a corporate account for corporate users.

[0041] A server according to one embodiment may correspond to a service platform that provides instant messaging services to clients, such as corporate users and individual users. A messenger application may include, for example, a computer, database, module, or program operated to perform functions such as composing and sending text, sending multimedia content (voice, photos, videos, etc.), message notification, and scheduling.

[0042] According to one embodiment, a first user (or first account) and a second user (or second account) can access a server through a terminal on which a messenger application is installed. The first user and the second user may be individual users having personal accounts, or corporate users having official accounts.

[0043] The first user's terminal and the second user's terminal may include any user device capable of installing and running a messenger application associated with the service server (100), such as one of electronic devices including, for example, a computer, UMPC (Ultra Mobile PC), workstation, netbook, PDA (Personal Digital Assistants), portable computer, web tablet, wireless phone, mobile phone, smartphone, e-book, PMP (portable multimedia player), portable game console, navigation device, black box, or digital camera. Under the control of the messenger application, the terminal can perform operations throughout the instant messaging service, such as configuring the service screen, inputting data, transmitting and receiving data, and storing data.

[0044] A messenger application according to one embodiment is implemented to be usable in a PC (Personal Computer) environment as well as a mobile environment, and may be implemented as a program that operates independently or configured as an in-app of a specific application so that it can operate on said specific application.

[0045] As will be explained in detail below, an instant messaging service according to one embodiment may provide a technique to enhance the utility of a profile view provided on a messenger application. A 'profile view' is a service screen that displays a user's profile and may be displayed on a terminal screen, for example, as shown in the screen (300) of FIG. 3a below. The profile view may include, for example, a profile image and profile information provided in relation to the user's user account. The profile view according to one embodiment may go beyond simply including a profile image and profile information and may further include profile backgrounds or profile items that express the user in various ways. The profile view may include different information depending on the user's settings, for example.

[0046] According to one embodiment, at least one profile item may be provided in the profile view. The user can apply the profile item(s) collectively to their profile view. As will be described in detail below, the user can freely edit the profile item(s) applied to the profile view through the edit view.

[0047] A plurality of profile items and / or combinations thereof may be applied to a profile view of a personal account according to one embodiment. At least one profile item may include various types of items displayed through the profile view, such as, for example, a music item, a logo item, a sticker item, a text item, a link item, a background effect item, a countdown item, a background image item, a background video item, and a feedback item. A music item may include, for example, a playlist of audio sources played through the profile view and a display style of the playlist.

[0048] A profile item according to one embodiment may further include at least one of an item for at least one touch input-based interaction, an item for a slider input-based interaction, an item indicating the number of times another account has touched the profile item, or an item indicating the number of views of the profile.

[0049] A profile item according to one embodiment may further include at least one of a first item for transmitting product data to another account or a second item for interacting with another account. The second item for interacting with another account may include at least one of an item for touch input-based interaction or an item for slider input-based interaction.

[0050] A profile item according to one embodiment may further include at least one of a third item displaying D-day date information or a fourth item which is a text item displaying text. D-day may refer to a scheduled date for implementing a plan or the time remaining until said scheduled date.

[0051] The terminal may provide an edit view for editing at least one profile item applied to the profile view. The edit view may provide an editing function for applying the aforementioned at least one profile item to the profile view.

[0052] A server according to one embodiment may be linked with a gift-giving service or a gift-giving server. The server may provide a gift-giving service linked with an instant messaging service, or it may provide a gift-giving service by linking with a gift-giving server that provides a gift-giving service. A gift-giving service may refer to a service that purchases a product based on a social commerce platform, designates a recipient of the product, and delivers the product to the recipient. For example, information that a product has been purchased or that a gift has been sent in the gift-giving service may be shared with the buyer (e.g., user of a first user terminal) and the recipient (e.g., user of a second user terminal) through a chat room provided by the instant messaging service. For example, a user may access the gift-giving service through an instant messenger. A user may use the gift-giving service by using an account registered with the instant messaging service. Alternatively, a user may use the instant messaging service by using an account registered with the gift-giving service.

[0053] According to one embodiment, the gifting service may provide a wishlist function for storing desired products. The wishlist may be created in correspondence with an account subscribed to the gifting service or the instant messaging service. A wishlist corresponding to a specific account may be shared with other users' accounts registered to that specific account (e.g., accounts registered as friends). In other words, a terminal logged in with a user's account may access a wishlist corresponding to another user's account registered as a friend. Accessing a wishlist may mean accessing a wishlist interface that provides information about the items included in the wishlist and provides functions related to the wishlist (e.g., a function to add items to the wishlist, a function to gift items included in the wishlist, etc.).

[0054] FIG. 1 is a flowchart illustrating a method of operation of a terminal for transmitting product data through an account profile view according to one embodiment.

[0055] A terminal according to one embodiment can determine a profile item applied to an account's profile view and coordinates indicating the location where the profile item is provided in the profile view based on a received input signal.

[0056] According to one embodiment, the screen of a terminal may be represented in an xy coordinate system. For example, the horizontal axis of the screen may be the x-axis and the vertical axis of the screen may be the y-axis. The terminal may display various objects on the screen based on the screen's coordinate system. It may also receive user input based on the screen's coordinate system. When a location where a profile item is to be displayed on the screen is selected, the terminal may convert the selected location into coordinates of the screen's coordinate system. The terminal may transmit the corresponding coordinates to a server so that the server can know the coordinates indicating the location where the profile item is to be provided.

[0057] According to one embodiment, a user can select a profile item applied to a profile view. The user can also select a location in the profile view where the profile item will be displayed. A terminal corresponding to an account can receive input from the user regarding the result of selecting a profile item and the location where the profile item will be displayed. According to one embodiment, a server can receive an input signal from the terminal. For example, the server can receive information regarding the profile item selected by the user and the location (e.g., coordinates) where the profile item will be displayed in the profile view.

[0058] A server or terminal according to one embodiment may receive various forms of input for a profile item. For example, various forms of input may include a click, double click, long click, continuous click, touch, double touch, continuous touch at regular intervals, touching the profile item for a regular period of time, swipe, etc. Interaction may be performed through various forms of input, and the present disclosure is not limited thereto.

[0059] According to one embodiment, the second item may be an item that allows another account to express empathy based on the touch input of the item. For example, if the second item is displayed on the profile view of an account (e.g., the second account), the second item may be displayed on the profile view of the corresponding account (e.g., the second account) on the screen of another account (e.g., the first account). Then, the user of the other account (e.g., the first account) may touch (or click) the second item to empathize with the emotions of the corresponding account (e.g., the second account). The user of the other account (e.g., the first account) may touch (or click) the second item multiple times as the degree of empathy increases. Therefore, as the number of touches (or clicks) of the second item increases, it can be interpreted that the degree of empathy is greater.

[0060] A second item according to one embodiment may include an emoticon indicating an emotion. For example, the emoticon may be displayed together with an item indicating the number of times the second item has been touched (or clicked).

[0061] The entity performing the following operations is a processor (710), and the processor (710) may be included in a terminal (e.g., a first user terminal or a second user terminal) or in a server. Accordingly, the operations described below may be performed in a server or a terminal.

[0062] In step (110) according to one embodiment, the processor (710) of the terminal (e.g., the processor (710) of FIG. 7) may display a profile item applied to the profile view of the account. The profile item may include a status message object registered in correspondence with the account. The profile item may include at least one of a first item for transmitting product data to the account or a second item for interacting with the account. Referring to FIG. 3a, the first item (311) and the second item (312) may be displayed in the status message object (310).

[0063] According to one embodiment, the first item may be a profile item for transmitting product data to an account corresponding to a profile view. For example, the account profile view of the second user may be displayed on the screen of the first user terminal. The first user of the first user terminal can view the account profile view of the second user through the screen of the first user terminal. The first user may wish to gift a product to the second user. The first user may gift a product to the second user to empathize with the second user's status or to congratulate the second user on their status. In this case, the first user may gift a product to the second user by viewing the status message displayed on the profile view of the second user's account and selecting the first item displayed on the profile view. In response to the selection of the first item, the first user may select a product to gift to the second user through a product purchase view displayed on the screen. When the first user selects a product to gift to the second user, the first user terminal may generate product data related to the selected product and transmit it to the server. The server may then transmit the product data related to the selected product to the second user terminal.

[0064] For convenience of explanation, the terminal that purchases the product is referred to as the first user terminal, and the terminal that receives the purchased product is referred to as the second user terminal; however, the present disclosure is not limited thereto. Additionally, as a non-limiting example, product data transmitted from the first user terminal to the server is referred to as the first product data, and product data transmitted from the server to the second user terminal is referred to as the second product data; the present disclosure is not limited thereto.

[0065] A second item according to one embodiment may be an item for interacting with an account. A first user may empathize with or congratulate the second user on their status through the second item displayed in the second user's account profile view. A specific description related to the second item will be described later with reference to FIGS. 5a to 5c.

[0066] A profile item according to one embodiment may further include at least one of a third item displaying D-day date information or a fourth item displaying text. Referring to FIG. 3a, a fourth item (313) displaying text may be displayed in the status message object (310). For example, a status message "I finally got a job" may be displayed as text in the status message object (310). Referring to FIG. 3a, a third item (351) displaying D-day date information may be displayed in the status message object (350). For example, the third item (351) may be an item displaying the number of remaining days until D-day.

[0067] A profile view may be displayed on the screen (300) of FIG. 3a. And at least one of a status message object (310), a first item (311), a second item (312), a profile image (320), an account name (330), or text (340) may be displayed against the background of the profile view. The text (340) may be a text-based message that the user can input in the profile settings. In another embodiment, the status message object (310) may include at least one of a third item (351), a second item (352), or a first item (353).

[0068] A processor (710) of a terminal according to one embodiment may display a product purchase view on a screen when it receives input related to a first item. The product purchase view may be a view for purchasing products. The product purchase view may be a view displayed by an instant messaging application. The product purchase view may display products (or services, hereinafter, products may be used to include services) that can be gifted to other accounts. And, the processor (710) of the server may generate product data based on the products selected through the product purchase view. Referring to FIG. 3b, a profile view (360) and a status message object (310) are displayed on the screen (301). And, the processor (710) of the terminal may display a product purchase view (370) on the screen with the profile view (360) as the background. In the product purchase view (370), at least one of a price range category (371), gift recommendation (372), sorting method (376), recommended products based on a wish list (373), recommended products based on product purchase history (374), product (375), product search (378), or product purchase view exit button (379) may be displayed.

[0069] The price range category (371) is a category related to the price range of a product, and when input for a specific price range category is received, products included in that price range may be displayed on the screen. The gift recommendation (372) category may be at least one product recommended to a specific account. For example, a gift recommendation for account A corresponding to the terminal may be displayed on the screen. The gift recommendation (372) may include multiple lists of recommended items corresponding to various types. For example, lists of recommended items may be provided based on characteristics such as the age of the user to whom the gift will be provided (e.g., 20s, 30s), gender, and relationship with the person giving the gift (e.g., friend, girlfriend, boyfriend, parent). For example, lists of recommended items may be provided based on the purpose of the gift, such as wedding gifts, housewarming gifts, birthday gifts, light gifts, and holiday gifts.

[0070] According to one embodiment, the gift recommendation (372) may include recommended products based on a status message displayed in the account's profile view. A processor (710) of the server may determine recommended products based on the status message. A processor (710) of the server may extract keywords from the status message. For example, if the status message is "I finally got a job," the keyword may be "employment." A processor (710) of the server may determine recommended products based on the keywords extracted from the status message. For example, if the status message is "I finally got a job," a processor (710) of the server may determine recommended products related to "employment." As another example, if the status message is "I am on vacation for 5 days," a processor (701) of the server may determine recommended products related to "vacation." A processor (710) of the server may analyze the meaning of the status message through natural language processing and determine recommended products based on the analyzed meaning. To analyze the meaning of the status message, a deep learning model may be used.

[0071] According to one embodiment, the gift recommendation (372) may include at least one of a recommended product (373) based on a wish list or a recommended product (374) based on a product purchase record. The wish list may be a wish list of another account that is friends with Account A. For example, the recommended product (373) based on the wish list may be a product included in the wish list of another account B that is friends with Account A. The processor (710) of the server may determine the recommended product based on the wish list of the other account. The recommended product (374) based on the product purchase record may be a recommended product based on the product purchase record corresponding to a specific account. The product purchase record may refer to all records related to product purchases corresponding to the account. The server processor (710) can determine recommended products based on product purchase records corresponding to an account. For example, if there is a product for which the number of times account A has purchased it is above a certain standard, the server processor (710) can determine that product as a recommended product (374) based on product purchase records.

[0072] The product search interfacing object (378) may be an object for searching for a product to be gifted. The user can search for a product to be gifted through the product search interfacing object (378). The product search results may be displayed on the screen. The sorting method (376) may be an object for selecting a method to sort multiple products displayed on the screen. For example, the sorting method (376) may be by recommendation, popularity, comments, etc. The product purchase view exit button (379) may be a button for exiting the product purchase view displayed on the screen.

[0073] According to one embodiment, the product purchase view may be displayed over the entire screen area of ​​the terminal. For example, the product purchase view (370) may be displayed over the entire screen (301) of FIG. 3b. In this case, the profile view may not be displayed on the screen. According to another embodiment, the product purchase view may be displayed over at least a portion of the screen of the terminal with the profile view as the background. For example, the product purchase view (370) may be displayed over at least a portion of the screen (301) of FIG. 3b. In this case, the profile view (360) may be displayed as the background on the screen, and the product purchase view (370) may be displayed over at least a portion of the screen (301).

[0074] When a product is selected through a product purchase view (370) according to one embodiment, the processor (710) of the terminal may display a payment view (380) (e.g., the payment view (380) of FIG. 3C) on the screen. The payment view (380) may be a view for generating payment information based on user input. The payment view (380) may display at least one of a product image (381), product-related information (382), product reviews (383), a payment method (390), a payment amount (391), or a payment button (392). The product-related information is information related to the product and may include, for example, a product manufacturer, a product distributor, an expiration date, a use-by date, a product name, a brand name, a product price, a method of using the product, a product description, an order number, a place of exchange, a method of exchanging the product, a barcode, a date of purchase, customer service information, a period for canceling the purchase, a method of use, a method of refusing a gift, etc. The payment method (390) is a means for a user to pay for a product and may include, for example, cash, card, points, virtual currency, etc. The payment amount (391) may be an amount determined based on at least one of the product price or product discount information. The payment button (392) may be a button for a user to check the product payment details and proceed with the payment. When a selection input for the payment button (392) is received, the processor (710) of the terminal may generate payment information.

[0075] When a payment is completed according to one embodiment, a payment completion message (393) may be displayed on the terminal screen (303) (e.g., the screen (303) of FIG. 3D). Referring to FIG. 3D, the payment completion message (393) may be displayed with the profile view as the background. The payment completion message (393) may include at least one of a product image (394), text (395) related to the payment completion, and product-related information. The aforementioned payment completion message (393) is merely an example and the present disclosure is not limited thereto.

[0076] In step (130) according to one embodiment, the processor (710) of the terminal can transmit first product data corresponding to a product determined based on user input received through a product purchase view to a server. For example, referring to FIG. 3b, the processor (710) of the terminal can transmit first product data corresponding to a product (373) determined based on user input to a server. The processor (710) of the terminal can generate payment information corresponding to a product determined based on user input received through a product purchase view. For example, the processor (710) of the terminal can generate payment information corresponding to a product (373) determined based on user input. Payment information is information necessary for product payment and may include, for example, payment means, payment-related authentication information, etc. The processor (710) of the terminal can transmit first product data to a server that includes at least one of product-related information, gift message information, or payment information. Gift message information may include information related to a message that the first user can write while gifting a product to the second user. The gift message information may include at least one of text entered by the first user, a gift card, or an emoticon. For example, the first user may send a congratulatory message to the second user along with a gift.

[0077] A first user terminal according to one embodiment may transmit first product data to a server. A second user terminal may receive second product data corresponding to the first product data from the server. The second product data may include at least one of information related to a determined product, account information of the terminal that transmitted the first product data, or gift message information. The gift message information received by the second user terminal may include a message generated by the first user terminal. The account information may include information related to an account corresponding to the first user terminal. For example, if the first user's account has gifted a product to the second user's account, the account information may be the first user's account information.

[0078] According to one embodiment, the processor (710) of the first user terminal or the second user terminal may display second product data in a chat room with a service provider account. The service provider may be an instant messaging application service provider. The service provider account may be a channel regarding a gift-giving service. Accordingly, the processor (710) of the first user terminal or the second user terminal may display second product data in the form of a message through a chat room of a channel regarding a gift-giving service. For example, referring to the screen (400) of FIG. 4, a chat room with a service provider account (410) may be displayed on the screen (400). The screen (400) may be displayed on the screen of the first user terminal or the screen of the second user terminal, and the present disclosure is not limited thereto. The message may include a status message object (420) containing at least one of a first item or a second item, product-related information (421), a method for verifying received second product data (422), a button to view a product holding database (430), or a message information verification button (440). The method for verifying received second product data (422) may indicate a method for verifying second product data received by the second user terminal. For example, the processor (710) of the second user terminal may indicate a method for verifying products received by the second user of the second user terminal. The method for verifying received second product data (422) may be a method for viewing a product holding database. The product holding database may include a list of products received by a specific account. For example, the product holding database may include a list of product data received by the second user's account from another account. The product holding database viewing button (430) may be a button for viewing a list of products received by a specific account.When the processor (710) of the second user terminal receives a selection input for the product holding database viewing button (430), it may receive the product holding database from the server and display a list of gifted products on the screen. The product holding database may be a product holding database corresponding to the terminal's account. Therefore, the user of the terminal can view the list of products received from other users through the terminal's screen. According to one embodiment, the processor (710) of the second user terminal may receive a record related to at least one second product data stored in the product holding database corresponding to the second user terminal's account. Based on the received record, the processor (710) of the second user terminal may display a record of product data received from another account through the first item on the screen. The message information check button (440) may be a button for checking a message. Text included in the gift message information may not be displayed in the message received from the service provider account (410). Therefore, the user can select the message information check button (440) to check the message received along with the product.

[0079] A processor (710) of a server according to one embodiment may determine whether a product can be purchased based on certain conditions. For example, since minors cannot purchase alcoholic beverages, the processor (710) of the server may restrict minor accounts from purchasing alcoholic beverages. Accordingly, when the processor (710) of the server according to one embodiment receives input related to a first item, it may determine whether the account corresponding to the terminal can purchase the product based on product purchase constraints. For example, when a product is selected through a product purchase view, the processor (710) of the server may determine whether the product is available for purchase based on product purchase constraints. Product purchase constraints may be conditions that restrict product purchases based on information of a specific account. Product purchase constraints may include at least one of an age constraint, a country constraint, or an account activation status condition for the account corresponding to the terminal. The processor (710) of the server may set age constraints for some products to allow the purchase of some products only for accounts that are of a certain age or older. The server processor (710) may set country restrictions on some products to limit the products that can be purchased in the country where the account is located. For example, there may be products that can only be purchased if the account is located in Korea. In this case, if the account is located in a country other than Korea, the product cannot be purchased. The server processor (710) may restrict product purchases for deactivated accounts. Therefore, the condition regarding account activation may be a condition that allows product purchases only for activated accounts.

[0081] FIG. 2 is a flowchart illustrating a method of operation of a server for transmitting product data to a second user terminal corresponding to an account through an account profile view according to one embodiment.

[0082] In step (210) according to one embodiment, the server may receive first product data corresponding to a product determined through a first item applied to the account's profile view from the first user terminal. The first item may be a profile item for transmitting product data to the account of the second user terminal. The user of the first user terminal may select the first item displayed on the terminal screen. The first item may be the first item displayed on the account's profile view of the second user terminal. The profile view of the account of the second user terminal may be displayed on the screen of the first user terminal. The first item may be displayed on the profile view of the account of the second user terminal. When the user of the first user terminal selects the first item, a product purchase view may be displayed on the terminal screen. The user of the first user terminal may determine a product to purchase through the product purchase view. The first user terminal may generate first product data corresponding to the product determined through the product purchase view. The first user terminal may transmit the first product data to the server. The first product data may include at least one of information related to the determined product, gift message information, or payment information. The server may perform payment for the determined product amount based on the payment information. If payment is not completed, the server may not generate second product data and may transmit payment failure information to the first user terminal.

[0083] In step (220) according to one embodiment, if payment is completed, the server may generate second product data based on the first product data.

[0084] In step (230) according to one embodiment, the server may transmit the generated second product data to the second user terminal. The second product data may include at least one of information related to the determined product, account information of the first user terminal, or gift message information. The second user terminal may receive the second product data and display the second product data in the form of a message in a chat room with the service provider account displayed on the screen of the second user terminal.

[0086] FIGS. 3a to 3d are drawings for explaining the process of transmitting product data according to one embodiment.

[0087] Since a detailed description of FIGS. 3a to 3d has been previously provided in FIG. 1, a detailed description is omitted in this drawing.

[0089] FIG. 4 is a diagram illustrating the screen of a terminal that has received product data according to one embodiment.

[0090] A detailed explanation of Fig. 4 has been provided in Fig. 1, so a detailed explanation is omitted in this drawing.

[0092] FIGS. 5a to 5c are drawings for explaining a method for transmitting an emoticon to a second user terminal corresponding to an account through a profile view of an account according to one embodiment.

[0093] For example, an account profile view may be displayed on the screen of the first user terminal. The account may refer to the second user's account.

[0094] A processor (710) of a first user terminal according to one embodiment may display a visual effect corresponding to the input on a screen when it receives an input related to a second item. The visual effect may include an effect in which an emoticon is displayed at predetermined coordinates on the screen. In the profile view screen (500) of FIG. 5a, at least one of a status message object (310), a first item (311), a second item (312), an emoticon input object (510) corresponding to the second item input, or a plurality of emoticons (511, 512, 513, 514, 515) is displayed. When the processor (710) of the first user terminal receives a selection input for the second item (312), it may display the emoticon input object (510) on the screen. Additionally, the processor (710) of the terminal may receive a selection input for one of the plurality of emoticons (511, 512, 513, 514, 515). When the processor (710) of the first user terminal receives an emoticon selection input, the processor (710) of the first user terminal may display the selected emoticon at predetermined coordinates on the screen. For example, if an emoticon (513) is selected in FIG. 5a, an emoticon (520) may be displayed at predetermined coordinates on the profile view screen (501) of FIG. 5b. The processor (710) of the first user terminal may dynamically display the selected emoticon on the screen. For example, the processor (710) of the first user terminal may implement a visual effect of moving the selected emoticon from top to bottom. As another example, the processor (710) of the first user terminal may implement a visual effect of making the selected emoticon gradually larger.

[0095] When the processor (710) of the first user terminal according to one embodiment receives input related to the second item, it may display an emoticon input means on the screen in response to the input. The emoticon input means (540) may be displayed on the profile view screen (502) of FIG. 5c. When the processor (710) of the first user terminal receives a selection input for the second item (312), it may display the emoticon input means (540) on the screen. The emoticon input means (540) may be a means for inputting various emoticons. The emoticon input means (540) may include at least one of an emoticon type (541), an emoticon purchase (542), a keyword-based emoticon category (543), or an emoticon keyboard (544). The emoticon type (541) may be a higher-level concept that includes emoticons. For example, the emoticon type (541) may be a set of emoticons defined by emoticon character. When a user selects one of the emoticon types, various emoticons corresponding to that type may be displayed on the emoticon keyboard (544). When selecting to purchase emoticons (542), an emoticon purchase view may be displayed on the screen. The keyword-based emoticon category (543) may include multiple keywords. The processor (710) of the first user terminal may display emoticons corresponding to each keyword on the emoticon keyboard (544). The processor (710) of the first user terminal may display an emoticon determined based on user input among the emoticons displayed on the emoticon input means (540) at predetermined coordinates on the screen. Referring to FIG. 5c, when the processor (710) of the first user terminal receives a selection input for an emoticon (545), the selected emoticon (530) may be displayed at predetermined coordinates on the screen.

[0096] The processor (710) of the first user terminal can request the server to send the selected emoticon to the second user terminal corresponding to the account.

[0098] FIGS. 6a and 6b are drawings for illustrating a screen displaying an emoticon reception record or a product data reception record according to one embodiment.

[0099] A processor (710) of a terminal according to one embodiment may display an emoticon reception record received through a second item. For example, a first user may send an emoticon to a second user through a second item. The second user may know that the first user has sent an emoticon through the emoticon reception record. Referring to FIG. 6a, an emoticon reception record (610) may be displayed on a screen (600). The emoticon reception record (610) may include at least one of a product record (630) received by an account from other accounts through a first item or an emoticon reception record (620) received through a second item. For example, a second account may register a status message object (310) in its profile view. In this case, other first accounts (e.g., Account A, Account B, Account C, etc.) may send an emoticon to the second account through a second item (312) included in the status message object (310) displayed in the second account's profile view. The user of the second account can view the emoticon reception records received from other first accounts through the emoticon reception records (620). The emoticon reception records (620) may display at least one of the profile image (621) of the first account that sent the emoticon to the second account, the account name (622), the number of times the emoticon was received (623) or the received emoticon (624), and a view of details (625). The user of the first account may send emoticons to the user of the second account multiple times, and the number of times the emoticon was received may be displayed on the screen of the second account user's terminal. For example, if the user of the first account sends emoticons to the second account three times, three times may be displayed on the screen of the second account user's terminal. The received emoticon (624) may display the emoticon received by the second account. Therefore, the user of the second account can know which emoticon they received from the first account and received empathy.View details (625) may be an option to view emoticons received from a specific account. For example, a user of a second account may receive multiple emoticons from a user of a first account, and the multiple emoticons received may all be the same or different. Through View details (625), the user of the second account can view various emoticons received from the user of the first account in the order of receipt. Referring to FIG. 6b, the screen (601) may be a screen displayed when View details (625) is selected by the user. For example, if the account that sent the emoticons to the user of the second account is Account A, the View details display object (650) may display at least one of the number of emoticons sent by Account A (651), Account A's profile image (652), account name (653), the time the emoticons were received (654), or the received emoticons (655).

[0100] When a product record (630) received through a first item according to one embodiment is selected, the processor (710) of the terminal may display a record related to at least one second product data stored in a product holding database on the screen. The product holding database may be a product holding database corresponding to the account of the terminal. The product record (630) received through the first item may display a product record received by the user of the second account from other users of the first account. The processor (710) of the terminal may display a product record received by the user of the second account from other users of the first account on the screen based on a record related to the second product data received from the server.

[0102] FIG. 7 is a block diagram of an electronic device according to one embodiment.

[0103] Referring to FIG. 7, the electronic device (700) includes a processor (710), memory (740), a communication interface (730), and a display (720). The electronic device (700) may correspond to a server and, depending on the embodiment, may include terminals (e.g., smartphone, personal computer, tablet PC, etc.).

[0104] An electronic device (700) according to one embodiment may include a device related to an instant messaging service. A processor (710) described above through FIGS. 1 to 6

[0106] One method can perform the operations of the steps. For example, the processor (710) can store the data generated as a result of performing the above-described operations in memory (740) or in an external database accessible from the electronic device.

[0107] The memory (740) can store the data described above and can store data generated according to the execution of the operation of the processor (710). The memory (740) may be volatile memory or non-volatile memory.

[0108] An electronic device according to one side may be connected to an external device (e.g., a terminal or network) through a communication interface (730) and may exchange data. For example, the electronic device may exchange data to interact with another account through the communication interface (730).

[0109] A processor (710) according to one embodiment can display a user interface through a display (720). The screens of the aforementioned drawings can be displayed through the display (720).

[0110] According to one embodiment, the processor can execute a program stored in memory and control a device. The code of the program executed by the processor can be stored in memory.

[0112] The embodiments described above may be implemented as hardware components, software components, and / or combinations of hardware and software components. For example, the devices, methods, and components described in the embodiments may be implemented using a general-purpose computer or a special-purpose computer, such as, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a programmable logic unit (PLU), a microprocessor, or any other device capable of executing and responding to instructions. The processing unit may execute an operating system (OS) and software applications executed on said operating system. Additionally, the processing unit may access, store, manipulate, process, and generate data in response to the execution of the software. For ease of understanding, the processing unit may be described as being used as a single unit, but those skilled in the art will understand that the processing unit may include multiple processing elements and / or multiple types of processing elements. For example, the processing unit may include multiple processors or one processor and one controller. In addition, other processing configurations, such as parallel processors, are also possible.

[0113] Software may include computer programs, code, instructions, or a combination of one or more of these, and may configure a processing unit to operate as desired or command the processing unit independently or collectively. Software and / or data may be permanently or temporarily embodied in any type of machine, component, physical device, virtual equipment, computer storage medium or device, or transmitted signal wave in order to be interpreted by the processing unit or to provide instructions or data to the processing unit. Software may be distributed over networked computer systems and may be stored or executed in a distributed manner. Software and data may be stored on computer-readable recording media.

[0114] The method according to the embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer-readable medium. The computer-readable medium may store program instructions, data files, data structures, etc., either individually or in combination, and the program instructions recorded on the medium may be those specifically designed and configured for the embodiment or those known and available to those skilled in the art 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 floptical disks; and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, and flash memory. Examples of program instructions include machine code, such as that generated by a compiler, as well as high-level language code that can be executed by a computer using an interpreter, etc.

[0115] The hardware device described above may be configured to operate as one or more software modules to perform the operation of the embodiment, and vice versa.

[0116] Although the embodiments have been described above with reference to the limited drawings, those skilled in the art can apply various technical modifications and variations based thereon. For example, suitable results may be achieved even if the described techniques are performed in a different order than described, and / or if the components of the described system, structure, device, circuit, etc. are combined or assembled in a form different from described, or replaced or substituted by other components or equivalents.

[0117] Therefore, other implementations, other embodiments, and equivalents to the claims also fall within the scope of the claims set forth below.

Claims

Claim 1 A method of operation of a terminal of a first user for transmitting product data through a profile view of a second user's account, comprising: a step of displaying a profile item in the profile view of the second user's account; a step of displaying a product purchase view when input related to a first item is received through the profile item; and a step of transmitting first product data corresponding to a product determined based on user input received through the product purchase view to a server, wherein the profile item includes a status message object registered corresponding to the second user's account and the first item for transmitting the product data to the second user's account, wherein a fourth item for displaying a status message is displayed in the status message object, and a recommended product based on the status message is displayed through the product purchase view, and the recommended product is determined based on either a keyword extracted from the status message or a semantic analysis result of the status message. Claim 2 A method of operation of a terminal, wherein the profile item further comprises at least one of a second item for interacting with the account of the second user and a third item for displaying D-day date information. Claim 3 A method of operation of a terminal, wherein, in claim 1, the product purchase view is displayed over the entire screen area of ​​the terminal or is displayed over at least a portion of the screen of the terminal with the profile view as a background. Claim 4 A method of operation of a terminal, wherein the product purchase view includes recommended products, and the recommended products further include products determined based on at least one of a wish list of another account distinct from the second user's account and a product purchase record of the second user's account. Claim 5 A method of operation of a terminal, wherein the step of transmitting the first product data to the server comprises: a step of generating payment information corresponding to a product determined based on user input received through the product purchase view; and a step of transmitting the first product data to the server, the first product data including at least one of information related to the product, gift message information, and payment information, wherein the gift message information includes information related to a message written by the first user while gifting a product to the second user. Claim 6 A method of operation of a terminal according to claim 1, further comprising: receiving from the server a second product data corresponding to the first product data—including at least one of information related to the determined product, account information of the terminal that transmitted the first product data, and gift message information; and displaying the second product data in a chat room with a service provider account, wherein the gift message information includes information related to a message written by the first user while gifting a product to the second user. Claim 7 A method of operation of a terminal according to claim 1, further comprising the step of determining whether the first user's account is eligible to purchase a product based on product purchase constraints when receiving input related to the first item. Claim 8 A method of operation of a terminal, wherein, in claim 7, the product purchase restriction condition comprises at least one of an age restriction condition of the first user’s account, a country restriction condition, and a condition regarding whether the first user’s account is active. Claim 9 A method of operation of a terminal, further comprising the step of receiving a record stored in a product holding database—said that the record is related to second product data—in the first paragraph. Claim 10 A method of operation of a terminal, wherein, in claim 1, the profile item further includes a second item for interacting with the account of the second user, and when input related to the second item is received from the first user, the method further includes the step of displaying a visual effect corresponding to the input on a screen where the profile view is output. Claim 11 In claim 10, the above visual effect includes an effect in which an emoticon is displayed at predetermined coordinates on the screen, a method of operation of a terminal. Claim 12 A method of operation of a terminal according to claim 1, wherein the profile item further includes a second item for interacting with the second user's account, and when an input related to the second item is received, in response to the input, a step of displaying an emoticon input means on a screen; and a step of displaying an emoticon determined based on user input among the emoticons displayed on the emoticon input means at predetermined coordinates on the screen. Claim 13 A method of operation of a terminal, wherein, in claim 1, the profile item further includes a second item for interacting with the account of the second user, and further includes the step of displaying a record of receiving emoticons received through the second item. Claim 14 A method of operation of a server for transmitting product data to a terminal of a second user through a profile view of a second user's account, comprising: receiving first product data corresponding to a product determined through a first item applied to the profile view of the second user's account from the terminal of the first user; generating second product data based on the first product data; and transmitting the second product data to the terminal of the second user through a first item included in a status message object; wherein a fourth item displaying a status message is displayed in the status message object, the product determined through the first item corresponds to a product determined among recommended products based on the status message, and the recommended product is determined based on either a keyword extracted from the status message or a semantic analysis result of the status message. Claim 15 In claim 14, the step of receiving the first product data from the first user's terminal comprises: a step of determining the product among recommended products based on the status message based on user input received through a product purchase view displayed on the screen of the first user's terminal in response to an input related to the first item; and a step of receiving the first product data corresponding to the determined product from the first user's terminal; a method of operation of a server. Claim 16 A method of operation of a server, wherein, in paragraph 14, the first product data comprises at least one of information related to the determined product, gift message information, and payment information corresponding to the determined product, and the gift message information comprises information related to a message written by the first user while gifting a product to the second user. Claim 17 A method of operation of a server, wherein, in paragraph 14, the second product data comprises at least one of information related to the determined product, account information of the first user's terminal, and gift message information, and the gift message information comprises information related to a message written by the first user while gifting a product to the second user. Claim 18 A computer program stored on a computer-readable recording medium in combination with hardware to execute the method of any one of claims 1 through 17. Claim 19 A terminal comprises at least one processor and memory; wherein the processor displays a profile item in an account profile view and, when it receives input related to a first item through the profile item, displays a product purchase view and transmits first product data corresponding to a product determined based on user input received through the product purchase view to a server, wherein the profile item includes a status message object registered in correspondence with the account and the first item for transmitting the product data to the account, wherein the status message object displays a fourth item for displaying a status message, and a recommended product based on the status message is displayed through the product purchase view, and the recommended product is determined based on either a keyword extracted from the status message or the result of semantic analysis of the status message.

Images