Sip Based Session Setup Method and Terminal Thereof

• US 20080192733A1
• Filed: 04/28/2006
• Published: 08/14/2008
• Est. Priority Date: 05/02/2005
• Status: Active Grant

• Current Assignee: LG Electronics, Inc. (LG Corporation)
• Original Assignee: LG Electronics, Inc. (LG Corporation)
• Inventors: Yoon, Kyung-Ae, Kim, Hyun-Sook, Ra, Mi-Seon, Song, Jae-Seung
• Granted Patent: US 8,817,607 B2
• Time in Patent Office: Days
• US Class Current: 370/352
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1095 Inter-network session transfer or sharing
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04L 69/24 Negotiation of communication capabilities
• CPC Class Codes: Y10S 370/912 Packet communications

Abstract

A Session Initiation Protocol (SIP) based session setup method and an terminal thereof, wherein the SIP based session setup method, in a session setup process performed between terminals in a SIP based network which includes at least one or more of the terminals and at least one or more entities, comprises sending a SIP INVITE message from a first terminal to a second terminal, receiving and analyzing the SIP INVITE message by the second terminal, and including a certain service condition in a SIP RESPONSE message, by the second terminal, and sending the SIP RESPONSE message including the service condition to the first terminal.

Claims

1. A Session Initiation Protocol (SIP) based session setup method in a session setup process performed between terminals in a SIP based network which includes at least one or more of the terminals and at least one or more entities, the method comprising:

sending a SIP INVITE message from a first terminal to a second terminal;

receiving and analyzing the SIP INVITE message by the second terminal; and

including a certain service condition in a SIP RESPONSE message, by the second terminal, and sending the SIP RESPONSE message including the service condition to the first terminal.

2. The method of claim 1, wherein the first and second terminals belong to the same network or to different networks from each other.

3. The method of claim 1, wherein the SIP INVITE message is sent from the first terminal to the second terminal via at least one or more network entities.

4. The method of claim 1, wherein the SIP RESPONSE message is sent from the second terminal to the first terminal via at least one or more network entities.

5. The method of claim 3 or 4, wherein the network entity is an Internet Protocol (IP) Multimedia Subsystems (IMS) server.

6. The method of claim 3 or 4, wherein the network entities include at least one or more Call Session Control Units (CSCFs).

7. The method of claim 1, wherein the SIP INVITE message includes a capabilities list.

8. The method of claim 7, wherein the capabilities list includes at least one or more media formats preferred by the first terminal or at least one or more codecs supported by the first terminal.

9. The method of claim 7, wherein the capabilities list includes at least one or more media formats preferred by the first terminal and at least one or more codecs supported by the first terminal.

10. The method of claim 1, wherein the certain service condition includes at least one or more capability information preferred by the second terminal or at least one or more capability information supported by the second terminal.

11. The method of claim 10, wherein the certain service condition includes either at least one or more media formats or at least one or more codecs.

12. The method of claim 10, wherein the certain service condition includes both at least one or more media formats and at least one or more codecs.

13. The method of claim 1, wherein the SIP RESPONSE message is one of a positive message, a negative message, or a separately defined RESPONSE message.

14. The method of claim 1, wherein the certain service condition is included in a body of the SIP RESPONSE message to thus be sent to the first terminal.

15. The method of claim 1, wherein the certain service condition is included in a parameter which is newly defined.

16. The method of claim 15, wherein the newly defined parameter is included in a body or header within the SIP RESPONSE message.

17. The method of claim 15, wherein the newly defined parameter is Retry-As.

18. The method of claim 1, further comprising:

receiving the SIP RESPONSE message by the first terminal to then analyze the service condition included in the SIP RESPONSE message, and thereafter recomposing a SIP INVITE message by the first terminal based upon the analysis to then send the recomposed SIP INVITE message to the second terminal.

19. A Session Initiation Protocol (SIP) based session setup method in a session setup process performed between terminals in a SIP based network which includes at least one or more of the terminals and at least one or more entities, the method comprising:

sending a SIP INVITE message including a capabilities list from a first terminal to a second terminal;

receiving the SIP INVITE message by the second terminal and then analyzing the capabilities list within the SIP INVITE message thereby;

selecting capabilities which the second terminal prefers or can support from the analyzed capabilities list; and

including a service condition requested by the second terminal and the selected capabilities in a SIP RESPONSE message, and sending the SIP RESPONSE message from the second terminal to the first terminal.

20. The method of claim 19, further comprising:

after analyzing the SIP RESPONSE message, recomposing the SIP INVITE message by the first terminal based upon the analysis and then sending the recomposed SIP INVITE message to the second terminal.

21. The method of claim 19, wherein the SIP INVITE message is sent from the first terminal to the second terminal via at least one or more network entities.

22. The method of claim 19, wherein the SIP RESPONSE message is sent from the second terminal to the first terminal via at least one or more network entities.

23. The method of claim 21 or 22, wherein the network entity is an IMS server.

24. The method of claim 21 or 22, wherein the network entities include at least one or more Call Session Control Units (CSCFs).

