KR20120015169A - Method for rejecting conference call invitation and mobile terminal using this method - Google Patents

Abstract

PURPOSE: A telephone conference invitation rejection method and a terminal using the same are provided to transmit a reason for a telephone conference invitation by including an SIP(Session Initiation Protocol) message body in various data packets. CONSTITUTION: A mobile terminal receives telephone conference attendance invitation(S310). The mobile terminal determines telephone conference attendance(S320). The mobile terminal responds acceptance determination(S330, S340). In case a user rejects telephone conference invitation, the mobile terminal responds refusal determination including a refusal reason(S350).

Description

METHOOD FOR REJECTING CONFERENCE CALL INVITATION AND MOBILE TERMINAL USING THIS METHOD}

The present invention relates to a communication method, and more particularly, to a method for rejecting a conference call invitation and a mobile terminal using the same.

Terminals may be divided into mobile / portable terminals and stationary terminals according to their mobility. The mobile terminal may be further classified into a handheld terminal and a vehicle mount terminal according to whether a user can directly carry it.

As the functions are diversified, for example, the terminal is implemented in the form of a multimedia player having complex functions such as taking a picture or a video, playing a music or a video file, playing a game, and receiving a broadcast. . In order to support and increase the function of such a terminal, it may be considered to improve the structural part and / or the software part of the terminal.

In general, conventional terminals have evolved to support a voice on the internet protocol (VoIP) function through a packet network for data communication. Internet telephony is also widely used for conference calls, and an Internet telephony call connection for a conference may be established through a session initiation protocol (SIP). In this case, the caller may invite another user to the conference call by sending an invitation message to the other user, and the callee may answer whether the call is accepted or the invitation is accepted.

However, when the recipient invited to the conference call cannot attend or does not want to attend the conference, there is a problem that the recipient cannot effectively convey the specific reason for rejection of the conference invitation to the caller (inviter).

An object of the present specification is to provide a method for rejecting a conference call invitation and a mobile terminal using the same, which can transmit a detailed reason for rejection of the conference call invitation to the inviter.

According to an embodiment of the present disclosure, a method for rejecting a conference call invitation according to an embodiment of the present disclosure includes receiving a call invitation to attend a conference call in a method of rejecting a conference call invitation of a mobile terminal supporting an Internet phone; Determining whether or not to attend the conference call and responding to the acceptance decision when accepting the conference call and responding to the rejection decision including a reason for rejection when rejecting the conference call.

A mobile terminal according to one embodiment disclosed herein for realizing the above-described problem, in a mobile terminal supporting an Internet phone call connected according to Session Initiation Protocol (SIP), receives an INVITE message requesting to attend a conference call. Determines whether to receive the wireless communication unit and whether to attend the conference call, and if the user accepts the conference call, sends a response message with a status code of SUCCESSFUL, and rejects the conference call with a status code of REQUEST FAILURE or GLOBAL FAILURE. And a control unit for transmitting the reason for rejection in the response message, wherein the rejection reason is configured in an XML format and included in the response message body.

The method of rejecting a conference call invitation and a mobile terminal using the same according to at least one exemplary embodiment disclosed in the present specification include a SIP message body and a SIP separately defined as a reason for rejection of a callee who cannot be invited to a conference call. It is included in a message or various data packets and sent to the sender (inviter) so that the sender (inviter) can confirm the reason why the invitation was rejected.

1 is a block diagram illustrating a mobile terminal according to one embodiment disclosed herein.
2 is a flowchart illustrating a method for rejecting a conference call between a calling terminal and a receiving terminal according to an exemplary embodiment disclosed herein.
3 is a flow chart illustrating a method for rejecting a conference call invitation according to an embodiment disclosed herein.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments disclosed herein will be described in detail with reference to the accompanying drawings, and the same or similar components will be given the same reference numerals regardless of the reference numerals, and redundant description thereof will be omitted. The suffix "module" and " part "for the components used in the following description are given or mixed in consideration of ease of specification, and do not have their own meaning or role. In the following description of the embodiments of the present invention, a detailed description of related arts will be omitted when it is determined that the gist of the embodiments disclosed herein may be blurred. In addition, it should be noted that the attached drawings are only for easy understanding of the embodiments disclosed in the present specification, and should not be construed as limiting the technical idea disclosed in the present specification by the attached drawings.

