[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

WO2010075688A1 - Ims集群会议的创建和加入方法、装置及系统 - Google Patents

Ims集群会议的创建和加入方法、装置及系统 Download PDF

Info

Publication number
WO2010075688A1
WO2010075688A1 PCT/CN2009/073279 CN2009073279W WO2010075688A1 WO 2010075688 A1 WO2010075688 A1 WO 2010075688A1 CN 2009073279 W CN2009073279 W CN 2009073279W WO 2010075688 A1 WO2010075688 A1 WO 2010075688A1
Authority
WO
WIPO (PCT)
Prior art keywords
conference
information
sip
application server
join
Prior art date
Application number
PCT/CN2009/073279
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 华为技术有限公司
Publication of WO2010075688A1 publication Critical patent/WO2010075688A1/zh

Links

Classifications

    • 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
    • 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/40—Support for services or applications
    • H04L65/403—Arrangements for multi-party communication, e.g. for conferences
    • H04L65/4046—Arrangements for multi-party communication, e.g. for conferences with distributed floor control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/56—Arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/006—Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP), including next generation networks with a packet-switched transport layer

Definitions

  • 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.
  • IMS multimedia subsystem
  • Session Initiation Protocol 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.
  • the Parlay application uses the SIP protocol
  • 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.
  • 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.
  • the current IMS cluster conference route distribution scheme can be used in the following scenarios:
  • 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.
  • SIP dispatcher SIP Dispatcher
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • a method for creating an IMS cluster conference including:
  • Another method of creating an IMS cluster conference 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;
  • the SIP application server saves the globally unique conference number in a local conference index table.
  • a method for joining an IMS cluster conference including:
  • 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:
  • 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 including:
  • 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.
  • a distribution system for an IMS cluster conference 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.
  • 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.
  • 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.
  • FIG. 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
  • a method for creating an IMS cluster conference 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.
  • 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.
  • the global unique conference number is saved in the local conference index table.
  • 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.
  • 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.
  • the index table obtains the deployment information of the conference, it can join the conference normally.
  • 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.
  • 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.
  • 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 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.
  • 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.
  • 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.
  • the newly acquired conference letter is added to the call signaling by creating a new call that acts as a bridge relay.
  • the conference number and the conference password are added after the service access code, and sent to the SIP distributor.
  • 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.
  • 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.
  • a method for joining an IMS cluster conference 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the initial network-side call can be relayed to the conference through the SDP (Session Description Protocol) media exchange.
  • SDP Session Description Protocol
  • 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.
  • 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 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.
  • the conference information is sent to the SIP application server where the conference is deployed, so that the conference user can join the conference.
  • an embodiment of the present invention provides a flowchart for creating an IMS cluster conference.
  • 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.
  • Step 503 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.
  • 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.
  • 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.
  • 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.
  • the protocol includes at least the service identifier ID information
  • the query includes at least the service identifier ID and the conference number information.
  • 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.
  • SIP Server and Global Conference Manager are used.
  • the underlying support mechanism for TCP/IP communication must be established.
  • 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.
  • Step 603 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.
  • 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.
  • SIP Server 1 For example, in this embodiment, it is SIP Server 1.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 0 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.
  • a new INVITE call is initiated to the SIP distributor to act as a bridge relay.
  • 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.
  • the new INVITE call that acts as the bridge relay is sent to the SIP server where the conference is deployed.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • General Engineering & Computer Science (AREA)
  • Telephonic Communication Services (AREA)

Description

