Method and system for making or answering mobile phone calls

Abstract

A method for making and answering a mobile phone call may be provided, the method comprising the steps of: generating, by a first device, a public key and a private key, and generating caller data in which a phone number for making a mobile phone call is hashed; generating a caller representative code by encoding the caller data using the private key; sending the caller representative code and the public key to a second device when making a mobile phone call; if the received public key exists in an address book of a second device, obtaining, by the second device, the caller data by decoding the received caller representative code using the public key; hashing the incoming phone number; a caller of the mobile phone is identified by comparing the hashed incoming phone number with the obtained caller data.

Description

Technical Field

[0001] Various embodiments relate to methods and systems for sending and receiving mobile phone calls. More specifically, embodiments relate to methods and systems for sending and receiving mobile phone calls, wherein the caller can be authenticated or identified by using a public key, a private key, and an incoming phone number. Background Art

[0002] With the ability to use multiple Subscriber Identity Module (SIM) cards in one mobile phone, a single mobile phone device can now have multiple outgoing telephone numbers.

[0003] In case a caller makes a call on a single mobile phone by using any one of different SIM cards, and the phone number of the used SIM card among the phone numbers of all SIM cards is not registered in the call receiver's address book, the call receiver may not recognize who the caller is.

[0004] Additionally, scams have emerged where hackers intercept calls and text messages from specific users by swapping the user's phone number with the hacker's third-party SIM card.

[0005] These changes in the communications environment have resulted in an increased demand for new technologies for sending and receiving mobile phone calls. Summary of the invention

[0006] Solution According to an embodiment, a method for sending and receiving a mobile phone call may include generating a public key and a private key by a first device, and generating caller data by hashing a phone number from which the mobile phone call is to be sent. According to an embodiment, the method for sending and receiving a mobile phone call may include generating a caller representative code by the first device by encrypting the caller data using the private key. According to an embodiment, the method for sending and receiving a mobile phone call may include sending the caller representative code and the public key by the first device to a second device when sending the mobile phone call. According to an embodiment, the method for sending and receiving a mobile phone call may include obtaining the caller data by decrypting the received caller representative code by the second device using the public key based on the existence of the received public key in an address book of the second device. According to an embodiment, the method for sending and receiving a mobile phone call may include hashing an incoming phone number by the second device. The method for sending and receiving a mobile phone call may include identifying the sender of the mobile phone call by the second device by comparing the hashed incoming phone number with the obtained caller data.

[0007] According to an embodiment, a system for sending and receiving mobile phone calls may include a first device, wherein the first device is configured to generate a public key and a private key, and generate caller data by hashing a telephone number from which the mobile phone call is to be sent. According to an embodiment, the system for sending and receiving mobile phone calls may include a first device configured to generate a caller representative code by encrypting the caller data using the private key. According to an embodiment, the system for sending and receiving mobile phone calls may include a first device configured to send the caller representative code and the public key to a second device when sending the mobile phone call.

[0008] According to an embodiment, a system for sending and receiving mobile phone calls may include a second device, wherein the second device is configured to obtain the caller data by decrypting the received caller representative code using the public key based on the received public key existing in the address book. According to an embodiment, a system for sending and receiving mobile phone calls may include a second device configured to hash an incoming phone number. According to an embodiment, a system for sending and receiving mobile phone calls may include a second device configured to identify the sender of the mobile phone call by comparing the hashed incoming phone number with the obtained caller data. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1a is a diagram showing an example of the operation of a mobile phone device according to the related art.

[0010] Figure 1b is a diagram illustrating an example of the operation of the mobile phone device according to an embodiment of the present disclosure.

[0011] Figure 2 is a block diagram illustrating a configuration of a system for sending and receiving a mobile phone call according to an embodiment of the present disclosure.

[0012] Figure 3 is a flow chart of a method of sending and receiving a mobile phone call according to an embodiment of the present disclosure.

[0013] Figure 4 is a diagram illustrating a data flow in a system for sending and receiving a mobile phone call according to an embodiment of the present disclosure.

[0014] Figure 5 is a block diagram illustrating a configuration of a first device according to an embodiment of the present disclosure.

[0015] Figure 6 is a block diagram for describing in more detail the configuration of a first device according to another embodiment of the present disclosure.

[0016] Figure 7 is a flowchart of a method of sending a mobile phone call performed by a first device according to an embodiment of the present disclosure.

[0017] Figure 8 is a diagram illustrating an example in which a mobile phone device manages an address book according to an embodiment of the present disclosure.

[0018] Fig. 9 is a diagram illustrating an example in which a first device generates a caller representative code according to an embodiment of the present disclosure.

[0019] Fig.10 is a block diagram illustrating a configuration of a second device according to an embodiment of the present disclosure.

[0020] Fig.11 is a flowchart of a method of receiving a mobile phone call performed by a second device according to an embodiment of the present disclosure.

[0021] Fig.12a is a diagram illustrating an example in which a second device generates an entry in an address book according to an embodiment of the present disclosure.

[0022] Figure 12b is a diagram illustrating an example in which a second device updates an address book according to an embodiment of the present disclosure.

[0023] Fig.12c is a diagram illustrating an example of an address book managed by a second device according to an embodiment of the present disclosure.

[0024] Fig.13 is a flowchart of a method of receiving a mobile phone call performed by a second device according to an embodiment of the present disclosure.

[0025] Fig.14 is a flowchart of a method of receiving a mobile phone call performed by a second device according to an embodiment of the present disclosure.

[0026] Fig.15 is a flowchart of a method for receiving a mobile phone message performed by a second device according to an embodiment of the present disclosure.

[0027] Fig.16 is a flow chart of a method of sending and receiving a mobile phone call according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0028] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings so that those skilled in the art can implement the present disclosure without difficulty. However, the present disclosure may be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein.

[0029] Although the terms used herein are general terms that are currently widely used and selected by considering their functions, the meanings of the terms may vary according to the intentions of ordinary technicians in the field, legal precedents, or the emergence of new technologies. Therefore, the terms should not be defined by their simple titles, but are defined based on their meanings and the context of the description throughout the present disclosure.

[0030] In addition, the terminology used herein is for describing particular embodiments and is not intended to limit the scope of the present disclosure.

[0031] Throughout this specification, when a component is referred to as being “connected to” another component, it may be “directly connected to” the other component or “electrically connected to” the other component through an intervening element.

[0032] The term "said" and other descriptions similar thereto in this specification (especially in the appended claims) should be understood to include both singular and plural forms. In addition, when there is no description of the order of operations of the method according to the present disclosure, the operations can be performed in an appropriate order. The present disclosure is not limited to the order of operations described.

[0033] As used herein, phrases such as "in some embodiments" or "in an embodiment" are not necessarily referring to the same embodiment.

[0034] Some embodiments of the present disclosure can be represented by block components and various processing operations. Some or all of the function blocks can be implemented by any number of hardware and / or software elements that perform a specific function. For example, the function blocks of the present disclosure can be embodied by at least one microprocessor or by a circuit component for a specific function. In addition, for example, the function blocks of the present disclosure can be implemented by using various programming or scripting languages. The function blocks can be implemented by using various algorithms that can be executed by one or more processors. In addition, the present disclosure can adopt known technologies for electronic settings, signal processing and / or data processing. Terms such as "mechanism", "element", "unit" or "component" are used in a broad sense and are not limited to mechanical or physical components.

[0035] In addition, the connecting lines or connecting members between components shown in the drawings are merely examples of functional connections and / or physical or circuit connections. Various alternative or additional functional connections, physical connections or circuit connections between components may exist in an actual device.

[0036] In addition, as used herein, terms such as “…machine”, “…unit”, “…module” and the like mean a unit that performs at least one function or operation, which may be implemented as hardware or software or a combination thereof.

[0037] Additionally, as used herein, the term "user" may refer to a person who uses a mobile phone device to control functions or operations of the mobile phone device.

[0038] As used herein, the term "mobile phone device" may refer to various mobile devices capable of sending and receiving mobile phone calls. For example, the mobile phone device may be implemented in various forms, such as a smart phone, a smart watch, a tablet personal computer (PC), a laptop computer, a netbook computer, a personal digital assistant (PDA), a portable multimedia player (PMP), or a wearable device.

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

[0040] Figure 1a is a diagram showing an example of the operation of a mobile phone device according to the related art, and Figure 1b is a diagram illustrating an example of the operation of the mobile phone device according to an embodiment of the present disclosure.

[0041] In the present disclosure, the first device 100 and the second device 200 may be mobile phone devices. In the present disclosure, user A may be a user of the first device 100, and user B may be a user of the second device 200.

[0042] In the present disclosure, the first device 100 or the second device 200 may use multiple user identity module (SIM) cards. The multiple SIM cards may include a physical universal SIM (USIM) or an embedded SIM (eSIM). The physical USIM may include USIMs of various sizes, such as a standard USIM, a micro USIM, or a nano-USIM. eSIM stands for embedded SIM, which means that it uses an eSIM chip inside the device, thereby eliminating the need for a physical USIM card.

[0043] exist Figure 1a and Figure 1b In the embodiment of the present invention, the first device 100 can use the first SIM card to use the first phone number and use the second SIM card to use the second phone number. The second device 200 receiving the call from the first device 100 can store the first phone number of user A in its address book, but may not store the second phone number of user A.

