Content for TR 23.749 Word version: 14.0.0
4 Assumption and Architecture Requirements
5 Key Issues
6 Solutions
7 Overall Evaluation
8 Conclusions
$ Change History
4 Assumption and Architecture Requirements p. 7
5 Key Issues p. 9
5.1 Key Issue 1 - How to make UE detected IMS emergency session successful p. 9
5.1.1 Description p. 9
5.2 Key Issue 2 - Handling of non UE detectable Emergency Session p. 10
5.2.1 Description p. 10
5.3 Key Issue 3 - Determination of the ID of the visited PLMN at IMS Entities in HPLMN p. 10
5.3.1 Description p. 10
5.4 Key Issue 4 - Local Number Translation and Routing p. 10
5.4.1 Description p. 10
6 Solutions p. 11
6.1 Solution #1: Local Database based non UE detectable emergency session p. 11
6.1.1 Description p. 11
6.1.2 Impacts on existing nodes and functionality p. 12
6.1.3 Solution Evaluation p. 13
6.1a Solution #1a: How P-CSCF can detect emergency numbers in a VPLMN p. 13
6.1a.1 Description of the solution p. 13
6.1a.2 Impacts on existing nodes and functionality p. 13
6.1a.3 Solution Evaluation p. 13
6.2 Solution #2: Local Number Translation p. 13
6.2.1 Description p. 13
6.2.2 Impacts on existing nodes and functionality p. 14
6.2.3 Solution Evaluation p. 14
6.3 Solution #3: Determination of PLMN-ID via HSS interaction p. 14
6.3.1 Description p. 14
6.3.2 Impacts on existing nodes and functionality p. 16
6.3.3 Solution Evaluation p. 16
6.4 Solution #4: VOID p. 16
6.5 Solution #5: IMS emergency session with or without IMS registration failure p. 16
6.5.1 Description p. 16
6.5.1.1 General p. 16
6.5.1.2 Solution description p. 17
6.5.2 Impacts on existing nodes and functionality p. 19
6.5.3 Solution Evaluation p. 20
6.6 Solution #6: P-CSCF subscription to PLMN ID in changes at IMS registration p. 20
6.6.1 Description p. 20
6.6.2 Impacts on existing nodes and functionality p. 21
6.6.3 Solution Evaluation p. 22
6.7 Solution #7: P-CSCF query PLMN ID in IMS registration and session establishment p. 22
6.7.1 Description p. 22
6.7.2 Impacts on existing nodes and functionality p. 22
6.7.3 Solution Evaluation p. 23
6.8 Solution #8: Local number translation on AS p. 23
6.8.1 Description p. 23
6.8.2 Impacts on existing nodes and functionality p. 24
6.8.3 Solution Evaluation p. 24
6.9 Solution #9: AS retrieving user's Geographical Identifier from HSS in S8HR roaming architecture p. 24
6.9.1 Description p. 24
6.9.2 Impacts on existing nodes and functionality p. 25
6.9.3 Solution Evaluation p. 25
6.10 Solution #10: P-CSCF retrieving user's Geographical Identifier from EPC in S8HR roaming architecture p. 26
6.10.1 Description p. 26
6.10.1.1 General description of the solution p. 26
6.10.1.2 Procedures to enable the solution p. 26
6.10.1.2.1 Reporting Geographical Identifier in the attach procedure p. 26
6.10.1.2.2 Reporting Geographical Identifier in the UE requested PDN connectivity procedure p. 27
6.10.1.2.3 Reporting Geographical Identifier in the Location Change Reporting procedure p. 28
6.10.1.2.4 P-CSCF retrieving Geo Identifier from PCRF during MO session setup p. 28
6.10.2 Impacts on existing nodes and functionality p. 29
6.10.3 Solution Evaluation p. 29
6.11 Solution #11: Extended NetLoc procedure for Geographical Information p. 29
6.11.1 Description p. 29
6.11.2 Impacts on existing nodes and functionality p. 30
6.11.3 Solution Evaluation p. 30
6.12 Solution #12: Local Number translation and routing with P-CSCF retrieving user's TAI from EPC in NetLoc procedure p. 30
7 Overall Evaluation p. 31
7.1 Key Issue 1: How to make UE detected IMS emergency session successful p. 31
7.2 Key Issue 2: Handling of non UE detectable Emergency Session p. 32
7.3 Key Issue 3: Determination of the ID of the visited PLMN at IMS Entities in HPLMN p. 32
7.4 Key Issue 4: Local Number Translation and Routing p. 33
8 Conclusions p. 37
$ Change History p. 38
