© 2006 Sprint Nextel WP5D Meeting Results Sprint grants a free, irrevocable license to 3GPP2 and its Organizational Partners to incorporate text or other copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner's name any Organizational Partner's standards publication even though it may include portions of the contribution; and at the Organizational Partner's sole discretion to permit others to reproduce in whole or in part such contributions or the resulting Organizational Partner's standards publication. The contributor must also be willing to grant licenses under such contributor copyrights to third parties on reasonable, non-discriminatory terms and conditions, as appropriate

2 IMT-Advanced Summary  Addendum to Circular Letter for IMT-ADV Issued  announces the availability of further relevant information associated with the IMT-Advanced in [Draft New] Report ITU-R M.[IMT.REST]  All Technical Requirements agreed  Spectrum Requirements agreed  Service Requirements agreed  Evaluation Criteria still not agreed

3 IMT.REST “ Requirements, Evaluation criteria, and Submission Templates ”  Contains Requirements for Services, Spectrum and Technical performance  Contains Evaluation Criteria and Methodology  Contains submission guidelines and Templates  Each candidate technology must fill out a Description Template  Each candidate technology must fill out a Compliance Template for Services, Spectrum and Technical Performance

4 Technical Requirements  Provided in document IMT.TECH  Cell spectral efficiency Test environment **Downlink (b/s/Hz/cell)Uplink (b/s/Hz/cell) Indoor32.25 Microcellular Base coverage urban High speed Peak Spectral Efficiency Downlink 15 bits/s/Hz Uplink 6.75 bits/s/Hz Bandwidth Scalable bandwidth is the ability of the candidate RIT to operate with different bandwidth allocations. This bandwidth may be supported by single or multiple RF carriers The RIT shall support a scalable bandwidth up to and including 40 MHz.

5 Technical Requirements (2)  Control Plane Latency  A transition time (excluding downlink paging delay and wireline network signalling delay) of less than 100 ms shall be achievable from idle state to an active state in such a way that the user plane is established  User Plane Latency  IMT-Advanced systems shall be able to achieve a User Plane Latency of less than 10 ms in unloaded conditions (i.e. single user with single data stream) for small IP packets (e.g. 0 byte payload + IP header) for both downlink and uplink  Mobility  A mobility class is supported if the traffic channel link data rate, normalized by bandwidth, on the uplink, is as shown in the Table below, when the user is moving at the maximum speed in that mobility class in each of the test environments Traffic Channel Link Data Rate (Bits/s/Hz) Speed (km/h) Indoor1.010 Microcellular Base Coverage Urban High Speed

6 Technical Requirements (3)  Handover Handover TypeInterruption Time (ms) Intra-Frequency27.5 Inter-Frequency - within a spectrum band - between spectrum bands VoIP Test environment**Min VoIP capacity (Active users/sector/MHz) Indoor50 Microcellular40 Base coverage urban40 High speed30

7 Services Requirement  Complete within WP5D  Controversy over adding the following sentence in IMT.EVAL  “If the proposal meets the peak spectral efficiency, latency and bandwidth requirements it can be regarded as being capable to meet this service aspect of requirements.”  In which case no need for the Compliance Template for Services as shown below X.YService related minimum capabilities within RIT/SRITEvaluator’s comments X.Y.1Support of a wide range of services Does the proposal support a wide range of services?: If bullets X.Y X.Y.1.8 are marked as "yes" then X.Y.1 is a "yes".  YES /  NO X.Y.1.1Ability to support basic conversational service class Is the proposal able to support basic conversational service class?:  YES /  NO X.Y.1.2Support of rich conversational service class Does the proposal support rich conversational service class?:  YES /  NO X.Y.1.3Support of conversational low delay service class Does the proposal support conversational low delay service class?:  YES /  NO

8 Spectrum Requirements  IMT Bands  MHz  MHz  MHz  MHz  MHz  MHz  MHz Spectrum capability requirements Spectrum bands Is the proposal able to utilize at least one band identified for IMT?:  YES /  NO Specify in which bands the candidate RIT or candidate SRIT can be deployed.

