SYSTEMS AND METHODS FOR CORRELATING MULTIPLE TCP SESSIONS FOR A VIDEO TRANSFER

• US 20170085652A1
• Filed: 11/30/2016
• Published: 03/23/2017
• Est. Priority Date: 10/04/2011
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Hsu, Wei-Jen, Panda, Biswaranjan, Iyer, Jayaraman, Bhupalam, Bhaskar, Bhargava, Pranav
• Granted Patent: US 10,320,916 B2
• Time in Patent Office: Days
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 65/401 wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference
• CPC Class Codes: H04L 65/61 for supporting one-way streaming services, e.g. Internet radio
• CPC Class Codes: H04L 65/65 Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 69/161 Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
• CPC Class Codes: H04N 21/234345 the reformatting operation being performed only on part of the stream, e.g. a region of the image or a time segment
• CPC Class Codes: H04N 21/64746 Control signals issued by the network directed to the server or the client
• CPC Class Codes: H04N 21/8358 involving watermark protecting executable software by watermarking G06F21/16; image watermarking in general G06T1/0021; watermarks inserted in still images for transmission purposes H04N1/32144; inserting watermarks during video coding H04N19/467
• CPC Class Codes: H04N 5/76 Television signal recording

Abstract

User equipments can download a video file by instantiating multiple video requests, each request specifying different parts of the video file. If each video request initiates a separate transmission control protocol (TCP) session, which is the case with an hypertext transfer protocol (HTTP) partial get request, then a network device in a communications network would be oblivious of contextual information, which indicates that the TCP sessions download different portions of the same video file. This disclosure provides systems and methods for correlating multiple TCP sessions so that a network device in a communications network can be aware of the contextual information.

Claims

1-20. -20. (canceled)

21. A method comprising:

receiving, at a gateway in communication with a least one mobile device over a communication network having a wireless network, a first video request over a first transmission control protocol (TCP) session and a second video request over a second TCP session, wherein portions of the first TCP session and the second TCP session are established over the wireless network;

deriving a first identification of a first video file requested by the first video request;

deriving a second identification of a second video file requested by the second video request; and

comparing, at the gateway, the first identification of the first video file and the second identification of the second video file to determine that the first TCP session and the second TCP session are correlated.

22. The method of claim 21, wherein deriving the first identification of the first video file includes deriving a first video location identifier of the first video file specified in the first video request, and deriving the second identification of the second video file includes deriving the second video location identifier of the second video file specified in the second video request.

23. The method of claim 22, wherein deriving the first video location identifier of the first video file includes reading a “

Request-URI”

field of the first video request and wherein deriving the second video location identifier of the second video file includes reading a “

Request-URI”

field of the second video request.

24. The method of claim 21, wherein deriving the first identification of the first video file includes deriving a first size of the first video file specified in the first video request and deriving the second identification of the second video file includes deriving a second size of the second video file specified in the second video request.

25. The method of claim 21, wherein deriving the first identification of the first video file includes downloading a predetermined portion of the first video file and deriving the second identification of the second video file includes downloading the same predetermined portion of the second video file.

26. The method of claim 21, further comprising:

receiving metadata of the first video file over the first TCP session; and

associating the metadata of the first video file with the second TCP session.

27. The method of claim 21, further comprising:

determining that the first video request over the first TCP session and the second video request over the second TCP session are requesting the same video file; and

adding a single count, to account for the first video request over the first TCP session and the second video request over the second TCP session, to a counter that is configured to maintain a number of distinct selections of the video file.

28. A gateway comprising:

an interface;

a memory; and

a processor; and

wherein the gateway is to;

communicate with at least one mobile device over a communication network having a wireless network;

receive a first video request over a first transmission control protocol (TCP) session and a second video request over a second TCP session, wherein portions of the first TCP session and the second TCP session are established over the wireless network;

derive a first identification of a first video file requested by the first video request;

derive a second identification of a second video file requested by the second video request; and

compare the first identification of the first video file and the second identification of the second video file to determine that the first TCP session and the second TCP session are correlated.

29. The gateway of claim 28, wherein deriving the first identification of the first video file includes deriving a first video location identifier of the first video file specified in the first video request, and deriving the second identification of the second video file includes deriving the second video location identifier of the second video file specified in the second video request.

30. The gateway of claim 29, wherein deriving the first video location identifier of the first video file includes reading a “

Request-URI”

field of the first video request and wherein deriving the second video location identifier of the second video file includes reading a “

Request-URI”

field of the second video request.

31. The gateway of claim 28, wherein deriving the first identification of the first video file includes deriving a first size of the first video file specified in the first video request and deriving the second identification of the second video file includes deriving a second size of the second video file specified in the second video request.

32. The gateway of claim 28, wherein deriving the first identification of the first video file includes downloading a predetermined portion of the first video file and deriving the second identification of the second video file includes downloading the same predetermined portion of the second video file.

33. The gateway of claim 28, wherein the gateway is further to:

receive metadata of the first video file over the first TCP session; and

associate the metadata of the first video file with the second TCP session.

34. The gateway of claim 28, wherein the gateway is further to:

determine that the first video request over the first TCP session and the second video request over the second TCP session are requesting the same video file; and

add a single count, to account for the first video request over the first TCP session and the second video request over the second TCP session, to a counter that is configured to maintain a number of distinct selections of the video file.

35. One or more non-transitory media comprising logic that when executed is to cause a gateway to:

communicate with at least one mobile device over a communication network having a wireless network;

receive a first video request over a first transmission control protocol (TCP) session and a second video request over a second TCP session, wherein portions of the first TCP session and the second TCP session are established over the wireless network;

derive a first identification of a first video file requested by the first video request;

derive a second identification of a second video file requested by the second video request; and

compare the first identification of the first video file and the second identification of the second video file to determine that the first TCP session and the second TCP session are correlated.

36. The one or more non-transitory media of claim 35, wherein deriving the first identification of the first video file includes deriving a first video location identifier of the first video file specified in the first video request, and deriving the second identification of the second video file includes deriving the second video location identifier of the second video file specified in the second video request.

37. The one or more non-transitory media of claim 36, wherein deriving the first video location identifier of the first video file includes reading a “

Request-URI”

field of the first video request and wherein deriving the second video location identifier of the second video file includes reading a “

Request-URI”

field of the second video request.

38. The one or more non-transitory media of claim 35, wherein deriving the first identification of the first video file includes deriving a first size of the first video file specified in the first video request and deriving the second identification of the second video file includes deriving a second size of the second video file specified in the second video request.

39. The one or more non-transitory media of claim 35, wherein deriving the first identification of the first video file includes downloading a predetermined portion of the first video file and deriving the second identification of the second video file includes downloading the same predetermined portion of the second video file.

40. The one or more non-transitory media of claim 35, the logic when executed to further cause the gateway to:

determine that the first video request over the first TCP session and the second video request over the second TCP session are requesting the same video file; and

add a single count, to account for the first video request over the first TCP session and the second video request over the second TCP session, to a counter that is configured to maintain a number of distinct selections of the video file.