System for routing incoming message to various devices based on media capabilities and type of media session

[0001] The present invention relates to controlling packet-switched media sessions, and in particular, relates to a composite user agent for controlling media sessions based on device capability for an associated group of devices.

[0002] The evolution of packet-switched communications now allows various types of media to be communicated over a common network to devices capable of receiving and processing compatible media. Currently, there exists an eclectic offering of devices capable of supporting data, audio, video media, alone or any combination thereof. For example, a personal computer may support all three types of media, whereas a video device may support only video media, a packet-switched telephone may support only audio media, and a personal digital assistant (PDA) may support voice and data. In essence, there are numerous devices having a mixed array of media capabilities.

[0003] In an effort to maximize the benefit of having these various media capabilities, users often have a number of devices with various media capabilities. Further, users may have more than one device with a common media capability, but may have a preference of one device over another for a given media capability, depending on quality, venue, or time of communication. Unfortunately, there is no efficient way for a user to manage communications using the various devices in light of their respective media capabilities. To establish a video session between a personal computer and another video device, the user must establish the video session, and if a related audio session should be created between the personal computer and an audio device, the user must control the establishment of a session between the personal computer and the audio device. In order to establish the separate audio and video sessions, the user must establish the respective sessions as if they were unrelated.

[0004] As such, there is a need for a way to efficiently manage multiple devices having various media capabilities. There is a further need to automate the establishment of various sessions based on the type of media and the capability of the respective devices. Where multiple devices have a common capability, there is a need for an efficient and automated way to select a preferred one of the devices to establish a media session.

[0005] The present invention relates to a composite user agent acting on behalf of a group of member user agents in a communication network. The composite user agent provides its group of member user agents with a specialized proxy function while representing the group to the network as a single user agent. To devices on the communication network, the composite user agent behaves and is viewed as a user agent. To the group of member user agents, the composite user agent behaves and is viewed as both a registrar and a proxy server.

[0006] Although the composite user agent understands the make-up of the group of member user agents, the member user agents need not have knowledge of each other or that they are being represented by the composite user agent to non-member devices. The composite user agent is configured to route incoming messages to one or more of the member user agents based on the capabilities of each of the particular member user agents. A user may configure the composite user agent to establish preferences or priorities for handling media or establishing sessions amongst the member devices.

[0007] Preferably, communications are facilitated using the Session Initiation Protocol (SIP) in accordance with the Internet Engineering Task Force's RFC 254:3: Session Initiation Protocol Internet Draft. As such, the member user agents act as typical user agents in a SIP environment and register with and are represented by the composite user agent. The composite user agent acts as a SIP proxy for the member user agents and represents the group of member user agents to network devices as a single SIP user agent.

[0008] In one embodiment, all member user agents register with the composite user agent prior to communications. The composite user agent will then register with a SIP proxy to provide an address or addresses to reach the user. After registration with the SIP proxy, all incoming SIP requests from the network are directed to the composite user agent before being passed to the appropriate member user agent. The member user agents locally configure themselves to send all SIP requests to the composite user agent. As noted, from the viewpoint of the member agent, the composite user agent will act as a proxy, handling all the responsibilities of a SIP proxy. In most cases, the composite user agent will pass all incoming SIP requests from its member user agents to the SIP proxy.

[0009] A user using a composite user agent initiates the session with another user by initiating an INVITE request from any of the member user agents. The INVITE message is addressed to the other user. The request is first sent to the composite user agent, since all member user agents have been configured to do so. The composite user agent will then forward the INVITE to the SIP proxy intact, except that the FROM and VIA headers will be altered to contain the SIP address of the composite user agent instead of the SIP address of the member user agent. Modifying these headers essentially hides the member user agent's address and ensures that subsequent request messages from the other user are sent to the composite user agent.

[0010] The composite user agent first receives any incoming INVITE request to a user since the composite user agent registered the public address of the user with the SIP proxy. The composite user agent will then determine which member user agent to forward the request to based on the content type found in the request. In forwarding the INVITE to the member user agent, the composite user agent can choose to rewrite the request, or leave the request intact as a proxy would, and simply add itself to the VIA header. The composite user agent forwards all outgoing responses received from member user agents to the SIP proxy intact, except that the FROM, CONTACT, and VIA headers are preferably altered to contain the SIP address of the composite user agent instead of the SIP address of the member user agent. Again, header manipulation hides the member user agent's address and ensures that subsequent request messages from the other user are sent to the composite user agent.

[0011] A user may add additional capabilities to a session through the existing member user agent, or by adding an additional member user agent to the session. This, is typically done by sending an INVITE request from the new member user agent to the composite user agent. The composite user agent will combine the content description from this INVITE request with the previous INVITE information used in the session to form a new multi-part MIME message body. A new multi-content INVITE is then sent to the other user, and the capabilities exchange process is carried out as would happen if the composite user agent were a single user agent application.

