METHOD, GATEW AND SYSTEM FOR PROVIDING A PUSH-TO-X SERVICE TO A USER OF A DATA TERMINAL

• US 20100226286A1
• Filed: 05/31/2007
• Published: 09/09/2010
• Est. Priority Date: 05/31/2007
• Status: Active Grant

• Current Assignee: Telecom Italia S.p.A.
• Original Assignee: Telecom Italia S.p.A.
• Inventors: Rossotto, Mauro, Spelta, Stefano, Perrucci, Alessandro, Cena, Piero
• Granted Patent: US 8,184,558 B2
• Time in Patent Office: Days
• US Class Current: 370/259
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• CPC Class Codes: H04L 61/5084 Providing for device mobility network addressing or numbering for mobility support in wireless networks H04W8/26; mobile IP H04W80/04
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/103 in the network
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/4061 Push-to services, e.g. push-to-talk or push-to-video
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04W 76/45 for Push-to-Talk [PTT] or Push-to-Talk over cellular [PoC] services

Abstract

A method of providing a push-to-x service to a user of a data terminal which is connected to a packet-switched network includes, at a gateway interfacing the packet-switched network and the framework supporting the push-to-x service: receiving from the data terminal a request for accessing the push-to-x service; checking a user class to which the user belongs; and, according to the user class, assigning a push-to-x identity to the user either by selecting the push-to-x identity from a set of predefined push-to-x identities, or by retrieving the push-to-x identity from a user profile table; and accessing the framework and the push-to-x service by using the push-to-x identity.

Claims

1-32. -32. (canceled)

33. A method of providing a push-to-x service to a user of a data terminal which is connected to a packet-switched network, comprising, at a gateway interfacing said packet-switched network and a framework supporting said push-to-x service:

a) receiving from said data terminal a request for accessing said push-to-x service;

b) checking a user class to which said user belongs and, according to said user class, assigning a push-to-x identity to said user;

either by selecting said push-to-x identity from a set of predefined push-to-x identities;

or

by retrieving said push-to-x identity from a user profile table; and

c) accessing said framework and said push-to-x service by using said push-to-x identity.

34. The method according to claim 33, wherein step b) further comprises, in case said push-to-x identity is selected from said set of predefined push-to-x identities, storing said push-to-x identity for a single session of said push-to-x service.

35. The method according to claim 33, wherein step b) comprises, in case said push-to-x identity is retrieved from said user profile table, retrieving from said user profile table, said push-to-x identity which has been previously selected by said gateway from said set of predefined push-to-x identities during a gateway registration operation performed by said user.

36. The method according to claim 33, wherein step b) comprises, in case said push-to-x identity is retrieved from said user profile table, retrieving from said user profile table said push-to-x identity which is provided by said user to said gateway during a gateway registration operation performed by said user, said push-to-x identity identifying a mobile phone configured for accessing said push-to-x service through a push-to-x client.

37. The method according to claim 33, wherein step a) comprises receiving a user identifier of said user.

38. The method according to claim 33, wherein step a) comprises receiving a streaming content format supported by said data terminal.

39. The method according to claim 33, wherein step a) comprises receiving a discrete content format supported by said data terminal.

40. The method according to claim 33, further comprising associating with said user a service event channel identifier identifying a service event channel to be used for exchanging at least one signalling message relating to said push-to-x service.

41. The method according to claim 33, further comprising associating with said user a media streaming channel identifier identifying a media streaming channel to be used for exchanging at least one streaming content during said push-to-x service.

42. The method according to claim 33, further comprising transmitting a notification message from said gateway to said data terminal for informing said user that said push-to-x service has been accessed.

43. The method according to claim 33, further comprising transmitting to said data terminal information indicative of at least one contact of said user, said information allowing said data terminal to display said at least one contact.

44. The method according to claim 43, further comprising:

receiving from said framework a presence update information relating to a presence status of said at least one contact; and

updating said presence status of said at least one contact according to said presence update information.

45. The method according to claim 43, further comprising:

receiving from said data terminal a request for modifying said at least one contact; and

modifying said at least one contact according to said request.

46. A gateway for interfacing a packet-switched network and a framework supporting a push-to-x service, comprising:

a′

) a push-to-x service access application capable of being configured to receive a request for accessing said push-to-x service from a data terminal of a user when said data terminal is connected to said packet-switched network;

b′

) an authentication manager capable of being configured to check a user class to which said user belongs and, according to said user class, assigning a push-to-x identity to said user;

either by selecting said push-to-x identity from a set of predefined push-to-x identities;

or

by retrieving said push-to-x identity from a user profile table; and

c′

) a signaling message interface capable of being configured to exchange with said framework at least one signaling message allowing said user to access said push-to-x service by using said push-to-x identity.

47. The gateway according to claim 46, wherein said authentication manager is further capable of being configured to, in case said push-to-x identity is selected from said set of predefined push-to-x identities, store said push-to-x identity for a single session of said push-to-x service.

48. The gateway according to claim 46, wherein said authentication manager is further capable of being configured to, in case said push-to-x identity is retrieved from said user profile table, retrieve from said user profile table said push-to-x identity which has been previously selected by said gateway from said set of predefined push-to-x identities during a gateway registration operation performed by said user.

49. The gateway according to claim 46, wherein said authentication manager is further capable of being configured to, in case said push-to-x identity is retrieved from said user profile table, retrieve from said user profile table said push-to-x identity which is provided by said user to said gateway during a gateway registration operation performed by said user, said push-to-x identity identifying a mobile phone configured for accessing said push-to-x service through a push-to-x client.

50. The gateway according to claim 46, further comprising a user contact list capable of storing at least one contact associated with said user.

51. The gateway according to claim 50, further comprising a user contact list access application capable of being configured to be invoked by said data terminal and, when invoked, to render a user interface at said data terminal, thereby allowing said user to visualize said least one contact.

52. The gateway according to claim 46, further comprising a user folder capable of storing at least one content exchanged by said user during a push-to-x session.

53. The gateway according to claim 52, further comprising a user folder access application capable of being configured to be invoked by said data terminal and, when invoked, to render a user interface at said data terminal allowing said user to visualize said at least one content.

54. The gateway according to claim 46, further comprising a push-to-x session set-up application capable of being configured to be invoked by said data terminal and, when invoked, to render a user interface at said data terminal allowing said user to request a set-up of a push-to-x session.

55. The gateway according to claim 46, further comprising a service event channel capable of being configured to transmit to and receive from said data terminal, signaling messages relating to said push-to-x service.

56. The gateway according to claim 46, further comprising a media streaming channel capable of being configured to transmit to and receive from said data terminal a first streaming content.

57. A telecommunication system comprising:

a packet-switched network;

a framework supporting a push-to-x service;

a data terminal connected to said packet-switched network; and

a gateway according to claim 46, interfacing said packet-switched network and said framework.