WO2010075688A1

WO2010075688A1 - Method, apparatus and system for creating and joining ip multimedia subsystem (ims) group conference

Info

Publication number: WO2010075688A1
Application number: PCT/CN2009/073279
Authority: WO
Inventors: 查峰
Original assignee: 华为技术有限公司
Priority date: 2008-12-31
Filing date: 2009-08-17
Publication date: 2010-07-08
Also published as: CN101772195B; CN101772195A

Abstract

A method, apparatus and system for creating and joining the IP Multimedia Subsystem (IMS) are disclosed by the embodiments of the present invention, which belong to the telegraphy field and can effectively solve the problem of joining a group conference by the voice dialing in the prior art, and enable the users to join the conference normally when playing sound and receiving telephone number are required in joining the IMS group conference. Comparing to the prior art, the system provided by the embodiments of the present invention adds a global conference manager, which is used to distribute a globally unique conference number to the conference to be created, and store the conference number in the global conference index table; and search the information of the Session Initiation Protocol (SIP) server which the conference is disposed in according to the information of the conference to be joined. The technical solution of the embodiment of the present invention can adapt to the technical requirements of the large-scale extender for the IMS group conference service capacity.

Description

Method, device and system for creating and joining IMS cluster meeting This application claims China with the application number of 200810186860.3, entitled "Creating and joining IMS cluster meeting and distribution system and device" submitted on December 31, 2008 Priority of the application, the entire contents of which are incorporated herein by reference. Technical field

The present invention relates to the field of telecommunications technologies, and in particular, to a multimedia subsystem (IMS) cluster conference creation method and joining method, device and system. Background technique

Session Initiation Protocol (SIP) is a signaling protocol for real-time communication applications in IP-based networks, especially in the network environment of the Internet. The application of SIP is in an Internet-based environment. Realize data, audio and video real-time communication and other multimedia applications. Parlay is an application programming interface (ΑΡΙ) for telecom services. These interfaces cover the functions of various telecommunication networks, such as call control, SMS service SMS/MMS service MMS, location, billing, presence and availability management, and policy management. Currently, the Parlay application uses the SIP protocol, and the SIP-based IMS conference service is an important Parlay application.

The IMS conference is centered on the Media Server (MS). The conference can be initiated by the user terminal through the core network (CoreNet) side, or by the SIP application server (SIP AS, also known as SIP Server or Parlay Server. This document is collectively referred to as SIP Server. , the same below) initiated. The signaling of the conference has standard initiation (INVITE) flow SIP signaling and SIP INFO control signaling. When the conference is held, the SIP server can call the user terminal to join the conference; the user terminal can also call in from the core network, and join the conference after the MS broadcasts the number and the rights are verified.

In many large telecom service operating environments, a single SIP server is difficult to meet the needs of a large number of concurrent call processing in terms of call processing speed and capacity indicators. So need to use the set Group technology to handle IMS conferencing services. The current IMS cluster conference route distribution scheme can be used in the following scenarios:

1) The conference user creates a conference from the network side INVITE, and the SIP dispatcher (SIP Dispatcher) transfers the SIP signaling to a SIP server according to the load balancing principle, and the SIP server parses the SIP Uniform Resource Identifier (Logic). After processing, it is judged that the user wants to create a new conference. If the conference user carries enough creation information in the SIP signaling, for example, the SIP URI or other fields include the conference access code, the user ID, and the conference password information, the one-time dialing can be authenticated on the SIP server. Operate and create a meeting session. In some IMS conference services, if the user ID and conference password information are added to the session description protocol SDP of the INVITE, a conference session can also be created.

2) The conference user joins the cluster conference from the network side INVITE, and the SIP distributor analyzes the characteristics of the SIP signaling. If the SIP signaling carries enough joining information, the SIP distributor can directly distribute the signaling route to the ongoing conference. The SIP server of the conference number implements the process of triggering the service and adding the authentication to the conference.

However, in the process of implementing the present invention, the inventor has found that the prior art has at least the following problems: In some conference services, the conference user joins the cluster conference from the network side INVITE, and does not carry the conference in the session description protocol SDP of the INVITE. In this case, the SIP server needs to establish a call with the MS, and the conference user is charged and collected to collect the information that the user wants to join the conference. However, if the created conference is not in the SIP server, the SIP server cannot be the conference. The user directly accesses the SIP server that holds the conference. As a result, the conference user cannot join the conference normally. Summary of the invention

In view of this, an embodiment of the present invention provides a method, an apparatus, and a system for creating and joining an IMS cluster conference, so that the user can join the conference normally when joining the IMS cluster conference.

To achieve the above object, an embodiment of the present invention is implemented by the following technical solutions:

