Content of the presentation

• Click to edit Master text stylesClick to edit Master text styles• Second levelSecond level• Third levelThird level• Fourth levelFourth level• Fifth levelFifth level

John M Meredith & Alain Sultan – 2003-09-15 1

3GPP – OMA Workshop3GPP – OMA WorkshopFrankfurt, 15 September 2003Frankfurt, 15 September 2003

The current 3GPP work programmeThe current 3GPP work programme

John M MeredithJohn M Meredith3GPP Specifications Manager3GPP Specifications Manager

([email protected])([email protected])

Alain SultanAlain Sultan3GPP Technical Coordinator3GPP Technical Coordinator

([email protected])([email protected])

ETSI Mobile Competence Centre ETSI Mobile Competence Centre



Content of the presentationContent of the presentation

• Management of the 3GPP work Management of the 3GPP work programmeprogramme

• Foreseen content of 3GPP Release 6Foreseen content of 3GPP Release 6• Identified interactions between 3GPP work Identified interactions between 3GPP work

and OMA workand OMA work• ConclusionConclusion






>>




A new version of the 3G system defined by 3GPP is produced periodically A new version of the 3G system defined by 3GPP is produced periodically (roughly every 18 months so far). Each version is called a “Release”.(roughly every 18 months so far). Each version is called a “Release”.

Each new Release builds on the functionality and capability of the previous Each new Release builds on the functionality and capability of the previous Release. The intention is to maintain backwards compatibility at all times. Release. The intention is to maintain backwards compatibility at all times.

Each Release is composed of a set of new “features”, which are defined as Each Release is composed of a set of new “features”, which are defined as new or substantially enhanced functionality which represents added value to new or substantially enhanced functionality which represents added value to the existing system. In this way, new features can be introduced incrementally the existing system. In this way, new features can be introduced incrementally with no disruption to existing services. Newer Release terminals will fall back with no disruption to existing services. Newer Release terminals will fall back to the capabilities of an older Release network (and vice versa). to the capabilities of an older Release network (and vice versa).

The interdependence of individual features is minimized to allow network The interdependence of individual features is minimized to allow network operators and terminal manufacturers to provide services tailored to identified operators and terminal manufacturers to provide services tailored to identified commercial needs.commercial needs.




The current 3GPP work programme, and the set of Features being actively The current 3GPP work programme, and the set of Features being actively defined, is monitored by the Work Plan. The Work Plan is an MS Project file defined, is monitored by the Work Plan. The Work Plan is an MS Project file showing those features which are currently being developed as enhancements showing those features which are currently being developed as enhancements to the existing system. Exports of the Work Plan are available in Excel, PDF to the existing system. Exports of the Work Plan are available in Excel, PDF and HTML views.and HTML views.

Further information on the Work Plan can be found at:Further information on the Work Plan can be found at:

http://www.3gpp.org/Management/WorkPlan.htmhttp://www.3gpp.org/Management/WorkPlan.htm



The current 3GPP work programmeThe current 3GPP work programmeThe quickest way to see the Work Plan is to use the HTML view inThe quickest way to see the Work Plan is to use the HTML view inhttp://www.3gpp.org/ftp/Specs/html-info/GanttChart-Level-1.htm.http://www.3gpp.org/ftp/Specs/html-info/GanttChart-Level-1.htm.

The features are the The features are the top level tasks. top level tasks. They are They are hyperlinked both to hyperlinked both to informal informal descriptions of the descriptions of the work and to their work and to their formal Work Item formal Work Item Description (WID) Description (WID) documents.documents.

Each feature is Each feature is composed of sub-composed of sub-tasks, which can be tasks, which can be seen by clicking on seen by clicking on the appropriate the appropriate button.button.




The view can be The view can be expanded to see expanded to see sub-tasks as well.sub-tasks as well.




This is the This is the expanded view, expanded view, showing the sub- showing the sub- tasks composing tasks composing the features.the features.






>>




The slides which follow give an overview of each Feature planned to be The slides which follow give an overview of each Feature planned to be introduced in Release 6.introduced in Release 6.

Interdependencies between a few of these Features and work being conducted Interdependencies between a few of these Features and work being conducted within OMA has already been identified, and this is illustrated by the final group of within OMA has already been identified, and this is illustrated by the final group of slides.slides.



Feature: Improvements of radio interface

The objective for this feature is to ensure that mechanisms are provided to allow enhancement of the radio interface in a backward compatible manner.

It is best understood by examining the more important component building blocks:

•Improvement of inter-frequency and inter-system measurement

•UMTS-850

•DS-CDMA introduction in the 800 MHz band

•UMTS 1.7/2.1 GHz

•(others to follow)



Feature: Improvements of radio interfaceBuilding block: Improvement of inter-frequency and inter-system

measurements

Compressed mode in Release 99 covers a limited set of methods for enabling measurements on other frequencies. There have been methods suggested that potentially improve the system capacity and operational flexibility in addition to the existing methods.

