8.5.4 UE capability transfer

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

8.5.4.1 UE capability transfer / Success

8.5.4.1.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state }

ensure that {

when { UE receives an UECapabilityEnquiry message before AS security is activated }

then { UE transmits an UECapabilityInformation message including UE radio access capability information corresponding to the ue-CapabilityRequest variable }

}

(2)

with { UE in RRC_CONNECTED state }

ensure that {

when { UE receives an UECapabilityEnquiry message after AS security is activated }

then { UE transmits an UECapabilityInformation message including UE radio access capability information corresponding to the ue-CapabilityRequest variable }

}

8.5.4.1.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.6.3.3, 5.6.22.2, 5.6.22.3 and TS 25.331, clause 8.1.16.3.

[TS 36.331, clause 5.6.3.3]

The UE shall:

1> set the contents of UECapabilityInformation message as follows:

2> if the ue-CapabilityRequest includes ‘eutra’:

3> include the UE-EUTRA-Capability within a ue-CapabilityRAT-Container and with the rat-Type set to ‘eutra’;

2> if the ue-CapabilityRequest includes ‘geran-cs’ and if the UE supports GERAN CS domain:

3> include the UE radio access capabilities for GERAN CS within a ue-CapabilityRAT-Container and with the rat-Type set to ‘geran-cs’;

2> if the ue-CapabilityRequest includes ‘geran-ps’ and if the UE supports GERAN PS domain:

3> include the UE radio access capabilities for GERAN PS within a ue-CapabilityRAT-Container and with the rat-Type set to ‘geran-ps’;

2> if the ue-CapabilityRequest includes ‘utra’ and if the UE supports UTRA:

3> include the UE radio access capabilities for UTRA within a ueCapabilityRAT-Container and with the rat-Type set to ‘utra’;

2> if the ue-CapabilityRequest includes ‘cdma2000-1XRTT’ and if the UE supports CDMA2000-1xRTT:

3> include the UE radio access capabilities for CDMA 2000 within a ueCapabilityRAT-Container and with the rat-Type set to ‘cdma2000-1XRTT’;

1> if the RRC message segmentation is enabled based on the field rrc-SegAllowed received, and the encoded RRC message is larger than the maximum supported size of a PDCP SDU specified in TS 36.323 [8]:

2> initiate the UL message segment transfer procedure as specified in clause 5.6.22;

1> else:

1> submit the UECapabilityInformation message to lower layers for transmission, upon which the procedure ends.

[TS 25.331, clause 8.1.16.3]

The UE shall:

1> if the UE supports both UMTS TDD and FDD:

2> determine whether capabilities are being requested for FDD or TDD mode; and

2> use the capabilities associated with that mode for the remainder of this procedure.

1> include the IE "UE security information", and the IE "UE security information2" if inter-RAT PS handover is supported by the UE; and

1> not include the IE "UE Specific Behaviour Information 1 interRAT";

1> in case support for the compressed version of the inter RAT handover info is indicated via the other radio access technology:

2> if the other radio access technology is not E-UTRA:

3> include of the following IEs the IE that after encoding has the smallest size: IE "Predefined configuration status information compressed" or the IE "Predefined configuration status information".

2> else:

3> exclude the IE "Predefined configuration status information" and "Predefined configuration status information compressed".

2> include the IE "UE radio access capability compressed".

1> else:

2> if the other radio access technology is not E-UTRA:

3> include the IE "Predefined configuration status information".

2> else:

3> exclude the IE "Predefined configuration status information".

2> include the IE "UE capability container", containing the IE "UE radio access capability" and the IE "UE radio access capability extension", in accordance with the following:

3> if the UE supports multiple UTRA FDD Frequency Bands; or

3> if the UE supports a single UTRA FDD Frequency Band different from Band I [21]; or

3> if the UE supports E-UTRA:

4> include the IE "UE radio access capability", excluding IEs "RF capability FDD" and "Measurement capability" for FDD and including the IE "Measurement capability TDD" for TDD;

4> include the IE "UE radio access capability extension", including the IEs "RF capability FDD extension", the "Measurement capability extension", the "Additional Secondary Cells" and the "Non-contiguous multi-cell" associated with each supported UTRA FDD frequency band indicated in the IE "Frequency band", but may omit all or part of these IEs for supported inter-RAT bands.

3> else:

4> include the IE "UE radio access capability", including the IEs "RF capability FDD" and "Measurement capability" associated with the Band I [21] for FDD and excluding the IE "Measurement capability TDD" for TDD;

4> include the IE "UE radio access capability extension", including the IEs "RF capability FDD extension", the "Measurement capability extension", the "Additional Secondary Cells" and the "Non-contiguous multi-cell" associated with each supported UTRA FDD frequency band indicated in the IE "Frequency band".

1> For FDD, include the IE "UE radio access capability comp 2";

1> For 1.28 Mcps TDD, include the IE "UE radio access capability comp for 1.28 Mcps TDD";

1> initiate the transfer of the INTER RAT HANDOVER INFO message via the other radio access technology, using radio access technology-specific procedures;

1> store the following in the variable INTER_RAT_HANDOVER_INFO_TRANSFERRED if they were included in the INTER RAT HANDOVER INFO message:

2> the IE "Predefined configuration status information";

2> the IE "Predefined configuration status information compressed";

2> the IE "UE security information";

2> the IE "UE security information2";

2> the IE "UE radio access capability";

2> the IE "UE radio access capability extension"; and

2> the IE "UE radio access capability compressed";

2> if the IE "UE radio access capability compressed" were included in the INTER RAT HANDOVER INFO message:

3> set the IE "Security Capability" to the mandatory R99 algorithms.

1> and the procedure ends.

[TS 36.331, clause 5.6.22.2]

A UE capable of UL RRC message segmentation in RRC_CONNECTED will initiate the procedure when the following conditions are met:

1> if the RRC message segmentation is enabled based on the field rrc-SegAllowed received, and

1> if the encoded RRC message is larger than the maximum supported size of a PDCP SDU specified in TS 36.323 [8];

Upon initiating the procedure, the UE shall:

  1. initiate transmission of the ULDedicatedMessageSegment message as specified in 5.6.22.3;

[TS 36.331, clause 5.6.22.3]

The UE shall segment the encoded RRC PDU based on the maximum supported size of a PDCP SDU specified in TS 36.323 [8]. UE shall minimize the number of segments and set the contents of the ULDedicatedMessageSegment messages as follows:

1> For each new UL DCCH message, set the segmentNumber to 0 for the first message segment and increment the segmentNumber for each subsequent RRC message segment;

1> set rrc-MessageSegmentContainer to include the segment of the UL DCCH message corresponding to the segmentNumber;

1> if the segment included in the rrc-MessageSegmentContainer is the last segment of the UL DCCH message:

2> set the rrc-MessageSegmentType to lastSegment;

1> else:

2> set the rrc-MessageSegmentType to notLastSegment;

1> submit all the ULDedicatedMessageSegment messages generated for the segmented RRC message to lower layers for transmission in ascending order based on the segmentNumber, upon which the procedure ends.

8.5.4.1.3 Test description

8.5.4.1.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Switched OFF (state 1) according to [18].

8.5.4.1.3.2 Test procedure sequence

Table 8.5.4.1.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The UE is switched on.

2-8

Steps 2-8 of the generic procedure for UE registration specified in TS 36.508 subclause 4.5.2.3 are performed.

9

The SS transmits a UECapabilityEnquiry message to request UE radio access capability information for E UTRA only with rrc-segAllowed-r16 set to enabled.

<–

UECapabilityEnquiry

EXCEPTION: The "lower case letter" identifies a step sequence that takes place depending on the size of UE capability message.

IF pc_LTE_UL_Segmentation and UE’s encoded UECapabilityInformation message >= Max PDCP SDU size then steps 10a1 and 10a2 will be performed else step 10b1 will be performed

EXCEPTION: Step 10a1 is repeated a maximum of 16 times or till rrc-MessageSegmentType-16 IE within the UlDedicatedMessageSegment message indicate rrc-MessageSegmentType-r16 = lastSegment.

10a1

The UE sends segments of UECapabilityInformation message contained within the rrc-MessageSegmentContainer-r16 IE of the ULDedicatedMessageSegment message.

–>

ULDedicatedMessageSegment

10a2

Check: Is the received UE radio access capability information as per the ue-CapabilityRequest variable?

1

P

10b1

Check: Does the UE transmit a UECapabilityInformation message?

–>

UECapabilityInformation

1

P

11

The SS transmits a SecurityModeCommand message to activate AS security.

<–

SecurityModeCommand

12

The UE transmits a SecurityModeComplete message and establishes the initial security configuration.

–>

SecurityModeComplete

EXCEPTION: Steps 13a1 to 13a2 describe behaviour that depends on UE configuration;

the "lower case letter" identifies a step sequence that take place if the UE has ESM information which needs to be transferred after SECURITY MODE COMPLETE message.

13a1

IF the UE sets the ESM information transfer flag in the last PDN CONNECTIVITY REQUEST message THEN the SS transmits a DLInformationTransfer message.

This message includes an ESM INFORMATION REQUEST message.

<–

DLInformationTransfer

13a2

The UE transmits a ULInformationTransfer message.

This message includes an ESM INFORMATION RESPONSE message.

–>

ULInformationTransfer

14-16c1

Steps 14-16c1 of the generic procedure for UE registration specified in TS 36.508 subclause 4.5.2.3 are performed.

17

The SS transmits a UECapabilityEnquiry message to request UE radio access capability information for E UTRA only with rrc-segAllowed-r16 set to enabled.

<–

UECapabilityEnquiry

EXCEPTION: The "lower case letter" identifies a step sequence that takes place depending on the size of UE capability message.

IF pc_LTE_UL_Segmentation and UE’s encoded UECapabilityInformation message >= Max PDCP SDU size then steps 18a1 and 18a2 will be performed else step 18b1 will be performed.

EXCEPTION: Step 18a1 is repeated a maximum of 16 times or till rrc-MessageSegmentType-16 IE within the UlDedicatedMessageSegment message indicate rrc-MessageSegmentType-r16 = lastSegment.

18a1

Check: Does the UE send segments of UECapabilityInformation message contained within the rrc-MessageSegmentContainer-r16 IE of the ULDedicatedMessageSegment message?

–>

ULDedicatedMessageSegment

18a2

Check: Is the received UE radio access capability information as per the ue-CapabilityRequest variable?

2

P

18b1

Check: Does the UE transmit a UECapabilityInformation message?

–>

UECapabilityInformation

2

P

EXCEPTION: Steps 19a1 to 19a2 describe behaviour that depends on the UE capability.

19a1

IF pc_FDD, pc_TDD_HCR, pc_TDD_LCR, pc_TDD_VHCR, pc_GERAN, pc_1xRTT or pc_HRPD THEN the SS transmits a UECapabilityEnquiry message to request UE radio access capability information for every other supported RATs.

<–

UECapabilityEnquiry

19a2

Check: Does the UE transmit a UECapabilityInformation message?

–>

UECapabilityInformation

2

P

20-22

IF MULTI_PDN = TRUE (NOTE) THEN steps 10-12 of the generic procedure for network initiated release of additional PDN connectivity specified in TS 36.508 subclause 4.5A.18.3 are performed for the non-IMS PDN.

NOTE: MULTI_PDN as defined in TS 36.508 subclause 4.5.2.

8.5.4.1.3.3 Specific message contents

Table 8.5.4.1.3.3-1: UEcapabilityEnquiry (step 9 and 17, Table 8.5.4.1.3.2-1)

Derivation path: 36.508 clause 4.6.1 table 4.6.1-22

Information Element

Value/Remark

Comment

Condition

UECapabilityEnquiry ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