In one aspect, a method for creating an IMS cluster conference is provided, including:

Receiving a create conference request sent by the SIP application server, where the creation request carries the user side Create meeting information;

Assigning a globally unique conference number to the conference to be created according to the information to be created, and saving the conference number in the global conference index table;

And returning a create conference request response to the SIP application server, where the create response carries the globally unique conference number assigned to the conference to be created.

Another method of creating an IMS cluster conference is provided, including:

The SIP application server sends a create conference request to the global conference manager, where the create conference request carries information about the conference to be created by the user side;

Receiving, by the SIP application server, a globally unique conference number returned by the global conference manager for the conference to be created;

The SIP application server saves the globally unique conference number in a local conference index table. On the other hand, a method for joining an IMS cluster conference is provided, including:

Receiving the joining conference signaling, the joining conference signaling carries the information that the user side wants to join the conference; querying the global conference index table to the global conference manager according to the information to be joined to the conference, and acquiring the SIP application server information where the conference deployment is located;

The joining conference signaling route is distributed to the SIP application server where the conference deployment is located. Another method of joining IMS cluster meetings is provided, including:

Sending a query conference deployment request to the global conference manager, where the query request carries information about the user side to join the conference;

Receiving a query request response returned by the global conference manager, where the query response carries the SIP application server information that the global conference manager queries according to the information to be joined to the conference; according to the received query response, the query to the query The SIP application server where the deployment is located initiates the joining of the conference signaling, and the joining conference signaling carries the information that the user side wants to join the conference.

Another method of joining IMS cluster meetings is provided, including:

Receiving join conference signaling initiated by the user side;

Obtain information about the user side to join the conference; The global conference index table is queried to the global conference manager according to the obtained information that the user side is to join the conference, and the session initiation protocol SIP application server information where the conference is deployed is obtained.

The joining conference signaling route is distributed to the SIP application server where the conference deployment is located. In another aspect, a distribution system for an IMS cluster conference is provided, including:

The SIP distributor is configured to receive and join the conference signaling; query the global conference index table to the global conference manager according to the information to be joined by the user side, and obtain the SIP application server information where the conference is deployed; a SIP application server to which the conference is deployed; a global conference manager, configured to allocate a globally unique conference number for the conference to be created, and save the conference number in the global conference index table; The information of the conference queries the SIP application server information where the conference is deployed.

And, providing a global conference manager, including:

a conference number assignment unit, configured to allocate a globally unique conference number to the conference to be created according to information to be created;

The conference deployment query unit is configured to query the SIP application server information where the conference is deployed according to the information to be joined to the conference;

The global conference index unit is used to maintain the conference number assigned by the conference number assignment unit and the query for the conference deployment for the conference deployment query unit.

According to the technical solution provided by the foregoing embodiment of the present invention, a global conference manager is added to the route distribution system of the existing IMS cluster conference, and a globally unique conference number is assigned to the conference to be created, and the conference is global. The session number is saved in the index table; and the information about the SIP application server where the conference is deployed is queried according to the information to be added to the conference, so that the user can join the conference when joining the IMS cluster conference, especially when the user needs voice dialing to join the IMS cluster conference. The SIP server can be bridged to the conference deployment, which effectively solves the problem of the prior art voice dialing joining the cluster conference, and can adapt to the technical requirements for the large-scale expansion of the IMS cluster conference service capacity. DRAWINGS

In order to more clearly illustrate the technical solution of the embodiment of the present invention, the following needs in the embodiment. The drawings used are briefly described.

1 is a schematic flowchart of a method for creating an IMS cluster conference according to an embodiment of the present invention; FIG. 2 is a schematic flowchart of a method for joining an IMS cluster conference according to an embodiment of the present invention; A schematic diagram of a method for creating an IMS cluster conference; FIG. 4 is a schematic diagram of a composition of a IMS cluster conference distribution system according to an embodiment of the present invention; FIG. 5 is a flowchart of creating an IMS cluster conference according to an embodiment of the present invention;

FIG. 6 is a flowchart of joining a cluster conference according to an embodiment of the present invention;

FIG. 7 is a flowchart of another joining a cluster conference according to an embodiment of the present invention;

FIG. 8 is a schematic structural diagram of a global conference manager according to an embodiment of the present invention. detailed description

The technical solutions provided by the present invention are further described in detail below with reference to the accompanying drawings and embodiments.

Referring to FIG. 1, a method for creating an IMS cluster conference according to an embodiment of the present invention includes: Step 11: A global conference manager receives a request for creating a conference sent by a SIP server, where the creation request carries information about a conference to be created by a user.

Step 12: The global conference manager allocates a globally unique conference number to the conference to be created according to the information to be created, and saves the conference number in the global conference index table.

