Supporting a serial and a parallel invitation protocol

• US 7,660,850 B2
• Filed: 05/27/2005
• Issued: 02/09/2010
• Est. Priority Date: 05/27/2005
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Moore, Timothy M., Tidwell, Paul D.
• Primary Examiner(s): Najjar; Saleh
• Assistant Examiner(s): SHAW, ROBERT A
• Application Number:
  US11/140,614
• Publication Number:
  US 20060271626A1
• Time in Patent Office: 1,719 Days
• Field of Search: 709/204, 709/206, 370/261
• US Class Current: 709/204
• CPC Class Codes: H04L 65/1093 by adding participants; by removing participants
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/148 Migration or transfer of sessions

Abstract

A method and system for establishing a multiparty session with a mesh configuration by sending out invitations to endpoints in parallel is provided. To initiate a session, an initiating endpoint sends invitations in parallel to the endpoints that are to be in the session. When the initiating endpoint receives an acceptance, it then sends to the accepting endpoint an indication of the other endpoints that are currently in the session. When an accepting endpoint receives the indication of the endpoints in the session, the accepting endpoint sends an invitation to establish a dialog to each of the indicated endpoints. When an endpoint that is in the session receives such an invitation, it can automatically accept the invitation because it is already participating in the session.

Claims

1. A method in an initiating endpoint having a memory and a processor for establishing a multiparty session that has not yet been established with a full-mesh configuration, the method comprising:

sending, by the initiating endpoint, in parallel to each of a plurality of endpoints a first Session Initiation Protocol (SIP) invitation,

wherein the first SIP invitation indicates that a parallel invitation protocol is being used to establish at least a portion of the multiparty session that has not yet been established and that the invited endpoints must support the parallel invitation protocol in order to accent the first SIP invitation,

wherein an endpoint that supports the SIP parallel invitation protocol must also support the SIP serial invitation protocol, and

wherein sending first SIP invitations in parallel includes sending the first SIP invitation to a first invited endpoint and, without waiting for a response from the first invited endpoint, sending the first SIP invitation to a second invited endpoint;

each time the initiating endpoint receives a SIP response indicating an acceptance of the invitation sent in parallel from an accepting invited endpoint, sending by the initiating endpoint to the accepting invited endpoint an indication of the invited endpoints that had already accented the first SIP invitation at the time the SIP response indicating acceptance was received, wherein an endpoint that supports the parallel invitation protocol, upon receiving the indication of the invited endpoints that have already accented the first SIP invitation, sends SIP invitations to each of the indicated endpoints to establish a dialog of the multiparty session; and

after receiving, by the initiating endpoint, a rejection from an invited endpoint in response to the first SIP invitation, wherein the rejection indicates that the invited endpoint does not support the parallel invitation protocol, and wherein the rejection does not indicate that the invited endpoint does not want to participate in the multiparty session,

sending, in serial, by the initiating endpoint, to the invited endpoint that rejected the first SIP invitation a second SIP invitation,

wherein the second SIP invitation indicates that a serial invitation protocol is being used to establish at least a portion of the multiparty session that has not yet been established, and includes an indication of the invited endpoints that have already accepted the first SIP invitation at the time the SIP response indicating acceptance was received,

wherein for each second SIP invitation that is sent to an endpoint that rejected the first SIP invitation the initiating endpoint must wait for a reply to the second SIP invitation before sending a second SIP invitation to the next invited endpoint that rejected the first SIP invitation, and

wherein an endpoint that accents the second SIP invitation, upon receiving the indication of the invited endpoints that have already accepted the first SIP invitation, sends SIP invitations to each of the indicated endpoints to establish a dialog of the multiparty session.

2. The method of claim 1, further comprising:

when a SIP response indicating acceptance of an invitation to the multiparty session is received from an invited endpoint, indicating that the invited endpoint is in the session.

3. The method of claim 1, further comprising:

after the multiparty session is established, designating an endpoint of the session that supports the parallel invitation protocol as a manager so that when a new endpoint is to be added to the established session, the manager endpoint sends an invitation to the new endpoint indicating support for the parallel invitation protocol and when the new endpoint rejects the invitation, the manager endpoint sends an invitation to the new endpoint indicating support for the serial invitation protocol.

4. The method of claim 3 wherein the invitation indicating support for the serial invitation protocol identifies endpoints in the session so that the new endpoint can establish a dialog with endpoints in the session.

5. The method of claim 1 wherein an invited endpoint accepts an invitation indicating support for the parallel invitation protocol after a participant at that endpoint indicates to accept the invitation.

6. The method of claim 1 wherein an invited endpoint accepts an invitation indicating support for the serial invitation protocol automatically.

7. The method of claim 1 wherein the endpoint to which the invited endpoint sends the invitation sends an acceptance along with an indication of the protocols that the sending endpoint supports.

8. A computer-readable storage medium containing instructions for controlling an initiating endpoint to establish a multiparty session that has not yet been established with a full-mesh configuration, by a method comprising:

