KR20180135756A - Server and method for processing conference call - Google Patents

Abstract

Provided is a server for processing a conference call and a method thereof. The server for processing a conference call comprises a memory for storing a program for processing a call originating terminal and at least two call destination terminals to make a conference call connected through a conference call server; and a processor for executing the program. The program includes instructions to: receive, from the call originating terminal, a conference call access number entered by the user, and a conference call request message in which call destination numbers of the at least two call destination terminals are set as the recipients; transmit the conference call request message to the conference call server corresponding to the conference call connection number; and transmit a conference call invitation message to each call destination terminal corresponding to the each call destination phone number in conjunction with the conference call server.

Description

TECHNICAL FIELD [0001] The present invention relates to a conference call processing server,

The present invention relates to a conference call processing server and a method thereof.

A conference call is a telephone call made between three or more people at the same time. Conference calls have been steadily used because of the ability to save time and money by allowing multiple people in multiple locations to meet without having to be in the same place.

A terminal supporting the conference calling function of the IMS (IP Multimedia Subsystem) standard provides a conference call menu on the terminal menu. The user selects a conference call participant from the terminal menu, and then selects a conference call request button to transmit a conference call. At this time, the terminal generates and transmits a message (INVITE) requesting a conference call according to the standard specification.

This method has a problem in that the user can easily request a conference call through the terminal menu, but all conference participants must use the IMS conference calling function. In addition, in the case of existing terminals, IMS conference calls are not supported. There is a problem in that all existing terminals must be replaced with a terminal adopting the IMS conference calling function in order to make a conference call.

On the other hand, even if the IMS conference call is not supported, the dedicated call app can be used to use the conference call service. A terminal installed with a dedicated app accesses a dedicated app server through an Internet network, requests a conference call, selects a participant list from a dedicated app menu, and registers the participant list in a dedicated app server. Upon receiving the conference call access number from the dedicated app server, the dedicated app generates and transmits a message (INVITE) requesting a conference call including the conference call access number. Such a message is transmitted to the dedicated app server, and the dedicated app server confirms the participant list selected in the dedicated app menu in advance and transmits the conference call invitation message to the corresponding participant terminal.

However, this method always requires installation and execution of dedicated apps. Users are faced with the inconvenience of running dedicated apps each time for a conference call.

Therefore, there is a need for a technological idea that makes the conference call service more convenient and convenient.

A problem to be solved by the present invention is to provide a conference call processing method capable of requesting a conference call in such a manner that a call connection is dialed out directly to a conference call access number and a recipient telephone number inputted by a user, A call processing server and a method thereof are provided.

According to one aspect of the present invention, there is provided a call processing server for processing a conference call, the call processing server comprising: a memory for storing a program for processing a calling party and at least two calling terminals, And a processor for executing the program, wherein the program is configured to receive a conference call request message set by a user as a conference call connection number and an incoming telephone number of each of the at least two destination terminals as a receiver from the calling terminal The conference call request message is forwarded to the conference call server corresponding to the conference call connection number, and the conference call request message is transmitted to each of the call terminals corresponding to the respective incoming telephone numbers, And instructions for transmitting the data.

Wherein the conference call request message comprises the conference call connection number and the incoming telephone numbers of each of the at least two called terminals in the receiver identifier,

Wherein the program deletes only the conference call access number in the recipient identifier and deletes the remaining incoming telephone numbers, changes the conference call request message by including the incoming telephone numbers in the newly defined conference call participant field, And a call request message to the conference call server.

The program may include instructions for generating a conference call invitation message in response to a request or response of the conference call server, wherein each conference call invitation message includes each of the incoming telephone numbers stored in the conference call participant field as a recipient identifier.

Wherein the conference call request message received from the calling terminal is an INVITE message of a Session Initiation Protocol (SIP), and the Request-URI specifying the recipient is the conference call connection number and the at least two incoming phone numbers And the Request-URI may be a form in which a delimiter is input between the conference call connection number and the at least two incoming call numbers.

