6.10.2

6.10.2.1

ASP function description

Identities
Within the SS, a cell is identified by cell identifier (cellId), which is of TTCN type CellId (INTEGER). Within a cell, a basic physical channel is identified by physical channel identifier (physicalChId), which is of TTCN type PhysicalChId (INTEGER). In multislot configuration a basic physical channel is identified by physical channel identifier (physicalChId) and timeslot, which is of TTCN type TN (INTEGER). Within a physical channel, logical channel is identified by logical channel type (g_LogicChType), which is of TTCN type G_LogicChType (INTEGER). When multiple logical channels of same type are carried by (mapped to) the same basic physical channel, they are differentiated by sub-channel number (subChannel), which is of TTCN type SubChannelNumber (INTEGER). At the top boundary of L2 emulation module two service access points (SAP) are available, they are identified by SAPI. SAPI=3 is used for short message service; SAPI=0 is used for L3 signalling messages and user data. EXAMPLE: If G_L2_DATA_REQ ASP has the following parameter setting: cellId = tsc_CellA; sAPI = tsc_SAPI_0; physicalChId = tsc_PhyCh0; g_LogicChType = tsc_SDCCH4; and sunChannel = tsc_SubChannel1;
it sends PDU on the SDCCH4(1) logical channel which is carried by the physical channel tsc_PhyCh0 in cell A.

6.10.2.2

Cell configuration and control
In GSM each base station has a base station identity code BSIC, it consists of network colour code and base station colour code (NCC + BCC). BSIC is continuously broadcasted on the SCH channel, and it shall be used as the training sequence code for broadcast and common control channels. In the test model the function of G_CL1_CreateCell_REQ ASP is to create a cell and pass parameter BSIC to it. This ASP establishes the cell identifier which shall be used in the ASP's related to this cell. This is the first step to configure L1 (GERAN) emulation module of the SS.

6.10.2.3

L1 (GERAN) configuration and control
Configuration and control functions identified for L1 (GERAN) of a cell are: creation of basic physical channels; creation of multislot configuration; release of basic physical channel; modifications of channel mode, ciphering parameters and transmission power level; reporting of L1 header of SACCH channel; pickup a frame in near future, which can carry L3 message.

6.10.2.3.1

Basic physical channel configuration
A basic physical channel uses a combination of frequency and time domain resources, therefore, the definition of a particular basic physical channel consists of a description in the frequency domain and a description in the time domain. In time domain the resource is called Time Slot, there are 8 time slots in one frame, numbered from 0 to 7. In frequency domain a basic physical channel may use only one frequency or may use multiple frequencies in frequency hopping. Basic physical channel carrying FCCH + SCH + BCCH + CCCH (PCH, AGCH, RACH) or FCCH + SCH + BCCH + CCCH + SDCCH4 logical channels shall be located in time slot 0, and uses single frequency (non-hopping). The basic physical channel carrying additional BCCH, CCCH (PCH, AGCH, RACH) logical channels shall be located in time slot 2, 4, 6 and uses the same single frequency as the frequency used by the physical channel carrying FCCH, SCH. GSM specification defines 24 permitted combinations of different logical channels, which can be mapped on to a basic physical channel. The combination defines which logical channels are carried by a basic physical channel, and it is also an indication of which modulation (GMSK or 8PSK) is used for the basic physical channel. Training Sequence Code (TSC) is another parameter needed by physical channel. Common control and broadcast channel have to use BCC as its TSC. Dedicated control channel and dedicated traffic channel need more parameters to configure. Parameter "Channel Mode" is needed to specify channel coding (therefore the user data rate). Ciphering related parameters are required to define the ciphering behaviour of the channel. Common control channels need parameters to configure where in the 51-multiframe paging and access grant blocks are located. Transmission power level is provided as per physical channel parameter, power level of each physical channel can be controlled independently. The function of ASP G_CL1_CreateBasicPhyCh_REQ is to create a basic physical channel which has the required property defined by all the parameters mentioned above. In the process of L1 (GERAN) configuration, calling the ASP is the next step after calling G_CL1_CreateCell_REQ.

6.10.2.3.2

Multislot configuration for circuit or packet switched channels
Multislot configuration for circuit switched connection consists of multiple circuit switched traffic channels, in L1 point of view these traffic channels are independent basic physical channels with the same frequency parameters (ARFCN or MA, MAIO, HSN) and the same training sequence code but located in different time slots, one of the basic physical channels is the main channel of the configuration carrying the main signalling (FACCH, SACCH, IACCH) for the configuration. The main channel shall be bi-directional channel and with channelCombanition TCH/F+FACCH/F+SACCH/M or E-TCH/F+E-IACCH/F+E-FACCH/F+E-SACCH/M. When transmitting user data (not signalling message) stream is divided into substreams, each substream is transmitted independently on a channel in the configuration. At the receiving side all substreams are combined back to user stream. According to the test model creation of a multislot configuration for circuit switched connection needs two ASP calls. Firstly, G_L1_CreatedBasicPhyCh_REQ is called to establish the main channel, then G_L1_CreateMultiSlotConfig_REQ is called to allocate more timeslots to the channel established by the previous ASP. A substream of a multislot configuration is identified with the physicalChId and timeslot. Multislot configuration for packet switched connection consists of multiple PDCHs which can carry PDTCH/Us or PDTCH/Ds. All these PDCHs use the same frequency parameters (ARFCN or MA, MAIO, HSN) and the same training sequence code, but are located on different timeslots. Similarly, a multislot configuration for packet switched connection is created with two ASP calls. First G_L1_CreatedBasicPhyCh_REQ is called to establish the first PDCH channel, then G_L1_CreateMultiSlotConfig_REQ is called to allocate more timeslots to the channel established by the previous ASP. All data ASP on packet data channel use physicalChId and timeslot to address the physical channels.

6.10.2.3.3

Frame in the near future
ASP G_CL1_ComingFN_REQ is defined to request L1 (GERAN) return the reduced frame number (FN modulo 42432) which is far enough in the future from current frame number and is able to carry L3 message on the specified channel. "far enough" means that there is enough time left for TTCN to prepare a L3 message to be sent on that frame. When calculating startingTime, this ASP could be useful. The starting time usually is set to a frame number in a time distance from current frame number. TTCN writer can use G_CL1_ComingFN_REQ to get a frame number in the future then add a certain number of frames as time distance to it and use the result as the value for startingTime.

ASN.1 Type Definition SS_MAC_hs_AddReconfQueue Applicable Rel-5 or later The priority of PriorityQueue shall set acoording to the priority of logical channels which is mapped on to this priority queue. Note: the range of priority of PriorityQueue is from 0 to 7 and 0 is the lowest priority. DiscardTimer defines the time (unit ms) to live for a MAC-hs SDU starting from the instant of its arrival into an HSDPA Priority Queue. The SS shall use this information to discard out-of-data MAC-hs SDUs from the HSDPA Priority Queues. Type Definition
SEQUENCE { mAChsAddReconfQueue logicalChannelList
MAC_hs_AddReconfQueue, SEQUENCE OF LogicalChannelIdentity, -- logical channels mapping onto the priority queue -- which is specified in maChsAddReconfQueue priority INTEGER(0.7), discardTimer ENUMERATED { v20(0),v40(1),v60(2),v80(3),v100(4),v120(5),v140(6),v160(7),v180(8),v200(9), v250(10),v300(11),v400(12),v500(13),v750(14),v1000(15),v1250(16),v1500(17),v1750(18),v20 00(19),v2500(20),v3000(21), v3500(22),v4000(23),v4500(24),v5000(25), v7500(26) } OPTIONAL }

7.3.2.2.14a

