160 likes | 272 Views
WP5D Meeting Results 2008-06. 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
E N D
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 not yet agreed • Evaluation Criteria still not agreed
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
Technical Requirements • Provided in document IMT.TECH • Cell spectral efficiency • 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.
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
Technical Requirements (3) • Handover VoIP
Services Requirement • Not yet complete within WP5D • Controversy over adding the following sentence • “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
Spectrum Requirements • IMT Bands • 450-470 MHz • 698-960 MHz • 1 710-2 025 MHz • 2 110-2 200 MHz • 2 300-2 400 MHz • 2 500-2 690 MHz • 3 400-3 600 MHz
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 • 3GPP2, and/or member companies may need to make contribution on this for the next WP5D meeting
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
Baseline Configuration Parameters(cell spectral efficiency, cell edge user spectral efficiency, control plane latency, user plane latency, mobility, handover interruption time and VoIP capacity) [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]In the horizontal plane.
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 http://www.itu.int/ITU-R/go/rsg5-imt-advanced
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 • 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 1st Quarter 2009 • It is expected that more discussion will ensue at the next two WP5D meetings
M.1580/1581 – Emission Requirements for IMT-2000 • It was agreed that M.1580/1 would be finalized at the next WP5D meeting in September • 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