DE102005013919A1 - Telecommunications-conference e.g. multimedia-telecommunications-conference, managing method for Internet protocol multimedia subsystem, involves generating new telecommunications-conference event under utilization of standard-file version - Google Patents

Abstract

The method involves initializing a telecommunications-conference between participants with events by a server mechanism. A version-information included in an electronic telecommunications-conference-standard-file is determined. The version is utilized within limits of the events. A new telecommunications-conference event is generated under utilization of the version by the mechanism and is specified as version information in the file. An independent claim is also included for a telecommunication-conference-server mechanism.

Description

The The invention relates to methods for computer-aided management of a telecommunications conference as well as telecommunication conference server facilities.

Within the so-called Work Items "IMS Stage-2 Enhancements "(TSG SA WD2 / TSG CN WD1) is under the 3rd Generation Partnership Project (3GPP) currently a multimedia telecommunication conference system for the Internet Protocol Multimedia Subsystem (IMS) of Universal Mobile Telecommunication System (UMTS) specified.

This Telecommunication Conference System is based on the architecture and the communication protocol components used in the by the Internet Engineering Task Force (IETF) for this defined framework (Conferencing Framework) (See [1]).

The Telecommunication conference system puts in addition to a procedure for controlling the access rights to multimedia telecommunication conference resources (also referred to as floor control) and the establishment of conference rules (also referred to as Conference Policy Control) further Session Initiation Protocol (SIP) -based procedures for, among other things, generation, management, for entering and leaving telecom conferences ready. Furthermore, in this system, methods of notification the conference participant (also referred to as Conference Notification Service) specific information concerning the telecommunications conference and events. Within the Telecommunication Conference System can any types of media exchanged between participants become. The telecommunication conference system will be out of this Reason also referred to below as a multimedia telecommunications conference system.

Examples different types of media between participants can be exchanged, are audio data, video data, instant messaging conference data and Gaming (Games) Conference Data. Furthermore, a limitation of the In general, bidirectional media flow is possible, so also a push-to-talk conference can be realized.

Out [2] is also the implementation of the framework described in [1] known in the Internet Protocol Multimedia Subsystem (IMS).

The Session Initiation Protocol (SIP) is described in [3].

[4] describes a call control mechanism according to the Session Initiation Protocol in the context of conferencing for User agents.

Farther is from [5] the so-called Conference Policy Control Protocol (CPCP) known.

[6] describes rules governing the privileges of users of a telecom conference, as described in [1], according to [6] Rules in a so-called Conference Policy Privileges document are stored.

Farther is known from [7] the so-called XCAP protocol, which is used to change the Rules files used in the telecommunication conference stored parameter can be used.

Further it is known from [7] and [8] that it is by means of the Conference Policy Control Protocols, as this is an XCAP application (Extensible Markup Language Configuration Access Protocol) is possible, individual elements, Attributes or attribute values of an XML file (Extensible Markup Language file) by means of the respective Hypertext Transfer Protocol Unique Resource Locator (HTTP URL) to address uniquely.

Out [9] is the functionality a telecommunication conference record within the conferencing framework.

Further, from [10], information is known which is a record of a telecommunications conference such as the URI (Unique Resource Identifier) of the telecommunications conference, by means of which the recording data can be accessed, to be used as part of a conference-related notification procedure.

Farther it is known from [11] and [5] for an item of telecommunication conference rule file indicate if this is valid is or not.

According to the state The technology will be part of a telecom conference the elements of the provided so-called Conference Policy Documents (also referred to as Conference Policy Document) for which the Producers of the telecommunication conference no conference parameter values in the creation of the document and thus in the Generation of a conference event of the telecommunication conference initialized with default values, including that of the producer the telecommunications conference predetermined and thus set parameters of the Conference Policy Documents. This Conference Policy Document will be enclosed afterwards the first telecommunication conference event to be generated within applied to the telecommunications conference. The telecom conference event is changing in their characteristics, for example, participants part during the first conference event, new participants will be added or change the wishes the participant of the telecommunication conference regarding for example the one to be transferred Media in the context of the telecom conference event, so if necessary changed the Conference Policy Document. Should now a second Telecommunication conference event as part of the Telecommunications Conference are generated, it is unclear whether in the context of generating the second Telecommunication conference event the original one (initial) Conference Policy Document should be used or whether in the context of the first telecommunications conference event made changes the second telecommunication conference event considered should be.

Of the The invention is based on the problem of a telecommunications conference by means of a telecommunication conference server device to manage, whereby it is easy to determine automatically, using whatever state of telecommunication conference rule file generates a telecommunication conference event of a telecommunication conference shall be.

The Problem is solved by a method for managing a telecommunication conference as well as through a telecommunications conference server facilities solved with the features according to the independent claims.

preferred Embodiments of the invention will become apparent from the dependent claims.

It A method for computer-aided managing a telecommunications conference by means of a telecommunication conference server device, which at least one telecommunication conference between several Participants with several telecommunication conference events provided. The telecommunication conference server device has access to one electronic telecommunication conference rule file, being in The Telecommunications Conference Rules File for the Telecommunication Conference Provided a version information which can be used to determine which version the telecommunication conference rule file as part of the generating a telecom conference event the telecommunications conference to be used, of the telecommunication conference server device a new telecom conference event using the version of the telecommunication conference rule file is generated in the telecommunication conference rule file is specified by means of the version information. One to use In particular, the version of the telecommunication conference rule file can be by the state of telecommunication conference rule file at Be given the end of a telecommunications conference event. Furthermore, can a new version through every change the telecommunication conference rule file are generated. Also can with every change the telecommunication conference rule file be specified individually, whether this causes a change of the version.

Under For example, a telecommunications conference is a multimedia telecommunications conference in a framework as described in [1]. In a telecommunication conference are one or more telecommunication conference events provided according to which the Communication between several predetermined participants provided can be.

Under For example, a telecommunications conference rule file is to understand a file in which a telecommunication conference and / or one or more telecommunication conference events characterizing data, such as parameters are included, which, if appropriate, for controlling the telecommunication conference and / or one or more telecommunication conference events. Examples of such data / parameters are information about participants, about times of telecommunication conference events to be generated, description from within the telecommunication conference and / or the telecommunication conference events exchangeable / exchangeable media (video, audio, text, etc.), Information about the access rights of the participants of the telecommunication conference events, Etc.

A Telecommunication conference server device is set up such that they have at least one telecom conference between multiple participants while Providing telecommunications conference events. The telecommunication conference server device is also arranged to have access to an electronic Telecommunication conference rule file, being in the telecommunication conference rule file for the provided telecommunication conference contain a version information is, by means of which can be determined, which version of the telecommunications conference rule file in the context of generating a telecommunication conference event of the telecommunication conference should be used. Further, the telecommunication conference server device set up to host a new telecom conference event using the version of the telecommunication conference rule file generated in the telecommunication conference rule file by means of the version information is specified.

clear The invention can be seen in that it by corresponding Posts in the telecommunication conference rule file now possible in a flexible manner is to specify which version of the telecommunications conference rule file as part of generating a new telecommunications conference event to use.

This leads to a very simple, yet infinitely adjustable Possibility, a guideline regarding the use of the telecommunication conference rule file in the framework developing and generating telecommunications conference events to be involved in a telecommunication conference architecture.

