Real-time transport protocol stream detection system and method

• US 8,306,063 B2
• Filed: 08/29/2006
• Issued: 11/06/2012
• Est. Priority Date: 08/29/2006
• Status: Active Grant

• Current Assignee: EXFO Incorporated (11172239 Canada, Inc.)
• Original Assignee: EXFO Service Assurance, Inc. (11172239 Canada, Inc.)
• Inventors: Erdal, Muhammet, Hedayat, Kaynam
• Primary Examiner(s): Rinehart, Mark
• Assistant Examiner(s): ANWAR, MOHAMMAD S
• Application Number:
  US11/511,924
• Publication Number:
  US 20080056302A1
• Time in Patent Office: 2,261 Days
• Field of Search: 370/474, 370/392, 370/230
• US Class Current: 370/474
• CPC Class Codes: H04L 65/1101 Session protocols
• 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 65/80 Responding to QoS

Abstract

A system and method for identifying UDP packets on an IP network as candidates for characterization as packets of a RTP stream. UDP packets are identified at a point on the IP network, and for each identified UDP packet 1) it is determined if a version number in a RTP header field in the payload of the UDP packet equals a predetermined value, 2) determined if a packet length associated with the UDP packet is within a predetermined range, 3) determined if a payload type RTP header field within the payload of the UDP packet is within a predetermined range. If all the criteria are satisfied, then the identified UDP packet is characterized as a candidate RTP packet. It is then determined if the candidate RTP packet belongs to a previously detected RTP stream, or to a newly encountered RTP stream. A stream data store is then updated using the information in the RTP header of the candidate RTP packet.

Claims

1. A method for identifying UDP packets on an IP network which are candidates for characterization as a RTP packet of a Real Time Transport Protocol (RTP) stream, each of said UDP packets having a UDP header and a payload, wherein the payload potentially includes a RTP packet having a RTP header and a RTP payload, comprising the steps of:

identifying UDP packets at a point on said IP network, and for each identified UDP packet performing the substeps of;

i. determining if a version number value in said RTP header located in the payload of said identified UDP packet equals a predetermined value, and

ii. determining if the packet length in said identified UDP packet header is within a predetermined range, and

if said determining substeps are affirmative, then characterizing said identified UDP packet as a candidate RTP packet of an RTP stream,

determining from said candidate RTP packet header;

a payload type, a SSRC, a sequence number, and a timestamp,

comparing said determined SSRC, sequence number, and timestamp with a stored SSRC, a stored sequence number, and a stored timestamp of previously identified RTP streams, and

comparing said determined payload type with a stored payload type field of said previously identified RTP streams and at least one dynamic payload type associated with said previously identified RTP streams, and

if there is a match in said comparison for one of said previously identified RTP streams, generating a signal associated with said candidate RTP packet denoting that said candidate RTP packet is a packet of said one previously identified RTP stream without regard to application level signaling associated with said one previously identified RTP stream.

2. The method according to claim 1, wherein said identifying step comprises the further substep of:

iii. determining if said payload type value in said RTP header field located in the payload of said identified UDP packet is within a predetermined range.

3. The method according to claim 2 comprising the further steps of:

for each candidate RTP packet, determining from a source IP address, a destination IP address, a source UDP port, and a destination UDP port, associated with said identified UDP packet, if said candidate RTP packet is associated with a previously identified RTP stream or is associated with a newly identified RTP stream, and

for each candidate RTP packet associated with a newly identified RTP stream, storing said SSRC, sequence number and timestamp of said candidate RTP packet in association with said newly identified RTP stream.

4. The method of claim 1, wherein the version number value is utilized in

combination with the detected size to identify streams.

5. The method of claim 1, wherein the version number value and the payload type value are utilized in combination with the detected size to identify streams.

6. The method of claim 1, wherein the version number value, the payload type value, the sequence number, and timestamp are utilized in combination with the detected size to identify streams.

7. The method of claim 1, comprising the further step of detecting packet spacing between the received packets and using the detected packet spacing in combination with the detected size and the header fields to identify streams.

8. The method of claim 1, wherein version number, the payload type, sequence number value, the timestamp value, and the detected packet spacing are utilized in combination with the detected size to identify streams.

9. The method of claim 1, wherein the version number value, the payload type value, the sequence number value, the timestamp value, the detected packet spacing, and the SSRC number value are utilized in combination with the detected size to identify streams.

10. The method of claim 1, comprising the further step of:

for a detected stream, when the detected size of the packets is less than approximately 320 bytes, characterizing said stream as an audio data stream.

11. The method of claim 1, comprising the further step of:

for a detected stream, when the detected packets have a packet spacing in the approximate range 10 ms to 50 ms, characterizing said stream as an audio stream.

12. The method of claim 1, comprising the further step of:

