throbber

`
`
`
`
`
`
`
`
`
`
`
`
`
`R2-061152
`
` (Draft 0) minutes of the RAN1-RAN2 joint meeting, 29th March 2006
` (during RAN1-44bis and RAN2-52, Athens, Greece)
`Approval
`3GPP support team
`
`
`
`(TSG-RAN WG2 53 meeting
`08-12 May, Shanghai, China)
`
`
`
`
`
`Title:
`
`Document for:
` Source:
`
`
`
`
`
`
`
`
`
`
`30th March 2006
`Claude Arzelier
`ETSI Mobile Competence Centre
`F-06921 Sophia Antipolis Cedex
`Tel: +33 4 92 94 42 61
`Email: Claude.Arzelier@etsi.org
`
`
`
`Intellectual Ventures II LLC Ex. 2002
`Ericsson Inc. v. Intellectual Ventures
`IPR2018-01380
`
`

`

`Draft Report of the RAN1-RAN2 LTE Joint session (Athens, 29th March 2006)
`
` 1
`
`Opening of the meeting ............................................................................................................................ 3
`
`Call for IPR ............................................................................................................................................................ 3
`1.1
`Approval of the agenda ............................................................................................................................ 3
`2
`Aspects to be discussed (during the joint meeting) .................................................................................. 3
`3
`Paging/Broadcast Control Information ................................................................................................................. 4
`3.1
`Random Access ...................................................................................................................................................... 8
`3.2
`TrCH multiplexing ............................................................................................................................................... 10
`3.3
`HARQ operation (Sync/Async, variable TTI, etc...) .......................................................................................... 11
`3.4
`Control signalling messages ................................................................................................................................ 13
`3.5
`L1 mesurements for Mobility (cell re-selection and handover) ......................................................................... 14
`3.6
`Physical layer model ............................................................................................................................................ 14
`3.7
`Other ..................................................................................................................................................................... 15
`3.8
`Liaisons and outputs to other groups ...................................................................................................... 16
`4
`Any other business ................................................................................................................................. 16
`5
`Closing of the meeting ........................................................................................................................... 16
`6
`Annex A: List of delegates (attendees) ......................................................................................................... 16
`Annex B: List of documents ......................................................................................................................... 16
`
`
`2
`
`

`

`Draft Report of the RAN1-RAN2 LTE joint session (Athens, 29th March 2006)
`
`1
`
`Opening of the meeting
`
`Call for IPR
`
`1.1
`
`The Chairmen (Dirk Gerstenberger from Ericsson and Denis Fauconnier from Nortel Networks) made the following IPR call:
`
`
`The attention of the delegates of this Working 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 hereby 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 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
`
`
`
` 3
`
`NOTE: IPRs may be declared to the Director-General or Chairman of the SDO, but not to the RAN WG Chairmen.
`
`
`
`Approval of the agenda
`
`WG Chairmen
`
`Agenda of the RAN1-RAN2 joint session
`R2-060816
`The Chairmen proposed the agenda for the meeting.
`Decision: The agenda was approved.
`
`
`
`Aspects to be discussed (during the joint meeting)
`
`
`
`3
`
`

`

`Draft Report of the RAN1-RAN2 LTE joint session (Athens, 29th March 2006)
`3.1
`Paging/Broadcast Control Information
`
`
`
`RAN1 Status for Joint Meeting
`R2-061072
`This document was presented by the RAN WG1 Chairman.
`Discussion:
`Decision: The document was noted.
`
`
`RAN1 Chairman
`
`RAN2 Chairman
`
`RAN2 Chairman summary (Broadcast/Paging) (RAN2 Status)
`R2-061073
`This document was presented by the RAN WG2 Chairman.
`Discussion:
`It was clarified (by the presenter) that the "wake-up" procedure may be the same than the paging (with regards to the initial precedure, not to the messages).
`However, details have not been discussed.
`It was clarified that for the monitoring of the scheduler, there may be different DRX periods. For the long DRX periods, uplink synchronisation may not be
`kept (to allow low battery consumption).
`Decision: The document was noted.
`
`
`
`NTT DoCoMo- Fujitsu, Mitsubishi Electric,
`NEC, Sharp, Toshiba Corporation
`Broadcast Channel Structure for E-UTRA Downlink
`R2-060836
`This document was presented by Kenichi Higuchi from NTT DoCoMo.
`Discussion:
`It was clarified that the same information bit was assumed between the 5 MHz and 1.25 MHz transmission. The total transmission power is the same
`between the two cases.
`It was clarified that the BCCH bit rate is still to be decided.
`It was clarified that interferences from other cells was not assumed in the simulations.
`It was clarified that re-use patterns were not excluded.
`It was highlighted that by comparing figures 1a with 3a, the gain (from 1 to 2 transmissions) appears to be 2 dB.
`Decision: The document was noted.
`
`
`
`BCH transport channel
`R2-060864
`This document was presented by Mr. Erik Dahlman from Ericsson.
`Discussion:
`It was clarified that the intention was to have a predetermined transport format ("low fixed data rate" for the BCH, re-using the Rel-6 terminology).
`It was clarified that one idea here was that less critical information (second set of information) could be sent in a dedicated way rather than broadcast
`continuously. Finding a goodd trade-off would be important : A capacity cost versus bit rate figure (for the BCH) would be useful.
`
`Ericsson
`
`4
`
`