clear becomes the Conference Policy, especially the Conference Policy Document or the Conference Policy Control Protocol (CPCP), in general The Telecom Conference Rules File different information expanded and thus to the ability added, indicate which status (i.e., which version) of the document (generally the telecommunications conference rule file) at the next conference event should be applied.

According to the state technology becomes the elements of the Conference Policy Document, for the the producer of the telecommunication conference has given no values, initialized at creation of the document with default values. This booth (including that of the conference producer, if applicable set parameters) of the Conference Policy Document is then at first conference event applied. It is currently under the Standardization committee unclear which state of the Conference Policy Documents at the second telecommunication conference event or a subsequent one Telecommunication conference event should be applied. This means it is unclear if again the state of the document is established before the first conference event and should be used or whether the state of the document is applied should be at the end of the previous or the first Telecommunications conference event existed. Would the State of the telecommunications conference rule file used on the End of the immediately preceding telecommunications conference event existed also in the context of generating each currently new used to create telecommunication conference event, then would For example, participants who during the first conference event or during the previous telecommunication conference event from the telecommunication conference server device (also referred to as Focus referred to), as part of the conferencing framework in [1], invited to the telecommunication conference were, i. the participants, in addition to the so-called dialout list (<dialout-list> data element) automatically become the second telecom conference event be invited. Both variants offer, depending on the situation, specific advantages and disadvantages. That's why it's special advantageous to configure according to the invention to be able to whether in each case the initial state of the Conference Policy Document, in general the initial version of the telecommunication conference rule file is applied or not.

According to the invention this configuration, for example, also by means of the element of the Conference Policy Document, by means of which general Settings for the conference takes place, i. for example, by means of the so-called <settings> data element. With the version information can be specified whether a new telecom conference event the telecommunications conference with a default initialization telecommunication conference rule file should be generated, as described above, for example with predetermined by the producer of the telecommunications conference Parameters or initialized with default values. In the case, that the version information indicates that a new one Telecommunication conference event of Telecom Conference with a default initialization telecommunication conference rule file will be the new telecommunications conference event generated with the initialization telecommunication conference rule file.

clear this means that with the version information as an item in the Conference Policy Document can be specified that for all subsequent Telecommunication conference events a telecommunications conference, the same initial telecommunications conference rules file as used in the generation of the first telecommunications conference event has been used.

alternative can be specified with the version information, if a new one Telecommunication conference event of Telecom Conference with a telecommunications conference event provided as part of a previous one changed Telecommunication conference rule file should be generated. For the case that is specified with the version information that a new telecom conference event with a telecom conference as part of a previous telecom conference event changed Telecommunications conference rule file is to be generated the new telecom conference event with the changed Telecommunication conference rule file generated.

clear This kind of version information means that the telecommunication conference rule file in the context of the telecommunication conference event (s) is continued continuously and in particular the Conference Policy Document will be continued without being reset to a given initialization status to become.

• • ein oder mehrere in der Telekommunikations-Konferenz-Regel-Datei angegebene (r) Teilnehmer der Telekommunikations-Konferenz verlässt oder verlassen die Telekommunikations-Konferenz, wobei der oder die Teilnehmer aus der Telekommunikations-Konferenz-Regel-Datei gelöscht wird/werden,
• • mindestens ein Telekommunikations-Konferenz-Parameter wird verändert, wobei der Telekommunikations-Konferenz-Parameter in der Telekommunikations-Konferenz-Regel-Datei entsprechend verändert wird.

A change in the telecommunication conference rule file may be made upon the occurrence of at least one event of the following events:

• One or more telecommunication conference participants specified in the telecommunication conference rule file leave or leave the telecommunication conference, the participant (s) being deleted from the telecommunication conference rule file,
• • at least one telecommunication conference parameter is changed, whereby the telecommunication conference parameter in the telecommunication conference rule file is changed accordingly.

One Telecommunication conference parameter is for example the indication which access rights a subscriber has to the telecommunication conference rule file or their parameters or what kind of media the respective one has Participants in the context of the telecommunications conference event transmitted gets.

By This embodiment of the invention makes it possible, important, specifiable Partial events as part of an ongoing telecom conference event to log in the telecommunication conference rule file and these changes if necessary, maintain a new telecom conference event based on the changed Conference situation with possibly changed participants or changed Participants Requirements regarding the access rights and the information to be transmitted to the participants Media allows becomes.

When changing The telecommunication conference rule file may be modified by change validity information be specified for which telecommunication conference events the change is valid. So can be specified with the change-validity information be that change only for the already created or the next Telecommunication conference event applies. Alternatively, the change-validity information can be specified be that change only for a predefinable number of telecommunication conference events yet to be generated applies. Alternatively or in addition can with the change validity information be specified that the change permanent, i. permanently valid should be.

by virtue of the use of change validity information It is made possible in a simple and thus cost-effective way, changes in terms of scope and importance and with it the telecommunication conference continue to be flexibly controllable.

According to one Another aspect of the invention is a method of computerized management a telecommunication conference by means of a telecommunication conference server device provided, wherein the telecommunication conference server device at least one telecommunication conference between several participants with several telecommunication conference events provides. The telecommunication conference server device has access on an electronic telecommunication conference rule file, being provided in the telecommunication conference rule file for the Telecommunications Conference contain a repeat information is, by means of which it can be determined at what time interval based on a predefinable reference time after the generation of a first telecommunication conference event at least a second, to the first telecom conference event the same (i.e., for example, with the same participants and using the same conference parameters), telecommunication conference event to be generated by the telecommunication conference server device the second telecommunication conference event to that with the retry information specified time is generated.

According to one Another aspect of the invention is a telecommunication conference server device provided, which is adapted to provide at least a telecommunication conference between several participants with several telecommunication conference events. The telecommunication conference server device is set up so that it has access to an electronic Telecommunication conference rule file, being in the telecommunication conference rule file for the provided telecommunication conference a repeat information is contained, by means of which it can be determined, in which temporal Distance relative to a predefinable reference time after generation of a first telecommunication conference event at least a second, to the first telecom conference event same, telecommunications conference event is to be generated.

clear will according to this Aspect of the invention provides a simple way without a regularly recurring one Telecom conference event everytime as a separate telecom conference event in the Telecommunications Conference Rules file to define one Telecommunications conference event to assign the repeat information and in this way to control that, based on a specifiable Reference time, the same telecommunication conference event is generated as the telecommunication conference event of the telecommunication conference, i. one Telecommunication conference event with the same conference parameters like the first telecom conference event, only after expiration a predefined period in relation to a given time, the reference time.

On this way, the telecommunication conference rule file becomes small and so on also the processing of the telecommunication conference rule file by means of the telecommunication conference server device very much easy and inexpensive held.

From the telecommunication conference server device can further, same as the first telecommunication conference event, telecommunication conference events are generated at times, which with the repetition information be specified.

When Reference time can be used a time that is dependent from the first telecommunication conference event, for example the Start of the generated first telecommunication conference event or the end of the generated first telecommunication conference event, generally the beginning or the end of a previously generated telecommunications conference event. These Reference times represent a very simple and reliable Reference variable to, starting from this generating a regularly periodic occurring new telecommunication conference event to be generated within the telecommunications conference.

• • stündlich
• • in einem periodischen Abstand von einer vorgebbaren Anzahl von Stunden,
• • täglich,
• • in einem periodischen Abstand von einer vorgebbaren Anzahl von Tagen,
• • wöchentlich,
• • in einem periodischen Abstand von einer vorgebbaren Anzahl von Wochen,
• • monatlich,
• • in einem periodischen Abstand von einer vorgebbaren Anzahl von Monaten,
• • jährlich,
• • in einem periodischen Abstand von einer vorgebbaren Anzahl von Jahren.

