WO2011017999A1 - Ip多媒体子系统会议中单方通话的方法及服务设备 - Google Patents

Ip多媒体子系统会议中单方通话的方法及服务设备 Download PDF

Info

Publication number
WO2011017999A1
WO2011017999A1 PCT/CN2010/075626 CN2010075626W WO2011017999A1 WO 2011017999 A1 WO2011017999 A1 WO 2011017999A1 CN 2010075626 W CN2010075626 W CN 2010075626W WO 2011017999 A1 WO2011017999 A1 WO 2011017999A1
Authority
WO
WIPO (PCT)
Prior art keywords
conference
communication device
call
message
request message
Prior art date
Application number
PCT/CN2010/075626
Other languages
English (en)
French (fr)
Inventor
杨强
王忱
唐飞
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to AU2010282015A priority Critical patent/AU2010282015A1/en
Priority to IN1512DEN2012 priority patent/IN2012DN01512A/en
Priority to MX2012001794A priority patent/MX2012001794A/es
Priority to BR112012003051-5A priority patent/BR112012003051B1/pt
Priority to EP10807944.3A priority patent/EP2466842B1/en
Priority to US13/258,372 priority patent/US20120134302A1/en
Priority to RU2012101842/08A priority patent/RU2515703C2/ru
Publication of WO2011017999A1 publication Critical patent/WO2011017999A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H04L65/403—Arrangements for multi-party communication, e.g. for conferences
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
    • H04L12/1822—Conducting the conference, e.g. admission, detection, selection or grouping of participants, correlating users to one or more conference sessions, prioritising transmission
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1083—In-session procedures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H04L65/401—Support for services or applications wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference
    • H04L65/4015—Support for services or applications wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference where at least one of the additional parallel sessions is real time or time sensitive, e.g. white board sharing, collaboration or spawning of a subconference
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/1886—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with traffic restrictions for efficiency improvement, e.g. involving subnets or subdomains
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]