Step 13: The global conference manager returns a create conference request response to the SIP server, where the create response carries the globally unique conference number allocated for the conference to be created.

There may be multiple types of conferencing services, such as video conferencing, audio conferencing, or data conferencing. The newly set global conference manager is configured to receive a conference request, and according to the information to be created, assign a globally unique conference number to the conference to be created, and save the conference number in the global conference index table; It is used to receive the query meeting deployment request, and query the SIP application server information where the conference is deployed according to the information to be joined to the conference.

Preferably, after the SIP application server receives the returned create conference request response, the global unique conference number is saved in the local conference index table. It should be noted that there are two methods for obtaining the conference information on the user side: one is that the user terminal directly carries the incoming call from the core network side; and the other is that the user terminal does not directly carry the incoming call from the core network side. The SIP distributor distributes the created conference signaling route initiated by the user side to a SIP server according to the principle of load balancing. The SIP server calls the media server to perform the sound collection and collection, and obtains information about the conference to be created on the user side.

The method for creating an IMS cluster conference provided by the embodiment of the present invention is configured to allocate a globally unique conference number to the conference to be created, and The conference number is saved in the conference index table, and the global conference deployment can be managed. When the conference user joins the IMS cluster conference, the conference number information carried by the conference number or the conference number information obtained through the voice collection number is used to query the global conference. After the index table obtains the deployment information of the conference, it can join the conference normally.

Referring to FIG. 2, an embodiment of the present invention provides a method for joining an IMS cluster conference, including: Step 21: A SIP distributor receives a join conference signaling, where the join conference signaling carries information about a user side to join a conference;

Step 22: The SIP distributor queries the global conference manager to query the global conference index table according to the information to be joined to the conference, and obtains the SIP Server information where the conference is deployed.

Step 23: The SIP distributor distributes the joining conference signaling route to the SIP server where the conference deployment is located.

In one embodiment, the SIP distributor receives the joining conference signaling that the conference user calls in from the core network side, and the joining conference signaling initiated by the user side carries the information that the user side wants to join the conference, and the SIP distributor according to the user The information of the joining conference is firstly queried to the global conference indexer to obtain the global conference index table, and the information about the SIP server in which the conference is deployed is distributed to the SIP server where the conference is deployed.

In another embodiment, the SIP distributor receives the joining conference signaling that the conference user calls in from the core network side, and the joining conference signaling initiated by the user side does not carry the information to join the conference, and the SIP distributor firstly The join conference signaling route initiated by the user side is distributed to any SIP server, and The SIP server calls the media server to perform the sound collection and collection, and obtains the information that the user side wants to join the conference, and then sends the conference conference signaling to the SIP distributor, and carries the information of the conference side to be joined by the user side obtained by the voice collection and reception number; The distributor then queries the global conference manager to query the global conference index table according to the information to be added to the conference, obtains the SIP server information of the conference deployment, and distributes the join conference signaling route to the SIP server where the conference is deployed. .

In a preferred embodiment, the SIP distributor receives the joining conference signaling that the conference user calls in from the core network side, and the joining conference signaling initiated by the user side does not carry the information to join the conference, and the SIP distributor firstly The join conference signaling route initiated by the user side is distributed to any SIP server, and the SIP server calls the media server to perform the sound collection and collection. After obtaining the information of the user side to join the conference, the local conference index table is first queried. If the conference is deployed, the SIP server creates a conference call to join the user to the conference. If the conference deployment is not queried, the SIP server sends the conference conference signaling to the SIP distributor and carries the voice collection number. The user side wants to join the information of the conference; the SIP distributor queries the global conference manager for the global conference index table according to the information to be joined to the conference, and obtains the SIP server information of the conference deployment, and then distributes the conference signaling route to the conference. The SIP server where the conference is deployed.

The optimized embodiment analyzes the SIP signaling feature in the SIP distributor, and directly distributes the signaling route that the user wants to join the conference to the SIP server where the conference is deployed, and does not need to initiate a new bridge call, thereby shortening the signaling transmission time. Accelerate the process of users joining a cluster meeting.

The method for joining a cluster conference provided by the embodiment of the present invention first analyzes the SIP signaling feature and performs a rule operation when the SIP distributor receives the conference-side signaling. If it is a conference service, and the information needs to be added to the cluster conference through the voice-receiving number, it is directly distributed to a SIP server. After the SIP server calls the media server to receive the voice number, the information about the user to join the conference is obtained. This information includes the type of conference service, conference number, and conference password. By querying the local conference index table, if a conference record is found, indicating that the conference is held on the server, the Parlay standard interface is invoked to join the conference user to the conference call. If the conference is not held at the server, the newly acquired conference letter is added to the call signaling by creating a new call that acts as a bridge relay. For example, in the SIP URI that joins the conference signaling, the conference number and the conference password are added after the service access code, and sent to the SIP distributor.

