Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 22.011  Word version:  17.3.0

Top   Top   Up   Prev   None
1…   3…   4…   5…

 

5  Support of Localised Service Area (SoLSA)

SoLSA consists of a set of service features that give the operator a basis to offer subscribers different services (e.g. tariffs or access rights) depending on the location of the subscriber (TS 42.043). The following section is only applicable to the support of SoLSA functionality in GERAN.

5.1  Network selection

The standard automatic and manual network selection procedures will be used.
Manual network selection may be required when the PLMN providing the users SoLSA service is not the one on which the user is currently registered.
At manual network selection the UE shall provide the means to present the subscribers LSA(s) for each PLMN presented.

5.2  The Idle-mode operation

The UE shall always select a valid LSA with the highest priority.

5.2.1  Subscriber moving from a normal environment to his localised service area.

The UE shall have the ability to prioritise allowed LSA cells in reselection, making it possible to camp on a LSA cell earlier (the function shall be network controlled).

5.2.2  Subscriber moving away from his localised service area to a normal environment.

The UE shall have the ability to prioritise allowed LSA cells in reselection, making it possible to camp on a LSA cell longer (the function shall be network controlled).

5.2.3  Subscriber staying in his localised service area

The UE shall have the ability to prioritise allowed LSA cells in reselection by being more persistent (the function shall be network controlled).

5.3  LSA only accessWord‑p. 25
It shall be possible to allow LSA user to access PLMN only within his LSAs. A LSA user is not allowed to receive and/or originate a call outside the allowed LSA area.
When UE is out of the allowed LSA area it shall be registered in PLMN but indicate subscriber/service specific "out of LSA area" notification. It shall be a network-controlled function to prevent terminated or/and originated calls. Emergency calls are however always allowed.

5.4  Exclusive access

Access to exclusive access cells is restricted to defined LSA subscribers.
Non-LSA subscriber shall consider exclusive access cells as not suitable, only allowing to camp for emergency calls (limited service state TS 23.122).

5.5  Preferential access

As a network-controlled function, it shall be possible in LSA to allocate resources at call setup and during the active mode to LSA users compared to non-LSA users.

6  Support of 3GPP - WLAN Interworking |R6|

Support of 3GPP-WLAN interworking and network selection is captured in TS 22.234

7  Administrative restriction of subscribers' access |R6|

7.1  Allowed Location and Routing Area identities access |R8|

Means shall be standardised for an administrative restriction of subscribers' access without the need of having explicit Tracking/Location/Routing Area identities in the individual subscription profiles.
To achieve this it shall be possible to indicate per subscriber, in subscription data, allowed categories of Tracking/ Location/Routing Areas. It shall be possible to use this subscription information to restrict subscribers' access to categories of Tracking/Location/Routing Areas in serving networks accordingly.
As a minimum, at least one of the following categories shall be available:
  1. GERAN
  2. UTRAN
  3. E-UTRAN
  4. NG-RAN
There might be cases where the visited network has not separated the Location/Routing area categories, in which case the administrative restriction of subscribers' access to only GERAN or UTRAN will not be possible.
In EPS, an operator may introduce subscriptions supporting the 5G NR Dual Connectivity in E-UTRAN. It shall be possible to indicate in subscription data that a subscriber's access to the 5G NR Dual Connectivity in E-UTRAN service is restricted.
This administrative restriction of subscribers' access shall be an optional feature.
Up

7.2Void

7.3  UE configured radio technology restriction |R16|Word‑p. 26
A UE shall support a Man Machine Interface setting for the user to disable use of one or more of the UE's radio technologies, regardless of PLMNs. Radio technologies that individually can be disabled is dependent on supported radio technology of the UE such as GSM/EDGE, WCDMA, E-UTRA, and NR.
A UE shall support a Man Machine Interface setting enabling the user to re-enable use of one or more of the ME's radio technologies for access to a radio access network, regardless of PLMNs. The user can only re-allow a radio technology that the user has previously disallowed.
A UE shall support a secure mechanism for the home operator to disallow selection of one or more of the UE's radio technologies for access to a radio access network, regardless of PLMNs. Radio technologies that individually can be disallowed are at least GSM/EDGE, WCDMA, E-UTRA, and NR.
A UE shall support a secure mechanism for the home operator to re-allow selection of one or more of the UE's radio technologies for access to a radio access network, regardless of PLMNs. Radio technologies that individually can be re-allowed are at least GSM/EDGE, WCDMA, E-UTRA, and NR. The home operator can only re-allow a radio technology that the home operator has previously disallowed.
For a prioritized service (e.g., Emergency Services, MPS, Mission Critical Services), the UE shall support a mechanism to automatically override user and network disallowed RATs when there are no PLMNs on the allowed radio technologies identified that the UE is able to access.
Upon power-cycle or when the USIM is disabled, the UE configuration of enabled/disabled radio technologies configured by the user shall remain as it was before such events happen. The radio technologies disallowed by the HPLMN shall remain as it was before a power cycle. The radio technologies disallowed by the HPLMN shall be bound to the USIM
Up

