AU2015297192B2

AU2015297192B2 - Mobile communication system, different mobile devices sharing same phone number on mobile communication system, and method of providing mobile communication service between different mobile devices sharing same phone number

Info

Publication number: AU2015297192B2
Application number: AU2015297192A
Authority: AU
Inventors: Shi-Yun Cho; Hee-Seok Jeong; Moon-Joo Lee
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2014-07-31
Filing date: 2015-07-27
Publication date: 2018-05-10
Anticipated expiration: 2035-07-27
Also published as: RU2017106249A3; TW201711491A; AU2018214146A1; AU2018214146B2; KR102345651B1; RU2017106249A; AU2015297192A1; TWI650035B; TW201613381A; RU2682905C2; KR20160016577A; TWI571161B

Abstract

A mobile device configured to share a phone number of another mobile device on a mobile communication system, the mobile device including: a controller configured to, after determining that a phone function of the another mobile device is deactivated, activate a phone function of the mobile device to which the phone number of the another mobile device is assigned; and a communicator configured to perform a mobile communication function using the phone number when the phone function of the mobile device is activated.

Description

Title of Invention: MOBILE COMMUNICATION SYSTEM, DIFFERENT MOBILE DEVICES SHARING SAME PHONE NUMBER ON MOBILE COMMUNICATION SYSTEM, AND

METHOD OF PROVIDING MOBILE COMMUNICATION SERVICE BETWEEN DIFFERENT MOBILE DEVICES SHARING SAME PHONE NUMBER

Technical Field [1] Aspects of one or more exemplary embodiments relate to a mobile communication system and different mobile devices sharing the same phone number on a mobile communication system.

Background Art [2] Digital-based information and communication technology is rapidly developing. Information innovation spread by mobile phones and the Internet, and smart phones and tablet devices, in which functions of mobile phones and the Internet are combined, are increasingly common. Devices using new paradigms, such as wearable devices, have appeared. Consumers who already own a smart phone want to use such new paradigm devices. Thus, studies have been conducted into ways for new types of devices or new paradigm devices to merge with existing smart phones and tablet devices and permeate into consumers' daily lives.

[2a] A reference herein to a patent document or any other matter identified as prior art, is not to be taken as an admission that the document or other matter was known or that the information it contains was part of the common general knowledge as at the priority date of any of the claims.

Disclosure of Invention [3] Aspects of one or more exemplary embodiments include a mobile communication system and different mobile devices sharing the same phone number on a mobile communication system. The technical problem to be solved by the exemplary embodiments is not limited to the above technical problems and thus other technical problems may be inferred from the following exemplary embodiments.

[4] Additional aspects will be set forth in part in the description which follows and, in part, will be apparent from the description, or may be learned by practice of the presented exemplary embodiments.

[5] According to a first aspect of the present invention, there is provided a second mobile device configured to share a phone number of a first mobile device on a mobile communication system, the mobile device comprising: a communication interface configured to download a subscriber identification module (SIM) information from a server when a call function of the second mobile device is activated; a subscriber identification module (SIM) configured to store the downloaded SIM information; and a controller configured to determine whether a call function of the first mobile device is deactivated and

2015297192 18 Apr 2018 to activate the call function of the second mobile device based on the call function of the first mobile device being deactivated and a phone number of the first mobile device being assigned to the second mobile device, wherein the controller controls the communication interface to transmit a request for using the downloaded SIM information to the server, and the controller activates the call function of the second mobile device in response to receiving an approval from the server.

[6] The mobile device may further include a subscriber identification module (SIM) configured to receive SIM information from a server and store the SIM information.

[7] The SIM information may include subscription information of the mobile device corresponding to the phone number on the mobile communication system on which the another mobile device and the mobile device exist.

[8] The communicator may be further configured to receive the SIM information from the server when the phone function of the mobile device is activated.

[9] The communicator may be further configured to: transmit a request to the server for the SIM information in response to the phone function of the mobile device being activated, and receive the SIM information in response to the request for the SIM information.

[10] The communicator may be further configured to: transmit a request to use the SIM information to the server when the SIM information is received, and perform the mobile communication function in response to receiving an approval from the server.

[11] The mobile device may further include a storage having stored thereon device identification (ID) information having a different value from a device ID information of the another mobile device.

[12] The device ID information of the another mobile device may include at least one of a serial number and an international mobile equipment identity (IMEI) of the another mobile device, and the device ID information of the mobile device may include at least one of a serial number and an IMEI of the mobile device.

[13] The communicator may be further configured to: connect to the another mobile device using short-range wireless communication, and exchange information about an activation state of the phone function of the another mobile device and an activation state of the phone function of the mobile device with the another mobile device.

[14] The controller may be further configured to activate the phone function of the mobile device based on the exchanged information.

[15] The controller may be further configured to, in response to it being determined that the phone function of the another mobile device is deactivated, automatically activate the phone function of the mobile device.

[16] The mobile device may further include a user interface (UI) configured to provide a popup UI for setting an activation state of the phone function of the mobile device.

[17] The controller may be further configured to, in response to a user input to set the activation state of the phone function of the mobile device to active being input through the popup UI, activate the phone function of the mobile device.

2015297192 12 Feb 2018 [18] The mobile device may further include a subscriber identification module (SIM) configured to: receive, from the server, SIM information regardless of an activation state of the phone function of the mobile device, and pre-store the received SIM information.

[19] The communicator may be further configured to, in response to the phone function of the mobile device being activated, transmit a request to use the pre-stored SIM information and perform the mobile communication function in response to receiving an approval from the server.

[20] The communicator may be further configured to, in response to the phone function of the mobile device being activated, receive subscriber identification module (SIM) information from the another mobile device.

[21 ] The communicator may be further configured to, in response to the SIM information being received from the another mobile device, transmit a request to use the received SIM information to the server and perform the mobile communication function in response to receiving an approval from the server.

[22] The communicator may be further configured to, in response to the phone function of the another mobile device being activated while the SIM information is stored in the SIM, transmit the stored SIM information to the another mobile device.

[23] The controller may be further configured to control the SIM to delete SIM information after the SIM information is transmitted.

[24] There may be provided a mobile communication system including: a first mobile device configured to perform a mobile communication function using first subscriber identification module (SIM) information comprising subscription information of a phone number registered with the mobile communication system; a second mobile device configured to perform the mobile communication function using second SIM information comprising the subscription information of the phone number; and a server configured to: receive requests to use the first SIM information and requests to use the second SIM, and connect, in response to the phone number being requested to be called, the phone call to a mobile device corresponding to the requested first SIM information or the requested second SIM information.

[25] The first mobile device may be configured to: transmit a request that the server transmit the first SIM information in response to a phone function of the first mobile device being activated; and transmit a request to use the first SIM information to the server when the first SIM information is received.

[26] The second mobile device may be configured to: transmit a request that the server transmit the second SIM information in response to a phone function of the second mobile device being activated; and transmit a request to use the second SIM information to the server when the second SIM information is received.

2015297192 18 Apr 2018 [27] The first mobile device may be further configured to receive, from the server, the first SIM information regardless of an activation state of a phone function of the first mobile device, and transmit a request to use the first SIM information to the server in response to the phone function being activated in the first mobile device.

[28] The second mobile device may be further configured to receive, from the server, the second SIM information regardless of an activation state of a phone function of the second mobile device, and transmit a request to use the second SIM information to the server in response to the phone function being activated in the second mobile device.

[29] At least one of the first mobile device may be further configured to receive, from the server, the first SIM information regardless of activation of a phone function of the first mobile device, and the second mobile device may be further configured to receive, from the server, the second SIM information regardless of activation of a phone function of the second mobile device.

[30] The first mobile device and the second mobile device may be further configured to exchange the pre-stored first SIM information or the pre-stored second SIM information between the first mobile device and the second mobile device.

[31 ] According to a second aspect of the present invention, there is provided a mobile communication system comprising: a first mobile device configured to perform a call function using a first subscriber identification module (SIM) information comprising subscription information of a phone number registered with the mobile communication system; a second mobile device configured to perform a call function using second SIM information comprising the subscription information of the phone number; and a server configured to: receive requests to use the first SIM information and requests to use the second SIM information, and connect, in response to the phone number being requested to be called, a phone call to a mobile device corresponding to the requested first SIM information or the request second SIM information, wherein the first mobile device is configured to determine whether the call function of the second mobile device is deactivated, activate the call function of the first mobile device when it is determined by the first mobile device that the call function of the second mobile device is deactivated, download the first SIM information from the server when the call function of the first mobile device is activated, wherein the first mobile device transmits a request to use the downloaded first SIM information to the server, and activates the call function of the first mobile device in response to receiving an approval from the server, and wherein the second mobile device is configured to determine whether the call function of the first mobile device is deactivated, activate the call function of the second mobile device based on the call function of the first mobile device being deactivated and the phone number being assigned to the second mobile device, and download the second SIM information from the server

4a

2015297192 18 Apr 2018 when the call function of the second mobile device is activated, and wherein the second mobile device transmits a request to use the downloaded second SIM information to the server, and activates the call function of the second mobile device in response to receiving an approval from the server.

[31 a] According to a third aspect of the present invention, there is provided a method of providing, by a second mobile device sharing a phone number of a first mobile device, a mobile communication device, the method comprising: determining, by the second mobile device, whether a call function of the first mobile device is deactivated and to activate a call function of the second mobile device based on the call function of the first mobile device being deactivated and a phone number of the first mobile device being assigned to the second mobile device; downloading, by the second mobile device, a Subscriber Identification Module (SIM) information from a server; transmitting, by the second mobile device, a request to use the downloaded SIM information to the server; and in response to receiving an approval from the server, activating, by the second mobile device, a call function of the second mobile device to which the phone number of the first mobile device is assigned when it is determined by the second mobile device that the call function of the first mobile device is deactivated.

Advantageous Effects of Invention [32] As described above, according to one or more exemplary embodiments, since a user may use several mobile devices on a mobile communication system using one phone number without having to manage the several mobile devices having different phone numbers, a user owning several mobile devices may receive a mobile communication service via one of the several mobile devices based on his/her situation. Also, the inconvenience of managing different phone numbers of the several mobile devices may be reduced, and other users need not memorize different phone numbers.

Brief Description of Drawings [33] These and/or other aspects will become apparent and more readily appreciated from the following description of certain exemplary embodiments, taken in conjunction with

WO 2016/018017

PCT/KR2015/007785 the accompanying drawings in which:

[34] FIG. 1 is a diagram for describing a mobile communication system in which different mobile devices make a call using a same phone number, according to an exemplary embodiment;

[35] FIG. 2 is a diagram for describing a second mobile device of a user A, according to an exemplary embodiment;

[36] FIG. 3 is a diagram for describing the second mobile device of the user A, according to another exemplary embodiment;

[37] FIG. 4 is a block diagram of the second mobile device, according to an exemplary embodiment;

[38] FIG. 5 is a diagram for describing device identification (ID) information and subscriber identification module (SIM) information, which are stored in each of a first mobile device and the second mobile device, according to an exemplary embodiment;

[39] FIG. 6 is a timing diagram of a method of making a call from a first mobile device and the second mobile device, which have a same phone number and are owned by the user A, to a mobile device of a user B, on the mobile communication system, according to an exemplary embodiment;

[40] FIG. 7 is a diagram for describing a server of a mobile carrier managing mobile devices owned by user A, according to an exemplary embodiment;

[41] FIG. 8A is a diagram for describing linking the first mobile device and the second mobile device in a two-phone mode, according to an exemplary embodiment;

[42] FIG. 8B is a diagram for describing separating the first mobile device and the second mobile device in the two-phone mode, according to an exemplary embodiment;

[43] FIG. 9 is a diagram for describing manually activating a phone function of the first mobile device or a phone function of the second mobile device in the two-phone mode, according to an exemplary embodiment;

[44] FIG. 10A is a flowchart of a method of activating the phone function of the first mobile device or the phone function of the second mobile device in the two-phone mode, according to an exemplary embodiment;

[45] FIG. 10B is a diagram for describing a case in which the phone function of the first mobile device is activated from among the first mobile device and the second mobile device, which are linked to each other in the two-phone mode, according to an exemplary embodiment;

[46] FIG. 10C is a diagram for describing a case in which the phone function of the second mobile device is activated from among the first mobile device and the second mobile device, which are linked to each other in the two-phone mode, according to an exemplary embodiment;

[47] FIG. 10D is a diagram for describing a case in which the phone function of the first

WO 2016/018017

PCT/KR2015/007785 mobile device is activated from among the first mobile device and the second mobile device, which are separated from each other in the two-phone mode, according to an exemplary embodiment;

[48] FIG. 10E is a diagram for describing a case in which the phone function of the second mobile device is activated from among the first mobile device and the second mobile device, which are separated from each other in the two-phone mode, according to an exemplary embodiment;

[49] FIG. 11A is a diagram for describing the device ID information and the SIM information, which are stored in each of the first mobile device and the second mobile device, according to another exemplary embodiment;

[50] FIG. 1 IB is a diagram for describing the device ID information and the SIM information, which are stored in each of the first mobile device and the second mobile device, according to another exemplary embodiment;

[51] FIGS. 12A and 12B are diagrams for describing a concept of a first scenario in which the first mobile device and the second mobile device, receive SIM information from the server of the mobile carrier and transmit a SIM information use request, according to an exemplary embodiment;

[52] FIG. 13A is a timing diagram of a method of performing a mobile communication function by the first mobile device according to a SIM information transmit request and a SIM information use request of the first mobile device, based on the first scenario while the first mobile device and the second mobile device are linked to each other, according to an exemplary embodiment;

[53] FIG. 13B is a timing diagram of a method of performing a mobile communication function by the second mobile device, according to a SIM information transmit request and a SIM information use request of the second mobile device, based on the first scenario while the first mobile device and the second mobile device are linked to each other, according to an exemplary embodiment;

[54] FIG. 13C is a timing diagram of a method of performing a mobile communication function by the first mobile device, according to a SIM information transmit request of the second mobile device and a SIM information use request of the first mobile device, based on the first scenario while the first mobile device and the second mobile device are linked to each other, according to an exemplary embodiment;

[55] FIG. 13D is a timing diagram of a method of performing a mobile communication function by the second mobile device, according to a SIM information transmit request of the first mobile device and a SIM information use request of the second mobile device, based on the first scenario while the first mobile device and the second mobile device are linked to each other, according to an exemplary embodiment;

[56] FIG. 14A is a timing diagram of a method of performing a mobile communication

WO 2016/018017

PCT/KR2015/007785 function by the first mobile device, according to a SIM information transmit request and a SIM information use request of the first mobile device, based on the first scenario while the first mobile device and the second mobile device are separated from each other, according to an exemplary embodiment;

[57] FIG. 14B is a timing diagram of a method of performing a mobile communication function by the second mobile device, according to a SIM information transmit request and a SIM information use request of the second mobile device, based on the first scenario while the first mobile device and the second mobile device are separated from each other, according to an exemplary embodiment;

[58] FIG. 14C is a timing diagram of a method of performing a mobile communication function by the first mobile device, according to a SIM information transmit request of the second mobile device and a SIM information use request of the first mobile device, based on the first scenario while the first mobile device and the second mobile device are separated from each other, according to an exemplary embodiment;

[59] FIG. 14D is a timing diagram of a method of performing a mobile communication function by the second mobile device, according to a SIM information transmit request of the first mobile device and a SIM information use request of the second mobile device, based on the first scenario while the first mobile device and the second mobile device are separated from each other, according to an exemplary embodiment;

[60] FIG. 15 is a diagram for describing a concept of a second scenario in which the first mobile device and the second mobile device, which pre-store SIM information, transmit a SIM use request to the server of the mobile carrier, according to an exemplary embodiment;

[61] FIG. 16A is a timing diagram of a method of performing a mobile communication function by the first mobile device, according to a SIM information use request of the first mobile device, based on the second scenario while the first mobile device and the second mobile device are linked to each other, according to an exemplary embodiment;

[62] FIG. 16B is a timing diagram of a method of performing a mobile communication function by the second mobile device, according to a SIM information use request of the second mobile device, based on the second scenario while the first mobile device and the second mobile device are linked to each other, according to an exemplary embodiment;

[63] FIG. 16C is a timing diagram of a method of performing a mobile communication function by the first mobile device, according to a SIM information use request of the second mobile device, based on the second scenario while the first mobile device and the second mobile device are linked to each other, according to an exemplary embodiment;

[64] FIG. 16D is a timing diagram of a method of performing a mobile communication

WO 2016/018017

PCT/KR2015/007785 function by the second mobile device, according to a SIM information use request of the first mobile device, based on the second scenario while the first mobile device and the second mobile device are linked to each other, according to an exemplary embodiment;

[65] FIG. 17A is a timing diagram of a method of performing a mobile communication function by the first mobile device, according to a SIM information use request of the first mobile device, based on the second scenario while the first mobile device and the second mobile device are separated from each other, according to an exemplary embodiment;

[66] FIG. 17B is a timing diagram of a method of performing a mobile communication function by the second mobile device, according to a SIM information use request of the second mobile device, based on the second scenario while the first mobile device and the second mobile device are separated from each other, according to an exemplary embodiment;

[67] FIG. 17C is a timing diagram of a method of performing a mobile communication function by the first mobile device, according to a SIM information use request of the second mobile device, based on the second scenario while the first mobile device and the second mobile device are separated from each other, according to an exemplary embodiment;

[68] FIG. 17D is a timing diagram of a method of performing a mobile communication function by the second mobile device, according to a SIM information use request of the first mobile device, based on the second scenario while the first mobile device and the second mobile device are separated from each other, according to an exemplary embodiment;

[69] FIGS. 18A and 18B are diagrams for describing a concept of a third scenario in which SIM information is pre-stored in any one of the first mobile device and the second mobile device, according to an exemplary embodiment;

[70] FIG. 19A is a timing diagram of a method of performing a mobile communication function by the first mobile device, when the second mobile device transmits a request to use second SIM information stored in a second downloadable SIM, based on the third scenario while the first mobile device and the second mobile device are linked to each other, according to an exemplary embodiment;

[71] FIG. 19B is a timing diagram of a method of performing a mobile communication function by the first mobile device, when the first mobile device transmits a request to use the second SIM information stored in the second downloadable SIM, based on the third scenario while the first mobile device and the second mobile device are linked to each other, according to an exemplary embodiment;

[72] FIG. 19C is a timing diagram of a method of performing a mobile communication

WO 2016/018017

PCT/KR2015/007785 function by the second mobile device, when the second mobile device transmits a request to use first SIM information stored in a first downloadable SIM, based on the third scenario while the first mobile device and the second mobile device are linked to each other, according to an exemplary embodiment;

[73] FIG. 19D is a timing diagram of a method of performing a mobile communication function by the second mobile device, when the first mobile device transmits a request to use the first SIM information stored in the first downloadable SIM, based on the third scenario while the first mobile device and the second mobile device are linked to each other, according to an exemplary embodiment;

