13 State transition model
23.0933GPPRelease 17Stage 2Technical realization of Completion of Calls to Busy Subscriber (CCBS)TS
13.1 State transition model for the CCBS service in the originating network
Figure 13.1.1 shows the successful cases of transition between the applicable logical states of the CCBS service in the originating network. The state changes may be caused by actions of the service provider or the network.
Figure 13.1.1: State Transition Model for CCBS Service in the originating network
13.2 State transition model for the CCBS service in the destination network
Figure 13.2.1 shows the successful cases of transition between the applicable logical states of the CCBS service in the destination network. The state changes may be caused by actions of the service provider or the network.
Figure 13.2.1: State Transition Model for CCBS Service in the destination network
13.3 State transition model for a CCBS Request
Figure 13.3.1 shows the successful cases of transition between the applicable logical states of a CCBS Request. The state changes may be caused by actions of the served subscriber or the network.
Each subscriber can be considered to have a set of n requests, where n is the maximum number of CCBS requests allowed for a subscriber as an originator.
Figure 13.3.1: State Transition Model for a CCBS Request in Originating Network
On provision of the CCBS service, all requests transit to the "Start" state
Figure 13.3.2: State Transition Model for a CCBS Request in Destination Network
13.4 Information stored in the VLRs
Originating Network Data
For the CCBS service in the originating network the VLR shall store the service state information received from HLR.
Destination Network Data
For the CCBS service in the destination network the VLR shall store the service state information received from HLR.
Annex A (informative):
Message flow diagrams showing a successful CCBS request
The following message flow diagrams show a successful CCBS request. Destination B busy when request activated, subscriber A free when destination B becomes free (mobile-to-mobile).
Annex B (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
Apr 1999 |
Transferred to 3GPP CN1 |
||||||
|
CN#03 |
Approved at CN#03 |
3.0.0 |
|||||
|
CN#06 |
0001 |
3 |
Approved at CN#06 |
3.1.0 |
|||
|
CN#06 |
0002 |
3 |
Approved at CN#06 |
3.1.0 |
|||
|
CN#09 |
0003 |
1 |
Handling of the Call Completion Treatment Indicator |
3.2.0 |
|||
|
CN#09 |
0004 |
Handling of the Call Diversion Treatment Indicator |
3.2.0 |
||||
|
CN#11 |
Release 4 after CN#11 |
4.0.0 |
|||||
|
CN#16 |
Release 5 after CN#16 |
5.0.0 |
|||||
|
CN#26 |
Release 6 after CN#26 |
6.0.0 |
|||||
|
CT#36 |
Upgraded unchanged from Rel-6 |
7.0.0 |
|||||
|
CT#37 |
0005 |
HLR procedure on Location Update from the current VLR |
7.1.0 |
||||
|
CT#37 |
0006 |
Incompatible terminal handling in VLR |
7.1.0 |
||||
|
CT#38 |
0007 |
Call forwarding on busy handling in HLR |
7.2.0 |
||||
|
CT#40 |
0008 |
1 |
Missing signal in process VLR_CCBS_Recall_Manager |
7.3.0 |
|||
|
CT#42 |
Upgraded unchanged from Rel-7 |
8.0.0 |
|||||
|
CT#46 |
– |
Update to Rel-9 version (MCC) |
9.0.0 |
||||
|
2011-03 |
– |
Update to Rel-10 version (MCC) |
10.0.0 |
||||
|
2011-11 |
Editorial correction to previous line in history table |
10.0.1 |
|||||
|
2012-09 |
– |
Update to Rel-11 version (MCC) |
11.0.0 |
||||
|
2014-09 |
– |
Update to Rel-12 version (MCC) |
12.0.0 |
||||
|
2015-12 |
– |
Update to Rel-13 version (MCC) |
13.0.0 |
||||
|
2017-03 |
– |
Update to Rel-14 version (MCC) |
14.0.0 |
||||
|
2018-06 |
– |
Update to Rel-15 version (MCC) |
15.0.0 |
||||
|
2020-07 |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
||||
|
2022-03 |
– |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |