Electronic device, method, and non-transitory computer-readable storage medium for displaying information

Abstract

An electronic device is disclosed. In a locked state of the electronic device, the electronic device may display, through a display, a lock screen including a first icon corresponding to a first application at a first position, a second icon corresponding to a second application at a second position, and a first widget of a third application at a third position between the first icon and the second icon. The electronic device may identify a notification from a fourth application. In response to the notification being related to an ongoing activity, the electronic device may display a second widget corresponding to the notification at the third position until another notification for a third widget is identified. In response to the notification being related to a static notification, the electronic device may display the second widget corresponding to the notification at the third position for a predetermined time period, and display the first widget at the third position after the predetermined time period.

Description

Electronic device, method, and non-transient computer-readable storage medium for displaying information

[0001] The following descriptions relate to an electronic device, a method, and a non-transient computer-readable storage medium for displaying information.

[0002] The electronic device can display pre-specified information (e.g., time or notifications) on the wallpaper (or background image) within the screen. Additionally, the electronic device can display notifications in the notification area within the home screen.

[0003] The present disclosure may include, by reference, all contents described in Korean Patent Application No. 10-2024-0119729 and Korean Patent Application No. 10-2024-0048963.

[0004] An electronic device is disclosed. The electronic device may include a touch-sensitive circuit and a display that displays a widget, which is a mini-application of an application; at least one processor that includes a processing circuit; and a memory that stores instructions and includes one or more storage media. When the instructions are executed individually or collectively by the at least one processor, the electronic device may cause the electronic device to display a lock screen through the display, comprising: a first icon corresponding to a first application at a first position, a second icon corresponding to a second application at a second position, and a first widget of a third application at a third position between the first icon and the second icon. When the instructions are executed individually or collectively by the at least one processor, the electronic device may cause the electronic device to identify a notification from a fourth application. When the above instructions are executed individually or collectively by the at least one processor, the electronic device may cause the second widget corresponding to the notification to be displayed at the third location until another notification for the third widget is identified in response to the notification being associated with an ongoing activity. When the above instructions are executed individually or collectively by the at least one processor, the electronic device may cause the second widget corresponding to the notification to be displayed at the third location for a predetermined time period in response to the notification being associated with a static notification, and after the predetermined time period, the first widget to be displayed at the third location.

[0005] An electronic device is disclosed. The electronic device may include a display that includes a touch-sensitive circuit and displays a widget which is a mini-application of an application; at least one processor that includes a processing circuit; and a memory that stores instructions and includes one or more storage media. When the instructions are executed individually or collectively by the at least one processor, the electronic device may cause a first icon corresponding to a first application and a second icon corresponding to a second application to be displayed on the lower part of the display through the display. When the instructions are executed individually or collectively by the at least one processor, the electronic device may cause a first widget containing information corresponding to a third application to be displayed on the display between the first icon and the second icon. The first widget may have a wider width than the first icon and the second icon. When the above instructions are executed individually or collectively by the at least one processor, the electronic device may receive a notification from a fourth application in the locked state and, through the display, display a second widget containing at least a portion of the notification on the first widget.

[0006] A method is disclosed. The method may be performed by an electronic device comprising a touch-sensitive circuit and a display that displays a widget, which is a mini-application of an application. The method may include, in a locked state of the electronic device: an action of displaying a lock screen through the display comprising a first icon corresponding to a first application at a first position, a second icon corresponding to a second application at a second position, and a first widget of a third application at a third position between the first icon and the second icon. The method may include an action of identifying a notification from a fourth application. The method may include an action of displaying a second widget corresponding to the notification at the third position until another notification for the third widget is identified in response to the notification being related to an ongoing activity. The method may include an action of displaying the second widget corresponding to the notification at the third position for a predetermined time period in response to the notification being related to a static notification, and, after the predetermined time period, displaying the first widget at the third position.

[0007] A method is disclosed. The method may be performed by an electronic device comprising a touch-sensitive circuit and a display that displays a widget, which is a mini-application of an application. The method may include an action of displaying a first icon corresponding to a first application and a second icon corresponding to a second application on the lower part of the display through the display. The method may include an action of displaying a first widget containing information corresponding to a third application between the first icon and the second icon through the display. The first widget may have a wider width than the first icon and the second icon. The method may include an action of receiving a notification from a fourth application in the lock state and displaying a second widget containing at least a portion of the notification on the first widget through the display.

[0008] A non-transitory computer-readable storage medium is disclosed. The non-transitory computer-readable storage medium may store a program comprising instructions. When the instructions are executed individually or collectively by at least one processor of an electronic device comprising a touch-sensitive circuit and a display that displays a widget which is a mini-application of an application, the electronic device may cause the electronic device to display a lock screen in a locked state of the electronic device, the lock screen comprising: a first icon corresponding to a first application at a first position, a second icon corresponding to a second application at a second position, and a first widget of a third application at a third position between the first icon and the second icon, through the display. When the instructions are executed individually or collectively by the at least one processor, the electronic device may cause the electronic device to identify a notification from a fourth application. When the above instructions are executed individually or collectively by the at least one processor, the electronic device may cause the second widget corresponding to the notification to be displayed at the third location until another notification for the third widget is identified in response to the notification being associated with an ongoing activity. When the above instructions are executed individually or collectively by the at least one processor, the electronic device may cause the second widget corresponding to the notification to be displayed at the third location for a predetermined time period in response to the notification being associated with a static notification, and after the predetermined time period, the first widget to be displayed at the third location.

[0009] A non-transient computer-readable storage medium is disclosed. The non-transient computer-readable storage medium may store a program comprising instructions. When the instructions are executed individually or collectively by at least one processor of an electronic device comprising a touch-sensitive circuit and a display that displays a widget which is a mini-application of an application, the electronic device may cause a first icon corresponding to a first application and a second icon corresponding to a second application to be displayed on the lower part of the display through the display. When the instructions are executed individually or collectively by the at least one processor, the electronic device may cause a first widget containing information corresponding to a third application to be displayed on the display between the first icon and the second icon. The first widget may have a wider width than the first icon and the second icon. When the above instructions are executed individually or collectively by the at least one processor, the electronic device may receive a notification from a fourth application in the locked state and, through the display, display a second widget containing at least a portion of the notification on the first widget.

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

[0011] FIG. 2 illustrates a lock screen displayed by an electronic device according to one embodiment.

[0012] FIG. 3 illustrates an AoD screen displayed by an electronic device according to one embodiment.

[0013] FIG. 4 illustrates a home screen displayed by an electronic device according to one embodiment.

[0014] FIG. 5a is a block diagram of a program according to one embodiment.

[0015] FIG. 5b is a block diagram of a program according to one embodiment.

[0016] FIG. 6 is a flowchart illustrating the operation of an electronic device determining the layout of a widget according to one embodiment.

[0017] FIG. 7 is a flowchart illustrating the operation of an electronic device displaying a widget according to one embodiment.

[0018] FIG. 8 is a flowchart illustrating the operation of an electronic device displaying a widget according to one embodiment.

[0019] FIG. 9 is a flowchart illustrating the operation of the notification manager and the Nauba manager of an electronic device according to one embodiment.

[0020] FIG. 10 illustrates an operation in which an electronic device changes the order of widgets according to one embodiment.

[0021] FIG. 11 is a flowchart illustrating the operation of a notification manager of an electronic device changing the order of widgets according to one embodiment.

[0022] FIG. 12 is a flowchart illustrating the operation of a notification manager transmitting a key name to a Nowva manager according to one embodiment.

[0023] FIG. 13 illustrates an operation in which an electronic device changes the order of widgets according to one embodiment.

[0024] FIG. 14 illustrates the operation of an electronic device notification manager transmitting a key name list to a Nauba manager according to one embodiment.

[0025] FIG. 15 illustrates an operation in which a notification manager of an electronic device transmits a key name list to a Nauba manager according to one embodiment.

[0026] FIG. 16 shows an item list of a Nauba Manager of an electronic device according to one embodiment.

[0027] FIG. 17 illustrates the operation of an electronic device notification manager transmitting a key name list to a Nauba manager according to one embodiment.

[0028] FIG. 18 illustrates an operation in which an electronic device changes the order of widgets according to one embodiment.

[0029] FIG. 19 illustrates the operation of a Nauba manager of an electronic device transmitting a key name list to a notification manager according to one embodiment.

[0030] FIG. 20 illustrates the operation of an electronic device notification manager displaying a Nowbar according to one embodiment.

[0031] FIG. 21 is a drawing illustrating the operation of displaying an ongoing activity widget of sports according to one embodiment.

[0032] FIG. 22 is a diagram illustrating the operation of an electronic device displaying an ongoing activity widget according to a schedule registered in a calendar DB, according to one embodiment.

[0033] FIG. 23 is a diagram illustrating the operation of an electronic device of a widget to improve visibility according to one embodiment.

[0034] FIGS. 24 to 26 are drawings illustrating a widget with improved visibility.

[0035] FIGS. 27a and FIGS. 27b are drawings illustrating an operation to change the display of another object so as not to overlap when an electronic device displays an enlarged widget according to one embodiment.

[0036] FIG. 28 is a diagram illustrating an operation of displaying a widget according to the position of a fingerprint sensor of an electronic device according to one embodiment.

[0037] FIG. 29 is a diagram illustrating an operation of displaying a notification related to the battery of an electronic device through a widget according to one embodiment.

[0038] FIG. 30 is a flowchart illustrating the operation of an electronic device initializing a Nauba according to one embodiment.

[0039] FIG. 31 is a flowchart illustrating the operation of an electronic device receiving an ongoing activity according to one embodiment.

[0040] FIG. 32 is a flowchart illustrating the operation of an electronic device displaying a battery status according to one embodiment.

[0041] FIG. 33 is a flowchart illustrating the operation of an electronic device updating contact info according to one embodiment.

[0042] FIG. 34 is a flowchart illustrating the operation of an electronic device displaying media according to one embodiment.

[0043] FIG. 35 is a flowchart illustrating the operation of an electronic device expanding a nauba according to one embodiment.

[0044] FIG. 36 is a flowchart illustrating the operation of an electronic device switching to a lock screen according to one embodiment.

[0045] FIGS. 37 and 38 are flowcharts illustrating the operation of an electronic device switching to dark mode according to one embodiment.

[0046] FIG. 39 is a flowchart illustrating the operation of an electronic device displaying a widget according to one embodiment.

[0047] FIG. 40 is a drawing illustrating a UI displayed on a multi-foldable electronic device according to one embodiment.

[0048] FIG. 1 is a block diagram of an electronic device (101) in a network environment (100) according to various embodiments.

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

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

[0051] The auxiliary processor (123) may control at least some of the functions or states associated with at least one component of the electronic device (101) (e.g., display module (160), sensor module (176), or communication module (190)) 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. According to one embodiment, the auxiliary processor (123) (e.g., image signal processor or communication processor) may be implemented as part of another functionally related component (e.g., camera module (180) or communication module (190)). According to one embodiment, the auxiliary processor (123) (e.g., neural network processing unit) may include a hardware structure specialized for processing an artificial intelligence model. The artificial intelligence model may be generated through machine learning. Such learning may be performed, for example, on the electronic device (101) itself where the artificial intelligence model is executed, or through a separate server (e.g., server (108)). The learning algorithm may 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 may include a plurality of artificial neural network layers.An artificial neural network may be 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 the hardware structure, the artificial intelligence model may include a software structure, either additionally or substantially.

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

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

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

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

[0056] The display module (160) can visually provide information to an external (e.g., 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 said device. According to 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 the force generated by said touch.

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

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

[0059] The interface (177) may support one or more specified protocols that can be used for the electronic device (101) to be connected directly or wirelessly to an external electronic device (e.g., electronic device (102)). According to 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.

[0060] The connection terminal (178) may include a connector through which the electronic device (101) can 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).

[0061] The haptic module (179) can convert an electrical signal into a mechanical stimulus (e.g., vibration or movement) or an electrical stimulus that the user can perceive through tactile or kinesthetic senses. According to one embodiment, the haptic module (179) may include, for example, a motor, a piezoelectric element, or an electric stimulation device.

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

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

