Schedule notification method and system using instant messaging application

Abstract

The present disclosure provides a method for schedule notification using an instant messaging application, performed by at least one processor. [Solution] The schedule notification method includes the steps of acquiring a schedule message generated based on date information registered in a schedule application, determining a notification date and time based on the schedule message, and displaying the schedule message in a schedule notification area at the determined notification date and time.

Description

[Technical Field]

[0001] The present disclosure relates to a method and system for notifying a user of a schedule, and more particularly to a method and system for notifying a user of a schedule by utilizing an instant messaging application. [Background technology]

[0002] With the widespread use of mobile devices such as smartphones and the development of the Internet, instant messaging applications on mobile devices have become widely used. Users of instant messaging applications on mobile devices can exchange various messages with other users through chat rooms. In addition to message sending and receiving functions, instant messaging applications also have a variety of functions such as search, games, video calls, etc.

[0003] Meanwhile, some instant messaging applications are equipped with a schedule notification function. To use this schedule notification function, a user must enter a chat room created by the instant messaging application, select a schedule registration menu included in the chat room, and then register their own schedule. As such, to use the schedule management function provided by conventional instant messaging applications, a user must enter a chat room and directly register information related to their schedule, which is inconvenient. Furthermore, to check a schedule using the schedule management function provided by conventional instant messaging applications, a user must enter a chat room, click a link in a message, and perform a predetermined procedure according to the purpose, which is inconvenient. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Korean Patent Publication No. 10-2016-0034029 Summary of the Invention [Problem to be solved by the invention]

[0005] The present disclosure provides a schedule notification method using an instant messaging application, a computer program stored on a recording medium, and an apparatus (system) for solving the above-mentioned problems. [Means for solving the problem]

[0006] The present disclosure may be implemented in various ways, including as a method, an apparatus (system), and / or a computer program stored on a computer-readable recording medium, or a computer-readable recording medium having a computer program stored thereon.

[0007] According to one embodiment of the present disclosure, a method for notifying a schedule using an instant messaging application, performed by at least one processor, includes the steps of: acquiring a schedule message generated based on date information registered in the schedule application; determining a notification date and time based on the schedule message; and displaying the schedule message in a schedule notification area at the determined notification date and time.

[0008] According to one embodiment of the present disclosure, the schedule message is generated by an external device converting date information registered in a schedule application into a format related to the instant messaging application, and the step of obtaining the schedule message includes a step of receiving the schedule message from the external device.

[0009] According to one embodiment of the present disclosure, the step of obtaining a schedule message includes the steps of obtaining schedule information registered in a schedule application, and generating a schedule message by converting the obtained schedule information into a format related to the instant messaging application.

[0010] According to one embodiment of the present disclosure, the step of displaying a schedule message in a schedule notification area includes the steps of identifying a schedule type included in the schedule message and displaying graphic information related to the identified schedule type in the schedule notification area together with at least a portion of the schedule message, and multiple schedule messages corresponding to different schedule types may be displayed in the schedule notification area.

[0011] According to one embodiment of the present disclosure, the schedule notification method further includes a step of receiving a first user input for selecting the schedule message displayed in the schedule notification area after displaying the schedule message in the schedule notification area, and a step of executing an online meeting link included in the schedule message in response to receiving the first user input, and an online meeting application associated with the schedule message can be executed in response to the execution of the online meeting link.

[0012] According to one embodiment of the present disclosure, the step of executing the link for an online meeting included in the schedule message includes the steps of determining whether there are multiple meetings that can be attended at the current time based on at least one saved schedule message, displaying a list of meetings that can be attended at the current time in response to determining that there are multiple meetings that can be attended at the current time, obtaining a link for any meeting selected by the user from the displayed list of meetings, and executing the obtained link.

[0013] According to one embodiment of the present disclosure, the schedule notification method further includes a step of identifying a schedule end date and time included in the schedule message after displaying the schedule message in the schedule notification area, and a step of removing the schedule message from the schedule notification area in response to determining that the end date and time has passed.

[0014] According to one embodiment of the present disclosure, the schedule notification method further includes a step of receiving a second user input for selecting the schedule message displayed in the schedule notification area after displaying the schedule message in the schedule notification area, and a step of removing the schedule message from the schedule notification area in response to receiving the second user input.

[0015] According to one embodiment of the present disclosure, the step of displaying a schedule message in a schedule notification area includes the steps of calculating the time remaining until the schedule start date / time or the schedule end date / time included in the schedule message, visualizing the schedule message using a first graphic element if it is determined that the calculated remaining time is within a first range, and visualizing the schedule message using a second graphic element if it is determined that the calculated remaining time is within a second range.

[0016] According to one embodiment of the present disclosure, the step of displaying a schedule message in a schedule notification area includes the steps of identifying a destination included in the schedule message, calculating an estimated travel time to the destination based on the user's means of transportation or travel speed, the user's current location, and the destination, and displaying the calculated estimated travel time in the schedule notification area together with at least a portion of the schedule message.

[0017] According to one embodiment of the present disclosure, the schedule notification method further includes a step of determining whether the user has arrived at the destination after displaying the schedule message in the schedule notification area, and a step of removing the schedule message from the schedule notification area in response to determining that the user has arrived at the destination.

[0018] According to one embodiment of the present disclosure, the step of displaying the schedule message in the schedule notification area includes the steps of identifying the destination and participants included in the schedule message; obtaining the user's current location and the participants' current locations; calculating a first estimated time it will take for the user to reach the destination based on the user's means of transportation or travel speed, the user's current location, and the destination; calculating a second estimated time it will take for the participants to reach the destination based on the participants' means of transportation or travel speed, the participants' current location, and the destination; and displaying the first estimated time and the second estimated time together with at least a portion of the schedule message in the schedule notification area.

[0019] According to one embodiment of the present disclosure, the step of displaying the schedule message in the schedule notification area further includes the steps of displaying a third graphic element related to the destination in the schedule notification area, displaying a fourth graphic element related to the user in the schedule notification area based on a first estimated duration, and displaying a fifth graphic element related to the participants in the schedule notification area based on a second estimated duration, wherein the distance between the third graphic element and the fourth graphic element may be determined based on the first estimated duration, and the distance between the third graphic element and the fifth graphic element may be determined based on the second estimated duration.

[0020] According to one embodiment of the present disclosure, the schedule notification method further includes a step of determining whether the user and all participants have arrived at the destination after displaying the schedule message in the schedule notification area, and a step of removing the schedule message from the schedule notification area in response to determining that the user and all participants have arrived at the destination.

[0021] According to one embodiment of the present disclosure, the schedule notification method further includes a step of obtaining an event message including an event area, a step of determining whether the user's current location is included in the event area, and a step of displaying the event message in the schedule notification area in response to determining that the user's current location is included in the event area.

[0022] According to one embodiment of the present disclosure, the schedule notification method further includes, after the step of displaying the event message in the schedule notification area, a step of determining whether the user has left the event area, and a step of removing the event message from the schedule notification area in response to determining that the user has left the event area.

[0023] According to one embodiment of the present disclosure, the schedule notification area may be included in at least one of a screen area where a conversation list of an instant messaging application is displayed, a home screen area of ​​the instant messaging application, or a screen area where a widget of a user terminal is displayed.

[0024] According to an embodiment of the present disclosure, the schedule notification method further includes, when a schedule message is acquired, displaying a schedule management message related to managing the schedule message in a conversation list of the instant messaging application, and displaying a user interface related to editing the schedule message in response to receiving a third user input selecting the schedule management message.

[0025] A computer-readable non-transitory recording medium may be provided that stores instructions for executing the above-described schedule notification method by a computer.

[0026] A user terminal according to one embodiment of the present disclosure includes a communication module, a memory, and at least one processor coupled to the memory and configured to execute at least one computer-readable program contained in the memory, wherein the at least one program includes instructions for obtaining a schedule message generated based on schedule information registered in a schedule application, determining a notification date and time based on the schedule message, and displaying the schedule message in a schedule notification area at the determined notification date and time. [Effects of the Invention]

[0027] According to some embodiments of the present disclosure, when schedule information is registered in a schedule application, a schedule message may be automatically generated based on the registered schedule information, and the schedule message may be displayed in a schedule notification area at the notification date and time through an instant messaging application. This eliminates the inconvenience of a user having to enter a chat room and separately register a schedule, and minimizes the input required from the user to register a schedule message. Furthermore, since entry into a chat room is not required to register a schedule message, and a schedule message based on instant messaging is automatically generated in conjunction with a schedule application that the user is familiar with, user convenience when registering a schedule message is improved. Furthermore, the schedule message may be easily viewed from the schedule notification area without entering a chat room of the instant messaging application.