After receiving the new conference call, the SIP distributor determines that it is a conference call, and carries the conference number, queries the global conference manager for the SIP server where the conference is deployed, and forwards the new call to the conference deployment. On the SIP Server. For the SIP distributor, the new joining conference call is the same as the incoming call initiated by the network side. The multiparty call is added to the conference call according to the Parlay standard procedure. If the cluster conference is successful, the system automatically completes the session description protocol SDP. The Session Description Protocol is refreshed, and the SDP of the conference server is sent back to the network side user terminal through the Re-INVITE signaling, so that the user terminal establishes a call with the media of the media server.

Referring to FIG. 3, a method for joining an IMS cluster conference according to an embodiment of the present invention includes: Step 31: A SIP application server sends a query conference deployment request to a global conference manager, where the query request carries a user side to join the conference. Information

Step 32: The SIP application server receives a query request response returned by the global conference manager, where the query response carries the SIP application server information in which the global conference manager queries the conference deployment according to the information to be joined to the conference;

Step 33: The SIP application server initiates joining conference signaling to the SIP application server where the queried conference is deployed according to the received query response, where the join conference signaling carries information about the conference to be joined by the user.

In one embodiment, the SIP distributor receives the joining conference signaling that the conference user calls in from the core network side, and the joining conference signaling initiated by the user side does not carry the information to join the conference, and the SIP distributor firstly uses the conference. The side-initiated join conference signaling route is distributed to any SIP server, and the SIP server calls the media server to perform the sound collection and collection, obtains the information that the user side wants to join the conference, and then sends a query conference deployment request to the global conference manager. And the information that the user side to be added to the conference is to be added to the conference; the SIP server receives the query request response returned by the global conference manager, and the query response carries the information of the SlPServe where the conference deployment is located, and the SIP is sent by the SIP The server directly initiates join conference signaling to the SIP Serve where the queried conference is deployed, and joins the conference. The signaling carries information about the user side to join the conference.

In another embodiment, preferably, the SIP distributor receives the joining conference signaling that the conference user calls in from the core network side, and the joining conference signaling initiated by the user side does not carry the information to join the conference.

The SIP distributor firstly distributes the join conference signaling route initiated by the user side to any SIP server, and the SIP server calls the media server to perform the sound collection and collection, and obtains the information of the user side to join the conference, and first queries the local conference index. If the conference is deployed, the conference call is created by the SIP server to join the conference to the conference; if the conference deployment is not queried, the SIP server sends a query conference deployment request to the global conference manager, and The information about the user to be added to the conference is the information of the conference request. The SIP server receives the query request response returned by the global conference manager. The SIP server sends the SIP Serve information of the conference deployment. The conference server signaling is directly sent to the SIP server where the conference is deployed, and the conference conference signaling carries the information that the user side wants to join the conference.

Referring to FIG. 4, an embodiment of the present invention provides a distribution system for an IMS cluster conference, including:

The SIP distributor 41 is configured to receive the join conference signaling, where the join conference signaling carries the information that the user side wants to join the conference; and the global conference manager queries the global conference index table according to the information to be joined to the conference, and obtains the conference deployment. The SIP server information is located; the route to join the conference signaling is distributed to the SIP server where the conference is deployed;

The global conference manager 42 is configured to allocate a globally unique conference number to the conference to be created, and save the conference number in the global conference index table; and query the SIP server where the conference is deployed according to the information to join the conference. information.

In FIG. 4, the NGN/IMS gateway 40, as a system call control core, is responsible for protocol adaptation, call processing, resource management, and service agent work, and functions as an external interface of the system to perform interconnection and interworking functions with other systems.

More than two SIP Servers 43 (SIP Server 1, SIP Server 2, ... SIP Server N), complying with the Parlay specification service platform, for handling multi-party calls, conference calls or data message services, performing business session establishment and Logic control, and the billing process is performed. The media server 49 is configured to provide a voice collection and conference service for the SIP server. Since the clustering technology is used to process the Parlay service, all the signaling that the NGN/IMS gateway 40 originally sends to the SIP server is directed to the SIP distributor 41. In the configuration of the NGN/IMS gateway 40, the SIP distributor 41 is equivalent to A SIP Server.

The SIP distributor 41 plays the role of load balancing, parses each SIP signaling, analyzes its contents, decomposes the content into computing elements, and distributes the SIP signaling sent by the NGN/IMS gateway 40 to meet the requirements. The rule conditions are a SIP Server.