sending, by the initiating endpoint, in parallel to each invited endpoint that supports the parallel invitation protocol a first Session Initiation Protocol (SIP) invitation to establish a dialog, wherein the first SIP invitation indicates that a parallel invitation protocol is being used to establish at least a portion of the multiparty session, wherein each of the invited endpoints that supports the parallel invitation protocol also supports a serial invitation protocol, and wherein sending first SIP invitations in parallel includes sending the first SIP invitation to a first invited endpoint and, without waiting for a response from the first invited endpoint, sending the first SIP invitation to a second invited endpoint

after receiving an indication of an acceptance of the first SIP invitation from an invited endpoint, sending to the invited endpoint from which the acceptance of the first SIP is received an indication of the invited endpoints that, at the time the acceptance was received, had already accented a SIP invitation to the multiparty session, wherein an endpoint that supports the parallel invitation protocol, upon receiving the indication of the invited endpoints that have already accented a SIP invitation, sends a SIP invitation to each of the indicated endpoints to establish a dialog of the multiparty session with each of the indicated endpoints;

after receiving an indication of an acceptance or an indication of a rejection from each of the invited endpoints in response to the first SIP invitation, sending in serial to each invited endpoint from which an indication of a rejection indicating that the invited endpoint does not support the parallel invitation protocol and that does not indicate that the invited endpoint does not want to participate in the multiparty session was received, a second SIP invitation to establish a dialog of the multiparty session, wherein the second SIP invitation indicates support for the serial invitation protocol and that a serial invitation protocol is being used to establish at least a portion of the multiparty session, wherein the second SIP invitation includes an indication of invited endpoints that have already accepted a SIP invitation to the multiparty session at the time the second SIP invitation was sent, wherein sending second SIP invitations in serial includes sending the second SIP invitation to a first invited endpoint that sent a rejection to the first SIP invitation and waiting for a response from the first invited endpoint that sent a rejection to the first SIP invitation before sending the second SIP invitation to a second invited endpoint that sent a rejection to the first SIP invitation, and wherein an invited endpoint that accepts the second SIP invitation sends a SIP invitation to each of the endpoints indicated in the second SIP invitation to establish a dialog of the multiparty session with each of indicated endpoints; and

after receiving an indication of an acceptance from an invited endpoint, indicating that the invited endpoint is in the session.

9. The computer-readable storage medium of claim 8 including determining whether an endpoint supports the parallel invitation protocol.

10. The computer-readable storage medium of claim 9 wherein the determining is based on acceptance or rejection of an invitation indicating that the parallel invitation protocol is required.

11. The computer-readable storage medium of claim 9 wherein determining is based on checking published information of an endpoint.

12. A computer system having a memory and a processor at an endpoint for establishing a multiparty session that has not yet been established with a full-mesh configuration, the computer system comprising:

an invitation component that;

sends in parallel to each of a plurality of invited endpoints that are not in the session a first Session Initiation Protocol (SIP) invitation indicating support for a parallel invitation protocol to establish a dialog, wherein the first SIP invitation indicates that a parallel invitation protocol is being used to establish at least a portion of the multiparty session, wherein each of the invited endpoints that supports the parallel invitation protocol also supports a serial invitation protocol,

and wherein sending first SIP invitations in parallel includes sending the first SIP invitation to a first invited endpoint and sending the first SIP invitation to a second invited endpoint without waiting for a response from the first invited endpoint

after receiving from an invited endpoint an indication of acceptance of the first SIP invitation, sends to the accepting invited endpoint an indication of the invited endpoints that had already accented a SIP invitation to the multiparty session at the time the acceptance was received, wherein an endpoint that supports the parallel invitation protocol, upon receiving the indication of the invited endpoints that had already accepted a SIP invitation, sends a SIP invitation to each of the indicated endpoints to establish a dialog of the multiparty session with each of the indicated endpoints, and

after receiving an indication of an acceptance or an indication of a rejection to the first SIP invitation from each invited endpoint, sends in serial to each rejecting invited endpoint a second SIP invitation wherein the second SIP invitation indicates support for the serial invitation protocol and that a serial invitation protocol is being used to establish at least a portion of the multiparty session, wherein the second SIP invitation includes an indication of invited endpoints that had already accented a SIP invitation to the multiparty session at the time the second SIP invitation was sent, wherein sending second SIP invitations in serial includes sending the second SIP invitation to a first invited endpoint that sent a rejection to the first SIP invitation and waiting for a response from the first invited endpoint that sent a rejection to the first SIP invitation before sending the second SIP invitation to a second invited endpoint that sent a rejection to the first SIP invitation and wherein sending a SIP invitation in serial includes sending an

indication of the endpoints in the session and wherein an invited endpoint that accents the second SIP invitation sends a SIP invitation to each of the invited endpoints indicated in the second SIP invitation to establish a dialog of the multiparty session with each of indicated invited endpoints; and

a receive invite component that,

when the endpoint is not in the session,

receives an invitation to establish a dialog of the session, sends a response, and receives an indication of endpoints in the session

wherein the endpoint establishes dialogs with other endpoints in the session, and

when the endpoint is in the session,

receives an invitation to establish a dialog of the session, and sends a response

wherein the components are stored as instructions in the memory for execution by the processor.

13. The computer system of claim 12 wherein the receive invite component sends a response automatically when the endpoint is in the session and sends a response after a participant indication when the endpoint is not in the session.

14. The computer system of claim 12, further comprising:

a component to elect a manager endpoint that is responsible for sending invitations to endpoints not in the session.