25. The method of claim 19, wherein the capabilities list included in the SIP INVITE message includes at least one or more capability information preferred by the first terminal or at least one or more capability information supported by the first terminal.

26. The method of claim 19 or 25, wherein the capabilities list includes either at least one or more media formats or at least one or more codecs.

27. The method of claim 19 or 25, wherein the capabilities list includes both at least one or more media formats and at least one or more codecs.

28. The method of claim 19, wherein the SIP RESPONSE message is one of a positive message or a separately defined RESPONSE message.

29. The method of claim 19, wherein the service condition is capability information preferred by the second terminal or capability information supported by the second terminal.

30. The method of claim 19, wherein the service condition is included in a body of the SIP RESPONSE message.

31. The method of claim 19, wherein the service condition is included in a newly defined parameter.

32. The method of claim 31, wherein the newly defined parameter is included in a body or header within the SIP RESPONSE message.

33. The method of claim 31, wherein the newly defined parameter is Retry-As.

34. A Session Initiation Protocol (SIP) based session setup method in a session setup process performed between terminals in a SIP based network which includes at least one or more of the terminals and at least one or more entities, the method comprising:

(a) sending a SIP INVITE message from a first terminal to a second terminal;

(b) receiving the SIP INVITE message by a first network entity;

(c) analyzing the received SIP INVITE message by the first network entity and checking a service condition of the second terminal registered in a second network entity; and

(d) including the service condition in a SIP RESPONSE message by the first network entity and then sending to the first terminal the SIP RESPONSE message including the service condition.

35. The method of claim 34, further comprising:

(e) receiving and analyzing the service condition of the second terminal and then recomposing a SIP INVITE message, by the first terminal, for setting a session with the second terminal to thereafter send the recomposed SIP INVITE message to the second terminal.

36. The method of claim 34, wherein the service condition of the second terminal includes at least one or more capability information preferred by the second terminal or at least one or more capability information supported by the second terminal.

37. The method of claim 36, wherein the capability information includes either at least one or more media formats or at least one or more codecs.

38. The method of claim 36, wherein the capability information includes both at least one or more media formats and at least one or more codecs.

39. The method of claim 34, wherein the first network entity is a Service Call Session Control Unit (CSCF).

40. The method of claim 34, wherein the second network entity is a Home Subscriber Server (HSS).

41. The method of claim 34, wherein the first network entity and the second network entity exist in the same network.

42. The method of claim 34, wherein when both the first terminal and the second terminal exist in the same network, the first network entity is a home of both the first and second terminals.

43. The method of claim 34, wherein when the first terminal and the second terminal exist in different networks each other, the first network entity is a home of the second terminal.

44. The method of claim 34, further comprising:

including a service condition requested by the second terminal in a SIP REGISTER message, by the second terminal, and then sending the SIP REGISTER message to the first network entity; and

registering the service condition within the SIP REGISTER message into the second network entity by the first network entity.

45. The method of claim 44, wherein the service condition requested by the second terminal is registered in the second network entity by use of the SIP REGISTER message while initially registering the second terminal for the use of the second terminal or while using the second terminal.

46. An terminal for setting up a SIP session through an IMS server, the terminal receives a SIP INVITE message from an originating end and thereafter sends to the originating end a certain service condition for setting up a session.

47. The terminal of claim 46, wherein the terminal sends the service condition in a body of a SIP RESPONSE message.

48. The terminal of claim 47, wherein the SIP RESPONSE message corresponds to one of a positive message, a negative message or a separately defined message.

49. The terminal of claim 46, wherein the service condition is either at least one or more capability information preferred by the terminal or at least one or more capability information supported by the terminal.

50. The terminal of claim 49, wherein the capability information includes either at least one or more media formats or at least one or more codecs.

51. The terminal of claim 49, wherein the capability information includes both at least one or more media formats and at least one or more codecs.

52. The terminal of claim 46, wherein the terminal sends the service condition included in a certain parameter, the certain parameter included in one of the SIP RESPONSE message and a separately defined RESPONSE message.

53. The terminal of claim 52, wherein the certain parameter is a newly defined parameter and implemented as Retry-As.

54. The terminal of claim 52, wherein the certain parameter is included in a body or header of one of the SIP RESPONSE message and a separately defined RESPONSE message.

55. The terminal of claim 46, wherein the terminal previously registers the service condition in a Home Subscriber Server (HSS) via at least one or more Call Session Control Units (CSCFs) before receiving the SIP INVITE message for setting up the SIP session.

56. The terminal of claim 46, wherein the terminal includes the service condition in a SIP REGISTER message and previously registers the SIP REGISTER message including the service condition in the HSS via the at least one or more CSCFs.

57. The terminal of claim 46, wherein the terminal analyzes the capabilities list included in the SIP INVITE message, selects supportable capabilities from the capabilities list, includes the service condition together with the selected capabilities in the SIP RESPONSE message, and then sending to the originating end the SIP RESPONSE message including the selected capabilities and the service condition.