The changed conference call request message may be an INVITE message of a Session Initiation Protocol (SIP) to which the conference call participant field is added in a header field.

Each of the conference invitation messages is an INVITE message of a Session Initiation Protocol (SIP), and a Request-URI specifying a recipient may be set to each incoming phone number.

According to another aspect of the present invention, a conference call processing method is a conference call processing method performed by an originating call processing server operated by at least one processor, the method comprising: receiving a call request message from a calling terminal; Determining whether the call request is a conference call request by confirming a recipient of the request message, and determining whether the call request is a conference call request to the calling terminal and the conference call server, which is connected to at least two destination terminals and provides a conference call service, Wherein the conference call request includes a conference call access number corresponding to the conference call server in the recipient of the call request message.

Wherein the call request message is an INVITE message of a Session Initiation Protocol (SIP), and the incoming call step includes receiving the conference call access number and at least one of a conference call access number and a conference call access number in a Request-URI designating a recipient of the INVITE message. When at least two incoming telephone numbers are included, the at least two incoming telephone numbers extracted from the Request-URI are recorded in the header field of the INVITE message while leaving only the conference call connection number in the Request-URI Changing the INVITE message, and transmitting the changed INVITE message to the conference call server.

The modifying may record the at least two incoming phone numbers extracted from the Request-URI in a newly defined conference call participant field in the header field.

Wherein the receiving comprises receiving the INVITE message originated from the originating session control device and transmitting the INVITE message to the conference call server by sending the modified INVITE message to the originating session control And to the conference call server through the apparatus and the called session control apparatus connected to the conference call server.

According to another aspect of the present invention, a conference call processing method is operated by at least one processor, and is connected to a calling terminal and at least two calling terminals, A method for processing a conference call call performed in a server, the method comprising: receiving a conference call request message from an originating communication network connected to the calling terminal; transmitting the conference call request message to the conference call server; Checking at least two incoming telephone numbers from the header field of the conference call request message, and generating a conference call invitation message having each confirmed incoming telephone number as a recipient and transmitting the generated conference call invitation message to each of the corresponding called terminals , Wherein the conference call request message Is a conference call connection number corresponding to the conference call server is set as a receiver identifier.

The conference call request message is a message in which the call request message transmitted from the calling terminal is changed in the calling side call processing server and is transmitted to the called side session control device through the calling side session control device, An incoming call can be triggered.

Wherein the conference call request message is an INVITE message of a Session Initiation Protocol (SIP), the conference call connection number is stored in a Request-URI designating a recipient of the INVITE message, The at least two incoming phone numbers may be included in the newly defined conference call participant field in the header field of the INVITE message.

The conference call invitation message is an INVITE message of a Session Initiation Protocol (SIP), and each incoming telephone number may be stored in a Request-URI designating a recipient of the INVITE message.

According to the embodiment of the present invention, after inputting a recipient telephone number, a conference call can be requested in a simple manner by clicking a call button, so that a user can start a conference call more easily.

In addition, even if the IMS conference call is not supported and a dedicated application is not installed, a conference call can be requested only by a simple user operation as in the case of requesting a general call. Therefore, .

1 is a configuration diagram of a conference call system according to an embodiment of the present invention.
2 is a flowchart illustrating a conference call method according to an embodiment of the present invention.
3 is an exemplary view of a conference call request screen according to an embodiment of the present invention.
4 is an exemplary view of a conference call request message according to an embodiment of the present invention.
5 is an exemplary view of a modified conference call request message according to an embodiment of the present invention.
6 is an exemplary view of a conference call invitation message according to an embodiment of the present invention.
7 is an exemplary view of a conference call invitation message according to an embodiment of the present invention.
8 is a configuration diagram of a conference call system according to another embodiment of the present invention.
9 is a hardware block diagram of a conference call system according to another embodiment of the present invention.
10 is a hardware block diagram of a terminal according to an embodiment of the present invention.

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