All services including conference services on each SIP Server are registered on the SIP distributor 41. The signaling semantics on the SIP distributor are very rich. It is necessary to parse the signaling, obtain all the contents contained in it, and analyze all its meanings to obtain the service type. First, according to the principle of business capability matching, several SIP servers with the ability to execute the service are determined, and then one of these devices is selected according to the load balancing principle, and the signaling is distributed. The SIP distributor has one or more, and needs to share a centralized database.

After the conference signaling passes through the SIP distributor 41, if it is a newly created cluster conference, the global conference manager 42 assigns a unique conference number; if it is a cluster conference, the service category identifier and the conference number parameter must be used to the global conference manager. 42 Query the deployment information of the conference. For the SIP signaling from the core network to the SIP distributor, if the signaling carries the conference number and conference type information to be joined, the global conference index table can be queried, and the signaling can be directly transferred to the SIP that deploys the conference. On the server. Otherwise, the SIP signaling is directly transferred to a SIP server, and the SIP server initiates a voice reception and the like to obtain the conference information to be joined, and then initiates a bridged trunk new call to the SIP distributor to join the cluster conference. The conference deployment is queried by the SIP distributor to the global conference manager 42 and is routed to the SIP server deploying the conference according to the queried conference deployment information. After the call is successfully added to the cluster conference, the initial network-side call can be relayed to the conference through the SDP (Session Description Protocol) media exchange.

In an IMS cluster conference distribution system provided by the embodiment of the present invention, an optimized embodiment is that each SIP server further maintains a local conference index table, which can be used according to the conference service type and conference number. Query the local meeting deployment.

It should be noted that the global conference manager provided by the embodiment of the present invention may be set separately or may be combined with a SIP distributor.

The distribution system of the IMS cluster conference provided by the embodiment of the present invention manages the global conference deployment by adding a global conference manager 42 to allocate a global unique conference number to the conference to be created, and save the conference number in the global conference index table. The conference number is used to query the information of the SIP application server where the conference is deployed, and the conference number information obtained by the SIP distributor 41 when the conference user joins the IMS cluster conference, or the conference number information obtained by using the voice collection number. After the global conference index table is obtained, the conference information is sent to the SIP application server where the conference is deployed, so that the conference user can join the conference.

Referring to FIG. 5, an embodiment of the present invention provides a flowchart for creating an IMS cluster conference.

In the step 501, the user sends an incoming call from the network side to the NGN/IMS gateway, and the INVITE creates a cluster conference. Step 502: The SIP distributor analyzes that it is a cluster conference service, and does not specify a conference, and directly distributes the INVITE signaling route to a certain one. A SIP server capable of handling this service, such as SIP Server 1.

Step 503 ~ Step 504, the SIP Server 1 responds to the user 180 on the network side via the SIP distributor.

Step 505 ~ Step 511, the SIP Server 1 obtains the information that the user wants to create a conference, and specifically, the SIP Server1 calls the media server, and the media server broadcasts a number to the user, thereby obtaining information about the user to create the conference.

Step 512: The SIP Server 1 sends a request to create a cluster conference to the global conference manager, where the request carries the information to be created.

Step 513: The global conference manager allocates a unique conference number for the conference to be created, and saves the conference number in the local conference index table of the corresponding conference service category.

Step 514: The global conference manager returns a create cluster conference request response to the SIP server 1, and carries the allocated conference number in the creation response. Step 515: After receiving the creation response, create a cluster conference call entity, and move the multi-party call entity into the conference call, and save the conference number in the local conference index table of the corresponding conference service type to complete the conference creation.

Of course, the creation of the meeting may also be initiated by WEB, still see Figure 5:

Step 520: The user initiates a conference directly on the SIP Server 2 through the WEB page.

Step 521: The SIP Server 2 sends a request to create a conference to the global conference manager, where the request carries the information to be created.

Step 522: The global conference manager allocates a unique conference number for the conference to be created, and saves the conference number in the local conference index table of the corresponding conference service category.

Step 523: The global conference manager returns a create conference request response to the SIP server 2, and carries the assigned conference number in the creation response.

It should be noted that, for the web conference service, the web initiates a conference request to the SIP server, and the SIP server sends a request for creating a cluster conference to the global conference manager, and creates a conference call after obtaining the conference number. The conference call entity needs to actively call out the conference service or join the user from the network side.

It should also be noted that the SIP server issues a conference creation request to the global conference manager, and receives a session request response that is returned by the global conference manager, and may use a transport control/internet protocol TCP/IP packet or use a SIP MESSAGE. Signaling bearer application protocol. The global conference manager provides communication protocols in the form of TCP/IP and SIP MESSAGE. The contents of the conference information can be allocated and queried in the message body of the TCP/IP packet or the SIP MESSAGE. When the conference number is assigned, the protocol includes at least the service identifier ID information, and the query includes at least the service identifier ID and the conference number information. Using SIP MESSAGE to carry the application protocol, text can be placed in the message body to mask the details of TCP communication, which is more open; it is more efficient to carry the application protocol in TCP/IP packet format, provided that SIP Server and Global Conference Manager are used. The underlying support mechanism for TCP/IP communication must be established.

