Using IMS as a service framework

IEEE Vehicular Technology Magazine

Volumn 2, Issue 1, 2007, Pages 4-11

  Gourraud, Christophe ^a  

^a Swisscom AG   (Switzerland)

Author keywords

[No Author keywords available]

Indexed keywords

MULTIMEDIA SERVICES; OPTIMIZATION;

SERVICE FRAMEWORK;

COMPUTER NETWORKS;

EID: 34547998160     PISSN: 15566072     EISSN: None     Source Type: Journal    
DOI: 10.1109/MVT.2007.898095     Document Type: Article

References (9)

1. 3GPP TS 23.228, IP Multimedia Subsystem (IMS) Stage 2, 3rd Generation Partnership Project.
2. RFC 3261: SIP: Session Initiation Protocol, Internet Engineering Task Force.
3. RFC 3840: Indicating User Agent Capabilities in the Session Initiation Protocol (SIP), Internet Engineering Task Force.
4. RFC 3841: Caller Preferences for the Session Initiation Protocol (SIP), Internet Engineering Task Force.
5. RFC 4483: A Mechanism for Content Indirection in Session Initiation Protocol (SIP) Messages, Internet Engineering Task Force.
6. RFC 3515: The Session Initiation Protocol (SIP) REFER method, Internet. Engineering Task Force.
7. RFC 3265: Session Initiation Protocol (SIP) Specific Event Notification, Internet Engineering Task Force.
8. RFC 3903: Session Initiation Protocol (SIP) Extension for Event State Publication, Internet Engineering Task Force.
9. RFC 3455: Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP), Internet Engineering Task Force.