[0044] exist Figure 1a and Figure 1bIn an embodiment of the present invention, the first device 100 may send a mobile phone call to the second device using the first phone number by using the first SIM card. In this case, the second device 200 may receive the first phone number as an incoming phone number. The second device 200 may search the received first phone number in the address book and display the user A corresponding to the first phone number on the display as the sender of the mobile phone call.

[0045] According to the relevant technology Figure 1a In an embodiment of the present invention, the first device 100 may send a mobile phone call to the second device 200 using the second phone number by using the second SIM card. In this case, the second device 200 may receive the second phone number as an incoming phone number. As a result of searching the received second phone number in the address book, the second device 200 may recognize that the user corresponding to the second phone number is not stored in the address book. In this case, the second device 200 cannot automatically recognize to whom the incoming phone number corresponds, and therefore may display the incoming phone number on the screen as it is.

[0046] In the embodiment according to the present disclosure Figure 1b In an embodiment of the present disclosure, the first device 100 can send a mobile phone call to the second device using the second phone number by using the second SIM card. In this case, the second device 200 can receive the second phone number as an incoming phone number. As a result of searching the received second phone number in the address book, the second device 200 can identify that the user corresponding to the second phone number is not stored in the address book. However, even when the second phone number is not stored in the address book, the second device 200 according to an embodiment of the present disclosure can confirm that the second phone number is another phone number of user A by using the public key received from the first device 100. In this case, the second device 200 can identify user A as the sender of the mobile phone call and display the identified sender on the display.

[0047] In addition, according to an embodiment of the present disclosure, since a public key unique to each device is generated, the second device 200 can verify whether a received mobile phone call is actually sent by the first device 100 owned by user A using a public key or the like.

[0048] This will be described in detail below.

[0049] Figure 2 is a block diagram illustrating a configuration of a system for sending and receiving a mobile phone call according to an embodiment of the present disclosure.

[0050] A system for sending and receiving a mobile phone call according to an embodiment of the present disclosure may include a first device 100 , a second device 200 , and a network 300 .

[0051] In an embodiment, the first device 100 may generate a public key and a private key.

[0052] In an embodiment, the first device 100 may generate a public key and a private key through an authorized certification authority.

[0053] In an embodiment, each of the public key and the private key may be paired with a passphrase to be protected.

[0054] In an embodiment, the private key may be recovered through use of a passphrase.

[0055] In this specification, the term "pass phrase" may refer to a string of words that is longer than a typical password, easier to remember, and difficult to crack or hack, and is used for authentication.

[0056] In order to prevent hackers from exchanging the user's mobile phone number with the hacker's SIM card, the first device 100 can strictly limit the generation of public keys and private keys. For example, the first device 100 can be configured to generate public keys and private keys only when the user sets a security method.

[0057] When the user deletes the security method, the first device 100 can discard the public key and the private key so that they are no longer usable.

[0058] In the present disclosure, a public key and a private key unique to a device may be generated. That is, a device may have one public key and one private key. Multiple SIM cards used in a single device may be assigned the same public key and private key.

[0059] In the embodiment of the present disclosure, when the SIM card is replaced or reissued, the public key or private key can be used to identify whether the user is a legitimate user. When the user fails to provide the correct public key, the replacement or reissue of the SIM card can be restricted.

[0060] For example, in the case where a user loses a SIM card, a person who finds the SIM card cannot provide the public key corresponding to the SIM card and therefore cannot utilize the SIM card.

[0061] In embodiments of the present disclosure, a public key or private key may be required to perform a security-critical change process, such as changing an account, password, or one-time password (OTP). That is, a user can only change an account, password, OTP, etc. by providing the correct public key or private key.

[0062] In embodiments of the present disclosure, the public key may prevent scams (fraud) by making it impossible for a hacker to transfer a user's phone number to another SIM card without providing the public key or private key.

[0063] In an embodiment of the present disclosure, when a SIM card of a mobile phone call sender or receiver is transferred to another person, the mobile phone device may cause a message or pop-up message to be displayed on the other party's mobile phone device to warn of the transfer of the SIM card.

[0064] In an embodiment of the present disclosure, a private key may be used to encrypt information related to a phone number, and a public key may be used to decrypt the encrypted information related to the phone number.

[0065] In an embodiment, the public key of the sender device (ie, the first device 100) may be received by the receiving mobile phone device (ie, the second device 200), stored in an address book, and used to identify the sender of the incoming call.

[0066] In an embodiment, the first device 100 may generate the caller data by hashing the telephone number from which the mobile phone call is to be sent.

[0067] In this specification, the term "hashing" may refer to converting a numeric string into a shorter value or key to represent the original numeric string, thereby allowing faster retrieval than using the original value. Hash data may be used for retrieval by indexing items within a database.

[0068] The following will refer to Fig. 9 etc. describe the generation of caller data in detail.

[0069] In an embodiment, the first device 100 may generate a caller representative code by encrypting the generated caller data using a private key.

[0070] In an embodiment, when the first device 100 sends a mobile phone call, the first device 100 may send a caller representative code and a public key to the second device 200 .

[0071] In an embodiment, the second device 200 may determine whether the public key received from the first device 100 exists in the address book, and obtain the caller data by decrypting the received caller representative code using the public key when the received public key exists in the address book.

[0072] In an embodiment, the second device 200 may hash the incoming phone number received from the network 300 .

[0073] In an embodiment, the second device 200 can identify the sender of the mobile phone call by comparing the hashed incoming phone number with the obtained caller data.

[0074] In an embodiment, the network 300 may receive data from the first device 100 and transmit the data to the second device 200 .

[0075] In an embodiment, the network 300 may send the incoming phone number to the second device 200 .

[0076] Figure 3 is a flow chart of a method of sending and receiving a mobile phone call according to an embodiment of the present disclosure.

[0077] Reference Figure 3 In a system for sending and receiving a mobile phone call, the first device 100 may generate a public key and a private key and generate caller data by hashing a phone number from which a mobile phone call is to be sent (S310).

[0078] The above reference will be omitted Figure 2 Provides a redundant description of the public and private keys.

[0079] When the first device 100 has already generated the public key and the private key, the generation of the public key and the private key may be omitted.

[0080] The telephone number from which the mobile phone call is to be sent may be a telephone number corresponding to a SIM card selected by user A from among a plurality of SIM cards used by the first device 100 to be used for sending the mobile phone call.

[0081] The first device 100 may generate caller data by hashing the telephone number from which the mobile phone call is to be sent. Fig. 9 etc. describe hashing in detail.

[0082] In the system for sending and receiving a mobile phone call, the first device 100 may generate a caller representative code by encrypting caller data using a private key (S320).

[0083] In the system for sending and receiving a mobile phone call, when sending a mobile phone call, the first device 100 may send a caller representative code and a public key to the second device (S330).

[0084] In an embodiment, the first device 100 may send the caller representative code and the public key to the second device via the network 300. The sending may be performed automatically without user intervention.

[0085] In the system for sending and receiving mobile phone calls, when the received public key exists in the address book of the second device 200, the second device 200 may obtain the caller data by decrypting the received caller representative code using the public key (S340).

[0086] The second device 200 may determine whether the received public key of the first device 100 exists in the address book of the second device 200. When the received public key exists in the address book of the second device 200, the second device 200 may obtain the caller data by decrypting the received caller representative code using the received public key of the first device 100.

[0087] The obtained caller data may be the same as the caller data generated by the first device 100 in operation S310.

[0088] In the system for sending and receiving mobile phone calls, the second device 200 may hash an incoming phone number (S350).

[0089] The second device 200 may hash the incoming phone number by using the same hash function as that used by the first device 100 .

[0090] In the system for sending and receiving mobile phone calls according to the embodiment, all mobile phone devices may share a hash function.

[0091] exist Figure 3 In the embodiment of FIG. 5 , operation S340 is shown as being performed before operation S350, but operations S340 and S350 may be performed in another order or may be performed simultaneously.

[0092] In the system for sending and receiving a mobile phone call, the second device 200 may identify the sender of the mobile phone call by comparing the hashed incoming phone number with the obtained caller data (S360).

[0093] The following will refer to Fig.11 , Fig.13 , Fig.14 , Fig.15 etc. describe in detail the process by which the second device 200 identifies the sender of a mobile phone call.

[0094] The method for sending and receiving a mobile phone call according to an embodiment of the present disclosure may include: generating a public key and a private key by the first device 100, sending a caller representative code and a public key by the first device 100 to the second device 200 when sending a mobile phone call, and identifying, by the second device 200, a user corresponding to the public key in the address book of the second device 200 as the sender of the mobile phone call when the received public key exists in the address book of the second device 200. In this embodiment, the private key may be omitted. Figure 3. In this embodiment, in a case where the first device 100 uses multiple SIM cards and only the first phone number is registered in the address book of the second device 200 among the multiple SIM cards, when the first device 100 sends a mobile phone call using a second phone number that is not registered in the address book of the second device 200, the second device 200 can detect that the call is made by the user of the first device 100. However, this embodiment may not include a security function to prevent hackers from exchanging mobile phone numbers. That is, even in a case where a hacker exchanges the mobile phone number of the first device 100 with the hacker's SIM card to impersonate the user of the first device 100, the second device 200 can display the sender of the mobile phone call as the user of the first device 100.