Throughout the specification, when an element is referred to as "comprising ", it means that it can include other elements as well, without excluding other elements unless specifically stated otherwise. Also, the terms " part, "" ... "," module ", and the like described in the specification mean a unit for processing at least one function or operation and may be implemented by hardware or software or a combination of hardware and software .

In this specification, a terminal is a user equipment, a device, a user equipment (UE), a mobile equipment (ME), a mobile station (MS), a mobile terminal (MT), a subscriber station SS, a portable subscriber station (PSS), a user equipment (UE), an access terminal (AT), or the like, and may be referred to as a mobile terminal, User devices, and the like.

The terminal may be a mobile communication terminal capable of handling SIP (Session Initiation Protocol) signaling, and may be any communication device capable of performing IP-based communication such as a mobile phone as well as a personal portable terminal. For example, the terminal may be a cellular phone, a PCS (Personal Communication Service) phone, a PDA (Personal Digital Assistant) phone, a GSM (Global System for Mobile Communications) phone, a WCDMA (Wideband Code Division Multiple Access) Access) -2000 phone, Digital Multimedia Broadcasting (DMB) phone, Long Term Evolution (LTE) phone, and the like.

Hereinafter, a conference call processing server and its method according to an embodiment of the present invention will be described with reference to the drawings.

In the present invention, a conference call (or a multi-party call) means a phone call made by at least three or more persons at the same time. Here, the telephone call may include a voice call or a video call.

FIG. 1 is a configuration diagram of a conference call system according to an embodiment of the present invention. FIG. 2 is a flowchart illustrating a conference call method according to an embodiment of the present invention. 4 is a diagram illustrating an example of a conference call request message according to an embodiment of the present invention. FIG. 5 illustrates an example of a changed conference call request message according to an embodiment of the present invention. 6 is an exemplary view of a conference call invitation message according to an embodiment of the present invention, and FIG. 7 is an exemplary view of a conference call invitation message according to an exemplary embodiment of the present invention.

Referring to FIG. 1, when the calling terminal 200 requests a call connection with at least two called terminals 301 and 303, the calling conference calling system 100 transmits the calling terminal 200 and the called terminals 301, 303) for transmission of a call. According to the SIP, the allocation of transmission resources is performed through a session connection between the calling terminal 200 and at least two called terminals 301, 303. When the session is established, the calling terminal 200 and the at least two called terminals 301 and 303 can simultaneously exchange voice packets through a connected session, which can be performed according to a VoIP (Voice over Internet Protocol) method.

Here, the conference call conference system 100 includes a call session control function (hereinafter referred to as 'CSCF') 101, a called CSCF 103, a call- (Hereinafter referred to as "TAS") 105, a called party TAS 107, and a conference call server 109.

The CSCFs 101 and 103 perform session control such as connection of a call session and release of a call session between the calling terminal 200 and at least two called terminals 301 and 303 and perform subscriber registration, Routing, lookup of the called party location, compression and release of the SIP message, and the like.

The CSCF (101, 103) relays the message exchange for the conference call. At this time, the message can use the SIP message. The CSCFs 101 and 103 forward SIP messages to each entity in the conference call system 100 to provide a conference call service, thereby allowing the session to be completed.

CSCFs 101 and 103 generate triggers for outgoing or incoming calls. The trigger is set in the CSCF 101, 103 in advance for the purpose of the subscriber's outgoing call or incoming call being forwarded to the TAS 105, 107.

The TAS 105, 107 is an application service node providing a telephony service, and processes a conference call according to an embodiment of the present invention.

The TAS 105 and 107 confirm whether or not the conference call service is subscribed according to the conference call request of the terminals 200 and 301 and 303 and the conference call server 109 synchronizes with the conference call server 109, 301, and 303 to establish a media session for a conference call.

At this time, the TAS 105 and 107 can confirm whether each terminal 200, 301, and 303 joins the conference call service through a service profile provided by a home subscriber server (HSS) (not shown).

At this time, the TASs 105 and 107 are divided into the calling TAS 105 and the called TAS 107, but they may be implemented as one integrated TAS.

