4.3.12a Support of Restricted Local Operator Service

23.4013GPPGeneral Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) accessRelease 18TS

4.3.12a.1 Introduction

Restricted Local Operator Services is an optional feature supported in certain countries. Service requirements of Restricted Local Operator Services is defined in TS 22.101 [80] and the architectural requirements are defined in TS 23.221 [27].

Access to Restricted Local Operator Services may be allowed for UEs in limited service state by the serving network depending on local regulation and operator policies. UEs may enter limited service state as specified in clause 4.3.12.1.

RLOS is requested by the UE, based on explicit request from the user. When attaching to the network to access RLOS, the UE shall send a NAS RLOS indication to the MME, which proceeds with the RLOS attach procedure described in clause 5.3.2.1 A specific RLOS-APN, unique for the PLMN, is configured in the MME.

Allowing access to RLOS is completely under the local operator’s control, e.g. EPC access for RLOS does not depend on whether the UE is authenticated or not, nor on whether authentication succeeds or fails.

To provide access to Restricted Local Operator Services, the MME is configured with MME RLOS Configuration Data that are applied to RLOS PDN connection that is established by an MME upon UE request. The MME RLOS Configuration Data contain the RLOS APN which is used to derive a PDN GW, or the MME RLOS Configuration Data may contain the statically configured PDN GW for the RLOS APN.

UEs in limited service state intending to access Restricted Local Operator Services determines that the cell supports RLOS services over E-UTRAN via a broadcast indicator in AS and subsequently initiates the Attach procedure with an indication that the attach is to access RLOS. The Networks supporting Restricted Local Operator Services provides access to these UEs, regardless whether authentication for the UEs is performed or not, and regardless of the authentication result if authentication is performed. If the PLMN does not advertise its support of RLOS, the UE shall block the origination attempt for RLOS.

Restricted Local Operator Services is applicable to WB-E-UTRAN only. Restricted Local Operator Services does not support UE requested PDN connectivity, inter-RAT mobility and Network triggered Service Request. Handover between 3GPP and non-3GPP accesses are not supported for UEs attached for RLOS. Location service does not apply to Restricted Local Operator Services.

NOTE 1: During situations when, for example, there is lack of resource in E-UTRAN, the E-UTRAN node can set the broadcast indicator accordingly in order to indicate that the RLOS UEs in the cell are not allowed.

NOTE 2: The RAN can take into account that the UE is attached for access to RLOS when setting the UE inactivity timer to avoid unnecessary release of the RRC connection in situations where the network response takes time to arrive.

On-line charging is not activated for RLOS APN. For off-line charging, an RLOS APN indication as well as IMEI, if available, is added to charging records.

4.3.12a.2 Architecture Reference Model for Restricted Local Operator Services

The same architecture as for emergency service specified in clause 4.3.12.2 applies.

4.3.12a.3 Mobility and Access Restrictions

When access to Restricted Local Operator Services is supported, the Mobility Restrictions in clause 4.3.5.7 should not be applied to UEs receiving Restricted Local Operator Services. However, for a RLOS attached UE, the MME shall restrict mobility to GERAN and UTRAN, and include GERAN and UTRAN in the Handover Restriction List.

4.3.12a.4 PDN GW selection function for Restricted Local Operator Services

Same mechanism as for emergency service specified in clause 4.3.12.4 applies with the following difference:

For Restricted Local Operator Services, RLOS Configuration Data containing RLOS APN is needed in MME. However, HRPD or WLAN handovers don’t apply.

4.3.12a.5 QoS for Restricted Local Operator Services

The initial QoS values used for establishing RLOS PDN connection during RLOS attach are obtained from the MME RLOS Configuration Data.

4.3.12a.6 PCC for Restricted Local Operator Services

Dynamic PCC based on the procedures described in TS 23.203 [6] may be used for UEs accessing Restricted Local Operator Services which involve voice services. When establishing PDN connection towards the RLOS APN with a PDN GW, according to clause 4.7.5, the PCRF provides the PDN GW with the QoS parameters, based on operator policy, including an ARP value reserved for the Restricted Local Operator Services where RLOS has a lower priority in terms of admission control than regular PDN connections

The PCRF ensures that the RLOS PDN connection is used only for Restricted Local Operator Services. The PCRF rejects an IMS session established via the RLOS PDN connection if the AF (i.e. P-CSCF) does not provide an RLOS indication to the PCRF.

4.3.12a.7 IP Address Allocation

RLOS is provided by the serving PLMN. The UE and PLMN must have compatible IP address versions in order for the UE to obtain a RLOS PDN connection. IP address allocation in the serving PLMN is provided according to clause 5.3.1 with the exception that the PDN GW associated with the RLOS APN shall support PDN type IPv4 and PDN type IPv6.

4.3.12a.8 Emergency service for RLOS attached UE

For an RLOS attached UE initiating emergency service, the UE shall first perform a local detach prior to initiating an emergency attach as described in TS 24.301 [46].