Method and apparatus for moving call

An operation method and apparatus of a terminal for call move are provided. The method includes, if receiving a call move request signal including registration information of a first device that is in voice communication with a second device from the first device, transmitting, by the terminal, a call state request signal for the first device using the registration information to a server, if determining that a call state for the first device is not a call through the server by using a call state response signal received from the server, establishing, by the terminal, a wireless connection with the first device, and, performing, by the terminal, voice communication with the second device through the established wireless connection.

The present application is related to and claims priority under 35 U.S.C. §119(a) to a Korean Patent Application filed in the Korean Intellectual Property Office on Jul. 18, 2013, and assigned Serial No. 10-2013-0084800, the contents of which are herein incorporated by reference.

TECHNICAL FIELD

The present invention relates to call move between terminals in an enterprise network environment.

BACKGROUND

When a user intended to move a call from a desk phone to a mobile terminal, he/she can transfer the call using a transfer flow, or pressed a shortcut button of the desk phone to move the call to a mobile terminal of a number designated to the shortcut button.

And, when the user was in conversation through the mobile terminal, he/she may not be able to move a call from the mobile terminal to the desk phone, or could receive a service of only an extension call connected to an enterprise server.

In a case where the user used a service of call move between terminals in a terminal interworking with the enterprise server and providing a conversation service, there can be a limit that he/she could receive a service of only a call connected through the enterprise server.

That is, in a case where the user is making a mobile communication call through a 3-Generation/Long Term Evolution (3G/LTE) system, that the user may not be able to move a call to the desk phone even when desiring to do so.

SUMMARY

To address the above-discussed deficiencies, it is a primary object to provide a method and apparatus for moving a call.

In a first example, a method and apparatus are provided for, if there is a request for a service of call move between terminals, querying an enterprise server whether call move is possible and, if the call move is possible, moving a call through Voice over Internet Protocol (VoIP) signaling.

In a second example, a method and apparatus are provided for, if there is a request for a service of call move between terminals, querying an enterprise server whether call move is possible and, if the call move is impossible, providing a service capable of setting and connecting Bluetooth between the terminals and maintaining conversation.

In a third embodiment, an operation method of a terminal for call move includes, if receiving a call move request signal including registration information of a first device that is in voice communication with a second device from the first device, transmitting, by the terminal, a call state request signal for the first device using the registration information to a server. The method also includes if determining that a call state for the first device is not a call through the server by using a call state response signal received from the server, establishing, by the terminal, a wireless connection with the first device, and, performing, by the terminal, voice communication with the second device through the established wireless connection.

In a fourth example, an operation method of a server for call move includes receiving, by the server, a call state request signal for a first device from a terminal. The method also includes deciding, by the server, a call state for the first device using registration information of the 1stdevice included in the call state request signal. The method further includes in accordance to the decision of the call state for the first device, transmitting, by the server, a call state response signal to the terminal.

In a fifth example, an apparatus of a terminal for call move includes a communication unit configured to communicate with another node. The apparatus also includes a control unit. The control unit is configured to, if receiving a call move request signal including registration information of a first device that is in voice communication with a second device from the first device, control the communication unit to transmit a call state request signal for the first device to a server using the registration information. The control unit is also configured to if determining that a call state for the first device is not a call through the server by using a call state response signal received from the server, establish a wireless connection with the first device, and performing voice communication with the second device through the established wireless connection.

In a sixth example, an apparatus of a server for call move includes a communication unit configured to communicate with another node. The apparatus also includes a control unit. The control unit is configured to, if receiving a call state request signal for a first device from a terminal, decide a call state for the first device using registration information of the first device included in the call state request signal, and control the communication unit to transmit a call state response signal to the terminal, in accordance to the decision of the call state for the first device.

DETAILED DESCRIPTION

FIGS. 1 through 13, discussed below, and the various embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged communication terminal. Various exemplary embodiments of the present disclosure will be described herein below with reference to the accompanying drawings. In describing the present disclosure, well-known functions or constructions are not described in detail since they would obscure the disclosure in unnecessary detail. And, terms described below, which are defined considering functions in the present disclosure, can be modified in accordance to user and operator's intention or practice. Therefore, the definition should be given on the basis of the content throughout the present specification.

Below, the present disclosure will be described for a method and apparatus for moving a call.

The present disclosure relates to a method and apparatus for easily providing service setting and call move service, through data transmission/reception which uses Near Field Communication (NFC) and Bluetooth protocol between a terminal (e.g., a desk phone) interworking with an enterprise server and a mobile terminal (e.g., a Fixed Mobile Convergence (FMC) phone, and a cellular phone) of a user.

In the following description, the terminal and the mobile terminal includes a mobile communication terminal supporting wireless communication, a smart phone, a tablet Personal Computer (PC), a digital camera, a Moving Picture Experts Group (MPEG) Audio Layer 3 (MP3) player, a navigator, a laptop, a netbook, and the like.

FIG. 1is a block diagram illustrating an example structure of an enterprise network according to this disclosure.

Referring toFIG. 1, the enterprise network includes an enterprise server100, a desk phone150, and a mobile terminal170.

The enterprise server100includes a call service engine101, a subscriber state monitoring block102, and a subscriber setting/authorization/registration management block103. The subscriber setting/authorization/registration management block103can takes charge of a function of setting, authorizing and registering a subscriber to the enterprise server100. The call service engine101provides a call service to the registered subscriber. The subscriber state monitoring block102monitors a current state of a requested subscriber or a specific subscriber among subscribers. For example, the subscriber state monitoring block102decides whether the subscriber is receiving the call service through the enterprise server100.