The conference call server 109 is a device for implementing a conference call in an IP (Internet Protocol) network, and is generally constructed in the form of an independent server. The terminals 200, 301, and 303 participating in the conference call are not directly connected to each other but are connected through the conference call server 109. [

The conference call server 109 performs a function of creating a new session to the called party as if it is a caller after terminating an outgoing call requesting a conference call as if it is the called party. Here, when creating a session with the called party, a conference call invitation message is transmitted to the called parties.

 The conference call server 109 supports call conferencing between the terminals 200, 301, and 303 by performing a call mixing process for providing a conference call service. That is, the conference call server 109 establishes a one-to-one session with each of the terminals 200, 301, and 303 participating in the conference call. The conference call server 109 receives all the call signals generated by the terminals 200, 301 and 303, mixes them, and encodes them into signals that can be processed by one terminal. And transmits the encoded signal to the corresponding terminal (200, 301, 303) through a session set in each terminal (200, 301, 303).

Referring to FIG. 2, the user inputs a conference call connection number and at least two incoming call numbers through the input means of the calling terminal 200 (S101), and when the calling button is clicked, the calling terminal 200 transmits a conference call And transmits a request message (INVITE) to the calling side CSCF 101 (S103).

Here, according to one embodiment, the conference call access number may be that the user establishes a conference call and is given a conference call connection number. For example, the conference call access number may be opened and granted via the web.

According to another embodiment, at least one conference call access number may be designated and used for each corporate subscriber in advance. Alternatively, a predetermined number band may be fixedly used as a conference call connection number. For example, a company A subscriber can use a conference call access number such as 010-9876-1234, 010-9876-1235, 010-9876-1236, etc. from a communication carrier for conference call.

3, the user inputs a conference call access number (e.g., 01098769876), at least two incoming phone numbers (e.g., 01045674567, 01056785678), and clicks a call button, request. That is, the call connection request (dial-out) is made directly to the incoming telephone number.

At this time, the user inputs the conference call access number and at least two incoming phone numbers, and the numbers are divided through predetermined delimiters. That is, a delimiter such as '#' can be entered between the number and the number. Of course, the delimiter is not limited to #, but various symbols can be used.

2, the calling terminal 200 transmits a conference call access number, at least two incoming phone numbers, and each number (hereinafter, referred to as " phone number ") entered by a user to a field containing caller information, I.e., all telephone numbers and symbols in the inputted order as shown in FIG. 3 are included. As described above, the conference call request message (INVITE) transmitted in step S103 may be represented as shown in FIG.

Basically, a SIP message consists of a START LINE, a HEADER field and a BODY field. At this time, the conference call request message (INVITE) 400 of FIG. 4 is shown with the exception of the body field.

Referring to FIG. 4, a conference call request message (INVITE) 400 includes a start line 401 and a plurality of HEADER fields 403.

The start line 401 includes a method, a SIP URI (Uniform Resource Identifier), and SIP version information. The method represents the message type, and 'INVITE' is described. The SIP URI is a kind of URI specifying the receiver of the SIP message, and may be called a Request-URI, and a tel URI is used. The way in which Internet terminals recognize the telephone number of the telephone network is the tel URI. SIP version information is described in SIP / 2.0.

At this time, the tel URI includes all telephone numbers and symbols entered by the user in step S101. That is, the tel URI includes the conference call connection number, at least two incoming telephone numbers, and delimiters between the numbers in the order in which they are entered.

A plurality of header fields 403 are header fields describing values for controlling a session, and include header fields such as To, Via, Cseq, From, Route, Call-ID, and Contact. Since these header fields correspond to a known technique, detailed description will be omitted.

2, when the calling CSCF 101 receives a conference call request message (INVITE) from the calling terminal 200, the calling CSCF 101 transmits a calling trigger to the calling TAS 105 (S105). The calling CSCF 101 checks the calling party information of the conference call request message (INVITE), confirms that the corresponding TAS is the calling TAS 105, and sends the calling trigger to the calling TAS 105. At this time, the origination trigger is a conference call request message (INVITE).

The originating TAS 105 recognizes the conference call based on the recipient information of the conference call request message INVITE (S107). Here, the recipient information may be a tel URI, and the originating TAS 105 may recognize the conference call via the form of the tel URI. That is, the conference call number can be recognized through the conference call connection number. For example, if the number band specified in the conference call connection number is stored in advance and the number band stored in the telephone number included in the tel URI is included, it can be recognized as a conference call number. Or it may recognize a conference call via a form that includes multiple phone numbers. Or the conference call access number obtained by querying the conference call server 109 with the telephone number included in the tel URI to confirm that the call is a conference call.

When the originating TAS 105 recognizes the conference call, it determines that a call connection should be established through the conference call server 109, and changes the conference call request message (INVITE) (S109). At this time, the calling TAS 105 changes the recipient of the conference call request message (INVITE) to the conference call server, and the modified conference call request message (INVITE) can be represented as shown in FIG.

Referring to FIG. 5, the modified conference call request message (INVITE) is the same as that of FIG. 4 except that the information included in the start line 501 and the plurality of header fields 503 are different.

The originating TAS 105 leaves the tel URI of the start line 401 with the conference call access number (e.g., +821098769876), and excludes the remaining incoming phone numbers and delimiters.

The header field 503 further includes a newly defined conference call participant (e.g., P-KT-Conference-List) field 505. The originating TAS 105 stores the incoming telephone numbers, which are excluded from the tel URI, in the conference call participant field 505. In this case, the incoming telephone numbers are respectively included in the form of a tel URI, for example, <tel: +821045674567> and <tel: +821056785678>. As such, each number is separated by <> and.

Referring again to FIG. 2, the calling TAS 105 returns the conference call request message (INVITE) changed in step S109 to the calling CSCF 101 (S111).

The source CSCF 101 transmits the changed conference call request message INVITE to the called CSCF 103 corresponding to the conference call server 109 in step S113. As described above, the calling TAS 105 changes the tel URI of the conference call request message (INVITE), and causes the conference terminal server 109 to receive the conference call request message transmitted by the calling terminal 200 (S103).

The destination CSCF 103 transmits an incoming trigger to the destination TAS 107 to which the conference call server 109 is connected (S115). At this time, the incoming trigger is a conference call request message (INVITE) changed (S109).

The called party TAS 107 recognizes the conference call based on the recipient information of the conference call request message (INVITE) changed (S109) (S117). Then, a conference call session is established with the conference call server 109 corresponding to the receiver (S119). Here, the conference call session connection S119 includes a series of operations such as sending and receiving a SIP message between the called TAS 107, the conference call server 109, and the calling terminal 200, It is only a connection technique, so a detailed description will be omitted.

The called party TAS 107 confirms the recipient information for which the calling terminal 200 requested the conference call through the conference call participant field of the conference call request message INVITE changed S109. In response to the request or response of the conference call server 109, a conference call invitation message (INVITE) is invited to invite each recipient for each recipient recorded in the conference call participant field 505 S121) to the destination CSCF 103 (S123, S125). At this time, if two recipients are assumed, two conference call invitation messages (INVITE), i.e., INVITE1 and INVITE1, are generated.