The retry information may indicate generation of another same telecommunication conference event according to at least one of the following time periods:

• • every hour
• • at a periodic interval from a predefinable number of hours,
• • Every day,
• • at a periodic interval from a predefinable number of days,
• • weekly,
• • at a periodic interval from a predefinable number of weeks,
• • per month,
• • at a periodic interval from a predefined number of months,
• • annually,
• • at a periodic interval from a predefined number of years.

According to one Another aspect of the invention is a method of computerized management a telecommunication conference by means of a telecommunication conference server device provided, wherein the telecommunication conference server device at least one telecommunication conference between several participants with several telecommunication conference events provides. The telecommunication conference server device has access on an electronic telecommunication conference rule file, being provided in the telecommunication conference rule file for the Telecommunications Conference moderator information is included, based on which it can be determined which subscriber to contact, if another subscriber engages in a generated telecom conference event the telecom conference would like to dial in to this subscriber the permission to dial to request in the telecommunication conference event, whereby of the telecommunication conference server device or of the other participants a request message to that in the moderator information specified participant Whether the other participant joins the telecom conference event dial may or not.

According to one Another aspect of the invention is a telecommunication conference server device provided, which is adapted to provide at least a telecommunication conference between several participants with several telecommunication conference events. The telecommunication conference server device is set up so that it has access to an electronic Telecommunication conference rule file, taking with telecommunication conference rule file for the provided telecom conference containing moderator information which can be used to determine which participant to contact is when another subscriber engages in a generated telecom conference event want to dial in to the telecommunications conference in order to attend these participants the permission to dial to request in the telecommunication conference event. The telecommunication conference server device is further arranged to send a request message generated and transmitted to the participant specified in the moderator information, wherein the request message includes the request whether the other participants in the telecom conference event dial may.

The Moderator information can be an address, preferably a SIP URI be the participant. Alternatively, with the moderator information be a reference of the subscriber specified, with which a function of the subscriber within the telecommunication conference is determined and by means of which an address of the subscriber is.

According to one more Another aspect of the invention is a method for computerized management of a Telecommunication conference by means of a telecommunication conference server device provided, wherein the telecommunication conference server device at least one telecommunication conference between several participants with multiple telecommunication conference events. The telecommunication conference server device is set up in such a way that it has access to an electronic telecommunication conference rule file, being provided in the telecommunication conference rule file for the Telecommunications Conference contain a record information which can be used to determine whether a telecom conference event the telecommunication conference is to be recorded, whereby a generated telecommunication conference event from the telecommunication conference server device dependent recorded by the recording information or not recorded becomes.

According to another aspect of the invention, there is provided a telecommunication conference server device arranged to provide at least one telecommunication conference between a plurality of participants with a plurality of telecommunication conference events. The telecommunication conference server device has access to an electronic telecommunication conference rule file, wherein in the telecommunication conference rule file for the provided telecommunication conference a record information is contained, by means of which it can be determined whether a Telecommunication conference event of the telecommunication conference should be recorded. The telecommunication conference server device is further arranged such that a generated telecommuni conference event is recorded or not recorded depending on the recording information.

On This way will be very easy and flexible for a telecom conference in the telecommunication conference rule file adjustable whether a telecom conference event will be recorded should or not. This may be at the level of the telecommunications conference yourself or for Each telecom conference event is separate in the Telecom Conference Rule file be specified.

According to one Another aspect of the invention is a method of computerized management a telecommunications conference provided by a telecommunication conference server device which at least one telecommunication conference between several participants with several telecom conference events, wherein the telecommunication conference server device access has on an electronic telecommunication conference rule file, being in the Telecommunication conference rule file for the provided telecommunication conference validity information and validity conference event information is included, which can be used to determine whether a rule within the telecommunication conference rule file for a via the validity conference event information Identified telecommunications conference event is valid. From the telecommunications conference server device is a Telecommunication conference event generated using the Rules of the telecommunication conference rule file, which according to the validity information and the validity conference event information for the Telecommunication conference event valid are.

According to one Another aspect of the invention is a telecommunication conference server device provided, which is adapted to provide at least a telecommunication conference between several participants with several telecommunication conference events. The telecommunication conference server device has access to an electronic telecommunication conference rule file, being provided in the telecommunication conference rule file for the Telecommunications Conference a validity information and validity conference event information included is, by means of which it can be determined whether a rule within the telecommunication conference rule file for a via the validity conference event information identified Telecommunication conference event valid is. The telecommunication conference server device is further arranged to be a telecommunications conference event can generate using (only) those rules of the telecommunication conference rule file, which according to the validity information and the validity conference event information for the telecommunication conference event valid are.

The relate to the embodiments of the inventions described below both the methods for computer-aided management of a telecommunications conference as well as the telecommunication conference server facilities described above.

The respective process steps or the described units can in their functionality both in hardware, i. using special electronic circuits, in software, i. using special computer programs or in any way hybrid form, i. arbitrarily divided into their sub-functionalities be realized in hardware and software.

According to one Embodiment of the invention, it is provided that the telecommunication conference rule file is provided in the extensible markup language and a plurality or Contains a plurality of authorization data elements, which also according to the Extensible Markup language format (i.e., encoded according to the XML format) are.

The Communication between the subscribers and the telecommunication conference server device is preferably at least partially according to the Session Initiation Protocol (SIP), which is described in [3].

According to one In another embodiment of the invention, the communication takes place between the subscribers and the telecommunications conference server device at least partially according to the Conference Policy Control Protocol (CPCP) as described in [5], in particular for Create or change the Conference Policy, and thus in particular for creating or changing the Telecommunication conference rule file.

According to one Embodiment of the invention is of the telecommunication conference server device provided a multimedia telecommunications conference, in which provided the participants with several different media data streams such as audio streams, video streams, text streams, etc.

According to this Embodiment of the invention will be a respect to be used Medium flexible and therefore for the participants provided comfortable telecommunication conference.

The Telecommunication conference server equipment is preferred uniquely identifiable by means of a SIP Unique Resource Identifier (URI), this identifier is preferred when generating a telecommunications conference this is assigned and after terminating the telecommunication conference again is released so that it reassigned to another, subsequently generated telecommunications conference can be. In particular, the corresponding conference identification according to [1] also referred to as Conference URI (C-URI).

The Telecommunication conference rule file is particularly preferred according to the Extensible Markup Language Format (XML Format) stored, creating a standardized, simple and cost-effective representation the file is reached.

The Telecommunication conference rule file is preferred according to the hypertext Transport Protocol (HTTP) read or written or changed, otherwise expressed The telecommunication conference rule file is preferably accessed via HTTP. This has the particular advantage of having standardized protocols for the Access to this file can be used with what existing systems regarding the file accesses not changed will need.

The Transfer and / or receive participants in the telecommunication conference Data preferred over a mobile radio system, particularly preferably according to a 3GPP mobile radio system, especially preferred according to UMTS. In other words this means that preferably the telecommunication conference server device for communication about a mobile radio system is set up, in this case being particularly preferred according to one 3GPP mobile radio system and thereby particularly preferably according to UMTS.