[0095] According to an embodiment of the present disclosure, the method for sending and receiving a mobile phone call may include: generating a public key and a private key by the first device 100, generating a caller representative code by the first device 100 by encrypting a phone number used to send the mobile phone call using the private key, sending the caller representative code and the public key by the first device 100 to the second device when sending the mobile phone call, decrypting the received caller representative code by the second device 200 by using the public key to obtain the sender's phone number when the received public key exists in the address book of the second device 200, and identifying the sender of the mobile phone call by the second device 200 by comparing the received incoming phone number with the obtained phone number. This embodiment omits Figure 3 In the case of hashing the mobile phone number, the retrieval speed may be reduced. In the present embodiment, in the case where the first device 100 uses multiple SIM cards and only the first phone number is registered in the address book of the second device 200 among the multiple SIM cards, when the first device 100 sends a mobile phone call using the second phone number that is not registered in the address book of the second device 200, the second device 200 may detect that the call is made by the user of the first device 100. The present embodiment may include a security function to prevent hackers from exchanging mobile phone numbers. That is, even in the case where a hacker exchanges the mobile phone number of the first device 100 with the hacker's SIM card to impersonate the user of the first device 100, the second device 200 may not display the sender of the mobile phone call as the user of the first device 100.

[0096] Figure 4 is a diagram illustrating a data flow in a system for sending and receiving a mobile phone call according to an embodiment of the present disclosure.

[0097] When user A, who is a user of the first device 100 , makes a mobile phone call to the second device 200 by using the first phone number, the first device 100 may transmit a message including a public key of the first device 100 and a caller representative code of the first device 100 to the network 300 .

[0098] In an embodiment, the message may be a Session Initiation Protocol (SIP) Invite message.

[0099] The network 300 may add the incoming phone number 1 to the received message and send a message including the public key of the first device 100 , the caller representative code of the first device 100 , and the incoming phone number 1 to the second device 200 .

[0100] In one embodiment, the incoming telephone number 1 may be the same as the first telephone number.

[0101] In an embodiment, the incoming telephone number 1 may have been obtained by the network 300 .

[0102] The first device 100 may transmit the public key of the first device 100 and the caller representative code of the first device 100 to the second device 200 via the network 300 .

[0103] The incoming phone number 1 may be sent by the network 300 to the second device 200 .

[0104] The incoming phone number 1 may be different from the incoming phone number sent by the first device 100 to the second device 200 .

[0105] The second device 200 may store the received first phone number and public key of the first device 100 in an address book for user A.

[0106] After the second device 200 stores the received first phone number and public key of the first device 100 in the address book for user A, user A, who is a user of the first device 100, can send a mobile phone call to the second device 200 by using the second phone number.

[0107] When user A, who is a user of the first device 100 , sends a mobile phone call to the second device 200 by using the second phone number, the first device 100 may send a message including a public key of the first device 100 and a caller representative code of the first device 100 to the network 300 .

[0108] In an embodiment, the message may be a SIP INVITE message.

[0109] The network 300 may add the incoming phone number 2 to the received message and send a message including the public key of the first device 100 , the caller representative code of the first device 100 , and the incoming phone number 2 to the second device 200 .

[0110] In an embodiment, the incoming telephone number 2 may be the same as the second telephone number.

[0111] In an embodiment, the incoming telephone number 2 may have been obtained by the network 300 .

[0112] The first device 100 may transmit the public key of the first device 100 and the caller representative code of the first device 100 to the second device 200 via the network 300 .

[0113] The incoming phone number 2 may be sent by the network 300 to the second device 200 .

[0114] The incoming phone number 2 may be different from the incoming phone number sent by the first device 100 to the second device 200 .

[0115] The second device 200 may detect that the received public key of the first device 100 exists in the address book. The second device 200 may search the address book and confirm that the received public key of the first device 100 matches the public key of user A stored in the address book.

[0116] The second device 200 may display user A, who is the user corresponding to the received public key, as the sender of the incoming mobile phone call on the display.

[0117] In an embodiment, the second device 200 can search for the received public key in the address book, and when the received public key matches the public key of user A stored in the address book and the result of decrypting the received caller representative code matches the incoming phone number, user A, who is the user corresponding to the received public key, is displayed on the display as the sender of the incoming mobile phone call.

[0118] In an embodiment, the second device 200 may update the address book by adding the second phone number as user A's mobile phone number.

[0119] Figure 5 is a block diagram illustrating a configuration of a first device according to an embodiment of the present disclosure.

[0120] refer to Figure 5 , the first device 100 may include a processor 110 , a memory 120 , and a display 130 .

[0121] The memory 120 may store a program for processing and control performed by the processor 110. In addition, the memory 120 may store data input to or output from the first device 100.

[0122] The memory 120 may include at least one of an internal memory (not shown) and an external memory (not shown). The memory 120 may store control history information, current environment information, and state information.

[0123] The memory 120 may include at least one of a flash memory type storage medium, a hard disk type storage medium, a multimedia card micro storage medium, a card type memory (e.g., an SD or XD memory), a random access memory (RAM), a static RAM (SRAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), a programmable ROM (PROM), a magnetic memory, a magnetic disk, and an optical disk.

[0124] The internal memory may include, for example, at least one of a volatile memory (e.g., dynamic RAM (DRAM), SRAM, synchronous DRAM (SDRAM), etc.), a non-volatile memory (e.g., one-time programmable read-only memory (OTPROM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), mask ROM, flash ROM, etc.), a hard disk drive (HDD), or a solid-state drive (SSD).

[0125] According to an embodiment, the processor 110 may load a command or data received from at least one of the non-volatile memory or other components into the volatile memory and process the command or data. In addition, the processor 110 may store data received from other components or generated by the processor 110 in the non-volatile memory.

[0126] The external memory may include, for example, at least one of Compact Flash (CF), Secure Digital (SD), Micro SD, Mini SD, Extreme Digital (xD), or Memory Stick.

[0127] The memory 120 may store one or more instructions executable by the processor 110 .

[0128] In an embodiment, the memory 120 may store various types of information input through an input / output unit (not shown).

[0129] In an embodiment, the memory 120 may store instructions for controlling the processor to generate a public key and a private key, generate caller data by hashing a telephone number from which a mobile phone call will be sent, generate a caller representative code by encrypting the caller data using the private key, and send the caller representative code and the public key to a second device when the mobile phone call is sent.

[0130] When a user input is received or a preset and stored condition is satisfied, the processor 110 may execute an operating system (OS) and various applications stored in the memory 120 .

[0131] The processor 110 may include a RAM and a ROM, wherein the RAM is used to store signals or data input from outside the first device 100 or to be used as a storage area for various operations performed by the first device 100 , and the ROM is used to store multiple instructions and / or control programs for controlling the first device 100 .

[0132] The processor 110 may include a single core, a dual core, a triple core, a quad core, or a core corresponding to a multiple thereof. In addition, the processor 110 may include a plurality of processors. For example, the processor 110 may be implemented as a main processor (not shown) and a sub-processor (not shown) operating in a sleep mode.

[0133] In addition, the processor 110 may include at least one of a central processing unit (CPU), a graphics processing unit (GPU), and a video processing unit (VPU). Optionally, according to an embodiment, the processor 110 may be implemented as a system on chip (SoC) in which at least one of the CPU, GPU, and VPU is integrated.

[0134] The processor 110 may execute one or more instructions stored in the memory 120 to control various components of the first device 100 .

[0135] In an embodiment, the processor 110 may generate a public key and a private key, and generate caller data by hashing a phone number from which a mobile phone call is to be sent. In an embodiment, the processor 110 may generate a caller representative code by encrypting the caller data using the private key. In an embodiment, when sending a mobile phone call, the processor 110 may send the caller representative code and the public key to the second device 200. In an embodiment, the processor 110 may select a phone number corresponding to a SIM card selected from a plurality of SIM cards used by the first device 100 as the phone number to be used to send the mobile phone call.

[0136] Figure 6 is a block diagram for describing in more detail the configuration of a first device according to another embodiment of the present disclosure.

[0137] Figure 6 The first device 100 may be the one referred to above Figure 1a , Figure 1b and Figures 2 to 5 An embodiment of a first apparatus 100 is described.

[0138] Figure 6 The processor 110 corresponds to Figure 5 The processor 110, Figure 6 The memory 120 corresponds to Figure 5 The memory 120, and Figure 6 The display 130 corresponds to Figure 5 Therefore, hereinafter, the description already provided above will be omitted.

[0139] according to Figure 6 In an embodiment of the present invention, the first device 100 may include a processor 110, a memory 120, a display 130, an external device interface unit 140, a user input unit 150, and a communication unit 160. Hereinafter, each component is described.

[0140] The above reference will be omitted Figure 5 A redundant description of the processor 110 and the memory 120 is provided.

[0141] The processor 110 may control the overall operation of the first device 100 , and may execute one or more instructions stored in the memory 120 to control the operation of the first device 100 .