The destination CSCF 103 transmits the generated conference invitation messages INVITE1 and INVITE2 to the corresponding destination terminals 301 and 303, respectively (S127 and S129).

At this time, the conference call invitation messages INVITE1 and INVITE2 may be represented as shown in FIG. 6 and FIG.

6, the tel URI of the start line 601 of the conference call invitation message INVITE1 includes the incoming telephone number of the receiving terminal 301 (e.g., +821045674567). The header field 603 is identical to the conference call request message (INVITE) transmitted by the calling terminal 200 illustrated in FIG.

Referring to FIG. 7, the tel URI of the start line 701 of the conference call invitation message INVITE2 includes the incoming telephone number of the call receiving terminal 303 (e.g., +821056785678). The header field 703 is identical to the conference call request message (INVITE) transmitted by the calling terminal 200 illustrated in FIG.

After the step S129, each of the receiving terminals 301 and 303 responds to each other to transmit and receive SIP messages between the calling terminal 200, the called terminals 301 and 303, and the conference call server 109, Is a known technology, and thus a detailed description thereof will be omitted.

In addition, although not shown, when the called terminal 1 (301) is connected to a called CSCF other than the called CSCF1 103, a conference call invitation message INVITE2 is transmitted between the step S125 and S129 to the called terminal 1 301 ) May be added to the called party CSCF and the called party TAS.