Consequently the invention is particularly suitable for use in one, preferably cell-based, cellular communication system. In other words This means that the telecommunication conference server device Thus, preferably a component of a mobile communication system, particularly preferred a 3GPP cellular communication system and particularly preferably the so-called IP Multimedia Core Network Subsystems (IMS) of the UMTS mobile communication system is.

embodiments The invention is illustrated in the figures and will be described below explained in more detail.

It demonstrate

1 a telecommunications conferencing system, such as a mobile telecommunications conferencing system, in accordance with preferred embodiments of the invention;

2 a block diagram in which the procedure is shown according to a first embodiment of the invention.

1 shows a cellular multimedia telecommunication conference system 100 in accordance with the preferred embodiments of the invention. It should be noted that in an alternative embodiment, it does not have to be a mobile multimedia telecommunication conference system. The methods described below and above may also be implemented in a landline multimedia telecommunications conferencing system, for example, an Internet-based landline multimedia telecommunications conferencing system. In this alternative embodiment, at least a part of the telecommunication terminals are set up as fixed-network telecommunication terminals, which are set up, for example, to carry out an internet-based telecommunication conference.

The system 100 is for all embodiments, which are explained in more detail below, iden table except for the different embodiments of the focus server, which is each set up such that it has implemented the functionalities of the respective embodiments.

The each of the units described below may each be individually, separate hardware units, for example, stand-alone Computer or

Mobile devices implemented or at least partially in software, i. using computer programs, implemented in separate or shared computer units are.

The Communication system is except for the changes described below according to the embodiments of the invention as described in [1].

That described in [1] and in l presented "Conferencing Framework" provides users, especially the mobile devices 101 . 102 . 103 . 104 different multimedia telecommunication conference services.

Especially are, as described in detail in [1], a control service access rights to telecommunication conference resources, Also referred to as floor control, a service for establishing Conference Rules (also referred to as Conference Policy Control), as well as in the form of the Session Initiation Protocol (SIP) based procedures additional Services for creation, management, entry and exit of multimedia telecommunication conferences intended.

Furthermore, the communication system provides 100 , as also described in [1], methods for notifying conference participants 101 . 102 . 103 . 104 , also referred to as the Conference Notification Service, about specific information and events pertaining to a respective Multimedia Telecommunication Conference.

The conference system 100 is set up such that any types of media between the participants, ie between the mobile terminals 101 . 102 . 103 . 104 can be exchanged. Examples of a type of media used in the context of the conference system 100 can be transmitted and processed, are audio data, video data, instant messaging data and data from multiplayer games in the context of a gaming conference.

1 shows, as described above, the multimedia telecommunications conference systems 100 according to the embodiments of the invention with its individual components and the interaction between the components.

The Multimedia Telecommunication Conference System 100 has a star-shaped conference architecture, in which all conference participants (also referred to as user agents), according to these embodiments mobile terminals 101 . 102 . 103 . 104 with the conference server device 105 , also referred to as focus 105 , via SIP signaling connection 106 connected. 1 shows only one example of one of these SIP signaling connections, 106 ,

A particular particular cellular telecommunication conference that has a particular conference server computer 105 , ie a certain focus, is assigned, or is executed on it, is assigned a unique conference address, the so-called Conference-Unique Resource Identifier (C-URI). The C-URI represents and addresses the respective conference uniquely. The focus 105 has, among other things, indirect access to the conference policy. The Conference Policy file, also referred to below as a conference rule file 108 , is usually logically composed of two sub-areas, a membership policy 109 as well as a media policy 110 , together. However, the Conference Policy file may physically be split into multiple subdivisions. In addition to the physical separation, a logical division of the conference policy file can also take place here. The conference rule file 108 is issued by a conference rule server (Conference Policy Server) 111 generated exclusively for a particular conference, in 1 symbolized by an arrow 112 , The focus 105 is via the conference rule server 111 informed about the content and any changes to the Conference Policy file. It is also conceivable that the focus 105 has direct access to the Conference Policy file.

In addition to the implementation of this in the conference rule file 108 stored conference rules has the focus 105 the task of providing the conference-specific distribution of the media data streams.

The focus is on distributing the media data streams 105 so-called mixer 113 In other words, data stream mixers, one using the in the Media Policy 110 stored media rules the individual compilation and distribution of the media streams to the participating in the conference mobile terminals 101 . 102 . 103 . 104 executes, in 1 symbolized by double arrows 114 . 115 . 116 . 117 , In the mobile devices 101 . 102 . 103 . 104 For the implementation of the conference service some additional procedures, communication protocols and functionalities are implemented, in particular new additional SIP procedures are implemented as well as the so-called Binary Floor Control Protocol (BFCP), implemented on the server side in a Floor Control Server 118 , and the Conference Policy Control Protocol (CPCP) or the respective units which are capable of executing the corresponding communication protocols. The Binary Floor Control Protocol communication link between a first mobile terminal 101 and the floor control server 118 is in 1 with an arrow 119 symbolizes.

Thus, every detail of these procedures and protocols is important to the mobile terminal (mobile terminal) 101 . 102 . 103 . 104 and thus for the hardware and / or software used in the terminal.

The in [5] offers the Conference Policy Control Protocol (CPCP) the possibility, different rules for to define a multimedia telecommunications conference. So, for example general conference rules, such as the maximum number of conference participants within the conference rule file (Conference Policy) CPCP. The conference rule file still exists for example, a so-called "dialout" list (<dialout-list> data element), indicating which users or which telecommunication terminals at a Activation of a conference to be invited to this.

The conference policy file 108 also contains authorization data elements, which are basically distinguished in two types, namely authorization rule data elements which relate to the conference participation of subscribers (<ruleset> data element) and rule data elements which define the privileges of the subscribers (<privileges> data element).

To For example, the category of authorization rule data items is one Determining which participant has specific, the conference information and events notified (Conference Notification Service), which participant May use SIP methods to invite subscribers and which ones Participants generally the method for controlling the access rights Use telecommunications conference resources (Floor Control) may.

To The category of rule data elements includes, for example, the specification, who enter participants in the "Dialout" list who is allowed to use the rules of the first category, i. the authorization rule data items change may and which participant which rules of the first category, i.e. the authorization rule data items allowed to read.

to Distinction between these different rights categories is two different Conference Policy documents, i. vivid conference Policy files, provided as described above.

While the Authorization rule data elements along with the basic ones Conference data elements in so-called "Conference Policy Documents" is described (compare [5]), the second category, i. the rule data elements, which vividly contains meta-rights or meta-data, in the so-called "Conference Policy Privileges Document " (compare [6]).

It However, it should be noted that this functional separation is not necessary is. The division of the individual functionalities and The data to be stored in different files can basically be arbitrary without the following statements regarding the function and the basic principles of the invention.

The Conference Policy contains also authorization data elements, by means of which it is specified which user other users in enter the "Dialout" list may (<allow-modify-dol> -data).

To specify who is allowed to edit authorization data items, CPCP provides for a higher-level authorization data item that provides access to all other authorization data items controls (<allow-modify-authorization-rules> data element).

The conference rule file 108 is specified in the form of at least one Extensible Markup Language (XML) document. Due to the use of XML to describe the conference rule file 108 It is possible to easily expand, generally modify, the conference rule file.

For transferring the XML files, in particular the conference rule file 108 or to read data from the conference rules file and / or to write data to the conference rules file 108 the Hypertext Transport Protocol (HTTP) is used.

