Release 11 Features
Advanced IP Interconnection of Services
The objective is 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.
To ensure that requirements are identified for the Stage 2 & 3 work to identify relevant existing specifications, initiate enhancements and the development of the new specifications as necessary.
Release 11 Studies
Study on IMS based Peer-to-Peer Content Distribution Services
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 improvements are needed to cater for content distributed services for above accesses;
- Evaluating possible impacts and improvements on network when IMS based content distribution services are deployed;
- Identifying QoS, mobility, charging and security related requirements in the case of content distribution services on IMS;
- Identifying potential copyright issues;
Study on Non Voice Emergency Services
The Non Voice Emergency Services could support the following examples of non-verbal communications to an emergency services network:
1. Text messages from citizen to emergency services
2. Session based and session-less instant messaging type sessions with emergency services
3. Multi-media (e.g., pictures, video clips) transfer to emergency services either during or after other communications with emergency services.
4. Real-time video session with emergency services
In addition to support the general public, this capability would facilitate emergency communications to emergency services by individuals with special needs (e.g., hearing impaired citizens).
The objectives of this study include the following questions for Non Voice Emergency Services with media other than or in addition to voice:
1. What are the requirements for Non Voice Emergency Services?
2. What are the security, reliability, and priority handling requirements for Non Voice Emergency Services?
3. How is the appropriate recipient emergency services system (e.g., PSAP) determined?
4. Are there any implications due to roaming?
5. Are there any implications to hand-over between access networks
6. 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)?
7. Do multiple communication streams (e.g., voice, text, video emergency services) need to be associated together?
8. What types of “call-back” capabilities are required?9. 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
The intent of this study item is to identify use cases and requirements enabling Mobile Network Operators to distribute new services based on the USIM, to improve the customer experience and ease the portability and customisation of operator-owned and customer-owned settings from one device to another (such as APN and other 3G Notebook settings, graphical user interface, MNO brand, Connection Manager settings,…), and help in reducing operation costs and radio resources usage.
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;
- To 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
M2M demand is forecast to grow from 50M connections to over 200M by 2013. A large number of these services are today deployed over circuit-switched GSM architectures and require E.164 MSISDNs although such services do not require "dialable" numbers, and generally do not communicate with each other by human interaction.
Without technical alternative to using public numbering resources as addresses, and considering the current forecasts and pending applications for numbers made to numbering plan administration agencies, there is a significant risk that some national numbering/dialling plans will run out of numbers in the near future, which would impact not only these M2M services but also the GSM/UMTS service providers in general.
The Objective is to 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