The following two technologies have been identified as candidates for compressed mode improvements:

•Compressed mode with puncturing and flexible positions; and

•Combination of the existing methods (including method in first bullet point).

The purpose of this work item is to work on the compressed mode improvements for improved system performance.



Feature: Improvements of radio interfaceBuilding block: UMTS-850

WRC 2000 extended the current IMT-2000 frequency allocation to include bands (currently occupied by other services) within the band range 806-960 MHz.

This WI studies the possibility to migrate GPRS/EDGE, TIA/EIA-136, TIA/EIA/IS-95, and Analog AMPS to UTRA FDD in this new band, more precisely (to conform with ITU-R M.1036-1): 824 – 849 MHz: Uplink 869 – 894 MHz: Downlink.

•Potential deployment is foreseen to take place only in ITU Region 2



Feature: Improvements of radio interface Building block: DS-CDMA introduction in the 800 MHz band

Referring to this same new band allocated by WRC-2000 (806 to 960 MHz), this WI studies the possibility of introducing DS-CDMA in the 800 MHz band in Japan, including impact on co-existing with ARIB STD-27(PDC), ARIB STD-T53(IS-95), and ARIB STD-T64 (cdma 2000), taking the frequency reframing plan in Japan into account.

The specific bands to be studied are (consistent with ITU-R M.[1036-1]): 810 – 855 MHz: Uplink 855 – 900 MHz: Downlink



Feature: Improvements of radio interface Building block: UMTS 1,7/2,1 GHz

Additional spectrum was identified for IMT-2000 at WRC-2000, including the band 1710-1885 MHz.

This WI aims at using this new band to allow band pairing between 1710 MHz UL and 2110 MHz DL for potential deployment only in ITU Region 2. More precisely, it studies the radio requirements of introducing UTRA FDD as follows:

1710 – 1770 MHz: Uplink 2110 – 2170 MHz: Downlink

It will also study the limitation to 1710 – 1755 MHz for Up-link and to 2110 – 2155 MHz for Down-link to restrict to the current FCC band allocation.



Feature: Multiple Input Multiple Output (MIMO) antennas

The purpose of this work item is to improve system capacity and spectral efficiency by increasing the data throughput in the downlink within the existing 5 MHz carrier. This can be achieved by means of deploying multiple antennas at both UE and Node-B side. The technical objective of this work item is the integration of MIMO functionality in UTRA, both FDD and TDD.

There is no intention to make MIMO mandatory in the UE.



Feature: Single Antenna receiver Interference Cancellation (SAIC)

The use of Single Antenna Interference Cancellation (SAIC) techniques has been proposed as a method for increasing the spectral efficiency of GSM/EDGE networks. These techniques are especially attractive for the downlink since they do not require multiple antennas.

This work item is a feasibility study to determine the potential of SAIC in typical network layouts. This includes study of the following aspects:

•Feasibility of SAIC for GMSK and 8PSK scenarios under realistic synchronized and non-synchronized network conditions. •Realistic DIR (Dominant-to-rest of Interference Ratio) levels and distributions based on network simulations and measurements. •Robustness against different training sequences. •Determine method to detect/indicate SAIC capability.



Feature: RAN improvements

This work item intends to introduce new mechanisms allowing improvements on all aspects dealing with the radio network subsystem internal interfaces, as well as the interface towards the core network. This includes transport of user and signalling plane as well as protocols over all interfaces of the radio network subsystem.

Work under this feature includes at present:

• Improvement of beamforming, • Network-assisted cell-change (UTRAN-GERAN),• Remote Control of electrical antenna tilting,• RAB support enhancement (Iu enhancements for IMS support in the RAN),• Improvement of RRM across RNS and RNS/BSS

as well as feasibility studies.



Feature: PS domain and IMS impacts for supporting IMS emergency calls

This WI aims at enabling the establishment of an emergency session via the packet-switched domain and the IP multimedia core network subsystem. The emergency sessions will be routed to an emergency centre in accordance with national regulations.

Due to the variability of emergency numbers in different networks, which is particularly problematical when roaming, the PS emergency session will be established without the need to dial a dedicated number: for example, selection of emergency session from the menu, linkage to a vehicle air-bag trigger, …

The feature addresses the normal case where the mobile equipment contains a valid USIM, and also the case where no USIM is fitted. The main focus is on SIP emergency sessions and related packet bearers.



Feature: Location Services enhancements 2

The objective is to align the 3GPP location services specifications and similar services developed in other fora, and to enhance the network support for user privacy in those services.

Specifically:•Standardization of the Le interface, alignment of LCS specifications •Enhanced support for anonymity and user privacy via support for anonymous target mobile users and enhanced codeword functionality •Enable LCS clients to use IMS public user identities (e.g. when a service such as Presence requests ME location information). •Develop the functionality to generate LCS triggering reports when an ME is within, or enters, or leaves, a defined area.



