Content for TR 23.797 Word version: 13.0.0
1 Scope
2 References
3 Definitions and abbreviations
3.1 Definitions
3.2 Abbreviations
4 Assumptions and architectural requirements
4.1 Assumptions
4.2 Architectural requirements
5 Key issues
...
...
1 Scope p. 5
This Technical Report contains the results of the Stage 2 study and evaluation of possible 3GPP technical system solutions for architectural enhancements needed to support Isolated E-UTRAN operation for public safety based on the Stage 1 requirements in TS 22.346.
2 References p. 5
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]
TR 41.001: "GSM Release Specifications".
→ to date, withdrawn by 3GPP
[3]
→ to date, withdrawn by 3GPP
TS 22.346: "Isolated Evolved Universal Terrestrial Radio Access Network (E-UTRAN) operation for public safety; Stage 1".
[4]
TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[5]
TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)".
[6]
TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode".
3 Definitions and abbreviations p. 5
3.1 Definitions p. 5
For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply.
A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
IOPS-capable eNB:
an eNB that has the capability of IOPS mode operation, which provides a local IP connectivity and public safety services to the UEs via a Local EPC when the eNB has lost backhaul to the Macro EPC or it has no backhaul to the Macro EPC.
IOPS network:
an IOPS network consists of one or more eNBs operating in IOPS mode and connected to a Local EPC.
Local EPC:
the Local EPC is an entity which provides functionality that eNBs in IOPS mode of operation use, instead of the Macro EPC, in order to support public safety services.
Local IP connectivity:
IP address assignment and local routing provided in the IOPS network.
Macro EPC:
the EPC which serves an eNB in normal mode of operation.
Nomadic EPS:
deployable system which has the capability to provide radio access (via deployable IOPS-capable eNB(s)), local IP connectivity and public safety services to the UEs in absence of normal EPS infrastructure availability.
3.2 Abbreviations p. 6
4 Assumptions and architectural requirements p. 6
4.1 Assumptions p. 6
No assumptions were identified during the study.
4.2 Architectural requirements p. 6
For the scenario that an eNB has no backhaul to the Macro EPC, the general IOPS architectural requirements include:
- When an UE accesses the eNB in IOPS mode of operation, a local IP connectivity and transport public safety service shall be provided to the UE by the Local EPC connected to the eNB, if authorized.
- An eNB that supports IOPS may enter IOPS mode of operation after it detects lack of S1 connectivity to the Macro EPC. The decision by an eNB to enter IOPS mode of operation shall be made in accordance with the local policies of the RAN operator.
5 Key issues p. 6
It was not considered necessary to describe key issues during this study.
