EP2086199B1 - Procédé et appareil pour configurer une connexion de conférence audio - Google Patents

Procédé et appareil pour configurer une connexion de conférence audio Download PDF

Info

Publication number
EP2086199B1
EP2086199B1 EP08163755A EP08163755A EP2086199B1 EP 2086199 B1 EP2086199 B1 EP 2086199B1 EP 08163755 A EP08163755 A EP 08163755A EP 08163755 A EP08163755 A EP 08163755A EP 2086199 B1 EP2086199 B1 EP 2086199B1
Authority
EP
European Patent Office
Prior art keywords
conference
terminal
leaf node
root node
node
Prior art date
Legal status (The legal status 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 status listed.)
Not-in-force
Application number
EP08163755A
Other languages
German (de)
English (en)
Other versions
EP2086199A1 (fr
Inventor
Feng Huawei Administration Building Cha
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of EP2086199A1 publication Critical patent/EP2086199A1/fr
Application granted granted Critical
Publication of EP2086199B1 publication Critical patent/EP2086199B1/fr
Not-in-force legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H04L65/403—Arrangements for multi-party communication, e.g. for conferences
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]

Definitions

  • the present invention relates to the field of communication technologies, and in particular, to a method and an apparatus for setting up an audio conference connection.
  • Audio conference is also known as teleconference. It is an important prevalent service in the Next Generation Network (NGN) and the IP Multimedia Subsystem (IMS).
  • NTN Next Generation Network
  • IMS IP Multimedia Subsystem
  • the audio conference system is primarily constructed on an IP MS.
  • an audio conference system under the Session Initiation Protocol (SIP) includes a Media Server (MS) 101 and a SIP Application Server (AS) 102.
  • the SIP AS102 is adapted to control the User Equipment (UE) 103 and the MS101, execute the conference logics and construct the conference signaling, maintain the resources on the MS101, and allocate resources for the calls.
  • SIP Session Initiation Protocol
  • UE User Equipment
  • the UE involved in the conference originates a call to the SIP AS102 through the gateway 104, and the SIP AS102 originates a call to the MS101 to create an audio conference.
  • the SIP AS102 can originate a conference actively.
  • a common method of setting up an audio conference connection in the system shown in Figure 1 is described below, supposing that the SIP AS originates the conference.
  • the SIP AS102 sends an INVITE (SIP call origination) message to the UE103.
  • INVITE SIP call origination
  • the UE 103 After going off-hook or picking up the phone, the UE 103 returns a 200 OK (acknowledgement) message to the SIP AS102, with the Session Description Protocol (SDP) information of the UE103 carried in the message.
  • SDP Session Description Protocol
  • the SDP information includes the IP address for receiving the audio packet, the port ID and the type of the processing media.
  • the SIP AS102 sends an INVITE message to the MS101, with the SDP information of the UE103 carried in the message.
  • the MS101 can create a conference terminal for receiving and transmitting data according to the SDP information of the UE103, and allocate an IP port for receiving and another IP port for transmitting data, to the conference terminal.
  • the conference terminal can be regarded as an entity for transmitting data between the audio processors located on the UE103 and the MS101.
  • the MS101 After creating the conference terminal of the UE103, the MS101 sends a 200 OK message to the UE103 through SIP AS102, with the SDP information of the conference terminal carried in the message. After the UE103 and the corresponding conference terminal on the MS101 know the relevant information about the peer such as IP address and port ID of the peer, the UE103 and the MS101 can transmit data in between according to the peer SDP information.
  • audio conference can be implemented on only one MS. Namely, no matter how many UEs are involved in the audio conference, all UEs of the conference are connected to only one MS, which requires the MS to have enough resources for supporting the whole conference.
  • a general commercial MS has limited quantity of audio conference ports. When the operation is busy, one MS tends to operate multiple conferences, which occupy plenty of resources. Therefore, if the quantity of attendees of a conference goes far beyond the capacity of a single MS, it is impossible to create a conference with enough resources on the MS, and the conference has to be cancelled or the number of attendees has to be reduced. Consequently, the conference service is affected.
  • the embodiments of the present invention provide a method and an apparatus for setting up audio conference connections, so as to create a large audio conference through multiple concatenated MSs.
  • a method for setting up audio conference connections provided in an embodiment of the present invention according to claim 1 includes:
  • the present invention also discloses an apparatus for setting up an audio conference connection, including:
  • the embodiments of the present invention can concatenate multiple MSs to implement functions of a large conference without limiting the UE quantity in the case that a single MS is not enough, thus solving the inability of convening large conferences reliably in the prior art for deficiency of MSs in the operation environment.
  • the user can operate the conference on a large integrated virtual MS regardless of the conference size and the quantity of MSs on which the conference is distributed.
  • the operators can deploy the MSs of a proper quantity according to the scale of the concurrent users.
  • the existing MSs can be integrated into the technical solution under the present invention regardless of the manufacturer, only if they provide standard interfaces and capacity parameters.
  • Figure 1 shows an exemplary architecture of an audio conference system in the prior art.
  • Figure 2 shows an exemplary architecture of a concatenated audio conference system according to an embodiment of the present invention.
  • Figure 3 is an exemplary flowchart of a method for setting up a concatenated audio conference between MSs according to an embodiment of the present invention.
  • Figure 4 is an exemplary flowchart of a method for setting up an audio conference connection between a UE with an MS according to an embodiment of the present invention.
  • Figure 5 shows an exemplary flowchart of a dynamic concatenation method according to an embodiment of the present invention.
  • Figure 6 is an exemplary flowchart of a method for switching the UE from the mute state to the speaking state according to an embodiment of the present invention.
  • Figure 7 shows an exemplary architecture of an apparatus for setting up an audio conference connection according to an embodiment of the present invention.
  • Figure 8 shows an exemplary architecture of an MS unit in the apparatus shown in Figure 7 according to an embodiment of the present invention.
  • Figure 9 shows an exemplary architecture of another MS unit in the apparatus shown in Figure 7 according to an embodiment of the present invention.
  • Figure 10 shows an exemplary architecture of another apparatus for setting up an audio conference connection according to an embodiment of the present invention.
  • a SIP AS performs uniform management on all MSs in the system, and is responsible for allocating resources to such MSs.
  • the MSs may involve different manufacturers.
  • the SIP AS can make two or more MSs into a tree topology. One of the MSs serves as a root node MS, and the remaining MSs serve as leaf node MSs in the conference of a tree structure.
  • the SIP AS allocates the UEs onto leaf node MSs or the root node MS, sets up a connection between every UE with the MS that serves that the UE and sets up a connection between every leaf node MS and the root node MS, thus accomplishing connections between all UEs.
  • the audio conference connected through a tree structure may be called a "concatenated audio conference" hereinafter.
  • FIG 2 shows an exemplary architecture of a concatenated audio conference system according to an embodiment of the present invention.
  • the SIP AS102 will allocate multiple MSs to the audio conference, for example, MS0 to MSn in Figure 1 , according to the size of the audio conference and the resource capacity on each MS.
  • the MS0 is a root node, and a total of M0 UEs are allocated to the MS0. Therefore, M0 conference terminals are allocated on MS0. Meanwhile, n conference terminals are allocated on the MS0, corresponding to the leaf nodes MS1 to MSn. In this way, the MS0 occupies at least "M0 + n" conference terminals.
  • the SIP AS allocates M1 conference terminals corresponding to the UEs, and allocates one conference terminal for accessing the root node MS0.
  • Other leaf nodes are similar.
  • M0 and n are respectively natural number
  • each leaf node MS in the conference needs to be connected with the root node MS0, and the UE allocated onto each MS needs to be connected with the MS that serves the UE.
  • Figure 3 is the flowchart of a method for setting up a concatenated audio conference between a root node and leaf nodes according to an embodiment of the present invention.
  • the method for setting up a concatenated audio conference between a leaf node MS1 and a root node MS0 showed in the system shown in Figure 2 includes the steps hereinafter.
  • S301 The SIP AS in the system sends an INVITE message to the root node MS0.
  • the MS0 After receiving the INVITE message, the MS0 creates a conference terminal T0, and allocates an IP port for receiving and another IP port for sending audio packets, to the conference terminal T0. Then the MS0 returns a 200 OK message to the SIP AS.
  • the 200 OK message carries the SDP 0 information of the conference terminal T0.
  • the SDP 0 information includes: IP address and port ID of the conference terminal T0 for receiving the audio packets, and type of media for processing.
  • the SIP AS sends an INVITE message to the leaf node MS1.
  • the INVITE message carries the SDP 0 information of the conference terminal T0.
  • the MS1 After receiving the INVITE message in the S303, the MS1 creates a conference terminal T I, and allocates an IP port for of receiving and another IP port for sending audio packets, to the conference terminal T1. Then the MS1 returns a 200 OK message to the SIP AS.
  • the 200 OK message carries the SDP 1 information of the conference terminal T1.
  • the SDP 1 information includes: IP address and port ID of the conference terminal T1 for receiving the audio packets, and type of media for processing.
  • S305 The SIP AS sends the SDP 1 information to the MS0 through an ACK (acknowledgement) message, notifying the MS0 of the information about the conference terminal allocated to the MS1.
  • ACK acknowledgement
  • the two conference terminals T0 and T1 know the SDP information of each other, and can transmit data according to the SDP information of each other in the subsequent communication.
  • S306 The SIP AS sends a SIP INFO (SIP media processing control language) message to the MS0, instructing the MS0 to create a master conference and add the conference terminal T0 into the created master conference.
  • SIP INFO SIP media processing control language
  • S307 The SIP AS sends a SIP INFO message to the MS1, instructing the MS1 to create a slave conference and add the conference terminal T1 into the created slave conference.
  • the method for creating a concatenated conference between other leaf nodes and the root node MS0 is similar and not repeated here any further.
  • FIG. 4 is an example flowchart of a method for setting up an audio conference connection between a UE with an MS according to an embodiment of the present invention. The method includes the steps hereinafter.
  • the SIP AS sends an INVITE message to the UE.
  • the SDP information includes: IP address and port ID of the UE for receiving audio packets, and type of media for processing.
  • the SIP AS sends an INVITE message to the MS.
  • the INVITE message carries the SDP information of the UE.
  • the MS After receiving the INVITE message, the MS creates a conference terminal T0, and allocates an IP port for receiving and another IP port for sending audio packets, to the conference terminal T0. Then the MS returns a 200 OK message to the SIP AS.
  • the 200 OK message carries the SDP 0 information of the conference terminal T0.
  • the SDP 0 information includes: IP address and port ID of the conference terminal T0 for receiving the audio packets, and type of media for processing.
  • the SIP AS sends an ACK message that carries the SDP 0 information of T0 to the UE, notifying the UE of the information about the conference terminal T0 on the MS. In this way, the UE and the conference terminal know the SDP information of each other, and hence can communicate with each other according to the SDP information.
  • the SIP AS sends a SIP INFO message to the MS, instructing the MS to add the conference terminal T0 into the corresponding master conference and slave conference. In this way, the UE connected with the conference terminal T0 is connected into the conference.
  • step 406 if no master or slave conference is created on the MS, the SIP AS sends a SIP INFO message to the MS, instructing the MS to create a master or slave conference and add the conference terminal T0 into the created conference.
  • SIP AS sends a first SIP INFO message for creating a master or slave conference first, instructing the MS to create a master or slave conference; and then sends a second SIP INFO message for joining the master or slave conference, instructing the MS to add the conference terminal T0 into the created conference.
  • the master conference is the conference which is initiated on a main media server at very first; the slave conference is established on a new media server when resources of the main media server turn short.
  • An application server can control the slave conferences to add them into the master conference, which makes a large-scale conference.
  • the SIP AS can distribute the UEs involved in the audio conference onto different MSs, connect the UEs on each MS with the MS in the way shown in Figure 4 , and concatenate the all leaf node MSs with the root node MS in the way shown in Figure 3 , thus adding all members into the audio conference.
  • the quantity of MSs allocated depends on the quantity of UEs involved in the conference and the quantity of ports available from each MS.
  • a master conference is created on the root node MS, and a slave conference is created on each leaf node MS.
  • the SIP AS needs to not only allocate a conference terminal to the UE, but also allocate a conference terminal to the upper-level root node MS for joining the master conference of the root node MS.
  • the SIP AS needs to not only allocate a conference terminal to the UE involved in the master conference, but also allocate a conference terminal to each leaf node involved in the master conference to ensure communication with each leaf node.
  • the root node MS is instructed to create a conference terminal through S301, and then in S303, the leaf node MS is instructed to create a conference terminal associated with the conference terminal of the root node MS, thus setting up a connection between the root node MS and the leaf node MS.
  • the method for setting up a connection between the root node MS and the leaf node MS may be: in S301', instructing the leaf node MS to create a conference terminal, and then in S302', sending the SDP information about the conference terminal created by the leaf node MS to the SIP AS through a 200 OK message; finally in S303', instructing the root node MS to create a conference terminal associated with the conference terminal on the leaf node MS.
  • the previous embodiment is briefly known as static concatenation creation mode; namely, the UEs involved in the conference are constant. Therefore, an audio conference of the corresponding size can be created according to the quantity of UEs involved in the conference. Nevertheless, in the actual conference process, it is a dynamic mode alternatively. That is, if a new member wants to join the conference, the SIP AS will calculate out whether the MS involved in the conference has additional resources for creating a conference terminal. If additional resources are available, the SIP AS will allocate a conference terminal to the new UE on the MS with resources in the way shown in Figure 4 , and then add the conference terminal into the conference on the MS.
  • the SIP AS will allocate a leaf node MS to the conference, and connect the new UEs with the newly allocated leaf node MS; and connect the newly allocated leaf node MS with the root node MS.
  • the method for connecting the UE with the newly allocated leaf node MS is similar to the embodiment shown in Figure 4
  • the method for connecting the newly allocated leaf node MS with the root node MS is similar to the embodiment shown in Figure 3 .
  • the SIP AS calculates and determines that the conference in the root node MS has no resource for adding the newly allocated leaf node MS
  • the SIP AS will divert a UE in the root node MS from the master conference to the slave conference before connecting the newly allocated leaf node MS to the root node.
  • a conference terminal associated with the UE is spared for concatenation with the new MS.
  • the SIP AS connects the new MS with the root node MS of the conference to add the new UE.
  • the method for adding new UEs into an existing concatenated audio conference is called “dynamic concatenation”
  • the conference connected in this method is called a "dynamic concatenation conference".
  • Figure 5 shows an example flowchart of a dynamic concatenation method according to an embodiment of the present invention. If the conference in the MS has deficient resources for adding the new user equipment U1, and the embodiment includes the steps hereinafter.
  • the SIP AS selects a user equipment U0 on the root node MS0, and obtains a conference terminal T0 corresponding to the user equipment U0 according to the corresponding relationship between the UE maintained by the SIP AS and the conference terminal on the MS0.
  • the SIP AS can choose the UE in the mute state as the U0 preferably.
  • the "mute" means that it is forbidden to be heard from.
  • the SIP AS allocates a new leaf node MS1 to the conference, and sends the SDP 0 information of the conference terminal T0 on the MS0 to the MS1 through an INVITE message.
  • the MS1 After receiving the INVITE message, the MS1 creates a conference terminal T1, and allocates an IP port for the purposes of receiving and another IP port for sending audio packets, to the conference terminal T1. Then the MS I returns a 200 OK message to the SIP AS.
  • the 200 OK message carries the SDP 1 information of the conference terminal T1.
  • the SDP 1 information includes: IP address and port ID of the conference terminal T1 for receiving the audio packets, and type of media for processing.
  • S504 The SIP AS sends a RE-INVITE message to the MS0, with the SDP 0 information of the conference terminal T1 carried in the message.
  • the MS 0 returns a 200 OK message to the SIP AS after receiving the RE-INVITE message.
  • the 200 OK message carries the SDP 0 information of the conference terminal T0.
  • the SIP AS sends a SIP INFO message to the MS, instructing the MS1 to create a slave conference and add the conference terminal T1 into the created slave conference.
  • S507 The SIP AS sends an INVITE message to the MS1, with the SDP information of the user equipment U0 carried in the message.
  • the MS1 After receiving the INVITE message in the S507, the MS1 creates a conference terminal T2, and sends the SDP 2 information of the conference terminal T2 to the SIP AS through a 200 OK message.
  • the SIP AS After receiving the 200 OK message, the SIP AS sends a RE-INVITE message to the U0, with the SDP 2 information of the conference terminal T2 carried in the message.
  • S510 The SIP AS sends a SIP INFO message to the MS, instructing the MS1 to add the conference terminal T2 into the created slave conference.
  • the SIP AS may send a BYE (terminate call) message to the MS0, instructing the MS0 to release the conference terminal T0.
  • the SIP AS may send an INVITE message to the MS0 instead of the RE-INVITE message in S504, instructing the MS0 to create another conference terminal; and in S505, the 200 OK message returned to the SIP AS carries the SDP information of the newly created conference terminal.
  • the INVITE message in S504 carries the SDP 1 information of the T1 allocated by the MS1.
  • the SIP AS can switch the UE in the root node MS to the leaf node in order to release a certain amount of resources for connecting the new leaf node MS, and then add the new member UE into the conference through a new leaf node MS.
  • the conference size is expanded by adding new leaf node MSs.
  • the SIP AS may not only send a SIP INFO message to the MS1 for creating and joining a slave conference, but also send a SIP INFO message to the MS0 for canceling the mute state of the user equipment U0.
  • the UE on the leaf node MS may be mute, and the speaking UE may be distributed on the root node MS, so as to avoid echo of the conference. Therefore, if a UE on the leaf node needs to speak, the UE must exit the slave conference on the leaf node MS and join the master conference on the root node MS.
  • Figure 6 is an example flowchart of a method for switching the UE from the mute state to the speaking state according to an embodiment of the present invention. In this embodiment, when the user equipment U1 on the leaf node MS1 is to be added to the root node MS0 for the purpose of speaking, the process of adding hereinafter occurs.
  • the SIP AS sends a BYE message to the leaf node MS1, instructing the MS1 to release the resources of the conference terminal T1 for communication with the user equipment U1.
  • the SIP AS sends an INVITE message to the root node MS0.
  • the INVITE message carries the SDP 1 information of the user equipment U1.
  • the MS0 After receiving the INVITE message, the MS0 creates a conference terminal T0, and allocates an IP port for receiving and another IP port for sending audio packets, to the conference terminal T0. Then the MS0 returns a 200 OK message to the SIP AS.
  • the 200 OK message carries the SDP 0 information of the conference terminal T0.
  • the SDP 0 information includes: IP address and port ID of the conference terminal T0 for receiving the audio packets, and type of media for processing.
  • S604 The SIP AS sends a RE-INVITE message to the user equipment U1, with the SDP 0 information of the conference terminal T0 carried in the message.
  • the U1 returns a 200 OK message to the SIP AS after receiving the RE-INVITE message.
  • the 200 OK message carries the SDP 1 information of the user equipment U1.
  • the SIP AS sends a SIP INFO message to the MS0, instructing the MS0 to add the conference terminal T0 into the master conference.
  • the previous embodiment is applicable to the circumstance that the resources on the root node MS0 are enough for adding a user equipment U1 into the conference.
  • the SIP AS can take the steps shown in Figure 5 after performing S601 to add the UE into the master conference on the root node MS0.
  • the sound (such as mute) can be set through a SIP INFO message.
  • the sound can be controlled through an INVITE message or a RE-INVITE message sent by the SIP AS.
  • the sound state can be set by changing the SDP information parameter in the INVITE or RE-INVITE message.
  • the above examples for exemplary purposes only, and the actual settings are not limited to them.
  • the "mute” means that it is forbidden to be heard from; the "dumb” means that it is forbidden to send a sound.
  • the previous embodiments illustrate an implementation method under the SIP protocol, and the present invention are not limited to such embodiments.
  • the method can be implemented under MGCP protocol. If the MGCP protocol is applied, the differences from the previous SIP-based implementation are: In the MGCP protocol, the AS instructs the MS to create a conference terminal by sending a CRCX message in place of the INVITE message in the previous embodiment; when creating the first conference terminal for the conference, the conference ID is not generated by the AS, but is generated by the MS when the MS creates a conference terminal; the conference ID generated is notified to the AS through a 200 OK message, so that the AS can notify the conference ID to the MS through a CRCX message when the AS instructs the MS to create another conference terminal again in the future.
  • the AS when the AS instructs the MS to add a conference terminal into a conference or set the sound state of the MS and the UE, the AS sends a MDCX message under the MGCP protocol in place of the SIP INFO message in the previous embodiment.
  • the AS instructs the MS to release resources, the AS under the MGCP protocol sends a DLCX message in place of the BYE message in the previous embodiment.
  • the embodiments of the present invention concatenate multiple MSs into a tree topology structure to form a master-slave conference and implement functions of a large conference without limiting the UE quantity in the case that a single MS is not enough, thus solving the inability of convening large conferences reliably in the prior art for deficiency of MSs in the operation environment.
  • the user can operate the conference on a large integrated virtual MS regardless of the conference size and the quantity of MSs on which the conference is distributed.
  • the operators can deploy the MSs of a proper quantity according to the scale of the concurrent users.
  • the existing MSs can be integrated into the technical solution under the present invention regardless of the manufacturer, only if they provide standard interfaces and capacity parameters. This also slashes the equipment cost greatly.
  • an apparatus for setting up audio conference connections is disclosed according to some embodiments of the present invention.
  • the apparatus can be integrated onto an application server such as SIP AS.
  • an application server such as SIP AS.
  • two or more MSs can be concatenated according to the quantity of UEs involved in the audio conference, so that all UEs that need to join the conference can be added into the conference.
  • Figure 7 shows the structure of an apparatus for setting up an audio conference connection.
  • the apparatus includes:
  • the process of creating an associated conference terminal on the root node MS and the leaf node MS respectively may be embodied as different modes: one of the modes, instructing the leaf node MS to create a conference terminal associated with the conference terminal on the root node MS, or further instructing the root node MS to create a conference terminal associated with the conference terminal on the leaf node.
  • the apparatuses corresponding to those two modes are described below with reference to accompanying drawings.
  • FIG 8 shows an example structure of an MS connecting unit 703 according to an embodiment of the present invention, wherein the MS connecting unit 703 may instruct the leaf node MS to create a conference terminal T1 associated with the conference terminal T0 on the root node MS.
  • the MS connecting unit 703 includes: a root node conference terminal sub-unit 7031, and a first MS connecting sub-unit 7032, wherein:
  • FIG 9 shows another structure of an MS connecting unit 703 shown in Figure 7 , wherein the MS connecting unit 703 may instruct the root node MS to create a conference terminal T0 associated with the conference terminal T1 on the leaf node MS.
  • the MS connecting unit 703 includes: a leaf node conference terminal sub-unit 7033, and a second MS connecting sub-unit 7034, wherein:
  • the apparatus will calculate out whether the MS involved in the conference has additional resources for creating a conference terminal. If additional resources are available, the UE connecting unit 702 of this apparatus will allocate a conference terminal to the new UE on the MS with available resources to connect the new UE with the MS that serves the conference.
  • FIG. 10 shows the architecture of another apparatus for setting up an audio conference connection according to an embodiment of the present invention.
  • this apparatus can include:
  • the conference creating unit 1001 can send a SIP INFO message to the root node MS, instructing the root node MS to create a master conference and add the conference terminal on the root node MS into the created master conference.
  • the conference creating unit 1001 can send a SIP INFO message to the leaf node MS, instructing the leaf node MS to create a slave conference and add the conference terminal on the leaf node MS into the created slave conference.
  • the conference creating unit 1001 and the conference adding unit 1002 shown in Figure 10 are applied not only to the apparatus shown in Figure 7 , but also to the apparatus shown in Figure 8 or Figure 9 , with the connection relations being the same as that shown in Figure 10 .
  • the apparatuses described above are for illustration only.
  • the unit described above as a separate component may be or may not be physically separated; the component displayed as a unit may be or may not be a physical unit; the components can be located in a place or distributed onto multiple network units.
  • the users can select part or all of the modules according to their own needs to fulfill the purposes of the embodiments of the present invention. Ordinary technicians in this field can understand and implement the technical solutions without making any creative effort.
  • the software is stored in a storage medium (for example, ROM/RAM, disk, and CD) and incorporates several instructions to instruct a computer device (for example, PC, server, or network device) to execute the method provided in the embodiments of the present invention.
  • a storage medium for example, ROM/RAM, disk, and CD
  • a computer device for example, PC, server, or network device

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Interconnected Communication Systems, Intercoms, And Interphones (AREA)
  • Sub-Exchange Stations And Push- Button Telephones (AREA)