8 is a configuration diagram of a conference call system according to another embodiment of the present invention.

Referring to FIG. 8, description of the same components as those of FIG. 1 will be omitted. In the conference call conference system 100 of FIG. 8, the called terminal 2 (303) is different from the communication service provider. Since the incoming CSCF2 (111) corresponds to the configuration of another communication carrier, it may not be the CSCF, and is a configuration that means a session control device or a call processing device.

1 to 7, except that the conference call invitation message (INVITE2) transmitted by the called party CSCF1 103 is transmitted to the called terminal 2 (303) via the called party CSCF2 (111) . Such a configuration corresponds to a general incoming call procedure, and thus the configuration of other communication carriers is not required to be changed.

Therefore, even if the calling terminal 200 makes a call like a normal call, the calling TAS 105 changes the conference call request message (INVITE) so that it can be received by the conference call server 109, The service according to the present invention can be implemented without changing the service.

9 is a hardware block diagram of a conference call system according to another embodiment of the present invention.

9, each entity included in the conference call system 900 or the conference call system 900, i.e., the session control device (CSCF) 900 or the call processing device (TAS) 900, 901), a memory 903, and a processor 905, and stores a program that is executed in combination with hardware at a specified location. The hardware has a configuration and performance capable of executing the configuration and / or the method according to the embodiments described in Figs. 1-8. The communication device 901 is connected to the processor 905 and transmits and / or receives signals to / from an external device via a network (not shown).