[0142] For example, the processor 110 may execute a program stored in the memory 120 to control the overall operation of the memory 120, the display 130, the external device interface unit 140, the user input unit 150, the communication unit 160, etc. The processor 110 may include at least one of a RAM, a ROM, a CPU, a GPU, and a bus. The RAM, the ROM, the CPU, the GPU, etc. may be connected to each other through a bus.

[0143] The communication unit 160 may perform communication with a plurality of peripheral devices located around the first device 100 via a wired or wireless communication network. In addition, the communication unit 160 may receive context information for predicting the likelihood of a user performing an operation. The communication unit 160 may include a short-range communication unit for short-range communication and a long-range communication unit (not shown) configured to perform communication with a server for supporting long-range communication according to a long-range communication standard.

[0144] The short-range wireless communication unit may include, but is not limited to, a Bluetooth communication unit, a Bluetooth low energy (BLE) communication unit, a near field communication unit, a wireless local area network (WLAN) (e.g., Wi-Fi) communication unit, a Zigbee communication unit, an infrared data association (IrDA) communication unit, a Wi-Fi Direct (WFD) communication unit, an ultra-wideband (UWB) communication unit, an Ant+ communication unit, an Ethernet communication unit, and the like.

[0145] The communication unit 160 may include a long-distance communication module configured to perform communication through a network for Internet communication. In addition, the communication unit 160 may include a communication module configured to perform communication through a communication network that complies with a mobile communication standard such as the third generation (3G), the fourth generation (4G) and / or the fifth generation (5G). In addition, the communication unit 160 may include at least one port for connecting to a peripheral device via a cable so as to communicate with the external device in a wired manner. Therefore, the communication unit 160 can perform communication with an external device connected to the communication unit 160 in a wired manner through at least one port.

[0146] The external device interface unit 140 may provide an interface environment between the first device 100 and various external devices. The external device interface unit 140 may include an audio / video (A / V) input / output unit. The external device interface unit 140 may be connected to an external device such as a digital versatile disk (DVD) and a Blu-ray player, a gaming device, a camera, a computer, an air conditioner, a laptop, a desktop, a television (TV), or a digital display device in a wired or wireless manner. The external device interface unit 140 may send an image, a video, and an audio signal input by an external device and information about an external device connected to the external device interface unit 140 to the processor 110 of the first device 100.

[0147] The A / V input / output unit may include a universal serial bus (USB) port, a composite video blanking sync (CVBS) port, a component port, a separate video (S-video) port (analog), a digital visual interface (DVI) port, a high-definition multimedia interface (HDMI) port, a display port (DP) port, a Thunderbolt port, a red, green, and blue (RGB) port, a D-SUB port, etc., so that information about the external device can be input to the first device 100.

[0148] Various peripheral devices may be connected to the first device 100 through the external device interface unit 140 .

[0149] The user input unit 150 may refer to an input unit configured to receive a user request from a user. The user input unit 150 may include, but is not limited to, at least one of a keyboard, a dome switch, a touch pad (e.g., a touch-type capacitive touch pad, a pressure-type resistive cover touch pad, an infrared sensor-type touch pad, a surface acoustic wave conduction touch pad, an integrated tension measurement touch pad, a piezoelectric effect touch pad), a roller, or a light push switch. The key may include various types of keys, such as mechanical buttons or wheels formed in various areas such as the front surface, side surface, and rear surface of the main body of the first device 100. The touch panel may detect the user's touch input and output a touch event value corresponding to the detected touch signal. In the case where a touch screen (not shown) is configured by combining a touch panel with a display panel, the touch screen may be implemented with various types of touch sensors (such as capacitive, resistive, or piezoelectric sensors). The first device 100 according to an embodiment of the present disclosure may obtain the user's request through the user input unit 150.

[0150] The display 130 converts the image signal, data signal, on-screen display (OSD) signal, control signal, etc., which have been processed by the processor 110, to generate a driving signal. The display 130 may be implemented as a plasma display panel (PDP), a liquid crystal display (LCD), an organic light emitting diode (OLED), a flexible display, or a three-dimensional (3D) display. In addition, the display 130 may be configured as a touch screen to be used as both an output device and an input device.

[0151] The display 130 may output various contents input through the communication unit 160 or the user input unit 150, or output an image stored in the memory 120. In addition, the display 130 may output information input by the user through the user input unit 150 on the screen.

[0152] The display 130 may include a display panel. The display panel may be a liquid crystal display (LCD) panel or a panel including various light-emitting elements such as a light-emitting diode (LED), an organic LED (OLED), or a cold cathode fluorescent lamp (CCFL). In addition, the display panel may include a curved display device having a screen with curvature, or a flexible display device having an adjustable curvature. The display panel may be a 3D display or an electrophoretic display.

[0153] The output resolution of the display panel may include, for example, high definition (HD), full HD, ultra HD, or a higher resolution than ultra HD.

[0154] in addition, Figure 5 and Figure 6The block diagram of the first device 100 shown in is a block diagram for an embodiment. Each of the components shown in the block diagram can be integrated, added, or omitted according to the specifications of the first device 100 actually implemented. That is, two or more components can be integrated into one component, or one component can be divided into two or more components as needed. In addition, the functions performed by each block are used to describe the embodiment, and its detailed operation or device does not limit the scope of the present disclosure.

[0155] Figure 7 is a flowchart of a method of sending a mobile phone call performed by a first device according to an embodiment of the present disclosure.

[0156] Reference Figure 7 , the first device 100 can generate a public key and a private key for the first device 100 (S710).

[0157] The public key and private key for the first device 100 can be the same as those mentioned above. Figure 2 The public and private keys described are identical.

[0158] When the first device 100 has already generated the public key and the private key, the generation of the public key and the private key (S710) may be omitted.

[0159] The public key may be transmitted to another external mobile phone device or the like via the network 300 .

[0160] According to an embodiment of the present disclosure, a mobile phone device can add a public key entry in its address book and store public keys received from other mobile phone devices together with names, telephone numbers, e-mail addresses, etc. in the address book.

[0161] Figure 8 is a diagram illustrating an example in which a mobile phone device manages an address book according to an embodiment of the present disclosure.

[0162] The first device 100 can be Figure 8 The address book input process shown stores a public key received from another external mobile phone device in the address book.

[0163] The first device 100 may store the public key 810 received from another mobile phone device in an address book together with a name, a phone number, an email address, and the like.

[0164] exist Figure 8 In the embodiment of , the received public key 810 may be “abc1234@svmc.” The format, length, and configuration of the public key are not limited to “abc1234@svmc” and may be defined in various ways.

[0165] In an embodiment, when a call is received for the first time from a mobile phone number in which only the phone number is stored in the address book and no public key is stored in the address book, the first device 100 can update the address book with the received public key after the user completes the call from the phone number.

[0166] In an embodiment, before updating the address book, the first device 100 may receive a confirmation from the user as to whether to update the address book.

[0167] In an embodiment, when a call is received for the first time from a mobile phone number in which only the phone number is stored in the address book and no public key is stored in the address book, the first device 100 may automatically update the address book with the received public key.

[0168] In an embodiment, the first device 100 can be set to update the address book using the received public key automatically or after receiving confirmation from the user about whether to update the address book when a call is received for the first time from a mobile phone number in which only the phone number is stored in the address book and no public key is stored in the address book.

[0169] The first device 100 may select a phone number of a SIM card to be used to send a mobile phone call to the second device 200 from among a plurality of SIM cards used by the first device 100 (S720).

[0170] Multiple SIM cards used by the first device 100 may use the same public key but different mobile phone numbers. Therefore, the second device 200 may use the same public key to detect different mobile phone numbers as the mobile phone number of the same user.

[0171] The first device 100 may generate caller data by hashing the selected phone number (S730).

[0172] The first device 100 may generate a caller representative code by encrypting the caller data using a private key (S740).

[0173] exist Fig. 9 Detailed description is given in FIG. 5 , in which the first device 100 generates caller data by hashing a selected phone number and generates a caller representative code by encrypting the caller data using a private key.

[0174] Fig. 9 is a diagram illustrating an example in which a first device generates a caller representative code according to an embodiment of the present disclosure.

[0175] The first device 100 can generate caller data by hashing the phone number selected for sending the mobile phone call. The hashing can be performed in a secure area of ​​the first device 100.

[0176] In this specification, a secure area may refer to an area in a main processor that is not accessible to other applications. For example, a secure area may include a trusted execution environment (TEE).

[0177] In the present disclosure, a trusted execution environment may refer to an area in a main processor, where codes and data loaded into the area are guaranteed to be confidentiality-protected.

[0178] In an embodiment, the hash function and data used in the hashing process may be stored in a secure memory in a secure area.

[0179] In an embodiment, the private key and hash function may be stored in a secure area.

[0180] exist Fig. 9 In an embodiment of the present invention, the telephone number of the first device 100 can be loaded into the secure area through an application programming interface (API).

[0181] The first device 100 may generate caller data by hashing a phone number loaded into the secure area using a hash function stored in the secure area.

[0182] The first device 100 may generate a caller representative code by encrypting the generated caller data using a private key stored in a secure area.

[0183] The first device 100 can send the generated caller representative code outside the secure area through the API.

[0184] When sending a mobile phone call, the first device 100 may send a message including a caller representative code and a public key to the second device 200 (S750).

