Dynamic RTCP Relay

• US 20120144056A1
• Filed: 07/30/2010
• Published: 06/07/2012
• Est. Priority Date: 08/12/2009
• Status: Abandoned Application

• Current Assignee: Koninklijke KPN NV, Nederlandse Organisatie Voor Toegepast-Natuurwetenschappelijk Onderzoek Tno
• Original Assignee: Koninklijke KPN NV, Nederlandse Organisatie Voor Toegepast-Natuurwetenschappelijk Onderzoek Tno
• Inventors: Stokking, Hans Maarten, Walraven, Fabian Arthur, Niamut, Omar Aziz, van Deventer, Mattijs Oskar
• Application Number:
  US13/389,725
• Publication Number:
  US 20120144056A1
• Time in Patent Office: Days
• US Class Current: 709/231
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/612 for unicast
• 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
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data

Abstract

A method and a system for dynamically relaying RTCP messages associated with one or more RTP streams is described. Each RTP stream is associated with a media session and with a sender node (MF) and one or more receiver nodes (UE). The method comprises the steps of: assigning at least one control node (MSAS) to at least one RTP stream; providing (4) a receiver node associated with said RTP stream with the address of said control node, said address being provided to said receiver node in a session control protocol message or an HTTP message and being different than the address of the associated sender node; and, said receiver node sending (8) receiver RTCP messages to said control node, using said address comprised in said session control protocol message or HTTP message.

Claims

1. Method of dynamically relaying messages of a first protocol for providing control and management information about media streams, the messages being associated with one or more second protocol based multimedia streams, the second protocol being arranged for streaming multimedia data over IP-based networks, each stream being associated with a media session and with a sender node and one or more receiver nodes, the method comprising the steps of:

assigning at least one control node to at least one stream;

providing a receiver node associated with said stream with the address of said control node, said address being provided to said receiver node in a session control protocol message or an HTTP message and being different than the address of the associated sender node; and

said receiver node sending receiver messages of the first protocol to said control node, using said address comprised in said session control protocol message or HTTP message.

2. Method according to claim 1, wherein the first protocol is RTCP, the second protocol is RIP, and the streams are RIP streams.

3. Method according to claim 2, said method further comprising the step of:

providing a group synchronization identifier associated with said RIP stream to said receiver node; and

sending said group synchronization identifier in a receiver RTCP message to said control node.

4. Method according to claim 2, wherein said method further comprises the step of:

said receiver node generating synchronization status information;

sending said synchronization status information in a sender RTCP message to said control node, said control node comprising a synchronization function for synchronizing the RIP stream associated with said sender RTCP message with one or more other RIP streams assigned to said control node.

5. Method according to claim 4, said method further comprising the steps of:

said synchronization function using said synchronization status information to calculate synchronization settings information;

said control node sending said synchronization settings information to said receiver node,

said receiver node using said synchronization settings information to instruct a delay buffer associated with said receiver node.

6. Method according to claim 2, said method further comprising the steps of:

providing said sender node associated with said RIP stream with the address of said control node, said address being provided to said sender node in a session control protocol message; and

said sender node sending sender RTCP messages to said control node, using said address comprised in said session control protocol message.

7. Method according to claim 6, said method further comprising the steps of:

the control node receiving one or more receiver RTCP messages and one or more sender RTCP messages and associating a receiving RTCP message with a sender RTCP when the RIP session identifier, preferably the SSRC, in said RTCP messages are identical; and

the control node sending a receiver RTCP message to the address from which an associated sender RTCP message originates and/or sending a sender RTCP message to the address from which an associated receiver RTCP message originates.

8. Method according to claim 7, wherein at least one of said receiver RTCP messages comprises synchronization status information, said method further comprises the steps of:

removing said synchronization status information from said receiver RTCP message; and

sending said receiver control message to said associated sender node.

9. Method according to claim 7, wherein said method further comprises the steps of:

said synchronization function providing synchronization settings information; and

sending said synchronization settings information in a sender RTCP message to said receiver node.

10. Method according to claim 2, the method further comprising the step of:

at least one sender node multicasting at least one of said RIP streams and associated sender RTCP messages to one or more receiver nodes.

11. Method according claim 10, the method further comprising the step of:

the receiver node sending at least one of said RTCP messages to said control node.

12. Method according claim 10, the method comprising the steps of:

sending a request for the control node to join the member group associated with said multicast or providing an unicast connection between the sender node and the control node for providing sender RTCP messages to said control node.

13. Method according claim 10, the method comprising the steps of:

the control node receiving one or more receiver RTCP messages and one or more sender RTCP messages and associating a receiving RTCP message with a sender RTCP when the RIP session identifier, preferably the SSRC, in said RTCP messages are identical; and

the control node sending a receiver RTCP message to the address from which an associated sender RTCP message originates and/or sending a sender RTCP message to the address from which an associated receiver RTCP message originates.

19. A computer program product comprising software code portions configured for, when run in the memory of one or more sender-, receiver- and/or control nodes, executing the method steps according to claim 1.

14. A system for dynamically relaying messages of a first protocol for providing control and management information about media streams, the system comprising:

a control node for receiving one or more of receiver messages of the first protocol generated by one or more receiver nodes and/or sender messages of the first protocol generated by one or more sender nodes;

a relay control function associated with said control node, said control function being configured to provide a receiver node and/or sender node associated with a second protocol based multimedia stream, with the address of said control node, said address being provided to said receiver and/or sender node in a session control protocol message or an HTTP message, said second protocol being arranged for streaming multimedia data over IP-based networks; and

at least one receiver node configured to send messages of the first protocol to said control node, using said address comprised in said session control protocol message or an HTTP message.

15. System according to claim 14, wherein the first protocol is RTCP, the second protocol is RIP, and the streams are RIP streams.

16. A system according to claim 15, the system further comprising:

at least one sender node configured to send RTCP messages to said control node, using said address comprised in said session control protocol message or HTTP message;

wherein said control node further comprises;

at least one input for receiving receiver RTCP messages originating from one or more receiver nodes and/or sender RTCP messages originating from one or more sender nodes;

a mapping function for associating a receiving RTCP message with a sender RTCP when the RIP session identifier, preferably the SSRC, in said RTCP messages are identical; and

at least one output for sending a receiver RTCP message to the address from which an associated sender RTCP message originates and/or sending a sender RTCP message to the address from which an associated receiver RTCP message originates.

17. A receiver node configured for use in the system according to claim 15, the receiver node configured for receiving a session control protocol message or an HTTP message comprising the address of a control node and for sending receiver RTCP messages generated by said receiver node to said control node, using said address comprised in said session control protocol message, the receiver node further comprising:

a sync client configured for generating synchronization status information, for inserting said synchronization status information in a receiver RTCP message and sending said receiver RTCP message to said control node.

18. A control node for use in a system according to claim 15, the control node comprising:

at least an input for receiving receiver RTCP messages originating from one or more receiver nodes and/or sender RTCP messages originating from one or more sender nodes;

a mapping function for associating a receiving RTCP message with a sender RTCP when the RIP session identifier, preferably the SSRC, in said RTCP messages are identical;

at least one output for sending a receiver RTCP message to the address from which an associated sender RTCP message originates and/or sending a sender RTCP message to the address from which an associated receiver RTCP message originates; and

, optionally,

a sync function configured for receiving synchronization status information sent by one or more receiver nodes in one or more receiver RTCP messages to said control node and for calculating on the basis of said synchronization status information synchronization settings information for said one or more receiver nodes, said synchronization settings information allowing the one or more receiver nodes to time-delay at least one RIP stream,

wherein the control node is configured for use in the system according to claim 15.