Messaging service method and apparatus
The server-based reserved message function in messaging services allows users to schedule message delivery and prevents abuse by validating chat rooms, improving user experience and service reliability.
Patent Information
- Application Number
- JP2023081059
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2022-05-16
- Filing Date
- 2023-05-16
- Publication Date
- 2024-11-13
- Estimated Expiration
- 2043-05-16
AI Technical Summary
Existing messaging services lack a function to send messages created in advance to a specified target at a specified time and do not adequately prevent abuse.
A server provides a reserved message function linked to a messaging service, enabling users to schedule messages for delivery at a later time, with features to validate chat rooms, prevent abuse, and manage message delivery status.
Enables scheduled message delivery and prevents abuse by ensuring messages are sent to valid chat rooms, enhancing user convenience and service reliability.
Smart Images

Figure 0007583107000001 
Figure 0007583107000002 
Figure 0007583107000003
Abstract
Description
[Technical field]
[0001] The following embodiments relate to a messaging service method and apparatus, and more particularly, to a server that provides a scheduled message function linked with an app for a messaging service. [Background technology]
[0002] 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 for creating and strengthening 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.
[0003] As communication through such mobile devices increases, online platform services are supporting not only 1:1 text-based communication with other users, but also features to facilitate communication by sharing various types of data. Summary of the Invention [Problem to be solved by the invention]
[0004] The object of the present invention is to provide a messaging service in the following embodiments that includes not only a function for sending messages created by a user in real time, but also a scheduled message function for sending pre-created messages at the user's request to a specified target at a specified time.
[0005] An object of the present invention is to provide a scheduled message function for preventing abusing in messaging services in the following embodiments.
[0006] However, the technical issues are not limited to those mentioned above, and further technical issues may exist. [Means for solving the problem]
[0007] According to one embodiment, an operating method of a server providing a reservation message function linked to an app for a messaging service includes the steps of: identifying a reservation message to be sent based on a stored record related to the reservation message corresponding to a first user account subscribed to the messaging service; determining whether a chat room corresponding to a destination of the identified reservation message is valid; and sending the identified reservation message through the chat room based on the determination of the validity.
[0008] A receipt confirmation status for a message received through the chat room prior to sending of the scheduled message may be changed in response to a connection of the chat room to a terminal logged in with the first user account.
[0009] The method of operating the server may further include a step of controlling a chat interface provided to a terminal logged in with a participant account of the chat room to display a changed acknowledgement status for a message sent via the chat room.
[0010] The reserved message may be displayed in a chat interface corresponding to the chat room together with a mark to distinguish it from general messages.
[0011] The operation method of the server may further include a step of identifying a scheduled message to be pre-notified based on information regarding a pre-notification setting included in a record related to the scheduled message, and a step of sending a pre-notification message via a chat room of a specific type corresponding to the first user account to inform the user that the scheduled message to be pre-notified is scheduled to be sent.
[0012] The destination of the scheduled message may include at least one of a second user account that subscribes to the messaging service and a chat room created by the messaging service.
[0013] Identifying the scheduled delivery reservation message may include identifying the scheduled delivery reservation message based on scheduled delivery time information included in the record.
[0014] The step of determining whether the chat room is valid may include a step of determining that the chat room is valid if there is a history of messages being sent or received through the chat room and participant information of the chat room has not changed, and a step of determining that the chat room is invalid if there is no history of messages being sent through the chat room or participant information of the chat room has changed.
[0015] The step of sending the identified reservation message may include a step of sending the identified reservation message via the chat room if the chat room is determined to be valid, and a step of notifying a terminal logged in with the first user account that the reservation message will not be sent if the chat room is determined to be invalid.
[0016] The record relating to the subscription message may include at least one of the contents of the subscription message, a scheduled time for sending the subscription message, a recipient of the subscription message, and a pre-notification setting for the subscription message.
[0017] The step of identifying the scheduled subscription message for delivery may include the steps of modifying a record related to the subscription message based on a request to edit the record, and identifying the scheduled subscription message for delivery based on the modified record.
[0018] Modifying the record may include restricting modification of the record if the time remaining until a scheduled delivery time included in the record is less than a threshold time.
[0019] According to one embodiment, a server providing a scheduled message function linked to an app for a messaging service includes at least one processor that identifies a scheduled message to be sent based on a record related to the scheduled message stored corresponding to a first user account subscribed to the messaging service, determines whether a chat room corresponding to the first user account and a destination of the identified scheduled message is valid, and sends the identified scheduled message via the chat room based on the determination of the validity.
[0020] A receipt confirmation status for a message received through the chat room prior to sending of the scheduled message may be changed in response to a connection of the chat room to a terminal logged in with the first user account.
[0021] The processor can control a chat interface provided to a terminal logged in with a participant account of the chat room to display a modified acknowledgement status for messages sent via the chat room.
[0022] The reserved message may be displayed in a chat interface corresponding to the chat room together with a mark to distinguish it from general messages.
[0023] The processor can identify a scheduled message that is subject to a pre-notification based on information about a pre-notification setting included in a record for the scheduled message, and can send a pre-notification message via a chat room of a particular type corresponding to the first user account to inform the user that the scheduled message that is subject to the pre-notification is scheduled to be sent.
[0024] In identifying the subscription message to be dispatched, the processor may modify a record related to the subscription message based on a request to edit the record, and identify the subscription message to be dispatched based on the modified record.
[0025] The processor may limit the modification of the record if the time remaining until a scheduled delivery time included in the record is less than a threshold time. Effect of the Invention
[0026] According to the following embodiment, a messaging service can be provided that includes not only a function for sending messages created by a user in real time, but also a scheduled message function for sending pre-created messages at a user's request to a specified target at a specified time.
[0027] According to the following embodiment, a scheduled message function for preventing abusing in a messaging service can be provided. [Brief description of the drawings]
[0028] [Figure 1]10 is a flowchart illustrating an operation of a server providing a scheduled message function linked with an app for a messaging service according to an embodiment. [Figure 2A] FIG. 13 illustrates an example of a chat interface screen in which a reservation message has been sent, according to one embodiment. [Figure 2B] 11 is a diagram illustrating an example of a screen of a terminal to which a delivery failure message for a reservation message is sent according to an embodiment; [Figure 3A] FIG. 13 is a diagram illustrating an example of an interface screen including a chat list provided to a terminal of a first user account via an app according to an embodiment. [Figure 3B] FIG. 13 is a diagram illustrating an example of a chat interface screen provided via an app on a terminal of a second user account according to an embodiment. [Figure 4] 13 is a diagram illustrating an example of a chat interface screen in which a pre-notification message for a scheduled message is sent according to an embodiment. FIG. [Figure 5A] FIG. 13 illustrates an interface screen for generating a subscription message according to an embodiment. [Figure 5B] FIG. 13 illustrates an interface screen for generating a subscription message according to an embodiment. [Figure 5C] FIG. 13 illustrates an interface screen for generating a subscription message according to an embodiment. [Figure 6A] 11 illustrates an example interface screen for viewing and editing a reservation message according to an embodiment; FIG. [Figure 6B] 11 illustrates an example interface screen for viewing and editing a reservation message according to an embodiment; FIG. [Figure 6C] 11 illustrates an example interface screen for viewing and editing a reservation message according to an embodiment; FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0029] The specific structural or functional description of the following embodiments is disclosed for the purpose of illustration only, and may be modified in various forms. Therefore, the embodiments are not limited to the specific disclosed forms, and the scope of the present specification includes modifications, equivalents, or alternatives within the technical spirit.
[0030] Although terms such as first or second may be used to describe multiple components, such terms should be construed 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.
[0031] When a component is referred to as being "coupled" or "connected" to another component, it should be understood that although it is directly coupled or connected to the other component, there may be other components in between.
[0032] The singular expression includes the plural expression unless the context clearly indicates otherwise. In this specification, the terms "comprise" or "have" and the like indicate the presence of a feature, number, step, operation, component, part, or combination thereof described in the specification, and should be understood as not precluding the possibility of the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.
[0033] Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. In the description with reference to the drawings, the same components are given the same reference numerals regardless of the reference numerals, and redundant description thereof will be omitted.
[0034] FIG. 1 is an operation flowchart of a server providing a scheduled message function linked with an app for a messaging service according to an embodiment.
[0035] Referring to FIG. 1, an operation method of a server providing a scheduled message function linked with an app for a messaging service according to one embodiment includes step S110 of identifying a scheduled message to be sent, step S120 of determining whether a chat room corresponding to a destination of the identified scheduled message is valid, and step S130 of sending the identified scheduled message via the chat room.
[0036] According to an embodiment, the server may provide a service related to a scheduled message function linked with an app for a messaging service. The messaging service is a service for sending messages to and receiving messages from subscribed users and sending notification messages to subscribed users, and may include, for example, an instant messaging service based on instant messages.
[0037] A messaging server according to an embodiment may generate a user account for a messaging service in response to a user's request to subscribe to a messaging service. The user account corresponds to a unit for identifying a user who has subscribed to a messaging service in the server. A terminal logged in to the user account can use a service provided by the server. Hereinafter, a terminal refers to a terminal logged in to a user account generated by subscribing to a messaging service.
[0038] The terminal refers to any device capable of installing and executing an app as one of electronic devices such as a computer, a portable computer, a wireless phone, a mobile phone, a smart phone, a PDA (Personal Digital Assistant), a web tablet, a wearable device, etc. Here, the terminal is provided with services and / or content provided by a server under the control of an app. For example, the terminal may perform general service operations such as configuring a service screen, inputting data, transmitting and receiving data, and storing data under the control of an app. For example, the terminal may process a user interface or user interaction through a processor, and may output a processing result through an output device of the terminal or transmit the processing result to a server.
[0039] According to one embodiment, the apps installed on the terminal include an app for a messaging service or a messenger app. The messaging service is provided to the terminal under the control of the messenger app, and a secretary function is provided by the server. Hereinafter, the app for the messaging service is simply referred to as "app."
[0040] According to an embodiment, a chat interface may be provided to a terminal via an app for a messaging service. The chat interface is an interface for a message sending and receiving function provided by a server, and may include, for example, an interface providing a function of sending a message through a chat room in which at least one user account participates and displaying a received message. The chat interface corresponds to a chat room, which is a virtual space in which at least one user account participates and in which chats between participants take place.
[0041] According to one embodiment, the scheduled message function means a function of sending a message prepared in advance at a user's request to a predetermined target at a predetermined time as a kind of secretary function provided to enhance the user's convenience in addition to a function related to sending and receiving messages in an app for a messaging service. As an example, the scheduled message function may include not only a function of sending a scheduled message, but also a scheduled message management function for registering, viewing, and editing a scheduled message corresponding to a user account.
[0042] The reservation message function according to an embodiment may be provided by the messaging server, or may be provided by a separate server interlocked with the messaging server. As an example, a part of the reservation message function may be provided by the messaging server, and another part may be provided by a separate server interlocked with the messaging server. In other words, a server providing the reservation message function interlocked with an app for a messaging service may refer to the messaging server, or may refer to a separate server interlocked with the messaging server to provide the reservation message function via an app for a messaging service. Hereinafter, a server providing the reservation message function interlocked with an app for a messaging service will be simply referred to as a "server".
[0043] According to one embodiment, the server identifies a scheduled message to be sent based on a scheduled message record stored corresponding to a first user account that has subscribed to the messaging service (S110). The first user account corresponds to the sender of the scheduled message. The scheduled message record is a unit of data generated by execution of the scheduled message function, and may include, for example, at least one of the contents of the scheduled message, the scheduled time of sending the scheduled message, the recipient (or recipients) of the scheduled message, and whether or not a pre-notification setting is set for the scheduled message. Depending on the context, a scheduled message may refer to a record of a scheduled message.
[0044] As an example, a terminal logged in with a first user account may execute a scheduled message function provided via an app to request the server to generate a scheduled message. The request to generate the scheduled message may include information about the scheduled message, such as the content of the scheduled message, the scheduled time of sending the scheduled message, the recipient of the scheduled message, and / or whether or not a pre-notification setting is enabled for the scheduled message. The server may generate a record related to the scheduled message based on the request to generate the scheduled message including information about the new scheduled message. The generated record may be stored in association with the first user account.
[0045] According to one embodiment, the content of the scheduled message may include the content sent in the scheduled message. For example, the content sent in the scheduled message may include various types of content such as text, emoticons, videos, and / or images.
[0046] According to one embodiment, the scheduled delivery time of the subscription message may include date and time values indicating the time when the subscription message will be delivered. The scheduled delivery time of the subscription message may be set to a time after the time of requesting generation of the subscription message. To this end, in an interface for setting the scheduled delivery time of the subscription message, times before the requested time may be inactivated and may or may not be displayed.
[0047] According to an embodiment, the destination of the reservation message may include at least one of a second user account subscribed to the messaging service and / or a chat room created by the messaging service. As an example, the second user account designated as the destination of the reservation message corresponds to a user account registered as a friend in correspondence with the first user account. Any user using the messaging service may register identification information related to another user account subscribed to the messaging service, such as a phone number or ID, as a friend user account via the app. The user may designate any one of the user accounts registered as friends via the app as the destination of the reservation message.
[0048] As an example, the chat room designated as the target for sending the reserved message corresponds to a chat room in which the first user account participates. The chat room is a virtual chat space provided by the messaging service, and at least one user account can participate in the chat room. The first user, who is an arbitrary user using the messaging service, can connect to the app and participate in the chat room with his / her own user account, the first user account, and the chat room in which the first user account participates can be stored in correspondence with the first user account. As an example, the identification information of the chat room in which the first user account participates may be mapped to the identification information of the first user account and stored in the messaging server or a database accessible by the server. As an example, the identification information of the chat room in which the first user account participates may be mapped to the identification information of the first user account and stored in the terminal. The user may set any one of the chat rooms in which the user is participating via the app as the target for sending the reserved message. By limiting the chat rooms set as targets for sending reserved messages to chat rooms in which the first user account is participating and not to any chat room, it is possible to prevent abuse using the reserved message function, such as setting a reserved message to be sent repeatedly to any chat room.
[0049] According to an embodiment, the pre-notification setting of the scheduled message may include a setting of whether or not the first user account that requested the delivery of the scheduled message receives a message for notifying the delivery of the scheduled message in advance. As an example, the pre-notification setting may further include time information for receiving the pre-notification. The time point at which the pre-notification is received may be determined based on the scheduled delivery time of the scheduled message. For example, the time point at which the pre-notification is received may be set to one day before, 15 minutes before, etc., based on the scheduled delivery time of the scheduled message. As an example, the pre-notification setting may further include a repeat setting of the pre-notification. For example, the pre-notification may be set to be repeated at regular intervals until the pre-notification is confirmed by the first user account.
[0050] Step S110 according to an embodiment includes identifying a scheduled delivery time-point-related reserved message based on information about a scheduled delivery time-point-related reserved message included in the record related to the scheduled delivery time-point-related reserved message, and identifying a record related to the scheduled delivery time-point-related reserved message among the records related to the scheduled delivery time-point-related reserved message stored in association with the first user account as a scheduled delivery time-point-related reserved message.
[0051] According to one embodiment, the server can identify subscribed messages for pre-notification based on information about pre-notification settings included in the record for the subscribed message, as described below.
[0052] Step S110 according to an embodiment includes modifying the record based on an edit request for the record related to the reserved message, and identifying the reserved message to be sent based on the modified record. As described below, the record related to the reserved message registered in correspondence with the first user account may be modified in response to an edit request from a user. For example, at least one of the contents of the reserved message included in the record related to the reserved message, the scheduled time of sending the reserved message, the delivery target of the reserved message, and whether or not a pre-notification setting for the reserved message is enabled may be modified in response to the edit request.
[0053] According to one embodiment, the step of modifying the record may include a step of restricting modification of the record when the time remaining until the scheduled delivery time included in the record is less than the threshold time. In other words, the time during which the record related to the registered reserved message can be edited may be restricted based on the scheduled delivery time of the reserved message. For example, the server may modify the record related to the reserved message based on a request to edit the record related to the reserved message up to the threshold time before the scheduled delivery time of the reserved message (e.g., 15 minutes before the scheduled delivery time). On the other hand, when the time remaining until the scheduled delivery time of the reserved message is less than the threshold time, the server may restrict modification of the record related to the reserved message. According to one embodiment, the server may restrict modification of the record related to the delivered reserved message and / or the record related to the failed delivery reserved message.
[0054] According to one embodiment, the server determines whether a chat room corresponding to the identified delivery target of the reserved message is valid (S120). As an example, if the delivery target of the reserved message is set as the second user account, the chat room corresponding to the delivery target of the reserved message means a chat room including the first user account and the second user account. As an example, if the delivery target of the reserved message is set as the first chat room, the chat room corresponding to the delivery target of the reserved message means the first chat room set as the delivery target of the reserved message.
[0055] Step S120 according to an embodiment may include a step of determining that a chat room corresponding to the scheduled message delivery target is valid if there is a history of a message being sent or received through the chat room corresponding to the scheduled message delivery target, and a step of determining that the chat room is not valid if there is no history of a message being sent through the chat room corresponding to the scheduled message delivery target. In other words, if there is a chat room with a history of a message being sent or received between a first user account and a second user account designated as the scheduled message delivery target, the chat room corresponding to the scheduled message delivery target may be determined to be valid. Alternatively, if there is a history of a message being sent or received through the chat room designated as the scheduled message delivery target, the chat room corresponding to the scheduled message delivery target is determined to be valid.
[0056] According to an embodiment, the delivery target of the scheduled message may be set as a chat room in a valid state. As an example, after a scheduled message with the delivery target set to the first chat room is generated, the first chat room may be changed to an inactive state. For example, if the first chat room is deleted before the scheduled message is delivered, if the first user account leaves the first chat room, if all other user accounts participating in the first chat room except the first user account leave the first chat room, or if the user accounts withdraw from the messaging service, the first chat room may be determined to be inactive. For example, if at least one user account participating in the first chat room leaves the first chat room or withdraws from the messaging service and the participant information of the first chat room is changed, the first chat room may also be determined to be inactive.
[0057] The server according to an embodiment sends the identified reserved message through a chat room corresponding to the delivery target of the reserved message based on whether the chat room is valid (S130). In other words, the reserved message may be sent through a chat room in which the first user account and the second user account designated as the delivery target of the reserved message participate, or through a chat room designated as the delivery target of the reserved message.
[0058] Step S130 according to an embodiment includes a step of sending the identified reserved message through the chat room when it is determined that the chat room corresponding to the delivery target of the reserved message is valid. As an example, when the delivery target of the reserved message is a second user account, a terminal logged in with the second user account may receive the reserved message through a chat room in which the first user account and the second user account participate. As an example, when the delivery target of the reserved message is a first chat room, a terminal logged in with a user account participating in the first chat room may receive the reserved message through the first chat room.
[0059] According to an embodiment, the reserved message may be displayed in a chat interface corresponding to a chat room together with an indication for distinguishing the reserved message from a general message. As an example, the indication for distinguishing the reserved message from a general message may include an indication indicating that the reserved message is a reserved message. For example, referring to FIG. 2A, a chat interface screen 201 corresponding to a chat room to which a reserved message 216 for delivery to "Min Young Hee" is sent is shown. Unlike a general message, the reserved message 216 is added with an indication 217 indicating that the reserved message is a reserved message. The indication 217 added to the reserved message 216 shown in FIG. 2A is merely an example of distinguishing the reserved message 216 from a general message in the chat interface, and the reserved message may be displayed in various ways to distinguish it from a general message. For example, the reserved message 216 may be displayed to be distinguished from a general message by displaying a color and / or a shape of a speech bubble in which the message is displayed differently from a general message, or by adding an indication 217 adjacent to the speech bubble corresponding to the reserved message 216 indicating that the message is a reserved message.
[0060] According to an embodiment, if it is determined that the chat room corresponding to the delivery target of the reserved message is invalid, the reserved message is not delivered and an exception process may be performed. For example, if there is no chat room corresponding to the delivery target of the reserved message, or if there is no history of a message being sent or received through the chat room corresponding to the delivery target of the reserved message, the chat room is determined to be invalid. Also, as described above, if the first chat room set as the delivery target of the reserved message was valid at the time of generation of the reserved message, but the first chat room is deleted after the reservation message is generated and before the reservation message is sent, the first user account leaves the first chat room, all other user accounts participating in the first chat room except the first user account leave, or participant information of the first chat room is changed, the first chat room is determined to be invalid. In other words, step S130 according to an embodiment may include a step of notifying the terminal logged in with the first user account that the reserved message is not delivered when it is determined that the chat room corresponding to the delivery target of the reserved message is invalid. According to an embodiment, even if the reservation message is not sent through the chat room, the reserved message is not delivered and an exception process may be performed. For example, if a reservation message cannot be sent through a chat room due to a network error, the reservation message may not be sent and may be handled as an exception. According to an embodiment, the reservation message enters a waiting state for sending, in which the reservation message waits for a preset time (e.g., 5 minutes) based on a sending condition such as a network state to be changed into a sending possible state, and if the preset time is exceeded, the reservation message is handled as a sending failure. For example, the server may send a sending failure message to a terminal logged in with a first user account, notifying the terminal that the reservation message cannot be sent. As an example, referring to the interface screen 202 shown in FIG. 2B, the sending failure message may be sent to the terminal in the form of a push message 221. Also, as an example, the sending failure message may be sent in the form of an instant message through a specific type of chat room.
[0061] The type of chat room may be determined based on at least one of the number of user accounts included in the chat room and the manner of participating in the chat room. For example, the type of chat room may include a chat room with me that does not include other user accounts, a 1:1 chat room that includes one other user account, and a group chat room that includes two or more other user accounts. For example, the type of chat room may include a general chat room and an anonymous chat room. The general chat room is a chat room created by designating other user accounts whose account information is registered in a messenger application as participants of the chat room. A user of a messenger application may register identification information related to a user account, such as a phone number or ID, to the account of a user who is a friend. The general chat room refers to a chat room that includes other user accounts whose account information is registered in a messenger application or that are registered as friends as participants. The anonymous chat room refers to a chat room that can be joined through link information regardless of whether or not the user is a friend in the messenger application. As an example, the anonymous chat room service may include the Open Chat (registered trademark of Kakao Co., Ltd.) service provided by the applicant Kakao, specifically, a non-acquaintance-based open chat service provided by the applicant's KakaoTalk application, and the anonymous chat room means a chat room (or chat room) of the open chat service provided by the applicant Kakao. The open chat service provided by Kakao is merely an example of an anonymous chat room service, and is not limited thereto, and the anonymous chat room service may include a service that provides a chat room that can be joined through a temporary profile that is not a real-name based account.
[0062] As an example, the failed delivery message may be sent through a chat room with me. For example, the failed delivery message may be sent through a chat room with me with an official account related to the reservation message function as the sender. An official account is a type of account that subscribes to a messaging service and sends notification messages for a company or service or an advertising message for a company or service. For example, the official account related to the reservation message function may be implemented as a chatbot.
[0063] Also, as an example, the delivery failure message may be sent via a chat room with an official account related to the reservation message function. The chat room with the official account related to the reservation message function corresponds to a chat room in which a notification message related to the reservation message function including the delivery failure message is sent. The notification message related to the reservation message function may be sent with the official account related to the reservation message function as the sender.
[0064] According to an embodiment, the receipt confirmation status of a message received through a chat room corresponding to the delivery target of the reservation message before the delivery of the reservation message may be changed in response to the connection of the corresponding chat room of a terminal logged in with a first user account. A message sent through a chat room before the delivery of the reservation message means a message sent not by the first user account but by another user account participating in the chat room. The receipt confirmation status of a message may be set as a state in which a message sent to a user account through a chat room has not been received and confirmed by the user account before the corresponding user account connects to the chat room, and may be set as a state in which the message has been received and confirmed after the corresponding user account connects to the chat room. In other words, the receipt confirmation status of a message sent through a chat room may be maintained regardless of the delivery of the reservation message. For example, a message sent through a chat room before the delivery of the reservation message and not received and confirmed by the first user account may still be displayed as a message not received and confirmed by the first user account even after a reservation message with the first user account as the sender is sent. Among messages sent through the chat room, messages that have not been acknowledged by the first user account may be displayed as new messages on a terminal logged in with the first user account. When a terminal logged in with the first user account connects to the chat room, messages sent through the chat room may be changed to messages that have been acknowledged by the first user account.
[0065] According to an embodiment, the method of operating the server may further include controlling a chat interface provided to a terminal logged in with a participant account of the chat room to display a changed acknowledgement status for a message sent through the chat room. For example, the server may control a chat interface provided to a terminal of a first user account and a second user account through the terminal.
[0066] For example, FIG. 3A is a diagram illustrating an example of an interface screen 301 including a chat list provided via an app to a terminal of a first user account. Referring to FIG. 3A, a list 310 of chat rooms in which the first user account is participating is displayed via the interface. As an example, the list 310 of chat rooms may include items of chat rooms in which the first user account is participating. Each chat room item may include the name of the chat room or the name of a user account participating in the chat room, recent messages sent and received via the chat room, and time information when the recent messages were sent and received via the chat room. The list of chat rooms may include an indication indicating that a new message has been received via the chat room and / or information on the number of new messages sent via the chat room that have not been acknowledged. A new message means a message that has not been acknowledged by the first user account. For example, referring to the chat room item 311, it is displayed 312 that two new messages have been received via the chat room.
[0067] According to one embodiment, the chat room corresponding to the chat room item 311 corresponds to the chat room to which the reservation message was sent. Even after the reservation message with the first user account as the sender is sent through the chat room to which the reservation message was sent, the indication 312 indicating that two new messages have been received in the chat room item 311 is maintained until the first user account connects to the corresponding chat room. When the terminal of the first user account connects to the chat room, the receipt confirmation for the received messages may be changed. By changing the receipt confirmation, the indication 312 indicating that a new message included in the chat room item 311 has been received is removed.
[0068] For example, FIG. 3B is a diagram illustrating a screen 302 of a chat interface provided to a terminal of a second user account via an app. The chat interface illustrated in FIG. 3B corresponds to a chat room in which a first user account and a second user account participate. Referring to FIG. 3B, the chat interface corresponding to the chat room displays messages 321, 322, and 323 sent and received through the chat room. As an example, a reserved message 323 with the first user account as the sender may be displayed through the chat interface. Messages 321 and 322 sent by the second user account through the chat room before the reserved message 323 is sent may include indications 321-1 and 322-1 that are not acknowledged by the first user account. When the terminal of the first user account connects to the chat room, the acknowledgement status for the messages 321 and 322 is changed. Changing the acknowledgement status may result in the chat interface changing from a not acknowledged indication 321-1, 322-1 to an acknowledged indication, or removing the not acknowledged indication 321-1, 322-1.
[0069] An operating method of the server according to one embodiment may further include a step of identifying a scheduled message to be pre-notified based on information regarding a pre-notification setting included in a record related to the scheduled message, and a step of sending a pre-notification message via a chat room of a specific type corresponding to a first user account to inform the user that the scheduled message to be pre-notified is scheduled to be sent.
[0070] The server according to an embodiment may identify a scheduled message to be pre-notified based on information on a time point for receiving the pre-notification included in the record related to the scheduled message. In other words, a record in which a pre-notification is set and a time point for receiving the pre-notification has arrived among the records related to the scheduled message stored in correspondence with the first user account may be identified as a scheduled message to be pre-notified.
[0071] FIG. 4 is a diagram illustrating an example of a chat interface screen in which a pre-notification message for a scheduled message is sent according to an embodiment.
[0072] According to one embodiment, the pre-notification message may be sent in the form of an instant message through a specific type of chat room. As an example, referring to screen 401 shown in FIG. 4, a pre-notification message 410 is sent through a chat room with me. The pre-notification message may be sent from an official account related to the reservation message function. The pre-notification message may include information about the reservation message (e.g., the delivery target, the reservation content) and information informing the user that the reservation message is scheduled to be delivered at the scheduled delivery time. The pre-notification message includes an interfacing object 411 connected to a details page for the reservation message. When an input for selecting the interfacing object 411 is received, a details page for the reservation message may be provided.
[0073] Also, as an example, the advance notification message may be sent via a 1:1 chat room with the official account for the scheduled message function.
[0074] 5A to 5C are diagrams illustrating interface screens for generating a subscription message according to an embodiment.
[0075] According to an embodiment, the request to generate a scheduled message may be received through a chat interface corresponding to a secretary mode. The secretary mode is one type of input mode of the chat interface and corresponds to an input mode for calling a secretary function. The secretary function is a function provided to enhance user convenience in addition to functions related to sending and receiving messages in a messenger application, and the above-mentioned scheduled message function corresponds to an example of the secretary function. The secretary function may further include at least one of a search function through a chat room, a schedule management function, and a to-do management function in addition to the scheduled message function. The secretary function may be provided by a messaging server or a separate server linked to the messaging server. The server may provide a chat interface corresponding to the secretary mode to a terminal.
[0076] 5A, the chat interface of the secretary mode includes interfacing objects for calling secretary functions. For example, the chat interface of the secretary mode corresponding to a chat room includes a search window 512 for calling a search function and a secretary function menu 511 including interfacing objects for calling a schedule management function, a to-do management function, and a reservation message function.
[0077] According to one embodiment, when an input for selecting a button included in the secretary function menu 511 is received, the terminal may call up a secretary function corresponding to the selected button. In other words, an input for selecting a button included in the secretary function menu 511 means an input for calling at least one secretary function. As an example, a reserved message function may be called up by an input for selecting a "reserve message" button included in the secretary function menu 511.
[0078] Referring to screen 502 shown in Fig. 5B, when a reserved message function is called through a chat interface converted to secretary mode, an interface for generating a reserved message (hereinafter, reserved message generation interface) is displayed in a partial area of the chat interface. The reserved message generation interface is not limited to the shape of screen 502 shown in Fig. 5B. For example, the reserved message generation interface may be displayed overlapping the chat interface corresponding to the chat room, and may be displayed through a partial area of the chat interface (for example, the upper part of the virtual keyboard, the lower part of the virtual keyboard, or the area where the virtual keyboard is displayed).
[0079] As an example, an input of selecting a "Reserve Message" button in the secretary function menu 511 shown in FIG. 5A corresponds to calling up the reserved message function. The reserved message generation interface can provide a function of generating (or registering) a new reserved message. For example, a user may input information about a new reserved message (e.g., the contents of the reserved message, the scheduled time of sending the reserved message, the recipient of the reserved message, and / or whether or not a pre-notification setting is set for the reserved message) through the reserved message generation interface. A user can request the server to generate a reserved message by input of selecting a "Register" button 521 in the reserved message generation interface. The server generates the requested reserved message and registers it in a reserved message database subordinate to the user's account. According to an embodiment, the "Register" button 521 is not activated unless at least a part of the information about the reserved message (e.g., at least one of the contents of the reserved message, the scheduled time of sending the reserved message, the recipient of the reserved message, and whether or not a pre-notification setting is set for the reserved message) is input.
[0080] According to an embodiment, when a subscription message is generated, a user can input a delivery target of the generated subscription message through a subscription message generation interface. As described above, the delivery target of the subscription message may include at least one user account and / or at least one chat room. By selecting the delivery target item 523, an interface for inputting the delivery target may be provided, such as screen 503 shown in FIG. 5C.
[0081] 5C, the interface for inputting the delivery target may include a list 531 of chat rooms in which the user account is participating. The interface for inputting the delivery target may include a picker for selecting each item included in the list 531 of chat rooms. Although not shown in FIG. 5C, the interface for inputting the delivery target may include a list of user accounts registered as friends with the user account. According to an embodiment, one or more chat rooms and / or one or more user accounts may be selected as targets for sending a reservation message.
[0082] The server according to an embodiment may automatically input chat room information as a delivery target of the reserved message based on the chat room where the request for the reserved message function occurred. For example, if the request for the reserved message function occurs through a specific chat room, the corresponding chat room or a user account participating in the corresponding chat room is automatically input as a delivery target of the reserved message. The user who requested the generation of the reserved message may make modifications, such as deleting the automatically input delivery target of the reserved message or adding a new delivery target of the reserved message, through a reservation message generation interface.
[0083] 6A to 6C are diagrams illustrating interface screens for viewing and editing a scheduled message according to an embodiment.
[0084] As an example, a screen 601 of an interface for querying reserved messages (hereinafter, the reserved message query interface) shown in FIG. 6A is displayed on the terminal in response to an input selecting the “View reservation list” button 522 shown in FIG. 5B.
[0085] 6A, the subscription message inquiry interface includes a list 610 of subscription message-related records registered corresponding to a user account logged into the terminal. A subscription message-related record is a data unit including information on a subscription message (e.g., the content of the subscription message, the scheduled delivery time of the subscription message, the delivery target of the subscription message, and / or whether or not a pre-notification setting for the subscription message is set), and is referred to as a "subscribed message."
[0086] For example, the reserved message inquiry interface may display a list 610 of reserved messages corresponding to the date the reserved message function was called. Also, for example, a list 610 of all reserved messages registered corresponding to a user account may be displayed. For example, the maximum number of reserved messages that can be registered corresponding to a user account may be limited. For example, the number of reserved messages registered corresponding to a user account may be 10 or less.
[0087] A list of scheduled messages 610 according to an embodiment includes scheduled message items 611 and 612 each including information about a scheduled message. For example, a first item 611 included in the list of scheduled messages includes a delivery target 611-1 of the scheduled message, a content 611-2 of the scheduled message, and a scheduled delivery time 611-3 of the scheduled message. The delivery target of the scheduled message may be set to a second user account or a 1:1 chat room with a second user account, as in the delivery target 611-1 of the first item 611, or may be set to a chat room, as in the delivery target 612-1 of the second item 612.
[0088] According to an embodiment, the list of reservation messages 610 may further include information regarding the status (e.g., waiting, shipped, and / or failed shipping) of each item. For example, a reservation message may be in a "waiting" status if it is before the scheduled shipping time, may be in a "shipped" status if the scheduled shipping time arrives and shipping to the shipping target is completed, and may be in a "shipping failed" status if the scheduled shipping time arrives but shipping to the shipping target has not been completed. According to an embodiment, a message in a "shipped" status is not included in the list of reservation messages 610 because it does not correspond to a reservation message any more. According to an embodiment, the reservation messages may be displayed in a list by status. For example, a list of reservation messages in a "waiting" status, a list of reservation messages in a "shipped" status, and a list of reservation messages in a "shipping failed" status may be displayed through respective interfaces, and the lists by status may be displayed by separating them from each other through different tabs.
[0089] According to an embodiment, the reserved message list 610 displayed in the reserved message inquiry interface may preferentially display reserved messages corresponding to the date on which the reserved message management function is called. For example, if the reserved message management function is called on November 18, 2021, reserved messages corresponding to November 18, 2021 may be preferentially displayed.
[0090] According to an embodiment, the scheduled messages included in the list of scheduled messages 610 may be sorted in chronological order of their scheduled delivery times. For example, as shown in screen 601 in Fig. 6A, the scheduled message items 611 and 612 included in the list of scheduled messages may be sorted in order from the scheduled message with the earliest delivery time to the scheduled message with the latest delivery time.
[0091] According to one embodiment, a scheduled message inquiry interface may be provided with a function for registering a new scheduled message. Upon selection of the "Schedule a message" button 620, an interface for registering a new scheduled message may be provided.
[0092] According to one embodiment, the reserved message inquiry interface can provide a function for editing a registered reserved message. When selecting a reserved message item 611, 612, an interface for editing the selected reserved message is provided.
[0093] As an example, the interface screen 602 for registering a new scheduled message shown in FIG. 6B may be displayed on the terminal in response to a new scheduled message registration function being invoked by an input selecting the “Schedule a Message” button 620 shown in FIG. 6A.
[0094] 6B, the user may input information about the new subscribed message (e.g., the content of the subscribed message, the time when the subscribed message is scheduled to be sent, the recipients of the subscribed message, and whether or not a notification is set for the subscribed message) through an interface for registering a new subscribed message. The user may request the server to generate a subscribed message corresponding to the information input by selecting a "Register" button 630 in the interface for registering a new subscribed message. The server may generate the requested subscribed message and register it in a subscribed message database subordinate to the user's account.
[0095] As an example, the interface screen 603 for editing a reserved message shown in FIG. 6C may be displayed on the terminal in response to a reserved message editing function being invoked by an input selecting the reserved message item 611 shown in FIG. 6A.
[0096] Referring to FIG. 6C, a user can modify information about a registered reserved message (e.g., the content of the reserved message 641, the scheduled time of sending the reserved message 642, the recipients of the reserved message 643, and whether or not notifications are set for the reserved message 644) through an interface for editing the reserved message.
[0097] For example, the time during which a registered reserved message can be edited may be limited based on the scheduled delivery time of the reserved message. For example, if the time remaining until the scheduled delivery time set for the reserved message is less than a threshold time, editing of the reserved message is limited. For example, editing of a reserved message that has already been sent and / or a reserved message that has failed to be sent is limited.
[0098] A server providing a secretary function linked to an app for a messaging service according to an embodiment includes a processor, a memory, and a communication module.
[0099] The processor of the server according to an embodiment may perform at least one of the operations of the server described above with reference to Fig. 1. For example, the processor of the server may perform at least one of the operations of step S110 of identifying a scheduled message to be sent based on a record related to the scheduled message stored corresponding to a first user account that subscribes to the messaging service described above with reference to Fig. 1, step S120 of determining whether a chat room corresponding to a destination of the identified scheduled message is valid, and step S130 of sending the identified scheduled message via the chat room.
[0100] The memory of the server according to an embodiment may store data necessary for performing the method described above with reference to Fig. 1 and / or data generated by the execution of the method described above with reference to Fig. 1. The memory may be a volatile memory or a non-volatile memory.
[0101] According to one embodiment, the memory of the server stores a program embodying the method described above with reference to Figure 1. The processor of the server can execute the program stored in the memory to control the server. Code of the program executed by the processor of the server is stored in the memory.
[0102] The server on one side is connected to an external device (eg, a terminal or a network) via a communication module to exchange data.
[0103] The embodiments described above may be implemented using hardware components, software components, or a combination of hardware and software components. For example, the devices and components described herein may be implemented using one or more general-purpose or special-purpose computers, such as a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable array (FPA), a programmable logic unit (PLU), a microprocessor, or other devices that execute and respond to instructions. The processing device executes an operating system (OS) and one or more software applications that run on the operating system. The processing device also accesses, stores, manipulates, processes, and generates data in response to the execution of the software. For ease of understanding, the processing device may be described as being one in which only one processing device is used, but one skilled in the art will appreciate that the processing device may include multiple processing elements and / or multiple types of processing elements. For example, the processing device may include multiple processors or one processor and one controller. Other processing configurations, such as parallel processors, are also possible.
[0104] The software may include computer programs, codes, instructions, or any combination of one or more thereof, which may configure or instruct a processing device to operate as desired, either independently or in combination. The software and / or data may be embodied in any type of machine, component, physical device, virtual device, computer storage medium or device, or transmitted signal wave, either permanently or temporarily, to be interpreted by the processing device or to provide instructions or data to the processing device. The software may be distributed over computer systems coupled to a network, and may be stored and executed in a distributed manner. The software and data may be stored on one or more computer readable recording media.
[0105] The method according to the present invention may be 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 may include program instructions, data files, data structures, and the like, alone or in combination. The recording medium and the program instructions may be specially designed and constructed for the purposes of the present invention, or may be well 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 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.
[0106] The hardware devices described above may be configured to operate as one or more software modules to perform the operations illustrated in the present invention, and vice versa.
[0107] Although the embodiments have been described above with reference to limited drawings, those skilled 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 form than described, and may be replaced or substituted with other components or equivalents to achieve appropriate results.
[0108] Accordingly, other implementations, embodiments, and equivalents of the claims are intended to be within the scope of the following claims.
Claims
1. A method for operating a server that provides a scheduled message function linked with an app for a messaging service, comprising: identifying a subscription message to be delivered based on a stored subscription message record corresponding to a first user account subscribed to the messaging service; determining whether a chat room corresponding to the identified reserved message delivery target is valid; sending the identified reservation message through the chat room based on the validity determination; Including, The step of determining whether the chat room is valid includes a step of determining that the chat room is valid if there is a history of messages being sent or received through the chat room.
2. 2. The method of claim 1, wherein a receipt confirmation status for a message received through the chat room before the scheduled message is sent is changed in response to a connection of the chat room to a terminal logged in with the first user account.
3. 3. The method of claim 2, further comprising the step of controlling a chat interface provided to a terminal logged in with a participant account of the chat room to display a modified receipt confirmation status for messages sent via the chat room.
4. The method of claim 1 , wherein the reserved message is displayed in a chat interface corresponding to the chat room together with an indication to distinguish the reserved message from general messages.
5. identifying a scheduled message that is to be pre-notified based on information regarding a pre-notification setting included in a record relating to the scheduled message; sending a pre-notification message to notify the first user account that the reservation message to be notified is scheduled to be sent through a chat room of a specific type corresponding to the first user account; The method of claim 1 further comprising:
6. The reservation message is sent to: a second user account subscribed to the messaging service; A chat room generated by the messaging service; 2. A method of operating the server of claim 1, comprising at least one of:
7. 2. The method of claim 1, wherein identifying the scheduled delivery reservation message comprises identifying the scheduled delivery reservation message based on information about a scheduled delivery time included in the record.
8. The step of determining that the chat room is valid includes:
2. The method of claim 1, further comprising determining that the chat room is valid if there is a history of messages being sent and received via the chat room and if participant information for the chat room has not been changed.
9. The step of sending the identified subscription message comprises: if the chat room is determined to be valid, sending the identified subscription message through the chat room; if it is determined that the chat room is not valid, notifying the terminal logged in with the first user account that the scheduled message will not be sent; 2. A method of operating a server according to claim 1, comprising:
10. The method of claim 1 , wherein the record relating to the subscription message includes at least one of the contents of the subscription message, a scheduled time for sending the subscription message, a recipient of the subscription message, and a pre-notification setting for the subscription message.
11. The step of identifying a reservation message to be sent includes: modifying the record based on a request to edit the record for the subscription message; identifying the scheduled delivery message based on the modified record; 2. A method of operating a server according to claim 1, comprising:
12. 12. The method of claim 11, wherein modifying the record includes restricting modification of the record if the time remaining until the scheduled delivery time included in the record is less than a threshold time.
13. A computer program stored on a non-transitory computer-readable recording medium for performing the method according to any one of claims 1 to 12 in combination with hardware.
14. A server that provides a scheduled message function linked with an application for a messaging service, identifying a scheduled message to be delivered based on a scheduled message record stored corresponding to a first user account subscribed to the messaging service; determining whether a chat room corresponding to the first user account and the identified scheduled message delivery target is valid; at least one processor that routes the identified reservation message through the chat room based on the validity determination; The processor, The server determines that the chat room is valid if there is a history of messages being sent and received through the chat room in determining whether the chat room is valid.
15. The server of claim 14, wherein a receipt confirmation status for a message received through the chat room prior to sending the reserved message is changed in response to a connection of the chat room to a terminal logged in with the first user account.
16. 16. The server of claim 15, wherein the processor controls a chat interface provided to a terminal logged in with a participant account of the chat room to display a modified acknowledgement status for messages sent via the chat room.
17. The server according to claim 14, wherein the reserved message is displayed in a chat interface corresponding to the chat room together with an indication to distinguish the reserved message from general messages.
18. The processor, Identifying a scheduled message that is a subject of a pre-notification based on information regarding a pre-notification setting included in the record relating to the scheduled message; The server according to claim 14, wherein a pre-notification message for notifying that the reservation message subject to the pre-notification is scheduled to be sent is sent via a chat room of a specific type corresponding to the first user account.
19. The processor, In identifying the scheduled delivery message, modifying the record based on a request to edit the record for the subscription message; The server of claim 14 , further comprising: a server configured to identify the scheduled delivery message based on the modified record.
20. 20. The server of claim 19, wherein the processor, in modifying the record, limits the modification of the record if the time remaining until a scheduled dispatch time included in the record is less than a threshold time.
Citation Information
Patent Citations
Message management device, message management system and message management method
JP2020154403A
Method, system, and non-transitory computer-readable recording medium for providing reminder message
JP2020177665A
