Tech-invite 3GPP-Specs Releases Features Entities Interfaces SBIs Identifiers T_i+

21 22 23 24 25 26 27 28 29 31 32 33 34 35 36 37 38 4‑5x

TR 23.715 SA2 ★
Study on System enhancements
for Provision of Access
to Restricted Local Operator Services
by an Unauthenticated UE

use "3GPP‑Page" to get the Word version
for a better overview, the Table of Contents (ToC) is reproduced

V16.0.0 (Wzip) 2018/09 38 p.

Rapporteur: Mr. Drevon, Nicolas

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, and determine which of the solutions can proceed to normative specifications.

full Table of Contents for TR 23.715 Word version: 16.0.0

1 Scope Word-p. 6

3 Definitions, symbols and abbreviations

3.1 Definitions

3.2 Symbols Word-p. 7

3.3 Abbreviations

4 Architectural Assumptions and Requirements

4.1 Architectural Assumptions

4.2 Architectural Requirements Word-p. 8

5 Key Issues for EPC

5.1 Key Issue #EPC-1: Network indicating support for Restricted Local Operator Services and related UE behaviour

5.2 Key Issue #EPC-2: RLOS request indication

5.3 Key Issue #EPC-3: Support of unauthenticated UEs access to RLOS

5.4 Key Issue #EPC-4: Support of authenticated UEs access to RLOS Word-p. 9

5.6 Key Issue #EPC-6: Collection of charging information

5.7 Key Issue #EPC-7: Level of security

6 Key Issues for IMS

6.1 Key issue #IMS-1: Support for unauthenticated and authenticated user

6.2 Key issue #IMS-2: Identification of Restricted Local Operator Services at IMS layer

6.3 Key issue #IMS-3: Handling IMS session for Restricted Local Operator Service Word-p. 10

6.4 Key issue #IMS-4: Support of emergency services by UEs attached for RLOS

7.1 Solution #1: New SIB indicating support for Restricted Local Operator Services

7.1.1 Functional Description

7.1.2 Procedures

7.1.3 Impact on existing entities and interfaces

7.2 Solution #2: EPC attach/PDN connection for RLOS from unauthenticated/authenticated UE Word-p. 11

7.2.1 Functional Description

7.2.2 Procedures

7.2.2.2 Detach procedure Word-p. 12

7.2.3 Impact on existing entities and interfaces

7.3 Solution #3: IMS procedures for RLOS

7.3.1 Functional Description

7.3.2 Procedures

7.3.3 Impact on existing entities and interfaces Word-p. 13

7.4 Solution #4: EPC solution using dedicated RLOS-APN

7.4.1 Functional Description

7.4.2 Procedures Word-p. 15

7.4.2.1 Attach procedure

7.4.2.2 UE-initiated Detach procedure Word-p. 17

7.4.2.3 MME-initiated Detach procedure

7.4.2.4 S1-based handover procedure Word-p. 18

7.4.2.5 UE requested PDN connectivity

7.4.3 Impact on existing entities and interfaces

7.5 Solution #5: IMS solution with dedicated RLOS-APN and RLOS-specific P/S-CSCF

7.5.1 Functional Description

7.5.2 Procedures Word-p. 19

7.5.2.1 IMS registration

7.5.2.2 Location Information retrieval Word-p. 20

7.5.2.3 UE initiated RLOS IMS session establishment

7.5.3 Impact on existing entities and interfaces Word-p. 21

7.6 Solution #6: Solution to key issue #EPC-3 & #EPC-4 to enable IMS calls after initial attachment

7.6.1 Functional Description

7.6.2 Procedures Word-p. 22

7.6.2.1 UEs in Limited Service State that cannot be authenticated

7.6.3 Impact on existing entities and interfaces

7.7 Solution #7 to key issues #IMS-1, #IMS-2, and #IMS-3: IMS support for RLOS users Word-p. 23

7.7.1 Functional Description

7.7.2 Procedures Word-p. 24

7.7.3 Impact on existing entities and interfaces

7.8 Solution #8: Solution to key issues #IMS-4: Support of emergency services by UEs attached for RLOS Word-p. 25

7.8.1 Functional Description

7.8.2 Procedures

7.8.2.1 UE performs detach from RLOS and then do emergency Attach

7.8.2.2 UE stays RLOS attached, and establishes emergency PDN connection Word-p. 26

7.8.3 Impact on existing entities and interfaces Word-p. 27

7.9 Solution #9: PLMN selection, radio access for RLOS and overload handling

7.9.1 Functional Description

7.9.2 Procedures Word-p. 28

7.9.3 Impact on existing entities and interfaces

7.10 Solution #10: IMS solution with dedicated RLOS-APN and skipping IMS registration

7.10.1 Functional Description

7.10.2 Procedures Word-p. 30

7.10.2.1 IMS registration

7.10.2.2 Location Information retrieval

7.10.2.3 UE initiated RLOS IMS session establishment

7.10.3 Impact on existing entities and interfaces Word-p. 31

7.11 Solution #11: Partial security solution for key issue #EPC-7

7.11.1 Functional Description

7.11.2 Procedures

7.11.3 Impact on existing entities and interfaces

8 Evaluation Word-p. 32

9 Conclusions Word-p. 36

A Change history Word-p. 38