Use Case for Non-3gpp access nsp

The connection to the 3^rd Party is temporary while delivering content or other service. The UE remains registered on the PLMN while also being connected to the WLAN access.

The facility to set an operator- (and user-) defined preference for the selection of this WLAN network is required.

TR 22.912 conclusions

Currently, the network selection behaviour of the UE is defined only for 3GPP access types (i.e. GERAN, UTRAN, E-UTRAN, I-WLAN). With increasing availability of UEs supporting other types of access (currently mainly WLAN but could include other types) it is desirable to define how and when these new access types can be selected.

The reason for this is to ensure predictable behaviour and also allow the user or application to select the most appropriate type of access for the service required. The various considerations include ability to uniquely identify the access, security, the circumstances under which the non-3GPP access would be selected and the user experience.

Concerning the access identity, an agreement should be sought with the specification body (IEEE 802.11) on how to uniquely identify the access. Security requirements should be met and may need consultation with other groups.

A mechanism needs to be defined to control how the UE selects non-3GPP access types and this should complement the mechanisms already in place for the selection of 3GPP access types (GERAN, UTRAN, E-UTRAN, I-WLAN). This should include similar features to those for PLMN network selection mechanism including consideration of "Steering of Roaming".

NOTE: "Steering of Roaming" by the VPLMN is not envisaged for GSM or UMTS.

TR 22.912 identifies requirements for selection of non-3GPP access and lead to TS 22.011 / TS 22.234 CRs.

Spin-off New Feature UID_380062 (N3GTONSP)

18.8 Study on Value-Added Services for Short Message Service uid_340034

Resources: S1

References

Document	Title/Contents
WID(s)
SP-060786	SID on Study on Value-Added Services for Short Message Service
Impacted Specifications
-	-
New Dedicated Specifications/Reports
TR 22.942	Study on Value Added Services (VAS) for Short Message Service (SMS)

Supporting Individual Members: China Mobile, Huawei, Comverse, TeliaSonera, RIM.

This study assesses requirements for Value-Added Services (VAS) for the Short Message Service (SMS) and identifies which can be met by existing solutions or could be candidates for future standardization. The study covered:

• Service definition of different VAS for SMS;

• Service interaction between different VAS for SMS;

• Existing solutions from other standards bodies (OMA etc.);

• Identify provisioning aspects of VAS for SMS (e.g. registration, activation, deactivation and withdrawal).

It studied enhanced SMS features, which is of great importance for increasing mobile operators' revenues. These enhanced capabilities for SMS are proposed as VAS for SMS and include:

• SM forwarding permits a called mobile subscriber to have the network send all incoming SMs, addressed to the called mobile subscriber's directory number to another directory number. SMs can be forwarded unconditionally, or based on different time period, etc.

• SM filtering permits the network to filter some SMs on behalf of a called party based on the called party's preferences (e.g. calling party's number, time to send message, etc).

• SM receipt permits the network to send a receipt (that the called party has customized) to the calling party.

• SM network storage permits the network helping the subscriber to store messages that the subscriber has sent or received.

Due to some limitations of the current architecture to deploy VAS, SA1 examined:

• The most efficient solution for the implementation of VASs for SMS;

• The most appropriate way to specify such functionality in 3GPP documentation;

• The architectural impact on the existing 3GPP defined architecture;

• If full backward compatibility with existing SMS architecture can be guaranteed.

TR 22.942 conclusions

• Studied requirements of VASs for SMS, which are enhancements (or supplements) of GSM SMS requirements;

• Recommends creating Stage 1 followed by Stage 2 specifications on VAS for SMS in 3GPP;

• Architecture and protocol of various VAS listed in TR 22.942 should be consistent with each other;

Genealogy of this spec:

this spec	descendant(s)
22.942	22.142

Spin-off Rel-9 Feature UID_370026 Value-Added Services for Short Message Service (VAS4SMS).