7.2 State Transition Diagrams for IpMultiPartyCall

29.198-04-33GPPOpen Service Access (OSA) Application Programming Interface (API)Part 4: Call controlRelease 9Subpart 3: Multi-party call control Service Capability Feature (SCF)TS

The state transition diagram shows the application view on the MultiParty Call object.

When an IpMultiPartyCall is created using createCall, or when an IpMultiPartyCall is given to the application for a notification with a monitor mode of P_CALL_MONITOR_MODE_INTERRUPT, an activity timer is started. The activity timer is stopped when the application invokes a method on the IpMultiPartyCall. The action upon expiry of this activity timer is to invoke callEnded() on the IpAppMultiPartyCall with a release cause of P_TIMER_EXPIRY. In the case when no IpAppMultiPartyCall is available on which to invoke callEnded(), callAborted() shall be invoked on the IpAppMultiPartyCallControlManager as this is an abnormal termination.

Figure : Application view on the MultiParty Call object

7.2.1 IDLE State

In this state the Call object has no Call Leg object associated to it.

The application can request for charging related information reports, call supervision, set the charge plan and set Advice Of Charge indicators. When the first Call Leg object is requested to be created a state transition is made to the Active state.

7.2.2 ACTIVE State

In this state the Call object has one or more Call Leg objects associated to it. The application is allowed to create additional Call Leg objects.

Furthermore, the application can request for call supervision. The Application can request charging related information reports, set the charge plan and set Advice Of Charge indicators in this state prior to call establishment.

7.2.3 RELEASED State

In this state the last Call leg object has released or the call itself was released. While the call is in this state, the requested call information will be collected and returned through getInfoRes() and / or superviseRes(). As soon as all information is returned, the application will be informed that the call has ended and Call object transition to the end state.

7.2.4 Overview of allowed methods

Methods applicable

Call Control Call State

Call Control Manager State

getCallLegs

Idle, Active, Released

createCallLeg,

createAndRouteCallLegReq, setAdviceOfCharge, superviseReq,

Idle, Active

Active

release

Active

Active

deassignCall

Idle, Active

setChargePlan, getInfoReq

Idle, Active

Active