Electronic device and method for blocking call

Abstract

This electronic device may comprise a processor, and a memory for storing instructions. When the instructions are executed by the processor, the electronic device can control that: a list of blocked call numbers is stored; a phone number related to a first message is identified on the basis of the first message for call reception being received; whether the phone number related to the first message is included in the list of blocked call numbers is identified; and, on the basis of the phone number related to the first message being included in the list of blocked call numbers, a second message for rejecting call reception is transmitted to an external device in a state in which at least one of operations for call connection is not performed.

Description

Electronic devices and methods for call blocking

[0001] This document relates to electronic devices, and more specifically, to electronic devices and methods for connecting and blocking calls. The electronic devices may include mobile communication terminals.

[0002] Wireless communication systems can provide wireless communication for electronic devices to ensure the mobility (or activity) of users carrying them. For example, wireless communication may include communication technologies in which a transmitting device and a receiving device transmit and / or receive signals (or data) via radio resources (e.g., frequency and / or time). Wireless communication systems are expanding their scope beyond voice services to include data services.

[0003] With the increasing penetration of mobile devices, they have become an essential part of modern life. These devices can now provide not only their own voice call services, but also various data transmission services and various additional services, transforming them into functionally multimedia communication devices.

[0004] Mobile terminals may include call blocking features. Recently, various additional features have been added to mobile terminals, such as automatically blocking calls without the recipient answering if the caller's number is a pre-configured call blocking number on the receiving terminal.

[0005] The receiving terminal can confirm that a call has been received from the calling terminal by receiving the SIP (session initiation protocol) message 'INVITE'. The receiving terminal can receive the SIP message at the IMS (IP Multimedia Subsystem) layer and send call-related messages (e.g., 100 Trying, 183 Session Progress, 180 Ringing). During this process, the receiving terminal can transmit information about the call reception or call incoming to the call-related application.

[0006] The receiving terminal can transmit call information to the call-related application and be assigned a bearer for communication. The application can determine whether the number is blocked by the user based on the call incoming information. If the incoming number is blocked, the application can reject the call by sending a rejection response to the IMS without notifying the user.

[0007] The IMS endpoint can receive a rejection response from the call-related application and send a message (e.g., 486 Reject) to the calling terminal. This can result in resource waste, as the receiving terminal must then send call-related messages (e.g., 100 Trying, 183 Session Progress, 180 Ringing) for the ultimately rejected call and allocate a bearer for communication.

[0008] An electronic device may include a processor and a memory storing instructions. The instructions, when executed by the processor, may cause the electronic device to store a list of blocked numbers, determine a phone number associated with a first message regarding a call reception based on receipt of a first message, determine whether the phone number associated with the first message is included in the list of blocked numbers, and transmit a second message rejecting a call reception to an external device without performing at least one of the operations for connecting a call based on whether the phone number associated with the first message is included in the list of blocked numbers.

[0009] In the method of operation, the method may include: an operation of storing a list of numbers to be blocked from receiving calls; an operation of checking a phone number associated with a first message based on receipt of a first message for receiving a call; an operation of checking whether the phone number associated with the first message is included in the list of numbers to be blocked from receiving calls; and an operation of transmitting a second message to an external device for rejecting a call reception without performing at least one of the operations for connecting a call based on the phone number associated with the first message being included in the list of numbers to be blocked from receiving calls.

[0010] The storage medium includes a processor, a memory storing a list of blocked numbers, and the memory stores instructions, which instructions, when executed by the processor, cause the electronic device to store the list of blocked numbers, determine a phone number associated with the first message based on receipt of a first message for incoming calls, determine whether the phone number associated with the first message is included in the list of blocked numbers, and transmit a second message rejecting incoming calls to an external device without performing at least one operation among operations for call connection based on the phone number associated with the first message being included in the list of blocked numbers.

[0011] The electronic device and method of operation according to this document can prevent waste of resources by transmitting call-related messages (e.g., 100Trying, 183 Session Progress, 180 Ringing) or a rejection message without assigning a bearer for communication when a call is received from a blocked number.

[0012] The electronic device and the operating method according to this document can prevent resource waste by checking the block number list in a call-related application as well as checking the block number list at the IMS end of the receiving terminal.

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

[0014] FIG. 2a illustrates a process in which an electronic device within a network environment establishes a call connection with an external device according to a comparative example.

