Sorry for my last reply to this post ...
Only now I understand that there is a UMTS tag in StackOverflow ... But I think I can help in some way.
First of all, let me answer your question. Then I will provide some information about this:
1. Does the value of the T323 timer indicate for the network or is changing with adaptation?
This timer is set over the network. It has the following possible values: 0,5,10,20,30,60,90,120 seconds.
I believe that it does not change dynamically, but the network can use different values in different regions or cells.
2. Can the transition from DCH to IDLE or DCH to PCH in this model?
I may be mistaken, but I believe that this is impossible.
SCRI is sent by phone. Then move the device to a different state (either IDLE, CELL_PCH, or URA_PCH). However, I believe that SCRI is usually sent when the device is in CELL_FACH. Thus, the phone switches to PCH only after the FACH state (and not from CELL_DCH).
3. Is there a way in the Android device to find out the value of the T323 timer timeout?
This timer is sent over the network in a System Information Block Type 1. Message. This value is then read and processed by the Mobile Baseband Processor (or modem or CP communications processor).
Typically, the Fastdormancy function is handled by the modem, and eventually the CP logs can print the value of T323. However, CP Logs is not so easy to use in end-user phones. This kind of logs is disabled in the end user software.
Of course, some company may want to process the FastDormancy function on the application side, and then you can check through the log message. However, I think this is not so ...
Considerations for the T323
This timer was created to block too many SCRI messages. This timer determines how long the mobile phone must wait to send two consecutive SCRI messages.
The following is the workflow: - The phone detects that new packets will not be sent to the network. - The phone sends the first SCRI and starts the T323 timer. - The network transfers the phone to CELL_PCH or URA_PCH. - The phone sends some data and detects that a new data packet will not be sent in the near future. - He's trying to send SCRI again. However, if T323 is running, this SCRI is blocked. - After the expiration of the T323 SCRI can be sent to the network, and the whole process will start again.
As you know, after sending a SCRI message, the network puts the phone into a low power consumption state (Cell_PCH or URA_PCH). By doing this, some resources are freed. If any new packet needs to be sent to the network, the telephone must return to CELL_FACH / CELL_DCH, and the resources must be restored. After sending data packets, the phone will probably send SCRI again, and the entire resource will be released again.
This is why the T323 was created. To avoid allocation or restoration of resources very often. This behavior increases the load on the signal in the cell because resources are released / restored through signaling messages.
As a mobile phone detects, a new package will not be sent
It is entirely the responsibility of the mobile phone. Thus, each mobile phone brand has its own algorithm or function to detect that SCRI can be sent.
Of course, you can create complex algorithms for predicting when a data packet will no longer be sent, and do not send an unnecessary SCRI.
However, a simpler solution was applied. Usually the phone just waits sometime, and if the data packet was not sent, it tries to send a SCRI message.
I hope I can help you.
T323 sometimes causes some confusion. But it only says how long the phone should wait before sending a new SCRI - after sending the first one.
It is installed over the network, and when set to 0, the phone does not wait for the SCRI to be sent. He can send whenever he wants.
However, the responsibility for the mobile phone rests with the mobile phone.
Fastdormancy strives to improve energy consumption by requesting the release of resources as soon as more packets are sent.