SA2 kindly asks CT1 to support a common CBC assuming that deployment and configuration of the common CBC is per agreement between the sharing operators.
|
|
C1-111654
|
Reply LS on applicability of the extended wait time per CN domain (S2-112012)
|
SA2
|
To
|
Reply LS in C1-111966
SA2 answer to RAN2's queries on Wait Timer for each CN domain. SA2 left a RAN2 question to CT1 to answer.
========= extract from LS ============
Question a) Does the Extended Wait Timer in NAS run per CN domain?
Answer A) Yes. The CS domain and PS domain are expected to experience independent (over)load situations. Hence SA2 expect that the Extended Wait Timer is specific to the CN domain.
Question b) Is it expected that in case a signalling connection is already established with one CN domain, and (during the established RRC connection) a NAS-requested signalling connection establishment to the other CN domain is rejected (due to high CN load), the signalling connection to the first CN domain remains, while the signalling connection with the second CN domain is rejected with Extended Wait Timer?
Answer B) Yes, it is expected that the communication with the non-congested domain is not interrupted (this helps avoid an overload in one domain leading to increased load in the other domain).
Question C) In case that a RRC Connection Release is sent to the UE including the Extended Wait Timer, does NAS expect an indication from the AS of the concerned CN domain, or is NAS able to decide this based on NAS-internal CN domain status information?
Answer C) SA 2 believes that this question is best answered by CT 1.
|