[0015] FIG. 2b illustrates a process in which an electronic device within a network environment according to a comparative example blocks a call connection with an external device.

[0016] Figure 3 is a block diagram showing the configuration of an electronic device according to one embodiment.

[0017] FIG. 4 illustrates a process in which an electronic device according to various embodiments of the present document blocks a call connection with an external device.

[0018] FIG. 5 is a flowchart illustrating a method for an electronic device according to one embodiment to block a call connection with an external device.

[0019] FIG. 6 is a flowchart illustrating an operation of an electronic device according to one embodiment to block a call connection with an external device.

[0020] FIGS. 7A and 7B illustrate an embodiment in which an electronic device according to one embodiment blocks a call connection with an external device and displays this to a user.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0049] FIG. 2a illustrates a process in which an electronic device within a network environment establishes a call connection with an external device according to a comparative example.

[0050] According to various embodiments referring to FIG. 2A, an electronic device (101) may receive a request message (e.g., invite) related to a call connection from an external device (104). Hereinafter, the electronic device (101) may include a receiving terminal (mobile terminated, MT). The external device (104) may include a transmitting terminal (mobile oriented, MO).

[0051] A request message (e.g., invite) related to a call connection may be transmitted to an electronic device (101) via a server (108) (operation 211). The electronic device (101) may include an IMS (Internet Protocol (IP) multimedia subsystem) layer that supports IMS functions. For example, a request signal (e.g., an invite message) related to a call connection may include information (e.g., an application) related to a call function with an external device (104). For example, a call connection event may be generated based on at least one of the execution of an application program or function related to a call, an input related to a call connection, the reception of a signal related to a call connection, or the acquisition of movement information related to a call connection. The IMS (IP multimedia subsystem) may refer to an architecture for providing various multimedia services such as voice, video, and messaging in an IP (Internet Protocol) network. The architecture may refer to rules for how components of a communication system (e.g., MO, MT, and network server) interact with each other. IMS can provide not only voice calls but also video calls, messaging, and multimedia content sharing capabilities.

[0052] Session Description Protocol (SDP) can refer to a protocol that determines the media type associated with a multimedia session between terminals. SDP can operate in an offer-and-answer structure. The SDP offer can include a request signal related to a call connection (e.g., an invite message). The SDP answer can include information related to the call connection tone (e.g., 180 ringing) or information related to the acceptance of the call connection (e.g., 200 OK).

[0053] According to various embodiments, the electronic device (101) may transmit information related to a call connection tone (e.g., 180 ringing) to the external device (104) via the server (108) based on receipt of a request signal related to a call connection (operation 213). For example, the call connection tone may refer to a signal tone played until the electronic device (101) accepts or rejects a call connection with the external device (104).

[0054] According to various embodiments, the electronic device (101) may transmit information related to acceptance of the call connection (e.g., 200 ok) to the external device (104) via the server (108) based on acceptance of the call connection (operation 215).

[0055] According to various embodiments, the external device (104) may transmit a response signal (e.g., ACK) to the electronic device (101) via the server (108) regarding information related to acceptance of a call connection received from the electronic device (101) (operation 217).

[0056] According to various embodiments, the electronic device (101) and the external device (104) may establish a call connection and a data channel with the server (108) based on information and a response signal related to acceptance of the call connection (operation 219). For example, the data channel may include an IMS data channel established between the electronic device (101), the external device (104), and the server (108). For example, the call connection between the electronic device (101) and the external device (104) may include a call connection based on a long term evolution (LTE) communication method or a new radio (NR) communication method (e.g., VoLTE or VoNR).

[0057] FIG. 2b illustrates a process in which an electronic device within a network environment according to a comparative example blocks a call connection with an external device.

[0058] According to various embodiments referring to FIG. 2B, the electronic device (101) may receive a request signal (e.g., an invite message) related to a call connection from an external device (104). The request signal (e.g., an invite message) related to the call connection may be transmitted to the electronic device (101) via a server (108) (operation 221). The electronic device (101) may include an IMS layer that supports IMS (internet protocol (IP) multimedia subsystem) functions.

[0059] In one embodiment, the server (108) may transmit a message (e.g., 100 trying) to the external device (104) indicating that it is processing a call request (operation 223). The electronic device (101) may transmit a message (e.g., 183 session progress) to the server (108) indicating that a media stream has started in the session (operation 225).