The desk phone150includes a Voice over Internet Protocol (VoIP) service controller151, a service User Interface (UI)152, and a service setting management block153. The VoIP service controller151controls VoIP telephony. By providing a user interface to a user, receiving an instruction from the user through the user interface, and providing the instruction to the corresponding function block in accordance to the kind of the instruction, the service UI152enables the user to control the execution of a function of the desk phone150through the user interface. The service setting management block153takes charge of a function of interworking with the enterprise server100and the mobile terminal170.

Also, the desk phone150includes an authorized device list block154, a Bluetooth controller155, and an NFC Peer-to-Peer (P2P) block156. The authorized device list block154manages information about authorized terminals. The Bluetooth controller155performs Bluetooth communication. The NFC P2P block156takes charge of NFC communication.

The mobile terminal170includes an authorized device list block171, a Bluetooth controller172, and an NFC P2P block173. The authorized device list block171manages information about authorized terminals. The Bluetooth controller172performs Bluetooth communication. The NFC P2P block173takes charge of NFC communication.

The mobile terminal170includes a service list block174, and a service UI175. The service list block174manages interworking services with the desk phone150and the enterprise server100. By providing a user interface to a user, receiving an instruction from the user through the user interface, and providing the instruction to the corresponding function block in accordance to the kind of the instruction, the service UI175enables the user to control the execution of a function of the mobile terminal170through the user interface.

Also, the mobile terminal170includes a service setting management block176taking charge of a function of interworking with the enterprise server100and the desk phone150.

FIG. 2is a diagram schematically illustrating an example call move process between terminals according to this disclosure.

Referring toFIG. 2, a desk phone250receiving a call move request from a mobile terminal210can perform call move of the mobile terminal210which has requested a currently called/incoming call to an enterprise server200through VoIP signal transmission (step201).

Similarly, the desk phone250receiving a call move request from a mobile terminal270can perform call move of the mobile terminal270which has requested a currently called/incoming call to the enterprise server200through VoIP signal transmission (step202).

This case is a case in which a call on busy goes through the enterprise server200.

However, the aforementioned call move is not possible when conversation is being carried out from the mobile terminal210to the mobile terminal270through a call not going through the enterprise server200.

The present disclosure includes querying the enterprise server200whether call move is possible and, if the call move is possible, performing the call move using the enterprise server200(steps201and202) and, if the call move is impossible, establishing an audio path from the mobile terminal270to the desk phone250through Bluetooth connection and making possible the call move (step203).

In the present disclosure, a call move request between terminals can be achieved through NFC communication. At NFC communication, a Bluetooth Media Access Control (MAC) address is transmitted together with terminal information and thus, a Bluetooth pairing process can be performed at one time.

FIG. 3is a message flowchart illustrating an example call move process between terminals according to at least a 1st embodiment this disclosure.

Referring toFIG. 3, if there is a need to move a call of a mobile terminal370to a desk phone 2350during conversation with a desk phone 1310(step301), the mobile terminal370transmits a call move request to the desk phone 2350(step302).

This call move request can be performed by user's selection. And, the call move request between terminals can be achieved through NFC communication. At NFC communication, a Bluetooth MAC address is transmitted together with terminal information and thus, a Bluetooth pairing process can be performed at one time. Also, the call move request between the terminals can be transmitted using a dedicated application.

The call move request can include terminal registration information as follows. That is, the call move request can include information such as a phone number (such as a Mobile Identification Number (MIN)) or an extension phone number, a wireless Local Area Network (LAN) IP address and a wireless LAN MAC address (such as a wireless LAN IP address of a requesting terminal and a wireless LAN MAC address thereof), a request service type (such as a call move request), and a Bluetooth MAC address (such as a Bluetooth MAC address of the requesting terminal).

After that, the desk phone 2350transmits a call state request to an enterprise server300(step303). The call state request is to request a state of a call that the mobile terminal370has requested to move. The desk phone 2350transmits the call state request to the enterprise server300using a Session Initiation Protocol (SIP) message. The SIP message can be a message such as NOTIFY, INFO and the like. InFIG. 3, utilization of the NOTIFY message is disclosed.

Next, if it is determined that the call state is in FMC conversation (step304), the enterprise server300transmits to the desk phone 2350a response including that the call state is in the FMC conversation (step305). Here, the enterprise server300searches a database for a MIN or extension phone number of the mobile terminal370having requested call state information and performs MIN or extension phone number registration or non-registration and conversation state query. Here, the FMC represents an application performing a VoIP service using Wireless Fidelity (WiFi) wireless communication.

The response including that the call state is in the FMC conversation can be a 200 OK message among the SIP message. The enterprise server300can add a proprietary header within the 200 OK message and notify the database search result to the desk phone 2350.

Next, the desk phone 2350transmits a conversation connection for the call, to the enterprise server300(step306). Here, an INVITE message is used among the SIPmessage. Here, because the desk phone 2350has been notified from the enterprise server300that it is a state where the call move is possible, the desk phone 2350transmits to the enterprise server300an originating request of requesting to move the call to the desk phone 2350. After that, the enterprise server300transmits a response to the desk phone 2350(step307).

Next, the enterprise server300transmits a conversation update request to the desk phone 1310(step308). Here, a Re-INVITE message is used among the SIP message. The Re-INVITE message is a message of the same kind as that of the INVITE message or a message of requesting update for an existing established call. The call uses an existing call session between the desk phone 1310and the mobile terminal370.