Referring to FIG. 6, FIG. 6 is a flowchart of joining a cluster conference according to an embodiment of the present invention. Step 601: The user calls in from the network side through the NGN/IMS gateway, and the INVITE creates a cluster conference. Step 602: The SIP distributor analyzes that it is joining the cluster conference service, and does not specify the conference number, and directly distributes the INVITE signaling to a certain one. A SIP server capable of handling this service, such as SIP

Server 2. The actual conference to be joined is deployed on SIP Server 1.

Step 603 ~ Step 604, the SIP Server 2 responds to the ringing of the user 180 on the network side via the SIP distributor.

Step 605 to step 611, the SIP Server 2 calls the media server to perform a sound collection and collection, and obtains information about the user to join the conference, where the information includes the conference service type and the conference number.

Step 612, the SIP Server 2 first queries the local index table to determine whether the conference is locally called. If yes, the local Parlay standard interface is invoked, the user is added to the cluster conference, and the process ends; if not, continue with the following process.

Step 613: The SIP Server 2 sends a BYE signaling to the media server to release the session with the media server.

In step 614, the SIP server 2 initiates a new INVITE to the SIP distributor, and the new INVITE signaling carries the information that the obtained user wants to join the conference and the information that the user calls in from the network side INVITE.

Step 615: The SIP distributor queries the global conference manager for the conference deployment according to the obtained conference information, and obtains the SIP server information to be added to the conference deployment.

Step 616: The SIP distributor distributes the new INVITE signaling route to the SIP server where the conference is deployed. For example, in this embodiment, it is SIP Server 1.

In step 617 to step 619, the new INVITE signaling triggers the conference service in the SIP server 1. The SIP server 1 creates a multi-party session entity, and the media server hosting the conference undergoes logical processing such as authentication, and adds the new INVITE signaling. The multiparty calling entity where the target meeting is located.

Step 620 to step 624, the SIP Server 1 forwards the multi-party call entity to the conference call entity by sending SIP INFO conference control signaling to the media server hosting the conference, and forwards the message successfully transferred to the conference call entity to the SIP distributor. SIP Server 2. Step 625 to step 627, the SIP Server 1 sends back the user on the network side through the Re-INVITE signaling, and establishes a session with the media server hosting the conference.

The method of joining the cluster conference in the embodiment of the present invention is that after the voice collection and reception is completed, if it is determined that the target conference is not locally held, a new INVITE call that acts as a bridge relay is initiated to the SIP distributor, and the SIP distributor is globally After the conference manager query determines that the conference is deployed, the SIP Provider then routes the new INVITE to the SIP Server where the conference is deployed.

Referring to FIG. 7, FIG. 7 is a flowchart of another joining conference of the cluster according to an embodiment of the present invention. Steps 701 to 713 are the same as steps 601 to 613 described above, and are not described herein again.

Step 714: The SIP server 2 sends a query meeting deployment request to the global conference manager, where the information about the obtained conference to be joined is included in the query request, and the information includes the type of the conference service and the conference number.

Step 715: The global conference manager returns a query for the conference deployment request to the SIP server 2, and the query response carries the SIP server information that the user wants to join the conference deployment.

In step 716, the SIP server 2 initiates a new INVITE signaling to the SIP server 1 where the conference is deployed. The new INVITE signaling carries the information that the obtained user wants to join the conference and the user calls in from the network side INVITE. Information.

In step 717 to step 719, the new INVITE signaling triggers the conference service in the SIP server 1. The SIP server 1 creates a multi-party session entity, and the media server hosting the conference undergoes logical processing such as authentication, and adds the new INVITE signaling. The multiparty calling entity where the target meeting is located.

Step 720 to step 723, the SIP Server 1 sends the SIP INFO conference control signaling to the media server hosting the conference, transfers the multi-party call entity to the conference call entity, and directly informs the SIP Server 2 ₀ that the conference call entity is successful.

Step 724 ~ Step 726, the SIP Server 1 sends back the user on the network side through the Re-INVITE signaling, and establishes a session with the media server hosting the conference.

The method for joining the cluster conference in the embodiment of the present invention is that after the sound collection and reception is completed, if the target is determined If the conference is not held locally, the global conference manager is first sent a query for the deployment of the conference. After the conference is deployed, the new INVITE call initiated by the bridge relay is directly sent to the SIP server where the conference is deployed.

