8.4.3 Inter-RAT mobility E-UTRA to GERAN

36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 16TSUser Equipment (UE) conformance specification

8.4.3.1 Inter-RAT handover / From E-UTRA to GPRS / PS HO

8.4.3.1.1 Test Purpose (TP)

(1)

with { UE in E-UTRA (data) RRC_CONNECTED state }

ensure that {

when { UE receives a MobilityFromEUTRACommand message including radio resources that have been allocated for the UE in the target cell }

then { UE successfully completes the handover and leaves the RRC_CONNECTED, enter the GPRS_Packet_Transfer_Mode}

}

8.4.3.1.2 Conformance requirements [D]

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.4.3.3, 5.4.3.4.

[TS 36.331, clause 5.4.3.3]

The UE shall be able to receive a MobilityFromEUTRACommand message and perform a cell change order to GERAN, even if no prior UE measurements have been performed on the target cell.

The UE shall:

1> stop timer T310, if running;

1> if the MobilityFromEUTRACommand message includes the purpose set to ‘handover’:

2> if the targetRAT-Type is set to ‘utra’ or ‘geran’:

3> consider inter-RAT mobility as initiated towards the RAT indicated by the targetRAT-Type included in the MobilityFromEUTRACommand message;

3> forward the nas-SecurityParamFromEUTRA to the upper layers;

3> access the target cell indicated in the inter-RAT message in accordance with the specifications of the target RAT;

3> if the targetRAT-Type is set to ‘geran’:

4> use the contents of systemInformation, if provided for PS Handover, as the system information to begin access on the target GERAN cell;

NOTE 1: If there are DRBs for which no radio bearers are established in the target RAT as indicated in the targetRAT-MessageContainer in the message, the E-UTRA RRC part of the UE does not indicate the release of the concerned DRBs to the upper layers. Upper layers may derive which bearers are not established from information received from the AS of the target RAT.

[TS 36.331, clause 5.4.3.4]

Upon successfully completing the handover or the cell change order, the UE shall:

1> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’;

1> stop timer T304, if running;

8.4.3.1.3 Test description

8.4.3.1.3.1 Pre-test conditions

System Simulator:

– Cell 1and Cell 24 – Cell 1 is an E-UTRAN cell, Cell 24 is a GERAN cell.

– All cells belong to the same PLMN.

– System information combination 5 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.

UE:

– None.

Preamble:

– UE is in state3 (Generic RB Established) in cell 1 as specified in clause 4.5.3 of TS 36.508.

8.4.3.1.3.2 Test procedure sequence

Table 8.4.3.1.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial condition after preamble, while columns marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 8.4.3.1.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 24

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-60

RSSI

dBm

[-85]

T1

Cell-specific RS EPRE

dBm/15kHz

-80

RSSI

dBm

[-65]

Table 8.4.3.1.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS configures cell 1 and GERAN cell 24 according to the row “T1” in Table 8.4.3.1.3.2-1

2

The SS transmits a MobilityFromEUTRACommand message on Cell 1.

<–

MobilityFromEUTRACommand

3

Check: Does the UE transmit a PS HANDOVER ACCESS message on cell 24?

–>

PS HANDOVER ACCESS

1

P

8.4.3.1.3.3 Specific message contents

Table 8.4.3.1.3.3-1: MobilityFromEUTRACommand (step 2, Table 8.4.1.2.3.2-1)

Derivation Path: 36.508 table 4.6.1-6

Information Element

Value/remark

Comment

Condition

MobilityFromEUTRACommand ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

mobilityFromEUTRACommand-r8 SEQUENCE {

CS-FallbackIndicator

false

Applies only for Rel.9

purpose CHOICE {

handover SEQUENCE {

targetRAT-Type

geran

targetRAT-MessageContainer

PS HANDOVER COMMAND

nas-SecurityParamFromEUTRA

UTRAGERAN

systemInformation

PSI-GERAN

PS HO

}

}

}

}

}

}

Table 8.4.3.1.3.3-2: PS HANDOVER COMMAND (Table 8.4.3.1.3.3-1)

Derivation Path: TS 36.508, Table 4.7D.1-1: PS HANDOVER COMMAND

Information Element

Value/remark

Comment

Condition

NAS Container for PS Handover

Present

Table 8.4.3.1.3.3-3: NAS Container for PS Handover (Table 8.4.3.1.3.3-2)

Information Element

Value/remark

Comment

Condition

NAS_CONTAINER_LENGTH

Present