Overall configuration of the mobile terminal

The mobile terminal described herein may include a mobile phone, a smart phone, a laptop computer, a digital broadcasting terminal, a personal digital assistant, a portable multimedia player (PMP), navigation, and the like. However, it will be readily apparent to those skilled in the art that the configuration according to the embodiments described herein may also be applied to fixed terminals such as digital TVs, desktop computers, etc., except when applicable only to mobile terminals.

1 is a block diagram illustrating a mobile terminal according to one embodiment disclosed herein.

The mobile terminal 100 includes a wireless communication unit 110, an A / V input unit 120, a user input unit 130, a sensing unit 140, an output unit 150, a memory 160, and an interface. The unit 170, the controller 180, and the power supply unit 190 may be included. The components shown in FIG. 1 are not essential, so that a mobile terminal having more or fewer components may be implemented.

Hereinafter, the components will be described in order.

The wireless communication unit 110 may include one or more modules that enable wireless communication between the mobile terminal 100 and the wireless communication system or between the mobile terminal 100 and a network in which the mobile terminal 100 is located. For example, the wireless communication unit 110 may include a broadcast receiving module 111, a mobile communication module 112, a wireless Internet module 113, a short range communication module 114, and a location information module 115 .

The broadcast receiving module 111 receives a broadcast signal and / or broadcast related information from an external broadcast management server through a broadcast channel. The broadcast related information may mean information related to a broadcast channel, a broadcast program, or a broadcast service provider. The broadcast related information may also be provided through a mobile communication network. In this case, it may be received by the mobile communication module 112. The broadcast signal and / or broadcast related information received through the broadcast receiving module 111 may be stored in the memory 160.

The mobile communication module 112 transmits and receives a wireless signal with at least one of a base station, an external terminal, and a server on a mobile communication network. The wireless signal may include various types of data according to transmission and reception of a voice call signal, a video call call signal, or a text / multimedia message.

The wireless internet module 113 refers to a module for wireless internet access and may be embedded or external to the mobile terminal 100. Wireless Internet technologies may include Wireless LAN (Wi-Fi), Wireless Broadband (Wibro), World Interoperability for Microwave Access (Wimax), High Speed Downlink Packet Access (HSDPA), and the like.

The short range communication module 114 refers to a module for short range communication. As a short range communication technology, Bluetooth, Radio Frequency Identification (RFID), Infrared Data Association (IrDA), Ultra Wideband (UWB), ZigBee, etc. may be used.

The location information module 115 is a module for obtaining a location of a mobile terminal, and a representative example thereof is a GPS (Global Position System) module.

Referring to FIG. 1, the A / V input unit 120 is for inputting an audio signal or a video signal, and may include a camera 121 and a microphone 122. The camera 121 processes image frames such as still images or moving images obtained by the image sensor in the video call mode or the photographing mode. The processed image frame may be displayed on the display unit 151.

The image frame processed by the camera 121 may be stored in the memory 160 or transmitted to the outside through the wireless communication unit 110. Two or more cameras 121 may be provided according to the use environment.

The microphone 122 receives an external sound signal by a microphone in a call mode, a recording mode, a voice recognition mode, etc., and processes the external sound signal into electrical voice data. The processed voice data can be converted into a form that can be transmitted to the mobile communication base station through the mobile communication module 112 when the voice data is in the call mode, and output. The microphone 122 may implement various noise removing algorithms for removing noise generated in the process of receiving an external sound signal.

The user input unit 130 generates input data for the user to control the operation of the terminal. The user input unit 130 may include a key pad dome switch, a touch pad (static pressure / capacitance), a jog wheel, a jog switch, and the like.

