< Example 1 >

: Following is for UA to notify its presence information to Prsence Server

[ Line 1  ] PUBLISH sip:+11234567890@test.3gpp.com SIP/2.0

[ Line 2  ] Accept: application/pidf+xml

[ Line 3  ] Expires: 1200

[ Line 4  ] Content-Type: application/pidf+xml

This SIP message clip highlights the following parameters: Expires, Content-Type. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.

[ Line 5  ] Event: presence

[ Line 6  ] Route: <sip:[2001:0:0:1::2]:5060;lr>

[ Line 7  ] Contact: <sip:+11234567890@[2001:0:0:1::1]:5060>

[ Line 8  ] From: <sip:+11234567890@test.3gpp.com>;tag=2500364513

[ Line 9  ] To: <sip:+11234567890@test.3gpp.com>

[ Line 10] Call-ID: 2218059820@2001:0:0:1::1

[ Line 11] CSeq: 1 PUBLISH

[ Line 12] Max-Forwards: 70

[ Line 13] Via: SIP/2.0/TCP [2001:0:0:1::1]:5060;branch=z9hG4bK3911887978smg;transport=TCP

[ Line 14] Content-Length: 1379

This SIP message clip highlights the following parameters: Via, Route, Contact, CSeq, Call-ID, From, To, Content-Length, Max-Forwards. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.

[ Line 15] <?xml version="1.0" encoding="UTF-8"?>

[ Line 16] <presence xmlns="urn:ietf:params:xml:ns:pidf"

                             xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid"

                             xmlns:op="urn:oma:xml:prs:pidf:oma-pres"

                             xmlns:pdm="urn:ietf:params:xml:ns:pidf:data-model"

                             xmlns:cipid="urn:ietf:params:xml:ns:pidf:cipid"

                             xmlns:caps="urn:ietf:params:xml:ns:pidf:caps"

                             entity="sip:+11234567890@test.3gpp.com">

[ Line 17]   <tuple id="disc298593918">

[ Line 18]     <status>

[ Line 19]       <basic>open</basic>

[ Line 20]     </status>

[ Line 21]     <op:service-description>

[ Line 22]       <op:service-id>org.3gpp.urn:urn-7:3gpp-application.ims.iari.rcse.dp</op:service-id>

[ Line 23]       <op:version>1.0</op:version>

[ Line 24]       <op:description>VoLTE Capabilities Discovery</op:description>

[ Line 25]     </op:service-description>

[ Line 26]     <contact>sip:+11234567890@test.3gpp.com</contact>

[ Line 27]   </tuple>

[ Line 28]   <tuple id="caps298593918">

[ Line 29]     <status>

[ Line 30]       <basic>open</basic>

[ Line 31]     </status>

[ Line 32]     <caps:servcaps>

[ Line 33]       <caps:audio>true</caps:audio>

[ Line 34]       <caps:duplex>

[ Line 35]         <caps:supported>

[ Line 36]           <caps:full/>

[ Line 36]         </caps:supported>

[ Line 37]       </caps:duplex>

[ Line 38]       <caps:video>true</caps:video>

[ Line 39]     </caps:servcaps>

[ Line 40]     <op:service-description>

[ Line 41]       <op:service-id>org.3gpp.urn:urn-7:3gpp-service.ims.icsi.mmtel</op:service-id>

[ Line 42]       <op:version>ver:1.0</op:version>

[ Line 43]       <op:description>VoLTE service</op:description>

[ Line 44]     </op:service-description>

[ Line 45]     <contact>sip:+11234567890@test.3gpp.com</contact>

[ Line 46]   </tuple>

[ Line 47] </presence>

< Example 2 >

[ Line 1  ] PUBLISH sip:+339012341234@anritsu-rcs.com SIP/2.0

[ Line 2  ] Call-ID: xSh0yaUHAA@192.168.1.1

[ Line 3  ] CSeq: 1 PUBLISH

[ Line 4  ] From: <sip:+339012341234@anritsu-rcs.com>;tag=xSh0yaUIAA

[ Line 5  ] To: <sip:+339012341234@anritsu-rcs.com>

[ Line 6  ] Via: SIP/2.0/UDP 192.168.1.1:5060;branch=z9hG4bK84da5f074a2ba56ea1c0d63f7fa45a54383138;rport