[0060] In one embodiment, the external device (104) may receive a message indicating that a media stream has started (e.g., 183 Session Progress) and transmit an acknowledgment for the received message to the electronic device (101). The external device (104) may transmit a message related to the acknowledgment (e.g., PRACK (Provisional Response ACKnowledgement)) to the electronic device (101) (operation 227). The PRACK (provisional response acknowledgment) may be used to send an acknowledgment for an intermediate response (e.g., 180 ringing or 183 session progress) in a SIP communication.

[0061] According to one embodiment, the electronic device (101) may transmit a message (e.g., 200 ok) to the external device (104) via the server (108) indicating that the call request was successfully received based on receiving a message (e.g., PRACK) related to an acknowledgement response (act 229).

[0062] According to one embodiment, the electronic device (101) may request the server (108) to allocate a bearer for a call with the external device (104) (operation 231). The electronic device (101) may request the server (108) to allocate a dedicated bearer. Unlike the default bearer, the dedicated bearer may be individually configured for a specific service or application. For example, the server (104) may configure a dedicated bearer for real-time applications such as Voice over IP (VoIP) or video streaming. Since real-time applications such as Voice over IP (VoIP) or video streaming are sensitive to latency or packet loss, the dedicated bearer can meet the requirements.

[0063] According to one embodiment, the electronic device (101) may transmit a message (e.g., 180 ringing) to the external device (104) indicating that a phone is ringing based on a bearer being assigned (act 233).

[0064] In one embodiment, the electronic device (101) may transmit a message (e.g., 486 busy here) to the external device (104) indicating that a call has not been received based on the number of the external device (104) being included in a block number list (operation 235). The external device (104) may receive the message (e.g., 486 busy here) indicating that a call has not been received and transmit a message (e.g., ACK) indicating that a call has been received to the electronic device (101) (operation 237).

[0065] The electronic device (101), the external device (104), and the server (108) may perform operations 221 to 237. In this process, if the number of the external device (104) is a reception-blocking number, operations 225, 227, 229, 231, and 233 may be unnecessary. Since the electronic device (101) has difficulty in checking in advance whether the number of the external device (104) is a reception-blocking number, the electronic device (101) may perform operations 225, 227, 229, 231, and 233 for call waiting. If operations 225, 227, 229, 231, and 233 are performed for call waiting to be rejected, unnecessary resource waste may occur in the electronic device (101) and the server (108).

[0066] The electronic device (101) and method according to this document can control not to perform operations 225, 227, 229, 231, and 233 when the number of the external device (104) from which a call connection is requested is included in the reception blocking list. The electronic device (101) according to this document can check in advance, at the IMS end of the electronic device (101), whether the number of the external device (104) from which a call connection is requested is included in the reception blocking list, and control not to perform preliminary operations for call connection (e.g., operations 225, 227, 229, 231, and 233).

[0067] According to one embodiment, the electronic device (101) can save resources of the electronic device (101) and the server (108) by controlling not to perform pre-operations for call connection (e.g., operations 225, 227, 229, 231, and 233). Hereinafter, operations of the electronic device (101) for saving resources will be described.

[0068] Figure 3 is a block diagram showing the configuration of an electronic device according to one embodiment.

[0069] Referring to FIG. 3, according to various embodiments, the electronic device (101) may include a processor (300), a communication circuit (310), and / or a memory (320). According to one embodiment, the processor (300) may be substantially the same as the processor (120) of FIG. 1 or may be included in the processor (120). The communication circuit (310) may be substantially the same as the wireless communication module (192) of FIG. 1 or may be included in the wireless communication module (192). The memory (320) may be substantially the same as the memory (130) of FIG. 1 or may be included in the memory (130).

[0070] According to one embodiment, the processor (300) may control operatively, functionally and / or electrically connected communication circuitry (310) and / or memory (320). According to one embodiment, the processor (300) may include an application processor (AP) (e.g., the main processor (121) of FIG. 1) and / or a communication processor (CP) (e.g., the auxiliary processor (123) or the communication module (190) of FIG. 1).

[0071] According to one embodiment, the processor (300) may control the communication circuit (310) to establish a call connection and data channel with the external device (104). When the occurrence of a call connection event related to the external device (104) is detected, the processor (300) may control the communication circuit (310) to connect the call with the external device (104) via the server (108).