[74] FIG. 20A is a timing diagram of a method of performing a mobile communication function by the first mobile device, when the first mobile device transmits a request to use the second SIM information stored in the second downloadable SIM, based on the third scenario while the first mobile device and the second mobile device are separated from each other, according to an exemplary embodiment;

[75] FIG. 20B is a timing diagram of a method of performing a mobile communication function by the first mobile device, when the second mobile device transmits a request to use the second SIM information stored in the second downloadable SIM, based on the third scenario while the first mobile device and the second mobile device are separated from each other, according to an exemplary embodiment;

[76] FIG. 20C is a timing diagram of a method of performing a mobile communication function by the second mobile device, when the second mobile device transmits a request to use the first SIM information stored in the first downloadable SIM, based on the third scenario while the first mobile device and the second mobile device are separated from each other, according to an exemplary embodiment;

[77] FIG. 20D is a timing diagram of a method of performing a mobile communication function by the second mobile device, when the first mobile device transmits a request to use the first SIM information stored in the first downloadable SIM, based on the third scenario while the first mobile device and the second mobile device are separated from each other, according to an exemplary embodiment;

[78] FIG. 21 is a diagram for describing the device ID information and the SIM information, which are stored in each of the first mobile device and the second mobile device, according to another exemplary embodiment;

[79] FIG. 22A is a timing diagram of a method of performing a mobile communication function by the first mobile device, when the device ID information of the first mobile device and the device ID information of the second mobile device are the same and the phone functions of the first and second mobile devices are both usable, according to an exemplary embodiment;

[80] FIG. 22B is a timing diagram of a method of performing a mobile communication

WO 2016/018017

PCT/KR2015/007785 function by the second mobile device, when the device ID information of the first mobile device and the device ID information of the second mobile device are the same and the phone functions of the first and second mobile devices are both usable, according to an exemplary embodiment;

[81] FIG. 22C is a timing diagram of a method of performing a mobile communication function by the first mobile device, when the device ID information of the first mobile device and the device ID information of the second mobile device are the same and only the phone function of the first mobile device is usable, according to an exemplary embodiment;

[82] FIG. 22D is a timing diagram of a method of performing a mobile communication function by the second mobile device, when the device ID information of the first mobile device and the device ID information of the second mobile device are the same and only the phone function of the first mobile device is usable, according to an exemplary embodiment;

[83] FIG. 22E is a timing diagram of a method of performing a mobile communication function by the second mobile device, when the device ID information of the first mobile device and the device ID information of the second mobile device are the same and only the phone function of the second mobile device is usable, according to an exemplary embodiment;

[84] FIG. 22F is a timing diagram of a method of performing a mobile communication function by the first mobile device, when the device ID information of the first mobile device and the device ID information of the second mobile device are the same and only the phone function of the second mobile device is usable, according to an exemplary embodiment;

[85] FIG. 23 is a block diagram of the second mobile device configured to share a first phone number of the first mobile device on the mobile communication system, according to an exemplary embodiment;

[86] FIG. 24 is a flowchart of a method of providing a mobile communication service using the second mobile device sharing the first phone number of the first mobile device, according to an exemplary embodiment;

[87] FIG. 25 is a diagram for describing synchronizing recent call histories between the first mobile device and the second mobile device, according to an exemplary embodiment;

[88] FIG. 26 is a flowchart of a method of synchronizing recent call histories when the first mobile device and the second mobile device are separated from each other, according to an exemplary embodiment;

[89] FIG. 27 is a table of a database of recent call histories stored in a device, according to an exemplary embodiment;

WO 2016/018017 PCT/KR2015/007785 [90] FIG. 28 is a flowchart of a method of synchronizing recent call histories when the first mobile device and the second mobile device are linked with each other, according to an exemplary embodiment;

[91] FIG. 29 is a diagram for describing a mobile communication system including a wearable device, according to an exemplary embodiment;

[92] FIG. 30 is a timing diagram of a method of performing a phone call by a wearable device of a standalone type instead of the first mobile device, according to an exemplary embodiment;

[93] FIG. 31 is a timing diagram of a method of performing a phone call when the wearable device is unable to receive a call, according to an exemplary embodiment;

[94] FIG. 32 is a timing diagram of a method of performing a phone call by the first mobile device connected to a wearable device of a companion type, according to an exemplary embodiment;

[95] FIG. 33 is a timing diagram of a method of receiving a call made to the first mobile device by the wearable device of the companion type, according to an exemplary embodiment;

[96] FIG. 34 is a timing diagram of a method of performing a phone call by the wearable device of the standalone type instead of the second mobile device that is a card-type phone, according to an exemplary embodiment;

[97] FIG. 35 is a timing diagram of a method of performing a phone call instead of the second mobile device when the wearable device is unable to receive a call, according to an exemplary embodiment;

[98] FIG. 36 is a timing diagram of a method of performing a phone call by the second mobile device connected to the wearable device of the companion type, according to an exemplary embodiment; and [99] FIG. 37 is a timing diagram of a method of receiving a call made to the second mobile device by the wearable device of the companion type, according to an exemplary embodiment.

Mode for the Invention [100] Certain exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, one or more exemplary embodiments may be embodied in many different forms, and should not be construed as being limited to the exemplary embodiments set forth herein. Rather, the exemplary embodiments described herein are provided so that this disclosure will be thorough and complete, and will fully convey the concept of one or more exemplary embodiments to those of ordinary skill in the art. In the following description, well-known functions or constructions may not be described in detail since they would obscure the description of

WO 2016/018017

PCT/KR2015/007785 one or more exemplary embodiments with unnecessary detail, and like reference numerals in the drawings denote like or similar elements throughout the specification.

[101] In the specification, when a region is connected to another region, the regions may not only be directly connected, but may also be electrically connected via another device therebetween. Also, when a region includes an element, the region may further include other elements.

[102] As used herein, the term and/or includes any and all combinations of one or more of the associated listed items. Expressions such as at least one of when preceding a list of elements, modify the entire list of elements and do not modify the individual elements of the list.

[103] In the specification, performing of a phone call includes both receiving a call and making a call.

[104] Hereinafter, one or more exemplary embodiments will be described in detail with reference to accompanying drawings.

[105] FIG. 1 is a diagram for describing a mobile communication system 1 in which different mobile devices make a call using a same phone number, according to an exemplary embodiment.

[106] Referring to FIG. 1, the mobile communication system 1 includes a server 10 of a mobile carrier, a first mobile device 20 of a user A, a second mobile device 30 of the user A, and a mobile device 40 of a user B. In the mobile communication system 1, the first mobile device 20, the second mobile device 30, and the mobile device 40 may each be a device having a mobile communication function, such as a smart phone, a tablet device, or a personal digital assistant (PDA). For example, the first and second mobile devices 20 and 30 may be two types of device. Hereinafter, for example, it is assumed that the first mobile device 20 is a smart phone and the second mobile device 30 is a card-type phone, but one or more exemplary embodiments are not limited thereto. The card-type phone will be described in detail with reference to accompanying drawings.

[107] The user A may own the first mobile device 20 that is a smart phone and the second mobile device 30 that is a card-type phone. In the mobile communication system 1, a phone number of the first mobile device 20 and a phone number of the second mobile device 30 are the same, i.e., +82-10-AAAA-BBBB. In other words, the first mobile device 20 and the second mobile device 30 may share a certain phone number.

[108] Accordingly, when the user B dials +82-10-AAAA-BBBB using the mobile device 40, the user A may talk to the user B using the first mobile device 20 or the second mobile device 30.

[109] The mobile carrier denotes any entity capable of providing mobile communication services, such as SK Telecom and KT in the Republic of Korea, and Verizon Wireless,

WO 2016/018017

PCT/KR2015/007785

AT&T, Sprint Nextel, and T-Mobile USA in the United States of America. The server 10 of the mobile carrier may denote a server operated by the mobile carrier to provide a mobile communication service to consumers.

[110] The server 10 of the mobile carrier may determine that a phone number +82-10-XXXX-XXXX is currently assigned to the mobile device 40 of the user B. Also, the server 10 of the mobile carrier may determine that one phone number +82-10-AAAA-BBBB is currently assigned to both the first mobile device 20 and the second mobile device 30 of the user A.

[111] When the mobile device 40 assigned with the phone number +82-10-XXXX-XXXX calls the phone number +82-10-AAAA-BBBB, the server 10 of the mobile carrier may relay a phone call to the first mobile device 20 or the second mobile device 30 assigned with the phone number +82-10-AAAA-BBBB.

[112] In other words, the first and second mobile devices 20 and 30 may both perform a mobile communication function by being subscribed to the mobile communication system 1, without having to be assigned different phone numbers by the server 10 of the mobile carrier. Meanwhile, in FIG. 1, the number of mobile devices owned by the user A is two, i.e., the first and second mobile devices 20 and 30, but this is only an example, and the user A may own two or more mobile devices having the same phone number.

[113] FIG. 2 is a diagram of the second mobile device 30 of the user A, according to an exemplary embodiment.

[114] Referring to FIG. 2, the second mobile device 30 may be a card-type phone having a different shape from a smart phone. The card-type phone may denote a mobile device having a mobile communication function like a smart phone, while having an ultraslim or ultra-thin shape like a credit card or a transportation card. In other words, like a smart phone, the card-type phone may be assigned with a phone number and perform a phone call with another phone through the mobile communication system 1. For example, since only subminiature modules are mounted on the card-type phone such that the card-type phone is ultra-slim, the card-type phone may only perform simple functions, such as a phone function or input/output functions, from among various functions of a smart phone, but one or more exemplary embodiments are not limited thereto.

[115] The second mobile device 30 realized as the card-type phone may include, for example, a display 311, e.g., a display unit, and an input interface 313, e.g., an input unit, on a front surface.

[116] The display 311 may display information input through the input interface 313. For example, the display 311 may display numbers input through a keypad of the input interface 313, a contact list stored in the second mobile device 30, or caller information

WO 2016/018017

PCT/KR2015/007785 of a received phone call. The display device 311 may perform a function of displaying various types of information processed by the second mobile device 30.

[117] The input interface 313 may be a keypad having physical buttons. The input interface 313 may be a keypad including, as non-limiting examples, number buttons, a call connection button, and a call termination button, and the like.

[118] FIG. 3 is a diagram of the second mobile device 30 of the user A, according to another exemplary embodiment.

[119] Referring to FIG. 3, the second mobile device 30 of FIG. 3 may include a touch screen 315 on a front surface. The second mobile device 30 of FIG. 3 is realized as a card-type phone that includes the touch screen 315 in which functions of the display 311 and the input interface 313 are integrated.

[120] Accordingly, the second mobile device 30 of FIG. 3 realized as the card-type phone may receive a number or a character via a soft keyboard displayed on the touch screen 315, and may display various types of information processed by the second mobile device 30, such as a contact list or caller information of a received phone call, through the touch screen 315.

[121] A card-type phone is not limited to the above description, and may be realized with various elements and features.

[122] FIG. 4 is a block diagram of the second mobile device 30, according to an exemplary embodiment.

[123] Referring to FIG. 4, the second mobile device 30 includes a user interface (UI) 310, e.g., a UI unit, a controller 320, a communicator 330, e.g., a communication unit, a memory 340, e.g., a storage or a memory unit, and a subscriber identity module (SIM) 350. The second mobile device 30 according to one or more exemplary embodiments may include additional hardware components, or may be missing of some the hardware components shown in FIG. 4. Meanwhile, the second mobile device 30 may be the card-type phone described above, but is not limited thereto.

[124] The UI 30 may be a hardware used by the user A to input data to control the second mobile device 30. For example, the UI 310 may be a keypad, a dome switch, a touch screen (a contact capacitance type, a pressure resistance film type, an infrared ray detecting type, a surface ultrasonic conducting type, an integral tension measuring type, or a Piezo-effect type), a jog wheel, or a jog switch, but is not limited thereto.

[125] The UI 310 may include the display 311, the input interface 313, and the touch screen 315 described above with reference to FIGS. 2 and 3. In addition, the UI 310 may include an interface, e.g., an interfacing unit, for notifying the user A about information processed by the second mobile device 30, such as a speaker or a buzzer outputting an audio signal or a voice signal, or a vibration motor outputting a vibration signal. For example, the UI 310 may receive inputs of the user A by providing UI

WO 2016/018017

PCT/KR2015/007785 screens for setting various functions, such as a popup Ul for activating or deactivating a phone function of the second mobile device 30, a popup Ul for activating or deactivating a two-phone mode, and a popup Ul for activating or deactivating a short-range wireless communication function.

[126] The controller 320 may control overall operations of the second mobile device 30. The controller 320 may execute programs stored in the memory 340 to control functions and operations of the Ul 310, the communicator 330, the memory 340, and the SIM 350. The controller 320 may activate the phone function of the second mobile device 30 after determining whether the phone function of the first mobile device 20 is deactivated, and also, control the communicator 330 to transmit a SIM information transmit request or a SIM information use request to the server 10 of the mobile carrier.

[127] The communicator 330 may include at least one hardware component enabling the second mobile device 30 to be connected to another mobile device, such as the mobile device 40 of FIG. 1, or the server 10 of the mobile carrier wirelessly or via wires. For example, the communicator 330 may include a short-range wireless communication module and a mobile communication module.

[128] The short-range wireless communication module of the communicator 330 may include a Bluetooth communication module, a Bluetooth low energy (BLE) communication module, a near field communication (NFC) module, a Wi-Fi communication module, a Wi-Fi direct (WFD) communication module, a Zigbee communication module, an infrared data association (IrDA) communication module, or an ultra wideband (UWB) communication module, but is not limited thereto.

[129] The mobile communication module of the communicator 330 is a module for performing a mobile communication with another mobile device through a base station provided by the mobile carrier according to any one of various communication methods, such as 2G mobile communication, 3G mobile communication, and 4G mobile communication, on the mobile communication system 1 of FIG. 1, and may be a module for receiving data in any type according to a transmission and reception of a voice call, a video call, or a text/multimedia message. For example, the communicator 330 may receive SIM information from the server 10 of the mobile carrier of FIG. 1.

[130] When the phone function of the second mobile device 30 is activated, the communicator 330 may communicate various types of information with the server 10 of the mobile carrier or other mobile devices, such as the first mobile device 20 and the mobile device 40, such that the second mobile device 30 performs the mobile communication function. For example, the communicator 330 may transmit the SIM information transmit request or the SIM information use request to the server 10 of the mobile carrier. Also, the communicator 330 may exchange the SIM information with

WO 2016/018017

PCT/KR2015/007785 the first mobile device 20, and receive various types of information about the first mobile device, such as an activated state of the phone function of the first mobile device 20, from the first mobile device 20.

[131] The memory 340 may store programs for processes and controls of the controller 320, and store data input to or output from the second mobile device 30. For example, the memory 340 may store device identification (ID) information, contact information, text message information, credit card information, or transportation card information of the second mobile device 30. The device ID information may include a serial number and an IMEI of the second mobile device 30, which are intrinsic to the second mobile device 30, and may also include various types of information, such as a model number and manufacturer information of the second mobile device 30.

[132] The memory 340 may include at least one type of storage medium from among a flash memory type memory, a hard disk type memory, a multimedia card micro type memory, a card type memory (for example, a secure digital (SD) memory or an extreme digital (XD) memory), a random access memory (RAM), a static random access memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, and an optical disk.

[133] The SIM 350 is a module that stores the SIM information including information related to a mobile communication service provided by the mobile carrier, such as an integrated circuit card identifier (ICCID), an international mobile subscriber identity (IMSI), an authentication key, and a location area identity. The SIM 350 may be a downloadable SIM type module that stores the SIM information received from the server 10 of the mobile carrier. For example, the SIM 350 may receive, from the server 10, and store SIM information including subscription information of a certain phone number registered with the mobile communication system 1. One or more exemplary embodiments are not limited thereto, and, alternatively, the SIM 350 may be a module that reads and stores information stored in a SIM card or a universal SIM (USIM) card when the SIM card or the USIM card is inserted into the SIM 350.

[134] FIG. 5 is a diagram for describing device ID information and SIM information, which are stored in each of the first mobile device 20 and the second mobile device 30, according to an exemplary embodiment.

[135] Referring to FIG. 5, a memory 510 of the first mobile device 20 may store device ID information about the first mobile device 20. The device ID information may include a serial number and an international mobile equipment identity (IMEI) of the first mobile device 20, which are intrinsic to the first mobile device 20. Also, the device ID information may include various types of information, such as a model number and manufacturer information of the first mobile device 20. Here, the serial number and the

WO 2016/018017 PCT/KR2015/007785

IMEI of the first mobile device 20 are intrinsic to the first mobile device as described above, and generally have combinations of different numbers according to mobile devices.

[136] A SIM 520 of the first mobile device 20 is a downloadable SIM, and may include phone number information and an ICCID. Here, the ICCID stored in the SIM 520 of the first mobile device 20 may correspond to information mapped to a certain phone number assigned by the mobile carrier. Accordingly, the server 10 of FIG. 1 of the mobile carrier may identify the user A of the first mobile device 20 and the phone number of the first mobile device 20 using the ICCID stored in the SIM 520.

[137] The SIM 350 of the second mobile device 30 is a downloadable SIM, and may include phone number information and an ICCID. Here, the ICCID stored in the SIM 350 of the second mobile device 30 may correspond to information mapped to a certain phone number assigned by the mobile carrier. Accordingly, the server 10 of FIG. 1 of the mobile carrier may identify the user A of the second mobile device 30 and the phone number of the second mobile device 30 using the ICCID stored in the SIM 350.

[138] As described above with reference to FIG. 1, in the mobile communication system 1, the phone number +10-82-AAAA-BBBB may be assigned to the first and second mobile devices 20 and 30. Also, the ICCID of the SIM 350 or 520 is mapped to a certain phone number. Accordingly, the server 10 of the mobile carrier may manage the ICCID of the SIM 350 and the ICCID of the SIM 520 as the same. Alternatively, the server 10 of the mobile carrier may manage the ICCID of the SIM 350 and the ICCID of the SIM 520 as different from each other.

[139] Hereinafter, for convenience of description, the device ID information and the SIM information of the first mobile device 20 will be respectively referred to as first device ID information and first SIM information, and the device ID information and the SIM information of the second mobile device 30 will be respectively referred to as second device ID information and second SIM information.

[140] FIG. 6 is a timing diagram of a method of making a call from the first mobile device 20 and the second mobile device 30, which have the same phone number and are owned by the user A, to the mobile device 40 of the user B, on the mobile communication system 1, according to an exemplary embodiment.

[141] Referring to FIG. 6, the phone number +10-82-AAAA-BBBB may be assigned to the first and second mobile devices 20 and 30 by the server 10 of the mobile carrier.