It should be noted that, for a call that is allocated to the SIP server and needs to be used to determine the conference number, if the conference session entity is not local, the two methods for joining the cluster conference provided by the embodiment of the present invention are different in: First, a new INVITE call is initiated to the SIP distributor to act as a bridge relay. After the SIP distributor queries the global conference manager to determine the conference deployment, the SIP distributor then routes the new INVITE to the SIP where the conference is deployed. The server sends a query to the global conference manager to query the conference deployment request. After the conference is deployed, the new INVITE call that acts as the bridge relay is sent to the SIP server where the conference is deployed.

Referring to FIG. 8, an embodiment of the present invention further provides a global conference manager, including:

a conference number assigning unit 81, configured to allocate a globally unique conference number to the conference to be created according to information to be created;

The conference deployment query unit 82 is configured to query the SIP application server information where the conference is deployed according to the information to be joined to the conference;

The global conference indexing unit 83 is configured to maintain the conference number assigned by the conference number assignment unit 81 and provide a query for the conference deployment for the conference deployment query unit 82.

The global conference manager provided by the embodiment of the present invention, still referring to FIG. 8, further includes:

a request request receiving unit 86, configured to receive a create conference request, where the create request carries information about a conference to be created by the user side;

The query request receiving unit 88 is configured to receive a query meeting deployment request, where the query request carries information that the user side wants to join the conference.

The global conference manager provided by the embodiment of the present invention allocates a unique conference number to the conference to be created by the conference number assignment unit 81, and queries the global conference index unit 83 to obtain the global conference deployment information through the conference deployment query unit 82, so that the present invention The embodiment can implement the establishment and joining scheme of the IMS cluster conference. Compared with the prior art, the user needs voice dialing to join the IMS cluster conference. The SIP server can be bridged to the conference deployment, which effectively solves the problem of the prior art voice dialing joining the cluster conference, and can adapt to the technical requirements for the large-scale expansion of the IMS cluster conference service capacity.

It should be noted that the method in the embodiment of the present invention may be implemented in the form of a software function module, and when the software function module is sold or used as a stand-alone product, it may also be stored in a computer readable storage medium. The above-mentioned storage medium may be a read only memory, a magnetic disk or an optical disk or the like.

The functional units in the embodiments of the present invention may be integrated into one processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. The integrated modules, if implemented in the form of software functional modules and sold or used as stand-alone products, may also be stored in a computer readable storage medium. The above-mentioned storage medium may be a read only memory, a magnetic disk or an optical disk or the like.

The method for creating and joining an IMS cluster conference and the distribution system and the global conference manager provided by the embodiments of the present invention are described in detail above. The description of the embodiments is only for helping to understand the method and the idea of the present invention; It will be obvious to those skilled in the art that variations or substitutions are within the scope of the present invention.

Claims

Claim

A multimedia subsystem IMS cluster conference creation method, comprising: receiving a session initiation protocol, a SIP creation request sent by a SIP application server, where the creation conference request carries information about a conference to be created by a user side;

The method of claim 1 , further comprising: receiving a query global conference index table request sent by the SIP distributor or the SIP application server, where the query request carries information to join the conference;

Obtaining, according to the information to be added to the conference and the global unique conference number, the SIP application server information where the conference deployment is located;

Returning the SIP application server information of the conference deployment to the SIP distributor or the SIP application server, so that the SIP distributor or the SIP application server sends the join conference signaling to the SIP application server where the conference deployment is located.

A method for creating a multimedia subsystem IMS cluster conference, comprising: a session initiation protocol SIP application server sends a create conference request to a global conference manager, where the create conference request carries information about a conference to be created by the user side;

The SIP application server saves the globally unique conference number in a local conference index table.

4. The method according to claim 3, wherein before the creating a meeting request sent to the global conference manager, the method comprises:

The SIP application server receives the creation of a conference letter initiated by the user side of the SIP distributor routing distribution The creating conference signaling does not carry information about the conference to be created;

The SIP application server calls the media server to perform a sound collection and collection, and obtains information for the user side to create a conference.

A multimedia subsystem IMS cluster conference joining method, comprising: receiving a joining conference signaling initiated by a user side;

Obtain information about the user side to join the conference;

And querying the global conference index table from the global conference manager according to the obtained information that the user side is to join the conference, and obtaining the session initiation protocol SIP application server information where the conference deployment is located;

The joining conference signaling route is distributed to the SIP application server where the conference deployment is located.

The joining method according to claim 5, wherein the user side-initiated joining conference signaling is received by the SIP distributor; if the joining conference signaling initiated by the user side carries the user side to join the conference Information