Feature: Uplink Time Difference of Arrival (U-TDOA) location determination for GSM / GPRS

The objective of this Work Item is to include Uplink TDOA as a User Equipment location determination method for GSM/GPRS. Priority for this work item is on achieving the US FCC’s E911 October 2003 location accuracy requirements for network-based location methods. These requirements are 100m (67%) and 300m (95%) levels of accuracy.



Feature: IMS phase 2

This is a continuation of the IMS feature included in Release 5.

This feature is a collection of independent IMS enhancements listed below:•Enhancements to the Cx and Sh interfaces •IMS Group Management •IMS Conferencing •IMS Messaging •IMS Local services •Interworking between IMS and IP networks •Mm interface (CSCF to external IP multimedia network) •Interworking between IMS and CS networks •Mn interface (IM-MGW to MGCF) enhancements •Mp (MRFC - MRFP) interface protocol definitions •Study of subscriber and operators relationship in IMS and related ISIM requirements for Rel 6 •Lawful Interception in the 3GPP Rel-6 architecture •IMS Subscription and access scenarios



Feature: Radio optimization impacts on PS domain architecture

For IM conversational services, some radio optimization such as Unequal Error Protection can be provided for PS multimedia services, and the introduction of such enhancement may bring architectural questions that have to be studied.

The objective of the Work Item is to consider the architectural impacts (on the core network) of radio optimization provided for services such as IMS that require the transport of real time traffic over the PS domain (both GERAN and UTRAN).



Feature: Interoperability and commonality between IMSs using different "IP-connectivity networks"

In Release 5, IMS is optimized for the 3GPP UMTS and GSM access networks. However, economies of scale (in terms of hardware, software and application development) should be improved by increasing the commonality of the IMS to different “IP-connectivity networks”, including specifically the 3GPP2 and W-LAN systems.

Similarly, it is necessary for users of one system to be able to “phone” (i.e. make a multimedia call with a speech component) users on another system. At least between 3GPP and 3GPP2 systems, this is currently problematic because the different systems use different transcoders in their mobiles.

The objective is:•To improve the commonality between the IMS systems used by 3GPP, 3GPP2 and that needed for W-LAN. •To ensure that users of the different IMSs can inter-operate.



Feature: Multimedia Messaging Service (MMS) enhancements

Further work is identified for MMS to take into account the following independent areas:

•To consider and accommodate the needs for•IP Multimedia Subsystem (IMS) •alternative User Agent capabilities for MMS •detail description of User Profile mechanisms •security and privacy enhancements •Digital Rights Management (DRM)•Presence service by MMS •defining over-the-air provisioning of MMS •interaction with legacy handsets



Feature: Multimedia Messaging Service (MMS) enhancements (continued)

•And enhancements of functionalities on:•reference point MM1 (MMS Relay/Server and MMS UA/UE ) and MM4 (MMS Relay/Server to MMS Relay/Server) •interworking and transcoding issues •terminal capability negotiation mechanism to ensure terminal interoperability •USIM and USAT aspects of MMS •charging methods •interworking with external messaging systems and with VAS applications •streaming •addressing •network based storage model in MMSE •media types/formats and multimedia presentation



Feature: Rel-6 Mobile Execution Environment (MExE) enhancements

This feature consists of two separate elements:•MExE Rel-6 improvements and investigations •MExE run-time independent framework feasibility study

(continued on next slide)



Feature: Rel-6 MExE enhancementsBuilding Block: MExE Rel-6 improvements and investigations

MExE is based on the concept of identifying external standards suitable for supporting services from a UE, and bringing them into the 3GPP scope by direct reference. In particular MExE enables the access to content and services from operators', manufacturers' and third parties' servers, and from the Internet.

MExE Release 6 work extends and develops the UE-based support of the client/server model for the flexible support of 3G services (e.g. multimedia services), more specifically, MExE Release 6 targets the following areas:

•the terminal parts of the VHE User Profile or Generic User Profile•Investigate and identify support of USAT/OSA/CAMEL interaction to provided advanced services •Investigate and identify support of: security enhancements, terminal management support, service provisioning.

In fact, interest in MExE has waned, and only minor enhancements have actually been performed.



Feature: Rel-6 MExE enhancements Building Block: MExE run-time independent framework feasibility study

This Work Item intends to broaden the applicability of the MExE security framework and services, enabling all MExE run-time environments to operate with a consistent MExE service environment. In particular, the new features and capabilities of this Work Item should allow for independence from, and re-use by, an extremely large set of external standards corresponding to different run-time environments. It also allows for independent use of the framework for secure software downloads without the need of a MExE run-time environment.

The main benefit of these analyses is that the extracted (and potentially contracted) characteristics and requirements are applicable to run-time environments identified in the future, as well as currently available run-time environments. Other benefits include increased clarity and reduced complexity.

In fact, interest in MExE has waned, and only minor enhancements have actually been performed.



Feature: Subscription management

