EP1869919A1 - Verfahren zum bilden einer gemeinsamen kommunikationssitzung, verfahren zum bilden einer ersten kommunikationssitzung und einer zweiten kommunikationssitzung aus einer gemeinsamen kommunikationssitzung und kommunikationssitzungs-steuerungs-server - Google Patents
Verfahren zum bilden einer gemeinsamen kommunikationssitzung, verfahren zum bilden einer ersten kommunikationssitzung und einer zweiten kommunikationssitzung aus einer gemeinsamen kommunikationssitzung und kommunikationssitzungs-steuerungs-serverInfo
- Publication number
- EP1869919A1 EP1869919A1 EP06722703A EP06722703A EP1869919A1 EP 1869919 A1 EP1869919 A1 EP 1869919A1 EP 06722703 A EP06722703 A EP 06722703A EP 06722703 A EP06722703 A EP 06722703A EP 1869919 A1 EP1869919 A1 EP 1869919A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- communication session
- communication
- poc
- session
- server
- 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.)
- Withdrawn
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/56—Arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/185—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast with management of multicast group membership
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/08—Trunked mobile radio systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
- H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2207/00—Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place
- H04M2207/18—Type of exchange or network, i.e. telephonic medium, in which the telephonic communication takes place wireless networks
Definitions
- a method for forming a common communication session method for forming a first communication session and a second communication session from a common
- the invention relates to a method for forming a common communication session, a method for forming a first communication session and a second communication session from a common communication session and communication session control server.
- the push-to-talk-over-cellular (PoC) communication service (described, for example, in [1] and [4]) allows a user of a mobile subscriber device to simultaneously transmit voice data to one or more recipients.
- a special PoC key is typically provided on the mobile radio user equipment, after the operation of which the user can start to speak voice data.
- the voice data are usually already distributed during the speech by means of a mobile communication network, that is transmitted to the desired recipient or receivers. This process is called streaming.
- the transmission takes place in the half-duplex method, that is to say that during the speech and during the transmission only the transmitter, that is to say the user who interprets and transmits the voice data, can transmit voice data to the receivers but not the receivers at the same time
- the transmitter can not be interrupted by the receivers.
- communication by means of PoC from the user's point of view corresponds to the conventional CB radio, but with the extension that the transmitter can transmit voice data to receivers which can be reached by means of the suitable switching technology of at least one mobile radio communication network.
- PoC push-to-talk-over-cellular communication sessions
- PoC sessions may arise the desire, at least temporarily merge several PoC communication sessions to a common PoC communication session. This situation is illustrated below.
- Communication devices communicate with each other in a first PoC session. Users (users) A, D and E, ie their communication devices, communicate with each other simultaneously in another, second PoC session. Now User A (who is involved in both PoC sessions) realizes that the same topic is currently being discussed in both PoC sessions. Therefore, it makes sense for User A that all users of both PoC sessions can communicate together in a common PoC session (at least as long as the topic is discussed). Once the topic is over, User A then wants to let the originally separate PoC sessions (ie, the first PoC ' session and the second PoC session) run separately again, ie, let them continue independently.
- the originally separate PoC sessions ie, the first PoC ' session and the second PoC session
- Period in a common PoC session can communicate together.
- user A can use the conference state notification service to determine the participants of the second PoC session, which is to be merged with the first PoC session to form a common PoC session. Then user A loads all participants of the second PoC session individually into the first PoC session. After these users (in the example above User D and User E) have accepted this invitation, they are also participants in the first PoC session. Thus, all participants from the two PoC sessions can now communicate with each other in the common PoC session.
- PoC Session Stati States of the PoC communication sessions which were present in the second PoC session at the time of the change, ie the transition to the common PoC session, can not be used in the common first PoC session, which is continued as a common PoC session be taken into account.
- An example of such a status is here the so-called Floor Control Queue.
- Document [6] discloses a method in which a first telephone conference between a first set of communication terminals and a second telephone conference between a second set of communication terminals can be merged into a single telephone conference. Further, a conference call may be in a first conference call between a first set of communication terminals and a second conference call be divided between a second set of communication terminals.
- the invention is based on the problem, compared with the above method easier a common
- the problem is solved by a method of forming a common communication session, a method of forming a first communication session and a second communication session of a common communication session, and communication session control servers having the features of the independent claims.
- Communication session control server is controlled, wherein the second communication session is controlled by a second communication session control server, calls upon a request to merge the communication session participant communication devices in the common communication session, one of the two Communication session control server to a common communication session at the other communication session control server by means of a fusion request message. Further, one of the two communication session control servers establishes the common communication session.
- Subscriber communication devices from a common communication session wherein the first communication session is controlled by a first communication session control server, wherein the second communication session is controlled by a second communication session control server, orders the communication session participants from the first communication session sharing the common communication session to the first communication session and the second communication session, one of the two communication session control servers
- Communication session participant communication devices of the first communication session and the second communication session Furthermore, one of the two communication session control servers informs the other communication session control server by means of a split message dividing the
- a communication session control server for forming a common communication session from a first communication session with a plurality of communication session user communication devices and a second communication session with a plurality of communication session user communication devices, wherein the first communication session is controlled by the communication session control server, wherein the second Communication session from another
- Communication session control server is controlled, has a processor which is arranged such that the following method steps are feasible: • Upon a request to merge the communication session participant communication devices in the common communication session, the communication session control server requests a common communication session at the other communication session control server by means of a
- the communication session control server establishes the joint communication session.
- Another communication session control server for forming a common communication session from a first communication session with a plurality
- Communication session participant communication devices and a second communication session with a plurality of communication session participant communication devices wherein the first communication session is controlled by the communication session control server, wherein the second communication session is controlled by another communication session control server, comprises a processor adapted to establish the common communication session upon receiving a fusion request message from another communication session control server requesting a common communication session.
- a communication session control server is for forming a first communication session with a plurality of communication session user communication devices and a second communication session with a plurality of communication session user communication devices from a common communication session, wherein the first communication session is controlled by the communication session control server, wherein the second communication session is controlled by another communication session control server, the communication session control server having a processor configured such is that the following procedural steps are feasible:
- the communication session control server Upon a request to split the communication session participants from the common communication session to the first communication session and the second communication session, the communication session control server assigns the communication session user communication devices to the first communication session and the second communication session, and
- the communication session control server notifies the other communication session control server by means of a partitioning message of the splitting of the communication session user communication devices.
- this invention solves the problem in a simple manner of how to combine two sessions (communication sessions) initially running independently of one another into a group-based service (such as PoC) and also back into the two independent sessions (communication sessions). can be divided.
- a group-based service such as PoC
- the request for example in the form of a merge request message, from a communication session user communication device of the first communication session and / or from a Communication session participant Ko ⁇ imunikations adopted the second communication session is sent.
- the first communication session control server can set up the communication common session.
- a communication session identification information of the second communication session is included, for example the
- Session ID of the second communication session alternatively an indication from which the second communication session is identifiable for the second communication session control server.
- the second communication session control server may be arranged to generate an acknowledgment message and transmit it to the first communication session control server.
- the first communication session control server is reliably informed that it can vividly add the second communication session to the first communication session it controls, generally that it can merge the first communication session and the second communication session into the common communication session.
- the confirmation message contains a list of the communication session user communication devices of the second communication session, the list having a unique address of the respective one
- Communication session participant communication devices of the second communication session may include or a reference to an identification by means of which the communication session participant communication devices of the second communication session are uniquely identifiable.
- the acknowledgment message By means of the acknowledgment message thus formed, a very simple mechanism is provided for informing the first communication session control server of the communication session user communication devices of the second communication session so that they can add them to the common communication session. It should be noted in this connection that in the event that the first communication session control server establishes the common communication session, the identities or addresses of the communication session user communication devices of the first communication session are known.
- a communication session control server sets up the common communication session, which up to this time does not control any of the communication sessions that have been running so far.
- Communication session participant communication devices of the second communication session be included.
- Communication session user communication devices of the second communication session include, for example, communication right queue information indicating the future communication right assignment of the communication session user communication devices in the second communication session.
- Conference Policy Document state of the session, rules in the session, state to the users
- Media Policy Document rules of language licensing, which media may and will be used
- Conference Policy Privileges Document which rights do the users have to change the entries in the first two documents.
- This communication right queue information for example according to PoC the QueueStatus information, is taken into account in the communication right assignment in the common communication session according to an embodiment of the invention.
- Communication session participant communication devices of the first communication session and / or the second communication session takes place.
- the second communication session control server may set up the common communication session.
- a communication session identification information of the first communication session may be included in the fusion request message.
- a list of the communication session user communication devices of the first Communication session is included, wherein the list may include a unique address of the respective communication session participant communication devices of the second communication session or a reference to an identification by which the
- the fusion request message may further include information about the communication right assignment of the communication session user communication devices of the first communication session, wherein the information about the communication right assignment of the communication session user communication devices of the first communication session comprises communication right queue information may be used to indicate the future communication rights assignment of the communication session user communication devices in the first communication session.
- the communication right assignment in the common communication session is carried out according to an embodiment of the invention, taking into account the information about the communication right assignment of communication session subscriber communication devices of the first communication session and / or the second communication session.
- the communication session control server establishing the common communication session sends a fusion message to each of the subscriber servers of the communication session user communication devices of the first communication session and / or the second communication session
- this embodiment of the invention in a hierarchical structuring of
- a subscriber server (there referred to as a participant server) is provided, the corresponding assignment of the transmitted data streams (ie, both multiplexing and demultiplexing the same) on the common Kommunikatio takes over.
- the Session Initiation Protocol may be used, in other words, at least some of the messages may be encoded and transmitted according to the SIP.
- the communication sessions can be push-to-talk
- Communication sessions for example, push-to-talk-over-cellular communication sessions (PoC communication sessions, PoC sessions).
- PoC communication sessions PoC sessions
- PoC sessions PoC sessions
- the invention can also be used in the context of another communication architecture, in which a (for example, temporary) merging of two at mutually independent Ko ⁇ ununikationsssitzept to be achieved to a common communication session.
- a conference architecture in which the communication sessions are provided via the Internet, ie using the Internet Protocol (IP) and the Transport Control Protocol (TCP).
- IP Internet Protocol
- TCP Transport Control Protocol
- the invention is not dependent on the type of data transmission medium used and can be used both in a mobile communication network as well as in a fixed network communication network or in a hybrid communication network with a mobile communication subnetwork and a fixed network communication subnetwork.
- the communication sessions can thus also be conferencing sessions, for example IMS conferencing or IETF conferencing.
- all respectively available and usefully usable status information of the two communication sessions is taken into account in the context of the formation of the common communication session.
- the status information about the second communication session is transmitted from the second communication session control server to the first communication session control server.
- the second communication session control server establishes the common communication session, for example, the
- FIG. 1 is a block diagram showing a PoC
- Figure 2 is a message flow diagram illustrating the exchange of messages for forming a common communication session according to a first embodiment of the invention
- FIG. 3 is a block diagram showing a PoC
- FIG. 4 shows a message flow diagram in which the exchange of messages for dividing the common communication session formed according to FIG. 1 into two communication sessions according to the first exemplary embodiment of the invention is illustrated;
- FIG. 5 is a message flow diagram illustrating the exchange of messages for forming a common communication session according to a second embodiment of the invention and a re-division thereof into the two communication sessions;
- FIG. 6 is a block diagram illustrating a PoC communication network after a common communication session according to a second communication session Embodiment of the invention has been formed.
- Pig.l shows a PoC communication network 100 according to the prior art.
- the PoC communication network 100 according to the exemplary embodiments of the invention is designed in the same way as explained in connection with FIG. 1 except for the extensions provided according to the exemplary embodiments of the invention.
- FIG. 1 shows five PoC clients, namely a first PoC client 101, a second PoC client 102, a third PoC client 103, a fourth PoC client 104 and a fifth PoC client 105.
- Each PoC client 101, 102, 103, 104, 105 is integrated in a respective communication terminal (not shown), for example a mobile communication terminal, for example a mobile phone or a personal digital assistant (PDA), i. implemented in it.
- a mobile communication terminal for example a mobile phone or a personal digital assistant (PDA), i. implemented in it.
- PDA personal digital assistant
- Communication terminal is a respective participating PoC server 106, 107, 108, 109, 110, hereinafter also referred to as subscriber server, assigned by means of an interface and with this via a mobile communication link 111, 112, 113, 114, 115
- Air interface coupled, for example, according to one of the following mobile communication standards, such as a 3GPP (Third Generation Partnership Project) mobile communication standard: Global System for Mobile Communications (GSM);
- 3GPP Third Generation Partnership Project
- GSM Global System for Mobile Communications
- EDGE Enhanced Data Service for GSM Evolution
- UMTS Universal Mobile Telecommunications System
- the respective PoC client 101, 102, 103, 104, 105 or its communication terminal by means of a PSTN communication link, i. by means of a landline communication connection to the respective participating PoC server 106, 107, 108, 109, 110 connected.
- a controlling PoC server 116, 117 For each established PoC communication session between a plurality of PoC communication session user equipments (including the respective involved PoC clients), a controlling PoC server 116, 117, also referred to hereinafter as a PoC communication session control server, is provided.
- a respective participating PoC server 106, 107, 108, 109, 110 is connected to that controlling PoC server 116, 117, which controls a PoC communication session, in which the PoC client 101, 102, 103, 104, 105 of the respective Participating PoC server 106, 107, 108, 109, 110 subscribers.
- the first PoC client 101 is a participant in a first PoC communication session controlled by the first controlling PoC server 116.
- the first participating PoC server 106 is connected to the first controlling PoC server 116 by means of a first communication link 118.
- the first PoC client 101 is a participant in a second PoC communication session controlled by the second controlling PoC server 117.
- the first participating PoC server 106 is connected to the second controlling PoC server 117 by means of a second communication link 119.
- the second PoC client 102 is a participant of the first PoC communication session controlled by the first controlling PoC server 116. For this reason, the second participating PoC server 107 with the first controlling PoC Server 116 connected by means of a third communication connection 120.
- the third PoC client 103 is also a subscriber of the first PoC communication session controlled by the first controlling PoC server 116, for which reason the third participating PoC server 108 is connected to the first controlling PoC server 116 by means of a fourth communication connection 121.
- the fourth PoC client 104 is a subscriber of the second PoC communication session controlled by the second controlling PoC server 117, for which reason the fourth participating PoC server 109 is connected to the second controlling PoC server 117 by means of a fifth communication link 122.
- the fifth PoC client 105 is also a participant in the second PoC communication server 117 controlled by the second PoC communication session, which is why the fifth participating PoC server 110 is connected to the second controlling PoC server 117 by means of a sixth communication link 123.
- the respective participating PoC servers have a connection to the respective controlling PoC server 116, 117
- the respective controlling PoC server 116, 117 has, among other things, the functionality to manage the language assignment (floor control), generally the communication right assignment, in the context of the communication session managed by him.
- the first PoC client 101 is thus dialed in simultaneously in two PoC sessions, ie its participating PoC server 106 has connection to two different controlling PoC servers, namely to the first controlling PoC server 116 and the second controlling PoC server 117 Case that in both PoC sessions at the same time Voice messages arise, can be forwarded to the first PoC client 101 according to the prior art, only one of the two.
- FIG. 2 shows a message flow diagram 200, in which the exchange of Session Initiation Protocol (SIP) messages for forming a common communication session according to a first embodiment of the invention is shown.
- SIP Session Initiation Protocol
- a first communication session which is controlled by the first controlling PoC server 116, is established between the first PoC client 101, the second PoC client 102 and the third PoC client 103 (symbolized in FIG. 2 with block 201).
- Merging the two communication sessions is initiated to a common communication session, according to this embodiment of one of the participants at least one of the two communication sessions, according to this embodiment in more detail from the first PoC client 101, which is participant of both the first communication session and the second communication session.
- the first controlling PoC server 116 is signaled that it is the current, ie the first PoC session with another PoC session, namely the second PoC Session, should merge. This is done by the first PoC client 101 generates a request message (SessionCombineRequest) 203 and transmits to the first controlling PoC server 116, wherein the PoC Session ID (as communication session identification information) of the second PoC session is given as a parameter.
- SessionCombineRequest a request message (SessionCombineRequest) 203 and transmits to the first controlling PoC server 116, wherein the PoC Session ID (as communication session identification information) of the second PoC session is given as a parameter.
- PoC session ID 204 of the second PoC session is known to the first PoC client 101, since it is also a participant in the second PoC session.
- the first controlling PoC server 116 does not support this feature, the first PoC client 101 and thus the first user A receives a corresponding error message as a response.
- the first controlling PoC server 116 On receipt of the request message 203, the first controlling PoC server 116 sends a fusion request message (SessionTakeOverRequest) 205 to the second controlling PoC server 117 (whose address is the above-given PoC session ID of the second PoC session). With the merger request message 205, in the second controlling PoC server 117 it is queried whether the first controlling PoC server 116 can merge the first PoC session with the second PoC session controlled by the second controlling PoC server 117.
- a fusion request message SessionTakeOverRequest
- the second controlling PoC server 117 agrees with the request and indicates this to the first controlling PoC server 116 by means of a fusion acknowledgment message 206, which is generated by the second controlling PoC server 117 and transmitted to the first controlling PoC server 116.
- the fusion confirmation message 206 contains the list of the current participants of the second PoC session (user A 207 of the first PoC client 101, user D 208 of the fourth PoC Clients 104 and users E 209 of the fifth PoC client 105) and a current status of the queue (Parameter QueueStatus 210) (optional, if available) descriptive information and possibly further the status of the second PoC session descriptive parameters.
- a link to a document that contains all the statuses for the second PoC session eg a Conference Policy Document
- the first controlling PoC server 116 will also receive a corresponding error message as an answer.
- user (user) A of the first PoC client 101 sends the fusion request message (SessionCombineRequest) 203 to the second controlling PoC server 117 (in this case with the session ID of the first PoC session).
- the second controlling PoC server 117 then requests the first one
- Controlling PoC Server 116 to merge the two PoC sessions the o.g. Parameters (list of participants in the second PoC session and possibly QueueStatus) are given.
- the first controlling PoC server 116 starts to invite the participants of the second PoC session to the first PoC session 1, thus logically forming a third, common communication session.
- the first controlling PoC server 116 sends a first SIP INVITE message 211 to the fourth participating PoC server 109 and a second SIP INVITE message 212 to the fifth participating PoC server 110.
- the first SIP INVITE Message 211 and in the second SIP INVITE message 212 each have a parameter (redirect: SessionID_2) 213 included, which indicates that the data stream of the second PoC session should be redirected by the respective participating PoC server to the first PoC session ,
- parameter 213 is for signaling that it is not a SIP INVITE message according to the prior art.
- the parameter 213 is formed by a flag (redirect) with the parameter of the affected PoC session. This flag causes the respective participating PoC servers 109, 110 not to send a SIP INVITE message to the corresponding PoC clients 104, 105 (as would be done in the prior art), but vividly the second PoC session (through the Parameter 213) for the PoC user to "redirect" to the first PoC session, in other words, the participating PoC server 109, 110 now associates the PoC session of the PoC client 104, 105 with the first controlling PoC server 116 instead of the PoC second controlling PoC Server 117 (for the fourth
- Participating PoC server 109 in Fig. 2 symbolizes with block 215, symbolized for the fifth participating PoC server 110 in Fig. 2 with block 217), without the respective PoC client 104, 105 noticing something of this. If necessary, however, the PoC clients 104, 105 can also be equipped with a SIP UPDATE
- the fourth participating PoC server 109 responds to the
- the fifth participating PoC server 110 responds to receiving the second SIP INVITE message 212 with a second SIP 200 OK message 216 and sends it to the first controlling PoC server 116.
- the first controlling PoC server 116 After the first controlling PoC server 116 has received at least one of the SIP INVITE messages 211, 212 sent by it, a SIP 200 OK message 214, 216 confirming the reception, the respective positively confirming users are in the first PoC Session integrated and the first controlling PoC server 116, the two queues (if available), or, if desired or appropriate, parts thereof, merge. According to this embodiment of the invention, this is done by clearly generating the new extended queue for the "merged" common PoC session according to the zipper principle (step 218). In other words, this means that the
- Communication rights assignment queue (Queue) of the common PoC session is formed by always alternately in chronological order in the "new" communication right assignment queue (Queue) an entry from the communication right assignment queue (Queue) of the first PoC session is inserted (or maintained) and then an entry from the communication right assignment queue (Queue) of the second PoC session is inserted, etc.
- the first controlling PoC server 116 signals to the second controlling PoC server 117 that the merge has been carried out successfully. This is done by means of a communication session
- Takeover message 219 (SessionTakeOverComplete) which is generated by the first controlling PoC server 116 and sent to the second controlling PoC server 117 is transmitted.
- the first controlling PoC server 116 confirms the first PoC client 101 and thus the user A its initially sent SessionCombineRequest with a request response message 220 (SessionCombineResponse).
- the second controlling PoC server 117 Upon receiving the communication session takeover message 219, the second controlling PoC server 117 interrupts the second PoC session (symbolized with block 221 in FIG. 2).
- the first PoC session is now a common PoC session in which all five PoC clients 101, 102, 103, 104, 105 subscribers (symbolized in block 2 with block 222).
- FIG. 3 shows in a block diagram 300 the state of
- the basic structure of the PoC communication network 100 according to FIG. 3 corresponds to that shown in FIG. 1, but the communication connections between the participating PoC servers 106, 107, 108, 109, 110 and the controlling PoC servers 116, 117 are different.
- the communication links 111, 112, 113, 114, 115 between the PoC clients 101, 102, 103, 104, 105 and the participating PoC servers 106, 107, 108, 109, 110 are unchanged.
- the fourth PoC client 104 and the fifth PoC client 105 use the same connection to their participating PoC servers 109, 110 that they have previously used.
- the connection between the second controlling PoC server 117 and the first PoC client 101 or its first participating PoC server 106 is shown in dashed lines, since no media is temporarily exchanged here.
- the first PoC client 101 sends a request as a partition request message (SessionSeparateRequest) 401 to the first controlling PoC server 116, in which the ID of the PoC session stored here, i. from the "common" first PoC session, is to be released as parameter 402.
- SessionSeparateRequest a partition request message
- the first controlling PoC server 116 Upon receipt of the split request message 401, the first controlling PoC server 116 signals
- Participating PoC servers of the original participants of the second PoC session ie the fourth participating PoC Server 109 and the fifth participating PoC server 110 that the merge is terminated.
- a first SIP BYE message 403 is generated and transmitted to the fourth participating PoC server 109, wherein the PoC SessionID the original second PoC session is supplied as a parameter 404. Furthermore, the first controlling PoC server 116 generates a second SIP BYE message 405 and transmits it to the fifth participating PoC server 110, wherein the PoC session ID of the original second PoC session is supplied as parameter 406.
- the respective participating PoC servers 109, 110 take the redirection back again, so that the original status of the second PoC session is regained (for the fourth participating PoC server 109 in FIG. 4, symbolized with block 408 and for the fifth participating PoC server 110 symbolized in block 4 with block 410).
- the first controlling PoC server 116 After the first controlling PoC server 116 has received all acknowledgments (a first SIP 200 OK message 407 from the fourth participating PoC server 109 and a second SIP 200 OK message 409 from the fifth participating PoC server 110) he second controlling PoC server 117 with a session session sharing message 412 that the merge is revoked. In this case, he removes the corresponding subscribers from the temporarily shared queue (queue separation block 411) and delivers this queue 416 together with the current subscribers belonging to the second PoC session (first PoC client 101 (first subscriber 413), fourth PoC client 104 (fourth participant 414), fifth PoC client 105 (fifth participant 415)), to the second controlling PoC server as a parameter with. Further, the first controlling PoC server 116 generates a communication session sharing response message 418 (SessionSeparateResponse (OK)) and sends it to the first PoC client 101.
- a communication session sharing response message 418 SessionSeparateRe
- the second controlling PoC server 117 then resumes the original second PoC session, with the result that the two PoC sessions now again run independently of one another (step 417).
- the first PoC session now runs again with the first PoC client 101, the second PoC client 102 and the third client 103 as subscribers, controlled by the first controlling PoC server 116 (symbolized in FIG. 4 with block 419), and the second PoC Session runs again with the first PoC client 101, the fourth PoC client 104 and the fifth client 105 as a subscriber, controlled by the second controlling PoC server 117 (symbolized in Figure 4 with block 420).
- FIG. 5 shows a message flow diagram 500 in which the
- SIP Session Initiation Protocol
- the first PoC client 101 of the user A signals, without limiting the generality, to the first controlling PoC server 116 that he / she has the current PoC session, ie the first PoC session, with another PoC session, the second PoC session. should merge. This is done by means of the request message (SessionCombineRequest) 203 generated by the first PoC client 101 and transmitted to the first controlling PoC server 116, wherein the PoC session ID of the second PoC session is provided as parameter 204.
- SessionCombineRequest the request message generated by the first PoC client 101 and transmitted to the first controlling PoC server 116, wherein the PoC session ID of the second PoC session is provided as parameter 204.
- the first controlling PoC server 116 Upon receipt of the request message 203, the first controlling PoC server 116 generates a SIP INVITE message 501 and sends it to the second controlling PoC server 117, in which the first controlling PoC server 116 using a defined flag 502 (here called SessionAttachRequest ) tells the second controlling PoC server 117 that this SIP session to be set up between the two controlling PoC servers 116, 117 is intended to be used to append the second PoC session to the first PoC session.
- SessionAttachRequest a defined flag 502
- the second controlling PoC server 117 Since the second controlling PoC server 117 agrees with this, it answers positively with a positive acknowledgment message 503 and transmits the list of the current subscribers in the second PoC session (user A 504 of the first PoC) as in the first exemplary embodiment of the invention Clients 101, users D 505 of the fourth PoC client 104 and users E 506 of the fifth PoC client 105) and a descriptive of the current status of the queue (parameter QueueStatus 507) (optional, if available)
- the first controlling PoC server 116 in the same way as in the first embodiment of the invention, forms a common communication rights grant queue (step 508).
- the second controlling PoC server 117 interrupts the second PoC session (block 509 in FIG. 5).
- the first controlling PoC server 116 then signals to the first PoC client 101 and thus to the user A with a response message (SessionCombineResponse) 510 that the merging of the two PoC sessions has been carried out successfully.
- a response message SessionCombineResponse 510 that the merging of the two PoC sessions has been carried out successfully.
- the second controlling PoC server 117 suspends, as described above, the second PoC session and acts only as a relay server, all signaling and media streams (media streams) between the participating PoC servers 109, 110 from the second PoC session and exchanges PoC Server 116 with the first controlling, but does not perform any further functions.
- Figure 5 shows how a Floor Request is handled by User D.
- the fourth participating PoC server 109 sends a FloorRequest message 512 to the second controlling PoC server 117, which forwards this request to the first controlling PoC server 116.
- the response message FloorGranted 513 is sent from the first controlling PoC server 116 via the second controlling PoC server 117 to the fourth participating PoC server 109.
- the SessionID 515 of the original second PoC session is supplied as a parameter and also the new queue 519 (the queue is split into a queue for the first PoC session and a queue for the second PoC session in step 521) together with an indication of the current subscribers belonging to the second PoC session (first PoC client 101 (first subscriber 516), fourth PoC client 104 (fourth subscriber 517), fifth PoC client 105 (fifth subscriber 518)), supplied as a parameter.
- the second controlling PoC server 117 confirms this with a SIP 200 OK message 520 and resumes the original second PoC session (step 522).
- the first PoC session now runs again with the first PoC client 101, the second PoC client 102 and the third client 103 as subscribers, controlled by the first controlling PoC server 116 (symbolized in FIG. 5 with block 523), and the second PoC Session runs again with the first PoC client 101, the fourth PoC client 104 and the fifth client 105 as a subscriber, controlled by the second controlling PoC server 117 (symbolized in Figure 5 with block 524).
- FIG. 6 shows in a block diagram 600 the state of
- the basic structure of the PoC communication network 100 according to FIG. 6 corresponds to that shown in FIG. 1, but the communication connections between the participating PoC servers 106, 107, 108, 109, 110 and the controlling PoC servers 116, 117 are different.
- the communication links 111, 112, 113, 114, 115 between the PoC clients 101, 102, 103, 104, 105 and the participating PoC servers 106, 107, 108, 109, 110 are unchanged.
- the fourth PoC client 104 and the fifth PoC client 105 use the same connection to their participating PoC servers that they have previously used.
- PoC clients which are temporarily switched to another PoC session, do not need any new functionality, as the necessary functionality is provided by their respective participating PoC servers
- PoC sessions For example, in the exemplary embodiment, the second PoC session would be or the second controlling PoC server in the hierarchy under the first PoC session or under the first controlling PoC server. Such a hierarchy could be continued arbitrarily with several PoC sessions.
- the second controlling PoC server plays the role of a pure relay server (second embodiment); • Merging the two FloorControl queues into a common queue according to the zipper principle;
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Multimedia (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE102005016587A DE102005016587B4 (de) | 2005-04-11 | 2005-04-11 | Verfahren zum Bilden einer gemeinsamen Kommunikationssitzung, Verfahren zum Bilden einer ersten Kommunikationssitzung und einer zweiten Kommunikationssitzung aus einer gemeinsamen Kommunikationssitzung und Kommunikationssitzungs-Steuerungs-Server |
PCT/DE2006/000551 WO2006108379A1 (de) | 2005-04-11 | 2006-03-28 | Verfahren zum bilden einer gemeinsamen kommunikationssitzung, verfahren zum bilden einer ersten kommunikationssitzung und einer zweiten kommunikationssitzung aus einer gemeinsamen kommunikationssitzung und kommunikationssitzungs-steuerungs-server |
Publications (1)
Publication Number | Publication Date |
---|---|
EP1869919A1 true EP1869919A1 (de) | 2007-12-26 |
Family
ID=36658692
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP06722703A Withdrawn EP1869919A1 (de) | 2005-04-11 | 2006-03-28 | Verfahren zum bilden einer gemeinsamen kommunikationssitzung, verfahren zum bilden einer ersten kommunikationssitzung und einer zweiten kommunikationssitzung aus einer gemeinsamen kommunikationssitzung und kommunikationssitzungs-steuerungs-server |
Country Status (5)
Country | Link |
---|---|
US (1) | US20080155106A1 (de) |
EP (1) | EP1869919A1 (de) |
CN (1) | CN101194524B (de) |
DE (1) | DE102005016587B4 (de) |
WO (1) | WO2006108379A1 (de) |
Families Citing this family (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE102005049077B4 (de) | 2005-10-13 | 2009-02-12 | Infineon Technologies Ag | Verfahren zum Übertragen von Mediendaten, Kommunikationsnetzwerk-Einheit und Computerprogrammelement |
JP2007201916A (ja) * | 2006-01-27 | 2007-08-09 | Matsushita Electric Ind Co Ltd | PoCデータ送信方法とPoC通話システムと装置 |
KR101183328B1 (ko) * | 2006-07-10 | 2012-09-14 | 삼성전자주식회사 | PoC 세션에서 발언권 관리 규칙 전달과 적용 방법 및이를 구현하기 위한 시스템 |
EP2061212B1 (de) * | 2007-11-13 | 2018-06-20 | Cellular Communications Equipment Llc | Verfahren, Vorrichtung und Programmproduct zum Zusammenführen von Kommunikationssitzungen in einem IMS |
CN101453700B (zh) | 2007-11-30 | 2010-09-29 | 华为技术有限公司 | 一种并发媒体处理方法和设备 |
US20090248809A1 (en) * | 2008-03-28 | 2009-10-01 | International Business Machines Corporation | Instant Message Session Transfers |
US8082351B1 (en) * | 2009-05-26 | 2011-12-20 | Adobe Systems Incorporated | Software load balancing for session requests that maintain state information |
US8583830B2 (en) * | 2009-11-19 | 2013-11-12 | Oracle International Corporation | Inter-working with a walled garden floor-controlled system |
US8514749B2 (en) * | 2010-03-10 | 2013-08-20 | Microsoft Corporation | Routing requests for duplex applications |
DE102010021770B9 (de) | 2010-05-27 | 2012-05-24 | Infineon Technologies Ag | Verfahren und Vorrichtung zum Anfordern einer Medien-Replikation in einer kollaborativen Kommunikationssitzung und Verfahren und Vorrichtung zum Zuweisen eines Kommunikations-Mediums einer kollaborativen Kommunikationssitzung |
US8832284B1 (en) * | 2011-06-16 | 2014-09-09 | Google Inc. | Virtual socializing |
US9955321B2 (en) | 2015-04-08 | 2018-04-24 | Blackberry Limited | Regrouping push-to-talk groups |
EP3079383B1 (de) * | 2015-04-08 | 2018-07-04 | BlackBerry Limited | Umgruppierung von push-to-talk-gruppen |
US9510166B1 (en) * | 2015-06-29 | 2016-11-29 | Blackberry Limited | Merging active group calls |
JP2024047669A (ja) * | 2022-09-27 | 2024-04-08 | 株式会社Jvcケンウッド | 端末装置、通信方法およびプログラム |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5195086A (en) * | 1990-04-12 | 1993-03-16 | At&T Bell Laboratories | Multiple call control method in a multimedia conferencing system |
EP2271148B1 (de) * | 2000-03-03 | 2012-10-31 | Qualcomm Incorporated | Kommunikationseinrichtung und seine entsprechende Methode, um Sicherheit in einem Gruppennachrichtennetz zur Verfügung zu stellen |
US7647374B2 (en) * | 2001-07-03 | 2010-01-12 | Nokia Corporation | Method for managing sessions between network parties, methods, network element and terminal for managing calls |
EP1282280B1 (de) * | 2001-07-30 | 2003-12-17 | Alcatel | Verfahren, Steuereinrichtung und Programmmodul zur Steuerung und Lenkung von Datenströmen einer Kommunikationsverbindung zwischen Teilnehmern eines Paketdatennetzes |
US6792281B2 (en) * | 2002-06-28 | 2004-09-14 | Motorola, Inc. | Method and system for patching dispatch calling parties together |
EP1661420B1 (de) * | 2003-09-04 | 2014-09-10 | Deutsche Telekom AG | Interworking in einem drücken-zum-sprechen system |
US20050055687A1 (en) * | 2003-09-04 | 2005-03-10 | Georg Mayer | Software update information via session initiation protocol event packages |
KR100840365B1 (ko) * | 2004-07-30 | 2008-06-20 | 삼성전자주식회사 | 다중 피.오.씨 세션의 세션 결합 방법 및 그 시스템 |
KR101058707B1 (ko) * | 2004-11-11 | 2011-08-22 | 삼성전자주식회사 | 세션 분할 방법 및 서버, 세션 분할 요청 클라이언트 및 세션 분할 요청 서버 |
-
2005
- 2005-04-11 DE DE102005016587A patent/DE102005016587B4/de not_active Expired - Fee Related
-
2006
- 2006-03-28 US US11/911,230 patent/US20080155106A1/en not_active Abandoned
- 2006-03-28 CN CN2006800207956A patent/CN101194524B/zh not_active Expired - Fee Related
- 2006-03-28 EP EP06722703A patent/EP1869919A1/de not_active Withdrawn
- 2006-03-28 WO PCT/DE2006/000551 patent/WO2006108379A1/de active Application Filing
Non-Patent Citations (1)
Title |
---|
See references of WO2006108379A1 * |
Also Published As
Publication number | Publication date |
---|---|
WO2006108379A1 (de) | 2006-10-19 |
DE102005016587A1 (de) | 2006-10-19 |
US20080155106A1 (en) | 2008-06-26 |
CN101194524A (zh) | 2008-06-04 |
DE102005016587B4 (de) | 2007-11-08 |
CN101194524B (zh) | 2011-05-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
DE102005016587B4 (de) | Verfahren zum Bilden einer gemeinsamen Kommunikationssitzung, Verfahren zum Bilden einer ersten Kommunikationssitzung und einer zweiten Kommunikationssitzung aus einer gemeinsamen Kommunikationssitzung und Kommunikationssitzungs-Steuerungs-Server | |
DE102004053597B4 (de) | Verfahren zum automatischen Erzeugen und/oder Steuern einer Telekommunikations-Konferenz mit einer Vielzahl von Teilnehmern, Telekommunikations-Konferenz-Endgerät und Telekommunikations-Konferenz-Servereinrichtung | |
EP1597935B1 (de) | Verfahren zum verwalten von kommunikationssitzungen | |
DE102005037569B4 (de) | Verfahren zum Vergeben eines Kommunikationsrechts, Kommunikationskonferenz-Sitzung-Server und Kommunikationskonferenz-Sitzung-Server-Anordnung | |
DE112006001922B4 (de) | Verfahren und Vorrichtung zur Vergabe von Zugangsberechtigungen ("Floor-Control") in einem Kommunikationssystem | |
DE102005043003A1 (de) | Telekommunikationskonferenz-Server, Telekommunikations-Endgerät, Verfahren zum Erzeugen einer Telekommunikationskonferenz-Steuernachricht, Verfahren zum Steuern einer Telekommunikationskonferenz, computerlesbare Speichermedien und Computerprogrammelemente | |
DE102005010038B4 (de) | Verfahren zum Bereitstellen mehrerer Gruppen-Kommunikationsdienste, Gruppen-Kommunikationsdienst-System und Gruppen-Kommunikationsdienst-Server-Einheit | |
WO2006086939A1 (de) | Verwaltung dynamischer gruppen in einem push-to-talk over cellular kommunikationssystems | |
DE102006021375B4 (de) | Verfahren zum Aufbau einer Push-to-talk-Kommunikationsverbindung | |
DE102005042141A1 (de) | Konferenz-Kommunikationssystem, Verfahren zum Betreiben eines Konferenz-Kommunikationssystems, Notifizierungseinrichtung und Verfahren zum Notifizieren eines Kommunikationsendgeräts | |
EP2469885B1 (de) | Verfahren zur Integration von Funktionen eines Telekommunikationsnetzes in ein Datennetz | |
DE102005049077B4 (de) | Verfahren zum Übertragen von Mediendaten, Kommunikationsnetzwerk-Einheit und Computerprogrammelement | |
DE102004063298B4 (de) | Verfahren zum rechnergestützten Verwalten von Kommunikationsrechten zum Kommunizieren mittels mehrerer unterschiedlicher Kommunikationsmedien in einer Telekommunikations-Konferenz mit mehreren Telekommunikations-Einrichtungen | |
DE102005039668B4 (de) | Verfahren zum rechnergestützten Bilden einer Konferenzsitzungs-Einladungsnachricht, Verfahren zum rechnergestützten Erzeugen einer Konferenzsitzung, Verfahren zum rechnergestützten Verarbeiten von Nachrichten in einer Konferenzsitzung, Konferenzsitzungs-Einladungsnachricht-Erzeugungseinheit, Konferenzsitzungs-Erzeugungseinheit und Kommunikations-Endgeräte | |
DE102004010925B9 (de) | Verfahren und Kommunikationsanordnung zum Aufbauen einer Push-to-talk-Kommunikationsverbindung und Push-to-talk-Client-Einheit | |
DE102005049074B4 (de) | Verfahren zum rechnergestützten Vergeben eines Kommunikationsrechts, Verfahren zum rechnergestützten Erzeugen einer Kommunikationsrecht-Anforderungsnachricht, Kommunikationsrecht-Vergabe-Einheit, Kommunikations-Konferenz-Servereinheit, Kommunikations-Konferenz-Nachricht-Erzeugungseinheit, Kommunikations-Endgerät und Verfahren zum rechnergestützten Initialisieren eines Konferenz-Nachrichtenflusses in einer Kommunikations-Konferenz | |
DE102010021770B4 (de) | Verfahren und Vorrichtung zum Anfordern einer Medien-Replikation in einer kollaborativen Kommunikationssitzung und Verfahren und Vorrichtung zum Zuweisen eines Kommunikations-Mediums einer kollaborativen Kommunikationssitzung | |
DE102005043006B4 (de) | Kommunikationssystem, Kommunikationssitzungs-Server-Einheit, Medienverteilungs-Einheit und Verfahren zum Übertragen von Daten im Rahmen einer Kommunikationssitzung | |
DE102008045425B3 (de) | Verfahren zur Ermittlung aktiver Kommunikationssitzungen, Kommunikationssitzungs-Informationsserver, Verfahren zum Bereitstellen einer Information über aktive Kommunikationssitzungen und Dokumentenmanagement-Server | |
WO2009153176A1 (de) | Verfahren zur ermittlung aktiver kommunikationssitzungen und kommunikationssitzungs-informationsserver | |
DE102005007342B4 (de) | Kommunikationssystem und Verfahren zum Betreiben eines Kommunikationssystems | |
DE102004005720B3 (de) | Verfahren zum Verwalten von Kommunikationssitzungen | |
DE102005053914B4 (de) | Kommunikationssystem, Verfahren zum Betreiben eines Kommunikationssystems, Server-Einheit, Verfahren zum Betreiben einer Server-Einheit, Kommunikationsdienst-Client-Einheit und Verfahren zum Betreiben einer Kommunikationsdienst-Client-Einheit | |
DE102008048880B4 (de) | Verfahren, Vorrichtung und Computerprogrammprodukt zum Ausgeben von Kommunikationsbeiträgen einer Konferenz und Verfahren, Vorrichtung und Computerprogrammprodukt zum Erzeugen einer Nachricht mit einem Kommunikationsbeitrag einer Konferenz | |
DE102004041884A1 (de) | Kommunikationsendgerät und Verfahren zum Steuern eines Kommunikationsendgeräts |
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: 20070925 |
|
AK | Designated contracting states |
Kind code of ref document: A1 Designated state(s): DE GB |
|
DAX | Request for extension of the european patent (deleted) | ||
RBV | Designated contracting states (corrected) |
Designated state(s): DE GB |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: INTEL MOBILE COMMUNICATIONS GMBH |
|
17Q | First examination report despatched |
Effective date: 20120515 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20141001 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R079 Free format text: PREVIOUS MAIN CLASS: H04Q0007280000 Ipc: H04W0088080000 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R079 Free format text: PREVIOUS MAIN CLASS: H04Q0007280000 Ipc: H04W0088080000 Effective date: 20150311 |