Third-party session modification

• US 20070250569A1
• Filed: 07/13/2006
• Published: 10/25/2007
• Est. Priority Date: 04/25/2006
• Status: Active Grant

• Current Assignee: Nokia Technologies Oy (Nokia Corporation)
• Original Assignee: Nokia Corporation
• Inventors: Leppisaari, Arto, Mutikainen, Jari
• Granted Patent: US 8,719,342 B2
• Time in Patent Office: Days
• US Class Current: 709/204
• CPC Class Codes: H04L 12/1818 Conference organisation arrangements, e.g. handling schedules, setting up parameters needed by nodes to attend a conference, booking network resources, notifying involved parties
• CPC Class Codes: H04L 12/1822 Conducting the conference, e.g. admission, detection, selection or grouping of participants, correlating users to one or more conference sessions, prioritising transmission
• CPC Class Codes: H04L 65/1089 by adding media; by removing media
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/403 Arrangements for multi-party communication, e.g. for conferences data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15
• CPC Class Codes: H04L 65/4038 with floor control
• CPC Class Codes: H04L 65/752 adapting media to network capabilities
• CPC Class Codes: H04L 65/756 adapting media to device capabilities
• CPC Class Codes: H04W 4/16 Communication-related supplementary services, e.g. call-transfer or call-hold

Abstract

The present invention relates to a method, system, client device, conference server device and computer program product of controlling media composition in a multi-party conversation involving a central control point (50). At a participant (10) of said multi-party conversation, a scope information (SoM) which specifies members of said multi-party conversation is selected and added to a session modifying request. The session modifying request is transmitted to the central control point (50) which initiates a media modification at the specified members in response to the scope information (SoM). Thereby, a client can control whether media modification is applied to the whole conference, selected participants or only between the client itself and the conference server.

Claims

1. A method of controlling media composition, said method comprising:

a) Selecting, for a participant of a multi-party conversation, a scope information (SoM) which specifies members of said multi-party conversation;

b) adding said selected scope information (SoM) to a session modifying request;

c) transmitting said session modifying request to a central control point; and

d) initiating a media modification at said specified members in response to said scope information (SoM).

2. A method according to claim 1, further comprising adding said scope information as a header parameter of said session modifying request.

3. A method according to claim 1, further comprising adding said scope information as an attribute of said session modifying request.

4. A method according to claim 3, wherein in adding said scope information, said attribute is a Session Description Protocol attribute.

5. A method according to claim 3, wherein in adding said scope information, said scope information is added as an a-line value.

6. A method according to claim 1, further comprising specifying in said scope information whether said media modification is to be applied to said participant only, or to all members of said multi-party conversation.

7. A method according to claim 1, wherein adding said scope information includes adding a list of addresses of those participants to whom said media modification shall be applied.

8. A method according to claim 7, wherein in adding said scope information, said list of addresses includes a SIP URI-list.

9. A method according to claim 7, wherein in adding said scope information, said list of addresses includes at least one Uniform Resource Indicator of the Session Initiation Protocol.

10. A method according to claim 1, wherein in adding said scope information, said session modifying request is a re-INVITE or UPDATE request of the Session Initiation Protocol.

11. A method according to claim 1, further comprising wherein said session modifying request identifies a recipient which should contact a third party using said scope information.

12. A method according to claim 11, wherein in adding said scope information, said session modifying request includes a header parameter used to inform said central control point that an existing dialog is to be modified, instead of creating a new dialog.

13. A method according to claim 12, wherein in adding said scope information, said session modifying request includes a callee capability information which indicates in which way said existing dialog is to be modified.

14. A method according to claim 11, wherein said scope information is added as an address list.

15. A method according to claim 14, wherein said address list comprises at least one Uniform Resource Indicator of the Session Initiation Protocol.

16. A client device, said client device comprising:

a) selecting module configured to select a scope information (SoM) which specifies members of a multi-party conversation;

b) adding module configured to add said selected scope information (SoM) to a session modifying request; and

c) transmitting module configured to transmit said session modifying request to a central control point.

17. A client device according to claim 16, wherein said adding module is configured to add said scope information as a header parameter of said session modifying request.

18. A client device according to claim 16, wherein said adding module is configured to add said scope information as a message attribute of said session modifying request.

19. A client device according to claim 18, wherein in said adding module, said message attribute is a Session Description Protocol attribute and said adding module is configured to add said scope information as an a-line value.

20. A client device according to claim 16, wherein in the selecting module said scope information specifies whether said media modification is to be applied only to a participant who has transmitted said session modifying request or to all members of said multi-party conversation.

21. A client device according to claim 16, wherein said adding module is configured to add said scope information as a list of addresses of those participants to whom said media modification shall be applied.

