Report from TSG GERAN2#21bis St Paul’s Bay, Malta, 4th – 8th October 2004 Diana Edwin, Siemens 3GPP TSG GERAN WG2 Chairman +44 (0)1794 833307, diana.edwin@roke.co.uk

Contents Introduction Technical discussions Initial document distribution Technical discussions Pre-release 5 corrections Release 5 Release 6 Open Work Items Liaison Statements Action points and ongoing topics Meeting calendar

Introduction Reference documents 67 initial, independent documents Official report to be distributed prior to next meeting GERAN2 work plan v17.0 in G2#21bis(04)0629 67 initial, independent documents 84 with mirror CRs, 135 after revisions 99% of initial documents were sent before the deadline 100% sent before the deadline were presented Approximate time distribution ~40% for MBMS ~30% for PS Handover ~25% for other Rel-6 items ~5% for pre-Release 6 corrections 39 delegates

Initial Document Distribution (1) 4 Letters / Reports from Other Groups 2 5.1 Pre-Release 5 Corrections 6 Release 98/99 3 Release 4 3 5.2 Release 5 Corrections 2 5.2.1 Iu mode corrections 0 5.2.2 Other corrections 2 5.3 Completed Release 6 Work Items 0 5.4 Open Work Items 57 5.4.1 Multimedia Multicast and Broadcast Service 29 5.4.2 Uplink TDOA for GSM/GPRS – PS domain 2 5.4.5 Conversational Services in A/Gb Mode via the PS Domain 13 5.4.6 Reduction of PS service interruption in Dual Transfer Mode 0 5.4.7 Small Technical Enhancements and Improvements for Rel-6 13 5.5 Other Technical Work 0 Total (without mirror CRs) 67

Initial Document Distribution (2)

Contents Introduction Technical discussions Initial document distribution Technical discussions Pre-release 5 corrections Release 5 Release 6 Open Work Items Liaison Statements Action points and ongoing topics Meeting calendar

Release 98 – A-GPS corrections G2-040585 CR 04.31-A114 rev 3: Correction of relation between GSM Reference Frame and GPS TOW to achieve high-accuracy timing assistance for AGPS Agreed G2-040576 CR 04.31-A118: Correction of allowed RRLP GPS reference location shapes for compatibility and consistent operation Postponed Companies requested time to check (Siemens) G2-040531 Positioning Reporting inconsistencies This topic requires further study and may involve RAN2 and RAN3 (Joint meeting required?)

Release 4 G2-040499 CR 48.008-137 Timers for the VGCS uplink control procedure Postponed G2-040502 CR 48.058-012 Incorrect length of group call reference IE Postponed G2-040505 CR 48.058-015 Incorrect length of the eMLPP priority Postponed Author was not available to present CRs

Release 5 G2-040497 CR 48.016-017 Correction of SNS PDUs for IP support Agreed G2-040617 CR 44.031-122 rev 2: Correction of the Real-Time Integrity field Postponed It was agreed to align this change in behaviour according to the available Rel-5+ indicator for the SMLC G2-040518 CR 48.018-089 rev 7 RIM-NACC clean up Postponed Handled in RIM/NACC parallel session, the technical issues have all been agreed Only editorial corrections needed so agreement on this CR is expected at G#22

Release 6 – Closed Work Items No contributions on the following closed WIs Multiple TBFs Streaming Services FLO U-TDOA for CS

Release 6 – U-TDOA G2-040590 CR 43.059-051 Inclusion of PS functionality for U-TDOA location method Agreed (Endorsed) GERAN WG2 agrees with the content of this CR G2-040509 CR 48.071-022 rev 7: Inclusion of PS functionality for U-TDOA location method Agreed

MBMS Stage 2 CRs GERAN WG2 endorsed the following draft CRs to TS 43.246: G2-040580 Addition of flexible reconfiguration for MBMS_BEARER_ID and MS_ID G2-040581 Addition of reception of multiple sessions G2-040611 Draft CR to TS 43.246 on Pre-notification arrangement for optimising power consumption WORKING ASSUMPTION to pre-notify on a session basis (assuming the service and session IDs fit into the message) G2-040626 Modification to description of MBMS Channel Release procedure G2-040625 Addition of the cause indication whereby an MBMS p-t-m bearer is not established in a cell inside the MBMS assignment message

MBMS Stage 2 CRs Draft CRs to TS 43.246 needing more work: G2-040607 MBMS Reception resumption after NAS service interruption G2-040537 BSS Release of MBMS Context if no data arrives Discussion paper G2-040568 MBMS Service Continuity at the service area border Negative response (i.e. reject) to MBMS SERVICE REQUEST message shall include one of four cause values Some scenarios still to be investigated