[ Line 7  ] Max-Forwards: 70

[ Line 8  ] Route: <sip:192.168.1.2:5060;transport=udp;lr>

[ Line 9  ] Expires: 3600

This SIP message clip highlights the following parameters: Via, Route, Expires, CSeq, Call-ID, From, To, Max-Forwards. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.

[ Line 10] SIP-If-Match: ac63be7e9042439dad76da16904cf48d

[ Line 11] User-Agent: IM-client/OMA1.0 OrangeLabs-RCS-client/2.5.13

This SIP message clip highlights the following parameters: User-Agent. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.

[ Line 12] Event: presence

[ Line 13] Content-Type: application/pidf+xml

[ Line 14] Content-Length: 2122

This SIP message clip highlights the following parameters: Content-Type, Content-Length. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.

[ Line 15] <?xml version="1.0" encoding="UTF-8"?>

[ Line 16] <presence xmlns="urn:ietf:params:xml:ns:pidf"

                             xmlns:op="urn:oma:xml:prs:pidf:oma-pres"

                             xmlns:opd="urn:oma:xml:pde:pidf:ext"

                             xmlns:pdm="urn:ietf:params:xml:ns:pidf:data-model"

                             xmlns:ci="urn:ietf:params:xml:ns:pidf:cipid"

                             xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid"

                             xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"                              xmlns:gml="urn:opengis:specification:gml:schema-xsd:feature:v3.0"

                             entity="sip:+339012341234@test.3gpp.com">

[ Line 17] <tuple id="t1">

[ Line 18]   <status><basic>open</basic></status>

[ Line 19]   <op:service-description>

[ Line 20]     <op:service-id>org.openmobilealliance:File-Transfer</op:service-id>

[ Line 21]     <op:version>1.0</op:version>

[ Line 22]   </op:service-description>

[ Line 23]   <contact>sip:+339012341234@test.3gpp.com</contact>

[ Line 24]   <timestamp>2014-06-19T06:30:45.000Z</timestamp>

[ Line 25] </tuple>

[ Line 26] <tuple id="t2">

[ Line 27]   <status><basic>open</basic></status>

[ Line 28]   <op:service-description>

[ Line 29]     <op:service-id>org.gsma.imageshare</op:service-id>

[ Line 30]     <op:version>1.0</op:version>

[ Line 31]   </op:service-description>

[ Line 32]   <contact>sip:+339012341234@test.3gpp.com</contact>

[ Line 33]   <timestamp>2014-06-19T06:30:45.000Z</timestamp>

[ Line 34] </tuple>

[ Line 35] <tuple id="t3">

[ Line 36]   <status><basic>open</basic></status>

[ Line 37]   <op:service-description>

[ Line 38]     <op:service-id>org.gsma.videoshare</op:service-id>

[ Line 39]     <op:version>1.0</op:version>

[ Line 40]   </op:service-description>

[ Line 41]   <contact>sip:+339012341234@test.3gpp.com</contact>

[ Line 42]   <timestamp>2014-06-19T06:30:45.000Z</timestamp>

[ Line 43] </tuple>

[ Line 44] <tuple id="t4">

[ Line 45]   <status><basic>open</basic></status>

[ Line 46]   <op:service-description>

[ Line 47]     <op:service-id>org.openmobilealliance:IM-session</op:service-id>

[ Line 48]     <op:version>1.0</op:version>

[ Line 49]   </op:service-description>

[ Line 50]   <contact>sip:+339012341234@test.3gpp.com</contact>

[ Line 51]   <timestamp>2014-06-19T06:30:45.000Z</timestamp>

[ Line 52] </tuple>

[ Line 53] <tuple id="t5">

[ Line 54]   <status><basic>open</basic></status>

[ Line 55]   <op:service-description>

[ Line 56]     <op:service-id>org.3gpp.cs-videotelephony</op:service-id>

[ Line 57]     <op:version>1.0</op:version>

[ Line 58]   </op:service-description>

[ Line 59]   <contact>sip:+339012341234@test.3gpp.com</contact>

[ Line 60]   <timestamp>2014-06-19T06:30:45.000Z</timestamp>

[ Line 61] </tuple>

[ Line 62] </presence>