Electronic device, method, and storage medium for updating screen including notification information

Abstract

This wearable device may comprise: a display; a memory for storing instructions; and at least one processor. The instructions, when executed by the at least one processor individually or collectively, may cause the wearable device to: display, on the display, first notification messages respectively corresponding to first messages received through a first application for messaging, within a user interface (UI) of a second application for notification; receive a second message through the first application while displaying the first notification messages within the UI; identify a user input received in relation to the UI after receiving the second message; and before a second notification message corresponding to the second message within the UI is moved to a reference position within the UI according to the user input, authorize to re-display, within the UI, at least some of the first notification messages, which have been stopped from being displayed, according to the user input.

Description

Electronic device, method, and storage medium for updating a screen containing notification information

[0001] The following descriptions relate to an electronic device, method, and storage medium for updating a screen containing notification information.

[0002] An electronic device may include a wearable device that can be worn by a user. For example, the wearable device may be worn on a body part of the user. For example, the body part may include the user's wrist or finger. For example, the electronic device may display a screen containing notification information on a display. For example, the notification information may include a message.

[0003] The above information may be provided as background art to aid in understanding the present disclosure. No claim or determination is made as to whether any of the above is applicable as prior art related to the present disclosure.

[0004] A wearable device according to embodiments of the present disclosure is provided. The wearable device may include a display. The wearable device may include a memory storing instructions and including one or more storage media. The wearable device may include at least one processor including a processing circuit. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to display, on the display, first notification messages corresponding to first messages received through a first messaging application within a user interface (UI) of a second messaging application. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to receive, through the first application, a second message while displaying the first notification messages within the UI of the second application. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to identify a received scroll input in relation to the UI of the second application after receiving the second message. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to authorize re-displaying within the UI of the second application at least some of the first notification messages whose display was interrupted in response to the scroll input before a second notification message corresponding to the second message moves to a reference position within the UI of the second application in response to the scroll input.

[0005] A wearable device according to embodiments of the present disclosure is provided. The wearable device may include a display. The wearable device may include a memory storing instructions and including one or more storage media. The wearable device may include at least one processor including a processing circuit. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to display, on the display, first notification messages corresponding to first messages received through a first messaging application within a user interface (UI) of a second messaging application. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to receive, through the first messaging application, a second message while displaying the first notification messages within the UI of the second messaging application. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to identify a received scroll input in relation to the UI of the second application after receiving the second message. The instructions, when individually or collectively executed by the at least one processor, may cause the wearable device to re-display at least some of the first notification messages that were interrupted from display in response to the scroll input within the UI of the second application based on receiving another scroll input opposite to the scroll input before a second notification message corresponding to the second message moves to a reference position within the UI of the second application in response to the scroll input.

[0006] FIG. 1 is a block diagram of an electronic device within a network environment according to various embodiments.

[0007] Figure 2 illustrates an exemplary block diagram of a wearable device.

[0008] FIG. 3 illustrates an example of how a wearable device displays a user interface (UI) including a notification message.

[0009] FIG. 4A illustrates an example of a method in which a wearable device displays a UI including first notification messages and then displays a UI including second notification messages.

[0010] FIG. 4b illustrates an example of a method in which a wearable device displays received second notification messages together with first notification messages within a UI before displaying a UI including second notification messages after displaying a UI including first notification messages.

[0011] Figure 5 illustrates an example of an operational flow for how a wearable device displays notification messages within a UI.

[0012] Figure 6a illustrates examples for the first notification view.

[0013] Figure 6b illustrates examples for the second notification view.

[0014] Figure 6c shows examples for the third notification view.

[0015] Figures 7a to 7d illustrate examples of a method for identifying a shortest common supersequence (SCS) using a first message sequence of first notification messages and a second message sequence of second notification messages.

[0016] Figures 8a to 8c illustrate examples of how to provide a pop-up message for a new notification message within a UI.

[0017] FIG. 9 illustrates an example of how a wearable device displays notification messages within a UI and disables display of a notification message that has stopped displaying.

[0018] The terms used in this disclosure are used only to describe specific embodiments and may not be intended to limit the scope of other embodiments. The singular expression may include plural expressions unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as commonly understood by those of ordinary skill in the art described in this disclosure. Terms defined in general dictionaries among the terms used in this disclosure may be interpreted as having the same or similar meaning in the context of the relevant technology, and shall not be interpreted in an idealized or overly formal sense unless explicitly defined in this disclosure. In some cases, even if a term is defined in this disclosure, it cannot be interpreted to exclude embodiments of the present disclosure.

[0019] The various embodiments of the present disclosure described below illustrate a hardware-based approach as an example. However, since the various embodiments of the present disclosure include techniques utilizing both hardware and software, the various embodiments of the present disclosure do not exclude a software-based approach.

[0020] In addition, in the present disclosure, expressions such as "more than" or "less than" may be used to determine whether a specific condition is satisfied or fulfilled, but this is merely a description for expressing an example and does not exclude descriptions such as "more than" or "less than." A condition described as "more than" may be replaced with "more than," a condition described as "less than" may be replaced with "less than," and a condition described as "more than and less than" may be replaced with "more than and less than." In addition, hereinafter, "A" to "B" mean at least one of the elements from A (including A) to B (including B). hereinafter, "C" and / or "D" mean at least one of "C" or "D," that is, including {"C", "D", "C" and "D"}. hereinafter, the meaning of "about E" may be replaced with a value within a margin of error of ±5% or ±10% based on E.

[0021] FIG. 1 is a block diagram of an electronic device within a network environment according to various embodiments.

[0022] Referring to FIG. 1, in a network environment (100), an electronic device (101) may communicate with an electronic device (102) via a first network (198) (e.g., a short-range wireless communication network), or may communicate with at least one of an electronic device (104) or a server (108) via a second network (199) (e.g., a long-range wireless communication network). According to one embodiment, the electronic device (101) may communicate with the electronic device (104) via the server (108). According to one embodiment, the electronic device (101) may include a processor (120), a memory (130), an input module (150), an audio output module (155), a display module (160), an audio module (170), a sensor module (176), an interface (177), a connection terminal (178), a haptic module (179), a camera module (180), a power management module (188), a battery (189), a communication module (190), a subscriber identification module (196), or an antenna module (197). In some embodiments, the electronic device (101) may omit at least one of these components (e.g., the connection terminal (178)), or may have one or more other components added. In some embodiments, some of these components (e.g., the sensor module (176), the camera module (180), or the antenna module (197)) may be integrated into one component (e.g., the display module (160)).

[0023] The processor (120) may, for example, execute software (e.g., a program (140)) to control at least one other component (e.g., a hardware or software component) of the electronic device (101) connected to the processor (120) and perform various data processing or calculations. According to one embodiment, as at least a part of the data processing or calculations, the processor (120) may store commands or data received from other components (e.g., a sensor module (176) or a communication module (190)) in a volatile memory (132), process the commands or data stored in the volatile memory (132), and store result data in a non-volatile memory (134). According to one embodiment, the processor (120) may include a main processor (121) (e.g., a central processing unit or an application processor) or a secondary processor (123) (e.g., a graphics processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor)) that can operate independently or together therewith. For example, if the electronic device (101) includes a main processor (121) and a secondary processor (123), the secondary processor (123) may be configured to use less power than the main processor (121) or to be specialized for a specified function. The secondary processor (123) may be implemented separately from the main processor (121) or as a part thereof.

[0024] The auxiliary processor (123) may control at least a portion of functions or states associated with at least one component (e.g., a display module (160), a sensor module (176), or a communication module (190)) of the electronic device (101), for example, on behalf of the main processor (121) while the main processor (121) is in an inactive (e.g., sleep) state, or together with the main processor (121) while the main processor (121) is in an active (e.g., application execution) state. In one embodiment, the auxiliary processor (123) (e.g., an image signal processor or a communication processor) may be implemented as a part of another functionally related component (e.g., a camera module (180) or a communication module (190)). In one embodiment, the auxiliary processor (123) (e.g., a neural network processing unit) may include a hardware structure specialized for processing artificial intelligence models. The artificial intelligence models may be generated through machine learning. This learning can be performed, for example, on the electronic device (101) itself where the artificial intelligence model is executed, or can be performed through a separate server (e.g., server (108)). The learning algorithm can include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but is not limited to the examples described above. The artificial intelligence model can include multiple artificial neural network layers.The artificial neural network may be one of a deep neural network (DNN), a convolutional neural network (CNN), a recurrent neural network (RNN), a restricted Boltzmann machine (RBM), a deep belief network (DBN), a bidirectional recurrent deep neural network (BRDNN), a deep Q-network, or a combination of two or more of the above, but is not limited to the examples described above. In addition to, or alternatively to, a hardware structure, an artificial intelligence model may include a software structure.

[0025] The memory (130) can store various data used by at least one component (e.g., processor (120) or sensor module (176)) of the electronic device (101). The data can include, for example, software (e.g., program (140)) and input data or output data for commands related thereto. The memory (130) can include volatile memory (132) or non-volatile memory (134).

[0026] The program (140) may be stored as software in the memory (130) and may include, for example, an operating system (142), middleware (144), or an application (146).

[0027] The input module (150) can receive commands or data to be used in a component of the electronic device (101) (e.g., a processor (120)) from an external source (e.g., a user) of the electronic device (101). The input module (150) can include, for example, a microphone, a mouse, a keyboard, a key (e.g., a button), or a digital pen (e.g., a stylus pen).

[0028] The audio output module (155) can output audio signals to the outside of the electronic device (101). The audio output module (155) can include, for example, a speaker or a receiver. The speaker can be used for general purposes, such as multimedia playback or recording playback. The receiver can be used to receive incoming calls. In one embodiment, the receiver can be implemented separately from the speaker or as part of the speaker.

[0029] The display module (160) can visually provide information to an external party (e.g., a user) of the electronic device (101). The display module (160) may include, for example, a display, a holographic device, or a projector and a control circuit for controlling the device. In one embodiment, the display module (160) may include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of a force generated by the touch.

[0030] The audio module (170) can convert sound into an electrical signal, or vice versa, convert an electrical signal into sound. According to one embodiment, the audio module (170) can acquire sound through the input module (150), output sound through the sound output module (155), or an external electronic device (e.g., electronic device (102)) (e.g., speaker or headphone) directly or wirelessly connected to the electronic device (101).

[0031] The sensor module (176) can detect the operating status (e.g., power or temperature) of the electronic device (101) or the external environmental status (e.g., user status) and generate an electrical signal or data value corresponding to the detected status. According to one embodiment, the sensor module (176) can include, for example, a gesture sensor, a gyro sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

[0032] The interface (177) may support one or more designated protocols that may be used to directly or wirelessly connect the electronic device (101) with an external electronic device (e.g., the electronic device (102)). In one embodiment, the interface (177) may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.

[0033] The connection terminal (178) may include a connector through which the electronic device (101) may be physically connected to an external electronic device (e.g., electronic device (102)). According to one embodiment, the connection terminal (178) may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

[0034] A haptic module (179) can convert electrical signals into mechanical stimuli (e.g., vibration or movement) or electrical stimuli that a user can perceive through tactile or kinesthetic sensations. In one embodiment, the haptic module (179) can include, for example, a motor, a piezoelectric element, or an electrical stimulation device.

[0035] The camera module (180) can capture still images and videos. According to one embodiment, the camera module (180) may include one or more lenses, image sensors, image signal processors, or flashes.

[0036] The power management module (188) can manage power supplied to the electronic device (101). According to one embodiment, the power management module (188) can be implemented, for example, as at least a part of a power management integrated circuit (PMIC).

[0037] A battery (189) may power at least one component of the electronic device (101). In one embodiment, the battery (189) may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0038] The communication module (190) may support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device (101) and an external electronic device (e.g., electronic device (102), electronic device (104), or server (108)), and the performance of communication through the established communication channel. The communication module (190) may operate independently from the processor (120) (e.g., application processor) and may include one or more communication processors that support direct (e.g., wired) communication or wireless communication. According to one embodiment, the communication module (190) may include a wireless communication module (192) (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module (194) (e.g., a local area network (LAN) communication module, or a power line communication module). Among these communication modules, the corresponding communication module can communicate with an external electronic device (104) via a first network (198) (e.g., a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) or a second network (199) (e.g., a long-range communication network such as a legacy cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or WAN)). These various types of communication modules can be integrated into a single component (e.g., a single chip) or implemented as multiple separate components (e.g., multiple chips). The wireless communication module (192) can verify or authenticate the electronic device (101) within a communication network such as the first network (198) or the second network (199) by using subscriber information (e.g., an international mobile subscriber identity (IMSI)) stored in the subscriber identification module (196).

[0039] The wireless communication module (192) can support 5G networks and next-generation communication technologies following the 4G network, such as NR access technology (new radio access technology). The NR access technology can support high-speed transmission of high-capacity data (eMBB (enhanced mobile broadband)), minimization of terminal power and connection of multiple terminals (mMTC (massive machine type communications)), or high reliability and low latency (URLLC (ultra-reliable and low-latency communications)). The wireless communication module (192) can support, for example, a high-frequency band (e.g., mmWave band) to achieve a high data transmission rate. The wireless communication module (192) can support various technologies for securing performance in a high-frequency band, such as beamforming, massive multiple-input and multiple-output (MIMO), full dimensional MIMO (FD-MIMO), array antenna, analog beam-forming, or large scale antenna. The wireless communication module (192) can support various requirements specified in the electronic device (101), an external electronic device (e.g., the electronic device (104)), or a network system (e.g., the second network (199)). According to one embodiment, the wireless communication module (192) can support a peak data rate (e.g., 20 Gbps or more) for eMBB realization, a loss coverage (e.g., 164 dB or less) for mMTC realization, or a U-plane latency (e.g., 0.5 ms or less for downlink (DL) and uplink (UL), or 1 ms or less for round trip) for URLLC realization.

[0040] The antenna module (197) can transmit or receive signals or power to or from an external device (e.g., an external electronic device). In one embodiment, the antenna module (197) may include an antenna including a radiator formed of a conductor or a conductive pattern formed on a substrate (e.g., a PCB). In one embodiment, the antenna module (197) may include a plurality of antennas (e.g., an array antenna). In this case, at least one antenna suitable for a communication method used in a communication network, such as the first network (198) or the second network (199), may be selected from the plurality of antennas by, for example, the communication module (190). A signal or power may be transmitted or received between the communication module (190) and an external electronic device through the selected at least one antenna. In some embodiments, in addition to the radiator, another component (e.g., a radio frequency integrated circuit (RFIC)) may be additionally formed as a part of the antenna module (197).

[0041] According to various embodiments, the antenna module (197) may form a mmWave antenna module. According to one embodiment, the mmWave antenna module may include a printed circuit board, an RFIC disposed on or adjacent a first side (e.g., a bottom side) of the printed circuit board and capable of supporting a designated high-frequency band (e.g., a mmWave band), and a plurality of antennas (e.g., an array antenna) disposed on or adjacent a second side (e.g., a top side or a side side) of the printed circuit board and capable of transmitting or receiving signals in the designated high-frequency band.

[0042] At least some of the above components can be interconnected and exchange signals (e.g., commands or data) with each other via a communication method between peripheral devices (e.g., a bus, GPIO (general purpose input and output), SPI (serial peripheral interface), or MIPI (mobile industry processor interface)).