[0064] The battery (189) can supply power to at least one component of the electronic device (101). According to one embodiment, the battery (189) may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0065] The communication module (190) can support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between an 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 include one or more communication processors that operate independently of the processor (120) (e.g., application processor) and 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., cellular communication module, short-range wireless communication module, or GNSS (global navigation satellite system) communication module) or a wired communication module (194) (e.g., LAN (local area network) communication module, or power line communication module). The corresponding communication module among these communication modules can communicate with an external electronic device (104) through a first network (198) (e.g., a short-range communication network such as Bluetooth, WiFi (wireless fidelity) direct, or IrDA (infrared data association)) or a second network (199) (e.g., 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 may 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 identify or authenticate the electronic device (101) within a communication network such as the first network (198) or the second network (199) using subscriber information (e.g., International Mobile Subscriber Identifier (IMSI)) stored in the subscriber identification module (196).

[0066] The wireless communication module (192) can support 5G networks and next-generation communication technologies following 4G networks, for example, new radio access technology. NR access technology can support high-speed transmission of high-capacity data (enhanced mobile broadband (eMBB)), minimization of terminal power and connection of multiple terminals (massive machine type communications (mMTC)), or high reliability and low latency (ultra-reliable and low-latency communications (URLLC)). The wireless communication module (192) can support a high-frequency band (e.g., mmWave band) to achieve a high data transmission rate, for example. The wireless communication module (192) can support various technologies for securing performance in the high-frequency band, such as beamforming, massive MIMO (multiple-input and multiple-output), 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), external electronic device (e.g., electronic device (104)), or network system (e.g., 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 realizing eMBB, loss coverage (e.g., 664 dB or less) for realizing mMTC, or U-plane latency (e.g., downlink (DL) and uplink (UL) each 0.5 ms or less, or round trip 6 ms or less) for realizing URLLC.

[0067] An antenna module (197) can transmit a signal or power to or from an external source (e.g., an external electronic device). According to one embodiment, the antenna module (197) may include an antenna comprising a radiator made of a conductor or a conductive pattern formed on a substrate (e.g., a PCB). According to 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 a first network (198) or a second network (199), may be selected from the plurality of antennas, for example, by a 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. According to some embodiments, in addition to the radiator, other components (e.g., a radio frequency integrated circuit (RFIC)) may be additionally formed as part of the antenna module (197).

[0068] 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 to a first surface (e.g., bottom surface) of the printed circuit board and capable of supporting a specified high frequency band (e.g., mmWave band), and a plurality of antennas (e.g., array antennas) disposed on or adjacent to a second surface (e.g., top surface or side surface) of the printed circuit board and capable of transmitting or receiving a signal of the specified high frequency band.

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

[0070] According to one embodiment, commands or data may be transmitted or received between the electronic device (101) and an external electronic device (104) through a server (108) connected to a second network (199). Each of the external electronic devices (102, or 104) may be the same or different type of device as the electronic device (101). According to one embodiment, all or part of the operations performed on the electronic device (101) may be performed on one or more of the external electronic devices (102, 104, or 108). For example, if the electronic device (101) needs to perform a function or service automatically or in response to a request from a user or another device, the electronic device (101) may request one or more external electronic devices to perform at least part of the function or service instead of performing the function or service itself or additionally. One or more external electronic devices that receive the above request may execute at least part of the requested function or service, or 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 provide the result as is or additionally processed as at least part of the response to the request. For this purpose, for example, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used. The electronic device (101) may provide ultra-low latency services using, for example, distributed computing or mobile edge computing. In another embodiment, the external electronic device (104) may include an Internet of Things (IoT) device. The server (108) may be an intelligent server using machine learning and / or neural networks. According to one embodiment, the external electronic device (104) or the server (108) may be included within 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.

[0071] FIG. 2 illustrates a lock screen displayed by an electronic device according to one embodiment.

[0072] Figure 2 can be explained with reference to Figure 1.

[0073] Referring to the state (201) of FIG. 2, the electronic device (101) may display a lock screen in a locked state through a display (260) (e.g., the display module (160) of FIG. 1). In one embodiment, the locked state may be a state in which access to the electronic device (101) is restricted. In one embodiment, restricted access to the electronic device (101) may include restricting the execution of applications other than allowed applications. In one embodiment, restricted access to the electronic device (101) may include restricting the display of information other than allowed information. In one embodiment, the lock screen may refer to a screen displayed on the display (260) in a locked state.

[0074] Referring to the state (201) of FIG. 2, the lock screen may include a background area (210). In one embodiment, a wallpaper (or background image) may be displayed in the background area (210). In one embodiment, the wallpaper displayed in the background area (210) of the lock screen may be a pre-specified image. In one embodiment, the wallpaper displayed in the background area (210) of the lock screen may be an image that changes according to the state of the electronic device (101). In one embodiment, the background area (210) may display a visual object (211) (e.g., a lock image) indicating a lock state and / or an input area (e.g., a fingerprint image) for obtaining an input (e.g., a fingerprint image) for unlocking the lock state (or an area where a sensor module (176) (e.g., a biometric sensor, a fingerprint sensor) is located) a visual object (213) (e.g., a fingerprint image).

[0075] In one embodiment, the lock screen may include a first icon area (230) and a second icon area (240). In one embodiment, icons of applications may be displayed in the first icon area (230) and the second icon area (240).

[0076] In one embodiment, the electronic device (101) can display a widget based on a notification (or event) on the lock screen.

[0077] Referring to the state (202) of FIG. 2, the electronic device (101) may display a widget in the widget area (220). In one embodiment, the widget area (220) may display a widget for displaying notifications (or information) related to an application. In one embodiment, the widget area (220) may display a widget for displaying information (or notifications) generated by an application running (in the background). In one embodiment, the widget may be classified into an information widget, a management widget, or a hybrid widget for information and management. In one embodiment, the information widget may display information elements (e.g., current weather, information on the currently playing song, step count, exercise time) provided by the application associated with the widget. In one embodiment, the management widget may display function elements (e.g., play next song, pause, answer call, hang up call) provided by the application associated with the widget. For example, the electronic device (101) can control some functions of an application associated with the widget in response to a selection of functional elements provided by the management widget. In one embodiment, the hybrid widget can display information elements and functional elements provided by the application associated with the widget. For example, the widget may be referred to as a mini-application for the application associated with the widget.

[0078] For example, a widget may include one or more objects to display information (or notifications) generated by an application. For example, one or more objects may include images and / or text.

[0079] In one embodiment, the widget area (220) may be located at a designated location on the lock screen. For example, the widget area (220) may be located between the first icon area (230) and the second icon area (240). For example, the distance between the widget area (220) and the first icon area (230) may be the same as the distance between the widget area (220) and the second icon area (240). In one embodiment, the widget area (220) may be located below the visual object (213) (or input area). In one embodiment, the widget area (220) may be located so as not to overlap with the visual object (213) (or input area).

[0080] In one embodiment, the horizontal line connecting the center of the widget area (220) may be the same as the horizontal line connecting the center of the first icon area (230). In one embodiment, the widget area (220) may have a longer length in the height direction than the first icon area (230). For example, as transitioning from state (201) to state (202), the diameter of the first icon area (230) (e.g., length in the height direction and / or length in the width direction) decreases, and accordingly, the length in the height direction of the widget area (220) may be longer than the length in the height direction of the first icon area (230).

[0081] In one embodiment, the horizontal line connecting the center of the widget area (220) may be the same as the horizontal line connecting the center of the second icon area (240). In one embodiment, the widget area (220) may have a longer length in the height direction than the second icon area (240). For example, as transitioning from state (201) to state (202), the diameter of the second icon area (240) (e.g., length in the height direction and / or length in the width direction) decreases, and accordingly, the length in the height direction of the widget area (220) may be longer than the length in the height direction of the second icon area (240).

[0082] In one embodiment, the widget area (220) may be located in a relatively lower part of the lock screen. For example, interactive objects displayed on the lock screen (e.g., icon areas (230, 240)) and / or information elements (e.g., weather) may be located at least on the same line as the widget area (220). For example, areas where interactive objects displayed on the lock screen (e.g., icon areas (230, 240)) and / or information elements (e.g., weather) may be displayed on a horizontal line connecting the center of the widget area (220). For example, areas where interactive objects displayed on the lock screen (e.g., icon areas (230, 240)) and / or information elements (e.g., weather) may not be displayed on the lower part of the horizontal line connecting the center of the widget area (220). However, this is not limited thereto.

[0083] In one embodiment, the widget area (220) may be located in a relatively central part of the lock screen. For example, the widget area (220) may be positioned with respect to a vertical line connecting the center of the lock screen. For example, the widget area (220) may be positioned such that the area to the left of the vertical line and the area to the right of the vertical line are identical. However, it is not limited thereto.

[0084] In one embodiment, the electronic device (101) can change the widget area (220) and / or icon areas (230, 240) displayed on the lock screen based on a notification (or event).

[0085] In one embodiment, the electronic device (101) may display an indicator (221) (or hint) indicating that there are more widgets displaying additional notifications based on the fact that there are two or more applications generating notifications (or events). The indicator (221) (or hint) may indicate that there are other widgets in the next layer of the widget displayed in the widget area (220).

[0086] For example, in the state (202) of FIG. 2, the electronic device (101) may display another widget in the widget area (220) instead of the widget based on an up or down swipe input (or, drag input) for the widget placed in the widget area (220). For example, the electronic device (101) may display a widget following the widget displayed in the widget area (220) in the widget area (220) based on an up or down swipe input (or, drag input) for the widget placed in the widget area (220). For example, in the state (202) of FIG. 2, the electronic device (101) may display another widget on top of the widget instead of the widget based on an up or down swipe input (or, drag input) for the widget placed in the widget area (220).

[0087] For example, in the state (202) of FIG. 2, the electronic device (101) may stop displaying the widget based on a swipe input (or drag input) in the left or right direction for the widget placed in the widget area (220). For example, if there is no widget following the widget displayed in the widget area (220), the electronic device (101) may transition to a state (201) in which the widget is not displayed in the widget area (220). In one embodiment, the electronic device (101) may stop displaying the widget through an animation effect in which the widget disappears based on the decision not to display the widget. According to an embodiment, in the state (201) of FIG. 2, the electronic device (101) may display the widget that was stopped in the widget area (220) again based on a tap input (or double tap input) for the widget area (220). In one embodiment, the electronic device (101) can redisplay the widget through an animation effect in which the widget appears, based on a decision to redisplay the widget.

[0088] For example, in state (202) of FIG. 2, the electronic device (101) may display the widget in the widget area (223) which is expanded above the top and sides of the widget area (220), based on a tap input (or double tap input) for the widget placed in the widget area (220). In one embodiment, based on a decision to display the widget displayed in the widget area (220) in the widget area (223), the electronic device (101) may display the widget in the widget area (223) through an animation effect in which the widget is expanded. In one embodiment, referring to state (203), the electronic device (101) may stop displaying icons in the first icon area (230) and the second icon area (240) as it displays the widget in the widget area (223) which is expanded beyond the distance between the first icon area (230) and the second icon area (240).

[0089] For example, in the state (203) of FIG. 2, the electronic device (101) may display a widget in the widget area (220) instead of the widget area (223) based on a tap input (or double tap input) for an area other than the widget area (223). In one embodiment, based on a decision to display a widget displayed in the widget area (223) in the widget area (220), the electronic device (101) may display the widget in the widget area (220) through an animation effect in which the widget is reduced.

[0090] FIG. 3 illustrates an AoD screen displayed by an electronic device according to one embodiment.

[0091] FIG. 3 can be explained with reference to FIG. 1 and FIG. 2.

[0092] In one embodiment, referring to the states (302, 303) of FIG. 3, the electronic device (101) may display an always-on-display (AoD) screen (hereinafter referred to as the AoD screen) based on specified conditions. For example, referring to the states (302, 303) of FIG. 3, the AoD screen may be a screen for low-power operation of the electronic device (101). The AoD screen may include a background screen of a specified color (e.g., black). The AoD screen may not include an indicator (221) (or a hint). In one embodiment, low-power operation of the electronic device (101) may include the processor (120) of the electronic device (101) being operated in a low-power state (e.g., the operating frequency of the processor (120) being lowered and / or some of the processors of the processor (120) entering a sleep state). In one embodiment, low-power operation of the electronic device (101) may include the display (260) of the electronic device (101) being operated in a low-power state (e.g., the screen refresh cycle displayed on the display (260) is extended and / or the brightness of the display (260) is reduced). In one embodiment, the mode in which the electronic device (101) displays an AoD screen may be referred to as a power-saving mode. In one embodiment, the AoD screen of the electronic device (101) may be referred to as a power-saving screen.

[0093] In one embodiment, a widget displayed in the widget area (220) of the AoD screen may contain less information than a widget displayed in the widget area (220) of the lock screen. For example, at least some of the information of a widget displayed in the widget area (220) of the lock screen may be displayed in a widget displayed in the widget area (220) of the AoD screen.

[0094] In the state (302) of FIG. 3, the electronic device (101) may not display icon areas (230, 240) on the AoD screen. Accordingly, icons may not be displayed in the icon areas (230, 240) of the AoD screen.

[0095] In one embodiment, when switching to an AoD screen while the lock screen of the state (202) of FIG. 2 is displayed, the electronic device (101) may display an AoD screen of the state (302) of FIG. 3. For example, when switching to an AoD screen while the lock screen of the state (202) of FIG. 2 is displayed, the electronic device (101) may display a widget in the widget area (220) of the AoD screen.

[0096] In one embodiment, when switching to an AoD screen while the lock screen of the state (203) of FIG. 2 is displayed, the electronic device (101) may display an AoD screen of the state (303) of FIG. 3. In one embodiment, when switching to an AoD screen while the lock screen of the state (203) of FIG. 2 is displayed, the electronic device (101) may display a widget in the enlarged widget area (223) of the AoD screen.

[0097] In one embodiment, when switching from a lock screen to an AoD screen, the electronic device (101) can determine whether a widget displayed on the lock screen can be displayed on the AoD screen. In one embodiment, the electronic device (101) can display a widget displayed on the lock screen on the AoD screen based on whether the widget displayed on the lock screen can be displayed on the AoD screen. In one embodiment, the electronic device (101) may not display a widget displayed on the lock screen on the AoD screen based on whether the widget displayed on the lock screen cannot be displayed on the AoD screen.

[0098] FIG. 4 illustrates a home screen displayed by an electronic device according to one embodiment.

[0099] FIG. 4 can be explained with reference to FIGS. 1 to 3.

[0100] In the state (402) of FIG. 4, the widget area (420) (or horizontal bar) (or notification bar) (or status bar) can be distinguished from the widget areas (220, 223) of FIG. 2. For example, the widget area (420) can be displayed at the top of the screen of the display (260). For example, the widget area (420) can be displayed on the left side of the screen of the display (260).

[0101] In one embodiment, a widget may be displayed in the widget area (420). The widget in the widget area (420) may display information related to an application. In one embodiment, the widget may display information (or notifications) generated by an application running (in the background). In one embodiment, the widget may be classified as an information widget, a management widget, or a hybrid widget for information and management. For example, the widget may include one or more objects to display information (or notifications) generated by the application. For example, one or more objects may include images and / or text.

[0102] In one embodiment, the widget area (420) may be displayed in the notification area (411). In one embodiment, the notification area (411) may be displayed at the top of the screen of the display (260). In one embodiment, the notification area (411) may indicate the status of the electronic device (e.g., battery status, communication status) and / or the current time.

[0103] In one embodiment, the widget area (420) may be displayed in an unlocked state (or in use state). In this case, a screen other than the lock screen (e.g., home screen, or application screen, or app screen) may be displayed in the background area (410) of the display (260).

[0104] In one embodiment, the electronic device (101) can change the widget area (420) displayed in the unlocked state (or, in use state) based on an event.

[0105] For example, in the state (402) of FIG. 4, the electronic device (101) may display the widget in a widget area (423) that is enlarged beyond the widget area (420) based on input for the widget placed in the widget area (420). For example, the widget area (423) may be displayed at a location that does not overlap with the notification area (411) (e.g., below the notification area (411)).

[0106] For example, in the state (402) of FIG. 4, the electronic device (101) may display another widget in the widget area (420) instead of the widget based on an up or down swipe input (or drag input) for the widget placed in the widget area (420). For example, the electronic device (101) may display a widget following the widget displayed in the widget area (420) in the widget area (420) based on an up or down swipe input (or drag input) for the widget placed in the widget area (420).

[0107] For example, the electronic device (101) may change the order of the widgets based on an upward or rightward swipe input (or drag input) for a widget placed in the widget area (420). For example, the order of the widgets may be used to determine which widget is displayed in the widget area (220, 223, 420, 423). For example, a top card widget among the widgets may be displayed in the widget area (220, 223, 420, 423). For example, by changing the order of the widgets, the widget displayed in the widget area (420, 423) within a screen other than the lock screen (e.g., home screen, and / or application screen) may be changed. Also, for example, by changing the order of the widgets, the widget displayed in the widget area (220, 223) within the lock screen (or AoD screen) may be changed.

[0108] For example, depending on an input that changes the order of widgets (e.g., a swipe input), the electronic device (101) can change the widgets displayed in the widget areas (220, 223, 420, 423). For example, depending on an input that changes the order of widgets for a widget displayed in the widget area (420) (e.g., a swipe input), the widgets displayed in the other widget areas (220, 223, 423) as well as in the widget area (420) can be changed.

[0109] For example, referring to the state (403) of FIG. 4, the electronic device (101) can change the widget area (420) into an enlarged widget area (423) based on input to the widget area (420). In the state (403), after a widget is displayed in the widget area (423) for a specified time, the widget area (423) can be changed back to the widget area (420).

[0110] For example, in the state (403) of FIG. 4, the electronic device (101) may display another widget in the widget area (423) instead of the widget based on an up or down swipe input (or, drag input) for the widget placed in the widget area (423). For example, the electronic device (101) may display a widget following the widget displayed in the widget area (423) in the widget area (423) based on an up or down swipe input (or, drag input) for the widget placed in the widget area (423). For example, in the state (403) of FIG. 4, the electronic device (101) may display another widget on top of the widget instead of the widget based on an up or down swipe input (or, drag input) for the widget placed in the widget area (423).

[0111] For example, in the state (403) of FIG. 4, while displaying a widget in the widget area (420, 423), the electronic device (101) may receive input for executing an application. For example, the electronic device (101) may display an application execution screen. For example, while displaying the application execution screen, the electronic device (101) may display a home screen through the display (260) based on user input for switching to the home screen. In one embodiment, the electronic device (101) may display an application widget or a widget displayed before executing the application in the widget area (420) within the home screen.

[0112] In one embodiment, the electronic device (101) may display the application's widget in the notification area (420) of the home screen based on the application executing a first task corresponding to an ongoing activity. In one embodiment, the electronic device (101) may display a previously displayed widget instead of the application's widget in the notification area (420) of the home screen based on the application executing a second task corresponding to a static notification.

[0113] FIG. 5a is a block diagram of a program (140) according to one embodiment. FIG. 5b is a block diagram of a program (140) according to one embodiment.

[0114] FIGS. 5a and FIGS. 5b can be explained with reference to FIGS. 1 to 4.

[0115] In one embodiment, referring to FIG. 5a, the electronic device (101) may include an ongoing application (510), a system UI (user interface) (550), and a system server (590) as a program (140) stored in memory (130).

[0116] In one embodiment, referring to FIG. 5a, the electronic device (101) may include a sports application (521), an AoD application (522), a map application (523), an IoT (internet of things) connection application (524), and / or a routine application (525) as a program (140) stored in memory (130).

[0117] In one embodiment, the ongoing application (510) may include a clock application (511), a voice recorder (512), a health application (513), an interpreter application (514), and / or a message application (515).

[0118] In one embodiment, the system UI (550) may include an artificial intelligence (AI) brief (551), a notification highlight (552), a media application (553), contact info (554), a Nowva UI (560), an ongoing UI (570), and / or an ongoing activity (580).

[0119] In one embodiment, the system server (590) may include an application search (591) and / or a notification (592).

[0120] In one embodiment, referring to FIG. 5b, a program (140) stored in memory (130) may include a Nowbar Manager (531), a Notification Manager (532), a Now Brief (533), and / or a Power Manager (534).

[0121] In one embodiment, the application (146) illustrated in FIG. 5b may be referred to as the ongoing application (510) of FIG. 5a. In one embodiment, the notification manager (532) illustrated in FIG. 5b may be referred to as the notification (592) of FIG. 5a.

[0122] In one embodiment, the Nowva Manager (531) can provide useful information via a widget based on the current state of the electronic device (101) on the lock screen, and / or update the widget in real time. For example, the Nowva Manager (531) can manage application notifications (e.g., notifications of ongoing activities and static notifications).

[0123] For example, the Nowva Manager (531) can display traffic conditions and / or weather information via a widget during the user's commute time. In one embodiment, the widget displayed by the Nowva Manager (531) on the lock screen (or AoD screen) may be referred to as Nowva.

[0124] For example, the notification manager (532) can manage notifications of the application (e.g., notifications of ongoing activities). For example, the notification manager (532) can manage the reception, classification, display, and / or deletion of all notifications of the application. For example, the notification manager (532) can receive message notifications from the message application (515), display the received message notifications via a widget, and delete the message notifications when the user checks the message notifications.

[0125] For example, the notification manager (532) can monitor a list of widgets displayed on the home screen and lock screen (or AoD screen) in real time and send an update request to the Nowva manager (531). In one embodiment, the Nowva manager (531) can update the Nowva item stack based on data from the notification manager (532). In one embodiment, the Nowva item stack may include Nowva items assigned priority according to the application type. For example, the priority of a Nowva item for an ongoing activity may be higher than the priority of a Nowva item for a static notification.

[0126] For example, the Nowva Manager (531) can monitor a list of widgets displayed on the lock screen (or AoD screen) in real time and, based on receiving user input to change the order of widgets displayed in the widget area (220, 223), can notify the Notification Manager (532) that the order of the widgets has been changed. In one embodiment, the Notification Manager (532) can update the order of key names based on data from the Nowva Manager (531) indicating that the order of the widgets has been changed. In one embodiment, the key name may represent information for identifying the widget of an application to determine the top card displayed in the widget area. Accordingly, when transitioning from the lock screen (or AoD screen) to the unlock screen, the Notification Manager (532) can determine the widget to be displayed in the widget area (420, 423) using the updated key name based on the data transmitted from the Nowva Manager (531).

[0127] In one embodiment, the application can register a notification with the notification manager (532). In one embodiment, the application search (591) can perform the role of a search engine as a system service of the operating system (OS) of the electronic device (101). For example, the application search (591) can search for applications and data within the electronic device (101) and provide the searched data to the notification manager (532) and / or the Nowva manager (531).

[0128] For example, the sports application (521) can provide sports game details (e.g., information before, during, and after the game) to the Nauba manager (531).

[0129] In one embodiment, the media application (553) can provide information about the media currently being played (e.g., music, video) (e.g., title and artist information of the media currently being played) to the Nowva manager (531).

[0130] In one embodiment, the power manager (534) may provide battery information of the electronic device (101) to the Nowva manager (531) as an intent. For example, the power manager (534) may provide a warning notification to the Nowva manager (531) when the remaining battery level of the electronic device (101) decreases to a threshold value (e.g., 15%) or lower.

[0131] In one embodiment, the routine application (525) can provide information indicating that the current mode is changed to the Nowva manager (531) via an intent.

[0132] In one embodiment, the Now Brief (533) can provide recommendations to the user. For example, the Now Brief (533) can provide recommendations reflecting personalized interests that match the current situation of the electronic device (101) (e.g., current location, time) to the Now Bar Manager (531) as an intent.

[0133] In one embodiment, the notification manager (532) may display an ongoing activity as a widget. In one embodiment, the Nowva manager (531) may display an ongoing activity and / or static notifications as widgets. For example, the widget displaying an ongoing activity may be referred to as the ongoing activity widget. For example, the widget displaying a static notification may be referred to as the static notification widget.

[0134] For example, an ongoing activity widget can display the status of a real-time task running in an application. For example, an ongoing activity widget can allow a user to check the progress of a task running in the background or interact with it. For example, an ongoing activity widget can include frequently changing information, such as timer playback, download status, and map navigation.

[0135] For example, an ongoing activity widget can be used for providing real-time information and managing tasks. For example, an ongoing activity widget may include control buttons to enable direct interaction with the user. For example, an ongoing activity widget may perform timer playback in a clock application (511), provide navigation in a map application (523), and / or voice recording in a voice recorder (512). For example, an ongoing activity widget for timer playback may include control buttons to start the timer in the clock application (511) and perform controls such as play, pause, and record. For example, an ongoing activity widget for file download may include control buttons that display the download progress in real-time and allow the file to be opened after completion. For example, an ongoing activity widget for navigation may display real-time route guidance and notifications such as remaining time and distance.

[0136] For example, the ongoing activity widget of a clock application (511) can display the real-time status of a timer and / or stopwatch. For example, the ongoing activity widget of a voice recorder (512) can display the status of an ongoing recording and related information. For example, the ongoing activity widget of a health application (513) can provide exercise tracking information (e.g., information such as exercise time, distance, and calories burned). For example, the ongoing activity widget of a map application (523) can provide map navigation (e.g., real-time route guidance, remaining distance, and estimated arrival time). For example, the ongoing activity widget of an application for sharing emergency situations can display that my location and other information are being shared with emergency contacts. For example, the ongoing activity widget of an interpreter application (514) can display that a conversation is currently being interpreted. For example, the ongoing activity widget of a third application can provide progress based on the type of application. For example, in the case of a delivery application, the ongoing activity widget can provide the progress of deliveries. For example, in the case of a taxi application, the ongoing activity widget can provide the current status, such as taxi reservations.

[0137] For example, a static notification widget may be a notification that provides the user with consistent information or has little to no change in the application's state. For instance, a static notification widget may contain information that does not change frequently, such as system information, routine settings, and battery status. For instance, a static notification widget can provide stable and continuous status information. For instance, a static notification widget may have limited interaction with the user and focus primarily on providing information.

[0138] For example, a static notification widget can display information about battery status, Wi-Fi (or Bluetooth) connection details, and / or configured routines. For example, regarding battery status, the static notification widget can continuously display the remaining battery level and charge status. For example, regarding Wi-Fi connection status, the static notification widget can display connected network information and provide a link to navigate to settings if a network change is required. For example, regarding user-configured routines, the static notification widget can display the status of a mode activated based on specific times or conditions (e.g., Night Mode, Do Not Disturb Mode). For example, a static notification widget for a mode (or routine) can display the active status of the user-defined mode or routine.

[0139] For example, a static notification widget for an application for playing a media application (553) (e.g., music, video) can display information about the media currently being played and control buttons. For example, a static notification widget for contact info (554) (e.g., contacts set by the user) can display the status of a call or message with a specific contact.

[0140] For example, in the case of an application for weather updates, the static notification widget may display real-time weather information. For example, in the case of an application that saves today's schedule, the static notification widget may display the user's schedule and appointments. However, embodiments are not limited thereto. For example, the static notification widget may display the airplane mode activation status, data usage, and / or readiness for system updates.

[0141] FIG. 6 is a flowchart illustrating the operation of an electronic device (101) determining the layout of a widget according to one embodiment.

[0142] FIG. 6 can be explained with reference to FIGS. 1 to 5b.

[0143] Referring to FIG. 6, in operation 601, the electronic device (101) can generate ongoing activity data.

[0144] In operation 602, the electronic device (101) can generate a Nauba item.

[0145] In operation 603, the electronic device (101) can refresh the Nowva content. The Nowva content may represent Nowva items. For example, the Nowva items may include an icon, primary information, secondary information, and / or information about an action button.

[0146] In operation 604, the electronic device (101) can determine whether the position of the chronometer is the first position. For example, if the primary information within the Nauba item indicates a chronometer (or timer), the electronic device (101) can determine that the position of the chronometer is the first position.

[0147] In operation 605, the electronic device (101) can determine whether the secondary information is in an empty state.

[0148] In operation 606, the electronic device (101) can determine the layout of the widget as a chronometer primary simple layout. For example, the chronometer primary simple layout may be a layout in which the widget includes an application icon, primary information representing the chronometer, and an action button.

[0149] In operation 607, the electronic device (101) can determine the layout of the widget as a chronometer primary layout. For example, the chronometer primary layout may be a layout in which the widget includes an application icon, primary information representing the chronometer, and secondary information.

[0150] In operation 608, the electronic device (101) can determine whether the position of the chronometer is a second position. For example, if the secondary information within the Nauba item indicates a chronometer (or timer), the electronic device (101) can determine that the position of the chronometer is a second position.

[0151] In operation 609, the electronic device (101) can determine the layout of the widget as a default chronometer layout. For example, the default chronometer layout may be a layout in which the widget includes an application icon, primary information, secondary information indicating a chronometer, and an action button.

[0152] In operation 610, the electronic device (101) can determine whether the secondary information is in an empty state and the position of the chronometer is undefined.

[0153] In operation 611, the electronic device (101) may determine the layout of the widget as a simple layout. For example, the simple layout may be a layout in which the widget includes an application icon, primary information, and an action button.

[0154] In operation 612, the electronic device (101) can determine the layout of the widget as a default layout. For example, the default layout may be a layout in which the widget includes an application icon, primary information, secondary information, and an action button.

[0155] FIG. 7 is a flowchart illustrating the operation of an electronic device (101) displaying a widget according to one embodiment.

[0156] FIG. 7 can be explained with reference to FIGS. 1 to 6.

[0157] Referring to FIG. 7, in operation 701, the electronic device (101) can execute a plurality of applications. The electronic device (101) can execute a plurality of applications in an unlocked state and / or a locked state.

[0158] In one embodiment, the electronic device (101) can display an ongoing activity widget of an application having an ongoing activity among applications running through the notification manager (532) in the widget area (420).

[0159] In operation 702, the electronic device (101) can identify the priority of the application through the notification manager (532).

[0160] In operation 703, the electronic device (101) can transmit the key name of the top card of an ongoing activity to the Nowva manager (531) via the notification manager (532). The electronic device (101) can identify the highest priority application identified via the notification manager (532) as the top card.

[0161] In operation 704, the electronic device (101) can display a screen (e.g., a lock screen, and / or an AoD screen) while locked.

[0162] In operation 705, the electronic device (101) can identify the order of widgets through key names via the Nowva manager (531). In one embodiment, the electronic device (101) can identify the order of widgets through key names that add static notifications to ongoing activities transmitted from the notification manager (532) via the Nowva manager (531).

[0163] In operation 706, the electronic device (101) can display widgets according to the order identification of widgets through the Nowva manager (531). For example, the electronic device (101) can display a widget having a top card in the widget area (220) through the Nowva manager (531). For example, the Nowva manager (531) can display a static notification widget in the widget area (220) if the static notification widget has a top card. For example, the Nowva manager (531) can display an ongoing activity widget in the widget area (220) if the ongoing activity widget has a top card.

[0164] FIG. 8 is a flowchart illustrating the operation of an electronic device (101) displaying a widget according to one embodiment.

[0165] FIG. 8 can be explained with reference to FIGS. 1 to 7.

[0166] The operations of FIG. 8 can be performed individually. For example, operations 820 and 821 are not performed after operations 810 and 811 of FIG. 8 have been performed. For example, operations 810 and 811, operations 820 and 821, and operations 830 and 831 can be performed individually. For example, operations 811, 821, and 831 can each be performed as each of operations 810, 820, and 830, which trigger operations 811, 821, and 831, is performed.

[0167] Referring to FIG. 8, in operation 810, the Nowva Card View Model (801) can identify that the AoD state has changed. In operation 811, the Nowva Card View Model (801) can refresh all views through the Nowva Card Stack View (802). For example, the stack structure for all views can be refreshed through the Nowva Card Stack View (802). In one embodiment, the views may represent UI objects within a widget. For example, the views may represent areas where icons, primary information, secondary information, and / or action buttons are displayed. For example, refreshing the views may include updating the display of areas corresponding to the views and / or the display of objects contained in the areas (e.g., icons, primary information, secondary information, and / or action buttons).

[0168] For example, the Nowva Card Stack View (802) can manage the order of applications in a stack structure. For example, the Nowva Card Stack View (802) can set the top card of applications that the user designates as important or frequently used. The Nowva Card Stack View (802) can dynamically change the stack structure (or top card) (or the order of widgets) according to the type of notification (or the type of application) (e.g., ongoing activity, or static notification).

[0169] For example, the Nowva Card Stack View (802) can create and / or refresh a stack structure based on ongoing activity data and static notification data delivered from the Notification Manager (532).

[0170] For example, the Nowva Card Stack View (802) may assign an ongoing activity as the first priority and static notifications as the second priority. For example, the Nowva Card Stack View (802) may display the widgets arranged in a stack according to priority, starting from the top. However, the embodiments are not limited thereto. In the case of a specific type of ongoing activity (e.g., the sports application (521)), the Nowva Card Stack View (802) may stop placing the ongoing activity at the top according to the notification of the ongoing activity. For example, in the case of the sports application (521), by stopping placing the ongoing activity at the top (or stopping assigning it as the first priority) according to the notification of the ongoing activity, the Nowva Card Stack View (802) may stop displaying notifications that occur during the game (e.g., score change notifications, foul occurrence notifications) as top cards.

[0171] In operation 820, the Nowva card view model (801) can identify that the positioning of the views is started and / or refreshed. For example, starting and / or refreshing the positioning of the views may include adjusting the display position of the views (or widgets). For example, starting and / or refreshing the positioning of the views may include adjusting the display position of the views (or widgets) according to a change in the size of the widgets.

[0172] In operation 821, the Nowva Card View model (801) can refresh all views through the Nowva Card Stack View (802). For example, the stack structure for all views can be refreshed through the Nowva Card Stack View (802).

[0173] In operation 830, the Nowva Card View model (801) can identify that an item is updated. In operation 831, the Nowva Card View model (801) can refresh all views through the Nowva Card Stack View (802). For example, the stack structure for all views can be refreshed through the Nowva Card Stack View (802). In operation 835, the Nowva Card Stack View (802) can display an animation. For example, if the top card changes, the Nowva Card Stack View (802) can display an animation for a widget indicating that the top card has changed.

[0174] In one embodiment, the Nowva card view model (801) and the Nowva card stack view (802) may be included in the Nowva manager (531).

[0175] FIG. 9 is a flowchart illustrating the operation of the notification manager (532) and the Nauba manager (531) of the electronic device (101) according to one embodiment.

[0176] FIG. 9 can be explained with reference to FIGS. 1 to 8.

[0177] In one embodiment, before the operations of FIG. 9 are performed, the electronic device (101) can check the initial state of the electronic device (101). For example, the notification manager (532) can manage a list of applications to be displayed on the home screen and filter ongoing activities to display an ongoing activity widget on the display (260). In one embodiment, the Nowva manager (531) can manage a list of applications to be displayed in the AoD state and manage ongoing activities and static notifications together.

[0178] Referring to FIG. 9, in operation 910, the notification manager (532) can identify a home screen application configuration request. For example, the home screen application configuration request may be a request for displaying the home screen.

[0179] In operation 911, the notification manager (532) can filter ongoing activity data. The notification manager (532) generates ongoing activity data by running applications installed on the electronic device (101). The notification manager (532) can process the generated ongoing activity data to generate data to be displayed on the home screen.

[0180] In operation 912, the notification manager (532) can display an application (or its ongoing activity widget) on the home screen. For example, the notification manager (532) can display an ongoing activity widget in the widget area (420) based on a priority determined by a stack structure.

[0181] In operation 913, the Nowva manager (531) can identify that it has transitioned to an AoD state (or, a locked state).

[0182] In operation 914, the notification manager (532) can transmit ongoing activity data to the Nowva manager (531). In one embodiment, the notification manager (532) can transmit data of the ongoing activity (e.g., key name) to the Nowva manager (531). For example, the key name may be a key name for an ongoing activity widget.

[0183] In action 915, the Nowva manager (531) can add static notification data. For example, the Nowva manager (531) can add static notification data to ongoing activity data.

[0184] In operation 916, the Nowva manager (531) can create a Nowva stack structure.

[0185] For example, the Nowva manager (531) can assign priority to each key name and create a stack structure according to the priority. For example, the Nowva manager (531) can assign priority to each key name so that it has a higher priority in the order of being most recently updated. For example, the Nowva manager (531) can assign priority to each key name so that if a certain amount of time has passed since the static notification was created, the priority of the static notification's key name is lowered.

[0186] For example, the Nowva Manager (531) can be configured so that the priority of the most recently executed application has top order. For example, the Nowva Manager (531) can be configured so that the priority of the most recently updated application has top order.

[0187] In operation 917, the Nowva manager (531) can display a Nowva. For example, the Nowva manager (531) can display a widget as a Nowva in the widget area (220).

[0188] FIG. 10 illustrates an operation in which an electronic device (101) changes the order of widgets according to one embodiment.

[0189] FIG. 10 can be explained with reference to FIGS. 1 to 9.

[0190] Referring to FIG. 10, widget (1011) is a top card, and widget (1012) may be the card following the top card. In state (1001), the electronic device (101) may display the widget (1011), which is the top card, in an enlarged widget area (423).

[0191] In one embodiment, the electronic device (101) may receive a request to change the order of the widgets (1011, 1012) while displaying the widget (1011) as a top card in an enlarged widget area (423). For example, the electronic device (101) may identify a request to change the order of the widgets (1011, 1012) based on a drag input (1013) for the widget (1011). However, the embodiment is not limited thereto. A request to change the order of the widgets (1011, 1012) may be generated based on user input for a button.

[0192] In one embodiment, the electronic device (101) can set the widget (1012) as the top card and set the widget (1011) as the card next to the top card via the notification manager (532) in response to a request to change the order of the widgets (1011, 1012). In state (1002), the electronic device (101) can display the widget (1012) that is the top card in the enlarged widget area (423) via the notification manager (532).

[0193] For example, the notification manager (532) can identify a list of ongoing activities currently displayed on the home screen. For example, the notification manager (532) can update data for Nowva items after a change in order (or a change in top card). For example, the notification manager (532) can generate a new list of key names that reflects the changed order. In one embodiment, the notification manager (532) can share the new list of key names with the Nowva manager (531).

[0194] FIG. 11 is a flowchart illustrating the operation of a notification manager (532) of an electronic device (101) changing the order of widgets according to one embodiment.

[0195] FIG. 11 may be described with reference to FIGS. 1 through 10. FIG. 11 may show an operation in which an electronic device (101) according to FIG. 10 changes the order of widgets.

[0196] Referring to FIG. 11, in operation 1111, the notification manager (532) can identify a request to change the order. For example, the notification manager (532) can receive a request to change the order of widgets (1011, 1012) while displaying widget (1011) as a top card in the enlarged widget area (423). For example, the notification manager (532) can identify a request to change the order of widgets (1011, 1012) based on a drag input (1013) for widget (1011).

[0197] In operation 1112, the notification manager (532) can process input events. For example, it can process a request to change the order.

[0198] In operation 1113, the notification manager (532) can update the key name list. For example, the notification manager (532) can update the key name list to set widget (1012) as the top card and widget (1011) as the card next to the top card in response to a request to change the order of widgets (1011, 1012).

[0199] In operation 1114, the notification manager (532) can display a home screen with the order changed. For example, the notification manager (532) can display a top card widget (1012) in an enlarged widget area (423).

[0200] FIG. 12 is a flowchart illustrating the operation of a notification manager (532) transmitting a key name to a Nowva manager (531) according to one embodiment.

[0201] FIG. 12 can be explained with reference to FIGS. 1 to 11.

[0202] Referring to FIG. 12, in operation 1211, the notification manager (532) can receive user input. In one embodiment, the notification manager (532) can identify user input for a change of order request.

[0203] In operation 1212, the notification manager (532) can deliver a list of changed key names to the Nowva manager (531). The notification manager (532) can deliver a Nowva item containing the list of changed key names to the Nowva manager (531). For example, the notification manager (532) can deliver a Nowva item containing a list of changed key names for an ongoing activity to the Nowva manager (531).

[0204] FIG. 13 illustrates an operation in which an electronic device (101) changes the order of widgets according to one embodiment.

[0205] FIG. 13 can be explained with reference to FIGS. 1 to 12.

[0206] Referring to FIG. 13, widget (1011) is a top card, and widget (1012) may be the card following the top card. In state (1301), the electronic device (101) may display the widget (1011), which is the top card, in an enlarged widget area (423).

[0207] In one embodiment, in state (1301), if there is no user input to the electronic device (101) for a specified period of time, or if a press input to the power button is received, the electronic device (101) may transition to a locked state. For example, in the locked state, the electronic device (101) may display a lock screen (or an AoD screen).

[0208] In one embodiment, the notification manager (532) may transmit to the Nowva manager (531) a Nowva item containing a list of key names indicating that the widget (1011) is the top card and the widget (1012) is the card next to the top card. For example, the notification manager (532) may transmit the Nowva item (or the key names of the top card) to the Nowva manager (531) via a specified definition language (e.g., Android interface definition language (AIDL)).

[0209] In one embodiment, the Nowva item may include notification identification information (e.g., a unique hash value possessed only by the ongoing activity), a card icon (e.g., an icon of the application displayed within the ongoing activity widget), primary information (e.g., primary information displayed in the ongoing activity widget), and / or secondary information (e.g., additional information displayed in the ongoing activity widget).

[0210] For example, the Nowva manager (531) can add static notification data to ongoing activity data containing Nowva items. The Nowva manager (531) can create a Nowva stack structure based on the data. For example, the Nowva manager (531) can assign a priority to each of the key names and create a stack structure based on the priority.

[0211] In one embodiment, the Nowva manager (531) can update the key name list to position a widget (1311) for static notifications between widget (1011) and widget (1012).

[0212] For example, the Nowva Manager (531) can be configured so that the priority of the most recently executed application has top order. For example, the Nowva Manager (531) can be configured so that the priority of the most recently updated application has top order.

[0213] In one embodiment, on an AoD screen (or lock screen), the electronic device (101) may display a widget (1011) as a top card in a widget area (220). At this time, the widget (1011) may be a top card, the widget (1311) may be a card next to the top card, and the widget (1012) may be a card next to the widget (1311).

[0214] FIG. 14 illustrates an operation in which a notification manager (532) of an electronic device (101) transmits a key name list to a Nauba manager (531) according to one embodiment.

[0215] FIG. 14 can be explained with reference to FIGS. 1 to 13.

[0216] Referring to FIG. 14, in operation 1411, the notification manager (532) can identify a request to change the order. For example, the notification manager (532) can receive a request to change the order of widgets (1011, 1012) while displaying widget (1011) as a top card in an enlarged widget area (423). For example, the notification manager (532) can identify a request to change the order of widgets (1011, 1012) based on a drag input (1013) for widget (1011).

[0217] In operation 1412, the notification manager (532) can update the key name list. For example, the notification manager (532) can update the key name list to set widget (1012) as the top card and widget (1011) as the card next to the top card in response to a request to change the order of widgets (1011, 1012).

[0218] In operation 1413, the notification manager (532) may transmit a list of key names to the Nauba manager (531). For example, the notification manager (532) may transmit a list of key names containing the key names of top cards to the Nauba manager (531) via a specified definition language (e.g., AIDL).

[0219] In operation 1414, the Nowva Manager (531) can verify and store data. For example, the Nowva Manager (531) can ensure data integrity and user experience through structuring the data (e.g., creating a stack structure) and / or verification. For example, the Nowva Manager (531) can store the verified data within an area of ​​memory (130) managed by the Nowva Manager (531). In one embodiment, the verification of data may include the Nowva Manager (531) checking a list of key names of an ongoing activity, comparing static notification data with the merged order, and determining whether the merged order matches. In one embodiment, the Nowva Manager (531) can modify the merged order if the merged order does not match.

[0220] FIG. 15 illustrates an operation in which a notification manager (532) of an electronic device (101) transmits a key name list to a Nowva manager (531) according to one embodiment. FIG. 16 illustrates an item list of the Nowva manager (531) of an electronic device (101) according to one embodiment.

[0221] FIGS. 15 and 16 can be explained with reference to FIGS. 1 to 14.

[0222] Referring to FIG. 15, in operation 1511, the notification manager (532) can pass a list of key names to the Nowva manager (531). For example, the Nowva manager (531) can parse the data to extract the list of key names. For example, the Nowva manager (531) can extract a list of key names for ongoing activities (e.g., ["Clock App", "Health"]).

[0223] In operation 1512, the Nowva manager (531) can prepare ongoing activity data. The Nowva manager (531) can create ongoing activity data (or, a stack structure) containing Nowva items.

[0224] In action 1513, the Nowva manager (531) can add static notification data. For example, the Nowva manager (531) can add static notification data to ongoing activity data. For example, the Nowva manager (531) can add a list of key names for static notifications (e.g., ["Media"]) to a list of key names for ongoing activities (e.g., ["Watch App", "Health"]).

[0225] Referring to FIG. 16, the item list (1610) may include one or more Nowva items. The Nowva items may include notification identification information (e.g., a unique hash value that only the ongoing activity has), a card icon (e.g., an icon of the application displayed within the ongoing activity widget), primary information (e.g., primary information displayed in the ongoing activity widget), and / or secondary information (e.g., additional information displayed in the ongoing activity widget).

[0226] In operation 1514, the Nowva manager (531) can identify that the device has been switched to a locked state. For example, the electronic device (101) can detect a user switching action. For example, the electronic device (101) can identify that the electronic device (101) has been switched from an unlocked state to a locked state. For example, the electronic device (101) can identify that the electronic device (101) has been switched from an unlocked state to a locked state according to a specified switching condition. For example, the specified switching condition may be determined to be satisfied if the electronic device (101) has not been used for a certain period of time, or if a press input is received on the power button.

[0227] In operation 1515, the Nowva manager (531) can initialize and sort the Nowva stack. For example, the Nowva manager (531) can determine the display order of the Nowva. For example, the Nowva manager (531) can assign priority to each of the key names and initialize and create the stack structure according to the priority.

[0228] In operation 1516, the Nowva manager (531) can display an AoD screen. For example, the Nowva manager (531) can display an AoD screen (or lock screen) based on data sorted according to a stack structure. For example, the Nowva manager (531) can display an AoD screen (or lock screen) according to a display order (e.g., "Clock app (top)", "Media", "Health"]).

