System and method for alias addressing during effectuation a push-to-talk service in a multiplayer gaming environment

• US 20070197293A1
• Filed: 02/20/2006
• Published: 08/23/2007
• Est. Priority Date: 02/20/2006
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Frivold, Thane, Jalava, Teemu
• Application Number:
  US11/358,882
• Publication Number:
  US 20070197293A1
• Time in Patent Office: Days
• US Class Current: 463/40
• CPC Class Codes: A63F 13/12 involving interaction between a plurality of game devices, e.g. transmisison or distribution systems protocols for networked virtual reality, networked games H04L29/06034
• CPC Class Codes: A63F 13/30 Interconnection arrangements between game servers and game devices; Interconnection arrangements between game devices; Interconnection arrangements between game servers
• CPC Class Codes: A63F 13/332 using wireless networks, e.g. cellular phone networks
• CPC Class Codes: A63F 13/335 using Internet
• CPC Class Codes: A63F 13/85 Providing additional services to players
• CPC Class Codes: A63F 2300/406 Transmission via wireless network, e.g. pager or GSM
• CPC Class Codes: A63F 2300/407 Data transfer via internet
• CPC Class Codes: A63F 2300/5553 user representation in the game field, e.g. avatar
• CPC Class Codes: A63F 2300/57 details of game services offered to the player
• CPC Class Codes: A63F 2300/63 for controlling the execution of the game in time

Abstract

A client for effectuating a push-to-talk service in a gaming environment includes a processor capable of operating a game client, where the client has an associated alias address in a gaming architecture and multimedia service address in a multimedia service architecture. The game client interacts with the gaming architecture to play an electronic game. During this interaction, the game client can then join the push-to-talk session in the multimedia service architecture, where joining the session includes sending a request to the multimedia service architecture, the request including the multimedia service address of the client. The request is routed through the gaming architecture such that the gaming architecture can modify the request to include the alias address of the client, and forward the modified request to the multimedia service architecture. The multimedia service architecture can then join the client to the push-to-talk session based upon the alias address.

Claims

1. A client for effectuating a push-to-talk service in a gaming environment, the client comprising:

a processor capable of operating a game client, the game client being capable of interacting with a gaming architecture to play an electronic game, wherein the game client is capable of interacting with the gaming architecture so as to receive at least one parameter of a push-to-talk session in a multimedia service architecture, and wherein the client has an associated alias address in the gaming architecture, and an associated multimedia service address in the multimedia service architecture,

wherein the game client is capable of joining the push-to-talk session in the multimedia service architecture based upon the at least one parameter while the client interacts with the gaming architecture, wherein the game client is capable of joining the push-to-talk session including sending a request to the multimedia service architecture, the request including the multimedia service address of the client, and

wherein the game client is capable of sending the request such that the request is routed through the gaming architecture, the gaming architecture being capable of modifying the request to include the alias address of the client, and capable of forwarding the modified request to the multimedia service architecture, the multimedia service architecture thereafter being capable of joining the client to the push-to-talk session based upon the alias address.

2. A client according to claim 1, wherein the game client is capable of receiving at least one parameter including a routing address identifying a first network entity in the gaming architecture, and

wherein the game client is capable of sending a request such that the request is routed through the first network entity identified by the routing address.

3. A client according to claim 2, wherein the routing address is associated with a session address identifying the push-to-talk session at a second network entity in the multimedia service architecture, and

wherein the game client is capable of sending a request such that the first network entity is capable of forwarding the modified request to the second network entity identified by the session address, the second network entity thereafter being capable of joining the client to the push-to-talk session identified by the session address.

4. A client according to claim 3, wherein the game client is capable of sending a request to a third network entity in the multimedia service architecture, the third network entity being capable of forwarding the request to the first network entity identified by the routing address.

5. A client according to claim 3, wherein the game client is further capable of establishing a push-to-talk session in the multimedia service architecture, the game client being capable of establishing the push-to-talk session including receiving at least one associated session parameter, the session parameters including the session address, and

