Redundancy lists in a peer-to-peer relay network

• US 20050086350A1
• Filed: 11/03/2003
• Published: 04/21/2005
• Est. Priority Date: 10/20/2003
• Status: Active Grant

• Current Assignee: Sony Interactive Entertainment LLC (Sony Group Corp.)
• Original Assignee: Sony Computer Entertainment America LLC (Sony Group Corp.)
• Inventors: Mai, Anthony
• Granted Patent: US 7,685,301 B2
• Time in Patent Office: Days
• US Class Current: 709/230
• 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/34 using peer-to-peer connections
• CPC Class Codes: A63F 2300/407 Data transfer via internet
• CPC Class Codes: A63F 2300/408 Peer to peer connection
• CPC Class Codes: A63F 2300/53 details of basic data processing
• CPC Class Codes: A63F 2300/534 for network load management, e.g. bandwidth optimization, latency reduction
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1057 involving pre-assessment of levels of reputation of peers
• CPC Class Codes: H04L 67/107 with limitation or expansion of the discovery scope

Abstract

Methods and apparatus for implementing peer-to-peer relay. In one implementation, a method of building a redundancy list in a peer system in a peer-to-peer relay network includes: receiving a first message including first identification information at a first peer system from a second peer system connected to said first peer system in a peer-to-peer relay network; storing said first identification information; receiving a second message including second identification information at said first peer system from a third peer system connected to said first peer system in said peer-to-peer relay network; comparing said second identification information with said first identification information; building a redundancy update message; and sending said redundancy update message to said third peer system.

Claims

1. A method of building a redundancy list in a peer system in a peer-to-peer relay network, comprising:

receiving a first message including first identification information at a first peer system from a second peer system connected to said first peer system in a peer-to-peer relay network;

storing said first identification information;

receiving a second message including second identification information at said first peer system from a third peer system connected to said first peer system in said peer-to-peer relay network;

comparing said second identification information with said first identification information;

building a redundancy update message; and

sending said redundancy update message to said third peer system.

2. The method of claim 1, wherein:

wherein said second identification information is the same as said first identification information

3. The method of claim 1, wherein:

a message includes data to be relayed, an origin identifier, a sequence value, and addressing information, and

the origin identifier of a message indicates an origin peer system.

4. The method of claim 3, wherein:

comparing said second identification information with said first identification information includes;

comparing the origin identifier of said first message with the origin identifier of said second message, and

comparing the sequence value of said first message with the sequence value of said second message.

5. The method of claim 3, wherein:

said redundancy update message includes an origin identifier and a recipient identifier,

the origin identifier of said redundancy update message indicates the origin peer system that is the same as the origin peer system indicated by the origin identifier of said first message and of said second message, and

the recipient identifier of said redundancy update message indicates said first peer system.

6. The method of claim 1, further comprising:

disconnecting said first peer system from a fourth peer system;

building a clear redundancy message; and

sending said clear redundancy message from said first peer system to each peer system connected to said first peer system in said peer-to-peer relay network.

7. The method of claim 6, wherein:

said clear redundancy message includes a recipient identifier indicating said first peer system.

8. The method of claim 6, wherein:

said fourth peer system is said second peer system or said third peer system.

9. The method of claim 1, wherein:

each peer system in said peer-to-peer relay network stores a connection limit defining a number of other peer systems up to which that peer system is permitted to connect, and

each peer system stores a set of one or more relay rules for relaying data to other peer systems connected to that peer system.

10. The method of claim 1, wherein:

the data relayed by peer systems is update data for a network environment.

11. The method of claim 1, wherein:

the data relayed by peer systems is update data for an online game.

12. The method of claim 1, wherein:

at least one peer system is a network-enabled game console.

13. The method of claim 1, wherein:

at least two peer systems are connected through the Internet.

14. A method of building a redundancy list in a peer system in a peer-to-peer relay network, comprising:

sending a message including identification information from a first peer system to a second peer system connected to said first peer system in a peer-to-peer relay network;

receiving a redundancy update message from said second peer system; and

updating a redundancy list including one or more entries;

wherein each entry in said redundancy list stores a recipient identifier indicating a peer system and a message identifier, such that an entry indicates said first peer system is not to send a message to the peer system indicated by the entry when the message includes identification information matching the message identifier indicated by the entry.

15. The method of claim 14, wherein:

a message includes data to be relayed, an origin identifier, a sequence value, and addressing information, and

the origin identifier of a message indicates an origin peer system.

