Content for TR 23.715 Word version: 16.0.0

3.1 Definitions 3.2 Symbols 3.3 Abbreviations
...

1 Scope p. 6

The objective of this Technical Report is to identify and evaluate potential architecture enhancements of EPS and IMS needed to support Provision of Access to Restricted Local Operator Services by Unauthenticated UEs as identified in TS 22.101, TS 22.115 and TS 22.228, and determine which of the solutions can proceed to normative specifications.

This feature is only applicable to EPS 3GPP access. Access to local operator services does not affect the UICC.

2 References p. 6

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 22.101: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; Service aspects; Service principles".

[3]

TS 22.115: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service aspects; Charging and billing".

[4]

TS 22.228: "3rd Generation Partnership Project; Service requirements for the IP multimedia core network subsystem".

[5]

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

[6]

TS 23.203: "Policies and Charging control architecture; Stage 2".

[7]

TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".

[8]

TS 23.167: "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; IP Multimedia Subsystem (IMS) emergency sessions".

[9]

TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".

[10]

TS 22.011: "Technical Specification Group Services and System Aspects; Service accessibility".

3 Definitions, symbols and abbreviations p. 6

3.1 Definitions p. 6

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.

Restricted local operator services:

communication services provided by an operator that involve either automated or human assistance (e.g. credit card billing, directory assistance, customer care) for which successful authentication is not necessary.

3.2 Symbols p. 7

For the purposes of the present document, the following symbols apply:

3.3 Abbreviations p. 7

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.

RLOS

Restricted Local Operator Services

4 Architectural Assumptions and Requirements p. 7

4.1 Architectural Assumptions p. 7

The goal of the study is to enable access to those Restricted Local Operator Services (RLOS), however the definition of such restricted local operator services offered by an operator is out of scope of 3GPP.

Architectural assumptions are the following:

Access to RLOS is only possible for UEs when using EPC via E-UTRAN as IPCAN.
Both unauthenticated UEs and authenticated UEs in limited service state can access RLOS via the same architecture.
An authenticated UE allowed to access EPC may access the same services that are provided as RLOS but in this case, it is not within the scope of RLOS. No work will be done in this area.
The UE shall indicate to the EPC and the IMS network that the request is a request for RLOS.
The standard shall support IMS emergency services for UEs attached for RLOS.
Allowing access to RLOS is completely under the local operator's control.
If the UE performs RLOS attach, the network may perform authentication if security information is available. Otherwise, authentication to EPC access for RLOS is skipped.

NOTE:
whether authentication for EPC access for roaming UEs in limited state may be performed based on the presence of specific roaming agreements is to be stated in the conclusions in clause 9.
The solution shall support both non-IMS and IMS RLOS services.
When RLOS are accessed via IMS sessions:
1. they do not require any specific support for location over and above what is defined by IMS already;
2. they do not require any specific support regarding call back to the user that has initiated the session;
3. the IMS RLOS are securely isolated to avoid e.g. DOS attacks to IMS entities offering regular IMS services.
Only UE-originated RLOS requests are supported.
No support of multiple PDN connections for RLOS.
No support of mobile terminated services.
This feature is only applicable to EPS 3GPP access.
Inter-RAT handovers and handover between 3GPP and non-3GPP accesses are not supported.
The use of the RLOS feature does not impact the local service provider's ability to support LI.