Subscription management standardization will significantly enhance the ability of 3GPP networks to offer complex services in the areas of:

•Multimedia •Data services •Value Added Services •End-to-end applications

This work item will refine the operational requirements, and define an architecture, data models, and integration reference points.



Feature: Support of Presence capability

"Presence" is the concept whereby users make themselves "visible" or "invisible" to other parties of their choice, allowing services to be offered. The concept of presence will enable other multimedia services to exploit this key enabler to support other advanced multimedia services. Examples of multimedia services that could potentially exploit the presence capability include "chat", e-mail, multimedia messaging, instant messaging, etc.

The objectives of this work item are to define and develop the support of the concept of presence information to facilitate multimedia services in a wireless network.



Feature: Flexible Layer One for GERAN

This feature will provide radio bearers (a flexible Layer One in GERAN Iu and A/Gb mode) that increase the spectral efficiency of real-time multimedia, streaming and other services that benefit from tailored SDU formats and low protocol overhead in GERAN.



Feature: Multimedia Broadcast and Multicast Service (MBMS)

Multicast/Broadcast are services that already exist in some form. For example, cell broadcast for text messages within GSM and IP multicast services in the internet. Both Multicast and Broadcast solutions should offer potentially large savings in network resource usage.

The objective is to provide a multicast/broadcast service architecture that meets the (existing) stage 1 requirements, and to consider architecture alternatives that may meet these requirements.



Feature: Speech recognition and speech-enabled services

Forecasts show that speech-driven services may play an important role on the 3G market. People want the ability to access information while on the move and the small portable mobile devices that will be used to access this information needs improved user interfaces using speech input.. A range of multi-modal applications is envisaged, incorporating different modes of input (e.g. speech, keyboard, pen) and speech and visual output.

The objective of this work item is to produce an analysis to understand how different architectures could work and co-exist, and to determine if there is a preferred solution (thus allowing minimization of the number of options needing to be supported by the 3GPP specifications).

The study will address both services and technologies including the possible locations of the speech recognition function (terminal, network, distributed, ...) and an evaluation of existing codecs and those under development.



Feature: Generic User Profile (GUP)

GUP is the collection of data which is stored and managed by different entities such as the UE, Home Environment, Visited Network and Value Added Service Providers, which affects the way in which an individual user experiences services. GUP is composed of a number of User Profile Components, and an individual service may make use of a subset of the available User Profile Components.Having several domains (i.e. CS, PS, IMS and service / application domains) introduces a wide distribution of data associated with the user. Several 3GPP WG already specify some parts of the GUP in their own descriptive methods. This distributed responsibility could lead to duplication and incompatibility amongst the GUP User Profile Components, so active coordination of the description methods is required.

The WI addresses the following aspects:•Definitions and scope of the GUP User Profile Components, and their storage, ownership, access methods, and distribution and some obvious common objects•The principles of a User Profile Policy (e.g. privacy aspects) •Protocols for transfer of User Profile data between cooperating elements of the 3GPP system.



Feature: Digital Rights Management (DRM)

Services and capabilities specified by 3GPP allow “content” (data, text, audio, video, etc.) to be delivered by streaming or downloading, and played or stored for future use on the mobile. Delivery methods may include forwarding onward from the device. It is essential to create a solution that will respect the intellectual property rights of the content owners.

The objective is to specify a framework that will support an interoperable, uniform, high-volume market for the distribution of protected content. Expression and enforcement of rights and rules - digital rights management - is an essential component of this distribution capability. In order for protected distribution of content to be acceptable to consumers, it must be transparent and non-intrusive, however security of downloadable and or streaming content must be preserved, i.e. it must not be possible to “play” unauthorized copies.

The work is limited to stage 1 specifications; the stages 2 and 3 work is expected to be performed by The Open Mobile Alliance.



Feature: Wireless-LAN to UMTS interworking

There is an increasing demand for wireless "local area" access in very different scenarios. Wireless access to Internet is provided to public users by the use of currently existing WLAN technology such as IEEE 802.11b. In companies, wireless access is provided to portable computer users by use of the same technology. For residential use, wireless access is also increasing. 3G technologies and systems will provide bearers for similar packet-switched services, with greater mobility and wider area coverage albeit with reduced data rate. WLAN technology can complement 3GPP-based networks in deployment environments with high user density and demand for higher data rates. However, in order to provide flexible use of both technologies in these environments and to provide mobility of services between the two technologies, it is sensible that some degree of interworking exist between them.

A feasibility study will be performed, covering the scenarios and possible architectures for interworking. Work will continue to produce specifications for the service and operational requirements.



Feature: Priority Service

There is a need to provide to authorized users (e.g. military, civil authorities) a preferential access to the network during crisis situations when the service might be restricted due to damage, congestion, or other faults.

The objective of this WI is to provide a secure and manageable mechanism to identify priority users and mark and guarantee their communications from access and call set up through to call completion. In the case of communications terminating on a mobile device, priority service includes priority egress.