The information about the user side to join the conference is obtained by the SIP distributor from the joining conference signaling initiated by the user side to obtain the information that the user side wants to join the conference.

The joining method according to claim 5, wherein the joining party signaling initiated by the user side is received by the SIP distributor; if the joining conference signaling does not carry information to join the conference; Obtaining information about the user side to join the conference specifically includes:

Transmitting, by the SIP distributor, the joining conference signaling initiated by the user side to any SIP application server;

The SIP distributor receives the joining conference signaling initiated by the SIP application server, and the joining conference signaling initiated by the application server carries the information that the user side to join the conference by the SIP application server to obtain the voice receiving number through the calling media server. .

The method of joining according to claim 7, wherein before the SIP distributor receives the joining conference signaling initiated by the SIP application server, the method further includes:

After the SIP application server performs the sound collection and collection by calling the media server to obtain the information of the user side to join the conference, the local conference index table is queried. If the conference is deployed, the SIP should be Creating a conference call with the server joins the user to the conference; if the conference deployment is not queried, the SIP application server sends the join conference signaling to the SIP distributor.

The joining method according to claim 5, wherein the SIP application server receives the joining conference signaling initiated by the user side distributed by the SIP distributor; if the joining conference signaling does not carry the information to join the conference, The obtaining the information to join the conference specifically includes:

The SIP application server obtains information about the user side to join the conference by calling the media server to perform the sound collection and reception;

The querying the global conference index table to the global conference manager according to the obtained information that the user side is to join the conference, and obtaining the session initiation protocol SIP application server information of the conference deployment is specifically: the SIP application server obtains according to the The user side joins the information of the conference to query the global conference index table of the global conference manager to obtain the session initiation protocol SIP application server information where the conference deployment is located;

The method of distributing the join conference signaling route to the SIP application server where the conference is deployed is specifically: the SIP application server distributes the join conference signaling route to a SIP application server where the conference deployment is located.

The joining method according to claim 9, wherein the SIP application server further includes: before querying the global conference index table by the global conference manager according to the acquired information of the user side to join the conference:

The SIP application server queries the local conference index table according to the information that the user side to join the conference obtained by the voice collection number, and if the conference is deployed, the SIP application server creates a conference call to join the user to the conference; If the conference is not queried, the SIP application server queries the global conference manager for the global conference index table according to the obtained information that the user side wants to join the conference.

A distribution system for a multimedia subsystem IMS cluster, comprising: a SIP distributor for receiving joining conference signaling; and querying a global conference manager for a global conference index according to information that the user side wants to join the conference Table, obtaining the SIP application server information where the conference is deployed; Distributing the join conference signaling route to the SIP application server where the conference deployment is located; a global conference manager, configured to allocate a globally unique conference number to the conference to be created, and save the conference number in the global conference index table. The conference number; and information for querying the SIP application server where the conference is deployed according to the information to be joined to the conference.

12. The distribution system according to claim 11, wherein the global conference manager is integrated with the SIP distributor.

The distribution system according to claim 11, wherein the distribution system further comprises: a SIP application server, configured to receive a SIP distributor route when the joining conference signaling does not carry information to join the conference The joining conference signaling is distributed; the information of the user side to join the conference is obtained by calling the media server to receive the voice number; and the joining conference message carrying the acquired information of the user side to join the conference is sent to the SIP distributor. make.

The SIP distributor is further configured to obtain information about the user side to join the conference according to the received conference conference signaling initiated by the SIP application server.

The distribution system according to claim 11, wherein the distribution system further comprises: a SIP application server, configured to receive a SIP distributor route when the joining conference signaling does not carry information to join the conference The joining conference signaling is distributed; the information of the user side to join the conference is obtained by calling the media server to receive the number of the conference; and the global conference index table is queried to the global conference manager according to the obtained information of the user side to join the conference. Get the session initialization protocol where the conference is deployed

SIP application server information; routing the joining conference signaling route to the SIP application server where the conference deployment is located.

The distribution system according to claim 13 or 14, wherein the distribution system further comprises a media server, configured to receive a call of the SIP application server, and perform a sound collection and reception according to the call to acquire the user. The side joins the information of the conference, and provides the acquired information of the user side to join the conference to the SIP application server.

16. A global conference manager, comprising:

a conference number assignment unit, configured to allocate one for the conference to be created according to information to be created a globally unique conference number;

The conference deployment query unit is configured to query, according to the information to be added to the conference, the session initialization protocol SIP application server information;

The global conference manager according to claim 16, further comprising: a create conference request receiving unit, configured to receive a create conference request, where the create request carries information about a conference to be created by the user side;

The query conference deployment request receiving unit is configured to receive a query conference deployment request, where the query request carries information about the user side to join the conference.