16. The method of claim 15, wherein:

the message identifier of an entry in said redundancy list indicates an origin peer system.

17. The method of claim 14, wherein:

said redundancy update message indicates identification information that is the same as the identification information of said message sent to said second peer system.

18. The method of claim 14, further comprising:

receiving a clear redundancy message including a recipient identifier indicating a third peer system; and

updating a redundancy list by removing any entries in said redundancy list indicating said third peer system as the recipient identifier of that entry.

19. The method of claim 18, wherein:

said third peer system is said second peer system.

20. The method of claim 14, wherein:

each peer system in said peer-to-peer relay network stores a connection limit defining a number of other peer systems up to which that peer system is permitted to connect, and

each peer system stores a set of one or more relay rules for relaying data to other peer systems connected to that peer system.

21. A peer system in a peer-to-peer relay network, comprising:

means for receiving a first message including first identification information from a first sending peer system connected to said peer system in a peer-to-peer relay network;

means for storing said first identification information;

means for receiving a second message including second identification information from a second sending peer system connected to said peer system in said peer-to-peer relay network;

means for comparing said second identification information with said first identification information;

means for building a redundancy update message; and

means for sending said redundancy update message to said second sending peer system.

22. The peer system of claim 21, further comprising:

means for building a clear redundancy message; and

means for sending said clear redundancy message from said peer system to each peer system connected to said first peer system in said peer-to-peer relay network.

23. The peer system of claim 21, further comprising:

means for sending a message including identification information to a recipient peer system connected to said peer system in a peer-to-peer relay network;

means for receiving a redundancy update message from said recipient peer system; and

means for updating a redundancy list including one or more entries;

wherein each entry in said redundancy list stores a recipient identifier indicating a peer system and a message identifier, such that an entry indicates said peer system is not to send a message to the peer system indicated by the entry when the message includes identification information matching the message identifier indicated by the entry.

24. The peer system of claim 21, further comprising:

means for receiving a clear redundancy message including a recipient identifier indicating a disconnected peer system; and

means for updating a redundancy list by removing any entries in said redundancy list indicating said disconnected peer system as the recipient identifier of that entry;

wherein each entry in said redundancy list stores a recipient identifier indicating a peer system and a message identifier, such that an entry indicates said peer system is not to send a message to the peer system indicated by the entry when the message includes identification information matching the message identifier indicated by the entry.

25. The peer system of claim 21, wherein:

said peer system stores a connection limit defining a number of other peer systems up to which said peer system is permitted to connect, and

said peer system stores a set of one or more relay rules for relaying data to other peer systems connected to said peer system.

26. A computer program, stored on a tangible storage medium, for use in a peer system in a peer-to-peer relay network, the program comprising executable instructions that cause a computer to:

process a received first message including first identification information from a first sending peer system connected to said peer system in a peer-to-peer relay network;

store said first identification information;

process a received second message including second identification information from a second sending peer system connected to said peer system in said peer-to-peer relay network;

compare said second identification information with said first identification information;

build a redundancy update message; and

send said redundancy update message to said second sending peer system.

27. The computer program of claim 26, further comprising instructions that cause a computer to:

build a clear redundancy message; and

send said clear redundancy message from said peer system to each peer system connected to said first peer system in said peer-to-peer relay network.

28. The computer program of claim 26, further comprising instructions that cause a computer to:

send a message including identification information to a recipient peer system connected to said peer system in a peer-to-peer relay network;

process a received redundancy update message from said recipient peer system; and

update a redundancy list including one or more entries;

wherein each entry in said redundancy list stores a recipient identifier indicating a peer system and a message identifier, such that an entry indicates said peer system is not to send a message to the peer system indicated by the entry when the message includes identification information matching the message identifier indicated by the entry.

29. The computer program of claim 26, further comprising instructions that cause a computer to:

process a received clear redundancy message including a recipient identifier indicating a disconnected peer system; and

update a redundancy list by removing any entries in said redundancy list indicating said disconnected peer system as the recipient identifier of that entry;

wherein each entry in said redundancy list stores a recipient identifier indicating a peer system and a message identifier, such that an entry indicates said peer system is not to send a message to the peer system indicated by the entry when the message includes identification information matching the message identifier indicated by the entry.

30. The computer program of claim 26, wherein:

said peer system stores a connection limit defining a number of other peer systems up to which said peer system is permitted to connect, and

said peer system stores a set of one or more relay rules for relaying data to other peer systems connected to said peer system.