hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.7.3 Extended Uplink TBF | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.7.3.1 PEO / Extended UL TBF | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.7.3.1.1 Conformance requirements | An exception case is where a mobile station has enabled PEO or EC-EGPRS in which case it shall operate as follows:
[…]
- If a mobile station that has enabled PEO enters extended uplink TBF mode (see sub-clauses 9.3.1a and 9.3.1b) then it monitors the downlink PACCH starting with the 8th 52-multiframe following the 52-m... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.7.3.1.2 Test purpose | To verify that an MS that has enabled PEO (eDRX) and enters Extended uplink TBF mode will only monitors its assigned PACCH when all uplink RLC data blocks are received by the network |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.7.3.1.3 Method of test | Initial conditions
System Simulator:
1 cell, PEO capable for eDRX, NW_EXT_UTBF = 1.
Mobile Station:
MS is in Packet Idle mode, GPRS attached with support of GERAN Feature Package 1 indicated in MS Radio Access Capabilities, and PDP context 2 established. eDRX negotiated to 52 MF (~12.2 sec)
Specific PICS Statements
-
P... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8 EC-GSM-IoT procedures | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1 EC-GSM-IoT / Packet Access | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.1 EC-GSM-IoT / Packet Access / EC-BCCH CHANGE MARK | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.1.1 Conformance requirements | A MS that has enabled EC operation shall have read a complete EC-SI message set no longer than 24 hours prior to attempting packet access. In addition, if the mobile station detects a change to the EC- BCCH CHANGE MARK field when reading the EC-SCH it shall re-acquire one ore more EC-SI (as determined by the EC SI_CHAN... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.1.2 Test purpose | To verify that a change of EC-BCCH CHANGE MARK detected when initiating uplink packet access triggers an EC-System Information acquisition prior to performing the uplink packet access.
To verify that the EC-GSM-IoT capable mobile station uses the correct procedures for packet access. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.1.3 Method of test | Initial conditions
System Simulator:
1 cell EC-GSM-IoT supported
1TS EC-RACH Mapping used:
- Access Timeslots field in EC_SI2 set to ‘0’.
CC used: CC1 in downlink and uplink.
- CC1 used in the downlink: Signal level for FCCH and EC-SCH set-up such that the estimated received signal level parameter (C_VALUE) is greater ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.2 EC-GSM-IoT / Packet Access / EC-GSM-IoT / RACH Access allowed / Packet Access on RACH | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.2.1 Conformance requirements | An EC-GSM-IoT capable mobile station in a cell that supports EC-GSM-IoT attempts packet access by:
- transmitting an EC PACKET CHANNEL REQUEST message using the RACH (see sub-clause 3.5.2.1.2); or
Reference
3GPP TS 44.018 subclause 3.10.1
RACH Access Control is a 1 bit field and is coded as follows:
0: A mobile station... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.2.2 Test purpose | To verify that the EC-GSM-IoT capable mobile station attempts packet access using an EC PACKET CHANNEL REQUEST message on RACH when RACH access is allowed and it is using CC1 in both downlink and uplink. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.2.3 Method of test | Initial conditions
System Simulator:
1 cell EC-GSM-IoT supported
RACH Access to be used:
- RACH Access allowed (CC1)
- CC1 used in the downlink
- CC1 used in the uplink
Mobile Station:
The MS is GPRS attached and in EC mode.
Specific PICS Statements
-
PIXIT Statements
-
Foreseen final state of the MS
-
Test procedure
T... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.3 EC-GSM-IoT / Packet Access / EC-GSM-IoT / 1TS EC-RACH Mapping / CC1 | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.3.1 Conformance requirements | The RR entity of a mobile station initiates the packet access procedure by scheduling the sending of EC PACKET CHANNEL REQUEST messages (see Table 3.5.2.1.2a and sub-clause 9.1.65) as follows:
- Using the 1TS EC-RACH Mapping method if using CC1 on the uplink or if the Access Timeslots field sent in EC-SI2 = 0.
Referen... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.3.2 Test purpose | To verify that the EC-GSM-IoT capable mobile station attempts packet access using an EC PACKET CHANNEL REQUEST message with 1TS EC-RACH Mapping when RACH access is not allowed though using CC1 in both downlink and uplink. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.3.3 Method of test | Initial conditions
System Simulator:
1 cell EC-GSM-IoT supported.
RACH Access not allowed (CC1)
4 DL coverage classes are indicated as supported
1TS EC-RACH Mapping to be used:
- Access Timeslots field in EC_SI2 set to ‘1’.
- CC1 used in the downlink
- CC1 used in the uplink
Mobile Station:
The MS is GPRS attached and ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.4 EC-GSM-IoT / Packet Access / EC-GSM-IoT / 1TS EC-RACH Mapping / Access Timeslots field = 0 | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.4.1 Conformance requirements | The RR entity of a mobile station initiates the packet access procedure by scheduling the sending of EC-EGPRS PACKET CHANNEL REQUEST messages (see Table 3.5.2.1.2a.1 and sub-clause 9.1.65) as follows:
- Using the 1TS EC-RACH Mapping method if using CC1 on the uplink or if the Access Timeslots field sent in EC-SI2 = 0.
... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.4.2 Test purpose | To verify that the GSM-IoT capable mobile station attempts packet access using an EC PACKET CHANNEL REQUEST message with 1TS EC-RACH Mapping when Access Timeslots field sent in EC-SI2 = 0. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.4.3 Method of test | Initial conditions
System Simulator:
1 cell EC-GSM-IoT supported.
RACH Access not allowed (CC1)
4 DL coverage classes are indicated as supported
1TS EC-RACH Mapping to be used:
- Access Timeslots field in EC_SI2 set to ‘0’
- CC1 not used in the uplink
Cell power: -90dBm (to ensure uplink CC2)
Mobile Station:
The MS is ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.5 EC-GSM-IoT / Packet Access / EC-GSM-IoT / 2TS EC-RACH Mapping | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.5.1 Conformance requirements | The RR entity of a mobile station initiates the packet access procedure by scheduling the sending of EC PACKET CHANNEL REQUEST messages (see Table 3.5.2.1.2a.1 and sub-clause 9.1.65) as follows:
- Using the 2TS EC-RACH Mapping method if using CC2, CC3 or CC4 on the uplink and the Access Timeslots field sent in EC-SI2 =... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.5.2 Test purpose | To verify that the EC-GSM-IoT capable mobile station attempts packet access using an EC PACKET CHANNEL REQUEST message with 2TS EC-RACH Mapping when using CC2 in uplink and when Access Timeslots field sent in EC-SI2 = 1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.5.3 Method of test | Initial conditions
System Simulator:
1 cell EC-GSM-IoT supported.
RACH Access not allowed (CC1)
4 DL coverage classes are indicated as supported
2TS EC RACH Mapping to be used:
- Access Timeslots field in EC_SI2 set to ‘1’ (i.e. 2TS EC-RACH mapping).
- UL coverage as CC2.
Cell power: -90dBm (to ensure uplink CC2)
Mobil... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.6 EC-GSM-IoT / Packet Access / Implicit Reject | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.6.1 Conformance requirements | …
A mobile station that is accessing the network for the purpose of NAS signalling low priority (see 3GPP TS 24.008 [79]) and is not sending an exception report (see sub-clause 9.1.65), shall read the Implicit Reject Status (IRS) field, EC-BCCH CHANGE MARK field and RACH Access Control field sent in the EC-SCH INFORMAT... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.6.2 Test purpose | To verify that the EC-EGPRS capable mobile station, accessing the network for the purpose of NAS signalling low priority and is not sending an exception report, checks the Implicit Reject Status (IRS) field before attempting packet access. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.6.3 Method of test | Initial Conditions
System Simulator:
1 cell, EC-GSM-IoT supported, MS is in GPRS attached state. Routing area T3312=6min.
Mobile Station:
The MS is configured for “NAS signalling low access priority” and is configured for one of Access Class 0 to 9.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS at... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.7 EC-GSM-IoT / Packet Access / Legacy Implicit Reject | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.7.1 Conformance requirements | - transmitting an EC-EGPRS PACKET CHANNEL REQUEST message using the RACH (see sub-clause 3.5.2.1.2); or
- transmitting an EC-EGPRS PACKET CHANNEL REQUEST message using the 1TS EC-RACH Mapping method (see sub-clause 3.5.2.1.2a); or
- transmitting an EC-EGPRS PACKET CHANNEL REQUEST message using the 2TS EC-RACH Mapping m... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.7.2 Test purpose | To verify that the EC-EGPRS capable mobile station, accessing the network for the purpose of NAS signalling low priority ignores the checks the Implicit Reject Status (IRS) field when sending an EC-EGPRS PACKET CHANNEL REQUEST message using the RACH. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.1.7.3 Method of test | Initial Conditions
System Simulator:
1 cell, EC-GSM-IoT supported, Implicit reject flag enabled and RACH Access Control = 1 in EC-SCH
Mobile Station:
The MS is configured for “NAS signalling low access priority”
The MS is GPRS attached and have acquired the EC-SI message
Specific PICS Statements
-
PIXIT Statements
-
Te... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.2 EC-GSM-IoT / Paging | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.2.1 EC-GSM-IoT / Paging / normal paging | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.2.1.1 Conformance requirements | The MS can request the use of power saving mode (PSM) during an attach or routing area updating procedures (see 3GPP TS 23.682 [133A] and 3GPP TS 23.060 [74]). The MS shall not request the use of PSM during:
- an attach for emergency bearer services procedure;
- a routing area updating procedure for initiating a PDN co... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.2.1.2 Test purpose | 1. To verify that the mobile station in packet idle mode can receive and analyse the paging messages sent on the paging subchannels on EC-CCCH
2. To verify that the mobile station can activate both PSM and eDRX when in EC operation.
3. To verify that the mobile station that has enabled EC operation with both PSM and eD... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.2.1.3 Method of test | Initial Conditions
System Simulator:
- 1 cell, EC-GSM-IoT, PSM and eDRX supported
Mobile Station:
- The MS is switched off.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is triggered to initiate the GPRS attach procedure on an EC-GSM-IoT capable Cell but does not include eDRX or PSM related parame... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.2.2 EC-GSM-IoT / Paging / normal paging / with eDRX or eDRX and PSM | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.2.2.1 Conformance requirements | The MS can request the use of power saving mode (PSM) during an attach or routing area updating procedures (see 3GPP TS 23.682 [133A] and 3GPP TS 23.060 [74]). The MS shall not request the use of PSM during:
- an attach for emergency bearer services procedure;
- a routing area updating procedure for initiating a PDN co... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.2.2.3 Method of test | Initial Conditions
System Simulator:
- 1 cell, EC-GSM-IoT, PSM and eDRX supported
Mobile Station:
- The MS is switched off.
Specific PICS Statements
• Support of PSM (TSPC_PSM)
PIXIT Statements
-
Test Procedure
The MS is triggered to initiate the GPRS attach procedure on an EC-GSM-IoT (eDRX & PSM) capable Cell. The MS ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4 EC-GSM-IoT / Coverage Class | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.0 EC-GSM-IoT / Coverage Class / Default Conditions | All default conditions, message contents and macros are defined in section 40, except for the parameters as described in this subclause. These parameters are applicable to the whole section 41.8, they shall be transmitted by the system simulator and are required to be received by the MS under test.
By default, DL_CC_Se... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.1 EC-GSM-IoT / Coverage Class / Paging Extension | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.1.1 Conformance requirement | A mobile station that has enabled EC operation and has successfully negotiated eDRXdeterminess its nominal paging group as defined for EC operation (see 3GPP TS 45.002) according to its negotiated eDRX cycle and selected downlink coverage class . A mobile station that has enabled EC operation but has not negotiated eD... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.1.2 Test purpose | To verify that in EC operation, an MS will correctly consider the EC Paging extension field acquired when reading a message sent within its nominal paging group:
- If the EC Page Extension field indicates paging extension is enabled for its downlink coverage class, one additional paging group shall be considered,
- If ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.1.3 Method of test | Initial conditions
System Simulator:
1 cell EC-GSM-IoT supported
DL_CC_Selection = 0 (RLA_EC based coverage class selection)
BT_Threshold_DL = 0 (-87 dBm)
BT_Threshold_UL = 20 (-110 dBm)
CC2_Range_DL = CC3_Range_DL = 5 (6 dB)
Mobile Station:
The MS is GPRS attached in packet idle mode. eDRX cycle negotiated to 0100 (~ ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.2 EC-GSM-IoT / Coverage Class / UL Coverage Class selection | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.2.1 Conformance requirement | The MS shall select the uplink CC to use on (EC-)RACH according to table 6.10.3-1, based on the uplink received signal strength, estimated as
BS_RX_PWR = RLA_EC + min(MSPWR, MS_TXPWR_MAX_CCH) – BSPWR.
MSPWR is the nominal maximum output power of the MS. MS_TXPWR_MAX_CCH is the maximum TX power level an MS is allowed to... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.2.2 Test purpose | To verify that an MS making an EC packet channel request will select the uplink CC to use on (EC-)RACH based on the uplink received signal strength, and the associated parameters. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.2.3 Method of test | Initial conditions
System Simulator:
1 cell EC-GSM-IoT supported
RLA_EC based coverage class selection.
BT_Threshold_UL = 0 (-90 dBm)
BT_Threshold_DL = 18 (-105 dBm)
CC2_Range_UL = CC3_Range_UL = 3 (4 dB)
Access_Timeslots = 0 to use 1TS EC_RACH Mapping
EC_Max_Retrans = 0 (1 retransmission)
CC_Access_Adaptation = 0
Mob... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.3 EC-GSM-IoT / Coverage Class / DL Coverage Class selection / RLA_EC | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.3.1 Conformance requirement | The MS shall select the downlink CC based on either RLA_EC or SLA, as indicated by the DL_CC_Selection parameter sent in EC SI 2 (see 3GPP TS 44.018 [17]), according to table 6.10.2-1 and indicate it to the network in the EC Packet Channel Request message (see 3GPP TS 44.018 [17]). The network shall apply the indicated... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.3.2 Test purpose | To verify that an MS make an EC operation access request shall select the downlink CC to use on EC-RACH, based on the downlink received signal strength and the associated parameters if the DL_CC_Selection indicates the RLA_EC based method. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.3.3 Method of test | Initial conditions
System Simulator:
1 Serving cell, EC-GSM-IoT supported
DL_CC_Selection = 0 (RLA_EC based coverage class selection)
BT_Threshold_DL = 0 (-87 dBm)
BT_Threshold_UL = 20 (-110 dBm)
CC2_Range_DL = CC3_Range_DL = 3 (4 dB)
Access_Timeslots = 0 to use 1TS EC_RACH Mapping
EC_Max_Retrans = 0 (1 retransmission)... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.4 EC-GSM-IoT / Coverage Class / DL Coverage Class selection / SLA | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.4.1 Conformance requirement | The MS shall select the downlink CC based on either RLA_EC or SLA, as indicated by the DL_CC_Selection parameter sent in EC SI 2 (see 3GPP TS 44.018 [17]), according to table 6.10.2-1 and indicate it to the network in the EC Packet Channel Request message (see 3GPP TS 44.018 [17]). The network shall apply the indicated... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.4.2 Test purpose | To verify that an MS make an EC operation access request shall select the downlink CC to use on EC-RACH, based on the SINR and the associated parameters if the DL_CC_Selection indicates the SLA based method. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.4.3 Method of test | Initial conditions
System Simulator:
1 Serving cell EC-GSM-IoT supported, RxLev -70dBm
2 non-serving cells (same ARFCN than the serving Cell), with RxLev set as per test configuration.
DL_CC_Selection = 1 (SLA based coverage class selection)
BT_Threshold_DL = 18 (8 dB)
BT_Threshold_UL = 20 (-110 dBm)
CC2_Range_DL = C... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.5 EC-GSM-IoT / Coverage Class / UL Coverage Class Adaptation | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.5.1 Conformance requirement | If CC adaptation on EC-RACH and EC-AGCH is allowed (as indicated by the CC_Access_Adaptation parameter broadcast in EC-SI2), the MS shall gradually increase its CC as described in 3GPP TS 44.018 and use it as its selected uplink or downlink CC.
Reference
3GPP TS 45.008 subclause 6.10.4
A mobile station accessing the ne... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.5.2 Test purpose | To verify that an MS make an access for NAS low priority may gradually increment its coverage class if it is allowed by the network (based on CC_Access_Adaptation), it cannot be done more than 2 times |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.5.3 Method of test | Initial conditions
System Simulator:
1 cell EC-GSM-IoT supported
RLA_EC based coverage class selection.
BT_Threshold_UL = 0 (-90 dBm)
BT_Threshold_DL = 18 (-105 dBm)
CC2_Range_UL = CC3_Range_UL = 3 (4 dB)
Access_Timeslots = 0 to use 1TS EC_RACH Mapping
EC_Max_Retrans = 11 (7 retransmissions)
CC_Access_Adaptation = 1
Mo... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.6 EC-GSM-IoT / Coverage Class / DL Coverage Class Update | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.6.1 Conformance requirement | An EC capable MS whose last uplink transmission was in a cell that does not support EC-GSM-IoT may choose to enable EC operation upon reselection to a cell that supports EC-GSM-IoT. In this case it shall perform an uplink transmission (e.g. a cell update) to update the network (i.e. addition of Coverage Class informati... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.6.2 Test purpose | To verify that an MS updates the network appropriately if the selected downlink coverage class is modified.
For EC Capable MS supporting GPRS, it is verified that the MS will inform the network, of its DL coverage class when the last uplink transmission was done in a cell not supporting EC-GSM-IoT. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 41.8.4.6.3 Method of test | Initial conditions
System Simulator:
1 Serving cell EC-GSM-IoT supported, RxLev -70dBm
1 GPRS Cell, turned Off
2 non-serving cells (same ARFCN than the serving Cell), with RxLev set at -78dBm to ensure DL CC2 is used.
DL_CC_Selection = 1 (SLA based coverage class selection)
BT_Threshold_DL = 18 (8 dB)
BT_Threshold_UL... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1 Test of Medium Access Control (MAC) Procedures | Default conditions
The SS default conditions simulate one cell with default settings as defined in the GPRS general default section.
The MS default initial condition is GPRS attached. Unless otherwise stated, no PDP context is required.
The default message contents and signalling macro not specified in the end of this ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.1 Void | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2 Packet Uplink/Downlink Assignment | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1 Packet uplink assignment procedure | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.1 Void | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.2 Void | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.3 Void | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.4 Void | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.5 Void | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.6 Void | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.7 Void | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.8 Void | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.9 Packet Uplink Assignment / Two phase access | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.9.1 Void | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.9.2 Packet Uplink Assignment / Two phase access / Contention resolution | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.9.2.1 Packet Uplink Assignment / Two phase access / Contention resolution / Expiry of timer T3168 | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.9.2.1.1 Conformance requirements | The contention resolution has failed on the mobile station side when the mobile station does not receive a PACKET UPLINK ASSIGNMENT message with its TLLI before expiry of timer T3168. The mobile station shall then reinitiate the packet access procedure unless it has already been repeated 4 times. In that case, TBF fail... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.9.2.1.2 Test purpose | To verify that the mobile station reinitiates the packet access procedure after a time equal to timer T3168 and the procedure shall be attempted a total of 4 or 5 times. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.9.2.1.3 Method of test | Initial conditions
System Simulator:
1 cell supporting GPRS, CCCH combined with SDCCH,SI13 GPRS Cell Options, T3168 = 7.
Mobile Station:
The MS is GPRS attached and in packet idle mode. PDP context 1 has been established.
Specific PICS Statements
- Release of GPRS supported (TSPC_MS_GPRS_RELEASE)
PIXIT Statements
-
Tes... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.9.2.2 Packet Uplink Assignment / Two phase access / Contention resolution / TLLI mismatch | The contention resolution is completed on the mobile station side when the mobile station receives a PACKET UPLINK ASSIGNMENT message with the same TLLI as the mobile station has included in the PACKET RESOURCE REQUEST message. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.9.2.2.1 Conformance requirements | If the failure is due to a TLLI mismatch, or to the expiry of timers T3166 or T3168, or to the fact that the counter N3104 reached its maximum value in the contention resolution procedure, and repetition as described in subclause 7.1.3.3 has been performed, the mobile station shall remain in packet idle mode, notify hi... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.9.2.2.2 Test purpose | To verify that the MS reinitiates packet access procedure with failure due to a TLLI mismatch in the contention resolution procedure, unless it has already been attempted 4 or 5 times. In that case, TBF failure has occurred. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.9.2.2.3 Method of test | Initial conditions
System Simulator:
1 cell supporting GPRS, CCCH combined with SDCCH, GPRS cell options ACCESS_BURST_TYPE indicates 8 bit access.
Mobile Station:
The MS is GPRS attached and in packet idle mode. PDP context 1 has been established.
Specific PICS Statements
- Release of GPRS supported (TSPC_MS_GPRS_RELEA... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.9.3 Packet Uplink Assignment / Two phase access / Packet Resource Request / No respond to Packet Downlink Assignment | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.9.3.1 Conformance requirements | At sending of the PACKET RESOURCE REQUEST message, the mobile station shall start timer T3168. Further more, the mobile station shall not respond to PACKET DOWNLINK ASSIGNMENT messages while timer T3168 is running.
Reference
3GPP TS 04.60 subclause 7.1.3.1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.9.3.2 Test purpose | To verify that the mobile station does not respond to PACKET DOWNLINK ASSIGNMENT messages while timer T3168 is running after sending of the PACKET RESOURCE REQUEST message. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.9.3.3 Method of test | Initial conditions
System Simulator:
1 cell supporting GPRS, CCCH combined with SDCCH, T3168 indicates value 7 in GPRS Cell Options.
Mobile Station:
The MS is GPRS attached and in packet idle mode. PDP context 2 has been established.
Specific PICS Statements
-
PIXIT Statements
-
Test procedure
The MS is triggered to in... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.10 Packet Uplink Assignment / Abnormal cases | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.10.1 Packet Uplink Assignment / Abnormal cases / Incorrect PDCH assignment | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.10.1.1 Conformance requirements | If the mobile station has been assigned more PDCHs than it supports according to its MS multislot class, the mobile station shall reinitiate the packet access procedure unless it has already been repeated 4 times. In that case, TBF failure has occurred.
Reference
3GPP TS 04.60 subclause 7.1.4. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 42.1.2.1.10.1.2 Test purpose | To verify that the mobile station reinitiates the packet access procedure when the mobile station has been assigned more PDCHs than it supports and after 4 or 5 attempts of the packet access procedure the mobile station shall initiate TBF failure. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.