[srslte-users] RRC establishment cause / srsue UE Capabilities / FeatureGroupIndication flag in ue.conf and FGI rel9 & rel10 addons /
Marc T.
m.triefelder at gmail.com
Fri Jun 12 08:41:02 UTC 2020
Hi srsLTE Team,
after a while of testing with srsue i have some questions and maybe found little bugs or issues.
1) RRC Establishment Cause
I observed with srsue 19.04 the RRC establishment case was „mo-Data“; while with 20.04. its "mo-signalling".
a trace excerpt from 19.04
LTE Radio Resource Control (RRC) protocol
UL-CCCH-Message
message: c1 (0)
c1: rrcConnectionRequest (1)
rrcConnectionRequest
criticalExtensions: rrcConnectionRequest-r8 (0)
rrcConnectionRequest-r8
ue-Identity: randomValue (1)
randomValue: 0dc0211220 [bit length 40, 0000 1101 1100 0000 0010 0001 0001 0010 0010 0000 decimal value 59057967648]
establishmentCause: mo-Data (4)
spare: 00 [bit length 1, 7 LSB pad bits, 0... .... decimal value 0]
a trace excerpt from 20.04
LTE Radio Resource Control (RRC) protocol
UL-CCCH-Message
message: c1 (0)
c1: rrcConnectionRequest (1)
rrcConnectionRequest
criticalExtensions: rrcConnectionRequest-r8 (0)
rrcConnectionRequest-r8
ue-Identity: s-TMSI (0)
s-TMSI
mmec: 01 [bit length 8, 0000 0001 decimal value 1]
m-TMSI: ffbcfce7 [bit length 32, 1111 1111 1011 1100 1111 1100 1110 0111 decimal value 4290575591]
establishmentCause: mo-Signalling (3)
spare: 00 [bit length 1, 7 LSB pad bits, 0... .... decimal value 0]
Is there a way to change or manipulate the RRC establishment Cause? Or how is that handled?
Could i also force another RRC establishment cause like „highPriorityAccess“?
eg. (excerpt from a S1 trace, commercial UE)
Item 4: id-RRC-Establishment-Cause
ProtocolIE-Field
id: id-RRC-Establishment-Cause (134)
criticality: ignore (1)
value
RRC-Establishment-Cause: highPriorityAccess (1)
As far as I’m aware of it it should be a USIM flag, in the ACC field. But even though i use a USIM (with this flag set) and a PCSC card reader the RRC establishment cause from srsue isn’t changed (mo-data or mo-signalling, depending on the srsue version).
2) srsue UE Capabilities and supported Bands
Lets start with an more general question:
Beside the fact i can tune any earfcn i wanted to ask which LTE Bands are actually supported by srsue?
I’m asking because i had a possibility to test srsue with a B65 (earfcn eg. 66236 or 66211) eNB, and it won’t work - i believe it doesn’t work cos srsue sent out truncated UE capabilities - it got cut exactly at the suportedBandEUTRA section, see below.
If you want more details (logs, traces, etc) just let me know.
Band7 - earfcn 3200 (ueCat4rel10) example - all fine, srsue attaches and works rocks solid.
LTE Radio Resource Control (RRC) protocol
UL-DCCH-Message
message: c1 (0)
c1: ueCapabilityInformation (7)
ueCapabilityInformation
rrc-TransactionIdentifier: 2
criticalExtensions: c1 (0)
c1: ueCapabilityInformation-r8 (0)
ueCapabilityInformation-r8
ue-CapabilityRAT-ContainerList: 1 item
Item 0
UE-CapabilityRAT-Container
rat-Type: eutra (0)
ueCapabilityRAT-Container: c98000018000f706ec4d001000a00000
UE-EUTRA-Capability
accessStratumRelease: rel10 (2)
ue-Category: 4
pdcp-Parameters
supportedROHC-Profiles
...0 .... profile0x0001-r15: False
.... 0... profile0x0002-r15: False
.... .0.. profile0x0003-r15: False
.... ..0. profile0x0004-r15: False
.... ...0 profile0x0006-r15: False
0... .... profile0x0101-r15: False
.0.. .... profile0x0102-r15: False
..0. .... profile0x0103-r15: False
...0 .... profile0x0104-r15: False
phyLayerParameters
.... 0... ue-TxAntennaSelectionSupported: False
.... .0.. ue-SpecificRefSigsSupported: False
rf-Parameters
supportedBandListEUTRA: 1 item
Item 0
SupportedBandEUTRA
bandEUTRA: 7
..0. .... halfDuplex: False
measParameters
bandListEUTRA: 1 item
Item 0
BandInfoEUTRA
interFreqBandList: 1 item
Item 0
InterFreqBandInfo
1... .... interFreqNeedForGaps: True
[bandEUTRA: 7 -> band 7]
featureGroupIndicators: ee0dd89a [bit length 32, 1110 1110 0000 1101 1101 1000 1001 1010 decimal value 3993884826]
1... .... = Indicator 1: Intra-subframe freq hopping for PUSCH scheduled by UL grant; DCI format 3a; Aperiodic CQI/PMI/RI report on PUSCH: Mode 2-0 & 2-2 - Supported
.1.. .... = Indicator 2: Simultaneous CQI & ACK/NACK on PUCCH (format 2a/2b); Absolute TPC command for PUSCH; Resource alloc type 1 for PDSCH; Periodic CQI/PMI/RI report on PUCCH: Mode 2-0 & 2-1 - Supported
..1. .... = Indicator 3: 5bit RLC UM SN; 7bit PDCP SN - Supported
...0 .... = Indicator 4: Short DRX cycle - Not supported
.... 1... = Indicator 5: Long DRX cycle; DRX command MAC control element - Supported
.... .1.. = Indicator 6: Prioritised bit rate - Supported
.... ..1. = Indicator 7: RLC UM - Supported
.... ...0 = Indicator 8: EUTRA RRC_CONNECTED to UTRA CELL_DCH PS handover - Not supported
0... .... = Indicator 9: EUTRA RRC_CONNECTED to GERAN GSM_Dedicated handover - Not Supported
.0.. .... = Indicator 10: EUTRA RRC_CONNECTED to GERAN (Packet_) Idle by Cell Change Order; EUTRA RRC_CONNECTED to GERAN (Packet_) Idle by Cell Change Order with NACC - Not supported
..0. .... = Indicator 11: EUTRA RRC_CONNECTED to CDMA2000 1xRTT CS Active handover - Not supported
...0 .... = Indicator 12: EUTRA RRC_CONNECTED to CDMA2000 HRPD Active handover - Not supported
.... 1... = Indicator 13: Inter-frequency handover (within FDD or TDD) - Supported
.... .1.. = Indicator 14: Measurement reporting event: Event A4 - Neighbour > threshold; Measurement reporting event: Event A5 - Serving < threshold1 & Neighbour > threshold2 - Supported
.... ..0. = Indicator 15: Measurement reporting event: Event B1 - Neighbour > threshold - Not supported
.... ...1 = Indicator 16: non-ANR related periodical measurement reporting - Supported
1... .... = Indicator 17: ANR related intra-frequency measurement reporting events - Supported
.1.. .... = Indicator 18: ANR related inter-frequency measurement reporting events - Supported
..0. .... = Indicator 19: ANR related inter-RAT measurement reporting events - Not supported
...1 .... = Indicator 20: SRB1 and SRB2 for DCCH + 8x AM DRB; SRB1 and SRB2 for DCCH + 5x AM DRB + 3x UM DRB (if indicator 7 is supported) - Supported
.... 1... = Indicator 21: Predefined intra- and inter-subframe frequency hopping for PUSCH with N_sb > 1; Predefined inter-subframe frequency hopping for PUSCH with N_sb > 1 - Supported
.... .0.. = Indicator 22: UTRAN measurements, reporting and measurement reporting event B2 in E-UTRA connected mode - Not supported
.... ..0. = Indicator 23: GERAN measurements, reporting and measurement reporting event B2 in E-UTRA connected mode - Not supported
.... ...0 = Indicator 24: 1xRTT measurements, reporting and measurement reporting event B2 in E-UTRA connected mode - Not supported
1... .... = Indicator 25: Inter-frequency measurements and reporting in E-UTRA connected mode - Supported
.0.. .... = Indicator 26: HRPD measurements, reporting and measurement reporting event B2 in E-UTRA connected mode - Not supported
..0. .... = Indicator 27: EUTRA RRC_CONNECTED to UTRA CELL_DCH CS handover - Not supported
...1 .... = Indicator 28: TTI bundling - Supported
.... 1... = Indicator 29: Semi-Persistent Scheduling - Supported
.... .0.. = Indicator 30: Handover between FDD and TDD - Not supported
.... ..1. = Indicator 31: Mechanisms defined for cells broadcasting multi band information - Supported
.... ...0 = Indicator 32: Undefined - Not supported
interRAT-Parameters
nonCriticalExtension
phyLayerParameters-v920
interRAT-ParametersGERAN-v920
csg-ProximityIndicationParameters-r9
neighCellSI-AcquisitionParameters-r9
son-Parameters-r9
nonCriticalExtension
nonCriticalExtension
phyLayerParameters-v1020
Band65 - earfcn 66211 (ueCat4rel10)
LTE Radio Resource Control (RRC) protocol
UL-DCCH-Message
message: c1 (0)
c1: ueCapabilityInformation (7)
ueCapabilityInformation
rrc-TransactionIdentifier: 2
criticalExtensions: c1 (0)
c1: ueCapabilityInformation-r8 (0)
ueCapabilityInformation-r8
ue-CapabilityRAT-ContainerList: 1 item
Item 0
UE-CapabilityRAT-Container
rat-Type: eutra (0)
ueCapabilityRAT-Container: c9800000
UE-EUTRA-Capability
accessStratumRelease: rel10 (2)
ue-Category: 4
pdcp-Parameters
supportedROHC-Profiles
...0 .... profile0x0001-r15: False
.... 0... profile0x0002-r15: False
.... .0.. profile0x0003-r15: False
.... ..0. profile0x0004-r15: False
.... ...0 profile0x0006-r15: False
0... .... profile0x0101-r15: False
.0.. .... profile0x0102-r15: False
..0. .... profile0x0103-r15: False
...0 .... profile0x0104-r15: False
phyLayerParameters
.... 0... ue-TxAntennaSelectionSupported: False
.... .0.. ue-SpecificRefSigsSupported: False
rf-Parameters
supportedBandListEUTRA: 1 item
Item 0
SupportedBandEUTRA
<<< ??? >>>
<<< Thats all, nothing more… only padding 000 data. >>>
3. FeatureGroupIndication Flag in ue.conf
Here a excerpt from ue.conf
[rrc]
ue_category = 4
release = 10
# std srsue
#feature_group = 3859025920 #0xe6041000
# test value ee0dd89a
feature_group = 3993884826 #0xee0dd89a
As you can see I'm not able to use hex values to set a feature group indication - i need to convert the hex values to decimal to able to either use the std 0xe6041000 or my test value 0xee0dd89a.
Is this a bug or did i misunderstand something here?
Another question regarding rrc.release Version 9 or 10:
I'm wondering if the rel9 and rel10 extensions were filled correctly in the UEcapabilities; i think it seems a bit less.
there the excerpt for the Band7 attach of srsue 20.04 above:
nonCriticalExtension
phyLayerParameters-v920
interRAT-ParametersGERAN-v920
csg-ProximityIndicationParameters-r9
neighCellSI-AcquisitionParameters-r9
son-Parameters-r9
nonCriticalExtension
nonCriticalExtension
phyLayerParameters-v1020
an excerpt of a commercial UE; even nothing from fgi rel9 or rel10 is supported but there are more values populated.
nonCriticalExtension
phyLayerParameters-v920
interRAT-ParametersGERAN-v920
csg-ProximityIndicationParameters-r9
neighCellSI-AcquisitionParameters-r9
intraFreqSI-AcquisitionForHO-r9: supported (0)
interFreqSI-AcquisitionForHO-r9: supported (0)
son-Parameters-r9
rach-Report-r9: supported (0)
nonCriticalExtension
lateNonCriticalExtension: 9000000005a04000
UE-EUTRA-Capability-v9a0-IEs
featureGroupIndRel9Add-r9: 00000000 [bit length 32, 0000 0000 0000 0000 0000 0000 0000 0000 decimal value 0]
0... .... = Indicator 33: Inter-RAT ANR features for UTRAN FDD - Not supported
.0.. .... = Indicator 34: Inter-RAT ANR features for GERAN - Not supported
..0. .... = Indicator 35: Inter-RAT ANR features for 1xRTT - Not supported
...0 .... = Indicator 36: Inter-RAT ANR features for HRPD - Not supported
.... 0... = Indicator 37: Inter-RAT ANR features for UTRAN TDD - Not supported
.... .0.. = Indicator 38: EUTRA RRC_CONNECTED to UTRA TDD CELL_DCH PS handover - Not supported
.... ..0. = Indicator 39: UTRAN TDD measurements, reporting and measurement reporting event B2 in E-UTRA connected mode - Not supported
.... ...0 = Indicator 40: EUTRA RRC_CONNECTED to UTRA TDD CELL_DCH CS handover - Not supported
0... .... = Indicator 41: Measurement reporting event: Event B1 - Neighbour > threshold for UTRAN FDD - Not supported
.0.. .... = Indicator 42: DCI format 3a - Not supported
..0. .... = Indicator 43: Undefined - Not supported
...0 .... = Indicator 44: Undefined - Not supported
.... 0... = Indicator 45: Undefined - Not supported
.... .0.. = Indicator 46: Undefined - Not supported
.... ..0. = Indicator 47: Undefined - Not supported
.... ...0 = Indicator 48: Undefined - Not supported
0... .... = Indicator 49: Undefined - Not supported
.0.. .... = Indicator 50: Undefined - Not supported
..0. .... = Indicator 51: Undefined - Not supported
...0 .... = Indicator 52: Undefined - Not supported
.... 0... = Indicator 53: Undefined - Not supported
.... .0.. = Indicator 54: Undefined - Not supported
.... ..0. = Indicator 55: Undefined - Not supported
.... ...0 = Indicator 56: Undefined - Not supported
0... .... = Indicator 57: Undefined - Not supported
.0.. .... = Indicator 58: Undefined - Not supported
..0. .... = Indicator 59: Undefined - Not supported
...0 .... = Indicator 60: Undefined - Not supported
.... 0... = Indicator 61: Undefined - Not supported
.... .0.. = Indicator 62: Undefined - Not supported
.... ..0. = Indicator 63: Undefined - Not supported
.... ...0 = Indicator 64: Undefined - Not supported
nonCriticalExtension
nonCriticalExtension
nonCriticalExtension
rf-Parameters-v9e0
supportedBandListEUTRA-v9e0: 1 item
Item 0
SupportedBandEUTRA-v9e0
bandEUTRA-v9e0: 65
nonCriticalExtension
phyLayerParameters-v1020
featureGroupIndRel10-r10: 00000000 [bit length 32, 0000 0000 0000 0000 0000 0000 0000 0000 decimal value 0]
0... .... = Indicator 101: DMRS with OCC (orthogonal cover code) and SGH (sequence group hopping) disabling - Not supported
.0.. .... = Indicator 102: Trigger type 1 SRS (aperiodic SRS) transmission (Up to X ports) - Not supported
..0. .... = Indicator 103: PDSCH TM9 when up to 4 CSI reference signal ports are configured - Not supported
...0 .... = Indicator 104: PDSCH TM9 for TDD when 8 CSI reference signal ports are configured - Not supported
.... 0... = Indicator 105: PUCCH RM2-0 when PDSCH TM9 is configured and RM2-1 when PDSCH TM9 and up to 4 CSI reference signal ports are configured - Not supported
.... .0.. = Indicator 106: PUCCH RM2-1 when PDSCH TM9 and 8 CSI reference signal ports are configured - Not supported
.... ..0. = Indicator 107: PUSCH RM2-0 when PDSCH TM9 is configured and RM2-2 when PDSCH TM9 and up to 4 CSI reference signal ports are configured - Not supported
.... ...0 = Indicator 108: PUSCH RM2-2 when PDSCH TM9 and 8 CSI reference signal ports are configured - Not supported
0... .... = Indicator 109: PUCCH RM1-1 submode 1 - Not supported
.0.. .... = Indicator 110: PUCCH RM1-1 submode 2 - Not supported
..0. .... = Indicator 111: Measurement reporting trigger Event A6 - Not supported
...0 .... = Indicator 112: SCell addition within the Handover to EUTRA procedure - Not supported
.... 0... = Indicator 113: Trigger type 0 SRS (periodic SRS) transmission on X Serving Cells - Not supported
.... .0.. = Indicator 114: Reporting of both UTRA CPICH RSCP and Ec/N0 in a Measurement Report - Not supported
.... ..0. = Indicator 115: Time domain ICIC RLM/RRM / ICIC RRM / ICIC CSI measurement sf restriction for the serving cell / neighbour cells - Not supported
.... ...0 = Indicator 116: Relative transmit phase continuity for spatial multiplexing in UL - Not supported
0... .... = Indicator 117: Undefined - Not supported
.0.. .... = Indicator 118: Undefined - Not supported
..0. .... = Indicator 119: Undefined - Not supported
...0 .... = Indicator 120: Undefined - Not supported
.... 0... = Indicator 121: Undefined - Not supported
.... .0.. = Indicator 122: Undefined - Not supported
.... ..0. = Indicator 123: Undefined - Not supported
.... ...0 = Indicator 124: Undefined - Not supported
0... .... = Indicator 125: Undefined - Not supported
.0.. .... = Indicator 126: Undefined - Not supported
..0. .... = Indicator 127: Undefined - Not supported
...0 .... = Indicator 128: Undefined - Not supported
.... 0... = Indicator 129: Undefined - Not supported
.... .0.. = Indicator 130: Undefined - Not supported
.... ..0. = Indicator 131: Undefined - Not supported
.... ...0 = Indicator 132: Undefined - Not supported
I know a lot of different things which i asks but somehow they seems to be related. :)
Thank you very much in advance!!!
Marc
Mit freundlichen Grüßen,
Best regards,
Marc Triefelder
E-Mail: m.triefelder at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20200612/fbe47e85/attachment.htm>
More information about the srsran-users
mailing list