A feasibility study will outline the technical requirements and scope of work required, and will perform a gap analysis to determine the extent existing 3GPP specifications can support these Priority Services requirements. If it is determined that providing for this service is feasible, then work will be extended to cover detailed specification.



Feature: Network sharing

The possibility of sharing part or all of the network by two or more separated commercial entities was not considered in the initial specification work of 3GPP. However, as e.g. a result of partnerships, the need for two or more operators to share common network infrastructure has become an economically desirable goal. Meanwhile, changes to public network operating licence conditions make such sharing possible from a regulatory point of view.

Some work has already been carried out in this area with the definition of the equivalent PLMN concept and partly with the introduction of Iu-Flex, but there is still the need to consolidate these activities under a coherent work plan.

This Work Item will first analyse the shortcomings of the standards in the area of network sharing, e.g. radio network sharing, and then develop enhanced requirements for the control of handover and cell reselection, services, charging, security in a shared network environment.



Feature: Quality of Service (QoS) improvements

The Release 5 IMS uses a policy control function (PCF) which is shown as being a logical entity of the P-CSCF. This does not enable a generic service policy to be applied to both IMS and non-IMS services. This WI aims at defining a standardized interface (the Go interface) between the PCF and application proxies (e.g. P-CSCF in the IMS). Initially, a study will be performed to assess how policy control used for IMS can interact with the appropriate IMS and non-IMS application servers.

Specifically, the study addresses the feasibility of the interface between the PCF and application proxies (e.g. P-CSCF in the IMS):

•Enable general policy control over IP bearer resources and SIP services to evolve separately; •Enable more flexibility in engineering and policy control of IP bearer resources; •De-couple policy functions from IMS entities.



Feature: Support for subscriber certificates

Digital signatures are the best way to secure mobile commerce, service authorization and accounting. The simplest way to introduce them in mobile networks is to make use of the existing authorization and charging infrastructure: they can indeed be used to provide local architecture for digital signatures.

Subscriber certificates provide a migration path towards global Public Key Infrastructure (PKI): operators do not have to wait for a world-wide PKI to benefit from public key technology as local architecture for digital signatures can be deployed incrementally. On the other hand, the existence of subscribers and service providers that use digital signatures makes it easier to build global PKI. The concept relies on authenticated signalling between mobile terminal and serving network and thus has to be standardized. The terminal and the serving network can interact only over standardized interface.

The objective is to make it possible to issue subscriber certificates in 3GPP systems in order to authorize and account for service usage both in home and in visited networks. This requires specification of:•Signalling procedures to issue temporary or long-term certificates to subscribers. •Standard format of certificates and digital signatures, e.g re-using wireless PKI.



Feature: Rel-6 Open Service Access (OSA) enhancements

OSA enables application developers compose services based on service enablers in the network. These enablers are accessed through open interfaces (the OSA APIs). The OSA API is independent of underlying network technology, and of vendor specific solutions and programming languages.

The Release 6 main enhancements of OSA are independent, as listed below:

•MMS relay / server to value-added service provider connectivity, to enable secure and trusted interaction of a MMS-VASP with the MMS relay / server. •Policy Management extensions•Presence and Availability Management for 3GPP IMS•OSA interfaces at different levels of abstraction (Web Services)•User Profile•Framework Function for federation•Network functions for user / application authentication. •Release flows in an IP session, control the IP session, monitor the IP session, and request of flow information.



Feature: Addition of frequency bands for GSM

The TETRA Advanced Packet Service (TAPS) standard is based on GPRS, the standards for which are maintained by 3GPP. It has been agreed by the ETSI groups responsible for TETRA that the TAPS standard will reference the relevant 3GPP specifications, which must therefore be enhanced to cater for the TAPS functionality and frequency band. This feature will permit the support of additional frequency ranges for TAPS / GPRS. In regions where TAPS is not employed, these frequencies may be used for GPRS.



Feature: Seamless support of streaming services in A/Gb mode

While full support of the streaming class is offered by the UTRAN, it cannot be guaranteed in GPRS, especially due to the large interruptions to the service at cell change. In order to have a seamless support across the PLMN, similar quality needs to be offered by the GERAN A/Gb mode and when changing RAN.

The objective of this WI is to analyse and provide the necessary changes and additions required for the efficient support of streaming services in the GERAN specifications.

This Work Item will focus initially on the setting and / or analysis of the requirements for the support of streaming services and the evaluation of the performance of the existing solutions and tools in the specifications.

The comparison between the requirements and the performance will determine whether/which improvements are pursued.



Feature: Performance characterization of default codecs for packet-switched conversational multimedia applications

The objective of this feature is to characterize the performance of default codecs for PS conversational multimedia applications.



Feature: Operations, Administration, Maintenance & Provisioning (OMA&P)

The objective of this Feature is to extend the OAM&P Framework in order to meet the requirements of the new features. As for previous Releases, this framework encompasses:

