KR101513472B1 - Apparatus for confirming buddy based on telephone number and method thereof - Google Patents

Abstract

A method for confirming whether a current user of another phone number is a friend by a device includes receiving a message including user information of the other phone number from a server, Confirming whether the first user is a friend of the first user using the telephone number, and transmitting the result of the confirmation to the server.

Description

[0001] APPARATUS FOR CONFIRMING BUDDY BASED ON TELEPHONE NUMBER AND METHOD THEREOF [0002]

The present invention relates to an apparatus and method for identifying a friend based on a telephone number, and more particularly, a friend confirmation apparatus can confirm whether a user using a specific telephone number as a friend in an application is an actual friend.

With the development of information and communication technology, a variety of IMS (Instant Message Service) programs that can send and receive messages between users have emerged. The role of the IMS program is not limited to sending and receiving messages between users, but also enables transfer of data such as files, presenting exchangeable products at convenience stores, and the like.

The above-mentioned roles can be performed through a dialog window with a friend in the IMS program, and the IMS program accesses the phone book of the user device and stores the users corresponding to the phone number stored by the user device as friends in the IMS program Can be stored.

However, the friend list of the user stored in the IMS server depends only on the phone book storage history of the user device regardless of the actual state of the other party. For example, the other party stored as A in the phone book of the user device can recognize only the A based on the phone book storage history of the user device, even though the actual user of the phone number on the phone book corresponding to A is B do.
In this regard, Korean Patent Laid-Open Publication No. 10-2011-0054137 (titled "Method and terminal for managing telephone number") discloses a technique for allowing a user to easily store and manage a changed telephone number of another specific user .

A friend confirmation device and method for checking whether a user who uses a specific phone number as a friend on a specific application service is an actual friend. Here, the friend on the specific application service may mean the other party whose phone number is registered in the phone book of the user device, and the other party in which the corresponding phone number is stored in the specific application service server. It is to be understood, however, that the technical scope of the present invention is not limited to the above-described technical problems, and other technical problems may exist.

According to an aspect of the present invention, there is provided a method for confirming whether a current user of a different telephone number is a friend by using a device according to the first aspect of the present invention, From the server, determining whether the current user is a friend of a first user using the phone number of the device based on the user information, and transmitting the result of the confirmation to the server .

Meanwhile, a method for confirming whether a current user of another phone number is a friend by a device according to the second aspect of the present invention transmits a request message including user information of the other phone number and the other phone number to a server And receiving a response message from the server, wherein the response message includes a result of whether the user information is the same as the current user information of the other telephone number, and based on the result, And checking whether the current user is a friend of the first user using the phone number of the device.

On the other hand, a method for confirming whether a second user of a second telephone number is a friend of a first user of a first telephone number, by a server according to the third aspect of the present invention, Receiving a request message from the device, verifying whether the user information of the second telephone number is changed, transmitting a response message including information indicating that the user of the second user or the user of the second telephone number is changed To the first device; and receiving a response from the first device indicating whether the second user is to be maintained or excluded as a friend of the first user.

On the other hand, a method for confirming whether a second user of a second telephone number is a friend of a first user of a first telephone number by the server according to the fourth aspect of the present invention comprises the steps of: Receiving a request message from a first device, transmitting a response message to the first device, the response message including status information of the user corresponding to the second telephone number, receiving, from the first device, Comparing the user information of the user corresponding to the second telephone number with the user information of the second user stored in the server to determine whether the second user is a friend of the first user , And transmitting the result of the confirmation to the first device.

Meanwhile, a method for confirming whether a second user of a second telephone number is a friend of a first user of a first telephone number by the server according to the fifth aspect of the present invention comprises the steps of: Receiving a request message from the first device, checking whether the user information of the second telephone number is changed, checking whether the second user is a friend of the first user based on a result of the user information change confirmation And transmitting the friend confirmation result to the first device.

A device according to a sixth aspect of the present invention includes a message generation unit for generating a request message including a telephone number of the device, a transmission unit for transmitting the generated request message to a server, And a confirmation processing unit for checking whether the current user of the other phone number is a friend of the first user using the phone number of the device based on the user information, And the transmitting unit transmits the result of the confirmation to the server.

According to a seventh aspect of the present invention, there is provided a server comprising: a receiver for receiving a request message from a first device corresponding to a first telephone number; a first confirmation processor for verifying whether user information of a second telephone number is changed; A second confirmation processing unit for confirming whether the current user of the second telephone number is a friend of the first user who uses the telephone number of the device based on the result of the user information change check of the first confirmation processing unit, And a transmission unit for transmitting the result of the determination to the first device.

The above-described task solution is merely exemplary and should not be construed as limiting the present invention. In addition to the exemplary embodiments described above, there may be additional embodiments described in the drawings and the detailed description of the invention.

According to any one of the above-mentioned means for solving the problems of the present invention, the friend confirmation apparatus and method can determine the friendliness of the friend on the service, thereby making it possible to improve user convenience.

