Electronic device and method of controlling electronic device

Abstract

The electronic device includes a memory, a communication interface, a display, and at least one processor that: requests a call connection from an external device via the communication interface; calculating an importance level corresponding to a telephone unconnected event when the telephone unconnected event stored in the memory is identified after requesting the call connection; if the importance level is equal to or greater than the threshold value, obtaining state information of the electronic device, the state information indicating an application running in the electronic device; if it is recognized that the pre-configured application is not running in the electronic device based on the state information, acquiring a notification time based on situation information of a user of the external device; and controlling the display to provide notification information indicating the telephone disconnection event based on the notification time.

Description

Technical Field

[0001] The present disclosure relates to an electronic device control and a method of controlling the electronic device, and more particularly, to an electronic device providing notification information indicating a call unconnected event to a user and a method of controlling the electronic device. Background Art

[0002] After attempting a telephone call connection, the call connection may not be successful for a variety of reasons.

[0003] In the case of an incoming phone call, if the call of the other party is not answered, a missed call message may be displayed on the smart phone. Therefore, the user may try to make a phone call to the other party after seeing the missed call message. However, if the user does not actually make a phone call after seeing the away message, there is a problem that the user easily forgets that he should call the other party.

[0004] In the case of an outgoing phone call, if the other party fails to answer the call, a missed call message is displayed to the other party, but a notification that the call connection with the other party is unsuccessful may not be displayed on the smartphone of the calling user. Therefore, there is a problem that the user easily forgets that he / she should call the other party again. Summary of the invention

Technical Solution

[0005] The present disclosure is designed to improve the aforementioned problems, and an object of the present disclosure is to provide an electronic device which provides notification information regarding a call unconnected event in consideration of a user's situation and a method of controlling the electronic device.

[0006] An electronic device according to an embodiment of the present disclosure includes a memory, a communication interface, a display and at least one processor, the at least one processor being configured to: request a call connection from an external device via the communication interface; and based on identifying a call unconnected event stored in the memory after requesting the call connection, calculate an importance level corresponding to the call unconnected event; and based on the importance level being greater than or equal to a threshold, obtain status information of the electronic device, the status information indicating an application being executed in the electronic device; and based on identifying that a predetermined application is not being executed in the electronic device according to the status information, obtain a notification time based on situation information of a user of the external device; and control the display to provide notification information indicating the call unconnected event based on the notification time.

[0007] Meanwhile, at least one processor may obtain at least one of contact number level information of the external device or communication frequency with the external device based on identifying the call unconnected event, and calculate the importance level based on at least one of the contact number level information or the communication frequency.

[0008] At the same time, at least one processor can obtain a first parameter corresponding to the contact number level information and a second parameter corresponding to the communication frequency based on identifying a call unconnected event, and calculate the importance level based on the first parameter, the first weight corresponding to the first parameter, the second parameter, and the second weight corresponding to the second parameter.

[0009] Meanwhile, the at least one processor may identify a category of the call unconnected event, and calculate the importance level based on the identified category, which may include at least one of an absence event, a rejection event, or a connection failure event.

[0010] Meanwhile, the predetermined application may be an application that performs a function that cannot be performed simultaneously with the call connection function.

[0011] At the same time, at least one processor can: based on identifying that a predetermined application is not being executed, identify whether a user input is received from an external device within a threshold time, and set the notification time to the current time point based on identifying that a user input is received from the external device within the threshold time.

[0012] At the same time, at least one processor can: obtain the user's schedule information based on identifying that the scheduled application is not being executed; and set the notification time to the current time point based on the fact that there is no schedule scheduled at the current time point according to the user's schedule information; and set the notification time to the time point when the scheduled schedule ends based on the fact that there is a schedule scheduled at the current time point according to the user's schedule information.

[0013] Meanwhile, the at least one processor may re-request the call connection with the external device through the communication interface based on receiving a user input for the call connection with the external device through the notification information.

[0014] Meanwhile, the notification information may include at least one of a reason for a call unconnected event, a message received from an external device, a callable time, or a notification time.

[0015] Meanwhile, the at least one processor may receive a callable time from an external device through the communication interface, and control the display to provide notification information including the callable time.

[0016] According to an embodiment of the present disclosure, a method for controlling an electronic device may include the following steps: requesting a call connection from an external device; and calculating an importance level corresponding to the call unconnected event based on identifying a call unconnected event stored in the electronic device after requesting the call connection; and based on the importance level being greater than or equal to a threshold, acquiring status information of the electronic device, the status information indicating an application being executed in the electronic device; and based on identifying that a predetermined application is not being executed in the electronic device according to the status information, acquiring a notification time based on situation information of a user of the external device; and providing notification information indicating the call unconnected event based on the notification time.

[0017] At the same time, in the step of obtaining the importance level, based on identifying the call unconnected event, at least one of the contact number level information of the external device or the communication frequency with the external device can be obtained, and the importance level can be calculated based on at least one of the contact number level information or the communication frequency.

[0018] At the same time, in the step of obtaining the importance level, based on the identification of the call unconnected event, a first parameter corresponding to the contact number level information and a second parameter corresponding to the communication frequency can be obtained, and the importance level can be calculated based on the first parameter, the first weight corresponding to the first parameter, the second parameter, and the second weight corresponding to the second parameter.

[0019] Meanwhile, in the step of acquiring the importance level, a category of the call unconnected event may be identified, the importance level may be calculated based on the identified category, and the category may include at least one of an absence event, a rejection event, or a connection failure event.

[0020] Meanwhile, the predetermined application may be an application that performs a function that cannot be performed simultaneously with the call connection function.

[0021] At the same time, in the step of obtaining the notification time, based on the recognition that the predetermined application is not being executed, it can be identified whether the user input is received from the external device within the threshold time, and based on the recognition that the user input is received from the external device within the threshold time, the notification time can be set to the current time point.

[0022] At the same time, in the step of obtaining the notification time, based on the recognition that the scheduled application is not being executed, the user's schedule information can be obtained, and based on the fact that there is no schedule scheduled at the current time point according to the user's schedule information, the notification time can be set to the current time point, and based on the fact that there is a schedule scheduled at the current time point according to the user's schedule information, the notification time can be set to the time point when the scheduled schedule ends.

[0023] Meanwhile, in the control method, based on receiving a user input for a call connection with the external device through the notification information, the call connection with the external device may be re-requested through the communication interface.

[0024] Meanwhile, the notification information may include at least one of a reason for a call unconnected event, a message received from an external device, a callable time, or a notification time.

[0025] Meanwhile, in the step of providing the notification information, a callable time may be received from an external device, and the notification information including the callable time may be provided. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Figure 1 is a block diagram showing an electronic device according to an embodiment of the present disclosure;

[0027] Figure 2 is a block diagram for illustrating a detailed configuration of an electronic device according to an embodiment of the present disclosure;

[0028] Figure 3 is a flowchart for illustrating an operation of providing notification information according to a call unconnected event;

[0029] Figure 4 is a flowchart for illustrating a method of providing notification information;

[0030] Figure 5 is a flow chart for illustrating a time when notification information is provided;

[0031] Figure 6 is a flowchart for illustrating operations for identifying a call unconnected event according to various embodiments;

[0032] Figure 7 is a flowchart for illustrating operations for identifying a call unconnected event according to various embodiments;

[0033] Figure 8 is a flowchart for illustrating operations for identifying a call unconnected event according to various embodiments;

[0034] Fig. 9 is a flowchart for illustrating operations for identifying a call unconnected event according to various embodiments;

[0035] Fig.10 is a flowchart for illustrating operations for identifying a call unconnected event according to various embodiments;

[0036] Fig.11 is a flowchart for illustrating operations for identifying a call unconnected event according to various embodiments;

[0037] Fig.12is a flowchart for illustrating an operation of calculating an importance level corresponding to an event;

[0038] Fig.13 is a flowchart for illustrating the operation of an electronic device according to the type of an event;

[0039] Fig.14 is a flow chart for illustrating the operation of an electronic device according to an incoming call event;

[0040] Fig.15 is a flow chart for illustrating the operation of an electronic device according to an outgoing call event;

[0041] Fig.16 is a flowchart for illustrating the operation of the electronic device according to whether a call with an external device is connected;

[0042] Fig.17 is a flow chart for illustrating operations related to retrying a call connection;

[0043] Fig.18 is a diagram for illustrating a call not connected event;

[0044] Fig.19 is a diagram for illustrating parameters used to calculate importance levels;

[0045] Fig. 20 is a diagram for showing status information of a device;

[0046] Fig.21 is a diagram for illustrating an operation of analyzing situation information of a user;

[0047] Fig. 22 A diagram for showing user's situation information;

[0048] Fig.23 is a flowchart for illustrating the operation of an electronic device that provides notification information based on information received from an external device;

[0049] Fig.24 is a diagram for illustrating notification information provided according to importance levels;

[0050] Fig.25 is a diagram for illustrating an operation of providing notification information according to various embodiments;

[0051] Fig.26 is a diagram for illustrating an operation of providing notification information according to various embodiments;

[0052] Fig. 27 is a diagram for illustrating a user interface (UI) displayed during a call connection according to various embodiments;

[0053] Fig.28 is a diagram for illustrating a user interface (UI) displayed during a call connection according to various embodiments;

[0054] Fig.29 is a diagram for illustrating an operation of providing notification information according to various embodiments;

[0055] Fig.30 is a diagram for illustrating an operation of providing notification information according to various embodiments;

[0056] Fig.31 is a diagram for illustrating an operation of updating an existing notification information providing model by acquiring parameters;

[0057] Fig.32 is a flowchart for illustrating an operation of providing notification information by using situation information of a user of an external device;

[0058] Fig.33 is a diagram for illustrating an operation of providing notification information according to various embodiments;

[0059] Fig.34 is a diagram for illustrating an operation of providing notification information according to various embodiments;

[0060] Fig.35 is a diagram for illustrating an operation of providing notification information according to various embodiments;