[0072] According to one embodiment, the processor (300) may control the communication circuit (310) to transmit and / or receive information (or data) related to an application program through a data channel with the external device (104) while a call is connected between the electronic device (101) and the external device (104).

[0073] According to one embodiment, the memory (320) may store various data used by at least one component of the electronic device (101) (e.g., the processor (300) and / or the communication circuit (310)). For example, the data may include status information related to an application program. According to one embodiment, the memory (320) may store instructions that may be executed by the processor (300).

[0074] According to one embodiment, the electronic device (101) may support IMS (Internet Protocol (IP) multimedia subsystem) functionality.

[0075] According to one embodiment, the electronic device (101) may include a memory (320). The memory (320) may store instructions. The instructions may be executed by the processor (300). When executed by the processor (300), the instructions may control the electronic device (101) to perform the following operations.

[0076] According to one embodiment, the electronic device (101) can confirm the number of the received call based on receiving a message regarding a call reception from an external device. The electronic device (101) can control the IMS layer to obtain a list of block numbers stored in the memory (320). The electronic device (101) can control the IMS layer to check whether the number of the received call is included in the block number list. The electronic device (101) can transmit a message to the external device for rejecting the call reception without performing operations for preparing a call connection establishment based on whether the number of the received call is included in the block number list. The operations for preparing a call connection establishment may include, for example, operations 225, 227, 229, 231, and 233 of FIG. 2B. Hereinafter, the processor (300) is a component of the electronic device (101), and the operations of the processor (300) can be understood as being performed by the electronic device (101).

[0077] According to one embodiment, the processor (300) (or the electronic device (101)) may transmit information about a call received on an application related to a call and, based on an instruction of the application, may transmit a message to the external device rejecting the call. The processor (300) may not request allocation of a bearer for exchanging data with the external device when preparing to transmit a message to the external device rejecting the call. A bearer may refer to a communication channel for ensuring Quality of Service (QoS). A bearer may be allocated by a network or server (108) with which a communication connection has been established. The processor (300) may use the bearer to connect a session to a specific network resource. Here, the session may include a session used by an application of the electronic device (101) to transmit traffic (e.g., IP flow). The processor (300) may use the bearer to maintain a quality of service including at least one of bandwidth, latency, or packet loss.

[0078] According to one embodiment, the processor (300) may control not to transmit a message indicating session progress and a message indicating that a call connection tone is ringing on the electronic device in a situation where it is preparing to transmit a message refusing a call reception to an external device.

[0079] According to one embodiment, the processor (300) may transmit a message to the external device rejecting the call reception based on the number of the received call being included in the list of blocked numbers, and may transmit a message indicating to the application that the call reception of the external device has been rejected.

[0080] According to one embodiment, the processor (300) can confirm the number of a received call by parsing the header of a SIP (session initiation protocol) message. SIP (Session Initiation Protocol) is a protocol used in Internet communications such as VoIP (Voice over IP), and can perform the role of initiating, modifying, and terminating a session. A SIP message can be composed of a header and a body. The header is located at the beginning of the SIP message, and the body can be used optionally. The header can be used in request and response messages. Parsing can refer to the process of interpreting and processing header fields.

[0081] The processor (300) can confirm the number of the received call by parsing the header of the SIP (session initiation protocol) message. The processor (300) can transmit the number of the confirmed call to the IMS layer. The IMS layer can confirm whether the number of the confirmed call is a blocked number. The IMS layer can obtain information about the blocked number from the memory (320) or a database (DB) related to the call. Based on the fact that the number of the confirmed call is a blocked number, the IMS layer can transmit a message to the external device rejecting the call reception without performing operations to prepare for establishing a call connection.

[0082] According to one embodiment, the processor (300) may display a notification on the display indicating that a call was received from a blocked number based on the call reception of the external device being rejected, and that the received call was automatically rejected.

[0083] According to one embodiment, the processor (300) may transmit a list of blocked numbers stored on the memory (320) to the IMS terminal, and transmit information about a received call to an application related to the call based on the IMS terminal's inability to access the list of blocked numbers stored on the memory.

[0084] According to one embodiment, the processor (300) may transmit information about a received call to an application based on whether the number of the received call is included in a list of blocked numbers, and request allocation of a bearer for exchanging data with an external device.