8  Support of Home NodeB and Home E-NodeB |R8|

The service requirements for Home NodeB and Home eNodeB can be found in [14].

9  Control of traffic from UE-based applications toward associated server |R14|Word‑p. 27

9.1  Description

This feature allows operators to control traffic from UEs to an application on a third-party server or the third-party server itself. When an application on a third-party server or the third-party server itself becomes congested or fails the traffic towards that server need to be controlled to avoid/mitigate potential issues caused by resulting unproductive use of 3GPP network resource. This will also make it possible to allow 3GPP network to help third party servers to handle overload and recover from failures (see [7]).
Up

9.2  Requirements

Under network control, the UE shall be able to control (i.e. block and/or prioritize) traffic from UEs to an application on a third-party server or the third-party server itself without affecting traffic to other applications on the third-party server or to other third-party servers.
For this purpose, the UE shall be able to identify the traffic towards the third-party server or the application on the third-party server.
When congestion or failure of the application on the third-party server or the third-party server abates, the control shall be applied in a phased manner to gradually restore traffic according to operator policy.
This feature and other forms of access control shall be able to be applied simultaneously.
In case of simultaneous application of ACDC and this feature, this feature shall take precedence over ACDC to control traffic from applications in the UE, only when such traffic is allowed by ACDC.
This feature shall be applicable both to new connections being set up and to existing connections from the UE towards an application on a third-party server or the third-party server.
Up

10  3GPP PS Data Off |R14|

10.1  Description

3GPP PS Data Off is a feature which, when configured by the HPLMN and activated by the user, prevents transport via PDN connections in 3GPP access networks of all data packets except IP packets required by 3GPP PS Data Off Exempt Services.

10.2  Requirements

The 3GPP system shall provide a mechanism by which an operator can configure which operator services are defined as 3GPP PS Data Off Exempt Services for their own subscribers.
When 3GPP PS Data Off is activated in the UE, in order to preserve charging consistency:
  • the UE shall inform the network that 3GPP PS Data Off is activated,
  • the UE shall cease the sending of uplink IP Packets of all services that are not 3GPP PS Data Off Exempt Services via PDN connections in 3GPP access networks,
  • the network shall cease the sending of downlink IP Packets to the UE for all services that are not 3GPP PS Data Off Exempt Services via PDN connections in 3GPP access networks,
  • the UE shall cease the sending of uplink traffic over non-IP PDN types via PDN connections in 3GPP access networks, and
  • the network shall cease the sending of downlink traffic over non-IP PDN types via PDN connections in 3GPP access networks.
Each of the following operator services shall be configurable by the HPLMN operator to be part of the 3GPP PS Data Off Exempt Services:
  • MMTel Voice;
  • SMS over IMS;
  • USSD over IMS (USSI);
  • MMTel Video;
  • Particular IMS services not defined by 3GPP, where each such IMS service is identified by an IMS communication service identifier;
  • Device Management over PS
  • Management of USIM files over PS (e.g. via Bearer Independent Protocol); and
  • IMS Supplementary Service configuration via the Ut interface using XCAP.
3GPP PS Data Off may be activated based on roaming status, and the HPLMN may configure up to two sets of 3GPP PS Data Off Exempt Services for its subscribers: one is used when in HPLMN and another when roaming.
The user should be made aware of the operator services that are 3GPP PS Data Off Exempt Services.
Up

$  Change historyWord‑p. 29

Up   Top