ueCapabilityEnquiry-r8 SEQUENCE {

ue-CapabilityRequest SEQUENCE (SIZE (1..maxRAT-Capabilities)) OF SEQUENCE {

1 entry

E-UTRA only

RAT-Type[1]

eutra

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

rrc-SegAllowed-r16

enabled

}

}

}

}

}

}

}

}

}

}

}

}

}

}

Table 8.5.4.1.3.3-2: UECapabilityInformation (step 10a2 and 18b1, Table 8.5.4.1.3.2-1)

Derivation path: 36.508 clause 4.6.1 table 4.6.1-23

Information Element

Value/Remark

Comment

Condition

UECapabilityInformation ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

ueCapabilityInformation-r8 SEQUENCE { SIZE (1..maxRAT-Capabilities)) OF SEQUENCE {

1 entry only

rat-Type[1]

eutra

E-UTRA only

ueCapabilitiesRAT-Container[1] OCTET STRING {

UE-EUTRA-Capability SEQUENCE {

accessStratumRelease

Not checked

Value should be based on Rel of Access stratum supported

ue-Category

Checked against UE Category indications in the PICS

Rel-8 or Rel-9

pdcp-Parameters

Not checked

Rel-8

pdcp-Parameters SEQUENCE {

> Rel-8

supportedROHC-Profiles SEQUENCE {

profile0x0001

Checked

pc_ROHC_profile0x0001

profile0x0002

Checked

pc_ROHC_profile0x0002

profile0x0003

Not checked

profile0x0004

Not checked

profile0x0006

Not checked

profile0x0101

Not checked

profile0x0102

Not checked

profile0x0103

Not checked

profile0x0104

Not checked

}

maxNumberROHC-ContextSessions

Not checked

}

phyLayerParameters SEQUENCE {

ul-AntennaSelectionSupported

Not checked

ue-SpecificRefSigsSupported

Not checked

}

rf-Parameters SEQUENCE {

supportedBandListEUTRA (SIZE (1..maxBands)) OF SEQUENCE {

n1 entries where n2 is the sum of pc_eBandα_Supp for α= 1 to 64, n3 is the sum of reported bands without pc_eBandα_Supp for α= 1 to 64, and n4 is the number of extended
bands indicated as maxFBI (=64) corresponding to the extended bands in supportedBandListEUTRA_v9e0 (Note 14).

n1= n2+n3+n4

not pc_FDD_TypeB_HalfDuplex

BandListEUTRA SEQUENCE {

bandEUTRA [α = 1..n2]

Any value β such that pc_eBandβ_Supp is TRUE and different from all eutra-Band[k] where k = 1 to α – 1.
Except bands indicated as extended bands.

halfDuplex[α = 1..n2]

False

FDD

}

}

supportedBandListEUTRA (SIZE (1..maxBands)) OF SEQUENCE {

n1 entries where n2 is the sum of pc_eBandα_Supp for α= 1 to 64, n3 is the sum of reported bands without pc_eBandα_Supp for α= 1 to 64, and n4 is the number of extended
bands indicated as maxFBI (=64) corresponding to the extended bands in supportedBandListEUTRA_v9e0 (Note 14).

n1=n2+n3+n4

pc_FDD_TypeB_HalfDuplex

BandListEUTRA SEQUENCE {

bandEUTRA [α = 1..n2]

Any value β such that pc_eBandβ_Supp is TRUE and different from all eutra-Band[k] where k = 1 to α – 1.

.
Except bands indicated as extended bands.

halfDuplex[α = 1..n2]

true

FDD

}

}

}

measurementParameters SEQUENCE {

BandListEUTRA(SIZE (1..maxBands)) OF SEQUENCE {

same number of entries like in SupportedBandListEUTRA

BandInfoEUTRA SEQUENCE {

InterFreqBandList (SIZE (1..maxBands)) OF SEQUENCE {

m entries (contents not checked, but m shall be equal to the number of bands listed in each IE present in interRAT-Parameters)

InterFreqBandInfo

}

InterRAT-BandList (SIZE (1..maxBands)) OF SEQUENCE {

InterRAT-BandInfo

Not checked

}

}

}

}

featureGroupIndicators

shall be set according to the corresponding PICS items

— FGI 1

Checked

— FGI 2

Checked

— FGI 3

Checked

— FGI 4

Checked

— FGI 5

Checked

— FGI 6

Checked

— FGI 7

Checked

— FGI 8

Checked

— FGI 9

Checked

— FGI 10

Checked

— FGI 11

Checked

— FGI 12

Checked

— FGI 13

Checked

— FGI 14

Checked

— FGI 15

Checked

— FGI 16

Checked

— FGI 17

Checked

— FGI 18

Checked

— FGI 19

Checked

— FGI 20

Checked

— FGI 21

Checked

— FGI 22

Checked

— FGI 23

Checked

— FGI 24

Checked

— FGI 25

Checked

— FGI 26

Checked

— FGI 27

Checked

— FGI 28

Checked

— FGI 29

Checked

— FGI 30

Checked

— FGI 31

Checked

— FGI 32

‘0’B (Undefined)

interRAT-Parameters SEQUENCE {

m elements are present

utraFDD

Present but value not checked

See Note 11

pc_FDD AND (px_ReportUTRA_RAT=fdd OR px_ReportUTRA_RAT=both)

utraTDD128

Present but value not checked

See Note 11

pc_TDD_LCR AND Not px_NoTDD_LCR_onLTE AND (px_ReportUTRA_RAT=tdd OR px_ReportUTRA_RAT=both)

Note 4

utraTDD384

Present but value not checked

See Note 11

pc_TDD_HCR AND (px_ReportUTRA_RAT=tdd OR px_ReportUTRA_RAT=both)

utraTDD768

Present but value not checked

See Note 11

pc_TDD_VHCR AND (px_ReportUTRA_RAT=tdd OR pc_ReportUTRA_RAT=both)

geran

Present but value not checked

pc_GERAN

cdma2000-HRPD

Present but value not checked

pc_HRPD

cdma2000-1xRTT

Present but value not checked

pc_1xRTT

}

nonCriticalExtension SEQUENCE {

See Note 2

phyLayerParameters-v920

Not checked

interRAT-ParametersGERAN-v920

Not checked

interRAT-ParametersUTRA-v920

Not checked

interRAT-ParametersCDMA2000-v920

Not checked

deviceType-r9

Not checked

csg-ProximityIndicationParameters-r9

Not checked

neighCellSI-AcquisitionParameters-r9

Not checked

son-Parameters-r9

Not checked

nonCriticalExtension SEQUENCE {

lateNonCriticalExtension SEQUENCE {

featureGroupIndRel9Add-r9

If present, shall be set according to the corresponding PICS items

— FGI 33

Checked

— FGI 34

Checked

— FGI 35

Checked

— FGI 36

Checked

— FGI 37

Checked

— FGI 38

Checked

— FGI 39

Checked

— FGI 40

Checked

— FGI 41

Checked

— FGI 42-64

‘0’B (Undefined)

fdd-Add-UE-EUTRA-Capabilities-r9 SEQUENCE {

phyLayerParameters-r9

Not checked

featureGroupIndicators-r9

Shall be set according to the corresponding PICS items. Checked. See Note 1.

BITSTRING 32

— FGI 1_F

Checked

— FGI 2_F

Checked

— FGI 3_F

Checked

FDD = TDD

— FGI 4_F

Checked

— FGI 5_F

Checked

FDD = TDD

— FGI 6_F

Checked

FDD = TDD

— FGI 7_F

Checked

FDD = TDD

— FGI 8_F

Checked

— FGI 9_F

Checked

— FGI 10_F

Checked

— FGI 11_F

Checked

— FGI 12_F

Checked

— FGI 13_F

Checked

FDD = TDD

— FGI 14_F

Checked

FDD = TDD

— FGI 15_F

Checked

— FGI 16_F

Checked

— FGI 17_F

Checked

FDD = TDD

— FGI 18_F

Checked

FDD = TDD

— FGI 19_F

Checked

— FGI 20_F

Checked

FDD = TDD

— FGI 21_F

Checked

FDD = TDD

— FGI 22_F

Checked

— FGI 23_F

Checked

— FGI 24_F

Checked

— FGI 25_F

Checked

FDD = TDD

— FGI 26_F

Checked

— FGI 27_F

Checked

— FGI 28_F

Checked

— FGI 29_F

Checked

— FGI 30_F

Checked

FDD = TDD

— FGI 31_F

Checked

— FGI 32_F

‘0’B (Undefined)

featureGroupIndRel9Add-r9

Shall be set according to the corresponding PICS items. Checked. See Note 1.

BITSTRING 32

— FGI 33_F

Checked

— FGI 34_F

Checked

— FGI 35_F

Checked

— FGI 36_F

Checked

— FGI 37_F

Checked

— FGI 38_F

Checked

— FGI 39_F

Checked

— FGI 40_F

Checked

— FGI 41_F

Checked

— FGI 42_F

Checked

— FGI 43-64_F

‘0’B (Undefined)

interRAT-ParametersGERAN-r9

Not checked

interRAT-ParametersUTRA-r9

Not checked

interRAT-ParametersGERAN-r9

Not checked

interRAT-ParametersCDMA2000-r9

Not checked

neighCellSI-AcquisitionParameters-r9

Not checked

}

tdd-Add-UE-EUTRA-Capabilities-r9 SEQUENCE {

phyLayerParameters-r9

Not checked

featureGroupIndicators-r9

Shall be set according to the corresponding PICS items. Checked. See Note 1.

BITSTRING 32

— FGI 1_T

Checked

— FGI 2_T

Checked

— FGI 3_T

Checked

FDD = TDD

— FGI 4_T

Checked

— FGI 5_T

Checked

FDD = TDD

— FGI 6_T

Checked

FDD = TDD

— FGI 7_T

Checked

FDD = TDD

— FGI 8_T

Checked

— FGI 9_T

Checked

— FGI 10_T

Checked

— FGI 11_T

Checked

— FGI 12_T

Checked

— FGI 13_T

Checked

FDD = TDD

— FGI 14_T

Checked

FDD = TDD

— FGI 15_T

Checked

— FGI 16_T

Checked

— FGI 17_T

Checked

FDD = TDD

— FGI 18_T

Checked

FDD = TDD

— FGI 19_T

Checked

— FGI 20_T

Checked

FDD = TDD

— FGI 21_T

Checked

FDD = TDD

— FGI 22_T

Checked

— FGI 23_T

Checked

— FGI 24_T

Checked

— FGI 25_T

Checked

FDD = TDD

— FGI 26_T

Checked

— FGI 27_T

Checked

— FGI 28_T

Checked

— FGI 29_T

Checked

— FGI 30_T

Checked

FDD = TDD

— FGI 31_T

Checked

— FGI 32_T

‘0’B (Undefined)

featureGroupIndRel9Add-r9

Shall be set according to the corresponding PICS items. Checked. See Note 1

BITSTRING 32

— FGI 33_T

Checked

— FGI 34_T

Checked

— FGI 35_T

Checked

— FGI 36_T

Checked

— FGI 37_T

Checked

— FGI 38_T

Checked

— FGI 39_T

Checked

— FGI 40_T

Checked

— FGI 41_T

Checked

— FGI 42_T

Checked

— FGI 43-64_T

‘0’B (Undefined)

interRAT-ParametersGERAN-r9

Not checked

interRAT-ParametersUTRA-r9

Not checked

interRAT-ParametersGERAN-r9

Not checked

interRAT-ParametersCDMA2000-r9

Not checked

neighCellSI-AcquisitionParameters-r9

Not checked

}

nonCriticalExtension SEQUENCE {

interRAT-ParametersUTRA-v9c0

Not checked

nonCriticalExtension SEQUENCE {

Not checked

phyLayerParameters-v9d0

Not checked

nonCriticalExtension SEQUENCE {

Not checked

rf-Parameters-v9e0 SEQUENCE {

supportedBandListEUTRA-v9e0 (SIZE (1..maxBands)) OF SEQUENCE {

n1 entries where n2 is the sum of pc_eBandα_Supp for α= 65 to 256 and n3 is the sum of reported bands without pc_eBandα_Supp for α= 65 to 256

n1= n2+n3

BandListEUTRA-v9e0 SEQUENCE {

bandEUTRA-v9e0 [α = 1..n2]

Any value β such that pc_eBandβ_Supp is TRUE and different from all eutra-Band[k] where k = 1 to α – 1

band 65 onwards,

up to 64 bands

}

}

}

nonCriticalExtension

Not checked

}

}

}

}

}

nonCriticalExtension SEQUENCE {

See Note 2

ue-Category-v1020

Checked against UE Category indications in the PICS and requirements from 36.306 cl. 4.1

phyLayerParameters-v1020

Not checked

rf-Parameters-v1020 {

Not checked

supportedBandCombination-r10 {

For as many band combinations as supported

Various conditions (Note 5)

BandCombinationParameters-r10 {

BandParameters-r10 {

bandEUTRA-r10 {

Not checked

}

BandParameterUL-r10 {

CA-MIMO-ParametersUL-r10 {

For as many bandwidth classes as supported

ca-BandwidthClassUL-r10

Not checked

supportedMIMO-CapabilityUL-r10

Not checked

}

}

BandParameterDL-r10 {

For as many bandwidth classes as supported

CA-MIMO-ParametersDL-r10 {

ca-BandwidthClassDL-r10

Not checked

supportedMIMO-CapabilityDL-r10

Not checked

}

}

}

}

measParameters-v1020 {

Not checked

bandCombinationListEUTRA-r10 {

For as many band combinations as supported

BandInfoEUTRA {

interFreqBandList {

InterFreqBandInfo {

interFreqNeedForGaps

Not checked

}

}

interRAT-BandList {

InterRAT-BandInfo {

interRAT-NeedForGaps

Not checked

}

}

}

}

}

}

}

featureGroupIndRel10-r10

Shall be set according to the corresponding PICS items. Checked.

BITSTRING 32

— FGI 101

Checked

— FGI 102

Checked

— FGI 103

Checked

Rel-10 to Rel-14 OR (>=Rel 15 AND NOT(UE category 8 OR UE category 11 OR UE category 12 OR UE DL Category 11 OR UE DL Category 12 OR UE DL Category 14))

(Note 12)

‘1’B

>= Rel-15 AND (UE category 8 OR UE category 11 OR UE category 12 OR UE DL Category 11 OR UE DL Category 12 OR UE DL Category 14)

(Note 12)

— FGI 104

Checked

Rel-10 to Rel-14 OR (>=Rel 15 AND NOT(UE category 8 OR UE category 11 OR UE category 12 OR UE DL Category 11 OR UE DL Category 12 OR UE DL Category 14))

(Note 12)

‘1’B

>= Rel-15 AND (UE category 8 OR UE category 11 OR UE category 12 OR UE DL Category 11 OR UE DL Category 12 OR UE DL Category 14)

(Note 12)

— FGI 105

Checked

— FGI 106

Checked

— FGI 107

Checked

— FGI 108

Checked

— FGI 109

Checked

— FGI 110

Checked

— FGI 111

Checked

— FGI 112

Checked

— FGI 113

Checked

IF set to ‘1’ THEN pc_UL_CA_2Carriers shall be TRUE

pc_UL_CA_2Carriers

— FGI 114

Checked

— FGI 115

Checked

— FGI 116

Checked

— FGI 117-132

‘0’B (Undefined)

interRAT-ParametersCDMA2000-v1020

Not checked

ue-BasedNetwPerfMeasParameters-r10

Not checked

interRAT-ParametersUTRA-TDD-v1020

Not checked

nonCriticalExtension SEQUENCE {

fdd-Add-UE-EUTRA-Capabilities-v1060

Shall be set according to the corresponding PICS items. Checked. See Note 1

BITSTRING 32

— FGI 101_F

Checked

— FGI 102_F

Checked

— FGI 103_F

Checked

Rel-10 to Rel-14 OR (>=Rel 15 AND NOT(UE category 8 OR UE category 11 OR UE category 12 OR UE DL Category 11 OR UE DL Category 12 OR UE DL Category 14))

(Note 12)

‘1’B

>= Rel-15 AND (UE category 8 OR UE category 11 OR UE category 12 OR UE DL Category 11 OR UE DL Category 12 OR UE DL Category 14)

(Note 12)

— FGI 104_F

Checked

Rel-10 to Rel-14 OR (>=Rel 15 AND NOT(UE category 8 OR UE category 11 OR UE category 12 OR UE DL Category 11 OR UE DL Category 12 OR UE DL Category 14))

(Note 12)

‘1’B

>= Rel-15 AND (UE category 8 OR UE category 11 OR UE category 12 OR UE DL Category 11 OR UE DL Category 12 OR UE DL Category 14)

(Note 12)

— FGI 105_F

Checked

— FGI 106_F

Checked

— FGI 107_F

Checked

— FGI 108_F

Checked

— FGI 109_F

Checked

— FGI 110_F

Checked

— FGI 111_F

Checked

— FGI 112_F

Checked

— FGI 113_F

Checked

IF set to ‘1’ THEN pc_UL_CA_2Carriers shall be TRUE

pc_UL_CA_2Carriers

— FGI 114_F

Checked

— FGI 115_F

Checked

— FGI 116_F

Checked

— FGI 117-132_F

‘0’B (Undefined)

tdd-Add-UE-EUTRA-Capabilities-v1060

Shall be set according to the corresponding PICS items. Checked. See Note 1

BITSTRING 32

— FGI 101_T

Checked

— FGI 102_T

Checked

— FGI 103_T

Checked

Rel-10 to Rel-14 OR (>=Rel 15 AND NOT(UE category 8 OR UE category 11 OR UE category 12 OR UE DL Category 11 OR UE DL Category 12 OR UE DL Category 14))

(Note 12)

‘1’B

>= Rel-15 AND (UE category 8 OR UE category 11 OR UE category 12 OR UE DL Category 11 OR UE DL Category 12 OR UE DL Category 14)

(Note 12)

— FGI 104_T

Checked

Rel-10 to Rel-14 OR (>=Rel 15 AND NOT(UE category 8 OR UE category 11 OR UE category 12 OR UE DL Category 11 OR UE DL Category 12 OR UE DL Category 14))

(Note 12)

‘1’B

>= Rel-15 AND (UE category 8 OR UE category 11 OR UE category 12 OR UE DL Category 11 OR UE DL Category 12 OR UE DL Category 14)

(Note 12)

— FGI 105_T

Checked

— FGI 106_T

Checked

— FGI 107_T

Checked

— FGI 108_T

Checked

— FGI 109_T

Checked

— FGI 110_T

Checked

— FGI 111_T

Checked

— FGI 112_T

Checked

— FGI 113_T

Checked

IF set to ‘1’ THEN pc_UL_CA_2Carriers shall be TRUE

pc_UL_CA_2Carriers

— FGI 114_T

Checked

— FGI 115_T

Checked

— FGI 116_T

Checked

— FGI 117-132_T

‘0’B (Undefined)

rf-Parameters-v1060

Not checked

nonCriticalExtension SEQUENCE {

rf-Parameters-v1090

Not checked

nonCriticalExtension SEQUENCE {

See Note 2

pdcp-Parameters-v1130

Not checked

phyLayerParameters-v1130

Not checked

Rel-8 to Rel-10

phyLayerParameters-v1130 SEQUENCE {

> Rel-10

crs-InterfHandl-r11

Checked

pc_CRS_Interference_Handling (Note 10)

ePDCCH-r11

Not checked

multiACK-CSI-Reporting-r11

Not checked

ss-CCH-InterfHandl-r11

Checked

pc_ss_CCH_Interference_Handling (Note 6)

tdd-SpecialSubframe-r11

Not checked

txDiv-PUCCH1b-ChSelect-r11

Not checked

ul-CoMP-r11

Not checked

}

rf-Parameters-v1130

Not checked

measParameters-v1130

Not checked

interRAT-ParametersCDMA2000-v1130

Not checked

otherParameters-r11

Not checked

fdd-Add-UE-EUTRA-Capabilities-v1130

Not checked

fdd-Add-UE-EUTRA-Capabilities-v1130

> Rel-10

phyLayerParameters-v1130 SEQUENCE {

crs-InterfHandl-r11

Checked

pc_CRS_Interference_Handling (Note 10)

ePDCCH-r11

Not checked

multiACK-CSI-Reporting-r11

Not checked

ss-CCH-InterfHandl-r11

Checked

pc_ss_CCH_Interference_Handling (Note 6)

tdd-SpecialSubframe-r11

Not checked

txDiv-PUCCH1b-ChSelect-r11

Not checked

ul-CoMP-r11

Not checked

}

measParameters-v1130

Not checked

otherParameters-r11

Not checked

}

tdd-Add-UE-EUTRA-Capabilities-v1130

Not checked

tdd-Add-UE-EUTRA-Capabilities-v1130

> Rel-10

phyLayerParameters-v1130 SEQUENCE {

crs-InterfHandl-r11

Checked

pc_CRS_Interference_Handling (Note 10)

ePDCCH-r11

Not checked

multiACK-CSI-Reporting-r11

Not checked

ss-CCH-InterfHandl-r11

Checked

pc_ss_CCH_Interference_Handling (Note 6)

tdd-SpecialSubframe-r11

Not checked

txDiv-PUCCH1b-ChSelect-r11

Not checked

ul-CoMP-r11

Not checked

}

measParameters-v1130

Not checked

otherParameters-r11

Not checked

}

nonCriticalExtension SEQUENCE {

phyLayerParameters-v1170

Not checked

ue-Category-v1170

Checked against UE Category indications in the PICS and requirements from 36.306 cl. 4.1

nonCriticalExtension SEQUENCE {

rf-Parameters-v1180

Not checked

mbms-Parameters-r11

Not checked

fdd-Add-UE-EUTRA-Capabilities-v1180

Not checked

tdd-Add-UE-EUTRA-Capabilities-v1180

Not checked

nonCriticalExtension SEQUENCE {

ue-Category-v11a0

Not checked

measParameters-v11a0

Not checked

nonCriticalExtension SEQUENCE {

phyLayerParameters-v1250

Not checked

rf-Parameters-v1250 SEQUENCE {

supportedBandListEUTRA-v1250

Not checked

supportedBandCombination-v1250

Not checked

supportedBandCombinationAdd-v1250

Not checked

freqBandPriorityAdjustment-r12

Checked

pc_freqBandPriorityAdjustment

}

rlc-Parameters-r12

Not checked

ue-BasedNetwPerfMeasParameters-v1250

Not checked

ue-CategoryDL-r12

Checked against UE Category indications in the PICS and requirements from 36.306 cl. 4.1

ue-CategoryUL-r12

Checked against UE Category indications in the PICS and requirements from 36.306 cl. 4.1

wlan-IW-Parameters-r12

Not checked

measParameters-v1250 SEQUENCE {

timerT312-r12

Not checked

alternativeTimeToTrigger-r12

Not checked

incMonEUTRA-r12

Not checked

incMonUTRA-r12

Not checked

extendedMaxMeasId-r12

Not checked

extendedRSRQ-LowerRange-r12

Not checked

rsrq-OnAllSymbols-r12

Not checked

crs-DiscoverySignalsMeas-r12

Not checked

csi-RS-DiscoverySignalsMeas-r12

Checked

pc_CSI-RS_DS_Meas

}

dc-Parameters-r12

Not checked

mbms-Parameters-v1250

Not checked

mac-Parameters-r12

Not checked

fdd-Add-UE-EUTRA-Capabilities-v1250

Not checked

tdd-Add-UE-EUTRA-Capabilities-v1250

Not checked

sl-Parameters-r12

Not checked

nonCriticalExtension SEQUENCE {

ue-CategoryDL-v1260

Checked against UE Category indications in the PICS and requirements from 36.306 cl. 4.1

nonCriticalExtension SEQUENCE {

rf-Parameters-v1270

Not checked

nonCriticalExtension SEQUENCE {

Not checked

phyLayerParameters-v1280

nonCriticalExtension SEQUENCE {

ue-CategoryDL-v1310

Checked against UE Category indications in the PICS and requirements from 36.306 cl. 4.1

See Note 3

pc_ue_CategoryDL_M1

ue-CategoryUL-v1310

Checked against UE Category indications in the PICS and requirements from 36.306 cl. 4.1

See Note 3

pc_ue_CategoryUL_M1

pdcp-Parameters-v1310

Not checked

rlc-Parameters-v1310

Not checked

mac-Parameters-v1310 SEQUENCE {

extendedMAC-LengthField-r13

Not checked

extendedLongDRX-r13

Checked

pc_extendedlongDRX

}

phyLayerParameters-v1310

Not checked

rf-Parameters-v1310

Not checked

measParameters-v1310 SEQUENCE {

rs-SINR-Meas-r13

Not checked

whiteCellList-r13

Not checked

extendedMaxObjectId-r13

Not checked

ul-PDCP-Delay-r13

Not checked

extendedFreqPriorities-r13

Not checked

multiBandInfoReport-r13

Not checked

rssi-AndChannelOccupancyReporting-r13

Checked

pc_rssiAndChannelOccupancyReporting

}

dc-Parameters-v1310

Not checked

sl-Parameters-v1310

Not checked

scptm-Parameters-r13

Not checked

ce-Parameters-r13 SEQUENCE {

ce-ModeA-r13

Checked

pc_CEmodeA

ce-ModeB-r13

Checked

pc_CEmodeB

}

interRAT-ParametersWLAN-r13

Not checked

laa-Parameters-r13 SEQUENCE {

crossCarrierSchedulingLAA-DL-r13

Not checked

csi-RS-DRS-RRM-MeasurementsLAA-r13

Not checked

downlinkLAA-r13

Checked

pc_downlink_LAA

endingDwPTS-r1310

Not checked

secondSlotStartingPosition- r13

Not checked

tm9-LAA-r13

Not checked

tm10-LAA-r13

Not checked

}

lwa-Parameters-r13

Not checked

wlan-IW-Parameters-v1310

Not checked

lwip-Parameters-r13

Not checked

fdd-Add-UE-EUTRA-Capabilities-v1310

Not checked

tdd-Add-UE-EUTRA-Capabilities-v1310

Not checked

nonCriticalExtension SEQUENCE{

Not checked

ce-Parameters-v1320 SEQUENCE {

intraFreqA3-CE-ModeA-r13

Checked

pc_IntraFreqA3_CE_ModeA

intraFreqA3-CE-ModeB-r13

Not checked

intraFreqHO-CE-ModeA-r13

Checked

pc_IntraFreqHO_CE_ModeA

intraFreqHO-CE-ModeB-r13

Not checked

}

phyLayerParameters-v1320

Not checked

rf-Parameters-v1320

Not checked

fdd-Add-UE-EUTRA-Capabilities-v1320

Not checked

tdd-Add-UE-EUTRA-Capabilities-v1320

Not checked

nonCriticalExtension

SEQUENCE{

Not checked

ue-CategoryDL-v1330

Checked against UE Category indications in the PICS and requirements from 36.306 cl. 4.1

phyLayerParameters-v1330

Not checked

ue-CE-NeedULGaps-r13

Not checked

nonCriticalExtension

SEQUENCE{

Not checked

ue-CategoryUL-v1340

Checked against UE Category indications in the PICS and requirements from 36.306 cl. 4.1

nonCritialExtension

SEQUENCE{

Not checked

ue-CategoryDL-v1350

Checked

See Note 7

pc_ue_CategoryDL_1bis

ue-CategoryUL-v1350

Checked

See Note 7

pc_ue_CategoryUL_1bis

ce-Parameters-v1350

Not checked

nonCriticalExtension SEQUENCE{

other-Parameters-v1360

Not checked

nonCriticalExtension SEQUENCE{

phyLayerParameters-v1430

Not checked

ue-CategoryDL-v1430

Not checked

See Note 8

ue-CategoryUL-v1430

Checked against UE Category indications in the PICS and requirements from 36.306 cl. 4.1

See Note 9

ue-CategoryUL-v1430b

Checked against UE Category indications in the PICS and requirements from 36.306 cl. 4.1

pc_ue_CategoryUL_21

mac-Parameters-v1430

Not checked

measParameters-v1430

Not checked

pdcp-Parameters-v1430

Not checked

rlc-Parameters-v1430

Not checked

rf-Parameters-v1430

Not checked

laa-Parameters-v1430

Not checked

lwa-Parameters-v1430

Not checked

lwip-Parameters-v1430

Not checked

otherParameters-v1430

Not checked

mmtel-Parameters-r14

Not checked

mobilityParameters-r14

Not checked

ce-Parameters-v1430

Not checked

fdd-Add-UE-EUTRA-Capabilities-v1430

Not checked

tdd-Add-UE-EUTRA-Capabilities-v1430

Not checked

mbms-Parameters-v1430

Not checked

sl-Parameters-v1430

Not checked

ue-BasedNetwPerfMeasParameters-v1430

Not checked

highSpeedEnhParameters-r14

Not checked

nonCriticalExtension SEQUENCE {

lwa-Parameters-v1440

Not checked

mac-Parameters v1440

Not checked

nonCriticalExtension SEQUENCE{

phyLayerParameters-v1450

Not checked

rf-Parameters-v1450

Not checked

ue-CategoryDL-v1450

Checked against UE Category indications in the PICS and requirements from 36.306 cl. 4.1

nonCriticalExtension SEQUENCE {

ue-CategoryDL-v1460

Checked against UE Category indications in the PICS and requirements from 36.306 cl. 4.1

pc_ue_CategoryDL_21

otherParameters-v1460

Not checked

nonCriticalExtension SEQUENCE {

irat-ParametersNR-

r15

Not checked

featureSetsEUTRA-

r15

Not checked

pdcp-ParametersNR-

r15

Not checked

fdd-Add-UE-EUTRA-Capabilities-

v1510

Not checked

tdd-Add-UE-EUTRA-Capabilities-

v1510

Not checked

nonCriticalExtension SEQUENCE {

measParameters-

v1520

Not checked

nonCriticalExtension SEQUENCE {

measParameters-

v1530 SEQUENCE {

qoe-MeasReport-r15

Not checked

qoe-MTSI-MeasReport-r15

Not checked

ca-IdleModeMeasurements-r15

Not checked

ca-IdleModeValidityArea-r15

Not checked

heightMeas-r15

Checked

pc_heightMeas

multipleCellsMeasExtension-r15

Checked

pc_Multiple_Cells_Meas_Ext

}

otherParameters-

v1530 SEQUENCE {

assistInfoBitForLC-r15

Not checked

timeReferenceProvision-r15

Not checked

flightPathPlan-r15

Checked

pc_FlightPathPlan

neighCellSI-AcquisitionParameters-

v1530

Not checked

mac-Parameters-

v1530

Not checked

phyLayerParameters-

v1530 SEQUENCE {

stti-SPT-Capabilities-r15

Not checked

ce-Capabilities-r15 SEQUENCE {

ce-CRS-IntfMitig-r15

Not checked

ce-CQI-AlternativeTable-r15

Not checked

ce-PDSCH-FlexibleStartPRB-CE-ModeA-r15

supported

pc_FlexibleStartPRB_PDSCH

ce-PDSCH-FlexibleStartPRB-CE-ModeB-r15

Not checked

ce-PDSCH-64QAM-r15

Not checked

ce-PUSCH-FlexibleStartPRB-CE-ModeA-r15

supported

pc_FlexibleStartPRB_PUSCH

ce-PUSCH-FlexibleStartPRB-CE-ModeB-r15

Not checked

ce-PUSCH-SubPRB-Allocation-r15

Not checked

ce-UL-HARQ-ACK-Feedback-r15

Not checked

shortCQI-ForSCellActivation-r15

Not checked

mimo-CBSR-AdvancedCSI-r15

Not checked

crs-IntfMitig-r15

Not checked

ul-PowerControlEnhancements-r15

Not checked

urllc-Capabilities-r15

Not checked

altMCS-Table-r15

Not checked

}

}

rf-Parameters-

v1530

Not checked

pdcp-Parameters-v1530

Not checked

ue-CategoryDL-

v1530

Checked against UE Category indications in the PICS and requirements from 36.306 cl. 4.1

ue-BasedNetwPerfMeasParameters-

v1530

Not checked

rlc-Parameters-

v1530

Not checked

sl-Parameters-

v1530

Not checked

extendedNumberOfDRBs-

v1530

Not checked

reducedCP-Latency-

v1530

Not checked

laa-Parameters-

v1530

Not checked

ue-CategoryUL-

v1530

Checked against UE Category indications in the PICS and requirements from 36.306 cl. 4.1

fdd-Add-UE-EUTRA-Capabilities-

v1530

Not checked

tdd-Add-UE-EUTRA-Capabilities-

v1530

Not checked

nonCriticalExtension SEQUENCE

UE-EUTRA-Capability-v1540-IEs

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

Condition

Explanation

Rel-8

Only for Rel-8

>Rel-8

For Rel-9 or later Releases

>Rel-10

For Rel-11 or later Releases

FDD = TDD

UE is not allowed to signal different values for FDD and TDD

Note 1: For Rel-9 UEs:
If FDD resp. TDD specific FGI values are reported
then
the FDD resp. TDD specific FGI PICS are checked against the reported FDD resp. TDD
specific FGI values,
else
the FDD resp. TDD specifc FGI PICS are both checked against the reported common FGI values.

For Rel-8 UEs the FDD resp. TDD specific FGI PICS are both checked against the reported common FGI values.

For Rel-10 and higher release versions the same holds as stated above for Rel-9, except that the common values may be assumed if not reported. See 36.331 Annex B.1.

Note 2: The present table shows the checking which is performed if a UE of the highest defined access stratum release indicator is tested. For UEs of lower release versions information related to higher release versions may be present if a UE has selective higher release features implemented. Such information is tolerated but not used for checking against any PICS items.

Note 3: Only checked against pc_ue_CategoryDL_M1 and pc_ue_CategoryUL_M1.

Note 4: Depending on UE implementation/configuration, the UE may not report certain RAT support based on information received from the network.

Note 5: List of Conditions:
pc_DL_intraBand_contCaBWclassB,
pc_DL_intraBand_contCaBWclassC,
pc_UL_intraBand_contCaBWclassB,
pc_UL_intraBand_contCaBWclassC,
pc_DL_intraBand_nonContCaBwClassComb_AA, pc_UL_intraBand_nonContCaBwClassComb_AA,
pc_DL_interBand_CaBwClassComb_AA,
pc_UL_SupportedInAllBandsInCAComb,
pc_UL_interBand_CaBwClassComb_AA

Checkpoints:
pc_DL_intraBand_contCaBWclassB shall be set to true if at least one DL Intra-band contiguous CA BW Class B CA configuration is reported;
pc_DL_intraBand_contCaBWclassC shall be set to true if at least one DL Intra-band contiguous CA BW ClassC CA configuration is reported;
pc_UL_intraBand_contCaBWclassB shall be set to true if at least one UL Intra-band contiguous CA BW Class B CA configuration is reported;
pc_UL_intraBand_contCaBWclassC shall be set to true if at least one UL Intra-band contiguous CA BW Class C CA configuration is reported;
pc_DL_intraBand_nonContCaBwClassComb_AA shall be set to true if at least one DL_intraBand_nonContCaBwClassComb_AA configuration is reported;
pc_UL_intraBand_nonContCaBwClassComb_AA shall be set to true if at least one UL_intraBand_nonContCaBwClassComb_AA configuration is reported;
pc_DL_interBand_CaBwClassComb_AA shall be set to true if at least one DL_DL_interBand_CaBwClassComb_AA configuration is reported;
pc_UL_SupportedInAllBandsInCAComb shall be set to true if UL_SupportedInAllBandsInCAComb configuration is reported for the CA band combination identified by px_EUTRA_CA_BandCombination;
pc_UL_interBand_CaBwClassComb_AA shall be set to true if at least one UL_interBand_CaBwClassComb_AA configuration is reported.

The UE shall include in supportedBandCombination-r10 as many as possible of the band combinations the UE supports. For each checkpoint listed above, in case none of the listed configuration is reported, the associated PICS item is assumed to be set correctly.

Note 6: If the UE is Single Mode (FDD or TDD) support of ss-CCH-InterfHandl-r11 will be signaled in the common IE.
If the UE is Dual Mode (FDD & TDD) and the support of ss-CCH-InterfHandl-r11 is different in both modes then it will be signaled under X-Add-UE-EUTRA-Capabilities-v1130 IE (X – fdd and/or tdd respectively), and it will not be present in the common IE. It will be signalled in the common IE if the value is the same on both modes (i.e. “supported” on both FDD and TDD). The IE may be signaled independently for either FDD or TDD or both.

Note 7: Only check against pc_ue_CategoryDL_1bis and pc_ue_CategoryUL_1bis.

Note 8: Not checked as no PICS are defined yet.

Note 9: Checked as far as PICS are defined.

Note 10: If the UE is Single Mode (FDD or TDD) support of crs-InterfHandl-r11 will be signaled in the common IE.
If the UE is Dual Mode (FDD & TDD) and the support of crs-InterfHandl -r11 is different in both modes then it will be signaled under X-Add-UE-EUTRA-Capabilities-v1130 IE (X – fdd and/or tdd respectively), and it will not be present in the common IE. It will be signalled in the common IE if the value is the same on both modes (i.e. “supported” on both FDD and TDD). The IE may be signaled independently for either FDD or TDD or both.

Note 11: Depending on UE implementation, the UE may not report both UTRA RATs supported.

Note 12: The applicable categories for FGI 103/104 checking are (UE category = 8 OR UE category >=11 OR UE DL Category = 11 OR UE DL Category = 12 OR UE DL Category >= 14) according to TS 36.331. The UE DL Categories higher than 14 are not explicitly listed in the condition because in this version of core specification UE DL Category > 14 requires supporting of UE Category 11 or 12.

Note 13: Void.

Note 14: The extended bands represented by their placeholders need to be related to the bands reported in supportedBandListEUTRA-v9e0.

Table 8.5.4.1.3.3-2A: UE-EUTRA-Capability-v1540-IEs (Table 8.5.4.1.3.3-2)

Derivation Path: TS 36.331 [11], clause 6.3.6

Information Element

Value/remark

Comment

Condition

UE-EUTRA-Capability-v1540-IEs SEQUENCE {

phyLayerParameters-v1540

Not checked

otherParameters-v1540

Not checked

fdd-Add-UE-EUTRA-Capabilities-v1540

Not checked

tdd-Add-UE-EUTRA-Capabilities-v1540

Not checked

sl-Parameters-v1540

Not checked

irat-ParametersNR-v1540

Not checked

nonCriticalExtension SEQUENCE {

UE-EUTRA-Capability-v1550-IEs

neighCellSI-AcquisitionParameters-v1550

Not checked

phyLayerParameters-v1550

Not checked

mac-Parameters-v1550

Not checked

fdd-Add-UE-EUTRA-Capabilities-v1550

Not checked

tdd-Add-UE-EUTRA-Capabilities-v1550

Not checked

nonCriticalExtension SEQUENCE {

UE-EUTRA-Capability-v1560-IEs

pdcp-ParametersNR-v1560

Not checked

irat-ParametersNR-v1560

Not checked

appliedCapabilityFilterCommon-r15

Not checked

fdd-Add-UE-EUTRA-Capabilities-v1560

Not checked

tdd-Add-UE-EUTRA-Capabilities-v1560

Not checked

nonCriticalExtension SEQUENCE {

UE-EUTRA-Capability-v1570-IEs

rf-Parameters-v1570

Not checked

irat-ParametersNR-v1570

Not checked

nonCriticalExtension SEQUENCE {

UE-EUTRA-Capability-v15a0-IEs

neighCellSI-AcquisitionParameters-v15a0

Not checked

eutra-5GC-Parameters-r15

Not checked

fdd-Add-UE-EUTRA-Capabilities-v15a0

Not checked

tdd-Add-UE-EUTRA-Capabilities-v15a0

Not checked

nonCriticalExtension SEQUENCE {

UE-EUTRA-Capability-v1610-IEs

highSpeedEnhParameters-v1610

Not checked

neighCellSI-AcquisitionParameters-v1610

Not checked

mbms-Parameters-v1610

Not checked

pdcp-Parameters-v1610

Not checked

mac-Parameters-v1610

Not checked

phyLayerParameters-v1610

Not checked

measParameters-v1610

Not checked

pur-Parameters-r16

Not checked

eutra-5GC-Parameters-v1610

Not checked

otherParameters-v1610

Not checked

dl-DedicatedMessageSegmentation-r16

Not checked

mmtel-Parameters-v1610

Not checked

irat-ParametersNR-v1610

Not checked

rf-Parameters-v1610

Not checked

mobilityParameters-v1610

Not checked

ue-BasedNetwPerfMeasParameters-v1610

Not checked

sl-Parameters-v1610

Not checked

fdd-Add-UE-EUTRA-Capabilities-v1610

Not checked

tdd-Add-UE-EUTRA-Capabilities-v1610

Not checked

nonCriticalExtension SEQUENCE {}

Not checked

}

}

}

}

}

Table 8.5.4.1.3.3-3: UEcapabilityEnquiry (step 19a1, Table 8.5.4.1.3.2-1)

Derivation path: 36.508 clause 4.6.1 table 4.6.1-22

Information Element

Value/Remark

Comment

Condition

UECapabilityEnquiry ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

ueCapabilityEnquiry-r8 SEQUENCE {

Numbering of entries is according to conditions met

According to inter-RAT capabilities of UE

ue-RadioAccessCapRequest[i1]

utran

This entry is present if the UE is capable of any mode (FDD/TDD) in UMTS.

pc_FDD, pc_TDD_HCR, pc_TDD_LCR, pc_TDD_VHCR

ue-RadioAccessCapRequest[i2]

geran-cs

pc_GERAN and pc_CS

ue-RadioAccessCapRequest[i3]

geran-ps

pc_GERAN and pc_PS

ue-RadioAccessCapRequest[i4]

cdma2000-1XRTT

pc_1xRTT,pc_HRPD

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

Table 8.5.4.1.3.3-4: UECapabilityInformation (step 19a2, Table 8.5.4.1.3.2-1)

Derivation path: 36.508 clause 4.6.1 table 4.6.1-23

Information Element

Value/Remark

Comment

Condition

UECapabilityInformation ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

ueCapabilityInformation-r8 SEQUENCE { SIZE (1..maxRAT-Capabilities)) OF SEQUENCE {

Stated capability shall be compatible with 3GPP TS 36.523-2 (ICS statements) and the user settings

rat-Type[i1]

utran

pc_FDD, pc_TDD_HCR, pc_TDD_LCR, pc_TDD_VHCR

ueCapabilitiesRAT-Container[i1] OCTET STRING {}

ueCapabilitiesRAT-Container-UTRAN

Encoded as an INTER RAT HANDOVER INFO messagewith UMTS TDD capabilities as defined in 3GPP TS 25.331 [17].

pc_TDD_HCR OR pc_TDD_LCR OR pc_TDD_VHCR

(pc_TDD_LCR AND pc_FDD) OR (pc_TDD_HCR AND pc_FDD)  OR (pc_TDD_VHCR AND pc_FDD)) (Note 1)

Encoded as an INTER RAT HANDOVER INFO message with UMTS FDD capabilities as defined in 3GPP TS 25.331 [17].

pc_FDD

(pc_TDD_LCR AND pc_FDD) OR (pc_TDD_HCR AND pc_FDD)  OR (pc_TDD_VHCR AND pc_FDD)) (Note 1)

rat-Type[i2]

geran-cs

pc_GERAN and pc_CS

ueCapabilitiesRAT-Container [i2] OCTET STRING {}

ueCapabilitiesRAT-Container-GERAN-CS

Encoded as the concatenation of IEs MS classmark 2 and MS classmark 3 as defined in 3GPP TS 24.008 [32].

pc_GERAN and pc_CS

rat-Type[i3]

geran-ps

pc_GERAN and pc_PS

ueCapabilitiesRAT-Container [ i3] OCTET STRING {}

ueCapabilitiesRAT-Container-GERAN-PS

Encoded as MS radio access capability IE as defined in 3GPP TS 24.008 [32].

pc_GERAN and pc_PS

rat-Type[i4]

cdma2000-1XRTT

pc_1xRTT, pc_HRPD

ueCapabilitiesRAT-Container [ i4] OCTET STRING {}

Not checked

Encoded as A21 Mobile Subscription Information as defined in 3GPP2 A.S0008-C v4.0 [33].

pc_1xRTT, pc_HRPD

nonCriticalExtension SEQUENCE {}

Not present

}

}

}

}

Table 8.5.4.1.3.3-5: ueCapabilitiesRAT-Container-UTRAN

Derivation path: 25.331 clause 11.2

Information Element

Value/Remark

Comment

Condition

ueCapabilitiesRAT-Container-UTRAN ::= SEQUENCE {

predefinedConfigStatusList CHOICE {

absent

NULL

}

uE-SecurityInformation

Not checked

The value of start CS is not used for LTE to UMTS handover in Rel-8

ue-CapabilityContainer CHOICE {

present

Not checked

Container including UE radio access capability

}

v390NonCriticalExtensions CHOICE {

present SEQUENCE {

interRATHandoverInfo-v390ext

Not checked

Positioning capability and dummy field

v3a0NonCriticalExtensions SEQUENCE {

interRATHandoverInfo-v3a0ext

Not checked

Positioning capability

laterNonCriticalExtensions SEQUENCE {

interRATHandoverInfo-v3d0ext

Not checked

Deprecated information

interRATHandoverInfo-r3-add-ext

Not checked if present

UE radio access capability for bands VIII to XIV, UE radio access capability extension, support of 2 DRX schemes in CELL_PCH, support of E-DPDCH power interpolation

v3g0NonCriticalExtensions SEQUENCE {

interRATHandoverInfo-v3g0ext

Not checked

Positioning capability extension

v4b0NonCriticalExtensions SEQUENCE {

interRATHandoverInfo-v4b0ext

Checked

Access Stratum Release indicator

v4d0NonCriticalExtensions SEQUENCE {

interRATHandoverInfo-v4d0ext

Not checked if present

LCR TDD UE capability

v590NonCriticalExtensions SEQUENCE {

interRATHandoverInfo-v590ext

Not checked if present

Predefined configuration status information compressed, UE radio access capability compressed

v690NonCriticalExtensions SEQUENCE {

interRATHandoverInfo-v690ext SEQUENCE {

ue-SecurityInformation2

Present but value not checked

START PS

pc_Featr Grp_8

ue-SecurityInformation2

Not present

NOT pc_FeatrGrp_8

ue-RadioAccessCapabilityComp

Not checked

RF capability for bands VIII to XIV

ue-RadioAccessCapabilityComp2

Present but value not checked

UE radio access capability comp 2

pc_FDD AND UE reportsF DD capabilities (Note1)

ue-RadioAccessCapabilityComp2

Not checked if present

UE radio access capability comp 2

NOT (pc_FDD AND UE reportsF DD capabilities) (Note 1)

}

v6b0NonCriticalExtensions SEQUENCE {

interRATHandoverInfo-v6b0ext

Not checked if present

Support for SIB11bis

v6e0NonCriticalExtensions SEQUENCE {

interRATHandoverInfo-v6e0ext

Not checked if present

Support of FDPCH

v770NonCriticalExtensions SEQUENCE {

interRATHandoverInfo-v770ext

Not checked if present

TDD RF and physical channel capability extensions in Rel-7, support of GANSS, support of MAC-ehs, LCR TDD UE specific capability information

v790nonCriticalExtensions SEQUENCE {

interRATHandoverInfo-v790ext

Not checked if present

Support of E-DPCCH power boosting

v860NonCriticalExtensions0 SEQUENCE {

interRATHandoverInfo-v860ext

Not checked if present

UE radio access capability for additional bands, Rel-8 HS-DSCH physical layer category, support of MAC-iis

v880NonCriticalExtensions SEQUENCE {

Present but value not checked

pc_TDD_LCR AND NOT px_NoTDD_LCR_onLTE

(Note 1)

v880NonCriticalExtensions SEQUENCE {

Not checked if present

NOT (pc_TDD_LCR AND NOT px_NoTDD_LCR_onLTE

) (Note 1)

v920NonCritical ExtensionsinterRATHandoverInfo-v880ext

Not checked

Support for priority reselection in UTRAN, Rel-8 radio access capability extensions for LCR TDD (e.g. multi-carrier operation)

SEQUENCE {

Not checked if present

interRATHandoverInfo-v920ext

Not checked if present

v8b0NonCritical Extensions SEQUENCE {

Present but value not checked

pc_TDD_LCR AND NOT px_NoTDD_LCR_onLTE

(Note 1)

v8b0NonCritical Extensions SEQUENCE {

Not checked if present

NOT (pc_TDD_LCR AND NOT px_NoTDD_LCR_onLTE

) (Note 1)

interRATHandoverInfo-v8b0ext

Not checked if present

v950NonCritical Extensions SEQUENCE {

interRATHandoverInfo-v950ext

Not checked if present

va40NonCritical Extensions SEQUENCE {

interRATHandoverInfo-va40ext

Not checked if present

va80NonCriticalExtensions SEQUENCE {

Not checked if present

interRATHandoverInfo-va80ext

Not checked if present

vb50NonCriticalExtensions SEQUENCE {

Not checked if present

interRATHandoverInfo-vb50ext

Not checked if present

vb70NonCriticalExtensions SEQUENCE {

Not checked if present

interRATHandoverInfo-vb70ext

Not checked if present

vbc0NonCriticalExtensions SEQUENCE {

Not checked if present

interRATHandoverInfo-vbc0ext

Not checked if present

vc50NonCriticalExtensions SEQUENCE {

Not checked if present

interRATHandoverInfo-vc50ext

Not checked if present

nonCritical Extensions SEQUENCE {}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

Note 1: When the UE supports more than one mode (e.g. pc_FDD and pc_TDD_HCR) then the UE is expected to report in the UTRA Container the capabilities associated with one of the supported modes.

Table 8.5.4.1.3.3-6: ueCapabilitiesRAT-Container-GERAN-CS

Derivation path: 25.331 clause 11.2

Information Element

Value/Remark

Comment

Condition

Mobile Station Classmark 2

First byte is 33H

Second byte is 3.

Third, Fourth and Fifth bytes are ignored.

Mobile Station Classmark 3

CSN.1 decoding shall be successful and the contents shall indicate that E-UTRA FDD or EUTRA TDD or both is supported.

Other values are not checked.

Table 8.5.4.1.3.3-7: ueCapabilitiesRAT-Container-GERAN-PS

Derivation path: 25.331 clause 11.2

Information Element

Value/Remark

Comment

Condition

MS Radio Access Capability

CSN.1 decoding shall be succesful and the contents shall indicate that E-UTRA FDD or EUTRA TDD or both is supported.

Other values are not checked.

8.5.4.2 Network-requested CA Band Combination Capability Signalling / Number of UE supported CA band combinations less than or equal to 128

8.5.4.2.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state }

ensure that {

when { UE supporting 128 or less CA band combinations receives a UECapabilityEnquiry message with IE requestedFrequencyBands indication prioritizing frequency band X}

then { UE transmits a UECapabilityInformation message with IE supportedBandCombination with the first 2DL+1UL CA band combination containing band X and including IE requestedBands with the same content as in the IE requestedFrequencyBands received in the UECapabilityEnquiry message }

}

8.5.4.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331 clauses 5.6.3.3, 5.6.22.2, 5.6.22.3.

[TS 36.331, clause 5.6.3.3]

The UE shall:

1> set the contents of UECapabilityInformation message as follows:

2> if the ue-CapabilityRequest includes eutra:

3> include the UE-EUTRA-Capability within a ue-CapabilityRAT-Container and with the rat-Type set to eutra;

….

3> if the UECapabilityEnquiry message includes requestedFrequencyBands and UE supports requestedFrequencyBands:

4> create a set of band combinations supported by the UE, including non-CA combinations, target for being included in supportedBandCombination while observing the following order (i.e. listed in order of decreasing priority):

– include all non-CA bands, regardless of whether UE supports carrier aggregation, only:

– if the UE includes ue-Category-v1020 (i.e. indicating category 6 to 8); or

– if for at least one of the non-CA bands, the UE supports more MIMO layers with TM9 and TM10 than implied by the UE category; or

– the UE supports TM10 with one or more CSI processes;

– include all 2DL+1UL CA band combinations, only consisting of bands included in requestedFrequencyBands;

– include all other 2DL+1UL CA band combinations;

– include all other CA band combinations, only consisting of bands included in requestedFrequencyBands, and prioritized in the order of requestedFrequencyBands, (i.e. first include remaining band combinations containing the first-listed band, then include remaining band combinations containing the second-listed band, and so on);

4> include in supportedBandCombination as many of the target band combinations as possible, determined according to the above, while observing the priority order;

4> include in supportedBandCombinationAdd as many of the remaining target band combinations as possible, i.e. the target band combinations the UE was not able to include in supportedBandCombination, and limited to those consisting of bands included in requestedFrequencyBands, while observing the priority order;

4> indicate in requestedBands the same bands and in the same order as included in the received requestedFrequencyBands;

3> else

4> create a set of band combinations supported by the UE, including non-CA combinations, target for being included in supportedBandCombination:

– include all non-CA bands, regardless of whether UE supports carrier aggregation, only:

– if the UE includes ue-Category-v1020 (i.e. indicating category 6 to 8); or

– if for at least one of the non-CA bands, the UE supports more MIMO layers with TM9 and TM10 than implied by the UE category; or

– the UE supports TM10 with one or more CSI processes;

– include all 2DL+1UL CA band combinations;

– include all other CA band combinations;

4> include in supportedBandCombination as many of the target band combinations as possible, determined according to the above;

4> if the number of non-CA and CA band combinations supported by UE exceeds the maximum number of band combinations of supportedBandCombination, the selection of subset of band combinations is up to UE implementation;

NOTE: If the UECapabilityEnquiry message does not include requestedFrequencyBands, UE does not include supportedBandCombinationAdd.

….

1> if the RRC message segmentation is enabled based on the field rrc-SegAllowed received, and the encoded RRC message is larger than the maximum supported size of a PDCP SDU specified in TS 36.323 [8]:

2> initiate the UL message segment transfer procedure as specified in clause 5.6.22;

1> else:

2> submit the UECapabilityInformation message to lower layers for transmission, upon which the procedure ends;

[TS 36.331, clause 5.6.22.2]

A UE capable of UL RRC message segmentation in RRC_CONNECTED will initiate the procedure when the following conditions are met:

1> if the RRC message segmentation is enabled based on the field rrc-SegAllowed received, and

1> if the encoded RRC message is larger than the maximum supported size of a PDCP SDU specified in TS 36.323 [8];

Upon initiating the procedure, the UE shall:

  1. initiate transmission of the ULDedicatedMessageSegment message as specified in 5.6.22.3;

[TS 36.331, clause 5.6.22.3]

The UE shall segment the encoded RRC PDU based on the maximum supported size of a PDCP SDU specified in TS 36.323 [8]. UE shall minimize the number of segments and set the contents of the ULDedicatedMessageSegment messages as follows:

1> For each new UL DCCH message, set the segmentNumber to 0 for the first message segment and increment the segmentNumber for each subsequent RRC message segment;

1> set rrc-MessageSegmentContainer to include the segment of the UL DCCH message corresponding to the segmentNumber;

1> if the segment included in the rrc-MessageSegmentContainer is the last segment of the UL DCCH message:

2> set the rrc-MessageSegmentType to lastSegment;

1> else:

2> set the rrc-MessageSegmentType to notLastSegment;

1> submit all the ULDedicatedMessageSegment messages generated for the segmented RRC message to lower layers for transmission in ascending order based on the segmentNumber, upon which the procedure ends.

8.5.4.2.3 Test description

8.5.4.2.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].

8.5.4.2.3.2 Test procedure sequence

Table 8.5.4.2.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits a UECapabilityEnquiry message to request UE radio access capability information for E UTRA only with rrc-segAllowed-r16 set to enabled. The IE requestedFrequencyBands is not included

<–

UECapabilityEnquiry

EXCEPTION: The "lower case letter" identifies a step sequence that takes place depending on the size of UE capability message.

IF pc_LTE_UL_Segmentation and UE’s encoded UECapabilityInformation message >= Max PDCP SDU size then steps 2a1 will be performed else step 2b1 will be performed

EXCEPTION: Step 2a1 is repeated a maximum of 16 times or till rrc-MessageSegmentType-16 IE within the UlDedicatedMessageSegment message indicate rrc-MessageSegmentType-r16 = lastSegment.

2a1

UE transmits segments of UECapabilityInformation message contained within the rrc-MessageSegmentContainer-r16 IE of the ULDedicatedMessageSegment message.

–>

ULDedicatedMessageSegment

2b1

UE transmits a UECapabilityInformation message.

–>

UECapabilityInformation

The reference to supportedBandCombinations and supportedBandListEUTRA below refers to the IEs received by the SS in the UECapabilityInformation message in step 2.

The SS locates the first 2DL+1UL CA band combination in the supportedBandCombination-r10 sequence. If the first CA band combination is an intra-band combination the SS stores the value of the IE bandEUTRA-r10 in the test variables B1 and B2. If the first CA band combination is an inter-band combination the SS stores the value of the IE bandEUTRA-r10 for each of the bands in the test variables B1 and B2 respectively.

The SS searches in the supportedBandCombination-r10 sequence for a 2DL+1UL CA band combination where the band or bands are different from the bands stored in the test variables B1 and B2. The SS stores the value of the IE bandEUTRA-r10 of the band (intra-band case) or of one of the bands (inter-band case) in the test variable B3.

3

The SS transmits a UECapabilityEnquiry message including the IE requestedFrequencyBands-r11 with the first requested frequency band entry set to the value of the test variable B3, the second entry to the value of the test variable B1 and the successive entries 3 to n set to frequency bands different from B1 and B3 derived from the UE indicated supported bands in IE supportedBandListEUTRA received by the SS in the UECapabilityInformation message in step 2 and where n is MIN(16, number of UE supported bands) and with rrc-segAllowed-r16 set to enabled.

<–

UECapabilityEnquiry

EXCEPTION: The "lower case letter" identifies a step sequence that takes place depending on the size of UE capability message.

IF pc_LTE_UL_Segmentation and UE’s encoded UECapabilityInformation message >= Max PDCP SDU size then steps 4a1 and 4a2 will be performed else step 4b1 will be performed

EXCEPTION: Step 4a1 is repeated a maximum of 16 times or till rrc-MessageSegmentType-16 IE within the UlDedicatedMessageSegment message indicate rrc-MessageSegmentType-r16 = lastSegment.

4a1

UE transmits segments of UECapabilityInformation message contained within the rrc-MessageSegmentContainer-r16 IE of the ULDedicatedMessageSegment message.

–>

ULDedicatedMessageSegment

4a2

Check: Is the received UE radio access capability information as per the ue-CapabilityRequest variable?

1

P

4

Check: Does the UE transmit a UECapabilityInformation message with IE supportedBandCombination-r10 where the first listed 2DL+1UL CA band combination contains a band equal to the band stored in test variable B3; and where IE requestedBands have the same content as the IE requestedFrequencyBands-r11 sent by the SS in step 3? (Note 1)

–>

UECapabilityInformation

1

P

Note 1: Acc. to TS 36.331 (ASN.1), each CA band combination listed in IE supportedBandCombination-r10 is denominated with the contained bandEUTRA-r10 element (in case of Intra-band) resp. bandEUTRA-r10 elements (in case of inter-band). Extended bands (i.e. band > 64) were defined from TS 36.331 v1090 (ASN.1) onwards and the respective IE bandEUTRA-r10 is always encoded as ’64’. Which means that it is not possible to distinguish among multiple reported extended band candidates in IE supportedBandCombination-r10.
As a consequence, the Check procedure in step 4 cannot distinguish between extended bands in case that the UE supports mulitple CA band combinations containing different extended bands or a CA band combination involving more than one extended band. In such case, the test procedure shall issue an INCONC (= inconclusive) verdict with the following error message:
Ambiguity due to more than one extended band reported in the supported CA band combinations.

8.5.4.2.3.3 Specific message contents

Table 8.5.4.2.3.3-1: UECapabilityEnquiry (step 1, Table 8.5.4.2.3.2-1)

Derivation path: 36.508 clause 4.6.1 table 4.6.1-22

Information Element

Value/Remark

Comment

Condition

UECapabilityEnquiry ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

ueCapabilityEnquiry-r8 SEQUENCE {

ue-CapabilityRequest SEQUENCE (SIZE (1..maxRAT-Capabilities)) OF SEQUENCE {

1 entry

E-UTRA only

RAT-Type[1]

Eutra

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

rrc-SegAllowed-r16

enabled

}

}

}

}

}

}

}

}

}

}

}

}

}

Table 8.5.4.2.3.3-2: UECapabilityInformation (steps 2a2 and 2b1, Table 8.5.4.2.3.2-1)

Derivation path: 36.508 clause 4.6.1 table 4.6.1-23

Information Element

Value/Remark

Comment

Condition

UECapabilityInformation ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

ueCapabilityInformation-r8 SEQUENCE {

ue-CapabilityRAT-ContainerList SEQUENCE (SIZE (0..maxRAT-Capabilities)) of SEQUENCE {

1 entry

rat-Type[1]

Eutra

E-UTRA only

ueCapabilityRAT-Container[1] OCTET STRING {

UE-EUTRA-Capability SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

rf-Parameters-v1020 {

supportedBandCombination-r10 {

See Table 8.5.4.2.3.2-1 for SS actions to set test variables B1, B2 and B3 based on the content in the IE supportedBandCombination-r10.

}

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

rf-Parameters-v1090 {

supportedBandCombination-v1090 {

See Table 8.5.4.2.3.2-1 for SS actions to set test variables B1, B2 and B3 based on the content in the IE supportedBandCombination-r10 and supportedBandCombination-v1090.

}

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

rf-Parameters-v1180 {

freqBandRetrieval-r11

Supported

requestedBands-r11

Not present

supportedBandCombinationAdd-r11

Not present

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

Table 8.5.4.2.3.3-3: UECapabilityEnquiry (step 3, Table 8.5.4.2.3.2-1)

Derivation path: 36.508 clause 4.6.1 table 4.6.1-22

Information Element

Value/Remark

Comment

Condition

UECapabilityEnquiry ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

ueCapabilityEnquiry-r8 SEQUENCE {

ue-CapabilityRequest SEQUENCE (SIZE (1..maxRAT-Capabilities)) OF SEQUENCE {

1 entry

E-UTRA only

RAT-Type[1]

Eutra

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

requestedFrequencyBands-r11

n entries, where n is equal to UE supported bands or 16 if number of UE supported bands exceeds 16.

FreqBandIndicator-r11 [1]

B3

See Table 8.5.4.2.3.2-1 for definition of B3.

FreqBandIndicator-r11 [2]

B1

See Table 8.5.4.2.3.2-1 for definition of B1.

FreqBandIndicator-r11 [k]

For k=3 to n set to value different from values set in preceding entries FreqBandIndicator-r11 [1] to FreqBandIndicator-r11 [k-1],

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

rrc-SegAllowed-r16

enabled

}

}

}

}

}

}

}

}

}

}

}

}

}

Table 8.5.4.2.3.3-4: UECapabilityInformation (steps 4a2 and 4b1, Table 8.5.4.2.3.2-1)

Derivation path: 36.508 clause 4.6.1 table 4.6.1-23

Information Element

Value/Remark

Comment

Condition

UECapabilityInformation ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

ueCapabilityInformation-r8 SEQUENCE {

ue-CapabilityRAT-ContainerList SEQUENCE (SIZE (0..maxRAT-Capabilities)) of SEQUENCE {

1 entry

rat-Type[1]

Eutra

E-UTRA only

ueCapabilitiesRAT-Container[1] OCTET STRING {

UE-EUTRA-Capability SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

rf-Parameters-v1020 {

supportedBandCombination-r10 {

See step 4 in Table 8.5.4.2.3.2-1 for SS actions for how to check content

}

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

rf-Parameters-v1090 {

supportedBandCombination-v1090 {

See step 4 in Table 8.5.4.2.3.2-1 for SS actions for how to check content

}

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

.. rf-Parameters-v1180 {

.. freqBandRetrieval-r11

Supported

.. requestedBands-r11

Same number of entries and content as SS sent in IE requestedFrequencyBands in the UEcapabilityEnquiry message in step 3

supportedBandCombinationAdd-r11

Not present

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

8.5.4.3 Network-requested CA Band Combination Capability Signalling / Number of UE supported CA band combinations exceeds 128

8.5.4.3.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state }

ensure that {

when { UE supporting more than 128 CA band combinations receives a UECapabilityEnquiry message with IE requestedFrequencyBands indication prioritizing frequency band X}

then { UE transmits a UECapabilityInformation message with IE supportedBandCombination with the first 2DL+1UL CA band combination containing band X and including IEs supportedBandCombinationAdd and requestedBands where IE requestedBands contains the same content as in the IE requestedFrequencyBands received in the UECapabilityEnquiry message }

}

(2)

with { UE in RRC_CONNECTED state }

ensure that {

when { UE supporting more than 128 CA band combinations receives a UECapabilityEnquiry message not including IE requestedFrequencyBands }

then { UE transmits a UECapabilityInformation message including IE supportedBandCombination, but not including IE supportedBandCombinationAdd }

}

8.5.4.3.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331 clauses 5.6.3.3, 5.6.22.2, 5.6.22.3.

[TS 36.331, clause 5.6.3.3]

The UE shall:

1> set the contents of UECapabilityInformation message as follows:

2> if the ue-CapabilityRequest includes eutra:

3> include the UE-EUTRA-Capability within a ue-CapabilityRAT-Container and with the rat-Type set to eutra;

….

3> if the UECapabilityEnquiry message includes requestedFrequencyBands and UE supports requestedFrequencyBands:

4> create a set of band combinations supported by the UE, including non-CA combinations, target for being included in supportedBandCombination while observing the following order (i.e. listed in order of decreasing priority):

– include all non-CA bands, regardless of whether UE supports carrier aggregation, only:

– if the UE includes ue-Category-v1020 (i.e. indicating category 6 to 8); or

– if for at least one of the non-CA bands, the UE supports more MIMO layers with TM9 and TM10 than implied by the UE category; or

– the UE supports TM10 with one or more CSI processes;

– include all 2DL+1UL CA band combinations, only consisting of bands included in requestedFrequencyBands;

– include all other 2DL+1UL CA band combinations;

– include all other CA band combinations, only consisting of bands included in requestedFrequencyBands, and prioritized in the order of requestedFrequencyBands, (i.e. first include remaining band combinations containing the first-listed band, then include remaining band combinations containing the second-listed band, and so on);

4> include in supportedBandCombination as many of the target band combinations as possible, determined according to the above, while observing the priority order;

4> include in supportedBandCombinationAdd as many of the remaining target band combinations as possible, i.e. the target band combinations the UE was not able to include in supportedBandCombination, and limited to those consisting of bands included in requestedFrequencyBands, while observing the priority order;

4> indicate in requestedBands the same bands and in the same order as included in the received requestedFrequencyBands;

3> else

4> create a set of band combinations supported by the UE, including non-CA combinations, target for being included in supportedBandCombination:

– include all non-CA bands, regardless of whether UE supports carrier aggregation, only:

– if the UE includes ue-Category-v1020 (i.e. indicating category 6 to 8); or

– if for at least one of the non-CA bands, the UE supports more MIMO layers with TM9 and TM10 than implied by the UE category; or

– the UE supports TM10 with one or more CSI processes;

– include all 2DL+1UL CA band combinations;

– include all other CA band combinations;

4> include in supportedBandCombination as many of the target band combinations as possible, determined according to the above;

4> if the number of non-CA and CA band combinations supported by UE exceeds the maximum number of band combinations of supportedBandCombination, the selection of subset of band combinations is up to UE implementation;

NOTE: If the UECapabilityEnquiry message does not include requestedFrequencyBands, UE does not include supportedBandCombinationAdd.

….

1> if the RRC message segmentation is enabled based on the field rrc-SegAllowed received, and the encoded RRC message is larger than the maximum supported size of a PDCP SDU specified in TS 36.323 [8]:

2> initiate the UL message segment transfer procedure as specified in clause 5.6.22;

1> else:

2> submit the UECapabilityInformation message to lower layers for transmission, upon which the procedure ends;

[TS 36.331, clause 5.6.22.2]

A UE capable of UL RRC message segmentation in RRC_CONNECTED will initiate the procedure when the following conditions are met:

1> if the RRC message segmentation is enabled based on the field rrc-SegAllowed received, and

1> if the encoded RRC message is larger than the maximum supported size of a PDCP SDU specified in TS 36.323 [8];

Upon initiating the procedure, the UE shall:

  1. initiate transmission of the ULDedicatedMessageSegment message as specified in 5.6.22.3;

[TS 36.331, clause 5.6.22.3]

The UE shall segment the encoded RRC PDU based on the maximum supported size of a PDCP SDU specified in TS 36.323 [8]. UE shall minimize the number of segments and set the contents of the ULDedicatedMessageSegment messages as follows:

1> For each new UL DCCH message, set the segmentNumber to 0 for the first message segment and increment the segmentNumber for each subsequent RRC message segment;

1> set rrc-MessageSegmentContainer to include the segment of the UL DCCH message corresponding to the segmentNumber;

1> if the segment included in the rrc-MessageSegmentContainer is the last segment of the UL DCCH message:

2> set the rrc-MessageSegmentType to lastSegment;

1> else:

2> set the rrc-MessageSegmentType to notLastSegment;

1> submit all the ULDedicatedMessageSegment messages generated for the segmented RRC message to lower layers for transmission in ascending order based on the segmentNumber, upon which the procedure ends.

8.5.4.3.3 Test description

8.5.4.3.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].

8.5.4.3.3.2 Test procedure sequence

Table 8.5.4.3.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits a UECapabilityEnquiry message to request UE radio access capability information for E UTRA only with rrc-segAllowed-r16 set to enabled. The IE requestedFrequencyBands is not included

<–

UECapabilityEnquiry

EXCEPTION: The "lower case letter" identifies a step sequence that takes place depending on the size of UE capability message.

IF pc_LTE_UL_Segmentation and UE’s encoded UECapabilityInformation message >= Max PDCP SDU size then steps 2a1 and 2a2 will be performed else step 2b1 will be performed

EXCEPTION: Step 2a1 is repeated a maximum of 16 times or till rrc-MessageSegmentType-16 IE within the UlDedicatedMessageSegment message indicate rrc-MessageSegmentType-r16 = lastSegment.

2a1

UE transmits segments of UECapabilityInformation message contained within the rrc-MessageSegmentContainer-r16 IE of the ULDedicatedMessageSegment message.

–>

ULDedicatedMessageSegment

2a2

Check: Is the received UE radio access capability information as per the ue-CapabilityRequest variable?

2

P

2b1

Check: Does the UE transmit a UECapabilityInformation message including IE supportedBandCombination, but not including IE supportedBandCombinationAdd?

–>

UECapabilityInformation

2

P

The reference to supportedBandCombinations and supportedBandListEUTRA below refers to the IEs received by the SS in the UECapabilityInformation message in step 2.

The SS locates the first 2DL+1UL CA band combination in supportedBandCombination-r10 sequence. If the first CA band combination is an intra-band combination the SS stores the value of the IE bandEUTRA-r10 in the test variables B1 and B2. If the first CA band combination is an inter-band combination the SS stores the value of the IE bandEUTRA-r10 for each of the bands in the test variables B1 and B2 respectively.

The SS searches in the supportedBandCombination-r10 sequence for a 2DL+1UL CA band combination where the band or bands are different from the bands stored in the test variables B1 and B2. The SS stores the value of the IE bandEUTRA-r10 of the band (intra-band case) or of one of the bands (inter-band case) in the test variable B3.

3

The SS transmits a UECapabilityEnquiry message including the IE requestedFrequencyBands with the first requested frequency band entry set to the value of the test variable B3, the second entry to the value of the test variable B1 and the successive entries 3 to n set to frequency bands different from B1 and B3 derived from the UE indicated supported bands in IE supportedBandListEUTRA received by the SS in the UECapabilityInformation message in step 2 and where n is MIN(16, number of UE supported bands) and with rrc-segAllowed-r16 set to enabled.

<–

UECapabilityEnquiry

EXCEPTION: The "lower case letter" identifies a step sequence that takes place depending on the size of UE capability message.

IF pc_LTE_UL_Segmentation and UE’s encoded UECapabilityInformation message >= Max PDCP SDU size then steps 4a1 and 4a2 will be performed else step 4b1 will be performed

EXCEPTION: Step 4a1 is repeated a maximum of 16 times or till rrc-MessageSegmentType-16 IE within the UlDedicatedMessageSegment message indicate rrc-MessageSegmentType-r16 = lastSegment.

4a1

UE transmits segments of UECapabilityInformation message contained within the rrc-MessageSegmentContainer-r16 IE of the ULDedicatedMessageSegment message.

–>

ULDedicatedMessageSegment

4a2

Check: Is the received UE radio access capability information as per the ue-CapabilityRequest variable?

1

P

4b1

Check: Does the UE transmit a UECapabilityInformation message with IE supportedBandCombination-r11 where the first listed 2DL+1UL CA band combination contains a band equal to the band stored in test variable B3; and is including IEs supportedBandCombinationAdd and requestedBand; and where IE requestedBands have the same content as the IE requestedFrequencyBands-r11 sent by the SS in step 3? (Note 1)

–>

UECapabilityInformation

1

P

Note 1: Acc. to TS 36.331 (ASN.1), each CA band combination listed in IE supportedBandCombination-r10 is denominated with the contained bandEUTRA-r10 element (in case of Intra-band) resp. bandEUTRA-r10 elements (in case of inter-band). Extended bands (i.e. band > 64) were defined from TS 36.331 v1090 (ASN.1) onwards and the respective IE bandEUTRA-r10 is always encoded as ’64’. Which means that it is not possible to distinguish among multiple reported extended band candidates in IE supportedBandCombination-r10.
As a consequence, the Check procedure in step 4 cannot distinguish between extended bands in case that the UE supports multiple CA band combinations containing different extended bands or a CA band combination involving more than one extended band. In such case, the test procedure shall issue an INCONC (= inconclusive) verdict with the following error message:
Ambiguity due to more than one extended band reported in the supported CA band combinations.

8.5.4.3.3.3 Specific message contents

Table 8.5.4.3.3.3-1: UECapabilityEnquiry (step 1, Table 8.5.4.3.3.2-1)

Derivation path: 36.508 clause 4.6.1 table 4.6.1-22

Information Element

Value/Remark

Comment

Condition

UECapabilityEnquiry ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

ueCapabilityEnquiry-r8 SEQUENCE {

ue-CapabilityRequest SEQUENCE (SIZE (1..maxRAT-Capabilities)) OF SEQUENCE {

1 entry

E-UTRA only

RAT-Type[1]

Eutra

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

rrc-SegAllowed-r16

enabled

}

}

}

}

}

}

}

}

}

}

}

}

}

Table 8.5.4.3.3.3-2: UECapabilityInformation (steps 2a2 and 2b1, Table 8.5.4.3.3.2-1)

Derivation path: 36.508 clause 4.6.1 table 4.6.1-23

Information Element

Value/Remark

Comment

Condition

UECapabilityInformation ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

ueCapabilityInformation-r8 SEQUENCE {

ue-CapabilityRAT-ContainerList SEQUENCE (SIZE (0..maxRAT-Capabilities)) of SEQUENCE {

1 entry

rat-Type[1]

Eutra

E-UTRA only

ueCapabilityRAT-Container[1] OCTET STRING {

UE-EUTRA-Capability SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

rf-Parameters-v1020 {

supportedBandCombination-r10 {

See Table 8.5.4.3.3.2-1 for SS actions to set test variables B1, B2 and B3 based on the content in the IE supportedBandCombination-r10.

}

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

rf-Parameters-v1090 {

supportedBandCombination-v1090 {

See Table 8.5.4.3.3.2-1 for SS actions to set test variables B1, B2 and B3 based on the content in the IE supportedBandCombination-r10 and supportedBandCombination-v1090.

}

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

.. rf-Parameters-v1180 {

.. freqBandRetrieval-r11

Supported

.. requestedBands-r11

Not present

.. supportedBandCombinationAdd-r11

Not present

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

Table 8.5.4.3.3.3-3: UECapabilityEnquiry (step 3, Table 8.5.4.3.3.2-1)

Derivation path: 36.508 clause 4.6.1 table 4.6.1-22

Information Element

Value/Remark

Comment

Condition

UECapabilityEnquiry ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

ueCapabilityEnquiry-r8 SEQUENCE {

ue-CapabilityRequest SEQUENCE (SIZE (1..maxRAT-Capabilities)) OF SEQUENCE {

1 entry

E-UTRA only

RAT-Type[1]

Eutra

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

requestedFrequencyBands-r11

n entries, where n is equal to UE supported bands or 16 if number of UE supported bands exceeds 16.

FreqBandIndicator-r11 [1]

B3

See Table 8.5.4.3.3.2-1 for definition of B3.

FreqBandIndicator-r11 [2]

B1

See Table 8.5.4.3.3.2-1 for definition of B1.

FreqBandIndicator-r11 [k]

For k=3 to n set to value different from values set in preceding entries FreqBandIndicator-r11 [1] to FreqBandIndicator-r11 [k-1],

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

rrc-SegAllowed-r16

enabled

}

}

}

}

}

}

}

}

}

}

}

}

}

Table 8.5.4.3.3.3-4: UECapabilityInformation (steps 4a2 and 4b1, Table 8.5.4.3.3.2-1)

Derivation path: 36.508 clause 4.6.1 table 4.6.1-23

Information Element

Value/Remark

Comment

Condition

UECapabilityInformation ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE{

ueCapabilityInformation-r8 SEQUENCE {

ue-CapabilityRAT-ContainerList SEQUENCE (SIZE (0..maxRAT-Capabilities)) of SEQUENCE {

1 entry

rat-Type[1]

Eutra

E-UTRA only

ueCapabilityRAT-Container[1] OCTET STRING {

UE-EUTRA-Capability SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

rf-Parameters-v1020 {

supportedBandCombination-r10 {

See step 4 in Table 8.5.4.3.3.2-1 for SS actions for how to check content

}

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

rf-Parameters-v1090 {

supportedBandCombination-v1090 {

See step 4 in Table 8.5.4.3.3.2-1 for SS actions for how to check content

}

}

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

.. rf-Parameters-v1180 {

.. freqBandRetrieval-r11

Supported

.. requestedBands-r11

Same number of entries and content as SS sent in IE requestedFrequencyBands in the UECapabilityEnquiry message in step 3

.. supportedBandCombinationAdd-r11

Any value

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

}

8.5.4.4 UE Capability Transfer/ Success/ UE Cat 0/ UE Paging Info

8.5.4.4.1 Test Purpose (TP)

(1)

with { UE in RRC_CONNECTED state }

ensure that {

when { UE supporting Cat 0 receives an UECapabilityEnquiry message }

then { UE transmits UECapabilityInformation message with IE UE-RadioPagingInfo including ue-Category }

}

8.5.4.4.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 36.331, clause 5.6.3.3

[TS 36.331, clause 5.6.3.3]

The UE shall:

1> set the contents of UECapabilityInformation message as follows:

2> if the ue-CapabilityRequest includes eutra:

3> if the UE is a category 0 UE according to TS 36.306 [5]:

4> include ue-RadioPagingInfo including ue-Category;

8.5.4.4.3 Test description

8.5.4.4.3.1 Pre-test conditions

System Simulator:

– Cell 1

UE:

None.

Preamble:

– The UE is in state Generic RB Established (state 3) on Cell 1 according to [18].

8.5.4.4.3.2 Test procedure sequence

Table 8.5.4.4.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The SS transmits a UECapabilityEnquiry message

<–

UECapabilityEnquiry

2

Check: Does the UE transmit a UECapabilityInformation message with IE UE-RadioPagingInfo including ue-Category ?

–>

UECapabilityInformation

1

P

8.5.4.4.3.3 Specific message contents

Table 8.5.4.4.3.3-1: UEcapabilityEnquiry (step 1 Table 8.5.4.4.3.2-1)

Derivation path: 36.508 clause 4.6.1 table 4.6.1-22

Information Element

Value/Remark

Comment

Condition

UECapabilityEnquiry ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

ueCapabilityEnquiry-r8 SEQUENCE {

ue-CapabilityRequest SEQUENCE (SIZE (1..maxRAT-Capabilities)) OF SEQUENCE {

1 entry

E-UTRA only

RAT-Type

eutra

}

}

}

}

}

Table 8.5.4.4.3.3-2: UECapabilityInformation (step 2, Table 8.5.4.4.3.2-1)

Derivation Path: 36.508, clause 4.6.1, Table 4.6.1-23

Information Element

Value/remark

Comment

Condition

UECapabilityInformation ::= SEQUENCE {

criticalExtensions CHOICE {

c1 CHOICE {

ueCapabilityInformation-r8 SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

ue-RadioPagingInfo-r12 SEQUENCE {

ue-Category-v1250

0

}

}

}

}

}

}

}