1 is a configuration diagram of a friend confirmation service providing system according to an embodiment of the present invention.
2 is a configuration diagram of the first device shown in FIG. 1 according to an embodiment of the present invention.
3 is a flowchart illustrating a method for confirming a friend relationship between a user of a first device and a user using a second telephone number, according to an embodiment of the present invention.
FIG. 4 is a flowchart illustrating a method for confirming the friend relationship shown in FIG. 3, according to an embodiment of the present invention.
5 is a diagram illustrating a UI displayed for confirming a friend relationship with a display device of a first device according to an embodiment of the present invention.
6 is a flowchart illustrating a method of confirming a friend relationship between a user of a first device and a user using a second telephone number according to another exemplary embodiment of the present invention.
7 is a flowchart illustrating a method for confirming a friend relationship between a user of a first device and a user using a second telephone number according to another embodiment of the present invention.
FIG. 8 is a configuration diagram of the server shown in FIG. 1, according to an embodiment of the present invention.
9 is a flowchart illustrating a method of confirming a friend relationship between a user of a first device and a user using a second phone number according to another embodiment of the present invention.
10 is a flowchart illustrating a method of confirming a friend relationship between a user of a first device and a user using a second telephone number according to another embodiment of the present invention.
11 is a flowchart illustrating a method of confirming a friend relationship between a user of a first device and a user using a second phone number according to another embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings, which will be readily apparent to those skilled in the art. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. In order to clearly illustrate the present invention, parts not related to the description are omitted, and similar parts are denoted by like reference characters throughout the specification.

Throughout the specification, when a part is referred to as being "connected" to another part, it includes not only "directly connected" but also "electrically connected" with another part in between . Also, when an element is referred to as "comprising ", it means that it can include other elements as well, without departing from the other elements unless specifically stated otherwise.

In this specification, the term " part " includes a unit realized by hardware, a unit realized by software, and a unit realized by using both. Further, one unit may be implemented using two or more hardware, or two or more units may be implemented by one hardware.

In this specification, some of the operations or functions described as being performed by the terminal or the device may be performed in the server connected to the terminal or the device instead. Similarly, some of the operations or functions described as being performed by the server may also be performed on a terminal or device connected to the server.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings.

1 is a configuration diagram of a friend confirmation service providing system according to an embodiment of the present invention. Referring to FIG. 1, a friend confirmation service providing system may include a server 10, a first device 20, a second device 30, a third device 40, and a network. However, since the friend confirmation service providing system of FIG. 1 is only one embodiment of the present invention, the present invention is not limited to FIG.

The server 10 may be a server of a provider providing a predetermined application service, and may store information about a plurality of users and / or devices using an application service and information (data) related to the application service. In this case, an example of the application service includes an application-based instant message service (IMS), a voice / video call service, and a group type community service. In addition, the server 10 is an example of a friend confirmation device.

The first telephone number to be described below is the telephone number of the first device 20 and the second telephone number is the telephone number of the second device 30 in the past but is currently the telephone number of the third device 40 have. That is, although the second device 30 is a device of the user using the second telephone number in the past, the second device 30 can no longer use the second telephone number because of the termination of the mobile communication service, Service, and the second telephone number is assigned.