The desk phone 1310receiving the conversation update request from the enterprise server300updates a codec, a Real-time Transport Protocol (RTP) destination address, a RTP destination port, and the like such that the desk phone 1310can make conversation with the desk phone 2350. That is, because the call has moved from the desk phone 1310to the desk phone 2350, the desk phone 1310updates the codec, the RTP destination address, the RTP destination port, and the like such that the desk phone 1310can make conversation with the desk phone 2350through the moved call. The codec, the RTP destination address, the RTP destination port, and the like can be forwarded through the Re-INVITE message. After that, the desk phone 1310transmits a response to the enterprise server300(step309). This represents that the call move is completed.

Next, the enterprise server300requests a conversation end to the mobile terminal370(step311). Here, a BYE message is used among the SIP message. Next, the mobile terminal370transmits a response to the enterprise server300(step312).

After that, conversation between the desk phone 1310and the desk phone 2350is carried out (step313). Meantime, while performing voice communication, the desk phone 1310and the desk phone 2350perform data communication including Dual Tone Multi Frequency (DTMF) information. If there is a DTMF input to the desk phone 2350, the desk phone 2350transmits information including the DTMF input to the desk phone 1310.

FIG. 4is a flowchart illustrating an example operation process of a desk phone 2 during a call move process between terminals according to at least the 1st embodiment of this disclosure.

Referring toFIG. 4, the desk phone 2 receives a call move request from a mobile terminal (step405). Here, it is a state where the mobile terminal is in conversation with a desk phone 1. This call move request can be performed by user's selection. And, the call move request between terminals can be achieved through NFC communication. At NFC communication, a Bluetooth MAC address is transmitted together with terminal information and thus, a Bluetooth pairing process can be performed at one time. Also, the call move request between the terminals can be transmitted using a dedicated application.

The call move request can include information as follows. That is, the call move request can include information such as a phone number (such as a MIN) or an extension phone number, a wireless LAN IP address and a wireless LAN MAC address (such as a wireless LAN IP address of a requesting terminal and a wireless LAN MAC address thereof), a request service type (such as a call move request), and a Bluetooth MAC address (such as a Bluetooth MAC address of the requesting terminal).

After that, the desk phone 2 transmits a call state request to an enterprise server (step410). The call state request is to request a state of a call that the mobile terminal has requested to move. The desk phone 2 transmits the call state request to the enterprise server using a SIP message. The SIP message can be a message such as NOTIFY, INFO and the like.

After that, if receiving from the enterprise server a response including that the call state is in FMC conversation (step415), the desk phone 2 transmits a conversation connection request for the call, to the enterprise server (step420). Here, an INVITE message is used among the SIP message. Here, because the desk phone 2 has been notified from the enterprise server that it is a state where the call move is possible, the desk phone 2 transmits to the enterprise server an originating request of requesting to move the call to the desk phone 2. After that, the desk phone 2 receives a response from the enterprise server (step425).

Here, the response including that the call state is in the FMC conversation can be a 200 OK message among the SIP message. The enterprise server can add a proprietary header within the 200 OK message and notify the database search result to the desk phone 2.

After that, the desk phone 2 makes conversation with the desk phone 1 (step430). Next, if DTMF information is inputted to the desk phone 2 while voice communication is carried out between the desk phone 1 and the desk phone 2, the desk phone 2 transmits the inputted DTMF information to the desk phone 1.

FIG. 5is a flowchart illustrating an example operation process of an enterprise server during a call move process between terminals according to at least the 1st embodiment of this disclosure.

Referring toFIG. 5, the enterprise server receives a call state request from a desk phone 2 (step505). The call state request is to request a state of a call that the mobile terminal has requested to move. The desk phone 2 transmits the call state request to the enterprise server using a SIP message. The SIP message can be a message such as NOTIFY, INFO and the like.

Next, the enterprise server determines the call state (step510). If it is determined that the call state is in FMC conversation, the enterprise server transmits to the desk phone 2 a response including that the call state is in the FMC conversation (step515). Here, the enterprise server searches a database for a MIN or extension phone number of the mobile terminal having requested call state information and performs MIN or extension phone number registration or non-registration and conversation state query. Here, the FMC represents an application performing a VoIP service using WiFi wireless communication.

The response including that the call state is in the FMC conversation can be a 200 OK message among the SIP message. The enterprise server can add a proprietary header within the 200 OK message and notify the database search result to the desk phone 2.

Next, the enterprise server receives a conversation connection request for the call, from the desk phone 2 (step520). Here, an INVITE message is used among the SIP message. Here, because the desk phone 2 has been notified from the enterprise server that it is a state where the call move is possible, the desk phone 2 transmits to the enterprise server an originating request of requesting to move the call to the desk phone 2.

After that, the enterprise server transmits a response to the desk phone 2 (step525).

Next, the enterprise server transmits a conversation update request (such as a call update request) to the desk phone 1 (step530). Here, a Re-INVITE message is used among the SIP message. The Re-INVITE message is a message of the same kind as that of the INVITE message or a message of requesting update for an existing established call. The call uses an existing call session between the desk phone 1 and the mobile terminal.

After that, the enterprise server receives a response from the desk phone 1 (step535). This represents that the call move is completed.

Next, the enterprise server requests a conversation end to the mobile terminal (step540). Here, a BYE message is used among the SIP message. After that, the enterprise server receives a response from the mobile terminal (step545). Next, conversation between the desk phone 1 and the desk phone 2 is performed.

FIG. 6is a flowchart illustrating an example operation process of a mobile terminal during a call move process between terminals according to at least the 1st embodiment of this disclosure.