[142] In operation 610, the server 10 of the mobile carrier registers the first mobile device 20, as a main mobile device.

[143] In operation 620, the server 10 of the mobile device registers the second mobile device 30, as a sub mobile device.

[144] In operation 630, the user B requests a phone call to the phone number

WO 2016/018017

PCT/KR2015/007785 +10-82-AAAA-BBBB using the mobile device 40.

[145] In operation 640, the server 10 of the mobile carrier identifies a list of the first and second mobile devices 20 and 30 owned by the user A.

[146] In operation 650, if the user A activated the phone function of the first mobile device 20 that is the main mobile device, the server 10 of the mobile carrier may transmit a request of the mobile device 40 for the phone call to the first mobile device 20. However, if the user A activated the phone function of the second mobile device 30 that is the sub mobile device, the server 10 of the mobile carrier may transmit the request of the mobile device 40 for the phone call to the second mobile device 30.

[147] In other words, when the same phone number +10-82-AAAA-BBBB is assigned to the first and second mobile devices 20 and 30, the user A may talk to the user B using any one of the first and second mobile devices 20 and 30.

[148] FIG. 7 is a diagram for describing the server 10 of the mobile carrier managing mobile devices owned by the user A, according to an exemplary embodiment.

[149] Referring to FIG. 7, the server 10 of the mobile carrier may identify the first and second mobile devices 20 and 30 owned by the user A. The server 10 of the mobile carrier may identify the first and second mobile devices 20 and 30 using the first and second device ID information and first and second SIM information stored in the first and second mobile devices 20 and 30. As described above, the first mobile device 20 may be a smart phone and the second mobile device 30 may be a card type phone. Accordingly, the user A may register the first mobile device 20, which has greater functionality than the second mobile device 30, as a main mobile device. Also, the user A may register the second mobile device 30 as a sub mobile device. The server 10 of the mobile carrier may identify and manage the main mobile device and the sub mobile device using the first and second device ID information of the first and second mobile devices 20 and 30.

[150] FIG. 8A is a diagram for describing linking, e.g., connecting or combining, the first mobile device 20 and the second mobile device 30 in a two-phone mode, according to an exemplary embodiment, and FIG. 8B is a diagram for describing separating, e.g., disconnecting, the first mobile device 20 and the second mobile device 30 in the twophone mode, according to an exemplary embodiment.

[151] The two-phone mode may be a mode for using two different mobile devices assigned with the same phone number, such as the first and second mobile devices 20 and 30 assigned with the phone number +10-82-AAAA-BBBB, on the mobile communication system 1 of FIG. 1. Here, the two-phone mode is a term used to indicate that two devices exist as described in one or more exemplary embodiments. Thus, the term two-phone mode may be replaced by another term, such as an N-phone mode or a multi-phone mode, when N devices having the same phone number are to be used on

WO 2016/018017

PCT/KR2015/007785 the mobile communication system 1 of FIG. 1, wherein N is a natural number greater than or equal to 2. In other words, the term two-phone mode may be variously changed and is not limited thereto.

[152] Referring to FIG. 8A, the first and second mobile devices 20 and 30 may be linked to each other by establishing a connection through short-range wireless communication. Examples of the short-range wireless communication include wireless communications, such as a Bluetooth communication, an NFC, and a Wi-Fi communication.

[153] With regard to the first mobile device 20, when the two-phone mode is to be activated, the first mobile device 20 may be linked to the second mobile device 30 through the short-range wireless communication, using a UI 810 inquiring whether to connect to the second mobile device 30. Similarly, with regard to the second mobile device 30, when the two-phone mode is to be activated, the second mobile device 30 may be linked to the first mobile device 20 through the short-range wireless communication, using a UI 820 inquiring whether to connect to the first mobile device 20.

[154] Referring to FIG. 8B, with regard to the first mobile device 20, when the two-phone mode is activated, the first mobile device 20 may be disconnected from the second mobile device 30 using a UI 830 inquiring whether to be disconnected from the second mobile device 30. Similarly, with regard to the second mobile device 30, when the two-phone mode is activated, the second mobile device 30 may be disconnected from the first mobile device 20 using a UI 840 inquiring whether to be disconnected from the first mobile device 20. Separating the first and second mobile devices 20 and 30 by disconnection does not mean that the two-phone mode is deactivated, but may mean that the user A wants to use either one of the first and second mobile devices 20 and 30 while the two-phone mode is activated.

[155] FIG. 9 is a diagram for describing manually activating the phone function of the first mobile device 20 or the phone function of the second mobile device 30 in the twophone mode, according to an exemplary embodiment.

[156] In the two-phone mode, the user A may want to make a call to another mobile device using one of the first and second mobile devices 20 and 30. In other words, in the twophone mode, the user A may input information for activating the phone function of one of the first and second mobile devices 20 and 30 to select the one of the first and second mobile devices 20 and 30. For example, referring to FIG. 9, the user A may input information for activating the phone function of the first mobile device 20 using a UI 910 inquiring whether to activate the phone function of the first mobile device 20, which is displayed on the first mobile device 20. Alternatively, the user A may input information for activating the phone function of the second mobile device 30 using a UI 920 inquiring whether to activate the phone function of the second mobile device 30, which is displayed on the second mobile device 30.

WO 2016/018017 PCT/KR2015/007785 [157] When the phone function of the first mobile device 20 is activated, the phone function of the second mobile device 30 may be automatically deactivated. Similarly, when the phone function of the second mobile device 30 is activated, the phone function of the first mobile device 20 may be automatically deactivated.

[158] FIG. 10A is a flowchart of a method of activating the phone function of the first mobile device 20 or the phone function of the second mobile device 30, according to an exemplary embodiment.

[159] In operation 1001, the first mobile device 20 determines whether the two-phone mode is set. If the two-phone mode is set, operation 1002 is performed. If the twophone mode is not set, the method ends since it is not required to determine which one of the phone functions of the first and second mobile devices 20 and 30 is to be activated.

[160] In operation 1002, the first mobile device 20 determines whether the phone function of the first mobile device 20 is usable. For example, the phone function of the first mobile device 20 may not operate normally due to any one of various reasons, such as a malfunction or shutdown of the mobile communication module included in the first mobile device 20. Thus, in operation 1002, the first mobile device 20 determines whether the phone function operates normally. If the phone function is usable, operation 1003 is performed. If the phone function is not usable, operation 1008 is performed.

[161] In operation 1003, the first mobile device 20 determines whether automatic activation of the phone function is set. If the two-phone mode is set, the first mobile device 20 may be set as default so that the phone function of the first mobile device 20 is activated prior to that of the second mobile device 30. In other words, the first mobile device 20 may be set such that the phone function is automatically activated in the two-phone mode, instead of the phone function being manually activated via the UI 910 as described above with reference to FIG. 9. If the automatic activation of the phone function is set, operation 1005 is performed. If the automatic activation of the phone function is not set, operation 1004 is performed.

[162] In operation 1004, the first mobile device 20 determines whether manual activation of the phone function is set. The first mobile device 20 determines whether information for manually activating the phone function is input. If the manual activation of the phone function is set, operation 1005 is performed. If the manual activation of the phone function is not set, operation 1008 is performed.

[163] In operation 1005, the first mobile device 20 activates the phone function of the first mobile device 20. The phone function of the second mobile device 30 may be automatically deactivated.

[164] In operation 1006, the second mobile device 30 determines whether the two-phone

WO 2016/018017

PCT/KR2015/007785 mode is set. If the two-phone mode is set, operation 1007 is performed. If the twophone mode is not set, the method ends since it is not required to determine which one of the phone functions of the first and second mobile devices 20 and 30 is to be activated.

[165] In operation 1007, the second mobile device 30 determines whether the phone function of the second mobile device 30 is usable. For example, the phone function of the second mobile device 30 may not operate normally due to any one of various reasons, such as a malfunction or shutdown of the mobile communication module included in the second mobile device 30. Thus, in operation 1007, the second mobile device 30 determines whether the phone function operates normally. If the phone function is usable, operation 1008 is performed. If the phone function is not usable, operation 1003 is performed.

[166] In operation 1008, the second mobile device 30 determines whether automatic activation of the phone function is set. The second mobile device 30 may be set as default so that the phone function of the second mobile device 30 is activated prior to that of the first mobile device 20. In other words, the second mobile device 30 may be set such that the phone function is automatically activated in the two-phone mode, instead of the phone function being manually activated via the UI 920 as described above with reference to FIG. 9. If the automatic activation of the phone function is set, operation 1010 is performed. If the automatic activation of the phone function is not set, operation 1009 is performed.

[167] In operation 1009, the second mobile device 30 determines whether manual activation of the phone function is set. The second mobile device 30 determines whether information for manually activating the phone function is input. If the manual activation of the phone function is set, operation 1010 is performed. If the manual activation of the phone function is not set, operation 1003 is performed.

[168] In operation 1010, the second mobile device 30 activates the phone function of the second mobile device 30. The phone function of the first mobile device 20 may be automatically deactivated.

[169] FIG. 10B is a diagram for describing a case in which the phone function of the first mobile device 20 is activated from among the first mobile device 20 and the second mobile device 30, which are linked to each other in the two-phone mode, according to an exemplary embodiment.

[170] Referring to FIG. 10B, the first mobile device 20 may display a UI 1020 indicating that the phone function is activated when the phone function of the first mobile device 20 is activated according to operation 1005 of FIG. 10A.

[171] FIG. 10C is a diagram for describing a case in which the phone function of the second mobile device 30 is activated from among the first mobile device 20 and the

WO 2016/018017

PCT/KR2015/007785 second mobile device 30, which are linked to each other in the two-phone mode, according to an exemplary embodiment.

[172] Referring to FIG. 10C, the second mobile device 30 may display a UI 1030 indicating that the phone function is activated when the phone function of the second mobile device 30 is activated according to operation 1010 of FIG. 10A.

[173] FIG. 10D is a diagram for describing a case in which the phone function of the first mobile device 20 is activated from among the first mobile device 20 and the second mobile device 30, which are separated from each other in the two-phone mode, according to an exemplary embodiment.

[174] Referring to FIG. 10D, the first mobile device 20 may display a UI 1040 indicating that the phone function is activated when the phone function of the first mobile device 20 is activated according to operation 1005 of FIG. 10A.

[175] FIG. 10E is a diagram for describing a case in which the phone function of the second mobile device 30 is activated from among the first mobile device 20 and the second mobile device 30, which are separated from each other in the two-phone mode, according to an exemplary embodiment.

[176] Referring to FIG. 10E, the second mobile device 30 may display a UI 1050 indicating that the phone function is activated when the phone function of the second mobile device 30 is activated according to operation 1010 of FIG. 10A.

[177] FIG. 1 IA is a diagram for describing the device ID information and the SIM information, which are stored in each of the first mobile device 20 and the second mobile device 30, according to another exemplary embodiment.

[178] Referring to FIG. 1 IA, the same phone number +82-10-AAAA-BBBB may be assigned to the first and second mobile devices 20 and 30. In the first device ID information of the first mobile device 20, the IMEI of the first mobile device 20 may have a value 35 abcdef 465607 8. The ICCID of the first SIM information of the first mobile device 20 may have a value abed efgh 0710 9991 604. Meanwhile, in the second device ID information of the second mobile device 30, the IMEI of the second mobile device 30 may have a value 23 abcxyz 576501 1, which is different from that of the IMEI of the first device ID information. Also, the ICCID of the second SIM information of the second mobile device 30 may have a value abed efgh 0710 9991 604, which is the same as that of the ICCID of the first SIM information.

[179] Referring to FIG. 1 IA, the first and second mobile devices 20 and 30 assigned with the same phone number +82-10-AAAA-BBBB have the same ICCID but different IMEI.

[180] FIG. 1 IB is a diagram for describing the device ID information and the SIM information, which are stored in each of the first mobile device 20 and the second mobile device 30, according to another exemplary embodiment.

WO 2016/018017 PCT/KR2015/007785 [181] Referring to FIG. 1 IB, the same phone number +82-10-AAAA-BBBB may be assigned to the first and second mobile devices 20 and 30. In the first device ID information of the first mobile device 20, the IMEI of the first mobile device 20 may have a value 35 abcdef 465607 8. The ICCID of the first SIM information of the first mobile device 20 may have a value abed efgh 0710 9991 604. Meanwhile, in the second device ID information of the second mobile device 30, the IMEI of the second mobile device 30 may have a value 23 abcxyz 576501 1, which is different from that of the IMEI of the first device ID information. The ICCID of the second SIM information of the second mobile device 30 may have a value abed hgfe 0710 9991 604, which is the different from that of the ICCID of the first SIM information.

[182] Referring to FIG. 1 IB, the first and second mobile devices 20 and 30 assigned with the same phone number +82-10-AAAA-BBBB have the different ICCID and different IMEI.

[183] In the exemplary embodiments described with reference to FIGS. 11A and 1 IB, the SIMs 520 and 350 included in the first mobile device 20 and the second mobile device 30 may have the same ICCID or different ICCID. Nevertheless, in the exemplary embodiments of FIGS. 11A and 11B, the same phone number +82-10-AAAA-BBBB may be assigned to the first and second mobile devices 20 and 30.

[184] FIGS. 12A through 20D are diagrams related to the exemplary embodiments of FIGS. HAand 11B.

[185] FIGS. 12A through 14D are diagrams for describing various exemplary embodiments according to a first scenario in which the first and second SIM information is not initially respectively stored in the SIMs 520 and 350 of the first and second mobile devices 20 and 30, but is received from the server 10 of the mobile carrier when necessary such that the mobile communication function is performed. The first scenario may be related to various exemplary embodiments in which the first or second mobile device 20 or 30 requests the server 10 of the mobile carrier to transmit or use the first or second SIM information when necessary.

[186] FIGS. 15 through 17D are diagrams for describing various exemplary embodiments according to a second scenario in which the first and second SIM information is initially respectively stored in the SIMs 520 and 350 of the first and second mobile devices 20 and 30, and the mobile communication function is performed as the first or second mobile device 20 or 30 transmits a request to use the first or second SIM information to the server 10 of the mobile carrier when necessary. The second scenario may be related to various exemplary embodiments in which the first or second mobile device 20 or 30 transmits only a request to use the first or second SIM information to the server 10 of the mobile carrier when necessary.

[187] FIGS. 18 through 20D are diagrams for describing various exemplary embodiments

WO 2016/018017

PCT/KR2015/007785 according to a third scenario in which SIM information is initially stored in any one of the SIMs 520 and 350 of the first and second mobile devices 20 and 30, and the mobile communication function is performed as the first and second mobile devices 20 and 30 exchanges the SIM information when necessary. The third scenario may be related to various exemplary embodiments in which the first and second mobile devices 20 and 30 exchange the SIM information when necessary.

[188] FIGS. 12A and 12B are diagrams for describing a concept of the first scenario in which the first mobile device 20 and the second mobile device 30, which do not store SIM information, receive SIM information from the server 10 of the mobile carrier and transmit a SIM use request, according to an exemplary embodiment.

[189] In FIGS. 12A and 12B, the first and second SIM information are not initially stored in the SIMs 520 and 350 of the first and second mobile devices 20 and 30, respectively.

[190] Referring to FIG. 12A, when the phone function of the first mobile device 20 is requested to be activated in the two-phone mode, the first mobile device 20 requests the server 10 of the mobile carrier to transmit the first SIM information. Accordingly, the server 10 of the mobile carrier transmits the first SIM information to the first mobile device 20, and the first mobile device 20 stores the first SIM information in the SIM 520. Then, the first mobile device 20 transmits a request to use the first SIM information to the server 10 of the mobile carrier. When the server 10 of the mobile carrier approves the request, the first mobile device 20 may perform the mobile communication function in the two-phone mode.

[191] Referring to FIG. 12B, when the phone function of the second mobile device 30 is requested to be activated in the two-phone mode, the second mobile device 30 requests the server 10 of the mobile carrier to transmit the second SIM information. Accordingly, the server 10 of the mobile carrier transmits the second SIM information to the second mobile device, and the second mobile device 30 stores the second SIM information in the SIM 350. Then, the second mobile device 30 transmits a request to use the second SIM information to the server 10 of the mobile carrier. When the server 10 of the mobile carrier approves the request, the second mobile device 30 may perform the mobile communication function in the two-phone mode.

[192] FIG. 13A is a timing diagram of a method of performing the mobile communication function by the first mobile device 20, according to a SIM information transmit request and a SIM information use request of the first mobile device 20, based on the first scenario while the first mobile device 20 and the second mobile device 30 are linked to each other, according to an exemplary embodiment.

[193] In operation 1301, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

WO 2016/018017 PCT/KR2015/007785 [194] In operation 1302, the first and second mobile devices 20 and 30 are linked with each other as a connection is established through short-range wireless communication.

[195] In operation 1303, the first mobile device 20 activates the phone function. The first mobile device 20 may activate the phone function manually or automatically. The activating of the phone function of the first mobile device 20 may mean that the user A wants to make a call using the first mobile device 20 that is a main mobile device.

[196] In operation 1304, the first mobile device 20 requests the server 10 of the mobile carrier to transmit the first SIM information.

[197] In operation 1305, the server 10 of the mobile carrier transmits the first SIM information to the first mobile device 20.

[198] In operation 1306, the first mobile device 20 stores the first SIM information in the SIM 520.

[199] In operation 1307, the first mobile device 20 transmits a request to use the first SIM information to the server 10 of the mobile carrier.

[200] In operation 1308, the server 10 of the mobile carrier approves the request to use the first SIM information.

[201] In operation 1309, when another mobile device, for example, the mobile device 40 of the user B of FIG. 1, requests a phone call to the phone number +82-10-AAAA-BBBB, the server 10 of the mobile carrier tries a call connection to the first mobile device 20. Since the phone function is not activated and there is no SIM information, a phone call is not connected to the second mobile device 30.

[202] FIG. 13B is a timing diagram of a method of performing the mobile communication function by the second mobile device 30, according to a SIM information transmit request and a SIM information activation request of the second mobile device 30, based on the first scenario while the first mobile device 20 and the second mobile device 30 are linked to each other, according to an exemplary embodiment.

[203] In operation 1311, the first mobile device 20 and the second mobile device 30 set a two-phone mode.

[204] In operation 1312, the first and second mobile devices 20 and 30 are linked with each other as a connection is established through short-range wireless communication.

[205] In operation 1313, the second mobile device 30 activates the phone function. The second mobile device 30 may activate the phone function manually or automatically. The activating of the phone function of the second mobile device 30 may mean that the user A wants to make a call using the second mobile device 30 that is a sub mobile device.

[206] In operation 1314, the second mobile device 30 requests the server 10 of the mobile carrier to transmit the second SIM information.

[207] In operation 1315, the server 10 of the mobile carrier transmits the second SIM in26

WO 2016/018017 PCT/KR2015/007785 formation to the second mobile device 30.