22. A client device according to claim 21, wherein in said adding module said list of addresses comprises at least one Uniform Resource Indicator of the Session Initiation Protocol.

23. A client device according to claim 16, wherein in the adding module said session modifying request is a re-INVITE or UPDATE request of the Session Initiation Protocol.

24. A client device according to claim 16, wherein in the adding module said session modifying request identifies a recipient which should contact a third party using said scope information.

25. A client device according to claim 24, wherein in the adding module said session modifying request includes a header parameter used to inform said central control point that an existing dialog is to be modified, instead of creating a new dialog.

26. A client device according to claim 25, wherein in the adding module said session modifying request includes a callee capability information which indicates how said existing dialog is to be modified.

27. A client device according to claim 24, wherein in the adding module said scope information comprises an address list.

28. A client device according to claim 27, wherein in the adding module said address list comprises at least one Uniform Resource Indicators of the Session Initiation Protocol.

29. A conference server device, said conference server device comprising:

a) detecting module configured to detect a scope information (SoM), which specifies members of a multi-party conversation, in a received session modifying request; and

b) initiating module, responsive to said scope information, configured to initiate a media modification towards said members specified by said scope information (SoM).

30. A conference server device according to claim 29, wherein said detecting module is configured to detect said scope information in a header of said session modifying request.

31. A conference server device according to claim 29, wherein said detecting module is configured to detect said scope information in a message attribute of said session modifying request.

32. A conference server device according to claim 31, wherein in the detecting module, said message attribute is a Session Description Protocol attribute and said detecting module is configured to detect said scope information as an a-line value.

33. A conference server device according to claim 29, wherein in said initiating module, said scope information specifies whether said media modification is to be applied only to a participant who has transmitted said session modifying request or to all members of said multi-party conversation.

34. A conference server device according to claim 29, wherein said detecting module is configured to detect said scope information as a list of addresses of those participants to whom said media modification shall be applied.

35. A conference server device according to claim 34, wherein in the detecting module, said list of addresses includes at least one Uniform Resource Indicator of the Session Initiation Protocol.

36. A conference server device according to claim 29, wherein in the detecting module, said session modifying request is a re-INVITE or UPDATE request of the Session Initiation Protocol.

37. A conference server device according to claim 29, wherein in the detecting module, said session modifying request identifies a recipient which should contact a third party using said scope information.

38. A conference server device according to claim 37, wherein said detecting module is configured to detect in said session modifying request a header parameter used to inform said conference server device that an existing dialog is to be modified, instead of creating a new dialog.

39. A conference server device according to claim 38, wherein said detecting module is configured to detect in said session modifying request a callee capability information which indicates in which way said existing dialog is to be modified.

40. A conference server device according to claim 37, wherein in the detecting module, said scope information includes an address list.

41. A conference server device according to claim 40, wherein in the detecting module, said address list includes at least one Uniform Resource Indicators of the Session Initiation Protocol.

42. A computer program embodied on a computer-readable medium comprising code means for:

a) selecting, for a participant of a multi-party conversation, a scope information (SoM) which specifies members of said multi-party conversation;

b) adding said selected scope information (SoM) to a session modifying request; and

c) transmitting said session modifying request to a central control point when run on a computer device.

43. A computer program according to claim 42, wherein said computer program further comprises a user agent provided for a client device.

44. A computer program according to claim 42, further comprising:

code means for initiating a media modification at said specified members in response to said scope information (SoM) when run on a computer device.

45. A computer program according to claim 44, wherein said computer program further comprises a user agent provided for a conference server device.

46. A system, said system comprising:

at least one client device, the client device including;

a) selecting module configured to select a scope information (SoM) which specifies members of a multi-party conversation;

b) adding module configured to add said selected scope information (SoM) to a session modifying request; and

c) transmitting module configured to transmit said session modifying request to a central control point; and

a conference server device, the conference server device including;

a) detecting module configured to detect a scope information (SoM), which specifies members of a multi-party conversation, in a received session modifying request; and

b) initiating module, responsive to said scope information, configured to initiate a media modification towards said members specified by said scope information (SoM).

47. A client device, said client device comprising:

a) selecting means for selecting a scope information (SoM) which specifies members of a multi-party conversation;

b) adding means for adding said selected scope information (SoM) to a session modifying request; and

c) transmitting means for transmitting said session modifying request to a central control point.

48. A conference server device, said conference server device comprising:

a) detecting means for detecting a scope information (SoM), which specifies members of a multi-party conversation, in a received session modifying request; and

b) initiating means, responsive to said scope information, for initiating a media modification towards said members specified by said scope information (SoM).