Referring toFIG. 6, if there is a need to move a call of the mobile terminal to a desk phone 2 during conversation with a desk phone 1, the mobile terminal transmits a call move request to the desk phone 2 (step605).

This call move request can be performed by user's selection. And, the call move request between terminals can be achieved through NFC communication. At NFC communication, a Bluetooth MAC address is transmitted together with terminal information and thus, a Bluetooth pairing process can be performed at one time. Also, the call move request between the terminals can be transmitted using a dedicated application.

The call move request can include terminal registration information as follows. That is, the call move request can include information such as a phone number or an extension phone number, a wireless LAN IP address and a wireless LAN MAC address (such as a wireless LAN IP address of a requesting terminal and a wireless LAN MAC address thereof), a request service type (such as a call move request), and a Bluetooth MAC address (such as a Bluetooth MAC address of the requesting terminal).

After that, the mobile terminal receives a conversation end request from an enterprise server (step610). Here, a BYE message is used among the SIP message. Next, the mobile terminal transmits a response to the enterprise server (step620).

After that, conversation between the desk phone 1 and the desk phone 2 is performed.

FIG. 7is a message flowchart illustrating an example call move process between terminals according to at least a 2nd embodiment this disclosure.

Referring toFIG. 7, if there is a need to move a call of a mobile terminal 2770to a desk phone750during conversation with a mobile terminal710(step701), the mobile terminal 2770transmits a call move request to the desk phone750(step702).

This call move request can be performed by user's selection. And, the call move request between terminals can be achieved through NFC communication. At NFC communication, a Bluetooth MAC address is transmitted together with terminal information and thus, a Bluetooth pairing process can be performed at one time. Also, the call move request between the terminals can be transmitted using a dedicated application.

The call move request can include registration information as follows. That is, the call move request can include information such as a phone number or an extension phone number, a wireless LAN IP address and a wireless LAN MAC address (such as a wireless LAN IP address of a requesting terminal and a wireless LAN MAC address thereof), a request service type (such as a call move request), and a Bluetooth MAC address (such as a Bluetooth MAC address of the requesting terminal).

After that, the desk phone750transmits a call state request to an enterprise server700(step703). The call state request is to request a state of a call that the mobile terminal 2770has requested to move. The desk phone750transmits the call state request to the enterprise server700using a SIP message. The SIP message can be a message such as NOTIFY, INFO and the like. InFIG. 7, utilizing the NOTIFY message is disclosed.

Next, if it is determined that the call state is not in FMC conversation (step704), the enterprise server700transmits to the desk phone750a response including that the call state is not in the FMC conversation (step705). Here, the enterprise server700searches a database for a MIN or extension phone number of the mobile terminal 2770having requested call state information and performs MIN or extension phone number registration or non-registration and conversation state query. Here, the FMC represents an application performing a VoIP service using WiFi wireless communication.

The response including that the call state is not in the FMC conversation can be a200OK message among the SIP message. The enterprise server700can add a proprietary header within the 200 OK message and notify the database search result to the desk phone750.

After that, the desk phone750recognizes that the call state received from the enterprise server700is not in the FMC conversation, that is, recognizes that the received call state is a call not going through the enterprise server700. And then, the desk phone750establishes a conversation path using wireless connection (such as Bluetooth, WiFi) with the mobile terminal 2770, and perform conversation with the mobile terminal710through the established the wireless connection.

Upon receiving the call move request of the mobile terminal 2770, the desk phone750can acquire a Bluetooth MAC address of the mobile terminal 2770and perform Bluetooth pairing with the mobile terminal 2770. In the drawing, Synchronous Connection Oriented (SCO) represents a Bluetooth audio data transmission path.

The desk phone750can establish a Bluetooth data communication path with the mobile terminal 2770. If there is a DTMF input to the desk phone750, the desk phone750can transmit information including the DTMF input, to the mobile terminal 2770, and the mobile terminal 2770can transmit the information including the DTMF input, to a corresponding device.

FIG. 8is a flowchart illustrating an example operation process of a desk phone during a call move process between terminals according to at least the 2nd embodiment of this disclosure.

Referring toFIG. 8, a desk phone receives a call move request from a mobile terminal 2 (step805). This call move request can be performed by user's selection. And, the call move request between terminals can be achieved through NFC communication. At NFC communication, a Bluetooth MAC address is transmitted together with terminal information and thus, a Bluetooth pairing process can be performed at one time. Also, the call move request between the terminals can be transmitted using a dedicated application.

The call move request can include information as follows. That is, the call move request can include information such as a phone number or an extension phone number, a wireless LAN IP address and a wireless LAN MAC address (such as a wireless LAN IP address of a requesting terminal and a wireless LAN MAC address thereof), a request service type (such as a call move request), and a Bluetooth MAC address (such as a Bluetooth MAC address of the requesting terminal).

After that, the desk phone transmits a call state request to an enterprise server (step810). The call state request is to request a state of a call that the mobile terminal 2 has requested to move. The desk phone transmits the call state request to the enterprise server using a SIP message. The SIP message can be a message such as NOTIFY, INFO and the like.

Next, the desk phone receives a response that the call state is not in FMC conversation, from the enterprise server (step815).

The response including that the call state is not in the FMC conversation can be a 200 OK message among the SIP message. The enterprise server can add a proprietary header within the 200 OK message and notify the database search result to the desk phone.

After that, the desk phone recognizes that the call state received from the enterprise server is not in the FMC conversation, that is, recognizes that the received call state is a call not going through the enterprise server. And then, the desk phone establishes a conversation path using wireless connection (such as Bluetooth, WiFi) with the mobile terminal 2 (step820), and performs conversation with the mobile terminal through the established the wireless connection (step825).