[208] In operation 1316, the second mobile device 30 stores the second SIM information in the SIM 350.

[209] In operation 1317, the second mobile device 30 transmits a request to use the second SIM information to the server 10 of the mobile carrier.

[210] In operation 1318, the server 10 of the mobile carrier approves the request to use the second SIM information.

[211] In operation 1319, when another mobile device, for example, the mobile device 40 of the user B of FIG. 1, requests a phone call to the phone number +82-10-AAAA-BBBB, the server 10 of the mobile carrier tries a call connection to the second mobile device 30. Since the phone function is not activated and there is no SIM information, a phone call is not connected to the first mobile device 20.

[212] FIG. 13C is a timing diagram of a method of performing the mobile communication function by the first mobile device 20, according to a SIM information transmit request of the second mobile device 30 and a SIM information use request of the first mobile device 20, based on the first scenario while the first mobile device 20 and the second mobile device 30 are linked to each other, according to an exemplary embodiment.

[213] In operation 1321, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

[214] In operation 1322, the first mobile device 20 and the second mobile device 30 are linked with each other by establishing a connection through short-range wireless communication.

[215] In operation 1323, the first mobile device 20 activates the phone function. The first mobile device 20 may activate the phone function manually or automatically. The activating of the phone function of the first mobile device 20 may mean that the user A wants to make a call using the first mobile device 20 that is a main mobile device.

[216] In operation 1334, the second mobile device 30 requests the server 10 of the mobile carrier to transmit the first SIM information to the first mobile device 20.

[217] In operation 1325, the server 10 of the mobile carrier transmits the first SIM information to the first mobile device 20.

[218] In operation 1326, the first mobile device 20 stores the first SIM information in the SIM 520.

[219] In operation 1327, the first mobile device 20 transmits a request to use the first SIM information to the server 10 of the mobile carrier.

[220] In operation 1328, the server 10 of the mobile carrier approves the request to use the first SIM information.

[221] In operation 1329, when another mobile device, for example, the mobile device 40 of the user B of FIG. 1, requests a phone call to the phone number

WO 2016/018017

PCT/KR2015/007785 +82-10-AAAA-BBBB, the server 10 of the mobile carrier tries a call connection to the first mobile device 20. Since the phone function is not activated and there is no SIM information, a phone call is not connected to the second mobile device 30.

[222] FIG. 13D is a timing diagram of a method of performing the mobile communication function by the second mobile device 30, according to a SIM information transmit request of the first mobile device 20 and a SIM information use request of the second mobile device 30, based on the first scenario while the first mobile device 20 and the second mobile device 30 are linked to each other, according to an exemplary embodiment.

[223] In operation 1331, the first mobile device 20 and the second mobile device 30 set a two-phone mode.

[224] In operation 1332, the first and second mobile devices 20 and 30 are linked with each other as a connection is established through short-range wireless communication.

[225] In operation 1333, the second mobile device 30 activates the phone function. The second mobile device 30 may activate the phone function manually or automatically. The activating of the phone function of the second mobile device 30 may mean that the user A wants to make a call using the second mobile device 30 that is a sub mobile device instead of the first mobile device 20 that is a main mobile device.

[226] In operation 1334, the first mobile device 20 requests the server 10 of the mobile carrier to transmit the second SIM information to the second mobile device 30.

[227] In operation 1335, the server 10 of the mobile carrier transmits the second SIM information to the second mobile device 30.

[228] In operation 1336, the second mobile device 30 stores the second SIM information in the SIM 350.

[229] In operation 1337, the second mobile device 30 transmits a request to use the second SIM information to the server 10 of the mobile carrier.

[230] In operation 1338, the server 10 of the mobile carrier approves the request to use the second SIM information.

[231] In operation 1339, when another mobile device, for example, the mobile device 40 of the user B of FIG. 1, requests a phone call to the phone number +82-10-AAAA-BBBB, the server 10 of the mobile carrier tries a call connection to the second mobile device 30. Since the phone function is not activated and there is no SIM information, a phone call is not connected to the first mobile device 20.

[232] FIG. 14A is a timing diagram of a method of performing the mobile communication function by the first mobile device 20, according to a SIM information transmit request and a SIM information use request of the first mobile device 20, based on the first scenario while the first mobile device 20 and the second mobile device 30 are separated from each other, according to an exemplary embodiment.

WO 2016/018017 PCT/KR2015/007785 [233] In operation 1401, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

[234] In operation 1402, the first and second mobile devices 20 and 30 are linked with each other as a connection is established through short-range wireless communication.

[235] In operation 1403, the first mobile device 20 activates the phone function. The first mobile device 20 may activate the phone function manually or automatically. The activating of the phone function of the first mobile device 20 may mean that the user A wants to make a call using the first mobile device 20 that is a main mobile device.

[236] In operation 1404, the first and second mobile devices 20 and 30 are separated from each other by terminating the connection through the short-range wireless communication.

[237] In operation 1405, the first mobile device 20 requests the server 10 of the mobile carrier to transmit the first SIM information.

[238] In operation 1406, the server 10 of the mobile carrier transmits the first SIM information to the first mobile device 20.

[239] In operation 1407, the first mobile device 20 stores the first SIM information in the SIM 520.

[240] In operation 1408, the first mobile device 20 transmits a request to use the first SIM information to the server 10 of the mobile carrier.

[241] In operation 1409, the server 10 of the mobile carrier approves the request to use the first SIM information.

[242] In operation 1410, when another mobile device, for example, the mobile device 40 of the user B of FIG. 1, requests a phone call to the phone number +82-10-AAAA-BBBB, the server 10 of the mobile carrier tries a call connection to the first mobile device 20. Since the phone function is not activated and there is no SIM information, a phone call is not connected to the second mobile device 30.

[243] FIG. 14B is a timing diagram of a method of performing the mobile communication function by the second mobile device 30, according to a SIM information transmit request and a SIM information use request of the second mobile device 30, based on the first scenario while the first mobile device 20 and the second mobile device 30 are separated from each other, according to an exemplary embodiment.

[244] In operation 1411, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

[245] In operation 1412, the first and second mobile devices 20 and 30 are linked with each other as a connection is established through short-range wireless communication.

[246] In operation 1413, the second mobile device 30 activates the phone function. The second mobile device 30 may activate the phone function manually or automatically. The activating of the phone function of the second mobile device 30 may mean that the

WO 2016/018017

PCT/KR2015/007785 user A wants to make a call using the second mobile device 30 that is a main mobile device instead of the first mobile device 20 that is a main mobile device.

[247] In operation 1414, the first and second mobile devices 20 and 30 are separated from each other by terminating the connection through the short-range wireless communication.

[248] In operation 1415, the second mobile device 20 requests the server 10 of the mobile carrier to transmit the second SIM information.

[249] In operation 1416, the server 10 of the mobile carrier transmits the second SIM information to the second mobile device 30.

[250] In operation 1417, the second mobile device 30 stores the second SIM information in the SIM 350.

[251] In operation 1418, the second mobile device 20 transmits a request to use the second SIM information to the server 10 of the mobile carrier.

[252] In operation 1419, the server 10 of the mobile carrier approves the request to use the second SIM information.

[253] In operation 1420, when another mobile device, for example, the mobile device 40 of the user B of FIG. 1, requests a phone call to the phone number +82-10-AAAA-BBBB, the server 10 of the mobile carrier tries a call connection to the second mobile device 30. Since the phone function is not activated and there is no SIM information, a phone call is not connected to the first mobile device 20.

[254] FIG. 14C is a timing diagram of a method of performing the mobile communication function by the first mobile device 20, according to a SIM information transmit request of the second mobile device 30 and a SIM information use request of the first mobile device 20, based on the first scenario while the first mobile device 20 and the second mobile device 30 are separated from each other, according to an exemplary embodiment.

[255] In operation 1421, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

[256] In operation 1422, the first mobile device 20 and the second mobile device 30 are linked with each other by establishing a connection through short-range wireless communication.

[257] In operation 1423, the first mobile device 20 activates the phone function. The first mobile device 20 may activate the phone function manually or automatically. The activating of the phone function of the first mobile device 20 may mean that the user A wants to make a call using the first mobile device 20 that is a main mobile device.

[258] In operation 1424, the first and second mobile devices 20 and 30 are separated from each other by terminating the connection through the short-range wireless communication.

WO 2016/018017 PCT/KR2015/007785 [259] In operation 1425, the second mobile device 30 requests the server 10 of the mobile carrier to transmit the first SIM information to the first mobile device 20.

[260] In operation 1426, the server 10 of the mobile carrier transmits the first SIM information to the first mobile device 20.

[261] In operation 1427, the first mobile device 20 stores the first SIM information in the SIM 520.

[262] In operation 1428, the first mobile device 20 transmits a request to use the first SIM information to the server 10 of the mobile carrier.

[263] In operation 1429, the server 10 of the mobile carrier approves the request to use the first SIM information.

[264] In operation 1430, when another mobile device, for example, the mobile device 40 of the user B of FIG. 1, requests a phone call to the phone number +82-10-AAAA-BBBB, the server 10 of the mobile carrier tries a call connection to the first mobile device 20. Since the phone function is not activated and there is no SIM information, a phone call is not connected to the second mobile device 30.

[265] FIG. 14D is a timing diagram of a method of performing the mobile communication function by the second mobile device 30, according to a SIM information transmit request of the first mobile device 20 and a SIM information use request of the second mobile device 30, based on the first scenario while the first mobile device 20 and the second mobile device 30 are separated from each other, according to an exemplary em bodiment.

[266] In operation 1431, the first mobile device 20 and the second mobile device 30 set a two-phone mode.

[267] In operation 1432, the first and second mobile devices 20 and 30 are linked with each other as a connection is established through short-range wireless communication.

[268] In operation 1433, the second mobile device 30 activates the phone function. The second mobile device 30 may activate the phone function manually or automatically. The activating of the phone function of the second mobile device 30 may mean that the user A wants to make a call using the second mobile device 30 that is a sub mobile device instead of the first mobile device 20 that is a main mobile device.

[269] In operation 1434, the first and second mobile devices 20 and 30 are separated from each other by terminating the connection through the short-range wireless communication.

[270] In operation 1435, the first mobile device 20 requests the server 10 of the mobile carrier to transmit the second SIM information to the second mobile device 30.

[271] In operation 1436, the server 10 of the mobile carrier transmits the second SIM information to the second mobile device 30.

[272] In operation 1437, the second mobile device 30 stores the second SIM information in

WO 2016/018017 PCT/KR2015/007785 the SIM 350.

[273] In operation 1438, the second mobile device 30 transmits a request to use the second SIM information to the server 10 of the mobile carrier.

[274] In operation 1439, the server 10 of the mobile carrier approves the request to use the second SIM information.

[275] In operation 1440, when another mobile device, for example, the mobile device 40 of the user B of FIG. 1, requests a phone call to the phone number +82-10-AAAA-BBBB, the server 10 of the mobile carrier tries a call connection to the second mobile device 30. Since the phone function is not activated and there is no SIM information, a phone call is not connected to the first mobile device 20.

[276] FIG. 15 is a diagram for describing a concept of the second scenario in which the first mobile device 20 and the second mobile device 30, which pre-store SIM information, transmits a SIM information use request to the server 10 of the mobile carrier, according to an exemplary embodiment.

[277] Referring to FIG. 15, the first and second mobile devices 20 and 30 pre-store the first and second SIM information in the SIMs 520 and 350, respectively. For example, before the two-phone mode is activated, the first and second mobile devices 20 and 30 pre-download the first and second SIM information from the server 10 of the mobile carrier and store the first and second SIM information in the SIMs 520 and 350, respectively. The SIMs 520 and 350 may pre-store the first and second SIM information respectively, regardless of an activation status of the phone functions of the first and second mobile devices 20 and 30.

[278] When the phone function of the first mobile device 20 is requested to be activated in the two-phone mode, the first mobile device 20 transmits a request to use the first SIM information to the server 10 of the mobile carrier. When the server 10 of the mobile carrier approves the request to use the first SIM information, the first mobile device 20 may perform the mobile communication function in the two-phone mode.

[279] When the phone function of the second mobile device 30 is requested to be activated in the two-phone mode, the second mobile device 30 transmits a request to use the second SIM information to the server 10 of the mobile carrier. When the server 10 of the mobile carrier approves the request to use the second SIM information, the second mobile device 30 may perform the mobile communication function in the two-phone mode.

[280] FIG. 16A is a timing diagram of a method of performing the mobile communication function by the first mobile device 20, according to a SIM information use request of the first mobile device 20, based on the second scenario while the first mobile device 20 and the second mobile device 30 are linked to each other, according to an exemplary embodiment.

WO 2016/018017 PCT/KR2015/007785 [281] In operation 1601, the first mobile device 20 stores the first SIM information in the SIM 520. Also, the second mobile device 30 stores the second SIM information in the SIM 350.

[282] In operation 1602, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

[283] In operation 1603, the first and second mobile devices 20 and 30 are linked with each other by establishing a connection through short-range wireless communication.

[284] In operation 1604, the first mobile device 20 activates the phone function. The first mobile device 20 may activate the phone function manually or automatically. The activating of the phone function of the first mobile device 20 may mean that the user A wants to make a call using the first mobile device 20 that is a main mobile device.

[285] In operation 1605, the first mobile device 20 transmits a request to use the first SIM information to the server 10 of the mobile carrier.

[286] In operation 1606, the server 10 of the mobile carrier approves the request to use the first SIM information.

[287] In operation 1607, when another mobile device, for example, the mobile device 40 of the user B of FIG. 1, requests a phone call to the phone number +82-10-AAAA-BBBB, the server 10 of the mobile carrier tries a call connection to the first mobile device 20. Since the second SIM information is not requested to be used, a phone call is not connected to the second mobile device 30.

[288] FIG. 16B is a timing diagram of a method of performing the mobile communication function by the second mobile device 30, according to a SIM information use request of the second mobile device 30, based on the second scenario while the first mobile device 20 and the second mobile device 30 are linked to each other, according to an exemplary embodiment.

[289] In operation 1611, the first mobile device 20 stores the first SIM information in the SIM 520. Also, the second mobile device 30 stores the second SIM information in the SIM 350.

[290] In operation 1612, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

[291] In operation 1613, the first and second mobile devices 20 and 30 are linked with each other by establishing a connection through short-range wireless communication.

[292] In operation 1614, the second mobile device 20 activates the phone function. The second mobile device 20 may activate the phone function manually or automatically. The activating of the phone function of the second mobile device 30 may mean that the user A wants to make a call using the second mobile device 30 that is a sub mobile device instead of the first mobile device 20 that is a main mobile device.

[293] In operation 1615, the second mobile device 30 transmits a request to use the second

WO 2016/018017 PCT/KR2015/007785

SIM information to the server 10 of the mobile carrier.

[294] In operation 1616, the server 10 of the mobile carrier approves the request to use the second SIM information.

[295] In operation 1617, when another mobile device, for example, the mobile device 40 of the user B of FIG. 1, requests a phone call to the phone number +82-10-AAAA-BBBB, the server 10 of the mobile carrier tries a call connection to the second mobile device 30. Since the first SIM information is not requested to be used, a phone call is not connected to the first mobile device 20.

[296] FIG. 16C is a timing of a method of performing the mobile communication function by the first mobile device 20, according to a SIM information use request of the second mobile device 30, based on the second scenario while the first mobile device 20 and the second mobile device 30 are linked to each other, according to an exemplary embodiment.

[297] In operation 1621, the first mobile device 20 stores the first SIM information in the SIM 520. Also, the second mobile device 30 stores the second SIM information in the SIM 350.

[298] In operation 1622, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

[299] In operation 1623, the first and second mobile devices 20 and 30 are linked with each other by establishing a connection through short-range wireless communication.

[300] In operation 1624, the first mobile device 20 activates the phone function. The first mobile device 20 may activate the phone function manually or automatically. The activating of the phone function of the first mobile device 20 may mean that the user A wants to make a call using the first mobile device 20 that is a main mobile device.

[301] In operation 1625, the second mobile device 30 transmits a request to use the first SIM information to the server 10 of the mobile carrier.

[302] In operation 1626, the server 10 of the mobile carrier approves the request to use the first SIM information.

[303] In operation 1627, when another mobile device, for example, the mobile device 40 of the user B of FIG. 1, requests a phone call to the phone number +82-10-AAAA-BBBB, the server 10 of the mobile carrier tries a call connection to the first mobile device 20. Since the second SIM information is not requested to be used, a phone call is not connected to the second mobile device 30.

[304] FIG. 16D is a timing diagram of a method of performing the mobile communication function by the second mobile device 30, according to a SIM information use request of the first mobile device 20, based on the second scenario while the first mobile device 20 and the second mobile device 30 are linked to each other, according to an exemplary embodiment.

WO 2016/018017 PCT/KR2015/007785 [305] In operation 1631, the first mobile device 20 stores the first SIM information in the SIM 520. Also, the second mobile device 30 stores the second SIM information in the SIM 350.

[306] In operation 1632, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

[307] In operation 1633, the first and second mobile devices 20 and 30 are linked with each other by establishing a connection through short-range wireless communication.

[308] In operation 1634, the second mobile device 20 activates the phone function. The second mobile device 20 may activate the phone function manually or automatically. The activating of the phone function of the second mobile device 30 may mean that the user A wants to make a call using the second mobile device 30 that is a sub mobile device instead of the first mobile device 20 that is a main mobile device.

[309] In operation 1635, the first mobile device 20 transmits a request to use the second SIM information to the server 10 of the mobile carrier.

[310] In operation 1636, the server 10 of the mobile carrier approves the request to use the second SIM information.

[311] In operation 1637, when another mobile device, for example, the mobile device 40 of the user B of FIG. 1, requests a phone call to the phone number +82-10-AAAA-BBBB, the server 10 of the mobile carrier tries a call connection to the second mobile device 30. Since the first SIM information is not requested to be used, a phone call is not connected to the first mobile device 20.

[312] FIG. 17 A is a timing diagram of a method of performing the mobile communication function by the first mobile device 20, according to a SIM information use request of the first mobile device 20, based on the second scenario while the first mobile device 20 and the second mobile device 30 are separated from each other, according to an exemplary embodiment.

[313] In operation 1701, the first mobile device 20 stores the first SIM information in the SIM 520. Also, the second mobile device 30 stores the second SIM information in the SIM 350.

[314] In operation 1702, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

[315] In operation 1703, the first and second mobile devices 20 and 30 are linked with each other by establishing a connection through short-range wireless communication.

[316] In operation 1704, the first mobile device 20 activates the phone function. The first mobile device 20 may activate the phone function manually or automatically. The activating of the phone function of the first mobile device 20 may mean that the user A wants to make a call using the first mobile device 20 that is a main mobile device.

[317] In operation 1705, the first and second mobile devices 20 and 30 are separated from

WO 2016/018017

PCT/KR2015/007785 each other by terminating the connection through the short-range wireless communication.