The sensing unit 140 detects a current state of the mobile terminal 100 such as an open / closed state of the mobile terminal 100, a location of the mobile terminal 100, presence or absence of a user contact, orientation of the mobile terminal, acceleration / deceleration of the mobile terminal, and the like. To generate a sensing signal for controlling the operation of the mobile terminal 100. For example, when the mobile terminal 100 is in the form of a slide phone, it may sense whether the slide phone is opened or closed. In addition, whether the power supply unit 190 is supplied with power, whether the interface unit 170 is coupled to the external device may be sensed. The sensing unit 140 may include a proximity sensor 141.

The output unit 150 is used to generate an output related to visual, auditory, or tactile, and may include a display unit 151, an audio output module 152, an alarm unit 153, and a haptic module 154. have.

The display unit 151 displays (outputs) information processed by the mobile terminal 100. For example, when the mobile terminal is in a call mode, the mobile terminal displays a user interface (UI) or a graphic user interface (GUI) related to the call. When the mobile terminal 100 is in a video call mode or a photographing mode, the mobile terminal 100 displays photographed and / or received images, a UI, and a GUI.

The display unit 151 includes a liquid crystal display (LCD), a thin film transistor-liquid crystal display (TFT LCD), an organic light-emitting diode (OLED), and a flexible display (flexible). display, a 3D display, or an e-ink display.

Some of these displays can be configured to be transparent or light transmissive so that they can be seen from the outside. This may be referred to as a transparent display. A representative example of the transparent display is TOLED (Transparant OLED). The rear structure of the display unit 151 may also be configured as a light transmissive structure. With this structure, the user can see the object located behind the terminal body through the area occupied by the display unit 151 of the terminal body.

There may be two or more display units 151 according to the implementation form of the mobile terminal 100. For example, in the mobile terminal 100, a plurality of display portions may be spaced apart from one another, or may be disposed integrally with one another, and may be disposed on different surfaces, respectively.

When the display unit 151 and a sensor for detecting a touch operation (hereinafter, referred to as a touch sensor) form a mutual layer structure (hereinafter referred to as a touch screen), the display unit 151 may be used in addition to an output device. Can also be used as an input device. The touch sensor may have, for example, a form of a touch film, a touch sheet, a touch pad, or the like.

The touch sensor may be configured to convert a change in pressure applied to a specific portion of the display unit 151 or capacitance generated in a specific portion of the display unit 151 into an electrical input signal. The touch sensor may be configured to detect not only the position and area of the touch but also the pressure at the touch.

If there is a touch input to the touch sensor, the corresponding signal (s) is sent to the touch controller. The touch controller processes the signal (s) and then transmits the corresponding data to the controller 180. As a result, the controller 180 can know which area of the display unit 151 is touched.

Referring to FIG. 1, a proximity sensor 141 may be disposed in an inner region of a mobile terminal surrounded by the touch screen or near the touch screen. The proximity sensor refers to a sensor that detects the presence or absence of an object approaching a predetermined detection surface or an object present in the vicinity without using a mechanical contact by using an electromagnetic force or infrared rays. Proximity sensors have a longer life and higher utilization than touch sensors.

Examples of the proximity sensor include a transmission photoelectric sensor, a direct reflection photoelectric sensor, a mirror reflection photoelectric sensor, a high frequency oscillation proximity sensor, a capacitive proximity sensor, a magnetic proximity sensor, and an infrared proximity sensor. When the touch screen is capacitive, the touch screen is configured to detect the proximity of the pointer by the change of the electric field according to the proximity of the pointer. In this case, the touch screen (touch sensor) may be classified as a proximity sensor.

The sound output module 152 may output audio data received from the wireless communication unit 110 or stored in the memory 160 in a call signal reception, a call mode or a recording mode, a voice recognition mode, a broadcast reception mode, and the like. The sound output module 152 may also output a sound signal related to a function (eg, a call signal reception sound, a message reception sound, etc.) performed in the mobile terminal 100. The sound output module 152 may include a receiver, a speaker, a buzzer, and the like.