Upon receiving the call move request of the mobile terminal 2, the desk phone can acquire a Bluetooth MAC address of the mobile terminal 2 and perform Bluetooth pairing with the mobile terminal 2.

Though not illustrated in the drawing, the desk phone can establish a Bluetooth data communication path with the mobile terminal 2. If there is a DTMF input to the desk phone, the desk phone can transmit information including the DTMF input, to the mobile terminal 2, and the mobile terminal 2 can transmit the information including the DTMF input, to a corresponding device being in conversation.

FIG. 9is a flowchart illustrating an example operation process of an enterprise server during a call move process between terminals according to at least the 2nd embodiment of this disclosure.

Referring toFIG. 9, the enterprise server receives a call state request from a desk phone (step905). The call state request is to request a state of a call that a mobile terminal 2 has requested to move. The desk phone transmits the call state request to the enterprise server using a SIP message. The SIP message can be a message such as NOTIFY, INFO and the like.

Next, the enterprise server determines the call state (step910). If it is determined that the call state is not in FMC conversation, the enterprise server transmits to the desk phone a response including that the call state is not in the FMC conversation (step915). Here, the enterprise server searches a database for a MIN or extension phone number of the mobile terminal 2 having requested call state information and performs MIN or extension phone number registration or non-registration and conversation state query. Here, the FMC represents an application performing a VoIP service using WiFi wireless communication.

The response including that the call state is not in the FMC conversation can be a 200 OK message among the SIP message. The enterprise server can add a proprietary header within the 200 OK message and notify the database search result to the desk phone.

FIG. 10is a flowchart illustrating an example operation process of a mobile terminal 2 during a call move process between terminals according to at least the 2nd embodiment of this disclosure.

Referring toFIG. 10, if there is a need to move a call of the mobile terminal 2 to a desk phone during conversation with a mobile terminal, the mobile terminal 2 transmits a call move request to the desk phone (step1005).

This call move request can be performed by user's selection. And, the call move request between terminals can be achieved through NFC communication. At NFC communication, a Bluetooth MAC address is transmitted together with terminal information and thus, a Bluetooth pairing process can be performed at one time. Also, the call move request between the terminals can be transmitted using a dedicated application.

The call move request can include registration information as follows. That is, the call move request can include information such as a phone number (such as a MIN) or an extension phone number, a wireless LAN IP address and a wireless LAN MAC address (such as a wireless LAN IP address of a requesting terminal and a wireless LAN MAC address thereof), a request service type (such as a call move request), and a Bluetooth MAC address (such as a Bluetooth MAC address of the requesting terminal).

After that, if sensing a wireless connection (e.g. Bluetooth, WiFi) request of the desk phone, the mobile terminal 2 establishes a conversation path using the wireless connection (e.g. Bluetooth, WiFi) with the desk phone (step1010), and performs conversation with the mobile terminal through the established Bluetooth path (step1015).

Upon receiving the call move request of the mobile terminal 2, the desk phone can acquire a Bluetooth MAC address of the mobile terminal 2 and perform Bluetooth pairing with the mobile terminal 2.

The desk phone can establish a Bluetooth data communication path with the mobile terminal 2. If there is a DTMF input to the desk phone, the desk phone can transmit information including the DTMF input, to the mobile terminal 2, and the mobile terminal 2 can transmit the information including the DTMF input, to a corresponding device being in conversation.

FIG. 11is a block diagram illustrating an example construction of a mobile terminal according to this disclosure.

Referring toFIG. 11, the mobile terminal1100can include one or more processors1110, a Subscriber Identification Module (SIM) card1114, a memory1120, a communication module1130, a sensor module1140, a user input module1150, a display module1160, an interface1170, an audio codec1180, a camera module1191, a power management module1195, a battery1196, an indicator1197, and a motor1198.

The processor1110can include one or more Application Processors (APs)1111or one or more Communication Processors (CPs)1113.

The processor1110is illustrated as the AP1111and the CP1113are included within the processor1110, but the AP1111and the CP1113can be included within different IC packages, respectively. In one exemplary embodiment, the AP1111and the CP1113can be included within one IC package.

The AP1111can drive an operating system or an application program and control a plurality of hardware or software constituent elements connected to the AP1111, and perform processing and operation of various data including multimedia data. The AP1111can be, for example, implemented as a System on Chip (SoC). According to one exemplary embodiment, the processor1110can further include a Graphic Processing Unit (GPU).

The CP1113can perform a function of managing a data link and converting a communication protocol in communication between a terminal including the hardware1100and other electronic devices connected through a network. The CP1113can be implemented as a SoC, for example. According to one exemplary embodiment, the CP1113can perform at least part of a multimedia control function. The CP1113can perform terminal distinction and authorization within a communication network, using a subscriber identity module (e.g., the SIM card1114). Also, the CP1113can provide services such as voice telephony, video telephony, a text message, packet data and the like to a user.

Also, the CP1113can control data transmission/reception of the communication module1130. AlthoughFIG. 11illustrates the constituent elements such as the CP1113, the power management module1195, the memory1120and the like as constituent elements separate from the AP1111, according to one exemplary embodiment, the AP1111can be implemented to include at least some (e.g., the CP1113) of the aforementioned constituent elements.

According to one exemplary embodiment, the AP1111or the CP1113can load to a volatile memory an instruction or data received from a non-volatile memory connected to each of the AP1111and the CP1113or at least one of other constituent elements, and process the loaded instruction or data. Also, the AP1111or the CP1113can store in the non-volatile memory data received from at least one of the other constituent elements or generated by at least one of the other constituent elements.