[0085] According to one embodiment, the processor (300) may notify the call-related application that a call has been received if the number of the received call is included in the list of blocked numbers. If the number of the received call is a blocked number, the IMS may, depending on the settings, transmit relevant information to the call-related application. The relevant information may include information indicating that the number of the received call is a blocked number. Alternatively, the IMS may, depending on the settings, reject a call from an external device without notifying the call-related application.

[0086] If the call-related application is configured to forward relevant information, the IMS can wait for a response from the call-related application without performing any actions necessary to establish a call connection. If the call-related application is configured not to forward relevant information, the IMS can send a call rejection message to the external device from which the call originated based on the call rejection message received from the call-related application.

[0087] FIG. 4 illustrates a process in which an electronic device according to various embodiments of the present document blocks a call connection with an external device.

[0088] A system for call connection may include an electronic device (101), an external device (104), and a server (108). The electronic device (101) may include a receiving terminal (mobile terminated, MT) as described in FIG. 1. The external device (104) may include a transmitting terminal (mobile originated, MO). The server (108) may include a server for an application related to call connection.

[0089] According to FIG. 4, the electronic device (101) may receive a message (e.g., invite) regarding a call connection request sent from an external device (104) via the server (108) (operation 402). The server (108) may receive the message (e.g., invite) regarding the call connection request from the external device (108) and transmit the message (e.g., invite) regarding the call connection request to the electronic device (101). In addition, the server (108) may transmit a message (e.g., 100 trying) indicating that it is processing the call request to the external device (104) (operation 404).

[0090] Unlike FIG. 2b according to the comparative example, the electronic device (101) of FIG. 4 can check whether the number of a call received at the IMS (IP multimedia subsystem) layer is a block number.

[0091] According to one embodiment, the electronic device (101) can check the number of the received call and obtain information about the block number from a memory (e.g., memory (320) of FIG. 3 or memory (130) of FIG. 1).

[0092] In one embodiment, the electronic device (101) may determine to reject the call based on the number of the received call being identified as a blocked number. Based on the determination to reject the call, the electronic device (101) may transmit a related message (e.g., 486 busy here) to the external device (104) (operation 406).

[0093] The electronic device according to the comparative embodiment of FIG. 2B has a limitation in performing operations 225, 227, 229, 231, and 233 in advance because it cannot check whether the number of the received call is a blocked number. On the other hand, the electronic device (101) according to various embodiments of the present document can check in advance whether the number of the received call is a blocked number, and can wait without performing operations 225, 227, 229, 231, and 233 while waiting for a response from the server (108). If the electronic device (101) waits without performing operations 225, 227, 229, 231, and 233, it can avoid wasting resources. Since the electronic device (101) does not request allocation of a bearer to the server (108), the resources of the server (108) can also be saved.

[0094] Specifically, the electronic device (101) according to various embodiments of the present document may not transmit a message indicating that a media stream has started (e.g., 183 session progress) if it is determined that the number of the received call is a blocked number (operation 225 of FIG. 2b). The external device (104) may not transmit a message related to an acknowledgment response (e.g., PRACK) if the message indicating that a media stream has started (e.g., 183 session progress) is not received (operation 227 of FIG. 2b). The electronic device (101) may not transmit a message indicating that a call request has been successfully received (e.g., 200 ok) if it does not receive a message related to an acknowledgment response (operation 229 of FIG. 2b).

[0095] Additionally, the electronic device (101) may not request bearer allocation to the server (108) if the number of the received call is determined to be a blocked number (operation 231 of FIG. 2B). The electronic device (101) may not transmit a message indicating that the phone is ringing (e.g., 180 ringing) to the external device (104) if the number of the received call is determined to be a blocked number (operation 233 of FIG. 2B). In this way, the electronic device (101) may control operations 225, 227, 229, 231, and 233 not to be executed, thereby saving resources of the electronic device (101) and the server (108).

[0096] In one embodiment, the electronic device (101) may transmit a message (e.g., 486 busy here) to the external device (104) indicating that a call has not been received based on the number of the external device (104) being included in a block number list (operation 406). The external device (104) may receive the message (e.g., 486 busy here) indicating that a call has not been received and transmit a message (e.g., ACK) indicating that a call has been received to the electronic device (101) (operation 408).

[0097] FIG. 5 is a flowchart illustrating a method for an electronic device according to one embodiment to block a call connection with an external device.

