MCC TF160 / SS VENDORS SESSION3GPP RAN5#69 16th – 20th November 2015 Anaheim, USA

R5-15xxxx MCC TF160

© ETSI 2014. All rights reserved

Agenda

Workshop#31 – open Action 31.3: • TF160: To provide status update on IMS re-transmissions and Big

Grants.

RTP/RTCP loopback – R5-155583: • follow-on discussions on the two alternatives.

IMS GBA (Anritsu): • Different IP address / port number for BSF server?

TTCN CRs reservation system: • migration to 3GU.

GCF WI-087/097 EPS FDD/TDD - GERAN Inter-RAT Protocol Rel-8:• Several TCs still unverified

© ETSI 2014. All rights reserved

Workshop#31 – open Action 31.3

Action 31.3: TF160: To provide status update on IMS re-transmissions and Big Grants.

Confirmed that: In test cases with default IMS handling (i.e. no test case specific IMS behaviour) we have a TTCN default handler which in case of unexpected IMS messages (e.g. SIP re-transmission) just discards them.

© ETSI 2014. All rights reserved

RTP/RTCP Loopback – R5-155583

R5-155583 was discussed Tuesday morning in the RAN5 SIG session. RAN5 endorsed that two possible ways forward will be discussed further, with a final decision being taken by the end of RAN5#69: A. Keep the current test model with clarifications in TS 36.523-3 prose. B. Alternative test model based around TTCN socket emulation.

Questions on AlternativeB?

© ETSI 2014. All rights reserved

IMS GBA

Different IP address / port number for BSF server?

© ETSI 2014. All rights reserved

TTCN CR Tdoc number reservation system – Status Update

Current status: ETSI ADN system still in use for TTCN CRs for both RAN5 (R5s15xxxx) & GERAN3 (G3t15xxxx).

3GU migration plans: • When: Plan is to start using 3GU right after TSG RAN#70, i.e. week

starting 14th December 2015.• TTCN CRs reservation will use 3GU (same as RAN5 prose CRs).

• RAN5: R5s16xxxx. • GERAN3:

• H1’16: G3t16xxxx.• H2’16: R5s16xxxx (GERAN3 merged into RAN5).

Further details TBC.

© ETSI 2014. All rights reserved

GCF WI-087/097 EPS FDD/TDD - GERAN Inter-RAT Protocol Rel-8

TC Title GERAN feature6.2.3.30 Inter-RAT cell reselection failure from GPRS Packet_transfer to E-UTRA NACC6.3.2 Inter-RAT cell reselection / From GSM_Idle/GPRS Packet_Idle to E-UTRA idle CSG cell CSG8.4.3.1 Inter-RAT handover / From E-UTRA to GPRS / PS HO PS HO13.1.11 Call setup from E-UTRA RRC_IDLE / CS fallback to GSM with PSHO / EDTM not supported / MT call PS HO13.1.12 Call setup from E-UTRA RRC_CONNECTED / CS fallback to GSM with PSHO / EDTM not supported / MO call PS HO

13.1.13 Call setup from E-UTRA RRC_IDLE / CS fallback to GSM with PSHO / EDTM supported / MT call PS HO13.4.2.2 Inter-system mobility / E-UTRA to GPRS packet PS HO13.4.2.6 Inter-RAT PS handover / From GPRS Packet_transfer to E-UTRA cell PS HO13.4.2.7 Inter-RAT PS handover / Synchronized / from GPRS Packet_transfer to E-UTRA cell / CCN mode PS HO13.4.2.8 Inter-RAT PS handover / Synchronized / from GPRS Packet_transfer to E-UTRA cell / NC2 mode PS HO

WI-087 has got 44 TCs, out of which 10 are still in ‘verifiable’ status.Any idea on the cause(s)? Is it because the required GSM/GPRS features are typically not implemented/deployed? (e.g. PS HO?)Should those TCs be added to iWD-003?

© ETSI 2014. All rights reserved