The SIM card1114can be a card implementing the subscriber identity module, and can be inserted into a slot provided in a specific location of an electronic device. The SIM card1114can include unique identification information (e.g., Integrated Circuit Card ID (ICCID)) or subscriber information (e.g., International Mobile Subscriber Identity (IMSI)).

The memory1120can include an internal memory1122or an external memory1124. The internal memory1122can include, for example, at least one of a volatile memory (e.g., a Dynamic Random Access Memory (DRAM), a Static Random Access Memory (SRAM), a Synchronous Dynamic Random Access Memory (SDRAM) and the like) or a non-volatile memory (e.g., a One Time PROM (OTPROM), a Programmable ROM (PROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), a mask Read Only Memory (ROM), a flash ROM, a Not AND (NAND) flash memory, a Not OR (NOR) flash memory and the like). According to one exemplary embodiment, the internal memory1122can also take a form of Solid State Drive (SSD). The external memory1124can further include, for example, Compact Flash (CF), Secure Digital (SD), Micro Secure Digital (Micro-SD), Mini Secure Digital (Mini-SD), extreme Digital (xD), a memory stick and the like.

The communication module1130can include a wireless communication module1131or a Radio Frequency (RF) module1134. The wireless communication module1131can include, for example, WiFi1133, Bluetooth (BT)1135, GPS1137and NFC1139. For example, the wireless communication module1131can provide a wireless communication function using radio frequency. Additionally or alternatively, the wireless communication module1131can include a network interface (e.g., a LAN card), a modem or the like for connecting the hardware1100with a network (e.g., the Internet, a LAN, a Wide Area Network (WAN), a telecommunication network, a cellular network, a satellite network, a Plain Old Telephone Service (POTS) or the like).

The RF module1134can take charge of transmission/reception of data, for example, transmission/reception of an RF signal or a called electronic signal. The RF module1134can include, though not illustrated, for example, a transceiver, a Power Amp Module (PAM), a frequency filter, a Low Noise Amplifier (LNA) or the like. Also, the RF module1134can further include a component for transmitting/receiving an electromagnetic wave on a free space in a wireless communication, for example, a conductor, a conductive line or the like.

The sensor module1140can include, for example, at least one of a gesture sensor1140A, a gyro sensor1140B, an air pressure sensor1140C, a magnetic sensor1140D, an acceleration sensor1140E, a grip sensor1140F, a proximity sensor1140G, a Red, Green, Blue (RGB) sensor1140H, a biological sensor1140I, a temperature/humidity sensor1140J, a light sensor1140K, and a Ultraviolet (UV) sensor1140M. The sensor module1140can measure a physical quantity or sense an activation state of the electronic device and convert measured or sensed information into an electrical signal. Additionally or alternatively, the sensor module1140can include, for example, an Electronic nose (E-nose) sensor, an Electromyography (EMG) sensor, an Electroencephalogram (EEG) sensor, an Electrocardiogram (ECG) sensor, a fingerprint sensor and the like. The sensor module1140can further include a control circuit for controlling at least one or more sensors provided therein.

The user input module1150can include a touch panel1152, a (digital) pen sensor1154, a key1156, and an ultrasonic input device1158. The touch panel1152can recognize, for example, a touch input in at least one method among a capacitive method, a pressure sensitive method, an infrared method, and an ultrasonic method. Also, the touch panel1152can also further include a controller. In the capacitive method, not only direct touch but also proximity recognition is possible. The touch panel1152can also further include a tactile layer. In this case, the touch panel1152can provide a tactile response to a user.

The (digital) pen sensor1154can be implemented, for example, using the same or similar method with receiving a user's touch input or a separate sheet for recognition. The key1156can be, for example, a keypad or a touch key. The ultrasonic input device1158is a device capable of determining data by sensing a sound wave with a microphone (e.g., a microphone1188) of the terminal, and can perform wireless recognition through a pen generating an ultrasonic signal. According to one exemplary embodiment, the hardware1100can also receive a user input from an external device (e.g., a network, a computer, or a server) connected to the mobile terminal1100using the communication module1130.

The display module1160can include a panel1162and a hologram1164. The panel1162can be, for example, a Liquid Crystal Display (LCD), an Active-Matrix Organic Light-Emitting Diode (AMOLED), or the like. The panel1162can be implemented to be flexible, transparent, or wearable, for example. The panel1162can be also constructed as one module together with the touch panel1152. The hologram1164can show a three-dimensional image in the air by using interference of light. According to one exemplary embodiment, the display module1160can further include a control circuit for controlling the panel1162and the hologram1164.

The interface1170can include, for example, a High-Definition Multimedia Interface (HDMI)1172, a Universal Serial Bus (USB)1174, a projector1176, and a D-subminiature (D-sub)1178. Additionally or alternatively, the interface1170can include, for example, Secure Digital (SD)/Multi Media Card (MMC) and Infrared Data Association (IrDA).

The audio codec1180can convert a voice and an electric signal interactively. The audio codec1180can convert, for example, voice information that is inputted or outputted through a speaker1182, a receiver1184, an earphone1186, the microphone1188, and the like.

The camera module1191is a device capable of taking an image and a video. According to one exemplary embodiment, the camera module1191can include one or more image sensors (e.g., a front lens or a rear lens), an Image Signal Processor (ISP), and a flash LED.

The power management module1195can manage power of the hardware1100. Though not illustrated, the power management module1195can include, for example, a Power Management Integrated Circuit (PMIC), a charger Integrated Circuit (IC), and a battery gauge.