[0098] The operations described through FIG. 5 may be implemented based on instructions that may be stored in a computer recording medium or memory (e.g., memory (130) of FIG. 1). The illustrated method (500) may be executed by an electronic device (e.g., electronic device (101) of FIG. 1) described above through FIGS. 1 to 4, and the technical features described above will be omitted below. The order of each operation of FIG. 5 may be changed, some operations may be omitted, and some operations may be performed simultaneously.

[0099] In operation 502 of FIG. 5, the electronic device (101) may receive a request message (e.g., invite) for a call or call connection.

[0100] In operation 510 of FIG. 5 , the electronic device (101) can determine whether the received request message (e.g., invite) is for a call. The request message (e.g., invite) may include, for example, a request to initiate one of text, video, or call. The electronic device (101) can determine whether the request message is for a call among text, video, or call. If the request message is not for a call, the electronic device (101) can terminate the process of FIG. 5 .

[0101] In operation 512 of FIG. 5, the electronic device (101) may check a list of block numbers based on the confirmation that the received message is a call request message. Information about the block numbers may be stored in the memory (130). The electronic device (101) may obtain the information or list about the block numbers stored in the memory (130) and transmit it to the IMS layer.

[0102] In operation 520, the electronic device (101) can determine whether the number of the received call is a blocked number. The electronic device (101) can compare the number of the received call with a list of blocked numbers stored in the memory (130).

[0103] According to one embodiment, the electronic device (101) may establish a call connection by performing the operations mentioned in FIG. 2A (e.g., operations 213 and 215 of FIG. 2A) based on whether the number of the received call is not a blocked number. If the number of the received call is not a blocked number, the electronic device (101) may terminate the operation of FIG. 5.

[0104] In operation 522, the electronic device (101) may transmit a message (e.g., 486 busy here) to an external device (e.g., the external device (104) of FIG. 4) indicating that reception was not made based on the number of the received call being a blocked number. The electronic device (101) may transmit the message (e.g., 486 busy here) indicating that reception was not made and terminate the operation of FIG. 5.

[0105] FIG. 6 is a flowchart illustrating an operation of an electronic device according to one embodiment to block a call connection with an external device.

[0106] The operations described through FIG. 6 can be implemented based on instructions that can be stored in a computer recording medium or memory (e.g., memory (130) of FIG. 1). The illustrated method (600) can be executed by the electronic device described above through FIGS. 1 to 4 (e.g., electronic device (101) of FIG. 1), and the technical features described above will be omitted below. The order of each operation of FIG. 6 can be changed, some operations can be omitted, and some operations can be performed simultaneously.

[0107] In operation 610, the electronic device (101) can check the number of the received call. The processor can check the number of the received call by parsing the header of the SIP (session initiation protocol) message.

[0108] In operation 620, the electronic device (101) can load a list of block numbers from the memory (130). The IMS (IP multimedia subsystem) of the electronic device (101) can obtain the list of block numbers. The block numbers can be input by the user and stored in the memory (130).

[0109] In operation 630, the electronic device (101) can check whether the number of the received call is included in the list of blocked numbers. The operation of checking the list of blocked numbers can be performed in the IMS (IP multimedia subsystem) of the electronic device (101).

[0110] In operation 640, the electronic device (101) may transmit a call rejection message (e.g., 486 reject) to the external device without performing operations to prepare for establishing a call connection. The operations to prepare for establishing a call connection may include, for example, 100 Trying, 183 Session Progress, and 180 Ringing. Additionally, the operations to prepare for establishing a call connection may include a bearer allocation operation. A bearer may refer to a communication channel of the Session Initiation Protocol (SIP). A bearer may be used to connect a user's data session to a specific network resource so that the data stream can maintain a quality of service. The quality of service may include, for example, one of fixed bandwidth, latency, or packet loss. The call rejection message (e.g., 486 reject) may be one of the SIP response codes. The call rejection message may be used to convey that a call cannot be received.

[0111] According to one embodiment, the processor (300) may transmit a message to an external device rejecting a call reception based on the number of the received call being included in the list of blocked numbers, and may transmit a message indicating to the application that the call reception of the external device has been rejected.

[0112] The processor (300) may display a notification on the display indicating that a call was received from a blocked number based on the rejection of a call reception from an external device and that the received call was automatically rejected.

[0113] FIGS. 7A and 7B illustrate an embodiment in which an electronic device blocks a call connection with an external device and displays this to a user of the electronic device, according to one embodiment.

