Tech-invite3GPPspecsGlossariesIETFRFCsGroupsSIPABNFsWorld Map
Top   in Index   Prev   Next

TR 23.749 (SA2)
Study on
S8 Home Routing Architecture for VoLTE

ToC   3GPP‑Page   Help    
V14.0.0 (Wzip)  2016/06  38 p.


Rapporteur:  Mr. Abe, Motohiro
See also:  VoLTE-related TS/TR

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


 

Here   Top

 

1 Scope2 References3 Definitions, symbols and abbreviations3.1 Definitions3.2 Symbols3.3 Abbreviations4 Assumption and Architecture Requirements4.1 Assumptions4.2 Architecture and Architecture Requirements5 Key Issues5.1 Key Issue 1 - How to make UE detected IMS emergency session successful5.2 Key Issue 2 - Handling of non UE detectable Emergency Session5.3 Key Issue 3 - Determination of the ID of the visited PLMN at IMS Entities in HPLMN5.4 Key Issue 4 - Local Number Translation and Routing6 Solutions6.1 Solution #1: Local Database based non UE detectable emergency session6.1a Solution #1a: How P-CSCF can detect emergency numbers in a VPLMN6.2 Solution #2: Local Number Translation6.3 Solution #3: Determination of PLMN-ID via HSS interaction6.4 Solution #4: VOID6.5 Solution #5: IMS emergency session with or without IMS registration failure6.6 Solution #6: P-CSCF subscription to PLMN ID in changes at IMS registration6.7 Solution #7: P-CSCF query PLMN ID in IMS registration and session establishment6.8 Solution #8: Local number translation on AS6.9 Solution #9: AS retrieving user's Geographical Identifier from HSS in S8HR roaming architecture6.10 Solution #10: P-CSCF retrieving user's Geographical Identifier from EPC in S8HR roaming architecture6.11 Solution #11: Extended NetLoc procedure for Geographical Information6.12 Solution #12: Local Number translation and routing with P-CSCF retrieving user's TAI from EPC in NetLoc procedure7 Overall Evaluation7.1 Key Issue 1: How to make UE detected IMS emergency session successful7.2 Key Issue 2: Handling of non UE detectable Emergency Session7.3 Key Issue 3: Determination of the ID of the visited PLMN at IMS Entities in HPLMN7.4 Key Issue 4: Local Number Translation and Routing8 ConclusionsA Change history

 

1  ScopeWord-p. 6
2  References
3  Definitions, symbols and abbreviationsWord-p. 7
4  Assumption and Architecture Requirements
5  Key IssuesWord-p. 9
6  SolutionsWord-p. 11Up
6.1  Solution #1: Local Database based non UE detectable emergency session
6.1a  Solution #1a: How P-CSCF can detect emergency numbers in a VPLMN
6.2  Solution #2: Local Number Translation
6.3  Solution #3: Determination of PLMN-ID via HSS interaction
6.4  Solution #4: VOID
6.5  Solution #5: IMS emergency session with or without IMS registration failure
6.6  Solution #6: P-CSCF subscription to PLMN ID in changes at IMS registration
6.7  Solution #7: P-CSCF query PLMN ID in IMS registration and session establishment
6.8  Solution #8: Local number translation on AS
6.9  Solution #9: AS retrieving user's Geographical Identifier from HSS in S8HR roaming architecture
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 Information
6.12  Solution #12: Local Number translation and routing with P-CSCF retrieving user's TAI from EPC in NetLoc procedure
7  Overall Evaluation
8  ConclusionsWord-p. 37
A  Change historyWord-p. 38

Up   Top