The alarm unit 153 outputs a signal for notifying occurrence of an event of the mobile terminal 100. Examples of events occurring in the mobile terminal include call signal reception, message reception, key signal input, and touch input. The alarm unit 153 may output a signal for notifying occurrence of an event in a form other than a video signal or an audio signal, for example, vibration. The video signal or the audio signal may be output through the display unit 151 or the audio output module 152, so that they 151 and 152 may be classified as part of the alarm unit 153.

The haptic module 154 generates various tactile effects that the user can feel. Vibration is a representative example of the haptic effect generated by the haptic module 154. The intensity and pattern of vibration generated by the haptic module 154 can be controlled. For example, different vibrations may be synthesized and output or may be sequentially output.

In addition to vibration, the haptic module 154 may be configured to provide a pin array that vertically moves with respect to the contact skin surface, a jetting force or suction force of air through an injection or inlet port, grazing to the skin surface, contact of an electrode, electrostatic force, and the like. Various tactile effects can be generated, such as effects by the endothermic and the reproduction of a sense of cold using the elements capable of endotherm or heat generation.

The haptic module 154 may not only deliver the haptic effect through direct contact, but also may implement the user to feel the haptic effect through a muscle sense such as a finger or an arm. Two or more haptic modules 154 may be provided according to configuration aspects of the mobile terminal 100.

The memory 160 may store a program for the operation of the controller 180 and may temporarily store input / output data (for example, a phone book, a message, a still image, a video, etc.). The memory 160 may store data relating to various patterns of vibration and sound output when a touch input on the touch screen is performed.

The memory 160 may be a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (for example, SD or XD memory), RAM random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic It may include a storage medium of at least one type of disk, optical disk. The mobile terminal 100 may operate in connection with a web storage that performs a storage function of the memory 160 on the Internet.

The interface unit 170 serves as a path with all external devices connected to the mobile terminal 100. The interface unit 170 receives data from an external device, receives power, transfers the power to each component inside the mobile terminal 100, or transmits data inside the mobile terminal 100 to an external device. For example, a wired / wireless headset port, an external charger port, a wired / wireless data port, a memory card port, a port for connecting a device having an identification module, an audio I / O port, A video input / output (I / O) port, an earphone port, and the like may be included in the interface unit 170.

The identification module is a chip that stores various types of information for authenticating the use authority of the mobile terminal 100. The identification module includes a user identify module (UIM), a subscriber identify module (SIM), and a universal user authentication module ( universal subscriber identity module (USIM), and the like. Devices with identification modules (hereinafter referred to as "identification devices") can be manufactured in a smart card format. Accordingly, the identification device can be connected to the terminal 100 through the port.

The interface unit may be a passage through which power from the cradle is supplied to the mobile terminal 100 when the mobile terminal 100 is connected to an external cradle, or various command signals input from the cradle by a user may be transferred. It may be a passage that is delivered to the terminal. Various command signals or power input from the cradle may be operated as signals for recognizing that the mobile terminal is correctly mounted on the cradle.

The controller 180 typically controls the overall operation of the mobile terminal. For example, perform related control and processing for voice calls, data communications, video calls, and the like. The controller 180 may include a multimedia module 181 for playing multimedia. The multimedia module 181 may be implemented in the controller 180 or may be implemented separately from the controller 180.

The controller 180 may perform a pattern recognition process for recognizing a writing input or a drawing input performed on the touch screen as text and an image, respectively.

The power supply unit 190 receives an external power source and an internal power source under the control of the controller 180 to supply power for operation of each component.

Various embodiments described herein may be implemented in a recording medium readable by a computer or similar device using, for example, software, hardware or a combination thereof.

According to a hardware implementation, the embodiments described herein include application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs). It may be implemented using at least one of processors, controllers, micro-controllers, microprocessors, and electrical units for performing other functions. In some cases, the embodiments described herein may be implemented by the controller 180 itself.

