Paging and Cell Update Issue with 3 SCCPCH

For internal use only

1
Nokia Siemens Networks

Issues
Some Blackberry devices were showing unexpected behavior when they
were in Cell PCH and the 3 SCCPH configuration was used in the RAN
The affected devices did not:

Issue 1: Did not respond to the Cell Update Confirm from the NW PS call drop
Issue 2 Did not respond to the CS paging from the NW Unsuccessful Mobile Terminated call

Issue 1

Issue 2
The device
unexpectedly repeats
the CU and after few
attempts the NW
release the PS Call
PS Call release
NW sends the paging
on the common
chanel but no
response from the
device
Device receives the
aging and send the
CU
Device respond to the
CUC with UMIC

For internal use only

2
Nokia Siemens Networks

Devices used for verification of NW workaround

Model

Chipset

SW Version

OS

BB9700

Marvel PXA940

6.0.0.448

BB OS 6.0

BB9700

Marvel PXA940

5.0.0.586

BB OS 5.0

BB9360

Marvel PXA940

7.0.0.177

BB OS

BB9800

Marvel Tavor PV2

6.0.0.526

BB OS 6.0

BB9900

MSM8260

7.0.0.187

BB OS 7.0

BB9300

Mavel Tavor PV2

5.0.0.846

BB OS 5.0

BB9300

Marvel Tavor PV2

6.0.0.448

BB OS 5.0

Samsung Galaxy 4G S

STE M5720

T595Vkb4_EC14_uvkcj

Android Froyo 2.2.1

LG G2x

MSM7230

Android Gingerbread 2.3.3

HTC Magic

MSM7200A

Android Gingerbread 2.3.3

HTC HD7

QSD8250

Windows 7

iPhone 3Gs

Intel XMM 6080

4.3

iOS

iPhone 4

Intel XMM 6160

4.3

iOS

Motorola Cliq

MSM7201A

Blur_Version.1.1.14.MB200.Orange.en.GB

Android Cupcake 1.5

Nokia N8

014.002

S60 V3

For internal use only

3
Nokia Siemens Networks

Verification Scenario
Test Scenario 1: Uplink data transfer when the Device is in Cell PCH
- Step 1: Device in cell_PCH
- Step 2: Start data transfer from the device. The device send Cell Update to the NW
with cause (ul data transmission)
- Step 3: NW responds with cell_update_confirm
- Step 4: Device responds to cell_update_confirm with the Utran_mobility_confirm
- Step 5: RB_reconfiguration, Data transmission is successful
Test Scenario 2: Device is in Cell PCH and there is an incoming voice call
- Step 1: device in cell_PCH
- Step 2: Incoming AMR call, the NW pages the device
- Step 3: Device sends a Cell Update with cause (cs terminated call)
- Step 4: Device responds to cell update confirm from the NW with
utran_mobility_information_confirm
- Step 5: The device sends the paging response to the NW

For internal use only

4
Nokia Siemens Networks

Outcome of testing
With the NW workaround:
All tested devices have responded properly to the CS paging from the NW
All MT call were successful

All the device have successfully performed the Cell update procedure
No PS drop call

There was no unexpected behavior on other legacy devices in

the tested environment

For internal use only

5
Nokia Siemens Networks