Thanks Thanks:  13
Showing results 1 to 7 of 7

Thread: CApacity management Utran and Feature Fast Dormancy

  1. #1
    Junior Member Reputation: 15
    Join Date
    2010-11-05
    Posts
    6


    2 out of 2 members found this post helpful.

    Post CApacity management Utran and Feature Fast Dormancy

    Last edited by tolite; 2013-05-06 at 06:17 AM

  2. # ADS
    Circuit advertisement
    Join Date
    Always
    Posts
    Many
     

  3. #2
    Member Reputation: 44
    Join Date
    2010-08-16
    Posts
    83


    Default Re: CApacity management Utran and Feature Fast Dormancy

    Some more details about the contents please.

  4. #3
    Junior Member Reputation: 10
    Join Date
    2012-02-03
    Posts
    3


    Default Re: CApacity management Utran and Feature Fast Dormancy

    Hi,

    Do you have more detailed info about Fast Dormancy Handling?
    Is there any impact on accesibility kpis?

    BR

  5. #4
    Junior Member Reputation: 15
    Join Date
    2010-11-05
    Posts
    6


    Default Re: CApacity management Utran and Feature Fast Dormancy

    Quote Originally Posted by ranopt View Post
    Hi,

    Do you have more detailed info about Fast Dormancy Handling?
    Is there any impact on accesibility kpis?

    BR
    With the fast dormancy, we have too many RRC connection, its the same for RRC release--> increasing of signaling.

    I speak french, so sorry for my english

  6. #5
    Member Reputation: 44
    Join Date
    2010-08-16
    Posts
    83


    Default Re: CApacity management Utran and Feature Fast Dormancy

    With fast dormancy implementation along with URA PCH, you will have huge reduction in signalling RRC/RAB attempts as well as MP load reduction and battery saving. Accessibility KPIs may suffer depending on RF environment. Try it in one RNC and see yourself. Formulae change will be required for PS DCR.

  7. #6
    Member Reputation: 61
    Join Date
    2010-07-25
    Posts
    41


    Default Re: CApacity management Utran and Feature Fast Dormancy

    A couple of years back, networks did not implement the CELL_PCH state. Needless to say that the UE's weren't well tested in this state either, even though they supported it. For an always-on PDP, the radio bearers were released typically by the network after 1 minute. With smartphones coming in requiring email sync every few minutes, this 1 minute timer became a cause of extremely low battery life (couple of hours instead of over a day). The reason was that even though email check used to complete within a few seconds, the radio bearer got released after 1 minute. Keeping the mobile on in Cell_DCH state for a minute every few minutes caused battery drain. To circumvent this, mobile vendors used the "Signalling Connection Release" message for PS domain. Typically, UE will check that there is no data for 3 to 5 seconds, and it will release signaling connection, and move the UE to Idle state. This increased the network signaling load significantly, and the UE will move to IDLE state directly and is not in the control of network. Any further establishment had to go thru a full IDLE -> FACH -> DCH transition and the number of signaling messages is large. Application's like What's App made the load worse. The number of signaling bytes is probably more than the message bytes for What's App. Specs evolved moving the control of signaling connection release from mobile to the network from Rel-8 onwards.

  8. #7
    Member Reputation: 307
    Join Date
    2008-05-23
    Location
    china
    Posts
    239


    Default Re: CApacity management Utran and Feature Fast Dormancy

    Do you know the new formula of DCR for PS while using URA PCH?

Tags for this Thread

Bookmarks

Bookmarks

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •