Tech-invite3GPP-SpecsReleasesFeaturesEntitiesInterfacesSBIsIdentifiersTi+Search in Tech-invite

Top   in Index   Prev   Next

TR 23.749SA2
Study on
S8 Home Routing Architecture
for VoLTE

use "3GPP‑Page" to get the Word version
for a better overview, the Table of Contents (ToC) is reproduced
V14.0.0 (Wzip)  2016/06  38 p.

Rapporteur:  Mr. Abe, Motohiro

GSMA has identified a new roaming model for VoLTE called "S8 Home Routed (S8HR)" whereby the PGW, PCRF and P-CSCF are located in the HPLMN also when the UE is roaming in a VPLMN. S8HR roaming architecture aims to provide IMS services to UEs roaming in VPLMN with the UE to network IMS interface (Gm) between the UE and the HPLMN only and not requiring any IMS network to network interface (NNI) between the VPLMN and HPLMN.
The present document studies and evaluates the architecture enhancements required to support S8HR for VoLTE. The architecture enhancements should also be applicable to other IMS services.
The study will cover at a minimum the following topics:
  • Support of Emergency calls to meet regulatory requirement
  • Impacts on SRVCC for the S8HR roaming scenarios required by GSMA.
  • Coexistence of LBO and S8HR roaming architectures
  • Providing VPLMN Identity to IMS entities in HPLMN
  • Handling of geo-local number

full Table of Contents for  TR 23.749  Word version:   14.0.0

this ToC is filtered in order to show the essential title levels only
Here   Top
1  ScopeWord-p. 6
2  ReferencesWord-p. 6
3  Definitions, symbols and abbreviationsWord-p. 7
4  Assumption and Architecture RequirementsWord-p. 7
5  Key IssuesWord-p. 9
5.1  Key Issue 1 - How to make UE detected IMS emergency session successfulUpWord-p. 9
5.2  Key Issue 2 - Handling of non UE detectable Emergency SessionWord-p. 10
5.3  Key Issue 3 - Determination of the ID of the visited PLMN at IMS Entities in HPLMNWord-p. 10
5.4  Key Issue 4 - Local Number Translation and RoutingWord-p. 10
6  SolutionsWord-p. 11
6.1  Solution #1: Local Database based non UE detectable emergency sessionWord-p. 11
6.1a  Solution #1a: How P-CSCF can detect emergency numbers in a VPLMNWord-p. 13
6.2  Solution #2: Local Number TranslationWord-p. 13
6.3  Solution #3: Determination of PLMN-ID via HSS interactionWord-p. 14
6.4  Solution #4: VOIDWord-p. 16
6.5  Solution #5: IMS emergency session with or without IMS registration failureWord-p. 16
6.6  Solution #6: P-CSCF subscription to PLMN ID in changes at IMS registrationWord-p. 20
6.7  Solution #7: P-CSCF query PLMN ID in IMS registration and session establishmentWord-p. 22
6.8  Solution #8: Local number translation on ASWord-p. 23
6.9  Solution #9: AS retrieving user's Geographical Identifier from HSS in S8HR roaming architectureWord-p. 24
6.10  Solution #10: P-CSCF retrieving user's Geographical Identifier from EPC in S8HR roaming architectureWord-p. 26
6.11  Solution #11: Extended NetLoc procedure for Geographical InformationWord-p. 29
6.12  Solution #12: Local Number translation and routing with P-CSCF retrieving user's TAI from EPC in NetLoc procedureWord-p. 30
7  Overall EvaluationWord-p. 31
7.1  Key Issue 1: How to make UE detected IMS emergency session successfulUpWord-p. 31
7.2  Key Issue 2: Handling of non UE detectable Emergency SessionWord-p. 32
7.3  Key Issue 3: Determination of the ID of the visited PLMN at IMS Entities in HPLMNWord-p. 32
7.4  Key Issue 4: Local Number Translation and RoutingWord-p. 33
8  ConclusionsWord-p. 37
A  Change historyWord-p. 38

Up   Top