[0185] The first device 100 may transmit the caller representative code and the public key to the second device 200 via the network 300 .

[0186] Fig.10 is a block diagram illustrating a configuration of a second device according to an embodiment of the present disclosure.

[0187] refer to Fig.10 , the second device 200 may include a processor 210 , a memory 220 , and a display 230 .

[0188] The memory 220 may store programs for processing and control performed by the processor 210. In addition, the memory 220 may store data input to or output from the second device 200.

[0189] The memory 220 may include at least one of an internal memory (not shown) and an external memory (not shown). The memory 220 may store control history information, current environment information, and state information.

[0190] The memory 220 may include at least one of a flash memory type storage medium, a hard disk type storage medium, a multimedia card micro storage medium, a card type memory (e.g., an SD or XD memory), a RAM, a SRAM, a ROM, an EEPROM, a PROM, a magnetic memory, a magnetic disk, and an optical disk.

[0191] The internal memory may include, for example, at least one of a volatile memory (e.g., DRAM, SRAM, SDRAM, etc.), a nonvolatile memory (e.g., OTPROM, PROM, EPROM, EEPROM, mask ROM, flash ROM, etc.), a HDD, or a SSD.

[0192] According to an embodiment, the processor 210 may load a command or data received from at least one of the non-volatile memory or other components into the volatile memory and process the command or data. In addition, the processor 210 may store data received from other components or generated by the processor 210 in the non-volatile memory.

[0193] The external memory may include, for example, at least one of CF, SD, micro SD, mini SD, xD, or memory stick.

[0194] The memory 220 may store one or more instructions executable by the processor 210 .

[0195] In an embodiment, the memory 220 may store various types of information input through an input / output unit (not shown).

[0196] In an embodiment, the memory 220 may store instructions for controlling the processor to perform the following operations: when the received public key exists in the address book of the second device 200, obtain caller data by decrypting the received caller representative code using the public key, hash the incoming telephone number, and identify the sender of the mobile phone call by comparing the obtained caller data with the hashed incoming telephone number.

[0197] When a user input is received or a preset and stored condition is satisfied, the processor 210 may execute the OS and various applications stored in the memory 220 .

[0198] The processor 210 may include a RAM and a ROM, wherein the RAM is used to store signals or data input from outside the second device 200 or to be used as a storage area for various operations performed by the second device 200 , and the ROM is used to store multiple instructions and / or control programs for controlling the second device 200 .

[0199] The processor 210 may include a single core, a dual core, a triple core, a quad core, or a core corresponding to a multiple thereof. In addition, the processor 210 may include a plurality of processors. For example, the processor 210 may be implemented as a main processor (not shown) and a sub-processor (not shown) operating in a sleep mode.

[0200] In addition, the processor 210 may include at least one of a CPU, a GPU, and a VPU. Alternatively, according to an embodiment, the processor 210 may be implemented as a SoC in which at least one of a CPU, a GPU, and a VPU is integrated.

[0201] The processor 210 may execute one or more instructions stored in the memory 220 to control various components of the second device 200 .

[0202] In an embodiment, when the received public key exists in the address book of the second device 200, the processor 210 may obtain the caller data by decrypting the received caller representative code using the public key. In an embodiment, the processor 210 may hash the incoming phone number. In an embodiment, the processor 210 may identify the sender of the mobile phone call by comparing the hashed incoming phone number with the obtained caller data. In an embodiment, the processor 210 may determine whether the incoming phone number exists in the address book of the second device 200.

[0203] In an embodiment, when the incoming phone number does not exist in the address book of the second device 200 and the hashed incoming phone number matches the obtained caller data, the processor 210 can identify the user corresponding to the public key stored in the address book of the second device 200 as the sender of the mobile phone call and display the identified sender.

[0204] In an embodiment, the processor 210 may update the address book of the second device 200 by adding the incoming phone number as the phone number of the user corresponding to the public key stored in the address book of the second device 200 .

[0205] In an embodiment, when an incoming telephone number, a public key, and a caller representative code are received, the processor 210 may send the public key of the second device 200 to the first device 100, so that the first device can compare the received public key of the second device 200 with the public key of the second device 200 stored in the address book of the first device 100.

[0206] In an embodiment, in response to receiving an incoming telephone number, a public key, and a caller representative code, when the incoming telephone number exists in the address book of the second device 200, the processor 210 can identify the user corresponding to the incoming telephone number stored in the address book of the second device 200 as the sender of the mobile phone call.

[0207] In an embodiment, when the incoming phone number exists in the address book of the second device 200 and the public key does not exist in the address book of the second device 200, the processor 210 may display a notification message.

[0208] In an embodiment, when an incoming phone number exists in the address book of the second device 200 and the public key does not exist in the address book of the second device 200, the processor 210 may not identify the user corresponding to the incoming phone number stored in the address book of the second device 200 as the sender of the mobile phone call, and may display the incoming phone number as the caller.

[0209] In an embodiment, when the incoming phone number does not exist in the address book of the second device 200 and the public key exists in the address book of the second device 200, the processor 210 may generate a new message box for a message from the identified caller. This will be referred to below. Fig.15 etc. for detailed description.

[0210] The second device 200 may further include Figure 6 The components of the first device 100 shown in FIG.

[0211] in addition, Fig.10 The block diagram of the second device 200 shown in is a block diagram for an embodiment. Each of the components shown in the block diagram can be integrated, added, or omitted according to the specifications of the second device 200 actually implemented. That is, two or more components can be integrated into one component, or one component can be divided into two or more components as needed. In addition, the functions performed by each block are used to describe the embodiment, and its detailed operation or device does not limit the scope of the present disclosure.

[0212] Fig.11 is a flowchart of a method of receiving a mobile phone call performed by a second device according to an embodiment of the present disclosure.

[0213] Reference Fig.11 , the second device 200 can receive the incoming phone number, the public key, and the caller representative code (S1110).

[0214] The second device 200 may receive the public key and the caller representative code from the first device 100 via the network 300. The second device 200 may receive an incoming phone number from the network 300.

[0215] The second device 200 may determine whether the incoming phone number exists in the address book of the second device 200 (S1120).

[0216] When the incoming phone number does not exist in the address book of the second device 200, the second device 200 may determine whether the public key exists in the address book of the second device 200 (S1130).

[0217] When the public key exists in the address book of the second device 200, the second device 200 can obtain the caller data by decrypting the received caller representative code using the public key (S1140). Here, the caller data can be the same as the address book of the second device 200. Figure 3 Operation S310 or Figure 7 The caller data generated by the first device 100 in operation S730 is the same.

[0218] The second device 200 may hash the incoming phone number (S1150). The second device 200 may hash the incoming phone number by using the same hash function and hash process as those used by the first device 100. The incoming phone number may be received from the network 300.

[0219] exist Fig.11 In the embodiment of FIG. 1 , operation S1140 is shown to be performed before operation S1150, but operations S1140 and S1150 may be performed in another order or may be performed simultaneously.

[0220] The second device 200 may determine whether the hashed incoming phone number matches the obtained caller data (S1160).

[0221] The second device 200 may compare the incoming phone number hashed in operation S1150 with the caller data obtained in operation S1140.

[0222] When the hashed incoming phone number and the obtained caller data match each other, the second device 200 may display the user corresponding to the public key (S1170). When the hashed incoming phone number and the obtained caller data match each other, the second device 200 may identify the user corresponding to the received public key found in the address book of the second device 200 as the other party of the mobile phone call (i.e., the caller), and display the identified user on the display 230 of the second device 200.

[0223] The second device 200 may update the address book of the second device 200 (S1180).

[0224] In an embodiment, the second device 200 can add the incoming phone number to the address book as the phone number of the user who received the public code. This will be referred to below Fig.12a , Figure 12b , Fig.12c etc. for detailed description.

[0225] When the hashed incoming phone number and the obtained caller data do not match each other, the second device 200 may display the incoming phone number (S1190). When the hashed incoming phone number and the obtained caller data do not match each other, the second device 200 may determine that a hacker's phone number exchange or the like may have occurred. Therefore, when the hashed incoming phone number and the obtained caller data do not match each other, the second device 200 may display the incoming phone number as it is on the display 230 without determining the user corresponding to the received public key found in the address book of the second device 200 as the other party of the mobile phone call. When the sender of a call or text message suspected of being a scam is displayed as an acquaintance, the user may become careless and be at risk. Through the above-mentioned processing, when the hashed incoming phone number and the obtained caller data do not match each other, the second device 200 may warn the user by displaying the call as if it comes from an unknown person rather than an acquaintance.

[0226] When the public key does not exist in the address book of the second device 200, the second device 200 may display the incoming phone number (S1190). When both the received incoming phone number and the received public key do not exist in the address book of the second device 200, the second device 200 cannot identify the other party of the mobile phone call, and thus may display the incoming phone number as it is.

[0227] exist Fig.11 In an embodiment, when the incoming phone number exists in the address book of the second device 200, the second device 200 may display the user corresponding to the incoming phone number stored in the address book as the other party of the incoming mobile phone call (S1195).

[0228] Fig.12a is a diagram illustrating an example in which a second device generates an entry in an address book according to an embodiment of the present disclosure.