Set accordingly

Type of ciphering algorithm

Present

old XID

Present

Reset with the old XID parameters

IOV-UI value

‘00000000’O

8.4.3.2 Inter-RAT cell change order / From E-UTRA data RRC_CONNECTED to GPRS / Without NACC

8.4.3.2.1 Test Purpose (TP)

(1)

with { UE in E-UTRA (data) RRC_CONNECTED state }

ensure that {

when { UE receives a MobilityFromEUTRACommand message including information facilitating access of the target cell }

then { UE successfully completing the cell change order and leaves the RRC_CONNECTED,enter the GPRS_Paccket_Idle}

}

8.4.3.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.4.3.3, 5.4.3.4.

[TS 36.331, clause 5.4.3.3]

The UE shall be able to receive a MobilityFromEUTRACommand message and perform a cell change order to GERAN, even if no prior UE measurements have been performed on the target cell.

The UE shall:

1> stop timer T310, if running;

1> if the MobilityFromEUTRACommand message includes the purpose set to ‘handover’:

2> if the targetRAT-Type is set to ‘utra’ or ‘geran’:

3> consider inter-RAT mobility as initiated towards the RAT indicated by the targetRAT-Type included in the MobilityFromEUTRACommand message;

3> forward the nas-SecurityParamFromEUTRA to the upper layers;

3> access the target cell indicated in the inter-RAT message in accordance with the specifications of the target RAT;

3> if the targetRAT-Type is set to ‘geran’:

4> use the contents of systemInformation, if provided for PS Handover, as the system information to begin access on the target GERAN cell;

NOTE 1: If there are DRBs for which no radio bearers are established in the target RAT as indicated in the targetRAT-MessageContainer in the message, the E-UTRA RRC part of the UE does not indicate the release of the concerned DRBs to the upper layers. Upper layers may derive which bearers are not established from information received from the AS of the target RAT.

2> else if the targetRAT-Type is set to ‘cdma2000-1XRTT’ or ‘cdma2000-HRPD’:

3> forward the targetRAT-Type and the targetRAT-MessageContainer to the CDMA2000 upper layers for the UE to access the cell indicated in the inter-RAT message in accordance with the specifications of the CDMA2000 target-RAT;

1> else if the MobilityFromEUTRACommand message includes the purpose set to ‘cellChangeOrder’:

2> start timer T304 with the timer value set to t304, as included in the MobilityFromEUTRACommand message;

2> if the targetRAT-Type is set to ‘geran’:

3> if networkControlOrder is included in the MobilityFromEUTRACommand message:

4> apply the value as specified in TS 44.060 [36];

3> else:

4> acquire networkControlOrder and apply the value as specified in TS 44.060 [36];

3> use the contents of systemInformation, if provided, as the system information to begin access on the target GERAN cell;

NOTE 2: The systemInformation is constructed in the same way as in 2G to 2G NACC, i.e. the PSI messages are encoded as such, whereas the SI messages exclude 2 octets of headers, see TS 44.060[36].

2> establish the connection to the target cell indicated in the CellChangeOrder;

NOTE 3: The criteria for success or failure of the cell change order to GERAN are specified in TS 44.060[36].

[TS 36.331, clause 5.4.3.4]

Upon successfully completing the handover or the cell change order, the UE shall:

1> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’;

1> stop timer T304, if running;

8.4.3.2.3 Test description

8.4.3.2.3.1 Pre-test conditions

System Simulator:

– Cell 1and Cell 24 – Cell 1 is an E-UTRAN cell, Cell 24 is a GERAN cell.

– All cells belong to the same PLMN.

– System information combination 5 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.

UE:

– None.

Preamble:

– UE is in state3 (Generic RB Established) in cell 1 as specified in clause 4.5.3 of TS 36.508.

8.4.3.2.3.2 Test procedure sequence

Table 8.4.3.2.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial condition after preamble, while columns marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 8.4.3.2.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 24

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-60

RSSI

dBm

-85

T1

Cell-specific RS EPRE

dBm/15kHz

-80

RSSI

dBm

-65

T2

Cell-specific RS EPRE

dBm/15kHz

-115

The power levels are such that reselection back to cell 1 should not occur

Table 8.4.3.2.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message to setup inter RAT measurement on Cell 1.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the setup of inter RAT measurement on Cell 1.

–>

RRCConnectionReconfigurationComplete

3

The SS changes Cell 1and Cell 24 parameters according to the row "T1" in table 8.4.3.2.3.2-1.