•Principles, high level Requirements and Architecture •Network Infrastructure Management •Performance Management •Trace Management •User Equipment Management



Feature: Charging management

The 3GPP specifications need to evolve in Rel-6 to allow additions and enhancements in the field of charging. New charging aspects are defined to cover both the enhancements to existing services and access technologies, and the provision of charging capabilities for the new Rel-6 Features (including Bearer, IMS and Service Charging aspects).

The structure of the charging specifications (TSs) is modified and now comprises:•a set of Implementers’ Guides (stage3 level descriptions) and •an “umbrella” specification (TS 32.240) that applies to all of the Implementers’ Guides.



Feature: Rel-6 UICC/USIM enhancements and interworking

This is an umbrella feature covering:•UICC API; and •Rel-6 USIM toolkit enhancements



Feature: Packet-switched streaming services (Rel-6)

The objective of this Feature is to standardize the components of a mobile multimedia content delivery service, including streaming protocols, media transport protocols and multimedia codecs, endeavouring to harmonize with existing and emerging 3GPP multimedia applications whenever possible.Solutions should be fully backwards-compatibile with the Rel-5 Extended Streaming standards.

This work item will cover:•Support for service adaptation: •Enabling adaptation based on capability exchange, including user preferences. •Support adaptation to varying network conditions. •Adaptation to network capabilities and characteristics (GERAN, UTRAN and WLAN). •Consideration of introduction of new codecs and formats. •Harmonized streaming support for MMS. •Consideration of introduction of a server file format and a file format for progressive download. •Real time monitoring of application level QoS.



Feature: Network Domain Security; Authentication Framework (NDS/AF)

The general objective is to develop a highly scaleable entity authentication framework for 3GPP network nodes belonging to the control plane of the core network.

The entity authentication is developed to replace the (not so scaleable) default IPsec/IKE use of pre-shared secrets to authenticate the network elements. The authentication framework will therefore be based on profiled X.509v3 type of digital certificates and of profiled public key infrastructure technology and standards.

The scope of this work item will be in accordance with and base on the Feasibility study on NDS/AF (3GPP TR 33.810).



Feature: AMR-WB extension for high audio quality

The objective of the work is to enhance the current AMR-WB codec (catering for wideband speech applications) by introducing new modes to provide consistent quality for audio (speech, music and mixed content), primarily intended for non-conversational services.

The extended codec is targeted for use in packet-switched streaming and messaging services targeting Release 6.

A target is to use similar bit-rates as the AMR-WB codec in order to ensure efficient use of radio resources.



Feature: Support of conversational services in A/Gb mode via the packet- switched (PS) domain

The overall goal is to introduce support for conversational services in the PS domain in A/Gb mode with a minimal impact on existing systems and standards. The current functional split of the protocol architecture between core and radio access network will be maintained.

To achieve this aim, this WI will have to resolve several aspects, such as:•Minimize the transfer delay between the SGSN and the MS •Minimize service interruption due to mobility e.g. introduction of PS handover •Minimize the protocol overhead on the user plane (e.g. optimization of IP header adaptation, modifications to LLC / SNDCP protocol headers) •Optimize radio channel support for conversational QoS (e.g. support of dedicated channels).



Feature: Enhancement of dialled service for CAMEL

“Enhanced CSE capability for dialled services” enables richer CAMEL services based on dialling patterns. This feature is needed for the control of charging for Release 6 CAMEL.

Note that the feature was removed from the Release 5, because the work could not be completed in time for Rel-5.



Feature: Definition of teleservice using Multimedia Broadcast/Multicast Service (MBMS)

Following on development of Stage 1 and 2 specifications that define the MBMS bearer service, there is now the need to define a teleservice that uses such an MBMS bearer. This implies that a limited set of media codecs, formats and transport/application protocols for MBMS need to be specified. Information about typical MBMS applications will be useful to for the design of the UTRAN and GERAN bearers.

This work item covers teleservice requirements and the definition of a set of media codecs, formats and transport/application protocols. The specification work will take into consideration the need to maximize the reuse of existing features of other 3GPP services. The impact of Digital Rights Management (DRM) will be taken into account within the work.



Feature: (U)SIM security reuse by peripheral devices on local interfaces

The possibility of using alternative peripheral devices (e.g. Wireless LAN, Bluetooth) on local interfaces to user equipment leads to an evaluation of the potential new security threats and potentially to specify appropriate security requirements.

The objectives of this work item study are:•To study the feasibility of diverse usage models (e.g., accessing 3GPP system and WLAN simultaneously) including the model with multiple external (wired or wireless) interfaces from a security point of view, and to realize these models without incorporating significant changes to the infrastructure. •To study the impact on current security specifications for 3GPP, especially with regards to key setting procedures, and USIM sequence number synchronization, UICC presence detection/UICC application presence detection issues and termination of the UICC usage etc. •To study any additional user authentication requirements (e.g. PINs) when used over local interfaces like Bluetooth, IR or USB. •To study the impact on having many entities using the same security mechanism and any 3GPP core network elements. •Conduct a threat analysis related to the proposed new functionality.