for a detected stream, when the detected size of the packets is about 1500 bytes, characterizing said stream as a video stream.

13. The method of claim 1, comprising the further step of:

for a detected stream, when the detected packets have a packet spacing less than approximately 10 ms, characterizing said stream as a video stream.

14. The method of claim 1, further including the sub-step of:

determining the version number value.

15. The method according to claim 14, further including the sub-step of:

determining if the payload type value in said packet header field is within a predetermined range.

16. The method according to claim 1, further including the sub-step of:

determining if the temporal spacing of said packets relative to a packet previously identified on said network is within a predetermined range.

17. A system for identifying UDP packets on an IP network which are candidates for characterization as a packet of a Real Time Transport Protocol (RTP) stream, each of said UDP packets having a UDP header and a payload, wherein the payload potentially includes a RTP packet having a RTP header and a RTP payload, wherein each of said UDP packet headers includes a field for packet length corresponding to the size of said UDP packet, the system comprising:

an identification processor adapted to identify UDP packets at a point on said IP network, including characterization means operative on each identified UDP packet for;

i. determining if a version number value in said RTP header located in the payload of said identified UDP packet equals a predetermined value, and

ii. determining if the packet length in said identified UDP packet header is within a predetermined range, and

if said determining substeps are affirmative, then characterizing said identified UDP packet as a candidate packet of an RTP stream,

determine from said candidate RTP packet header;

a payload type, a SSRC, a sequence number and a timestamp,

compare said determined SSRC, sequence number and timestamp with a stored SSRC, a stored sequence number, and a stored timestamp of a previously identified RTP stream,

compare said determined payload type with a stored payload type field of said previously identified RTP stream and at least one dynamic payload type associated with said previously identified RTP stream, and

if there is a match in said comparisons for one of said previously identified RTP streams, generate a signal associated with said candidate RTP packet denoting that said candidate RTP packet is a packet of said one previously identified RTP stream without regard to application level signaling associated with said one previously identified RTP stream.

18. The system according to claim 17, wherein said identification processor further comprises the means operative on each identified UDP packet for:

iii. determining if the payload type value in said RTP header located in the payload of said identified UDP packet is within a predetermined range.

19. The system according to claim 18 wherein said identification processor is adapted to:

for each candidate RTP packet, determine from a source IP address, a destination IP address, a source UDP port, and a destination UDP port of said identified UDP packet, associated with said candidate RTP packet, if said candidate RTP packet is associated with a previously identified RTP stream or is associated with a newly identified RTP stream, and

for each candidate RTP packet associated with a newly identified RTP stream, store said SSRC, sequence number and timestamp of said candidate RTP packet in association with said newly identified RTP stream.

20. A non-transitory computer storage readable medium comprising computer executable instructions for identifying UDP packets on an IP network which are candidates for characterization as a packet of a Real Time Transport Protocol (RTP) stream, each of said UDP packets having a UDP header and a payload, wherein the payload potentially includes a RTP packet having a RTP header and a RTP payload, the computer storage readable medium comprising computer executable instructions for:

identifying UDP packets at a point on said IP network, and for each identified UDP packet performing the substeps of;

i. determining if a version number value in said RTP header located in the payload of said identified UDP packet equals a predetermined value, and

ii. determining if the packet length in said identified UDP packet header is within a predetermined range, and

if said determining substeps are affirmative, then characterizing said identified UDP packet as a candidate packet of an RTP stream;

determining from said candidate RTP packet header;

a payload type, a SSRC, a sequence number, and a timestamp,

comparing said determined SSRC, sequence number, and timestamp with a stored SSRC, a stored sequence number, and a stored timestamp of previously identified RTP streams, and

comparing said determined payload type with a stored payload type field of said previously identified RTP streams and at least one dynamic payload type associated with said previously identified RTP streams, and

if there is a match in said comparison for one of said previously identified RTP streams, generating a signal associated with said candidate RTP packet denoting that said candidate RTP packet is a packet of said one previously identified RTP stream without regard to application level signaling associated with said one previously identified RTP stream.

21. The computer storage readable medium according to claim 20, wherein said computer storage readable medium further comprises computer executable instructions for:

iii. determining if a payload type value in said RTP header located in the payload of said identified UDP packet is within a predetermined range.

22. The computer storage readable medium according to claim 21 further comprising computer executable instructions for:

for each candidate RTP packet, determining from a source IP address, a destination IP address, a source UDP port, and a destination UDP port of said identified UDP packet, associated with said candidate RTP packet, if said candidate RTP packet is associated with a previously identified RTP stream or is associated with a newly identified RTP stream, and

for each candidate RTP packet associated with a newly identified RTP stream, storing said SSRC, sequence number and timestamp of said candidate RTP packet in association with said newly identified RTP stream.