[318] In operation 1706, the first mobile device 20 transmits a request to use the first SIM information to the server 10 of the mobile carrier.

[319] In operation 1707, the server 10 of the mobile carrier approves the request to use the first SIM information.

[320] In operation 1708, when another mobile device, for example, the mobile device 40 of the user B of FIG. 1, requests a phone call to the phone number +82-10-AAAA-BBBB, the server 10 of the mobile carrier tries a call connection to the first mobile device 20. Since the second SIM information is not requested to be used, a phone call is not connected to the second mobile device 30.

[321] FIG. 17B is a timing diagram of a method of performing the mobile communication function by the second mobile device 30, according to a SIM information use request of the second mobile device 30, based on the second scenario while the first mobile device 20 and the second mobile device 30 are separated from each other, according to an exemplary embodiment.

[322] In operation 1711, the first mobile device 20 stores the first SIM information in the SIM 520. Also, the second mobile device 30 stores the second SIM information in the SIM 350.

[323] In operation 1712, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

[324] In operation 1713, the first and second mobile devices 20 and 30 are linked with each other by establishing a connection through short-range wireless communication.

[325] In operation 1714, the second mobile device 30 activates the phone function. The second mobile device 30 may activate the phone function manually or automatically. The activating of the phone function of the second mobile device 30 may mean that the user A wants to make a call using the second mobile device 30 that is a sub mobile device instead of the first mobile device 20 that is a main mobile device.

[326] In operation 1715, the first and second mobile devices 20 and 30 are separated from each other by terminating the connection through the short-range wireless communication.

[327] In operation 1716, the second mobile device 30 transmits a request to use the second SIM information to the server 10 of the mobile carrier.

[328] In operation 1717, the server 10 of the mobile carrier approves the request to use the second SIM information.

[329] In operation 1718, when another mobile device, for example, the mobile device 40 of the user B of FIG. 1, requests a phone call to the phone number +82-10-AAAA-BBBB, the server 10 of the mobile carrier tries a call connection to

WO 2016/018017

PCT/KR2015/007785 the second mobile device 30. Since the first SIM information is not requested to be used, a phone call is not connected to the first mobile device 20.

[330] FIG. 17C is a timing diagram of a method of performing the mobile communication function by the first mobile device 20, according to a SIM information use request of the second mobile device 30, based on the second scenario while the first mobile device 20 and the second mobile device 30 are separated from each other, according to an exemplary embodiment.

[331] In operation 1721, the first mobile device 20 stores the first SIM information in the SIM 520. Also, the second mobile device 30 stores the second SIM information in the SIM 350.

[332] In operation 1722, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

[333] In operation 1723, the first and second mobile devices 20 and 30 are linked with each other by establishing a connection through short-range wireless communication.

[334] In operation 1724, the first mobile device 20 activates the phone function. The first mobile device 20 may activate the phone function manually or automatically. The activating of the phone function of the first mobile device 20 may mean that the user A wants to make a call using the first mobile device 20 that is a main mobile device.

[335] In operation 1725, the first and second mobile devices 20 and 30 are separated from each other by terminating the connection through the short-range wireless communication.

[336] In operation 1726, the second mobile device 30 transmits a request to use the first SIM information to the server 10 of the mobile carrier.

[337] In operation 1727, the server 10 of the mobile carrier approves the request to use the first SIM information.

[338] In operation 1728, when another mobile device, for example, the mobile device 40 of the user B of FIG. 1, requests a phone call to the phone number +82-10-AAAA-BBBB, the server 10 of the mobile carrier tries a call connection to the first mobile device 20. Since the second SIM information is not requested to be used, a phone call is not connected to the second mobile device 30.

[339] FIG. 17D is a timing diagram of a method of performing the mobile communication function by the second mobile device 30, according to a SIM information use request of the first mobile device 20, based on the second scenario while the first mobile device 20 and the second mobile device 30 are separated from each other, according to an exemplary embodiment.

[340] In operation 1731, the first mobile device 20 stores the first SIM information in the SIM 520. Also, the second mobile device 30 stores the second SIM information in the SIM 350.

WO 2016/018017 PCT/KR2015/007785 [341] In operation 1732, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

[342] In operation 1733, the first and second mobile devices 20 and 30 are linked with each other by establishing a connection through short-range wireless communication.

[343] In operation 1734, the second mobile device 30 activates the phone function. The second mobile device 30 may activate the phone function manually or automatically. The activating of the phone function of the second mobile device 30 may mean that the user A wants to make a call using the second mobile device 30 that is a sub mobile device instead of the first mobile device 20 that is a main mobile device.

[344] In operation 1735, the first and second mobile devices 20 and 30 are separated from each other by terminating the connection through the short-range wireless communication.

[345] In operation 1736, the first mobile device 20 transmits a request to use the second SIM information to the server 10 of the mobile carrier.

[346] In operation 1737, the server 10 of the mobile carrier approves the request to use the second SIM information.

[347] In operation 1738, when another mobile device, for example, the mobile device 40 of the user B of FIG. 1, requests a phone call to the phone number +82-10-AAAA-BBBB, the server 10 of the mobile carrier tries a call connection to the second mobile device 30. Since the first SIM information is not requested to be used, a phone call is not connected to the first mobile device 20.

[348] FIGS. 18A and 18B are diagrams for describing a concept of the third scenario in which SIM information is pre-stored in any one of the first mobile device 20 and the second mobile device 30, according to an exemplary embodiment.

[349] In FIG. 18A, the first SIM information is pre-stored in the SIM 520 of the first mobile device 20, but the second SIM information is not pre-stored in the SIM 350 of the second mobile device 30. On the other hand, in FIG. 18B, the first SIM information is not pre-stored in the SIM 520 of the first mobile device 20, but the second SIM information is pre-stored in the SIM 350 of the second mobile device 30. In other words, one of the SIM 520 or the SIM 350 may pre-store SIM information regardless of activation state of the phone function of the first or second mobile device 20 or 30.

[350] Referring to FIG. 18A, when the phone function of the first mobile device 20 is requested to be activated in the two-phone mode, the first mobile device 20 transmits a request to use the first SIM information to the server 10 of the mobile carrier. When the server 10 of the mobile carrier approves the request to use the first SIM information, the first mobile device 20 may perform the mobile communication function in the two-phone mode. Further, according to the third scenario, the first mobile device 20 copies and provides the first SIM information to the second mobile device 30 so

WO 2016/018017

PCT/KR2015/007785 that the second mobile device 30 may use the copied first SIM information in the same manner as using the second SIM information. In other words, the second mobile device having the copied first SIM information may perform the mobile communication function in the two-phone mode using the copied first SIM information.

[351] Referring to FIG. 18B, when the phone function of the second mobile device 30 is requested to be activated in the two-phone mode, the second mobile device 30 transmits a request to use the second SIM information to the server 10 of the mobile carrier. When the server 10 of the mobile carrier approves the request to use the second SIM information, the second mobile device 30 may perform the mobile communication function in the two-phone mode. Further, according to the third scenario, the second mobile device 30 copies and provides the second SIM information to the first mobile device 20 so that the first mobile device 20 may use the copied second SIM information in the same manner as using the first SIM information. In other words, the first mobile device 20 having the copied second SIM information may perform the mobile communication function in the two-phone mode using the copied second SIM information.

[352] FIG. 19A is a timing diagram of a method of performing the mobile communication function by the first mobile device 20, when the second mobile device 30 transmits a request to use the second SIM information stored in the SIM 350, based on the third scenario while the first mobile device 20 and the second mobile device 30 are linked to each other, according to an exemplary embodiment.

[353] In operation 1901, the second mobile device 30 stores the second SIM information in the SIM 350.

[354] In operation 1902, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

[355] In operation 1903, the first and second mobile devices 20 and 30 are linked with each other by establishing a connection through short-range wireless communication.

[356] In operation 1904, the first mobile device 20 activates the phone function. The first mobile device 20 may activate the phone function manually or automatically. The activating of the phone function of the first mobile device 20 may mean that the user A wants to make a call using the first mobile device 20 that is a main mobile device.

[357] In operation 1905, the second mobile device 30 copies the second SIM information and provides the copied second SIM information to the first mobile device 20.

[358] In operation 1906, the first mobile device 20 stores the copied second SIM information in the SIM 520.

[359] In operation 1907, the second mobile device 30 deletes the second SIM information stored in the SIM 350.

[360] In operation 1908, the second mobile device 30 transmits a request to use the copied

WO 2016/018017 PCT/KR2015/007785 second SIM information to the server 10 of the mobile carrier.

[361] In operation 1909, the server 10 of the mobile carrier approves the request to use the copied second SIM information.

[362] In operation 1910, when another mobile device, for example, the mobile device 40 of the user B of FIG. 1, requests a phone call to the phone number +82-10-AAAA-BBBB, the server 10 of the mobile carrier tries a call connection to the first mobile device 20. Since the second SIM information is deleted from the SIM 350, a phone call is not connected to the second mobile device 30.

[363] FIG. 19B is a timing diagram of a method of performing the mobile communication function by the first mobile device 20, when the first mobile device 20 transmits a request to use the second SIM information stored in the SIM 350, based on the third scenario while the first mobile device 20 and the second mobile device 30 are linked to each other, according to an exemplary embodiment.

[364] In operation 1911, the second mobile device 30 stores the second SIM information in the SIM 350.

[365] In operation 1912, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

[366] In operation 1913, the first and second mobile devices 20 and 30 are linked with each other by establishing a connection through short-range wireless communication.

[367] In operation 1914, the first mobile device 20 activates the phone function. The first mobile device 20 may activate the phone function manually or automatically. The activating of the phone function of the first mobile device 20 may mean that the user A wants to make a call using the first mobile device 20 that is a main mobile device.

[368] In operation 1915, the second mobile device 30 copies the second SIM information and provides the copied second SIM information to the first mobile device 20.

[369] In operation 1916, the first mobile device 20 stores the copied second SIM information in the SIM 520.

[370] In operation 1917, the second mobile device 30 deletes the second SIM information stored in the SIM 350.

[371] In operation 1918, the first mobile device 20 transmits a request to use the copied second SIM information to the server 10 of the mobile carrier.

[372] In operation 1919, the server 10 of the mobile carrier approves the request to use the copied second SIM information.

[373] In operation 1920, when another mobile device, for example, the mobile device 40 of the user B of FIG. 1, requests a phone call to the phone number +82-10-AAAA-BBBB, the server 10 of the mobile carrier tries a call connection to the first mobile device 20. Since the second SIM information is deleted from the SIM 350, a phone call is not connected to the second mobile device 30.

WO 2016/018017 PCT/KR2015/007785 [374] FIG. 19C is a timing diagram of a method of performing the mobile communication function by the second mobile device 30, when the second mobile device 30 transmits a request to use the first SIM information stored in the SIM 520, based on the third scenario while the first mobile device 20 and the second mobile device 30 are linked to each other, according to an exemplary embodiment.

[375] In operation 1921, the first mobile device 20 stores the first SIM information in the SIM 520.

[376] In operation 1922, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

[377] In operation 1923, the first and second mobile devices 20 and 30 are linked with each other by establishing a connection through short-range wireless communication.

[378] In operation 1924, the second mobile device 30 activates the phone function. The second mobile device 30 may activate the phone function manually or automatically. The activating of the phone function of the second mobile device 30 may mean that the user A wants to make a call using the second mobile device 30 that is a sub mobile device, instead of the first mobile device 20 that is a main mobile device.

[379] In operation 1925, the first mobile device 20 copies the first SIM information and provides the copied first SIM information to the second mobile device 30.

[380] In operation 1926, the second mobile device 30 stores the copied first SIM information in the SIM 350.

[381] In operation 1927, the first mobile device 20 deletes the first SIM information stored in the SIM 520.

[382] In operation 1928, the second mobile device 30 transmits a request to use the copied first SIM information to the server 10 of the mobile carrier.

[383] In operation 1929, the server 10 of the mobile carrier approves the request to use the copied first SIM information.

[384] In operation 1930, when another mobile device, for example, the mobile device 40 of the user B of FIG. 1, requests a phone call to the phone number +82-10-AAAA-BBBB, the server 10 of the mobile carrier tries a call connection to the second mobile device 30. Since the first SIM information is deleted from the SIM 520, a phone call is not connected to the first mobile device 20.

[385] FIG. 19D is a timing diagram of a method of performing the mobile communication function by the second mobile device 30, when the first mobile device 20 transmits a request to use the first SIM information stored in the SIM 520, based on the third scenario while the first mobile device 20 and the second mobile device 30 are linked to each other, according to an exemplary embodiment.

[386] In operation 1931, the first mobile device 20 stores the first SIM information in the SIM 520.

WO 2016/018017 PCT/KR2015/007785 [387] In operation 1932, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

[388] In operation 1933, the first and second mobile devices 20 and 30 are linked with each other by establishing a connection through short-range wireless communication.

[389] In operation 1934, the second mobile device 30 activates the phone function. The second mobile device 30 may activate the phone function manually or automatically. The activating of the phone function of the second mobile device 30 may mean that the user A wants to make a call using the second mobile device 30 that is a sub mobile device, instead of the first mobile device 20 that is a main mobile device.

[390] In operation 1935, the first mobile device 20 copies the first SIM information and provides the copied first SIM information to the second mobile device 30.

[391] In operation 1936, the second mobile device 30 stores the copied first SIM information in the SIM 350.

[392] In operation 1937, the first mobile device 20 deletes the first SIM information stored in the SIM 520.

[393] In operation 1938, the first mobile device 20 transmits a request to use the copied first SIM information to the server 10 of the mobile carrier.

[394] In operation 1939, the server 10 of the mobile carrier approves the request to use the copied first SIM information.

[395] In operation 1940, when another mobile device, for example, the mobile device 40 of the user B of FIG. 1, requests a phone call to the phone number +82-10-AAAA-BBBB, the server 10 of the mobile carrier tries a call connection to the second mobile device 30. Since the first SIM information is deleted from the SIM 520, a phone call is not connected to the first mobile device 20.

[396] FIG. 20A is a timing diagram of a method of performing the mobile communication function by the first mobile device 20, when the first mobile device 20 transmits a request to use the second SIM information stored in the SIM 350, based on the third scenario while the first mobile device 20 and the second mobile device 30 are separated from each other, according to an exemplary embodiment.

[397] In operation 2001, the second mobile device 30 stores the second SIM information in the SIM 350.

[398] In operation 2002, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

[399] In operation 2003, the first and second mobile devices 20 and 30 are linked with each other by establishing a connection through short-range wireless communication.

[400] In operation 2004, the first mobile device 20 activates the phone function. The first mobile device 20 may activate the phone function manually or automatically. The activating of the phone function of the first mobile device 20 may mean that the user A

WO 2016/018017

PCT/KR2015/007785 wants to make a call using the first mobile device 20 that is a main mobile device.

[401] In operation 2005, the second mobile device 30 copies the second SIM information and provides the copied second SIM information to the first mobile device 20.

[402] In operation 2006, the first mobile device 20 stores the copied second SIM information in the SIM 520.

[403] In operation 2007, the second mobile device 30 deletes the second SIM information stored in the SIM 350.

[404] In operation 2008, the first and second mobile devices 20 and 30 are separated from each other by terminating the connection through the short-range wireless communication.

[405] In operation 2009, the first mobile device 20 transmits a request to use the copied second SIM information to the server 10 of the mobile carrier.

[406] In operation 2010, the server 10 of the mobile carrier approves the request to use the copied second SIM information.

[407] In operation 2011, when another mobile device, for example, the mobile device 40 of the user B of FIG. 1, requests a phone call to the phone number +82-10-AAAA-BBBB, the server 10 of the mobile carrier tries a call connection to the first mobile device 20. Since the second SIM information is deleted from the SIM 350, a phone call is not connected to the second mobile device 30.

[408] FIG. 20B is a timing diagram of a method of performing the mobile communication function by the first mobile device 20, when the second mobile device 30 transmits a request to use the second SIM information stored in the SIM 250, based on the third scenario while the first mobile device 20 and the second mobile device 30 are separated from each other, according to an exemplary embodiment.

[409] In operation 2021, the second mobile device 30 stores the second SIM information in the SIM 350.

[410] In operation 2022, the first mobile device 20 sets the two-phone mode. Also, the second mobile device 30 sets the two-phone mode.

[411] In operation 2023, the first and second mobile devices 20 and 30 are linked with each other by establishing a connection through short-range wireless communication.

[412] In operation 2024, the first mobile device 20 activates the phone function. The first mobile device 20 may activate the phone function manually or automatically. The activating of the phone function of the first mobile device 20 may mean that the user A wants to make a call using the first mobile device 20 that is a main mobile device.

[413] In operation 2025, the second mobile device 30 copies the second SIM information and provides the copied second SIM information to the first mobile device 20.

[414] In operation 2026, the first mobile device 20 stores the copied second SIM information in the SIM 520.

WO 2016/018017 PCT/KR2015/007785 [415] In operation 2027, the second mobile device 30 deletes the second SIM information stored in the SIM 350.

[416] In operation 2028, the first and second mobile devices 20 and 30 are separated from each other by terminating the connection through the short-range wireless communication.

[417] In operation 2029, the second mobile device 20 transmits a request to use the copied second SIM information to the server 10 of the mobile carrier.

[418] In operation 2030, the server 10 of the mobile carrier approves the request to use the copied second SIM information.

[419] In operation 2031, when another mobile device, for example, the mobile device 40 of the user B of FIG. 1, requests a phone call to the phone number +82-10-AAAA-BBBB, the server 10 of the mobile carrier tries a call connection to the first mobile device 20. Since the second SIM information is deleted from the SIM 350, a phone call is not connected to the second mobile device 30.

[420] FIG. 20C is a timing diagram of a method of performing the mobile communication function by the second mobile device 30, when the second mobile device 30 transmits a request to use the first SIM information stored in the SIM 520, based on the third scenario while the first mobile device 20 and the second mobile device 30 are separated from each other, according to an exemplary embodiment.

[421] In operation 2041, the first mobile device 20 stores the first SIM information in the SIM 520.

[422] In operation 2042, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

[423] In operation 2043, the first and second mobile devices 20 and 30 are linked with each other by establishing a connection through short-range wireless communication.

[424] In operation 2044, the second mobile device 30 activates the phone function. The second mobile device 30 may activate the phone function manually or automatically. The activating of the phone function of the second mobile device 30 may mean that the user A wants to make a call using the second mobile device 30 that is a sub mobile device, instead of the first mobile device 20 that is a main mobile device.

[425] In operation 2045, the first mobile device 20 copies the first SIM information and provides the copied first SIM information to the second mobile device 30.

[426] In operation 2046, the second mobile device 30 stores the copied first SIM information in the SIM 350.

[427] In operation 2047, the first mobile device 20 deletes the first SIM information stored in the SIM 520.