The PMIC can be mounted, for example, within an integrated circuit or a SoC semiconductor. A charging method can be divided into wired and wireless. The charger IC can charge a battery, and can prevent the inflow of overvoltage or overcurrent from an electric charger. According to one exemplary embodiment, the charger IC can include a charger IC for at least one of a wired charging method and a wireless charging method. As the wireless charging method, there are a magnetic resonance method, a magnetic induction method, an electromagnetic method and the like, for example. The charger IC can be added with additional circuits for wireless charging, for example, circuits of a coil loop, a resonance circuit, a rectifier and the like.

The battery gauge can measure, for example, a level of the battery1196, a voltage in charging, an electric current, and a temperature. The battery1196can generate electricity and supply a power source. The battery1196can be, for example, a rechargeable battery.

The indicator1197can display a specific state of the hardware1100or a part (e.g., the AP1111) thereof, for example, a booting state, a message state, a charging state and the like. The motor1198can convert an electrical signal into a mechanical vibration. A The processor1110can control the sensor module1140.

Though not illustrated, the hardware1100can include a processing device (e.g., a GPU) for mobile TV support. The processing device for mobile TV support can process, for example, standard media data of Digital Multimedia Broadcasting (DMB), Digital Video Broadcasting (DVB), a media flow and the like.

The names of the aforementioned constituent elements of the hardware1100according to the present disclosure can be varied according to the kind of the electronic device. The hardware1100according to the present disclosure can include at least one of the aforementioned constituent elements, and can omit some constituent elements or further include additional other constituent elements. Also, some of the constituent elements of the hardware1100according to the present disclosure are coupled and constructed as one entity, thereby being able to identically perform the functions of the corresponding constituent elements of before being coupled.

In accordance to the present disclosure, the application processor1111includes an authorized device list block171, a service list block174, and a service UI175. The authorized device list block171manages information about authorized terminals ofFIG. 1. The service list block174manages interworking services with the desk phone150and the enterprise server100. By providing a user interface to a user, receiving an instruction from the user through the user interface, and providing the instruction to the corresponding function block in accordance to the kind of the instruction, the service UI175enables the user to control the execution of a function of the application processor1111through the user interface.

Also, the application processor1111includes a service setting management block176taking charge of a function of interworking with the enterprise server100and the desk phone150.

The service setting management block176performs a function of a mobile terminal of at least the 1stexemplary embodiment of this disclosure. If there is a need to move a call of the mobile terminal to a desk phone 2 during conversation with a desk phone 1, the service setting management block176transmits a call move request to the desk phone 2.

The service setting management block176receives a conversation end request from an enterprise server, and transmits a response to the enterprise server.

The service setting management block176performs a function of a mobile terminal 2 of at least the 2ndembodiment of this disclosure.

If there is a need to move a call of the mobile terminal 2 to a desk phone during conversation with a mobile terminal, the service setting management block176transmits a call move request to the desk phone.

If sensing a Bluetooth connection request of the desk phone, the service setting management block176establishes a conversation path using Bluetooth pairing with the desk phone and performs conversation with the mobile terminal through the established Bluetooth path.

FIG. 12is a block diagram illustrating an example construction of a desk phone according to this disclosure.

Referring toFIG. 12, the desk phone includes a wired communication unit1205, a wireless communication unit1210, a control unit1220, and a storage unit1230.

The wired communication unit1205a module for communicating with other device, and includes a wired processing unit, a baseband processing unit, and the like. The wired processing unit converts a signal received through a wired path into a baseband signal and provides the baseband signal to the baseband processing unit, and converts a baseband signal from the baseband processing unit into a wireless signal such that it can actually transmit on the wired path, and transmits the wireless signal through the wired path.

The wireless communication unit1210is a module for communicating with other device, and includes a wireless processing unit, a baseband processing unit, and the like. The wireless processing unit converts a signal received through an antenna into a baseband signal and provides the baseband signal to the baseband processing unit, and converts a baseband signal from the baseband processing unit into a wireless signal such that it can actually transmit on a wireless path, and transmits the wireless signal through the antenna.

The control unit1220controls a general operation of the desk phone. For example, the control unit1220performs processing and control for voice telephony and packet communication and, particularly, includes a call connection management unit1225in accordance with this disclosure. The control unit1220can perform a function of the call connection management unit1225. Separately constructing and illustrating these in this disclosure is for distinguishing and describing the respective functions.

Accordingly, in the aforementioned block construction, when a product is actually implemented, it can be constructed such that the control unit1220processes all of functions of the call connection management unit1225, or can be constructed such that the control unit1220processes only some of the functions.

The storage unit1230performs a function of storing a program for controlling a general operation of the desk phone and temporary data generated during program execution. Particularly, in accordance with this disclosure, the storage unit1230can store information about a mobile terminal.

The call connection management unit1225includes a VoIP service controller151, a service UI152, and a service setting management block153. The VoIP service controller151controls VoIP telephony. By providing a user interface to a user, receiving an instruction from the user through the user interface, and providing the instruction to the corresponding function block in accordance to the kind of the instruction, the service UI152enables the user to control the execution of a function of the desk phone150through the user interface. The service setting management block153takes charge of a function of interworking with the enterprise server and the mobile terminal.

The call connection management unit1225includes an authorized device list block154for managing information about an authorized terminal.

The call connection management unit1225performs a function of a desk phone of at least the 1stembodiment this disclosure.

The call connection management unit1225receives a call move request from a mobile terminal.

The call connection management unit1225transmits a call state request to an enterprise server.

