throbber
R1-073240
`
` 1
`
` Opening of the meeting (Day 1: 9.00 AM)
`1.1 Call for IPR
`
`I draw your attention to your obligations under the 3GPP Partner Organizations' IPR policies. Every Individual
`Member organization is obliged to declare to the Partner Organization or Organizations of which it is a member
`any IPR owned by the Individual Member or any other organization which is or is likely to become essential to the
`work of 3GPP.
`
`The attention of the delegates to the meeting of this Technical Specification Group was drawn to the fact that
`3GPP Individual Members have the obligation under the IPR Policies of their respective Organizational
`Partners to inform their respective Organizational Partners of Essential IPRs they become aware of.
`
`The delegates were asked to take note that they were thereby invited:
`
`
`
`
`
`to investigate whether their organization or any other organization owns IPRs which were, or were
`likely to become Essential in respect of the work of 3GPP.
`to notify their respective Organizational Partners of all potential IPRs, e.g., for ETSI, by means of
`the IPR Statement and the Licensing declaration forms (http://webapp.etsi.org/Ipr/).
`
`2 Approval of the agenda
`3 Approval of the minutes from previous meeting
`4 Election of 3GPP RAN WG1 Officials
`Election of the chairman and two vice-chairmen for 3GPP RAN WG1.
`For further details see: http://www.3gpp.org/tb/RAN/RAN1/elections2007/RAN1_election.htm
`5 Liaison statement handling
`6 Maintenance of Release 99 – Release 7
`7 Evolved UTRA and UTRAN
`7.1 Updated Physical Layer Specifications
`Inputs to the draft specifications to be prepared by the editors.
`
`3GPP TSG RAN WG1 Meeting #50
`Athens, Greece, August 20 – 24, 2007
`
`
`Source:
`
`Title:
`
`Document for:
`
`The deadline is 13 August 6.00 PM, CEST
`Tdoc request:
`The deadline is 13 August 9.00 AM, CEST
`Tdoc submission (AI 6):
`Tdoc submission (all other AI): The deadline is 15 August 9.00 AM, CEST
`
`Chairman
`
`Draft Agenda
`
`Decision
`
`APPLE 1049
`
`Page 1 of 3
`
`

`

`7.2 Finalization of TS 36.211
`
`7.2.1 Downlink reference signals
`Summary of the conclusions from the email ad hoc to be prepared by Aris Papasakellariou.
`Main remaining issues are support of both hopping and shifting, detailed sequence design, dedicated
`RS for beamforming.
`
`7.2.2 Uplink reference signals
`Summary of the conclusions from the email ad hoc to be prepared by Aris Papasakellariou.
`Main remaining issues are on SRS (parameter signalling, exact value of parameters) and of DM RS
`(sequence construction, base sequence and hopping pattern signalling, number of SDMA cyclic shifts).
`
`7.2.3 Downlink Control Signalling
`Summary of the status from email discussions on control signalling to be prepared by Stefan Parkvall.
`Main remaining issues are signaling details, PDCCH mapping, coding scheme for MIMO signalling,
`CCE aggregation and blind detection, cell specific interleaving/shift.
`
`7.2.4 Uplink Control Signalling
`Summary of the status from email discussions on control signalling to be prepared by Stefan Parkvall.
`Main remaining issues are CQI/PMI/Rank report, transmission scheme for scheduling request.
`
`7.2.5 Mapping of virtual resource blocks to physical resource blocks
`Main issues are on DL RB mapping (value of Nd, mapping of DVRB onto PRBs, N_DPRB, use of
`remaining RE in BCH subframe), and on UL RB mapping (resource allocation with uplink hopping).
`
`7.2.6 Remaining details on DL MIMO, TX diversity and beamforming
`Remaining details for 36.211 on precoding, codebook, layer mapping etc.
`
`7.2.7 SSC, PSC
`Summary of the conclusions from email ad hoc on SCH to be prepared by Amitava Ghosh.
`Main remaining issue is details on scrambling for SSC.
`
`7.2.8 PBCH
`No major remaining issues.
`
`7.2.9 RACH
`Summary of the conclusions from email ad hoc on RACH to be prepared by Amitava Ghosh.
`Main remaining issues are exact definition of ZC index number, exact PRACH slot configuration, exact
`value of cyclic shift, cyclic shift restriction method for high mobility cells.
`
`7.3 Finalization of TS 36.212
`Summary of the conclusions from the email ad hoc to be prepared by Sadayuki Abeta.
`Main issues are Turbo code rate matching scheme details, segmentation details, channel interleaver,
`constellation rearrangement and HARQ process number, PUCCH channel coding.
`
`7.4 Finalization of TS 36.213
`
`7.4.1 Timing synchronization
`Synchronization primitives, Radio link monitoring, inter-cell synchronisation, transmission timing
`adjustments.
`
`7.4.2 UL/DL Power Control
`Summary of the conclusions from the email ad hoc to be prepared by Jari Lindholm.
`Main remaining issues on PUSCH power control (exact parameter values, absolute/accumulated UE
`specific correction value), on PUCCH power control (detailed coding scheme for PC bits, exact
`
`Page 2 of 3
`
`

`

`parameter values), on SRS (how to set offset value to PUSCH), and on persistent scheduling (how to
`set offset value to PUCCH), description of UE and eNB behaviour in 36.213.
`
`Inter-cell Interference Coordination
`7.4.3
`Need for request/grant based schemes.
`
`7.4.4 RACH timing and preamble sequence selection
`
`7.4.5 UE Procedures for downlink shared channel
`UE Procedures for CQI reporting and MIMO feedback reporting, UE Procedures related to TX
`diversity (UL antenna switching).
`
`7.4.6 UE Procedures for uplink shared channel
`UE procedures for Sounding, UE procedures for ACK/NACK detection.
`
`7.5 Finalization of TS 36.214
`Summary of the conclusions from the email discussion to be prepared by Dirk Gerstenberger.
`Continued discussion on UE measurements. Feasibility, necessity and definitions of eNB L1
`measurements.
`8 Combination of Higher Order Modulation and MIMO
`in HSDPA
`9 Closing of the meeting (Day5: 5.00 PM at the latest)
`
`Page 3 of 3
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket