KR20240029958A - Method and apparatus for managing phone number and contacts in a wireless communication system - Google Patents

Abstract

This disclosure relates to 5G or 6G communication systems to support higher data rates. In a wireless communication system, a method performed by a first terminal includes obtaining at least one phone number from a plurality of available sources, and changing the at least one phone number into a permanent state, temporary state, or temporary state depending on the usage state. It may include classifying the status as one of a status or an invalid status, and transmitting a session initiation protocol (SIP) message including information about the classified at least one phone number to a second terminal.

Description

Method and apparatus for managing phone numbers and contacts in a wireless communication system {METHOD AND APPARATUS FOR MANAGING PHONE NUMBER AND CONTACTS IN A WIRELESS COMMUNICATION SYSTEM}

This disclosure relates generally to wireless communication systems, and more specifically to methods and devices for efficiently managing phone numbers and contact information.

Looking back at the development process of each generation of mobile communication, technologies have been developed mainly for human services, such as voice, multimedia, and data. After the commercialization of 5G (5th Generation) communication systems, it is expected that an explosive increase in connected devices will be connected to communication networks. Examples of objects connected to the network may include vehicles, robots, drones, home appliances, displays, smart sensors installed in various infrastructures, construction machinery, and factory equipment. Mobile devices are expected to evolve into various form factors such as augmented reality glasses, virtual reality headsets, and hologram devices. In the 6G (6th Generation) era, efforts are being made to develop an improved 6G communication system to provide a variety of services by connecting hundreds of billions of devices and objects. For this reason, the 6G communication system is called a Beyond 5G system.

The 6G communication system, which is expected to be realized around 2030, has a maximum transmission speed of Tera (1000 gigabytes) ps (bit per second) and a wireless delay time of 100 microseconds (μsec), which is 50 times faster than the 5G communication system and is wireless. Delay time is reduced by 1/10.

To achieve these high data rates and ultra-low latency, 6G communication systems are being considered for implementation in Terahertz bands (e.g., 95 GHz to 3 THz bands). there is. The importance of technology that can guarantee signal reach, or coverage, is expected to increase in the terahertz band due to more serious path loss and atmospheric absorption compared to the mmWave band introduced in 5G. The main technologies to ensure coverage are RF (Radio Frequency) elements, antennas, new waveforms that are better in terms of coverage than OFDM (Orthogonal Frequency Division Multiplexing), beamforming, and massive MIMO. , multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna must be developed. In addition, new technologies such as metamaterial-based lenses and antennas, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), and Reconfigurable Intelligent Surface (RIS) are being discussed to improve the coverage of terahertz band signals.

In addition, in order to improve frequency efficiency and system network, the 6G communication system uses full duplex technology in which the uplink (terminal transmission) and downlink (base station transmission) simultaneously utilize the same frequency resources at the same time. , network technology that comprehensively utilizes satellites and HAPS (High-altitude Platform Stations), network structure innovation technology that supports mobile base stations, etc. and enables network operation optimization and automation, etc., and conflict based on spectrum usage prediction. Dynamic spectrum sharing technology through avoidance, AI-based communication technology that utilizes AI from the technology design stage and internalizes end-to-end AI support functions to realize system optimization, and terminal computing capabilities. The development of next-generation distributed computing technologies that realize services of complexity beyond limits by utilizing ultra-high-performance communication and computing resources (MEC, cloud, etc.) is being developed. In addition, through the design of new protocols to be used in the 6G communication system, the implementation of a hardware-based security environment, the development of mechanisms for safe use of data, and the development of technologies for maintaining privacy, the connectivity between devices is further strengthened and the network is further improved. Attempts are continuing to optimize, promote softwareization of network entities, and increase the openness of mobile communications.

Due to the research and development of these 6G communication systems, a new level of hyper-connected experience (The Next Hyper-Connected) is created through the hyper-connectivity of the 6G communication system, which includes not only connections between objects but also connections between people and objects. Experience) is expected to become possible. Specifically, it is expected that the 6G communication system will be able to provide services such as Truly Immersive XR, High-Fidelity Mobile Hologram, and Digital Replica. In addition, services such as remote surgery, industrial automation, and emergency response by improving security and reliability are provided through the 6G communication system, enabling application in various fields such as industry, medicine, automobiles, and home appliances. It will be.

Recently, the number of terminal users using more than one phone number is increasing, and accordingly, if the recipient of the call does not save the outgoing phone number in his/her contacts, the recipient may not know who the caller is. In a wireless communication system, an operation method is required to efficiently manage phone numbers and contact information between sending and receiving terminals operating based on IMS (internet protocol) multimedia subsystem (IMS) calls.

Based on the above-described discussion, this disclosure seeks to provide an apparatus and method that can effectively provide services in a wireless communication system.

More specifically, an apparatus and method for efficiently managing phone numbers and contact information between calling and receiving terminals operating based on IMS (internet protocol) multimedia subsystem (IMS) calls are provided.

In a wireless communication system, a method performed by a first terminal includes obtaining at least one phone number from a plurality of available sources, and changing the at least one phone number into a permanent state, temporary state, or temporary state depending on the usage state. It may include classifying the status as one of a status or an invalid status, and transmitting a session initiation protocol (SIP) message including information about the classified at least one phone number to a second terminal.

In a wireless communication system, the method performed by a second terminal includes receiving a session initiation protocol (SIP) message from a first terminal, identifying that information about the unique phone number of the first terminal is not stored. It may include the step of identifying whether the SIP message includes at least one phone number different from the unique phone number of the first terminal, and displaying the at least one phone number. .

In a wireless communication system, a first terminal includes at least one transceiver and at least one processor functionally coupled to the at least one transceiver, wherein the at least one processor includes, Obtaining at least one phone number from a plurality of available sources, classifying the at least one phone number into one of a permanent state, a temporary state, or an invalid state according to a usage state, and transmitting the classified state to a second terminal. It may be configured to transmit a session initiation protocol (SIP) message including information about at least one phone number.

In a wireless communication system, a second terminal includes at least one transceiver and at least one processor functionally coupled to the at least one transceiver, wherein the at least one processor includes, Receive a session initiation protocol (SIP) message from a first terminal, identify that information about the unique phone number of the first terminal is not stored, and determine whether the SIP message is at least different from the unique phone number of the first terminal. It may be configured to identify whether it includes one phone number, and to display the at least one phone number.

The present disclosure provides an apparatus and method that can effectively provide services in a wireless communication system.

The effects that can be obtained from the present disclosure are not limited to the effects mentioned in the various embodiments, and other effects not mentioned will be clearly understood by those skilled in the art from the description below. It could be.

1 illustrates an example of a wireless communication environment, according to embodiments of the present disclosure.
FIG. 2A shows the functional configuration of a base station in a wireless communication system according to various embodiments of the present disclosure.
FIG. 2B shows the functional configuration of a terminal in a wireless communication system according to various embodiments of the present disclosure.
FIG. 3A illustrates an example of an internet protocol (IP) multimedia subsystem (IMS) communication network system according to various embodiments of the present disclosure.
FIG. 3B illustrates the functional configuration of a terminal for IMS (internet protocol (IP) multimedia subsystem) communication according to various embodiments of the present disclosure.
FIG. 4 illustrates a flow of operations for efficiently managing phone numbers and contact information between sending and receiving terminals according to various embodiments of the present disclosure.
Figure 5 illustrates an example of an operation for transferring and managing phone numbers and contact information between sending and receiving terminals according to various embodiments of the present disclosure.
Figure 6 shows a flow of operations for a calling terminal to obtain a phone number from a server according to various embodiments of the present disclosure.
FIG. 7 illustrates a flow of operations for a calling terminal to obtain a phone number from a nearby device according to various embodiments of the present disclosure.
Figure 8 illustrates the flow of an operation in which a receiving terminal updates contact information based on a received phone number according to various embodiments of the present disclosure.
Figure 9 illustrates the flow of operations for managing the phone number and contact information received by the receiving terminal when the anonymous number rejection function according to various embodiments of the present disclosure is activated.
FIG. 10 illustrates a flow of operations for managing a phone number and contact information received by a receiving terminal when an unstored number rejection function according to various embodiments of the present disclosure is activated.
FIG. 11 illustrates a flow of operations for managing phone numbers and contact information received by a receiving terminal when a black list is activated according to various embodiments of the present disclosure.
FIG. 12 illustrates a flow of operations for a receiving terminal to manage phone numbers and contact information based on valid or invalid keys according to various embodiments of the present disclosure.
FIG. 13 illustrates a flow of operations for a receiving terminal to manage a phone number and contact information based on permanent or temporary phone number information according to various embodiments of the present disclosure.

Terms used in this disclosure are merely used to describe specific embodiments and may not be intended to limit the scope of other embodiments. Singular expressions may include plural expressions, unless the context clearly indicates otherwise. Terms used, including technical or scientific terms, may have the same meaning as generally understood by a person of ordinary skill in the technical field described in this disclosure. Among the terms used in this disclosure, terms defined in general dictionaries may be interpreted to have the same or similar meaning as the meaning they have in the context of related technology, and unless clearly defined in this disclosure, have an ideal or excessively formal meaning. It is not interpreted as In some cases, even terms defined in the present disclosure cannot be interpreted to exclude embodiments of the present disclosure.

In various embodiments of the present disclosure described below, a hardware approach method is explained as an example. However, since various embodiments of the present disclosure include technology using both hardware and software, the various embodiments of the present disclosure do not exclude software-based approaches. Additionally, terms referring to network entities, terms referring to device components, etc. are exemplified for convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meaning may be used.

A term referring to variables related to the display of data used in the following description (e.g., target object, data time interval, resource level, data type level), and network entities. Terms referring to components of a device (modified appropriately according to the invention), etc. are provided as examples for convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meaning may be used.

In addition, the present disclosure describes various embodiments using terms used in some communication standards (eg, 3rd Generation Partnership Project (3GPP)), but this is only an example for explanation. Various embodiments of the present disclosure can be easily modified and applied to other communication systems.