wherein the game client is capable of transferring at least one of the session parameters to the gaming architecture, the gaming architecture thereafter being capable of associating the session address with the routing address and advertising the associated routing address for receipt by the client.

6. A network entity for effectuating a push-to-talk service in a gaming environment, the network entity comprising:

a processor capable of operating an application in a gaming architecture as a client interacts with the gaming architecture to play an electronic game, the application being capable of receiving a request to join the client to a push-to-talk session in a multimedia service architecture, wherein the request includes a multimedia service address associated with the client in the multimedia service architecture, the application capable of receiving the request based upon at least one parameter of the push-to-talk session received by the client during interaction with the gaming architecture,

wherein the application is capable of modifying the request to include an alias address associated with the client in the gaming architecture, and

wherein the application is capable of forwarding the modified request to the multimedia service architecture, the multimedia service architecture thereafter being capable of joining the client to the push-to-talk session based upon the alias address.

7. A network entity according to claim 6, wherein the at least one parameter of the push-to-talk session received by the client includes a routing address identifying the network entity in the gaming architecture, and

wherein the application is capable of receiving a request based upon the routing address identifying the network entity.

8. A network entity according to claim 7, wherein the routing address is associated with a session address identifying the push-to-talk session at a second network entity in the multimedia service architecture, and

wherein the application is capable of forwarding the modified request to the second network entity identified by the session address, the second network entity thereafter being capable of joining the client to the push-to-talk session identified by the session address.

9. A network entity according to claim 8, wherein the application is capable of receiving a request via a third network entity in the multimedia service architecture, the third network entity being capable of forwarding the request to the network entity identified by the routing address.

10. A client for effectuating a push-to-talk service in a gaming environment, the client comprising:

a first means for interacting a client with a gaming architecture to play an electronic game, wherein the first means is adapted to interact with the gaming architecture to receive at least one parameter of a push-to-talk session in a multimedia service architecture, and wherein the client has an associated alias address in the gaming architecture, and an associated multimedia service address in the multimedia service architecture; and

a second means for joining the client to the push-to-talk session in the multimedia service architecture based upon the at least one parameter while the client interacts with the gaming architecture, wherein the second means is adapted to join the client including sending a request to the multimedia service architecture, the request including the multimedia service address of the client, and

wherein the second means is adapted to send the request such that the request is routed through the gaming architecture, the gaming architecture being capable of modifying the request to include the alias address of the client, and capable of forwarding the modified request to the multimedia service architecture, the multimedia service architecture thereafter being capable of joining the client to the push-to-talk session based upon the alias address.

11. A client according to claim 10, wherein the first means is adapted to receive at least one parameter including a routing address identifying a first network entity in the gaming architecture, and

wherein the second means is adapted to send a request such that the request is routed through the first network entity identified by the routing address.

12. A client according to claim 11, wherein the routing address is associated with a session address identifying the push-to-talk session at a second network entity in the multimedia service architecture, and

wherein the second means is adapted to send a request such that the first network entity is capable of forwarding the modified request to the second network entity identified by the session address, the second network entity thereafter being capable of joining the client to the push-to-talk session identified by the session address.

13. A client according to claim 12, wherein the second means is adapted to send a request to a third network entity in the multimedia service architecture, the third network entity being capable of forwarding the request to the first network entity identified by the routing address.

14. A client according to claim 12 further comprising:

a third means for establishing a push-to-talk session in the multimedia service architecture, the third means being adapted to establish the push-to-talk session including receiving at least one associated session parameter, the session parameters including the session address; and

a fourth means for transferring at least one of the session parameters to the gaming architecture, the gaming architecture thereafter being capable of associating the session address with the routing address and advertising the associated routing address for receipt by the client.

15. A network entity for effectuating a push-to-talk service in a gaming environment, the network entity comprising:

a first means for receiving a request to join a client to a push-to-talk session in a multimedia service architecture, wherein the request includes a multimedia service address associated with the client in the multimedia service architecture, the request being received in a gaming architecture as the client interacts with the gaming architecture to play an electronic game, and being received based upon at least one parameter of the push-to-talk session received by the client during interaction with the gaming architecture;

a second means for modifying the request to include an alias address associated with the client in the gaming architecture; and

a third means for forwarding the modified request to the multimedia service architecture, the multimedia service architecture thereafter being capable of joining the client to the push-to-talk session based upon the alias address.

16. A network entity according to claim 15, wherein the at least one parameter of the push-to-talk session received by the client includes a routing address identifying the network entity in the gaming architecture, and

wherein the first means is adapted to receive a request based upon the routing address identifying the network entity.

17. A network entity according to claim 16, wherein the routing address is associated with a session address identifying the push-to-talk session at a second network entity in the multimedia service architecture, and

wherein the third means is adapted to forward the modified request to the second network entity identified by the session address, the second network entity thereafter being capable of joining the client to the push-to-talk session identified by the session address.

18. A network entity according to claim 17, wherein the first means is adapted to receive a request via a third network entity in the multimedia service architecture, the third network entity being capable of forwarding the request to the network entity identified by the routing address.

19. A method of effectuating a push-to-talk service in a gaming environment, the method comprising:

interacting a client with a gaming architecture to play an electronic game, wherein the interacting step includes receiving at least one parameter of a push-to-talk session in a multimedia service architecture, and wherein the client has an associated alias address in the gaming architecture, and an associated multimedia service address in the multimedia service architecture; and

joining the client to the push-to-talk session in the multimedia service architecture based upon the at least one parameter while the client interacts with the gaming architecture, wherein the joining step includes sending a request to the multimedia service architecture, the request including the multimedia service address of the client, and

wherein the sending step comprises sending the request such that the request is routed through the gaming architecture, the gaming architecture being capable of modifying the request to include the alias address of the client, and capable of forwarding the modified request to the multimedia service architecture, the multimedia service architecture thereafter being capable of joining the client to the push-to-talk session based upon the alias address.

20. A method according to claim 19, wherein the receiving step comprises receiving at least one parameter including a routing address identifying a first network entity in the gaming architecture, and

wherein the sending step comprises sending a request such that the request is routed through the first network entity identified by the routing address.

21. A method according to claim 20, wherein the routing address is associated with a session address identifying the push-to-talk session at a second network entity in the multimedia service architecture, and

wherein the sending step comprises sending a request such that the first network entity is capable of forwarding the modified request to the second network entity identified by the session address, the second network entity thereafter being capable of joining the client to the push-to-talk session identified by the session address.

22. A method according to claim 21, wherein the sending step comprises sending a request to a third network entity in the multimedia service architecture, the third network entity being capable of forwarding the request to the first network entity identified by the routing address.

23. A method according to claim 21 further comprising:

establishing a push-to-talk session in the multimedia service architecture, the establishing step including receiving at least one associated session parameter, the session parameters including the session address; and

transferring at least one of the session parameters to the gaming architecture, the gaming architecture thereafter being capable of associating the session address with the routing address and advertising the associated routing address for receipt by the client.

24. A method of effectuating a push-to-talk service in a gaming environment, the method comprising:

receiving a request to join a client to a push-to-talk session in a multimedia service architecture, wherein the request includes a multimedia service address associated with the client in the multimedia service architecture, the request being received in a gaming architecture as the client interacts with the gaming architecture to play an electronic game, and being received based upon at least one parameter of the push-to-talk session received by the client during interaction with the gaming architecture;

modifying the request to include an alias address associated with the client in the gaming architecture; and

forwarding the modified request to the multimedia service architecture, the multimedia service architecture thereafter being capable of joining the client to the push-to-talk session based upon the alias address.

25. A method according to claim 24, wherein the at least one parameter of the push-to-talk session received by the client includes a routing address identifying a first network entity in the gaming architecture, and

wherein the receiving step comprises receiving a request at the first network entity identified by the routing address.

26. A method according to claim 25, wherein the routing address is associated with a session address identifying the push-to-talk session at a second network entity in the multimedia service architecture, and

wherein the forwarding step comprises forwarding the modified request to the second network entity identified by the session address, the second network entity thereafter being capable of joining the client to the push-to-talk session identified by the session address.