The server 10 may receive a request message for the user information of the second telephone number from the first device 20. [ At this time, the request message may include a first telephone number or a second telephone number. In response, the server 10 may send user information using the second telephone number to the first device 20. Here, the user information may be personal information or ID of the user.

Although the server 10 is described as requesting and transmitting user information for one device, the present invention is not limited thereto. The server 10 may transmit user information for each of a plurality of phone numbers from the first device 20 And the server 10 may transmit user information for each of a plurality of phone numbers to the first device 20 in a list form.

Further, the server 10 may receive a result of whether the user using the second telephone number from the first device 20 is a friend of the user using the first device 20.

According to another embodiment of the present invention, the server 10 can confirm whether or not the user using the second telephone number is changed, and when the user has a changed history, the server 10 transmits the user information using the second telephone number to the first device (20). Further, the server 10 may receive a response from the first device 20 indicating whether to keep the user using the second telephone number as a friend of the user who uses the first telephone number or to exclude the friend from the friend.

The first device 20 can receive an application service from the server 10 and register a user using the second phone number as a friend on the application service. In this case, an example of the application service is an IMS service, and the IMS can be provided through an IMS application installed in the first device 20. [ Here, the application is an application, and may include, for example, an app (app) running on the first device 20. Also, the first device 20 is an example of a friend confirmation device.

The first device 20 can transmit a message requesting the user information of the second telephone number to the server 10 and receive the user information of the second telephone number from the server 10 as the response message to the server 10 . Further, the first device 20 confirms whether the user currently using the second telephone number is a friend of the user of the first device 20, based on the user information of the second telephone number received from the server 10 . For example, the first device 20 may determine whether to retain the user using the second telephone number as a friend of the application service of the user of the first device 20, or to exclude the user of the application service from the friend And can transmit the determination result to the server 10.

As described above, the user of the second device 30 using the second phone number may have a friend relationship with the user of the first device 20 on the application service of the first device 20. However, even if the user of the second device 30 cancels the mobile communication service, the user of the first device 20 and the user of the second device 30 corresponding to the second phone number The friendship between the users of the two devices 30 may be maintained. When the user of the third device 40 subscribes to the mobile communication service or changes the telephone number used in the third device 40, the user of the third device 40 transmits the second telephone number to the third device 40 (40). In this case, since the user corresponding to the second telephone number registered as a friend of the user of the first device 20 is the user of the third device 40, The user of the application 40 may remain a friend on the application service.

The first device 20 to the third device 40 may include a mobile terminal capable of wireless communication and according to various embodiments of the present invention the first device 20 to the third device 40 may comprise various Lt; / RTI > For example, the first device 20 to the third device 40 may be a TV device, a computer, or a portable terminal capable of accessing a remote server through a network. Here, an example of the TV apparatus includes a smart TV, an IPTV set-top box, and the like. Examples of the computer include a notebook computer, a desktop computer, a laptop computer, One example of the terminal includes a Personal Communication System (PCS), a Global System for Mobile Communications (GSM), a Personal Digital Cellular (PDC), a Personal Handyphone System (PHS) Assistant, IMT (International Mobile Telecommunication) -2000, Code Division Multiple Access (CDMA) -2000, W-Code Division Multiple Access (W-CDMA), Wibro (Wireless Broadband Internet) terminals, smart phones, And the like may be included in the present invention.

The server 10, the first device 20, the second device 30, and the third device 40 included in the friend confirmation service providing system may be connected through a network. In this case, the network means a connection structure in which information can be exchanged between each node such as terminals and servers. An example of such a network is the Internet, a wireless local area network (WLAN) , Wide Area Network (WAN), Personal Area Network (PAN), 3G, Long Term Evolution (LTE), Wireless Fidelity (WiFi), World Interoperability for Microwave Access (WiMAX), and Wireless Gigabit It does not.

Hereinafter, the operation of the first device 20 of FIG. 1 will be described in more detail.

Fig. 2 is a configuration diagram of the first device 20 shown in Fig. 1 according to an embodiment of the present invention. 2, the first device 20 includes a message generation unit 201, a transmission unit 202, a reception unit 203, a confirmation processing unit 204, a display unit 205, a user interface 206, and a DB Database) 207, as shown in FIG. However, the first device 20 shown in FIG. 2 is only one embodiment of the present invention, and various modifications are possible based on the components shown in FIG.

The message generation unit 201 may generate a request message. The request message may be a message requesting user information of a user using a second telephone number, and accordingly, the request message may include a second telephone number.

The transmitting unit 202 may transmit the request message generated by the message generating unit 201 to the server 10. Further, the receiving unit 203 may receive user information about the user using the second telephone number from the server 10 as a response message.

The confirmation processing unit 204 can confirm whether the user is a friend of the user of the first device 20 based on the user information about the user using the second phone number received by the receiving unit 203. [ At this time, the transmitting unit 202 can transmit the confirmation result to the server 10.

The display unit 205 may be connected to the first device 20 or may display information necessary for the display device mounted on the first device 20. [ For example, the display unit 205 may display on the display device a UI for confirming a friend so that the user of the first device 20 can determine whether the user using the second telephone number is a friend.

The user interface 206 may receive any command or information from the user of the first device 20. In this case, the user interface 206 may be an input device such as a keyboard, a mouse, a touch pad, a touch screen, or the like, but may be a graphical user interface (GUI) represented in an image display device.

The DB 207 can store data. In this case, the data stored in the DB may include data to be input and output between the respective components in the first device 20, and data stored in the first device 20 and the components outside the first device 20 And may include data to be input and output between them. For example, the DB 207 may store user information on a user using the second telephone number received by the receiving unit 203. [ In addition, the DB 207 can store the friendship between the user of the first device 20 identified by the confirmation processing unit 204 and the user using the second telephone number. One example of such a DB 207 may include a hard disk drive, a ROM (Read Only Memory), a RAM (Random Access Memory), a flash memory, a memory card, and the like, which are located inside or outside the first device 20.

Those skilled in the art will recognize that the message generation unit 201, the transmission unit 202, the reception unit 203, the confirmation processing unit 204, the display unit 205, the user interface 206 and the DB 207 are separately implemented, Or < / RTI >

3 is a flowchart illustrating a method for confirming a friend relationship between a user of a first device 20 and a user using a second telephone number, according to an embodiment of the present invention. The method for confirming the friendship between users according to the embodiment shown in FIG. 3 includes the steps of time series processing in the server 10 and the first device 20 according to the embodiment shown in FIGS. 1 and 2 do. Therefore, even if omitted below, the contents described with respect to the server 10 and the first device 20 in FIGS. 1 and 2 are also applied to a method for confirming the friendship between users according to the embodiment shown in FIG. 3 .

In step S310, the first device 20 may transmit a request message to the server 10. Here, the request message may be a message requesting user information including identification information such as the user's real name or personal information using the second telephone number, or a friend confirmation request message. Alternatively, the request message may be a message requesting a friend list including user information of the user using the second telephone number.

In step S320, the server 10 may transmit a response message to the first device 20 in response to the request message received in step S310. In this case, the response message may include a user list of the user using the second telephone number or a list of friends including the user information.

The server 10 may receive the user information of the user using the second telephone number from the user terminal to which the second telephone number is assigned or may collect it from the DB of the server 10. [ Specifically, when the user information is stored in the DB of the server 10, the server 10 receives and stores the changed user information when the user using the second telephone number is changed, May periodically receive and store user information for a user using the second telephone number with respect to the second telephone number.

In step S330, the first device 20 can check whether the user using the second telephone number is a friend based on the user information received in step S320. A specific method of checking whether a user using the second telephone number is a friend will be described with reference to FIGS. 4 and 5. FIG.

FIG. 4 is a flowchart illustrating a method for confirming the friend relationship shown in FIG. 3 according to an embodiment of the present invention. FIG. And a UI displayed to confirm a friend relationship with the device.

Referring to FIG. 4, in step S331, the first device 20 may display on the display device a UI including an icon or an input window that can receive user information and user input received in step S320. Here, the UI may further include various embodiments other than the method shown in FIG. 5 as a user interface for confirming the friend relationship.

In step S332, the first device 20 receives the user input for the icon or the input window displayed on the display device in step S331, and determines whether the user using the second telephone number is a friend based on the received user input have.

5 displays the name of the friend corresponding to the specific phone number and the 'friend confirmation required' icon 511 for the friend in the friend list UI 51 received by the first device 20 from the server 10, And a 'friend confirmation completion' icon 512 are included.

Here, the name of the friend included in the friend list UI 51 is the name stored in the phone book of the first device 20, and is a name of the friend of the first device 20 regardless of the intention of the actual user using the specific phone number. May be directly input values. Therefore, even if the user using the telephone number is changed, the friend name of the friend list can not be updated unless the name on the telephone book of the first device 20 is changed.

If the user information of the user using the telephone number is changed after the friend relationship is established with the user using the specific telephone number, the 'friend confirmation required' icon 511 may be displayed. Otherwise, Completion 'icon 512 may be displayed.

The first friend confirmation UI 52 may be displayed on the display device of the first device 20 when the 'friend confirmation required' icon 511 is selected through the user input in the first device 20. In this case, the user of the first device 20 inputs the friend information of the friend into the input field 521 through the user interface, and can select the 'friend confirmation' icon 522 by a click, a touch, or the like have. The device 20 can confirm whether or not the user of the first device 20 is a friend of the user of the first device 20 based on the selection of the 'friend identification' icon 522. [

In another embodiment of the present invention, the second friend confirmation UI 53 is displayed on the display device of the first device 20 when the 'friend confirmation required' icon 511 is selected through the user input in the first device 20, May be displayed. The subsequent procedure corresponds to the first friend confirmation UI 52, and an unnecessary description will be omitted.

In the first friend confirmation UI 52, the name registered in the phone book of the first device 20 is exposed to a friend requiring friend confirmation, while the second friend confirmation UI 53 is displayed to the friend who needs friend confirmation The telephone number registered in the telephone directory of the first device 20 may be exposed.

Referring back to FIG. 3, in step S340, the first device 20 may transmit the result of the friend confirmation to the server 10 in step S330. In this case, based on the confirmation result, the first device 20 can determine whether to hold the user using the second telephone number as a friend or delete it from the friend list, and transmit it to the server 10.

In step S350, the server 10 can store the friend confirmation result received in step S340, and further, in accordance with the determination of the first device 20 received in step S340, the friend list of the first device 20 Can be modified.

In the above description, steps S310 to S350 may be further divided into further steps or combined into fewer steps, according to an embodiment of the present invention. Also, some of the steps may be omitted as necessary, and the order between the steps may be changed.

6 is a flowchart illustrating a method of confirming a friend relationship between a user of a first device and a user using a second telephone number according to another exemplary embodiment of the present invention. The method for confirming the friendship between users according to the embodiment shown in FIG. 6 is performed by the server 10, the first device 20 and the third device 40 according to the embodiment shown in FIGS. 1 and 2 And thermally processed. 1 and 2, the contents described with respect to the server 10, the first device 20, and the third device 40 in the first embodiment are the same as those in the first embodiment, It can also be applied to the method of confirming the relationship.

In step S610, the third device 40, which has been given the second telephone number, may transmit the user information registration or change request to the server 10. In this case, the user information registration can be performed when the application service is newly started by installing the IMS application in the third device 40, and the user information change can be performed at any time by the request of the third device 40 . Further, the user information registration or change request may include user information of the third device 40. [

In step S620, the server 10 stores the user information of the third device 40 received in step S610, and stores the telephone number of the third device 40 and the telephone number of the third device 40 on the basis of the telephone number assigned to the third device 40 The user of the first device 20 having a friend relationship can be inquired.

In step S630, the server 10 may transmit a notification message to the inquired first device 20 informing that the third device 40 has requested the user information registration or change in step S610. In addition, the notification message may include user information of the third device 40 stored in step S620. Further, the notification message may be transmitted to the first device 20 every predetermined period.

In step S640, the first device 20 can check whether the user of the third device 40 is a friend, based on the user information of the third device 40 received in step S630.

In step S650, the first device 20 may transmit the result of the friend confirmation to the server 10 in step S640. In this case, the first device 20 determines whether to keep the user of the third device 40 using the second telephone number as a friend or delete it from the friend list, based on the confirmation result, and sends it to the server 10 Lt; / RTI >

In step S660, the server 10 may store the friend confirmation result received in step S650, and further, in accordance with the determination of the first device 20 received in step S650, the friend list of the first device 20 Can be modified.

In step S670, the server 10 may transmit the received friend confirmation result to the third device 40 in step S650.

In the above description, steps S610 through S670 may be further divided into further steps or combined into fewer steps, according to an embodiment of the present invention. Also, some of the steps may be omitted as necessary, and the order between the steps may be changed.

7 is a flowchart illustrating a method for confirming a friend relationship between a user of a first device and a user using a second telephone number according to another embodiment of the present invention. The method of confirming the friendship between users according to the embodiment shown in FIG. 7 is performed by the server 10, the first device 20 and the third device 40 according to the embodiment shown in FIGS. 1 and 2 And thermally processed. 1 and 2, the content described with respect to the server 10, the first device 20, and the third device 40 in FIG. 1 and FIG. It can also be applied to the method of confirming the relationship.

In step S710, the first device 20 may transmit a request message to the server 10. Here, the request message may include the second phone number as the friend confirmation request message and the user information corresponding to the second phone number. The user information corresponding to the second telephone number may be newly input from the user of the first device 20 or may be information collected from the DB of the first device 20. [ If the device using the second telephone number is changed from the second device 30 to the third device 40 and the first device 20 does not know the fact, The user information may be user information of the second device 30.

In step S720, the server 10 may transmit the friend confirmation request message received in step S710 to the third device 40 corresponding to the second telephone number.

In step S730, the third device 40 compares the user information corresponding to the second phone number included in the friend confirmation request message received in step S720 with the user information on the third device 40, The user of the device 20 and the user of the third device 40 can check whether they are friends.

In step S740, the third device 40 may transmit the friend confirmation result to the server 10 in step S730. In step S750, the server 10 transmits the friend confirmation result received in step S740 to the first device 20).

In step S760, the first device 20 determines whether to keep the user of the third device 40 using the second phone number as a friend or delete it from the friend list based on the result of the friendship check received in step S750 .

In the above description, steps S710 to S760 may be further divided into further steps or combined into fewer steps, according to an embodiment of the present invention. Also, some of the steps may be omitted as necessary, and the order between the steps may be changed.

Hereinafter, the operation of the server 10 of FIG. 1 will be described in more detail.

FIG. 8 is a configuration diagram of the server 10 shown in FIG. 1 according to an embodiment of the present invention. 8, the server 10 includes a receiving unit 101, a first checking processing unit 102, a second checking processing unit 103, a transmitting unit 104, a storing unit 105, and a DB 106 can do. If necessary, the message generating unit 107 may be further included. However, the server 10 shown in FIG. 8 is only one embodiment of the present invention, and various modifications are possible based on the components shown in FIG.

The receiving unit 101 may receive a request message from the first device 20 corresponding to the first telephone number. In this case, the request message may be user information of the second user or a message requesting whether the second user is a friend of the first user.

The first confirmation processing unit 102 can confirm whether or not the user information of the second telephone number is changed.

The second confirmation processing unit 103 can confirm whether or not the second user is a friend of the first user based on the user information change confirmation result of the first confirmation processing unit 102. [

The transmitting unit 104 may transmit the response message generated by the message generating unit 103 or the confirmation result of the friend of the second confirmation processing unit 104 to the first device 20.

The storage unit 105 may perform management or processing of data in the DB 106. For example, the storage unit 105 may store the friend list data of the first device 20 in the DB 106 or store the friend confirmation result data of the first device 30 in the DB 106 . For example, the storage unit 105 may extract the friend list data of the first device 20 from the DB 106 or delete some of the friend list data of the first device 20.

The DB 106 may store data. In this case, the data stored in the DB 106 includes data to be input and output between the respective components in the server 10, and data input and output between the components outside the server 10 and the server 10 Lt; / RTI > For example, the DB 106 may store a friend list of a user of the first device 20 and may store a phone number corresponding to a second user included in the friend list of the user of the first device 20 have. In addition, the DB 106 may store a history of changes to the user information of the second user. One example of such a DB 106 may include a hard disk drive, a ROM (Read Only Memory), a RAM (Random Access Memory), a flash memory, a memory card, or the like existing inside or outside the server 10.

The message generating unit 107 may generate a response message including user information of a second user assigned a second telephone number or information indicating that a user of the second telephone number is changed. The response message generated by the message generation unit 107 may be transmitted to the first device 20 through the transmission unit 105.

Those skilled in the art will recognize that the receiving unit 101, the first confirmation processing unit 102, the second confirmation processing unit 103, the transmission unit 104, the storage unit 105, the DB 106, and the message generation unit 107, Or that one or more of them may be implemented in an integrated manner.

9 is a flowchart illustrating a method of confirming a friend relationship between a user of a first device 20 and a user using a second telephone number according to another embodiment of the present invention. The method for confirming the friendship between users according to the embodiment shown in FIG. 9 is performed in a time-series manner in the server 10 and the first device 20 according to the embodiment shown in FIGS. 1, 2 and 8 / RTI > Therefore, even if omitted in the following description, the contents described with respect to the server 10 and the first device 20 in FIGS. 1, 2, and 8 are the same as those described with reference to FIG. Method.

The first device 20 can transmit a request message to the server 10 in step S910. Here, the request message may be the user information of the second user in the friend relationship of the user of the first device 20 or the request message to the friend list of the first device 20. The request message for the friend list may include a telephone number corresponding to each of a plurality of friends included in the friend list. For example, if there is a second user in the buddy list, the request message for the buddy list may include the phone number stored in the first device 20 corresponding to the second user.

In step S920, the server 10 receives the request message from the first device 20 and can check whether the user information of the second telephone number in the friend list of the user of the first device 20 has been changed. If the request message includes user information corresponding to the second telephone number and the second telephone number, the change of the user information may be confirmed through the change history of the user information of the second telephone number, The user information of the user corresponding to the telephone number can be compared with the user information of the second user corresponding to the second telephone number stored in the server. Herein, the user information of the second user is the user information of the device currently assigned the second telephone number, the device which is allocated the second telephone number cancels the mobile communication service, There may be a case where another device that has changed the telephone number by the number registers the user information by subscribing to the application service based on the second telephone number. Furthermore, the change history of the user information includes information on the time point at which the user information is changed, and the time reference for determining whether to change the user information is determined based on whether to allow the first device 20 to keep the user of the specific device as a friend, It may be a time when it is judged whether or not to exclude it. That is, if the user information of the second user is changed after the first device 20 determines whether the user of the specific device should be kept as a friend or excluded from the friend list, the server 10 transmits the user information of the second user It may transmit a response message to the first device 20.

In step S930, when the change of the user information is confirmed, the server 10 sends a message including the user information of the second user or the information indicating that the user of the second telephone number is changed to the first device 20 as a response message Lt; / RTI >

In step S940, based on the response message received in step S930, the first device 20 can determine whether to hold the user of the device using the second telephone number as a friend or exclude from the friend list.

In step S950, the first device 20 can transmit the determination result in step S940 to the server 10.

In step S960, the server 10 can update the friend list of the first device 20 based on the determination result in step S940 received in step S950.

In the above description, steps S910 to S960 may be further divided into further steps or combined into fewer steps, according to an embodiment of the present invention. Also, some of the steps may be omitted as necessary, and the order between the steps may be changed.

10 is a flowchart illustrating a method for confirming a friend relationship between a user of a first device 20 and a user using a second telephone number according to another embodiment of the present invention. The method of confirming the friendship between users according to the embodiment shown in FIG. 10 is performed in a time-series manner in the server 10 and the first device 20 according to the embodiment shown in FIGS. 1, 2 and 8 / RTI > Therefore, even if omitted in the following description, the contents described with respect to the server 10 and the first device 20 in FIGS. 1, 2, and 8 are the same as those described with reference to FIG. Method.

In step S1010, the first device 20 may request the server 10 of the friend list of the first device 20. [

In step S1020, the server 10 may transmit the friend list of the first device 20 to the first device 20 in response to the friend list request received in step S1010. The friend list transmitted to the first device 20 may include status information of each of the friends included in the friend list. Here, one example of the status information may be information indicating whether each friend included in the friend list is identified as a friend or whether a friend confirmation is required.

In step S1030, the first device 20 may display the friend list received in step S1020 on the display device of the first device 20. [ At this time, if there is an object (friend) whose friend has not been confirmed, an identifier indicating that friend confirmation is necessary for the friend may be displayed together. An identifier indicating that the friend confirmation has been completed may be displayed for the object whose friend confirmation has been completed.

In step S1040, the first device 20 may transmit a friend confirmation request to the server 10 for a friend whose friend list is to be checked out of the friend list received in step S1030. In this case, the friend confirmation request may include user information that the first device 20 knows about the object requiring the friend confirmation.

In step S1050, the server 10 may perform a friend confirmation procedure based on the friend confirmation request received in step S1040. The friend confirmation procedure may be performed by comparing the user information included in the friend confirmation request received in step S1040 with the user information about the user of the second phone number stored in the server 10. [

In step S1060, the server 10 may transmit the friend confirmation result to the first device 20 in step S1050.

In step S1070, based on the friend confirmation result received in step S1060, the first device 20 can determine whether to keep the user of the device using the second telephone number as a friend or exclude from the friend list.

In step S1080, the first device 20 may transmit the determination result in step S1070 to the server 10. [

In step S1090, the server 10 can update the friend list of the first device 20 based on the determination result in step S1070 received in step S1080.

In the above description, steps S1010 to S1090 may be further divided into additional steps or combined into fewer steps, according to an embodiment of the present invention. Also, some of the steps may be omitted as necessary, and the order between the steps may be changed.

11 is a flowchart illustrating a method for confirming a friend relationship between a user of a first device 20 and a user using a second telephone number according to another embodiment of the present invention. The method of confirming the friendship between users according to the embodiment shown in FIG. 11 is performed in a time-series manner in the server 10 and the first device 20 according to the embodiment shown in FIGS. 1, 2 and 8 / RTI > Therefore, even if omitted in the following description, the contents described with respect to the server 10 and the first device 20 in FIGS. 1, 2, and 8 are the same as those described with reference to FIG. Method.

The first device 20 may transmit the friend list request message of the first device 20 to the server 10 in step S1110. In this case, the update request message may include, for the second telephone number, an update request for the second user assigned the second telephone number.

In step S1120, the server 10 can confirm whether or not each of the friends (users) included in the friend list of the first device 20 or the user information corresponding to the second phone number is changed. If the user information change is confirmed through the change history of the user information of the second telephone number or if the friend list request message includes user information corresponding to the second telephone number and the second telephone number, The user information corresponding to the second telephone number can be compared with the second user information corresponding to the second telephone number stored in the server.

In step S1130, the server 10 can update the friend list based on the result of the user information change confirmation in step S1120.

In step S1140, the server 10 may transmit the updated friend list of the first device 20 to the first device 20 in step S1130.

In the above description, steps S1110 to S1140 may be further divided into further steps or combined into fewer steps, according to an embodiment of the present invention. Also, some of the steps may be omitted as necessary, and the order between the steps may be changed.

One embodiment of the present invention may also be embodied in the form of a recording medium including instructions executable by a computer, such as program modules, being executed by a computer. Computer readable media can be any available media that can be accessed by a computer and includes both volatile and nonvolatile media, removable and non-removable media. In addition, the computer-readable medium may include both computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Communication media typically includes any information delivery media, including computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave, or other transport mechanism.

It will be understood by those skilled in the art that the foregoing description of the present invention is for illustrative purposes only and that those of ordinary skill in the art can readily understand that various changes and modifications may be made without departing from the spirit or essential characteristics of the present invention. will be. It is therefore to be understood that the above-described embodiments are illustrative in all aspects and not restrictive. For example, each component described as a single entity may be distributed and implemented, and components described as being distributed may also be implemented in a combined form.

It is intended that the present invention covers the modifications and variations of this invention provided they come within the scope of the appended claims and their equivalents. .

10: Server
20: First device
30: second device
40: Third device

Claims (22)

A method for confirming whether a current user of another phone number included in a friend list of an application providing an instant message service by a device is a friend,
Transmitting a request message requesting user information of the another telephone number to a server;
Receiving a response message including user information of the other telephone number from the server;
Determining whether the current user is a friend of a first user using the phone number of the device based on the user information of the other phone number; And
And transmitting the result of the confirmation to the server,
Wherein the step of verifying whether the first user is a friend includes:
Comparing the user information stored in the device with the user information of the another phone number included in the response message or checking whether the user information of the other phone number is changed,
Wherein the transmitting the result of the confirmation to the server comprises:
If there is a mismatch between the user information of the other telephone number included in the response message and the user information stored in the device or if there is a changed history of the user of the device using the other telephone number in the change history, And sending a response as to whether to keep or exclude the user as a friend of the first user.
delete The method according to claim 1,
Wherein the user information is personal information or an identity of the current user.
The method according to claim 1,
Wherein the step of verifying whether the first user is a friend includes:
Displaying an icon or an input window associated with the user information on a display of the device; And
Determining whether the current user is a friend of a first user using the phone number based on the input to the icon or input window.
The method according to claim 1,
Wherein the step of verifying whether the first user is a friend includes:
The current user is a friend of the first user who uses the telephone number according to the comparison result between the user information inputted from the user interface of the device or the user information previously stored in the database of the device and the user information of the other telephone number How to check whether, how.
The method according to claim 1,
Wherein the response message includes a friend list of the first user,
Wherein the buddy list includes a plurality of other phone numbers and current user information of each of the plurality of other phone numbers,
Wherein the step of confirming whether or not the first user is a friend includes the step of determining whether or not the current user of each of the plurality of other telephone numbers is in the state of being a friend of the other user based on the current user information of each of the plurality of other telephone numbers and each of the plurality of other telephone numbers 1 < / RTI >user's friend.
The method according to claim 1,
Transmitting the result of the confirmation to the server,
Wherein the result of the confirmation includes first data requesting to register or maintain the other phone number with the friend phone number of the phone number when the current user is a friend of the first user, And second data requesting to exclude the other phone number from the friend phone number of the phone number if the friend is not a friend of one user.
The method according to claim 1,
Wherein the message is a notification message informing a user information registration or change request from the other device of the current user.
9. The method of claim 8,
Prior to the step of receiving the notification message from the server,
Receiving a user information registration or change request from another device of the current user; And
And inquiring the first user having a friend relationship with another phone number based on the received user information registration or change request.
A method for confirming whether a current user of another phone number included in a friend list of an application providing an instant message service by a device is a friend,
Transmitting a request message including the other telephone number stored in the device and user information of the other telephone number to a server;
Receiving a response message from the server, wherein the response message includes a result of whether the user information of the another telephone number is the same as the current user information of the other telephone number; And
And determining whether the current user is a friend of a first user using the phone number of the device based on the result,
Wherein the result included in the response message includes:
A result obtained by comparing the user information of the other device with the user information of the other phone number included in the request message or the change history of the user information of the other phone number in the other device corresponding to the other phone number Lt; / RTI >
Wherein the step of verifying whether the first user is a friend includes:
If there is a mismatch between the user information of the other device and the user information of the other phone number contained in the request message or if there is a changed history of the user of the device using the other phone number in the change history, And sending a response as to whether to maintain or exclude the changed user as a friend of the first user.
11. The method of claim 10,
Wherein the server transmits the user information of the other telephone number to another device corresponding to the other telephone number, receives the result from the other device, and transmits the received result to the device.
A method of confirming whether a second user of a second phone number included in a friend list of an application providing an instant messaging service by a server is a friend of a first user of a first phone number,
Receiving a request message from a first device corresponding to the first telephone number;
Confirming whether the user information of the second telephone number is changed;
Transmitting a response message including user information of the second user or information indicating that a user of the second telephone number is changed to the first device; And
Receiving a response from the first device as to whether to keep or exclude the second user as a friend of the first user,
Wherein the step of verifying whether the user information of the second telephone number is changed comprises:
Comparing the user information of the second telephone number included in the request message with the user information stored in the server or checking the change history of the user information of the second telephone number to determine whether the user information of the second telephone number is changed Lt; / RTI >
Wherein the step of receiving a response as to whether to maintain or exclude the second user as a friend of the first user comprises:
If the user information of the second telephone number included in the request message is inconsistent with the user information stored in the server or a history of the user of the device using the second telephone number as the change history is changed to the second user exists And receiving a response from the first device as to whether to keep or exclude the second user as a friend of the first user
13. The method of claim 12,
Wherein the change history includes a time point at which the user information of the second telephone number is changed,
Wherein the step of transmitting the first telephone number to the first device comprises the steps of: when there is a history in which the user information of the second telephone number is changed to the user information of the second user, And sending a response message containing the user information of the second user to the first device.
13. The method of claim 12,
Wherein the step of verifying whether the user information of the second telephone number is changed comprises:
When the request message received from the first device includes the user information of the user corresponding to the second telephone number and the second telephone number, the user of the user corresponding to the second telephone number included in the request message, And comparing the information with user information of a second user corresponding to the second phone number stored in the server.
A method of confirming whether a second user of a second phone number included in a friend list of an application providing an instant messaging service by a server is a friend of a first user of a first phone number,
Receiving a request message from a first device corresponding to the first telephone number;
Transmitting a response message including status information of a user corresponding to the second telephone number to the first device;
Receiving a friend confirmation request message including user information of a user corresponding to the second telephone number from the first device;
Comparing the user information of the user corresponding to the second telephone number with the user information of the second user stored in the server to confirm whether the second user is a friend of the first user;
Transmitting the result of the confirmation to the first device; And
Receiving a response from the first device as to whether to keep or exclude the second user as a friend of the first user,
Wherein the step of confirming whether the second user is a friend of the first user comprises:
Comparing the user information of the second user stored in the server with the user information included in the friend confirmation request message or checking the change history of the user information of the second phone number, Make sure you are friends,
Wherein the step of receiving a response as to whether to maintain or exclude the second user as a friend of the first user comprises:
If there is a mismatch between the user information of the second user stored in the server and the user information contained in the friend confirmation request message or if the history of the user of the device using the second phone number changed to the second user exists And if so, receiving a response as to whether to keep or exclude the second user from the first device as a friend of the first user.
16. The method of claim 15,
Receiving a response from the first device as to whether to keep or exclude the second user as a friend of the first user; And
And updating the buddy list of the first phone number based on the response.
16. The method of claim 15,
Wherein the status information of the user corresponding to the second telephone number is information indicating whether a friend confirmation or a friend confirmation is necessary.
A method of confirming whether a second user of a second phone number included in a friend list of an application providing an instant messaging service by a server is a friend of a first user of a first phone number,
Receiving a request message from a first device corresponding to the first telephone number;
Confirming whether the user information of the second telephone number is changed;
Checking whether the second user is a friend of the first user based on a result of checking whether the user information of the second phone number is changed;
Transmitting the friend confirmation result to the first device; And
Receiving a response from the first device as to whether to keep or exclude the second user as a friend of the first user,
Wherein the step of verifying whether the user information of the second telephone number is changed comprises:
Comparing the user information stored in the server with the user information of the second telephone number included in the request message or checking the change history of the user information of the second telephone number to determine whether the user information of the second telephone number is changed Lt; / RTI >
Wherein the step of receiving a response as to whether to maintain or exclude the second user as a friend of the first user comprises:
If there is a mismatch between the user information stored in the server and the user information of the second phone number included in the request message or a history of the user of the device using the second phone number changed to the second user exists in the change history And receive a response as to whether to keep or exclude the second user from the first device as a friend of the first user.
19. The method of claim 18,
And updating the friend list of the first user according to the result of the friendship check if the second user is not a friend of the first user.
A device for confirming whether a current user of another phone number included in a friend list of an application providing an instant message service is a friend, comprising:
A message generator for generating a request message including a telephone number of the device;
A transmitting unit for transmitting the generated request message to a server;
A receiving unit for receiving a response message including user information of the other telephone number from a server; And
And a confirmation processing unit for checking whether the current user of the other phone number is a friend of the first user using the phone number of the device based on the user information of the other phone number,
The confirmation processing unit,
Comparing the user information stored in the device with the user information of the another phone number included in the response message or checking the change history of the user information of the other phone number,
Wherein the transmission unit comprises:
When there is a mismatch between the user information stored in the device and the user information of the other telephone number included in the response message or if there is a history in which the user of the device using the other telephone number is changed to the second user, And send a response to the server whether to keep or exclude the second user as a friend of the first user.
A server for confirming whether a second user of a second phone number included in a friend list of an application providing an instant messaging service is a friend of a first user of a first phone number,
A receiving unit for receiving a request message from a first device corresponding to the first telephone number;
A first confirmation processing unit for checking whether the user information of the second telephone number is changed;
A second confirmation processing unit for confirming whether the current user of the second telephone number is a friend of the first user using the telephone number of the device, based on the result of checking the user information change of the first confirmation processing unit; And
And a transmitting unit for transmitting the result of the friend confirmation to the first device,
The first confirmation processing unit,
Comparing the user information stored in the server with the user information of the second phone number included in the request message or checking the change history of the user information of the second phone number,
The receiver may further comprise:
The user information stored in the server and the user information of the second telephone number included in the request message do not match or a history of a user of the device using the second telephone number changed to the second user exists in the change history And receives a response as to whether to keep or exclude the second user from the first device as a friend of the first user.
22. The method of claim 21,
Further comprising a message generating unit for generating a response message including user information of the current user or information indicating that a user of the second telephone number is changed,
Wherein the transmitting unit transmits the response message generated by the message generating unit to the first device.

Images