IMS集群会议的创建和加入方法、 装置及系统 本申请要求了 2008年 12月 31 日提交的、 申请号为 200810186860.3、 发 明名称为" IMS 集群会议的创建和加入方法及分发系统和装置"的中国申请的 优先权， 其全部内容通过引用结合在本申请中。 技术领域
本发明涉及电信技术领域， 具体而言是涉及一种多媒体子系统 ( Multimedia Subsystem, IMS ) 集群会议的创建方法和加入方法、 装置及系 统。 背景技术
会话初始化协议 ( Session Initiation Protocol, SIP )是在基于 IP的网络中， 特别是在 Internet结构的网络环境中实现实时通信应用的一种信令协议， SIP 的应用目标是在基于 Internet的环境中， 实现数据、 音视频实时通信及其它多 媒体应用。 Parlay是一个电信业务的应用程序接口 （ Application Programming Interface ,ΑΡΙ )。 这些接口覆盖了各种电信网的功能， 比如， 呼叫控制、 短信 服务 SMS/多媒体短信服务 MMS、 定位、 计费、 在席和可用性管理以及策略 管理等。 目前 Parlay应用使用的是 SIP协议， 而且基于 SIP协议的 IMS会议 业务是一种重要的 Parlay应用。
IMS会议以媒体服务器（Media Server, MS )为中心， 会议可由用户终端 通过核心网（ CoreNet )侧发起，也可由 SIP应用服务器（ SIP AS,又称 SIP Server 或 Parlay Server, 本文统一称为 SIP Server, 下同 )发起。 会议的信令有标准 的发起 ( INVITE )流程 SIP信令和 SIP INFO控制信令。 会议召开时， 可以由 SIP Server呼用户终端入会； 也可以由用户终端从核心网呼入， 通过 MS放音 收号、 权限验证后加入会议。
在很多大的电信业务运营环境中，单台 SIP Server无论从呼叫处理速度还 是容量指标来看， 都很难满足未来大量并发呼叫处理需要。 因此需要釆用集 群技术来处理 IMS会议业务。 目前釆用的 IMS集群会议路由分发方案， 可以 用于以下的场景：
1 )会议用户从网络侧 INVITE创建会议， SIP分发器（ SIP Dispatcher ) 按负载均衡原则将 SIP信令转给一台 SIP Server, 该 SIP Server解析 SIP统一 资源标识符 URI (Uniform Resource Identifier) , 逻辑处理后判断用户要创建新 会议。如果会议用户在 SIP信令中携带足够多的创建信息，例如 SIP URI或其 它字段中有会议接入码、 用户 ID、 会议密码信息， 通过这种一次拨号就可以 在该 SIP Server上通过鉴权操作并创建会议会话。 在有的 IMS会议业务中， 如果在 INVITE的会话描述协议 SDP中加入以上的用户 ID及会议密码信息， 也可以创建会议会话。
2 )会议用户从网络侧 INVITE加入集群会议， SIP分发器分析 SIP信令 的特征，如果 SIP信令中携带足够多的加入信息， SIP分发器就可以直接将该 信令路由分发至正在召开该会议号的 SIP Server, 实现触发业务、 鉴权加入会 议的过程。
但是， 在实现本发明的过程中， 发明人发现现有技术至少存在以下问题： 在有些会议业务中，会议用户从网络侧 INVITE加入集群会议，在 INVITE 的会话描述协议 SDP 中没有携带要加入会议的信息， 此时， 需要通过 SIP Server与 MS建立通话， 对会议用户进行放音收号收集用户要加入会议的信 息， 但如果创建的会议不在该 SIP Server, 则该 SIP Server将无法将该会议用 户直接接入到召开会议的 SIP Server, 最终导致会议用户无法正常加入会议。 发明内容
有鉴于此， 本发明的实施例提供一种 IMS集群会议的创建和加入方法、 装置及系统， 使得用户在加入 IMS集群会议时能够正常加入会议。
为实现上述目的， 本发明的实施例是通过如下技术方案实现的：
一方面， 提供一种 IMS集群会议的创建方法， 包括：
接收 SIP应用服务器发送的创建会议请求， 所述创建请求携带用户侧要 创建会议的信息；
根据所述要创建会议的信息， 为所述要创建会议分配一个全局唯一的会 议号， 并在全局会议索引表中保存该会议号；
向所述 SIP应用服务器返回创建会议请求响应， 所述创建响应携带为所 述要创建会议分配的所述全局唯一的会议号。
提供的另一种 IMS集群会议的创建方法， 包括：
SIP应用服务器向全局会议管理器发送创建会议请求，所述创建会议请求 携带用户侧要创建会议的信息；
所述 SIP应用服务器接收全局会议管理器返回的为所述要创建会议分配 的一个全局唯一的会议号；
所述 SIP应用服务器在本地会议索引表中保存所述全局唯一的会议号。 另一方面， 提供一种 IMS集群会议的加入方法， 包括：
接收加入会议信令， 所述加入会议信令携带用户侧要加入会议的信息； 根据所述要加入会议的信息向全局会议管理器查询全局会议索引表， 获 取会议部署所在的 SIP应用服务器信息；
将所述加入会议信令路由分发至所述会议部署所在的 SIP应用服务器。 提供的另一种 IMS集群会议的加入方法， 包括：
向全局会议管理器发送查询会议部署请求， 所述查询请求携带用户侧要 加入会议的信息；
接收全局会议管理器返回的查询请求响应， 所述查询响应携带全局会议 管理器根据要加入会议的信息查询到的会议部署所在的 SIP应用服务器信息； 根据接收到的查询响应， 向查询到的会议部署所在的 SIP应用服务器发 起加入会议信令， 所述加入会议信令携带用户侧要加入会议的信息。
提供的再一种 IMS集群会议的加入方法， 包括：
接收用户侧发起的加入会议信令；
获取用户侧要加入会议的信息； 根据所述获取的用户侧要加入会议的信息向全局会议管理器查询全局会 议索引表， 获取会议部署所在的会话初始化协议 SIP应用服务器信息；
将所述加入会议信令路由分发至所述会议部署所在的 SIP应用服务器。 再一方面， 提供一种 IMS集群会议的分发系统， 包括：
SIP分发器，用于接收加入会议信令；根据用户侧要加入会议的信息向全 局会议管理器查询全局会议索引表， 获取会议部署所在的 SIP应用服务器信 息； 将所述加入会议信令路由分发至所述会议部署所在的 SIP应用服务器； 全局会议管理器， 用于为所述要创建会议分配一个全局唯一的会议号， 并在全局会议索引表中保存该会议号； 以及用于根据要加入会议的信息查询 会议部署所在的 SIP应用服务器信息。
以及， 提供一种全局会议管理器， 包括：
会议号分配单元， 用于根据要创建会议的信息， 为所述要创建会议分配 一个全局唯一的会议号；
会议部署查询单元，用于根据要加入会议的信息查询会议部署所在的 SIP 应用服务器信息；
全局会议索引单元， 用于维护会议号分配单元分配的会议号和为会议部 署查询单元提供会议部署的查询。
由以上本发明实施例提供的技术方案可知，通过在现有 IMS集群会议的路 由分发系统中增设全局会议管理器， 用于为所述要创建会议分配一个全局唯 一的会议号， 并在全局会议索引表中保存该会议号； 以及用于根据要加入会 议的信息查询会议部署所在的 SIP应用服务器信息， 使得用户在加入 IMS集群 会议时能够正常加入会议，尤其在用户需要语音拨号加入 IMS集群会议时能够 桥接中继至会议部署的 SIP Server, 有效地解决了现有技术语音拨号加入集群 会议的难题， 能够适应 IMS集群会议业务容量大规模扩展的技术要求。 附图说明
为了更清楚地说明本发明实施例的技术方案， 下面将对实施例中所需要 使用的附图作简单地介绍。
图 1为本发明实施例提供的一种 IMS集群会议的创建方法流程示意图； 图 2为本发明实施例提供的一种 IMS集群会议的加入方法流程示意图； 图 3为本发明实施例提供的另一种 IMS集群会议的创建方法流程示意图； 图 4为本发明实施例提供的一种 IMS集群会议的分发系统组成示意图； 图 5为本发明实施例提供的一种创建 IMS集群会议的流程图；
图 6为本发明实施例提供的一种加入集群会议的流程图；
图 7为本发明实施例提供的另一种加入集群会议的流程图；
图 8为本发明实施例提供的一种全局会议管理器的结构示意图。 具体实施方式
为使本发明的目的、 技术方案、 及优点更加清楚明白， 下面结合附图并 举实施例， 对本发明提供的技术方案进一步详细描述。
参见图 1 , 本发明实施例提供的一种 IMS集群会议的创建方法， 包括： 步骤 11 , 全局会议管理器接收 SIP Server发送的创建会议请求， 所述创 建请求携带用户侧要创建会议的信息；
步骤 12, 全局会议管理器根据所述要创建会议的信息， 为所述要创建会 议分配一个全局唯一的会议号， 并在全局会议索引表中保存该会议号；
步骤 13 , 全局会议管理器向所述 SIP Server返回创建会议请求响应， 所 述创建响应携带为所述要创建会议分配的所述全局唯一的会议号。
会议业务可能有多种， 例如视频会议、 音频会议或者数据会议等。 新设 置的全局会议管理器用于接收创建会议请求， 根据所述要创建会议的信息， 为所述要创建会议分配一个全局唯一的会议号， 并在全局会议索引表中保存 该会议号； 同时也用于接收查询会议部署请求， 根据要加入会议的信息查询 会议部署所在的 SIP应用服务器信息。
优选地， 在所述 SIP应用服务器接收到返回的创建会议请求响应后， 在 本地会议索引表中保存所述全局唯一的会议号。 需要说明的是， 获取用户侧要创建会议信息的方法有两种： 一种是用户 终端从核心网侧呼入时直接携带； 一种是用户终端从核心网侧呼入时未直接 携带， 由 SIP分发器按负载均衡的原则将用户侧发起的创建会议信令路由分 发给一台 SIP Server, 由该 SIP Server呼叫媒体服务器进行放音收号， 获取用 户侧要创建会议的信息。
本发明实施例提供的创建 IMS集群会议的方法， 根据创建会议请求中携 带的用户侧要创建会议的信息， 通过全局会议管理器为所述要创建会议分配 一个全局唯一的会议号， 并在全局会议索引表中保存该会议号， 能够对全局 会议部署进行管理， 使得会议用户在加入 IMS集群会议时， 通过携带的会议 号信息或通过放音收号获取到的会议号信息， 在查询全局会议索引表获取会 议召开的部署信息后， 能够正常加入会议。
参见图 2, 本发明实施例提供一种 IMS集群会议的加入方法， 包括： 步骤 21 , SIP分发器接收加入会议信令， 所述加入会议信令携带用户侧 要加入会议的信息；
步骤 22, SIP分发器根据所述要加入会议的信息向全局会议管理器查询 全局会议索引表， 获取会议部署所在的 SIP Server信息；
步骤 23 , SIP分发器将所述加入会议信令路由分发至所述会议部署所在 的 SIP Server。
一种实施例， SIP分发器接收会议用户从核心网侧呼入的加入会议信令， 所述用户侧发起的加入会议信令携带用户侧要加入会议的信息， 此时 SIP分 发器根据用户要加入会议的信息首先向全局会议管理器查询全局会议索引 表， 获取会议部署所在的 SIP Server信息后， 将所述加入会议信令路由分发至 所述会议部署所在的 SIP Server。
另一种实施例， SIP 分发器接收会议用户从核心网侧呼入的加入会议信 令， 所述用户侧发起的加入会议信令未携带要加入会议的信息， 此时 SIP分 发器首先将该用户侧发起的加入会议信令路由分发给任一 SIP Server, 由该 SIP Server呼叫媒体服务器进行放音收号， 获取用户侧要加入会议的信息后， 再向 SIP分发器发送加入会议信令， 并携带放音收号获取的用户侧要加入会 议的信息； 由 SIP分发器根据所述要加入会议的信息再向全局会议管理器查 询全局会议索引表， 获取会议部署所在的 SIP Server信息后， 将所述加入会议 信令路由分发至所述会议部署所在的 SIP Server。
一种优选实施例， SIP分发器接收会议用户从核心网侧呼入的加入会议信 令， 所述用户侧发起的加入会议信令未携带要加入会议的信息， 此时 SIP分 发器首先将该用户侧发起的加入会议信令路由分发给任一 SIP Server, 由该 SIP Server呼叫媒体服务器进行放音收号， 获取用户侧要加入会议的信息后， 首先查询本地会议索引表， 如果查询到该会议部署， 则由该 SIP Server创建会 议呼叫将用户加入到会议中； 如果未查询到该会议部署， 则由该 SIP Server 再向 SIP分发器发送加入会议信令， 并携带放音收号获取的用户侧要加入会 议的信息； SIP分发器根据所述要加入会议的信息向全局会议管理器查询全 局会议索引表， 获取会议部署所在的 SIP Server信息后， 将所述加入会议信令 路由分发至所述会议部署所在的 SIP Server。
本优化实施例在 SIP分发器分析 SIP信令特征， 直接将用户要加入会议 的信令路由分发至部署会议所在的 SIP Server情形下，无需再发起新的桥接呼 叫， 可以缩短信令传输时间， 加快用户加入集群会议的流程。
本发明实施例提供的加入集群会议的方法， 在 SIP分发器收到网络侧的 加入会议信令时， 首先分析 SIP信令特征， 进行规则运算。 如果是会议业务， 且需要通过放音收号才能决定加入集群会议的信息， 则直接分发给某台 SIP Server , 该 SIP Server呼叫媒体服务器进行放音收号后， 获取用户要加入会议 的信息， 该信息包括会议业务种类、 会议号和会议密码等。 通过查询本地会 议索引表， 如果查找到会议记录， 说明该会议在本服务器召开， 则调用 Parlay 标准接口， 将会议用户加入到会议呼叫中。 如果该会议不在本服务器召开， 则通过创建起桥接中继作用的新呼叫， 在呼叫信令中加入新获取到的会议信 息，例如在加入会议信令的 SIP URI里，在该业务接入码后加入会议号及会议 密码， 发送给 SIP分发器。
SIP分发器收到该新的加入会议呼叫，判定是会议呼叫 ,而且带了会议号， 则向全局会议管理器中查询会议部署所在的 SIP Server, 并将该新的呼叫转发 到会议部署所在的 SIP Server上。 对 SIP分发器而言， 该新的加入会议呼叫 与网络侧发起的入会呼叫无异， 按 Parlay标准流程将该多方呼叫加入到会议 呼叫； 如果加入集群会议成功， 系统会自动完成会话描述协议 SDP ( Session Description Protocol )刷新， 将会议服务器的 SDP通过 Re-INVITE信令回送 给网络侧用户终端， 从而用户终端与媒体服务器的媒体建立通话。
参见图 3 , 本发明实施例还提供的一种 IMS集群会议的加入方法， 包括： 步骤 31 , SIP应用服务器向全局会议管理器发送查询会议部署请求， 所 述查询请求携带用户侧要加入会议的信息；
步骤 32,所述 SIP应用服务器接收全局会议管理器返回的查询请求响应， 所述查询响应携带全局会议管理器根据要加入会议的信息查询到的会议部署 所在的 SIP应用服务器信息；
步骤 33 , 所述 SIP应用服务器根据接收到的查询响应， 向查询到的会议 部署所在的 SIP应用服务器发起加入会议信令， 所述加入会议信令携带用户 侧要加入会议的信息。
一种实施例， SIP分发器接收会议用户从核心网侧呼入的加入会议信令， 所述用户侧发起的加入会议信令未携带要加入会议的信息， 此时 SIP分发器 首先将该用户侧发起的加入会议信令路由分发给任一 SIP Server, 由该 SIP Server呼叫媒体服务器进行放音收号， 获取用户侧要加入会议的信息后，再向 全局会议管理器发送查询会议部署请求， 并携带放音收号获取的用户侧要加 入会议的信息； 该 SIP Server接收全局会议管理器返回的查询请求响应， 在该 查询响应中携带查询到的会议部署所在的 SlPServe信息， 则由该 SIP Server 直接向查询到的会议部署所在的 SIP Serve发起加入会议信令， 所述加入会议 信令携带用户侧要加入会议的信息。
另一种实施例， 优选地， SIP分发器接收会议用户从核心网侧呼入的加入 会议信令， 所述用户侧发起的加入会议信令未携带要加入会议的信息， 此时
SIP分发器首先将该用户侧发起的加入会议信令路由分发给任一 SIP Server, 由该 SIP Server呼叫媒体服务器进行放音收号，获取用户侧要加入会议的信息 后， 首先查询本地会议索引表， 如果查询到该会议部署， 则由该 SIP Server 创建会议呼叫将用户加入到会议中； 如果未查询到该会议部署， 则由该 SIP Server再向全局会议管理器发送查询会议部署请求，并携带放音收号获取的用 户侧要加入会议的信息；该 SIP Server接收全局会议管理器返回的查询请求响 应， 在该查询响应携带查询到的会议部署所在的 SIP Serve信息， 则由该 SIP Server直接向查询到的会议部署所在的 SIP Server发起加入会议信令， 所述加 入会议信令携带用户侧要加入会议的信息。
参见图 4, 本发明实施例提供一种 IMS集群会议的分发系统， 包括：
SIP分发器 41 , 用于接收加入会议信令， 所述加入会议信令携带用户侧 要加入会议的信息； 根据所述要加入会议的信息向全局会议管理器查询全局 会议索引表， 获取会议部署所在的 SIP Server信息； 将所述加入会议信令路由 分发至所述会议部署所在的 SIP Server;
全局会议管理器 42,用于为所述要创建会议分配一个全局唯一的会议号， 并在全局会议索引表中保存该会议号； 以及用于根据要加入会议的信息查询 会议部署所在的 SIP Server信息。
在附图 4中， NGN/IMS网关 40,作为系统呼叫控制核心， 负责协议适配、 呼叫处理、 资源管理、 业务代理工作， 同时作为系统的对外接口完成和其它 系统的互连互通功能。
两个以上的 SIP Server 43 ( SIP Server 1, SIP Server 2,... SIP Server N ), 遵 从 Parlay规范的业务平台， 用于处理多方呼叫、 会议呼叫或数据消息业务， 执行业务会话的建立和逻辑控制， 并执行计费流程。 媒体服务器 49, 用于为 SIP Server提供放音收号及会议服务。 由于釆用集群技术来处理 Parlay业务， 所有 NGN/IMS网关 40本来发送 给 SIP Server的信令全部定向给 SIP分发器 41 , 在 NGN/IMS网关 40的配置 中， SIP分发器 41就等价于一个 SIP Server。
SIP分发器 41起着负载均衡的作用， 解析每条 SIP信令， 分析其内容， 将这些内容分解为计算元素，按规则计算后，将 NGN/IMS网关 40发来的 SIP 信令分发给满足规则条件一台 SIP Server。
在 SIP分发器 41上注册了每台 SIP Server上包括会议业务在内的所有业 务。 SIP分发器上的信令语义非常丰富， 必须解析信令， 获得其中包含的全部 内容， 分析其全部含义才能够获取业务类型。 首先按业务能力匹配原则确定 出具有执行该业务的能力几台 SIP Server, 然后按负载均衡原则从这几台设备 选择一台， 将信令分发过去。 所述 SIP分发器有一个或多个， 需共用一个集 中数据库。
会议信令经过 SIP分发器 41后， 如果是新创建集群会议， 由全局会议管 理器 42分配一个唯一的会议号； 如果是加入集群会议， 必须用业务种类标识 和会议号参数向全局会议管理器 42查询该会议的部署信息。 对于从核心网到 SIP分发器的 SIP信令， 如果信令中携带了要加入的会议号和会议种类信息， 则通过查询全局会议索引表， 就能直接将信令转到部署该会议的 SIP Server 上。 否则， 先将 SIP信令直接转到某台 SIP Server, 由该 SIP Server发起放音 收号等方式获取将要加入的会议信息， 再向 SIP分发器发起加入集群会议的 一个桥接中继新呼叫， 由 SIP分发器向全局会议管理器 42查询会议部署， 并 根据查询到的会议部署信息，将该呼叫路由到部署会议的 SIP Server上。 当该 呼叫成功加入集群会议后， 通过会话描述协议 SDP ( Session Description Protocol )媒体交换后， 就能将最初网络侧呼叫中继到会议中。
在本发明实施例提供的 IMS集群会议的分发系统中，一种优化实施例是， 每台 SIP Server还维护一张本地会议索引表，可用于按会议业务种类和会议号 查询本地会议部署。
需要说明的是， 本发明实施例提供的全局会议管理器可以单独设置， 也 可以与 SIP分发器合设。
本发明实施例提供的 IMS集群会议的分发系统， 通过增设全局会议管理 器 42对全局会议部署进行管理， 为所述要创建会议分配一个全局唯一的会议 号， 并在全局会议索引表中保存该会议号， 用于查询会议部署所在的 SIP应 用服务器信息， 能够使得会议用户在加入 IMS集群会议时， 由 SIP分发器 41 通过携带的会议号信息或通过放音收号获取到的会议号信息， 在查询全局会 议索引表获取会议召开的部署信息后， 将加入会议信令路由分发至所述会议 部署所在的 SIP应用服务器， 使得会议用户能够正常加入会议。
参见图 5, 本发明实施例提供了一种创建 IMS集群会议的流程图。
步骤 501 , 用户从网络侧经 NGN/IMS网关呼入， INVITE创建集群会议； 步骤 502, SIP分发器分析其为创建集群会议业务， 且未指定会议， 直接 将 INVITE信令路由分发给某一有能力处理该业务的 SIP Server, 例如 SIP Server 1。
步骤 503 ~步骤 504, SIP Server 1经 SIP分发器向网络侧的用户 180振 铃响应。
步骤 505 ~步骤 511 , SIP Server 1获取用户要创建会议的信息， 具体可以 是 SIP Serverl呼叫媒体服务器， 由媒体服务器向用户放音收号， 从而获取用 户要创建会议的信息。
步骤 512, SIP Server 1向全局会议管理器发出创建集群会议请求， 创建 请求中携带要创建会议的信息。
步骤 513 ,全局会议管理器为该要创建的会议分配一个唯一的会议号， 并 在相应会议业务种类的本地会议索引表中保存该会议号。
步骤 514, 全局会议管理器向 SIP Server 1返回创建集群会议请求响应， 在创建响应中携带该分配的会议号。 步骤 515 , 收到该创建响应后， 创建集群会议呼叫实体， 并将多方呼叫实 体移入会议呼叫， 同时在相应会议业务种类的本地会议索引表中保存该会议 号， 完成会议的创建。
当然会议的创建也可能是由 WEB发起， 仍参见图 5:
步骤 520 , 用户通过 WEB页面直接在 SIP Server 2上发起会议。
步骤 521 , SIP Server 2向全局会议管理器发出创建会议请求， 创建请求 中携带要创建会议的信息。
步骤 522,全局会议管理器为该要创建的会议分配一个唯一的会议号， 并 在相应会议业务种类的本地会议索引表中保存该会议号。
步骤 523 , 全局会议管理器向 SIP Server 2返回创建会议请求响应， 在创 建响应中携带该分配的会议号。
需要说明的是， 对于 Web会议业务， 由 Web发起向 SIP Server创建会议 请求， SIP Server向全局会议管理器发出创建集群会议的请求， 获得会议号后 创建会议呼叫， 这时的会议呼叫中还没有会议呼叫实体， 需要会议业务主动 呼出或者用户从网络侧加入。
还需要说明的是， 所述 SIP Server向全局会议管理器发出会议创建请求， 以及接收全局会议管理器返回的创建集群会议请求响应， 可以使用传输控制 / 网际协议 TCP/IP数据包或者使用 SIP MESSAGE信令承载应用协议。 全局会 议管理器提供 TCP/IP和 SIP MESSAGE格式的通信协议，在 TCP/IP数据包或 者 SIP MESSAGE的消息体中可以定义分配、查询会议信息的内容。分配会议 号时协议中至少包含业务标识 ID信息， 查询时至少包括业务标识 ID和会议 号信息。 用 SIP MESSAGE承载应用协议可以使用文本放在消息体中， 屏蔽 TCP通信细节， 更具开放性； 用 TCP/IP数据包格式承载应用协议效率效率更 高些， 前提是 SIP Server和全局会议管理器必须建立 TCP/IP通信底层支撑机 制。
参见图 6, 图 6为本发明实施例提供的一种加入集群会议的流程图。 步骤 601 , 用户从网络侧经 NGN/IMS网关呼入， INVITE创建集群会议； 步骤 602 , SIP分发器分析其为加入集群会议业务， 且未指定会议号， 直接将 INVITE 信令分发给某一有能力处理该业务的 SIP Server, 例如 SIP
Server 2。 而实际要加入的会议部署在 SIP Server 1。
步骤 603 ~步骤 604, SIP Server 2经 SIP分发器向网络侧的用户 180振铃 口向应。
步骤 605〜步骤 611 , SIP Server 2呼叫媒体服务器进行放音收号， 获取用 户要加入会议的信息， 所述信息包括会议业务种类和会议号等。
步骤 612, SIP Server 2首先查询本地索引表， 判定该会议是否在本地召 开。 如果是， 则调用本地的 Parlay标准接口， 将用户加入集群会议中， 流程 结束返回； 如果否， 继续下面的流程。
步骤 613 , SIP Server 2向媒体服务器发送 BYE信令， 释放与媒体服务器 的会话。
步骤 614, SIP Server 2向 SIP分发器发起一个新的 INVITE, 在该新的 INVITE信令中携带获取到的用户要加入会议的信息和用户从网络侧 INVITE 呼入的信息。
步骤 615 , SIP分发器根据获取的加入会议信息， 向全局会议管理器查询 会议部署， 获取要加入会议部署所在的 SIP Server信息。
步骤 616, SIP分发器将该新的 INVITE信令路由分发至该会议部署所在 的 SIP Server, 例如， 本实施例中为 SIP Server 1。
步骤 617 ~步骤 619,该新的 INVITE信令触发 SIP Server 1中的会议业务， SIP Server 1创建多方会话实体， 与承载会议的媒体服务器经过鉴权等逻辑处 理， 将该新的 INVITE信令加入目标会议所在的多方呼叫实体。
步骤 620〜步骤 624, SIP Server 1通过向承载会议的媒体服务器发 SIP INFO会控信令， 将多方呼叫实体转入会议呼叫实体， 并将转入会议呼叫实体 成功的消息经 SIP分发器转发给 SIP Server 2。 步骤 625 ~步骤 627 , SIP Server 1通过 Re-INVITE信令回送给网络侧的 用户， 将用户与承载会议的媒体服务器建立会话。
本发明实施例加入集群会议的方法是放音收号完毕后， 如果确定目标会 议不在本地召开， 则先向 SIP分发器发起一个起桥接中继作用的新的 INVITE 呼叫， 由 SIP分发器向全局会议管理器查询确定会议部署后，再由 SIP分发器 将该新的 INVITE路由至会议部署所在的 SIP Server。
参见图 7 , 图 7为本发明实施例提供的另一种加入集群会议的流程图。 步骤 701〜步骤 713 , 分别同于上述的步骤 601〜步骤 613 , 在此不再赘 述。
步骤 714, SIP Server 2向全局会议管理器发出查询会议部署请求， 在查 询请求中携带所述获取到的用户要加入会议的信息， 该信息包括查询到的会 议业务种类和会议号。
步骤 715 , 全局会议管理器向 SIP Server 2返回查询会议部署请求响应， 在查询响应中携带用户要加入会议部署所在的 SIP Server信息。
步骤 716 , SIP Server 2 向会议部署所在的 SIP Server 1 发起一个新的 INVITE信令， 所述新的 INVITE信令中携带所述获取到的用户要加入会议的 信息和用户从网络侧 INVITE呼入的信息。
步骤 717 ~步骤 719,该新的 INVITE信令触发 SIP Server 1中的会议业务， SIP Server 1创建多方会话实体， 与承载会议的媒体服务器经过鉴权等逻辑处 理， 将该新的 INVITE信令加入目标会议所在的多方呼叫实体。
步骤 720 ~步骤 723 , SIP Server 1通过向承载会议的媒体服务器发 SIP INFO会控信令， 将多方呼叫实体转入会议呼叫实体， 并将转入会议呼叫实体 成功的消息直接告知 SIP Server 20
步骤 724 ~步骤 726, SIP Server 1通过 Re-INVITE信令回送给网络侧的 用户， 将用户与承载会议的媒体服务器建立会话。
本发明实施例加入集群会议的方法是放音收号完毕后， 如果确定目标会 议不在本地召开， 则先向全局会议管理器发出查询会议部署请求， 确定会议 部署后，直接将发起的起桥接中继作用的新的 INVITE呼叫发给会议部署所在 的 SIP Server。
需要说明的是， 对于分配到 SIP Server需要放音收号确定会议号的呼叫， 如果会议会话实体不在本地， 本发明实施例提供的两种加入集群会议的方法， 它们的不同在于： 一种是先向 SIP 分发器发起一个起桥接中继作用的新的 INVITE 呼叫， 由 SIP分发器向全局会议管理器查询确定会议部署后， 再由 SIP分发器将该新的 INVITE路由至会议部署所在的 SIP Server; 一种是先向 全局会议管理器发出查询会议部署请求， 确定会议部署后， 直接将发起的起 桥接中继作用的新的 INVITE呼叫发给会议部署所在的 SIP Server。
参见图 8, 本发明实施例还提供一种全局会议管理器， 包括：
会议号分配单元 81 , 用于根据要创建会议的信息， 为所述要创建会议分 配一个全局唯一的会议号；
会议部署查询单元 82, 用于根据要加入会议的信息查询会议部署所在的 SIP应用服务器信息；
全局会议索引单元 83 ,用于维护会议号分配单元 81分配的会议号和为会 议部署查询单元 82提供会议部署的查询。
本发明实施例提供的全局会议管理器， 仍参见图 8, 还包括：
创建请求接收单元 86 , 用于接收创建会议请求， 所述创建请求携带用户 侧要创建会议的信息； 以及，
查询请求接收单元 88, 用于接收查询会议部署请求， 所述查询请求携带 用户侧要加入会议的信息。
本发明实施例提供的全局会议管理器， 通过会议号分配单元 81为要创建 的会议分配一个唯一的会议号， 通过会议部署查询单元 82查询全局会议索引 单元 83获取全局会议部署信息，使得本发明实施例能够实施 IMS集群会议的 建立和加入方案， 与现有技术相比， 在用户需要语音拨号加入 IMS集群会议 时能够桥接中继至会议部署的 SIP Server, 有效地解决了现有技术语音拨号加 入集群会议的难题，能够适应 IMS集群会议业务容量大规模扩展的技术要求。
需要说明的是， 本发明实施例中的方法可以软件功能模块的形式实现， 并且该软件功能模块作为独立的产品销售或使用时， 也可以存储在一个计算 机可读取存储介质中。 上述提到的存储介质可以是只读存储器， 磁盘或光盘 等。
本发明实施例中的各功能单元可以集成在一个处理模块中， 也可以是各 个单元单独物理存在， 也可以两个或两个以上单元集成在一个模块中。 上述 集成的模块既可以釆用硬件的形式实现， 也可以釆用软件功能模块的形式实 现。 所述集成的模块如果以软件功能模块的形式实现并作为独立的产品销售 或使用时， 也可以存储在一个计算机可读取存储介质中。 上述提到的存储介 质可以是只读存储器， 磁盘或光盘等。
以上对本发明实施例所提供的 IMS集群会议的创建和加入方法及分发系 统和全局会议管理器进行了详细介绍， 实施例的说明只是用于帮助理解本发 明的方法及其思想； 任何熟悉本技术领域的技术人员在本发明揭露的技术范 围内， 可轻易想到变化或替换， 都应涵盖在本发明的保护范围之内。