According to the software implementation, embodiments such as the procedures and functions described herein may be implemented as separate software modules. Each of the software modules may perform one or more functions and operations described herein. Software code can be implemented in a software application written in a suitable programming language. The software code may be stored in the memory 160 and executed by the controller 180.

How to handle user input to a mobile terminal

The user input unit 130 is operated to receive a command for controlling the operation of the mobile terminal 100 and may include a plurality of operation units. The manipulation units may also be referred to collectively as a manipulating portion, and may be employed in any manner as long as the user is tactile in the manner of tactile feeling.

Various types of time information can be displayed on the display unit 151. [ These pieces of information can be displayed in the form of letters, numbers, symbols, graphics, or icons.

At least one of the letters, numbers, symbols, graphics, or icons may be displayed in a predetermined arrangement for inputting such information, thereby being implemented as a keypad. Such a keypad may be called a so-called " soft key ".

The display unit 151 may operate in an entire area or may be operated in a divided manner. In the latter case, the plurality of areas can be configured to operate in association with each other.

For example, an output window and an input window may be displayed on the upper and lower portions of the display unit 151, respectively. The output window and the input window are areas allocated for output or input of information, respectively. In the input window, a softkey displaying a number for inputting a telephone number or the like may be output. When the softkey is touched, a number or the like corresponding to the touched softkey is displayed in the output window. When the operation unit is operated, call connection to the telephone number displayed in the output window may be attempted or text displayed in the output window may be input to the application.

The display unit 151 or the touch pad may be configured to receive a touch input by scrolling. The user may move a cursor or a pointer located on an object displayed on the display unit 151, for example, an icon, by scrolling the display unit 151 or the touch pad. In addition, when the finger is moved on the display unit 151 or the touch pad, a path along which the finger moves may be visually displayed on the display unit 151. This may be useful for editing an image displayed on the display unit 151.

In response to the display unit 151 (touch screen) and the touch pad being touched together within a predetermined time range, one function of the terminal may be executed. In the case of being touched together, there may be a case where the user clamps the terminal body using the thumb and index finger. For example, the function may be activation or deactivation of the display unit 151 or the touch pad.

Hereinafter, embodiments related to a control method that can be implemented in the terminal configured as described above will be described with reference to the accompanying drawings. Embodiments described later may be used alone or in combination with each other. In addition, embodiments described below may be used in combination with the above-described user interface (UI).

How to decline a conference invitation and mobile terminal using the same

The method for rejecting a conference call invitation according to an exemplary embodiment disclosed herein may include a SIP message body, a SIP message defined separately from the RFC 2543/3261 standard, or various data packets, indicating a reason for the rejection that a recipient invited to the conference call cannot participate in the conference call. The present invention proposes a method in which the sender (inviter) can confirm the reason for the rejection of the invitation by sending it to the sender (inviter). In particular, the method for rejecting a conference call invitation according to an embodiment disclosed in the present disclosure may be applied to an internet phone complementing 3GPP Multimedia Telephony technology.

Hereinafter, for convenience of description, it is assumed that the mobile terminal 100 according to the exemplary embodiment disclosed herein is a mobile terminal supporting an Internet phone call according to a session initiation protocol (SIP). However, the case in which the mobile terminal 100 supports SIP is only for explaining an embodiment of the present invention, and it should be noted that the technical idea of the present invention is not limited to this embodiment. For example, the present invention can be applied to the case where the mobile terminal 100 supports an Internet telephone call according to the ITU-T H.323 standard.

Specifically, the wireless communication unit 110 receives an invitation to attend a conference call from a counterpart terminal (invitation terminal). For example, the counterpart terminal may invite the mobile terminal 100 to the conference call by switching to a conference call and sending an INVITE message to the mobile terminal 100 while talking on the internet phone with another terminal.

The controller 180 determines whether to attend the conference call with respect to the received invitation to attend. In this case, when the controller 180 displays a pop-up message window notifying the invitation to attend, the user may press the 'accept' button displayed on the pop-up message window to accept the invitation or reject the invitation by pressing the 'decline' button. .

When the user presses the 'decline' button, the controller 180 may display an edit screen on the display unit 151 for creating a reason for rejection. The user may input text, an icon, an image, a figure, a video, etc. on the edit screen through a keypad input, a virtual keypad input, a touch input, a gesture input, a motion input, or the like. When the user presses the button 'Complete refusal reason creation' displayed on the edit screen, the controller 180 may transmit the created rejection reason to the counterpart terminal together with the rejection response as described below.

When the controller 180 accepts the conference call participation, the controller 180 responds to the counterpart terminal with an acceptance decision. In this case, the controller 180 may notify the counterpart terminal of the acceptance decision by sending a response message in which a status code or a response code is SUCCESSFUL (for example, '200 OK').

When the controller 180 refuses to attend the conference call, the controller 180 responds to the counterpart terminal with a rejection decision including a reason for rejection.

The rejection reason may be not only a physical communication reason such as a request processing impossible, but also a personal reason of the user of the mobile terminal 100. For example, the reason for the refusal may be 'in a meeting', 'driving', 'no interest', 'difficult in a public place', 'summer vacation from August 2, 2010 to August 6, 2010.' Middle, etc., and furthermore, 'can't attend the meeting.' Please invite me to the next meeting. ' Or the like.

The refusal reason may be configured according to a format such as plain text, hyper text markup language (HTML), extensible markup language (XML), etc., using text, an icon, an image, a figure, a video, and the like as components. . For example, the controller 180 screen captures the image of the schedule of the user of the invited mobile terminal 100 and 'is currently unavailable for business trip. Please refer to the schedule you sent, and ask me to invite you again on a possible date. '

The controller 180 sends a response message in which the status code or response code is REQUEST FAILURE (for example, '486 Busy Here') or GLOBAL FAILURE (for example, '602 Decline'). , The rejection reason configured according to the XML format may be included or stored in the response message body.

Alternatively, on the assumption that a new status code or response code (eg, '499 User Defined') that is not included in the RFC 2543/3261 standard is separately defined, the controller 180 sets the status code or response code to '499 User'. The response message, which is Defined ', may be sent, and the rejection reason configured according to a general plain text form, HTML format, XML format, or the like may be included or stored in the response message body.

In this case, it is assumed that the mobile terminal 100 and the counterpart terminal know in advance the status code or the response code defined separately from the RFC 2543/3261 standard. Therefore, when the mobile terminal 100 transmits a message having the status code or the response code defined separately, the counterpart terminal may interpret the received message normally.

Alternatively, assuming that a new message (eg, '7xx NOTIFY') not included in the RFC 2543/3261 standard is defined separately, the controller 180 sends a NOTIFY message, and the plain text form, HTML format, XML The rejection reason configured according to a format may be included or stored in the NOTIFY message body.

In this case, it is assumed that the mobile terminal 100 and the counterpart terminal recognize the message previously defined separately from the RFC 2543/3261 standard. Therefore, when the mobile terminal 100 transmits the message defined separately, the counterpart terminal can interpret the received message normally.

2 is a flowchart illustrating a method for rejecting a conference call between a calling terminal and a receiving terminal according to an exemplary embodiment disclosed herein.

Referring to FIG. 2, first, a first terminal may request a server (eg, a conference server) to generate a conference call during a call with a third terminal. When the conference call is generated, the first terminal sends a conference invitation invitation message (eg, an INVITE message) to the second terminal via the server.

The second terminal, which has decided to reject the conference call invitation, transmits an invitation rejection message to the first terminal via the server, including the reason for the rejection. Although not shown separately in FIG. 2, the second terminal that has decided to accept the conference call invitation may transmit an acceptance response message (eg, 200 OK message) to the first terminal through the server.

As described above, the second terminal includes the reason for the rejection in the invitation rejection message in which the status code or the response code is REQUEST FAILURE (eg, '486 Busy Here') or GLOBAL FAILURE (eg, '602 Decline'). You can.

Alternatively, the second terminal may include the reason for rejection in the invitation rejection message having a new status code or response code (eg, '499 User Defined') not included in the RFC 2543/3261 standard. Alternatively, the second terminal may include the reason for rejection in a new message (eg, '7xx NOTIFY') not included in the RFC 2543/3261 standard.

Meanwhile, the first terminal may check the specific reason for rejecting the invitation from the reason for rejection included in the invitation rejection message.

3 is a flow chart illustrating a method for rejecting a conference call invitation according to an embodiment disclosed herein.

Referring to FIG. 3, first, the mobile terminal 100 receives an invitation to attend a conference call (S310). Next, the mobile terminal 100 determines whether to attend a conference call (S320).

In the case of accepting the conference call (S330), the mobile terminal 100 responds to the acceptance decision (S340).

If the attendance of the conference call is rejected (S330), the mobile terminal 100 responds to the rejection decision including the reason for rejection (S350). In this case, the mobile terminal 100 may transmit a SIP message including the reason for rejection. For example, the SIP message may be a response message having a status code of '486 Busy Here' or a response message having a status code of '602 Decline'. In addition, the mobile terminal 100 may transmit the rejection reason configured in the XML format in the response message body.

The method for processing call waiting according to the embodiments disclosed herein may be understood similarly to the above description with reference to FIGS. 1 and 2 with respect to the mobile terminal according to the embodiments disclosed herein. Omit.

In addition, according to one embodiment disclosed herein, the above-described method may be implemented as code that can be read by a processor in a medium in which a program is recorded. Examples of processor-readable media include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage, and the like, and may be implemented in the form of a carrier wave (for example, transmission over the Internet). Include.

The mobile terminal described above can be applied to not only the configuration and method of the embodiments described above but also all or some of the embodiments may be selectively combined so that various modifications may be made to the embodiments It is possible.

Embodiments disclosed herein have been described with reference to the accompanying drawings.

Here, the terms or words used in the present specification and claims should not be construed as being limited to the ordinary or dictionary meanings, but should be interpreted as meanings and concepts corresponding to the technical spirit disclosed in the present specification.

Therefore, the embodiments described in the present specification and the configuration shown in the drawings are only one embodiment disclosed in the present specification, and do not represent all the technical ideas disclosed in the present specification. It should be understood that there may be equivalents and variations.

100: mobile terminal 110: wireless communication unit
120: A / V input unit 130: user input unit
140: sensing unit 150: output unit
160: memory 170: interface unit
180: control unit 190: power supply unit

Claims (5)

In the method of rejecting a conference call invitation of a mobile terminal that supports Internet telephony,
Receiving an invitation to attend a conference call;
Determining whether to attend the conference call; And
Responding to the acceptance decision if accepting the conference call, and responding to the rejection decision including a reason for rejection if rejecting the conference call. The method of claim 1,
And in response to the rejection determination, transmit a SIP message including the reason for rejection. The method of claim 2,
The SIP message may be a response message having a status code of '486 Busy Here' or a response message having a status code of '602 Decline'. The method of claim 1,
In response to the rejection decision, the method of rejecting a conference call invitation of a mobile terminal, characterized in that the transmission of the rejection reason in XML format included in the response message body. A mobile terminal supporting an internet phone call established according to a session initiation protocol (SIP),
A wireless communication unit receiving an INVITE message requesting to attend a conference call; And
Determine whether or not to attend the conference call, if the user accepts the conference call, sends a response message with a status code of SUCCESSFUL, and if rejecting the conference call, rejects the response message with a status code of REQUEST FAILURE or GLOBAL FAILURE Including a control unit for transmitting, including;
The reason for rejection is a mobile terminal, characterized in that the XML format is included in the response message body.

Images