The following technologies include code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), etc. It can be used in various wireless access systems such as: CDMA can be implemented as a radio technology such as universal terrestrial radio access (UTRA) or CDMA2000. TDMA may be implemented with wireless technologies such as global system for mobile communications (GSM), general packet radio service (GPRS), or enhanced data rates for GSM evolution (EDGE). OFDMA may be implemented with wireless technologies such as IEEE 802.11 (i.e., Wi-Fi), IEEE 802.16 (i.e., WiMAX), IEEE 802-20, Evolved UTRA (E-UTRA), etc. Hereinafter, for clear explanation, the present disclosure will be mainly described in terms of 3GPP NR, but the technical idea of the present disclosure is not limited thereto.

In addition, in the present disclosure, expressions of more or less may be used to determine whether a specific condition is satisfied or fulfilled, but this is only a description for expressing an example and excludes descriptions of more or less. It's not about doing it. Conditions written as ‘more than’ can be replaced with ‘more than’, conditions written as ‘less than’ can be replaced with ‘less than’, and conditions written as ‘more than and less than’ can be replaced with ‘greater than and less than’.

In the following description, terms referring to signals, terms referring to channels, terms referring to control information, terms referring to network entities, terms referring to device components, etc. are used for convenience of explanation. This is exemplified. Accordingly, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meaning may be used.

1 illustrates an example of a wireless communication environment 100 in accordance with various embodiments of the present disclosure. Referring to FIG. 1, a base station 110 and a terminal 120 are illustrated as some of the nodes that use a wireless channel in a wireless communication system. Terminal 120 may also be connected to multiple base stations. Although not shown in FIG. 1, base stations may be connected to the terminal 120 through multiple connectivity (eg, dual connectivity (DC)). According to one embodiment, the terminal 120 may perform wireless communication with another terminal through connection to the base station 110. According to various embodiments of the present disclosure, wireless communication performed by a sending terminal and a receiving terminal is not only wireless communication through a base station, but also a plurality of terminals that are equivalent or substantially similar to this, such as device-to-device (DTD) communication. Of course, it may include wireless communication between livers.

The base station 110 is a network infrastructure that provides wireless access to the terminal 120. Base station 110 has coverage defined as a certain geographic area based on the distance over which signals can be transmitted. Hereinafter, the term 'coverage' used may refer to a service coverage area in the base station 110. The base station 110 may cover one cell or multiple cells. Here, the plurality of cells can be divided by the frequency they support and the area of the sector they cover.

In addition to the base station, the base station 110 includes 'access point (AP)', 'eNodeB (eNB)', '5G node (5th generation node)', and '5G NodeB (5G NodeB). NB)', 'gNB (next generation node B)', 'wireless point', 'transmission/reception point (TRP)', 'distributed unit (DU)', 'wireless unit (radio unit, RU), remote radio head (RRH), or other terms with equivalent technical meaning. According to various embodiments, the base station 110 may be connected to one or more 'transmission/reception points (TRP)'. The base station 110 may transmit a downlink signal or receive an uplink signal to the terminal 120 through one or more TRPs.

The terminal 120 is a device used by a user and communicates with the base station 110 through a wireless channel. In some cases, the terminal 120 may be operated without user involvement. That is, at least one of the terminals 120 is a device that performs machine type communication (MTC) and may not be carried by the user. The terminal 120 is a terminal, as well as 'user equipment (UE)', 'mobile station', 'subscriber station', and 'customer premises equipment (CPE)'. , ‘remote terminal’, ‘wireless terminal’, ‘electronic device’, or ‘vehicle terminal’, ‘user device’ or technical equivalent. It may be referred to by other terms with different meanings. In addition, according to various embodiments of the present disclosure, a terminal making an outgoing call may be referred to as an originating terminal, a mobile original (MO), a first terminal, or equivalent or similar terms, and may receive a call ( A terminal making an incoming call may be referred to as a called terminal, a receiving terminal, a mobile terminated (MT), a second terminal, or terms equivalent or similar thereto. Here, MO may refer to a mobile device (or device) that sends a call to the MT, and MT may refer to a mobile device (or device) that receives a call from the MO. Hereinafter, in the present disclosure, various terms referring to the above-described terminal 120 may be used interchangeably and described.

FIG. 2A shows the functional configuration of a base station in a wireless communication system according to various embodiments of the present disclosure. Terms such as '... unit' and '... unit' used hereinafter refer to a unit that processes at least one function or operation, which can be implemented through hardware, software, or a combination of hardware and software. there is.

Referring to FIG. 2A, the base station 110 includes a communication unit 210, a backhaul communication unit 220, a storage unit 230, and a control unit 240.

The communication unit 210 performs functions for transmitting and receiving signals through a wireless channel. For example, the communication unit 210 performs a conversion function between a baseband signal and a bit string according to the physical layer standard of the system. For example, when transmitting data, the communication unit 210 generates complex symbols by encoding and modulating the transmission bit string. Additionally, when receiving data, the communication unit 210 restores the received bit stream by demodulating and decoding the baseband signal. The communication unit 210 may be configured to perform at least one of the operations of the transmitting end or the operations of the receiving end described through FIGS. 1 to 10. According to one embodiment, the communication unit 210 may be configured to transmit a downlink signal to the terminal 120 or to receive an uplink signal from the terminal 120.

The communication unit 210 upconverts the baseband signal into a radio frequency (RF) band signal and transmits it through an antenna, and downconverts the RF band signal received through the antenna into a baseband signal. To this end, the communication unit 210 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), an analog to digital convertor (ADC), etc. Additionally, the communication unit 210 may include a plurality of transmission and reception paths. Furthermore, the communication unit 210 may include at least one antenna array composed of a plurality of antenna elements. In terms of hardware, the communication unit 210 may be composed of a digital unit and an analog unit, and the analog unit is divided into a plurality of sub-units according to operating power, operating frequency, etc. It can be configured. According to one embodiment, the communication unit 210 may include a unit that forms a beam, that is, a beamforming unit. For example, the communication unit 210 may include a massive MIMO unit (MMU) for beamforming.

The communication unit 210 can transmit and receive signals. For this purpose, the communication unit 210 may include at least one transceiver. For example, the communication unit 210 may transmit a synchronization signal, reference signal, system information, message, control information, or data. Additionally, the communication unit 210 may perform beamforming. The communication unit 210 may apply a beamforming weight to the signal to be transmitted and received in order to give directionality according to the settings of the control unit 240. According to one embodiment, the communication unit 210 may generate a baseband signal according to the scheduling result and the transmission power calculation result. Additionally, the RF unit within the communication unit 210 may transmit the generated signal through an antenna.

The communication unit 210 transmits and receives signals as described above. Accordingly, all or part of the communication unit 210 may be referred to as a ‘transmitting unit’, a ‘receiving unit’, or a ‘transmitting/receiving unit’. Additionally, in the following description, transmission and reception performed through a wireless channel are used to mean that processing as described above is performed by the communication unit 210.

The backhaul communication unit 220 provides an interface for communicating with other nodes in the network. That is, the backhaul communication unit 220 converts a bit string transmitted from the base station 110 to another node, for example, another access node, another base station 110, a higher node, a core network, etc., into a physical signal, and The physical signal received from is converted into a bit string.

The storage unit 230 stores data such as basic programs, application programs, and setting information for operation of the base station 110. The storage unit 230 may include memory. The storage unit 230 may be comprised of volatile memory, non-volatile memory, or a combination of volatile memory and non-volatile memory. And, the storage unit 230 provides stored data according to the request of the control unit 240.

The control unit 240 controls the overall operations of the base station 110. For example, the control unit 240 transmits and receives signals through the communication unit 210 or the backhaul communication unit 220. Additionally, the control unit 240 records and reads data from the storage unit 230. Additionally, the control unit 240 can perform protocol stack functions required by communication standards. For this purpose, the control unit 240 may include at least one processor. According to various embodiments, the control unit 240 may control the base station 110 to perform operations according to various embodiments described below. According to one embodiment, the control unit 240 may estimate an uplink channel.

The configuration of the base station 110 shown in FIG. 2A is only an example of a base station, and examples of base stations that perform various embodiments of the present disclosure are not limited to the configuration shown in FIG. 2A. That is, some configurations may be added, deleted, or changed according to various embodiments.

In FIG. 2A, the base station is depicted as one entity, but as described above, the present disclosure is not limited thereto. The base station 110 according to various embodiments of the present disclosure may be implemented to form an access network having not only an integrated deployment (e.g., eNB of LTE) but also a distributed deployment. As illustrated to explain the embodiments of FIGS. 1 to 13, the base station is divided into a central unit (CU) and a digital unit (DU), and the CU performs upper layer functions (e.g., packet data (PDCP) convergence protocol (RRC)) DU may be implemented to perform lower layer functions (e.g., medium access control (MAC), physical (PHY)).

As such, a base station with a separate deployment may further include a configuration for fronthaul interface communication. According to one embodiment, a base station, as a DU, may perform functions for transmitting and receiving signals in a wired communication environment. The DU may include a wired interface to control direct connection between devices through a transmission medium (e.g., copper wire, optical fiber). For example, DU can transmit electrical signals to other devices through copper wires or perform conversion between electrical signals and optical signals. DUs can be connected to CUs in a distributed deployment. However, this description is not to be interpreted as excluding the scenario in which the DU is connected to the CU through a wireless network. Additionally, the DU may be additionally connected to a radio unit (RU). However, this description is not to be interpreted as excluding a wireless environment consisting of only CU and DU.

FIG. 2B shows the functional configuration of a terminal in a wireless communication system according to various embodiments of the present disclosure. Terms such as '... unit' and '... unit' used hereinafter refer to a unit that processes at least one function or operation, which can be implemented through hardware, software, or a combination of hardware and software. there is.

Referring to FIG. 2B, the terminal 120 includes a communication unit 205, a storage unit 215, and a control unit 225.

The communication unit 205 performs functions for transmitting and receiving signals through a wireless channel. For example, the communication unit 205 performs a conversion function between baseband signals and bit strings according to the physical layer specifications of the system. For example, when transmitting data, the communication unit 205 generates complex symbols by encoding and modulating the transmission bit string. Additionally, when receiving data, the communication unit 205 restores the received bit stream by demodulating and decoding the baseband signal. The communication unit 205 upconverts the baseband signal into an RF band signal and transmits it through an antenna, and downconverts the RF band signal received through the antenna into a baseband signal. For example, the communication unit 205 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc.

Additionally, the communication unit 205 may include a plurality of transmission and reception paths. Furthermore, the communication unit 205 may include an antenna unit. The communication unit 205 may include at least one antenna array composed of a plurality of antenna elements. In terms of hardware, the communication unit 205 may be composed of digital circuits and analog circuits (eg, radio frequency integrated circuit (RFIC)). Here, the digital circuit and analog circuit can be implemented in one package. Additionally, the communication unit 205 may include a plurality of RF chains. The communication unit 205 may perform beamforming. The communication unit 205 may apply a beamforming weight to the signal to be transmitted and received in order to give directionality according to the settings of the control unit 225.

Additionally, the communication unit 205 can transmit and receive signals. For this purpose, the communication unit 205 may include at least one transceiver. The communication unit 205 can receive a downlink signal. Downlink signals include synchronization signal (SS), reference signal (RS) (e.g., cell-specific reference signal (CRS), demodulation (DM)-RS), system information (e.g., MIB, SIB, It may include remaining system information (RMSI), other system information (OSI), configuration message, control information, or downlink data. Additionally, the communication unit 205 can transmit an uplink signal. Uplink signals include uplink control information (UCI), random access-related signals (e.g., random access preamble (RAP) (or Msg1 (message 1), Msg3 (message 3)), and standards. It may include a signal (e.g., sounding reference signal (SRS), DM-RS), or buffer status report (BSR). For example, the uplink control information may include at least one of a scheduling request (SR), ACK/NACK information of a hybrid acknowledge (HARQ) procedure, or channel state information (CSI). According to one embodiment, the communication unit 205 may receive uplink DMRS allocation information. Additionally, according to one embodiment, the communication unit 205 may transmit an uplink DMRS symbol.

Specifically, the communication unit 205 may include an RF processing unit and a baseband processing unit. The RF processing unit performs functions to transmit and receive signals through a wireless channel, such as converting the signal band and amplifying it. The RF processing unit upconverts the baseband signal provided from the baseband processing unit into an RF band signal and transmits it through an antenna, and downconverts the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), an analog to digital convertor (ADC), etc. Terminal 120 may include one or more antennas. The RF processing unit may include multiple RF chains. Furthermore, the RF processing unit can perform beamforming. For the beamforming, the RF processing unit can adjust the phase and size of each signal transmitted and received through a plurality of antennas or antenna elements.

The baseband processing unit performs a conversion function between baseband signals and bit strings according to the system's physical layer specifications. For example, when transmitting data, the baseband processor generates complex symbols by encoding and modulating the transmission bit stream. Additionally, when receiving data, the baseband processing unit restores the received bit stream by demodulating and decoding the baseband signal provided from the RF processing unit. For example, when following the OFDM (orthogonal frequency division multiplexing) method, when transmitting data, the baseband processor generates complex symbols by encoding and modulating the transmission bit string, maps the complex symbols to subcarriers, and performs IFFT. OFDM symbols are constructed through (inverse fast Fourier transform) operation and CP (cyclic prefix) insertion. In addition, when receiving data, the baseband processing unit divides the baseband signal provided from the RF processing unit into OFDM symbols, restores the signals mapped to subcarriers through FFT (fast Fourier transform) operation, and then performs demodulation and decoding. Restore the received bit string through

The communication unit 205 transmits and receives signals as described above. Accordingly, all or part of the communication unit 205 may be referred to as a transmitting unit, a receiving unit, or a transmitting and receiving unit. Furthermore, the communication unit 205 may include a plurality of communication modules to support a plurality of different wireless access technologies. Additionally, the communication unit 205 may include different communication modules to process signals in different frequency bands. For example, the different wireless access technologies may include wireless LAN (eg, IEEE 802.1x), cellular network (eg, LTE, NR), etc. Additionally, the different frequency bands may include a super high frequency (SHF) (e.g., 2.5GHz, 5Ghz) band and a millimeter wave (e.g., 60GHz) band. In addition, the communication unit 205 performs the same type of wireless communication on different frequency bands (e.g., licensed assisted access (LAA) or unlicensed (NR-U) band, citizens broadband radio service (CBRS) (e.g., 3.5 GHz)). Access technology can also be used.

The storage unit 215 stores data such as basic programs, application programs, and setting information for the operation of the terminal 120. The storage unit 215 may be comprised of volatile memory, non-volatile memory, or a combination of volatile memory and non-volatile memory. The storage unit 215 stores data such as basic programs, application programs, and setting information for operation of the terminal 120.

The control unit 225 controls the overall operations of the terminal 120. For example, the control unit 225 transmits and receives signals through the communication unit 205. Additionally, the control unit 225 writes and reads data into the storage unit 215. Additionally, the control unit 225 can perform protocol stack functions required by communication standards. For this purpose, the control unit 225 may include at least one processor. The control unit 225 may include at least one processor or microprocessor, or may be part of a processor. Additionally, part of the communication unit 205 and the control unit 225 may be referred to as CP. The control unit 225 may include various modules for performing communication. According to various embodiments, the control unit 225 may control the terminal to perform operations according to various embodiments described later.

The control unit 225 controls overall operations of the terminal 120. For example, the control unit 225 transmits and receives signals through the communication unit 205. Additionally, the control unit 225 records and reads data into the storage unit 215. For this purpose, the control unit 225 may include at least one processor. For example, the control unit 225 may include a CP (communication processor) that performs control for communication and an AP (application processor) that controls upper layers such as application programs. According to various embodiments of the present disclosure, the control unit 225 may be configured to perform the function of dynamic spectrum sharing. According to one embodiment, the control unit 225 may be configured to allow the terminal 120 to dynamically use LTE cells and NR cells in an EN-DC environment. Additionally, according to one embodiment, the control unit 225 may be configured to allow the terminal 120 to dynamically use cells by two nodes in an MR-DC environment as well as an EN-DC environment. In addition, the control unit 225 may control the terminal 120 to perform operations according to various embodiments described below.

FIG. 3A illustrates an example of an internet protocol (IP) multimedia subsystem (IMS) communication network system according to various embodiments of the present disclosure. IMS (IP Multimedia Subsystem) may be a framework for providing multimedia services on an IP network.

Referring to FIG. 3A, the IMS service network includes a telephony application server (TAS) (330-1, 330-2) that provides additional services such as caller ID service, call blocking, and call forwarding, as shown in FIG. 3A. It may further include multimedia resource functions (MRFs) (320-1, 320-2), conversion servers (310-1, 310-2), etc. related to multimedia streams and resources.

Referring to FIG. 3A, the first terminal 120-1 transmits and receives signals with the first IMS core network system 300-1 and the second terminal 120-2. Signals can be transmitted and received with the second terminal 120-2 via the second IMS core network system 300-2, which transmits and receives signals. More specifically, each terminal can transmit and receive signals with any one IMS core network system 300 among the plurality of IMS core network systems 300, and the first terminal 120-1 and the second terminal 120 -2) A call session can be connected through the IMS core network system 300, which can transmit and receive signals with each terminal. At this time, signal transmission and reception between the IMS core network system 300 may be performed through call session control function (CSCF) 340-1 and 340-2 within the IMS core network system 300. Hereinafter, the configuration of a terminal for establishing a call session in the IMS system is described in more detail.

FIG. 3B illustrates the functional configuration of a terminal for IMS (internet protocol (IP) multimedia subsystem) communication according to various embodiments of the present disclosure. Referring to FIG. 3b, the biggest feature of the ALL IP network, which replaces all infrastructure of wireless communication networks with IP, may be that it is the first 3GPP network to support IP multimedia services.

Specifically, referring to Figure 3b, the features of the ALL IP network can be implemented by newly added nodes to support IP multimedia services, and the new nodes are collectively referred to as the Internet Protocol Multimedia Subsystem (IMS) 300. can be referred to.

IMS is a set of newly introduced nodes to provide IP multimedia services, and the IMS service network includes call (or call) session control servers (CSCF) (340-1, 340-2) and home subscriber servers. It may include a home subscriber server (HSS) 350 and an application server (AS) 330. In addition, as shown in FIG. 3A, the IMS service network includes a telephony application server (TAS) (330-1, 330) that provides additional services such as caller ID service, call blocking, and call forwarding, as shown in FIG. 3A. -2), MRF (multimedia resource function) (320-1, 320-2), conversion server (310-1, 310-2), etc. related to multi-media streams and resources may be further included. The call session control server (CSCF) and home subscriber server (HSS) may form the IMS core network, and the application server (AS) may form the IMS service network.

A call session control server (CSCF) can perform multimedia call control based on session initiation protocol (SIP). The call session control servers (CSCF) (340-1, 340-2) include proxy-call session control function (P-CSCF) (not shown), interrogating-call session control function (I-CSCF) (not shown), and S -May include serving-call session control function (CSCF) 340.

The home subscriber server (HSS) 350 can store all data about the user equipment (UE) 120 or user data, and manages information for management of user profiles and mobility of the user equipment (UE). and authorization. The home subscriber server (HSS) 350 can largely provide HLR/AUC (home location register/authentication) functions and IP multimedia functions for IP multimedia services.

The application server (AS) 330 supports IM (instant messaging), presence, VCC (voice call continuity), PTT (push-to-talk), VoIP (voice over internet protocol), and GLMS (group It may be a network object that delivers IP multimedia services, including list management server (IMS), ICS (IMS centralized services), etc., to subscribers. In particular, the application server 330 may include a TAS (330-1, 330-2) that provides additional services such as caller ID service, call/call blocking, and call forwarding.

When the terminal 120 transmits a service request message (SIP message) to the P-CSCF for an IP multimedia service, the P-CSCF can transmit this service request message back to the I-CSCF. The I-CSCF that has received the service request message may select the S-CSCF 340 based on the service request message. S-CSCF can provide information-related services to the application server (AS) 330, which is an endpoint. That is, when providing a specific service in the IMS network, the S-CSCF can deliver a SIP message generated from the user terminal (UE) to the specific application server (AS) 330. According to various embodiments of the present disclosure, the SIP message may include a SIP INVITE (or INVITE SIP) message used when initiating a session.

Specifically, referring to FIG. 3B, the home subscriber server (HSS) 350 is a master database about subscribers and may include basic data about subscribers. Basic information about subscribers includes subscriber identifier (e.g., number and address information), subscriber security information (e.g., network access control information for authentication and authority verification), and subscriber location information (e.g., registration and inter-system level movement information) and the subscriber's service profile information, etc. In addition, the home subscriber server 350 can operate as a master database for not only the IMS network but also various networks, and provides access information not only to the IMS network of the subscriber terminal 120 but also to various communication networks (e.g., 3G, LTE, 5G, etc.). It can be included.

The HSS 350 can control the delivery of initial filter criteria (IFC) to the S-CSCF 340 based on various states of the subscriber terminal 120 as well as information on the IMS network itself.

CSCF can perform call control, serving profile management, and address processing functions. Specifically, CSCF may include P-CSCF, I-CSCF, or S-CSCF 340. The IMS network 300 may use Session Initiation Protocol (SIP) as a signaling protocol. Signaling between the subscriber terminal 120 and the CSCF, PCSCF, I-CSCF, and S-CSCF may be performed based on the Session Initiation Protocol (SIP).

Additionally, the S-CSCF 340 can receive IFC from the HSS 350 along with the subscriber profile when the subscriber terminal 120 registers with the IMS network 300. The S-CSCF 340 can deliver a SIP message generated from the subscriber terminal 120 to the AS 330 only when a specific condition is satisfied. IFC can contain profiles with specific conditions.

AS (330)) provides instant messaging (IM), presence, voice call continuity (VCC), push to-talk (PTT), voice over internet protocol (VoIP), group list management server (GLMS), and ICS. It may be a network element that delivers IP multimedia services, including (IMS centralized services), to the subscriber terminal 120. For example, when the AS 330 receives a SIP message generated from the subscriber terminal 120 from the S-CSCF 340, the AS 330 may provide a service corresponding to the SIP message to the subscriber terminal 120.

According to various embodiments of the present disclosure, signaling for IMS-based call processing performed by a terminal or various IMS objects is described through FIGS. 3A and 3B. However, the present disclosure is not limited thereto and can be equally applied to various terminal-to-terminal call processing signaling as well as IMS.

As technology has recently advanced, the number of users of wireless communication using more than one phone number has increased. When the sender of a call attempts to call the recipient of the call using a specific phone number, if the recipient has not previously saved the caller's specific phone number in his/her contacts, the recipient may not know who the call is coming from. In another case, if the recipient activates the 'Automatically block calls from anonymous numbers' or 'Automatically block calls from numbers not saved in contacts' feature, the recipient's terminal will not be saved. There may be cases where calls are automatically blocked for certain numbers that are not in use. In another case, if the recipient has activated the feature that automatically blocks calls from a specific caller's number, and a random caller borrows the phone of a specific caller that has been blocked and tries to make a call, the recipient will be able to call the random caller. There may be cases where you miss a call from .

In order to solve the above-described problem, various embodiments of the present disclosure allow a caller or a calling terminal to obtain a phone number other than the specific phone number of the calling terminal and transmit two or more phone numbers to the receiving terminal in a single call attempt. Discloses a method and device for doing so. Additionally, a method and device for receiving a call from a caller are disclosed even when the recipient or receiving terminal does not store the phone number of the calling terminal or a function to block the phone number is activated.

FIG. 4 illustrates a flow of operations for efficiently managing phone numbers and contact information between sending and receiving terminals according to various embodiments of the present disclosure. Specifically, FIG. 4A discloses a flow of operations for an originating terminal (MO) or a receiving terminal (MT) to efficiently manage phone numbers and contact information, according to various embodiments of the present disclosure.

Additionally, various embodiments of the present disclosure may include all, part, or a combination of each step performed by the sending terminal or the receiving terminal. For example, according to one embodiment, it may include performing all, part, or only a combination of some of the operations of the sending terminal, regardless of the operations of the receiving terminal, or may also include the opposite case. Additionally, according to various embodiments of the present disclosure, the INVITE SIP message transmitted from the calling terminal to the receiving terminal in FIGS. 4 to 13 may include a message for the calling terminal, a SIP message, etc.

Referring to Figure 4, in step 405, the calling terminal may collect a phone number list. Specifically, the calling terminal can obtain one or more phone numbers based on several available sources. According to one embodiment, the calling terminal may obtain one or more phone numbers from at least one of a subscriber identity module (SIM) inserted in the calling terminal, a cloud server, or a peripheral device. According to one embodiment, one or more phone numbers acquired by the calling terminal may include lists of phone numbers. According to one embodiment, the calling terminal may obtain one or more phone numbers not only from the inserted SIM, but also from a terminal identification object newly inserted or installed from the outside. According to one embodiment, when the calling terminal attempts to make a call to the called terminal, the phone number of the calling terminal displayed to the called terminal may be a phone number obtained based on the SIM inserted into the calling terminal. In addition, hereinafter, according to various embodiments of the present disclosure, when the calling terminal attempts to make a call to the called terminal, the phone number of the calling terminal displayed to the called terminal is the unique phone number (or a specific phone number, identification number) of the calling terminal. may be referred to as a phone number).

In step 415, the calling terminal may classify (or categorize) the list of phone numbers based on one or more phone numbers obtained. According to one embodiment, the calling terminal may classify the list of phone numbers according to usage status. The usage status, which is one of the criteria by which the calling terminal classifies the list of phone numbers, may include a permanent status, a temporary status, or an invalid status. For example, the calling terminal can identify whether one or more acquired phone numbers are in a permanent state that can be used permanently, a temporary state that can be used one-time, or an invalid state that the receiving terminal cannot receive normally, Depending on the identified status, the phone number list can be classified (or categorized).

In step 425, the calling terminal may attempt to make a call to the receiving terminal and transmit an INVITE SIP message. Specifically, when sending a call to a receiving terminal, the calling terminal may transmit an INVITE SIP message to the receiving terminal based on the IMS network. According to one embodiment, the INVITE SIP message transmitted by the calling terminal includes at least one of information about one or more phone numbers acquired by the calling terminal, information about a list of phone numbers, or information about a list of classified (or categorized) phone numbers. It can contain one. According to one embodiment, the information about one or more phone numbers transmitted by the calling terminal may include information about one or more phone numbers acquired by the calling terminal from a plurality of sources in addition to the unique phone number of the calling terminal. According to one embodiment, information about the classified phone number list transmitted by the calling terminal may include information about the classified phone number list according to usage status.

In step 410, the receiving terminal may receive a call and an INVITE SIP message from the calling terminal. According to one embodiment, when the receiving terminal receives a call from the calling terminal, the receiving terminal only receives the call based on the unique phone number of the calling terminal or sends an INVITE SIP message based on the IMS network along with the call from the calling terminal. You can receive it. According to one embodiment, the INVITE SIP message may include at least one of information about one or more phone numbers, information about a list of phone numbers, or information about a classified (or categorized) list of phone numbers. According to one embodiment, the information about one or more phone numbers may include information about one or more phone numbers acquired by the calling terminal from a plurality of sources in addition to the unique phone number of the calling terminal. According to one embodiment, information about the classified phone number list transmitted by the calling terminal may include information about the classified phone number list according to usage status.

