11.07.2015 Views

UMTS: Alive and Well - 4G Americas

UMTS: Alive and Well - 4G Americas

UMTS: Alive and Well - 4G Americas

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

has defined a work item on Network Improvements for Machine-Type Communication (NIMTC). Thefollowing goals <strong>and</strong> objectives are described in the work item:The goal of this work item is to:• Provide network operators with lower operational costs when offering machine-typecommunication services• Reduce the impact <strong>and</strong> effort of h<strong>and</strong>ling large machine-type communication groups• Optimize network operations to minimize impact on device battery power usage• Stimulate new machine-type communication applications by enabling operators to offer servicestailored to machine-type communication requirementsThe objectives of this work item include:• Identify <strong>and</strong> specify general requirements for machine-type communications• Identify service aspects where network improvements (compared to the current H2H orientedservices) are needed to cater for the specific nature of machine-type communications• Specify machine-type communication requirements for these service aspects where networkimprovements are needed for machine-type communication• Address system architecture impacts to support machine-type communication scenarios <strong>and</strong>applicationsA RAN study item to investigate the air interface enhancements for the benefit of M2M communicationhas also been recently approved. The study will be initiated in early 2010.7.8.7.2 FIXED MOBILE CONVERGENCE ENHANCEMENTThe Fixed Mobile Convergence (FMC) scenario in 3GPP is part of the Evolved Packet System defined by3GPP TS 23.402 where it is specified how a non-3GPP system can be connected to a 3GPP EPCnetwork. The interconnection of a Non-3GPP system is based on two scenarios based on whether theNon-3GPP network is considered a Trusted access network or an Untrusted access network. In 3GPPspecifications, the Non-3GPP system can be any technology not defined by 3GPP, such as WLAN,WiMAX, 3GPP2 <strong>and</strong> xDSL. However in some cases, the access characteristics are taken into account,while in other cases it is assumed that access network will support some 3GPP specific features. Asimple example is represented by APN <strong>and</strong> PCO. 3GPP assumes that if supported then the UE has thesame behavior in 3GPP access <strong>and</strong> in non-3GPP access, otherwise the UE cannot establish a PDNconnection from Non-3GPP system, so the user cannot obtain the same services form both networks.In 3GPP, there already is an overall requirement to support fixed accesses (3GPP TS 22.278).Implementation of this high level requirement is likely to uncover additional detailed requirements tosupport the technology <strong>and</strong> business models used by fixed access providers. Parallel work based on theoriginal 3GPP FMC use case as well as additional use cases for interworking with both 3GPP accesses<strong>and</strong> 3GPP core network is underway in the Broadb<strong>and</strong> Forum (BBF). Other new features in 3GPP suchas H(e)NBs, Local IP access (LIPA) to residential/corporate local networks; Selected IP traffic offload(SIPTO) for H(e)NBs; IP Flow Mobility <strong>and</strong> seamless WLAN offload (IFOM); <strong>and</strong> Inter-UE Transfer (IUT)may have requirements for interworking with fixed broadb<strong>and</strong> accesses as well. Nonetheless, a specific3GPP work item has been defined to provide detailed service requirements for supporting interworkingbetween the 3GPP EPS <strong>and</strong> the fixed broadb<strong>and</strong> accesses as defined by BBF.www.3G<strong>Americas</strong>.org February 2010 Page 112

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!