[0012] The other user may add a media session by sending an INVITE message to the composite user agent requesting additional media to be added to the session. The composite user agent will determine if an additional member user agent needs to be brought into the session based upon which member user agent is preferred for the requested media type. If the preferred member user agent is the member user agent already active in the session, then the composite user agent basically passes the INVITE message on to that member user agent. Otherwise, the preferred member user agent needs to be brought into the session. This is accomplished by sending an INVITE request to the preferred member user agent containing the content information pertaining to the additional media.

[0013] Sessions may be ended by having the composite user agent constrained to forwarding of BYE messages to remaining member user agents or user ancient upon receipt of a BYE message from a particular device.

[0014] Those skilled in the art will appreciate the scope of the present invention and realize additional aspects thereof after reading the following detailed description of the preferred embodiments in association with the accompanying drawing figures.

[0023] The present invention provides for an application program that acts on behalf of a group of associated devices on a communication network. The application provides its group of devices with a specialized proxy function, while representing the group to the network as a single entity. The application routes incoming messages to the various devices based on the device's media capability. One or more communication sessions may be established via the application between one or more devices based on the type of media session. Although the concepts of the present invention are applicable to various communication environments and related protocols, the present invention is preferably implemented using the Session Initiation Protocol (SIP). The specification for SIP is provided in the Internet Engineering Task Force's RFC 254.3: Session Initiation Protocol Internet Draft, which is incorporated herein by reference in its entirety.

[0024] The embodiments set forth below represent the necessary information to enable those skilled in the art to practice the invention and illustrate the best mode of practicing the invention. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the invention and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure and the accompanying claims.

[0025] As illustrated in FIG. 1, a SIP network 12 is implemented over a packet-switched network, and in association with a SIP proxy 14, facilitates media sessions between any number of endpoints 16A–16D. These endpoints may support any one or a combination of data, audio, and voice media sessions, depending on configuration of the device. Although not inclusive, typical endpoints may take the form of a personal computer (PC) 16A, a direct or wireless packet-switched compatible telephone 16B, a PDA 16C, or a gateway 16D capable of supporting any number of telephony devices or providing an interface to other networks, as will be described in more detail below. For clarity, a generic endpoint will be referenced as 16.

[0026] A SIP endpoint 16 is capable of running an application, which is typically referred to as a user agent (UA) 18, capable of facilitating media sessions using SIP. User agents 18 register their ability to establish sessions with the SIP proxy 14 by sending “REGISTER” messages to the SIP proxy 14. The register message informs the SIP proxy 14 of the SIP universal resource locator (URL) that: identifies the user agent 18 to the SIP network 12. The register message also contains information about how to reach the specific user agent 18 over the SIP network 12, typically by providing the Internet Protocol (IP) address and port that the user agent 18 will use for SIP sessions.

[0027] Typically, when a user agent 18 wants to establish a session with another user agent 18, the user agent initiating the session will send an “INVITE” message to the SIP proxy 14 and specify the targeted user agent 18 in the “TO” header of the invite message. Identification of the user agent 18 takes the form of a SIP URL. In its simplest form, the URL is represented by “<username>@<domain>,” such as “[email protected].” The SIP proxy 14 will use the SIP URL in the “TO” header of the message to determine if the targeted user agent 18 is registered with the SIP proxy 14. Generally, the user name is unique within the name space of the specified domain.

[0028] If the targeted user agent 18 has registered with the SIP proxy 14, the SIP proxy 14 will forward the invite message directly to the targeted user agent 18. The targeted user agent 18 will respond with a “200 OK” message, and a session between the respective user agents 18 will be established as per the message exchange required in the SIP specification. Media capabilities are passed between the two user agents 18 of the respective endpoints 16 as parameters embedded with the session setup messages, such as the invite, 200 OK, and acknowledgement (ACK) messages. Media capabilities may be exchanged in other messages, such as the SIP “INFO” message. Media capabilities are typically described using the Session Description Protocol (SDP). Once respective endpoints 16 are in an active session with each other and they have determined each others capabilities, the specified media content may be exchanged during an appropriate media session.

[0029] According to the Internet Engineering Task Force's RFC 2543, a user agent is an application that contains both a user agent client and a user agent server. A user agent client generally refers to a client application that initiates SIP REQUESTs, whereas a user agent server is an application that contacts the user when a SIP REQUEST is received, and returns a response on behalf of the user. Typically, the response accepts, rejects, or redirects the received REQUEST.

[0030] The present invention provides for a composite user agent 20, which is an application program that acts on behalf of a group of user agents 18, designated as member user agents 18′. The composite user agent 20 provides its group of member user agents 18′ with a specialized proxy function while representing the group to other user agents 18 over the SIP network 12 as a single user agent 18. A member user agent 18′ is a traditional user agent 18 that has registered with and is being represented by the composite user agent 20.