The current work programme also includes a number of The current work programme also includes a number of feasibility studies, particularly in the radio access feasibility studies, particularly in the radio access network area. The results of these studies will be network area. The results of these studies will be included in later Releases of the system specifications.included in later Releases of the system specifications.




• Foreseen content of 3GPP Release 6Foreseen content of 3GPP Release 6• Identified interactions between 3GPP workIdentified interactions between 3GPP work


>>



So what is the relationship with So what is the relationship with OMA … ?OMA … ?

Some interdependencies between the work of 3GPP and Some interdependencies between the work of 3GPP and OMA have already been identified …OMA have already been identified …



Feature: Speech recognition and speech-enabled services

Forecasts show that speech-driven services may play an important role on the 3G market. People want the ability to access information while on the move and the small portable mobile devices that will be used to access this information needs improved user interfaces using speech input.. A range of multi-modal applications is envisaged, incorporating different modes of input (e.g. speech, keyboard, pen) and speech and visual output.

The objective of this work item is to produce an analysis to understand how different architectures could work and co-exist, and to determine if there is a preferred solution (thus allowing minimization of the number of options needing to be supported by the 3GPP specifications). Any solution, or solutions, must be acceptable to all players (terminal manufacturers, network operators, third-party service providers, speech recognition vendors, etc.). The study will address both services and technologies including the possible locations of the speech recognition function (terminal, network, distributed, ...) and an evaluation of existing codecs and those under development.

OMA is defining multimodal support, though the exact work split is not yet clear.



Feature: Location Services enhancements 2

The objective is to align the 3GPP location services specifications and similar services developed in other fora, and to enhance the network support for user privacy in those services.

Specifically:•Standardization of the Le interface (3GPP TS 23.271), alignment of LCS specifications •Enhanced support for anonymity and user privacy via support for anonymous target mobile users and enhanced codeword functionality •Enable LCS clients to use IMS public user identities (e.g. when a service such as Presence requests ME location information). •Develop the functionality to generate LCS triggering reports when an ME is within, or enters, or leaves, a defined area.

OMA LWG is specifying protocols for the Le, Lr, Lp and Lid interfaces.



Feature: Digital Rights Management (DRM)

Services and capabilities specified by 3GPP allow “content” (data, text, audio, video, etc.) to be delivered by streaming or downloading, and played or stored for future use on the mobile. Delivery methods may include forwarding onward from the device. It is essential to create a solution that will respect the intellectual property rights of the content owners.

The objective is to specify a framework that will support an interoperable, uniform, high-volume market for the distribution of protected content. Expression and enforcement of rights and rules - digital rights management - is an essential component of this distribution capability. In order for protected distribution of content to be acceptable to consumers, it must be transparent and non-intrusive, however security of downloadable and or streaming content must be preserved, i.e. it must not be possible to “play” unauthorized copies.

The work is limited to stage 1 specifications; the stages 2 and 3 work is expected to be performed by The Open Mobile Alliance.

All technical work done in OMA.



Feature: Packet-switched streaming services (Rel-6)

The objective of this Feature is to standardize the components of a mobile multimedia content delivery service, including streaming protocols, media transport protocols and multimedia codecs, endeavouring to harmonize with existing and emerging 3GPP multimedia applications whenever possible.Solutions should be fully backwards-compatibile with the Rel-5 Extended Streaming standards.

This work item will cover:•Support for service adaptation: •Enabling adaptation based on capability exchange, including user preferences. •Support adaptation to varying network conditions. •Adaptation to network capabilities and characteristics (GERAN, UTRAN and WLAN). •Consideration of introduction of new codecs and formats. •Harmonized streaming support for MMS. •Consideration of introduction of a server file format and a file format for progressive download. •Real time monitoring of application level QoS.

Uses OMA DRM.



Feature: Multimedia Messaging Service (MMS) enhancements

A need for further elaboration and new functionality of MMS is identified. Therefore the following items are planned to be included in the expected work on MMS.


MM1 interface specs (stage 3) from OMA.



Feature: Support for subscriber certificates

Digital signatures are the best way to secure mobile commerce, service authorization and accounting. But digital signature by itself is not enough: global support for authorization and charging is required. The simplest way to introduce digital signatures in mobile networks is to make use of infrastructure that already exists.

Thus, the global and secure authorization and charging infrastructure of mobile networks should be used to provide local architecture for digital signatures.Subscriber certificates provide a migration path towards global Public Key Infrastructure (PKI). On the one hand, operators and service providers do not have to wait for a world-wide PKI to benefit from public key technology. Local architecture for digital signatures can be deployed incrementally; an operator can choose to deploy independently of the others. On the other hand, the existence of subscribers and service providers that use digital signatures makes it easier to build global PKI. The concept relies on authenticicated signalling between mobile terminal and serving network and thus has to be standardized. The terminal and the serving network can interact only over standardized interface.


