Content for TR 22.897 Word version: 13.0.0
4 Problem statement
5 Use cases
6 Potential requirements
7 Conclusion and recommendations
$ Change history
4 Problem statement p. 8
5 Use cases p. 8
5.1 Local fall back at eNB group call use case p. 8
5.1.1 Description p. 8
5.1.2 Actors p. 8
5.1.3 Pre-conditions p. 9
5.1.4 Service Flows p. 9
5.1.4.1 Service Flow 1 - Disconnection of link between eNB and EPC p. 9
5.1.4.2 Service Flow 2 - Operation whilst eNB disconnected from EPC p. 9
5.1.4.3 Service Flow 3 - Reconnection between eNB and EPC p. 9
5.1.5 Alternative Service Flows p. 9
5.1.6 Post-conditions p. 10
5.1.7 Potential Requirements p. 10
5.2 Local fall back at eNB individual call use case p. 10
5.2.1 Description p. 10
5.2.2 Actors p. 10
5.2.3 Pre-conditions p. 10
5.2.4 Service Flows p. 11
5.2.4.1 Service Flow 1 - Loss of connection between eNB and EPC p. 11
5.2.4.2 Service Flow 2 - Operation whilst eNB disconnected from EPC p. 11
5.2.4.3 Service Flow 3 - Reconnection between eNB and EPC p. 11
5.2.5 Alternative Service Flows p. 12
5.2.6 Post-conditions p. 12
5.2.7 Potential Requirements p. 12
5.3 Local routing use case p. 13
5.3.1 Local routing use case with an infrastructure-derived Isolated E-UTRAN p. 13
5.3.1.1 Description p. 13
5.3.1.2 Pre-conditions p. 13
5.3.1.3 Service Flows p. 13
5.3.1.4 Post-conditions p. 13
5.3.1.5 Potential Requirements p. 13
5.3.2 Local routing use case with an NeNB-derived Isolated E-UTRAN p. 14
5.3.2.1 Description p. 14
5.3.2.2 Pre-conditions p. 14
5.3.2.3 Service Flows p. 14
5.3.2.4 Post-conditions p. 14
5.3.2.5 Potential Requirements p. 14
5.4 A limited backhaul connection use case p. 15
5.4.1 A limited backhaul connection use case with an infrastructure-derived Isolated E-UTRAN p. 15
5.4.1.1 Description p. 15
5.4.1.2 Pre-conditions p. 15
5.4.1.3 Service Flows p. 15
5.4.1.4 Post-conditions p. 15
5.4.1.5 Potential Requirements p. 15
5.4.2 A limited backhaul connection use case with an NeNB-derived Isolated E-UTRAN p. 16
5.4.2.1 Description p. 16
5.4.2.2 Pre-conditions p. 16
5.4.2.3 Service Flows p. 16
5.4.2.4 Post-conditions p. 16
5.4.2.5 Potential Requirements p. 16
5.5 A wide area Isolated E-UTRAN use case p. 17
5.5.1 A wide area Isolated E-UTRAN use case using a number of infrastructure eNBs p. 17
5.5.1.1 Description p. 17
5.5.1.2 Pre-conditions p. 17
5.5.1.3 Service Flows p. 17
5.5.1.4 Post-conditions p. 17
5.5.1.5 Potential Requirements p. 17
5.5.2 A wide area Isolated E-UTRAN use case using a number of NeNBs p. 18
5.5.2.1 Description p. 18
5.5.2.2 Pre-conditions p. 18
5.5.2.3 Service Flows p. 18
5.5.2.4 Post-conditions p. 18
5.5.2.5 Potential Requirements p. 18
5.6 User moves between isolated and fully connected E-UTRAN use case p. 19
5.6.1 Description p. 19
5.6.2 Pre-conditions p. 19
5.6.3 Service Flows p. 19
5.6.4 Post-conditions p. 19
5.6.5 Potential Requirements p. 19
6 Potential requirements p. 19
7 Conclusion and recommendations p. 22
$ Change history p. 24