[0031] Preferably, to user agents 18 over the SIP network 12, the composite user agent 20 behaves and is viewed as a user agent 18 as specified in the SIP RFC 2543. Other user agents 18 interacting with the composite user agent 20 need not have knowledge of the individual member user agents 18′ represented by the composite user agent 20. The composite user agent 20 and the associated endpoints 16 implementing the member user agents 18′ form a user domain 22.

[0032] To the member user agents 18′, the composite user agent 20 behaves and is viewed as both a registrar and a proxy server, as specified in Internet Engineering Task Force's RFC 2534. The composite user agent 20 is aware of the member user agents 18′ within the user domain 22; however, the member user agents 18′ need not be aware of each other, even when two or more of the member user agents 18′ are involved in associated multimedia sessions. Preferably, the composite user agent 20 is configured to route incoming SIP REQUESTs to one or more of the member user agents 18′ based on the capabilities of the respective member user agents 18′.

[0033] In one embodiment, there is no need to modify the SIP specifications as implemented by the member user agents 18′, traditional user agents 18, or the SIP proxy 14. As such, the present invention specifies a new composite user agent 20 having a role different from the roles already defined in RFC 2543, but uses the guidelines set forth therein. Because the composite user agent 20 is viewed by devices with which it interfaces as either a user agent 18 or a proxy server 14, which are both existing SIP roles, the composite user agent 20 is compatible with all existing products that follow the SIP specification.

[0034] Continuing with FIG. 1, various types of media sessions may be established through numerous devices. As noted, these sessions may be facilitated through direct or wireless packet-switched networks using IP, Wireless Application Protocol (WAP), and the like. Communications extending to other networks may be facilitated through a gateway 16D, which also runs an application implementing a member user agent 18′. The gateway 16D may be configured to facilitate communications between the SIP network 12 and a disparate network, such as the public switched telephone network (PSTN) 24. As such, audio and data communications may be facilitated through devices supported by the PSTN 24, such as telephony device 26. Alternatively, the gateway 16D may directly support one or more telephony devices 28. Typically, these telephony devices 26, 28 incorporate circuit-switched communications, wherein the gateway 16D must be configured to translated between packet- and circuit-switched communications. Notably, the PSTN 24 may support, include, or otherwise be associated with wireless communication networks facilitating circuit-switched communications. These wireless circuit-switched networks facilitate communications with mobile terminal 30, such as wireless telephones and PDAs, through base stations 32 in traditional fashion.

[0035] Initially, all member user agents 18′ within the user domain 22 that wish to be represented by the composite user agent 20 must register with the composite user agent 20. As such, each member user agent 18′ may send a registration message to the composite user agent 20, or the composite user agent 20 may be configured with registration data corresponding to each member user agent 18′. Independent of the registration of the member user agents 18′, the composite user agent 20 should register with the proxy server 14 to provide the various addresses corresponding to the member user agents 18′ within the user domain 22. Once registration is complete, all incoming SIP REQUESTs from the SIP network 14 are directed to the composite user agent 20 before being passed to the appropriate member user agents 18′. Also note that a member user agent 18A′ or 18B′ that has registered with the composite user agent 20A may also register with the SIP proxy 14 using another address. This allows the composite user agent 20A to be bypassed when desired.

[0036] All member user agents 18′ are configured to send SIP REQUESTs to the composite user agent 20. From the viewpoint of the member user agents 18′, the composite user agent 20 acts as a proxy handling all the traditional responsibilities of a traditional SIP proxy server. In most cases, the composite user agent 20 will pass all incoming SIP REQUESTs from its member user agents 18′ to the SIP proxy 14; however, it may be desirable for the composite user agent 20 to send SIP REQUESTs directly to a remote user agent 18 using a corresponding SIP URL, if such capability is desired.

[0037] The composite user agent 20 is differentiated from a traditional SIP proxy 14 in that it can be configured to route REQUESTs to one or more of its member user agents 18′ based upon capabilities of the respective member user agents 18′. Traditionally, a SIP proxy 14 has the ability to fork REQUESTs when more than one user agent 18 is registered using the same address, but the choice is to either send the request to all, such as a multicast session, or to just one, such as a unicast session, wherein the decision is made independent of the capabilities of each user agent 18. The composite user agent 20 is different, in that it examines content information of SIP messages, such as incoming INVITE messages, and routes the message to the preferred member user agent 18′ that handles the media type specified in the message. If more than one media type is requested, the composite user agent 20 may route the message to each member user agent 18′ that is preferred for each media type.