In step 420, the receiving terminal may identify that one or more numbers received from the calling terminal are not stored. According to one embodiment, the receiving terminal receives a call from the calling terminal and identifies whether the unique phone number of the calling terminal is a phone number (or an anonymous phone number) not stored in the receiving terminal (or the receiving terminal's contact information). can do. The receiving terminal or the contact information of the receiving terminal may include contacts that can be obtained from the receiving terminal device, software within the device, or an external server to which the receiving terminal can be connected. According to one embodiment, before receiving a call from the sending terminal, the receiving terminal has 'a function to automatically block calls from anonymous numbers' or 'a function to automatically block calls from numbers not stored in the contacts'. may be activated. According to one embodiment, when the above-described blocking functions are activated, the receiving terminal blocks a call from the calling terminal when it detects that the unique phone number of the calling terminal is an anonymous phone number or an unstored phone number. You can. According to one embodiment, the action of blocking a call may include not performing any action or display related to the calling terminal's call on the receiving terminal's display or application.

In step 430, the receiving terminal can identify whether information about the phone number list has been received from the calling terminal. According to one embodiment, when the receiving terminal receives a call from the calling terminal, it can identify whether it has received information including the INVITE SIP message along with the unique phone number of the calling terminal. According to one embodiment, if the receiving terminal does not receive the INVITE SIP message, the call from the calling terminal may be blocked and the procedure may be terminated. According to one embodiment, when the receiving terminal receives a call from the calling terminal and also receives the INVITE SIP message, it may proceed to step 440.

In step 440, the receiving terminal may disable the incoming call blocking function. According to one embodiment, when the receiving terminal receives an INVITE SIP message from the sending terminal, the receiving terminal has 'a function to automatically block calls from anonymous numbers' or 'Automatically blocks calls from numbers not stored in the contacts.' You can disable the 'function'. For example, when the receiving terminal receives an INVITE SIP message containing information about a phone number other than the unique phone number of the calling terminal from the calling terminal, it can ignore the activated blocking functions and perform the following steps. According to one embodiment, if the 'function to automatically block calls from anonymous numbers' or 'the function to automatically block calls from numbers not stored in contacts' is not activated, the receiving terminal performs step ( 440) may not be performed.

In step 450, the receiving terminal displays contact information corresponding to one or more phone numbers included in messages received from the sending terminal (e.g., INVITE SIP message, message containing the unique phone number of the sending terminal). can do. According to one embodiment, when one or more contacts corresponding to one or more received phone numbers are stored, the receiving terminal may display or provide a phone number without a corresponding contact along with the stored contacts. According to one embodiment, the receiving terminal may display or provide all of the one or more received phone numbers when the contact information corresponding to the one or more received phone numbers is not stored.

In step 460, the receiving terminal can identify that the call with the calling terminal has ended. According to one embodiment, step 460 of identifying call termination may not be performed, and subsequent steps may proceed even when a call is in progress.

In step 470, the receiving terminal may identify whether one or more numbers received from the calling terminal are in a permanent state. According to one embodiment, the receiving terminal may identify the usage status of one or more numbers based on a classified phone number list included in the INVITE SIP message received from the sending terminal. According to one embodiment, if one or more phone numbers received by the receiving terminal are classified as permanent, step 480 may be performed. According to one embodiment, if one or more phone numbers received by the receiving terminal are classified as non-permanent, the procedure may be terminated. However, according to various embodiments of the present disclosure, in step 470, the receiving terminal is shown to perform the operation based on whether the one or more phone numbers received are in a permanent state, but is not limited thereto and is not limited to this. The criteria may include at least one of a permanent state, a temporary state, or an invalid state.

In step 480, the receiving terminal may update the contact information included in the receiving terminal. The receiving terminal or the contact information of the receiving terminal may include contacts that can be obtained from the receiving terminal device, software within the device, or an external server to which the receiving terminal can be connected. According to one embodiment, the receiving terminal may determine whether to update the contact number or contact list based on the usage status of one or more phone numbers. According to one embodiment, the receiving terminal may store one or more phone numbers received from the sending terminal in the contact information of the receiving terminal. According to one embodiment, the operation of updating the contact information of the receiving terminal may include storing one or more phone numbers that are not stored in the contact information of the receiving terminal. According to one embodiment, the operation of the receiving terminal updating the contact information is performed when one or more phone numbers received by the receiving terminal are not stored in the first contact information, but are stored in the second contact information, and the second contact number is stored in the first contact information. May include a merge operation.

FIG. 5 illustrates an example of an operation for transferring and managing phone numbers and contact information between sending and receiving terminals according to various embodiments of the present disclosure. Specifically, Figure 5 visually illustrates some of the various operations or steps according to various embodiments of the present disclosure.

The calling terminal (or caller) 510 may have one or more phone numbers 511, 513, and 515, including the unique phone number 511 of the calling terminal. According to one embodiment, the calling terminal may obtain one or more numbers 511, 513, and 515 from various sources, including the SIM inserted in the calling terminal.

The calling terminal may attempt to call the receiving terminal (or recipient) 520 based on one or more phone numbers. According to one embodiment, when a call is attempted by the calling terminal, the receiving terminal may display or provide the unique number 511 of the calling terminal to the receiving terminal. According to one embodiment, the receiving terminal 520 may receive an INVITE SIP message including information about one or more phone numbers 511, 513, and 515 from the sending terminal 510.

The receiving terminal 520 may include a contact number 521 in which arbitrary phone numbers are stored. According to one embodiment, one number 513 among one or more phone numbers received from the calling terminal 510 may be stored in the contact information 521 of the receiving terminal 520.

The receiving terminal 520 may display (523) a portion 511 of one or more phone numbers received from the sending terminal 510 along with the stored phone number 513 of the sending terminal 510.

The receiving terminal 520 may display or provide (525) to the user whether to store a part (511) of one or more phone numbers received from the sending terminal (510) that was not stored in the contact list.

Whether or not the receiving terminal 520 will merge the contacts storing part of one or more phone numbers 511 received from the sending terminal 510 with the previously stored contacts storing the phone number of the sending terminal 510. can be displayed or provided to the user (527).

Hereinafter, according to various embodiments of the present disclosure, each individual step performed by the sending terminal or the receiving terminal is described in detail.

Figure 6 shows a flow of operations for a calling terminal to obtain a phone number from a server according to various embodiments of the present disclosure. Specifically, one or more phone numbers including the unique phone number of the calling terminal may be assigned to the caller or calling terminal. At this time, the calling terminal can upload or download one or more phone numbers based on the server account. According to various embodiments of the present disclosure, a series of steps or each step shown in FIG. 6 may be performed corresponding to or combined with steps 405 to 425 of FIG. 4.

In step 610, the calling terminal may add the authenticated phone number to the server account. According to one embodiment, the server account to which the calling terminal is connected may include wireless storage objects including a cloud server, a server dedicated to a specific terminal, etc. According to one embodiment, the calling terminal may add (or upload) one or more phone numbers assigned to the calling terminal to the server account. According to one embodiment, one or more phone numbers that the calling terminal adds to the server account may include an authenticated phone number (e.g., including a phone number that has been authenticated as valid from the server account) or an inserted It may include one or more phone numbers obtained from a SIM or a terminal identification object that is newly inserted or installed from the outside.

According to one embodiment, the inserted SIM and the server account may be included in the same device. For example, the calling terminal can obtain the phone number (or one or more phone numbers) of the inserted SIM and add it to a server account included in the same device.

According to one embodiment, the inserted SIM and server account may be contained in different devices. For example, the user of the calling terminal may attempt to add the phone number (or one or more phone numbers) of the manually inserted SIM to the server account. In this case, the server account can request authentication by sending an OTP (one-time password) to the sending terminal into which the SIM is inserted. When the caller or calling terminal performs authentication based on OTP, the phone number (or one or more phone numbers) of the inserted SIM may be added to the server account.

Although not shown in FIG. 6, when the calling terminal adds one or more phone numbers to the server account, the server account can check or authenticate whether the added phone number is valid. According to one embodiment, when a certain period (e.g., one day) has passed since one or more phone numbers were added to the server account, the server account may check or authenticate whether the phone number is valid. For example, the server may obtain a list of phone numbers from all devices (eg, terminals) logged in or connected to the server account at regular intervals. According to one embodiment, a server account identifies one or more phone numbers as valid if one or more phone numbers included in the list of phone numbers acquired by the server account are identified as available on all devices logged in or connected to the server account. can do. According to one embodiment, a server account may identify its validity by sending an OTP for an unidentified phone number that is available on all devices logged in or connected to the server account. At this time, the server account can identify the phone number that can receive the OTP as valid, and identify the phone number that cannot receive the OTP as an invalid phone number (or a phone number in an invalid state).

In step 620, the calling terminal may obtain a phone number from the server account. According to one embodiment, the phone number that the calling terminal obtains from the server account may include one or more phone numbers added in step 610. According to one embodiment, one or more phone numbers acquired by the calling terminal may include lists of phone numbers. According to one embodiment, the calling terminal may store one or more phone numbers obtained by logging into a server account on the device of the calling terminal.

In step 630, the calling terminal may identify one or more phone numbers or a list of phone numbers to be transmitted to the receiving terminal based on the phone number obtained from the server account. According to one embodiment, one or more phone numbers or a list of phone numbers to be transmitted to the receiving terminal may include the unique phone number of the calling terminal.

In step 640, the calling terminal may attempt to make a call to the receiving terminal and transmit an INVITE SIP message. According to one embodiment, the INVITE SIP message transmitted from the calling terminal to the receiving terminal may include information about one or more phone numbers acquired by the calling terminal from a server account along with the unique phone number of the calling terminal. According to one embodiment, when the calling terminal attempts to make a call to the called terminal, the phone number of the calling terminal displayed to the called terminal may be a phone number obtained based on the SIM inserted into the calling terminal. In addition, hereinafter, according to various embodiments of the present disclosure, when the calling terminal attempts to make a call to the called terminal, the phone number of the calling terminal displayed to the called terminal is the unique phone number (or a specific phone number, identification number) of the calling terminal. may be referred to as a phone number).

FIG. 7 illustrates a flow of operations for a calling terminal to obtain a phone number from a nearby device according to various embodiments of the present disclosure. Specifically, one or more phone numbers including the unique phone number of the calling terminal may be assigned to the caller or calling terminal. At this time, the calling terminal can transmit one or more phone numbers to other calling terminal devices located nearby. According to various embodiments of the present disclosure, a series of steps or each step shown in FIG. 7 may be performed corresponding to or combined with steps 405 to 425 of FIG. 4 . Hereinafter, with reference to FIG. 7, a terminal attempting to make a call to a receiving terminal may be referred to as a calling terminal, and a terminal located within a certain distance from the calling terminal and delivering one or more phone numbers to the calling terminal may be referred to as another terminal. It can be.

In step 710, when the calling terminal attempts to call the called terminal, it can identify whether another phone number is included in addition to the unique phone number of the calling terminal. For example, the calling terminal or the user of the calling terminal can identify whether one or more phone numbers that are different from the phone number stored in the calling terminal or a server associated with the calling terminal should be transmitted to the called terminal.

In step 720, the calling terminal may receive one or more phone numbers from another terminal. According to one embodiment, another terminal may transmit one or more phone numbers assigned to another terminal to the calling terminal. According to one embodiment, one or more phone numbers that another terminal transmits to the calling terminal may include or insert an authenticated phone number (e.g., including a phone number that has been authenticated as valid from a server account). It may include one or more phone numbers obtained from a new SIM or a terminal identification object that is newly inserted or installed from the outside.

According to one embodiment, if the calling terminal allows, another terminal may transmit one or more phone numbers to the calling terminal through short-range wireless communication technology (eg, Bluetooth or near field communication (NFC)). For example, a sending terminal may be connected to another terminal located nearby through short-range wireless communication technology. According to one embodiment, another terminal may transmit information about one or more phone numbers to the connected calling terminal. According to one embodiment, another terminal may transmit information about one or more phone numbers to the calling terminal based on a request received from the connected calling terminal.

In step 730, the calling terminal may identify one or more phone numbers or a list of phone numbers to be transmitted to the receiving terminal based on a phone number acquired from another terminal. According to one embodiment, one or more phone numbers or a list of phone numbers to be transmitted to the receiving terminal may include the unique phone number of the calling terminal.

In step 740, the calling terminal may attempt to make a call to the receiving terminal and transmit an INVITE SIP message. According to one embodiment, the INVITE SIP message transmitted from the calling terminal to the receiving terminal may include information about one or more phone numbers acquired by the calling terminal from another terminal along with the unique phone number of the calling terminal. According to one embodiment, when the calling terminal attempts to make a call to the called terminal, the phone number of the calling terminal displayed to the called terminal may be a phone number obtained based on the SIM inserted into the calling terminal. In addition, hereinafter, according to various embodiments of the present disclosure, when the calling terminal attempts to make a call to the called terminal, the phone number of the calling terminal displayed to the called terminal is the unique phone number (or a specific phone number, identification number) of the calling terminal. may be referred to as a phone number).

Figure 8 illustrates the flow of an operation in which a receiving terminal updates contact information based on a received phone number according to various embodiments of the present disclosure. According to various embodiments of the present disclosure, a series of steps or each step shown in FIG. 8 may be performed corresponding to or combined with steps 470 to 480 of FIG. 4.

In step 810, the receiving terminal can identify that the call with the calling terminal has ended. According to one embodiment, step 810 of identifying call termination may not be performed, and subsequent steps may proceed even when a call is in progress.