[428] In operation 2048, the first and second mobile devices 20 and 30 are separated from each other by terminating the connection through the short-range wireless commu44

WO 2016/018017 PCT/KR2015/007785 nication.

[429] In operation 2049, the second mobile device 30 transmits a request to use the copied first SIM information to the server 10 of the mobile carrier.

[430] In operation 2050, the server 10 of the mobile carrier approves the request to use the copied first SIM information.

[431] In operation 2051, when another mobile device, for example, the mobile device 40 of the user B of FIG. 1, requests a phone call to the phone number +82-10-AAAA-BBBB, the server 10 of the mobile carrier tries a call connection to the second mobile device 20. Since the first SIM information is deleted from the SIM 520, a phone call is not connected to the first mobile device 20.

[432] FIG. 20D is a timing diagram of a method of performing the mobile communication function by the second mobile device 30, when the first mobile device 20 transmits a request to use the first SIM information stored in the SIM 520, based on the third scenario while the first mobile device 20 and the second mobile device 30 are separated from each other, according to an exemplary embodiment.

[433] In operation 2061, the first mobile device 20 stores the first SIM information in the SIM 520.

[434] In operation 2062, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

[435] In operation 2063, the first and second mobile devices 20 and 30 are linked with each other by establishing a connection through short-range wireless communication.

[436] In operation 2064, the second mobile device 30 activates the phone function. The second mobile device 30 may activate the phone function manually or automatically. The activating of the phone function of the second mobile device 30 may mean that the user A wants to make a call using the second mobile device 30 that is a sub mobile device, instead of the first mobile device 20 that is a main mobile device.

[437] In operation 2065, the first mobile device 20 copies the first SIM information and provides the copied first SIM information to the second mobile device 30.

[438] In operation 2066, the second mobile device 30 stores the copied first SIM information in the SIM 350.

[439] In operation 2067, the first mobile device 20 deletes the first SIM information stored in the SIM 520.

[440] In operation 2068, the first and second mobile devices 20 and 30 are separated from each other by terminating the connection through the short-range wireless communication.

[441] In operation 2069, the second mobile device 30 transmits a request to use the copied first SIM information to the server 10 of the mobile carrier.

[442] In operation 2070, the server 10 of the mobile carrier approves the request to use the

WO 2016/018017

PCT/KR2015/007785 copied first SIM information.

[443] In operation 2071, when another mobile device, for example, the mobile device 40 of the user B of FIG. 1, requests a phone call to the phone number +82-10-AAAA-BBBB, the server 10 of the mobile carrier tries a call connection to the second mobile device 20. Since the first SIM information is deleted from the SIM 520, a phone call is not connected to the first mobile device 20.

[444] FIG. 21 is a diagram for describing the device ID information and the SIM information, which are stored in each of the first mobile device and the second mobile device, according to another exemplary embodiment.

[445] Referring to FIG. 21, the same phone number +82-10-AAAA-BBBB may be assigned to the first and second mobile devices 20 and 30. In the first device ID information of the first mobile device 20, the IMEI of the first mobile device 20 may have a value 35 abcdef 465607 8. Also, the ICCID of the first SIM information of the first mobile device 20 may have a value abed efgh 0710 9991 604. In the second device ID information of the second mobile device 30, the IMEI of the second mobile device 30 may have a value 35 abcdef 465607 8, which is the same as the IMEI of the first device ID information. Also, the ICCID of the second SIM information of the second mobile device 30 may have a value abed efgh 0710 9991 604, which is the same as the ICCID of the first SIM information.

[446] In other words, according to FIG. 21, the first and second mobile devices 20 and 30 are assigned with the same phone number +82-10-AAAA-BBBB, have SIM information of the same ICCID, and have device ID information of the same IMEI. The exemplary embodiment described with reference to FIG. 21 differs from the exemplary embodiments described with reference to FIGS. 11A and 1 IB in that, in FIG. 21, the first device ID information of the first mobile device 20 and the second device ID information of the second mobile device 30 are the same.

[447] FIGS. 22A through 27 are diagrams related to methods according to the exemplary embodiment of FIG. 21.

[448] FIG. 22A is a timing diagram of a method of performing the mobile communication function by the first mobile device 20, when the first device ID information of the first mobile device 20 and the second device ID information of the second mobile device 30 are the same and the phone functions of the first and second mobile devices 20 and 30 are both usable, according to an exemplary embodiment.

[449] In operation 2201, the server 10 of the mobile carrier transmits the first SIM information to the first mobile device 20.

[450] In operation 2202, the server 10 of the mobile carrier transmits the second SIM information to the second mobile device 30.

[451] In operation 2203, the first mobile device 20 stores the first SIM information in the

WO 2016/018017

PCT/KR2015/007785

SIM 520. Also, the second mobile device 30 stores the second SIM information in the SIM 350.

[452] In operation 2204, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

[453] In operation 2205, the first and second mobile devices 20 and 30 are linked to each other by establishing a connection through short-range wireless communication.

[454] In operation 2206, the first mobile device 20 is set as a preferred device from among the first and second mobile devices 20 and 30 owned by the user A according to an input of the user A. A preferred device may denote a device for receiving a phone call to the phone number +82-10-AAAA-BBBB.

[455] In operation 2207, the phone function of the second mobile device 30 is deactivated because the first mobile device 20 is set as the preferred device.

[456] In operation 2208, when the phone number +82-10-AAAA-BBBB is requested to be called from another mobile device, such as the mobile device 40 of the user B of FIG. 1, the server 10 of the mobile carrier tries a call connection to the first mobile device 20. A phone call is not connected to the second mobile device 30 since the phone function of the second mobile device 30 is deactivated.

[457] FIG. 22B is a timing diagram of a method of performing the mobile communication function by the second mobile device 30, when the first device ID information of the first mobile device 20 and the second device ID information of the second mobile device 30 are the same and the phone functions of the first and second mobile devices 20 and 30 are both usable, according to an exemplary embodiment.

[458] In operation 2211, the server 10 of the mobile carrier transmits the first SIM information to the first mobile device 20.

[459] In operation 2212, the server 10 of the mobile carrier transmits the second SIM information to the second mobile device 30.

[460] In operation 2213, the first mobile device 20 stores the first SIM information in the SIM 520. Also, the second mobile device 30 stores the second SIM information in the SIM 350.

[461] In operation 2214, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

[462] In operation 2215, the first and second mobile devices 20 and 30 are linked to each other by establishing a connection through short-range wireless communication.

[463] In operation 2216, the second mobile device 30 is set as a preferred device from among the first and second mobile devices 20 and 30 owned by the user A according to an input of the user A. A preferred device may denote a device for receiving a phone call to the phone number +82-10-AAAA-BBBB.

[464] In operation 2217, the phone function of the first mobile device 20 is deactivated

WO 2016/018017

PCT/KR2015/007785 because the second mobile device 30 is set as the preferred device.

[465] In operation 2218, when the phone number +82-10-AAAA-BBBB is requested to be called from another mobile device, such as the mobile device 40 of the user B of FIG. 1, the server 10 of the mobile carrier tries a call connection to the second mobile device 30. A phone call is not connected to the first mobile device 20 since the phone function of the first mobile device 30 is deactivated.

[466] FIG. 22C is a timing diagram of a method of performing the mobile communication function by the first mobile device 20, when the first device ID information of the first mobile device 20 and the second device ID information of the second mobile device 30 are the same and only the phone function of the first mobile device 20 is usable, according to an exemplary embodiment.

[467] In operation 2221, the server 10 of the mobile carrier transmits the first SIM information to the first mobile device 20.

[468] In operation 2222, the server 10 of the mobile carrier transmits the second SIM information to the second mobile device 30.

[469] In operation 2223, the first mobile device 20 stores the first SIM information in the SIM 520. Also, the second mobile device 30 stores the second SIM information in the SIM 350.

[470] In operation 2204, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

[471] In operation 2225, the first and second mobile devices 20 and 30 are linked to each other by establishing a connection through short-range wireless communication.

[472] In operation 2226, the second mobile device 30 notifies the first mobile device 20 that the phone function of the second mobile device 30 is in an unusable state. The unusable state of the phone function may denote a state in which the mobile communication module included in the second mobile device 30 is malfunctioning or shutoff.

[473] In operation 2227, the first mobile device 20 activates the phone function of the first mobile device 20.

[474] In operation 2228, when the phone number +82-10-AAAA-BBBB is requested to be called from another mobile device, such as the mobile device 40 of the user B of FIG. 1, the server 10 of the mobile carrier tries a call connection to the first mobile device 20. A phone call is not connected to the second mobile device 30 since the phone function of the second mobile device 30 is not usable.

[475] FIG. 22D is a timing diagram of a method of performing the mobile communication function by the second mobile device 30, when the first device ID information of the first mobile device 20 and the second device ID information of the second mobile device 30 are the same and only the phone function of the first mobile device 20 is usable, according to an exemplary embodiment.

WO 2016/018017 PCT/KR2015/007785 [476] In operation 2231, the server 10 of the mobile carrier transmits the first SIM information to the first mobile device 20.

[477] In operation 2232, the server 10 of the mobile carrier transmits the second SIM information to the second mobile device 30.

[478] In operation 2233, the first mobile device 20 stores the first SIM information in the SIM 520. Also, the second mobile device 30 stores the second SIM information in the SIM 350.

[479] In operation 2234, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

[480] In operation 2235, the first and second mobile devices 20 and 30 are linked to each other by establishing a connection through short-range wireless communication.

[481] In operation 2236, the second mobile device 30 notifies the first mobile device 20 that the phone function of the second mobile device 30 is in an unusable state. The unusable state of the phone function may denote a state in which the mobile communication module included in the second mobile device 30 is malfunctioning or shutoff.

[482] In operation 2237, the first mobile device 20 activates the phone function of the first mobile device 20.

[483] In operation 2238, when the phone number +82-10-AAAA-BBBB is requested to be called from another mobile device, such as the mobile device 40 of the user B of FIG. 1, the server 10 of the mobile carrier tries a call connection to the first mobile device 20.

[484] In operation 2239, the first mobile device 20 call-forwards the phone call received from the server 10 of the mobile carrier to the second mobile device 30 via an outof-band wireless connection method using short-range wireless communication.

[485] FIG. 22E is a timing diagram of a method of performing the mobile communication function by the second mobile device 30, when the first device ID information of the first mobile device 20 and the second device ID information of the second mobile device 30 are the same and only the phone function of the second mobile device 30 is usable, according to an exemplary embodiment.

[486] In operation 2241, the server 10 of the mobile carrier transmits the first SIM information to the first mobile device 20.

[487] In operation 2242, the server 10 of the mobile carrier transmits the second SIM information to the second mobile device 30.

[488] In operation 2243, the first mobile device 20 stores the first SIM information in the SIM 520. Also, the second mobile device 30 stores the second SIM information in the SIM 350.

[489] In operation 2244, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

WO 2016/018017 PCT/KR2015/007785 [490] In operation 2245, the first and second mobile devices 20 and 30 are linked to each other by establishing a connection through short-range wireless communication.

[491] In operation 2246, the first mobile device 20 notifies the second mobile device 30 that the phone function of the first mobile device 20 is in an unusable state. The unusable state of the phone function may denote a state in which the mobile communication module included in the first mobile device 20 is malfunctioning or shutoff.

[492] In operation 2247, the second mobile device 30 activates the phone function of the second mobile device 30.

[493] In operation 2248, when the phone number +82-10-AAAA-BBBB is requested to be called from another mobile device, such as the mobile device 40 of the user B of FIG. 1, the server 10 of the mobile carrier tries a call connection to the second mobile device 30. A phone call is not connected to the first mobile device 20 since the phone function of the first mobile device 20 is not usable.

[494] FIG. 22F is a timing diagram of a method of performing the mobile communication function by the first mobile device 20, when the first device ID information of the first mobile device 20 and the second device ID information of the second mobile device 30 are the same and only the phone function of the second mobile device 30 is usable, according to an exemplary embodiment.

[495] In operation 2251, the server 10 of the mobile carrier transmits the first SIM information to the first mobile device 20.

[496] In operation 2252, the server 10 of the mobile carrier transmits the second SIM information to the second mobile device 30.

[497] In operation 2253, the first mobile device 20 stores the first SIM information in the SIM 520. Also, the second mobile device 30 stores the second SIM information in the SIM 350.

[498] In operation 2254, the first mobile device 20 and the second mobile device 30 set the two-phone mode.

[499] In operation 2255, the first and second mobile devices 20 and 30 are linked to each other by establishing a connection through short-range wireless communication.

[500] In operation 2256, the first mobile device 20 notifies the second mobile device 30 that the phone function of the first mobile device 20 is in an unusable state. The unusable state of the phone function may denote a state in which the mobile communication module included in the first mobile device 20 is malfunctioning or shutoff.

[501] In operation 2257, the second mobile device 30 activates the phone function of the first mobile device 20.

[502] In operation 2258, when the phone number +82-10-AAAA-BBBB is requested to be called from another mobile device, such as the mobile device 40 of the user B of FIG. 1, the server 10 of the mobile carrier tries a call connection to the second mobile

WO 2016/018017 PCT/KR2015/007785 device 30.

[503] In operation 2259, the second mobile device 30 call-forwards the phone call received from the server 10 of the mobile carrier to the first mobile device 20 via an out-of-band wireless connection method using short-range wireless communication.

[504] FIG. 23 is a block diagram of the second mobile device 30 configured to share a first phone number of the first mobile device 20 on a mobile communication system, according to an exemplary embodiment.

[505] Referring to FIG. 23, the second mobile device 30 may include the controller 320, the communicator 330, and the SIM 350. The second mobile device 30 may include additional hardware components, or may not include all of the hardware components shown in FIG. 23. The second mobile device 30 of FIG. 23 may be a card-type phone described above, but is not limited thereto. The second mobile device 30 of FIG. 23 may perform, for example, operations of the second mobile device 30 described above with reference to FIGS. 1 through 22F.

[506] The controller 320 activates the phone function of the second mobile device 30 after determining that the phone function of the first mobile device 20 is deactivated.

[507] The SIM 350 receives, from the server 10, and stores the second SIM information including subscription information of the first phone number registered with the mobile communication system.

[508] When the phone function of the second mobile device 30 is activated, the communicator 330 transmits a request to use the second SIM information to the server 10 of the mobile carrier such that the mobile communication function is performed.

[509] FIG. 24 is a flowchart of a method of providing a mobile communication service using the second mobile device 30 sharing the first phone number of the first mobile device 20, according to an exemplary embodiment. Referring to FIG. 24, the method includes operations processed in time-series by the second mobile device 30 described above. Thus, details about the second mobile device 30 may be applied to the method of FIG. 24.

[510] In operation 2401, the controller 320 determines whether the phone function of the first mobile device 20 is deactivated.

[511] In operation 2402, the controller 320 activates the phone function of the second mobile device 30 based on a result of the determining of operation 2401.

[512] In operation 2403, when the phone function of the second mobile device 30 is activated, the communicator 330 requests the server 10 of the mobile carrier to activate the second SIM information that is stored in the SIM 350 and includes the subscription information of the first phone number registered with the mobile communication service.

[513] In operation 2404, when the second SIM information is activated by the server 10 of

WO 2016/018017

PCT/KR2015/007785 the mobile carrier, the communicator 330 performs the mobile communication function using the activated second SIM information.

[514] FIG. 25 is a diagram for describing synchronizing recent call histories between the first mobile device 20 and the second mobile device 30, according to an exemplary embodiment.

[515] As described above, the first and second mobile devices 20 are independent devices capable of making and receiving phone calls. Accordingly, a history of phone calls made and received by the first mobile device 20 may be stored only in the first mobile device 20, and a history of phone calls made and received by the second mobile device 30 may be stored only in the second mobile device 30. However, since the first and second mobile devices 20 and 30 share one phone number, recent call histories of the first and second mobile devices 20 and 30 may be synchronized for user convenience.

[516] A point of time when the recent call histories are synchronized may be when the first and second mobile devices 20 and 30 are separated from or linked with each other, but one or more exemplary embodiments are not limited thereto, and the recent call histories may be synchronized at any time desired by a user.

[517] FIG. 26 is a flowchart of a method of synchronizing recent call histories when the first mobile device 20 and the second mobile device 30 are separated from each other, according to an exemplary embodiment.

[518] Referring to FIG. 26, separating of the first and second mobile devices 20 and 30 may mean that a user wants to use the second mobile device 30, for example, a cardtype phone, instead of the first mobile device 20, for example, a smart phone.

[519] In operation 2601, the first mobile device 20 stores a recent call history about recent phone calls up to the last phone call while being linked to the second mobile device 30.

[520] In operation 2602, when a user inputs a request to separate the first and second mobile devices 20 and 30, the first mobile device 20 sets separation of the first and second mobile devices 20 and 30.

[521] In operation 2603, the first mobile device 20 requests the second mobile device 30 for synchronization of a recent call history.

[522] In operation 2604, the first mobile device 20 receives, from the second mobile device 30, an index of the last phone call in a recent call history stored in the second mobile device 30. Here, an index (or a sync index) may be ID information assigned to classify phone call records in a recent call history to manage the recent call history. Further, the first mobile device 20 may store the recent call history using an index (or a sync index).

[523] In operation 2605, the first mobile device 20 determines whether the index received from the second mobile device 30 matches an index of the last phone call of the first mobile device 20. In other words, the first mobile device 20 determines whether the

WO 2016/018017

PCT/KR2015/007785 recent call history of the first mobile device 20 is different from that of the second mobile device 30 based on the received index to determine whether the recent call history needs to be synchronized. When the indexes match each other, the method is ended since the recent call history does not need to be synchronized. When the indexes do not match each other, operation 2606 is performed.

[524] In operation 2606, the first mobile device 20 generates information about a phone call history after the index received from the second mobile device 30. Such information is about a recent call history that only exists in the first mobile device 20 and does not exist in the second mobile device.

[525] In operation 2607, the second mobile device 30 updates the recent call history of the second mobile device 30 using the information about the phone call history received from the first mobile device 20. As such, the recent call history may be synchronized between the first and second mobile devices.

[526] In operation 2608, the second mobile device 30 is separated from the first mobile device 20. In other words, the user may make or receive a call through the second mobile device 30 instead of the first mobile device 20.

[527] According to another exemplary embodiment, the first mobile device 20 may receive, from the second mobile device 30, the recent call history of the second mobile device 30 after operation 2603, and update the received recent call history to the recent call history of the first mobile device 20. In this case, operations 2604 through 2606 may not be performed.

[528] FIG. 27 is a table illustrating a database of recent call histories stored in a device, according to an exemplary embodiment.