4

The UE transmit a MeasurementReport message to report the event B2 for Cell 24.

–>

MeasurementReport

5

The SS transmits a MobilityFromEUTRACommand message on Cell 1.

<–

MobilityFromEUTRACommand

5A

The UE transmits a CHANNEL REQUEST message on Cell24.

–>

CHANNEL REQUEST

5B

The SS changes cell 1 power level according to the row “T2”

6-15

Check: Does the test result of steps 2-11 in generic test procedure in TS 36.508 subclause 6.4.2.9 indicate that the UE is camped on GERAN Cell 24?

NOTE: The UE performs an RAU procedure and the RRC connection is released.

1

P

8.4.3.2.3.3 Specific message contents

Table 8.4.3.2.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.4.3.2.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 8.4.3.2.3.3-2: MeasConfig (step 1, Table 8.4.3.2.3.2-2)

Derivation Path: 36.508, Table 4.6.6-1, condition GERAN

Information Element

Value/remark

Comment

Condition

MeasConfig ::= SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f11

measObject[2]

MeasObjectGERAN-GENERIC(f11)

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-B2-GERAN

reportConfig[1]

ReportConfigInterRAT-B2-GERAN(-69, -79)

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f11

reportConfigId[1]

IdReportConfig-B2-GERAN

}

quantityConfig SEQUENCE {

quantityConfigGERAN SEQUENCE {

measQuantityGERAN

rssi

filterCoefficient

fc0

}

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF {

2 entries

Band > 64

measObjectEUTRA-v9e0[1] ::= SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] ::= SEQUENCE {}

}

}

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.4.3.2.3.3-3: MobilityFromEUTRACommand (step 5, Table 8.4.3.2.3.2-2)

Derivation Path: 36.508 table 4.6.1-6

Information Element

Value/remark

Comment

Condition

MobilityFromEUTRACommand ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL

criticalExtensions CHOICE {

c1 CHOICE {

mobilityFromEUTRACommand-r8::=SEQUENCE {

csFallbackIndicator

False

purpose CHOICE {

cellChangeOrder::= SEQUENCE {

t304

ms8000

targetRAT-Type CHOICE{

geran::= SEQUENCE {

physCellId

0001H

carrierFreq ::= SEQUENCE {

arfcn

Downlink ARFCN of Cell 24

bandIndicator

The same band indicator of the Cell 24

}

}

}

}

}

}

}

}

}

8.4.3.3 Inter-RAT cell change order / From E-UTRA data to GPRS / With NACC

8.4.3.3.1 Test Purpose (TP)

(1)

with { UE in E-UTRA (data) RRC_CONNECTED state }

ensure that {

when { UE receives a MobilityFromEUTRACommand message including information facilitating access of the target cell }

then { UE successfully completing the cell change order and leaves the RRC_CONNECTED,enter the GPRS_Paccket_Idle}

}

8.4.3.3.2 Conformance requirements[D]

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clauses 5.4.3.3, 5.4.3.4.

[TS 36.331, clause 5.4.3.3]

The UE shall be able to receive a MobilityFromEUTRACommand message and perform a cell change order to GERAN, even if no prior UE measurements have been performed on the target cell.

The UE shall:

1> stop timer T310, if running;

1> if the MobilityFromEUTRACommand message includes the purpose set to ‘handover’:

2> if the targetRAT-Type is set to ‘utra’ or ‘geran’:

3> consider inter-RAT mobility as initiated towards the RAT indicated by the targetRAT-Type included in the MobilityFromEUTRACommand message;

3> forward the nas-SecurityParamFromEUTRA to the upper layers;

3> access the target cell indicated in the inter-RAT message in accordance with the specifications of the target RAT;

3> if the targetRAT-Type is set to ‘geran’:

4> use the contents of systemInformation, if provided for PS Handover, as the system information to begin access on the target GERAN cell;

NOTE 1: If there are DRBs for which no radio bearers are established in the target RAT as indicated in the targetRAT-MessageContainer in the message, the E-UTRA RRC part of the UE does not indicate the release of the concerned DRBs to the upper layers. Upper layers may derive which bearers are not established from information received from the AS of the target RAT.

2> else if the targetRAT-Type is set to ‘cdma2000-1XRTT’ or ‘cdma2000-HRPD’:

3> forward the targetRAT-Type and the targetRAT-MessageContainer to the CDMA2000 upper layers for the UE to access the cell indicated in the inter-RAT message in accordance with the specifications of the CDMA2000 target-RAT;