[0061] Fig.36 is a diagram for illustrating an operation of providing notification information according to various embodiments; and

[0062] Fig.37 is a flowchart for illustrating a method of controlling an electronic device according to various embodiments. DETAILED DESCRIPTION

[0063] Hereinafter, the present disclosure will be described in detail with reference to the accompanying drawings.

[0064] In view of the functions described in the present disclosure, currently widely used general terms have been selected as terms used in the embodiments of the present disclosure as much as possible. However, the terms may vary depending on the intention of those skilled in the art, previous court decisions, or the emergence of new technologies, etc. In addition, in certain cases, there may be terms arbitrarily specified by the applicant, and in this case, the meaning of the terms will be described in detail in the relevant descriptions in the present disclosure. Therefore, the terms used in the present disclosure should be defined based on the meaning of the terms and the overall content of the present disclosure rather than just based on the names of the terms.

[0065] Furthermore, in this specification, expressions such as “have”, “may have”, “include”, and “may include” indicate the presence of such characteristics (for example, elements such as numbers, functions, operations, and components), and do not exclude the presence of additional features.

[0066] Furthermore, the expression “at least one of A and / or B” should be interpreted as meaning any one of “A” or “B” or “A and B”.

[0067] In addition, the expressions "first", "second", etc. used in this specification can be used to describe various elements, regardless of any order and / or importance. In addition, such expressions are only used to distinguish one element from another element, and are not intended to limit the elements.

[0068] Meanwhile, the description that an element (e.g., a first element) in the present disclosure is “(operably or communicatively) coupled to” or “connected to” another element (e.g., a second element) should be interpreted as including the following two cases: a case where the one element is directly coupled to the other element, and a case where the one element is coupled to the other element via another element (e.g., a third element).

[0069] In addition, singular expressions include plural expressions as long as they do not have obviously different meanings in the context. In addition, in the present disclosure, terms such as "including" and "consisting of..." should be interpreted as indicating the existence of such characteristics, quantities, steps, operations, elements, components or combinations thereof described in the specification, but do not mean to exclude in advance the possibility of the existence or addition of one or more other characteristics, quantities, steps, operations, elements, components or combinations thereof.

[0070] In addition, in the present disclosure, a "module" or "unit" can perform at least one function or operation, and can be implemented as hardware or software, or a combination of hardware and software. In addition, in addition to a "module" or "unit" that needs to be implemented as specific hardware, multiple "modules" or "units" can be integrated into at least one module and implemented as at least one processor.

[0071] In addition, in this specification, the term "user" may refer to a person who uses an electronic device or a device that uses an electronic device (eg, an artificial intelligence electronic device).

[0072] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0073] Figure 1 is a block diagram showing an electronic device 100 according to an embodiment of the present disclosure.

[0074] refer to Figure 1, the electronic device 100 includes a memory 110 , a communication interface 120 , a display 130 and at least one processor 140 .

[0075] The electronic device 100 may represent a smart phone, a tablet computer, a wearable device, etc. that performs a phone call function.

[0076] The memory 110 may store a plurality of predetermined call unconnected events, a function of a calculation method indicating an importance level, an analysis method for acquiring state information or situation information, a method for providing notification information, and the like.

[0077] The communication interface 120 may perform a function for performing a call connection with the external device 200. The communication interface 120 may communicate with the server 300 to perform a call connection with the external device 200. The server 300 may represent a server of a communication company that provides a telephone service between users. The user of the electronic device 100 will be described as a first user, and the user of the external device 200 will be described as a second user.

[0078] At least one processor 140 can request a call connection from the external device 200 through the communication interface 120, and if a call unconnected event stored in the memory 110 is identified after requesting the call connection, an importance level corresponding to the call unconnected event is calculated, and if the importance level is greater than or equal to a threshold, status information of the electronic device 100 indicating an application being executed in the electronic device 100 is obtained, and if it is identified based on the status information that a predetermined application is not being executed in the electronic device 100, a notification time is obtained based on situation information of a user of the external device 200, and the display 130 is controlled to provide notification information indicating the call unconnected event based on the notification time.

[0079] A call unconnected event may represent an event in which a call connection is not performed normally. A call unconnected event may also be described as a call unsuccessful event. A call unconnected event may be a predetermined event. A call unconnected event may represent at least one of an incoming call unconnected event or an outgoing call unconnected event. An incoming call unconnected event may represent an event in which a call is received from a second user of an external device but the call is not connected. An outgoing call unconnected event may represent an event in which a first user of an electronic device makes an outgoing call but the call is not connected.

[0080] The situations identified as call disconnection events can be various. For example, as call disconnection events, there can be a call during absence, receiving an instruction to reject the call, unable to connect the communication, etc. Fig.18 Detailed descriptions of the call not connected event are described in.

[0081] The importance level may represent a score indicating the importance level associated with the identified event. The importance level may be described as an importance level value, an evaluation, an evaluation value, etc. The importance level corresponding to the call unconnected event may represent the importance of the other party of the call unconnected event to the user.

[0082] Assume that a first user of the electronic device 100 makes a phone call to a second user of the external device 200. The at least one processor 140 may request a call connection from the external device 200 through the communication interface 120. Specifically, the at least one processor 140 may send a control signal for requesting a call connection to the external device 200. According to various embodiments, the at least one processor 140 may send a control signal to the external device 200 via the server 300. The operation of using the server 300 will be described in detail in FIG. Figures 6 to 11 According to various embodiments, at least one processor 140 may directly send a control signal to the external device 200 .

[0083] At least one processor 140 may compare the calculated (or acquired) importance level with a predetermined threshold. The predetermined threshold may be a criterion for determining whether the occurrence of an event needs to be notified to the user. For example, it may not be necessary to repeatedly notify the user of all calls during absence. Therefore, in order to repeatedly notify the user of only selected calls during absence, at least one processor 140 may provide notification information only for events whose importance level is greater than or equal to the threshold. The predetermined threshold may be different according to the user's settings.

[0084] Meanwhile, if a call unconnected event is identified, the at least one processor 140 may acquire at least one of contact number level information of the external device 200 or a communication frequency with the external device 200 and calculate an importance level based on at least one of the contact number level information or the communication frequency.

[0085] At the same time, if a call unconnected event is identified, at least one processor 140 can obtain a first parameter corresponding to the contact number level information and a second parameter corresponding to the communication frequency, and calculate the importance level based on the first parameter, the first weight corresponding to the first parameter, the second parameter, and the second weight corresponding to the second parameter.

[0086] The process of calculating the importance level by using the parameters will be in Fig.19 Described in.

[0087] Meanwhile, the at least one processor 140 may identify a category of the call unconnected event and calculate an importance level based on the identified category, and the category may include at least one of an absence event, a rejection event, or a connection failure event.

[0088] The state information of the electronic device 100 may include information related to the current state of the electronic device 100. In addition, the state information of the electronic device 100 may include information related to the electronic device 100 at a time point when a call unconnected event occurs.

[0089] The status information of the electronic device 100 may include information related to hardware driven in the electronic device 100 (for example, activation information of the microphone, power information of the display), information related to a specific mode driven in the electronic device 100 (for example, focus mode, do not disturb mode), information indicating applications installed in the electronic device 100, information indicating applications currently being executed in the electronic device 100, information indicating the remaining power of the electronic device 100, etc.

[0090] In the foregoing description, the information related to the hardware and the information indicating the application being executed are described separately. However, at least one processor 140 may determine the state in which the power of the display is turned on as the state in which the predetermined application is being executed. This is because the operation of supplying power to the display may be performed in a specific application. In addition, at least one processor 140 may determine the state in which the microphone 180 is activated as the state in which the predetermined application is being executed. The state in which the microphone 180 is activated may indicate the state in which the power of the microphone 180 is turned on.

[0091] Details about the status information are given in Fig. 20 Described in.

[0092] If the importance level of the call unconnected event is greater than or equal to the threshold, the at least one processor 140 may determine that it is necessary to provide notification information about the call unconnected event to the user. In the case where notification information is provided for all call unconnected events, the notification information may be identified as spam. Therefore, the at least one processor 140 may determine whether a predetermined application is currently being executed based on the status information of the electronic device 100.

[0093] According to various embodiments, at least one processor 140 may additionally consider the second state information of the external device 200 and the first state information of the electronic device 100. Specifically, at least one processor 140 may request state information (second state information) from the external device 200. The external device 200 may send the second state information in response to the request of the electronic device 100. The at least one processor 140 may analyze the second state information. In the case where the external device 200 is not executing a predetermined application based on the second state information, the at least one processor 140 may acquire the notification time based on the situation information of the second user.

[0094] Meanwhile, the predetermined application may be an application that performs a function that cannot be performed simultaneously with the call connection function.

[0095] The function that cannot be executed simultaneously with the call connection function may refer to an audio receiving function. Therefore, the predetermined application may refer to an application that uses the audio receiving function. The predetermined application may refer to an application that receives a user's voice through a microphone. For example, the predetermined application may be a telephone application, a video conferencing application, a voice chat application, a game application using a microphone, etc.

[0096] At least one processor 140 may determine whether the microphone 180 is currently activated based on the state information of the electronic device 100. If the microphone 180 is activated, the at least one processor 140 may determine that a predetermined application is being executed. If the microphone 180 is not activated, the at least one processor 140 may determine the notification time based on the user's situation information.

[0097] If it is recognized based on the state information that the predetermined application is not being executed in the electronic device 100, the at least one processor 140 may request the external device 200 for situation information through the communication interface 120. Specifically, the at least one processor 140 may request the situation information of the user of the external device 200. In response to the request of the electronic device 100, the external device 200 may send the situation information of the second user to the electronic device 100. The at least one processor 140 may receive the situation information (the situation information of the second user) from the external device 200 through the communication interface 120. The at least one processor 140 may acquire the notification time based on the received situation information.