Although not shown in FIG. 8, according to various embodiments of the present disclosure, after step 810, the receiving terminal may identify whether one or more numbers received from the calling terminal are in a permanent state. According to one embodiment, the receiving terminal may identify the usage status of one or more numbers based on a classified phone number list included in the INVITE SIP message received from the sending terminal. According to one embodiment, if one or more phone numbers received by the receiving terminal are classified as permanent, step 820 may be performed. According to one embodiment, if one or more phone numbers received by the receiving terminal are classified as non-permanent, the procedure may be terminated. However, according to various embodiments of the present disclosure, the above-described steps are described as performing operations based on whether one or more phone numbers received by the receiving terminal are in a permanent state, but are not limited thereto and are not limited to this and are based on the usage state criteria. may include at least one of a permanent state, a temporary state, or an invalid state.

In step 820, the receiving terminal may identify whether one or more received phone numbers are stored in the receiving terminal or in the contact information of the receiving terminal. The receiving terminal or the contact information of the receiving terminal may include contacts that can be obtained from the receiving terminal device, software within the device, or an external server to which the receiving terminal can be connected. According to one embodiment, if one or more phone numbers received by the receiving terminal are stored in the receiving terminal or the contact information of the receiving terminal, step 830 may be performed. According to one embodiment, if one or more phone numbers received by the receiving terminal are not stored in the receiving terminal or the contact information of the receiving terminal, step 850 may be performed.

In step 850, the receiving terminal may recommend (for example, display or provide) an update to the contact information included in the receiving terminal. According to one embodiment, the receiving terminal may determine whether to update the contact number or contact list based on the usage status of one or more phone numbers. According to one embodiment, the receiving terminal may store one or more phone numbers received from the sending terminal in the contact information of the receiving terminal. According to one embodiment, the operation of updating the contact information of the receiving terminal may include storing one or more phone numbers that are not stored in the contact information of the receiving terminal.

In step 830, the receiving terminal may identify whether contacts in which one or more received phone numbers are stored are the same contact number. According to one embodiment, the receiving terminal may include contact information in which arbitrary phone numbers are stored. According to one embodiment, the receiving terminal may save one of the one or more phone numbers received from the sending terminal as a new contact, or one number of the one or more phone numbers received may be stored in the contacts of the receiving terminal. there is. According to one embodiment, if each contact number corresponding to one or more phone numbers received by the receiving terminal is the same contact number, the procedure may be terminated. According to one embodiment, if each contact number corresponding to one or more phone numbers received by the receiving terminal is not the same contact number, step 840 may be performed.

In step 840, the receiving terminal may recommend (eg, display or provide) merging each contact number corresponding to one or more received phone numbers. According to one embodiment, the receiving terminal displays or provides to the user whether to merge the contacts storing part of one or more phone numbers received from the sending terminal with the previously stored contacts storing the calling terminal's phone number. can do. According to one embodiment, each contact that the receiving terminal can merge may be contacts corresponding to the same sending terminal.

According to various embodiments of the present disclosure, steps 830 to 850 may be performed as one step. For example, the operation of the receiving terminal updating the contact information may be performed by merging the second contact information into the first contact information when one or more phone numbers received by the receiving terminal are not stored in the first contact information, but are stored in the second contact information ( merge) operation may be included.

Figure 9 illustrates the flow of operations for managing the phone number and contact information received by the receiving terminal when the anonymous number rejection function according to various embodiments of the present disclosure is activated. According to various embodiments of the present disclosure, a series of steps or each step shown in FIG. 9 may be performed corresponding to or combined with steps 410 to 450 of FIG. 4.

Although not shown in FIG. 9, before step 910, the receiving terminal may activate a function to automatically block calls from anonymous numbers. Additionally, the unique phone number of the calling terminal attempting to call the receiving terminal may be an anonymous phone number for the receiving terminal.

In step 910, the receiving terminal can identify whether the INVITE SIP message received from the calling terminal includes a phone number other than the unique phone number of the calling terminal. According to various embodiments of the present disclosure, operations similar to or substantially the same as steps 410 to 430 of FIG. 4 may be performed.

According to one embodiment, the receiving terminal can identify whether information about the phone number list has been received from the sending terminal. According to one embodiment, when the receiving terminal receives a call from the calling terminal, it can identify whether it has received information including the INVITE SIP message along with the unique phone number of the calling terminal. According to one embodiment, when the receiving terminal does not receive the INVITE SIP message (for example, including the case where the INVITE SIP message does not include a phone number other than the unique phone number of the calling terminal), the call from the calling terminal may be blocked and the procedure may be terminated. According to one embodiment, when the receiving terminal receives a call from the calling terminal, an INVITE SIP message (for example, including the case where the INVITE SIP message includes a phone number other than the unique phone number of the calling terminal) is also received. In one case, step 920 may be reached.

In step 920, the receiving terminal may disable the incoming call blocking function. According to one embodiment, when the receiving terminal receives an INVITE SIP message from the sending terminal, the 'function to automatically block calls from anonymous numbers' may be disabled. For example, when the receiving terminal receives an INVITE SIP message containing information about a phone number other than the unique phone number of the calling terminal from the calling terminal, it can ignore the activated blocking function and perform the following steps. According to one embodiment, if the 'function to automatically block calls from anonymous numbers' is not activated, the receiving terminal may not perform step 920.

In step 930, the receiving terminal displays contact information corresponding to one or more phone numbers included in messages received from the sending terminal (e.g., INVITE SIP message, message containing the unique phone number of the sending terminal). can do. According to one embodiment, the receiving terminal may display or provide one or more received numbers along with the unique phone number of the sending terminal corresponding to the anonymous number.

FIG. 10 illustrates a flow of operations for managing a phone number and contact information received by a receiving terminal when an unstored number rejection function according to various embodiments of the present disclosure is activated. According to various embodiments of the present disclosure, a series of steps or each step shown in FIG. 10 may be performed corresponding to or combined with steps 410 to 450 of FIG. 4.

Although not shown in FIG. 10, before step 1010, the receiving terminal may activate a function to automatically block calls from numbers not stored in the contact list.

In step 1010, the receiving terminal can identify whether the INVITE SIP message received from the calling terminal includes a phone number other than the unique phone number of the calling terminal. According to various embodiments of the present disclosure, operations similar to or substantially the same as steps 410 to 430 of FIG. 4 may be performed.

According to one embodiment, the receiving terminal can identify whether information about the phone number list has been received from the sending terminal. According to one embodiment, when the receiving terminal receives a call from the calling terminal, it can identify whether it has received information including the INVITE SIP message along with the unique phone number of the calling terminal. According to one embodiment, when the receiving terminal does not receive the INVITE SIP message (for example, including the case where the INVITE SIP message does not include a phone number other than the unique phone number of the calling terminal), the call from the calling terminal may be blocked and the procedure may be terminated. According to one embodiment, when the receiving terminal receives a call from the calling terminal, an INVITE SIP message (for example, including the case where the INVITE SIP message includes a phone number other than the unique phone number of the calling terminal) is also received. In one case, step 1020 may be reached.

In step 1020, the receiving terminal can identify whether one or more numbers received from the calling terminal are stored. The receiving terminal or the contact information of the receiving terminal may include contacts that can be obtained from the receiving terminal device, software within the device, or an external server to which the receiving terminal can be connected. According to one embodiment, the receiving terminal may proceed to step 1030 when some of the one or more phone numbers received are stored in the contact information of the receiving terminal. According to one embodiment, the receiving terminal may proceed to step 1040 when some of the one or more phone numbers received are not stored in the contact information of the receiving terminal.

In step 1030, the receiving terminal displays contact information corresponding to one or more phone numbers included in messages received from the sending terminal (e.g., INVITE SIP message, message containing the unique phone number of the sending terminal). can do. According to one embodiment, when one or more contacts corresponding to one or more received phone numbers are stored, the receiving terminal may display or provide a phone number without a corresponding contact along with the stored contacts.

In step 1040, the receiving terminal can identify whether a function to automatically block calls from numbers not stored in the contact list is activated. According to one embodiment, if the blocking function is activated, step 1050 may be performed. According to one embodiment, if the blocking function is not activated, step 1060 may be performed.

In step 1050, when the receiving terminal identifies that the unique phone number of the calling terminal is not stored and that the corresponding blocking function is activated, the receiving terminal can block the call from the calling terminal. According to one embodiment, the action of blocking a call may include not performing any action or display related to the calling terminal's call on the receiving terminal's display or application.

In step 1060, the receiving terminal displays contact information corresponding to one or more phone numbers included in messages received from the sending terminal (e.g., INVITE SIP message, message containing the unique phone number of the sending terminal). can do. According to one embodiment, the receiving terminal may display or provide one or more received numbers along with the unique phone number of the sending terminal corresponding to the anonymous number.

FIG. 11 illustrates a flow of operations for managing phone numbers and contact information received by a receiving terminal when a black list is activated according to various embodiments of the present disclosure. According to various embodiments of the present disclosure, a series of steps or each step shown in FIG. 11 may be performed corresponding to or combined with steps 410 to 450 of FIG. 4.

Although not shown in FIG. 11, before step 1110, the receiving terminal may create and store a black list for blocking calls. According to one embodiment, the unique phone number of the calling terminal attempting to call the receiving terminal may be included in the blacklist of the receiving terminal.

In step 1110, the receiving terminal can identify whether the unique phone number of the calling terminal is included in the black list. According to one embodiment, if the unique phone number of the calling terminal is included in the black list, step 1120 may be performed. According to one embodiment, if the unique phone number of the calling terminal is not included in the black list, the procedure may be terminated.

In step 1120, the receiving terminal can identify whether the INVITE SIP message received from the calling terminal includes a phone number other than the unique phone number of the calling terminal. According to various embodiments of the present disclosure, operations similar to or substantially the same as steps 410 to 430 of FIG. 4 may be performed.

According to one embodiment, the receiving terminal can identify whether information about the phone number list has been received from the sending terminal. According to one embodiment, when the receiving terminal receives a call from the calling terminal, it can identify whether it has received information including the INVITE SIP message along with the unique phone number of the calling terminal. According to one embodiment, when the receiving terminal does not receive the INVITE SIP message (for example, including the case where the INVITE SIP message does not include a phone number other than the unique phone number of the calling terminal), the call from the calling terminal may be blocked and may proceed to step 1140. According to one embodiment, when the receiving terminal receives a call from the calling terminal, an INVITE SIP message (for example, including the case where the INVITE SIP message includes a phone number other than the unique phone number of the calling terminal) is also received. In one case, step 1130 may be reached.