If receiving from the enterprise server a response including that a call state is in FMC conversation, the call connection management unit1225requests a conversation connection for the call, to the enterprise server.

The call connection management unit1225receives a response from the enterprise server.

The call connection management unit1225performs a function of a desk phone of at least the 2ndembodiment of this disclosure.

The call connection management unit1225receives a call move request from a mobile terminal 2.

The call connection management unit1225transmits a call state request to an enterprise server.

The call connection management unit1225receives from the enterprise server a response including that a call state is not in FMC conversation.

The call connection management unit1225recognizes that the call state received from the enterprise server is not in the FMC conversation, that is, recognizes that the received call state is a call not going through the enterprise server. And then, the call connection management unit1225establishes a conversation path using Bluetooth pairing with the mobile terminal 2, and performs conversation with a mobile terminal through the established Bluetooth path.

Upon receiving the call move request of the mobile terminal 2, the call connection management unit1225can acquire a Bluetooth MAC address of the mobile terminal 2 and perform Bluetooth pairing with the mobile terminal 2.

FIG. 13is a block diagram illustrating an example construction of an enterprise server according to this disclosure.

Referring toFIG. 13, the enterprise server includes a communication unit1310, a control unit1320, and a storage unit1330.

The communication unit1310is a module for communicating with other device, and includes a wired processing unit, a baseband processing unit, and the like. The wired processing unit converts a signal received through a wired path into a baseband signal and provides the baseband signal to the baseband processing unit, and converts a baseband signal from the baseband processing unit into a wireless signal such that it can actually transmit on the wired path, and transmits the wireless signal through the wired path.

The control unit1320controls a general operation of the enterprise server. For example, the control unit1320performs processing and control for FMC function operation and, particularly, includes a call management unit1325in accordance to this disclosure. The control unit1320can perform a function of the call management unit1325. Separately constructing and illustrating these in this disclosure is for distinguishing and describing the respective functions.

Accordingly, in the aforementioned block construction, when a product is actually implemented, it can be constructed such that the control unit1320processes all of functions of the call management unit1325, or can be constructed such that the control unit1320processes only some of the functions.

The storage unit1330performs a function of storing a program for controlling a general operation of the enterprise server and temporary data generated during program execution. Particularly, the storage unit1330can store call state information about terminals.

The call management unit1325includes a call service engine101, a subscriber state monitoring block102, and a subscriber setting/authorization/registration management block103. The subscriber setting/authorization/registration management block103takes charge of a function of setting, authorizing and registering a subscriber to the enterprise server ofFIG. 1. The call service engine101provides a call service to the registered subscriber. The subscriber state monitoring block102monitors a current state of a requested subscriber or a specific subscriber among subscribers. For example, the subscriber state monitoring block102decides whether the subscriber is receiving the call service through the enterprise server100.

The call management unit1325performs a function of an enterprise server of at least the 1stembodiment this disclosure.

The call management unit1325receives a call state request from a desk phone 2.

The call management unit1325determines the call state. If it is determined that the call state is in FMC conversation, the call management unit1325transmits to the desk phone 2 a response including that the call state is in the FMC conversation. Here, the call management unit1325searches a database for a MIN or extension phone number of a mobile terminal having requested call state information and performs MIN or extension phone number registration or non-registration and conversation state query. Here, the FMC represents an application performing a VoIP service using WiFi wireless communication.

The call management unit1325receives a conversation connection request for the call, from the desk phone 2, and transmits a response to the desk phone 2.

The call management unit1325transmits a conversation update request to a desk phone 1 and receives a response from the desk phone 1.

The call management unit1325requests a conversation end to the mobile terminal and receives a response from the mobile terminal.

The call management unit1325performs a function of an enterprise server of at least the 2ndembodiment of this disclosure.

The call management unit1325receives a call state request from a desk phone.

The call management unit1325determines the call state. If it is determined that the call state is not in FMC conversation, the call management unit1325transmits to the desk phone a response including that the call state is not in the FMC conversation. Here, the call management unit1325searches a database for a MIN or extension phone number of a mobile terminal 2 having requested call state information and performs MIN or extension phone number registration or non-registration and conversation state query. Here, the FMC represents an application performing a VoIP service using WiFi wireless communication.

Embodiments of the present disclosure have an advantage of being capable of enhancing a user's convenience by providing a service of call move between terminals using a Bluetooth protocol, although a user does not use a FMC module performing VoIP communication with an enterprise server, under the enterprise network environment.

Embodiments of the present disclosure have an advantage of being capable of providing a seamless service even to a terminal using a FMC module, by providing a call move service identically for all of a call going through an enterprise server and a 3G/LTE call not going through the enterprise server.

Exemplary embodiments and all function operations of the disclosure described in the present specification can be implemented by computer software including structures disclosed in the present specification and equivalent structures thereof, firmware, hardware or a combination of two or more of them. Also, the exemplary embodiments of the disclosure described in the present specification can be implemented by one or more computer program products, such as data processing devices, or can be implemented by one or more modules of computer program instructions encoded on a computer-readable medium for controlling operations of these devices.

The computer-readable medium can be a machine-readable storage medium, a machine-readable storage substrate, a memory device, a construction of substance affecting a machine-readable radio wave stream, or a combination of two or more of them. The term of data processing device can include, for example, all instruments, devices and machines for processing data including a programmable processor or computer, or a multi-processor or computer. The instrument can include a code added to hardware and generating an execution environment for a corresponding computer program, for example, a code constructing a processor firmware, a protocol stack, a database management system, an operating system, or a combination of two or more of them.