`

`Draft Report of the RAN1-RAN2 LTE joint session (Athens, 29th March 2006)
`There is a need to assess if having quick feedback from the neighbour cells would be useful (introducing this this may also impact the scheduling).
`It was clarified that (for example) the PMN Id would be sent in macro diversity.
`Decision: The document was noted.
`
`
`
`Flexible rate transmission of BCCH
`R2-060887
`This document was presented by Dr. Konstantinos Dimou from Panasonic.
`Discussion:
`It was clarified that the fixed rate part would be sent on the fixed part broadcast channel. All information may be received by all UEs on downlink shared
`channels.
`Decision: The document was noted.
`
`
`Panasonic
`
`Motorola
`Paging/Broadcast Control
`R2-060942
`This document was presented by Mr Ravi Kuchibhotla from Motorola (focusing on the bradcast part).
`Discussion:
`Question was raised if the whole part of the subframe would be used.
`Decision: The document was noted.
`
`
`
`Qualcomm
`Europe
`
`Considerations on BCH and 20 MHz system BW
`R2-060903
`This document was presented by Mr. Patrick Fischer from LG Electronics.
`
`LG Electronics
`
`5
`
`Broadcast Control Information
`R2-060995
`This document was presented by Mr Juan Montojo from Qualcomm
`Discussion:
`It was commented that the distinction (of information) should be more on static versus semi static, rather than on system specific versus cell specific. The
`former already exists today (by using different value tags).
`Decision: The document was noted.
`
`
`Samsung
`
`Principles of scalable bandwidth scenarios
`R2-061001
`This document was presented by Mr. Jeong, Kyeong in from Samsung.
`Discussion:
`It was clarified (by the presenter) that there may be a need of two BCHs (duplicate BCH transmissions), because of MBMS. It was replied that this is in fact
`a BCH in two cells.
`It was commented that another solution would be to deliver MBMS in less than 10 MHz.
`Decision: The document was noted.
`
`
`