The memory 903 stores programs that are associated with the processor 905 and include instructions that cause the configuration and / or method according to the embodiments described in Figs. 1-8 to be executed. The processor 905 executes the program stored in the memory 903. [

FIG. 10 is a hardware block diagram of a terminal according to an embodiment of the present invention, and shows the hardware configuration of the calling terminal 200 described in FIGS. 1 to 8. FIG.

10, the calling terminal 1000 is composed of hardware including a communication device 1001, a memory device 1003, a display 1005, an input device 1007, and a processor 1009, A program to be executed in combination with hardware is stored. The hardware has a configuration and performance capable of executing the configuration and / or the method according to the embodiments described in Figs. 1-8. At this time, the display 1005 and the input device 1007 may be implemented as a single device. The program includes instructions that may execute the configuration and / or methodology in accordance with the embodiments described in FIGS. 1-8, and may be implemented in conjunction with hardware such as memory device 1003 and processor 1009 to implement the invention do. At this time, when generating the conference call request message (INVITE), all telephone numbers and symbols entered by the user are included in the Request-URI as they are in the input order and the input number.

As described above, according to the embodiment of the present invention, a method of inviting participants to an existing conference call service is improved, so that a conference call can be started more easily. In addition, The conference call service can be applied without.

The embodiments of the present invention described above are not implemented only by the apparatus and method, but may be implemented through a program for realizing the function corresponding to the configuration of the embodiment of the present invention or a recording medium on which the program is recorded.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed exemplary embodiments, It belongs to the scope of right.

Claims (14)

A call processing server for processing a conference call,
A memory for storing a program for processing the calling terminal and the at least two called terminals so that the conference call is connected through the conference call server; and
And a processor for executing the program,
The program includes:
Receiving a conference call request message set by the user as a recipient and receiving the conference call connection message from the calling terminal, and transmitting the conference call request message corresponding to the conference call connection number To the conference call server,
And instructions for sending a conference call invite message to each called terminal corresponding to the respective incoming phone numbers in association with the conference call server. The method of claim 1,
The conference call request message includes:
The conference call access number and the incoming telephone numbers of each of the at least two destination terminals are included in the receiver identifier,
The program includes:
The remaining call forwarding numbers are deleted while leaving only the conference call access number in the recipient identifier, the incoming call numbers are included in the newly defined conference call participant field to change the conference call request message, And for forwarding the call to the conference call server. 3. The method of claim 2,
The program includes:
And generating each conference call invite message having each recipient phone number stored in the conference call participant field as a recipient identifier according to a request or response of the conference call server. 4. The method of claim 3,
The conference call request message, which is received from the calling terminal,
(INVITE) message of a Session Initiation Protocol (SIP), a Request-URI specifying a recipient is set to the conference call access number and the at least two incoming telephone numbers,
The Request-
And a delimiter is input between the conference call connection number and the at least two incoming call numbers. 4. The method of claim 3,
The changed conference call request message may include:
(INVITE) message of a Session Initiation Protocol (SIP) to which the conference call participant field is added in a header field. 4. The method of claim 3,
Wherein each of the conference call invite messages comprises:
A Session Initiation Protocol (SIP) INVITE message, wherein a Request-URI specifying a recipient is set for each incoming phone number. A conference call processing method performed by an originating call processing server operated by at least one processor,
Receiving a call request message from a calling terminal,
Determining a recipient of the call request message and determining whether the call request is a conference call request; and
Receiving a call request message from the calling terminal and at least two or more calling terminals to a conference call server that provides a conference call service when it is determined to be the conference call request,
The conference call request includes:
Wherein the conference call access number corresponding to the conference call server is included in the recipient of the call request message. 8. The method of claim 7,
The call request message is an INVITE message of a Session Initiation Protocol (SIP)
The receiving step comprises:
If the conference call connection number and at least two incoming call numbers are included in the Request-URI designating the recipient of the INVITE message, only the conference call connection number is left in the Request-URI, Modifying the INVITE message by writing the at least two incoming telephone numbers extracted from the URI in a header field of the INVITE message;
Transmitting the changed INVITE message to the conference call server
Wherein the conference call processing method comprises the steps of: 9. The method of claim 8,
Wherein the modifying comprises:
Wherein the at least two incoming telephone numbers extracted from the Request-URI are recorded in a newly defined conference call participant field in the header field. 9. The method of claim 8,
Wherein the receiving comprises:
Receiving the INVITE message originated from the originating session control device,
Wherein the step of transmitting to the conference call server comprises:
And transmitting the changed INVITE message to the conference call server through the called session control device connected to the calling session control device and the conference call server. A conference call processing method performed by at least one processor and performed by a called party call processing server connected to a calling terminal and at least two calling terminals and connected to a conference call server for providing a conference call service,
Receiving a conference call request message from a calling side communication network connected to the calling terminal,
Transmitting the conference call request message to the conference call server,
Checking at least two incoming telephone numbers from the header field of the conference call request message in cooperation with the conference call server, and
And generating a conference call invitation message having each of the confirmed incoming phone numbers as a receiver, and transmitting the generated conference call invitation message to each of the corresponding called terminals,
The conference call request message includes:
Wherein the conference call access number corresponding to the conference call server is set to the recipient identifier. 12. The method of claim 11,
The conference call request message includes:
The call request message transmitted by the calling terminal is changed in the calling side call processing server,
Wherein the call is triggered from the called session control device after being transmitted to the called session control device via the calling session control device. The method of claim 12,
The conference call request message includes:
SIP (Session Initiation Protocol) INVITE message,
Wherein the conference call connection number is stored in a Request-URI designating a recipient of the INVITE message,
Wherein the at least two incoming phone numbers are included in the newly defined conference call participant field of the header field of the INVITE message. The method of claim 13,
The conference call invitation message includes:
SIP (Session Initiation Protocol) INVITE message,
Wherein each incoming call number is stored in a Request-URI designating a recipient of the INVITE message.

Images