[0098] At the same time, if it is recognized that the predetermined application is not being executed, the at least one processor 140 can recognize whether the input of the user (the second user) is received from the external device 200 within the threshold time, and if it is recognized that the input of the user (the second user) is received from the external device 200 within the threshold time, the at least one processor 140 can set the notification time to the current time point.

[0099] If it is recognized that the predetermined application is not being executed, the at least one processor 140 may provide notification information about the call unconnected event to the user. Here, the at least one processor 140 may determine a notification time at which the notification information will be provided to the user.

[0100] According to various embodiments, at least one processor 140 may provide notification information immediately at the time point when the call unconnected event occurs. However, even if notification information is provided at the time point when the call unconnected event occurs, it may not be necessary for the user to immediately realize this. This is because: even if the call connection is attempted again through the notification information, the call unconnected event is likely to occur again. For example, even if a call is requested again from the other party through a notification about the other party's absence, the other party is likely not to answer the call.

[0101] Therefore, at least one processor 140 may determine the notification time at which notification information will be provided in consideration of the user's situation information. Here, the user's situation information may include at least one of situation information corresponding to a first user of the electronic device 100 (which may be described as first situation information) or situation information corresponding to a second user of the external device 200 (which may be described as second situation information).

[0102] According to various embodiments, a feature of determining a notification time in consideration of second situation information of a second user will be described.

[0103] If it is recognized that the predetermined application is not being executed, the at least one processor 140 may receive situation information (second situation information) of a user (second user) of the external device 200 through the communication interface 120. Then, the at least one processor 140 may analyze the situation information.

[0104] At the same time, if it is identified that the scheduled application is not being executed, at least one processor 140 can obtain the schedule information of the second user, and if there is no schedule scheduled at the current time point based on the schedule information of the second user, at least one processor 140 can set the notification time to the current time point, and if there is a schedule scheduled at the current time point based on the schedule information of the second user, at least one processor 140 can set the notification time to the time point when the scheduled schedule ends.

[0105] The at least one processor 140 may request the schedule information of the second user from the external device 200. The external device 200 may send the schedule information of the second user to the electronic device 100 in response to the request of the electronic device 100. The at least one processor 140 may receive the schedule information of the second user from the external device 200 through the communication interface 120.

[0106] According to various embodiments, a feature of determining a notification time in consideration of first situation information of a first user and second situation information of a second user will be described.

[0107] At least one processor 140 may consider both the first situation information of the first user and the second situation information of the second user in providing notification information. This is because: when making a call, both the first user and the second user need to be in a state where the call can be performed. When an input (e.g., a touch input) of the first user is received from the electronic device 100 and an input (e.g., a touch input) of the second user is received from the external device 200 within a threshold time, the at least one processor 140 may determine the notification time as the current time.

[0108] If no user input is recognized in any one of the electronic device 100 or the external device 200, the at least one processor 140 may not provide notification information until user input is received from both the electronic device 100 and the external device 200 within a threshold time. Therefore, the current time does not necessarily refer to a point in time when a call unconnected event occurs. The current time may refer to a point in time when it is determined whether to provide notification information.

[0109] Detailed information about the situation will be provided in Fig.21 and Fig. 22 Described in.

[0110] Meanwhile, if an input of a user (first user) for a call connection with the external device 200 is received through the notification information, the at least one processor 140 may re-request a call connection with the external device 200 through the communication interface 120. A detailed description of this aspect will be given in Fig.17 Described in.

[0111] Meanwhile, the notification information may include at least one of a reason for a call unconnected event, a message received from the external device 200, a callable time, or a notification time.

[0112] Meanwhile, the at least one processor 140 may receive a callable time from the external device 200 through the communication interface 120 and control the display 130 to provide notification information including the callable time.

[0113] Details on how to provide notification information are provided in Fig.24 Described in.

[0114] The UI related to various types of notification information will be Figures 25 to 30 as well as Figure 33 to Figure 36 Described in.

[0115] Meanwhile, in the above, only simple components constituting the electronic device 100 are shown and described, but in actual implementation, various components may be additionally included. This aspect will be described below with reference to Figure 2 to describe.

[0116] Figure 2 1 is a block diagram for illustrating a detailed configuration of the electronic device 100 according to an embodiment of the present disclosure.

[0117] refer to Figure 2 The electronic device 100 may include at least one of a memory 110 , a communication interface 120 , a display 130 , at least one processor 140 , a manipulation interface 150 , an input / output interface 160 , a speaker 170 , or a microphone 180 .

[0118] Meanwhile, repeated explanations on the same operations as those described above will be omitted.

[0119] The electronic device according to various embodiments of the present specification may include, for example, a smart phone, a tablet computer, a mobile phone, a video phone, an e-book reader, a desktop PC, a laptop PC, a netbook computer, a workstation, a server, a PDA, a portable multimedia player (PMP), an MP3 player, a medical device, a camera, or at least one of a wearable device. The wearable device may include at least one of an accessory device (e.g., a watch, a ring, a bracelet, an anklet, a necklace, glasses, contact lenses, or a head-mounted device (HMD)), a device integrated with fabric or clothing (e.g., electronic clothing), a body-attached device (e.g., a skin patch or a tattoo), or an implantable circuit. In addition, in some embodiments, the electronic device may include, for example, a television, a digital video disk (DVD) player, a stereo, a refrigerator, an air conditioner, a vacuum cleaner, an oven, a microwave oven, a washing machine, an air purifier, a set-top box, a home automation control panel, a security control panel, a media box (e.g., Samsung HomeSync TM , Apple TV TM , or Google TV TM ), game consoles (e.g. Xbox TM , PlayStation TM ), electronic dictionary, electronic key, camera or electronic photo frame.

[0120] The memory 110 may be implemented as an internal memory included in the at least one processor 140, such as a ROM (e.g., an electrically erasable programmable read-only memory (EEPROM)), a RAM, or the like, or as a memory separate from the at least one processor 140. In this case, the memory 110 may be implemented in the form of a memory embedded in the electronic device 100, or may be implemented in the form of a memory capable of being attached to or detached from the electronic device 100, depending on the purpose of storing data. For example, in the case of data for driving the electronic device 100, the data may be stored in a memory embedded in the electronic device 100, and in the case of data for expanding functions of the electronic device 100, the data may be stored in a memory capable of being attached to or detached from the electronic device 100.

