No response to immediate assignment

Hi Pix, here is the sample of one try to get response to paging. The sequency repeats 6 times and customer gets “missed call” notification sms, or paging is unsucssesful.

LAYER 3 DOWNLINK

Time: 6:53:23.655

PAGING REQUEST TYPE 1 3GPP TS 44.018 ver 5.21.0 Rel 5 (9.1.22)

M Protocol Discriminator (hex data: 6)
(0x6) Radio resource management message
M Skip Indicator (hex data: 0)
Value: 0
M Message Type (hex data: 21)
Message number: 33
M Page Mode (hex data: 0)
Paging mode: Normal paging
M Channels Needed for Mobiles 1 and 2 (hex data: 2)
First channel: TCH/F (full rate)
Second channel: Any channel
M Mobile Identity 1 (hex data: 05f44001 808a)
Type of identity: TMSI/P-TMSI
Identity digits: 4001808a
M P1 Rest Octets (hex data: 2b2b2b2b 2b2b2b2b 2b2b2b2b 2b)
Packet Page Indication 1: paging procedure for RR connection establishment
Packet Page Indication 2: paging procedure for RR connection establishment

Layer 3 data:
06 21 20 05 f4 40 01 80 8a 2b
2b 2b 2b 2b 2b 2b 2b 2b 2b 2b
2b 2b

LAYER 3 DOWNLINK

Time: 6:53:24.108

PAGING REQUEST TYPE 1 3GPP TS 44.018 ver 5.21.0 Rel 5 (9.1.22)

M Protocol Discriminator (hex data: 6)
(0x6) Radio resource management message
M Skip Indicator (hex data: 0)
Value: 0
M Message Type (hex data: 21)
Message number: 33
M Page Mode (hex data: 0)
Paging mode: Normal paging
M Channels Needed for Mobiles 1 and 2 (hex data: 2)
First channel: TCH/F (full rate)
Second channel: Any channel
M Mobile Identity 1 (hex data: 05f44001 808a)
Type of identity: TMSI/P-TMSI
Identity digits: 4001808a
M P1 Rest Octets (hex data: 2b2b2b2b 2b2b2b2b 2b2b2b2b 2b)
Packet Page Indication 1: paging procedure for RR connection establishment
Packet Page Indication 2: paging procedure for RR connection establishment

Layer 3 data:
06 21 20 05 f4 40 01 80 8a 2b
2b 2b 2b 2b 2b 2b 2b 2b 2b 2b
2b 2b

LAYER 3 UPLINK

Time: 6:53:24.124

CHANNEL REQUEST 3GPP TS 24.008 ver 5.6.0 Rel 5 (9.1.8)

M Establishment Cause (hex data: 2c)
Meaning of establishment cause: Answer to paging TCH/F in dual rate

Layer 3 data:
2c
LAYER 3 DOWNLINK

Time: 6:53:24.296

IMMEDIATE ASSIGNMENT 3GPP TS 44.018 ver 5.21.0 Rel 5 (9.1.18)

M Protocol Discriminator (hex data: 6)
(0x6) Radio resource management message
M Skip Indicator (hex data: 0)
Value: 0
M Message Type (hex data: 3f)
Message number: 63
M Page Mode (hex data: 0)
Paging mode: Normal paging
M Dedicated Mode or TBF (hex data: 0)
TMA: No meaning
Downlink: no meaning
T/D: This message assigns a dedicated mode resource
Description: This message assigns a dedicated mode resource
M Channel Description (hex data: 507001)
Timeslot: 0
Channel type and TDMA offset: SDCCH/8 + SACCH/C8 or CBCH (SDCCH/8)
Subchannel: 2
Training sequence code: 3
Hopping channel: RF hopping channel
MAIO: 0
HSN: 1
M Request Reference (hex data: 2cbcb5)
Random access information: 44
T1′: 23
T2: 21
T3: 37
Frame Number: 31351
M Timing Advance (hex data: 04)
Timing advance value: 4 (= 14 microseconds)
M Mobile Allocation (hex data: 0207ff)
Mobile allocation channels (total 2 bytes): 1 2 3 4 5 6 7 8 9 10 11
M IA Rest Octets (hex data: 2b2b2b2b 2b2b2b2b 2b)
Compressed_Inter_RAT_HO_INFO_IND: A compressed version of the INTER RAT HANDOVER INFO message shall not be used

Layer 3 data:
06 3f 00 50 70 01 2c bc b5 04
02 07 ff 2b 2b 2b 2b 2b 2b 2b
2b 2b

That happens in whole network and different cells. We use only EGSM frequencies. The paging is repeated (I found in ericsson docs) twice if there no big paging load and paging is repeated by BTS (instead of dummy paging), but not from MSC.

The EGSM is interesting… that might cause some problems.

Could you try, temporarily, to use PGSM frequencies only ?

Hi,

Have you check paging stats and processor loading already?

We experienced same scenario as you described but we later found out congestion on MSC Media Gateway Transit thus this occurs only on peak hours..but yours is weird since you experienced same thing at 3 am.

Hi friends,

I am back to pavilion. I didn’t succeeded in the new sphere ( of politics).

It is always good to see some good discussions.

One thing is sure from the current discussion and i.e

Nothing is wrong at cell level.

So, no need to check and modify any parameter at cell level.

Just focus the attention at BSC.

Now for the cases like “Timers” I would suggest to touch the concept of ” CLOCK”. May be at BSC level or at MSC. Also, give a consideration to the ” Media part” as eventually this is only the transporter of “clock” from MSC to BSC.

Hope you can find some clue thereafter!

Regards,

MKT

Thanks Pix..

hi,

what i’m saying is that your nemo MS is collecting all immediate assignments sent by the cell. Not only the ones which are aiming at your MS especially.

To know which immediate assignments are sent to your MS, you must match the random number in the ch req and in the imm assg.

regards
pix