Writing a conference rule file 108 or writing in a conference rule file 108 done by means of an HTTP Put Request, whereas to read a conference rule file 108 or part of a conference rule file 108 an HTTP Get Request and delete an entire conference rule file 108 or part of the conference rule file 108 an HTTP delete request is used.

By The use of CPCP will allow the addressing of individual elements, attributes or attribute values of an XML document and thus the Conference Policy Document and the Conference Policy Privileges Documents about to realize the respective HTTP URL since the CPCP is an XCRP application represents (compare [7], [8]).

The following is the structure of a conference rule file 108 explained in more detail in XML, the basic structure of such a conference rule file 108 from [5] and is also constructed in this way.

In the conference rule file 108 the conference rules are described.

The conference rule file 108 has different data elements, for example the <info> data element in which general free text information for the respective multimedia telecommunication conference is contained, the <settings> data element, in which inter alia the conference address (<conference-uri> sub-address) Data element) and the maximum number of conferees (<max-participants-count> sub data element), the <authorization-rules> data element that contains the individual authorization data elements and, for example, the <dialout list> Data element listing the participants to be invited for the respective conference.

It also assigns the conference rule file 108 a <time> data element, in which inter alia the beginning and the end of various telecommunication conference events (represented by an <occurence> data element) are specified, a <ruleset> data element containing the authorization rule data elements described above and thus contains the data elements of the first category, and further includes, for example, the <dialout list> data element described above, which lists the participants to be invited.

Abb. 1: Beispiel eines Conference Policy Documents gemäß [5] The following is an example of a prior art Conference Policy document in XML format:

Fig. 1: Example of a Conference Policy Document according to [5]

Further Below is an example of a Conference Policy privilege Document in XML format as shown in [6] is described.

Abb. 2: Beispiel eines Conference Policy Privileges Documents gemäß [6] According to these embodiments of the invention, the Conference Policy Privileges Document contains exclusively the rule data elements, ie the authorization elements of the second category described above:

Fig. 2: Example of a Conference Policy Privilege Documents according to [6]

According to a first embodiment of the invention, the Conference Policy Document or CPCP is illustratively enhanced by the ability to indicate which state, ie which version, of the Conference Policy Document, in general, which version of the conference rule file 108 to be applied at the next conference event to be created.

In this context, it should be noted that, according to the prior art, the elements of the Conference Policy Document for which the producer of the telecommunication conference has not provided any values are initialized in the creation of the Conference Policy Document with default values. This version (including that of the producer of the telecommunication conference, ie of the focus 105 set parameter) of the Conference Policy Document is then applied when generating the first telecommunication conference event. It is not determined in the prior art which state of the Conference Policy Document will be used in a second telecommunication conference event to be generated or a subsequent third or fourth telecommunication conference event, etc. This means it is unclear whether the version of the Conference Policy Documents before the first telecom and whether the version of the Conference Policy Document that existed at the end of the immediately preceding telecom conference event is restored and used. Thus, according to the prior art, for example, subscribers who would be aware of the focus during the first telecommunication conference event 105 have been invited to the telecommunication conference event, ie the subscribers who have additionally been entered in the dialout list (<Dialout List> Data Element) are also automatically invited to the second telecommunication conference event. Both variants described above always offer specific advantages and disadvantages depending on the particular situation.

Out For this reason, it is advantageous to configure according to the invention to be able to whether in each case the initial state of the Conference Policy Documents at Generating a subsequent telecommunication conference event is applied or not.

According to this embodiment According to the invention, this configuration is carried out by means of a data element in FIG the Conference Policy Documents, with the help of general settings for the Telecommunications conference, i. according to the embodiment of the invention using the <settings> data element as described above has been.

According to this embodiment According to the invention, this determination is made by means of the newly provided <continued-policy> sub-data element.

is this sub-data item is set to the value "true", then the conference Policy Document continuously continued, i. it will not happen every generation of a new telecommunication conference event reset to the initial values in the telecommunication conference.

Abb. 3: Conference Policy Document gemäß dem ersten Ausführungsbeispiel der Erfindung The following is an example of a conference policy document according to this embodiment of the invention:

Fig. 3: Conference Policy Document according to the first embodiment of the invention

According to the Conference Policy Document outlined above, it is assumed that each conference conference event to be created will use the state of the Conference Policy Document that existed "at the end" of the previous conference teleconference event to be reset to a status corresponding to the initial status represented by the above figure
<Continued-policy> true </ Continued policy>.

Attendees with appropriate access rights, the Conference Policy File and also the Conference Policy Document as before according to the state edit and change the technology at any time.

According to this embodiment The invention may also apply to any modification of the Conference Policy Document be specified whether these changes only for the subsequent, i. the next Telecommunications conference event or for the current, i. that already generated telecom conference event or whether this change permanent, ie. for the telecommunication conference in general (i.e. each telecom conference event of the generated telecom conference).

to Realization of this additional Feature is every sub data element and attribute with a Attribute / parameter according to the above illustration of the Conference Policy Documents indicating that this change permanently applies. Alternatively, this attribute can indicate whether the change is not is permanent.

An example of such a sub-data element is shown below:

2 shows in a simplified block diagram 200 the procedure described above.

After by the Conference Policy Server 111 a telecommunications conference is initialized (step 201 ) is in a subsequent step (step 202 ) generates the Conference Policy Document for the initialized telecommunications conference.

From the focus 105 becomes according to the Conference Policy Document, generally the conference rule file 108 generates a first conference event according to the specifications in the generated Conference Policy Document (step 203 ).

Hereinafter, according to this embodiment of the invention, it is assumed that a new subscriber is from the focus 105 is invited into the first generated conference event and also recorded (in 2 shown with block 204 ).

Upon inclusion of the new participant in the first telecommunication conference event, the Conference Policy Document is updated to include the new participant in the first telecommunication conference event (step 205 ).

After the desired information has been exchanged in the first telecommunication conference event, the first conference event is ended (step 206 ).

The steps 205 and 206 are repeatedly performed in accordance with each change in the telecommunication conference to be logged in the Conference Policy Document.

Subsequently, after a predetermined time, again, for example, according to the information in the Conference Policy Document, the focus 105 a second conference event 105 is generated, wherein the version of the Conference Policy Documents updated to include the new subscriber in the first conference event is used as part of generating the second conference event.

In this case, the new participant is automatically invited to the second conference event (step 207 ).

According to one other embodiment of the invention, which will be described below, is assumed from the <time> data element, with which among other things the beginning and / or the end of different Telecommunication conference events in a telecommunication conference (<occurence> data element).

Abb. 4: Conference Policy Document gemäß dem zweiten Ausführungsbeispiel der Erfindung In the above 1 an example is given in which the telecommunication conference event ends at 12:30 pm on December 17, 2004 (<mixing-stop-time> data element), according to this embodiment of the invention only a single conference event, ie an <occurence> Data element is specified. A second, different telecommunication conference event would be indicated by another <occurence> data element, which in turn would then indicate the beginning time and the end time of this further telecommunication conference event. According to the second embodiment of the invention, as in the following 4 which describes an illustration of a conference policy document according to the second embodiment of the invention in XML format, the above disadvantage is avoided. This principle offers advantages in the definition of conference events to be generated and carried out regularly, for example daily, weekly or monthly conference events to be generated:

Fig. 4: Conference Policy Document according to the second embodiment of the invention