9 Technical Description Template  Technical Description Template describes the characteristics of the candidate Radio Interface Technology (RIT) or Set of RIT (SRIT)  Information to be provided by the candidate RIT or SRIT for each test environment  Needed in order to do evaluations  Template could not be agreed upon at the WP5D meeting  Current Template contains more information than thought necessary for evaluation  Correspondence Group formed to work on Description Template prior to the next WP5D meeting  Member companies of 3GPP2 or SDOs may need to make contribution on this for the next WP5D meeting

10 Evaluation Criteria and Methodology  Evaluation Criteria and Methodology given in document IMT.EVAL  IMT.EVAL still not fully completed  Document still subject to change at the next meeting  Main item of contention is the evaluation of Services  IMT.EVAL is key in deciding how the technical requirements are evaluated  General Agreement on many of the Evaluation Criteria  Number of Test Environments – A RIT or SRIT must meet at least 3 test environments  Number of Antennas – Up to 8 for BS and up to 2 for MS  TIA contribution on Advanced MIMO techniques and Relays not agreed to be added  Channel Model completed

11 Baseline Configuration Parameters (cell spectral efficiency, cell edge user spectral efficiency, control plane latency, user plane latency, mobility, handover interruption time and VoIP capacity) Deployment scenario for the evaluation process Urban macro-cellUrban micro-cellIndoor hotspotRural macro- cell Suburban macro-cell Base Station (BS) antenna height 25 m, above rooftop10 m, below rooftop6 m, mounted on ceiling 35 m, above rooftop Number of BS antenna elements [1] [1] Up to 8 rx Up to 8 tx Up to 8 rx Up to 8 tx Up to 8 rx Up to 8 tx Up to 8 rx Up to 8 tx Up to 8 rx Up to 8 tx Total BS TX power at antenna feedpoint 46dBm for 10MHz, 49dBm for 20MHz 41 dBm for 10MHz, 44 dBm for 20MHz 24dBm for 40 MHz, 21 dBm for 20 MHz 46dBm for 10MHz, 49dBm for 20MHz User Terminal (UT) power class 24dBm 21dBm24dBm UT antenna system (see the footnote) 1 Up to 2 tx Up to 2 rx Up to 2 tx Up to 2 rx Up to 2 tx Up to 2 rx Up to 2 tx Up to 2 rx Up to 2 tx Up to 2 rx Minimum distance between UT and serving cell [2] [2] >= 25 meters>= 10 meters>= 3 meters>= 35 meters Carrier Frequency (CF) for evaluation (representative of IMT bands) 2GHz2.5 GHz3.4 GHz800 MHzSame as Urban macro-cell Outdoor to Indoor building penetration loss N.A.see Annex 1 Table A1- 1 N.A. 20 dB Outdoor to in-car penetration loss 9 dB (LN, σ = 5 dB)N.A. 9 dB (LN, σ = 5 dB) [1] [1] Evaluation group should use the number of antennas specified by proponent in the technology description template if it is not more than the number specified in this table. [2] [2] In the horizontal plane.

12 Configuration Parameters (Peak Spectral Efficiency) Deployment scenario for the evaluation process Urban macro-cellUrban micro-cellIndoor hotspotRural macro- cell Suburban macro- cell Number of BS antenna elements Up to 4 rx Up to 4 tx Up to 4 rx Up to 4 tx Up to 4 rx Up to 4 tx Up to 4 rx Up to 4 tx Up to 4 rx Up to 4 tx UT antenna systemUp to 2 tx Up to 4 rx Up to 2 tx Up to 4 rx Up to 2 tx Up to 4 rx Up to 2 tx Up to 4 rx Up to 2 tx Up to 4 rx

13 Schedule for IMT-Advanced

14 Evaluation Groups  External Evaluation Groups will be set up to evaluate proposals  Independent evaluation groups are requested to register with the ITU-R before the end of 2008  Evaluation group registration forms are available at