1> else if the MobilityFromEUTRACommand message includes the purpose set to ‘cellChangeOrder’:

2> start timer T304 with the timer value set to t304, as included in the MobilityFromEUTRACommand message;

2> if the targetRAT-Type is set to ‘geran’:

3> if networkControlOrder is included in the MobilityFromEUTRACommand message:

4> apply the value as specified in TS 44.060 [36];

3> else:

4> acquire networkControlOrder and apply the value as specified in TS 44.060 [36];

3> use the contents of systemInformation, if provided, as the system information to begin access on the target GERAN cell;

NOTE 2: The systemInformation is constructed in the same way as in 2G to 2G NACC, i.e. the PSI messages are encoded as such, whereas the SI messages exclude 2 octets of headers, see TS 44.060[36].

2> establish the connection to the target cell indicated in the CellChangeOrder;

NOTE 3: The criteria for success or failure of the cell change order to GERAN are specified in TS 44.060[36].

[TS 36.331, clause 5.4.3.4]

Upon successfully completing the handover or the cell change order, the UE shall:

1> perform the actions upon leaving RRC_CONNECTED as specified in 5.3.12, with release cause ‘other’;

1> stop timer T304, if running;

8.4.3.3.3 Test description

8.4.3.3.3.1 Pre-test conditions

System Simulator:

– Cell 1and Cell 24 – Cell 1 is an E-UTRAN cell, Cell 24 is a GERAN cell.

– All cells belong to the same PLMN.

– System information combination 5 as defined in TS 36.508 [18] clause 4.4.3.1 is used in E-UTRA cells.

UE:

– None.

Preamble:

– UE is in state3 (Generic RB Established)in cell 1 as specified in clause 4.5.3 of TS 36.508.

8.4.3.3.3.2 Test procedure sequence

Table 8.4.3.3.3.2-1 illustrates the downlink power levels and other changing parameters to be applied for the cells at various time instants of the test execution. Row marked "T0" denotes the initial conditions after preamble, while columns marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 8.4.3.3.3.2-1: Time instances of cell power level and parameter changes

Parameter

Unit

Cell 1

Cell 24

Remark

T0

Cell-specific RS EPRE

dBm/15kHz

-60

RSSI

dBm

[-85]

T1

Cell-specific RS EPRE

dBm/15kHz

-80

RSSI

dBm

[-65]

T2

Cell-specific RS EPRE

dBm/15kHz

-115

The power levels are such that reselection back to cell 1 should not occur

Table 8.4.3.3.3.2-2: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits an RRCConnectionReconfiguration message to setup inter RAT measurement on Cell 1.

<–

RRCConnectionReconfiguration

2

The UE transmits an RRCConnectionReconfigurationComplete message to confirm the setup of inter RAT measurement on Cell 1.

–>

RRCConnectionReconfigurationComplete

3

The SS changes Cell 1and Cell 24 parameters according to the row "T1" in table 8.4.3.3.3.2-1.

4

The UE transmit a MeasurementReport message to report the event B2 for Cell 24.

–>

MeasurementReport

5

The SS transmits a MobilityFromEUTRACommand message on Cell 1.

<–

MobilityFromEUTRACommand

5A

Check: Does the UE send a CHANNEL REQUEST message on the cell(s) specified in the test case?

–>

CHANNEL REQUEST

1

P

5AA

The SS changes cell 1 power level according to the row “T2”

5B

An uplink TBF is established in order to allow the UE to transmit a ROUTING AREA UPDATE REQUEST message signalling.

5C

The UE transmits a ROUTING AREA UPDATE REQUEST message.

–>

ROUTING AREA UPDATING REQUEST

5D

the UE transmits a PACKET SI STATUS message

–>

PACKET SI STATUS

6 -13

The reminder (steps 4 – 11) of generic test procedure in TS 36.508 subclause 6.4.2.9 is performed.

NOTE: The UE performs an RAU procedure and the RRC connection is released.

8.4.3.3.3.3 Specific message contents

Table 8.4.3.3.3.3-1: RRCConnectionReconfiguration (step 1, Table 8.4.3.3.3.2-2)

Derivation Path: 36.508, Table 4.6.1-8, condition MEAS

Table 8.4.3.3.3.3-2: MeasConfig (step 1, Table 8.4.3.3.3.2-2)

Derivation Path: 36.508, Table 4.6.6-1, condition GERAN

Information Element

Value/remark

Comment

Condition