CPHY_ UL_PowerModify
ASN.1 ASP Type Definition CPHY_UL_PowerModify_CNF CSAP To confirm the increase/decrease in UE uplink DPCH power transmission or send the TPC commands as instructed. Type Definition
ASN.1 ASP Type Definition CPHY_UL_PowerModify_REQ CSAP To request increase/decrease in the UE uplink DPCH transmission by the delta value given in dB, from the existing transmission level or make UE to transmit at maximum or minimum power level. It is assumed that the UE UL DPCH transmission power level is set to -20dbm by default at beginning of each test. For routing Info the Dl DPCH Physical channel ID shall be used. For IE ul_DPCH_Id, the physical channel ID of associated UL DPCH shall be given. SS can use it or neglect it. Ul_UE_TxPower gives either the value in dB, by which SS shall increase/decrease the uplink transmission power of UE from the existing transmission power, when this primitive is called or Start transmission of TPC commands on DL DPCCH as configured Type Definition
INTEGER(0.63), RoutingInfo, INTEGER(0.31), Ul_UE_Tx_Power
{ cellId routingInfo ul_DPCH_Id ul_UE_Tx_Power
ASN.1 Type Definition Ul_UE_Tx_Power Choice delta gives the value in dB, by which the existing UE UL DPCH transmission power level is to be increased or decreased. After reaching the new desired level SS shall make UE to maintain this new transmission power level. WithChoice maxMin, and ENUM 'tpc_Up' selection, SS shall start transmitting TPC commands on the DL DPCCH, as '1' every slot so as to ask UE to increase the transmission power. With Choice maxMin, and ENUM 'tpc_Down' selection, SS shall start transmitting TPC commands on the DL DPCCH, as '0' every slot so as to ask UE to decrease the transmission power. With Choice maxMin, and ENUM 'tpc_Maintain' selection, SS will start transmitting TPC commands on the DL DPCCH, as alternate '0' and '1' in alternate slots so as to maintain the UE uplink transmission power Type Definition

INTEGER(-1.63), RoutingInfo, RatType, CN_DomainIdentity, CipheringModeInfo,
SEQUENCE { cellId routingInfo ratType cn_DomainIdentity cipheringModeInfo incHFN Increment Mode }
ASN.1 Type Definition Increment_Mode Type Definition
ENUMERATED {incPerCFN_Cycler(0), notInc(1), incByOne_IncPerCFN_Cycle(2)}

7.3.2.2.17

CMAC_Config
ASN.1 ASP Type Definition CMAC_Config_CNF CSAP For MAC emulator to report that a previous attempt to setup, reconfigure or release a logical channel is successful. Type Definition
cellId routingInfo INTEGER(-1.63), RoutingInfo
ASN.1 ASP Type Definition CMAC_Config_REQ CSAP To request to configure MAC entity. Setup is used for creation of the MAC instances or the MAC resources. Release is used for free the all MAC resources. The reconfiguration is to change the MAC parameters, it is not the MAC modification. Type Definition
INTEGER(-1.63), RoutingInfo, RatType, CHOICE { CmacConfigReq, CmacConfigReq, NULL
{ cellId routingInfo ratType configMessage setup reconfigure release }
ASN.1 Type Definition CmacConfigReq To request to configure MAC Type Definition
SS_ActivationTime, UE_Info, TrCHInfo, TrCH_LogCHMappingList1 TBD, TBD
{ activationTime uE_Info trCHInfo trCH_LogCHMapping -- RACHTrasmissionCtrolElements -- CPCHTransmissionControlElements
ASN.1 Type Definition UE_Info The value of c_RNTI_DSCH_RNTI is 16 bits, used either for C-RNTI or DSCH-RNTI. DSCH is configured if the physical channel in CMAC_config_REQ is a PDSCH. Otherwise, C-RNTI is applied. At the MAC-hs configuration both u_RNTI and c_RNTI_DSCH_RNTI are omitted. Type Definition
U_RNTI C_RNTI OPTIONAL, OPTIONAL
SEQUENCE { u_RNTI c_RNTI_DSCH_RNTI }
ASN.1 Type Definition TrCH_LogCHMappingList1 maxulTrCH = maxdlTrCH = 16 Type Definition
SEQUENCE { ulconnectedTrCHList SEQUENCE (SIZE (1.maxulTrCH)) OF SEQUENCE { trchid TransportChannelIdentity, trCH_LogCHMappingList TrCH_LogCHMappingList } OPTIONAL, dlconnectedTrCHList SEQUENCE (SIZE (1.maxdlTrCH)) OF SEQUENCE { trchid TransportChannelIdentity, trCH_LogCHMappingList TrCH_LogCHMappingList } OPTIONAL, dlconnectedMACdFlows SEQUENCE (SIZE (1.8)) OF SEQUENCE { mac_dFlowId MAC_d_FlowIdentity, trCH_LogCHMappingList TrCH_LogCHMappingList } OPTIONAL -- Rel-5 or later }
ASN.1 Type Definition TrCH_LogCHMappingList maxLogCHperTrCH = 15 Type Definition
TrCH_LogicalChannelMapping
SEQUENCE (SIZE (1.maxLogCHperTrCH)) OF
ASN.1 Type Definition TrCHInfo The same TFCS information should be provided to the PHY and MAC layers at all times. When a CMAC_Config_REQ is used to configure the MAC layer, a corresponding CPHY_TrCH_Config_REQ should be sent to the PHY layer to ensure that the configuration is consistent. For MAC-hs configuration: When ulconnectedTrCHList, ulTFCS, dlconnectedTrCHList and dlTFCS are omitted this ASP configures an MAC-hs entity. Type Definition

Table 53: Downlink configuration of Cell_FACH_BMC
RB Identity LogCh Type LogCh Identity RLC AM mode MAC 1 priority TrCH FACH Type TrCH tsc_FACH2 identity (14) PhyCh Type PhyCH identity tsc_RB0 tsc_RB1 tsc_RB2 tsc_RB3 tsc_RB4 (0) (1) (2) (3) (4) CCCH tsc_DL_ CCCH5 (5) UM 1 DCCH tsc_DL_ DCCH1 (1) UM 2 DCCH tsc_DL_ DCCH2 (2) AM 3 DCCH tsc_DL_ DCCH3 (3) AM 4 FACH tsc_FACH1 (13) Secondary CCPCH tsc_S_CCPCH1 (5) DCCH tsc_DL_ DCCH4 (4) AM 5 tsc_RB_BCC H_FACH (-3) BCCH tsc_BCCH6 (6) TM 6 Tsc_RB30 (30) CTCH Tsc_CTCH (11) UM 7 tsc_RB_PCCH (-2) PCCH tsc_PCCH1 (1) TM 1 PCH tsc_PCH1 (12)
Configuration of PS Cell_DCH_64kPS_RAB_SRB and Cell_PDCP_AM_RAB
The configuration is based on 3GPP TS 34.108 [3], clause 6.10.2.4.1.26. The RB0/UM-CCCH is referred to 3GPP TS 34.108 [3], clause 6.10.2.4.3.2.1.2 and RB0/TM-CCCH is referred to 3GPP TS 34.108 [3], clause 6.10.2.4.4.1.1.1. The configuration is applied to those RRC and NAS signalling tests in the DCH state where a PS RAB on DTCH is setup for the interactive or background service class. The configuration is applied to PDCP test cases in acknowledge mode. Table 54: Uplink configuration of PS Cell_DCH_64kPS_RAB_SRB SRB and Cell_PDCP_AM_RAB
tsc_RB20 (20) LogCh Type DTCH tsc_UL_DTC LogCh H1 Identity (7) RLC mode AM TrCH Type DCH tsc_UL_DCH TrCH identity 1 (1) PhyCh Type PhyCH identity RB Identity
Same as uplink configuration of Cell_DCH_StandAloneSRB on DPCH
Table 55: Downlink configuration of PS Cell_DCH_64kPS_RAB_SRB SRB and Cell_PDCP_AM_RAB
RB Identity LogCh Type LogCh Identity RLC mode MAC priority TrCH Type TrCH identity PhyCh Type PhyCH identity tsc_RB20 (20) DTCH tsc_DL_DTC H1 (7) AM 1 DCH tsc_DL_DCH 1 (6) DPCH tsc_DL_DPCH1 (26) Secondary CCPCH tsc_S_CCPCH1 (5)
Configuration of Cell_Two_DTCH
The configuration is based on 3GPP TS 34.108 [3], clauses 6.10.2.4.1.6 to 6.10.2.4.1.11. The RB0/UM-CCCH is referred to 3GPP TS 34.108 [3], clause 6.10.2.4.3.2.1.2 and RB0/TM-CCCH is referred to 3GPP TS 34.108 [3], clause 6.10.2.4.4.1.1.1. The configuration is applied to RB tests. Table 56: Uplink configuration of Cell_Two_DTCH
tsc_RB10 tsc_RB11 (10) (11) LogCh Type DTCH DTCH tsc_UL_DTCH tsc_UL_DTCH LogCh Same as uplink configuration of Identity Cell_DCH_StandAloneSRB on DPCH (7) (8) RLC mode TM TM TrCH Type DCH DCH TrCH tsc_UL_DCH1 tsc_UL_DCH2 identity (1) (2) PhyCh Type DPCH PhyCH tsc_UL_DPDCH1 identity (20) RB Identity
Table 57: Downlink configuration of Cell_Two_DTCH
tsc_RB10 tsc_RB11 (10) (11) LogCh Type DTCH DTCH tsc_DL_DTCH1 tsc_DL_DTCH2 LogCh Identity Same as downlink configuration of (7) (8) Cell_DCH_StandAloneSRB on RLC mode TM TM DPCH MAC priority TrCH Type DCH DCH tsc_DL_DCH1 tsc_DL_DCH2 TrCH identity (6) (7) PhyCh Type DPCH tsc_DL_DPCH1 PhyCH identity (26) RB Identity

Test SIB default schedule

Table 114

Frame No. REP-POS Block Type Frame No. REP-POS Block Type Frame No. REP-POS Block Type Frame No. REP-POS Block Type

MIB MIB MIB MIB

SB9 SB17 SB25 SB1
SIB10 SIB7/SIB18 SIB7/SIBSIB7/SIB4

SIB11 SIB1/SIB 19 SIB27

- (FDD) SIB5(LCR TDD)

SIB13 SIB21 SIB29 SIB11

SIB14 SIB22 SIB30 SIB11

SIB15 SIB23 SIB31 SIB11

SIB-repeat period (in frame) Table 115
Block Type SIB Rep Max. No of seg. MIB SB1 SIB1 SIB1 SIB1 SIB1 SIB4(FDD)

5(LCR TDD)

8.4.3.1
Test SIB schedule for idle mode, measurement and Inter-RAT UTRAN to GERAN test cases

Table 116

SIB10 SIB1/SIB18 SIB26 SIB11

SIB11 SIB19 SIB27 SIB11

SIB7/SIB 15 SIB7/SIB 23 SIB7/SIB 31 SIB7/SIB 4
SIB-repeat period (in frame)

Table 117

Block Type SIB Rep Max. No of seg. MIB SB1 SIB1 SIB1 SIB1 SIB1 SIB5 SIB6 SIB1 SIB4 SIB4 SIB1

4(FDD) 4(FDD)

5(LCR TDD) 3(LCR TDD)

8.4.4.1

Test SIB special schedule
Test SIB schedule for two S-CCPCH or two PRACH

Table 118

Frame No. REP-POS Block Type Frame No. REP-POS Block Type Frame No. REP-POS Block Type Frame No. REP-POS Block Type Frame No. REP-POS Block Type Frame No. REP-POS Block Type Frame No. REP-POS Block Type Frame No. REP-POS Block Type MIB MIB MIB MIB MIB MIB MIB MIB SB9 SB17 SB25 SB33 SB41 SB49 SB57 SB2 SB10 SB18 SB26 SB34 SB42 SB50 SB58 SB4 MIB MIB MIB MIB MIB MIB MIB MIB SIB13 SIB21 SIB29 SIB37 SIB45 SIB6 SIB7 SIB15 SIB23 SIB31 SIB39 SIB47 SIB55
SIB19 SIB27 SIB35 SIB43 SIB51

SIB30 SIB38 SIB46

108 54
SIB-repeat period (in frame) Table 119
Block Type SIB Rep Max. No of seg. MIB SB2 SIB1 SIB1 SIB1 SIB1 SIB8 SIB1 SIB3 SIB3 SIB1

8.4.4.2

Test SIB schedule for Inter-Rat Handover from GERAN to UTRAN Test

Table 120

Frame No. REP-POS Block Type Frame No. REP-POS Block Type Frame No. REP-POS Block Type Frame No. REP-POS Block Type Frame No. REP-POS Block Type Frame No. REP-POS Block Type Frame No. REP-POS Block Type Frame No. REP-POS Block Type

8.5.4.2.1.2

Ciphering started
CIPHERING_STATUS = Started for the CN domain concerned CRLC_SecurityMode_Config_REQ startValue = value most recently received cipheringKey = value maintained by TTCN cn_DomainIdentity = CS or PS CRLC_Ciphering_Activate_REQ (CN domain concerned) cipheringModeCommand = Start/Restart (algorithm) rb_DL_CiphActivationTimeInfo = 0 (from the first block) incHFN = NotInc CRLC_Ciphering_Activate_REQ (CN domain concerned) rb_UL_CipheringActivationTimeInfo = 0 (from the first block) incHFN = NotInc

8.5.4.2.2

Enter Cell_DCH, no TM RB established before, "COUNT-C activation time" IE included in RADIO BEARER SETUP COMPLETE message.

8.5.4.2.2.1

Ciphering not started
CIPHERING_STATUS = NotStarted for the CN domain concerned,
1 Send the RADIO BEARER SETUP message 2 Configuring the RB 3 After receiving RADIO BEARER SETUP COMPLETE
CMAC_SecurityMode_Config_REQ startValue = value most recently received cn_DomainIdentity = CS or PS CMAC_Ciphering_Activate_REQ (CN domain concerned) incHFN = NotInc cipheringModeCommand = NULL (no ciphering) activationTimeForDPCH = value in "COUNT-C activation time"

8.5.4.2.2.2

CIPHERING_STATUS = Started for the CN domain concerned,
1 Sending RADIO BEARER SETUP 2 Configuring the RB
CMAC_SecurityMode_Config_REQ startValue = value most recently received cipheringKey = value maintained by TTCN cn_DomainIdentity = CS or PS CMAC_Ciphering_Activate_REQ (CN domain concerned) incHFN = NotInc cipheringModeCommand = Start/Restart (algorithm) activationTimeForDPCH = value in "Activation time" of the RB
3 After receiving RADIO BEARER SETUP COMPLETE message
CMAC_SecurityMode_Config_REQ startValue = value received in response message cipheringKey = value maintained by TTCN cn_DomainIdentity = CS or PS CMAC_Ciphering_Activate_REQ (CN domain concerned) incHFN = IncPerCFN_Cycle cipheringModeCommand = Start/Restart (algorithm) activationTimeForDPCH = value in "COUNT-C activation time"

8.5.4.3

RB Reconfiguration for AM RAB modification of RLC size
CIPHERING_STATUS = Started for the CN domain concerned, "RB mapping info" IE, changeing AM RB RLC size, is included in CELL UPDATE CONFIRM, RADIO REARER RECONFIGURATION, RADIO BEARER RELEASE

8.5.4.3.1

"RB mapping info" in CELL UPDATE CONFIRM

After sending the CELL UPDATE CONFIRM message, re-establish the RB and re-configure the RB with new RLC size and re-initialize COUNT-C for the RB:
CRLC_Config_REQ Release the concerned RB CRLC_Config_REQ Setup the concerned RB (new RLC size) CRLC_SecurityMode_Config_REQ startValue = value received in the CELL UPDATE message integrityKey = value maintained by TTCN cn_DomainIdentity = CS or PS CRLC_Ciphering_Activate_REQ cipheringModeCommand = Start/Restart (existing algorithm) rb_DL_CiphActivationTimeInfo = now incHFN = NotInc CRLC_ Ciphering_Activate_REQ rb_UL_CiphActivationTimeInfo = now incHFN = NotInc

8.5.4.3.2

"RB mapping info" in RB RECONFIGURATION / RELEASE
After receiving the reconfiguration complete message, re-establish the RB and re-configure the RB with new RLC size and re-initialize COUNT-C for the RB:
CRLC_Config_REQ Release the concerned RB CRLC_Config_REQ Setup the concerned RB (new RLC size) CRLC_SecurityMode_Config_REQ startValue = value received in the reconfiguration complete message integrityKey = value maintained by TTCN cn_DomainIdentity = CS or PS CRLC_Ciphering_Activate_REQ cipheringModeCommand = Start/Restart (existing algorithm) rb_DL_CiphActivationTimeInfo = now incHFN = NotInc CRLC_Ciphering_Activate_REQ rb_UL_CiphActivationTimeInfo = now incHFN = NotInc

8.5.4.4

Security modification
Updating security keys is the scenario in this clause.
INTEGRITY_PROTECTION STATUS = Started SECURITY MODE COMMAND contains "Ciphering mode info" IE and/or "Integrity protection mode info" IE

8.5.4.4.1

Integrity started, ciphering not started
CIPHERING_STATUS = NotStarted for the CN domain concerned SECURITY MODE COMMAND with "Integrity protection mode info" IE containing integrityProtectionModeCommand = modify, but "Ciphering mode info" IE absent the same CN domain as in the previous SMC to start integrity protection.
CRLC_SecurityMode_Config_REQ startValue = 0 (new key) integrityKey = new key cn_DomainIdentity = CS or PS CRLC_RRC_MessageSN_REQ -- Get current RRC Message SN for calculation of DL activation time CRLC_Integrity_Activate_REQ (CN domain concerned) integrityProtectionModeCommand = modify dl_IntegrityProtActivationInfo = now (SRB2), calculated value or a pending activation time set by previous security mode control procedure (SRB2 other than SRB2) CRLC_Integrity_Activate_REQ (CN domain concerned, RB2) ul_IntegrityProtActivationInfo = now

USIM field Priority PLMN Access Technology Identifier UTRAN

EFLOCI EFPLMNwAcT

PLMN 3
Test USIM is configured as below for emergency calls in TC_6_1_2_6. Table 114a
USIM field EFLOCI EFFPLMN Priority PLMN 3 PLMN PLMN1
Test USIMs are configured as bellow for Selection of the correct PLMN and associated RAT in TC_6_2_1_1. Two test USIMs are needed for the test. Table 126: USIM A
USIM field EFLOCI EFHPLMNwAcT EFHPLMNwAcT Priority
Access Technology Identifier GSM UTRAN

1 nd 2

Table 127: USIM B
USIM field EFLOCI EFHPLMNwAcT Priority
Access Technology Identifier UTRAN GSM
Test USIMs are configured as bellow for Selection of RAT for HPLMN in TC_6_2_1_2. Two test USIMs are needed for the test. Table 128: USIM A

PLMN PLMN 1

Table 129: USIM B
Access Technology Identifier UTRAN
Test USIMs are configured as bellow for Selection of RAT for HPLMN in TC_6_2_1_6. Two test USIMs are needed for the test. Table 128a: USIM A
USIM field EFLOCI EFHPLMNwAcT EFPLMNwAcT Priority
Access Technology Identifier UTRAN GSM UTRAN

1 nd 2 st 1

Table 129a: USIM B
Test USIM for Selection of RAT for UPLMN or OPLMN in TC_6_2_1_3, TC_6_2_1_4, TC_6_2_1_7, TC_6_2_1_8 and for Selection of Other PLMN with access technology combinations"; Automatic mode in TC_6_2_1_9. Table 130
USIM field EFLOCI EFHPLMNwAcT EFPLMNwAcT EFOPLMNwAcT Priority
Access Technology Identifier UTRAN GSM UTRAN GSM UTRAN GSM
1 nd 2 st 1 nd 2 st 1 nd 2
PLMN 3 PLMN 4 PLMN 5 PLMN 6
Test USIM are configured as bellow for manual selection of other PLMN with access technology combinations in TC_6_2_1_5. Table 131

EFLOCI EFFPLMN

PLMN 7 PLMN 8 PLMN 9
Test USIM for cell reselection if cell becomes barred or for cell reselection timings requires that the USIM does not contain any preferred RAT. This specific test USIM applies to TC_6_2_2_1, TC_6_2_2_2 and TC_6_2_2_3.
Downlink power setting in SS
Refer to 3GPP TS 34.108 [3] clause 6.1.5.
Test suite operation definitions
Test suite operation definitions in the module BasicM
Table 132: TSO definitions in BasicM
Description Type of the result: BOOLEAN Parameters: p_AuthRsp : AuthRsp p_AuthRspExt : AuthRspExt p_K : BITSTRING p_RAND : BITSTRING p_Ext : BOOLEAN Description Checks the input parameter p_AuthRsp and p_AuthRspExt, both received in an Authentication Response, according to the authentication algorithm defined in the following procedure. The extension, p_AuthRspExt, is optional. Its presence is indicated by p_Ext. Returns TRUE if the Authentication Response contained in parameters p_AuthRsp and eventually p_AuthRspExt is correct, FALSE otherwise. The value of tcv_Auth_n indicates whether the AuthRspExt has been provided by the UE or not (n=31, or 31 < n < 128). See 3GPP TS 34.108 [3] clause 8.1.2. If not the parameter p_AuthRspExt is not to be used. Algorithm (without the knowledge of tcv_Auth_n): ========================================= if NOT p_Ext EvaluateAuthRsp else EvaluateAuthRspAndAuthRspExt EvaluateAuthRsp: ============== resultbitstring = o_BitstringXOR(XRES, AuthRsp) if resultbitstring is all 0s then there is a match. EvaluateAuthRspAndAuthRspExt: ============================ XREShigh = o_BitstringXtract(XRES, 32, 32, 0) /* XRES divides into 2 parts: the higher part of 32 bits related to AuthRsp and the lower part related to AuthRspExt \*/ /* SourceLength of 32 is only to ensure usage of the procedure \*/ resultbitstring = o_BitstringXOR(XREShigh, AuthRsp) if resultbitstring is all 0s then there is a match for the first 32 bits:EvaluateAuthRspExt else Authentication failed. EvaluateAuthRspExt: ================= /* As AuthRespExt may not be octet aligned the last octet indicated in AuthRspExt is not used for checking \*/ if (AuthRspExt.iel = 1) then Authentication passed /* there was only 1 possibly incomplete octet which is not used \*/ else { AuthRspExthigh = o_BitstringXtract(AuthRspExt.authRsp, ((AuthRspExt.iel -1)* 8), (AuthRspExt.iel -1)* 8, 0) /* extract (AuthRspExt.iel -1)* 8 bits starting from bit 0 \*/ XRESlow = o_BitstringXtract(XRES, ((AuthRspExt.iel -1)* 8 + 32), (AuthRspExt.iel -1)* 8, 32) /* extract (AuthRspExt.iel -1)* 8 bits starting from bit 32 \*/ resultbitstring = o_BitstringXOR(XRESlow, AuthRspExthigh, (AuthRspExt.iel -1)* 8) if resultbitstring is all 0s then there is a match for the bits following the first 32 bits else Authentication failed

o_BitstringXtract
3GPP TS 34.123-3 version 5.2.0 Release 5 TSO Name o_BMC_DrxScheduling
Description Type of the result: BMC_ResultOfSchedulingLevel2 Parameters: p_BMC_CBS_Message1 : BMCCBSMESSAGE p_BMC_CBS_Message2 : BMCCBSMESSAGE p_BMC_CB_RepPeriod : INTEGER p_BMC_NoOfBroadcast_Req : INTEGER p_Offset : BMC_DRX_Offset Description This TSO shall calculate all BMC CBS schedule Messages for the CBS messages as described in 3GPP TS 34.123-1, clause 7.4.3.1. The TSO has to precalculate the CTCH Block SETs needed, i.e. it shall have all necessary knowledge (RLC segmentation, MAC handling, if needed) to predict the CTCH with BMC contents for the given input to be sent. The TSO shall consider the BMC CBS Scheduling Level2 as described in 3GPP TS 25.324 [20], 3GPP TR 25.925 [44] and the description of BMC test architecture and test method in the present document, clause 6.8. The TSO calculates the BMC CBS Schedule messages to predict its next BlockSet to be sent. In addition, a DRX scheduling Bitmap is created for each CTCH allocated TTI aligned to the pre-calculated offset in between 2 CTCH Block Sets. The principle of DRX shall be followed by this TSO. I.e. BMC Messages shall be sent blockwise (CTCH Block Set) with predicted offset in between 2 Block Sets. The TSO shall consider the following aspects to calculate the DRX Selection Bitmap and to create the BMC CBS Schedule messages: 1. The first CTCH Block Set consists of the first BMC CBS Schedule message predicting the offset, length and content of the following Block Set where the BMC CBS Message1 shall be send as new message. 2. The BMC CBS Message1 shall be repeated for p_BMC_CB_RepPeriod multiplied by p_BMC_NoOfBroadcast_Req times before the BMC CBS Message2 is broadcasted. 3. The BMC CBS Schedule Messages shall be the last message of a CTCH Block Set, i.e. on the end of a Block Set. 4. If no further repetition of BMC CBS Messages is needed, no further BMC CBS Schedule message shall be created. output parameter: DrxSelectionBitmap: The TSO creates a Bitmap as Octetstring for scheduled CTCH allocated TTI as described in 3GPP TS 34.123-3: clause 6.8.2 BMC test method and architecture. CBS_Schedule_Message01, CBS_Schedule_Message02, CBS_Schedule_Message03:Considering the given BMC PDUs BMC_DRX_Offset and BMCCBSMESSAGE to be sent, the BMC Schedule messages have to be created according the given parameter. Type of the result: BOOLEAN Parameters: p_SourceString: IA5String p_StartString : IA5String Description o_CheckStringStartWith returns TRUE if the p_sourceString start with the p_StartString. Otherwise it returns FALSE. EXAMPLE: o_CheckStringStartWith ("+CLCC:1,0,0,2,0;", "+CLCC:1,0,0")=TRUE */.

o_CheckStringStartWith

3GPP TS 34.123-3 version 5.2.0 Release 5 TSO Name o_ComputeSM_Contents

237 Description

o_SecondDigit
Description Calculate the PAGING_GROUP (0. N?1) = ((IMSI mod 1000) mod (BS_CC_CHANS x N)) mod N where : N = number of paging blocks "available" on one CCCH = (number of paging blocks "available" in a 51-multiframe on one CCCH) x BS_PA_MFRMS. IMSI = International Mobile Subscriber Identity, as defined in 3GPP TS 23.003 [6]. mod = Modulo. div = Integer division. Type of the result: B4 Parameters: p_digits : HEXSTRING Description The input parameter bcddigits shall be a BCD string (subset of HEXSTRING) except the third digit can take value 'F'H, the result is a BITSTRING[4] of a binary representation of one digit in the input string. The function of the o_SecondDigit is to return the second digit of the input parameter p_digits. EXAMPLE 1: o_G_FirstDigit('123') = '0010'B. EXAMPLE 2: o_G_FirstDigit('01F') = '0001'B. Type of the result: B4 Parameters: p_digits : HEXSTRING Description The input parameter bcddigits shall be a BCD string (subset of HEXSTRING) except the third digit can take value 'F'H, the result is a BITSTRING[4] of a binary representation of one digit in the input string. The function of the o_ThirdDigit is to return the third digit of the input parameter p_digits. EXAMPLE 1: o_G_FirstDigit('123') = '0011'B. EXAMPLE 2: o_G_FirstDigit('01F') = '1111'B. Type of the result: BITSTRING Parameters: p_PDU : PDU Description The function of the o_TTCN_HOCommandToBitstring is as the follows: - It returns the bitstring representation of the input HANDOVERCOMMAND p_PDU.

o_ThirdDigit

o_TTCN_HO_CommandTo Bitstring
Specific test suite operation for Multi RAB testing
Table 136: TSO definitions for Multi RAB testing
Description Type of the result: BOOLEAN Parameters: p_RAB_Tx_Info : RAB_Tx_Info Conditions: Inputs: p_RAB_Tx_Info: test data, number of RBs, and RB info of each RB (RB id, SDU size and number of SDUs to be transmitted in consecutive TTIs Outputs: The BOOLEAN result of the TSO: TRUE if system simulator accepts the information sent from TTCN FALSE if system simulator rejects the information sent from TTCN. Description When sending the data through the TSO, after the CMAC_Restriction_REQ, the TFC under test will be one corresponding the maximum CTFC value in the Restricted list, so that SS can select the number of Transport blocks and the size of Transport blocks on individual Transport channels derived from this CTFC. Starting from the beginning of the raw data buffer given in the TSO: Data to be sent on a particular RbId is the first (number of SDUs * SDU_Size) bits All calls to TSO o_sendContinuosData in a test will always specify the exact same set of RbIds.

DecipheringKeys ::= OCTET STRING (SIZE (15)) -- Octets in DecipheringKeys are coded in the same way as the octets 3 to 17 -- of Deciphering Key IE in 3GPP TS 49.031. I.e. these octets contain -- Current Deciphering Key, Next Deciphering Key and Ciphering Key Flag.
Lcs-MOLR-ErrPara ::= CHOICE { systemFailure SystemFailureParam, unexpectedDataValue UnexpectedDataParam, dataMissing DataMissingParam, facilityNotSupported FacilityNotSupParam, ss-SubscriptionViolation SS-SubscriptionViolationParam, positionMethodFailure PositionMethodFailure-Param } -- This is derived from information object "lcs-MOLR"
--******************************************************** -- Derived from MAP-Errors 3GPP 29.002 --********************************************************
SystemFailureParam ::= CHOICE { networkResource NetworkResource, -- networkResource must not be used in version 3 extensibleSystemFailureParam ExtensibleSystemFailureParam -- extensibleSystemFailureParam must not be used in version <3 }
NetworkResource ::= ENUMERATED { plmn (0), hlr (1), vlr (2), pvlr (3), controllingMSC (4), vmsc (5), eir (6), rss (7)}
ExtensibleSystemFailureParam ::= SEQUENCE { networkResource NetworkResource extensionContainer ExtensionContainer

OPTIONAL, OPTIONAL }

UnexpectedDataParam ::= SEQUENCE { extensionContainer

ExtensionContainer }

DataMissingParam ::= SEQUENCE { extensionContainer }

ExtensionContainer

FacilityNotSupParam ::= SEQUENCE { extensionContainer., shapeOfLocationEstimateNotSupported neededLcsCapabilityNotSupportedInServingNode }
[0] IMPLICIT NULL OPTIONAL, [1] IMPLICIT NULL OPTIONAL
SS-SubscriptionViolationParam ::= SEQUENCE { extensionContainer ExtensionContainer }
PositionMethodFailure-Param ::= SEQUENCE { positionMethodFailure-Diagnostic [0] IMPLICIT PositionMethodFailure-Diagnostic extensionContainer [1] IMPLICIT ExtensionContainer OPTIONAL,. } PositionMethodFailure-Diagnostic ::= ENUMERATED { congestion (0), insufficientResources (1), insufficientMeasurementData (2), inconsistentMeasurementData (3), locationProcedureNotCompleted (4), locationProcedureNotSupportedByTargetMS (5), qoSNotAttainable (6), positionMethodNotAvailableInNetwork (7), positionMethodNotAvailableInLocationArea (8),. } -- exception handling: -- any unrecognized value shall be ignored

B B B B B B B B B B B B B B B B B B B B B B B B B B B B B F F F F F F
T1s040620 T1s040609 T1s040607 T1s040552 T1s040548 T1s040585 T1s040412 T1s040404 T1s040602 T1s040600 T1s040436 T1s040434 T1s040487 T1s040442 T1s040579 T1s040427 T1s040472 T1s040534 T1s040570 T1s040508 T1s040510 T1s040506 T1s040565 T1s040561 T1s040563 T1s040559 T1s040556 T1s040454 T1s040766 T1s040735 T1s040736 T1s040734 T1s040737 T1s040738 T1s040731

F F F F F F F F F

3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0
3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0
T1s040732 T1s040733 T1s040723 T1s040711 T1s040712 T1s040713 T1s040714 T1s040722 T1s040724
TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26

343 Subject

F F F F F F F
TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242
3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0
3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0
T1s040725 T1s040726 T1s040727 T1s040729 T1s040730 T1s040721 T1s040715
TP-26 TP-26 TP-26 TP-26 TP-26
TP-040242 TP-040242 TP-040242 TP-040242 TP-040242
TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-26
TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242

1174 1175

test Case 10.1.2.5.1 Correction in TTCN for execution of Opmode C UE. Correction to RRC Package 4 TC 8.1.2.3 Correction to RRC test cases 8.1.2.1 and 8.1.2.7 Correction to RRC test cases 8.1.3.1, 8.1.3.3, 8.1.3.4 and 8.1.3.5 Correction to RRC Package 1 TC 8.1.2.9 Correction to Package 2 RRC test case 8.3.1.4 Correction to Package 3 RRC inter-RAT measurement test cases 8.4.1.31 + 8.4.1.33 + 8.4.1.34 + 8.4.1.35 + 8.4.1.36 + 8.4.1.40 Correction to approved NAS test case 12.9.4 Correction to Approved RRC Package 2 TC 8.3.7.2 Correction to Approved RRC Package 3 TC 8.2.4.1a Correction to Approved RRC Package 3 TC 8.4.1.31 Correction to GCF P2 test cases 6.2.1.1, 6.2.1.6 and 6.2.1.9 to IR_U ATS v3.7.0 to check the displayed PLMN. Correction to Package 2 RAB test case 14.4.2.2 and 14.4.2.3. Correction to GCF P4 NAS test Case 12.4.1.2 (Revision of T1-040673) Correction of GCF P1 test case 7.2.3.23 Global correction of Structured Type Constraints containing wildcards violating coding convention E.3.7 Correction to GCF P4 RRC test Case 8.3.1.15 Extension to Guard Timer for Approved NAS GMM Test Cases Correction to RRC TC 8.1.12 for handling correct number of RRC Connection Release Complete message based on the value of N308 Corrections Required for the wk42 ATS Corrections to release of SS resources for a cell during test case execution Correction to approved RRC Package 1 8.3.1.1 Correction to approved RRC Package 4 TC 8.2.6.11 Regression test error corrections to TTCN deliveries of wk40 Correction of GCF P1 test case 7.2.3.14 Correction of GCF P1 test case 11.1.1.1 Correction of GCF P3 SMS test cases 16.1.1, 16.1.2, 16.1.9.1, 16.1.9.2, 16.1.10, 16.2.1, 16.2.2, 16.2.10 Corrections Required for the wk40 ATS Correction to Approved RRC Package 2 TC 8.2.4.3 Correction to Package 3 SMS test cases. Correction to approved package 4 NAS Test case tc_12_4_1_4d2 Correction to Package 4 NAS test case 12.2.1.2 for increasing the guard timer. Regression error corrections to TTCN deliveries of wk34 and wk37 Summary of regression errors in the wk37 ATS. Correction to RRC Package 1 test cases 8.1.7.1 and 8.1.7.2 (Revision of T1s040532) Corrections Required for the wk37 ATS (Revision of T1s040606) Correction to Package 2 RRC test case 8.3.2.11 to increase the timer while waiting for URA Update. Correction to Approved RRC Package 1 TC 8.1.2.2 Radiolink removal and subsequent addition to align the TTCN with 34.123-1 TTCN Correction to Test Case 14.2.12 and 14.2.16 Correction to Approved RRC Package 2 TC 8.4.1.2 Corrections to GCF package 2 IR_U test case 6.2.1.1 Corrections to GCF package 2 IR_U test case 6.2.1.6 Correction of GCF package 2 IR_U test case 8.3.7.1. Correction of GCF package 2 IR_U test case 8.3.7.2. Correction of GCF package 2 IR_U test case 8.3.7.3. Correction of GCF package 2 IR_U test case 8.3.7.4. Correction of GCF package 2 IR_U test case 8.4.1.40. TTCN changes to approved package 1 RRC testcase

7.3.2.2.16 7.3.2.2.17 7.3.2.2.17a 7.3.2.2.18 7.3.2.2.19 7.3.2.2.20 7.3.2.2.21 7.3.2.2.22 7.3.2.2.22a 7.3.2.2.23 7.3.2.2.24 7.3.2.2.25 7.3.2.2.26 7.3.2.2.26a 7.3.2.2.27 7.3.2.2.27a 7.3.2.2.28 7.3.2.2.28a 7.3.2.2.28b 7.3.2.2.29 7.3.2.2.29a 7.3.2.2.30 7.3.2.2.31 7.3.2.2.32 7.3.2.2.33 7.3.2.2.34 7.3.2.2.35 7.3.2.3 7.3.2.3.1 7.3.2.3.2 7.3.3 7.3.3.1 7.3.4 7.3.4.1 7.3.4.1.1 7.3.4.1.2 7.3.4.2 7.3.4.2.1 7.3.4.2.2 7.3.4.3 7.3.4.3.1 7.3.4.3.2 7.3.5 7.3.5.1 7.3.5.2 7.3.5.3 7.3.5.3.1 7.3.5.3.2
CMAC_Ciphering_Activate...76 CMAC_Config.....77 CMAC_MAChs_TFRCconfigure (later than r4)....80 CMAC_PAGING_Config....82 CMAC_Restriction....83 CMAC_SecurityMode_Config....84 CMAC_SequenceNumber....84 CMAC_SYSINFO_Config....84 CRLC_Bind_TestData_TTI...85 CRLC_Ciphering_Activate....86 CRLC_Config....86 CRLC_Integrity_Activate....88 CRLC_Integrity_Failure....89 CRLC_MAC_I_Mode....90 CRLC_Resume.....90 CRLC_RRC_MessageSN....91 CRLC_SecurityMode_Config....91 CRLC_SetRRC_MessageSN....92 CRLC_Set_Count_I....93 CRLC_SequenceNumber....93 CRLC_SendContinuousData_TTI....94 CRLC_Status.....95 CRLC_Suspend....95 CBMC_Config.....95 RLC_TR_DATA.....96 RLC_AM_DATA....97 RLC_UM_DATA....98 Specific ASP and IE definitions for 1.28 Mcps TDD (later than R99)..98 Specific ASP definitions....99 Specific IE definitions....99 TTCN primitives.....100 UTRAN TTCN primitives....100 GERAN PCO and ASP definitions....101 PCO Type definitions....101 PCO type for data transmission and reception in GERAN..101 PCO type for configuration and control in GERAN...101 PCO definitions.....102 PCOs for data transmission and reception in GERAN...102 PCOs for control primitives transmission and reception in GERAN..102 GERAN ASP Definitions....104 ASPs for data transmission and reception in GERAN..104 ASPs for control primitive transmission and reception in GERAN...115 A-GPS Upper tester, PCO and ASP definitions...133 Upper tester.....133 SV PCO.....133 A-GPS Primitives.....133 Control ASP Type Definition....134 Data ASP Type Definition....134

[28] [29] [30] [31]

3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol". 3GPP TS 04.60: "Digital cellular telecommunications system (Phase 2+); General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol". 3GPP TS 44.064: "Mobile Station - Serving GPRS Support Node (MS-SGSN) Logical Link Control (LLC) layer specification". 3GPP TS 23.038: "Alphabets and language-specific information". 3GPP TS 23.040: "Technical realization of Short Message Service (SMS)". 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)". ETSI ETR 141: "Methods for Testing and Specification (MTS); Protocol and profile conformance testing specifications; The Tree and Tabular Combined Notation (TTCN) style guide". ETSI TR 101 101: "Methods for Testing and Specification (MTS); TTCN interim version including ASN.support [ISO/IEC 9646-3] (Second Edition Mock-up for JTC1/SC21 Review)". ITU-T Recommendation X.680: "Information technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation". 3GPP TS 25.211: "Physical channels and mapping of transport channels onto physical channels (FDD)". ISO/IEC 9646 (all parts): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework". 3GPP TS 44.006: "Mobile Station - Base Stations System (MS - BSS) Interface Data Link (DL) layer specification". 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol". 3GPP TS 04.18: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol". 3GPP TR 25.925: "Radio interface for Broadcast/Multicast Services". ITU-T Recommendation O.153: "Basic parameters for the measurement of error performance at bit rates below the primary rate". IETF RFC 1144: "Compressing TCP/IP headers for low-speed serial links". ITU-T Recommendation V.42bis: "Data compression procedures for data circuit-terminating equipment (DCE) using error correction procedures". ITU-T Recommendation V.44: "Data compression procedures". 3GPP TS 44.008: "Mobile radio interface layer 3 specification". 3GPP TS 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". 3GPP TS 24.080: "Mobile radio interface layer 3 supplementary services specification; Formats and coding" 3GPP TS 29.002: "Mobile Application Part (MAP) specification" ITU-T Recommendation Q.773: "Signalling System No. 7 - Transaction Capabilities Formats and Encoding" ITU-T Recommendation X.880: "Information Technology - Remote Operations: Concepts, Model and Notation"

Assign new TLLI, ciphering key and algorithm unchanged MS uses the assigned uplink TBF to transmit the L3 message to SS, the SS manages the operation of the TBF without TTCN intervention and releases the TBF automatically according the countdown procedure Release resources in the SS for RLC/MAC emulation entity Release resources in the SS for LLC emulation entity Release SS resources of channel combination 11 Release SS resources of channel combination 5

6.10.2.7.2

6.10.2.7.2.1
Cell change order within a TBF
Cell change order procedure in channel combinations 5 and 13
message Comments Create the physical channel combination 5 for FCCH+SCH+BCCH+CCC H+SDCCH/4(0.3)+SACCH /C4(0.3) Create the physical channel combination 13 for PDTCH/F+PACCH/F+PTC CH/F
3GPP TS 34.123-3 version 5.0.0 Release 5 Direction ASP SS -> MS G_L2_SYSINFO_REQ
46 message SYSTEM INFORMATION TYPE1, SYSTEM INFORMATION TYPE2, SYSTEM INFORMATION TYPE2quater, SYSTEM INFORMATION TYPE3, SYSTEM INFORMATION TYPE4, SYSTEM INFORMATION TYPE13
ETSI TS 134 123-3 V5.0.0 (2005-03) Comments Broadcast system information messages: SI 1~4; SI 13

SS SS SS MS

G_CRLC_CreateRLC_MAC_REQ G_CLLC_CreateLLE_REQ G_CLLC_ Assign_REQ

G_L2_ACCESS_IND

SS -> MS G_L2_UNITDATA_REQ MS -> SS G_LLC_UNITDATA_IND
Create RLC/MAC emulation entity Create LLC emulation entity Assign TLLI, ciphering key and algorithm MS is GPRS attached, PDP context activated, then trigger MS to send two SNDCP PDU on LLC SAPI 3, each with 500 bytes user data. CHANNEL REQUEST RACH, TBF establishment with Establishment Cause = one phase packet access. Set up uplink TBF in RLC/MAC entity in SS, this TBF is corresponding to what indicated in the next IMMEDIATE ASSIGNMENT. The USFRate is set to 5 USF per second. IMMEDIATE ASSIGNMENT Assign the uplink resources (uplink TBF) to MS User data on SAPI 3, the The TBF shall not be in first SNDCP PDU countdown process PACKET MEASUREMENT ORDER This is within the TBF established above, which is in the process handling the second SNDCP PDU REPORT_TYPE = 1 MS sends the PACKET MEASUREMENT REPORT This is within the TBF established above what follows are in UTRAN cell, not present here

ASN.1 Type Definition Increment_Mode Type Definition
ENUMERATED {incPerCFN_Cycler(0), notInc(1), incByOne_IncPerCFN_Cycle(2)}

7.3.2.2.17

CMAC_Config
ASN.1 ASP Type Definition CMAC_Config_CNF CSAP For MAC emulator to report that a previous attempt to setup, reconfigure or release a logical channel is successful. Type Definition
cellId routingInfo INTEGER(-1.63), RoutingInfo
ASN.1 ASP Type Definition CMAC_Config_REQ CSAP To request to configure MAC entity. Setup is used for creation of the MAC instances or the MAC resources. Release is used for free the all MAC resources. The reconfiguration is to change the MAC parameters, it is not the MAC modification. Type Definition
INTEGER(-1.63), RoutingInfo, RatType, CHOICE { CmacConfigReq, CmacConfigReq, NULL
{ cellId routingInfo ratType configMessage setup reconfigure release }
ASN.1 Type Definition CmacConfigReq To request to configure MAC Type Definition
SS_ActivationTime, UE_Info, TrCHInfo, TrCH_LogCHMappingList1 TBD, TBD
{ activationTime uE_Info trCHInfo trCH_LogCHMapping -- RACHTrasmissionCtrolElements -- CPCHTransmissionControlElements
ASN.1 Type Definition UE_Info The value of c_RNTI_DSCH_RNTI is 16 bits, used either for C-RNTI or DSCH-RNTI. DSCH is configured if the physical channel in CMAC_config_REQ is a PDSCH. Otherwise, C-RNTI is applied. At the MAC-hs configuration both u_RNTI and c_RNTI_DSCH_RNTI are omitted. Type Definition
U_RNTI C_RNTI OPTIONAL, OPTIONAL
SEQUENCE { u_RNTI c_RNTI_DSCH_RNTI }
ASN.1 Type Definition TrCH_LogCHMappingList1 maxulTrCH = maxdlTrCH = 16 Type Definition
SEQUENCE { ulconnectedTrCHList SEQUENCE (SIZE (1.maxulTrCH)) OF SEQUENCE { trchid TransportChannelIdentity, trCH_LogCHMappingList TrCH_LogCHMappingList } OPTIONAL, dlconnectedTrCHList SEQUENCE (SIZE (1.maxdlTrCH)) OF SEQUENCE { trchid TransportChannelIdentity, trCH_LogCHMappingList TrCH_LogCHMappingList } OPTIONAL, dlconnectedMACdFlows SEQUENCE (SIZE (1.8)) OF SEQUENCE { mac_dFlowId MAC_d_FlowIdentity, trCH_LogCHMappingList TrCH_LogCHMappingList } OPTIONAL -- later than r4 }
ASN.1 Type Definition TrCH_LogCHMappingList maxLogCHperTrCH = 15 Type Definition
TrCH_LogicalChannelMapping
SEQUENCE (SIZE (1.maxLogCHperTrCH)) OF
ASN.1 Type Definition TrCHInfo The same TFCS information should be provided to the PHY and MAC layers at all times. When a CMAC_Config_REQ is used to configure the MAC layer, a corresponding CPHY_TrCH_Config_REQ should be sent to the PHY layer to ensure that the configuration is consistent. For MAC-hs configuration: When ulconnectedTrCHList, ulTFCS, dlconnectedTrCHList and dlTFCS are omitted this ASP configures an MAC-hs entity. Type Definition

ASP Name G_L2_Release_REQ PCO Type G_DSAP Comments This ASP requests L2 to send Layer 2 DISC command on the indicated SAPI. Parameter Name Parameter Type Comments cellId CellId sAPI SAPI 0 or 3 physicalChId PhysicalChId Channel identifier g_LogicChType G_LogicChType For SDCCH/8 and SACCH/C8 value is (0.7); for SDCCH/4 and SACCH/C4 value is (0.3). subChannel SubChannelNumber This field is not applicable and the SS shall ignore it if this field is coded as 15. 0 = normal release; releaseMode BITSTRING[1] 1 = local release. Detailed Comments
G_L2_Release_IND G_DSAP The ASP is used to receive an indication of the termination of an established multiple frame operation Comments or an indication of an unsuccessful establishment attempt. Parameter Name Parameter Type Comments cellId CellId sAPI SAPI 0 physicalChId PhysicalChId Channel identifier g_LogicChType G_LogicChType Valid only for logical channel types: TCH/H, FACCH/H, SACCH/TH, SDCCH/8, SACCH/C8, SDCCH/4, and SACCH/C4. For TCH/H, FACCH/H subChannel SubChannelNumber and SACCH/TH value is (0.1); for SDCCH/8 and SACCH/C8 value is (0.7); for SDCCH/4 and SACCH/C4 value is (0.3). releaseMode BITSTRING[1] 0 = normal release; 1 = local end release whether or not there are outstanding outstanding_Indicator BOOLEAN acknowledgements or unsolved G_L2_DATA_REQ primitives. Detailed Comments
ASP Name G_L2_SYSINFO_REQ PCO Type G_DSAP Comments The ASP is used to send system information messages to the lower layer emulator. Parameter Name Parameter Type Comments cellId CellId sAPI SAPI 0 physicalChId PhysicalChId g_LogicChType G_LogicChType BCCH or SACCH To indicate the instance of the system information messages. For SYSTEM INFORMATION Type 2ter, 18, 19, 20 the instanceIndex INTEGER value is (0.7); for type 14, 15 the value is (0.3); for type 2quater the value is (0.15); for all other type the value is 0. SYSTEM INFORMATION Type 5, 5bis, 5ter, and 6 are sysInfoType SysInfoType sent on SACCH, the other SYSTEM INFORMATION 's are sent on BCCH. This field contains SYSTEM INFORMATION message. See 3GPP TS 44.018 [43] clause 9.1.31 to msg PDU clause 9.1.43h for SYSTEM INFORMATION message definitions. The lower layer emulator shall store the SYSTEM INFORMATION's, and transmit them periodically according to the rules specified in clause 6.3.1.3 of 3GPP TS 05.02 or Detailed Comments 3GPP TS 45.002 [31]. The msg shall override the same type system information message previous stored in the lower layer emulator.
3GPP TS 34.123-3 version 5.0.0 Release 5 Type Name Type Definition Type Encoding SysInfoType INTEGER
25--SYSTEM INFORMATION TYPE 1 26--SYSTEM INFORMATION TYPE -- SYSTEM INFORMATION TYPE 2bis 3 -- SYSTEM INFORMATION TYPE 2ter 7 -- SYSTEM INFORMATION TYPE 2quater 27--SYSTEM INFORMATION TYPE 3 28--SYSTEM INFORMATION TYPE 4 29--SYSTEM INFORMATION TYPE -- SYSTEM INFORMATION TYPE 5bis 6 -- SYSTEM INFORMATION TYPE 5ter 30--SYSTEM INFORMATION TYPE 6 31--SYSTEM INFORMATION TYPE 7 24--SYSTEM INFORMATION TYPE -- SYSTEM INFORMATION TYPE -- SYSTEM INFORMATION TYPE 13 61--SYSTEM INFORMATION TYPE 16 62--SYSTEM INFORMATION TYPE 17 64--SYSTEM INFORMATION TYPE 18 65--SYSTEM INFORMATION TYPE 19 66--SYSTEM INFORMATION TYPE 20

7.3.5.2

SV PCO
The upper tester has an ASP interface through a PCO in type of SatS PCO defined in the table.
PCO Type Role Comments PCO Type Declarations SatS UT PCO type used for the Satellite Simulator and the assistance data source in the upper tester
PCO Name PCO Type Role Comments
PCO Declarations SV SatS UT Carry control, configuration and GPS assistance data to/from satellite simulator and assistance data source in the upper tester

7.3.5.3

A-GPS Primitives
The primitives at SV PCO are used to load a pre-defined GPS test scenario into the satellite simulator, start or stop generating and broadcasting satellite signals from the satellite simulator retrieve the GPS assistance data from assistance data source, the table below is the summary of these primitives.
3GPP TS 34.123-3 version 5.0.0 Release 5 Primitive Satellite_StartStop_REQ Satellite_StartStop_CNF Load_GPS_Scenario_ REQ
ETSI TS 134 123-3 V5.0.0 (2005-03) Use Start or stop generating satellite signals in the satellite simulator. Confirm the Satellite_StartStop_Req. Requests to load a pre-defined GPS test scenario into the satellite simulator Confirm the load_GPS_Scenario_Req Request the assistance data source to provide the next (in time) valid GPS assistance data elements. Return the GPS assistance data retrieved
Parameters Mode: start or stop Null GPS test scenario number
Load_GPS_Scenario_ CNF Null Retri_GPS_AssistanceData_REQ Indication of which assistance data elements to be retrieved Retri_GPS_AssistanceData_CNF GPS assistance data elements

7.3.5.3.1

Type Name PCO Type Comment ASN.1 ASP Type Definition Satellite_StartStop_CNF SatS To confirm successful of Satellite_StartStop_REQ Type Definition

confirm NULL

ASN.1 ASP Type Definition Satellite_StartStop_REQ SatS To start or stop generating satellite signals in the satellite simulator start starts broadcasting satellite signals; stop stops broadcasting satellite signals If used for start (0), this ASP shall be called 2 s. after the ASP Load_GPS_Scenario_REQ for loading or reloading a pre-defined GPS test scenario. Type Definition

downlink uplink downlink uplink downlink uplink downlink uplink downlink uplink downlink uplink downlink uplink downlink uplink downlink uplink downlink uplink downlink uplink downlink uplink downlink uplink downlink uplink downlink uplink
SRB0 SRB1 SRB1 SRB2 SRB2 SRB3 SRB3 SRB4 SRB4
RAB#1-1 RAB#1-1 RAB#1-2 RAB#1-2 RAB#1-3 RAB#1-3 RAB#2 RAB#2 RAB#1 RAB#1 RAB#2 RAB#2 RAB#2 RAB#2 RAB#2 RAB#2 RAB#2 RAB#2 RAB#1
UM UM UM AM AM AM AM AM AM TM TM TM TM TM TM TM TM TM TM AM AM UM UM AM AM AM AM AM AM AM
CS or PS CS or PS CS or PS CS or PS CS or PS CS or PS CS or PS CS or PS CS or PS
CS CS CS CS CS CS CS CS PS PS PS PS PS PS PS PS PS PS PS
tsc_RB25 (25) tsc_RB29 (29) tsc_RB30 (30) tsc_RB31 (31)

RAB#1 SRB0

AM AM UM UM
2nd AM RAB for PS 2nd AM RAB for PS 2nd AM RAB for PS 2nd AM RAB for PS Later than r4 DTCH on DPCH associated HSDSCH Later than r4 DTCH on HS-DSCH RB Id for Radio bearer that carries the 2nd CCCH in the DL CTCH FACH Second CTCH FACH
The RB values 0 to 5 are used for the signalling bearers. The values 10 to 15 are assigned to the CS RAB sub-flows. The values 20 to 25 are assigned to the PS RAB sub-flows. The value 30 is assigned to the CBSMS/BMC service.
Table 36: RB identities mapping between 34.123-1 & 34.123-3
RAB Combinations Single CS RAB 34.123-1 RB5 RB6 RB7 RB5 RB7 RB8 RB5 RB6 RB7 RB8 RB9 RB5 RB6 RB7 RB8 RB5 RB6 RB7 RB8 34.123-3 tsc_RB10 tsc_RB11 tsc_RB12 tsc_RB20 tsc_RB20 tsc_RB20 tsc_RB10 tsc_RB11, tsc_RB20 tsc_RB12 tsc_RB20 tsc_RB22 tsc_RB10 tsc_RB11 tsc_RB12 tsc_RB13 tsc_RB20 tsc_RB22 tsc_RB20 tsc_RB24

Single PS RAB

CS+PS Multi RABs

CS+CS Multi RABs

PS+PS Multi RABs
Scrambling and channelization codes
Table 37 shows the primary/secondary scrambling codes and the channelization codes for downlink channels.
Table 37: Primary/secondary scrambling codes and channelization codes for downlink channels
Type P-CCPCH P-CPICH S-CCPCH Identities (value assigned) tsc_P_CCPCH (4) tsc_P_CPICH (0) tsc_S_CCPCH1 (5) tsc_S_CCPCH2 (10) PICH tsc_PICH1 (6) tsc_PICH2 (11) AICH tsc_AICH1 (7) tsc_AICH2 (12) DPCH tsc_DL_DPCH1 (26) Secondary scrambling code (px_PrimaryScramblingCode + 50 ( cell No -1) ) mod 512 NA (px_PrimaryScramblingCode + 50 ( cell No -1) ) mod 512 NA (px_PrimaryScramblingCode + 50 ( cell No -1) ) mod 512 NA (carrying PCH) (px_PrimaryScramblingCode + 50 ( cell No -1) ) mod 512 NA (carrying PCH) (px_PrimaryScramblingCode + 50 ( cell No -1) ) mod 512 NA (px_PrimaryScramblingCode + 50 ( cell No -1) ) mod 512 NA (px_PrimaryScramblingCode + 50 ( cell No -1) ) mod 512 NA (px_PrimaryScramblingCode + 50 ( cell No -1) ) mod 512 NA (px_PrimaryScramblingCode + 50 ( cell No -1) ) mod 512 tsc_DL_DPCH1_2ndScrC (1) This value is related to the primary scrambling code of the cell (px_PrimaryScramblingCode + 50 ( cell No -1) ) mod 512 tsc_DL_DPCH2_2ndScrC (1) This value is related to the primary scrambling code of the cell Same as HS-SCCH Same as HS-SCCH Primary scrambling code Channelization Code tsc_P_CCPCH_ChC (256:1) tsc_P_CPICH_ChC (256:0) tsc_S_CCPCH1_ChC (64:1) tsc_S_CCPCH2_ChC (64:2) tsc_PICH1_ChC (256:2) tsc_PICH2_ChC (256:12) tsc_AICH1_ChC (256:3) tsc_AICH2_ChC (256:13) Depending on the configuration: tsc_DL_DPCH1_ChC_SRB (128:9) tsc_DL_DPCH1_ChC_Speech (128:0) tsc_DL_DPCH1_ChC_Streaming (32:0) tsc_DL_DPCH1_ChC_64k_CS (32:0) tsc_DL_DPCH1_ChC_64k_PS (32:0) Depending on the configuration: tsc_DL_DPCH2_ChC_SRB (256:1) tsc_DL_DPCH2_ChC_Speech (128:1) tsc_DL_DPCH2_ChC_Streaming (32:1) tsc_DL_DPCH2_ChC_64k_CS (32:1) tsc_DL_DPCH2_ChC_64k_PS (32:1) Later than r4 SF= 16 Number of codes depending on the configuration, at most 15 codes Later than r4 SF =128 Number of codes depending on the configuration, at most 4 codes

Table 98: Downlink configuration of Cell_FACH_3_SCCPCH_3_FACH_CTCH_2a: 3 S-CCPCH
RB Identity LogCh Type LogCh Identity RLC mode MAC priority TrCH Type TrCH identity PhyCh Type PhyCH identity tsc_RB24 (24) tsc_RB20 (20) DTCH DTCH tsc_RB(29) CCCH tsc_DL_ CCCH6 (6) UM 1 tsc_RB1 (1) DCCH tsc_DL_ DCCH1 (1) UM 2 tsc_RB2 (2) DCCH tsc_DL_ DCCH2 (2) AM 3 FACH tsc_FACH3 (16) Secondary CCPCH tsc_S_CCPCH3 (13) tsc_RB3 (3) DCCH tsc_DL_ DCCH3 (3) AM 4 tsc_RB_ tsc_RB4 BCCH_F (4) ACH_RA B (-19) DCCH tsc_DL_ DCCH4 (5) AM 5 BCCH tsc_BCC H7 (7) TM 6
tsc_DL_D tsc_DL_D TCH4(10) TCH1 (7) AM 1 FACH AM 1 FACH

tsc_FACH4 (17)

8.3.32
Configuration of PS Cell_DCH_HS-DSCH_64kPS_RAB (later than r4)
The configuration is based on 3GPP TS 34.108 [3], clause 6.10.2.4.5.1. The RB0/UM-CCCH is referred to 3GPP TS 34.108 [3], clause 6.10.2.4.3.2.1.2 and RB0/TM-CCCH is referred to 3GPP TS 34.108 [3], clause 6.10.2.4.4.1.1.1. The configuration is applied to those RAB signaling tests where a PS RAB on DTCH is setup for the interactive or background service class is mapped on to HS-DSCH. The uplink configuration is same in clause 8.3.8 except a HS-DPCCH shall be included in the UL_DPCH. Table 99: Downlink configuration of PS Cell_DCH_HS-DSCH_PS_RAB
RB Identity LogCh Type LogCh Identity RLC mode MAC priority TrCH Type TrCH identity PhyCh Type PhyCH identity tsc_RB25 (25) DTCH tsc_DL_DTCH1 (7) AM 1 HS_DSCH N/A HS-PDSCH tsc_HSPDSCH (18) DPCH tsc_DL_DPCH1 (26) Secondary CCPCH tsc_S_CCPCH1 (5) Same as downlink configuration of Cell_DCH_StandAloneSRB on DPCH Same as downlink configuration of Cell_DCH_StandAloneSRB on sCCPCH

8.3.33

Configuration of PS Cell_DCH_HS-DSCH_384kPS_RAB (later than r4)
The configuration is based on 3GPP TS 34.108 [3], clause 6.10.2.4.5.2. The RB0/UM-CCCH is referred to 3GPP TS 34.108 [3], clause 6.10.2.4.3.2.1.2 and RB0/TM-CCCH is referred to 3GPP TS 34.108 [3], clause 6.10.2.4.4.1.1.1. The configuration is applied to those RAB signaling tests where a PS RAB on DTCH is setup for the interactive or background service class is mapped on to HS-DSCH. The uplink configuration is same in clause 8.3.8 except a HS-DPCCH shall be included in the UL_DPCH. Table 100: Downlink configuration of PS Cell_DCH_HS-DSCH_PS_RAB

CIPHERING_STATUS = Started for the CN domain concerned, "RB mapping info" IE, changeing AM RB RLC size, is inculded in CELL UPDATE CONFIRM, RADIO REARER RECONFIGURATION, RADIO BEARER RELEASE

8.5.4.3.1

"RB mapping info" in CELL UPDATE CONFIRM
After sending the CELL UPDATE CONFIRM message, re-establish the RB and re-configure the RB with new RLC size and re-initialize COUNT-C for the RB:
CRLC_Config_REQ Release the concerned RB CRLC_Config_REQ Setup the concerned RB (new RLC size)
CRLC_SecurityMode_Config_REQ startValue = value received in the CELL UPDATE message integrityKey = value maintained by TTCN cn_DomainIdentity = CS or PS CRLC_Ciphering_Activate_REQ cipheringModeCommand = Start/Restart (existing algorithm) rb_DL_CiphActivationTimeInfo = now incHFN = NotInc CRLC_ Ciphering_Activate_REQ rb_UL_CiphActivationTimeInfo = now incHFN = NotInc

8.5.4.3.2

"RB mapping info" in RB RECONFIGURATION / RELEASE
After receiving the reconfiguration complete message, re-establish the RB and re-configure the RB with new RLC size and re-initialize COUNT-C for the RB:
CRLC_Config_REQ Release the concerned RB CRLC_Config_REQ Setup the concerned RB (new RLC size) CRLC_SecurityMode_Config_REQ startValue = value received in the reconfiguration complete message integrityKey = value maintained by TTCN cn_DomainIdentity = CS or PS CRLC_Ciphering_Activate_REQ cipheringModeCommand = Start/Restart (existing algorithm) rb_DL_CiphActivationTimeInfo = now incHFN = NotInc CRLC_Ciphering_Activate_REQ rb_UL_CiphActivationTimeInfo = now incHFN = NotInc

8.5.4.4

Security modification
Updating security keys is the scenario in this clause.
INTEGRITY_PROTECTION STATUS = Started SECURITY MODE COMMAND contains "Ciphering mode info" IE and/or "Integrity protection mode info" IE

8.5.4.4.1

Integrity started, ciphering not started
CIPHERING_STATUS = NotStarted for the CN domain concerned SECURITY MODE COMMAND with "Integrity protection mode info" IE containing integrityProtectionModeCommand = modify, but "Ciphering mode info" IE absent the same CN domain as in the previous SMC to start integrity protection.
CRLC_SecurityMode_Config_REQ startValue = 0 (new key) integrityKey = new key cn_DomainIdentity = CS or PS CRLC_RRC_MessageSN_REQ -- Get current RRC Message SN for calculation of DL activation time CRLC_Integrity_Activate_REQ (CN domain concerned) integrityProtectionModeCommand = modify dl_IntegrityProtActivationInfo = now (SRB2), calculated value or a pending activation time set by previous security mode control procedure (SRB2 other than SRB2) CRLC_Integrity_Activate_REQ (CN domain concerned, RB2) ul_IntegrityProtActivationInfo = now

6 Re-initialize COUNT-I for all RBs and SRBs (except RB2)
CRLC_SecurityMode_Config_REQ startValue = 0 (new key) integrityKey = new key cn_DomainIdentity = CS or PS
CRLC_Integrity_Activate_REQ IntegrityProtectionModeCommand = Start (FRESH) IntegrityProtectionAlgorithm = selected value (downlink integrity protection starts immediately) CRLC_Integrity_Activate_REQ ul_IntegProtActivationInfo = value (now)

8.5.4.5.3.3

Pending security configuration (no new key)
CRLC_SequenceNumber_REQ CRLC_SequenceNumber_CNF HFN = MAX(HFN of DL/UL COUNT-C of RB2) + 1 CRLC_Config_REQ Release RB2 CRLC_Config_REQ Setup RB2 CRLC_SecurityMode_Config_REQ startValue = HFN calculated above n_DomainIdentity = CS or PS CRLC_Ciphering_Activate_REQ if CIPHERING_STATUS= NotStarted cipheringModeCommand = NULL (no ciphering) if CIPHERING_STATUS = Started cipheringModeCommand = Start/Restart (existing algorithm) rb_DL_CiphActivationTimeInfo = now (RB2 only) incHFN = NotInc CRLC_Ciphering_Activate_REQ rb_UL_CipheringActivationTimeInfo = now (RB2 only) incHFN = NotInc
CRLC_Config_REQ Release all RB's and SRB's (except RB2) CRLC_Config_REQ Setup all RB's and SRB's (except RB2) CRLC_SecurityMode_Config_REQ startValue = value received in the response mesage integrityKey = value maintained by TTCN cn_DomainIdentity = CS or PS CRLC_ Ciphering_Activate _REQ cipheringModeCommand = Start/Restart (new algorithm) rb_DL_CiphActivationTimeInfo = now (except RB2) CRLC_ Ciphering_Activate _REQ rb_UL_CiphActivationTimeInfo = now (except RB2)
CRLC_SecurityMode_Config_REQ startValue = value received in the response message integrityKey = value maintained by TTCN cn_DomainIdentity = CS or PS CRLC_Integrity_Activate_REQ IntegrityProtectionModeCommand = Start (FRESH) IntegrityProtectionAlgorithm = selected value (downlink integrity protection starts immediately)
CRLC_Integrity_Activate_REQ ul_IntegProtActivationInfo = value (now)

8.5.4.6

8.5.4.6.1

CELL/URA update

RLC re-establish (RB2, RB3, RB4)
"RLC re-establish (RB2, RB3, RB4)" in CELL UPDATE CONFIRM message is set to TRUE CIPHERING_STATUS = Started for the CN domain concerned
1. After sending CELL UPDATE CONFIRM message, re-establish the RB2, RB3 and RB4 (if established)
CRLC_SecurityMode_Config_REQ startValue = value received from CELL UPDATE message cipheringKey = value maintained by TTCN cn_DomainIdentity = CS or PS CRLC_Ciphering_Activate_REQ (CN domain concerned) cipheringModeCommand = Start/Restart (existing algorithm) rb_DL_CiphActivationTimeInfo = now (RB2, RB3, RB4) incHFN = NotInc CRLC_Ciphering_Activate_REQ (CN domain concerned) rb_UL_CipheringActivationTimeInfo = now (RB2, RB3, RB4) incHFN = NotInc

8.5.4.6.2

RLC re-establish (RAB)

'00001'B

ItcInt

B5 B1 B1 B2 B3 B3 B1
'00110'B '1'B '1'B '10'B '011'B '001'B '1'B

263 Type

ETSI TS 134 123-3 V5.0.0 (2005-03) Default value Supported value
Description UE flow control. 0-outband, 1-inband, px_BcapUeFlowControl 2-no flow control. 3- X.25 4- X.75 Default: 0, outband flow control Dialling digits used to initiate a CC MO px_CC_CallDiallingDigits call (used with the AT dial D command). Service selected for Mobile Originated calls and Mobile Terminated calls. The possible values are px_CC_Serv ("Telephony", "EmergencyCall", "31kHz", "V110", "V120", "PIAFS", "FTM", "X31", "BTM", "MmediaCall") Tdelta value (refer to 34.108 clause px_DeltaSS_DelayTime 4.2.3) in ms. px_IMEI_Def Default IMEI value px_IMEISV_Def Default IMEISV value Different IMSI from the IMSI stored in px_IMSI_Diff the USIM This indicates if the UE implementation supports network originated PDP px_NwOrgPDP_Support Context. TRUE indicates, supported FALSE indicate, not supported A string parameter that identifies the px_PDP_IP_AddrInfoDCH MT in the address space applicable to the PDP for DCH. A string parameter that identifies the px_PDP_IP_AddrInfoFAC MT in the address space applicable to H the PDP for FACH. px_PTMSI_2 Second PTMSI used for testing.

FlowControl

IA5String

"0123456902"

Services

"31kHz"

HEXSTRING See note 1 HEXSTRING See note 1 '0010106543210 HEXSTRING 63'H

"200.1.1.80"

"200.1.1.90"
OCTETSTRI '09876543'O NG Second PTMSI signature used for OCTETSTRI px_PTMSI_Sig2 'AB1234'O testing. NG OCTETSTRI px_TMSI_2 Second TMSI value for testing '09876543'O NG NOTE 1: No default value can be proposed (Manufacturer defined value).
NAS test suite parameters declarations

Table B.3: NAS PIXIT

The following parameters are commonly used in the NAS ATS.
Description A second Random Challenge px_AuthRAND_2 (128 bits) Number of B-party numbers that can px_AutocallingBlacklistNum be stored in the list of blacklisted ber numbers Cause value of category 1 or 2 to be px_AutocallingCause1or2 used in TC_17_1_3 Called number to be used for auto px_AutocallingNumber calling Number of repeat attempt done for the px_AutocallingRepeatCat1o category 1 or 2 to be used in r2 TC_17_1_3 Not supported service selected for Mobile Originated calls and Mobile px_CC_ServNotSupp Terminated calls. The possible values are

3GPP TS 34.123-3 version 5.0.0 Release 5 Abbreviations ciph cld clsmk cmd cmpl cnf cfg conn ctrl def descr disc enq err (re)est ext fail ho id ie iel ind info init lvl loc locUpd max mgmt min misc mod ms msg mt neigh ntw num orig pag params perm phy qual rand ref reg rej rel req rsp rx sel seq serv st sysInfo sync sys tx
Meaning cipher, ciphering called classmark command complete confirm configuration connect control default description disconnect enquiry error (re)establish extended failure handover identity / identification information element information element length indication information initialize level location location update maximum management minimum miscellaneous modification mobile station message mobile terminal neighbour network number origin/-al page/-ing parameters permission physical quality random reference register reject release request response receiver selection sequence service state system information synchronization system transmitter

a) b) c)

RULE 4: Specific naming rules for test suite parameters/constants/variables test case variables and formal parameters The name should reflect the purpose/objective the object is used for. If the type is not a predefined one, it is useful that the name reflects the type, too. It could be useful, that the individual naming conventions are not the same for all object classes this rule applies to. e.g. use upper case letters for test suite parameters/constants, and use one of the other possibilities presented in ETR 141 [37] example 1 for other object classes.
See also ETR 141 [37] clauses 5.1 to 5.4 for further discussion on naming test suite parameters.
RULE 5: Specific naming rule for timers If the timer is not defined in the protocol to be tested, the name should reflect the objective of the timer used for testing. NOTE: There is no need to indicate the object type "timer" in the name, since timers only occur together with timer operations
RULE 6: Specific naming rule for PDU/ASP/structured types As far as applicable, derivation rules or mapping tables should be used to relate the names of the types to the corresponding objects in the protocol or service definition. NOTE: There may be types, e.g. erroneous PDU types, that do not relate to an object in the protocol or service definition.

3.7.0 3.7.0 3.7.0 3.7.0 3.7.0
3.8.0 3.8.0 3.8.0 3.8.0 3.8.0
T1s040716 T1s040709 T1s040708 T1s040707 T1s040693
T1s040697 T1s040696 T1s040694 T1s040695 T1s040675 T1s040692 T1s040687
F F F F F F F F F F F F F F F F F F F F F F F F F F F F F F
3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0 3.7.0
3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0 3.8.0
T1s040682 T1s040681 T1s040668 T1s040667 T1s040666 T1s040660 T1s040661 T1s040662 T1s040663 T1s040655 T1s040637 T1s040648 T1s040630 T1s040636 T1s040617 T1s040618 T1s040619 T1s040599 T1s040584 T1s040583 T1s040581 T1s040582 T1s040536 T1s040538 T1s040540 T1s040542 T1s040544 T1s040546 T1s040554 T1s040576

TP-26 TP-26 TP-26

333 Subject
TP-040242 TP-040242 TP-040242

3.7.0 3.7.0 3.7.0

3.8.0 3.8.0 3.8.0
T1s040575 T1s040572 T1s040569
TP-26 TP-26 TP-26 TP-26 TP-26 TP-26 TP-27
TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-040242 TP-050039
TP-27 TP-27 TP-27 TP-27 TP-27 TP-27
TP-050039 TP-050039 TP-050039 TP-050039 TP-050039 TP-050039

1190 1191

TP-050039

TP-27 TP-27

TP-050039 TP-050039

1195 1196

1197 1198

1199 1200

1201 1202
TP-27 TP-27 TP-27 TP-27 TP-27 TP-27 TP-27 TP-27 TP-27
TP-050039 TP-050039 TP-050039 TP-050039 TP-050039 TP-050039 TP-050039 TP-050039 TP-050040
Correction to MultiRAB test cases 14.2.38a, 14.2.38b and 14.2.38e Correction to Approved RRC Package 2 TC 8.4.1.2 Addition of verdicts in RRC default message handler on Dc SAP for Deactivate PDP Context Request message in RRC ATS.(Revision of T1s040512) Regression error corrections to TTCN deliveries of wk26 and wk31 Modification to MAC Package 2 test case 7.1.3.1 Correction to NAS test cases 9.4.2.3 (P2), 9.4.2.4 Proc 2 (P2), and 12.4.1.1a (P1) Correction to Package 3 SMS test case 16.2.1. Correction to GCF P1 test case 8.3.1.1 Regression test error corrections to TTCN deliveries of wk42 RRC Connection Establishment: Reject with InterRATInfo is set to GSM and selection to the designated system fails RRC Connection Establishment: Reject with interRATInfo is set to GSM MM connection / abortion by the network / cause not equal to #6 PS detach / rejected / PS services not allowed in this PLMN/ test1 Routing area updating / abnormal cases / attempt counter check / miscellaneous reject causes RRC / Paging for Connection in connected mode (URA_PCH, multiple paging records) Combined routing area updating / abnormal cases / access barred due to access class control / test procedure 1 Combined routing area updating / abnormal cases / access barred due to access class control / test procedure 2 Interactive or background / UL:64 DL:384 kbps / PS RAB + UL:3.4 DL: 3.4 kbps SRBs for DCCH / 20 ms TTI Measurement Report on INITIAL DIRECT TRANSFER message and UPLINK DIRECT TRANSFER message Conversational / speech / UL:5.9 DL:5.9 kbps / CS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH Interactive or background / UL:384 DL:384 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH / 10 ms TTI Interactive or background / UL:128 DL:128 kbps / PS RAB + UL:3.4 DL:3.4 kbps SRBs for DCCH Cell change order from UTRAN/To GPRS/CELL_DCH/Failure (Physical channel & Reversion Failure) RRC Connection Release in CELL_DCH state (Network Authentication Failure): Success Inter system handover from UTRAN/To GSM/Speech/Failure (Physical channel Failure and Reversion Failure) Cell reselection using cell status and cell reservations RRC / Radio Bearer Establishment for transition from CELL_DCH to CELL_FACH (Frequency band modification): Success Correct Selection of RACH parameters (FDD) Measurement Control and Report: Additional Measurements list PS attach / rejected / PS services not allowed in this PLMN Access Service class selection for RACH transmission Selection of RAT for UPLMN; Automatic mode Selection of RAT for OPLMN; Automatic mode Cell reselection if cell becomes barred or S<0; UTRAN to GPRS (CELL_FACH) Service Request / RAB re-establishment / UE initiated / multiple PDP contexts Summary of regression errors in the wk04 ATS