3GPP has already started work on Release 11. See objectives of features & study items from 3GPP Work Items below.

3GPP has already started work on Release 11. See objectives of features & study items from 3GPP Work Items below.

Advanced IP Interconnection of Services (source: 3GPP Work Item SP-100227)

To specify the technical requirements for carrier grade inter-operator IP Interconnection of Services for the support of Multimedia services provided by IMS and for legacy voice PTSN/PLMN services transported over IP infrastructure (e.g. VoIP). These technical requirements should cover the new interconnect models developed by GSMA (i.e. the IPX interconnect model) and take into account interconnect models between national operators (including transit functionality) and peering based business trunking. Any new requirements identified should not overlap with requirements already defined by other bodies (e.g. GSMA, ETSI TISPAN). Specifically the work will cover: 

• Service level aspects for direct IP inter-connection between Operators, service level aspects for national transit IP interconnect and service level aspects for next generation corporate network IP interconnect (peer-to-peer business trunking).
• Service layer aspects for interconnection of voice services (e.g. toll-free, premium rate and emergency calls).
• Service level aspects for IP Interconnection (service control and user plane aspects) between Operators and 3rd party Application Providers.

Study on IMS based Peer-to-Peer Content Distribution Services (source: 3GPP Work Item SP-090491)

The objectives are to study IMS based  content distribution services with the following aspects: 

Identifying the user cases to describe how users, operators and service providers will benefit by using/deploying IMS based  content distribution services. such as with the improvement of Peer-to-Peer technology. The following shall be considered:

• Mobile access only (e.g. UTRAN, E-UTRAN, I-WLAN);
• Fixed access only (e.g. xDSL, LAN);
• Fixed and mobile convergence scenarios;
• Identifying service aspects where IMS network 

Study on Non Voice Emergency Services (source: 3GPP Work Item SP-090897)

The objectives of this study include the following questions for  Non Voice Emergency Services with media other than or in addition to voice:

• What are the requirements for Non Voice Emergency Services?  
• What are the security, reliability, and priority handling requirements for Non Voice Emergency Services?
• How is the appropriate recipient emergency services system (e.g., PSAP) determined?
• Are there any implications due to roaming?
• Are there any implications to hand-over between access networks
• Are there any implications due to the subscriber crossing a PSAP boundary during Non Voice Emergency Services communications (e.g., subsequent text messages should go to the same PSAP)?
• Do multiple communication streams (e.g., voice, text, video emergency services) need to be associated together?
• What types of “call-back” capabilities are required?
• Investigate the load impact of Non Voice Emergency Services in the case of a large scale emergency event or malicious use.

Non Voice Emergency Services will be applicable to GPRS (GERAN, UTRAN) and to EPS (GERAN, UTRAN, E-UTRAN and non-3GPP).

Study on UICC/USIM enhancements (source: 3GPP Work Item SP-090852)

Objectives of this study item are:

• To identify use cases and requirements for new USIM-based services taking into account the GSMA Smart SIM deliverables;
• o identify use cases and requirements for the USIM used inside terminals with specialised functionalities (e.g. radio modems, 3G Notebook terminals) taking into account the GSMA 3GNBK deliverables;
• To identify use cases and requirements to drive the evolution from the traditional USAT to a multimedia USIM toolkit support, with a particular aim to the Smart Card Web Server;

Study on Alternatives to E.164 for Machine-Type Communications (source: 3GPP Work Item SP-100198)

Determine an alternative to identify individual devices and route messages between those devices. Requirements for this alternative include:

• Effectively identify addressing method to be used for end point devices
• Effectively route messaging between those devices
• Support multiple methods for delivering messages, as defined by 22.368
• Support land-based and wireless connectivity
• Make use of IP-based network architectures
• Addressing/identifiers must support mobility and roaming
• support on high speed packet-switched networks when available and on circuit-switched networks
• Consider if there are security issues associated with any alternatives