[0038] When the user domain 22 includes member user agents 18′ supporting common media types, various types of profiles and preferences may be defined in the composite user agent 20. The profiles and preferences may dictate selection of a member user agent 18′ based on priority, timing, availability, and the like. For example, a first of two member user agents 18′ supporting a common media type may be selected during normal work hours, while the other may be selected during non-work hours. The profiles or preferences may also make these selections based on the need for additional media capabilities or the source of incoming media. Those skilled in the art will recognize numerous variations and combinations for such profiles and preferences.

[0039] The manner in which the composite user agent 20 determined which member user agent 18′ is preferred for each media type is a matter of implementation. The preferences or profiles can be provisioned on each composite user agent 20, or the composite user agent 20 could query the capabilities of each member user agent 18′ using SIP “OPTIONS” message. If the composite user agent 20 receives an INVITE message with a media type that is not supported by any of its member user agents 18′, the composite user agent 20 could respond with a “415 UNSUPPORTED MEDIA TYPE” message.

[0040] Several exemplary illustrations follow in view of the communication environment 10 illustrated in FIG. 2. As illustrated, a composite system 38, which represents, any type of computing device, is used to implement the composite user agent 20A, and includes the URL and port: 47.147.69.100:5060. The composite system 38 forms the user domain 22 with two endpoints 16: an audio device 34 implementing a member user agent 18A′, and a video device 36 implementing a member user agent 18B′. The audio device 34 has an address and port number 47.140.7.196:5060, and the video device 36 has a URL and port number 47.147.69.100:6060. As described above, the user agents 18A′ and 18B′ for the respective audio device 34 and video device 36 have registered with the composite user agent 20A of composite system 38. The user associated with the user domain 22 and the composite user agent 20A is user A.

[0041] Given the configuration of FIG. 2, the user domain 22 for user A has audio capability through audio device 34 and video capability through video device 36. In the illustrated embodiment, the video device 36 is a video camera running on composite system 38, which is a personal computer. The composite user agent 20A recognizes the respective devices and their capabilities, and has registered with the SIP proxy 14 as a single user agent on behalf of both audio device 34 and video device 36.

[0042] Assume that user A of the user domain 22 desires to participate in a media session requiring audio and video capabilities with user Z, which has an audio/video device 40, such as a multimedia personal computer having an audio device 42 find video device 44. The audio/video device 40 can facilitate audio and video sessions via the address and port 47.147.69.101:5060. The address and port for the SIP proxy 14 is 47.174.69.72:5060.

[0043] From the perspective of the SIP proxy 14 and the user agent 18 running on the audio/video device 40, the media session with user A must be established with the composite user agent 20A of the composite system 38 as if it were a traditional endpoint and user agent.

[0044] An exemplary communication flow in light of the communication environment 10 of FIG. 2 for initiating an audio session from audio device 34 is shown in FIG. 3. For user A to initiate an audio session with user Z using audio device 34, the composite user agent 20A will initiate a session with user agent 18 by initiating an INVITE message from member user agent 18A′. The INVITE message is addressed to user agent 18 for user Z's audio/video device 40. The INVITE message is first sent to the composite user agent 20A (message 1). In response, the composite user agent 20A will send a 100 TRYING message to the member user agent 18A′ (message 2), as well as forward the INVITE message to the SIP proxy 14 (message 3), substantially intact with the exception that the FROM and VIA headers will be altered to contain the SIP address of the composite user agent 20A instead of the SIP address for the member user agent 18A′. Changing the headers hides the member user agent's address and ensures that subsequent messages from other user agents 18 are sent to the composite user agent 20A. The SIP proxy 14 will forward the INVITE to the user agent 18 for user Z. For the rest of the description, various messages sent between the composite user agent 20A and user agent 18 of user Z are sent back and forth via the SIP proxy 14.

[0045] In response to forwarding the INVITE message to user Z via the SIP proxy 14, the composite user agent 20A will receive a 100 TRYING (message 4) and a 180 RINGING (message 5). In response, the composite user agent 20A will send a 180 RINGING (message 6) to the member user agent 18A′.

[0046] Meanwhile, a 200 OK (message 7) is sent to the composite user agent 20A from user Z via the SIP proxy 14, wherein the composite user agent 20A will forward the 200 OK (message 8) to the member user agent 18A′. In response, the member user agent 18A′ will provide an ACK (message 9) to the composite user agent 20A, which will forward it to user Z via the SIP proxy 14 (message 10). At this point, a media session is established for audio between the audio device 34 and the audio/video device 40.

[0047] Exemplary messages for messages 1–10 are shown in Example 1 from the viewpoint of the composite user agent 20A:

[0048]

Message 1>	INVITE sip: [email protected] SIP/2.0
	Via: SIP/2.0/UDP 47.140.7.196:5060
	From: Device A <sip: [email protected]:5060>
	To: User Z <sip: [email protected]>
	Call-ID: [email protected]
	Cseq: 1 INVITE
	Content-Type: application/sdp
	Content-Length: . . .