Security issues (SA3) rely on already completed OMA SEC/SCT specifications.



How to track OMA progress at 3GPP?How to track OMA progress at 3GPP?

3GPP has identified the areas of interaction between OMA and 3GPP work. The 3GPP has identified the areas of interaction between OMA and 3GPP work. The next step is to find a consistent way to track the progress of the OMA work at next step is to find a consistent way to track the progress of the OMA work at 3GPP.3GPP.

Currently, there are two different ways in the Work Plan.Currently, there are two different ways in the Work Plan.

Solution 1: the DRM way: one 3GPP working group (SA1 in the example) is the DRM way: one 3GPP working group (SA1 in the example) is responsible of keeping track of the actual progress of OMA. The corresponding responsible of keeping track of the actual progress of OMA. The corresponding MCC Secretary relays progress back to the Work Plan manager.MCC Secretary relays progress back to the Work Plan manager.



How to track OMA progress at 3GPP?How to track OMA progress at 3GPP?(cont)(cont)

Solution 2: the LCS way: there are tasks directly allocated to OMA in the 3GPP the LCS way: there are tasks directly allocated to OMA in the 3GPP Work Plan. The Work Plan manager needs to find a contact person to report on Work Plan. The Work Plan manager needs to find a contact person to report on the actual progress. the actual progress.

Is there a preferred approach? Solution 2 is more accurate (as visible in the Is there a preferred approach? Solution 2 is more accurate (as visible in the example…) because more direct, but a contact person needs to be identified at example…) because more direct, but a contact person needs to be identified at OMA for reporting back to the 3GPP Work Plan manager.OMA for reporting back to the 3GPP Work Plan manager.





and OMA workand OMA work• ConclusionConclusion>>



Ongoing work from previous Ongoing work from previous ReleasesReleases

The preceding slides have outlined the current 3GPP work programme. The preceding slides have outlined the current 3GPP work programme. However, 3GPP is responsible for the maintenance of previous Releases of However, 3GPP is responsible for the maintenance of previous Releases of the system specifications. Work on topics such as:the system specifications. Work on topics such as:

• AT command setAT command set

• SMSSMS

• … …

is occasionally required.is occasionally required.

Unless enhancements are sufficiently important to warrant new a new work Unless enhancements are sufficiently important to warrant new a new work item in their own right, they are grouped under an umbrella item “item in their own right, they are grouped under an umbrella item “small small technical enhancements and improvementstechnical enhancements and improvements” (” (TEITEI). Each Release has such a ). Each Release has such a TEI catch-all work item, but due to its ad hoc nature, it is not shown on the TEI catch-all work item, but due to its ad hoc nature, it is not shown on the work plan.work plan.

Of course, OMA may well propose services which impinge on the features of Of course, OMA may well propose services which impinge on the features of previous Releases, necessitating enhancements in a future Release.previous Releases, necessitating enhancements in a future Release.



Information on previous ReleasesInformation on previous Releases

So now I know what is in the current plans. How do I find out what features So now I know what is in the current plans. How do I find out what features were included in were included in previous 3GPP Releasesprevious 3GPP Releases??

Answer:Answer:

You look at the 3GPP web, where you will find the enhancements for each You look at the 3GPP web, where you will find the enhancements for each new Release.new Release.

http://www.3gpp.org/specs/releases-contents.htmhttp://www.3gpp.org/specs/releases-contents.htm

In addition, an MS Word document describes the content of Release 5 (future In addition, an MS Word document describes the content of Release 5 (future documents will cover other Releases). documents will cover other Releases). It can be found at: It can be found at: http://www.3gpp.org/ftp/Information/WORK_PLAN/MS%20Word%20docs%20describing%20Releases/Rel5_features_v_2003_08_20.zip http://www.3gpp.org/ftp/Information/WORK_PLAN/MS%20Word%20docs%20describing%20Releases/Rel5_features_v_2003_08_20.zip



ConclusionConclusion

•All the current 3GPP activities have been presented to All the current 3GPP activities have been presented to OMA.OMA.

•The areas of interactions between OMA work and 3GPP The areas of interactions between OMA work and 3GPP work have been stressed.work have been stressed.

•There is a need to identify the process by which 3GPP is There is a need to identify the process by which 3GPP is informed of OMA work progress for these areas, so that informed of OMA work progress for these areas, so that 3GPP can take relevant decisions (e.g. foreseen freezing 3GPP can take relevant decisions (e.g. foreseen freezing dates of Releases).dates of Releases).



For more information please visitFor more information please visit

http://www.3gpp.orghttp://www.3gpp.org

Or contact:Or contact:

john.john.meredithmeredith@@etsietsi.org.org for general information for general information

[email protected] for information concerning the Work [email protected] for information concerning the Work Plan

Content of the presentation

Documents

Transcript of Content of the presentation