[0229] like Fig.12a As shown, the second device 200 may generate an entry for the new user in the address book. The process of generating an entry in the address book may include the process of inputting the public key "abc1234@svmc". In an embodiment, the process may be performed by a user input for indicating the generation of the address book. Fig.12a Generation of entries in the address book shown in .

[0230] In an embodiment, the second device 200 may generate an entry for the new user in the address book, such as Fig.12a As shown. This process of generating an entry in the address book may necessarily include a process of inputting the public key "abc1234@svmc". In an embodiment, the second device 200 may manage the public key as a necessary input value.

[0231] In an embodiment, when an entry is created in the address book, the value received for the phone number may be automatically entered as the public key in conjunction with the incoming phone number.

[0232] In an embodiment, the public key may be manually entered by receiving user input.

[0233] In an embodiment, the second device 200 may periodically check the address book to automatically update contacts for which no public key is stored with the public key.

[0234] In an embodiment, when the second device 200 detects that the public key of a particular user has changed, the second device 200 may automatically update the address book with the new public key.

[0235] Figure 12b is a diagram illustrating an example in which a second device updates an address book according to an embodiment of the present disclosure.

[0236] In an embodiment, the second device 200 may detect that there are two entries with the same public key in the address book.

[0237] In an embodiment, the second device 200 may detect that there are two entries having the same public key and different phone numbers.

[0238] exist Figure 12b In the embodiment, the second device 200 can detect that there are two contact entries with "abc1234@svmc" as the public key, namely, the contact entry 1210 of "user A" and the contact entry 1220 of "Abro".

[0239] In an embodiment, the second device 200 may update the contact entries of user A and A's brother by merging the contact entries of user A and A's brother into one contact entry 1230 of "user AA's brother." The merged contact entry 1230 of "user AA's brother" may include all two different phone numbers.

[0240] In an embodiment, the second device 200 may determine the user corresponding to the merged contact entry as "User A" or "A's brother".

[0241] In an embodiment, the second device 200 may periodically and automatically perform the above-mentioned address book update operation.

[0242] In an embodiment, the second device 200 may manually perform the address book update operation by obtaining an instruction from a user.

[0243] Fig.12c is a diagram illustrating an example of an address book managed by a second device according to an embodiment of the present disclosure.

[0244] In an embodiment, when the public key received along with the received mobile phone call exists in the address book, the second device 200 can automatically update the existing address book with the same public key as the received mobile phone call with the new incoming phone number.

[0245] In an embodiment, as in Figure 12b In the embodiment of the present invention, when two contact entries that have been separately input by the user include the same public key, the second device 200 may update the address book by merging the two contact entries.

[0246] As in Fig.12c In an embodiment, the address book updated as described above may include a contact entry of "User A", and the contact entry of "User A" includes a first phone number "01012345678", a second phone number "010XXXXXXXX" and a public key "abc1234@svmc".

[0247] Fig.13 is a flowchart of a method of receiving a mobile phone call performed by a second device according to an embodiment of the present disclosure.

[0248] Reference Fig.13 , the second device 200 can receive an incoming phone number, a public key, and a caller representative code (S1310).

[0249] exist Fig.13 In an embodiment, the second device 200 may pair a public key with a user in an address book instead of pairing a phone number with a user.

[0250] The second device 200 may receive the public key and the caller representative code from the first device 100 via the network 300. The second device 200 may receive an incoming phone number from the network 300.

[0251] The second device 200 may determine whether the public key exists in the address book of the second device 200 (S1320). In this embodiment, the second device 200 may only check whether the public key exists in the address book of the second device 200 without checking whether the incoming phone number exists in the address book.

[0252] When the public key exists in the address book of the second device 200, the second device 200 can obtain the caller data by decrypting the received caller representative code using the public key (S1330). Here, the caller data can be the same as the one in the address book of the second device 200. Figure 3 Operation S310 or Figure 7 The caller data generated by the first device 100 in operation S730 is the same.

[0253] The second device 200 may hash the incoming phone number (S1340). The second device 200 may hash the incoming phone number by using the same hash function and hash process as those used by the first device 100. The incoming phone number may be received from the network 300.

[0254] exist Fig.13 In the embodiment of FIG. 1 , operation S1330 is shown to be performed before operation S1340, but operations S1330 and S1340 may be performed in another order or may be performed simultaneously.

[0255] The second device 200 may determine whether the hashed incoming phone number matches the obtained caller data (S1350).

[0256] The second device 200 may compare the incoming phone number hashed in operation S1340 with the caller data obtained in operation S1330.

[0257] When the hashed incoming phone number and the obtained caller data match each other, the second device 200 may display the user corresponding to the public key (S1360). When the hashed incoming phone number and the obtained caller data match each other, the second device 200 may identify the user corresponding to the received public key found in the address book of the second device 200 as the other party of the mobile phone call (i.e., the caller), and display the identified user on the display 230 of the second device 200.

[0258] The second device 200 may update the address book of the second device 200 (S1370).

[0259] In an embodiment, the second device 200 can add the incoming phone number as the phone number of the user of the received public code. Details of these operations can be referred to above. Fig.12a , Figure 12b , Fig.12c The operation is the same as described above.

[0260] When the hashed incoming phone number and the obtained caller data do not match each other, the second device 200 may display the incoming phone number (S1380). When the hashed incoming phone number and the obtained caller data do not match each other, the second device 200 may determine that a hacker's phone number exchange or the like may have occurred. Therefore, when the hashed incoming phone number and the obtained caller data do not match each other, the second device 200 may display the incoming phone number as it is on the display 230 without determining the user corresponding to the received public key found in the address book of the second device 200 as the other party of the mobile phone call. Through this process, the second device 200 can warn the user by notifying that the call is from an unknown person rather than an acquaintance.

[0261] When the public key does not exist in the address book of the second device 200, the second device 200 may display the incoming phone number (S1380). When the received public key does not exist in the address book, the second device 200 may determine that it cannot identify the other party of the mobile phone call, and thus display the incoming phone number as it is.

[0262] Fig.14 is a flowchart of a method of receiving a mobile phone call performed by a second device according to an embodiment of the present disclosure.

[0263] Reference Fig.14 , the second device 200 can receive an incoming phone number, a public key, and a caller representative code (S1410).

[0264] The second device 200 may receive the public key and the caller representative code from the first device 100 via the network 300. The second device 200 may receive an incoming phone number from the network 300.

[0265] The second device 200 may determine whether the public key exists in the address book of the second device 200 (S1420).

[0266] When the public key exists in the address book of the second device 200, the second device 200 can obtain the caller data by decrypting the received caller representative code using the public key (S1430). Here, the caller data can be the same as the one in the address book of the second device 200. Figure 3 Operation S310 or Figure 7 The caller data generated by the first device 100 in operation S730 is the same.

[0267] The second device 200 may hash the incoming phone number (S1440). The second device 200 may hash the incoming phone number by using the same hash function and hash process as those used by the first device 100. The incoming phone number may be received from the network 300.

[0268] exist Fig.14 In the embodiment of FIG. 14 , operation S1430 is shown to be performed before operation S1440, but operations S1430 and S1440 may be performed in another order or may be performed simultaneously.

[0269] The second device 200 may determine whether the hashed incoming phone number matches the obtained caller data (S1450).

[0270] The second device 200 may compare the incoming phone number hashed in operation S1440 with the caller data obtained in operation S1430.

[0271] When the hashed incoming phone number and the obtained caller data match each other, the second device 200 may display the user corresponding to the public key (S1460). When the hashed incoming phone number and the obtained caller data match each other, the second device 200 may identify the user corresponding to the received public key found in the address book of the second device 200 as the other party of the mobile phone call (i.e., the caller), and display the identified user on the display 230.

[0272] The second device 200 may update the address book of the second device 200 (S1470).

[0273] In an embodiment, the second device 200 can add the incoming phone number as the phone number of the user of the received public code. Details of these operations can be referred to above. Fig.12a , Figure 12b , Fig.12c The operation is the same as described above.

[0274] When the hashed incoming phone number and the obtained caller data do not match each other, the second device 200 may display the incoming phone number (S1495). When the hashed incoming phone number and the obtained caller data do not match each other, the second device 200 may determine that a hacker's phone number exchange or the like may have occurred. Therefore, when the hashed incoming phone number and the obtained caller data do not match each other, the second device 200 may display the incoming phone number as it is on the display 230 without determining the user corresponding to the received public key found in the address book of the second device 200 as the other party of the mobile phone call. Through this process, the second device 200 can warn the user by notifying that the call is from an unknown person rather than an acquaintance.

[0275] When the public key does not exist in the address book of the second device 200, the second device 200 may determine whether the incoming phone number exists in the address book of the second device 200 (S1480).

[0276] When the incoming phone number does not exist in the address book of the second device 200, the second device 200 may display the incoming phone number (S1495). When both the received incoming phone number and the received public key do not exist in the address book of the second device 200, the second device 200 cannot identify the other party of the mobile phone call, and thus may display the incoming phone number as it is.

[0277] When the public key does not exist in the address book of the second device 200 and the incoming phone number exists in the address book of the second device 200, the second device 200 may display a notification message (S1490).