[0229] FIG. 17 illustrates an operation in which a notification manager (532) of an electronic device (101) transmits a key name list to a Nowva manager (531) according to one embodiment. FIG. 18 illustrates an operation in which an electronic device (101) changes the order of widgets according to one embodiment.

[0230] FIGS. 17 and FIGS. 18 can be explained with reference to FIGS. 1 to 16.

[0231] Referring to FIG. 17, in operation 1711, the notification manager (532) can transmit ongoing activity data to the Nowva manager (531). The notification manager (532) can transmit ongoing activity data including a list of key names to the Nowva manager (531).

[0232] In operation 1712, the Nowva manager (531) can load static notification data. The Nowva manager (531) can load a list of key names for static notifications (e.g., ["media"]) from an area within memory (130) managed by the Nowva manager (531).

[0233] In action 1713, the Nowva manager (531) can merge ongoing activity data and static notification data. For example, the Nowva manager (531) can add static notification data to the ongoing activity data.

[0234] In operation 1714, the Nowva manager (531) can initialize and sort the Nowva stack. For example, the Nowva manager (531) can determine the display order of the Nowva. For example, the Nowva manager (531) can assign priority to each of the key names and initialize and create the stack structure according to the priority.

[0235] Referring to FIG. 18, widget (1012) is the top card, widget (1011) is the card next to the top card, and widget (1311) may be the card next to widget (1011).