[0028] According to some embodiments of the present disclosure, a schedule message may be displayed along with graphic information based on the type of the schedule message, allowing a user to intuitively identify the type of schedule message and quickly grasp various information through various types of schedule messages.

[0029] According to some embodiments of the present disclosure, when a user input for selecting a schedule message is received, an online conference application associated with a link included in the schedule message may be automatically executed, thereby reducing the inconvenience to the user of having to enter a chat room or separately execute an online conference application when proceeding with the corresponding schedule.

[0030] According to some embodiments of the present disclosure, when a schedule message includes a destination, an estimated travel time for the user or participant to reach the destination may be displayed along with at least a portion of the schedule message, allowing the user to intuitively estimate the participant's or participant's arrival time.

[0031] According to some embodiments of the present disclosure, various graphic elements may be displayed with at least a portion of a schedule message based on the time remaining until the start date / time or end date / time of the schedule, allowing a user to intuitively check the time remaining until the start date / time or end date / time of the schedule.

[0032] The effects of the present disclosure are not limited to those described above, and other effects not described will be clearly understood by a person having ordinary knowledge in the technical field to which the present disclosure pertains (hereinafter referred to as "ordinary engineer") from the description in the claims. [Brief explanation of the drawings]

[0033] Embodiments of the present disclosure will now be described with reference to the accompanying drawings, as described below, in which like reference numerals indicate like elements, but not limited to the drawings. [Figure 1] 1 is a diagram illustrating an example of a screen of a user terminal including a schedule message according to an embodiment of the present disclosure. [Figure 2] 1 is a schematic diagram illustrating a configuration in which an information processing system is connected to a plurality of user terminals so as to be able to communicate with each other, according to an embodiment of the present disclosure; [Figure 3] FIG. 2 is a block diagram illustrating an internal configuration of a user terminal and an information processing system according to an embodiment of the present disclosure. [Figure 4] FIG. 2 is a block diagram illustrating the internal configuration of a processor of a user terminal according to an embodiment of the present disclosure. [Figure 5] 4 is a flowchart illustrating a process of obtaining a schedule message in a user terminal according to an embodiment of the present disclosure. [Figure 6] 1 is a diagram illustrating a first user interface provided in a schedule application according to an embodiment of the present disclosure. [Figure 7] 10 is a diagram illustrating an example of a screen of a user terminal on which a first schedule message is displayed according to an embodiment of the present disclosure. [Figure 8] 10 is a diagram illustrating an example of a screen of a user terminal in which a second schedule message is visualized with different graphic elements over time, according to an embodiment of the present disclosure. [Figure 9] 10 is a diagram illustrating an example of a screen of a user terminal on which a third schedule message is displayed according to an embodiment of the present disclosure. [Figure 10] 10 is a diagram illustrating an example of a screen of a user terminal in which graphic elements related to a fourth schedule message are updated over time according to an embodiment of the present disclosure. [Figure 11] 10 is a diagram illustrating an example of a screen of a user terminal on which an event message is displayed according to an embodiment of the present disclosure. [Figure 12]1 is a diagram illustrating an example of a screen of a user terminal in which a schedule message is displayed through a schedule notification area fixed at the top of a conversation list according to an embodiment of the present disclosure. [Figure 13] 10 is a diagram illustrating an example of a second user interface related to editing a schedule message according to an embodiment of the present disclosure. [Figure 14] 1 is a flowchart illustrating a schedule notification method using an instant messaging application according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0034] Hereinafter, specific details for implementing the present disclosure will be described in detail with reference to the accompanying drawings, however, in the following description, detailed descriptions of well-known functions and configurations will be omitted if they may unnecessarily obscure the gist of the present disclosure.

[0035] In the accompanying drawings, the same or corresponding components are denoted by the same reference numerals. In addition, in the following description of the embodiments, duplicated descriptions of the same or corresponding components may be omitted. However, even if technology related to a component is omitted, it is not intended that such a component is not included in a certain embodiment.

[0036] The advantages and features of the disclosed embodiments, and methods for achieving them, will become apparent from the following description of the embodiments taken in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below, and may be embodied in various different forms. However, the present embodiments are provided merely to complete the disclosure and fully convey the scope of the invention to those skilled in the art.

[0037] The terms used in this specification will be briefly explained, and the disclosed embodiments will be described in detail. The terms used in this specification are currently commonly used and general terms that have been selected as much as possible while taking into consideration the function of the present disclosure. However, these terms may change depending on the intentions of engineers in the relevant field, precedents, the emergence of new technologies, etc. In addition, in certain cases, the applicant may arbitrarily select terms, and in such cases, the meanings of these terms will be described in detail in the relevant description of the invention. Therefore, the terms used in this disclosure should be defined based on the meanings of the terms and the overall content of the present disclosure, rather than simply by their names.

[0038] In this specification, the singular expression includes the plural expression unless the context clearly dictates otherwise. Furthermore, the plural expression includes the singular expression unless the context clearly dictates otherwise. When a part throughout the specification includes a certain element, this does not mean that it excludes other elements, but that it may further include other elements, unless otherwise specified.

[0039] Additionally, the terms "module" and "module" used in this specification refer to a software or hardware component, and a "module" or "module" performs a certain function. However, the terms "module" and "module" are not limited to software or hardware. A "module" or "module" may be configured to reside on an addressable storage medium or to execute on one or more processors. Thus, by way of example, a "module" or "module" may include components such as software components, object-oriented software components, class components, and task components, as well as at least one of a process, function, attribute, procedure, subroutine, program code segment, driver, firmware, microcode, circuit, data, database, data structure, table, array, or variable. The functionality provided within a component and "module" or "module" may be combined into fewer components and "modules" or "modules," or further separated into additional components and "modules" or "modules."

