Session set-up between two communication entities

• US 20070118659A1
• Filed: 01/12/2006
• Published: 05/24/2007
• Est. Priority Date: 11/22/2005
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Artamo, Atte, Cuny, Renaud, Martikainen, Anssi
• Application Number:
  US11/330,190
• Publication Number:
  US 20070118659A1
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1094 Inter-user-equipment sessions transfer or sharing
• CPC Class Codes: H04L 69/24 Negotiation of communication capabilities

Abstract

An improved session set-up between communication entities over a communication network, wherein a communication entity performs the steps of receiving, from a requesting communication entity, a request for setting up a desired session, including desired session attribute information of the requesting communication entity; retrieving matching capability attribute information of the communication entity on the basis of a target application for the desired session; and sending a first response to the requesting communication entity, including the retrieved capability attribute information of the communication entity.

Claims

1. A method of setting up a desired session between first and second communication entities over a communication network, wherein the second communication entity performs the steps of:

receiving, from the first communication entity, a request for setting up the desired session, including desired session attribute information of the first communication entity;

retrieving matching capability attribute information of the second communication entity on the basis of a target application for the desired session; and

sending a first response to the first communication entity, including the retrieved capability attribute information of the second communication entity.

2. The method according to claim 1, wherein the step of retrieving further comprises a step of:

retrieving the matching capability attribute information from previously stored capability information of applications supported by the second communication entity.

3. The method according to claim 2, further comprising the step of:

maintaining the previously stored capability information in the second communication entity.

4. The method according to claim 2, further comprising the step of:

maintaining the previously stored capability information in an updated manner for every application which has been launched at least once at the second communication entity.

5. The method according to claim 1, wherein the step of retrieving matching capability information is independent of an operating state of the target application.

6. The method according to claim 1, further comprising the step of:

configuring in the first response an inactive indication indicating that the second communication entity is not prepared for exchanging content relating to the desired session with the first communication entity.

7. The method according to claim 1, wherein the second communication entity further performs the step of:

launching the target application for the desired session.

8. The method according to claim 7, wherein the step of launching the target application further comprises a step of:

starting application components required for the target application.

9. The method according to claim 7, further comprising the step of:

performing the steps of retrieving matching capability attribute information and sending a first response in parallel or prior to the step of launching the target application.

10. The method according to claim 7, wherein the second communication entity further performs a step of:

sending a second response to the first communication entity, including an active indication indicating that the second communication entity is prepared for exchanging content relating to the desired session with the first communication entity.

11. The method according to claim 10, further comprising the step of:

performing the step of sending a second response after the target application is launched.

12. The method according to claim 1, wherein the request, the first response and the second response are in accordance with a session initiation protocol, SIP.

13. The method according to claim 12, wherein the session attribute information is in accordance with a session description protocol, SDP.

14. The method according to claim 12, wherein the request is a SIP INVITE message.

15. The method according to claim 12, wherein the first response is a SIP SESSION PROGRESS message.

16. The method according to claim 12, wherein the first response is a SIP RINGING message.

17. The method according to claim 1, wherein the desired session is a multimedia session.

18. The method according to claim 17, wherein the content exchange in the desired session is based on a real-time protocol, RTP.

19. The method according to claim 10, wherein the second response is a RTP dummy packet.

20. The method according to claim 1, wherein the communication network is a mobile communication network.

21. The method according to claim 1, wherein the communication network is an Internet Protocol based multimedia subsystem, IMS.

22. A communication entity being configured for setting up a desired session with another communication entity over a communication network, comprising:

transceiver means for sending to and receiving from a requesting communication entity;

said transceiver means being configured to receive, a request for setting up the desired session, including desired session attribute information of the requesting communication entity; and

retrieving means for retrieving matching capability attribute information of the communication entity on the basis of a target application for the desired session, and

said transceiver means being further configured to send a first response to the requesting communication entity, including the retrieved capability attribute information of the communication entity.

23. The communication entity according to claim 22, wherein the retrieving means is further configured to retrieve the matching capability attribute information from previously stored capability information of applications supported by the communication entity.

24. The communication entity according to claim 23, further comprising:

storage means for maintaining the previously stored capability information.

25. The communication entity according to claim 23, wherein the previously stored capability information is maintained in an updated manner for every application which has been launched at least once at said communication entity.

26. The communication entity according to claim 25, wherein the capability information of a new application is stored upon installation of the new application.

27. The communication entity according to claim 22, wherein the retrieving means operates independent of an operating state of the target application.

28. The communication entity according to claim 22, wherein the first response further includes an inactive indication indicating that the communication entity is not prepared for exchanging content relating to the desired session with the requesting communication entity.

29. The communication entity according to claim 22, further comprising:

application means for launching the target application for the desired session.

30. The communication entity according to claim 29, wherein the application means is further configured to start application components required for the target application.

31. The communication entity according to claim 29, wherein the retrieving and transceiver means are configured to retrieve matching capability attribute information and to send a first response in parallel or prior to launching of the target application by the application means.

32. The communication entity according to claim 29, wherein the transceiver means is further configured to send a second response to the requesting communication entity, including an active indication indicating that the communication entity is prepared for exchanging content relating to the desired session with the requesting communication entity.

33. The communication entity according to claim 32, wherein the transceiver means is further configured to send the second response after the target application is launched by the application means.

34. The communication entity according to claim 22, wherein the request, the first response and the second response are in accordance with a session initiation protocol, SIP.

35. The communication entity according to claim 34, wherein the session attribute information is in accordance with a session description protocol, SDP.

36. The communication entity according to claim 22, wherein the communication entity is a terminal device.

37. The communication entity according to claim 22, wherein the communication entity acts as a client entity.

38. The communication entity according to claim 22, wherein the communication entity acts as a server entity.

39. A computer program embodied in a computer-readable medium comprising program code configured to set-up a desired session between first and second communication entities over a communication network, the computer program being configured to perform the steps of:

receiving, from the first communication entity, a request for setting up the desired session, including desired session attribute information of the first communication entity;

retrieving matching capability attribute information of the second communication entity on the basis of a target application for the desired session; and

sending a first response to the first communication entity, including the retrieved capability attribute information of the second communication entity.