MBMS Stage 3 CRs G2-040615 CR 44.060-576 rev 2: RLC protocol behaviour for MBMS data transfer Agreed Introduces non-persistent RLC mode which is only applicable for MBMS bearers Discussion in TEI6 WI about whether to also use this new RLC mode for (E)GPRS TBFs (FFS) G2-040532 CR 48.018: Addition of MBMS session start/stop messages Drafting Ongoing It was agreed that the BSS may discard MBMS LLC PDUs arriving from the SGSN (e.g. if no radio channel has been established yet) Handling and actions on MBMS service context needs to be explained more in the procedures G2-040573 MBMS Session Start Request Drafting Ongoing To be discussed with WG1

MBMS Stage 3 CRs G2-040535, 36 CRs to 44.060 & 44.018: Addition of MBMS access procedures and MBMS SERVICE REQUEST message Drafting Ongoing It is accepted that this CR prevents further extension to the 8-bit PCR for further access causes (with 3 random bits), after this the use of the 11-bit formats would need to be mandated. G2-040533, 34 CRs to 44.060 & 44.018: Addition of MBMS NOTIFICATION message Drafting Ongoing Shorter version of TMGI + Session ID in order to provide pre-notification in this message is FFS

MBMS Neighbour Cell Info G2-040566 Prioritizing MBMS Neighbouring Cell Information GERAN2 generally agrees with this concept, but it needs to be seen by GERAN1 also. G2-040569 Acquisition of neighbouring cell data during packet transfer mode and/or MBMS Benefits for using this proposal for MSs with (E)GPRS TBF should be investigated over what is available today. Some aspects may need to be discussed in WG1. G2-040605, 570 Draft CR 43.246 and CR 44.060-574 on Use of the MBMS NEIGHBOURING CELL INFORMATION message CRs to be completed once concept is agreed (by WG1)

MBMS RIM G2-040520 RIM applications for MBMS Some dependencies on details of main R5 RIM/NACC CR For next revision it is assumed that the controlling BSS requests the MBMS information via RIM for each TMGI, this remains valid until the end of the MBMS session or until the controlling BSS resets the info for the TMGI Stage 3 CRs to be revised, but can only be agreed once Rel-5 CR for RIM/NACC is agreed. G2-040521 CR 48.018-113 Introduction of the RIM application SI3 G2-040522 CR 48.018-114 Introduction of the RIM application MBMS data channel

MBMS – Paging co-ordination G2-040555 PS Paging Co-ordination in MBMS The single message at SESSION START is still preferred over introducing a “UE linking” procedure for all MBMS-capable MSs whenever they create a BSS PFC. Need to liase to SA2 on this point G2-040556 CS Paging Co-ordination in MBMS Need to decide on which is preferred UL RR or GTTP message for MS to send P-TMSI at call establishment Evaluate RA-Capability-Update procedure for both PS/CS Feedback on the related stage 3 CRs is requested by Vodafone

PS HO G2-040538 Packet Switched Handover for GERAN A/Gb mode, Stage 2, TS 43.129 v0.7.1 Presented and editorial changes in G2-040539 agreed. Draft CRs to TS 43.129 were agreed on the following topics: G2-040597 Handling of MS RAC during PS Handover G2-040598 Container Handling G2-040599 XID Parameter Management G2-040600 Additional step for the transfer of the XiD Command G2-040608 Packet Handling/Forward SRNS context The TS is considered 70 % complete

PS HO – NSAPI/SAPI/PFI mapping Of the four options for handling remapping of the SAPI/PFI values for each NSAPI, as laid out in G2-040544, two are still being considered Alternative 1 – Remapping can be done by the new SGSN (the MS is informed via the PS HO Command message), the MS maintains knowledge of both the old and the new mapping until PS HO is complete. Ericsson’s and Siemens’ preference Alternative 3 – If remapping is required for a PDP Context, this PDP Context will not be handed over and will be subject to PDP Context Modification procedures in the new cell causing a delay in data resumption. Nokia’s preference, acceptable for Vodafone and Ericsson

PS HO – START_PS handling and UE RAC Both of the existing solutions for providing these parameters when needed for PS HO have significant disadvantages, Option 1: GMM procedures are affected (SGSN and possibly BSS has to store 3G params). Could use a RA-Capability-Enquiry to retrieve the info from the SGSN, which would reduce the number of times the info is sent unnecessarily on the Gb. Option 2: MS has to send this (large) information in an RLC/MAC control message (How? No segmentation scheme in uplink?). RAN2 needs to be contacted regarding how the source RNC gets the MS RAC to insert in the same forward container in the HO preparation phase. CN1 needs to be contacted asking about option 1 which would affect GMM procedures.

