Avamprogetto 2a

Technical requirements for the handover interfaces for the execution of telecommunications surveillance

Description and requirements Example

Identifier of the retained call data, e.g. SIP callID, for [email protected] correlating data from different DR sources in CSP.

contentType Table D.5

Description and requirements Examples

List of the media type of the message body. application/sdp

text/html

mediaComponents Table D.2.4.4

Description and requirements

The mediaComponents structure shall contains the

following 5 elements listed below: 1) time, 2)

mediaName, 3) mediaDescription, 4) mediaInititiator

and 5) accessCorrelationID.

1) time Table D.2.4.4

Description and requirements Example

Time when this media component has been processed. 20140406145238+0200

2) mediaName Table D.2.4.4

Description and requirements Examples

Media component name in the SDP data of the 200 OK audio

message (from "m=" line in SDP data as in IETF RFC video

4566). text

application

message

image

3) mediaDescription Table D.2.4.4

Description and requirements Examples

The media component description specifies the media m=audio 49174 RTP/AVP 8 described in the SDP media name (from "attribute-line" a=rtpmap:96 L8/8000 (i=, c=, b=, k=, a=, etc...) content in SDP data of the c=IN IP4 192.0.2.14/127/2 200 OK message, as in IETF RFC 4566.

4) mediaInitiator Table D.2.4.4

Description and requirements Examples

Media component initiator. calling Party

called Party

5) accessCorrelationID Table D.2.4.4

Description and requirements Example

Correlation identifier for the access used for SIP usage. 87A3284CD6

This field holds the charging identifier of the access

network. For GPRS and I-WLAN access, this shall be

the GPRS Charging ID, for EPS, this shall be the

charging ID and for other access networks this shall be

the Access Network Charging Identifier Value.