[0114] In Figure 710 of Figure 7a, a processor (e.g., processor (300) of Figure 3) may receive a call from an external device and, if rejected, display an indicator (712) indicating that the received call has been rejected.

[0115] In Figure 714, the processor (300) may display a notification on the display indicating that a call was received from a blocked number based on the call reception of the external device being rejected, and that the received call was automatically rejected.

[0116] In Figure 720, the processor (300) may display a record of when a rejected call was received based on a user input on an indicator (712) for the rejected call. Furthermore, the processor (300) may display an indicator (722) asking whether to continue rejecting calls in the future. The processor (300) may store the number of the rejected call in a call blocking list based on a user input on the indicator (722) asking whether to continue rejecting calls in the future.

[0117] According to one embodiment, the processor (300) may notify the call-related application that a call has been received if the number of the received call is included in the list of blocked numbers. If the number of the received call is a blocked number, the IMS may, depending on the settings, transmit relevant information to the call-related application. The relevant information may include information indicating that the number of the received call is a blocked number. Alternatively, the IMS may, depending on the settings, reject a call from an external device without notifying the call-related application.

[0118] If the call-related application is configured to forward relevant information, the IMS can wait for a response from the call-related application without performing any actions necessary to establish a call connection. If the call-related application is configured not to forward relevant information, the IMS can send a call rejection message to the external device from which the call originated based on the call rejection message received from the call-related application.

[0119] In FIG. 7b, the processor (300) may display an indicator (730) indicating that a specific number has been blocked. In FIG. 740, the processor (300) may display information indicating that a specific number has been blocked based on a user input for the indicator (730). In FIG. 750, the processor (300) may display information indicating when a call was received from a blocked number and when the number was registered as a blocked number based on a user input for FIG. 740.

[0120] According to one embodiment, the processor (300) may reject a call received from a blocked number based on user settings and may not display a notification indicating that the call has been automatically rejected. Alternatively, the processor (300) may display a call received from a blocked number based on user settings and display an indicator on the display to emphasize that the number is blocked. The processor (300) may use a different notification for a call received from a blocked number based on user settings than for a general call. The notification may, for example, include a ringtone or vibration in addition to a message.

[0121] According to one embodiment, an electronic device may include a processor and a memory storing instructions. The instructions, when executed by the processor, may cause the electronic device to store a list of blocked numbers, determine a phone number associated with a first message regarding a call reception based on receipt of a first message, determine whether the phone number associated with the first message is included in the list of blocked numbers, and transmit a second message rejecting a call reception to an external device without performing at least one of operations for connecting a call based on whether the phone number associated with the first message is included in the list of blocked numbers.

[0122] According to one embodiment, the first message includes a session initiation protocol (SIP) message, and the second message may be transmitted without a bearer being assigned.

[0123] According to one embodiment, the electronic device performs an operation to check a phone number associated with the first message at the IMS (IP multimedia subsystem) layer, and to check whether the phone number associated with the first message is included in a list of blocked numbers, and the operations for call connection may include any one of a message indicating bearer allocation, a message indicating session progress, or a message indicating that a call connection tone is ringing on the electronic device.

[0124] According to one embodiment, the electronic device may transmit a message to the external device rejecting the call based on the number of the received call being included in a list of blocked numbers, and may transmit a message indicating to an application associated with the call that the call from the external device has been rejected.

[0125] According to one embodiment, the electronic device may display a notification on the display indicating that a call was received from a blocked number based on the external device rejecting the call and that the received call was automatically rejected.

[0126] According to one embodiment, the electronic device can transmit a list of blocked numbers stored in memory to the IMS terminal, and transmit information about a received call to an application related to the call based on the IMS terminal's inability to access the list of blocked numbers stored in memory.

[0127] In the method of operation, the method may include an operation of storing a list of blocked numbers, an operation of checking a phone number associated with a first message based on receipt of a first message for receiving a call, an operation of checking whether a phone number associated with the first message is included in the list of blocked numbers, and an operation of transmitting a second message rejecting a call reception to an external device without performing at least one of the following operations: an operation of storing a list of blocked numbers; an operation of checking whether a phone number associated with the first message is included in the list of blocked numbers; and an operation of connecting a call based on the phone number associated with the first message being included in the list of blocked numbers.