[0043] According to one embodiment, commands or data may be transmitted or received between the electronic device (101) and an external electronic device (104) via a server (108) connected to a second network (199). Each of the external electronic devices (102 or 104) may be the same or a different type of device as the electronic device (101). According to one embodiment, all or part of the operations executed in the electronic device (101) may be executed in one or more of the external electronic devices (102, 104, or 108). For example, when the electronic device (101) is to perform a certain function or service automatically or in response to a request from a user or another device, the electronic device (101) may, instead of or in addition to executing the function or service itself, request one or more external electronic devices to perform the function or at least a part of the service. One or more external electronic devices that receive the request may execute at least a portion of the requested function or service, or an additional function or service related to the request, and transmit the result of the execution to the electronic device (101). The electronic device (101) may process the result as is or additionally and provide it as at least a portion of a response to the request. For this purpose, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used, for example. The electronic device (101) may provide an ultra-low latency service by using distributed computing or mobile edge computing, for example. In another embodiment, the external electronic device (104) may include an Internet of Things (IoT) device. The server (108) may be an intelligent server utilizing machine learning and / or a neural network. According to one embodiment, the external electronic device (104) or the server (108) may be included in the second network (199).The electronic device (101) can be applied to intelligent services (e.g., smart home, smart city, smart car, or healthcare) based on 5G communication technology and IoT-related technology.

[0044] Figure 2 illustrates an exemplary block diagram of a wearable device.

[0045] FIG. 2 illustrates an exemplary block diagram of a wearable device (103). For example, the wearable device (103) of FIG. 2 may be connected to the electronic device (101) of FIG. 1. For example, the wearable device (103) may be an example of the electronic device (102) of FIG. 1. For example, the wearable device (103) may be worn on a part of the user's body. For example, the part may include a wrist part. For example, the wearable device (103) may have a watch shape. For example, the wearable device (103) may be referred to as a watch or a smart watch. However, the present disclosure is not limited thereto. For example, the wearable device (103) may include a wearable device that may be worn on another part of the user's body.

[0046] Referring to FIG. 2, the wearable device (103) may be connected to the electronic device (101) based on a wired network and / or a wireless network. For example, the wired network may include a network such as the Internet, a local area network (LAN), a wide area network (WAN), or a combination thereof. For example, the wireless network may include a network such as long term evolution (LTE), 5g new radio (NR), wireless fidelity (WiFi), Zigbee, near field communication (NFC), Bluetooth, Bluetooth low-energy (BLE), or a combination thereof. The wearable device (103) may be directly connected to the electronic device (101), or may be indirectly connected via one or more routers and / or access points (APs).

[0047] Referring to FIG. 2, according to one embodiment, a wearable device (103) may include a processor (210), a display (220), a communication circuit (230), and a memory (240). However, the embodiments of the present disclosure are not limited thereto. For example, the processor (210), the display (220), the communication circuit (230), and the memory (240) may be electrically and / or operably coupled with each other by a communication bus. Hereinafter, the hardware components being operably coupled may mean that a direct connection or an indirect connection is established between the hardware components, either wired or wireless, such that a second hardware component is controlled by a first hardware component among the hardware components. Although illustrated based on different blocks, the embodiment is not limited thereto, and some of the hardware components illustrated in FIG. 2 (e.g., at least a portion of the processor (210) and the communication circuit (230)) may be included in a single integrated circuit such as a system on a chip (SoC) or a system in package (SIP). The type and / or number of hardware components included in the wearable device (103) is not limited to those illustrated in FIG. 2. For example, the wearable device (103) may include only some of the hardware components illustrated in FIG. 2.

[0048] According to one embodiment, the processor (210) of the wearable device (103) may include a hardware component for processing data based on one or more instructions. The hardware component for processing data may include, for example, an arithmetic and logic unit (ALU), a floating point unit (FPU), and a field programmable gate array (FPGA). As an example, the hardware component for processing data may include a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processing (DSP), a microcontroller (MCU), and / or a neural processing unit (NPU). The number of processors (210) may be one or more. For example, the processor (210) may have a multi-core processor structure such as a dual core, a quad core, or a hexa core. The processor (210) of FIG. 2 may be substantially identical to the content of the processor (120) of FIG. 1.

[0049] For example, the processor (210) may include various processing circuits and / or multiple processors. For example, the term "processor" as used herein, including in the claims, may include various processing circuits including at least one processor, one or more of which may be configured to individually and / or collectively perform the various functions described below in a distributed manner. As used herein, when "processor," "at least one processor," and "one or more processors" are described as being configured to perform various functions, these terms encompass, for example, and without limitation, situations where one processor performs some of the recited functions and other processor(s) perform other parts of the recited functions, and also situations where one processor may perform all of the recited functions. Additionally, the at least one processor may include a combination of processors that perform the various functions enumerated / disclosed, for example, in a distributed manner. At least one processor may execute program instructions to achieve or perform the various functions.

[0050] According to one embodiment, the display (220) of the wearable device (103) can output visualized information to a user of the wearable device (103). For example, the display (220) can be controlled by a processor (210) including circuits such as a CPU, a GPU (graphic processing unit), and / or a DPU (display processing unit) to output visualized information to the user. The display (220) can include a flexible display, a flat panel display (FPD), and / or electronic paper. The display (220) can include a liquid crystal display (LCD), a plasma display panel (PDP), and / or one or more light emitting diodes (LEDs). The LEDs can include organic LEDs (OLEDs). The embodiment is not limited thereto, and for example, if the wearable device (103) includes a lens for transmitting external light (or ambient light), the display (220) may include a projector (or projection assembly) for projecting light onto the lens. In one embodiment, the display (220) may be referred to as a display panel and / or a display module. The display (220) of FIG. 2 may be substantially identically applied to the display module (160) of FIG. 1.

[0051] According to one embodiment, the communication circuit (230) of the wearable device (103) may include hardware for supporting transmission and / or reception of electrical signals between the first wearable device (103) and the wearable device (103), and between the second wearable device (105) and the wearable device (103). The communication circuit (230) may include, for example, at least one of a modem, an antenna, and an optical / electronic (O / E) converter. The communication circuit (230) may support transmission and / or reception of electrical signals based on various types of communication means, such as Ethernet, Bluetooth, Bluetooth low energy (BLE), ZigBee, long term evolution (LTE), and 5G new radio (NR). Specific details regarding the communication circuit (230) of FIG. 2 can be applied substantially identically to the communication module (190) and / or antenna module (197) of FIG. 1.

[0052] According to one embodiment, the memory (240) of the wearable device (103) may include a hardware component for storing data and / or instructions input to and / or output from the processor (210). The memory may include, for example, a volatile memory such as a random-access memory (RAM), and / or a non-volatile memory such as a read-only memory (ROM). The volatile memory may include, for example, at least one of a dynamic RAM (DRAM), a static RAM (SRAM), a cache RAM, and a pseudo SRAM (PSRAM). The non-volatile memory may include, for example, at least one of a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), a flash memory, a hard disk, a compact disc, and an embedded multimedia card (eMMC). The specific details of the memory (240) of Fig. 2 can be applied substantially identically to the details of the memory (130) of Fig. 1.

[0053] According to one embodiment, one or more instructions (or commands) representing operations and / or actions to be performed on data by the processor (210) of the wearable device (103) may be stored in the memory (240) of the wearable device (103). A set of one or more instructions may be referred to as a program, firmware, an operating system, a process, a routine, a sub-routine, and / or an application. Hereinafter, when an application is installed in an electronic device (e.g., a wearable device (103)), it may mean that one or more instructions provided in the form of an application are stored in the memory (240), and that the one or more applications are stored in a format executable by the processor of the electronic device (e.g., a file having an extension designated by the operating system of the wearable device (103)). According to one embodiment, the wearable device (103) may perform the operations of FIG. 5 by executing one or more instructions stored in the memory (240). For example, the one or more instructions, when executed by the processor (210), may cause the wearable device (103) to perform at least some of the operations of FIG. 5.

[0054] Referring to FIG. 2, programs installed in the wearable device (103) may be included in any one of different layers, including the application layer (250), the framework layer (260), and / or the hardware abstraction layer (HAL) (270), based on the target. For example, programs (e.g., modules or drivers) designed to target the hardware (e.g., the display (220)) of the wearable device (103) may be included in the hardware abstraction layer (270). The framework layer (260) may be referred to as a notification framework layer from the perspective of including one or more programs for providing notification information (or notification messages) generated using notification data acquired from the application layer (250). For example, the layers illustrated in FIG. 2 may be logically (or for convenience of explanation) separated, and may not mean that the address space of the memory (240) is separated by the layers.

[0055] For example, a program designed to target users of the wearable device (103) may be included within the application layer (250). Examples of programs included in the application layer (250) include a first application (251) for messaging, a third application (253) for messaging, and / or a second application (252) for notifications, but the embodiment is not limited thereto. For example, the first application (251) for messaging and the third application (253) for messaging may be examples of applications for message services. For example, the first application (251) for messaging may be referred to as a messenger application or a message application. For example, the second application (252) for notifications may be at least a part of an application for displaying a home screen (or a home screen application). For example, the second application (283) may be an example of a system user interface (UI) of a home screen application. For example, the second application (252) may be referred to as a home screen application or a notification application. Specific details regarding the second application (252) are described below in FIG. 3. For example, programs (e.g., software applications) included in the application layer (250) may call an API to cause the execution of functions supported by programs included in the framework layer (260).