[0278] The situation where the public key does not exist in the address book of the second device 200 and the incoming phone number exists in the address book of the second device 200 may include: the situation where the public key of the first device 100 that has sent the mobile phone call has been modified, or the situation where a hacker has exchanged the first device 100 with the hacker's SIM code to impersonate the user of the first device 100.

[0279] Therefore, when the incoming phone number exists in the address book of the second device 200 but the public key does not exist in the address book of the second device 200, the second device (200) may display a notification message for notifying the user of the second device 200 of the risk. The notification message may be in various forms such as a pop-up message.

[0280] Fig.15 is a flowchart of a method for receiving a mobile phone message performed by a second device according to an embodiment of the present disclosure.

[0281] Reference Fig.15 , the second device 200 can receive an incoming phone number, a public key, and a caller representative code (S1510).

[0282] The second device 200 may receive the public key and the caller representative code from the first device 100 via the network 300. The second device 200 may receive an incoming phone number from the network 300.

[0283] The second device 200 may determine whether the incoming phone number exists in the address book of the second device 200 (S1520).

[0284] When the incoming phone number does not exist in the address book of the second device 200, the second device 200 may determine whether the public key exists in the address book of the second device 200 (S1530).

[0285] When the public key exists in the address book of the second device 200, the second device 200 can obtain the caller data by decrypting the received caller representative code using the public key (S1540). Here, the caller data can be the same as the one in the address book of the second device 200. Figure 3 Operation S310 or Figure 7 The caller data generated by the first device 100 in operation S730 is the same.

[0286] The second device 200 may hash the incoming phone number (S1550). The second device 200 may hash the incoming phone number by using the same hash function and hash process as those used by the first device 100. The incoming phone number may be received from the network 300.

[0287] exist Fig.15 In the embodiment of FIG. 5 , operation S1540 is shown to be performed before operation S1550, but operations S1540 and S1550 may be performed in another order or may be performed simultaneously.

[0288] The second device 200 may determine whether the hashed incoming phone number matches the obtained caller data (S1560).

[0289] The second device 200 may compare the incoming phone number hashed in operation S1550 with the caller data obtained in operation S1540.

[0290] When the hashed incoming phone number and the obtained caller data match each other, the second device 200 may generate a new message box for the user corresponding to the public key and store the message (S1570). When the hashed incoming phone number and the obtained caller data match each other, the second device 200 may identify the user corresponding to the received public key found in the address book of the second device 200 as the other party of the mobile phone message, i.e., the sender. However, if the message is received from the same user but using a different phone number, the second device 200 may generate a new message box and store the message therein.

[0291] In an embodiment, when the hashed incoming phone number and the obtained caller data match each other, the second device 200 may store the message in an existing message box of the user corresponding to the public key.

[0292] When the hashed incoming phone number and the obtained caller data do not match each other, the second device 200 may store a message in a message box for the incoming phone number (S1580).

[0293] When the hashed incoming phone number and the obtained caller data do not match each other, the second device 200 may determine that a hacker's phone number exchange or the like may have occurred. Therefore, when the hashed incoming phone number and the obtained caller data do not match each other, the second device 200 may not determine the user corresponding to the received public key found in the address book of the second device 200 as the sender of the mobile phone message. In this case, the second device 200 may generate a new message box for the incoming phone number and store the message in the generated message box (S1580). When a message box for the incoming phone number already exists, the second device 200 may store the message in the existing message box for the incoming phone number.

[0294] Through this process, when the hashed incoming phone number and the obtained caller data do not match each other, the second device 200 can notify the user of the possibility that the message is dangerous by displaying that the message is not from the user registered in the address book.

[0295] When the public key does not exist in the address book of the second device 200, the second device 200 may store the message in a message box for the incoming phone number (S1580). When both the received incoming phone number and the received public key do not exist in the address book of the second device 200, the second device 200 cannot identify the sender of the mobile phone message, and thus may generate a message box for the incoming phone number and store the message in the generated message box. When a message box for the incoming phone number already exists, the second device 200 may store the message in an existing message box for the incoming phone number.

[0296] Even in this case, the second device 200 can notify the user of the possibility of the message danger by displaying the message via a message box of the incoming phone number.

[0297] When the incoming phone number exists in the address book of the second device 200, the second device 200 may add a message to a message box for a user corresponding to the incoming phone number (S1590).

[0298] When the incoming phone number exists in the address book of the second device 200, the second device 200 can determine the user corresponding to the incoming phone number stored in the address book as the other party of the incoming mobile phone call, and generate a message box for the user corresponding to the incoming phone number to store the message, or add the message to the existing message box of the user corresponding to the incoming phone number to store the message.

[0299] Fig.16 is a flow chart of a method of sending and receiving a mobile phone call according to an embodiment of the present disclosure.

[0300] refer to Fig.16 , the first device 100 may send a mobile phone call to the second device 200 (S1610). The first device 100 may select any one of a plurality of SIM cards used by the first device and send a mobile phone call to the second device 200 by using a phone number corresponding to the selected SIM card.

[0301] The second device 200 may respond by sending a message including the public key of the second device 200 to the first device 100 (S1620).

[0302] In an embodiment, the second device 200 that has received a mobile phone call from the first device 100 may send a public key of the second device 200 or a message including the public key of the second device 200 to the first device 100 in response to receiving the mobile phone call.

[0303] In an embodiment, the second device 200 may pre-respond to a mobile phone call from the first device 100 by sending a public key of the second device 200 to the first device 100 via the network 300. This pre-response may be performed automatically regardless of the user of the second device 200.

[0304] The first device 100 may determine whether the public key of the second device 200 exists in the address book of the first device 100 (S1630).

[0305] In an embodiment, the first device 100 may receive the public key of the second device 200 via a message from the second device 200 .

[0306] In an embodiment, the first device 100 may receive the public key of the second device 200 from the second device 200 via the network 300 .

[0307] The first device 100 may determine whether the received public key of the second device 200 exists in the address book of the first device 100 .

[0308] When the received public key does not exist in the address book of the first device 100, the first device 100 may display a notification message to the user (S1640).

[0309] In an embodiment, when the received public key does not exist in the address book of the first device 100, it may mean that the second device 200 has been used by someone else. For example, the user of the second device 200 may no longer use the corresponding SIM card and phone number, and a third party may use the SIM card and phone number. Therefore, when the received public key does not exist in the address book of the first device 100, the first device 100 may display a notification message on the display that the user of the second device 200 may have changed. The notification message may be in various forms such as a pop-up message.

[0310] The first device 100 may determine whether to continue the call (S1650).

[0311] In an embodiment, the first device 100 may determine whether to continue the call by receiving a user input regarding whether to continue the call.

[0312] In an embodiment, by default, the first device 100 may be set to display a notification message that the user of the second device 200 may have changed, and continue the phone call. In this case, operation S1650 may be omitted.

[0313] When the first device 100 determines not to continue the call, the first device 100 may cancel the call (S1660).

[0314] In an embodiment, upon receiving a user input for interrupting a call, the first device 100 may determine not to continue the call, and cancel the call.

[0315] In an embodiment, the first device 100 may be set to automatically cancel the call because the user of the second device 200 may have changed. In this case, operation S1650 may be omitted.

[0316] When the first device (100) determines to continue the call, the first device (100) may continue the call (S1670).

[0317] In an embodiment, upon receiving a user input for continuing the call, the first device 100 may continue the call.

[0318] When the received public key exists in the address book of the first device 100, the first device 100 can continue the call (S1670). When the received public key exists in the address book of the first device 100, the user of the second device 200 has not changed, and therefore, the first device 100 can continue the call.

[0319] The method for sending and receiving a mobile phone call according to an embodiment can be implemented as a computer-readable recording medium including computer executable instructions such as a computer executable program module. Computer-readable media can be any available media that can be accessed by a computer, and can include volatile or non-volatile media and removable or non-removable media. Computer-readable media can include program instructions, data files, data structures, etc., alone or in combination. The program instructions to be recorded on the medium can be specially designed and configured for the present disclosure, or can be known to and can be used by technicians in the field of computer software. Examples of computer-readable recording media include magnetic media (such as hard disks, floppy disks, or tapes), optical media (such as optical disks ROM (CD-ROM) or DVDs), magneto-optical media (such as floppy disks), and hardware devices (such as ROM, RAM, or flash memory), which are specially configured to store and execute program commands. Examples of program commands can include not only machine codes, such as codes made by compilers, but also high-level language codes that can be executed by computers using interpreters, etc.

[0320] The above description is provided for illustrative purposes only, and those skilled in the art will appreciate that the present disclosure can be easily modified to other detailed configurations without modifying the technical aspects and essential features of the present disclosure. Therefore, it should be understood that the above embodiments are exemplary in all respects and are not restrictive. For example, each element described in a single type can be executed in a distributed manner, and the elements described in a distributed manner can also be executed in an integrated form.

[0321] According to an embodiment, a method for sending and receiving mobile phone calls may include: generating a public key and a private key by a first device, and generating caller data by hashing a telephone number from which the mobile phone call will be sent, generating a caller representative code by the first device by encrypting the caller data using the private key, sending the caller representative code and the public key by the first device to a second device when sending the mobile phone call, obtaining the caller data by the second device by decrypting the received caller representative code using the public key based on the presence of the received public key in an address book of the second device, hashing the incoming telephone number by the second device, and identifying the sender of the mobile phone call by the second device by comparing the hashed incoming telephone number with the obtained caller data.