MeasConfig ::= SEQUENCE {

measObjectToAddModList SEQUENCE (SIZE (1..maxObjectId)) OF SEQUENCE {

2 entries

measObjectId[1]

IdMeasObject-f1

measObject[1]

MeasObjectEUTRA-GENERIC(f1)

measObject[1]

MeasObjectEUTRA-GENERIC(maxEARFCN)

Band > 64

measObjectId[2]

IdMeasObject-f11

measObject[2]

MeasObjectGERAN-GENERIC(f11)

}

reportConfigToAddModList SEQUENCE (SIZE (1..maxReportConfigId)) OF SEQUENCE {

1 entry

reportConfigId[1]

IdReportConfig-B2-GERAN

reportConfig[1]

ReportConfigInterRAT-B2-GERAN(-69, [-79])

}

measIdToAddModList SEQUENCE (SIZE (1..maxMeasId)) OF SEQUENCE {

1 entry

measId[1]

1

measObjectId[1]

IdMeasObject-f11

reportConfigId[1]

IdReportConfig-B2-GERAN

}

quantityConfig SEQUENCE {

quantityConfigGERAN SEQUENCE {

measQuantityGERAN

rssi

filterCoefficient

fc0

}

}

measObjectToAddModList-v9e0 ::= SEQUENCE (SIZE (1..maxObjectId)) OF {

2 entries

Band > 64

measObjectEUTRA-v9e0[1] ::= SEQUENCE {

carrierFreq-v9e0

Same downlink EARFCN as used for f1

}

measObjectEUTRA-v9e0[2] ::= SEQUENCE {}

}

}

Condition

Explanation

Band > 64

If band > 64 is selected

Table 8.4.3.3.3.3-3: MobilityFromEUTRACommand (step 5, Table 8.4.3.3.3.2-2)

Derivation Path: 36.508 table 4.6.1-6

Information Element

Value/remark

Comment

Condition

MobilityFromEUTRACommand ::= SEQUENCE {

rrc-TransactionIdentifier

RRC-TransactionIdentifier-DL

criticalExtensions CHOICE {

c1 CHOICE {

mobilityFromEUTRACommand-r8::=SEQUENCE {

csFallbackIndicator

False

purpose CHOICE {

cellChangeOrder::= SEQUENCE {

t304

ms2000

targetRAT-Type CHOICE{

geran::= SEQUENCE {

physCellId

0001H

carrierFreq ::= SEQUENCE {

arfcn

Downlink ARFCN of Cell 24

bandIndicator

The same band indicator of the Cell 24

}

networkControlOrder

00

NC0: MS controlled cell re-selection, no measurement reporting

SI-OrPSI-GERAN::= CHOICE{

PS HO

SystemInfoListGERAN ::= SEQUENCE{

SYSTEM INFORMATION TYPE 1

Set according to clause 4.4.5 in TS 36.508.

SYSTEM INFORMATION TYPE 3

Set according to clause 4.4.5 in TS 36.508.

SYSTEM INFORMATION TYPE 13

Set according to clause 4.4.5 in TS 36.508.

}

}

}

}

}

}

}

}

}

}

Table 8.4.3.3.3.3-4: System Information 13 (Preamble onwards)

Derivation Path: 51.010, Clause 40.2.1.1.1

SI 13 Rest Octets

– SI_STATUS_IND bit

1 PACKET SI STATUS message supported

Table 8.4.3.3.3.3-5: Packet SI Status

Information element

Value/remark

< GLOBAL_TFI : Global TFI IE >

Present, any Value

< BCCH_CHANGE_MARK : bit (3) >

Present, any Value

< Received SI Message List : { 1 < SI_MESSAGE_TYPE : bit (8) >

{ < MESS_REC : bit (2)

}

SI_MESSAGE_TYPE : bit (8) >

{ < MESS_REC : bit (2)

}

} ** 0

< ADDITIONAL_MSG_TYPE : bit > ;

1

00011001 (SI1)

01 ( Message type supported and received, single instance)

1

00011011 (SI3)

1

Not Checked, The UE may include additional information

Present, any Value

< Received Unknown SI Message List :

{ 1 < SI_MESSAGE_TYPE : bit (8) > } ** 0

< ADDITIONAL_MSG_TYPE : bit > ;

0 (not present)

Present, any Value

| 1 — Additions for REL-6 :

< PSCSI_SUPPORT : bit >

< PS_REL_REQ : bit >

Not Checked

Not Checked

Not Checked