B.5 Example 4

29.2143GPPPolicy and charging control over Rx reference pointRelease 17TS

In this example, the SDP "a=rtcp" attribute defined in IETF RFC 3605 is used.

An UE, as the offerer, sends a SDP session description, as shown in table B.5.1, to an application server (only relevant SDP parameters are shown):

Table B.5.1: The values of the SDP parameters sent by the UE in example 1.

V=0
o=ecsreid 3262464865 3262464868 IN IP6 2001:0646:00F1:0045:02D0:59FF:FE14:F33A
s=MM01
i=One unidirectional video media
t=3262377600 3262809600
m=video 50230 RTP/AVP 31
c=IN IP6 2001:0646:00F1:0045:02D0:59FF:FE14:F33A
a=recvonly
a=rtcp: 49320

and receives the SDP parameters, as shown in table B.5.2, from the application server:

Table B.5.2: The values of the SDP parameters sent by the application server in example 1.

V=0
o=ecsreid 3262464865 3262464868 IN IP6 2001:0646:00F1:0045:02D0:59FF:FE14:F33A
s=MM01
i=One unidirectional video media
t=3262377600 3262809600
m=video 51372 RTP/AVP 31
c=IN IP6 2001:0646:000A:03A7:02D0:59FF:FE40:2014
a=sendonly
a=rtcp:53020

From this offer–answer exchange of SDP parameters the UE and the PCRF each creates a list of flow identifiers comprising the IP flows as shown in table B.5.3:

Table B.5.3: Flow identifiers in example 4.

Order of ‘m=’-line

Type of IP flows

Destination IP address / Port number of the IP flows

Flow identifier

1

RTP (Video) DL

2001:0646:00F1:0045:02D0:59FF:FE14:F33A / 50230

<1,2>

1

RTCP DL

2001:0646:00F1:0045:02D0:59FF:FE14:F33A / 49320

<1,1>

1

RTCP UL

2001:0646:000A:03A7:02D0:59FF:FE40:2014 / 53020

<1,1>

Annex C (informative):
Void

Annex D (normative):
Monitoring Related SCEF Procedures over Rx