Definitions

  • the present invention belongs to the field of communications technologies, and in particular, to a method and a service device for single-party calling in an IP Multimedia Core Network Subsystem (IMS) conference.
  • IMS IP Multimedia Core Network Subsystem
  • the IMS system is an Internet Protocol (IP)-based network architecture proposed by the 3rd Generation Partnership Project (3GPP) to build an open and flexible business environment.
  • IP Internet Protocol
  • 3GPP 3rd Generation Partnership Project
  • a conference is a service in an IMS system.
  • the service includes a conference chairperson who hosts the conference and a conference member who participates in the conference.
  • the service allows multiple conference members and the conference chairperson to talk at the same time, that is, the conference member or the conference chairperson speaks other conferences. Members or conference chairmen can hear.
  • the chairman of the meeting can do the operations of joining the meeting members, kicking out the meeting members and isolating the meeting members according to their own wishes.
  • the chairman of the meeting cannot apply for a one-way conversation with a member of the meeting, while maintaining the meeting chairman and other meeting members.
  • the so-called conference chairman and the conference member unilaterally talk, that is, let the conference chairman and the designated conference member unilaterally talk without affecting the other conference members to continue the conference.
  • an object of the present invention is to provide a method and a service device for single-party calling in an IP multimedia subsystem conference, which can implement a one-party conversation between a conference chairperson and a conference member during a conference.
  • the present invention provides a method for single-party calling in an IP multimedia subsystem conference, and the method includes:
  • the service device according to the received first request message, modifying the conference media in the communication device that has joined the conference in the first communication device and the second communication device;
  • the service device After the modification of the conference medium is completed, the service device establishes a one-party conversation between the first communication device and the second communication device.
  • the first communication device is a communication device on the conference chair side
  • the second communication device is a communication device on the user member side.
  • the method further includes: the service device forwarding the first request message to the second communication device;
  • the second communication device sends a second request message to the service device, where the second request message is a request message sent by the second communication device to perform a one-party call with the first communication device;
  • the service device modifies the conference media in the communication device that has joined the conference in the first communication device and the second communication device.
  • the first communication device is a communication device on the user member side
  • the second communication device is a communication device on the conference chair side.
  • the service device modifies the conference media in the communication device that has joined the conference in the first communication device and the second communication device:
  • the service device shields the first communication device and the second communication device from a call between other communication devices in the conference, and/or
  • the service device shields the other communication device in the conference from a call between the first communication device and the second communication device.
  • the service device modifies the conference media of the first communication device and the second communication device, and resumes a call between the first communication device and the second communication device and a previous conference.
  • the method further includes:
  • the service device sends call information to the second communication device
  • the service device After the second communication device answers the call of the service device, the service device establishes a one-party call between the first communication device and the second communication device.
  • the method also includes:
  • the service device releases the second communication device, and modifies the conference media message of the first communication device, and restores the first communication device to Conference call.
  • a service device for a single-party call in an IP multimedia subsystem conference includes: a message receiving module, a processing module, and a single-party calling module;
  • the message receiving module is configured to receive a first request message sent by the first communications device, where the first request message is a message that is sent by the first communications device to perform a one-way call with the second communications device;
  • the processing module is configured to modify the first according to the received first request message a conference medium of the communication device that has joined the conference in the communication device and the second communication device; the setting a single-party call module, configured to establish the first communication device and the second after the conference media modification is completed One-way communication of communication devices.
  • the service device further includes a message forwarding module, configured to forward the first request message to the second communication device;
  • the message receiving module is further configured to receive a second request message sent by the second communications device, where the processing module is further configured to modify the first communications device according to the received second request message
  • the conference medium of the communication device of the conference has been added to the second communication device.
  • the service device further includes:
  • a content screening module configured to block a call between the other communication devices in the conference from the first communication device and the second communication device, and/or
  • a call between the first communication device and the second communication device is shielded from other communication devices in the conference.
  • the message receiving module is further configured to receive a request message that is sent by the first communications device and is unicast from the second communications device;
  • the processing module is further configured to modify the conference media of the first communication device and the second communication device according to the received request message for exiting the single-party call with the second communication device, and restore the A call of the first communication device and the second communication device with a previous conference.
  • the service device further includes:
  • a calling module configured to send call information to the second communications device when the first communications device and the second communications device are not in the same conference
  • the message receiving module is further configured to receive a response of the second communications device to the call information, where the processing module is further configured to establish, according to the received response, the first communications device and the second One-way communication of communication devices.
  • the message receiving module is further configured to receive an exit single-party call sent by the first communications device Request message
  • the processing module is further configured to: when the first communication device exits the single-party call, release the second communication device, and modify the conference media message of the first communication device, and restore the first communication device and The call from the previous meeting.
  • the present invention modifies the conference media of the conference chairperson and/or the conference member, so that the conference chairperson can conveniently implement a one-party call with a conference member according to the actual situation. It is possible for the conference members to conveniently make a one-way conversation with the conference chairperson according to their own wishes and according to the actual situation.
  • FIG. 1 is a flowchart of a method for a single-party call in an IMS system conference according to an embodiment of the present invention
  • FIG. 1A is a schematic flowchart of a method for a conference chairperson to apply for a separate call with another user
  • FIG. 1B is a conference member application and a conference chairperson of the present invention.
  • FIG. 2 is a flowchart of a method in which a conference chairperson applies for a one-party call with a conference member according to an embodiment of the present invention
  • FIG. 3 is a flowchart of a conference chairperson applying for a one-party call with a conference outside the conference according to an embodiment of the present invention;
  • Figure 1 is a flowchart of a method for a single-party call in an IMS system conference according to an embodiment of the present invention
  • FIG. 1A is a schematic flowchart of a method for a conference chairperson to apply for a separate call with another user
  • FIG. 1B is a conference member application
  • FIG. 4 is a flow chart of a conference member applying a one-party call with a conference chair in an embodiment of the present invention
  • FIG. 5 is a structural block diagram of a service device according to an embodiment of the present invention. detailed description
  • the service device first receives a first request message sent by the first communication device as the conference chairperson and the second communication device performs a one-party call; and then, the service device, according to the received first request message, Modifying the conference media of the communication device that has joined the conference in the first communication device and the second communication device; finally, after the conference media modification is completed, the service device establishes a one-party call between the first communication device and the second communication device.
  • FIG. 1 is a flowchart of a method for single-party calling in a conference of an IMS system according to the present invention. As shown in FIG. 1, the specific steps of a single-party call in a conference of the IMS system of the present invention are as follows:
  • Step 101 The service device receives a first request message that is sent by the first communication device and the second communication device performs a one-party call.
  • the first communication device is a communication device that is participating in a conference with other communication devices
  • the second communication device may be a communication device participating in the conference, a communication device participating in other conferences, or a non-meeting communication device.
  • Step 102 The service device determines whether the first communication device and the second communication device are in the same conference. If yes, go to step 103; otherwise, go to step 107.
  • the service device may parse the identification information of the first communication device and the second communication device carried in the first request message, and then query the identifier information of the first communication device and the identifier of the second communication device. Whether the information is in the identification information list of the communication device of the same conference, if all, it can be determined that the first communication device and the second communication device are in the same conference; otherwise, the first communication device and the second communication device are not in the same conference. in.
  • the identification information of the communication device may be the number information of the communication device, or may be the IP address of the communication device, and determine whether the first communication device and the second communication device are in the same conference. Limited to this.
  • Step 103 Determine whether the first communication device is the communication device on the conference chair side of the conference service or the communication device on the conference member side. If the first communication device is the communication device on the conference chair side, step 106 is performed; if the first communication device is For the communication device on the conference member side, step 104 is performed.
  • the first communication device can be determined as the communication device on the conference chair side according to the identification information of the first communication device, and if the first communication device is the communication device on the chair side, the service is The device may modify the conference media in the first communication device and the second communication device according to the first request message received in step 101, when the first communication device and the second communication device have joined the same conference.
  • Step 104 The service device forwards the first request message sent by the first communication device to the second communication device to perform a one-party call with the second communication device, and then performs step 105.
  • Step 105 The second communication device sends a second request message requesting a one-party conversation with the first communication device to the service device, and then step 106 is performed.
  • Step 106 The service device modifies the conference media of the first communication device and the second communication device, and establishes a one-party call between the first communication device and the second communication device, and the process ends.
  • Step 107 The service device modifies the conference media of the first communication device, and then performs step 108.
  • the first communication device may be a communication device on the conference chair side of a conference, or may be a communication device on the conference member side.
  • the first communication device is the communication device on the conference chair side.
  • Step 108 After the second communication device answers the call of the service device, the service device establishes a one-party call between the first communication device and the second communication device.
  • the service device Before performing step 108, the service device sends a call request to the second communication device according to the identification information of the second communication device carried in the first request message.
  • FIG. 1A the method for the conference chairperson to apply for a separate call with other users is shown in FIG. 1A.
  • the method for the conference member application and the conference chairperson to talk separately is shown in FIG. 1B.
  • the conference media of the conference chairperson and/or the conference member is modified, so that the conference chairperson can conveniently cooperate with a conference member according to the actual situation.
  • the conference members can also conveniently make a one-way conversation with the conference chairperson according to their own wishes and according to the actual situation.
  • a process of unilateral conversation between a conference chairperson and a conference member or a non-meeting member in an IMS system conference is described, and between the conference chairperson and the conference member or non-meeting member is described below.
  • the unilateral call is divided into three situations:
  • Case 1 The chairman of the meeting applies for a one-way conversation with a member of the meeting, and after the call ends, the chairman of the meeting and the member of the meeting return to the meeting;
  • Case 2 The chairman of the meeting applies for a unilateral call with a user (non-conference member) outside the meeting, and after the call ends, the chairman of the meeting can return to the meeting and release the user at the same time;
  • Scenario 3 A conference member applies and the conference chairman unilaterally calls. After the call ends, the conference chairman and the conference member can return to the conference;
  • the conference in the IMS system includes: conference chair UE-A, conference member UE-B, conference member UE-C, and conference member UE-D, and UE-A, UE-B, UE -C, UE-D has entered the conference, and the process of entering the conference can be implemented through existing technologies.
  • the conference chairperson applies to the service device for a unilateral conversation with a conference member, and after the unilateral call ends, the conference chairperson and the conference member can return to the conference and continue to participate in the conference.
  • FIG. 2 is a flowchart of a conference party requesting a one-party call with a conference member in the embodiment of the present invention. As shown in FIG. 2, in the embodiment of the present invention, the specific steps of the conference chairperson requesting a one-party call with the conference member are as follows:
  • Step 201 The conference chair UE-A and the conference members UE-B, UE-C, and UE-D join the conference.
  • the conference chair UE-A can join the conference members UE-B, UE-C, and UE-D to the conference by using existing technologies.
  • Step 202 The conference chairperson UE-A sends a request message for the one-party call between the conference chair UE-A and the conference member UE-B to the service device.
  • the request message for performing the one-way call may be a REFER message, where the "method" parameter of the Refer-To header field of the REFER message may be set to "INVITE", and the conference chairman UE-A needs to be unilaterally called in the REFER message.
  • User identification information of the conference member UE-B the user identification information may be the telephone number information of the conference member, or may be the IP address of the conference member, and is not limited thereto.
  • the service device may determine that the request message is the conference chairperson UE-A request and the conference member according to the user corresponding to the user identity information of the called conference member carried in the REFER message that the user is already in the conference, and the "method" parameter is "INVITE".
  • UE-B makes a request message for a one-party call.
  • the REFER message defined in RFC3515 can be used for both the single-party call application and the exit, so that only the conference chairperson and the conference member who makes a one-way call with the conference chairperson support REFER and NOTIFY message processing, and other conference members can REFER and NOTIFY message processing are not supported, and other conference members may not be Session Initiation Protocol (SIP) users.
  • SIP Session Initiation Protocol
  • the specific message that the conference chairperson UE-A requests to unilaterally talk with the conference member is not limited to the above REFER message, and the specific content of the message is not limited to the "method" parameter of the REFER message, as long as the service device can be made with the appropriate message.
  • the "method" parameter can be extended so that the service device and the conference chairperson can make a request for a single call or exit the unilateral according to more specific instructions. Call and other judgments.
  • Step 203 The service device sends an acceptance message to the conference chairperson UE-A to accept the one-way call request.
  • Step 204 The service device sends a conference call progress notification to the conference chairperson UE-A, the conference chair UE-A and the conference member UE-B.
  • Step 205 The service device sends a conference media request to modify the conference chair UE-A and the conference member UE-B to the conference resource.
  • Step 206 The conference resource returns a conference media response that modifies the conference chair UE-A and the conference member UE-B to the service device.
  • the conference resource can modify the user media of the conference chair UE-A and the conference member UE-B and the corresponding conference media according to the indication of the request message of the single-party call and the processing logic of the service device, and do not allow the UE- A and UE-B send a message to the conference, that is, the service device blocks the content of the call between UE-A and UE-B to other conference members, and/or does not prevent the conference from being forwarded to the conference chair UE-A and the conference member UE.
  • -B sends a message, that is, the conference chair UE-A and the conference member UE-B block the content of the call between other conference members.
  • Steps 207 - 213 The service device modifies the conference media of the conference chair UE-A and the conference member UE-B, and establishes a one-party call between the conference chair UE-A and the conference member UE-B.
  • Step 214 The service device sends a success message to the conference chairperson UE-A to implement a one-party call between the conference chair UE-A and the conference member UE-B.
  • the service device notifies the conference chairperson UE-A that the service device has successfully implemented a one-party call between the conference chair UE-A and the conference member UE-B.
  • the notification message may be a NOTIFY message, and the message body is 200 OK.
  • Step 215 The conference chairperson UE-A sends a request message that the conference chair UE-A and the conference member UE-B exit the one-party call to the service device.
  • the conference chair UE-A sends a request message for exiting the one-party call to the service device, and the request message may be a REFER message, where the message is Refer-To
  • the "method" parameter of the header field may be "INVITE”, and the message carries the user identification information of the conference member UE-B, and the user identification information may be the telephone number information of the conference member UE-B, or the conference member UE-B.
  • IP address the service device can correspond to the conference according to the identification information of the called conference member carried in the REFER message.
  • the UE-A conference party member UE-B of the one-party call can determine that the message is the conference chairperson UE-A and the conference chair UE-A and the conference member UE-B exit the one-party call according to the "method" parameter of "INVITE".
  • Step 216 The service device sends the conference chair UE-A and the conference member UE-B to the conference chair UE-A to cancel the acceptance message of the one-party call request.
  • the service device After the service device receives the request message for exiting the one-party call, the service device sends an accept message for exiting the one-way call request to the conference chairperson UE-A, and the accept message may be set to 202.
  • Step 217 The service device sends a conference chairperson to the conference chairperson UE-A UE-A and the conference member UE-B exits the one-party call progress message.
  • the service device notifies the conference chairperson UE-A that the service device has started the process of the conference chair UE-A and the conference member UE-B exiting the one-party call, and the progress message can make the NOTIFY message, and the message body is 100 Trying.
  • Steps 218 - 224 The service device modifies the conference media of the conference chair UE-A, the conference member UE-B, and the corresponding conference media, and restores the call between the conference chair UE-A and the conference member UE-B and the previous conference, so that the conference chair UE -A and the conference member UE-B return to the conference, so that the conference chair UE-A communicates with the conference member UE-B, the conference member UE-C, and the conference member UE-D.
  • Step 225 The service device sends a success message to the conference chairperson UE-A that the conference chair UE-A and the conference member UE-B exit the one-party call and return to the conference.
  • the service device may notify the conference chairperson UE-A that the conference device UE-A and the conference member UE-B have successfully exited the unilateral call and returned to the conference.
  • the notification message may be a NOTIFY message.
  • the message body is 200 OK.
  • the conference chair UE-A and a conference member can be unicast, and after the call ends, the conference chair UE-A and the conference member return to the conference.
  • Embodiment 2
  • the conference of the IMS system includes: conference chair UE-A, The conference member UE-B and the conference member UE-C, and the UE-A, UE-B, and UE-C have entered the conference, and the process of entering the conference can be implemented by using the prior art.
  • other members of the meeting who want to attend the meeting can join the meeting through existing technology.
  • the conference chairperson applies for a unilateral conversation with a non-conference member outside the conference. After the call ends, the conference chairman returns to the conference and releases the non-meeting member.
  • FIG. 3 is a flowchart of a method for a conference chairperson to make a one-party call with a user outside the conference in the embodiment of the present invention. As shown in FIG. 3, the specific steps of the conference chairperson in the second embodiment to apply for a single call with a user outside the conference are shown in FIG. as follows:
  • Step 301 The conference chair UE-A joins the conference members UE-B and UE-C to the conference.
  • the conference chair UE-A can join the conference members UE-B and UE-C to the conference by using existing technologies.
  • Step 302 The conference chairperson UE-A sends a request message for the one-party call between the conference chair UE-A and the non-meeting member UE-D to the service device.
  • the request message for performing the one-way call may be a REFER message, where the "method" parameter of the Refer-To header field of the REFER message may be "INVITE", and the user who needs to talk with the conference chairman UE-A in the REFER message is carried in the REFER message.
  • the identification information of the UE-D (non-conference member), the identification information may be the phone number information of the user, or may be the IP address of the user, and is not limited thereto.
  • the service device may not be in the conference according to the identifier information of the called user carried in the REFER message, and the "replace" field is not present, and the "method" parameter is "INVITE" to determine that the message is the conference chair UE.
  • -A requests a request message for a one-way call with a non-meeting member UE-D.
  • the specific message requested by the conference chairperson UE-A and the non-meeting member UE-D is not limited to the REFER message, and the specific content of the message is not limited to the "method" parameter of the REFER message, as long as the appropriate message is used.
  • Ability to let the service device know the meeting chair or meeting The intent of the member is to let the conference chairperson or conference member know the service device's handling of the request.
  • the "method" parameter can be extended so that the service device and the conference chairperson can make a request for a unilateral call according to more specific instructions. .
  • Step 303 The service device sends an acceptance message of the conference chair UE-A and the non-meeting member UE-D single-party call request to the conference chairperson UE-A.
  • Step 304 The service device sends, to the conference chairperson UE-A, a progress message of the conference call UE-A and the non-meeting member UE-D unilateral call.
  • the service device notifies the conference chairperson UE-A that the service device has started to process the one-party call between the conference chair UE-A and the non-meeting member UE-D.
  • the progress message of the single-party call may be a NOTIFY message, and the message body is 100 Trying.
  • Steps 305 to 306 The service device modifies the user media of the conference chair UE-A and the corresponding conference media according to the instruction of the conference chair UE-A and the non-meeting member UE-D single-party call request message and the processing logic of the service device, and does not allow
  • the conference chairperson UE-A sends a message to the conference (blocks the content of the call between the conference chair UE-A and the non-meeting member UE-D to other conference members), and/or does not allow the conference to send a message to the conference chair UE-A.
  • Conference chair UE-A blocks the content of calls between other conference members).
  • Steps 307 ⁇ 315 The service device establishes a one-party call between the conference chair UE-A and the non-meeting member UE-D.
  • Step 316 The service device sends a notification message to the conference chairperson UE-A that the conference chair UE-A and the non-meeting member UE-D have a single-party call success.
  • the service device notifies the conference chairperson UE-A that the service device has successfully implemented the conference call UE-A and the non-meeting member UE-D single-party call, and the notification message may be a NOTIFY message, and the message body is 200 OK.
  • Step 317 The conference chairperson UE-A requests the service device to quit the non-meeting member UE-D unilateral call. And the conference chair UE-A returns to the conference request message, and the request message can use the REFER message, wherein the "method" parameter of the Refer-To header field of the message can be "BYE", and the REFER message carries the non-meeting member UE-
  • the user identification information of the D may be the phone number information of the non-meeting member UE-D, or the IP address of the non-meeting member UE-D, and is not limited thereto.
  • the service device may perform a one-way call with the conference chair UE-A according to the user identifier information of the called user carried in the REFER message, and the "method" parameter is "BYE" to determine that the message is the conference chair UE-A. Request to release the non-conference member UE-D and let the conference chair UE-A return to the conference.
  • Step 318 The service device sends an acceptance message for exiting the one-party call request to the conference chairperson UE-A.
  • the service device returns a non-meeting member UE-D to the conference chairperson UE-A, and a response message that the conference chairperson UE-A returns to the conference.
  • Step 319 The service device sends a notification of the progress of the unilateral call request to the conference chairperson.
  • the service device sends a conference message to the conference chair UE-A to release the non-meeting member UE-D, and the conference chair UE-A returns to the conference, and informs the UE-A that the service device has started to release the non-meeting member UE-D, the conference.
  • the chairman UE-A returns to the processing of the conference.
  • the progress notification can be a NOTIFY message, and the message body is 100 Trying.
  • Steps 320 to 325 The service device releases the non-meeting member UE-D, and modifies the user media of the conference chairperson UE-A and the corresponding conference media, and establishes a conference call UE-A and the conference call, that is, the conference chair UE-A Go back to the meeting and achieve normal communication with other meeting members.
  • Step 326 The service device sends a conference message to the conference chair UE-A to release the non-meeting member UE-D, and the conference chair UE-A returns to the conference success message, and notifies the conference chairperson UE-A that the service device has successfully released the non-meeting member.
  • UE-D, and the conference chair UE-A returns to the conference the The work message can be a NOTIFY message, and the message body is 200 OK.
  • the voice flow can be implemented in different ways according to different terminal and service device control policies.
  • Steps 301 to 326 can implement the conference chairperson application and a single party call outside the conference. After the call ends, the conference chairperson returns. Go to the meeting and release the user.
  • the conference in the IMS system includes: conference chair UE-A, conference member UE-B, conference member UE-C, and conference member UE-D, and UE-A, UE-B, UE -C and UE-D have entered the conference, and the process of entering the conference can be implemented by existing technology.
  • UE-A, UE-B, UE -C and UE-D have entered the conference, and the process of entering the conference can be implemented by existing technology.
  • other conference members who want to attend the conference can join the conference through existing technology.
  • a conference member application and the conference chairperson make a unilateral call, and after the conference ends, the conference chairperson and the conference member can return to the conference.
  • FIG. 4 is a flow chart of a conference member applying a one-party call with a conference chairperson in the embodiment of the present invention. As shown in FIG. 4, the specific steps of a conference member applying a single-party call with the conference chairperson in the third embodiment are as follows:
  • Step 401 The conference chair UE-A and the conference members UE-B, UE-C, and UE-D join the conference.
  • the conference chair UE-A can join the conference members UE-B, UE-C, and UE-D to the conference by using existing technologies.
  • Step 402 The conference member UE-B sends a request message for the conference call UE-B and the conference chair UE-A to make a one-party call to the service device.
  • the request message for the one-way call may be a REFER message, where the "method" parameter of the Refer-To header field of the REFER message may be "INVITE", and the message carries the user identification information of the conference chairperson, and the user identity information may be the conference.
  • the telephone number information of the chairman can also be the IP address of the conference member.
  • the service device may determine, according to the called user identification information carried in the REFER message, the user identification information corresponding to the conference chairperson UE-A, and the "method" parameter is "INVITE" to determine that the message is the UE-B request and the conference chair UE.
  • Step 403 The service device forwards the request message of the one-party call sent by the conference member UE-B to the conference chair UE-A.
  • the service device judges according to the local policy that the conference member UE-B has the right to unilaterally talk with the conference chairperson, and forwards the conference member UE-B and the conference chair UE-A to make a one-party call request to the conference chair UE-A.
  • the request message can use the REFER message.
  • Step 404 The service device sends a conference message to the conference member UE-B to receive the message of the conference call UE-A single-party call request.
  • Step 405 The conference chairperson UE-A sends a request message requesting a one-party call with the conference member UE-B to the service device.
  • the conference chairperson UE-A confirms that the conference member UE-B can make a one-party call, and the conference chairperson UE-A sends the conference chair UE-A and the conference member UE to the service device.
  • the request message for the one-party call the request message may be a REFER message, where the "method" parameter of the Refer-To header field of the REFER message may be "INVITE", and the REFER message carries the conference chairman UE-A needs to be unilaterally
  • User identification information of the conference member UE-B the user identification information may be the telephone number information of the conference member, or may be the IP address of the conference member, and is not limited thereto.
  • the specific message that the conference member UE-B requests to unilaterally talk with the conference chairperson UE-A is not limited to the REFER message, and the specific content of the message is not limited to the "method" parameter of the REFER message, as long as the appropriate message is used. It is possible to let the service device know the intent of the conference chairperson or conference member, and let the conference chairperson or conference member know the service device's handling of the request, for example, the "method" parameter can be extended, so that the service device and the conference chairperson can be more clear.
  • the instructions make a judgment such as requesting a one-way call or exiting a one-way call.
  • the service device may determine that the message is the conference chairperson UE-A request and the conference member UE according to the user corresponding to the user identity information of the called conference member carried in the REFER message that the user is already in the conference, and the "method" parameter is "INVITE". B makes a one-way call.
  • Step 406 The service device sends an acceptance message of the request message of the one-party call to the conference chairperson UE-A to the conference chair UE-A and the conference member UE-B.
  • Step 407 The service device sends a progress message of the one-party call to the conference member UE-B and the conference chair UE-A to the conference member UE-B, and the conference member UE-B is notified by the progress message, and the service device has started to be the conference member UE.
  • -B performs a one-party call with the conference chair UE-A.
  • the progress message can use the NOTIFY message, and the message body is 100 Trying.
  • Step 408 The service device sends a progress message of the one-party call to the conference chair UE-A and the conference member UE-B to the conference chairperson UE-A, and notify the conference member UE-A that the service device has started to be the conference chair UE.
  • -A and the conference member UE-B perform the processing of the one-party call, and the progress message can also use the NOTIFY message, and the message body is 100 Trying.
  • Steps 409 - 410 Modify the user media of the conference chairperson UE-A and the conference member UE-B and the user according to the indication of the request message of the one-party call and the processing logic of the service device by the conference chair UE-A and the conference member UE-B
  • the corresponding conference media does not allow the conference chairperson UE-A and the conference member UE-B to send a message to the conference (block the call content between the conference chair UE-A and the conference member UE-B to other conference members), and/or not Let the conference not send a message to the conference chairperson UE-A and the conference member UE-B (to block the call content between other conference members from the conference chair UE-A and the conference member UE-B).
  • Step 411 417 The service device modifies the conference media of the conference chair UE-A and the conference member UE-B, so that the conference chair UE-A and the conference member UE-B implement a one-party call.
  • Step 418 The service device sends a conference party UE-B and the conference chair UE-A single-party call success message to the conference member UE-B, and notifies the conference member UE-B that the service device has successfully implemented the conference member UE-B and the conference chairperson.
  • UE-A single-party call The above notification message can use the NOTIFY message, and the message body is 200 OK.
  • Step 419 The service device sends a conference party UE-A and the conference member UE-B a single-party call success message to the conference chair UE-A, and notifies the conference chairperson UE-A that the service device has successfully implemented the conference chair UE-A and the conference member.
  • UE-B single-party call The service device sends a conference party UE-A and the conference member UE-B a single-party call success message to the conference chair UE-A, and notifies the conference chairperson UE-A that the service device has successfully implemented the conference chair UE-A and the conference member.
  • UE-B single-party call.
  • the above notification message can use the NOTIFY message, and the message body is 200 OK.
  • Step 420 The conference chairperson UE-A sends a request message that the conference chair UE-A and the conference member UE-B exit the one-party call to the service device.
  • the request message may use a REFER message, where the "method" parameter of the Refer-To header field of the REFER message may be "INVITE", and the message carries the user identification information of the conference member UE-B, and the service device may carry the message according to the REFER message.
  • the user corresponding to the user identification information of the called conference member is unilaterally talking with the conference chairperson, and the "method" parameter is "INVITE" to determine that the message is the conference chairperson UE-A requesting the conference chair UE-A and the conference member UE- B Exit the unilateral call and return to the meeting.
  • Step 421 The service device sends the conference chairperson UE-A to the conference chairperson UE-A, and the conference member UE-B quits the accept message of the one-party call request.
  • Step 422 The service device sends a progress message to the conference chairperson UE-A to send the conference chair UE-A and the conference member UE-B to unilaterally call, and notify the conference chairperson UE-A that the service device has started to be the conference chair UE-A and The conference member UE-B exits the processing of the one-party call, and the progress message can use the NOTIFY message, and the message body is 100 Trying.
  • Steps 423 ⁇ 429 The service device modifies the conference chair UE-A, the conference user UE-B user media and their corresponding conference media, and has the conference chair UE-A and the conference member UE-B return to the conference.
  • Step 430 The service device sends a success message to the conference chairperson UE-A that the conference chair UE-A and the conference member UE-B exit the unilateral call and return to the conference, thereby notifying the conference chair UE-A that the service device has successfully implemented the conference.
  • the chairman UE-A and the conference member UE-B quit the one-party call and return To the meeting; the progress message can use the NOTIFY message, the message body is 200 OK.
  • the conference chair UE-A is directly sent a request message for the one-party call between the conference member UE-B and the conference chair UE-A, or the conference chairman UE-A is given a notification tone under the control of the service device.
  • the response of the conference chairperson UE-A to allow a single-party call under the prompt tone may be determined according to the control policy of the service device and the processing capability of the conference chair UE-A terminal; in the embodiment of FIG. 4, the exit and conference chair UE
  • the -A single call request can also be initiated by the conference member UE-B.
  • embodiments of the present invention also provide a service device for single-party calling in an IP multimedia subsystem conference.
  • the modules in the service device are all designed to implement the steps of the foregoing method, but the present invention is not limited to the following.
  • any service device and module that can implement the above method should be included in the scope of protection of the present invention. And in the following description, the same contents as the foregoing methods are omitted here to save space.
  • FIG. 5 is a structural block diagram of a service device according to an embodiment of the present invention.
  • the service device includes: a message receiving module, a processing module, and a single-party calling module.
  • the message receiving module is configured to receive a first request message sent by the first communications device, where the first request message is a message that is sent by the first communications device to the second communications device
  • the processing module is configured to receive, according to the first a request message, modifying a conference medium of the communication device that has joined the conference in the first communication device and the second communication device; the setting a single-party call module, configured to establish the first after the conference media modification is completed A one-way conversation between a communication device and the second communication device.
  • the service device further includes a message forwarding module, configured to forward the first request message to the second communication device;
  • the message receiving module is further configured to receive a second request message sent by the second communications device, where the processing module is further configured to modify the first message according to the received second request message
  • the service device further includes:
  • a content screening module configured to block a call between the other communication devices in the conference from the first communication device and the second communication device, and/or
  • a call between the first communication device and the second communication device is shielded from other communication devices in the conference.
  • the message receiving module is further configured to receive a request message that is sent by the first communications device and is unicast from the second communications device;
  • the processing module is further configured to modify the conference media of the first communication device and the second communication device according to the received request message for exiting the single-party call with the second communication device, and restore the A call of the first communication device and the second communication device with a previous conference.
  • the service device further includes:
  • a calling module configured to send call information to the second communications device when the first communications device and the second communications device are not in the same conference
  • the message receiving module is further configured to receive a response of the second communications device to the call information, where the processing module is further configured to establish, according to the received response, the first communications device and the second One-way communication of communication devices.
  • the message receiving module is further configured to receive a request message for exiting the one-party call sent by the first communications device;
  • the processing module is further configured to: when the first communication device exits the single-party call, release the second communication device, and modify the conference media message of the first communication device, and restore the first communication device and The call from the previous meeting.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • General Engineering & Computer Science (AREA)
  • Telephonic Communication Services (AREA)
  • Sub-Exchange Stations And Push- Button Telephones (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Abstract

本发明公开了一种IP多媒体子系统会议中单方通话的方法，服务设备接收第一通信设备发送的与第二通信设备进行单方通话的第一请求消息；第一通信设备为会议主席侧的通信设备，则服务设备修改所述第一通信设备和所述第二通信设备中已经加入会议的通信设备中的会议媒体；会议媒体的修改完成后， 服务设备建立第一通信设备与第二通信设备的单方通话，本发明还相应地公开一种IP多媒体子系统会议中单方通话的服务设备。本发明在接收到单方通话的请求后，对会议主席和/或会议成员的会议媒体进行修改，使得会议主席/会议成员可以根据自己的意愿，根据实际情况，方便的与会议成员/会议主席实现单方通话。

Description

IP多媒体子系统会议中单方通话的方法及服务设备 技术领域
本发明属于通信技术领域， 尤其涉及一种 IP 多媒体子系统 （IP Multimedia Core Network Subsystem, IMS )会议中单方通话的方法及服务 设备。 背景技术
IMS系统是由第三代合作伙伴计划 （ 3rd Generation Partnership Project, 3GPP )组织提出的一种基于网络互联协议（Internet Protocol, IP ) 的网络 架构， 构建了一个开放而灵活的业务环境， IMS 系统支持多媒体应用， 并 为用户提供丰富的多媒体业务。
会议是 IMS系统中的一种业务， 在该业务中包括主持会议的会议主席 以及参与会议的会议成员， 该业务允许多个会议成员和会议主席同时通话， 即会议成员或者会议主席说话其他的会议成员或会议主席都能听见。
目前， 在会议主席不挂机的情况下， 会议主席可以根据自己的意愿做 加入会议成员、 踢出会议成员和隔离会议成员等操作。 但目前， 在进入会 议后， 在保持会议主席与其他会议成员开会的情况下， 会议主席不能申请 和某个会议成员进行单方通话。 所谓会议主席与会议成员单方通话， 就是 在不影响其他会议成员继续开会的情况下， 让会议主席与指定的一个会议 成员单方通话。
由于在开会过程中， 会议主席在不通知其他会议成员， 以及不影响其 他会议成员继续开会的情况下， 不能和某个会议成员单方通话， 所以， 现 有技术中， 会议主席既不能单独提醒或告诫某个会议成员， 也不能单独获 得某个会议成员的支持或提醒。 发明内容
为了解决上述问题， 本发明的目的是提供一种 IP多媒体子系统会议中 单方通话的方法及服务设备， 可实现在会议过程中会议主席与会议成员进 行单方通话。
为了达到上述目的， 本发明提供一种 IP多媒体子系统会议中单方通话 的方法， 该方法包括：
服务设备接收第一通信设备发送的第一请求消息， 所述第一请求消息 为第一通信设备发送的与第二通信设备进行单方通话的请求消息；
则所述服务设备根据接收到的所述第一请求消息， 修改所述第一通信 设备和所述第二通信设备中已经加入会议的通信设备中的会议媒体；
所述会议媒体的修改完成后， 所述服务设备建立所述第一通信设备与 所述第二通信设备的单方通话。
所述第一通信设备为会议主席侧的通信设备， 所述第二通信设备为用 户成员侧的通信设备。
服务设备接收第一通信设备发送的第一请求消息后， 该方法还包括： 所述服务设备向所述第二通信设备转发所述第一请求消息；
第二通信设备向所述服务设备发送第二请求消息， 所述第二请求消息 为所述第二通信设备发送的请求与所述第一通信设备进行单方通话的请求 消息；
所述服务设备收到所述第二请求消息后， 修改所述第一通信设备和所 述第二通信设备中已经加入会议的通信设备中的会议媒体。
所述第一通信设备为用户成员侧的通信设备， 所述第二通信设备为会 议主席侧的通信设备。
所述服务设备修改所述第一通信设备和所述第二通信设备中已经加入 会议的通信设备中的会议媒体为： 所述服务设备向所述第一通信设备和所述第二通信设备屏蔽所述会议 中其他通信设备之间的通话， 和 /或
所述服务设备向所述会议中的其他通信设备屏蔽所述第一通信设备和 所述第二通信设备之间的通话。
所述服务设备接收所述第一通信设备发送的退出与所述第二通信设备 的单方通话的请求消息；
所述服务设备修改所述第一通信设备和所述第二通信设备的会议媒 体， 恢复所述第一通信设备和所述第二通信设备与之前会议的通话。
所述第一通信设备和所述第二通信设备不在同一会议中时， 该方法还 包括：
所述服务设备向所述第二通信设备发送呼叫信息；
当所述第二通信设备应答所述服务设备的呼叫后， 所述服务设备建立 所述第一通信设备和所述第二通信设备的单方通话。
该方法还包括：
所述服务设备接收所述第一通信设备发送的退出单方通话的请求消 息；
所述服务设备接受所述第一通信设备退出单方通话， 则所述服务设备 释放所述第二通信设备， 并修改所述第一通信设备的会议媒体消息， 恢复 所述第一通信设备与之前会议的通话。
一种 IP多媒体子系统会议中单方通话的服务设备， 该服务设备包括： 消息接收模块、 处理模块和设置单方通话模块； 其中，
所述消息接收模块， 用于接收第一通信设备发送的第一请求消息， 所 述第一请求消息为第一通信设备发送的与第二通信设备进行单方通话的消 息；
所述处理模块， 用于根据接收到的所述第一请求消息， 修改所述第一 通信设备和所述第二通信设备中已经加入会议的通信设备的会议媒体； 所述设置单方通话模块， 用于在所述会议媒体修改完成后， 建立所述 第一通信设备与所述第二通信设备的单方通话。
所述服务设备还包括消息转发模块， 用于向第二通信设备转发所述第 一请求消息；
所述消息接收模块， 还用于接收第二通信设备发送的第二请求消息； 所述处理模块， 还用于根据接收到的所述第二请求消息， 修改所述第 一通信设备和所述第二通信设备中已经加入会议的通信设备的会议媒体。
所述服务设备还包括：
内容屏蔽模块， 用于向所述第一通信设备和所述第二通信设备屏蔽所 述会议中其他通信设备之间的通话， 和 /或
向所述会议中其他通信设备屏蔽所述第一通信设备和所述第二通信设 备之间的通话。
所述消息接收模块， 还用于接收第一通信设备发送的退出与所述第二 通信设备的单方通话的请求消息；
所述处理模块， 还用于根据接收到的所述退出与所述第二通信设备的 单方通话的请求消息， 修改所述第一通信设备和所述第二通信设备的会议 媒体， 恢复所述第一通信设备和所述第二通信设备与之前会议的通话。
所述服务设备还包括：
呼叫模块， 用于在所述第一通信设备和所述第二通信设备不在同一会 议中时， 向所述第二通信设备发送呼叫信息；
所述消息接收模块， 还用于接收第二通信设备对所述呼叫信息的应答； 所述处理模块， 还用于根据接收到的所述应答， 建立所述第一通信设 备和所述第二通信设备的单方通话。
所述消息接收模块， 还用于接收第一通信设备发送的退出单方通话的 请求消息；
所述处理模块， 还用于在接受所述第一通信设备退出单方通话时， 释 放所述第二通信设备， 并修改所述第一通信设备的会议媒体消息， 恢复所 述第一通信设备与之前会议的通话。
本发明在接收到单方通话的请求后， 对会议主席和 /或会议成员的会议 媒体进行修改， 使得会议主席可以根据自己的意愿， 根据实际情况， 方便 的与某个会议成员实现单方通话， 也可以让会议成员根据自己的意愿， 根 据实际情况， 方便的与会议主席实现单方通话。 附图说明
图 1为本发明实施例中 IMS系统会议中单方通话的方法流程图； 图 1 A为本发明会议主席申请和其他用户单独通话的方法流程示意图； 图 1B为本发明会议成员申请和会议主席单独通话的方法流程示意图； 图 2为本发明的实施例中会议主席申请与会议成员单方通话的流程图； 图 3 为本发明的实施例中会议主席申请与会议外的某个用户单方通话 的流程图；
图 4为本发明的实施例中某个会议成员申请与会议主席单方通话的流 程图；
图 5为本发明的实施例中服务设备的结构框图。 具体实施方式
在本发明的实施例中， 服务设备首先接收作为会议主席的第一通信设 备发送的请求与第二通信设备进行单方通话的第一请求消息； 然后， 服务 设备根据接收到的第一请求消息， 修改第一通信设备和第二通信设备中已 经加入会议的通信设备的会议媒体； 最后， 会议媒体修改完成后， 服务设 备建立第一通信设备与第二通信设备的单方通话。 为了使本发明实施例的目的、 技术方案和优点更加清楚明白， 下面结 合实施例和附图， 对本发明实施例作进一步详细地说明。 在此， 本发明的 示意性实施例及说明用于解释本发明， 但并不作为对本发明的限定。
图 1为本发明 IMS系统会议中单方通话的方法流程图， 如图 1所示， 本发明 IMS系统会议中单方通话的具体步骤如下：
步骤 101 :服务设备接收第一通信设备发送的请求与第二通信设备进行 单方通话的第一请求消息。
所述第一通信设备是正在与其他通信设备参与会议的通信设备， 而第 二通信设备可以是参与该会议的通信设备， 也可以是参与其他会议的通信 设备， 还可以是非会议通信设备。
步骤 102:服务设备判断第一通信设备和第二通信设备是否在同一会议 中， 若是， 执行步骤 103; 否则， 执行步骤 107。
在接收到第一请求消息后， 服务设备可解析出第一请求消息中携带的 第一通信设备和第二通信设备的标识信息， 然后查询第一通信设备的标识 信息和第二通信设备的标识信息是否在同一会议的通信设备的标识信息列 表中， 若都在， 则可判断出第一通信设备和第二通信设备在同一会议中， 否则， 第一通信设备和第二通信设备不在同一会议中。
在本实施例中， 通信设备的标识信息可以是该通信设备的号码信息， 也可以是该通信设备的 IP地址， 并且判断第一通信设备和第二通信设备是 否在同一会议中的方式并不限于此。
步骤 103:判断第一通信设备是会议业务中的会议主席侧的通信设备还 是会议成员侧的通信设备， 若第一通信设备为会议主席侧的通信设备， 则 执行步骤 106;若第一通信设备为会议成员侧的通信设备，则执行步骤 104。
同样， 可以根据第一通信设备的标识信息来判断第一通信设备是否为 会议主席侧的通信设备， 若第一通信设备为主席侧的通信设备时， 该服务 设备可根据步骤 101 中接收到的第一请求消息修改第一通信设备和第二通 信设备中的会议媒体， 此时第一通信设备和第二通信设备已加入到同一会 议中。
步骤 104:服务设备向第二通信设备转发第一通信设备发送的请求与第 二通信设备进行单方通话的第一请求消息， 然后执行步骤 105。
步骤 105;第二通信设备向服务设备发送请求与第一通信设备进行单方 通话的第二请求消息， 然后执行步骤 106。
步骤 106: 服务设备修改第一通信设备和第二通信设备的会议媒体， 并 建立第一通信设备和第二通信设备的单方通话， 流程结束。
步骤 107:服务设备修改第一通信设备的会议媒体，然后执行步骤 108。 此时， 该第一通信设备可以是某会议中的会议主席侧的通信设备， 或 者也可以是会议成员侧的通信设备。 在实施例二中， 仅介绍该第一通信设 备为会议主席侧的通信设备的情形。
步骤 108: 当第二通信设备应答服务设备的呼叫后，服务设备建立第一 通信设备和第二通信设备的单方通话。
在执行步骤 108之前， 该服务设备根据第一请求消息中携带的第二通 信设备的标识信息， 向该第二通信设备发出呼叫请求。
根据上述方案， 会议主席申请和其他用户单独通话的方法流程如图 1A 所示， 会议成员申请和会议主席单独通话的方法流程如图 1B所示。
由上述技术方案可知， 通过在接收到单方通话的请求后， 对会议主席 和 /或会议成员的会议媒体进行修改， 使得会议主席可以根据自己的意愿， 根据实际情况， 方便的与某个会议成员实现单方通话， 也可以让会议成员 根据自己的意愿， 根据实际情况， 方便的与会议主席实现单方通话。
在本发明中， 描述了 IMS系统会议中会议主席与会议成员或者非会议 成员的单方通话的过程， 下面将会议主席与会议成员或者非会议成员之间 的单方通话划分为三种情形：
情形一： 会议主席申请和某个会议成员单方通话， 并且在通话结束后 会议主席和该会议成员回到会议中；
情形二： 会议主席申请和会议外的某个用户 （非会议成员）单方通话， 并且在通话结束后会议主席可回到会议中， 同时释放该用户；
情形三： 某个会议成员申请和会议主席单方通话， 通话结束后会议主 席和该会议成员可回到会议中；
针对上述三种情形， 可分别以三个具体的实施例进行详细介绍。
实施例一
在下面的描述中， 可假设在该 IMS系统会议中包括： 会议主席 UE-A、 会议成员 UE-B、 会议成员 UE-C和会议成员 UE-D, 而且 UE-A、 UE-B、 UE-C、 UE-D 已经进入会议， 进入会议的流程可通过现有技术实现。 当然 在本实施例中， 会议主席向服务设备申请与某个会议成员进行单方通 话， 并且在单方通话结束后， 会议主席和该会议成员可回到会议中， 继续 参与会议。
图 2为本发明的实施例中会议主席申请与会议成员单方通话的流程图 , 如图 2所示， 本发明的实施例中会议主席申请与会议成员单方通话的具体 步骤如下：
步骤 201 : 会议主席 UE-A和会议成员 UE-B、 UE-C, UE-D加入到会 议中。
在本步骤中，会议主席 UE-A可釆用现有技术将会议成员 UE-B、UE-C、 UE-D加入到会议中。
步骤 202: 会议主席 UE-A向服务设备发送会议主席 UE-A与会议成员 UE-B的进行单方通话的请求消息。 上述进行单方通话的请求消息可以是 REFER消息， 其中 REFER消息 的 Refer-To头字段的 "method" 参数可设置为 "INVITE" , 并且在 REFER 消息中携带有会议主席 UE-A需要与之单方通话的会议成员 UE-B的用户标 识信息， 该用户标识信息可以是该会议成员的电话号码信息， 也可以是该 会议成员的 IP地址， 当然也并不限于此。
服务设备可根据 REFER消息中携带的被叫会议成员的用户标识信息所 对应的用户已经在会议中， 并且 "method" 参数为 "INVITE" 来确定该请 求消息为会议主席 UE-A请求与会议成员 UE-B进行单方通话的请求消息。
在本实施例中， 单方通话申请和退出都可釆用 RFC3515 中定义的 REFER消息， 这样只需会议主席和与会议主席进行单方通话的会议成员支 持 REFER和 NOTIFY消息处理外， 其他的会议成员可以不支持 REFER和 NOTIFY消息处理， 其他会议成员也可以不是会话初始化协议（ SIP )用户。
当然，会议主席 UE-A请求与会议成员单方通话的具体消息不局限于上 述的 REFER消息 ,以及消息的具体内容也不限于用 REFER消息的 "method" 参数， 只要用合适的消息能够让服务设备知道会议主席或意图， 让会议主 席知道服务设备对请求的处理情况即可， 比如可以对 "method" 参数进行 扩展， 以便服务设备和会议主席能根据更明确的指示做出请求单方通话或 退出单方通话等判断。
步骤 203:服务设备给会议主席 UE-A发送接受单方通话请求的接受消 息。
步骤 204: 服务设备给会议主席 UE-A发送会议主席 UE-A与会议成员 UE-B的单方通话进展通知。
也就是， 服务设备通知会议主席 UE-A, 该服务设备已经开始做会议主 席 UE-A与会议成员 UE-B单方通话的处理，上述进展通知可以是 NOTIFY 消息， 消息体为 100 Trying。 步骤 205: 服务设备向会议资源发送修改会议主席 UE-A和会议成员 UE-B的会议媒体请求。
步骤 206: 会议资源向服务设备返回修改会议主席 UE-A和会议成员 UE-B的会议媒体响应。
通过执行步骤 205 ~ 206, 会议资源可根据单方通话的请求消息的指示 和服务设备的处理逻辑，修改会议主席 UE-A和会议成员 UE-B的用户媒体 以及对应的会议媒体， 不让 UE-A和 UE-B向会议发信息， 也就是该服务设 备向其他会议成员屏蔽 UE-A和 UE-B之间的通话内容， 和 /或不让会议不 向会议主席 UE-A和会议成员 UE-B发信息，也就是向会议主席 UE-A和会 议成员 UE-B屏蔽其他会议成员之间的通话内容。
步骤 207 - 213 : 服务设备修改会议主席 UE-A和会议成员 UE-B的会 议媒体， 建立会议主席 UE- A和会议成员 UE-B之间单方通话。
步骤 214: 服务设备向会议主席 UE-A发送实现会议主席 UE-A与会议 成员 UE-B单方通话的成功消息。
服务设备通知会议主席 UE-A , 该服务设备已经成功实现会议主席 UE-A与会议成员 UE-B的单方通话， 该通知消息可以是 NOTIFY消息， 消 息体为 200 OK。
步骤 215: 会议主席 UE-A向服务设备发送会议主席 UE-A与会议成员 UE-B退出单方通话的请求消息。
当会议主席 UE-A与会议成员 UE-B之间的单方通话结束时，会议主席 UE-A向服务设备发送退出单方通话的请求消息，该请求消息可以是 REFER 消息， 其中消息的 Refer-To 头字段的 "method" 参数可以为 "INVITE" , 消息中携带会议成员 UE-B的用户标识信息，同样该用户标识信息可以是会 议成员 UE-B的电话号码信息， 或者是会议成员 UE-B的 IP地址， 服务设 备可以根据 REFER消息中携带的被叫会议成员的标识信息对应出正与会议 主席 UE-A 单方通话的会议成员 UE-B , 并且可根据 "method" 参数为 "INVITE" 来确定该消息为会议主席 UE-A请求会议主席 UE-A与会议成 员 UE-B退出单方通话。
步骤 216: 服务设备向会议主席 UE-A发送会议主席 UE-A与会议成员 UE-B退出单方通话请求的接受消息。
当服务设备接收到退出单方通话的请求消息后， 服务设备向会议主席 UE-A发送退出单方通话请求的接受消息， 该接受消息可以设置为 202。
步骤 217: 服务设备向会议主席 UE-A发会议主席 UE-A与会议成员 UE-B退出单方通话进展消息。
也就是该服务设备通知会议主席 UE-A,服务设备已经开始做会议主席 UE-A与会议成员 UE-B退出单方通话的处理， 该进展消息可以使 NOTIFY 消息， 消息体为 100 Trying。
步骤 218 - 224: 服务设备修改会议主席 UE-A、会议成员 UE-B的用户 媒体以及对应的会议媒体，恢复会议主席 UE-A和会议成员 UE-B与之前会 议的通话， 让会议主席 UE-A和会议成员 UE-B回到会议中， 使得会议主席 UE-A与会议成员 UE-B、 会议成员 UE-C、 和会议成员 UE-D的正常交流。
步骤 225: 服务设备向会议主席 UE-A发送实现会议主席 UE-A与会议 成员 UE-B退出单方通话并回到会议的成功消息。
在本步骤中， 该服务设备可通知会议主席 UE-A, 该服务设备已经成功 实现会议主席 UE-A与会议成员 UE-B退出单方通话并回到会议中，该通知 消息可以是 NOTIFY消息， 消息体为 200 OK。
通过步骤 201~224可实现会议主席 UE-A和某个会议成员单方通话， 并且在通话结束后该会议主席 UE-A和该会议成员再回到会议中。 实施例二
在下面的描述中， 可假设在该 IMS系统会议中包括： 会议主席 UE-A、 会议成员 UE-B和会议成员 UE-C, 并且 UE-A、 UE-B、 UE-C已进入会议， 进入会议的流程可通过现有技术实现。 当然其他想参加会议的会议成员可 通过现有技术加入到该会议中。
在本实施例中， 会议主席申请和会议外的某个非会议成员进行单方通 话， 在通话结束后会议主席再回到会议中， 并释放该非会议成员。
图 3 为本发明的实施例中会议主席申请与会议外的某个用户单方通话 的流程图， 如图 3 所示， 实施例二中会议主席申请与会议外的某个用户单 方通话的具体步骤如下：
步骤 301 : 会议主席 UE-A将会议成员 UE-B、 UE-C加入到会议中。 在本步骤中，会议主席 UE-A可釆用现有技术将会议成员 UE-B和 UE-C 加入到会议中。
步骤 302: 会议主席 UE-A向服务设备发送会议主席 UE-A与非会议成 员 UE-D进行单方通话的请求消息。
上述进行单方通话的请求消息可以是 REFER消息， 其中 REFER消息 的 Refer-To头字段的 "method" 参数可以为 "INVITE" , 并且在 REFER消 息中携带会议主席 UE-A需要与之单方通话的用户 UE-D (非会议成员）的 标识信息， 该标识信息可以是该用户的电话号码信息， 也可以是该用户的 IP地址， 当然也并不限于此。
服务设备可根据 REFER消息中携带的被叫用户的标识信息所对应的用 户 UE-D不在会议中，也没有 "replace"字段，并且" method"参数为 "INVITE" 来确定该消息为会议主席 UE-A请求与非会议成员 UE-D进行单方通话的请 求消息。
在本步骤中，会议主席 UE-A请求与非会议成员 UE-D的具体消息不局 限于用 REFER 消息， 以及消息的具体内容也不限于用 REFER 消息的 "method" 参数， 只要用合适的消息能够让服务设备知道会议主席或会议 成员的意图， 让会议主席或会议成员知道服务设备对请求的处理情况即可， 比如可以对 "method" 参数进行扩展， 以便服务设备和会议主席能根据更 明确的指示做出请求单方通话的判断。
步骤 303: 服务设备向会议主席 UE-A发送会议主席 UE-A与非会议成 员 UE-D单方通话请求的接受消息。
步骤 304: 服务设备向会议主席 UE-A发送会议主席 UE-A与非会议成 员 UE-D单方通话的进展消息。
服务设备通知会议主席 UE-A, 该服务设备已经开始做会议主席 UE-A 与非会议成员 UE-D 单方通话的处理， 该单方通话的进展消息可以是 NOTIFY消息， 消息体为 100 Trying。
步骤 305 ~ 306: 服务设备根据会议主席 UE-A与非会议成员 UE-D单 方通话请求消息的指示和服务设备的处理逻辑，修改会议主席 UE-A的用户 媒体以及对应的会议媒体，不让会议主席 UE-A向会议发信息（向其他会议 成员屏蔽会议主席 UE-A和非会议成员 UE-D之间的通话内容）， 和 /或者不 让会议向会议主席 UE-A发信息（向会议主席 UE-A屏蔽其他会议成员之间 的通话内容）。
步骤 307 ~ 315: 服务设备建立会议主席 UE-A与非会议成员 UE-D之 间的单方通话。
步骤 316: 服务设备向会议主席 UE-A发送会议主席 UE-A与非会议成 员 UE-D单方通话成功的通知消息。
也就是服务设备通知会议主席 UE-A,该服务设备已经成功实现会议主 席 UE-A与非会议成员 UE-D单方通话， 该通知消息可以是 NOTIFY消息， 消息体为 200 OK。
步骤 317: 会议主席 UE-A向服务设备请求退出与非会议成员 UE-D单 方通话。 并且会议主席 UE-A回到会议的请求消息， 该请求消息可以釆用 REFER消 息， 其中消息的 Refer-To头字段的 "method" 参数可以为 "BYE" , REFER 消息中携带非会议成员 UE-D的用户标识信息，该用户标识信息可以是非会 议成员 UE-D的电话号码信息， 也可以是非会议成员 UE-D的 IP地址， 当 然也并不限于此。
服务设备可以根据 REFER消息中携带的被叫用户的用户标识信息所对 应的用户正与会议主席 UE-A进行单方通话，并且 "method"参数为 "BYE" 来确定该消息为会议主席 UE-A请求释放非会议成员 UE-D , 并让会议主席 UE-A回到会议中。
步骤 318:服务设备向会议主席 UE-A发送退出单方通话请求的接受消 息。
在本步骤中， 服务设备向会议主席 UE-A返回释放非会议成员 UE-D , 以及会议主席 UE-A回到会议的响应消息。
步骤 319; 服务设备向会议主席发送退出单方通话请求进展通知。
服务设备向会议主席 UE-A发送释放非会议成员 UE-D , 以及会议主席 UE-A回到会议的进展消息， 并通知 UE-A该服务设备已经开始做释放非会 议成员 UE-D ,会议主席 UE-A回到会议的处理，该进展通知可以是 NOTIFY 消息， 消息体为 100 Trying。
步骤 320 ~ 325:服务设备释放非会议成员 UE-D,并修改会议主席 UE-A 的用户媒体以及之对应会议媒体，建立会议主席 UE- A与会议的通话，也就 是让会议主席 UE-A回到会议中， 实现与其他会议成员的正常交流。
步骤 326:服务设备给会议主席 UE-A发送实现释放非会议成员 UE-D, 会议主席 UE-A回到会议的成功消息，并通知会议主席 UE-A该服务设备已 经成功实现释放非会议成员 UE-D, 并且会议主席 UE-A回到会议中， 该成 功消息可以是 NOTIFY消息 , 消息体为 200 OK。 话流程在实际实现中根据不同的终端和服务设备的具体控制策略有多种实 现方式； 且通过步骤 301~326可实现会议主席申请和会议外的某个用户单 方通话， 通话结束后会议主席回到会议中， 并释放该用户。 实施例三
在下面的描述中， 可假设在该 IMS系统会议中包括： 会议主席 UE-A、 会议成员 UE-B、 会议成员 UE-C和会议成员 UE-D, 并且 UE-A、 UE-B、 UE-C和 UE-D已进入会议， 进入会议的流程可通过现有技术实现。 当然其 他想参加会议的会议成员可通过现有技术加入到该会议中。
在本实施例中， 某个会议成员申请和会议主席进行单方通话， 并在会 议结束后会议主席和该会议成员可回到会议中。
图 4为本发明的实施例中某个会议成员申请与会议主席单方通话的流 程图， 如图 4 所示， 实施例三中某个会议成员申请与会议主席单方通话的 具体步骤如下：
步骤 401 : 会议主席 UE-A和会议成员 UE-B、 UE-C, UE-D加入到会 议中。
在本步骤中，会议主席 UE-A可釆用现有技术将会议成员 UE-B、 UE-C 和 UE-D加入到会议中。
步骤 402: 会议成员 UE-B向服务设备发送会议成员 UE-B与会议主席 UE-A进行单方通话的请求消息。
上述进行单方通话的请求消息可以是 REFER消息， 其中 REFER消息 的 Refer-To 头字段的 "method" 参数可以为 "INVITE" , 消息中携带会议 主席的用户标识信息， 该用户标识信息可以是该会议主席的电话号码信息 , 也可以该会议成员的 IP地址， 当然也并不限于此。 服务设备可以根据 REFER消息中携带的被叫的用户标识信息为会议主 席 UE-A所对应的用户标识信息， 并且 "method" 参数为 "INVITE" 来确 定该消息为 UE-B请求与会议主席 UE-A进行单方通话的请求消息；
步骤 403: 服务设备向会议主席 UE-A转发会议成员 UE-B发送的单方 通话的请求消息。
也就是在本步骤中，服务设备根据本地策略判断，会议成员 UE-B有权 与会议主席单方通话， 向会议主席 UE-A转发会议成员 UE-B与会议主席 UE-A进行单方通话的请求消息， 该请求消息可以釆用 REFER消息。
步骤 404: 服务设备给会议成员 UE-B发会议成员与会议主席 UE-A单 方通话请求的接受消息。
步骤 405: 会议主席 UE-A向服务设备发送请求与会议成员 UE-B单方 通话的请求消息。
也就是，在收到步骤 403中的请求消息后，会议主席 UE-A确认出可以 和会议成员 UE-B进行单方通话， 会议主席 UE-A向服务设备发会议主席 UE-A 与会议成员 UE-B 进行单方通话的请求消息， 该请求消息可以是 REFER消息， 其中 REFER消息的 Refer-To头字段的 "method" 参数可以 为 "INVITE" , REFER消息中携带会议主席 UE-A需要与之单方通话的会 议成员 UE-B的用户标识信息，该用户标识信息可以是该会议成员的电话号 码信息， 也可以是该会议成员的 IP地址， 当然也并不限于此。
在本步骤中，会议成员 UE-B请求与会议主席 UE-A单方通话的具体消 息不局限于 REFER消息， 以及消息的具体内容也不限于用 REFER消息的 "method" 参数， 只要用合适的消息能够让服务设备知道会议主席或会议 成员的意图， 让会议主席或会议成员知道服务设备对请求的处理情况即可， 比如可以对 "method" 参数进行扩展， 以便服务设备和会议主席能根据更 明确的指示做出请求单方通话或退出单方通话等判断。 服务设备可以根据 REFER消息中携带的被叫会议成员的用户标识信息 对应的用户已经在会议中， 并且 "method" 参数为 "INVITE" 来确定该消 息为会议主席 UE-A请求与会议成员 UE-B进行单方通话。
步骤 406: 服务设备向会议主席 UE-A发会议主席 UE-A与会议成员 UE-B进行单方通话的请求消息的接受消息。
步骤 407: 服务设备向会议成员 UE-B发会议成员 UE-B与会议主席 UE-A进行单方通话的进展消息， 通过该进展消息通知会议成员 UE-B , 该 服务设备已经开始做会议成员 UE-B与会议主席 UE-A进行单方通话的处 理， 该进展消息可釆用 NOTIFY消息， 消息体为 100 Trying。
步骤 408: 服务设备向会议主席 UE-A发会议主席 UE-A与会议成员 UE-B进行单方通话的进展消息， 同该进展消息通知会议成员 UE-A, 该服 务设备已经开始做会议主席 UE-A与会议成员 UE-B进行单方通话的处理， 同样该进展消息可釆用 NOTIFY消息， 消息体为 100 Trying。
步骤 409 - 410: 根据会议主席 UE-A与会议成员 UE-B进行单方通话 的请求消息的指示和服务设备的处理逻辑，修改会议主席 UE-A和会议成员 UE-B的用户媒体以及与他们对应的会议媒体， 不让会议主席 UE-A、 会议 成员 UE-B向会议发信息（向其他会议成员屏蔽会议主席 UE-A和会议成员 UE-B之间的通话内容），和 /或不让会议不向会议主席 UE-A、会议成员 UE-B 发信息（向会议主席 UE-A和会议成员 UE-B屏蔽其他会议成员之间的通话 内容）。
步骤 411 417: 服务设备修改会议主席 UE-A、 会议成员 UE-B的会议 媒体， 使会议主席 UE-A和会议成员 UE-B之间实现单方通话。
步骤 418: 服务设备给会议成员 UE-B发送实现会议成员 UE-B与会议 主席 UE-A单方通话成功消息， 通知会议成员 UE-B, 该服务设备已经成功 实现会议成员 UE-B与会议主席 UE-A单方通话。 上述通知消息可釆用 NOTIFY消息 , 消息体为 200 OK。
步骤 419: 服务设备给会议主席 UE-A发实现会议主席 UE-A与会议成 员 UE-B单方通话成功消息， 通知会议主席 UE-A, 该服务设备已经成功实 现会议主席 UE-A与会议成员 UE-B单方通话。
同样上述通知消息可釆用 NOTIFY消息， 消息体为 200 OK。
步骤 420: 会议主席 UE-A向服务设备发会议主席 UE-A与会议成员 UE-B退出单方通话的请求消息。
上述请求消息可以釆用 REFER消息， 其中 REFER消息的 Refer-To头 字段的 "method" 参数可以为 "INVITE" , 消息中携带会议成员 UE-B的用 户标识信息，服务设备可以根据 REFER消息中携带的被叫会议成员的用户 标识信息所对应的用户正与会议主席单方通话， 并且 "method" 参数为 "INVITE" 来确定该消息为会议主席 UE-A请求会议主席 UE-A与会议成 员 UE-B退出单方通话并回到会议中。
步骤 421 : 服务设备向会议主席 UE-A发会议主席 UE-A与会议成员 UE-B退出单方通话请求的接受消息。
步骤 422: 服务设备给会议主席 UE-A发会议主席 UE-A与会议成员 UE-B退出单方通话的进展消息， 并通知会议主席 UE-A, 该服务设备已经 开始做会议主席 UE-A与会议成员 UE-B退出单方通话的处理，该进展消息 可釆用 NOTIFY消息， 消息体为 100 Trying。
步骤 423 ~ 429: 服务设备修改会议主席 UE-A、会议成员 UE-B的用户 媒体以及他们所对应的会议媒体，并让会议主席 UE-A和会议成员 UE-B回 到会议中。
步骤 430: 服务设备向会议主席 UE-A发送实现会议主席 UE-A与会议 成员 UE-B退出单方通话并回到会议的成功消息，以此通知会议主席 UE-A, 服务设备已经成功实现会议主席 UE-A与会议成员 UE-B退出单方通话并回 到会议中； 该进展消息可以釆用 NOTIFY消息， 消息体为 200 OK。
在本实施例中，直接给会议主席 UE-A发送会议成员 UE-B与会议主席 UE-A 进行单方通话的请求消息， 还是在服务设备的控制下给会议主席 UE-A放收号提示音以便会议主席 UE-A在提示音下做是否允许单方通话的 响应，可以根据服务设备的控制策略以及会议主席 UE-A终端的处理能力来 确定；在图 4实施例中，退出与会议主席 UE-A单方通话请求也可以由会议 成员 UE-B发起。
为了实现上述的方法实施例， 本发明的其他实施例还提供了一种 IP多 媒体子系统会议中单方通话的服务设备。 另需首先说明的是， 由于下述的 实施例是为实现前述的方法实施例， 故该服务设备中的模块都是为了实现 前述方法的各步骤而设， 但本发明并不限于下述的实施例， 任何可实现上 述方法的服务设备和模块都应包含于本发明的保护范围。 并且在下面的描 述中， 与前述方法相同的内容在此省略， 以节约篇幅。
参见图 5 , 为本发明的实施例中服务设备的结构框图， 由图中可知， 该 服务设备包括： 消息接收模块、 处理模块和设置单方通话模块； 其中， 所述消息接收模块， 用于接收第一通信设备发送的第一请求消息， 所述 第一请求消息为第一通信设备发送的与第二通信设备进行单方通话的消息； 所述处理模块， 用于根据接收到的所述第一请求消息， 修改所述第一 通信设备和所述第二通信设备中已经加入会议的通信设备的会议媒体； 所述设置单方通话模块， 用于在所述会议媒体修改完成后， 建立所述 第一通信设备与所述第二通信设备的单方通话。
所述服务设备还包括消息转发模块， 用于向第二通信设备转发所述第 一请求消息；
所述消息接收模块， 还用于接收第二通信设备发送的第二请求消息； 所述处理模块， 还用于根据接收到的所述第二请求消息， 修改所述第 一通信设备和所述第二通信设备中已经加入会议的通信设备的会议媒体。 所述服务设备还包括：
内容屏蔽模块， 用于向所述第一通信设备和所述第二通信设备屏蔽所 述会议中其他通信设备之间的通话， 和 /或
向所述会议中其他通信设备屏蔽所述第一通信设备和所述第二通信设 备之间的通话。
所述消息接收模块， 还用于接收第一通信设备发送的退出与所述第二 通信设备的单方通话的请求消息；
所述处理模块， 还用于根据接收到的所述退出与所述第二通信设备的 单方通话的请求消息， 修改所述第一通信设备和所述第二通信设备的会议 媒体， 恢复所述第一通信设备和所述第二通信设备与之前会议的通话。
所述服务设备还包括：
呼叫模块， 用于在所述第一通信设备和所述第二通信设备不在同一会 议中时， 向所述第二通信设备发送呼叫信息；
所述消息接收模块， 还用于接收第二通信设备对所述呼叫信息的应答； 所述处理模块， 还用于根据接收到的所述应答， 建立所述第一通信设 备和所述第二通信设备的单方通话。
所述消息接收模块， 还用于接收第一通信设备发送的退出单方通话的 请求消息；
所述处理模块， 还用于在接受所述第一通信设备退出单方通话时， 释 放所述第二通信设备， 并修改所述第一通信设备的会议媒体消息， 恢复所 述第一通信设备与之前会议的通话。
以上所述仅是本发明的优选实施方式， 应当指出， 对于本技术领域的 普通技术人员来说， 在不脱离本发明原理的前提下， 还可以作出若干改进 和润饰， 这些改进和润饰也应视为本发明的保护范围。

Claims

权利要求书
1. 一种 IP多媒体子系统会议中单方通话的方法， 其特征在于， 该方法 包括：
服务设备接收第一通信设备发送的第一请求消息， 所述第一请求消息 为第一通信设备发送的与第二通信设备进行单方通话的请求消息；
则所述服务设备根据接收到的所述第一请求消息， 修改所述第一通信 设备和所述第二通信设备中已经加入会议的通信设备中的会议媒体；
所述会议媒体的修改完成后， 所述服务设备建立所述第一通信设备与 所述第二通信设备的单方通话。
2. 根据权利要求 1所述的方法， 其特征在于， 所述第一通信设备为会 议主席侧的通信设备， 所述第二通信设备为用户成员侧的通信设备。
3. 根据权利要求 1所述的方法， 其特征在于， 服务设备接收第一通信 设备发送的第一请求消息后， 该方法还包括：
所述服务设备向所述第二通信设备转发所述第一请求消息；
第二通信设备向所述服务设备发送第二请求消息， 所述第二请求消息 为所述第二通信设备发送的请求与所述第一通信设备进行单方通话的请求 消息；
所述服务设备收到所述第二请求消息后， 修改所述第一通信设备和所 述第二通信设备中已经加入会议的通信设备中的会议媒体。
4. 根据权利要求 3所述的方法， 其特征在于， 所述第一通信设备为用 户成员侧的通信设备， 所述第二通信设备为会议主席侧的通信设备。
5. 根据权利要求至 4任一项所述的方法， 其特征在于， 所述服务设备 修改所述第一通信设备和所述第二通信设备中已经加入会议的通信设备中 的会议媒体为：
所述服务设备向所述第一通信设备和所述第二通信设备屏蔽所述会议 中其他通信设备之间的通话， 和 /或
所述服务设备向所述会议中的其他通信设备屏蔽所述第一通信设备和 所述第二通信设备之间的通话。
6. 根据权利要求 1所述的方法， 其特征在于， 该方法还包括： 所述服务设备接收所述第一通信设备发送的退出与所述第二通信设备 的单方通话的请求消息；
所述服务设备修改所述第一通信设备和所述第二通信设备的会议媒 体， 恢复所述第一通信设备和所述第二通信设备与之前会议的通话。
7. 根据权利要求 1所述的方法， 其特征在于， 所述第一通信设备和所 述第二通信设备不在同一会议中时， 该方法还包括：
所述服务设备向所述第二通信设备发送呼叫信息；
当所述第二通信设备应答所述服务设备的呼叫后， 所述服务设备建立 所述第一通信设备和所述第二通信设备的单方通话。
8. 根据权利要求 7所述的方法， 其特征在于， 该方法还包括： 所述服务设备接收所述第一通信设备发送的退出单方通话的请求消 息；
所述服务设备接受所述第一通信设备退出单方通话， 则所述服务设备 释放所述第二通信设备， 并修改所述第一通信设备的会议媒体消息， 恢复 所述第一通信设备与之前会议的通话。
9. 一种 IP多媒体子系统会议中单方通话的服务设备， 其特征在于， 该 服务设备包括： 消息接收模块、 处理模块和设置单方通话模块； 其中， 所述消息接收模块， 用于接收第一通信设备发送的第一请求消息， 所 述第一请求消息为第一通信设备发送的与第二通信设备进行单方通话的消 息；
所述处理模块， 用于根据接收到的所述第一请求消息， 修改所述第一 通信设备和所述第二通信设备中已经加入会议的通信设备的会议媒体； 所述设置单方通话模块， 用于在所述会议媒体修改完成后， 建立所述 第一通信设备与所述第二通信设备的单方通话。
10、 根据权利要求 9所述的服务设备， 其特征在于， 所述服务设备还 包括消息转发模块， 用于向第二通信设备转发所述第一请求消息；
所述消息接收模块， 还用于接收第二通信设备发送的第二请求消息； 所述处理模块， 还用于根据接收到的所述第二请求消息， 修改所述第 一通信设备和所述第二通信设备中已经加入会议的通信设备的会议媒体。
11. 根据权利要求 9所述的服务设备， 其特征在于， 所述服务设备还包 括：
内容屏蔽模块， 用于向所述第一通信设备和所述第二通信设备屏蔽所 述会议中其他通信设备之间的通话， 和 /或
向所述会议中其他通信设备屏蔽所述第一通信设备和所述第二通信设 备之间的通话。
12、 根据权利要求 9所述的服务设备， 其特征在于，
所述消息接收模块， 还用于接收第一通信设备发送的退出与所述第二 通信设备的单方通话的请求消息；
所述处理模块， 还用于根据接收到的所述退出与所述第二通信设备的 单方通话的请求消息， 修改所述第一通信设备和所述第二通信设备的会议 媒体， 恢复所述第一通信设备和所述第二通信设备与之前会议的通话。
13. 根据权利要求 9所述的服务设备， 其特征在于， 所述服务设备还包 括：
呼叫模块， 用于在所述第一通信设备和所述第二通信设备不在同一会 议中时， 向所述第二通信设备发送呼叫信息；
所述消息接收模块， 还用于接收第二通信设备对所述呼叫信息的应答； 所述处理模块， 还用于根据接收到的所述应答， 建立所述第一通信设 备和所述第二通信设备的单方通话。
14、 根据权利要求 9所述的服务设备， 其特征在于，
所述消息接收模块， 还用于接收第一通信设备发送的退出单方通话的 请求消息；
所述处理模块， 还用于在接受所述第一通信设备退出单方通话时， 释 放所述第二通信设备， 并修改所述第一通信设备的会议媒体消息， 恢复所 述第一通信设备与之前会议的通话。
PCT/CN2010/075626 2009-08-12 2010-08-02 Ip多媒体子系统会议中单方通话的方法及服务设备 WO2011017999A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
AU2010282015A AU2010282015A1 (en) 2009-08-12 2010-08-02 Method and service device for private call of conference in IP multimedia subsystem
IN1512DEN2012 IN2012DN01512A (zh) 2009-08-12 2010-08-02
MX2012001794A MX2012001794A (es) 2009-08-12 2010-08-02 Metodo y dispositivo de servicio para realizar una llamada privada durante una conferencia en un subsistema multimedia de protocolo de internet.
BR112012003051-5A BR112012003051B1 (pt) 2009-08-12 2010-08-02 Metodo para realizaqao de uma chamada privada durante uma conferencia em um subsistema de multimidia de ip e dispositivo de serviqo para realizaqao de uma chamada privada durante uma conferencia em um subsistema de multimidia de ip
EP10807944.3A EP2466842B1 (en) 2009-08-12 2010-08-02 Method and service device for private call of conference in ip multimedia subsystem
US13/258,372 US20120134302A1 (en) 2009-08-12 2010-08-02 Method and Service Device for Realizing a Private Call During A Conference in an IP Multimedia Subsystem
RU2012101842/08A RU2515703C2 (ru) 2009-08-12 2010-08-02 Способ и сервисное устройство для осуществления персонального разговора во время конференции в сети ims

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2009100912196A CN101997694A (zh) 2009-08-12 2009-08-12 Ip多媒体子系统会议中单方通话的方法及服务设备
CN200910091219.6 2009-08-12

Publications (1)

Publication Number Publication Date
WO2011017999A1 true WO2011017999A1 (zh) 2011-02-17

Family

ID=43585938

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/075626 WO2011017999A1 (zh) 2009-08-12 2010-08-02 Ip多媒体子系统会议中单方通话的方法及服务设备

Country Status (9)

Country Link
US (1) US20120134302A1 (zh)
EP (1) EP2466842B1 (zh)
CN (1) CN101997694A (zh)
AU (1) AU2010282015A1 (zh)
BR (1) BR112012003051B1 (zh)
IN (1) IN2012DN01512A (zh)
MX (1) MX2012001794A (zh)
RU (1) RU2515703C2 (zh)
WO (1) WO2011017999A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102223243A (zh) * 2011-06-20 2011-10-19 中兴通讯股份有限公司 向音频会议中的用户单独播放音频的方法和装置
US20130282803A1 (en) * 2012-04-18 2013-10-24 Microsoft Corporation Engaging session elements in conference sessions
CN105897888B (zh) * 2016-04-08 2020-09-22 腾讯科技（深圳）有限公司 一种客户端连接方法及系统
CN111225177B (zh) * 2020-02-20 2022-12-23 视联动力信息技术股份有限公司 视频会议的处理方法、装置、电子设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006034067A2 (en) * 2004-09-17 2006-03-30 Nextel Communications, Inc. System and method for conducting a dispatch multi-party call and sidebar session
CN101110686A (zh) * 2006-07-18 2008-01-23 中兴通讯股份有限公司 一种利用媒体服务器实现子会议的方法
CN101471806A (zh) * 2007-12-27 2009-07-01 华为技术有限公司 子会议实现方法、私密会议实现方法、装置和终端设备

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7058168B1 (en) * 2000-12-29 2006-06-06 Cisco Technology, Inc. Method and system for participant control of privacy during multiparty communication sessions
US8467502B2 (en) * 2001-02-27 2013-06-18 Verizon Data Services Llc Interactive assistant for managing telephone communications
US20030035527A1 (en) * 2001-08-14 2003-02-20 Charles Baker Conference call tunneling method and apparatus
US9451422B2 (en) * 2003-03-17 2016-09-20 Nokia Technologies Oy Method, system and network device for routing a message to a temporarily unavailable network user
US7480259B2 (en) * 2003-10-09 2009-01-20 Hewlett-Packard Development Company, L.P. System and method for establishing a parallel conversation thread during a remote collaboration
EP1749387B1 (en) * 2004-05-28 2012-08-29 TELEFONAKTIEBOLAGET LM ERICSSON (publ) Communications method and apparatus, database information retrieval method and apparatus
RU2344562C2 (ru) * 2004-06-29 2009-01-20 Нокиа Сименс Нетворкс Гмбх Унд Ко. Кг Способ выбора сервера из набора серверов
US7679640B2 (en) * 2005-01-27 2010-03-16 Polycom, Inc. Method and system for conducting a sub-videoconference from a main videoconference
US7634074B2 (en) * 2005-09-30 2009-12-15 Motorola, Inc. Method and apparatus for making sidebar calls
CN101316178B (zh) * 2007-05-29 2011-06-08 华为技术有限公司 会话建立方法和会话系统
CN101374067A (zh) * 2007-08-21 2009-02-25 华为技术有限公司 实现子会议的方法、网络系统及多媒体处理器
JP5167726B2 (ja) * 2007-08-23 2013-03-21 ソニー株式会社 コンテンツ課金システム、コンテンツ取得装置、コンテンツ取得方法およびそのプログラム、並びにコンテンツ提供装置、コンテンツ提供方法およびそのプログラム

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006034067A2 (en) * 2004-09-17 2006-03-30 Nextel Communications, Inc. System and method for conducting a dispatch multi-party call and sidebar session
CN101110686A (zh) * 2006-07-18 2008-01-23 中兴通讯股份有限公司 一种利用媒体服务器实现子会议的方法
CN101471806A (zh) * 2007-12-27 2009-07-01 华为技术有限公司 子会议实现方法、私密会议实现方法、装置和终端设备

Also Published As

Publication number Publication date
EP2466842A4 (en) 2016-10-26
BR112012003051A8 (pt) 2020-01-28
RU2515703C2 (ru) 2014-05-20
EP2466842B1 (en) 2018-10-10
IN2012DN01512A (zh) 2015-06-05
US20120134302A1 (en) 2012-05-31
AU2010282015A1 (en) 2012-03-22
EP2466842A1 (en) 2012-06-20
RU2012101842A (ru) 2013-09-20
BR112012003051B1 (pt) 2021-07-13
BR112012003051A2 (pt) 2019-12-31
MX2012001794A (es) 2012-03-16
CN101997694A (zh) 2011-03-30

Similar Documents

Publication Publication Date Title
US20090022072A1 (en) Method and apparatus for processing media stream queues based on control
WO2011017889A1 (zh) 一种多媒体会议的实现方法及系统
WO2012113193A1 (zh) 一种多方通话业务的实现方法和系统
WO2007028304A1 (fr) Procede et systeme de realisation de service d'appels de groupe
CN106797379B (zh) 使用合成标识符的电话会议系统
WO2009036662A1 (fr) Procédé, système et appareil permettant d'accéder à une réunion multimédia en réseau
WO2021228005A1 (zh) 会话创建方法、装置及电子设备
EP2738999B1 (en) Method and device for realizing a seamless switch from a two-party call to a conference
WO2011017999A1 (zh) Ip多媒体子系统会议中单方通话的方法及服务设备
WO2012151909A1 (zh) 一种点击拨号业务中实现三方通话的方法及系统
WO2007095855A1 (fr) Procédé et entité réseau de négociation d'un paramètre de type média
WO2011157076A1 (zh) 一种实现多方会议业务的方法、系统及接入网关
WO2007095814A1 (fr) Procédé et système d'obtention de la capacité de session du participant à une session dans un système de communication multipartie
WO2010078781A1 (zh) 一种ptt群组通话控制方法、用户终端及网络侧设备
WO2010091567A1 (zh) 一种点击拨号业务到多媒体会议业务的切换系统及方法
CN108347412A (zh) 一种三方会议中邀请新会议成员的方法、装置及系统
WO2008000157A1 (fr) Procédé et dispositif assurant une fonction d'appel parallèle d'un appel multimédia
WO2008131620A1 (fr) Procédé de prise en charge pour paramètre d'expansion de message de référence
WO2011140744A1 (zh) 一种下一代网络中的多媒体会议系统及实现方法
CN105991239A (zh) 一种ims系统中的信令处理方法、装置和相关设备
WO2012163098A1 (zh) 一种用应用服务器实现子会议功能的方法和系统
WO2013091310A1 (zh) 终端实现呼叫等待的方法、装置和系统
WO2012034423A1 (zh) 会话中早媒体的播放方法及系统
WO2011107012A1 (zh) 一种业务控制方法和装置
WO2023273369A1 (zh) 会议通话方法、装置、存储介质和电子设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10807944

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 13258372

Country of ref document: US

Ref document number: MX/A/2012/001794

Country of ref document: MX

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 1512/DELNP/2012

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2010807944

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2010282015

Country of ref document: AU

WWE Wipo information: entry into national phase

Ref document number: 2012101842

Country of ref document: RU

Ref document number: A20120346

Country of ref document: BY

ENP Entry into the national phase

Ref document number: 2010282015

Country of ref document: AU

Date of ref document: 20100802

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112012003051

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112012003051

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20120210