METHOD AND COMPUTER PROGRAM PRODUCT UTILIZING MULTIPLE UDP DATA PACKETS TO TRANSFER A QUANTITY OF DATA OTHERWISE IN EXCESS OF A SINGLE UDP PACKET

• US 20120246274A1
• Filed: 06/06/2012
• Published: 09/27/2012
• Est. Priority Date: 09/17/2007
• Status: Active Grant

• Current Assignee: McAfee, LLC
• Original Assignee: McAfee, Inc. (McAfee, LLC)
• Inventors: Sargent, John, Barton, Chris, Engelken, Dallas, Roberts, Guy
• Granted Patent: US 8,601,094 B2
• Time in Patent Office: Days
• US Class Current: 709/217
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/193 at the transport layer, e.g. TCP related
• CPC Class Codes: H04L 47/35 by embedding flow control information in regular packets, e.g. piggybacking
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 63/101 Access control lists [ACL]
• CPC Class Codes: H04L 69/326 in the transport layer [OSI layer 4] H04L69/16 takes precedence

Abstract

A method and computer program produce provide the capability to use UDP to send messages that include more data than can be handled by a single UDP packet. A method for performing data transfer implemented in a computer system comprises transmitting a request for data, receiving a response to the request for data comprising a portion of the requested data and an indication that additional data is available, and transmitting a request for additional data.

Claims

1-28. -28. (canceled)

29. A method for performing data transfer implemented in a computer system comprising:

transmitting a request for data;

receiving a response to the request for data comprising a portion of the requested data and a pseudo-Internet Protocol address including an indication of an amount of additional data that is available; and

transmitting a request for the additional data.

30. The method of claim 29, wherein the transmitted request for data includes a domain.

31. The method of claim 29, wherein the transmitted request for data comprises a lookup request for a domain sent to a Domain Name Server Blacklist/Realtime Blackhole List.

32. The method of claim 29, wherein the request for the additional data comprises a pseudo-domain indicating that the additional data is being requested.

33. The method of claim 29, further comprising:

repeating the receiving of the response and the transmitting of the request for the additional data until a response is received indicating that no additional data is available.

34. The method of claim 29, wherein the request for data is transmitted using User Datagram Protocol.

35. The method of claim 29, wherein the response to the request for data is received using User Datagram Protocol.

36. The method of claim 35, wherein the response includes a portion of the requested data that fits in a User Datagram Protocol packet.

37. The method of claim 29, wherein the request for the additional data is transmitted using User Datagram Protocol.

38. The method of claim 29, wherein the request for the additional data includes a pseudo-domain indicating that the additional data is being requested.

39. The method of claim 38, wherein the pseudo-domain is generated by appending a number, in sequence, to a domain included in the transmitted request for data.

40. A non-transitory computer readable storage medium for storing instructions for performing operations comprising:

transmitting a request for data;

receiving a response to the request for data comprising a portion of the requested data and a pseudo-Internet Protocol address including an indication of an amount of additional data that is available; and

transmitting a request for the additional data.

41. The non-transitory computer readable storage medium of claim 40, wherein the transmitted request for data includes a domain.

42. The non-transitory computer readable storage medium of claim 40, wherein the transmitted request for data comprises a lookup request for a domain sent to a Domain Name Server Blacklist/Realtime Blackhole List.

43. The non-transitory computer readable storage medium of claim 40, wherein the request for the additional data comprises a pseudo-domain indicating that the additional data is being requested.

44. The non-transitory computer readable storage medium of claim 40, the operations further comprising:

repeating the receiving of the response and the transmitting of the request for the additional data until a response is received indicating that no additional data is available.

45. The non-transitory computer readable storage medium of claim 40, wherein the request for data is transmitted using User Datagram Protocol.

46. The non-transitory computer readable storage medium of claim 40, wherein the response to the request for data is received using User Datagram Protocol.

47. The non-transitory computer readable storage medium of claim 46, wherein the response includes a portion of the requested data that fits in a User Datagram Protocol packet.

48. The non-transitory computer readable storage medium of claim 40, wherein the request for the additional data is transmitted using User Datagram Protocol.

49. The non-transitory computer readable storage medium of claim 40, wherein the request for the additional data includes a pseudo-domain indicating that the additional data is being requested.

50. The non-transitory computer readable storage medium of claim 49, wherein the pseudo-domain is generated by appending a number, in sequence, to a domain included in the transmitted request for data.

51. A system, comprising:

a processor for;

transmitting a request for data;

receiving a response to the request for data comprising a portion of the requested data and a pseudo-Internet Protocol address including an indication of an amount of additional data that is available; and

transmitting a request for the additional data.