UMTS Video Call

Simplified Call Setup

Particular steps• MS initiates RR connection and moves to RRC connected state.

• RRC Connection request specifies a cause value ‘originating conversational call’ (the same as for speech connection).

• Mobility Management service CM Service Request is passed to the Core network (the same content as for speech call).

Particular steps• Integrity protection and ciphering are enabled during Security Mode procedure.

• Setup message is sent, this time indicating request for video connection, not speech.

SEE attached exemplary message

Setup message incl. bearer capability

Bearer capability information.

Particular steps• Setup message is confirmed by the Core Network with Call Proceeding message.

• Core network contacts the terminating UE.

• UE is paged (the same like in speech call).

• Upon response RR Connection is setup.

• Paging response follows (the same like in speech call).

• Security procedures are performed

Particular steps• Setup message is sent to the terminating UE indicating Video Call not speech (including parameters of the connection like codecs).

• Setup message is acknowledged by Call Confirmed.

• Radio Access Bearer is setup by the Core Network including proper QoS parameters.

• Alerting follows.• Finally call is connected.

GCP RANAP interworking – support mode

GCP RANAP interworking – transparent mode

Support vs Transparent mode.• CS speech is framed with an IuUP header of 4 bytes and CS data in IuUP support mode with an IuUP header of 3 bytes.

• Transport of CS data in IuUP transparent mode does not carry an IuUP header.

1) UE 2 releases the voice call.2) MSC 2 sends a RELEASE message with the release cause.

3) MSC 1 sends a RELEASE COMPLETE message to MSC 2.

4) MSC 1 releases the voice call with UE 1.

5) MSC 2 and MSC 1 locally release the Iu connections to RNC 2 and RNC 1 (assuming that there are no other CM connections active). RNC 2 and RNC 1 then release the RRC connections (assuming that their mobiles are not in PMM connected state).

6) UE 2 and UE 1 camp on suitable cells and perform the required idle mode tasks.

7) UE 2 initiates RRC connection setup and sends the Setup message for the video call to MSC 2. The Called Party number is the one stored in step 0. The Setup message should carry extra information to indicate that it is the result of a redial attempt.

8) MSC 2 requests the allocation of radio resources.

9) If radio resource allocation was successful, the IAM message is sent to MSC 1 and the Call Proceeding message is sent to UE 2.

10) MSC 1 pages UE 1. UE 1 responds by establishing an RRC connection and sending the Paging Response message to MSC 1 within the RRC-Initial Direct Transfer and RANAP-Initial UE messages. MSC 1 then sends the Setup message for the video call to UE 1. The Setup message carries the CLI of UE 2.

11) UE 1 confirms its capability to handle the video call in the Call Confirmed message and MSC 1 requests the allocation of radio resources.

12) If the radio resource allocation was successful, UE 1 sends an Alerting message to MSC 1. MSC 1 sends the ACM message to MSC 2 and MSC 2 sends the Alerting message to UE 2.

13) User 1 answers the video call. For privacy reasons, the 'switch to video' and 'switch to voice' answer functions should not be automated.

14) The video call is established.

Temporary Master CP & Leader CP

SIS

eth eth eth

APZ VLAN ISOS VLAN

Temporary master CP

Faulty CP

Leader CP

Active BSOM

Active BSOM• When PLEX and MAS start, MAS decides which CP blade that must act as active BSOM, and it will be the one that is the Leader CP, i.e. the Leader CP act as the active BSOM. R14.0

• The role of the Active BSOM can be taken by any CP blade and is assigned dynamically by APZ. R14.1

Definition of new user in APGC:\APG> net user name passwd /add C:\APG> net localgroup EXPERTG name /addOther groups to be added : MCSADMG, MCSUSRG, ACSADMG, ACSUSRG, CPADMG

• MCSADMG - Members of this group are allowed to use most MCS commands, except the commands that handle the CP–APG43 profile assignments .

• MCSUSRG - Members of this group are able to use non-changing MCS print commands in the AP.

Definition of Command Authority Profile.capdef -c coca ... cap- c coca ... Command category group This option specifies a list of Command Category (COCA) groups. The COCA group specifies the functional group that a particular Man-Machine Language (MML) command belongs to.

- cap AP group This operand specifies the name of an existing Adjunct Processor (AP) local group. The AP local group is a Microsoft Windows user group.

• In the following example, the AP local group USERG is associated to COCA groups 0 and 32 to 59.

capdef -c 0,32-59 USERG