[0236] In operation 1715, the Nowva manager (531) can display the Nowva. For example, the Nowva manager (531) can display an AoD screen (or lock screen) based on data sorted according to a stack structure.

[0237] For example, the electronic device (101) can identify that the priority changes according to a real-time update for the widget (1012) while displaying the top card widget (1011) in the widget area (220) in the state (1302) of FIG. 13. Accordingly, in the state (1801), the electronic device (101) can display the top card widget (1012) in the widget area (220).

[0238] According to an embodiment, the electronic device (101) can add a new notification of an application to the list of key names for Nowva via the Nowva manager (531) when the notification arrives. According to an embodiment, the electronic device (101) can remove the key name of the terminated ongoing activity from the list of key names via the Nowva manager (531) when the ongoing activity is terminated.

[0239] FIG. 19 illustrates the operation in which a Nauba manager (531) of an electronic device (101) transmits a key name list to a notification manager (532) according to one embodiment.

[0240] FIG. 19 can be explained with reference to FIGS. 1 to 18.

[0241] Referring to FIG. 19, in operation 1911, the notification manager (532) can transmit key name list data to the Nowva manager (531). For example, the Nowva manager (531) can parse the data to extract the key name list. For example, the Nowva manager (531) can extract a key name list for ongoing activities (e.g., ["Clock App", "Health"]).

[0242] In operation 1912, the Nowva manager (531) can load static notification data. The Nowva manager (531) can load a list of key names for static notifications (e.g., ["media"]) from an area within memory (130) managed by the Nowva manager (531).

[0243] In operation 1913, the Nowva manager (531) can merge ongoing activity data and static notification data. For example, the Nowva manager (531) can add static notification data to the ongoing activity data.

[0244] In operation 1914, the Nauba manager (531) may receive a screen activation request. For example, the screen activation request may be generated by a tap input (or double tap input) on the display (260), or by a press input on the power button.