Claims

权 利 要求 书
1、 一种多媒体子系统 IMS集群会议的创建方法， 其特征在于， 包括： 接收会话初始化协议 SIP应用服务器发送的创建会议请求， 所述创建会议 请求携带用户侧要创建会议的信息；
根据所述要创建会议的信息， 为所述要创建会议分配一个全局唯一的会议 号， 并在全局会议索引表中保存该会议号；
向所述 SIP应用服务器返回创建会议请求响应， 所述创建响应携带为所述 要创建会议分配的所述全局唯一的会议号。
2、 根据权利要求 1所述的创建方法， 其特征在于， 进一步包括： 接收 SIP分发器或 SIP应用服务器发送的查询全局会议索引表倚求，所述的 查询请求中携带要加入会议的信息；
根据所述要加入会议的信息以及所述全局唯一的会议号获取会议部署所在 的 SIP应用服务器信息；
向所述 SIP分发器或 SIP应用服务器返回会议部署所在的 SIP应用服务器 信息，以便于所述的 SIP分发器或 SIP应用服务器向所述会议部署所在的 SIP应 用服务器发送加入会议信令。
3、 一种多媒体子系统 IMS集群会议的创建方法， 其特征在于， 包括： 会话初始化协议 SIP应用服务器向全局会议管理器发送创建会议请求， 所 述创建会议请求携带用户侧要创建会议的信息；
所述 SIP应用服务器接收全局会议管理器返回的为所述要创建会议分配的 一个全局唯一的会议号；
所述 SIP应用服务器在本地会议索引表中保存所述全局唯一的会议号。
4、 根据权利要求 3所述的创建方法， 其特征在于， 在向全局会议管理器发 送的创建会议请求之前， 所述方法包括：
所述 SIP应用服务器接收 SIP分发器路由分发的用户侧发起的创建会议信 令， 所述创建会议信令未携带要创建会议的信息；
所述 SIP应用服务器呼叫媒体服务器进行放音收号， 获取用户侧要创建会 议的信息。
5、 一种多媒体子系统 IMS集群会议的加入方法， 其特征在于， 包括： 接收用户侧发起的加入会议信令；
获取用户侧要加入会议的信息；
根据所述获取的用户侧要加入会议的信息向全局会议管理器查询全局会议 索引表， 获取会议部署所在的会话初始化协议 SIP应用服务器信息；
将所述加入会议信令路由分发至所述会议部署所在的 SIP应用服务器。
6、 根据权利要求 5所述的加入方法， 其特征在于， 由 SIP分发器接收所述 用户侧发起的加入会议信令； 如果所述用户侧发起的加入会议信令携带用户侧 要加入会议的信息；
则所述获取用户侧要加入会议的信息具体为： SIP分发器从所述用户侧发起 的加入会议信令获取所述的用户侧要加入会议的信息。
7、 根据权利要求 5所述的加入方法， 其特征在于， 由 SIP分发器接收所述 用户侧发起的加入会议信令； 如果所述加入会议信令未携带要加入会议的信息； 则所述获取用户侧要加入会议的信息具体包括：
所述的 SIP分发器路由分发所述用户侧发起的加入会议信令至任一 SIP应用 服务器；
所述 SIP分发器接收所述 SIP应用服务器发起的加入会议信令，所述应用服 务器发起的加入会议信令携带 SIP应用服务器通过呼叫媒体服务器进行放音收 号获取的用户侧要加入会议的信息。
8、 根据权利要求 7所述的加入方法， 其特征在于， 在 SIP分发器接收 SIP 应用服务器发起的加入会议信令之前， 所述方法还包括：
所述 SIP应用服务器通过呼叫媒体服务器进行放音收号获取用户侧要加入 会议的信息后， 查询本地会议索引表， 如果查询到该会议部署， 则所述 SIP应 用服务器创建会议呼叫将用户加入到会议中； 如果未查询到该会议部署， 则所 述 SIP应用服务器再向所述 SIP分发器发送所述加入会议信令。
9、 根据权利要求 5所述的加入方法， 其特征在于， 由 SIP应用服务器接收 SIP分发器分发的用户侧发起的加入会议信令；如果所述加入会议信令未携带要 加入会议的信息， 则所述获取要加入会议的信息具体包括：
所述 SIP应用服务器通过呼叫媒体服务器进行放音收号获取用户侧要加入 会议的信息；
所述根据所述获取的用户侧要加入会议的信息向全局会议管理器查询全局 会议索引表， 获取会议部署所在的会话初始化协议 SIP应用服务器信息具体为： 所述 SIP应用服务器根据所述获取的用户侧要加入会议的信息向全局会议管理 器查询全局会议索引表， 获取会议部署所在的会话初始化协议 SIP应用服务器 信息；
所述将所述加入会议信令路由分发至所述会议部署所在的 SIP应用服务器 具体为： 所述 SIP应用服务器将所述加入会议信令路由分发至所述会议部署所 在的 SIP应用服务器。
10、 根据权利要求 9所述的加入方法， 其特征在于， 所述 SIP应用服务器 在根据所述获取的用户侧要加入会议的信息向全局会议管理器查询全局会议索 引表之前进一步包括：
所述 SIP应用服务器根据放音收号获取的用户侧要加入会议的信息， 查询 本地会议索引表， 如果查询到该会议部署， 则所述 SIP应用服务器创建会议呼 叫将用户加入到会议中； 如杲未查询到该会议部署， 则所述 SIP应用服务器再 根据所述获取的用户侧要加入会议的信息向全局会议管理器查询全局会议索引 表。
11、 一种多媒体子系统 IMS集群^义的分发系统， 其特征在于， 包括： SIP分发器，用于接收加入会议信令； 根据用户侧要加入会议的信息向全局 会议管理器查询全局会议索引表， 获取会议部署所在的 SIP应用服务器信息； 将所述加入会议信令路由分发至所述会议部署所在的 SIP应用服务器； 全局会议管理器， 用于为所述要创建会议分配一个全局唯一的会议号， 并 在全局会议索引表中保存该会议号； 以及用于根据要加入会议的信息查询会议 部署所在的 SIP应用服务器信息。
12、 根据权利要求 11所述的分发系统， 其特征在于， 所述全局会议管理器 与所述 SIP 分发器合设。
13、 根据权利要求 11所述的分发系统， 其特征在于， 所述分发系统进一步 包括： SIP应用服务器， 用于当所述加入会议信令未携带要加入会议的信息时， 接收 SIP 分发器路由分发的加入会议信令； 通过呼叫媒体服务器进行放音收号 获取所述用户侧要加入会议的信息； 向所述 SIP分发器发送携带所述获取的用 户侧要加入会议的信息的加入会议信令。
所述 SIP分发器， 进一步用于根据接收到的所述 SIP应用服务器发起的加 入会议信令获取用户侧要加入会议的信息。
14、 根据权利要求 11所述的分发系统， 其特征在于， 所述分发系统进一步 包括： SIP应用服务器， 用于当所述加入会议信令未携带要加入会议的信息时， 接收 SIP 分发器路由分发的加入会议信令； 通过呼叫媒体服务器进行放音收号 获取所述用户侧要加入会议的信息； 根据所述获取的用户侧要加入会议的信息 向全局会议管理器查询全局会议索引表， 获取会议部署所在的会话初始化协议
SIP应用服务器信息； 将所述加入会议信令路由分发至所述会议部署所在的 SIP 应用服务器。
15、 根据权利要求 13或 14所述的分发系统， 其特征在于， 所述分发系统 进一步包括媒体服务器， 用于接收 SIP应用服务器的呼叫， 根据所述呼叫进行 放音收号以获取所述用户侧要加入会议的信息， 并向所述 SIP应用服务器提供 所获取的用户侧要加入会议的信息。
16、 一种全局会议管理器， 其特征在于， 包括：
会议号分配单元， 用于根据要创建会议的信息， 为所述要创建会议分配一 个全局唯一的会议号；
会议部署查询单元， 用于根据要加入会议的信息查询会议部署所在的会话 初始化协议 SIP应用服务器信息；
全局会议索引单元， 用于维护会议号分配单元分配的会议号和为会议部署 查询单元提供会议部署的查询。
17、 根据权利要求 16所述全局会议管理器， 其特征在于， 还包括： 创建会议请求接收单元， 用于接收创建会议请求， 所述创建请求携带用户 侧要创建会议的信息； 以及，
查询会议部署请求接收单元， 用于接收查询会议部署请求， 所述查询请求 携带用户侧要加入会议的信息。
PCT/CN2009/073279 2008-12-31 2009-08-17 Ims集群会议的创建和加入方法、装置及系统 WO2010075688A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200810186860.3A CN101772195B (zh) 2008-12-31 2008-12-31 Ims集群会议的创建和加入方法及分发系统和装置
CN200810186860.3 2008-12-31

Publications (1)

Publication Number Publication Date
WO2010075688A1 true WO2010075688A1 (zh) 2010-07-08

Family

ID=42309780

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/073279 WO2010075688A1 (zh) 2008-12-31 2009-08-17 Ims集群会议的创建和加入方法、装置及系统

Country Status (2)

Country Link
CN (1) CN101772195B (zh)
WO (1) WO2010075688A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102724047B (zh) * 2011-03-30 2015-08-12 中兴通讯股份有限公司 一种进行多媒体会议的方法及系统
CN103686618B (zh) * 2012-09-11 2017-04-05 普天信息技术研究院有限公司 一种触发建立宽带多媒体集群业务的方法
ES2560409T3 (es) * 2012-09-20 2016-02-18 Huawei Technologies Co., Ltd. Método, dispositivo y sistema de acceso a una conferencia

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101018168A (zh) * 2006-02-06 2007-08-15 华为技术有限公司 Ip多媒体系统业务的承载方法及其系统
CN101047534A (zh) * 2007-04-09 2007-10-03 华为技术有限公司 用户主动加入会议的方法、装置及系统
WO2008118334A1 (en) * 2007-03-27 2008-10-02 Lucent Technologies Inc. Ims networks providing business-related content to wireless devices

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101018168A (zh) * 2006-02-06 2007-08-15 华为技术有限公司 Ip多媒体系统业务的承载方法及其系统
WO2008118334A1 (en) * 2007-03-27 2008-10-02 Lucent Technologies Inc. Ims networks providing business-related content to wireless devices
CN101047534A (zh) * 2007-04-09 2007-10-03 华为技术有限公司 用户主动加入会议的方法、装置及系统