[0128] The storage medium includes a processor, a memory storing a list of blocked numbers, and the memory stores instructions, which instructions, when executed by the processor, cause the electronic device to store the list of blocked numbers, determine a phone number associated with the first message based on receipt of a first message for incoming calls, determine whether the phone number associated with the first message is included in the list of blocked numbers, and transmit a second message rejecting incoming calls to an external device without performing at least one operation among operations for call connection based on the phone number associated with the first message being included in the list of blocked numbers.

Claims

1. In an electronic device (101), At least one processor (300); and Includes a memory (320) for storing instructions, The above instructions, when executed by the at least one processor, cause the electronic device to Save a list of blocked numbers, Based on the receipt of the first message regarding call reception Verify the phone number associated with the first message above, Verify that the phone number associated with the above first message is included in the list of blocked numbers, An electronic device that controls to transmit a second message to an external device for refusing to receive a call without performing at least one of the operations for connecting a call based on the telephone number associated with the first message being included in a list of numbers to be blocked from receiving.

2. In paragraph 1, The above first message includes a SIP (session initiation protocol) message, The above second message is transmitted by an electronic device in a state where no bearer is assigned.

3. In paragraph 1, The above electronic device Verify the telephone number associated with the first message at the IMS (IP multimedia subsystem) layer, Performs an action to check whether the telephone number associated with the above first message is included in the list of blocked numbers; The above actions for connecting the call are: An electronic device comprising any one of a message indicating bearer allocation, a message indicating session progress, or a message indicating that a call connection tone is ringing on said electronic device.

4. In paragraph 1, The above electronic device Transmitting a message to the external device to reject a call based on the number of the received call being included in the list of blocked numbers, An electronic device that transmits a message indicating that a call received from said external device has been rejected in a call-related application.

5. In paragraph 1, The above electronic device An electronic device that parses the header of a SIP (session initiation protocol) message to verify the number of a received call.

6. In paragraph 1, The above electronic device Based on the rejection of the call reception from the above external device, There was a call received from a blocked number, An electronic device that displays a notification on its display indicating that a received call has been automatically rejected.

7. In paragraph 1, The above electronic device Transmitting the list of blocked reception numbers stored in the above memory to the IMS terminal, An electronic device that transmits information about a call received on an application related to a call based on the inability to access a list of blocked numbers stored on the memory in the IMS terminal.

8. In paragraph 1, The above electronic device Transmit information about a received call to a call-related application based on the fact that the number of the received call is not included in the list of blocked numbers; An electronic device that requests a network to allocate a bearer for exchanging data with the above external device.

9. In terms of operation method, Action to store a list of blocked numbers; Based on the receipt of the first message regarding call reception An action to verify the telephone number associated with the first message; An action to check whether the telephone number associated with the first message is included in the list of blocked numbers; and A method comprising the action of transmitting a second message to an external device for rejecting a call reception without performing at least one of the actions for connecting a call based on the telephone number associated with the first message being included in a list of numbers to be blocked from receiving.

10. In paragraph 9, The above first message includes a SIP (session initiation protocol) message, The above second message is transmitted in a state where no bearer is assigned.

11. In paragraph 9, An operation of verifying the telephone number associated with the first message at the IMS (IP multimedia subsystem) layer; and The IMS unit further includes an operation for checking whether the telephone number associated with the first message is included in the list of blocked reception numbers. The above actions for connecting the call are: A method comprising any one of a message indicating bearer allocation, a message indicating session progress, or a message indicating that a call connection tone is ringing on an electronic device.

12. In paragraph 9, An action of transmitting a message to the external device refusing to receive a call based on the number of the received call being included in the list of blocked numbers; and A method further comprising the action of transmitting a message indicating that the call reception from said external device has been rejected in a call-related application.

13. In paragraph 9, The operation of checking the number of the received call based on receiving a message about receiving a call from the above external device A method further including an action of checking the number of a received call by parsing the header of a SIP (session initiation protocol) message.

14. In paragraph 9, Based on the rejection of the call reception from the above external device, A method further comprising the action of displaying a notification on a display indicating that a call was received from a blocked number and that the received call was automatically rejected.

15. In paragraph 9, An operation of transmitting a list of blocked reception numbers stored in memory to the IMS unit; and A method further comprising the action of transmitting information about a received call to an application related to the call based on the inability to access a list of blocked reception numbers stored in the memory in the IMS terminal.

Images