According to this embodiment The invention relates to the <occurence> data element, with which defines a conference event by adding an attribute. This attribute, which in the context of this description also as Repetition information is (hereinafter referred to as "Repition" attribute, for example), and outputs the Time span until the next conference event to be generated.

The according to this embodiment The invention provides for values of the repition attribute without restriction the general public, "daily", "weekly", "biweekly", "monthly", etc. Alternatively could the Repition attribute also contains a numeric value of "hours", "days", and so on. That way a daily Conference event can be specified by the value "24hours".

According to another embodiment of the invention, the <join-handling> data element of the Conference Policy Document is functionally extended, whereby the <join-handling> data element determines, among other things, how the focus 105 to respond to an attempt by a potential new entrant to join the conference (see [5]).

there a rule for the corresponding participant with the <join-handling> data element set to the value "block", then the participant (user) does not become the conference and the associated conference event approved, i. whose conference entrance is rejected. He follows setting this rule while the participant is already in the conference or the conference event is, it is from the conference or the conference event removed as long as there is no rule that allows him in the Conference or conference event. A would have such a rule Takes precedence over an exclusion rule. If the <join-handling> data item was set to the value "allow", then the participant is entitled to join the conference or the conference event dial.

Of the latest current at the time of standardization for a conference Policy Document defined parameter "confirm" is set if the moderator of the Telecommunications Conference must be contacted in order to over the request of a possible decide new participant.

According to the state The technology can not specify which participant of the Moderator is, or it is unclear which participant in the above described case is to contact.

According to this embodiment For this reason, the invention becomes the <join-handling> sub-data item with the attribute "moderator" in the context of this Description also as moderator information designated, extended.

The Moderator attribute gives according to this embodiment the invention to which subscriber is to contact. The moderator can be specified by means of the <id> data element become. Alternatively, the corresponding subscriber to be contacted be specified by a special status, for example the status <key-participant> can be used, to not mark the moderator with an immediate address to have to, but by its function, about in turn, his address can be determined.

Abb. 5: Conference Policy Document gemäß dem dritten Ausführungsbeispiel der Erfindung An example of a conference policy document according to this embodiment of the invention is shown below in XML format:

Fig. 5: Conference Policy Document according to the third embodiment of the invention

According to one fourth embodiment The invention assumes that according to the prior art within of the current Conference Policy Documents a way to indicate whether recorded the conference or a specific conference event should or should not be.

The functionality The conference record is generally within the conferencing Frameworks [9] have been described. Information that is a record of the conference, such as the URI, by means of the The recording data can be accessed in one conference-related notification procedures as described in [10].

According to this embodiment of the invention, the determination of whether or not to record a specific conference event is made in the Conference Policy Document, generally in the conference rule file 108 This is done according to this embodiment of the invention either by the introduction of a new sub-data element within a data element of the Conference Policy Document or by the introduction of a sub-data element or attribute within the sub-data-instance.

For the above-described first variant according to this exemplary embodiment of the invention, the element of the Conference Policy Document lends itself, by means of which general settings for the conference are defined, ie, for example, the <settings> data element, as in the above 1 is shown. In this case, according to this embodiment of the invention, a new sub-data element, for example referred to as a <recorded> data element, is introduced.

A conference or conference event is recorded when the <recorded> sub-data item is set to true, so:
<Recorded> true </ recorded>

is the <recorded> sub data item is not present in the Conference Policy Document, then according to this embodiment the invention by default Value "false" ("not true "), with which the conference or the individual conference events are not to be recorded.

Should one specific conference event will not be recorded, others but already, it is necessary with this solution, the Conference To edit the policy document between each conference event because the <settings> data element and each of its subdata elements on all conference events of the generated Refer conference. In this way, the <recorded> sub data item is set if necessary or not set.

Abb. 6: Conference Policy Document gemäß dem vierten Ausführungsbeispiel der Erfindung An individual indication for each conference event as to whether it is to be recorded is made in accordance with this embodiment of the invention by the introduction of a new sub-data element within the <occurence> sub-data element. This is illustrated below by way of example in a Conference Policy Document according to this exemplary embodiment of the invention:

Fig. 6: Conference Policy Document according to the fourth embodiment of the invention

This solution has the advantage that the Conference Policy Document generally does not need to be edited before each conference event. According to the example above, the first conference event and the third conference event was recorded, but the second conference event was not.

According to one another embodiment The invention assumes that it is possible for individual authorization rule data elements or Rule data elements (the first category or the one described above second category) according to the state the technology possible is, a validity period to specify the respective rule.

This carried out in accordance with [11] and [5] using the <validity> sub-data element within of the <conditions> sub-data element. According to [11] and [5] becomes the validity period indicated by a start time and a stop time.

As Shown in the figure below is the prior art specified in the rule id = "1" rule element Service.

Abb. 7: Conference Policy Document gemäß dem fünften Ausführungsbeispiel

Fig. 7: Conference Policy Document according to the fifth embodiment

As a result the <validity> sub-data element is the corresponding authorization rule only on 17.12.2004 of 10:30 to 12:30, valid i.e. only in this period may Members of the domain "example.com" join the conference or dial in the conference event (referred to in the Conference Policy Document with <join-handling> allow </ join-handling>).

According to this embodiment According to the invention, rule id = "3" has generally been specified embodiment The invention will be incorporated into the <validity> sub-data element specific conference event (<occurence> sub-data element) is referenced. For this the corresponding <occurence> data element is referenced, for the the appropriate authorization rule, i. the corresponding authorization rule data item or rule data element valid is. According to this embodiment the invention is the rule element rule id = "3" during of the second conference event. The numbering of Conference events take place according to this embodiment of the invention in the order of their appearance in the conference Policy Document.

It It should be noted that the embodiments described above be realized in any combination with each other of the invention can, i.e. it can be any subset of all the extensions described above the Conference Policy or the Conference Policy Document, in general the conference rule files and their use as part of the administration the conferences or conference events are used.

Thus, the invention can vividly in the extension and supplement of the Conference Policy or the Conference Policy Documents, generally the conference rule file 108 to be seen to date unrealizable functionalities. The individual functionalities and their realization were described above.

• • von regelmäßigen Konferenzereignissen, beispielsweise wöchentlichen Konferenzereignissen;
• • welcher Nutzer über eine Anfrage zur Konferenz-Teilnahme entscheiden soll;
• • ob die Konferenz bzw. das Konferenzereignis aufgezeichnet werden soll. Dies kann für alle Konferenzereignisse zusammen oder für jedes Konferenzereignis separat angegeben werden;
• • ob die Conference Policy vor jedem Konferenzereignis auf den initialen Stand, der vor dem ersten Konferenzereignis existierte, zurückgesetzt wird oder ob das Conference Policy Document weitergeführt wird, womit die Änderungen, die während des oder der vorangegangen Konferenzereignisses) durchgeführt wurden, die neuen Startwerte für das nächste Konferenzereignis bilden;
• • für welches Konferenzereignis eine Autorisierungs-Regel gültig ist. Dies wird durch die Referenzierung des jeweiligen Konferenzereignisses erreicht.

In summary, the following aspects of the invention should be mentioned:
The conference policy is extended to specify

• • regular conference events, such as weekly conference events;
• • which user should decide on a request for conference participation;
• • whether the conference or conference event is to be recorded. This can be specified separately for all conference events or for each conference event;
• • whether the Conference Policy is reset to the initial state that existed prior to the first conference event, or whether the Conference Policy Document continues, with any changes made during the previous conference event (s) prior to each conference event, the new start values for form the next conference event;
• • for which conference event an authorization rule is valid. This is achieved by referencing the respective conference event.