[0056] For example, the framework layer (260) may include programs designed to target at least one of the hardware abstraction layer (270) and / or the application layer (250). For example, the framework layer (260) may use data received from a first application (251) for messaging to generate (or update, change, or provide) a notification message to be displayed within the UI of a second application (252) for notification, a screen including the notification message, or the UI including the notification message. For example, the data received from the first application (251) may be referred to as notification data, a message, or message data. For example, the data (or notification data, message, or message data) may be used to generate the notification message. For example, the data may include identification information defined by the first application (251), text indicating the contents of the message, and the time at which the message was received. For example, the identification information may be used to indicate the user (or chat room) who sent the message, and may be defined by the first application (251). For example, the identification information may be defined using the ID (identifier) ​​of the user who sent the message within the first application (251) and a key based on the ID. For example, the time at which the message was received may indicate the time at which the message sent from the user was received by the first application (251) (or the server of the first application (251). However, the present disclosure is not limited thereto. For example, the data may include the text indicating the identification information and the content of the message.

[0057] For example, programs included in the framework layer (260) may provide an API (application programming interface) that can be executed (or invoked or called) based on other programs.

[0058] Specific details on a method for providing a notification message generated using notification data (or message) provided from a first application for messaging (251) (or an application for messaging (253)) through a second application for messaging (252) are exemplified and described below with reference to FIG. 3.

[0059] Hereinafter, the present disclosure describes a method performed by the wearable device (103) of FIG. 2, but the present disclosure is not limited thereto. For example, the present disclosure may be applied not to the wearable device (103) as a secondary device, but also to an electronic device as a primary device. For example, the present disclosure may be applied to the UI of the second application (252) for notifications, but not to the UI of the first application (251) for messaging of the electronic device. As a non-limiting example, the present disclosure may also be applied to a situation where the size of the display (220) is small, the displayable area (or display area) of the display (220) is small, or the displayable area of ​​the display (220) is limited (e.g., a split screen).

[0060] FIG. 3 illustrates an example of how a wearable device displays a user interface (UI) including a notification message.

[0061] FIG. 3 illustrates states (301, 302, 303) of how the wearable device (103) of FIG. 2 displays a UI (330) including a notification message on the display (220). For example, the UI (330) may be an example of the UI of the second application (252) for notification of FIG. 2.

[0062] Referring to state (301), the wearable device (103) can display a screen (310) including a watch face on the display (220). For example, the screen (310) including the watch face can be referred to as a home screen. For example, the watch face of the screen (310) can be set within a home screen application. For example, while the wearable device (103) displays the screen (310) including the watch face, it can receive (or acquire) an input (315) with respect to the screen (310). For example, the input (315) can include a swipe input. For example, the input (315) can include a touch input to a designated location on the screen (310) and a drag input in a designated direction that is continuous from the touch input. For example, the designated location may include a left portion of the screen (310), and the designated direction may include a direction from the left portion to the right portion. However, the present disclosure is not limited thereto. For example, the location may include an upper portion of the screen (310), and the designated direction may include a direction from the upper portion to the lower portion. According to one embodiment, the wearable device (103) may display an image (313) (e.g., an icon) indicating the receipt of a notification on a designated area of ​​the screen (310) including a watch face. For example, the wearable device (103) may display the image (313) (or icon) within a right area (or an area in the 9 o'clock direction) of the screen (310) when the notification is received. For example, the image (313) may have a shape of a dot (or circle) of a specific color (e.g., red or orange). For example, the wearable device (103) can receive (or acquire) an input (315) for an image (313).

[0063] Referring to state (302), the wearable device (103) may display a UI (320) of a second application (252) for notification from the screen (310) on the display (220) based on identifying the received input (315). For example, the UI (320) may be a UI for notifying that there is a notification message corresponding to notification data received from the first application (251) (e.g., Messenger A). For example, the UI (320) may be an example of the UI of the second application (252). For example, the UI (320) may be referred to as a detail view of the second application (252), or a notification detail view. For example, the wearable device (103) may receive a user input (325) for the UI (320). For example, the input (325) may include a touch input at any location of the UI (320). In FIG. 3, the UI (320) is displayed from the screen (310) based on the wearable device (103) identifying the input (315), but the present disclosure is not limited thereto. For example, the wearable device (103) may also display the UI (330) from the screen (310) based on the identification of the input (315).

[0064] Referring to state (303), the wearable device (103) may display a UI (330) changed from the UI (320) of the second application (252) on the display (220) based on identifying the input (325) (or based on identifying the input (315)). For example, the UI (330) may be a UI for displaying a notification message for notification data received from the first application (251). For example, the UI (330) may be an example of the UI of the second application (252). For example, the UI (330) may be referred to as a notification view or a thread view of the second application (252). For example, the thread view may be an example of the detail view for displaying a messaging-style notification (or message thread) among the extended notification styles.

[0065] For example, the UI (330) may include a plurality of notification messages (331, 332, 333). In state (303) of FIG. 3, the UI (330) is illustrated as including three notification messages, but the present disclosure is not limited thereto. For example, the UI (330) may include two or fewer notification messages, or may include four or more notification messages. If four or more notification messages are included, the wearable device (103) may authorize display of the four or more notification messages within the UI (330). For example, the wearable device (103) may display at least some of the four or more notification messages on the display (220), and may not display the remaining some of the notification messages within the UI (330) on the display (220). For example, some of the remaining information may not currently be displayed on the display (220) but may be displayed on the display (220) in response to a user input (e.g., a scroll input, a swipe input, a flick input, a touch input, a hovering input). In the present disclosure, authorizing displaying may include currently displaying on the display (220) or not currently displayed on the display (220) but may be displayed on the display (220) in response to a user input (e.g., a scroll input, a swipe input, a flick input, a touch input, a hovering input). For example, each of the notification messages (331, 332, 333) may be referred to as a bubble, a chat bubble, a message bubble, or a conversation object.

[0066] For example, a first notification message (331) of the UI (330) may include text (331a) (e.g., "Hello") indicating a first message corresponding to the first notification message (331), text (331b) (e.g., "Friend A") indicating identification information of the user who sent the first message, and text (331c) (e.g., 11:01) indicating the time at which the first message was received. The identification information of the user who sent the first message may include identification information used to define the user within the first application (251). For example, the identification information may be defined for a specific user, defined for a specific conversation (or chat room), or defined for specific notification data. For example, messages (or notification data) that include different messages sent by the same user may include the same identification information.

[0067] In state (303) of FIG. 3, the first notification message (331) is illustrated as including text (331a) indicating a first message corresponding to the first notification message (331) (e.g., "Hello"), text (331b) indicating identification information of the user who sent the first message (e.g., "Friend A"), and text (331c) indicating the time at which the first message was received, but the present disclosure is not limited thereto. For example, the first notification message (331) may include text (331a) and text (331b) among text (331a), text (331b), and text (331c). Hereinafter, for convenience of explanation, the first notification message (331) is described as including text (331a), text (331b), and text (331c), but the present disclosure is not limited thereto. For example, the first notification message (331) may refer to text (331a) indicating a first message corresponding to the first notification message (331).

[0068] Referring to state (303), UI (330) may include a first notification message (331) indicating "hello," a second notification message (332) indicating "good morning," and a third notification message (333) indicating "what are you doing today?" For example, the second notification message (332) may include text indicating the same time (e.g., 11:01) as the first notification message (331). In state (303) of FIG. 3, even when the second notification message (332) indicates the same time as the first notification message (331), a case is illustrated in which the second notification message (332) including text indicating the time (e.g., 11:01) is displayed, but the present disclosure is not limited thereto. For example, if the second notification message (332) and the first notification message (331) indicate the same time, the text indicating the time may not be included in the second notification message (332) (or the first notification message (331)). In other words, the text indicating the time may not be displayed within the second notification message (332) (or the first notification message (331)).

[0069] For example, the third notification message (333) may include text indicating a different time (e.g., 11:02) than the first notification message (331). In state (303), the second notification message (332) and the first notification message (331) are shown as being received at the same time (e.g., 11:01), but in reality, the first notification message (331) may be received first and the second notification message (332) may be received later. That is, the notification messages may be distinguished in terms of the times they were received by units smaller than minutes (e.g., seconds or milliseconds).

[0070] Referring to FIG. 3, the wearable device (103) may display a notification message corresponding to the notification data within the UI of the second application (252) by using the notification data provided from the first application (251) rather than displaying a message received within the UI of the first application (251) by executing the first application (251). The first application (251) executed within the wearable device (103) or the electronic device (101) connected to the wearable device (103) may easily provide a history of messages received in the past or currently received. The first application (251) may provide the history by using a list (or metadata) of messages by identification information (or user, chat room), and may update messages received in real time within the UI of the first application (251). However, when specific notification data is received from the first application (251), the wearable device (103) can display notification messages corresponding to the specific notification data within the UI of the second application (252) (e.g., the UI (330) of FIG. 3), and it may be difficult to update notification messages for past messages or notification messages for messages received in real time within the UI of the second application (252). Since the second application (252) generates a notification message using the notification data received from the first application (251), when different notification data is received, it may be difficult to provide (or display) both the previous notification message and the new notification message, but only generate a new notification message using the different notification data.

[0071] Below, FIG. 4a illustrates an example of a method for updating the UI of a second application (252) compared to the UI of a first application (251).

[0072] FIG. 4A illustrates an example of a method in which a wearable device displays a UI including first notification messages and then displays a UI including second notification messages.

[0073] Referring to FIG. 4A, examples of a UI (400) of a first application (251) and examples of UIs (430, 450, 450a) of a second application (252) are illustrated. In FIG. 4A, for convenience of explanation, an example of a UI (400) of a first application (251) running on an electronic device (101) is illustrated, but the present disclosure is not limited thereto. For example, the UI (400) may be a UI of a first application (251) running on a wearable device (103).

[0074] For example, the electronic device (101) may display a UI (400) of a first application (251). For example, the UI (400) may include messages (401, 402, 403, 404). For example, the messages (401, 402, 403, 404) may be messages that have not yet been confirmed. For example, the first message (401) may include text indicating "Hello" and a received time (e.g., 11:01). For example, the second message (402) may include text indicating "Good morning" and a received time (e.g., 11:01). For example, the third message (403) may include text indicating "What are you doing today?" and a received time (e.g., 11:02). For example, the fourth message (404) may include text indicating "Want to go to the amusement park?" and a received time (e.g., 11:02). In addition, for example, the UI (400) may further include a message (405) that was received (or confirmed) in the past in addition to messages (401, 402, 403, 404). Messages (401, 402, 403, 404) and message (405) may be messages sent by the same user (e.g., Friend A). However, the present disclosure is not limited thereto. For example, when there are multiple users in a specific chat room, messages (401, 402, 403, 404) and message (405) may be messages sent by the multiple users.

[0075] For example, a first application (251) may provide first notification data (410) to a framework layer (260). For example, the first application (251) may transmit the first notification data (410) to the framework layer (260) (or the second application (252) for notification) to provide the first notification data (410) as a notification through a second application (252). For example, the first notification data (410) may include a first message (401), a second message (402), and a third message (403). In FIG. 4A, for convenience of explanation, three messages (401, 402, 403) are illustrated as being included in one first notification data (410), but the present disclosure is not limited thereto. For example, the number of messages included in one notification data may be adjusted. For example, the above number may be a natural number greater than or equal to 1.

[0076] For example, the first notification data (410) may include identification information of a user (or chat room) providing messages (401, 402, 403), text content of each of the messages (401, 402, 403) (e.g., Hello, Good morning, What are you doing today), and the time at which each of the messages (401, 402, 403) was received. The time may indicate not only the display unit (e.g., hour and minute) shown in each of the messages (401, 402, 403), but also the unit of the actual received time (e.g., second or millisecond).

[0077] For example, the framework layer (260) may generate first notification messages (431, 432, 433) using the received first notification data (410). For example, generating the first notification messages (431, 432, 433) in the framework layer (260) may include generating an image to be displayed within the UI of the second application (252). For example, the size of the image may be larger than or equal to the size of the area that can be displayed within the UI of the second application (252). For example, the wearable device (103) may output information notifying that the first notification messages (431, 432, 433) are generated as it generates the first notification messages (431, 432, 433). For example, the information may include at least one of visual information (e.g., notification pop-up, LED light), auditory information (e.g., sound), or tactile information (e.g., vibration). For example, when the user of the wearable device (103) recognizes the information, based on providing input (315) (and input (325)) as illustrated in state (301) of FIG. 3, the wearable device (103) may display the UI (430) of the second application (252).

[0078] For example, the wearable device (103) may display first notification messages (431, 432, 433) within the UI (430) of the second application (252). For example, the first notification messages (431, 432, 433) may include a first notification message (431), a second notification message (432), and a third notification message (433). For example, the first notification message (431) may correspond to the first message (401) and include text indicating “hello.” For example, the second notification message (432) may correspond to the second message (402) and include text indicating “good morning.” For example, the third notification message (433) may correspond to the third message (403) and include text indicating “what are you doing today?”

[0079] Again, referring to the UI (400) of the first application (251), the first application (251) may provide the second notification data (420) with a new message, a fourth message (404), added to the framework layer (260). For example, the second notification data (420) may include the new message, the fourth message (404), and the second message (402) and the third message (403) included in the first notification data (410). In FIG. 4A, an example is shown in which the first application (251) generates notification data to include three messages in one notification data and one new message (e.g., the fourth message (404)), but the present disclosure is not limited thereto. For example, a first application (251) may provide first notification data (410) including two messages (e.g., a first message (401) and a second message (402)) and second notification data (420) including two messages (e.g., a third message (403) and a fourth message (404)) to the framework layer (260). In the above example, the first notification data (410) and the second notification data (420) may not overlap with each other.

[0080] For example, the first application (251) may transmit the second notification data (420) to the framework layer (260) (or the second application (252) for notification) to provide the second notification data (420) as a notification through the second application (252). For example, the second notification data (420) may include a second message (402), a third message (403), and a fourth message (404).

[0081] For example, the framework layer (260) may generate second notification messages (432, 433, 434) using the received second notification data (420). For example, generating the second notification messages (432, 433, 434) in the framework layer (260) may include generating an image to be displayed within the UI of the second application (252). For example, the wearable device (103) may output information indicating that the second notification messages (432, 433, 434) are generated as it generates the second notification messages (432, 433, 434). For example, the information may include at least one of visual information (e.g., notification pop-up, LED lighting), auditory information (e.g., sound), or tactile information (e.g., vibration). For example, as the user of the wearable device (103) recognizes the above information, based on providing input (315) (and input (325)) as shown in state (301) of FIG. 3, the wearable device (103) may display the UI (450) of the second application (252). However, the present disclosure is not limited thereto. For example, the wearable device (103) may display the UI (430) and, in response to generating second notification messages (432, 433, 434) according to the second notification data (420), display the UI (450) that is changed (or updated) from the UI (430).

[0082] For example, the wearable device (103) may display second notification messages (432, 433, 434) within the UI (450) of the second application (252). For example, the second notification messages (432, 433, 434) may include a second notification message (432), a third notification message (433), and a fourth notification message (434). For example, the second notification message (432) may correspond to the second message (402) and include text indicating “Good morning.” For example, the third notification message (433) may correspond to the third message (403) and include text indicating “What are you doing today?” For example, the fourth notification message (434) may correspond to the fourth message (404) and include text indicating “Do you want to go to an amusement park?”

[0083] For example, the wearable device (103) may display first notification messages (431, 432, 433) generated for first notification data (410) within the UI (430), and then display second notification messages (432, 433, 434) generated for second notification data (420) within the UI (450) that is changed (or updated) from the UI (430). For example, the wearable device (103) may receive an input (459) with respect to the UI (450). For example, the input (459) may include a scroll input in a first direction (e.g., from top to bottom). For example, the wearable device (103) may display a UI (450a) that is at least partially modified from the UI (450) based on identifying an input (459) received in relation to the UI (450). The UI (450a) may be a UI for displaying another area of ​​the image that has been moved from an area of ​​the image displayed within the UI (450).

[0084] For example, the wearable device (103) may display second notification messages (432, 433, 434) within the UI (450a). Compared to the UI (450), the second notification messages (432, 433, 434) within the UI (450a) may be displayed in a state moved in the first direction. For example, the UI (450a) may include text (458) (e.g., “Today”) above the second notification messages (432, 433, 434) to indicate that it is the last message. For example, the text (458) may be used to indicate that there are no more notification messages that may be displayed within the UI (450a) based on an input (459). For example, text (458) (e.g., “today”) may indicate when the second notification messages (432, 433, 434) (or second notification data (420) corresponding to the second notification messages (432, 433, 434)) were received.

[0085] Compared to the UI (430) displaying the first notification messages (431, 432, 433), the UI (450) (and UI (450a)) may not include the first notification message (431). Since the UI (450) (and UI (450a)) includes the second notification messages (432, 433, 434) generated using the second notification data (420), the first notification message (431) corresponding to the first message (401) that is not included in the second notification data (420) may be excluded from the UI (450) (and UI (450a)). In other words, even if the user performs an input (459) to the UI (450) of the wearable device (103), the user cannot confirm the first notification message (431) within the UI (450) and UI (450a).

[0086] Referring to FIG. 4A, within the UI (400) of the first application (251), not only the newly received first message (401), second message (402), third message (403), and fourth message (404), but also the previously received message (405) may be displayed. Since the first application (251) uses a list of messages (or history information), within the UI (400) of the first application (251), not only the first message (401), second message (402), third message (403), and fourth message (404), but also the previously received message (405) may be displayed or may be authorized to be displayed.

[0087] However, unlike the UI (400) of the first application (251), only the first notification messages (431, 432, 433) of the first notification data (410) may be displayed in the UI (430) of the second application (252) generated using the first notification data (410) provided from the first application (251). In addition, only the second notification messages (432, 433, 434) of the second notification data (420) may be displayed in the UI (450) (and UI (450a)) of the second application (252) generated using the second notification data (420) provided from the first application (251). This may be because the notification data for notification messages to be displayed in the second application (252) for notification does not include the list or update information stored for each identification information (e.g., a specific user or chat room) of the first application (251), and is composed of a message sequence. In other words, the notification data may represent a set of messages (or a message sequence) having an order (or order information). For example, the first notification data (410) may include a first message (401), a second message (402), and a third message (403), and may include an order from the first message (401) to the third message (403).

[0088] Hereinafter, in the present disclosure, in the example of the first notification data (410), the message sequence of the first notification data (410) may be briefly described as <1, 2, 3> (first message (401), second message (402), third message (403)). Similarly, in the example of the second notification data (420), the message sequence of the second notification data (420) may be briefly described as <2, 3, 4>. For example, when specific notification data includes message A, message B, and message C, the message sequence of the specific notification data may be,<A, B, C> It can be briefly described as follows.

[0089] As described above, when the framework layer (260) and / or the second application (252) receives the second notification data (420) while displaying the UI (430) for the first notification data (410) after receiving the first notification data (410), it may be difficult to determine which of the messages of the second notification data (420) are messages added from the first notification data (410) and which are messages maintained from the first notification data (410). Accordingly, the wearable device (103) may display a UI (430) that displays first notification messages (431, 432, 433) corresponding to the first notification data (410) and then display a UI (450) that displays second notification messages (432, 433, 434) corresponding to the second notification data (420), and may not update (or add, change) the UI (430) to include a fourth notification message (434) corresponding to the fourth message (404).

[0090] For example, the wearable device (103) can identify the second notification data (420) changed from the first notification data (410) by using the first message sequence of the first notification data (410) and the second message sequence of the second notification data (420). At this time, the wearable device (103) can use the longest common subsequence (LCS) of the first message sequence and the second message sequence. For specific details related thereto, reference may be made to FIGS. 7A and 7B below. When using the LCS, the wearable device (103) can identify which messages have actually been added and which messages are maintained, even if it is notification data.

[0091] However, even in this case, if the second notification data (420) is received while checking the UI (430) for the first notification data (410) received in the past, the changed UI (450) is displayed from the UI (430). That is, if the user has only checked a part of the UI (430) (e.g., the first notification message (431)), even if the user wants to check the remaining part of the UI (430) (e.g., the second notification message (432) and the third notification message (433)), the changed UI (450) is displayed, making it impossible to check the UI (430). In the example of FIG. 4a, relatively consecutive messages are transmitted as one notification data (e.g., first notification data (410) including a first message (401), a second message (402), and a third message (403), and second notification data (420) including a second message (402), a third message (403), and a fourth message (404), so that the user may not feel much inconvenience. However, when the UI (430) is displayed upon receiving the first notification data (410) including the first message (401), the second message (402), and the third message (403), and the second notification data (420) including the first message (401) and the third message (403) (or the first message (401), the third message (403), and the fourth message (404)) is received as the second message (402) is deleted by the other user, the user may feel inconvenienced by the discontinuous messages. In addition, when the UI (430) is displayed after receiving the first notification data (410) including the first message (401) and the second message (402), and then the second notification data (420) including the third message (403) and the fourth message (404) is received after a long time due to a network problem, the user may feel inconvenienced by the discontinuous messages.The above problem may be due to the fact that the message sequence is discontinuous, containing fragmentary information rather than past history information or update information.

[0092] Hereinafter, the present disclosure can update the UI to include further new notification data while maintaining the previously received notification data while displaying notification messages corresponding to received notification data within the UI. In this case, a hint regarding the new notification data can be provided within the updated UI. For example, the hint can be a pop-up message including text indicating the new notification data. Accordingly, the present disclosure can provide the same user experience as the UI of the first application (251) within the UI of the second application (252) for notification to the user. For specific details related thereto, reference may be made to FIG. 4B below.

[0093] FIG. 4b illustrates an example of a method in which a wearable device displays received second notification messages together with first notification messages within a UI before displaying a UI including second notification messages after displaying a UI including first notification messages.

[0094] Referring to FIG. 4b, examples of a UI (400) of a first application (251) and examples of UIs (430, 440, 440a, 450) of a second application (252) are illustrated. In FIG. 4b, for convenience of explanation, an example of a UI (400) of a first application (251) running on an electronic device (101) is illustrated, but the present disclosure is not limited thereto. For example, the UI (400) may be a UI of a first application (251) running on a wearable device (103).

[0095] For example, the electronic device (101) may display a UI (400) of a first application (251). For example, the UI (400) may include messages (401, 402, 403, 404). For example, the messages (401, 402, 403, 404) may be messages that have not yet been confirmed. For example, the first message (401) may include text indicating "Hello" and a received time (e.g., 11:01). For example, the second message (402) may include text indicating "Good morning" and a received time (e.g., 11:01). For example, the third message (403) may include text indicating "What are you doing today?" and a received time (e.g., 11:02). For example, the fourth message (404) may include text indicating "Want to go to the amusement park?" and a received time (e.g., 11:02). In addition, for example, the UI (400) may further include a previously received (or confirmed) message (405) other than messages (401, 402, 403, 404).

[0096] For example, a first application (251) may provide first notification data (410) to a framework layer (260). For example, the first application (251) may transmit the first notification data (410) to the framework layer (260) (or the second application (252) for notification) to provide the first notification data (410) as a notification through a second application (252). For example, the first notification data (410) may include a first message (401), a second message (402), and a third message (403).

[0097] For example, the wearable device (103) may display first notification messages (431, 432, 433) within the UI (430) of the second application (252). For example, the first notification messages (431, 432, 433) may include a first notification message (431), a second notification message (432), and a third notification message (433). For example, the first notification message (431) may correspond to the first message (401) and include text indicating “hello.” For example, the second notification message (432) may correspond to the second message (402) and include text indicating “good morning.” For example, the third notification message (433) may correspond to the third message (403) and include text indicating “what are you doing today?”

[0098] Again, referring to the UI (400) of the first application (251), the first application (251) may provide the framework layer (260) with the second notification data (420) that adds a new message, the fourth message (404). For example, the second notification data (420) may include the new message, the fourth message (404), and may further include the second message (402) and the third message (403) included in the first notification data (410).

[0099] For example, the framework layer (260) may generate notification messages (431, 432, 433, 434) including both the first notification data (410) and the second notification data (420) by using the first notification data (410) and the received second notification data (420). Among the notification messages (431, 432, 433, 434), in comparison with the first notification data (410), in the second notification data (420), the first notification message (431) may be identified as a deleted message, the second notification message (432) and the third notification message (433) may be identified as maintained messages, and the fourth notification message (434) may be identified as an added message. This can be identified based on the LCS and SCS (shortest common supersequence) between the first message sequence of the first notification data (410) and the second message sequence of the second notification data (420), as described later in FIGS. 7a to 7d.

[0100] For example, the wearable device (103) may display the UI (440) of the second application (252). For example, the UI (440) may be a UI that has been changed (or updated) from the UI (430) as the second notification data (420) is received while the UI (430) including the first notification messages (431, 432, 433) is being displayed. For example, the wearable device (103) may display the UI (440) that has been changed from the UI (430) when the third notification message (433) that is most recently generated among the first notification messages (431, 432, 433) of the UI (430) is positioned below the reference position. In the present disclosure, the most recently generated notification message may be displayed in a state positioned at the bottom among the notification messages of specific notification data, or may indicate a notification message to be displayed. For example, the wearable device (103) may display a UI (450) changed from the UI (430) when the most recently generated third notification message (433) among the first notification messages (431, 432, 433) of the UI (430) is located above the reference position.

[0101] For example, the wearable device (103) may be authorized to display notification messages (431, 432, 433, 434) within the UI (440). For example, the wearable device (103) may display a first notification message (431), a second notification message (432), and a third notification message (433) within the UI (440), and may not display a fourth notification message (434). The fourth notification message (434) may not be displayed within the UI (440) (or its display may be paused), but may be capable of being displayed.

[0102] For example, the wearable device (103) may display a pop-up message (437) within the UI (440) to notify that a fourth notification message (434) has been generated. For example, the pop-up message (437) may float on the UI (440) together with the first notification message (431), the second notification message (432), and the third notification message (433) (or the first notification messages (431, 432, 433)). For example, the pop-up message (437) may include at least a portion of the texts of the fourth notification message (434). For example, the pop-up message (437) may include at least one of identification information, texts, or time of the fourth notification message (434).

[0103] For example, the wearable device (103) can identify a received input (449) with respect to the UI (440). For example, the input (449) can include a scroll input in a second direction (e.g., from bottom to top) opposite to the first direction (e.g., from top to bottom). For example, the wearable device (103) can display a UI (440a) that is at least partially modified from the UI (440) based on identifying the received input (449) while displaying the UI (440). The UI (440a) can be a UI for displaying another area of ​​the image that is moved from an area of ​​the image displayed within the UI (440). For example, the wearable device (103) can display notification messages (431, 432, 433, 434) within the UI (440a). Compared to the UI (440), the notification messages (431, 432, 433, 434) within the UI (440a) may be displayed in a state moved in the second direction. For example, due to limitations in the space that can be displayed on the display (220) of the wearable device (103), the first notification message (431) within the UI (440a) may not be partially displayed. In this case, the wearable device (103) may authorize displaying (or completely displaying) the first notification message (431) based on identifying another scroll input in the first direction opposite to the second direction received in relation to the UI (440a). For example, the wearable device (103) may continue to display a pop-up message (437) to notify that a fourth notification message (434) is generated, even within the UI (440a).

[0104] For example, while displaying the UI (440), the wearable device (103) may identify whether the fourth notification message (434) most recently generated among the notification messages (431, 432, 433, 434) of the UI (440) moves to the reference position based on the received input (449). For example, the wearable device (103) may maintain displaying the UI (440) to the UI (440a) before the fourth notification message (434) moves to the reference position based on the input (449) (or while it is located below the reference position). Alternatively, for example, the wearable device (103) may display a changed UI (450) from the UI (440) (or UI (440a)) when the fourth notification message (434) is moved to the reference position (or positioned above the reference position) according to the input (449). Or, for example, the wearable device (103) may display a changed UI (450) from the UI (440) (or UI (440a)) based on identifying the input received for the pop-up message (437).

[0105] For example, the wearable device (103) may display second notification messages (432, 433, 434) generated for the second notification data (420) within the UI (450). For example, the wearable device (103) may disable displaying the first notification message (431) even if it identifies an input (e.g., another scroll input in the first direction) to the UI (450). In other words, the wearable device (103) may not display the first notification message (431) even if it identifies another scroll input in the first direction to the UI (450). The first notification message (431) may be excluded within the UI (450). This may be because the wearable device (103) displays second notification messages (432, 433, 434) generated for second notification data (420) within the UI (450).

[0106] As described above, when the wearable device (103) receives second notification data (420) while displaying the UI (430) for the first notification data (410), the wearable device (103) may display a UI (440) including both the first notification data (410) and the second notification data (420). At this time, the wearable device (103) may allow displaying both past messages (e.g., the first message (401), the second message (402), and the third message (403)) and currently received messages (e.g., the second message (402), the third message (403), and the fourth message (404)) within the UI (440) displayed on the display (220). At this time, the UI (440) may display a pop-up message (437) (or hint) to notify that a notification message (e.g., the fourth notification message (434)) corresponding to a new message (e.g., the fourth message (404)) has been generated. Thereafter, the wearable device (103) may display a UI (450) for the second notification data (420) when a specific condition is satisfied. Accordingly, the present disclosure may provide a user experience similar to that provided by the first application (251) even within the second application (252) for notification (or the UI of the second application (252)).

[0107] In FIG. 4B, an example is shown in which the second notification data (420) includes three messages (402, 403, 404) and second notification messages (432, 433, 434) corresponding to the second notification data (420) are displayed, but the present disclosure is not limited thereto. For example, the second notification data (420) may include one fourth message (404), and the second notification message (434) corresponding to the second notification data (420) may be displayed within the UI (450). In the above example where the second notification data (420) including the fourth message (404) is received, when the first notification messages (431, 432, 433) corresponding to the first notification data (410) including three messages (401, 402, 403) are displayed, the notification messages (e.g., notification messages (431, 432, 433, 434)) may be displayed within the UI (440). The UI (440) of the above example where the second notification data (420) including the fourth message (404) is received may be substantially the same as the UI (440) illustrated in FIG. 4B.

[0108] Figure 5 illustrates an example of an operational flow for how a wearable device displays notification messages within a UI.

[0109] At least some of the methods of FIG. 5 may be performed by the wearable device (103) of FIG. 2. For example, at least some of the methods may be controlled by the processor (210) of the wearable device (103). In the embodiments described below, the operations may be performed sequentially, but are not necessarily performed sequentially. For example, the order of the operations may be changed, and at least two operations may be performed in parallel.

[0110] Referring to FIG. 5, in operation (510), the wearable device (103) may receive first messages. For example, the wearable device (103) may receive the first messages from a first application (251) for messaging. For example, the first messages may be referred to as first notification data (e.g., first notification data (410) of FIG. 4B).

[0111] For example, the wearable device (103) may generate first notification messages (e.g., first notification messages (431, 432, 433) of FIG. 4B) using the first messages received from the first application (251). For example, the framework layer (260) of the wearable device (103) may generate the first notification messages using the first messages.

[0112] In operation (520), the wearable device (103) may display a first notification view including the first notification messages. For example, the first notification view may be an example of a UI of a second application (252) for notification. For example, the first notification view may be the UI (430) of FIG. 4B. The first notification view may be referred to as a UI, a previous step UI, or a previous screen. For example, the first notification view may include the first notification messages generated using the received first messages (or the first notification data). For a specific example of the first notification view, reference may be made to FIG. 6A.

[0113] Figure 6a illustrates examples for the first notification view.

[0114] Referring to FIG. 6A, states (601, 602) of a first notification view are illustrated, which include first notification messages (611, 612, 613) corresponding to the first messages, respectively, including “Hello,” “Today’s weather,” and “Very good.” The first notification view (610) (and the first notification view (610a)) may be referred to as a UI of a second application (251). For example, the first notification view (610) (and the first notification view (610a)) may be an example of the UI (430) of FIG. 4B.

[0115] For example, the notification message (611) of the first notification messages (611, 612, 613) may correspond to a message indicating "hello" among the first messages. For example, the notification message (612) of the first notification messages (611, 612, 613) may correspond to a message indicating "today's weather" among the first messages. For example, the notification message (613) of the first notification messages (611, 612, 613) may correspond to a message indicating "very good" among the first messages.

[0116] Referring to state (601), the wearable device (103) may authorize displaying the first notification messages (611, 612, 613) within the first notification view (610). For example, the wearable device (103) may display some of the first notification messages (612, 613) within the first notification view (610) on the display (220) and stop displaying (or not displaying) the remaining notification messages (611) within the first notification view (610). In this case, the notification message (611) may be displayed within the first notification view (610) based on an input (619) received in relation to the first notification view (610). However, state (601) is merely an example for convenience of explanation, and the present disclosure is not limited thereto. For example, first notification messages (611, 612, 613) may be displayed within the first notification view (610).

[0117] In state (601), the wearable device (103) can identify an input (619) received in relation to the first notification view (610). For example, the input (619) can include a scroll input in a first direction (e.g., from top to bottom). For example, based on identifying the input (619) received in relation to the first notification view (610), the wearable device (103) can display a first notification view (610a) of state (602) that is at least partially changed from the first notification view (610) of state (601). The first notification view (610a) of state (602) can be a UI for displaying another region of the image that is moved from the region of the image displayed within the first notification view (610) of state (601).

[0118] Referring to state (602), the wearable device (103) may authorize display of the first notification messages (611, 612, 613) within the first notification view (610a). For example, the wearable device (103) may display some of the first notification messages (611, 612, 613) within the first notification view (610a) on the display (220) and stop displaying (or not displaying) the remaining notification messages (613) within the first notification view (610a). In this case, the stopped notification messages (613) may be displayed within the first notification view (610a) by identifying another input received in relation to the first notification view (610a) (e.g., a scroll input in a second direction opposite to the first direction).

[0119] Referring back to FIG. 5, in operation (530), the wearable device (103) may receive a second message. For example, the second message may be referred to as second notification data (e.g., second notification data (420) of FIG. 4b). In FIG. 5, for convenience of explanation, it is assumed that one second message is received, but the present disclosure is not limited thereto. In addition, FIG. 5 assumes that the identification information (e.g., user or chat room) of the received second message is the same as the identification information (e.g., user or chat room) of the first messages. For example, multiple second messages may be received, such as the second alarm data (420) of FIG. 4b. For example, the wearable device (103) may receive the second message while displaying the first notification view including the first alarm messages on the display (220).

[0120] For example, the wearable device (103) can generate a second notification message (e.g., the second notification messages (432, 433, 434) of FIG. 4B) using the second message received from the first application (251). In FIG. 5, it is assumed that the second message is the fourth message (404) of FIG. 4B. Accordingly, the second notification message corresponding to the second message may be the fourth notification message (434) of FIG. 4B. For example, the framework layer (260) of the wearable device (103) can generate the second notification message using the second message.

[0121] In operation (540), the wearable device (103) may identify whether a third notification message among the first notification messages is located below the reference position. For example, the third notification message may be the most recently generated notification message among the first notification messages. In examples (601, 602) of FIG. 6A, the third notification message may be notification message (613) among the first notification messages (611, 612, 613).

[0122] For example, the reference position may indicate a virtual position of the first notification view (or UI) of the second application (252). For example, the reference position may indicate a threshold coordinate for the y-coordinate of the notification view. For example, the wearable device (103) may compare the coordinate value of the specified position of the third notification message with the reference position (or the threshold coordinate). For example, the specified position of the third notification message may include the y-coordinate of the bottom of the third notification message. For example, the bottom may indicate the lowest position among the areas where the time is displayed when the third notification message includes a time (e.g., 11:02) as in the examples (601, 602) of FIG. 6A.

[0123] In operation (540), the wearable device (103) may perform operation (550) if the third notification message among the first notification messages is located below the reference position. Alternatively, in operation (540), the wearable device (103) may perform operation (560) if the third notification message among the first notification messages is located above the reference position (or located above and at the same position as the reference position).

[0124] In operation (550), the wearable device (103) may display a second notification view. For example, if the third notification message is located below the reference position, the wearable device (103) may display the second notification view. The second notification view may be referred to as a UI, an intermediate stage UI, or an intermediate screen. For example, if the third notification message is located below the reference position, the wearable device (103) may, while displaying the first notification view, recognize that the user is checking a part of the first notification view (e.g., the notification message (611) or the notification message (612) of FIG. 6A) and has not yet checked the last part of the first notification view (e.g., the notification message (613)). Accordingly, the wearable device (103) may display the second notification view changed from the first notification view. For example, the second notification view may include first notification messages corresponding to each of the first messages and second notification messages corresponding to the second message. For specific details related thereto, reference may be made to FIG. 6B below.

[0125] Figure 6b illustrates examples for the second notification view.

[0126] Referring to FIG. 6B, examples of second notification views (621, 622) are shown, including first notification messages (611, 612, 613) corresponding to the first messages, including "Hello", "Today's weather", and "So good", and second notification message (614) corresponding to the second message, "So go out and play". The second notification view (620) (and the second notification view (620a)) may be referred to as a UI of the second application (251). For example, the second notification view (620) (and the second notification view (620a)) may be an example of the UI (440) or UI (440a) of FIG. 4B.

[0127] Referring to state (602) of FIG. 6A and state (621) of FIG. 6B, the wearable device (103) can identify that the most recently generated notification message (613) among the first notification messages (611, 612, 613) is located below the reference position (650). In state (602), the notification message (613) is located below the notification message (612), and thus, the display may be stopped in the first notification view (610a) of state (602). Accordingly, the wearable device (103) can change (or update) from the first notification view (610a) to the second notification view (620).

[0128] Referring to state (621), the wearable device (103) may authorize displaying the first notification messages (611, 612, 613) and the second notification message (614) within the second notification view (620). For example, the wearable device (103) may display some of the first notification messages (611, 612, 613) within the second notification view (620) on the display (220), and stop displaying (or not displaying) the remaining notification messages (613) and the second notification message (614) among the first notification messages (611, 612, 613) within the second notification view (620). At this time, the notification message (613) and the second notification message (614) may be displayed within the second notification view (620) according to the input (629) received in relation to the second notification view (620).

[0129] Referring to state (621), the wearable device (103) may display a pop-up message (617) within the second notification view (620) to notify that a second notification message (614) has been generated. For example, the pop-up message (617) may include at least some of the texts of the second notification message (614). In state (621), the pop-up message (617) may float on the second notification view (620) together with some of the first notification messages (611, 612, 613).

[0130] In state (621), the wearable device (103) can identify an input (629) received in relation to the second notification view (620). For example, the input (629) can include a scroll input in a second direction (e.g., from bottom to top). For example, based on identifying the input (629) received in relation to the second notification view (620), the wearable device (103) can display a second notification view (620a) of state (622) that is at least partially changed from the second notification view (620) of state (621). The second notification view (620a) of state (622) can be a UI for displaying another area of ​​the image that has been moved from an area of ​​the image displayed within the second notification view (620) of state (621).

[0131] Referring to state (622), the wearable device (103) may authorize displaying the first notification messages (611, 612, 613) and the second notification message (614) within the second notification view (620a). For example, the wearable device (103) may display some of the first notification messages (611, 612, 613) and the second notification message (614) within the second notification view (620a) on the display (220), and may stop displaying (or not display) the remaining notification message (611) among the first notification messages (611, 612, 613) within the second notification view (620a). Referring to state (622), the wearable device (103) may maintain displaying a pop-up message (617) within the second notification view (620a) to notify that a second notification message (614) has been generated.

[0132] At this time, the notification message (611) whose display has been stopped may be displayed within the second notification view (620a) by identifying another input (e.g., a scroll input in the first direction opposite to the second direction) received in relation to the second notification view (620a). However, the present disclosure is not limited thereto. As illustrated in FIG. 9, in the case of a notification message (611) that is not to be displayed in the third notification view (630) (and the third notification view (630a)) of FIG. 6c, the wearable device (103) may stop displaying the notification message (611) within the second notification view (620a) according to the input (629), thereby disapproving its re-display within the second notification view (620a).

[0133] In state (622), the wearable device (103) can identify an input (639) received in relation to the second notification view (620a). For example, the input (639) can include a scroll input in the second direction (e.g., from bottom to top). For example, the wearable device (103) can identify whether the second notification message (614) moves to the reference position (650) based on identifying the input (639) received in relation to the second notification view (620a). For example, the wearable device (103) may authorize the second notification message (614) to re-display the first notification messages (611, 612, 613) and the second notification message (614), whose display was at least partially interrupted, within the second notification view (620a) before the second notification message (614) moves to the reference location (650) (or is positioned below the reference location (650)) according to the input (639). Alternatively, for example, the wearable device (103) may display the third notification view (630) of FIG. 6c when the second notification message (614) moves to the reference location (650) (or is positioned above the reference location (650)) according to the input (639). Alternatively, for example, the wearable device (103) may display the third notification view (630) of FIG. 6c when it identifies a received input (or touch input) for a pop-up message (617).

[0134] Referring back to FIG. 5, in operation (560), the wearable device (103) may display a third notification view. The third notification view may be referred to as a UI, a next step UI, or a next screen. For example, the wearable device (103) may display the third notification view when the third notification message is positioned above the reference position within the first notification view. Or, for example, the wearable device (103) may display the third notification view when the second notification message moves to the reference position according to a scroll input (e.g., input (629) or input (639) of FIG. 6B) within the second notification view. Or, for example, the wearable device (103) may display the third notification view when it identifies an input (or touch input) for a pop-up message (e.g., pop-up message (617) of FIG. 6B) displayed on the second notification view. For example, the third notification view may include the second notification message corresponding to the second message. For specific details related thereto, reference may be made to FIG. 6c below.

[0135] Figure 6c shows examples for the third notification view.

[0136] Referring to FIG. 6c, examples (641, 642) of a third notification view are illustrated, including a second notification message (614) corresponding to the second message "So, let's go play." The third notification view (630) (and the third notification view (630a)) may be referenced as a UI of the second application (251). For example, the third notification view (630) (and the third notification view (630a)) may be an example of the UI (450) of FIG. 4b.

[0137] Referring to state (641), the wearable device (103) may authorize displaying a second notification message (614) within a third notification view (630). For example, the wearable device (103) may display the second notification message (614) within the third notification view (630) on the display (220).

[0138] In state (641), an input (649) received in relation to a third notification view (630) may be identified. For example, the input (649) may include a scroll input in a first direction (e.g., from top to bottom). For example, the wearable device (103) may display a third notification view (630a) of state (642) that is at least partially changed from the third notification view (630) of state (641) based on identifying the input (639) received in relation to the third notification view (630). The third notification view (630a) of state (642) may be a UI for displaying another area of ​​the image that has been moved from an area of ​​the image displayed within the third notification view (630) of state (641).

[0139] Referring to state (642), the wearable device (103) may disallow displaying the first notification messages (611, 612, 613) again within the third notification view (630a). In other words, the wearable device (103) may stop displaying (or block displaying) the first notification messages (611, 612, 613) when displaying the third notification view (630) (or the third notification view (630a)) that has been changed (or updated) from the second notification view (620) (or the second notification view (620a)).

[0140] Referring to the above-described FIGS. 4B, 5, 6A, 6B, and 6C, the wearable device (103) may first display a first notification view including a first notification message corresponding to received first notification data (or first messages), and receive second notification data (or second messages, second message) while displaying the first notification view including the first notification message. The wearable device (103) may generate a second notification message corresponding to the second notification data, and display a second notification view including the first notification message and the second notification message or a third notification view including the second notification message. Within the second notification view including the first notification message and the second notification message, a message sequence of the first notification data and a message sequence of the second notification data may be used to distinguish added messages, maintained messages, and deleted messages in the second notification message compared to the first notification message. For specific details related to this, reference may be made to FIGS. 7a to 7d below.

[0141] Figures 7a to 7d illustrate examples of a method for identifying a shortest common supersequence (SCS) using a first message sequence of first notification messages and a second message sequence of second notification messages.

[0142] FIG. 7A illustrates examples of a first message sequence (710) of the first notification messages and a second message sequence (720) of the second notification messages. For example, the first message sequence (710) may represent a message sequence representing first notification data for generating the first notification messages. For example, the second message sequence (720) may represent a message sequence representing second notification data for generating the second notification messages.

[0143] Referring to FIG. 7A, the wearable device (103) (or the framework layer (260) of the wearable device (103)) may receive the first notification data including an A message (711), a B message (712), a C message (713), a C message (714), and a D message (715) from the first application (251). For example, the wearable device (103) may identify a first message sequence (710) of the first notification data using the received first notification data. For example, the first message sequence (710) may include an A message (711), a B message (712), a C message (713), a C message (714), and a D message (715). For example, the first message sequence (710) may have the order from A message (711), B message (712), C message (713), C message (714), and D message (715).

[0144] Although not shown in FIG. 7a, the wearable device (103) may be authorized to display the first notification messages generated using the first notification data within the UI of the second application (252).

[0145] For example, while authorizing display of the first notification messages within the UI of the second application (252), the wearable device (103) (or the framework layer (260) of the wearable device (103)) may receive the second notification data including a B message (721), a B message (722), a C message (723), a D message (724), and a D message (725) from the first application (251). For example, the wearable device (103) may identify a second message sequence (720) of the second notification data using the received second notification data. For example, the second message sequence (720) may include a B message (721), a B message (722), a C message (723), a D message (724), and a D message (725). For example, the second message sequence (720) may have the order from B message (721), B message (722), C message (723), D message (724), and D message (725).

[0146] In the above example, the wearable device (103) is described as using the first notification data to identify the first message sequence (710) of the first notification data, displaying the first notification messages within a UI, and then using the first notification data to identify the second message sequence (720) of the second notification data, but the present disclosure is not limited thereto. For example, the wearable device (103) may also identify the first message sequence (710) of the first notification data and the second message sequence (720) of the second notification data upon receiving the second notification data, after displaying the first notification messages within a UI using the first notification data.

[0147] In FIGS. 7A to 7D , for convenience of explanation, the message sequence representing each notification data is illustrated as including five messages, but the present disclosure is not limited thereto. In addition, in FIGS. 7A to 7D , for convenience of explanation, each message sequence is illustrated as including identical messages (e.g., C message (713) and C message (714), or B message (712) and B message (722)), but the present disclosure is not limited thereto. The identical messages may represent messages that appear identical to the user on the display (or within the screen, UI). For example, the identical messages may have identical message identification information, message text (or content), and message reception times. However, in general, even if the portion where the message reception time is displayed is identical in a specific unit (e.g., minutes), the actual reception time of the message is distinguished by another specific unit (e.g., seconds or milliseconds), so it may be rare for identical messages to be generated. In the following, for convenience of explanation, an example is given where the message sequence includes identical messages; however, the following explanations can be applied substantially equally even when the message sequence does not include identical messages.

[0148] For example, the wearable device (103) can identify the longest common subsequence (LCS) and the shortest common supersequence (SCS) between the first message sequence (710) and the second message sequence (720) to distinguish added messages, maintained messages, and deleted messages from the second notification messages compared to the first notification messages.

[0149] For example, the LCS may represent a subsequence having the longest length among the common subsequences among the subsequences of the first message sequence (710) and the subsequences of the second message sequence (720). For example, the subsequences of the first message sequence (710) may be: , ,<A, C> ,<B, C, D> ,<C, C, D> ...may include. For example, the subsequences of the second message sequence (720) may include: ,<C, D> ,<B, C, D> ,<B, B, C, D> ...may include. For example, the common subsequences may include: ,<B, C, D> ...may be included. A method for identifying the LCS may be referred to in the following Figure 7b.

[0150] For example, the SCS may represent a sequence having the shortest length among the sequences, each of which includes a first message sequence (710) and a second message sequence (720) as a subsequence. For example, the SCS may be identified using the LCS. A method of identifying the SCS may be referred to in FIG. 7c below. In the present disclosure, the length of a sequence may represent the number of messages included in the sequence. For example, a subsequence The length of is 1, and the subsequence is<B, C, D> The length of may be 3. For example, the length of the first message sequence (710) may be 5.

[0151] FIG. 7B illustrates an example (730) of a method for identifying an LCS for a first message sequence (710) and a second message sequence (720). The rows of the example (730) represent the first message sequence (710) of the first notification data, and the columns of the example (730) represent the second message sequence (720) of the second notification data. The first row and the first column of the example (730) may both be defined as 0. The area where a row and a column meet is defined as a cell. For example, the area where the first row and the first column meet may be defined as cell #11. For example, the area where the first row and the second column meet may be defined as cell #12.

[0152] For example, the value of each cell may contain three values. For example, each cell may contain the length of the LCS of two sequences (e.g., 0, 1, 2, 3), a referenced subsequence to determine the LCS of the two sequences (e.g., an arrow), and an LCS between the two sequences (e.g., B, BC, BCD). For example, the direction of the arrow pointing to the referenced subsequence may point to the adjacent upper left cell (e.g., ↖) if the values ​​between the two sequences are the same (i.e., the messages are the same). Alternatively, the direction of the arrow pointing to the referenced subsequence may point to the longer cell among the adjacent upper cell and the adjacent left cell (e.g., ←, ↑, or ←↑(same length)) if the values ​​between the two sequences are different (i.e., the messages are different). For convenience of explanation, only one LCS is illustrated in Fig. 7b, but each cell may have multiple LCSs.

[0153] Referring to example (730), cell #22 in the second row and second column can be determined by comparing message A (711) and message B (721). For example, in cell #22, since message A (711) and message B (721) are different from each other, cell #12 and cell #21 can be referenced to determine LCS. Since neither cell #12 nor cell #21 has an LCS defined, the length of the LCS of cell #22 can be 0.

[0154] Referring to example (730), cell #23 (731) in the second row and third column can be determined by comparing B message (712) and B message (721). For example, in cell #23 (731), since B message (712) and B message (721) are identical, LCS can be determined by adding the same message (e.g., B) to the LCS of the adjacent upper left cell #12. Accordingly, the LCS of cell #23 (731) is , and the length of the LCS may be 1. The direction of the arrow indicating the subsequence referenced to determine the LCS of cell #23 (731) may be ↖. For example, in cell #24 (732), since the C message (713) and the B message (721) are different from each other, cell #23 (731) and cell #14 may be referenced to determine the LCS. The LCS of cell #23 (731) having a longer length among cell #23 (731) and cell #14 may be determined as the LCS of cell #24 (732). Accordingly, the LCS of cell #24 (732) is , and the length of the LCS may be 1. The direction of the arrow indicating the subsequence referenced to determine the LCS of cell #24 (732) may be ←. Cell #25 in the second row and fifth column and cell #26 in the second row and sixth column may be determined in the same manner as cell #24 (732).

[0155] Referring to example (730), cell #32 in the third row and second column can be determined by comparing the A message (711) and the B message (722). For example, in cell #32, since the A message (711) and the B message (722) are different from each other, cell #31 and cell #22 can be referenced to determine the LCS of cell #32. Since neither cell #31 nor cell #22 has an LCS defined, the length of the LCS of cell #32 can be 0. Accordingly, the length of the LCS of cell #32 is 0, and the direction of the arrow indicating the subsequence referenced to determine the LCS of cell #32 can be ←↑. Cell #42 in the fourth row and second column, cell #52 in the fifth row and second column, and cell #62 in the sixth row and second column can each be determined in the same manner as cell #32.

[0156] Referring to example (730), cell #34 (733) in the third row and fourth column can be determined by comparing the C message (713) and the B message (722). For example, in cell #34 (733), since the C message (713) and the B message (722) are different from each other, cell #33 and cell #24 (732) can be referenced to determine the LCS of cell #34 (733). LCS of cell #33 (e.g., ) and LCS of cell #24 (732) (e.g. ) are identical to each other, so the LCS of cell #34 (733) is may be. Accordingly, the length of the LCS of cell #34 (733) is 1, and the direction of the arrow indicating the subsequence referenced to determine the LCS of cell #34 (733) may be ←↑.

[0157] Referring to example (730), cell #45 (734) in the 4th row and 5th column can be determined by comparing the C message (714) and the C message (723). For example, in cell #45 (734), since the C message (714) and the C message (723) are the same, the LCS of cell #45 (734) can be determined by adding the same message (e.g., C) to the LCS of the adjacent upper left cell #34 (733). Accordingly, the LCS of cell #45 (734) is<B, C> , and the length of the LCS may be 2. The direction of the arrow indicating the subsequence referenced to determine the LCS of cell #45 (734) may be ↖.

[0158] Referring to example (730), cell #55 (735) in the fifth row and fifth column can be determined by comparing the C message (714) and the D message (724). For example, in cell #55 (735), since the C message (714) and the D message (724) are different from each other, cell #45 (734) and cell #54 can be referenced to determine the LCS of cell #55 (735). LCS of cell #45 (734) (e.g.,<B, C> ) and LCS of cell #54 (e.g.<B, C> ) are identical to each other, so the LCS of cell #55 (735) is<B, C> It can be. Accordingly, the length of the LCS of cell #55 (735) is 2, and the direction of the arrow indicating the subsequence referenced to determine the LCS of cell #55 (735) can be ←↑.

[0159] Referring to example (730), cell #66 (736) in the 6th row and 6th column can be determined by comparing the D message (715) and the D message (725). For example, in cell #66 (736), since the D message (715) and the D message (725) are the same, the LCS of cell #66 (736) can be determined by adding the same message (e.g., D) to the LCS of the adjacent upper left cell #55 (735). Accordingly, the LCS of cell #66 (736) is<B, C, D> , and the length of the LCS may be 3. The direction of the arrow indicating the subsequence referenced to determine the LCS of cell #66 (736) may be ↖.

[0160] In example (730), the LCS between the first message sequence (710) and the second message sequence (720) can be identified as the LCS of the last determined cell #66 (736). For example, the LCS between the first message sequence (710) and the second message sequence (720) has a length of 3.<B, C, D> can be identified as.

[0161] For example, the wearable device (103) may be configured to provide an LCS (e.g.,<B, C, D> ) and the second message sequence (720) (e.g.<B, B, C, D, D> ), by comparing the difference between the first message sequence (710) (e.g.<A, B, C, C, D> ) can identify the added messages (B, D) (or the messages added in the second message sequence (720)). In addition, for example, the wearable device (103) can identify the deleted messages (A, C) in the first message sequence (710) (or the messages excluded from the second message sequence (720)) by comparing the LCS between the first message sequence (710) and the second message sequence (720) with the difference between the second message sequence (720). For example, the wearable device (103) can identify the maintained messages (B, C, D) by using the LCS between the first message sequence (710) and the second message sequence (720).

[0162] In the above example, since the added messages (B, D) contain the same message (B, D) as the maintained messages (B, C, D), the wearable device (103) needs to decide whether to add the added messages below or above the maintained messages within the message sequence (e.g., SCS) that includes both the first message sequence (710) and the second message sequence (720). Similarly, since the deleted messages (A, C) contain the same message (C) as the maintained messages (B, C, D), the wearable device (103) needs to decide whether to delete the above message or the below message among the same messages (C, C) within the message sequence (e.g., SCS) that includes both the first message sequence (710) and the second message sequence (720). In this regard, for specific details on a method for determining an SCS including the first message sequence (710) and the second message sequence (720) from an LCS between the first message sequence (710) and the second message sequence (720), reference may be made to FIG. 7c below.

[0163] FIG. 7c illustrates an example (740) of a method for identifying an SCS using an LCS between a first message sequence (710) and a second message sequence (720) identified in example (730) of FIG. 7b.

[0164] Referring to example (740), the wearable device (103) can determine an SCS including the first message sequence (710) and the second message sequence (720) by determining a path from cell #66 (741) to cell #11, which is identical to cell #66 (736) representing an LCS between the first message sequence (710) and the second message sequence (720) of example (730).

[0165] For example, the wearable device (103) can determine the path by comparing the cell that is the target of the search (hereinafter, search cell) with adjacent cells. For example, if the search cell is cell #66 (741), the wearable device (103) can determine the path by comparing the adjacent upper cell #56 (742), the left cell #65, and the upper left cell #55, respectively. At this time, the path can be identified according to a designated criterion. For example, the designated criterion can be set to sequentially determine whether each cell (or message of each cell) is an added message, a maintained message, or a deleted message. For example, the designated criterion can include the following three sequential steps.

[0166] Among the three steps above, in the first step, the wearable device (103) may determine a message corresponding to a row of the search cell as an added message if there is an upper cell adjacent to the search cell and the length of the upper cell is the same as the length of the search cell. In one example, a tag (or indication, marker) indicating that the message corresponding to the row of the search cell is the added message may be set. Thereafter, the new search cell may be changed to an upper cell adjacent to the search cell (or a previous search cell).

[0167] Among the three steps, in the second step, the wearable device (103) may determine the message of the search cell (or the message corresponding to the row and the message corresponding to the column) as the maintained message if there is an upper left cell adjacent to the search cell, the length of the search cell is longer by 1 than the length of the upper left cell, and the message corresponding to the row of the search cell and the message corresponding to the column of the search cell are the same. In one example, a tag (or an indication, a marker) indicating that the message corresponding to the row of the search cell is the maintained message may be set. Thereafter, the new search cell may be changed to the upper left cell adjacent to the search cell (or the previous search cell).

[0168] Among the three steps above, in the third step, the wearable device (103) may determine a message corresponding to a column of the search cell as a deleted message if there is a cell on the left adjacent to the search cell and the length of the search cell is the same as the length of the cell on the left. In one example, a tag (or indication, marker) indicating that the message corresponding to the column of the search cell is a deleted message may be set. Thereafter, the new search cell may be changed to a cell on the left adjacent to the search cell (or the previous search cell).

[0169] The three steps of the above-mentioned specified criteria may have priorities in the order of the first step, the second step, and the third step. In other words, if both the first step and the second step among the above-mentioned specified criteria are satisfied, the first step may be determined to be satisfied.

[0170] According to the above-mentioned criteria, the SCS of the first message sequence (710) and the second message sequence (720) can be identified using the LCS of example (730).

[0171] Referring to example (740), the first search cell may be cell #66 (741). The wearable device (103) may apply the above-described criteria to cell #66 (741). For cell #66 (741), the wearable device (103) may determine that both the first step and the second step among the above-described criteria are satisfied, but the first step is satisfied in order of priority. Accordingly, the D message (725) corresponding to the 6th row of cell #66 (741) may be determined as an added message. Thereafter, the new search cell may be cell #56 (742).

[0172] Referring to example (740), the wearable device (103) may apply the above-described criteria to cell #56 (742). For cell #56 (742), the wearable device (103) may determine that the second step among the above-described criteria is satisfied. Accordingly, the D message (724) corresponding to the fifth row of cell #56 (742) (or, alternatively, the D message (715) corresponding to the sixth column) may be determined as the maintained message. Thereafter, the new search cell may be cell #45 (743).

[0173] Referring to example (740), the wearable device (103) may apply the above-described criteria to cell #45 (743). For cell #45 (743), the wearable device (103) may determine that the second step among the above-described criteria is satisfied. Accordingly, the C message (723) corresponding to the fourth row of cell #45 (743) (and the C message (714) corresponding to the fifth column) may be determined as a maintained message. Thereafter, the new search cell may be cell #34 (744).

[0174] Referring to example (740), the wearable device (103) may apply the above-described criteria to cell #34 (744). For cell #34 (744), the wearable device (103) may determine that the first step among the above-described criteria is satisfied. Accordingly, the B message (722) corresponding to the third row of cell #34 (744) may be determined as an added message. Thereafter, the new search cell may be cell #24 (745).

[0175] Referring to example (740), the wearable device (103) may apply the above-described criteria to cell #24 (745). For cell #24 (745), the wearable device (103) may determine that the third step among the above-described criteria is satisfied. Accordingly, the C message (713) corresponding to the fourth column of cell #24 (745) may be determined to be a deleted message. Thereafter, the new search cell may be cell #23 (746).

[0176] Referring to example (740), the wearable device (103) may apply the above-described criteria to cell #23 (746). For cell #23 (746), the wearable device (103) may determine that the second step among the above-described criteria is satisfied. Accordingly, the B message (721) corresponding to the second row of cell #23 (746) (and the B message (712) corresponding to the third column) may be determined as a maintained message. Thereafter, the new search cell may be cell #12 (747).

[0177] Referring to example (740), the wearable device (103) may apply the above-described criteria to cell #12 (747). For cell #12 (747), the wearable device (103) may determine that the third step among the above-described criteria is satisfied. Accordingly, the A message (711) corresponding to the second column of cell #12 (747) may be determined as a deleted message. Thereafter, the new search cell may be cell #11. When the new search cell is cell #11, the wearable device (103) may determine the path from cell #66 (741), to cell #56 (742), cell #45 (743), cell #34 (744), cell #24 (745), cell #23 (746), and cell #12 (747).

[0178] The wearable device (103) uses the determined path to determine the SCS between the first message sequence (710) and the second message sequence (720).<A, B, C, B, C, D, D> can be identified. The SCS identified according to the above-mentioned conditions may be a message in which a lower message (right in the sequence) among consecutive identical messages is a deleted message, and a higher message (left in the sequence) among consecutive identical messages is an added message. For example, B on the left side of the SCS is a maintained message, and B on the right side is an added message. D on the left side of the SCS is a maintained message, and D on the right side is an added message. For example, C on the left side of the SCS is a deleted message, and C on the right side is a maintained message. For specific details related thereto, reference may be made to FIG. 7d below.

[0179] FIG. 7d illustrates examples of a first message sequence (710), a second message sequence (720), and an SCS (750). For example, the SCS (750) may include a first message sequence (710) and a second message sequence (720). For example, the first message sequence (710) may include an A message (711), a B message (712), a C message (713), a C message (714), and a D message (715). For example, the second message sequence (720) may include a B message (721), a B message (722), a C message (723), a D message (724), and a D message (725).

[0180] For example, SCS (750) may include A message (711), B message (712), C message (713), B message (722), C message (724), D message (725), and D message (725). To identify SCS (750) using first message sequence (710) and second message sequence (720), examples (750a, 750b, 750c) may be referenced.

[0181] In example (750a), in the first message sequence (710), messages (712, 714, 715) that are LCSs between the first message sequence (710) and the second message sequence (720) can be identified. In the second message sequence (720), messages (721, 723, 724) that are LCSs can be identified. The messages (721, 723, 724) of the second message sequence (720) can be messages that are retained from the messages (712, 714, 715) of the first message sequence (710).

[0182] In example (750b), within the SCS (750) in which the first message sequence (710) and the second message sequence (720) are integrated, messages (722, 725) added in the second message sequence (720) can be identified. For example, among the added messages (722, 725), the B message (722) can be positioned below the B message (712). For example, among the added messages (722, 725), the D message (725) can be positioned below the D message (715).

[0183] In example (750c), within the SCS (750) in which the first message sequence (710) and the second message sequence (720) are integrated, messages (711, 713) deleted from the first message sequence (710) can be identified. For example, among the added messages (711, 713), the C message (713) can be positioned above the C message (714).

[0184] As described above, the wearable device (103) can identify the SCS (750) using the second message sequence (720) of the second notification data received while displaying the first notification messages related to the first message sequence (710) within the UI of the second application (252), and display notification messages based on the SCS (750) within the UI of the second application (252). The notification messages based on the SCS (750) can correspond to each of the A message (711), the B message (712), the C message (713), the B message (722), the C message (724), the D message (725), and the D message (725).

[0185] As in the example of FIG. 7d, if the last message (e.g., D message (725)) among the notification messages based on SCS (750) is an added message, the wearable device (103) may display a pop-up message (e.g., pop-up message (617) of FIG. 6a) for the last message while authorizing the display of the notification messages within the UI of the second application (252) (or while displaying at least some of the notification messages). For example, the pop-up message may be referenced as a hint or accessory for a new notification message. Specific examples related to the display of the pop-up message may refer to FIGS. 8a to 8c.

[0186] Figures 8a to 8c illustrate examples of how to provide a pop-up message for a new notification message within a UI.

[0187] FIGS. 8A to 8C illustrate examples (800, 820, 840) of a method for providing a pop-up message for a new notification message within a UI of a second application (252). The UIs illustrated in the examples (800, 820, 840) may be notification views of the second application (252).

[0188] In examples (800, 820, 840), for convenience of explanation, the messages of the notification data and the notification messages are simplified as A, B, C, D, and E, respectively, but the present disclosure is not limited thereto. For example, each of the notification messages may further include text indicating identification information (e.g., text (313b) of FIG. 3) and text indicating the time of reception (e.g., text (313c) of FIG. 3). In addition, in examples (800, 820, 840), unlike FIGS. 7a to 7d, if the messages (or notification messages) of the previous notification data and the messages (or notification messages) of the new notification data are indicated with the same alphabet, the message is assumed to be a maintained message.

[0189] Referring to state (800) of FIG. 8A, the wearable device (103) may receive first notification data (or first messages) including A, B, and C at a first time point (801), and generate first notification messages (A, B, C) for the first notification data. For example, the wearable device (103) may display the first notification messages (A, B, C) within the UI (811) of the second application (252) on the display (220). For example, the UI (811) may be an example of the first notification view.

[0190] For example, while the wearable device (103) displays the first notification messages (A, B, C) within the UI (811), the wearable device (103) may receive second notification data (or second messages) including B and C at a second time point (802). At this time, the second notification data may be transmitted as a retransmission of B and C among A, B, and C of the first notification data when the user deletes A among A, B, and C of the first notification data within the UI of the first application (251) (e.g., UI (400) of FIG. 4b). Unlike the state (800) illustrated in FIG. 8a, when the user deletes A among A, B, and C of the first notification data within the UI of the first application (251) (e.g., UI (400) of FIG. 4b), the second notification data may include X, B, and C. In other words, the second alarm data may include a message X containing text indicating “This message has been deleted.”

[0191] For example, the wearable device (103) can generate notification messages (A, B, C) based on the SCS by identifying the SCS using the message sequence of the first notification data and the message sequence of the second notification data. At this time, among the notification messages (A, B, C) based on the SCS, the most recently generated C may be a maintained message, not an added message.

[0192] For example, the wearable device (103) may display notification messages (A, B, C) based on the SCS within the UI (812) of the second application (252). For example, the UI (812) may be an example of a second notification view. The wearable device (103) may refrain from displaying a pop-up message (817) within the UI (812) because the last message (or the most recently generated C) among the notification messages (A, B, C) based on the SCS is not an added message.

[0193] For example, the wearable device (103) may display a UI (813) that has been changed (or updated) from the UI (812) at a third time point (803) while displaying the UI (812). For example, the wearable device (103) may display second notification messages (B, C) within the UI (813) of the second application (252). For example, the UI (813) may be displayed when the most recently generated C among the notification messages (A, B, C) based on the SCS is positioned above a reference position (e.g., reference position (650) of FIG. 6B) according to a scroll input within the UI (812). For example, the UI (813) may be an example of a third notification view.

[0194] Referring to state (820) of FIG. 8B, the wearable device (103) may receive first notification data (or first messages) including A, B, and C at a first time point (821), and generate first notification messages (A, B, C) for the first notification data. For example, the wearable device (103) may display the first notification messages (A, B, C) within the UI (831) of the second application (252) on the display (220). For example, the UI (831) may be an example of the first notification view.

[0195] For example, the wearable device (103) may receive second notification data (or second messages) including B, C, and D at a second time point (822) while displaying first notification messages (A, B, C) within the UI (831). For example, the wearable device (103) may identify an SCS using the message sequence of the first notification data and the message sequence of the second notification data, thereby generating notification messages (A, B, C, D) based on the SCS. At this time, among the notification messages (A, B, C, D) based on the SCS, the most recently generated D may be an added message.

[0196] For example, the wearable device (103) may be authorized to display notification messages (A, B, C, D) based on the SCS within the UI (832) of the second application (252). For example, within the UI (832), among the notification messages (A, B, C, D) based on the SCS, the notification messages (A, B, C) may be displayed, and among the notification messages (A, B, C, D) based on the SCS, the notification message (D) may not be displayed. In this case, among the notification messages (A, B, C, D) based on the SCS, the notification message (D) may be displayed according to a scroll input received in relation to the UI (832). For example, the UI (832) may be an example of the second notification view. The wearable device (103) may display a pop-up message (837-1) within the UI (832) as the last message (or the most recently generated D) among the notification messages (A, B, C, D) based on the SCS is an added message.

[0197] For example, the wearable device (103) may receive third notification data (or third messages) including B and C at a third time point (823) while displaying notification messages (A, B, C, D) based on the SCS within the UI (832). At this time, the third notification data may be transmitted as a retransmission of B and C among B, C, D of the second notification data by the user deleting D among B, C, D of the second notification data within the UI of the first application (251) (e.g., UI (400) of FIG. 4b). For example, the wearable device (103) may generate notification messages (A, B, C) based on the additional SCS by identifying the additional SCS using the message sequence of the first notification data and the message sequence of the third notification data. At this time, compared to the first notification messages (A, B, C), the most recently generated C among the notification messages (A, B, C) based on the SCS may be a maintained message, not an added message.

[0198] For example, the wearable device (103) may display notification messages (A, B, C) based on the additional SCS within the UI (833) of the second application (252). For example, the UI (833) may be an example of a second notification view. The wearable device (103) may refrain from displaying a pop-up message (837-2) within the UI (833) because the last message (or the most recently generated C) among the notification messages (A, B, C) based on the additional SCS is a maintained message. At this time, the wearable device (103) may stop displaying the pop-up message (837-1) displayed within the UI (832) and refrain from displaying the pop-up message (837-2) within the UI (833).

[0199] For example, the wearable device (103) may display a UI (834) that has been changed (or updated) from the UI (833) at a fourth time point (824) while displaying the UI (833). For example, the wearable device (103) may display second notification messages (B, C) within the UI (834) of the second application (252). For example, the UI (834) may be displayed when the most recently generated C among the notification messages (A, B, C) based on the additional SCS is positioned above a reference position (e.g., reference position (650) of FIG. 6B) according to a scroll input within the UI (833). For example, the UI (834) may be an example of a third notification view.

[0200] Referring to state (840) of FIG. 8c, the wearable device (103) may receive first notification data (or first messages) including A, B, and C at a first time point (841), and generate first notification messages (A, B, C) for the first notification data. For example, the wearable device (103) may display the first notification messages (A, B, C) within the UI (851) of the second application (252) on the display (220). For example, the UI (851) may be an example of the first notification view.

[0201] For example, the wearable device (103) may receive second notification data (or second messages) including B, C, and D at a second time point (842) while displaying first notification messages (A, B, C) within the UI (851). For example, the wearable device (103) may identify an SCS using the message sequence of the first notification data and the message sequence of the second notification data, thereby generating notification messages (A, B, C, D) based on the SCS. At this time, among the notification messages (A, B, C, D) based on the SCS, the most recently generated D may be an added message.

[0202] For example, the wearable device (103) may be authorized to display notification messages (A, B, C, D) based on the SCS within the UI (852) of the second application (252). For example, within the UI (852), among the notification messages (A, B, C, D) based on the SCS, the notification messages (A, B, C) may be displayed, and among the notification messages (A, B, C, D) based on the SCS, the notification message (D) may not be displayed. In this case, among the notification messages (A, B, C, D) based on the SCS, the notification message (D) may be displayed according to a scroll input received in relation to the UI (852). For example, the UI (852) may be an example of the second notification view. The wearable device (103) may display a pop-up message (857-1) within the UI (852) as the last message (or the most recently generated D) among the notification messages (A, B, C, D) based on the SCS is an added message.

[0203] For example, the wearable device (103) may receive third notification data (or third messages) including C, D, and E at a third time point (843) while displaying notification messages (A, B, C, D) based on the SCS within the UI (852). For example, the wearable device (103) may identify an additional SCS using the message sequence of the first notification data, the message sequence of the second notification data, and the message sequence of the third notification data, thereby generating notification messages (A, B, C, D, E) based on the additional SCS. At this time, the most recently generated E among the notification messages (A, B, C, D, E) based on the additional SCS may be an added message.

[0204] For example, the wearable device (103) may be authorized to display notification messages (A, B, C, D, E) based on the additional SCS within the UI (853) of the second application (252). For example, within the UI (853), among the notification messages (A, B, C, D, E) based on the additional SCS, notification messages (A, B, C) may be displayed, and among the notification messages (A, B, C, D, E) based on the additional SCS, notification messages (D, E) may not be displayed. In this case, among the notification messages (A, B, C, D, E) based on the additional SCS, notification messages (D, E) may be displayed according to a scroll input received in relation to the UI (853). For example, the UI (853) may be an example of a second notification view. The wearable device (103) may display a pop-up message (857-2) within the UI (853) as the last message (or the most recently generated E) among the notification messages (A, B, C, D, E) based on the additional SCS is an added message. At this time, the wearable device (103) may stop displaying the pop-up message (857-1) displayed within the UI (852) and display the pop-up message (857-2) within the UI (853).

[0205] For example, the wearable device (103) may receive fourth notification data (or fourth messages) including C and D at a third time point (844) while displaying notification messages (A, B, C, D, E) based on the SCS within the UI (853). At this time, the fourth notification data may be transmitted as a retransmission of C and D among C, D, E of the third notification data by the user deleting E among C, D, E of the third notification data within the UI of the first application (251) (e.g., UI (400) of FIG. 4b). For example, the wearable device (103) may identify another additional SCS by using the message sequence of the first notification data, the message sequence of the second notification data, and the message sequence of the fourth notification data, thereby generating notification messages (A, B, C, D) based on the other additional SCS. At this time, compared to the first notification messages (A, B, C), the most recently generated D among the notification messages (A, B, C, D) based on the other additional SCS may be an added message.

[0206] For example, the wearable device (103) may be authorized to display notification messages (A, B, C, D) based on the other additional SCS within the UI (854) of the second application (252). For example, within the UI (854), among the notification messages (A, B, C, D) based on the other additional SCS, notification messages (A, B, C) may be displayed, and among the notification messages (A, B, C, D) based on the other additional SCS, notification message (D) may not be displayed. In this case, among the notification messages (A, B, C, D) based on the other additional SCS, notification message (D) may be displayed according to a scroll input received in relation to the UI (854). For example, the UI (854) may be an example of a second notification view. The wearable device (103) may display a pop-up message (857-3) within the UI (854) as the last message (or the most recently generated D) among the notification messages (A, B, C, D) based on the other additional SCS is an added message. At this time, the wearable device (103) may stop displaying the pop-up message (857-2) displayed within the UI (853) and display the pop-up message (857-3) within the UI (854). For example, the pop-up message (857-3) within the UI (854) may be identical to the pop-up message (857-1) within the UI (852).

[0207] For example, the wearable device (103) may display a UI (855) that has been changed (or updated) from the UI (854) at a fifth point in time (845) while displaying the UI (854). For example, the wearable device (103) may display second notification messages (C, D) within the UI (855) of the second application (252). For example, the UI (855) may be displayed when the most recently generated D among the notification messages (A, B, C, D) based on the other additional SCS is positioned above a reference position (e.g., reference position (650) of FIG. 6B) according to a scroll input within the UI (854). Or, for example, the UI (855) may be displayed based on identifying a touch input for a pop-up message (857-3) of the UI (854). For example, UI (855) may be an example of a third notification view.

[0208] FIG. 9 illustrates an example of how a wearable device displays notification messages within a UI and disables display of a notification message that has stopped displaying.

[0209] FIG. 9 illustrates a state (900) of a method for displaying notification messages and disabling display of notification messages whose display has been suspended within a UI of a second application (252). The UIs illustrated in state (900) may be notification views of the second application (252).

[0210] In state (900), for convenience of explanation, the messages of the notification data and the notification messages are simplified as A, B, C, D, and E, respectively, but the present disclosure is not limited thereto. For example, each of the notification messages may further include text indicating identification information (e.g., text (313b) of FIG. 3) and text indicating the time of reception (e.g., text (313c) of FIG. 3). In addition, in state (900), unlike FIGS. 7a to 7d, if the messages (or notification messages) of the previous notification data and the messages (or notification messages) of the new notification data are indicated with the same alphabet, the message is assumed to be a maintained message.

[0211] Referring to state (900), the wearable device (103) may receive first notification data (or first messages) including A, B, and C at a first time point (901), and generate first notification messages (A, B, C) for the first notification data. For example, the wearable device (103) may display the first notification messages (A, B, C) within the UI (911) of the second application (252) on the display (220). For example, the UI (911) may be an example of the first notification view.

[0212] For example, the wearable device (103) may receive second notification data (or second messages) including B, C, and D at a second time point (902) while displaying first notification messages (A, B, C) within the UI (911). For example, the wearable device (103) may identify an SCS using the message sequence of the first notification data and the message sequence of the second notification data, thereby generating notification messages (A, B, C, D) based on the SCS. At this time, among the notification messages (A, B, C, D) based on the SCS, the most recently generated D may be an added message.

[0213] For example, the wearable device (103) may be authorized to display notification messages (A, B, C, D) based on the SCS within the UI (912) of the second application (252). For example, within the UI (912), among the notification messages (A, B, C, D) based on the SCS, the notification messages (A, B, C) may be displayed, and among the notification messages (A, B, C, D) based on the SCS, the notification message (D) may not be displayed. In this case, among the notification messages (A, B, C, D) based on the SCS, the notification message (D) may be displayed according to a scroll input received in relation to the UI (912). For example, the UI (912) may be an example of a second notification view. The wearable device (103) may display a pop-up message (917-1) within the UI (912) as the last message (or the most recently generated D) among the notification messages (A, B, C, D) based on the SCS is an added message.

[0214] For example, the wearable device (103) may receive third notification data (or third messages) including C, D, and E at a third time point (903) while displaying notification messages (A, B, C, D) based on the SCS within the UI (912). For example, the wearable device (103) may identify an additional SCS using the message sequence of the first notification data, the message sequence of the second notification data, and the message sequence of the third notification data, thereby generating notification messages (A, B, C, D, E) based on the additional SCS. At this time, the most recently generated E among the notification messages (A, B, C, D, E) based on the additional SCS may be an added message.

[0215] For example, the wearable device (103) may be authorized to display notification messages (A, B, C, D, E) based on the additional SCS within the UI (913) of the second application (252). For example, the UI (913) may be an example of a second notification view. For example, within the UI (913), among the notification messages (A, B, C, D, E) based on the additional SCS, the notification messages (A, B, C, D) may be displayed, and among the notification messages (A, B, C, D, E) based on the additional SCS, the notification message (E) may not be displayed. In this case, among the notification messages (A, B, C, D, E) based on the additional SCS, the notification message (E) may be displayed according to a scroll input (919-1) received in relation to the UI (913).

[0216] For example, the wearable device (103) may display a UI (913a) that is at least partially changed from the UI (913) based on identifying a scroll input (919-1) in a first direction (e.g., from top to bottom) received in relation to the UI (913). For example, within the UI (913a), among the notification messages (A, B, C, D, E) based on the additional SCS, the notification messages (B, C, D) may be displayed, and among the notification messages (A, B, C, D, E) based on the additional SCS, the notification messages (A, E) may not be displayed. More specifically, according to the scroll input (919-1), the display of the notification message (A) among the notification messages (A, B, C, D, E) based on the additional SCS may be stopped. Within the UI (913a) changed according to the scroll input (919-1), the display of the pop-up message (917-2) can be maintained.

[0217] For example, the wearable device (103) may display a UI (913b) that is at least partially changed from the UI (913a) based on identifying a scroll input (919-2) in a second direction (e.g., from bottom to top) received in relation to the UI (913a). For example, within the UI (913-3), among the notification messages (A, B, C, D, E) based on the additional SCS, the notification messages (B, C, D) may be displayed, and among the notification messages (A, B, C, D, E) based on the additional SCS, the notification messages (A, E) may not be displayed. More specifically, even if the UI (913a) is changed to the UI (913b) according to the scroll input (919-2), the display of the notification message (A) among the notification messages (A, B, C, D, E) based on the additional SCS may not be authorized. The notification message (A) may be a message that will not be displayed (or deleted) in the UI (914) (or the third notification view). Alternatively, based on identifying another scroll input opposite to the scroll input (919-2), the display of the notification message (E) among the notification messages (A, B, C, D, E) based on the additional SCS may be authorized. Within the UI (913b) changed according to the scroll input (919-2), the display of the pop-up message (917-2) may be maintained.

[0218] For example, the wearable device (103) may display a UI (914) that has been changed (or updated) from the UI (919b) at a fourth time point (904) while displaying the UI (919b). For example, the wearable device (103) may display second notification messages (C, D, E) within the UI (914) of the second application (252). For example, the UI (914) may be displayed when the most recently generated E among the notification messages (A, B, C, D, E) based on the other additional SCS is positioned above a reference position (e.g., reference position (650) of FIG. 6b) according to a scroll input within the UI (913b). Or, for example, the UI (914) may be displayed based on identifying a touch input for a pop-up message (917-2) of the UI (913b). For example, UI (914) may be an example of a third notification view.

[0219] In one example, the wearable device (103) may apply visual effects to deleted messages (e.g., A, B) and added messages (e.g., D, E) in the second alarm messages (C, D, E) among the notification messages (A, B, C, D, E) based on the additional SCS. For example, the deleted messages (e.g., A, B) in the UI (913) of the second application (252) may be displayed using the first visual effect (941). As a non-limiting example, the first visual effect (941) may include displaying them in a blurry manner. For example, the first visual effect (941) may be applied to an alarm message that is displayed with a tag indicating that it is a deleted message among the notification messages (A, B, C, D, E) based on the additional SCS.

[0220] For example, an added message (e.g., D, E) in the UI (913) of the second application (252) may be displayed using a second visual effect (942). As a non-limiting example, the second visual effect (942) may include visually highlighting the message. For example, the second visual effect (942) may be applied to an alarm message that is marked with a tag indicating that it is an added message among the notification messages (A, B, C, D, E) based on the additional SCS.

[0221] While the above example describes displaying visual effects within UI (913), the present disclosure is not limited thereto. For example, visual effects may be displayed in each of the second notification views, UI (912), UI (913), UI (913a), and UI (913b).

[0222] Although examples in which previous notification data and new notification data at least partially overlap are illustrated in FIGS. 8A to 9 , the present disclosure is not limited thereto. For example, at a first point in time, first notification data (or first messages) including A, B, and C may be received, and first notification messages (A, B, C) for the first notification data may be generated. For example, the wearable device (103) may display the first notification messages (A, B, C) within the first notification view of the second application (252) on the display (220).

[0223] For example, the wearable device (103) may receive second notification data (or second messages) including D, E, and F at a second time point while displaying first notification messages (A, B, and C) within the first notification view. For example, the wearable device (103) may identify an SCS using the message sequence of the first notification data and the message sequence of the second notification data, thereby generating notification messages (A, B, C, D, E, and F) based on the SCS. At this time, among the notification messages (A, B, C, D, E, and F) based on the SCS, the most recently generated F may be an added message. For example, the wearable device (103) may authorize displaying the notification messages (A, B, C, D, E, and F) based on the SCS within the second notification view of the second application (252).

[0224] For example, while displaying the second notification view, the wearable device (103) may, at a third point in time, display a third notification view that is changed (or updated) from the second notification view. For example, the wearable device (103) may display second notification messages (D, E, F) within the third notification view of the second application (252). For example, the third notification view may be displayed when the most recently generated F among the notification messages (A, B, C, D, E, F) based on the SCS is positioned above a reference position (e.g., the reference position (650) of FIG. 6B) according to a scroll input within the second notification view. Or, for example, the third notification view may be displayed based on identifying a touch input for a pop-up message of the second notification view.

[0225] As described above, the present disclosure can update the UI to include further new notification data while maintaining the previously received notification data while displaying notification messages corresponding to received notification data within the UI. In this case, a hint regarding the new notification data can be provided within the updated UI. For example, the hint can be a message including text indicating the new notification data. Accordingly, the present disclosure can provide a user experience similar to the UI of the first application (251) within the UI of the second application (252) for notification to a user who is permitted to have a restricted display.

[0226] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs from the description below.

[0227] As described above, the wearable device (103) may include a display (220). The wearable device (103) may include a memory (240) that stores instructions and includes one or more storage media. The wearable device (103) may include at least one processor (210) that includes a processing circuit. The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to display, on the display (220), first notification messages corresponding to first messages received through a first application for messaging, within a user interface (UI) of a second application for notification. The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to receive a second message through the first application while displaying the first notification messages within the UI of the second application. The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to identify a user input received in connection with the UI of the second application after receiving the second message. The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to authorize re-displaying within the UI of the second application at least some of the first notification messages whose display was interrupted in response to the user input before the second notification message corresponding to the second message within the UI is moved to a reference position within the UI in response to the user input.

[0228] According to one embodiment, the instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to disable re-displaying the first notification messages within the UI of the second application based on identifying the second notification message moved to the reference location according to the user input.

[0229] In one embodiment, the instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to identify whether a most recently generated third notification message among the first notification messages displayed within the UI of the second application is positioned below the reference position within the UI of the second application after receiving the second message and before receiving the user input. The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to authorize display of the first notification messages and the second notification message within the UI of the second application based on identifying that the third notification message is positioned below the reference position. The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to disallow re-displaying the first notification messages within the UI of the second application and to display the second notification message within the UI of the second application based on identifying that the third notification message is located above the reference location.

[0230] In one embodiment, the instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to display a portion of the first notification messages and a portion of the second notification message within the UI of the second application based on identifying that the third notification message is located below the reference location. The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to stop displaying the second notification message and to display the first notification messages within the UI of the second application based on another user input in a first direction received prior to receiving the user input. The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to display, within the UI of the second application, a portion of the first notification messages and a portion of the second notification messages, in response to another user input in a second direction opposite to the first direction received after receiving the other user input in the first direction before receiving the user input, and to disallow re-displaying a notification message whose display was interrupted in response to the other user input in the second direction among the first notification messages.

[0231] According to one embodiment, the instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to display a pop-up message to indicate that the second notification message has been generated, floated on the UI of the second application, based on identifying that the third notification message is located below the reference location.

[0232] In one embodiment, the instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to identify a touch input with respect to the pop-up message displayed within the UI of the second application. The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to, based on identifying the touch input, disallow re-displaying the first notification messages within the UI of the second application and to display the second notification message within the UI of the second application.

[0233] In one embodiment, the instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to receive, through the first application, second messages including the second message while displaying the first notification messages within the UI of the second application. The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to identify, after receiving the second messages and before receiving the user input, whether a most recently generated third notification message among the first notification messages displayed within the UI of the second application is positioned below the reference position within the UI of the second application. The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to authorize displaying fourth notification messages, each corresponding to the first notification messages and the second messages, within the UI of the second application based on identifying that the third notification message is positioned below the reference location. The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to disauthorize displaying the first notification messages again within the UI of the second application and to display the fourth notification messages within the UI of the second application based on identifying that the third notification message is positioned above the reference location.

[0234] According to one embodiment, the instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to display a pop-up message to indicate that the second notification message, which is the most recently generated one of the fourth notification messages, has been generated, based on identifying that the third notification message is located below the reference location, on the UI of the second application.

[0235] According to one embodiment, the instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to authorize displaying a fifth notification message among the first notification messages and the fourth notification messages within the UI of the second application based on identifying that the third notification message is located below the reference location. The fifth notification message among the first notification messages may be a different notification message than the fourth notification messages among the first notification messages.

[0236] In one embodiment, the instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to, based on identifying that the third notification message is located below the reference location, authorize display of the fifth notification message and the fourth notification messages among the first notification messages within the UI of the second application, and then identify another user input received in connection with the UI of the second application prior to receiving the user input. The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to display, within the UI of the second application, at least some of the fifth notification message and the fourth notification messages, based on the other user input. Among the first notification messages, the fifth notification message, when displayed within the UI of the second application in response to the other user input, may have a first visual effect indicating that it is a deleted message. Among the fourth notification messages, the second notification message, which is different from the first notification messages and was most recently generated, may have a second visual effect indicating that it is an added message when displayed within the UI of the second application in response to the other user input.

[0237] In one embodiment, the instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to identify a first message sequence of the first messages based on identifying that the third notification message is located below the reference location. The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to identify a second message sequence of the second messages based on identifying that the third notification message is located below the reference location. The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to identify a shortest common supersequence (SCS) having each of the first message sequence and the second message sequence as a subsequence based on identifying that the third notification message is located below the reference location. The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to authorize display of the fifth notification message and the fourth notification messages within the UI of the second application using the SCS based on identifying that the third notification message is located below the reference location.

[0238] In one embodiment, the instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to identify, using the SCS, a third message from among the first messages that is different from the second messages. The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to identify, using the SCS, a fourth message from among the first messages that is the same as the second messages. The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to identify, using the SCS, a fifth message from among the second messages that is different from the first messages. The third message may correspond to a notification message deleted from the first notification messages and not included in the fourth notification messages. The fourth message may correspond to a notification message included in the fourth notification messages and maintained in the first notification messages. The fifth message may correspond to a notification message included in the fourth notification messages and added to the fourth notification messages.

[0239] In one embodiment, the instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to display a floated pop-up message on the UI of the second application based on identifying the last message among the messages of the SCS as the fifth message. The pop-up message may be updated to correspond to the last message among the second messages.

[0240] In one embodiment, the SCS may be identified according to a specified criterion using the longest common subsequence (LCS) between the first message sequence and the second message sequence. The specified criterion may include sequentially determining whether each message within the SCS is an added message, a maintained message, or a deleted message.

[0241] In one embodiment, the instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to identify the user input received in connection with the UI of the second application after receiving the second messages. The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to authorize the most recently generated of the fourth notification messages each corresponding to the second messages, before the second notification message corresponding to the second message moves to the reference position in response to the user input, to re-display at least some of the first notification messages, the display of which was interrupted in response to the user input, within the UI of the second application, and to authorize the display of the fourth notification messages within the UI of the second application.

[0242] According to one embodiment, the instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to, based on identifying the second notification message moved to the reference position in accordance with the user input, disallow re-displaying the first notification messages within the UI of the second application, and to display the fourth notification messages within the UI of the second application.

[0243] In one embodiment, the instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to receive third messages through the first application while authorizing display of the first notification messages and the fourth notification messages within the UI of the second application based on identifying that the third notification message is located below the reference location. The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to identify, after receiving the third messages and before receiving the user input, whether the most recently generated second notification message among the fourth notification messages displayed within the UI of the second application is located below the reference location within the UI of the second application. The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to authorize displaying, within the UI of the second application, fifth notification messages corresponding to the first notification messages, the fourth notification messages, and the third messages, respectively, based on identifying that the second notification message is positioned below the reference location. The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to disauthorize displaying, within the UI of the second application, the first notification messages and the fourth notification messages again, and to display, within the UI of the second application, the fifth notification messages, based on identifying that the second notification message is positioned above the reference location.

[0244] According to one embodiment, the first identification information for the first messages defined in the first application may be identical to the second identification information for the second messages defined in the first application.

[0245] In one embodiment, the instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to display a home screen including a watch face on the display (220). The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to display the UI of the second application on the display (220) based on a swipe input received with respect to the home screen.

[0246] As described above, the wearable device (103) may include a display (220). The wearable device (103) may include a memory (240) that stores instructions and includes one or more storage media. The wearable device (103) may include at least one processor (210) that includes a processing circuit. The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to display first notification messages, including a first message and a second message, on the display (220). The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to generate second notification messages including the second message and the third message based on receiving the second message and the third message while displaying the first notification messages. The instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to display, on the display (220), at least some of third notification messages including the first message, the second message, and the third message, generated based on the first notification messages and the second notification messages. The above instructions, when individually or collectively executed by the at least one processor (210), may cause the wearable device (103) to display, on the display, the second notification messages modified from the third notification messages based on a user input.

[0247] Electronic devices according to the various embodiments disclosed in this document may take various forms. Electronic devices may include, for example, portable communication devices (e.g., smartphones), computer devices, portable multimedia devices, portable medical devices, cameras, wearable devices, or home appliances. Electronic devices according to the embodiments of this document are not limited to the aforementioned devices.

[0248] The various embodiments of this document and the terminology used therein are not intended to limit the technical features described in this document to specific embodiments, but should be understood to include various modifications, equivalents, or substitutes of the embodiments. In connection with the description of the drawings, similar reference numerals may be used for similar or related components. The singular form of a noun corresponding to an item may include one or more of the items, unless the context clearly indicates otherwise. In this document, each of the phrases "A or B", "at least one of A and B", "at least one of A or B", "A, B, or C", "at least one of A, B, and C", and "at least one of A, B, or C" can include any one of the items listed together in the corresponding phrase among those phrases, or all possible combinations thereof. Terms such as "first," "second," or "first" or "second" may be used merely to distinguish one component from another, and do not limit the components in any other respect (e.g., importance or order). When a component (e.g., a first component) is referred to as "coupled" or "connected" to another component (e.g., a second component), with or without the terms "functionally" or "communicatively," it means that the component can be connected to the other component directly (e.g., wired), wirelessly, or through a third component.

[0249] The term "module" used in various embodiments of this document may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with terms such as logic, logic block, component, or circuit. A module may be an integral component, or a minimum unit or part of such a component that performs one or more functions. For example, according to one embodiment, a module may be implemented in the form of an application-specific integrated circuit (ASIC).

[0250] Various embodiments of the present document may be implemented as software (e.g., a program (140)) including one or more instructions stored in a storage medium (e.g., an internal memory (136) or an external memory (138)) readable by a machine (e.g., an electronic device (101)). For example, a processor (e.g., a processor (120)) of the machine (e.g., an electronic device (101)) may call at least one instruction among the one or more instructions stored from the storage medium and execute it. This enables the machine to operate to perform at least one function according to the at least one called instruction. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' simply means that the storage medium is a tangible device and does not contain signals (e.g., electromagnetic waves), and the term does not distinguish between cases where data is stored semi-permanently or temporarily on the storage medium.

[0251] According to one embodiment, the method according to various embodiments disclosed in this document may be provided as a computer program product. The computer program product may be traded between sellers and buyers as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., compact disc read-only memory (CD-ROM)) or may be provided through an application store (e.g., Play Store). TM ) or directly between two user devices (e.g., smart phones), online distribution (e.g., downloading or uploading). In the case of online distribution, at least a portion of the computer program product may be at least temporarily stored or temporarily created in a machine-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or an intermediary server.

[0252] According to various embodiments, each component (e.g., a module or a program) of the above-described components may include one or more entities, and some of the entities may be separated and placed in other components. According to various embodiments, one or more components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (e.g., a module or a program) may be integrated into a single component. In such a case, the integrated component may perform one or more functions of each of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to the integration. According to various embodiments, the operations performed by a module, program, or other component may be executed sequentially, in parallel, iteratively, or heuristically, or one or more of the operations may be executed in a different order, omitted, or one or more other operations may be added.

Claims

1. In a wearable device (103), display (220); A memory (240) storing instructions and including one or more storage media; and At least one processor (210) comprising a processing circuit, The above instructions, when individually or collectively executed by the at least one processor (210): Displaying first notification messages corresponding to first messages received through the first application for messaging, respectively, on the display (220) within the UI (user interface) of the second application for notification; While displaying the first notification messages within the UI of the second application, a second message is received through the first application; After receiving the second message, identify the user input received in relation to the UI of the second application; Causing the wearable device (103) to authorize re-displaying at least some of the first notification messages whose display has been interrupted within the UI of the second application before the second notification message corresponding to the second message within the UI is moved to a reference position within the UI according to the user input. Wearable device (103).

2. In claim 1, The above instructions, when individually or collectively executed by the at least one processor (210): Causing the wearable device (103) to disable re-displaying the first notification messages within the UI of the second application based on identifying the second notification message moved to the reference position according to the user input. Wearable device (103).

3. In claim 1, The above instructions, when individually or collectively executed by the at least one processor (210): After receiving the second message and before receiving the user input, identifying whether the most recently generated third notification message among the first notification messages displayed within the UI of the second application is located below the reference position within the UI of the second application; Authorizing display of the first notification messages and the second notification message within the UI of the second application based on identifying that the third notification message is located below the reference location; and Causing the wearable device (103) to disallow the re-display of the first notification messages within the UI of the second application based on identifying that the third notification message is located above the reference location, and to display the second notification message within the UI of the second application. Wearable device (103).

4. In claim 3, The above instructions, when individually or collectively executed by the at least one processor (210): Based on identifying that the third notification message is located below the reference location, displaying a portion of the first notification messages and a portion of the second notification message within the UI of the second application; According to another user input of the first direction received before receiving the user input, stop displaying the second notification message, and display the first notification messages within the UI of the second application; and After receiving another user input in the first direction before receiving the user input, according to another user input in the second direction opposite to the received first direction: Displaying a portion of the first notification messages and a portion of the second notification messages within the UI of the second application, and Causing the wearable device (103) to not authorize the re-display of a notification message that was stopped from being displayed according to another user input in the second direction among the first notification messages. Wearable device (103).

5. In claim 3, The above instructions, when individually or collectively executed by the at least one processor (210): Causing the wearable device (103) to display a pop-up message to notify that the second notification message is generated, floating on the UI of the second application, based on identifying that the third notification message is located below the reference position. Wearable device (103).

6. In claim 5, The above instructions, when individually or collectively executed by the at least one processor (210): Identifying a touch input with respect to the pop-up message displayed within the UI of the second application; and Based on identifying the touch input, causing the wearable device (103) to disallow re-displaying of the first notification messages within the UI of the second application, and to display the second notification message within the UI of the second application. Wearable device (103).

7. In claim 1, The above instructions, when individually or collectively executed by the at least one processor (210): While displaying the first notification messages within the UI of the second application, receiving second messages including the second message through the first application; After receiving the second messages and before receiving the user input, identifying whether the most recently generated third notification message among the first notification messages displayed within the UI of the second application is located below the reference position within the UI of the second application; Based on identifying that the third notification message is located below the reference location, authorizing display of fourth notification messages corresponding to the first notification messages and the second messages within the UI of the second application; and Causing the wearable device (103) to disallow re-displaying of the first notification messages within the UI of the second application based on identifying that the third notification message is located above the reference location, and to display the fourth notification messages within the UI of the second application. Wearable device (103).

8. In claim 7, The above instructions, when individually or collectively executed by the at least one processor (210): Causing the wearable device (103) to display a pop-up message to notify that the second notification message, which is the most recently generated one of the fourth notification messages, has been generated, based on identifying that the third notification message is located below the reference position, and is floated on the UI of the second application. Wearable device (103).

9. In claim 7, The above instructions, when individually or collectively executed by the at least one processor (210): Causing the wearable device (103) to authorize display of the fifth notification message among the first notification messages and the fourth notification messages within the UI of the second application based on identifying that the third notification message is located below the reference location, Among the first notification messages, the fifth notification message is a notification message different from the fourth notification messages among the first notification messages. Wearable device (103).

10. In claim 9, The above instructions, when individually or collectively executed by the at least one processor (210): Based on identifying that the third notification message is located below the reference position, after authorizing display of the fifth notification message and the fourth notification messages among the first notification messages within the UI of the second application, identifying other user input received in relation to the UI of the second application before receiving the user input; and Causing the wearable device (103) to display at least some of the fifth notification message and the fourth notification messages within the UI of the second application, according to the other user input; Among the first notification messages, the fifth notification message, when displayed within the UI of the second application according to the other user input, has a first visual effect indicating that it is a deleted message, and Among the fourth notification messages, the second notification message, which is different from the first notification messages and is the most recently generated, has a second visual effect indicating that it is an added message when displayed within the UI of the second application according to the other user input. Wearable device (103).

11. In claim 9, The above instructions, when individually or collectively executed by the at least one processor (210): Based on identifying that the above third notification message is located below the above reference location: Identifying a first message sequence of the first messages; Identifying a second message sequence of the second messages; Identifying a shortest common supersequence (SCS) having each of the first message sequence and the second message sequence as a subsequence; and Using the SCS, causing the wearable device (103) to display the fifth notification message and the fourth notification messages within the UI of the second application. Wearable device (103).

12. In claim 11, The above instructions, when individually or collectively executed by the at least one processor (210): Using the above SCS, identify a third message among the first messages that is different from the second messages; Using the SCS, identify a fourth message among the first messages that is identical to the second messages; and Using the SCS, the wearable device (103) is caused to identify a fifth message among the second messages that is different from the first messages, The third message corresponds to a notification message deleted within the first notification messages that is not included in the fourth notification messages, The fourth message is included in the fourth notification messages and corresponds to a notification message maintained within the first notification messages, and The fifth message is included in the fourth notification messages and corresponds to a notification message added within the fourth notification messages. Wearable device (103).

13. In claim 12, The above instructions, when individually or collectively executed by the at least one processor (210): Causing the wearable device (103) to display a floated pop-up message on the UI of the second application based on identifying the last message among the messages of the SCS as the fifth message; The above pop-up message is updated to correspond to the last message among the second messages. Wearable device (103).

14. In claim 12, The SCS is identified according to a specified criterion using the longest common subsequence (LCS) between the first message sequence and the second message sequence, and The above specified criteria include sequentially determining whether each message within the SCS is an added message, a maintained message, or a deleted message. Wearable device (103).

15. In claim 7, The above instructions, when individually or collectively executed by the at least one processor (210): After receiving the second messages, identifying the user input received in relation to the UI of the second application; and Causing the wearable device (103) to authorize re-displaying at least some of the first notification messages, the display of which was stopped according to the user input, within the UI of the second application before the second notification message corresponding to the second message, which is the most recently generated among the fourth notification messages corresponding to the second messages, moves to the reference position according to the user input, and to authorize displaying the fourth notification messages within the UI of the second application. Wearable device (103).

Images