27. A method according to claim 26, wherein the receiving step comprises receiving a request at the first network entity via a third network entity in the multimedia service architecture, the third network entity being capable of forwarding the request to the first network entity identified by the routing address.

28. A computer program product for effectuating a push-to-talk service in a gaming environment, wherein the computer program product comprises at least one computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising:

a first executable portion for interacting a client with a gaming architecture to play an electronic game, wherein the first executable portion is adapted to interact with the gaming architecture including receiving at least one parameter of a push-to-talk session in a multimedia service architecture, and wherein the client has an associated alias address in the gaming architecture, and an associated multimedia service address in the multimedia service architecture; and

a second executable portion for joining the client to the push-to-talk session in the multimedia service architecture based upon the at least one parameter while the client interacts with the gaming architecture, wherein the second executable portion is adapted to join the client by sending a request to the multimedia service architecture, the request including the multimedia service address of the client, and

wherein the second executable portion is adapted to send the request such that the request is routed through the gaming architecture, the gaming architecture being capable of modifying the request to include the alias address of the client, and capable of forwarding the modified request to the multimedia service architecture, the multimedia service architecture thereafter being capable of joining the client to the push-to-talk session based upon the alias address.

29. A computer program product according to claim 28, wherein the first executable portion is adapted to receive at least one parameter including a routing address identifying a first network entity in the gaming architecture, and

wherein the second executable portion is adapted to send a request such that the request is routed through the first network entity identified by the routing address.

30. A computer program product according to claim 29, wherein the routing address is associated with a session address identifying the push-to-talk session at a second network entity in the multimedia service architecture, and

wherein the second executable portion is adapted to send a request such that the first network entity is capable of forwarding the modified request to the second network entity identified by the session address, the second network entity thereafter being capable of joining the client to the push-to-talk session identified by the session address.

31. A computer program product according to claim 30, wherein the second executable portion is adapted to send a request to a third network entity in the multimedia service architecture, the third network entity being capable of forwarding the request to the first network entity identified by the routing address.

32. A computer program product according to claim 30 further comprising:

a third executable portion for establishing a push-to-talk session in the multimedia service architecture, the third executable portion being adapted to establish the push-to-talk session including receiving at least one associated session parameter, the session parameters including the session address; and

a fourth executable portion for transferring at least one of the session parameters to the gaming architecture, the gaming architecture thereafter being capable of associating the session address with the routing address and advertising the associated routing address for receipt by the client.

33. A computer program product for effectuating a push-to-talk service in a gaming environment, wherein the computer program product comprises at least one computer-readable storage medium having computer-readable program code portions stored therein, the computer-readable program code portions comprising:

a first executable portion for receiving a request to join a client to a push-to-talk session in a multimedia service architecture, wherein the request includes a multimedia service address associated with the client in the multimedia service architecture, the request being received in a gaming architecture as the client interacts with the gaming architecture to play an electronic game, and being received based upon at least one parameter of the push-to-talk session received by the client during interaction with the gaming architecture;

a second executable portion for modifying the request to include an alias address associated with the client in the gaming architecture; and

a third executable portion for forwarding the modified request to the multimedia service architecture, the multimedia service architecture thereafter being capable of joining the client to the push-to-talk session based upon the alias address.

34. A computer program product according to claim 33, wherein the at least one parameter of the push-to-talk session received by the client includes a routing address identifying a first network entity in the gaming architecture, and

wherein the first executable portion is adapted to receive a request at the first network entity identified by the routing address.

35. A computer program product according to claim 34, wherein the routing address is associated with a session address identifying the push-to-talk session at a second network entity in the multimedia service architecture, and

wherein the third executable portion is adapted to forward the modified request to the second network entity identified by the session address, the second network entity thereafter being capable of joining the client to the push-to-talk session identified by the session address.

36. A computer program product according to claim 35, wherein the first executable portion is adapted to receive a request at the first network entity via a third network entity in the multimedia service architecture, the third network entity being capable of forwarding the request to the first network entity identified by the routing address.