15 Workshop on IMT Advanced  Workshop on IMT Advanced to be held in Korea on October 7 th  Purpose of Workshop  to provide common understanding of the process for IMT-Advanced standardization including technical requirements and evaluation guidelines. In particular, it would enable those not directly involved WP5D works to understand IMT.TECH, IMT.EVAL and process better.  to observe current and future development aspects of IMT-Advanced Radio Interface Technology  to facilitate possible proponents for consensus building among the possible candidate IMT- Advanced RITs/Set of RIT  to share IMT-Advanced market and regulatory aspects for the introduction of the IMT-Advance  How WP5D has addressed the needs of developing countries  presentations from regional representatives(ASMG, ATU, APT, CITEL, CTU, CEPT and RCC)  Correspondence Group formed to work out detailed agenda  A tentative agenda has been proposed  RIT proponents will be asked to do a presentation  3GPP2 should consider making proposal at the workshop

16 Tentative Agenda for IMT Advanced Workshop 9:00 – 9:20Registration 9:20 – 9:30Opening Chairman WP5D Session 1 Process and requirements of IMT-Advanced standardization * 20min. presentation, 10min. Q&A Mr. WEE 9:30 – 10:00 10:00 – 10:30 10:30 – 11:00 Process(Circular Letter, Res. ITU-R 57 and IMT.ADV2) Minimum requirements of IMT-Advanced(IMT.TECH) Evaluation guideline [1] (IMT.EVAL) [1] Mr. Yoshino Mr. Grant Mr. Wang 11:00 – 11:30Coffee break Session 2 Possible candidate IMT-Advanced Radio Interface Techniques [2] [2] Mr. Ohlsen [3] [3] 11:30 – 12:00Proponent A 12:00 – 12:30Proponent B 12:30 – 14:00Lunch 14:00 – 14:30Proponent C 14:30 – 15:00Proponent D 15:30 – 16:00Coffee Break Session 3 Needs of Developing countries [4] [4] 16:00 – 18:00 - How WP5D has addressed the needs of developing countries. - Presentations from regional representatives(APT, ASMG, ATU, CITEL, CEPT, CPT, CTU and RCC) Ms.Sanders Regional speakers

17 M.1457 Revision 9  All 6 IMT-2000 technology Radio Interfaces submitted their intention to update to Revision 9  IMT-2000 CDMA MC stated their intention to include a TDD component  TIA asked to provide information on how they would incorporate a TDD component in their update  Question as to whether all SDOs need to agree to have a TDD component as an update and not a new radio interface for CDMA-MC – SDOs need to discuss – SDOs need to provide Letters of Conveyance.  OFDMA TDD WMAN stated their intention to include a FDD component  France commented that the new TDD and FDD components may have to be new Radio Interfaces and not just updates to existing Interfaces  No discussion at this meeting as to whether these will be new Radio Interfaces  Final submittals for Revision 9 not due until 1 st Quarter 2009  It is expected that more discussion will ensue at the next two WP5D meetings

18 M.1580/1581 – Emission Requirements for IMT-2000  It was agreed that M.1580/1 would be finalized at the next WP5D meeting in Octovber  Contributions for updates to M.1580/1 received from 3GPP, 3GPP2 and WF  Updates were included into the working document  No agreement as yet on the scope of M.1580/1  Should contain frequency band specific information of M.1457 parameters to provide an easy access for those administrations that need guidance on “generic unwanted emission characteristics parameters”  Should contain necessary technical parameters in relation to global circulation of terminals  General agreement that ACS values should not be included  General agreement that ACLR is used for sharing studies but one administration stated that they were used for more than just sharing studies  Meeting agreed to Request views from Administrations for the next WP5D Meeting  Regarding the proposed “removal of ACLR from M.1580/81 and to put it in another recommendation (e.g. M.1457 or a new recommendation incorporating material from report M.2039) and in the individual sharing studies”.  On whether there is any other usage of “ACLR” apart from sharing studies  Definition of the parameter “ACLR”  On the need for further/other parameters,  Proposals for the change of the scope of Rec.1580/81