Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TR 24.837  Word version:  10.0.0

Top   Top   None   None   Next
1…   4…   4.6   4.7…   5…

 

1  ScopeWord‑p. 16
This technical report intends to develop enhancements to Rel-9 IMS service continuity stage 3 within the scope of TS 24.237, specifically in the area of inter-UE transfer. This technical report serves as a collection and a base for decision on alternative solution proposals for the different enhancement to Rel-9 IMS service continuity stage 3.
This technical report will be used to move the agreed solutions into the main specifications, once the content has stabilized.
Up

2  References

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.237: "IP Multimedia subsystem (IMS) Service Continuity; Stage 2".
[3]
TR 23.831: "IP Multimedia Subsystem (IMS) Inter-UE transfer enhancements, Stage 2".
[4]
TS 24.229: "IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[5]
RFC 2976:  "The SIP INFO Method".
[6]
TS 24.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 3".
[7]
RFC 3428:  "Session Initiation Protocol (SIP) Extension for Instant Messaging".
[8]
RFC 3515:  "The Session Initiation Protocol (SIP) Refer Method".
[9]
RFC 3840  (August 2004): "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)".
[10]
RFC 3891:  "The Session Initiation Protocol (SIP) "Replaces" Header".
[11]
RFC 3903:  "The Session Initiation Protocol (SIP) Publish Extension for Event State Publication".
[12]
RFC 4235:  "An INVITE- Initiated Dialog Event Package for the Session Initiation Protocol (SIP)".
[13]
RFC 4661:  "An Extensible Markup Language (XML) - Based Format for Event Notification Filtering".
[14]
draft-ietf-sipcore-info-events-09  (September 2010): "Session Initiation Protocol (SIP) INFO Method and Package Framework".
[15]
draft-ietf-mmusic-sdp-misc-cap-00  (March 2010) "Miscellaneous Capabilities Negotiation in the Session Description Protocol (SDP)".
[16]
draft-yang-dispatch-SIP-connection-address-type-01  (June 2010) " Session Description Protocol (SDP) Extension for A SIP Connection Address Type".
[17]
TS 24.605: "Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[18]
TS 24.629: "Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[19]
RFC 4538:  "Request Authorization through Dialog Identification in the Session Initiation Protocol".
[20]
RFC 3261:  "SIP: Session Initiation Protocol".
[21]
RFC 3023:  "XML Media Types".
[22]
draft-holmberg-sipcore-proxy-feature-00  (September 2010): "Indication of features supported by proxy".
[23]
RFC 5368:  " Referring to Multiple Resources in the Session Initiation Protocol (SIP)".
[24]
RFC 5364:  "Extensible Markup Language (XML) Format Extension for Representing Copy Control Attributes in Resource Lists".
[25]
TS 24.623: "Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Supplementary Services".
Up

3  Definitions, symbols and abbreviationsWord‑p. 17

3.1  Definitions

For the purposes of the present document, the terms and definitions given in TR 21.905, TS 24.237 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 and TS 24.237.
Controller capable UE:
A UE that is capable of becoming a controller UE.
Up

3.2  Abbreviations

For the purposes of the present document, the abbreviations given in TR 21.905, TS 24.237 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 and TS 24.237.
Up

Up   Top   ToC