PS HO – LLC and SNDCP Engine Management G2-040538 After discussion it was agreed that using the combination of LLC UM and RLC AM modes risks that one LLC PDU will be lost, this means we cannot call this behaviour “LOSSLESS” but there is still a benefit in providing this “Minimum packet loss” behaviour. It was agreed that: “SNDCP and PDCP sequence numbers can be transferred across PS handover in order to avoid data duplications and to avoid data loss for services that make use of LLC-ABM in A/Gb mode.”

PS HO – Packet Forwarding FORWARD SRNS CONTEXT procedure is at least for LLC AM and for when delivery order is required. CR in G2-040549 assumes DL data starts at RAU Complete to align with existing 23.060, this is FFS. Translation between N-PDU and PDCP PDU sequence numbers needs to be studied.

Release 6 – DTM G2-040593 CR 44.018-390 rev 1: MS behaviour in DTM resource reallocation during uplink TBF establishment Agreed G2-040517 CR 43.055-026 rev 2 Alignment of stage 2 with stage 3 for DTM Endorsed (to go to WG1) G2-040513 CR 44.018-389 rev 1 Change to PS Timing Advance behaviour for DTM to Packet Transfer transition Postponed G2-040515 CR 44.018-391 Removal of use of main DCCH for Packet Resource in DTM Agreed G2-040594 CR 44.060-575 rev 1: MS behaviour on receiving PACKET CS RELEASE INDICATION message Agreed G2-040602 CR 44.018-388 rev 1: Clarification of messages used for change of frequency parameters in DTM resource reallocation Agreed

Release 6 – VGCS G2-040601 CR 44.018-366 rev 2 Introduction of new VGCS/VBS ciphering mechanism Postponed It was noted that it is assumed that support of VGCS ciphering is mandatory for a Rel-6 MS, however this is not explicitly stated in TS 42.068 (stage 1) or TS 43.068 (stage 2). Possible LS or inputs to CN1/SA3. G2-040511 Draft to CR 48.008 Introduction of USIM based VGCS/VBS ciphering mechanism This needs more work offline

Release 6 – RLC mode modifications G2-040553 BSS controlled RLC mode selection This proposes that the BSS should be able to decide the preferred RLC mode for both DL and UL TBFs. G2-040554 Non-persistent RLC mode for p-t-p (non-MBMS) services Proposes a non-persistent RLC mode with a variable non-exhaustive retransmission functionality (it could also be set to provide no retransmissions). Performance results are requested to show the gains over RLC UM with link adaptation.

Release 6 – Other G2-040592 CR 44.060-551 rev 4: RLC data block usage during change of service demand Agreed G2-040545 Fast TBF Reallocation This proposal is applicable only for the non-mTBF case, it is still not clear what the benefits of this feature are whether this enhancement is justified and why we need to provide better QoS to parallel flows in a Rel-6 non-mTBF-capable MS. More justification expected for G#22

Outgoing LSs G2-040582 LS on user-specific priorities for MBMS services G2-040628 LS to SA2 on GERAN Assumptions and Open Issues for MBMS G2-040627 LS on ‘Ciphering for Voice Group Call Services’

Meeting Calendar 2004 Meeting Week Dates Place Host G2 #17bis 3/04 12 – 16 Jan 2004 Edinburgh, UK EF3 G2 #18 6/04 03 – 05 Feb 2004 Reykjavik, Iceland EF3 G2 #18bis 13/04 22 – 26 Mar 2004 Phoenix, USA NAF3 G2 #19 17/04 20 – 22 Apr 2004 Cancun, Mexico NAF3 G2 #19bis 22/04 24 – 28 May 2004 Sophia-Antipolis ETSI G2 #20 26/04 22 – 24 Jun 2004 Bilbao, Spain EF3 G2 #21 35/04 24 – 26 Aug 2004 Montreal, Canada NAF3 MBMS Adhoc 38/04 13 – 15 Sep 2004 Turin, Italy TIM G2 #21bis 41/04 04 – 08 Oct 2004 Malta EF3 G2 #22 46/04 09 – 11 Nov 2004 Cape Town, South Africa Possible stage 3 CR drafting sessions on individual Rel-6 topics. 49/04 22 – 26 Nov 2004 ? 50/04 29 Nov – 3 Dec 2004 ?

Meeting Calendar 2005 Meeting Dates Location G2 #23 25 – 27 Jan 2005 [Tampa, Florida] G2 #23bis 07 – 11 Mar 2005 [Helsinki, Finland] G2 #24 05 – 07 Apr 2005 [Dublin, Ireland] G2 #24bis 23 – 27 May 2005 [US] G2 #25 21 – 23 Jun 2005 [US] G2 #26 23 – 25 Aug 2005 [Europe] G2 #26bis 03 – 07 Oct 2005 [Europe] G2 #27 08 – 10 Nov 2005 [US]