Also Published As

Publication number Publication date
CN101772195B (zh) 2014-05-07
CN101772195A (zh) 2010-07-07

Similar Documents

Publication Publication Date Title
KR101503569B1 (ko) 가입자 장치의 전역 고유 식별자의 생성
RU2528616C1 (ru) Шлюз сетевого обобщения и соответствующий способ обобщения оконечной точки
JP4116616B2 (ja) Ｓｉｐプロトコルを使用するイベントの予約購読方法及びシステム
CN101103609B (zh) 用于处理紧急呼叫的方法及装置
CN101420432B (zh) 一种ims监听的实现方法、系统及装置
US8195147B2 (en) Method of enabling a combinational service and communication network implementing the service
EP1757142B1 (en) Session establishment for real-time media communication service
CN103379096B (zh) 因特网与运营商网络业务共享方法、服务方及网页网关
EP1914973B1 (en) System and method to provide combinational services to anonymous callers
WO2013189338A2 (zh) 实现会话发起协议多业务服务器分发的方法、装置及系统
WO2009010017A1 (en) The implementing method and system for ue redirection service of sharing pui
CN101018238B (zh) 用户标识系统及注册、业务和路由配置方法
CN101291235A (zh) 与支持多种消息业务的用户通信的方法及系统
WO2010075688A1 (zh) Ims集群会议的创建和加入方法、装置及系统
KR100727069B1 (ko) Ｓｉｐ 기반의 무선 패킷 교환망 시스템에서의 타망 연동방법 및 그 시스템
WO2017113071A1 (zh) 一种补充业务实现方法、终端设备和ims服务器
CN114679432B (zh) 一种有害电话防范设备和方法
CN119182758A (zh) 媒体通信方法、装置、产品及电子设备
KR100706339B1 (ko) Ｓｉｐ 기반의 무선 패킷 교환망 시스템에서의 타망 연동방법 및 그 시스템
CN101009664B (zh) 一种处理会话初始化协议消息中内容的方法及网络实体
KR20070045426A (ko) Ｓｉｐ 기반의 무선 패킷 교환망 시스템에서의 타망 연동방법 및 그 시스템
KR100757535B1 (ko) 어플리케이션 구분이 가능한 멀티미디어 서비스 방법 및장치
WO2006032204A1 (en) A method for enabling communication in the application servers

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: 09835975

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09835975

Country of ref document: EP

Kind code of ref document: A1