• [1] J. Rosenberg, A framework for conferencing with the session initiation protocol, SIP Internet-Draft, IETF SIPPING working group: Draft-IETF-SIPPING-conferencing-framework-03, Oktober 2004;
• [2] 3rd Generation Partnership Project, Technical Specification Group Core Network, Conferencing Using The IP Multimedia (IM) Core Network (CN) Subsystem, Stage 3 (Release 6), 3GPP TS 24.147 V6.0.0, September 2004;
• [3] Requests for Comments (RFC) 3261, SIP: Session Initiation Protocol;
• [4] A. Johnston et al., Session Initiation Protocol Call Control – Conferencing for user agents, SIPPING Working Group, Internet Draft, IETF SIPPING Working Group: Draft-IETF-SIPPING-CC-Conferencing-06, Juli 2004;
• [5] H. Khartabil et al., The Conference Policy Control Protocol (CPCP), XCON, Internet Draft, IETF XCON Working Group: Draft IETF-XCON-CPCP-01, Oktober 2004;
• [6] H. Khartabil et al., Privileges for Manipulating a Conference Policy, XCON, Internet Draft, IETF XCON Working Group: draft-ietf-xcon-conference-policy-privileges-01, Oktober 2004;
• [7] H. Khartabil, An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usages for Conference Policy Manipulation and Conference Policy Privelges Manipulation, XCON, Internet Draft, draft-ietf-xcon-cpcp-xcap-03;
• [8] J. Rosenberg, The Extensible Markup Language (XML) Configuration Access Protocol (XCAP), SIMPLE Internet Draft, IETF SIMPLE Working group: Draft-IETF-SIMPLE-XCAP- 06, Oktober 2004;
• [9] J. Rosenberg, A Framework for Conferencing with the Session Initiation Protocol, Sipping Internet Draft, draft-ietf-sipping-conferencing-framework-03, Oktober 2004;
• [10] J. Rosenberg et al, A Session Initiation Protocol (SIP) Event Package for Conference State, Sipping Internet Draft, draft-ietf-sipping-conference-package-08, Dezember 2004;
• [11] H. Schulzrinne et al, A Document Format for Expressing Privacy Preferences, GEOPRIV Internet Draft, draft-ietf-geopriv-common-policy-03.txt, Oktober 2004.

This document cites the following publications:

• [1] J. Rosenberg, A Framework for Conferencing with Session Initiation Protocol, SIP Internet Draft, IETF SIPPING working group: Draft-IETF-SIPPING-conferencing-framework-03, October 2004;
• [2] 3rd Generation Partnership Project, Technical Specification Group Core Network, Conferencing Using The IP Multimedia (IM) Core Network (CN) Subsystem, Stage 3 (Release 6), 3GPP TS 24.147 V6.0.0, September 2004;
• [3] Requests for Comments (RFC) 3261, SIP: Session Initiation Protocol;
• [4] A. Johnston et al., Session Initiation Protocol Call Control - Conferencing for user agents, SIPPING Working Group, Internet draft, IETF SIPPING Working Group: Draft-IETF-SIPPING-CC-Conferencing-06, July 2004;
• [5] H. Khartabil et al., The Conference Policy Control Protocol (CPCP), XCON, Internet Draft, IETF XCON Working Group: Draft IETF-XCON-CPCP-01, October 2004;
• [6] H. Khartabil et al., Privileges for Manipulating a Conference Policy, XCON, Internet Draft, IETF XCON Working Group: draft-ietf-xcon-conference-policy-privileges-01, October 2004;
• [7] H. Khartabil, An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usages for Conference Policy Manipulation and Conference Policy Privilege Manipulation, XCON, Internet draft, draft-ietf-xcon-cpcp-xcap-03;
• [8] J. Rosenberg, The Extensible Markup Language (XML) Configuration Access Protocol (XCAP), SIMPLE Internet Draft, IETF SIMPLE Working group: Draft-IETF-SIMPLE-XCAP- 06, October 2004;
• [9] J. Rosenberg, A Framework for Conferencing with Session Initiation Protocol, Sipping Internet Draft, draft-ietf-sipping-conferencing-framework-03, October 2004;
• [10] J. Rosenberg et al, Session Initiation Protocol (SIP) Event Package for Conference State, Sipping Internet Draft, draft-ietf-sipping-conference-package-08, December 2004;
• [11] H. Schulzrinne et al, A Document Format for Expressing Privacy Preferences, GEOPRIV Internet Draft, draft-ietf-geopriv-common-policy-03.txt, October 2004.

100

Multimedia telecommunication conference system

101

Mobile radio terminal

102

Mobile radio terminal

103

Mobile radio terminal

104

Mobile radio terminal

105

Conference Server Setup

106

SIP signaling connection

107

SIP signaling connection

108

Conference strategy file

109

Membership Policy File

110

Media Policy File

111

Conference Policy Server

112

arrow

113

mixer

114

double arrow

115

double arrow

116

double arrow

117

double arrow

118

Floor Control Server

119

arrow

200

block diagram

201

Initialize conference

202

Produce Conference Policy

203

Produce first conference event

204

admission of a new participant in the first conference

event

205

To update Conference Policy Document

206

break up first conference event

207

Produce second conference event

Claims (31)