Message 2>	SIP/2.0 100 Trying
	Via: SIP/2.0/UDP 47.147.69.100:5060
	From: Device A <sip: [email protected]:5060>
	To: User Z <sip: [email protected]>
	Call-ID: [email protected]
	Cseq: 1 INVITE
	Content-Length: 0
Message 3>	INVITE sip:[email protected] SIP/2.0
	Via: SIP/2.0/UDP 47.147.69.100:5060
	From: User A <sip:[email protected]>
	To: User Z <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 1 INVITE
	Content-Type: application/sdp
	ConLent-Length: . . .
Message 4>	SIP/2.0 100 Trying
	Via: SIP/2.0/UDP 47.147.69.72:5060
	Via: SIP/2.0/UDP 47.147.69.101:5060
	From: User A <sip:[email protected]>
	To: User Z <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 1 INVITE
	Content-Length: 0
Message 5>	SIP/2.0 180 Ringing
	Via: SIP/2.0/UDP 47.147.69.72:5060
	Via: SIP/2.0/UDP 47.147.69.101:5060
	From: User A <sip:[email protected]>
	To: User Z <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 1 INVITE
	Content-Length: 0
Message 6>	SIP/2.0 180 Ringing
	Via: SIP/2.0/UDP 47.147.69.100:5060
	From: Device A <sip:[email protected]:5060>
	To: User Z <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 1 INVITE
	Content-Length: 0
Message 7>	SIP/2.0 200 OK
	Via: SIP/2.0/UDP 47.147.69.72:5060
	Via: SIP/2.0/UDP 47.147.69.101:5060
	From: User A <sip:[email protected]>
	To: User Z <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 1 INVITE
	Contact: sip: userZ@contactAddress
	Content-Type: application/sdp
	Content-Length: . . .
Message 8>	SIP/2.0 200 OK
	Via: SIP/2.0/UDP 47.147.69.100:5060
	From: Device A <sip:[email protected]:5060>
	To: User Z <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 1 INVITE
	Contact: sip: userA@contactAddress
	Content-Type: application/sdp
	Content-Length: . . .
Message 9>	ACK sip:userA@contactAddress SIP/2.0
	Via: SIP/2.0/UDP 47.140.7.196:5060
	From: Device A <sip:[email protected]:5060>
	To: User Z <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 1 ACK
Message 10>	ACK sip:userZ@contactAddress SIP/2.0
	Via: SIP/2.0/UDP 47.147.69.100:5060
	From: User A <sip:[email protected]>
	To: User Z <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 1 ACK

[0049] Continuing with FIG. 3, the process of receiving an INVITE message for a device within the user domain 22 is illustrated. Since the composite user agent 20A registered the public address of the user with the SIP proxy 14, the composite user agent 20A will receive any incoming INVITE messages originating from user agent 18 of user Z (message 11). The composite user agent 20A will then send a 200 TRYING message to the user agent 18 via the SIP proxy 14 (message 12). The composite user agent 20A will determine which member user agent 18A′ or 18B′ to forward the request based upon the media type identified in the INVITE message. Further, the composite user agent 20A will forward the INVITE message to member user agent 18A′ (message 13). In forwarding the INVITE message to the member user agent 18A′, the composite user agent 20A can choose to rewrite the message, for example alter the TO, VIA, and CALL ID headers, or leave the message intact as the SIP proxy 14 would, and simply add itself to the VIA header. The composite user agent 20A forwards all outgoing responses received from the respective member user agents 18A′ or 18B′ to the SIP proxy 14 intact, except that the FROM, CONTACT, and VIA headers may be altered to contain the SIP address of the composite user agent 20A instead of the SIP address For the member user agent 18A′ or 18B′. As noted above, changing these headers essentially hides the member user agent's address and ensures that subsequent INVITE messages from the user agent 18 are sent to the composite user agent 20A.

[0050] Continuing with FIG. 3, the member user agent 18A′ will respond to the forwarded INVITE message by sending a 100 TRYING (message 14) and a 180 RINGING (message 15) to the composite user agent 20A. The composite user agent 20A will forward the 180 RINGING (message 16) to the user agent 18 via the SIP proxy 14. The member user agent 18A′ will also send a 200 OK (message 17) to the composite user agent 20A for forwarding to the user agent 18 via the SIP proxy 14 (message 18). In response, the user agent 18 will send an ACK (message 19) via the SIP proxy 14 to the composite user agent 20A, which will further forward the ACK message to the member user agent 18A′ (message 20). At this point, user Z has initiated and established a session with the audio device 34 in the user domain 22. Notably, user Z did not have to select or identify the appropriate device having audio capability. Instead, the composite user agent 20A essentially represented itself as a device having audio capability on behalf of the audio device 34 and establishment of the media session occurred automatically. Exemplary messages for messages 11–20 are provided in Example 2 from the viewpoint of the composite user agent 20A.

