18.6 Study on Paging Permission with Access Control (fs_ppac) uid_330016

Resources: S1

References

Document	Title/Contents
WID(s)
SP-060785	SID on Paging Permission with Access Control (PPAC)
Impacted Specifications
-	-
New Dedicated Specifications/Reports
TR 22.908	Study on Paging Permission with Access Control (PPAC)

Supporting Individual Members: Fujitsu, NEC, NTT DoCoMo, Toshiba.

The Study on Paging Permission with Access Control (PPAC) investigated three issues caused by the current access control mechanism, which does not allow to reach UEs for which access class restriction was applied:

• Priority service There is a priority communication service which is produced to an authorized user (e.g. government) by using priority mechanisms such as special access class (i.e. access classes 11 to 15) allocation and high priority level allocation of eMLPP (enhanced Multi-Level Precedence and Pre-emption). However, there is an issue in the congestion situation (e.g. caused by earthquake) that the authorized user cannot access to the corresponded user when access class barring is applied to the corresponded user.

• Emergency service User sets up an emergency call and it is unfortunately released. At the condition, emergency agencies (e.g. police) would like to call back the user. However in the current specification, it is impossible to call back if access control restriction has been applied to the user.

• Communication between UEs in the same area where access control is performed There is an area where access control is performed. In order to allow all the users in the area to setup calls, broadcasting access class numbers are changed at an interval of some seconds. For example, in an interval UEs with access class 0 can perform setup and UEs with access classes 1-9 cannot do setup, in another interval UEs with access class 1 can do setup and UEs with access classes 0, 2-9 cannot do setup. However there is an issue that communication between UE with an access class number and UE with another access class number cannot be established in the area. The communication helps users in emergency situation, e.g. a mother's call to her child to know where he/she is.

TR 22.908 conclusion

• Use-cases investigated, performed gap analysis and clarified issues;

• Requirements recommended for PPAC (paging permission of the UE applied access control);

• Only one new capability identified: allow UEs with indications from the network to perform location registration and respond to a paging request even though it is under access class barring conditions to complete certain classes of calls or messages (e.g. calls from emergency personnel, etc. ).

Spin-off Rel-8 Feature UID_370084 (PPACR)

18.7 Study on Non-3gpp access Network Selection Principles (nsp) uid_340033

Resources: S1

References

Document	Title/Contents
WID(s)
SP-080318	SID on Study on Non-3GPP access Network Selection Principles (NSP)
Impacted Specifications
-	-
New Dedicated Specifications/Reports
TR 22.912	Study into network selection requirements for non-3GPP access

Supporting Individual Members: O2, RIM, Gemalto, BT, Softbank Mobile.

Network access via WLAN is becoming more widespread. UEs supporting both 3GPP and non-3GPP access technologies such as WLAN become available. Hence, it is important to have clear requirements describing how multiple access devices use and prioritize networks providing these access technologies.

Selection of networks available only through non-3GPP access technologies is not covered yet by 3GPP and therefore how mobile devices select these networks is undefined.

Non-3GPP access technologies were considered in Rel-7 TR 22.811 (Review of Network Selection Principles), which concluded that where multiple technologies are available in a given location, a single mechanism for identifying preferences should be provided.

This work studies how a UE supporting networks through both 3GPP and non-3GPP accesses performs the network selection procedures. It could lead updating TS 22.011 (Service accessibility) to include selection of networks offering these access types. The following aspects for networks offered through non-3GPP access types were considered:

• Automatic selection

• Manual selection

• Operator management of network preferences;

• Operator management of how the device accesses networks.

TR 22.912 provides five use cases; one being when a GSM/3G operator has a commercial relationship with a 3^rd party content provider having its own WLAN giving access to a server containing specialized content and services (e.g. music download). The operator arranges with the 3^rd party that its subscribers can access the 3^rd party over its WLAN to complement its own products and services available over GSM/3G. Authentication and authorization in the WLAN is independent of authentication and authorization in the 3GPP network.