2ms – Current restriction list for 3.0 and 4.

0
 If CS & PS co-exist (on same UE), do not allow PS on 2ms ***

 If CS exists and PS comes in, always establish on 10ms

 If PS exists and CS comes in, drops PS to allow CS. PS will re-establish and then it will be on set up on 10ms

 Do not allow Compressed Mode for PS on 2ms ***

 Never allow CM for PS on 2ms TTI. Choose DAHO instead of MAHO for 2ms TTI user.

Reason for this is CR723699 (under investigation in BCR4.1). David is currently investigating to see exactly what
is expected, based on Macro requirements.

 If PS Handin, do not allow PS handin on 2ms ***

 Never allow 2ms TTI for PS Handin. Always give 10ms to incoming PS. LIFTED

 Lab only retsriction on PC302

 Having 2ms call means data rate on other users drop to 0K, PC302 is not recommended to have 2ms enabled in
field on Home deployments.

 Max 2ms TTI user = 1 ***

 Pico chip result and lab results indicate throughput degradation if max 2ms users > 1.
*** All restrictions are configurable via sparePara35 strings
 If 2ms PS user exist already, subsequent users on 10ms have better throughput compared to if they were on 2ms
Alcatel-Lucent – Internal
1 | 2ms restrictions | June 2012 Proprietary – Use pursuant to Company instruction.
Functionality after restrictions and workarounds

Scenario 2ms 10ms Comments

PS setup -multi PDP Yes Yes No restriction

PS on top of CS NO Yes Every PS on top of existing CS will be setup on 10ms to avoid PC crash.

CS on top of PS NO Yes Incoming CS will cause drop of PS. CS will be setup and then we rely on UE to

re-establish PS RAB again – when requested again, PS will be set on 10ms.

Hand in YES Yes PS Handin will not be allowed on 2ms. PS call will be handed in at 10ms.

LIFTED
Hand out Yes Yes There is no special restriction but implicit simplification of scenarios.

-SimB calls will anyways have PS on 10ms.

- Only PS will ever exist on 2ms.

Alcatel-Lucent – Internal
2 | 2ms restrictions | June 2012 Proprietary – Use pursuant to Company instruction.
2ms TTI Post 3.04 Activities

P1 MUST HAVE: 2ms TTI demo only PC302 (CR681969)

LATEST: CR is still under investigation with Pico/ RTPP

P2 MUST HAVE: Cat4 UE throughput less than requirement (CR726530, SAE MR

2… TBD)

LATEST: Restriction lifted, ETFCS table modified, Cat4 UE throughput now

meets requirement

P3 NICE TO HAVE...: 2ms Handin- should now WORK with changes around MAC
E scheduler, this can be tested and if proven to be ok, the restriction on
2ms TTI handin (currently reverts to 10ms) could be lifted in 3.05. Will
require mild NLT effort to confirm.

LATEST: Restriction lifted, 2ms PS handin is working, verified on 3.0.71

Alcatel-Lucent – Internal
3 | 2ms restrictions | June 2012 Proprietary – Use pursuant to Company instruction.