[529] Referring to FIG. 27, a recent call history of the first or second mobile device 20 or 30 may include times of incoming and outgoing calls and phone numbers of incoming and outgoing calls, and may be converted to a database in a form of a table 2700 in which a sync index is assigned to each phone call record. A sync index is ID information assigned to classify the phone call records, and the first and second mobile devices 20 and 30 may determine whether recent call histories need to be synchronized by comparing sync indexes stored therein. The form of the database regarding the recent call history is not limited to the table 2700 of FIG. 27, and may be in a different form of a table or text.

[530] FIG. 28 is a flowchart of a method of synchronizing recent call histories when the first mobile device 20 and the second mobile device 30 are linked with each other, according to an exemplary embodiment.

[531] Referring to FIG. 28, the first and second mobile devices 20 and 30 may be linked when a user wants to use the first mobile device 20 (for example, a smart phone).

[532] In operation 2801, the first mobile device 20 stores a recent call history about recent

WO 2016/018017

PCT/KR2015/007785 phone calls up to the last phone call while being separated from the second mobile device. 30.

[533] In operation 2802, when the user inputs a request to link the first and second mobile devices 20 and 30, the second mobile device 30 sets connecting of the first and second mobile devices 20 and 30.

[534] In operation 2803, the second mobile device 30 requests the first mobile device 20 for synchronization of a recent call history.

[535] In operation 2804, the second mobile device 30 receives, from the first mobile device, an index of the last phone call in the recent call history stored in the first mobile device 20. Here, an index (or a sync index) may be ID information assigned to classify phone call records in the recent call history to manage the recent call history in the first mobile device 20. Meanwhile, not only the first mobile device 20, but also the second mobile device 30 may manage a recent call history of the second mobile device 30 using an index (or a sync index).

[536] In operation 2805, the second mobile device 30 determines whether the index received from the first mobile device 20 is the same as an index of the last phone call of the second mobile device 30. In other words, the second mobile device 30 may determine whether the recent call histories of the first and second mobile devices 20 and 30 are different from each other based on the received index, or whether the recent call histories of the first and second mobile devices 20 and 30 need to be synchronized. When the indexes are the same, the method is ended since the recent call histories do not need to be synchronized. When the indexes are not the same, operation 2806 is performed.

[537] In operation 2806, the second mobile device 30 generates information about a phone call history after the index received from the first mobile device 20. Such information includes information about a recent call history that exists only in the second mobile device 30 and does not exist in the first mobile device 20.

[538] In operation 2807, the first mobile device 20 updates the recent call history of the first mobile device 20 using the information about the phone call history received from the second mobile device 30. Accordingly, the recent call histories of the first and second mobile devices 20 and 30 may be synchronized.

[539] In operation 2808, the first mobile device 20 is linked with the second mobile device 30. In other words, the user may make or receive a call through the first mobile device 20 instead of the second mobile device 30.

[540] According to another exemplary embodiment, the second mobile device 30 may receive, from the first mobile device 20, the recent call history of the first mobile device 20 after operation 2803, and update the received recent call history to the recent call history of the second mobile device 30. In this case, operations 2804 through 2806

WO 2016/018017

PCT/KR2015/007785 may not be performed.

[541] FIG. 29 is a diagram for describing a mobile communication system including a wearable device, according to an exemplary embodiment.

[542] Referring to FIG. 29, the first and second mobile devices 20 and 30 are devices that share one phone number as described above with reference to FIG. 1. A wearable device 50 may be device of a standalone type or a companion type.

[543] When the wearable device 50 is a standalone type, a phone number different from that of the first mobile device 20 (or the second mobile device 30) is assigned to the wearable device 50. However, the server 10 of the mobile carrier may map the phone number of the wearable device 50 to the phone number of the first mobile device 20 (or the second mobile device 30). Accordingly, in terms of the mobile communication system, the first mobile device 20 (or the second mobile device 30) and the wearable device 50 are managed as having different phone numbers, but in terms of a user of the first mobile device 20 (or the second mobile device 30) and the wearable device 50 or a third person, the first mobile device 20 (or the second mobile device 30) and the wearable device 50 may be viewed as sharing one phone number.

[544] When the wearable device 50 is a companion type, a phone number is not assigned to the wearable device 50.

[545] A method of linking a call using the wearable device 50 when the wearable device 50 is a standalone type will be described with reference to FIGS. 30, 31, 34, and 35. Also, a method of linking a call using the wearable device 50 when the wearable device 50 is a companion type will be described with reference to FIGS. 32, 33, 36, and 37.

[546] FIG. 30 is a timing diagram of a method of performing a phone call by the wearable device 50 of a standalone type instead of the first mobile device 20, according to an exemplary embodiment.

[547] Referring to FIG. 30, it is assumed that the wearable device 50 of the standalone type is connectable only to the first mobile device 20 and is not connectable to the second mobile device 30.

[548] In operation 3001, the wearable device 50 requests the first mobile device 20 for a connection. Here, a method of connecting the wearable device 50 and the first mobile device 20 may include any one of various short-range wireless communication methods, such as Wi-Fi, Wi-Fi direct, Bluetooth, and NFC.

[549] In operation 3002, the wearable device 50 and the first mobile device 20 synchronizes recent call histories. Here, the synchronizing of the recent call histories may be performed in the similar manner as that performed between the first and second mobile devices 20 and 30 described above with reference to FIG. 28.

[550] In operation 3003, the wearable device 50 is set as a primary receiving device for receiving a call ahead of the first mobile device 20.

WO 2016/018017 PCT/KR2015/007785 [551] In operation 3004, the first mobile device 20 is set as a backup receiving device for receiving a call when the wearable device 50 is unable to receive a call.

[552] In operation 3005, since the wearable device 50 is the primary receiving device, the wearable device 50 is in a standby state.

[553] In operation 3006, when an external source (for example, a third person) requests a phone call, the server 10 of the mobile carrier transmits a phone call request to the wearable device 50 set as the primary receiving device. According to FIG. 30, a phone number of the first mobile device 20 is +82-10-AAAA-BBBB and a phone number of the wearable device 50 is +82-10-CCCC-DDDD, and thus are different from each other. However, as described above with reference to FIG. 29, since the server 10 of the mobile carrier maps the phone numbers of the first mobile device 20 and the wearable device 50, and manages the devices so that a main phone number of the user of the first mobile device 20 and the wearable device 50 is +82-10-AAAA-BBBB that is the phone number of the first mobile device 20, and thus the external source (the third person) need not separately recognize +82-10-CCCC-DDDD as the phone number of the wearable device 50. In other words, the external source (the third person) makes a call to the first mobile device 20 or the wearable device 50 by using only the phone number +82-10-AAAA-BBBB.

[554] In operation 3007, the wearable device 50 notifies a user of an incoming call.

[555] In operation 3008, the wearable device 50 transmits information about the incoming call to the first mobile device 20.

[556] In operation 3009, the first mobile device 20 notifies the user of the incoming call.

[557] In operation 3010, the wearable device 50 answers the incoming call according to the phone call request from the server 10 of the mobile carrier.

[558] In operation 3011, the wearable device 50 hangs up when the incoming call is terminated.

[559] In operation 3012, when the incoming call is terminated, the wearable device 50 notifies the first mobile device 20 of the terminated incoming call.

[560] In operation 3013, the wearable device 50 updates a recent call history based on information about the terminated incoming call.

[561] In operation 3014, the first mobile device 20 also updates a recent call history based on the information about the terminated incoming call.

[562] FIG. 31 is a timing diagram of a method of performing a phone call by the wearable device of the standalone type instead of the first mobile device, wherein the wearable device is unable to receive a call, according to an exemplary embodiment.

[563] Referring to FIG. 31, it is assumed that the wearable device 50 of the standalone type is connectable only to the first mobile device 20 and is not connectable to the second mobile device 30.

WO 2016/018017 PCT/KR2015/007785 [564] In operation 3101, the wearable device 50 requests the first mobile device 20 for a connection.

[565] In operation 3102, the wearable device 50 and the first mobile device 20 synchronizes recent call histories.

[566] In operation 3103, the wearable device 50 is set as a primary receiving device for receiving a call ahead of the first mobile device 20.

[567] In operation 3104, the first mobile device 20 is set as a backup receiving device for receiving a call when the wearable device 50 is unable to receive a call.

[568] In operation 3105, since the wearable device 50 is the primary receiving device, the wearable device 50 is in a standby state.

[569] In operation 3106, when an external source (for example, a third person) requests a phone call, the server 10 of the mobile carrier transmits a phone call request to the wearable device 50 set as the primary receiving device.

[570] In operation 3107, the wearable device 50 notifies the user of the incoming call.

[571] In operation 3108, the wearable device 50 transmits information about the incoming call to the first mobile device 20.

[572] In operation 3109, the first mobile device 20 notifies the user of the incoming call.

[573] In operation 3110, when the wearable device 50 does not answer the incoming call for a certain period of time, the server 10 of the mobile carrier changes a receiving device to the first mobile device 20.

[574] In operation 3111, the server 10 re-transmits the phone call request to the first mobile device 20 that is set as the backup receiving device.

[575] In operation 3112, the first mobile device 20 answers the incoming call according to the phone call request from the server 10 of the mobile carrier.

[576] In operation 3113, the first mobile device 20 hangs up when the incoming call is terminated.

[577] In operation 3114, when the incoming call is terminated, the first mobile device 20 notifies the wearable device 50 of the terminated incoming call.

[578] In operation 3115, the wearable device 50 updates a recent call history based on information about the terminated incoming call.

[579] In operation 3116, the first mobile device 20 also updates a recent call history based on the information about the terminated incoming call.

[580] FIG. 32 is a timing diagram of a method of performing a phone call by the first mobile device 20 connected to the wearable device 50 of a companion type, according to an exemplary embodiment.

[581] Referring to FIG. 32, it is assumed that the wearable device 50 of the companion type is connectable only to the first mobile device 20 and is not connectable to the second mobile device 30.

WO 2016/018017 PCT/KR2015/007785 [582] In operation 3201, the wearable device 50 and the first mobile device 20 are connected to each other via wireless communication.

[583] In operation 3202, the first mobile device 20 is set to a standby state.

[584] In operation 3203, when an external source (for example a third person) requests a phone call, the server 10 of the mobile carrier transmits a phone call request to the first mobile device 20. Since the wearable device 50 is the companion type unlike FIGS. 30 and 31, the server 10 of the mobile carrier may not transmit the phone call request directly to the wearable device 50.

[585] In operation 3204, the first mobile device 20 notifies the user of the incoming call.

[586] In operation 3205, the first mobile device 20 transmits information about the incoming call to the wearable device 50.

[587] In operation 3206, the wearable device 50 notifies the user of the incoming call.

[588] In operation 3207, the user of the first mobile device 20 answers the incoming call using the first mobile device 20.

[589] In operation 3208, the first mobile device 20 notifies the wearable device 50 of the answered incoming call.

[590] In operation 3209, the first mobile device 20 hangs up when the incoming call is terminated.

[591] In operation 3210, when the incoming call is terminated, the first mobile device 20 notifies the wearable device 50 of the terminated incoming call.

[592] In operation 3211, the wearable device 50 updates a recent call history based on information about the terminated incoming call.

[593] In operation 3212, the first mobile device 20 also updates a recent call history based on the information about the terminated incoming call.

[594] FIG. 33 is a timing diagram of a method of receiving a call made to the first mobile device 20 by the wearable device 50 of the companion type, according to an exemplary embodiment.

[595] Referring to FIG. 33, it is assumed that the wearable device 50 of the companion type is connectable only to the first mobile device 20 and is not connectable to the second mobile device 30.

[596] In operation 3301, the wearable device 50 and the first mobile device 20 are connected to each other via wireless communication.

[597] In operation 3302, the first mobile device 20 is set to a standby state.

[598] In operation 3303, when an external source (for example a third person) requests a phone call, the server 10 of the mobile carrier transmits a phone call request to the first mobile device 20. Since the wearable device 50 is the companion type unlike FIGS. 30 and 31, the server 10 of the mobile carrier may not transmit the phone call request directly to the wearable device 50.

WO 2016/018017 PCT/KR2015/007785 [599] In operation 3304, the first mobile device 20 notifies the user of the incoming call.

[600] In operation 3305, the first mobile device 20 transmits information about the incoming call to the wearable device 50.

[601] In operation 3306, the wearable device 50 the user of the incoming call.

[602] In operation 3307, the user of the wearable device 50 answers the incoming call using the wearable device 50.

[603] In operation 3308, the first mobile device 20 forwards the phone call request to the wearable device 50.

[604] In operation 3309, the wearable device 50 hangs up when the incoming call is terminated.

[605] In operation 3310, when the incoming call is terminated, the wearable device 50 notifies the first mobile device 20 of the terminated incoming call.

[606] In operation 3311, the wearable device 50 updates a recent call history based on information about the terminated incoming call.

[607] In operation 3312, the first mobile device 20 also updates a recent call history based on the information about the terminated incoming call.

[608] FIG. 34 is a timing diagram of a method of performing a phone call by the wearable device 50 of the standalone type, instead of the second mobile device 30 that is a cardtype phone, according to an exemplary embodiment.

[609] Referring to FIG. 34, it is assumed that the wearable device 50 of the standalone type is connectable only to the second mobile device 30 and is not connectable to the first mobile device 20.

[610] In operation 3401, the wearable device 50 requests the second mobile device 30 for a connection. A method of connecting the wearable device 50 and the second mobile device 30 may include any one of various short-range wireless communication methods, such as Wi-Fi, Wi-Fi direct, Bluetooth, and NFC.

[611] In operation 3402, the wearable device 50 and the second mobile device 30 synchronizes recent call histories. The synchronizing of the recent call histories may be performed in the similar manner as that performed between the first and second mobile devices 20 and 30 described above with reference to FIG. 28.

[612] In operation 3403, the wearable device 50 is set as a primary receiving device for receiving a call ahead of the second mobile device 30.

[613] In operation 3404, the second mobile device 30 is set as a backup receiving device for receiving a call when the wearable device 50 is unable to receive a call.

[614] In operation 3405, since the wearable device 50 is the primary receiving device, the wearable device 50 is in a standby state.

[615] In operation 3406, when an external source (for example, a third person) requests a phone call, the server 10 of the mobile carrier transmits a phone call request to the

WO 2016/018017

PCT/KR2015/007785 wearable device 50 set as the primary receiving device. According to FIG. 34, a phone number of the second mobile device 30 is +82-10-AAAA-BBBB and a phone number of the wearable device 50 is +82-10-CCCC-DDDD. However, as described above with reference to FIG. 29, since the server 10 of the mobile carrier maps the phone numbers of the second mobile device 30 and the wearable device 50, and manages a main phone number of the user of the second mobile device 30 and the wearable device 50 to be +82-10-AAAA-BBBB, that is, the phone number of the first mobile device 20, the external source (the third person) may not be aware that +82-10-CCCC-DDDD is the phone number of the wearable device 50. In other words, the external source (the third person) makes a call to the second mobile device 30 or the wearable device 50 using only the phone number +82-10-AAAA-BBBB.

[616] In operation 3407, the wearable device 50 notifies the user of the incoming call.

[617] In operation 3408, the wearable device 50 transmits information about the incoming call to the second mobile device 30.

[618] In operation 3409, the second mobile device 30 notifies the user of the incoming call.

[619] In operation 3410, the wearable device 50 answers the incoming call according to the phone call request from the server 10 of the mobile carrier.

[620] In operation 3411, the wearable device 50 hangs up when the incoming call is terminated.

[621] In operation 3412, when the incoming call is terminated, the wearable device 50 notifies the second mobile device 30 of the terminated incoming call.

[622] In operation 3413, the wearable device 50 updates a recent call history based on information about the terminated incoming call.

[623] In operation 3414, the second mobile device 30 also updates a recent call history based on the information about the terminated incoming call.

[624] FIG. 35 is a timing diagram of a method of performing a phone call by the wearable device 50 of the standalone type instead of the second mobile device 30, wherein the wearable device 50 is unable to receive a call, according to an exemplary embodiment.

[625] Referring to FIG. 35, it is assumed that the wearable device 50 of the standalone type is connectable only to the second mobile device 30 and is not connectable to the first mobile device 20.

[626] In operation 3501, the wearable device 50 requests the second mobile device 30 for a connection.

[627] In operation 3502, the wearable device 50 and the second mobile device 30 synchronizes recent call histories.

[628] In operation 3503, the wearable device 50 is set as a primary receiving device for receiving a call ahead of the second mobile device 30.

[629] In operation 3504, the second mobile device 30 is set as a backup receiving device

WO 2016/018017

PCT/KR2015/007785 for receiving a call when the wearable device 50 is unable to receive a call.

[630] In operation 3505, since the wearable device 50 is the primary receiving device, the wearable device 50 is in a standby state.

[631] In operation 3506, when an external source (for example, a third person) requests a phone call, the server 10 of the mobile carrier transmits a phone call request to the wearable device 50 set as the primary receiving device.

[632] In operation 3507, the wearable device 50 notifies the user of the incoming call.

[633] In operation 3508, the wearable device 50 transmits information about the incoming call to the second mobile device 30.

[634] In operation 3509, the second mobile device 30 notifies the user of the incoming call.

[635] In operation 3510, when the wearable device 50 does not answer the incoming call for a certain period of time, the server 10 of the mobile carrier changes a receiving device to the second mobile device 30, which is the backup receiving device.

[636] In operation 3511, the server 10 re-transmits the phone call request to the second mobile device 30 that is set as the backup receiving device.

[637] In operation 3512, the second mobile device 30 answers the incoming call according to the phone call request from the server 10 of the mobile carrier.

[638] In operation 3513, the second mobile device 30 hangs up when the incoming call is terminated.

[639] In operation 3514, when the incoming call is terminated, the second mobile device 30 notifies the wearable device 50 of the terminated incoming call.

[640] In operation 3515, the wearable device 50 updates a recent call history based on information about the terminated incoming call.

[641] In operation 3516, the second mobile device 30 also updates a recent call history based on the information about the terminated incoming call.

[642] FIG. 36 is a timing diagram of a method of performing a phone call by the second mobile device 30 connected to the wearable device 50 of the companion type, according to an exemplary embodiment.

[643] Referring to FIG. 36, it is assumed that the wearable device 50 of the companion type is connectable only to the second mobile device 30 and is not connectable to the first mobile device 20.

[644] In operation 3601, the wearable device 50 and the second mobile device 30 are connected to each other via wireless communication.

[645] In operation 3602, the second mobile device 30 is set to a standby state.

[646] In operation 3603, when an external source (for example a third person) requests a phone call, the server 10 of the mobile carrier transmits a phone call request to the second mobile device 30. Since the wearable device 50 is the companion type, the server 10 of the mobile carrier may not transmit the phone call request directly to the

WO 2016/018017 PCT/KR2015/007785 wearable device 50.

[647] In operation 3604, the second mobile device 30 notifies the user of the incoming call.

[648] In operation 3605, the second mobile device 320 transmits information about the incoming call to the wearable device 50.

[649] In operation 3606, the wearable device 50 notifies the user of the incoming call.

[650] In operation 3607, the user of the second mobile device 30 answers the incoming call using the second mobile device 30.

[651] In operation 3608, the second mobile device 30 notifies the wearable device 50 of the answered incoming call.

[652] In operation 3609, the second mobile device 30 hangs up when the incoming call is terminated.

[653] In operation 3610, when the incoming call is terminated, the second mobile device 30 notifies the wearable device 50 of the terminated incoming call.

[654] In operation 3611, the wearable device 50 updates a recent call history based on information about the terminated incoming call.

[655] In operation 3612, the second mobile device 30 also updates a recent call history based on the information about the terminated incoming call.

[656] FIG. 37 is a timing of a method of receiving a call made to the second mobile device 30 by the wearable device 50 of the companion type, according to an exemplary embodiment.

[657] Referring to FIG. 37, it is assumed that the wearable device 50 of the companion type is connectable only to the second mobile device 30 and is not connectable to the first mobile device 20.

[658] In operation 3701, the wearable device 50 and the second mobile device 30 are connected to each other via wireless communication.

[659] In operation 3702, the second mobile device 30 is set to a standby state.

[660] In operation 3703, when an external source (for example a third person) requests a phone call, the server 10 of the mobile carrier transmits a phone call request to the second mobile device 30. Since the wearable device 50 is the companion type, the server 10 of the mobile carrier may not transmit the phone call request directly to the wearable device 50.

[661] In operation 3704, the second mobile device 30 notifies the user of the incoming call.

[662] In operation 3705, the second mobile device 30 transmits information about the incoming call to the wearable device 50.

[663] In operation 3706, the wearable device 50 notifies the user of the incoming call.

[664] In operation 3707, the user of the wearable device 50 answers the incoming call using the wearable device 50.

[665] In operation 3708, the second mobile device 30 forwards the phone call request to

WO 2016/018017 PCT/KR2015/007785 the wearable device 50.

[666] In operation 3709, the wearable device 50 hangs up when the incoming call is terminated.

[667] In operation 3710, when the incoming call is terminated, the wearable device 50 notifies the second mobile device 30 of the terminated incoming call.

[668] In operation 3711, the wearable device 50 updates a recent call history based on information about the terminated incoming call.

[669] In operation 3712, the second mobile device 30 also updates a recent call history based on the information about the terminated incoming call.

[670] As described above, according to one or more exemplary embodiments, since a user may use several mobile devices on a mobile communication system using one phone number without having to manage the several mobile devices having different phone numbers, a user owning several mobile devices may receive a mobile communication service via one of the several mobile devices based on his/her situation. Also, the inconvenience of managing different phone numbers of the several mobile devices may be reduced, and other users need not memorize different phone numbers.

[671] One or more exemplary embodiments may also be realized in a form of a computerreadable recording medium, such as a program module executed by a computer. A computer-readable recording medium may be a non-transitory computer-readable recording medium. A computer-readable recording medium may be an arbitrary available medium accessible by a computer, and examples thereof include all volatile and non-volatile media and separable and non-separable media. Further, examples of the computer-readable recording medium may include a computer storage medium and a communication medium. Examples of the computer storage medium include all volatile and non-volatile media and separable and non-separable media, which have been implemented by an arbitrary method or technology, for storing information such as computer-readable commands, data structures, program modules, and other data. The communication medium typically include a computer-readable command, a data structure, a program module, other data of a modulated data signal, or another transmission mechanism, and an example thereof includes an arbitrary information transmission medium.

[672] Also, herein, a unit may be a hardware component, such as a processor or a circuit, and/or a software component executed by a hardware component, such as a processor.

[673] While certain exemplary embodiments have been shown and described, it will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present invention as defined by the following claims and their equivalents. Hence, it will be understood that the certain exemplary embodiments described above are not limiting.

2015297192 18 Apr 2018

For example, each component described in a single type may be executed in a distributed manner, and components described distributed may also be executed in an integrated form.

[674] The scope of the present invention is indicated by the claims and their equivalents rather than the detailed description, and it should be understood that the claims and all modifications or modified forms drawn from the concept of the claims and their equivalents are included in the scope of the present invention.

[675] Where any or all of the terms comprise, comprises, comprised or comprising are used in this specification (including the claims) they are to be interpreted as specifying the presence of the stated features, integers, steps or components, but not precluding the presence of one or more other features, integers, steps or components.

2015297192 18 Apr 2018 [Claim 1] [Claim 2] [Claim 3] [Claim 4] [Claim 5]

Claims

Claims

A second mobile device configured to share a phone number of a first mobile device on a mobile communication system, the second mobile device comprising:

a communication interface configured to download a Subscriber Identification Module (SIM) information from a server when a call function of the second mobile device is activated;

a subscriber information module (SIM) configured to store the downloaded SIM information; and a controller configured to determine whether a call function of the first mobile device is deactivated and to activate the call function of the second mobile device based on the call function of the first mobile device being deactivated and a phone number of the first mobile device being assigned to the second mobile device, wherein the controller controls the communication interface to transmit a request for using the downloaded SIM information to the server, and the controller activates the call function of the second mobile device in response to receiving an approval from the server.

The second mobile device of claim 1, wherein the SIM information comprises subscription information of the second mobile device corresponding to the phone number on the mobile communication system on which the first mobile device and the second mobile device exist.

The second mobile device of claim 2, wherein the communication interface is further configured to:

transmit a request to the server for the SIM information in response to the call function of the second mobile device being activated, and receive the SIM information in response to the request for the SIM information.

The second mobile device of any one of claims 1 to 3, further comprising a storage having stored thereon device identification (ID) information having a different value from a device ID information of the another mobile device.

The second mobile device of claim 4, wherein the device ID information of the first mobile device comprises at least one of a serial number and an international mobile equipment identity (IMEI) of the first mobile device, and the device ID information of the second mobile device comprises at least one of a serial number and an IMEI of the mobile device.

2015297192 18 Apr 2018 [Claim 6] [Claim 7] [Claim 8] [Claim 9]

The second mobile device of any one of claims 1 to 5, wherein the communication interface is further configured to: connect to the first mobile device using short-range wireless communication, and exchange information about an activation state of the call function of the first mobile device and an activation state of the call function of the second mobile device with the first mobile device, and the controller is further configured to activate the call function of the second mobile device based on the exchanged information.

The second mobile device of claim 6, wherein the controller is further configured to automatically activate the call function of the second mobile device based on the call function of the first mobile device being deactivated and the phone number of the first mobile device being assigned to the second mobile device.

The second mobile device of claim 6, further comprising a user interface (UI) configured to provide a popup UI for setting an activation state of the call function of the second mobile device, wherein the controller is further configured to, in response to a user input to set the activation state of the call function of the second mobile device to active being input through the popup UI, activate the call function of the second mobile device.

A mobile communication system comprising:

a first mobile device configured to perform a call function using a first subscriber identification module (SIM) information comprising subscription information of a phone number registered with the mobile communication system;

a second mobile device configured to perform a call function using second SIM information comprising the subscription information of the phone number; and a server configured to:

receive requests to use the first SIM information and requests to use the second SIM information, and connect, in response to the phone number being requested to be called, a phone call to a mobile device corresponding to the requested first SIM information or the request second SIM information, wherein the first mobile device is configured to determine whether the call function of the second mobile device is deactivated, activate the call

2015297192 18 Apr 2018 [Claim 10] [Claim 11] function of the first mobile device when it is determined by the first mobile device that the call function of the second mobile device is deactivated, download the first SIM information from the server when the call function of the first mobile device is activated, wherein the first mobile device transmits a request to use the downloaded first SIM information to the server, and activates the call function of the first mobile device in response to receiving an approval from the server, and wherein the second mobile device is configured to determine whether the call function of the first mobile device is deactivated, activate the call function of the second mobile device based on the call function of the first mobile device being deactivated and the phone number being assigned to the second mobile device, and download the second SIM information from the server when the call function of the second mobile device is activated, and wherein the second mobile device transmits a request to use the downloaded second SIM information to the server, and activates the call function of the second mobile device in response to receiving an approval from the server.

The mobile communication system of claim 9, wherein the first mobile device is configured to:

transmit a request that the server transmit the first SIM information in response to the call function of the first mobile device being activated; and the second mobile device is configured to:

transmit a request that the server transmit the second SIM information in response to the call function of the second mobile device being activated. A method of providing, by a second mobile device sharing a phone number of a first mobile device, a mobile communication device, the method comprising:

determining, by the second mobile device, whether a call function of the first mobile device is deactivated and to activate a call function of the second mobile device based on the call function of the first mobile device being deactivated and a phone number of the first mobile device being assigned to the second mobile device;

downloading, by the second mobile device, a Subscriber Identification Module (SIM) information from a server; transmitting, by the second mobile device, a request to use the downloaded SIM information to the server; and

2015297192 18 Apr 2018 in response to receiving an approval from the server, activating, by the second mobile device, a call function of the second mobile device to which the phone number of the first mobile device is assigned when it is determined by the second mobile device that the call function of the first mobile device is deactivated.

1/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 1] <SMART PHONE: +82-1O-XXXX-XXXX>

<USER A>

<USER A>

[Fig. 2]

Wo ²°!6/0l80i₇
2/66

I

I ^PCT,K«mis/_w?7ss
3/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 3]

LO

CO

O

CO
4/66

WO 2016/018017 [Fig. 4]

PCT/KR2015/007785

SECOND MOBILE DEVICE
5/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 5]
6/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 6] +82-10-AAAA-BBBB +82-10-AAAA-BBBB

LU o

>

LU

Q

LU _I

CO o

cc

LU I— co

O

LU cc o

CM co

LU

O

LU

Q

LU

CO o

co Z> CO □c LU I— co o

LU cr cn co co co co

I $

<

<c

I

CM

CO

I θ

o

LO co o

LU <

O >

□c o

\

Λ □□ cr

LU co

Z)

V o +

LU cr cr o
7/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 7] o

>

L±J □

LU _l m

O

CO <

LU

O <

m

=) co co <
8/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 8A] s z / \
9/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 8B]

CO

LU >Q

O O DC o

o co co

Λ

LU

Q

O

O =E □_

LU

O_ >I—

I

Q

CC <

o o

cc co

LU ><

! CL Z

I I Z ' O O

I o ' F- — ( V Q
10/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 9] o

Cd

0QID
11/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 10A] o
12/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 10B]
13/66

WO 2016/018017 [Fig. IOC]

PCT/KR2015/007785 /' / \
14/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 10D] o
15/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 10E]
16/66

WO 2016/018017

PCT/KR2015/007785 [Fig. UA]
17/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 1 IB] in IS
18/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 12A]

A

CO o

-Ω

CO

Ό

CO

O o

O

V
19/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 12B]

A

C\J

Zf>

_o

-Ω

CO

T3

CO

O

O “O

V
20/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 13A] +82-10-AAAA-BBBB +82-10-AAAA-BBBB

TRY CALL CONNECTION (1309
21/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 13B] +82-10-AAAA-BBBB +82-10-AAAA-BBBB
22/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 13C] +82-10-AAAA-BBBB +82-10-ΑΑΑΑ-ΒΒΒΒ

TRY CALL CONNECTIONS 329)
23/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 13D] +82-10-AAAA-BBBB +82-10-AAAA-BBBB
24/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 14A] +82-10-AAAA-BBBB +82-10-AAAA-BBBB

TRY CALL CONNECTION 41 Qi
25/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 14B] +82-10-AAAA-BBBB +82-10-AAAA-BBBB
26/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 14C] +82-10-AAAA-BBBB +82-10-ΑΑΑΑ-ΒΒΒΒ

TRY CALL CONNECTIONQ430'
27/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 14D] +82-10-AAAA-BBBB +82-10-ΑΑΑΑ-ΒΒΒΒ
28/66

WO 2016/018017

PCT/KR2015/007785

CO _ω _Ω co

Ό

CO _o c= o

O

V

CO _o

ZD

CO

T5

CO

O c= £

o

Ό

V
29/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 16A] +82-1O-AAAA-BBBB +82-10-ΑΑΑΑ-ΒΒΒΒ
30/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 16B] +82-10-AAAA-BBBB +82-10-AAAA-BBBB
31/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 16C] +82-10-AAAA-BBBB +82-10-ΑΑΑΑ-ΒΒΒΒ

32/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 16D] +82-10-AAAA-BBBB +82-1Ο-ΑΑΑΑ-ΒΒΒΒ ο

co

_ CM co CO CO co CO LU — Q TION 0 2 Λ <c LU CC Z o 0 □c Ll_ LU — o_ CO 75 CO 0 r 1— cn cc £ 1— 1 Ll_ 1— 0 LU LU cc CO ΣΣΣ co 0 CO GD l·— _1 -ΣΣ. CO co z EC CM co co CO CO CO CO 1 1 1 0 CO \ O <c MODI z 0 _1 CD Λ cc 0 NE <c cr — Ll_ 0 D_ LU CO co 1 =3 ΓΊ O V $ O O 1— LLl CO LU LU CO CC 0 co

LO

CO

CO o

ίο:

cr o

co

Q co

LLf

CO o

LU

OC cr

I CO I CO ι <

I o I >! DC I Iι

33/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 17A] +82-1O-AAAA-BBBB +82-10-ΑΑΑΑ-ΒΒΒΒ
34/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 17B]
35/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 17C] +82-10-AAAA-BBBB +82-10-ΑΑΑΑ-ΒΒΒΒ
36/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 17D]
37/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 18A]

O I— co i

LU

CE

Q_

CO

V
38/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 18B]

O

O

LUCO^ i#2

O-Z.

i-O //

LU^

2cr οθ ljJll □C

I—^— coco <

cr

I— nk

COM @am cr

O

LL

CO

Q

Z

O o

LLI

CO

LU cr O I— co I

LU cr

Cl

CM

CO

V
39/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 19A] +82-10-ΑΑΑΑ-ΒΒΒΒ +82-10-ΑΑΑΑ-ΒΒΒΒ
40/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 19B] +82-1O-AAAA-BBBB +82-10-ΑΑΑΑ-ΒΒΒΒ
41/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 19C] +82-10-AAAA-BBBB +82-10-ΑΑΑΑ-ΒΒΒΒ
42/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 19D] +82-10-AAAA-BBBB +82-10-ΑΑΑΑ-ΒΒΒΒ
43/66

WO 2016/018017

PCT/KR2015/007785 +82-1O-AAAA-BBBB +82-1O-AAAA-BBBB [Fig. 20Α]

TRY CALL CONNECTION (2011
44/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 20Β] +82-10-AAAA-BBBB +82-10-ΑΑΑΑ-ΒΒΒΒ
45/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 20C] +82-10-AAAA-BBBB +82-10-ΑΑΑΑ-ΒΒΒΒ
46/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 20D] +82-10-AAAA-BBBB +82-10-ΑΑΑΑ-ΒΒΒΒ
47/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 21]

LU <

UJ

II

CO

CO
48/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 22A] \ ^v

TRY CALL CONNECTION (2208)

49/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 22B]

CM

OO +

CM

Z o

!<

CC

O

CM

-Σ. o CM CM o CM LU CM 1— <c Q O \ o CC o LL LL HONE IONE CO o_ u_ CL 1— o LU co cc LL 1— VAT STORE SET o 13? Si DEACTI m

CD

CO m

oo □c z

<

cc

CM

O

I— <

CC o

CM

03 Ι<

CC \ ^V co £ Ed

CO

O z: o

03 Q Z O o LU 03 LU CC O I— CO

O

ΣΕ

ΟΙ

O

CC □c □c Q_ 03 < I— LU CO

TRY CALL CONNECTION (2218)

50/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 22C]

TRY CALL CONNECTION(2228)

51/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 22D]

SIM INFORMATION M^- co CM CM \ -PHONE MODE 1— CO o CC U_ 1— LU CC LU o CO 1— co

o

ZC co m z o

-z. o co CM 1— CM LU < CC \ 1001 o 2 u_ LU o co Q CL ! CON wo- LU 1— CO 1— LU LU CC CO o co

co m p SZ. o z o

1^co

CM

CM o

□Ξ

Q_

LU

LU CO h- co

5 CM

CO _zLU O ig

CO z

S !

CO I CM I CM o

i— o LU

CALL-FORWARD BY USING WIRELESS

CONNECTION(2239)

52/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 22E]

TRY CALL CONNECTION (2248)
53/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 22F]

CALL-FORWARD BY USING WIRELESS

CONNECTION(2259)
54/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 23] [Fig. 24] [Fig. 25] <FIRST MOBILE DEVICE >

<SECOND MOBILE DEVICE>
55/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 26]

56/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 27]

2700

CM o 05 05 05 05 OO OO CO OO OO LU X X X X L_J X X X X X X X X o X X X X OO OO OO OO Z. LO LO LO LO • >- co CM CM CM CM zc zc zc ZC Q Q Q Q : : : : : : _1 _1 < II C 1 CO CO CO °4cm CM CO <tyCM IME OF iMING I V/N 15.04 M05:4 15.04 M03:3 15.04 MO9:1 : 1— o OCL OCL o< o CM CM CM — _1 _1 DF GCA 04.28 15:45 < < < . LU LO z Z z — o 50- ·—h- Cd =) o QC >- X X >- X X X X X X CQ X X X X X I I I X LO CO LO LO co CM CM 25 23 . LU LO CO co • z T— I I I 1 O o o LJ o ZC T— I I I Q_ +82- CM CM CM OO OO OO + + + CD C LU CD CD o o o <c CD Q Q • co cz CD • c CD _cz CZ k_ c o co CD CO J co CD

57/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 28]
58/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 29]

CO

QC

Ο<WEARABLE DEVICE>
59/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 30] o <+82-10-CCCC-DDDD> <+82-1O-AAAA-BBBB>

UPDATE RECENT CALL HISTORY UPDATE RECENT CALL HISTORY o

co \
60/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 31] <+82-10-CCCC-DDDD> <+82-10-AAAA~BBBB>
61/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 32]
62/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 33] <+82-10-AAAA-BBBB>

CONNECT WEARABLE DEVICE AND FIRST MOBILE DEVICE ¢3301)

SET TO STANDBY STATE —3302 TRANSMIT PHONE CALL REQUEST(3303) NOTIFY INCOMING CALL —3304

TRANSMIT INFORMATION ABOUT INCOMING CALL (3305)

NOTIFY INCOMING CALL —3306 I ANSWER INCOMING CALL —3307 FORWARD PHONE CALL REQUEST (3308) TERMINATE INCOMING CALL —3309 NOTIFY TERMINATED INCOMING CALL (3310) UPDATE RECENT CALL HISTORY —3311 UPDATE RECENT CALL HISTORY
63/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 34]
64/66

WO 2016/018017 PCT/KR2015/007785 [Fig. 35]
65/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 36]
66/66

WO 2016/018017

PCT/KR2015/007785 [Fig. 37]