`

`
`
`Draft Report of the RAN1-RAN2 LTE joint session (Athens, 29th March 2006)
`Discussion:
`It was clarified that in the information split, information would be split in two code blocks.
`All UEs in active mode would have to read the BCH.
`Decision: The document was noted.
`
`Summary on Broadcast proposals and decisions (RAN WG2 Chairman) (new document, after discussions):
`R2-061074
`Broadcast Summary
`RAN2 Chairman
`This document was presented by the RAN2 Chairman.
`Discussion:
`It was clarified that MCH (Multicast Channel) is similar to the MCCH, a logical channel carried on the FACH transport channel and introduced in the Rel-6
`for MBMS.
`Decision:
`RAN WG2 to study ways to reduce BCH load based on BCCH content delivery mechanism.
`RAN WG1 to provide a capacity cost versus bit rate figure.
`
`
`
`NTT DoCoMo, Fujitsu, Mitsubishi Electric,
`NEC, Toshiba Corporation
`Paging Channel Structure for E-UTRA Downlink
`R2-060837
`This document was presented by Kenichi Higuchi from NTT DoCoMo.
`Discussion:
`It was clarified that independant paging indicators were proposed in order to achieve also soft combining.
`Question on whether different SFNs would be used between paging and broadcast. It was clarified that soft combining for paging channels is limited to cells
`within the same Node-B.
`Decision: The document was noted.
`
`
`Philips
`
`Evolved Paging for LTE
`R2-060849
`This document was presented by Mr Paul Bucknell from Philips.
`Discussion:
`It was clarified that the paging would be for mobiles in idle mode. Question on the associated increased resource load (only one mobile would benefit from
`it).
`Question on when the UE would acquire the uplink sync. Answer that the UE would perform a RACH as normally.
`Decision: The document was noted.
`
`
`PCH transport channel
`R2-060865
`This document was presented by Mr. Erik Dahlman from Ericsson.
`Discussion:
`
`Ericsson
`
`6
`
`

`

`Draft Report of the RAN1-RAN2 LTE joint session (Athens, 29th March 2006)
`It was clarified that downlink shared channels are similar to e.g. HS-DSCH, or HS-SCCH.
`Decision: The document was noted.
`
`
`Motorola
`Paging/Broadcast Control
`R2-060942
`This document was presented by Mr Ravi Kuchibhotla from Motorola (focusing on the paging part).
`Discussion:
`Last bullet point of option 1 should be ignored following the discussions.
`Decision: The document was noted.
`
`
`Qualcomm
`Europe
`
`Paging Procedure
`R2-060994
`This document was presented by Mr Juan Montojo from Qualcomm
`Discussion:
`It was clarified that this concept is a concept of indicator that does not include ressource assignment.
`It was commented that the chosen identity should still not conflict with the identity chosen for the HS-SCCH.
`Decision: The document was noted.
`
`
`LG Electronics
`Inc.
`
`Discusion on LTE Paging and DRX
`R2-061014
`This document was presented by (...) from LG Electronics
`Discussion:
`It was reminded that the PICH was needed in WCDMA because the paging was long. But is it needed if it is shorter ? Answer that there may still be gains
`linked with decoding simplicity.
`It was clarified that long (respectively: short) identities could be used for idle mode (respectively: active) UEs.
`Decision: The document was noted.
`
`
`Proposals/Way forward for Paging: See R2-061075 (new document, after discussions):
`
`R2-061075
`Paging summary
`
`Way forward (taken from R2-061075):
`PCH is a separate transport channel:
`
`- Used for idle mode.
`RAN2 to define procedure/message.
`RAN1 to study PCH design, Paging Indicator need, etc..:
`
`- Maximise commonalities in PHY layer with DL-SCH operation i.e. RRC IDLE and RRC CONNECTED.
`
`
`RAN2 Chairman
`
`7
`
`

`

`Draft Report of the RAN1-RAN2 LTE joint session (Athens, 29th March 2006)
`
`
`Cell code allocation and neighbour list broadcasting
`R2-060838
`The document was not presented during the meeting.
`
`Random Access
`3.2
`RAN1 Chairman
`R2-061072
`RAN1 Status for Joint Meeting
`This document was presented by the RAN WG1 Chairman (focusing on the RACH part, e.g. slide 3).
`Discussion:
`Decision: The document was noted.
`
`
`NTT DoCoMo
`
`Nokia
`
`RACH Content
`R2-060821
`This document was presented by Mr. Benoist Sébire from Nokia.
`Discussion:
`It was commented that shorter random accesss would also lead to less collisions.
`It was clarified that the 30 bits would be associated with 2 ms.
`Decision: The document was noted.
`
`General comments:
`Approach 1 from R1-060885 is a "one step approach". Approach 2 is a "two steps approach".
`It was reminded that the longer the random access, the more seldom it can be sent.
`What is the bandwidth associated with the Async Access burst delay figures (e.g. 0.5 ms, 2 ms) ? It was clarified that this was based on link budget and
`hence independent on the bandwidth.
`
`
`Way forward on the RACH (work split between RAN1 and RAN2):
`(See R2-061076 (new document), that also includes a summary of proposals/figures).
`RAN2 to study content of the first message (including Id), and one versus two step access.
`RAN2 to study how to make scheduling request (scheduled/allocated access versus random request).
`RAN1 to study signatures/sequences.
`RAN1 to look at collision probability in random access case.
`RAN1 to study best way/cost to keep L1 sync:
`
`- At which point should we leave the mobile go to async ?
`RAN1 to confirm message size.
`
`
`
`8
`
`

`

`Draft Report of the RAN1-RAN2 LTE joint session (Athens, 29th March 2006)
`R2-060832
`Prioritizing Non-synchronized Random Access in E-UTRA Uplink
`The document was not presented during the meeting.
`
`
`Random Access for LTE
`R2-060850
`The document was not presented during the meeting.
`
`
`Random Access usage for RRC state transitions and mobility support
`R2-060852
`The document was revised before presentation into R2-061071:
`
`
`
`Random Access usage for RRC state transitions and mobility support
`R2-061071
`The document was not presented during the meeting.
`
`
`Random Access procedures for LTE
`R2-060866
`The document was not presented during the meeting.
`
`
`Text Proposal on Random Access for TR 25.813
`R2-060867
`The document was not presented during the meeting.
`
`
`RACH message performance
`R2-060873
`The document was not presented during the meeting.
`
`
`LTE Random Access Use Cases
`R2-060890
`The document was not presented during the meeting.
`
`
`Access procedure for TDD
`R2-060905
`The document was not presented during the meeting.
`
`
`User ID Assignment during Initial Access
`R2-060913
`The document was not presented during the meeting.
`
`
`Access Procedures
`R2-060996
`The document was not presented during the meeting.
`
`
`Resource Request in Synchronized Case
`R2-061018
`The document was not presented during the meeting.
`
`9
`
`ITRI
`
`Philips
`
`Texas
`Instruments
`
`Texas
`Instruments
`
`Ericsson
`
`Ericsson
`
`Nortel
`
`LG Electronics
`
`CATT- RITT
`
`IPWireless
`
`Qualcomm
`Europe
`
`LG Electronics
`
`

`

`Draft Report of the RAN1-RAN2 LTE joint session (Athens, 29th March 2006)
`
`
`UL timing sync procedure
`R2-061006
`The document was not presented during the meeting.
`
`
`TrCH multiplexing
`
`Random Access Channel Structure for E-UTRA Uplink (=R1-060786)
`R2-061064
`The document was not presented during the meeting.
`
`3.3
`
`
`Samsung
`
`NTT DoCoMo
`
`Samsung
`
`Motorola
`
`Qualcomm
`Europe
`
`Need for mux3 and mux4 ?
`R2-060926
`This document was presented by Mr. Gert-Jan van Lieshout from Samsung.
`Discussion:
`Decision: The document was noted.
`
`
`Transport Channel Multiplexing
`R2-060943
`This document was presented by Ravi Kuchibhotla from Motorola.
`Discussion:
`It was clarified that slide 11 (transport channel multiplexing) was more applicable to the downlink. It was clarified that there are independent information for
`the two transport channels: the resources are not shared.
`In slide 7, it was clarified that a transport block may be mapped to one group of resource blocks.
`Decision: The document was noted.
`
`
`LTE TrCH Multiplexing
`R2-060997
`This document was presented by Etienne Chaponniere from Qualcomm.
`Discussion:
`Decision: The document was noted.
`
`
`Transport Channel Multiplexing and Mapping of Transport Channels to Physical
`Channels
`R2-060851
`This document was presented by Mr Paul Bucknell from Philips.
`Discussion:
`It was clarified that the proposal was primarily intended for the downlink.
`Question was raised on how could this be applicable to the uplink. Resources are not independently accessible.
`It was clarified that this could be applicable to the uplink, but mapped to the same resources.
`
`Philips
`
`10
`
`

`

`Draft Report of the RAN1-RAN2 LTE joint session (Athens, 29th March 2006)
`Decision: The document was noted.
`
`General comment/question:
`What is the maximum TTI assumed ? (especially in the uplink): 2 ms ? For longer TTIs, additional procedures may be needed (e.g. flush the buffer).
`
`
`See the L1 Multiplexing summary/outcome in R2-061077.
`
`
`
`Channel Coding Structure for LTE downlink
`R2-060902
`The document was not presented during the meeting.
`
`
`R2-060839 Multiplexing structure
`The document was not presented during the meeting.
`
`
`Panasonic
`
`NTT DoCoMo
`
`Orange, France
`Telecom
`
`CATT
`
`CATT
`
`Nokia
`
`Transport channel for MBMS support
`R2-060847
`The document was not presented during the meeting.
`
`
`
`
`HARQ operation (Sync/Async, variable TTI, etc...)
`
`R2-060985 MAC multiplexing and scheduling
`This document was revised before presentation into R2-061055:
`R2-061055 MAC multiplexing and scheduling
`The document was not presented during the meeting.
`
`3.4
`
`
`HARQ Operation for E-UTRAN
`R2-060822
`This document was presented by Mr. Benoist Sébire from Nokia.
`Discussion:
`Decision: The document was noted.
`
`
`NTT DoCoMo, Fujitsu, Mitsubishi Electric,
`NEC, Sharp, Toshiba Corporation
`Hybrid ARQ Scheme for E-UTRA Downlink
`R2-060840
`This document was presented by Mr. Kenichi Higuchi from NTT DoCoMo.
`Discussion:
`
`11
`
`

`

`Draft Report of the RAN1-RAN2 LTE joint session (Athens, 29th March 2006)
`It was clarified that the removal of the user Id field may change the format of the signalling.
`Decision: The document was noted.
`
`
`Ericsson
`
`Synchronous vs. Asynchronous HARQ
`R2-060869
`This document was presented by Mr. Henrik Enbuske from Ericsson.
`Discussion:
`There is a typo of 3 bits in the table.
`Question was raised if the impact on synchronous HARQ operation had been assessed (TTM/FDM).
`Decision: The document was noted.
`
`
`Siemens
`
`HARQ operation
`R2-060916
`This document was presented by Mr. Burghard Unteregger from Siemens.
`Discussion:
`It was clarified that this was proposed for the downlink only. The TTI size is however for both the uplink and downlink.
`Decision: The document was noted.
`
`
`Motorola
`
`HARQ Operation
`R2-060944
`This document was presented by Mr Ravi Kuchibhotla from Motorola.
`Discussion:
`Decision: The document was noted.
`
`
`HARQ operation
`R2-061000
`This document was presented by Juho Lee from Samsung.
`Discussion:
`It was clarified that this scheme was proposed for both the uplink and the downlink.
`Decision: The document was noted.
`
`
`See the HARQ conclusions (e.g. Sync versus Async) (new document following discussions), in R2-061078.
`
`
`
`Samsung
`
`Ericsson
`
`Increased TTI Length
`R2-060868
`The document was not presented during the meeting.
`
`
`Text proposal to TR25.814 on synchronous/asynchronous hybrid ARQ
`R2-060870
`The document was not presented during the meeting.
`
`Ericsson
`
`12
`
`

`

`Draft Report of the RAN1-RAN2 LTE joint session (Athens, 29th March 2006)
`
`
`Physical Layer Processing of Large Transport Blocks
`R2-060876
`The document was not presented during the meeting.
`
`
`HARQ Operation
`R2-060998
`The document was not presented during the meeting.
`
`3.5
`
`
`Control signalling messages
`
`RAN1 Status for Joint Meeting
`R2-061072
`Slides 9, 10 and 11 from this document were presented by the RAN WG1 Chairman.
`Discussion:
`For the uplink signalling, question was raised on why no headroom had been considered.
`Decision: The document was noted. This will be studied in RAN WG2.
`
`
`
`E-UTRA Uplink Control Signaling
`R2-060853
`The document was not presented during the meeting.
`
`
`E-UTRA Downlink Control Signaling
`R2-060854
`The document was not presented during the meeting.
`
`
`Uplink TFC selection in E-UTRA
`R2-060871
`The document was not presented during the meeting.
`
`
`R2-060919 OFDM Downlink Signalling
`The document was not presented during the meeting.
`
`
`Control Signaling
`R2-060945
`The document was not presented during the meeting.
`
`
`PCH mapping and Paging control
`R2-060988
`The document was not presented during the meeting.
`
`
`13
`
`HUAWEI
`
`Qualcomm
`Europe
`
`RAN1 Chairman
`
`Intel
`
`Intel
`
`Ericsson
`
`Alcatel
`
`Motorola
`
`CATT
`
`

`

`Draft Report of the RAN1-RAN2 LTE joint session (Athens, 29th March 2006)
`
`Control Signaling Messages
`R2-060999
`The document was not presented during the meeting.
`
`3.6
`
`
`L1 mesurements for Mobility (cell re-selection and handover)
`
`Clarifications on different UE measurement types
`R2-060823
`The document was not presented during the meeting.
`
`
`L1 UE measurement to support intra E-UTRA mobility
`R2-060834
`The document was not presented during the meeting.
`
`
`UE Measurement for Dynamic Camped Frequency Allocation
`R2-060835
`The document was not presented during the meeting.
`
`
`Inter-frequency/RAT Measurement Gap Control
`R2-060841
`The document was not presented during the meeting.
`
`
`Scheduling Scheme for Inter-frequency/RAT Measurements
`R2-060986
`The document was not presented during the meeting.
`
`
`Scheduling of measurements in LTE
`R2-060987
`The document was not presented during the meeting.
`
`
`A generic association procedure to improve handover process
`R2-060874
`The document was not presented during the meeting.
`
`3.7
`
`
`Physical layer model
`
`Functions of the Physical Layer
`R2-060824
`The document was not presented during the meeting.
`
`
`R2-060842 Mappings between Transport Channels and Physical
`
`Qualcomm
`Europe
`
`Nokia
`
`NEC Group
`
`NEC Group
`
`NTT DoCoMo
`
`CATT- RITT
`
`QUALCOMM
`Europe
`
`ITRI
`
`Nokia
`
`NTT DoCoMo, Fujitsu, Mitsubishi
`14
`
`

`

`Draft Report of the RAN1-RAN2 LTE joint session (Athens, 29th March 2006)
`Channels for E-UTRA Uplink
`
`The document was not presented during the meeting.
`
`
`E-UTRA Physical Layer Model
`R2-060872
`The document was not presented during the meeting.
`
`
`PHY Layer Models
`R2-060946
`The document was not presented during the meeting.
`
`
`LTE Physical Layer Model
`R2-061038
`The document was not presented during the meeting.
`
`3.8
`
`
`Other
`
`Link adaption for EMBMS
`R2-060955
`The document was not presented during the meeting.
`
`
`R2-060957 Modelling of the LTE RRC Active state
`The document was not presented during the meeting.
`
`
`R2-060958 MBMS Radio Link Design for LTE
`The document was not presented during the meeting.
`
`
`E-MBMS Structure
`R2-060993
`The document was not presented during the meeting.
`
`
`Cell switching in LTE_Active state
`R2-061036
`The document was not presented during the meeting.
`
`
`Electric, NEC, Sharp, Toshiba
`Corporation
`
`Ericsson
`
`Motorola
`
`Qualcomm
`Europe
`
`Motorola
`
`Vodafone Group
`PLC
`
`Vodafone Group
`PLC
`
`Qualcomm
`Europe S.A.R.L.
`
`Qualcomm
`Europe
`
`15
`
`

`

`Draft Report of the RAN1-RAN2 LTE joint session (Athens, 29th March 2006)
`4
`Liaisons and outputs to other groups
`There was no input under this agenda item.
`
`Any other business
`5
`There was no input under this agenda item.
`
`Closing of the meeting
`6
`(There was no input under this agenda item).
`
`List of delegates (attendees)
`Annex A:
`See the list of delegates from RAN1-44bis and RAN2-52.
`
`
`List of documents
`Annex B:
`(Ordered per agenda item).
`
`
`Doc. Name
`R2-060816
`
`Title
`Agenda of the RAN1-RAN2 joint session
`
`R2-060836
`
`Broadcast Channel Structure for E-UTRA Downlink
`
`R2-060837
`R2-060838
`R2-060849
`R2-060864
`R2-060865
`
`Paging Channel Structure for E-UTRA Downlink
`Cell code allocation and neighbour list broadcasting
`Evolved Paging for LTE
`BCH transport channel
`PCH transport channel
`
`16
`
`Source
`WG Chairmen
`NTT DoCoMo-
`Fujitsu, Mitsubishi
`Electric, NEC,
`Sharp, Toshiba
`Corporation
`NTT DoCoMo,
`Fujitsu, Mitsubishi
`Electric, NEC,
`Toshiba
`Corporation
`NTT DoCoMo
`Philips
`Ericsson
`Ericsson
`
`Allocations
`Joint02: Approval of the agenda
`
`Note
`
`
`Joint03.1: Paging/Broadcast Control Information
`
`Joint03.1: Paging/Broadcast Control Information
`Joint03.1: Paging/Broadcast Control Information
`Joint03.1: Paging/Broadcast Control Information
`Joint03.1: Paging/Broadcast Control Information
`Joint03.1: Paging/Broadcast Control Information
`
`
`
`
`
`
`
`
`
`

`

`Draft Report of the RAN1-RAN2 LTE joint session (Athens, 29th March 2006)
`R2-060942
`Paging/Broadcast Control
`R2-060994
`Paging Procedure
`R2-060995
`Broadcast Control Information
`R2-061001
`Principles of scalable bandwidth scenarios
`R2-061014
`Disucssion on LTE Paging and DRX
`R2-061029
`Discussion on LTE Paging and DRX
`R2-061072
`RAN1 Status for Joint Meeting
`R2-061073
`RAN2 Chairman summary (Broadcast/Paging) (RAN2 Status)
`R2-061074
`Broadcast Summary
`R2-061075
`Paging Summary
`
`Flexible rate transmission of BCCH
`R2-060887
`RACH Content
`R2-060821
`Prioritizing Non-synchronized Random Access in E-UTRA Uplink
`R2-060832
`Random Access for LTE
`R2-060850
`Random Access usage for RRC state transitions and mobility support
`R2-060852
`Random Access procedures for LTE
`R2-060866
`Text Proposal on Random Access for TR 25.813
`R2-060867
`LTE Random Access Use Cases
`R2-060890
`Considerations on BCH and 20 MHz system BW
`R2-060903
`Access procedure for TDD
`R2-060905
`User ID Assignment during Initial Access
`R2-060913
`Access Procedures
`R2-060996
`UL timing sync procedure
`R2-061006
`Resource Request in Synchronized Case
`R2-061018
`Resource Request in synchronized case
`R2-061033
`Random Access Channel Structure for E-UTRA Uplink (=R1-060786)
`R2-061064
`Random Access usage for RRC state transitions and mobility support
`R2-061071
`RACH Summary
`R2-061076
`RACH message performance
`R2-060873
`R2-060839 Multiplexing structure
`
`R2-060847
`
`R2-060851
`R2-060902
`R2-060920
`
`Transport channel for MBMS support
`Transport Channel Multiplexing and Mapping of Transport Channels to
`Physical Channels
`Channel Coding Structure for LTE downlink
`Need for Mux3 and Mux4 ?
`
`17
`
`Motorola
`Qualcomm Europe
`Qualcomm Europe
`Samsung
`LG Electronics Inc.
`LG Electronics
`RAN1 Chairman
`RAN2 Chairman
`RAN2 Chairman
`RAN2 Chairman
`
`Panasonic
`Nokia
`ITRI
`Philips
`Texas Instruments
`Ericsson
`Ericsson
`LG Electronics
`LG Electronics
`CATT- RITT
`IPWireless
`Qualcomm Europe
`Samsung
`LG Electronics Inc.
`LG Electronics
`NTT DoCoMo
`Texas Instruments
`RAN2 Chairman
`Nortel
`NTT DoCoMo
`Orange, France
`Telecom
`
`Philips
`Panasonic
`Samsung
`
`Joint03.1: Paging/Broadcast Control Information
`Joint03.1: Paging/Broadcast Control Information
`Joint03.1: Paging/Broadcast Control Information
`Joint03.1: Paging/Broadcast Control Information
`Joint03.1: Paging/Broadcast Control Information
`Joint03.1: Paging/Broadcast Control Information
`Joint03.1: Paging/Broadcast Control Information
`Joint03.1: Paging/Broadcast Control Information
`Joint03.1: Paging/Broadcast Control Information
`Joint03.1: Paging/Broadcast Control Information
`Joint03.1: Paging/Broadcast Control Information
`- 06.1: RRC and MAC protocol States and State
`transitions- split between MAC and RRC
`functions
`Joint03.2: Random Access
`Joint03.2: Random Access
`Joint03.2: Random Access
`Joint03.2: Random Access
`Joint03.2: Random Access
`Joint03.2: Random Access
`Joint03.2: Random Access
`Joint03.2: Random Access
`Joint03.2: Random Access
`Joint03.2: Random Access
`Joint03.2: Random Access
`Joint03.2: Random Access
`Joint03.2: Random Access
`Joint03.2: Random Access
`Joint03.2: Random Access
`Joint03.2: Random Access
`Joint03.2: Random Access
`Joint03.2: Random Access
`Joint03.3: TrCH multiplexing
`
`Joint03.3: TrCH multiplexing
`
`Joint03.3: TrCH multiplexing
`Joint03.3: TrCH multiplexing
`Joint03.3: TrCH multiplexing
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Draft Report of the RAN1-RAN2 LTE joint session (Athens, 29th March 2006)
`R2-060922
`Need for Mux3 and Mux4 ?
`R2-060924
`Need for Mux3 and Mux4 ?
`R2-060926
`Need for mux3 and mux4 ?
`R2-060943
`Transport Channel Multiplexing
`
`R2-060985 MAC multiplexing and scheduling
`R2-060997
`LTE TrCH Multiplexing
`
`R2-061055 MAC multiplexing and scheduling
`R2-061077
`L1 Multiplexing Summary
`
`R2-060822
`
`HARQ Operation for E-UTRAN
`
`R2-060840
`
`Hybrid ARQ Scheme for E-UTRA Downlink
`
`R2-060868
`
`Increased TTI Length
`
`R2-060869
`
`Synchronous vs. Asynchronous HARQ
`
`R2-060870
`
`Text proposal to TR25.814 on synchronous/asynchronous hybrid ARQ
`
`R2-060876
`
`Physical Layer Processing of Large Transport Blocks
`
`R2-060916
`
`HARQ operation
`
`R2-060944
`
`HARQ Operation
`
`R2-060998
`
`HARQ Operation
`
`R2-061000
`
`HARQ operation
`
`R2-061078
`
`HARQ Conclusions
`
`R2-060853
`
`E-UTRA Uplink Control Signaling
`
`R2-060854
`R2-060871
`
`E-UTRA Downlink Control Signaling
`Uplink TFC selection in E-UTRA
`
`18
`
`Samsung
`Samsung
`Samsung
`Motorola
`
`Joint03.3: TrCH multiplexing
`Joint03.3: TrCH multiplexing
`Joint03.3: TrCH multiplexing
`Joint03.3: TrCH multiplexing
`
`CATT
`Qualcomm Europe
`
`Joint03.3: TrCH multiplexing
`Joint03.3: TrCH multiplexing
`
`CATT
`RAN2 Chairman
`
`Nokia
`NTT DoCoMo,
`Fujitsu, Mitsubishi
`Electric, NEC,
`Sharp, Toshiba
`Corporation
`
`Ericsson
`
`Ericsson
`
`Ericsson
`
`HUAWEI
`
`Siemens
`
`Motorola
`
`Qualcomm Europe
`
`Samsung
`
`RAN2 Chairman
`
`Intel
`
`Intel
`Ericsson
`
`Joint03.3: TrCH multiplexing
`Joint03.3: TrCH multiplexing
`Joint03.4: HARQ operation (Sync/Async...)-
`(Variable TTI...)
`
`Joint03.4: HARQ operation (Sync/Async...)-
`(Variable TTI...)
`Joint03.4: HARQ operation (Sync/Async...)-
`(Variable TTI...)
`Joint03.4: HARQ operation (Sync/Async...)-
`(Variable TTI...)
`Joint03.4: HARQ operation (Sync/Async...)-
`(Variable TTI...)
`Joint03.4: HARQ operation (Sync/Async...)-
`(Variable TTI...)
`Joint03.4: HARQ operation (Sync/Async...)-
`(Variable TTI...)
`Joint03.4: HARQ operation (Sync/Async...)-
`(Variable TTI...)
`Joint03.4: HARQ operation (Sync/Async...)-
`(Variable TTI...)
`Joint03.4: HARQ operation (Sync/Async...)-
`(Variable TTI...)
`Joint03.4: HARQ operation (Sync/Async...)-
`(Variable TTI...)
`Joint03.5: Control Signalling messages (e.g.
`equiv. to HS-SCCH- AGCH)
`Joint03.5: Control Signalling messages (e.g.
`equiv. to HS-SCCH- AGCH)
`Joint03.5: Control Signalling messages (e.g.
`
`
`
`
`
`Revised
`in R2-
`061055
`
`Revision
`of R2-
`060985
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Draft Report of the RAN1-RAN2 LTE joint session (Athens, 29th March 2006)
`
`R2-060919 OFDM Downlink Signalling
`
`R2-060945
`
`Control Signaling
`
`R2-060988
`
`PCH mapping and Paging control
`
`R2-060999
`
`Control Signaling Messages
`
`R2-060823
`
`Clarifications on different UE measurement types
`
`R2-060834
`
`L1 UE measurement to support intra E-UTRA mobility
`
`R2-060835
`
`UE Measurement for Dynamic Camped Frequency Allocation
`
`R2-060841
`
`Inter-frequency/RAT Measurement Gap Control
`
`R2-060986
`
`Scheduling Scheme for Inter-frequency/RAT Measurements
`
`R2-060987
`
`Scheduling of measurements in LTE
`
`R2-060874
`R2-060824
`
`A generic association procedure to improve handover process
`Functions of the Physical Layer
`
`R2-060842
`R2-060872
`R2-060946
`R2-061038
`R2-060955
`
`Mappings between Transport Channels and Physical Channels for E-UTRA
`Uplink
`E-UTRA Physical Layer Model
`PHY Layer Models
`LTE Physical Layer Model
`Link adaption for EMBMS
`
`R2-060993
`R2-061036
`
`E-MBMS Structure
`Cell switching in LTE_Active state
`
`R2-060957 Modelling of the LTE RRC Active state
`
`R2-060958 MBMS Radio Link Design for LTE
`
`19
`
`Alcatel
`
`Motorola
`
`CATT
`
`Qualcomm Europe
`
`Nokia
`

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