In step 1130, the receiving terminal may identify whether one or more phone numbers other than the unique phone number of the calling terminal are included in the blacklist. According to one embodiment, when one or more phone numbers other than the unique phone number of the calling terminal received by the receiving terminal (e.g., all phone numbers received by the receiving terminal) are included in the blacklist, step 1140 It can proceed as follows. According to one embodiment, if one or more phone numbers other than the unique phone number of the calling terminal received by the receiving terminal are not included in the blacklist, the procedure may be terminated.

In step 1140, when the receiving terminal identifies that both the unique phone number of the calling terminal and one or more other phone numbers are included in the blacklist, the receiving terminal may block a call from the calling terminal. According to one embodiment, the action of blocking a call may include not performing any action or display related to the calling terminal's call on the receiving terminal's display or application.

FIG. 12 illustrates a flow of operations for a receiving terminal to manage phone numbers and contact information based on valid or invalid keys according to various embodiments of the present disclosure. According to various embodiments of the present disclosure, a series of steps or each step shown in FIG. 12 may be performed corresponding to or combined with steps 410 to 450 of FIG. 4.

Although not shown in FIG. 12, before step 1210, the receiving terminal receives an INVITE SIP message from the calling terminal that further includes information about one or more phone numbers and a corresponding key in addition to the unique phone number of the calling terminal. You can receive it. According to one embodiment, the key may include personal information such as a hash string generated in the sending terminal. According to one embodiment, as the calling terminal and the receiving terminal perform a call, they may identify and store a key corresponding to the call. Accordingly, the key stored by each terminal can be used to confirm information related to the performed call. According to one embodiment, when a call is attempted from the calling terminal, the receiving terminal may receive a current key from the calling terminal and compare the received latest key with a key stored based on a previous call.

More specifically, according to one embodiment, when the sending terminal attempts to make a call to the receiving terminal, it can generate a private key and transmit it to the receiving terminal through an INVITE SIP message. According to one embodiment, the key may be a string such as a header value of a call-identifier (Call-ID). According to one embodiment, the receiving terminal may store information about one or more numbers received from the sending terminal and the corresponding key pair.

In step 1210, the receiving terminal can identify whether the INVITE SIP message received from the calling terminal includes a phone number other than the unique phone number of the calling terminal. According to various embodiments of the present disclosure, operations similar to or substantially the same as steps 410 to 430 of FIG. 4 may be performed.

According to one embodiment, the receiving terminal can identify whether information about the phone number list has been received from the sending terminal. According to one embodiment, when the receiving terminal receives a call from the calling terminal, it can identify whether it has received information including the INVITE SIP message along with the unique phone number of the calling terminal. According to one embodiment, when the receiving terminal does not receive the INVITE SIP message (for example, including the case where the INVITE SIP message does not include a phone number other than the unique phone number of the calling terminal), the call from the calling terminal may be blocked and may proceed to step 1250. According to one embodiment, when the receiving terminal receives a call from the calling terminal, an INVITE SIP message (for example, including the case where the INVITE SIP message includes a phone number other than the unique phone number of the calling terminal) is also received. In one case, step 1220 may be reached.

In step 1220, the receiving terminal may delete one or more phone numbers with invalid keys. According to one embodiment, the one or more phone numbers with the invalid key may include phone numbers that do not contain the key. According to one embodiment, the one or more phone numbers with an invalid key may include a phone number corresponding to a key that does not match information about a key previously stored in association with the one or more phone numbers. The receiving terminal can maintain security from the receiving phone number by identifying only one or more phone numbers corresponding to the valid key.

In step 1230, the receiving terminal can identify whether one or more numbers received from the calling terminal are stored. The receiving terminal or the contact information of the receiving terminal may include contacts that can be obtained from the receiving terminal device, software within the device, or an external server to which the receiving terminal can be connected. According to one embodiment, the receiving terminal may proceed to step 1240 when some of the one or more phone numbers received are stored in the contact information of the receiving terminal. According to one embodiment, the receiving terminal may proceed to step 1250 when some of the one or more phone numbers received are not stored in the contact information of the receiving terminal.

In step 1240, the receiving terminal displays contact information corresponding to one or more phone numbers included in messages received from the sending terminal (e.g., an INVITE SIP message, a message containing the unique phone number of the sending terminal). can do. According to one embodiment, when one or more contacts corresponding to one or more received phone numbers are stored, the receiving terminal may display or provide a phone number without a corresponding contact along with the stored contacts.

In step 1250, the receiving terminal displays a valid phone number among one or more phone numbers included in messages received from the sending terminal (e.g., an INVITE SIP message, a message containing the unique phone number of the sending terminal). can do.

FIG. 13 illustrates a flow of operations for a receiving terminal to manage phone numbers and contact information based on permanent or temporary phone number information according to various embodiments of the present disclosure. According to various embodiments of the present disclosure, a series of steps or each step shown in FIG. 13 may be performed corresponding to or combined with steps 410 to 450 of FIG. 4.

According to one embodiment, although not shown in FIG. 13, before step 1310, the receiving terminal may identify whether one or more numbers received from the calling terminal are in a permanent state. Whether one or more numbers received by the receiving terminal are in a permanent state may be determined through an operation similar or substantially the same as step 415 of FIG. 4, the authentication operation of FIG. 6, or step 720 of FIG. 7. According to one embodiment, although not shown in FIG. 13, before step 1310, the receiving terminal may identify whether one or more numbers received from the calling terminal are valid. Whether one or more numbers received by the receiving terminal are valid may be determined through operations similar or substantially the same as at least one of step 415 of FIG. 4, the authentication operation of FIG. 6, or step 720 of FIG. 7.

At step 1310, the receiving terminal may recommend deleting one or more phone numbers with invalid keys. According to one embodiment, the one or more phone numbers with the invalid key may include phone numbers that do not contain the key. According to one embodiment, the one or more phone numbers with an invalid key may include a phone number corresponding to a key that does not match information about a key previously stored in association with the one or more phone numbers. The receiving terminal can maintain security from the receiving phone number by identifying only one or more phone numbers corresponding to the valid key.

In step 1320, the receiving terminal may obtain a permanent phone number from the calling terminal. According to one embodiment, the receiving terminal may identify whether one or more numbers received from the calling terminal are in a permanent state. According to one embodiment, the receiving terminal may identify the usage status of one or more numbers based on a classified phone number list included in the INVITE SIP message received from the sending terminal. According to one embodiment, when one or more phone numbers received by the receiving terminal are classified as permanent, the receiving terminal may acquire one or more numbers in a permanent state.

In step 1330, the receiving terminal may identify whether one or more received phone numbers are stored in the receiving terminal or in the contact information of the receiving terminal. The receiving terminal or the contact information of the receiving terminal may include contacts that can be obtained from the receiving terminal device, software within the device, or an external server to which the receiving terminal can be connected. According to one embodiment, if one or more phone numbers received by the receiving terminal are stored in the receiving terminal or the contact information of the receiving terminal, step 1340 may be performed. According to one embodiment, if one or more phone numbers received by the receiving terminal are not stored in the receiving terminal or the contact information of the receiving terminal, step 1350 may be performed.

In step 1350, the receiving terminal may recommend (for example, display or provide) an update to the contact information included in the receiving terminal. According to one embodiment, the receiving terminal may determine whether to update the contact number or contact list based on the usage status of one or more phone numbers. According to one embodiment, the receiving terminal may store one or more phone numbers received from the sending terminal in the contact information of the receiving terminal. According to one embodiment, the operation of updating the contact information of the receiving terminal may include storing one or more phone numbers that are not stored in the contact information of the receiving terminal.

In step 1340, the receiving terminal may identify whether contacts in which one or more received phone numbers are stored are the same contact number. According to one embodiment, the receiving terminal may include contact information in which arbitrary phone numbers are stored. According to one embodiment, the receiving terminal may save one of the one or more phone numbers received from the sending terminal as a new contact, or one number of the one or more phone numbers received may be stored in the contacts of the receiving terminal. there is. According to one embodiment, if each contact number corresponding to one or more phone numbers received by the receiving terminal is the same contact number, the procedure may be terminated. According to one embodiment, if each contact number corresponding to one or more phone numbers received by the receiving terminal is not the same contact number, step 1360 may be performed.

In step 1360, the receiving terminal may recommend (eg, display or provide) merging each contact number corresponding to one or more received phone numbers. According to one embodiment, the receiving terminal displays or provides to the user whether to merge the contacts storing part of one or more phone numbers received from the sending terminal with the previously stored contacts storing the calling terminal's phone number. can do. According to one embodiment, each contact that the receiving terminal can merge may be contacts corresponding to the same sending terminal.

According to various embodiments of the present disclosure, steps 1340 to 1360 may be performed as one step. For example, the operation of the receiving terminal updating the contact information may be performed by merging the second contact information into the first contact information when one or more phone numbers received by the receiving terminal are not stored in the first contact information, but are stored in the second contact information ( merge) operation may be included.

According to various embodiments of the present disclosure, in a wireless communication system, a method performed by a first terminal includes obtaining at least one phone number from a plurality of available sources, the at least one phone number Classifying a number into one of a permanent state, a temporary state, or an invalid state according to a usage state, and transmitting a session initiation protocol (SIP) message containing information about the classified at least one phone number to a second terminal. may include.

According to one embodiment, the method includes transmitting a phone number associated with the first terminal to a server connected to the first terminal, receiving a phone number certified as valid by the server among the plurality of phone numbers. It may further include the step of transmitting the SIP message to the second terminal based on the phone number authenticated as valid.

According to one embodiment, a phone number certified as valid by the server among the plurality of phone numbers may include a phone number authenticated based on a one-time password (OTP) received from the server.

According to one embodiment, the method includes receiving a plurality of phone numbers from another terminal adjacent to the first terminal, and the first terminal based on the plurality of phone numbers received from another terminal adjacent to the first terminal. 2 The step of transmitting the SIP message to the terminal may be further included.

According to one embodiment, the method further includes generating a key corresponding to the at least one phone number, and transmitting the SIP message based on the at least one phone number and the generated key. can do.

According to various embodiments of the present disclosure, in a wireless communication system, a method performed by a second terminal includes receiving a session initiation protocol (SIP) message from a first terminal, a unique phone number of the first terminal, identifying that information about is not stored, identifying whether the SIP message includes at least one phone number different from the unique phone number of the first terminal, and displaying the at least one phone number. It may include a display step.

According to one embodiment, the method further includes disabling the blocking function for unstored phone numbers when the SIP message includes at least one phone number different from the unique phone number of the first terminal. It can be included.

According to one embodiment, the method includes identifying whether the unique phone number of the first terminal is included in a blacklist, wherein the SIP message contains at least one phone number different from the unique phone number of the first terminal. When including, identifying whether the at least one phone number is included in the black list, and if the at least one phone number is included in the black list, blocking a call from the first terminal. Additional steps may be included.

According to one embodiment, the method includes receiving the SIP message including the at least one phone number and a key corresponding to the at least one phone number from the first terminal, and the at least one phone number It may further include deleting the phone number corresponding to the invalid key from the list containing the at least one phone number based on the key corresponding to.

According to one embodiment, the method may include, when the SIP message includes at least one phone number different from the unique phone number of the first terminal, contact information of the second terminal based on the at least one phone number. An updating step may be further included.

According to various embodiments of the present disclosure, in a wireless communication system, a first terminal includes at least one transceiver and at least one processor functionally coupled to the at least one transceiver. wherein the at least one processor obtains at least one phone number from a plurality of available sources, and classifies the at least one phone number into one of a permanent state, a temporary state, or an invalid state depending on the usage state. And may be configured to transmit a session initiation protocol (SIP) message including information about the at least one classified phone number to the second terminal.

According to one embodiment, the at least one processor transmits a phone number related to the first terminal to a server connected to the first terminal, and a phone number certified as valid by the server among the plurality of phone numbers. and transmit the SIP message to the second terminal based on the phone number authenticated as valid.

According to one embodiment, a phone number certified as valid by the server among the plurality of phone numbers may include a phone number authenticated based on a one-time password (OTP) received from the server.

According to one embodiment, the at least one processor receives a plurality of phone numbers from another terminal adjacent to the first terminal, and based on the plurality of phone numbers received from another terminal adjacent to the first terminal, It may be further configured to transmit the SIP message to the second terminal.

According to one embodiment, the at least one processor is further configured to generate a key corresponding to the at least one phone number, and transmit the SIP message based on the at least one phone number and the generated key. It can be.

According to various embodiments of the present disclosure, in a wireless communication system, a second terminal includes at least one transceiver and at least one processor functionally coupled to the at least one transceiver. The at least one processor receives a session initiation protocol (SIP) message from a first terminal, identifies that information about the unique phone number of the first terminal is not stored, and the SIP message is transmitted to the first terminal. It may be configured to identify whether it includes at least one phone number different from the unique phone number of the first terminal, and to display the at least one phone number.

According to one embodiment, the at least one processor is configured to disable the blocking function for unstored phone numbers when the SIP message includes at least one phone number different from the unique phone number of the first terminal. It can be configured further.

According to one embodiment, the at least one processor identifies whether the unique phone number of the first terminal is included in a blacklist, and the SIP message includes at least one message different from the unique phone number of the first terminal. If it includes a phone number, identify whether the at least one phone number is included in the black list, and if the at least one phone number is included in the black list, block a call from the first terminal. It may be further configured to do so.

According to one embodiment, the at least one processor receives the SIP message including the at least one phone number and a key corresponding to the at least one phone number from the first terminal, and the at least one The method may be further configured to delete a phone number corresponding to an invalid key from the list containing the at least one phone number based on the key corresponding to the phone number.

According to one embodiment, the at least one processor is, when the SIP message includes at least one phone number different from the unique phone number of the first terminal, the second terminal based on the at least one phone number. It may be further configured to update the contact information of .

Methods according to embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

When implemented as software, a computer-readable storage medium that stores one or more programs (software modules) may be provided. One or more programs stored in a computer-readable storage medium are configured to be executable by one or more processors in an electronic device (configured for execution). One or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.

These programs (software modules, software) may include random access memory, non-volatile memory, including flash memory, read only memory (ROM), and electrically erasable programmable ROM. (electrically erasable programmable read only memory, EEPROM), magnetic disc storage device, compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other types of disk storage. It can be stored in an optical storage device or magnetic cassette. Alternatively, it may be stored in a memory consisting of a combination of some or all of these. Additionally, a plurality of each configuration memory may be included.

In addition, the program may be distributed through a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), or a storage area network (SAN), or a combination thereof. It may be stored on an attachable storage device that is accessible. This storage device can be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communications network may be connected to the device performing embodiments of the present disclosure.

In the specific embodiments of the present disclosure described above, elements included in the disclosure are expressed in singular or plural numbers depending on the specific embodiment presented. However, singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components, and even components expressed in plural may be composed of singular or singular. Even expressed components may be composed of plural elements.

Meanwhile, in the detailed description of the present disclosure, specific embodiments have been described, but of course, various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be determined not only by the scope of the patent claims described later, but also by the scope of this patent claim and equivalents.

Claims (20)

In a wireless communication system, the method performed by the first terminal is:
Obtaining at least one phone number from a plurality of available sources;
classifying the at least one phone number into one of a permanent state, a temporary state, or an invalid state according to a usage state; and
A method comprising transmitting a session initiation protocol (SIP) message including information about the at least one classified phone number to a second terminal.
The method of claim 1, wherein the method comprises:
transmitting a phone number related to the first terminal to a server connected to the first terminal;
Receiving a phone number certified as valid by the server among the plurality of phone numbers; and
The method further comprising transmitting the SIP message to the second terminal based on the phone number authenticated as valid.
The method of claim 2, wherein the phone number certified as valid by the server among the plurality of phone numbers includes a phone number authenticated based on a one-time password (OTP) received from the server.
The method of claim 1, wherein the method comprises:
Receiving a plurality of phone numbers from another terminal adjacent to the first terminal; and
The method further includes transmitting the SIP message to the second terminal based on a plurality of phone numbers received from another terminal adjacent to the first terminal.
The method of claim 1, wherein the method comprises:
generating a key corresponding to the at least one phone number; and
The method further comprising transmitting the SIP message based on the at least one phone number and the generated key.
In a wireless communication system, the method performed by the second terminal is:
Receiving a session initiation protocol (SIP) message from a first terminal;
identifying that information on the unique phone number of the first terminal is not stored;
Identifying whether the SIP message includes at least one phone number different from the unique phone number of the first terminal; and
A method comprising displaying the at least one phone number.
The method of claim 6, wherein the method:
If the SIP message includes at least one phone number different from the unique phone number of the first terminal, the method further includes disabling a blocking function for a phone number that is not stored.
The method of claim 6, wherein the method:
identifying whether the unique phone number of the first terminal is included in a black list;
When the SIP message includes at least one phone number that is different from the unique phone number of the first terminal, identifying whether the at least one phone number is included in a blacklist; and
The method further includes blocking a call from the first terminal when the at least one phone number is included in the blacklist.
The method of claim 6, wherein the method:
Receiving the SIP message including the at least one phone number and a key corresponding to the at least one phone number from the first terminal; and
The method further includes deleting a phone number corresponding to an invalid key from a list containing the at least one phone number based on the key corresponding to the at least one phone number.
The method of claim 6, wherein the method:
If the SIP message includes at least one phone number different from the unique phone number of the first terminal, the method further includes updating the contact information of the second terminal based on the at least one phone number.
In a wireless communication system, the first terminal,
At least one transceiver; and
Comprising at least one processor functionally coupled to the at least one transceiver,
The at least one processor,
Obtain at least one telephone number from a plurality of available sources,
classify the at least one phone number into one of permanent, temporary, or invalid status depending on its usage status, and
A device configured to transmit a session initiation protocol (SIP) message including information about the at least one classified phone number to a second terminal.
The method of claim 11, wherein the at least one processor:
Transmitting a phone number related to the first terminal to a server connected to the first terminal,
Receiving a phone number certified as valid by the server among the plurality of phone numbers, and
The device is further configured to transmit the SIP message to the second terminal based on the phone number authenticated as valid.
The device of claim 12, wherein the phone number certified as valid by the server among the plurality of phone numbers includes a phone number authenticated based on a one-time password (OTP) received from the server.
The method of claim 11, wherein the at least one processor:
Receiving a plurality of phone numbers from another terminal adjacent to the first terminal, and
The device is further configured to transmit the SIP message to the second terminal based on a plurality of phone numbers received from another terminal adjacent to the first terminal.
The method of claim 11, wherein the at least one processor:
generate a key corresponding to the at least one phone number, and
The device further configured to transmit the SIP message based on the at least one phone number and the generated key.
In a wireless communication system, the second terminal,
At least one transceiver; and
Comprising at least one processor functionally coupled to the at least one transceiver,
The at least one processor,
Receive a session initiation protocol (SIP) message from the first terminal,
Identifying that information about the unique phone number of the first terminal is not stored,
Identify whether the SIP message includes at least one phone number different from the unique phone number of the first terminal, and
A device configured to display the at least one phone number.
The method of claim 16, wherein the at least one processor:
The device is further configured to disable a blocking function for unstored phone numbers when the SIP message includes at least one phone number different from the unique phone number of the first terminal.
The method of claim 16, wherein the at least one processor:
Identify whether the unique phone number of the first terminal is included in the black list,
If the SIP message includes at least one phone number different from the unique phone number of the first terminal, identify whether the at least one phone number is included in a blacklist, and
The device is further configured to block a call from the first terminal when the at least one phone number is included in a blacklist.
The method of claim 16, wherein the at least one processor:
Receiving the SIP message including the at least one phone number and a key corresponding to the at least one phone number from the first terminal, and
The apparatus further configured to delete a phone number corresponding to an invalid key from the list containing the at least one phone number based on the key corresponding to the at least one phone number.
The method of claim 16, wherein the at least one processor:
If the SIP message includes at least one phone number that is different from the unique phone number of the first terminal, the device is further configured to update the contact information of the second terminal based on the at least one phone number.

Images