Generic selectors
Exact matches only
Search in title
Search in content

No response to immediate assignment

Viewing 14 posts - 31 through 44 (of 44 total)
  • Author
    Posts
  • #58808 Reply
    Kryshka
    Guest

    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

    #58809 Reply
    Pix
    Guest

    And problem occurs with several MS from different brands ?
    In different cells ?

    Randomly ?

    What do you think about the two pagings prior to the channel request ? Could it “confuse” the MS ?

    Why is the paging repeated twice ?

    #58810 Reply
    Kryshka
    Guest

    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.

    #58811 Reply
    Kryshka
    Guest

    Number 15 of different models and different brands that percepts the problem significant.
    Manufacturer Modell
    Vodafone 226
    Nokia 6300
    Nokia 6020
    Nokia 6230i
    Nokia 5310
    Nokia 3310
    Nokia 6233
    SonyEricsson S500i
    Nokia 2760
    Nokia 6230
    Samsung Electronics D880
    SonyEricsson K750i

    #58812 Reply
    Pix
    Guest

    The EGSM is interesting… that might cause some problems.

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

    #58813 Reply
    Kryshka
    Guest

    We have only E-GSM licence, so we cannot use PGSM ๐Ÿ™

    #58814 Reply
    ISO
    Guest

    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.

    #58815 Reply
    Pix
    Guest

    Kryshka,

    Can’t you steal one frequency, for few minutes ? Nobody would know… ๐Ÿ™‚

    Iso,

    IMO, the problem clearly comes from the MS : it doesn’t send the SABM on the SDCCH channel !

    But… mmmm…

    Kryshka,

    SABM is a layer 2 message ! could you check the layer 2 window in your drive test, and check if MS did send the SABM on the SDCCH channel or not ?

    Thanks,
    Pix

    #58816 Reply
    MKT
    Guest

    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

    #58817 Reply
    Pix
    Guest

    Hi MKT, I’m sorry and yet glad to see you back here. Other opportunities will arise for you, i hope ๐Ÿ™‚

    #58818 Reply
    MKT
    Guest

    Thanks Pix..

    #58819 Reply
    Water
    Guest

    Hey People
    Pix, u saying this is expected:
    “According to your description, I expect the following messages:
    1/ CHANNEL REQUEST
    2/ IMM. ASSG.
    3/ PAGING
    4/ …”

    what we get is:
    1/ CHANNEL REQUEST
    2/ IMM. ASSG.
    3/ IMM. ASSG.
    4/ IMM. ASSG.

    or at times even in idle mode we get
    1/ PAGING
    2/ IMM. ASSG.
    3/ IMM. ASSG.
    4/ IMM. ASSG.

    and our call setup is a mess, as low as 79% and the threshold is 94%. the problem is at BSC level

    #58820 Reply
    pix
    Guest

    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

    #58821 Reply
    Gokul
    Guest

    In the case of P1 rest Octet filling , how does the mobile decide whether the PactePageIndication2 is presebt or not ? Is it based on the Priority2 presence ?
    =============================
    < P1 Rest Octets > ::=
    {L I H < NLN(PCH) : bit (2) > < NLN status(PCH) : bit >}
    {L I H < Priority1 ::= Priority >}
    {L I H < Priority2 ::= Priority >}
    {L | H < Group Call information >}
    < Packet Page Indication 1 : {L | H} >
    < Packet Page Indication 2 : {L | H} >
    { null | L — Receiver compatible with earlier release
    | H — Additions in Release 6 :
    { 0 | 1
    =================================
    The Packet Page Indication i field relates to Mobile Identity i (i = 1, 2) and indicates the kind of paging procedure associated with the mobile station identity. If the identity is not IMSI the Packet Page Indication has no meaning and is ignored.
    L paging procedure for RR connection establishment;
    H packet paging procedure.
    =================================
    Regards,
    Gokul

Viewing 14 posts - 31 through 44 (of 44 total)
Reply To: No response to immediate assignment
Your information:




<a href="" title="" rel="" target=""> <blockquote cite=""> <code> <pre class=""> <em> <strong> <del datetime="" cite=""> <ins datetime="" cite=""> <ul> <ol start=""> <li> <img src="" border="" alt="" height="" width="">