Method for computer-aided management of a telecommunications conference by means of a telecommunication conference server device, which at least one telecommunication conference between several Participants with several telecommunication conference events providing, wherein the telecommunication conference server device Has access to an electronic telecommunication conference rules file, being in the telecommunication conference rule file for the provided telecommunication conference version information which can be used to determine which version the telecommunication conference rule file as part of the generating a telecommunications conference event of the Telecommunications Conference is to be used, being used by the telecommunication conference server device using a new telecom conference event the version of the telecommunication conference rule file that is in the telecommunication conference rule file by means of the version information is generated is generated. The method of claim 1, wherein: the version information may indicate whether a new telecommunications conference event of the telecommunications conference is to be generated with a predetermined initialization telecommunication conference rule file, and if so, if so in that the version information indicates that a new telecommunications conference event of the telecommunication conference with a predetermined initialization telecom communication conference rule file is generated, the new telecommunication conference event is generated with the initialization telecommunication conference rule file. Method according to claim 1 or 2, • at which can be specified with the version information, whether a new one Telecommunication conference event of Telecom Conference with a telecommunications conference event provided as part of a previous one changed Telecommunication conference rule file should be generated, and • at for the case that is specified with the version information that a new telecom conference event the telecommunication conference with one in the context of a previous one Modified Telecom Conference event Telecommunications conference rule file should be generated new telecom conference event with the changed Telecommunication conference rule file is generated. Method according to one the claims 1 to 3, where a change the telecommunication conference rule file when at least one of the following events occurs: • one or several specified in the telecommunication conference rule file r) Participants of the telecommunication conference leave or leave the telecommunication conference, whereby the participant (s) from the telecommunication conference rule file deleted will be, • at least a telecom conference parameter is changed, where the telecommunication conference parameters in the telecommunication conference rule file changed accordingly becomes. Method according to one the claims 1 to 4, when changed the telecommunications conference rule file specified by a change validity information is for which telecommunication conference events the change valid is. Method according to claim 5, with the change-validity information it is stated that the change only for the already created or next Telecommunications Conference Event applies. Method according to claim 5 or 6, in which the change validity information it is stated that the change only for a predefinable number of telecommunication conference events yet to be generated applies. Method according to one the claims 1 to 7, in which the change validity information it is stated that the change permanently applies. Method for computer-aided management of a telecommunications conference by means of a telecommunication conference server device, which at least one telecommunication conference between several Participants with several telecommunication conference events providing, wherein the telecommunication conference server device Has access to an electronic telecommunication conference rules file, being in the telecommunication conference rule file for the provided telecommunication conference a repeat information is contained, by means of which it can be determined, in which temporal Distance related to a predefinable reference time after the Generating a first telecommunication conference event at least a second, to the first telecom conference event same telecom conference event is to be generated, wherein, from the telecommunication conference server device, the second telecommunication conference event generated at the time specified by the retry information becomes. Method according to claim 9, in which by the telecommunication conference server device more, same as the first telecom conference event, Telecommunication conference events to with the retry information specified times are generated. Method according to claim 9 or 10, which uses a time as the reference time that becomes dependent is from a previously generated telecommunications conference event. Method according to claim 11 in which as reference time one of the following times is used: • of the Beginning of the first generated telecommunication conference event, • the end of the first generated telecommunication conference event. Method according to one the claims 9 to 12, in which generating with the repeat information another, same telecommunications conference event according to at least one of the following time periods: • Hourly, • in one periodic distance from a predefinable number of hours, • Every day, • in one periodic distance from a predefinable number of days, • Weekly, • in one periodic distance from a predefinable number of weeks, • Per month, • in one periodic distance from a predefinable number of months, • Annually, • in one periodic distance from a predefinable number of years. Method for computer-aided management of a telecommunications conference by means of a telecommunication conference server device, which at least one telecommunication conference between several Participants with several telecommunication conference events providing, wherein the telecommunication conference server device Has access to an electronic telecommunication conference rules file, being in the telecommunication conference rule file for the provided telecommunication conference moderator information is included, which can be used to determine which participant is to contact if another participant in a generated Telecommunication conference event of Telecom Conference dial would like to, at this subscriber the permission to dial into the telecom conference event requesting from the telecommunication conference server device or from the other participant a request message to the in the Moderator information specified by the participant is transmitted, whether the other Participant is allowed to dial into the telecom conference event. Method according to claim 14 • at in the moderator information specified an address of the participant is, or • at in the moderator information a reference of the participant specified is with which a function of the subscriber within the telecommunication conference is described, and by means of which an address of the subscriber can be determined. Method for computer-aided management of a telecommunications conference by means of a telecommunication conference server device, which at least one telecommunication conference between several Participants with several telecommunication conference events providing, wherein the telecommunication conference server device Has access to an electronic telecommunication conference rules file, being in the telecommunication conference rule file for the Telecommunications Conference provided a record information which can be used to determine whether a telecom conference event the telecommunications conference being recorded, wherein a generated telecommunication conference event from the telecommunication conference server device depending on the recording information is recorded or not recorded becomes. Method for computer-aided management of a telecommunications conference by means of a telecommunication conference server device, which at least one telecommunication conference between several Participants with several telecommunication conference events providing, wherein the telecommunication conference server device Has access to an electronic telecommunication conference rules file, being in the telecommunication conference rule file for the provided telecommunication conference validity information and validity conference event information is included, which can be used to determine whether a rule within the telecommunication conference rule file for a via the validity conference event information Identified telecommunications conference event is valid, wherein from the telecommunication conference server means Telecommunication conference event is generated using the rules of the telecommunication conference rule file, which according to the validity information and the validity conference event information for the Telecommunications conference event are valid. Method according to one the claims 1 to 17, in which the communication between the participants and the telecommunications conference server device at least partially according to the session Initiation Protocol takes place. Method according to one the claims 1 to 18, in which the communication between the participants and the telecommunications conference server device at least partially according to the conference policy Control Protocol takes place. Method according to one the claims 1 to 19, in which as a telecommunication conference a multimedia telecommunication conference is provided in the participants provided several different media data streams become. Method according to one the claims 1 to 20, in which the telecommunication conference server device uniquely identified by means of a SIP Unique Resource Identifier becomes. Method according to one the claims 1 to 21, where the telecommunication conference rule file in XML format saved is. Method according to one the claims 1 to 22, at the telecom conference rule file according to the hypertext Transfer Protocol is accessed. Method according to one the claims 1 to 23, at which the participants of the telecommunications conference Data according to one Mobile communication protocol transmitted and / or received. Method according to claim 24, where the participants of the telecommunications conference data according to one 3GPP cellular communication protocol transmitted and / or received. Method according to claim 25, in which the participants of the telecommunications conference data according to one UMTS mobile communication protocol transmitted and / or received. Telecommunication conference server device, • set up to provide at least one telecommunication conference between multiple participants with multiple telecommunication conference events, • where the Telecommunication conference server device has access to one electronic telecommunication conference rule file, being in the telecommunication conference rule file for the provided telecommunication conference version information which can be used to determine which version the telecommunication conference rule file as part of the generating a telecom conference event the telecommunications conference is to be used, • where the Telecommunications conference server device is set up, a new telecom conference event using the version of the telecommunications conference rule file, the in the telecommunication conference rule file by means of the Version information is specified to generate. Telecommunication conference server device, • set up to provide at least one telecommunication conference between multiple participants with multiple telecommunication conference events, • where the Telecommunication conference server device has access to one electronic telecommunication conference rule file, being in the telecommunication conference rule file for the provided telecommunication conference a repeat information is contained, by means of which it can be determined, in which temporal Distance related to a predefinable reference time after the Generating a first telecommunication conference event at least a second, to the first telecom conference event same telecom conference event is to be generated, • where the Telecommunications conference server device is set up, the second telecommunication conference event at the time specified with the retry information produce. Telecommunication conference server equipment, • arranged to provide at least one telecommunication conference between several subscribers with a plurality of telecommunication conference events, • wherein the telecommunication conference server device has access to an electronic telecommunication conference rule file, wherein in the telecommunication conference Conference Rule File for the telecommunication conference provided is moderator information that can be used to determine which subscriber to contact when another subscriber wishes to dial into a generated telecommunications conference event of the telecommunication conference to request that subscriber to dial into the telecommunication conference event, • the telecommunication conference server being arranged to send a request message to the subscriber in the presenter information to indicate whether the other participant is allowed to dial into the telecommunications conference event. Telecommunication conference server device, • set up to provide at least one telecommunication conference between multiple participants with multiple telecommunication conference events, • where the Telecommunication conference server device has access to one electronic telecommunication conference rule file, being in the telecommunication conference rule file for the Telecommunications Conference provided a record information which can be used to determine whether a telecom conference event the telecommunications conference should be recorded • in which set up the telecommunication conference server device is dependent on a generated telecom conference event record or not record the recording information. Telecommunication conference server device, • set up to provide at least one telecommunication conference between multiple participants with multiple telecommunication conference events, • where the Telecommunication conference server device has access to one electronic telecommunication conference rule file, being in the telecommunication conference rule file for the provided telecommunication conference validity information and validity conference event information is included, which can be used to determine whether a rule within the telecommunication conference rule file for a via the validity conference event information Identified telecommunications conference event is valid, • being telecommunication conference server device is set up to generate a telecommunications conference event using the rules of the telecommunication conference rule file, which according to the validity information and the validity conference event information for the telecommunication conference event valid are.