Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TR 23.756  Word version:  16.0.0

Top   Top   None   None   Next
1…   5… 
1 Scope  2 References  3 Definitions and abbreviations  4 Architectural assumptions and requirements 
...

 

1  Scope  p. 6

The scope of the present document is to investigate solutions from architecture point of view to support single radio voice call continuity (SRVCC) from NG-RAN to UTRAN.
Issues to be resolved will be collected and documented in the TR with a possible resolution.

2  References  p. 6

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.502: "Procedures for the 5G System".
[3]
TS 23.216: "Single Radio Voice Call Continuity (SRVCC)".
[4]
TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2".
[5]
TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[6]
TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".
[7]
TS 23.501: "System Architecture for the 5G System".
Up

3  Definitions and abbreviations  p. 6

3.1  Definitions  p. 6

For the purposes of the present document, the terms and definitions given in TR 21.905 apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.

3.2  Abbreviations  p. 6

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

4  Architectural assumptions and requirements  p. 6

The following architectural assumptions apply:
  • Solutions shall not consider voice continuity from GERAN/UTRAN to NG-RAN.
  • Solutions shall not consider voice continuity from NG-RAN to GERAN.
  • Solutions shall not consider video service continuity between NG-RAN and GERAN/UTRAN.
  • Solutions shall not consider IP address preservation for PS service when UE moves between NG-RAN and GERAN/UTRAN.
  • Solutions shall not consider service continuity between 5GS and CDMA.
Up

Up   Top   ToC