Claims (12)

  1. Procédé pour établir une communication de conférence audio, comprenant les étapes consistant à :
    allouer, par l'intermédiaire d'une unité d'allocation (701), au moins deux serveurs de média, SM, en fonction de la quantité de terminaux impliqués dans une conférence audio ;
    sélectionner, par l'intermédiaire de l'unité d'allocation (701), un SM parmi les au moins deux SM comme SM de noeud racine, et le/les SM restant(s) comme SM de noeud feuille ;
    établir (301~305), par l'intermédiaire d'une unité de communication de terminal (702), une communication entre le SM de noeud racine et le/les SM de noeud feuille ; et
    établir (401~406), par l'intermédiaire d'une unité de communication de SM (703), une communication entre un terminal et le SM desservi pour le terminal ;
    caractérisé en ce que le procédé d'établissement, par l'intermédiaire de l'unité de communication de SM, d'une communication entre un terminal et le SM desservi pour le terminal comprend en outre les étapes consistant à :
    allouer les terminaux prêts à parler au SM de noeud racine ; et
    allouer les autres terminaux non prêts à parler au SM de noeud feuille.
  2. Procédé selon la revendication 1, caractérisé en ce que le procédé d'établissement d'une communication entre le SM de noeud racine et le/les SM de noeud feuille comprend en outre les étapes consistant à :
    établir les terminaux de conférence dans le SM de noeud racine, où la quantité des terminaux de conférence dans le SM de noeud racine est la même que celle du/des SM de noeud feuille, et chaque terminal de conférence dans le SM de noeud racine communique respectivement avec un SM de noeud feuille (301~302) ;
    notifier des informations de protocole de description de session du terminal de conférence dans le SM de noeud racine au SM de noeud feuille correspondant (303), respectivement ;
    établir un terminal de conférence dans chacun des SM de noeud feuille, où le terminal de conférence dans chacun des SM de noeud feuille communique respectivement avec le terminal de conférence correspondant dans le SM de noeud racine (304) ;
    notifier des informations de protocole de description de session du terminal de conférence dans chacun des SM de noeud feuille au SM de noeud racine (305) ; où les informations de protocole de description de session comprennent une adresse IP, une quantité de ports et un type pour traiter le média, pour recevoir les paquets de données audio par les terminaux de conférence.
  3. Procédé selon la revendication 1, caractérisé en ce que le procédé d'établissement d'une communication entre le SM de noeud racine et le/les SM de noeud feuille comprend en outre les étapes consistant à :
    établir un terminal de conférence dans chacun des SM de noeud feuille, où le terminal de conférence dans chacun des SM de noeud feuille communique respectivement avec le SM de noeud racine (301') ;
    notifier des informations de protocole de description de session des terminaux de conférence dans le/les SM de noeud feuille au SM de noeud racine (302') ;
    établir des terminaux de conférence dans le SM de noeud racine, où les terminaux de conférence dans le SM de noeud racine communiquent respectivement avec les terminaux de conférence correspondants dans le/les SM de noeud feuille (303') ;
    notifier des informations de protocole de description de session des terminaux de conférence dans le SM de noeud racine au SM de noeud feuille correspondant (305) ; où les informations de protocole de description de session comprennent une adresse IP, une quantité de ports et un type pour traiter le média, pour recevoir les paquets de données audio par les terminaux de conférence.
  4. Procédé selon l'une quelconque des revendications 1 à 3, caractérisé en ce qu'il comprend en outre les étapes consistant à :
    établir une conférence principale de la conférence audio sur le SM de noeud racine et
    une conférence esclave de la conférence audio sur chaque SM de noeud feuille (306, 307) ;
    permettre aux terminaux de conférence du SM de noeud racine de rejoindre la conférence principale (306) ; et
    permettre à chaque terminal de conférence du/des SM de noeud feuille de rejoindre la conférence esclave du SM de noeud feuille correspondant (307).
  5. Procédé selon l'une quelconque des revendications 1 à 4, caractérisé en ce qu'il comprend en outre les étapes consistant à :
    déterminer si le SM de noeud racine dispose des ressources pour communiquer avec un nouveau SM de noeud feuille lorsqu'un nouveau terminal rejoint la conférence audio ;
    établir la communication entre le nouveau SM de noeud feuille et le SM de noeud racine si le SM de noeud racine dispose des ressources requises ; et
    établir la communication entre le nouveau terminal et le nouveau SM de noeud feuille.
  6. Procédé selon la revendication 5, caractérisé en ce qu'il comprend en outre les étapes consistant à :
    transférer un terminal du SM de noeud racine de la conférence principale sur le SM de noeud racine vers la conférence esclave sur un SM de noeud feuille, lorsque le SM de noeud racine ne dispose pas des ressources requises, de manière à préserver les ressources ;
    établir une communication entre un nouveau SM de noeud feuille et le SM de noeud racine en utilisant les ressources préservées ; et
    établir une communication entre un nouveau terminal et le nouveau SM de noeud feuille.
  7. Procédé selon la revendication 4, dans lequel si un terminal sur le noeud feuille a besoin de parler, le terminal quitte la conférence esclave sur le SM de noeud feuille et rejoint la conférence principale sur le SM de noeud racine.
  8. Appareil pour établir une communication de conférence audio, où l'appareil comprend :
    une unité d'allocation (701), adaptée pour allouer au moins deux serveurs de média, SM, en fonction de la quantité de terminaux impliqués dans une conférence audio, et
    sélectionner un SM parmi les au moins deux SM comme SM de noeud racine, et le/les SM restant(s) comme SM de noeud feuille ;
    une unité de communication de terminal (702), adaptée pour établir une communication entre un terminal et un SM desservi pour le terminal ; et
    une unité de communication de SM (703), adaptée pour établir une communication entre le SM de noeud racine et le/les SM de noeud feuille ; caractérisé en ce que l'unité de communication de terminal alloue les terminaux prêts à parler au SM de noeud racine et alloue les autres terminaux non prêts à parler au SM de noeud feuille.
  9. Appareil selon la revendication 8, dans lequel l'unité de communication de SM (703) comprend en outre :
    une sous-unité de terminal de conférence de noeud racine (7031), adaptée pour envoyer un premier message au SM de noeud racine, de manière à indiquer au SM de noeud racine d'établir des terminaux de conférence ;
    une sous-unité de communication de SM (7032), adaptée pour envoyer un second message comprenant des informations de protocole de description de session du terminal de conférence établi par le SM de noeud racine à un SM de noeud feuille, de manière à indiquer au SM de noeud feuille d'établir, en fonction des informations de protocole de description de session, un terminal de conférence.
  10. Appareil selon la revendication 8, dans lequel l'unité de communication de SM (703) comprend en outre :
    une sous-unité de terminal de conférence de noeud feuille (7033), adaptée pour envoyer un troisième message à un SM de noeud feuille, de manière à indiquer au SM de noeud feuille d'établir un terminal de conférence ;
    une sous-unité de communication de SM (7034), adaptée pour envoyer un quatrième message comprenant des informations de protocole de description de session du terminal de conférence établi par le SM de noeud feuille au SM de noeud racine, de manière à indiquer au SM de noeud racine d'établir, en fonction des informations de protocole de description de session, un terminal de conférence.
  11. Appareil selon l'une quelconque des revendications 8 à 10, dans lequel l'appareil comprend en outre :
    une unité de raccordement et d'établissement de conférence (1001, 1002), adaptée pour établir une conférence principale de la conférence audio dans le SM de noeud racine, permettre à des terminaux de conférence du SM de noeud racine de se joindre à la conférence principale, établir une conférence esclave de la conférence audio dans chaque SM de noeud feuille, et permettre à un terminal de conférence de chaque SM de noeud feuille de se joindre à la conférence esclave correspondante.
  12. Produit logiciel informatique, caractérisé en ce qu'il comprend un code de programme informatique qui, lorsqu'il est exécuté par un ordinateur, amène l'ordinateur à exécuter toutes les étapes de l'une quelconque des revendications 1 à 7.
EP08163755A 2008-01-31 2008-09-05 Procédé et appareil pour configurer une connexion de conférence audio Not-in-force EP2086199B1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN2008100068009A CN101227533B (zh) 2008-01-31 2008-01-31 一种建立音频会议连接的方法和装置

Publications (2)

Publication Number Publication Date
EP2086199A1 EP2086199A1 (fr) 2009-08-05
EP2086199B1 true EP2086199B1 (fr) 2010-01-20

Family

ID=39859275

Family Applications (1)

Application Number Title Priority Date Filing Date
EP08163755A Not-in-force EP2086199B1 (fr) 2008-01-31 2008-09-05 Procédé et appareil pour configurer une connexion de conférence audio

Country Status (6)

Country Link
US (1) US20100241721A1 (fr)
EP (1) EP2086199B1 (fr)
CN (1) CN101227533B (fr)
AT (1) ATE456242T1 (fr)
DE (1) DE602008000587D1 (fr)
WO (1) WO2009097792A1 (fr)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101227533B (zh) * 2008-01-31 2011-09-14 华为技术有限公司 一种建立音频会议连接的方法和装置
CN101707593B (zh) * 2009-11-17 2012-12-19 红杉树（杭州）信息技术有限公司 一种基于树形服务器、pc客户端和电话设备客户端的会议系统
CN101848170B (zh) * 2010-06-21 2015-05-13 中兴通讯股份有限公司 Mcu资源调度方法及系统
US9282190B2 (en) * 2012-04-04 2016-03-08 Unify Gmbh & Co. Kg Method for transferring control of a conference call
CN102710922B (zh) * 2012-06-11 2014-07-09 华为技术有限公司 一种多点控制服务器的级联建立方法，设备及系统
CN103023731B (zh) * 2012-11-29 2016-01-13 深圳市迪威视讯股份有限公司 一种级联会议实现方法及系统
US9635698B2 (en) * 2013-11-20 2017-04-25 At&T Intellectual Property I, L.P. Method and apparatus for enabling a mobile endpoint device to be a hub for a conference call
US9538134B2 (en) * 2013-12-23 2017-01-03 Vonage Business Inc. Method and system for resource load balancing in a conferencing session
CN108737480B (zh) * 2017-04-24 2022-08-16 中兴通讯股份有限公司 基于软件媒体服务器的会议级联方法、服务器及存储介质
CN107147653B (zh) * 2017-05-22 2020-01-31 福建星网智慧科技股份有限公司 一种媒体分发级联方法及系统
CN114826803B (zh) * 2022-04-26 2023-10-31 北京字跳网络技术有限公司 会议状态处理方法、装置、电子设备及介质

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6950501B1 (en) * 2000-11-28 2005-09-27 Sprint Communications Company L.P. Internet-based message translation for the hearing and speech impaired
NO20013497D0 (no) * 2001-07-13 2001-07-13 Ericsson Telefon Ab L M Dynamisk distribuering av deltagere i sentraliserte IP- telefonkonferanser
CN1214635C (zh) * 2002-05-10 2005-08-10 华为技术有限公司 Ip网络会议电视的会议调度系统与方法
GB0219947D0 (en) * 2002-08-28 2002-10-02 Nokia Corp Conferencing system
FI20045175A0 (fi) * 2004-05-12 2004-05-12 Nokia Corp Istunnon käynnistys reaaliaikaista mediakommunikaatiopalvelua varten
US7176957B2 (en) * 2004-05-25 2007-02-13 Seiko Epson Corporation Local video loopback method for a multi-participant conference system using a back-channel video interface
US8214447B2 (en) * 2004-06-08 2012-07-03 Bose Corporation Managing an audio network
JP3870955B2 (ja) * 2004-06-21 2007-01-24 株式会社日立製作所 階層型中継処理を行うセッション制御装置
US7460508B2 (en) * 2004-12-01 2008-12-02 Telefonaktiebolaget L M Ericsson (Publ) Methods for cluster-based multi-party conferencing in ad-hoc networks
CN100493123C (zh) * 2005-05-19 2009-05-27 深圳市友邻通讯设备有限公司 电话会议系统和控制方法
US7814220B2 (en) * 2005-09-14 2010-10-12 Sony Ericsson Mobile Communications Ab User interface for an electronic device
CN101026616B (zh) * 2006-02-18 2013-01-09 华为技术有限公司 基于ip多媒体子系统的交互式媒体会话建立方法
US7792899B2 (en) * 2006-03-24 2010-09-07 Cisco Technology, Inc. Automatically providing announcements for a push-to-talk communication session
CN100571147C (zh) * 2006-07-18 2009-12-16 中兴通讯股份有限公司 一种利用媒体服务器实现子会议的方法
CN100420194C (zh) * 2006-10-08 2008-09-17 华为技术有限公司 一种视频会议系统及其数据传输方法及装置
CN100490416C (zh) * 2006-12-01 2009-05-20 上海华平信息技术股份有限公司 树状分层结构会议系统及会议系统构建方法
US8667160B1 (en) * 2007-02-02 2014-03-04 Max Haot System and method for internet audio/video delivery
US20090164645A1 (en) * 2007-12-19 2009-06-25 Nortel Networks Limited Real time communication between web and sip end points
CN101227533B (zh) * 2008-01-31 2011-09-14 华为技术有限公司 一种建立音频会议连接的方法和装置

Also Published As

Publication number Publication date
CN101227533A (zh) 2008-07-23
WO2009097792A1 (fr) 2009-08-13
ATE456242T1 (de) 2010-02-15
US20100241721A1 (en) 2010-09-23
DE602008000587D1 (de) 2010-03-11
CN101227533B (zh) 2011-09-14
EP2086199A1 (fr) 2009-08-05

Similar Documents

Publication Publication Date Title
EP2086199B1 (fr) Procédé et appareil pour configurer une connexion de conférence audio
US9106716B2 (en) Method, apparatus, and system for cross-platform conference convergence
US20100281129A1 (en) Method, device, and system for implementing file sharing in audio and video conference
US8180933B2 (en) Dynamic call handling from multiple attached devices wherein devices advertize its capabililes before facilitating call through appropriate device
US20130097333A1 (en) Methods and apparatuses for unified streaming communication
CN105721570B (zh) 数据点对点传输方法及装置
Elleuch Models for multimedia conference between browsers based on WebRTC
US10506000B2 (en) Mesh conferencing
US20180255182A1 (en) Web Real-Time Client Communication Over a Stimulus Based Network
US9544157B1 (en) Systems and methods for conferencing enterprise and non-enterprise callers
US11330022B2 (en) System and method for separation of call origination and call delivery techniques
US8249612B2 (en) Method, system, server, and client for transmitting media burst data
CN101674305A (zh) 一种多媒体会议的实现方法及系统
JP7463552B2 (ja) セッション作成方法、電子機器、および可読記憶媒体
US20090047938A1 (en) Media Handling for Multimedia Conferencing in Multihop Cellular Networks
CN101557603B (zh) 一种合法监听的方法、装置和系统
US20200259873A1 (en) Messaging resource function
CN111835674A (zh) 通信方法、装置、第一网元及通信系统
US20080039065A1 (en) Data transmission in a communication session
CN101686138B (zh) 一种实现三方会议的方法、设备和系统
US10091261B2 (en) Methods and nodes for enabling a peer-to-peer teleconference
CN104702602A (zh) 基于sip实现集群网关动态创建通道和扩容的系统和方法
CN104901929A (zh) 一种录音方法、呼叫控制服务器及录音系统
KR20180021448A (ko) 그룹 통화를 위한 시스템 및 방법과 이를 위한 장치
Elleuch et al. SIP-based protocol for p2p large-scale multiparty voip (mvoip) conference support

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20080905

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MT NL NO PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA MK RS

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MT NL NO PL PT RO SE SI SK TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REF Corresponds to:

Ref document number: 602008000587

Country of ref document: DE

Date of ref document: 20100311

Kind code of ref document: P

AKX Designation fees paid

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MT NL NO PL PT RO SE SI SK TR

REG Reference to a national code

Ref country code: SE

Ref legal event code: TRGR

REG Reference to a national code

Ref country code: NL

Ref legal event code: VDEP

Effective date: 20100120

LTIE Lt: invalidation of european patent or patent extension

Effective date: 20100120

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100120

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100120

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100120

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100501

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100520

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100120

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100420

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100120

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100120

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100120

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100120

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100120

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100120

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100120

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100120

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100421

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100420

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100120

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100120

26N No opposition filed

Effective date: 20101021

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100120

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100120

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20100930

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20100905

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100120

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100721

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20100905

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20100120

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120930

Ref country code: PT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20100120

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120930

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 9

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 10

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 11

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20210812

Year of fee payment: 14

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602008000587

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0029060000

Ipc: H04L0065000000

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20210805

Year of fee payment: 14

Ref country code: SE

Payment date: 20210910

Year of fee payment: 14

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20220609

Year of fee payment: 15

REG Reference to a national code

Ref country code: SE

Ref legal event code: EUG

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20220905

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220930

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220906

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20220905

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 602008000587

Country of ref document: DE