[0040] According to one embodiment of the present disclosure, a "module" or "unit" may be embodied with a processor and memory. "Processor" should be broadly interpreted to include a general-purpose processor, a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a controller, a microcontroller, a state machine, etc. In some circumstances, "processor" may refer to an application-specific semiconductor (ASIC), a programmable logic device (PLD), a field-programmable gate array (FPGA), etc. "Processor" may refer to a combination of processing devices, such as, for example, a combination of a DSP and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors in conjunction with a DSP core, or any other such configuration. Additionally, "memory" should be broadly interpreted to include any electronic component capable of storing electronic information. "Memory" may refer to various types of processor-readable media, such as random access memory (RAM), read-only memory (ROM), non-volatile random access memory (NVRAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable PROM (EEPROM), flash memory, magnetic or optical data storage devices, registers, etc. Memory is said to be in electronic communication with a processor if the processor can read information from and store information in the memory. Memory that is integrated into a processor is in electronic communication with the processor.

[0041] In the present disclosure, a "system" may include at least one of a server device and a cloud device, but is not limited thereto. For example, a system may be configured with one or more server devices. As another example, a system may be configured with one or more cloud devices. As yet another example, a system may be configured and operated by both a server device and a cloud device.

[0042] Furthermore, terms such as 1st, 2nd, A, B, (a), (b) etc. used in the following embodiments are merely used to distinguish one component from another, and do not limit the essence, order or sequence of the corresponding components.

[0043] Furthermore, in the following embodiments, when a component is described as being "coupled," "coupled," or "connected" to another component, it should be understood that the component may be directly coupled or connected to the other component, but that there may also be other components "coupled," "coupled," or "connected" between each component.

[0044] Furthermore, when used in the following embodiments, "comprises" and / or "comprising" does not exclude the presence or addition of one or more other components, steps, operations and / or elements to a referenced component, step, operation and / or element.

[0045] Before describing the various embodiments of the present disclosure, it is helpful to explain the terminology used. In an embodiment of the present disclosure, a "schedule message" is an instant message related to a schedule and may include at least one of a schedule start date and time or an end date and time. Additionally, the schedule message may include at least one of a title, a location, a notification date and time, a link, participant identification information, a note, or an attachment.

[0046] In an embodiment of the present disclosure, a "graphic element" is data used to display various graphic information on a screen, and may include at least one of text, numbers, colors, figures, images, or animations.

[0047] Various embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings.

[0048] 1 is a diagram illustrating an example of a screen 120 of a user terminal 100 including a schedule message 140 according to an embodiment of the present disclosure. According to an embodiment, the user terminal 110 may display conversation messages 130 exchanged with conversation partners through an instant messaging application in a conversation list. The conversation list of FIG. 1 is illustrated as including conversation messages 130 exchanged between the user and "Brown," "Sally," and "Cony," respectively.

[0049] According to one embodiment, various types of schedule messages 140 may be displayed in the conversation list of the user terminal 110. The schedule messages 140 may be displayed fixedly in a certain area within the overall area where the conversation list is displayed. Alternatively, the schedule messages 140 may be displayed in the overall area where the conversation list is displayed, arranged in chronological order of receipt together with general conversation messages 130. Additionally or alternatively, the schedule messages 140 may be displayed in the home screen area of ​​the instant messaging application or in the screen area where the widget of the user terminal 110 is displayed.

[0050] 1 illustrates four types of schedule messages 140, at least one of which may be generated based on schedule information registered in a schedule application, where the schedule application may be an application for schedule management installed in the user terminal 110.

[0051] The first type of schedule message (schedule message related to Spot Meeting) illustrated in FIG. 1 may be a schedule message related to joining a meeting, and the second type of schedule message (schedule message related to Spot Privacy) may be a message to remind a person of their schedule. The third type of schedule message (schedule message related to Spot Location) illustrated in FIG. 1 may be a schedule message related to an appointment location, and the fourth type of schedule message (schedule message related to an arrow graphic) may be a schedule message related to a gathering with multiple participants. Also, as illustrated in FIG. 1, a location-based event message 150 may be displayed in the conversation list.

[0052] In one embodiment, the schedule message may be displayed in a schedule notification area. The schedule notification area may be at least one of a screen area where a conversation list of an instant messaging application is displayed, a home screen area of ​​the instant messaging application, or a screen area where a widget of the user terminal is displayed. An event message may also be displayed in the schedule notification area together with the schedule message.

[0053] As illustrated in FIG. 1, schedule messages may be categorized into various types. Graphic information displayed for each schedule message may differ depending on the type. Here, a profile image associated with the type of the corresponding schedule message may be used as the graphic information. As illustrated in FIG. 1, "M" may be displayed as a profile image associated with a first type of schedule message, and "P" may be displayed as a profile image associated with a second type of schedule message. "L" may be displayed as a profile image associated with a third type of schedule message, and "R" may be displayed as a profile image associated with a fourth type of schedule message. Furthermore, "E" may be displayed as a profile image associated with an event message.

[0054] Additionally or alternatively, the hue of the profile image for each schedule message may be determined to be different depending on the type. For example, the hue of the profile image associated with a first type schedule message, a second type schedule message, a third type schedule message, and a fourth type schedule message may be determined to be a first hue, a second hue, a third hue, and a fourth hue, respectively. The hue of the profile image associated with an event message may be determined to be a fifth hue.

[0055] Various embodiments in which various types of schedule messages and event messages are displayed and subsequently removed will be described in more detail with reference to FIGS.

[0056] 2 is a schematic diagram illustrating a configuration in which an information processing system 230 according to an embodiment of the present disclosure is connected to a plurality of user terminals 210_1, 210_2, and 210_3 so as to be able to communicate with them. As illustrated, the plurality of user terminals 210_1, 210_2, and 210_3 may be connected to the information processing system 230, which can provide an instant messaging service through a network 220. Here, the plurality of user terminals 210_1, 210_2, and 210_3 may include terminals of users who receive the instant messaging service.

[0057] In one embodiment, the information processing system 230 may include one or more server devices and / or databases, or one or more distributed computing devices and / or distributed databases based on a cloud computing service, that can store, provide, and execute computer-executable programs (e.g., downloadable applications) and data related to providing instant messaging services, etc.

[0058] The instant messaging service provided by the information processing system 230 may be provided to users through an instant messaging application installed in each of the user terminals 210_1, 210_2, and 210_3. For example, the information processing system 230 may transmit an instant message received from the user terminals 210_1, 210_2, and 210_3 to a designated destination (i.e., the terminal of the other party in the conversation) through the instant messaging application.

[0059] According to one embodiment, when schedule information is registered in a schedule application installed in the user terminals 210_1, 210_2, and 210_3, the information processing system 230 can receive the schedule information from the user terminals 210_1, 210_2, and 210_3. According to one embodiment, the information processing system 230 can convert the received schedule information into an instant message format (i.e., a format related to the instant messaging application) to generate a schedule message and then transmit the schedule message to the user terminals 210_1, 210_2, and 210_3. The information processing system 230 may include multiple external devices. A method for generating and transmitting a schedule message through multiple external devices will be described below with reference to FIG. 5.

[0060] A plurality of user terminals 210_1, 210_2, and 210_3 can communicate with the information processing system 230 through the network 220. The network 220 can be configured to enable communication between the plurality of user terminals 210_1, 210_2, and 210_3 and the information processing system 230. Depending on the installation environment, the network 220 can be configured as a wired network such as Ethernet, a wired home network (Power Line Communication), a telephone line communication device, and RS-serial communication, a wireless network such as a mobile communication network, a WLAN (Wireless LAN), Wi-Fi, Bluetooth, and ZigBee, or a combination thereof. The communication method is not limited and can include not only a communication method using a communication network (e.g., a mobile communication network, a wired Internet, a wireless Internet, a broadcast network, a satellite network, etc.) that the network 220 can include, but also short-range wireless communication between the user terminals 210_1, 210_2, and 210_3.

[0061] 2, a mobile phone terminal 210_1, a tablet terminal 210_2, and a PC terminal 210_3 are illustrated as examples of user terminals, but the user terminals 210_1, 210_2, and 210_3 may be any computing device capable of wired and / or wireless communication and on which an instant messaging application, a web browser, etc. are installed and run. For example, the user terminal may include an AI speaker, a smartphone, a mobile phone, a navigation system, a computer, a laptop, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a tablet PC, a game console, a wearable device, an internet of things (IoT) device, a virtual reality (VR) device, an augmented reality (AR) device, a set-top box, etc. Also, although FIG. 2 illustrates three user terminals 210_1, 210_2, and 210_3 communicating with the information processing system 230 through the network 220, this is not limited thereto, and a different number of user terminals may be configured to communicate with the information processing system 230 through the network 220.

[0062] According to an embodiment, when the user terminals 210_1, 210_2, and 210_3 receive a schedule message from the information processing system 230, they may determine a notification date and time based on the schedule message and then display the schedule message in a schedule notification area at the notification date and time. Displaying a schedule message in the schedule notification area may mean that at least one of a title, a portion of a body text, or the entire body text included in the schedule message is displayed in the schedule notification area. Here, the body text may include at least one of the appointment location, participants, notes, and attachments.

[0063] FIG. 3 is a block diagram illustrating the internal configuration of a user terminal 210 and an information processing system 230 according to an embodiment of the present disclosure. The user terminal 210 may refer to any computing device capable of executing an instant messaging application or the like and capable of wired / wireless communication, and may include, for example, the mobile phone terminal 210_1, tablet terminal 210_2, or PC terminal 210_3 of FIG. 2. As illustrated, the user terminal 210 may include a memory 312, a processor 314, a communication module 316, and an input / output interface 318. Similarly, the information processing system 230 may include a memory 332, a processor 334, a communication module 336, and an input / output interface 338. As illustrated in FIG. 3, the user terminal 210 and the information processing system 230 may be configured to communicate information and / or data over the network 220 using their respective communication modules 316 and 336. In addition, the input / output device 320 may be configured to input information and / or data to the user terminal 210 or output information and / or data generated by the user terminal 210 via the input / output interface 318.

[0064] The memories 312 and 332 may include any non-transitory computer-readable recording medium. According to one embodiment, the memories 312 and 332 may include a permanent mass storage device such as a read only memory (ROM), a disk drive, a solid state drive (SSD), or a flash memory. As another example, a permanent mass storage device such as a ROM, an SSD, a flash memory, or a disk drive may be included in the user terminal 210 or the information processing system 230 as a separate permanent storage device distinct from the memory. The memories 312 and 332 may also store an operating system and at least one program code (e.g., code for an instant messaging application installed and operated in the user terminal 210).

[0065] These software components may be loaded from a computer-readable recording medium separate from the memories 312, 332. Such separate computer-readable recording medium may include a recording medium directly connectable to the user terminal 210 and the information processing system 230, such as a floppy drive, disk, tape, DVD / CD-ROM drive, or memory card. As another example, the software components may be loaded into the memories 312, 332 through a communication module that is not a computer-readable recording medium. For example, at least one program may be loaded into the memories 312, 332 based on a computer program installed by a file provided over the network 220 by a developer or a file distribution system that distributes application installation files.

[0066] The processors 314, 334 may be configured to process computer program instructions by performing basic arithmetic, logic, and input / output operations. The instructions may be provided to the processors 314, 334 by the memory 312, 332 or the communication modules 316, 336. For example, the processors 314, 334 may be configured to execute instructions received from program code stored in a storage device such as the memory 312, 332.

[0067] The communication modules 316 and 336 may provide a configuration or function for the user terminal 210 and the information processing system 230 to communicate with each other via the network 220, and may provide a configuration or function for the user terminal 210 and / or the information processing system 230 to communicate with other user terminals or other systems (e.g., a separate cloud system). For example, a request or data (e.g., a conversation message) generated by the processor 314 of the user terminal 210 via program code stored in a storage device such as the memory 312 may be transmitted to the information processing system 230 via the network 220 under the control of the communication module 316. Conversely, a control signal or command provided by the processor 334 of the information processing system 230 may be received by the user terminal 210 via the communication module 316 of the user terminal 210 via the communication module 336 and the network 220. For example, the user terminal 210 may receive a conversation message, a schedule message, etc. from the information processing system 230.

[0068] The input / output interface 318 may be a means for interfacing with the input / output device 320. For example, the input device may include a camera including an audio sensor and / or an image sensor, a keyboard, a microphone, a mouse, etc., and the output device may include a display, a speaker, a haptic feedback device, etc. As another example, the input / output interface 318 may be a means for interfacing with a device that integrates components or functions for performing input and output, such as a touch screen. For example, when the processor 314 of the user terminal 210 processes instructions of a computer program loaded in the memory 312, a service screen configured using information and / or data provided by the information processing system 230 or another user terminal may be displayed on the display through the input / output interface 318. Although FIG. 3 illustrates the input / output device 320 as not being included in the user terminal 210, this is not limited thereto and the input / output device 320 may be configured as a single device together with the user terminal 210. In addition, the input / output interface 338 of the information processing system 230 may be a means for interfacing with an input or output device (not shown) that may be connected to or included in the information processing system 230. Although the input / output interfaces 318 and 338 are illustrated as elements configured separately from the processors 314 and 334 in FIG. 3, this is not limiting, and the input / output interfaces 318 and 338 may be configured to be included in the processors 314 and 334.

[0069] The user terminal 210 and the information processing system 230 may include more components than those shown in FIG. 3 . However, it is not necessary to explicitly illustrate most conventional components. According to one embodiment, the user terminal 210 may be embodied to include at least some of the input / output devices 320 described above. The user terminal 210 may also include other components such as a transceiver, a global positioning system (GPS) module, a camera, various sensors, a database, etc. For example, if the user terminal 210 is a smartphone, it may include components typically included in a smartphone. For example, the user terminal 210 may be embodied to further include various components such as an acceleration sensor, a gyro sensor, an image sensor, a proximity sensor, a touch sensor, an illuminance sensor, a camera module, various physical buttons, buttons using a touch panel, an input / output port, and a vibrator for vibration.

[0070] While a program for an instant messaging application or the like is running, the processor 314 can receive text, images, videos, sounds, and / or actions entered or selected through an input device such as a touch screen, keyboard, camera including an audio sensor and / or image sensor, or microphone connected to the input / output interface 318, and can store the received text, images, videos, sounds, and / or actions in the memory 312 or provide them to the information processing system 230 via the communication module 316 and the network 220.

[0071] The processor 314 of the user terminal 210 may be configured to manage, process, and / or store information and / or data received from the input / output device 320, other user terminals, the information processing system 230, and / or multiple external systems. The information and / or data processed by the processor 314 may be provided to the information processing system 230 via the communication module 316 and the network 220. The processor 314 of the user terminal 210 may transmit and output information and / or data to the input / output device 320 via the input / output interface 318. For example, the processor 314 may display the received information and / or data on the screen of the user terminal 210.

[0072] The processor 334 of the information processing system 230 may be configured to manage, process, and / or store information and / or data received from multiple user terminals 210 and / or multiple external systems. The information and / or data processed by the processor 334 may be provided to the user terminal 210 via the communication module 336 and the network 220.

[0073] 4 is a block diagram illustrating an internal configuration of the processor 314 of the user terminal according to an embodiment of the present disclosure. As shown, the processor 314 may include a message acquisition unit 410, a message output unit 420, and a message management unit 430.

[0074] The message acquisition unit 410 can receive at least one of a conversation message, a schedule message, or an event message from the information processing system and store it in a storage unit. Additionally or alternatively, the message acquisition unit 410 can generate a schedule message in conjunction with a schedule application installed in the user terminal. For example, the message acquisition unit 410 can generate and store a schedule message based on schedule information registered in the schedule application installed in the user terminal. At this time, the message acquisition unit 410 can generate a schedule message having an instant message format by converting the schedule information into an instant message format. In addition, the message acquisition unit 410 can determine a type of schedule message based on detailed data included in the schedule information and generate a schedule message including identification information (e.g., a type ID) of the determined type.

[0075] According to one embodiment, the message acquisition unit 410 may determine the schedule message as a first type when the schedule information includes link information for an online meeting. Furthermore, the message acquisition unit 410 may determine the schedule message as a second type when the schedule information does not include online meeting information and a destination but includes a schedule date and time. The message acquisition unit 410 may determine the schedule message as a third type when the schedule information includes destination information but does not include participant information. The message acquisition unit 410 may determine the schedule message as a fourth type when the schedule information includes destination information and participant information.

[0076] The message output unit 420 may determine a notification date and time based on the schedule message and display the schedule message in the schedule notification area at the determined notification date and time. According to an embodiment, the schedule message may include a schedule start date and time, and the message output unit 420 may determine the schedule start date and time or a date and time n minutes before the schedule start date and time as the notification date and time. The message output unit 420 may determine the notification date and time based on the type of each schedule message. For example, in the case of a first type of schedule message, the message output unit 420 may determine the notification date and time to be one hour before the schedule start date and time, and in the case of a second type of schedule message, the message output unit 420 may determine the notification date and time to be two hours before the start date and time. As another example, in the case of a third type of schedule message, the message output unit 420 may determine the notification date and time to be three hours before the start date and time, and in the case of a fourth type of schedule message, the message output unit 420 may determine the notification date and time to be four hours before the start date and time.

[0077] Meanwhile, the schedule information registered in the schedule application may include a notification date and time. That is, when a user registers a schedule through the schedule application, the user may register not only the schedule start date and time but also the notification date and time. In this case, the schedule message may include the schedule start date and time and the notification date and time, and the message output unit 420 may display the schedule message in the schedule notification area at the notification date and time included in the schedule message.

[0078] The message management unit 430 may manage the display state of schedule messages displayed in the schedule notification area. According to one embodiment, the message management unit 430 may determine a removal time for a schedule message and remove the schedule message from the schedule notification area at the determined removal time. The message management unit 430 may remove the schedule message from the schedule notification area at the schedule end date and time included in the schedule message. Additionally or alternatively, the message management unit 430 may remove the schedule message from the schedule notification area when a predetermined time has elapsed after the schedule start date and time included in the schedule message. Additionally or alternatively, the message management unit 430 may remove the schedule message from the schedule notification area when a user input (e.g., a touch or click) selecting the schedule message is received. On the other hand, if the schedule message includes a destination, the message management unit 430 may remove the schedule message from the schedule notification area in response to a determination that the user has reached the destination. In this case, the message management unit 430 may periodically or in real time calculate the user's estimated travel time based on at least one of the user's travel speed, the means of travel, the distance from the user's location to the destination, the user's current location, or the destination, and display the calculated estimated travel time together with at least a portion of the schedule message in the schedule notification area until the schedule message is removed from the schedule notification area.

[0079] When a schedule message includes a destination and participants, the message management unit 430 may calculate a first estimated time required for the user to arrive at the destination based on at least one of the user's travel speed, travel mode, distance from the user's location to the destination, the user's current location, or the destination. Additionally, the message management unit 430 may calculate a second estimated time required for the participants to arrive at the destination based on at least one of the participants' travel mode, travel speed, distance from the participant's location to the destination, the participant's current location, or the destination. The message management unit 430 may display the calculated first estimated time and second estimated time in the schedule notification area together with at least a portion of the schedule message. According to an embodiment, the message management unit 430 may remove the schedule message from the schedule notification area upon determining that the user and all participants have arrived at the destination. Alternatively, the message management unit 430 may remove the schedule message from the schedule notification area when a predetermined time has passed since the schedule start time or when the schedule end time has arrived.

[0080] According to an embodiment, the message management unit 430 may provide a user interface for editing each schedule message. For example, when a schedule message is acquired, the message management unit 430 may display a schedule management message related to the management of the schedule message in a conversation list of an instant messaging application. When a user input for selecting a schedule management message is received, the message management unit 430 may display a user interface related to editing the schedule message. When a schedule message is edited through the user interface, the message management unit 430 may update the schedule message based on the edited content. Here, the schedule message to be edited may include at least one of a schedule message displayed in the schedule notification area or a schedule message that is being saved but not displayed in the schedule notification area.

[0081] 5 is a flowchart illustrating a process of acquiring a schedule message 564 in a user terminal 580 according to an embodiment of the present disclosure. Fig. 5 illustrates a method of generating a schedule message through a first external device 540 and a second external device 560 included in an information processing system and transmitting the schedule message to the user terminal 580. Here, the first external device 540 may be a device for interfacing with a schedule application 520, and the second external device 560 may be a device for supporting an instant messaging service. Each of the external devices 540 and 560 may be implemented in the form of a server, or may be installed in a cloud computing system in the form of a virtual machine.

[0082] Schedule information may be registered in the schedule application 520 (522). For example, a user may register schedule information including a schedule start date and time using the schedule application 520 installed in the user terminal 580. Alternatively, a user may register schedule information including a schedule start date and time using a web-based schedule service. The schedule information may additionally include at least one of a schedule end date and time, a title, a memo, web conference-related information, a conference location, a location of the gathering, participant identification information, or creator identification information.

[0083] In one embodiment, the participant identification information or creator identification information may be a mobile phone number or a login ID. Here, the login ID may be a login ID associated with an instant messaging service or a login ID associated with a schedule service. If the login ID associated with the instant messaging service and the login ID associated with the schedule service are different, ID matching information may be stored in the first external device 540.

[0084] The schedule application 520 may be installed in the user terminal 580 or may be an application installed in another user terminal. A first user interface provided through the schedule application 520 will be described later with reference to FIG. 6. Schedule information 524 registered in the schedule application 520 may be transmitted to a first external device 540.

[0085] The first external device 540 may generate a schedule message based on the received schedule information (542). At this time, the first external device 540 may convert the schedule information 524 into an instant message format (i.e., a format associated with an instant messaging application) to generate the schedule message 544.

[0086] The first external device 540 may determine the type of the schedule message based on detailed data included in the schedule information and include identification information (e.g., a type ID) of the determined type in the schedule message. The instant message format used may vary depending on the type of the schedule message. For example, the first external device 540 may determine the schedule message as a first type (e.g., Spot Meeting) if the schedule information includes link information for an online meeting. If the schedule information does not include online meeting information and a destination but includes a schedule start date and time, the first external device 540 may determine the schedule message as a second type (e.g., Spot Privacy). As another example, if the schedule information includes destination information but not participant information, the first external device 540 may determine the schedule message as a third type (Spot Location). If the schedule information includes destination information but not participant information, the first external device 540 may determine the schedule message as a fourth type (Spot Realtime).

[0087] Tables 1 to 4 below show examples of various types of schedule messages.

[0088] [Table 1]

[0089] [Table 2]

[0090] [Table 3]

[0091] [Table 4] Referring to Tables 1 to 4, the schedule message illustrated in Table 1 is a message related to Type 1 (Spot Meeting) and may include a link address for an online meeting. The schedule message illustrated in Table 2 is a message related to Type 2 (Spot Privacy) and may include information to remind the user of their personal life pattern or schedule (e.g., taking medicine). The schedule message illustrated in Table 3 is a message related to Type 3 (Spot Location) and may include a destination and transportation. The schedule message illustrated in Table 4 is a message related to Type 4 (Spot Realtime) and may include a destination, participant information, and transportation for each participant.

[0092] After a schedule message having a specific type is generated, the first external device 540 can transmit the generated schedule message 544 to the second external device 560. At this time, the schedule message 544 can include user identification information. Here, the user identification information is identification information of the user who registered schedule information in the schedule application, and can be a mobile phone number or a login ID associated with an instant messaging application.

[0093] Next, the second external device 560 can extract user identification information included in the schedule message (562). If the type of the schedule message is the fourth type (Spot Realtime), the second external device 560 can additionally extract participant identification information from the schedule message. Here, the participant identification information can be a mobile phone number or a login ID associated with an instant messaging application.

[0094] Thereafter, the second external device 560 may transmit a schedule message 564 to a user terminal 580 associated with the user identification information. If the schedule message 564 includes participant identification information, the second external device 560 may additionally transmit the schedule message to other user terminals associated with the participant identification information.

[0095] The user terminal 580 that has received the schedule message may store the schedule message (582). According to one embodiment, the schedule message may be received and stored through an instant messaging application installed in the user terminal 580. At this time, the instant messaging application installed in the user terminal 580 may not immediately display the received schedule message, but may store it in an undisplayed state until the notification date and time.

[0096] Thereafter, the instant messaging application installed in the user terminal 580 determines the notification date and time based on the schedule start date and time included in the schedule message, and when the notification date and time arrives, the schedule message can be displayed in the schedule notification area (584).

[0097] According to this embodiment, when schedule information is registered in the schedule application, the schedule information is converted into a schedule message in an instant message format through the first external device 540, and the schedule message can be transmitted to the user terminal 580 through the second external device 560. In one embodiment, the first external device 540 and the second external device 560 can be integrated into a single device.

[0098] Meanwhile, according to some embodiments, a schedule message may be generated independently by the user terminal 580. For example, a processor of the user terminal 580 may acquire schedule information registered in a schedule application, convert the acquired schedule information into a format related to an instant messaging application, and generate and store a schedule message. 6 is a diagram illustrating a first user interface 600 provided by a schedule application according to an embodiment of the present disclosure. The first user interface 600 shown in FIG. 6 may be displayed when a specific date is selected in the schedule application.

[0099] 6, the first user interface 600 may include a first input field 602 for entering a title, a second input field 604 for setting the start date / time, end date / time, and schedule recurrence information, and a third input field 606 for determining a calendar to save the schedule. The first user interface 600 may also include a fourth input field 608 for entering participants in conjunction with an address book, a fifth input field 610 for entering a link address for the online conference, a sixth input field 612 for reserving equipment required for the online conference, a seventh input field 614 for entering a location (e.g., a destination or meeting location), an eighth input field 616 for entering notes, a ninth input field 618 for attaching files, and a tenth input field 620 for determining whether the schedule information should be made public.

[0100] 6, an eleventh input field for determining a mode of transportation for at least one of the users or participants may be additionally included in the first user interface 600. The eleventh input field may include a selection list from which one of public transportation, walking, private car, etc. Alternatively, the mode of transportation for the users or participants may be selected by each user through an instant messaging application installed on their own user terminal.

[0101] Among the input fields included in the first user interface 600, information on the schedule start date / time or end date / time included in the second input field 604 may be essential information required to generate schedule information. Data entered from input fields other than the second input field 604 may be additional information for the schedule information.

[0102] The schedule information may include data input through each input field in the first user interface 600. The type of schedule message may be determined based on the detailed data included in the schedule information.

[0103] 7 is a diagram illustrating an example of a screen 710 of a user terminal displaying a first schedule message 712 according to an embodiment of the present disclosure. Here, the first schedule message 712 may be a message corresponding to a first type (Spot Meeting). In FIGS. 7 to 12, the schedule notification area is illustrated as being included in a screen area where a conversation list of an instant messaging application is displayed, but is not limited thereto. For example, the schedule notification area may be included in a home screen area of ​​the instant messaging application or a screen area where a widget of the user terminal is displayed.

[0104] 7, a first schedule message 712 may be displayed in the schedule notification area at the notified date and time. While the first schedule message 712 is displayed, a first user input may be received to select the first schedule message 712. In this case, the online meeting link included in the first schedule message 712 may be immediately executed.

[0105] Meanwhile, when a first user input is received, at least one processor included in the user terminal may determine whether there are multiple conferences available for participation at the current time based on at least one pre-stored schedule message. For example, it may determine whether multiple first-type schedule messages including the current time as a conference time are stored. The processor may display a list of conferences available for participation in response to determining that there are multiple conferences available for participation at the current time. In this case, when the user selects one of the conferences in the displayed list, the processor may obtain a link related to the selected conference and automatically execute the obtained link.

[0106] In response to the execution of the online conference link, an online conference application related to the schedule message is executed, and an online conference screen 720 provided by the online conference application may be displayed on the user terminal. Figure 7 illustrates an example in which an online conference application related to an avatar conference is executed, and an online conference screen 720 including an avatar image (character) is displayed instead of a human image.

[0107] In some embodiments, when the online meeting screen 720 is displayed, the first schedule message 712 may be removed from the schedule notification area. Removing the first schedule message 712 from the schedule notification area may mean that the first schedule message 712 is no longer in the schedule notification area. At this time, the first schedule message 712 may still be stored in the storage means.

[0108] According to this configuration, when a user selects the first schedule message 712, an online conference application associated with the link included in the first schedule message 712 is automatically executed, thereby reducing the user's inconvenience of having to separately execute a corresponding application or enter a chat room to participate in an online conference.

[0109] 8 illustrates user terminal screens 810, 820, and 830 in which second schedule messages 812, 822, and 832 are visualized with different graphic elements over time according to an embodiment of the present disclosure. Here, the second schedule messages 812, 822, and 832 may be messages corresponding to a second type (Spot Privacy).

[0110] 8, a second schedule message 812 may be displayed in the schedule notification area 10 minutes before the start time of the schedule. At this time, the second schedule message 812 may be visualized using a first graphic element and displayed in the schedule notification area, and as time passes, second schedule messages 822, 832 visualized using other graphic elements may be displayed in the schedule notification area. According to one embodiment, at least one processor included in the user terminal may calculate the time remaining until the schedule start date / time or schedule end date / time included in the second schedule message 812, 822, 832, and visualize the second schedule message 812, 822, 832 using a specific graphic element based on the calculated remaining time.

[0111] In FIG. 8, when the remaining time falls within a first range (e.g., 5 to 10 minutes), a second schedule message 812 may be visualized using a first graphic element (e.g., a first color) and displayed in the schedule notification area. When the remaining time falls within a second range (e.g., 1 to 5 minutes), a second schedule message 822 may be visualized using a second graphic element (e.g., a second color). When the remaining time falls within a third range (e.g., within 1 minute), a second schedule message 832 may be visualized using a third graphic element (e.g., a third color). Screens 810, 820, and 830 in FIG. 8 illustrate examples of second schedule messages visualized using different graphic elements as time passes.

[0112] In addition to color, various graphic elements such as visual patterns, icons, animations, etc. may be used to visualize the second schedule message over time. Also, various types of schedule messages other than the second schedule message may be visualized in the same / similar manner.

[0113] According to an embodiment, in response to receiving a second user input selecting the second schedule message, the second schedule message may be completed and removed from the schedule notification area.

[0114] According to the present disclosure, at least a portion of a schedule message is displayed together with various graphic elements based on the time remaining until the schedule start date / time or end date / time, allowing a user to intuitively check the remaining time.

[0115] 9 illustrates exemplary screens 910, 920, and 930 of a user terminal displaying third schedule messages 912, 922, and 932 according to an embodiment of the present disclosure. Here, the third schedule messages 912, 922, and 932 may be messages corresponding to a third type (Spot Location), and the estimated required time may be updated and displayed as time passes. As illustrated in the first screen 910 of FIG. 9, after the third schedule message 912 is displayed in the schedule notification area at the notification date and time, the estimated required time associated with the third schedule messages 922 and 932 may be updated and displayed as in the second screen 920 and the third screen 930 of FIG. 9.

[0116] According to one embodiment, a processor included in the user terminal can identify a destination included in the third schedule message and display the identified destination in a schedule notification area along with at least a portion of the third schedule message. Furthermore, at least one processor included in the user terminal can extract the user's means of transportation included in the third schedule message and determine the user's location. According to one embodiment, the processor can determine the user's location based on a Global Navigation Satellite System (GNSS) signal collected using a GPS module included in the user terminal. In this case, the processor can use a map / guidance application / service (not shown) to obtain an estimated travel time based on the means of transportation, current location, and destination.

[0117] Alternatively, the processor can calculate the user's speed based on the distance traveled by the user during a predetermined time period, and the processor can calculate an expected time to reach the destination based on the user's speed, the user's current location, and the destination.

[0118] The estimated travel time obtained by the processor may be displayed in the schedule notification area together with at least a portion of the third schedule message. FIG. 9 illustrates an example in which a destination included in the third schedule message is extracted and the estimated travel time is displayed in the schedule notification area together with the destination. The estimated travel time may be recalculated in real time or at regular intervals, and the displayed estimated travel time may be updated to the recalculated estimated travel time. As illustrated in FIG. 9, the estimated travel times displayed in 912, 922, and 932 are shown in order of decreasing time.

[0119] On the other hand, when the user arrives at the destination, the third schedule message may be removed from the schedule notification area.

[0120] 10 illustrates user terminal screens 1010, 1020, and 1030 in which graphic elements associated with fourth schedule messages 1012, 1022, and 1032 are updated over time according to an embodiment of the present disclosure. Here, the fourth schedule messages 1012, 1022, and 1032 may be messages corresponding to a fourth type (Spot Realtime). As illustrated in the first screen 1010 of FIG. 10, after the fourth schedule message 1012 is displayed in the schedule notification area on the notification date and time, the estimated duration and the positions of the graphic elements associated with the fourth schedule messages 1022 and 1032 may be updated as time passes, as in the second screen 1020 and the third screen 1030 of FIG. 10.

[0121] According to one embodiment, a processor included in the user terminal can extract the user's means of transportation from the fourth schedule message and determine the user's location. According to one embodiment, the processor can determine the user's location based on GNSS signals collected using a GPS module included in the user terminal. Additionally or alternatively, the processor of the user terminal can calculate the user's movement speed based on the distance traveled by the user during a predetermined period of time.

[0122] Additionally, the processor included in the user terminal may periodically or in real time receive location information from each mobile terminal (not shown in the drawings) owned by a participant (e.g., Sally, Cony). According to one embodiment, each participant may agree to provide location information, and in response to the provision of location information, the processor of the user terminal may receive location information from the mobile terminal owned by each participant and collect the location of each participant. Alternatively, a second external device (instant messaging service server) may receive the location information of the participants periodically or in real time.

[0123] In one embodiment, the processor can calculate a first expected travel time to reach the destination based on the user's transportation mode or travel speed, the user's current location, and the destination. In one embodiment, if the user's transportation mode (e.g., walking, public transportation, or private car) is extracted from the fourth schedule message, the processor can use a map / directions application / service (not shown) to obtain an expected travel time based on the transportation mode, current location, and destination.

[0124] The processor may also calculate an expected time required for each participant to arrive at the destination based on the transportation means or travel speed of each participant, the current location of each participant, and the destination. For example, the processor may calculate a second expected time required for a first participant to arrive at the destination based on the transportation means or travel speed of the first participant, the current location of the first participant, and the destination. As another example, the processor may calculate a third expected time required for a second participant to arrive at the destination based on the transportation means or travel speed of the second participant, the current location of the second participant, and the destination. Alternatively, a second external device (instant messaging service server) may calculate the expected time required for each participant and provide the calculated information to the user terminal.

[0125] FIG. 10 illustrates an example in which a long arrow is displayed in the schedule notification area as a fourth graphic element associated with a destination. Additionally, a fifth graphic element associated with a user may be displayed in the schedule notification area based on a first estimated travel time, a sixth graphic element associated with a first participant may be displayed in the schedule notification area based on a second estimated travel time, and a seventh graphic element associated with a second participant may be displayed in the schedule notification area based on a third estimated travel time. In FIG. 10, the fifth graphic element is the user's name (e.g., "Me"), the sixth graphic element is the name of the first participant (Sally) in the address book, and the seventh graphic element is the name of the second participant (Cony) in the address book. Additionally or alternatively, the user's profile image may be displayed in the schedule notification area as the fifth graphic element, the first participant's profile image may be displayed in the schedule notification area as the sixth graphic element, and the second participant's profile image may be displayed in the schedule notification area as the seventh graphic element.

[0126] The positions of the fifth, sixth, and seventh graphic elements displayed in the schedule notification area may be determined based on the corresponding estimated durations, i.e., the shorter the corresponding estimated durations, the closer the fifth, sixth, and seventh graphic elements may be to the right end of the fourth graphic element.

[0127] The first to third estimated durations are recalculated in real time or at regular intervals, and the position of the fifth, sixth, or seventh graphic element being displayed may be updated based on the recalculated estimated durations. As illustrated in screens 1010, 1020, and 1030 of Figure 10, the estimated durations of the user and each participant become shorter as time passes, and accordingly, the fifth, sixth, and seventh graphic elements gradually move closer to the right end of the fourth graphic element.

[0128] Meanwhile, when a participant or user arrives at the destination, visual information (i.e., Arrival) notifying that the participant (i.e., Cony, Sally) has arrived may be displayed in the schedule notification area, as illustrated in the second screen 1020 and the third screen 1030 of Figure 10. According to one embodiment, when the user and all participants have arrived at the destination, the fourth schedule message may be removed from the schedule notification area.

[0129] 11 is a diagram illustrating an example of a user terminal screen 1110 displaying an event message 1112 according to an embodiment of the present disclosure. Here, the event message 1112 may include an event area. For example, the event area may include a location range within a certain radius based on a specific location.

[0130] At least one processor included in the user terminal may receive an event message from the information processing system and pre-store it. Alternatively, the information processing system may transmit the event message to the user terminal in response to determining that the user terminal is within an event area. The event message may be a message registered by an event organizer. For example, the event message may include the event area, a promotional comment, a discount coupon, an event period, etc.

[0131] The processor may extract the event area included in the event message, compare the event area with the current location of the user terminal, and determine whether the current location of the user terminal is included in the event area. If it is determined that the current location of the user terminal is included in the event area, an event message 1112 may be displayed in the schedule notification area, as in a first screen 1110 illustrated in FIG. 11 .

[0132] When it is determined that the user's location has left the event area, the event message 1112 may be removed from the schedule notification area, as shown in the second screen 1120 of Fig. 11. Additionally or alternatively, when a fourth user input selecting the event message in the schedule notification area is received, detailed content about the event message (e.g., a discount coupon image, event period, etc.) may be displayed, and then the event message 1112 may be removed from the schedule notification area.

[0133] In the above-described embodiment, an example is shown in which conversation messages are displayed in the first area of ​​the entire conversation list area and different types of schedule messages are displayed in the second area. However, the present invention is not limited to this, and schedule messages may be displayed in various forms. For example, messages may be sorted based on the notification date and time of the schedule message and the reception date and time of the conversation message, and then the sorted schedule messages and conversation messages may be displayed in the conversation list. That is, the conversation message with the earliest reception date and time or the schedule message with the earliest notification date and time may be displayed at the top or bottom of the conversation list. In this case, the schedule notification area may be changed as needed based on the reception date and time of the conversation message and / or the notification date and time of the schedule message.

[0134] As another example, a schedule notification message may be fixed to the top, bottom, or middle area of ​​the conversation list, and in this case, multiple schedule messages may be displayed together in the fixed schedule notification area.

[0135] 12 is a diagram illustrating an example of a user terminal screen 1210 in which a schedule message is displayed in a schedule notification area 1212 fixed at the top of a conversation list according to an embodiment of the present disclosure. In FIG. 12, multiple types of schedule messages are shown as being displayed together in the schedule notification area 1212 fixed at the top position.

[0136] 12, a first type schedule message, a second type schedule message, and a fourth type schedule message may be displayed in a schedule notification area 1212 fixed at the top. In FIG. 12, a fourth type schedule message having the latest notification date and time (i.e., the first displayed) is displayed at the rightmost position, a second type schedule message having the second-order notification date and time (i.e., the second-order displayed) is displayed at the middle position, and a first type schedule message having the most recent notification date and time (i.e., the most recently displayed) is displayed at the leftmost position. That is, after each schedule message is sorted in descending order of notification date and time, the schedule messages sorted from left to right may be displayed sequentially.

[0137] Additionally or alternatively, the schedule notification area may be included in at least one of the home screen area of ​​the instant messaging application or the screen area where a widget of the user terminal is displayed. For example, when a user input for selecting the home tab of the instant messaging application is received, a home screen including the schedule notification area may be displayed. In this case, the user can check the schedule message at a glance through the home screen. As another example, the schedule notification area may be implemented in the form of a widget, in which case the schedule notification area may be displayed on a screen associated with the widget (e.g., the background screen of the user terminal). In this case, the user can check the schedule message through the widget-related screen.

[0138] Meanwhile, a second user interface related to editing the schedule message may be provided, and the user can edit the schedule included in the schedule message using the second user interface.

[0139] 13 illustrates an example of a second user interface 1320 related to editing a schedule message according to one embodiment of the present disclosure. As illustrated, when a schedule message or an event message is received, an administration message 1312 related to managing the schedule message and / or event message may be displayed in the conversation list. As illustrated in screen 1310 of FIG. 13, the administration message 1312 may be displayed in the conversation list together with a profile image associated with the administration message.

[0140] In response to receiving a third user input selecting the management message 1312 in the conversation list, the processor may display a second user interface 1320 that allows editing of at least one of the schedule message and the event message.

[0141] The second user interface 1320 displays at least one schedule message 1322, 1324, 1326, 1330 and an event message 1328 displayed in the schedule notification area, and a schedule message or event message selected by the user can be edited. Here, editing a schedule message may mean updating at least one of the date information, appointment location, conference room, participants, etc. The user can change the means of transportation associated with a specific schedule message or set a default means of transportation using the second user interface 1320. Editing an event message may mean editing information related to the event, such as deleting a saved coupon.

[0142] 14 is a flowchart illustrating a method 1400 for notifying a schedule using an instant messaging application according to an embodiment of the present disclosure. The method illustrated in FIG. 14 is merely one embodiment for achieving the object of the present disclosure, and it goes without saying that some steps may be added or deleted as necessary. Furthermore, the method illustrated in FIG. 14 may be performed by at least one processor included in the user terminal illustrated in FIG. 3. For convenience of explanation, the steps illustrated in FIG. 14 will be described as being performed by the processor included in the user terminal illustrated in FIG. 3.

[0143] The processor may acquire a schedule message generated based on schedule information registered in the schedule application (S1410). According to one embodiment, an external device may convert the schedule information registered in the schedule application into a format related to an instant messaging application to generate a schedule message, and the processor may receive the schedule message from the external device. According to some embodiments, the processor may acquire schedule information registered in the schedule application and convert the acquired schedule information into a format related to the instant messaging application to generate a schedule message.

[0144] The processor can then determine the notification date and time based on the schedule message (S1420).

[0145] The processor may then display the schedule message in the schedule notification area at the determined notification date and time (S1430). According to one embodiment, the processor may identify a schedule type included in the schedule message and display graphic information related to the identified schedule type together with at least a portion of the schedule message in the schedule notification area. A plurality of schedule messages corresponding to different schedule types may be displayed in the schedule notification area.

[0146] The processor may also calculate the time remaining until the schedule start date / time or the schedule end date / time included in the schedule message, and if it determines that the calculated remaining time falls within a first range, it may visualize the schedule message using a first graphic element. If it determines that the calculated remaining time falls within a second range, it may visualize the schedule message using a second graphic element.

[0147] According to one embodiment, when a destination included in a schedule message is identified, the processor can calculate an expected travel time to the destination based on the user's transportation means or travel speed, the user's current location, and the destination, and display the calculated expected travel time in the schedule notification area together with at least a portion of the schedule message. Thereafter, the processor can determine whether the user has arrived at the destination, and in response to determining that the user has arrived at the destination, remove the schedule message from the schedule notification area.

[0148] According to one embodiment, when the destination and participants included in the schedule message are identified, the processor can acquire the user's current location and the participants' current locations. The processor can then calculate a first estimated time it will take for the user to reach the destination based on the user's transportation means or travel speed, the user's current location, and the destination, and calculate a second estimated time it will take for the participants to reach the destination based on the participants' transportation means or travel speed, the participants' current locations, and the destination. The processor can also display the first estimated time and the second estimated time in a schedule notification area together with at least a portion of the schedule message.

[0149] The processor may also display a third graphic element associated with the destination in the schedule notification area, a fourth graphic element associated with the user based on the first expected travel time in the schedule notification area, and a fifth graphic element associated with the participants based on the second expected travel time in the schedule notification area. In this case, the distance between the third and fourth graphic elements may be determined based on the first expected travel time. The distance between the third and fifth graphic elements may be determined based on the second expected travel time.

[0150] According to one embodiment, the processor can determine whether the user and all participants have arrived at the destination, and can remove the schedule message from the schedule notification area in response to determining that the user and all participants have arrived at the destination.

[0151] After a schedule message is displayed in the schedule notification area, the processor may receive a first user input selecting the schedule message displayed in the schedule notification area. In this case, the processor may execute an online conference link included in the schedule message in response to receiving the first user input. At this time, an online conference application associated with the schedule message may be executed in response to the execution of the online conference link. According to one embodiment, when executing the online conference link included in the schedule message, the processor may determine whether there are multiple conferences currently available to attend based on at least one stored schedule message. In response to determining that there are multiple conferences currently available to attend, the processor may display a list of available conferences, obtain a link related to any conference selected by the user from the displayed conference list, and then execute the obtained link.

[0152] According to one embodiment, after displaying the schedule message in the schedule notification area, the processor may identify the schedule end date and time included in the schedule message and remove the schedule message from the schedule notification area in response to determining that the end date and time has passed. Additionally or alternatively, after displaying the schedule message in the schedule notification area, the processor may remove the schedule message from the schedule notification area when receiving a second user input selecting the schedule message displayed in the schedule notification area.

[0153] According to one embodiment, the processor may obtain an event message including an event area. In this case, the processor may determine whether a user's current location is included in the event area, and, in response to determining that the user's current location is included in the event area, display the event message in the schedule notification area. After the event message is displayed in the schedule notification area, the processor may determine whether the user has left the event area, and, in response to determining that the user has left the event area, remove the event message from the schedule notification area.

[0154] According to an embodiment, when a schedule message is acquired, the processor may display a schedule management message related to managing the schedule message in a conversation list of the instant messaging application, and may display a user interface related to editing the schedule message in response to receiving a third user input selecting the schedule management message.

[0155] The above flowcharts and descriptions are merely examples and may be implemented differently in some embodiments, for example, the order of steps may be changed, some steps may be repeated, some steps may be omitted, or some steps may be added.

[0156] The above-described method may be provided as a computer program stored on a computer-readable recording medium for execution by a computer. The medium may store a computer-executable program or temporarily store it for execution or download. The medium may also be various recording or storage means in the form of a single piece of hardware or multiple pieces of hardware combined together. The medium is not limited to media directly connected to a computer system but may also be distributed over a network. Examples of 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 media configured to store program instructions, including ROM, RAM, and flash memory. Other examples of media include recording or storage media managed by app stores that distribute applications and other sites or servers that provide or distribute various software.

[0157] The methods, operations, or techniques of the present disclosure may be implemented by various means. For example, such techniques may be implemented in hardware, firmware, software, or a combination thereof. Those of ordinary skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the present disclosure may be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, the various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the particular application and design requirements imposed on the overall system. Those of ordinary skill in the art may implement the described functions in various ways for each particular application, but such implementation should not be interpreted as a departure from the scope of the present disclosure.

[0158] In a hardware implementation, the processing units used to perform the techniques may be embodied within one or more ASICs, DSPs, digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, electronic devices, other electronic units designed to perform the functions described in this disclosure, computers, or combinations thereof.

[0159] Thus, the various illustrative logic blocks, modules, and circuits described in connection with this disclosure may be embodied or performed by a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be embodied as a combination of computing devices, e.g., a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other configuration.

[0160] In a firmware and / or software implementation, the techniques may be embodied with instructions stored on a computer-readable medium such as random access memory (RAM), read-only memory (ROM), non-volatile random access memory (NVRAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable PROM (EEPROM), flash memory, compact disc (CD), magnetic or optical data storage device, etc. The instructions may be executable by one or more processors and may cause the processor(s) to perform certain aspects of the functions described in this disclosure.

[0161] If implemented in software, the techniques described above may be stored on or transmitted through a computer-readable medium as one or more instructions or code. Computer-readable media includes any medium that facilitates transfer of a computer program from one place to another, and includes both computer storage media and communication media. Storage media may be any available medium that can be accessed by a computer. By way of non-limiting example, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to transport or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Additionally, any connection may be made appropriately with a computer-readable medium.

[0162] For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, lead wire, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, the coaxial cable, fiber optic cable, lead wire, digital subscriber line, or wireless technologies such as infrared, radio, and microwave are included within the definition of medium. As used herein, "disk" and "disc" include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically, while discs typically reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0163] A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium may be coupled to the processor such that the processor can read information from, and record information on, the storage medium. Alternatively, the storage medium may be integrated into the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. Alternatively, the processor and the storage medium may reside as discrete components in a user terminal.

[0164] While the embodiments described above have been described as utilizing aspects of the presently disclosed subject matter on one or more stand-alone computer systems, the present disclosure is not limited thereto and may be implemented in connection with any computing environment, such as a network or distributed computing environment. Furthermore, aspects of the subject matter in the present disclosure may be implemented on multiple processing chips or devices, and storage may be affected equally across multiple devices. Such devices may include PCs, network servers, and handheld devices.

[0165] Although the present disclosure has been described herein with reference to some embodiments, various modifications and changes that would be understood by those of ordinary skill in the art to which the present disclosure pertains can be made without departing from the scope of the present disclosure, and such modifications and changes should be understood to fall within the scope of the claims appended hereto.

Claims

1. A method for notifying a schedule using an instant messaging application, the method being performed by at least one processor of a user terminal, comprising: acquiring a schedule message generated based on schedule information registered in a schedule application; determining a notification date and time based on the schedule message; and displaying the schedule message in a schedule notification area at the determined notification date and time.

2. the schedule message is generated by an external device converting date information registered in the schedule application into a format related to the instant messaging application; The step of obtaining the schedule message includes: The method of claim 1 , further comprising receiving the schedule message from the external device.

3. The step of obtaining the schedule message includes: acquiring schedule information registered in the schedule application; 2. The schedule notification method according to claim 1, further comprising: generating the schedule message by converting the acquired schedule information into a format related to the instant messaging application.

4. The step of displaying the schedule message in a schedule notification area includes: identifying a schedule type included in the schedule message; and displaying graphic information related to the identified schedule type in the schedule notification area together with at least a portion of the schedule message; The method of claim 1 , wherein the schedule notification area displays a plurality of schedule messages corresponding to different schedule types.

5. After displaying the schedule message in the schedule notification area, receiving a first user input selecting the schedule message displayed in the schedule notification area; and executing the online meeting link included in the schedule message in response to receiving the first user input; 2. The schedule notification method according to claim 1, wherein an online meeting application associated with the schedule message is executed in response to execution of the online meeting link.

6. The step of executing the online meeting link included in the schedule message includes: determining whether there are multiple meetings currently available to attend based on the at least one stored schedule message; displaying a list of attendable conferences in response to determining that there are multiple attendable conferences at the current time; obtaining a link for any conference selected by the user from the displayed conference list; 6. The schedule notification method according to claim 5, further comprising: a step of executing the acquired link.

7. After displaying the schedule message in the schedule notification area, identifying an end date and time of the schedule included in the schedule message; The schedule notification method according to claim 1 , further comprising the step of removing the schedule message from the schedule notification area in response to determining that the end date and time has passed.

8. After displaying the schedule message in the schedule notification area, receiving a second user input selecting the schedule message displayed in the schedule notification area; The method of claim 1 , further comprising: removing the schedule message from the schedule notification area in response to receiving the second user input.

9. The step of displaying the schedule message in a schedule notification area includes: calculating the time remaining until the schedule start date and time or the schedule end date and time included in the schedule message; If it is determined that the calculated remaining time is within a first range, visualizing the schedule message using a first graphic element; 2. The method of claim 1, further comprising: visualizing the schedule message using a second graphic element when it is determined that the calculated remaining time is within a second range.

10. The step of displaying the schedule message in a schedule notification area includes: identifying a destination included in the schedule message; calculating an expected travel time to the destination based on the user's means of transportation or travel speed, the user's current location, and the destination; 2. The schedule notification method according to claim 1, further comprising a step of displaying the calculated estimated required time in the schedule notification area together with at least a part of the schedule message.

11. After displaying the schedule message in the schedule notification area, determining whether the user has reached the destination; The schedule notification method of claim 10 , further comprising: removing the schedule message from the schedule notification area in response to determining that the user has arrived at the destination.

12. The step of displaying the schedule message in a schedule notification area includes: identifying destinations and participants included in said schedule message; obtaining a current location of a user and a current location of the participant; calculating a first estimated time required for the user to arrive at the destination based on the user's means of transportation or travel speed, the user's current location, and the destination; calculating a second expected time it will take for the participant to reach the destination based on the participant's mode of transportation or travel speed, the participant's current location, and the destination; The schedule notification method according to claim 1 , further comprising: displaying the first estimated duration and the second estimated duration in the schedule notification area together with at least a part of the schedule message.

13. The step of displaying the schedule message in a schedule notification area includes: displaying a third graphical element associated with the destination in the schedule notification area; displaying a fourth graphic element associated with the user in the schedule notification area based on the first estimated time required; displaying a fifth graphical element associated with the participant in the schedule notification area based on the second estimated duration; further comprising a distance between the third graphic element and the fourth graphic element is determined based on the first expected time required; The schedule notification method according to claim 12 , wherein the distance between the third graphic element and the fifth graphic element is determined based on the second estimated required time.

14. After displaying the schedule message in the schedule notification area, determining whether the user and all of the participants have arrived at the destination; The schedule notification method according to claim 12 , further comprising the step of removing the schedule message from the schedule notification area in response to determining that the user and all of the participants have arrived at the destination.

15. obtaining an event message including an event area; determining whether a user's current location is included in the event area; The method of claim 1 , further comprising: displaying the event message in the schedule notification area in response to determining that the user's current location is included in the event area.

16. After the step of displaying the event message in the schedule notification area, determining whether the user has left the event area; The schedule notification method of claim 15 , further comprising: removing the event message from the schedule notification area in response to determining that the user has left the event area.

17. 2. The schedule notification method of claim 1, wherein the schedule notification area is included in at least one of a screen area where a conversation list of the instant messaging application is displayed, a home screen area of ​​the instant messaging application, or a screen area where a widget of the user terminal is displayed.

18. When the schedule message is acquired, displaying a schedule management message related to management of the schedule message in a conversation list of the instant messaging application; The method of claim 1 , further comprising: displaying a user interface related to editing the schedule message in response to receiving a third user input selecting the schedule management message.

19. A computer-readable non-transitory recording medium having recorded thereon instructions for causing a computer to execute the schedule notification method according to claim 1.

20. A user terminal, a communication module; Memory and at least one processor coupled to the memory and configured to execute at least one computer-readable program contained in the memory; Including, The at least one program Obtain a schedule message generated based on the schedule information registered in the schedule application, determining a notification date and time based on the schedule message; a user terminal including a command for displaying the schedule message in a schedule notification area at the determined notification date and time;

Images