Content for TR 23.798 Word version: 15.0.0

3.1 Definitions 3.2 Abbreviations 4.1 Architectural assumptions 4.2 Architectural requirements
...

1 Scope p. 5

The present document studies potential enhancements to the "Isolated E-UTRAN Operation for Public Safety" feature specified in TS 23.401.

Whereas this feature assumes a complete absence of backhaul, the present study considers following cases:

the backhaul is not completely lost but suffers from a limited bandwidth, which does not suffice for normal operation; or
the backhaul is completely lost and a backup link is set up (by means outside the scope of this study) to provide backhaul with a limited bandwidth as above.

Under such scenario it is desirable to use the available backhaul for signalling between an E-UTRAN site and other PLMN entities, for local mission critical communications. The present document studies enhancements to realize this in an optimal manner.

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]

TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".

[3]

TS 33.210: "3G security; Network Domain Security (NDS); IP network layer security".

[4]

TS 33.401: "3GPP System Architecture Evolution (SAE); Security architecture".

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 network:

see TS 23.401.

IOPS network with Limited Backhaul:

A network consisting of one or more eNBs and a Local EPC with a sub-set of the functional entities, having limited backhaul to the Macro EPC to connect to the rest of the EPC functional entities.

3.2 Abbreviations p. 6

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.

4 Architectural considerations p. 6

4.1 Architectural assumptions p. 6

Like a Rel-13 IOPS network, an IOPS network with Limited Backhaul broadcasts a PLMN identity that is dedicated to IOPS mode of operation. This PLMN identity corresponds to the one that is served by the HSS of the Local EPC. In addition, UEs having a subscription in other IOPS PLMNs may be served by the IOPS network with Limited Backhaul.

4.2 Architectural requirements p. 6

The architecture for IOPS with Limited Backhaul should not expose the IMSI more than the current EPS architecture.