B.1 Roaming into networks or registering in network entities not supporting CCBS
22.0933GPPCompletion of Calls to Busy Subscriber (CCBS)Release 17Service description, Stage 1TS
This clause looks at the times when either parties involved in CCBS may roam from a supporting network entity into a non-supporting network or network entity.
Consider the times when neither Subscriber A or Destination B can register in another location area.
Subscriber A cannot register in another location area:
a) Having received a CCBS Possible indication and while the network is awaiting the initial CCBS Request;
b) Having received a CCBS Recall and while the network is awaiting acceptance of the CCBS Recall;
c) During the duration of the CCBS Call.
Destination B cannot register in another location area:
a) During the duration of the CCBS Call;
B.1.1 Subscriber A may register in a non-supporting network or network entity
Whilst waiting for the CCBS Recall from Destination B
If Subscriber A registers in a non-supporting entity whilst waiting for the CCBS Recall from destination B. The network shall be aware that the CCBS supplementary service is not supported and shall suspend the CCBS Request. The CCBS Request shall remain suspended until either Subscriber A registers in a supporting entity or until the service duration timer T3 expires.
B.1.2 Destination B may register in a non-supporting network entity
a) If destination B becomes idle after "CCBS Possible" has been sent and before a "CCBS Request" is received.
If destination B is idle and has registered in a non-supporting entity when the CCBS Request arrives then the CCBS Request shall be accepted, but the handling of the destination B CCBS queue shall be frozen until the destination B registers in a supporting entity or until a service duration timer expires.
b) While T8 is running.
If destination B registers in a non-supporting network entity during T8, then the processing of the destination B CCBS queue shall be stopped until either destination B registers in a supporting network entity or the service duration time expires.
c) After T8 expires.
If Destination B registers in a non-supporting entity after having sent the CCBS Recall, then error handling will ensure that the entity informs the network that it doesn’t support CCBS. However, the CCBS Call shall be allowed to continue. When the non-supporting entity receives the CCBS Call, it will not be able to inform the network that the CCBS has been completed. The only safeguard is that T9 in the network will expire, which will result in automatic deactivation of the CCBS Request from the queue.
d) When a CCBS Request is suspended and before it is resumed.
If destination B has registered in a non-supporting entity when the CCBS Resume arrives, then the CCBS Resume shall be treated as a CCBS Request and shall be accepted, but the handling of the destination B CCBS queue shall be frozen until destination B registers in a supporting entity or until a service duration timer expires.
Annex C (informative):
Change history
|
Change history |
|||||||||||
|
TSG SA# |
SA Doc. |
SA1 Doc |
Spec |
CR |
Rev |
Rel |
Cat |
Subject/Comment |
Old |
New |
WI |
|
Jun 1999 |
GSM 02.93 |
Transferred to 3GPP SA1 |
7.0.0 |
||||||||
|
SA#04 |
22.093 |
R99 |
Transferred to 3GPP SA1 |
3.0.0 |
|||||||
|
SP-05 |
SP-99479 |
S1-99638 |
22.093 |
001 |
R99 |
D |
Editorial changes for alignment |
3.0.0 |
3.0.1 |
Editorial changes |
|
|
SP-11 |
SP-010065 |
S1-010258 |
22.093 |
Rel-4 |
Transferred to 3GPP Release 4 |
3.0.1 |
4.0.0 |
||||
|
SP-16 |
SP-020267 |
S1-021043 |
22.093 |
Rel-5 |
Updated from Rel-4 to Rel5 |
4.0.0 |
5.0.0 |
||||
|
SP-26 |
SP-040744 |
S1-040997 |
22.093 |
Rel-6 |
Updated from Rel-5 to Rel-6 |
5.0.0 |
6.0.0 |
||||
|
SP-36 |
22.093 |
Rel-7 |
Updated from Rel-6 to Rel-7 |
6.0.0 |
7.0.0 |
||||||
|
SP-42 |
– |
– |
Rel-8 |
Updated from Rel-7 to Rel-8 |
7.0.0 |
8.0.0 |
|||||
|
SP-46 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-9 by MCC |
8.0.0 |
9.0.0 |
|
|
2011-03 |
– |
– |
– |
– |
– |
– |
– |
Update to Rel-10 version (MCC) |
9.0.0 |
10.0.0 |
|
|
2012-09 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-11 by MCC |
10.0.0 |
11.0.0 |
|
|
2014-10 |
– |
– |
– |
– |
– |
– |
– |
Update to Rel-12 version (MCC) |
11.0.0 |
12.0.0 |
|
|
2015-12 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-13 by MCC |
12.0.0 |
13.0.0 |
|
|
2017-03 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-14 by MCC |
13.0.0 |
14.0.0 |
|
|
2018-06 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-15 by MCC |
14.0.0 |
15.0.0 |
|
|
SA#88e |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-16 by MCC |
15.0.0 |
16.0.0 |
|
|
2022-03 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-17 by MCC |
16.0.0 |
17.0.0 |
|