[0245] In operation 1915, the Nowva manager (531) can display the Nowva. For example, the Nowva manager (531) can display the Nowva using the Nowva stack after initializing and sorting the Nowva stack.

[0246] For example, the Nauba Manager (531) can generate cards for each of the applications based on data about the Nauba item (e.g., for the watch application (511), "Timer - Time remaining: 15 minutes", for the media application (553), "Song title: AAA, Artist: BBB", for the health application, "Exercise distance: 3 km, Calories burned: 200 kcal").

[0247] For example, the Nowva Manager (531) can insert icons and data for each application into each application's card. For example, the Nowva Manager (531) can insert "Timer - Time remaining: 15 minutes" into the card of the clock application (511).

[0248] For example, the Nowva manager (531) can display the cards in stack order. For example, if the card of the clock application (511) is the top card, the Nowva manager (531) can display the card of the clock application (511) as a widget in the widget area (220, 223).

[0249] FIG. 20 illustrates the operation of a notification manager (532) of an electronic device (101) displaying a Nowbar according to one embodiment.

[0250] FIG. 20 can be explained with reference to FIGS. 1 to 19.

[0251] Referring to FIG. 20, in operation 2011, the application (146) can identify an application execution request.

[0252] In operation 2012, the application (146) can request the notification manager (532) to register a notification.

[0253] In operation 2013, the notification manager (532) can transmit notification information to the Nowva manager (531). The notification manager (532) can transmit a Nowva item for the application that generated the notification information to the Nowva manager (531).

[0254] In operation 2014, the Nowva manager (531) can display a notification. For example, the Nowva manager (531) can add notification information received from the notification manager (532) to a Nowva item and display a widget representing the notification based on a list of key names for the Nowva item.

[0255] In operation 2015, the Nowva manager (531) can identify a reorder request. For example, the Nowva manager (531) can identify a reorder request based on user input to change the priority of a widget.

[0256] In operation 2016, the Nowva manager (531) may request the changed order from the notification manager (532). In operation 2017, the notification manager (532) may transmit the changed order notification information to the Nowva manager (531).

[0257] In operation 2018, the Nowva manager (531) can display out-of-order notifications. For example, the Nowva manager (531) can display out-of-order notifications based on an updated list of key names received from the notification manager (532).

[0258] Below, according to an example of a specific application, the operation of registering a notification and displaying a widget corresponding to the notification is described. Operations 2019 to 2021, operations 2022 to 2024, and operations 2015 to 2027 may not be performed sequentially. For example, operations 2019 to 2021 are performed only in accordance with an event for the sports application (521), and operations 2022 to 2024 and operations 2015 to 2027 are not performed sequentially after operations 2019 to 2021 are performed.

[0259] In operation 2019, the sports application (521) can identify requests for matches of interest. For example, the sports application (521) can identify requests for matches of interest for a preferred team based on the user registering a preferred team.

[0260] In operation 2020, the sports application (521) can provide match information to the Nauba Manager (531). In operation 2021, the Nauba Manager (531) can display match information.

[0261] For example, the display of match information may include displaying information indicating the start of the match as a widget, displaying information during the progress of the match as a widget, and displaying information after the completion of the match as a widget.

[0262] In operation 2022, the map application (523) can identify appointments. For example, the map application (523) can identify schedule data (e.g., location, time, schedule content, participants) of a user registered in the calendar DB (2221 in FIG. 22). In one embodiment, the electronic device (101) can propose providing a notification to the Nowva manager (531) via a smart proposal (2223 in FIG. 22) based on the location of the electronic device (101) and the current time via a location sensor (2222 in FIG. 22). In one embodiment, the Nowva manager (531) can request information about the identified appointments from the map application (523).

[0263] In operation 2023, the map application (523) can provide appointment information to the Nowva manager (531). The map application (523) can provide the Nowva manager (531) with information regarding the travel route, the time to depart, and / or the time required to travel, for moving from the current location to a place (or destination) according to the schedule data.

[0264] In operation 2024, the Nowva manager (531) can display appointment information as a widget.

[0265] For example, the display of appointment information may include displaying, as a widget, the time to depart from the current location to the destination according to the appointment information (e.g., pre-ongoing activity), displaying as a widget the travel route from the current location to the destination (e.g., ongoing activity), and displaying as a widget the estimated time of arrival at the destination (e.g., post-ongoing activity).

[0266] In operation 2025, the delivery application (2001) can identify an order. In operation 2026, the delivery application (2001) can provide order information to the Nowva manager (531). In operation 2027, the Nowva manager (531) can display the order information as a widget.

[0267] For example, the display of order information may include displaying information as a widget indicating that an order has been received (or is being prepared for delivery) (or is being cooked) (e.g., a pre-ongoing activity), displaying as a widget the estimated time of arrival from the delivery person's current location to the destination (e.g., an ongoing activity), and displaying as a widget information indicating that the delivery is ready to be received (e.g., a post-ongoing activity).

[0268] In operation 2028, the Nowva Manager (531) can perform information provision and updates. For example, the Nowva Manager (531) can update ongoing activities based on data received from applications.

[0269] In one embodiment, the Nowva manager (531) can display a widget in a post-ongoing activity state in the widget area (220) for a specified time (e.g., 30 minutes) (or until a widget according to another notification is displayed).

[0270] In one embodiment, the Nowva manager (531) may display a widget (e.g., a widget displaying match information) in the widget area (220) even after a specified time (e.g., 30 minutes) until a specified condition is met. For example, the Nowva manager (531) may display the widget in the widget area (220) until a specified condition is met to determine that the user has recognized the widget. For example, the Nowva manager (531) may display the widget in the widget area (220) until a specified condition is met if the widget (e.g., a widget displaying match information) is a top card. For example, the Nowva manager (531) may store information of the widget in an area allocated within memory (130) and display the stored information in the widget area (220). Displaying the stored information in the widget area (220) may include displaying the information stored in the widget area (220) through a widget that generated the information (e.g., a sports application (521)). Displaying the stored information in the widget area (220) may include displaying the information stored in the widget area (220) through another widget (e.g., a widget of Now Brief (533)) instead of the widget that generated the information (e.g., a widget of the sports application (521)).

[0271] For example, a specified condition may be determined to be satisfied if, when the time at which the widget transitions to a post-ongoing activity (e.g., when the game ends in the case of sports) (hereinafter referred to as the transition time) is early morning (or the user's sleep time), a specified time (e.g., 12 hours) has elapsed from the transition time.

[0272] For example, a specified condition may be determined to be satisfied if, at the time of switching, the mode of the electronic device (101) is a specified mode (e.g., Do Not Disturb mode, or sleep mode), and a specified time (e.g., 12 hours) has elapsed from the time of switching.

[0273] For example, if the electronic device (101) is locked at the time of switching, the specified condition may be determined to be satisfied after a specified time (e.g., 12 hours) has elapsed from the time of switching.

[0274] For example, a specified condition may be determined to be satisfied if, even before a specified time (e.g., 12 hours) has elapsed, the electronic device (101) is unlocked, or if another specified time (e.g., 30 minutes) has elapsed after the electronic device (101) is unlocked.

[0275] For example, a specified condition may be determined to be satisfied even before a specified time (e.g., 12 hours) has elapsed, if user interaction with a widget of the electronic device (101) (e.g., tap input, swipe input on the widget) is identified.

[0276] For example, a specified condition may be determined to be satisfied if another time (e.g., 4 hours) has elapsed from the point in time when the user of the electronic device (101) is identified as having woken up, even before a specified time (e.g., 12 hours) has elapsed.

[0277] FIG. 21 is a drawing illustrating the operation of displaying an ongoing activity widget of sports according to one embodiment.

[0278] FIG. 21 can be explained with reference to FIGS. 1 to 20.

[0279] In one embodiment, a sports application (521) may request an application search (591) to create (or update) an application search database (DB) (2121). To do this, in operation 2111, the sports application (521) may request the application search (591) to create an application search DB (2121). In operation 2116, the application search (591) may notify the sports application (521) of the creation of the application search DB (2121).

[0280] In operation 2112, the application search (591) can open a connection (or session (2125)) between the created application search DB (2121) and the sports application (521). In operation 2113, during the session (2125), the sports application (521) can set the schema (2122) of the application search DB (2121) (or create a schema type (2123)). In operation 2114, during the session (2125), the sports application (521) can input a document (2124) into the application search DB (2121) based on its own document (2126). In operation 2115, during the session (2125), the sports application (521) can search in the application search DB (2121).

[0281] In one embodiment, the application search (591) can generate data for a notification based on the document (2124) and register it as an ongoing activity in the AoD application (522). The notification manager (532) can deliver the ongoing activity to the Nowva manager (531) as a Nowva item. Accordingly, the Nowva manager (531) can display a widget in the widget area (220) according to the status of the registered ongoing activity.

[0282] FIG. 22 is a diagram illustrating the operation of an electronic device displaying an ongoing activity widget according to a schedule registered in a calendar DB (2221) according to one embodiment.

[0283] FIG. 22 can be explained with reference to FIGS. 1 to 21.

[0284] In one embodiment, the electronic device (101) can identify the schedule data of a user registered in the calendar DB (2221) (e.g., location, time, schedule content, participants) through a smart suggestion (2223). In one embodiment, the electronic device (101) can propose the provision of a notification to the Nowva Manager (531) through a smart suggestion (2223) based on the location of the electronic device (101) and the current time through a location sensor (2222). In one embodiment, the electronic device (101) can provide the Nowva Manager (531) with a Nowva item to display a widget containing information on a travel route to move from the current location to a place (or destination) according to the schedule data, the time to depart, and / or the time required to travel, through a smart suggestion (2223). Subsequently, the Nowva Manager (531) can display an ongoing activity widget based on the Nowva item.

[0285] FIG. 23 is a drawing illustrating an operation in which an electronic device of a widget improves visibility according to one embodiment. FIG. 24 to 26 are drawings illustrating a widget with improved visibility.

[0286] FIGS. 23 to 26 can be explained with reference to FIGS. 1 to 22.

[0287] In one embodiment, the Nowva manager (531) can improve the visibility of a widget by changing the color of the widget according to the saturation and / or brightness of the wallpaper on the lock screen of the electronic device (101). For example, a widget displayed in the widget area (420) within the home screen and a widget displayed in the widget area (220) within the lock screen (or AoD screen) may have the same content. For example, in the case of a widget displayed in the widget area (420) within the home screen, the electronic device (101) can ensure visibility by displaying the background and / or content in a different color depending on whether the context of the electronic device (101) indicates dark mode. For example, in the case of a widget displayed in a widget area (220) within a lock screen (or AoD screen), the electronic device (101) can ensure visibility by determining the background color based on the saturation and / or brightness of the wallpaper rather than the color applied to the widget area (420) within the home screen, and displaying the content in a single color (e.g., white) in response.

[0288] Referring to FIG. 23, in operation 2311, the Nowva manager (531) can identify the lock screen. For example, the Nowva manager (531) can identify the wallpaper of the lock screen displayed in the lock state.

[0289] In operation 2312, the Nowva manager (531) can determine whether the saturation and brightness of the lock screen (or wallpaper) each have a first saturation and a first brightness. For example, the first saturation may have a range of 68 to 100 within a total saturation range of 0 to 100. For example, the first brightness may have a range of 0 to 79 within a total brightness range of 0 to 100.

[0290] In operation 2313, the Nowva manager (531) can display a widget with a first color tone. For example, the first color tone may have a saturation of 86 and a brightness of 48. For example, as in the state (2401) of FIG. 24, the Nowva manager (531) can display a widget with a first color tone so that the color tone of the widget corresponds to the color tone of the wallpaper.

[0291] In operation 2314, the Nowva manager (531) can determine whether the saturation and brightness of the lock screen (or wallpaper) each have a second saturation and a second brightness. For example, the second saturation may have a range of 0 to 67 within a total saturation range of 0 to 100. For example, the second brightness may have a range of 80 to 100 within a total brightness range of 0 to 100.

[0292] In operation 2315, the Nowva manager (531) can display the widget with a second color tone. For example, the second color tone may have a saturation of 33 and a brightness of 96. For example, as in the state (2402) of FIG. 24, the Nowva manager (531) can display the widget with a second color tone so that the color tone of the widget corresponds to the color tone of the wallpaper.

[0293] In operation 2316, the Nowva manager (531) can display the widget with a third color tone. For example, the third color tone may have a saturation of 64 and a brightness of 60. For example, as in the state (2403) of FIG. 24, the Nowva manager (531) can display the widget with a third color tone so that the color tone of the widget corresponds to the color tone of the wallpaper.

[0294] According to an embodiment, the Nowva Manager (531) can ensure the visibility of text on a widget of a specific color (e.g., white) by applying a dark blur to a bright wallpaper and a bright blur to a dark wallpaper in dark mode.

[0295] For example, in the state (2501) of FIG. 25, the Nowva manager (531) can apply a relatively dark blur to the widget when the dark mode setting value (e.g., darkamount) is 0. For example, in the state (2502) of FIG. 25, the Nowva manager (531) can apply a relatively bright blur to the widget when the dark mode setting value (e.g., darkamount) is 1.

[0296] According to an embodiment, the Nowva manager (531) can set the color of the icon displayed in the widget area (420, 423) of the notification manager (532) so that the color of the icon displayed in the widget area (220, 223) corresponds to the color of the icon displayed in the widget area (420, 423) of the notification manager (532).

[0297] For example, in the state (2601) of FIG. 26, the color of the widget (2610) (or the icon within the widget (2610)) of the enlarged widget area (423) displayed by the notification manager (532) may be the same as the color of the icon (2621) within the widget of the widget area (220) displayed by the Nowva manager (531) in the state (2602) of FIG. 26. For example, in the state (2602) of FIG. 26, the color of the background area (2625) within the widget of the widget area (220) displayed by the Nowva manager (531) may be the same as the color of the wallpaper (2623) within the background area (210).

[0298] FIGS. 27a and FIGS. 27b are drawings illustrating an operation to change the display of another object so as not to overlap when an electronic device displays an enlarged widget according to one embodiment.

[0299] FIGS. 27a and FIGS. 27b can be explained with reference to FIGS. 1 through 26.

[0300] In one embodiment, in the state (2701) of FIG. 27a, UI objects (2711, 2712) can be displayed within the lock screen in the locked state of the electronic device (101). In one embodiment, the first layer of the widget (220) in the reduced state and the second layer of the UI objects (2711, 2712) may be different from each other.

[0301] In one embodiment, in the state (2702) of FIG. 27a, in response to an input to enlarge the reduced widget (220), the electronic device (101) may further display a UI (2713) that displays additional information about the widget along with the enlarged widget (223). In this case, if the display of UI objects (2711, 2712) is maintained, the UI objects (2711, 2712) displayed on the second layer may be exposed through areas (2714, 2715) surrounding the UI (2713). In this case, the user experience of receiving the UI (2713) that displays additional information about the widget along with the enlarged widget (223) may be degraded. Accordingly, in order to minimize the degradation of the user experience, in response to an input to enlarge the reduced widget (220) in state (2702), the electronic device (101) may stop displaying at least some of the UI objects (2711, 2712) that overlap with the enlarged widget and / or additional information displayed with the enlarged widget in the UI (2713).

[0302] In one embodiment, in the state (2703) of FIG. 27b, a UI object (2721) may be displayed within the lock screen while the electronic device (101) is in a locked state. In one embodiment, in the state (2704) of FIG. 27b, in response to an input to enlarge a collapsed widget (220), the electronic device (101) may further display a UI (2713) that displays additional information about the widget along with the enlarged widget (223). According to an embodiment, in the state (2704) of FIG. 27b, the electronic device (101) may display a collapsed UI object (2722) from the UI object (2721) in an area that does not overlap with the enlarged widget (223) and / or the UI (2713) that displays additional information about the widget, in order to maintain the display of information displayed through the UI object (2721) that displays essential information.

[0303] FIG. 28 is a diagram illustrating an operation of displaying a widget according to the position of a fingerprint sensor of an electronic device according to one embodiment.

[0304] FIG. 28 can be explained with reference to FIGS. 1 to 27b.

[0305] FIG. 28 illustrates an example in which the electronic device (101) displays a widget when the position of the sensor for acquiring biometric information (e.g., fingerprint) of the electronic device (101) is located relatively lower.

[0306] For example, referring to the state (2801, 2802) of FIG. 28, the electronic device (101) may display a visual object (213) below the widget area (2820). For example, the electronic device (101) may display the visual object (213) below the widget area (2820) as the position of the sensor for acquiring biometric information (e.g., fingerprint) is located relatively lower. For example, the electronic device (101) may display the visual object (213) below the widget area (2820) when it is configured to use biometric information (e.g., fingerprint) for user authentication to unlock the electronic device (101).

[0307] Referring to the state (2803) of FIG. 28, the electronic device (101) can display a widget in an enlarged widget area (223) based on input to the widget area (220) while in a locked state.

[0308] Referring to the state (2804) of FIG. 28, the electronic device (101) can arrange the widget area (220) alongside the icon areas (230, 240) of the lock screen (2810) when locked. For example, the electronic device (101) can arrange the widget area (220) alongside the icon areas (230, 240) of the lock screen (2810) when it is configured not to use biometric information (e.g., fingerprint) for user authentication to unlock the electronic device (101).

[0309] FIG. 29 is a diagram illustrating an operation of displaying a notification related to the battery of an electronic device through a widget according to one embodiment.

[0310] FIG. 29 can be explained with reference to FIGS. 1 to 28.

[0311] The states (2901 to 2905) of FIG. 29 may represent UIs that indicate information about the battery status displayed by the electronic device (101).

[0312] For example, in state (2901), the electronic device (101) may display a widget in the widget area (220) that includes information indicating that the battery is charging and information indicating the state of charge (SoC). For example, while the electronic device (101) is displaying a widget containing information about the battery in the widget area (220), it may receive an input to display the widget in the enlarged widget area (223). For example, in response to receiving an input to display the widget in the enlarged widget area (223), the electronic device (101) may display a widget that displays detailed information about the battery in the enlarged widget area (223) (e.g., state (2803) of FIG. 28).

[0313] For example, in state (2902), the electronic device (101) may display a widget in the widget area (220) to indicate an abnormality regarding the battery. According to an embodiment, to indicate an abnormality regarding the battery in more detail, the electronic device (101) may display additional information in addition to the widget.

[0314] For example, in state (2903), the electronic device (101) may display a widget (2910) for notifying of an abnormality regarding the battery and a UI object (2911) indicating the type of abnormality. In one embodiment, the widget (2910) may be displayed on the widget area (220), and the UI object (2911) indicating the type of abnormality may be displayed on the widget area (220).

[0315] For example, in state (2904), the electronic device (101) may display a widget (2920) for indicating an abnormality regarding the battery and UI objects (2921, 2922) representing two or more types. In one embodiment, the widget (2920) may be displayed on the widget area (220), and among the UI objects (2921, 2922) representing the abnormality types, the UI object (2921) may be displayed on the widget area (220), and the UI object (2922) may be displayed between the widget (2920) and the UI object (2921).

[0316] For example, in state (2905), the electronic device (101) may display a widget (2930) for indicating the state of the battery, UI objects (2931, 2932) representing two or more types, and a text message (2933) representing the above. In one embodiment, the widget (2930) may be displayed on the widget area (220), and among the UI objects (2931, 2932) representing two or more types, the UI object (2931) may be displayed on the widget area (220), and the UI object (2932) may be displayed between the widget (2930) and the UI object (2931).

[0317] FIG. 30 is a flowchart illustrating the operation of an electronic device initializing a Nauba according to one embodiment.

[0318] FIG. 30 can be described with reference to FIG. 1 through 29. The operations of FIG. 30 can be performed when the Nowva is initialized.

[0319] In one embodiment of FIG. 30, the Nowva Item Manager (3002), Nowva Controller (3003), and Nowva Card View Model (801) may be included in the Nowva Manager (531).

[0320] Referring to FIG. 30, in operation 3011, the plugin face widget manager (3001) can send an initialization command (init()) to the notification manager (532). In accordance with the initialization command (init()), the Nowva manager (531) can update Nowva items for the ongoing activity.

[0321] In operation 3012, the notification manager (532) may send a notification (onNowBarItemUpdated()) to the NowBar Item manager (3002) indicating that a NowBar item has been updated. The notification (onNowBarItemUpdated()) may contain data about the updated NowBar items for the ongoing activity.

[0322] In operation 3013, the Nowva item manager (3002) can send a request to update a Nowva item (update()) to the Nowva controller (3003). The Nowva controller (3003) can update the Nowva items. For example, the Nowva controller (3003) can update Nowva items for an ongoing activity and a static notification.

[0323] In operation 3014, the Nowva controller (3003) can send a request to update the Nowva (updateView()) to the Nowva card view model (801). For example, the Nowva card view model (801) can display the widget of the application with the highest priority in the widget area according to the updated Nowva item.

[0324] FIG. 31 is a flowchart illustrating the operation of an electronic device receiving an ongoing activity according to one embodiment.

[0325] FIG. 31 can be described with reference to FIG. 1 through 30. The operations of FIG. 31 can be performed when an ongoing activity is created.

[0326] Referring to FIG. 31, in operation 3111, the notification collection (3101) can send a message (onEntryUpdated()) to the ongoing activity controller (3102) indicating that a notification has been registered. In accordance with the message (onEntryUpdated()), the ongoing activity controller (3102) can register an ongoing activity.

[0327] In operation 3112, the ongoing activity controller (3102) can send a notification (notifyUpdatedObservers()) to the ongoing activity data helper (3103) indicating an observation of the ongoing activity registered therein. The ongoing activity data helper (3103) can update the Nowva items for the ongoing activity.

[0328] In operation 3113, the ongoing activity data helper (3103) can send a notification (notifyUpdatedNowBarItems()) of the update of NowBar items to the face widget notification controller wrapper (3104).

[0329] In operation 3114, the face widget notification controller wrapper (3104) can send a notification (onNowBarItemUpdated()) of an update to a NowBar item to the notification manager (532).

[0330] In operation 3115, the notification manager (532) can send a notification (onNowBarItemUpdated()) of an update to a NowBar item to the NowBar item manager (3002).

[0331] In operation 3116, the Nowva item manager (3002) can send a request to update a Nowva item (update()) to the Nowva controller (3003). The Nowva controller (3003) can update the Nowva items. For example, the Nowva controller (3003) can update Nowva items for ongoing activities and static notifications. Afterward, the Nowva controller (3003) can send a request to update a Nowva item (updateView()) to the Nowva card view model (801). For example, the Nowva card view model (801) can display the widget of the application with the highest priority in the widget area according to the updated Nowva item.

[0332] FIG. 32 is a flowchart illustrating the operation of an electronic device displaying a battery status according to one embodiment.

[0333] FIG. 32 can be described with reference to FIG. 1 through 31. The operations of FIG. 32 may be performed when a battery state is changed (e.g., start of charging, or end of charging).

[0334] Referring to FIG. 32, in operation 3211, the AoD battery manager (3201) can send a notification (onBatteryChanged()) to the Nauba item manager (3002) indicating that the battery status has changed.

[0335] In operation 3212, the Nowva item manager (3002) can refresh (refreshBatteryItem()) (or update) the Nowva item for the battery upon notification (onBatteryChanged()).

[0336] In operation 3213, the NowBar item manager (3002) can generate a notification (onNowBarItemUpdated()) indicating that the NowBar item for the battery has been updated as the refresh (refreshBatteryItem()) (or update) of the NowBar item for the battery is completed.

[0337] In operation 3214, the Nowva item manager (3002) can send a request (update()) to the Nowva controller (3003) to update the Nowva items. The Nowva controller (3003) can update the Nowva items. For example, the Nowva controller (3003) can update the Nowva items for an ongoing activity and a static notification.

[0338] In operation 3215, the Nowva controller (3003) can send a request (updateView()) to the Nowva card view model (801) to update the Nowva. For example, the Nowva card view model (801) can display the widget of the application with the highest priority in the widget area according to the updated Nowva item.

[0339] FIG. 33 is a flowchart illustrating the operation of an electronic device updating contact info according to one embodiment.

[0340] FIG. 33 can be described with reference to FIG. 1 through 32. The operations of FIG. 33 can be performed when contact info is updated.

[0341] Referring to FIG. 33, in operation 3311, the plug-in key guard status view (3301) can send a notification (onStartedWakingUp()) for waking up to the face widget view model (3302).

[0342] In operation 3312, the face widget view model (3302) can request the Nowva controller (3003) to switch to a charging-only mode (setChargingOnlyMode()).

[0343] In operation 3313, the Nowva controller (3003) may request the Nowva item manager (3002) to switch to a charging-only mode (setChargingOnlyMode()). The Nowva item manager (3002) may switch to a charging-only mode.

[0344] In operation 3314, the Nowva item manager (3002) can send a request (update()) to the Nowva controller (3003) to update the Nowva items. The Nowva controller (3003) can update the Nowva items.

[0345] In operation 3315, the Nowva controller (3003) can send a request (updateView()) to the Nowva card view model (801) to update the Nowva. For example, the Nowva card view model (801) can display the widget of the application with the highest priority in the widget area according to the updated Nowva item.

[0346] FIG. 34 is a flowchart illustrating the operation of an electronic device displaying media according to one embodiment.

[0347] FIG. 34 can be described with reference to FIG. 1 through 33. The operations of FIG. 34 may be performed when a notification is generated for the media being played.

[0348] Referring to FIG. 34, in operation 3411, the media data manager (3401) may send a message (onMediaDataLoaded()) to the ongoing activity controller (3102) indicating that media data has been loaded (or that media playback has been requested). In accordance with the message (onMediaDataLoaded()), the ongoing activity controller (3102) may register an ongoing activity.

[0349] In operation 3412, the ongoing activity controller (3102) can send a notification of the update of NowBar items (notifyUpdatedNowBarItems()) to the face widget notification controller wrapper (3104). For example, the ongoing activity controller (3102) sends a notification (notifyUpdatedObservers()) indicating an observer for the registered ongoing activity, and the ongoing activity data helper (3103) updates the NowBar items for the ongoing activity, and then the ongoing activity data helper (3103) can send a notification of the update of NowBar items (notifyUpdatedNowBarItems()) to the face widget notification controller wrapper (3104).

[0350] In operation 3413, the face widget notification controller wrapper (3104) can send a notification (onNowBarItemUpdated()) of an update to a NowBar item to the notification manager (532).

[0351] In operation 3414, the notification manager (532) can send a notification (onNowBarItemUpdated()) of an update to a NowBar item to the NowBar item manager (3002).

[0352] In operation 3415, the Nowva item manager (3002) may send a request (update()) to the Nowva controller (3003) to update the Nowva items. The Nowva controller (3003) may update the Nowva items. For example, the Nowva controller (3003) may update Nowva items for ongoing activities and static notifications. Afterward, the Nowva controller (3003) may send a request (updateView()) to the Nowva card view model (801) to update the Nowva. For example, the Nowva card view model (801) may display the widget of the application with the highest priority in the widget area according to the updated Nowva items.

[0353] FIG. 35 is a flowchart illustrating the operation of an electronic device expanding a nauba according to one embodiment.

[0354] FIG. 35 can be described with reference to FIG. 1 through 34. The operations of FIG. 35 can be performed when an input for changing the size of a widget is received.

[0355] Referring to FIG. 35, in operation 3511, the Nowva card stack view (802) can receive a message (onClick()) indicating that an input has been received.

[0356] In operation 3512, the Nowva Card Stack View (802) may send a request (updateNowBarState()) to update the state of a widget in response to a message (onClick()) notifying the Nowva Card View Model (801) that input has been received. For example, the Nowva Card View Model (801) may, in response to the request (updateNowBarState()), display a widget displayed in the widget area (220) in the enlarged widget area (223), or display a widget displayed in the enlarged widget area (223) in the widget area (220).

[0357] In operation 3513, the Nowva card view model (801) can send a notification (onChanged()) to the Nowva extended card view observer (3501) indicating that the widget area where the widget is displayed has changed.

[0358] FIG. 36 is a flowchart illustrating the operation of an electronic device switching to a lock screen according to one embodiment.

[0359] FIG. 36 can be described with reference to FIG. 1 through 35. The operations of FIG. 36 may be performed when the electronic device (101) switches to displaying an AoD screen (or lock screen) while displaying a home screen (or, application screen).

[0360] In operation 3611, AoD Ex (3601) can identify that the display of AoD has started based on a message (e.g., onStartAODAfterRotation()). In operation 3612, AoD Ex (3601) can request the current state (requestState()) to the AoD state machine (3602) based on that the display of AoD has started.

[0361] In operation 3613, the AoD state machine (3602) can send a message (transitionTo()) requesting a state transition to the AoD UI controller (3603) according to the state (requestState()).

[0362] In operation 3614, the AoD UI controller (3603) can execute an instruction (attachAODView()) to display an AoD view (or widget) according to the message (transitionTo()).

[0363] In operation 3615, the AoD UI controller (3603) can request the AoD state (requestAODState()) to the face widget controller (3604). In operation 3616, the face widget controller (3604) can request the AoD state (requestAODState()) to the face widget view model (3302). In operation 3617, the face widget view model (3302) can request the AoD state (requestAODState()) to the Nowva controller (3003).

[0364] FIGS. 37 and 38 are flowcharts illustrating the operation of an electronic device switching to dark mode according to one embodiment.

[0365] FIGS. 37 and FIGS. 38 may be described with reference to FIGS. 1 through 36. The operations of FIGS. 37 and FIGS. 38 may be performed when the electronic device (101) is switched to dark mode.

[0366] In operation 3711, the view system (3701) may send a notification (onConfigurationChanged()) to the face widget view model (3302) indicating that the settings have been changed. In one embodiment, the notification (onConfigurationChanged()) may indicate a transition from normal mode (or light mode) to dark mode. For example, dark mode may be a screen mode that displays white text on a screen (or dark screen) having a relatively dark color tone.

[0367] In operation 3712, the face widget view model (3302) can send a notification (onConfigurationChanged()) to the Nowva controller (3003).

[0368] In operation 3713, the Nowva controller (3003) can send a notification (onConfigurationChanged()) to the Nowva card view model (801).

[0369] In operation 3714, the Nowbar card view model (801) can refresh the positioning of the views (refreshViewForPositioning()) upon notification (onConfigurationChanged()). In operation 3715, the Nowbar card view model (801) can request a refresh (refreshAllView()) from the Nowbar card stack view (802). For example, the Nowbar card view model (801) can refresh all views upon notification (onConfigurationChanged()). For example, the Nowbar card view model (801) can display the widgets in dark colors with white text according to dark mode.

[0370] In operation 3811, the ongoing activity controller (3102) can send a message (onNowBarItemUpdated()) to the face widget notification controller (3801) indicating that the NowBar item has been updated as it switches to dark mode.

[0371] In operation 3812, the face widget notification controller (3801) can send a message (onNowBarItemUpdated()) to the NowBar item manager (3002).

[0372] In operation 3813, the Nowva Item Manager (3002) can identify a notification (notifyUpdatedObservers()) indicating an observation of the ongoing activity. The Nowva Item Manager (3002) can update Nowva items for the ongoing activity according to the notification (notifyUpdatedObservers()).

[0373] In operation 3814, the Nowva item manager (3002) can send a message (updatedItems()) indicating updated Nowva items to the Nowva controller (3003).

[0374] In operation 3815, the Nowva controller (3003) can send a message (updatedItems()) indicating updated Nowva items to the Nowva card view model (801).

[0375] In operation 3816, the Nowva Card View model (801) can request the Nowva Card Stack View (802) to apply an animation effect to the widget (showAnimation()).

[0376] In operation 3817, the Nowva Card Stack View (802) can refresh all views. For example, the Nowva Card View Model (801) can display widgets in dark colors with white text according to dark mode.

[0377] FIG. 39 is a flowchart illustrating the operation of an electronic device displaying a widget according to one embodiment.

[0378] FIG. 39 can be explained with reference to FIGS. 1 to 38.

[0379] Referring to FIG. 39, in operation 3910, the electronic device (101) may display a lock screen including a first icon, a second icon, and a widget. For example, the electronic device (101) may display a first icon of a first application in a first icon area (230) within the lock screen. For example, the electronic device (101) may display a second icon of a second application in a second icon area (240) within the lock screen. For example, the electronic device (101) may display a first widget of a third application in a widget area (220) between the first icon area (230) and the second icon area (240) within the lock screen.

[0380] For example, the electronic device (101) can execute a third application in an unlocked state (or a state displaying a home screen) (or a state displaying an application screen). For example, the electronic device (101) can receive user input to enter a lock state (or a lock screen) while the third application is running.

[0381] For example, the electronic device (101) may display a first widget in the widget area (220) within the lock screen based on the third application executing a first task corresponding to an ongoing activity (or corresponding to a pre-specified application). For example, the electronic device (101) may not display the first widget in the widget area (220) within the lock screen based on the third application executing a second task corresponding to a static notification (or not corresponding to a pre-specified application). For example, the notification manager (532) may not transmit the key name of the third application to the Nowva manager (531). For example, the Nowva manager (531) may stop displaying the first widget of the third application.

[0382] For example, the electronic device (101) can execute the third application and the fourth application in an unlocked state (or a state displaying the home screen) (or a state displaying the application screen). For example, the electronic device (101) can receive user input to enter a locked state (or a lock screen) while the third application and the fourth application are executed.

[0383] For example, the electronic device (101) may determine the priority between the third application and the fourth application based on whether the third application and the fourth application execute tasks corresponding to ongoing activities (or correspond to pre-specified applications). For example, the notification manager (532) of the electronic device (101) may store the key names of the third application and the fourth application in the Nowva item stack according to priority. For example, the notification manager (532) may determine the most recently executed application among the third application and the fourth application as the top card, and the application executed before that as the card following the top card. For example, the notification manager (532) may determine the application that received the most recent notification among the third application and the fourth application as the top card, and the application that received a notification before that as the card following the top card.

[0384] For example, the notification manager (532) can set the priority of the application in the ongoing activity state among the third and fourth applications higher than the application in the pre-ongoing activity or post-ongoing activity state.

[0385] For example, the notification manager (532) can display the widget of the selected application according to priority in the widget area (220) within the lock screen. For example, as it is determined that the priority of the third application is higher than the priority of the fourth application, the notification manager (532) can display the first widget of the third application in the widget area (220).

[0386] For example, the electronic device (101) may determine that the priority of the third application is higher than the priority of the fourth application based on the fact that the third application executes a task corresponding to an ongoing activity and the fourth application executes a task corresponding to a static notification. For example, the notification manager (532) of the electronic device (101) may display the first widget of the third application that executes a task corresponding to an ongoing activity in the widget area (220) within the lock screen.

[0387] In one embodiment, the electronic device (101) may turn off the display (260) based on the fulfillment of a specified condition (e.g., when a specified time elapses without user input, or when a press input for the power button is received). In one embodiment, the electronic device (101) may display a widget representing notifications generated while the display (260) is turned off in the widget area (220) when the display (260) is turned on. For example, the electronic device (101) may turn on the display (260) in response to user input to turn on the turned-off display (260). Subsequently, the electronic device (101) may display a widget representing notifications generated while the display (260) is turned off in the widget area (220) within the lock screen that is displayed as the display (260) is turned on. For example, the electronic device (101) may display a notification generated while the display (260) is turned off in the widget area (220) within the lock screen until a specified condition is met. For example, the specified condition may be determined to be met if a specified time (e.g., 12 hours) has elapsed from the time when the widget is switched to a post-ongoing activity (e.g., the time when a game ends in the case of sports) (hereinafter, the time of switching) is at dawn (or the user's sleep time). For example, the specified condition may be determined to be met if, even before the specified time (e.g., 12 hours) has elapsed, the electronic device (101) is unlocked, and another specified time (e.g., 30 minutes) has elapsed after the electronic device (101) is unlocked. For example, a specified condition may be determined to be satisfied even before a specified time (e.g., 12 hours) has elapsed, if user interaction with a widget of the electronic device (101) (e.g., tap input, swipe input on the widget) is identified.For example, a specified condition may be determined to be satisfied if another time (e.g., 4 hours) has elapsed from the point in time when the user of the electronic device (101) is identified as having woken up, even before a specified time (e.g., 12 hours) has elapsed.

[0388] In operation 3920, the electronic device (101) can receive a notification. For example, the electronic device (101) can identify a notification from a third application and another application. In one embodiment, the notification may be a notification from an application for an ongoing activity and / or static notification. In one embodiment, the third application and another application may be a first application, a second application, or other applications. Hereinafter, the third application and other applications may be referred to as a fourth application. However, the embodiments are not limited thereto. For example, the electronic device (101) may display a first widget for a first task in a widget area (220) within the lock screen while the third application is executing a plurality of tasks. For example, the electronic device (101) may identify a notification from a second task of the third application while displaying a first widget for a first task in a widget area (220) within the lock screen. In one embodiment, the first task and / or the second task may include a task for an ongoing activity or a task for a static notification.

[0389] In operation 3930, the electronic device (101) can determine whether a notification is an ongoing activity. For example, the electronic device (101) can determine that a notification is an ongoing activity if the notification is a notification of a real-time task running in a fourth application. For example, the electronic device (101) can determine that a notification is an ongoing activity if the notification is a notification of a fourth application classified as an ongoing activity. For example, a fourth application classified as an ongoing activity may include a sports application (521), a map application (523), a clock application (511), a voice recorder (512), a health application (513), an interpreter application (514), and / or a message application (515).

[0390] For example, the electronic device (101) can determine that a notification is a static notification if the notification is a notification that provides the user with little to no change in the state of the application or a constant amount of information. For example, the electronic device (101) can determine that a notification is a static notification if the notification is a notification of a fourth application classified as a static notification. For example, a fourth application classified as a static notification may include an AI brief (551), a notification highlight (552), a media application (553), and / or contact info (554).

[0391] In operation 3940, the electronic device (101) may display another widget representing a notification on top of the widget. For example, the electronic device (101) may display a second widget corresponding to the notification in the widget area (220) until another notification is identified in response to the notification being related to an ongoing activity.

[0392] In one embodiment, the Nowva manager (531) may display the second widget of the fourth application, which is an ongoing activity, in the widget area (220) until a specified condition is met. For example, the Nowva manager (531) may display the second widget in the widget area (220) until a specified time has elapsed from the point at which the second widget is switched to a post-ongoing activity.

[0393] For example, the electronic device (101) may receive user input for unlocking in a locked state (or a state displaying a lock screen) (or a state displaying an AoD screen). For example, the electronic device (101) may display a second widget of a fourth application, which is an ongoing activity, in a widget area (420) within the home screen in an unlocked state. For example, the electronic device (101) may display a second widget of a fourth application, which is an ongoing activity, in an enlarged widget area (423) below the notification bar (411) containing the widget area (420), based on input for enlarging the second widget displayed in the widget area (420) within the home screen in an unlocked state.

[0394] For example, the electronic device (101) may receive an input (e.g., a swipe input for the second widget) to stop displaying the second widget that is being displayed in the widget area (420, 423) within the home screen while in an unlocked state. For example, the electronic device (101) may stop displaying the second widget based on the input (e.g., a swipe input for the second widget) while in an unlocked state. For example, stopping displaying the second widget may include the notification manager (532) removing the key name for the second widget from the Nowva item stack. Accordingly, the notification manager (532) may send a message to the Nowva manager (531) indicating that the key name for the second widget has been deleted. Subsequently, based on the electronic device (101) switching to a locked state as the key name for the second widget is deleted, the electronic device (101) may stop displaying the second widget.

[0395] For example, while the electronic device (101) displays a first widget for a first task of a third application in a widget area (220) within the lock screen, it may display another widget representing a notification of a second task, which is an ongoing activity of the third application, on top of the first widget for the first task as it identifies a notification from a second task.

[0396] In operation 3950, the electronic device (101) may display another widget indicating a notification over the widget for a specified time (e.g., 30 minutes). For example, the electronic device (101) may display a second widget over the first widget for a specified time (e.g., 30 minutes). For example, after a specified time, the electronic device (101) may display the second widget below the first widget, which is displayed in the widget area (220) as an indicator (221) (or hint).

[0397] For example, while the electronic device (101) displays a first widget for a first task of a third application in a widget area (220) within the lock screen, it may display another widget representing a notification of a second task, which is a static notification of the third application, on top of the first widget for the first task as it identifies a notification from a second task.

[0398] In operation 3960, the electronic device (101) may display a widget on top of another widget after a specified time. For example, the electronic device (101) may display a first widget in the widget area (220) after a specified time and display a second widget below the first widget as an indicator (221) (or hint).

[0399] For example, the electronic device (101) may display a first widget for a first task on top of another widget that displays a notification of a second task, which is a static notification of a third application after a specified time.

[0400] FIG. 40 is a drawing illustrating a UI displayed on a multi-foldable electronic device according to one embodiment.

[0401] In the fully folded state (4001) of FIG. 40, the electronic device (4000) may display a lock screen including a background area (210) on the cover display (4060) of the first housing part (4011) among the first to third housing parts (4011, 4012, 4013). For example, the electronic device (4000) may display a visual object (211) indicating a lock state (e.g., a lock image) in the background area (210). The electronic device (4000) may display a widget in the widget area (220). In one embodiment, the electronic device (101) may further display icon areas (230, 240) together with the widget area (220). For example, the electronic device (101) may further display icon areas (230, 240) located to the left and right of the widget area (220).

[0402] From the fully folded state (4001) of FIG. 40 to the partially folded state (4002) in which the first housing part (4011) is unfolded, the electronic device (4000) may display a lock screen including a background area (210) in the main display part located in the first housing part (4011) and the second housing part (4012) among the main displays (4065) located in the first to third housing parts (4011, 4012, 4013). For example, the electronic device (4000) may display widgets in the widget area (220) and additional widget area (4021) in the main display part located in the first housing part (4011) and the second housing part (4012).

[0403] In the fully unfolded state (4003) in which the third housing part (4013) is unfolded from the partially folded state (4002) of FIG. 40, the electronic device (4000) may display a lock screen including a background area (210) on a main display (4065) positioned in the first to third housing parts (4011, 4012, 4013). For example, the electronic device (4000) may display widgets in a widget area (220) and additional widget areas (4021, 4022) on the main display (4065).

[0404] The technical problems to be solved in this disclosure are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which this disclosure pertains.

[0405] As described above, the electronic device (101) may include a touch-sensitive circuit and a display (260) that displays a widget which is a mini-application of an application, at least one processor (120) that includes a processing circuit, and a memory (130) that stores instructions and includes one or more storage media. When the instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may cause the electronic device (101) to display a lock screen through the display (260) that includes a first icon corresponding to a first application at a first position (230), a second icon corresponding to a second application at a second position (240), and a first widget of a third application at a third position (220) between the first icon and the second icon. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may be caused to identify a notification from a fourth application. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may be caused to display a second widget corresponding to the notification at the third location (220) until another notification for the third widget is identified in response to the notification being related to an ongoing activity. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may be caused to display the second widget corresponding to the notification at the third location (220) for a predetermined time period in response to the notification being related to a static notification, and after the predetermined time period, display the first widget at the third location (220).

[0406] When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may receive user input to enter the lock screen while the third application is running. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may cause the first widget to be displayed on the lock screen based on the third application executing a first task corresponding to the ongoing activity. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may cause the display of the first widget on the lock screen to be stopped based on the third application executing a second task corresponding to the static notification.

[0407] When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may receive user input to enter the lock screen while the third application and the fourth application are running. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may identify the priority between the third application and the fourth application based on the third application and the fourth application executing tasks corresponding to the ongoing activity. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may display the widget of the application selected according to the priority on the lock screen.

[0408] When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may receive the user input to enter the lock screen while the third application and the fourth application are running. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may cause the widget of the application running the task corresponding to the ongoing activity to be displayed on the lock screen, based on one of the third application or the fourth application running the task corresponding to the ongoing activity and the other application running the task corresponding to the static notification.

[0409] When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may receive user input to enter the lock screen while the third application is running. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may cause the first widget to be displayed on the lock screen based on whether the third application corresponds to a pre-specified application. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may cause the first widget to be withheld based on whether the third application does not correspond to a pre-specified application.

[0410] When the above instructions are executed individually or collectively by the at least one processor (120), they may cause the electronic device (101) to execute the fourth application before executing the third application. When the above instructions are executed individually or collectively by the at least one processor (120), they may cause the electronic device (101) to display the first widget on the second widget based on the third application corresponding to the pre-specified application. When the above instructions are executed individually or collectively by the at least one processor (120), they may cause the electronic device (101) to display the second widget at the third location (220) based on the third application not corresponding to the pre-specified application.

[0411] When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may receive a first user input to unlock the lock state in which a lock screen including the first widget is displayed. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may receive a collapsed widget corresponding to the first widget in a notification area within the unlock screen of the unlock state in response to the first user input. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may receive a second user input for the collapsed widget. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may cause the display of an enlarged widget corresponding to the first widget below the notification area in response to the second user input.

[0412] When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may receive a third user input to stop displaying the enlarged widget. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may stop displaying the enlarged widget in response to the third user input. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may stop displaying the widget at the third location (220) in response to a fourth user input to enter the lock screen.

[0413] The above instructions, when executed individually or collectively by the at least one processor (120), may cause the electronic device (101) to receive a fifth user input for executing a fifth application while the enlarged widget is displayed. The above instructions, when executed individually or collectively by the at least one processor (120), may cause the electronic device (101) to receive a sixth user input for displaying a home screen while displaying a screen of the fifth application in response to the fifth user input. The above instructions, when executed individually or collectively by the at least one processor (120), may cause the electronic device (101) to display a collapsed widget corresponding to the fourth widget of the fifth application instead of the collapsed widget corresponding to the first widget in the notification area of ​​the home screen, based on the fifth application executing a first task corresponding to the ongoing activity. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may cause the fifth application to display the reduced widget corresponding to the first widget in the notification area of ​​the home screen based on the execution of the second task corresponding to the static notification.

[0414] When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may cause the reduced widget corresponding to the fourth widget to enlarge and display the enlarged widget corresponding to the fourth widget in response to a seventh user input for the reduced widget corresponding to the fourth widget. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may cause the enlarged widget corresponding to the first widget to display on the enlarged widget corresponding to the fourth widget in response to a swipe input for the enlarged widget corresponding to the fourth widget. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may cause the first widget to display on the fourth widget in response to an eighth user input for entering the lock screen.

[0415] When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may be caused to enter a power saving mode based on the fulfillment of a predetermined condition in a locked state. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may be caused to display a widget containing at least a portion of the information contained in the first widget on a power saving screen displayed in the power saving mode, based on the first widget being displayable in the power saving mode. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may be caused to refrain from displaying the first widget based on the first widget not being displayable in the power saving mode.

[0416] When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may cause the display of the first icon and the second icon on the power saving screen in the power saving mode.

[0417] When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may cause the display (260) to turn off based on other predetermined conditions being met. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may cause the display (260) to turn on the turned-off display (260) in response to a ninth user input to turn on the display (260), a fifth widget containing a notification generated while the display (260) was turned off at the third location (220) within the lock screen that is displayed as the display (260) is turned on. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may cause the display of the fifth widget to be stopped based on identifying that the condition for stopping the display of the fifth widget is satisfied.

[0418] When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may be caused to identify that the condition for stopping the display of the fifth widget is satisfied based on receiving a first-to-first user input for the fifth widget after displaying the fifth widget at the third location (220).

[0419] When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may be caused to identify that the condition for stopping the display of the fifth widget is satisfied based on the elapsed time after the electronic device (101) is unlocked, after the electronic device (101) has displayed the fifth widget at the third location (220).

[0420] When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may be caused to identify that the condition for stopping the display of the fifth widget is satisfied based on the elapsed time of a specified other time after the fifth widget has been displayed at the third location (220).

[0421] As described above, the electronic device (101) may include a touch-sensitive circuit and a display (260) that displays a widget which is a mini-application of an application; at least one processor (120) that includes a processing circuit; and a memory (130) that stores instructions and includes one or more storage media. When the instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may cause the electronic device (101) to display a first icon corresponding to a first application and a second icon corresponding to a second application on the lower part of the display (260) through the display (260) while the electronic device (101) is in a locked state. When the instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may cause the electronic device (101) to display a first widget containing information corresponding to a third application between the first icon and the second icon. The first widget may have a wider width than the first icon and the second icon. When the instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may receive a notification from the fourth application in the locked state via the display (260) and display a second widget containing at least a portion of the notification on the first widget.

[0422] When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may receive user input to enter the lock state in the execution state of the third application. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may cause the first widget to be displayed through the display (260) based on the determination that the third application corresponds to a predetermined application. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may cause the first widget to be withheld through the display (260) based on the determination that the third application does not correspond to a predetermined application.

[0423] When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may cause the second widget to be displayed over the first widget until another notification is received, based on determining via the display (260) that the notification corresponds to an ongoing activity. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may cause the second widget to be displayed over the first widget for a predetermined time length via the display (260), and the first widget to be displayed instead of the second widget after the predetermined time length has elapsed, based on determining that the notification is a static notification.

[0424] The above instructions, when executed individually or collectively by the at least one processor (120), may cause the electronic device (101) to receive user input for a first widget displayed in the locked state of the electronic device (101). The above instructions, when executed individually or collectively by the at least one processor (120), may cause the electronic device (101) to display an enlarged widget from the first widget through the display (260) in response to the user input for the first widget. The above instructions, when executed individually or collectively by the at least one processor (120), may cause the electronic device (101) to move the first icon and the second icon so that the first icon and the second icon move apart from each other in a horizontal direction based on the display of the enlarged widget.

[0425] The method as described above may be performed by an electronic device (101) comprising a touch-sensitive circuit and a display (260) that displays a widget, which is a mini-application of an application. The method may include, in a locked state of the electronic device (101): displaying a lock screen through the display (260) comprising a first icon corresponding to a first application at a first position (230), a second icon corresponding to a second application at a second position (240), and a first widget of a third application at a third position (220) between the first icon and the second icon. The method may include identifying a notification from a fourth application. The method may include displaying a second widget corresponding to the notification at the third position (220) until another notification for the third widget is identified in response to the notification being related to an ongoing activity. The above method may include, in response to the notification being related to a static notification: displaying the second widget corresponding to the notification at the third location (220) for a predetermined time period, and after the predetermined time period, displaying the first widget at the third location (220).

[0426] The method described above may be performed by an electronic device (101) comprising a touch-sensitive circuit and a display (260) that displays a widget, which is a mini-application of an application. The method may include, in a locked state of the electronic device (101): displaying a first icon corresponding to a first application and a second icon corresponding to a second application on the lower part of the display (260) through the display (260). The method may include, through the display (260), displaying a first widget containing information corresponding to a third application between the first icon and the second icon. The first widget may have a wider width than the first icon and the second icon. The method may include, in the locked state, receiving a notification from a fourth application and, through the display (260), displaying a second widget containing at least a portion of the notification on top of the first widget.

[0427] A non-transitory computer-readable storage medium as described above may store a program containing instructions. When the instructions are executed, individually or collectively, by at least one processor (120) of an electronic device (101) that includes a touch-sensitive circuit and a display (260) that displays a widget which is a mini-application of an application, the electronic device (101) may cause the electronic device (101) to display a lock screen through the display (260) while the electronic device (101) is locked, the lock screen may include: a first icon corresponding to a first application at a first position (230), a second icon corresponding to a second application at a second position (240), and a first widget of a third application at a third position (220) between the first icon and the second icon. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may be caused to identify a notification from a fourth application. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may be caused to display a second widget corresponding to the notification at the third location (220) until another notification for the third widget is identified in response to the notification being related to an ongoing activity. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may be caused to display the second widget corresponding to the notification at the third location (220) for a predetermined time period in response to the notification being related to a static notification, and after the predetermined time period, display the first widget at the third location (220).

[0428] A non-transient computer-readable storage medium as described above may store a program containing instructions. When the instructions are executed individually or collectively by at least one processor (120) of an electronic device (101) that includes a touch-sensitive circuit and a display (260) that displays a widget which is a mini-application of an application, the electronic device (101) may cause the display (260) to display a first icon corresponding to a first application and a second icon corresponding to a second application on the lower part of the display (260). When the instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may cause the display (260) to cause a first widget containing information corresponding to a third application to display between the first icon and the second icon. The first widget may have a wider width than the first icon and the second icon. When the above instructions are executed individually or collectively by the at least one processor (120), the electronic device (101) may receive a notification from a fourth application in the locked state and, through the display (260), cause a second widget containing at least a portion of the notification to be displayed on the first widget.

[0429] The effects obtainable from the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure belongs.

[0430] The electronic device according to the various embodiments disclosed in this document may be of various forms. The electronic device may include, for example, a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a consumer electronics device. The electronic device according to the embodiments of this document is not limited to the devices described above.

[0431] The various embodiments of this document and the terms used therein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various modifications, equivalents, or substitutions of said 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 said items unless the relevant context clearly indicates otherwise. In this document, phrases such as "A or B," "at least one of A and B," "at least one of A or B," "A, B or C," "at least one of A, B and C," and "at least one of A, B, or C" may each include any one of the items listed together in the corresponding phrase, or all possible combinations thereof. Terms such as "first," "second," or "first" or "second" may be used simply to distinguish said components from other said components and do not limit said components in any other aspect (e.g., importance or order). Where any (e.g., 1st) component is referred to as "coupled" or "connected" to another (e.g., 2nd) component, with or without the terms "functionally" or "communicationly," it means that said any component may be connected to said other component directly (e.g., via a wire), wirelessly, or through a third component.

[0432] The term “module” as used in the 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, for example. A module may be a component formed integrally, or a minimum unit of said component or a part thereof 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).

[0433] Various embodiments of the present document may be implemented as software (e.g., program (140)) comprising one or more instructions stored in a storage medium (e.g., internal memory (136) or external memory (138)) readable by a machine (e.g., electronic device (101)). For example, a processor (e.g., processor (120)) of the machine (e.g., electronic device (101)) may call at least one of the one or more instructions stored in the storage medium and execute it. This enables the machine to be operated 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 that can be executed by an interpreter. The storage medium readable by the machine may be provided in the form of a non-transitory storage medium. Here, 'non-temporary' simply means that the storage medium is a tangible device and does not contain a signal (e.g., electromagnetic waves), and the term does not distinguish between cases where data is stored semi-permanently and cases where it is stored temporarily.

[0434] According to one embodiment, the method according to the various embodiments disclosed herein may be provided as included in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be distributed in the form of a device-readable storage medium (e.g., CD-ROM (compact disc read-only memory)), or distributed online (e.g., download or upload) through an application store (e.g., Play Store™) or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created on a device-readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a relay server.

[0435] According to various embodiments, each component (e.g., module or program) of the components described above may include a singular or multiple entities, and some of the multiple entities may be separated and placed in other components. According to various embodiments, one or more of the components or operations of the aforementioned components may be omitted, or one or more other components or operations may be added. Generally or additionally, multiple components (e.g., module or program) may be integrated into a single component. In this case, the integrated component may perform one or more functions of each of the multiple components in the same or similar manner as those performed by the corresponding component among the multiple components prior to integration. According to various embodiments, operations performed by the module, program, or other components 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 an electronic device, A display including a touch-sensitive circuit and displaying a widget, which is a mini-application of an application; At least one processor including a processing circuit; and The electronic device includes a memory that stores instructions and includes one or more storage media, wherein the instructions, when executed individually or collectively by the at least one processor, In the locked state of the above electronic device: A lock screen is displayed through the above display, comprising a first icon corresponding to a first application at a first position, a second icon corresponding to a second application at a second position, and a first widget of a third application at a third position between the first icon and the second icon. Identify notifications from the fourth application, and In response to the above notification being related to an ongoing activity, until another notification for the third widget is identified, a second widget corresponding to the above notification is displayed at the third location, and In response to the above notification being related to a static notification: Display the second widget corresponding to the above notification at the third location for a predetermined time period, and After the above-mentioned predetermined time period, causing the above-mentioned first widget to be displayed at the above-mentioned third location, Electronic device.

2. In Claim 1, When the above instructions are executed individually or collectively by the at least one processor, the electronic device, While the above third application is running, user input for entering the lock screen is received, and Based on the third application executing a first task corresponding to the ongoing activity, the first widget is displayed on the lock screen, and Based on the third application executing a second task corresponding to the static notification, causing the first widget to be withheld from being displayed on the lock screen, Electronic device.

3. In claim 1 or claim 2, When the above instructions are executed individually or collectively by the at least one processor, the electronic device, With the above third application and the above fourth application running, receive user input to enter the lock screen, and Based on the fact that the third application and the fourth application execute tasks corresponding to the ongoing activity, the priority between the third application and the fourth application is identified, and Causing the widget of the application selected according to the above priority to be displayed on the lock screen, Electronic device.

4. In Claim 3, When the above instructions are executed individually or collectively by the at least one processor, the electronic device, With the above third application and the above fourth application running, receiving the user input for entering the lock screen, and Based on one of the third application or the fourth application executing a task corresponding to the ongoing activity and the other application executing a task corresponding to the static notification, causing the widget of the application executing the task corresponding to the ongoing activity to be displayed on the lock screen. Electronic device.

5. In any one of claims 1 to 4, When the above instructions are executed individually or collectively by the at least one processor, the electronic device, While the above third application is running, user input for entering the lock screen is received, and Based on the fact that the above third application corresponds to a pre-specified application, the above first widget is displayed on the lock screen, and Causing the display of the first widget to be withheld based on the fact that the third application does not correspond to a pre-specified application, Electronic device.

6. In Claim 5, When the above instructions are executed individually or collectively by the at least one processor, the electronic device, Before executing the third application, execute the fourth application, and Based on the fact that the above third application corresponds to the above pre-specified application, the first widget is displayed on the second widget, and Causing the second widget to be displayed at the third location based on the fact that the third application does not correspond to the pre-specified application, Electronic device.

7. In any one of claims 1 to 6, When the above instructions are executed individually or collectively by the at least one processor, the electronic device, In a locked state where a lock screen including the first widget is displayed, a first user input is received to unlock the lock state, and In response to the above first user input, a reduced widget corresponding to the first widget is displayed in a notification area within the unlock screen in the unlocked state, and Receiving a second user input for the above-mentioned reduced widget, and In response to the second user input, causing an enlarged widget corresponding to the first widget to be displayed below the notification area, Electronic device.

8. In Claim 7, When the above instructions are executed individually or collectively by the at least one processor, the electronic device, Receiving a third user input to stop the display of the enlarged widget, In response to the third user input above, stop the display of the enlarged widget, and In response to a fourth user input for entering the lock screen, causing the display of the widget at the third location to be refrained, Electronic device.

9. In Claim 7, When the above instructions are executed individually or collectively by the at least one processor, the electronic device, While the above-mentioned enlarged widget is displayed, a fifth user input for executing a fifth application is received, and While displaying the screen of the fifth application in response to the fifth user input, receiving a sixth user input to display the home screen, Based on the fact that the fifth application executes a first task corresponding to the ongoing activity, a collapsed widget corresponding to the fourth widget of the fifth application is displayed in the notification area of ​​the home screen instead of the collapsed widget corresponding to the first widget, and Based on the fifth application executing a second task corresponding to the static notification, causing the collapsed widget corresponding to the first widget to be displayed in the notification area of ​​the home screen, Electronic device.

10. In Claim 9, When the above instructions are executed individually or collectively by the at least one processor, the electronic device, In response to a seventh user input regarding a reduced widget corresponding to the fourth widget, the reduced widget corresponding to the fourth widget is enlarged, and the enlarged widget corresponding to the fourth widget is displayed. In response to a swipe input for the enlarged widget corresponding to the fourth widget, the enlarged widget corresponding to the first widget is displayed on the enlarged widget corresponding to the fourth widget, and In response to an eighth user input for entering the lock screen, causing the first widget to be displayed on the fourth widget on the lock screen, Electronic device.

11. In any one of claims 1 to 10, When the above instructions are executed individually or collectively by the at least one processor, the electronic device, Based on the fulfillment of a predetermined condition while in a locked state, enter power saving mode, and Based on the fact that the first widget is displayable in the power saving mode, a widget including at least a portion of the information included in the first widget is displayed on a power saving screen displayed in the power saving mode, and Based on the fact that the first widget cannot be displayed in the power saving mode, causing the display of the first widget to be refrained from. Electronic device.

12. In Claim 11, When the above instructions are executed individually or collectively by the at least one processor, the electronic device, causing the display of the first icon and the second icon to be avoided on the power saving screen in the power saving mode. Electronic device.

13. In any one of claims 1 to 12, When the above instructions are executed individually or collectively by the at least one processor, the electronic device, Based on other predetermined conditions being met, the display is turned off, and In response to a ninth user input for turning on the turned-off display, a fifth widget including a notification generated while the display was turned off is displayed at the third location within the lock screen that is displayed as the display is turned on, and Based on identifying that the condition for stopping the display of the fifth widget is satisfied, causing the display of the fifth widget to be stopped, Electronic device.

14. In Claim 13, When the above instructions are executed individually or collectively by the at least one processor, the electronic device, After displaying the fifth widget at the third location, causing to identify that the condition for stopping the display of the fifth widget is satisfied based on receiving the first tenth user input regarding the fifth widget, Electronic device.

15. In Claim 13, When the above instructions are executed individually or collectively by the at least one processor, the electronic device, After displaying the fifth widget at the third location, causing to identify that the condition for stopping the display of the fifth widget is satisfied based on the elapsed time after the electronic device is unlocked, Electronic device.

Images