[0121] Meanwhile, in the case of a memory embedded in the electronic device 100, the memory may be implemented as at least one of the following: a volatile memory (e.g., a dynamic RAM (DRAM), a static RAM (SRAM), or a synchronous dynamic RAM (SDRAM), etc.), or a non-volatile memory (e.g., a one-time programmable ROM (OTPROM), a programmable ROM (PROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a mask ROM, a flash ROM, a flash memory (e.g., a NAND flash memory or a NOR flash memory, etc.), a hard disk drive, or a solid-state drive (SSD). Furthermore, in the case of a memory that can be attached to or detached from the electronic device 100, the memory may be implemented in the form of a memory card (e.g., a compact flash (CF), a secure digital (SD), a micro secure digital (micro SD), a mini secure digital (mini SD), an extreme digital (xD), a multimedia card (MMC), etc.), and an external memory (e.g., a USB memory) that can be attached to a USB port, etc.

[0122] The communication interface 120 is a component that performs communication with various types of external devices according to various types of communication methods. The communication interface 120 may include a wireless communication module or a wired communication module. Each communication module may be implemented in the form of at least one hardware chip.

[0123] The wireless communication module may be a module for wirelessly communicating with an external device. For example, the wireless communication module may include at least one of a Wi-Fi module, a Bluetooth module, an infrared communication module, or other communication modules.

[0124] The Wi-Fi module and the Bluetooth module can perform communication by the Wi-Fi method and the Bluetooth method, respectively. In the case of using the Wi-Fi module or the Bluetooth module, various types of connection information such as a service set identifier (SSID), a session key, etc. are first sent and received, and a communication connection is performed by using the information, and then various types of information can be sent and received.

[0125] The infrared communication module performs communication according to an Infrared Data Association (IrDA) technology that wirelessly transmits data to a near field by using infrared rays between visible light and millimeter waves.

[0126] Other communication modules may include at least one communication chip that performs communication according to various other wireless communication protocols different from the aforementioned communication methods (such as Zigbee, third generation (3G), third generation partnership project (3GPP), long term evolution (LTE), LTE advanced (LTE-A), fourth generation (4G), fifth generation (5G), etc.).

[0127] The wired communication module may be a module for communicating with an external device via wires. For example, the wired communication module may include at least one of a local area network (LAN) module, an Ethernet module, a twisted pair, a coaxial cable, an optical fiber cable, or an ultra-wideband (UWB) module.

[0128] The display 130 may be implemented as various forms of displays, such as a liquid crystal display (LCD), an organic light emitting diode (OLED) display, a plasma display panel (PDP), etc. Inside the display 130, a driving circuit and a backlight unit may also be included together. The driving circuit may be implemented in forms such as amorphous silicon thin film transistors (a-siTFT), low temperature polycrystalline silicon (LTPS) TFT, organic TFT (OTFT), etc. At the same time, the display 130 may be implemented as a touch screen combined with a touch sensor, a flexible display, a three-dimensional (3D) display, etc. In addition, the display 130 according to an embodiment of the present disclosure may include not only a display panel that outputs an image, but also a frame that accommodates the display panel. Specifically, the frame according to an embodiment of the present disclosure may include a touch sensor (not shown) for detecting user interaction.

[0129] The manipulation interface 150 may be implemented as a device such as a button, a touch pad, a mouse, a keyboard, or a touch screen capable of performing both the aforementioned display function and the manipulation input function. The button may be various types of buttons (such as a mechanical button, a touch pad, a scroll wheel, etc.) formed in any area (front surface part or side surface part, rear surface part, etc.) outside the body of the electronic device 100.

[0130] The input / output interface 160 may be an interface of any one of a high-definition multimedia interface (HDMI), a mobile high-definition link (MHL), a universal serial bus (USB), a display port (DP), thunderbolt, a video graphics array (VGA) port, an RGB port, a D-SUB, or a digital video interface (DVI). The input / output interface 160 may input or output at least one of an audio signal or a video signal. Depending on the implementation example, the input / output interface 160 may include a port that outputs only an audio signal and a port that outputs only a video signal as separate ports, or it may be implemented as one port that inputs and outputs both an audio signal and a video signal. At the same time, the electronic device 100 may send at least one of an audio signal or a video signal to an external device (e.g., an external display device or an external speaker) through the input / output interface 160. Specifically, the output port included in the input / output interface 160 may be connected to an external device, and the electronic device 100 may send at least one of an audio signal or a video signal to the external device through the output port.

[0131] The input / output interface 160 may be connected to the communication interface. The input / output interface 160 may transmit information received from an external device to the communication interface, or transmit information received through the communication interface to the external device.

[0132] The speaker 170 may be a component that outputs not only various types of audio data but also various types of notification sounds or voice messages or the like.

[0133] The microphone 180 is a component for receiving the input of the user's voice or other sounds and converting it into audio data. The microphone 180 can receive the user's voice in an activated state. For example, the microphone 180 can be formed as an integrated type integrated into the upper side or front surface direction, side surface direction, etc. of the electronic device 100. The microphone 180 may include various components, such as a microphone for collecting the user's voice in analog form, an amplifier circuit for amplifying the collected user's voice, an A / D conversion circuit for sampling the amplified user's voice and converting the user's voice into a digital signal, a filter circuit for removing noise components from the converted digital signal, etc.

[0134] Figure 3 is a flowchart for illustrating an operation of providing notification information according to a call unconnected event.

[0135] refer to Figure 3 In step S310, the electronic device 100 may identify a call unconnected event. The call unconnected event may represent an event in which a call connection is not performed normally. The call unconnected event may also be described as a call unsuccessful event. The call unconnected event may be a predetermined event. The call unconnected event may refer to at least one of an incoming call unconnected event or an outgoing call unconnected event.

[0136] In step S320, the electronic device 100 may acquire an importance level corresponding to the event. The importance level may represent a score indicating an importance level associated with the identified event. The importance level may be described as an importance level value, an evaluation, an evaluation value, etc.

[0137] In step S330, the electronic device 100 may provide notification information based on the importance level. The providing operation may refer to providing notification information to at least one of the first user of the electronic device or the second user of the external device. The electronic device 100 may determine the notification type based on the importance level.

[0138] Figure 4 is a flowchart for illustrating a method of providing notification information.

[0139] Figure 4 Steps S410 and S420 in may correspond to Figure 3Therefore, repeated description will be omitted.

[0140] After obtaining the importance level, in step S430, the electronic device 100 may identify the notification type based on the importance level. The notification type may include at least one of the notification target, notification content, and notification time. Fig.24 Detailed instructions for notification types are described in.

[0141] In step S440, the electronic device 100 may provide notification information based on the notification type. The electronic device 100 may generate notification information according to the determined notification type. Then, the electronic device 100 may provide the generated notification information.

[0142] Figure 5 is a flowchart for illustrating the timing of providing notification information.

[0143] Figure 5 Steps S510, S520, S530 and S540 in may correspond to Figure 4 Steps S410, S420, S430 and S440 in .

[0144] After identifying the notification type, in step S531, the electronic device 100 may determine whether a predetermined event is identified. The predetermined event may refer to an event in which a call can be made with a user. In the case of an incoming call unconnected event, the predetermined event may refer to an event in which a call can be made with the first user of the electronic device 100. The predetermined event may also be described as a predetermined situation.

[0145] If, in step S531-Y, a predetermined event is identified, in step S540, the electronic device 100 may provide notification information based on the notification type. If, in step S531-N, no predetermined event is identified, the electronic device 100 may store the call unconnected event in the memory 110. After the call is not connected, the electronic device 100 may store the fact that the call is finally unconnected in the memory 110. Thereafter, if there is a request from the user for an additional check, the electronic device 100 may provide a list of call unconnected events stored in the memory 110.

[0146] Figure 6 is a flow chart for illustrating operations of identifying a call unconnected event according to various embodiments.

[0147] refer to Figure 6In step S605, the electronic device 100 may receive an instruction for call connection. In step S610, the electronic device 100 may send a signal for call connection to the server 300. The server 300 may refer to a server that provides a telephone service between the electronic device 100 and the external device 200.

[0148] The server 300 may receive a signal for a call connection from the electronic device 100. In step S615, the server 300 may transmit a signal for a call connection to the external device 200.

[0149] The external device 200 may receive the signal for the call connection transmitted from the electronic device 100 from the server 300. The second user of the external device 200 may determine whether to accept the call connection.

[0150] In a state where the second user does not accept the call connection, the first user of the electronic device 100 may cancel the call connection. In step S620, the electronic device 100 may receive an instruction for call cancellation. In step S625, the electronic device 100 may send a signal for call cancellation to the external device 200.

[0151] The server 300 may receive a signal for call cancellation from the electronic device 100. In step S630, the server 300 may transmit a signal for call cancellation to the external device 200.

[0152] After receiving the instruction for call cancellation, in step S635, the electronic device 100 may identify a call unconnected event according to the instruction for call cancellation. In the case where the first user cancels the call connection, the electronic device 100 may confirm that the call unconnected event has been identified.

[0153] Figure 7 is a flow chart for illustrating operations of identifying a call unconnected event according to various embodiments.

[0154] Figure 7 Steps S705, S710, S715, S720, S725, S730, and S735 in may correspond to Figure 6 Therefore, repeated description will be omitted.

[0155] After receiving the instruction for call cancellation, in step S731, the electronic device 100 may identify, at the time point when the instruction for call cancellation is received, whether a threshold time has passed from the time point when the instruction for call connection is received.

[0156] If, in step S731 -Y, the threshold time has passed, then in step S735 , the electronic device 100 may identify a call unconnected event.

[0157] If the threshold time has not elapsed in step S731-N, the electronic device 100 may determine that a call unconnected event has not occurred because the call connection itself may be an erroneous attempt.

[0158] Figure 8 is a flow chart for illustrating operations of identifying a call unconnected event according to various embodiments.

[0159] Figure 8 Steps S805, S810 and S815 in may correspond to Figure 6 Therefore, repeated description will be omitted.

[0160] After receiving the call connection attempt made by the electronic device 100, in step S820, the external device 200 may receive an instruction made by the second user to reject the call. The second user may reject the call connection request of the first user. In step S825, the external device 200 may send a signal for rejecting the call to the server 300.

[0161] The server 300 may receive a signal for rejecting the call from the external device 200. In step S830, the server 300 may transmit a signal for rejecting the call to the electronic device 100.

[0162] The electronic device 100 may receive a signal for rejecting a call from the external device 200. In step S835, the electronic device 100 may identify a call unconnected event based on the signal for rejecting a call. When the signal for rejecting a call is received from the server 300, the electronic device 100 may identify that a call unconnected event has occurred.

[0163] Fig. 9 is a flow chart for illustrating operations of identifying a call unconnected event according to various embodiments.

[0164] Fig. 9 Steps S905, S910 and S915 in may correspond to Figure 6 Therefore, repeated description will be omitted.

[0165] After receiving the call connection attempt made by the electronic device 100, the external device 200 may receive an instruction for call acceptance in step S920. In step S925, the external device 200 may send a signal for call connection success to the server 300.

[0166] The server 300 may receive a signal for call connection success from the external device 200. In step S930, the server 300 may transmit a signal for call connection success to the electronic device 100.

[0167] In step S935, the external device 200 may receive an instruction for call disconnection during the call connection with the electronic device 100. The instruction for call disconnection may refer to an instruction to disconnect the current phone call due to a newly received call request from a third party. In step S940, the external device 200 may send a signal for call disconnection to the server 300.

[0168] The server 300 may receive a signal for call disconnection from the external device 200. In step S945, the server 300 may transmit a signal for call disconnection to the electronic device 100.

[0169] The electronic device 100 may receive a signal for call disconnection from the server 300. In step S950, the electronic device 100 may identify a call disconnection event based on the signal for call disconnection. When receiving the signal for call disconnection, the electronic device 100 may identify that a call disconnection event has occurred. The signal for call disconnection may represent a signal indicating a situation different from a situation in which the second user simply ends the call.

[0170] Fig.10 is a flow chart for illustrating operations of identifying a call unconnected event according to various embodiments.

[0171] Fig.10 Steps S1005, S1010 and S1015 in may correspond to Figure 6 Therefore, repeated description will be omitted.

[0172] After receiving the instruction for call connection, the communication session between the server 300 and the electronic device 100 may end without a predetermined instruction. In step S1020, the electronic device 100 may recognize that the communication session with the server 300 ends without a predetermined instruction. In addition, in step S1021, the server 300 may recognize that the communication session with the electronic device 100 ends without a predetermined instruction.

[0173] If the communication session with the server 300 ends without a predetermined instruction, in step S1025 , the electronic device 100 may recognize that a call unconnected event has occurred.

[0174] Fig.11is a flow chart for illustrating operations of identifying a call unconnected event according to various embodiments.

[0175] Fig.11 Steps S1105, S1110 and S1115 in may correspond to Figure 6 Therefore, repeated description will be omitted.

[0176] After receiving the instruction for call connection, the communication session between the server 300 and the external device 200 may end without a predetermined instruction. In step S1120, the external device 200 may recognize that the communication session with the server 300 ends without a predetermined instruction.

[0177] If the communication session with the server 300 ends without a predetermined instruction, the external device 200 may recognize that a call unconnected event has occurred in step S1120. In addition, the server 300 may recognize that the communication session with the external device 200 ends without a predetermined instruction in step S1121.

[0178] After the communication session ends, in step S1125, the server 300 may send a notification about the inability to make a call connection to the electronic device 100. The notification about the inability to make a call connection may also be described as a signal indicating that the call connection cannot be made.

[0179] The electronic device 100 may receive a notification that a call connection cannot be made from the server 300. When receiving the notification that a call connection cannot be made, the electronic device 100 may recognize that a call unconnected event has occurred.

[0180] Meanwhile, from now on, the description will be described with the configuration of the server 300 omitted. Depending on the implementation example, the server 300 is not described in the following description, but the server 300 may be used to perform communication between the electronic device 100 and the external device 200.

[0181] Fig.12 is a flowchart for illustrating an operation of calculating an importance level corresponding to an event.

[0182] refer to Fig.12 In step S1205, the electronic device 100 may identify a call disconnection event. In step S1210, the electronic device 100 may obtain parameters corresponding to the event. The parameters may also be described as parameter information. Fig.19 A detailed description of this aspect is described in Table 1910 in .

[0183] In step S1215, the electronic device 100 may calculate the importance level corresponding to the event based on the parameter. In step S1220, the electronic device 100 may acquire the state information of the device. The state information may include at least one of the state information of the electronic device 100 or the state information of the external device 200.

[0184] In step S1225 , the electronic device 100 may acquire the user's situation information. The situation information may include at least one of situation information of a first user using the electronic device 100 or situation information of a second user using the external device 200 .

[0185] In step S1230, the electronic device 100 may provide notification information based on at least one of the importance level, the state information of the device, or the situation information of the user.

[0186] Fig.13 is a flowchart for illustrating an operation of the electronic device 100 according to the type of an event.

[0187] refer to Fig.13 In step S1305, the electronic device 100 may identify whether the call unconnected event is an incoming call event. If in step S1305-Y, the call unconnected event is an incoming call event, then in step S1310, the electronic device 100 may obtain the state information of the electronic device 100 at the time of the incoming call. In step S1315, the electronic device 100 may determine whether a predetermined application is being executed in the device based on the state information of the electronic device 100.

[0188] If the predetermined application is not being executed in the electronic device 100 in step S1315-N, the electronic device 100 may wait until the predetermined application is completed.

[0189] If, in step S1315-Y, a predetermined application is being executed in the electronic device 100, then in step S1320, the electronic device 100 may obtain the situation information of the user (the first user). In step S1325, the electronic device 100 may track the user's behavior. The electronic device 100 may store and analyze what operations the user has performed in the electronic device 100 after the call unconnected event occurs.

[0190] Fig.14 is a flowchart for illustrating the operation of the electronic device 100 according to an incoming call event.

[0191] refer to Fig.14In step S1405, the electronic device 100 may identify an incoming call unconnected event. In step S1410, the electronic device 100 may acquire a parameter set corresponding to the event. In step S1415, the electronic device 100 may calculate an event importance level (importance level corresponding to the event) based on the parameters.

[0192] In step S1420, the electronic device 100 may identify whether the importance level is greater than or equal to a threshold value. If in step S1420-N, the importance level is not greater than or equal to the threshold value, the electronic device 100 may repeatedly perform steps S1405 to S1420.

[0193] If the importance level is greater than or equal to the threshold in step S1420-Y, the electronic device 100 may acquire the state information of the electronic device 100 at the time of the incoming call in step S1425. In step S1430, the electronic device 100 may identify whether a predetermined application is being executed in the electronic device 100 based on the state information of the electronic device 100.

[0194] If the predetermined application is not being executed in the electronic device 100 in step S1430-N, the electronic device 100 may wait until the predetermined application is completed.

[0195] If, in step S1430-Y, the predetermined application is being executed in the electronic device 100, then in step S1435, the electronic device 100 may acquire the situation information of the user (the first user). In step S1440, the electronic device 100 may provide notification information based on the situation information of the user.

[0196] Fig.15 is a flowchart for illustrating the operation of the electronic device 100 according to an outgoing call event.

[0197] refer to Fig.15 In step S1505, the electronic device 100 may identify an outgoing call unconnected event. In step S1510, the electronic device 100 may acquire a parameter set corresponding to the event. In step S1515, the electronic device 100 may calculate an event importance level (importance level corresponding to the event) based on the parameters.

[0198] In step S1520, the electronic device 100 may identify whether the importance level is greater than or equal to a threshold value. If in step S1520-N, the importance level is not greater than or equal to the threshold value, the electronic device 100 may repeatedly perform steps S1505 to S1520.

[0199] If in step S1520-Y, the importance level is greater than or equal to the threshold, then in step S1525, the electronic device 100 may send a signal to the external device 200 requesting at least one of status information of the external device 200 as the subject of the outgoing call or situation information of the second user.

[0200] In step S1530, the electronic device 100 may receive at least one of the state information of the external device 200 or the situation information of the second user from the external device 200. In step S1535, the electronic device 100 may provide notification information based on at least one of the state information of the external device 200 or the situation information of the second user.

[0201] Fig.16 is a flowchart for illustrating an operation of the electronic device 100 according to whether a call with an external device is connected.

[0202] refer to Fig.16 In step S1605, the electronic device 100 may identify a call disconnection event. In step S1610, the electronic device 100 may acquire identification information of the external device 200 associated with the call disconnection event. In step S1615, the electronic device 100 may store event occurrence information including the identification information in the memory 110.

[0203] In step S1620, the electronic device 100 may identify whether the call with the external device 200 is connected after the event occurs. After a threshold time has passed after the event occurs, the electronic device 100 may determine whether to perform a call connection with the external device 200.

[0204] If the call connection with the external device 200 is not performed after the event occurs in step S1620-N, in step S1625, the electronic device 100 may request to call the external device 200. Then, the electronic device 100 may perform step S1620.

[0205] According to various embodiments, in a case where a call connection is not performed although the number of times the call request is made is greater than or equal to the threshold number of times, the electronic device 100 may immediately perform steps S1635 and S1640.

[0206] According to various embodiments, the electronic device 100 may immediately perform steps S1635 and S1640 without performing step S1625.

[0207] If a call connection with the external device 200 is performed after the event occurs in step S1620-Y, the electronic device 100 may delete the event occurrence information from the memory 110 in step S1630. In step S1635, the electronic device 100 may track the user behavior. In step S1640, the electronic device 100 may update the parameter information based on the analysis result of tracking the user behavior. For example, the electronic device 100 may change the weight corresponding to the parameter based on the result of monitoring the user behavior.

[0208] Fig.17 is a flowchart for illustrating operations related to retrying a call connection.

[0209] Fig.17 Steps S1705, S1710, S1715, S1720, S1725, S1730, S1735, and S1740 in may correspond to Fig.16 Therefore, repeated description will be omitted.

[0210] In the case where the call connection with the external device is not performed, in step S1721, the electronic device 100 may determine whether a user instruction for retrying the call connection is received. The electronic device 100 may provide the user (the first user) with a guide UI for retrying the call connection. Then, the user may input an instruction for retrying the call connection into the electronic device 100 through the UI.

[0211] If a user instruction for retrying the call connection is received in step S1721-Y, the electronic device 100 may perform step S1725. If a user instruction for retrying the call connection is not received in step S1721-N, the electronic device 100 may perform steps S1735 and S1740.

[0212] Fig.18 is a diagram for illustrating a call unconnected event.

[0213] Fig.18 Table 1810 in indicates the type, cause, and event content of the call not connected event.

[0214] The type of call unconnected event includes at least one of absence, rejection, connection failure, or others. Absence indicates the following type: the operation of attempting call connection is cancelled after the call connection is attempted. Rejection indicates the following type: an instruction made by the user to reject the call is received after the call connection is attempted. Connection failure may indicate the following type: the call connection is ended despite the failure to receive a predetermined instruction (e.g., a user instruction).

[0215] The reasons for the call unconnected event can be divided according to the type. The reasons for the absence type can be cancellation or time limit exceeded, etc.

[0216] Cancellation means that the user cancels the call connection after attempting the call connection. In the case where a call connection attempt is received from the external device 200, but the second user of the external device 200 directly cancels the call connection attempt, the electronic device 100 can recognize that a call unconnected event (absence) has occurred. In the case where a call connection attempt is attempted with the external device 200, but the first user of the electronic device 100 directly cancels the call connection attempt, the electronic device 100 can recognize that a call unconnected event (absence) has occurred.

[0217] Exceeding the time limit indicates the following situation: the call connection is not completed after the threshold time has passed from the time point of the call connection attempt. When the threshold time has passed, the user can directly cancel the call. In addition, when the threshold time has passed, guidance that the call connection cannot be performed can be provided to the user. If a call connection attempt is received from the external device 200, but the call connection attempt has not been completed for a threshold time, the electronic device 100 can recognize that a call connection failure event (absence) has occurred. If a call connection attempt is made with the external device 200, but the call connection attempt has not been completed for a threshold time, the electronic device 100 can recognize that a call connection failure event (absence) has occurred.

[0218] The reasons for the rejection type can be user rejection, device automatic rejection, etc.

[0219] User rejection may indicate that the user directly rejects the call connection. If a call connection attempt is received from the external device 200, but the first user of the electronic device 100 directly rejects the call connection attempt, the electronic device 100 may recognize that a call unconnected event (rejection) has occurred. If a call connection is attempted with the external device 200, but the second user of the external device 200 directly rejects the call connection attempt, the electronic device 100 may recognize that a call unconnected event (rejection) has occurred.

[0220] Automatic device rejection may refer to the device automatically notifying that a call connection cannot be performed. For example, as an automatic device rejection, there may be an interception function or a do not disturb function at a specific time, etc. If a call connection attempt is received from an external device 200, but the electronic device 100 automatically rejects it, the electronic device 100 may recognize that a call unconnected event (rejection) has occurred. If a call connection attempt is made with an external device 200, but the external device 200 automatically rejects it, the electronic device 100 may recognize that a call unconnected event (rejection) has occurred.

[0221] The reason for the connection failure may be the absence of a signal, etc. In the case where the communication session ends suddenly, it may be that the signal for the connection cannot be searched. If a call connection attempt is received from the external device 200, but a signal for the communication connection is not searched without a predetermined instruction, the electronic device 100 may recognize that a call unconnected event (connection failure) has occurred. If a call connection attempt is made with the external device 200, but a signal for the communication connection is not searched without a predetermined instruction, the electronic device 100 may recognize that a call unconnected event (connection failure) has occurred.

[0222] Other types of reasons may be short calls, etc. In the case where the duration of the phone call is less than a threshold time, the electronic device 100 may determine that the call is not connected normally. An event classified as a short call may be based on the premise that the call connection is performed for a pre-stored contact number.

[0223] If a call connection attempt is received from the external device 200 and the call ends before a threshold time during the call connection, the electronic device 100 may recognize that a call unconnected event (other) has occurred. If a call connection attempt is made with the external device 200 and the call ends before a threshold time during the call connection, the electronic device 100 may recognize that a call unconnected event (other) has occurred.

[0224] Fig.19 is a diagram for illustrating parameters used to calculate importance levels.

[0225] Fig.19 Table 1910 in indicates a plurality of parameters used when calculating the importance level. The electronic device 100 may store weights w1 to w10 corresponding to the respective parameters x1 to x10. The electronic device 100 may apply different parameters according to the type of the call unconnected event.

[0226] According to various embodiments, if an absence event is recognized, the electronic device 100 may calculate the importance level regarding the absence event using only some parameters x1 to x8.

[0227] According to various embodiments, if a rejection event is recognized, the electronic device 100 may calculate the importance level regarding the rejection event using only some parameters x1, x2, x6 to x10.

[0228] According to various embodiments, if a connection failure event is recognized, the electronic device 100 may calculate the importance level regarding the connection failure event using only some parameters x1, x2, x4, x5.

[0229] Fig.19Table 1920 in indicates the process of calculating the importance level according to the type of call unconnected event. If an absence event is identified, the electronic device 100 can calculate the importance level corresponding to the absence event by using x1*w1+x2*w2+x3*w3+x4*w4+x5*w5+x6*w6+x7*w7+x8*w8. If a rejection event is identified, the electronic device 100 can calculate the importance level corresponding to the rejection event by using x1*w1+x2*w2+x6*w6+x7*w7+x8*w8+x9*w9+x10*w10. If a connection failure event is identified, the electronic device 100 can calculate the importance level corresponding to the connection failure event by using x1*w1+x2*w2+x4*w4+x5*w5.

[0230] Fig. 20 A diagram showing status information of a device.

[0231] Fig. 20 Table 2010 in FIG. 2 indicates the state information of the device. The state information of the device may indicate a first state (non-callable state) or a second state (callable state). The device may include at least one of the electronic device 100 and the external device 200.

[0232] When the display of the device is in the on state and a predetermined application (first application group) is being executed, the electronic device 100 may determine that the device is in the first state. For example, the predetermined application (first application group) may include at least one of a game application, a lecture application, a conference application, or a video chat application. The feature that the display is in the on state may refer to a state in which power is supplied to the display and a screen is being displayed.

[0233] When the display of the device is in the off state and a predetermined application (second application group) is being executed, the electronic device 100 may determine that the device is in the second state. For example, the predetermined application (second application group) may include a phone application and the like.

[0234] When the device is executed in a predetermined mode, the electronic device 100 may determine that the device is in the first state. For example, the predetermined mode may include at least one of a focus mode or a do not disturb mode.

[0235] If the device is in the first state, the electronic device 100 may wait. In addition, if the device changes to the second state, the electronic device 100 may provide notification information.

[0236] When the predetermined application is not executed in the device and the device is not executing the predetermined mode, the electronic device 100 can determine that the device is in the second state. In addition, when the device is in the second state, the electronic device 100 can obtain the user's situation information. Then, the electronic device 100 can determine whether to provide notification information about the call unconnected event based on the user's situation information.

[0237] Fig.21 It is a diagram for illustrating an operation of analyzing situation information of a user.

[0238] refer to Fig.21 The electronic device 100 may include at least one of a data collecting module 2110, an analyzing module 2120 for user's situation information, and a storing module 2130 for user's situation information.

[0239] The data collection module 2110 may be a module that acquires various types of data for analyzing situation information of a user.

[0240] The data collection module 2110 may acquire user data. The user data may include at least one of schedule information, reminder information, or email information.

[0241] The data collection module 2110 may acquire the state information of the device. The state information of the device may include at least one of execution information (execution of the application) or location information.

[0242] The data collection module 2110 may acquire surrounding environment information, which may refer to noise information or brightness information recognized around the device.

[0243] The data collection module 2110 may obtain connection information of the external device. The connection information of the external device may include one of the following information: information related to connection with the Internet of Things (IoT), information related to connection with a Metaverse server, or information related to connection with a wearable device.

[0244] The analyzing module 2120 of the user's situation information may analyze the user's situation based on various types of data acquired from the data collecting module 2110 .

[0245] For example, if the schedule included in the user data includes a meeting schedule, the analysis module 2120 may determine that this is a case where the user cannot perform a call connection during the time included in the meeting schedule.

[0246] For example, in a case where the device is executing a predetermined application, the analysis module 2120 may determine that this is a case where the user cannot perform a call connection.

[0247] For example, if the noise included in the surrounding environment information is greater than or equal to a threshold, the analysis module 2120 may determine that this is a situation where the user cannot perform a call connection. If the brightness included in the surrounding environment information is less than a threshold, the analysis module 2120 may determine that this is a situation where the user cannot perform a call connection.

[0248] For example, in the case where the device is connected to the Metaverse server, the analysis module 2120 may determine that this is a case where the user is unable to perform a call connection.

[0249] The storage module 2130 of the user's situation information may store the analysis result acquired from the analysis module 2120. Then, the storage module 2130 may store the analysis result by classifying the analysis result into predetermined categories. The electronic device 100 may update the weight corresponding to the parameter based on the analysis result.

[0250] Fig. 22 A diagram for showing user situation information.

[0251] Fig. 22 Table 2210 in FIG. 2 indicates that the situation information of the user is classified into predetermined categories.

[0252] The first case indicates that this is a case where a call can be made and the call is idle. For example, in a case where the user is near the device and no external event (predetermined event) is recognized, the electronic device 100 may determine that this is the first case.

[0253] The second case indicates that this is a case where a call can be made but the user is busy. For example, when the user is near the device and an external event (movie watching, etc.) is recognized, the electronic device 100 can determine that this is the second case.

[0254] The third case indicates a situation where a call cannot be made and the user is busy. For example, when the user is near the device and recognizes an external event (meeting, etc.), the electronic device 100 may determine that this is the third case.

[0255] The fourth case indicates that this is a case where the user is not near the device. For example, when the location information of the device does not change within a threshold time, the electronic device 100 may determine that this is the fourth case.

[0256] Fig. 22 Table 2220 in indicates whether to provide notification information according to the determined situation. In the first situation or the second situation, the electronic device 100 may provide notification information. In the third situation or the fourth situation, the electronic device 100 may not provide notification information.

[0257] For example, if it is the fourth case at the time point when the call unconnected event occurs but it is the first case at the current time point, the electronic device 100 may provide notification information.

[0258] For example, if it is the third case at the time point when the call unconnected event occurs but it is the first case at the current time point, the electronic device 100 may provide notification information.

[0259] For example, if the fourth case is the case at the time point when the call unconnected event occurs but the third case is the case at the current time point, the electronic device 100 cannot provide notification information.

[0260] Fig.23 1 is a flowchart for illustrating an operation of the electronic device 100 providing notification information based on information received from an external device.

[0261] refer to Fig.23 In step S2305, the electronic device 100 may receive an instruction for call connection. In step S2310, the electronic device 100 may send a signal for call connection to the external device 200. After sending the signal for call connection, in step S2320, the electronic device 100 may identify a call unconnected event. In step S2320, the electronic device 100 may request a callable time from the external device 200. The electronic device 100 may send a signal for requesting a callable time to the second user of the external device 200. Step S2320 is an optional operation and may be omitted.

[0262] The external device 200 may receive a request for a callable time from the electronic device 100. The external device 200 may obtain the situation information of the second user. In step S2330, the external device 200 may determine whether the callable time of the second user is recognized based on the situation information. If the callable time is recognized in step S2330-Y, the external device 200 may send the callable time to the electronic device 100 in step S2335.

[0263] The electronic device 100 may receive the callable time from the external device 200. Then, in step S2340, the electronic device 100 may provide notification information based on the callable time.

[0264] If the callable time is not identified in step S2330-N, in step S2345, the external device 200 may determine whether the second user can answer the call. If in step S2345-N, the second user cannot answer the call, the external device 200 may repeatedly determine whether the second user can answer the call during the threshold time. If in step S2345-Y, the second user can answer the call, in step S2350, the external device 200 may send a notification that the call can be made to the electronic device 100.

[0265] The electronic device 100 may receive a notification that a call is available from the external device 200. Then, in step S2355, the electronic device 100 may provide notification information.

[0266] Fig.24 is a diagram for illustrating that notification information is provided according to importance levels.

[0267] Fig.24 Table 2410 in indicates multiple notification types. The first notification may be a notification provided to the electronic device during the event occurrence time. The second notification may be a notification provided to the electronic device during the reservation time. The third notification may be a notification provided to the electronic device during the callable time. The fourth notification may be a notification provided to the external device during the event occurrence time. The fifth notification may be a notification provided to the external device during the reservation time. The sixth notification may be a notification provided to the external device during the callable time.

[0268] Fig.24 Table 2420 in indicates the notifications provided according to importance level.

[0269] If the importance level is 0 to 30, the electronic device 100 may not store information about the call unconnected event in the memory 110 and may not provide any notification. The electronic device 100 may determine that the event is a spam event or an unimportant event.

[0270] If the importance level is 31 to 40, the electronic device 100 may store information about the call unconnected event in the memory 110. The electronic device 100 may determine that the event is not an event for which a notification needs to be provided, but needs to store information about the event in the memory 110. The information stored in the memory 110 may be used in a later process of updating parameters.

[0271] If the importance level is 41 to 50, the electronic device 100 may store information about the call unconnected event in the memory 110 and provide a first notification.

[0272] If the importance level is 51 to 60, the electronic device 100 may store information about the call unconnected event in the memory 110 and provide a first notification and a second notification.

[0273] If the importance level is 61 to 70, the electronic device 100 may store information about the call unconnected event in the memory 110 and provide first to third notifications.

[0274] If the importance level is 71 to 80, the electronic device 100 may store information about the call unconnected event in the memory 110 , and provide first to third notifications, and transmit a fourth notification to the external device 200 .

[0275] If the importance level is 81 to 90, the electronic device 100 may store information about the call unconnected event in the memory 110 , and provide first to third notifications to the external device 200 , and transmit fourth and fifth notifications to the external device 200 .

[0276] If the importance level is 91 to 100, the electronic device 100 may store information about the call unconnected event in the memory 110 , and provide first to third notifications to the external device 200 , and send fourth to sixth notifications to the external device 200 .

[0277] Meanwhile, the electronic device 100 may perform various notifications providing operations other than the embodiment in Table 2420 .

[0278] Fig.25 is a diagram for illustrating an operation of providing notification information according to various embodiments.

[0279] Fig.25 The UI 2510 in the figure may be a screen provided as notification information. The electronic device 100 may provide notification information including the UI 2510 according to a call unconnected event.

[0280] UI 2510 may include at least one of the following items: text 2511 indicating that notification information is provided based on a call unconnected event, user information 2512 corresponding to an important call, text 2513 indicating that a call unconnected event has occurred, text 2514 indicating a detailed reason for the call unconnected event, a message 2515 from the other party related to the call unconnected event, the other party's callable time 2516, or text 2517 indicating a subsequent notification schedule.

[0281] Fig.26 is a diagram for illustrating an operation of providing notification information according to various embodiments.

[0282] Fig.26 The UI items 2611, 2612, 2613, 2614, 2615 in may correspond to Fig.25 2511, 2512, 2513, 2514, 2515. Therefore, repeated description will be omitted.

[0283] UI 2610 may not correctly include the callable time 2616 associated with the call unconnected event. This is because no information about the callable time is received from the other party. If the other party is available to answer the call, the electronic device 100 can display a notification. UI 2610 may include text 2617 indicating that a notification will be displayed when the other party is available to answer the call.

[0284] Fig. 27 is a diagram for illustrating a user interface (UI) displayed during a call connection according to various embodiments.

[0285] Fig. 27 The UI 2710 in may be a screen displayed in the case where a call connection attempt is received.

[0286] The UI 2710 may include at least one of the following items: a text 2711 notifying the fact that a call is received, user information 2712 corresponding to the other party requesting a call, an item 2713 for accepting the call, items 2714, 2715 for sending a reason for not accepting the call in the form of a message, or an item 2716 for sending a callable time. In the case where the items 2714, 2715, 2716 are selected, a call rejection signal may be automatically sent to the other party.

[0287] Fig.28 is a diagram for illustrating a user interface (UI) displayed during a call connection according to various embodiments.

[0288] Fig.28 The UI items 2811, 2812, 2813 in may correspond to Fig. 27 2711, 2712, 2713 in. Therefore, repeated description will be omitted.

[0289] UI 2810 may include item 2814, which requests user input on whether to automatically send a notification when a call can be made. When user input is received through item 2814, notification information may be provided at a time point when the call can be made. In the case where item 2814 is selected, a rejection call signal may be automatically sent to the other party.

[0290] Fig.29 is a diagram for illustrating an operation of providing notification information according to various embodiments.

[0291] Fig.29The UI 2910 in the figure may be a screen provided as notification information. The electronic device 100 may provide notification information including the UI 2910 according to a call unconnected event.

[0292] UI 2910 may include information about the other party (e.g., Mr. Li) associated with the call unconnected event. In addition, UI 2910 may include item 2911, which indicates the cumulative number of call unconnected events for the other party associated with the call unconnected event. If a call unconnected event is identified and a call connection is performed within a threshold time (30 minutes), the electronic device 100 may change (reduce) the cumulative number. If a user input for selecting item 2911 is received, the electronic device 100 may provide the other party with a screen for attempting a call connection. If a user input for selecting item 2911 is received and the call connection with the other party is successful, the electronic device 100 may initialize the cumulative number.

[0293] Fig.30 is a diagram for illustrating an operation of providing notification information according to various embodiments.

[0294] Fig.30 The UI 3010 in the figure may be a screen provided as notification information. The electronic device 100 may provide notification information including the UI 3010 according to a call unconnected event.

[0295] The UI 3010 may include notification information in the form of a pop-up window 3011. When a screen related to a predetermined application is being displayed, notification information in the form of a pop-up window 3011 may be provided in an upper portion of the screen.

[0296] Fig.31 It is a diagram for illustrating an operation of updating an existing notification information providing model by acquiring parameters.

[0297] Fig.31 Graph 3110 in may represent the number of times data associated with a parameter is stored. Graph 3110 may indicate that data corresponding to the x1 parameter is stored three times, data corresponding to the x2 parameter is stored five times, data corresponding to the x3 parameter is stored four times, data corresponding to the x4 parameter is stored once, and data corresponding to the x5 parameter is stored four times.

[0298] The electronic device 100 may determine the weight corresponding to the parameter based on the accumulated number of times of data corresponding to the parameter.

[0299] Fig.31 Embodiment 3120 in FIG. 1 indicates that the notification information providing model is updated when new data is stored. When new data is acquired, the notification information providing model may be updated based on the new data. The electronic device 100 may classify the types of parameters corresponding to the new data ( Fig.19 Then, the electronic device 100 may update the cumulative number of each type of parameter. Then, the electronic device 100 may update the weight corresponding to the parameter based on the updated cumulative number. Therefore, the electronic device 100 may perform an update operation by changing the weight of the existing model.

[0300] Fig.32 is a flowchart for illustrating an operation of providing notification information by using situation information of a user of an external device.

[0301] refer to Fig.32 In step S3205, the electronic device 100 may receive an instruction for call connection. In step S3210, the electronic device 100 may send a signal for call connection to the external device 200.

[0302] The external device 200 may receive a signal for call connection from the electronic device 100. In step S3215, the external device 200 may receive an instruction for call connection. In step S3220, the external device 200 may send a message for rejecting the call to the electronic device 100.

[0303] The electronic device 100 may receive a message for rejecting a call from the external device 200. When receiving the message for rejecting a call, in step S3225, the electronic device 100 may recognize that a call unconnected event has occurred. In step S3230, the electronic device 100 may request situation information from the external device 200. The situation information may refer to a situation of a second user using the external device 200.

[0304] The external device 200 may receive a request for situation information from the electronic device 100. In step S3235, the external device 200 may acquire the situation information of the second user. In step S3240, the external device 200 may send the situation information of the second user to the electronic device 100.

[0305] The electronic device 100 may receive the situation information of the second user from the external device 200. In step S3250, the electronic device 100 may identify whether the second user is available to answer the call based on the received situation information. If, in step S3250-N, the second user is unable to answer the call, the electronic device 100 may repeatedly determine whether the second user is available to answer the call within a threshold time.

[0306] If, in step S3250-Y, the second user can answer the call, in step S3255, the electronic device 100 may provide notification information.

[0307] In step S3245, the external device 200 may identify whether the situation information of the second user has changed. If the situation information has changed in step S3245-Y, the external device 200 may again send the situation information of the second user to the electronic device 100 in step S3240. Then, the electronic device 100 may perform steps S3250 to S3255.

[0308] Fig.33 is a diagram for illustrating an operation of providing notification information according to various embodiments.

[0309] Fig.33 The UI 3310 in the figure may be a screen provided as notification information. The electronic device 100 may provide notification information including the UI 3310 according to a call unconnected event.

[0310] The UI 3310 may include notification information in the form of a pop-up window 3311. When a screen related to a predetermined application is being displayed, notification information in the form of a pop-up window 3311 may be provided in a lower portion of the screen.

[0311] Fig.34 is a diagram for illustrating an operation of providing notification information according to various embodiments.

[0312] Fig.34 The UI 3410 in the figure may be a screen provided as notification information. The electronic device 100 may provide notification information including the UI 3410 according to a call unconnected event.

[0313] UI 3410 may include notification information 3411 provided in a virtual environment provided by the Metaverse service. Assume that a first user of electronic device 100 is using the Metaverse service. Electronic device 100 may identify a call unconnected event. Electronic device 100 may provide an application related to the Metaverse service so that notification information 3411 is provided in the Metaverse service instead of popping up separately according to a predetermined event.

[0314] Fig.35 is a diagram for illustrating an operation of providing notification information according to various embodiments.

[0315] Fig.35 Screen 3510 in FIG. 35 indicates notification information provided in a locked screen state. If the electronic device 100 is in a locked screen state at the time point when the notification information is provided, the electronic device 100 may control the display to be turned on and provide the notification information. If the user unlocks the screen and activates the top control bar after displaying screen 3510, screen 3520 may be provided.

[0316] Fig.35Screen 3520 in FIG. 35 indicates notification information provided when a user input for activating the top control bar is received. The user input may refer to an input of touching the upper area of ​​the screen and dragging it downward.

[0317] Fig.36 is a diagram for illustrating an operation of providing notification information according to various embodiments.

[0318] Fig.36 The screen 3610 in FIG. 1 may include a guide item provided to the user for filtering information (e.g., phone number, name) related to the call unconnected event. When the user selects the item 3611 corresponding to the important call, the electronic device 100 may identify the event corresponding to the important call among the multiple call unconnected events.

[0319] Then, the electronic device 100 may display information (eg, phone number, name) about the recognized event in a separate area 3621. In addition, the electronic device 100 may display an icon 3622 corresponding to the recognized event in an area indicating the recognized event.

[0320] Fig.37 is a flowchart for illustrating a method of controlling the electronic device 100 according to various embodiments.

[0321] refer to Fig.37 According to an embodiment of the present disclosure, the method for controlling the electronic device 100 may include the following steps: requesting a call connection from the external device 200 (S3705); and based on identifying a call unconnected event stored in the electronic device 100 after requesting the call connection, calculating an importance level corresponding to the call unconnected event (S3710); and based on the importance level being greater than or equal to a threshold, acquiring status information of the electronic device 100, the status information indicating an application being executed in the electronic device 100 (S3715); and based on identifying that a predetermined application is not being executed in the electronic device 100 according to the status information, acquiring a notification time based on situation information of a user of the electronic device 100 (S3720); and providing notification information indicating a call unconnected event based on the notification time (S3725).

[0322] At the same time, in step S3710 of obtaining the importance level, if a call unconnected event is identified, at least one of the contact number level information of the external device 200 or the communication frequency with the external device 200 can be obtained, and the importance level can be calculated based on at least one of the contact number level information or the communication frequency.

[0323] At the same time, in step S3710 of obtaining the importance level, if a call unconnected event is identified, a first parameter corresponding to the contact number level information and a second parameter corresponding to the communication frequency can be obtained, and the importance level can be calculated based on the first parameter, the first weight corresponding to the first parameter, the second parameter, and the second weight corresponding to the second parameter.

[0324] Meanwhile, in step S3710 of acquiring importance level, the category of the call unconnected event may be identified, and the importance level may be calculated based on the identified category, and the category may include at least one of an event during absence, a rejection event, or a connection failure event.

[0325] Meanwhile, the predetermined application may be an application that performs a function that cannot be performed simultaneously with the call connection function.

[0326] At the same time, in step S3720 of obtaining the notification time, based on the recognition that the predetermined application is not being executed, it can be recognized whether the user input is received from the external device 200 within the threshold time, and based on the recognition that the user input is received from the external device 200 within the threshold time, the notification time can be set to the current time point.

[0327] At the same time, in step S3720 of obtaining the notification time, based on the recognition that the scheduled application is not being executed, the user's schedule information can be obtained, and based on the fact that there is no schedule scheduled at the current time point according to the user's schedule information, the notification time can be set to the current time point, and based on the fact that there is a schedule scheduled at the current time point according to the user's schedule information, the notification time can be set to the time point when the scheduled schedule ends.

[0328] Meanwhile, in the control method, based on receiving a user input for a call connection with the external device 200 through the notification information, the call connection with the external device 200 may be re-requested.

[0329] Meanwhile, the notification information may include at least one of a reason for a call unconnected event, a message received from the external device 200, a callable time, or a notification time.

[0330] Meanwhile, in the step S3725 of providing notification information, a callable time may be received from the external device 200, and notification information including the callable time may be provided.

[0331] at the same time, Fig.37 The control method of the electronic device in the embodiment can be Figure 1 or Figure 2 The method may be executed on an electronic device having the configuration in , and may also be executed on electronic devices having other configurations.

[0332] Meanwhile, the methods according to the aforementioned various embodiments of the present disclosure may be implemented in the form of an application that can be installed on a conventional electronic device.

[0333] Furthermore, the methods according to the aforementioned various embodiments of the present disclosure may be implemented only by software upgrade or hardware upgrade of a conventional electronic device.

[0334] In addition, the aforementioned various embodiments of the present disclosure may also be executed by an embedded server disposed on the electronic device, or an external server of at least one of the electronic device or the display device.

[0335] At the same time, according to an embodiment of the present disclosure, the aforementioned various embodiments may be implemented as software, which includes instructions stored in a machine-readable storage medium, which can be read by a machine (e.g., a computer). A machine refers to a device that calls instructions stored in a storage medium and can operate according to the called instructions, and the device may include the electronic device of the aforementioned embodiment. In the case where the instructions are executed by a processor, the processor may perform the functions corresponding to the instructions by itself, or use other components under its control to perform the functions corresponding to the instructions. The instructions may include code generated or executed by a compiler or interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. The term "non-transitory" only means that the storage medium does not include a signal and is tangible, but does not indicate whether the data is stored in the storage medium semi-permanently or temporarily.

[0336] In addition, according to an embodiment of the present disclosure, the method according to the aforementioned various embodiments may be provided by being included in a computer program product. A computer program product refers to a product that can be traded between a seller and a buyer. The computer program product may be distributed online in the form of a machine-readable storage medium (e.g., a compact disk read-only memory (CD-ROM)), or through an application store (e.g., Play Store TM ) Online distribution. In the case of online distribution, at least a portion of the computer program product may be at least temporarily stored in a storage medium (such as a memory of a manufacturer's server, an application store's server, and a relay server), or may be temporarily generated.

[0337] In addition, each component (e.g., module or program) according to the aforementioned various embodiments may be composed of a single object or multiple objects. In addition, among the aforementioned corresponding subcomponents, some subcomponents may be omitted, or other subcomponents may also be included in various embodiments. Alternatively or additionally, some components (e.g., modules or programs) may be integrated into one object, and the functions performed by each component before integration are performed in the same or similar manner. The operations performed by modules, programs or other components according to various embodiments may be performed sequentially, in parallel, repeatedly or heuristically. Alternatively, at least some operations may be performed in a different order or omitted, or other operations may be added.

[0338] In addition, although the preferred embodiments of the present disclosure have been shown and described, the present disclosure is not limited to the aforementioned specific embodiments, and it is obvious that various modifications can be made by a person skilled in the art of the present disclosure without departing from the subject matter of the present disclosure as claimed in the appended claims. In addition, it is intended that these modifications should not be interpreted independently of the technical concept or prospect of the present disclosure.

Claims

1. An electronic device, comprising: Memory; Communication interface; monitor; as well as At least one processor configured to: requesting a call connection from an external device via the communication interface, calculating an importance level corresponding to the call unconnected event based on recognizing the call unconnected event stored in the memory after requesting the call connection, Based on the importance level being greater than or equal to a threshold, acquiring status information of the electronic device, the status information indicating an application being executed in the electronic device, Based on recognizing that the predetermined application is not being executed in the electronic device according to the state information, acquiring the notification time based on the situation information of the user of the external device, and The display is controlled to provide notification information indicating the call unconnected event based on the notification time.

2. The electronic device according to claim 1, in, The at least one processor is configured to: Based on identifying the call unconnected event, obtaining at least one of the contact number level information of the external device or the communication frequency with the external device, and The importance level is calculated based on at least one of the contact number level information or the communication frequency.

3. The electronic device according to claim 2, in, The at least one processor is configured to: Based on identifying the call unconnected event, acquiring a first parameter corresponding to the contact number level information and a second parameter corresponding to the communication frequency, and The importance level is calculated based on the first parameter, a first weight corresponding to the first parameter, the second parameter, and a second weight corresponding to the second parameter.

4. The electronic device according to claim 1, in, The at least one processor is configured to: identifying a category of the call not connected event, and Based on the identified categories, calculating the importance level, and The categories include: At least one of an absence event, a rejection event, or a connection failure event.

5. The electronic device according to claim 1, in, The predetermined application is an application that performs a function that cannot be performed simultaneously with the call connection function.

6. The electronic device according to claim 1, in, The at least one processor is configured to: Based on recognizing that the predetermined application is not being executed, recognizing whether an input of the user is received from the external device within a threshold time, and The notification time is set to a current time point based on recognizing that the user's input is received from the external device within the threshold time.

7. The electronic device according to claim 6, in, The at least one processor is configured to: acquiring the user's schedule information based on recognizing that the predetermined application is not being executed, Based on the fact that there is no scheduled schedule at the current time point according to the schedule information of the user, setting the notification time to the current time point, and Based on the existence of a scheduled schedule at the current time point according to the schedule information of the user, the notification time is set to the time point when the scheduled schedule ends.

8. The electronic device according to claim 1, in, The at least one processor is configured to: Based on receiving a user input for a call connection with the external device through the notification information, a call connection with the external device is re-requested through the communication interface.

9. The electronic device according to claim 1, in, The notification information includes at least one of the following: The cause of the call unconnected event, the message received from the external device, the callable time, or the notification time.

10. The electronic device according to claim 1, in, The at least one processor is configured to: receiving a callable time from the external device through the communication interface, and The display is controlled to provide notification information including the callable time.

11. A method for controlling an electronic device, the method comprising: Request a call connection from an external device; calculating an importance level corresponding to the call unconnected event based on identifying a call unconnected event stored in the electronic device after requesting the call connection; Based on the importance level being greater than or equal to a threshold, acquiring status information of the electronic device, the status information indicating an application being executed in the electronic device; acquiring a notification time based on situation information of a user of the external device, based on recognizing, according to the state information, that a predetermined application is not being executed in the electronic device; as well as Notification information indicating the call unconnected event is provided based on the notification time.

12. The control method according to claim 11, in, Obtaining the importance level includes: Based on identifying the call unconnected event, acquiring at least one of contact number level information of the external device or a communication frequency with the external device; and The importance level is calculated based on at least one of the contact number level information or the communication frequency.

13. The control method according to claim 12, in, Obtaining the importance level includes: Based on identifying the call unconnected event, acquiring a first parameter corresponding to the contact number level information and a second parameter corresponding to the communication frequency; and The importance level is calculated based on the first parameter, a first weight corresponding to the first parameter, the second parameter, and a second weight corresponding to the second parameter.

14. The control method according to claim 11, in, Obtaining the importance level includes: identifying a category of the call not connected event; and Based on the identified categories, calculating the importance level, and The categories include: At least one of an absence event, a rejection event, or a connection failure event.

15. The control method according to claim 11, in, The predetermined application is an application that performs a function that cannot be performed simultaneously with the call connection function.

Images