[0051]

Message 11>	INVITE sip:[email protected]:5060 SIP/2.0
	Via: SIP/2.0/UDP 47.147.69.72:5060
	Via: SIP/2.0/UDP 47.147.69.101:5060
	From: User Z <sip:[email protected]>
	To: User A <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 1 INVITE
	Content-Type: application/sdp
	Content-Length: . . .
Message 12>	SIP/2.0 100 Trying
	Via: SIP/2.0/UDP 47.147.69.100:5060
	From: User Z <sip:[email protected]>
	To: user A <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 1 INVITE
	Content-Length: 0
Message 13>	INVITE sip:[email protected]:5060 SIP/2.0
	Via: SIP/2.0/UDP 47.147.69.100:5060
	From: User A <sip:[email protected]:5060>
	To: Device A <sip:[email protected]:5060>
	Call-ID: [email protected]
	Cseq: 1 INVITE
	Content-Type: application/sdp
	Content-Length: . . .
Message 14>	SIP/2.0 100 Trying
	Via: SIP/2.0/UDP 47.140.7.196:5060
	From: User A <sip:[email protected]:5060>
	To: Device A <sip:[email protected]:5060>
	Call-ID: [email protected]
	Cseq: 1 INVITE
	Content-Length: 0
Message 15>	SIP/2.0 180 Ringing
	Via: SIP/2.0/UDP 47.140.7.196:5060
	From: User A <sip:[email protected]:5060>
	To: Device A <sip:[email protected]:5060>
	Call-ID: [email protected]
	Cseq: 1 INVITE
	Content-Length: 0
Message 16>	SIP/2.0 180 Ringing
	Via: SIP/2.0/UDP 47.147.69.100:5060
	From: User Z <sip:[email protected]>
	To: User A <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 1 INVITE
	Content-Length: 0
Message 17>	SIP/2.0 200 OK
	Via: SIP/2.0/UDP 47.140.7.196:5060
	From: User A <sip:[email protected]:5060>
	To: Device A <sip:[email protected]:5060>
	Call-ID: [email protected]
	Cseq: 1 INVITE
	Contact: sip:deviceA@contactAddress
	Content-Type: application/sdp
	Content-Length: . . .
Message 18>	SIP/2.0 200 OK
	Via: SIP/2.0/UDP 47.147.69.100:5060
	From: User Z <sip:[email protected]>
	To: User A <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 1 INVITE
	Contact: sip: userA@contactAddress
	Content-Type: application/sdp
	Content-Length: . . .
Message 19>	ACK sip: userA@contactAddress SIP/2.0
	Via: SIP/2.0/UDP 47.147.69.72:5060
	Via: SIP/2.0/UDP 47.147.69.101:5060
	From: User Z <sip:[email protected]>
	To: User A <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 1 ACK
Message 20>	ACK sip:deviceA@contactAddress SIP/2.0
	Via: SIP/2.0/UDP 47.147.69.100:5060
	From: User A <sip:[email protected]:5060>
	To: Device A <sip:[email protected]:5060>
	Call-ID: [email protected]
	Cseq: 1 ACK

[0052] FIG. 4 illustrates an exemplary process for adding member user agent 18A′ to an existing session when initiated by user A. Assume that an audio session is established as outlined in messages 1–10 in FIG. 3.

[0053] In any SIP peer-to-peer session, participating user agents may change or add additional capabilities to a session. When using a composite user agent 20A, a user may add additional capabilities to the session through an existing member user agent 18′ or by adding an additional member user agent 18′ to the session. This may be done by sending an INVITE message from the new member user agent 18B′ to the composite user agent 20A (message 21). Ir response, the composite user agent 20A will reply with a 100 TRYING (message 22) as well as combine the content description from the INVITE (message 21) with the previous INVITE information used to establish the original session (message 1, FIG. 3) to form a new multi-part MIME message body.

[0054] MIME defines a technique whereby an object can contain a reference or pointer to data rather than having to contain the data itself. This system is embodied in the text/uri-list media type defined in the Internet Engineering Task Force's RFC1521, which is incorporated herein by reference in its entirety. In essence, MIME is a defined way to label items to make them more amenable to correct handling. The composite user agent 20A then sends the multi-content INVITE (message 23) to user agent 18 via SIP proxy 14 and the capabilities exchange process is carried out as if the composite user agent 20A were a single user agent 18. The only difference is that the composite user agent 20A must separate and route the appropriate Session Description Protocol (SDP) information to and from each member user agent 18A′, 18B′.

[0055] In response, a 200 OK (message 25) is sent to the composite user agent 20A and forwarded to member user agent 18B′ (message 26), which will respond with an ACK (message 27) to the composite user agent 20A. The composite user agent 20A forwards the ACK (message 28) to the user agent 18 via the SIP proxy 14. Exemplary messages for messages 21–28 are provided in Example 3 from the viewpoint of the composite user agent 20A.