[0322] According to an embodiment, the phone number from which the mobile phone call is to be sent may be a phone number corresponding to a SIM card selected from a plurality of SIM cards used by the first device.

[0323] According to an embodiment, the method of sending and receiving a mobile phone call may further include determining whether the incoming phone number exists in an address book of the second device.

[0324] According to an embodiment, a method for sending and receiving a mobile phone call may include: in response to receiving an incoming phone number, a public key, and a caller representative code, based on the presence of the incoming phone number in an address book of a second device, the second device identifies, by the second device, a user corresponding to the incoming phone number stored in the address book of the second device as the sender of the mobile phone call.

[0325] According to an embodiment, the method of sending and receiving a mobile phone call may include displaying a notification message based on the presence of an incoming phone number in an address book of a second device and the absence of a public key in the address book of the second device.

[0326] According to an embodiment, a method for sending and receiving a mobile phone call may include: based on the presence of the incoming phone number in the address book of the second device and the absence of a public key in the address book of the second device, displaying the incoming phone number as the sender, without identifying the user corresponding to the incoming phone number stored in the address book of the second device as the sender of the mobile phone call.

[0327] According to an embodiment, a method for sending and receiving a mobile phone call may include: based on the fact that the incoming phone number does not exist in the address book of the second device, and the hashed incoming phone number and the obtained caller data match each other, identifying a user corresponding to a public key stored in the address book of the second device as the sender of the mobile phone call, and displaying the identified sender.

[0328] According to an embodiment, the method of sending and receiving a mobile phone call may include updating an address book of the second device by adding an incoming phone number as a phone number of a user corresponding to a public key in an address book stored in the second device.

[0329] According to an embodiment, the method of sending and receiving a mobile phone call may include generating a new message box for a message from an identified caller based on an incoming phone number not existing in an address book of the second device and a public key existing in the address book of the second device.

[0330] According to an embodiment, a method for sending and receiving a mobile phone call may include: based on receiving an incoming telephone number, a public key, and a caller representative code, a second device sending a public key of the second device to a first device, and based on the received public key not matching the public key of the second device stored in an address book of the first device, a notification by the first device indicating the possibility that the telephone number of the second device has been changed.

[0331] According to an embodiment, a system for sending and receiving mobile phone calls may include: a first device, configured to generate a public key and a private key, generate caller data by hashing a telephone number from which the mobile phone call will be sent, generate a caller representative code by encrypting the caller data using the private key, and send the caller representative code and the public key to a second device when the mobile phone call is sent; and a second device, configured to obtain caller data based on the presence of a received public key in an address book, by decrypting the received caller representative code using the public key, hash the incoming telephone number, and identify the sender of the mobile phone call by comparing the hashed incoming telephone number with the obtained caller data.

[0332] According to an embodiment, the phone number from which the mobile phone call is to be sent may be a phone number corresponding to a SIM card selected from a plurality of SIM cards used by the first device.

[0333] According to an embodiment, the second device may determine whether the incoming phone number exists in an address book of the second device.

[0334] According to an embodiment, based on the fact that the incoming phone number does not exist in the address book of the second device and the hashed incoming phone number and the obtained caller data match each other, the second device can identify the user corresponding to the public key stored in the address book of the second device as the sender of the mobile phone call and display the identified sender.

[0335] According to an embodiment, based on the presence of the incoming phone number in the address book of the second device and the absence of the public key in the address book of the second device, the second device may display a notification message.

[0336] According to an embodiment, based on the presence of the incoming phone number in the address book of the second device and the absence of the public key in the address book of the second device, the second device can display the incoming phone number as the sender without identifying the user corresponding to the incoming phone number stored in the address book of the second device as the sender of the mobile phone call.

[0337] According to an embodiment, based on the fact that the incoming phone number does not exist in the address book of the second device and the hashed incoming phone number and the obtained caller data match each other, the second device can identify the user corresponding to the public key stored in the address book of the second device as the sender of the mobile phone call and display the identified sender.

[0338] According to an embodiment, the second device may update the address book of the second device by adding the incoming phone number as the phone number of the user corresponding to the public key stored in the address book of the second device.

[0339] According to an embodiment, based on the incoming phone number not existing in the address book of the second device and the public key existing in the address book of the second device, the second device may generate a new message box for the message from the identified sender.

[0340] According to an embodiment, based on receiving the incoming telephone number, public key, and caller representative code, the second device can send the public key of the second device to the first device, and based on the fact that the received public key of the second device does not match the public key of the second device stored in the address book of the first device, the first device can display a notification of the possibility that the telephone number of the second device has been changed.

Claims

1. A method for sending and receiving mobile phone calls, the method comprising: generating a public key and a private key by the first device (100) and generating caller data by hashing a telephone number from which the mobile phone call is to be sent; generating, by the first device (100), a caller representative code by encrypting the caller data using the private key; When sending the mobile phone call, the first device (100) sends the caller representative code and the public key to the second device (200); Based on the received public key existing in the address book of the second device (200), the second device (200) obtains the caller data by decrypting the received caller representative code using the public key; hashing the incoming telephone number by the second device (200); as well as The sender of the mobile phone call is identified by a second device (200) by comparing the hashed incoming telephone number with the obtained caller data.

2. The method according to claim 1, wherein: The telephone number from which the mobile phone call is to be sent is a telephone number corresponding to a Subscriber Identity Module (SIM) card selected from a plurality of SIM cards used by the first device (100).

3. The method according to any one of claims 1 to 2, further comprising: The second device (200) determines whether the incoming phone number exists in the address book of the second device (200).

4. The method according to any one of claims 1 to 3, further comprising: In response to receiving the incoming telephone number, the public key and the caller representative code, based on the presence of the incoming telephone number in the address book of the second device (200), the second device (200) identifies the user corresponding to the incoming telephone number stored in the address book of the second device (200) as the sender of the mobile phone call.

5. The method according to any one of claims 1 to 4, further comprising: Based on the presence of the incoming phone number in the address book of the second device (200) and the absence of the public key in the address book of the second device (200), a notification message is displayed by the second device (200).

6. The method according to any one of claims 1 to 3, further comprising: Based on the presence of the incoming telephone number in the address book of the second device (200) and the absence of the public key in the address book of the second device (200), the second device (200) displays the incoming telephone number as the sender without identifying the user corresponding to the incoming telephone number stored in the address book of the second device (200) as the sender of the mobile phone call.

7. The method according to any one of claims 1 to 3, further comprising: Based on the fact that the incoming telephone number does not exist in the address book of the second device (200) and that the hashed incoming telephone number and the obtained caller data match each other, the second device (200) identifies the user corresponding to the public key stored in the address book of the second device (200) as the sender of the mobile phone call, and displays the identified sender.

8. The method according to claim 7, further comprising: The address book of the second device (200) is updated by the second device (200) by adding the incoming phone number as the phone number of the user corresponding to the public key stored in the address book of the second device (200).

9. The method according to any one of claims 1 to 3, further comprising: Based on the fact that the incoming phone number does not exist in the address book of the second device (200) and the public key exists in the address book of the second device (200), a new message box is generated by the second device (200) for the message from the identified sender.

10. The method according to any one of claims 1 to 9, further comprising: The second device (200) sends the public key of the second device (200) to the first device (100) based on receiving the incoming phone number, the public key and the caller representative code; and A notification is displayed by the first device (100) of the possibility that the telephone number of the second device (200) has been changed based on the received public key not matching the public key of the second device (200) stored in the address book of the first device (100).

11. A system for sending and receiving mobile phone calls, the system comprising: a first device (100) configured to generate a public key and a private key, generate caller data by hashing a telephone number from which the mobile phone call is to be sent, generate a caller representative code by encrypting the caller data using the private key, and send the caller representative code and the public key to a second device (200) when sending the mobile phone call; as well as The second device (200) is configured to obtain the caller data by decrypting the received caller representative code using the public key based on the received public key being present in the address book of the second device (200), hashing the incoming telephone number, and identifying the sender of the mobile phone call by comparing the hashed incoming telephone number with the obtained caller data.

12. The system of claim 11, wherein: The telephone number from which the mobile phone call is to be sent is a telephone number corresponding to a Subscriber Identity Module (SIM) card selected from a plurality of SIM cards used by the first device (100).

13. The system of any one of claims 11 to 12, wherein: The second device (200) is also configured to determine whether the incoming phone number exists in the address book of the second device (200).

14. The system of any one of claims 11 to 13, wherein: The second device (200) is also configured to: based on the fact that the incoming telephone number does not exist in the address book of the second device (200) and the hashed incoming telephone number and the obtained caller data match each other, identify the user corresponding to the public key stored in the address book of the second device (200) as the sender of the mobile phone call, and display the identified sender.

15. The system of any one of claims 11 to 14, wherein: The second device (200) is further configured to send the public key of the second device (200) to the first device (100) based on receiving the incoming phone number, the public key and the caller representative code, and The first device (100) is also configured to display a notification of the possibility that the telephone number of the second device (200) has been changed based on the received public key of the second device (200) not matching the public key of the second device (200) stored in the address book of the first device (100).

Images