Академический Документы
Профессиональный Документы
Культура Документы
a. Cell DCH:
When UE is switched ON, it assumes the CELL_DCH State by default.
It exists when UE really requires UL/DL dedicated resource.
UE is characterized at cell level according to its current Active set.
Logical channels DCCH+DTCH are mapped to transport channel DCH.
E.g. Voice call(CS), Video telephony(CS+PS)
(1) UE doesnt require continuous circuit connection with n/w, but DL packets will work.
(2) UE is forced to release the n/w resources to decrease the congestion problems (flip-flop between
DCH and FACH).
(3) Eventual location updates to support CELL_PCH and URA_PCH states (flip-flop between
FACH and PCH).
E.g. Call on hold(CS), File downloading(PS)
No dedicated UL/DL is provided. However, UE will keep monitoring to DL common transport
channel FACH continuously and receives packet data meant for UE itself.
When UL transmission is required, it uses RACH for 1-2 frames or CPCH for few more frames,
depending on common access procedures; still UL transmission will be discontinuous.
UE is known on cell level, but this time its based on the last cell update it made.
c. Cell PCH:
This happens when UE doesnt require an active connection(common/dedicated). But still needs
to be connected, as its expecting a n/w initiated or terminated call(CS or PS) in future.
So, no UL transmission is allowed. Selects a PCH(based on algo.) and keep monitoring (receiving)
it in discontinuous mode(DRX).
Can commute only into CELL_FACH state.
E.g. No outgoing call or data receive for long time
UE is still identified on cell level, but now in the cell where UE made its last update, when it was in
CELL_FACH state.
At regular time interval, UE would have to move in CELL_FACH state to update the location area.
If UE is traveling, this update will become frequent because of changing cells.
In some cases UE can have the transition from CELL_DCH to CELL_PCH, but not vice versa; it
has to go via CELL_FACH.
d. URA PCH:
This can be considered as a general case of CELL_PCH state. Because all the characteristics are
same except one.
That is, UE is known on URA(UTRAN Registration Area) level rather than cell level. It listens to
PCH(and updates URA when required).
If UE is traveling continuously from one cell to another. It would have to transit multiple time to
CELL_FACH state for location update. By assigning URA_PCH state, this condition is avoided,
since 1 URA contains one or more cells and vice versa.
3) In which conditions UE will be in Cell FACH state?
This happens when,
UE doesnt require continuous circuit connection with n/w, but DL packets will work.
UE is forced to release the n/w resources to decrease the congestion problems (flip-flop between
DCH and FACH).
Eventual location updates to support CELL_PCH and URA_PCH states (flip-flop between FACH
and PCH).
E.g. Call on hold(CS), File downloading(PS)
4) What is the difference between Cell PCH and URA PCH state?
UE is known on URA(UTRAN Registration Area) level rather than cell level
If UE is traveling continuously from one cell to another. It would have to transit multiple time to
CELL_FACH state for location update. By assigning URA_PCH state, this condition is avoided,
since 1 URA contains one or more cells and vice versa
5) What is U-RNTI?
URNTI is a 32bit identity.
SRNC identifier + SRNTI makes URNTI
The most obvious cause for performing a handover is that due to its movement a user can be
served in another cell more efficiently (like less power emission, less interference). It may
however also be performed for other reasons such as system load control.
13) In what situation UE goes to CELL PCH and URA PCH states?
a. Cell PCH:
This happens when UE doesnt require an active Connection(common/dedicated). But still
needs to be connected, as its expecting a n/w initiated or terminated call(CS or PS) in future
b. URA PCH:
In Cell PCH UE is still identified on cell level, but now in the cell where UE made its last update,
when it was in CELL_FACH state.At regular time interval, UE would have to move in
CELL_FACH state to update the location area. If UE is traveling, this update will become
frequent because of changing cells. If UE is traveling continuously from one cell to another. It
would have to transit multiple time to CELL_FACH state for location update. By assigning
URA_PCH state, this condition is avoided, since 1 URA contains one or more cells and vice versa
14) What is Cell Update Procedure? What are various Cell Update causes?
Uplink data transmission:
For FDD, if the variable H_RNTI is not set, and for TDD:
if the UE is in URA_PCH or CELL_PCH state; and
if the UE has uplink RLC data PDU or uplink RLC control PDU on RB1 or upwards to
transmit:
perform cell update using the cause "uplink data transmission".
Paging response:
if the criteria for performing cell update with the cause specified above. are not met; and
if the UE in URA_PCH or CELL_PCH state, receives a PAGING TYPE 1 .message fulfilling the
conditions for initiating a cell update procedure.
perform cell update using the cause "paging response".
Radio link failure:
if none of the criteria for performing cell update with the causes specified above in the current
subclause is met:
if the UE is in CELL_DCH state and the criteria for radio link failure are ,or
if the transmission of the UE CAPABILITY INFORMATION message fails.
perform cell update using the cause "radio link failure".
MBMS ptp RB request:
if none of the criteria for performing cell update with the causes specified above in the current
subclause is met; and
if the UE is in URA_PCH, Cell_PCH or Cell_FACH state; and
if the UE should perform cell update for MBMS ptp radio bearer request,
perform cell update using the cause "MBMS ptp RB request".
Re-entering service area:
if none of the criteria for performing cell update with the causes specified above in the current
subclause is met; and
if the UE is in CELL_FACH or CELL_PCH state; and
2> if the UE has been out of service area and re-enters service area before T307 or T317
expires:
3> perform cell update using the cause "re-entering service area".
RLC unrecoverable error:
if none of the criteria for performing cell update with the causes specified above in the current
subclause is met; and
if the UE detects RLC unrecoverable error [16] in an AM RLC entity:
perform cell update using the cause "RLC unrecoverable error".
Cell reselection:
if none of the criteria for performing cell update with the causes specified above in the current
subclause is met:
if the UE is in CELL_FACH or CELL_PCH state and the UE performs cell re-selection; or
if the UE is in CELL_FACH state and the variable C_RNTI is empty:
perform cell update using the cause "cell reselection".
Periodical cell update:
if none of the criteria for performing cell update with the causes specified above in the current
subclause is met; and
if the UE is in CELL_FACH or CELL_PCH state; and
if the timer T305 expires; and
if the criteria for "in service area" and
if periodic updating has been configured by T305 in the IE "UE Timers and constants in
connected mode" set to any other value than "infinity":
perform cell update using the cause "periodical cell update".
MBMS reception:
if none of the criteria for performing cell update with the causes specified above in the current
subclause is met; and
if the UE is in URA_PCH, Cell_PCH or Cell_FACH state; and
if the UE should perform cell update for MBMS counting ,
perform cell update using the cause "MBMS reception".