[0056]

Message 21>	INVITE sip:[email protected] SIP/2.0
	Via: SIP/2.0/UDP 47.147.69.100:6060
	From: Device B <sip:[email protected]:6060>
	To: User Z <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 1 INVITE
	Content-Type: application/sdp
	Content-Length: . . .
Message 22>	SIP/2.0 100 Trying
	Via: SIP/2.0/UDP 47.147.69.100:5060
	From: Device B <sip:[email protected]:6060>
	To: User Z <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 1 INVITE
	Content-Length: 0
Message 23>	INVITE sip:[email protected] SIP/2.0
	Via: SIP/20/UDP 47.147.69.100:5060
	From: User A <sip:[email protected]>
	To: User Z <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 2 INVITE
	Content-Type: multipart/ . . .
	Content-Length: . . .
Message 24>	SIP/2.0 100 Trying
	Via: SIP/2.0/UDP 47.147.69.72:5060
	Via: SIP/2.0/UDP 47.147.69.101:5060
	From: User A <sip:[email protected]>
	To: User Z <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 2 INVITE
	Content-Length: 0
Message 25>	SIP/2.0 200 OK
	Via: SIP/2.0/UDP 47.147.69.72:5060
	Via: SIP/2.0/UDP 47.147.69.101:5060
	From: User A <sip:[email protected]>
	To: User Z <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 2 INVITE
	Contact: sip: userZ@contactAddress
	Content-Type: multipart/. . .
	Content-Length: . . .
Message 26>	SIP/2.0 200 OK
	Via: SIP/2.0/UDP 47.147.69.100:5060
	From: Device B <sip:[email protected]:6060>
	To: User Z <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 1 INVITE
	Contact: sip: userA@contactAddress
	Content-Type:application/sdp
	Content-Length: . . .
Message 27>	ACK sip:userA@contactAddress SIP/2.0
	Via: SIP/2.0/UDP 47.147.69.100:6060
	From: Device B <sip:[email protected]:6060>
	To: User Z <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 1 ACK
Message 28>	ACK sip:userZ@contactAddress SIP/2.0
	Via: SIP/2.0/UDP 47.147.69.100:5060
	From: User A <sip:[email protected]>
	To: User Z <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 2 ACK

[0057] FIG. 5 illustrates an exemplary process for adding a media session by the user agent 18 via the SIP proxy 14. In the event that a subsequent INVITE message is received by a composite user agent 20A requesting additional media to be added to a session, the composite user agent 20A will determine if an additional member user agent should be brought into the session. The decision is based on the member user agent preferred for the requested media type. If the preferred member user agent is currently active, the composite user agent 20A essentially passes the INVITE message on to that member user agent. Otherwise, the preferred member user agent must be brought into the session. Assume that an audio session is established as outlined in messages 1–20 in FIG. 3.

[0058] Establishing the new media session from another user agent 18 for user Z is initiated by sending an INVITE message to the composite user agent 20A via the SIP proxy 14 (message 29). In response, the composite user agent 20A will reply with a 100 TRYING (message 30) and send an INVITE message to the member user agent 18B′ for the video device 36 (message 31). Accord ingly, the member user agent 18B′ will send 100 TRYING and 200 OK messages (messages 32 and 33) to the composite user agent 20A. Upon receiving the 200 OK message from the member user agent 18B′, the composite user agent 20A will combine the content description from this response with the previous content description used in this session to form a new multipart MIME message body.

[0059] A new multi-content 200 OK message (message 34) is then sent to the user agent 183. The capabilities exchange process is carried out as if the composite user agent 20A were a single user agent application. Acknowledgement messages are forwarded through the composite user agent 20A to the member user agent 18B′ (messages 35 and 36). The only difference is that the composite user agent 20A must separate and route the appropriate SDP information to and from each member user agent 18A′ and 18B′. The example illustrated in FIG. 5 only illustrates exchanging messages with the member user agent 18B′ based on the assumption that the SDP information for the existing member user agent 18A′ has not changed. Exemplary messages for messages 29–36 are provided in Example 4 from the viewpoint of the composite user agent 20A.

[0060]

Message 29>	INVITE sip:[email protected]:5060 SIP/2.0
	Via: SIP/2.0/UDP 47.147.69.72:5060
	Via: SIP/2.0/UDp 47.147.69.101:5060
	From: User Z <sip:[email protected]>
	To: User A <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 2 INVITE
	Content-Type:multipart/. . .
	Content-Length: . . .
Message 30>	SIP/2.0 100 Trying
	Via: SIP/2.0/UDP 47.147.69.100:5060
	From: User Z <sip:[email protected]>
	To: User A <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 2 INVITE
	Content-Length: 0
Message 31>	INVITE sip:[email protected]:6060 SIP/2.0
	Via: SIP/2.0/UDP 47.147.69.100:5060
	From: User A <sip:[email protected]:5060>
	To: Device B <sip:[email protected]:6060>
	Call-ID: [email protected]
	Cseq: 1 INVITE
	Content-Type: application/sdp
	Content-Length: . . .
Message 32>	SIP/2.0 100 Trying
	Via: SIP/2.0/UDP 47.140.7.196:6060
	From: User A <sip:[email protected]:5060>
	To: Device B <sip:[email protected]:6060>
	Call-ID: [email protected]
	Cseq: 1 INVITE
	Content-Length: 0
Message 33>	SIP/2.0 200 OK
	Via: SIP/2.0/UDP 47.140.7.196:6060
	From: User A <sip:[email protected]:5060>
	To: Device B <sip:[email protected]:6060>
	Call-ID: [email protected]
	Cseq: 1 INVITE
	Contact: sip:deviceB@contactAddress
	Content-Type: application/sdp
	Content-Length: . . .
Message 34>	SIP/2.0 200 OK
	Via: SIP/2.0/UDP 47.147.69.100:5060
	From: User A <sip:[email protected]>
	To: User Z <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 2 INVITE
	Contact: sip: userA@contactAddress
	Content-Type:multipart/. . .
	Content-Length: . . .
Message 35>	ACK sip: userA@contactAddress SIP/2.0
	Via: SIP/2.0/UDP 47.147.69.72:5060
	Via: SIP/2.0/UDP 47.147.69.101:5060
	From: User A <sip:[email protected]>
	To: User Z <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 2 ACK
Message 36>	ACK sip:deviceB@contactAddress SIP/2.0
	Via: SIP/2.0/UDP 47.147.69.100:5060
	From: User A <sip:[email protected]:5060>
	To: Device B <sip:[email protected]:6060>
	Call-ID: [email protected]
	Cseq: 1 ACK

[0061] An exemplary flow for terminating sessions is outlined in FIG. 6. For user A to end a session, a BYE message may be sent from one of the member user agents, such as member user agent 18A′ (message 37), to the composite user agent 20A, which will respond with a 200 OK (message 38). The composite user agent 20A will also send the BYE message 39 to the user agent 18 of user Z via the SIP proxy 14 (message 39), and to other participating member user agents, such as member user agent 18B′ (message 40). In response, the member user agent 18B′ will send a 200 OK (message 41) to the composite user agent 20A. Meanwhile, the user agent 18 of user Z will send a 200 OK message to the composite user agent 20A (message 42) to finalize the termination of both sessions.

[0062] Example 5 shows representative messages for messages 37–42 from the viewpoint of the composite user agent 20A.

[0063]

Message 37>	BYE sip: [email protected] SIP/2.0
	Via: SIP/2.0/UDP 47.140.7.196:5060
	From: Device A <sip: [email protected]:5060>
	To: User Z <sip: [email protected]>
	Call-ID: [email protected]
	Cseq: 2 BYE
Message 38>	SIP/2.0 200 OK
	Via: SIP/2.0/UDP 47.147.69.100:5060
	From: Device A <sip:[email protected]:5060>
	To: User Z <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 2 BYE
Message 39>	BYE sip:[email protected] SIP/2.0
	Via: SIP/2.0/UDP 47.147.69.100:5060
	From: User A <sip:[email protected]>
	To: User Z <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 3 BYE
Message 40>	BYE sip:[email protected] SIP/2.0
	Via: SIP/2.0/UDP 47.147.69.100:5060
	From: User Z <sip:[email protected]>
	To: Device B <sip:[email protected]:6060>
	Call-ID: [email protected]
	Cseq: 2 BYE
Message 41>	SIP/2.0 200 OK
	Via: SIP/2.0/UDP 47.147.69.100:6060
	From: User Z <sip:[email protected]>
	To: Device B <sip:[email protected]:6060>
	Call-ID: [email protected]
	Cseq: 2 BYE
Message 42>	SIP/2.0 200 OK
	Via: SIP/2.0/UDP 47.147.69.72:5060
	Via: SIP/2.0/UDP 47.147.69.101:5060
	From: User A <sip:[email protected]>
	To: User Z <sip:[email protected]>
	Call-ID: [email protected]
	Cseq: 3 BYE

[0064] As illustrated in FIG. 7, a typical composite system 38 may include a central processing unit (CPU) 46 associated with memory 48. The memory 48 would contain the necessary software for implementing a composite user agent 20 and related data 50. A network interface 52 is also associated with the CPU 46 and facilitates packet-switched communications over the SIP network 12.

[0065] Those skilled in the art will recognize improvements and modifications to the preferred embodiments of the present invention. All such improvements and modifications are considered within the scope of the concepts disclosed herein and the claims that follow.