×
Jan-03-2024
Apple Inc is looking for a 4G/5G system engineer on mobility control. Based in California, USA (Bay Area or San Diego). Details Here.
This ASN.1 segment is the start of the NR RRC PDU definitions.
The BCCH-BCH-Message class is the set of RRC messages that may be sent from the network to the UE via BCH on the BCCH logical channel.
-- ASN1START -- TAG-BCCH-BCH-MESSAGE-START BCCH-BCH-Message ::= SEQUENCE { message BCCH-BCH-MessageType } BCCH-BCH-MessageType ::= CHOICE { mib MIB, messageClassExtension SEQUENCE {} } -- TAG-BCCH-BCH-MESSAGE-STOP -- ASN1STOP
The BCCH-DL-SCH-Message class is the set of RRC messages that may be sent from the network to the UE via DL-SCH on the BCCH logical channel.
-- ASN1START -- TAG-BCCH-DL-SCH-MESSAGE-START BCCH-DL-SCH-Message ::= SEQUENCE { message BCCH-DL-SCH-MessageType } BCCH-DL-SCH-MessageType ::= CHOICE { c1 CHOICE { systemInformation SystemInformation, systemInformationBlockType1 SIB1 }, messageClassExtension SEQUENCE {} } -- TAG-BCCH-DL-SCH-MESSAGE-STOP -- ASN1STOP
The DL-CCCH-Message class is the set of RRC messages that may be sent from the Network to the UE on the downlink CCCH logical channel.
-- ASN1START -- TAG-DL-CCCH-MESSAGE-START DL-CCCH-Message ::= SEQUENCE { message DL-CCCH-MessageType } DL-CCCH-MessageType ::= CHOICE { c1 CHOICE { rrcReject RRCReject, rrcSetup RRCSetup, spare2 NULL, spare1 NULL }, messageClassExtension SEQUENCE {} } -- TAG-DL-CCCH-MESSAGE-STOP -- ASN1STOP
The DL-DCCH-Message class is the set of RRC messages that may be sent from the network to the UE on the downlink DCCH logical channel.
-- ASN1START -- TAG-DL-DCCH-MESSAGE-START DL-DCCH-Message ::= SEQUENCE { message DL-DCCH-MessageType } DL-DCCH-MessageType ::= CHOICE { c1 CHOICE { rrcReconfiguration RRCReconfiguration, rrcResume RRCResume, rrcRelease RRCRelease, rrcReestablishment RRCReestablishment, securityModeCommand SecurityModeCommand, dlInformationTransfer DLInformationTransfer, ueCapabilityEnquiry UECapabilityEnquiry, counterCheck CounterCheck, mobilityFromNRCommand MobilityFromNRCommand, dlDedicatedMessageSegment-r16 DLDedicatedMessageSegment-r16, ueInformationRequest-r16 UEInformationRequest-r16, dlInformationTransferMRDC-r16 DLInformationTransferMRDC-r16, loggedMeasurementConfiguration-r16 LoggedMeasurementConfiguration-r16, spare3 NULL,spare2 NULL,spare1 NULL }, messageClassExtension SEQUENCE {} } -- TAG-DL-DCCH-MESSAGE-STOP -- ASN1STOP
The PCCH-Message class is the set of RRC messages that may be sent from the Network to the UE on the PCCH logical channel.
-- ASN1START -- TAG-PCCH-PCH-MESSAGE-START PCCH-Message ::= SEQUENCE { message PCCH-MessageType } PCCH-MessageType ::= CHOICE { c1 CHOICE { paging Paging, spare1 NULL }, messageClassExtension SEQUENCE {} } -- TAG-PCCH-PCH-MESSAGE-STOP -- ASN1STOP
The UL-CCCH-Message class is the set of 48-bits RRC messages that may be sent from the UE to the Network on the uplink CCCH logical channel.
-- ASN1START -- TAG-UL-CCCH-MESSAGE-START UL-CCCH-Message ::= SEQUENCE { message UL-CCCH-MessageType } UL-CCCH-MessageType ::= CHOICE { c1 CHOICE { rrcSetupRequest RRCSetupRequest, rrcResumeRequest RRCResumeRequest, rrcReestablishmentRequest RRCReestablishmentRequest, rrcSystemInfoRequest RRCSystemInfoRequest }, messageClassExtension SEQUENCE {} } -- TAG-UL-CCCH-MESSAGE-STOP -- ASN1STOP
The UL-CCCH1-Message class is the set of 64-bits RRC messages that may be sent from the UE to the Network on the uplink CCCH1 logical channel.
-- ASN1START -- TAG-UL-CCCH1-MESSAGE-START UL-CCCH1-Message ::= SEQUENCE { message UL-CCCH1-MessageType } UL-CCCH1-MessageType ::= CHOICE { c1 CHOICE { rrcResumeRequest1 RRCResumeRequest1, spare3 NULL, spare2 NULL, spare1 NULL }, messageClassExtension SEQUENCE {} } -- TAG-UL-CCCH1-MESSAGE-STOP -- ASN1STOP
The UL-DCCH-Message class is the set of RRC messages that may be sent from the UE to the network on the uplink DCCH logical channel.
-- ASN1START -- TAG-UL-DCCH-MESSAGE-START UL-DCCH-Message ::= SEQUENCE { message UL-DCCH-MessageType } UL-DCCH-MessageType ::= CHOICE { c1 CHOICE { measurementReport MeasurementReport, rrcReconfigurationComplete RRCReconfigurationComplete, rrcSetupComplete RRCSetupComplete, rrcReestablishmentComplete RRCReestablishmentComplete, rrcResumeComplete RRCResumeComplete, securityModeComplete SecurityModeComplete, securityModeFailure SecurityModeFailure, ulInformationTransfer ULInformationTransfer, locationMeasurementIndication LocationMeasurementIndication, ueCapabilityInformation UECapabilityInformation, counterCheckResponse CounterCheckResponse, ueAssistanceInformation UEAssistanceInformation, failureInformation FailureInformation, ulInformationTransferMRDC ULInformationTransferMRDC, scgFailureInformation SCGFailureInformation, scgFailureInformationEUTRA SCGFailureInformationEUTRA }, messageClassExtension CHOICE { c2 CHOICE { ulDedicatedMessageSegment-r16 ULDedicatedMessageSegment-r16, dedicatedSIBRequest-r16 DedicatedSIBRequest-r16, mcgFailureInformation-r16 MCGFailureInformation-r16, ueInformationResponse-r16 UEInformationResponse-r16, sidelinkUEInformationNR-r16 SidelinkUEInformationNR-r16, ulInformationTransferIRAT-r16 ULInformationTransferIRAT-r16, iabOtherInformation-r16 IABOtherInformation-r16, spare9 NULL,spare8 NULL,spare7 NULL,spare6 NULL, spare5 NULL,spare4 NULL,spare3 NULL,spare2 NULL,spare1 NULL }, messageClassExtensionFuture-r16 SEQUENCE {} } } -- TAG-UL-DCCH-MESSAGE-STOP -- ASN1STOP
The CounterCheck message is used by the network to indicate the current COUNT MSB values associated to each DRB and to request the UE to compare these to its COUNT MSB values and to report the comparison results to the network.
-- ASN1START -- TAG-COUNTERCHECK-START CounterCheck ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { counterCheck CounterCheck-IEs, criticalExtensionsFuture SEQUENCE {} } } CounterCheck-IEs ::= SEQUENCE {drb-CountMSB-InfoListIndicates the MSBs of the COUNT values of the DRBs.DRB-CountMSB-InfoList, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } DRB-CountMSB-InfoList ::= SEQUENCE (SIZE (1..maxDRB)) OF DRB-CountMSB-Info DRB-CountMSB-Info ::= SEQUENCE { drb-Identity DRB-Identity,countMSB-UplinkIndicates the value of 25 MSBs from TX_NEXT – 1 (specified in TS 38.323 [5]) associated to this DRB.INTEGER(0..33554431),countMSB-DownlinkIndicates the value of 25 MSBs from RX_NEXT – 1 (specified in TS 38.323 [5]) associated to this DRB.INTEGER(0..33554431) } -- TAG-COUNTERCHECK-STOP -- ASN1STOP
CounterCheck-IEs field descriptions |
---|
drb-CountMSB-InfoList Indicates the MSBs of the COUNT values of the DRBs. |
DRB-CountMSB-Info field descriptions |
---|
countMSB-Downlink Indicates the value of 25 MSBs from RX_NEXT – 1 (specified in TS 38.323 [5]) associated to this DRB. |
countMSB-Uplink Indicates the value of 25 MSBs from TX_NEXT – 1 (specified in TS 38.323 [5]) associated to this DRB. |
The CounterCheckResponse message is used by the UE to respond to a CounterCheck message.
-- ASN1START -- TAG-COUNTERCHECKRESPONSE-START CounterCheckResponse ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { counterCheckResponse CounterCheckResponse-IEs, criticalExtensionsFuture SEQUENCE {} } } CounterCheckResponse-IEs ::= SEQUENCE {drb-CountInfoListIndicates the COUNT values of the DRBs.DRB-CountInfoList, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } DRB-CountInfoList ::= SEQUENCE (SIZE (0..maxDRB)) OF DRB-CountInfo DRB-CountInfo ::= SEQUENCE { drb-Identity DRB-Identity,count-UplinkIndicates the value of TX_NEXT – 1 (specified in TS 38.323 [5]) associated to this DRB.INTEGER(0..4294967295),count-DownlinkIndicates the value of RX_NEXT – 1 (specified in TS 38.323 [5]) associated to this DRB.INTEGER(0..4294967295) } -- TAG-COUNTERCHECKRESPONSE-STOP -- ASN1STOP
CounterCheckResponse-IEs field descriptions |
---|
drb-CountInfoList Indicates the COUNT values of the DRBs. |
DRB-CountInfo field descriptions |
---|
count-Downlink Indicates the value of RX_NEXT – 1 (specified in TS 38.323 [5]) associated to this DRB. |
count-Uplink Indicates the value of TX_NEXT – 1 (specified in TS 38.323 [5]) associated to this DRB. |
The DedicatedSIBRequest message is used to request SIB(s)required by the UE in RRC_CONNECTED as specified in clause 5.2.2.3.5.
-- ASN1START -- TAG-DEDICATEDSIBREQUEST-START DedicatedSIBRequest-r16 ::= SEQUENCE { criticalExtensions CHOICE { dedicatedSIBRequest-r16 DedicatedSIBRequest-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } DedicatedSIBRequest-r16-IEs ::= SEQUENCE { onDemandSIB-RequestList-r16 SEQUENCE {requestedSIB-List-r16Contains a list of SIB(s) the UE requests while in RRC_CONNECTED.SEQUENCE (SIZE (1..maxOnDemandSIB-r16)) OF SIB-ReqInfo-r16 OPTIONAL,requestedPosSIB-List-r16Contains a list of posSIB(s) the UE requests while in RRC_CONNECTED.SEQUENCE (SIZE (1..maxOnDemandPosSIB-r16)) OF PosSIB-ReqInfo-r16 OPTIONAL } OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } SIB-ReqInfo-r16 ::= ENUMERATED { sib12, sib13, sib14, spare5, spare4, spare3, spare2, spare1 } PosSIB-ReqInfo-r16 ::= SEQUENCE {gnss-id-r16The presence of this field indicates that the request positioning SIB type is for a specific GNSS. Indicates a specific GNSS (see also TS 37.355 [49])GNSS-ID-r16 OPTIONAL,sbas-id-r16The presence of this field indicates that the request positioning SIB type is for a specific SBAS. Indicates a specific SBAS (see also TS 37.355 [49]).SBAS-ID-r16 OPTIONAL, posSibType-r16 ENUMERATED { posSibType1-1, posSibType1-2, posSibType1-3, posSibType1-4, posSibType1-5, posSibType1-6, posSibType1-7, posSibType1-8, posSibType2-1, posSibType2-2, posSibType2-3, posSibType2-4, posSibType2-5, posSibType2-6, posSibType2-7, posSibType2-8, posSibType2-9, posSibType2-10, posSibType2-11, posSibType2-12, posSibType2-13, posSibType2-14, posSibType2-15, posSibType2-16, posSibType2-17, posSibType2-18, posSibType2-19, posSibType2-20, posSibType2-21, posSibType2-22, posSibType2-23, posSibType3-1, posSibType4-1, posSibType5-1, posSibType6-1, posSibType6-2, posSibType6-3,... } } -- TAG-DEDICATEDSIBREQUEST-STOP -- ASN1STOP
DedicatedSIBRequest field descriptions |
---|
requestedSIB-List Contains a list of SIB(s) the UE requests while in RRC_CONNECTED. |
requestedPosSIB-List Contains a list of posSIB(s) the UE requests while in RRC_CONNECTED. |
PosSIB-ReqInfo field descriptions |
---|
gnss-id The presence of this field indicates that the request positioning SIB type is for a specific GNSS. Indicates a specific GNSS (see also TS 37.355 [49]) |
sbas-id The presence of this field indicates that the request positioning SIB type is for a specific SBAS. Indicates a specific SBAS (see also TS 37.355 [49]). |
The DLDedicatedMessageSegment message is used to transfer one segment of the RRCResume or RRCReconfiguration messages.
-- ASN1START -- TAG-DLDEDICATEDMESSAGESEGMENT-START DLDedicatedMessageSegment-r16 ::= SEQUENCE { criticalExtensions CHOICE { dlDedicatedMessageSegment-r16 DLDedicatedMessageSegment-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } DLDedicatedMessageSegment-r16-IEs ::= SEQUENCE {segmentNumber-r16Identifies the sequence number of a segment within the encoded DL DCCH message.The network transmits the segments with continuously increasing segmentNumber order so that the UE's RRC layer may expect to obtain them from lower layers in the correct order. Hence, the UE is not required to perform segment re-ordering on RRC level.INTEGER(0..4),rrc-MessageSegmentContainer-r16Includes a segment of the encoded DL DCCH message. The size of the included segment in this container should be small enough so the resulting encoded RRC message PDU is less than or equal to the PDCP SDU size limit.OCTET STRING,rrc-MessageSegmentType-r16Indicates whether the included DL DCCH message segment is the last segment of the message or not.ENUMERATED {notLastSegment, lastSegment}, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-DLDEDICATEDMESSAGESEGMENT-STOP -- ASN1STOP
DLDedicatedMessageSegment field descriptions |
---|
segmentNumber Identifies the sequence number of a segment within the encoded DL DCCH message.The network transmits the segments with continuously increasing segmentNumber order so that the UE's RRC layer may expect to obtain them from lower layers in the correct order. Hence, the UE is not required to perform segment re-ordering on RRC level. |
rrc-MessageSegmentContainer Includes a segment of the encoded DL DCCH message. The size of the included segment in this container should be small enough so the resulting encoded RRC message PDU is less than or equal to the PDCP SDU size limit. |
rrc-MessageSegmentType Indicates whether the included DL DCCH message segment is the last segment of the message or not. |
The DLInformationTransfer message is used for the downlink transfer of NAS dedicated information and timing information for the 5G internal system clock.
-- ASN1START -- TAG-DLINFORMATIONTRANSFER-START DLInformationTransfer ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { dlInformationTransfer DLInformationTransfer-IEs, criticalExtensionsFuture SEQUENCE {} } } DLInformationTransfer-IEs ::= SEQUENCE { dedicatedNAS-Message DedicatedNAS-Message OPTIONAL, -- Need N lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension DLInformationTransfer-v1610-IEs OPTIONAL } DLInformationTransfer-v1610-IEs ::= SEQUENCE { referenceTimeInfo-r16 ReferenceTimeInfo-r16 OPTIONAL, -- Need N nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-DLINFORMATIONTRANSFER-STOP -- ASN1STOP
The DLInformationTransferMRDC message is used for the downlink transfer of RRC messages during fast MCG link recovery.
-- ASN1START -- TAG-DLINFORMATIONTRANSFERMRDC-START DLInformationTransferMRDC-r16 ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE { dlInformationTransferMRDC-r16 DLInformationTransferMRDC-r16-IEs, spare3 NULL,spare2 NULL,spare1 NULL }, criticalExtensionsFuture SEQUENCE {} } } DLInformationTransferMRDC-r16-IEs::= SEQUENCE {dl-DCCH-MessageNR-r16Includes the DL-DCCH-Message. In this version of the specification, the field is only used to transfer the NR RRCReconfiguration,RRCRelease, and MobilityFromNRCommandmessages.OCTET STRING OPTIONAL, -- Need Ndl-DCCH-MessageEUTRA-r16Includes the DL-DCCH-Message. In this version of the specification, the field is only used to transfer the E-UTRA RRCConnectionReconfiguration,RRCConnectionRelease, and MobilityFromEUTRACommand messages as specified in TS 36.331 [10].OCTET STRING OPTIONAL, -- Need N lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-DLINFORMATIONTRANSFERMRDC-STOP -- ASN1STOP
DLInformationTransferMRDC field descriptions |
---|
dl-DCCH-MessageNR Includes the DL-DCCH-Message. In this version of the specification, the field is only used to transfer the NR RRCReconfiguration,RRCRelease, and MobilityFromNRCommandmessages. |
dl-DCCH-MessageEUTRA Includes the DL-DCCH-Message. In this version of the specification, the field is only used to transfer the E-UTRA RRCConnectionReconfiguration,RRCConnectionRelease, and MobilityFromEUTRACommand messages as specified in TS 36.331 [10]. |
The FailureInformation message is used to inform the network about a failure detected by the UE.
-- ASN1START -- TAG-FAILUREINFORMATION-START FailureInformation ::= SEQUENCE { criticalExtensions CHOICE { failureInformation FailureInformation-IEs, criticalExtensionsFuture SEQUENCE {} } } FailureInformation-IEs ::= SEQUENCE { failureInfoRLC-Bearer FailureInfoRLC-Bearer OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension FailureInformation-v1610-IEs OPTIONAL } FailureInfoRLC-Bearer ::= SEQUENCE { cellGroupId CellGroupId, logicalChannelIdentity LogicalChannelIdentity, failureType ENUMERATED {rlc-failure, spare3, spare2, spare1} } FailureInformation-v1610-IEs ::= SEQUENCE { failureInfoDAPS-r16 FailureInfoDAPS-r16 OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } FailureInfoDAPS-r16 ::= SEQUENCE { failureType-r16 ENUMERATED {daps-failure, spare3, spare2, spare1} } -- TAG-FAILUREINFORMATION-STOP -- ASN1STOP
The IABOtherInformation message is used by IAB-MT to request the network to allocate IP addresses for the collocated IAB-DU or inform the network about IP addresses allocated to the collocated IAB-DU.
-- ASN1START -- TAG-IABOTHERINFORMATION-START IABOtherInformation-r16 ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { iabOtherInformation-r16 IABOtherInformation-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } IABOtherInformation-r16-IEs ::= SEQUENCE { ip-InfoType-r16 CHOICE { iab-IP-Request-r16 SEQUENCE {iab-IPv4-AddressNumReq-r16This field is used to request the numbers of IPv4 address per specific usage. The specific usages include F1-C traffic, F1-U traffic, non-F1 traffic and all traffic.IAB-IP-AddressNumReq-r16 OPTIONAL, iab-IPv6-AddressReq-r16 CHOICE {iab-IPv6-AddressNumReq-r16This field is used to request the numbers of IPv6 address per specific usage. The specific usages include F1-C traffic, F1-U traffic, non-F1 traffic and all traffic.IAB-IP-AddressNumReq-r16,iab-IPv6-AddressPrefixReq-r16This field is used to request the prefix of IPv6 address per specific usage. The specific usages include F1-C traffic, F1-U traffic, non-F1 traffic and all traffic.IAB-IP-AddressPrefixReq-r16, ... } OPTIONAL }, iab-IP-Report-r16 SEQUENCE {iab-IPv4-AddressReport-r16This field is used to report the IPv4 address per specific usage assigned by OAM for IAB-DU. The specific usages include F1-C traffic, F1-U traffic, non-F1 traffic and all traffic.IAB-IP-AddressAndTraffic-r16 OPTIONAL, iab-IPv6-Report-r16 CHOICE {iab-IPv6-AddressReport-r16This field is used to report the IPv6 address per specific usage assigned by OAM for IAB-DU. The specific usages include F1-C traffic, F1-U traffic, non-F1 traffic and all traffic.IAB-IP-AddressAndTraffic-r16,iab-IPv6-PrefixReport-r16This field is used to report the prefix of IPv6 address per specific usage assigned by OAM for IAB-DU. The specific usages include F1-C traffic, F1-U traffic, non-F1 traffic and all traffic.IAB-IP-PrefixAndTraffic-r16, ... } OPTIONAL }, ... }, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } IAB-IP-AddressNumReq-r16 ::= SEQUENCE {all-Traffic-NumReq-r16This field is used to request the numbers of IP address for all traffic.INTEGER (1..8) OPTIONAL,f1-C-Traffic-NumReq-r16This field is used to request the numbers of IP address for F1-C traffic.INTEGER (1..8) OPTIONAL,f1-U-Traffic-NumReq-r16This field is used to request the numbers of IP address for F1-U traffic.INTEGER (1..8) OPTIONAL,non-F1-Traffic-NumReq-r16This field is used to request the numbers of IP address for non-F1 traffic.INTEGER (1..8) OPTIONAL, ... } IAB-IP-AddressPrefixReq-r16 ::= SEQUENCE {all-Traffic-PrefixReq-r16This field is used to request the IPv6 address prefix for all traffic. The length of allocated IPv6 prefix is fixed to 64.ENUMERATED {true} OPTIONAL,f1-C-Traffic-PrefixReq-r16This field is used to request the IPv6 address prefix for F1-C traffic. The length of allocated IPv6 prefix is fixed to 64.ENUMERATED {true} OPTIONAL,f1-U-Traffic-PrefixReq-r16This field is used to request the IPv6 address prefix for F1-U traffic. The length of allocated IPv6 prefix is fixed to 64.ENUMERATED {true} OPTIONAL,non-F1-Traffic-PrefixReq-r16This field is used to request the IPv6 address prefix for non-F1 traffic. The length of allocated IPv6 prefix is fixed to 64.ENUMERATED {true} OPTIONAL, ... } IAB-IP-AddressAndTraffic-r16 ::= SEQUENCE {all-Traffic-IAB-IP-Address-r16This field is used to report to IAB-donor-CU the IP address(es) or IPv6 address prefix for all traffic.SEQUENCE (SIZE(1..8)) OF IAB-IP-Address-r16 OPTIONAL,f1-C-Traffic-IP-Address-r16This field is used to report to IAB-donor-CU the IP address(es) or IPv6 address prefix for F1-C traffic.SEQUENCE (SIZE(1..8)) OF IAB-IP-Address-r16 OPTIONAL,f1-U-Traffic-IP-Address-r16This field is used to report to IAB-donor-CU the IP address(es) or IPv6 address prefix for F1-U traffic.SEQUENCE (SIZE(1..8)) OF IAB-IP-Address-r16 OPTIONAL,non-F1-Traffic-IP-Address-r16This field is used to report to IAB-donor-CU the IP address(es) or IPv6 address prefix for non-F1 traffic.SEQUENCE (SIZE(1..8)) OF IAB-IP-Address-r16 OPTIONAL } IAB-IP-PrefixAndTraffic-r16 ::= SEQUENCE {all-Traffic-IAB-IP-Address-r16This field is used to report to IAB-donor-CU the IP address(es) or IPv6 address prefix for all traffic.IAB-IP-Address-r16 OPTIONAL,f1-C-Traffic-IP-Address-r16This field is used to report to IAB-donor-CU the IP address(es) or IPv6 address prefix for F1-C traffic.IAB-IP-Address-r16 OPTIONAL,f1-U-Traffic-IP-Address-r16This field is used to report to IAB-donor-CU the IP address(es) or IPv6 address prefix for F1-U traffic.IAB-IP-Address-r16 OPTIONAL,non-F1-Traffic-IP-Address-r16This field is used to report to IAB-donor-CU the IP address(es) or IPv6 address prefix for non-F1 traffic.IAB-IP-Address-r16 OPTIONAL } -- TAG-IABOTHERINFORMATION-STOP -- ASN1STOP
IABOtherInformation-IEs field descriptions |
---|
iab-IPv4-AddressNumReq This field is used to request the numbers of IPv4 address per specific usage. The specific usages include F1-C traffic, F1-U traffic, non-F1 traffic and all traffic. |
iab-IPv4-AddressReport This field is used to report the IPv4 address per specific usage assigned by OAM for IAB-DU. The specific usages include F1-C traffic, F1-U traffic, non-F1 traffic and all traffic. |
iab-IPv6-AddressNumReq This field is used to request the numbers of IPv6 address per specific usage. The specific usages include F1-C traffic, F1-U traffic, non-F1 traffic and all traffic. |
iab-IPv6-AddressPrefixReq This field is used to request the prefix of IPv6 address per specific usage. The specific usages include F1-C traffic, F1-U traffic, non-F1 traffic and all traffic. |
iab-IPv6-AddressReport This field is used to report the IPv6 address per specific usage assigned by OAM for IAB-DU. The specific usages include F1-C traffic, F1-U traffic, non-F1 traffic and all traffic. |
iab-IPv6-PrefixReport This field is used to report the prefix of IPv6 address per specific usage assigned by OAM for IAB-DU. The specific usages include F1-C traffic, F1-U traffic, non-F1 traffic and all traffic. |
IAB-IP-AddressNumReq-IEs field descriptions |
---|
all-Traffic-NumReq This field is used to request the numbers of IP address for all traffic. |
f1-C-Traffic-NumReq This field is used to request the numbers of IP address for F1-C traffic. |
f1-U-Traffic-NumReq This field is used to request the numbers of IP address for F1-U traffic. |
non-F1-Traffic-NumReq This field is used to request the numbers of IP address for non-F1 traffic. |
IAB-IP-AddressPrefixReq-IEs field descriptions |
---|
all-Traffic-PrefixReq This field is used to request the IPv6 address prefix for all traffic. The length of allocated IPv6 prefix is fixed to 64. |
f1-C-Traffic-PrefixReq This field is used to request the IPv6 address prefix for F1-C traffic. The length of allocated IPv6 prefix is fixed to 64. |
f1-U-Traffic-PrefixReq This field is used to request the IPv6 address prefix for F1-U traffic. The length of allocated IPv6 prefix is fixed to 64. |
non-F1-Traffic-PrefixReq This field is used to request the IPv6 address prefix for non-F1 traffic. The length of allocated IPv6 prefix is fixed to 64. |
IAB-IP-AddressAndTraffic-IEs field descriptions |
---|
all-Traffic-IAB-IP-Address This field is used to report to IAB-donor-CU the IP address(es) or IPv6 address prefix for all traffic. |
f1-C-Traffic-IP-Address This field is used to report to IAB-donor-CU the IP address(es) or IPv6 address prefix for F1-C traffic. |
f1-U-Traffic-IP-Address This field is used to report to IAB-donor-CU the IP address(es) or IPv6 address prefix for F1-U traffic. |
non-F1-Traffic-IP-Address This field is used to report to IAB-donor-CU the IP address(es) or IPv6 address prefix for non-F1 traffic. |
The LocationMeasurementIndication message is used to indicate that the UE is going to either start or stop location related measurement which requires measurement gaps.
-- ASN1START -- TAG-LOCATIONMEASUREMENTINDICATION-START LocationMeasurementIndication ::= SEQUENCE { criticalExtensions CHOICE { locationMeasurementIndication LocationMeasurementIndication-IEs, criticalExtensionsFuture SEQUENCE {} } } LocationMeasurementIndication-IEs ::= SEQUENCE { measurementIndication SetupRelease {LocationMeasurementInfo}, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } -- TAG-LOCATIONMEASUREMENTINDICATION-STOP -- ASN1STOP
The LoggedMeasurementConfiguration message is used to perform logging of measurement results while in RRC_IDLE or RRC_INACTIVE. It is used to transfer the logged measurement configuration for network performance optimisation.
-- ASN1START -- TAG-LOGGEDMEASUREMENTCONFIGURATION-START LoggedMeasurementConfiguration-r16 ::= SEQUENCE { criticalExtensions CHOICE { loggedMeasurementConfiguration-r16 LoggedMeasurementConfiguration-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } LoggedMeasurementConfiguration-r16-IEs ::= SEQUENCE { traceReference-r16 TraceReference-r16,traceRecordingSessionRef-r16Parameter Trace Recording Session Reference: See TS 32.422 [52].OCTET STRING (SIZE (2)),tce-Id-r16Parameter Trace Collection Entity Id: See TS 32.422 [52].OCTET STRING (SIZE (1)),absoluteTimeInfo-r16Indicates the absolute time in the current cell.AbsoluteTimeInfo-r16,areaConfiguration-r16Used to restrict the area in which the UE performs measurement logging to cells broadcasting either one of the included cell identities or one of the included tracking area codes/ frequencies.AreaConfiguration-r16 OPTIONAL, --Need Rplmn-IdentityList-r16Indicates a set of PLMNs defining when the UE performs measurement logging as well as the associated status indication and information retrieval i.e. the UE performs these actions when the RPLMN is part of this set of PLMNs.PLMN-IdentityList2-r16 OPTIONAL, --Need R bt-NameList-r16 SetupRelease {BT-NameList-r16} OPTIONAL, --Need M wlan-NameList-r16 SetupRelease {WLAN-NameList-r16} OPTIONAL, --Need M sensor-NameList-r16 SetupRelease {Sensor-NameList-r16} OPTIONAL, --Need M loggingDuration-r16 LoggingDuration-r16,reportTypeParameter configures the type of MDT configuration, specifically Periodic MDT configuration or Event Triggerd MDT configuration.CHOICE { periodical LoggedPeriodicalReportConfig-r16, eventTriggered LoggedEventTriggerConfig-r16, ... }, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } LoggedPeriodicalReportConfig-r16 ::= SEQUENCE { loggingInterval-r16 LoggingInterval-r16, ... } LoggedEventTriggerConfig-r16 ::= SEQUENCE {eventType-r16The value outOfCoverage indicates the UE to perform logging of measurements when the UE enters any cell selection state, and the value eventL1 indicates the UE to perform logging of measurements when the triggering condition (similar as event A2 as specified in 5.5.4.3) as configured in the event is met for the camping cell in camped normally state.EventType-r16, loggingInterval-r16 LoggingInterval-r16, ... } EventType-r16 ::= CHOICE { outOfCoverage NULL, eventL1 SEQUENCE { l1-Threshold MeasTriggerQuantity, hysteresis Hysteresis, timeToTrigger TimeToTrigger }, ... } -- TAG-LOGGEDMEASUREMENTCONFIGURATION-STOP -- ASN1STOP
LoggedMeasurementConfiguration field descriptions |
---|
absoluteTimeInfo Indicates the absolute time in the current cell. |
areaConfiguration Used to restrict the area in which the UE performs measurement logging to cells broadcasting either one of the included cell identities or one of the included tracking area codes/ frequencies. |
eventType The value outOfCoverage indicates the UE to perform logging of measurements when the UE enters any cell selection state, and the value eventL1 indicates the UE to perform logging of measurements when the triggering condition (similar as event A2 as specified in 5.5.4.3) as configured in the event is met for the camping cell in camped normally state. |
plmn-IdentityList Indicates a set of PLMNs defining when the UE performs measurement logging as well as the associated status indication and information retrieval i.e. the UE performs these actions when the RPLMN is part of this set of PLMNs. |
tce-Id Parameter Trace Collection Entity Id: See TS 32.422 [52]. |
traceRecordingSessionRef Parameter Trace Recording Session Reference: See TS 32.422 [52]. |
reportType Parameter configures the type of MDT configuration, specifically Periodic MDT configuration or Event Triggerd MDT configuration. |
The MCGFailureInformation message is used to provide information regarding NR MCG failures detected by the UE.
-- ASN1START -- TAG-MCGFAILUREINFORMATION-START MCGFailureInformation-r16 ::= SEQUENCE { criticalExtensions CHOICE { mcgFailureInformation-r16 MCGFailureInformation-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } MCGFailureInformation-r16-IEs ::= SEQUENCE { failureReportMCG-r16 FailureReportMCG-r16 OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } FailureReportMCG-r16 ::= SEQUENCE { failureType-r16 ENUMERATED {t310-Expiry, randomAccessProblem, rlc-MaxNumRetx, t312-Expiry-r16, lbt-Failure-r16, beamFailureRecoveryFailure-r16, bh-RLF-r16, spare1} OPTIONAL,measResultFreqList-r16The field contains available results of measurements on NR frequencies the UE is configured to measure by the measConfig associated with the MCG.MeasResultList2NR OPTIONAL,measResultFreqListEUTRA-r16The field contains available results of measurements on E-UTRA frequencies the UE is configured to measure by measConfig associated with the MCG.MeasResultList2EUTRA OPTIONAL,measResultSCG-r16The field contains the MeasResultSCG-Failure IE which includes available measurement results on NR frequencies the UE is configured to measure by the measConfig associated with the SCG.OCTET STRING (CONTAINING MeasResultSCG-Failure) OPTIONAL,measResultSCG-EUTRA-r16The field contains the EUTRA MeasResultSCG-FailureMRDC IE which includes available results of measurements on E-UTRA frequencies the UE is configured to measure by the E-UTRA RRCConnectionReconfiguration message as specified in TS 36.331 [10].OCTET STRING OPTIONAL,measResultFreqListUTRA-FDD-r16The field contains available results of measurements on UTRA FDD frequencies the UE is configured to measure by measConfig associated with the MCG.MeasResultList2UTRA OPTIONAL, ... } MeasResultList2UTRA ::= SEQUENCE (SIZE (1..maxFreq)) OF MeasResult2UTRA-FDD-r16 MeasResult2UTRA-FDD-r16 ::= SEQUENCE { carrierFreq-r16 ARFCN-ValueUTRA-FDD-r16, measResultNeighCellList-r16 MeasResultListUTRA-FDD-r16 } MeasResultList2EUTRA ::= SEQUENCE (SIZE (1..maxFreq)) OF MeasResult2EUTRA-r16 -- TAG-MCGFAILUREINFORMATION-STOP -- ASN1STOP
MCGFailureInformation field descriptions |
---|
measResultFreqList The field contains available results of measurements on NR frequencies the UE is configured to measure by the measConfig associated with the MCG. |
measResultFreqListEUTRA The field contains available results of measurements on E-UTRA frequencies the UE is configured to measure by measConfig associated with the MCG. |
measResultFreqListUTRA-FDD The field contains available results of measurements on UTRA FDD frequencies the UE is configured to measure by measConfig associated with the MCG. |
measResultSCG The field contains the MeasResultSCG-Failure IE which includes available measurement results on NR frequencies the UE is configured to measure by the measConfig associated with the SCG. |
measResultSCG-EUTRA The field contains the EUTRA MeasResultSCG-FailureMRDC IE which includes available results of measurements on E-UTRA frequencies the UE is configured to measure by the E-UTRA RRCConnectionReconfiguration message as specified in TS 36.331 [10]. |
The MeasurementReport message is used for the indication of measurement results.
-- ASN1START -- TAG-MEASUREMENTREPORT-START MeasurementReport ::= SEQUENCE { criticalExtensions CHOICE { measurementReport MeasurementReport-IEs, criticalExtensionsFuture SEQUENCE {} } } MeasurementReport-IEs ::= SEQUENCE { measResults MeasResults, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } -- TAG-MEASUREMENTREPORT-STOP -- ASN1STOP
The MIB includes the system information transmitted on BCH.
-- ASN1START -- TAG-MIB-START MIB ::= SEQUENCE {systemFrameNumberThe 6 most significant bits (MSB) of the 10-bit System Frame Number (SFN). The 4 LSB of the SFN are conveyed in the PBCH transport block as part of channel coding (i.e. outside the MIBencoding), as defined in clause 7.1 in TS 38.212 [17].BIT STRING (SIZE (6)),subCarrierSpacingCommonSubcarrier spacing for SIB1, Msg.2/4 and MsgB for initial access, paging and broadcast SI-messages. If the UE acquires this MIB on an FR1 carrier frequency, the value scs15or60 corresponds to 15 kHz and the value scs30or120 corresponds to 30 kHz. If the UE acquires this MIB on an FR2 carrier frequency, the value scs15or60 corresponds to 60 kHz and the value scs30or120 corresponds to 120 kHz. For operation with shared spectrum channel access (see 37.213 [48]), the subcarrier spacing for SIB1, Msg.2/4 and MsgB for initial access, paging and broadcast SI-messages is same as that for the corresponding SSB and this field instead is used for deriving the QCL relation between SS/PBCH blocks as specified in TS 38.213 [13], clause 4.1.ENUMERATED {scs15or60, scs30or120},ssb-SubcarrierOffsetCorresponds to kSSB (see TS 38.213 [13]), which is the frequency domain offset between SSB and the overall resource block grid in number of subcarriers. (See TS 38.211 [16], clause 7.4.3.1).For operation with shared spectrum channel access (see 37.213 [48]), this field corresponds to , and kSSB is obtained from (see TS 38.211 [16], clause 7.4.3.1); the LSB of this field is used also for deriving the QCL relation between SS/PBCH blocks as specified in TS 38.213 [13], clause 4.1. The value range of this field may be extended by an additional most significant bit encoded within PBCH as specified in TS 38.213 [13]. This field may indicate that this cell does not provide SIB1 and that there is hence no CORESET#0 configured in MIB (see TS 38.213 [13], clause 13). In this case, the field pdcch-ConfigSIB1 may indicate the frequency positions where the UE may (not) find a SS/PBCH with a control resource set and search space for SIB1 (see TS 38.213 [13], clause 13).INTEGER (0..15),dmrs-TypeA-PositionPosition of (first) DM-RS for downlink (see TS 38.211 [16], clause 7.4.1.1.2) and uplink (see TS 38.211 [16], clause 6.4.1.1.3).ENUMERATED {pos2, pos3},pdcch-ConfigSIB1Determines a common ControlResourceSet (CORESET), a common search space and necessary PDCCH parameters. If the field ssb-SubcarrierOffset indicates that SIB1 is absent, the field pdcch-ConfigSIB1 indicates the frequency positions where the UE may find SS/PBCH block with SIB1 or the frequency range where the network does not provide SS/PBCH block with SIB1 (see TS 38.213 [13], clause 13).PDCCH-ConfigSIB1,cellBarredValue barred means that the cell is barred, as defined in TS 38.304 [20]. This field is ignored by IAB-MT.ENUMERATED {barred, notBarred},intraFreqReselectionControls cell selection/reselection to intra-frequency cells when the highest ranked cell is barred, or treated as barred by the UE, as specified in TS 38.304 [20].This field is ignored by IAB-MT.ENUMERATED {allowed, notAllowed}, spare BIT STRING (SIZE (1)) } -- TAG-MIB-STOP -- ASN1STOP
MIB field descriptions |
---|
cellBarred Value barred means that the cell is barred, as defined in TS 38.304 [20]. This field is ignored by IAB-MT. |
dmrs-TypeA-Position Position of (first) DM-RS for downlink (see TS 38.211 [16], clause 7.4.1.1.2) and uplink (see TS 38.211 [16], clause 6.4.1.1.3). |
intraFreqReselection Controls cell selection/reselection to intra-frequency cells when the highest ranked cell is barred, or treated as barred by the UE, as specified in TS 38.304 [20].This field is ignored by IAB-MT. |
pdcch-ConfigSIB1 Determines a common ControlResourceSet (CORESET), a common search space and necessary PDCCH parameters. If the field ssb-SubcarrierOffset indicates that SIB1 is absent, the field pdcch-ConfigSIB1 indicates the frequency positions where the UE may find SS/PBCH block with SIB1 or the frequency range where the network does not provide SS/PBCH block with SIB1 (see TS 38.213 [13], clause 13). |
ssb-SubcarrierOffset Corresponds to kSSB (see TS 38.213 [13]), which is the frequency domain offset between SSB and the overall resource block grid in number of subcarriers. (See TS 38.211 [16], clause 7.4.3.1).For operation with shared spectrum channel access (see 37.213 [48]), this field corresponds to , and kSSB is obtained from (see TS 38.211 [16], clause 7.4.3.1); the LSB of this field is used also for deriving the QCL relation between SS/PBCH blocks as specified in TS 38.213 [13], clause 4.1. The value range of this field may be extended by an additional most significant bit encoded within PBCH as specified in TS 38.213 [13]. This field may indicate that this cell does not provide SIB1 and that there is hence no CORESET#0 configured in MIB (see TS 38.213 [13], clause 13). In this case, the field pdcch-ConfigSIB1 may indicate the frequency positions where the UE may (not) find a SS/PBCH with a control resource set and search space for SIB1 (see TS 38.213 [13], clause 13). |
subCarrierSpacingCommon Subcarrier spacing for SIB1, Msg.2/4 and MsgB for initial access, paging and broadcast SI-messages. If the UE acquires this MIB on an FR1 carrier frequency, the value scs15or60 corresponds to 15 kHz and the value scs30or120 corresponds to 30 kHz. If the UE acquires this MIB on an FR2 carrier frequency, the value scs15or60 corresponds to 60 kHz and the value scs30or120 corresponds to 120 kHz. For operation with shared spectrum channel access (see 37.213 [48]), the subcarrier spacing for SIB1, Msg.2/4 and MsgB for initial access, paging and broadcast SI-messages is same as that for the corresponding SSB and this field instead is used for deriving the QCL relation between SS/PBCH blocks as specified in TS 38.213 [13], clause 4.1. |
systemFrameNumber The 6 most significant bits (MSB) of the 10-bit System Frame Number (SFN). The 4 LSB of the SFN are conveyed in the PBCH transport block as part of channel coding (i.e. outside the MIBencoding), as defined in clause 7.1 in TS 38.212 [17]. |
The MobilityFromNRCommand message is used to command handover from NR to E-UTRA/EPC, E-UTRA/5GC or UTRA-FDD.
-- ASN1START -- TAG-MOBILITYFROMNRCOMMAND-START MobilityFromNRCommand ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { mobilityFromNRCommand MobilityFromNRCommand-IEs, criticalExtensionsFuture SEQUENCE {} } } MobilityFromNRCommand-IEs ::= SEQUENCE {targetRAT-TypeIndicates the target RAT type.ENUMERATED { eutra, utra-fdd-v1610, spare2, spare1, ...},targetRAT-MessageContainerThe field contains a message specified in another standard, as indicated by the targetRAT-Type, and carries information about the target cell identifier(s) and radio parameters relevant for the target radio access technology. A complete message is included, as specified in the other standard. See NOTE 1OCTET STRING,nas-SecurityParamFromNRIf targetRAT-Type is eutra, this field is used to deliver the key synchronisation and Key freshness for the NR to LTE/EPC handovers and a part of the downlink NAS COUNT as specified in TS 33.501 [11] and the content of the parameter is defined in TS 24.501 [23]. If targetRAT-Type is utra-fdd, this field is used to deliver the key synchronisation and Key freshness for the NR to FDD UTRAN handover and a part of the downlink NAS COUNT as specified in TS 33.501 [11] and the content of the parameter is defined in TS 24.501 [23].OCTET STRING OPTIONAL, -- Cond HO-ToEPCUTRAN lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension MobilityFromNRCommand-v1610-IEs OPTIONAL } MobilityFromNRCommand-v1610-IEs ::= SEQUENCE {voiceFallbackIndication-r16Indicates the handover is triggered by EPS fallback for IMS voice as specified in TS 23.502 [43].ENUMERATED {true} OPTIONAL, -- Need N nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-MOBILITYFROMNRCOMMAND-STOP -- ASN1STOP
MobilityFromNRCommand-IEs field descriptions |
---|
nas-SecurityParamFromNR If targetRAT-Type is eutra, this field is used to deliver the key synchronisation and Key freshness for the NR to LTE/EPC handovers and a part of the downlink NAS COUNT as specified in TS 33.501 [11] and the content of the parameter is defined in TS 24.501 [23]. If targetRAT-Type is utra-fdd, this field is used to deliver the key synchronisation and Key freshness for the NR to FDD UTRAN handover and a part of the downlink NAS COUNT as specified in TS 33.501 [11] and the content of the parameter is defined in TS 24.501 [23]. |
targetRAT-MessageContainer The field contains a message specified in another standard, as indicated by the targetRAT-Type, and carries information about the target cell identifier(s) and radio parameters relevant for the target radio access technology. A complete message is included, as specified in the other standard. See NOTE 1 |
targetRAT-Type Indicates the target RAT type. |
voiceFallbackIndication Indicates the handover is triggered by EPS fallback for IMS voice as specified in TS 23.502 [43]. |
targetRAT-Type | Standard to apply | targetRAT-MessageContainer |
---|---|---|
eutra | TS 36.331 [10] (clause 5.4.2) | DL-DCCH-Message including theRRCConnectionReconfiguration |
utra-fdd | TS 25.331 [45] (clause 10.2.16a) | Handover TO UTRAN command |
Conditional Presence | Explanation |
---|---|
HO-ToEPCUTRAN | This field is mandatory present in case of inter system handover to "EPC" or "FDD UTRAN". Otherwise it is absent. |
The Paging message is used for the notification of one or more UEs.
-- ASN1START -- TAG-PAGING-START Paging ::= SEQUENCE { pagingRecordList PagingRecordList OPTIONAL, -- Need N lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } PagingRecordList ::= SEQUENCE (SIZE(1..maxNrofPageRec)) OF PagingRecord PagingRecord ::= SEQUENCE { ue-Identity PagingUE-Identity,accessTypeIndicates whether the Paging message is originated due to the PDU sessions from the non-3GPP access.ENUMERATED {non3GPP} OPTIONAL, -- Need N ... } PagingUE-Identity ::= CHOICE { ng-5G-S-TMSI NG-5G-S-TMSI, fullI-RNTI I-RNTI-Value, ... } -- TAG-PAGING-STOP -- ASN1STOP
PagingRecord field descriptions |
---|
accessType Indicates whether the Paging message is originated due to the PDU sessions from the non-3GPP access. |
The RRCReestablishment message is used to re-establish SRB1.
-- ASN1START -- TAG-RRCREESTABLISHMENT-START RRCReestablishment ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcReestablishment RRCReestablishment-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCReestablishment-IEs ::= SEQUENCE { nextHopChainingCount NextHopChainingCount, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-RRCREESTABLISHMENT-STOP -- ASN1STOP
The RRCReestablishmentComplete message is used to confirm the successful completion of an RRC connection re-establishment.
-- ASN1START -- TAG-RRCREESTABLISHMENTCOMPLETE-START RRCReestablishmentComplete ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcReestablishmentComplete RRCReestablishmentComplete-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCReestablishmentComplete-IEs ::= SEQUENCE { lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCReestablishmentComplete-v1610-IEs OPTIONAL } RRCReestablishmentComplete-v1610-IEs ::= SEQUENCE { ue-MeasurementsAvailable-r16 UE-MeasurementsAvailable-r16 OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-RRCREESTABLISHMENTCOMPLETE-STOP -- ASN1STOP
The RRCReestablishmentRequest message is used to request the reestablishment of an RRC connection.
-- ASN1START -- TAG-RRCREESTABLISHMENTREQUEST-START RRCReestablishmentRequest ::= SEQUENCE { rrcReestablishmentRequest RRCReestablishmentRequest-IEs } RRCReestablishmentRequest-IEs ::= SEQUENCE {ue-IdentityUE identity included to retrieve UE context and to facilitate contention resolution by lower layers.ReestabUE-Identity,reestablishmentCauseIndicates the failure cause that triggered the re-establishment procedure. gNB is not expected to reject a RRCReestablishmentRequest due to unknown cause value being used by the UE.ReestablishmentCause, spare BIT STRING (SIZE (1)) } ReestabUE-Identity ::= SEQUENCE { c-RNTI RNTI-Value,physCellIdThe Physical Cell Identity of the PCell the UE was connected to prior to the failure.PhysCellId, shortMAC-I ShortMAC-I } ReestablishmentCause ::= ENUMERATED {reconfigurationFailure, handoverFailure, otherFailure, spare1} -- TAG-RRCREESTABLISHMENTREQUEST-STOP -- ASN1STOP
ReestabUE-Identity field descriptions |
---|
physCellId The Physical Cell Identity of the PCell the UE was connected to prior to the failure. |
RRCReestablishmentRequest-IEs field descriptions |
---|
reestablishmentCause Indicates the failure cause that triggered the re-establishment procedure. gNB is not expected to reject a RRCReestablishmentRequest due to unknown cause value being used by the UE. |
ue-Identity UE identity included to retrieve UE context and to facilitate contention resolution by lower layers. |
The RRCReconfiguration message is the command to modify an RRC connection. It may convey information for measurement configuration, mobility control, radio resource configuration (including RBs, MAC main configuration and physical channel configuration) and AS security configuration.
-- ASN1START -- TAG-RRCRECONFIGURATION-START RRCReconfiguration ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcReconfiguration RRCReconfiguration-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCReconfiguration-IEs ::= SEQUENCE {radioBearerConfigConfiguration of Radio Bearers (DRBs, SRBs) including SDAP/PDCP. In (NG)EN-DC, this field may only be present if the RRCReconfiguration is transmitted over SRB3.RadioBearerConfig OPTIONAL, -- Need MsecondaryCellGroupConfiguration of secondary cell group ((NG)EN-DC or NR-DC).OCTET STRING (CONTAINING CellGroupConfig) OPTIONAL, -- Cond SCG measConfig MeasConfig OPTIONAL, -- Need M lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCReconfiguration-v1530-IEs OPTIONAL } RRCReconfiguration-v1530-IEs ::= SEQUENCE {masterCellGroupConfiguration of master cell group.OCTET STRING (CONTAINING CellGroupConfig) OPTIONAL, -- Need MfullConfigIndicates that the full configuration option is applicable for the RRCReconfiguration message for intra-system intra-RAT HO. For inter-RAT HO from E-UTRA to NR, fullConfig indicates whether or not delta signalling of SDAP/PDCP from source RAT is applicable. This field is absent if any DAPS bearer is configured or when the RRCReconfiguration message is transmitted on SRB3, and in an RRCReconfiguration message for SCG contained in another RRCReconfiguration message (or RRCConnectionReconfiguration message, see TS 36.331 [10]) transmitted on SRB1.ENUMERATED {true} OPTIONAL, -- Cond FullConfigdedicatedNAS-MessageListThis field is used to transfer UE specific NAS layer information between the network and the UE. The RRC layer is transparent for each PDU in the list.SEQUENCE (SIZE(1..maxDRB)) OF DedicatedNAS-Message OPTIONAL, -- Cond nonHO masterKeyUpdate MasterKeyUpdate OPTIONAL, -- Cond MasterKeyChangededicatedSIB1-DeliveryThis field is used to transfer SIB1 to the UE.The field has the same values as the corresponding configuration in servingCellConfigCommon.OCTET STRING (CONTAINING SIB1) OPTIONAL, -- Need NdedicatedSystemInformationDeliveryThis field is used to transfer SIB6, SIB7, SIB8 to the UE with an active BWP with no common search space configured. For UEs in RRC_CONNECTED, this field is also used to transfer the SIBs requested on-demand.OCTET STRING (CONTAINING SystemInformation) OPTIONAL, -- Need NotherConfigContains configuration related to other configurations. When configured for the SCG, only fields drx-PreferenceConfig, maxBW-PreferenceConfig, maxCC-PreferenceConfig, maxMIMO-LayerPreferenceConfig,minSchedulingOffsetPreferenceConfig, btNameList, wlanNameList, sensorNameListand obtainCommonLocationcan be included.OtherConfig OPTIONAL, -- Need M nonCriticalExtension RRCReconfiguration-v1540-IEs OPTIONAL } RRCReconfiguration-v1540-IEs ::= SEQUENCE { otherConfig-v1540 OtherConfig-v1540 OPTIONAL, -- Need M nonCriticalExtension RRCReconfiguration-v1560-IEs OPTIONAL } RRCReconfiguration-v1560-IEs ::= SEQUENCE { mrdc-SecondaryCellGroupConfig SetupRelease { MRDC-SecondaryCellGroupConfig } OPTIONAL, -- Need MradioBearerConfig2Configuration of Radio Bearers (DRBs, SRBs) including SDAP/PDCP. This field can only be used if the UE supports NR-DC or NE-DC.OCTET STRING (CONTAINING RadioBearerConfig) OPTIONAL, -- Need Msk-CounterA counter used upon initial configuration of S-KgNB or S-KeNB, as well as upon refresh of S-KgNB or S-KeNB. This field is always included either upon initial configuration of an NR SCG or upon configuration of the first RB with keyToUse set to secondary, whichever happens first. This field is absent if there is neither any NR SCG nor any RB with keyToUse set to secondary.SK-Counter OPTIONAL, -- Need N nonCriticalExtension RRCReconfiguration-v1610-IEs OPTIONAL } RRCReconfiguration-v1610-IEs ::= SEQUENCE { otherConfig-v1610 OtherConfig-v1610 OPTIONAL, -- Need Mbap-Config-r16This field is used to configure the BAP entity for IAB nodes.SetupRelease { BAP-Config-r16 } OPTIONAL, -- Need M iab-IP-AddressConfigurationList-r16 IAB-IP-AddressConfigurationList-r16 OPTIONAL, -- Need MconditionalReconfiguration-r16Configuration of candidate target SpCell(s) and execution condition(s) for conditional handover or conditional PSCell change.For conditional PSCell change, this field may only be present in an RRCReconfiguration message for intra-SN PSCell change. The network does not configure a UE with both conditional PCell change and conditional PSCell change simultaneously. The field is absent if any DAPS bearer is configured or if the masterCellGroupincludes ReconfigurationWithSync.For conditional PSCell change, the field is absent if the secondaryCellGroup includes ReconfigurationWithSync. The RRCReconfiguration message contained in DLInformationTransferMRDC cannot contain the field conditionalReconfiguration for conditional PSCell change.ConditionalReconfiguration-r16 OPTIONAL, -- Need Mdaps-SourceRelease-r16Indicates to UE that the source cell part of DAPS operation is to be stopped and the source cell part of DAPS configuration is to be released.ENUMERATED{true} OPTIONAL, -- Need Nt316-r16Indicates the value for timer T316 as described in clause 7.1. Value ms50 corresponds to 50 ms, value ms100 corresponds to 100 ms and so on. This field can be configured only if the UE is configured with split SRB1 or SRB3.SetupRelease {T316-r16} OPTIONAL, -- Need MneedForGapsConfigNR-r16Configuration for the UE to report measurement gap requirement information of NR target bands in the RRCReconfigurationComplete and RRCResumeComplete message.SetupRelease {NeedForGapsConfigNR-r16} OPTIONAL, -- Need MonDemandSIB-Request-r16If the field is present, the UE is allowed to request SIB(s) on-demand while in RRC_CONNECTED according to clause 5.2.2.3.5.SetupRelease { OnDemandSIB-Request-r16 } OPTIONAL, -- Need MdedicatedPosSysInfoDelivery-r16This field is used to transfer SIBPos to the UE in RRC_CONNECTED.OCTET STRING (CONTAINING PosSystemInformation-r16-IEs) OPTIONAL, -- Need Nsl-ConfigDedicatedNR-r16This field is used to provide the dedicated configurations for NR sidelink communication.SetupRelease {SL-ConfigDedicatedNR-r16} OPTIONAL, -- Need Msl-ConfigDedicatedEUTRA-Info-r16This field includes the E-UTRA RRCConnectionReconfiguration as specified in TS 36.331 [10]. In this version of the specification, the E-UTRA RRCConnectionReconfiguration can only includes sidelink related fields for V2X sidelink communication, i.e. sl-V2X-ConfigDedicated, sl-V2X-SPS-Config, measConfig and/or otherConfig.SetupRelease {SL-ConfigDedicatedEUTRA-Info-r16} OPTIONAL, -- Need MtargetCellSMTC-SCG-r16The SSB periodicity/offset/duration configuration of target cell for NR PSCell addition and SN change. When UE receives this field, UE applies the configuration based on the timing reference of NR PCell for PSCell addition and PSCell change for the case of no reconfiguration with sync of MCG, and UE applies the configuration based on the timing reference of target NR PCell for the case of reconfiguration with sync of MCG. If both this field and the smtc in secondaryCellGroup -> SpCellConfig -> reconfigurationWithSync are absent, the UE uses the SMTC in the measObjectNR having the same SSB frequency and subcarrier spacing, as configured before the reception of the RRC message.SSB-MTC OPTIONAL, -- Need S nonCriticalExtension SEQUENCE {} OPTIONAL } MRDC-SecondaryCellGroupConfig ::= SEQUENCE {mrdc-ReleaseAndAddThis field indicates that the current SCG configuration is released and a new SCG is added at the same time.ENUMERATED {true} OPTIONAL, -- Need Nmrdc-SecondaryCellGroupIncludes an RRC message for SCG configuration in NR-DC or NE-DC.For NR-DC (nr-SCG), mrdc-SecondaryCellGroup contains the RRCReconfiguration message as generated (entirely) by SN gNB. In this version of the specification, the RRC message can only include fields secondaryCellGroup, otherConfig, conditionalReconfiguration and measConfig. For NE-DC (eutra-SCG), mrdc-SecondaryCellGroup includes the E-UTRA RRCConnectionReconfiguration message as specified in TS 36.331 [10]. In this version of the specification, the E-UTRA RRC message can only include the field scg-Configuration.CHOICE { nr-SCG OCTET STRING (CONTAINING RRCReconfiguration), eutra-SCG OCTET STRING } } BAP-Config-r16 ::= SEQUENCE {bap-Address-r16Indicates the BAP address of an IAB-node. The BAP address of an IAB-node cannot be changed once configured to the BAP entity.BIT STRING (SIZE (10)) OPTIONAL, -- Need MdefaultUL-BAP-RoutingID-r16This field is used for IAB-node to configure the default uplink Routing ID, which is used by IAB-node during IAB-node bootstrapping, migration, IAB-MT RRC resume and IAB-MT RRC re-establishment for F1-C and non-F1 traffic. The defaultUL-BAP-RoutingID can be (re-)configured when IAB-node IP address for F1-C related traffic changes. This field is mandatory only for IAB-node bootstrapping.BAP-RoutingID-r16 OPTIONAL, -- Need MdefaultUL-BH-RLC-Channel-r16This field is used for IAB-nodes to configure the default uplink BH RLC channel, which is used by IAB-nodeduring IAB-node bootstrapping, migration, IAB-MT RRC resume and IAB-MT RRC re-establishmentfor F1-C and non-F1 traffic. The defaultUL-BH-RLC-Channel can be (re-)configured when IAB-node IP address for F1-C related traffic changes, and the new IP address is anchored at a different IAB-donor-DU. This field is mandatory for IAB-node bootstrapping. If the IAB-MT is operating in EN-DC, the default uplink BH RLC channel is referring to an RLC channel on the SCG; Otherwise, it is referring to an RLC channel on the MCG.BH-RLC-ChannelID-r16 OPTIONAL, -- Need MflowControlFeedbackType-r16This field is only used for IAB-node that support hop-by-hop flow control to configure the type of flow control feedback. Value perBH-RLC-Channel indicates that the IAB-node shall provide flow control feedback per BH RLC channel, value perRoutingID indicates that the IAB-node shall provide flow control feedback per routing ID, and value both indicates that the IAB-node shall provide flow control feedback both per BH RLC channel and per routing ID.ENUMERATED {perBH-RLC-Channel, perRoutingID, both} OPTIONAL, -- Need R ... } MasterKeyUpdate ::= SEQUENCE {keySetChangeIndicatorIndicates whether UE shall derive a new KgNB. If reconfigurationWithSync is included, value true indicates that a KgNB key is derived from a KAMF key taken into use through the latest successful NAS SMC procedure, or N2 handover procedure with KAMF change, as described in TS 33.501 [11] for KgNB re-keying. Value false indicates that the new KgNB key is obtained from the current KgNB key or from the NH as described in TS 33.501 [11].BOOLEAN,nextHopChainingCountParameter NCC: See TS 33.501 [11]NextHopChainingCount,nas-ContainerThis field is used to transfer UE specific NAS layer information between the network and the UE. The RRC layer is transparent for this field, although it affects activation of AS security after inter-system handover to NR. The content is defined in TS 24.501 [23].OCTET STRING OPTIONAL, -- Cond securityNASC ... } OnDemandSIB-Request-r16 ::= SEQUENCE {onDemandSIB-RequestProhibitTimer-r16Prohibit timer for requesting SIB(s) on-demand while in RRC_CONNECTED according to clause 5.2.2.3.5. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on.ENUMERATED {s0, s0dot5, s1, s2, s5, s10, s20, s30} } T316-r16 ::= ENUMERATED {ms50, ms100, ms200, ms300, ms400, ms500, ms600, ms1000, ms1500, ms2000} IAB-IP-AddressConfigurationList-r16 ::= SEQUENCE {iab-IP-AddressToAddModList-r16List of IP addresses allocated for IAB-node to be added and modified.SEQUENCE (SIZE(1..maxIAB-IP-Address-r16)) OF IAB-IP-AddressConfiguration-r16 OPTIONAL, -- Need Niab-IP-AddressToReleaseList-r16List of IP address allocated for IAB-node to be released.SEQUENCE (SIZE(1..maxIAB-IP-Address-r16)) OF IAB-IP-AddressIndex-r16 OPTIONAL, -- Need N ... } IAB-IP-AddressConfiguration-r16 ::= SEQUENCE {iab-IP-AddressIndex-r16This field is used to identify a configuration of an IP address.IAB-IP-AddressIndex-r16,iab-IP-Address-r16This field is used to provide the IP address information for IAB-node.IAB-IP-Address-r16 OPTIONAL, -- Need Miab-IP-Usage-r16This field is used to indicate the usage of the assigned IP address. If this field is not configured, the assigned IP address is used for all traffic.IAB-IP-Usage-r16 OPTIONAL, -- Need Miab-donor-DU-BAP-Address-r16This field is used to indicate the BAP address of the IAB-donor-DU where the IP address is anchored.BIT STRING (SIZE(10)) OPTIONAL, -- Need M ... } SL-ConfigDedicatedEUTRA-Info-r16 ::= SEQUENCE { sl-ConfigDedicatedEUTRA-r16 OCTET STRING OPTIONAL, -- Need M sl-TimeOffsetEUTRA-List-r16 SEQUENCE (SIZE (8)) OF SL-TimeOffsetEUTRA-r16 OPTIONAL -- Need M } SL-TimeOffsetEUTRA-r16 ::= ENUMERATED {ms0, ms0dot25, ms0dot5, ms0dot625, ms0dot75, ms1, ms1dot25, ms1dot5, ms1dot75, ms2, ms2dot5, ms3, ms4, ms5, ms6, ms8, ms10, ms20} -- TAG-RRCRECONFIGURATION-STOP -- ASN1STOP
RRCReconfiguration-IEs field descriptions |
---|
bap-Config This field is used to configure the BAP entity for IAB nodes. |
bap-Address Indicates the BAP address of an IAB-node. The BAP address of an IAB-node cannot be changed once configured to the BAP entity. |
conditionalReconfiguration Configuration of candidate target SpCell(s) and execution condition(s) for conditional handover or conditional PSCell change.For conditional PSCell change, this field may only be present in an RRCReconfiguration message for intra-SN PSCell change. The network does not configure a UE with both conditional PCell change and conditional PSCell change simultaneously. The field is absent if any DAPS bearer is configured or if the masterCellGroupincludes ReconfigurationWithSync.For conditional PSCell change, the field is absent if the secondaryCellGroup includes ReconfigurationWithSync. The RRCReconfiguration message contained in DLInformationTransferMRDC cannot contain the field conditionalReconfiguration for conditional PSCell change. |
daps-SourceRelease Indicates to UE that the source cell part of DAPS operation is to be stopped and the source cell part of DAPS configuration is to be released. |
dedicatedNAS-MessageList This field is used to transfer UE specific NAS layer information between the network and the UE. The RRC layer is transparent for each PDU in the list. |
dedicatedPosSysInfoDelivery This field is used to transfer SIBPos to the UE in RRC_CONNECTED. |
dedicatedSIB1-Delivery This field is used to transfer SIB1 to the UE.The field has the same values as the corresponding configuration in servingCellConfigCommon. |
dedicatedSystemInformationDelivery This field is used to transfer SIB6, SIB7, SIB8 to the UE with an active BWP with no common search space configured. For UEs in RRC_CONNECTED, this field is also used to transfer the SIBs requested on-demand. |
defaultUL-BAP-RoutingID This field is used for IAB-node to configure the default uplink Routing ID, which is used by IAB-node during IAB-node bootstrapping, migration, IAB-MT RRC resume and IAB-MT RRC re-establishment for F1-C and non-F1 traffic. The defaultUL-BAP-RoutingID can be (re-)configured when IAB-node IP address for F1-C related traffic changes. This field is mandatory only for IAB-node bootstrapping. |
defaultUL-BH-RLC-Channel This field is used for IAB-nodes to configure the default uplink BH RLC channel, which is used by IAB-nodeduring IAB-node bootstrapping, migration, IAB-MT RRC resume and IAB-MT RRC re-establishmentfor F1-C and non-F1 traffic. The defaultUL-BH-RLC-Channel can be (re-)configured when IAB-node IP address for F1-C related traffic changes, and the new IP address is anchored at a different IAB-donor-DU. This field is mandatory for IAB-node bootstrapping. If the IAB-MT is operating in EN-DC, the default uplink BH RLC channel is referring to an RLC channel on the SCG; Otherwise, it is referring to an RLC channel on the MCG. |
flowControlFeedbackType This field is only used for IAB-node that support hop-by-hop flow control to configure the type of flow control feedback. Value perBH-RLC-Channel indicates that the IAB-node shall provide flow control feedback per BH RLC channel, value perRoutingID indicates that the IAB-node shall provide flow control feedback per routing ID, and value both indicates that the IAB-node shall provide flow control feedback both per BH RLC channel and per routing ID. |
fullConfig Indicates that the full configuration option is applicable for the RRCReconfiguration message for intra-system intra-RAT HO. For inter-RAT HO from E-UTRA to NR, fullConfig indicates whether or not delta signalling of SDAP/PDCP from source RAT is applicable. This field is absent if any DAPS bearer is configured or when the RRCReconfiguration message is transmitted on SRB3, and in an RRCReconfiguration message for SCG contained in another RRCReconfiguration message (or RRCConnectionReconfiguration message, see TS 36.331 [10]) transmitted on SRB1. |
iab-IP-Address This field is used to provide the IP address information for IAB-node. |
iab-IP-AddressIndex This field is used to identify a configuration of an IP address. |
iab-IP-AddressToAddModList List of IP addresses allocated for IAB-node to be added and modified. |
iab-IP-AddressToReleaseList List of IP address allocated for IAB-node to be released. |
iab-IP-Usage This field is used to indicate the usage of the assigned IP address. If this field is not configured, the assigned IP address is used for all traffic. |
iab-donor-DU-BAP-Address This field is used to indicate the BAP address of the IAB-donor-DU where the IP address is anchored. |
keySetChangeIndicator Indicates whether UE shall derive a new KgNB. If reconfigurationWithSync is included, value true indicates that a KgNB key is derived from a KAMF key taken into use through the latest successful NAS SMC procedure, or N2 handover procedure with KAMF change, as described in TS 33.501 [11] for KgNB re-keying. Value false indicates that the new KgNB key is obtained from the current KgNB key or from the NH as described in TS 33.501 [11]. |
masterCellGroup Configuration of master cell group. |
mrdc-ReleaseAndAdd This field indicates that the current SCG configuration is released and a new SCG is added at the same time. |
mrdc-SecondaryCellGroup Includes an RRC message for SCG configuration in NR-DC or NE-DC.For NR-DC (nr-SCG), mrdc-SecondaryCellGroup contains the RRCReconfiguration message as generated (entirely) by SN gNB. In this version of the specification, the RRC message can only include fields secondaryCellGroup, otherConfig, conditionalReconfiguration and measConfig. For NE-DC (eutra-SCG), mrdc-SecondaryCellGroup includes the E-UTRA RRCConnectionReconfiguration message as specified in TS 36.331 [10]. In this version of the specification, the E-UTRA RRC message can only include the field scg-Configuration. |
nas-Container This field is used to transfer UE specific NAS layer information between the network and the UE. The RRC layer is transparent for this field, although it affects activation of AS security after inter-system handover to NR. The content is defined in TS 24.501 [23]. |
needForGapsConfigNR Configuration for the UE to report measurement gap requirement information of NR target bands in the RRCReconfigurationComplete and RRCResumeComplete message. |
nextHopChainingCount Parameter NCC: See TS 33.501 [11] |
onDemandSIB-Request If the field is present, the UE is allowed to request SIB(s) on-demand while in RRC_CONNECTED according to clause 5.2.2.3.5. |
onDemandSIB-RequestProhibitTimer Prohibit timer for requesting SIB(s) on-demand while in RRC_CONNECTED according to clause 5.2.2.3.5. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on. |
otherConfig Contains configuration related to other configurations. When configured for the SCG, only fields drx-PreferenceConfig, maxBW-PreferenceConfig, maxCC-PreferenceConfig, maxMIMO-LayerPreferenceConfig,minSchedulingOffsetPreferenceConfig, btNameList, wlanNameList, sensorNameListand obtainCommonLocationcan be included. |
radioBearerConfig Configuration of Radio Bearers (DRBs, SRBs) including SDAP/PDCP. In (NG)EN-DC, this field may only be present if the RRCReconfiguration is transmitted over SRB3. |
radioBearerConfig2 Configuration of Radio Bearers (DRBs, SRBs) including SDAP/PDCP. This field can only be used if the UE supports NR-DC or NE-DC. |
secondaryCellGroup Configuration of secondary cell group ((NG)EN-DC or NR-DC). |
sk-Counter A counter used upon initial configuration of S-KgNB or S-KeNB, as well as upon refresh of S-KgNB or S-KeNB. This field is always included either upon initial configuration of an NR SCG or upon configuration of the first RB with keyToUse set to secondary, whichever happens first. This field is absent if there is neither any NR SCG nor any RB with keyToUse set to secondary. |
sl-ConfigDedicatedNR This field is used to provide the dedicated configurations for NR sidelink communication. |
sl-ConfigDedicatedEUTRA-Info This field includes the E-UTRA RRCConnectionReconfiguration as specified in TS 36.331 [10]. In this version of the specification, the E-UTRA RRCConnectionReconfiguration can only includes sidelink related fields for V2X sidelink communication, i.e. sl-V2X-ConfigDedicated, sl-V2X-SPS-Config, measConfig and/or otherConfig. |
sl-TimeOffsetEUTRA This field indicates the possible time offset to (de)activation of V2X sidelink transmission after receiving DCI format 3_1 used for scheduling V2X sidelink communication. Value ms0dpt75 corresponds to 0.75ms, ms1 corresponds to 1ms and so on. The network includes this field only when sl-ConfigDedicatedEUTRA is configured. |
targetCellSMTC-SCG The SSB periodicity/offset/duration configuration of target cell for NR PSCell addition and SN change. When UE receives this field, UE applies the configuration based on the timing reference of NR PCell for PSCell addition and PSCell change for the case of no reconfiguration with sync of MCG, and UE applies the configuration based on the timing reference of target NR PCell for the case of reconfiguration with sync of MCG. If both this field and the smtc in secondaryCellGroup -> SpCellConfig -> reconfigurationWithSync are absent, the UE uses the SMTC in the measObjectNR having the same SSB frequency and subcarrier spacing, as configured before the reception of the RRC message. |
t316 Indicates the value for timer T316 as described in clause 7.1. Value ms50 corresponds to 50 ms, value ms100 corresponds to 100 ms and so on. This field can be configured only if the UE is configured with split SRB1 or SRB3. |
Conditional Presence | Explanation |
---|---|
nonHO | The field is absent in case of reconfiguration with sync within NR or to NR; otherwise it is optionally present, need N. |
securityNASC | This field is mandatory present in case of inter system handover. Otherwise the field is optionally present, need N. |
MasterKeyChange | This field is mandatory present in case masterCellGroup includes ReconfigurationWithSync and RadioBearerConfig includes SecurityConfig with SecurityAlgorithmConfig, indicating a change of the AS security algorithms associated to the master key. If ReconfigurationWithSync is included for other cases, this field is optionally present, need N. Otherwise the field is absent. |
FullConfig | The field is mandatory present in case of inter-system handover from E-UTRA/EPC to NR. It is optionally present, Need N, during reconfiguration with sync and also in first reconfiguration after reestablishment; or for intra-system handover from E-UTRA/5GC to NR. It is absent otherwise. |
SCG | The field is mandatory present in: -an RRCReconfiguration message contained in an RRCResume message (or in an RRCConnectionResume message, see TS 36.331 [10]), -an RRCReconfiguration message contained in an RRCConnectionReconfiguration message, see TS 36.331 [10], which is contained in DLInformationTransferMRDCtransmitted on SRB3 (as a response to ULInformationTransferMRDC including an MCGFailureInformation). The field is optional present, Need M, in: -an RRCReconfiguration message transmitted on SRB3, -an RRCReconfiguration message contained in another RRCReconfiguration message (or in an RRCConnectionReconfiguration message, see TS 36.331 [10]) transmitted on SRB1 -an RRCReconfiguration message contained in another RRCReconfiguration message which is contained in DLInformationTransferMRDCtransmitted on SRB3 (as a response to ULInformationTransferMRDC including an MCGFailureInformation) Otherwise, the field is absent |
The RRCReconfigurationComplete message is used to confirm the successful completion of an RRC connection reconfiguration.
-- ASN1START -- TAG-RRCRECONFIGURATIONCOMPLETE-START RRCReconfigurationComplete ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcReconfigurationComplete RRCReconfigurationComplete-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCReconfigurationComplete-IEs ::= SEQUENCE { lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCReconfigurationComplete-v1530-IEs OPTIONAL } RRCReconfigurationComplete-v1530-IEs ::= SEQUENCE {uplinkTxDirectCurrentListThe Tx Direct Current locations for the configured serving cells and BWPs if requested by the NW (see reportUplinkTxDirectCurrent in CellGroupConfig).UplinkTxDirectCurrentList OPTIONAL, nonCriticalExtension RRCReconfigurationComplete-v1560-IEs OPTIONAL } RRCReconfigurationComplete-v1560-IEs ::= SEQUENCE {scg-ResponseIn case of NR-DC (nr-SCG-Response), this field includes the RRCReconfigurationComplete message. In case of NE-DC (eutra-SCG-Response), this field includes the E-UTRA RRCConnectionReconfigurationComplete message as specified in TS 36.331 [10].CHOICE { nr-SCG-Response OCTET STRING (CONTAINING RRCReconfigurationComplete), eutra-SCG-Response OCTET STRING } OPTIONAL, nonCriticalExtension RRCReconfigurationComplete-v1610-IEs OPTIONAL } RRCReconfigurationComplete-v1610-IEs ::= SEQUENCE { ue-MeasurementsAvailable-r16 UE-MeasurementsAvailable-r16 OPTIONAL,needForGapsInfoNR-r16This field is used to indicate the measurement gap requirement information of the UE for NR target bands.NeedForGapsInfoNR-r16 OPTIONAL, nonCriticalExtension RRCReconfigurationComplete-v1640-IEs OPTIONAL } RRCReconfigurationComplete-v1640-IEs ::= SEQUENCE {uplinkTxDirectCurrentTwoCarrierList-r16The Tx Direct Current locations for the configured uplink intra-band CA with two carriers if requested by the NW (see reportUplinkTxDirectCurrentTwoCarrier-r16 in CellGroupConfig).UplinkTxDirectCurrentTwoCarrierList-r16 OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-RRCRECONFIGURATIONCOMPLETE-STOP -- ASN1STOP
RRCReconfigurationComplete-IEs field descriptions |
---|
needForGapsInfoNR This field is used to indicate the measurement gap requirement information of the UE for NR target bands. |
scg-Response In case of NR-DC (nr-SCG-Response), this field includes the RRCReconfigurationComplete message. In case of NE-DC (eutra-SCG-Response), this field includes the E-UTRA RRCConnectionReconfigurationComplete message as specified in TS 36.331 [10]. |
uplinkTxDirectCurrentList The Tx Direct Current locations for the configured serving cells and BWPs if requested by the NW (see reportUplinkTxDirectCurrent in CellGroupConfig). |
uplinkTxDirectCurrentTwoCarrierList The Tx Direct Current locations for the configured uplink intra-band CA with two carriers if requested by the NW (see reportUplinkTxDirectCurrentTwoCarrier-r16 in CellGroupConfig). |
The RRCReject message is used to reject an RRC connection establishment or an RRC connection resumption.
-- ASN1START -- TAG-RRCREJECT-START RRCReject ::= SEQUENCE { criticalExtensions CHOICE { rrcReject RRCReject-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCReject-IEs ::= SEQUENCE {waitTimeWait time value in seconds. The field is always included.RejectWaitTime OPTIONAL, -- Need N lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } -- TAG-RRCREJECT-STOP -- ASN1STOP
RRCReject-IEs field descriptions |
---|
waitTime Wait time value in seconds. The field is always included. |
The RRCRelease message is used to command the release of an RRC connection or the suspension of the RRC connection.
-- ASN1START -- TAG-RRCRELEASE-START RRCRelease ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcRelease RRCRelease-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCRelease-IEs ::= SEQUENCE {redirectedCarrierInfoIndicates a carrier frequency (downlink for FDD) and is used to redirect the UE to an NR or an inter-RAT carrier frequency, by means of cell selection at transition to RRC_IDLE or RRC_INACTIVE as specified in TS 38.304 [20]. Based on UE capability, the network may includeredirectedCarrierInfo in RRCRelease message with suspendConfig if this message is sent in response to an RRCResumeRequest or an RRCResumeRequest1 which is triggered by the NAS layer (see 5.3.1.4 in TS 24.501 [23]).RedirectedCarrierInfo OPTIONAL, -- Need N cellReselectionPriorities CellReselectionPriorities OPTIONAL, -- Need RsuspendConfigIndicates configuration for the RRC_INACTIVE state. The network does not configure suspendConfig when the network redirect the UE to an inter-RAT carrier frequencyor if the UE is configured with a DAPS bearer.SuspendConfig OPTIONAL, -- Need RdeprioritisationReqIndicates whether the current frequency or RAT is to be de-prioritised.SEQUENCE { deprioritisationType ENUMERATED {frequency, nr},deprioritisationTimerIndicates the period for which either the current carrier frequency or NR is deprioritised. Value minN corresponds to N minutes.ENUMERATED {min5, min10, min15, min30} } OPTIONAL, -- Need N lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCRelease-v1540-IEs OPTIONAL } RRCRelease-v1540-IEs ::= SEQUENCE { waitTime RejectWaitTime OPTIONAL, -- Need N nonCriticalExtension RRCRelease-v1610-IEs OPTIONAL } RRCRelease-v1610-IEs ::= SEQUENCE {voiceFallbackIndication-r16Indicates the RRC release is triggered by EPS fallback for IMS voice as specified in TS 23.502 [43].ENUMERATED {true} OPTIONAL, -- Need NmeasIdleConfig-r16Indicates measurement configuration to be stored and used by the UE while in RRC_IDLE or RRC_INACTIVE.SetupRelease {MeasIdleConfigDedicated-r16} OPTIONAL, -- Need M nonCriticalExtension RRCRelease-v1650-IEs OPTIONAL } RRCRelease-v1650-IEs ::= SEQUENCE {mpsPriorityIndication-r16Indicates the UE can set the establishment cause to mps-PriorityAccess for a new connection following a redirect to NR or set the resume cause to mps-PriorityAccess for a resume following a redirect to NR. If the target RAT is E-UTRA, see TS36.331[10]. The gNB sets the indication only for UEs authorized to receive MPS treatment as indicated by ARP and/or QoS characteristics at the gNB, and it is applicable only for this instance of release with redirection to carrier/RAT included in the redirectedCarrierInfo field in the RRCRelease message.ENUMERATED {true} OPTIONAL, -- Cond Redirection2 nonCriticalExtension SEQUENCE {} OPTIONAL } RedirectedCarrierInfo ::= CHOICE { nr CarrierInfoNR, eutra RedirectedCarrierInfo-EUTRA, ... } RedirectedCarrierInfo-EUTRA ::= SEQUENCE { eutraFrequency ARFCN-ValueEUTRA,cnTypeIndicate that the UE is redirected to EPC or 5GC.ENUMERATED {epc,fiveGC} OPTIONAL -- Need N } CarrierInfoNR ::= SEQUENCE {carrierFreqIndicates the redirected NR frequency.ARFCN-ValueNR,ssbSubcarrierSpacingSubcarrier spacing of SSB in the redirected SSB frequency. Only the values 15 kHz or 30 kHz (FR1), and 120 kHz or 240 kHz (FR2) are applicable.SubcarrierSpacing,smtcThe SSB periodicity/offset/duration configuration for the redirected SSB frequency. It is based on timing reference of PCell. If the field is absent, the UE uses the SMTC configured in the measObjectNR having the same SSB frequency and subcarrier spacing.SSB-MTC OPTIONAL, -- Need S ... } SuspendConfig ::= SEQUENCE { fullI-RNTI I-RNTI-Value, shortI-RNTI ShortI-RNTI-Value,ran-PagingCycleRefers to the UE specific cycle for RAN-initiated paging. Value rf32 corresponds to 32 radio frames, value rf64 corresponds to 64 radio frames and so on.PagingCycle,ran-NotificationAreaInfoNetwork ensures that the UE in RRC_INACTIVE always has a valid ran-NotificationAreaInfo.RAN-NotificationAreaInfo OPTIONAL, -- Need Mt380Refers to the timer that triggers the periodic RNAU procedure in UE. Value min5 corresponds to 5 minutes, value min10 corresponds to 10 minutes and so on.PeriodicRNAU-TimerValue OPTIONAL, -- Need R nextHopChainingCount NextHopChainingCount, ... } PeriodicRNAU-TimerValue ::= ENUMERATED { min5, min10, min20, min30, min60, min120, min360, min720} CellReselectionPriorities ::= SEQUENCE { freqPriorityListEUTRA FreqPriorityListEUTRA OPTIONAL, -- Need M freqPriorityListNR FreqPriorityListNR OPTIONAL, -- Need M t320 ENUMERATED {min5, min10, min20, min30, min60, min120, min180, spare1} OPTIONAL, -- Need R ... } PagingCycle ::= ENUMERATED {rf32, rf64, rf128, rf256} FreqPriorityListEUTRA ::= SEQUENCE (SIZE (1..maxFreq)) OF FreqPriorityEUTRA FreqPriorityListNR ::= SEQUENCE (SIZE (1..maxFreq)) OF FreqPriorityNR FreqPriorityEUTRA ::= SEQUENCE {carrierFreqIndicates the redirected NR frequency.ARFCN-ValueEUTRA, cellReselectionPriority CellReselectionPriority, cellReselectionSubPriority CellReselectionSubPriority OPTIONAL -- Need R } FreqPriorityNR ::= SEQUENCE {carrierFreqIndicates the redirected NR frequency.ARFCN-ValueNR, cellReselectionPriority CellReselectionPriority, cellReselectionSubPriority CellReselectionSubPriority OPTIONAL -- Need R } RAN-NotificationAreaInfo ::= CHOICE {cellListA list of cells configured as RAN area.PLMN-RAN-AreaCellList,ran-AreaConfigListA list of RAN area codes or RA code(s) as RAN area.PLMN-RAN-AreaConfigList, ... } PLMN-RAN-AreaCellList ::= SEQUENCE (SIZE (1.. maxPLMNIdentities)) OF PLMN-RAN-AreaCell PLMN-RAN-AreaCell ::= SEQUENCE {plmn-IdentityPLMN Identity to which the cells in ran-AreaCells belong. If the field is absent the UE not in SNPN access mode uses the ID of the registered PLMN. This field is not included for UE in SNPN access mode (for UE in SNPN access mode the ran-AreaCells always belongs to the registered SNPN).PLMN-Identity OPTIONAL, -- Need Sran-AreaCellsThe total number of cells of all PLMNs does not exceed 32.SEQUENCE (SIZE (1..32)) OF CellIdentity } PLMN-RAN-AreaConfigList ::= SEQUENCE (SIZE (1..maxPLMNIdentities)) OF PLMN-RAN-AreaConfig PLMN-RAN-AreaConfig ::= SEQUENCE {plmn-IdentityPLMN Identity to which the cells in ran-AreaCells belong. If the field is absent the UE not in SNPN access mode uses the ID of the registered PLMN. This field is not included for UE in SNPN access mode (for UE in SNPN access mode the ran-AreaCells always belongs to the registered SNPN).PLMN-Identity OPTIONAL, -- Need Sran-AreaIndicates whether TA code(s) or RAN area code(s) are used for the RAN notification area. The network uses only TA code(s) or both TA code(s) and RAN area code(s) to configure a UE. The total number of TACs across all PLMNs does not exceed 16.SEQUENCE (SIZE (1..16)) OF RAN-AreaConfig } RAN-AreaConfig ::= SEQUENCE { trackingAreaCode TrackingAreaCode,ran-AreaCodeListThe total number of RAN-AreaCodes of all PLMNs does not exceed 32.SEQUENCE (SIZE (1..32)) OF RAN-AreaCode OPTIONAL -- Need R } -- TAG-RRCRELEASE-STOP -- ASN1STOP
RRCRelease-IEs field descriptions |
---|
cnType Indicate that the UE is redirected to EPC or 5GC. |
deprioritisationReq Indicates whether the current frequency or RAT is to be de-prioritised. |
deprioritisationTimer Indicates the period for which either the current carrier frequency or NR is deprioritised. Value minN corresponds to N minutes. |
measIdleConfig Indicates measurement configuration to be stored and used by the UE while in RRC_IDLE or RRC_INACTIVE. |
mpsPriorityIndication Indicates the UE can set the establishment cause to mps-PriorityAccess for a new connection following a redirect to NR or set the resume cause to mps-PriorityAccess for a resume following a redirect to NR. If the target RAT is E-UTRA, see TS36.331[10]. The gNB sets the indication only for UEs authorized to receive MPS treatment as indicated by ARP and/or QoS characteristics at the gNB, and it is applicable only for this instance of release with redirection to carrier/RAT included in the redirectedCarrierInfo field in the RRCRelease message. |
suspendConfig Indicates configuration for the RRC_INACTIVE state. The network does not configure suspendConfig when the network redirect the UE to an inter-RAT carrier frequencyor if the UE is configured with a DAPS bearer. |
redirectedCarrierInfo Indicates a carrier frequency (downlink for FDD) and is used to redirect the UE to an NR or an inter-RAT carrier frequency, by means of cell selection at transition to RRC_IDLE or RRC_INACTIVE as specified in TS 38.304 [20]. Based on UE capability, the network may includeredirectedCarrierInfo in RRCRelease message with suspendConfig if this message is sent in response to an RRCResumeRequest or an RRCResumeRequest1 which is triggered by the NAS layer (see 5.3.1.4 in TS 24.501 [23]). |
voiceFallbackIndication Indicates the RRC release is triggered by EPS fallback for IMS voice as specified in TS 23.502 [43]. |
CarrierInfoNR field descriptions |
---|
carrierFreq Indicates the redirected NR frequency. |
ssbSubcarrierSpacing Subcarrier spacing of SSB in the redirected SSB frequency. Only the values 15 kHz or 30 kHz (FR1), and 120 kHz or 240 kHz (FR2) are applicable. |
smtc The SSB periodicity/offset/duration configuration for the redirected SSB frequency. It is based on timing reference of PCell. If the field is absent, the UE uses the SMTC configured in the measObjectNR having the same SSB frequency and subcarrier spacing. |
RAN-NotificationAreaInfo field descriptions |
---|
cellList A list of cells configured as RAN area. |
ran-AreaConfigList A list of RAN area codes or RA code(s) as RAN area. |
PLMN-RAN-AreaConfig field descriptions |
---|
plmn-Identity PLMN Identity to which the cells in ran-Area belong. If the field is absent the UE not in SNPN access mode uses the ID of the registered PLMN. This field is not included for UE in SNPN access mode (for UE in SNPN access mode the ran-Area always belongs to the registered SNPN). |
ran-AreaCodeList The total number of RAN-AreaCodes of all PLMNs does not exceed 32. |
ran-Area Indicates whether TA code(s) or RAN area code(s) are used for the RAN notification area. The network uses only TA code(s) or both TA code(s) and RAN area code(s) to configure a UE. The total number of TACs across all PLMNs does not exceed 16. |
PLMN-RAN-AreaCell field descriptions |
---|
plmn-Identity PLMN Identity to which the cells in ran-AreaCells belong. If the field is absent the UE not in SNPN access mode uses the ID of the registered PLMN. This field is not included for UE in SNPN access mode (for UE in SNPN access mode the ran-AreaCells always belongs to the registered SNPN). |
ran-AreaCells The total number of cells of all PLMNs does not exceed 32. |
SuspendConfig field descriptions |
---|
ran-NotificationAreaInfo Network ensures that the UE in RRC_INACTIVE always has a valid ran-NotificationAreaInfo. |
ran-PagingCycle Refers to the UE specific cycle for RAN-initiated paging. Value rf32 corresponds to 32 radio frames, value rf64 corresponds to 64 radio frames and so on. |
t380 Refers to the timer that triggers the periodic RNAU procedure in UE. Value min5 corresponds to 5 minutes, value min10 corresponds to 10 minutes and so on. |
Conditional Presence | Explanation |
---|---|
Redirection2 | The field is optionally present, Need R, if redirectedCarrierInfo is included; otherwise the field is not present. |
The RRCResume message is used to resume the suspended RRC connection.
-- ASN1START -- TAG-RRCRESUME-START RRCResume ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcResume RRCResume-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCResume-IEs ::= SEQUENCE {radioBearerConfigConfiguration of Radio Bearers (DRBs, SRBs) including SDAP/PDCP.RadioBearerConfig OPTIONAL, -- Need MmasterCellGroupConfiguration of the master cell group.OCTET STRING (CONTAINING CellGroupConfig) OPTIONAL, -- Need M measConfig MeasConfig OPTIONAL, -- Need M fullConfig ENUMERATED {true} OPTIONAL, -- Need N lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCResume-v1560-IEs OPTIONAL } RRCResume-v1560-IEs ::= SEQUENCE {radioBearerConfig2Configuration of Radio Bearers (DRBs, SRBs) including SDAP/PDCP. This field can only be used if the UE supports NR-DC or NE-DC.OCTET STRING (CONTAINING RadioBearerConfig) OPTIONAL, -- Need Msk-CounterA counter used to derive S-KgNB or S-KeNB based on the newly derived KgNB during RRC Resume. The field is only included when there is one or more RB with keyToUse set to secondaryor mrdc-SecondaryCellGroup is included.SK-Counter OPTIONAL, -- Need N nonCriticalExtension RRCResume-v1610-IEs OPTIONAL } RRCResume-v1610-IEs ::= SEQUENCE {idleModeMeasurementReq-r16This field indicates that the UE shall report the idle/inactive measurements, if available, to the network in the RRCResumeComplete messageENUMERATED {true} OPTIONAL, -- Need NrestoreMCG-SCells-r16Indicates that the UE shall restore the MCG SCells from the UE Inactive AS Context, if stored.ENUMERATED {true} OPTIONAL, -- Need NrestoreSCG-r16Indicates that the UE shall restore the SCG configurationsfrom the UE Inactive AS Context, if stored.ENUMERATED {true} OPTIONAL, -- Need Nmrdc-SecondaryCellGroup-r16Includes an RRC message for SCG configuration in NR-DC or NE-DC. For NR-DC (nr-SCG), mrdc-SecondaryCellGroup contains the RRCReconfiguration message as generated (entirely) by SN gNB. In this version of the specification, the RRC message can only include fields secondaryCellGroup(with at least reconfigurationWithSync),otherConfigand measConfig. For NE-DC (eutra-SCG), mrdc-SecondaryCellGroup includes the E-UTRA RRCConnectionReconfiguration message as specified in TS 36.331 [10]. In this version of the specification, the E-UTRA RRC message only include the field scg-Configuration with at least mobilityControlInfoSCG.CHOICE { nr-SCG-r16 OCTET STRING (CONTAINING RRCReconfiguration), eutra-SCG-r16 OCTET STRING } OPTIONAL, -- Cond RestoreSCGneedForGapsConfigNR-r16Configuration for the UE to report measurement gap requirement information of NR target bands in the RRCReconfigurationComplete and RRCResumeComplete message.SetupRelease {NeedForGapsConfigNR-r16} OPTIONAL, -- Need M nonCriticalExtension SEQUENCE{} OPTIONAL } -- TAG-RRCRESUME-STOP -- ASN1STOP
RRCResume-IEs field descriptions |
---|
idleModeMeasurementReq This field indicates that the UE shall report the idle/inactive measurements, if available, to the network in the RRCResumeComplete message |
masterCellGroup Configuration of the master cell group. |
mrdc-SecondaryCellGroup Includes an RRC message for SCG configuration in NR-DC or NE-DC. For NR-DC (nr-SCG), mrdc-SecondaryCellGroup contains the RRCReconfiguration message as generated (entirely) by SN gNB. In this version of the specification, the RRC message can only include fields secondaryCellGroup(with at least reconfigurationWithSync),otherConfigand measConfig. For NE-DC (eutra-SCG), mrdc-SecondaryCellGroup includes the E-UTRA RRCConnectionReconfiguration message as specified in TS 36.331 [10]. In this version of the specification, the E-UTRA RRC message only include the field scg-Configuration with at least mobilityControlInfoSCG. |
needForGapsConfigNR Configuration for the UE to report measurement gap requirement information of NR target bands in the RRCReconfigurationComplete and RRCResumeComplete message. |
radioBearerConfig Configuration of Radio Bearers (DRBs, SRBs) including SDAP/PDCP. |
radioBearerConfig2 Configuration of Radio Bearers (DRBs, SRBs) including SDAP/PDCP. This field can only be used if the UE supports NR-DC or NE-DC. |
restoreMCG-SCells Indicates that the UE shall restore the MCG SCells from the UE Inactive AS Context, if stored. |
restoreSCG Indicates that the UE shall restore the SCG configurationsfrom the UE Inactive AS Context, if stored. |
sk-Counter A counter used to derive S-KgNB or S-KeNB based on the newly derived KgNB during RRC Resume. The field is only included when there is one or more RB with keyToUse set to secondaryor mrdc-SecondaryCellGroup is included. |
Conditional Presence | Explanation |
---|---|
RestoreSCG | The field is mandatory present if restoreSCG is included. It is optionally present, Need M, otherwise. |
The RRCResumeComplete message is used to confirm the successful completion of an RRC connection resumption.
-- ASN1START -- TAG-RRCRESUMECOMPLETE-START RRCResumeComplete ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcResumeComplete RRCResumeComplete-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCResumeComplete-IEs ::= SEQUENCE { dedicatedNAS-Message DedicatedNAS-Message OPTIONAL,selectedPLMN-IdentityIndex of the PLMN selected by the UE from the plmn-IdentityInfoListor npn-IdentityInfoListfields included in SIB1.INTEGER (1..maxPLMN) OPTIONAL,uplinkTxDirectCurrentListThe Tx Direct Current locations for the configured serving cells and BWPs if requested by the NW (see reportUplinkTxDirectCurrent in CellGroupConfig).UplinkTxDirectCurrentList OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCResumeComplete-v1610-IEs OPTIONAL } RRCResumeComplete-v1610-IEs ::= SEQUENCE {idleMeasAvailable-r16Indication that the UE has idle/inactive measurement report available.ENUMERATED {true} OPTIONAL,measResultIdleEUTRA-r16EUTRA measurement results performed during RRC_INACTIVE.MeasResultIdleEUTRA-r16 OPTIONAL,measResultIdleNR-r16NR measurement results performed during RRC_INACTIVE.MeasResultIdleNR-r16 OPTIONAL, scg-Response-r16 CHOICE { nr-SCG-Response OCTET STRING (CONTAINING RRCReconfigurationComplete), eutra-SCG-Response OCTET STRING } OPTIONAL, ue-MeasurementsAvailable-r16 UE-MeasurementsAvailable-r16 OPTIONAL, mobilityHistoryAvail-r16 ENUMERATED {true} OPTIONAL, mobilityState-r16 ENUMERATED {normal, medium, high, spare} OPTIONAL,needForGapsInfoNR-r16This field is used to indicate the measurement gap requirement information of the UE for NR target bands.NeedForGapsInfoNR-r16 OPTIONAL, nonCriticalExtension RRCResumeComplete-v1640-IEs OPTIONAL } RRCResumeComplete-v1640-IEs ::= SEQUENCE {uplinkTxDirectCurrentTwoCarrierList-r16The Tx Direct Current locations for the configured uplink intra-band CA with two carriers if requested by the NW (see reportUplinkTxDirectCurrentTwoCarrier-r16 in CellGroupConfig).UplinkTxDirectCurrentTwoCarrierList-r16 OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-RRCRESUMECOMPLETE-STOP -- ASN1STOP
RRCResumeComplete-IEs field descriptions |
---|
idleMeasAvailable Indication that the UE has idle/inactive measurement report available. |
measResultIdleEUTRA EUTRA measurement results performed during RRC_INACTIVE. |
measResultIdleNR NR measurement results performed during RRC_INACTIVE. |
needForGapsInfoNR This field is used to indicate the measurement gap requirement information of the UE for NR target bands. |
selectedPLMN-Identity Index of the PLMN selected by the UE from the plmn-IdentityInfoListor npn-IdentityInfoListfields included in SIB1. |
uplinkTxDirectCurrentList The Tx Direct Current locations for the configured serving cells and BWPs if requested by the NW (see reportUplinkTxDirectCurrent in CellGroupConfig). |
uplinkTxDirectCurrentTwoCarrierList The Tx Direct Current locations for the configured uplink intra-band CA with two carriers if requested by the NW (see reportUplinkTxDirectCurrentTwoCarrier-r16 in CellGroupConfig). |
The RRCResumeRequest message is used to request the resumption of a suspended RRC connection or perform an RNA update.
-- ASN1START -- TAG-RRCRESUMEREQUEST-START RRCResumeRequest ::= SEQUENCE { rrcResumeRequest RRCResumeRequest-IEs } RRCResumeRequest-IEs ::= SEQUENCE {resumeIdentityUE identity to facilitate UE context retrieval at gNB.ShortI-RNTI-Value,resumeMAC-IAuthentication token to facilitate UE authentication at gNB. The 16 least significant bits of the MAC-I calculated using the AS security configuration as specified in 5.3.13.3.BIT STRING (SIZE (16)),resumeCauseProvides the resume cause for the RRC connection resume request as provided by the upper layers or RRC. The network is not expected to reject an RRCResumeRequest due to unknown cause value being used by the UE.ResumeCause, spare BIT STRING (SIZE (1)) } -- TAG-RRCRESUMEREQUEST-STOP -- ASN1STOP
RRCResumeRequest-IEs field descriptions |
---|
resumeCause Provides the resume cause for the RRC connection resume request as provided by the upper layers or RRC. The network is not expected to reject an RRCResumeRequest due to unknown cause value being used by the UE. |
resumeIdentity UE identity to facilitate UE context retrieval at gNB. |
resumeMAC-I Authentication token to facilitate UE authentication at gNB. The 16 least significant bits of the MAC-I calculated using the AS security configuration as specified in 5.3.13.3. |
The RRCResumeRequest1 message is used to request the resumption of a suspended RRC connection or perform an RNA update.
-- ASN1START -- TAG-RRCRESUMEREQUEST1-START RRCResumeRequest1 ::= SEQUENCE { rrcResumeRequest1 RRCResumeRequest1-IEs } RRCResumeRequest1-IEs ::= SEQUENCE {resumeIdentityUE identity to facilitate UE context retrieval at gNB.I-RNTI-Value,resumeMAC-IAuthentication token to facilitate UE authentication at gNB. The 16 least significant bits of the MAC-I calculated using the AS security configuration as specified in 5.3.13.3.BIT STRING (SIZE (16)),resumeCauseProvides the resume cause for the RRCResumeRequest1 as provided by the upper layers or RRC. A gNB is not expected to reject an RRCResumeRequest1 due to unknown cause value being used by the UE.ResumeCause, spare BIT STRING (SIZE (1)) } -- TAG-RRCRESUMEREQUEST1-STOP -- ASN1STOP
RRCResumeRequest1-IEs field descriptions |
---|
resumeCause Provides the resume cause for the RRCResumeRequest1 as provided by the upper layers or RRC. A gNB is not expected to reject an RRCResumeRequest1 due to unknown cause value being used by the UE. |
resumeIdentity UE identity to facilitate UE context retrieval at gNB. |
resumeMAC-I Authentication token to facilitate UE authentication at gNB. The 16 least significant bits of the MAC-I calculated using the AS security configuration as specified in 5.3.13.3. |
The RRCSetup message is used to establish SRB1.
-- ASN1START -- TAG-RRCSETUP-START RRCSetup ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcSetup RRCSetup-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCSetup-IEs ::= SEQUENCE {radioBearerConfigOnly SRB1 can be configured in RRC setup.RadioBearerConfig,masterCellGroupThe network configures only the RLC bearer for the SRB1, mac-CellGroupConfig, physicalCellGroupConfig and spCellConfig.OCTET STRING (CONTAINING CellGroupConfig), lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } -- TAG-RRCSETUP-STOP -- ASN1STOP
RRCSetup-IEs field descriptions |
---|
masterCellGroup The network configures only the RLC bearer for the SRB1, mac-CellGroupConfig, physicalCellGroupConfig and spCellConfig. |
radioBearerConfig Only SRB1 can be configured in RRC setup. |
The RRCSetupComplete message is used to confirm the successful completion of an RRC connection establishment.
-- ASN1START -- TAG-RRCSETUPCOMPLETE-START RRCSetupComplete ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcSetupComplete RRCSetupComplete-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCSetupComplete-IEs ::= SEQUENCE {selectedPLMN-IdentityIndex of the PLMN or SNPN selected by the UE from the plmn-IdentityInfoList or npn-IdentityInfoList fields included in SIB1.INTEGER (1..maxPLMN),registeredAMFThis field is used to transfer the GUAMI of the AMF where the UE is registered, as provided by upper layers, see TS 23.003 [21].RegisteredAMF OPTIONAL,guami-TypeThis field is used to indicate whether the GUAMI included is native (derived from native 5G-GUTI) or mapped (from EPS, derived from EPS GUTI) as specified in TS 24.501 [23].ENUMERATED {native, mapped} OPTIONAL, s-NSSAI-List SEQUENCE (SIZE (1..maxNrofS-NSSAI)) OF S-NSSAI OPTIONAL, dedicatedNAS-Message DedicatedNAS-Message, ng-5G-S-TMSI-Value CHOICE { ng-5G-S-TMSI NG-5G-S-TMSI,ng-5G-S-TMSI-Part2The leftmost 9 bits of 5G-S-TMSI.BIT STRING (SIZE (9)) } OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCSetupComplete-v1610-IEs OPTIONAL } RRCSetupComplete-v1610-IEs ::= SEQUENCE {iab-NodeIndication-r16This field is used to indicate that the connection is being established by an IAB-node as specified in TS 38.300 [2].ENUMERATED {true} OPTIONAL,idleMeasAvailable-r16Indication that the UE has idle/inactive measurement report available.ENUMERATED {true} OPTIONAL, ue-MeasurementsAvailable-r16 UE-MeasurementsAvailable-r16 OPTIONAL, mobilityHistoryAvail-r16 ENUMERATED {true} OPTIONAL,mobilityState-r16This field indicates the UE mobility state (as defined in TS 38.304 [20], clause 5.2.4.3) just prior to UE going into RRC_CONNECTED state. The UE indicates the value of medium and high when being in Medium-mobility and High-mobility states respectively. Otherwise the UE indicates the value normal.ENUMERATED {normal, medium, high, spare} OPTIONAL, nonCriticalExtension RRCSetupComplete-v1690-IEs OPTIONAL } RRCSetupComplete-v1690-IEs ::= SEQUENCE {ul-RRC-Segmentation-r16This field indicates the UE supports uplink RRC segmentationof UECapabilityInformation.ENUMERATED {true} OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } RegisteredAMF ::= SEQUENCE { plmn-Identity PLMN-Identity OPTIONAL, amf-Identifier AMF-Identifier } -- TAG-RRCSETUPCOMPLETE-STOP -- ASN1STOP
RRCSetupComplete-IEs field descriptions |
---|
guami-Type This field is used to indicate whether the GUAMI included is native (derived from native 5G-GUTI) or mapped (from EPS, derived from EPS GUTI) as specified in TS 24.501 [23]. |
iab-NodeIndication This field is used to indicate that the connection is being established by an IAB-node as specified in TS 38.300 [2]. |
idleMeasAvailable Indication that the UE has idle/inactive measurement report available. |
mobilityState This field indicates the UE mobility state (as defined in TS 38.304 [20], clause 5.2.4.3) just prior to UE going into RRC_CONNECTED state. The UE indicates the value of medium and high when being in Medium-mobility and High-mobility states respectively. Otherwise the UE indicates the value normal. |
ng-5G-S-TMSI-Part2 The leftmost 9 bits of 5G-S-TMSI. |
registeredAMF This field is used to transfer the GUAMI of the AMF where the UE is registered, as provided by upper layers, see TS 23.003 [21]. |
selectedPLMN-Identity Index of the PLMN or SNPN selected by the UE from the plmn-IdentityInfoList or npn-IdentityInfoList fields included in SIB1. |
ul-RRC-Segmentation This field indicates the UE supports uplink RRC segmentationof UECapabilityInformation. |
The RRCSetupRequest message is used to request the establishment of an RRC connection.
-- ASN1START -- TAG-RRCSETUPREQUEST-START RRCSetupRequest ::= SEQUENCE { rrcSetupRequest RRCSetupRequest-IEs } RRCSetupRequest-IEs ::= SEQUENCE {ue-IdentityUE identity included to facilitate contention resolution by lower layers.InitialUE-Identity,establishmentCauseProvides the establishment cause for the RRCSetupRequest in accordance with the information received from upper layers. gNB is not expected to reject an RRCSetupRequest due to unknown cause value being used by the UE.EstablishmentCause, spare BIT STRING (SIZE (1)) } InitialUE-Identity ::= CHOICE {ng-5G-S-TMSI-Part1The rightmost 39 bits of 5G-S-TMSI.BIT STRING (SIZE (39)),randomValueInteger value in the range 0 to 239 – 1.BIT STRING (SIZE (39)) } EstablishmentCause ::= ENUMERATED { emergency, highPriorityAccess, mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, mps-PriorityAccess, mcs-PriorityAccess, spare6, spare5, spare4, spare3, spare2, spare1} -- TAG-RRCSETUPREQUEST-STOP -- ASN1STOP
RRCSetupRequest-IEs field descriptions |
---|
establishmentCause Provides the establishment cause for the RRCSetupRequest in accordance with the information received from upper layers. gNB is not expected to reject an RRCSetupRequest due to unknown cause value being used by the UE. |
ue-Identity UE identity included to facilitate contention resolution by lower layers. |
InitialUE-Identity field descriptions |
---|
ng-5G-S-TMSI-Part1 The rightmost 39 bits of 5G-S-TMSI. |
randomValue Integer value in the range 0 to 239 – 1. |
The RRCSystemInfoRequest message is used to request SI message(s) required by the UE as specified in clause 5.2.2.3.3 and 5.2.2.3.3a.
-- ASN1START -- TAG-RRCSYSTEMINFOREQUEST-START RRCSystemInfoRequest ::= SEQUENCE { criticalExtensions CHOICE { rrcSystemInfoRequest RRCSystemInfoRequest-IEs, criticalExtensionsFuture-r16 CHOICE { rrcPosSystemInfoRequest-r16 RRC-PosSystemInfoRequest-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } } RRCSystemInfoRequest-IEs ::= SEQUENCE {requested-SI-ListContains a list of requested SI messages. According to the order of entry in the list of SI messages configured by schedulingInfoList in si-SchedulingInfo in SIB1, first bit corresponds to first/leftmost listed SI message, second bit corresponds to second listed SI message, and so on.BIT STRING (SIZE (maxSI-Message)), --32bits spare BIT STRING (SIZE (12)) } RRC-PosSystemInfoRequest-r16-IEs ::= SEQUENCE {requestedPosSI-ListContains a list of requested SI messages. According to the order of entry in the list of SI messages configured by posSchedulingInfoList in posSI-SchedulingInfo in SIB1, first bit corresponds to first/leftmost listed SI message, second bit corresponds to second listed SI message, and so on.BIT STRING (SIZE (maxSI-Message)), --32bits spare BIT STRING (SIZE (11)) } -- TAG-RRCSYSTEMINFOREQUEST-STOP -- ASN1STOP
RRCSystemInfoRequest-IEs field descriptions |
---|
requested-SI-List Contains a list of requested SI messages. According to the order of entry in the list of SI messages configured by schedulingInfoList in si-SchedulingInfo in SIB1, first bit corresponds to first/leftmost listed SI message, second bit corresponds to second listed SI message, and so on. |
requestedPosSI-List Contains a list of requested SI messages. According to the order of entry in the list of SI messages configured by posSchedulingInfoList in posSI-SchedulingInfo in SIB1, first bit corresponds to first/leftmost listed SI message, second bit corresponds to second listed SI message, and so on. |
The SCGFailureInformation message is used to provide information regarding NR SCG failures detected by the UE.
-- ASN1START -- TAG-SCGFAILUREINFORMATION-START SCGFailureInformation ::= SEQUENCE { criticalExtensions CHOICE { scgFailureInformation SCGFailureInformation-IEs, criticalExtensionsFuture SEQUENCE {} } } SCGFailureInformation-IEs ::= SEQUENCE { failureReportSCG FailureReportSCG OPTIONAL, nonCriticalExtension SCGFailureInformation-v1590-IEs OPTIONAL } SCGFailureInformation-v1590-IEs ::= SEQUENCE { lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } FailureReportSCG ::= SEQUENCE { failureType ENUMERATED { t310-Expiry, randomAccessProblem, rlc-MaxNumRetx, synchReconfigFailureSCG, scg-ReconfigFailure, srb3-IntegrityFailure, other-r16, spare1},measResultFreqListThe field contains available results of measurements on NR frequencies the UE is configured to measure by measConfig.MeasResultFreqList OPTIONAL,measResultSCG-FailureThe field contains the MeasResultSCG-Failure IE which includes available results of measurements on NR frequencies the UE is configured to measure by the NR SCG RRCReconfiguration message.OCTET STRING (CONTAINING MeasResultSCG-Failure) OPTIONAL, ..., [[ locationInfo-r16 LocationInfo-r16 OPTIONAL, failureType-v1610 ENUMERATED {scg-lbtFailure-r16, beamFailureRecoveryFailure-r16, t312-Expiry-r16, bh-RLF-r16, spare4, spare3, spare2, spare1} OPTIONAL ]] } MeasResultFreqList ::= SEQUENCE (SIZE (1..maxFreq)) OF MeasResult2NR -- TAG-SCGFAILUREINFORMATION-STOP -- ASN1STOP
SCGFailureInformation field descriptions |
---|
measResultFreqList The field contains available results of measurements on NR frequencies the UE is configured to measure by measConfig. |
measResultSCG-Failure The field contains the MeasResultSCG-Failure IE which includes available results of measurements on NR frequencies the UE is configured to measure by the NR SCG RRCReconfiguration message. |
The SCGFailureInformationEUTRA message is used to provide information regarding E-UTRA SCG failures detected by the UE.
-- ASN1START -- TAG-SCGFAILUREINFORMATIONEUTRA-START SCGFailureInformationEUTRA ::= SEQUENCE { criticalExtensions CHOICE { scgFailureInformationEUTRA SCGFailureInformationEUTRA-IEs, criticalExtensionsFuture SEQUENCE {} } } SCGFailureInformationEUTRA-IEs ::= SEQUENCE { failureReportSCG-EUTRA FailureReportSCG-EUTRA OPTIONAL, nonCriticalExtension SCGFailureInformationEUTRA-v1590-IEs OPTIONAL } SCGFailureInformationEUTRA-v1590-IEs ::= SEQUENCE { lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } FailureReportSCG-EUTRA ::= SEQUENCE { failureType ENUMERATED { t313-Expiry, randomAccessProblem,rlc-MaxNumRetx, scg-ChangeFailure, spare4, spare3, spare2, spare1}, measResultFreqListMRDC MeasResultFreqListFailMRDC OPTIONAL, measResultSCG-FailureMRDC OCTET STRING OPTIONAL, ..., [[ locationInfo-r16 LocationInfo-r16 OPTIONAL ]] } MeasResultFreqListFailMRDC ::= SEQUENCE (SIZE (1.. maxFreq)) OF MeasResult2EUTRA -- TAG-SCGFAILUREINFORMATIONEUTRA-STOP -- ASN1STOP
The SecurityModeCommand message is used to command the activation of AS security.
-- ASN1START -- TAG-SECURITYMODECOMMAND-START SecurityModeCommand ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { securityModeCommand SecurityModeCommand-IEs, criticalExtensionsFuture SEQUENCE {} } } SecurityModeCommand-IEs ::= SEQUENCE { securityConfigSMC SecurityConfigSMC, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } SecurityConfigSMC ::= SEQUENCE { securityAlgorithmConfig SecurityAlgorithmConfig, ... } -- TAG-SECURITYMODECOMMAND-STOP -- ASN1STOP
SCGFailureInformationEUTRA field descriptions |
---|
measResultFreqListMRDC The field contains available results of measurements on E-UTRA frequencies the UE is configured to measure by measConfig. |
measResultSCG-FailureMRDC Includes the E-UTRA MeasResultSCG-FailureMRDC IE as specified in TS 36.331 [10]. The field contains available results of measurements on E-UTRA frequencies the UE is configured to measure by the E-UTRA RRCConnectionReconfiguration message. |
The SecurityModeComplete message is used to confirm the successful completion of a security mode command.
-- ASN1START -- TAG-SECURITYMODECOMPLETE-START SecurityModeComplete ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { securityModeComplete SecurityModeComplete-IEs, criticalExtensionsFuture SEQUENCE {} } } SecurityModeComplete-IEs ::= SEQUENCE { lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } -- TAG-SECURITYMODECOMPLETE-STOP -- ASN1STOP
The SecurityModeFailure message is used to indicate an unsuccessful completion of a security mode command.
-- ASN1START -- TAG-SECURITYMODEFAILURE-START SecurityModeFailure ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { securityModeFailure SecurityModeFailure-IEs, criticalExtensionsFuture SEQUENCE {} } } SecurityModeFailure-IEs ::= SEQUENCE { lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } -- TAG-SECURITYMODEFAILURE-STOP -- ASN1STOP
SIB1 contains information relevant when evaluating if a UE is allowed to access a cell and defines the scheduling of other system information. It also contains radio resource configuration information that is common for all UEs and barring information applied to the unified access control.
-- ASN1START -- TAG-SIB1-START SIB1 ::= SEQUENCE {cellSelectionInfoParameters for cell selection related to the serving cell.SEQUENCE {q-RxLevMinParameter "Qrxlevmin" in TS 38.304 [20], applicable for serving cell.Q-RxLevMin,q-RxLevMinOffsetParameter "Qrxlevminoffset" in TS 38.304 [20]. Actual value Qrxlevminoffset = field value * 2 [dB]. If absent, the UE applies the (default) value of 0 dB for Qrxlevminoffset. Affects the minimum required Rx level in the cell.INTEGER (1..8) OPTIONAL, -- Need Sq-RxLevMinSULParameter "Qrxlevmin" in TS 38.304 [20], applicable for serving cell.Q-RxLevMin OPTIONAL, -- Need Rq-QualMinParameter "Qqualmin" in TS 38.304 [20], applicable for serving cell. If the field is absent, the UE applies the (default) value of negative infinity for Qqualmin.Q-QualMin OPTIONAL, -- Need Sq-QualMinOffsetParameter "Qqualminoffset" in TS 38.304 [20]. Actual value Qqualminoffset = field value [dB]. If the field is absent, the UE applies the (default) value of 0 dB for Qqualminoffset.Affects the minimum required quality level in the cell.INTEGER (1..8) OPTIONAL -- Need S } OPTIONAL, -- Cond Standalone cellAccessRelatedInfo CellAccessRelatedInfo, connEstFailureControl ConnEstFailureControl OPTIONAL, -- Need R si-SchedulingInfo SI-SchedulingInfo OPTIONAL, -- Need RservingCellConfigCommonConfiguration of the serving cell.ServingCellConfigCommonSIB OPTIONAL, -- Need Rims-EmergencySupportIndicates whether the cell supports IMS emergency bearer services for UEs in limited service mode. If absent, IMS emergency call is not supported by the network in the cell for UEs in limited service mode.ENUMERATED {true} OPTIONAL, -- Need ReCallOverIMS-SupportIndicates whether the cell supports eCall over IMS services as defined in TS 23.501 [32]. If absent, eCall over IMS is not supported by the network in the cell.ENUMERATED {true} OPTIONAL, -- Need Rue-TimersAndConstantsTimer and constant values to be used by the UE. The cell operating as PCell always provides this field.UE-TimersAndConstants OPTIONAL, -- Need R uac-BarringInfo SEQUENCE {uac-BarringForCommonCommon access control parameters for each access category. Common values are used for all PLMNs/SNPNs, unless overwritten by the PLMN/SNPN specific configuration provided in uac-BarringPerPLMN-List. The parameters are specified by providing an index to the set of configurations (uac-BarringInfoSetList). UE behaviour upon absence of this field is specified in clause 5.3.14.2.UAC-BarringPerCatList OPTIONAL, -- Need S uac-BarringPerPLMN-List UAC-BarringPerPLMN-List OPTIONAL, -- Need S uac-BarringInfoSetList UAC-BarringInfoSetList,uac-AccessCategory1-SelectionAssistanceInfoInformation used to determine whether Access Category 1 applies to the UE, as defined in TS 22.261 [25]. If plmnCommon is chosen,the UAC-AccessCategory1-SelectionAssistanceInfo is applicable to all the PLMNs and SNPNs in plmn-IdentityInfoListand npn-IdentityInfoList.If individualPLMNList is chosen, the 1st entry in the list corresponds to the first network within all of the PLMNsand SNPNs across the plmn-IdentityListand the npn-IdentityInfoList, the 2nd entry in the list corresponds to the second network within all of the PLMNsand SNPNs across the plmn-IdentityListand the npn-IdentityInfoListand so on.If uac-AC1-SelectAssistInfo-r16 is present, the UE shall ignore the uac-AccessCategory1-SelectionAssistanceInfo.CHOICE { plmnCommon UAC-AccessCategory1-SelectionAssistanceInfo, individualPLMNList SEQUENCE (SIZE (2..maxPLMN)) OF UAC-AccessCategory1-SelectionAssistanceInfo } OPTIONAL -- Need S } OPTIONAL, -- Need RuseFullResumeIDIndicates which resume identifier and Resume request message should be used. UE uses fullI-RNTI and RRCResumeRequest1 if the field is present, or shortI-RNTI and RRCResumeRequest if the field is absent.ENUMERATED {true} OPTIONAL, -- Need R lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SIB1-v1610-IEs OPTIONAL } SIB1-v1610-IEs ::= SEQUENCE {idleModeMeasurementsEUTRA-r16This field indicates that a UE that is configured for EUTRA idle/inactive measurements shall perform the measurements while camping in this cell and report availability of these measurements when establishing or resuming a connection in this cell. If absent, a UE is not required to perform EUTRA idle/inactive measurements.ENUMERATED{true} OPTIONAL, -- Need RidleModeMeasurementsNR-r16This field indicates that a UE that is configured for NR idle/inactive measurements shall perform the measurements while camping in this cell and report availability of these measurements when establishing or resuming a connection in this cell. If absent, a UE is not required to perform NR idle/inactive measurements.ENUMERATED{true} OPTIONAL, -- Need R posSI-SchedulingInfo-r16 PosSI-SchedulingInfo-r16 OPTIONAL, -- Need R nonCriticalExtension SIB1-v1630-IEs OPTIONAL } SIB1-v1630-IEs ::= SEQUENCE { uac-BarringInfo-v1630 SEQUENCE {uac-AC1-SelectAssistInfo-r16Information used to determine whether Access Category 1 applies to the UE, as defined in TS 22.261 [25]. The 1st entry in the list corresponds to the first network within all of the PLMNsand SNPNs across the plmn-IdentityListand npn-IdentityInfoList, the 2nd entry in the list corresponds to the second network within all of the PLMNsand SNPNs across the plmn-IdentityListand the npn-IdentityInfoListand so on.Value notConfigured indicates that Access Category1 isnot configured for the corresponding PLMN/SNPN.SEQUENCE (SIZE (2..maxPLMN)) OF UAC-AC1-SelectAssistInfo-r16 } OPTIONAL, -- Need R nonCriticalExtension SEQUENCE {} OPTIONAL } UAC-AccessCategory1-SelectionAssistanceInfo ::= ENUMERATED {a, b, c} UAC-AC1-SelectAssistInfo-r16 ::= ENUMERATED {a, b, c, notConfigured} -- TAG-SIB1-STOP -- ASN1STOP
SIB1 field descriptions |
---|
cellSelectionInfo Parameters for cell selection related to the serving cell. |
eCallOverIMS-Support Indicates whether the cell supports eCall over IMS services as defined in TS 23.501 [32]. If absent, eCall over IMS is not supported by the network in the cell. |
idleModeMeasurementsEUTRA This field indicates that a UE that is configured for EUTRA idle/inactive measurements shall perform the measurements while camping in this cell and report availability of these measurements when establishing or resuming a connection in this cell. If absent, a UE is not required to perform EUTRA idle/inactive measurements. |
idleModeMeasurementsNR This field indicates that a UE that is configured for NR idle/inactive measurements shall perform the measurements while camping in this cell and report availability of these measurements when establishing or resuming a connection in this cell. If absent, a UE is not required to perform NR idle/inactive measurements. |
ims-EmergencySupport Indicates whether the cell supports IMS emergency bearer services for UEs in limited service mode. If absent, IMS emergency call is not supported by the network in the cell for UEs in limited service mode. |
q-QualMin Parameter "Qqualmin" in TS 38.304 [20], applicable for serving cell. If the field is absent, the UE applies the (default) value of negative infinity for Qqualmin. |
q-QualMinOffset Parameter "Qqualminoffset" in TS 38.304 [20]. Actual value Qqualminoffset = field value [dB]. If the field is absent, the UE applies the (default) value of 0 dB for Qqualminoffset.Affects the minimum required quality level in the cell. |
q-RxLevMin Parameter "Qrxlevmin" in TS 38.304 [20], applicable for serving cell. |
q-RxLevMinOffset Parameter "Qrxlevminoffset" in TS 38.304 [20]. Actual value Qrxlevminoffset = field value * 2 [dB]. If absent, the UE applies the (default) value of 0 dB for Qrxlevminoffset. Affects the minimum required Rx level in the cell. |
q-RxLevMinSUL Parameter "Qrxlevmin" in TS 38.304 [20], applicable for serving cell. |
servingCellConfigCommon Configuration of the serving cell. |
uac-AccessCategory1-SelectionAssistanceInfo Information used to determine whether Access Category 1 applies to the UE, as defined in TS 22.261 [25]. If plmnCommon is chosen,the UAC-AccessCategory1-SelectionAssistanceInfo is applicable to all the PLMNs and SNPNs in plmn-IdentityInfoListand npn-IdentityInfoList.If individualPLMNList is chosen, the 1st entry in the list corresponds to the first network within all of the PLMNsand SNPNs across the plmn-IdentityListand the npn-IdentityInfoList, the 2nd entry in the list corresponds to the second network within all of the PLMNsand SNPNs across the plmn-IdentityListand the npn-IdentityInfoListand so on.If uac-AC1-SelectAssistInfo-r16 is present, the UE shall ignore the uac-AccessCategory1-SelectionAssistanceInfo. |
uac-AC1-SelectAssistInfo Information used to determine whether Access Category 1 applies to the UE, as defined in TS 22.261 [25]. The 1st entry in the list corresponds to the first network within all of the PLMNsand SNPNs across the plmn-IdentityListand npn-IdentityInfoList, the 2nd entry in the list corresponds to the second network within all of the PLMNsand SNPNs across the plmn-IdentityListand the npn-IdentityInfoListand so on.Value notConfigured indicates that Access Category1 isnot configured for the corresponding PLMN/SNPN. |
uac-BarringForCommon Common access control parameters for each access category. Common values are used for all PLMNs/SNPNs, unless overwritten by the PLMN/SNPN specific configuration provided in uac-BarringPerPLMN-List. The parameters are specified by providing an index to the set of configurations (uac-BarringInfoSetList). UE behaviour upon absence of this field is specified in clause 5.3.14.2. |
ue-TimersAndConstants Timer and constant values to be used by the UE. The cell operating as PCell always provides this field. |
useFullResumeID Indicates which resume identifier and Resume request message should be used. UE uses fullI-RNTI and RRCResumeRequest1 if the field is present, or shortI-RNTI and RRCResumeRequest if the field is absent. |
Conditional Presence | Explanation |
---|---|
Standalone | The field is mandatory present in a cell that supports standalone operation, otherwise it is absent. |
The SidelinkUEinformationNR message is used for the indication of NR sidelink UE information to the network.
-- ASN1START -- TAG-SIDELINKUEINFORMATIONNR-START SidelinkUEInformationNR-r16::= SEQUENCE { criticalExtensions CHOICE { sidelinkUEInformationNR-r16 SidelinkUEInformationNR-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } SidelinkUEInformationNR-r16-IEs ::= SEQUENCE {sl-RxInterestedFreqList-r16Indicates the index of frequency on which the UE is interested to receive NR sidelink communication. The value 1 corresponds to the frequency of first entry in sl-FreqInfoList broadcast in SIB12, the value 2 corresponds to the frequency of second entry in sl-FreqInfoList broadcast in SIB12 and so on. In this release, only value 1 can be included in the interested frequency list.SL-InterestedFreqList-r16 OPTIONAL, sl-TxResourceReqList-r16 SL-TxResourceReqList-r16 OPTIONAL, sl-FailureList-r16 SL-FailureList-r16 OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } SL-InterestedFreqList-r16 ::= SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF INTEGER (1..maxNrofFreqSL-r16) SL-TxResourceReqList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-TxResourceReq-r16 SL-TxResourceReq-r16 ::= SEQUENCE {sl-DestinationIdentity-r16Indicates the destination for which the SL failure is reporting for unicast.SL-DestinationIdentity-r16,sl-CastType-r16Indicates the cast type for the corresponding destination for which to request the resource.ENUMERATED {broadcast, groupcast, unicast, spare1}, sl-RLC-ModeIndicationList-r16 SEQUENCE (SIZE (1.. maxNrofSLRB-r16)) OF SL-RLC-ModeIndication-r16 OPTIONAL,sl-QoS-InfoList-r16Includes the QoS profile of the sidelink QoS flow as specified in TS 23.287 [55].SEQUENCE (SIZE (1..maxNrofSL-QFIsPerDest-r16)) OF SL-QoS-Info-r16 OPTIONAL,sl-TypeTxSyncList-r16A list of synchronization reference used by the UE. The UE shall include the same number of entries, listed in the same order, as in sl-TxInterestedFreqList, i.e. one for each carrier frequency included in sl-TxInterestedFreqList.SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-TypeTxSync-r16 OPTIONAL,sl-TxInterestedFreqList-r16Each entry of this field indicates the index of frequency on which the UE is interested to transmit NR sidelink communication. The value 1 corresponds to the frequency of first entry in sl-FreqInfoList broadcast in SIB12, the value 2 corresponds to the frequency of second entry in sl-FreqInfoList broadcast in SIB12 and so on. In this release, only value 1 can be included in the interested frequency list. In this release, only one entry can be included in the list.SL-TxInterestedFreqList-r16 OPTIONAL,sl-CapabilityInformationSidelink-r16Includes the UECapabilityInformationSidelink message (which can be also included in ueCapabilityInformationSidelink-r16 in UECapabilityEnquirySidelink from peer UE) received from the peer UE.OCTET STRING OPTIONAL } SL-TxInterestedFreqList-r16 ::= SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF INTEGER (1..maxNrofFreqSL-r16) SL-QoS-Info-r16 ::= SEQUENCE {sl-QoS-FlowIdentity-r16This identity uniquely identifies one sidelink QoS flow between the UE and the network in the scope of UE, which is unique for different destination and cast type.SL-QoS-FlowIdentity-r16, sl-QoS-Profile-r16 SL-QoS-Profile-r16 OPTIONAL } SL-RLC-ModeIndication-r16 ::= SEQUENCE { sl-Mode-r16 CHOICE { sl-AM-Mode-r16 NULL, sl-UM-Mode-r16 NULL },sl-QoS-InfoList-r16Includes the QoS profile of the sidelink QoS flow as specified in TS 23.287 [55].SEQUENCE (SIZE (1..maxNrofSL-QFIsPerDest-r16)) OF SL-QoS-Info-r16 } SL-FailureList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-Failure-r16 SL-Failure-r16 ::= SEQUENCE {sl-DestinationIdentity-r16Indicates the destination for which the SL failure is reporting for unicast.SL-DestinationIdentity-r16,sl-Failure-r16Indicates the sidelink failure cause for the sidelink RLF (value rlf) and sidelink AS configuration failure (value configFailure) for the associated destination for unicast.ENUMERATED {rlf,configFailure, spare6, spare5, spare4, spare3, spare2, spare1} } -- TAG-SIDELINKUEINFORMATIONNR-STOP -- ASN1STOP
SidelinkUEinformationNR field descriptions |
---|
sl-RxInterestedFreqList Indicates the index of frequency on which the UE is interested to receive NR sidelink communication. The value 1 corresponds to the frequency of first entry in sl-FreqInfoList broadcast in SIB12, the value 2 corresponds to the frequency of second entry in sl-FreqInfoList broadcast in SIB12 and so on. In this release, only value 1 can be included in the interested frequency list. |
sl-TxResourceReq Parameters to request the transmission resources for NR sidelink communication to the network in the Sidelink UE Information report. |
SL-TxResourceReq field descriptions |
---|
sl-CapabilityInformationSidelink Includes the UECapabilityInformationSidelink message (which can be also included in ueCapabilityInformationSidelink-r16 in UECapabilityEnquirySidelink from peer UE) received from the peer UE. |
sl-CastType Indicates the cast type for the corresponding destination for which to request the resource. |
sl-DestinationIdentity Indicates the destination for which the TX resource request and allocation from the network are concerned. |
sl-QoS-InfoList Includes the QoS profile of the sidelink QoS flow as specified in TS 23.287 [55]. |
sl-QoS-FlowIdentity This identity uniquely identifies one sidelink QoS flow between the UE and the network in the scope of UE, which is unique for different destination and cast type. |
sl-RLC-ModeIndication This field indicates the RLC mode and optionally the related QoS profiles for the sidelink radio bearer, which has not been configured by the network and is initiated by another UE in unicast. The RLC mode for one sidelink radio bearer is aligned between UE and NW by the sl-QoS-FlowIdentity. |
sl-TxInterestedFreqList Each entry of this field indicates the index of frequency on which the UE is interested to transmit NR sidelink communication. The value 1 corresponds to the frequency of first entry in sl-FreqInfoList broadcast in SIB12, the value 2 corresponds to the frequency of second entry in sl-FreqInfoList broadcast in SIB12 and so on. In this release, only value 1 can be included in the interested frequency list. In this release, only one entry can be included in the list. |
sl-TypeTxSyncList A list of synchronization reference used by the UE. The UE shall include the same number of entries, listed in the same order, as in sl-TxInterestedFreqList, i.e. one for each carrier frequency included in sl-TxInterestedFreqList. |
SL-Failure field descriptions |
---|
sl-DestinationIdentity Indicates the destination for which the SL failure is reporting for unicast. |
sl-Failure Indicates the sidelink failure cause for the sidelink RLF (value rlf) and sidelink AS configuration failure (value configFailure) for the associated destination for unicast. |
The SystemInformation message is used to convey one or more System Information Blocks or Positioning System Information Blocks. All the SIBs or posSIBs included are transmitted with the same periodicity.
-- ASN1START -- TAG-SYSTEMINFORMATION-START SystemInformation ::= SEQUENCE { criticalExtensions CHOICE { systemInformation SystemInformation-IEs, criticalExtensionsFuture-r16 CHOICE { posSystemInformation-r16 PosSystemInformation-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } } SystemInformation-IEs ::= SEQUENCE { sib-TypeAndInfo SEQUENCE (SIZE (1..maxSIB)) OF CHOICE { sib2 SIB2, sib3 SIB3, sib4 SIB4, sib5 SIB5, sib6 SIB6, sib7 SIB7, sib8 SIB8, sib9 SIB9, ..., sib10-v1610 SIB10-r16, sib11-v1610 SIB11-r16, sib12-v1610 SIB12-r16, sib13-v1610 SIB13-r16, sib14-v1610 SIB14-r16 }, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-SYSTEMINFORMATION-STOP -- ASN1STOP
The UEAssistanceInformation message is used for the indication of UE assistance information to the network.
-- ASN1START -- TAG-UEASSISTANCEINFORMATION-START UEAssistanceInformation ::= SEQUENCE { criticalExtensions CHOICE { ueAssistanceInformation UEAssistanceInformation-IEs, criticalExtensionsFuture SEQUENCE {} } } UEAssistanceInformation-IEs ::= SEQUENCE {delayBudgetReportIndicates the UE-preferred adjustment to connected mode DRX.DelayBudgetReport OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension UEAssistanceInformation-v1540-IEs OPTIONAL } DelayBudgetReport::= CHOICE {type1Indicates the preferred amount of increment/decrement to the long DRX cycle length with respect to the current configuration. Value in number of milliseconds. Value ms40 corresponds to 40 milliseconds, msMinus40 corresponds to -40 milliseconds and so on.ENUMERATED { msMinus1280, msMinus640, msMinus320, msMinus160,msMinus80, msMinus60, msMinus40, msMinus20, ms0, ms20,ms40, ms60, ms80, ms160, ms320, ms640, ms1280}, ... } UEAssistanceInformation-v1540-IEs ::= SEQUENCE { overheatingAssistance OverheatingAssistance OPTIONAL, nonCriticalExtension UEAssistanceInformation-v1610-IEs OPTIONAL } OverheatingAssistance ::= SEQUENCE { reducedMaxCCs ReducedMaxCCs-r16 OPTIONAL,reducedMaxBW-FR1Indicates the UE's preference on reduced configuration corresponding to the maximum aggregated bandwidth across all downlink carrier(s) and across all uplink carrier(s) of FR1, to address overheating or power saving. This field is allowed to be reported only when UE is configured with serving cell(s) operating on FR1. The aggregated bandwidth across all downlink carrier(s) of FR1 is the sum of bandwidth of active downlink BWP(s) across all activated downlink carrier(s) of FR1. The aggregated bandwidth across all uplink carrier(s) of FR1 is the sum of bandwidth of active uplink BWP(s) across all activated uplink carrier(s) of FR1. If the field is absent from the MaxBW-Preference IE or the OverheatingAssistance IE, it is interpreted as the UE having no preference on the maximum aggregated bandwidth of FR1. When indicated to address overheating, this maximum aggregated bandwidth includes carrier(s) of FR1 of both the NR MCG and the SCG. This maximum aggregated bandwidth only includes carriers of FR1 of the SCG in (NG)EN-DC. Value mhz0 is not used when indicated to address overheating. When indicated to address power saving, this maximum aggregated bandwidth includes carrier(s) of FR1 of the cell group that this UE assistance information is associated with. The aggregated bandwidth can only range up to the current active configuration when indicated to address power savings.ReducedMaxBW-FRx-r16 OPTIONAL,reducedMaxBW-FR2Indicates the UE's preference on reduced configuration corresponding to the maximum aggregated bandwidth across all downlink carrier(s) and across all uplink carrier(s) of FR2, to address overheating or power saving. This field is allowed to be reported only when UE is configured with serving cell(s) operating on FR2.The aggregated bandwidth across all downlink carrier(s) of FR2 is the sum of bandwidth of active downlink BWP(s) across all activated downlink carrier(s) of FR2. The aggregated bandwidth across all uplink carrier(s) of FR2 is the sum of bandwidth of active uplink BWP(s) across all activated uplink carrier(s) of FR2. If the field is absent from the MaxBW-Preference IE or the OverheatingAssistance IE, it is interpreted as the UE having no preference on the maximum aggregated bandwidth of FR2. When indicated to address overheating, this maximum aggregated bandwidth includes carrier(s)of FR2 of both the NR MCG and the NR SCG. This maximum aggregated bandwidth only includes carriers of FR2 of the SCG in (NG)EN-DC. When indicated to address power saving, this maximum aggregated bandwidth includes carrier(s) of FR2 of the cell group that this UE assistance information is associated with. The aggregated bandwidth can only range up to the current active configuration when indicated to address power savings.ReducedMaxBW-FRx-r16 OPTIONAL, reducedMaxMIMO-LayersFR1 SEQUENCE {reducedMIMO-LayersFR1-DLIndicates the UE's preference on reduced configuration corresponding to the maximum number of downlink MIMO layers of each serving cell operating on FR1 indicated by the field, to address overheating or power saving. This field is allowed to be reported only when UE is configured with serving cells operating on FR1. The maximum number of downlink MIMO layers can only range up to the maximum number of MIMO layers configured across all activated downlink carrier(s) of FR1 in the cell group when indicated to address power savings.MIMO-LayersDL,reducedMIMO-LayersFR1-ULIndicates the UE's preference on reduced configuration corresponding to the maximum number of uplink MIMO layers of each serving cell operating on FR1 indicated by the field, to address overheating or power saving (see NOTE 1). This field is allowed to be reported only when UE is configured with serving cells operating on FR1. The maximum number of uplink MIMO layerscan only range up to the maximum number of MIMO layers configured across all activated uplink carrier(s) of FR1 in the cell group when indicated to address power savings.MIMO-LayersUL } OPTIONAL, reducedMaxMIMO-LayersFR2 SEQUENCE {reducedMIMO-LayersFR2-DLIndicates the UE's preference on reduced configuration corresponding to the maximum number of downlink MIMO layers of each serving cell operating on FR2 indicated by the field, to address overheating or power saving. This field is allowed to be reported only when UE is configured with serving cells operating on FR2. The maximum number of downlink MIMO layers can only range up to the maximum number of MIMO layers configured across all activated downlink carrier(s) of FR2 in the cell group when indicated to address power savings.MIMO-LayersDL,reducedMIMO-LayersFR2-ULIndicates the UE's preference on reduced configuration corresponding to the maximum number of uplink MIMO layers of each serving cell operating on FR2 indicated by the field, to address overheating or power saving (see NOTE 1). This field is allowed to be reported only when UE is configured with serving cells operating on FR2. The maximum number of uplink MIMO layers can only range up to the maximum number of MIMO layers configured across all activated uplink carrier(s) of FR2 in the cell group when indicated to address power savings.MIMO-LayersUL } OPTIONAL } ReducedAggregatedBandwidth ::= ENUMERATED {mhz0, mhz10, mhz20, mhz30, mhz40, mhz50, mhz60, mhz80, mhz100, mhz200, mhz300, mhz400} UEAssistanceInformation-v1610-IEs ::= SEQUENCE { idc-Assistance-r16 IDC-Assistance-r16 OPTIONAL, drx-Preference-r16 DRX-Preference-r16 OPTIONAL, maxBW-Preference-r16 MaxBW-Preference-r16 OPTIONAL, maxCC-Preference-r16 MaxCC-Preference-r16 OPTIONAL, maxMIMO-LayerPreference-r16 MaxMIMO-LayerPreference-r16 OPTIONAL,minSchedulingOffsetPreference-r16Indicates the UE's preferences on minimumSchedulingOffset of cross-slot scheduling for power saving.MinSchedulingOffsetPreference-r16 OPTIONAL, releasePreference-r16 ReleasePreference-r16 OPTIONAL,sl-UE-AssistanceInformationNR-r16Indicates the traffic characteristic of sidelink logical channel(s), specified in the IE SL-TrafficPatternInfo, that are setup for NR sidelink communication.SL-UE-AssistanceInformationNR-r16 OPTIONAL,referenceTimeInfoPreference-r16Indicates whether the UE prefers being provisioned with the timing information specified in the IE ReferenceTimeInfo.BOOLEAN OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } IDC-Assistance-r16 ::= SEQUENCE {affectedCarrierFreqList-r16Indicates a list of NR carrier frequencies that are affected by IDC problem.AffectedCarrierFreqList-r16 OPTIONAL,affectedCarrierFreqCombList-r16Indicates a list of NR carrier frequencie combinations that are affected by IDC problems due to Inter-Modulation Distortion and harmonics from NR when configured with UL CA.AffectedCarrierFreqCombList-r16 OPTIONAL, ... } AffectedCarrierFreqList-r16 ::= SEQUENCE (SIZE (1.. maxFreqIDC-r16)) OF AffectedCarrierFreq-r16 AffectedCarrierFreq-r16 ::= SEQUENCE { carrierFreq-r16 ARFCN-ValueNR,interferenceDirection-r16Indicates the direction of IDC interference. Value nr indicates that only NR is victim of IDC interference, value other indicates that only another radio is victim of IDC interference and value both indicates that both NR and another radio are victims of IDC interference. The other radio refers to either the ISM radio or GNSS (see TR 36.816 [44]).ENUMERATED {nr, other, both, spare} } AffectedCarrierFreqCombList-r16 ::= SEQUENCE (SIZE (1..maxCombIDC-r16)) OF AffectedCarrierFreqComb-r16 AffectedCarrierFreqComb-r16 ::= SEQUENCE { affectedCarrierFreqComb-r16 SEQUENCE (SIZE (2..maxNrofServingCells)) OF ARFCN-ValueNR OPTIONAL,victimSystemType-r16Indicate the list of victim system types to which IDC interference is caused from NR when configured with UL CA. Value gps, glonass, bds, galileo and navIC indicates the type of GNSS. Value wlan indicates WLAN and value bluetooth indicates Bluetooth.VictimSystemType-r16 } VictimSystemType-r16 ::= SEQUENCE { gps-r16 ENUMERATED {true} OPTIONAL, glonass-r16 ENUMERATED {true} OPTIONAL, bds-r16 ENUMERATED {true} OPTIONAL, galileo-r16 ENUMERATED {true} OPTIONAL, navIC-r16 ENUMERATED {true} OPTIONAL, wlan-r16 ENUMERATED {true} OPTIONAL, bluetooth-r16 ENUMERATED {true} OPTIONAL, ... } DRX-Preference-r16 ::= SEQUENCE {preferredDRX-InactivityTimer-r16Indicates the UE's preferred DRX inactivity timer length for power saving. Value in ms (milliSecond). ms0 corresponds to 0, ms1 corresponds to 1 ms, ms2 corresponds to 2 ms, and so on. If the field is absent from the DRX-Preference IE, it is interpreted as the UE having no preference for the DRX inactivity timer. If secondary DRX group is configured, the preferredDRX-InactivityTimer only applies to the default DRX group.ENUMERATED { ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL,preferredDRX-LongCycle-r16Indicates the UE's preferred long DRX cycle length for power saving. Value in ms. ms10 corresponds to 10ms, ms20 corresponds to 20 ms, ms32 corresponds to 32 ms, and so on. If preferredDRX-ShortCycleis provided, the value of preferredDRX-LongCycleshall be a multiple of the preferredDRX-ShortCyclevalue. If the field is absent from the DRX-Preference IE, it is interpreted as the UE having no preference for the long DRX cycle.ENUMERATED { ms10, ms20, ms32, ms40, ms60, ms64, ms70, ms80, ms128, ms160, ms256, ms320, ms512, ms640, ms1024, ms1280, ms2048, ms2560, ms5120, ms10240, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } OPTIONAL,preferredDRX-ShortCycle-r16Indicates the UE's preferred short DRX cycle length for power saving. Value in ms. ms2 corresponds to 2ms, ms3 corresponds to 3 ms, ms4 corresponds to 4 ms, and so on. If the field is absent from the DRX-Preference IE, it is interpreted as the UE having no preference for the short DRX cycle.ENUMERATED { ms2, ms3, ms4, ms5, ms6, ms7, ms8, ms10, ms14, ms16, ms20, ms30, ms32, ms35, ms40, ms64, ms80, ms128, ms160, ms256, ms320, ms512, ms640, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } OPTIONAL,preferredDRX-ShortCycleTimer-r16Indicates the UE's preferred short DRX cycle timer for power saving. Value in multiples of preferredDRX-ShortCycle. A value of 1 corresponds to preferredDRX-ShortCycle, a value of 2 corresponds to 2 * preferredDRX-ShortCycle and so on. If the field is absent from the DRX-Preference IE, it is interpreted as the UE having no preference for the short DRX cycle timer. A preference for the short DRX cycle is indicated when a preference for the short DRX cycle timer is indicated.INTEGER (1..16) OPTIONAL } MaxBW-Preference-r16 ::= SEQUENCE {reducedMaxBW-FR1-r16Indicates the UE's preference on reduced configuration corresponding to the maximum aggregated bandwidth across all downlink carrier(s) and across all uplink carrier(s) of FR1, to address overheating or power saving. This field is allowed to be reported only when UE is configured with serving cell(s) operating on FR1. The aggregated bandwidth across all downlink carrier(s) of FR1 is the sum of bandwidth of active downlink BWP(s) across all activated downlink carrier(s) of FR1. The aggregated bandwidth across all uplink carrier(s) of FR1 is the sum of bandwidth of active uplink BWP(s) across all activated uplink carrier(s) of FR1. If the field is absent from the MaxBW-Preference IE or the OverheatingAssistance IE, it is interpreted as the UE having no preference on the maximum aggregated bandwidth of FR1. When indicated to address overheating, this maximum aggregated bandwidth includes carrier(s) of FR1 of both the NR MCG and the SCG. This maximum aggregated bandwidth only includes carriers of FR1 of the SCG in (NG)EN-DC. Value mhz0 is not used when indicated to address overheating. When indicated to address power saving, this maximum aggregated bandwidth includes carrier(s) of FR1 of the cell group that this UE assistance information is associated with. The aggregated bandwidth can only range up to the current active configuration when indicated to address power savings.ReducedMaxBW-FRx-r16 OPTIONAL,reducedMaxBW-FR2-r16Indicates the UE's preference on reduced configuration corresponding to the maximum aggregated bandwidth across all downlink carrier(s) and across all uplink carrier(s) of FR2, to address overheating or power saving. This field is allowed to be reported only when UE is configured with serving cell(s) operating on FR2.The aggregated bandwidth across all downlink carrier(s) of FR2 is the sum of bandwidth of active downlink BWP(s) across all activated downlink carrier(s) of FR2. The aggregated bandwidth across all uplink carrier(s) of FR2 is the sum of bandwidth of active uplink BWP(s) across all activated uplink carrier(s) of FR2. If the field is absent from the MaxBW-Preference IE or the OverheatingAssistance IE, it is interpreted as the UE having no preference on the maximum aggregated bandwidth of FR2. When indicated to address overheating, this maximum aggregated bandwidth includes carrier(s)of FR2 of both the NR MCG and the NR SCG. This maximum aggregated bandwidth only includes carriers of FR2 of the SCG in (NG)EN-DC. When indicated to address power saving, this maximum aggregated bandwidth includes carrier(s) of FR2 of the cell group that this UE assistance information is associated with. The aggregated bandwidth can only range up to the current active configuration when indicated to address power savings.ReducedMaxBW-FRx-r16 OPTIONAL } MaxCC-Preference-r16 ::= SEQUENCE { reducedMaxCCs-r16 ReducedMaxCCs-r16 OPTIONAL } MaxMIMO-LayerPreference-r16 ::= SEQUENCE { reducedMaxMIMO-LayersFR1-r16 SEQUENCE {reducedMIMO-LayersFR1-DL-r16Indicates the UE's preference on reduced configuration corresponding to the maximum number of downlink MIMO layers of each serving cell operating on FR1 indicated by the field, to address overheating or power saving. This field is allowed to be reported only when UE is configured with serving cells operating on FR1. The maximum number of downlink MIMO layers can only range up to the maximum number of MIMO layers configured across all activated downlink carrier(s) of FR1 in the cell group when indicated to address power savings.INTEGER (1..8),reducedMIMO-LayersFR1-UL-r16Indicates the UE's preference on reduced configuration corresponding to the maximum number of uplink MIMO layers of each serving cell operating on FR1 indicated by the field, to address overheating or power saving (see NOTE 1). This field is allowed to be reported only when UE is configured with serving cells operating on FR1. The maximum number of uplink MIMO layerscan only range up to the maximum number of MIMO layers configured across all activated uplink carrier(s) of FR1 in the cell group when indicated to address power savings.INTEGER (1..4) } OPTIONAL, reducedMaxMIMO-LayersFR2-r16 SEQUENCE {reducedMIMO-LayersFR2-DL-r16Indicates the UE's preference on reduced configuration corresponding to the maximum number of downlink MIMO layers of each serving cell operating on FR2 indicated by the field, to address overheating or power saving. This field is allowed to be reported only when UE is configured with serving cells operating on FR2. The maximum number of downlink MIMO layers can only range up to the maximum number of MIMO layers configured across all activated downlink carrier(s) of FR2 in the cell group when indicated to address power savings.INTEGER (1..8),reducedMIMO-LayersFR2-UL-r16Indicates the UE's preference on reduced configuration corresponding to the maximum number of uplink MIMO layers of each serving cell operating on FR2 indicated by the field, to address overheating or power saving (see NOTE 1). This field is allowed to be reported only when UE is configured with serving cells operating on FR2. The maximum number of uplink MIMO layers can only range up to the maximum number of MIMO layers configured across all activated uplink carrier(s) of FR2 in the cell group when indicated to address power savings.INTEGER (1..4) } OPTIONAL } MinSchedulingOffsetPreference-r16 ::= SEQUENCE {preferredK0-r16Indicates the UE's preferred value of k0 (slot offset between DCI and its scheduled PDSCH - see TS 38.214 [19], clause 5.1.2.1) for cross-slot scheduling for power saving. Value is defined for each subcarrier spacing (numerology) in units of slots. sl1 corresponds to 1 slot, sl2 corresponds to 2 slots, sl4 corresponds to 4 slots, and so on. If a value for a subcarrier spacing is absent, it is interpreted as the UE having no preference on k0 for cross-slot scheduling for that subcarrier spacing. If the field is absent from the MinSchedulingOffsetPreference IE, it is interpreted as the UE having no preference on k0 for cross-slot scheduling.SEQUENCE { preferredK0-SCS-15kHz-r16 ENUMERATED {sl1, sl2, sl4, sl6} OPTIONAL, preferredK0-SCS-30kHz-r16 ENUMERATED {sl1, sl2, sl4, sl6} OPTIONAL, preferredK0-SCS-60kHz-r16 ENUMERATED {sl2, sl4, sl8, sl12} OPTIONAL, preferredK0-SCS-120kHz-r16 ENUMERATED {sl2, sl4, sl8, sl12} OPTIONAL } OPTIONAL,preferredK2-r16Indicates the UE's preferred value of k2 (slot offset between DCI and its scheduled PUSCH - see TS 38.214 [19], clause 6.1.2.1) for cross-slot scheduling for power saving. Value is defined for each subcarrier spacing (numerology) in units of slots. sl1 corresponds to 1 slot, sl2 corresponds to 2 slots, sl4 corresponds to 4 slots, and so on. If a value for a subcarrier spacing is absent, it is interpreted as the UE having no preference on k2 for cross-slot scheduling for that subcarrier spacing. If the field is absent from the MinSchedulingOffsetPreference IE, it is interpreted as the UE having no preference on k2 for cross-slot scheduling.SEQUENCE { preferredK2-SCS-15kHz-r16 ENUMERATED {sl1, sl2, sl4, sl6} OPTIONAL, preferredK2-SCS-30kHz-r16 ENUMERATED {sl1, sl2, sl4, sl6} OPTIONAL, preferredK2-SCS-60kHz-r16 ENUMERATED {sl2, sl4, sl8, sl12} OPTIONAL, preferredK2-SCS-120kHz-r16 ENUMERATED {sl2, sl4, sl8, sl12} OPTIONAL } OPTIONAL } ReleasePreference-r16 ::= SEQUENCE {preferredRRC-State-r16Indicates the UE's preferred RRC state. The value idle is indicated if the UE prefers to be released from RRC_CONNECTED and transition to RRC_IDLE. The value inactive is indicated if the UE prefers to be released from RRC_CONNECTED and transition to RRC_INACTIVE. The value connected is indicated if the UE prefers to revert an earlier indication to leave RRC_CONNECTED state. The value outOfConnected is indicated if the UE prefers to be released from RRC_CONNECTED and has no preferred RRC state to transition to.The value connected can only be indicated if the UE is configured with connectedReporting.ENUMERATED {idle, inactive, connected, outOfConnected} } ReducedMaxBW-FRx-r16 ::= SEQUENCE { reducedBW-DL-r16 ReducedAggregatedBandwidth, reducedBW-UL-r16 ReducedAggregatedBandwidth } ReducedMaxCCs-r16 ::= SEQUENCE {reducedCCsDL-r16Indicates the UE's preference on reduced configuration corresponding to the maximum number of downlink SCells indicated by the field, to address overheating or power saving. When indicated to address overheating, this maximum number includes both SCells of the NR MCG and PSCell/SCells of the SCG. This maximum number only includes PSCell/SCells of the SCG in (NG)EN-DC. When indicated to address power saving, this maximum number includes PSCell/SCells of the cell group that this UE assistance information is associated with. The maximum number of downlink SCells can only range up to the current active configuration when indicated to address power savings.INTEGER (0..31),reducedCCsUL-r16Indicates the UE's preference on reduced configuration corresponding to the maximum number of uplink SCells indicated by the field, to address overheating or power saving. When indicated to address overheating, this maximum number includes both SCells of the NR MCG and PSCell/SCells of the SCG. This maximum number only includes PSCell/SCells of the SCG in (NG)EN-DC. When indicated to address power saving, this maximum number includes PSCell/SCells of the cell group that this UE assistance information is associated with. The maximum number of uplink SCells can only range up to the current active configuration when indicated to address power savings.INTEGER (0..31) } SL-UE-AssistanceInformationNR-r16 ::= SEQUENCE (SIZE (1..maxNrofTrafficPattern-r16)) OF SL-TrafficPatternInfo-r16 SL-TrafficPatternInfo-r16::= SEQUENCE {trafficPeriodicity-r16This field indicates the estimated data arrival periodicity in a sidelink logical channel. Value ms20 corresponds to 20 ms, ms50 corresponds to 50 ms and so on.ENUMERATED {ms20, ms50, ms100, ms200, ms300, ms400, ms500, ms600, ms700, ms800, ms900, ms1000},timingOffset-r16This field indicates the estimated timing for a packet arrival in a sidelink logical channel. Specifically, the value indicates the timing offset with respect to subframe#0 of SFN#0 in milliseconds.INTEGER (0..10239),messageSize-r16Indicates the maximum TB size based on the observed traffic pattern. The value refers to the index of TS 38.321 [3], table 6.1.3.1-2.BIT STRING (SIZE (8)),sl-QoS-FlowIdentity-r16This identity uniquely identifies one sidelink QoS flow between the UE and the network in the scope of UE, which is unique for different destination and cast type.SL-QoS-FlowIdentity-r16 } -- TAG-UEASSISTANCEINFORMATION-STOP -- ASN1STOP
UEAssistanceInformation field descriptions |
---|
affectedCarrierFreqList Indicates a list of NR carrier frequencies that are affected by IDC problem. |
affectedCarrierFreqCombList Indicates a list of NR carrier frequencie combinations that are affected by IDC problems due to Inter-Modulation Distortion and harmonics from NR when configured with UL CA. |
delayBudgetReport Indicates the UE-preferred adjustment to connected mode DRX. |
interferenceDirection Indicates the direction of IDC interference. Value nr indicates that only NR is victim of IDC interference, value other indicates that only another radio is victim of IDC interference and value both indicates that both NR and another radio are victims of IDC interference. The other radio refers to either the ISM radio or GNSS (see TR 36.816 [44]). |
minSchedulingOffsetPreference Indicates the UE's preferences on minimumSchedulingOffset of cross-slot scheduling for power saving. |
preferredDRX-InactivityTimer Indicates the UE's preferred DRX inactivity timer length for power saving. Value in ms (milliSecond). ms0 corresponds to 0, ms1 corresponds to 1 ms, ms2 corresponds to 2 ms, and so on. If the field is absent from the DRX-Preference IE, it is interpreted as the UE having no preference for the DRX inactivity timer. If secondary DRX group is configured, the preferredDRX-InactivityTimer only applies to the default DRX group. |
preferredDRX-LongCycle Indicates the UE's preferred long DRX cycle length for power saving. Value in ms. ms10 corresponds to 10ms, ms20 corresponds to 20 ms, ms32 corresponds to 32 ms, and so on. If preferredDRX-ShortCycleis provided, the value of preferredDRX-LongCycleshall be a multiple of the preferredDRX-ShortCyclevalue. If the field is absent from the DRX-Preference IE, it is interpreted as the UE having no preference for the long DRX cycle. |
preferredDRX-ShortCycle Indicates the UE's preferred short DRX cycle length for power saving. Value in ms. ms2 corresponds to 2ms, ms3 corresponds to 3 ms, ms4 corresponds to 4 ms, and so on. If the field is absent from the DRX-Preference IE, it is interpreted as the UE having no preference for the short DRX cycle. |
preferredDRX-ShortCycleTimer Indicates the UE's preferred short DRX cycle timer for power saving. Value in multiples of preferredDRX-ShortCycle. A value of 1 corresponds to preferredDRX-ShortCycle, a value of 2 corresponds to 2 * preferredDRX-ShortCycle and so on. If the field is absent from the DRX-Preference IE, it is interpreted as the UE having no preference for the short DRX cycle timer. A preference for the short DRX cycle is indicated when a preference for the short DRX cycle timer is indicated. |
preferredK0 Indicates the UE's preferred value of k0 (slot offset between DCI and its scheduled PDSCH - see TS 38.214 [19], clause 5.1.2.1) for cross-slot scheduling for power saving. Value is defined for each subcarrier spacing (numerology) in units of slots. sl1 corresponds to 1 slot, sl2 corresponds to 2 slots, sl4 corresponds to 4 slots, and so on. If a value for a subcarrier spacing is absent, it is interpreted as the UE having no preference on k0 for cross-slot scheduling for that subcarrier spacing. If the field is absent from the MinSchedulingOffsetPreference IE, it is interpreted as the UE having no preference on k0 for cross-slot scheduling. |
preferredK2 Indicates the UE's preferred value of k2 (slot offset between DCI and its scheduled PUSCH - see TS 38.214 [19], clause 6.1.2.1) for cross-slot scheduling for power saving. Value is defined for each subcarrier spacing (numerology) in units of slots. sl1 corresponds to 1 slot, sl2 corresponds to 2 slots, sl4 corresponds to 4 slots, and so on. If a value for a subcarrier spacing is absent, it is interpreted as the UE having no preference on k2 for cross-slot scheduling for that subcarrier spacing. If the field is absent from the MinSchedulingOffsetPreference IE, it is interpreted as the UE having no preference on k2 for cross-slot scheduling. |
preferredRRC-State Indicates the UE's preferred RRC state. The value idle is indicated if the UE prefers to be released from RRC_CONNECTED and transition to RRC_IDLE. The value inactive is indicated if the UE prefers to be released from RRC_CONNECTED and transition to RRC_INACTIVE. The value connected is indicated if the UE prefers to revert an earlier indication to leave RRC_CONNECTED state. The value outOfConnected is indicated if the UE prefers to be released from RRC_CONNECTED and has no preferred RRC state to transition to.The value connected can only be indicated if the UE is configured with connectedReporting. |
reducedMaxBW-FR1 Indicates the UE's preference on reduced configuration corresponding to the maximum aggregated bandwidth across all downlink carrier(s) and across all uplink carrier(s) of FR1, to address overheating or power saving. This field is allowed to be reported only when UE is configured with serving cell(s) operating on FR1. The aggregated bandwidth across all downlink carrier(s) of FR1 is the sum of bandwidth of active downlink BWP(s) across all activated downlink carrier(s) of FR1. The aggregated bandwidth across all uplink carrier(s) of FR1 is the sum of bandwidth of active uplink BWP(s) across all activated uplink carrier(s) of FR1. If the field is absent from the MaxBW-Preference IE or the OverheatingAssistance IE, it is interpreted as the UE having no preference on the maximum aggregated bandwidth of FR1. When indicated to address overheating, this maximum aggregated bandwidth includes carrier(s) of FR1 of both the NR MCG and the SCG. This maximum aggregated bandwidth only includes carriers of FR1 of the SCG in (NG)EN-DC. Value mhz0 is not used when indicated to address overheating. When indicated to address power saving, this maximum aggregated bandwidth includes carrier(s) of FR1 of the cell group that this UE assistance information is associated with. The aggregated bandwidth can only range up to the current active configuration when indicated to address power savings. |
reducedMaxBW-FR2 Indicates the UE's preference on reduced configuration corresponding to the maximum aggregated bandwidth across all downlink carrier(s) and across all uplink carrier(s) of FR2, to address overheating or power saving. This field is allowed to be reported only when UE is configured with serving cell(s) operating on FR2.The aggregated bandwidth across all downlink carrier(s) of FR2 is the sum of bandwidth of active downlink BWP(s) across all activated downlink carrier(s) of FR2. The aggregated bandwidth across all uplink carrier(s) of FR2 is the sum of bandwidth of active uplink BWP(s) across all activated uplink carrier(s) of FR2. If the field is absent from the MaxBW-Preference IE or the OverheatingAssistance IE, it is interpreted as the UE having no preference on the maximum aggregated bandwidth of FR2. When indicated to address overheating, this maximum aggregated bandwidth includes carrier(s)of FR2 of both the NR MCG and the NR SCG. This maximum aggregated bandwidth only includes carriers of FR2 of the SCG in (NG)EN-DC. When indicated to address power saving, this maximum aggregated bandwidth includes carrier(s) of FR2 of the cell group that this UE assistance information is associated with. The aggregated bandwidth can only range up to the current active configuration when indicated to address power savings. |
reducedCCsDL Indicates the UE's preference on reduced configuration corresponding to the maximum number of downlink SCells indicated by the field, to address overheating or power saving. When indicated to address overheating, this maximum number includes both SCells of the NR MCG and PSCell/SCells of the SCG. This maximum number only includes PSCell/SCells of the SCG in (NG)EN-DC. When indicated to address power saving, this maximum number includes PSCell/SCells of the cell group that this UE assistance information is associated with. The maximum number of downlink SCells can only range up to the current active configuration when indicated to address power savings. |
reducedCCsUL Indicates the UE's preference on reduced configuration corresponding to the maximum number of uplink SCells indicated by the field, to address overheating or power saving. When indicated to address overheating, this maximum number includes both SCells of the NR MCG and PSCell/SCells of the SCG. This maximum number only includes PSCell/SCells of the SCG in (NG)EN-DC. When indicated to address power saving, this maximum number includes PSCell/SCells of the cell group that this UE assistance information is associated with. The maximum number of uplink SCells can only range up to the current active configuration when indicated to address power savings. |
reducedMIMO-LayersFR1-DL Indicates the UE's preference on reduced configuration corresponding to the maximum number of downlink MIMO layers of each serving cell operating on FR1 indicated by the field, to address overheating or power saving. This field is allowed to be reported only when UE is configured with serving cells operating on FR1. The maximum number of downlink MIMO layers can only range up to the maximum number of MIMO layers configured across all activated downlink carrier(s) of FR1 in the cell group when indicated to address power savings. |
reducedMIMO-LayersFR1-UL Indicates the UE's preference on reduced configuration corresponding to the maximum number of uplink MIMO layers of each serving cell operating on FR1 indicated by the field, to address overheating or power saving (see NOTE 1). This field is allowed to be reported only when UE is configured with serving cells operating on FR1. The maximum number of uplink MIMO layerscan only range up to the maximum number of MIMO layers configured across all activated uplink carrier(s) of FR1 in the cell group when indicated to address power savings. |
reducedMIMO-LayersFR2-DL Indicates the UE's preference on reduced configuration corresponding to the maximum number of downlink MIMO layers of each serving cell operating on FR2 indicated by the field, to address overheating or power saving. This field is allowed to be reported only when UE is configured with serving cells operating on FR2. The maximum number of downlink MIMO layers can only range up to the maximum number of MIMO layers configured across all activated downlink carrier(s) of FR2 in the cell group when indicated to address power savings. |
reducedMIMO-LayersFR2-UL Indicates the UE's preference on reduced configuration corresponding to the maximum number of uplink MIMO layers of each serving cell operating on FR2 indicated by the field, to address overheating or power saving (see NOTE 1). This field is allowed to be reported only when UE is configured with serving cells operating on FR2. The maximum number of uplink MIMO layers can only range up to the maximum number of MIMO layers configured across all activated uplink carrier(s) of FR2 in the cell group when indicated to address power savings. |
referenceTimeInfoPreference Indicates whether the UE prefers being provisioned with the timing information specified in the IE ReferenceTimeInfo. |
sl-QoS-FlowIdentity This identity uniquely identifies one sidelink QoS flow between the UE and the network in the scope of UE, which is unique for different destination and cast type. |
sl-UE-AssistanceInformationNR Indicates the traffic characteristic of sidelink logical channel(s), specified in the IE SL-TrafficPatternInfo, that are setup for NR sidelink communication. |
type1 Indicates the preferred amount of increment/decrement to the long DRX cycle length with respect to the current configuration. Value in number of milliseconds. Value ms40 corresponds to 40 milliseconds, msMinus40 corresponds to -40 milliseconds and so on. |
victimSystemType Indicate the list of victim system types to which IDC interference is caused from NR when configured with UL CA. Value gps, glonass, bds, galileo and navIC indicates the type of GNSS. Value wlan indicates WLAN and value bluetooth indicates Bluetooth. |
SL-TrafficPatternInfo field descriptions |
---|
messageSize Indicates the maximum TB size based on the observed traffic pattern. The value refers to the index of TS 38.321 [3], table 6.1.3.1-2. |
timingOffset This field indicates the estimated timing for a packet arrival in a sidelink logical channel. Specifically, the value indicates the timing offset with respect to subframe#0 of SFN#0 in milliseconds. |
trafficPeriodicity This field indicates the estimated data arrival periodicity in a sidelink logical channel. Value ms20 corresponds to 20 ms, ms50 corresponds to 50 ms and so on. |
The UECapabilityEnquiry message is used to request UE radio access capabilities for NR as well as for other RATs.
-- ASN1START -- TAG-UECAPABILITYENQUIRY-START UECapabilityEnquiry ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { ueCapabilityEnquiry UECapabilityEnquiry-IEs, criticalExtensionsFuture SEQUENCE {} } } UECapabilityEnquiry-IEs ::= SEQUENCE { ue-CapabilityRAT-RequestList UE-CapabilityRAT-RequestList, lateNonCriticalExtension OCTET STRING OPTIONAL, ue-CapabilityEnquiryExt OCTET STRING (CONTAINING UECapabilityEnquiry-v1560-IEs) OPTIONAL -- Need N } UECapabilityEnquiry-v1560-IEs ::= SEQUENCE { capabilityRequestFilterCommon UE-CapabilityRequestFilterCommon OPTIONAL, -- Need N nonCriticalExtension UECapabilityEnquiry-v1610-IEs OPTIONAL } UECapabilityEnquiry-v1610-IEs ::= SEQUENCE { rrc-SegAllowed-r16 ENUMERATED {enabled} OPTIONAL, -- Need N nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-UECAPABILITYENQUIRY-STOP -- ASN1STOP
The IE UECapabilityInformation message is used to transfer UE radio access capabilities requested by the network.
-- ASN1START -- TAG-UECAPABILITYINFORMATION-START UECapabilityInformation ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { ueCapabilityInformation UECapabilityInformation-IEs, criticalExtensionsFuture SEQUENCE {} } } UECapabilityInformation-IEs ::= SEQUENCE { ue-CapabilityRAT-ContainerList UE-CapabilityRAT-ContainerList OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } -- TAG-UECAPABILITYINFORMATION-STOP -- ASN1STOP
The UEInformationRequest message is used by the network to retrieve information from the UE.
-- ASN1START -- TAG-UEINFORMATIONREQUEST-START UEInformationRequest-r16 ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { ueInformationRequest-r16 UEInformationRequest-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } UEInformationRequest-r16-IEs ::= SEQUENCE {idleModeMeasurementReq-r16This field indicates that the UE shall report the idle/inactive measurement information, if available, to the network in the UEInformationResponse message.ENUMERATED{true} OPTIONAL, -- Need NlogMeasReportReq-r16This field is used to indicate whether the UE shall report information about logged measurements.ENUMERATED {true} OPTIONAL, -- Need NconnEstFailReportReq-r16This field is used to indicate whether the UE shall report information about the connection failure.ENUMERATED {true} OPTIONAL, -- Need Nra-ReportReq-r16This field is used to indicate whether the UE shall report information about the random access procedure.ENUMERATED {true} OPTIONAL, -- Need Nrlf-ReportReq-r16This field is used to indicate whether the UE shall report information about the radio link failure.ENUMERATED {true} OPTIONAL, -- Need NmobilityHistoryReportReq-r16This field is used to indicate whether the UE shall report information about mobility history information.ENUMERATED {true} OPTIONAL, -- Need N lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-UEINFORMATIONREQUEST-STOP -- ASN1STOP
UEInformationRequest-IEs field descriptions |
---|
connEstFailReportReq This field is used to indicate whether the UE shall report information about the connection failure. |
idleModeMeasurementReq This field indicates that the UE shall report the idle/inactive measurement information, if available, to the network in the UEInformationResponse message. |
logMeasReportReq This field is used to indicate whether the UE shall report information about logged measurements. |
mobilityHistoryReportReq This field is used to indicate whether the UE shall report information about mobility history information. |
ra-ReportReq This field is used to indicate whether the UE shall report information about the random access procedure. |
rlf-ReportReq This field is used to indicate whether the UE shall report information about the radio link failure. |
The UEInformationResponse message is used by the UE to transfer information requested by the network.
-- ASN1START -- TAG-UEINFORMATIONRESPONSE-START UEInformationResponse-r16 ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { ueInformationResponse-r16 UEInformationResponse-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } UEInformationResponse-r16-IEs ::= SEQUENCE {measResultIdleEUTRA-r16EUTRA measurement results performed during RRC_INACTIVE or RRC_IDLE.MeasResultIdleEUTRA-r16 OPTIONAL,measResultIdleNR-r16NR measurement results performed during RRC_INACTIVE or RRC_IDLE.MeasResultIdleNR-r16 OPTIONAL,logMeasReport-r16This field is used to provide the measurement results stored by the UE associated to logged MDT.LogMeasReport-r16 OPTIONAL, connEstFailReport-r16 ConnEstFailReport-r16 OPTIONAL,ra-ReportList-r16This field is used to provide the list of RA reports that is stored by the UE for the past upto maxRAReport-r16 number of successful random access procedures.RA-ReportList-r16 OPTIONAL,rlf-Report-r16This field is used to indicate the RLF report related contents.RLF-Report-r16 OPTIONAL, mobilityHistoryReport-r16 MobilityHistoryReport-r16 OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } LogMeasReport-r16 ::= SEQUENCE {absoluteTimeStamp-r16Indicates the absolute time when the logged measurement configuration logging is provided, as indicated by NR within absoluteTimeInfo.AbsoluteTimeInfo-r16, traceReference-r16 TraceReference-r16,traceRecordingSessionRef-r16Parameter Trace Recording Session Reference: See TS 32.422 [52].OCTET STRING (SIZE (2)),tce-Id-r16Parameter Trace Collection Entity Id: See TS 32.422 [52].OCTET STRING (SIZE (1)), logMeasInfoList-r16 LogMeasInfoList-r16, logMeasAvailable-r16 ENUMERATED {true} OPTIONAL, logMeasAvailableBT-r16 ENUMERATED {true} OPTIONAL, logMeasAvailableWLAN-r16 ENUMERATED {true} OPTIONAL, ... } LogMeasInfoList-r16 ::= SEQUENCE (SIZE (1..maxLogMeasReport-r16)) OF LogMeasInfo-r16 LogMeasInfo-r16 ::= SEQUENCE { locationInfo-r16 LocationInfo-r16 OPTIONAL,relativeTimeStamp-r16Indicates the time of logging measurement results, measured relative to the absoluteTimeStamp. Value in seconds.INTEGER (0..7200), servCellIdentity-r16 CGI-Info-Logging-r16 OPTIONAL,measResultServingCell-r16This field refers to the log measurement results taken in the Serving cell.MeasResultServingCell-r16 OPTIONAL,measResultNeighCells-r16This field refers to the neighbour cell measurements when connection establishment failure or connection resume failure happened.SEQUENCE { measResultNeighCellListNR MeasResultListLogging2NR-r16 OPTIONAL, measResultNeighCellListEUTRA MeasResultList2EUTRA-r16 OPTIONAL },anyCellSelectionDetected-r16This field is used to indicate the detection of any cell selection state, as defined in TS 38.304 [20]. The UE sets this field when performing the logging of measurement results in RRC_IDLE or RRC_INACTIVE and there is no suitable cell or no acceptable cell.ENUMERATED {true} OPTIONAL, ... } ConnEstFailReport-r16 ::= SEQUENCE {measResultFailedCell-r16This field refers to the last measurement results taken in the cell, where connection establishment failure or connection resume failure happened.MeasResultFailedCell-r16, locationInfo-r16 LocationInfo-r16 OPTIONAL,measResultNeighCells-r16This field refers to the neighbour cell measurements when connection establishment failure or connection resume failure happened.SEQUENCE { measResultNeighCellListNR MeasResultList2NR-r16 OPTIONAL, measResultNeighCellListEUTRA MeasResultList2EUTRA-r16 OPTIONAL },numberOfConnFail-r16This field is used to indicate the latest number of consecutive failed RRCSetup or RRCResume procedures in the same cell independent of RRC state transition.INTEGER (1..8), perRAInfoList-r16 PerRAInfoList-r16,timeSinceFailure-r16This field is used to indicate the time that elapsed since the connection (radio link or handover) failure.Value in seconds. The maximum value 172800 means 172800s or longer.TimeSinceFailure-r16, ... } MeasResultServingCell-r16 ::= SEQUENCE { resultsSSB-Cell MeasQuantityResults, resultsSSB SEQUENCE{ best-ssb-Index SSB-Index, best-ssb-Results MeasQuantityResults,numberOfGoodSSBIndicates the number of good beams (beams that are above absThreshSS-BlocksConsolidation, if configured by the network) associated to the cells within the R value range (which is configured by network for cell reselection) of the highest ranked cell as part of the beam level measurements. If the UE has no SSB of a neighbour cell whose measurement quantity is above the absThreshSS-BlocksConsolidation or if the network has not configured the absThreshSS-BlocksConsolidation, then the UE does not include numberOfGoodSSB for the corresponding neighbour cell. If the UE has no SSB of the serving cell whose measurement quantity is above the absThreshSS-BlocksConsolidation or if the network has not configured the absThreshSS-BlocksConsolidation, then the UE shall set the numberOfGoodSSB for the serving cell to one.INTEGER (1..maxNrofSSBs-r16) } OPTIONAL } MeasResultFailedCell-r16 ::= SEQUENCE { cgi-Info CGI-Info-Logging-r16, measResult-r16 SEQUENCE { cellResults-r16 SEQUENCE{ resultsSSB-Cell-r16 MeasQuantityResults }, rsIndexResults-r16 SEQUENCE{ resultsSSB-Indexes-r16 ResultsPerSSB-IndexList } } } RA-ReportList-r16 ::= SEQUENCE (SIZE (1..maxRAReport-r16)) OF RA-Report-r16 RA-Report-r16 ::= SEQUENCE { cellId-r16 CHOICE { cellGlobalId-r16 CGI-Info-Logging-r16, pci-arfcn-r16 PCI-ARFCN-NR-r16 },ra-InformationCommon-r16This field is optionally included when connectionFailureType is set to 'hof' or when connectionFailureType is set to 'rlf' and the rlf-Cause equals to 'randomAccessProblem' or 'beamRecoveryFailure'; otherwise this field is absent.RA-InformationCommon-r16 OPTIONAL,raPurpose-r16This field is used to indicate the RA scenario for which the RA report entry is triggered. The RA accesses associated to Initial access from RRC_IDLE, RRC re-establishment procedure, transition from RRC-INACTIVE and the MSG3 based SI request are indicated using the indicator 'accessRelated'. The indicator beamFailureRecovery is used in case of successful beam failure recovery related RA procedure in the SpCell [3]. The indicator reconfigurationWithSync is used if the UE executes a reconfiguration with sync. The indicator ulUnSynchronized is used if the random access procedure is initiated in a SpCell by DL or UL data arrival during RRC_CONNECTED when the timeAlignmentTimer is not running in the PTAG or if the RA procedure is initiatedin a serving cell by a PDCCH order [3]. The indicator schedulingRequestFailure is used in case of SR failures [3]. The indicator noPUCCHResourceAvailable is used when the UE has no valid SR PUCCH resources configured [3]. The indicator requestForOtherSI is used for MSG1 based on demand SI request.ENUMERATED {accessRelated, beamFailureRecovery, reconfigurationWithSync, ulUnSynchronized, schedulingRequestFailure, noPUCCHResourceAvailable, requestForOtherSI, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1}, ... } RA-InformationCommon-r16 ::= SEQUENCE {absoluteFrequencyPointA-r16This field indicates the absolute frequency position of the reference resource block (Common RB 0).ARFCN-ValueNR,locationAndBandwidth-r16Frequency domain location and bandwidth of the bandwidth part associated to the random-access resources used by the UE.INTEGER (0..37949),subcarrierSpacing-r16Subcarrier spacing used in the BWP associated to the random-access resources used by the UE.SubcarrierSpacing, msg1-FrequencyStart-r16 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, msg1-FrequencyStartCFRA-r16 INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, msg1-SubcarrierSpacing-r16 SubcarrierSpacing OPTIONAL, msg1-SubcarrierSpacingCFRA-r16 SubcarrierSpacing OPTIONAL, msg1-FDM-r16 ENUMERATED {one, two, four, eight} OPTIONAL, msg1-FDMCFRA-r16 ENUMERATED {one, two, four, eight} OPTIONAL, perRAInfoList-r16 PerRAInfoList-r16, ..., [[ perRAInfoList-v1660 PerRAInfoList-v1660 OPTIONAL ]], [[msg1-SCS-From-prach-ConfigurationIndex-r16This field is set by the UE with the corresponding SCS for CBRA as derived from the prach-ConfigurationIndex in RACH-ConfigGenericwhen the msg1-SubcarrierSpacing is absent; otherwise, this field is absent.ENUMERATED {kHz1dot25, kHz5, spare2, spare1} OPTIONAL ]], [[msg1-SCS-From-prach-ConfigurationIndexCFRA-r16This field is set by the UE with the corresponding SCS for CFRA as derived from the prach-ConfigurationIndex in RACH-ConfigGenericwhen the msg1-SubcarrierSpacing is absent; otherwise, this field is absent.ENUMERATED {kHz1dot25, kHz5, spare2, spare1} OPTIONAL ]] } PerRAInfoList-r16 ::= SEQUENCE (SIZE (1..200)) OF PerRAInfo-r16 PerRAInfoList-v1660 ::= SEQUENCE (SIZE (1..200)) OF PerRACSI-RSInfo-v1660 PerRAInfo-r16 ::= CHOICE {perRASSBInfoList-r16This field provides detailed information about the successive random access attempts associated to the same SS/PBCH block.PerRASSBInfo-r16,perRACSI-RSInfoList-r16This field provides detailed information about the successive random access attempts associated to the same CSI-RS.PerRACSI-RSInfo-r16 } PerRASSBInfo-r16 ::= SEQUENCE {ssb-Index-r16This field is used to indicate the SS/PBCH index of the SS/PBCH block corresponding to the random access attempt.SSB-Index,numberOfPreamblesSentOnSSB-r16This field is used to indicate the total number of successive RA preambles that were transmitted on the corresponding SS/PBCH block.INTEGER (1..200),perRAAttemptInfoList-r16This field provides detailed information about a random access attempt.PerRAAttemptInfoList-r16 } PerRACSI-RSInfo-r16 ::= SEQUENCE { csi-RS-Index-r16 CSI-RS-Index,numberOfPreamblesSentOnCSI-RS-r16This field is used to indicate the total number of successive RA preambles that were transmitted on the corresponding CSI-RS.INTEGER (1..200) } PerRACSI-RSInfo-v1660 ::= SEQUENCE { csi-RS-Index-v1660 INTEGER (1..96) OPTIONAL } PerRAAttemptInfoList-r16 ::= SEQUENCE (SIZE (1..200)) OF PerRAAttemptInfo-r16 PerRAAttemptInfo-r16 ::= SEQUENCE {contentionDetected-r16This field is used to indicate that contention was detected for the transmitted preamble in the given random access attempt or not. This field is not included when the UE performs random access attempt is using contention free random-access resources or when the raPurpose is set to requestForOtherSI.BOOLEAN OPTIONAL,dlRSRPAboveThreshold-r16This field is used to indicate whether the DL beam (SSB) quality associated to the random access attempt was above or below the threshold rsrp-ThresholdSSBin beamFailureRecoveryConfig in UL BWP configuration of UL BWP selected for random access procedure initiated for beam failure recovery; Otherwise, rsrp-ThresholdSSB in rach-ConfigCommon in UL BWP configuration of UL BWP selected for random access procedure.BOOLEAN OPTIONAL, ... } RLF-Report-r16 ::= CHOICE { nr-RLF-Report-r16 SEQUENCE {measResultLastServCell-r16This field refers to the log measurement results taken in the PCell upon detecting radio link failure or the source PCell upon handover failure.MeasResultRLFNR-r16,measResultNeighCells-r16This field refers to the neighbour cell measurements when connection establishment failure or connection resume failure happened.SEQUENCE {measResultListNR-r16This field refers to the last measurement results taken in the neighboring NR Cells, when the radio link failure or handover failure happened.MeasResultList2NR-r16 OPTIONAL,measResultListEUTRA-r16This field refers to the last measurement results taken in the neighboring EUTRA Cells, when the radio link failure or handover failure happened.MeasResultList2EUTRA-r16 OPTIONAL } OPTIONAL,c-RNTI-r16This field indicates the C-RNTI used in the PCell upon detecting radio link failure or the C-RNTI used in the source PCell upon handover failure.RNTI-Value,previousPCellId-r16This field is used to indicate the source PCell of the last handover (source PCell when the last RRCReconfiguration message including reconfigurationWithSync was received). For intra-NR handover nrPreviousCell is included and for the handover from EUTRA to NR eutraPreviousCell is included.CHOICE { nrPreviousCell-r16 CGI-Info-Logging-r16, eutraPreviousCell-r16 CGI-InfoEUTRALogging } OPTIONAL,failedPCellId-r16This field is used to indicate the PCell in which RLF is detected or the target PCell of the failed handover. For intra-NR handover nrFailedPCellId is included and for the handover from NR to EUTRA eutraFailedPCellId is included. The UE sets the ARFCN according to the frequency band used for transmission/ reception when the failure occurred.CHOICE { nrFailedPCellId-r16 CHOICE { cellGlobalId-r16 CGI-Info-Logging-r16, pci-arfcn-r16 PCI-ARFCN-NR-r16 }, eutraFailedPCellId-r16 CHOICE { cellGlobalId-r16 CGI-InfoEUTRALogging, pci-arfcn-r16 PCI-ARFCN-EUTRA-r16 } },reconnectCellId-r16This field is used to indicate the cell in which the UE comes back to connected after connection failure and after failing to perform reestablishment. If the UE comes back to RRC CONNECTED in an NR cell then nrReconnectCellID is included and if the UE comes back to RRC CONNECTED in an LTE cell then eutraReconnectCellID is includedCHOICE { nrReconnectCellId-r16 CGI-Info-Logging-r16, eutraReconnectCellId-r16 CGI-InfoEUTRALogging } OPTIONAL,timeUntilReconnection-r16This field is used to indicate the time that elapsed between the connection (radio link or handover) failure and the next time the UE comes to RRC CONNECTED in an NR or EUTRA cell, after failing to perform reestablishment.Value in seconds. The maximum value 172800 means 172800s or longer.TimeUntilReconnection-r16 OPTIONAL,reestablishmentCellId-r16This field is used to indicate the cell in which the re-establishment attempt was made after connection failure.CGI-Info-Logging-r16 OPTIONAL,timeConnFailure-r16This field is used to indicate the time elapsed since the last HO initialization until connection failure. Actual value = field value * 100ms. The maximum value 1023 means 102.3s or longer.INTEGER (0..1023) OPTIONAL,timeSinceFailure-r16This field is used to indicate the time that elapsed since the connection (radio link or handover) failure.Value in seconds. The maximum value 172800 means 172800s or longer.TimeSinceFailure-r16,connectionFailureType-r16This field is used to indicate whether the connection failure is due to radio link failure or handover failure.ENUMERATED {rlf, hof},rlf-Cause-r16This field is used to indicate the cause of the last radio link failure that was detected. In case of handover failure information reporting (i.e., the connectionFailureType is set to 'hof'), the UE is allowed to set this field to any value.ENUMERATED {t310-Expiry, randomAccessProblem, rlc-MaxNumRetx, beamFailureRecoveryFailure, lbtFailure-r16, bh-rlfRecoveryFailure, spare2, spare1}, locationInfo-r16 LocationInfo-r16 OPTIONAL,noSuitableCellFound-r16This field is set by the UE when the T311 expires.ENUMERATED {true} OPTIONAL,ra-InformationCommon-r16This field is optionally included when connectionFailureType is set to 'hof' or when connectionFailureType is set to 'rlf' and the rlf-Cause equals to 'randomAccessProblem' or 'beamRecoveryFailure'; otherwise this field is absent.RA-InformationCommon-r16 OPTIONAL, ..., [[ csi-rsRLMConfigBitmap-v1650 BIT STRING (SIZE (96)) OPTIONAL ]] }, eutra-RLF-Report-r16 SEQUENCE {failedPCellId-EUTRAThis field is used to indicate the PCell in which RLF is detected or the source PCell of the failed handover in an E-UTRA RLF report.CGI-InfoEUTRALogging,measResult-RLF-Report-EUTRA-r16Includes the E-UTRA RLF-Report-r9 IE as specified in TS 36.331 [10].OCTET STRING, ..., [[measResult-RLF-Report-EUTRA-v1690Includes the E-UTRA RLF-Report-v9e0 IE as specified in TS 36.331 [10].OCTET STRING OPTIONAL ]] } } MeasResultList2NR-r16 ::= SEQUENCE(SIZE(1..maxFreq)) OF MeasResult2NR-r16 MeasResultList2EUTRA-r16 ::= SEQUENCE(SIZE(1..maxFreq)) OF MeasResult2EUTRA-r16 MeasResult2NR-r16 ::= SEQUENCE { ssbFrequency-r16 ARFCN-ValueNR OPTIONAL, refFreqCSI-RS-r16 ARFCN-ValueNR OPTIONAL, measResultList-r16 MeasResultListNR } MeasResultListLogging2NR-r16 ::= SEQUENCE(SIZE(1..maxFreq)) OF MeasResultLogging2NR-r16 MeasResultLogging2NR-r16 ::= SEQUENCE { carrierFreq-r16 ARFCN-ValueNR, measResultListLoggingNR-r16 MeasResultListLoggingNR-r16 } MeasResultListLoggingNR-r16 ::= SEQUENCE (SIZE (1..maxCellReport)) OF MeasResultLoggingNR-r16 MeasResultLoggingNR-r16 ::= SEQUENCE { physCellId-r16 PhysCellId, resultsSSB-Cell-r16 MeasQuantityResults,numberOfGoodSSB-r16Indicates the number of good beams (beams that are above absThreshSS-BlocksConsolidation, if configured by the network) associated to the cells within the R value range (which is configured by network for cell reselection) of the highest ranked cell as part of the beam level measurements. If the UE has no SSB of a neighbour cell whose measurement quantity is above the absThreshSS-BlocksConsolidation or if the network has not configured the absThreshSS-BlocksConsolidation, then the UE does not include numberOfGoodSSB for the corresponding neighbour cell. If the UE has no SSB of the serving cell whose measurement quantity is above the absThreshSS-BlocksConsolidation or if the network has not configured the absThreshSS-BlocksConsolidation, then the UE shall set the numberOfGoodSSB for the serving cell to one.INTEGER (1..maxNrofSSBs-r16) OPTIONAL } MeasResult2EUTRA-r16 ::= SEQUENCE { carrierFreq-r16 ARFCN-ValueEUTRA, measResultList-r16 MeasResultListEUTRA } MeasResultRLFNR-r16 ::= SEQUENCE { measResult-r16 SEQUENCE { cellResults-r16 SEQUENCE{ resultsSSB-Cell-r16 MeasQuantityResults OPTIONAL, resultsCSI-RS-Cell-r16 MeasQuantityResults OPTIONAL }, rsIndexResults-r16 SEQUENCE{ resultsSSB-Indexes-r16 ResultsPerSSB-IndexList OPTIONAL,ssbRLMConfigBitmap-r16This field is used to indicate the SS/PBCH block indexes configured in the RLM configurations for the active BWP when the UE declares RLF or HOF.The first/leftmost bit corresponds to SSB index 0, the second bit corresponds to SSB index 1. This field is included only if the RadioLinkMonitoringConfig for the respective BWP is configured.BIT STRING (SIZE (64)) OPTIONAL, resultsCSI-RS-Indexes-r16 ResultsPerCSI-RS-IndexList OPTIONAL, csi-rsRLMConfigBitmap-r16 BIT STRING (SIZE (96)) OPTIONAL } OPTIONAL } } TimeSinceFailure-r16 ::= INTEGER (0..172800) MobilityHistoryReport-r16 ::= VisitedCellInfoList-r16 TimeUntilReconnection-r16 ::= INTEGER (0..172800) -- TAG-UEINFORMATIONRESPONSE-STOP -- ASN1STOP
UEInformationResponse-IEs field descriptions |
---|
logMeasReport This field is used to provide the measurement results stored by the UE associated to logged MDT. |
measResultIdleEUTRA EUTRA measurement results performed during RRC_INACTIVE or RRC_IDLE. |
measResultIdleNR NR measurement results performed during RRC_INACTIVE or RRC_IDLE. |
ra-ReportList This field is used to provide the list of RA reports that is stored by the UE for the past upto maxRAReport-r16 number of successful random access procedures. |
rlf-Report This field is used to indicate the RLF report related contents. |
LogMeasReport field descriptions |
---|
absoluteTimeStamp Indicates the absolute time when the logged measurement configuration logging is provided, as indicated by NR within absoluteTimeInfo. |
anyCellSelectionDetected This field is used to indicate the detection of any cell selection state, as defined in TS 38.304 [20]. The UE sets this field when performing the logging of measurement results in RRC_IDLE or RRC_INACTIVE and there is no suitable cell or no acceptable cell. |
measResultServingCell This field refers to the log measurement results taken in the Serving cell. |
numberOfGoodSSB Indicates the number of good beams (beams that are above absThreshSS-BlocksConsolidation, if configured by the network) associated to the cells within the R value range (which is configured by network for cell reselection) of the highest ranked cell as part of the beam level measurements. If the UE has no SSB of a neighbour cell whose measurement quantity is above the absThreshSS-BlocksConsolidation or if the network has not configured the absThreshSS-BlocksConsolidation, then the UE does not include numberOfGoodSSB for the corresponding neighbour cell. If the UE has no SSB of the serving cell whose measurement quantity is above the absThreshSS-BlocksConsolidation or if the network has not configured the absThreshSS-BlocksConsolidation, then the UE shall set the numberOfGoodSSB for the serving cell to one. |
relativeTimeStamp Indicates the time of logging measurement results, measured relative to the absoluteTimeStamp. Value in seconds. |
tce-Id Parameter Trace Collection Entity Id: See TS 32.422 [52]. |
traceRecordingSessionRef Parameter Trace Recording Session Reference: See TS 32.422 [52]. |
ConnEstFailReport field descriptions |
---|
measResultFailedCell This field refers to the last measurement results taken in the cell, where connection establishment failure or connection resume failure happened. |
measResultNeighCells This field refers to the neighbour cell measurements when connection establishment failure or connection resume failure happened. |
numberOfConnFail This field is used to indicate the latest number of consecutive failed RRCSetup or RRCResume procedures in the same cell independent of RRC state transition. |
timeSinceFailure This field is used to indicate the time that elapsed since the connection (establishment or resume) failure.Value in seconds. The maximum value 172800 means 172800s or longer. |
RA-InformationCommon field descriptions |
---|
absoluteFrequencyPointA This field indicates the absolute frequency position of the reference resource block (Common RB 0). |
locationAndBandwidth Frequency domain location and bandwidth of the bandwidth part associated to the random-access resources used by the UE. |
perRAInfoList, perRAInfoList-v1660 This field provides detailed information about each of the random access attempts in the chronological order of the random access attempts. IfperRAInfoList-v1660 is present, it shall contain the same number of entries, listed in the same order as in perRAInfoList-r16. |
subcarrierSpacing Subcarrier spacing used in the BWP associated to the random-access resources used by the UE. |
RA-Report field descriptions |
---|
cellID This field indicates the CGI of the cell in which the associated random access procedure was performed. |
contentionDetected This field is used to indicate that contention was detected for the transmitted preamble in the given random access attempt or not. This field is not included when the UE performs random access attempt is using contention free random-access resources or when the raPurpose is set to requestForOtherSI. |
csi-RS-Index, csi-RS-Index-v1660 This field is used to indicate the CSI-RS index corresponding to the random access attempt. If the random access procedure is for beam failure recovery, the field indicates the NZP-CSI-RS-ResourceId. For CSI-RS index larger than maxNrofCSI-RS-ResourcesRRM-1, the index value is the sum of csi-RS-Index (without suffix) and csi-RS-Index-v1660. |
dlRSRPAboveThreshold This field is used to indicate whether the DL beam (SSB) quality associated to the random access attempt was above or below the threshold rsrp-ThresholdSSBin beamFailureRecoveryConfig in UL BWP configuration of UL BWP selected for random access procedure initiated for beam failure recovery; Otherwise, rsrp-ThresholdSSB in rach-ConfigCommon in UL BWP configuration of UL BWP selected for random access procedure. |
msg1-SCS-From-prach-ConfigurationIndex This field is set by the UE with the corresponding SCS for CBRA as derived from the prach-ConfigurationIndex in RACH-ConfigGenericwhen the msg1-SubcarrierSpacing is absent; otherwise, this field is absent. |
msg1-SCS-From-prach-ConfigurationIndexCFRA This field is set by the UE with the corresponding SCS for CFRA as derived from the prach-ConfigurationIndex in RACH-ConfigGenericwhen the msg1-SubcarrierSpacing is absent; otherwise, this field is absent. |
numberOfPreamblesSentOnCSI-RS This field is used to indicate the total number of successive RA preambles that were transmitted on the corresponding CSI-RS. |
numberOfPreamblesSentOnSSB This field is used to indicate the total number of successive RA preambles that were transmitted on the corresponding SS/PBCH block. |
perRAAttemptInfoList This field provides detailed information about a random access attempt. |
perRACSI-RSInfoList This field provides detailed information about the successive random access attempts associated to the same CSI-RS. |
perRASSBInfoList This field provides detailed information about the successive random access attempts associated to the same SS/PBCH block. |
ra-InformationCommon This field is used to provide information on random access attempts. This field is mandatory present. |
raPurpose This field is used to indicate the RA scenario for which the RA report entry is triggered. The RA accesses associated to Initial access from RRC_IDLE, RRC re-establishment procedure, transition from RRC-INACTIVE and the MSG3 based SI request are indicated using the indicator 'accessRelated'. The indicator beamFailureRecovery is used in case of successful beam failure recovery related RA procedure in the SpCell [3]. The indicator reconfigurationWithSync is used if the UE executes a reconfiguration with sync. The indicator ulUnSynchronized is used if the random access procedure is initiated in a SpCell by DL or UL data arrival during RRC_CONNECTED when the timeAlignmentTimer is not running in the PTAG or if the RA procedure is initiatedin a serving cell by a PDCCH order [3]. The indicator schedulingRequestFailure is used in case of SR failures [3]. The indicator noPUCCHResourceAvailable is used when the UE has no valid SR PUCCH resources configured [3]. The indicator requestForOtherSI is used for MSG1 based on demand SI request. |
ssb-Index This field is used to indicate the SS/PBCH index of the SS/PBCH block corresponding to the random access attempt. |
RLF-Report field descriptions |
---|
connectionFailureType This field is used to indicate whether the connection failure is due to radio link failure or handover failure. |
csi-rsRLMConfigBitmap,csi-rsRLMConfigBitmap-v1650 These fieldsare used to indicate the CSI-RS indexes configured in the RLM configurations for the active BWP when the UE declares RLF or HOF. The UE first fills in the csi-rsRLMConfigBitmap-r16 to indicate the first 96 CSI-RS indexes and then csi-rsRLMConfigBitmap-v1650 to indicate the latter 96 CSI-RS indexes. The first/leftmost bit in csi-rsRLMConfigBitmap-r16 corresponds to CSI-RS index 0, the second bit corresponds to CSI-RS index 1. The first/leftmost bit in csi-rsRLMConfigBitmap-v1650corresponds to CSI-RS index 96, the second bit corresponds to CSI-RS index 97. These fields are included only if the RadioLinkMonitoringConfig for the respective BWP is configured. |
c-RNTI This field indicates the C-RNTI used in the PCell upon detecting radio link failure or the C-RNTI used in the source PCell upon handover failure. |
failedPCellId This field is used to indicate the PCell in which RLF is detected or the target PCell of the failed handover. For intra-NR handover nrFailedPCellId is included and for the handover from NR to EUTRA eutraFailedPCellId is included. The UE sets the ARFCN according to the frequency band used for transmission/ reception when the failure occurred. |
failedPCellId-EUTRA This field is used to indicate the PCell in which RLF is detected or the source PCell of the failed handover in an E-UTRA RLF report. |
measResultListEUTRA This field refers to the last measurement results taken in the neighboring EUTRA Cells, when the radio link failure or handover failure happened. |
measResultListNR This field refers to the last measurement results taken in the neighboring NR Cells, when the radio link failure or handover failure happened. |
measResultLastServCell This field refers to the log measurement results taken in the PCell upon detecting radio link failure or the source PCell upon handover failure. |
measResult-RLF-Report-EUTRA Includes the E-UTRA RLF-Report-r9 IE as specified in TS 36.331 [10]. |
measResult-RLF-Report-EUTRA-v1690 Includes the E-UTRA RLF-Report-v9e0 IE as specified in TS 36.331 [10]. |
noSuitableCellFound This field is set by the UE when the T311 expires. |
previousPCellId This field is used to indicate the source PCell of the last handover (source PCell when the last RRCReconfiguration message including reconfigurationWithSync was received). For intra-NR handover nrPreviousCell is included and for the handover from EUTRA to NR eutraPreviousCell is included. |
ra-InformationCommon This field is optionally included when connectionFailureType is set to 'hof' or when connectionFailureType is set to 'rlf' and the rlf-Cause equals to 'randomAccessProblem' or 'beamRecoveryFailure'; otherwise this field is absent. |
reconnectCellId This field is used to indicate the cell in which the UE comes back to connected after connection failure and after failing to perform reestablishment. If the UE comes back to RRC CONNECTED in an NR cell then nrReconnectCellID is included and if the UE comes back to RRC CONNECTED in an LTE cell then eutraReconnectCellID is included |
reestablishmentCellId This field is used to indicate the cell in which the re-establishment attempt was made after connection failure. |
rlf-Cause This field is used to indicate the cause of the last radio link failure that was detected. In case of handover failure information reporting (i.e., the connectionFailureType is set to 'hof'), the UE is allowed to set this field to any value. |
ssbRLMConfigBitmap This field is used to indicate the SS/PBCH block indexes configured in the RLM configurations for the active BWP when the UE declares RLF or HOF.The first/leftmost bit corresponds to SSB index 0, the second bit corresponds to SSB index 1. This field is included only if the RadioLinkMonitoringConfig for the respective BWP is configured. |
timeConnFailure This field is used to indicate the time elapsed since the last HO initialization until connection failure. Actual value = field value * 100ms. The maximum value 1023 means 102.3s or longer. |
timeSinceFailure This field is used to indicate the time that elapsed since the connection (radio link or handover) failure.Value in seconds. The maximum value 172800 means 172800s or longer. |
timeUntilReconnection This field is used to indicate the time that elapsed between the connection (radio link or handover) failure and the next time the UE comes to RRC CONNECTED in an NR or EUTRA cell, after failing to perform reestablishment.Value in seconds. The maximum value 172800 means 172800s or longer. |
The ULDedicatedMessageSegment message is used to transfer segments of the UECapabilityInformation message.
-- ASN1START -- TAG-ULDEDICATEDMESSAGESEGMENT-START ULDedicatedMessageSegment-r16 ::= SEQUENCE { criticalExtensions CHOICE { ulDedicatedMessageSegment-r16 ULDedicatedMessageSegment-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } ULDedicatedMessageSegment-r16-IEs ::= SEQUENCE {segmentNumber-r16Identifies the sequence number of a segment within the encoded UL DCCH message.INTEGER (0..15),rrc-MessageSegmentContainer-r16Includes a segment of the encoded UL DCCH message. The size of the included segment in this container should be small enough that the resulting encoded RRC message PDU is less than or equal to the PDCP SDU size limit.OCTET STRING,rrc-MessageSegmentType-r16Indicates whether the included UL DCCH message segment is the last segment or not.ENUMERATED {notLastSegment, lastSegment}, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-ULDEDICATEDMESSAGESEGMENT-STOP -- ASN1STOP
ULDedicatedMessageSegment field descriptions |
---|
segmentNumber Identifies the sequence number of a segment within the encoded UL DCCH message. |
rrc-MessageSegmentContainer Includes a segment of the encoded UL DCCH message. The size of the included segment in this container should be small enough that the resulting encoded RRC message PDU is less than or equal to the PDCP SDU size limit. |
rrc-MessageSegmentType Indicates whether the included UL DCCH message segment is the last segment or not. |
The ULInformationTransfer message is used for the uplink transfer of NAS or non-3GPP dedicated information.
-- ASN1START -- TAG-ULINFORMATIONTRANSFER-START ULInformationTransfer ::= SEQUENCE { criticalExtensions CHOICE { ulInformationTransfer ULInformationTransfer-IEs, criticalExtensionsFuture SEQUENCE {} } } ULInformationTransfer-IEs ::= SEQUENCE { dedicatedNAS-Message DedicatedNAS-Message OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-ULINFORMATIONTRANSFER-STOP -- ASN1STOP
The ULInformationTransferIRAT message is used for the uplink transfer of information terminated at NR MCG but specified by another RAT. In this version of the specification, the message is used for V2X sidelink communication messages specified in TS 36.331 [10].
-- ASN1START -- TAG-ULINFORMATIONTRANSFERIRAT-START ULInformationTransferIRAT-r16 ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE { ulInformationTransferIRAT-r16 ULInformationTransferIRAT-r16-IEs, spare3 NULL,spare2 NULL,spare1 NULL }, criticalExtensionsFuture SEQUENCE {} } } ULInformationTransferIRAT-r16-IEs ::= SEQUENCE { ul-DCCH-MessageEUTRA-r16 OCTET STRING OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-ULINFORMATIONTRANSFERIRAT-STOP -- ASN1STOP
The ULInformationTransferMRDC message is used for the uplink transfer of MR-DC dedicated information (e.g. for transferring the NR or E-UTRA RRC MeasurementReport message, the FailureInformation message, the UEAssistanceInformation message, the RRCReconfigurationComplete message or the NR or E-UTRA RRC MCGFailureInformation message).
-- ASN1START -- TAG-ULINFORMATIONTRANSFERMRDC-START ULInformationTransferMRDC ::= SEQUENCE { criticalExtensions CHOICE { c1 CHOICE { ulInformationTransferMRDC ULInformationTransferMRDC-IEs, spare3 NULL,spare2 NULL,spare1 NULL }, criticalExtensionsFuture SEQUENCE {} } } ULInformationTransferMRDC-IEs::= SEQUENCE {ul-DCCH-MessageNRIncludes the UL-DCCH-Message. In this version of the specification, the field is only used to transfer the NR RRC MeasurementReport, RRCReconfigurationComplete, UEAssistanceInformation and FailureInformation messages when sent via SRB1 and to transfer the NR MCGFailureInformation message when sent via SRB3.OCTET STRING OPTIONAL,ul-DCCH-MessageEUTRAIncludes the UL-DCCH-Message. In this version of the specification, the field is only used to transfer the E-UTRA RRC MeasurementReport message when sent via SRB1 and to transfer the E-UTRA MCGFailureInformation message when sent via SRB3.OCTET STRING OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-ULINFORMATIONTRANSFERMRDC-STOP -- ASN1STOP
ULInformationTransferIRAT field descriptions |
---|
ul-DCCH-MessageEUTRA Includes the UL-DCCH-Message as defined in TS 36.331 [10]. In this version of the specification, the field is only used to transfer the E-UTRA RRC MeasurementReport, E-UTRA RRC SidelinkUEInformation and the E-UTRA RRC UEAssistanceInformation messages. |
ULInformationTransferMRDC field descriptions |
---|
ul-DCCH-MessageNR Includes the UL-DCCH-Message. In this version of the specification, the field is only used to transfer the NR RRC MeasurementReport, RRCReconfigurationComplete, UEAssistanceInformation and FailureInformation messages when sent via SRB1 and to transfer the NR MCGFailureInformation message when sent via SRB3. |
ul-DCCH-MessageEUTRA Includes the UL-DCCH-Message. In this version of the specification, the field is only used to transfer the E-UTRA RRC MeasurementReport message when sent via SRB1 and to transfer the E-UTRA MCGFailureInformation message when sent via SRB3. |
SetupRelease allows the ElementTypeParam to be used as the referenced data type for the setup and release entries. See A.3.8 for guidelines.
-- ASN1START -- TAG-SETUPRELEASE-START SetupRelease { ElementTypeParam } ::= CHOICE { release NULL, setup ElementTypeParam } -- TAG-SETUPRELEASE-STOP -- ASN1STOP
SIB2 contains cell re-selection information common for intra-frequency, inter-frequency and/or inter-RAT cell re-selection (i.e. applicable for more than one type of cell re-selection but not necessarily all) as well as intra-frequency cell re-selection information other than neighbouring cell related.
-- ASN1START -- TAG-SIB2-START SIB2 ::= SEQUENCE { cellReselectionInfoCommon SEQUENCE { nrofSS-BlocksToAverage INTEGER (2..maxNrofSS-BlocksToAverage) OPTIONAL, -- Need S absThreshSS-BlocksConsolidation ThresholdNR OPTIONAL, -- Need S rangeToBestCell RangeToBestCell OPTIONAL, -- Need R q-Hyst ENUMERATED { dB0, dB1, dB2, dB3, dB4, dB5, dB6, dB8, dB10, dB12, dB14, dB16, dB18, dB20, dB22, dB24}, speedStateReselectionPars SEQUENCE { mobilityStateParameters MobilityStateParameters, q-HystSF SEQUENCE { sf-Medium ENUMERATED {dB-6, dB-4, dB-2, dB0}, sf-High ENUMERATED {dB-6, dB-4, dB-2, dB0} } } OPTIONAL, -- Need R ... }, cellReselectionServingFreqInfo SEQUENCE { s-NonIntraSearchP ReselectionThreshold OPTIONAL, -- Need S s-NonIntraSearchQ ReselectionThresholdQ OPTIONAL, -- Need S threshServingLowP ReselectionThreshold, threshServingLowQ ReselectionThresholdQ OPTIONAL, -- Need R cellReselectionPriority CellReselectionPriority, cellReselectionSubPriority CellReselectionSubPriority OPTIONAL, -- Need R ... }, intraFreqCellReselectionInfo SEQUENCE { q-RxLevMin Q-RxLevMin, q-RxLevMinSUL Q-RxLevMin OPTIONAL, -- Need R q-QualMin Q-QualMin OPTIONAL, -- Need S s-IntraSearchP ReselectionThreshold, s-IntraSearchQ ReselectionThresholdQ OPTIONAL, -- Need S t-ReselectionNR T-Reselection, frequencyBandList MultiFrequencyBandListNR-SIB OPTIONAL, -- Need S frequencyBandListSUL MultiFrequencyBandListNR-SIB OPTIONAL, -- Need R p-Max P-Max OPTIONAL, -- Need S smtc SSB-MTC OPTIONAL, -- Need S ss-RSSI-Measurement SS-RSSI-Measurement OPTIONAL, -- Need R ssb-ToMeasure SSB-ToMeasure OPTIONAL, -- Need S deriveSSB-IndexFromCell BOOLEAN, ..., [[ t-ReselectionNR-SF SpeedStateScaleFactors OPTIONAL -- Need N ]], [[ smtc2-LP-r16 SSB-MTC2-LP-r16 OPTIONAL, -- Need R ssb-PositionQCL-Common-r16 SSB-PositionQCL-Relation-r16 OPTIONAL -- Cond SharedSpectrum ]] }, ..., [[ relaxedMeasurement-r16 SEQUENCE { lowMobilityEvaluation-r16 SEQUENCE { s-SearchDeltaP-r16 ENUMERATED { dB3, dB6, dB9, dB12, dB15, spare3, spare2, spare1}, t-SearchDeltaP-r16 ENUMERATED { s5, s10, s20, s30, s60, s120, s180, s240, s300, spare7, spare6, spare5, spare4, spare3, spare2, spare1} } OPTIONAL, -- Need R cellEdgeEvaluation-r16 SEQUENCE { s-SearchThresholdP-r16 ReselectionThreshold, s-SearchThresholdQ-r16 ReselectionThresholdQ OPTIONAL -- Need R } OPTIONAL, -- Need R combineRelaxedMeasCondition-r16 ENUMERATED {true} OPTIONAL, -- Need R highPriorityMeasRelax-r16 ENUMERATED {true} OPTIONAL -- Need R } OPTIONAL -- Need R ]] } RangeToBestCell ::= Q-OffsetRange -- TAG-SIB2-STOP -- ASN1STOP
SIB3 contains neighbouring cell related information relevant only for intra-frequency cell re-selection. The IE includes cells with specific re-selection parameters as well as blacklisted cells.
-- ASN1START -- TAG-SIB3-START SIB3 ::= SEQUENCE {intraFreqNeighCellListList of intra-frequency neighbouring cells with specific cell re-selection parameters. If intraFreqNeighCellList-v1610 is present, it shall contain the same number of entries, listed in the same order as in intraFreqNeighCellList (without suffix).IntraFreqNeighCellList OPTIONAL, -- Need RintraFreqBlackCellListList of blacklisted intra-frequency neighbouring cells.IntraFreqBlackCellList OPTIONAL, -- Need R lateNonCriticalExtension OCTET STRING OPTIONAL, ..., [[ intraFreqNeighCellList-v1610 IntraFreqNeighCellList-v1610 OPTIONAL, -- Need RintraFreqWhiteCellList-r16List of whitelisted intra-frequency neighbouring cells, see TS 38.304 [20], clause 5.2.4.IntraFreqWhiteCellList-r16 OPTIONAL, -- Cond SharedSpectrum2intraFreqCAG-CellList-r16List of intra-frequency neighbouring CAG cells (as defined in TS 38.304 [20]) per PLMN.SEQUENCE (SIZE (1..maxPLMN)) OF IntraFreqCAG-CellListPerPLMN-r16 OPTIONAL -- Need R ]] } IntraFreqNeighCellList ::= SEQUENCE (SIZE (1..maxCellIntra)) OF IntraFreqNeighCellInfo IntraFreqNeighCellList-v1610::= SEQUENCE (SIZE (1..maxCellIntra)) OF IntraFreqNeighCellInfo-v1610 IntraFreqNeighCellInfo ::= SEQUENCE { physCellId PhysCellId,q-OffsetCellParameter "Qoffsets,n" in TS 38.304 [20].Q-OffsetRange,q-RxLevMinOffsetCellParameter "Qrxlevminoffsetcell" in TS 38.304 [20]. Actual value Qrxlevminoffsetcell = field value * 2 [dB].INTEGER (1..8) OPTIONAL, -- Need Rq-RxLevMinOffsetCellSULParameter "QrxlevminoffsetcellSUL" in TS 38.304 [20]. Actual value QrxlevminoffsetcellSUL = field value * 2 [dB].INTEGER (1..8) OPTIONAL, -- Need Rq-QualMinOffsetCellParameter "Qqualminoffsetcell" in TS 38.304 [20]. Actual value Qqualminoffsetcell = field value [dB].INTEGER (1..8) OPTIONAL, -- Need R ... } IntraFreqNeighCellInfo-v1610 ::= SEQUENCE {ssb-PositionQCL-r16Indicates the QCL relation between SS/PBCH blocks for a specific intra-frequency neighbor cell as specified in TS 38.213 [13], clause 4.1. If provided, the cell specific value overwrites the value signalled by ssb-PositionQCL-Common in SIB2 for the indicated cell.SSB-PositionQCL-Relation-r16 OPTIONAL -- Cond SharedSpectrum2 } IntraFreqBlackCellList ::= SEQUENCE (SIZE (1..maxCellBlack)) OF PCI-Range IntraFreqWhiteCellList-r16 ::= SEQUENCE (SIZE (1..maxCellWhite)) OF PCI-Range IntraFreqCAG-CellListPerPLMN-r16 ::= SEQUENCE { plmn-IdentityIndex-r16 INTEGER (1..maxPLMN), cag-CellList-r16 SEQUENCE (SIZE (1..maxCAG-Cell-r16)) OF PCI-Range } -- TAG-SIB3-STOP -- ASN1STOP
SIB2 field descriptions |
---|
absThreshSS-BlocksConsolidation Threshold for consolidation of L1 measurements per RS index. If the field is absent, the UE uses the measurement quantity as specified in TS 38.304 [20]. |
cellEdgeEvaluation Indicates the criteria for a UE to detect that it is not at cell edge, in order to relax measurement requirements for cell reselection (see TS 38.304 [20], clause 5.2.4.9.2). |
cellReselectionInfoCommon Cell re-selection information common for intra-frequency, inter-frequency and/ or inter-RAT cell re-selection. |
cellReselectionServingFreqInfo Information common for non-intra-frequency cell re-selection i.e. cell re-selection to inter-frequency and inter-RAT cells. |
combineRelaxedMeasCondition When both lowMobilityEvalutation and cellEdgeEvalutation criteria are present in SIB2, this parameter configures the UE to fulfil both criteria in order to relax measurement requirements for cell reselection. If the field is absent, the UE is allowed to relax measurement requirements for cell reselection when either or both of the criteria are met. (See TS 38.304 [20], clause 5.2.4.9.0) |
deriveSSB-IndexFromCell This field indicates whether the UE can utilize serving cell timing to derive the index of SS block transmitted by neighbour cell. If this field is set to true, the UE assumes SFN and frame boundary alignment across cells on the serving frequency as specified in TS 38.133 [14]. |
frequencyBandList Indicates the list of frequency bands for which the NR cell reselection parameters apply. The UE behaviour in case the field is absent is described in clause 5.2.2.4.3. |
highPriorityMeasRelax Indicates whether measurements can be relaxed on high priority frequencies. If the field is absent, the UE shall not relax measurements on high priority frequenciesbeyond "Thigher_priority_search" unless both low mobility and not at cell edge criteria are fulfilled (see TS 38.133 [14], clauses 4.2.2.7, 4.2.2.10 and 4.2.2.11). |
intraFreqCellReselectionInfo Cell re-selection information common for intra-frequency cells. |
lowMobilityEvaluation Indicates the criteria for a UE to detect low mobility, in order to relax measurement requirements for cell reselection (see TS 38.304 [20], clause 5.2.4.9.1). |
nrofSS-BlocksToAverage Number of SS blocks to average for cell measurement derivation. If the field is absent the UE uses the measurement quantity as specified in TS 38.304 [20]. |
p-Max Value in dBm applicable for the intra-frequency neighbouring NR cells. If absent the UE applies the maximum power according to TS 38.101-1 [15] in case of an FR1 cell or TS 38.101-2 [39] in case of an FR2 cell. In this release of the specification, if p-Max is present on a carrier frequency in FR2, the UE shall ignore the field and applies the maximum power according to TS 38.101-2 [39]. This field is ignored by IAB-MT. The IAB-MT applies output power and emissions requirements, as specified in TS 38.174 [63]. |
q-Hyst Parameter "Qhyst" in TS 38.304 [20], Value in dB. Value dB1 corresponds to 1 dB, dB2 corresponds to 2 dB and so on. |
q-HystSF Parameter "Speed dependent ScalingFactor for Qhyst" in TS 38.304 [20]. The sf-Medium and sf-High concern the additional hysteresis to be applied, in Medium and High Mobility state respectively, to Qhyst as defined in TS 38.304 [20]. In dB. Value dB-6 corresponds to -6dB, dB-4 corresponds to -4dB and so on. |
q-QualMin Parameter "Qqualmin" in TS 38.304 [20], applicable for intra-frequency neighbour cells. If the field is absent, the UE applies the (default) value of negative infinity for Qqualmin. |
q-RxLevMin Parameter "Qrxlevmin" in TS 38.304 [20], applicable for intra-frequency neighbour cells. |
q-RxLevMinSUL Parameter "Qrxlevmin" in TS 38.304 [20], applicable for intra-frequency neighbour cells. |
rangeToBestCell Parameter "rangeToBestCell" in TS 38.304 [20]. The network configures only non-negative (in dB) values. |
relaxedMeasurement Configuration to allow relaxation of RRM measurement requirements for cell reselection (see TS 38.304 [20], clause 5.2.4.9). |
s-IntraSearchP Parameter "SIntraSearchP" in TS 38.304 [20]. |
s-IntraSearchQ Parameter "SIntraSearchQ" in TS 38.304 [20]. If the field is absent, the UE applies the (default) value of 0 dB for SIntraSearchQ. |
s-NonIntraSearchP Parameter "SnonIntraSearchP" in TS 38.304 [20]. If this field is absent, the UE applies the (default) value of infinity for SnonIntraSearchP. |
s-NonIntraSearchQ Parameter "SnonIntraSearchQ" in TS 38.304 [20]. If the field is absent, the UE applies the (default) value of 0 dB for SnonIntraSearchQ. |
s-SearchDeltaP Parameter "SSearchDeltaP" in TS 38.304 [20]. Value dB3 corresponds to 3 dB, dB6 corresponds to 6 dB and so on. |
s-SearchThresholdP Parameter "SSearchThresholdP" in TS 38.304 [20]. The network configures s-SearchThresholdPto be less than or equal to s-IntraSearchP and s-NonIntraSearchP. |
s-SearchThresholdQ Parameter "SSearchThresholdQ" in TS 38.304 [20]. The network configures s-SearchThresholdQto be less than or equal to s-IntraSearchQ and s-NonIntraSearchQ. |
smtc Measurement timing configuration for intra-frequency measurement. If this field is absent, the UE assumes that SSB periodicity is 5 ms for the intra-frequnecy cells. |
smtc2-LP Measurement timing configuration for intra-frequency neighbour cells with a Long Periodicity (LP) indicated by periodicity in smtc2-LP. The timing offset and duration are equal to the offset and duration indicated in smtc in intraFreqCellReselectionInfo. The periodicity in smtc2-LP can only be set to a value strictly larger than the periodicity in smtc in intraFreqCellReselectionInfo (e.g. if smtc indicates sf20 the Long Periodicity can only be set to sf40, sf80 or sf160, if smtc indicates sf160, smtc2-LP cannot be configured). The pci-List, if present, includes the physical cell identities of the intra-frequency neighbour cells with Long Periodicity. If smtc2-LP is absent, the UE assumes that there are no intra-frequency neighbour cells with a Long Periodicity. |
ssb-PositionQCL-Common Indicates the QCL relation between SS/PBCH blocks for intra-frequency neighbor cells as specified in TS 38.213 [13], clause 4.1. |
ssb-ToMeasure The set of SS blocks to be measured within the SMTC measurement duration (see TS 38.215 [9]). When the field is absent the UE measures on all SS-blocks. |
t-ReselectionNR Parameter "TreselectionNR" in TS 38.304 [20]. |
t-ReselectionNR-SF Parameter "Speed dependent ScalingFactor for TreselectionNR" in TS 38.304 [20]. If the field is absent, the UE behaviour is specified in TS 38.304 [20]. |
threshServingLowP Parameter "ThreshServing, LowP" inTS 38.304 [20]. |
threshServingLowQ Parameter "ThreshServing, LowQ" inTS 38.304 [20]. |
t-SearchDeltaP Parameter "TSearchDeltaP" in TS 38.304 [20]. Value in seconds. Value s5 means 5 seconds, value s10 means 10 seconds and so on. |
Conditional Presence | Explanation |
---|---|
SharedSpectrum | This field is mandatory present if this intra-frequency operates with shared spectrum channel access. Otherwise, it is absent, Need R. |
SIB3field descriptions |
---|
intraFreqBlackCellList List of blacklisted intra-frequency neighbouring cells. |
intraFreqCAG-CellList List of intra-frequency neighbouring CAG cells (as defined in TS 38.304 [20]) per PLMN. |
intraFreqNeighCellList List of intra-frequency neighbouring cells with specific cell re-selection parameters. If intraFreqNeighCellList-v1610 is present, it shall contain the same number of entries, listed in the same order as in intraFreqNeighCellList (without suffix). |
intraFreqWhiteCellList List of whitelisted intra-frequency neighbouring cells, see TS 38.304 [20], clause 5.2.4. |
q-OffsetCell Parameter "Qoffsets,n" in TS 38.304 [20]. |
q-QualMinOffsetCell Parameter "Qqualminoffsetcell" in TS 38.304 [20]. Actual value Qqualminoffsetcell = field value [dB]. |
q-RxLevMinOffsetCell Parameter "Qrxlevminoffsetcell" in TS 38.304 [20]. Actual value Qrxlevminoffsetcell = field value * 2 [dB]. |
q-RxLevMinOffsetCellSUL Parameter "QrxlevminoffsetcellSUL" in TS 38.304 [20]. Actual value QrxlevminoffsetcellSUL = field value * 2 [dB]. |
ssb-PositionQCL Indicates the QCL relation between SS/PBCH blocks for a specific intra-frequency neighbor cell as specified in TS 38.213 [13], clause 4.1. If provided, the cell specific value overwrites the value signalled by ssb-PositionQCL-Common in SIB2 for the indicated cell. |
Conditional Presence | Explanation |
---|---|
SharedSpectrum2 | The field is optional present, Need R, if this intra-frequency or neighbor cell operates with shared spectrum channel access. Otherwise, it is absent, Need R. |
SIB4 contains information relevant for inter-frequency cell re-selection (i.e. information about other NR frequencies and inter-frequency neighbouring cells relevant for cell re-selection), which can also be used for NR idle/inactive measurements. The IE includes cell re-selection parameters common for a frequency as well as cell specific re-selection parameters.
-- ASN1START -- TAG-SIB4-START SIB4 ::= SEQUENCE {interFreqCarrierFreqListList of neighbouring carrier frequencies and frequency specific cell re-selection information. If interFreqCarrierFreqList-v1610 is present, it shall contain the same number of entries, listed in the same order as in interFreqCarrierFreqList (without suffix).InterFreqCarrierFreqList, lateNonCriticalExtension OCTET STRING OPTIONAL, ..., [[ interFreqCarrierFreqList-v1610 InterFreqCarrierFreqList-v1610 OPTIONAL -- Need R ]] } InterFreqCarrierFreqList ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo InterFreqCarrierFreqList-v1610 ::= SEQUENCE (SIZE (1..maxFreq)) OF InterFreqCarrierFreqInfo-v1610 InterFreqCarrierFreqInfo ::= SEQUENCE {dl-CarrierFreqThis field indicates center frequency of the SS block of the neighbour cells, where the frequency corresponds to a GSCN value as specified in TS 38.101-1 [15].ARFCN-ValueNR,frequencyBandListIndicates the list of frequency bands for which the NR cell reselection parameters apply.MultiFrequencyBandListNR-SIB OPTIONAL, -- Cond Mandatory frequencyBandListSUL MultiFrequencyBandListNR-SIB OPTIONAL, -- Need RnrofSS-BlocksToAverageNumber of SS blocks to average for cell measurement derivation. If the field is absent, the UE uses the measurement quantity as specified in TS 38.304 [20].INTEGER (2..maxNrofSS-BlocksToAverage) OPTIONAL, -- Need SabsThreshSS-BlocksConsolidationThreshold for consolidation of L1 measurements per RS index. If the field is absent, the UE uses the measurement quantity as specified in TS 38.304 [20].ThresholdNR OPTIONAL, -- Need SsmtcMeasurement timing configuration for inter-frequency measurement. If this field is absent, the UE assumes that SSB periodicity is 5 ms in this frequency.SSB-MTC OPTIONAL, -- Need SssbSubcarrierSpacingSubcarrier spacing of SSB. Only the values 15 kHz or 30 kHz (FR1), and 120 kHz or 240 kHz (FR2) are applicable.SubcarrierSpacing,ssb-ToMeasureThe set of SS blocks to be measured within the SMTC measurement duration (see TS 38.215 [9]). When the field is absent the UE measures on all SS-blocks.SSB-ToMeasure OPTIONAL, -- Need SderiveSSB-IndexFromCellThis field indicates whether the UE may use the timing of any detected cell on that frequency to derive the SSB index of all neighbour cells on that frequency. If this field is set to true, the UE assumes SFN and frame boundary alignment across cells on the neighbor frequency as specified in TS 38.133 [14].BOOLEAN, ss-RSSI-Measurement SS-RSSI-Measurement OPTIONAL, -- Need Rq-RxLevMinParameter "Qrxlevmin" in TS 38.304 [20].Q-RxLevMin,q-RxLevMinSULParameter "Qrxlevmin" in TS 38.304 [20].Q-RxLevMin OPTIONAL, -- Need Rq-QualMinParameter "Qqualmin" in TS 38.304 [20]. If the field is absent, the UE applies the (default) value of negative infinity for Qqualmin.Q-QualMin OPTIONAL, -- Need Sp-MaxValue in dBm applicable for the neighbouring NR cells on this carrier frequency. If absent the UE applies the maximum power according to TS 38.101-1 [15] in case of an FR1 cell or TS 38.101-2 [39] in case of an FR2 cell. In this release of the specification, if p-Max is present on a carrier frequency in FR2, the UE shall ignore the field and applies the maximum power according to TS 38.101-2 [39].This field is ignored by IAB-MT. The IAB-MT applies output power and emissions requirements, as specified in TS 38.174 [63].P-Max OPTIONAL, -- Need St-ReselectionNRParameter "TreselectionNR" in TS 38.304 [20].T-Reselection,t-ReselectionNR-SFParameter "Speed dependent ScalingFactor for TreselectionNR" in TS 38.304 [20]. If the field is absent, the UE behaviour is specified in TS 38.304 [20].SpeedStateScaleFactors OPTIONAL, -- Need SthreshX-HighPParameter "ThreshX, HighP" in TS 38.304 [20].ReselectionThreshold,threshX-LowPParameter "ThreshX, LowP" in TS 38.304 [20].ReselectionThreshold, threshX-Q SEQUENCE {threshX-HighQParameter "ThreshX, HighQ" in TS 38.304 [20].ReselectionThresholdQ,threshX-LowQParameter "ThreshX, LowQ" in TS 38.304 [20].ReselectionThresholdQ } OPTIONAL, -- Cond RSRQ cellReselectionPriority CellReselectionPriority OPTIONAL, -- Need R cellReselectionSubPriority CellReselectionSubPriority OPTIONAL, -- Need Rq-OffsetFreqParameter "Qoffsetfrequency" in TS 38.304 [20].Q-OffsetRange DEFAULT dB0,interFreqNeighCellListList of inter-frequency neighbouring cells with specific cell re-selection parameters. If interFreqNeighCellList-v1610 is present, it shall contain the same number of entries, listed in the same order as in interFreqNeighCellList (without suffix).InterFreqNeighCellList OPTIONAL, -- Need RinterFreqBlackCellListList of blacklisted inter-frequency neighbouring cells.InterFreqBlackCellList OPTIONAL, -- Need R ... } InterFreqCarrierFreqInfo-v1610 ::= SEQUENCE { interFreqNeighCellList-v1610 InterFreqNeighCellList-v1610 OPTIONAL, -- Need Rsmtc2-LP-r16Measurement timing configuration for inter-frequency neighbour cells with a Long Periodicity (LP) indicated by periodicity in smtc2-LP. The timing offset and duration are equal to the offset and duration indicated in smtc in InterFreqCarrierFreqInfo. The periodicity in smtc2-LP can only be set to a value strictly larger than the periodicity in smtc in InterFreqCarrierFreqInfo (e.g. if smtc indicates sf20 the Long Periodicity can only be set to sf40, sf80 or sf160, if smtc indicates sf160, smtc2-LP cannot be configured). The pci-List, if present, includes the physical cell identities of the inter-frequency neighbour cells with Long Periodicity. If smtc2-LP is absent, the UE assumes that there are no inter-frequency neighbour cells with a Long Periodicity.SSB-MTC2-LP-r16 OPTIONAL, -- Need RinterFreqWhiteCellList-r16List of whitelisted inter-frequency neighbouring cells, see TS 38.304 [20], clause 5.2.4.InterFreqWhiteCellList-r16 OPTIONAL, -- Cond SharedSpectrum2ssb-PositionQCL-Common-r16Indicates the QCL relation between SS/PBCH blocks for inter-frequency neighbor cells as specified in TS 38.213 [13], clause 4.1.SSB-PositionQCL-Relation-r16 OPTIONAL, -- Cond SharedSpectruminterFreqCAG-CellList-r16List of inter-frequency neighbouring CAG cells (as defined in TS 38.304 [20] per PLMN.SEQUENCE (SIZE (1..maxPLMN)) OF InterFreqCAG-CellListPerPLMN-r16 OPTIONAL -- Need R } InterFreqNeighCellList ::= SEQUENCE (SIZE (1..maxCellInter)) OF InterFreqNeighCellInfo InterFreqNeighCellList-v1610 ::= SEQUENCE (SIZE (1..maxCellInter)) OF InterFreqNeighCellInfo-v1610 InterFreqNeighCellInfo ::= SEQUENCE { physCellId PhysCellId,q-OffsetCellParameter "Qoffsets,n" in TS 38.304 [20].Q-OffsetRange,q-RxLevMinOffsetCellParameter "Qrxlevminoffsetcell" in TS 38.304 [20]. Actual value Qrxlevminoffsetcell = field value * 2 [dB].INTEGER (1..8) OPTIONAL, -- Need Rq-RxLevMinOffsetCellSULParameter "QrxlevminoffsetcellSUL" in TS 38.304 [20]. Actual value QrxlevminoffsetcellSUL = field value * 2 [dB].INTEGER (1..8) OPTIONAL, -- Need Rq-QualMinOffsetCellParameter "Qqualminoffsetcell" in TS 38.304 [20]. Actual value Qqualminoffsetcell = field value [dB].INTEGER (1..8) OPTIONAL, -- Need R ... } InterFreqNeighCellInfo-v1610 ::= SEQUENCE {ssb-PositionQCL-r16Indicates the QCL relation between SS/PBCH blocks for a specific neighbor cell as specified in TS 38.213 [13], clause 4.1. If provided, the cell specific value overwrites the common value signalled by ssb-PositionQCL-Common in SIB4 for the indicated cell.SSB-PositionQCL-Relation-r16 OPTIONAL -- Cond SharedSpectrum2 } InterFreqBlackCellList ::= SEQUENCE (SIZE (1..maxCellBlack)) OF PCI-Range InterFreqWhiteCellList-r16 ::= SEQUENCE (SIZE (1..maxCellWhite)) OF PCI-Range InterFreqCAG-CellListPerPLMN-r16 ::= SEQUENCE { plmn-IdentityIndex-r16 INTEGER (1..maxPLMN), cag-CellList-r16 SEQUENCE (SIZE (1..maxCAG-Cell-r16)) OF PCI-Range } -- TAG-SIB4-STOP -- ASN1STOP
SIB4 field descriptions |
---|
absThreshSS-BlocksConsolidation Threshold for consolidation of L1 measurements per RS index. If the field is absent, the UE uses the measurement quantity as specified in TS 38.304 [20]. |
deriveSSB-IndexFromCell This field indicates whether the UE may use the timing of any detected cell on that frequency to derive the SSB index of all neighbour cells on that frequency. If this field is set to true, the UE assumes SFN and frame boundary alignment across cells on the neighbor frequency as specified in TS 38.133 [14]. |
dl-CarrierFreq This field indicates center frequency of the SS block of the neighbour cells, where the frequency corresponds to a GSCN value as specified in TS 38.101-1 [15]. |
frequencyBandList Indicates the list of frequency bands for which the NR cell reselection parameters apply. |
interFreqBlackCellList List of blacklisted inter-frequency neighbouring cells. |
interFreqCAG-CellList List of inter-frequency neighbouring CAG cells (as defined in TS 38.304 [20] per PLMN. |
interFreqCarrierFreqList List of neighbouring carrier frequencies and frequency specific cell re-selection information. If interFreqCarrierFreqList-v1610 is present, it shall contain the same number of entries, listed in the same order as in interFreqCarrierFreqList (without suffix). |
interFreqNeighCellList List of inter-frequency neighbouring cells with specific cell re-selection parameters. If interFreqNeighCellList-v1610 is present, it shall contain the same number of entries, listed in the same order as in interFreqNeighCellList (without suffix). |
interFreqWhiteCellList List of whitelisted inter-frequency neighbouring cells, see TS 38.304 [20], clause 5.2.4. |
nrofSS-BlocksToAverage Number of SS blocks to average for cell measurement derivation. If the field is absent, the UE uses the measurement quantity as specified in TS 38.304 [20]. |
p-Max Value in dBm applicable for the neighbouring NR cells on this carrier frequency. If absent the UE applies the maximum power according to TS 38.101-1 [15] in case of an FR1 cell or TS 38.101-2 [39] in case of an FR2 cell. In this release of the specification, if p-Max is present on a carrier frequency in FR2, the UE shall ignore the field and applies the maximum power according to TS 38.101-2 [39].This field is ignored by IAB-MT. The IAB-MT applies output power and emissions requirements, as specified in TS 38.174 [63]. |
q-OffsetCell Parameter "Qoffsets,n" in TS 38.304 [20]. |
q-OffsetFreq Parameter "Qoffsetfrequency" in TS 38.304 [20]. |
q-QualMin Parameter "Qqualmin" in TS 38.304 [20]. If the field is absent, the UE applies the (default) value of negative infinity for Qqualmin. |
q-QualMinOffsetCell Parameter "Qqualminoffsetcell" in TS 38.304 [20]. Actual value Qqualminoffsetcell = field value [dB]. |
q-RxLevMin Parameter "Qrxlevmin" in TS 38.304 [20]. |
q-RxLevMinOffsetCell Parameter "Qrxlevminoffsetcell" in TS 38.304 [20]. Actual value Qrxlevminoffsetcell = field value * 2 [dB]. |
q-RxLevMinOffsetCellSUL Parameter "QrxlevminoffsetcellSUL" in TS 38.304 [20]. Actual value QrxlevminoffsetcellSUL = field value * 2 [dB]. |
q-RxLevMinSUL Parameter "Qrxlevmin" in TS 38.304 [20]. |
smtc Measurement timing configuration for inter-frequency measurement. If this field is absent, the UE assumes that SSB periodicity is 5 ms in this frequency. |
smtc2-LP Measurement timing configuration for inter-frequency neighbour cells with a Long Periodicity (LP) indicated by periodicity in smtc2-LP. The timing offset and duration are equal to the offset and duration indicated in smtc in InterFreqCarrierFreqInfo. The periodicity in smtc2-LP can only be set to a value strictly larger than the periodicity in smtc in InterFreqCarrierFreqInfo (e.g. if smtc indicates sf20 the Long Periodicity can only be set to sf40, sf80 or sf160, if smtc indicates sf160, smtc2-LP cannot be configured). The pci-List, if present, includes the physical cell identities of the inter-frequency neighbour cells with Long Periodicity. If smtc2-LP is absent, the UE assumes that there are no inter-frequency neighbour cells with a Long Periodicity. |
ssb-PositionQCL Indicates the QCL relation between SS/PBCH blocks for a specific neighbor cell as specified in TS 38.213 [13], clause 4.1. If provided, the cell specific value overwrites the common value signalled by ssb-PositionQCL-Common in SIB4 for the indicated cell. |
ssb-PositionQCL-Common Indicates the QCL relation between SS/PBCH blocks for inter-frequency neighbor cells as specified in TS 38.213 [13], clause 4.1. |
ssb-ToMeasure The set of SS blocks to be measured within the SMTC measurement duration (see TS 38.215 [9]). When the field is absent the UE measures on all SS-blocks. |
ssbSubcarrierSpacing Subcarrier spacing of SSB. Only the values 15 kHz or 30 kHz (FR1), and 120 kHz or 240 kHz (FR2) are applicable. |
threshX-HighP Parameter "ThreshX, HighP" in TS 38.304 [20]. |
threshX-HighQ Parameter "ThreshX, HighQ" in TS 38.304 [20]. |
threshX-LowP Parameter "ThreshX, LowP" in TS 38.304 [20]. |
threshX-LowQ Parameter "ThreshX, LowQ" in TS 38.304 [20]. |
t-ReselectionNR Parameter "TreselectionNR" in TS 38.304 [20]. |
t-ReselectionNR-SF Parameter "Speed dependent ScalingFactor for TreselectionNR" in TS 38.304 [20]. If the field is absent, the UE behaviour is specified in TS 38.304 [20]. |
Conditional Presence | Explanation |
---|---|
Mandatory | The field is mandatory present in SIB4. |
RSRQ | The field is mandatory present if threshServingLowQ is present in SIB2; otherwise it is absent. |
SharedSpectrum | This field is mandatory present if this inter-frequency operates with shared spectrum channel access. Otherwise, it is absent, Need R. |
SharedSpectrum2 | The field is optional present, Need R, if this inter-frequency or neighbor cell operates with shared spectrum channel access. Otherwise, it is absent, Need R. |
SIB5 contains information relevant only for inter-RAT cell re-selection i.e. information about E-UTRA frequencies and E-UTRAs neighbouring cells relevant for cell re-selection. The IE includes cell re-selection parameters common for a frequency.
-- ASN1START -- TAG-SIB5-START SIB5 ::= SEQUENCE {carrierFreqListEUTRAList of carrier frequencies of E-UTRA. If the carrierFreqListEUTRA-v1610 is present, it shall contain the same number of entries, listed in the same order as in the carrierFreqListEUTRA (without suffix).CarrierFreqListEUTRA OPTIONAL, -- Need Rt-ReselectionEUTRAParameter "TreselectionEUTRA" in TS 38.304 [20].T-Reselection,t-ReselectionEUTRA-SFParameter "Speed dependent ScalingFactor for TreselectionEUTRA" in TS 38.304 [20]. If the field is absent, the UE behaviour is specified in TS 38.304 [20].SpeedStateScaleFactors OPTIONAL, -- Need S lateNonCriticalExtension OCTET STRING OPTIONAL, ..., [[ carrierFreqListEUTRA-v1610 CarrierFreqListEUTRA-v1610 OPTIONAL -- Need R ]] } CarrierFreqListEUTRA ::= SEQUENCE (SIZE (1..maxEUTRA-Carrier)) OF CarrierFreqEUTRA CarrierFreqListEUTRA-v1610 ::= SEQUENCE (SIZE (1..maxEUTRA-Carrier)) OF CarrierFreqEUTRA-v1610 CarrierFreqEUTRA ::= SEQUENCE { carrierFreq ARFCN-ValueEUTRA,eutra-multiBandInfoListIndicates the list of frequency bands in addition to the band represented by carrierFreq for which cell reselection parameters are common, and a list of additionalPmax and additionalSpectrumEmission values, as defined in TS 36.101 [22], table 6.2.4-1, for the frequency bands in eutra-multiBandInfoListEUTRA-MultiBandInfoList OPTIONAL, -- Need R eutra-FreqNeighCellList EUTRA-FreqNeighCellList OPTIONAL, -- Need Reutra-BlackCellListList of blacklisted E-UTRA neighbouring cells.EUTRA-FreqBlackCellList OPTIONAL, -- Need R allowedMeasBandwidth EUTRA-AllowedMeasBandwidth, presenceAntennaPort1 EUTRA-PresenceAntennaPort1, cellReselectionPriority CellReselectionPriority OPTIONAL, -- Need R cellReselectionSubPriority CellReselectionSubPriority OPTIONAL, -- Need RthreshX-HighParameter "ThreshX, HighP" in TS 38.304 [20].ReselectionThreshold,threshX-LowParameter "ThreshX, LowP" in TS 38.304 [20].ReselectionThreshold,q-RxLevMinParameter "Qrxlevmin" in TS 36.304 [27]. Actual value Qrxlevmin = field value * 2 [dBm].INTEGER (-70..-22),q-QualMinParameter "Qqualmin" in TS 36.304 [27]. Actual value Qqualmin = field value [dB].INTEGER (-34..-3),p-MaxEUTRAThe maximum allowed transmission power in dBm on the (uplink) carrier frequency, see TS 36.304 [27].INTEGER (-30..33), threshX-Q SEQUENCE {threshX-HighQParameter "ThreshX, HighQ" in TS 38.304 [20].ReselectionThresholdQ,threshX-LowQParameter "ThreshX, LowQ" in TS 38.304 [20].ReselectionThresholdQ } OPTIONAL -- Cond RSRQ } CarrierFreqEUTRA-v1610 ::= SEQUENCE {highSpeedEUTRACarrier-r16If the field is present, the UE shall apply the enhanced NR-EUTRA inter-RAT measurement requirements to support high speed up to 500 km/h as specified in TS 38.133 [14] to the E-UTRA carrier.ENUMERATED {true} OPTIONAL -- Need R } EUTRA-FreqBlackCellList ::= SEQUENCE (SIZE (1..maxEUTRA-CellBlack)) OF EUTRA-PhysCellIdRange EUTRA-FreqNeighCellList ::= SEQUENCE (SIZE (1..maxCellEUTRA)) OF EUTRA-FreqNeighCellInfo EUTRA-FreqNeighCellInfo ::= SEQUENCE { physCellId EUTRA-PhysCellId,dummyThis field is not used in the specification. If received it shall be ignored by the UE.EUTRA-Q-OffsetRange,q-RxLevMinOffsetCellParameter "Qrxlevminoffsetcell" in TS 36.304 [27]. Actual value Qrxlevminoffsetcell = field value * 2 [dB].INTEGER (1..8) OPTIONAL, -- Need Rq-QualMinOffsetCellParameter "Qqualminoffsetcell" in TS 36.304 [27]. Actual value Qqualminoffsetcell = field value [dB].INTEGER (1..8) OPTIONAL -- Need R } -- TAG-SIB5-STOP -- ASN1STOP
SIB5 field descriptions |
---|
carrierFreqListEUTRA List of carrier frequencies of E-UTRA. If the carrierFreqListEUTRA-v1610 is present, it shall contain the same number of entries, listed in the same order as in the carrierFreqListEUTRA (without suffix). |
dummy This field is not used in the specification. If received it shall be ignored by the UE. |
eutra-BlackCellList List of blacklisted E-UTRA neighbouring cells. |
eutra-multiBandInfoList Indicates the list of frequency bands in addition to the band represented by carrierFreq for which cell reselection parameters are common, and a list of additionalPmax and additionalSpectrumEmission values, as defined in TS 36.101 [22], table 6.2.4-1, for the frequency bands in eutra-multiBandInfoList |
highSpeedEUTRACarrier If the field is present, the UE shall apply the enhanced NR-EUTRA inter-RAT measurement requirements to support high speed up to 500 km/h as specified in TS 38.133 [14] to the E-UTRA carrier. |
p-MaxEUTRA The maximum allowed transmission power in dBm on the (uplink) carrier frequency, see TS 36.304 [27]. |
q-QualMin Parameter "Qqualmin" in TS 36.304 [27]. Actual value Qqualmin = field value [dB]. |
q-QualMinOffsetCell Parameter "Qqualminoffsetcell" in TS 36.304 [27]. Actual value Qqualminoffsetcell = field value [dB]. |
q-RxLevMin Parameter "Qrxlevmin" in TS 36.304 [27]. Actual value Qrxlevmin = field value * 2 [dBm]. |
q-RxLevMinOffsetCell Parameter "Qrxlevminoffsetcell" in TS 36.304 [27]. Actual value Qrxlevminoffsetcell = field value * 2 [dB]. |
t-ReselectionEUTRA Parameter "TreselectionEUTRA" in TS 38.304 [20]. |
threshX-High Parameter "ThreshX, HighP" in TS 38.304 [20]. |
threshX-HighQ Parameter "ThreshX, HighQ" in TS 38.304 [20]. |
threshX-Low Parameter "ThreshX, LowP" in TS 38.304 [20]. |
threshX-LowQ Parameter "ThreshX, LowQ" in TS 38.304 [20]. |
t-ReselectionEUTRA-SF Parameter "Speed dependent ScalingFactor for TreselectionEUTRA" in TS 38.304 [20]. If the field is absent, the UE behaviour is specified in TS 38.304 [20]. |
Conditional Presence | Explanation |
---|---|
RSRQ | The field is mandatory present if the threshServingLowQ is present in SIB2; otherwise it is absent. |
SIB6 contains an ETWS primary notification.
-- ASN1START -- TAG-SIB6-START SIB6 ::= SEQUENCE {messageIdentifierIdentifies the source and type of ETWS notification.BIT STRING (SIZE (16)),serialNumberIdentifies variations of an ETWS notification.BIT STRING (SIZE (16)),warningTypeIdentifies the warning type of the ETWS primary notification and provides information on emergency user alert and UE popup.OCTET STRING (SIZE (2)), lateNonCriticalExtension OCTET STRING OPTIONAL, ... } -- TAG-SIB6-STOP -- ASN1STOP
SIB6 field descriptions |
---|
messageIdentifier Identifies the source and type of ETWS notification. |
serialNumber Identifies variations of an ETWS notification. |
warningType Identifies the warning type of the ETWS primary notification and provides information on emergency user alert and UE popup. |
SIB7 contains an ETWS secondary notification.
-- ASN1START -- TAG-SIB7-START SIB7 ::= SEQUENCE {messageIdentifierIdentifies the source and type of ETWS notification.BIT STRING (SIZE (16)),serialNumberIdentifies variations of an ETWS notification.BIT STRING (SIZE (16)),warningMessageSegmentTypeIndicates whether the included ETWS warning message segment is the last segment or not.ENUMERATED {notLastSegment, lastSegment},warningMessageSegmentNumberSegment number of the ETWS warning message segment contained in the SIB. A segment number of zero corresponds to the first segment, A segment number of one corresponds to the second segment, and so on.INTEGER (0..63),warningMessageSegmentCarries a segment of the Warning Message Contents IE.OCTET STRING,dataCodingSchemeIdentifies the alphabet/coding and the language applied variations of an ETWS notification.OCTET STRING (SIZE (1)) OPTIONAL, -- Cond Segment1 lateNonCriticalExtension OCTET STRING OPTIONAL, ... } -- TAG-SIB7-STOP -- ASN1STOP
SIB7 field descriptions |
---|
dataCodingScheme Identifies the alphabet/coding and the language applied variations of an ETWS notification. |
messageIdentifier Identifies the source and type of ETWS notification. |
serialNumber Identifies variations of an ETWS notification. |
warningMessageSegment Carries a segment of the Warning Message Contents IE. |
warningMessageSegmentNumber Segment number of the ETWS warning message segment contained in the SIB. A segment number of zero corresponds to the first segment, A segment number of one corresponds to the second segment, and so on. |
warningMessageSegmentType Indicates whether the included ETWS warning message segment is the last segment or not. |
Conditional Presence | Explanation |
---|---|
Segment1 | The field is mandatory present in the first segment of SIB7, otherwise it is absent. |
SIB8 contains a CMAS notification.
-- ASN1START -- TAG-SIB8-START SIB8 ::= SEQUENCE {messageIdentifierIdentifies the source and type of CMAS notification.BIT STRING (SIZE (16)),serialNumberIdentifies variations of a CMAS notification.BIT STRING (SIZE (16)),warningMessageSegmentTypeIndicates whether the included CMAS warning message segment is the last segment or not. If warning area coordinates are provided for the warning message, then this field applies to both warning message segment and warning area coordinates segment.ENUMERATED {notLastSegment, lastSegment},warningMessageSegmentNumberSegment number of the CMAS warning message segment contained in the SIB. A segment number of zero corresponds to the first segment, one corresponds to the second segment, and so on. If warning area coordinates are provided for the warning message, then this field applies to both warning message segment and warning area coordinates segment.INTEGER (0..63),warningMessageSegmentCarries a segment, with one or more octets, of the Warning Message Contents IE defined in TS 38.413 [42]. The first octet of the Warning Message Contents IE is equivalent to the first octet of the CB data IE defined in and encoded according to TS 23.041 [29], clause 9.4.2.2.5, and so on.OCTET STRING,dataCodingSchemeIdentifies the alphabet/coding and the language applied variations of a CMAS notification.OCTET STRING (SIZE (1)) OPTIONAL, -- Cond Segment1warningAreaCoordinatesSegmentIf present, carries a segment, with one or more octets, of the geographical area where the CMAS warning message is valid as defined in [28]. The first octet of the first warningAreaCoordinatesSegment is equivalent to the first octet of Warning Area Coordinates IE defined in and encoded according to TS 23.041 [29] and so on.OCTET STRING OPTIONAL, -- Need R lateNonCriticalExtension OCTET STRING OPTIONAL, ... } -- TAG-SIB8-STOP -- ASN1STOP
SIB8 field descriptions |
---|
dataCodingScheme Identifies the alphabet/coding and the language applied variations of a CMAS notification. |
messageIdentifier Identifies the source and type of CMAS notification. |
serialNumber Identifies variations of a CMAS notification. |
warningAreaCoordinatesSegment If present, carries a segment, with one or more octets, of the geographical area where the CMAS warning message is valid as defined in [28]. The first octet of the first warningAreaCoordinatesSegment is equivalent to the first octet of Warning Area Coordinates IE defined in and encoded according to TS 23.041 [29] and so on. |
warningMessageSegment Carries a segment, with one or more octets, of the Warning Message Contents IE defined in TS 38.413 [42]. The first octet of the Warning Message Contents IE is equivalent to the first octet of the CB data IE defined in and encoded according to TS 23.041 [29], clause 9.4.2.2.5, and so on. |
warningMessageSegmentNumber Segment number of the CMAS warning message segment contained in the SIB. A segment number of zero corresponds to the first segment, one corresponds to the second segment, and so on. If warning area coordinates are provided for the warning message, then this field applies to both warning message segment and warning area coordinates segment. |
warningMessageSegmentType Indicates whether the included CMAS warning message segment is the last segment or not. If warning area coordinates are provided for the warning message, then this field applies to both warning message segment and warning area coordinates segment. |
Conditional Presence | Explanation |
---|---|
Segment1 | The field is mandatory present in the first segment of SIB8, otherwise it is absent. |
SIB9 contains information related to GPS time and Coordinated Universal Time (UTC). The UE may use the parameters provided in this system information block to obtain the UTC,the GPS and the local time.
-- ASN1START -- TAG-SIB9-START SIB9 ::= SEQUENCE { timeInfo SEQUENCE { timeInfoUTC INTEGER (0..549755813887), dayLightSavingTime BIT STRING (SIZE (2)) OPTIONAL, -- Need R leapSeconds INTEGER (-127..128) OPTIONAL, -- Need R localTimeOffset INTEGER (-63..64) OPTIONAL -- Need R } OPTIONAL, -- Need R lateNonCriticalExtension OCTET STRING OPTIONAL, ..., [[ referenceTimeInfo-r16 ReferenceTimeInfo-r16 OPTIONAL -- Need R ]] } -- TAG-SIB9-STOP -- ASN1STOP
SIB10 contains the HRNNs of the NPNs listed in SIB1. SIB10 information element
-- ASN1START -- TAG-SIB10-START SIB10-r16 ::= SEQUENCE { hrnn-List-r16 HRNN-List-r16 OPTIONAL, -- Need R lateNonCriticalExtension OCTET STRING OPTIONAL, ... } HRNN-List-r16 ::= SEQUENCE (SIZE (1..maxNPN-r16)) OF HRNN-r16 HRNN-r16 ::= SEQUENCE { hrnn-r16 OCTET STRING (SIZE(1.. maxHRNN-Len-r16)) OPTIONAL -- Need R } -- TAG-SIB10-STOP -- ASN1STOP
SIB9 field descriptions |
---|
dayLightSavingTime Indicates if and how daylight-saving time (DST) is applied to obtain the local time.The semantics are the same as the semantics of the Daylight Saving Time IE in TS 24.501 [23] and TS 24.008 [38]. The first/leftmost bit of the bit string contains the b2 of octet 3 and the second bit of the bit string contains b1 of octet 3 in the value part of theDaylight Saving Time IE in TS 24.008 [38]. |
leapSeconds Number of leap seconds offset between GPS Time and UTC. UTC and GPS time are related i.e. GPS time -leapSeconds = UTC time. |
localTimeOffset Offset between UTC and local time in units of 15 minutes. Actual value = field value * 15 minutes. Local time of the day is calculated as UTC time + localTimeOffset. |
timeInfoUTC Coordinated Universal Time corresponding to the SFN boundary at or immediately after the ending boundary of the SI-window in which SIB9 is transmitted. The field counts the number of UTC seconds in 10 ms units since 00:00:00 on Gregorian calendar date 1 January, 1900 (midnight between Sunday, December 31, 1899 and Monday, January 1, 1900). See NOTE 1. This field is excluded when determining changes in system information, i.e. changes of timeInfoUTC should neither result in system information change notifications nor in a modification of valueTag in SIB1. |
SIB10 field descriptions |
---|
HRNN-List The same amount of HRNN (see TS 23.003 [21]) elements as the number of NPNs in SIB 1 are included. The n-th entry of HRNN-List contains the human readable network name of the n-th NPN of SIB1. The hrnn in the corresponding entry in HRNN-List is absent if there is no HRNN associated with the given NPN. |
SIB11 contains information related to idle/inactive measurements.
-- ASN1START -- TAG-SIB11-START SIB11-r16 ::= SEQUENCE {measIdleConfigSIB-r16Indicates measurement configuration to be stored and used by the UE while in RRC_IDLE or RRC_INACTIVE.MeasIdleConfigSIB-r16 OPTIONAL, -- Need S lateNonCriticalExtension OCTET STRING OPTIONAL, ... } -- TAG-SIB11-STOP -- ASN1STOP
SIB11 field descriptions |
---|
measIdleConfigSIB Indicates measurement configuration to be stored and used by the UE while in RRC_IDLE or RRC_INACTIVE. |
SIB12 contains NR sidelink communication configuration.
-- ASN1START -- TAG-SIB12-START SIB12-r16 ::= SEQUENCE { segmentNumber-r16 INTEGER (0..63), segmentType-r16 ENUMERATED {notLastSegment, lastSegment}, segmentContainer-r16 OCTET STRING } SIB12-IEs-r16 ::= SEQUENCE { sl-ConfigCommonNR-r16 SL-ConfigCommonNR-r16, lateNonCriticalExtension OCTET STRING OPTIONAL, ... } SL-ConfigCommonNR-r16 ::= SEQUENCE { sl-FreqInfoList-r16 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-FreqConfigCommon-r16 OPTIONAL, -- Need R sl-UE-SelectedConfig-r16 SL-UE-SelectedConfig-r16 OPTIONAL, -- Need R sl-NR-AnchorCarrierFreqList-r16 SL-NR-AnchorCarrierFreqList-r16 OPTIONAL, -- Need R sl-EUTRA-AnchorCarrierFreqList-r16 SL-EUTRA-AnchorCarrierFreqList-r16 OPTIONAL, -- Need R sl-RadioBearerConfigList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SL-RadioBearerConfig-r16 OPTIONAL, -- Need R sl-RLC-BearerConfigList-r16 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-BearerConfig-r16 OPTIONAL, -- Need R sl-MeasConfigCommon-r16 SL-MeasConfigCommon-r16 OPTIONAL, -- Need R sl-CSI-Acquisition-r16 ENUMERATED {enabled} OPTIONAL, -- Need R sl-OffsetDFN-r16 INTEGER (1..1000) OPTIONAL, -- Need R t400-r16 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000} OPTIONAL, -- Need R sl-MaxNumConsecutiveDTX-r16 ENUMERATED {n1, n2, n3, n4, n6, n8, n16, n32} OPTIONAL, -- Need R sl-SSB-PriorityNR-r16 INTEGER (1..8) OPTIONAL -- Need R } SL-NR-AnchorCarrierFreqList-r16 ::= SEQUENCE (SIZE (1..maxFreqSL-NR-r16)) OF ARFCN-ValueNR SL-EUTRA-AnchorCarrierFreqList-r16 ::= SEQUENCE (SIZE (1..maxFreqSL-EUTRA-r16)) OF ARFCN-ValueEUTRA -- TAG-SIB12-STOP -- ASN1STOP
SIB13 contains configurations of V2X sidelink communication defined in TS 36.331 [10].
SIB14 contains configurations of V2X sidelink communication defined in TS 36.331 [10], which can be used jointly with that included in SIB13.
SIB12field descriptions |
---|
segmentContainer This field includes a segment of the encoded SIB12-IEs. The size of the included segment in this container should be small enough that the SIB message size is less than or equal to the maximum size of a NR SI, i.e. 2976 bits when SIB12 is broadcast. |
segmentNumber This field identifies the sequence number of a segment of SIB12-IEs. A segment number of zero corresponds to the first segment, A segment number of one corresponds to the second segment, and so on. |
segmentType This field indicates whether the included segment is the last segment or not. |
sl-CSI-Acquisition This field indicates whether CSI reporting is enabled in sidelink unicast. If not set, SL CSI reporting is disabled. |
sl-EUTRA-AnchorCarrierFreqList This field indicates the EUTRA anchor carrier frequency list, which can provide the NR sidelink communication configurations. |
sl-FreqInfoList This field indicates the NR sidelink communication configuration on some carrier frequency (ies). In this release, only one entry can be configured in the list. |
sl-MaxNumConsecutiveDTX This field indicates the maximum number of consecutive HARQ DTX before triggering sidelink RLF. Value n1 corresponds to 1, value n2 corresponds to 2, and so on. |
sl-MeasConfigCommon This field indicates the measurement configurations (e.g. RSRP) for NR sidelink communication. |
sl-NR-AnchorCarrierFreqList This field indicates the NR anchor carrier frequency list, which can provide the NR sidelink communication configurations. |
sl-OffsetDFN Indicates the timing offset for the UE to determine DFN timing when GNSS is used for timing reference. Value 1 corresponds to 0.001 milliseconds, value 2 corresponds to 0.002 milliseconds, and so on. |
sl-RadioBearerConfigList This field indicates one or multiple sidelink radio bearer configurations. |
sl-RLC-BearerConfigList This field indicates one or multiple sidelink RLC bearer configurations. |
sl-SSB-PriorityNR This field indicates the priority of NR sidelink SSB transmission and reception. |
t400 Indicates the value for timer T400 as described in clause 7.1. Value ms100 corresponds to 100 ms, value ms200 corresponds to 200 ms and so on. |
SIB13field descriptions |
---|
dummy This field is not used in the specification and the UE ignores the received value. |
sl-V2X-ConfigCommon This field includes the E-UTRA SystemInformationBlockType21 message as specified in TS 36.331 [10]. |
tdd-Config This field includes the tdd-Config in E-UTRA SystemInformationBlockType1 message as specified in TS 36.331 [10]. |
SIB14field descriptions |
---|
sl-V2X-ConfigCommonExt This field includes the E-UTRA SystemInformationBlockType26 message as specified in TS 36.331 [10]. |
-- ASN1START -- TAG-POSSYSTEMINFORMATION-R16-IES-START PosSystemInformation-r16-IEs ::= SEQUENCE { posSIB-TypeAndInfo-r16 SEQUENCE (SIZE (1..maxSIB)) OF CHOICE { posSib1-1-r16 SIBpos-r16, posSib1-2-r16 SIBpos-r16, posSib1-3-r16 SIBpos-r16, posSib1-4-r16 SIBpos-r16, posSib1-5-r16 SIBpos-r16, posSib1-6-r16 SIBpos-r16, posSib1-7-r16 SIBpos-r16, posSib1-8-r16 SIBpos-r16, posSib2-1-r16 SIBpos-r16, posSib2-2-r16 SIBpos-r16, posSib2-3-r16 SIBpos-r16, posSib2-4-r16 SIBpos-r16, posSib2-5-r16 SIBpos-r16, posSib2-6-r16 SIBpos-r16, posSib2-7-r16 SIBpos-r16, posSib2-8-r16 SIBpos-r16, posSib2-9-r16 SIBpos-r16, posSib2-10-r16 SIBpos-r16, posSib2-11-r16 SIBpos-r16, posSib2-12-r16 SIBpos-r16, posSib2-13-r16 SIBpos-r16, posSib2-14-r16 SIBpos-r16, posSib2-15-r16 SIBpos-r16, posSib2-16-r16 SIBpos-r16, posSib2-17-r16 SIBpos-r16, posSib2-18-r16 SIBpos-r16, posSib2-19-r16 SIBpos-r16, posSib2-20-r16 SIBpos-r16, posSib2-21-r16 SIBpos-r16, posSib2-22-r16 SIBpos-r16, posSib2-23-r16 SIBpos-r16, posSib3-1-r16 SIBpos-r16, posSib4-1-r16 SIBpos-r16, posSib5-1-r16 SIBpos-r16, posSib6-1-r16 SIBpos-r16, posSib6-2-r16 SIBpos-r16, posSib6-3-r16 SIBpos-r16, ... }, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-POSSYSTEMINFORMATION-R16-IES-STOP -- ASN1STOP
-- ASN1START -- TAG-POSSI-SCHEDULINGINFO-START PosSI-SchedulingInfo-r16 ::= SEQUENCE { posSchedulingInfoList-r16 SEQUENCE (SIZE (1..maxSI-Message)) OF PosSchedulingInfo-r16, posSI-RequestConfig-r16 SI-RequestConfig OPTIONAL, -- Cond MSG-1 posSI-RequestConfigSUL-r16 SI-RequestConfig OPTIONAL, -- Cond SUL-MSG-1 ... } PosSchedulingInfo-r16 ::= SEQUENCE { offsetToSI-Used-r16 ENUMERATED {true} OPTIONAL, -- Need R posSI-Periodicity-r16 ENUMERATED {rf8, rf16, rf32, rf64, rf128, rf256, rf512}, posSI-BroadcastStatus-r16 ENUMERATED {broadcasting, notBroadcasting}, posSIB-MappingInfo-r16 PosSIB-MappingInfo-r16, ... } PosSIB-MappingInfo-r16 ::= SEQUENCE (SIZE (1..maxSIB)) OF PosSIB-Type-r16 PosSIB-Type-r16 ::= SEQUENCE { encrypted-r16 ENUMERATED { true } OPTIONAL, -- Need R gnss-id-r16 GNSS-ID-r16 OPTIONAL, -- Need R sbas-id-r16 SBAS-ID-r16 OPTIONAL, -- Cond GNSS-ID-SBAS posSibType-r16 ENUMERATED { posSibType1-1, posSibType1-2, posSibType1-3, posSibType1-4, posSibType1-5, posSibType1-6, posSibType1-7, posSibType1-8, posSibType2-1, posSibType2-2, posSibType2-3, posSibType2-4, posSibType2-5, posSibType2-6, posSibType2-7, posSibType2-8, posSibType2-9, posSibType2-10, posSibType2-11, posSibType2-12, posSibType2-13, posSibType2-14, posSibType2-15, posSibType2-16, posSibType2-17, posSibType2-18, posSibType2-19, posSibType2-20, posSibType2-21, posSibType2-22, posSibType2-23, posSibType3-1, posSibType4-1, posSibType5-1,posSibType6-1, posSibType6-2, posSibType6-3,... }, areaScope-r16 ENUMERATED {true} OPTIONAL -- Need S } GNSS-ID-r16 ::= SEQUENCE { gnss-id-r16 ENUMERATED{gps, sbas, qzss, galileo, glonass, bds, ...}, ... } SBAS-ID-r16 ::= SEQUENCE { sbas-id-r16 ENUMERATED { waas, egnos, msas, gagan, ...}, ... } -- TAG-POSSI-SCHEDULINGINFO-STOP -- ASN1STOP
The IE SIBpos contains positioning assistance data as defined in TS 37.355 [49].
-- ASN1START -- TAG-SIPOS-START SIBpos-r16 ::= SEQUENCE {assistanceDataSIB-Element-r16Parameter AssistanceDataSIBelement defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit.OCTET STRING, lateNonCriticalExtension OCTET STRING OPTIONAL, ... } -- TAG-SIPOS-STOP -- ASN1STOP
PosSI-SchedulingInfo field descriptions |
---|
areaScope Indicates that a posSIB is area specific. If the field is absent, the posSIB is cell specific. |
encrypted The presence of this field indicates that the pos-sib-type is encrypted as specified in TS 37.355 [49]. |
gnss-id The presence of this field indicates that the positioning SIB type is for a specific GNSS. Indicates a specific GNSS (see also TS 37.355 [49]) |
posSI-BroadcastStatus Indicates if the SI message is being broadcasted or not.Change of posSI-BroadcastStatus should not result in system information change notifications in Short Message transmitted with P-RNTI over DCI (see clause 6.5). The value of the indication is valid until the end of the BCCH modification period when set to broadcasting. |
posSI-RequestConfig Configuration of Msg1 resources that the UE uses for requesting SI-messages for which posSI-BroadcastStatus is set to notBroadcasting. |
posSI-RequestConfigSUL Configuration of Msg1 resources that the UE uses for requesting SI-messages for which posSI-BroadcastStatus is set to notBroadcasting. |
posSIB-MappingInfo List of the posSIBs mapped to this SystemInformation message. |
posSibType The positioning SIB type is defined in TS 37.355 [49]. |
posSI-Periodicity Periodicity of the SI-message in radio frames, such that rf8 denotes 8 radio frames, rf16 denotes 16 radio frames, and so on. If the offsetToSI-Used is configured, the posSI-Periodicity of rf8 cannot be used. |
offsetToSI-Used This field, if present indicates that all the SI messages in posSchedulingInfoList are scheduled with an offset of 8 radio frames compared to SI messages in schedulingInfoList. offsetToSI-Used may be present only if the shortest configured SI message periodicity for SI messages in schedulingInfoList is 80ms. If SI offset is used, this field is present in each of the SI messages in the posSchedulingInfoList. |
sbas-id The presence of this field indicates that the positioning SIB type is for a specific SBAS. Indicates a specific SBAS (see also TS 37.355 [49]). |
Conditional presence | Explanation |
---|---|
GNSS-ID-SBAS | The field is mandatory present if gnss-id is set to sbas. It is absent otherwise. |
MSG-1 | The field is optionally present, Need R, if posSI-BroadcastStatus is set to notBroadcastingfor any SI-message included in posSchedulingInfoList. It is absent otherwise. |
SUL-MSG-1 | The field is optionally present, Need R, if supplementaryUplink is configured in ServingCellConfigCommonSIB and if posSI-BroadcastStatus is set to notBroadcasting for any SI-message included in posSchedulingInfoList. It is absent otherwise. |
SIBpos field descriptions |
---|
assistanceDataSIB-Element Parameter AssistanceDataSIBelement defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit. |
The IE AdditionalSpectrumEmission is used to indicate emission requirements to be fulfilled by the UE (see TS 38.101-1 [15], clause 6.2.3/6.2A.3, and TS 38.101-2 [39], clause 6.2.3/6.2A.3).
The IE Alpha defines possible values of a the pathloss compensation coefficient for uplink power control. Value alpha0 corresponds to the value 0, Value alpha04 corresponds to the value 0.4, Value alpha05 corresponds to the value 0.5 and so on. Value alpha1 corresponds to value 1. See also clause 7.1 of TS 38.213 [13].
The IE AMF-Identifier (AMFI) comprises of an AMF Region ID,an AMF Set ID and an AMF Pointer as specified in TS 23.003 [21], clause 2.10.1.
The IE ARFCN-ValueEUTRA is used to indicate the ARFCN applicable for a downlink, uplink or bi-directional (TDD) E-UTRA carrier frequency, as defined in TS 36.101 [22].
The IE ARFCN-ValueNR is used to indicate the ARFCN applicable for a downlink, uplink or bi-directional (TDD) NR global frequency raster, as defined in TS 38.101-1 [15] and TS 38.101-2 [39], clause 5.4.2.
The IE ARFCN-ValueUTRA-FDD is used to indicate the ARFCN applicable for a downlink (Nd, FDD) UTRA-FDD carrier frequency, as defined in TS 25.331 [45].
The IE AvailabilityCombinationsPerCell is used to configure the AvailabilityCombinations applicable for a cell of the IAB DU (see TS 38.213 [13], clause 14). Note that the IE AvailabilityCombinationsPerCellIndex can only be configured up to 511.
-- ASN1START -- TAG-AVAILABILITYCOMBINATIONSPERCELL-START AvailabilityCombinationsPerCell-r16 ::= SEQUENCE { availabilityCombinationsPerCellIndex-r16 AvailabilityCombinationsPerCellIndex-r16,iab-DU-CellIdentity-r16The ID of the IAB-DU cell for which the availabilityCombinations are applicable.CellIdentity,positionInDCI-AI-r16The (starting) position (bit) of the availabilityCombinationId for the indicated IAB-DU cell (iab-DU-CellIdentity) within the DCI payload.INTEGER(0..maxAI-DCI-PayloadSize-1-r16) OPTIONAL, -- Need M availabilityCombinations-r16 SEQUENCE (SIZE (1..maxNrofAvailabilityCombinationsPerSet-r16)) OF AvailabilityCombination-r16, ... } AvailabilityCombinationsPerCellIndex-r16 ::= INTEGER(0..maxNrofDUCells-r16) AvailabilityCombination-r16 ::= SEQUENCE {availabilityCombinationId-r16This ID is used in the DCI Format 2_5 payload to dynamically select this AvailabilityCombination, see TS 38.213 [13], clause 14.AvailabilityCombinationId-r16,resourceAvailability-r16Indicates the resource availability of soft symbols for a set of consecutive slots in the time domain. The meaning of this fieldis described in TS 38.213 [13], Table 14.3.SEQUENCE (SIZE (1..maxNrofResourceAvailabilityPerCombination-r16)) OF INTEGER (0..7) } AvailabilityCombinationId-r16 ::= INTEGER (0..maxNrofAvailabilityCombinationsPerSet-1-r16) -- TAG-AVAILABILITYCOMBINATIONSPERCELL-STOP -- ASN1STOP
AvailabilityCombination field descriptions |
---|
resourceAvailability Indicates the resource availability of soft symbols for a set of consecutive slots in the time domain. The meaning of this fieldis described in TS 38.213 [13], Table 14.3. |
availabilityCombinationId This ID is used in the DCI Format 2_5 payload to dynamically select this AvailabilityCombination, see TS 38.213 [13], clause 14. |
AvailabilityCombinationsPerCell field descriptions |
---|
iab-DU-CellIdentity The ID of the IAB-DU cell for which the availabilityCombinations are applicable. |
positionInDCI-AI The (starting) position (bit) of the availabilityCombinationId for the indicated IAB-DU cell (iab-DU-CellIdentity) within the DCI payload. |
The IE AvailabilityIndicator is used to configure monitoring a PDCCH for Availability Indicators (AI).
-- ASN1START -- TAG-AVAILABILITYINDICATOR-START AvailabilityIndicator-r16 ::= SEQUENCE {ai-RNTI-r16Used by an IAB-MT for detection of DCI format 2_5 indicating AvailabilityCombinationId for an IAB-DU's cells.AI-RNTI-r16,dci-PayloadSizeAI-r16Total length of the DCI payload scrambled with ai-RNTI (see TS 38.213 [13]).INTEGER (1..maxAI-DCI-PayloadSize-r16),availableCombToAddModList-r16A list of availabilityCombinations to add for the IAB-DU's cells. (see TS 38.213 [13], clause 14).SEQUENCE (SIZE(1..maxNrofDUCells-r16)) OF AvailabilityCombinationsPerCell-r16 OPTIONAL, -- Need NavailableCombToReleaseList-r16A list of availabilityCombinations to release for the IAB-DU's cells. (see TS 38.213 [13], clause 14).SEQUENCE (SIZE(1..maxNrofDUCells-r16)) OF AvailabilityCombinationsPerCellIndex-r16 OPTIONAL, -- Need N ... } AI-RNTI-r16 ::= RNTI-Value -- TAG-AVAILABILITYINDICATOR-STOP -- ASN1STOP
AvailabilityIndicator field descriptions |
---|
ai-RNTI Used by an IAB-MT for detection of DCI format 2_5 indicating AvailabilityCombinationId for an IAB-DU's cells. |
availableCombToAddModList A list of availabilityCombinations to add for the IAB-DU's cells. (see TS 38.213 [13], clause 14). |
availableCombToReleaseList A list of availabilityCombinations to release for the IAB-DU's cells. (see TS 38.213 [13], clause 14). |
dci-PayloadSizeAI Total length of the DCI payload scrambled with ai-RNTI (see TS 38.213 [13]). |
The IE BAP-RoutingID is used for IAB-node to configure the BAP Routing ID.
BAP-RoutingID field descriptions |
---|
bap-Address The ID of a destination IAB-node or IAB-donor-DU used in the BAP header. |
bap-PathId The ID of a path used in the BAP header. |
The IE BeamFailureRecoveryConfig is used to configure the UE with RACH resources and candidate beams for beam failure recovery in case of beam failure detection. See also TS 38.321 [3], clause 5.1.1.
-- ASN1START -- TAG-BEAMFAILURERECOVERYCONFIG-START BeamFailureRecoveryConfig ::= SEQUENCE {rootSequenceIndex-BFRPRACH root sequence index (see TS 38.211 [16], clause 6.3.3.1) for beam failure recovery.INTEGER (0..137) OPTIONAL, -- Need Mrach-ConfigBFRConfiguration of random access parameters for BFR.RACH-ConfigGeneric OPTIONAL, -- Need Mrsrp-ThresholdSSBL1-RSRP threshold used for determining whether a candidate beam may be used by the UE to attempt contention free random access to recover from beam failure (see TS 38.213 [13], clause 6).RSRP-Range OPTIONAL, -- Need M candidateBeamRSList SEQUENCE (SIZE(1..maxNrofCandidateBeams)) OF PRACH-ResourceDedicatedBFR OPTIONAL, -- Need Mssb-perRACH-OccasionNumber of SSBs per RACH occasion for CF-BFR, see TS 38.213 [13], clause 8.1.ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen} OPTIONAL, -- Need Mra-ssb-OccasionMaskIndexExplicitly signalled PRACH Mask Index for RA Resource selection in TS 38.321 [3]. The mask is valid for all SSB resources.INTEGER (0..15) OPTIONAL, -- Need MrecoverySearchSpaceIdSearch space to use for BFR RAR. The network configures this search space to be within the linked DL BWP (i.e., within the DL BWP with the same bwp-Id) of the UL BWP in which the BeamFailureRecoveryConfig is provided. The CORESET associated with the recovery search space cannot be associated with another search space. Network always configures the UE with a value for this field when contention free random access resources for BFR are configured.SearchSpaceId OPTIONAL, -- Need R ra-Prioritization RA-Prioritization OPTIONAL, -- Need RbeamFailureRecoveryTimerTimer for beam failure recovery timer. Upon expiration of the timer the UE does not use CFRA for BFR. Value in ms. Value ms10 corresponds to 10 ms, value ms20 corresponds to 20 ms, and so on.ENUMERATED {ms10, ms20, ms40, ms60, ms80, ms100, ms150, ms200} OPTIONAL, -- Need M ..., [[msg1-SubcarrierSpacingSubcarrier spacing for contention free beam failure recovery. Only the values 15 kHz or 30 kHz (FR1), and 60 kHz or 120 kHz (FR2) are applicable. See TS 38.211 [16], clause 5.3.2.SubcarrierSpacing OPTIONAL -- Need M ]], [[ra-PrioritizationTwoStep-r16Parameters which apply for prioritized 2-step random access procedure for BFR (see TS 38.321 [3], clause 5.1.1).RA-Prioritization OPTIONAL, -- Need R candidateBeamRSListExt-v1610 SetupRelease{ CandidateBeamRSListExt-r16 } OPTIONAL -- Need M ]], [[spCell-BFR-CBRA-r16Indicates that UE is configured to send BFR MAC CE for SpCell BFR as specified in TS38.321 [3].ENUMERATED {true} OPTIONAL -- Need R ]] } PRACH-ResourceDedicatedBFR ::= CHOICE {ssbThe ID of an SSB transmitted by this serving cell. It determines a candidate beam for beam failure recovery (BFR).BFR-SSB-Resource,csi-RSThe ID of a NZP-CSI-RS-Resource configured in the CSI-MeasConfig of this serving cell. This reference signal determines a candidate beam for beam failure recovery (BFR).BFR-CSIRS-Resource } BFR-SSB-Resource ::= SEQUENCE {ssbThe ID of an SSB transmitted by this serving cell. It determines a candidate beam for beam failure recovery (BFR).SSB-Index,ra-PreambleIndexThe preamble index that the UE shall use when performing BFR upon selecting the candidate beams identified by this SSB.INTEGER (0..63), ... } BFR-CSIRS-Resource ::= SEQUENCE {csi-RSThe ID of a NZP-CSI-RS-Resource configured in the CSI-MeasConfig of this serving cell. This reference signal determines a candidate beam for beam failure recovery (BFR).NZP-CSI-RS-ResourceId,ra-OccasionListRA occasions that the UE shall use when performing BFR upon selecting the candidate beam identified by this CSI-RS.The network ensures that the RA occasion indexes provided herein are also configured by prach-ConfigurationIndex and msg1-FDM. Each RACH occasion is sequentially numbered, first, in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions; second, in increasing order of time resource indexes for time multiplexed PRACH occasions within a PRACH slot and Third, in increasing order of indexes for PRACH slots. If the field is absent the UE uses the RA occasion associated with the SSB that is QCLed with this CSI-RS.SEQUENCE (SIZE(1..maxRA-OccasionsPerCSIRS)) OF INTEGER (0..maxRA-Occasions-1) OPTIONAL, -- Need Rra-PreambleIndexThe preamble index that the UE shall use when performing BFR upon selecting the candidate beams identified by this SSB.INTEGER (0..63) OPTIONAL, -- Need R ... } CandidateBeamRSListExt-r16::= SEQUENCE (SIZE(1.. maxNrofCandidateBeamsExt-r16)) OF PRACH-ResourceDedicatedBFR -- TAG-BEAMFAILURERECOVERYCONFIG-STOP -- ASN1STOP
BeamFailureRecoveryConfig field descriptions |
---|
beamFailureRecoveryTimer Timer for beam failure recovery timer. Upon expiration of the timer the UE does not use CFRA for BFR. Value in ms. Value ms10 corresponds to 10 ms, value ms20 corresponds to 20 ms, and so on. |
candidateBeamRSList, candidateBeamRSListExt-v1610 Set of reference signals (CSI-RS and/or SSB) identifying the candidate beams for recovery and the associated RA parameters. This set includes all elements of candidateBeamRSList (without suffix) and all elements of candidateBeamRSListExt-v1610.The UE maintains candidateBeamRSList and candidateBeamRSListExt-v1610 separately: Receiving candidateBeamRSListExt-v1610 set to release releases only the entries that were configured by candidateBeamRSListExt-v1610, and receiving candidateBeamRSListExt-v1610 set to setup replaces only the entries that were configured by candidateBeamRSListExt-v1610 with the newly signalled entries. The network configures these reference signals to be within the linked DL BWP (i.e., within the DL BWP with the same bwp-Id) of the UL BWP in which the BeamFailureRecoveryConfig is provided. |
msg1-SubcarrierSpacing Subcarrier spacing for contention free beam failure recovery. Only the values 15 kHz or 30 kHz (FR1), and 60 kHz or 120 kHz (FR2) are applicable. See TS 38.211 [16], clause 5.3.2. |
rsrp-ThresholdSSB L1-RSRP threshold used for determining whether a candidate beam may be used by the UE to attempt contention free random access to recover from beam failure (see TS 38.213 [13], clause 6). |
ra-prioritization Parameters which apply for prioritized random access procedure for BFR (see TS 38.321 [3], clause 5.1.1). |
ra-PrioritizationTwoStep Parameters which apply for prioritized 2-step random access procedure for BFR (see TS 38.321 [3], clause 5.1.1). |
ra-ssb-OccasionMaskIndex Explicitly signalled PRACH Mask Index for RA Resource selection in TS 38.321 [3]. The mask is valid for all SSB resources. |
rach-ConfigBFR Configuration of random access parameters for BFR. |
recoverySearchSpaceId Search space to use for BFR RAR. The network configures this search space to be within the linked DL BWP (i.e., within the DL BWP with the same bwp-Id) of the UL BWP in which the BeamFailureRecoveryConfig is provided. The CORESET associated with the recovery search space cannot be associated with another search space. Network always configures the UE with a value for this field when contention free random access resources for BFR are configured. |
rootSequenceIndex-BFR PRACH root sequence index (see TS 38.211 [16], clause 6.3.3.1) for beam failure recovery. |
spCell-BFR-CBRA Indicates that UE is configured to send BFR MAC CE for SpCell BFR as specified in TS38.321 [3]. |
ssb-perRACH-Occasion Number of SSBs per RACH occasion for CF-BFR, see TS 38.213 [13], clause 8.1. |
BFR-CSIRS-Resource field descriptions |
---|
csi-RS The ID of a NZP-CSI-RS-Resource configured in the CSI-MeasConfig of this serving cell. This reference signal determines a candidate beam for beam failure recovery (BFR). |
ra-OccasionList RA occasions that the UE shall use when performing BFR upon selecting the candidate beam identified by this CSI-RS.The network ensures that the RA occasion indexes provided herein are also configured by prach-ConfigurationIndex and msg1-FDM. Each RACH occasion is sequentially numbered, first, in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions; second, in increasing order of time resource indexes for time multiplexed PRACH occasions within a PRACH slot and Third, in increasing order of indexes for PRACH slots. If the field is absent the UE uses the RA occasion associated with the SSB that is QCLed with this CSI-RS. |
ra-PreambleIndex The RA preamble index to use in the RA occasions associated with this CSI-RS. If the field is absent, the UE uses the preamble index associated with the SSB that is QCLed with this CSI-RS. |
BFR-SSB-Resource field descriptions |
---|
ra-PreambleIndex The preamble index that the UE shall use when performing BFR upon selecting the candidate beams identified by this SSB. |
ssb The ID of an SSB transmitted by this serving cell. It determines a candidate beam for beam failure recovery (BFR). |
The IE BeamFailureRecoverySCellConfig is used to configure the UE with candidate beams for beam failure recovery in case of beam failure detection in SCell. See also TS 38.321 [3], clause 5.17.
-- ASN1START -- TAG-BEAMFAILURERECOVERYSCELLCONFIG-START BeamFailureRecoverySCellConfig-r16 ::= SEQUENCE {rsrp-ThresholdBFR-r16L1-RSRP threshold used for determining whether a candidate beam may be included by the UE in BFR MAC CE (see TS 38.213 [13], clause 6).The network always configures this parameter in every instance of this IE.RSRP-Range OPTIONAL, -- Need McandidateBeamRSSCellList-r16A list of reference signals (CSI-RS and/or SSB) identifying the candidate beams for recovery. The network always configures this parameter in every instance of this IE.SEQUENCE (SIZE(1..maxNrofCandidateBeams-r16)) OF CandidateBeamRS-r16 OPTIONAL, -- Need M ... } CandidateBeamRS-r16 ::= SEQUENCE {candidateBeamConfig-r16Indicates the resource (i.e. SSB or CSI-RS) defining this beam resource.CHOICE { ssb-r16 SSB-Index, csi-RS-r16 NZP-CSI-RS-ResourceId },servingCellIdIf the field is absent, the RS belongs to the serving cell in which this BeamFailureSCellRecoveryConfig is configuredServCellIndex OPTIONAL -- Need R } -- TAG-BEAMFAILURERECOVERYSCELLCONFIG-STOP -- ASN1STOP
BeamFailureRecoverySCellConfig field descriptions |
---|
candidateBeamConfig Indicates the resource (i.e. SSB or CSI-RS) defining this beam resource. |
candidateBeamRSSCellList A list of reference signals (CSI-RS and/or SSB) identifying the candidate beams for recovery. The network always configures this parameter in every instance of this IE. |
rsrp-ThresholdBFR L1-RSRP threshold used for determining whether a candidate beam may be included by the UE in BFR MAC CE (see TS 38.213 [13], clause 6).The network always configures this parameter in every instance of this IE. |
servingCellId If the field is absent, the RS belongs to the serving cell in which this BeamFailureSCellRecoveryConfig is configured |
The IE BetaOffsets is used to configure beta-offset values, see TS 38.213 [13], clause 9.3.
-- ASN1START -- TAG-BETAOFFSETS-START BetaOffsets ::= SEQUENCE {betaOffsetACK-Index1Up to 2 bits HARQ-ACK (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 11.INTEGER(0..31) OPTIONAL, -- Need SbetaOffsetACK-Index2Up to 11 bits HARQ-ACK (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 11.INTEGER(0..31) OPTIONAL, -- Need SbetaOffsetACK-Index3Above 11 bits HARQ-ACK (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 11.INTEGER(0..31) OPTIONAL, -- Need SbetaOffsetCSI-Part1-Index1Up to 11 bits of CSI part 1 bits (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 13.INTEGER(0..31) OPTIONAL, -- Need SbetaOffsetCSI-Part1-Index2Above 11 bits of CSI part 1 bits (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 13.INTEGER(0..31) OPTIONAL, -- Need SbetaOffsetCSI-Part2-Index1Up to 11 bits of CSI part 2 bits (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 13.INTEGER(0..31) OPTIONAL, -- Need SbetaOffsetCSI-Part2-Index2Above 11 bits of CSI part 2 bits (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 13.INTEGER(0..31) OPTIONAL -- Need S } -- TAG-BETAOFFSETS-STOP -- ASN1STOP
BetaOffsets field descriptions |
---|
betaOffsetACK-Index1 Up to 2 bits HARQ-ACK (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 11. |
betaOffsetACK-Index2 Up to 11 bits HARQ-ACK (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 11. |
betaOffsetACK-Index3 Above 11 bits HARQ-ACK (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 11. |
betaOffsetCSI-Part1-Index1 Up to 11 bits of CSI part 1 bits (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 13. |
betaOffsetCSI-Part1-Index2 Above 11 bits of CSI part 1 bits (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 13. |
betaOffsetCSI-Part2-Index1 Up to 11 bits of CSI part 2 bits (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 13. |
betaOffsetCSI-Part2-Index2 Above 11 bits of CSI part 2 bits (see TS 38.213 [13], clause 9.3). When the field is absent the UE applies the value 13. |
The IE BH-LogicalChannelIdentity is used to identify a logical channel between an IAB-node and its parent IAB-node or IAB-donor-DU.
-- ASN1START -- TAG-BHLOGICALCHANNELIDENTITY-START BH-LogicalChannelIdentity-r16 ::= CHOICE { bh-LogicalChannelIdentity-r16 LogicalChannelIdentity, bh-LogicalChannelIdentityExt-r16 BH-LogicalChannelIdentity-Ext-r16 } -- TAG-BHLOGICALCHANNELIDENTITY-STOP -- ASN1STOP
The IE BH-LogicalChannelIdentity-Ext is used to identify a logical channel between an IAB-node and its parent node.
BH-LogicalChannelIdentityfield descriptions |
---|
bh-LogicalChannelIdentity ID used for the MAC logical channel. |
bh-LogicalChannelIdentityExt ID used for the MAC logical channel. |
The IE BH-RLC-ChannelConfig is used to configure an RLC entity, a corresponding logical channel in MAC for BH RLC channel between IAB-node and its parent node.
-- ASN1START -- TAG-BHRLCCHANNELCONFIG-START BH-RLC-ChannelConfig-r16::= SEQUENCE { bh-LogicalChannelIdentity-r16 BH-LogicalChannelIdentity-r16 OPTIONAL, -- Cond LCH-SetupOnly bh-RLC-ChannelID-r16 BH-RLC-ChannelID-r16, reestablishRLC-r16 ENUMERATED {true} OPTIONAL, -- Need N rlc-Config-r16 RLC-Config OPTIONAL, -- Cond LCH-Setup mac-LogicalChannelConfig-r16 LogicalChannelConfig OPTIONAL, -- Cond LCH-Setup ... } -- TAG-BHRLCCHANNELCONFIG-STOP -- ASN1STOP
The IE BH-RLC-ChannelID is used to identify a BH RLC channel in the link between IAB-MT of the IAB-node and IAB-DU of the parent IAB-node or IAB-donor-DU.
BH-RLC-ChannelConfigfield descriptions |
---|
bh-LogicalChannelIdentity Indicates the logical channel id for BH RLC channel of the IAB-node. |
bh-RLC-ChannelID Indicates the BH RLC channel in the link between IAB-MT of the IAB-node and IAB-DU of the parent IAB-nodeor IAB-donor-DU. |
reestablishRLC Indicates that RLC should be re-established. |
rlc-Config Determines the RLC mode (UM, AM) and provides corresponding parameters. |
Conditional Presence | Explanation |
---|---|
LCH-Setup | This field is mandatory present upon creation of a new logical channel for a BH RLC channel. It is optionally present, Need M, otherwise. |
LCH-SetupOnly | This field is mandatory present upon creation of a new logical channel for aBH RLC channel. It is absent, Need M otherwise. |
The IE BSR-Config is used to configure buffer status reporting.
-- ASN1START -- TAG-BSR-CONFIG-START BSR-Config ::= SEQUENCE {periodicBSR-TimerValue in number of subframes. Value sf1 corresponds to 1 subframe, value sf5 corresponds to 5 subframes and so on.ENUMERATED { sf1, sf5, sf10, sf16, sf20, sf32, sf40, sf64, sf80, sf128, sf160, sf320, sf640, sf1280, sf2560, infinity },retxBSR-TimerValue in number of subframes. Value sf10 corresponds to 10 subframes, value sf20 corresponds to 20 subframes and so on.ENUMERATED { sf10, sf20, sf40, sf80, sf160, sf320, sf640, sf1280, sf2560, sf5120, sf10240, spare5, spare4, spare3, spare2, spare1},logicalChannelSR-DelayTimerValue in number of subframes. Value sf20 corresponds to 20 subframes, sf40 corresponds to 40 subframes, and so on.ENUMERATED { sf20, sf40, sf64, sf128, sf512, sf1024, sf2560, spare1} OPTIONAL, -- Need R ... } -- TAG-BSR-CONFIG-STOP -- ASN1STOP
BSR-Config field descriptions |
---|
logicalChannelSR-DelayTimer Value in number of subframes. Value sf20 corresponds to 20 subframes, sf40 corresponds to 40 subframes, and so on. |
periodicBSR-Timer Value in number of subframes. Value sf1 corresponds to 1 subframe, value sf5 corresponds to 5 subframes and so on. |
retxBSR-Timer Value in number of subframes. Value sf10 corresponds to 10 subframes, value sf20 corresponds to 20 subframes and so on. |
The IE BWP is used to configure generic parameters of a bandwidth part as defined in TS 38.211 [16], clause 4.5, and TS 38.213 [13], clause 12. For each serving cell the network configures at least an initial downlink bandwidth part and one (if the serving cell is configured with an uplink) or two (if using supplementary uplink (SUL)) initial uplink bandwidth parts. Furthermore, the network may configure additional uplink and downlink bandwidth parts for a serving cell. The uplink and downlink bandwidth part configurations are divided into common and dedicated parameters.
-- ASN1START -- TAG-BWP-START BWP ::= SEQUENCE {locationAndBandwidthFrequency domain location and bandwidth of this bandwidth part. The value of the field shall be interpreted as resource indicator value (RIV) as defined TS 38.214 [19] with assumptions as described in TS 38.213 [13], clause 12, i.e. setting =275. The first PRB is a PRB determined by subcarrierSpacing of this BWP and offsetToCarrier (configured in SCS-SpecificCarrier contained within FrequencyInfoDL / FrequencyInfoUL / FrequencyInfoUL-SIB / FrequencyInfoDL-SIB within ServingCellConfigCommon / ServingCellConfigCommonSIB) corresponding to this subcarrier spacing. In case of TDD, a BWP-pair (UL BWP and DL BWP with the same bwp-Id) must have the same center frequency (see TS 38.213 [13], clause 12)INTEGER (0..37949),subcarrierSpacingSubcarrier spacing to be used in this BWP for all channels and reference signals unless explicitly configured elsewhere. Corresponds to subcarrier spacing according to TS 38.211 [16], table 4.2-1. The value kHz15 corresponds to µ=0, value kHz30 corresponds to µ=1, and so on. Only the values 15 kHz, 30 kHz, or 60 kHz (FR1), and 60 kHz or 120 kHz (FR2) are applicable. For the initial DL BWP and operation in licensed spectrum this field has the same value as the field subCarrierSpacingCommon in MIB of the same serving cell. Except for SUL, the network ensures the same subcarrier spacing is used in active DL BWP and active UL BWP within a serving cell. For the initial DL BWP and operation with shared spectrum channel access, the value of this field corresponds to the subcarrier spacing of the SSB associated to the initial DL BWP.SubcarrierSpacing,cyclicPrefixIndicates whether to use the extended cyclic prefix for this bandwidth part. If not set, the UE uses the normal cyclic prefix. Normal CP is supported for all subcarrier spacings and slot formats. Extended CP is supported only for 60 kHz subcarrier spacing. (see TS 38.211 [16], clause 4.2). Except for SUL, the network ensures the same cyclic prefix length is used in active DL BWP and active UL BWP within a serving cell.ENUMERATED { extended } OPTIONAL -- Need R } -- TAG-BWP-STOP -- ASN1STOP
BWP field descriptions |
---|
cyclicPrefix Indicates whether to use the extended cyclic prefix for this bandwidth part. If not set, the UE uses the normal cyclic prefix. Normal CP is supported for all subcarrier spacings and slot formats. Extended CP is supported only for 60 kHz subcarrier spacing. (see TS 38.211 [16], clause 4.2). Except for SUL, the network ensures the same cyclic prefix length is used in active DL BWP and active UL BWP within a serving cell. |
locationAndBandwidth Frequency domain location and bandwidth of this bandwidth part. The value of the field shall be interpreted as resource indicator value (RIV) as defined TS 38.214 [19] with assumptions as described in TS 38.213 [13], clause 12, i.e. setting =275. The first PRB is a PRB determined by subcarrierSpacing of this BWP and offsetToCarrier (configured in SCS-SpecificCarrier contained within FrequencyInfoDL / FrequencyInfoUL / FrequencyInfoUL-SIB / FrequencyInfoDL-SIB within ServingCellConfigCommon / ServingCellConfigCommonSIB) corresponding to this subcarrier spacing. In case of TDD, a BWP-pair (UL BWP and DL BWP with the same bwp-Id) must have the same center frequency (see TS 38.213 [13], clause 12) |
subcarrierSpacing Subcarrier spacing to be used in this BWP for all channels and reference signals unless explicitly configured elsewhere. Corresponds to subcarrier spacing according to TS 38.211 [16], table 4.2-1. The value kHz15 corresponds to µ=0, value kHz30 corresponds to µ=1, and so on. Only the values 15 kHz, 30 kHz, or 60 kHz (FR1), and 60 kHz or 120 kHz (FR2) are applicable. For the initial DL BWP and operation in licensed spectrum this field has the same value as the field subCarrierSpacingCommon in MIB of the same serving cell. Except for SUL, the network ensures the same subcarrier spacing is used in active DL BWP and active UL BWP within a serving cell. For the initial DL BWP and operation with shared spectrum channel access, the value of this field corresponds to the subcarrier spacing of the SSB associated to the initial DL BWP. |
The IE BWP-Downlink is used to configure an additional downlink bandwidth part (not for the initial BWP).
-- ASN1START -- TAG-BWP-DOWNLINK-START BWP-Downlink ::= SEQUENCE {bwp-IdAn identifier for this bandwidth part. Other parts of the RRC configuration use the BWP-Id to associate themselves with a particular bandwidth part. The network configures the BWPs with consecutive IDs from 1. The Network does not include the value 0, since value 0 is reserved for the initial BWP.BWP-Id, bwp-Common BWP-DownlinkCommon OPTIONAL, -- Cond SetupOtherBWP bwp-Dedicated BWP-DownlinkDedicated OPTIONAL, -- Cond SetupOtherBWP ... } -- TAG-BWP-DOWNLINK-STOP -- ASN1STOP
BWP-Downlink field descriptions |
---|
bwp-Id An identifier for this bandwidth part. Other parts of the RRC configuration use the BWP-Id to associate themselves with a particular bandwidth part. The network configures the BWPs with consecutive IDs from 1. The Network does not include the value 0, since value 0 is reserved for the initial BWP. |
Conditional Presence | Explanation |
---|---|
SetupOtherBWP | The field is mandatory present upon configuration of a new DL BWP. The field is optionally present, Need M, otherwise. |
The IE BWP-DownlinkCommon is used to configure the common parameters of a downlink BWP. They are "cell specific" and the network ensures the necessary alignment with corresponding parameters of other UEs. The common parameters of the initial bandwidth part of the PCell are also provided via system information. For all other serving cells, the network provides the common parameters via dedicated signalling.
-- ASN1START -- TAG-BWP-DOWNLINKCOMMON-START BWP-DownlinkCommon ::= SEQUENCE { genericParameters BWP,pdcch-ConfigCommonCell specific parameters for the PDCCH of this BWP. This field is absent for a dormant BWP.SetupRelease { PDCCH-ConfigCommon } OPTIONAL, -- Need Mpdsch-ConfigCommonCell specific parameters for the PDSCH of this BWP.SetupRelease { PDSCH-ConfigCommon } OPTIONAL, -- Need M ... } -- TAG-BWP-DOWNLINKCOMMON-STOP -- ASN1STOP
BWP-DownlinkCommon field descriptions |
---|
pdcch-ConfigCommon Cell specific parameters for the PDCCH of this BWP. This field is absent for a dormant BWP. |
pdsch-ConfigCommon Cell specific parameters for the PDSCH of this BWP. |
The IE BWP-DownlinkDedicated is used to configure the dedicated (UE specific) parameters of a downlink BWP.
-- ASN1START -- TAG-BWP-DOWNLINKDEDICATED-START BWP-DownlinkDedicated ::= SEQUENCE {pdcch-ConfigUE specific PDCCH configuration for one BWP.SetupRelease { PDCCH-Config } OPTIONAL, -- Need Mpdsch-ConfigUE specific PDSCH configuration for one BWP.SetupRelease { PDSCH-Config } OPTIONAL, -- Need Msps-ConfigUE specific SPS (Semi-Persistent Scheduling) configuration for one BWP. Except for reconfiguration with sync, the NW does not reconfigure sps-Config when there is an active configured downlink assignment (see TS 38.321 [3]). However, the NW may release the sps-Config at any time. Network can only configure SPS in one BWP using either this field or sps-ConfigToAddModList.SetupRelease { SPS-Config } OPTIONAL, -- Need MradioLinkMonitoringConfigUE specific configuration of radio link monitoring for detecting cell- and beam radio link failure occasions.The maximum number of failure detection resources should be limited up to 8 for both cell and beam radio link failure detection. For SCells, only periodic 1-port CSI-RS can be configured in IE RadioLinkMonitoringConfig.SetupRelease { RadioLinkMonitoringConfig } OPTIONAL, -- Need M ..., [[sps-ConfigToAddModList-r16Indicates a list of one or more DL SPS configurations to be added or modified in one BWP. Except for reconfiguration with sync, the NW does not reconfigure a SPS configuration when it is active (see TS 38.321 [3]).SPS-ConfigToAddModList-r16 OPTIONAL, -- Need Nsps-ConfigToReleaseList-r16Indicates a list of one or more DL SPS configurations to be released. The NW may release a SPS configuration at any time.SPS-ConfigToReleaseList-r16 OPTIONAL, -- Need Nsps-ConfigDeactivationStateList-r16Indicates a list of the deactivation states in which each state can be mapped to a single or multiple SPS configurations to be deactivated, see clause 10.2 in TS 38.213 [13]. If a state is mapped to multiple SPS configurations, each of these SPS configurations is configured with the same harq-CodebookID.SPS-ConfigDeactivationStateList-r16 OPTIONAL, -- Need RbeamFailureRecoverySCellConfig-r16Configuration of candidate RS for beam failure recovery in SCells.SetupRelease {BeamFailureRecoverySCellConfig-r16} OPTIONAL, -- Cond SCellOnlysl-PDCCH-Config-r16Indicates the UE specific PDCCH configurations for receiving the SL grants (via SL-RNTI or SL-CS-RNTI) for NR sidelink communication.SetupRelease { PDCCH-Config } OPTIONAL, -- Need Msl-V2X-PDCCH-Config-r16Indicates the UE specific PDCCH configurations for receiving SL grants (i.e. sidelink SPS) for V2X sidelink communication.SetupRelease { PDCCH-Config } OPTIONAL -- Need M ]] } SPS-ConfigToAddModList-r16 ::= SEQUENCE (SIZE (1..maxNrofSPS-Config-r16)) OF SPS-Config SPS-ConfigToReleaseList-r16 ::= SEQUENCE (SIZE (1..maxNrofSPS-Config-r16)) OF SPS-ConfigIndex-r16 SPS-ConfigDeactivationState-r16 ::= SEQUENCE (SIZE (1..maxNrofSPS-Config-r16)) OF SPS-ConfigIndex-r16 SPS-ConfigDeactivationStateList-r16 ::= SEQUENCE (SIZE (1..maxNrofSPS-DeactivationState)) OF SPS-ConfigDeactivationState-r16 -- TAG-BWP-DOWNLINKDEDICATED-STOP -- ASN1STOP
BWP-DownlinkDedicated field descriptions |
---|
beamFailureRecoverySCellConfig Configuration of candidate RS for beam failure recovery in SCells. |
pdcch-Config UE specific PDCCH configuration for one BWP. |
pdsch-Config UE specific PDSCH configuration for one BWP. |
sps-Config UE specific SPS (Semi-Persistent Scheduling) configuration for one BWP. Except for reconfiguration with sync, the NW does not reconfigure sps-Config when there is an active configured downlink assignment (see TS 38.321 [3]). However, the NW may release the sps-Config at any time. Network can only configure SPS in one BWP using either this field or sps-ConfigToAddModList. |
sps-ConfigDeactivationStateList Indicates a list of the deactivation states in which each state can be mapped to a single or multiple SPS configurations to be deactivated, see clause 10.2 in TS 38.213 [13]. If a state is mapped to multiple SPS configurations, each of these SPS configurations is configured with the same harq-CodebookID. |
sps-ConfigToAddModList Indicates a list of one or more DL SPS configurations to be added or modified in one BWP. Except for reconfiguration with sync, the NW does not reconfigure a SPS configuration when it is active (see TS 38.321 [3]). |
sps-ConfigToReleaseList Indicates a list of one or more DL SPS configurations to be released. The NW may release a SPS configuration at any time. |
radioLinkMonitoringConfig UE specific configuration of radio link monitoring for detecting cell- and beam radio link failure occasions.The maximum number of failure detection resources should be limited up to 8 for both cell and beam radio link failure detection. For SCells, only periodic 1-port CSI-RS can be configured in IE RadioLinkMonitoringConfig. |
sl-PDCCH-Config Indicates the UE specific PDCCH configurations for receiving the SL grants (via SL-RNTI or SL-CS-RNTI) for NR sidelink communication. |
sl-V2X-PDCCH-Config Indicates the UE specific PDCCH configurations for receiving SL grants (i.e. sidelink SPS) for V2X sidelink communication. |
Conditional Presence | Explanation |
---|---|
ScellOnly | The field is optionally present, Need M, in the BWP-DownlinkDedicated of an Scell. It is absent otherwise. |
The IE BWP-Id is used to refer to Bandwidth Parts (BWP). The initial BWP is referred to by BWP-Id 0. The other BWPs are referred to by BWP-Id 1 to maxNrofBWPs.
The IE BWP-Uplink is used to configure an additional uplink bandwidth part (not for the initial BWP).
-- ASN1START -- TAG-BWP-UPLINK-START BWP-Uplink ::= SEQUENCE {bwp-IdAn identifier for this bandwidth part. Other parts of the RRC configuration use the BWP-Id to associate themselves with a particular bandwidth part. The network configures the BWPs with consecutive IDs from 1. The Network does not include the value 0, since value 0 is reserved for the initial BWP.BWP-Id, bwp-Common BWP-UplinkCommon OPTIONAL, -- Cond SetupOtherBWP bwp-Dedicated BWP-UplinkDedicated OPTIONAL, -- Cond SetupOtherBWP ... } -- TAG-BWP-UPLINK-STOP -- ASN1STOP
BWP-Uplink field descriptions |
---|
bwp-Id An identifier for this bandwidth part. Other parts of the RRC configuration use the BWP-Id to associate themselves with a particular bandwidth part. The network configures the BWPs with consecutive IDs from 1. The Network does not include the value 0, since value 0 is reserved for the initial BWP. |
Conditional Presence | Explanation |
---|---|
SetupOtherBWP | The field is mandatory present upon configuration of a new UL BWP. The field is optionally present, Need M, otherwise. |
The IE BWP-UplinkCommon is used to configure the common parameters of an uplink BWP. They are "cell specific" and the network ensures the necessary alignment with corresponding parameters of other UEs. The common parameters of the initial bandwidth part of the PCell are also provided via system information. For all other serving cells, the network provides the common parameters via dedicated signalling.
-- ASN1START -- TAG-BWP-UPLINKCOMMON-START BWP-UplinkCommon ::= SEQUENCE { genericParameters BWP,rach-ConfigCommonConfiguration of cell specific random access parameters which the UE uses for contention based and contention free random access as well as for contention based beam failure recovery in this BWP. The NW configures SSB-based RA (and hence RACH-ConfigCommon) only for UL BWPs if the linked DL BWPs (same bwp-Id as UL-BWP) are the initial DL BWPs or DL BWPs containing the SSB associated to the initial DL BWP. The network configures rach-ConfigCommon, whenever it configures contention free random access (for reconfiguration with sync or for beam failure recovery).SetupRelease { RACH-ConfigCommon } OPTIONAL, -- Need Mpusch-ConfigCommonCell specific parameters for the PUSCH of this BWP.SetupRelease { PUSCH-ConfigCommon } OPTIONAL, -- Need Mpucch-ConfigCommonCell specific parameters for the PUCCH of this BWP.SetupRelease { PUCCH-ConfigCommon } OPTIONAL, -- Need M ..., [[rach-ConfigCommonIAB-r16Configuration of cell specific random access parameters for the IAB-MT. The IAB specific IAB RACH configuration is used by IAB-MT, if configured.SetupRelease { RACH-ConfigCommon } OPTIONAL, -- Need MuseInterlacePUCCH-PUSCH-r16If the field is present, the UE uses uplink frequency domain resource allocation Type 2 for cell-specific PUSCH, e.g., PUSCH scheduled by RAR UL grant (see TS 38.213 [13], clause 8.3 and TS 38.214 [19], clause 6.1.2.2) and uses interlaced PUCCH Format 0 and 1 for cell-specific PUCCH (see TS 38.213 [13], clause 9.2.1).ENUMERATED {enabled} OPTIONAL, -- Need RmsgA-ConfigCommon-r16Configuration of the cell specific PRACH and PUSCH resource parameters for transmission of MsgA in 2-step random access type procedure. The NW can configuremsgA-ConfigCommononly for UL BWPs if the linked DL BWPs (same bwp-Id as UL-BWP) are the initial DL BWPs or DL BWPs containing the SSB associated to the initial BL BWPSetupRelease { MsgA-ConfigCommon-r16 } OPTIONAL -- Cond SpCellOnly2 ]] } -- TAG-BWP-UPLINKCOMMON-STOP -- ASN1STOP
BWP-UplinkCommon field descriptions |
---|
msgA-ConfigCommon Configuration of the cell specific PRACH and PUSCH resource parameters for transmission of MsgA in 2-step random access type procedure. The NW can configuremsgA-ConfigCommononly for UL BWPs if the linked DL BWPs (same bwp-Id as UL-BWP) are the initial DL BWPs or DL BWPs containing the SSB associated to the initial BL BWP |
pucch-ConfigCommon Cell specific parameters for the PUCCH of this BWP. |
pusch-ConfigCommon Cell specific parameters for the PUSCH of this BWP. |
rach-ConfigCommon Configuration of cell specific random access parameters which the UE uses for contention based and contention free random access as well as for contention based beam failure recovery in this BWP. The NW configures SSB-based RA (and hence RACH-ConfigCommon) only for UL BWPs if the linked DL BWPs (same bwp-Id as UL-BWP) are the initial DL BWPs or DL BWPs containing the SSB associated to the initial DL BWP. The network configures rach-ConfigCommon, whenever it configures contention free random access (for reconfiguration with sync or for beam failure recovery). |
rach-ConfigCommonIAB Configuration of cell specific random access parameters for the IAB-MT. The IAB specific IAB RACH configuration is used by IAB-MT, if configured. |
useInterlacePUCCH-PUSCH If the field is present, the UE uses uplink frequency domain resource allocation Type 2 for cell-specific PUSCH, e.g., PUSCH scheduled by RAR UL grant (see TS 38.213 [13], clause 8.3 and TS 38.214 [19], clause 6.1.2.2) and uses interlaced PUCCH Format 0 and 1 for cell-specific PUCCH (see TS 38.213 [13], clause 9.2.1). |
Conditional Presence | Explanation |
---|---|
SpCellOnly2 | The field is optionally present, Need M, in the BWP-UplinkCommon of an SpCell. It is absent otherwise. |
The IE BWP-UplinkDedicated is used to configure the dedicated (UE specific) parameters of an uplink BWP.
-- ASN1START -- TAG-BWP-UPLINKDEDICATED-START BWP-UplinkDedicated ::= SEQUENCE {pucch-ConfigPUCCH configuration for one BWP of the normal UL or SUL of a serving cell. If the UE is configured with SUL, the network configures PUCCH only on the BWPs of one of the uplinks (normal UL or SUL). The network configures PUCCH-Config at least on non-initial BWP(s) for SpCell and on all BWP(s) for PUCCH SCell. If supported by the UE, the network may configure at most one additional SCell of a cell group with PUCCH-Config (i.e. PUCCH SCell). In (NG)EN-DC and NE-DC, the NW configures at most one serving cell per frequency range with PUCCH. In (NG)EN-DC and NE-DC, if two PUCCH groups are configured, the serving cells of the NR PUCCH group in FR2 use the same numerology. For NR-DC, the maximum number of PUCCH groups in each cell group is one, and only the same numerology is supported for the cell group with carriers only in FR2. The NW may configure PUCCH for a BWP when setting up the BWP. The network may also add/remove the pucch-Config in an RRCReconfiguration with reconfigurationWithSync (for SpCell or PUCCH SCell) or with SCell release and add (for PUCCH SCell) to move the PUCCH between the UL and SUL carrier of one serving cell. In other cases, only modifications of a previously configured pucch-Config are allowed. If one (S)UL BWP of a serving cell is configured with PUCCH, all other (S)UL BWPs must be configured with PUCCH, too.SetupRelease { PUCCH-Config } OPTIONAL, -- Need Mpusch-ConfigPUSCH configuration for one BWP of the normal UL or SUL of a serving cell. If the UE is configured with SUL and if it has a PUSCH-Config for both UL and SUL, an UL/SUL indicator field in DCI indicates which of the two to use. See TS 38.212 [17], clause 7.3.1.SetupRelease { PUSCH-Config } OPTIONAL, -- Need MconfiguredGrantConfigA Configured-Grant of type1 or type2. It may be configured for UL or SUL but in case of type1 not for both at a time. Except for reconfiguration with sync, the NW does not reconfigure configuredGrantConfigwhen there is an active configured uplink grant Type 2 (see TS 38.321 [3]). However, the NW may release the configuredGrantConfigat any time.Network can only configure configured grant in one BWP using either this field or configuredGrantConfigToAddModList.SetupRelease { ConfiguredGrantConfig } OPTIONAL, -- Need Msrs-ConfigUplink sounding reference signal configuration.SetupRelease { SRS-Config } OPTIONAL, -- Need MbeamFailureRecoveryConfigConfiguration of beam failure recovery. If supplementaryUplink is present, the field is present only in one of the uplink carriers, either UL or SUL.SetupRelease { BeamFailureRecoveryConfig } OPTIONAL, -- Cond SpCellOnly ..., [[sl-PUCCH-Config-r16Indicates the UE specific PUCCH configurations used for the HARQ-ACK feedback reporting for NR sidelink communication.SetupRelease { PUCCH-Config } OPTIONAL, -- Need M cp-ExtensionC2-r16 INTEGER (1..28) OPTIONAL, -- Need R cp-ExtensionC3-r16 INTEGER (1..28) OPTIONAL, -- Need RuseInterlacePUCCH-PUSCH-r16If the field is present, the UE uses uplink frequency domain resource allocation Type 2 for PUSCH (see TS 38.213 [13], clause 8.3 and TS 38.214 [19], clause 6.1.2.2) and uses interlaced PUCCH Format 0, 1, 2, and 3 for PUCCH (see TS 38.213 [13], clause 9.2.1).ENUMERATED {enabled} OPTIONAL, -- Need Rpucch-ConfigurationList-r16PUCCH configurations for two simultaneously constructed HARQ-ACK codebooks (see TS 38.213 [13], clause 9.1). Different PUCCH Resource IDs are configured in different PUCCH-Config within the pucch-ConfigurationList if configured.SetupRelease { PUCCH-ConfigurationList-r16 } OPTIONAL, -- Need Mlbt-FailureRecoveryConfig-r16Configures parameters used for detection of consistent uplink LBT failures for operationwith shared spectrum channel access, as specified in TS 38.321 [3].SetupRelease { LBT-FailureRecoveryConfig-r16 } OPTIONAL, -- Need MconfiguredGrantConfigToAddModList-r16Indicates a list of one or more configured grant configurations to be added or modified for one BWP. Except for reconfiguration with sync, the NW does not reconfigure a Type 2 configured grant configuration when it is active (see TS 38.321 [3]).ConfiguredGrantConfigToAddModList-r16 OPTIONAL, -- Need NconfiguredGrantConfigToReleaseList-r16Indicates a list of one or more UL Configured Grant configurations to be released. The NW may release a configured grant configuration at any time.ConfiguredGrantConfigToReleaseList-r16 OPTIONAL, -- Need NconfiguredGrantConfigType2DeactivationStateList-r16Indicates a list of the deactivation states in which each state can be mapped to a single or multiple Configured Grant type 2 configurations to be deactivated when the corresponding deactivation DCI is received, see clause 7.3.1 in TS 38.212 [17] and clause 10.2 in TS 38.213 [13].ConfiguredGrantConfigType2DeactivationStateList-r16 OPTIONAL -- Need R ]] } ConfiguredGrantConfigToAddModList-r16 ::= SEQUENCE (SIZE (1..maxNrofConfiguredGrantConfig-r16)) OF ConfiguredGrantConfig ConfiguredGrantConfigToReleaseList-r16 ::= SEQUENCE (SIZE (1..maxNrofConfiguredGrantConfig-r16)) OF ConfiguredGrantConfigIndex-r16 ConfiguredGrantConfigType2DeactivationState-r16 ::= SEQUENCE (SIZE (1..maxNrofConfiguredGrantConfig-r16)) OF ConfiguredGrantConfigIndex-r16 ConfiguredGrantConfigType2DeactivationStateList-r16 ::= SEQUENCE (SIZE (1..maxNrofCG-Type2DeactivationState)) OF ConfiguredGrantConfigType2DeactivationState-r16 -- TAG-BWP-UPLINKDEDICATED-STOP -- ASN1STOP
BWP-UplinkDedicated field descriptions |
---|
beamFailureRecoveryConfig Configuration of beam failure recovery. If supplementaryUplink is present, the field is present only in one of the uplink carriers, either UL or SUL. |
configuredGrantConfig A Configured-Grant of type1 or type2. It may be configured for UL or SUL but in case of type1 not for both at a time. Except for reconfiguration with sync, the NW does not reconfigure configuredGrantConfigwhen there is an active configured uplink grant Type 2 (see TS 38.321 [3]). However, the NW may release the configuredGrantConfigat any time.Network can only configure configured grant in one BWP using either this field or configuredGrantConfigToAddModList. |
configuredGrantConfigToAddModList Indicates a list of one or more configured grant configurations to be added or modified for one BWP. Except for reconfiguration with sync, the NW does not reconfigure a Type 2 configured grant configuration when it is active (see TS 38.321 [3]). |
configuredGrantConfigToReleaseList Indicates a list of one or more UL Configured Grant configurations to be released. The NW may release a configured grant configuration at any time. |
configuredGrantConfigType2DeactivationStateList Indicates a list of the deactivation states in which each state can be mapped to a single or multiple Configured Grant type 2 configurations to be deactivated when the corresponding deactivation DCI is received, see clause 7.3.1 in TS 38.212 [17] and clause 10.2 in TS 38.213 [13]. |
cp-ExtensionC2, cp-ExtensionC3 Configures the cyclic prefix (CP) extension (see TS 38.211 [16], clause 5.3.1). For 15 kHz SCS, {1..28} are validfor both cp-ExtensionC2 and cp-ExtensionC3. For 30 kHz SCS, {1..28} are valid for cp-ExtensionC2 and {2..28} are valid for cp-ExtensionC3.For 60 kHz SCS, {2..28} are validfor cp-ExtensionC2 and {3..28} are valid for cp-ExtensionC3. |
lbt-FailureRecoveryConfig Configures parameters used for detection of consistent uplink LBT failures for operationwith shared spectrum channel access, as specified in TS 38.321 [3]. |
pucch-Config PUCCH configuration for one BWP of the normal UL or SUL of a serving cell. If the UE is configured with SUL, the network configures PUCCH only on the BWPs of one of the uplinks (normal UL or SUL). The network configures PUCCH-Config at least on non-initial BWP(s) for SpCell and on all BWP(s) for PUCCH SCell. If supported by the UE, the network may configure at most one additional SCell of a cell group with PUCCH-Config (i.e. PUCCH SCell). In (NG)EN-DC and NE-DC, the NW configures at most one serving cell per frequency range with PUCCH. In (NG)EN-DC and NE-DC, if two PUCCH groups are configured, the serving cells of the NR PUCCH group in FR2 use the same numerology. For NR-DC, the maximum number of PUCCH groups in each cell group is one, and only the same numerology is supported for the cell group with carriers only in FR2. The NW may configure PUCCH for a BWP when setting up the BWP. The network may also add/remove the pucch-Config in an RRCReconfiguration with reconfigurationWithSync (for SpCell or PUCCH SCell) or with SCell release and add (for PUCCH SCell) to move the PUCCH between the UL and SUL carrier of one serving cell. In other cases, only modifications of a previously configured pucch-Config are allowed. If one (S)UL BWP of a serving cell is configured with PUCCH, all other (S)UL BWPs must be configured with PUCCH, too. |
pucch-ConfigurationList PUCCH configurations for two simultaneously constructed HARQ-ACK codebooks (see TS 38.213 [13], clause 9.1). Different PUCCH Resource IDs are configured in different PUCCH-Config within the pucch-ConfigurationList if configured. |
pusch-Config PUSCH configuration for one BWP of the normal UL or SUL of a serving cell. If the UE is configured with SUL and if it has a PUSCH-Config for both UL and SUL, an UL/SUL indicator field in DCI indicates which of the two to use. See TS 38.212 [17], clause 7.3.1. |
sl-PUCCH-Config Indicates the UE specific PUCCH configurations used for the HARQ-ACK feedback reporting for NR sidelink communication. |
srs-Config Uplink sounding reference signal configuration. |
useInterlacePUCCH-PUSCH If the field is present, the UE uses uplink frequency domain resource allocation Type 2 for PUSCH (see TS 38.213 [13], clause 8.3 and TS 38.214 [19], clause 6.1.2.2) and uses interlaced PUCCH Format 0, 1, 2, and 3 for PUCCH (see TS 38.213 [13], clause 9.2.1). |
Conditional Presence | Explanation |
---|---|
SpCellOnly | The field is optionally present, Need M, in the BWP-UplinkDedicated of an SpCell. It is absent otherwise. |
The IE CellAccessRelatedInfo indicates cell access related information for this cell.
-- ASN1START -- TAG-CELLACCESSRELATEDINFO-START CellAccessRelatedInfo ::= SEQUENCE {plmn-IdentityInfoListThe plmn-IdentityInfoList is used to configure a set of PLMN-IdentityInfo elements. Each of those elements contains a list of one or more PLMN Identities and additional information associated with those PLMNs. A PLMN-identity can be included only once, and in only one entry of the PLMN-IdentityInfoList. The PLMN index is defined as b1+b2+…+b(n-1)+i for the PLMN included at the n-th entry of PLMN-IdentityInfoList and the i-th entry of its corresponding PLMN-IdentityInfo, where b(j) is the number of PLMN-Identity entries in each PLMN-IdentityInfo, respectively.PLMN-IdentityInfoList,cellReservedForOtherUseIndicates whether the cell is reserved, as defined in 38.304 [20]. The field is applicable to all PLMNs.This field is ignored by IAB-MT for cell barring determination, but still considered by NPN capable IAB-MT for determination of an NPN-only cell.ENUMERATED {true} OPTIONAL, -- Need R ..., [[cellReservedForFutureUse-r16Indicates whether the cell is reserved, as defined in 38.304 [20] for future use. The field is applicable to all PLMNs and NPNs.This field is ignored by IAB-MT.ENUMERATED {true} OPTIONAL, -- Need Rnpn-IdentityInfoList-r16The npn-IdentityInfoList is used to configure a set of NPN-IdentityInfo elements. Each of those elements contains a list of one or more NPN Identities and additional information associated with those NPNs. The total number of PLMNs (identified by a PLMN identity in plmn -IdentityList), PNI-NPNs (identified by a PLMN identity and a CAG-ID), and SNPNs (identified by a PLMN identity and a NID) together in the PLMN-IdentityInfoList and NPN-IdentityInfoList does not exceed 12, except for the NPN-only cells. A PNI-NPN and SNPN can be included only once, and in only one entry of the NPN-IdentityInfoList. In case of NPN-only cells the PLMN-IdentityList contains a single element that does not count to the limit of 12 and the cellIdentity of the first entry of the PLMN-IdentityInfoList is set to the same value as the cellIdentity-r16 of the first entry of the NPN-IdentityInfoList. The NPN index is defined as B+c1+c2+…+c(n-1)+d1+d2+…+d(m-1)+e(i) for the NPN identity included in the n-th entry of NPN-IdentityInfoList and in the m-th entry of npn-Identitylist within that NPN-IdentityInfoList entry, and the i-th entry of its corresponding NPN-Identity, where - B is the index used for the last PLMN in the PLMN-IdentittyInfoList; in NPN-only cells B is considered 0; - c(j) is the number of NPN index values used in the j-th NPN-IdentityInfoList entry; - d(k) is the number of NPN index values used in the k-th npn-IdentityList entry within the n-th NPN-IdentityInfoList entry; - e(i) is - i if the n-th entry of NPN-IdentityInfoList entry is for SNPN(s); - 1 if the n-th entry of NPN-IdentityInfoList entry is for PNI-NPN(s).NPN-IdentityInfoList-r16 OPTIONAL -- Need R ]] } -- TAG-CELLACCESSRELATEDINFO-STOP -- ASN1STOP
CellAccessRelatedInfo field descriptions |
---|
cellReservedForFutureUse Indicates whether the cell is reserved, as defined in 38.304 [20] for future use. The field is applicable to all PLMNs and NPNs.This field is ignored by IAB-MT. |
cellReservedForOtherUse Indicates whether the cell is reserved, as defined in 38.304 [20]. The field is applicable to all PLMNs.This field is ignored by IAB-MT for cell barring determination, but still considered by NPN capable IAB-MT for determination of an NPN-only cell. |
npn-IdentityInfoList The npn-IdentityInfoList is used to configure a set of NPN-IdentityInfo elements. Each of those elements contains a list of one or more NPN Identities and additional information associated with those NPNs. The total number of PLMNs (identified by a PLMN identity in plmn -IdentityList), PNI-NPNs (identified by a PLMN identity and a CAG-ID), and SNPNs (identified by a PLMN identity and a NID) together in the PLMN-IdentityInfoList and NPN-IdentityInfoList does not exceed 12, except for the NPN-only cells. A PNI-NPN and SNPN can be included only once, and in only one entry of the NPN-IdentityInfoList. In case of NPN-only cells the PLMN-IdentityList contains a single element that does not count to the limit of 12 and the cellIdentity of the first entry of the PLMN-IdentityInfoList is set to the same value as the cellIdentity-r16 of the first entry of the NPN-IdentityInfoList. The NPN index is defined as B+c1+c2+…+c(n-1)+d1+d2+…+d(m-1)+e(i) for the NPN identity included in the n-th entry of NPN-IdentityInfoList and in the m-th entry of npn-Identitylist within that NPN-IdentityInfoList entry, and the i-th entry of its corresponding NPN-Identity, where - B is the index used for the last PLMN in the PLMN-IdentittyInfoList; in NPN-only cells B is considered 0; - c(j) is the number of NPN index values used in the j-th NPN-IdentityInfoList entry; - d(k) is the number of NPN index values used in the k-th npn-IdentityList entry within the n-th NPN-IdentityInfoList entry; - e(i) is - i if the n-th entry of NPN-IdentityInfoList entry is for SNPN(s); - 1 if the n-th entry of NPN-IdentityInfoList entry is for PNI-NPN(s). |
plmn-IdentityInfoList The plmn-IdentityInfoList is used to configure a set of PLMN-IdentityInfo elements. Each of those elements contains a list of one or more PLMN Identities and additional information associated with those PLMNs. A PLMN-identity can be included only once, and in only one entry of the PLMN-IdentityInfoList. The PLMN index is defined as b1+b2+…+b(n-1)+i for the PLMN included at the n-th entry of PLMN-IdentityInfoList and the i-th entry of its corresponding PLMN-IdentityInfo, where b(j) is the number of PLMN-Identity entries in each PLMN-IdentityInfo, respectively. |
The IE CellAccessRelatedInfo-EUTRA-5GC indicates cell access related information for an LTE cell connected to 5GC.
-- ASN1START -- TAG-CELLACCESSRELATEDINFOEUTRA-5GC-START CellAccessRelatedInfo-EUTRA-5GC ::= SEQUENCE { plmn-IdentityList-eutra-5gc PLMN-IdentityList-EUTRA-5GC, trackingAreaCode-eutra-5gc TrackingAreaCode, ranac-5gc RAN-AreaCode OPTIONAL, cellIdentity-eutra-5gc CellIdentity-EUTRA-5GC } PLMN-IdentityList-EUTRA-5GC::= SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-Identity-EUTRA-5GC PLMN-Identity-EUTRA-5GC ::= CHOICE { plmn-Identity-EUTRA-5GC PLMN-Identity, plmn-index INTEGER (1..maxPLMN) } CellIdentity-EUTRA-5GC ::= CHOICE { cellIdentity-EUTRA BIT STRING (SIZE (28)), cellId-index INTEGER (1..maxPLMN) } -- TAG-CELLACCESSRELATEDINFOEUTRA-5GC-STOP -- ASN1STOP
The IE CellAccessRelatedInfo-EUTRA-EPC indicates cell access related information for an LTE cell connected to EPC.
-- ASN1START -- TAG-CELLACCESSRELATEDINFOEUTRA-EPC-START CellAccessRelatedInfo-EUTRA-EPC ::= SEQUENCE { plmn-IdentityList-eutra-epc PLMN-IdentityList-EUTRA-EPC, trackingAreaCode-eutra-epc BIT STRING (SIZE (16)), cellIdentity-eutra-epc BIT STRING (SIZE (28)) } PLMN-IdentityList-EUTRA-EPC::= SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-Identity -- TAG-CELLACCESSRELATEDINFOEUTRA-EPC-STOP -- ASN1STOP
The CellGroupConfig IE is used to configure a master cell group (MCG) or secondary cell group (SCG). A cell group comprises of one MAC entity, a set of logical channels with associated RLC entities and of a primary cell (SpCell) and one or more secondary cells (SCells).
-- ASN1START -- TAG-CELLGROUPCONFIG-START -- Configuration of one Cell-Group: CellGroupConfig ::= SEQUENCE { cellGroupId CellGroupId,rlc-BearerToAddModListConfiguration of the MAC Logical Channel, the corresponding RLC entities and association with radio bearers.SEQUENCE (SIZE(1..maxLC-ID)) OF RLC-BearerConfig OPTIONAL, -- Need N rlc-BearerToReleaseList SEQUENCE (SIZE(1..maxLC-ID)) OF LogicalChannelIdentity OPTIONAL, -- Need Nmac-CellGroupConfigMAC parameters applicable for the entire cell group.MAC-CellGroupConfig OPTIONAL, -- Need M physicalCellGroupConfig PhysicalCellGroupConfig OPTIONAL, -- Need MspCellConfigParameters for the SpCell of this cell group (PCell of MCG or PSCell of SCG).SpCellConfig OPTIONAL, -- Need MsCellToAddModListList of secondary serving cells (SCells) to be added or modified.SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellConfig OPTIONAL, -- Need NsCellToReleaseListList of secondary serving cells (SCells) to be released.SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellIndex OPTIONAL, -- Need N ..., [[reportUplinkTxDirectCurrentEnables reporting of uplink and supplementary uplink Direct Current location information upon BWP configuration and reconfiguration. This field is only present when the BWP configuration is modified or any serving cell is added or removed. This field is absent in the IE CellGroupConfig when provided as part of RRCSetup message. If UE is configured with SUL carrier, UE reports both UL and SUL Direct Current locations.ENUMERATED {true} OPTIONAL -- Cond BWP-Reconfig ]], [[bap-Address-r16BAP address of the parent node in cell group.BIT STRING (SIZE (10)) OPTIONAL, -- Need Mbh-RLC-ChannelToAddModList-r16Configuration of the backhaul RLC entities and the corresponding MAC Logical Channels to be added and modified.SEQUENCE (SIZE(1..maxBH-RLC-ChannelID-r16)) OF BH-RLC-ChannelConfig-r16 OPTIONAL, -- Need Nbh-RLC-ChannelToReleaseList-r16List of the backhaul RLC entities and the corresponding MAC Logical Channels to be released.SEQUENCE (SIZE(1..maxBH-RLC-ChannelID-r16)) OF BH-RLC-ChannelID-r16 OPTIONAL, -- Need Nf1c-TransferPath-r16The F1-C transfer path that an EN-DC IAB-MT should use for transferring F1-C packets to the IAB-donor-CU. If IAB-MT is configured with lte, IAB-MT can only use LTE leg for F1-C transfer. If IAB-MT is configured with nr, IAB-MT can only use NR leg for F1-C transfer. If IAB-MT is configured with both, it is up to IAB-MT to select an LTE leg or a NR leg for F1-C transfer. If the field is not configured, the IAB node uses the NR leg as the default one.ENUMERATED {lte, nr, both} OPTIONAL, -- Need M simultaneousTCI-UpdateList1-r16 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, -- Need R simultaneousTCI-UpdateList2-r16 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, -- Need R simultaneousSpatial-UpdatedList1-r16 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, -- Need R simultaneousSpatial-UpdatedList2-r16 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, -- Need RuplinkTxSwitchingOption-r16Indicates which option is configured for dynamic UL Tx switching for inter-band UL CA or (NG)EN-DC. The field is set to switchedUL if network configures option 1 as specified in TS 38.214 [19], or dualUL if network configures option 2 as specified in TS 38.214 [19]. Network always configures UE with a value for this field in inter-band UL CA case and (NG)EN-DC case where UE supports dynamic UL Tx switching.ENUMERATED {switchedUL, dualUL} OPTIONAL, -- Need RuplinkTxSwitchingPowerBoosting-r16Indicates whether the UE is allowed to enable 3dB boosting on the maximum output power for transmission on carrier2 under the operation state in which 2-port transmission can be supported on carrier2 for inter-band UL CA case with dynamic UL Tx switching as defined in TS 38.101-1 [15]. Network can only configure this field for dynamic UL Tx switching in inter-band UL CA case with power Class 3 as defined in TS 38.101-1 [15].ENUMERATED {enabled} OPTIONAL -- Need R ]], [[reportUplinkTxDirectCurrentTwoCarrier-r16Enables reporting of uplink Direct Current location information when the UE is configured with uplink intra-band CA with two carriers. This field is absent in the IE CellGroupConfig when provided as part of RRCSetup message.ENUMERATED {true} OPTIONAL -- Need N ]] } -- Serving cell specific MAC and PHY parameters for a SpCell: SpCellConfig ::= SEQUENCE {servCellIndexServing cell ID of a PSCell. The PCell of the Master Cell Group uses ID = 0.ServCellIndex OPTIONAL, -- Cond SCGreconfigurationWithSyncParameters for the synchronous reconfiguration to the target SpCell.ReconfigurationWithSync OPTIONAL, -- Cond ReconfWithSyncrlf-TimersAndConstantsTimers and constants for detecting and triggering cell-level radio link failure. For the SCG, rlf-TimersAndConstants can only be set to setup and is always included at SCG addition.SetupRelease { RLF-TimersAndConstants } OPTIONAL, -- Need MrlmInSyncOutOfSyncThresholdBLER threshold pair index for IS/OOS indication generation, see TS 38.133 [14], table 8.1.1-1. n1 corresponds to the value 1. When the field is absent, the UE applies the value 0. Whenever this is reconfigured, UE resets N310 and N311, and stops T310, if running. Network does not include this field.ENUMERATED {n1} OPTIONAL, -- Need S spCellConfigDedicated ServingCellConfig OPTIONAL, -- Need M ... } ReconfigurationWithSync ::= SEQUENCE { spCellConfigCommon ServingCellConfigCommon OPTIONAL, -- Need M newUE-Identity RNTI-Value, t304 ENUMERATED {ms50, ms100, ms150, ms200, ms500, ms1000, ms2000, ms10000},rach-ConfigDedicatedRandom access configuration to be used for the reconfiguration with sync (e.g. handover). The UE performs the RA according to these parameters in the firstActiveUplinkBWP (see UplinkConfig).CHOICE { uplink RACH-ConfigDedicated, supplementaryUplink RACH-ConfigDedicated } OPTIONAL, -- Need N ..., [[smtcThe SSB periodicity/offset/duration configuration of target cell for NR SCell addition. The network sets the periodicityAndOffset to indicate the same periodicity as ssb-periodicityServingCell in sCellConfigCommon. The smtc is based on the timing of the SpCell of associated cell group. In case of inter-RAT handover to NR, the timing reference is the NR PCell. In case of intra-NR PCell change (standalone NR) or NR PSCell change (EN-DC), the timing reference is the target SpCell. If the field is absent, the UE uses the SMTC in the measObjectNR having the same SSB frequency and subcarrier spacing, as configured before the reception of the RRC message.SSB-MTC OPTIONAL -- Need S ]], [[ daps-UplinkPowerConfig-r16 DAPS-UplinkPowerConfig-r16 OPTIONAL -- Need N ]] } DAPS-UplinkPowerConfig-r16 ::= SEQUENCE {p-DAPS-Source-r16The maximum total transmit power to be used by the UE in the source cell group during DAPS handover.P-Max,p-DAPS-Target-r16The maximum total transmit power to be used by the UE in the target cell group during DAPS handover.P-Max,uplinkPowerSharingDAPS-Mode-r16Indicates the uplink power sharing mode that the UE uses in DAPS handover (see TS 38.213 [13]).ENUMERATED {semi-static-mode1, semi-static-mode2, dynamic } } SCellConfig ::= SEQUENCE { sCellIndex SCellIndex, sCellConfigCommon ServingCellConfigCommon OPTIONAL, -- Cond SCellAdd sCellConfigDedicated ServingCellConfig OPTIONAL, -- Cond SCellAddMod ..., [[smtcThe SSB periodicity/offset/duration configuration of target cell for NR SCell addition. The network sets the periodicityAndOffset to indicate the same periodicity as ssb-periodicityServingCell in sCellConfigCommon. The smtc is based on the timing of the SpCell of associated cell group. In case of inter-RAT handover to NR, the timing reference is the NR PCell. In case of intra-NR PCell change (standalone NR) or NR PSCell change (EN-DC), the timing reference is the target SpCell. If the field is absent, the UE uses the SMTC in the measObjectNR having the same SSB frequency and subcarrier spacing, as configured before the reception of the RRC message.SSB-MTC OPTIONAL -- Need S ]], [[sCellState-r16Indicates whether the SCell shall be considered to be in activated state upon SCell configuration.ENUMERATED {activated} OPTIONAL, -- Cond SCellAddSyncsecondaryDRX-GroupConfig-r16The field is used to indicate whether the SCell belongs to the secondary DRX group. All serving cells in the secondary DRX group shall belong to one Frequency Range and all serving cells in the legacy DRX group shall belong to another Frequency Range.If drx-ConfigSecondaryGroup is configured, the field is optionally present. The network always includes the field if the field was previously configured for this SCell and the SCell remains in the secondary DRX group. Removal of an individual SCell from the secondary DRX group is supported by using an SCell release and addition. Otherwise, if drx-ConfigSecondaryGroup is not configured, the field is absent and the UE shall release the field. The UE shall also release the field if drx-ConfigSecondaryGroup is released without including sCellToAddModList.ENUMERATED {true} OPTIONAL -- Need S ]]} -- TAG-CELLGROUPCONFIG-STOP -- ASN1STOP
CellGroupConfig field descriptions |
---|
bap-Address BAP address of the parent node in cell group. |
bh-RLC-ChannelToAddModList Configuration of the backhaul RLC entities and the corresponding MAC Logical Channels to be added and modified. |
bh-RLC-ChannelToReleaseList List of the backhaul RLC entities and the corresponding MAC Logical Channels to be released. |
f1c-TransferPath The F1-C transfer path that an EN-DC IAB-MT should use for transferring F1-C packets to the IAB-donor-CU. If IAB-MT is configured with lte, IAB-MT can only use LTE leg for F1-C transfer. If IAB-MT is configured with nr, IAB-MT can only use NR leg for F1-C transfer. If IAB-MT is configured with both, it is up to IAB-MT to select an LTE leg or a NR leg for F1-C transfer. If the field is not configured, the IAB node uses the NR leg as the default one. |
mac-CellGroupConfig MAC parameters applicable for the entire cell group. |
rlc-BearerToAddModList Configuration of the MAC Logical Channel, the corresponding RLC entities and association with radio bearers. |
reportUplinkTxDirectCurrent Enables reporting of uplink and supplementary uplink Direct Current location information upon BWP configuration and reconfiguration. This field is only present when the BWP configuration is modified or any serving cell is added or removed. This field is absent in the IE CellGroupConfig when provided as part of RRCSetup message. If UE is configured with SUL carrier, UE reports both UL and SUL Direct Current locations. |
reportUplinkTxDirectCurrentTwoCarrier Enables reporting of uplink Direct Current location information when the UE is configured with uplink intra-band CA with two carriers. This field is absent in the IE CellGroupConfig when provided as part of RRCSetup message. |
rlmInSyncOutOfSyncThreshold BLER threshold pair index for IS/OOS indication generation, see TS 38.133 [14], table 8.1.1-1. n1 corresponds to the value 1. When the field is absent, the UE applies the value 0. Whenever this is reconfigured, UE resets N310 and N311, and stops T310, if running. Network does not include this field. |
sCellState Indicates whether the SCell shall be considered to be in activated state upon SCell configuration. |
sCellToAddModList List of secondary serving cells (SCells) to be added or modified. |
sCellToReleaseList List of secondary serving cells (SCells) to be released. |
simultaneousTCI-UpdateList1, simultaneousTCI-UpdateList2 List of serving cells which can be updated simultaneously for TCI relation with a MAC CE. The simultaneousTCI-UpdateList1 and simultaneousTCI-UpdateList2 shall not contain same serving cells. Network should not configure serving cells that are configured with a BWP with two different values for the coresetPoolIndex in these lists. |
simultaneousSpatial-UpdatedList1, simultaneousSpatial-UpdatedList2 List of serving cells which can be updated simultaneously for spatial relation with a MAC CE. The simultaneousSpatial-UpdatedList1 and simultaneousSpatial-UpdatedList2 shall not contain same serving cells. Network should not configure serving cells that are configured with a BWP with two different values for the coresetPoolIndex in these lists. |
spCellConfig Parameters for the SpCell of this cell group (PCell of MCG or PSCell of SCG). |
uplinkTxSwitchingOption Indicates which option is configured for dynamic UL Tx switching for inter-band UL CA or (NG)EN-DC. The field is set to switchedUL if network configures option 1 as specified in TS 38.214 [19], or dualUL if network configures option 2 as specified in TS 38.214 [19]. Network always configures UE with a value for this field in inter-band UL CA case and (NG)EN-DC case where UE supports dynamic UL Tx switching. |
uplinkTxSwitchingPowerBoosting Indicates whether the UE is allowed to enable 3dB boosting on the maximum output power for transmission on carrier2 under the operation state in which 2-port transmission can be supported on carrier2 for inter-band UL CA case with dynamic UL Tx switching as defined in TS 38.101-1 [15]. Network can only configure this field for dynamic UL Tx switching in inter-band UL CA case with power Class 3 as defined in TS 38.101-1 [15]. |
DAPS-UplinkPowerConfigfield descriptions |
---|
p-DAPS-Source The maximum total transmit power to be used by the UE in the source cell group during DAPS handover. |
p-DAPS-Target The maximum total transmit power to be used by the UE in the target cell group during DAPS handover. |
uplinkPowerSharingDAPS-Mode Indicates the uplink power sharing mode that the UE uses in DAPS handover (see TS 38.213 [13]). |
ReconfigurationWithSync field descriptions |
---|
rach-ConfigDedicated Random access configuration to be used for the reconfiguration with sync (e.g. handover). The UE performs the RA according to these parameters in the firstActiveUplinkBWP (see UplinkConfig). |
smtc The SSB periodicity/offset/duration configuration of target cell for NR PSCell change and NR PCell change. The network sets the periodicityAndOffset to indicate the same periodicity as ssb-periodicityServingCell in spCellConfigCommon. For case of NR PCell change, the smtc is based on the timing reference of (source) PCell. For case of NR PSCell change, it is based on the timing reference of source PSCell. If both this field and targetCellSMTC-SCG are absent, the UE uses the SMTC in the measObjectNR having the same SSB frequency and subcarrier spacing,as configured before the reception of the RRC message. |
SCellConfig field descriptions |
---|
secondaryDRX-GroupConfig The field is used to indicate whether the SCell belongs to the secondary DRX group. All serving cells in the secondary DRX group shall belong to one Frequency Range and all serving cells in the legacy DRX group shall belong to another Frequency Range.If drx-ConfigSecondaryGroup is configured, the field is optionally present. The network always includes the field if the field was previously configured for this SCell and the SCell remains in the secondary DRX group. Removal of an individual SCell from the secondary DRX group is supported by using an SCell release and addition. Otherwise, if drx-ConfigSecondaryGroup is not configured, the field is absent and the UE shall release the field. The UE shall also release the field if drx-ConfigSecondaryGroup is released without including sCellToAddModList. |
smtc The SSB periodicity/offset/duration configuration of target cell for NR SCell addition. The network sets the periodicityAndOffset to indicate the same periodicity as ssb-periodicityServingCell in sCellConfigCommon. The smtc is based on the timing of the SpCell of associated cell group. In case of inter-RAT handover to NR, the timing reference is the NR PCell. In case of intra-NR PCell change (standalone NR) or NR PSCell change (EN-DC), the timing reference is the target SpCell. If the field is absent, the UE uses the SMTC in the measObjectNR having the same SSB frequency and subcarrier spacing, as configured before the reception of the RRC message. |
SpCellConfig field descriptions |
---|
reconfigurationWithSync Parameters for the synchronous reconfiguration to the target SpCell. |
rlf-TimersAndConstants Timers and constants for detecting and triggering cell-level radio link failure. For the SCG, rlf-TimersAndConstants can only be set to setup and is always included at SCG addition. |
servCellIndex Serving cell ID of a PSCell. The PCell of the Master Cell Group uses ID = 0. |
Conditional Presence | Explanation |
---|---|
BWP-Reconfig | The field is optionally present, Need N, if the BWPs are reconfigured or if serving cells are added or removed. Otherwise it is absent. |
ReconfWithSync | The field is mandatory present in the RRCReconfiguration message: -in each configured CellGroupConfig for which the SpCell changes, -in the masterCellGroup: -at change of AS security key derived from KgNB, -in an RRCReconfiguration message contained in a DLInformationTransferMRDC message, -in the secondaryCellGroup at: -PSCell addition, -SCG resume with NR-DC or (NG)EN-DC, -update of required SI for PSCell, -change of AS security key derived from S-KgNBin NR-DC while the UE is configured with at least one radio bearer with keyToUse set to secondary and that is not released by this RRCReconfiguration message, -MN handover in (NG)EN-DC. Otherwise, it is optionally present, need M. The field is absent in the masterCellGroup in RRCResume and RRCSetup messages and is absent in the masterCellGroup in RRCReconfiguration messages if source configuration is not released during DAPS handover. |
SCellAdd | The field is mandatory present upon SCell addition; otherwise it is absent, Need M. |
SCellAddMod | The field is mandatory present upon SCell addition; otherwise it is optionally present, need M. |
SCellAddSync | The field is optionally present, Need N, in case of SCell addition, reconfiguration with sync, and resuming an RRC connection. It is absent otherwise. |
SCG | The field is mandatory present in an SpCellConfig for the PSCell. It is absent otherwise. |
The IE CellGroupId is used to identify a cell group. Value 0 identifies the master cell group. Other values identify secondary cell groups. In this version of the specification only values 0 and 1 are supported.
The IE CellIdentity is used to unambiguously identify a cell within a PLMN/SNPN.
The IE CellReselectionPriority concerns the absolute priority of the concerned carrier frequency, as used by the cell reselection procedure. Corresponds to parameter "priority" in TS 38.304 [20]. Value 0 means lowest priority. The UE behaviour for the case the field is absent, if applicable, is specified in TS 38.304 [20].
The IE CellReselectionSubPriority indicates a fractional value to be added to the value of cellReselectionPriority to obtain the absolute priority of the concerned carrier frequency for E-UTRA and NR. Value oDot2 corresponds to 0.2, value oDot4 corresponds to 0.4 and so on.
The IE CGI-InfoEUTRA indicates EUTRA cell access related information, which is reported by the UE as part of E-UTRA report CGI procedure.
-- ASN1START -- TAG-CGI-INFOEUTRA-START CGI-InfoEUTRA ::= SEQUENCE { cgi-info-EPC SEQUENCE { cgi-info-EPC-legacy CellAccessRelatedInfo-EUTRA-EPC, cgi-info-EPC-list SEQUENCE (SIZE (1..maxPLMN)) OF CellAccessRelatedInfo-EUTRA-EPC OPTIONAL } OPTIONAL, cgi-info-5GC SEQUENCE (SIZE (1..maxPLMN)) OF CellAccessRelatedInfo-EUTRA-5GC OPTIONAL, freqBandIndicator FreqBandIndicatorEUTRA, multiBandInfoList MultiBandInfoListEUTRA OPTIONAL, freqBandIndicatorPriority ENUMERATED {true} OPTIONAL } -- TAG-CGI-INFOEUTRA-STOP -- ASN1STOP
The IE CGI-InfoEUTRALogging indicates EUTRA cell related information, which is reported by the UE as part of RLF reporting procedure.
-- ASN1START -- TAG-CGI-INFOEUTRALOGGING-START CGI-InfoEUTRALogging ::= SEQUENCE { plmn-Identity-eutra-5gc PLMN-Identity OPTIONAL, trackingAreaCode-eutra-5gc TrackingAreaCode OPTIONAL, cellIdentity-eutra-5gc BIT STRING (SIZE (28)) OPTIONAL, plmn-Identity-eutra-epc PLMN-Identity OPTIONAL, trackingAreaCode-eutra-epc BIT STRING (SIZE (16)) OPTIONAL, cellIdentity-eutra-epc BIT STRING (SIZE (28)) OPTIONAL } -- TAG-CGI-INFOEUTRALOGGING-STOP -- ASN1STOP
CGI-InfoEUTRALogging field descriptions |
---|
cellIdentity-eutra-epc, cellIdentity-eutra-5GC Unambiguously identify a cell within the context of the PLMN. It belongs the first PLMN entry of plmn-IdentityList (when connected to EPC) or of plmn-IdentityList-r15 (when connected to 5GC) in SystemInformationBlockType1. |
plmn-Identity-eutra-epc, plmn-Identity-eutra-5GC Identifies the PLMN of the cell for the reported cellIdentity: the first PLMN entry of plmn-IdentityList (when connected to EPC) or of plmn-IdentityList-r15 (when connected to 5GC) in SystemInformationBlockType1 that contained the reported cellIdentity. |
trackingAreaCode-eutra-epc, trackingAreaCode-eutra-5gc Indicates Tracking Area Code to which the cell indicated by cellIdentity-eutra-epc, cellIdentity-eutra-5GC belongs. |
The IE CGI-InfoNR indicates cell access related information, which is reported by the UE as part of report CGI procedure.
-- ASN1START -- TAG-CGI-INFO-NR-START CGI-InfoNR ::= SEQUENCE { plmn-IdentityInfoList PLMN-IdentityInfoList OPTIONAL, frequencyBandList MultiFrequencyBandListNR OPTIONAL, noSIB1 SEQUENCE { ssb-SubcarrierOffset INTEGER (0..15), pdcch-ConfigSIB1 PDCCH-ConfigSIB1 } OPTIONAL, ..., [[ npn-IdentityInfoList-r16 NPN-IdentityInfoList-r16 OPTIONAL ]], [[ cellReservedForOtherUse-r16 ENUMERATED {true} OPTIONAL ]] } -- TAG-CGI-INFO-NR-STOP -- ASN1STOP
The IE CGI-Info-Logging indicates the NR Cell Global Identifier (NCGI) for logging purposes (e.g. RLF report), the globally unique identity, and the TAC information of a cell in NR.
-- ASN1START -- TAG-CGI-INFO-LOGGING-START CGI-Info-Logging-r16 ::= SEQUENCE {plmn-Identity-r16Identifies the PLMN of the cell for the reported cellIdentity: the first PLMN entry of plmn-IdentityList (in SIB1) in the instance of PLMN-IdentityInfoList that contained the reported cellIdentity.PLMN-Identity,cellIdentity-r16Unambiguously identify a cell within the context of the PLMN. It belongs the first PLMN-IdentityInfo IE of PLMN-IdentityInfoList in SIB1.CellIdentity,trackingAreaCode-r16Indicates Tracking Area Code to which the cell indicated by cellIdentity field belongs.TrackingAreaCode OPTIONAL } -- TAG-CGI-INFO-LOGGING-STOP -- ASN1STOP
CGI-InfoNR field descriptions |
---|
noSIB1 Contains ssb-SubcarrierOffset and pdcch-ConfigSIB1 fields acquired by the UE from MIB of the cell for which report CGI procedure was requested by the network in case SIB1 was not broadcast by the cell. |
cellReservedForOtherUse Contains cellReservedForOtherUse field acquired by the UE that supports nr-CGI-Reporting-NPN from SIB1 of the cell for which report CGI procedure was requested by the network. |
CGI-Info-Logging field descriptions |
---|
cellIdentity Unambiguously identify a cell within the context of the PLMN. It belongs the first PLMN-IdentityInfo IE of PLMN-IdentityInfoList in SIB1. |
plmn-Identity Identifies the PLMN of the cell for the reported cellIdentity: the first PLMN entry of plmn-IdentityList (in SIB1) in the instance of PLMN-IdentityInfoList that contained the reported cellIdentity. |
trackingAreaCode Indicates Tracking Area Code to which the cell indicated by cellIdentity field belongs. |
The IE CLI-RSSI-Range specifies the value range used in CLI-RSSI measurements and thresholds. The integer value for CLI-RSSI measurements is according to Table 10.1.22.2.2-1 in TS 38.133 [14].
The IE CodebookConfig is used to configure codebooks of Type-I and Type-II (see TS 38.214 [19], clause 5.2.2.2)
-- ASN1START -- TAG-CODEBOOKCONFIG-START CodebookConfig ::= SEQUENCE { codebookType CHOICE { type1 SEQUENCE { subType CHOICE { typeI-SinglePanel SEQUENCE { nrOfAntennaPorts CHOICE { two SEQUENCE { twoTX-CodebookSubsetRestriction BIT STRING (SIZE (6)) }, moreThanTwo SEQUENCE { n1-n2 CHOICE { two-one-TypeI-SinglePanel-Restriction BIT STRING (SIZE (8)), two-two-TypeI-SinglePanel-Restriction BIT STRING (SIZE (64)), four-one-TypeI-SinglePanel-Restriction BIT STRING (SIZE (16)), three-two-TypeI-SinglePanel-Restriction BIT STRING (SIZE (96)), six-one-TypeI-SinglePanel-Restriction BIT STRING (SIZE (24)), four-two-TypeI-SinglePanel-Restriction BIT STRING (SIZE (128)), eight-one-TypeI-SinglePanel-Restriction BIT STRING (SIZE (32)), four-three-TypeI-SinglePanel-Restriction BIT STRING (SIZE (192)), six-two-TypeI-SinglePanel-Restriction BIT STRING (SIZE (192)), twelve-one-TypeI-SinglePanel-Restriction BIT STRING (SIZE (48)), four-four-TypeI-SinglePanel-Restriction BIT STRING (SIZE (256)), eight-two-TypeI-SinglePanel-Restriction BIT STRING (SIZE (256)), sixteen-one-TypeI-SinglePanel-Restriction BIT STRING (SIZE (64)) }, typeI-SinglePanel-codebookSubsetRestriction-i2 BIT STRING (SIZE (16)) OPTIONAL -- Need R } }, typeI-SinglePanel-ri-Restriction BIT STRING (SIZE (8)) }, typeI-MultiPanel SEQUENCE { ng-n1-n2 CHOICE { two-two-one-TypeI-MultiPanel-Restriction BIT STRING (SIZE (8)), two-four-one-TypeI-MultiPanel-Restriction BIT STRING (SIZE (16)), four-two-one-TypeI-MultiPanel-Restriction BIT STRING (SIZE (8)), two-two-two-TypeI-MultiPanel-Restriction BIT STRING (SIZE (64)), two-eight-one-TypeI-MultiPanel-Restriction BIT STRING (SIZE (32)), four-four-one-TypeI-MultiPanel-Restriction BIT STRING (SIZE (16)), two-four-two-TypeI-MultiPanel-Restriction BIT STRING (SIZE (128)), four-two-two-TypeI-MultiPanel-Restriction BIT STRING (SIZE (64)) }, ri-Restriction BIT STRING (SIZE (4)) } }, codebookMode INTEGER (1..2) }, type2 SEQUENCE { subType CHOICE { typeII SEQUENCE { n1-n2-codebookSubsetRestriction CHOICE { two-one BIT STRING (SIZE (16)), two-two BIT STRING (SIZE (43)), four-one BIT STRING (SIZE (32)), three-two BIT STRING (SIZE (59)), six-one BIT STRING (SIZE (48)), four-two BIT STRING (SIZE (75)), eight-one BIT STRING (SIZE (64)), four-three BIT STRING (SIZE (107)), six-two BIT STRING (SIZE (107)), twelve-one BIT STRING (SIZE (96)), four-four BIT STRING (SIZE (139)), eight-two BIT STRING (SIZE (139)), sixteen-one BIT STRING (SIZE (128)) }, typeII-RI-Restriction BIT STRING (SIZE (2)) }, typeII-PortSelection SEQUENCE { portSelectionSamplingSize ENUMERATED {n1, n2, n3, n4} OPTIONAL, -- Need R typeII-PortSelectionRI-Restriction BIT STRING (SIZE (2)) } }, phaseAlphabetSize ENUMERATED {n4, n8}, subbandAmplitude BOOLEAN, numberOfBeams ENUMERATED {two, three, four} } } } CodebookConfig-r16 ::= SEQUENCE { codebookType CHOICE { type2 SEQUENCE { subType CHOICE { typeII-r16 SEQUENCE { n1-n2-codebookSubsetRestriction-r16 CHOICE { two-one BIT STRING (SIZE (16)), two-two BIT STRING (SIZE (43)), four-one BIT STRING (SIZE (32)), three-two BIT STRING (SIZE (59)), six-one BIT STRING (SIZE (48)), four-two BIT STRING (SIZE (75)), eight-one BIT STRING (SIZE (64)), four-three BIT STRING (SIZE (107)), six-two BIT STRING (SIZE (107)), twelve-one BIT STRING (SIZE (96)), four-four BIT STRING (SIZE (139)), eight-two BIT STRING (SIZE (139)), sixteen-one BIT STRING (SIZE (128)) }, typeII-RI-Restriction-r16 BIT STRING (SIZE(4)) }, typeII-PortSelection-r16 SEQUENCE { portSelectionSamplingSize-r16 ENUMERATED {n1, n2, n3, n4}, typeII-PortSelectionRI-Restriction-r16 BIT STRING (SIZE (4)) } }, numberOfPMI-SubbandsPerCQI-Subband-r16 INTEGER (1..2), paramCombination-r16 INTEGER (1..8) } } } -- TAG-CODEBOOKCONFIG-STOP -- ASN1STOP
The IE CommonLocationInfo is used to transfer detailed location information available at the UE to correlate measurements and UE position information.
-- ASN1START -- TAG-COMMONLOCATIONINFO-START CommonLocationInfo-r16 ::= SEQUENCE {gnss-TOD-msec-r16Parameter type gnss-TOD-msec defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit.OCTET STRING OPTIONAL, locationTimestamp-r16 OCTET STRING OPTIONAL,locationCoordinate-r16Parameter type LocationCoordinates defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit.OCTET STRING OPTIONAL,locationError-r16Parameter LocationError defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit.OCTET STRING OPTIONAL,locationSource-r16Parameter LocationSource defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit.OCTET STRING OPTIONAL,velocityEstimate-r16Parameter type Velocity defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit.OCTET STRING OPTIONAL } -- TAG-COMMONLOCATIONINFO-STOP -- ASN1STOP
CodebookConfig field descriptions |
---|
codebookMode CodebookMode as specified in TS 38.214 [19], clause 5.2.2.2.2. |
codebookType CodebookType including possibly sub-types and the corresponding parameters for each (see TS 38.214 [19], clause 5.2.2.2). |
n1-n2-codebookSubsetRestriction Number of antenna ports in first (n1) and second (n2) dimension and codebook subset restriction (see TS 38.214 [19] clause 5.2.2.2.3). Number of bits for codebook subset restriction is CEIL(log2(nchoosek(O1*O2,4)))+8*n1*n2 where nchoosek(a,b) = a!/(b!(a-b)!). |
n1-n2 Number of antenna ports in first (n1) and second (n2) dimension and codebook subset restriction (see TS 38.214 [19] clause 5.2.2.2.1). |
ng-n1-n2 Codebook subset restriction for Type I Multi-panel codebook (see TS 38.214 [19], clause 5.2.2.2.2). |
numberOfBeams Number of beams, L, used for linear combination. |
numberOfPMI-SubbandsPerCQI-Subband Field indicates how PMI subbands are defined per CQI subband according to TS 38.214 [19], clause 5.2.2.2.5, |
paramCombination Field describes supported parameter combination () as specified in TS 38.214 [19]. |
phaseAlphabetSize The size of the PSK alphabet, QPSK or 8-PSK. |
portSelectionSamplingSize The size of the port selection codebook (parameter d), see TS 38.214 [19] clause 5.2.2.2.6. |
ri-Restriction Restriction for RI for TypeI-MultiPanel-RI-Restriction (see TS 38.214 [19], clause 5.2.2.2.2). |
subbandAmplitude If subband amplitude reporting is activated (true). |
twoTX-CodebookSubsetRestriction Codebook subset restriction for 2TX codebook (see TS 38.214 [19] clause 5.2.2.2.1). |
typeI-SinglePanel-codebookSubsetRestriction-i2 i2 codebook subset restriction for Type I Single-panel codebook used when reportQuantity is CRI/Ri/i1/CQI (see TS 38.214 [19] clause 5.2.2.2.1). |
typeI-SinglePanel-ri-Restriction Restriction for RI for TypeI-SinglePanel-RI-Restriction (see TS 38.214 [19], clause 5.2.2.2.1). |
typeII-PortSelectionRI-Restriction Restriction for RI for TypeII-PortSelection-RI-Restriction (see TS 38.214 [19], clauses 5.2.2.2.4 and 5.2.2.2.6). |
typeII-RI-Restriction Restriction for RI for TypeII-RI-Restriction (see TS 38.214 [19], clauses 5.2.2.2.3 and 5.2.2.2.5). |
CommonLocationInfo field descriptions |
---|
gnss-TOD-msec Parameter type gnss-TOD-msec defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit. |
locationTimeStamp Parameter type DisplacementTimeStamp defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit. |
locationCoordinate Parameter type LocationCoordinates defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit. |
locationError Parameter LocationError defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit. |
locationSource Parameter LocationSource defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit. |
velocityEstimate Parameter type Velocity defined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit. |
The IE CondReconfigId is used to identify a CHO or CPC configuration.
The IE CondReconfigToAddModList concerns a list of conditional reconfigurations to add or modify, with for each entry the condReconfigId and the associated condExecutionCond and condRRCReconfig.
-- ASN1START -- TAG-CONDRECONFIGTOADDMODLIST-START CondReconfigToAddModList-r16 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigToAddMod-r16 CondReconfigToAddMod-r16 ::= SEQUENCE { condReconfigId-r16 CondReconfigId-r16,condExecutionCond-r16The execution condition that needs to be fulfilled in order to trigger the execution of a conditional reconfiguration. When configuring 2 triggering events (Meas Ids) for a candidate cell, network ensures that both refer to the same measObject.SEQUENCE (SIZE (1..2)) OF MeasId OPTIONAL, -- Cond condReconfigAddcondRRCReconfig-r16The RRCReconfiguration message to be applied when the condition(s) are fulfilled. The RRCReconfiguration message contained in condRRCReconfig cannot contain the field conditionalReconfiguration, the field daps-Configor the configuration for target SCG for CHO.OCTET STRING (CONTAINING RRCReconfiguration) OPTIONAL, -- Cond condReconfigAdd ... } -- TAG-CONDRECONFIGTOADDMODLIST-STOP -- ASN1STOP
CondReconfigToAddMod field descriptions |
---|
condExecutionCond The execution condition that needs to be fulfilled in order to trigger the execution of a conditional reconfiguration. When configuring 2 triggering events (Meas Ids) for a candidate cell, network ensures that both refer to the same measObject. |
condRRCReconfig The RRCReconfiguration message to be applied when the condition(s) are fulfilled. The RRCReconfiguration message contained in condRRCReconfig cannot contain the field conditionalReconfiguration, the field daps-Configor the configuration for target SCG for CHO. |
Conditional Presence | Explanation |
---|---|
condReconfigAdd | The field is mandatory present when a condReconfigId is being added. Otherwise the field is optional, need M. |
The IE ConditionalReconfiguration is used to add, modify and release the configuration of conditional reconfiguration.
-- ASN1START -- TAG-CONDITIONALRECONFIGURATION-START ConditionalReconfiguration-r16 ::= SEQUENCE {attemptCondReconfig-r16If present, the UE shall perform conditional reconfiguration if selected cell is a target candidate cell and it is the first cell selection after failure as described in clause 5.3.7.3.ENUMERATED {true} OPTIONAL, -- Cond CHOcondReconfigToRemoveList-r16List of the configuration of candidate SpCells to be removed.CondReconfigToRemoveList-r16 OPTIONAL, -- Need NcondReconfigToAddModList-r16List of the configuration of candidate SpCells to be added or modified for CHO or CPC.CondReconfigToAddModList-r16 OPTIONAL, -- Need N ... } CondReconfigToRemoveList-r16 ::= SEQUENCE (SIZE (1.. maxNrofCondCells-r16)) OF CondReconfigId-r16 -- TAG-CONDITIONALRECONFIGURATION-STOP -- ASN1STOP
ConditionalReconfiguration field descriptions |
---|
attemptCondReconfig If present, the UE shall perform conditional reconfiguration if selected cell is a target candidate cell and it is the first cell selection after failure as described in clause 5.3.7.3. |
condReconfigToAddModList List of the configuration of candidate SpCells to be added or modified for CHO or CPC. |
condReconfigToRemoveList List of the configuration of candidate SpCells to be removed. |
Conditional Presence | Explanation |
---|---|
CHO | The field is optional present, Need R, if the UE is configured with at least a candidate SpCell for CHO. Otherwise the field is not present. |
The IE ConfiguredGrantConfig is used to configure uplink transmission without dynamic grant according to two possible schemes. The actual uplink grant may either be configured via RRC (type1) or provided via the PDCCH (addressed to CS-RNTI) (type2). Multiple Configured Grant configurations may be configured in one BWP of a serving cell.
-- ASN1START -- TAG-CONFIGUREDGRANTCONFIG-START ConfiguredGrantConfig ::= SEQUENCE {frequencyHoppingThe value intraSlot enables 'Intra-slot frequency hopping' and the value interSlot enables 'Inter-slot frequency hopping'. If the field is absent, frequency hopping is not configured. The field frequencyHoppingapplies to configured grant for 'pusch-RepTypeA' (see TS 38.214 [19], clause 6.3.1).ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need Scg-DMRS-ConfigurationDMRS configuration (see TS 38.214 [19], clause 6.1.2.3).DMRS-UplinkConfig,mcs-TableIndicates the MCS table the UE shall use for PUSCH without transform precoding. If the field is absent the UE applies the value qam64.ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Smcs-TableTransformPrecoderIndicates the MCS table the UE shall use for PUSCH with transform precoding. If the field is absent the UE applies the value qam64.ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need Suci-OnPUSCHSelection between and configuration of dynamic and semi-static beta-offset. For Type 1 UL data transmission without grant, uci-OnPUSCH should be set to semiStatic.SetupRelease { CG-UCI-OnPUSCH } OPTIONAL, -- Need MresourceAllocationConfiguration of resource allocation type 0 and resource allocation type 1. For Type 1 UL data transmission without grant, resourceAllocation should be resourceAllocationType0 or resourceAllocationType1.ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch },rbg-SizeSelection between configuration 1 and configuration 2 for RBG size for PUSCH. The UE does not apply this field if resourceAllocation is set to resourceAllocationType1. Otherwise, the UE applies the value config1 when the field is absent. Note: rbg-Size is used when the transformPrecoder parameter is disabled.ENUMERATED {config2} OPTIONAL, -- Need SpowerControlLoopToUseClosed control loop to apply (see TS 38.213 [13], clause 7.1.1).ENUMERATED {n0, n1},p0-PUSCH-AlphaIndex of the P0-PUSCH-AlphaSet to be used for this configuration.P0-PUSCH-AlphaSetId,transformPrecoderEnables or disables transform precoding for type1 and type2. If the field is absent, the UE enables or disables transform precoding in accordance with the field msg3-transformPrecoder in RACH-ConfigCommon, see TS 38.214 [19], clause 6.1.3.ENUMERATED {enabled, disabled} OPTIONAL, -- Need SnrofHARQ-ProcessesThe number of HARQ processes configured. It applies for both Type 1 and Type 2. See TS 38.321 [3], clause 5.4.1.INTEGER(1..16),repKNumber of repetitions K, see TS 38.214 [19].ENUMERATED {n1, n2, n4, n8},repK-RVThe redundancy version (RV) sequence to use. See TS 38.214 [19], clause 6.1.2. The network configures this field if repetitions are used, i.e., if repK is set to n2, n4 or n8. This field is not configured when cg-RetransmissionTimer is configured. Otherwise, the field is absent.ENUMERATED {s1-0231, s2-0303, s3-0000} OPTIONAL, -- Need RperiodicityPeriodicity for UL transmission without UL grant for type 1 and type 2 (see TS 38.321 [3], clause 5.8.2). The following periodicities are supported depending on the configured subcarrier spacing [symbols]: 15 kHz:2, 7, n*14, where n={1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 320, 640} 30 kHz:2, 7, n*14, where n={1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 256, 320, 640, 1280} 60 kHz with normal CP2, 7, n*14, where n={1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 256, 320, 512, 640, 1280, 2560} 60 kHz with ECP:2, 6, n*12, where n={1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 256, 320, 512, 640, 1280, 2560} 120 kHz:2, 7, n*14, where n={1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 256, 320, 512, 640, 1024, 1280, 2560, 5120}ENUMERATED { sym2, sym7, sym1x14, sym2x14, sym4x14, sym5x14, sym8x14, sym10x14, sym16x14, sym20x14, sym32x14, sym40x14, sym64x14, sym80x14, sym128x14, sym160x14, sym256x14, sym320x14, sym512x14, sym640x14, sym1024x14, sym1280x14, sym2560x14, sym5120x14, sym6, sym1x12, sym2x12, sym4x12, sym5x12, sym8x12, sym10x12, sym16x12, sym20x12, sym32x12, sym40x12, sym64x12, sym80x12, sym128x12, sym160x12, sym256x12, sym320x12, sym512x12, sym640x12, sym1280x12, sym2560x12 },configuredGrantTimerIndicates the initial value of the configured grant timer (see TS 38.321 [3]) in multiples of periodicity. When cg-RetransmissonTimer is configured, if HARQ processes are shared among different configured grants on the same BWP, configuredGrantTimer * periodicity is set to the same value for the configurations that share HARQ processes on this BWP.INTEGER (1..64) OPTIONAL, -- Need Rrrc-ConfiguredUplinkGrantConfiguration for "configured grant" transmission with fully RRC-configured UL grant (Type1). If this field is absent the UE uses UL grant configured by DCI addressed to CS-RNTI (Type2).SEQUENCE {timeDomainOffsetOffset related to the reference SFN indicated by timeReferenceSFN, see TS 38.321 [3], clause 5.8.2.INTEGER (0..5119),timeDomainAllocationIndicates a combination of start symbol and length and PUSCH mapping type, see TS 38.214 [19], clause 6.1.2 and TS 38.212 [17], clause 7.3.1.INTEGER (0..15),frequencyDomainAllocationIndicates the frequency domain resource allocation, see TS 38.214 [19], clause 6.1.2, and TS 38.212 [17], clause 7.3.1).BIT STRING (SIZE(18)),antennaPortIndicates the antenna port(s) to be used for this configuration, and the maximum bitwidth is 5. See TS 38.214 [19], clause 6.1.2, and TS 38.212 [17], clause 7.3.1.INTEGER (0..31),dmrs-SeqInitializationThe network configures this field if transformPrecoder is disabled. Otherwise the field is absent.INTEGER (0..1) OPTIONAL, -- Need RprecodingAndNumberOfLayersIndicates the precoding and number of layers (see TS 38.212 [17], clause 7.3.1.1.2, and TS 38.214 [19], clause 6.1.2.3).INTEGER (0..63),srs-ResourceIndicatorIndicates the SRS resource to be used.INTEGER (0..15) OPTIONAL, -- Need RmcsAndTBSThe modulation order, target code rate and TB size (see TS 38.214 [19], clause 6.1.2). The NW does not configure the values 28~31 in this version of the specification.INTEGER (0..31),frequencyHoppingOffsetFrequency hopping offset used when frequency hopping is enabled (see TS 38.214 [19], clause 6.1.2 and clause 6.3).INTEGER (1.. maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Need RpathlossReferenceIndexIndicates the reference signal index used as PUSCH pathloss reference (see TS 38.213 [13], clause 7.1.1).INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1), ..., [[pusch-RepTypeIndicator-r16Indicates whether UE follows the behavior for PUSCH repetition type A or the behavior for PUSCH repetition type B for each Type 1 configured grant configuration. The value pusch-RepTypeA enables the 'PUSCH repetition type A' and the value pusch-RepTypeB enables the 'PUSCH repetition type B' (see TS 38.214 [19], clause 6.1.2.3). The value pusch-RepTypeB is not configured simultaneously with cg-nrofPUSCH-InSlot-r16 and cg-nrofSlots-r16.ENUMERATED {pusch-RepTypeA,pusch-RepTypeB} OPTIONAL, -- Need MfrequencyHoppingPUSCH-RepTypeB-r16Indicates the frequency hopping scheme for Type 1 CG when pusch-RepTypeIndicator is set to 'pusch-RepTypeB' (see TS 38.214 [19], clause 6.1). The value interRepetition enables 'Inter-repetition frequency hopping', and the value interSlot enables 'Inter-slot frequency hopping'. If the field is absent, the frequency hopping is not enabled for Type 1 CG.ENUMERATED {interRepetition, interSlot} OPTIONAL, -- Cond RepTypeBtimeReferenceSFN-r16Indicates SFN used for determination of the offset of a resource in time domain. The UE uses the closest SFN with the indicated number preceding the reception of the configured grant configuration, see TS 38.321 [3], clause 5.8.2. If the field timeReferenceSFN is not present, the reference SFN is 0.ENUMERATED {sfn512} OPTIONAL -- Need S ]] } OPTIONAL, -- Need R ..., [[cg-RetransmissionTimer-r16Indicates the initial value of the configured retransmission timer (see TS 38.321 [3]) in multiples of periodicity. The value of cg-RetransmissionTimer is always less than or equal to the value of configuredGrantTimer. This field is always configured for operation with shared spectrum channel access together with harq-ProcID-Offset. This field is not configured for operation in licensed spectrum or simultaneously with harq-ProcID-Offset2.INTEGER (1..64) OPTIONAL, -- Need Rcg-minDFI-Delay-r16Indicates the minimum duration (in unit of symbols) from the ending symbol of the PUSCH to the starting symbol of the PDCCH containing the downlink feedback indication (DFI) carrying HARQ-ACK for this PUSCH. The HARQ-ACK received before this minimum duration is not considered as valid for this PUSCH (see TS 38.213 [13], clause 10.5). The following minimum duration values are supported, depending on the configured subcarrier spacing [symbols]: 15 kHz:7, m*14, where m = {1, 2, 3, 4} 30 kHz:7, m*14, where m = {1, 2, 3, 4, 5, 6, 7, 8} 60 kHz:7, m*14, where m = {1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16}ENUMERATED {sym7, sym1x14, sym2x14, sym3x14, sym4x14, sym5x14, sym6x14, sym7x14, sym8x14, sym9x14, sym10x14, sym11x14, sym12x14, sym13x14, sym14x14,sym15x14, sym16x14 } OPTIONAL, -- Need Rcg-nrofPUSCH-InSlot-r16Indicates the number of consecutive PUSCH configured to CG within a slot where the SLIV indicating the first PUSCH and additional PUSCH appended with the same length (see TS 38.214 [19], clause 6.1.2.3).INTEGER (1..7) OPTIONAL, -- Need Rcg-nrofSlots-r16Indicates the number of allocated slots in a configured grant periodicity following the time instance of configured grant offset (see TS 38.214 [19], clause 6.1.2.3).INTEGER (1..40) OPTIONAL, -- Need R cg-StartingOffsets-r16 CG-StartingOffsets-r16 OPTIONAL, -- Need Rcg-UCI-Multiplexing-r16If present, this field indicates that in the case of PUCCH overlapping with CG-PUSCH(s) within a PUCCH group, the CG-UCI and HARQ-ACK are jointly encoded (see TS 38.213 [13], clause 9).ENUMERATED {enabled} OPTIONAL, -- Need Rcg-COT-SharingOffset-r16Indicates the offset from the end of the slot where the COT sharing indication in UCI is enabled where the offset in symbols is equal to 14*n, where n is the signaled value for cg-COT-SharingOffset. Applicable when ul-toDL-COT-SharingED-Threshold-r16 is not configured (see 37.213 [48], clause 4.1.3).INTEGER (1..39) OPTIONAL, -- Need RbetaOffsetCG-UCI-r16Beta offset for CG-UCI in CG-PUSCH, see TS 38.213 [13], clause 9.3INTEGER (0..31) OPTIONAL, -- Need Rcg-COT-SharingList-r16Indicates a table for COT sharing combinations (see 37.213 [48], clause 4.1.3). One row of the table can be set to noCOT-Sharing to indicate that there is no channel occupancy sharing.SEQUENCE (SIZE (1..1709)) OF CG-COT-Sharing-r16 OPTIONAL, -- Need Rharq-ProcID-Offset-r16For operation with shared spectrum channel access, this configures the range of HARQ process IDs which can be used for this configured grant where the UE can select a HARQ process ID within [harq-procID-offset, .., (harq-procID-offset + nrofHARQ-Processes – 1)].INTEGER (0..15) OPTIONAL, -- Need Mharq-ProcID-Offset2-r16Indicates the offset used in deriving the HARQ process IDs, see TS 38.321 [3], clause 5.4.1. This field is not configured for operation with shared spectrum channel access.INTEGER (0..15) OPTIONAL, -- Need MconfiguredGrantConfigIndex-r16Indicates the index of the Configured Grant configurations within the BWP.ConfiguredGrantConfigIndex-r16 OPTIONAL, -- Cond CG-ListconfiguredGrantConfigIndexMAC-r16Indicates the index of the Configured Grant configurations within the MAC entity.ConfiguredGrantConfigIndexMAC-r16 OPTIONAL, -- Cond CG-IndexMACperiodicityExt-r16This field is used to calculate the periodicity for UL transmission without UL grant for type 1 and type 2 (see TS 38.321 [3], clause 5.8.2). If this field is present, the field periodicity is ignored. The following periodicites are supported depending on the configured subcarrier spacing [symbols]: 15 kHz:periodicityExt*14, where periodicityExt has a value between 1 and 640. 30 kHz:periodicityExt*14, where periodicityExt has a value between 1 and 1280. 60 kHz with normal CP:periodicityExt*14, where periodicityExt has a value between 1 and 2560. 60 kHz with ECP:periodicityExt*12, where periodicityExt has a value between 1 and 2560. 120 kHz:periodicityExt*14, where periodicityExt has a value between 1 and 5120.INTEGER (1..5120) OPTIONAL, -- Need RstartingFromRV0-r16This field is used to determine the initial transmission occasion of a transport block for a given RV sequence, see TS 38.214 [19], clause 6.1.2.3.1.ENUMERATED {on, off} OPTIONAL, -- Need Rphy-PriorityIndex-r16Indicates the PHY priority of CG PUSCH at least for PHY-layer collision handling. Value p0 indicates low priority and value p1 indicates high priority.ENUMERATED {p0, p1} OPTIONAL, -- Need RautonomousTx-r16If this field is present, the Configured Grant configuration is configured with autonomous transmission, see TS 38.321 [3].ENUMERATED {enabled} OPTIONAL -- Cond LCH-BasedPrioritization ]] } CG-UCI-OnPUSCH ::= CHOICE { dynamic SEQUENCE (SIZE (1..4)) OF BetaOffsets, semiStatic BetaOffsets } CG-COT-Sharing-r16 ::= CHOICE { noCOT-Sharing-r16 NULL, cot-Sharing-r16 SEQUENCE {duration-r16Indicates the number of DL transmission slots within UE initiated COT (see 37.213 [48], clause 4.1.3).INTEGER (1..39),offset-r16Indicates the number of DL transmission slots from the end of the slot where CG-UCI is detected after which COT sharing can be used (see 37.213 [48], clause 4.1.3).INTEGER (1..39),channelAccessPriority-r16Indicates the Channel Access Priority Class that the gNB can assume when sharing the UE initiated COT (see 37.213 [48], clause 4.1.3).INTEGER (1..4) } } CG-StartingOffsets-r16 ::= SEQUENCE {cg-StartingFullBW-InsideCOT-r16A set of configured grant PUSCH transmission starting offsets (see TS 38.211[16], Table 5.3.1-2) which indicates the length of a CP extension of the first symbol that is located before the configured resource when frequency domain resource allocation includes all interlaces in the allocated RB set(s) and the CG PUSCH resource is inside gNB COT (see TS 38.214 [19], clause 6.1.2.3).SEQUENCE (SIZE (1..7)) OF INTEGER (0..6) OPTIONAL, -- Need Rcg-StartingFullBW-OutsideCOT-r16A set of configured grant PUSCH transmission starting offset indices (see TS 38.211[16], Table 5.3.1-2) which indicates the length of a CP extension of the first symbol that is located before the configured resource when frequency domain resource allocation includes all interlaces in the allocated RB set(s) and the CG PUSCH resource is outside gNB COT (see TS 38.214 [19], clause 6.1.2.3).SEQUENCE (SIZE (1..7)) OF INTEGER (0..6) OPTIONAL, -- Need Rcg-StartingPartialBW-InsideCOT-r16A set of configured grant PUSCH transmission starting offset index (see TS 38.211[16], Table 5.3.1-2) which indicates the length of a CP extension of the first symbol that is located before the configured resource when frequency domain resource allocation does not include all interlaces in the allocated RB set(s) and the CG PUSCH resource is inside gNB COT (see TS 38.214 [19], clause 6.1.2.3).INTEGER (0..6) OPTIONAL, -- Need Rcg-StartingPartialBW-OutsideCOT-r16A set of configured grant PUSCH transmission starting offset index (see TS 38.211[16], Table 5.3.1-2) which indicates the length of a CP extension of the first symbol that is located before the configured resource when frequency domain resource allocation does not include all interlaces in the allocated RB set(s) and the CG PUSCH resource is outside gNB COT (see TS 38.214 [19], clause 6.1.2.3).INTEGER (0..6) OPTIONAL -- Need R } -- TAG-CONFIGUREDGRANTCONFIG-STOP -- ASN1STOP
ConfiguredGrantConfig field descriptions |
---|
antennaPort Indicates the antenna port(s) to be used for this configuration, and the maximum bitwidth is 5. See TS 38.214 [19], clause 6.1.2, and TS 38.212 [17], clause 7.3.1. |
autonomousTx If this field is present, the Configured Grant configuration is configured with autonomous transmission, see TS 38.321 [3]. |
betaOffsetCG-UCI Beta offset for CG-UCI in CG-PUSCH, see TS 38.213 [13], clause 9.3 |
cg-COT-SharingList Indicates a table for COT sharing combinations (see 37.213 [48], clause 4.1.3). One row of the table can be set to noCOT-Sharing to indicate that there is no channel occupancy sharing. |
cg-COT-SharingOffset Indicates the offset from the end of the slot where the COT sharing indication in UCI is enabled where the offset in symbols is equal to 14*n, where n is the signaled value for cg-COT-SharingOffset. Applicable when ul-toDL-COT-SharingED-Threshold-r16 is not configured (see 37.213 [48], clause 4.1.3). |
cg-DMRS-Configuration DMRS configuration (see TS 38.214 [19], clause 6.1.2.3). |
cg-minDFI-Delay Indicates the minimum duration (in unit of symbols) from the ending symbol of the PUSCH to the starting symbol of the PDCCH containing the downlink feedback indication (DFI) carrying HARQ-ACK for this PUSCH. The HARQ-ACK received before this minimum duration is not considered as valid for this PUSCH (see TS 38.213 [13], clause 10.5). The following minimum duration values are supported, depending on the configured subcarrier spacing [symbols]: 15 kHz:7, m*14, where m = {1, 2, 3, 4} 30 kHz:7, m*14, where m = {1, 2, 3, 4, 5, 6, 7, 8} 60 kHz:7, m*14, where m = {1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16} |
cg-nrofPUSCH-InSlot Indicates the number of consecutive PUSCH configured to CG within a slot where the SLIV indicating the first PUSCH and additional PUSCH appended with the same length (see TS 38.214 [19], clause 6.1.2.3). |
cg-nrofSlots Indicates the number of allocated slots in a configured grant periodicity following the time instance of configured grant offset (see TS 38.214 [19], clause 6.1.2.3). |
cg-RetransmissionTimer Indicates the initial value of the configured retransmission timer (see TS 38.321 [3]) in multiples of periodicity. The value of cg-RetransmissionTimer is always less than or equal to the value of configuredGrantTimer. This field is always configured for operation with shared spectrum channel access together with harq-ProcID-Offset. This field is not configured for operation in licensed spectrum or simultaneously with harq-ProcID-Offset2. |
cg-UCI-Multiplexing If present, this field indicates that in the case of PUCCH overlapping with CG-PUSCH(s) within a PUCCH group, the CG-UCI and HARQ-ACK are jointly encoded (see TS 38.213 [13], clause 9). |
configuredGrantConfigIndex Indicates the index of the Configured Grant configurations within the BWP. |
configuredGrantConfigIndexMAC Indicates the index of the Configured Grant configurations within the MAC entity. |
configuredGrantTimer Indicates the initial value of the configured grant timer (see TS 38.321 [3]) in multiples of periodicity. When cg-RetransmissonTimer is configured, if HARQ processes are shared among different configured grants on the same BWP, configuredGrantTimer * periodicity is set to the same value for the configurations that share HARQ processes on this BWP. |
dmrs-SeqInitialization The network configures this field if transformPrecoder is disabled. Otherwise the field is absent. |
frequencyDomainAllocation Indicates the frequency domain resource allocation, see TS 38.214 [19], clause 6.1.2, and TS 38.212 [17], clause 7.3.1). |
frequencyHopping The value intraSlot enables 'Intra-slot frequency hopping' and the value interSlot enables 'Inter-slot frequency hopping'. If the field is absent, frequency hopping is not configured. The field frequencyHoppingapplies to configured grant for 'pusch-RepTypeA' (see TS 38.214 [19], clause 6.3.1). |
frequencyHoppingOffset Frequency hopping offset used when frequency hopping is enabled (see TS 38.214 [19], clause 6.1.2 and clause 6.3). |
frequencyHoppingPUSCH-RepTypeB Indicates the frequency hopping scheme for Type 1 CG when pusch-RepTypeIndicator is set to 'pusch-RepTypeB' (see TS 38.214 [19], clause 6.1). The value interRepetition enables 'Inter-repetition frequency hopping', and the value interSlot enables 'Inter-slot frequency hopping'. If the field is absent, the frequency hopping is not enabled for Type 1 CG. |
harq-ProcID-Offset For operation with shared spectrum channel access, this configures the range of HARQ process IDs which can be used for this configured grant where the UE can select a HARQ process ID within [harq-procID-offset, .., (harq-procID-offset + nrofHARQ-Processes – 1)]. |
harq-ProcID-Offset2 Indicates the offset used in deriving the HARQ process IDs, see TS 38.321 [3], clause 5.4.1. This field is not configured for operation with shared spectrum channel access. |
mcs-Table Indicates the MCS table the UE shall use for PUSCH without transform precoding. If the field is absent the UE applies the value qam64. |
mcs-TableTransformPrecoder Indicates the MCS table the UE shall use for PUSCH with transform precoding. If the field is absent the UE applies the value qam64. |
mcsAndTBS The modulation order, target code rate and TB size (see TS 38.214 [19], clause 6.1.2). The NW does not configure the values 28~31 in this version of the specification. |
nrofHARQ-Processes The number of HARQ processes configured. It applies for both Type 1 and Type 2. See TS 38.321 [3], clause 5.4.1. |
p0-PUSCH-Alpha Index of the P0-PUSCH-AlphaSet to be used for this configuration. |
pathlossReferenceIndex Indicates the reference signal index used as PUSCH pathloss reference (see TS 38.213 [13], clause 7.1.1). |
periodicity Periodicity for UL transmission without UL grant for type 1 and type 2 (see TS 38.321 [3], clause 5.8.2). The following periodicities are supported depending on the configured subcarrier spacing [symbols]: 15 kHz:2, 7, n*14, where n={1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 320, 640} 30 kHz:2, 7, n*14, where n={1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 256, 320, 640, 1280} 60 kHz with normal CP2, 7, n*14, where n={1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 256, 320, 512, 640, 1280, 2560} 60 kHz with ECP:2, 6, n*12, where n={1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 256, 320, 512, 640, 1280, 2560} 120 kHz:2, 7, n*14, where n={1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 256, 320, 512, 640, 1024, 1280, 2560, 5120} |
periodicityExt This field is used to calculate the periodicity for UL transmission without UL grant for type 1 and type 2 (see TS 38.321 [3], clause 5.8.2). If this field is present, the field periodicity is ignored. The following periodicites are supported depending on the configured subcarrier spacing [symbols]: 15 kHz:periodicityExt*14, where periodicityExt has a value between 1 and 640. 30 kHz:periodicityExt*14, where periodicityExt has a value between 1 and 1280. 60 kHz with normal CP:periodicityExt*14, where periodicityExt has a value between 1 and 2560. 60 kHz with ECP:periodicityExt*12, where periodicityExt has a value between 1 and 2560. 120 kHz:periodicityExt*14, where periodicityExt has a value between 1 and 5120. |
phy-PriorityIndex Indicates the PHY priority of CG PUSCH at least for PHY-layer collision handling. Value p0 indicates low priority and value p1 indicates high priority. |
powerControlLoopToUse Closed control loop to apply (see TS 38.213 [13], clause 7.1.1). |
precodingAndNumberOfLayers Indicates the precoding and number of layers (see TS 38.212 [17], clause 7.3.1.1.2, and TS 38.214 [19], clause 6.1.2.3). |
pusch-RepTypeIndicator Indicates whether UE follows the behavior for PUSCH repetition type A or the behavior for PUSCH repetition type B for each Type 1 configured grant configuration. The value pusch-RepTypeA enables the 'PUSCH repetition type A' and the value pusch-RepTypeB enables the 'PUSCH repetition type B' (see TS 38.214 [19], clause 6.1.2.3). The value pusch-RepTypeB is not configured simultaneously with cg-nrofPUSCH-InSlot-r16 and cg-nrofSlots-r16. |
rbg-Size Selection between configuration 1 and configuration 2 for RBG size for PUSCH. The UE does not apply this field if resourceAllocation is set to resourceAllocationType1. Otherwise, the UE applies the value config1 when the field is absent. Note: rbg-Size is used when the transformPrecoder parameter is disabled. |
repK-RV The redundancy version (RV) sequence to use. See TS 38.214 [19], clause 6.1.2. The network configures this field if repetitions are used, i.e., if repK is set to n2, n4 or n8. This field is not configured when cg-RetransmissionTimer is configured. Otherwise, the field is absent. |
repK Number of repetitions K, see TS 38.214 [19]. |
resourceAllocation Configuration of resource allocation type 0 and resource allocation type 1. For Type 1 UL data transmission without grant, resourceAllocation should be resourceAllocationType0 or resourceAllocationType1. |
rrc-ConfiguredUplinkGrant Configuration for "configured grant" transmission with fully RRC-configured UL grant (Type1). If this field is absent the UE uses UL grant configured by DCI addressed to CS-RNTI (Type2). |
srs-ResourceIndicator Indicates the SRS resource to be used. |
startingFromRV0 This field is used to determine the initial transmission occasion of a transport block for a given RV sequence, see TS 38.214 [19], clause 6.1.2.3.1. |
timeDomainAllocation Indicates a combination of start symbol and length and PUSCH mapping type, see TS 38.214 [19], clause 6.1.2 and TS 38.212 [17], clause 7.3.1. |
timeDomainOffset Offset related to the reference SFN indicated by timeReferenceSFN, see TS 38.321 [3], clause 5.8.2. |
timeReferenceSFN Indicates SFN used for determination of the offset of a resource in time domain. The UE uses the closest SFN with the indicated number preceding the reception of the configured grant configuration, see TS 38.321 [3], clause 5.8.2. If the field timeReferenceSFN is not present, the reference SFN is 0. |
transformPrecoder Enables or disables transform precoding for type1 and type2. If the field is absent, the UE enables or disables transform precoding in accordance with the field msg3-transformPrecoder in RACH-ConfigCommon, see TS 38.214 [19], clause 6.1.3. |
uci-OnPUSCH Selection between and configuration of dynamic and semi-static beta-offset. For Type 1 UL data transmission without grant, uci-OnPUSCH should be set to semiStatic. |
CG-COT-Sharing field descriptions |
---|
channelAccessPriority Indicates the Channel Access Priority Class that the gNB can assume when sharing the UE initiated COT (see 37.213 [48], clause 4.1.3). |
duration Indicates the number of DL transmission slots within UE initiated COT (see 37.213 [48], clause 4.1.3). |
offset Indicates the number of DL transmission slots from the end of the slot where CG-UCI is detected after which COT sharing can be used (see 37.213 [48], clause 4.1.3). |
CG-StartingOffsets field descriptions |
---|
cg-StartingFullBW-InsideCOT A set of configured grant PUSCH transmission starting offsets (see TS 38.211[16], Table 5.3.1-2) which indicates the length of a CP extension of the first symbol that is located before the configured resource when frequency domain resource allocation includes all interlaces in the allocated RB set(s) and the CG PUSCH resource is inside gNB COT (see TS 38.214 [19], clause 6.1.2.3). |
cg-StartingFullBW-OutsideCOT A set of configured grant PUSCH transmission starting offset indices (see TS 38.211[16], Table 5.3.1-2) which indicates the length of a CP extension of the first symbol that is located before the configured resource when frequency domain resource allocation includes all interlaces in the allocated RB set(s) and the CG PUSCH resource is outside gNB COT (see TS 38.214 [19], clause 6.1.2.3). |
cg-StartingPartialBW-InsideCOT A set of configured grant PUSCH transmission starting offset index (see TS 38.211[16], Table 5.3.1-2) which indicates the length of a CP extension of the first symbol that is located before the configured resource when frequency domain resource allocation does not include all interlaces in the allocated RB set(s) and the CG PUSCH resource is inside gNB COT (see TS 38.214 [19], clause 6.1.2.3). |
cg-StartingPartialBW-OutsideCOT A set of configured grant PUSCH transmission starting offset index (see TS 38.211[16], Table 5.3.1-2) which indicates the length of a CP extension of the first symbol that is located before the configured resource when frequency domain resource allocation does not include all interlaces in the allocated RB set(s) and the CG PUSCH resource is outside gNB COT (see TS 38.214 [19], clause 6.1.2.3). |
Conditional Presence | Explanation |
---|---|
LCH-BasedPrioritization | This field is optionally present, Need R, if lch-BasedPrioritization is configured in the MAC entity. It is absent otherwise. |
RepTypeB | The field is optionally present if pusch-RepTypeIndicator is set to pusch-RepTypeB, Need S, and absent otherwise. |
CG-List | The field is mandatory present when included in configuredGrantConfigToAddModList-r16, otherwise the field is absent. |
CG-IndexMAC | The field is mandatory present if at least one configured grant is configured by configuredGrantConfigToAddModList-r16 in any BWP of this MAC entity, otherwise it is optionally present, need R. |
The IE ConfiguredGrantConfigIndex is used to indicate the index of one of multiple UL Configured Grant configurations in one BWP.
The IE ConfiguredGrantConfigIndexMAC is used to indicate the unique Configured Grant configurations index per MAC entity.
The IE ConnEstFailureControl is used to configure parameters for connection establishment failure control.
-- ASN1START -- TAG-CONNESTFAILURECONTROL-START ConnEstFailureControl ::= SEQUENCE {connEstFailCountNumber of times that the UE detects T300 expiry on the same cell before applying connEstFailOffset.ENUMERATED {n1, n2, n3, n4},connEstFailOffsetValidityAmount of time that the UE applies connEstFailOffset before removing the offset from evaluation of the cell. Value s30 corresponds to 30 seconds, value s60 corresponds to 60 seconds, and so on.ENUMERATED {s30, s60, s120, s240, s300, s420, s600, s900},connEstFailOffsetParameter "Qoffsettemp" in TS 38.304 [20]. If the field is absent, the value of infinity shall be used for "Qoffsettemp".INTEGER (0..15) OPTIONAL -- Need S } -- TAG-CONNESTFAILURECONTROL-STOP -- ASN1STOP
ConnEstFailureControl field descriptions |
---|
connEstFailCount Number of times that the UE detects T300 expiry on the same cell before applying connEstFailOffset. |
connEstFailOffset Parameter "Qoffsettemp" in TS 38.304 [20]. If the field is absent, the value of infinity shall be used for "Qoffsettemp". |
connEstFailOffsetValidity Amount of time that the UE applies connEstFailOffset before removing the offset from evaluation of the cell. Value s30 corresponds to 30 seconds, value s60 corresponds to 60 seconds, and so on. |
The IE ControlResourceSet is used to configure a time/frequency control resource set (CORESET) in which to search for downlink control information (see TS 38.213 [13], clause 10.1).
-- ASN1START -- TAG-CONTROLRESOURCESET-START ControlResourceSet ::= SEQUENCE {controlResourceSetIdIdentifies the instance of the ControlResourceSet IE. Value 0 identifies the common CORESET configured in MIB and in ServingCellConfigCommon (controlResourceSetZero) and is hence not used here in the ControlResourceSet IE. Other values identify CORESETs configured by dedicated signalling or in SIB1. The controlResourceSetId is unique among the BWPs of a serving cell. If the field controlResourceSetId-v1610 is present, the UE shall ignore the controlResourceSetId field (without suffix).ControlResourceSetId,frequencyDomainResourcesFrequency domain resources for the CORESET. Each bit corresponds a group of 6 RBs, with grouping starting from the first RB group in the BWP. When at least one search space is configured with freqMonitorLocation-r16, only the first bits are valid (see TS 38.213 [13], clause 10.1). The first (left-most / most significant) bit corresponds to the first RB group in the BWP, and so on. A bit that is set to 1 indicates that this RB group belongs to the frequency domain resource of this CORESET. Bits corresponding to a group of RBs not fully contained in the bandwidth part within which the CORESET is configured are set to zero (see TS 38.211 [16], clause 7.3.2.2).BIT STRING (SIZE (45)),durationContiguous time duration of the CORESET in number of symbols (see TS 38.211 [16], clause 7.3.2.2).INTEGER (1..maxCoReSetDuration),cce-REG-MappingTypeMapping of Control Channel Elements (CCE) to Resource Element Groups (REG) (see TS 38.211 [16], clauses 7.3.2.2 and 7.4.1.3.2).CHOICE { interleaved SEQUENCE {reg-BundleSizeResource Element Groups (REGs) can be bundled to create REG bundles. This parameter defines the size of such bundles (see TS 38.211 [16], clause 7.3.2.2).ENUMERATED {n2, n3, n6},interleaverSizeInterleaver-size (see TS 38.211 [16], clause 7.3.2.2).ENUMERATED {n2, n3, n6},shiftIndexWhen the field is absent the UE applies the value of the physCellIdconfigured for this serving cell (see TS 38.211 [16], clause 7.3.2.2).INTEGER(0..maxNrofPhysicalResourceBlocks-1) OPTIONAL -- Need S }, nonInterleaved NULL },precoderGranularityPrecoder granularity in frequency domain (see TS 38.211 [16], clauses 7.3.2.2 and 7.4.1.3.2).ENUMERATED {sameAsREG-bundle, allContiguousRBs},tci-StatesPDCCH-ToAddListA subset of the TCI states defined in pdsch-Config included in the BWP-DownlinkDedicated corresponding to the serving cell and to the DL BWP to which the ControlResourceSet belong to. They are used for providing QCL relationships between the DL RS(s) in one RS Set (TCI-State) and the PDCCH DMRS ports (see TS 38.213 [13], clause 6.). The network configures at most maxNrofTCI-StatesPDCCH entries.SEQUENCE(SIZE(1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL, -- Cond NotSIB1-initialBWP tci-StatesPDCCH-ToReleaseList SEQUENCE(SIZE(1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL, -- Cond NotSIB1-initialBWPtci-PresentInDCIThis field indicates if TCI field is present or absent in DCI format 1_1. When the field is absent the UE considers the TCI to be absent/disabled. In case of cross carrier scheduling, the network sets this field to enabled for the ControlResourceSet used for cross carrier scheduling in DCI format 1_1 in the scheduling cell if enableDefaultBeamForCCS is not configured (see TS 38.214 [19], clause 5.1.5).ENUMERATED {enabled} OPTIONAL, -- Need Spdcch-DMRS-ScramblingIDPDCCH DMRS scrambling initialization (see TS 38.211 [16], clause 7.4.1.3.1). When the field is absent the UE applies the value of the physCellId configured for this serving cell.INTEGER (0..65535) OPTIONAL, -- Need S ..., [[rb-Offset-r16Indicates the RB level offset in units of RB from the first RB of the first 6RB group to the first RB of BWP (see 38.213 [13], clause 10.1).INTEGER (0..5) OPTIONAL, -- Need Stci-PresentDCI-1-2-r16Configures the number of bits for "Transmission configuration indicator" in DCI format 1_2. When the field is absent the UE applies the value of 0 bit for the "Transmission configuration indicator" in DCI format 1_2 (see TS 38.212[17], clause 7.3.1 and TS 38.214[19], clause 5.1.5). In case of cross carrier scheduling, the network configures this field for the ControlResourceSet used for cross carrier scheduling in DCI format 1_2 in the scheduling cell if enableDefaultBeamForCCS is not configured (see TS 38.214 [19], clause 5.1.5).INTEGER (1..3) OPTIONAL, -- Need ScoresetPoolIndex-r16The index of the CORESET pool for this CORESET as specified in TS 38.213 [13] (clauses 9 and 10) and TS 38.214 [19] (clauses 5.1 and 6.1). If the field is absent, the UE applies the value 0.INTEGER (0..1) OPTIONAL, -- Need S controlResourceSetId-v1610 ControlResourceSetId-v1610 OPTIONAL -- Need S ]] } -- TAG-CONTROLRESOURCESET-STOP -- ASN1STOP
ControlResourceSet field descriptions |
---|
cce-REG-MappingType Mapping of Control Channel Elements (CCE) to Resource Element Groups (REG) (see TS 38.211 [16], clauses 7.3.2.2 and 7.4.1.3.2). |
controlResourceSetId Identifies the instance of the ControlResourceSet IE. Value 0 identifies the common CORESET configured in MIB and in ServingCellConfigCommon (controlResourceSetZero) and is hence not used here in the ControlResourceSet IE. Other values identify CORESETs configured by dedicated signalling or in SIB1. The controlResourceSetId is unique among the BWPs of a serving cell. If the field controlResourceSetId-v1610 is present, the UE shall ignore the controlResourceSetId field (without suffix). |
coresetPoolIndex The index of the CORESET pool for this CORESET as specified in TS 38.213 [13] (clauses 9 and 10) and TS 38.214 [19] (clauses 5.1 and 6.1). If the field is absent, the UE applies the value 0. |
duration Contiguous time duration of the CORESET in number of symbols (see TS 38.211 [16], clause 7.3.2.2). |
frequencyDomainResources Frequency domain resources for the CORESET. Each bit corresponds a group of 6 RBs, with grouping starting from the first RB group in the BWP. When at least one search space is configured with freqMonitorLocation-r16, only the first bits are valid (see TS 38.213 [13], clause 10.1). The first (left-most / most significant) bit corresponds to the first RB group in the BWP, and so on. A bit that is set to 1 indicates that this RB group belongs to the frequency domain resource of this CORESET. Bits corresponding to a group of RBs not fully contained in the bandwidth part within which the CORESET is configured are set to zero (see TS 38.211 [16], clause 7.3.2.2). |
interleaverSize Interleaver-size (see TS 38.211 [16], clause 7.3.2.2). |
pdcch-DMRS-ScramblingID PDCCH DMRS scrambling initialization (see TS 38.211 [16], clause 7.4.1.3.1). When the field is absent the UE applies the value of the physCellId configured for this serving cell. |
precoderGranularity Precoder granularity in frequency domain (see TS 38.211 [16], clauses 7.3.2.2 and 7.4.1.3.2). |
rb-Offset Indicates the RB level offset in units of RB from the first RB of the first 6RB group to the first RB of BWP (see 38.213 [13], clause 10.1). |
reg-BundleSize Resource Element Groups (REGs) can be bundled to create REG bundles. This parameter defines the size of such bundles (see TS 38.211 [16], clause 7.3.2.2). |
shiftIndex When the field is absent the UE applies the value of the physCellIdconfigured for this serving cell (see TS 38.211 [16], clause 7.3.2.2). |
tci-PresentInDCI This field indicates if TCI field is present or absent in DCI format 1_1. When the field is absent the UE considers the TCI to be absent/disabled. In case of cross carrier scheduling, the network sets this field to enabled for the ControlResourceSet used for cross carrier scheduling in DCI format 1_1 in the scheduling cell if enableDefaultBeamForCCS is not configured (see TS 38.214 [19], clause 5.1.5). |
tci-PresentDCI-1-2 Configures the number of bits for "Transmission configuration indicator" in DCI format 1_2. When the field is absent the UE applies the value of 0 bit for the "Transmission configuration indicator" in DCI format 1_2 (see TS 38.212[17], clause 7.3.1 and TS 38.214[19], clause 5.1.5). In case of cross carrier scheduling, the network configures this field for the ControlResourceSet used for cross carrier scheduling in DCI format 1_2 in the scheduling cell if enableDefaultBeamForCCS is not configured (see TS 38.214 [19], clause 5.1.5). |
tci-StatesPDCCH-ToAddList A subset of the TCI states defined in pdsch-Config included in the BWP-DownlinkDedicated corresponding to the serving cell and to the DL BWP to which the ControlResourceSet belong to. They are used for providing QCL relationships between the DL RS(s) in one RS Set (TCI-State) and the PDCCH DMRS ports (see TS 38.213 [13], clause 6.). The network configures at most maxNrofTCI-StatesPDCCH entries. |
Conditional Presence | Explanation |
---|---|
NotSIB1-initialBWP | The field is absent in SIB1 and in the PDCCH-ConfigCommon of the initial BWP in ServingCellConfigCommon, if SIB1 is broadcasted. Otherwise, it is optionally present, Need N. |
The ControlResourceSetId IE concerns a short identity, used to identify a control resource set within a serving cell. The ControlResourceSetId = 0 identifies the ControlResourceSet#0 configured via PBCH (MIB) and in controlResourceSetZero (ServingCellConfigCommon). The ID space is used across the BWPs of a Serving Cell.
-- ASN1START -- TAG-CONTROLRESOURCESETID-START ControlResourceSetId ::= INTEGER (0..maxNrofControlResourceSets-1) ControlResourceSetId-r16 ::= INTEGER (0..maxNrofControlResourceSets-1-r16) ControlResourceSetId-v1610 ::= INTEGER (maxNrofControlResourceSets..maxNrofControlResourceSets-1-r16) -- TAG-CONTROLRESOURCESETID-STOP -- ASN1STOP
The IE ControlResourceSetZero is used to configure CORESET#0 of the initial BWP (see TS 38.213 [13], clause 13).
The IE CrossCarrierSchedulingConfig is used to specify the configuration when the cross-carrier scheduling is used in a cell.
-- ASN1START -- TAG-CROSSCARRIERSCHEDULINGCONFIG-START CrossCarrierSchedulingConfig ::= SEQUENCE { schedulingCellInfo CHOICE {ownParameters for self-scheduling, i.e., a serving cell is scheduled by its own PDCCH.SEQUENCE { -- Cross carrier scheduling: scheduling cellcif-PresenceThe field is used to indicate whether carrier indicator field is present (value true) or not (value false) in PDCCH DCI formats, see TS 38.213 [13]. If cif-Presence is set to true, the CIF value indicating a grant or assignment for this cell is 0.BOOLEAN },otherParameters for cross-carrier scheduling, i.e., a serving cell is scheduled by a PDCCH on another (scheduling) cell. The network configures this field only for SCells.SEQUENCE { -- Cross carrier scheduling: scheduled cellschedulingCellIdIndicates which cell signals the downlink allocations and uplink grants, if applicable, for the concerned SCell. In case the UE is configured with DC, the scheduling cell is part of the same cell group (i.e. MCG or SCG) as the scheduled cell.In case the UE is configured with two PUCCH groups, the scheduling cell and the scheduled cell are within the same PUCCH group. If drx-ConfigSecondaryGroup is configured in the MAC-CellGroupConfig associated with this serving cell, the scheduling cell and the scheduled cell belong to the same Frequency Range. In addition, the serving cell with an aperiodic CSI trigger and the PUSCH resource scheduled for the report are on the same carrier and serving cell, but the cell for which CSI is reported may belong to the same or a different Frequency Range. The network should not trigger a CSI request for a serving cell in the other Frequency Range when that serving cell is outside Active Time.ServCellIndex,cif-InSchedulingCellThe field indicates the CIF value used in the scheduling cell to indicate a grant or assignment applicable for this cell, see TS 38.213 [13].INTEGER (1..7) } }, ..., [[ carrierIndicatorSize-r16 SEQUENCE { carrierIndicatorSizeDCI-1-2-r16 INTEGER (0..3), carrierIndicatorSizeDCI-0-2-r16 INTEGER (0..3) } OPTIONAL, -- Cond CIF-PRESENCEenableDefaultBeamForCCS-r16This field indicates whether default beam selection for cross-carrier scheduled PDSCH is enabled, see TS 38.214 [19]. If not present, the default beam selection behaviour is not applied, i.e. Rel-15 behaviour is applied.ENUMERATED {enabled} OPTIONAL -- Need S ]] } -- TAG-CROSSCARRIERSCHEDULINGCONFIG-STOP -- ASN1STOP
CrossCarrierSchedulingConfig field descriptions |
---|
carrierIndicatorSizeDCI-0-2, carrierIndicatorSizeDCI-1-2 Configures the number of bits for the field of carrier indicator in PDCCH DCI format 0_2/1_2. The field carrierIndicatorSizeDCI-0-2 refers to DCI format 0_2 and the field carrierIndicatorSizeDCI-1-2 refers to DCI format 1_2, respectively (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 10.1). |
cif-Presence The field is used to indicate whether carrier indicator field is present (value true) or not (value false) in PDCCH DCI formats, see TS 38.213 [13]. If cif-Presence is set to true, the CIF value indicating a grant or assignment for this cell is 0. |
cif-InSchedulingCell The field indicates the CIF value used in the scheduling cell to indicate a grant or assignment applicable for this cell, see TS 38.213 [13]. |
enableDefaultBeamForCCS This field indicates whether default beam selection for cross-carrier scheduled PDSCH is enabled, see TS 38.214 [19]. If not present, the default beam selection behaviour is not applied, i.e. Rel-15 behaviour is applied. |
other Parameters for cross-carrier scheduling, i.e., a serving cell is scheduled by a PDCCH on another (scheduling) cell. The network configures this field only for SCells. |
own Parameters for self-scheduling, i.e., a serving cell is scheduled by its own PDCCH. |
schedulingCellId Indicates which cell signals the downlink allocations and uplink grants, if applicable, for the concerned SCell. In case the UE is configured with DC, the scheduling cell is part of the same cell group (i.e. MCG or SCG) as the scheduled cell.In case the UE is configured with two PUCCH groups, the scheduling cell and the scheduled cell are within the same PUCCH group. If drx-ConfigSecondaryGroup is configured in the MAC-CellGroupConfig associated with this serving cell, the scheduling cell and the scheduled cell belong to the same Frequency Range. In addition, the serving cell with an aperiodic CSI trigger and the PUSCH resource scheduled for the report are on the same carrier and serving cell, but the cell for which CSI is reported may belong to the same or a different Frequency Range. The network should not trigger a CSI request for a serving cell in the other Frequency Range when that serving cell is outside Active Time. |
Conditional Presence | Explanation |
---|---|
CIF-PRESENCE | The field is mandatory present if the cif-Presence is set to true. The field is absent otherwise. |
The CSI-AperiodicTriggerStateList IE is used to configure the UE with a list of aperiodic trigger states. Each codepoint of the DCI field "CSI request" is associated with one trigger state (see TS 38.321 [3], clause 6.1.3.13). Upon reception of the value associated with a trigger state, the UE will perform measurement of CSI-RS, CSI-IM and/or SSB (reference signals) and aperiodic reporting on L1 according to all entries in the associatedReportConfigInfoList for that trigger state.
-- ASN1START -- TAG-CSI-APERIODICTRIGGERSTATELIST-START CSI-AperiodicTriggerStateList ::= SEQUENCE (SIZE (1..maxNrOfCSI-AperiodicTriggers)) OF CSI-AperiodicTriggerState CSI-AperiodicTriggerState ::= SEQUENCE { associatedReportConfigInfoList SEQUENCE (SIZE(1..maxNrofReportConfigPerAperiodicTrigger)) OF CSI-AssociatedReportConfigInfo, ... } CSI-AssociatedReportConfigInfo ::= SEQUENCE {reportConfigIdThe reportConfigId of one of the CSI-ReportConfigToAddMod configured in CSI-MeasConfigCSI-ReportConfigId, resourcesForChannel CHOICE { nzp-CSI-RS SEQUENCE {resourceSetNZP-CSI-RS-ResourceSet for channel measurements. Entry number in nzp-CSI-RS-ResourceSetList in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement in the CSI-ReportConfig indicated by reportConfigId above (value 1 corresponds to the first entry, value 2 to thesecond entry, and so on).INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig),qcl-infoList of references to TCI-States for providing the QCL source and QCL type for each NZP-CSI-RS-Resource listed in nzp-CSI-RS-Resources of the NZP-CSI-RS-ResourceSet indicated by resourceSetwithin nzp-CSI-RS. Each TCI-StateId refers to the TCI-State which has this value for tci-StateId and is defined in tci-StatesToAddModList in the PDSCH-Config included in the BWP-Downlink corresponding to the serving cell and to the DL BWP to which the resourcesForChannelMeasurement (in the CSI-ReportConfig indicated by reportConfigId above) belong to. First entry in qcl-info corresponds to first entry in nzp-CSI-RS-Resources of that NZP-CSI-RS-ResourceSet, second entry in qcl-info corresponds to second entry in nzp-CSI-RS-Resources, and so on (see TS 38.214 [19], clause 5.2.1.5.1)SEQUENCE (SIZE(1..maxNrofAP-CSI-RS-ResourcesPerSet)) OF TCI-StateId OPTIONAL -- Cond Aperiodic },csi-SSB-ResourceSetCSI-SSB-ResourceSet for channel measurements. Entry number in csi-SSB-ResourceSetList in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement in the CSI-ReportConfig indicated by reportConfigId above (value 1 corresponds to the first entry, value 2 to the second entry, and so on).INTEGER (1..maxNrofCSI-SSB-ResourceSetsPerConfig) },csi-IM-ResourcesForInterferenceCSI-IM-ResourceSet for interference measurement. Entry number in csi-IM-ResourceSetList in the CSI-ResourceConfig indicated by csi-IM-ResourcesForInterference in the CSI-ReportConfig indicated by reportConfigId above (value 1 corresponds to the first entry, value 2 to the second entry, and so on). The indicated CSI-IM-ResourceSet should have exactly the same number of resources like the NZP-CSI-RS-ResourceSet indicated in resourceSetwithin nzp-CSI-RS.INTEGER(1..maxNrofCSI-IM-ResourceSetsPerConfig) OPTIONAL, -- Cond CSI-IM-ForInterferencenzp-CSI-RS-ResourcesForInterferenceNZP-CSI-RS-ResourceSet for interference measurement. Entry number in nzp-CSI-RS-ResourceSetList in the CSI-ResourceConfig indicated by nzp-CSI-RS-ResourcesForInterference in the CSI-ReportConfig indicated by reportConfigId above (value 1 corresponds to the first entry, value 2 to the second entry, and so on).INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig) OPTIONAL, -- Cond NZP-CSI-RS-ForInterference ... } -- TAG-CSI-APERIODICTRIGGERSTATELIST-STOP -- ASN1STOP
CSI-AssociatedReportConfigInfo field descriptions |
---|
csi-IM-ResourcesForInterference CSI-IM-ResourceSet for interference measurement. Entry number in csi-IM-ResourceSetList in the CSI-ResourceConfig indicated by csi-IM-ResourcesForInterference in the CSI-ReportConfig indicated by reportConfigId above (value 1 corresponds to the first entry, value 2 to the second entry, and so on). The indicated CSI-IM-ResourceSet should have exactly the same number of resources like the NZP-CSI-RS-ResourceSet indicated in resourceSetwithin nzp-CSI-RS. |
csi-SSB-ResourceSet CSI-SSB-ResourceSet for channel measurements. Entry number in csi-SSB-ResourceSetList in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement in the CSI-ReportConfig indicated by reportConfigId above (value 1 corresponds to the first entry, value 2 to the second entry, and so on). |
nzp-CSI-RS-ResourcesForInterference NZP-CSI-RS-ResourceSet for interference measurement. Entry number in nzp-CSI-RS-ResourceSetList in the CSI-ResourceConfig indicated by nzp-CSI-RS-ResourcesForInterference in the CSI-ReportConfig indicated by reportConfigId above (value 1 corresponds to the first entry, value 2 to the second entry, and so on). |
qcl-info List of references to TCI-States for providing the QCL source and QCL type for each NZP-CSI-RS-Resource listed in nzp-CSI-RS-Resources of the NZP-CSI-RS-ResourceSet indicated by resourceSetwithin nzp-CSI-RS. Each TCI-StateId refers to the TCI-State which has this value for tci-StateId and is defined in tci-StatesToAddModList in the PDSCH-Config included in the BWP-Downlink corresponding to the serving cell and to the DL BWP to which the resourcesForChannelMeasurement (in the CSI-ReportConfig indicated by reportConfigId above) belong to. First entry in qcl-info corresponds to first entry in nzp-CSI-RS-Resources of that NZP-CSI-RS-ResourceSet, second entry in qcl-info corresponds to second entry in nzp-CSI-RS-Resources, and so on (see TS 38.214 [19], clause 5.2.1.5.1) |
reportConfigId The reportConfigId of one of the CSI-ReportConfigToAddMod configured in CSI-MeasConfig |
resourceSet NZP-CSI-RS-ResourceSet for channel measurements. Entry number in nzp-CSI-RS-ResourceSetList in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement in the CSI-ReportConfig indicated by reportConfigId above (value 1 corresponds to the first entry, value 2 to thesecond entry, and so on). |
Conditional Presence | Explanation |
---|---|
Aperiodic | The field is mandatory present if the NZP-CSI-RS-Resources in the associated resourceSet have the resourceType aperiodic. The field is absent otherwise. |
CSI-IM-ForInterference | This field is mandatory present if the CSI-ReportConfig identified by reportConfigId is configured with csi-IM-ResourcesForInterference; otherwise it is absent. |
NZP-CSI-RS-ForInterference | This field is mandatory present if the CSI-ReportConfig identified by reportConfigId is configured with nzp-CSI-RS-ResourcesForInterference; otherwise it is absent. |
The IE CSI-FrequencyOccupation is used to configure the frequency domain occupation of a channel state information measurement resource (e.g. NZP-CSI-RS-Resource, CSI-IM-Resource).
-- ASN1START -- TAG-CSI-FREQUENCYOCCUPATION-START CSI-FrequencyOccupation ::= SEQUENCE {startingRBPRB where this CSI resource starts in relation to common resource block #0 (CRB#0) on the common resource block grid. Only multiples of 4 are allowed (0, 4, ...)INTEGER (0..maxNrofPhysicalResourceBlocks-1),nrofRBsNumber of PRBs across which this CSI resource spans. Only multiples of 4 are allowed. The smallest configurable number is the minimum of 24 and the width of the associated BWP. If the configured value is larger than the width of the corresponding BWP, the UE shall assume that the actual CSI-RS bandwidth is equal to the width of the BWP.INTEGER (24..maxNrofPhysicalResourceBlocksPlus1), ... } -- TAG-CSI-FREQUENCYOCCUPATION-STOP -- ASN1STOP
CSI-FrequencyOccupation field descriptions |
---|
nrofRBs Number of PRBs across which this CSI resource spans. Only multiples of 4 are allowed. The smallest configurable number is the minimum of 24 and the width of the associated BWP. If the configured value is larger than the width of the corresponding BWP, the UE shall assume that the actual CSI-RS bandwidth is equal to the width of the BWP. |
startingRB PRB where this CSI resource starts in relation to common resource block #0 (CRB#0) on the common resource block grid. Only multiples of 4 are allowed (0, 4, ...) |
The IE CSI-IM-Resource is used to configure one CSI Interference Management (IM) resource.
-- ASN1START -- TAG-CSI-IM-RESOURCE-START CSI-IM-Resource ::= SEQUENCE { csi-IM-ResourceId CSI-IM-ResourceId,csi-IM-ResourceElementPatternThe resource element pattern (Pattern0 (2,2) or Pattern1 (4,1)) with corresponding parameters (see TS 38.214 [19], clause 5.2.2.4)CHOICE { pattern0 SEQUENCE {subcarrierLocation-p0OFDM subcarrier occupancy of the CSI-IM resource for Pattern0 (see TS 38.214 [19], clause 5.2.2.4)ENUMERATED { s0, s2, s4, s6, s8, s10 },symbolLocation-p0OFDM symbol location of the CSI-IM resource for Pattern0 (see TS 38.214 [19], clause 5.2.2.4)INTEGER (0..12) }, pattern1 SEQUENCE {subcarrierLocation-p1OFDM subcarrier occupancy of the CSI-IM resource for Pattern1 (see TS 38.214 [19], clause 5.2.2.4)ENUMERATED { s0, s4, s8 },symbolLocation-p1OFDM symbol location of the CSI-IM resource for Pattern1 (see TS 38.214 [19], clause 5.2.2.4)INTEGER (0..13) } } OPTIONAL, -- Need MfreqBandFrequency-occupancy of CSI-IM (see TS 38.214 [19], clause 5.2.2.4)CSI-FrequencyOccupation OPTIONAL, -- Need MperiodicityAndOffsetPeriodicity and slot offset for periodic/semi-persistent CSI-IM. Network always configures the UE with a value for this field for periodic and semi-persistent CSI-IM-Resources (as indicated in CSI-ResourceConfig). A change of configuration between periodic or semi-persistent and aperiodic for a CSI-IM-Resource is not supported without a release and add.CSI-ResourcePeriodicityAndOffset OPTIONAL, -- Cond PeriodicOrSemiPersistent ... } -- TAG-CSI-IM-RESOURCE-STOP -- ASN1STOP
CSI-IM-Resource field descriptions |
---|
csi-IM-ResourceElementPattern The resource element pattern (Pattern0 (2,2) or Pattern1 (4,1)) with corresponding parameters (see TS 38.214 [19], clause 5.2.2.4) |
freqBand Frequency-occupancy of CSI-IM (see TS 38.214 [19], clause 5.2.2.4) |
periodicityAndOffset Periodicity and slot offset for periodic/semi-persistent CSI-IM. Network always configures the UE with a value for this field for periodic and semi-persistent CSI-IM-Resources (as indicated in CSI-ResourceConfig). A change of configuration between periodic or semi-persistent and aperiodic for a CSI-IM-Resource is not supported without a release and add. |
subcarrierLocation-p0 OFDM subcarrier occupancy of the CSI-IM resource for Pattern0 (see TS 38.214 [19], clause 5.2.2.4) |
subcarrierLocation-p1 OFDM subcarrier occupancy of the CSI-IM resource for Pattern1 (see TS 38.214 [19], clause 5.2.2.4) |
symbolLocation-p0 OFDM symbol location of the CSI-IM resource for Pattern0 (see TS 38.214 [19], clause 5.2.2.4) |
symbolLocation-p1 OFDM symbol location of the CSI-IM resource for Pattern1 (see TS 38.214 [19], clause 5.2.2.4) |
Conditional Presence | Explanation |
---|---|
PeriodicOrSemiPersistent | The field is optionally present, Need M, for periodic and semi-persistent CSI-IM-Resources (as indicated in CSI-ResourceConfig). The field is absent otherwise. |
The IE CSI-IM-ResourceId is used to identify one CSI-IM-Resource.
The IE CSI-IM-ResourceSet is used to configure a set of one or more CSI Interference Management (IM) resources (their IDs) and set-specific parameters.
-- ASN1START -- TAG-CSI-IM-RESOURCESET-START CSI-IM-ResourceSet ::= SEQUENCE { csi-IM-ResourceSetId CSI-IM-ResourceSetId,csi-IM-ResourcesCSI-IM-Resources associated with this CSI-IM-ResourceSet (see TS 38.214 [19], clause 5.2).SEQUENCE (SIZE(1..maxNrofCSI-IM-ResourcesPerSet)) OF CSI-IM-ResourceId, ... } -- TAG-CSI-IM-RESOURCESET-STOP -- ASN1STOP
CSI-IM-ResourceSet field descriptions |
---|
csi-IM-Resources CSI-IM-Resources associated with this CSI-IM-ResourceSet (see TS 38.214 [19], clause 5.2). |
The IE CSI-IM-ResourceSetId is used to identify CSI-IM-ResourceSets.
The IE CSI-MeasConfig is used to configure CSI-RS (reference signals) belonging to the serving cell in which CSI-MeasConfig is included, channel state information reports to be transmitted on PUCCH on the serving cell in which CSI-MeasConfig is included and channel state information reports on PUSCH triggered by DCI received on the serving cell in which CSI-MeasConfig is included. See also TS 38.214 [19], clause 5.2.
-- ASN1START -- TAG-CSI-MEASCONFIG-START CSI-MeasConfig ::= SEQUENCE {nzp-CSI-RS-ResourceToAddModListPool of NZP-CSI-RS-Resource which can be referred to from NZP-CSI-RS-ResourceSet.SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP-CSI-RS-Resource OPTIONAL, -- Need N nzp-CSI-RS-ResourceToReleaseList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP-CSI-RS-ResourceId OPTIONAL, -- Need Nnzp-CSI-RS-ResourceSetToAddModListPool of NZP-CSI-RS-ResourceSet which can be referred to from CSI-ResourceConfig or from MAC CEs.SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSets)) OF NZP-CSI-RS-ResourceSet OPTIONAL, -- Need N nzp-CSI-RS-ResourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSets)) OF NZP-CSI-RS-ResourceSetId OPTIONAL, -- Need Ncsi-IM-ResourceToAddModListPool of CSI-IM-Resource which can be referred to from CSI-IM-ResourceSet.SEQUENCE (SIZE (1..maxNrofCSI-IM-Resources)) OF CSI-IM-Resource OPTIONAL, -- Need N csi-IM-ResourceToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-IM-Resources)) OF CSI-IM-ResourceId OPTIONAL, -- Need Ncsi-IM-ResourceSetToAddModListPool of CSI-IM-ResourceSet which can be referred to from CSI-ResourceConfig or from MAC CEs.SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSets)) OF CSI-IM-ResourceSet OPTIONAL, -- Need N csi-IM-ResourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSets)) OF CSI-IM-ResourceSetId OPTIONAL, -- Need Ncsi-SSB-ResourceSetToAddModListPool of CSI-SSB-ResourceSet which can be referred to from CSI-ResourceConfig.SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSets)) OF CSI-SSB-ResourceSet OPTIONAL, -- Need N csi-SSB-ResourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSets)) OF CSI-SSB-ResourceSetId OPTIONAL, -- Need Ncsi-ResourceConfigToAddModListConfigured CSI resource settings as specified in TS 38.214 [19] clause 5.2.1.2.SEQUENCE (SIZE (1..maxNrofCSI-ResourceConfigurations)) OF CSI-ResourceConfig OPTIONAL, -- Need N csi-ResourceConfigToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-ResourceConfigurations)) OF CSI-ResourceConfigId OPTIONAL, -- Need Ncsi-ReportConfigToAddModListConfigured CSI report settings as specified in TS 38.214 [19] clause 5.2.1.1.SEQUENCE (SIZE (1..maxNrofCSI-ReportConfigurations)) OF CSI-ReportConfig OPTIONAL, -- Need N csi-ReportConfigToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-ReportConfigurations)) OF CSI-ReportConfigId OPTIONAL, -- Need N reportTriggerSize INTEGER (0..6) OPTIONAL, -- Need MaperiodicTriggerStateListContains trigger states for dynamically selecting one or more aperiodic and semi-persistent reporting configurations and/or triggering one or more aperiodic CSI-RS resource sets for channel and/or interference measurement (see TS 38.214 [19], clause 5.2.1).SetupRelease { CSI-AperiodicTriggerStateList } OPTIONAL, -- Need M semiPersistentOnPUSCH-TriggerStateList SetupRelease { CSI-SemiPersistentOnPUSCH-TriggerStateList } OPTIONAL, -- Need M ..., [[ reportTriggerSizeDCI-0-2-r16 INTEGER (0..6) OPTIONAL -- Need R ]] } -- TAG-CSI-MEASCONFIG-STOP -- ASN1STOP
CSI-MeasConfig field descriptions |
---|
aperiodicTriggerStateList Contains trigger states for dynamically selecting one or more aperiodic and semi-persistent reporting configurations and/or triggering one or more aperiodic CSI-RS resource sets for channel and/or interference measurement (see TS 38.214 [19], clause 5.2.1). |
csi-IM-ResourceSetToAddModList Pool of CSI-IM-ResourceSet which can be referred to from CSI-ResourceConfig or from MAC CEs. |
csi-IM-ResourceToAddModList Pool of CSI-IM-Resource which can be referred to from CSI-IM-ResourceSet. |
csi-ReportConfigToAddModList Configured CSI report settings as specified in TS 38.214 [19] clause 5.2.1.1. |
csi-ResourceConfigToAddModList Configured CSI resource settings as specified in TS 38.214 [19] clause 5.2.1.2. |
csi-SSB-ResourceSetToAddModList Pool of CSI-SSB-ResourceSet which can be referred to from CSI-ResourceConfig. |
nzp-CSI-RS-ResourceSetToAddModList Pool of NZP-CSI-RS-ResourceSet which can be referred to from CSI-ResourceConfig or from MAC CEs. |
nzp-CSI-RS-ResourceToAddModList Pool of NZP-CSI-RS-Resource which can be referred to from NZP-CSI-RS-ResourceSet. |
reportTriggerSize, reportTriggerSizeDCI-0-2 Size of CSI request field in DCI (bits) (see TS 38.214 [19], clause 5.2.1.5.1). The field reportTriggerSizeapplies to DCI format 0_1 and the field reportTriggerSizeDCI-0-2applies to DCI format 0_2 (see TS 38.214 [19], clause 5.2.1.5.1). |
The IE CSI-ReportConfig is used to configure a periodic or semi-persistent report sent on PUCCH on the cell in which the CSI-ReportConfig is included, or to configure a semi-persistent or aperiodic report sent on PUSCH triggered by DCI received on the cell in which the CSI-ReportConfig is included (in this case, the cell on which the report is sent is determined by the received DCI). See TS 38.214 [19], clause 5.2.1.
-- ASN1START -- TAG-CSI-REPORTCONFIG-START CSI-ReportConfig ::= SEQUENCE { reportConfigId CSI-ReportConfigId,carrierIndicates in which serving cell the CSI-ResourceConfig indicated below are to be found. If the field is absent, the resources are on the same serving cell as this report configuration.ServCellIndex OPTIONAL, -- Need SresourcesForChannelMeasurementResources for channel measurement. csi-ResourceConfigId of a CSI-ResourceConfig included in the configuration of the serving cell indicated with the field "carrier" above. The CSI-ResourceConfig indicated here contains only NZP-CSI-RS resources and/or SSB resources. This CSI-ReportConfig is associated with the DL BWP indicated by bwp-Id in that CSI-ResourceConfig.CSI-ResourceConfigId,csi-IM-ResourcesForInterferenceCSI IM resources for interference measurement. csi-ResourceConfigId of a CSI-ResourceConfig included in the configuration of the serving cell indicated with the field "carrier" above. The CSI-ResourceConfig indicated here contains only CSI-IM resources. The bwp-Id in that CSI-ResourceConfig is the same value as the bwp-Id in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement.CSI-ResourceConfigId OPTIONAL, -- Need Rnzp-CSI-RS-ResourcesForInterferenceNZP CSI RS resources for interference measurement. csi-ResourceConfigId of a CSI-ResourceConfig included in the configuration of the serving cell indicated with the field "carrier" above. The CSI-ResourceConfig indicated here contains only NZP-CSI-RS resources. The bwp-Id in that CSI-ResourceConfig is the same value as the bwp-Id in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement.CSI-ResourceConfigId OPTIONAL, -- Need RreportConfigTypeTime domain behavior of reporting configuration.CHOICE { periodic SEQUENCE {reportSlotConfigPeriodicity and slot offset (see TS 38.214 [19], clause 5.2.1.4). If the field reportSlotConfig-v1530 is present, the UE shall ignore the value provided in reportSlotConfig (without suffix).CSI-ReportPeriodicityAndOffset,pucch-CSI-ResourceListIndicates which PUCCH resource to use for reporting on PUCCH.SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource }, semiPersistentOnPUCCH SEQUENCE {reportSlotConfigPeriodicity and slot offset (see TS 38.214 [19], clause 5.2.1.4). If the field reportSlotConfig-v1530 is present, the UE shall ignore the value provided in reportSlotConfig (without suffix).CSI-ReportPeriodicityAndOffset,pucch-CSI-ResourceListIndicates which PUCCH resource to use for reporting on PUCCH.SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource }, semiPersistentOnPUSCH SEQUENCE {reportSlotConfigPeriodicity and slot offset (see TS 38.214 [19], clause 5.2.1.4). If the field reportSlotConfig-v1530 is present, the UE shall ignore the value provided in reportSlotConfig (without suffix).ENUMERATED {sl5, sl10, sl20, sl40, sl80, sl160, sl320}, reportSlotOffsetList SEQUENCE (SIZE (1.. maxNrofUL-Allocations)) OF INTEGER(0..32),p0alphaIndex of the p0-alpha set determining the power control for this CSI report transmission (see TS 38.214 [19], clause 6.2.1.2).P0-PUSCH-AlphaSetId }, aperiodic SEQUENCE { reportSlotOffsetList SEQUENCE (SIZE (1..maxNrofUL-Allocations)) OF INTEGER(0..32) } },reportQuantityThe CSI related quantities to report. see TS 38.214 [19], clause 5.2.1. If the field reportQuantity-r16 is present, UE shall ignore reportQuantity (without suffix).CHOICE { none NULL, cri-RI-PMI-CQI NULL, cri-RI-i1 NULL, cri-RI-i1-CQI SEQUENCE {pdsch-BundleSizeForCSIPRB bundling size to assume for CQI calculation when reportQuantity is CRI/RI/i1/CQI. If the field is absent, the UE assumes that no PRB bundling is applied (see TS 38.214 [19], clause 5.2.1.4.2).ENUMERATED {n2, n4} OPTIONAL -- Need S }, cri-RI-CQI NULL, cri-RSRP NULL, ssb-Index-RSRP NULL, cri-RI-LI-PMI-CQI NULL },reportFreqConfigurationReporting configuration in the frequency domain. (see TS 38.214 [19], clause 5.2.1.4).SEQUENCE {cqi-FormatIndicatorIndicates whether the UE shall report a single (wideband) or multiple (subband) CQI (see TS 38.214 [19], clause 5.2.1.4).ENUMERATED { widebandCQI, subbandCQI } OPTIONAL, -- Need Rpmi-FormatIndicatorIndicates whether the UE shall report a single (wideband) or multiple (subband) PMI. (see TS 38.214 [19], clause 5.2.1.4).ENUMERATED { widebandPMI, subbandPMI } OPTIONAL, -- Need Rcsi-ReportingBandIndicates a contiguous or non-contiguous subset of subbands in the bandwidth part which CSI shall be reported for. Each bit in the bit-string represents one subband. The right-most bit in the bit string represents the lowest subband in the BWP. The choice determines the number of subbands (subbands3 for 3 subbands, subbands4 for 4 subbands, and so on) (see TS 38.214 [19], clause 5.2.1.4). This field is absent if there are less than 24 PRBs (no sub band) and present otherwise(see TS 38.214 [19], clause 5.2.1.4).CHOICE { subbands3 BIT STRING(SIZE(3)), subbands4 BIT STRING(SIZE(4)), subbands5 BIT STRING(SIZE(5)), subbands6 BIT STRING(SIZE(6)), subbands7 BIT STRING(SIZE(7)), subbands8 BIT STRING(SIZE(8)), subbands9 BIT STRING(SIZE(9)), subbands10 BIT STRING(SIZE(10)), subbands11 BIT STRING(SIZE(11)), subbands12 BIT STRING(SIZE(12)), subbands13 BIT STRING(SIZE(13)), subbands14 BIT STRING(SIZE(14)), subbands15 BIT STRING(SIZE(15)), subbands16 BIT STRING(SIZE(16)), subbands17 BIT STRING(SIZE(17)), subbands18 BIT STRING(SIZE(18)), ..., subbands19-v1530 BIT STRING(SIZE(19)) } OPTIONAL -- Need S } OPTIONAL, -- Need RtimeRestrictionForChannelMeasurementsTime domain measurement restriction for the channel (signal) measurements (see TS 38.214 [19], clause 5.2.1.1).ENUMERATED {configured, notConfigured},timeRestrictionForInterferenceMeasurementsTime domain measurement restriction for interference measurements (see TS 38.214 [19], clause 5.2.1.1).ENUMERATED {configured, notConfigured},codebookConfigCodebook configuration for Type-1 or Type-2 including codebook subset restriction. Network does not configure codebookConfig and codebookConfig-r16 simultaneously to a UECodebookConfig OPTIONAL, -- Need RdummyThis field is not used in the specification. If received it shall be ignored by the UE.ENUMERATED {n1, n2} OPTIONAL, -- Need RgroupBasedBeamReportingTurning on/off group beam based reporting (see TS 38.214 [19], clause 5.2.1.4).CHOICE { enabled NULL, disabled SEQUENCE {nrofReportedRSThe number (N) of measured RS resources to be reported per report setting in a non-group-based report. N <= N_max, where N_max is either 2 or 4 depending on UE capability. (see TS 38.214 [19], clause 5.2.1.4) When the field is absent the UE applies the value 1.ENUMERATED {n1, n2, n3, n4} OPTIONAL -- Need S } },cqi-TableWhich CQI table to use for CQI calculation (see TS 38.214 [19], clause 5.2.2.1).ENUMERATED {table1, table2, table3, spare1} OPTIONAL, -- Need RsubbandSizeIndicates one out of two possible BWP-dependent values for the subband size as indicated in TS 38.214 [19], table 5.2.1.4-2 . If csi-ReportingBand is absent, the UE shall ignore this field.ENUMERATED {value1, value2},non-PMI-PortIndicationPort indication for RI/CQI calculation. For each CSI-RS resource in the linked ResourceConfig for channel measurement, a port indication for each rank R, indicating which R ports to use. Applicable only for non-PMI feedback (see TS 38.214 [19], clause 5.2.1.4.2). The first entry in non-PMI-PortIndication corresponds to the NZP-CSI-RS-Resource indicated by the first entry in nzp-CSI-RS-Resources in the NZP-CSI-RS-ResourceSet indicated in the first entry of nzp-CSI-RS-ResourceSetList of the CSI-ResourceConfig whose CSI-ResourceConfigId is indicated in a CSI-MeasId together with the above CSI-ReportConfigId; the second entry in non-PMI-PortIndication corresponds to the NZP-CSI-RS-Resource indicated by the second entry in nzp-CSI-RS-Resources in the NZP-CSI-RS-ResourceSet indicated in the first entry of nzp-CSI-RS-ResourceSetList of the same CSI-ResourceConfig, and so on until the NZP-CSI-RS-Resource indicated by the last entry in nzp-CSI-RS-Resources in the in the NZP-CSI-RS-ResourceSet indicated in the first entry of nzp-CSI-RS-ResourceSetList of the same CSI-ResourceConfig. Then the next entry corresponds to the NZP-CSI-RS-Resource indicated by the first entry in nzp-CSI-RS-Resources in the NZP-CSI-RS-ResourceSet indicated in the second entry of nzp-CSI-RS-ResourceSetList of the same CSI-ResourceConfig and so on.SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerConfig)) OF PortIndexFor8Ranks OPTIONAL, -- Need R ..., [[ semiPersistentOnPUSCH-v1530 SEQUENCE { reportSlotConfig-v1530 ENUMERATED {sl4, sl8, sl16} } OPTIONAL -- Need R ]], [[ semiPersistentOnPUSCH-v1610 SEQUENCE { reportSlotOffsetListDCI-0-2-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL, -- Need R reportSlotOffsetListDCI-0-1-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL -- Need R } OPTIONAL, -- Need R aperiodic-v1610 SEQUENCE { reportSlotOffsetListDCI-0-2-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL, -- Need R reportSlotOffsetListDCI-0-1-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL -- Need R } OPTIONAL, -- Need RreportQuantity-r16The CSI related quantities to report. see TS 38.214 [19], clause 5.2.1. If the field reportQuantity-r16 is present, UE shall ignore reportQuantity (without suffix).CHOICE { cri-SINR-r16 NULL, ssb-Index-SINR-r16 NULL } OPTIONAL, -- Need RcodebookConfig-r16Codebook configuration for Type-1 or Type-2 including codebook subset restriction. Network does not configure codebookConfig and codebookConfig-r16 simultaneously to a UECodebookConfig-r16 OPTIONAL -- Need R ]] } CSI-ReportPeriodicityAndOffset ::= CHOICE { slots4 INTEGER(0..3), slots5 INTEGER(0..4), slots8 INTEGER(0..7), slots10 INTEGER(0..9), slots16 INTEGER(0..15), slots20 INTEGER(0..19), slots40 INTEGER(0..39), slots80 INTEGER(0..79), slots160 INTEGER(0..159), slots320 INTEGER(0..319) } PUCCH-CSI-Resource ::= SEQUENCE { uplinkBandwidthPartId BWP-Id,pucch-ResourcePUCCH resource for the associated uplink BWP. Only PUCCH-Resource of format 2, 3 and 4 is supported. The actual PUCCH-Resource is configured in PUCCH-Config and referred to by its ID. When two PUCCH-Config are configured within PUCCH-ConfigurationList, PUCCH-ResourceId in a PUCCH-CSI-Resource refers to a PUCCH-Resource in the PUCCH-Config used for HARQ-ACK with low priority.PUCCH-ResourceId } PortIndexFor8Ranks ::= CHOICE {portIndex8Port-Index configuration for up to rank 8. If present, the network configures port indexes for at least one of the ranks.SEQUENCE{ rank1-8 PortIndex8 OPTIONAL, -- Need R rank2-8 SEQUENCE(SIZE(2))OF PortIndex8 OPTIONAL, -- Need R rank3-8 SEQUENCE(SIZE(3))OF PortIndex8 OPTIONAL, -- Need R rank4-8 SEQUENCE(SIZE(4))OF PortIndex8 OPTIONAL, -- Need R rank5-8 SEQUENCE(SIZE(5))OF PortIndex8 OPTIONAL, -- Need R rank6-8 SEQUENCE(SIZE(6))OF PortIndex8 OPTIONAL, -- Need R rank7-8 SEQUENCE(SIZE(7))OF PortIndex8 OPTIONAL, -- Need R rank8-8 SEQUENCE(SIZE(8))OF PortIndex8 OPTIONAL -- Need R },portIndex4Port-Index configuration for up to rank 4. If present, the network configures port indexes for at least one of the ranks.SEQUENCE{ rank1-4 PortIndex4 OPTIONAL, -- Need R rank2-4 SEQUENCE(SIZE(2))OF PortIndex4 OPTIONAL, -- Need R rank3-4 SEQUENCE(SIZE(3))OF PortIndex4 OPTIONAL, -- Need R rank4-4 SEQUENCE(SIZE(4))OF PortIndex4 OPTIONAL -- Need R },portIndex2Port-Index configuration for up to rank 2. If present, the network configures port indexes for at least one of the ranks.SEQUENCE{ rank1-2 PortIndex2 OPTIONAL, -- Need R rank2-2 SEQUENCE(SIZE(2))OF PortIndex2 OPTIONAL -- Need R },portIndex1Port-Index configuration for rank 1.NULL } PortIndex8::= INTEGER (0..7) PortIndex4::= INTEGER (0..3) PortIndex2::= INTEGER (0..1) -- TAG-CSI-REPORTCONFIG-STOP -- ASN1STOP
CSI-ReportConfig field descriptions |
---|
carrier Indicates in which serving cell the CSI-ResourceConfig indicated below are to be found. If the field is absent, the resources are on the same serving cell as this report configuration. |
codebookConfig Codebook configuration for Type-1 or Type-2 including codebook subset restriction. Network does not configure codebookConfig and codebookConfig-r16 simultaneously to a UE |
cqi-FormatIndicator Indicates whether the UE shall report a single (wideband) or multiple (subband) CQI (see TS 38.214 [19], clause 5.2.1.4). |
cqi-Table Which CQI table to use for CQI calculation (see TS 38.214 [19], clause 5.2.2.1). |
csi-IM-ResourcesForInterference CSI IM resources for interference measurement. csi-ResourceConfigId of a CSI-ResourceConfig included in the configuration of the serving cell indicated with the field "carrier" above. The CSI-ResourceConfig indicated here contains only CSI-IM resources. The bwp-Id in that CSI-ResourceConfig is the same value as the bwp-Id in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement. |
csi-ReportingBand Indicates a contiguous or non-contiguous subset of subbands in the bandwidth part which CSI shall be reported for. Each bit in the bit-string represents one subband. The right-most bit in the bit string represents the lowest subband in the BWP. The choice determines the number of subbands (subbands3 for 3 subbands, subbands4 for 4 subbands, and so on) (see TS 38.214 [19], clause 5.2.1.4). This field is absent if there are less than 24 PRBs (no sub band) and present otherwise(see TS 38.214 [19], clause 5.2.1.4). |
dummy This field is not used in the specification. If received it shall be ignored by the UE. |
groupBasedBeamReporting Turning on/off group beam based reporting (see TS 38.214 [19], clause 5.2.1.4). |
non-PMI-PortIndication Port indication for RI/CQI calculation. For each CSI-RS resource in the linked ResourceConfig for channel measurement, a port indication for each rank R, indicating which R ports to use. Applicable only for non-PMI feedback (see TS 38.214 [19], clause 5.2.1.4.2). The first entry in non-PMI-PortIndication corresponds to the NZP-CSI-RS-Resource indicated by the first entry in nzp-CSI-RS-Resources in the NZP-CSI-RS-ResourceSet indicated in the first entry of nzp-CSI-RS-ResourceSetList of the CSI-ResourceConfig whose CSI-ResourceConfigId is indicated in a CSI-MeasId together with the above CSI-ReportConfigId; the second entry in non-PMI-PortIndication corresponds to the NZP-CSI-RS-Resource indicated by the second entry in nzp-CSI-RS-Resources in the NZP-CSI-RS-ResourceSet indicated in the first entry of nzp-CSI-RS-ResourceSetList of the same CSI-ResourceConfig, and so on until the NZP-CSI-RS-Resource indicated by the last entry in nzp-CSI-RS-Resources in the in the NZP-CSI-RS-ResourceSet indicated in the first entry of nzp-CSI-RS-ResourceSetList of the same CSI-ResourceConfig. Then the next entry corresponds to the NZP-CSI-RS-Resource indicated by the first entry in nzp-CSI-RS-Resources in the NZP-CSI-RS-ResourceSet indicated in the second entry of nzp-CSI-RS-ResourceSetList of the same CSI-ResourceConfig and so on. |
nrofReportedRS The number (N) of measured RS resources to be reported per report setting in a non-group-based report. N <= N_max, where N_max is either 2 or 4 depending on UE capability. (see TS 38.214 [19], clause 5.2.1.4) When the field is absent the UE applies the value 1. |
nzp-CSI-RS-ResourcesForInterference NZP CSI RS resources for interference measurement. csi-ResourceConfigId of a CSI-ResourceConfig included in the configuration of the serving cell indicated with the field "carrier" above. The CSI-ResourceConfig indicated here contains only NZP-CSI-RS resources. The bwp-Id in that CSI-ResourceConfig is the same value as the bwp-Id in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement. |
p0alpha Index of the p0-alpha set determining the power control for this CSI report transmission (see TS 38.214 [19], clause 6.2.1.2). |
pdsch-BundleSizeForCSI PRB bundling size to assume for CQI calculation when reportQuantity is CRI/RI/i1/CQI. If the field is absent, the UE assumes that no PRB bundling is applied (see TS 38.214 [19], clause 5.2.1.4.2). |
pmi-FormatIndicator Indicates whether the UE shall report a single (wideband) or multiple (subband) PMI. (see TS 38.214 [19], clause 5.2.1.4). |
pucch-CSI-ResourceList Indicates which PUCCH resource to use for reporting on PUCCH. |
reportConfigType Time domain behavior of reporting configuration. |
reportFreqConfiguration Reporting configuration in the frequency domain. (see TS 38.214 [19], clause 5.2.1.4). |
reportQuantity The CSI related quantities to report. see TS 38.214 [19], clause 5.2.1. If the field reportQuantity-r16 is present, UE shall ignore reportQuantity (without suffix). |
reportSlotConfig Periodicity and slot offset (see TS 38.214 [19], clause 5.2.1.4). If the field reportSlotConfig-v1530 is present, the UE shall ignore the value provided in reportSlotConfig (without suffix). |
reportSlotOffsetList, reportSlotOffsetListDCI-0-1, reportSlotOffsetListDCI-0-2 Timing offset Y for semi persistent reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config. A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on. The first report is transmitted in slot n+Y, second report in n+Y+P, where P is the configured periodicity. Timing offset Y for aperiodic reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config. A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on (see TS 38.214 [19], clause 6.1.2.1). The field reportSlotOffsetListDCI-0-1applies to DCI format 0_1 and the field reportSlotOffsetListDCI-0-2applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.2.1). |
resourcesForChannelMeasurement Resources for channel measurement. csi-ResourceConfigId of a CSI-ResourceConfig included in the configuration of the serving cell indicated with the field "carrier" above. The CSI-ResourceConfig indicated here contains only NZP-CSI-RS resources and/or SSB resources. This CSI-ReportConfig is associated with the DL BWP indicated by bwp-Id in that CSI-ResourceConfig. |
subbandSize Indicates one out of two possible BWP-dependent values for the subband size as indicated in TS 38.214 [19], table 5.2.1.4-2 . If csi-ReportingBand is absent, the UE shall ignore this field. |
timeRestrictionForChannelMeasurements Time domain measurement restriction for the channel (signal) measurements (see TS 38.214 [19], clause 5.2.1.1). |
timeRestrictionForInterferenceMeasurements Time domain measurement restriction for interference measurements (see TS 38.214 [19], clause 5.2.1.1). |
PortIndexFor8Ranks field descriptions |
---|
portIndex8 Port-Index configuration for up to rank 8. If present, the network configures port indexes for at least one of the ranks. |
portIndex4 Port-Index configuration for up to rank 4. If present, the network configures port indexes for at least one of the ranks. |
portIndex2 Port-Index configuration for up to rank 2. If present, the network configures port indexes for at least one of the ranks. |
portIndex1 Port-Index configuration for rank 1. |
PUCCH-CSI-Resource field descriptions |
---|
pucch-Resource PUCCH resource for the associated uplink BWP. Only PUCCH-Resource of format 2, 3 and 4 is supported. The actual PUCCH-Resource is configured in PUCCH-Config and referred to by its ID. When two PUCCH-Config are configured within PUCCH-ConfigurationList, PUCCH-ResourceId in a PUCCH-CSI-Resource refers to a PUCCH-Resource in the PUCCH-Config used for HARQ-ACK with low priority. |
The IE CSI-ReportConfigId is used to identify one CSI-ReportConfig.
The IE CSI-ResourceConfig defines a group of one or more NZP-CSI-RS-ResourceSet, CSI-IM-ResourceSet and/or CSI-SSB-ResourceSet.
-- ASN1START -- TAG-CSI-RESOURCECONFIG-START CSI-ResourceConfig ::= SEQUENCE {csi-ResourceConfigIdUsed in CSI-ReportConfig to refer to an instance of CSI-ResourceConfig.CSI-ResourceConfigId, csi-RS-ResourceSetList CHOICE { nzp-CSI-RS-SSB SEQUENCE {nzp-CSI-RS-ResourceSetListList of references to NZP CSI-RS resources used for beam measurement and reporting in a CSI-RS resource set. Contains up to maxNrofNZP-CSI-RS-ResourceSetsPerConfig resource sets if resourceType is 'aperiodic' and 1 otherwise (see TS 38.214 [19], clause 5.2.1.2).SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig)) OF NZP-CSI-RS-ResourceSetId OPTIONAL, -- Need Rcsi-SSB-ResourceSetListList of references to SSB resources used for CSI measurement and reporting in a CSI-RS resource set (see TS 38.214 [19], clause 5.2.1.2).SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSetsPerConfig)) OF CSI-SSB-ResourceSetId OPTIONAL -- Need R },csi-IM-ResourceSetListList of references to CSI-IM resources used for CSI measurement and reporting in a CSI-RS resource set. Contains up to maxNrofCSI-IM-ResourceSetsPerConfig resource sets if resourceType is 'aperiodic' and 1 otherwise (see TS 38.214 [19], clause 5.2.1.2).SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSetsPerConfig)) OF CSI-IM-ResourceSetId },bwp-IdThe DL BWP which the CSI-RS associated with this CSI-ResourceConfig are located in (see TS 38.214 [19], clause 5.2.1.2.BWP-Id,resourceTypeTime domain behavior of resource configuration (see TS 38.214 [19], clause 5.2.1.2). It does not apply to resources provided in the csi-SSB-ResourceSetList.ENUMERATED { aperiodic, semiPersistent, periodic }, ... } -- TAG-CSI-RESOURCECONFIG-STOP -- ASN1STOP
CSI-ResourceConfig field descriptions |
---|
bwp-Id The DL BWP which the CSI-RS associated with this CSI-ResourceConfig are located in (see TS 38.214 [19], clause 5.2.1.2. |
csi-IM-ResourceSetList List of references to CSI-IM resources used for CSI measurement and reporting in a CSI-RS resource set. Contains up to maxNrofCSI-IM-ResourceSetsPerConfig resource sets if resourceType is 'aperiodic' and 1 otherwise (see TS 38.214 [19], clause 5.2.1.2). |
csi-ResourceConfigId Used in CSI-ReportConfig to refer to an instance of CSI-ResourceConfig. |
csi-SSB-ResourceSetList List of references to SSB resources used for CSI measurement and reporting in a CSI-RS resource set (see TS 38.214 [19], clause 5.2.1.2). |
nzp-CSI-RS-ResourceSetList List of references to NZP CSI-RS resources used for beam measurement and reporting in a CSI-RS resource set. Contains up to maxNrofNZP-CSI-RS-ResourceSetsPerConfig resource sets if resourceType is 'aperiodic' and 1 otherwise (see TS 38.214 [19], clause 5.2.1.2). |
resourceType Time domain behavior of resource configuration (see TS 38.214 [19], clause 5.2.1.2). It does not apply to resources provided in the csi-SSB-ResourceSetList. |
The IE CSI-ResourceConfigId is used to identify a CSI-ResourceConfig.
The IE CSI-ResourcePeriodicityAndOffset is used to configure a periodicity and a corresponding offset for periodic and semi-persistent CSI resources, and for periodic and semi-persistent reporting on PUCCH. both, the periodicity and the offset are given in number of slots. The periodicity value slots4 corresponds to 4 slots, value slots5 corresponds to 5 slots, and so on.
-- ASN1START -- TAG-CSI-RESOURCEPERIODICITYANDOFFSET-START CSI-ResourcePeriodicityAndOffset ::= CHOICE { slots4 INTEGER (0..3), slots5 INTEGER (0..4), slots8 INTEGER (0..7), slots10 INTEGER (0..9), slots16 INTEGER (0..15), slots20 INTEGER (0..19), slots32 INTEGER (0..31), slots40 INTEGER (0..39), slots64 INTEGER (0..63), slots80 INTEGER (0..79), slots160 INTEGER (0..159), slots320 INTEGER (0..319), slots640 INTEGER (0..639) } -- TAG-CSI-RESOURCEPERIODICITYANDOFFSET-STOP -- ASN1STOP
The IE CSI-RS-ResourceConfigMobility is used to configure CSI-RS based RRM measurements.
-- ASN1START -- TAG-CSI-RS-RESOURCECONFIGMOBILITY-START CSI-RS-ResourceConfigMobility ::= SEQUENCE {subcarrierSpacingSubcarrier spacing of CSI-RS. Only the values 15, 30 kHz or 60 kHz (FR1), and 60 or 120 kHz (FR2) are applicable.SubcarrierSpacing,csi-RS-CellList-MobilityList of cells for CSI-RS based RRM measurements.SEQUENCE (SIZE (1..maxNrofCSI-RS-CellsRRM)) OF CSI-RS-CellMobility, ..., [[refServCellIndexIndicates the serving cell providing the timing reference for CSI-RS resources without associatedSSB. The field may be present only if there is at least one CSI-RS resource configured without associatedSSB. If this field is absent, the UE shall use the timing of the PCell for measurements on the CSI-RS resources without associatedSSB. The CSI-RS resources and the serving cell indicated by refServCellIndex for timing reference should be located in the same band.ServCellIndex OPTIONAL -- Need S ]] } CSI-RS-CellMobility ::= SEQUENCE { cellId PhysCellId, csi-rs-MeasurementBW SEQUENCE {nrofPRBsAllowed size of the measurement BW in PRBs. See TS 38.211 [16], clause 7.4.1.ENUMERATED { size24, size48, size96, size192, size264},startPRBStarting PRB index of the measurement bandwidth. See TS 38.211 [16], clause 7.4.1.INTEGER(0..2169) },densityFrequency domain density for the 1-port CSI-RS for L3 mobility. See TS 38.211 [16], clause 7.4.1.ENUMERATED {d1,d3} OPTIONAL, -- Need Rcsi-rs-ResourceList-MobilityList of CSI-RS resources for mobility. The maximum number of CSI-RS resources that can be configured per measObjectNR depends on the configuration of associatedSSB and the support of increasedNumberofCSIRSPerMO capability (see TS 38.214 [19], clause 5.1.6.1.3).SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesRRM)) OF CSI-RS-Resource-Mobility } CSI-RS-Resource-Mobility ::= SEQUENCE {csi-RS-IndexCSI-RS resource index associated to the CSI-RS resource to be measured (and used for reporting).CSI-RS-Index,slotConfigIndicates the CSI-RS periodicity (in milliseconds) and for each periodicity the offset (in number of slots). When subcarrierSpacing is set to kHz15, the maximum offset values for periodicities ms4/ms5/ms10/ms20/ms40 are 3/4/9/19/39 slots. When subcarrierSpacing is set to kHz30, the maximum offset values for periodicities ms4/ms5/ms10/ms20/ms40 are 7/9/19/39/79 slots. When subcarrierSpacing is set to kHz60, the maximum offset values for periodicities ms4/ms5/ms10/ms20/ms40 are 15/19/39/79/159 slots. When subcarrierSpacing is set kHz120, the maximum offset values for periodicities ms4/ms5/ms10/ms20/ms40 are 31/39/79/159/319 slots.CHOICE { ms4 INTEGER (0..31), ms5 INTEGER (0..39), ms10 INTEGER (0..79), ms20 INTEGER (0..159), ms40 INTEGER (0..319) },associatedSSBIf this field is present, the UE may base the timing of the CSI-RS resource indicated in CSI-RS-Resource-Mobility on the timing of the cell indicated by the cellId in the CSI-RS-CellMobility. In this case, the UE is not required to monitor that CSI-RS resource if the UE cannot detect the SS/PBCH block indicated by this associatedSSB and cellId. If this field is absent, the UE shall base the timing of the CSI-RS resource indicated in CSI-RS-Resource-Mobility on the timing of the serving cell indicated by refServCellIndex. In this case, the UE is required to measure the CSI-RS resource even if SS/PBCH block(s) with cellId in the CSI-RS-CellMobility are not detected. CSI-RS resources with and without associatedSSB may be configured in accordance with the rules in TS 38.214 [19], clause 5.1.6.1.3.SEQUENCE { ssb-Index SSB-Index,isQuasiColocatedIndicates that the CSI-RS resource is quasi co-located with the associated SS/PBCH block, see TS 38.214 [19], clause 5.1.6.1.3.BOOLEAN } OPTIONAL, -- Need RfrequencyDomainAllocationFrequency domain allocation within a physical resource block in accordance with TS 38.211 [16], clause 7.4.1.5.3 including table 7.4.1.5.2-1. The number of bits that may be set to one depend on the chosen row in that table.CHOICE { row1 BIT STRING (SIZE (4)), row2 BIT STRING (SIZE (12)) },firstOFDMSymbolInTimeDomainTime domain allocation within a physical resource block. The field indicates the first OFDM symbol in the PRB used for CSI-RS, see TS 38.211 [16], clause 7.4.1.5.3.INTEGER (0..13),sequenceGenerationConfigScrambling ID for CSI-RS (see TS 38.211 [16], clause 7.4.1.5.2).INTEGER (0..1023), ... } CSI-RS-Index ::= INTEGER (0..maxNrofCSI-RS-ResourcesRRM-1) -- TAG-CSI-RS-RESOURCECONFIGMOBILITY-STOP -- ASN1STOP
CSI-RS-CellMobility field descriptions |
---|
csi-rs-ResourceList-Mobility List of CSI-RS resources for mobility. The maximum number of CSI-RS resources that can be configured per measObjectNR depends on the configuration of associatedSSB and the support of increasedNumberofCSIRSPerMO capability (see TS 38.214 [19], clause 5.1.6.1.3). |
density Frequency domain density for the 1-port CSI-RS for L3 mobility. See TS 38.211 [16], clause 7.4.1. |
nrofPRBs Allowed size of the measurement BW in PRBs. See TS 38.211 [16], clause 7.4.1. |
startPRB Starting PRB index of the measurement bandwidth. See TS 38.211 [16], clause 7.4.1. |
CSI-RS-ResourceConfigMobility field descriptions |
---|
csi-RS-CellList-Mobility List of cells for CSI-RS based RRM measurements. |
refServCellIndex Indicates the serving cell providing the timing reference for CSI-RS resources without associatedSSB. The field may be present only if there is at least one CSI-RS resource configured without associatedSSB. If this field is absent, the UE shall use the timing of the PCell for measurements on the CSI-RS resources without associatedSSB. The CSI-RS resources and the serving cell indicated by refServCellIndex for timing reference should be located in the same band. |
subcarrierSpacing Subcarrier spacing of CSI-RS. Only the values 15, 30 kHz or 60 kHz (FR1), and 60 or 120 kHz (FR2) are applicable. |
CSI-RS-Resource-Mobility field descriptions |
---|
associatedSSB If this field is present, the UE may base the timing of the CSI-RS resource indicated in CSI-RS-Resource-Mobility on the timing of the cell indicated by the cellId in the CSI-RS-CellMobility. In this case, the UE is not required to monitor that CSI-RS resource if the UE cannot detect the SS/PBCH block indicated by this associatedSSB and cellId. If this field is absent, the UE shall base the timing of the CSI-RS resource indicated in CSI-RS-Resource-Mobility on the timing of the serving cell indicated by refServCellIndex. In this case, the UE is required to measure the CSI-RS resource even if SS/PBCH block(s) with cellId in the CSI-RS-CellMobility are not detected. CSI-RS resources with and without associatedSSB may be configured in accordance with the rules in TS 38.214 [19], clause 5.1.6.1.3. |
csi-RS-Index CSI-RS resource index associated to the CSI-RS resource to be measured (and used for reporting). |
firstOFDMSymbolInTimeDomain Time domain allocation within a physical resource block. The field indicates the first OFDM symbol in the PRB used for CSI-RS, see TS 38.211 [16], clause 7.4.1.5.3. |
frequencyDomainAllocation Frequency domain allocation within a physical resource block in accordance with TS 38.211 [16], clause 7.4.1.5.3 including table 7.4.1.5.2-1. The number of bits that may be set to one depend on the chosen row in that table. |
isQuasiColocated Indicates that the CSI-RS resource is quasi co-located with the associated SS/PBCH block, see TS 38.214 [19], clause 5.1.6.1.3. |
sequenceGenerationConfig Scrambling ID for CSI-RS (see TS 38.211 [16], clause 7.4.1.5.2). |
slotConfig Indicates the CSI-RS periodicity (in milliseconds) and for each periodicity the offset (in number of slots). When subcarrierSpacing is set to kHz15, the maximum offset values for periodicities ms4/ms5/ms10/ms20/ms40 are 3/4/9/19/39 slots. When subcarrierSpacing is set to kHz30, the maximum offset values for periodicities ms4/ms5/ms10/ms20/ms40 are 7/9/19/39/79 slots. When subcarrierSpacing is set to kHz60, the maximum offset values for periodicities ms4/ms5/ms10/ms20/ms40 are 15/19/39/79/159 slots. When subcarrierSpacing is set kHz120, the maximum offset values for periodicities ms4/ms5/ms10/ms20/ms40 are 31/39/79/159/319 slots. |
The IE CSI-RS-ResourceMapping is used to configure the resource element mapping of a CSI-RS resource in time- and frequency domain.
-- ASN1START -- TAG-CSI-RS-RESOURCEMAPPING-START CSI-RS-ResourceMapping ::= SEQUENCE {frequencyDomainAllocationFrequency domain allocation within a physical resource block in accordance with TS 38.211 [16], clause 7.4.1.5.3. The applicable row number in table 7.4.1.5.3-1 is determined by the frequencyDomainAllocation for rows 1, 2 and 4, and for other rows by matching the values in the column Ports, Density and CDMtype in table 7.4.1.5.3-1 with the values of nrofPorts, cdm-Type and density below and, when more than one row has the 3 values matching, by selecting the row where the column (k bar, l bar) in table 7.4.1.5.3-1 has indexes for k ranging from 0 to 2*n-1 where n is the number of bits set to 1 in frequencyDomainAllocation.CHOICE { row1 BIT STRING (SIZE (4)), row2 BIT STRING (SIZE (12)), row4 BIT STRING (SIZE (3)), other BIT STRING (SIZE (6)) },nrofPortsNumber of ports (see TS 38.214 [19], clause 5.2.2.3.1).ENUMERATED {p1,p2,p4,p8,p12,p16,p24,p32},firstOFDMSymbolInTimeDomainTime domain allocation within a physical resource block. The field indicates the first OFDM symbol in the PRB used for CSI-RS. See TS 38.211 [16], clause 7.4.1.5.3.INTEGER (0..13),firstOFDMSymbolInTimeDomain2Time domain allocation within a physical resource block. See TS 38.211 [16], clause 7.4.1.5.3.INTEGER (2..12) OPTIONAL, -- Need Rcdm-TypeCDM type (see TS 38.214 [19], clause 5.2.2.3.1).ENUMERATED {noCDM, fd-CDM2, cdm4-FD2-TD2, cdm8-FD2-TD4},densityDensity of CSI-RS resource measured in RE/port/PRB (see TS 38.211 [16], clause 7.4.1.5.3). Values 0.5 (dot5), 1 (one) and 3 (three) are allowed for X=1, values 0.5 (dot5) and 1 (one) are allowed for X=2, 16, 24 and 32, value 1 (one) is allowed for X=4, 8, 12. For density = 1/2, includes 1-bit indication for RB level comb offset indicating whether odd or even RBs are occupied by CSI-RS.CHOICE { dot5 ENUMERATED {evenPRBs, oddPRBs}, one NULL, three NULL, spare NULL },freqBandWideband or partial band CSI-RS, (see TS 38.214 [19], clause 5.2.2.3.1).CSI-FrequencyOccupation, ... } -- TAG-CSI-RS-RESOURCEMAPPING-STOP -- ASN1STOP
CSI-RS-ResourceMapping field descriptions |
---|
cdm-Type CDM type (see TS 38.214 [19], clause 5.2.2.3.1). |
density Density of CSI-RS resource measured in RE/port/PRB (see TS 38.211 [16], clause 7.4.1.5.3). Values 0.5 (dot5), 1 (one) and 3 (three) are allowed for X=1, values 0.5 (dot5) and 1 (one) are allowed for X=2, 16, 24 and 32, value 1 (one) is allowed for X=4, 8, 12. For density = 1/2, includes 1-bit indication for RB level comb offset indicating whether odd or even RBs are occupied by CSI-RS. |
firstOFDMSymbolInTimeDomain2 Time domain allocation within a physical resource block. See TS 38.211 [16], clause 7.4.1.5.3. |
firstOFDMSymbolInTimeDomain Time domain allocation within a physical resource block. The field indicates the first OFDM symbol in the PRB used for CSI-RS. See TS 38.211 [16], clause 7.4.1.5.3. |
freqBand Wideband or partial band CSI-RS, (see TS 38.214 [19], clause 5.2.2.3.1). |
frequencyDomainAllocation Frequency domain allocation within a physical resource block in accordance with TS 38.211 [16], clause 7.4.1.5.3. The applicable row number in table 7.4.1.5.3-1 is determined by the frequencyDomainAllocation for rows 1, 2 and 4, and for other rows by matching the values in the column Ports, Density and CDMtype in table 7.4.1.5.3-1 with the values of nrofPorts, cdm-Type and density below and, when more than one row has the 3 values matching, by selecting the row where the column (k bar, l bar) in table 7.4.1.5.3-1 has indexes for k ranging from 0 to 2*n-1 where n is the number of bits set to 1 in frequencyDomainAllocation. |
nrofPorts Number of ports (see TS 38.214 [19], clause 5.2.2.3.1). |
The CSI-SemiPersistentOnPUSCH-TriggerStateList IE is used to configure the UE with list of trigger states for semi-persistent reporting of channel state information on L1. See also TS 38.214 [19], clause 5.2.
-- ASN1START -- TAG-CSI-SEMIPERSISTENTONPUSCHTRIGGERSTATELIST-START CSI-SemiPersistentOnPUSCH-TriggerStateList ::= SEQUENCE(SIZE(1..maxNrOfSemiPersistentPUSCH-Triggers)) OF CSI-SemiPersistentOnPUSCH-TriggerState CSI-SemiPersistentOnPUSCH-TriggerState ::= SEQUENCE { associatedReportConfigInfo CSI-ReportConfigId, ... } -- TAG-CSI-SEMIPERSISTENTONPUSCHTRIGGERSTATELIST-STOP -- ASN1STOP
The IE CSI-SSB-ResourceSet is used to configure one SS/PBCH block resource set which refers to SS/PBCH as indicated in ServingCellConfigCommon.
-- ASN1START -- TAG-CSI-SSB-RESOURCESET-START CSI-SSB-ResourceSet ::= SEQUENCE { csi-SSB-ResourceSetId CSI-SSB-ResourceSetId, csi-SSB-ResourceList SEQUENCE (SIZE(1..maxNrofCSI-SSB-ResourcePerSet)) OF SSB-Index, ... } -- TAG-CSI-SSB-RESOURCESET-STOP -- ASN1STOP
The IE CSI-SSB-ResourceSetId is used to identify one SS/PBCH block resource set.
The IE DedicatedNAS-Message is used to transfer UE specific NAS layer information between the 5GC CN and the UE. The RRC layer is transparent for this information.
The IE DMRS-DownlinkConfig is used to configure downlink demodulation reference signals for PDSCH.
-- ASN1START -- TAG-DMRS-DOWNLINKCONFIG-START DMRS-DownlinkConfig ::= SEQUENCE {dmrs-TypeSelection of the DMRS type to be used for DL (see TS 38.211 [16], clause 7.4.1.1.1). If the field is absent, the UE uses DMRS type 1.ENUMERATED {type2} OPTIONAL, -- Need Sdmrs-AdditionalPositionPosition for additional DM-RS in DL, see Tables 7.4.1.1.2-3 and 7.4.1.1.2-4 in TS 38.211 [16]. If the field is absent, the UE applies the value pos2.See also clause 7.4.1.1.2 for additional constraints on how the network may set this field depending on the setting of other fields.ENUMERATED {pos0, pos1, pos3} OPTIONAL, -- Need SmaxLengthThe maximum number of OFDM symbols for DL front loaded DMRS. len1 corresponds to value 1. len2 corresponds to value 2. If the field is absent, the UE applies value len1. If set to len2, the UE determines the actual number of DM-RS symbols by the associated DCI. (see TS 38.211 [16], clause 7.4.1.1.2).ENUMERATED {len2} OPTIONAL, -- Need SscramblingID0DL DMRS scrambling initialization (see TS 38.211 [16], clause 7.4.1.1.1). When the field is absent the UE applies the value physCellId configured for this serving cell.INTEGER (0..65535) OPTIONAL, -- Need SscramblingID1DL DMRS scrambling initialization (see TS 38.211 [16], clause 7.4.1.1.1). When the field is absent the UE applies the value physCellId configured for this serving cell.INTEGER (0..65535) OPTIONAL, -- Need SphaseTrackingRSConfigures downlink PTRS. If the field is not configured, the UE assumes that downlink PTRS are absent. See TS 38.214 [19] clause 5.1.6.3.SetupRelease { PTRS-DownlinkConfig } OPTIONAL, -- Need M ..., [[dmrs-Downlink-r16This field indicates whether low PAPR DMRS is used, as specified in TS38.211 [16], clause 7.4.1.1.1.ENUMERATED {enabled} OPTIONAL -- Need R ]] } -- TAG-DMRS-DOWNLINKCONFIG-STOP -- ASN1STOP
DMRS-DownlinkConfig field descriptions |
---|
dmrs-AdditionalPosition Position for additional DM-RS in DL, see Tables 7.4.1.1.2-3 and 7.4.1.1.2-4 in TS 38.211 [16]. If the field is absent, the UE applies the value pos2.See also clause 7.4.1.1.2 for additional constraints on how the network may set this field depending on the setting of other fields. |
dmrs-Downlink This field indicates whether low PAPR DMRS is used, as specified in TS38.211 [16], clause 7.4.1.1.1. |
dmrs-Type Selection of the DMRS type to be used for DL (see TS 38.211 [16], clause 7.4.1.1.1). If the field is absent, the UE uses DMRS type 1. |
maxLength The maximum number of OFDM symbols for DL front loaded DMRS. len1 corresponds to value 1. len2 corresponds to value 2. If the field is absent, the UE applies value len1. If set to len2, the UE determines the actual number of DM-RS symbols by the associated DCI. (see TS 38.211 [16], clause 7.4.1.1.2). |
phaseTrackingRS Configures downlink PTRS. If the field is not configured, the UE assumes that downlink PTRS are absent. See TS 38.214 [19] clause 5.1.6.3. |
scramblingID0 DL DMRS scrambling initialization (see TS 38.211 [16], clause 7.4.1.1.1). When the field is absent the UE applies the value physCellId configured for this serving cell. |
scramblingID1 DL DMRS scrambling initialization (see TS 38.211 [16], clause 7.4.1.1.1). When the field is absent the UE applies the value physCellId configured for this serving cell. |
The IE DMRS-UplinkConfig is used to configure uplink demodulation reference signals for PUSCH.
-- ASN1START -- TAG-DMRS-UPLINKCONFIG-START DMRS-UplinkConfig ::= SEQUENCE {dmrs-TypeSelection of the DMRS type to be used for UL (see TS 38.211 [16], clause 6.4.1.1.3) If the field is absent, the UE uses DMRS type 1.ENUMERATED {type2} OPTIONAL, -- Need Sdmrs-AdditionalPositionPosition for additional DM-RS in UL (see TS 38.211 [16], clause 6.4.1.1.3). If the field is absent, the UE applies the value pos2. See also clause 6.4.1.1.3 for additional constraints on how the network may set this field depending on the setting of other fields.ENUMERATED {pos0, pos1, pos3} OPTIONAL, -- Need SphaseTrackingRSConfigures uplink PTRS (see TS 38.211 [16]).SetupRelease { PTRS-UplinkConfig } OPTIONAL, -- Need MmaxLengthThe maximum number of OFDM symbols for UL front loaded DMRS. len1 corresponds to value 1. len2 corresponds to value 2. If the field is absent, the UE applies value len1. If set to len2, the UE determines the actual number of DM-RS symbols by the associated DCI. (see TS 38.211 [16], clause 6.4.1.1.3).ENUMERATED {len2} OPTIONAL, -- Need StransformPrecodingDisabledDMRS related parameters for Cyclic Prefix OFDM.SEQUENCE {scramblingID0UL DMRS scrambling initialization for CP-OFDM (see TS 38.211 [16], clause 6.4.1.1.1.1). When the field is absent the UE applies the value Physical cell ID (physCellId).INTEGER (0..65535) OPTIONAL, -- Need SscramblingID1UL DMRS scrambling initialization for CP-OFDM. (see TS 38.211 [16], clause 6.4.1.1.1.1). When the field is absent the UE applies the value Physical cell ID (physCellId).INTEGER (0..65535) OPTIONAL, -- Need S ..., [[dmrs-Uplink-r16This field indicates whether low PAPR DMRS is used, as specified in TS38.211 [16], clause 6.4.1.1.1.1.ENUMERATED {enabled} OPTIONAL -- Need R ]] } OPTIONAL, -- Need RtransformPrecodingEnabledDMRS related parameters for DFT-s-OFDM (Transform Precoding).SEQUENCE {nPUSCH-IdentityParameter: N_ID^(PUSCH) for DFT-s-OFDM DMRS. If the value is absent or released, the UE uses the value Physical cell ID (physCellId). See TS 38.211 [16].INTEGER(0..1007) OPTIONAL, -- Need SsequenceGroupHoppingFor DMRS transmission with transform precoder the NW may configure group hopping by the cell-specific parameter groupHoppingEnabledTransformPrecoding in PUSCH-ConfigCommon. In this case, the NW may include this UE specific field to disable group hopping for PUSCH transmission except for Msg3, i.e., to override the configuration in PUSCH-ConfigCommon (see TS 38.211 [16]). If the field is absent, the UE uses the same hopping mode as for Msg3.ENUMERATED {disabled} OPTIONAL, -- Need SsequenceHoppingDetermines if sequence hopping is enabled for DMRS transmission with transform precoderfor PUSCH transmission other than Msg3 (sequence hopping is always disabled for Msg3). If the field is absent, the UE uses the same hopping mode as for msg3. The network does not configure simultaneous group hopping and sequence hopping. See TS 38.211 [16], clause 6.4.1.1.1.2.ENUMERATED {enabled} OPTIONAL, -- Need S ..., [[dmrs-UplinkTransformPrecoding-r16This field indicates whether low PAPR DMRS is used for PUSCH with pi/2 BPSK modulation, as specified in TS38.211 [16], clause 6.4.1.1.1.2. The network configures this field only if tp-pi2BPSK is configured in PUSCH-Config.SetupRelease {DMRS-UplinkTransformPrecoding-r16} OPTIONAL -- Need M ]] } OPTIONAL, -- Need R ... } DMRS-UplinkTransformPrecoding-r16 ::= SEQUENCE { pi2BPSK-ScramblingID0 INTEGER(0..65535) OPTIONAL, -- Need S pi2BPSK-ScramblingID1 INTEGER(0..65535) OPTIONAL -- Need S } -- TAG-DMRS-UPLINKCONFIG-STOP -- ASN1STOP
DMRS-UplinkConfig field descriptions |
---|
dmrs-AdditionalPosition Position for additional DM-RS in UL (see TS 38.211 [16], clause 6.4.1.1.3). If the field is absent, the UE applies the value pos2. See also clause 6.4.1.1.3 for additional constraints on how the network may set this field depending on the setting of other fields. |
dmrs-Type Selection of the DMRS type to be used for UL (see TS 38.211 [16], clause 6.4.1.1.3) If the field is absent, the UE uses DMRS type 1. |
dmrs-Uplink This field indicates whether low PAPR DMRS is used, as specified in TS38.211 [16], clause 6.4.1.1.1.1. |
dmrs-UplinkTransformPrecoding This field indicates whether low PAPR DMRS is used for PUSCH with pi/2 BPSK modulation, as specified in TS38.211 [16], clause 6.4.1.1.1.2. The network configures this field only if tp-pi2BPSK is configured in PUSCH-Config. |
maxLength The maximum number of OFDM symbols for UL front loaded DMRS. len1 corresponds to value 1. len2 corresponds to value 2. If the field is absent, the UE applies value len1. If set to len2, the UE determines the actual number of DM-RS symbols by the associated DCI. (see TS 38.211 [16], clause 6.4.1.1.3). |
nPUSCH-Identity Parameter: N_ID^(PUSCH) for DFT-s-OFDM DMRS. If the value is absent or released, the UE uses the value Physical cell ID (physCellId). See TS 38.211 [16]. |
phaseTrackingRS Configures uplink PTRS (see TS 38.211 [16]). |
pi2BPSK-ScramblingID0, pi2BPSK-ScramblingID1 UL DMRS scrambling initialization for pi/2 BPSK DMRS for PUSCH (see TS 38.211 [16], Clause 6.4.1.1.2). When the field is absent the UE applies the value Physical cell ID (physCellId) of the serving cell. |
scramblingID0 UL DMRS scrambling initialization for CP-OFDM (see TS 38.211 [16], clause 6.4.1.1.1.1). When the field is absent the UE applies the value Physical cell ID (physCellId). |
scramblingID1 UL DMRS scrambling initialization for CP-OFDM. (see TS 38.211 [16], clause 6.4.1.1.1.1). When the field is absent the UE applies the value Physical cell ID (physCellId). |
sequenceGroupHopping For DMRS transmission with transform precoder the NW may configure group hopping by the cell-specific parameter groupHoppingEnabledTransformPrecoding in PUSCH-ConfigCommon. In this case, the NW may include this UE specific field to disable group hopping for PUSCH transmission except for Msg3, i.e., to override the configuration in PUSCH-ConfigCommon (see TS 38.211 [16]). If the field is absent, the UE uses the same hopping mode as for Msg3. |
sequenceHopping Determines if sequence hopping is enabled for DMRS transmission with transform precoderfor PUSCH transmission other than Msg3 (sequence hopping is always disabled for Msg3). If the field is absent, the UE uses the same hopping mode as for msg3. The network does not configure simultaneous group hopping and sequence hopping. See TS 38.211 [16], clause 6.4.1.1.1.2. |
transformPrecodingDisabled DMRS related parameters for Cyclic Prefix OFDM. |
transformPrecodingEnabled DMRS related parameters for DFT-s-OFDM (Transform Precoding). |
The IE DownlinkConfigCommon provides common downlink parameters of a cell.
-- ASN1START -- TAG-DOWNLINKCONFIGCOMMON-START DownlinkConfigCommon ::= SEQUENCE {frequencyInfoDLBasic parameters of a downlink carrier and transmission thereon.FrequencyInfoDL OPTIONAL, -- Cond InterFreqHOAndServCellAddinitialDownlinkBWPThe initial downlink BWP configuration for a serving cell.The network configures the locationAndBandwidth so that the initial downlink BWP contains the entire CORESET#0 of this serving cell in the frequency domain.BWP-DownlinkCommon OPTIONAL, -- Cond ServCellAdd ... } -- TAG-DOWNLINKCONFIGCOMMON-STOP -- ASN1STOP
DownlinkConfigCommon field descriptions |
---|
frequencyInfoDL Basic parameters of a downlink carrier and transmission thereon. |
initialDownlinkBWP The initial downlink BWP configuration for a serving cell.The network configures the locationAndBandwidth so that the initial downlink BWP contains the entire CORESET#0 of this serving cell in the frequency domain. |
Conditional Presence | Explanation |
---|---|
InterFreqHOAndServCellAdd | This field is mandatory present for inter-frequency handover, and upon serving cell (PSCell/SCell) addition. Otherwise, the field is optionally present, Need M. |
ServCellAdd | This field is mandatory present upon serving cell addition (for PSCell and SCell) and upon handover from E-UTRA to NR. It is optionally present, Need M otherwise. |
The IE DownlinkConfigCommonSIB provides common downlink parameters of a cell.
-- ASN1START -- TAG-DOWNLINKCONFIGCOMMONSIB-START DownlinkConfigCommonSIB ::= SEQUENCE { frequencyInfoDL FrequencyInfoDL-SIB,initialDownlinkBWPThe initial downlink BWP configuration for a PCell. The network configures the locationAndBandwidth so that the initial downlink BWP contains the entire CORESET#0 of this serving cell in the frequency domain. The UE applies the locationAndBandwidthupon reception of this field (e.g. to determine the frequency position of signals described in relation to this locationAndBandwidth) but it keeps CORESET#0 until after reception of RRCSetup/RRCResume/RRCReestablishment.BWP-DownlinkCommon,bcch-ConfigThe modification period related configuration.BCCH-Config,pcch-ConfigThe paging related configuration.PCCH-Config, ... } BCCH-Config ::= SEQUENCE {modificationPeriodCoeffActual modification period, expressed in number of radio frames m = modificationPeriodCoeff * defaultPagingCycle, see clause 5.2.2.2.2. n2 corresponds to value 2, n4 corresponds to value 4, and so on.ENUMERATED {n2, n4, n8, n16}, ... } PCCH-Config ::= SEQUENCE {defaultPagingCycleDefault paging cycle, used to derive 'T' in TS 38.304 [20]. Value rf32 corresponds to 32 radio frames, value rf64 corresponds to 64 radio frames and so on.PagingCycle,nAndPagingFrameOffsetUsed to derive the number of total paging frames in T (corresponding to parameter N in TS 38.304 [20]) and paging frame offset (corresponding to parameter PF_offset in TS 38.304 [20]). A value of oneSixteenthT corresponds to T / 16, a value of oneEighthT corresponds to T / 8, and so on. If pagingSearchSpace is set to zero and if SS/PBCH block and CORESET multiplexing pattern is 2 or 3 (as specified in TS 38.213 [13]): -for ssb-periodicityServingCell of 5 or 10 ms, N can be set to one of {oneT, halfT, quarterT, oneEighthT, oneSixteenthT} -for ssb-periodicityServingCell of 20 ms, N can be set to one of {halfT, quarterT, oneEighthT, oneSixteenthT} -for ssb-periodicityServingCell of 40 ms, N can be set to one of {quarterT, oneEighthT, oneSixteenthT} -for ssb-periodicityServingCell of 80 ms, N can be set to one of {oneEighthT, oneSixteenthT} -for ssb-periodicityServingCell of 160 ms, N can be set to oneSixteenthT If pagingSearchSpace is set to zero and if SS/PBCH block and CORESET multiplexing pattern is 1 (as specified in TS 38.213 [13]), N can be set to one of {halfT, quarterT, oneEighthT, oneSixteenthT} If pagingSearchSpace is not set to zero, N can be configured to one of {oneT, halfT, quarterT, oneEighthT, oneSixteenthT}CHOICE { oneT NULL, halfT INTEGER (0..1), quarterT INTEGER (0..3), oneEighthT INTEGER (0..7), oneSixteenthT INTEGER (0..15) },nsNumber of paging occasions per paging frame.ENUMERATED {four, two, one},firstPDCCH-MonitoringOccasionOfPOPoints out the first PDCCH monitoring occasion for paging of each PO of the PF, see TS 38.304 [20].CHOICE { sCS15KHZoneT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..139), sCS30KHZoneT-SCS15KHZhalfT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..279), sCS60KHZoneT-SCS30KHZhalfT-SCS15KHZquarterT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..559), sCS120KHZoneT-SCS60KHZhalfT-SCS30KHZquarterT-SCS15KHZoneEighthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..1119), sCS120KHZhalfT-SCS60KHZquarterT-SCS30KHZoneEighthT-SCS15KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..2239), sCS120KHZquarterT-SCS60KHZoneEighthT-SCS30KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..4479), sCS120KHZoneEighthT-SCS60KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..8959), sCS120KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..17919) } OPTIONAL, -- Need R ..., [[nrofPDCCH-MonitoringOccasionPerSSB-InPO-r16The number of PDCCH monitoring occasions corresponding to an SSB within a Paging Occasion, see TS 38.304 [20], clause 7.1.INTEGER (2..4) OPTIONAL -- Cond SharedSpectrum2 ]] } -- TAG-DOWNLINKCONFIGCOMMONSIB-STOP -- ASN1STOP
DownlinkConfigCommonSIB field descriptions |
---|
bcch-Config The modification period related configuration. |
frequencyInfoDL-SIB Basic parameters of a downlink carrier and transmission thereon. |
initialDownlinkBWP The initial downlink BWP configuration for a PCell. The network configures the locationAndBandwidth so that the initial downlink BWP contains the entire CORESET#0 of this serving cell in the frequency domain. The UE applies the locationAndBandwidthupon reception of this field (e.g. to determine the frequency position of signals described in relation to this locationAndBandwidth) but it keeps CORESET#0 until after reception of RRCSetup/RRCResume/RRCReestablishment. |
nrofPDCCH-MonitoringOccasionPerSSB-InPO The number of PDCCH monitoring occasions corresponding to an SSB within a Paging Occasion, see TS 38.304 [20], clause 7.1. |
pcch-Config The paging related configuration. |
BCCH-Config field descriptions |
---|
modificationPeriodCoeff Actual modification period, expressed in number of radio frames m = modificationPeriodCoeff * defaultPagingCycle, see clause 5.2.2.2.2. n2 corresponds to value 2, n4 corresponds to value 4, and so on. |
PCCH-Config field descriptions |
---|
defaultPagingCycle Default paging cycle, used to derive 'T' in TS 38.304 [20]. Value rf32 corresponds to 32 radio frames, value rf64 corresponds to 64 radio frames and so on. |
firstPDCCH-MonitoringOccasionOfPO Points out the first PDCCH monitoring occasion for paging of each PO of the PF, see TS 38.304 [20]. |
nAndPagingFrameOffset Used to derive the number of total paging frames in T (corresponding to parameter N in TS 38.304 [20]) and paging frame offset (corresponding to parameter PF_offset in TS 38.304 [20]). A value of oneSixteenthT corresponds to T / 16, a value of oneEighthT corresponds to T / 8, and so on. If pagingSearchSpace is set to zero and if SS/PBCH block and CORESET multiplexing pattern is 2 or 3 (as specified in TS 38.213 [13]): -for ssb-periodicityServingCell of 5 or 10 ms, N can be set to one of {oneT, halfT, quarterT, oneEighthT, oneSixteenthT} -for ssb-periodicityServingCell of 20 ms, N can be set to one of {halfT, quarterT, oneEighthT, oneSixteenthT} -for ssb-periodicityServingCell of 40 ms, N can be set to one of {quarterT, oneEighthT, oneSixteenthT} -for ssb-periodicityServingCell of 80 ms, N can be set to one of {oneEighthT, oneSixteenthT} -for ssb-periodicityServingCell of 160 ms, N can be set to oneSixteenthT If pagingSearchSpace is set to zero and if SS/PBCH block and CORESET multiplexing pattern is 1 (as specified in TS 38.213 [13]), N can be set to one of {halfT, quarterT, oneEighthT, oneSixteenthT} If pagingSearchSpace is not set to zero, N can be configured to one of {oneT, halfT, quarterT, oneEighthT, oneSixteenthT} |
ns Number of paging occasions per paging frame. |
Conditional Presence | Explanation |
---|---|
SharedSpectrum2 | The field is optional present, Need R, if this cell operates with shared spectrum channel access. Otherwise, it is absent, Need R. |
The IE DownlinkPreemption is used to configure the UE to monitor PDCCH for the INT-RNTI (interruption).
-- ASN1START -- TAG-DOWNLINKPREEMPTION-START DownlinkPreemption ::= SEQUENCE {int-RNTIRNTI used for indication pre-emption in DL (see TS 38.213 [13], clause 10).RNTI-Value,timeFrequencySetSet selection for DL-preemption indication (see TS 38.213 [13], clause 11.2) The set determines how the UE interprets the DL preemption DCI payload.ENUMERATED {set0, set1},dci-PayloadSizeTotal length of the DCI payload scrambled with INT-RNTI (see TS 38.213 [13], clause 11.2).INTEGER (0..maxINT-DCI-PayloadSize),int-ConfigurationPerServingCellIndicates (per serving cell) the position of the 14 bit INT values inside the DCI payload (see TS 38.213 [13], clause 11.2).SEQUENCE (SIZE (1..maxNrofServingCells)) OF INT-ConfigurationPerServingCell, ... } INT-ConfigurationPerServingCell ::= SEQUENCE { servingCellId ServCellIndex,positionInDCIStarting position (in number of bit) of the 14 bit INT value applicable for this serving cell (servingCellId) within the DCI payload (see TS 38.213 [13], clause 11.2). Must be multiples of 14 (bit).INTEGER (0..maxINT-DCI-PayloadSize-1) } -- TAG-DOWNLINKPREEMPTION-STOP -- ASN1STOP
DownlinkPreemption field descriptions |
---|
dci-PayloadSize Total length of the DCI payload scrambled with INT-RNTI (see TS 38.213 [13], clause 11.2). |
int-ConfigurationPerServingCell Indicates (per serving cell) the position of the 14 bit INT values inside the DCI payload (see TS 38.213 [13], clause 11.2). |
int-RNTI RNTI used for indication pre-emption in DL (see TS 38.213 [13], clause 10). |
timeFrequencySet Set selection for DL-preemption indication (see TS 38.213 [13], clause 11.2) The set determines how the UE interprets the DL preemption DCI payload. |
INT-ConfigurationPerServingCell field descriptions |
---|
positionInDCI Starting position (in number of bit) of the 14 bit INT value applicable for this serving cell (servingCellId) within the DCI payload (see TS 38.213 [13], clause 11.2). Must be multiples of 14 (bit). |
The IE DRB-Identity is used to identify a DRB used by a UE.
The IE DRX-Config is used to configure DRX related parameters.
-- ASN1START -- TAG-DRX-CONFIG-START DRX-Config ::= SEQUENCE { drx-onDurationTimer CHOICE { subMilliSeconds INTEGER (1..31), milliSeconds ENUMERATED { ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms400, ms500, ms600, ms800, ms1000, ms1200, ms1600, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } }, drx-InactivityTimer ENUMERATED { ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1}, drx-HARQ-RTT-TimerDL INTEGER (0..56), drx-HARQ-RTT-TimerUL INTEGER (0..56), drx-RetransmissionTimerDL ENUMERATED { sl0, sl1, sl2, sl4, sl6, sl8, sl16, sl24, sl33, sl40, sl64, sl80, sl96, sl112, sl128, sl160, sl320, spare15, spare14, spare13, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1}, drx-RetransmissionTimerUL ENUMERATED { sl0, sl1, sl2, sl4, sl6, sl8, sl16, sl24, sl33, sl40, sl64, sl80, sl96, sl112, sl128, sl160, sl320, spare15, spare14, spare13, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 }, drx-LongCycleStartOffset CHOICE { ms10 INTEGER(0..9), ms20 INTEGER(0..19), ms32 INTEGER(0..31), ms40 INTEGER(0..39), ms60 INTEGER(0..59), ms64 INTEGER(0..63), ms70 INTEGER(0..69), ms80 INTEGER(0..79), ms128 INTEGER(0..127), ms160 INTEGER(0..159), ms256 INTEGER(0..255), ms320 INTEGER(0..319), ms512 INTEGER(0..511), ms640 INTEGER(0..639), ms1024 INTEGER(0..1023), ms1280 INTEGER(0..1279), ms2048 INTEGER(0..2047), ms2560 INTEGER(0..2559), ms5120 INTEGER(0..5119), ms10240 INTEGER(0..10239) }, shortDRX SEQUENCE { drx-ShortCycle ENUMERATED { ms2, ms3, ms4, ms5, ms6, ms7, ms8, ms10, ms14, ms16, ms20, ms30, ms32, ms35, ms40, ms64, ms80, ms128, ms160, ms256, ms320, ms512, ms640, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 }, drx-ShortCycleTimer INTEGER (1..16) } OPTIONAL, -- Need R drx-SlotOffset INTEGER (0..31) } -- TAG-DRX-CONFIG-STOP -- ASN1STOP
The IE DRX-ConfigSecondaryGroup is used to configure DRX related parameters for the second DRX group as specified in TS 38.321 [3].
-- ASN1START -- TAG-DRX-CONFIGSECONDARYGROUP-START DRX-ConfigSecondaryGroup-r16 ::= SEQUENCE { drx-onDurationTimer-r16 CHOICE { subMilliSeconds INTEGER (1..31), milliSeconds ENUMERATED { ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms400, ms500, ms600, ms800, ms1000, ms1200, ms1600, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } }, drx-InactivityTimer-r16 ENUMERATED { ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} } -- TAG-DRX-CONFIGSECONDARYGROUP-STOP -- ASN1STOP
The IE FilterCoefficient specifies the measurement filtering coefficient. Value fc0 corresponds to k = 0, fc1 corresponds to k = 1, and so on.
DRX-Config field descriptions |
---|
drx-HARQ-RTT-TimerDL Value in number of symbols of the BWP where the transport block was received. |
drx-HARQ-RTT-TimerUL Value in number of symbols of the BWP where the transport block was transmitted. |
drx-InactivityTimer Value in multiple integers of 1 ms. ms0 corresponds to 0, ms1 corresponds to 1 ms, ms2 corresponds to 2 ms, and so on. |
drx-LongCycleStartOffset drx-LongCycle in ms and drx-StartOffset in multiples of 1 ms. If drx-ShortCycle is configured, the value of drx-LongCycle shall be a multiple of the drx-ShortCycle value. |
drx-onDurationTimer Value in multiples of 1/32 ms (subMilliSeconds) or in ms (milliSecond). For the latter, value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, and so on. |
drx-RetransmissionTimerDL Value in number of slot lengths of the BWP where the transport block was received. value sl0 corresponds to 0 slots, sl1 corresponds to 1 slot, sl2 corresponds to 2 slots, and so on. |
drx-RetransmissionTimerUL Value in number of slot lengths of the BWP where the transport block was transmitted. sl0 corresponds to 0 slots, sl1 corresponds to 1 slot, sl2 corresponds to 2 slots, and so on. |
drx-ShortCycleTimer Value in multiples of drx-ShortCycle. A value of 1 corresponds to drx-ShortCycle, a value of 2 corresponds to 2 * drx-ShortCycle and so on. |
drx-ShortCycle Value in ms. ms1 corresponds to 1 ms, ms2 corresponds to 2 ms, and so on. |
drx-SlotOffset Value in 1/32 ms. Value 0 corresponds to 0 ms, value 1 corresponds to 1/32 ms, value 2 corresponds to 2/32 ms, and so on. |
DRX-ConfigSecondaryGroup field descriptions |
---|
drx-InactivityTimer Value in multiple integers of 1 ms. ms0 corresponds to 0 ms, ms1 corresponds to 1 ms, ms2 corresponds to 2 ms, and so on, as specified in TS 38.321 [3]. The network configures a drx-InactivityTimer value for the second DRX group that is smaller than the drx-InactivityTimer configured for the default DRX group in IE DRX-Config. |
drx-onDurationTimer Value in multiples of 1/32 ms (subMilliSeconds) or in ms (milliSeconds). For the latter, value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, and so on, as specified in TS 38.321 [3]. The network configures a drx-onDurationTimer value for the second DRX group that is smaller than the drx-onDurationTimer configured for the default DRX group in IE DRX-Config. |
The IE FreqBandIndicatorNR is used to convey an NR frequency band number as defined in TS 38.101-1 [15] and TS 38.101-2 [39].
The IE FrequencyInfoDL provides basic parameters of a downlink carrier and transmission thereon.
-- ASN1START -- TAG-FREQUENCYINFODL-START FrequencyInfoDL ::= SEQUENCE {absoluteFrequencySSBFrequency of the SSB to be used for this serving cell. SSB related parameters (e.g. SSB index) provided for a serving cell refer to this SSB frequency unless mentioned otherwise. The cell-defining SSB of the PCell is always on the sync raster. Frequencies are considered to be on the sync raster if they are also identifiable with a GSCN value (see TS 38.101-1 [15]). If the field is absent, the SSB related parameters should be absent, e.g. ssb-PositionsInBurst, ssb-periodicityServingCell and subcarrierSpacing in ServingCellConfigCommon IE. If the field is absent, the UE obtains timing reference from the SpCellor an SCell if applicable as described in TS 38.213 [13], clause 4.1. This is only supported in case the SCell for which the UE obtains the timing reference is in the same frequency band as the cell (i.e. the SpCell or the SCell, respectively) from which the UE obtains the timing reference.ARFCN-ValueNR OPTIONAL, -- Cond SpCellAddfrequencyBandListList containing only one frequency band to which this carrier(s) belongs. Multiple values are not supported.MultiFrequencyBandListNR,absoluteFrequencyPointAAbsolute frequency position of the reference resource block (Common RB 0). Its lowest subcarrier is also known as Point A (see TS 38.211 [16], clause 4.4.4.2). Note that the lower edge of the actual carrier is not defined by this field but rather in the scs-SpecificCarrierList.ARFCN-ValueNR,scs-SpecificCarrierListA set of carriers for different subcarrier spacings (numerologies). Defined in relation to Point A. The network configures a scs-SpecificCarrier at least for each numerology (SCS) that is used e.g. in a BWP (see TS 38.211 [16], clause 5.3).SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier, ... } -- TAG-FREQUENCYINFODL-STOP -- ASN1STOP
FrequencyInfoDL field descriptions |
---|
absoluteFrequencyPointA Absolute frequency position of the reference resource block (Common RB 0). Its lowest subcarrier is also known as Point A (see TS 38.211 [16], clause 4.4.4.2). Note that the lower edge of the actual carrier is not defined by this field but rather in the scs-SpecificCarrierList. |
absoluteFrequencySSB Frequency of the SSB to be used for this serving cell. SSB related parameters (e.g. SSB index) provided for a serving cell refer to this SSB frequency unless mentioned otherwise. The cell-defining SSB of the PCell is always on the sync raster. Frequencies are considered to be on the sync raster if they are also identifiable with a GSCN value (see TS 38.101-1 [15]). If the field is absent, the SSB related parameters should be absent, e.g. ssb-PositionsInBurst, ssb-periodicityServingCell and subcarrierSpacing in ServingCellConfigCommon IE. If the field is absent, the UE obtains timing reference from the SpCellor an SCell if applicable as described in TS 38.213 [13], clause 4.1. This is only supported in case the SCell for which the UE obtains the timing reference is in the same frequency band as the cell (i.e. the SpCell or the SCell, respectively) from which the UE obtains the timing reference. |
frequencyBandList List containing only one frequency band to which this carrier(s) belongs. Multiple values are not supported. |
scs-SpecificCarrierList A set of carriers for different subcarrier spacings (numerologies). Defined in relation to Point A. The network configures a scs-SpecificCarrier at least for each numerology (SCS) that is used e.g. in a BWP (see TS 38.211 [16], clause 5.3). |
Conditional Presence | Explanation |
---|---|
SpCellAdd | The field is mandatory present if this FrequencyInfoDL is for SpCell. Otherwise the field is optionally present, Need S. |
The IE FrequencyInfoDL-SIB provides basic parameters of a downlink carrier and transmission thereon.
-- ASN1START -- TAG-FREQUENCYINFODL-SIB-START FrequencyInfoDL-SIB ::= SEQUENCE {frequencyBandListList of one or multiple frequency bands to which this carrier(s) belongs.MultiFrequencyBandListNR-SIB,offsetToPointARepresents the offset to Point A as defined in TS 38.211 [16], clause 4.4.4.2.INTEGER (0..2199),scs-SpecificCarrierListA set of carriers for different subcarrier spacings (numerologies). Defined in relation to Point A (see TS 38.211 [16], clause 5.3). The network configures this for all SCSs that are used in DL BWPs in this serving cell.SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier } -- TAG-FREQUENCYINFODL-SIB-STOP -- ASN1STOP
FrequencyInfoDL-SIB field descriptions |
---|
offsetToPointA Represents the offset to Point A as defined in TS 38.211 [16], clause 4.4.4.2. |
frequencyBandList List of one or multiple frequency bands to which this carrier(s) belongs. |
scs-SpecificCarrierList A set of carriers for different subcarrier spacings (numerologies). Defined in relation to Point A (see TS 38.211 [16], clause 5.3). The network configures this for all SCSs that are used in DL BWPs in this serving cell. |
The IE FrequencyInfoUL provides basic parameters of an uplink carrier and transmission thereon.
-- ASN1START -- TAG-FREQUENCYINFOUL-START FrequencyInfoUL ::= SEQUENCE {frequencyBandListList containing only one frequency band to which this carrier(s) belongs. Multiple values are not supported.MultiFrequencyBandListNR OPTIONAL, -- Cond FDD-OrSULabsoluteFrequencyPointAAbsolute frequency of the reference resource block (Common RB 0). Its lowest subcarrier is also known as Point A. Note that the lower edge of the actual carrier is not defined by this field but rather in the scs-SpecificCarrierList (see TS 38.211 [16], clause 4.4.4.2).ARFCN-ValueNR OPTIONAL, -- Cond FDD-OrSULscs-SpecificCarrierListA set of carriers for different subcarrier spacings (numerologies). Defined in relation to Point A. The network configures a scs-SpecificCarrier at least for each numerology (SCS) that is used e.g. in a BWP (see TS 38.211 [16], clause 5.3).SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier,additionalSpectrumEmissionThe additional spectrum emission requirements to be applied by the UE on this uplink. If the field is absent, the UE uses value 0 for the additionalSpectrumEmission (see TS 38.101-1 [15], tables 6.2.3.1-1A, 6.2A.3.1.1-2 and 6.2A.3.1.2-2, and TS 38.101-2 [39], tables 6.2.3.1-2 and 6.2A.3.1-2).Network configures the same value in additionalSpectrumEmission for all uplink carrier(s) of the same band with UL configured, except for additionalSpectrumEmission value corresponding to NS_55. If NS_55 (see TS 38.101-1 [15], table 6.2.3.1-1) is applicable for at least one uplink carrier, the network may configure either NS_55 or NS_01 for these uplink carriers, and NS_01 for the remaining uplink carrier(s) of band n77. The additionalSpectrumEmission is applicable for all uplink carriers of the same band with UL configured.AdditionalSpectrumEmission OPTIONAL, -- Need Sp-MaxMaximum transmit power allowed in this serving cell. The maximum transmit power that the UE may use on this serving cell may be additionally limited by p-NR-FR1 (configured for the cell group) and by p-UE-FR1 (configured total for all serving cells operating on FR1). If absent, the UE applies the maximum power according to TS 38.101-1 [15]in case of an FR1 cell or TS 38.101-2 [39] in case of an FR2 cell. In this release of the specification, if p-Max is present on a carrier frequency in FR2, the UE shall ignore the field and applies the maximum power according to TS 38.101-2 [39]. Value in dBm.This field is ignored by IAB-MT, the IAB-MT applies output power and emissions requirements, as specified in TS 38.174 [63].P-Max OPTIONAL, -- Need SfrequencyShift7p5khzEnable the NR UL transmission with a 7.5 kHz shift to the LTE raster. If the field is absent, the frequency shift is disabled.ENUMERATED {true} OPTIONAL, -- Cond FDD-TDD-OrSUL-Optional ... } -- TAG-FREQUENCYINFOUL-STOP -- ASN1STOP
FrequencyInfoUL field descriptions |
---|
absoluteFrequencyPointA Absolute frequency of the reference resource block (Common RB 0). Its lowest subcarrier is also known as Point A. Note that the lower edge of the actual carrier is not defined by this field but rather in the scs-SpecificCarrierList (see TS 38.211 [16], clause 4.4.4.2). |
additionalSpectrumEmission The additional spectrum emission requirements to be applied by the UE on this uplink. If the field is absent, the UE uses value 0 for the additionalSpectrumEmission (see TS 38.101-1 [15], tables 6.2.3.1-1A, 6.2A.3.1.1-2 and 6.2A.3.1.2-2, and TS 38.101-2 [39], tables 6.2.3.1-2 and 6.2A.3.1-2).Network configures the same value in additionalSpectrumEmission for all uplink carrier(s) of the same band with UL configured, except for additionalSpectrumEmission value corresponding to NS_55. If NS_55 (see TS 38.101-1 [15], table 6.2.3.1-1) is applicable for at least one uplink carrier, the network may configure either NS_55 or NS_01 for these uplink carriers, and NS_01 for the remaining uplink carrier(s) of band n77. The additionalSpectrumEmission is applicable for all uplink carriers of the same band with UL configured. |
frequencyBandList List containing only one frequency band to which this carrier(s) belongs. Multiple values are not supported. |
frequencyShift7p5khz Enable the NR UL transmission with a 7.5 kHz shift to the LTE raster. If the field is absent, the frequency shift is disabled. |
p-Max Maximum transmit power allowed in this serving cell. The maximum transmit power that the UE may use on this serving cell may be additionally limited by p-NR-FR1 (configured for the cell group) and by p-UE-FR1 (configured total for all serving cells operating on FR1). If absent, the UE applies the maximum power according to TS 38.101-1 [15]in case of an FR1 cell or TS 38.101-2 [39] in case of an FR2 cell. In this release of the specification, if p-Max is present on a carrier frequency in FR2, the UE shall ignore the field and applies the maximum power according to TS 38.101-2 [39]. Value in dBm.This field is ignored by IAB-MT, the IAB-MT applies output power and emissions requirements, as specified in TS 38.174 [63]. |
scs-SpecificCarrierList A set of carriers for different subcarrier spacings (numerologies). Defined in relation to Point A. The network configures a scs-SpecificCarrier at least for each numerology (SCS) that is used e.g. in a BWP (see TS 38.211 [16], clause 5.3). |
Conditional Presence | Explanation |
---|---|
FDD-OrSUL | The field is mandatory present if this FrequencyInfoUL is for the paired UL for a DL (defined in a FrequencyInfoDL) or if this FrequencyInfoUL is for a supplementary uplink (SUL). It is absent, Need R, otherwise (if this FrequencyInfoUL is for an unpaired UL (TDD). |
FDD-TDD-OrSUL-Optional | The field is optionally present, Need R, if this FrequencyInfoUL is for the paired UL for a DL (defined in a FrequencyInfoDL), or if this FrequencyInfoUL is for an unpaired UL (TDD) in certain bands (as defined in clause 5.4.2.1 of TS 38.101-1 and in clause 5.4.2.1 of TS 38.104 [12]), or if this FrequencyInfoUL is for a supplementary uplink (SUL). It is absent, Need R, otherwise. |
The IE FrequencyInfoUL-SIB provides basic parameters of an uplink carrier and transmission thereon.
-- ASN1START -- TAG-FREQUENCYINFOUL-SIB-START FrequencyInfoUL-SIB ::= SEQUENCE {frequencyBandListProvides the frequency band indicator and a list of additionalPmax and additionalSpectrumEmission values as defined in TS 38.101-1 [15], table 6.2.3.1-1, and TS 38.101-2 [39], table 6.2.3.1-2. The UE shall apply the first listed band which it supports in the frequencyBandList field.MultiFrequencyBandListNR-SIB OPTIONAL, -- Cond FDD-OrSULabsoluteFrequencyPointAAbsolute frequency of the reference resource block (Common RB 0). Its lowest subcarrier is also known as Point A. Note that the lower edge of the actual carrier is not defined by this field but rather in the scs-SpecificCarrierList (see TS 38.211 [16], clause 4.4.4.2).ARFCN-ValueNR OPTIONAL, -- Cond FDD-OrSULscs-SpecificCarrierListA set of carriers for different subcarrier spacings (numerologies). Defined in relation to Point A (see TS 38.211 [16], clause 5.3). The network configures this for all SCSs that are used in UL BWPs configured in this serving cell.SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier,p-MaxValue in dBm applicable for the cell. If absent the UE applies the maximum power according to TS 38.101-1 [15] in case of an FR1 cell or TS 38.101-2 [39] in case of an FR2 cell. In this release of the specification, if p-Max is present on a carrier frequency in FR2, the UE shall ignore the field and applies the maximum power according to TS 38.101-2 [39]. This field is ignored by IAB-MT, the IAB-MT applies output power and emissions requirements, as specified in TS 38.174 [63].P-Max OPTIONAL, -- Need SfrequencyShift7p5khzEnable the NR UL transmission with a 7.5 kHz shift to the LTE raster. If the field is absent, the frequency shift is disabled.ENUMERATED {true} OPTIONAL, -- Cond FDD-TDD-OrSUL-Optional ... } -- TAG-FREQUENCYINFOUL-SIB-STOP -- ASN1STOP
FrequencyInfoUL-SIB field descriptions |
---|
absoluteFrequencyPointA Absolute frequency of the reference resource block (Common RB 0). Its lowest subcarrier is also known as Point A. Note that the lower edge of the actual carrier is not defined by this field but rather in the scs-SpecificCarrierList (see TS 38.211 [16], clause 4.4.4.2). |
frequencyBandList Provides the frequency band indicator and a list of additionalPmax and additionalSpectrumEmission values as defined in TS 38.101-1 [15], table 6.2.3.1-1, and TS 38.101-2 [39], table 6.2.3.1-2. The UE shall apply the first listed band which it supports in the frequencyBandList field. |
frequencyShift7p5khz Enable the NR UL transmission with a 7.5 kHz shift to the LTE raster. If the field is absent, the frequency shift is disabled. |
p-Max Value in dBm applicable for the cell. If absent the UE applies the maximum power according to TS 38.101-1 [15] in case of an FR1 cell or TS 38.101-2 [39] in case of an FR2 cell. In this release of the specification, if p-Max is present on a carrier frequency in FR2, the UE shall ignore the field and applies the maximum power according to TS 38.101-2 [39]. This field is ignored by IAB-MT, the IAB-MT applies output power and emissions requirements, as specified in TS 38.174 [63]. |
scs-SpecificCarrierList A set of carriers for different subcarrier spacings (numerologies). Defined in relation to Point A (see TS 38.211 [16], clause 5.3). The network configures this for all SCSs that are used in UL BWPs configured in this serving cell. |
Conditional Presence | Explanation |
---|---|
FDD-OrSUL | The field is mandatory present if this FrequencyInfoUL-SIB is for the paired UL for a DL (defined in a FrequencyInfoDL-SIB) or if this FrequencyInfoUL-SIB is for a supplementary uplink (SUL). It is absent otherwise (if this FrequencyInfoUL-SIB is for an unpaired UL (TDD). |
FDD-TDD-OrSUL-Optional | The field is optionally present, Need R, if this FrequencyInfoUL-SIB is for the paired UL for a DL (defined in a FrequencyInfoDL-SIB), or if this FrequencyInfoUL-SIB is for an unpaired UL (TDD) in certain bands (as defined in clause 5.4.2.1 of TS 38.101-1 and in clause 5.4.2.1 of TS 38.104 [12]), or if this FrequencyInfoUL-SIB is for a supplementary uplink (SUL). It is absent otherwise. |
The IE HighSpeedConfig is used to configure parameters for high speed scenarios.
-- ASN1START -- TAG-HIGHSPEEDCONFIG-START HighSpeedConfig-r16 ::= SEQUENCE {highSpeedMeasFlag-r16If the field is presentandUE supportsmeasurementEnhancement-r16, the UE shall apply the enhanced intra-NR and inter-RAT EUTRANRRM requirements to support high speed up to 500 km/h as specified in TS 38.133 [14]. If the field is present and UE supports intraNR-MeasurementEnhancement-r16, the UE shall apply enhanced intra-NR RRM requirement to support high speed up to 500 km/h as specified in TS 38.133 [14]. If the field is present and UE supports interRAT-MeasurementEnhancement-r16, the UE shall apply enhanced inter-RAT EUTRAN RRM requirement to support high speed up to 500 km/h as specified in TS 38.133 [14]. This parameter only applies to the serving frequency of SpCell.ENUMERATED {true} OPTIONAL, -- Cond SpCellOnlyhighSpeedDemodFlag-r16If the field is present and UE supports demodulationEnhancement-r16, the UE shall apply the enhanced demodulation processing for HST-SFN joint transmission scheme with velocity up to 500km/h as specified in TS 38.101-4 [59]. This parameter only applies to SpCell.ENUMERATED {true} OPTIONAL, -- Need R ... } -- TAG-HIGHSPEEDCONFIG-STOP -- ASN1STOP
HighSpeedConfig field descriptions |
---|
highSpeedMeasFlag If the field is presentandUE supportsmeasurementEnhancement-r16, the UE shall apply the enhanced intra-NR and inter-RAT EUTRANRRM requirements to support high speed up to 500 km/h as specified in TS 38.133 [14]. If the field is present and UE supports intraNR-MeasurementEnhancement-r16, the UE shall apply enhanced intra-NR RRM requirement to support high speed up to 500 km/h as specified in TS 38.133 [14]. If the field is present and UE supports interRAT-MeasurementEnhancement-r16, the UE shall apply enhanced inter-RAT EUTRAN RRM requirement to support high speed up to 500 km/h as specified in TS 38.133 [14]. This parameter only applies to the serving frequency of SpCell. |
highSpeedDemodFlag If the field is present and UE supports demodulationEnhancement-r16, the UE shall apply the enhanced demodulation processing for HST-SFN joint transmission scheme with velocity up to 500km/h as specified in TS 38.101-4 [59]. This parameter only applies to SpCell. |
Conditional Presence | Explanation |
---|---|
SpCellOnly | The field is optionally present, Need R, in the ServingCellConfigCommonSIB or in the ServingCellConfigCommon of an SpCell. It is absent otherwise. |
The IE Hysteresis is a parameter used within the entry and leave condition of an event triggered reporting condition. The actual value is field value * 0.5 dB.
The IE InvalidSymbolPattern is used to configure one invalid symbol pattern for PUSCH transmission repetition type B applicable for both DCI format 0_1 and 0_2, see TS 38.214 [19], clause 6.1.
-- ASN1START -- TAG-INVALIDSYMBOLPATTERN-START InvalidSymbolPattern-r16 ::= SEQUENCE {symbols-r16A symbol level bitmap in time domain (see TS 38.214[19], clause 6.1). For oneSlot, if ECP is configured, the first 12 bits represent the symbols within the slot and the last two bits within the bitstring are ignored by the UE; Otherwise, the 14 bits represent the symbols within the slot. For twoSlots, if ECP is configured, the first 12 bits represent the symbols within the first slot and the next 12 bits represent the symbols in the second slot and the last four bits within the bit string are ignored by the UE; Otherwise, the first 14 bits represent the symbols within the first slot and the next 14 bits represent the symbols in the second slot. For the bits representing symbols in a slot, the most significant bit of the bit string represents the first symbol in the slot and the second most significant bit represents the second symbol in the slot and so on. This pattern recurs (in time domain) with the configured periodicityAndPattern.CHOICE { oneSlot BIT STRING (SIZE (14)), twoSlots BIT STRING (SIZE (28)) },periodicityAndPattern-r16A time domain repetition pattern at which the pattern defined by symbols recurs. This slot pattern repeats itself continuously. When the field is not configured, the UE uses the value n1 (see TS 38.214 [19], clause 6.1).CHOICE { n2 BIT STRING (SIZE (2)), n4 BIT STRING (SIZE (4)), n5 BIT STRING (SIZE (5)), n8 BIT STRING (SIZE (8)), n10 BIT STRING (SIZE (10)), n20 BIT STRING (SIZE (20)), n40 BIT STRING (SIZE (40)) } OPTIONAL, -- Need M ... } -- TAG-INVALIDSYMBOLPATTERN-STOP -- ASN1STOP
InvalidSymbolPattern field descriptions |
---|
periodicityAndPattern A time domain repetition pattern at which the pattern defined by symbols recurs. This slot pattern repeats itself continuously. When the field is not configured, the UE uses the value n1 (see TS 38.214 [19], clause 6.1). |
symbols A symbol level bitmap in time domain (see TS 38.214[19], clause 6.1). For oneSlot, if ECP is configured, the first 12 bits represent the symbols within the slot and the last two bits within the bitstring are ignored by the UE; Otherwise, the 14 bits represent the symbols within the slot. For twoSlots, if ECP is configured, the first 12 bits represent the symbols within the first slot and the next 12 bits represent the symbols in the second slot and the last four bits within the bit string are ignored by the UE; Otherwise, the first 14 bits represent the symbols within the first slot and the next 14 bits represent the symbols in the second slot. For the bits representing symbols in a slot, the most significant bit of the bit string represents the first symbol in the slot and the second most significant bit represents the second symbol in the slot and so on. This pattern recurs (in time domain) with the configured periodicityAndPattern. |
The IE I-RNTI-Value is used to identify the suspended UE context of a UE in RRC_INACTIVE.
The IE LBT-FailureRecoveryConfig-r16 is used to configure the parameters used for detection of consistent uplink LBT failures for operation with shared spectrum channel access, as specified in TS 38.321 [3].
-- ASN1START -- TAG-LBT-FAILURERECOVERYCONFIG-START LBT-FailureRecoveryConfig-r16 ::= SEQUENCE { lbt-FailureInstanceMaxCount-r16 ENUMERATED {n4, n8, n16, n32, n64, n128}, lbt-FailureDetectionTimer-r16 ENUMERATED {ms10, ms20, ms40, ms80, ms160, ms320}, ... } -- TAG-LBT-FAILURERECOVERYCONFIG-STOP -- ASN1STOP
The IE LocationInfo is used to transfer available detailed location information, Bluetooth, WLAN and sensor available measurement results at the UE.
-- ASN1START -- TAG-LOCATIONINFO-START LocationInfo-r16 ::= SEQUENCE { commonLocationInfo-r16 CommonLocationInfo-r16 OPTIONAL, bt-LocationInfo-r16 LogMeasResultListBT-r16 OPTIONAL, wlan-LocationInfo-r16 LogMeasResultListWLAN-r16 OPTIONAL, sensor-LocationInfo-r16 Sensor-LocationInfo-r16 OPTIONAL, ... } -- TAG-LOCATIONINFO-STOP -- ASN1STOP
LBT-FailureRecoveryConfig field descriptions |
---|
lbt-FailureDetectionTimer Timer for consistent uplink LBT failure detection (see TS 38.321 [3]). Value ms10 corresponds to 10 ms, value ms20 corresponds to 20 ms, and so on. |
lbt-FailureInstanceMaxCount This field determines after how many LBT failure indications received from the physical layer the UE triggers uplink LBT failure recovery (see TS 38.321 [3]). Value n4 corresponds to 4, value n8 corresponds to 8, and so on. |
The IE LocationMeasurementInfo defines the information sent by the UE to the network to assist with the configuration of measurement gaps for location related measurements.
-- ASN1START -- TAG-LOCATIONMEASUREMENTINFO-START LocationMeasurementInfo ::= CHOICE { eutra-RSTD EUTRA-RSTD-InfoList, ..., eutra-FineTimingDetection NULL, nr-PRS-Measurement-r16 NR-PRS-MeasurementInfoList-r16 } EUTRA-RSTD-InfoList ::= SEQUENCE (SIZE (1..maxInterRAT-RSTD-Freq)) OF EUTRA-RSTD-Info EUTRA-RSTD-Info ::= SEQUENCE {carrierFreqThe EARFCN value of the carrier received from upper layers for which the UE needs to perform the inter-RAT RSTD measurements.ARFCN-ValueEUTRA,measPRS-OffsetIndicates the requested gap offset for performing RSTD measurements towards E-UTRA. It is the smallest subframe offset from the beginning of subframe 0 of SFN=0 of the serving cell of the requested gap for measuring PRS positioning occasions in the carrier frequency carrierFreq for which the UE needs to perform the inter-RAT RSTD measurements. The PRS positioning occasion information is received from upper layers. The value of measPRS-Offset is obtained by mapping the starting subframe of the PRS positioning occasion in the measured cell onto the corresponding subframe in the serving cell and is calculated as the serving cell's number of subframes from SFN=0 mod 40. The UE shall take into account any additional time required by the UE to start PRS measurements on the other carrier when it does this mapping for determining the measPRS-Offset. NOTE:Figure 6.2.2-1 in TS 36.331[10] illustrates the measPRS-Offset field.INTEGER (0..39), ... } NR-PRS-MeasurementInfoList-r16 ::= SEQUENCE (SIZE (1..maxFreqLayers)) OF NR-PRS-MeasurementInfo-r16 NR-PRS-MeasurementInfo-r16 ::= SEQUENCE {dl-PRS-PointA-r16The ARFCN value of the carrier received from upper layers for which the UE needs to perform the NR DL-PRS measurements.ARFCN-ValueNR,nr-MeasPRS-RepetitionAndOffset-r16Indicates the gap periodicity in ms and offset in number of subframes of the requested measurement gap for performing NR DL-PRS measurements.CHOICE { ms20-r16 INTEGER (0..19), ms40-r16 INTEGER (0..39), ms80-r16 INTEGER (0..79), ms160-r16 INTEGER (0..159), ... },nr-MeasPRS-length-r16Indicates measurement gap length in ms of the requested measurement gap for performing NR DL-PRS measurements. The measurement gap length is according to in Table 9.1.2-1 in TS 38.133 [14].ENUMERATED {ms1dot5, ms3, ms3dot5, ms4, ms5dot5, ms6, ms10, ms20}, ... } -- TAG-LOCATIONMEASUREMENTINFO-STOP -- ASN1STOP
LocationMeasurementInfo field descriptions |
---|
carrierFreq The EARFCN value of the carrier received from upper layers for which the UE needs to perform the inter-RAT RSTD measurements. |
measPRS-Offset Indicates the requested gap offset for performing RSTD measurements towards E-UTRA. It is the smallest subframe offset from the beginning of subframe 0 of SFN=0 of the serving cell of the requested gap for measuring PRS positioning occasions in the carrier frequency carrierFreq for which the UE needs to perform the inter-RAT RSTD measurements. The PRS positioning occasion information is received from upper layers. The value of measPRS-Offset is obtained by mapping the starting subframe of the PRS positioning occasion in the measured cell onto the corresponding subframe in the serving cell and is calculated as the serving cell's number of subframes from SFN=0 mod 40. The UE shall take into account any additional time required by the UE to start PRS measurements on the other carrier when it does this mapping for determining the measPRS-Offset. NOTE:Figure 6.2.2-1 in TS 36.331[10] illustrates the measPRS-Offset field. |
dl-PRS-PointA The ARFCN value of the carrier received from upper layers for which the UE needs to perform the NR DL-PRS measurements. |
nr-MeasPRS-RepetitionAndOffset Indicates the gap periodicity in ms and offset in number of subframes of the requested measurement gap for performing NR DL-PRS measurements. |
nr-MeasPRS-length Indicates measurement gap length in ms of the requested measurement gap for performing NR DL-PRS measurements. The measurement gap length is according to in Table 9.1.2-1 in TS 38.133 [14]. |
The IE LogicalChannelConfig is used to configure the logical channel parameters.
-- ASN1START -- TAG-LOGICALCHANNELCONFIG-START LogicalChannelConfig ::= SEQUENCE { ul-SpecificParameters SEQUENCE {priorityLogical channel priority, as specified in TS 38.321 [3].INTEGER (1..16),prioritisedBitRateValue in kiloBytes/s. Value kBps0 corresponds to 0 kiloBytes/s, value kBps8 corresponds to 8 kiloBytes/s, value kBps16 corresponds to 16 kiloBytes/s, and so on. For SRBs, the value can only be set to infinity.ENUMERATED {kBps0, kBps8, kBps16, kBps32, kBps64, kBps128, kBps256, kBps512, kBps1024, kBps2048, kBps4096, kBps8192, kBps16384, kBps32768, kBps65536, infinity},bucketSizeDurationValue in ms. ms5 corresponds to 5 ms, value ms10 corresponds to 10 ms, and so on.ENUMERATED {ms5, ms10, ms20, ms50, ms100, ms150, ms300, ms500, ms1000, spare7, spare6, spare5, spare4, spare3,spare2, spare1},allowedServingCellsIf present, UL MAC SDUs from this logical channel can only be mapped to the serving cells indicated in this list. Otherwise, UL MAC SDUs from this logical channel can be mapped to any configured serving cell of this cell group. Corresponds to 'allowedServingCells' in TS 38.321 [3].SEQUENCE (SIZE (1..maxNrofServingCells-1)) OF ServCellIndex OPTIONAL, -- Cond PDCP-CADuplicationallowedSCS-ListIf present, UL MAC SDUs from this logical channel can only be mapped to the indicated numerology. Otherwise, UL MAC SDUs from this logical channel can be mapped to any configured numerology. Only the values 15/30/60 kHz (for FR1) and 60/120 kHz (for FR2) are applicable. Corresponds to 'allowedSCS-List' as specified in TS 38.321 [3].SEQUENCE (SIZE (1..maxSCSs)) OF SubcarrierSpacing OPTIONAL, -- Need RmaxPUSCH-DurationIf present, UL MAC SDUs from this logical channel can only be transmitted using uplink grants that result in a PUSCH duration shorter than or equal to the duration indicated by this field. Otherwise, UL MAC SDUs from this logical channel can be transmitted using an uplink grant resulting in any PUSCH duration. Corresponds to "maxPUSCH-Duration" in TS 38.321 [3]. The PUSCH duration is calculated based on the same length of all symbols, and the shortest length applies if the symbol lengths are different.ENUMERATED {ms0p02, ms0p04, ms0p0625, ms0p125, ms0p25, ms0p5, spare2, spare1} OPTIONAL, -- Need RconfiguredGrantType1AllowedIf present, or if the capability lcp-Restriction as specified in TS 38.306 [26] is not supported, UL MAC SDUs from this logical channel can be transmitted on a configured grant type 1. Otherwise, UL MAC SDUs from this logical channel cannot be transmitted on a configured grant type 1. Corresponds to 'configuredGrantType1Allowed' in TS 38.321 [3].ENUMERATED {true} OPTIONAL, -- Need RlogicalChannelGroupID of the logical channel group, as specified in TS 38.321 [3], which the logical channel belongs to.INTEGER (0..maxLCG-ID) OPTIONAL, -- Need R schedulingRequestID SchedulingRequestId OPTIONAL, -- Need RlogicalChannelSR-MaskControls SR triggering when a configured uplink grant of type1 or type2 is configured. true indicates that SR masking is configured for this logical channelas specified in TS 38.321 [3].BOOLEAN,logicalChannelSR-DelayTimerAppliedIndicates whether to apply the delay timer for SR transmission for this logical channel. Set to false if logicalChannelSR-DelayTimer is not included in BSR-Config.BOOLEAN, ...,bitRateQueryProhibitTimerThe timer is used for bit rate recommendation query in TS 38.321 [3], in seconds. Value s0 means 0 s, s0dot4 means 0.4 s and so on.ENUMERATED {s0, s0dot4, s0dot8, s1dot6, s3, s6, s12, s30} OPTIONAL, -- Need R [[allowedCG-List-r16This restriction applies only when the UL grant is a configured grant. If present, UL MAC SDUs from this logical channel can only be mapped to the indicated configured grant configuration. If the size of the sequence is zero, then UL MAC SDUs from this logical channel cannot be mapped to any configured grant configurations. If the field is not present, UL MAC SDUs from this logical channel can be mapped to any configured grant configurations. If the field configuredGrantType1Allowed is present, only those configured grant type 1 configuration indicated in this sequence are allowed for use by this logical channel; otherwise, this sequence shall not include any configured grant type 1 configuration. Corresponds to "allowedCG-List" as specified in TS 38.321 [3].SEQUENCE (SIZE (0.. maxNrofConfiguredGrantConfigMAC-1-r16)) OF ConfiguredGrantConfigIndexMAC-r16 OPTIONAL, -- Need SallowedPHY-PriorityIndex-r16This restriction applies only when the UL grant is a dynamic grant. If the field is present and the dynamic grant has a PHY-priority index, UL MAC SDUs from this logical channel can only be mapped to the dynamic grants indicating PHY-priority index equal to the values configured by this field. If the field is present and the dynamic grant does not have a PHY-priority index, UL MAC SDUs from this logical channel can only be mapped to this dynamic grant if the value of the field is p0, see TS 38.213 [13], clause 9. If the field is not present, UL MAC SDUs from this logical channel can be mapped to any dynamic grants. Corresponds to "allowedPHY-PriorityIndex" as specified in TS 38.321 [3].ENUMERATED {p0, p1} OPTIONAL -- Need S ]] } OPTIONAL, -- Cond UL ..., [[channelAccessPriority-r16Indicates the Channel Access Priority Class (CAPC), as specified in TS 38.300 [2], to be used on uplink transmissions for operation with shared spectrum channel access. The network configures this field only for SRB2 and DRBs.INTEGER (1..4) OPTIONAL, -- Need RbitRateMultiplier-r16Bit rate multiplier for recommended bit rate MAC CE as specified in TS 38.321 [3]. Value x40 indicates bit rate multiplier 40, value x70 indicates bit rate multiplier 70 and so on.ENUMERATED {x40, x70, x100, x200} OPTIONAL -- Need R ]] } -- TAG-LOGICALCHANNELCONFIG-STOP -- ASN1STOP
LogicalChannelConfig field descriptions |
---|
allowedCG-List This restriction applies only when the UL grant is a configured grant. If present, UL MAC SDUs from this logical channel can only be mapped to the indicated configured grant configuration. If the size of the sequence is zero, then UL MAC SDUs from this logical channel cannot be mapped to any configured grant configurations. If the field is not present, UL MAC SDUs from this logical channel can be mapped to any configured grant configurations. If the field configuredGrantType1Allowed is present, only those configured grant type 1 configuration indicated in this sequence are allowed for use by this logical channel; otherwise, this sequence shall not include any configured grant type 1 configuration. Corresponds to "allowedCG-List" as specified in TS 38.321 [3]. |
allowedPHY-PriorityIndex This restriction applies only when the UL grant is a dynamic grant. If the field is present and the dynamic grant has a PHY-priority index, UL MAC SDUs from this logical channel can only be mapped to the dynamic grants indicating PHY-priority index equal to the values configured by this field. If the field is present and the dynamic grant does not have a PHY-priority index, UL MAC SDUs from this logical channel can only be mapped to this dynamic grant if the value of the field is p0, see TS 38.213 [13], clause 9. If the field is not present, UL MAC SDUs from this logical channel can be mapped to any dynamic grants. Corresponds to "allowedPHY-PriorityIndex" as specified in TS 38.321 [3]. |
allowedSCS-List If present, UL MAC SDUs from this logical channel can only be mapped to the indicated numerology. Otherwise, UL MAC SDUs from this logical channel can be mapped to any configured numerology. Only the values 15/30/60 kHz (for FR1) and 60/120 kHz (for FR2) are applicable. Corresponds to 'allowedSCS-List' as specified in TS 38.321 [3]. |
allowedServingCells If present, UL MAC SDUs from this logical channel can only be mapped to the serving cells indicated in this list. Otherwise, UL MAC SDUs from this logical channel can be mapped to any configured serving cell of this cell group. Corresponds to 'allowedServingCells' in TS 38.321 [3]. |
bitRateMultiplier Bit rate multiplier for recommended bit rate MAC CE as specified in TS 38.321 [3]. Value x40 indicates bit rate multiplier 40, value x70 indicates bit rate multiplier 70 and so on. |
bitRateQueryProhibitTimer The timer is used for bit rate recommendation query in TS 38.321 [3], in seconds. Value s0 means 0 s, s0dot4 means 0.4 s and so on. |
bucketSizeDuration Value in ms. ms5 corresponds to 5 ms, value ms10 corresponds to 10 ms, and so on. |
channelAccessPriority Indicates the Channel Access Priority Class (CAPC), as specified in TS 38.300 [2], to be used on uplink transmissions for operation with shared spectrum channel access. The network configures this field only for SRB2 and DRBs. |
configuredGrantType1Allowed If present, or if the capability lcp-Restriction as specified in TS 38.306 [26] is not supported, UL MAC SDUs from this logical channel can be transmitted on a configured grant type 1. Otherwise, UL MAC SDUs from this logical channel cannot be transmitted on a configured grant type 1. Corresponds to 'configuredGrantType1Allowed' in TS 38.321 [3]. |
logicalChannelGroup ID of the logical channel group, as specified in TS 38.321 [3], which the logical channel belongs to. |
logicalChannelSR-Mask Controls SR triggering when a configured uplink grant of type1 or type2 is configured. true indicates that SR masking is configured for this logical channelas specified in TS 38.321 [3]. |
logicalChannelSR-DelayTimerApplied Indicates whether to apply the delay timer for SR transmission for this logical channel. Set to false if logicalChannelSR-DelayTimer is not included in BSR-Config. |
maxPUSCH-Duration If present, UL MAC SDUs from this logical channel can only be transmitted using uplink grants that result in a PUSCH duration shorter than or equal to the duration indicated by this field. Otherwise, UL MAC SDUs from this logical channel can be transmitted using an uplink grant resulting in any PUSCH duration. Corresponds to "maxPUSCH-Duration" in TS 38.321 [3]. The PUSCH duration is calculated based on the same length of all symbols, and the shortest length applies if the symbol lengths are different. |
priority Logical channel priority, as specified in TS 38.321 [3]. |
prioritisedBitRate Value in kiloBytes/s. Value kBps0 corresponds to 0 kiloBytes/s, value kBps8 corresponds to 8 kiloBytes/s, value kBps16 corresponds to 16 kiloBytes/s, and so on. For SRBs, the value can only be set to infinity. |
schedulingRequestId If present, it indicates the scheduling request configuration applicable for this logical channel, as specified in TS 38.321 [3]. |
Conditional Presence | Explanation |
---|---|
PDCP-CADuplication | The field is mandatory present if the DRB/SRB associated with this logical channel is configured with PDCP CA duplication in UL in the cell group in which this IE is included (i.e. the PDCP entity is associated with multiple RLC entities belonging to this cell group). Otherwise the field is optionally present, need R. |
UL | The field is mandatory present for a logical channel with uplink if it serves DRB. It is optionally present, Need R, for a logical channel with uplink if it serves an SRB. Otherwise it is absent. |
The IE LogicalChannelIdentity is used to identify one logical channel (LogicalChannelConfig) and the corresponding RLC bearer (RLC-BearerConfig) or BH RLC channel (BH-RLC-ChannelConfig).
The IE MAC-CellGroupConfig is used to configure MAC parameters for a cell group, including DRX.
-- ASN1START -- TAG-MAC-CELLGROUPCONFIG-START MAC-CellGroupConfig ::= SEQUENCE {drx-ConfigUsed to configure DRX as specified in TS 38.321 [3].SetupRelease { DRX-Config } OPTIONAL, -- Need M schedulingRequestConfig SchedulingRequestConfig OPTIONAL, -- Need M bsr-Config BSR-Config OPTIONAL, -- Need Mtag-ConfigThe field is used to configure parameters for a time-alignment group. The field is not present if any DAPS bearer is configured.TAG-Config OPTIONAL, -- Need M phr-Config SetupRelease { PHR-Config } OPTIONAL, -- Need M skipUplinkTxDynamic BOOLEAN, ..., [[csi-MaskIf set to true, the UE limits CSI reports to the on-duration period of the DRX cycle, see TS 38.321 [3].BOOLEAN OPTIONAL, -- Need MdataInactivityTimerReleases the RRC connection upon data inactivity as specified in clause 5.3.8.5 and in TS 38.321 [3]. Value s1 corresponds to 1 second, value s2 corresponds to 2 seconds, and so on.SetupRelease { DataInactivityTimer } OPTIONAL -- Cond MCG-Only ]], [[usePreBSR-r16If set to true, the MAC entity of the IAB-MT may use the Pre-emptive BSR, see TS 38.321 [3].ENUMERATED {true} OPTIONAL, -- Need RschedulingRequestID-LBT-SCell-r16Indicates the scheduling request configuration applicable for consistent uplink LBT recovery on SCell, as specified in TS 38.321 [3].SchedulingRequestId OPTIONAL, -- Need Rlch-BasedPrioritization-r16If this field is present, the corresponding MAC entity of the UE is configured with prioritization between overlapping grants and between scheduling request and overlapping grants based on LCH priority, see TS 38.321 [3].The network does not configure lch-BasedPrioritization with enhancedSkipUplinkTxDynamicsimultaneously nor lch-BasedPrioritization withenhancedSkipUplinkTxConfiguredsimultaneously.ENUMERATED {enabled} OPTIONAL, -- Need RschedulingRequestID-BFR-SCell-r16Indicates the scheduling request configuration applicable for BFR on SCell, as specified in TS 38.321 [3].SchedulingRequestId OPTIONAL, -- Need Rdrx-ConfigSecondaryGroup-r16Used to configure DRX related parameters for the second DRX group as specified in TS 38.321 [3].The network does not configure secondary DRX group with DCP simultaneously nor secondary DRX group with a dormant BWP simultaneously.SetupRelease { DRX-ConfigSecondaryGroup-r16 } OPTIONAL -- Need M ]], [[ enhancedSkipUplinkTxDynamic-r16 ENUMERATED {true} OPTIONAL, -- Need R enhancedSkipUplinkTxConfigured-r16 ENUMERATED {true} OPTIONAL -- Need R ]] } DataInactivityTimer ::= ENUMERATED {s1, s2, s3, s5, s7, s10, s15, s20, s40, s50, s60, s80, s100, s120, s150, s180} -- TAG-MAC-CELLGROUPCONFIG-STOP -- ASN1STOP
MAC-CellGroupConfig field descriptions |
---|
csi-Mask If set to true, the UE limits CSI reports to the on-duration period of the DRX cycle, see TS 38.321 [3]. |
dataInactivityTimer Releases the RRC connection upon data inactivity as specified in clause 5.3.8.5 and in TS 38.321 [3]. Value s1 corresponds to 1 second, value s2 corresponds to 2 seconds, and so on. |
drx-Config Used to configure DRX as specified in TS 38.321 [3]. |
drx-ConfigSecondaryGroup Used to configure DRX related parameters for the second DRX group as specified in TS 38.321 [3].The network does not configure secondary DRX group with DCP simultaneously nor secondary DRX group with a dormant BWP simultaneously. |
lch-BasedPrioritization If this field is present, the corresponding MAC entity of the UE is configured with prioritization between overlapping grants and between scheduling request and overlapping grants based on LCH priority, see TS 38.321 [3].The network does not configure lch-BasedPrioritization with enhancedSkipUplinkTxDynamicsimultaneously nor lch-BasedPrioritization withenhancedSkipUplinkTxConfiguredsimultaneously. |
schedulingRequestID-BFR-SCell Indicates the scheduling request configuration applicable for BFR on SCell, as specified in TS 38.321 [3]. |
schedulingRequestID-LBT-SCell Indicates the scheduling request configuration applicable for consistent uplink LBT recovery on SCell, as specified in TS 38.321 [3]. |
skipUplinkTxDynamic, enhancedSkipUplinkTxDynamic, enhancedSkipUplinkTxConfigured If set to true, the UE skips UL transmissions as described in TS 38.321 [3].If the UE is configured with enhancedSkipUplinkTxDynamic or enhancedSkipUplinkTxConfigured with value true, REPETITION_NUMBER (as specified in TS 38.321 [3], clause 5.4.2.1) of the corresponding PUSCH transmission of the uplink grant shall be equal to 1. |
tag-Config The field is used to configure parameters for a time-alignment group. The field is not present if any DAPS bearer is configured. |
usePreBSR If set to true, the MAC entity of the IAB-MT may use the Pre-emptive BSR, see TS 38.321 [3]. |
Conditional Presence | Explanation |
---|---|
MCG-Only | This field is optionally present, Need M, for the MAC-CellGroupConfig of the MCG. It is absent otherwise. |
The IE MeasConfig specifies measurements to be performed by the UE,and covers intra-frequency, inter-frequency and inter-RAT mobility as well as configuration of measurement gaps.
-- ASN1START -- TAG-MEASCONFIG-START MeasConfig ::= SEQUENCE {measObjectToRemoveListList of measurement objects to remove.MeasObjectToRemoveList OPTIONAL, -- Need NmeasObjectToAddModListList of measurement objects to add and/or modify.MeasObjectToAddModList OPTIONAL, -- Need NreportConfigToRemoveListList of measurement reporting configurations to remove.ReportConfigToRemoveList OPTIONAL, -- Need NreportConfigToAddModListList of measurement reporting configurations to add and/or modify.ReportConfigToAddModList OPTIONAL, -- Need NmeasIdToRemoveListList of measurement identities to remove.MeasIdToRemoveList OPTIONAL, -- Need NmeasIdToAddModListList of measurement identities to add and/or modify.MeasIdToAddModList OPTIONAL, -- Need Ns-MeasureConfigThreshold for NR SpCell RSRP measurement controlling when the UE is required to perform measurements on non-serving cells. Choice of ssb-RSRP corresponds to cell RSRP based on SS/PBCH block and choice of csi-RSRP corresponds to cell RSRP of CSI-RS.CHOICE { ssb-RSRP RSRP-Range, csi-RSRP RSRP-Range } OPTIONAL, -- Need M quantityConfig QuantityConfig OPTIONAL, -- Need MmeasGapConfigUsed to setup and release measurement gaps in NR.MeasGapConfig OPTIONAL, -- Need MmeasGapSharingConfigSpecifies the measurement gap sharing scheme and controls setup/ release of measurement gap sharing.MeasGapSharingConfig OPTIONAL, -- Need M ..., [[interFrequencyConfig-NoGap-r16If the field is set to true, UE is configured to perform SSB based inter-frequency measurement without measurement gaps when the inter-frequency SSB is completely contained in the active DL BWP of the UE, as specified in TS 38.133 [14], clause 9.3. Otherwise, the SSB based inter-frequency measurement is performed within measurement gaps.In NR-DC, the field can only be configured in the measConfig associated with MCG, and when configured, it applies to all the inter-frequency measurements configured by MN and SN.ENUMERATED {true} OPTIONAL -- Need R ]] } MeasObjectToRemoveList ::= SEQUENCE (SIZE (1..maxNrofObjectId)) OF MeasObjectId MeasIdToRemoveList ::= SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasId ReportConfigToRemoveList ::= SEQUENCE (SIZE (1..maxReportConfigId)) OF ReportConfigId -- TAG-MEASCONFIG-STOP -- ASN1STOP
MeasConfig field descriptions |
---|
interFrequencyConfig-NoGap-r16 If the field is set to true, UE is configured to perform SSB based inter-frequency measurement without measurement gaps when the inter-frequency SSB is completely contained in the active DL BWP of the UE, as specified in TS 38.133 [14], clause 9.3. Otherwise, the SSB based inter-frequency measurement is performed within measurement gaps.In NR-DC, the field can only be configured in the measConfig associated with MCG, and when configured, it applies to all the inter-frequency measurements configured by MN and SN. |
measGapConfig Used to setup and release measurement gaps in NR. |
measIdToAddModList List of measurement identities to add and/or modify. |
measIdToRemoveList List of measurement identities to remove. |
measObjectToAddModList List of measurement objects to add and/or modify. |
measObjectToRemoveList List of measurement objects to remove. |
reportConfigToAddModList List of measurement reporting configurations to add and/or modify. |
reportConfigToRemoveList List of measurement reporting configurations to remove. |
s-MeasureConfig Threshold for NR SpCell RSRP measurement controlling when the UE is required to perform measurements on non-serving cells. Choice of ssb-RSRP corresponds to cell RSRP based on SS/PBCH block and choice of csi-RSRP corresponds to cell RSRP of CSI-RS. |
measGapSharingConfig Specifies the measurement gap sharing scheme and controls setup/ release of measurement gap sharing. |
The IE MeasGapConfig specifies the measurement gap configuration and controls setup/release of measurement gaps.
-- ASN1START -- TAG-MEASGAPCONFIG-START MeasGapConfig ::= SEQUENCE {gapFR2Indicates measurement gap configuration applies to FR2 only. In (NG)EN-DC or NE-DC, gapFR2 can only be set up by NR RRC (i.e. LTE RRC cannot configure FR2 gap). In NR-DC, gapFR2 can only be set up in the measConfig associated with MCG. gapFR2 cannot be configured together with gapUE. The applicability of the FR2 measurement gap is according to Table 9.1.2-2 and Table 9.1.2-3 in TS 38.133 [14].SetupRelease { GapConfig } OPTIONAL, -- Need M ..., [[gapFR1Indicates measurement gap configuration that applies to FR1 only. In (NG)EN-DC, gapFR1 cannot be set up by NR RRC (i.e. only LTE RRC can configure FR1 measurement gap). In NE-DC, gapFR1 can only be set up by NR RRC (i.e. LTE RRC cannot configure FR1 gap). In NR-DC, gapFR1 can only be set up in the measConfig associated with MCG. gapFR1 can not be configured together with gapUE. The applicability of the FR1 measurement gap is according to Table 9.1.2-2 and Table 9.1.2-3 in TS 38.133 [14].SetupRelease { GapConfig } OPTIONAL, -- Need MgapUEIndicates measurement gap configuration that applies to all frequencies (FR1 and FR2). In (NG)EN-DC, gapUE cannot be set up by NR RRC (i.e. only LTE RRC can configure per UE measurement gap). In NE-DC, gapUE can only be set up by NR RRC (i.e. LTE RRC cannot configure per UE gap). In NR-DC, gapUE can only be set up in the measConfig associated with MCG. If gapUE is configured, then neither gapFR1 nor gapFR2 can be configured. The applicability of the per UE measurement gap is according to Table 9.1.2-2 and Table 9.1.2-3 in TS 38.133 [14].SetupRelease { GapConfig } OPTIONAL -- Need M ]] } GapConfig ::= SEQUENCE {gapOffsetValue gapOffset is the gap offset of the gap pattern with MGRP indicated in the field mgrp. The value range is from 0 to mgrp-1.INTEGER (0..159),mglValue mgl is the measurement gap length in ms of the measurement gap. The measurement gap length is according to in Table 9.1.2-1 in TS 38.133 [14]. Value ms1dot5 corresponds to 1.5 ms, ms3 corresponds to 3 ms and so on. If mgl-r16 is present, UE shall ignore the mgl (without suffix).ENUMERATED {ms1dot5, ms3, ms3dot5, ms4, ms5dot5, ms6},mgrpValue mgrp is measurement gap repetition period in (ms) of the measurement gap. The measurement gap repetition period is according to Table 9.1.2-1 in TS 38.133 [14].ENUMERATED {ms20, ms40, ms80, ms160},mgtaValue mgta is the measurement gap timing advance in ms. The applicability of the measurement gap timing advance is according to clause 9.1.2 of TS 38.133 [14]. Value ms0 corresponds to 0 ms, ms0dot25 corresponds to 0.25 ms and ms0dot5 corresponds to 0.5 ms. For FR2, the network only configures 0 ms and 0.25 ms.ENUMERATED {ms0, ms0dot25, ms0dot5}, ..., [[refServCellIndicatorIndicates the serving cell whose SFN and subframe are used for gap calculation for this gap pattern. Value pCell corresponds to the PCell, pSCell corresponds to the PSCell, and mcg-FR2 corresponds to a serving cell on FR2 frequency in MCG.ENUMERATED {pCell, pSCell, mcg-FR2} OPTIONAL -- Cond NEDCorNRDC ]], [[refFR2ServCellAsyncCA-r16Indicates the FR2 serving cell identifier whose SFN and subframe is used for FR2 gap calculation for this gap pattern with asynchronous CA involving FR2 carrier(s).ServCellIndex OPTIONAL, -- Cond AsyncCAmgl-r16Value mgl is the measurement gap length in ms of the measurement gap. The measurement gap length is according to in Table 9.1.2-1 in TS 38.133 [14]. Value ms1dot5 corresponds to 1.5 ms, ms3 corresponds to 3 ms and so on. If mgl-r16 is present, UE shall ignore the mgl (without suffix).ENUMERATED {ms10, ms20} OPTIONAL -- Cond PRS ]] } -- TAG-MEASGAPCONFIG-STOP -- ASN1STOP
MeasGapConfig field descriptions |
---|
gapFR1 Indicates measurement gap configuration that applies to FR1 only. In (NG)EN-DC, gapFR1 cannot be set up by NR RRC (i.e. only LTE RRC can configure FR1 measurement gap). In NE-DC, gapFR1 can only be set up by NR RRC (i.e. LTE RRC cannot configure FR1 gap). In NR-DC, gapFR1 can only be set up in the measConfig associated with MCG. gapFR1 can not be configured together with gapUE. The applicability of the FR1 measurement gap is according to Table 9.1.2-2 and Table 9.1.2-3 in TS 38.133 [14]. |
gapFR2 Indicates measurement gap configuration applies to FR2 only. In (NG)EN-DC or NE-DC, gapFR2 can only be set up by NR RRC (i.e. LTE RRC cannot configure FR2 gap). In NR-DC, gapFR2 can only be set up in the measConfig associated with MCG. gapFR2 cannot be configured together with gapUE. The applicability of the FR2 measurement gap is according to Table 9.1.2-2 and Table 9.1.2-3 in TS 38.133 [14]. |
gapUE Indicates measurement gap configuration that applies to all frequencies (FR1 and FR2). In (NG)EN-DC, gapUE cannot be set up by NR RRC (i.e. only LTE RRC can configure per UE measurement gap). In NE-DC, gapUE can only be set up by NR RRC (i.e. LTE RRC cannot configure per UE gap). In NR-DC, gapUE can only be set up in the measConfig associated with MCG. If gapUE is configured, then neither gapFR1 nor gapFR2 can be configured. The applicability of the per UE measurement gap is according to Table 9.1.2-2 and Table 9.1.2-3 in TS 38.133 [14]. |
gapOffset Value gapOffset is the gap offset of the gap pattern with MGRP indicated in the field mgrp. The value range is from 0 to mgrp-1. |
mgl Value mgl is the measurement gap length in ms of the measurement gap. The measurement gap length is according to in Table 9.1.2-1 in TS 38.133 [14]. Value ms1dot5 corresponds to 1.5 ms, ms3 corresponds to 3 ms and so on. If mgl-r16 is present, UE shall ignore the mgl (without suffix). |
mgrp Value mgrp is measurement gap repetition period in (ms) of the measurement gap. The measurement gap repetition period is according to Table 9.1.2-1 in TS 38.133 [14]. |
mgta Value mgta is the measurement gap timing advance in ms. The applicability of the measurement gap timing advance is according to clause 9.1.2 of TS 38.133 [14]. Value ms0 corresponds to 0 ms, ms0dot25 corresponds to 0.25 ms and ms0dot5 corresponds to 0.5 ms. For FR2, the network only configures 0 ms and 0.25 ms. |
refFR2ServCellAsyncCA Indicates the FR2 serving cell identifier whose SFN and subframe is used for FR2 gap calculation for this gap pattern with asynchronous CA involving FR2 carrier(s). |
refServCellIndicator Indicates the serving cell whose SFN and subframe are used for gap calculation for this gap pattern. Value pCell corresponds to the PCell, pSCell corresponds to the PSCell, and mcg-FR2 corresponds to a serving cell on FR2 frequency in MCG. |
Conditional Presence | Explanation |
---|---|
AsyncCA | This field is mandatory present when configuring and reconfiguring FR2 gap pattern to UE in: - (NG)EN-DC or NR SA with asynchronous CA involving FR2 carrier(s); - NE-DC or NR-DC with asynchronous CA involving FR2 carrier(s), if the fieldrefServCellIndicator is set to mcg-FR2. Otherwise, it is absent, Need R. |
NEDCorNRDC | This field is mandatory present when configuring and reconfiguring gap pattern to UE in NE-DC or NR-DC. Otherwise, it is absent, Need R. |
PRS | This field is optionally present, Need R, when configuring gap pattern to UE for measurements of DL-PRS configured via LPP (TS 37.355 [49]).Otherwise, it is absent. |
The IE MeasGapSharingConfig specifies the measurement gap sharing scheme and controls setup/ release of measurement gap sharing.
-- ASN1START -- TAG-MEASGAPSHARINGCONFIG-START MeasGapSharingConfig ::= SEQUENCE {gapSharingFR2Indicates the measurement gap sharing scheme that applies to the gap set for FR2 only. In (NG)EN-DC or NE-DC, gapSharingFR2 can only be set up by NR RRC (i.e. LTE RRC cannot configure FR2 gap sharing). In NR-DC, gapSharingFR2 can only be set up by MCG in the measConfig associated with MCG. gapSharingFR2 cannot be configured together with gapSharingUE. For applicability of the different gap sharing schemes, see TS 38.133 [14]. Value scheme00 corresponds to scheme "00", value scheme01 corresponds to scheme "01", and so on.SetupRelease { MeasGapSharingScheme } OPTIONAL, -- Need M ..., [[gapSharingFR1Indicates the measurement gap sharing scheme that applies to the gap set for FR1 only. In (NG)EN-DC, gapSharingFR1 cannot be set up by NR RRC (i.e. only LTE RRC can configure FR1 gap sharing). In NE-DC, gapSharingFR1 can only be set up by NR RRC (i.e. LTE RRC cannot configure FR1 gap sharing). In NR-DC, gapSharingFR1 can only be set up in the measConfig associated with MCG. gapSharingFR1 can not be configured together with gapSharingUE. For the applicability of the different gap sharing schemes, see TS 38.133 [14]. Value scheme00 corresponds to scheme "00", value scheme01 corresponds to scheme "01", and so on.SetupRelease { MeasGapSharingScheme } OPTIONAL, --Need MgapSharingUEIndicates the measurement gap sharing scheme that applies to the gap set per UE. In (NG)EN-DC, gapSharingUE cannot be set up by NR RRC (i.e. only LTE RRC can configure per UE gap sharing). In NE-DC, gapSharingUE can only be set up by NR RRC (i.e. LTE RRC cannot configure per UE gap sharing). In NR-DC, gapSharingUE can only be set up in the measConfig associated with MCG. If gapSharingUE is configured, then neither gapSharingFR1 nor gapSharingFR2 can be configured. For the applicability of the different gap sharing schemes, see TS 38.133 [14]. Value scheme00 corresponds to scheme "00", value scheme01 corresponds to scheme "01", and so on.SetupRelease { MeasGapSharingScheme } OPTIONAL --Need M ]] } MeasGapSharingScheme::= ENUMERATED {scheme00, scheme01, scheme10, scheme11} -- TAG-MEASGAPSHARINGCONFIG-STOP -- ASN1STOP
MeasGapSharingConfig field descriptions |
---|
gapSharingFR1 Indicates the measurement gap sharing scheme that applies to the gap set for FR1 only. In (NG)EN-DC, gapSharingFR1 cannot be set up by NR RRC (i.e. only LTE RRC can configure FR1 gap sharing). In NE-DC, gapSharingFR1 can only be set up by NR RRC (i.e. LTE RRC cannot configure FR1 gap sharing). In NR-DC, gapSharingFR1 can only be set up in the measConfig associated with MCG. gapSharingFR1 can not be configured together with gapSharingUE. For the applicability of the different gap sharing schemes, see TS 38.133 [14]. Value scheme00 corresponds to scheme "00", value scheme01 corresponds to scheme "01", and so on. |
gapSharingFR2 Indicates the measurement gap sharing scheme that applies to the gap set for FR2 only. In (NG)EN-DC or NE-DC, gapSharingFR2 can only be set up by NR RRC (i.e. LTE RRC cannot configure FR2 gap sharing). In NR-DC, gapSharingFR2 can only be set up by MCG in the measConfig associated with MCG. gapSharingFR2 cannot be configured together with gapSharingUE. For applicability of the different gap sharing schemes, see TS 38.133 [14]. Value scheme00 corresponds to scheme "00", value scheme01 corresponds to scheme "01", and so on. |
gapSharingUE Indicates the measurement gap sharing scheme that applies to the gap set per UE. In (NG)EN-DC, gapSharingUE cannot be set up by NR RRC (i.e. only LTE RRC can configure per UE gap sharing). In NE-DC, gapSharingUE can only be set up by NR RRC (i.e. LTE RRC cannot configure per UE gap sharing). In NR-DC, gapSharingUE can only be set up in the measConfig associated with MCG. If gapSharingUE is configured, then neither gapSharingFR1 nor gapSharingFR2 can be configured. For the applicability of the different gap sharing schemes, see TS 38.133 [14]. Value scheme00 corresponds to scheme "00", value scheme01 corresponds to scheme "01", and so on. |
The IE MeasId is used to identify a measurement configuration, i.e., linking of a measurement object and a reporting configuration.
The IE MeasIdleConfig is used to convey information to UE about measurements requested to be done while in RRC_IDLE or RRC_INACTIVE.
-- ASN1START -- TAG-MEASIDLECONFIG-START MeasIdleConfigSIB-r16 ::= SEQUENCE {measIdleCarrierListNR-r16Indicates the NR carriers to be measured during RRC_IDLE or RRC_INACTIVE.SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF MeasIdleCarrierNR-r16 OPTIONAL, -- Need SmeasIdleCarrierListEUTRA-r16Indicates the E-UTRA carriers to be measured during RRC_IDLE or RRC_INACTIVE.SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF MeasIdleCarrierEUTRA-r16 OPTIONAL, -- Need S ... } MeasIdleConfigDedicated-r16 ::= SEQUENCE {measIdleCarrierListNR-r16Indicates the NR carriers to be measured during RRC_IDLE or RRC_INACTIVE.SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF MeasIdleCarrierNR-r16 OPTIONAL, -- Need NmeasIdleCarrierListEUTRA-r16Indicates the E-UTRA carriers to be measured during RRC_IDLE or RRC_INACTIVE.SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF MeasIdleCarrierEUTRA-r16 OPTIONAL, -- Need NmeasIdleDuration-r16Indicates the duration for performing idle/inactive measurements while in RRC_IDLE or RRC_INACTIVE. Value sec10 correspond to 10 seconds, value sec30 to 30 seconds and so on.ENUMERATED{sec10, sec30, sec60, sec120, sec180, sec240, sec300, spare},validityAreaList-r16Indicates the list of frequencies and optionally, for each frequency, a list of cells within which the UE is required to perform measurements while in RRC_IDLE and RRC_INACTIVE.ValidityAreaList-r16 OPTIONAL, -- Need N ... } ValidityAreaList-r16 ::= SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF ValidityArea-r16 ValidityArea-r16 ::= SEQUENCE {carrierFreq-r16Indicates the NR carrier frequency to be used for measurements during RRC_IDLE or RRC_INACTIVE.ARFCN-ValueNR, validityCellList-r16 ValidityCellList OPTIONAL -- Need N } ValidityCellList ::= SEQUENCE (SIZE (1.. maxCellMeasIdle-r16)) OF PCI-Range MeasIdleCarrierNR-r16 ::= SEQUENCE {carrierFreq-r16Indicates the NR carrier frequency to be used for measurements during RRC_IDLE or RRC_INACTIVE.ARFCN-ValueNR,ssbSubcarrierSpacing-r16Indicates subcarrier spacing of SSB. Only the values 15 kHz or 30 kHz (FR1), and 120 kHz or 240 kHz (FR2) are applicable.SubcarrierSpacing,frequencyBandListIndicates the list of frequency bands for which the NR idle/inactive measurement parameters apply. The UE shall select the first listed band which it supports in the frequencyBandList field to represent the NR neighbour carrier frequency.MultiFrequencyBandListNR OPTIONAL, -- Need RmeasCellListNR-r16Indicates the list of NR cells which the UE is requested to measure and report for idle/inactive measurements.CellListNR-r16 OPTIONAL, -- Need RreportQuantities-r16Indicates which measurement quantities UE is requested to report in the idle/inactive measurement report.ENUMERATED {rsrp, rsrq, both},qualityThreshold-r16Indicates the quality thresholds for reporting the measured cells for idle/inactive NR measurements.SEQUENCE { idleRSRP-Threshold-NR-r16 RSRP-Range OPTIONAL, -- Need R idleRSRQ-Threshold-NR-r16 RSRQ-Range OPTIONAL -- Need R } OPTIONAL, -- Need R ssb-MeasConfig-r16 SEQUENCE {nrofSS-BlocksToAverage-r16Number of SS blocks to average for cell measurement derivation.INTEGER (2..maxNrofSS-BlocksToAverage) OPTIONAL, -- Need SabsThreshSS-BlocksConsolidation-r16Threshold for consolidation of L1 measurements per RS index.ThresholdNR OPTIONAL, -- Need Ssmtc-r16Indicates the measurement timing configuration for inter-frequency measurement. If this field is absent in VarMeasIdleConfig, the UE assumes that SSB periodicity is 5 ms in this frequency.SSB-MTC OPTIONAL, -- Need Sssb-ToMeasure-r16The set of SS blocks to be measured within the SMTC measurement duration (see TS 38.215 [9]). When the field is absent in VarMeasIdleConfig, the UE measures on all SS-blocks.SSB-ToMeasure OPTIONAL, -- Need SderiveSSB-IndexFromCell-r16This field indicates whether the UE may use the timing of any detected cell on that frequency to derive the SSB index of all neighbour cells on that frequency. If this field is set to true, the UE assumes SFN and frame boundary alignment across cells on the neighbor frequency as specified in TS 38.133 [14].BOOLEAN,ss-RSSI-Measurement-r16Indicates the SSB-based RSSI measurement configuration. If the field is absent in VarMeasIdleConfig, the UE behaviour is defined in TS 38.215 [89], clause 5.1.3.SS-RSSI-Measurement OPTIONAL -- Need S } OPTIONAL, -- Need SbeamMeasConfigIdle-r16Indicates the beam level measurement configuration.BeamMeasConfigIdle-NR-r16 OPTIONAL, -- Need R ... } MeasIdleCarrierEUTRA-r16 ::= SEQUENCE {carrierFreqEUTRA-r16Indicates the E-UTRA carrier frequency to be used for measurements during RRC_IDLE or RRC_INACTIVE.ARFCN-ValueEUTRA, allowedMeasBandwidth-r16 EUTRA-AllowedMeasBandwidth,measCellListEUTRA-r16Indicates the list of E-UTRA cells which the UE is requested to measure and report for idle/inactive measurements.CellListEUTRA-r16 OPTIONAL, -- Need RreportQuantitiesEUTRA-r16Indicates which E-UTRA measurement quantities the UE is requested to report in the idle/inactive measurement report.ENUMERATED {rsrp, rsrq, both},qualityThresholdEUTRA-r16Indicates the quality thresholds for reporting the measured cells for idle/inactive E-UTRA measurements.SEQUENCE { idleRSRP-Threshold-EUTRA-r16 RSRP-RangeEUTRA OPTIONAL, -- Need R idleRSRQ-Threshold-EUTRA-r16 RSRQ-RangeEUTRA-r16 OPTIONAL -- Need R } OPTIONAL, -- Need S ... } CellListNR-r16 ::= SEQUENCE (SIZE (1..maxCellMeasIdle-r16)) OF PCI-Range CellListEUTRA-r16 ::= SEQUENCE (SIZE (1..maxCellMeasIdle-r16)) OF EUTRA-PhysCellIdRange BeamMeasConfigIdle-NR-r16 ::= SEQUENCE {reportQuantityRS-Indexes-r16Indicates which measurement information per beam index the UE shall include in the NR idle/inactive measurement results.ENUMERATED {rsrp, rsrq, both},maxNrofRS-IndexesToReport-r16Max number of beam indices to include in the idle/inactive measurement result.INTEGER (1.. maxNrofIndexesToReport),includeBeamMeasurements-r16Indicates whether or not the UE shall include beam measurements in the NR idle/inactive measurement results.BOOLEAN } RSRQ-RangeEUTRA-r16 ::= INTEGER (-30..46) -- TAG-MEASIDLECONFIG-STOP -- ASN1STOP
MeasIdleConfig field descriptions |
---|
absThreshSS-BlocksConsolidation Threshold for consolidation of L1 measurements per RS index. |
beamMeasConfigIdle Indicates the beam level measurement configuration. |
carrierFreq Indicates the NR carrier frequency to be used for measurements during RRC_IDLE or RRC_INACTIVE. |
carrierFreqEUTRA Indicates the E-UTRA carrier frequency to be used for measurements during RRC_IDLE or RRC_INACTIVE. |
deriveSSB-IndexFromCell This field indicates whether the UE may use the timing of any detected cell on that frequency to derive the SSB index of all neighbour cells on that frequency. If this field is set to true, the UE assumes SFN and frame boundary alignment across cells on the neighbor frequency as specified in TS 38.133 [14]. |
frequencyBandList Indicates the list of frequency bands for which the NR idle/inactive measurement parameters apply. The UE shall select the first listed band which it supports in the frequencyBandList field to represent the NR neighbour carrier frequency. |
includeBeamMeasurements Indicates whether or not the UE shall include beam measurements in the NR idle/inactive measurement results. |
maxNrofRS-IndexesToReport Max number of beam indices to include in the idle/inactive measurement result. |
measCellListEUTRA Indicates the list of E-UTRA cells which the UE is requested to measure and report for idle/inactive measurements. |
measCellListNR Indicates the list of NR cells which the UE is requested to measure and report for idle/inactive measurements. |
measIdleCarrierListEUTRA Indicates the E-UTRA carriers to be measured during RRC_IDLE or RRC_INACTIVE. |
measIdleCarrierListNR Indicates the NR carriers to be measured during RRC_IDLE or RRC_INACTIVE. |
measIdleDuration Indicates the duration for performing idle/inactive measurements while in RRC_IDLE or RRC_INACTIVE. Value sec10 correspond to 10 seconds, value sec30 to 30 seconds and so on. |
nrofSS-BlocksToAverage Number of SS blocks to average for cell measurement derivation. |
qualityThreshold Indicates the quality thresholds for reporting the measured cells for idle/inactive NR measurements. |
qualityThresholdEUTRA Indicates the quality thresholds for reporting the measured cells for idle/inactive E-UTRA measurements. |
reportQuantities Indicates which measurement quantities UE is requested to report in the idle/inactive measurement report. |
reportQuantitiesEUTRA Indicates which E-UTRA measurement quantities the UE is requested to report in the idle/inactive measurement report. |
reportQuantityRS-Indexes Indicates which measurement information per beam index the UE shall include in the NR idle/inactive measurement results. |
smtc Indicates the measurement timing configuration for inter-frequency measurement. If this field is absent in VarMeasIdleConfig, the UE assumes that SSB periodicity is 5 ms in this frequency. |
ssbSubcarrierSpacing Indicates subcarrier spacing of SSB. Only the values 15 kHz or 30 kHz (FR1), and 120 kHz or 240 kHz (FR2) are applicable. |
ssb-ToMeasure The set of SS blocks to be measured within the SMTC measurement duration (see TS 38.215 [9]). When the field is absent in VarMeasIdleConfig, the UE measures on all SS-blocks. |
ss-RSSI-Measurement Indicates the SSB-based RSSI measurement configuration. If the field is absent in VarMeasIdleConfig, the UE behaviour is defined in TS 38.215 [89], clause 5.1.3. |
validityAreaList Indicates the list of frequencies and optionally, for each frequency, a list of cells within which the UE is required to perform measurements while in RRC_IDLE and RRC_INACTIVE. |
The IE MeasIdToAddModList concerns a list of measurement identities to add or modify, with for each entry the measId, the associated measObjectId and the associated reportConfigId.
-- ASN1START -- TAG-MEASIDTOADDMODLIST-START MeasIdToAddModList ::= SEQUENCE (SIZE (1..maxNrofMeasId)) OF MeasIdToAddMod MeasIdToAddMod ::= SEQUENCE { measId MeasId, measObjectId MeasObjectId, reportConfigId ReportConfigId } -- TAG-MEASIDTOADDMODLIST-STOP -- ASN1STOP
The IE MeasObjectCLI specifies information applicable for SRS-RSRP measurements and/or CLI-RSSI measurements.
-- ASN1START -- TAG-MEASOBJECTCLI-START MeasObjectCLI-r16 ::= SEQUENCE {cli-ResourceConfig-r16SRS and/or CLI-RSSI resource configuration for CLI measurement.CLI-ResourceConfig-r16, ... } CLI-ResourceConfig-r16 ::= SEQUENCE {srs-ResourceConfig-r16SRS resources to be used for CLI measurements.SetupRelease { SRS-ResourceListConfigCLI-r16 } OPTIONAL, -- Need Mrssi-ResourceConfig-r16CLI-RSSI resources to be used for CLI measurements.SetupRelease { RSSI-ResourceListConfigCLI-r16 } OPTIONAL -- Need M } SRS-ResourceListConfigCLI-r16 ::= SEQUENCE (SIZE (1.. maxNrofCLI-SRS-Resources-r16)) OF SRS-ResourceConfigCLI-r16 RSSI-ResourceListConfigCLI-r16 ::= SEQUENCE (SIZE (1.. maxNrofCLI-RSSI-Resources-r16)) OF RSSI-ResourceConfigCLI-r16 SRS-ResourceConfigCLI-r16 ::= SEQUENCE { srs-Resource-r16 SRS-Resource,srs-SCS-r16Subcarrier spacing for SRS. Only the values 15, 30 kHz or 60 kHz (FR1), and 60 or 120 kHz (FR2) are applicable.SubcarrierSpacing,refServCellIndex-r16The index of the reference serving cell. Frequency reference point of the RSSI resource is subcarrier 0 of CRB0 of the reference serving cell. If this field is absent, the reference serving cell is PCell.ServCellIndex OPTIONAL, -- Need SrefBWP-r16DL BWP id that is used to derive the reference point of the SRS resource (see TS 38.211[16], clause 6.4.1.4.3)BWP-Id, ... } RSSI-ResourceConfigCLI-r16 ::= SEQUENCE { rssi-ResourceId-r16 RSSI-ResourceId-r16,rssi-SCS-r16Reference subcarrier spacing for CLI-RSSI measurement. Only the values 15, 30 kHz or 60 kHz (FR1), and 60 or 120 kHz (FR2) are applicable. UE performs CLI-RSSI measurement with the SCS of the active bandwidth part within the configured CLI-RSSI resource in the active BWP regardless of the reference SCS of the measurement resource.SubcarrierSpacing,startPRB-r16Starting PRB index of the measurement bandwidth. For the case where the reference subcarrier spacing is smaller than subcarrier spacing of active DL BWP(s), network configures startPRB and nrofPRBs are as a multiple of active BW SCS divided by reference SCS.INTEGER (0..2169),nrofPRBs-r16Allowed size of the measurement BW. Only multiples of 4 are allowed. The smallest configurable number is the minimum of 4 and the width of the active DL BWP. If the configured value is larger than the width of the active DL BWP, the UE shall assume that the actual CLI-RSSI resource bandwidth is within the active DL BWP.INTEGER (4..maxNrofPhysicalResourceBlocksPlus1),startPosition-r16OFDM symbol location of the CLI-RSSI resource within a slot.INTEGER (0..13),nrofSymbols-r16Within a slot that is configured for CLI-RSSI measurement (see slotConfiguration), the UE measures the RSSI from startPosition to startPosition + nrofSymbols - 1. The configured CLI-RSSI resource does not exceed the slot boundary of the reference SCS. If the SCS of configured DL BWP(s) is larger than the reference SCS, network configures startPosition and nrofSymbols such that the configured CLI-RSSI resource not to exceed the slot boundary corresponding to the configured BWP SCS. If the reference SCS is larger than SCS of configured DL BWP(s), network ensures startPosition and nrofSymbols are integer multiple of reference SCS divided by configured BWP SCS.INTEGER (1..14),rssi-PeriodicityAndOffset-r16Periodicity and slot offset for this CLI-RSSI resource.All values are in "number of slots". Value sl1 corresponds to a periodicity of 1 slot, value sl2 corresponds to a periodicity of 2 slots, and so on. For each periodicity the corresponding offset is given in number of slots.RSSI-PeriodicityAndOffset-r16,refServCellIndex-r16The index of the reference serving cell. Frequency reference point of the RSSI resource is subcarrier 0 of CRB0 of the reference serving cell. If this field is absent, the reference serving cell is PCell.ServCellIndex OPTIONAL, -- Need S ... } RSSI-ResourceId-r16 ::= INTEGER (0.. maxNrofCLI-RSSI-Resources-1-r16) RSSI-PeriodicityAndOffset-r16 ::= CHOICE { sl10 INTEGER(0..9), sl20 INTEGER(0..19), sl40 INTEGER(0..39), sl80 INTEGER(0..79), sl160 INTEGER(0..159), sl320 INTEGER(0..319), s1640 INTEGER(0..639), ... } -- TAG-MEASOBJECTCLI-STOP -- ASN1STOP
CLI-ResourceConfig field descriptions |
---|
srs-ResourceConfig SRS resources to be used for CLI measurements. |
rssi-ResourceConfig CLI-RSSI resources to be used for CLI measurements. |
MeasObjectCLI field descriptions |
---|
cli-ResourceConfig SRS and/or CLI-RSSI resource configuration for CLI measurement. |
SRS-ResourceConfigCLI field descriptions |
---|
refBWP DL BWP id that is used to derive the reference point of the SRS resource (see TS 38.211[16], clause 6.4.1.4.3) |
refServCellIndex The index of the reference serving cell that the refBWP belongs to. If this field is absent, the reference serving cell is PCell. |
srs-SCS Subcarrier spacing for SRS. Only the values 15, 30 kHz or 60 kHz (FR1), and 60 or 120 kHz (FR2) are applicable. |
RSSI-ResourceConfigCLI field descriptions |
---|
nrofPRBs Allowed size of the measurement BW. Only multiples of 4 are allowed. The smallest configurable number is the minimum of 4 and the width of the active DL BWP. If the configured value is larger than the width of the active DL BWP, the UE shall assume that the actual CLI-RSSI resource bandwidth is within the active DL BWP. |
nrofSymbols Within a slot that is configured for CLI-RSSI measurement (see slotConfiguration), the UE measures the RSSI from startPosition to startPosition + nrofSymbols - 1. The configured CLI-RSSI resource does not exceed the slot boundary of the reference SCS. If the SCS of configured DL BWP(s) is larger than the reference SCS, network configures startPosition and nrofSymbols such that the configured CLI-RSSI resource not to exceed the slot boundary corresponding to the configured BWP SCS. If the reference SCS is larger than SCS of configured DL BWP(s), network ensures startPosition and nrofSymbols are integer multiple of reference SCS divided by configured BWP SCS. |
refServCellIndex The index of the reference serving cell. Frequency reference point of the RSSI resource is subcarrier 0 of CRB0 of the reference serving cell. If this field is absent, the reference serving cell is PCell. |
rssi-PeriodicityAndOffset Periodicity and slot offset for this CLI-RSSI resource.All values are in "number of slots". Value sl1 corresponds to a periodicity of 1 slot, value sl2 corresponds to a periodicity of 2 slots, and so on. For each periodicity the corresponding offset is given in number of slots. |
rssi-SCS Reference subcarrier spacing for CLI-RSSI measurement. Only the values 15, 30 kHz or 60 kHz (FR1), and 60 or 120 kHz (FR2) are applicable. UE performs CLI-RSSI measurement with the SCS of the active bandwidth part within the configured CLI-RSSI resource in the active BWP regardless of the reference SCS of the measurement resource. |
startPosition OFDM symbol location of the CLI-RSSI resource within a slot. |
startPRB Starting PRB index of the measurement bandwidth. For the case where the reference subcarrier spacing is smaller than subcarrier spacing of active DL BWP(s), network configures startPRB and nrofPRBs are as a multiple of active BW SCS divided by reference SCS. |
The IE MeasObjectEUTRA specifies information applicable for EUTRA cells.
-- ASN1START -- TAG-MEASOBJECTEUTRA-START MeasObjectEUTRA::= SEQUENCE {carrierFreqIdentifies EUTRA carrier frequency for which this configuration is valid. Network does not configure more than one MeasObjectEUTRA for the same physical frequency, regardless of the E-ARFCN used to indicate this.ARFCN-ValueEUTRA,allowedMeasBandwidthThe maximum allowed measurement bandwidth on a carrier frequency as defined by the parameter Transmission Bandwidth Configuration "NRB" TS 36.104 [33].EUTRA-AllowedMeasBandwidth,cellsToRemoveListEUTRANList of cells to remove from the cell list.EUTRA-CellIndexList OPTIONAL, -- Need NcellsToAddModListEUTRANList of cells to add/ modify in the cell list.SEQUENCE (SIZE (1..maxCellMeasEUTRA)) OF EUTRA-Cell OPTIONAL, -- Need NblackCellsToRemoveListEUTRANList of cells to remove from the black list of cells.EUTRA-CellIndexList OPTIONAL, -- Need NblackCellsToAddModListEUTRANList of cells to add/ modify in the black list of cells.SEQUENCE (SIZE (1..maxCellMeasEUTRA)) OF EUTRA-BlackCell OPTIONAL, -- Need Neutra-PresenceAntennaPort1When set to true, the UE may assume that at least two cell-specific antenna ports are used in all neighbouring cells.EUTRA-PresenceAntennaPort1,eutra-Q-OffsetRangeUsed to indicate a cell, or frequency specific offset to be applied when evaluating triggering conditions for measurement reporting. The value is in dB. Value dB-24 corresponds to -24 dB, value dB-22 corresponds to -22 dB and so on.EUTRA-Q-OffsetRange OPTIONAL, -- Need RwidebandRSRQ-MeasIf set to true, the UE shall, when performing RSRQ measurements, use a wider bandwidth in accordance with TS 36.133 [40]. The network may set the field to trueif the measurement bandwidth indicated by allowedMeasBandwidth is 50 resource blocks or larger; otherwise the network sets this field to false.BOOLEAN, ... } EUTRA-CellIndexList ::= SEQUENCE (SIZE (1..maxCellMeasEUTRA)) OF EUTRA-CellIndex EUTRA-CellIndex ::= INTEGER (1..maxCellMeasEUTRA) EUTRA-Cell ::= SEQUENCE {cellIndexEUTRAEntry index in the cell list.EUTRA-CellIndex, physCellId EUTRA-PhysCellId,cellIndividualOffsetCell individual offset applicable to a specific cell. Value dB-24 corresponds to -24 dB, dB-22 corresponds to -22 dB and so on.EUTRA-Q-OffsetRange } EUTRA-BlackCell ::= SEQUENCE {cellIndexEUTRAEntry index in the cell list.EUTRA-CellIndex, physCellIdRange EUTRA-PhysCellIdRange } -- TAG-MEASOBJECTEUTRA-STOP -- ASN1STOP
EUTRAN-BlackCell field descriptions |
---|
cellIndexEUTRA Entry index in the cell list. |
physicalCellIdRange Physical cell identity or a range of physical cell identities. |
EUTRAN-Cell field descriptions |
---|
physicalCellId Physical cell identity of a cell in the cell list. |
cellIndividualOffset Cell individual offset applicable to a specific cell. Value dB-24 corresponds to -24 dB, dB-22 corresponds to -22 dB and so on. |
MeasObjectEUTRA field descriptions |
---|
allowedMeasBandwidth The maximum allowed measurement bandwidth on a carrier frequency as defined by the parameter Transmission Bandwidth Configuration "NRB" TS 36.104 [33]. |
blackCellsToAddModListEUTRAN List of cells to add/ modify in the black list of cells. |
blackCellsToRemoveListEUTRAN List of cells to remove from the black list of cells. |
carrierFreq Identifies EUTRA carrier frequency for which this configuration is valid. Network does not configure more than one MeasObjectEUTRA for the same physical frequency, regardless of the E-ARFCN used to indicate this. |
cellsToAddModListEUTRAN List of cells to add/ modify in the cell list. |
cellsToRemoveListEUTRAN List of cells to remove from the cell list. |
eutra-PresenceAntennaPort1 When set to true, the UE may assume that at least two cell-specific antenna ports are used in all neighbouring cells. |
eutra-Q-OffsetRange Used to indicate a cell, or frequency specific offset to be applied when evaluating triggering conditions for measurement reporting. The value is in dB. Value dB-24 corresponds to -24 dB, value dB-22 corresponds to -22 dB and so on. |
widebandRSRQ-Meas If set to true, the UE shall, when performing RSRQ measurements, use a wider bandwidth in accordance with TS 36.133 [40]. The network may set the field to trueif the measurement bandwidth indicated by allowedMeasBandwidth is 50 resource blocks or larger; otherwise the network sets this field to false. |
The IE MeasObjectId used to identify a measurement object configuration.
The IE MeasObjectNR specifies information applicable for SS/PBCH block(s) intra/inter-frequency measurements and/or CSI-RS intra/inter-frequency measurements.
-- ASN1START -- TAG-MEASOBJECTNR-START MeasObjectNR ::= SEQUENCE { ssbFrequency ARFCN-ValueNR OPTIONAL, -- Cond SSBorAssociatedSSBssbSubcarrierSpacingSubcarrier spacing of SSB. Only the values 15 kHz or 30 kHz (FR1), and 120 kHz or 240 kHz (FR2) are applicable.SubcarrierSpacing OPTIONAL, -- Cond SSBorAssociatedSSBsmtc1Primary measurement timing configuration. (see clause 5.5.2.10).SSB-MTC OPTIONAL, -- Cond SSBorAssociatedSSBsmtc2Secondary measurement timing configuration for SS corresponding to this MeasObjectNR with PCI listed in pci-List. For these SS, the periodicity is indicated by periodicity in smtc2 and the timing offset is equal to the offset indicated in periodicityAndOffset modulo periodicity. periodicity in smtc2 can only be set to a value strictly shorter than the periodicity indicated by periodicityAndOffset in smtc1 (e.g. if periodicityAndOffset indicates sf10, periodicity can only be set of sf5, if periodicityAndOffset indicates sf5, smtc2 cannot be configured).SSB-MTC2 OPTIONAL, -- Cond IntraFreqConnectedrefFreqCSI-RSPoint A which is used for mapping of CSI-RS to physical resources according to TS 38.211 [16] clause 7.4.1.5.3.ARFCN-ValueNR OPTIONAL, -- Cond CSI-RSreferenceSignalConfigRS configuration for SS/PBCH block and CSI-RS.ReferenceSignalConfig,absThreshSS-BlocksConsolidationAbsolute threshold for the consolidation of measurement results per SS/PBCH block(s) from L1 filter(s). The field is used for the derivation of cell measurement results as described in 5.5.3.3 and the reporting of beam measurement information per SS/PBCH block index as described in 5.5.5.2.ThresholdNR OPTIONAL, -- Need RabsThreshCSI-RS-ConsolidationAbsolute threshold for the consolidation of measurement results per CSI-RS resource(s) from L1 filter(s). The field is used for the derivation of cell measurement results as described in 5.5.3.3 and the reporting of beam measurement information per CSI-RS resource as described in 5.5.5.2.ThresholdNR OPTIONAL, -- Need RnrofSS-BlocksToAverageIndicates the maximum number of measurement results per beam based on SS/PBCH blocks to be averaged. The same value applies for each detected cell associated with this MeasObject.INTEGER (2..maxNrofSS-BlocksToAverage) OPTIONAL, -- Need R nrofCSI-RS-ResourcesToAverage INTEGER (2..maxNrofCSI-RS-ResourcesToAverage) OPTIONAL, -- Need RquantityConfigIndexIndicates the n-th element of quantityConfigNR-List provided in MeasConfig.INTEGER (1..maxNrofQuantityConfig),offsetMOOffset values applicable to all measured cells with reference signal(s) indicated in this MeasObjectNR.Q-OffsetRangeList,cellsToRemoveListList of cells to remove from the cell list.PCI-List OPTIONAL, -- Need NcellsToAddModListList of cells to add/modify in the cell list.CellsToAddModList OPTIONAL, -- Need NblackCellsToRemoveListList of cells to remove from the black list of cells.PCI-RangeIndexList OPTIONAL, -- Need NblackCellsToAddModListList of cells to add/modify in the black list of cells. It applies only to SSB resources.SEQUENCE (SIZE (1..maxNrofPCI-Ranges)) OF PCI-RangeElement OPTIONAL, -- Need NwhiteCellsToRemoveListList of cells to remove from the white list of cells.PCI-RangeIndexList OPTIONAL, -- Need NwhiteCellsToAddModListList of cells to add/modify in the white list of cells.It applies only to SSB resources.SEQUENCE (SIZE (1..maxNrofPCI-Ranges)) OF PCI-RangeElement OPTIONAL, -- Need N ..., [[freqBandIndicatorNRThe frequency band in which the SSB and/or CSI-RS indicated in this MeasObjectNR are located and according to which the UE shall perform the RRM measurements. This field is always provided when the network configures measurements with this MeasObjectNR.FreqBandIndicatorNR OPTIONAL, -- Need RmeasCycleSCellThe parameter is used only when an SCell is configured on the frequency indicated by the measObjectNR and is in deactivated state, see TS 38.133 [14]. gNB configures the parameter whenever an SCell is configured on the frequency indicated by the measObjectNR, but the field may also be signalled when an SCell is not configured. Value sf160 corresponds to 160 sub-frames, valuesf256 corresponds to 256 sub-frames and so on.ENUMERATED {sf160, sf256, sf320, sf512, sf640, sf1024, sf1280} OPTIONAL -- Need R ]], [[smtc3list-r16Measurement timing configuration list for SS corresponding to IAB-MT. This is used for the IAB-node's discovery of other IAB-nodes and the IAB-Donor-DUs.SSB-MTC3List-r16 OPTIONAL, -- Need R rmtc-Config-r16 SetupRelease {RMTC-Config-r16} OPTIONAL, -- Need Mt312-r16The value of timer T312. Value ms0 represents 0 ms, ms50 represents 50 ms and so on.SetupRelease { T312-r16 } OPTIONAL -- Need M ]] } SSB-MTC3List-r16::= SEQUENCE (SIZE(1..4)) OF SSB-MTC3-r16 T312-r16 ::= ENUMERATED { ms0, ms50, ms100, ms200, ms300, ms400, ms500, ms1000} ReferenceSignalConfig::= SEQUENCE {ssb-ConfigMobilitySSB configuration for mobility (nominal SSBs, timing configuration).SSB-ConfigMobility OPTIONAL, -- Need Mcsi-rs-ResourceConfigMobilityCSI-RS resources to be used for CSI-RS based RRM measurements.SetupRelease { CSI-RS-ResourceConfigMobility } OPTIONAL -- Need M } SSB-ConfigMobility::= SEQUENCE {ssb-ToMeasureThe set of SS blocks to be measured within the SMTC measurement duration. The first/leftmost bit corresponds to SS/PBCH block index 0, the second bit corresponds to SS/PBCH block index 1, and so on. Value 0 in the bitmap indicates that the corresponding SS/PBCH block is not to be measured while value 1 indicates that the corresponding SS/PBCH block is to be measured (see TS 38.215 [9]). When the field is not configured the UE measures on all SS blocks. Regardless of the value of this field, SS/PBCH blocks outside of the applicable smtc are not to be measured. See TS 38.215 [9] clause 5.1.1.SetupRelease { SSB-ToMeasure } OPTIONAL, -- Need MderiveSSB-IndexFromCellIf this field is set to true, UE assumes SFN and frame boundary alignment across cells on the same frequency carrier as specified in TS 38.133 [14]. Hence, if the UE is configured with a serving cell for which (absoluteFrequencySSB, subcarrierSpacing) in ServingCellConfigCommon is equal to (ssbFrequency, ssbSubcarrierSpacing) in this MeasObjectNR, this field indicates whether the UE can utilize the timing of this serving cell to derive the index of SS block transmitted by neighbour cell. Otherwise, this field indicates whether the UE may use the timing of any detected cell on that target frequency to derive the SSB index of all neighbour cells on that frequency.BOOLEAN, ss-RSSI-Measurement SS-RSSI-Measurement OPTIONAL, -- Need M ..., [[ssb-PositionQCL-Common-r16Indicates the QCL relationship between SS/PBCH blocks for all measured cells as specified in TS 38.213 [13], clause 4.1.SSB-PositionQCL-Relation-r16 OPTIONAL, -- Cond SharedSpectrum ssb-PositionQCL-CellsToAddModList-r16 SSB-PositionQCL-CellsToAddModList-r16 OPTIONAL, -- Need N ssb-PositionQCL-CellsToRemoveList-r16 PCI-List OPTIONAL -- Need N ]] } Q-OffsetRangeList ::= SEQUENCE { rsrpOffsetSSB Q-OffsetRange DEFAULT dB0, rsrqOffsetSSB Q-OffsetRange DEFAULT dB0, sinrOffsetSSB Q-OffsetRange DEFAULT dB0, rsrpOffsetCSI-RS Q-OffsetRange DEFAULT dB0, rsrqOffsetCSI-RS Q-OffsetRange DEFAULT dB0, sinrOffsetCSI-RS Q-OffsetRange DEFAULT dB0 } ThresholdNR ::= SEQUENCE{ thresholdRSRP RSRP-Range OPTIONAL, -- Need R thresholdRSRQ RSRQ-Range OPTIONAL, -- Need R thresholdSINR SINR-Range OPTIONAL -- Need R } CellsToAddModList ::= SEQUENCE (SIZE (1..maxNrofCellMeas)) OF CellsToAddMod CellsToAddMod ::= SEQUENCE {physCellIdPhysical cell identity of a cell in the cell list.PhysCellId,cellIndividualOffsetCell individual offsets applicable to a specific cell.Q-OffsetRangeList } RMTC-Config-r16 ::= SEQUENCE {rmtc-Periodicity-r16Indicates the RSSI measurement timing configuration (RMTC) periodicity (see TS 38.215 [9], clause 5.1.21).ENUMERATED {ms40, ms80, ms160, ms320, ms640},rmtc-SubframeOffset-r16Indicates the RSSI measurement timing configuration (RMTC) subframe offset for this frequency (see TS 38.215 [9], clause 5.1.21). For inter-frequency measurements, this field is optional present and if it is not configured, the UE chooses a random value as rmtc-SubframeOffset for measDurationSymbols which shall be selected to be between 0 and the configured rmtc-Periodicity with equal probability.INTEGER(0..639) OPTIONAL, -- Need MmeasDurationSymbols-r16Number of consecutive symbols for which the Physical Layer reports samples of RSSI (see TS 38.215 [9], clause 5.1.21). Value sym1 corresponds to one symbol, sym14or12 corresponds to 14 symbolsof the reference numerology for NCP and 12 symbols for ECP, and so on.ENUMERATED {sym1, sym14or12, sym28or24, sym42or36, sym70or60},rmtc-Frequency-r16Indicates the center frequency of the measured bandwidth for a frequency which operates with shared spectrum channel access(see TS 38. 215 [9], clause 5.1.21).ARFCN-ValueNR,ref-SCS-CP-r16Indicates a reference subcarrier spacing and cyclic prefix to be used for RSSI measurements (see TS 38.215 [9]). Value kHz15 corresponds to 15kHz, kHz30 corresponds to 30 kHz, value kHz60-NCP corresponds to 60 kHz using normal cyclic prefix (NCP), and kHz60-ECP corresponds to 60 kHz using extended cyclic prefix (ECP).ENUMERATED {kHz15, kHz30, kHz60-NCP, kHz60-ECP}, ... } SSB-PositionQCL-CellsToAddModList-r16 ::= SEQUENCE (SIZE (1..maxNrofCellMeas)) OF SSB-PositionQCL-CellsToAddMod-r16 SSB-PositionQCL-CellsToAddMod-r16 ::= SEQUENCE {physCellId-r16Physical cell identity of a cell in the cell list.PhysCellId,ssb-PositionQCL-r16Indicates the QCL relation between SS/PBCH blocks for a specific cell as specified in TS 38.213 [13], clause 4.1. If provided, the cell specific value overwrites the value signalled by ssb-PositionQCL-Common.SSB-PositionQCL-Relation-r16 } -- TAG-MEASOBJECTNR-STOP -- ASN1STOP
CellsToAddMod field descriptions |
---|
cellIndividualOffset Cell individual offsets applicable to a specific cell. |
physCellId Physical cell identity of a cell in the cell list. |
MeasObjectNR field descriptions |
---|
absThreshCSI-RS-Consolidation Absolute threshold for the consolidation of measurement results per CSI-RS resource(s) from L1 filter(s). The field is used for the derivation of cell measurement results as described in 5.5.3.3 and the reporting of beam measurement information per CSI-RS resource as described in 5.5.5.2. |
absThreshSS-BlocksConsolidation Absolute threshold for the consolidation of measurement results per SS/PBCH block(s) from L1 filter(s). The field is used for the derivation of cell measurement results as described in 5.5.3.3 and the reporting of beam measurement information per SS/PBCH block index as described in 5.5.5.2. |
blackCellsToAddModList List of cells to add/modify in the black list of cells. It applies only to SSB resources. |
blackCellsToRemoveList List of cells to remove from the black list of cells. |
cellsToAddModList List of cells to add/modify in the cell list. |
cellsToRemoveList List of cells to remove from the cell list. |
freqBandIndicatorNR The frequency band in which the SSB and/or CSI-RS indicated in this MeasObjectNR are located and according to which the UE shall perform the RRM measurements. This field is always provided when the network configures measurements with this MeasObjectNR. |
measCycleSCell The parameter is used only when an SCell is configured on the frequency indicated by the measObjectNR and is in deactivated state, see TS 38.133 [14]. gNB configures the parameter whenever an SCell is configured on the frequency indicated by the measObjectNR, but the field may also be signalled when an SCell is not configured. Value sf160 corresponds to 160 sub-frames, valuesf256 corresponds to 256 sub-frames and so on. |
nrofCSInrofCSI-RS-ResourcesToAverage Indicates the maximum number of measurement results per beam based on CSI-RS resources to be averaged. The same value applies for each detected cell associated with this MeasObjectNR. |
nrofSS-BlocksToAverage Indicates the maximum number of measurement results per beam based on SS/PBCH blocks to be averaged. The same value applies for each detected cell associated with this MeasObject. |
offsetMO Offset values applicable to all measured cells with reference signal(s) indicated in this MeasObjectNR. |
quantityConfigIndex Indicates the n-th element of quantityConfigNR-List provided in MeasConfig. |
referenceSignalConfig RS configuration for SS/PBCH block and CSI-RS. |
refFreqCSI-RS Point A which is used for mapping of CSI-RS to physical resources according to TS 38.211 [16] clause 7.4.1.5.3. |
smtc1 Primary measurement timing configuration. (see clause 5.5.2.10). |
smtc2 Secondary measurement timing configuration for SS corresponding to this MeasObjectNR with PCI listed in pci-List. For these SS, the periodicity is indicated by periodicity in smtc2 and the timing offset is equal to the offset indicated in periodicityAndOffset modulo periodicity. periodicity in smtc2 can only be set to a value strictly shorter than the periodicity indicated by periodicityAndOffset in smtc1 (e.g. if periodicityAndOffset indicates sf10, periodicity can only be set of sf5, if periodicityAndOffset indicates sf5, smtc2 cannot be configured). |
smtc3list Measurement timing configuration list for SS corresponding to IAB-MT. This is used for the IAB-node's discovery of other IAB-nodes and the IAB-Donor-DUs. |
ssbFrequencyIndicates the frequency of the SS associated to this MeasObjectNR. For operation with shared spectrum channel access, this field is a k*30 kHz shift from the sync raster where k = 0,1,2, and so on if the reportType within the corresponding ReportConfigNR is set to reportCGI (see TS 38.211 [16], clause 7.4.3.1). Frequencies are considered to be on the sync raster if they are also identifiable with a GSCN value (see TS 38.101-1 [15]). |
ssb-PositionQCL-Common Indicates the QCL relationship between SS/PBCH blocks for all measured cells as specified in TS 38.213 [13], clause 4.1. |
ssbSubcarrierSpacing Subcarrier spacing of SSB. Only the values 15 kHz or 30 kHz (FR1), and 120 kHz or 240 kHz (FR2) are applicable. |
t312 The value of timer T312. Value ms0 represents 0 ms, ms50 represents 50 ms and so on. |
whiteCellsToAddModList List of cells to add/modify in the white list of cells.It applies only to SSB resources. |
whiteCellsToRemoveList List of cells to remove from the white list of cells. |
RMTC-Configfield descriptions |
---|
measDurationSymbols Number of consecutive symbols for which the Physical Layer reports samples of RSSI (see TS 38.215 [9], clause 5.1.21). Value sym1 corresponds to one symbol, sym14or12 corresponds to 14 symbolsof the reference numerology for NCP and 12 symbols for ECP, and so on. |
ref-SCS-CP Indicates a reference subcarrier spacing and cyclic prefix to be used for RSSI measurements (see TS 38.215 [9]). Value kHz15 corresponds to 15kHz, kHz30 corresponds to 30 kHz, value kHz60-NCP corresponds to 60 kHz using normal cyclic prefix (NCP), and kHz60-ECP corresponds to 60 kHz using extended cyclic prefix (ECP). |
rmtc-Frequency Indicates the center frequency of the measured bandwidth for a frequency which operates with shared spectrum channel access(see TS 38. 215 [9], clause 5.1.21). |
rmtc-Periodicity Indicates the RSSI measurement timing configuration (RMTC) periodicity (see TS 38.215 [9], clause 5.1.21). |
rmtc-SubframeOffset Indicates the RSSI measurement timing configuration (RMTC) subframe offset for this frequency (see TS 38.215 [9], clause 5.1.21). For inter-frequency measurements, this field is optional present and if it is not configured, the UE chooses a random value as rmtc-SubframeOffset for measDurationSymbols which shall be selected to be between 0 and the configured rmtc-Periodicity with equal probability. |
ReferenceSignalConfig field descriptions |
---|
csi-rs-ResourceConfigMobility CSI-RS resources to be used for CSI-RS based RRM measurements. |
ssb-ConfigMobility SSB configuration for mobility (nominal SSBs, timing configuration). |
SSB-ConfigMobility field descriptions |
---|
deriveSSB-IndexFromCell If this field is set to true, UE assumes SFN and frame boundary alignment across cells on the same frequency carrier as specified in TS 38.133 [14]. Hence, if the UE is configured with a serving cell for which (absoluteFrequencySSB, subcarrierSpacing) in ServingCellConfigCommon is equal to (ssbFrequency, ssbSubcarrierSpacing) in this MeasObjectNR, this field indicates whether the UE can utilize the timing of this serving cell to derive the index of SS block transmitted by neighbour cell. Otherwise, this field indicates whether the UE may use the timing of any detected cell on that target frequency to derive the SSB index of all neighbour cells on that frequency. |
ssb-ToMeasure The set of SS blocks to be measured within the SMTC measurement duration. The first/leftmost bit corresponds to SS/PBCH block index 0, the second bit corresponds to SS/PBCH block index 1, and so on. Value 0 in the bitmap indicates that the corresponding SS/PBCH block is not to be measured while value 1 indicates that the corresponding SS/PBCH block is to be measured (see TS 38.215 [9]). When the field is not configured the UE measures on all SS blocks. Regardless of the value of this field, SS/PBCH blocks outside of the applicable smtc are not to be measured. See TS 38.215 [9] clause 5.1.1. |
SSB-PositionQCL-CellsToAddMod field descriptions |
---|
physCellId Physical cell identity of a cell in the cell list. |
ssb-PositionQCL Indicates the QCL relation between SS/PBCH blocks for a specific cell as specified in TS 38.213 [13], clause 4.1. If provided, the cell specific value overwrites the value signalled by ssb-PositionQCL-Common. |
Conditional Presence | Explanation |
---|---|
CSI-RS | This field is mandatory present if csi-rs-ResourceConfigMobility is configured, otherwise, it is absent. |
SSBorAssociatedSSB | This field is mandatory present if ssb-ConfigMobility is configured or associatedSSB is configured in at least one cell. Otherwise, it is absent, Need R. |
IntraFreqConnected | This field is optionally present, Need R if the UE is configured with a serving cell for which (absoluteFrequencySSB, subcarrierSpacing) in ServingCellConfigCommon is equal to (ssbFrequency, ssbSubcarrierSpacing) in this MeasObjectNR, otherwise, it is absent. |
SharedSpectrum | This field is mandatory present if this MeasObject is for a frequency which operates with shared spectrum channel access. Otherwise, it is absent, Need R. |
The IE MeasObjectNR-SL concerns a measurement object including a list of transmission resource pool(s) for which CBR measurement is performed for NR sidelink communication.
-- ASN1START -- TAG-MEASOBJECTNR-SL-START MeasObjectNR-SL-r16 ::= SEQUENCE { tx-PoolMeasToRemoveList-r16 Tx-PoolMeasList-r16 OPTIONAL, -- Need N tx-PoolMeasToAddModList-r16 Tx-PoolMeasList-r16 OPTIONAL -- Need N } Tx-PoolMeasList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-PoolToMeasureNR-r16)) OF SL-ResourcePoolID-r16 -- TAG-MEASOBJECTNR-SL-STOP -- ASN1STOP
The IE MeasObjectToAddModList concerns a list of measurement objects to add or modify.
-- ASN1START -- TAG-MEASOBJECTTOADDMODLIST-START MeasObjectToAddModList ::= SEQUENCE (SIZE (1..maxNrofObjectId)) OF MeasObjectToAddMod MeasObjectToAddMod ::= SEQUENCE { measObjectId MeasObjectId, measObject CHOICE { measObjectNR MeasObjectNR, ..., measObjectEUTRA MeasObjectEUTRA, measObjectUTRA-FDD-r16 MeasObjectUTRA-FDD-r16, measObjectNR-SL-r16 MeasObjectNR-SL-r16, measObjectCLI-r16 MeasObjectCLI-r16 } } -- TAG-MEASOBJECTTOADDMODLIST-STOP -- ASN1STOP
The IE MeasObjectUTRA-FDD specifies information applicable for inter-RAT UTRA-FDD neighbouring cells.
-- ASN1START -- TAG-MEASOBJECTUTRA-FDD-START MeasObjectUTRA-FDD-r16 ::= SEQUENCE {carrierFreq-r16Identifies UTRA-FDD carrier frequency for which this configuration is valid.NR does not configure more than one measurement object for the same physical frequency regardless of the ARFCN used to indicate this.ARFCN-ValueUTRA-FDD-r16,utra-FDD-Q-OffsetRange-r16Used to indicate a frequency specific offset to be applied when evaluating triggering conditions for measurement reporting. The value is in dB.UTRA-FDD-Q-OffsetRange-r16 OPTIONAL, -- Need RcellsToRemoveList-r16List of cells to remove from the neighbouring cell list.UTRA-FDD-CellIndexList-r16 OPTIONAL, -- Need NcellsToAddModList-r16List of UTRA-FDD cells to add/modify in the neighbouring cell list.CellsToAddModListUTRA-FDD-r16 OPTIONAL, -- Need N ... } CellsToAddModListUTRA-FDD-r16 ::= SEQUENCE (SIZE (1..maxCellMeasUTRA-FDD-r16)) OF CellsToAddModUTRA-FDD-r16 CellsToAddModUTRA-FDD-r16 ::= SEQUENCE {cellIndexUTRA-FDD-r16Entry index in the neighbouring cell list.UTRA-FDD-CellIndex-r16, physCellId-r16 PhysCellIdUTRA-FDD-r16 } UTRA-FDD-CellIndexList-r16 ::= SEQUENCE (SIZE (1..maxCellMeasUTRA-FDD-r16)) OF UTRA-FDD-CellIndex-r16 UTRA-FDD-CellIndex-r16 ::= INTEGER (1..maxCellMeasUTRA-FDD-r16) -- TAG-MEASOBJECTUTRA-FDD-STOP -- ASN1STOP
MeasObjectUTRA-FDD field descriptions |
---|
carrierFreq Identifies UTRA-FDD carrier frequency for which this configuration is valid.NR does not configure more than one measurement object for the same physical frequency regardless of the ARFCN used to indicate this. |
cellIndexUTRA-FDD Entry index in the neighbouring cell list. |
cellsToAddModList List of UTRA-FDD cells to add/modify in the neighbouring cell list. |
cellsToRemoveList List of cells to remove from the neighbouring cell list. |
utra-FDD-Q-OffsetRange Used to indicate a frequency specific offset to be applied when evaluating triggering conditions for measurement reporting. The value is in dB. |
The IE MeasResultCellListSFTD-NR consists of SFN and radio frame boundary difference between the PCell and an NR cell as specified in TS 38.215 [9] and TS 38.133 [14].
-- ASN1START -- TAG-MEASRESULTCELLLISTSFTD-NR-START MeasResultCellListSFTD-NR ::= SEQUENCE (SIZE (1..maxCellSFTD)) OF MeasResultCellSFTD-NR MeasResultCellSFTD-NR ::= SEQUENCE { physCellId PhysCellId,sfn-OffsetResultIndicates the SFN difference between the PCell and the NR cell as an integer value according to TS 38.215 [9].INTEGER (0..1023),frameBoundaryOffsetResultIndicates the frame boundary difference between the PCell and the NR cell as an integer value according to TS 38.215 [9].INTEGER (-30720..30719), rsrp-Result RSRP-Range OPTIONAL } -- TAG-MEASRESULTCELLLISTSFTD-NR-STOP -- ASN1STOP
MeasResultCellSFTD-NR field descriptions |
---|
sfn-OffsetResult Indicates the SFN difference between the PCell and the NR cell as an integer value according to TS 38.215 [9]. |
frameBoundaryOffsetResult Indicates the frame boundary difference between the PCell and the NR cell as an integer value according to TS 38.215 [9]. |
The IE MeasResultCellListSFTD-EUTRA consists of SFN and radio frame boundary difference between the PCell and an E-UTRA PSCell.
-- ASN1START -- TAG-MEASRESULTCELLLISTSFTD-EUTRA-START MeasResultCellListSFTD-EUTRA ::= SEQUENCE (SIZE (1..maxCellSFTD)) OF MeasResultSFTD-EUTRA MeasResultSFTD-EUTRA ::= SEQUENCE {eutra-PhysCellIdIdentifies the physical cell identity of the E-UTRA cell for which the reporting is being performed.EUTRA-PhysCellId,sfn-OffsetResultIndicates the SFN difference between the PCell and the E-UTRA cell as an integer value according to TS 38.215 [9].INTEGER (0..1023),frameBoundaryOffsetResultIndicates the frame boundary difference between the PCell and the E-UTRA cell as an integer value according to TS 38.215 [9].INTEGER (-30720..30719), rsrp-Result RSRP-Range OPTIONAL } -- TAG-MEASRESULTCELLLISTSFTD-EUTRA-STOP -- ASN1STOP
MeasResultSFTD-EUTRA field descriptions |
---|
eutra-PhysCellId Identifies the physical cell identity of the E-UTRA cell for which the reporting is being performed. |
sfn-OffsetResult Indicates the SFN difference between the PCell and the E-UTRA cell as an integer value according to TS 38.215 [9]. |
frameBoundaryOffsetResult Indicates the frame boundary difference between the PCell and the E-UTRA cell as an integer value according to TS 38.215 [9]. |
The IE MeasResults covers measured results for intra-frequency, inter-frequency, inter-RAT mobility and measured results for NR sidelink communication.
-- ASN1START -- TAG-MEASRESULTS-START MeasResults ::= SEQUENCE {measIdIdentifies the measurement identity for which the reporting is being performed.MeasId,measResultServingMOListMeasured results of measured cells with reference signals indicated in the serving cell measurement objects including measurement results of SpCell, configured SCell(s) and best neighbouring cell within measured cells with reference signals indicated in on each serving cell measurement object. If the sending of the MeasurementReport message is triggered by a measurement configured by the field sl-ConfigDedicatedForNR received within an E-UTRA RRCConnectionReconfiguration message (i.e. CBR measurements), this field is not applicable and its contents is ignored by the network.MeasResultServMOList, measResultNeighCells CHOICE {measResultListNRList of measured results for the maximum number of reported best cells for an NR measurement identity.MeasResultListNR, ...,measResultListEUTRAList of measured results for the maximum number of reported best cells for an E-UTRA measurement identity.MeasResultListEUTRA,measResultListUTRA-FDD-r16List of measured results for the maximum number of reported best cells for a UTRA-FDD measurement identity.MeasResultListUTRA-FDD-r16 } OPTIONAL, ..., [[measResultServFreqListEUTRA-SCGMeasured results of the E-UTRA SCG serving frequencies: the measurement result of PSCell and each SCell, if any, and of the best neighbouring cell on each E-UTRA SCG serving frequency.MeasResultServFreqListEUTRA-SCG OPTIONAL,measResultServFreqListNR-SCGMeasured results of the NR SCG serving frequencies: the measurement result of PSCell and each SCell, if any, and of the best neighbouring cell on each NR SCG serving frequency.MeasResultServFreqListNR-SCG OPTIONAL,measResultSFTD-EUTRASFTD measurement results between the PCell and the E-UTRA PScell in NE-DC.MeasResultSFTD-EUTRA OPTIONAL,measResultSFTD-NRSFTD measurement results between the PCell and the NR PScell in NR-DC.MeasResultCellSFTD-NR OPTIONAL ]], [[measResultCellListSFTD-NRSFTD measurement results between the PCell and the NR neighbour cell(s) in NR standalone.MeasResultCellListSFTD-NR OPTIONAL ]], [[measResultForRSSI-r16Includes measured RSSI result in dBm (see TS 38.215 [9]) and channelOccupancy which is the percentage of samples when the RSSI was above the configured channelOccupancyThreshold for the associated reportConfig.MeasResultForRSSI-r16 OPTIONAL,locationInfo-r16Positioning related information and measurements.LocationInfo-r16 OPTIONAL, ul-PDCP-DelayValueResultList-r16 UL-PDCP-DelayValueResultList-r16 OPTIONAL,measResultsSL-r16CBR measurements results for NR sidelink communication.MeasResultsSL-r16 OPTIONAL,measResultCLI-r16CLI measurement results.MeasResultCLI-r16 OPTIONAL ]] } MeasResultServMOList ::= SEQUENCE (SIZE (1..maxNrofServingCells)) OF MeasResultServMO MeasResultServMO ::= SEQUENCE { servCellId ServCellIndex, measResultServingCell MeasResultNR, measResultBestNeighCell MeasResultNR OPTIONAL, ... } MeasResultListNR ::= SEQUENCE (SIZE (1..maxCellReport)) OF MeasResultNR MeasResultNR ::= SEQUENCE {physCellIdThe physical cell identity of the UTRA-FDD cell for which the reporting is being performed.PhysCellId OPTIONAL, measResult SEQUENCE {cellResultsCell level measurement results.SEQUENCE{resultsSSB-CellCell level measurement results based on SS/PBCH related measurements.MeasQuantityResults OPTIONAL,resultsCSI-RS-CellCell level measurement results based on CSI-RS related measurements.MeasQuantityResults OPTIONAL },rsIndexResultsBeam level measurement results.SEQUENCE{resultsSSB-IndexesBeam level measurement results based on SS/PBCH related measurements.ResultsPerSSB-IndexList OPTIONAL,resultsCSI-RS-IndexesBeam level measurement results based on CSI-RS related measurements.ResultsPerCSI-RS-IndexList OPTIONAL } OPTIONAL }, ..., [[ cgi-Info CGI-InfoNR OPTIONAL ]] } MeasResultListEUTRA ::= SEQUENCE (SIZE (1..maxCellReport)) OF MeasResultEUTRA MeasResultEUTRA ::= SEQUENCE {eutra-PhysCellIdIdentifies the physical cell identity of the E-UTRA cell for which the reporting is being performed. The UE reports a value in the range 0..503, other values are reserved.PhysCellId, measResult MeasQuantityResultsEUTRA, cgi-Info CGI-InfoEUTRA OPTIONAL, ... } MultiBandInfoListEUTRA ::= SEQUENCE (SIZE (1..maxMultiBands)) OF FreqBandIndicatorEUTRA MeasQuantityResults ::= SEQUENCE { rsrp RSRP-Range OPTIONAL, rsrq RSRQ-Range OPTIONAL, sinr SINR-Range OPTIONAL } MeasQuantityResultsEUTRA ::= SEQUENCE { rsrp RSRP-RangeEUTRA OPTIONAL, rsrq RSRQ-RangeEUTRA OPTIONAL, sinr SINR-RangeEUTRA OPTIONAL } ResultsPerSSB-IndexList::= SEQUENCE (SIZE (1..maxNrofIndexesToReport2)) OF ResultsPerSSB-Index ResultsPerSSB-Index ::= SEQUENCE { ssb-Index SSB-Index, ssb-Results MeasQuantityResults OPTIONAL } ResultsPerCSI-RS-IndexList::= SEQUENCE (SIZE (1..maxNrofIndexesToReport2)) OF ResultsPerCSI-RS-Index ResultsPerCSI-RS-Index ::= SEQUENCE { csi-RS-Index CSI-RS-Index, csi-RS-Results MeasQuantityResults OPTIONAL } MeasResultServFreqListEUTRA-SCG ::= SEQUENCE (SIZE (1..maxNrofServingCellsEUTRA)) OF MeasResult2EUTRA MeasResultServFreqListNR-SCG ::= SEQUENCE (SIZE (1..maxNrofServingCells)) OF MeasResult2NR MeasResultListUTRA-FDD-r16 ::= SEQUENCE (SIZE (1..maxCellReport)) OF MeasResultUTRA-FDD-r16 MeasResultUTRA-FDD-r16 ::= SEQUENCE {physCellId-r16The physical cell identity of the UTRA-FDD cell for which the reporting is being performed.PhysCellIdUTRA-FDD-r16, measResult-r16 SEQUENCE {utra-FDD-RSCP-r16According to CPICH_RSCP in TS 25.133 [46]for FDD.INTEGER (-5..91) OPTIONAL,utra-FDD-EcN0-r16According to CPICH_Ec/No in TS 25.133 [46]for FDD.INTEGER (0..49) OPTIONAL } } MeasResultForRSSI-r16 ::= SEQUENCE { rssi-Result-r16 RSSI-Range-r16, channelOccupancy-r16 INTEGER (0..100) } MeasResultCLI-r16 ::= SEQUENCE { measResultListSRS-RSRP-r16 MeasResultListSRS-RSRP-r16 OPTIONAL, measResultListCLI-RSSI-r16 MeasResultListCLI-RSSI-r16 OPTIONAL } MeasResultListSRS-RSRP-r16 ::= SEQUENCE (SIZE (1.. maxCLI-Report-r16)) OF MeasResultSRS-RSRP-r16 MeasResultSRS-RSRP-r16 ::= SEQUENCE { srs-ResourceId-r16 SRS-ResourceId, srs-RSRP-Result-r16 SRS-RSRP-Range-r16 } MeasResultListCLI-RSSI-r16 ::= SEQUENCE (SIZE (1.. maxCLI-Report-r16)) OF MeasResultCLI-RSSI-r16 MeasResultCLI-RSSI-r16 ::= SEQUENCE { rssi-ResourceId-r16 RSSI-ResourceId-r16, cli-RSSI-Result-r16 CLI-RSSI-Range-r16 } UL-PDCP-DelayValueResultList-r16 ::= SEQUENCE (SIZE (1..maxDRB)) OF UL-PDCP-DelayValueResult-r16 UL-PDCP-DelayValueResult-r16 ::= SEQUENCE {drb-Id-r16Indicates DRB value for which uplink PDCP delay ratio or value is provided, according to TS 38.314 [53].DRB-Identity,averageDelay-r16Indicates average delay for the packets during the reporting period, as specified in TS 38.314 [53]. Value 0 corresponds to 0 millisecond, value 1 corresponds to 0.1 millisecond, value 2 corresponds to 0.2 millisecond, and so on.INTEGER (0..10000), ... } -- TAG-MEASRESULTS-STOP -- ASN1STOP
MeasResultEUTRA field descriptions |
---|
eutra-PhysCellId Identifies the physical cell identity of the E-UTRA cell for which the reporting is being performed. The UE reports a value in the range 0..503, other values are reserved. |
MeasResultNR field descriptions |
---|
averageDelay Indicates average delay for the packets during the reporting period, as specified in TS 38.314 [53]. Value 0 corresponds to 0 millisecond, value 1 corresponds to 0.1 millisecond, value 2 corresponds to 0.2 millisecond, and so on. |
cellResults Cell level measurement results. |
drb-Id Indicates DRB value for which uplink PDCP delay ratio or value is provided, according to TS 38.314 [53]. |
locationInfo Positioning related information and measurements. |
physCellId The physical cell identity of the NR cell for which the reporting is being performed. |
resultsSSB-Cell Cell level measurement results based on SS/PBCH related measurements. |
resultsSSB-Indexes Beam level measurement results based on SS/PBCH related measurements. |
resultsCSI-RS-Cell Cell level measurement results based on CSI-RS related measurements. |
resultsCSI-RS-Indexes Beam level measurement results based on CSI-RS related measurements. |
rsIndexResults Beam level measurement results. |
MeasResultUTRA-FDD field descriptions |
---|
physCellId The physical cell identity of the UTRA-FDD cell for which the reporting is being performed. |
utra-FDD-EcN0 According to CPICH_Ec/No in TS 25.133 [46]for FDD. |
utra-FDD-RSCP According to CPICH_RSCP in TS 25.133 [46]for FDD. |
MeasResults field descriptions |
---|
measId Identifies the measurement identity for which the reporting is being performed. |
measQuantityResults The value sinr is not included when it is used for LogMeasReport-r16. |
measResultCellListSFTD-NR SFTD measurement results between the PCell and the NR neighbour cell(s) in NR standalone. |
measResultCLI CLI measurement results. |
measResultEUTRA Measured results of an E-UTRA cell. |
measResultForRSSI Includes measured RSSI result in dBm (see TS 38.215 [9]) and channelOccupancy which is the percentage of samples when the RSSI was above the configured channelOccupancyThreshold for the associated reportConfig. |
measResultListEUTRA List of measured results for the maximum number of reported best cells for an E-UTRA measurement identity. |
measResultListNR List of measured results for the maximum number of reported best cells for an NR measurement identity. |
measResultListUTRA-FDD List of measured results for the maximum number of reported best cells for a UTRA-FDD measurement identity. |
measResultNR Measured results of an NR cell. |
measResultServFreqListEUTRA-SCG Measured results of the E-UTRA SCG serving frequencies: the measurement result of PSCell and each SCell, if any, and of the best neighbouring cell on each E-UTRA SCG serving frequency. |
measResultServFreqListNR-SCG Measured results of the NR SCG serving frequencies: the measurement result of PSCell and each SCell, if any, and of the best neighbouring cell on each NR SCG serving frequency. |
measResultServingMOList Measured results of measured cells with reference signals indicated in the serving cell measurement objects including measurement results of SpCell, configured SCell(s) and best neighbouring cell within measured cells with reference signals indicated in on each serving cell measurement object. If the sending of the MeasurementReport message is triggered by a measurement configured by the field sl-ConfigDedicatedForNR received within an E-UTRA RRCConnectionReconfiguration message (i.e. CBR measurements), this field is not applicable and its contents is ignored by the network. |
measResultSFTD-EUTRA SFTD measurement results between the PCell and the E-UTRA PScell in NE-DC. |
measResultSFTD-NR SFTD measurement results between the PCell and the NR PScell in NR-DC. |
measResultsSL CBR measurements results for NR sidelink communication. |
measResultUTRA-FDD Measured result of a UTRA-FDD cell. |
The IE MeasResult2EUTRA contains measurements on E-UTRA frequencies.
-- ASN1START -- TAG-MEASRESULT2EUTRA-START MeasResult2EUTRA ::= SEQUENCE { carrierFreq ARFCN-ValueEUTRA, measResultServingCell MeasResultEUTRA OPTIONAL, measResultBestNeighCell MeasResultEUTRA OPTIONAL, ... } -- TAG-MEASRESULT2EUTRA-STOP -- ASN1STOP
The IE MeasResult2NR contains measurements on NR frequencies.
-- ASN1START -- TAG-MEASRESULT2NR-START MeasResult2NR ::= SEQUENCE { ssbFrequency ARFCN-ValueNR OPTIONAL, refFreqCSI-RS ARFCN-ValueNR OPTIONAL, measResultServingCell MeasResultNR OPTIONAL, measResultNeighCellListNR MeasResultListNR OPTIONAL, ... } -- TAG-MEASRESULT2NR-STOP -- ASN1STOP
The IE MeasResultIdleEUTRA covers the E-UTRA measurement results performed in RRC_IDLE and RRC_INACTIVE.
-- ASN1START -- TAG-MEASRESULTIDLEEUTRA-START MeasResultIdleEUTRA-r16 ::= SEQUENCE { measResultsPerCarrierListIdleEUTRA-r16 SEQUENCE (SIZE (1.. maxFreqIdle-r16)) OF MeasResultsPerCarrierIdleEUTRA-r16, ... } MeasResultsPerCarrierIdleEUTRA-r16 ::= SEQUENCE { carrierFreqEUTRA-r16 ARFCN-ValueEUTRA, measResultsPerCellListIdleEUTRA-r16 SEQUENCE (SIZE (1..maxCellMeasIdle-r16)) OF MeasResultsPerCellIdleEUTRA-r16, ... } MeasResultsPerCellIdleEUTRA-r16 ::= SEQUENCE { eutra-PhysCellId-r16 EUTRA-PhysCellId, measIdleResultEUTRA-r16 SEQUENCE { rsrp-ResultEUTRA-r16 RSRP-RangeEUTRA OPTIONAL, rsrq-ResultEUTRA-r16 RSRQ-RangeEUTRA-r16 OPTIONAL }, ... } -- TAG-MEASRESULTIDLEEUTRA-STOP -- ASN1STOP
The IE MeasResultIdleNR covers the NR measurement results performed in RRC_IDLE and RRC_INACTIVE.
-- ASN1START -- TAG-MEASRESULTIDLENR-START MeasResultIdleNR-r16 ::= SEQUENCE {measResultServingCell-r16Measured results of the serving cell (i.e., PCell) from idle/inactive measurements.SEQUENCE { rsrp-Result-r16 RSRP-Range OPTIONAL, rsrq-Result-r16 RSRQ-Range OPTIONAL,resultsSSB-Indexes-r16Beam level measurement results (indexes and optionally, beam measurements).ResultsPerSSB-IndexList-r16 OPTIONAL }, measResultsPerCarrierListIdleNR-r16 SEQUENCE (SIZE (1.. maxFreqIdle-r16)) OF MeasResultsPerCarrierIdleNR-r16 OPTIONAL, ... } MeasResultsPerCarrierIdleNR-r16 ::= SEQUENCE {carrierFreq-r16Indicates the NR carrier frequency.ARFCN-ValueNR,measResultsPerCellListIdleNR-r16List of idle/inactive measured results for the maximum number of reported best cells for a given NR carrier.SEQUENCE (SIZE (1..maxCellMeasIdle-r16)) OF MeasResultsPerCellIdleNR-r16, ... } MeasResultsPerCellIdleNR-r16 ::= SEQUENCE { physCellId-r16 PhysCellId,measIdleResultNR-r16Idle/inactive measurement results for an NR cell (optionally including beam level measurements).SEQUENCE { rsrp-Result-r16 RSRP-Range OPTIONAL, rsrq-Result-r16 RSRQ-Range OPTIONAL,resultsSSB-Indexes-r16Beam level measurement results (indexes and optionally, beam measurements).ResultsPerSSB-IndexList-r16 OPTIONAL }, ... } ResultsPerSSB-IndexList-r16 ::= SEQUENCE (SIZE (1.. maxNrofIndexesToReport)) OF ResultsPerSSB-IndexIdle-r16 ResultsPerSSB-IndexIdle-r16 ::= SEQUENCE { ssb-Index-r16 SSB-Index, ssb-Results-r16 SEQUENCE { ssb-RSRP-Result-r16 RSRP-Range OPTIONAL, ssb-RSRQ-Result-r16 RSRQ-Range OPTIONAL } OPTIONAL } -- TAG-MEASRESULTIDLENR-STOP -- ASN1STOP
MeasResultIdleEUTRA field descriptions |
---|
carrierFreqEUTRA Indicates the E-UTRA carrier frequency. |
eutra-PhysCellId Indicates the physical cell identity of an E-UTRA cell. |
measIdleResultEUTRA Idle/inactive measurement results for an E-UTRA cell. |
measResultsPerCarrierListIdleEUTRA List of idle/inactive measured results for the maximum number of reported E-UTRA carriers. |
measResultsPerCellListIdleEUTRA List of idle/inactive measured results for the maximum number of reported best cells for a given E-UTRA carrier. |
MeasResultIdleNR field descriptions |
---|
carrierFreq Indicates the NR carrier frequency. |
measIdleResultNR Idle/inactive measurement results for an NR cell (optionally including beam level measurements). |
measResultServingCell Measured results of the serving cell (i.e., PCell) from idle/inactive measurements. |
measResultsPerCellListIdleNR List of idle/inactive measured results for the maximum number of reported best cells for a given NR carrier. |
resultsSSB-Indexes Beam level measurement results (indexes and optionally, beam measurements). |
The IE MeasResultSCG-Failure is used to provide information regarding failures detected by the UE in (NG)EN-DC and NR-DC.
-- ASN1START -- TAG-MEASRESULTSCG-FAILURE-START MeasResultSCG-Failure ::= SEQUENCE { measResultPerMOList MeasResultList2NR, ..., [[ locationInfo-r16 LocationInfo-r16 OPTIONAL ]] } MeasResultList2NR ::= SEQUENCE (SIZE (1..maxFreq)) OF MeasResult2NR -- TAG-MEASRESULTSCG-FAILURE-STOP -- ASN1STOP
The IE MeasResultsSL covers measured results for NR sidelink communication.
-- ASN1START -- TAG-MEASRESULTSSL-START MeasResultsSL-r16 ::= SEQUENCE { measResultsListSL-r16 CHOICE {measResultNR-SL-r16Include the measured results for NR sidelink communication.MeasResultNR-SL-r16, ... }, ... } MeasResultNR-SL-r16 ::= SEQUENCE {measResultListCBR-NR-r16CBR measurement results for NR sidelink communication.SEQUENCE (SIZE (1.. maxNrofSL-PoolToMeasureNR-r16)) OF MeasResultCBR-NR-r16, ... } MeasResultCBR-NR-r16 ::= SEQUENCE {sl-poolReportIdentity-r16The identity of the transmission resource pool which is corresponding to the sl-ResourcePoolID configured in a resource pool for NR sidelink communication.SL-ResourcePoolID-r16, sl-CBR-ResultsNR-r16 SL-CBR-r16, ... } -- TAG-MEASRESULTSSL-STOP -- ASN1STOP
MeasResultsSL field descriptions |
---|
measResultNR-SL Include the measured results for NR sidelink communication. |
MeasResultNR-SL field descriptions |
---|
measResultListCBR-NR CBR measurement results for NR sidelink communication. |
sl-poolReportIdentity The identity of the transmission resource pool which is corresponding to the sl-ResourcePoolID configured in a resource pool for NR sidelink communication. |
The IE MeasTriggerQuantityEUTRA is used to configure the trigger quantity and reporting range for E-UTRA measurements. The RSRP,RSRQ and SINR ranges correspond to RSRP-Range, RSRQ-Range and RS-SINR-Range in TS 36.331 [10], respectively.
-- ASN1START -- TAG-MEASTRIGGERQUANTITYEUTRA-START MeasTriggerQuantityEUTRA::= CHOICE { rsrp RSRP-RangeEUTRA, rsrq RSRQ-RangeEUTRA, sinr SINR-RangeEUTRA } RSRP-RangeEUTRA ::= INTEGER (0..97) RSRQ-RangeEUTRA ::= INTEGER (0..34) SINR-RangeEUTRA ::= INTEGER (0..127) -- TAG-MEASTRIGGERQUANTITYEUTRA-STOP -- ASN1STOP
The IE MobilityStateParameters contains parameters to determine UE mobility state.
-- ASN1START -- TAG-MOBILITYSTATEPARAMETERS-START MobilityStateParameters ::= SEQUENCE{t-EvaluationThe duration for evaluating criteria to enter mobility states. Corresponds to TCRmax in TS 38.304 [20]. Value in seconds, s30 corresponds to 30 s and so on.ENUMERATED { s30, s60, s120, s180, s240, spare3, spare2, spare1},t-HystNormalThe additional duration for evaluating criteria to enter normal mobility state. Corresponds to TCRmaxHyst in TS 38.304 [20]. Value in seconds, value s30 corresponds to 30 seconds and so on.ENUMERATED { s30, s60, s120, s180, s240, spare3, spare2, spare1},n-CellChangeMediumThe number of cell changes to enter medium mobility state. Corresponds to NCR_M in TS 38.304 [20].INTEGER (1..16),n-CellChangeHighThe number of cell changes to enter high mobility state. Corresponds to NCR_H in TS 38.304 [20].INTEGER (1..16) } -- TAG-MOBILITYSTATEPARAMETERS-STOP -- ASN1STOP
MobilityStateParameters field descriptions |
---|
n-CellChangeHigh The number of cell changes to enter high mobility state. Corresponds to NCR_H in TS 38.304 [20]. |
n-CellChangeMedium The number of cell changes to enter medium mobility state. Corresponds to NCR_M in TS 38.304 [20]. |
t-Evaluation The duration for evaluating criteria to enter mobility states. Corresponds to TCRmax in TS 38.304 [20]. Value in seconds, s30 corresponds to 30 s and so on. |
t-HystNormal The additional duration for evaluating criteria to enter normal mobility state. Corresponds to TCRmaxHyst in TS 38.304 [20]. Value in seconds, value s30 corresponds to 30 seconds and so on. |
The IE MsgA-ConfigCommon is used to configure the PRACH and PUSCH resource for transmission of MsgA in 2-step random access type procedure.
-- ASN1START -- TAG-MSGACONFIGCOMMON-START MsgA-ConfigCommon-r16 ::= SEQUENCE {rach-ConfigCommonTwoStepRA-r16Configuration of cell specific random access parameters which the UE uses for contention based and contention free 2-step random access type procedure as well as for 2-step RA type contention based beam failure recovery in this BWP.RACH-ConfigCommonTwoStepRA-r16,msgA-PUSCH-Config-r16Configuration of cell-specific MsgA PUSCH parameters which the UE uses for contention-based MsgA PUSCH transmission of this BWP. If the field is not configured for the selected UL BWP, the UE shall use the MsgA PUSCH configuration of initial UL BWP.MsgA-PUSCH-Config-r16 OPTIONAL --Cond InitialBWPConfig } -- TAG-MSGACONFIGCOMMON-STOP -- ASN1STOP
MsgA-ConfigCommon field descriptions |
---|
msgA-PUSCH-Config Configuration of cell-specific MsgA PUSCH parameters which the UE uses for contention-based MsgA PUSCH transmission of this BWP. If the field is not configured for the selected UL BWP, the UE shall use the MsgA PUSCH configuration of initial UL BWP. |
rach-ConfigCommonTwoStepRA Configuration of cell specific random access parameters which the UE uses for contention based and contention free 2-step random access type procedure as well as for 2-step RA type contention based beam failure recovery in this BWP. |
Conditional Presence | Explanation |
---|---|
InitialBWPConfig | The field is mandatory present when MsgA-ConfigCommon is configured for the initial uplink BWP, or when MsgA-ConfigCommon is configured for a non-initial uplink BWP and MsgA-ConfigCommon is not configured for the initial uplink BWP, otherwise the field is optionally present, Need S. |
The IE MsgA-PUSCH-Config is used to specify the PUSCH allocation for MsgA in 2-step random access type procedure.
-- ASN1START -- TAG-MSGA-PUSCH-CONFIG-START MsgA-PUSCH-Config-r16 ::= SEQUENCE {msgA-PUSCH-ResourceGroupA-r16MsgA PUSCH resources that the UE shall use when performing MsgA transmission using preambles group A. If field is not configured for the selected UL BWP, the UE shall use the MsgA PUSCH configuration for group A of initial UL BWP.MsgA-PUSCH-Resource-r16 OPTIONAL, -- Cond InitialBWPConfigmsgA-PUSCH-ResourceGroupB-r16MsgA PUSCH resources that the UE shall use when performing MsgA transmission using preambles group B.MsgA-PUSCH-Resource-r16 OPTIONAL, -- Cond GroupBConfiguredmsgA-TransformPrecoder-r16Enables or disables the transform precoder for MsgA transmission (see clause 6.1.3 of TS 38.214 [19]).ENUMERATED {enabled, disabled} OPTIONAL, -- Need RmsgA-DataScramblingIndex-r16Identifier used to initiate data scrambling (c_init) for msgA PUSCH. If the field is absent the UE applies the value Physical cell ID (physCellID).INTEGER (0..1023) OPTIONAL, -- Need SmsgA-DeltaPreamble-r16Power offset of msgA PUSCH relative to the preamble received target power.Actual value = field value * 2 [dB] (see TS 38.213 [13], clause 7.1).INTEGER (-1..6) OPTIONAL -- Need R } MsgA-PUSCH-Resource-r16 ::= SEQUENCE {msgA-MCS-r16Indicates the MCS index for msgA PUSCH from the Table 6.1.4.1-1 for DFT-s-OFDM and Table 5.1.3.1-1 for CP-OFDM in TS 38.214 [19].INTEGER (0..15),nrofSlotsMsgA-PUSCH-r16Number of slots (in active UL BWP numerology) containing one or multiple PUSCH occasions, each slot has the same time domain resource allocation (see TS 38.213 [13], clause 8.1A).INTEGER (1..4),nrofMsgA-PO-PerSlot-r16Number of time domain PUSCH occasions in each slot. PUSCH occasions including guard period are contiguous in time domain within a slot (see TS 38.213 [13], clause 8.1A).ENUMERATED {one, two, three, six},msgA-PUSCH-TimeDomainOffset-r16A single time offset with respect to the start of each PRACH slot (with at least one valid RO), counted as the number of slots (based on the numerology of active UL BWP). See TS 38.213 [13], clause 8.1A.INTEGER (1..32),msgA-PUSCH-TimeDomainAllocation-r16Indicates a combination of start symbol and length and PUSCH mapping type from the TDRA table (PUSCH-TimeDomainResourceAllocationList if provided in PUSCH-ConfigCommon, or else the default Table 6.1.2.1.1-2 in 38.214 [19] is used if pusch-TimeDomainAllocationList is not provided in PUSCH-ConfigCommon). The parameter K2 in the table is not used for msgA PUSCH. The network configures one of msgA-PUSCH-TimeDomainAllocation and startSymbolAndLengthMsgA-PO, but not both. If the field is absent, the UE shall use the value of startSymbolAndLenghtMsgA-PO.INTEGER (1..maxNrofUL-Allocations) OPTIONAL, -- Need SstartSymbolAndLengthMsgA-PO-r16An index giving valid combinations of start symbol, length and mapping type as start and length indicator (SLIV) for the first msgA PUSCH occasion, for RRC_CONNECTED UEs in non-initial BWP as described in TS 38.214 [19] clause 6.1.2. The network configures the field so that the allocation does not cross the slot boundary. The number of occupied symbols excludes the guard period. If the field is absent, the UE shall use the value in msgA-PUSCH-TimeDomainAllocation (see TS 38.213 [13], clause 8.1A). The network configures one of msgA-PUSCH-TimeDomainAllocation and startSymbolAndLengthMsgA-PO, but not both. If the field is absent, the UE shall use the value of msgA-PUSCH-TimeDomainAllocation.INTEGER (0..127) OPTIONAL, -- Need SmappingTypeMsgA-PUSCH-r16PUSCH mapping type A or B. If the field is absent, the UE shall use the parameter msgA-PUSCH-TimeDomainAllocation (see TS 38.213 [13], clause 8.1A).ENUMERATED {typeA, typeB} OPTIONAL, -- Need SguardPeriodMsgA-PUSCH-r16Guard period between PUSCH occasions in the unit of symbols (see TS 38.213 [13], clause 8.1A).INTEGER (0..3) OPTIONAL, -- Need RguardBandMsgA-PUSCH-r16PRB-level guard band between FDMed PUSCH occasions (see TS 38.213 [13], clause 8.1A). If interlaced PUSCH is configured, value 0 is applied.INTEGER (0..1),frequencyStartMsgA-PUSCH-r16Offset of lowest PUSCH occasion in frequency domain with respect to PRB 0 (see TS 38.213 [13], clause 8.1A).INTEGER (0..maxNrofPhysicalResourceBlocks-1),nrofPRBs-PerMsgA-PO-r16Number of PRBs per PUSCH occasion (see TS 38.213 [13], clause 8.1A).INTEGER (1..32),nrofMsgA-PO-FDM-r16The number of msgA PUSCH occasions FDMed in one time instance (see TS 38.213 [13], clause 8.1A).ENUMERATED {one, two, four, eight},msgA-IntraSlotFrequencyHopping-r16Intra-slot frequency hopping per PUSCH occasion (see TS 38.213 [13], clause 8.1A).ENUMERATED {enabled} OPTIONAL, -- Need RmsgA-HoppingBits-r16Value of hopping bits to indicate which frequency offset to be used for second hop. See Table 8.3-1 in TS 38.213 [13].BIT STRING (SIZE(2)) OPTIONAL, -- Cond FreqHopConfiguredmsgA-DMRS-Config-r16DMRS configuration for msgA PUSCH (see TS 38.213 [13], clause 8.1A and TS 38.214 [19] clause 6.2.2).MsgA-DMRS-Config-r16,nrofDMRS-Sequences-r16Number of DMRS sequences for MsgA PUSCH for CP-OFDM. In case of single PUSCH configuration or if the DMRS symbols of multiple configurations are not overlapped, if the DMRS resources configured in one PUSCH occasion is no larger than 8 (for len2) or 4 (for len1), then only DMRS port is configured.INTEGER (1..2),msgA-Alpha-r16Dedicated alpha value for MsgA PUSCH. If the field is absent, the UE shall use the value of msg3-Alpha if configured, else UE applies value 1 (see TS 38.213 [13], clause 7.1.1).ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} OPTIONAL, -- Need SinterlaceIndexFirstPO-MsgA-PUSCH-r16Interlace index of the first PUSCH occasion in frequency domain if interlaced PUSCH is configured. For 30kHz SCS only the integers 1, 2, 3, 4, 5 are applicable (see TS 38.213 [13], clause 8.1A).INTEGER (1..10) OPTIONAL, -- Need RnrofInterlacesPerMsgA-PO-r16Number of consecutive interlaces per PUSCH occasion if interlaced PUSCH is configured. For 30kHz SCS only the integers 1, 2, 3, 4, 5 are applicable (see TS 38.213 [13], clause 8.1A).INTEGER (1..10) OPTIONAL, -- Need R ... } MsgA-DMRS-Config-r16 ::= SEQUENCE {msgA-DMRS-AdditionalPosition-r16Indicates the position for additional DM-RS. If the field is absent, the UE applies value pos2.ENUMERATED {pos0, pos1, pos3} OPTIONAL, -- Need SmsgA-MaxLength-r16indicates single-symbol or double-symbol DMRS. If the field is absent, the UE applies value len1.ENUMERATED {len2} OPTIONAL, -- Need SmsgA-PUSCH-DMRS-CDM-Group-r161-bit indication of indices of CDM group(s). If the field is absent, then both CDM groups are used.INTEGER (0..1) OPTIONAL, -- Need SmsgA-PUSCH-NrofPorts-r160 indicates 1 port per CDM group, 1 indicates 2 ports per CDM group. If the field is absent then 4 ports per CDM group are used (see TS 38.213 [13], clause 8.1A).INTEGER (0..1) OPTIONAL, -- Need SmsgA-ScramblingID0-r16UL DMRS scrambling initialization for CP-OFDM. If the field is absent the UE applies the value Physical cell ID (physCellID).INTEGER (0..65535) OPTIONAL, -- Need SmsgA-ScramblingID1-r16UL DMRS scrambling initialization for CP-OFDM. If the field is absent the UE applies the value Physical cell ID (physCellID).INTEGER (0..65535) OPTIONAL -- Need S } -- TAG-MSGA-PUSCH-CONFIG-STOP -- ASN1STOP
MsgA-PUSCH-Config field descriptions |
---|
msgA-DataScramblingIndex Identifier used to initiate data scrambling (c_init) for msgA PUSCH. If the field is absent the UE applies the value Physical cell ID (physCellID). |
msgA-DeltaPreamble Power offset of msgA PUSCH relative to the preamble received target power.Actual value = field value * 2 [dB] (see TS 38.213 [13], clause 7.1). |
msgA-PUSCH-ResourceGroupA MsgA PUSCH resources that the UE shall use when performing MsgA transmission using preambles group A. If field is not configured for the selected UL BWP, the UE shall use the MsgA PUSCH configuration for group A of initial UL BWP. |
msgA-PUSCH-ResourceGroupB MsgA PUSCH resources that the UE shall use when performing MsgA transmission using preambles group B. |
msgA-TransformPrecoder Enables or disables the transform precoder for MsgA transmission (see clause 6.1.3 of TS 38.214 [19]). |
MsgA-PUSCH-Resource field descriptions |
---|
guardBandMsgA-PUSCH PRB-level guard band between FDMed PUSCH occasions (see TS 38.213 [13], clause 8.1A). If interlaced PUSCH is configured, value 0 is applied. |
guardPeriodMsgA-PUSCH Guard period between PUSCH occasions in the unit of symbols (see TS 38.213 [13], clause 8.1A). |
frequencyStartMsgA-PUSCH Offset of lowest PUSCH occasion in frequency domain with respect to PRB 0 (see TS 38.213 [13], clause 8.1A). |
interlaceIndexFirstPO-MsgA-PUSCH Interlace index of the first PUSCH occasion in frequency domain if interlaced PUSCH is configured. For 30kHz SCS only the integers 1, 2, 3, 4, 5 are applicable (see TS 38.213 [13], clause 8.1A). |
mappingTypeMsgA-PUSCH PUSCH mapping type A or B. If the field is absent, the UE shall use the parameter msgA-PUSCH-TimeDomainAllocation (see TS 38.213 [13], clause 8.1A). |
msgA-Alpha Dedicated alpha value for MsgA PUSCH. If the field is absent, the UE shall use the value of msg3-Alpha if configured, else UE applies value 1 (see TS 38.213 [13], clause 7.1.1). |
msgA-DMRS-Config DMRS configuration for msgA PUSCH (see TS 38.213 [13], clause 8.1A and TS 38.214 [19] clause 6.2.2). |
msgA-HoppingBits Value of hopping bits to indicate which frequency offset to be used for second hop. See Table 8.3-1 in TS 38.213 [13]. |
msgA-IntraSlotFrequencyHopping Intra-slot frequency hopping per PUSCH occasion (see TS 38.213 [13], clause 8.1A). |
msgA-MCS Indicates the MCS index for msgA PUSCH from the Table 6.1.4.1-1 for DFT-s-OFDM and Table 5.1.3.1-1 for CP-OFDM in TS 38.214 [19]. |
msgA-PUSCH-TimeDomainAllocation Indicates a combination of start symbol and length and PUSCH mapping type from the TDRA table (PUSCH-TimeDomainResourceAllocationList if provided in PUSCH-ConfigCommon, or else the default Table 6.1.2.1.1-2 in 38.214 [19] is used if pusch-TimeDomainAllocationList is not provided in PUSCH-ConfigCommon). The parameter K2 in the table is not used for msgA PUSCH. The network configures one of msgA-PUSCH-TimeDomainAllocation and startSymbolAndLengthMsgA-PO, but not both. If the field is absent, the UE shall use the value of startSymbolAndLenghtMsgA-PO. |
msgA-PUSCH-TimeDomainOffset A single time offset with respect to the start of each PRACH slot (with at least one valid RO), counted as the number of slots (based on the numerology of active UL BWP). See TS 38.213 [13], clause 8.1A. |
nrofDMRS-Sequences Number of DMRS sequences for MsgA PUSCH for CP-OFDM. In case of single PUSCH configuration or if the DMRS symbols of multiple configurations are not overlapped, if the DMRS resources configured in one PUSCH occasion is no larger than 8 (for len2) or 4 (for len1), then only DMRS port is configured. |
nrofInterlacesPerMsgA-PO Number of consecutive interlaces per PUSCH occasion if interlaced PUSCH is configured. For 30kHz SCS only the integers 1, 2, 3, 4, 5 are applicable (see TS 38.213 [13], clause 8.1A). |
nrofMsgA-PO-FDM The number of msgA PUSCH occasions FDMed in one time instance (see TS 38.213 [13], clause 8.1A). |
nrofMsgA-PO-PerSlot Number of time domain PUSCH occasions in each slot. PUSCH occasions including guard period are contiguous in time domain within a slot (see TS 38.213 [13], clause 8.1A). |
nrofPRBs-PerMsgA-PO Number of PRBs per PUSCH occasion (see TS 38.213 [13], clause 8.1A). |
nrofSlotsMsgA-PUSCH Number of slots (in active UL BWP numerology) containing one or multiple PUSCH occasions, each slot has the same time domain resource allocation (see TS 38.213 [13], clause 8.1A). |
startSymbolAndLengthMsgA-PO An index giving valid combinations of start symbol, length and mapping type as start and length indicator (SLIV) for the first msgA PUSCH occasion, for RRC_CONNECTED UEs in non-initial BWP as described in TS 38.214 [19] clause 6.1.2. The network configures the field so that the allocation does not cross the slot boundary. The number of occupied symbols excludes the guard period. If the field is absent, the UE shall use the value in msgA-PUSCH-TimeDomainAllocation (see TS 38.213 [13], clause 8.1A). The network configures one of msgA-PUSCH-TimeDomainAllocation and startSymbolAndLengthMsgA-PO, but not both. If the field is absent, the UE shall use the value of msgA-PUSCH-TimeDomainAllocation. |
MsgA-DMRS-Config field descriptions |
---|
msgA-DMRS-AdditionalPosition Indicates the position for additional DM-RS. If the field is absent, the UE applies value pos2. |
msgA-MaxLength indicates single-symbol or double-symbol DMRS. If the field is absent, the UE applies value len1. |
msgA-PUSCH-DMRS-CDM-Group 1-bit indication of indices of CDM group(s). If the field is absent, then both CDM groups are used. |
msgA-PUSCH-NrofPorts 0 indicates 1 port per CDM group, 1 indicates 2 ports per CDM group. If the field is absent then 4 ports per CDM group are used (see TS 38.213 [13], clause 8.1A). |
msgA-ScramblingID0 UL DMRS scrambling initialization for CP-OFDM. If the field is absent the UE applies the value Physical cell ID (physCellID). |
msgA-ScramblingID1 UL DMRS scrambling initialization for CP-OFDM. If the field is absent the UE applies the value Physical cell ID (physCellID). |
Conditional Presence | Explanation |
---|---|
FreqHopConfigured | This field is mandatory present when the field msgA-IntraSlotFrequencyHopping is configured. Otherwise, the field is absent. |
GroupBConfigured | The field is mandatory present if groupB-ConfiguredTwoStepRA is configured in RACH-ConfigCommonTwoStepRA, otherwise the field is absent. |
InitialBWPConfig | The field is mandatory present when MsgA-ConfigCommon is configured for the initial uplink BWP, or when MsgA-ConfigCommon is configured for a non-initial uplink BWP and MsgA-ConfigCommon is not configured for the initial uplink BWP, otherwise the field is optionally present, Need S. |
The IE MultiFrequencyBandListNR is used to configure a list of one or multiple NR frequency bands.
-- ASN1START -- TAG-MULTIFREQUENCYBANDLISTNR-START MultiFrequencyBandListNR ::= SEQUENCE (SIZE (1..maxNrofMultiBands)) OF FreqBandIndicatorNR -- TAG-MULTIFREQUENCYBANDLISTNR-STOP -- ASN1STOP
The IE MultiFrequencyBandListNR-SIB indicates the list of frequency bands, for which cell (re-)selection parameters are common, and a list of additionalPmax and additionalSpectrumEmission.
-- ASN1START -- TAG-MULTIFREQUENCYBANDLISTNR-SIB-START MultiFrequencyBandListNR-SIB ::= SEQUENCE (SIZE (1.. maxNrofMultiBands)) OF NR-MultiBandInfo NR-MultiBandInfo ::= SEQUENCE {freqBandIndicatorNRProvides an NR frequency band number as defined in TS 38.101-1 [15] and TS 38.101-2 [39], table 5.2-1.FreqBandIndicatorNR OPTIONAL, -- Cond OptULNotSIB2nr-NS-PmaxListProvides a list of additionalPmax and additionalSpectrumEmission values. If the field is absent the UE uses value 0 for the additionalSpectrumEmission (see TS 38.101-1 [15] table 6.2.3.1-1A, and TS 38.101-2 [39], table 6.2.3.1-2). This field is ignored by IAB-MT, the IAB-MT applies output power and emissions requirements, as specified in TS 38.174 [63].NR-NS-PmaxList OPTIONAL -- Need S } -- TAG-MULTIFREQUENCYBANDLISTNR-SIB-STOP -- ASN1STOP
NR-MultiBandInfo field descriptions |
---|
freqBandIndicatorNR Provides an NR frequency band number as defined in TS 38.101-1 [15] and TS 38.101-2 [39], table 5.2-1. |
nr-NS-PmaxList Provides a list of additionalPmax and additionalSpectrumEmission values. If the field is absent the UE uses value 0 for the additionalSpectrumEmission (see TS 38.101-1 [15] table 6.2.3.1-1A, and TS 38.101-2 [39], table 6.2.3.1-2). This field is ignored by IAB-MT, the IAB-MT applies output power and emissions requirements, as specified in TS 38.174 [63]. |
Conditional Presence | Explanation |
---|---|
OptULNotSIB2 | The field is absent for SIB2 and is mandatory present in SIB4 and frequencyInfoDL-SIB. Otherwise, if the field is absent in frequencyInfoUL-SIB in UplinkConfigCommonSIB, the UE will use the frequency band indicated in frequencyInfoDL-SIB in DownlinkConfigCommonSIB. |
The IE NeedForGapsConfigNR contains configuration related to the reporting of measurement gap requirement information. –NeedForGapsInfoNR The IE NeedForGapsInfoNR indicates whether measurement gap is required for the UE to perform SSB based measurements on an NR target band while NR-DC or NE-DC is not configured.
-- ASN1START -- TAG-NeedForGapsConfigNR-START NeedForGapsConfigNR-r16 ::= SEQUENCE {requestedTargetBandFilterNR-r16Indicates the target NR bands that the UE is requested to report the gap requirement information.SEQUENCE (SIZE (1..maxBands)) OF FreqBandIndicatorNR OPTIONAL -- Need R } -- TAG-NeedForGapsConfigNR-STOP -- ASN1STOP -- ASN1START -- TAG-NeedForGapsInfoNR-START NeedForGapsInfoNR-r16 ::= SEQUENCE {intraFreq-needForGap-r16Indicates the measurement gap requirement information for NR intra-frequency measurement.NeedForGapsIntraFreqList-r16,interFreq-needForGap-r16Indicates the measurement gap requirement information for NR inter-frequency measurement.NeedForGapsBandListNR-r16 } NeedForGapsIntraFreqList-r16 ::= SEQUENCE (SIZE (1.. maxNrofServingCells)) OF NeedForGapsIntraFreq-r16 NeedForGapsBandListNR-r16 ::= SEQUENCE (SIZE (1..maxBands)) OF NeedForGapsNR-r16 NeedForGapsIntraFreq-r16 ::= SEQUENCE {servCellId-r16Indicates the serving cell which contains the target SSB (associated with the initial DL BWP) to be measured.ServCellIndex,gapIndicationIntra-r16Indicates whether measurement gap is required for the UE to perform intra-frequency SSB based measurements on the concerned serving cell. Value gap indicates that a measurement gap is needed if any of the UE configured BWPs do not contain the frequency domain resources of the SSB associated to the initial DL BWP. Value no-gap indicates a measurement gap is not needed to measure the SSB associated to the initial DL BWP for all configured BWPs, no matter the SSB is within the configured BWP or not.ENUMERATED {gap, no-gap} } NeedForGapsNR-r16 ::= SEQUENCE {bandNR-r16Indicates the NR target band to be measured.FreqBandIndicatorNR,gapIndication-r16Indicates whether measurement gap is required for the UE to perform SSB based measurements on the concerned NR target band while NR-DC or NE-DC is not configured. The UE determines this information based on the resultant configuration of the RRCReconfiguration or RRCResumemessage that triggers this response. Value gap indicates that a measurement gap is needed, value no-gap indicates a measurement gap is not needed.ENUMERATED {gap, no-gap} } -- TAG-NeedForGapsInfoNR-STOP -- ASN1STOP
NeedForGapsConfigNR field descriptions |
---|
requestedTargetBandFilterNR Indicates the target NR bands that the UE is requested to report the gap requirement information. |
NeedForGapsInfoNR field descriptions |
---|
intraFreq-needForGap Indicates the measurement gap requirement information for NR intra-frequency measurement. |
interFreq-needForGap Indicates the measurement gap requirement information for NR inter-frequency measurement. |
NeedForGapsIntraFreq field descriptions |
---|
servCellId Indicates the serving cell which contains the target SSB (associated with the initial DL BWP) to be measured. |
gapIndicationIntra Indicates whether measurement gap is required for the UE to perform intra-frequency SSB based measurements on the concerned serving cell. Value gap indicates that a measurement gap is needed if any of the UE configured BWPs do not contain the frequency domain resources of the SSB associated to the initial DL BWP. Value no-gap indicates a measurement gap is not needed to measure the SSB associated to the initial DL BWP for all configured BWPs, no matter the SSB is within the configured BWP or not. |
NeedForGapsNR field descriptions |
---|
bandNR Indicates the NR target band to be measured. |
gapIndication Indicates whether measurement gap is required for the UE to perform SSB based measurements on the concerned NR target band while NR-DC or NE-DC is not configured. The UE determines this information based on the resultant configuration of the RRCReconfiguration or RRCResumemessage that triggers this response. Value gap indicates that a measurement gap is needed, value no-gap indicates a measurement gap is not needed. |
The IE NextHopChainingCount is used to update the KgNB key and corresponds to parameter NCC: See TS 33.501 [11].
The IE NG-5G-S-TMSI contains a 5G S-Temporary Mobile Subscription Identifier (5G-S-TMSI), a temporary UE identity provided by the 5GC which uniquely identifies the UE within the tracking area, see TS 23.003 [21].
The IE NPN-Identity includes either a list of CAG-IDs or a list of NIDs per PLMN Identity. Further information regarding how to set the IE is specified in TS 23.003 [21].
-- ASN1START -- TAG-NPN-IDENTITY-START NPN-Identity-r16 ::= CHOICE { pni-npn-r16 SEQUENCE { plmn-Identity-r16 PLMN-Identity,cag-IdentityList-r16The cag-IdentityList contains one or more CAG IDs. All CAG IDs associated to the same PLMN ID are listed in the same cag-IdentityList entry.SEQUENCE (SIZE (1..maxNPN-r16)) OF CAG-IdentityInfo-r16 }, snpn-r16 SEQUENCE { plmn-Identity-r16 PLMN-Identity,nid-List-r16The nid-List contains one or more NID.SEQUENCE (SIZE (1..maxNPN-r16)) OF NID-r16 } } CAG-IdentityInfo-r16 ::= SEQUENCE {cag-Identity-r16A CAG-ID as specified in TS 23.003 [21]. The PLMN ID and a CAG ID in the NPN-Identity identifies a PNI-NPN.BIT STRING (SIZE (32)),manualCAGselectionAllowed-r16The manualCAGselectionAllowed indicates that the CAG ID can be selected manually even if it is outside the UE's allowed CAG list.ENUMERATED {true} OPTIONAL -- Need R } NID-r16 ::= BIT STRING (SIZE (44)) -- TAG-NPN-IDENTITY-STOP -- ASN1STOP
NPN-Identity field descriptions |
---|
cag-Identity A CAG-ID as specified in TS 23.003 [21]. The PLMN ID and a CAG ID in the NPN-Identity identifies a PNI-NPN. |
cag-IdentityList The cag-IdentityList contains one or more CAG IDs. All CAG IDs associated to the same PLMN ID are listed in the same cag-IdentityList entry. |
manualCAGselectionAllowed The manualCAGselectionAllowed indicates that the CAG ID can be selected manually even if it is outside the UE's allowed CAG list. |
NID A NID as specified in TS 23.003 [21]. The PLMN ID and a NID in the NPN-Identity identifies a SNPN. |
nid-List The nid-List contains one or more NID. |
The IE NPN-IdentityInfoList includes a list of NPN identity information.
-- ASN1START -- TAG-NPN-IDENTITYINFOLIST-START NPN-IdentityInfoList-r16 ::= SEQUENCE (SIZE (1..maxNPN-r16)) OF NPN-IdentityInfo-r16 NPN-IdentityInfo-r16 ::= SEQUENCE {npn-IdentityList-r16The npn-IdentityList contains one or more NPN Identity elements.SEQUENCE (SIZE (1..maxNPN-r16)) OF NPN-Identity-r16,trackingAreaCode-r16Indicates the Tracking Area Code to which the cell indicated by cellIdentity field belongs.TrackingAreaCode,ranac-r16Indicates the RAN Area Code to which the cell indicated by cellIdentity field belongs.RAN-AreaCode OPTIONAL, -- Need R cellIdentity-r16 CellIdentity,cellReservedForOperatorUse-r16Indicates whether the cell is reserved for operator use (for the NPN(s) identified in the npn-IdentityList) as defined in TS 38.304 [20].This field is ignored by NPN capable IAB-MT.ENUMERATED {reserved, notReserved},iab-Support-r16This field combines both the support of IAB and the cell status for IAB. If the field is present, the cell supports IAB and the cell is also considered as a candidate for cell (re)selection for IAB-nodes; if the field is absent, the cell does not support IAB and/or the cell is barred for IAB-node.ENUMERATED {true} OPTIONAL, -- Need S ... } -- TAG-NPN-IDENTITYINFOLIST-STOP -- ASN1STOP
NPN-IdentityInfoList field descriptions |
---|
iab-Support This field combines both the support of IAB and the cell status for IAB. If the field is present, the cell supports IAB and the cell is also considered as a candidate for cell (re)selection for IAB-nodes; if the field is absent, the cell does not support IAB and/or the cell is barred for IAB-node. |
NPN-IdentityInfo The NPN-IdentityInfo contains one or more NPN identities and additional information associated with those NPNs. Only the same type of NPNs (either SNPNs or PNI-NPNs) can be listed in a NPN-IdentityInfo element. |
npn-IdentityList The npn-IdentityList contains one or more NPN Identity elements. |
trackingAreaCode Indicates the Tracking Area Code to which the cell indicated by cellIdentity field belongs. |
ranac Indicates the RAN Area Code to which the cell indicated by cellIdentity field belongs. |
cellReservedForOperatorUse Indicates whether the cell is reserved for operator use (for the NPN(s) identified in the npn-IdentityList) as defined in TS 38.304 [20].This field is ignored by NPN capable IAB-MT. |
The IE NR-NS-PmaxList is used to configure a list of additionalPmax and additionalSpectrumEmission, as defined in TS 38.101-1 [15], table 6.2.3.1-1A, and TS 38.101-2 [39], table 6.2.3.1-2, for a given frequency band.
-- ASN1START -- TAG-NR-NS-PMAXLIST-START NR-NS-PmaxList ::= SEQUENCE (SIZE (1..maxNR-NS-Pmax)) OF NR-NS-PmaxValue NR-NS-PmaxValue ::= SEQUENCE { additionalPmax P-Max OPTIONAL, -- Need N additionalSpectrumEmission AdditionalSpectrumEmission } -- TAG-NR-NS-PMAXLIST-STOP -- ASN1STOP
The IE NZP-CSI-RS-Resource is used to configure Non-Zero-Power (NZP) CSI-RS transmitted in the cell where the IE is included, which the UE may be configured to measure on (see TS 38.214 [19], clause 5.2.2.3.1). A change of configuration between periodic, semi-persistent or aperiodic for an NZP-CSI-RS-Resource is not supported without a release and add.
-- ASN1START -- TAG-NZP-CSI-RS-RESOURCE-START NZP-CSI-RS-Resource ::= SEQUENCE { nzp-CSI-RS-ResourceId NZP-CSI-RS-ResourceId,resourceMappingOFDM symbol location(s) in a slot and subcarrier occupancy in a PRB of the CSI-RS resource.CSI-RS-ResourceMapping,powerControlOffsetPower offset of PDSCH RE to NZP CSI-RS RE. Value in dB (see TS 38.214 [19], clauses 5.2.2.3.1 and 4.1).INTEGER (-8..15),powerControlOffsetSSPower offset of NZP CSI-RS RE to SSS RE. Value in dB (see TS 38.214 [19], clause 5.2.2.3.1).ENUMERATED{db-3, db0, db3, db6} OPTIONAL, -- Need RscramblingIDScrambling ID (see TS 38.214 [19], clause 5.2.2.3.1).ScramblingId,periodicityAndOffsetPeriodicity and slot offset sl1 corresponds to a periodicity of 1 slot, sl2 to a periodicity of two slots, and so on. The corresponding offset is also given in number of slots (see TS 38.214 [19], clause 5.2.2.3.1). Network always configures the UE with a value for this field for periodic and semi-persistent NZP-CSI-RS-Resource (as indicated in CSI-ResourceConfig).CSI-ResourcePeriodicityAndOffset OPTIONAL, -- Cond PeriodicOrSemiPersistentqcl-InfoPeriodicCSI-RSFor a target periodic CSI-RS, contains a reference to one TCI-State in TCI-States for providing the QCL source and QCL type. For periodic CSI-RS, the source can be SSB or another periodic-CSI-RS. Refers to the TCI-State which has this value for tci-StateId and is defined in tci-StatesToAddModList in the PDSCH-Config included in the BWP-Downlink corresponding to the serving cell and to the DL BWP to which the resource belongs to (see TS 38.214 [19], clause 5.2.2.3.1).TCI-StateId OPTIONAL, -- Cond Periodic ... } -- TAG-NZP-CSI-RS-RESOURCE-STOP -- ASN1STOP
NZP-CSI-RS-Resource field descriptions |
---|
periodicityAndOffset Periodicity and slot offset sl1 corresponds to a periodicity of 1 slot, sl2 to a periodicity of two slots, and so on. The corresponding offset is also given in number of slots (see TS 38.214 [19], clause 5.2.2.3.1). Network always configures the UE with a value for this field for periodic and semi-persistent NZP-CSI-RS-Resource (as indicated in CSI-ResourceConfig). |
powerControlOffset Power offset of PDSCH RE to NZP CSI-RS RE. Value in dB (see TS 38.214 [19], clauses 5.2.2.3.1 and 4.1). |
powerControlOffsetSS Power offset of NZP CSI-RS RE to SSS RE. Value in dB (see TS 38.214 [19], clause 5.2.2.3.1). |
qcl-InfoPeriodicCSI-RS For a target periodic CSI-RS, contains a reference to one TCI-State in TCI-States for providing the QCL source and QCL type. For periodic CSI-RS, the source can be SSB or another periodic-CSI-RS. Refers to the TCI-State which has this value for tci-StateId and is defined in tci-StatesToAddModList in the PDSCH-Config included in the BWP-Downlink corresponding to the serving cell and to the DL BWP to which the resource belongs to (see TS 38.214 [19], clause 5.2.2.3.1). |
resourceMapping OFDM symbol location(s) in a slot and subcarrier occupancy in a PRB of the CSI-RS resource. |
scramblingID Scrambling ID (see TS 38.214 [19], clause 5.2.2.3.1). |
Conditional Presence | Explanation |
---|---|
Periodic | The field is optionally present, Need M, for periodic NZP-CSI-RS-Resources (as indicated in CSI-ResourceConfig). The field is absent otherwise. |
PeriodicOrSemiPersistent | The field is optionally present, Need M, for periodic and semi-persistent NZP-CSI-RS-Resources (as indicated in CSI-ResourceConfig). The field is absent otherwise. |
The IE NZP-CSI-RS-ResourceId is used to identify one NZP-CSI-RS-Resource.
The IE NZP-CSI-RS-ResourceSet is a set of Non-Zero-Power (NZP) CSI-RS resources (their IDs) and set-specific parameters.
-- ASN1START -- TAG-NZP-CSI-RS-RESOURCESET-START NZP-CSI-RS-ResourceSet ::= SEQUENCE { nzp-CSI-ResourceSetId NZP-CSI-RS-ResourceSetId,nzp-CSI-RS-ResourcesNZP-CSI-RS-Resources associated with this NZP-CSI-RS resource set (see TS 38.214 [19], clause 5.2). For CSI, there are at most 8 NZP CSI RS resources per resource set.SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerSet)) OF NZP-CSI-RS-ResourceId,repetitionIndicates whether repetition is on/off. If the field is set to off or if the field is absent, the UE may not assume that the NZP-CSI-RS resources within the resource set are transmitted with the same downlink spatial domain transmission filter (see TS 38.214 [19], clauses 5.2.2.3.1 and 5.1.6.1.2). It can only be configured for CSI-RS resource sets which are associated with CSI-ReportConfig with report of L1 RSRP, L1 SINR or "no report".ENUMERATED { on, off } OPTIONAL, -- Need S aperiodicTriggeringOffset INTEGER(0..6) OPTIONAL, -- Need Strs-InfoIndicates that the antenna port for all NZP-CSI-RS resources in the CSI-RS resource set is same. If the field is absent or released the UE applies the value false (see TS 38.214 [19], clause 5.2.2.3.1).ENUMERATED {true} OPTIONAL, -- Need R ..., [[ aperiodicTriggeringOffset-r16 INTEGER(0..31) OPTIONAL -- Need S ]] } -- TAG-NZP-CSI-RS-RESOURCESET-STOP -- ASN1STOP
NZP-CSI-RS-ResourceSet field descriptions |
---|
aperiodicTriggeringOffset, aperiodicTriggeringOffset-r16 Offset X between the slot containing the DCI that triggers a set of aperiodic NZP CSI-RS resources and the slot in which the CSI-RS resource set is transmitted. For aperiodicTriggeringOffset, the value 0 corresponds to 0 slots, value 1 corresponds to 1 slot, value 2 corresponds to 2 slots, value 3 corresponds to 3 slots, value 4 corresponds to 4 slots, value 5 corresponds to 16 slots, value 6 corresponds to 24 slots. For aperiodicTriggeringOffset-r16, the value indicates the number of slots. The network configures only one of the fields. When neither field is included, the UE applies the value 0. |
nzp-CSI-RS-Resources NZP-CSI-RS-Resources associated with this NZP-CSI-RS resource set (see TS 38.214 [19], clause 5.2). For CSI, there are at most 8 NZP CSI RS resources per resource set. |
repetition Indicates whether repetition is on/off. If the field is set to off or if the field is absent, the UE may not assume that the NZP-CSI-RS resources within the resource set are transmitted with the same downlink spatial domain transmission filter (see TS 38.214 [19], clauses 5.2.2.3.1 and 5.1.6.1.2). It can only be configured for CSI-RS resource sets which are associated with CSI-ReportConfig with report of L1 RSRP, L1 SINR or "no report". |
trs-Info Indicates that the antenna port for all NZP-CSI-RS resources in the CSI-RS resource set is same. If the field is absent or released the UE applies the value false (see TS 38.214 [19], clause 5.2.2.3.1). |
The IE NZP-CSI-RS-ResourceSetId is used to identify one NZP-CSI-RS-ResourceSet.
The IE P-Max is used to limit the UE's uplink transmission power on a carrier frequency, in TS 38.101-1 [15] and is used to calculate the parameter Pcompensation defined in TS 38.304 [20].
The IE PCI-ARFCN-EUTRA is used to encode EUTRA PCI and ARFCN.
-- ASN1START -- TAG-PCIARFCNEUTRA-START PCI-ARFCN-EUTRA-r16 ::= SEQUENCE { physCellId-r16 EUTRA-PhysCellId, carrierFreq-r16 ARFCN-ValueEUTRA } -- TAG-PCIARFCNEUTRA-STOP -- ASN1STOP
The IE PCI-ARFCN-NR is used to encode NR PCI and ARFCN.
-- ASN1START -- TAG-PCIARFCNNR-START PCI-ARFCN-NR-r16 ::= SEQUENCE { physCellId-r16 PhysCellId, carrierFreq-r16 ARFCN-ValueNR } -- TAG-PCIARFCNNR-STOP -- ASN1STOP
The IE PCI-List concerns a list of physical cell identities, which may be used for different purposes.
-- ASN1START -- TAG-PCI-LIST-START PCI-List ::= SEQUENCE (SIZE (1..maxNrofCellMeas)) OF PhysCellId -- TAG-PCI-LIST-STOP -- ASN1STOP
The IE PCI-Range is used to encode either a single or a range of physical cell identities. The range is encoded by using a start value and by indicating the number of consecutive physical cell identities (including start) in the range. For fields comprising multiple occurrences of PCI-Range, the Network may configure overlapping ranges of physical cell identities.
-- ASN1START -- TAG-PCI-RANGE-START PCI-Range ::= SEQUENCE {startIndicates the lowest physical cell identity in the range.PhysCellId,rangeIndicates the number of physical cell identities in the range (including start). Value n4 corresponds with 4, value n8 corresponds with 8 and so on. The UE shall apply value 1 in case the field is absent, in which case only the physical cell identity value indicated by start applies.ENUMERATED {n4, n8, n12, n16, n24, n32, n48, n64, n84, n96, n128, n168, n252, n504, n1008,spare1} OPTIONAL -- Need S } -- TAG-PCI-RANGE-STOP -- ASN1STOP
PCI-Range field descriptions |
---|
range Indicates the number of physical cell identities in the range (including start). Value n4 corresponds with 4, value n8 corresponds with 8 and so on. The UE shall apply value 1 in case the field is absent, in which case only the physical cell identity value indicated by start applies. |
start Indicates the lowest physical cell identity in the range. |
The IE PCI-RangeElement is used to define a PCI-Range as part of a list (e.g. AddMod list).
-- ASN1START -- TAG-PCI-RANGEELEMENT-START PCI-RangeElement ::= SEQUENCE { pci-RangeIndex PCI-RangeIndex,pci-RangePhysical cell identity or a range of physical cell identities.PCI-Range } -- TAG-PCI-RANGEELEMENT-STOP -- ASN1STOP
PCI-RangeElement field descriptions |
---|
pci-Range Physical cell identity or a range of physical cell identities. |
The IE PCI-RangeIndex identifies a physical cell id range, which may be used for different purposes.
The IE PCI-RangeIndexList concerns a list of indexes of physical cell id ranges, which may be used for different purposes.
-- ASN1START -- TAG-PCI-RANGEINDEXLIST-START PCI-RangeIndexList ::= SEQUENCE (SIZE (1..maxNrofPCI-Ranges)) OF PCI-RangeIndex -- TAG-PCI-RANGEINDEXLIST-STOP -- ASN1STOP
The IE PDCCH-Config is used to configure UE specific PDCCH parameters such as control resource sets (CORESET), search spaces and additional parameters for acquiring the PDCCH. If this IE is used for the scheduled cell in case of cross carrier scheduling, the fields other than searchSpacesToAddModList and searchSpacesToReleaseList are absent. If the IE is used for a dormant BWP,the fields other than controlResourceSetToAddModList and controlResourceSetToReleaseList are absent.
-- ASN1START -- TAG-PDCCH-CONFIG-START PDCCH-Config ::= SEQUENCE { controlResourceSetToAddModList SEQUENCE(SIZE(1..3)) OF ControlResourceSet OPTIONAL, -- Need N controlResourceSetToReleaseList SEQUENCE(SIZE(1..3)) OF ControlResourceSetId OPTIONAL, -- Need N searchSpacesToAddModList SEQUENCE(SIZE(1..10)) OF SearchSpace OPTIONAL, -- Need N searchSpacesToReleaseList SEQUENCE(SIZE(1..10)) OF SearchSpaceId OPTIONAL, -- Need NdownlinkPreemptionConfiguration of downlink preemption indications to be monitored in this cell (see TS 38.213 [13], clause 11.2).SetupRelease { DownlinkPreemption } OPTIONAL, -- Need Mtpc-PUSCHEnable and configure reception of group TPC commands for PUSCH.SetupRelease { PUSCH-TPC-CommandConfig } OPTIONAL, -- Need Mtpc-PUCCHEnable and configure reception of group TPC commands for PUCCH.SetupRelease { PUCCH-TPC-CommandConfig } OPTIONAL, -- Need Mtpc-SRSEnable and configure reception of group TPC commands for SRS.SetupRelease { SRS-TPC-CommandConfig} OPTIONAL, -- Need M ..., [[ controlResourceSetToAddModListSizeExt-v1610 SEQUENCE (SIZE (1..2)) OF ControlResourceSet OPTIONAL, -- Need N controlResourceSetToReleaseListSizeExt-r16 SEQUENCE (SIZE (1..5)) OF ControlResourceSetId-r16 OPTIONAL, -- Need N searchSpacesToAddModListExt-r16 SEQUENCE(SIZE(1..10)) OF SearchSpaceExt-r16 OPTIONAL, -- Need NuplinkCancellation-r16Configuration of uplink cancellation indications to be monitored in this cell (see TS 38.213 [13], clause 11.2A).SetupRelease { UplinkCancellation-r16 } OPTIONAL, -- Need MmonitoringCapabilityConfig-r16Configures either Rel-15 PDCCH monitoring capability or Rel-16 PDCCH monitoring capability for PDCCH monitoring on a serving cell. Value r15monitoringcapablity enables the Rel-15 monitoring capability, and value r16monitoringcapablity enables the Rel-16 PDCCH monitoring capability (see TS 38.213 [13], clause 10.1).ENUMERATED { r15monitoringcapability,r16monitoringcapability } OPTIONAL, -- Need M searchSpaceSwitchConfig-r16 SearchSpaceSwitchConfig-r16 OPTIONAL -- Need R ]] } SearchSpaceSwitchConfig-r16 ::= SEQUENCE {cellGroupsForSwitchList-r16The list of serving cells which are bundled for the search space group switching purpose (see TS 38.213 [13], clause 10.4). A serving cell can belong to only one CellGroupForSwitch. The network configures the same list for all BWPs of serving cells in the same CellGroupForSwitch.SEQUENCE(SIZE(1..4)) OF CellGroupForSwitch-r16 OPTIONAL, -- Need RsearchSpaceSwitchDelay-r16Indicates the value to be applied by a UE for Search Space Set Group switching; corresponds to the P value in TS 38.213 [13], clause 10.4. The network configures the same value for all BWPs of serving cells in the same CellGroupForSwitch.INTEGER (10..52) OPTIONAL -- Need R } CellGroupForSwitch-r16 ::= SEQUENCE(SIZE(1..16)) OF ServCellIndex -- TAG-PDCCH-CONFIG-STOP -- ASN1STOP
PDCCH-Config field descriptions |
---|
controlResourceSetToAddModList, controlResourceSetToAddModListSizeExt List of UE specifically configured Control Resource Sets (CORESETs) to be used by the UE. The network restrictions on configuration of CORESETs per DL BWP are specified in TS 38.213 [13], clause 10.1 and TS 38.306 [26]. The UE shall consider entries in controlResourceSetToAddModList and in controlResourceSetToAddModListSizeExt as a single list, i.e. an entry created using controlResourceSetToAddModList can be modified using controlResourceSetToAddModListSizeExt(or deleted using controlResourceSetToReleaseListSizeExt) and vice-versa. In case network reconfigures control resource set with the same ControlResourceSetId as used for commonControlResourceSet configured via PDCCH-ConfigCommon, the configuration from PDCCH-Config always takes precedence and should not be updated by the UE based on servingCellConfigCommon. |
controlResourceSetToReleaseList, controlResourceSetToReleaseListSizeExt List of UE specifically configured Control Resource Sets (CORESETs) to be released by the UE. This field only applies to CORESETs configured by controlResourceSetToAddModListor controlResourceSetToAddModListSizeExt and does not release the field commonControlResourceSet configured by PDCCH-ConfigCommon. |
downlinkPreemption Configuration of downlink preemption indications to be monitored in this cell (see TS 38.213 [13], clause 11.2). |
monitoringCapabilityConfig Configures either Rel-15 PDCCH monitoring capability or Rel-16 PDCCH monitoring capability for PDCCH monitoring on a serving cell. Value r15monitoringcapablity enables the Rel-15 monitoring capability, and value r16monitoringcapablity enables the Rel-16 PDCCH monitoring capability (see TS 38.213 [13], clause 10.1). |
searchSpacesToAddModList, searchSpacesToAddModListExt List of UE specifically configured Search Spaces. The network configures at most 10 Search Spaces per BWP per cell (including UE-specific and common Search Spaces). If the network includes searchSpacesToAddModListExt, it includes the same number of entries, and listed in the same order, as in searchSpacesToAddModList. |
tpc-PUCCH Enable and configure reception of group TPC commands for PUCCH. |
tpc-PUSCH Enable and configure reception of group TPC commands for PUSCH. |
tpc-SRS Enable and configure reception of group TPC commands for SRS. |
uplinkCancellation Configuration of uplink cancellation indications to be monitored in this cell (see TS 38.213 [13], clause 11.2A). |
SearchSpaceSwitchConfig field descriptions |
---|
cellGroupsForSwitchList The list of serving cells which are bundled for the search space group switching purpose (see TS 38.213 [13], clause 10.4). A serving cell can belong to only one CellGroupForSwitch. The network configures the same list for all BWPs of serving cells in the same CellGroupForSwitch. |
searchSpaceSwitchDelay Indicates the value to be applied by a UE for Search Space Set Group switching; corresponds to the P value in TS 38.213 [13], clause 10.4. The network configures the same value for all BWPs of serving cells in the same CellGroupForSwitch. |
The IE PDCCH-ConfigCommon is used to configure cell specific PDCCH parameters provided in SIB as well as in dedicated signalling.
-- ASN1START -- TAG-PDCCH-CONFIGCOMMON-START PDCCH-ConfigCommon ::= SEQUENCE {controlResourceSetZeroParameters of the common CORESET#0 which can be used in any common or UE-specific search spaces. The values are interpreted like the corresponding bits in MIBpdcch-ConfigSIB1. Even though this field is only configured in the initial BWP (BWP#0) controlResourceSetZero can be used in search spaces configured in other DL BWP(s) than the initial DL BWP if the conditions defined in TS 38.213 [13], clause 10 are satisfied.ControlResourceSetZero OPTIONAL, -- Cond InitialBWP-OnlycommonControlResourceSetAn additional common control resource set which may be configured and used for any common or UE-specific search space. If the network configures this field, it uses a ControlResourceSetId other than 0 for this ControlResourceSet. The network configures the commonControlResourceSet in SIB1 so that it is contained in the bandwidth of CORESET#0.ControlResourceSet OPTIONAL, -- Need RsearchSpaceZeroParameters of the common SearchSpace#0. The values are interpreted like the corresponding bits in MIBpdcch-ConfigSIB1. Even though this field is only configured in the initial BWP (BWP#0), searchSpaceZero can be used in search spaces configured in other DL BWP(s) than the initial DL BWP if the conditions described in TS 38.213 [13], clause 10, are satisfied.SearchSpaceZero OPTIONAL, -- Cond InitialBWP-Only commonSearchSpaceList SEQUENCE (SIZE(1..4)) OF SearchSpace OPTIONAL, -- Need RsearchSpaceSIB1ID of the search space for SIB1 message. In the initial DL BWP of the UE′s PCell, the network sets this field to 0. If the field is absent, the UE does not receive SIB1 in this BWP. (see TS 38.213 [13], clause 10)SearchSpaceId OPTIONAL, -- Need SsearchSpaceOtherSystemInformationID of the Search space for other system information, i.e., SIB2 and beyond (see TS 38.213 [13], clause 10.1). If the field is absent, the UE does not receive other system information in this BWP.SearchSpaceId OPTIONAL, -- Need SpagingSearchSpaceID of the Search space for paging (see TS 38.213 [13], clause 10.1). If the field is absent, the UE does not receive paging in this BWP (see TS 38.213 [13], clause 10).SearchSpaceId OPTIONAL, -- Need Sra-SearchSpaceID of the Search space for random access procedure (see TS 38.213 [13], clause 10.1). If the field is absent, the UE does not receive RAR in this BWP.This field is mandatory present in the DL BWP(s) if the conditions described in TS 38.321 [3], clause 5.15 are met.SearchSpaceId OPTIONAL, -- Need S ..., [[firstPDCCH-MonitoringOccasionOfPOIndicates the first PDCCH monitoring occasion of each PO of the PF on this BWP, see TS 38.304 [20].CHOICE { sCS15KHZoneT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..139), sCS30KHZoneT-SCS15KHZhalfT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..279), sCS60KHZoneT-SCS30KHZhalfT-SCS15KHZquarterT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..559), sCS120KHZoneT-SCS60KHZhalfT-SCS30KHZquarterT-SCS15KHZoneEighthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..1119), sCS120KHZhalfT-SCS60KHZquarterT-SCS30KHZoneEighthT-SCS15KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..2239), sCS120KHZquarterT-SCS60KHZoneEighthT-SCS30KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..4479), sCS120KHZoneEighthT-SCS60KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..8959), sCS120KHZoneSixteenthT SEQUENCE (SIZE (1..maxPO-perPF)) OF INTEGER (0..17919) } OPTIONAL -- Cond OtherBWP ]], [[ commonSearchSpaceListExt-r16 SEQUENCE (SIZE(1..4)) OF SearchSpaceExt-r16 OPTIONAL -- Need R ]] } -- TAG-PDCCH-CONFIGCOMMON-STOP -- ASN1STOP
PDCCH-ConfigCommon field descriptions |
---|
commonControlResourceSet An additional common control resource set which may be configured and used for any common or UE-specific search space. If the network configures this field, it uses a ControlResourceSetId other than 0 for this ControlResourceSet. The network configures the commonControlResourceSet in SIB1 so that it is contained in the bandwidth of CORESET#0. |
commonSearchSpaceList, commonSearchSpaceListExt A list of additional common search spaces. If the network configures this field, it uses the SearchSpaceIds other than 0. If the field is included, it replaces any previous list, i.e. all the entries of the list are replaced and each of the SearchSpace entries is considered to be newly created and the conditions and Need codes for setup of the entry apply. If the network includes commonSearchSpaceListExt, it includes the same number of entries, and listed in the same order, as in commonSearchSpaceList. |
controlResourceSetZero Parameters of the common CORESET#0 which can be used in any common or UE-specific search spaces. The values are interpreted like the corresponding bits in MIBpdcch-ConfigSIB1. Even though this field is only configured in the initial BWP (BWP#0) controlResourceSetZero can be used in search spaces configured in other DL BWP(s) than the initial DL BWP if the conditions defined in TS 38.213 [13], clause 10 are satisfied. |
firstPDCCH-MonitoringOccasionOfPO Indicates the first PDCCH monitoring occasion of each PO of the PF on this BWP, see TS 38.304 [20]. |
pagingSearchSpace ID of the Search space for paging (see TS 38.213 [13], clause 10.1). If the field is absent, the UE does not receive paging in this BWP (see TS 38.213 [13], clause 10). |
ra-SearchSpace ID of the Search space for random access procedure (see TS 38.213 [13], clause 10.1). If the field is absent, the UE does not receive RAR in this BWP.This field is mandatory present in the DL BWP(s) if the conditions described in TS 38.321 [3], clause 5.15 are met. |
searchSpaceOtherSystemInformation ID of the Search space for other system information, i.e., SIB2 and beyond (see TS 38.213 [13], clause 10.1). If the field is absent, the UE does not receive other system information in this BWP. |
searchSpaceSIB1 ID of the search space for SIB1 message. In the initial DL BWP of the UE′s PCell, the network sets this field to 0. If the field is absent, the UE does not receive SIB1 in this BWP. (see TS 38.213 [13], clause 10) |
searchSpaceZero Parameters of the common SearchSpace#0. The values are interpreted like the corresponding bits in MIBpdcch-ConfigSIB1. Even though this field is only configured in the initial BWP (BWP#0), searchSpaceZero can be used in search spaces configured in other DL BWP(s) than the initial DL BWP if the conditions described in TS 38.213 [13], clause 10, are satisfied. |
Conditional Presence | Explanation |
---|---|
InitialBWP-Only | If SIB1 is broadcast the field is mandatory present in the PDCCH-ConfigCommon of the initial BWP (BWP#0) in ServingCellConfigCommon; it is absent in other BWPs and when sent in system information. If SIB1 is not broadcast and there is an SSB associated to the cell, the field is optionally present, Need M, in the PDCCH-ConfigCommon of the initial BWP (BWP#0) in ServingCellConfigCommon (still with the same setting for all UEs). In other cases, the field is absent. |
OtherBWP | This field is optionally present, Need R, if this BWP is not the initial DL BWP and pagingSearchSpace is configured in this BWP. Otherwise this field is absent. |
The IE PDCCH-ConfigSIB1 is used to configure CORESET#0 and search space#0.
-- ASN1START -- TAG-PDCCH-CONFIGSIB1-START PDCCH-ConfigSIB1 ::= SEQUENCE {controlResourceSetZeroDetermines a common ControlResourceSet (CORESET) with ID #0, see TS 38.213 [13], clause 13.ControlResourceSetZero,searchSpaceZeroDetermines a common search space with ID #0, see TS 38.213 [13], clause 13.SearchSpaceZero } -- TAG-PDCCH-CONFIGSIB1-STOP -- ASN1STOP
PDCCH-ConfigSIB1 field descriptions |
---|
controlResourceSetZero Determines a common ControlResourceSet (CORESET) with ID #0, see TS 38.213 [13], clause 13. |
searchSpaceZero Determines a common search space with ID #0, see TS 38.213 [13], clause 13. |
The IE PDCCH-ServingCellConfig is used to configure UE specific PDCCH parameters applicable across all bandwidth parts of a serving cell.
-- ASN1START -- TAG-PDCCH-SERVINGCELLCONFIG-START PDCCH-ServingCellConfig ::= SEQUENCE {slotFormatIndicatorConfiguration of Slot-Format-Indicators to be monitored in the correspondingly configured PDCCHs of this serving cell.SetupRelease { SlotFormatIndicator } OPTIONAL, -- Need M ..., [[availabilityIndicator-r16Use to configure monitoring a PDCCH for Availability Indicators (AI).SetupRelease {AvailabilityIndicator-r16} OPTIONAL, -- Need MsearchSpaceSwitchTimer-r16The value of the timer in slots for monitoring PDCCH in the active DL BWP of the serving cell before moving to the default search space group (see TS 38.213 [13], clause 10.4). For 15 kHz SCS, {1..20} are valid. For 30 kHz SCS, {1..40} are valid. For 60kHz SCS, {1..80} are valid. The network configures the same value for all serving cells in the same CellGroupForSwitch.INTEGER (1..80) OPTIONAL -- Need R ]] } -- TAG-PDCCH-SERVINGCELLCONFIG-STOP -- ASN1STOP
PDCCH-ServingCellConfig field descriptions |
---|
availabilityIndicator Use to configure monitoring a PDCCH for Availability Indicators (AI). |
searchSpaceSwitchTimer The value of the timer in slots for monitoring PDCCH in the active DL BWP of the serving cell before moving to the default search space group (see TS 38.213 [13], clause 10.4). For 15 kHz SCS, {1..20} are valid. For 30 kHz SCS, {1..40} are valid. For 60kHz SCS, {1..80} are valid. The network configures the same value for all serving cells in the same CellGroupForSwitch. |
slotFormatIndicator Configuration of Slot-Format-Indicators to be monitored in the correspondingly configured PDCCHs of this serving cell. |
The IE PDCP-Config is used to set the configurable PDCP parameters for signalling and data radio bearers.
-- ASN1START -- TAG-PDCP-CONFIG-START PDCP-Config ::= SEQUENCE { drb SEQUENCE {discardTimerValue in ms of discardTimer specified in TS 38.323 [5]. Value ms10 corresponds to 10 ms, value ms20 corresponds to 20 ms and so on. The value for this field cannot be changed in case of reconfiguration with sync, if the bearer is configured as DAPS bearer.ENUMERATED {ms10, ms20, ms30, ms40, ms50, ms60, ms75, ms100, ms150, ms200, ms250, ms300, ms500, ms750, ms1500, infinity} OPTIONAL, -- Cond Setuppdcp-SN-SizeULPDCP sequence number size for uplink, 12 or 18 bits, as specified in TS 38.323 [5]. For SRBs only the value len12bits is applicable. The value for this field cannot be changed in case of reconfiguration with sync, if the bearer is configured as DAPS bearer.ENUMERATED {len12bits, len18bits} OPTIONAL, -- Cond Setup2pdcp-SN-SizeDLPDCP sequence number size for downlink, 12 or 18 bits, as specified in TS 38.323 [5]. For SRBs only the value len12bits is applicable. The value for this field cannot be changed in case of reconfiguration with sync, if the bearer is configured as DAPS bearer.ENUMERATED {len12bits, len18bits} OPTIONAL, -- Cond Setup2headerCompressionIf rohc is configured, the UE shall apply the configured ROHC profile(s) in both uplink and downlink. If uplinkOnlyROHC is configured, the UE shall apply the configured ROHC profile(s) in uplink (there is no header compression in downlink). ROHC can be configured for any bearer type. ROHC and EHC can be both configured simultaneously for a DRB. The network reconfigures headerCompression only upon reconfiguration involving PDCP re-establishmentor involving PDCP entity reconfiguration to configure DAPS bearer(s), and without any drb-ContinueROHC. Network configures headerCompression to notUsed when outOfOrderDelivery is configured.CHOICE { notUsed NULL, rohc SEQUENCE {maxCIDIndicates the value of the MAX_CID parameter as specified in TS 38.323 [5]. The total value of MAX_CIDs across all bearers for the UE should be less than or equal to the value of maxNumberROHC-ContextSessions parameter as indicated by the UE.INTEGER (1..16383) DEFAULT 15, profiles SEQUENCE { profile0x0001 BOOLEAN, profile0x0002 BOOLEAN, profile0x0003 BOOLEAN, profile0x0004 BOOLEAN, profile0x0006 BOOLEAN, profile0x0101 BOOLEAN, profile0x0102 BOOLEAN, profile0x0103 BOOLEAN, profile0x0104 BOOLEAN },drb-ContinueROHCIndicates whether the PDCP entity continues or resets the ROHC header compression protocol during PDCP re-establishment, as specified in TS 38.323 [5]. This field is configured only in case of resuming an RRC connection or reconfiguration with sync, where the PDCP termination point is not changed and the fullConfig is not indicated. The network does not include the field if the bearer is configured as DAPS bearer.ENUMERATED { true } OPTIONAL -- Need N }, uplinkOnlyROHC SEQUENCE {maxCIDIndicates the value of the MAX_CID parameter as specified in TS 38.323 [5]. The total value of MAX_CIDs across all bearers for the UE should be less than or equal to the value of maxNumberROHC-ContextSessions parameter as indicated by the UE.INTEGER (1..16383) DEFAULT 15, profiles SEQUENCE { profile0x0006 BOOLEAN },drb-ContinueROHCIndicates whether the PDCP entity continues or resets the ROHC header compression protocol during PDCP re-establishment, as specified in TS 38.323 [5]. This field is configured only in case of resuming an RRC connection or reconfiguration with sync, where the PDCP termination point is not changed and the fullConfig is not indicated. The network does not include the field if the bearer is configured as DAPS bearer.ENUMERATED { true } OPTIONAL -- Need N }, ... },integrityProtectionIndicates whether or not integrity protection is configured for this radio bearer. The network configures all DRBs with the same PDU-session ID with same value for this field. The value for this field cannot be changed after the DRB is set up.ENUMERATED { enabled } OPTIONAL, -- Cond ConnectedTo5GC1statusReportRequiredFor AM DRBs and DAPS UM DRBs, indicates whether the DRB is configured to send a PDCP status report in the uplink, as specified in TS 38.323 [5]. For DAPS AM DRBs, it also indicates whether the DRB is configured to send a second PDCP status report in the uplink, as specified in TS 38.323 [5].ENUMERATED { true } OPTIONAL, -- Cond Rlc-AM-UMoutOfOrderDeliveryIndicates whether or not outOfOrderDelivery specified in TS 38.323 [5] is configured.This field should be either always present or always absent, after the radio bearer is established.ENUMERATED { true } OPTIONAL -- Need R } OPTIONAL, -- Cond DRBmoreThanOneRLCThis field configures UL data transmission when more than one RLC entity is associated with the PDCP entity. This field is not present if the bearer is configured as DAPS bearer.SEQUENCE {primaryPathIndicates the cell group ID and LCID of the primary RLC entity as specified in TS 38.323 [5], clause 5.2.1 for UL data transmission when more than one RLC entity is associated with the PDCP entity. In this version of the specification, only cell group ID corresponding to MCG is supported for SRBs, except when the UE is required to set the primaryPath to refer to the SCG as specified in clause 5.7.3b.4. In this case, if the network sends an RRCReconfiguration message (in NR-DC) or an EUTRA RRCConnectionReconfiguration message (in (NG)EN-DC) keeping SRB1 as split SRB, the network explicitly configures the primaryPath for the PDCP entity of SRB1 to refer to the MCG. The NW indicates cellGroup for split bearers using logical channels in different cell groups. The NW always indicates logicalChannel if CA based PDCP duplication is configured in the cell group indicated by cellGroup of this field.SEQUENCE { cellGroup CellGroupId OPTIONAL, -- Need R logicalChannel LogicalChannelIdentity OPTIONAL -- Need R },ul-DataSplitThresholdParameter specified in TS 38.323 [5]. Value b0 corresponds to 0 bytes, value b100 corresponds to 100 bytes, value b200 corresponds to 200 bytes, and so on. The network sets this field to infinity for UEs not supporting splitDRB-withUL-Both-MCG-SCG. If the field is absent when the split bearer is configured for the radio bearer first time, then the default value infinity is applied.UL-DataSplitThreshold OPTIONAL, -- Cond SplitBearerpdcp-DuplicationIndicates whether or not uplink duplication status at the time of receiving this IE is configured and activated as specified in TS 38.323 [5]. The presence of this field indicates that duplication is configured. PDCP duplication is not configured for CA packet duplication of LTE RLC bearer. The value of this field, when the field is present, indicates the state of the duplication at the time of receiving this IE. If set to true, duplication is activated. The value of this field is always true, when configured for a SRB. For PDCP entity with more than two associated RLC entities for UL transmission, this field is always present. If the field moreThanTwoRLC-DRB is present, the value of this field is ignored and the state of the duplication is indicated by duplicationState. For PDCP entity with more than two associated RLC entities, only NR RLC bearer is supported.BOOLEAN OPTIONAL -- Need R } OPTIONAL, -- Cond MoreThanOneRLCt-ReorderingValue in ms of t-Reordering specified in TS 38.323 [5]. Value ms0 corresponds to 0 ms, value ms20 corresponds to 20 ms, value ms40 corresponds to 40 ms, and so on. When the field is absent the UE applies the value infinity. The value for this field cannot be changed in case of reconfiguration with sync, if the bearer is configured as DAPS bearer.ENUMERATED { ms0, ms1, ms2, ms4, ms5, ms8, ms10, ms15, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms120, ms140, ms160, ms180, ms200, ms220, ms240, ms260, ms280, ms300, ms500, ms750, ms1000, ms1250, ms1500, ms1750, ms2000, ms2250, ms2500, ms2750, ms3000, spare28, spare27, spare26, spare25, spare24, spare23, spare22, spare21, spare20, spare19, spare18, spare17, spare16, spare15, spare14, spare13, spare12, spare11, spare10, spare09, spare08, spare07, spare06, spare05, spare04, spare03, spare02, spare01 } OPTIONAL, -- Need S ..., [[cipheringDisabledIf included, ciphering is disabled for this DRB regardless of which ciphering algorithm is configured for the SRB/DRBs. The field may only be included if the UE is connected to 5GC. Otherwise the field is absent. The network configures all DRBs with the same PDU-session ID with same value for this field. The value for this field cannot be changed after the DRB is set up.ENUMERATED {true} OPTIONAL -- Cond ConnectedTo5GC ]], [[discardTimerExt-r16Value in ms of discardTimer specified in TS 38.323 [5]. Value ms0dot5 corresponds to 0.5 ms, value ms1 corresponds to 1ms and so on. If this field is present, the field discardTimer is ignored and discardTimerExt is used instead.SetupRelease { DiscardTimerExt-r16 } OPTIONAL, -- Cond DRB2moreThanTwoRLC-DRB-r16This field configures UL data transmission when more than two RLC entities are associated with the PDCP entity for DRBs.SEQUENCE {splitSecondaryPath-r16Indicates the LCID of the split secondary RLC entity as specified in TS 38.323 [5] for fallback to split bearer operation when UL data transmission with more than two RLC entities is associated with the PDCP entity. This RLC entity belongs to a cell group that is different from the cell group indicated by cellGroup in the field primaryPath.LogicalChannelIdentity OPTIONAL, -- Cond SplitBearer2duplicationState-r16This field indicates the uplink PDCP duplication state for the associated RLC entities at the time of receiving this IE. If set to true, the PDCP duplication state is activated for the associated RLC entity. The index for the indication is determined by ascending order of logical channel ID of all RLC entities other than the primary RLC entityindicated by primaryPath in the order of MCG and SCG, as in clause 6.1.3.32 of TS 38.321 [3]. If the number of associated RLC entities other than the primary RLC entity is two, UE ignores the value in the largest index of this field. If the field is absent, the PDCP duplication states are deactivated for all associated RLC entities.SEQUENCE (SIZE (3)) OF BOOLEAN OPTIONAL -- Need S } OPTIONAL, -- Cond MoreThanTwoRLC-DRBethernetHeaderCompression-r16This fields configures Ethernet Header Compression. This field can only be configured for a bi-directional DRB. The network reconfigures ethernetHeaderCompression only upon reconfiguration involving PDCP re-establishment and with neither drb-ContinueEHC-DL nor drb-ContinueEHC-UL configured.SetupRelease { EthernetHeaderCompression-r16 } OPTIONAL -- Need M ]] } EthernetHeaderCompression-r16 ::= SEQUENCE {ehc-Common-r16Indicates the configurations that apply for both downlink and uplink.SEQUENCE {ehc-CID-Length-r16Indicates the length of the CID field for EHC packet. The value bits7 indicates the length is 7 bits, and the value bits15 indicates the length is 15 bits. Once the field ethernetHeaderCompression-r16 is configured for a DRB, the value of the field ehc-CID-Length for this DRB is not reconfigured to a different value.ENUMERATED { bits7, bits15 }, ... },ehc-Downlink-r16Indicates the configurations that apply for only downlink. If the field is configured, then Ethernet header compression is configured for downlink. Otherwise, it is not configured for downlink.SEQUENCE {drb-ContinueEHC-DL-r16Indicates whether the PDCP entity continues or resets the downlink EHC header compression protocol during PDCP re-establishment, as specified in TS 38.323 [5]. The field is configured only in case of resuming an RRC connection or reconfiguration with sync, where the PDCP termination point is not changed and the fullConfig is not indicated.ENUMERATED { true } OPTIONAL, -- Need N ... } OPTIONAL, -- Need Mehc-Uplink-r16Indicates the configurations that apply for only uplink. If the field is configured, then Ethernet header compression is configured for uplnik. Otherwise, it is not configured for uplink.SEQUENCE {maxCID-EHC-UL-r16Indicates the value of the MAX_CID_EHC_UL parameter as specified in TS 38.323 [5]. The total value of MAX_CID_EHC_UL across all bearers for the UE should be less than or equal to the value of maxNumberEHC-Contexts parameter as indicated by the UE.INTEGER (1..32767),drb-ContinueEHC-UL-r16Indicates whether the PDCP entity continues or resets the uplink EHC header compression protocol during PDCP re-establishment, as specified in TS 38.323 [5]. The field is configured only in case of resuming an RRC connection or reconfiguration with sync, where the PDCP termination point is not changed and the fullConfig is not indicated.ENUMERATED { true } OPTIONAL, -- Need N ... } OPTIONAL -- Need M } UL-DataSplitThreshold ::= ENUMERATED { b0, b100, b200, b400, b800, b1600, b3200, b6400, b12800, b25600, b51200, b102400, b204800, b409600, b819200, b1228800, b1638400, b2457600, b3276800, b4096000, b4915200, b5734400, b6553600, infinity, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} DiscardTimerExt-r16 ::= ENUMERATED {ms0dot5, ms1, ms2, ms4, ms6, ms8, spare2, spare1} -- TAG-PDCP-CONFIG-STOP -- ASN1STOP
PDCP-Config field descriptions |
---|
cipheringDisabled If included, ciphering is disabled for this DRB regardless of which ciphering algorithm is configured for the SRB/DRBs. The field may only be included if the UE is connected to 5GC. Otherwise the field is absent. The network configures all DRBs with the same PDU-session ID with same value for this field. The value for this field cannot be changed after the DRB is set up. |
discardTimer Value in ms of discardTimer specified in TS 38.323 [5]. Value ms10 corresponds to 10 ms, value ms20 corresponds to 20 ms and so on. The value for this field cannot be changed in case of reconfiguration with sync, if the bearer is configured as DAPS bearer. |
discardTimerExt Value in ms of discardTimer specified in TS 38.323 [5]. Value ms0dot5 corresponds to 0.5 ms, value ms1 corresponds to 1ms and so on. If this field is present, the field discardTimer is ignored and discardTimerExt is used instead. |
drb-ContinueROHC Indicates whether the PDCP entity continues or resets the ROHC header compression protocol during PDCP re-establishment, as specified in TS 38.323 [5]. This field is configured only in case of resuming an RRC connection or reconfiguration with sync, where the PDCP termination point is not changed and the fullConfig is not indicated. The network does not include the field if the bearer is configured as DAPS bearer. |
duplicationState This field indicates the uplink PDCP duplication state for the associated RLC entities at the time of receiving this IE. If set to true, the PDCP duplication state is activated for the associated RLC entity. The index for the indication is determined by ascending order of logical channel ID of all RLC entities other than the primary RLC entityindicated by primaryPath in the order of MCG and SCG, as in clause 6.1.3.32 of TS 38.321 [3]. If the number of associated RLC entities other than the primary RLC entity is two, UE ignores the value in the largest index of this field. If the field is absent, the PDCP duplication states are deactivated for all associated RLC entities. |
ethernetHeaderCompression This fields configures Ethernet Header Compression. This field can only be configured for a bi-directional DRB. The network reconfigures ethernetHeaderCompression only upon reconfiguration involving PDCP re-establishment and with neither drb-ContinueEHC-DL nor drb-ContinueEHC-UL configured. |
headerCompression If rohc is configured, the UE shall apply the configured ROHC profile(s) in both uplink and downlink. If uplinkOnlyROHC is configured, the UE shall apply the configured ROHC profile(s) in uplink (there is no header compression in downlink). ROHC can be configured for any bearer type. ROHC and EHC can be both configured simultaneously for a DRB. The network reconfigures headerCompression only upon reconfiguration involving PDCP re-establishmentor involving PDCP entity reconfiguration to configure DAPS bearer(s), and without any drb-ContinueROHC. Network configures headerCompression to notUsed when outOfOrderDelivery is configured. |
integrityProtection Indicates whether or not integrity protection is configured for this radio bearer. The network configures all DRBs with the same PDU-session ID with same value for this field. The value for this field cannot be changed after the DRB is set up. |
maxCID Indicates the value of the MAX_CID parameter as specified in TS 38.323 [5]. The total value of MAX_CIDs across all bearers for the UE should be less than or equal to the value of maxNumberROHC-ContextSessions parameter as indicated by the UE. |
moreThanOneRLC This field configures UL data transmission when more than one RLC entity is associated with the PDCP entity. This field is not present if the bearer is configured as DAPS bearer. |
moreThanTwoRLC-DRB This field configures UL data transmission when more than two RLC entities are associated with the PDCP entity for DRBs. |
outOfOrderDelivery Indicates whether or not outOfOrderDelivery specified in TS 38.323 [5] is configured.This field should be either always present or always absent, after the radio bearer is established. |
pdcp-Duplication Indicates whether or not uplink duplication status at the time of receiving this IE is configured and activated as specified in TS 38.323 [5]. The presence of this field indicates that duplication is configured. PDCP duplication is not configured for CA packet duplication of LTE RLC bearer. The value of this field, when the field is present, indicates the state of the duplication at the time of receiving this IE. If set to true, duplication is activated. The value of this field is always true, when configured for a SRB. For PDCP entity with more than two associated RLC entities for UL transmission, this field is always present. If the field moreThanTwoRLC-DRB is present, the value of this field is ignored and the state of the duplication is indicated by duplicationState. For PDCP entity with more than two associated RLC entities, only NR RLC bearer is supported. |
pdcp-SN-SizeDL PDCP sequence number size for downlink, 12 or 18 bits, as specified in TS 38.323 [5]. For SRBs only the value len12bits is applicable. The value for this field cannot be changed in case of reconfiguration with sync, if the bearer is configured as DAPS bearer. |
pdcp-SN-SizeUL PDCP sequence number size for uplink, 12 or 18 bits, as specified in TS 38.323 [5]. For SRBs only the value len12bits is applicable. The value for this field cannot be changed in case of reconfiguration with sync, if the bearer is configured as DAPS bearer. |
primaryPath Indicates the cell group ID and LCID of the primary RLC entity as specified in TS 38.323 [5], clause 5.2.1 for UL data transmission when more than one RLC entity is associated with the PDCP entity. In this version of the specification, only cell group ID corresponding to MCG is supported for SRBs, except when the UE is required to set the primaryPath to refer to the SCG as specified in clause 5.7.3b.4. In this case, if the network sends an RRCReconfiguration message (in NR-DC) or an EUTRA RRCConnectionReconfiguration message (in (NG)EN-DC) keeping SRB1 as split SRB, the network explicitly configures the primaryPath for the PDCP entity of SRB1 to refer to the MCG. The NW indicates cellGroup for split bearers using logical channels in different cell groups. The NW always indicates logicalChannel if CA based PDCP duplication is configured in the cell group indicated by cellGroup of this field. |
splitSecondaryPath Indicates the LCID of the split secondary RLC entity as specified in TS 38.323 [5] for fallback to split bearer operation when UL data transmission with more than two RLC entities is associated with the PDCP entity. This RLC entity belongs to a cell group that is different from the cell group indicated by cellGroup in the field primaryPath. |
statusReportRequired For AM DRBs and DAPS UM DRBs, indicates whether the DRB is configured to send a PDCP status report in the uplink, as specified in TS 38.323 [5]. For DAPS AM DRBs, it also indicates whether the DRB is configured to send a second PDCP status report in the uplink, as specified in TS 38.323 [5]. |
t-Reordering Value in ms of t-Reordering specified in TS 38.323 [5]. Value ms0 corresponds to 0 ms, value ms20 corresponds to 20 ms, value ms40 corresponds to 40 ms, and so on. When the field is absent the UE applies the value infinity. The value for this field cannot be changed in case of reconfiguration with sync, if the bearer is configured as DAPS bearer. |
ul-DataSplitThreshold Parameter specified in TS 38.323 [5]. Value b0 corresponds to 0 bytes, value b100 corresponds to 100 bytes, value b200 corresponds to 200 bytes, and so on. The network sets this field to infinity for UEs not supporting splitDRB-withUL-Both-MCG-SCG. If the field is absent when the split bearer is configured for the radio bearer first time, then the default value infinity is applied. |
EthernetHeaderCompression field descriptions |
---|
drb-ContinueEHC-DL Indicates whether the PDCP entity continues or resets the downlink EHC header compression protocol during PDCP re-establishment, as specified in TS 38.323 [5]. The field is configured only in case of resuming an RRC connection or reconfiguration with sync, where the PDCP termination point is not changed and the fullConfig is not indicated. |
drb-ContinueEHC-UL Indicates whether the PDCP entity continues or resets the uplink EHC header compression protocol during PDCP re-establishment, as specified in TS 38.323 [5]. The field is configured only in case of resuming an RRC connection or reconfiguration with sync, where the PDCP termination point is not changed and the fullConfig is not indicated. |
ehc-CID-Length Indicates the length of the CID field for EHC packet. The value bits7 indicates the length is 7 bits, and the value bits15 indicates the length is 15 bits. Once the field ethernetHeaderCompression-r16 is configured for a DRB, the value of the field ehc-CID-Length for this DRB is not reconfigured to a different value. |
ehc-Common Indicates the configurations that apply for both downlink and uplink. |
ehc-Downlink Indicates the configurations that apply for only downlink. If the field is configured, then Ethernet header compression is configured for downlink. Otherwise, it is not configured for downlink. |
ehc-Uplink Indicates the configurations that apply for only uplink. If the field is configured, then Ethernet header compression is configured for uplnik. Otherwise, it is not configured for uplink. |
maxCID-EHC-UL Indicates the value of the MAX_CID_EHC_UL parameter as specified in TS 38.323 [5]. The total value of MAX_CID_EHC_UL across all bearers for the UE should be less than or equal to the value of maxNumberEHC-Contexts parameter as indicated by the UE. |
Conditional presence | Explanation |
---|---|
DRB | This field is mandatory present when the corresponding DRB is being set up, absent for SRBs. Otherwise this field is optionally present, need M. |
DRB2 | This field is optionally present in case of DRB, need M. Otherwise, it is absent for SRBs. |
MoreThanOneRLC | This field is mandatory present upon RRC reconfiguration with setup of a PDCP entity for a radio bearer with more than one associated logical channel and upon RRC reconfiguration with the association of additional logical channels to the PDCP entity. The field is also mandatory present in case the field moreThanTwoRLC-DRB is included in PDCP-Config. Upon RRC reconfiguration when a PDCP entity is associated with multiple logical channels, this field is optionally present need M. Otherwise, this field is absent. Need R. |
MoreThanTwoRLC-DRB | For SRBs, this field is absent. For DRBs, this field is mandatory present upon RRC reconfiguration with setup of a PDCP entity for a radio bearer with more than two associated logical channels and upon RRC reconfiguration with the association of one or more additional logical channel(s) to the PDCP entity so that the PDCP entity has more than two associated logical channels. Upon RRC reconfiguration when a PDCP entity is associated with more than two logical channels, this field is optionally present, Need M. Otherwise, the field is absent, Need R. |
Rlc-AM-UM | For RLC UM (if the UE supports DAPS handover) or RLC AM, the field is optionally present, need R. Otherwise, the field is absent. |
Setup | The field is mandatory present in case of radio bearer setup. Otherwise the field is optionally present, need M. |
SplitBearer | The field is absent for SRBs. Otherwise, the field is optional present, need M, in case of radio bearer with more than one associated RLC mapped to different cell groups. |
SplitBearer2 | The field is mandatory present, in case of a split bearer. Otherwise the field is absent. |
ConnectedTo5GC | The field is optionally present, need R, if the UE is connected to 5GC. Otherwise the field is absent. |
ConnectedTo5GC1 | The field is optionally present, need R, if the UE is connected to NR/5GC. Otherwise the field is absent. |
Setup2 | This field is mandatory present in case for radio bearer setup for RLC-AM and RLC-UM. Otherwise, this field is absent, Need M. |
The PDSCH-Config IE is used to configure the UE specific PDSCH parameters.
-- ASN1START -- TAG-PDSCH-CONFIG-START PDSCH-Config ::= SEQUENCE { dataScramblingIdentityPDSCH INTEGER (0..1023) OPTIONAL, -- Need S dmrs-DownlinkForPDSCH-MappingTypeA SetupRelease { DMRS-DownlinkConfig } OPTIONAL, -- Need M dmrs-DownlinkForPDSCH-MappingTypeB SetupRelease { DMRS-DownlinkConfig } OPTIONAL, -- Need Mtci-StatesToAddModListA list of Transmission Configuration Indicator (TCI) states indicating a transmission configuration which includes QCL-relationships between the DL RSs in one RS set and the PDSCH DMRS ports (see TS 38.214 [19], clause 5.1.5).SEQUENCE (SIZE(1..maxNrofTCI-States)) OF TCI-State OPTIONAL, -- Need N tci-StatesToReleaseList SEQUENCE (SIZE(1..maxNrofTCI-States)) OF TCI-StateId OPTIONAL, -- Need N vrb-ToPRB-Interleaver ENUMERATED {n2, n4} OPTIONAL, -- Need S resourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch}, pdsch-TimeDomainAllocationList SetupRelease { PDSCH-TimeDomainResourceAllocationList } OPTIONAL, -- Need Mpdsch-AggregationFactorNumber of repetitions for data (see TS 38.214 [19], clause 5.1.2.1). When the field is absent the UE applies the value 1.ENUMERATED { n2, n4, n8 } OPTIONAL, -- Need SrateMatchPatternToAddModListResources patterns which the UE should rate match PDSCH around. The UE rate matches around the union of all resources indicated in the rate match patterns (see TS 38.214 [19], clause 5.1.4.1).SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPattern OPTIONAL, -- Need N rateMatchPatternToReleaseList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPatternId OPTIONAL, -- Need N rateMatchPatternGroup1 RateMatchPatternGroup OPTIONAL, -- Need R rateMatchPatternGroup2 RateMatchPatternGroup OPTIONAL, -- Need Rrbg-SizeSelection between config 1 and config 2 for RBG size for PDSCH. The UE ignores this field if resourceAllocation is set to resourceAllocationType1 (see TS 38.214 [19], clause 5.1.2.2.1).ENUMERATED {config1, config2}, mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need SmaxNrofCodeWordsScheduledByDCIMaximum number of code words that a single DCI may schedule. This changes the number of MCS/RV/NDI bits in the DCI message from 1 to 2.ENUMERATED {n1, n2} OPTIONAL, -- Need R prb-BundlingType CHOICE { staticBundling SEQUENCE { bundleSize ENUMERATED { n4, wideband } OPTIONAL -- Need S }, dynamicBundling SEQUENCE { bundleSizeSet1 ENUMERATED { n4, wideband, n2-wideband, n4-wideband } OPTIONAL, -- Need S bundleSizeSet2 ENUMERATED { n4, wideband } OPTIONAL -- Need S } },zp-CSI-RS-ResourceToAddModListA list of Zero-Power (ZP) CSI-RS resources used for PDSCH rate-matching. Each resource in this list may be referred to from only one type of resource set, i.e., aperiodic, semi-persistent or periodic (see TS 38.214 [19]).SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-Resources)) OF ZP-CSI-RS-Resource OPTIONAL, -- Need N zp-CSI-RS-ResourceToReleaseList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-Resources)) OF ZP-CSI-RS-ResourceId OPTIONAL, -- Need N aperiodic-ZP-CSI-RS-ResourceSetsToAddModList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSet OPTIONAL, -- Need N aperiodic-ZP-CSI-RS-ResourceSetsToReleaseList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSetId OPTIONAL, -- Need Nsp-ZP-CSI-RS-ResourceSetsToAddModListAddMod/Release lists for configuring semi-persistent zero-power CSI-RS resource sets. Each set contains a ZP-CSI-RS-ResourceSetId and the IDs of one or more ZP-CSI-RS-Resources (the actual resources are defined in the zp-CSI-RS-ResourceToAddModList) (see TS 38.214 [19], clause 5.1.4.2).SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSet OPTIONAL, -- Need N sp-ZP-CSI-RS-ResourceSetsToReleaseList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSetId OPTIONAL, -- Need Np-ZP-CSI-RS-ResourceSetA set of periodically occurring ZP-CSI-RS-Resources (the actual resources are defined in the zp-CSI-RS-ResourceToAddModList). The network uses the ZP-CSI-RS-ResourceSetId=0 for this set.SetupRelease { ZP-CSI-RS-ResourceSet } OPTIONAL, -- Need M ..., [[maxMIMO-Layers-r16Indicates the maximum number of MIMO layers to be used for PDSCH in this DL BWP. If not configured, the UE uses the maxMIMO-Layers configuration in IE PDSCH-ServingCellConfig of the serving cell to which this BWP belongs, when the UE operates in this BWP. The value of maxMIMO-Layers for a DL BWP shall be smaller than or equal to the value of maxMIMO-Layers configured in IE PDSCH-ServingCellConfig of the serving cell to which this BWP belongs.SetupRelease { MaxMIMO-LayersDL-r16 } OPTIONAL, -- Need MminimumSchedulingOffsetK0-r16List of minimum K0 values.Minimum K0 parameter denotes minimum applicable value(s) for the TDRA table for PDSCH and for A-CSI RS triggering Offset(s) (see TS 38.214 [19], clause 5.3.1).SetupRelease { MinSchedulingOffsetK0-Values-r16 } OPTIONAL, -- Need M -- Start of the parameters for DCI format 1_2 introduced in V16.1.0antennaPortsFieldPresenceDCI-1-2-r16Configure the presence of "Antenna ports" field in DCI format 1_2. When the field is configured, then the "Antenna ports" field is present in DCI format 1_2. Otherwise, the field size is set to 0 for DCI format 1_2 (See TS 38.212 [17], clause 7.3.1.1.3). If neither dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2 nor dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2 is configured, this field is absent.ENUMERATED {enabled} OPTIONAL, -- Need S aperiodicZP-CSI-RS-ResourceSetsToAddModListDCI-1-2-r16 SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSet OPTIONAL, -- Need N aperiodicZP-CSI-RS-ResourceSetsToReleaseListDCI-1-2-r16 SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSetId OPTIONAL, -- Need N dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2-r16 SetupRelease { DMRS-DownlinkConfig } OPTIONAL, -- Need M dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2-r16 SetupRelease { DMRS-DownlinkConfig } OPTIONAL, -- Need M dmrs-SequenceInitializationDCI-1-2-r16 ENUMERATED {enabled} OPTIONAL, -- Need Sharq-ProcessNumberSizeDCI-1-2-r16Configure the number of bits for the field "HARQ process number" in DCI format 1_2 (see TS 38.212 [17], clause 7.3.1).INTEGER (0..4) OPTIONAL, -- Need R mcs-TableDCI-1-2-r16 ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need SnumberOfBitsForRV-DCI-1-2-r16Configures the number of bits for "Redundancy version" in the DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.214 [19], clause 5.1.2.1).INTEGER (0..2) OPTIONAL, -- Need R pdsch-TimeDomainAllocationListDCI-1-2-r16 SetupRelease { PDSCH-TimeDomainResourceAllocationList-r16 } OPTIONAL, -- Need M prb-BundlingTypeDCI-1-2-r16 CHOICE { staticBundling-r16 SEQUENCE { bundleSize-r16 ENUMERATED { n4, wideband } OPTIONAL -- Need S }, dynamicBundling-r16 SEQUENCE { bundleSizeSet1-r16 ENUMERATED { n4, wideband, n2-wideband, n4-wideband } OPTIONAL, -- Need S bundleSizeSet2-r16 ENUMERATED { n4, wideband } OPTIONAL -- Need S } } OPTIONAL, -- Need R priorityIndicatorDCI-1-2-r16 ENUMERATED {enabled} OPTIONAL, -- Need S rateMatchPatternGroup1DCI-1-2-r16 RateMatchPatternGroup OPTIONAL, -- Need R rateMatchPatternGroup2DCI-1-2-r16 RateMatchPatternGroup OPTIONAL, -- Need RresourceAllocationType1GranularityDCI-1-2-r16Configure the scheduling granularity applicable for both the starting point and length indication for resource allocation type 1 in DCI format 1_2. If this field is absent, the granularity is 1 PRB (see TS 38.214 [19], clause 5.1.2.2.2).ENUMERATED {n2,n4,n8,n16} OPTIONAL, -- Need S vrb-ToPRB-InterleaverDCI-1-2-r16 ENUMERATED {n2, n4} OPTIONAL, -- Need SreferenceOfSLIVDCI-1-2-r16Enable using the starting symbol of the PDCCH monitoring occasion in which the DL assignment is detected as the reference of the SLIV for DCI format 1_2. When the RRC parameter enables the utilization of the new reference, the new reference is applied for TDRA entries with K0=0. For other entries (if any) in the same TDRA table, the reference is slot boundary as in Rel-15. PDSCH mapping type A is not supported with the new reference. The new reference of SLIV is not configured for a serving cell configured to be scheduled by cross-carrier scheduling on a scheduling cell with different numerology (see TS 38.212 [17] clause 7.3.1 and TS 38.214 [19] clause 5.1.2.1).ENUMERATED {enabled} OPTIONAL, -- Need S resourceAllocationDCI-1-2-r16 ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch} OPTIONAL, -- Need M -- End of the parameters for DCI format 1_2 introduced in V16.1.0 priorityIndicatorDCI-1-1-r16 ENUMERATED {enabled} OPTIONAL, -- Need S dataScramblingIdentityPDSCH2-r16 INTEGER (0..1023) OPTIONAL, -- Need R pdsch-TimeDomainAllocationList-r16 SetupRelease { PDSCH-TimeDomainResourceAllocationList-r16 } OPTIONAL, -- Need MrepetitionSchemeConfig-r16Configure the UE with repetition schemes. The network does not configure repetitionSchemeConfig-r16 and repetitionSchemeConfig-v1630 simultaneously to setup in the same PDSCH-Config.SetupRelease { RepetitionSchemeConfig-r16} OPTIONAL -- Need M ]], [[ repetitionSchemeConfig-v1630 SetupRelease { RepetitionSchemeConfig-v1630} OPTIONAL -- Need M ]] } RateMatchPatternGroup ::= SEQUENCE (SIZE (1..maxNrofRateMatchPatternsPerGroup)) OF CHOICE { cellLevel RateMatchPatternId, bwpLevel RateMatchPatternId } MinSchedulingOffsetK0-Values-r16 ::= SEQUENCE (SIZE (1..maxNrOfMinSchedulingOffsetValues-r16)) OF INTEGER (0..maxK0-SchedulingOffset-r16) MaxMIMO-LayersDL-r16 ::= INTEGER (1..8) -- TAG-PDSCH-CONFIG-STOP -- ASN1STOP
PDSCH-Config field descriptions |
---|
antennaPortsFieldPresenceDCI-1-2 Configure the presence of "Antenna ports" field in DCI format 1_2. When the field is configured, then the "Antenna ports" field is present in DCI format 1_2. Otherwise, the field size is set to 0 for DCI format 1_2 (See TS 38.212 [17], clause 7.3.1.1.3). If neither dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2 nor dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2 is configured, this field is absent. |
aperiodic-ZP-CSI-RS-ResourceSetsToAddModList, aperiodic-ZP-CSI-RS-ResourceSetsToAddModListDCI-1-2 AddMod/Release lists for configuring aperiodically triggered zero-power CSI-RS resource sets. Each set contains a ZP-CSI-RS-ResourceSetId and the IDs of one or more ZP-CSI-RS-Resources (the actual resources are defined in the zp-CSI-RS-ResourceToAddModList). The network configures the UE with at most 3 aperiodic ZP-CSI-RS-ResourceSets and it uses only the ZP-CSI-RS-ResourceSetId 1 to 3. The network triggers a set by indicating its ZP-CSI-RS-ResourceSetId in the DCI payload. The DCI codepoint '01' triggers the resource set with ZP-CSI-RS-ResourceSetId 1, the DCI codepoint '10' triggers the resource set with ZP-CSI-RS-ResourceSetId 2, and the DCI codepoint '11' triggers the resource set with ZP-CSI-RS-ResourceSetId 3 (see TS 38.214 [19], clause 5.1.4.2). The field aperiodic-ZP-CSI-RS-ResourceSetsToAddModList applies to DCI format 1_1 and the field aperiodic-ZP-CSI-RS-ResourceSetsToAddModListDCI-1-2applies to DCI format 1_2 (see TS 38.214 [19], clause 5.1.4.2 and TS 38.212 [17] clause 7.3.1). |
dataScramblingIdentityPDSCH, dataScramblingIdentityPDSCH2 Identifier(s) used to initialize data scrambling (c_init) for PDSCH as specified in TS 38.211 [16], clause 7.3.1.1.The dataScramblingIdentityPDSCH2 is configured if coresetPoolIndex is configured with 1 for at least one CORESET in the same BWP. |
dmrs-DownlinkForPDSCH-MappingTypeA, dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2 DMRS configuration for PDSCH transmissions using PDSCH mapping type A (chosen dynamically via PDSCH-TimeDomainResourceAllocation). Only the fields dmrs-Type, dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B. The field dmrs-DownlinkForPDSCH-MappingTypeA applies to DCI format 1_1 and the field dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1). |
dmrs-DownlinkForPDSCH-MappingTypeB, dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2 DMRS configuration for PDSCH transmissions using PDSCH mapping type B (chosen dynamically via PDSCH-TimeDomainResourceAllocation). Only the fields dmrs-Type, dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B. The field dmrs-DownlinkForPDSCH-MappingTypeB applies to DCI format 1_1 and the field dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1). |
dmrs-SequenceInitializationDCI-1_2 Configure whether the field "DMRS Sequence Initialization" is present or not in DCI format 1_2 If the field is absent, then the UE applies the value of 0 bit for the field "DMRS Sequence Initialization" in DCI format 1_2. If the field is present, then the UE applies the value of 1 bit as in DCI format 1_2 (see TS 38.212 [17], clause 7.3.1). |
harq-ProcessNumberSizeDCI-1-2 Configure the number of bits for the field "HARQ process number" in DCI format 1_2 (see TS 38.212 [17], clause 7.3.1). |
maxMIMO-Layers Indicates the maximum number of MIMO layers to be used for PDSCH in this DL BWP. If not configured, the UE uses the maxMIMO-Layers configuration in IE PDSCH-ServingCellConfig of the serving cell to which this BWP belongs, when the UE operates in this BWP. The value of maxMIMO-Layers for a DL BWP shall be smaller than or equal to the value of maxMIMO-Layers configured in IE PDSCH-ServingCellConfig of the serving cell to which this BWP belongs. |
maxNrofCodeWordsScheduledByDCI Maximum number of code words that a single DCI may schedule. This changes the number of MCS/RV/NDI bits in the DCI message from 1 to 2. |
mcs-Table, mcs-TableDCI-1-2 Indicates which MCS table the UE shall use for PDSCH. (see TS 38.214 [19], clause 5.1.3.1). If the field is absent the UE applies the value 64QAM. The field mcs-Table applies to DCI format 1_0 and DCI format 1_1, and the field mcs-TableDCI-1-2applies to DCI format 1_2 (see TS 38.214 [19], clause 5.1.3.1). |
minimumSchedulingOffsetK0 List of minimum K0 values.Minimum K0 parameter denotes minimum applicable value(s) for the TDRA table for PDSCH and for A-CSI RS triggering Offset(s) (see TS 38.214 [19], clause 5.3.1). |
numberOfBitsForRV-DCI-1-2 Configures the number of bits for "Redundancy version" in the DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.214 [19], clause 5.1.2.1). |
pdsch-AggregationFactor Number of repetitions for data (see TS 38.214 [19], clause 5.1.2.1). When the field is absent the UE applies the value 1. |
pdsch-TimeDomainAllocationList, pdsch-TimeDomainAllocationListDCI-1-2 List of time-domain configurations for timing of DL assignment to DL data. The field pdsch-TimeDomainAllocationList (with or without suffix) applies to DCI format 1_0 and DCI format 1_1 (see table 5.1.2.1.1-1 in TS 38.214 [19]), and if the field pdsch-TimeDomainAllocationListDCI-1-2 is not configured, to DCI format 1_2. If the field pdsch-TimeDomainAllocationListDCI-1-2is configured, it applies to DCI format 1_2 (see table 5.1.2.1.1-1A in TS 38.214 [19]). The network does not configure the pdsch-TimeDomainAllocationList-r16 simultaneously with the pdsch-TimeDomainAllocationList (without suffix) in the same PDSCH-Config. |
prb-BundlingType,prb-BundlingTypeDCI-1-2 Indicates the PRB bundle type and bundle size(s) (see TS 38.214 [19], clause 5.1.2.3). If dynamic is chosen, the actual bundleSizeSet1 or bundleSizeSet2 to use is indicated via DCI. Constraints on bundleSize(Set) setting depending on vrb-ToPRB-Interleaver and rbg-Size settings are described in TS 38.214 [19], clause 5.1.2.3. If a bundleSize(Set) value is absent, the UE applies the value n2. The field prb-BundlingType applies to DCI format 1_1, and the field prb-BundlingTypeDCI-1-2applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.214 [19], clause 5.1.2.3). |
priorityIndicatorDCI-1-1, priorityIndicatorDCI-1-2 Configure the presence of "priority indicator" in DCI format 1_1/1_2. When the field is absent in the IE, then 0 bit for "priority indicator" in DCI format 1_1/1_2. The field priorityIndicatorDCI-1-1 applies to DCI format 1_1 and the field priorityIndicatorDCI-1-2applies to DCI format 1_2, respectively (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13] clause 9). |
p-ZP-CSI-RS-ResourceSet A set of periodically occurring ZP-CSI-RS-Resources (the actual resources are defined in the zp-CSI-RS-ResourceToAddModList). The network uses the ZP-CSI-RS-ResourceSetId=0 for this set. |
rateMatchPatternGroup1, rateMatchPatternGroup1DCI-1-2 The IDs of a first group of RateMatchPatterns defined in PDSCH-Config->rateMatchPatternToAddModList (BWP level) or in ServingCellConfig ->rateMatchPatternToAddModList (cell level). These patterns can be activated dynamically by DCI (see TS 38.214 [19], clause 5.1.4.1). The field rateMatchPatternGroup1 applies to DCI format 1_1, and the field rateMatchPatternGroup1DCI-1-2applies to DCI format 1_2 (see TS 38.214 [19], clause 5.1.4.1). |
rateMatchPatternGroup2, rateMatchPatternGroup2DCI-1-2 The IDs of a second group of RateMatchPatterns defined in PDSCH-Config->rateMatchPatternToAddModList (BWP level) or in ServingCellConfig ->rateMatchPatternToAddModList (cell level). These patterns can be activated dynamically by DCI (see TS 38.214 [19], clause 5.1.4.1). The field rateMatchPatternGroup2 applies to DCI format 1_1, and the field rateMatchPatternGroup2DCI-1-2applies to DCI format 1_2 (see TS 38.214 [19], clause 5.1.4.1). |
rateMatchPatternToAddModList Resources patterns which the UE should rate match PDSCH around. The UE rate matches around the union of all resources indicated in the rate match patterns (see TS 38.214 [19], clause 5.1.4.1). |
rbg-Size Selection between config 1 and config 2 for RBG size for PDSCH. The UE ignores this field if resourceAllocation is set to resourceAllocationType1 (see TS 38.214 [19], clause 5.1.2.2.1). |
referenceOfSLIVDCI-1-2 Enable using the starting symbol of the PDCCH monitoring occasion in which the DL assignment is detected as the reference of the SLIV for DCI format 1_2. When the RRC parameter enables the utilization of the new reference, the new reference is applied for TDRA entries with K0=0. For other entries (if any) in the same TDRA table, the reference is slot boundary as in Rel-15. PDSCH mapping type A is not supported with the new reference. The new reference of SLIV is not configured for a serving cell configured to be scheduled by cross-carrier scheduling on a scheduling cell with different numerology (see TS 38.212 [17] clause 7.3.1 and TS 38.214 [19] clause 5.1.2.1). |
repetitionSchemeConfig Configure the UE with repetition schemes. The network does not configure repetitionSchemeConfig-r16 and repetitionSchemeConfig-v1630 simultaneously to setup in the same PDSCH-Config. |
resourceAllocation, resourceAllocationDCI-1-2 Configuration of resource allocation type 0 and resource allocation type 1 for non-fallback DCI (see TS 38.214 [19], clause 5.1.2.2). The field resourceAllocation applies to DCI format 1_1, and the field resourceAllocationDCI-1-2 applies to DCI format 1_2 (see TS 38.214 [19], clause 5.1.2.2). |
resourceAllocationType1GranularityDCI-1-2 Configure the scheduling granularity applicable for both the starting point and length indication for resource allocation type 1 in DCI format 1_2. If this field is absent, the granularity is 1 PRB (see TS 38.214 [19], clause 5.1.2.2.2). |
sp-ZP-CSI-RS-ResourceSetsToAddModList AddMod/Release lists for configuring semi-persistent zero-power CSI-RS resource sets. Each set contains a ZP-CSI-RS-ResourceSetId and the IDs of one or more ZP-CSI-RS-Resources (the actual resources are defined in the zp-CSI-RS-ResourceToAddModList) (see TS 38.214 [19], clause 5.1.4.2). |
tci-StatesToAddModList A list of Transmission Configuration Indicator (TCI) states indicating a transmission configuration which includes QCL-relationships between the DL RSs in one RS set and the PDSCH DMRS ports (see TS 38.214 [19], clause 5.1.5). |
vrb-ToPRB-Interleaver, vrb-ToPRB-InterleaverDCI-1-2 Interleaving unit configurable between 2 and 4 PRBs (see TS 38.211 [16], clause 7.3.1.6). When the field is absent, the UE performs non-interleaved VRB-to-PRB mapping. |
zp-CSI-RS-ResourceToAddModList A list of Zero-Power (ZP) CSI-RS resources used for PDSCH rate-matching. Each resource in this list may be referred to from only one type of resource set, i.e., aperiodic, semi-persistent or periodic (see TS 38.214 [19]). |
The IE PDSCH-ConfigCommon is used to configure cell specific PDSCH parameters.
-- ASN1START -- TAG-PDSCH-CONFIGCOMMON-START PDSCH-ConfigCommon ::= SEQUENCE {pdsch-TimeDomainAllocationListList of time-domain configurations for timing of DL assignment to DL data (see table 5.1.2.1.1-1 in TS 38.214 [19]).PDSCH-TimeDomainResourceAllocationList OPTIONAL, -- Need R ... } -- TAG-PDSCH-CONFIGCOMMON-STOP -- ASN1STOP
PDSCH-ConfigCommon field descriptions |
---|
pdsch-TimeDomainAllocationList List of time-domain configurations for timing of DL assignment to DL data (see table 5.1.2.1.1-1 in TS 38.214 [19]). |
The IE PDSCH-ServingCellConfig is used to configure UE specific PDSCH parameters that are common across the UE's BWPs of one serving cell.
-- ASN1START -- TAG-PDSCH-SERVINGCELLCONFIG-START PDSCH-ServingCellConfig ::= SEQUENCE {codeBlockGroupTransmissionEnables and configures code-block-group (CBG) based transmission (see TS 38.213 [13], clause 9.1.1).Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group.SetupRelease { PDSCH-CodeBlockGroupTransmission } OPTIONAL, -- Need MxOverheadAccounts for overhead from CSI-RS, CORESET, etc. If the field is absent, the UE applies value xOh0 (see TS 38.214 [19], clause 5.1.3.2).ENUMERATED { xOh6, xOh12, xOh18 } OPTIONAL, -- Need SnrofHARQ-ProcessesForPDSCHThe number of HARQ processes to be used on the PDSCH of a serving cell. Value n2 corresponds to 2 HARQ processes, value n4 to 4 HARQ processes, and so on. If the field is absent, the UE uses 8 HARQ processes (see TS 38.214 [19], clause 5.1).ENUMERATED {n2, n4, n6, n10, n12, n16} OPTIONAL, -- Need Spucch-CellThe ID of the serving cell (of the same cell group) to use for PUCCH. If the field is absent, the UE sends the HARQ feedback on the PUCCH of the SpCell of this cell group, or on this serving cell if it is a PUCCH SCell.ServCellIndex OPTIONAL, -- Cond SCellAddOnly ..., [[maxMIMO-LayersIndicates the maximum number of MIMO layers to be used for PDSCH in all BWPs of this serving cell. (see TS 38.212 [17], clause 5.4.2.1).INTEGER (1..8) OPTIONAL, -- Need MprocessingType2EnabledEnables configuration of advanced processing time capability 2 for PDSCH (see 38.214 [19], clause 5.3).BOOLEAN OPTIONAL -- Need M ]], [[pdsch-CodeBlockGroupTransmissionList-r16A list of configurations for up to two simultaneously constructed HARQ-ACK codebooks (see TS 38.213 [13], clause 9.3).SetupRelease { PDSCH-CodeBlockGroupTransmissionList-r16 } OPTIONAL -- Need M ]] } PDSCH-CodeBlockGroupTransmission ::= SEQUENCE {maxCodeBlockGroupsPerTransportBlockMaximum number of code-block-groups (CBGs) per TB. In case of multiple CW, the maximum CBG is 4 (see TS 38.213 [13], clause 9.1.1).ENUMERATED {n2, n4, n6, n8},codeBlockGroupFlushIndicatorIndicates whether CBGFI for CBG based (re)transmission in DL is enabled (true). (see TS 38.212 [17], clause 7.3.1.2.2).BOOLEAN, ... } PDSCH-CodeBlockGroupTransmissionList-r16 ::= SEQUENCE (SIZE (1..2)) OF PDSCH-CodeBlockGroupTransmission -- TAG-PDSCH-SERVINGCELLCONFIG-STOP -- ASN1STOP
PDSCH-CodeBlockGroupTransmission field descriptions |
---|
codeBlockGroupFlushIndicator Indicates whether CBGFI for CBG based (re)transmission in DL is enabled (true). (see TS 38.212 [17], clause 7.3.1.2.2). |
maxCodeBlockGroupsPerTransportBlock Maximum number of code-block-groups (CBGs) per TB. In case of multiple CW, the maximum CBG is 4 (see TS 38.213 [13], clause 9.1.1). |
PDSCH-ServingCellConfig field descriptions |
---|
codeBlockGroupTransmission Enables and configures code-block-group (CBG) based transmission (see TS 38.213 [13], clause 9.1.1).Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group. |
maxMIMO-Layers Indicates the maximum number of MIMO layers to be used for PDSCH in all BWPs of this serving cell. (see TS 38.212 [17], clause 5.4.2.1). |
nrofHARQ-ProcessesForPDSCH The number of HARQ processes to be used on the PDSCH of a serving cell. Value n2 corresponds to 2 HARQ processes, value n4 to 4 HARQ processes, and so on. If the field is absent, the UE uses 8 HARQ processes (see TS 38.214 [19], clause 5.1). |
pdsch-CodeBlockGroupTransmissionList A list of configurations for up to two simultaneously constructed HARQ-ACK codebooks (see TS 38.213 [13], clause 9.3). |
processingType2Enabled Enables configuration of advanced processing time capability 2 for PDSCH (see 38.214 [19], clause 5.3). |
pucch-Cell The ID of the serving cell (of the same cell group) to use for PUCCH. If the field is absent, the UE sends the HARQ feedback on the PUCCH of the SpCell of this cell group, or on this serving cell if it is a PUCCH SCell. |
xOverhead Accounts for overhead from CSI-RS, CORESET, etc. If the field is absent, the UE applies value xOh0 (see TS 38.214 [19], clause 5.1.3.2). |
Conditional Presence | Explanation |
---|---|
SCellAddOnly | It is optionally present, Need S, for (non-PUCCH) SCells when adding a new SCell. The field is absent, Need M, when reconfiguring SCells. The field is also absent for the SpCells as well as for a PUCCH SCell. |
The IE PDSCH-TimeDomainResourceAllocation is used to configure a time domain relation between PDCCH and PDSCH. The PDSCH-TimeDomainResourceAllocationList contains one or more of such PDSCH-TimeDomainResourceAllocations. The network indicates in the DL assignment which of the configured time domain allocations the UE shall apply for that DL assignment. The UE determines the bit width of the DCI field based on the number of entries in the PDSCH-TimeDomainResourceAllocationList. Value 0 in the DCI field refers to the first element in this list, value 1 in the DCI field refers to the second element in this list, and so on.
-- ASN1START -- TAG-PDSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-START PDSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-TimeDomainResourceAllocation PDSCH-TimeDomainResourceAllocation ::= SEQUENCE {k0Slot offset between DCI and its scheduled PDSCH (see TS 38.214 [19], clause 5.1.2.1) When the field is absent the UE applies the value 0.INTEGER(0..32) OPTIONAL, -- Need SmappingTypePDSCH mapping type. (see TS 38.214 [19], clause 5.3).ENUMERATED {typeA, typeB},startSymbolAndLengthAn index giving valid combinations of start symbol and length (jointly encoded) as start and length indicator (SLIV). The network configures the field so that the allocation does not cross the slot boundary (see TS 38.214 [19], clause 5.1.2.1).INTEGER (0..127) } PDSCH-TimeDomainResourceAllocationList-r16 ::= SEQUENCE (SIZE(1..maxNrofDL-Allocations)) OF PDSCH-TimeDomainResourceAllocation-r16 PDSCH-TimeDomainResourceAllocation-r16 ::= SEQUENCE {k0-r16Slot offset between DCI and its scheduled PDSCH (see TS 38.214 [19], clause 5.1.2.1) When the field is absent the UE applies the value 0.INTEGER(0..32) OPTIONAL, -- Need SmappingType-r16PDSCH mapping type. (see TS 38.214 [19], clause 5.3).ENUMERATED {typeA, typeB},startSymbolAndLength-r16An index giving valid combinations of start symbol and length (jointly encoded) as start and length indicator (SLIV). The network configures the field so that the allocation does not cross the slot boundary (see TS 38.214 [19], clause 5.1.2.1).INTEGER (0..127),repetitionNumber-r16Indicates the number of PDSCH transmission occasions for slot-based repetition scheme in IE RepetitionSchemeConfig. The parameter is used as specified in 38.214 [19].ENUMERATED {n2, n3, n4, n5, n6, n7, n8, n16} OPTIONAL, -- Cond Formats1-0and1-1 ... } -- TAG-PDSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP -- ASN1STOP
PDSCH-TimeDomainResourceAllocation field descriptions |
---|
k0 Slot offset between DCI and its scheduled PDSCH (see TS 38.214 [19], clause 5.1.2.1) When the field is absent the UE applies the value 0. |
mappingType PDSCH mapping type. (see TS 38.214 [19], clause 5.3). |
repetitionNumber Indicates the number of PDSCH transmission occasions for slot-based repetition scheme in IE RepetitionSchemeConfig. The parameter is used as specified in 38.214 [19]. |
startSymbolAndLength An index giving valid combinations of start symbol and length (jointly encoded) as start and length indicator (SLIV). The network configures the field so that the allocation does not cross the slot boundary (see TS 38.214 [19], clause 5.1.2.1). |
Conditional Presence | Explanation |
---|---|
Formats1-0and1-1 | In pdsch-TimeDomainResourceAllocationList-r16, this field is optionally present, Need R. In pdsch-TimeDomainAllocationListDCI-1-2, this field is absent. |
The IE PHR-Config is used to configure parameters for power headroom reporting.
-- ASN1START -- TAG-PHR-CONFIG-START PHR-Config ::= SEQUENCE {phr-PeriodicTimerValue in number of subframes for PHR reporting as specified in TS 38.321 [3]. Value sf10 corresponds to 10 subframes, value sf20 corresponds to 20 subframes, and so on.ENUMERATED {sf10, sf20, sf50, sf100, sf200,sf500, sf1000, infinity},phr-ProhibitTimerValue in number of subframes for PHR reporting as specified in TS 38.321 [3]. Value sf0 corresponds to 0 subframe, value sf10 corresponds to 10 subframes, value sf20 corresponds to 20 subframes, and so on.ENUMERATED {sf0, sf10, sf20, sf50, sf100,sf200, sf500, sf1000},phr-Tx-PowerFactorChangeValue in dB for PHR reporting as specified in TS 38.321 [3]. Value dB1 corresponds to 1 dB, dB3 corresponds to 3 dB and so on. The same value applies for each serving cell (although the associated functionality is performed independently for each cell).ENUMERATED {dB1, dB3, dB6, infinity},multiplePHRIndicates if power headroom shall be reported using the Single Entry PHR MAC control element or Multiple Entry PHR MAC control element defined in TS 38.321 [3]. True means to use Multiple Entry PHR MAC control element and False means to use the Single Entry PHR MAC control element defined in TS 38.321 [3]. The network configures this field to true for MR-DC and UL CA for NR, and to false in all other cases.BOOLEAN,dummyThis field is not used in this version of the specification and the UE ignores the received value.BOOLEAN,phr-Type2OtherCellIf set to true, the UE shall report a PHR type 2 for the SpCell of the other MAC entity. See TS 38.321 [3], clause 5.4.6. Network sets this field to false if the UE is not configured with an E-UTRA MAC entity.BOOLEAN,phr-ModeOtherCGIndicates the mode (i.e. real or virtual) used for the PHR of the activated cells that are part of the other Cell Group (i.e. MCG or SCG), when DC is configured. If the UE is configured with only one cell group (no DC), it ignores the field.ENUMERATED {real, virtual}, ..., [[mpe-Reporting-FR2-r16Indicates whether the UE shall report MPE P-MPR in the PHR MAC control element, as specified in TS 38.321 [3].SetupRelease { MPE-Config-FR2-r16 } OPTIONAL -- Need M ]] } MPE-Config-FR2-r16 ::= SEQUENCE {mpe-ProhibitTimer-r16Value in number of subframes for MPE reporting, as specified in TS 38.321 [3]. Value sf10 corresponds to 10 subframes, and so on.ENUMERATED {sf0, sf10, sf20, sf50, sf100, sf200, sf500, sf1000},mpe-Threshold-r16Value of the P-MPR threshold in dB for reporting MPE P-MPR when FR2 is configured, as specified in TS 38.321 [3]. The same value applies for each serving cell (although the associated functionality is performed independently for each cell).ENUMERATED {dB3, dB6, dB9, dB12} } -- TAG-PHR-CONFIG-STOP -- ASN1STOP
PHR-Config field descriptions |
---|
dummy This field is not used in this version of the specification and the UE ignores the received value. |
mpe-ProhibitTimer Value in number of subframes for MPE reporting, as specified in TS 38.321 [3]. Value sf10 corresponds to 10 subframes, and so on. |
mpe-Reporting-FR2 Indicates whether the UE shall report MPE P-MPR in the PHR MAC control element, as specified in TS 38.321 [3]. |
mpe-Threshold Value of the P-MPR threshold in dB for reporting MPE P-MPR when FR2 is configured, as specified in TS 38.321 [3]. The same value applies for each serving cell (although the associated functionality is performed independently for each cell). |
multiplePHR Indicates if power headroom shall be reported using the Single Entry PHR MAC control element or Multiple Entry PHR MAC control element defined in TS 38.321 [3]. True means to use Multiple Entry PHR MAC control element and False means to use the Single Entry PHR MAC control element defined in TS 38.321 [3]. The network configures this field to true for MR-DC and UL CA for NR, and to false in all other cases. |
phr-ModeOtherCG Indicates the mode (i.e. real or virtual) used for the PHR of the activated cells that are part of the other Cell Group (i.e. MCG or SCG), when DC is configured. If the UE is configured with only one cell group (no DC), it ignores the field. |
phr-PeriodicTimer Value in number of subframes for PHR reporting as specified in TS 38.321 [3]. Value sf10 corresponds to 10 subframes, value sf20 corresponds to 20 subframes, and so on. |
phr-ProhibitTimer Value in number of subframes for PHR reporting as specified in TS 38.321 [3]. Value sf0 corresponds to 0 subframe, value sf10 corresponds to 10 subframes, value sf20 corresponds to 20 subframes, and so on. |
phr-Tx-PowerFactorChange Value in dB for PHR reporting as specified in TS 38.321 [3]. Value dB1 corresponds to 1 dB, dB3 corresponds to 3 dB and so on. The same value applies for each serving cell (although the associated functionality is performed independently for each cell). |
phr-Type2OtherCell If set to true, the UE shall report a PHR type 2 for the SpCell of the other MAC entity. See TS 38.321 [3], clause 5.4.6. Network sets this field to false if the UE is not configured with an E-UTRA MAC entity. |
The PhysCellId identifies the physical cell identity (PCI).
The IE PhysicalCellGroupConfig is used to configure cell-group specific L1 parameters.
-- ASN1START -- TAG-PHYSICALCELLGROUPCONFIG-START PhysicalCellGroupConfig ::= SEQUENCE {harq-ACK-SpatialBundlingPUCCHEnables spatial bundling of HARQ ACKs. It is configured per cell group (i.e. for all the cells within the cell group) for PUCCH reporting of HARQ-ACK. It is only applicable when more than 4 layers are possible to schedule. When the field is absent, the spatial bundling of PUCCH HARQ ACKs for the primary PUCCH group is disabled (see TS 38.213 [13], clause 9.1.2.1). If the field harq-ACK SpatialBundlingPUCCH-secondaryPUCCHgroup is present, harq-ACK-SpatialBundlingPUCCH is only applied to primary PUCCH group. Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group.ENUMERATED {true} OPTIONAL, -- Need Sharq-ACK-SpatialBundlingPUSCHEnables spatial bundling of HARQ ACKs. It is configured per cell group (i.e. for all the cells within the cell group) for PUSCH reporting of HARQ-ACK. It is only applicable when more than 4 layers are possible to schedule. When the field is absent, the spatial bundling of PUSCH HARQ ACKs for the primary PUCCH group is disabled (see TS 38.213 [13], clauses 9.1.2.2 and 9.1.3.2). If the field harq-ACK SpatialBundlingPUSCH-secondaryPUCCHgroup is present, harq-ACK-SpatialBundlingPUSCH is only applied to primary PUCCH group. Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group.ENUMERATED {true} OPTIONAL, -- Need Sp-NR-FR1The maximum total transmit power to be used by the UE in this NR cell group across all serving cells in frequency range 1 (FR1). The maximum transmit power that the UE may use may be additionally limited by p-Max (configured in FrequencyInfoUL) and by p-UE-FR1 (configured total for all serving cells operating on FR1).P-Max OPTIONAL, -- Need Rpdsch-HARQ-ACK-CodebookThe PDSCH HARQ-ACK codebook is either semi-static or dynamic. This is applicable to both CA and none CA operation (see TS 38.213 [13], clauses 9.1.2 and 9.1.3). If pdsch-HARQ-ACK-Codebook-r16 is signalled, UE shall ignore the pdsch-HARQ-ACK-Codebook (without suffix). For the HARQ-ACK for sidelink, if pdsch-HARQ-ACK-Codebook-r16 is signalled, the UE uses pdsch-HARQ-ACK-Codebook (without suffix) and ignores pdsch-HARQ-ACK-Codebook-r16. If the field pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup is present, pdsch-HARQ-ACK-Codebook is applied to primary PUCCH group. Otherwise, this field is applied to the cell group (i.e. for all the cells within the cell group). For the HARQ-ACK for sidelink, if the field pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup is present, pdsch-HARQ-ACK-Codebook is applied to primary and secondary PUCCH group and the UE ignores pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup.ENUMERATED {semiStatic, dynamic},tpc-SRS-RNTIRNTI used for SRS TPC commands on DCI (see TS 38.213 [13], clause 10.1).RNTI-Value OPTIONAL, -- Need Rtpc-PUCCH-RNTIRNTI used for PUCCH TPC commands on DCI (see TS 38.213 [13], clause 10.1).RNTI-Value OPTIONAL, -- Need Rtpc-PUSCH-RNTIRNTI used for PUSCH TPC commands on DCI (see TS 38.213 [13], clause 10.1).RNTI-Value OPTIONAL, -- Need Rsp-CSI-RNTIRNTI for Semi-Persistent CSI reporting on PUSCH (see CSI-ReportConfig) (see TS 38.214 [19], clause 5.2.1.5.2). Network always configures the UE with a value for this field when at least one CSI-ReportConfig with reportConfigType set to semiPersistentOnPUSCH is configured.RNTI-Value OPTIONAL, -- Need Rcs-RNTIRNTI value for downlink SPS (see SPS-Config) and uplink configured grant (see ConfiguredGrantConfig).SetupRelease { RNTI-Value } OPTIONAL, -- Need M ..., [[mcs-C-RNTIRNTI to indicate use of qam64LowSE for grant-based transmissions. When the mcs-C-RNTI is configured, RNTI scrambling of DCI CRC is used to choose the corresponding MCS table.RNTI-Value OPTIONAL, -- Need Rp-UE-FR1The maximum total transmit power to be used by the UE across all serving cells in frequency range 1 (FR1) across all cell groups. The maximum transmit power that the UE may use may be additionally limited by p-Max (configured in FrequencyInfoUL) and by p-NR-FR1 (configured for the cell group).P-Max OPTIONAL -- Cond MCG-Only ]], [[xScaleThe UE is allowed to drop NR only if the power scaling applied to NR results in a difference between scaled and unscaled NR UL of more than xScale dB (see TS 38.213 [13]). If the value is not configured for dynamic power sharing, the UE assumes default value of 6 dB.ENUMERATED {dB0, dB6, spare2, spare1} OPTIONAL -- Cond SCG-Only ]], [[ pdcch-BlindDetection SetupRelease { PDCCH-BlindDetection } OPTIONAL -- Need M ]], [[ dcp-Config-r16 SetupRelease { DCP-Config-r16 } OPTIONAL, -- Need Mharq-ACK-SpatialBundlingPUCCH-secondaryPUCCHgroup-r16Indicates whether spatial bundling of PUCCH HARQ ACKs for the secondary PUCCH group is enabled or disabled. The field is only applicable when more than 4 layers are possible to schedule (see TS 38.213 [13], clause 9.1.2.1). When the field is absent, the use of spatial bundling of PUCCH HARQ ACKs for the secondary PUCCH group is indicated by harq-ACK-SpatialBundlingPUCCH. See TS 38.213 [13], clause 9.1.2.1. Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group.ENUMERATED {enabled, disabled} OPTIONAL, -- Cond twoPUCCHgroupharq-ACK-SpatialBundlingPUSCH-secondaryPUCCHgroup-r16Indicates whether spatial bundling of PUSCH HARQ ACKs for the secondary PUCCH group is enabled or disabled. The field is only applicable when more than 4 layers are possible to schedule (see TS 38.213 [13], clauses 9.1.2.2 and 9.1.3.2). When the field is absent, the use of spatial bundling of PUSCH HARQ ACKs for the secondary PUCCH group is indicated by harq-ACK-SpatialBundlingPUSCH. See TS 38.213 [13], clauses 9.1.2.2 and 9.1.3.2. Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group.ENUMERATED {enabled, disabled} OPTIONAL, -- Cond twoPUCCHgrouppdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup-r16The PDSCH HARQ-ACK codebook is either semi-static or dynamic. This is applicable to CA operation (see TS 38.213 [13], clauses 9.1.2 and 9.1.3). It is configured for secondary PUCCH group.ENUMERATED {semiStatic, dynamic} OPTIONAL, -- Cond twoPUCCHgroupp-NR-FR2-r16The maximum total transmit power to be used by the UE in this NR cell group across all serving cells in frequency range 2 (FR2). The maximum transmit power that the UE may use may be additionally limited by p-Max (configured in FrequencyInfoUL) and by p-UE-FR2 (configured total for all serving cells operating on FR2). This field is only used in NR-DC. A UE does not expect to be configured with this parameter in this release of the specification.P-Max OPTIONAL, -- Need Rp-UE-FR2-r16The maximum total transmit power to be used by the UE across all serving cells in frequency range 2 (FR2) across all cell groups. The maximum transmit power that the UE may use may be additionally limited by p-Max (configured in FrequencyInfoUL) and by p-NR-FR2 (configured for the cell group). A UE does not expect to be configured with this parameter in this release of the specification.P-Max OPTIONAL, -- Cond MCG-Onlynrdc-PCmode-FR1-r16Indicates the uplink power sharing mode that the UE uses in NR-DC in frequency range 1 (FR1) (see TS 38.213 [13], clause 7.6).ENUMERATED {semi-static-mode1, semi-static-mode2, dynamic} OPTIONAL, -- Cond MCG-Onlynrdc-PCmode-FR2-r16Indicates the uplink power sharing mode that the UE uses in NR-DC in frequency range 2 (FR2) (see TS 38.213 [13], clause 7.6).ENUMERATED {semi-static-mode1, semi-static-mode2, dynamic} OPTIONAL, -- Cond MCG-Onlypdsch-HARQ-ACK-Codebook-r16The PDSCH HARQ-ACK codebook is either semi-static or dynamic. This is applicable to both CA and none CA operation (see TS 38.213 [13], clauses 9.1.2 and 9.1.3). If pdsch-HARQ-ACK-Codebook-r16 is signalled, UE shall ignore the pdsch-HARQ-ACK-Codebook (without suffix). For the HARQ-ACK for sidelink, if pdsch-HARQ-ACK-Codebook-r16 is signalled, the UE uses pdsch-HARQ-ACK-Codebook (without suffix) and ignores pdsch-HARQ-ACK-Codebook-r16. If the field pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup is present, pdsch-HARQ-ACK-Codebook is applied to primary PUCCH group. Otherwise, this field is applied to the cell group (i.e. for all the cells within the cell group). For the HARQ-ACK for sidelink, if the field pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup is present, pdsch-HARQ-ACK-Codebook is applied to primary and secondary PUCCH group and the UE ignores pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup.ENUMERATED {enhancedDynamic} OPTIONAL, -- Need Rnfi-TotalDAI-Included-r16Indicates whether the NFI and total DAI fields of the non-scheduled PDSCH group is included in the non-fallback DL grant DCI (see TS 38.212 [17], clause 7.3.1). The network configures this only when enhanced dynamic codebook is configured (pdsch-HARQ-ACK-Codebook is set to enhancedDynamic).ENUMERATED {true} OPTIONAL, -- Need Rul-TotalDAI-Included-r16Indicates whether the total DAI fields of the additonal PDSCH group is included in the non-fallback UL grant DCI (see TS 38.212 [17], clause 7.3.1). The network configures this only when enhanced dynamic codebook is configured (pdsch-HARQ-ACK-Codebook is set to enhancedDynamic).ENUMERATED {true} OPTIONAL, -- Need Rpdsch-HARQ-ACK-OneShotFeedback-r16When configured, the DCI_format 1_1 can request the UE to report A/N for all HARQ processes and all CCs configured in the PUCCH group (see TS 38.212 [17], clause 7.3.1).ENUMERATED {true} OPTIONAL, -- Need Rpdsch-HARQ-ACK-OneShotFeedbackNDI-r16When configured, the DCI_format 1_1 can request the UE to include NDI for each A/N reported.The network configures this only when pdsch-HARQ-ACK-OneShotFeedback is configured.ENUMERATED {true} OPTIONAL, -- Need Rpdsch-HARQ-ACK-OneShotFeedbackCBG-r16When configured, the DCI_format 1_1 can request the UE to include CBG level A/N for each CC with CBG level transmission configured. When not configured, the UE will report TB level A/N even if CBG level transmission is configured for a CC.The network configures this only when pdsch-HARQ-ACK-OneShotFeedback is configured.ENUMERATED {true} OPTIONAL, -- Need RdownlinkAssignmentIndexDCI-0-2-r16Indicates if "Downlink assignment index" is present or absent in DCI format 0_2. If the field "downlinkAssignmentIndexDCI-0-2" is absent, then 0 bit for "Downlink assignment index" in DCI format 0_2. If the field "downlinkAssignmentIndexDCI-0-2" is present, then the bitwidth of "Downlink assignment index" in DCI format 0_2 is defined in the same was as that in DCI format 0_1 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.1).ENUMERATED { enabled } OPTIONAL, -- Need SdownlinkAssignmentIndexDCI-1-2-r16Configures the number of bits for "Downlink assignment index" in DCI format 1_2. If the field is absent, then 0 bit is applied for "Downlink assignment index" in DCI format 1_2. Note that 1 bit and 2 bits are applied if only one serving cell is configured in the DL and pdsch-HARQ-ACK-Codebook is set to dynamic. 4 bits is applied if more than one serving cell are configured in the DL and pdsch-HARQ-ACK-Codebook is set to dynamic (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.1).ENUMERATED {n1, n2, n4} OPTIONAL, -- Need Spdsch-HARQ-ACK-CodebookList-r16A list of configurations for one or two HARQ-ACK codebooks. Each configuration in the list is defined in the same way as pdsch-HARQ-ACK-Codebook (see TS 38.212 [17], clause 7.3.1.2.2 and TS 38.213 [13], clauses 7.2.1, 9.1.2, 9.1.3 and 9.2.1). If this field is present, the field pdsch-HARQ-ACK-Codebook is ignored. If this field is present, the value of this field is applied for primary PUCCH group and for secondary PUCCH group (if configured). For the HARQ-ACK for sidelink, the UE uses pdsch-HARQ-ACK-Codebook and ignores pdsch-HARQ-ACK-CodebookList if this field is present.SetupRelease {PDSCH-HARQ-ACK-CodebookList-r16} OPTIONAL, -- Need MackNackFeedbackMode-r16Indicates which among the joint and separate ACK/NACK feedback modes to use within a slot as specified in TS 38.213 [13] (clause 9).ENUMERATED {joint, separate} OPTIONAL, -- Need Rpdcch-BlindDetectionCA-CombIndicator-r16Configure one combination of pdcch-BlindDetectionCA1 (for R15) and pdcch-BlindDetectionCA2 (for R16) for UE to use for scaling PDCCH monitoring capability if the number of serving cells configured to a UE is larger than the reported capability, and if UE reports more than one combination of pdcch-BlindDetectionCA1 and pdcch-BlindDetectionCA2 as UE capability. The combination of pdcch-BlindDetectionCA1 and pdcch-BlindDetectionCA2) configured by pdcch-BlindDetectionCACombIndicator is from the more than one combination of pdcch-BlindDetectionCA1 and pdcch-BlindDetectionCA2 reported by UE (see TS 38.213 [13], clause 10).SetupRelease { PDCCH-BlindDetectionCA-CombIndicator-r16 } OPTIONAL, -- Need M pdcch-BlindDetection2-r16 SetupRelease { PDCCH-BlindDetection2-r16 } OPTIONAL, -- Need M pdcch-BlindDetection3-r16 SetupRelease { PDCCH-BlindDetection3-r16 } OPTIONAL, -- Need MbdFactorR-r16Parameter for determining and distributing the maximum numbers of BD/CCE for mPDCCH based mPDSCH transmission as specified in TS 38.213 [13] Clause 10.1.ENUMERATED {n1} OPTIONAL -- Need R ]] } PDCCH-BlindDetection ::= INTEGER (1..15) DCP-Config-r16 ::= SEQUENCE {ps-RNTI-r16RNTI value for scrambling CRC of DCI format 2-6 used for power saving (see TS 38.213 [13], clause 10.1).RNTI-Value,ps-Offset-r16The start of the search-time of DCI format 2-6 with CRC scrambled by PS-RNTI relative to the start of the drx-onDurationTimer of Long DRX (see TS 38.213 [13], clause 10.3). Value in multiples of 0.125ms (milliseconds). 1 corresponds to 0.125 ms, 2corresponds to 0.25 ms, 3 corresponds to 0.375 ms and so on.INTEGER (1..120),sizeDCI-2-6-r16Size of DCI format 2-6 (see TS 38.213 [13], clause 10.3).INTEGER (1..maxDCI-2-6-Size-r16),ps-PositionDCI-2-6-r16Starting position of UE wakeup and SCell dormancy indication in DCI format 2-6 (see TS 38.213 [13], clause 10.3).INTEGER (0..maxDCI-2-6-Size-1-r16),ps-WakeUp-r16Indicates the UE to wake-up if DCI format 2-6 is not detected outside active time (see TS 38.321 [3], clause 5.7). If the field is absent, the UE does not wake-up if DCI format 2-6 is not detected outside active time.ENUMERATED {true} OPTIONAL, -- Need Sps-TransmitPeriodicL1-RSRP-r16Indicates the UE to transmit periodic L1-RSRP report(s) when the drx-onDurationTimer does not start (see TS 38.321 [3], clause 5.7). If the field is absent, the UE does not transmit periodic L1-RSRP report(s) when the drx-onDurationTimer does not start.ENUMERATED {true} OPTIONAL, -- Need Sps-TransmitOtherPeriodicCSI-r16Indicates the UE to transmit periodic CSI report(s) other than L1-RSRP reports when the drx-onDurationTimer does not start (see TS 38.321 [3], clause 5.7). If the field is absent, the UE does not transmit periodic CSI report(s) other than L1-RSRP reports when the drx-onDurationTimer does not start.ENUMERATED {true} OPTIONAL -- Need S } PDSCH-HARQ-ACK-CodebookList-r16 ::= SEQUENCE (SIZE (1..2)) OF ENUMERATED {semiStatic, dynamic} PDCCH-BlindDetectionCA-CombIndicator-r16 ::= SEQUENCE { pdcch-BlindDetectionCA1-r16 INTEGER (1..15), pdcch-BlindDetectionCA2-r16 INTEGER (1..15) } PDCCH-BlindDetection2-r16 ::= INTEGER (1..15) PDCCH-BlindDetection3-r16 ::= INTEGER (1..15) -- TAG-PHYSICALCELLGROUPCONFIG-STOP -- ASN1STOP
PhysicalCellGroupConfig field descriptions |
---|
ackNackFeedbackMode Indicates which among the joint and separate ACK/NACK feedback modes to use within a slot as specified in TS 38.213 [13] (clause 9). |
bdFactorR Parameter for determining and distributing the maximum numbers of BD/CCE for mPDCCH based mPDSCH transmission as specified in TS 38.213 [13] Clause 10.1. |
cs-RNTI RNTI value for downlink SPS (see SPS-Config) and uplink configured grant (see ConfiguredGrantConfig). |
downlinkAssignmentIndexDCI-0-2 Indicates if "Downlink assignment index" is present or absent in DCI format 0_2. If the field "downlinkAssignmentIndexDCI-0-2" is absent, then 0 bit for "Downlink assignment index" in DCI format 0_2. If the field "downlinkAssignmentIndexDCI-0-2" is present, then the bitwidth of "Downlink assignment index" in DCI format 0_2 is defined in the same was as that in DCI format 0_1 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.1). |
downlinkAssignmentIndexDCI-1-2 Configures the number of bits for "Downlink assignment index" in DCI format 1_2. If the field is absent, then 0 bit is applied for "Downlink assignment index" in DCI format 1_2. Note that 1 bit and 2 bits are applied if only one serving cell is configured in the DL and pdsch-HARQ-ACK-Codebook is set to dynamic. 4 bits is applied if more than one serving cell are configured in the DL and pdsch-HARQ-ACK-Codebook is set to dynamic (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.1). |
harq-ACK-SpatialBundlingPUCCH Enables spatial bundling of HARQ ACKs. It is configured per cell group (i.e. for all the cells within the cell group) for PUCCH reporting of HARQ-ACK. It is only applicable when more than 4 layers are possible to schedule. When the field is absent, the spatial bundling of PUCCH HARQ ACKs for the primary PUCCH group is disabled (see TS 38.213 [13], clause 9.1.2.1). If the field harq-ACK SpatialBundlingPUCCH-secondaryPUCCHgroup is present, harq-ACK-SpatialBundlingPUCCH is only applied to primary PUCCH group. Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group. |
harq-ACK-SpatialBundlingPUCCH-secondaryPUCCHgroup Indicates whether spatial bundling of PUCCH HARQ ACKs for the secondary PUCCH group is enabled or disabled. The field is only applicable when more than 4 layers are possible to schedule (see TS 38.213 [13], clause 9.1.2.1). When the field is absent, the use of spatial bundling of PUCCH HARQ ACKs for the secondary PUCCH group is indicated by harq-ACK-SpatialBundlingPUCCH. See TS 38.213 [13], clause 9.1.2.1. Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group. |
harq-ACK-SpatialBundlingPUSCH Enables spatial bundling of HARQ ACKs. It is configured per cell group (i.e. for all the cells within the cell group) for PUSCH reporting of HARQ-ACK. It is only applicable when more than 4 layers are possible to schedule. When the field is absent, the spatial bundling of PUSCH HARQ ACKs for the primary PUCCH group is disabled (see TS 38.213 [13], clauses 9.1.2.2 and 9.1.3.2). If the field harq-ACK SpatialBundlingPUSCH-secondaryPUCCHgroup is present, harq-ACK-SpatialBundlingPUSCH is only applied to primary PUCCH group. Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group. |
harq-ACK-SpatialBundlingPUSCH-secondaryPUCCHgroup Indicates whether spatial bundling of PUSCH HARQ ACKs for the secondary PUCCH group is enabled or disabled. The field is only applicable when more than 4 layers are possible to schedule (see TS 38.213 [13], clauses 9.1.2.2 and 9.1.3.2). When the field is absent, the use of spatial bundling of PUSCH HARQ ACKs for the secondary PUCCH group is indicated by harq-ACK-SpatialBundlingPUSCH. See TS 38.213 [13], clauses 9.1.2.2 and 9.1.3.2. Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group. |
mcs-C-RNTI RNTI to indicate use of qam64LowSE for grant-based transmissions. When the mcs-C-RNTI is configured, RNTI scrambling of DCI CRC is used to choose the corresponding MCS table. |
nfi-TotalDAI-Included Indicates whether the NFI and total DAI fields of the non-scheduled PDSCH group is included in the non-fallback DL grant DCI (see TS 38.212 [17], clause 7.3.1). The network configures this only when enhanced dynamic codebook is configured (pdsch-HARQ-ACK-Codebook is set to enhancedDynamic). |
nrdc-PCmode-FR1 Indicates the uplink power sharing mode that the UE uses in NR-DC in frequency range 1 (FR1) (see TS 38.213 [13], clause 7.6). |
nrdc-PCmode-FR2 Indicates the uplink power sharing mode that the UE uses in NR-DC in frequency range 2 (FR2) (see TS 38.213 [13], clause 7.6). |
pdcch-BlindDetection, pdcch-BlindDetection2, pdcch-BlindDetection3 Indicates the reference number of cells for PDCCH blind detection for the CG. Network configures the field for each CG when the UE is in NR DC and sets the value in accordance with the constraints specified in TS 38.213 [13]. The network configures pdcch-BlindDetection only if the UE is in NR-DC. The network configures pdcch-BlindDetection2 only if the UE is in NR-DC with at least one downlink cell using Rel-16 PDCCH monitoring capability. The network configures pdcch-BlindDetection3 only if the UE is in NR-DC with at least one downlink cell using Rel-15 PDCCH monitoring capability. |
pdcch-BlindDetectionCA-CombIndicator Configure one combination of pdcch-BlindDetectionCA1 (for R15) and pdcch-BlindDetectionCA2 (for R16) for UE to use for scaling PDCCH monitoring capability if the number of serving cells configured to a UE is larger than the reported capability, and if UE reports more than one combination of pdcch-BlindDetectionCA1 and pdcch-BlindDetectionCA2 as UE capability. The combination of pdcch-BlindDetectionCA1 and pdcch-BlindDetectionCA2) configured by pdcch-BlindDetectionCACombIndicator is from the more than one combination of pdcch-BlindDetectionCA1 and pdcch-BlindDetectionCA2 reported by UE (see TS 38.213 [13], clause 10). |
p-NR-FR1 The maximum total transmit power to be used by the UE in this NR cell group across all serving cells in frequency range 1 (FR1). The maximum transmit power that the UE may use may be additionally limited by p-Max (configured in FrequencyInfoUL) and by p-UE-FR1 (configured total for all serving cells operating on FR1). |
p-NR-FR2 The maximum total transmit power to be used by the UE in this NR cell group across all serving cells in frequency range 2 (FR2). The maximum transmit power that the UE may use may be additionally limited by p-Max (configured in FrequencyInfoUL) and by p-UE-FR2 (configured total for all serving cells operating on FR2). This field is only used in NR-DC. A UE does not expect to be configured with this parameter in this release of the specification. |
ps-RNTI RNTI value for scrambling CRC of DCI format 2-6 used for power saving (see TS 38.213 [13], clause 10.1). |
ps-Offset The start of the search-time of DCI format 2-6 with CRC scrambled by PS-RNTI relative to the start of the drx-onDurationTimer of Long DRX (see TS 38.213 [13], clause 10.3). Value in multiples of 0.125ms (milliseconds). 1 corresponds to 0.125 ms, 2corresponds to 0.25 ms, 3 corresponds to 0.375 ms and so on. |
ps-WakeUp Indicates the UE to wake-up if DCI format 2-6 is not detected outside active time (see TS 38.321 [3], clause 5.7). If the field is absent, the UE does not wake-up if DCI format 2-6 is not detected outside active time. |
ps-PositionDCI-2-6 Starting position of UE wakeup and SCell dormancy indication in DCI format 2-6 (see TS 38.213 [13], clause 10.3). |
ps-TransmitPeriodicL1-RSRP Indicates the UE to transmit periodic L1-RSRP report(s) when the drx-onDurationTimer does not start (see TS 38.321 [3], clause 5.7). If the field is absent, the UE does not transmit periodic L1-RSRP report(s) when the drx-onDurationTimer does not start. |
ps-TransmitOtherPeriodicCSI Indicates the UE to transmit periodic CSI report(s) other than L1-RSRP reports when the drx-onDurationTimer does not start (see TS 38.321 [3], clause 5.7). If the field is absent, the UE does not transmit periodic CSI report(s) other than L1-RSRP reports when the drx-onDurationTimer does not start. |
p-UE-FR1 The maximum total transmit power to be used by the UE across all serving cells in frequency range 1 (FR1) across all cell groups. The maximum transmit power that the UE may use may be additionally limited by p-Max (configured in FrequencyInfoUL) and by p-NR-FR1 (configured for the cell group). |
p-UE-FR2 The maximum total transmit power to be used by the UE across all serving cells in frequency range 2 (FR2) across all cell groups. The maximum transmit power that the UE may use may be additionally limited by p-Max (configured in FrequencyInfoUL) and by p-NR-FR2 (configured for the cell group). A UE does not expect to be configured with this parameter in this release of the specification. |
pdsch-HARQ-ACK-Codebook The PDSCH HARQ-ACK codebook is either semi-static or dynamic. This is applicable to both CA and none CA operation (see TS 38.213 [13], clauses 9.1.2 and 9.1.3). If pdsch-HARQ-ACK-Codebook-r16 is signalled, UE shall ignore the pdsch-HARQ-ACK-Codebook (without suffix). For the HARQ-ACK for sidelink, if pdsch-HARQ-ACK-Codebook-r16 is signalled, the UE uses pdsch-HARQ-ACK-Codebook (without suffix) and ignores pdsch-HARQ-ACK-Codebook-r16. If the field pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup is present, pdsch-HARQ-ACK-Codebook is applied to primary PUCCH group. Otherwise, this field is applied to the cell group (i.e. for all the cells within the cell group). For the HARQ-ACK for sidelink, if the field pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup is present, pdsch-HARQ-ACK-Codebook is applied to primary and secondary PUCCH group and the UE ignores pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup. |
pdsch-HARQ-ACK-CodebookList A list of configurations for one or two HARQ-ACK codebooks. Each configuration in the list is defined in the same way as pdsch-HARQ-ACK-Codebook (see TS 38.212 [17], clause 7.3.1.2.2 and TS 38.213 [13], clauses 7.2.1, 9.1.2, 9.1.3 and 9.2.1). If this field is present, the field pdsch-HARQ-ACK-Codebook is ignored. If this field is present, the value of this field is applied for primary PUCCH group and for secondary PUCCH group (if configured). For the HARQ-ACK for sidelink, the UE uses pdsch-HARQ-ACK-Codebook and ignores pdsch-HARQ-ACK-CodebookList if this field is present. |
pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup The PDSCH HARQ-ACK codebook is either semi-static or dynamic. This is applicable to CA operation (see TS 38.213 [13], clauses 9.1.2 and 9.1.3). It is configured for secondary PUCCH group. |
pdsch-HARQ-ACK-OneShotFeedback When configured, the DCI_format 1_1 can request the UE to report A/N for all HARQ processes and all CCs configured in the PUCCH group (see TS 38.212 [17], clause 7.3.1). |
pdsch-HARQ-ACK-OneShotFeedbackCBG When configured, the DCI_format 1_1 can request the UE to include CBG level A/N for each CC with CBG level transmission configured. When not configured, the UE will report TB level A/N even if CBG level transmission is configured for a CC.The network configures this only when pdsch-HARQ-ACK-OneShotFeedback is configured. |
pdsch-HARQ-ACK-OneShotFeedbackNDI When configured, the DCI_format 1_1 can request the UE to include NDI for each A/N reported.The network configures this only when pdsch-HARQ-ACK-OneShotFeedback is configured. |
sizeDCI-2-6 Size of DCI format 2-6 (see TS 38.213 [13], clause 10.3). |
sp-CSI-RNTI RNTI for Semi-Persistent CSI reporting on PUSCH (see CSI-ReportConfig) (see TS 38.214 [19], clause 5.2.1.5.2). Network always configures the UE with a value for this field when at least one CSI-ReportConfig with reportConfigType set to semiPersistentOnPUSCH is configured. |
tpc-PUCCH-RNTI RNTI used for PUCCH TPC commands on DCI (see TS 38.213 [13], clause 10.1). |
tpc-PUSCH-RNTI RNTI used for PUSCH TPC commands on DCI (see TS 38.213 [13], clause 10.1). |
tpc-SRS-RNTI RNTI used for SRS TPC commands on DCI (see TS 38.213 [13], clause 10.1). |
ul-TotalDAI-Included Indicates whether the total DAI fields of the additonal PDSCH group is included in the non-fallback UL grant DCI (see TS 38.212 [17], clause 7.3.1). The network configures this only when enhanced dynamic codebook is configured (pdsch-HARQ-ACK-Codebook is set to enhancedDynamic). |
xScale The UE is allowed to drop NR only if the power scaling applied to NR results in a difference between scaled and unscaled NR UL of more than xScale dB (see TS 38.213 [13]). If the value is not configured for dynamic power sharing, the UE assumes default value of 6 dB. |
Conditional Presence | Explanation |
---|---|
MCG-Only | This field is optionally present, Need R, in the PhysicalCellGroupConfig of the MCG. It is absent otherwise. |
SCG-Only | This field is optionally present, Need S, in the PhysicalCellGroupConfig of the SCG in (NG)EN-DC as defined in TS 38.213 [13]. It is absent otherwise. |
twoPUCCHgroup | This field is optionally present, Need R, if secondary PUCCH group is configured. It is absent otherwise. |
The IE PLMN-Identity identifies a Public Land Mobile Network. Further information regarding how to set the IE is specified in TS 23.003 [21].
-- ASN1START -- TAG-PLMN-IDENTITY-START PLMN-Identity ::= SEQUENCE {mccThe first element contains the first MCC digit, the second element the second MCC digit and so on. If the field is absent, it takes the same value as the mcc of the immediately preceding IE PLMN-Identity. See TS 23.003 [21].MCC OPTIONAL, -- Cond MCCmncThe first element contains the first MNC digit, the second element the second MNC digit and so on. See TS 23.003 [21].MNC } MCC ::= SEQUENCE (SIZE (3)) OF MCC-MNC-Digit MNC ::= SEQUENCE (SIZE (2..3)) OF MCC-MNC-Digit MCC-MNC-Digit ::= INTEGER (0..9) -- TAG-PLMN-IDENTITY-STOP -- ASN1STOP
PLMN-Identity field descriptions |
---|
mcc The first element contains the first MCC digit, the second element the second MCC digit and so on. If the field is absent, it takes the same value as the mcc of the immediately preceding IE PLMN-Identity. See TS 23.003 [21]. |
mnc The first element contains the first MNC digit, the second element the second MNC digit and so on. See TS 23.003 [21]. |
Conditional Presence | Explanation |
---|---|
MCC | This field is mandatory present when PLMN-Identity is not used in a list or if it is the first entry of PLMN-Identity in a list. Otherwise it is optionally present, Need S. |
The IE PLMN-IdentityInfoList includes a list of PLMN identity information.
-- ASN1START -- TAG-PLMN-IDENTITYINFOLIST-START PLMN-IdentityInfoList ::= SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-IdentityInfo PLMN-IdentityInfo ::= SEQUENCE { plmn-IdentityList SEQUENCE (SIZE (1..maxPLMN)) OF PLMN-Identity, trackingAreaCode TrackingAreaCode OPTIONAL, -- Need R ranac RAN-AreaCode OPTIONAL, -- Need R cellIdentity CellIdentity, cellReservedForOperatorUse ENUMERATED {reserved, notReserved}, ..., [[ iab-Support-r16 ENUMERATED {true} OPTIONAL -- Need S ]] } -- TAG-PLMN-IDENTITYINFOLIST-STOP -- ASN1STOP
Includes a list of PLMN identities.
-- ASN1START -- TAG-PLMNIDENTITYLIST2-START PLMN-IdentityList2-r16 ::= SEQUENCE (SIZE (1..16)) OF PLMN-Identity -- TAG-PLMNIDENTITYLIST2-STOP -- ASN1STOP
PLMN-IdentityInfo field descriptions |
---|
cellReservedForOperatorUse Indicates whether the cell is reserved for operator use (per PLMN), as defined in TS 38.304 [20]. This field is ignored by IAB-MT. |
iab-Support This field combines both the support of IAB and the cell status for IAB. If the field is present, the cell supports IAB and the cell is also considered as a candidate for cell (re)selection for IAB-node; if the field is absent, the cell does not support IAB and/or the cell is barred for IAB-node. |
trackingAreaCode Indicates Tracking Area Code to which the cell indicated by cellIdentity field belongs. The absence of the field indicates that the cell only supports PSCell/SCell functionality (per PLMN). |
The IE PRB-Id identifies a Physical Resource Block (PRB) position within a carrier.
The IE PTRS-DownlinkConfig is used to configure downlink phase tracking reference signals (PTRS) (see TS 38.214 [19] clause 5.1.6.3)
-- ASN1START -- TAG-PTRS-DOWNLINKCONFIG-START PTRS-DownlinkConfig ::= SEQUENCE {frequencyDensityPresence and frequency density of DL PT-RS as a function of Scheduled BW. If the field is absent, the UE uses K_PT-RS = 2 (see TS 38.214 [19], clause 5.1.6.3, table 5.1.6.3-2).SEQUENCE (SIZE (2)) OF INTEGER (1..276) OPTIONAL, -- Need StimeDensityPresence and time density of DL PT-RS as a function of MCS. The value 29 is only applicable for MCS Table 5.1.3.1-1 (TS 38.214 [19]). If the field is absent, the UE uses L_PT-RS = 1 (see TS 38.214 [19], clause 5.1.6.3, table 5.1.6.3-1).SEQUENCE (SIZE (3)) OF INTEGER (0..29) OPTIONAL, -- Need Sepre-RatioEPRE ratio between PTRS and PDSCH. Value 0 corresponds to the codepoint "00" in table 4.1-2. Value 1 corresponds to codepoint "01", and so on. If the field is not provided, the UE applies value 0 (see TS 38.214 [19], clause 4.1).INTEGER (0..3) OPTIONAL, -- Need SresourceElementOffsetIndicates the subcarrier offset for DL PTRS. If the field is absent, the UE applies the value offset00 (see TS 38.211 [16], clause 7.4.1.2.2).ENUMERATED { offset01, offset10, offset11 } OPTIONAL, -- Need S ..., [[maxNrofPorts-r16The maximum number of DL PTRS ports specified in TS 38.214 [19] (clause 5.1.6.3). 2 PT-RS ports can only be configured for a DL BWP that is configured, as specified in TS 38.214 [19] clause 5.1, with a mode where a single PDSCH has association between the DM-RS ports and the TCI states as defined in TS 38.214 [19] clause 5.1.6.2.ENUMERATED {n1, n2} OPTIONAL -- Need R ]] } -- TAG-PTRS-DOWNLINKCONFIG-STOP -- ASN1STOP
PTRS-DownlinkConfig field descriptions |
---|
epre-Ratio EPRE ratio between PTRS and PDSCH. Value 0 corresponds to the codepoint "00" in table 4.1-2. Value 1 corresponds to codepoint "01", and so on. If the field is not provided, the UE applies value 0 (see TS 38.214 [19], clause 4.1). |
frequencyDensity Presence and frequency density of DL PT-RS as a function of Scheduled BW. If the field is absent, the UE uses K_PT-RS = 2 (see TS 38.214 [19], clause 5.1.6.3, table 5.1.6.3-2). |
maxNrofPorts The maximum number of DL PTRS ports specified in TS 38.214 [19] (clause 5.1.6.3). 2 PT-RS ports can only be configured for a DL BWP that is configured, as specified in TS 38.214 [19] clause 5.1, with a mode where a single PDSCH has association between the DM-RS ports and the TCI states as defined in TS 38.214 [19] clause 5.1.6.2. |
resourceElementOffset Indicates the subcarrier offset for DL PTRS. If the field is absent, the UE applies the value offset00 (see TS 38.211 [16], clause 7.4.1.2.2). |
timeDensity Presence and time density of DL PT-RS as a function of MCS. The value 29 is only applicable for MCS Table 5.1.3.1-1 (TS 38.214 [19]). If the field is absent, the UE uses L_PT-RS = 1 (see TS 38.214 [19], clause 5.1.6.3, table 5.1.6.3-1). |
The IE PTRS-UplinkConfig is used to configure uplink Phase-Tracking-Reference-Signals (PTRS).
-- ASN1START -- TAG-PTRS-UPLINKCONFIG-START PTRS-UplinkConfig ::= SEQUENCE {transformPrecoderDisabledConfiguration of UL PTRS without transform precoder (with CP-OFDM).SEQUENCE {frequencyDensityPresence and frequency density of UL PT-RS for CP-OFDM waveform as a function of scheduled BW If the field is absent, the UE uses K_PT-RS = 2 (see TS 38.214 [19], clause 6.1).SEQUENCE (SIZE (2)) OF INTEGER (1..276) OPTIONAL, -- Need StimeDensityPresence and time density of UL PT-RS for CP-OFDM waveform as a function of MCS If the field is absent, the UE uses L_PT-RS = 1 (see TS 38.214 [19], clause 6.1).SEQUENCE (SIZE (3)) OF INTEGER (0..29) OPTIONAL, -- Need SmaxNrofPortsThe maximum number of UL PTRS ports for CP-OFDM (see TS 38.214 [19], clause 6.2.3.1).ENUMERATED {n1, n2},resourceElementOffsetIndicates the subcarrier offset for UL PTRS for CP-OFDM. If the field is absent, the UE applies the value offset00 (see TS 38.211 [16], clause 6.4.1.2.2).ENUMERATED {offset01, offset10, offset11 } OPTIONAL, -- Need Sptrs-PowerUL PTRS power boosting factor per PTRS port (see TS 38.214 [19], clause 6.1, table 6.2.3.1.3).ENUMERATED {p00, p01, p10, p11} } OPTIONAL, -- Need RtransformPrecoderEnabledConfiguration of UL PTRS with transform precoder (DFT-S-OFDM).SEQUENCE {sampleDensitySample density of PT-RS for DFT-s-OFDM, pre-DFT, indicating a set of thresholds T={NRBn, n=0,1,2,3,4}, that indicates dependency between presence of PT-RS and scheduled BW and the values of X and K the UE should use depending on the scheduled BW, see TS 38.214 [19], clause 6.1, table 6.2.3.2-1.SEQUENCE (SIZE (5)) OF INTEGER (1..276),timeDensityTransformPrecodingTime density (OFDM symbol level) of PT-RS for DFT-s-OFDM. If the field is absent, the UE applies value d1 (see TS 38.214 [19], clause 6.1).ENUMERATED {d2} OPTIONAL -- Need S } OPTIONAL, -- Need R ... } -- TAG-PTRS-UPLINKCONFIG-STOP -- ASN1STOP
PTRS-UplinkConfig field descriptions |
---|
frequencyDensity Presence and frequency density of UL PT-RS for CP-OFDM waveform as a function of scheduled BW If the field is absent, the UE uses K_PT-RS = 2 (see TS 38.214 [19], clause 6.1). |
maxNrofPorts The maximum number of UL PTRS ports for CP-OFDM (see TS 38.214 [19], clause 6.2.3.1). |
ptrs-Power UL PTRS power boosting factor per PTRS port (see TS 38.214 [19], clause 6.1, table 6.2.3.1.3). |
resourceElementOffset Indicates the subcarrier offset for UL PTRS for CP-OFDM. If the field is absent, the UE applies the value offset00 (see TS 38.211 [16], clause 6.4.1.2.2). |
sampleDensity Sample density of PT-RS for DFT-s-OFDM, pre-DFT, indicating a set of thresholds T={NRBn, n=0,1,2,3,4}, that indicates dependency between presence of PT-RS and scheduled BW and the values of X and K the UE should use depending on the scheduled BW, see TS 38.214 [19], clause 6.1, table 6.2.3.2-1. |
timeDensity Presence and time density of UL PT-RS for CP-OFDM waveform as a function of MCS If the field is absent, the UE uses L_PT-RS = 1 (see TS 38.214 [19], clause 6.1). |
timeDensityTransformPrecoding Time density (OFDM symbol level) of PT-RS for DFT-s-OFDM. If the field is absent, the UE applies value d1 (see TS 38.214 [19], clause 6.1). |
transformPrecoderDisabled Configuration of UL PTRS without transform precoder (with CP-OFDM). |
transformPrecoderEnabled Configuration of UL PTRS with transform precoder (DFT-S-OFDM). |
The IE PUCCH-Config is used to configure UE specific PUCCH parameters (per BWP).
-- ASN1START -- TAG-PUCCH-CONFIG-START PUCCH-Config ::= SEQUENCE { resourceSetToAddModList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH-ResourceSet OPTIONAL, -- Need N resourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH-ResourceSetId OPTIONAL, -- Need N resourceToAddModList SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-Resource OPTIONAL, -- Need N resourceToReleaseList SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceId OPTIONAL, -- Need Nformat1Parameters that are common for all PUCCH resources of format 1.SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need Mformat2Parameters that are common for all PUCCH resources of format 2.SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need Mformat3Parameters that are common for all PUCCH resources of format 3.SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need Mformat4Parameters that are common for all PUCCH resources of format 4.SetupRelease { PUCCH-FormatConfig } OPTIONAL, -- Need M schedulingRequestResourceToAddModList SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfig OPTIONAL, -- Need N schedulingRequestResourceToReleaseList SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceId OPTIONAL, -- Need N multi-CSI-PUCCH-ResourceList SEQUENCE (SIZE (1..2)) OF PUCCH-ResourceId OPTIONAL, -- Need M dl-DataToUL-ACK SEQUENCE (SIZE (1..8)) OF INTEGER (0..15) OPTIONAL, -- Need M spatialRelationInfoToAddModList SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfo OPTIONAL, -- Need N spatialRelationInfoToReleaseList SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfoId OPTIONAL, -- Need N pucch-PowerControl PUCCH-PowerControl OPTIONAL, -- Need M ..., [[ resourceToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceExt-v1610 OPTIONAL, -- Need N dl-DataToUL-ACK-r16 SetupRelease { DL-DataToUL-ACK-r16 } OPTIONAL, -- Need Mul-AccessConfigListDCI-1-1-r16List of the combinations of cyclic prefix extension and UL channel access type (See TS 38.212 [17], Clause 7.3.1).SetupRelease { UL-AccessConfigListDCI-1-1-r16 } OPTIONAL, -- Need MsubslotLengthForPUCCH-r16Indicates the sub-slot length for sub-slot based PUCCH feedback in number of symbols (see TS 38.213 [13], clause 9). Value n2 corresponds to 2 symbols, value n6 corresponds to 6 symbols, value n7 corresponds to 7 symbols. For normal CP, the value is either n2 or n7. For extended CP, the value is either n2 or n6.CHOICE { normalCP-r16 ENUMERATED {n2,n7}, extendedCP-r16 ENUMERATED {n2,n6} } OPTIONAL, -- Need R dl-DataToUL-ACK-DCI-1-2-r16 SetupRelease { DL-DataToUL-ACK-DCI-1-2-r16} OPTIONAL, -- Need MnumberOfBitsForPUCCH-ResourceIndicatorDCI-1-2-r16Configuration of the number of bits for "PUCCH resource indicator" in DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.2.3).INTEGER (0..3) OPTIONAL, -- Need Rdmrs-UplinkTransformPrecodingPUCCH-r16This field is used for PUCCH formats 3 and 4 according to TS 38.211, Clause 6.4.1.3.3.1.ENUMERATED {enabled} OPTIONAL, -- Cond PI2-BPSK spatialRelationInfoToAddModListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfosDiff-r16)) OF PUCCH-SpatialRelationInfo OPTIONAL, -- Need N spatialRelationInfoToReleaseListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfosDiff-r16)) OF PUCCH-SpatialRelationInfoId OPTIONAL, -- Need N spatialRelationInfoToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos-r16)) OF PUCCH-SpatialRelationInfoExt-r16 OPTIONAL, -- Need N spatialRelationInfoToReleaseListExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos-r16)) OF PUCCH-SpatialRelationInfoId-r16 OPTIONAL, -- Need N resourceGroupToAddModList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceGroups-r16)) OF PUCCH-ResourceGroup-r16 OPTIONAL, -- Need N resourceGroupToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceGroups-r16)) OF PUCCH-ResourceGroupId-r16 OPTIONAL, -- Need Nsps-PUCCH-AN-List-r16Indicates a list of PUCCH resources for DL SPS HARQ ACK. The field maxPayloadSize is absent for the first and the last SPS-PUCCH-AN in the list. If configured, this overrides n1PUCCH-AN in SPS-config.SetupRelease { SPS-PUCCH-AN-List-r16 } OPTIONAL, -- Need M schedulingRequestResourceToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfigExt-v1610 OPTIONAL -- Need N ]] } PUCCH-FormatConfig ::= SEQUENCE {interslotFrequencyHoppingIf the field is present, the UE enables inter-slot frequency hopping when PUCCH Format 1, 3 or 4 is repeated over multiple slots. For long PUCCH over multiple slots, the intra and inter slot frequency hopping cannot be enabled at the same time for a UE. The field is not applicable for format 2. See TS 38.213 [13], clause 9.2.6.ENUMERATED {enabled} OPTIONAL, -- Need RadditionalDMRSIf the field is present, the UE enables 2 DMRS symbols per hop of a PUCCH Format 3 or 4 if both hops are more than X symbols when FH is enabled (X=4). And it enables 4 DMRS symbols for a PUCCH Format 3 or 4 with more than 2X+1 symbols when FH is disabled (X=4). The field is not applicable for format 1 and 2. See TS 38.213 [13], clause 9.2.2.ENUMERATED {true} OPTIONAL, -- Need RmaxCodeRateMax coding rate to determine how to feedback UCI on PUCCH for format 2, 3 or 4. The field is not applicable for format 1. See TS 38.213 [13], clause 9.2.5.PUCCH-MaxCodeRate OPTIONAL, -- Need RnrofSlotsNumber of slots with the same PUCCH F1, F3 or F4. When the field is absent the UE applies the value n1. The field is not applicable for format 2. See TS 38.213 [13], clause 9.2.6.ENUMERATED {n2,n4,n8} OPTIONAL, -- Need Spi2BPSKIf the field is present, the UE uses pi/2 BPSK for UCI symbols instead of QPSK for PUCCH. The field is not applicable for format 1 and 2. See TS 38.213 [13], clause 9.2.5.ENUMERATED {enabled} OPTIONAL, -- Need RsimultaneousHARQ-ACK-CSIIf the field is present, the UE uses simultaneous transmission of CSI and HARQ-ACK feedback with or without SR with PUCCH Format 2, 3 or 4. See TS 38.213 [13], clause 9.2.5. When the field is absent the UE applies the value off. The field is not applicable for format 1.ENUMERATED {true} OPTIONAL -- Need R } PUCCH-MaxCodeRate ::= ENUMERATED {zeroDot08, zeroDot15, zeroDot25, zeroDot35, zeroDot45, zeroDot60, zeroDot80} -- A set with one or more PUCCH resources PUCCH-ResourceSet ::= SEQUENCE { pucch-ResourceSetId PUCCH-ResourceSetId,resourceListPUCCH resources of format0 and format1 are only allowed in the first PUCCH resource set, i.e., in a PUCCH-ResourceSet with pucch-ResourceSetId = 0. This set may contain between 1 and 32 resources. PUCCH resources of format2, format3 and format4 are only allowed in a PUCCH-ResourceSet with pucch-ResourceSetId > 0. If present, these sets contain between 1 and 8 resources each. The UE chooses a PUCCH-Resource from this list as specified in TS 38.213 [13], clause 9.2.3. Note that this list contains only a list of resource IDs. The actual resources are configured in PUCCH-Config.SEQUENCE (SIZE (1..maxNrofPUCCH-ResourcesPerSet)) OF PUCCH-ResourceId,maxPayloadSizeMaximum number of UCI information bits that the UE may transmit using this PUCCH resource set (see TS 38.213 [13], clause 9.2.1). In a PUCCH occurrence, the UE chooses the first of its PUCCH-ResourceSet which supports the number of bits that the UE wants to transmit. The field is absent in the first set (Set0) and in the last configured set since the UE derives the maximum number of UCI information bits as specified in TS 38.213 [13], clause 9.2.1. This field can take integer values that are multiples of 4.INTEGER (4..256) OPTIONAL -- Need R } PUCCH-ResourceSetId ::= INTEGER (0..maxNrofPUCCH-ResourceSets-1) PUCCH-Resource ::= SEQUENCE {pucch-ResourceIdIdentifier of the PUCCH resource.PUCCH-ResourceId, startingPRB PRB-Id,intraSlotFrequencyHoppingEnabling intra-slot frequency hopping, applicable for all types of PUCCH formats. For long PUCCH over multiple slots, the intra and inter slot frequency hopping cannot be enabled at the same time for a UE. See TS 38.213 [13], clause 9.2.1.ENUMERATED { enabled } OPTIONAL, -- Need RsecondHopPRBIndex of first PRB after frequency hopping of PUCCH. This value is applicable for intra-slot frequency hopping (see TS 38.213 [13], clause 9.2.1) or inter-slot frequency hopping (see TS 38.213 [13], clause 9.2.6).PRB-Id OPTIONAL, -- Need RformatSelection of the PUCCH format (format 0 – 4) and format-specific parameters, see TS 38.213 [13], clause 9.2. format0 and format1 are only allowed for a resource in a first PUCCH resource set. format2, format3 and format4 are only allowed for a resource in non-first PUCCH resource set. The network can only configure format-v1610 when format is set to format2 or format3.CHOICE { format0 PUCCH-format0,format1Parameters that are common for all PUCCH resources of format 1.PUCCH-format1,format2Parameters that are common for all PUCCH resources of format 2.PUCCH-format2,format3Parameters that are common for all PUCCH resources of format 3.PUCCH-format3,format4Parameters that are common for all PUCCH resources of format 4.PUCCH-format4 } } PUCCH-ResourceExt-v1610 ::= SEQUENCE { interlaceAllocation-r16 SEQUENCE {rb-SetIndex-r16Indicates the RB set where PUCCH resource is allocated.INTEGER (0..4),interlace0-r16This is the only interlace of interlaced PUCCH Format 0 and 1 and the first interlace for interlaced PUCCH Format 2 and 3.CHOICE { scs15 INTEGER (0..9), scs30 INTEGER (0..4) } } OPTIONAL, --Need R format-v1610 CHOICE { interlace1-v1610 INTEGER (0..9), occ-v1610 SEQUENCE { occ-Length-v1610 ENUMERATED {n2,n4} OPTIONAL, -- Need M occ-Index-v1610 ENUMERATED {n0,n1,n2,n3} OPTIONAL -- Need M } } OPTIONAL, -- Need R ... } PUCCH-ResourceId ::= INTEGER (0..maxNrofPUCCH-Resources-1) PUCCH-format0 ::= SEQUENCE { initialCyclicShift INTEGER(0..11), nrofSymbols INTEGER (1..2), startingSymbolIndex INTEGER(0..13) } PUCCH-format1 ::= SEQUENCE { initialCyclicShift INTEGER(0..11), nrofSymbols INTEGER (4..14), startingSymbolIndex INTEGER(0..10), timeDomainOCC INTEGER(0..6) } PUCCH-format2 ::= SEQUENCE {nrofPRBsThe supported values are 1,2,3,4,5,6,8,9,10,12,15 and 16. The UE shall ignore this field when format-v1610 is configured.INTEGER (1..16), nrofSymbols INTEGER (1..2), startingSymbolIndex INTEGER(0..13) } PUCCH-format3 ::= SEQUENCE {nrofPRBsThe supported values are 1,2,3,4,5,6,8,9,10,12,15 and 16. The UE shall ignore this field when format-v1610 is configured.INTEGER (1..16), nrofSymbols INTEGER (4..14), startingSymbolIndex INTEGER(0..10) } PUCCH-format4 ::= SEQUENCE { nrofSymbols INTEGER (4..14),occ-LengthIndicates the orthogonal cover code length (see TS 38.213 [13], clause 9.2.1). This field is applicable when useInterlacePUCCH-PUSCH-r16 is configured.ENUMERATED {n2,n4},occ-IndexIndicates the orthogonal cover code index (see TS 38.213 [13], clause 9.2.1). This field is applicable when useInterlacePUCCH-PUSCH-r16 is configured.ENUMERATED {n0,n1,n2,n3}, startingSymbolIndex INTEGER(0..10) } PUCCH-ResourceGroup-r16 ::= SEQUENCE { pucch-ResourceGroupId-r16 PUCCH-ResourceGroupId-r16, resourcePerGroupList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourcesPerGroup-r16)) OF PUCCH-ResourceId } PUCCH-ResourceGroupId-r16 ::= INTEGER (0..maxNrofPUCCH-ResourceGroups-1-r16) DL-DataToUL-ACK-r16 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (-1..15) DL-DataToUL-ACK-DCI-1-2-r16 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (0..15) UL-AccessConfigListDCI-1-1-r16 ::= SEQUENCE (SIZE (1..16)) OF INTEGER (0..15) -- TAG-PUCCH-CONFIG-STOP -- ASN1STOP
PUCCH-Config field descriptions |
---|
dl-DataToUL-ACK, dl-DataToUL-ACK-DCI-1-2 List of timing for given PDSCH to the DL ACK (see TS 38.213 [13], clause 9.1.2). The field dl-DataToUL-ACKapplies to DCI format 1_1 and the field dl-DataToUL-ACK-DCI-1-2applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.2.3). If dl-DataToUL-ACK-r16 is signalled, UE shall ignore the dl-DataToUL-ACK(without suffix). The value -1 corresponds to "inapplicable value" for the case where the A/N feedback timing is not explicitly included at the time of scheduling PDSCH. |
dmrs-UplinkTransformPrecodingPUCCH This field is used for PUCCH formats 3 and 4 according to TS 38.211, Clause 6.4.1.3.3.1. |
format1 Parameters that are common for all PUCCH resources of format 1. |
format2 Parameters that are common for all PUCCH resources of format 2. |
format3 Parameters that are common for all PUCCH resources of format 3. |
format4 Parameters that are common for all PUCCH resources of format 4. |
numberOfBitsForPUCCH-ResourceIndicatorDCI-1-2 Configuration of the number of bits for "PUCCH resource indicator" in DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.2.3). |
resourceGroupToAddModList, resourceGroupToReleaseList Lists for adding and releasing groups of PUCCH resources that can be updated simultaneously for spatial relations with a MAC CE. |
resourceSetToAddModList, resourceSetToReleaseList Lists for adding and releasing PUCCH resource sets (see TS 38.213 [13], clause 9.2). |
resourceToAddModList, resourceToAddModListExt, resourceToReleaseList Lists for adding and releasing PUCCH resources applicable for the UL BWP and serving cell in which the PUCCH-Config is defined. The resources defined herein are referred to from other parts of the configuration to determine which resource the UE shall use for which report. If the network includes of resourceToAddModListExt, it includes the same number of entries, and listed in the same order, as in resourceToAddModList. |
spatialRelationInfoToAddModList, spatialRelationInfoToAddModListSizeExt , spatialRelationInfoToAddModListExt Configuration of the spatial relation between a reference RS and PUCCH. Reference RS can be SSB/CSI-RS/SRS. If the list has more than one element, MAC-CE selects a single element (see TS 38.321 [3], clause 5.18.8 and TS 38.213 [13], clause 9.2.2). The UE shall consider entries in spatialRelationInfoToAddModList and in spatialRelationInfoToAddModListSizeExt as a single list, i.e. an entry created using spatialRelationInfoToAddModList can be modified using spatialRelationInfoToAddModListSizeExt (or deleted using spatialRelationInfoToReleaseListSizeExt) and vice-versa. If the network includes spatialRelationInfoToAddModListExt, it includes the same number of entries, and listed in the same order, as in the concatenation of spatialRelationInfoToAddModList and of spatialRelationInfoToAddModListSizeExt. |
spatialRelationInfoToReleaseList, spatialRelationInfoToReleaseListSizeExt, spatialRelationInfoToReleaseListExt Lists of spatial relation configurations between a reference RS and PUCCH to be released by the UE. |
sps-PUCCH-AN-List Indicates a list of PUCCH resources for DL SPS HARQ ACK. The field maxPayloadSize is absent for the first and the last SPS-PUCCH-AN in the list. If configured, this overrides n1PUCCH-AN in SPS-config. |
subslotLengthForPUCCH Indicates the sub-slot length for sub-slot based PUCCH feedback in number of symbols (see TS 38.213 [13], clause 9). Value n2 corresponds to 2 symbols, value n6 corresponds to 6 symbols, value n7 corresponds to 7 symbols. For normal CP, the value is either n2 or n7. For extended CP, the value is either n2 or n6. |
ul-AccessConfigListDCI-1-1 List of the combinations of cyclic prefix extension and UL channel access type (See TS 38.212 [17], Clause 7.3.1). |
PUCCH-format3 field descriptions |
---|
nrofPRBs The supported values are 1,2,3,4,5,6,8,9,10,12,15 and 16. The UE shall ignore this field when format-v1610 is configured. |
PUCCH-FormatConfig field descriptions |
---|
additionalDMRS If the field is present, the UE enables 2 DMRS symbols per hop of a PUCCH Format 3 or 4 if both hops are more than X symbols when FH is enabled (X=4). And it enables 4 DMRS symbols for a PUCCH Format 3 or 4 with more than 2X+1 symbols when FH is disabled (X=4). The field is not applicable for format 1 and 2. See TS 38.213 [13], clause 9.2.2. |
interslotFrequencyHopping If the field is present, the UE enables inter-slot frequency hopping when PUCCH Format 1, 3 or 4 is repeated over multiple slots. For long PUCCH over multiple slots, the intra and inter slot frequency hopping cannot be enabled at the same time for a UE. The field is not applicable for format 2. See TS 38.213 [13], clause 9.2.6. |
maxCodeRate Max coding rate to determine how to feedback UCI on PUCCH for format 2, 3 or 4. The field is not applicable for format 1. See TS 38.213 [13], clause 9.2.5. |
nrofSlots Number of slots with the same PUCCH F1, F3 or F4. When the field is absent the UE applies the value n1. The field is not applicable for format 2. See TS 38.213 [13], clause 9.2.6. |
pi2BPSK If the field is present, the UE uses pi/2 BPSK for UCI symbols instead of QPSK for PUCCH. The field is not applicable for format 1 and 2. See TS 38.213 [13], clause 9.2.5. |
rb-SetIndex Indicates the RB set where PUCCH resource is allocated. |
simultaneousHARQ-ACK-CSI If the field is present, the UE uses simultaneous transmission of CSI and HARQ-ACK feedback with or without SR with PUCCH Format 2, 3 or 4. See TS 38.213 [13], clause 9.2.5. When the field is absent the UE applies the value off. The field is not applicable for format 1. |
PUCCH-Resource, PUCCH-ResourceExtfield descriptions |
---|
format Selection of the PUCCH format (format 0 – 4) and format-specific parameters, see TS 38.213 [13], clause 9.2. format0 and format1 are only allowed for a resource in a first PUCCH resource set. format2, format3 and format4 are only allowed for a resource in non-first PUCCH resource set. The network can only configure format-v1610 when format is set to format2 or format3. |
interlace0 This is the only interlace of interlaced PUCCH Format 0 and 1 and the first interlace for interlaced PUCCH Format 2 and 3. |
interlace1 A second interlace, in addition to interlace 0, as specified in TS 38.213 [13], clause 9.2.1. For 15kHz SCS, values {0..9} are applicable; for 30kHz SCS, values {0..4} are applicable. For 15kHz SCS, the values of interlace1 shall satisfy interlace1=mod(interlace0+X,10) where X=1, -1, or 5. |
intraSlotFrequencyHopping Enabling intra-slot frequency hopping, applicable for all types of PUCCH formats. For long PUCCH over multiple slots, the intra and inter slot frequency hopping cannot be enabled at the same time for a UE. See TS 38.213 [13], clause 9.2.1. |
occ-Index Indicates the orthogonal cover code index (see TS 38.213 [13], clause 9.2.1). This field is applicable when useInterlacePUCCH-PUSCH-r16 is configured. |
occ-Length Indicates the orthogonal cover code length (see TS 38.213 [13], clause 9.2.1). This field is applicable when useInterlacePUCCH-PUSCH-r16 is configured. |
pucch-ResourceId Identifier of the PUCCH resource. |
secondHopPRB Index of first PRB after frequency hopping of PUCCH. This value is applicable for intra-slot frequency hopping (see TS 38.213 [13], clause 9.2.1) or inter-slot frequency hopping (see TS 38.213 [13], clause 9.2.6). |
PUCCH-ResourceSet field descriptions |
---|
maxPayloadSize Maximum number of UCI information bits that the UE may transmit using this PUCCH resource set (see TS 38.213 [13], clause 9.2.1). In a PUCCH occurrence, the UE chooses the first of its PUCCH-ResourceSet which supports the number of bits that the UE wants to transmit. The field is absent in the first set (Set0) and in the last configured set since the UE derives the maximum number of UCI information bits as specified in TS 38.213 [13], clause 9.2.1. This field can take integer values that are multiples of 4. |
resourceList PUCCH resources of format0 and format1 are only allowed in the first PUCCH resource set, i.e., in a PUCCH-ResourceSet with pucch-ResourceSetId = 0. This set may contain between 1 and 32 resources. PUCCH resources of format2, format3 and format4 are only allowed in a PUCCH-ResourceSet with pucch-ResourceSetId > 0. If present, these sets contain between 1 and 8 resources each. The UE chooses a PUCCH-Resource from this list as specified in TS 38.213 [13], clause 9.2.3. Note that this list contains only a list of resource IDs. The actual resources are configured in PUCCH-Config. |
Conditional Presence | Explanation |
---|---|
PI2-BPSK | The field is optionally present, Need R, if format3 and/or format4 are configured and pi2BPSK is configured in each of them. It is absent, Need R otherwise. |
The IE PUCCH-ConfigCommon is used to configure the cell specific PUCCH parameters.
-- ASN1START -- TAG-PUCCH-CONFIGCOMMON-START PUCCH-ConfigCommon ::= SEQUENCE {pucch-ResourceCommonAn entry into a 16-row table where each row configures a set of cell-specific PUCCH resources/parameters. The UE uses those PUCCH resources until it is provided with a dedicated PUCCH-Config (e.g. during initial access) on the initial uplink BWP. Once the network provides a dedicated PUCCH-Config for that bandwidth part the UE applies that one instead of the one provided in this field (see TS 38.213 [13], clause 9.2).INTEGER (0..15) OPTIONAL, -- Cond InitialBWP-Onlypucch-GroupHoppingConfiguration of group- and sequence hopping for all the PUCCH formats 0, 1, 3 and 4. Value neither implies neither group or sequence hopping is enabled. Value enable enables group hopping and disables sequence hopping. Value disable disables group hopping and enables sequence hopping (see TS 38.211 [16], clause 6.3.2.2).ENUMERATED { neither, enable, disable },hoppingIdCell-specific scrambling ID for group hopping and sequence hopping if enabled, see TS 38.211 [16], clause 6.3.2.2.INTEGER (0..1023) OPTIONAL, -- Need Rp0-nominalPower control parameter P0 for PUCCH transmissions. Value in dBm. Only even values (step size 2) allowed (see TS 38.213 [13], clause 7.2).INTEGER (-202..24) OPTIONAL, -- Need R ... } -- TAG-PUCCH-CONFIGCOMMON-STOP -- ASN1STOP
PUCCH-ConfigCommon field descriptions |
---|
hoppingId Cell-specific scrambling ID for group hopping and sequence hopping if enabled, see TS 38.211 [16], clause 6.3.2.2. |
p0-nominal Power control parameter P0 for PUCCH transmissions. Value in dBm. Only even values (step size 2) allowed (see TS 38.213 [13], clause 7.2). |
pucch-GroupHopping Configuration of group- and sequence hopping for all the PUCCH formats 0, 1, 3 and 4. Value neither implies neither group or sequence hopping is enabled. Value enable enables group hopping and disables sequence hopping. Value disable disables group hopping and enables sequence hopping (see TS 38.211 [16], clause 6.3.2.2). |
pucch-ResourceCommon An entry into a 16-row table where each row configures a set of cell-specific PUCCH resources/parameters. The UE uses those PUCCH resources until it is provided with a dedicated PUCCH-Config (e.g. during initial access) on the initial uplink BWP. Once the network provides a dedicated PUCCH-Config for that bandwidth part the UE applies that one instead of the one provided in this field (see TS 38.213 [13], clause 9.2). |
Conditional Presence | Explanation |
---|---|
InitialBWP-Only | The field is mandatory present in the PUCCH-ConfigCommon of the initial BWP (BWP#0) in SIB1. It is absent in other BWPs. |
The IE PUCCH-ConfigurationList is used to configure UE specific PUCCH parameters (per BWP) for two simultaneously constructed HARQ-ACK codebooks. See TS 38.213 [13], clause 9.1.
-- ASN1START -- TAG-PUCCH-CONFIGURATIONLIST-START PUCCH-ConfigurationList-r16 ::= SEQUENCE (SIZE (1..2)) OF PUCCH-Config -- TAG-PUCCH-CONFIGURATIONLIST-STOP -- ASN1STOP
The IE PUCCH-PathlossReferenceRS-Id is an ID for a reference signal (RS) configured as PUCCH pathloss reference (see TS 38.213 [13], clause 7.2).
-- ASN1START -- TAG-PUCCH-PATHLOSSREFERENCERS-ID-START PUCCH-PathlossReferenceRS-Id ::= INTEGER (0..maxNrofPUCCH-PathlossReferenceRSs-1) PUCCH-PathlossReferenceRS-Id-v1610 ::= INTEGER (maxNrofPUCCH-PathlossReferenceRSs..maxNrofPUCCH-PathlossReferenceRSs-1-r16) -- TAG-PUCCH-PATHLOSSREFERENCERS-ID-STOP -- ASN1STOP
The IE PUCCH-PowerControl is used to configure UE-specific parameters for the power control of PUCCH.
-- ASN1START -- TAG-PUCCH-POWERCONTROL-START PUCCH-PowerControl ::= SEQUENCE {deltaF-PUCCH-f0deltaF for PUCCH format 0 with 1dB step size (see TS 38.213 [13], clause 7.2).INTEGER (-16..15) OPTIONAL, -- Need RdeltaF-PUCCH-f1deltaF for PUCCH format 1 with 1dB step size (see TS 38.213 [13], clause 7.2).INTEGER (-16..15) OPTIONAL, -- Need RdeltaF-PUCCH-f2deltaF for PUCCH format 2 with 1dB step size (see TS 38.213 [13], clause 7.2).INTEGER (-16..15) OPTIONAL, -- Need RdeltaF-PUCCH-f3deltaF for PUCCH format 3 with 1dB step size (see TS 38.213 [13], clause 7.2).INTEGER (-16..15) OPTIONAL, -- Need RdeltaF-PUCCH-f4deltaF for PUCCH format 4 with 1dB step size (see TS 38.213 [13], clause 7.2).INTEGER (-16..15) OPTIONAL, -- Need Rp0-SetA set with dedicated P0 values for PUCCH, i.e., {P01, P02,... } (see TS 38.213 [13], clause 7.2).SEQUENCE (SIZE (1..maxNrofPUCCH-P0-PerSet)) OF P0-PUCCH OPTIONAL, -- Need M pathlossReferenceRSs SEQUENCE (SIZE (1..maxNrofPUCCH-PathlossReferenceRSs)) OF PUCCH-PathlossReferenceRS OPTIONAL, -- Need MtwoPUCCH-PC-AdjustmentStatesNumber of PUCCH power control adjustment states maintained by the UE (i.e., g(i)). If the field is present (n2) the UE maintains two power control states (i.e., g(i,0) and g(i,1)). If the field is absent, it maintains one power control state (i.e., g(i,0)) (see TS 38.213 [13], clause 7.2).ENUMERATED {twoStates} OPTIONAL, -- Need S ..., [[ pathlossReferenceRSs-v1610 SetupRelease { PathlossReferenceRSs-v1610 } OPTIONAL -- Need M ]] } P0-PUCCH ::= SEQUENCE { p0-PUCCH-Id P0-PUCCH-Id,p0-PUCCH-ValueP0 value for PUCCH with 1dB step size.INTEGER (-16..15) } P0-PUCCH-Id ::= INTEGER (1..8) PathlossReferenceRSs-v1610 ::= SEQUENCE (SIZE (1..maxNrofPUCCH-PathlossReferenceRSsDiff-r16)) OF PUCCH-PathlossReferenceRS-r16 PUCCH-PathlossReferenceRS ::= SEQUENCE { pucch-PathlossReferenceRS-Id PUCCH-PathlossReferenceRS-Id, referenceSignal CHOICE { ssb-Index SSB-Index, csi-RS-Index NZP-CSI-RS-ResourceId } } PUCCH-PathlossReferenceRS-r16 ::= SEQUENCE { pucch-PathlossReferenceRS-Id-r16 PUCCH-PathlossReferenceRS-Id-v1610, referenceSignal-r16 CHOICE { ssb-Index-r16 SSB-Index, csi-RS-Index-r16 NZP-CSI-RS-ResourceId } } -- TAG-PUCCH-POWERCONTROL-STOP -- ASN1STOP
P0-PUCCH field descriptions |
---|
p0-PUCCH-Value P0 value for PUCCH with 1dB step size. |
PUCCH-PowerControl field descriptions |
---|
deltaF-PUCCH-f0 deltaF for PUCCH format 0 with 1dB step size (see TS 38.213 [13], clause 7.2). |
deltaF-PUCCH-f1 deltaF for PUCCH format 1 with 1dB step size (see TS 38.213 [13], clause 7.2). |
deltaF-PUCCH-f2 deltaF for PUCCH format 2 with 1dB step size (see TS 38.213 [13], clause 7.2). |
deltaF-PUCCH-f3 deltaF for PUCCH format 3 with 1dB step size (see TS 38.213 [13], clause 7.2). |
deltaF-PUCCH-f4 deltaF for PUCCH format 4 with 1dB step size (see TS 38.213 [13], clause 7.2). |
p0-Set A set with dedicated P0 values for PUCCH, i.e., {P01, P02,... } (see TS 38.213 [13], clause 7.2). |
pathlossReferenceRSs, pathlossReferenceRSs-v1610 A set of Reference Signals (e.g. a CSI-RS config or a SS block) to be used for PUCCH pathloss estimation. Up to maxNrofPUCCH-PathlossReference-RSs may be configured. If the field is not configured, the UE uses the SSB as reference signal (see TS 38.213 [13], clause 7.2).The set includes Reference Signals indicated in pathlossReferenceRSs (without suffix) and in pathlossReferenceRSs-v1610. The UE maintains pathlossReferenceRSs and pathlossReferenceRSs-v1610 separately: Receiving pathlossReferenceRSs-v1610 set to release releases only the entries that were configured by pathlossReferenceRSs-v1610, and receiving pathlossReferenceRSs-v1610 set to setup replaces only the entries that were configured by pathlossReferenceRSs-v1610 with the newly signalled entries. |
twoPUCCH-PC-AdjustmentStates Number of PUCCH power control adjustment states maintained by the UE (i.e., g(i)). If the field is present (n2) the UE maintains two power control states (i.e., g(i,0) and g(i,1)). If the field is absent, it maintains one power control state (i.e., g(i,0)) (see TS 38.213 [13], clause 7.2). |
The IE PUCCH-SpatialRelationInfo is used to configure the spatial setting for PUCCH transmission and the parameters for PUCCH power control, see TS 38.213, [13], clause 9.2.2.
-- ASN1START -- TAG-PUCCH-SPATIALRELATIONINFO-START PUCCH-SpatialRelationInfo ::= SEQUENCE {pucch-SpatialRelationInfoIdWhen pucch-SpatialRelationInfoId-v1610 is configured, the UE shall ignore pucch-SpatialRelationInfoId (without suffix). If pucch-SpatialRelationInfoId-v1610 is absent, the UE shall use the pucch-SpatialRelationInfoId (without suffix).PUCCH-SpatialRelationInfoId,servingCellIdIf the field is absent, the UE applies the ServCellId of the serving cell in which this PUCCH-SpatialRelationInfo is configuredServCellIndex OPTIONAL, -- Need S referenceSignal CHOICE { ssb-Index SSB-Index, csi-RS-Index NZP-CSI-RS-ResourceId, srs PUCCH-SRS }, pucch-PathlossReferenceRS-Id PUCCH-PathlossReferenceRS-Id, p0-PUCCH-Id P0-PUCCH-Id, closedLoopIndex ENUMERATED { i0, i1 } } PUCCH-SpatialRelationInfoExt-r16 ::= SEQUENCE { pucch-SpatialRelationInfoId-v1610 PUCCH-SpatialRelationInfoId-v1610 OPTIONAL, -- Need S pucch-PathlossReferenceRS-Id-v1610 PUCCH-PathlossReferenceRS-Id-v1610 OPTIONAL, --Need R ... } PUCCH-SRS ::= SEQUENCE { resource SRS-ResourceId, uplinkBWP BWP-Id } -- TAG-PUCCH-SPATIALRELATIONINFO-STOP -- ASN1STOP
PUCCH-SpatialRelationInfo field descriptions |
---|
pucch-PathLossReferenceRS-Id When pucch-PathLossReferenceRS-Id-v1610 is configured, the UE shall ignore pucch-PathLossReferenceRS-Id (without suffix). |
pucch-SpatialRelationInfoId When pucch-SpatialRelationInfoId-v1610 is configured, the UE shall ignore pucch-SpatialRelationInfoId (without suffix). If pucch-SpatialRelationInfoId-v1610 is absent, the UE shall use the pucch-SpatialRelationInfoId (without suffix). |
servingCellId If the field is absent, the UE applies the ServCellId of the serving cell in which this PUCCH-SpatialRelationInfo is configured |
The IE PUCCH-SpatialRelationInfo-Id is used to identify a PUCCH-SpatialRelationInfo
-- ASN1START -- TAG-PUCCH-SPATIALRELATIONINFO-START PUCCH-SpatialRelationInfoId ::= INTEGER (1..maxNrofSpatialRelationInfos) PUCCH-SpatialRelationInfoId-r16 ::= INTEGER (1..maxNrofSpatialRelationInfos-r16) PUCCH-SpatialRelationInfoId-v1610::= INTEGER (maxNrofSpatialRelationInfos-plus-1..maxNrofSpatialRelationInfos-r16) -- TAG-PUCCH-SPATIALRELATIONINFO-STOP -- ASN1STOP
The IE PUCCH-TPC-CommandConfig is used to configure the UE for extracting TPC commands for PUCCH from a group-TPC messages on DCI.
-- ASN1START -- TAG-PUCCH-TPC-COMMANDCONFIG-START PUCCH-TPC-CommandConfig ::= SEQUENCE {tpc-IndexPCellAn index determining the position of the first bit of TPC command (applicable to the SpCell) inside the DCI format 2-2 payload.INTEGER (1..15) OPTIONAL, -- Cond PDCCH-OfSpcelltpc-IndexPUCCH-SCellAn index determining the position of the first bit of TPC command (applicable to the PUCCH SCell) inside the DCI format 2-2 payload.INTEGER (1..15) OPTIONAL, -- Cond PDCCH-ofSpCellOrPUCCH-SCell ... } -- TAG-PUCCH-TPC-COMMANDCONFIG-STOP -- ASN1STOP
PUCCH-TPC-CommandConfig field descriptions |
---|
tpc-IndexPCell An index determining the position of the first bit of TPC command (applicable to the SpCell) inside the DCI format 2-2 payload. |
tpc-IndexPUCCH-SCell An index determining the position of the first bit of TPC command (applicable to the PUCCH SCell) inside the DCI format 2-2 payload. |
Conditional Presence | Explanation |
---|---|
PDCCH-OfSpcell | The field is mandatory present if the PUCCH-TPC-CommandConfig is provided in the PDCCH-Config for the SpCell. Otherwise, the field is absent, Need R. |
PDCCH-ofSpCellOrPUCCH-SCell | The field is mandatory present if the PUCCH-TPC-CommandConfig is provided in the PDCCH-Config for the PUCCH-SCell. The field is optionally present, need R, if the UE is configured with a PUCCH SCell in this cell group and if the PUCCH-TPC-CommandConfig is provided in the PDCCH-Config for the SpCell. Otherwise, the field is absent, Need R. |
The IE PUSCH-Config is used to configure the UE specific PUSCH parameters applicable to a particular BWP.
-- ASN1START -- TAG-PUSCH-CONFIG-START PUSCH-Config ::= SEQUENCE {dataScramblingIdentityPUSCHIdentifier used to initialise data scrambling (c_init) for PUSCH. If the field is absent, the UE applies the physical cell ID. (see TS 38.211 [16], clause 6.3.1.1).INTEGER (0..1023) OPTIONAL, -- Need StxConfigWhether UE uses codebook based or non-codebook based transmission (see TS 38.214 [19], clause 6.1.1). If the field is absent, the UE transmits PUSCH on one antenna port, see TS 38.214 [19], clause 6.1.1.ENUMERATED {codebook, nonCodebook} OPTIONAL, -- Need S dmrs-UplinkForPUSCH-MappingTypeA SetupRelease { DMRS-UplinkConfig } OPTIONAL, -- Need M dmrs-UplinkForPUSCH-MappingTypeB SetupRelease { DMRS-UplinkConfig } OPTIONAL, -- Need M pusch-PowerControl PUSCH-PowerControl OPTIONAL, -- Need MfrequencyHoppingThe value intraSlot enables 'Intra-slot frequency hopping' and the value interSlot enables 'Inter-slot frequency hopping'. If the field is absent, frequency hopping is not configured for 'pusch-RepTypeA' (see TS 38.214 [19], clause 6.3). The field frequencyHopping applies to DCI format 0_0 and 0_1 for 'pusch-RepTypeA'.ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need S frequencyHoppingOffsetLists SEQUENCE (SIZE (1..4)) OF INTEGER (1.. maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Need M resourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},pusch-TimeDomainAllocationListList of time domain allocations for timing of UL assignment to UL data (see TS 38.214 [19], table 6.1.2.1.1-1). The field pusch-TimeDomainAllocationList applies to DCI formats 0_0 or DCI format 0_1 when the field pusch-TimeDomainAllocationListDCI-0-1 is not configured (see TS 38.214 [19], table 6.1.2.1.1-1 and table 6.1.2.1.1-1A). The network does not configure the pusch-TimeDomainAllocationList (without suffix) simultaneously with the pusch-TimeDomainAllocationListDCI-0-2-r16orpusch-TimeDomainAllocationListDCI-0-1-r16 or pusch-TimeDomainAllocationListForMultiPUSCH-r16.SetupRelease { PUSCH-TimeDomainResourceAllocationList } OPTIONAL, -- Need Mpusch-AggregationFactorNumber of repetitions for data (see TS 38.214 [19], clause 6.1.2.1). If the field is absent the UE applies the value 1.ENUMERATED { n2, n4, n8 } OPTIONAL, -- Need S mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S mcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need StransformPrecoderThe UE specific selection of transformer precoder for PUSCH (see TS 38.214 [19], clause 6.1.3). When the field is absent the UE applies the value of the field msg3-transformPrecoder.ENUMERATED {enabled, disabled} OPTIONAL, -- Need S codebookSubset ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent,nonCoherent} OPTIONAL, -- Cond codebookBased maxRank INTEGER (1..4) OPTIONAL, -- Cond codebookBasedrbg-SizeSelection between configuration 1 and configuration 2 for RBG size for PUSCH. The UE does not apply this field if resourceAllocation is set to resourceAllocationType1. Otherwise, the UE applies the value config1 when the field is absent (see TS 38.214 [19], clause 6.1.2.2.1).ENUMERATED { config2} OPTIONAL, -- Need S uci-OnPUSCH SetupRelease { UCI-OnPUSCH} OPTIONAL, -- Need Mtp-pi2BPSKEnables pi/2-BPSK modulation with transform precoding if the field is present and disables it otherwise.ENUMERATED {enabled} OPTIONAL, -- Need S ..., [[minimumSchedulingOffsetK2-r16List of minimum K2 values.Minimum K2 parameter denotes minimum applicable value(s) for the Time domain resource assignment table for PUSCH (see TS 38.214 [19], clause 6.1.2.1).SetupRelease { MinSchedulingOffsetK2-Values-r16 } OPTIONAL, -- Need Mul-AccessConfigListDCI-0-1-r16List of the combinations of cyclic prefix extension, channel access priority class (CAPC), and UL channel access type (see TS 38.212 [17], Table 7.3.1.1.2-35).SetupRelease { UL-AccessConfigListDCI-0-1-r16 } OPTIONAL, -- Need M -- Start of the parameters for DCI format 0_2 introduced in V16.1.0harq-ProcessNumberSizeDCI-0-2-r16Configure the number of bits for the field "HARQ process number" in DCI format 0_2 (see TS 38.212 [17], clause 7.3.1).INTEGER (0..4) OPTIONAL, -- Need Rdmrs-SequenceInitializationDCI-0-2-r16Configure whether the field "DMRS Sequence Initialization" is present or not in DCI format 0_2. If the field is absent, then 0 bit for the field "DMRS Sequence Initialization" in DCI format 0_2. If the field is present, then the number of bits is determined in the same way as DCI format 0_1 (see TS 38.212 [17], clause 7.3.1).ENUMERATED {enabled} OPTIONAL, -- Need SnumberOfBitsForRV-DCI-0-2-r16Configures the number of bits for "Redundancy version" in the DCI format 0_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.214 [19], clause 6.1.2.1).INTEGER (0..2) OPTIONAL, -- Need RantennaPortsFieldPresenceDCI-0-2-r16Configure the presence of "Antenna ports" field in DCI format 0_2. When the field is configured, then the "Antenna ports" field is present in DCI format 0_2. Otherwise, the field size is set to 0 for DCI format 0_2 (See TS 38.212 [17], clause 7.3.1.1.3). If neither dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2 nor dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2 is configured, this field is absent.ENUMERATED {enabled} OPTIONAL, -- Need S dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2-r16 SetupRelease { DMRS-UplinkConfig } OPTIONAL, -- Need M dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2-r16 SetupRelease { DMRS-UplinkConfig } OPTIONAL, -- Need MfrequencyHoppingDCI-0-2-r16Indicate the frequency hopping scheme for DCI format 0_2. The value intraSlot enables 'intra-slot frequency hopping', and the value interRepetition enables 'Inter-repetition frequency hopping', and the value interSlot enables 'Inter-slot frequency hopping'. When pusch-RepTypeIndicatorDCI-0-2 is set to 'pusch-RepTypeA', the frequency hopping scheme can be chosen between 'intra-slot frequency hopping and 'inter-slot frequency hopping' if enabled. When pusch-RepTypeIndicatorDCI-0-2 is set to 'pusch-RepTypeB', the frequency hopping scheme can be chosen between 'inter-repetition frequency hopping' and 'inter-slot frequency hopping' if enabled. If the field is absent, frequency hopping is not configured for DCI format 0_2 (see TS 38.214 [19], clause 6.3).CHOICE { pusch-RepTypeA ENUMERATED {intraSlot, interSlot}, pusch-RepTypeB ENUMERATED {interRepetition, interSlot} } OPTIONAL, -- Need S frequencyHoppingOffsetListsDCI-0-2-r16 SetupRelease { FrequencyHoppingOffsetListsDCI-0-2-r16} OPTIONAL, -- Need M codebookSubsetDCI-0-2-r16 ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent,nonCoherent} OPTIONAL, -- Cond codebookBased invalidSymbolPatternIndicatorDCI-0-2-r16 ENUMERATED {enabled} OPTIONAL, -- Need S maxRankDCI-0-2-r16 INTEGER (1..4) OPTIONAL, -- Cond codebookBased mcs-TableDCI-0-2-r16 ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S mcs-TableTransformPrecoderDCI-0-2-r16 ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S priorityIndicatorDCI-0-2-r16 ENUMERATED {enabled} OPTIONAL, -- Need S pusch-RepTypeIndicatorDCI-0-2-r16 ENUMERATED { pusch-RepTypeA, pusch-RepTypeB} OPTIONAL, -- Need R resourceAllocationDCI-0-2-r16 ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch} OPTIONAL, -- Need MresourceAllocationType1GranularityDCI-0-2-r16Configures the scheduling granularity applicable for both the starting point and length indication for resource allocation type 1 in DCI format 0_2. If this field is absent, the granularity is 1 PRB (see TS 38.214 [19], clause 6.1.2.2.2).ENUMERATED { n2,n4,n8,n16 } OPTIONAL, -- Need S uci-OnPUSCH-ListDCI-0-2-r16 SetupRelease { UCI-OnPUSCH-ListDCI-0-2-r16} OPTIONAL, -- Need Mpusch-TimeDomainAllocationListDCI-0-2-r16Configuration of the time domain resource allocation (TDRA) table for DCI format 0_2 (see TS 38.214 [19], clause 6.1.2, table 6.1.2.1.1-1B).SetupRelease { PUSCH-TimeDomainResourceAllocationList-r16 } OPTIONAL, -- Need M -- End of the parameters for DCI format 0_2 introduced in V16.1.0 -- Start of the parameters for DCI format 0_1 introduced in V16.1.0pusch-TimeDomainAllocationListDCI-0-1-r16Configuration of the time domain resource allocation (TDRA) table for DCI format 0_1 (see TS 38.214 [19], clause 6.1, table 6.1.2.1.1-1A).SetupRelease { PUSCH-TimeDomainResourceAllocationList-r16 } OPTIONAL, -- Need M invalidSymbolPatternIndicatorDCI-0-1-r16 ENUMERATED {enabled} OPTIONAL, -- Need S priorityIndicatorDCI-0-1-r16 ENUMERATED {enabled} OPTIONAL, -- Need S pusch-RepTypeIndicatorDCI-0-1-r16 ENUMERATED { pusch-RepTypeA, pusch-RepTypeB} OPTIONAL, -- Need RfrequencyHoppingDCI-0-1-r16Indicates the frequency hopping scheme for DCI format 0_1 when pusch-RepTypeIndicatorDCI-0-1 is set to 'pusch-RepTypeB', The value interRepetition enables 'Inter-repetition frequency hopping', and the value interSlot enables 'Inter-slot frequency hopping'. If the field is absent, frequency hopping is not configured for DCI format 0_1 for 'pusch-RepTypeB'(see TS 38.214 [19], clause 6.1).ENUMERATED {interRepetition, interSlot} OPTIONAL, -- Cond RepTypeB uci-OnPUSCH-ListDCI-0-1-r16 SetupRelease { UCI-OnPUSCH-ListDCI-0-1-r16 } OPTIONAL, -- Need M -- End of the parameters for DCI format 0_1 introduced in V16.1.0invalidSymbolPattern-r16Indicates one pattern for invalid symbols for PUSCH transmission repetition type B applicable to both DCI format 0_1 and 0_2. If InvalidSymbolPattern is not configured, semi-static flexible symbols are used for PUSCH. Segmentation occurs only around semi-static DL symbols (see TS 38.214 [19] clause 6.1).InvalidSymbolPattern-r16 OPTIONAL, -- Need S pusch-PowerControl-v1610 SetupRelease {PUSCH-PowerControl-v1610} OPTIONAL, -- Need Mul-FullPowerTransmission-r16Configures the UE with UL full power transmission mode as specified in TS 38.213[13].ENUMERATED {fullpower, fullpowerMode1, fullpowerMode2} OPTIONAL, -- Need Rpusch-TimeDomainAllocationListForMultiPUSCH-r16Configuration of the time domain resource allocation (TDRA) table for multiple PUSCH (see TS 38.214 [19], clause 6.1.2). The network configures at most 64 rows in this TDRA table in PUSCH-TimeDomainResourceAllocationList-r16 configured by this field. This field is not configured simultaneously with pusch-AggregationFactor.The network does not configure the pusch-TimeDomainAllocationListForMultiPUSCH-r16 simultaneously with the pusch-TimeDomainAllocationListDCI-0-1-r16.SetupRelease { PUSCH-TimeDomainResourceAllocationList-r16 } OPTIONAL, -- Need MnumberOfInvalidSymbolsForDL-UL-Switching-r16Indicates the number of symbols after the last semi-static DL symbol that are invalid symbols for PUSCH repetition Type B. If it is absent, no symbol is explicitly defined for DL-to-UL switching (see TS 38.214 [19], clause 6.1).INTEGER (1..4) OPTIONAL -- Cond RepTypeB2 ]] } UCI-OnPUSCH ::= SEQUENCE {betaOffsetsSelection between and configuration of dynamic and semi-static beta-offset for DCI formats other than DCI format 0_2. If the field is not configured, the UE applies the value 'semiStatic' (see TS 38.213 [13], clause 9.3).CHOICE { dynamic SEQUENCE (SIZE (4)) OF BetaOffsets, semiStatic BetaOffsets } OPTIONAL, -- Need MscalingIndicates a scaling factor to limit the number of resource elements assigned to UCI on PUSCH for DCI formats other than DCI format 0_2. Value f0p5 corresponds to 0.5, value f0p65 corresponds to 0.65, and so on. The value configured herein is applicable for PUSCH with configured grant (see TS 38.212 [17], clause 6.3).ENUMERATED { f0p5, f0p65, f0p8, f1 } } MinSchedulingOffsetK2-Values-r16 ::= SEQUENCE (SIZE (1..maxNrOfMinSchedulingOffsetValues-r16)) OF INTEGER (0..maxK2-SchedulingOffset-r16) UCI-OnPUSCH-DCI-0-2-r16 ::= SEQUENCE {betaOffsetsDCI-0-2-r16Configuration of beta-offset for DCI format 0_2. If semiStaticDCI-0-2 is chosen, the UE shall apply the value of 0 bit for the field of beta offset indicator in DCI format 0_2. If dynamicDCI-0-2 is chosen, the UE shall apply the value of 1 bit or 2 bits for the field of beta offset indicator in DCI format 0_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13] clause 9.3).CHOICE {dynamicDCI-0-2-r16Indicates the UE applies the value 'dynamic' for DCI format 0_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.3).CHOICE { oneBit-r16 SEQUENCE (SIZE (2)) OF BetaOffsets, twoBits-r16 SEQUENCE (SIZE (4)) OF BetaOffsets },semiStaticDCI-0-2-r16Indicates the UE applies the value 'semiStatic' for DCI format 0_2. (see TS 38.212 [17], clause 7.3.1 and see TS 38.213 [13], clause 9.3).BetaOffsets } OPTIONAL, -- Need MscalingDCI-0-2-r16Indicates a scaling factor to limit the number of resource elements assigned to UCI on PUSCH for DCI format 0_2. Value f0p5 corresponds to 0.5, value f0p65 corresponds to 0.65, and so on (see TS 38.212 [17], clause 6.3).ENUMERATED { f0p5, f0p65, f0p8, f1 } } FrequencyHoppingOffsetListsDCI-0-2-r16 ::= SEQUENCE (SIZE (1..4)) OF INTEGER (1.. maxNrofPhysicalResourceBlocks-1) UCI-OnPUSCH-ListDCI-0-2-r16 ::= SEQUENCE (SIZE (1..2)) OF UCI-OnPUSCH-DCI-0-2-r16 UCI-OnPUSCH-ListDCI-0-1-r16 ::= SEQUENCE (SIZE (1..2)) OF UCI-OnPUSCH UL-AccessConfigListDCI-0-1-r16 ::= SEQUENCE (SIZE (1..64)) OF INTEGER (0..63) -- TAG-PUSCH-CONFIG-STOP -- ASN1STOP
PUSCH-Config field descriptions |
---|
antennaPortsFieldPresenceDCI-0-2 Configure the presence of "Antenna ports" field in DCI format 0_2. When the field is configured, then the "Antenna ports" field is present in DCI format 0_2. Otherwise, the field size is set to 0 for DCI format 0_2 (See TS 38.212 [17], clause 7.3.1.1.3). If neither dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2 nor dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2 is configured, this field is absent. |
codebookSubset, codebookSubsetDCI-0-2 Subset of PMIs addressed by TPMI, where PMIs are those supported by UEs with maximum coherence capabilities (see TS 38.214 [19], clause 6.1.1.1). The field codebookSubset applies to DCI format 0_1 and the field codebookSubsetDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.1.1). |
dataScramblingIdentityPUSCH Identifier used to initialise data scrambling (c_init) for PUSCH. If the field is absent, the UE applies the physical cell ID. (see TS 38.211 [16], clause 6.3.1.1). |
dmrs-SequenceInitializationDCI-0-2 Configure whether the field "DMRS Sequence Initialization" is present or not in DCI format 0_2. If the field is absent, then 0 bit for the field "DMRS Sequence Initialization" in DCI format 0_2. If the field is present, then the number of bits is determined in the same way as DCI format 0_1 (see TS 38.212 [17], clause 7.3.1). |
dmrs-UplinkForPUSCH-MappingTypeA, dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2 DMRS configuration for PUSCH transmissions using PUSCH mapping type A (chosen dynamically via PUSCH-TimeDomainResourceAllocation). Only the fields dmrs-Type, dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B. The field dmrs-UplinkForPUSCH-MappingTypeA applies to DCI format 0_1 and the field dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2 applies to DCI format 0_2 (see TS 38.212 [17], clause 7.3.1). |
dmrs-UplinkForPUSCH-MappingTypeB, dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2 DMRS configuration for PUSCH transmissions using PUSCH mapping type B (chosen dynamically via PUSCH-TimeDomainResourceAllocation). Only the fields dmrs-Type, dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B. The field dmrs-UplinkForPUSCH-MappingTypeB applies to DCI format 0_1 and the field dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2 applies to DCI format 0_2 (see TS 38.212 [17], clause 7.3.1). |
frequencyHopping The value intraSlot enables 'Intra-slot frequency hopping' and the value interSlot enables 'Inter-slot frequency hopping'. If the field is absent, frequency hopping is not configured for 'pusch-RepTypeA' (see TS 38.214 [19], clause 6.3). The field frequencyHopping applies to DCI format 0_0 and 0_1 for 'pusch-RepTypeA'. |
frequencyHoppingDCI-0-1 Indicates the frequency hopping scheme for DCI format 0_1 when pusch-RepTypeIndicatorDCI-0-1 is set to 'pusch-RepTypeB', The value interRepetition enables 'Inter-repetition frequency hopping', and the value interSlot enables 'Inter-slot frequency hopping'. If the field is absent, frequency hopping is not configured for DCI format 0_1 for 'pusch-RepTypeB'(see TS 38.214 [19], clause 6.1). |
frequencyHoppingDCI-0-2 Indicate the frequency hopping scheme for DCI format 0_2. The value intraSlot enables 'intra-slot frequency hopping', and the value interRepetition enables 'Inter-repetition frequency hopping', and the value interSlot enables 'Inter-slot frequency hopping'. When pusch-RepTypeIndicatorDCI-0-2 is set to 'pusch-RepTypeA', the frequency hopping scheme can be chosen between 'intra-slot frequency hopping and 'inter-slot frequency hopping' if enabled. When pusch-RepTypeIndicatorDCI-0-2 is set to 'pusch-RepTypeB', the frequency hopping scheme can be chosen between 'inter-repetition frequency hopping' and 'inter-slot frequency hopping' if enabled. If the field is absent, frequency hopping is not configured for DCI format 0_2 (see TS 38.214 [19], clause 6.3). |
frequencyHoppingOffsetLists, frequencyHoppingOffsetListsDCI-0-2 Set of frequency hopping offsets used when frequency hopping is enabled for granted transmission (not msg3) and type 2 configured grant activation (see TS 38.214 [19], clause 6.3).The field frequencyHoppingOffsetLists applies to DCI format 0_0 and DCI format 0_1 and the field frequencyHoppingOffsetListsDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.3). |
harq-ProcessNumberSizeDCI-0-2 Configure the number of bits for the field "HARQ process number" in DCI format 0_2 (see TS 38.212 [17], clause 7.3.1). |
invalidSymbolPattern Indicates one pattern for invalid symbols for PUSCH transmission repetition type B applicable to both DCI format 0_1 and 0_2. If InvalidSymbolPattern is not configured, semi-static flexible symbols are used for PUSCH. Segmentation occurs only around semi-static DL symbols (see TS 38.214 [19] clause 6.1). |
invalidSymbolPatternIndicatorDCI-0-1, invalidSymbolPatternIndicatorDCI-0-2 Indicates the presence of an additional bit in the DCI format 0_1/0_2. If invalidSymbolPattern is absent, then both invalidSymbolPatternIndicatorDCI-0-1 and invalidSymbolPatternIndicatorDCI-0-2 are absent. The field invalidSymbolPatternIndicatorDCI-0-1 applies to the DCI format 0_1 and the field invalidSymbolPatternIndicatorDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19] clause 6.1). If the field is absent, the UE behaviour is specified in TS 38.214 [19], clause 6.1.2.1. |
maxRank, maxRankDCI-0-2 Subset of PMIs addressed by TRIs from 1 to ULmaxRank (see TS 38.214 [19], clause 6.1.1.1). The field maxRank applies to DCI format 0_1 and the field maxRankDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.1.1). |
mcs-Table, mcs-TableFormat0-2 Indicates which MCS table the UE shall use for PUSCH without transform precoder (see TS 38.214 [19], clause 6.1.4.1). If the field is absent the UE applies the value 64QAM. The field mcs-Table applies to DCI format 0_0 and DCI format 0_1 and the field mcs-TableDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.4.1). |
mcs-TableTransformPrecoder, mcs-TableTransformPrecoderDCI-0-2 Indicates which MCS table the UE shall use for PUSCH with transform precoding (see TS 38.214 [19], clause 6.1.4.1) If the field is absent the UE applies the value 64QAM. The field mcs-TableTransformPrecoder applies to DCI format 0_0 and DCI format 0_1 and the field mcs-TableTransformPrecoderDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.4.1). |
minimumSchedulingOffsetK2 List of minimum K2 values.Minimum K2 parameter denotes minimum applicable value(s) for the Time domain resource assignment table for PUSCH (see TS 38.214 [19], clause 6.1.2.1). |
numberOfBitsForRV-DCI-0-2 Configures the number of bits for "Redundancy version" in the DCI format 0_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.214 [19], clause 6.1.2.1). |
numberOfInvalidSymbolsForDL-UL-Switching Indicates the number of symbols after the last semi-static DL symbol that are invalid symbols for PUSCH repetition Type B. If it is absent, no symbol is explicitly defined for DL-to-UL switching (see TS 38.214 [19], clause 6.1). |
priorityIndicatorDCI-0-1, priorityIndicatorDCI-0-2 Configures the presence of "priority indicator" in DCI format 0_1/0_2. When the field is absent in the IE, then the UE shall apply 0 bit for "Priority indicator" in DCI format 0_1/0_2. The field priorityIndicatorDCI-0-1 applies to DCI format 0_1 and the field priorityIndicatorDCI-0-2 applies to DCI format 0_2 (see TS 38.212 [17] clause 7.3.1 and TS 38.213 [13] clause 9). |
pusch-AggregationFactor Number of repetitions for data (see TS 38.214 [19], clause 6.1.2.1). If the field is absent the UE applies the value 1. |
pusch-RepTypeIndicatorDCI-0-1, pusch-RepTypeIndicatorDCI-0-2 Indicates whether UE follows the behavior for "PUSCH repetition type A" or the behavior for "PUSCH repetition type B" for the PUSCH scheduled by DCI format 0_1/0_2 and for Type 2 CG associated with the activating DCI format 0_1/0_2.The value pusch-RepTypeA enables the 'PUSCH repetition type A' and the value pusch-RepTypeB enables the 'PUSCH repetition type B'. The field pusch-RepTypeIndicatorDCI-0-1 applies to DCI format 0_1 and the field pusch-RepTypeIndicatorDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.2.1). |
pusch-TimeDomainAllocationList List of time domain allocations for timing of UL assignment to UL data (see TS 38.214 [19], table 6.1.2.1.1-1). The field pusch-TimeDomainAllocationList applies to DCI formats 0_0 or DCI format 0_1 when the field pusch-TimeDomainAllocationListDCI-0-1 is not configured (see TS 38.214 [19], table 6.1.2.1.1-1 and table 6.1.2.1.1-1A). The network does not configure the pusch-TimeDomainAllocationList (without suffix) simultaneously with the pusch-TimeDomainAllocationListDCI-0-2-r16orpusch-TimeDomainAllocationListDCI-0-1-r16 or pusch-TimeDomainAllocationListForMultiPUSCH-r16. |
pusch-TimeDomainAllocationListDCI-0-1 Configuration of the time domain resource allocation (TDRA) table for DCI format 0_1 (see TS 38.214 [19], clause 6.1, table 6.1.2.1.1-1A). |
pusch-TimeDomainAllocationListDCI-0-2 Configuration of the time domain resource allocation (TDRA) table for DCI format 0_2 (see TS 38.214 [19], clause 6.1.2, table 6.1.2.1.1-1B). |
pusch-TimeDomainAllocationListForMultiPUSCH Configuration of the time domain resource allocation (TDRA) table for multiple PUSCH (see TS 38.214 [19], clause 6.1.2). The network configures at most 64 rows in this TDRA table in PUSCH-TimeDomainResourceAllocationList-r16 configured by this field. This field is not configured simultaneously with pusch-AggregationFactor.The network does not configure the pusch-TimeDomainAllocationListForMultiPUSCH-r16 simultaneously with the pusch-TimeDomainAllocationListDCI-0-1-r16. |
rbg-Size Selection between configuration 1 and configuration 2 for RBG size for PUSCH. The UE does not apply this field if resourceAllocation is set to resourceAllocationType1. Otherwise, the UE applies the value config1 when the field is absent (see TS 38.214 [19], clause 6.1.2.2.1). |
resourceAllocation, resourceAllocationDCI-0-2 Configuration of resource allocation type 0 and resource allocation type 1 for non-fallback DCI (see TS 38.214 [19], clause 6.1.2). The field resourceAllocation applies to DCI format 0_1 and the field resourceAllocationDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.2). |
resourceAllocationType1GranularityDCI-0-2 Configures the scheduling granularity applicable for both the starting point and length indication for resource allocation type 1 in DCI format 0_2. If this field is absent, the granularity is 1 PRB (see TS 38.214 [19], clause 6.1.2.2.2). |
tp-pi2BPSK Enables pi/2-BPSK modulation with transform precoding if the field is present and disables it otherwise. |
transformPrecoder The UE specific selection of transformer precoder for PUSCH (see TS 38.214 [19], clause 6.1.3). When the field is absent the UE applies the value of the field msg3-transformPrecoder. |
txConfig Whether UE uses codebook based or non-codebook based transmission (see TS 38.214 [19], clause 6.1.1). If the field is absent, the UE transmits PUSCH on one antenna port, see TS 38.214 [19], clause 6.1.1. |
uci-OnPUSCH-ListDCI-0-1, uci-OnPUSCH-ListDCI-0-2 Configuration for up to 2 HARQ-ACK codebooks specific to DCI format 0_1/0_2. The field uci-OnPUSCH-ListDCI-0-1 applies to DCI format 0_1 and the field uci-OnPUSCH-ListDCI-0-2 applies to DCI format 0_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13] clause 9.3). |
ul-AccessConfigListDCI-0-1 List of the combinations of cyclic prefix extension, channel access priority class (CAPC), and UL channel access type (see TS 38.212 [17], Table 7.3.1.1.2-35). |
ul-FullPowerTransmission Configures the UE with UL full power transmission mode as specified in TS 38.213[13]. |
UCI-OnPUSCH field descriptions |
---|
betaOffsets Selection between and configuration of dynamic and semi-static beta-offset for DCI formats other than DCI format 0_2. If the field is not configured, the UE applies the value 'semiStatic' (see TS 38.213 [13], clause 9.3). |
scaling Indicates a scaling factor to limit the number of resource elements assigned to UCI on PUSCH for DCI formats other than DCI format 0_2. Value f0p5 corresponds to 0.5, value f0p65 corresponds to 0.65, and so on. The value configured herein is applicable for PUSCH with configured grant (see TS 38.212 [17], clause 6.3). |
UCI-OnPUSCH-DCI-0-2 field descriptions |
---|
betaOffsetsDCI-0-2 Configuration of beta-offset for DCI format 0_2. If semiStaticDCI-0-2 is chosen, the UE shall apply the value of 0 bit for the field of beta offset indicator in DCI format 0_2. If dynamicDCI-0-2 is chosen, the UE shall apply the value of 1 bit or 2 bits for the field of beta offset indicator in DCI format 0_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13] clause 9.3). |
dynamicDCI-0-2 Indicates the UE applies the value 'dynamic' for DCI format 0_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 9.3). |
semiStaticDCI-0-2 Indicates the UE applies the value 'semiStatic' for DCI format 0_2. (see TS 38.212 [17], clause 7.3.1 and see TS 38.213 [13], clause 9.3). |
scalingDCI-0-2 Indicates a scaling factor to limit the number of resource elements assigned to UCI on PUSCH for DCI format 0_2. Value f0p5 corresponds to 0.5, value f0p65 corresponds to 0.65, and so on (see TS 38.212 [17], clause 6.3). |
Conditional Presence | Explanation |
---|---|
codebookBased | The field is mandatory present if txConfig is set to codebook and absent otherwise. |
RepTypeB | The field is optionally present, Need S, if pusch-RepTypeIndicatorDCI-0-1 is set to pusch-RepTypeB. It is absent otherwise. |
RepTypeB2 | The field is optionally present, Need S, if pusch-RepTypeIndicatorDCI-0-1 or pusch-RepTypeIndicatorDCI-0-2 is set to pusch-RepTypeB. It is absent otherwise. |
The IE PUSCH-ConfigCommon is used to configure the cell specific PUSCH parameters.
-- ASN1START -- TAG-PUSCH-CONFIGCOMMON-START PUSCH-ConfigCommon ::= SEQUENCE {groupHoppingEnabledTransformPrecodingFor DMRS transmission with transform precoder, the NW may configure group hopping by this cell-specific parameter, see TS 38.211 [16], clause 6.4.1.1.1.2.ENUMERATED {enabled} OPTIONAL, -- Need Rpusch-TimeDomainAllocationListList of time domain allocations for timing of UL assignment to UL data (see TS 38.214 [19], table 6.1.2.1.1-1).PUSCH-TimeDomainResourceAllocationList OPTIONAL, -- Need Rmsg3-DeltaPreamblePower offset between msg3 and RACH preamble transmission. Actual value = field value * 2 [dB] (see TS 38.213 [13], clause 7.1)INTEGER (-1..6) OPTIONAL, -- Need Rp0-NominalWithGrantP0 value for PUSCH with grant (except msg3). Value in dBm. Only even values (step size 2) allowed (see TS 38.213 [13], clause 7.1) This field is cell specificINTEGER (-202..24) OPTIONAL, -- Need R ... } -- TAG-PUSCH-CONFIGCOMMON-STOP -- ASN1STOP
PUSCH-ConfigCommon field descriptions |
---|
groupHoppingEnabledTransformPrecoding For DMRS transmission with transform precoder, the NW may configure group hopping by this cell-specific parameter, see TS 38.211 [16], clause 6.4.1.1.1.2. |
msg3-DeltaPreamble Power offset between msg3 and RACH preamble transmission. Actual value = field value * 2 [dB] (see TS 38.213 [13], clause 7.1) |
p0-NominalWithGrant P0 value for PUSCH with grant (except msg3). Value in dBm. Only even values (step size 2) allowed (see TS 38.213 [13], clause 7.1) This field is cell specific |
pusch-TimeDomainAllocationList List of time domain allocations for timing of UL assignment to UL data (see TS 38.214 [19], table 6.1.2.1.1-1). |
The IE PUSCH-PowerControl is used to configure UE specific power control parameter for PUSCH.
-- ASN1START -- TAG-PUSCH-POWERCONTROL-START PUSCH-PowerControl ::= SEQUENCE {tpc-AccumulationIf enabled, UE applies TPC commands via accumulation. If not enabled, UE applies the TPC command without accumulation. If the field is absent, TPC accumulation is enabled (see TS 38.213 [13], clause 7.1).ENUMERATED { disabled } OPTIONAL, -- Need Smsg3-AlphaDedicated alpha value for msg3 PUSCH (see TS 38.213 [13], clause 7.1). When the field is absent the UE applies the value 1.Alpha OPTIONAL, -- Need Sp0-NominalWithoutGrantP0 value for UL grant-free/SPS based PUSCH. Value in dBm. Only even values (step size 2) allowed (see TS 38.213 [13], clause 7.1).INTEGER (-202..24) OPTIONAL, -- Need Mp0-AlphaSetsConfiguration {p0-pusch, alpha} sets for PUSCH (except msg3 and msgA PUSCH), i.e., { {p0,alpha,index1}, {p0,alpha,index2},...} (see TS 38.213 [13], clause 7.1). When no set is configured, the UE uses the P0-nominal for msg3/msgA PUSCH, P0-UE is set to 0 and alpha is set according to either msg3-Alpha or msgA-Alpha (see TS 38.213 [13], clause 7.1).SEQUENCE (SIZE (1..maxNrofP0-PUSCH-AlphaSets)) OF P0-PUSCH-AlphaSet OPTIONAL, -- Need M pathlossReferenceRSToAddModList SEQUENCE (SIZE (1..maxNrofPUSCH-PathlossReferenceRSs)) OF PUSCH-PathlossReferenceRS OPTIONAL, -- Need N pathlossReferenceRSToReleaseList SEQUENCE (SIZE (1..maxNrofPUSCH-PathlossReferenceRSs)) OF PUSCH-PathlossReferenceRS-Id OPTIONAL, -- Need NtwoPUSCH-PC-AdjustmentStatesNumber of PUSCH power control adjustment states maintained by the UE (i.e., fc(i)). If the field is present (n2) the UE maintains two power control states (i.e., fc(i,0) and fc(i,1)). If the field is absent, it maintains one power control state (i.e., fc(i,0)) (see TS 38.213 [13], clause 7.1).ENUMERATED {twoStates} OPTIONAL, -- Need SdeltaMCSIndicates whether to apply delta MCS. When the field is absent, the UE applies Ks = 0 in delta_TFC formula for PUSCH (see TS 38.213 [13], clause 7.1).ENUMERATED {enabled} OPTIONAL, -- Need Ssri-PUSCH-MappingToAddModListA list of SRI-PUSCH-PowerControl elements among which one is selected by the SRI field in DCI (see TS 38.213 [13], clause 7.1).SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF SRI-PUSCH-PowerControl OPTIONAL, -- Need N sri-PUSCH-MappingToReleaseList SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF SRI-PUSCH-PowerControlId OPTIONAL -- Need N } P0-PUSCH-AlphaSet ::= SEQUENCE { p0-PUSCH-AlphaSetId P0-PUSCH-AlphaSetId,p0P0 value for PUSCH with grant (except msg3) in steps of 1dB (see TS 38.213 [13], clause 7.1). When the field is absent the UE applies the value 0.INTEGER (-16..15) OPTIONAL, -- Need Salphaalpha value for PUSCH with grant (except msg3) (see TS 38.213 [13], clause 7.1). When the field is absent the UE applies the value 1.Alpha OPTIONAL -- Need S } P0-PUSCH-AlphaSetId ::= INTEGER (0..maxNrofP0-PUSCH-AlphaSets-1) PUSCH-PathlossReferenceRS ::= SEQUENCE { pusch-PathlossReferenceRS-Id PUSCH-PathlossReferenceRS-Id, referenceSignal CHOICE { ssb-Index SSB-Index, csi-RS-Index NZP-CSI-RS-ResourceId } } PUSCH-PathlossReferenceRS-r16 ::= SEQUENCE { pusch-PathlossReferenceRS-Id-r16 PUSCH-PathlossReferenceRS-Id-v1610, referenceSignal-r16 CHOICE { ssb-Index-r16 SSB-Index, csi-RS-Index-r16 NZP-CSI-RS-ResourceId } } PUSCH-PathlossReferenceRS-Id ::= INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1) PUSCH-PathlossReferenceRS-Id-v1610 ::= INTEGER (maxNrofPUSCH-PathlossReferenceRSs..maxNrofPUSCH-PathlossReferenceRSs-1-r16) SRI-PUSCH-PowerControl ::= SEQUENCE {sri-PUSCH-PowerControlIdThe ID of this SRI-PUSCH-PowerControl configuration. It is used as the codepoint (payload) in the SRI DCI field.SRI-PUSCH-PowerControlId,sri-PUSCH-PathlossReferenceRS-IdThe ID of PUSCH-PathlossReferenceRS as configured in the pathlossReferenceRSToAddModList in PUSCH-PowerControl.PUSCH-PathlossReferenceRS-Id,sri-P0-PUSCH-AlphaSetIdThe ID of a P0-PUSCH-AlphaSet as configured in p0-AlphaSetsin PUSCH-PowerControl.P0-PUSCH-AlphaSetId,sri-PUSCH-ClosedLoopIndexThe index of the closed power control loop associated with this SRI-PUSCH-PowerControl.ENUMERATED { i0, i1 } } SRI-PUSCH-PowerControlId ::= INTEGER (0..maxNrofSRI-PUSCH-Mappings-1) PUSCH-PowerControl-v1610 ::= SEQUENCE { pathlossReferenceRSToAddModListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofPUSCH-PathlossReferenceRSsDiff-r16)) OF PUSCH-PathlossReferenceRS-r16 OPTIONAL, -- Need N pathlossReferenceRSToReleaseListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofPUSCH-PathlossReferenceRSsDiff-r16)) OF PUSCH-PathlossReferenceRS-Id-v1610 OPTIONAL, -- Need Np0-PUSCH-SetList-r16Configure one additional P0-PUSCH-Set per SRI. If present, the one bit or 2 bits in the DCI is used to dynamically indicate among the P0 value from the existing P0-PUSCH-AlphaSet and the P0 value(s) from the P0-PUSCH-Set (See TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 17).SEQUENCE (SIZE (1..maxNrofSRI-PUSCH-Mappings)) OF P0-PUSCH-Set-r16 OPTIONAL, -- Need R olpc-ParameterSet SEQUENCE { olpc-ParameterSetDCI-0-1-r16 INTEGER (1..2) OPTIONAL, -- Need R olpc-ParameterSetDCI-0-2-r16 INTEGER (1..2) OPTIONAL -- Need R } OPTIONAL, -- Need M ... } P0-PUSCH-Set-r16 ::= SEQUENCE {p0-PUSCH-SetId-r16Configure the index of a p0-PUSCH-Set (see TS 38.213 [13] clause 7 and TS 38.212 [17] clause 7.3.1).P0-PUSCH-SetId-r16,p0-List-r16Configuration of {p0-PUSCH, p0-PUSCH} sets for PUSCH. If SRI is present in the DCI, then one p0-PUSCH can be configured in P0-PUSCH-Set. If SRI is not present in the DCI, and both olpc-ParameterSetDCI-0-1 and olpc-ParameterSetDCI-0-2 are configured to be 1 bit, then one p0-PUSCH can be configured in P0-PUSCH-Set. If SRI is not present in the DCI, and if any of olpc-ParameterSetDCI-0-1 and olpc-ParameterSetDCI-0-2 is configured to be 2 bits, then two p0-PUSCH values can be configured in P0-PUSCH-Set (see TS 38.213 [13] clause 7 and TS 38.212 [17] clause 7.3.1).SEQUENCE (SIZE (1..maxNrofP0-PUSCH-Set-r16)) OF P0-PUSCH-r16 OPTIONAL, -- Need R ... } P0-PUSCH-SetId-r16 ::= INTEGER (0..maxNrofSRI-PUSCH-Mappings-1) P0-PUSCH-r16 ::= INTEGER (-16..15) -- TAG-PUSCH-POWERCONTROL-STOP -- ASN1STOP
P0-PUSCH-AlphaSet field descriptions |
---|
alpha alpha value for PUSCH with grant (except msg3) (see TS 38.213 [13], clause 7.1). When the field is absent the UE applies the value 1. |
p0 P0 value for PUSCH with grant (except msg3) in steps of 1dB (see TS 38.213 [13], clause 7.1). When the field is absent the UE applies the value 0. |
P0-PUSCH-Set field descriptions |
---|
p0-List Configuration of {p0-PUSCH, p0-PUSCH} sets for PUSCH. If SRI is present in the DCI, then one p0-PUSCH can be configured in P0-PUSCH-Set. If SRI is not present in the DCI, and both olpc-ParameterSetDCI-0-1 and olpc-ParameterSetDCI-0-2 are configured to be 1 bit, then one p0-PUSCH can be configured in P0-PUSCH-Set. If SRI is not present in the DCI, and if any of olpc-ParameterSetDCI-0-1 and olpc-ParameterSetDCI-0-2 is configured to be 2 bits, then two p0-PUSCH values can be configured in P0-PUSCH-Set (see TS 38.213 [13] clause 7 and TS 38.212 [17] clause 7.3.1). |
p0-PUSCH-SetId Configure the index of a p0-PUSCH-Set (see TS 38.213 [13] clause 7 and TS 38.212 [17] clause 7.3.1). |
PUSCH-PowerControl field descriptions |
---|
deltaMCS Indicates whether to apply delta MCS. When the field is absent, the UE applies Ks = 0 in delta_TFC formula for PUSCH (see TS 38.213 [13], clause 7.1). |
msg3-Alpha Dedicated alpha value for msg3 PUSCH (see TS 38.213 [13], clause 7.1). When the field is absent the UE applies the value 1. |
olpc-ParameterSetDCI-0-1, olpc-ParameterSetDCI-0-2 Configures the number of bits for Open-loop power control parameter set indication for DCI format 0_1/0_2 in case SRI is not configured in the DCI. 2 bits is applicable only if SRI is not present in the DCI format 0_1. The field olpc-ParameterSetDCI-0-1 applies to DCI format 0_1 and the field olpc-ParameterSetDCI-0-2applies to DCI format 0_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 11). |
p0-AlphaSets Configuration {p0-pusch, alpha} sets for PUSCH (except msg3 and msgA PUSCH), i.e., { {p0,alpha,index1}, {p0,alpha,index2},...} (see TS 38.213 [13], clause 7.1). When no set is configured, the UE uses the P0-nominal for msg3/msgA PUSCH, P0-UE is set to 0 and alpha is set according to either msg3-Alpha or msgA-Alpha (see TS 38.213 [13], clause 7.1). |
p0-NominalWithoutGrant P0 value for UL grant-free/SPS based PUSCH. Value in dBm. Only even values (step size 2) allowed (see TS 38.213 [13], clause 7.1). |
p0-PUSCH-SetList Configure one additional P0-PUSCH-Set per SRI. If present, the one bit or 2 bits in the DCI is used to dynamically indicate among the P0 value from the existing P0-PUSCH-AlphaSet and the P0 value(s) from the P0-PUSCH-Set (See TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 17). |
pathlossReferenceRSToAddModList, pathlossReferenceRSToAddModListSizeExt A set of Reference Signals (e.g. a CSI-RS config or a SS block) to be used for PUSCH path loss estimation. The set consists of Reference Signals configured using pathLossReferenceRSToAddModList and Reference Signals configured using pathlossReferenceRSToAddModListSizeExt.Up to maxNrofPUSCH-PathlossReferenceRSs may be configured (see TS 38.213 [13], clause 7.1). |
pathlossReferenceRSToReleaseList, pathlossReferenceRSToReleaseListSizeExt Lists of reference symbols for PUSCH path loss estimation to be released by the UE. |
sri-PUSCH-MappingToAddModList A list of SRI-PUSCH-PowerControl elements among which one is selected by the SRI field in DCI (see TS 38.213 [13], clause 7.1). |
tpc-Accumulation If enabled, UE applies TPC commands via accumulation. If not enabled, UE applies the TPC command without accumulation. If the field is absent, TPC accumulation is enabled (see TS 38.213 [13], clause 7.1). |
twoPUSCH-PC-AdjustmentStates Number of PUSCH power control adjustment states maintained by the UE (i.e., fc(i)). If the field is present (n2) the UE maintains two power control states (i.e., fc(i,0) and fc(i,1)). If the field is absent, it maintains one power control state (i.e., fc(i,0)) (see TS 38.213 [13], clause 7.1). |
SRI-PUSCH-PowerControl field descriptions |
---|
sri-P0-PUSCH-AlphaSetId The ID of a P0-PUSCH-AlphaSet as configured in p0-AlphaSetsin PUSCH-PowerControl. |
sri-PUSCH-ClosedLoopIndex The index of the closed power control loop associated with this SRI-PUSCH-PowerControl. |
sri-PUSCH-PathlossReferenceRS-Id The ID of PUSCH-PathlossReferenceRS as configured in the pathlossReferenceRSToAddModList in PUSCH-PowerControl. |
sri-PUSCH-PowerControlId The ID of this SRI-PUSCH-PowerControl configuration. It is used as the codepoint (payload) in the SRI DCI field. |
The IE PUSCH-ServingCellConfig is used to configure UE specific PUSCH parameters that are common across the UE's BWPs of one serving cell.
-- ASN1START -- TAG-PUSCH-SERVINGCELLCONFIG-START PUSCH-ServingCellConfig ::= SEQUENCE {codeBlockGroupTransmissionEnables and configures code-block-group (CBG) based transmission (see TS 38.214 [19], clause 5.1.5).SetupRelease { PUSCH-CodeBlockGroupTransmission } OPTIONAL, -- Need MrateMatchingEnables LBRM (Limited buffer rate-matching). When the field is absent the UE applies FBRM (Full buffer rate-matchingLBRM) (see TS 38.212 [17], clause 5.4.2).ENUMERATED {limitedBufferRM} OPTIONAL, -- Need SxOverheadIf the field is absent, the UE applies the value 'xoh0' (see TS 38.214 [19], clause 5.1.3.2).ENUMERATED {xoh6, xoh12, xoh18} OPTIONAL, -- Need S ..., [[maxMIMO-LayersIndicates the maximum MIMO layer to be used for PUSCH in all BWPs of the normal UL of this serving cell (see TS 38.212 [17], clause 5.4.2.1). If present, the network sets maxRank to the same value. For SUL, the maximum number of MIMO layers is always 1, and network does not configure this field. The field maxMIMO-Layers refers to DCI format 0_1.INTEGER (1..4) OPTIONAL, -- Need MprocessingType2EnabledEnables configuration of advanced processing time capability 2 for PUSCH (see 38.214 [19], clause 6.4).BOOLEAN OPTIONAL -- Need M ]], [[maxMIMO-LayersDCI-0-2-r16Indicates the maximum MIMO layer to be used for PUSCH for DCI format 0_2 in all BWPs of the normal UL of this serving cell (see TS 38.212 [17], clause 5.4.2.1). If present, the network sets maxRankDCI-0-2 to the same value. For SUL, the maximum number of MIMO layers is always 1, and network does not configure this field.SetupRelease { MaxMIMO-LayersDCI-0-2-r16} OPTIONAL -- Need M ]] } PUSCH-CodeBlockGroupTransmission ::= SEQUENCE {maxCodeBlockGroupsPerTransportBlockMaximum number of code-block-groups (CBGs) per TB (see TS 38.213 [13], clause 9.1).ENUMERATED {n2, n4, n6, n8}, ... } MaxMIMO-LayersDCI-0-2-r16 ::= INTEGER (1..4) -- TAG-PUSCH-SERVINGCELLCONFIG-STOP -- ASN1STOP
PUSCH-CodeBlockGroupTransmission field descriptions |
---|
maxCodeBlockGroupsPerTransportBlock Maximum number of code-block-groups (CBGs) per TB (see TS 38.213 [13], clause 9.1). |
PUSCH-ServingCellConfig field descriptions |
---|
codeBlockGroupTransmission Enables and configures code-block-group (CBG) based transmission (see TS 38.214 [19], clause 5.1.5). |
maxMIMO-Layers Indicates the maximum MIMO layer to be used for PUSCH in all BWPs of the normal UL of this serving cell (see TS 38.212 [17], clause 5.4.2.1). If present, the network sets maxRank to the same value. For SUL, the maximum number of MIMO layers is always 1, and network does not configure this field. The field maxMIMO-Layers refers to DCI format 0_1. |
processingType2Enabled Enables configuration of advanced processing time capability 2 for PUSCH (see 38.214 [19], clause 6.4). |
rateMatching Enables LBRM (Limited buffer rate-matching). When the field is absent the UE applies FBRM (Full buffer rate-matchingLBRM) (see TS 38.212 [17], clause 5.4.2). |
xOverhead If the field is absent, the UE applies the value 'xoh0' (see TS 38.214 [19], clause 5.1.3.2). |
maxMIMO-LayersDCI-0-2 Indicates the maximum MIMO layer to be used for PUSCH for DCI format 0_2 in all BWPs of the normal UL of this serving cell (see TS 38.212 [17], clause 5.4.2.1). If present, the network sets maxRankDCI-0-2 to the same value. For SUL, the maximum number of MIMO layers is always 1, and network does not configure this field. |
The IE PUSCH-TimeDomainResourceAllocation is used to configure a time domain relation between PDCCH and PUSCH. PUSCH-TimeDomainResourceAllocationList contains one or more of such PUSCH-TimeDomainResourceAllocations. The network indicates in the UL grant which of the configured time domain allocations the UE shall apply for that UL grant. The UE determines the bit width of the DCI field based on the number of entries in the PUSCH-TimeDomainResourceAllocationList. Value 0 in the DCI field refers to the first element in this list, value 1 in the DCI field refers to the second element in this list, and so on.
-- ASN1START -- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-START PUSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofUL-Allocations)) OF PUSCH-TimeDomainResourceAllocation PUSCH-TimeDomainResourceAllocation ::= SEQUENCE {k2Corresponds to L1 parameter 'K2' (see TS 38.214 [19], clause 6.1.2.1) When the field is absent the UE applies the value 1 when PUSCH SCS is 15/30 kHz; the value 2 when PUSCH SCS is 60 kHz, and the value 3 when PUSCH SCS is 120KHz.INTEGER(0..32) OPTIONAL, -- Need SmappingTypeMapping type (see TS 38.214 [19], clause 6.1.2.1).ENUMERATED {typeA, typeB},startSymbolAndLengthAn index giving valid combinations of start symbol and length (jointly encoded) as start and length indicator (SLIV). The network configures the field so that the allocation does not cross the slot boundary. (see TS 38.214 [19], clause 6.1.2.1).INTEGER (0..127) } PUSCH-TimeDomainResourceAllocationList-r16 ::= SEQUENCE (SIZE(1..maxNrofUL-Allocations-r16)) OF PUSCH-TimeDomainResourceAllocation-r16 PUSCH-TimeDomainResourceAllocation-r16 ::= SEQUENCE {k2-r16Corresponds to L1 parameter 'K2' (see TS 38.214 [19], clause 6.1.2.1) When the field is absent the UE applies the value 1 when PUSCH SCS is 15/30 kHz; the value 2 when PUSCH SCS is 60 kHz, and the value 3 when PUSCH SCS is 120KHz.INTEGER(0..32) OPTIONAL, -- Need SpuschAllocationList-r16One or multiple PUSCH continuous in time domain which share a common k2 (see TS 38.214 [19], clause 6.1.2.1). This list only has one element in pusch-TimeDomainAllocationListDCI-0-1-r16 and in pusch-TimeDomainAllocationListDCI-0-2-r16.SEQUENCE (SIZE(1..maxNrofMultiplePUSCHs-r16)) OF PUSCH-Allocation-r16, ... } PUSCH-Allocation-r16 ::= SEQUENCE {mappingType-r16Mapping type (see TS 38.214 [19], clause 6.1.2.1).ENUMERATED {typeA, typeB} OPTIONAL, -- Cond NotFormat01-02-Or-TypeAstartSymbolAndLength-r16An index giving valid combinations of start symbol and length (jointly encoded) as start and length indicator (SLIV). The network configures the field so that the allocation does not cross the slot boundary. (see TS 38.214 [19], clause 6.1.2.1).INTEGER (0..127) OPTIONAL, -- Cond NotFormat01-02-Or-TypeAstartSymbol-r16Indicates the index of start symbol for PUSCH for DCI format 0_1/0_2 (see TS 38.214 [19], clause 6.1.2.1).INTEGER (0..13) OPTIONAL, -- Cond RepTypeBlength-r16Indicates the length allocated for PUSCH for DCI format 0_1/0_2 (see TS 38.214 [19], clause 6.1.2.1).INTEGER (1..14) OPTIONAL, -- Cond RepTypeBnumberOfRepetitions-r16Number of repetitions for DCI format 0_1/0_2 (see TS 38.214 [19], clause 6.1.2.1).ENUMERATED {n1, n2, n3, n4, n7, n8, n12, n16} OPTIONAL, -- Cond Format01-02 ... } -- TAG-PUSCH-TIMEDOMAINRESOURCEALLOCATIONLIST-STOP -- ASN1STOP
PUSCH-TimeDomainResourceAllocationList field descriptions |
---|
k2 Corresponds to L1 parameter 'K2' (see TS 38.214 [19], clause 6.1.2.1) When the field is absent the UE applies the value 1 when PUSCH SCS is 15/30 kHz; the value 2 when PUSCH SCS is 60 kHz, and the value 3 when PUSCH SCS is 120KHz. |
length Indicates the length allocated for PUSCH for DCI format 0_1/0_2 (see TS 38.214 [19], clause 6.1.2.1). |
mappingType Mapping type (see TS 38.214 [19], clause 6.1.2.1). |
numberOfRepetitions Number of repetitions for DCI format 0_1/0_2 (see TS 38.214 [19], clause 6.1.2.1). |
puschAllocationList One or multiple PUSCH continuous in time domain which share a common k2 (see TS 38.214 [19], clause 6.1.2.1). This list only has one element in pusch-TimeDomainAllocationListDCI-0-1-r16 and in pusch-TimeDomainAllocationListDCI-0-2-r16. |
startSymbol Indicates the index of start symbol for PUSCH for DCI format 0_1/0_2 (see TS 38.214 [19], clause 6.1.2.1). |
startSymbolAndLength An index giving valid combinations of start symbol and length (jointly encoded) as start and length indicator (SLIV). The network configures the field so that the allocation does not cross the slot boundary. (see TS 38.214 [19], clause 6.1.2.1). |
Conditional Presence | Explanation |
---|---|
Format01-02 | In pusch-TimeDomainAllocationListForMultiPUSCH-r16, the field is absent. In pusch-TimeDomainAllocationListDCI-0-1 and in pusch-TimeDomainAllocationListDCI-0-2,the field is mandatory present. |
NotFormat01-02-Or-TypeA | In pusch-TimeDomainAllocationListForMultiPUSCH-r16, the field is mandatory present. In pusch-TimeDomainAllocationListDCI-0-1, the field is mandatory present if pusch-RepTypeIndicatorDCI-0-1 is not set to pusch-RepTypeB. It is absent otherwise, Need R. In pusch-TimeDomainAllocationListDCI-0-2, the field is mandatory present if pusch-RepTypeIndicatorDCI-0-2 is not set to pusch-RepTypeB. It is absent otherwise, Need R. |
RepTypeB | In pusch-TimeDomainAllocationListForMultiPUSCH-r16, the field is absent. In pusch-TimeDomainAllocationListDCI-0-1, the field is mandatory present if pusch-RepTypeIndicatorDCI-0-1 is set to pusch-RepTypeB. It is absent otherwise, Need R. In pusch-TimeDomainAllocationListDCI-0-2, the field is mandatory present if pusch-RepTypeIndicatorDCI-0-2 is set to pusch-RepTypeB. It is absent otherwise, Need R. |
The IE PUSCH-TPC-CommandConfig is used to configure the UE for extracting TPC commands for PUSCH from a group-TPC messages on DCI.
-- ASN1START -- TAG-PUSCH-TPC-COMMANDCONFIG-START PUSCH-TPC-CommandConfig ::= SEQUENCE {tpc-IndexAn index determining the position of the first bit of TPC command inside the DCI format 2-2 payload.INTEGER (1..15) OPTIONAL, -- Cond SULtpc-IndexSULAn index determining the position of the first bit of TPC command inside the DCI format 2-2 payload.INTEGER (1..15) OPTIONAL, -- Cond SUL-OnlytargetCellThe serving cell to which the acquired power control commands are applicable. If the value is absent, the UE applies the TPC commands to the serving cell on which the command has been received.ServCellIndex OPTIONAL, -- Need S ... } -- TAG-PUSCH-TPC-COMMANDCONFIG-STOP -- ASN1STOP
PUSCH-TPC-CommandConfig field descriptions |
---|
targetCell The serving cell to which the acquired power control commands are applicable. If the value is absent, the UE applies the TPC commands to the serving cell on which the command has been received. |
tpc-Index An index determining the position of the first bit of TPC command inside the DCI format 2-2 payload. |
tpc-IndexSUL An index determining the position of the first bit of TPC command inside the DCI format 2-2 payload. |
Conditional Presence | Explanation |
---|---|
SUL-Only | The field is optionally present, Need R, if supplementaryUplink is configured within ServingCellConfig. It is absent otherwise. |
SUL | The field is optionally present, Need R, if supplementaryUplink is configured within ServingCellConfig. It is mandatory present otherwise. |
The IE Q-OffsetRange is used to indicate a cell, beam or measurement object specific offset to be applied when evaluating candidates for cell re-selection or when evaluating triggering conditions for measurement reporting. The value is in dB. Value dB-24 corresponds to -24 dB, dB-22 corresponds to -22 dB and so on.
The IE Q-QualMin is used to indicate for cell selection/ re-selection the required minimum received RSRQ level in the (NR) cell. Corresponds to parameter Qqualmin in TS 38.304 [20]. Actual value Qqualmin = field value [dB].
The IE Q-RxLevMin is used to indicate for cell selection/ re-selection the required minimum received RSRP level in the (NR) cell. Corresponds to parameter Qrxlevmin in TS 38.304 [20]. Actual value Qrxlevmin = field value * 2 [dBm].
The IE QuantityConfig specifies the measurement quantities and layer 3 filtering coefficients for NR and inter-RAT measurements.
-- ASN1START -- TAG-QUANTITYCONFIG-START QuantityConfig ::= SEQUENCE { quantityConfigNR-List SEQUENCE (SIZE (1..maxNrofQuantityConfig)) OF QuantityConfigNR OPTIONAL, -- Need M ..., [[ quantityConfigEUTRA FilterConfig OPTIONAL -- Need M ]], [[ quantityConfigUTRA-FDD-r16 QuantityConfigUTRA-FDD-r16 OPTIONAL, -- Need M quantityConfigCLI-r16 FilterConfigCLI-r16 OPTIONAL -- Need M ]] } QuantityConfigNR::= SEQUENCE {quantityConfigCellSpecifies L3 filter configurations for cell measurement results for the configurable RS Types (e.g. SS/PBCH block and CSI-RS) and the configurable measurement quantities (e.g. RSRP, RSRQ and SINR).QuantityConfigRS,quantityConfigRS-IndexSpecifies L3 filter configurations for measurement results per RS index for the configurable RS Types (e.g. SS/PBCH block and CSI-RS) and the configurable measurement quantities (e.g. RSRP, RSRQ and SINR).QuantityConfigRS OPTIONAL -- Need M } QuantityConfigRS ::= SEQUENCE {ssb-FilterConfigSS Block based L3 filter configurations: Specifies L3 filter configurations for SS-RSRP, SS-RSRQ and SS-SINR measurement results from the L1 filter(s), as defined in TS 38.215 [9].FilterConfig,csi-RS-FilterConfigCSI-RS based L3 filter configurations: Specifies L3 filter configurations for CSI-RSRP, CSI-RSRQ and CSI-SINR measurement results from the L1 filter(s), as defined in TS 38.215 [9].FilterConfig } FilterConfig ::= SEQUENCE { filterCoefficientRSRP FilterCoefficient DEFAULT fc4, filterCoefficientRSRQ FilterCoefficient DEFAULT fc4, filterCoefficientRS-SINR FilterCoefficient DEFAULT fc4 } FilterConfigCLI-r16 ::= SEQUENCE { filterCoefficientSRS-RSRP-r16 FilterCoefficient DEFAULT fc4, filterCoefficientCLI-RSSI-r16 FilterCoefficient DEFAULT fc4 } QuantityConfigUTRA-FDD-r16 ::= SEQUENCE {filterCoefficientRSCP-r16Specifies L3 filter coefficient for FDD UTRAN CPICH_RSCP measuement results from L1 filter.FilterCoefficient DEFAULT fc4, filterCoefficientEcNO-r16 FilterCoefficient DEFAULT fc4 } -- TAG-QUANTITYCONFIG-STOP -- ASN1STOP
QuantityConfigNR field descriptions |
---|
quantityConfigCell Specifies L3 filter configurations for cell measurement results for the configurable RS Types (e.g. SS/PBCH block and CSI-RS) and the configurable measurement quantities (e.g. RSRP, RSRQ and SINR). |
quantityConfigRS-Index Specifies L3 filter configurations for measurement results per RS index for the configurable RS Types (e.g. SS/PBCH block and CSI-RS) and the configurable measurement quantities (e.g. RSRP, RSRQ and SINR). |
QuantityConfigRS field descriptions |
---|
csi-RS-FilterConfig CSI-RS based L3 filter configurations: Specifies L3 filter configurations for CSI-RSRP, CSI-RSRQ and CSI-SINR measurement results from the L1 filter(s), as defined in TS 38.215 [9]. |
ssb-FilterConfig SS Block based L3 filter configurations: Specifies L3 filter configurations for SS-RSRP, SS-RSRQ and SS-SINR measurement results from the L1 filter(s), as defined in TS 38.215 [9]. |
QuantityConfigUTRA-FDD field descriptions |
---|
filterCoefficientRSCP Specifies L3 filter coefficient for FDD UTRAN CPICH_RSCP measuement results from L1 filter. |
filterCoefficientEcN0 Specifies L3 filter coefficient for FDD UTRAN CPICH_EcN0 measuement results from L1 filter. |
The IE RACH-ConfigCommon is used to specify the cell specific random-access parameters.
-- ASN1START -- TAG-RACH-CONFIGCOMMON-START RACH-ConfigCommon ::= SEQUENCE {rach-ConfigGenericRACH parameters for both regular random access and beam failure recovery.RACH-ConfigGeneric,totalNumberOfRA-PreamblesTotal number of preambles used for contention based and contention free 4-step or 2-step random access in the RACH resources defined in RACH-ConfigCommon, excluding preambles used for other purposes (e.g. for SI request). If the field is absent, all 64 preambles are available for RA. The setting should be consistent with the setting of ssb-perRACH-OccasionAndCB-PreamblesPerSSB, i.e. it should be a multiple of the number of SSBs per RACH occasion.INTEGER (1..63) OPTIONAL, -- Need Sssb-perRACH-OccasionAndCB-PreamblesPerSSBThe meaning of this field is twofold: the CHOICE conveys the information about the number of SSBs per RACH occasion. Value oneEighth corresponds to one SSB associated with 8 RACH occasions, value oneFourth corresponds to one SSB associated with 4 RACH occasions, and so on. The ENUMERATED part indicates the number of Contention Based preambles per SSB. Value n4 corresponds to 4 Contention Based preambles per SSB, value n8 corresponds to 8 Contention Based preambles per SSB, and so on. The total number of CB preambles in a RACH occasion is given by CB-preambles-per-SSB * max(1, SSB-per-rach-occasion). See TS 38.213 [13].CHOICE { oneEighth ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, oneFourth ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, oneHalf ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, one ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, two ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32}, four INTEGER (1..16), eight INTEGER (1..8), sixteen INTEGER (1..4) } OPTIONAL, -- Need M groupBconfigured SEQUENCE {ra-Msg3SizeGroupATransport Blocks size threshold in bits below which the UE shall use a contention-based RA preamble of group A. (see TS 38.321 [3], clause 5.1.2).ENUMERATED {b56, b144, b208, b256, b282, b480, b640, b800, b1000, b72, spare6, spare5,spare4, spare3, spare2, spare1},messagePowerOffsetGroupBThreshold for preamble selection. Value is in dB. Value minusinfinity corresponds to –infinity. Value dB0 corresponds to 0 dB, dB5 corresponds to 5 dB and so on. (see TS 38.321 [3], clause 5.1.2)ENUMERATED { minusinfinity, dB0, dB5, dB8, dB10, dB12, dB15, dB18},numberOfRA-PreamblesGroupAThe number of CB preambles per SSB in group A. This determines implicitly the number of CB preambles per SSB available in group B. (see TS 38.321 [3], clause 5.1.1). The setting should be consistent with the setting of ssb-perRACH-OccasionAndCB-PreamblesPerSSB.INTEGER (1..64) } OPTIONAL, -- Need Rra-ContentionResolutionTimerThe initial value for the contention resolution timer (see TS 38.321 [3], clause 5.1.5). Value sf8 corresponds to 8 subframes, value sf16 corresponds to 16 subframes, and so on.ENUMERATED { sf8, sf16, sf24, sf32, sf40, sf48, sf56, sf64},rsrp-ThresholdSSBUE may select the SS block and corresponding PRACH resource for path-loss estimation and (re)transmission based on SS blocks that satisfy the threshold (see TS 38.213 [13]).RSRP-Range OPTIONAL, -- Need Rrsrp-ThresholdSSB-SULThe UE selects SUL carrier to perform random access based on this threshold (see TS 38.321 [3], clause 5.1.1). The value applies to all the BWPs.RSRP-Range OPTIONAL, -- Cond SULprach-RootSequenceIndexPRACH root sequence index (see TS 38.211 [16], clause 6.3.3.1). The value range depends on whether L=839 or L=139 or L=571 or L=1151. The length of the root sequence corresponding with the index indicated in this IE should be consistent with the one indicated in prach-ConfigurationIndex in the RACH-ConfigDedicated (if configured). If prach-RootSequenceIndex-r16 is signalled, UE shall ignore the prach-RootSequenceIndex (without suffix).CHOICE { l839 INTEGER (0..837), l139 INTEGER (0..137) },msg1-SubcarrierSpacingSubcarrier spacing of PRACH (see TS 38.211 [16], clause 5.3.2). Only the values 15 or 30 kHz (FR1), and 60 or 120 kHz (FR2) are applicable. If absent, the UE applies the SCS as derived from the prach-ConfigurationIndex in RACH-ConfigGeneric (see tables Table 6.3.3.1-1, Table 6.3.3.1-2, Table 6.3.3.2-2 and Table 6.3.3.2-3, TS 38.211 [16]). The value also applies to contention free random access (RACH-ConfigDedicated), to SI-request and to contention-based beam failure recovery (CB-BFR). But it does not apply for contention free beam failure recovery (CF-BFR) (see BeamFailureRecoveryConfig).SubcarrierSpacing OPTIONAL, -- Cond L139restrictedSetConfigConfiguration of an unrestricted set or one of two types of restricted sets, see TS 38.211 [16], clause 6.3.3.1.ENUMERATED {unrestrictedSet, restrictedSetTypeA, restrictedSetTypeB},msg3-transformPrecoderEnables the transform precoder for Msg3 transmission according to clause 6.1.3 of TS 38.214 [19]. If the field is absent, the UE disables the transformer precoder (see TS 38.213 [13], clause 8.3).ENUMERATED {enabled} OPTIONAL, -- Need R ..., [[ ra-PrioritizationForAccessIdentity-r16 SEQUENCE {ra-Prioritization-r16Parameters which apply for prioritized random access procedure on any UL BWP of SpCell for specific Access Identities (see TS 38.321 [3], clause 5.1.1a).RA-Prioritization,ra-PrioritizationForAI-r16Indicates whether the field ra-Prioritization-r16 applies for Access Identities. The first/leftmost bit corresponds to Access Identity 1, the next bit corresponds to Access Identity 2. Value 1 indicates that the field ra-Prioritization-r16 applies otherwise the field does not apply (see TS 23.501 [32]).BIT STRING (SIZE (2)) } OPTIONAL, -- Cond InitialBWP-Onlyprach-RootSequenceIndex-r16PRACH root sequence index (see TS 38.211 [16], clause 6.3.3.1). The value range depends on whether L=839 or L=139 or L=571 or L=1151. The length of the root sequence corresponding with the index indicated in this IE should be consistent with the one indicated in prach-ConfigurationIndex in the RACH-ConfigDedicated (if configured). If prach-RootSequenceIndex-r16 is signalled, UE shall ignore the prach-RootSequenceIndex (without suffix).CHOICE { l571 INTEGER (0..569), l1151 INTEGER (0..1149) } OPTIONAL -- Need R ]] } -- TAG-RACH-CONFIGCOMMON-STOP -- ASN1STOP
RACH-ConfigCommon field descriptions |
---|
messagePowerOffsetGroupB Threshold for preamble selection. Value is in dB. Value minusinfinity corresponds to –infinity. Value dB0 corresponds to 0 dB, dB5 corresponds to 5 dB and so on. (see TS 38.321 [3], clause 5.1.2) |
msg1-SubcarrierSpacing Subcarrier spacing of PRACH (see TS 38.211 [16], clause 5.3.2). Only the values 15 or 30 kHz (FR1), and 60 or 120 kHz (FR2) are applicable. If absent, the UE applies the SCS as derived from the prach-ConfigurationIndex in RACH-ConfigGeneric (see tables Table 6.3.3.1-1, Table 6.3.3.1-2, Table 6.3.3.2-2 and Table 6.3.3.2-3, TS 38.211 [16]). The value also applies to contention free random access (RACH-ConfigDedicated), to SI-request and to contention-based beam failure recovery (CB-BFR). But it does not apply for contention free beam failure recovery (CF-BFR) (see BeamFailureRecoveryConfig). |
msg3-transformPrecoder Enables the transform precoder for Msg3 transmission according to clause 6.1.3 of TS 38.214 [19]. If the field is absent, the UE disables the transformer precoder (see TS 38.213 [13], clause 8.3). |
numberOfRA-PreamblesGroupA The number of CB preambles per SSB in group A. This determines implicitly the number of CB preambles per SSB available in group B. (see TS 38.321 [3], clause 5.1.1). The setting should be consistent with the setting of ssb-perRACH-OccasionAndCB-PreamblesPerSSB. |
prach-RootSequenceIndex PRACH root sequence index (see TS 38.211 [16], clause 6.3.3.1). The value range depends on whether L=839 or L=139 or L=571 or L=1151. The length of the root sequence corresponding with the index indicated in this IE should be consistent with the one indicated in prach-ConfigurationIndex in the RACH-ConfigDedicated (if configured). If prach-RootSequenceIndex-r16 is signalled, UE shall ignore the prach-RootSequenceIndex (without suffix). |
ra-ContentionResolutionTimer The initial value for the contention resolution timer (see TS 38.321 [3], clause 5.1.5). Value sf8 corresponds to 8 subframes, value sf16 corresponds to 16 subframes, and so on. |
ra-Msg3SizeGroupA Transport Blocks size threshold in bits below which the UE shall use a contention-based RA preamble of group A. (see TS 38.321 [3], clause 5.1.2). |
ra-Prioritization Parameters which apply for prioritized random access procedure on any UL BWP of SpCell for specific Access Identities (see TS 38.321 [3], clause 5.1.1a). |
ra-PrioritizationForAI Indicates whether the field ra-Prioritization-r16 applies for Access Identities. The first/leftmost bit corresponds to Access Identity 1, the next bit corresponds to Access Identity 2. Value 1 indicates that the field ra-Prioritization-r16 applies otherwise the field does not apply (see TS 23.501 [32]). |
rach-ConfigGeneric RACH parameters for both regular random access and beam failure recovery. |
restrictedSetConfig Configuration of an unrestricted set or one of two types of restricted sets, see TS 38.211 [16], clause 6.3.3.1. |
rsrp-ThresholdSSB UE may select the SS block and corresponding PRACH resource for path-loss estimation and (re)transmission based on SS blocks that satisfy the threshold (see TS 38.213 [13]). |
rsrp-ThresholdSSB-SUL The UE selects SUL carrier to perform random access based on this threshold (see TS 38.321 [3], clause 5.1.1). The value applies to all the BWPs. |
ssb-perRACH-OccasionAndCB-PreamblesPerSSB The meaning of this field is twofold: the CHOICE conveys the information about the number of SSBs per RACH occasion. Value oneEighth corresponds to one SSB associated with 8 RACH occasions, value oneFourth corresponds to one SSB associated with 4 RACH occasions, and so on. The ENUMERATED part indicates the number of Contention Based preambles per SSB. Value n4 corresponds to 4 Contention Based preambles per SSB, value n8 corresponds to 8 Contention Based preambles per SSB, and so on. The total number of CB preambles in a RACH occasion is given by CB-preambles-per-SSB * max(1, SSB-per-rach-occasion). See TS 38.213 [13]. |
totalNumberOfRA-Preambles Total number of preambles used for contention based and contention free 4-step or 2-step random access in the RACH resources defined in RACH-ConfigCommon, excluding preambles used for other purposes (e.g. for SI request). If the field is absent, all 64 preambles are available for RA. The setting should be consistent with the setting of ssb-perRACH-OccasionAndCB-PreamblesPerSSB, i.e. it should be a multiple of the number of SSBs per RACH occasion. |
Conditional Presence | Explanation |
---|---|
L139 | The field is mandatory present if prach-RootSequenceIndex L=139, otherwise the field is absent, Need S. |
SUL | The field is mandatory present in initialUplinkBWP if supplementaryUplink is configured in ServingCellConfigCommonSIB or if supplementaryUplinkConfig is configured in ServingCellConfigCommon; otherwise, the field is absent. |
InitialBWP-Only | This field is optionally present, Need R, if this BWP is the initial BWP of SpCell. Otherwise the field is absent. |
The IE RACH-ConfigCommonTwoStepRA is used to specify cell specific 2-step random-access type parameters.
-- ASN1START -- TAG-RACH-CONFIGCOMMONTWOSTEPRA-START RACH-ConfigCommonTwoStepRA-r16 ::= SEQUENCE {rach-ConfigGenericTwoStepRA-r162-step random access type parameters for both regular random access and beam failure recovery.RACH-ConfigGenericTwoStepRA-r16,msgA-TotalNumberOfRA-Preambles-r16Indicates the total number of preambles used for contention-based and contention-free 2-step random access type when ROs for 2-step are not shared with 4-step. If the field is absent, and 2-step and 4-step does not have shared ROs, all 64 preambles are available for 2-step random access type.INTEGER (1..63) OPTIONAL, -- Need SmsgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB-r16The meaning of this field is twofold: the CHOICE conveys the information about the number of SSBs per RACH occasion. Value oneEight corresponds to one SSB associated with 8 RACH occasions, value oneFourth corresponds to one SSB associated with 4 RACH occasions, and so on. The ENUMERATED part indicates the number of Contention Based preambles per SSB. Value n4 corresponds to 4 Contention Based preambles per SSB, value n8 corresponds to 8 Contention Based preambles per SSB, and so on. The total number of CB preambles in a RACH occasion is given by CB-preambles-per-SSB * max(1, SSB-per-rach-occasion). If the field is not configured and both 2-step and 4-step are configured for the BWP, the UE applies the value in the field ssb-perRACH-OccasionAndCB-PreamblesPerSSB in RACH-ConfigCommon. The field is not present when RACH occasions are shared between 2-step and 4-step type random access in the BWP.CHOICE { oneEighth ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, oneFourth ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, oneHalf ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, one ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, two ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32}, four INTEGER (1..16), eight INTEGER (1..8), sixteen INTEGER (1..4) } OPTIONAL, -- Cond 2StepOnlymsgA-CB-PreamblesPerSSB-PerSharedRO-r16Number of contention-based preambles used for 2-step RA type from the non-CBRA 4-step type preambles associated with each SSB for RO shared with 4-step type RA. The number of preambles for 2-step RA type shall not exceed the number of preambles per SSB minus the number of contention-based preambles per SSB for 4-step type RA. The possible value range for this parameter needs to be aligned with value range for the configured SSBs per RACH occasion in ssb-perRACH-OccasionAndCB-PreamblesPerSSB in RACH-ConfigCommon. The field is only applicable for the case of shared ROs with 4-step type random access.INTEGER (1..60) OPTIONAL, -- Cond SharedROmsgA-SSB-SharedRO-MaskIndex-r16Indicates the subset of 4-step type ROs shared with 2-step random access type for each SSB. This field is configured when there is more than one RO per SSB. If the field is absent, and 4-step and 2-step has shared ROs, then all ROs are shared.INTEGER (1..15) OPTIONAL, -- Need SgroupB-ConfiguredTwoStepRA-r16Preamble grouping for 2-step random access type. If the field is absent then there is only one preamble group configured and only one msgA PUSCH configuration.GroupB-ConfiguredTwoStepRA-r16 OPTIONAL, -- Need SmsgA-PRACH-RootSequenceIndex-r16PRACH root sequence index. If the field is not configured, the UE applies the value in field prach-RootSequenceIndex in RACH-ConfigCommon in the configured BWP. When both 2-step and 4-step type random access is configured, this field is only configured for the case of separate ROs between 2-step and 4-step type random access.CHOICE { l839 INTEGER (0..837), l139 INTEGER (0..137), l571 INTEGER (0..569), l1151 INTEGER (0..1149) } OPTIONAL, -- Cond 2StepOnlymsgA-TransMax-r16Max number of MsgA preamble transmissions performed before switching to 4-step random access (see TS 38.321 [3], clauses 5.1.1). This field is only applicable when 2-step and 4-step RA type are configured and switching to 4-step type RA is supported. If the field is absent, switching from 2-step RA type to 4-step RA type is not allowed.ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100, n200} OPTIONAL, -- Need RmsgA-RSRP-Threshold-r16The UE selects 2-step random access type to perform random access based on this threshold (see TS 38.321 [3], clause 5.1.1). This field is only present if both 2-step and 4-step RA type are configured for the BWP.RSRP-Range OPTIONAL, -- Cond 2Step4StepmsgA-RSRP-ThresholdSSB-r16UE may select the SS block and corresponding PRACH resource for path-loss estimation and (re)transmission based on SS blocks that satisfy the threshold (see TS 38.213 [13]).RSRP-Range OPTIONAL, -- Need RmsgA-SubcarrierSpacing-r16Subcarrier spacing of PRACH (see TS 38.211 [16], clause 5.3.2). Only the values 15 or 30 kHz (FR1), and 60 or 120 kHz (FR2) are applicable. If the field is absent, the UE applies the SCS as derived from the msgA-PRACH-ConfigurationIndex in RACH-ConfigGenericTwoStepRA (see tables Table 6.3.3.1-1, Table 6.3.3.1-2, Table 6.3.3.2-2 and Table 6.3.3.2-3, TS 38.211 [16]) in case of 2-step only BWP, otherwise the UE applies the same SCS as Msg1 derived from RACH-ConfigCommon. The value also applies to contention free 2-step random access type (RACH-ConfigDedicated).SubcarrierSpacing OPTIONAL, -- Cond 2StepOnlyL139msgA-RestrictedSetConfig-r16Configuration of an unrestricted set or one of two types of restricted sets for 2-step random access type preamble. If the field is not configured, the UE applies the value in field restrictedSetConfigin RACH-ConfigCommon in the configured BWP.When both 2-step and 4-step type random access is configured, this field is only configured for the case of separate ROs between 2-step and 4-step type random access.ENUMERATED {unrestrictedSet, restrictedSetTypeA, restrictedSetTypeB} OPTIONAL, -- Cond 2StepOnly ra-PrioritizationForAccessIdentityTwoStep-r16 SEQUENCE {ra-Prioritization-r16Parameters which apply for prioritized random access procedure on any UL BWP of SpCell for specific Access Identities (see TS 38.321 [3], clause 5.1.1a).RA-Prioritization,ra-PrioritizationForAI-r16Indicates whether the field ra-Prioritization-r16 applies for Access Identities. The first/leftmost bit corresponds to Access Identity 1, the next bit corresponds to Access Identity 2. Value 1 for an Access Identity indicates that the field ra-Prioritization-r16 applies, otherwise the field does not apply.BIT STRING (SIZE (2)) } OPTIONAL, -- Cond InitialBWP-Onlyra-ContentionResolutionTimer-r16The initial value for the contention resolution timer for fallback RAR in case no 4-step random access type is configured (see TS 38.321 [3], clause 5.1.5). Value sf8 corresponds to 8 subframes, value sf16 corresponds to 16 subframes, and so on. If both 2-step and 4-step random access type resources are configured on the BWP, then this field is absent.ENUMERATED {sf8, sf16, sf24, sf32, sf40, sf48, sf56, sf64} OPTIONAL, -- Cond 2StepOnly ... } GroupB-ConfiguredTwoStepRA-r16 ::= SEQUENCE {ra-MsgA-SizeGroupATransport block size threshold in bits below which the UE shall use a contention-based RA preamble of group A. (see TS 38.321 [3], clause 5.1.1).ENUMERATED {b56, b144, b208, b256, b282, b480, b640, b800, b1000, b72, spare6, spare5, spare4, spare3, spare2, spare1},messagePowerOffsetGroupBThreshold for preamble selection. Value is in dB. Value minusinfinity corresponds to –infinity. Value dB0 corresponds to 0 dB, dB5 corresponds to 5 dB and so on. (see TS 38.321 [3], clause 5.1.1).ENUMERATED {minusinfinity, dB0, dB5, dB8, dB10, dB12, dB15, dB18},numberOfRA-PreamblesGroupAThe number of CB preambles per SSB in group A for idle/inactive or connected mode. The setting of the number of preambles for each group should be consistent with msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB or msgA-CB-PreamblesPerSSB-PerSharedRO if configured.INTEGER (1..64) } -- TAG-RACH-CONFIGCOMMONTWOSTEPRA-STOP -- ASN1STOP
RACH-ConfigCommonTwoStepRA field descriptions |
---|
groupB-ConfiguredTwoStepRA Preamble grouping for 2-step random access type. If the field is absent then there is only one preamble group configured and only one msgA PUSCH configuration. |
msgA-CB-PreamblesPerSSB-PerSharedRO Number of contention-based preambles used for 2-step RA type from the non-CBRA 4-step type preambles associated with each SSB for RO shared with 4-step type RA. The number of preambles for 2-step RA type shall not exceed the number of preambles per SSB minus the number of contention-based preambles per SSB for 4-step type RA. The possible value range for this parameter needs to be aligned with value range for the configured SSBs per RACH occasion in ssb-perRACH-OccasionAndCB-PreamblesPerSSB in RACH-ConfigCommon. The field is only applicable for the case of shared ROs with 4-step type random access. |
msgA-PRACH-RootSequenceIndex PRACH root sequence index. If the field is not configured, the UE applies the value in field prach-RootSequenceIndex in RACH-ConfigCommon in the configured BWP. When both 2-step and 4-step type random access is configured, this field is only configured for the case of separate ROs between 2-step and 4-step type random access. |
msgA-RestrictedSetConfig Configuration of an unrestricted set or one of two types of restricted sets for 2-step random access type preamble. If the field is not configured, the UE applies the value in field restrictedSetConfigin RACH-ConfigCommon in the configured BWP.When both 2-step and 4-step type random access is configured, this field is only configured for the case of separate ROs between 2-step and 4-step type random access. |
msgA-RSRP-Threshold The UE selects 2-step random access type to perform random access based on this threshold (see TS 38.321 [3], clause 5.1.1). This field is only present if both 2-step and 4-step RA type are configured for the BWP. |
msgA-RSRP-ThresholdSSB UE may select the SS block and corresponding PRACH resource for path-loss estimation and (re)transmission based on SS blocks that satisfy the threshold (see TS 38.213 [13]). |
msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB The meaning of this field is twofold: the CHOICE conveys the information about the number of SSBs per RACH occasion. Value oneEight corresponds to one SSB associated with 8 RACH occasions, value oneFourth corresponds to one SSB associated with 4 RACH occasions, and so on. The ENUMERATED part indicates the number of Contention Based preambles per SSB. Value n4 corresponds to 4 Contention Based preambles per SSB, value n8 corresponds to 8 Contention Based preambles per SSB, and so on. The total number of CB preambles in a RACH occasion is given by CB-preambles-per-SSB * max(1, SSB-per-rach-occasion). If the field is not configured and both 2-step and 4-step are configured for the BWP, the UE applies the value in the field ssb-perRACH-OccasionAndCB-PreamblesPerSSB in RACH-ConfigCommon. The field is not present when RACH occasions are shared between 2-step and 4-step type random access in the BWP. |
msgA-SSB-SharedRO-MaskIndex Indicates the subset of 4-step type ROs shared with 2-step random access type for each SSB. This field is configured when there is more than one RO per SSB. If the field is absent, and 4-step and 2-step has shared ROs, then all ROs are shared. |
msgA-SubcarrierSpacing Subcarrier spacing of PRACH (see TS 38.211 [16], clause 5.3.2). Only the values 15 or 30 kHz (FR1), and 60 or 120 kHz (FR2) are applicable. If the field is absent, the UE applies the SCS as derived from the msgA-PRACH-ConfigurationIndex in RACH-ConfigGenericTwoStepRA (see tables Table 6.3.3.1-1, Table 6.3.3.1-2, Table 6.3.3.2-2 and Table 6.3.3.2-3, TS 38.211 [16]) in case of 2-step only BWP, otherwise the UE applies the same SCS as Msg1 derived from RACH-ConfigCommon. The value also applies to contention free 2-step random access type (RACH-ConfigDedicated). |
msgA-TotalNumberOfRA-Preambles Indicates the total number of preambles used for contention-based and contention-free 2-step random access type when ROs for 2-step are not shared with 4-step. If the field is absent, and 2-step and 4-step does not have shared ROs, all 64 preambles are available for 2-step random access type. |
msgA-TransMax Max number of MsgA preamble transmissions performed before switching to 4-step random access (see TS 38.321 [3], clauses 5.1.1). This field is only applicable when 2-step and 4-step RA type are configured and switching to 4-step type RA is supported. If the field is absent, switching from 2-step RA type to 4-step RA type is not allowed. |
ra-ContentionResolutionTimer The initial value for the contention resolution timer for fallback RAR in case no 4-step random access type is configured (see TS 38.321 [3], clause 5.1.5). Value sf8 corresponds to 8 subframes, value sf16 corresponds to 16 subframes, and so on. If both 2-step and 4-step random access type resources are configured on the BWP, then this field is absent. |
ra-Prioritization Parameters which apply for prioritized random access procedure on any UL BWP of SpCell for specific Access Identities (see TS 38.321 [3], clause 5.1.1a). |
ra-PrioritizationForAI Indicates whether the field ra-Prioritization-r16 applies for Access Identities. The first/leftmost bit corresponds to Access Identity 1, the next bit corresponds to Access Identity 2. Value 1 for an Access Identity indicates that the field ra-Prioritization-r16 applies, otherwise the field does not apply. |
rach-ConfigGenericTwoStepRA 2-step random access type parameters for both regular random access and beam failure recovery. |
GroupB-ConfiguredTwoStepRA field descriptions |
---|
messagePowerOffsetGroupB Threshold for preamble selection. Value is in dB. Value minusinfinity corresponds to –infinity. Value dB0 corresponds to 0 dB, dB5 corresponds to 5 dB and so on. (see TS 38.321 [3], clause 5.1.1). |
numberOfRA-PreamblesGroupA The number of CB preambles per SSB in group A for idle/inactive or connected mode. The setting of the number of preambles for each group should be consistent with msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB or msgA-CB-PreamblesPerSSB-PerSharedRO if configured. |
ra-MsgA-SizeGroupA Transport block size threshold in bits below which the UE shall use a contention-based RA preamble of group A. (see TS 38.321 [3], clause 5.1.1). |
Conditional Presence | Explanation |
---|---|
2StepOnlyL139 | The field is mandatory present if msgA-PRACH-RootSequenceIndex L=139 and no 4-step random access type is configured, otherwise the field is absent, Need S. |
2StepOnly | The field is mandatory present if there are no 4-step random access configurations configured in the BWP, i.e only 2-step random access type configured in the BWP, otherwise the field is optionally present, Need S. |
SharedRO | The field is mandatory present if the 2-step random access type occasions are shared with 4-step random access type, otherwise the field is not present. |
2Step4Step | The field is mandatory present if both 2-step random access type and 4-step random access type are configured in the BWP, otherwise the field is not present. |
InitialBWP-Only | This field is optionally present, Need R, if this BWP is the initial BWP of SpCell. Otherwise the field is absent. |
The IE RACH-ConfigDedicated is used to specify the dedicated random access parameters.
-- ASN1START -- TAG-RACH-CONFIGDEDICATED-START RACH-ConfigDedicated ::= SEQUENCE {cfraParameters for contention free random access to a given target cell. If this field and cfra-TwoStep are absent, the UE performs contention based random access.CFRA OPTIONAL, -- Need S ra-Prioritization RA-Prioritization OPTIONAL, -- Need N ..., [[ra-PrioritizationTwoStep-r16Parameters which apply for prioritized 2-step random access type procedure to a given target cell (see TS 38.321 [3], clause 5.1.1).RA-Prioritization OPTIONAL, -- Need Ncfra-TwoStep-r16Parameters for contention free 2-step random access type to a given target cell. Network ensures that cfra and cfra-TwoStep are not configured at the same time.If this field and cfra are absent, the UE performs contention based random access. This field may only be present if msgA-ConfigCommon is configured on the BWP.CFRA-TwoStep-r16 OPTIONAL -- Need S ]] } CFRA ::= SEQUENCE {occasionsRA occasions for contention free random access. If the field is absent, the UE uses the RA occasions configured in RACH-ConfigCommon in the first active UL BWP.SEQUENCE {rach-ConfigGenericConfiguration of contention free random access occasions for CFRA. The UE shall ignore preambleReceivedTargetPower, preambleTransMax, powerRampingStep, ra-ResponseWindow signaled within this field and use the corresponding values provided in RACH-ConfigCommon.RACH-ConfigGeneric,ssb-perRACH-OccasionNumber of SSBs per RACH occasion.ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen} OPTIONAL -- Cond Mandatory } OPTIONAL, -- Need S resources CHOICE {ssbThe ID of an SSB transmitted by this serving cell.SEQUENCE { ssb-ResourceList SEQUENCE (SIZE(1..maxRA-SSB-Resources)) OF CFRA-SSB-Resource,ra-ssb-OccasionMaskIndexExplicitly signalled PRACH Mask Index for RA Resource selection in TS 38.321 [3]. The mask is valid for all SSB resources signalled in ssb-ResourceList.INTEGER (0..15) }, csirs SEQUENCE { csirs-ResourceList SEQUENCE (SIZE(1..maxRA-CSIRS-Resources)) OF CFRA-CSIRS-Resource, rsrp-ThresholdCSI-RS RSRP-Range } }, ..., [[totalNumberOfRA-PreamblesTotal number of preambles used for contention free random access in the RACH resources defined in CFRA, excluding preambles used for other purposes (e.g. for SI request). If the field is absent but the field occasions is present, the UE may assume all the 64 preambles are for RA. The setting should be consistent with the setting of ssb-perRACH-Occasion, if present, i.e. it should be a multiple of the number of SSBs per RACH occasion.INTEGER (1..63) OPTIONAL -- Cond Occasions ]] } CFRA-TwoStep-r16 ::= SEQUENCE {occasionsTwoStepRA-r16RA occasions for contention free random access. If the field is absent, the UE uses the RA occasions configured in RACH-ConfigCommonTwoStepRA in the first active UL BWP.SEQUENCE {rach-ConfigGenericTwoStepRA-r16Configuration of contention free random access occasions for CFRA 2-step random access type.RACH-ConfigGenericTwoStepRA-r16, ssb-PerRACH-OccasionTwoStepRA-r16 ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen} } OPTIONAL, -- Need SmsgA-CFRA-PUSCH-r16PUSCH resource configuration(s) for msgA CFRA.MsgA-PUSCH-Resource-r16,msgA-TransMax-r16Max number of MsgA preamble transmissions performed before switching to 4-step type random access (see TS 38.321 [3], clauses 5.1.1). This field is only applicable when 2-step and 4-step RA type are configured and switching to 4-step type RA is supported. If the field is absent in cfra-TwoStep, switching from 2-step RA type to 4-step RA type is not allowed.ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100, n200} OPTIONAL, -- Need S resourcesTwoStep-r16 SEQUENCE { ssb-ResourceList SEQUENCE (SIZE(1..maxRA-SSB-Resources)) OF CFRA-SSB-Resource,ra-ssb-OccasionMaskIndexExplicitly signalled PRACH Mask Index for RA Resource selection in TS 38.321 [3]. The mask is valid for all SSB resources signalled in ssb-ResourceList.INTEGER (0..15) }, ... } CFRA-SSB-Resource ::= SEQUENCE {ssbThe ID of an SSB transmitted by this serving cell.SSB-Index,ra-PreambleIndexThe preamble index that the UE shall use when performing CF-RA upon selecting the candidate beams identified by this SSB.INTEGER (0..63), ..., [[msgA-PUSCH-Resource-Index-r16Identifies the index of the PUSCH resource used for MSGA CFRA. The PUSCH resource index indicates a valid PUSCH occasion (as specified in TS 38.213 [13], clause 8.1A) and the associated DMRS resources corresponding to a PRACH slot. The PUSCH resource indexes are sequentially numbered and are mapped to valid PUSCH occasions corresponding to a PRACH slot which are ordered, first, in increasing order of frequency resource indexes for frequency multiplexed PUSCH occasions; second, in increasing order of DMRS resource indexes within a PUSCH occasion, where a DMRS resource index is determined first in an ascending order of a DMRS port index and then in an ascending order of a DMRS sequence index, third in increasing order of time resource indexes for time multiplexed PUSCH occasions within a PUSCH slot and fourth, in increasing order of indexes for PUSCH slots. For the case of contention free 2-step random access type, if this field is absent, the UE shall use the value 0.INTEGER (0..3071) OPTIONAL -- Cond 2StepCFRA ]] } CFRA-CSIRS-Resource ::= SEQUENCE {csi-RSThe ID of a CSI-RS resource defined in the measurement object associated with this serving cell.CSI-RS-Index,ra-OccasionListRA occasions that the UE shall use when performing CF-RA upon selecting the candidate beam identified by this CSI-RS. The network ensures that the RA occasion indexes provided herein are also configured by prach-ConfigurationIndex and msg1-FDM. Each RACH occasion is sequentially numbered, first, in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions; second, in increasing order of time resource indexes for time multiplexed PRACH occasions within a PRACH slot and Third, in increasing order of indexes for PRACH slots.SEQUENCE (SIZE(1..maxRA-OccasionsPerCSIRS)) OF INTEGER (0..maxRA-Occasions-1),ra-PreambleIndexThe preamble index that the UE shall use when performing CF-RA upon selecting the candidate beams identified by this SSB.INTEGER (0..63), ... } -- TAG-RACH-CONFIGDEDICATED-STOP -- ASN1STOP
CFRA-CSIRS-Resource field descriptions |
---|
csi-RS The ID of a CSI-RS resource defined in the measurement object associated with this serving cell. |
ra-OccasionList RA occasions that the UE shall use when performing CF-RA upon selecting the candidate beam identified by this CSI-RS. The network ensures that the RA occasion indexes provided herein are also configured by prach-ConfigurationIndex and msg1-FDM. Each RACH occasion is sequentially numbered, first, in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions; second, in increasing order of time resource indexes for time multiplexed PRACH occasions within a PRACH slot and Third, in increasing order of indexes for PRACH slots. |
ra-PreambleIndex The RA preamble index to use in the RA occasions associated with this CSI-RS. |
CFRA field descriptions |
---|
occasions RA occasions for contention free random access. If the field is absent, the UE uses the RA occasions configured in RACH-ConfigCommon in the first active UL BWP. |
ra-ssb-OccasionMaskIndex Explicitly signalled PRACH Mask Index for RA Resource selection in TS 38.321 [3]. The mask is valid for all SSB resources signalled in ssb-ResourceList. |
rach-ConfigGeneric Configuration of contention free random access occasions for CFRA. The UE shall ignore preambleReceivedTargetPower, preambleTransMax, powerRampingStep, ra-ResponseWindow signaled within this field and use the corresponding values provided in RACH-ConfigCommon. |
ssb-perRACH-Occasion Number of SSBs per RACH occasion. |
totalNumberOfRA-Preambles Total number of preambles used for contention free random access in the RACH resources defined in CFRA, excluding preambles used for other purposes (e.g. for SI request). If the field is absent but the field occasions is present, the UE may assume all the 64 preambles are for RA. The setting should be consistent with the setting of ssb-perRACH-Occasion, if present, i.e. it should be a multiple of the number of SSBs per RACH occasion. |
CFRA-SSB-Resource field descriptions |
---|
msgA-PUSCH-Resource-Index Identifies the index of the PUSCH resource used for MSGA CFRA. The PUSCH resource index indicates a valid PUSCH occasion (as specified in TS 38.213 [13], clause 8.1A) and the associated DMRS resources corresponding to a PRACH slot. The PUSCH resource indexes are sequentially numbered and are mapped to valid PUSCH occasions corresponding to a PRACH slot which are ordered, first, in increasing order of frequency resource indexes for frequency multiplexed PUSCH occasions; second, in increasing order of DMRS resource indexes within a PUSCH occasion, where a DMRS resource index is determined first in an ascending order of a DMRS port index and then in an ascending order of a DMRS sequence index, third in increasing order of time resource indexes for time multiplexed PUSCH occasions within a PUSCH slot and fourth, in increasing order of indexes for PUSCH slots. For the case of contention free 2-step random access type, if this field is absent, the UE shall use the value 0. |
ra-PreambleIndex The preamble index that the UE shall use when performing CF-RA upon selecting the candidate beams identified by this SSB. |
ssb The ID of an SSB transmitted by this serving cell. |
CFRA-TwoStep field descriptions |
---|
msgA-CFRA-PUSCH PUSCH resource configuration(s) for msgA CFRA. |
msgA-TransMax Max number of MsgA preamble transmissions performed before switching to 4-step type random access (see TS 38.321 [3], clauses 5.1.1). This field is only applicable when 2-step and 4-step RA type are configured and switching to 4-step type RA is supported. If the field is absent in cfra-TwoStep, switching from 2-step RA type to 4-step RA type is not allowed. |
occasionsTwoStepRA RA occasions for contention free random access. If the field is absent, the UE uses the RA occasions configured in RACH-ConfigCommonTwoStepRA in the first active UL BWP. |
ra-SSB-OccasionMaskIndex Explicitly signalled PRACH Mask Index for RA Resource selection in TS 38.321 [3]. The mask is valid for all SSB resources signalled in ssb-ResourceList. |
rach-ConfigGenericTwoStepRA Configuration of contention free random access occasions for CFRA 2-step random access type. |
ssb-PerRACH-OccasionTwoStep Number of SSBs per RACH occasion for 2-step random access type. |
RACH-ConfigDedicated field descriptions |
---|
cfra Parameters for contention free random access to a given target cell. If this field and cfra-TwoStep are absent, the UE performs contention based random access. |
cfra-TwoStep Parameters for contention free 2-step random access type to a given target cell. Network ensures that cfra and cfra-TwoStep are not configured at the same time.If this field and cfra are absent, the UE performs contention based random access. This field may only be present if msgA-ConfigCommon is configured on the BWP. |
ra-prioritization Parameters which apply for prioritized random access procedure to a given target cell (see TS 38.321 [3], clause 5.1.1). |
ra-PrioritizationTwoStep Parameters which apply for prioritized 2-step random access type procedure to a given target cell (see TS 38.321 [3], clause 5.1.1). |
Conditional Presence | Explanation |
---|---|
Mandatory | The field is mandatory present. |
Occasions | The field is optionally present, Need S, if the field occasions is present, otherwise it is absent. |
2StepCFRA | The field is optionally present for the case of 2-step RA type contention free random access, Need S, otherwise it is absent. |
The IE RACH-ConfigGeneric is used to specify the random-access parameters both for regular random access as well as for beam failure recovery.
-- ASN1START -- TAG-RACH-CONFIGGENERIC-START RACH-ConfigGeneric ::= SEQUENCE {prach-ConfigurationIndexPRACH configuration index. For prach-ConfigurationIndex configured under beamFailureRecovery-Config, the prach-ConfigurationIndex can only correspond to the short preamble format, (see TS 38.211 [16], clause 6.3.3.2). If the field prach-ConfigurationIndex-v1610 is present, the UE shall ignore the value provided in prach-ConfigurationIndex (without suffix).INTEGER (0..255),msg1-FDMThe number of PRACH transmission occasions FDMed in one time instance. (see TS 38.211 [16], clause 6.3.3.2).ENUMERATED {one, two, four, eight},msg1-FrequencyStartOffset of lowest PRACH transmission occasion in frequency domain with respective to PRB 0. The value is configured so that the corresponding RACH resource is entirely within the bandwidth of the UL BWP. (see TS 38.211 [16], clause 6.3.3.2).INTEGER (0..maxNrofPhysicalResourceBlocks-1),zeroCorrelationZoneConfigN-CS configuration, see Table 6.3.3.1-5 in TS 38.211 [16].INTEGER(0..15),preambleReceivedTargetPowerThe target power level at the network receiver side (see TS 38.213 [13], clause 7.4, TS 38.321 [3], clauses 5.1.2, 5.1.3). Only multiples of 2 dBm may be chosen (e.g. -202, -200, -198, ...).INTEGER (-202..-60),preambleTransMaxMax number of RA preamble transmission performed before declaring a failure (see TS 38.321 [3], clauses 5.1.4, 5.1.5).ENUMERATED {n3, n4, n5, n6, n7, n8, n10, n20, n50, n100, n200},powerRampingStepPower ramping steps for PRACH (see TS 38.321 [3],5.1.3).ENUMERATED {dB0, dB2, dB4, dB6},ra-ResponseWindowMsg2 (RAR) window length in number of slots. The network configures a value lower than or equal to 10 ms when Msg2 is transmitted in licensed spectrum and a value lower than or equal to 40 ms when Msg2 is transmitted with shared spectrum channel access (see TS 38.321 [3], clause 5.1.4). UE ignores the field if included in SCellConfig. If ra-ResponseWindow-v1610 is signalled, UE shall ignore the ra-ResponseWindow (without suffix).ENUMERATED {sl1, sl2, sl4, sl8, sl10, sl20, sl40, sl80}, ..., [[prach-ConfigurationPeriodScaling-IAB-r16Scaling factor to extend the periodicity of the baseline configuration indicated by prach-ConfigurationIndex and is used only by the IAB-MT. Value scf1 corresponds to scaling factor of 1 and so on. (see TS 38.211 [16], clause 6.3.3.2).ENUMERATED {scf1,scf2,scf4,scf8,scf16,scf32,scf64} OPTIONAL, -- Need Rprach-ConfigurationFrameOffset-IAB-r16Frame offset for ROs defined in the baseline configuration indicated by prach-ConfigurationIndex and is used only by the IAB-MT. (see TS 38.211 [16], clause 6.3.3.2).INTEGER (0..63) OPTIONAL, -- Need Rprach-ConfigurationSOffset-IAB-r16Subframe/Slot offset for ROs defined in the baseline configuration indicated by prach-ConfigurationIndex and is used only by the IAB-MT. (see TS 38.211 [16], clause 6.3.3.2).INTEGER (0..39) OPTIONAL, -- Need R ra-ResponseWindow-v1610 ENUMERATED { sl60, sl160} OPTIONAL, -- Need R prach-ConfigurationIndex-v1610 INTEGER (256..262) OPTIONAL -- Need R ]] } -- TAG-RACH-CONFIGGENERIC-STOP -- ASN1STOP
RACH-ConfigGeneric field descriptions |
---|
msg1-FDM The number of PRACH transmission occasions FDMed in one time instance. (see TS 38.211 [16], clause 6.3.3.2). |
msg1-FrequencyStart Offset of lowest PRACH transmission occasion in frequency domain with respective to PRB 0. The value is configured so that the corresponding RACH resource is entirely within the bandwidth of the UL BWP. (see TS 38.211 [16], clause 6.3.3.2). |
powerRampingStep Power ramping steps for PRACH (see TS 38.321 [3],5.1.3). |
prach-ConfigurationFrameOffset-IAB Frame offset for ROs defined in the baseline configuration indicated by prach-ConfigurationIndex and is used only by the IAB-MT. (see TS 38.211 [16], clause 6.3.3.2). |
prach-ConfigurationIndex PRACH configuration index. For prach-ConfigurationIndex configured under beamFailureRecovery-Config, the prach-ConfigurationIndex can only correspond to the short preamble format, (see TS 38.211 [16], clause 6.3.3.2). If the field prach-ConfigurationIndex-v1610 is present, the UE shall ignore the value provided in prach-ConfigurationIndex (without suffix). |
prach-ConfigurationPeriodScaling-IAB Scaling factor to extend the periodicity of the baseline configuration indicated by prach-ConfigurationIndex and is used only by the IAB-MT. Value scf1 corresponds to scaling factor of 1 and so on. (see TS 38.211 [16], clause 6.3.3.2). |
prach-ConfigurationSOffset-IAB Subframe/Slot offset for ROs defined in the baseline configuration indicated by prach-ConfigurationIndex and is used only by the IAB-MT. (see TS 38.211 [16], clause 6.3.3.2). |
preambleReceivedTargetPower The target power level at the network receiver side (see TS 38.213 [13], clause 7.4, TS 38.321 [3], clauses 5.1.2, 5.1.3). Only multiples of 2 dBm may be chosen (e.g. -202, -200, -198, ...). |
preambleTransMax Max number of RA preamble transmission performed before declaring a failure (see TS 38.321 [3], clauses 5.1.4, 5.1.5). |
ra-ResponseWindow Msg2 (RAR) window length in number of slots. The network configures a value lower than or equal to 10 ms when Msg2 is transmitted in licensed spectrum and a value lower than or equal to 40 ms when Msg2 is transmitted with shared spectrum channel access (see TS 38.321 [3], clause 5.1.4). UE ignores the field if included in SCellConfig. If ra-ResponseWindow-v1610 is signalled, UE shall ignore the ra-ResponseWindow (without suffix). |
zeroCorrelationZoneConfig N-CS configuration, see Table 6.3.3.1-5 in TS 38.211 [16]. |
The IE RACH-ConfigGenericTwoStepRA is used to specify the 2-step random access type parameters.
-- ASN1START -- TAG-RACH-CONFIGGENERICTWOSTEPRA-START RACH-ConfigGenericTwoStepRA-r16 ::= SEQUENCE {msgA-PRACH-ConfigurationIndex-r16Cell-specific PRACH configuration index for 2-step RA type. If the field is absent the UE shall use the value of corresponding 4-step random access parameter in the configured BWP. If the value is in the range of 256 to 262, the field prach-ConfigurationIndex-v1610 should be considered configured (see TS 38.211 [16], clause 6.3.3.2). This field may only be present if no 4-step type RA is configured in the BWP or in the case of separate ROs with 4-step type RA.INTEGER (0..262) OPTIONAL, -- Cond 2StepOnlymsgA-RO-FDM-r16The number of msgA PRACH transmission occasions Frequency-Division Multiplexed in one time instance. If the field is absent, UE shall use value of msg1-FDM in RACH-ConfigGeneric in the configured BWP (see TS 38.211 [16], clause 6.3.3.2). This field may only be present if no 4-step type RA is configured in the BWP or in the case of separate ROs with 4-step type RA.ENUMERATED {one, two, four, eight} OPTIONAL, -- Cond 2StepOnlymsgA-RO-FrequencyStart-r16Offset of lowest PRACH transmissions occasion in frequency domain with respect to PRB 0. If the field is absent, UE shall use value of msg1-FrequencyStart in RACH-ConfigGeneric in the configured BWP (see TS 38.211 [16], clauses 5.3.2 and 6.3.3.2). This field may only be present if no 4-step type RA is configured in the BWP or in the case of separate ROs with 4-step type RA.INTEGER (0..maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Cond 2StepOnlymsgA-ZeroCorrelationZoneConfig-r16N-CS configuration for msgA preamble, see Table 6.3.3.1-5 in TS 38.211 [16]. If the field is absent, UE shall use value zeroCorrelationZoneConfig in RACH-ConfigGeneric in the configured BWP. This field may only be present if no 4-step type RA is configured in the BWP or in the case of separate ROs with 4-step type RA.INTEGER (0..15) OPTIONAL, -- Cond 2StepOnlymsgA-PreamblePowerRampingStep-r16Power ramping steps for msgA PRACH. If the field is absent, UE shall use the value of powerRampingStep in RACH-ConfigGeneric in the configured BWP (see TS 38.321 [3], 5.1.3). This field may only be present if no 4-step type RA is configured in the BWP or in the case of separate ROs with 4-step type RA. The field is absent if RACH-ConfigGenericTwoStepRA is included in CFRA-TwoStep in RACH-ConfigDedicated and thenthe UE uses the value of msgA-PreamblePowerRampingStep in RACH-ConfigGenericTwoStepRA configured forCBRA.ENUMERATED {dB0, dB2, dB4, dB6} OPTIONAL, -- Cond 2StepOnlyNoCFRAmsgA-PreambleReceivedTargetPower-r16The target power level at the network receiver side (see TS 38.213 [13], clause 7.1.1 and TS 38.321 [3], clause 5.1.1). Only multiples of 2 dBm may be chosen (e.g -202, -200, -198, …). If the field is absent, UE shall use the value of preambleReceivedTargetPower in RACH-ConfigGeneric in the configured BWP. This field may only be present if no 4-step type RA is configured in the BWP. The field is absent if RACH-ConfigGenericTwoStepRA is included in CFRA-TwoStep in RACH-ConfigDedicated and thenthe UE uses the value of msgA-PreambleReceivedTargetPowerin RACH-ConfigGenericTwoStepRA configured forCBRA.INTEGER (-202..-60) OPTIONAL, -- Cond 2StepOnlyNoCFRAmsgB-ResponseWindow-r16MsgB monitoring window length in number of slots. The network configures a value lower than or equal to 40ms (see TS 38.321 [3], clause 5.1.1). If the field is absent,the UE uses the value of msgB-ResponseWindow in RACH-ConfigGenericTwoStepRA configured for CBRA.ENUMERATED {sl1, sl2, sl4, sl8, sl10, sl20, sl40, sl80, sl160, sl320} OPTIONAL, -- Cond NoCFRApreambleTransMax-r16Max number of RA preamble transmission performed before declaring a failure (see TS 38.321 [3], clauses 5.1.4, 5.1.5). If the field is absent, UE shall use the value of preambleTransMax in RACH-ConfigGeneric in the configured BWP. The field is absent if RACH-ConfigGenericTwoStepRA is included in CFRA-TwoStep in RACH-ConfigDedicated and thenthe UE uses the value of preambleTransMaxin RACH-ConfigGenericTwoStepRA configured forCBRA.ENUMERATED {n3, n4, n5, n6, n7, n8, n10, n20, n50, n100, n200} OPTIONAL, -- Cond 2StepOnlyNoCFRA ... } -- TAG-RACH-CONFIGGENERICTWOSTEPRA-STOP -- ASN1STOP
RACH-ConfigGenericTwoStepRA field descriptions |
---|
msgA-PreamblePowerRampingStep Power ramping steps for msgA PRACH. If the field is absent, UE shall use the value of powerRampingStep in RACH-ConfigGeneric in the configured BWP (see TS 38.321 [3], 5.1.3). This field may only be present if no 4-step type RA is configured in the BWP or in the case of separate ROs with 4-step type RA. The field is absent if RACH-ConfigGenericTwoStepRA is included in CFRA-TwoStep in RACH-ConfigDedicated and thenthe UE uses the value of msgA-PreamblePowerRampingStep in RACH-ConfigGenericTwoStepRA configured forCBRA. |
msgA-PreambleReceivedTargetPower The target power level at the network receiver side (see TS 38.213 [13], clause 7.1.1 and TS 38.321 [3], clause 5.1.1). Only multiples of 2 dBm may be chosen (e.g -202, -200, -198, …). If the field is absent, UE shall use the value of preambleReceivedTargetPower in RACH-ConfigGeneric in the configured BWP. This field may only be present if no 4-step type RA is configured in the BWP. The field is absent if RACH-ConfigGenericTwoStepRA is included in CFRA-TwoStep in RACH-ConfigDedicated and thenthe UE uses the value of msgA-PreambleReceivedTargetPowerin RACH-ConfigGenericTwoStepRA configured forCBRA. |
msgA-PRACH-ConfigurationIndex Cell-specific PRACH configuration index for 2-step RA type. If the field is absent the UE shall use the value of corresponding 4-step random access parameter in the configured BWP. If the value is in the range of 256 to 262, the field prach-ConfigurationIndex-v1610 should be considered configured (see TS 38.211 [16], clause 6.3.3.2). This field may only be present if no 4-step type RA is configured in the BWP or in the case of separate ROs with 4-step type RA. |
msgA-RO-FDM The number of msgA PRACH transmission occasions Frequency-Division Multiplexed in one time instance. If the field is absent, UE shall use value of msg1-FDM in RACH-ConfigGeneric in the configured BWP (see TS 38.211 [16], clause 6.3.3.2). This field may only be present if no 4-step type RA is configured in the BWP or in the case of separate ROs with 4-step type RA. |
msgA-RO-FrequencyStart Offset of lowest PRACH transmissions occasion in frequency domain with respect to PRB 0. If the field is absent, UE shall use value of msg1-FrequencyStart in RACH-ConfigGeneric in the configured BWP (see TS 38.211 [16], clauses 5.3.2 and 6.3.3.2). This field may only be present if no 4-step type RA is configured in the BWP or in the case of separate ROs with 4-step type RA. |
msgA-ZeroCorrelationZoneConfig N-CS configuration for msgA preamble, see Table 6.3.3.1-5 in TS 38.211 [16]. If the field is absent, UE shall use value zeroCorrelationZoneConfig in RACH-ConfigGeneric in the configured BWP. This field may only be present if no 4-step type RA is configured in the BWP or in the case of separate ROs with 4-step type RA. |
msgB-ResponseWindow MsgB monitoring window length in number of slots. The network configures a value lower than or equal to 40ms (see TS 38.321 [3], clause 5.1.1). If the field is absent,the UE uses the value of msgB-ResponseWindow in RACH-ConfigGenericTwoStepRA configured for CBRA. |
preambleTransMax Max number of RA preamble transmission performed before declaring a failure (see TS 38.321 [3], clauses 5.1.4, 5.1.5). If the field is absent, UE shall use the value of preambleTransMax in RACH-ConfigGeneric in the configured BWP. The field is absent if RACH-ConfigGenericTwoStepRA is included in CFRA-TwoStep in RACH-ConfigDedicated and thenthe UE uses the value of preambleTransMaxin RACH-ConfigGenericTwoStepRA configured forCBRA. |
Conditional Presence | Explanation |
---|---|
2StepOnly | The field is mandatory present if there are no 4-step random access configurations configured in the BWP, i.e only 2-step random access type configured in the BWP, otherwise the field is optionally present, Need S. |
2StepOnlyNoCFRA | The field is mandatory present if RACH-ConfigGenericTwoStepRA is included in the RACH-ConfigCommonTwoStepRA and there are no 4-step random access configurations configured in the BWP (i.e only 2-step random access type configured in the BWP), otherwise (i.e. 4-step random access configuration also exists in the BWP) the field is optionally present, Need S. When RACH-ConfigGenericTwoStepRA is included in the RACH-ConfigDedicated, this field is absent. |
NoCFRA | The field is mandatory present if RACH-ConfigGenericTwoStepRA is not included in CFRA-TwoStep in RACH-ConfigDedicated, otherwise the field is absent, Need S. |
The IE RA-Prioritization is used to configure prioritized random access.
-- ASN1START -- TAG-RA-PRIORITIZATION-START RA-Prioritization ::= SEQUENCE { powerRampingStepHighPriority ENUMERATED {dB0, dB2, dB4, dB6},scalingFactorBIScaling factor for the backoff indicator (BI) for the prioritized random access procedure. (see TS 38.321 [3], clause 5.1.4). Value zero corresponds to 0, value dot25 corresponds to 0.25 and so on.ENUMERATED {zero, dot25, dot5, dot75} OPTIONAL, -- Need R ... } -- TAG-RA-PRIORITIZATION-STOP -- ASN1STOP
RA-Prioritization field descriptions |
---|
powerRampingStepHighPrioritiy Power ramping step applied for prioritized random access procedure. |
scalingFactorBI Scaling factor for the backoff indicator (BI) for the prioritized random access procedure. (see TS 38.321 [3], clause 5.1.4). Value zero corresponds to 0, value dot25 corresponds to 0.25 and so on. |
The IE RadioBearerConfig is used to add, modify and release signalling and/or data radio bearers. Specifically, this IE carries the parameters for PDCP and, if applicable, SDAP entities for the radio bearers.
-- ASN1START -- TAG-RADIOBEARERCONFIG-START RadioBearerConfig ::= SEQUENCE { srb-ToAddModList SRB-ToAddModList OPTIONAL, -- Cond HO-Connsrb3-ToReleaseRelease SRB3. SRB3 release can only be done over SRB1 and only at SCG release and reconfiguration with sync.ENUMERATED{true} OPTIONAL, -- Need N drb-ToAddModList DRB-ToAddModList OPTIONAL, -- Cond HO-toNR drb-ToReleaseList DRB-ToReleaseList OPTIONAL, -- Need NsecurityConfigIndicates the security algorithm and key to use for the signalling and data radio bearers configured with the list in this IE RadioBearerConfig. When the field is not included after AS security has been activated, the UE shall continue to use the currently configured keyToUse and security algorithm for the radio bearers reconfigured with the lists in this IE RadioBearerConfig. The field is not included when configuring SRB1 before AS security is activated.SecurityConfig OPTIONAL, -- Need M ... } SRB-ToAddModList ::= SEQUENCE (SIZE (1..2)) OF SRB-ToAddMod SRB-ToAddMod ::= SEQUENCE {srb-IdentityValue 1 is applicable for SRB1 only. Value 2 is applicable for SRB2 only. Value 3 is applicable for SRB3 only.SRB-Identity,reestablishPDCPIndicates that PDCP should be re-established. Network sets this to true whenever the security key used for this radio bearer changes. Key change could for example be due to reconfiguration with sync, for SRB2 when resuming an RRC connection, or at the first reconfiguration after RRC connection reestablishment in NR. For SRB1, when resuming an RRC connection, or at the first reconfiguration after RRC connection reestablishment in NR, the network does not set this field to true. For LTE SRBs using NR PDCP, it could be for handover, RRC connection reestablishment or resume. Network doesn't include this field if any DAPS bearer is configured.ENUMERATED{true} OPTIONAL, -- Need NdiscardOnPDCPIndicates that PDCP should discard stored SDU and PDU according to TS 38.323 [5].ENUMERATED{true} OPTIONAL, -- Need N pdcp-Config PDCP-Config OPTIONAL, -- Cond PDCP ... } DRB-ToAddModList ::= SEQUENCE (SIZE (1..maxDRB)) OF DRB-ToAddMod DRB-ToAddMod ::= SEQUENCE {cnAssociationIndicates if the bearer is associated with the eps-bearerIdentity (when connected to EPC) or sdap-Config (when connected to 5GC).CHOICE {eps-BearerIdentityThe EPS bearer ID determines the EPS bearer.INTEGER (0..15),sdap-ConfigThe SDAP configuration determines how to map QoS flows to DRBs when NR or E-UTRA connects to the 5GC and presence/absence of UL/DL SDAP headers.SDAP-Config } OPTIONAL, -- Cond DRBSetupdrb-IdentityIn case of DC, the DRB identity is unique within the scope of the UE, i.e. an MCG DRB cannot use the same value as a split DRB. For a split DRB the same identity is used for the MCG and SCG parts of the configuration.DRB-Identity,reestablishPDCPIndicates that PDCP should be re-established. Network sets this to true whenever the security key used for this radio bearer changes. Key change could for example be due to reconfiguration with sync, for SRB2 when resuming an RRC connection, or at the first reconfiguration after RRC connection reestablishment in NR. For SRB1, when resuming an RRC connection, or at the first reconfiguration after RRC connection reestablishment in NR, the network does not set this field to true. For LTE SRBs using NR PDCP, it could be for handover, RRC connection reestablishment or resume. Network doesn't include this field if any DAPS bearer is configured.ENUMERATED{true} OPTIONAL, -- Need NrecoverPDCPIndicates that PDCP should perform recovery according to TS 38.323 [5]. Network doesn't include this field if the bearer is configured as DAPS bearer.ENUMERATED{true} OPTIONAL, -- Need N pdcp-Config PDCP-Config OPTIONAL, -- Cond PDCP ..., [[daps-Config-r16Indicates that the bearer is configured as DAPS bearer.ENUMERATED{true} OPTIONAL -- Cond DAPS ]] } DRB-ToReleaseList ::= SEQUENCE (SIZE (1..maxDRB)) OF DRB-Identity SecurityConfig ::= SEQUENCE {securityAlgorithmConfigIndicates the security algorithm for the signalling and data radio bearers configured with the list in this IE RadioBearerConfig. When the field is not included, the UE shall continue to use the currently configured security algorithm for the radio bearers reconfigured with the lists in this IE RadioBearerConfig.SecurityAlgorithmConfig OPTIONAL, -- Cond RBTermChange1keyToUseIndicates if the bearers configured with the list in this IE RadioBearerConfig are using the master key or the secondary key for deriving ciphering and/or integrity protection keys. For MR-DC, network should not configure SRB1 and SRB2 with secondary key and SRB3 with the master key. When the field is not included, the UE shall continue to use the currently configured keyToUse for the radio bearers reconfigured with the lists in this IE RadioBearerConfig.ENUMERATED{master, secondary} OPTIONAL, -- Cond RBTermChange ... } -- TAG-RADIOBEARERCONFIG-STOP -- ASN1STOP
DRB-ToAddMod field descriptions |
---|
cnAssociation Indicates if the bearer is associated with the eps-bearerIdentity (when connected to EPC) or sdap-Config (when connected to 5GC). |
daps-Config Indicates that the bearer is configured as DAPS bearer. |
drb-Identity In case of DC, the DRB identity is unique within the scope of the UE, i.e. an MCG DRB cannot use the same value as a split DRB. For a split DRB the same identity is used for the MCG and SCG parts of the configuration. |
eps-BearerIdentity The EPS bearer ID determines the EPS bearer. |
reestablishPDCP Indicates that PDCP should be re-established. Network sets this to true whenever the security key used for this radio bearer changes. Key change could for example be due to termination point change for the bearer,reconfiguration with sync, resuming an RRC connection, or the first reconfiguration after reestablishment. It is also applicable for LTE procedures when NR PDCP is configured. Network doesn't include this field for DRB if the bearer is configured as DAPS bearer. |
recoverPDCP Indicates that PDCP should perform recovery according to TS 38.323 [5]. Network doesn't include this field if the bearer is configured as DAPS bearer. |
sdap-Config The SDAP configuration determines how to map QoS flows to DRBs when NR or E-UTRA connects to the 5GC and presence/absence of UL/DL SDAP headers. |
RadioBearerConfig field descriptions |
---|
securityConfig Indicates the security algorithm and key to use for the signalling and data radio bearers configured with the list in this IE RadioBearerConfig. When the field is not included after AS security has been activated, the UE shall continue to use the currently configured keyToUse and security algorithm for the radio bearers reconfigured with the lists in this IE RadioBearerConfig. The field is not included when configuring SRB1 before AS security is activated. |
srb3-ToRelease Release SRB3. SRB3 release can only be done over SRB1 and only at SCG release and reconfiguration with sync. |
SecurityConfig field descriptions |
---|
keyToUse Indicates if the bearers configured with the list in this IE RadioBearerConfig are using the master key or the secondary key for deriving ciphering and/or integrity protection keys. For MR-DC, network should not configure SRB1 and SRB2 with secondary key and SRB3 with the master key. When the field is not included, the UE shall continue to use the currently configured keyToUse for the radio bearers reconfigured with the lists in this IE RadioBearerConfig. |
securityAlgorithmConfig Indicates the security algorithm for the signalling and data radio bearers configured with the list in this IE RadioBearerConfig. When the field is not included, the UE shall continue to use the currently configured security algorithm for the radio bearers reconfigured with the lists in this IE RadioBearerConfig. |
SRB-ToAddMod field descriptions |
---|
discardOnPDCP Indicates that PDCP should discard stored SDU and PDU according to TS 38.323 [5]. |
reestablishPDCP Indicates that PDCP should be re-established. Network sets this to true whenever the security key used for this radio bearer changes. Key change could for example be due to reconfiguration with sync, for SRB2 when resuming an RRC connection, or at the first reconfiguration after RRC connection reestablishment in NR. For SRB1, when resuming an RRC connection, or at the first reconfiguration after RRC connection reestablishment in NR, the network does not set this field to true. For LTE SRBs using NR PDCP, it could be for handover, RRC connection reestablishment or resume. Network doesn't include this field if any DAPS bearer is configured. |
srb-Identity Value 1 is applicable for SRB1 only. Value 2 is applicable for SRB2 only. Value 3 is applicable for SRB3 only. |
Conditional Presence | Explanation |
---|---|
RBTermChange | The field is mandatory present in case of: -set up of signalling and data radio bearer, -change of termination point for the radio bearer between MN and SN. It is optionally present otherwise, Need S. |
RBTermChange1 | The field is mandatory present in case of: -set up of signalling and data radio bearer, -change of termination point for the radio bearer between MN and SN, -handover from E-UTRA/EPC or E-UTRA/5GC to NR, -handover from NR or E-UTRA/EPC to E-UTRA/5GC if the UE supports NGEN-DC. It is optionally present otherwise, Need S. |
PDCP | The field is mandatory present if the corresponding DRB is being setup or corresponding DRB is reconfigured with NR PDCP or corresponding SRB associated with two RLC entities is being setup or if the number of RLC bearers associated with the DRB or SRB is changed. The field is optionally present, Need S, if the corresponding SRB associated with one RLC entity is being setup or corresponding SRB is reconfigured with NR PDCP; otherwise the field is optionally present, need M. |
DRBSetup | The field is mandatory present if the corresponding DRB is being setup; otherwise the field is optionally present, need M. |
HO-Conn | The field is mandatory present -in case of inter-system handover from E-UTRA/EPC to E-UTRA/5GC or NR, -or when the fullConfig is included in the RRCReconfiguration messageand NE-DC/NR-DC is not configured, -or in case of RRCSetup. Otherwise the field is optionally present, need N. Upon RRCSetup, only SRB1 can be present. |
HO-toNR | The field is mandatory present -in case of inter-system handover from E-UTRA/EPC to E-UTRA/5GC or NR, -or when the fullConfig is included in the RRCReconfiguration message and NE-DC/NR-DC is not configured. In case of RRCSetup, the field is absent; otherwise the field is optionally present, need N. |
DAPS | The field is optionally present, need N, in case masterCellGroup includes ReconfigurationWithSync, SCell(s) and SCG are not configured, multi-DCI/single-DCI based multi-TRP are not configured in any DL BWP, supplementaryUplink is not configured, ethernetHeaderCompression is not configured for the DRB, conditionalReconfiguration for CHO is not configured, and NR sidelink and V2X sidelinkare not configured. Otherwise the field is absent. |
The IE RadioLinkMonitoringConfig is used to configure radio link monitoring for detection of beam- and/or cell radio link failure. See also TS 38.321 [3], clause 5.1.1.
-- ASN1START -- TAG-RADIOLINKMONITORINGCONFIG-START RadioLinkMonitoringConfig ::= SEQUENCE {failureDetectionResourcesToAddModListA list of reference signals for detecting beam failure and/or cell level radio link failure (RLF). The limits of the reference signals that the network can configure are specified in TS 38.213 [13], table 5-1. The network configures at most two detectionResources per BWP for the purpose beamFailure or both. If no RSs are provided for the purpose of beam failure detection, the UE performs beam monitoring based on the activated TCI-State for PDCCH as described in TS 38.213 [13], clause 6. If no RSs are provided in this list for the purpose of RLF detection, the UE performs Cell-RLM based on the activated TCI-State of PDCCH as described in TS 38.213 [13], clause 5. The network ensures that the UE has a suitable set of reference signals for performing cell-RLM.SEQUENCE (SIZE(1..maxNrofFailureDetectionResources)) OF RadioLinkMonitoringRS OPTIONAL, -- Need N failureDetectionResourcesToReleaseList SEQUENCE (SIZE(1..maxNrofFailureDetectionResources)) OF RadioLinkMonitoringRS-Id OPTIONAL, -- Need NbeamFailureInstanceMaxCountThis field determines after how many beam failure events the UE triggers beam failure recovery (see TS 38.321 [3], clause 5.17). Value n1 corresponds to 1 beam failure instance, value n2 corresponds to 2 beam failure instances and so on.ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10} OPTIONAL, -- Need RbeamFailureDetectionTimerTimer for beam failure detection (see TS 38.321 [3], clause 5.17). See also the BeamFailureRecoveryConfig IE. Value in number of "Qout,LR reporting periods of Beam Failure Detection" Reference Signal (see TS 38.213 [13], clause 6). Value pbfd1 corresponds to 1 Qout,LR reporting period of Beam Failure Detection Reference Signal, value pbfd2 corresponds to 2 Qout,LR reporting periods of Beam Failure Detection Reference Signal and so on.ENUMERATED {pbfd1, pbfd2, pbfd3, pbfd4, pbfd5, pbfd6, pbfd8, pbfd10} OPTIONAL, -- Need R ... } RadioLinkMonitoringRS ::= SEQUENCE { radioLinkMonitoringRS-Id RadioLinkMonitoringRS-Id,purposeDetermines whether the UE shall monitor the associated reference signal for the purpose of cell- and/or beam failure detection. For SCell, network only configures the value to beamFailure.ENUMERATED {beamFailure, rlf, both},detectionResourceA reference signal that the UE shall use for radio link monitoring or beam failure detection (depending on the indicated purpose). Only periodic 1-port CSI-RS can be configured on SCell for beam failure detection purpose.CHOICE { ssb-Index SSB-Index, csi-RS-Index NZP-CSI-RS-ResourceId }, ... } -- TAG-RADIOLINKMONITORINGCONFIG-STOP -- ASN1STOP
RadioLinkMonitoringConfig field descriptions |
---|
beamFailureDetectionTimer Timer for beam failure detection (see TS 38.321 [3], clause 5.17). See also the BeamFailureRecoveryConfig IE. Value in number of "Qout,LR reporting periods of Beam Failure Detection" Reference Signal (see TS 38.213 [13], clause 6). Value pbfd1 corresponds to 1 Qout,LR reporting period of Beam Failure Detection Reference Signal, value pbfd2 corresponds to 2 Qout,LR reporting periods of Beam Failure Detection Reference Signal and so on. |
beamFailureInstanceMaxCount This field determines after how many beam failure events the UE triggers beam failure recovery (see TS 38.321 [3], clause 5.17). Value n1 corresponds to 1 beam failure instance, value n2 corresponds to 2 beam failure instances and so on. |
failureDetectionResourcesToAddModList A list of reference signals for detecting beam failure and/or cell level radio link failure (RLF). The limits of the reference signals that the network can configure are specified in TS 38.213 [13], table 5-1. The network configures at most two detectionResources per BWP for the purpose beamFailure or both. If no RSs are provided for the purpose of beam failure detection, the UE performs beam monitoring based on the activated TCI-State for PDCCH as described in TS 38.213 [13], clause 6. If no RSs are provided in this list for the purpose of RLF detection, the UE performs Cell-RLM based on the activated TCI-State of PDCCH as described in TS 38.213 [13], clause 5. The network ensures that the UE has a suitable set of reference signals for performing cell-RLM. |
RadioLinkMonitoringRS field descriptions |
---|
detectionResource A reference signal that the UE shall use for radio link monitoring or beam failure detection (depending on the indicated purpose). Only periodic 1-port CSI-RS can be configured on SCell for beam failure detection purpose. |
purpose Determines whether the UE shall monitor the associated reference signal for the purpose of cell- and/or beam failure detection. For SCell, network only configures the value to beamFailure. |
The IE RadioLinkMonitoringRS-Id is used to identify one RadioLinkMonitoringRS.
The IE RAN-AreaCode is used to identify a RAN area within the scope of a tracking area.
The IE RateMatchPattern is used to configure one rate matching pattern for PDSCH,see TS 38.214 [19], clause 5.1.4.1.
-- ASN1START -- TAG-RATEMATCHPATTERN-START RateMatchPattern ::= SEQUENCE { rateMatchPatternId RateMatchPatternId, patternType CHOICE {bitmapsIndicates rate matching pattern by a pair of bitmaps resourceBlocks and symbolsInResourceBlock to define the rate match pattern within one or two slots, and a third bitmap periodicityAndPattern to define the repetition pattern with which the pattern defined by the above bitmap pair occurs.SEQUENCE {resourceBlocksA resource block level bitmap in the frequency domain. A bit in the bitmap set to 1 indicates that the UE shall apply rate matching in the corresponding resource block in accordance with the symbolsInResourceBlock bitmap. If used as cell-level rate matching pattern, the bitmap identifies "common resource blocks (CRB)". If used as BWP-level rate matching pattern, the bitmap identifies "physical resource blocks" inside the BWP. The first/ leftmost bit corresponds to resource block 0, and so on (see TS 38.214 [19], clause 5.1.4.1).BIT STRING (SIZE (275)),symbolsInResourceBlockA symbol level bitmap in time domain. It indicates with a bit set to true that the UE shall rate match around the corresponding symbol. This pattern recurs (in time domain) with the configured periodicityAndPattern (see TS 38.214 [19], clause 5.1.4.1). For oneSlot, if ECP is configured, the first 12 bits represent the symbols within the slot and the last two bits within the bitstring are ignored by the UE; Otherwise, the 14 bits represent the symbols within the slot. For twoSlots, if ECP is configured, the first 12 bits represent the symbols within the first slot and the next 12 bits represent the symbols in the second slot and the last four bits within the bit string are ignored by the UE; Otherwise, the first 14 bits represent the symbols within the first slot and the next 14 bits represent the symbols in the second slot. For the bits representing symbols in a slot, the most significant bit of the bit string represents the first symbol in the slot and the second most significant bit represents the second symbol in the slot and so on.CHOICE { oneSlot BIT STRING (SIZE (14)), twoSlots BIT STRING (SIZE (28)) },periodicityAndPatternA time domain repetition pattern at which the pattern defined by symbolsInResourceBlock and resourceBlocks recurs. This slot pattern repeats itself continuously. Absence of this field indicates the value n1 (see TS 38.214 [19], clause 5.1.4.1).CHOICE { n2 BIT STRING (SIZE (2)), n4 BIT STRING (SIZE (4)), n5 BIT STRING (SIZE (5)), n8 BIT STRING (SIZE (8)), n10 BIT STRING (SIZE (10)), n20 BIT STRING (SIZE (20)), n40 BIT STRING (SIZE (40)) } OPTIONAL, -- Need S ... },controlResourceSetThis ControlResourceSet is used as a PDSCH rate matching pattern, i.e., PDSCH reception rate matches around it. In frequency domain, the resource is determined by the frequency domain resource of the CORESET with the corresponding CORESET ID. Time domain resource is determined by the parameters of the associated search space of the CORESET. If the field controlResourceSetId-r16 is present, UE shall ignore the controlResourceSetId (without suffix).ControlResourceSetId },subcarrierSpacingThe SubcarrierSpacing for this resource pattern. If the field is absent, the UE applies the SCS of the associated BWP. The value kHz15 corresponds to µ=0, the value kHz30 corresponds to µ=1, and so on. Only the values 15 kHz, 30 kHz or 60 kHz (FR1), and 60 kHz or 120 kHz (FR2) are applicable (see TS 38.214 [19], clause 5.1.4.1).SubcarrierSpacing OPTIONAL, -- Cond CellLevel dummy ENUMERATED { dynamic, semiStatic }, ..., [[controlResourceSet-r16This ControlResourceSet is used as a PDSCH rate matching pattern, i.e., PDSCH reception rate matches around it. In frequency domain, the resource is determined by the frequency domain resource of the CORESET with the corresponding CORESET ID. Time domain resource is determined by the parameters of the associated search space of the CORESET. If the field controlResourceSetId-r16 is present, UE shall ignore the controlResourceSetId (without suffix).ControlResourceSetId-r16 OPTIONAL -- Need R ]] } -- TAG-RATEMATCHPATTERN-STOP -- ASN1STOP
RateMatchPattern field descriptions |
---|
bitmaps Indicates rate matching pattern by a pair of bitmaps resourceBlocks and symbolsInResourceBlock to define the rate match pattern within one or two slots, and a third bitmap periodicityAndPattern to define the repetition pattern with which the pattern defined by the above bitmap pair occurs. |
controlResourceSet This ControlResourceSet is used as a PDSCH rate matching pattern, i.e., PDSCH reception rate matches around it. In frequency domain, the resource is determined by the frequency domain resource of the CORESET with the corresponding CORESET ID. Time domain resource is determined by the parameters of the associated search space of the CORESET. If the field controlResourceSetId-r16 is present, UE shall ignore the controlResourceSetId (without suffix). |
periodicityAndPattern A time domain repetition pattern at which the pattern defined by symbolsInResourceBlock and resourceBlocks recurs. This slot pattern repeats itself continuously. Absence of this field indicates the value n1 (see TS 38.214 [19], clause 5.1.4.1). |
resourceBlocks A resource block level bitmap in the frequency domain. A bit in the bitmap set to 1 indicates that the UE shall apply rate matching in the corresponding resource block in accordance with the symbolsInResourceBlock bitmap. If used as cell-level rate matching pattern, the bitmap identifies "common resource blocks (CRB)". If used as BWP-level rate matching pattern, the bitmap identifies "physical resource blocks" inside the BWP. The first/ leftmost bit corresponds to resource block 0, and so on (see TS 38.214 [19], clause 5.1.4.1). |
subcarrierSpacing The SubcarrierSpacing for this resource pattern. If the field is absent, the UE applies the SCS of the associated BWP. The value kHz15 corresponds to µ=0, the value kHz30 corresponds to µ=1, and so on. Only the values 15 kHz, 30 kHz or 60 kHz (FR1), and 60 kHz or 120 kHz (FR2) are applicable (see TS 38.214 [19], clause 5.1.4.1). |
symbolsInResourceBlock A symbol level bitmap in time domain. It indicates with a bit set to true that the UE shall rate match around the corresponding symbol. This pattern recurs (in time domain) with the configured periodicityAndPattern (see TS 38.214 [19], clause 5.1.4.1). For oneSlot, if ECP is configured, the first 12 bits represent the symbols within the slot and the last two bits within the bitstring are ignored by the UE; Otherwise, the 14 bits represent the symbols within the slot. For twoSlots, if ECP is configured, the first 12 bits represent the symbols within the first slot and the next 12 bits represent the symbols in the second slot and the last four bits within the bit string are ignored by the UE; Otherwise, the first 14 bits represent the symbols within the first slot and the next 14 bits represent the symbols in the second slot. For the bits representing symbols in a slot, the most significant bit of the bit string represents the first symbol in the slot and the second most significant bit represents the second symbol in the slot and so on. |
Conditional Presence | Explanation |
---|---|
CellLevel | The field is mandatory present if the RateMatchPattern is defined on cell level. The field is absent when the RateMatchPattern is defined on BWP level. If the RateMatchPattern is defined on BWP level, the UE applies the SCS of the BWP. |
The IE RateMatchPatternId identifies one RateMatchPattern (see TS 38.214 [19], clause 5.1.4.1).
The IE RateMatchPatternLTE-CRS is used to configure a pattern to rate match around LTE CRS. See TS 38.214 [19], clause 5.1.4.2.
-- ASN1START -- TAG-RATEMATCHPATTERNLTE-CRS-START RateMatchPatternLTE-CRS ::= SEQUENCE {carrierFreqDLCenter of the LTE carrier (see TS 38.214 [19], clause 5.1.4.2).INTEGER (0..16383),carrierBandwidthDLBW of the LTE carrier in number of PRBs (see TS 38.214 [19], clause 5.1.4.2).ENUMERATED {n6, n15, n25, n50, n75, n100, spare2, spare1},mbsfn-SubframeConfigListLTE MBSFN subframe configuration (see TS 38.214 [19], clause 5.1.4.2).EUTRA-MBSFN-SubframeConfigList OPTIONAL, -- Need MnrofCRS-PortsNumber of LTE CRS antenna port to rate-match around (see TS 38.214 [19], clause 5.1.4.2).ENUMERATED {n1, n2, n4},v-ShiftShifting value v-shift in LTE to rate match around LTE CRS (see TS 38.214 [19], clause 5.1.4.2).ENUMERATED {n0, n1, n2, n3, n4, n5} } LTE-CRS-PatternList-r16 ::= SEQUENCE (SIZE (1..maxLTE-CRS-Patterns-r16)) OF RateMatchPatternLTE-CRS -- TAG-RATEMATCHPATTERNLTE-CRS-STOP -- ASN1STOP
RateMatchPatternLTE-CRS field descriptions |
---|
carrierBandwidthDL BW of the LTE carrier in number of PRBs (see TS 38.214 [19], clause 5.1.4.2). |
carrierFreqDL Center of the LTE carrier (see TS 38.214 [19], clause 5.1.4.2). |
mbsfn-SubframeConfigList LTE MBSFN subframe configuration (see TS 38.214 [19], clause 5.1.4.2). |
nrofCRS-Ports Number of LTE CRS antenna port to rate-match around (see TS 38.214 [19], clause 5.1.4.2). |
v-Shift Shifting value v-shift in LTE to rate match around LTE CRS (see TS 38.214 [19], clause 5.1.4.2). |
The IE ReferenceTimeInfo contains timing information for 5G internal system clock used for, e.g., time stamping, see TS 23.501 [32], clause 5.27.1.2.
-- ASN1START -- TAG-REFERENCETIMEINFO-START ReferenceTimeInfo-r16 ::= SEQUENCE {time-r16This field indicates time reference with 10ns granularity. The indicated time is referenced at the network, i.e., without compensating for RF propagation delay. The indicated time in 10ns unit from the origin is refDays*86400*1000*100000 + refSeconds*1000*100000 + refMilliSeconds*100000 + refTenNanoSeconds. The refDays field specifies the sequential number of days (with day count starting at 0) from the origin of the time field. If the referenceTimeInfo field is received in DLInformationTransfer message, the time field indicates the time at the ending boundary of the system frame indicated by referenceSFN. The UE considers this frame (indicated by referenceSFN) to be the frame which is nearest to the frame where the message is received (which can be either in the past or in the future). If the referenceTimeInfo field is received in SIB9, the time field indicates the time at the SFN boundary at or immediately after the ending boundary of the SI-window in which SIB9 is transmitted. If referenceTimeInfo field is received in SIB9, this field is excluded when determining changes in system information, i.e. changes of time should neither result in system information change notifications nor in a modification of valueTag in SIB1.ReferenceTime-r16,uncertainty-r16This field indicates the uncertainty of the reference time information provided by the time field. The uncertainty is 25ns multiplied by this field. If this field is absent, the uncertainty is unspecified.INTEGER (0..32767) OPTIONAL, -- Need StimeInfoType-r16If timeInfoType is not included, the time indicates the GPS time and the origin of the time field is 00:00:00 on Gregorian calendar date 6 January, 1980 (start of GPS time). If timeInfoType is set to localClock, the origin of the time is unspecified.ENUMERATED {localClock} OPTIONAL, -- Need SreferenceSFN-r16This field indicates the reference SFN corresponding to the reference time information. If referenceTimeInfo field is received in DLInformationTransfer message, this field indicates the SFN of PCell.INTEGER (0..1023) OPTIONAL -- Cond RefTime } ReferenceTime-r16 ::= SEQUENCE { refDays-r16 INTEGER (0..72999), refSeconds-r16 INTEGER (0..86399), refMilliSeconds-r16 INTEGER (0..999), refTenNanoSeconds-r16 INTEGER (0..99999) } -- TAG-REFERENCETIMEINFO-STOP -- ASN1STOP
ReferenceTimeInfo field descriptions |
---|
referenceSFN This field indicates the reference SFN corresponding to the reference time information. If referenceTimeInfo field is received in DLInformationTransfer message, this field indicates the SFN of PCell. |
time This field indicates time reference with 10ns granularity. The indicated time is referenced at the network, i.e., without compensating for RF propagation delay. The indicated time in 10ns unit from the origin is refDays*86400*1000*100000 + refSeconds*1000*100000 + refMilliSeconds*100000 + refTenNanoSeconds. The refDays field specifies the sequential number of days (with day count starting at 0) from the origin of the time field. If the referenceTimeInfo field is received in DLInformationTransfer message, the time field indicates the time at the ending boundary of the system frame indicated by referenceSFN. The UE considers this frame (indicated by referenceSFN) to be the frame which is nearest to the frame where the message is received (which can be either in the past or in the future). If the referenceTimeInfo field is received in SIB9, the time field indicates the time at the SFN boundary at or immediately after the ending boundary of the SI-window in which SIB9 is transmitted. If referenceTimeInfo field is received in SIB9, this field is excluded when determining changes in system information, i.e. changes of time should neither result in system information change notifications nor in a modification of valueTag in SIB1. |
timeInfoType If timeInfoType is not included, the time indicates the GPS time and the origin of the time field is 00:00:00 on Gregorian calendar date 6 January, 1980 (start of GPS time). If timeInfoType is set to localClock, the origin of the time is unspecified. |
uncertainty This field indicates the uncertainty of the reference time information provided by the time field. The uncertainty is 25ns multiplied by this field. If this field is absent, the uncertainty is unspecified. |
Conditional Presence | Explanation |
---|---|
RefTime | The field is mandatory present if referenceTimeInfo is included in DLInformationTransfer message; otherwise the field is absent. |
The IE RejectWaitTime is used to provide the value in seconds for timer T302.
The IE RepetitionSchemeConfig is used to configure the UE with repetition schemes as specified in TS 38.214 [19] clause 5.1.
-- ASN1START -- TAG-REPETITIONSCHEMECONFIG-START RepetitionSchemeConfig-r16 ::= CHOICE {fdm-TDM-r16Configures UE with a repetition scheme among fdmSchemeA, fdmSchemeB and tdmSchemeA as specified in clause 5.1 of TS 38.214 [19]. The network does not set this field to release. Upon reception of this field in RepetitionSchemeConfig-r16, the UE shall release slotBased if previously configured in the same instance of RepetitionSchemeConfig-r16.SetupRelease { FDM-TDM-r16 },slotBased-r16Configures UE with slot-based repetition scheme. Network always configures this field when the parameter repetitionNumber is present in IE PDSCH-TimeDomainResourceAllocationList. The network does not set this field to release. Upon reception of this field in RepetitionSchemeConfig-r16, the UE shall release fdm-TDM if previously configured in the same instance of RepetitionSchemeConfig-r16.SetupRelease { SlotBased-r16 } } RepetitionSchemeConfig-v1630 ::= SEQUENCE { slotBased-v1630 SetupRelease { SlotBased-v1630 } } FDM-TDM-r16 ::= SEQUENCE { repetitionScheme-r16 ENUMERATED {fdmSchemeA, fdmSchemeB,tdmSchemeA },startingSymbolOffsetK-r16The starting symbol of the second transmission occasion has K symbol offset relative to the last symbol of the first transmission occasion. When UE is configured with tdmSchemeA, the parameter startingSymbolOffsetK is present, otherwise absent.INTEGER (0..7) OPTIONAL -- Need R } SlotBased-r16 ::= SEQUENCE {tciMapping-r16Enables TCI state mapping method to PDSCH transmission occasions.ENUMERATED {cyclicMapping, sequentialMapping},sequenceOffsetForRV-r16For slot-based repetition scheme, selected RV sequence is applied to transmission occasions associated to the first TCI state. The RV sequence associated to the second TCI state is determined by a RV offset from that selected RV sequence.INTEGER (1..3) } SlotBased-v1630 ::= SEQUENCE {tciMapping-r16Enables TCI state mapping method to PDSCH transmission occasions.ENUMERATED {cyclicMapping, sequentialMapping},sequenceOffsetForRV-r16For slot-based repetition scheme, selected RV sequence is applied to transmission occasions associated to the first TCI state. The RV sequence associated to the second TCI state is determined by a RV offset from that selected RV sequence.INTEGER (0) } -- TAG-REPETITIONSCHEMECONFIG-STOP -- ASN1STOP
RepetitionSchemeConfig field descriptions |
---|
fdm-TDM Configures UE with a repetition scheme among fdmSchemeA, fdmSchemeB and tdmSchemeA as specified in clause 5.1 of TS 38.214 [19]. The network does not set this field to release. Upon reception of this field in RepetitionSchemeConfig-r16, the UE shall release slotBased if previously configured in the same instance of RepetitionSchemeConfig-r16. |
sequenceOffsetForRV For slot-based repetition scheme, selected RV sequence is applied to transmission occasions associated to the first TCI state. The RV sequence associated to the second TCI state is determined by a RV offset from that selected RV sequence. |
slotBased Configures UE with slot-based repetition scheme. Network always configures this field when the parameter repetitionNumber is present in IE PDSCH-TimeDomainResourceAllocationList. The network does not set this field to release. Upon reception of this field in RepetitionSchemeConfig-r16, the UE shall release fdm-TDM if previously configured in the same instance of RepetitionSchemeConfig-r16. |
startingSymbolOffsetK The starting symbol of the second transmission occasion has K symbol offset relative to the last symbol of the first transmission occasion. When UE is configured with tdmSchemeA, the parameter startingSymbolOffsetK is present, otherwise absent. |
tciMapping Enables TCI state mapping method to PDSCH transmission occasions. |
The IE ReportConfigId is used to identify a measurement reporting configuration.
The IE ReportConfigInterRAT specifies criteria for triggering of an inter-RAT measurement reporting event. The inter-RAT measurement reporting events for E-UTRA and UTRA-FDD are labelled BN with N equal to 1, 2 and so on.
-- ASN1START -- TAG-REPORTCONFIGINTERRAT-START ReportConfigInterRAT ::= SEQUENCE {reportTypeType of the configured measurement report. In (NG)EN-DC, and NR-DC, network does not configure report of type ReportCGI-EUTRAfor SCG.CHOICE { periodical PeriodicalReportConfigInterRAT, eventTriggered EventTriggerConfigInterRAT, reportCGI ReportCGI-EUTRA, ..., reportSFTD ReportSFTD-EUTRA } } ReportCGI-EUTRA ::= SEQUENCE { cellForWhichToReportCGI EUTRA-PhysCellId, ..., [[useAutonomousGaps-r16Indicates whether or not the UE is allowed to use autonomous gaps in acquiring system information from the E-UTRAN neighbour cell. When the field is included, the UE applies the corresponding value for T321.ENUMERATED {setup} OPTIONAL -- Need R ]] } ReportSFTD-EUTRA ::= SEQUENCE { reportSFTD-Meas BOOLEAN, reportRSRP BOOLEAN, ... } EventTriggerConfigInterRAT ::= SEQUENCE {eventIdChoice of inter RAT event triggered reporting criteria.CHOICE { eventB1 SEQUENCE { b1-ThresholdEUTRA MeasTriggerQuantityEUTRA,reportOnLeaveIndicates whether or not the UE shall initiate the measurement reporting procedure when the leaving condition is met for a cell in cellsTriggeredList, as specified in 5.5.4.1.BOOLEAN, hysteresis Hysteresis,timeToTriggerTime during which specific criteria for the event needs to be met in order to trigger a measurement report.TimeToTrigger, ... }, eventB2 SEQUENCE {b2-Threshold1NR threshold to be used in inter RAT measurement report triggering condition for event B2.MeasTriggerQuantity, b2-Threshold2EUTRA MeasTriggerQuantityEUTRA,reportOnLeaveIndicates whether or not the UE shall initiate the measurement reporting procedure when the leaving condition is met for a cell in cellsTriggeredList, as specified in 5.5.4.1.BOOLEAN, hysteresis Hysteresis,timeToTriggerTime during which specific criteria for the event needs to be met in order to trigger a measurement report.TimeToTrigger, ... }, ..., [[ eventB1-UTRA-FDD-r16 SEQUENCE { b1-ThresholdUTRA-FDD-r16 MeasTriggerQuantityUTRA-FDD-r16,reportOnLeave-r16Indicates whether or not the UE shall initiate the measurement reporting procedure when the leaving condition is met for a cell in cellsTriggeredList, as specified in 5.5.4.1.BOOLEAN, hysteresis-r16 Hysteresis,timeToTrigger-r16Time during which specific criteria for the event needs to be met in order to trigger a measurement report.TimeToTrigger, ... }, eventB2-UTRA-FDD-r16 SEQUENCE {b2-Threshold1-r16NR threshold to be used in inter RAT measurement report triggering condition for event B2.MeasTriggerQuantity, b2-Threshold2UTRA-FDD-r16 MeasTriggerQuantityUTRA-FDD-r16,reportOnLeave-r16Indicates whether or not the UE shall initiate the measurement reporting procedure when the leaving condition is met for a cell in cellsTriggeredList, as specified in 5.5.4.1.BOOLEAN, hysteresis-r16 Hysteresis,timeToTrigger-r16Time during which specific criteria for the event needs to be met in order to trigger a measurement report.TimeToTrigger, ... } ]] }, rsType NR-RS-Type, reportInterval ReportInterval,reportAmountNumber of measurement reports applicable for eventTriggered as well as for periodical report typesENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}, reportQuantity MeasReportQuantity,maxReportCellsMax number of non-serving cells to include in the measurement report.INTEGER (1..maxCellReport), ..., [[ reportQuantityUTRA-FDD-r16 MeasReportQuantityUTRA-FDD-r16 OPTIONAL -- Need R ]], [[ includeCommonLocationInfo-r16 ENUMERATED {true} OPTIONAL, -- Need R includeBT-Meas-r16 SetupRelease {BT-NameList-r16} OPTIONAL, -- Need M includeWLAN-Meas-r16 SetupRelease {WLAN-NameList-r16} OPTIONAL, -- Need M includeSensor-Meas-r16 SetupRelease {Sensor-NameList-r16} OPTIONAL -- Need M ]] } PeriodicalReportConfigInterRAT ::= SEQUENCE { reportInterval ReportInterval,reportAmountNumber of measurement reports applicable for eventTriggered as well as for periodical report typesENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}, reportQuantity MeasReportQuantity,maxReportCellsMax number of non-serving cells to include in the measurement report.INTEGER (1..maxCellReport), ..., [[ reportQuantityUTRA-FDD-r16 MeasReportQuantityUTRA-FDD-r16 OPTIONAL -- Need R ]], [[ includeCommonLocationInfo-r16 ENUMERATED {true} OPTIONAL, -- Need R includeBT-Meas-r16 SetupRelease {BT-NameList-r16} OPTIONAL, -- Need M includeWLAN-Meas-r16 SetupRelease {WLAN-NameList-r16} OPTIONAL, -- Need M includeSensor-Meas-r16 SetupRelease {Sensor-NameList-r16} OPTIONAL -- Need M ]] } MeasTriggerQuantityUTRA-FDD-r16 ::= CHOICE{ utra-FDD-RSCP-r16 INTEGER (-5..91), utra-FDD-EcN0-r16 INTEGER (0..49) } MeasReportQuantityUTRA-FDD-r16 ::= SEQUENCE { cpich-RSCP BOOLEAN, cpich-EcN0 BOOLEAN } -- TAG-REPORTCONFIGINTERRAT-STOP -- ASN1STOP
ReportConfigInterRAT field descriptions |
---|
reportType Type of the configured measurement report. In (NG)EN-DC, and NR-DC, network does not configure report of type ReportCGI-EUTRAfor SCG. |
ReportCGI-EUTRA field descriptions |
---|
useAutonomousGaps Indicates whether or not the UE is allowed to use autonomous gaps in acquiring system information from the E-UTRAN neighbour cell. When the field is included, the UE applies the corresponding value for T321. |
EventTriggerConfigInterRATfield descriptions |
---|
b2-Threshold1 NR threshold to be used in inter RAT measurement report triggering condition for event B2. |
bN-ThresholdEUTRA E-UTRA threshold value associated with the selected trigger quantity (RSRP, RSRQ, SINR) to be used in inter RAT measurement report triggering condition for event number bN. In the same eventB2, the network configures the same CHOICE name (rsrp, rsrq or sinr) for the MeasTriggerQuantity of the b2-Threshold1 and for the MeasTriggerQuantityEUTRA of the b2-Threshold2EUTRA. |
eventId Choice of inter RAT event triggered reporting criteria. |
maxReportCells Max number of non-serving cells to include in the measurement report. |
reportAmount Number of measurement reports applicable for eventTriggered as well as for periodical report types |
reportOnLeave Indicates whether or not the UE shall initiate the measurement reporting procedure when the leaving condition is met for a cell in cellsTriggeredList, as specified in 5.5.4.1. |
reportQuantity, reportQuantityUTRA-FDD The cell measurement quantities to be included in the measurement report. If the field eventB1-UTRA-FDD or eventB2-UTRA-FDD is present, the UE shall ignore the value(s) provided in reportQuantity. |
timeToTrigger Time during which specific criteria for the event needs to be met in order to trigger a measurement report. |
bN-ThresholdUTRA-FDD UTRA-FDD threshold value associated with the selected trigger quantity (RSCP, EcN0) to be used in inter RAT measurement report triggering condition for event number bN. utra-FDD-RSCP corresponds to CPICH_RSCP in TS 25.133 [46] for FDD. utra-FDD-EcN0 corresponds to CPICH_Ec/No in TS 25.133 [46] for FDD. For utra-FDD-RSCP: The actual value is field value – 115 dBm. For utra-FDD-EcN0: The actual value is (field value – 49)/2 dB. |
The IE ReportConfigNR specifies criteria for triggering of an NR measurement reporting event or of a CHO or CPC event. For events labelled AN with N equal to 1, 2 and so on, measurement reporting events and CHO or CPC events are based on cell measurement results, which can either be derived based on SS/PBCH block or CSI-RS. For event I1, measurement reporting event is based on CLI measurement results, which can either be derived based on SRS-RSRP or CLI-RSSI.
-- ASN1START -- TAG-REPORTCONFIGNR-START ReportConfigNR ::= SEQUENCE {reportTypeType of the configured measurement report. In MR-DC, network does not configure report of type reportCGI using SRB3. ThecondTriggerConfig is used for CHO or CPC configuration.CHOICE { periodical PeriodicalReportConfig, eventTriggered EventTriggerConfig, ..., reportCGI ReportCGI, reportSFTD ReportSFTD-NR, condTriggerConfig-r16 CondTriggerConfig-r16, cli-Periodical-r16 CLI-PeriodicalReportConfig-r16, cli-EventTriggered-r16 CLI-EventTriggerConfig-r16 } } ReportCGI ::= SEQUENCE { cellForWhichToReportCGI PhysCellId, ..., [[useAutonomousGaps-r16Indicates whether or not the UE is allowed to use autonomous gaps in acquiring system information from the NR neighbour cell. When the field is included, the UE applies the corresponding value for T321.ENUMERATED {setup} OPTIONAL -- Need R ]] } ReportSFTD-NR ::= SEQUENCE {reportSFTD-MeasIndicates whether UE is required to perform SFTD measurement between PCell and NR PSCell in NR-DC.BOOLEAN,reportRSRPIndicates whether UE is required to include RSRP result of NR PSCell or NR neighbour cells in SFTD measurement result, derived based on SSB. If it is set to true, the network should ensure that ssb-ConfigMobilityis included in the measurement object for NR PSCell or NR neighbour cells.BOOLEAN, ..., [[reportSFTD-NeighMeasIndicates whether UE is required to perform SFTD measurement between PCell and NR neighbour cells in NR standalone. The network does not include this field if reportSFTD-Meas is set to true.ENUMERATED {true} OPTIONAL, -- Need Rdrx-SFTD-NeighMeasIndicates that the UE shall use available idle periods (i.e. DRX off periods) for the SFTD measurement in NR standalone. The network only includes drx-SFTD-NeighMeas field when reprtSFTD-NeighMeas is set to true.ENUMERATED {true} OPTIONAL, -- Need R cellsForWhichToReportSFTD SEQUENCE (SIZE (1..maxCellSFTD)) OF PhysCellId OPTIONAL -- Need R ]] } CondTriggerConfig-r16 ::= SEQUENCE {condEventIdChoice of NR conditional reconfiguration event triggered criteria.CHOICE { condEventA3 SEQUENCE {a3-OffsetOffset value(s) to be used in NR conditional reconfiguration triggering condition for cond event a3. The actual value is field value * 0.5 dB.MeasTriggerQuantityOffset, hysteresis Hysteresis,timeToTriggerTime during which specific criteria for the event needs to be met in order to trigger a measurement report.TimeToTrigger }, condEventA5 SEQUENCE { a5-Threshold1 MeasTriggerQuantity, a5-Threshold2 MeasTriggerQuantity, hysteresis Hysteresis,timeToTriggerTime during which specific criteria for the event needs to be met in order to trigger a measurement report.TimeToTrigger }, ... }, rsType-r16 NR-RS-Type, ... } EventTriggerConfig::= SEQUENCE {eventIdChoice of CLI event triggered reporting criteria.CHOICE { eventA1 SEQUENCE { a1-Threshold MeasTriggerQuantity,reportOnLeaveIndicates whether or not the UE shall initiate the measurement reporting procedure when the leaving condition is met for a CLI measurement resource in srsTriggeredList or rssiTriggeredList, as specified in 5.5.4.1.BOOLEAN, hysteresis Hysteresis,timeToTriggerTime during which specific criteria for the event needs to be met in order to trigger a measurement report.TimeToTrigger }, eventA2 SEQUENCE { a2-Threshold MeasTriggerQuantity,reportOnLeaveIndicates whether or not the UE shall initiate the measurement reporting procedure when the leaving condition is met for a CLI measurement resource in srsTriggeredList or rssiTriggeredList, as specified in 5.5.4.1.BOOLEAN, hysteresis Hysteresis,timeToTriggerTime during which specific criteria for the event needs to be met in order to trigger a measurement report.TimeToTrigger }, eventA3 SEQUENCE {a3-OffsetOffset value(s) to be used in NR conditional reconfiguration triggering condition for cond event a3. The actual value is field value * 0.5 dB.MeasTriggerQuantityOffset,reportOnLeaveIndicates whether or not the UE shall initiate the measurement reporting procedure when the leaving condition is met for a CLI measurement resource in srsTriggeredList or rssiTriggeredList, as specified in 5.5.4.1.BOOLEAN, hysteresis Hysteresis,timeToTriggerTime during which specific criteria for the event needs to be met in order to trigger a measurement report.TimeToTrigger,useWhiteCellListIndicates whether only the cells included in the white-list of the associated measObject are applicable as specified in 5.5.4.1.BOOLEAN }, eventA4 SEQUENCE { a4-Threshold MeasTriggerQuantity,reportOnLeaveIndicates whether or not the UE shall initiate the measurement reporting procedure when the leaving condition is met for a CLI measurement resource in srsTriggeredList or rssiTriggeredList, as specified in 5.5.4.1.BOOLEAN, hysteresis Hysteresis,timeToTriggerTime during which specific criteria for the event needs to be met in order to trigger a measurement report.TimeToTrigger,useWhiteCellListIndicates whether only the cells included in the white-list of the associated measObject are applicable as specified in 5.5.4.1.BOOLEAN }, eventA5 SEQUENCE { a5-Threshold1 MeasTriggerQuantity, a5-Threshold2 MeasTriggerQuantity,reportOnLeaveIndicates whether or not the UE shall initiate the measurement reporting procedure when the leaving condition is met for a CLI measurement resource in srsTriggeredList or rssiTriggeredList, as specified in 5.5.4.1.BOOLEAN, hysteresis Hysteresis,timeToTriggerTime during which specific criteria for the event needs to be met in order to trigger a measurement report.TimeToTrigger,useWhiteCellListIndicates whether only the cells included in the white-list of the associated measObject are applicable as specified in 5.5.4.1.BOOLEAN }, eventA6 SEQUENCE { a6-Offset MeasTriggerQuantityOffset,reportOnLeaveIndicates whether or not the UE shall initiate the measurement reporting procedure when the leaving condition is met for a CLI measurement resource in srsTriggeredList or rssiTriggeredList, as specified in 5.5.4.1.BOOLEAN, hysteresis Hysteresis,timeToTriggerTime during which specific criteria for the event needs to be met in order to trigger a measurement report.TimeToTrigger,useWhiteCellListIndicates whether only the cells included in the white-list of the associated measObject are applicable as specified in 5.5.4.1.BOOLEAN }, ... }, rsType NR-RS-Type, reportInterval ReportInterval,reportAmountNumber of measurement reports applicable for eventTriggered as well as for periodical report typesENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity},reportQuantityCellThe cell measurement quantities to be included in the measurement report.MeasReportQuantity,maxReportCellsMax number of non-serving cells to include in the measurement report.INTEGER (1..maxCellReport),reportQuantityRS-IndexesIndicates which measurement information per RS index the UE shall include in the measurement report.MeasReportQuantity OPTIONAL, -- Need RmaxNrofRS-IndexesToReportMax number of RS indexes to include in the measurement report.INTEGER (1..maxNrofIndexesToReport) OPTIONAL, -- Need R includeBeamMeasurements BOOLEAN,reportAddNeighMeasIndicates that the UE shall include the best neighbour cells per serving frequency.ENUMERATED {setup} OPTIONAL, -- Need R ..., [[ measRSSI-ReportConfig-r16 MeasRSSI-ReportConfig-r16 OPTIONAL, -- Need RuseT312-r16If value TRUE is configured, the UE shall use the timer T312 with the value t312 as specified in the corresponding measObjectNR. If value FALSE is configured, the timer T312 is considered as disabled. Network configures value TRUEonly if reportTypeis set to eventTriggered.BOOLEAN OPTIONAL, -- Need M includeCommonLocationInfo-r16 ENUMERATED {true} OPTIONAL, -- Need R includeBT-Meas-r16 SetupRelease {BT-NameList-r16} OPTIONAL, -- Need M includeWLAN-Meas-r16 SetupRelease {WLAN-NameList-r16} OPTIONAL, -- Need M includeSensor-Meas-r16 SetupRelease {Sensor-NameList-r16} OPTIONAL -- Need M ]] } PeriodicalReportConfig ::= SEQUENCE { rsType NR-RS-Type, reportInterval ReportInterval,reportAmountNumber of measurement reports applicable for eventTriggered as well as for periodical report typesENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity},reportQuantityCellThe cell measurement quantities to be included in the measurement report.MeasReportQuantity,maxReportCellsMax number of non-serving cells to include in the measurement report.INTEGER (1..maxCellReport),reportQuantityRS-IndexesIndicates which measurement information per RS index the UE shall include in the measurement report.MeasReportQuantity OPTIONAL, -- Need RmaxNrofRS-IndexesToReportMax number of RS indexes to include in the measurement report.INTEGER (1..maxNrofIndexesToReport) OPTIONAL, -- Need R includeBeamMeasurements BOOLEAN,useWhiteCellListIndicates whether only the cells included in the white-list of the associated measObject are applicable as specified in 5.5.4.1.BOOLEAN, ..., [[ measRSSI-ReportConfig-r16 MeasRSSI-ReportConfig-r16 OPTIONAL, -- Need R includeCommonLocationInfo-r16 ENUMERATED {true} OPTIONAL, -- Need R includeBT-Meas-r16 SetupRelease {BT-NameList-r16} OPTIONAL, -- Need M includeWLAN-Meas-r16 SetupRelease {WLAN-NameList-r16} OPTIONAL, -- Need M includeSensor-Meas-r16 SetupRelease {Sensor-NameList-r16} OPTIONAL, -- Need Mul-DelayValueConfig-r16If the field is present, the UE shall perform the actual UL PDCP Packet Average Delay measurement per DRB as specified in TS 38.314 [53] and the UE shall ignore the fields reportQuantityCell and maxReportCells. The applicable values for the corresponding reportInterval are (one of the) {ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, ms20480, ms40960, min1,min6, min12, min30}. The reportInterval indicates the periodicity for performing and reporting of UL PDCP Packet Average Delay per DRB measurement as specified in TS 38.314 [53].SetupRelease { UL-DelayValueConfig-r16 } OPTIONAL, -- Need MreportAddNeighMeas-r16Indicates that the UE shall include the best neighbour cells per serving frequency.ENUMERATED {setup} OPTIONAL -- Need R ]] } NR-RS-Type ::= ENUMERATED {ssb, csi-rs} MeasTriggerQuantity ::= CHOICE { rsrp RSRP-Range, rsrq RSRQ-Range, sinr SINR-Range } MeasTriggerQuantityOffset ::= CHOICE { rsrp INTEGER (-30..30), rsrq INTEGER (-30..30), sinr INTEGER (-30..30) } MeasReportQuantity ::= SEQUENCE { rsrp BOOLEAN, rsrq BOOLEAN, sinr BOOLEAN } MeasRSSI-ReportConfig-r16 ::= SEQUENCE {channelOccupancyThreshold-r16RSSI threshold which is used for channel occupancy evaluation.RSSI-Range-r16 OPTIONAL -- Need R } CLI-EventTriggerConfig-r16 ::= SEQUENCE {eventId-r16Choice of CLI event triggered reporting criteria.CHOICE { eventI1-r16 SEQUENCE {i1-Threshold-r16Threshold value associated to the selected trigger quantity (e.g. SRS-RSRP, CLI-RSSI) to be used in CLI measurement report triggering condition for event i1.MeasTriggerQuantityCLI-r16,reportOnLeave-r16Indicates whether or not the UE shall initiate the measurement reporting procedure when the leaving condition is met for a CLI measurement resource in srsTriggeredList or rssiTriggeredList, as specified in 5.5.4.1.BOOLEAN, hysteresis-r16 Hysteresis,timeToTrigger-r16Time during which specific criteria for the event needs to be met in order to trigger a measurement report.TimeToTrigger }, ... }, reportInterval-r16 ReportInterval,reportAmount-r16Number of measurement reports applicable for eventTriggered as well as for periodical report typesENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity},maxReportCLI-r16Max number of CLI measurement resource to include in the measurement report.INTEGER (1..maxCLI-Report-r16), ... } CLI-PeriodicalReportConfig-r16 ::= SEQUENCE { reportInterval-r16 ReportInterval,reportAmount-r16Number of measurement reports applicable for eventTriggered as well as for periodical report typesENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity},reportQuantityCLI-r16The CLI measurement quantities to be included in the measurement report.MeasReportQuantityCLI-r16,maxReportCLI-r16Max number of CLI measurement resource to include in the measurement report.INTEGER (1..maxCLI-Report-r16), ... } MeasTriggerQuantityCLI-r16 ::= CHOICE { srs-RSRP-r16 SRS-RSRP-Range-r16, cli-RSSI-r16 CLI-RSSI-Range-r16 } MeasReportQuantityCLI-r16 ::= ENUMERATED {srs-rsrp, cli-rssi} -- TAG-REPORTCONFIGNR-STOP -- ASN1STOP
PeriodicalReportConfigInterRAT field descriptions |
---|
maxReportCells Max number of non-serving cells to include in the measurement report. |
reportAmount Number of measurement reports applicable for eventTriggered as well as for periodical report types |
reportQuantity, reportQuantityUTRA-FDD The cell measurement quantities to be included in the measurement report. If the field reportQuantityUTRA-FDD is present, the UE shall ignore the value(s) provided in reportQuantity. |
CondTriggerConfig field descriptions |
---|
a3-Offset Offset value(s) to be used in NR conditional reconfiguration triggering condition for cond event a3. The actual value is field value * 0.5 dB. |
a5-Threshold1/ a5-Threshold2 Threshold value associated to the selected trigger quantity (e.g. RSRP, RSRQ, SINR) per RS Type (e.g. SS/PBCH block, CSI-RS) to be used in NR conditional reconfiguration triggering condition for cond event a5. In the same condeventA5, the network configures the same quantity for the MeasTriggerQuantity of the a5-Threshold1 and for the MeasTriggerQuantity of the a5-Threshold2. |
condEventId Choice of NR conditional reconfiguration event triggered criteria. |
timeToTrigger Time during which specific criteria for the event needs to be met in order to execute the conditional reconfiguration evaluation. |
ReportConfigNRfield descriptions |
---|
reportType Type of the configured measurement report. In MR-DC, network does not configure report of type reportCGI using SRB3. ThecondTriggerConfig is used for CHO or CPC configuration. |
ReportCGIfield descriptions |
---|
useAutonomousGaps Indicates whether or not the UE is allowed to use autonomous gaps in acquiring system information from the NR neighbour cell. When the field is included, the UE applies the corresponding value for T321. |
EventTriggerConfig field descriptions |
---|
a3-Offset/a6-Offset Offset value(s) to be used in NR measurement report triggering condition for event a3/a6. The actual value is field value * 0.5 dB. |
aN-ThresholdM Threshold value associated to the selected trigger quantity (e.g. RSRP, RSRQ, SINR) per RS Type (e.g. SS/PBCH block, CSI-RS) to be used in NR measurement report triggering condition for event number aN. If multiple thresholds are defined for event number aN, the thresholds are differentiated by M. The network configures aN-Threshold1 only for events A1, A2, A4, A5 and a5-Threshold2 only for event A5. In the same eventA5, the network configures the same quantity for the MeasTriggerQuantity of the a5-Threshold1 and for the MeasTriggerQuantity of the a5-Threshold2. |
channelOccupancyThreshold RSSI threshold which is used for channel occupancy evaluation. |
eventId Choice of NR event triggered reporting criteria. |
maxNrofRS-IndexesToReport Max number of RS indexes to include in the measurement report for A1-A6 events. |
maxReportCells Max number of non-serving cells to include in the measurement report. |
reportAddNeighMeas Indicates that the UE shall include the best neighbour cells per serving frequency. |
reportAmount Number of measurement reports applicable for eventTriggered as well as for periodical report types. |
reportOnLeave Indicates whether or not the UE shall initiate the measurement reporting procedure when the leaving condition is met for a cell in cellsTriggeredList, as specified in 5.5.4.1. |
reportQuantityCell The cell measurement quantities to be included in the measurement report. |
reportQuantityRS-Indexes Indicates which measurement information per RS index the UE shall include in the measurement report. |
timeToTrigger Time during which specific criteria for the event needs to be met in order to trigger a measurement report. |
useT312 If value TRUE is configured, the UE shall use the timer T312 with the value t312 as specified in the corresponding measObjectNR. If value FALSE is configured, the timer T312 is considered as disabled. Network configures value TRUEonly if reportTypeis set to eventTriggered. |
useWhiteCellList Indicates whether only the cells included in the white-list of the associated measObject are applicable as specified in 5.5.4.1. |
CLI-EventTriggerConfig field descriptions |
---|
i1-Threshold Threshold value associated to the selected trigger quantity (e.g. SRS-RSRP, CLI-RSSI) to be used in CLI measurement report triggering condition for event i1. |
eventId Choice of CLI event triggered reporting criteria. |
maxReportCLI Max number of CLI measurement resource to include in the measurement report. |
reportAmount Number of measurement reports. |
reportOnLeave Indicates whether or not the UE shall initiate the measurement reporting procedure when the leaving condition is met for a CLI measurement resource in srsTriggeredList or rssiTriggeredList, as specified in 5.5.4.1. |
timeToTrigger Time during which specific criteria for the event needs to be met in order to trigger a measurement report. |
CLI-PeriodicalReportConfig field descriptions |
---|
maxReportCLI Max number of CLI measurement resource to include in the measurement report. |
reportAmount Number of measurement reports. |
reportQuantityCLI The CLI measurement quantities to be included in the measurement report. |
PeriodicalReportConfig field descriptions |
---|
maxNrofRS-IndexesToReport Max number of RS indexes to include in the measurement report. |
maxReportCells Max number of non-serving cells to include in the measurement report. |
reportAddNeighMeas Indicates that the UE shall include the best neighbour cells per serving frequency. |
reportAmount Number of measurement reports applicable for eventTriggered as well as for periodical report types |
reportQuantityCell The cell measurement quantities to be included in the measurement report. |
reportQuantityRS-Indexes Indicates which measurement information per RS index the UE shall include in the measurement report. |
ul-DelayValueConfig If the field is present, the UE shall perform the actual UL PDCP Packet Average Delay measurement per DRB as specified in TS 38.314 [53] and the UE shall ignore the fields reportQuantityCell and maxReportCells. The applicable values for the corresponding reportInterval are (one of the) {ms120, ms240, ms480, ms640, ms1024, ms2048, ms5120, ms10240, ms20480, ms40960, min1,min6, min12, min30}. The reportInterval indicates the periodicity for performing and reporting of UL PDCP Packet Average Delay per DRB measurement as specified in TS 38.314 [53]. |
useWhiteCellList Indicates whether only the cells included in the white-list of the associated measObject are applicable as specified in 5.5.4.1. |
ReportSFTD-NR field descriptions |
---|
cellForWhichToReportSFTD Indicates the target NR neighbour cells for SFTD measurement between PCell and NR neighbour cells. |
drx-SFTD-NeighMeas Indicates that the UE shall use available idle periods (i.e. DRX off periods) for the SFTD measurement in NR standalone. The network only includes drx-SFTD-NeighMeas field when reprtSFTD-NeighMeas is set to true. |
reportSFTD-Meas Indicates whether UE is required to perform SFTD measurement between PCell and NR PSCell in NR-DC. |
reportSFTD-NeighMeas Indicates whether UE is required to perform SFTD measurement between PCell and NR neighbour cells in NR standalone. The network does not include this field if reportSFTD-Meas is set to true. |
reportRSRP Indicates whether UE is required to include RSRP result of NR PSCell or NR neighbour cells in SFTD measurement result, derived based on SSB. If it is set to true, the network should ensure that ssb-ConfigMobilityis included in the measurement object for NR PSCell or NR neighbour cells. |
otherfield descriptions |
---|
MeasTriggerQuantity SINR is applicable only for CONNECTED mode events. |
The IE ReportConfigNR-SL specifies criteria for triggering of a CBR measurement reporting event for NR sidelink communication. Measurement reporting events are based on CBR measurement results on the corresponding transmission resource pools. These events are labelled CN with N equal to 1 and 2. Event C1:CBR of NR sidelink communication is above a threshold; Event C2:CBR of NR sidelink communication is below a threshold;
-- ASN1START -- TAG-REPORTCONFIGNR-SL-START ReportConfigNR-SL-r16 ::= SEQUENCE {reportType-r16Type of the configured CBR measurement report for NR sidelink communication.CHOICE { periodical-r16 PeriodicalReportConfigNR-SL-r16, eventTriggered-r16 EventTriggerConfigNR-SL-r16 } } EventTriggerConfigNR-SL-r16::= SEQUENCE {eventId-r16Choice of NR event triggered reporting criteria.CHOICE { eventC1 SEQUENCE { c1-Threshold-r16 SL-CBR-r16, hysteresis-r16 Hysteresis,timeToTrigger-r16Time during which specific criteria for the event needs to be met in order to trigger a measurement report.TimeToTrigger }, eventC2-r16 SEQUENCE { c2-Threshold-r16 SL-CBR-r16, hysteresis-r16 Hysteresis,timeToTrigger-r16Time during which specific criteria for the event needs to be met in order to trigger a measurement report.TimeToTrigger }, ... }, reportInterval-r16 ReportInterval,reportAmount-r16Number of measurement reports applicable for eventTriggered as well as for periodical report types.ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity},reportQuantity-r16The sidelink measurement quantities to be included in the measurement report. In this release, this is set as the CBR measurement result.MeasReportQuantity-r16, ... } PeriodicalReportConfigNR-SL-r16 ::= SEQUENCE { reportInterval-r16 ReportInterval,reportAmount-r16Number of measurement reports applicable for eventTriggered as well as for periodical report types.ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity},reportQuantity-r16The sidelink measurement quantities to be included in the measurement report. In this release, this is set as the CBR measurement result.MeasReportQuantity-r16, ... } MeasReportQuantity-r16 ::= SEQUENCE { cbr-r16 BOOLEAN, ... } -- TAG-REPORTCONFIGNR-SL-STOP -- ASN1STOP
ReportConfigNR-SL field descriptions |
---|
reportType Type of the configured CBR measurement report for NR sidelink communication. |
EventTriggerConfigNR-SL field descriptions |
---|
cN-Threshold Threshold used for events C1 and C2 specified in clauses 5.5.4.11 and 5.5.4.12, respectively. |
eventId Choice of NR event triggered reporting criteria. |
reportAmoun Number of measurement reports applicable for eventTriggered as well as for periodical report types. |
reportQuantity The sidelink measurement quantities to be included in the measurement report. In this release, this is set as the CBR measurement result. |
timeToTrigger Time during which specific criteria for the event needs to be met in order to trigger a measurement report. |
PeriodicalReportConfigNR-SL field descriptions |
---|
reportAmount Number of measurement reports applicable for eventTriggered as well as for periodical report types. |
reportQuantity The sidelink measurement quantities to be included in the measurement report. In this release, this is set as the CBR measurement result. |
The IE ReportConfigToAddModList concerns a list of reporting configurations to add or modify.
-- ASN1START -- TAG-REPORTCONFIGTOADDMODLIST-START ReportConfigToAddModList ::= SEQUENCE (SIZE (1..maxReportConfigId)) OF ReportConfigToAddMod ReportConfigToAddMod ::= SEQUENCE { reportConfigId ReportConfigId, reportConfig CHOICE { reportConfigNR ReportConfigNR, ..., reportConfigInterRAT ReportConfigInterRAT, reportConfigNR-SL-r16 ReportConfigNR-SL-r16 } } -- TAG-REPORTCONFIGTOADDMODLIST-STOP -- ASN1STOP
The IE ReportInterval indicates the interval between periodical reports. The ReportInterval is applicable if the UE performs periodical reporting (i.e. when reportAmount exceeds 1), when reportType is set to either eventTriggered, periodical, cli-EventTriggered or cli-Periodical. Value ms120 corresponds to 120 ms, value ms240 corresponds to 240 ms and so on, while value min1 corresponds to 1 min, min6 corresponds to 6 min and so on.
The IE ReselectionThreshold is used to indicate an Rx level threshold for cell reselection. Actual value of threshold = field value * 2 [dB].
The IE ReselectionThresholdQ is used to indicate a quality level threshold for cell reselection. Actual value of threshold = field value [dB].
The IE ResumeCause is used to indicate the resume cause in RRCResumeRequest and RRCResumeRequest1.
The IE RLC-BearerConfig is used to configure an RLC entity, a corresponding logical channel in MAC and the linking to a PDCP entity (served radio bearer).
-- ASN1START -- TAG-RLC-BEARERCONFIG-START RLC-BearerConfig ::= SEQUENCE {logicalChannelIdentityID used commonly for the MAC logical channel and for the RLC bearer.LogicalChannelIdentity,servedRadioBearerAssociates the RLC Bearer with an SRB or a DRB. The UE shall deliver DL RLC SDUs received via the RLC entity of this RLC bearer to the PDCP entity of the servedRadioBearer. Furthermore, the UE shall advertise and deliver uplink PDCP PDUs of the uplink PDCP entity of the servedRadioBearer to the uplink RLC entity of this RLC bearer unless the uplink scheduling restrictions (moreThanOneRLC in PDCP-Config and the restrictions in LogicalChannelConfig) forbid it to do so.CHOICE { srb-Identity SRB-Identity, drb-Identity DRB-Identity } OPTIONAL, -- Cond LCH-SetupOnlyreestablishRLCIndicates that RLC should be re-established. Network sets this to true at least whenever the security key used for the radio bearer associated with this RLC entity changes. For SRB2 and DRBs, unless full configuration is used, it is also set to true during the resumption of the RRC connection or the first reconfiguration after reestablishment.For SRB1, when resuming an RRC connection, or at the first reconfiguration after RRC connection reestablishment, the network does not set this field to true.ENUMERATED {true} OPTIONAL, -- Need Nrlc-ConfigDetermines the RLC mode (UM, AM) and provides corresponding parameters. RLC mode reconfiguration can only be performed by DRB release/addition or full configuration. The network may configure rlc-Config-v1610 only when rlc-Config (without suffix) is set to am.RLC-Config OPTIONAL, -- Cond LCH-Setup mac-LogicalChannelConfig LogicalChannelConfig OPTIONAL, -- Cond LCH-Setup ..., [[ rlc-Config-v1610 RLC-Config-v1610 OPTIONAL -- Need R ]] } -- TAG-RLC-BEARERCONFIG-STOP -- ASN1STOP
RLC-BearerConfig field descriptions |
---|
logicalChannelIdentity ID used commonly for the MAC logical channel and for the RLC bearer. |
reestablishRLC Indicates that RLC should be re-established. Network sets this to true at least whenever the security key used for the radio bearer associated with this RLC entity changes. For SRB2 and DRBs, unless full configuration is used, it is also set to true during the resumption of the RRC connection or the first reconfiguration after reestablishment.For SRB1, when resuming an RRC connection, or at the first reconfiguration after RRC connection reestablishment, the network does not set this field to true. |
rlc-Config Determines the RLC mode (UM, AM) and provides corresponding parameters. RLC mode reconfiguration can only be performed by DRB release/addition or full configuration. The network may configure rlc-Config-v1610 only when rlc-Config (without suffix) is set to am. |
servedRadioBearer Associates the RLC Bearer with an SRB or a DRB. The UE shall deliver DL RLC SDUs received via the RLC entity of this RLC bearer to the PDCP entity of the servedRadioBearer. Furthermore, the UE shall advertise and deliver uplink PDCP PDUs of the uplink PDCP entity of the servedRadioBearer to the uplink RLC entity of this RLC bearer unless the uplink scheduling restrictions (moreThanOneRLC in PDCP-Config and the restrictions in LogicalChannelConfig) forbid it to do so. |
Conditional Presence | Explanation |
---|---|
LCH-Setup | This field is mandatory present upon creation of a new logical channel for a DRB. This field is optionally present, Need S, upon creation of a new logical channel for an SRB. It is optionally present, Need M, otherwise. |
LCH-SetupOnly | This field is mandatory present upon creation of a new logical channel. It is absent, Need M otherwise. |
The IE RLC-Config is used to specify the RLC configuration of SRBs and DRBs.
-- ASN1START -- TAG-RLC-CONFIG-START RLC-Config ::= CHOICE { am SEQUENCE { ul-AM-RLC UL-AM-RLC, dl-AM-RLC DL-AM-RLC }, um-Bi-Directional SEQUENCE { ul-UM-RLC UL-UM-RLC, dl-UM-RLC DL-UM-RLC }, um-Uni-Directional-UL SEQUENCE { ul-UM-RLC UL-UM-RLC }, um-Uni-Directional-DL SEQUENCE { dl-UM-RLC DL-UM-RLC }, ... } UL-AM-RLC ::= SEQUENCE {sn-FieldLengthIndicates the RLC SN field size, see TS 38.322 [4], in bits. Value size6 means 6 bits, value size12 means 12 bits, value size18 means 18 bits. The value of sn-FieldLengthof an RLC entity for the DRB shall be changed only using reconfiguration with sync. The network configures only value size12 in SN-FieldLengthAM for SRB.SN-FieldLengthAM OPTIONAL, -- Cond Reestabt-PollRetransmitTimer for RLC AM in TS 38.322 [4], in milliseconds. Value ms5 means 5 ms, value ms10 means 10 ms and so on.T-PollRetransmit,pollPDUParameter for RLC AM in TS 38.322 [4]. Value p4 corresponds to 4 PDUs, value p8 corresponds to 8 PDUs and so on. infinity corresponds to an infinite number of PDUs.PollPDU,pollByteParameter for RLC AM in TS 38.322 [4]. Value kB25 corresponds to 25 kBytes, value kB50 corresponds to 50 kBytes and so on. infinity corresponds to an infinite amount of kBytes.PollByte,maxRetxThresholdParameter for RLC AM in TS 38.322 [4]. Value t1 corresponds to 1 retransmission, value t2 corresponds to 2 retransmissions and so on.ENUMERATED { t1, t2, t3, t4, t6, t8, t16, t32 } } DL-AM-RLC ::= SEQUENCE {sn-FieldLengthIndicates the RLC SN field size, see TS 38.322 [4], in bits. Value size6 means 6 bits, value size12 means 12 bits, value size18 means 18 bits. The value of sn-FieldLengthof an RLC entity for the DRB shall be changed only using reconfiguration with sync. The network configures only value size12 in SN-FieldLengthAM for SRB.SN-FieldLengthAM OPTIONAL, -- Cond Reestabt-ReassemblyTimer for reassembly in TS 38.322 [4], in milliseconds. Value ms0 means 0 ms, valuems5 means 5 ms and so on.T-Reassembly,t-StatusProhibitTimer for status reporting in TS 38.322 [4], in milliseconds. Value ms0 means 0 ms, value ms5 means 5 ms and so on. If t-StatusProhibit-v1610 is present, the UE shall ignoret-StatusProhibit (without suffix).T-StatusProhibit } UL-UM-RLC ::= SEQUENCE {sn-FieldLengthIndicates the RLC SN field size, see TS 38.322 [4], in bits. Value size6 means 6 bits, value size12 means 12 bits, value size18 means 18 bits. The value of sn-FieldLengthof an RLC entity for the DRB shall be changed only using reconfiguration with sync. The network configures only value size12 in SN-FieldLengthAM for SRB.SN-FieldLengthUM OPTIONAL -- Cond Reestab } DL-UM-RLC ::= SEQUENCE {sn-FieldLengthIndicates the RLC SN field size, see TS 38.322 [4], in bits. Value size6 means 6 bits, value size12 means 12 bits, value size18 means 18 bits. The value of sn-FieldLengthof an RLC entity for the DRB shall be changed only using reconfiguration with sync. The network configures only value size12 in SN-FieldLengthAM for SRB.SN-FieldLengthUM OPTIONAL, -- Cond Reestabt-ReassemblyTimer for reassembly in TS 38.322 [4], in milliseconds. Value ms0 means 0 ms, valuems5 means 5 ms and so on.T-Reassembly } T-PollRetransmit ::= ENUMERATED { ms5, ms10, ms15, ms20, ms25, ms30, ms35, ms40, ms45, ms50, ms55, ms60, ms65, ms70, ms75, ms80, ms85, ms90, ms95, ms100, ms105, ms110, ms115, ms120, ms125, ms130, ms135, ms140, ms145, ms150, ms155, ms160, ms165, ms170, ms175, ms180, ms185, ms190, ms195, ms200, ms205, ms210, ms215, ms220, ms225, ms230, ms235, ms240, ms245, ms250, ms300, ms350, ms400, ms450, ms500, ms800, ms1000, ms2000, ms4000, ms1-v1610, ms2-v1610, ms3-v1610, ms4-v1610, spare1} PollPDU ::= ENUMERATED { p4, p8, p16, p32, p64, p128, p256, p512, p1024, p2048, p4096, p6144, p8192, p12288, p16384,p20480, p24576, p28672, p32768, p40960, p49152, p57344, p65536, infinity, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} PollByte ::= ENUMERATED { kB1, kB2, kB5, kB8, kB10, kB15, kB25, kB50, kB75, kB100, kB125, kB250, kB375, kB500, kB750, kB1000, kB1250, kB1500, kB2000, kB3000, kB4000, kB4500, kB5000, kB5500, kB6000, kB6500, kB7000, kB7500, mB8, mB9, mB10, mB11, mB12, mB13, mB14, mB15, mB16, mB17, mB18, mB20, mB25, mB30, mB40, infinity, spare20, spare19, spare18, spare17, spare16, spare15, spare14, spare13, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} T-Reassembly ::= ENUMERATED { ms0, ms5, ms10, ms15, ms20, ms25, ms30, ms35, ms40, ms45, ms50, ms55, ms60, ms65, ms70, ms75, ms80, ms85, ms90, ms95, ms100, ms110, ms120, ms130, ms140, ms150, ms160, ms170, ms180, ms190, ms200, spare1} T-StatusProhibit ::= ENUMERATED { ms0, ms5, ms10, ms15, ms20, ms25, ms30, ms35, ms40, ms45, ms50, ms55, ms60, ms65, ms70, ms75, ms80, ms85, ms90, ms95, ms100, ms105, ms110, ms115, ms120, ms125, ms130, ms135, ms140, ms145, ms150, ms155, ms160, ms165, ms170, ms175, ms180, ms185, ms190, ms195, ms200, ms205, ms210, ms215, ms220, ms225, ms230, ms235, ms240, ms245, ms250, ms300, ms350, ms400, ms450, ms500, ms800, ms1000, ms1200, ms1600, ms2000, ms2400, spare2, spare1} SN-FieldLengthUM ::= ENUMERATED {size6, size12} SN-FieldLengthAM ::= ENUMERATED {size12, size18} RLC-Config-v1610 ::= SEQUENCE { dl-AM-RLC-v1610 DL-AM-RLC-v1610 } DL-AM-RLC-v1610 ::= SEQUENCE { t-StatusProhibit-v1610 T-StatusProhibit-v1610 OPTIONAL, -- Need R ... } T-StatusProhibit-v1610 ::= ENUMERATED { ms1, ms2, ms3, ms4, spare4, spare3, spare2, spare1} -- TAG-RLC-CONFIG-STOP -- ASN1STOP
RLC-Config field descriptions |
---|
maxRetxThreshold Parameter for RLC AM in TS 38.322 [4]. Value t1 corresponds to 1 retransmission, value t2 corresponds to 2 retransmissions and so on. |
pollByte Parameter for RLC AM in TS 38.322 [4]. Value kB25 corresponds to 25 kBytes, value kB50 corresponds to 50 kBytes and so on. infinity corresponds to an infinite amount of kBytes. |
pollPDU Parameter for RLC AM in TS 38.322 [4]. Value p4 corresponds to 4 PDUs, value p8 corresponds to 8 PDUs and so on. infinity corresponds to an infinite number of PDUs. |
sn-FieldLength Indicates the RLC SN field size, see TS 38.322 [4], in bits. Value size6 means 6 bits, value size12 means 12 bits, value size18 means 18 bits. The value of sn-FieldLengthof an RLC entity for the DRB shall be changed only using reconfiguration with sync. The network configures only value size12 in SN-FieldLengthAM for SRB. |
t-PollRetransmit Timer for RLC AM in TS 38.322 [4], in milliseconds. Value ms5 means 5 ms, value ms10 means 10 ms and so on. |
t-Reassembly Timer for reassembly in TS 38.322 [4], in milliseconds. Value ms0 means 0 ms, valuems5 means 5 ms and so on. |
t-StatusProhibit Timer for status reporting in TS 38.322 [4], in milliseconds. Value ms0 means 0 ms, value ms5 means 5 ms and so on. If t-StatusProhibit-v1610 is present, the UE shall ignoret-StatusProhibit (without suffix). |
Conditional Presence | Explanation |
---|---|
Reestab | The field is mandatory present at RLC bearer setup. It is optionally present, need M, at RLC re-establishment. Otherwise it is absent. Need M. |
The IE RLF-TimersAndConstants is used to configure UE specific timers and constants.
-- ASN1START -- TAG-RLF-TIMERSANDCONSTANTS-START RLF-TimersAndConstants ::= SEQUENCE { t310 ENUMERATED {ms0, ms50, ms100, ms200, ms500, ms1000, ms2000, ms4000, ms6000}, n310 ENUMERATED {n1, n2, n3, n4, n6, n8, n10, n20}, n311 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10}, ..., [[ t311 ENUMERATED {ms1000, ms3000, ms5000, ms10000, ms15000, ms20000, ms30000} ]] } -- TAG-RLF-TIMERSANDCONSTANTS-STOP -- ASN1STOP
RLF-TimersAndConstants field descriptions |
---|
n3xy Constants are described in clause 7.3. Value n1 corresponds to 1, value n2 corresponds to 2 and so on. |
t3xy Timers are described in clause 7.1. Value ms0 corresponds to 0 ms, value ms50 corresponds to 50 ms and so on. |
The IE RNTI-Value represents a Radio Network Temporary Identity.
The IE RSRP-Range specifies the value range used in RSRP measurements and thresholds. For measurements, integer value for RSRP measurements is according to Table 10.1.6.1-1 in TS 38.133 [14]. For thresholds, the actual value is (IE value – 156) dBm, except for the IE value 127, in which case the actual value is infinity.
The IE RSRQ-Range specifies the value range used in RSRQ measurements and thresholds. For measurements, integer value for RSRQ measurements is according to Table 10.1.11.1-1 in TS 38.133 [14]. For thresholds, the actual value is (IE value – 87) / 2 dB.
The IE RSSI-Range specifies the value range used in RSSI measurements and thresholds for NR operation with shared spectrum channel access. The integer value for RSSI measurements is according to Table 10.1.34.3-1 in TS 38.133 [14].
The IE SCellIndex concerns a short identity, used to identify an SCell. The value range is shared across the Cell Groups.
The IE SchedulingRequestConfig is used to configure the parameters, for the dedicated scheduling request (SR) resources.
-- ASN1START -- TAG-SCHEDULINGREQUESTCONFIG-START SchedulingRequestConfig ::= SEQUENCE {schedulingRequestToAddModListList of Scheduling Request configurations to add or modify.SEQUENCE (SIZE (1..maxNrofSR-ConfigPerCellGroup)) OF SchedulingRequestToAddMod OPTIONAL, -- Need NschedulingRequestToReleaseListList of Scheduling Request configurations to release.SEQUENCE (SIZE (1..maxNrofSR-ConfigPerCellGroup)) OF SchedulingRequestId OPTIONAL -- Need N } SchedulingRequestToAddMod ::= SEQUENCE {schedulingRequestIdUsed to modify a SR configuration and to indicate, in LogicalChannelConfig, the SR configuration to which a logical channel is mapped and to indicate, in SchedulingRequestresourceConfig, the SR configuration for which a scheduling request resource is used.SchedulingRequestId,sr-ProhibitTimerTimer for SR transmission on PUCCH in TS 38.321 [3]. Value is in ms. Value ms1 corresponds to 1ms, value ms2 corresponds to 2ms, and so on. When the field is absent, the UE applies the value 0.ENUMERATED {ms1, ms2, ms4, ms8, ms16, ms32, ms64, ms128} OPTIONAL, -- Need Ssr-TransMaxMaximum number of SR transmissions as described in TS 38.321 [3]. Value n4 corresponds to 4, value n8 corresponds to 8, and so on.ENUMERATED { n4, n8, n16, n32, n64, spare3, spare2, spare1} } -- TAG-SCHEDULINGREQUESTCONFIG-STOP -- ASN1STOP
SchedulingRequestConfig field descriptions |
---|
schedulingRequestToAddModList List of Scheduling Request configurations to add or modify. |
schedulingRequestToReleaseList List of Scheduling Request configurations to release. |
SchedulingRequestToAddMod field descriptions |
---|
schedulingRequestId Used to modify a SR configuration and to indicate, in LogicalChannelConfig, the SR configuration to which a logical channel is mapped and to indicate, in SchedulingRequestresourceConfig, the SR configuration for which a scheduling request resource is used. |
sr-ProhibitTimer Timer for SR transmission on PUCCH in TS 38.321 [3]. Value is in ms. Value ms1 corresponds to 1ms, value ms2 corresponds to 2ms, and so on. When the field is absent, the UE applies the value 0. |
sr-TransMax Maximum number of SR transmissions as described in TS 38.321 [3]. Value n4 corresponds to 4, value n8 corresponds to 8, and so on. |
The IE SchedulingRequestId is used to identify a Scheduling Request instance in the MAC layer.
The IE SchedulingRequestResourceConfig determines physical layer resources on PUCCH where the UE may send the dedicated scheduling request (D-SR) (see TS 38.213 [13], clause 9.2.4).
-- ASN1START -- TAG-SCHEDULINGREQUESTRESOURCECONFIG-START SchedulingRequestResourceConfig ::= SEQUENCE { schedulingRequestResourceId SchedulingRequestResourceId,schedulingRequestIDThe ID of the SchedulingRequestConfig that uses this scheduling request resource.SchedulingRequestId,periodicityAndOffsetSR periodicity and offset in number of symbols or slots (see TS 38.213 [13], clause 9.2.4) The following periodicities may be configured depending on the chosen subcarrier spacing: SCS = 15 kHz: 2sym, 7sym, 1sl, 2sl, 4sl, 5sl, 8sl, 10sl, 16sl, 20sl, 40sl, 80sl SCS = 30 kHz: 2sym, 7sym, 1sl, 2sl, 4sl, 8sl, 10sl, 16sl, 20sl, 40sl, 80sl, 160sl SCS = 60 kHz: 2sym, 7sym/6sym, 1sl, 2sl, 4sl, 8sl, 16sl, 20sl, 40sl, 80sl, 160sl, 320sl SCS = 120 kHz: 2sym, 7sym, 1sl, 2sl, 4sl, 8sl, 16sl, 40sl, 80sl, 160sl, 320sl, 640sl sym6or7 corresponds to 6 symbols if extended cyclic prefix and a SCS of 60 kHz are configured, otherwise it corresponds to 7 symbols. For periodicities 2sym, 7sym and sl1 the UE assumes an offset of 0 slots.CHOICE { sym2 NULL, sym6or7 NULL, sl1 NULL, -- Recurs in every slot sl2 INTEGER (0..1), sl4 INTEGER (0..3), sl5 INTEGER (0..4), sl8 INTEGER (0..7), sl10 INTEGER (0..9), sl16 INTEGER (0..15), sl20 INTEGER (0..19), sl40 INTEGER (0..39), sl80 INTEGER (0..79), sl160 INTEGER (0..159), sl320 INTEGER (0..319), sl640 INTEGER (0..639) } OPTIONAL, -- Need MresourceID of the PUCCH resource in which the UE shall send the scheduling request. The actual PUCCH-Resource is configured in PUCCH-Config of the same UL BWP and serving cell as this SchedulingRequestResourceConfig. The network configures a PUCCH-Resource of PUCCH-format0 or PUCCH-format1 (other formats not supported) (see TS 38.213 [13], clause 9.2.4)PUCCH-ResourceId OPTIONAL -- Need M } SchedulingRequestResourceConfigExt-v1610 ::= SEQUENCE {phy-PriorityIndex-r16Indicates whether this scheduling request resource is high or low priority in PHY prioritization/multiplexing handling (see TS 38.213 [13], clause 9.2.4). Value p0 indicates low priority and value p1 indicates high priority.ENUMERATED {p0, p1} OPTIONAL, -- Need M ... } -- TAG-SCHEDULINGREQUESTRESOURCECONFIG-STOP -- ASN1STOP
SchedulingRequestResourceConfig field descriptions |
---|
periodicityAndOffset SR periodicity and offset in number of symbols or slots (see TS 38.213 [13], clause 9.2.4) The following periodicities may be configured depending on the chosen subcarrier spacing: SCS = 15 kHz: 2sym, 7sym, 1sl, 2sl, 4sl, 5sl, 8sl, 10sl, 16sl, 20sl, 40sl, 80sl SCS = 30 kHz: 2sym, 7sym, 1sl, 2sl, 4sl, 8sl, 10sl, 16sl, 20sl, 40sl, 80sl, 160sl SCS = 60 kHz: 2sym, 7sym/6sym, 1sl, 2sl, 4sl, 8sl, 16sl, 20sl, 40sl, 80sl, 160sl, 320sl SCS = 120 kHz: 2sym, 7sym, 1sl, 2sl, 4sl, 8sl, 16sl, 40sl, 80sl, 160sl, 320sl, 640sl sym6or7 corresponds to 6 symbols if extended cyclic prefix and a SCS of 60 kHz are configured, otherwise it corresponds to 7 symbols. For periodicities 2sym, 7sym and sl1 the UE assumes an offset of 0 slots. |
phy-PriorityIndex Indicates whether this scheduling request resource is high or low priority in PHY prioritization/multiplexing handling (see TS 38.213 [13], clause 9.2.4). Value p0 indicates low priority and value p1 indicates high priority. |
resource ID of the PUCCH resource in which the UE shall send the scheduling request. The actual PUCCH-Resource is configured in PUCCH-Config of the same UL BWP and serving cell as this SchedulingRequestResourceConfig. The network configures a PUCCH-Resource of PUCCH-format0 or PUCCH-format1 (other formats not supported) (see TS 38.213 [13], clause 9.2.4) |
schedulingRequestID The ID of the SchedulingRequestConfig that uses this scheduling request resource. |
The IE SchedulingRequestResourceId is used to identify scheduling request resources on PUCCH.
The IE ScramblingID is used for scrambling channels and reference signals.
The IE SCS-SpecificCarrier provides parameters determining the location and width of the actual carrier or the carrier bandwidth. It is defined specifically for a numerology (subcarrier spacing (SCS)) and in relation (frequency offset) to Point A.
-- ASN1START -- TAG-SCS-SPECIFICCARRIER-START SCS-SpecificCarrier ::= SEQUENCE { offsetToCarrier INTEGER (0..2199), subcarrierSpacing SubcarrierSpacing, carrierBandwidth INTEGER (1..maxNrofPhysicalResourceBlocks), ..., [[ txDirectCurrentLocation INTEGER (0..4095) OPTIONAL -- Need S ]] } -- TAG-SCS-SPECIFICCARRIER-STOP -- ASN1STOP
The IE SDAP-Config is used to set the configurable SDAP parameters for a data radio bearer. All configured instances of SDAP-Config with the same value of pdu-Session correspond to the same SDAP entity as specified in TS 37.324 [24].
-- ASN1START -- TAG-SDAP-CONFIG-START SDAP-Config ::= SEQUENCE {pdu-SessionIdentity of the PDU session whose QoS flows are mapped to the DRB.PDU-SessionID,sdap-HeaderDLIndicates whether or not a SDAP header is present for DL data on this DRB. The field cannot be changed after a DRB is established.ENUMERATED {present, absent},sdap-HeaderULIndicates whether or not a SDAP header is present for UL data on this DRB. The field cannot be changed after a DRB is established.The network sets this field to present if the field defaultDRB is set to true.ENUMERATED {present, absent},defaultDRBIndicates whether or not this is the default DRB for this PDU session. Among all configured instances of SDAP-Config with the same value of pdu-Session, this field shall be set to true in at most one instance of SDAP-Config and to false in all other instances.BOOLEAN,mappedQoS-FlowsToAddIndicates the list of QFIs of UL QoS flows of the PDU session to be additionally mapped to this DRB. A QFI value can be included at most once in all configured instances of SDAP-Config with the same value of pdu-Session. For QoS flow remapping, the QFI value of the remapped QoS flow is only included in mappedQoS-FlowsToAdd in sdap-Config corresponding to the new DRB and not included in mappedQoS-FlowsToRelease in sdap-Config corresponding to the old DRB.SEQUENCE (SIZE (1..maxNrofQFIs)) OF QFI OPTIONAL, -- Need NmappedQoS-FlowsToReleaseIndicates the list of QFIs of QoS flows of the PDU session to be released from existing QoS flow to DRB mapping of this DRB.SEQUENCE (SIZE (1..maxNrofQFIs)) OF QFI OPTIONAL, -- Need N ... } QFI ::= INTEGER (0..maxQFI) PDU-SessionID ::= INTEGER (0..255) -- TAG-SDAP-CONFIG-STOP -- ASN1STOP
SCS-SpecificCarrier field descriptions |
---|
carrierBandwidth Width of this carrier in number of PRBs (using the subcarrierSpacing defined for this carrier) (see TS 38.211 [16], clause 4.4.2). |
offsetToCarrier Offset in frequency domain between Point A (lowest subcarrier of common RB 0) and the lowest usable subcarrier on this carrier in number of PRBs (using the subcarrierSpacing defined for this carrier). The maximum value corresponds to 275*8-1. See TS 38.211 [16], clause 4.4.2. |
txDirectCurrentLocation Indicates the downlink Tx Direct Current location for the carrier. A value in the range 0..3299 indicates the subcarrier index within the carrier. The values in the value range 3301..4095 are reserved and ignored by the UE. If this field is absent for downlink within ServingCellConfigCommon and ServingCellConfigCommonSIB, the UE assumes the default value of 3300 (i.e. "Outside the carrier"). (see TS 38.211 [16], clause 4.4.2). Network does not configure this field via ServingCellConfig or for uplink carriers. |
subcarrierSpacing Subcarrier spacing of this carrier. It is used to convert the offsetToCarrier into an actual frequency. Only the values 15 kHz, 30 kHz or 60 kHz (FR1), and 60 kHz or 120 kHz (FR2) are applicable. |
SDAP-Config field descriptions |
---|
defaultDRB Indicates whether or not this is the default DRB for this PDU session. Among all configured instances of SDAP-Config with the same value of pdu-Session, this field shall be set to true in at most one instance of SDAP-Config and to false in all other instances. |
mappedQoS-FlowsToAdd Indicates the list of QFIs of UL QoS flows of the PDU session to be additionally mapped to this DRB. A QFI value can be included at most once in all configured instances of SDAP-Config with the same value of pdu-Session. For QoS flow remapping, the QFI value of the remapped QoS flow is only included in mappedQoS-FlowsToAdd in sdap-Config corresponding to the new DRB and not included in mappedQoS-FlowsToRelease in sdap-Config corresponding to the old DRB. |
mappedQoS-FlowsToRelease Indicates the list of QFIs of QoS flows of the PDU session to be released from existing QoS flow to DRB mapping of this DRB. |
pdu-Session Identity of the PDU session whose QoS flows are mapped to the DRB. |
sdap-HeaderUL Indicates whether or not a SDAP header is present for UL data on this DRB. The field cannot be changed after a DRB is established.The network sets this field to present if the field defaultDRB is set to true. |
sdap-HeaderDL Indicates whether or not a SDAP header is present for DL data on this DRB. The field cannot be changed after a DRB is established. |
The IE SearchSpace defines how/where to search for PDCCH candidates. Each search space is associated with one ControlResourceSet. For a scheduled cell in the case of cross carrier scheduling, except for nrofCandidates, all the optional fields are absent (regardless of their presence conditions).
-- ASN1START -- TAG-SEARCHSPACE-START SearchSpace ::= SEQUENCE {searchSpaceIdIdentity of the search space. SearchSpaceId = 0 identifies the searchSpaceZero configured via PBCH (MIB) or ServingCellConfigCommon and may hence not be used in the SearchSpace IE. The searchSpaceId is unique among the BWPs of a Serving Cell. In case of cross carrier scheduling, search spaces with the same searchSpaceId in scheduled cell and scheduling cell are linked to each other. The UE applies the search space for the scheduled cell only if the DL BWPs in which the linked search spaces are configured in scheduling cell and scheduled cell are both active. For an IAB-MT, the search space defines how/where to search for PDCCH candidates for an IAB-MT. Each search space is associated with one ControlResearchSet. For a scheduled cell in the case of cross carrier scheduling, except for nrofCandidates, all the optional fields are absent.SearchSpaceId,controlResourceSetIdThe CORESET applicable for this SearchSpace. Value 0 identifies the common CORESET#0 configured in MIB and in ServingCellConfigCommon. Values 1..maxNrofControlResourceSets-1 identify CORESETs configured in System Information or by dedicated signalling. The CORESETs with non-zero controlResourceSetIdare configured in the same BWP as this SearchSpace. If the field controlResourceSetId-r16 is present, UE shall ignore the controlResourceSetId (without suffix).ControlResourceSetId OPTIONAL, -- Cond SetupOnlymonitoringSlotPeriodicityAndOffsetSlots for PDCCH Monitoring configured as periodicity and offset. If the UE is configured to monitor DCI format 2_1, only the values 'sl1', 'sl2' or 'sl4' are applicable. If the UE is configured to monitor DCI format 2_0, only the values ′sl1′, ′sl2′, ′sl4′, ′sl5′, ′sl8′, ′sl10′, ′sl16′, and ′sl20′ are applicable (see TS 38.213 [13], clause 10). If the UE is configured to monitor DCI format 2_4, only the values 'sl1', 'sl2', 'sl4', 'sl5', 'sl8' and 'sl10' are applicable. For IAB-MT,If the IAB-MT is configured to monitor DCI format 2_1, only the values 'sl1', 'sl2' or 'sl4' are applicable. If the IAB-MT is configured to monitor DCI format 2_0 or DCI format 2_5, only the values ′sl1′, ′sl2′, ′sl4′, ′sl5′, ′sl8′, ′sl10′, ′sl16′, and ′sl20′ are applicable (see TS 38.213, clause 10).CHOICE { sl1 NULL, sl2 INTEGER (0..1), sl4 INTEGER (0..3), sl5 INTEGER (0..4), sl8 INTEGER (0..7), sl10 INTEGER (0..9), sl16 INTEGER (0..15), sl20 INTEGER (0..19), sl40 INTEGER (0..39), sl80 INTEGER (0..79), sl160 INTEGER (0..159), sl320 INTEGER (0..319), sl640 INTEGER (0..639), sl1280 INTEGER (0..1279), sl2560 INTEGER (0..2559) } OPTIONAL, -- Cond SetupdurationNumber of consecutive slots that a SearchSpace lasts in every occasion, i.e., upon every period as given in the periodicityAndOffset. If the field is absent, the UE applies the value 1 slot, except for DCI format 2_0. The UE ignores this field for DCI format 2_0. The maximum valid duration is periodicity-1 (periodicity as given in the monitoringSlotPeriodicityAndOffset). For IAB-MT, duration indicates number of consecutive slots that a SearchSpace lasts in every occasion, i.e., upon every period as given in the periodicityAndOffset. If the field is absent, the IAB-MT applies the value 1 slot, except for DCI format 2_0 and DCI format 2_5. The IAB-MT ignores this field for DCI format 2_0 and DCI format 2_5. The maximum valid duration is periodicity-1 (periodicity as given in the monitoringSlotPeriodicityAndOffset).INTEGER (2..2559) OPTIONAL, -- Need SmonitoringSymbolsWithinSlotThe first symbol(s) for PDCCH monitoring in the slots configured for PDCCH monitoring (see monitoringSlotPeriodicityAndOffset and duration). The most significant (left) bit represents the first OFDM in a slot, and the second most significant (left) bit represents the second OFDM symbol in a slot and so on. The bit(s) set to one identify the first OFDM symbol(s) of the control resource set within a slot. If the cyclic prefix of the BWP is set to extended CP, the last two bits within the bit string shall be ignored by the UE or IAB-MT. For DCI format 2_0, the first one symbol applies if the duration of CORESET (in the IE ControlResourceSet) identified by controlResourceSetId indicates 3 symbols, the first two symbols apply if the duration of CORESET identified by controlResourceSetId indicates 2 symbols, and the first three symbols apply if the duration of CORESET identified by controlResourceSetId indicates 1 symbol. See TS 38.213 [13], clause 10. For IAB-MT: For DCI format 2_0 or DCI format 2_5, the first one symbol applies if the duration of CORESET (in the IE ControlResourceSet) identified by controlResourceSetId indicates 3 symbols, the first two symbols apply if the duration of CORESET identified by controlResourceSetId indicates 2 symbols, and the first three symbols apply if the duration of CORESET identified by controlResourceSetId indicates 1 symbol. See TS 38.213 [13], clause 10.BIT STRING (SIZE (14)) OPTIONAL, -- Cond SetupnrofCandidatesNumber of PDCCH candidates per aggregation level. The number of candidates and aggregation levels configured here applies to all formats unless a particular value is specified or a format-specific value is provided (see inside searchSpaceType). If configured in the SearchSpace of a cross carrier scheduled cell, this field determines the number of candidates and aggregation levels to be used on the linked scheduling cell (see TS 38.213 [13], clause 10).SEQUENCE { aggregationLevel1 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8}, aggregationLevel2 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8}, aggregationLevel4 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8}, aggregationLevel8 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8}, aggregationLevel16 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8} } OPTIONAL, -- Cond SetupsearchSpaceTypeIndicates whether this is a common search space (present) or a UE specific search space as well as DCI formats to monitor for.CHOICE {commonConfigures this search space as common search space (CSS) and DCI formats to monitor.SEQUENCE {dci-Format0-0-AndFormat1-0If configured, the UE monitors the DCI formats 0_0 and 1_0 according to TS 38.213 [13], clause 10.1.SEQUENCE { ... } OPTIONAL, -- Need Rdci-Format2-0If configured, UE monitors the DCI format 2_0 according to TS 38.213 [13], clause 10.1, 11.1.1.SEQUENCE {nrofCandidates-SFIThe number of PDCCH candidates specifically for format 2-0 for the configured aggregation level. If an aggregation level is absent, the UE does not search for any candidates with that aggregation level. The network configures only one aggregationLevel and the corresponding number of candidates (see TS 38.213 [13], clause 11.1.1). For a search space configured with freqMonitorLocations-r16, only value ′n1′ is valid.SEQUENCE { aggregationLevel1 ENUMERATED {n1, n2} OPTIONAL, -- Need R aggregationLevel2 ENUMERATED {n1, n2} OPTIONAL, -- Need R aggregationLevel4 ENUMERATED {n1, n2} OPTIONAL, -- Need R aggregationLevel8 ENUMERATED {n1, n2} OPTIONAL, -- Need R aggregationLevel16 ENUMERATED {n1, n2} OPTIONAL -- Need R }, ... } OPTIONAL, -- Need Rdci-Format2-1If configured, UE monitors the DCI format 2_1 according to TS 38.213 [13], clause 10.1, 11.2.SEQUENCE { ... } OPTIONAL, -- Need Rdci-Format2-2If configured, UE monitors the DCI format 2_2 according to TS 38.213 [13], clause 10.1, 11.3.SEQUENCE { ... } OPTIONAL, -- Need Rdci-Format2-3If configured, UE monitors the DCI format 2_3 according to TS 38.213 [13], clause 10.1, 11.4SEQUENCE { dummy1 ENUMERATED {sl1, sl2, sl4, sl5, sl8, sl10, sl16, sl20} OPTIONAL, -- Cond Setup dummy2 ENUMERATED {n1, n2}, ... } OPTIONAL -- Need R },ue-SpecificConfigures this search space as UE specific search space (USS). The UE monitors the DCI format with CRC scrambled by C-RNTI, CS-RNTI (if configured), and SP-CSI-RNTI (if configured)SEQUENCE {dci-FormatsIndicates whether the UE monitors in this USS for DCI formats 0-0 and 1-0 or for formats 0-1 and 1-1.ENUMERATED {formats0-0-And-1-0, formats0-1-And-1-1}, ..., [[dci-Formats-MT-r16Indicates whether the IAB-MT monitors the DCI formats 2-5 according to TS 38.213 [13], clause 14.ENUMERATED {formats2-5} OPTIONAL, -- Need Rdci-FormatsSL-r16Indicates whether the UE monitors in this USS for DCI formats 0-0 and 1-0 or for formats 0-1 and 1-1 or for format 3-0 or for format 3-1 or for formats 3-0 and 3-1. If this field is present, the field dci-Formats is ignored and dci-FormatsSL is used.ENUMERATED {formats0-0-And-1-0, formats0-1-And-1-1, formats3-0, formats3-1, formats3-0-And-3-1} OPTIONAL, -- Need Rdci-FormatsExt-r16If this field is present, the field dci-Formats is ignored and dci-FormatsExt is used instead to indicate whether the UE monitors in this USS for DCI format 0_2 and 1_2 or formats 0_1 and 1_1 and 0_2 and 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 10.1). This field is not configured for operation with shared spectrum channel access in this release.ENUMERATED {formats0-2-And-1-2, formats0-1-And-1-1And-0-2-And-1-2} OPTIONAL -- Need R ]] } } OPTIONAL -- Cond Setup2 } SearchSpaceExt-r16 ::= SEQUENCE {controlResourceSetId-r16The CORESET applicable for this SearchSpace. Value 0 identifies the common CORESET#0 configured in MIB and in ServingCellConfigCommon. Values 1..maxNrofControlResourceSets-1 identify CORESETs configured in System Information or by dedicated signalling. The CORESETs with non-zero controlResourceSetIdare configured in the same BWP as this SearchSpace. If the field controlResourceSetId-r16 is present, UE shall ignore the controlResourceSetId (without suffix).ControlResourceSetId-r16 OPTIONAL, -- Cond SetupOnly2searchSpaceType-r16Indicates whether this is a common search space (present) or a UE specific search space as well as DCI formats to monitor for.SEQUENCE {common-r16Configures this search space as common search space (CSS) and DCI formats to monitor.SEQUENCE {dci-Format2-4-r16If configured, UE monitors the DCI format 2_4 according to TS 38.213 [13], clause 11.2A.SEQUENCE {nrofCandidates-CI-r16The number of PDCCH candidates specifically for format 2-4 for the configured aggregation level. If an aggregation level is absent, the UE does not search for any candidates with that aggregation level. The network configures only one aggregationLevel and the corresponding number of candidates (see TS 38.213 [13], clause 10.1).SEQUENCE { aggregationLevel1-r16 ENUMERATED {n1, n2} OPTIONAL, -- Need R aggregationLevel2-r16 ENUMERATED {n1, n2} OPTIONAL, -- Need R aggregationLevel4-r16 ENUMERATED {n1, n2} OPTIONAL, -- Need R aggregationLevel8-r16 ENUMERATED {n1, n2} OPTIONAL, -- Need R aggregationLevel16-r16 ENUMERATED {n1, n2} OPTIONAL -- Need R }, ... } OPTIONAL, -- Need Rdci-Format2-5-r16If configured, IAB-MT monitors the DCI format 2_5 according to TS 38.213 [13], clause 14.SEQUENCE { nrofCandidates-IAB-r16 SEQUENCE { aggregationLevel1-r16 ENUMERATED {n1, n2} OPTIONAL, -- Need R aggregationLevel2-r16 ENUMERATED {n1, n2} OPTIONAL, -- Need R aggregationLevel4-r16 ENUMERATED {n1, n2} OPTIONAL, -- Need R aggregationLevel8-r16 ENUMERATED {n1, n2} OPTIONAL, -- Need R aggregationLevel16-r16 ENUMERATED {n1, n2} OPTIONAL -- Need R }, ... } OPTIONAL, -- Need Rdci-Format2-6-r16If configured, UE monitors the DCI format 2_6 according to TS 38.213 [13], clause 10.1, 10.3. DCI format 2_6 can only be configured on the SpCell.SEQUENCE { ... } OPTIONAL, -- Need R ... } } OPTIONAL, -- Cond Setup3searchSpaceGroupIdList-r16List of search space group IDs which the search space is associated with. The network configures at most 2 search space groups per BWP where the group ID is either 0 or 1.SEQUENCE (SIZE (1.. 2)) OF INTEGER (0..1) OPTIONAL, -- Need RfreqMonitorLocations-r16Defines an association of the search space to multiple monitoring locations in the frequency domain and indicates whether the pattern configured in the associated CORESET is replicated to a specific RB set, see TS 38.213, clause 10.1. Each bit in the bitmap corresponds to one RB set, and the leftmost (most significant) bit corresponds to RB set 0 in the BWP. A bit set to 1 indicates that a frequency domain resource allocation replicated from the pattern configured in the associated CORESET is mapped to the RB set.BIT STRING (SIZE (5)) OPTIONAL -- Need R } -- TAG-SEARCHSPACE-STOP -- ASN1STOP
SearchSpace field descriptions |
---|
common Configures this search space as common search space (CSS) and DCI formats to monitor. |
controlResourceSetId The CORESET applicable for this SearchSpace. Value 0 identifies the common CORESET#0 configured in MIB and in ServingCellConfigCommon. Values 1..maxNrofControlResourceSets-1 identify CORESETs configured in System Information or by dedicated signalling. The CORESETs with non-zero controlResourceSetIdare configured in the same BWP as this SearchSpace. If the field controlResourceSetId-r16 is present, UE shall ignore the controlResourceSetId (without suffix). |
dummy1, dummy2 This field is not used in the specification. If received it shall be ignored by the UE. |
dci-Format0-0-AndFormat1-0 If configured, the UE monitors the DCI formats 0_0 and 1_0 according to TS 38.213 [13], clause 10.1. |
dci-Format2-0 If configured, UE monitors the DCI format 2_0 according to TS 38.213 [13], clause 10.1, 11.1.1. |
dci-Format2-1 If configured, UE monitors the DCI format 2_1 according to TS 38.213 [13], clause 10.1, 11.2. |
dci-Format2-2 If configured, UE monitors the DCI format 2_2 according to TS 38.213 [13], clause 10.1, 11.3. |
dci-Format2-3 If configured, UE monitors the DCI format 2_3 according to TS 38.213 [13], clause 10.1, 11.4 |
dci-Format2-4 If configured, UE monitors the DCI format 2_4 according to TS 38.213 [13], clause 11.2A. |
dci-Format2-5 If configured, IAB-MT monitors the DCI format 2_5 according to TS 38.213 [13], clause 14. |
dci-Format2-6 If configured, UE monitors the DCI format 2_6 according to TS 38.213 [13], clause 10.1, 10.3. DCI format 2_6 can only be configured on the SpCell. |
dci-Formats Indicates whether the UE monitors in this USS for DCI formats 0-0 and 1-0 or for formats 0-1 and 1-1. |
dci-FormatsExt If this field is present, the field dci-Formats is ignored and dci-FormatsExt is used instead to indicate whether the UE monitors in this USS for DCI format 0_2 and 1_2 or formats 0_1 and 1_1 and 0_2 and 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 10.1). This field is not configured for operation with shared spectrum channel access in this release. |
dci-Formats-MT Indicates whether the IAB-MT monitors the DCI formats 2-5 according to TS 38.213 [13], clause 14. |
dci-FormatsSL Indicates whether the UE monitors in this USS for DCI formats 0-0 and 1-0 or for formats 0-1 and 1-1 or for format 3-0 or for format 3-1 or for formats 3-0 and 3-1. If this field is present, the field dci-Formats is ignored and dci-FormatsSL is used. |
duration Number of consecutive slots that a SearchSpace lasts in every occasion, i.e., upon every period as given in the periodicityAndOffset. If the field is absent, the UE applies the value 1 slot, except for DCI format 2_0. The UE ignores this field for DCI format 2_0. The maximum valid duration is periodicity-1 (periodicity as given in the monitoringSlotPeriodicityAndOffset). For IAB-MT, duration indicates number of consecutive slots that a SearchSpace lasts in every occasion, i.e., upon every period as given in the periodicityAndOffset. If the field is absent, the IAB-MT applies the value 1 slot, except for DCI format 2_0 and DCI format 2_5. The IAB-MT ignores this field for DCI format 2_0 and DCI format 2_5. The maximum valid duration is periodicity-1 (periodicity as given in the monitoringSlotPeriodicityAndOffset). |
freqMonitorLocations Defines an association of the search space to multiple monitoring locations in the frequency domain and indicates whether the pattern configured in the associated CORESET is replicated to a specific RB set, see TS 38.213, clause 10.1. Each bit in the bitmap corresponds to one RB set, and the leftmost (most significant) bit corresponds to RB set 0 in the BWP. A bit set to 1 indicates that a frequency domain resource allocation replicated from the pattern configured in the associated CORESET is mapped to the RB set. |
monitoringSlotPeriodicityAndOffset Slots for PDCCH Monitoring configured as periodicity and offset. If the UE is configured to monitor DCI format 2_1, only the values 'sl1', 'sl2' or 'sl4' are applicable. If the UE is configured to monitor DCI format 2_0, only the values ′sl1′, ′sl2′, ′sl4′, ′sl5′, ′sl8′, ′sl10′, ′sl16′, and ′sl20′ are applicable (see TS 38.213 [13], clause 10). If the UE is configured to monitor DCI format 2_4, only the values 'sl1', 'sl2', 'sl4', 'sl5', 'sl8' and 'sl10' are applicable. For IAB-MT,If the IAB-MT is configured to monitor DCI format 2_1, only the values 'sl1', 'sl2' or 'sl4' are applicable. If the IAB-MT is configured to monitor DCI format 2_0 or DCI format 2_5, only the values ′sl1′, ′sl2′, ′sl4′, ′sl5′, ′sl8′, ′sl10′, ′sl16′, and ′sl20′ are applicable (see TS 38.213, clause 10). |
monitoringSymbolsWithinSlot The first symbol(s) for PDCCH monitoring in the slots configured for PDCCH monitoring (see monitoringSlotPeriodicityAndOffset and duration). The most significant (left) bit represents the first OFDM in a slot, and the second most significant (left) bit represents the second OFDM symbol in a slot and so on. The bit(s) set to one identify the first OFDM symbol(s) of the control resource set within a slot. If the cyclic prefix of the BWP is set to extended CP, the last two bits within the bit string shall be ignored by the UE or IAB-MT. For DCI format 2_0, the first one symbol applies if the duration of CORESET (in the IE ControlResourceSet) identified by controlResourceSetId indicates 3 symbols, the first two symbols apply if the duration of CORESET identified by controlResourceSetId indicates 2 symbols, and the first three symbols apply if the duration of CORESET identified by controlResourceSetId indicates 1 symbol. See TS 38.213 [13], clause 10. For IAB-MT: For DCI format 2_0 or DCI format 2_5, the first one symbol applies if the duration of CORESET (in the IE ControlResourceSet) identified by controlResourceSetId indicates 3 symbols, the first two symbols apply if the duration of CORESET identified by controlResourceSetId indicates 2 symbols, and the first three symbols apply if the duration of CORESET identified by controlResourceSetId indicates 1 symbol. See TS 38.213 [13], clause 10. |
nrofCandidates-CI The number of PDCCH candidates specifically for format 2-4 for the configured aggregation level. If an aggregation level is absent, the UE does not search for any candidates with that aggregation level. The network configures only one aggregationLevel and the corresponding number of candidates (see TS 38.213 [13], clause 10.1). |
nrofCandidates-SFI The number of PDCCH candidates specifically for format 2-0 for the configured aggregation level. If an aggregation level is absent, the UE does not search for any candidates with that aggregation level. The network configures only one aggregationLevel and the corresponding number of candidates (see TS 38.213 [13], clause 11.1.1). For a search space configured with freqMonitorLocations-r16, only value ′n1′ is valid. |
nrofCandidates Number of PDCCH candidates per aggregation level. The number of candidates and aggregation levels configured here applies to all formats unless a particular value is specified or a format-specific value is provided (see inside searchSpaceType). If configured in the SearchSpace of a cross carrier scheduled cell, this field determines the number of candidates and aggregation levels to be used on the linked scheduling cell (see TS 38.213 [13], clause 10). |
searchSpaceGroupIdList List of search space group IDs which the search space is associated with. The network configures at most 2 search space groups per BWP where the group ID is either 0 or 1. |
searchSpaceId Identity of the search space. SearchSpaceId = 0 identifies the searchSpaceZero configured via PBCH (MIB) or ServingCellConfigCommon and may hence not be used in the SearchSpace IE. The searchSpaceId is unique among the BWPs of a Serving Cell. In case of cross carrier scheduling, search spaces with the same searchSpaceId in scheduled cell and scheduling cell are linked to each other. The UE applies the search space for the scheduled cell only if the DL BWPs in which the linked search spaces are configured in scheduling cell and scheduled cell are both active. For an IAB-MT, the search space defines how/where to search for PDCCH candidates for an IAB-MT. Each search space is associated with one ControlResearchSet. For a scheduled cell in the case of cross carrier scheduling, except for nrofCandidates, all the optional fields are absent. |
searchSpaceType Indicates whether this is a common search space (present) or a UE specific search space as well as DCI formats to monitor for. |
ue-Specific Configures this search space as UE specific search space (USS). The UE monitors the DCI format with CRC scrambled by C-RNTI, CS-RNTI (if configured), and SP-CSI-RNTI (if configured) |
Conditional Presence | Explanation |
---|---|
Setup | This field is mandatory present upon creation of a new SearchSpace. It is optionally present, Need M, otherwise. |
Setup2 | This field is mandatory present when a new SearchSpace is set up, if the same SearchSpace ID is not included in searchSpacesToAddModListExt-r16 of the parent IE with the field searchSpaceType-r16 included. Otherwise it is optionally present, Need M. |
Setup3 | This field is mandatory present when a new SearchSpace is set up, if the same SearchSpace ID is not included in searchSpacesToAddModListExt (without suffix) of the parent IE with the field searchSpaceType (without suffix) included. Otherwise it is optionally present, Need M. |
SetupOnly | This field is mandatory present upon creation of a new SearchSpace. It is absent, Need M, otherwise. |
SetupOnly2 | In PDCCH-Config, the field is optionally present upon creation of a new SearchSpace and absent, Need M upon reconfiguration of an existing SearchSpace. In PDCCH-ConfigCommon, the field is absent. |
The IE SearchSpaceId is used to identify Search Spaces. The ID space is used across the BWPs of a Serving Cell. The search space with the SearchSpaceId = 0 identifies the search space configured via PBCH (MIB) and in ServingCellConfigCommon (searchSpaceZero). The number of Search Spaces per BWP is limited to 10 including the common and UE specific Search Spaces.
The IE SearchSpaceZero is used to configure SearchSpace#0 of the initial BWP (see TS 38.213 [13], clause 13).
The IE SecurityAlgorithmConfig is used to configure AS integrity protection algorithm and AS ciphering algorithm for SRBs and DRBs.
-- ASN1START -- TAG-SECURITYALGORITHMCONFIG-START SecurityAlgorithmConfig ::= SEQUENCE { cipheringAlgorithm CipheringAlgorithm, integrityProtAlgorithm IntegrityProtAlgorithm OPTIONAL, -- Need R ... } IntegrityProtAlgorithm ::= ENUMERATED { nia0, nia1, nia2, nia3, spare4, spare3, spare2, spare1, ...} CipheringAlgorithm ::= ENUMERATED { nea0, nea1, nea2, nea3, spare4, spare3, spare2, spare1, ...} -- TAG-SECURITYALGORITHMCONFIG-STOP -- ASN1STOP
The IE SemiStaticChannelAccessConfig is used to configure channel access parameters when the network is operating in semi-static channel access mode (see clause 4.3 in TS 37.213 [48].
SecurityAlgorithmConfig field descriptions |
---|
cipheringAlgorithm Indicates the ciphering algorithm to be used for SRBs and DRBs, as specified in TS 33.501 [11]. The algorithms nea0-nea3 are identical to the LTE algorithms eea0-3. The algorithms configured for all bearers using master key shall be the same, and the algorithms configured for all bearers using secondary key, if any, shall be the same. If UE is connected to E-UTRA/EPC, this field indicates the ciphering algorithm to be used for RBs configured with NR PDCP, as specified in TS 33.501 [11]. |
integrityProtAlgorithm Indicates the integrity protection algorithm to be used for SRBs and DRBs, as specified in TS 33.501 [11]. The algorithms nia0-nia3 are identical to the E-UTRA algorithms eia0-3. The algorithms configured for all bearers using master key shall be the same and the algorithms configured for all bearers using secondary key, if any, shall be the same.The network does not configure nia0 except for unauthenticated emergency sessions for unauthenticated UEs in LSM (limited service mode). If UE is connected to E-UTRA/EPC, this field indicates the integrity protection algorithm to be used for SRBs configured with NR PDCP, as specified in TS 33.501 [11]. The network does not configure nia0 for SRB3. |
The IE Sensor-LocationInfo is used by the UE to provide sensor information.
-- ASN1START -- TAG-SENSORLOCATIONINFO-START Sensor-LocationInfo-r16 ::= SEQUENCE {sensor-MeasurementInformation-r16This field provides barometric pressure measurements as Sensor-MeasurementInformationdefined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit.OCTET STRING OPTIONAL,sensor-MotionInformation-r16This field provides motion sensor measurements as Sensor-MotionInformationdefined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit.OCTET STRING OPTIONAL, ... } -- TAG-SENSORLOCATIONINFO-STOP -- ASN1STOP
SemiStaticChannelAccessConfig field descriptions |
---|
period Indicates the periodicity of the semi-static channel access mode (see TS 37.213 [48], clause 4.3). Value ms1 corresponds to 1 ms, value ms2 corresponds to 2 ms, value ms2dot5 corresponds to 2.5 ms, and so on. |
Sensor-LocationInfofield descriptions |
---|
sensor-MeasurementInformation This field provides barometric pressure measurements as Sensor-MeasurementInformationdefined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit. |
sensor-MotionInformation This field provides motion sensor measurements as Sensor-MotionInformationdefined in TS 37.355 [49]. The first/leftmost bit of the first octet contains the most significant bit. |
The IE ServCellIndex concerns a short identity, used to uniquely identify a serving cell (i.e. the PCell, the PSCell or an SCell) across the cell groups. Value 0 applies for the PCell, while the SCellIndex that has previously been assigned applies for SCells.
The IE ServingCellConfig is used to configure (add or modify) the UE with a serving cell, which may be the SpCell or an SCell of an MCG or SCG. The parameters herein are mostly UE specific but partly also cell specific (e.g. in additionally configured bandwidth parts). Reconfiguration between a PUCCH and PUCCHless SCell is only supported using an SCell release and add.
-- ASN1START -- TAG-SERVINGCELLCONFIG-START ServingCellConfig ::= SEQUENCE { tdd-UL-DL-ConfigurationDedicated TDD-UL-DL-ConfigDedicated OPTIONAL, -- Cond TDDinitialDownlinkBWPThe dedicated (UE-specific) configuration for the initial downlink bandwidth-part (i.e. DL BWP#0). If any of the optional IEs are configured within this IE, the UE considers the BWP#0 to be an RRC configured BWP (from UE capability viewpoint). Otherwise, the UE does not consider the BWP#0 as an RRC configured BWP (from UE capability viewpoint). Network always configures the UE with a value for this field if no other BWPs are configured. NOTE1BWP-DownlinkDedicated OPTIONAL, -- Need MdownlinkBWP-ToReleaseListList of additional downlink bandwidth parts to be released. (see TS 38.213 [13], clause 12).SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Id OPTIONAL, -- Need NdownlinkBWP-ToAddModListList of additional downlink bandwidth parts to be added or modified. (see TS 38.213 [13], clause 12).SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Downlink OPTIONAL, -- Need NfirstActiveDownlinkBWP-IdIf configured for an SpCell, this field contains the ID of the DL BWP to be activated upon performing the RRC (re-)configuration. If the field is absent, the RRC (re-)configuration does not impose a BWP switch. If configured for an SCell, this field contains the ID of the downlink bandwidth part to be used upon activation of an SCell. The initial bandwidth part is referred to by BWP-Id = 0. Upon reconfiguration with reconfigurationWithSync, the network sets the firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id to the same value.BWP-Id OPTIONAL, -- Cond SyncAndCellAddbwp-InactivityTimerThe duration in ms after which the UE falls back to the default Bandwidth Part (see TS 38.321 [3], clause 5.15). When the network releases the timer configuration, the UE stops the timer without switching to the default BWP.ENUMERATED {ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40,ms50, ms60, ms80,ms100, ms200,ms300, ms500, ms750, ms1280, ms1920, ms2560, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } OPTIONAL, --Need RdefaultDownlinkBWP-IdThe initial bandwidth part is referred to by BWP-Id = 0. ID of the downlink bandwidth part to be used upon expiry of the BWP inactivity timer. This field is UE specific. When the field is absent the UE uses the initial BWP as default BWP. (see TS 38.213 [13], clause 12 and TS 38.321 [3], clause 5.15).BWP-Id OPTIONAL, -- Need SuplinkConfigNetwork may configure this field only when uplinkConfigCommon is configured in ServingCellConfigCommon or ServingCellConfigCommonSIB. Addition or release of this field can only be done upon SCell addition or release (respectively).UplinkConfig OPTIONAL, -- Need MsupplementaryUplinkNetwork may configure this field only when supplementaryUplinkConfig is configured in ServingCellConfigCommon or supplementaryUplink is configured inServingCellConfigCommonSIB.UplinkConfig OPTIONAL, -- Need M pdcch-ServingCellConfig SetupRelease { PDCCH-ServingCellConfig } OPTIONAL, -- Need Mpdsch-ServingCellConfigPDSCH related parameters that are not BWP-specific.SetupRelease { PDSCH-ServingCellConfig } OPTIONAL, -- Need M csi-MeasConfig SetupRelease { CSI-MeasConfig } OPTIONAL, -- Need MsCellDeactivationTimerSCell deactivation timer in TS 38.321 [3]. If the field is absent, the UE applies the value infinity.ENUMERATED {ms20, ms40, ms80, ms160, ms200, ms240, ms320, ms400, ms480, ms520, ms640, ms720, ms840, ms1280, spare2,spare1} OPTIONAL, -- Cond ServingCellWithoutPUCCHcrossCarrierSchedulingConfigIndicates whether this serving cell is cross-carrier scheduled by another serving cell or whether it cross-carrier schedules another serving cell.CrossCarrierSchedulingConfig OPTIONAL, -- Need Mtag-IdTiming Advance Group ID, as specified in TS 38.321 [3], which this cell belongs to.TAG-Id, dummy1 ENUMERATED {enabled} OPTIONAL, -- Need RpathlossReferenceLinkingIndicates whether UE shall apply as pathloss reference either the downlink of SpCell (PCell for MCG or PSCell for SCG) or of SCell that corresponds with this uplink (see TS 38.213 [13], clause 7).ENUMERATED {spCell, sCell} OPTIONAL, -- Cond SCellOnlyservingCellMOmeasObjectId of the MeasObjectNR in MeasConfig which is associated to the serving cell. For this MeasObjectNR, the following relationship applies between this MeasObjectNR and frequencyInfoDL in ServingCellConfigCommon of the serving cell: if ssbFrequency is configured, its value is the same as the absoluteFrequencySSB and if csi-rs-ResourceConfigMobility is configured, the value of its subcarrierSpacing is present in one entry of the scs-SpecificCarrierList, csi-RS-CellListMobility includes an entry corresponding to the serving cell (with cellId equal to physCellId in ServingCellConfigCommon) and the frequency range indicated by the csi-rs-MeasurementBW of the entry in csi-RS-CellListMobility is included in the frequency range indicated by in the entry of the scs-SpecificCarrierList.MeasObjectId OPTIONAL, -- Cond MeasObject ..., [[lte-CRS-ToMatchAroundParameters to determine an LTE CRS pattern that the UE shall rate match around.SetupRelease { RateMatchPatternLTE-CRS } OPTIONAL, -- Need MrateMatchPatternToAddModListResources patterns which the UE should rate match PDSCH around. The UE rate matches around the union of all resources indicated in the rate match patterns. Rate match patterns defined here on cell level apply only to PDSCH of the same numerology. See TS 38.214 [19], clause 5.1.4.1.SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPattern OPTIONAL, -- Need N rateMatchPatternToReleaseList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPatternId OPTIONAL, -- Need NdownlinkChannelBW-PerSCS-ListA set of UE specific channel bandwidth and location configurations for different subcarrier spacings (numerologies). Defined in relation to Point A. The UE uses the configuration provided in this field only for the purpose of channel bandwidth and location determination. If absent, UE uses the configuration indicated in scs-SpecificCarrierList in DownlinkConfigCommon / DownlinkConfigCommonSIB. Network only configures channel bandwidth that corresponds to the channel bandwidth values defined in TS 38.101-1 [15] and TS 38.101-2 [39].SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier OPTIONAL -- Need S ]], [[supplementaryUplinkRelease-r16If this field is included, the UE shall release the uplink configuration configured by supplementaryUplink. The network only includes either supplementaryUplinkRelease or supplementaryUplink at a time.ENUMERATED {true} OPTIONAL, -- Need Ntdd-UL-DL-ConfigurationDedicated-IAB-MT-r16Resource configuration per IAB-MT D/U/F overrides all symbols (with a limitation that effectively only flexible symbols can be overwritten in Rel-16) per slot over the number of slots as provided by TDD-UL-DL ConfigurationCommon.TDD-UL-DL-ConfigDedicated-IAB-MT-r16 OPTIONAL, -- Cond TDD_IABdormantBWP-Config-r16The dormant BWP configuration for an SCell. This field can be configured only for a (non-PUCCH) SCell.SetupRelease { DormantBWP-Config-r16 } OPTIONAL, -- Need Mca-SlotOffset-r16Slot offset between the primary cell (PCell/PSCell) and the SCell in unaligned frame boundary with slot alignment and partial SFN alignment inter-band CA. Based on this field, the UE determines the time offset of the SCell as specified in clause 4.5 of TS 38.211 [16]. The granularity of this field is determined by the reference SCS for the slot offset (i.e. the maximum of PCell/PSCell lowest SCS among all the configured SCSs in DL/UL SCS-SpecificCarrierList in ServingCellConfigCommon or ServingCellConfigCommonSIB and this serving cell's lowest SCS among all the configured SCSs in DL/UL SCS-SpecificCarrierList in ServingCellConfigCommon or ServingCellConfigCommonSIB). The Network configures at most single non-zero offset duration in ms (independent on SCS) among CCs in the unaligned CA configuration. If the field is absent, the UE applies the value of 0.The slot offset value can only be changed with SCell release and add.CHOICE { refSCS15kHz INTEGER (-2..2), refSCS30KHz INTEGER (-5..5), refSCS60KHz INTEGER (-10..10), refSCS120KHz INTEGER (-20..20) } OPTIONAL, -- Cond AsyncCA dummy2 SetupRelease { DummyJ } OPTIONAL, -- Need M intraCellGuardBandsDL-List-r16 SEQUENCE (SIZE (1..maxSCSs)) OF IntraCellGuardBandsPerSCS-r16 OPTIONAL, -- Need S intraCellGuardBandsUL-List-r16 SEQUENCE (SIZE (1..maxSCSs)) OF IntraCellGuardBandsPerSCS-r16 OPTIONAL, -- Need Scsi-RS-ValidationWithDCI-r16Indicates how the UE performs periodic and semi-persistent CSI-RS reception in a slot. The presence of this field indicates that the UE usesDCI detection to validate whether to receive CSI-RS (see TS 38.213 [13], clause 11.1).ENUMERATED {enabled} OPTIONAL, -- Need Rlte-CRS-PatternList1-r16A list of LTE CRS patterns around which the UE shall do rate matching for PDSCH. The LTE CRS patterns in this list shall be non-overlapping in frequency. The network does not configure this field and lte-CRS-ToMatchAround simultaneously.SetupRelease { LTE-CRS-PatternList-r16 } OPTIONAL, -- Need Mlte-CRS-PatternList2-r16A list of LTE CRS patterns around which the UE shall do rate matching for PDSCH scheduled with a DCI detected on a CORESET with CORESETPoolIndex configured with 1. This list is configured only if CORESETPoolIndex configured with 1. The first LTE CRS pattern in this list shall be fully overlapping in frequency with the first LTE CRS pattern in lte-CRS-PatternList1, The second LTE CRS pattern in this list shall be fully overlapping in frequency with the second LTE CRS pattern in lte-CRS-PatternList1, and so on. Network configures this field only if the field lte-CRS-ToMatchAround is not configured and there is at least one ControlResourceSet in one DL BWP of this serving cell with coresetPoolIndex set to 1.SetupRelease { LTE-CRS-PatternList-r16 } OPTIONAL, -- Need Mcrs-RateMatch-PerCORESETPoolIndex-r16Indicates how UE performs rate matching when both lte-CRS-PatternList1-r16 and lte-CRS-PatternList2-r16 are configured as specified in TS 38.214 [19], clause 5.1.4.2.ENUMERATED {enabled} OPTIONAL, -- Need RenableTwoDefaultTCI-States-r16Presence of this field indicates the UE shall follow the release 16 behavior of two default TCI states for PDSCH when at least one TCI codepoint is mapped to two TCI states is enabledENUMERATED {enabled} OPTIONAL, -- Need RenableDefaultTCI-StatePerCoresetPoolIndex-r16Presence of this field indicates the UE shall follow the release 16 behavior of default TCI state per CORESETPoolindex when the UE is configured by higher layer parameter PDCCH-Config that contains two different values of CORESETPoolIndex in ControlResourceSet is enabled.ENUMERATED {enabled} OPTIONAL, -- Need RenableBeamSwitchTiming-r16Indicates the aperiodic CSI-RS triggering with beam switching triggering behaviour as defined in clause 5.2.1.5.1 of TS 38.214 [19].ENUMERATED {true} OPTIONAL, -- Need R cbg-TxDiffTBsProcessingType1-r16 ENUMERATED {enabled} OPTIONAL, -- Need R cbg-TxDiffTBsProcessingType2-r16 ENUMERATED {enabled} OPTIONAL -- Need R ]], [[directionalCollisionHandling-r16Indicates that this serving cell is using directional collision handling between a reference and other cell(s) for half-duplex operation in TDD CA with same SCS as specified in TS 38.213 [13], clause 11.1. The half-duplex operation only applies within the same frequency range and cell group. The network only configures this field for TDD serving cells that are using the same SCS.ENUMERATED {enabled} OPTIONAL, -- Need RchannelAccessConfig-r16List of parameters used for access procedures of operation with shared spectrum channel access (see TS 37.213 [48).SetupRelease { ChannelAccessConfig-r16 } OPTIONAL -- Need M ]] } UplinkConfig ::= SEQUENCE {initialUplinkBWPThe dedicated (UE-specific) configuration for the initial uplink bandwidth-part (i.e. UL BWP#0). If any of the optional IEs are configured within this IE as part of the IE uplinkConfig, the UE considers the BWP#0 to be an RRC configured BWP (from UE capability viewpoint). Otherwise, the UE does not consider the BWP#0 as an RRC configured BWP (from UE capability viewpoint). Network always configures the UE with a value for this field if no other BWPs are configured. NOTE1BWP-UplinkDedicated OPTIONAL, -- Need MuplinkBWP-ToReleaseListThe additional bandwidth parts for uplink to be released.SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Id OPTIONAL, -- Need NuplinkBWP-ToAddModListThe additional bandwidth parts for uplink to be added or modified. In case of TDD uplink- and downlink BWP with the same bandwidthPartId are considered as a BWP pair and must have the same center frequency.SEQUENCE (SIZE (1..maxNrofBWPs)) OF BWP-Uplink OPTIONAL, -- Need NfirstActiveUplinkBWP-IdIf configured for an SpCell, this field contains the ID of the UL BWP to be activated upon performing the RRC (re-)configuration. If the field is absent, the RRC (re-)configuration does not impose a BWP switch. If configured for an SCell, this field contains the ID of the uplink bandwidth part to be used upon activation of an SCell. The initial bandwidth part is referred to by BandiwdthPartId = 0.BWP-Id OPTIONAL, -- Cond SyncAndCellAddpusch-ServingCellConfigPUSCH related parameters that are not BWP-specific.SetupRelease { PUSCH-ServingCellConfig } OPTIONAL, -- Need McarrierSwitchingIncludes parameters for configuration of carrier based SRS switching (see TS 38.214 [19], clause 6.2.1.3.SetupRelease { SRS-CarrierSwitching } OPTIONAL, -- Need M ..., [[powerBoostPi2BPSKIf this field is set to true, the UE determines the maximum output power for PUCCH/PUSCH transmissions that use pi/2 BPSK modulation according to TS 38.101-1 [15], clause 6.2.4.BOOLEAN OPTIONAL, -- Need MuplinkChannelBW-PerSCS-ListA set of UE specific channel bandwidth and location configurations for different subcarrier spacings (numerologies). Defined in relation to Point A. The UE uses the configuration provided in this field only for the purpose of channel bandwidth and location determination. If absent, UE uses the configuration indicated in scs-SpecificCarrierList in UplinkConfigCommon / UplinkConfigCommonSIB. Network only configures channel bandwidth that corresponds to the channel bandwidth values defined in TS 38.101-1 [15] and TS 38.101-2 [39].SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier OPTIONAL -- Need S ]], [[enablePL-RS-UpdateForPUSCH-SRS-r16When this parameter is present, the Rel-16 feature of MAC CE based pathloss RS updates for PUSCH/SRS is enabled. Network only configures this parameter when the UE is configured with sri-PUSCH-PowerControl.If this field is not configured, network configures at most 4 pathloss RS resources for PUSCH/PUCCH/SRS transmissions per BWP, not including pathloss RS resources for SRS transmissions for positioning. (See TS 38.213 [13], clause 7).ENUMERATED {enabled} OPTIONAL, -- Need R enableDefaultBeamPL-ForPUSCH0-0-r16 ENUMERATED {enabled} OPTIONAL, -- Need R enableDefaultBeamPL-ForPUCCH-r16 ENUMERATED {enabled} OPTIONAL, -- Need R enableDefaultBeamPL-ForSRS-r16 ENUMERATED {enabled} OPTIONAL, -- Need R uplinkTxSwitching-r16 SetupRelease { UplinkTxSwitching-r16 } OPTIONAL, -- Need Mmpr-PowerBoost-FR2-r16Indicates whether UE is allowed to boost uplink transmission power by suspending in-band emission (IBE) requirements as specified in TS 38.101-2 [39]. Network only configures this field for FR2 serving cells.ENUMERATED {true} OPTIONAL -- Need R ]] } DummyJ ::= SEQUENCE {maxEnergyDetectionThreshold-r16Indicates the absolute maximum energy detection threshold value. Unit in dBm. Value -85 corresponds to -85 dBm, value -84 corresponds to -84 dBm, and so on (i.e. in steps of 1dBm) as specified in TS 37.213 [48], clause 4.2.3.INTEGER(-85..-52),energyDetectionThresholdOffset-r16Indicates the offset to the default maximum energy detection threshold value. Unit in dB. Value -13 corresponds to -13dB, value -12 corresponds to -12dB, and so on (i.e. in steps of 1dB) as specified in TS 37.213 [48], clause 4.2.3.INTEGER (-20..-13),ul-toDL-COT-SharingED-Threshold-r16Maximum energy detection threshold that the UE should use to share channel occupancy with gNB for DL transmission as specified in TS 37.213 [48], clause 4.1.3 for downlink channel access and clause 4.2.3 for uplink channel access.INTEGER (-85..-52) OPTIONAL, -- Need RabsenceOfAnyOtherTechnology-r16Presence of this field indicates absence on a long term basis (e.g. by level of regulation) of any other technology sharing the carrier; absence of this field indicates thepotential presence of any other technology sharing the carrier, as specified in TS 37.213 [48] clauses 4.2.1 and 4.2.3.ENUMERATED {true} OPTIONAL -- Need R } ChannelAccessConfig-r16 ::= SEQUENCE {energyDetectionConfig-r16Indicates whether to use the maxEnergyDetectionThreshold or theenergyDetectionThresholdOffset (see TS 37.213 [48], clause 4.2.3).CHOICE {maxEnergyDetectionThreshold-r16Indicates the absolute maximum energy detection threshold value. Unit in dBm. Value -85 corresponds to -85 dBm, value -84 corresponds to -84 dBm, and so on (i.e. in steps of 1dBm) as specified in TS 37.213 [48], clause 4.2.3.INTEGER (-85..-52),energyDetectionThresholdOffset-r16Indicates the offset to the default maximum energy detection threshold value. Unit in dB. Value -13 corresponds to -13dB, value -12 corresponds to -12dB, and so on (i.e. in steps of 1dB) as specified in TS 37.213 [48], clause 4.2.3.INTEGER (-13..20) } OPTIONAL, -- Need Rul-toDL-COT-SharingED-Threshold-r16Maximum energy detection threshold that the UE should use to share channel occupancy with gNB for DL transmission as specified in TS 37.213 [48], clause 4.1.3 for downlink channel access and clause 4.2.3 for uplink channel access.INTEGER (-85..-52) OPTIONAL, -- Need RabsenceOfAnyOtherTechnology-r16Presence of this field indicates absence on a long term basis (e.g. by level of regulation) of any other technology sharing the carrier; absence of this field indicates thepotential presence of any other technology sharing the carrier, as specified in TS 37.213 [48] clauses 4.2.1 and 4.2.3.ENUMERATED {true} OPTIONAL -- Need R } IntraCellGuardBandsPerSCS-r16 ::= SEQUENCE { guardBandSCS-r16 SubcarrierSpacing, intraCellGuardBands-r16 SEQUENCE (SIZE (1..4)) OF GuardBand-r16 } GuardBand-r16 ::= SEQUENCE {startCRB-r16Indicates the starting RB of the guard band.INTEGER (0..274), nrofCRBs-r16 INTEGER (0..15) } DormancyGroupID-r16 ::= INTEGER (0..4) DormantBWP-Config-r16::= SEQUENCE {dormantBWP-Id-r16This field contains the ID of the downlink bandwidth part to be used as dormant BWP. If this field is configured, its value is different from defaultDownlinkBWP-Id, and at least one of the withinActiveTimeConfig and outsideActiveTimeConfig should be configured.BWP-Id OPTIONAL, -- Need MwithinActiveTimeConfig-r16This field contains the configuration to be used for SCell dormancy within active time, as specified in TS 38.213 [13].SetupRelease { WithinActiveTimeConfig-r16 } OPTIONAL, -- Need MoutsideActiveTimeConfig-r16This field contains the configuration to be used for SCell dormancy outside active time, as specified in TS 38.213 [13]. The field can only be configured when the cell group the SCell belongs to is configured with dcp-Config.SetupRelease { OutsideActiveTimeConfig-r16 } OPTIONAL -- Need M } WithinActiveTimeConfig-r16 ::= SEQUENCE {firstWithinActiveTimeBWP-Id-r16This field contains the ID of the downlink bandwidth part to be activated when receiving a DCI indication for SCell dormancy within active time.BWP-Id OPTIONAL, -- Need MdormancyGroupWithinActiveTime-r16This field contains the ID of an SCell group for Dormancy within active time, to which this SCell belongs. The use of the Dormancy within active time for SCell groups is specified in TS 38.213 [13].DormancyGroupID-r16 OPTIONAL -- Need R } OutsideActiveTimeConfig-r16 ::= SEQUENCE {firstOutsideActiveTimeBWP-Id-r16This field contains the ID of the downlink bandwidth part to be activated when receiving a DCI indication for SCell dormancy outside active time.BWP-Id OPTIONAL, -- Need MdormancyGroupOutsideActiveTime-r16This field contains the ID of an SCell group for Dormancy outside active time, to which this SCell belongs. The use of the Dormancy outside active time for SCell groups is specified in TS 38.213 [13].DormancyGroupID-r16 OPTIONAL -- Need R } UplinkTxSwitching-r16 ::= SEQUENCE {uplinkTxSwitchingPeriodLocation-r16Indicates whether the location of UL Tx switching period is configured in this uplink carrier in case of inter-band UL CA, SUL, or (NG)EN-DC, as specified in TS 38.101-1 [15] and TS 38.101-3 [34]. In case of inter-band UL CA or SUL, network configures this field to TRUE for one of the uplink carriers involved in dynamic UL TX switching and configures this field in the other carrier to FALSE. In case of (NG)EN-DC, network always configures this field to TRUE for NR carrier (i.e. with (NG)EN-DC, the UL switching period always occurs on the NR carrier).BOOLEAN,uplinkTxSwitchingCarrier-r16Indicates that the configured carrier is carrier1 or carrier2 for dynamic uplink Tx switching, as defined in TS 38.101-1 [15] and TS 38.101-3 [34]. In case of inter-band UL CA or SUL, network configures one of the two uplink carriers involved in dynamic UL TX switching as carrier1 and the other as carrier2. In case of (NG)EN-DC, network always configures the NR carrier as carrier 2.ENUMERATED {carrier1, carrier2} } -- TAG-SERVINGCELLCONFIG-STOP -- ASN1STOP
ChannelAccessConfig field descriptions |
---|
absenceOfAnyOtherTechnology Presence of this field indicates absence on a long term basis (e.g. by level of regulation) of any other technology sharing the carrier; absence of this field indicates thepotential presence of any other technology sharing the carrier, as specified in TS 37.213 [48] clauses 4.2.1 and 4.2.3. |
energyDetectionConfig Indicates whether to use the maxEnergyDetectionThreshold or theenergyDetectionThresholdOffset (see TS 37.213 [48], clause 4.2.3). |
energyDetectionThresholdOffset Indicates the offset to the default maximum energy detection threshold value. Unit in dB. Value -13 corresponds to -13dB, value -12 corresponds to -12dB, and so on (i.e. in steps of 1dB) as specified in TS 37.213 [48], clause 4.2.3. |
maxEnergyDetectionThreshold Indicates the absolute maximum energy detection threshold value. Unit in dBm. Value -85 corresponds to -85 dBm, value -84 corresponds to -84 dBm, and so on (i.e. in steps of 1dBm) as specified in TS 37.213 [48], clause 4.2.3. |
ul-toDL-COT-SharingED-Threshold Maximum energy detection threshold that the UE should use to share channel occupancy with gNB for DL transmission as specified in TS 37.213 [48], clause 4.1.3 for downlink channel access and clause 4.2.3 for uplink channel access. |
ServingCellConfig field descriptions |
---|
bwp-InactivityTimer The duration in ms after which the UE falls back to the default Bandwidth Part (see TS 38.321 [3], clause 5.15). When the network releases the timer configuration, the UE stops the timer without switching to the default BWP. |
ca-SlotOffset Slot offset between the primary cell (PCell/PSCell) and the SCell in unaligned frame boundary with slot alignment and partial SFN alignment inter-band CA. Based on this field, the UE determines the time offset of the SCell as specified in clause 4.5 of TS 38.211 [16]. The granularity of this field is determined by the reference SCS for the slot offset (i.e. the maximum of PCell/PSCell lowest SCS among all the configured SCSs in DL/UL SCS-SpecificCarrierList in ServingCellConfigCommon or ServingCellConfigCommonSIB and this serving cell's lowest SCS among all the configured SCSs in DL/UL SCS-SpecificCarrierList in ServingCellConfigCommon or ServingCellConfigCommonSIB). The Network configures at most single non-zero offset duration in ms (independent on SCS) among CCs in the unaligned CA configuration. If the field is absent, the UE applies the value of 0.The slot offset value can only be changed with SCell release and add. |
cbg-TxDiffTBsProcessingType1, cbg-TxDiffTBsProcessingType2 Indicates whether processing types 1 and 2 based CBG based operation is enabled according to Rel-16 UE capabilities. |
channelAccessConfig List of parameters used for access procedures of operation with shared spectrum channel access (see TS 37.213 [48). |
crossCarrierSchedulingConfig Indicates whether this serving cell is cross-carrier scheduled by another serving cell or whether it cross-carrier schedules another serving cell. |
crs-RateMatch-PerCORESETPoolIndex Indicates how UE performs rate matching when both lte-CRS-PatternList1-r16 and lte-CRS-PatternList2-r16 are configured as specified in TS 38.214 [19], clause 5.1.4.2. |
csi-RS-ValidationWithDCI Indicates how the UE performs periodic and semi-persistent CSI-RS reception in a slot. The presence of this field indicates that the UE usesDCI detection to validate whether to receive CSI-RS (see TS 38.213 [13], clause 11.1). |
defaultDownlinkBWP-Id The initial bandwidth part is referred to by BWP-Id = 0. ID of the downlink bandwidth part to be used upon expiry of the BWP inactivity timer. This field is UE specific. When the field is absent the UE uses the initial BWP as default BWP. (see TS 38.213 [13], clause 12 and TS 38.321 [3], clause 5.15). |
directionalCollisionHandling Indicates that this serving cell is using directional collision handling between a reference and other cell(s) for half-duplex operation in TDD CA with same SCS as specified in TS 38.213 [13], clause 11.1. The half-duplex operation only applies within the same frequency range and cell group. The network only configures this field for TDD serving cells that are using the same SCS. |
dormantBWP-Config The dormant BWP configuration for an SCell. This field can be configured only for a (non-PUCCH) SCell. |
downlinkBWP-ToAddModList List of additional downlink bandwidth parts to be added or modified. (see TS 38.213 [13], clause 12). |
downlinkBWP-ToReleaseList List of additional downlink bandwidth parts to be released. (see TS 38.213 [13], clause 12). |
downlinkChannelBW-PerSCS-List A set of UE specific channel bandwidth and location configurations for different subcarrier spacings (numerologies). Defined in relation to Point A. The UE uses the configuration provided in this field only for the purpose of channel bandwidth and location determination. If absent, UE uses the configuration indicated in scs-SpecificCarrierList in DownlinkConfigCommon / DownlinkConfigCommonSIB. Network only configures channel bandwidth that corresponds to the channel bandwidth values defined in TS 38.101-1 [15] and TS 38.101-2 [39]. |
dummy1, dummy 2 This field is not used in the specification. If received it shall be ignored by the UE. |
enableBeamSwitchTiming Indicates the aperiodic CSI-RS triggering with beam switching triggering behaviour as defined in clause 5.2.1.5.1 of TS 38.214 [19]. |
enableDefaultTCI-StatePerCoresetPoolIndex Presence of this field indicates the UE shall follow the release 16 behavior of default TCI state per CORESETPoolindex when the UE is configured by higher layer parameter PDCCH-Config that contains two different values of CORESETPoolIndex in ControlResourceSet is enabled. |
enableTwoDefaultTCI-States Presence of this field indicates the UE shall follow the release 16 behavior of two default TCI states for PDSCH when at least one TCI codepoint is mapped to two TCI states is enabled |
firstActiveDownlinkBWP-Id If configured for an SpCell, this field contains the ID of the DL BWP to be activated upon performing the RRC (re-)configuration. If the field is absent, the RRC (re-)configuration does not impose a BWP switch. If configured for an SCell, this field contains the ID of the downlink bandwidth part to be used upon activation of an SCell. The initial bandwidth part is referred to by BWP-Id = 0. Upon reconfiguration with reconfigurationWithSync, the network sets the firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id to the same value. |
initialDownlinkBWP The dedicated (UE-specific) configuration for the initial downlink bandwidth-part (i.e. DL BWP#0). If any of the optional IEs are configured within this IE, the UE considers the BWP#0 to be an RRC configured BWP (from UE capability viewpoint). Otherwise, the UE does not consider the BWP#0 as an RRC configured BWP (from UE capability viewpoint). Network always configures the UE with a value for this field if no other BWPs are configured. NOTE1 |
intraCellGuardBandsDL-List, intraCellGuardBandsUL-List List of intra-cell guard bands in a serving cell for operation with shared spectrum channel access. If not configured, the guard bands are defined according to 38.101-1 [15], see TS 38.214 [19], clause 7. For operation in licensed spectrum, this field is absent, and no UE action is required. |
lte-CRS-PatternList1 A list of LTE CRS patterns around which the UE shall do rate matching for PDSCH. The LTE CRS patterns in this list shall be non-overlapping in frequency. The network does not configure this field and lte-CRS-ToMatchAround simultaneously. |
lte-CRS-PatternList2 A list of LTE CRS patterns around which the UE shall do rate matching for PDSCH scheduled with a DCI detected on a CORESET with CORESETPoolIndex configured with 1. This list is configured only if CORESETPoolIndex configured with 1. The first LTE CRS pattern in this list shall be fully overlapping in frequency with the first LTE CRS pattern in lte-CRS-PatternList1, The second LTE CRS pattern in this list shall be fully overlapping in frequency with the second LTE CRS pattern in lte-CRS-PatternList1, and so on. Network configures this field only if the field lte-CRS-ToMatchAround is not configured and there is at least one ControlResourceSet in one DL BWP of this serving cell with coresetPoolIndex set to 1. |
lte-CRS-ToMatchAround Parameters to determine an LTE CRS pattern that the UE shall rate match around. |
pathlossReferenceLinking Indicates whether UE shall apply as pathloss reference either the downlink of SpCell (PCell for MCG or PSCell for SCG) or of SCell that corresponds with this uplink (see TS 38.213 [13], clause 7). |
pdsch-ServingCellConfig PDSCH related parameters that are not BWP-specific. |
rateMatchPatternToAddModList Resources patterns which the UE should rate match PDSCH around. The UE rate matches around the union of all resources indicated in the rate match patterns. Rate match patterns defined here on cell level apply only to PDSCH of the same numerology. See TS 38.214 [19], clause 5.1.4.1. |
sCellDeactivationTimer SCell deactivation timer in TS 38.321 [3]. If the field is absent, the UE applies the value infinity. |
servingCellMO measObjectId of the MeasObjectNR in MeasConfig which is associated to the serving cell. For this MeasObjectNR, the following relationship applies between this MeasObjectNR and frequencyInfoDL in ServingCellConfigCommon of the serving cell: if ssbFrequency is configured, its value is the same as the absoluteFrequencySSB and if csi-rs-ResourceConfigMobility is configured, the value of its subcarrierSpacing is present in one entry of the scs-SpecificCarrierList, csi-RS-CellListMobility includes an entry corresponding to the serving cell (with cellId equal to physCellId in ServingCellConfigCommon) and the frequency range indicated by the csi-rs-MeasurementBW of the entry in csi-RS-CellListMobility is included in the frequency range indicated by in the entry of the scs-SpecificCarrierList. |
supplementaryUplink Network may configure this field only when supplementaryUplinkConfig is configured in ServingCellConfigCommon or supplementaryUplink is configured inServingCellConfigCommonSIB. |
supplementaryUplinkRelease If this field is included, the UE shall release the uplink configuration configured by supplementaryUplink. The network only includes either supplementaryUplinkRelease or supplementaryUplink at a time. |
tag-Id Timing Advance Group ID, as specified in TS 38.321 [3], which this cell belongs to. |
tdd-UL-DL-ConfigurationDedicated-IAB-MT Resource configuration per IAB-MT D/U/F overrides all symbols (with a limitation that effectively only flexible symbols can be overwritten in Rel-16) per slot over the number of slots as provided by TDD-UL-DL ConfigurationCommon. |
uplinkConfig Network may configure this field only when uplinkConfigCommon is configured in ServingCellConfigCommon or ServingCellConfigCommonSIB. Addition or release of this field can only be done upon SCell addition or release (respectively). |
UplinkConfig field descriptions |
---|
carrierSwitching Includes parameters for configuration of carrier based SRS switching (see TS 38.214 [19], clause 6.2.1.3. |
enableDefaultBeamPL-ForPUSCH0-0, enableDefaultBeamPL-ForPUCCH, enableDefaultBeamPL-ForSRS When the parameter is present, UE derives the spatial relation and the corresponding pathloss reference Rs as specified in 38.213, clauses 7.1.1, 7.2.1, 7.3.1 and 9.2.2. The network only configures these parameters for FR2. |
enablePL-RS-UpdateForPUSCH-SRS When this parameter is present, the Rel-16 feature of MAC CE based pathloss RS updates for PUSCH/SRS is enabled. Network only configures this parameter when the UE is configured with sri-PUSCH-PowerControl.If this field is not configured, network configures at most 4 pathloss RS resources for PUSCH/PUCCH/SRS transmissions per BWP, not including pathloss RS resources for SRS transmissions for positioning. (See TS 38.213 [13], clause 7). |
firstActiveUplinkBWP-Id If configured for an SpCell, this field contains the ID of the UL BWP to be activated upon performing the RRC (re-)configuration. If the field is absent, the RRC (re-)configuration does not impose a BWP switch. If configured for an SCell, this field contains the ID of the uplink bandwidth part to be used upon activation of an SCell. The initial bandwidth part is referred to by BandiwdthPartId = 0. |
initialUplinkBWP The dedicated (UE-specific) configuration for the initial uplink bandwidth-part (i.e. UL BWP#0). If any of the optional IEs are configured within this IE as part of the IE uplinkConfig, the UE considers the BWP#0 to be an RRC configured BWP (from UE capability viewpoint). Otherwise, the UE does not consider the BWP#0 as an RRC configured BWP (from UE capability viewpoint). Network always configures the UE with a value for this field if no other BWPs are configured. NOTE1 |
mpr-PowerBoost-FR2 Indicates whether UE is allowed to boost uplink transmission power by suspending in-band emission (IBE) requirements as specified in TS 38.101-2 [39]. Network only configures this field for FR2 serving cells. |
powerBoostPi2BPSK If this field is set to true, the UE determines the maximum output power for PUCCH/PUSCH transmissions that use pi/2 BPSK modulation according to TS 38.101-1 [15], clause 6.2.4. |
pusch-ServingCellConfig PUSCH related parameters that are not BWP-specific. |
uplinkBWP-ToAddModList The additional bandwidth parts for uplink to be added or modified. In case of TDD uplink- and downlink BWP with the same bandwidthPartId are considered as a BWP pair and must have the same center frequency. |
uplinkBWP-ToReleaseList The additional bandwidth parts for uplink to be released. |
uplinkChannelBW-PerSCS-List A set of UE specific channel bandwidth and location configurations for different subcarrier spacings (numerologies). Defined in relation to Point A. The UE uses the configuration provided in this field only for the purpose of channel bandwidth and location determination. If absent, UE uses the configuration indicated in scs-SpecificCarrierList in UplinkConfigCommon / UplinkConfigCommonSIB. Network only configures channel bandwidth that corresponds to the channel bandwidth values defined in TS 38.101-1 [15] and TS 38.101-2 [39]. |
uplinkTxSwitchingPeriodLocation Indicates whether the location of UL Tx switching period is configured in this uplink carrier in case of inter-band UL CA, SUL, or (NG)EN-DC, as specified in TS 38.101-1 [15] and TS 38.101-3 [34]. In case of inter-band UL CA or SUL, network configures this field to TRUE for one of the uplink carriers involved in dynamic UL TX switching and configures this field in the other carrier to FALSE. In case of (NG)EN-DC, network always configures this field to TRUE for NR carrier (i.e. with (NG)EN-DC, the UL switching period always occurs on the NR carrier). |
uplinkTxSwitchingCarrier Indicates that the configured carrier is carrier1 or carrier2 for dynamic uplink Tx switching, as defined in TS 38.101-1 [15] and TS 38.101-3 [34]. In case of inter-band UL CA or SUL, network configures one of the two uplink carriers involved in dynamic UL TX switching as carrier1 and the other as carrier2. In case of (NG)EN-DC, network always configures the NR carrier as carrier 2. |
DormantBWP-Config field descriptions |
---|
dormancyGroupWithinActiveTime This field contains the ID of an SCell group for Dormancy within active time, to which this SCell belongs. The use of the Dormancy within active time for SCell groups is specified in TS 38.213 [13]. |
dormancyGroupOutsideActiveTime This field contains the ID of an SCell group for Dormancy outside active time, to which this SCell belongs. The use of the Dormancy outside active time for SCell groups is specified in TS 38.213 [13]. |
dormantBWP-Id This field contains the ID of the downlink bandwidth part to be used as dormant BWP. If this field is configured, its value is different from defaultDownlinkBWP-Id, and at least one of the withinActiveTimeConfig and outsideActiveTimeConfig should be configured. |
firstOutsideActiveTimeBWP-Id This field contains the ID of the downlink bandwidth part to be activated when receiving a DCI indication for SCell dormancy outside active time. |
firstWithinActiveTimeBWP-Id This field contains the ID of the downlink bandwidth part to be activated when receiving a DCI indication for SCell dormancy within active time. |
outsideActiveTimeConfig This field contains the configuration to be used for SCell dormancy outside active time, as specified in TS 38.213 [13]. The field can only be configured when the cell group the SCell belongs to is configured with dcp-Config. |
withinActiveTimeConfig This field contains the configuration to be used for SCell dormancy within active time, as specified in TS 38.213 [13]. |
GuardBand field descriptions |
---|
startCRB Indicates the starting RB of the guard band. |
nrofCRB Indicates the length of the guard band in RBs. When set to 0, zero-size guard band is used. |
Conditional Presence | Explanation |
---|---|
AsyncCA | This field is mandatory present for SCells whose slot offset between the SpCell is not 0. Otherwise it is absent, Need S. |
MeasObject | This field is mandatory present for the SpCell if the UE has a measConfig, and it is optionally present, Need M, for SCells. |
SCellOnly | This field is optionally present, Need R, for SCells. It is absent otherwise. |
ServingCellWithoutPUCCH | This field is optionally present, Need S, for SCells except PUCCH SCells. It is absent otherwise. |
SyncAndCellAdd | This field is mandatory present for a SpCell upon reconfiguration with reconfigurationWithSyncand upon RRCSetup/RRCResume. The field is optionally present for an SpCell, Need N, upon reconfiguration without reconfigurationWithSync. The field is mandatory present for an SCell upon addition, and absent for SCell in other cases, Need M. |
TDD | This field is optionally present, Need R, for TDD cells. It is absent otherwise. |
TDD_IAB | For IAB-MT, this field is optionally present, Need R, for TDD cells. It is absent otherwise. |
The IE ServingCellConfigCommon is used to configure cell specific parameters of a UE's serving cell. The IE contains parameters which a UE would typically acquire from SSB,MIB or SIBs when accessing the cell from IDLE. With this IE,the network provides this information in dedicated signalling when configuring a UE with a SCells or with an additional cell group (SCG). It also provides it for SpCells (MCG and SCG) upon reconfiguration with sync.
-- ASN1START -- TAG-SERVINGCELLCONFIGCOMMON-START ServingCellConfigCommon ::= SEQUENCE { physCellId PhysCellId OPTIONAL, -- Cond HOAndServCellAdd,downlinkConfigCommonThe common downlink configuration of the serving cell, including the frequency information configuration and the initial downlink BWP common configuration. The parameters provided herein should match the parameters configured by MIB and SIB1 (if provided) of the serving cell, with the exception of controlResourceSetZero and searchSpaceZero which can be configured in ServingCellConfigCommon even if MIB indicates that they are absent.DownlinkConfigCommon OPTIONAL, -- Cond HOAndServCellAdd uplinkConfigCommon UplinkConfigCommon OPTIONAL, -- Need MsupplementaryUplinkConfigThe network configures this field only if uplinkConfigCommon is configured. If this field is absent, the UE shall release the supplementaryUplinkConfig and the supplementaryUplink configured in ServingCellConfig of this serving cell, if configured.UplinkConfigCommon OPTIONAL, -- Need Sn-TimingAdvanceOffsetThe N_TA-Offset to be applied for all uplink transmissions on this serving cell. If the field is absent, the UE applies the value defined for the duplex mode and frequency range of this serving cell. See TS 38.133 [14], table 7.1.2-2.ENUMERATED { n0, n25600, n39936 } OPTIONAL, -- Need Sssb-PositionsInBurstFor operation in licensed spectrum, indicates the time domain positions of the transmitted SS-blocks in a half frame with SS/PBCH blocks as defined in TS 38.213 [13], clause 4.1. The first/leftmost bit corresponds to SS/PBCH block index 0, the second bit corresponds to SS/PBCH block index 1, and so on. Value 0 in the bitmap indicates that the corresponding SS/PBCH block is not transmitted while value 1 indicates that the corresponding SS/PBCH block is transmitted. The network configures the same pattern in this field as in the corresponding field in ServingCellConfigCommonSIB. For operation with shared spectrum channel access, only mediumBitmap is used and the UE assumes that one or more SS/PBCH blocks indicated by ssb-PositionsInBurst may be transmitted within the discovery burst transmission window and have candidate SS/PBCH blocks indexes corresponding to SS/PBCH block indexes provided by ssb-PositionsInBurst (see TS 38.213 [13], clause 4.1). If the k-th bit of ssb-PositionsInBurst is set to 1, the UE assumes that one or more SS/PBCH blocks within the discovery burst transmission window with candidate SS/PBCH block indexes corresponding to SS/PBCH block index equal to k – 1 may be transmitted; if the kt-th bit is set to 0, the UE assumes that the corresponding SS/PBCH block(s) are not transmitted. The k-th bit is set to 0, where k > ssb-PositionQCL and the number of actually transmitted SS/PBCH blocks is not larger than the number of 1's in the bitmap. The network configures the same pattern in this field as in the corresponding field in ServingCellConfigCommonSIB.CHOICE {shortBitmapBitmap when maximum number of SS/PBCH blocks per half frame equals to 4 as defined in TS 38.213 [13], clause 4.1.BIT STRING (SIZE (4)),mediumBitmapBitmap when maximum number of SS/PBCH blocks per half frame equals to 8 as defined in TS 38.213 [13], clause 4.1.BIT STRING (SIZE (8)),longBitmapBitmap when maximum number of SS/PBCH blocks per half frame equals to 64 as defined in TS 38.213 [13], clause 4.1.BIT STRING (SIZE (64)) } OPTIONAL, -- Cond AbsFreqSSBssb-periodicityServingCellThe SSB periodicity in ms for the rate matching purpose. If the field is absent, the UE applies the value ms5. (see TS 38.213 [13], clause 4.1)ENUMERATED { ms5, ms10, ms20, ms40, ms80, ms160, spare2, spare1 } OPTIONAL, -- Need Sdmrs-TypeA-PositionPosition of (first) DM-RS for downlink (see TS 38.211 [16], clause 7.4.1.1.1) and uplink (TS 38.211 [16], clause 6.4.1.1.3).ENUMERATED {pos2, pos3},lte-CRS-ToMatchAroundParameters to determine an LTE CRS pattern that the UE shall rate match around.SetupRelease { RateMatchPatternLTE-CRS } OPTIONAL, -- Need MrateMatchPatternToAddModListResources patterns which the UE should rate match PDSCH around. The UE rate matches around the union of all resources indicated in the rate match patterns. Rate match patterns defined here on cell level apply only to PDSCH of the same numerology (see TS 38.214 [19], clause 5.1.4,1).SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPattern OPTIONAL, -- Need N rateMatchPatternToReleaseList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPatternId OPTIONAL, -- Need NssbSubcarrierSpacingSubcarrier spacing of SSB. Only the values 15 kHz or 30 kHz (FR1), and 120 kHz or 240 kHz (FR2) are applicable.SubcarrierSpacing OPTIONAL, -- Cond HOAndServCellWithSSBtdd-UL-DL-ConfigurationCommonA cell-specific TDD UL/DL configuration, see TS 38.213 [13], clause 11.1.TDD-UL-DL-ConfigCommon OPTIONAL, -- Cond TDDss-PBCH-BlockPowerAverage EPRE of the resources elements that carry secondary synchronization signals in dBm that the NW used for SSB transmission, see TS 38.213 [13], clause 7.INTEGER (-60..50), ..., [[channelAccessMode-r16If present, this field indicates which channel access procedures to apply for operation with shared spectrum channel access as defined in TS 37.213 [48]. If the field is configured as "semiStatic", the UE shall apply the channel access procedures for semi-static channel occupancy as described in clause 4.3 in TS 37.213. If the field is configured as "dynamic", the UE shall apply the channel access procedures in TS 37.213, with the exception of clause 4.3 of TS 37.213.CHOICE { dynamic NULL, semiStatic SemiStaticChannelAccessConfig-r16 } OPTIONAL, -- Cond SharedSpectrumdiscoveryBurstWindowLength-r16Indicates the window length of the discovery burst in ms (see TS 37.213 [48]).ENUMERATED {ms0dot5, ms1, ms2, ms3, ms4, ms5} OPTIONAL, -- Need Rssb-PositionQCL-r16Indicates the QCL relation between SSB positions for this serving cell as specified in TS 38.213 [13], clause 4.1.SSB-PositionQCL-Relation-r16 OPTIONAL, -- Cond SharedSpectrum highSpeedConfig-r16 HighSpeedConfig-r16 OPTIONAL -- Need R ]] } -- TAG-SERVINGCELLCONFIGCOMMON-STOP -- ASN1STOP
ServingCellConfigCommon field descriptions |
---|
channelAccessMode If present, this field indicates which channel access procedures to apply for operation with shared spectrum channel access as defined in TS 37.213 [48]. If the field is configured as "semiStatic", the UE shall apply the channel access procedures for semi-static channel occupancy as described in clause 4.3 in TS 37.213. If the field is configured as "dynamic", the UE shall apply the channel access procedures in TS 37.213, with the exception of clause 4.3 of TS 37.213. |
dmrs-TypeA-Position Position of (first) DM-RS for downlink (see TS 38.211 [16], clause 7.4.1.1.1) and uplink (TS 38.211 [16], clause 6.4.1.1.3). |
downlinkConfigCommon The common downlink configuration of the serving cell, including the frequency information configuration and the initial downlink BWP common configuration. The parameters provided herein should match the parameters configured by MIB and SIB1 (if provided) of the serving cell, with the exception of controlResourceSetZero and searchSpaceZero which can be configured in ServingCellConfigCommon even if MIB indicates that they are absent. |
discoveryBurstWindowLength Indicates the window length of the discovery burst in ms (see TS 37.213 [48]). |
longBitmap Bitmap when maximum number of SS/PBCH blocks per half frame equals to 64 as defined in TS 38.213 [13], clause 4.1. |
lte-CRS-ToMatchAround Parameters to determine an LTE CRS pattern that the UE shall rate match around. |
mediumBitmap Bitmap when maximum number of SS/PBCH blocks per half frame equals to 8 as defined in TS 38.213 [13], clause 4.1. |
n-TimingAdvanceOffset The N_TA-Offset to be applied for all uplink transmissions on this serving cell. If the field is absent, the UE applies the value defined for the duplex mode and frequency range of this serving cell. See TS 38.133 [14], table 7.1.2-2. |
rateMatchPatternToAddModList Resources patterns which the UE should rate match PDSCH around. The UE rate matches around the union of all resources indicated in the rate match patterns. Rate match patterns defined here on cell level apply only to PDSCH of the same numerology (see TS 38.214 [19], clause 5.1.4,1). |
shortBitmap Bitmap when maximum number of SS/PBCH blocks per half frame equals to 4 as defined in TS 38.213 [13], clause 4.1. |
ss-PBCH-BlockPower Average EPRE of the resources elements that carry secondary synchronization signals in dBm that the NW used for SSB transmission, see TS 38.213 [13], clause 7. |
ssb-periodicityServingCell The SSB periodicity in ms for the rate matching purpose. If the field is absent, the UE applies the value ms5. (see TS 38.213 [13], clause 4.1) |
ssb-PositionQCL Indicates the QCL relation between SSB positions for this serving cell as specified in TS 38.213 [13], clause 4.1. |
ssb-PositionsInBurst For operation in licensed spectrum, indicates the time domain positions of the transmitted SS-blocks in a half frame with SS/PBCH blocks as defined in TS 38.213 [13], clause 4.1. The first/leftmost bit corresponds to SS/PBCH block index 0, the second bit corresponds to SS/PBCH block index 1, and so on. Value 0 in the bitmap indicates that the corresponding SS/PBCH block is not transmitted while value 1 indicates that the corresponding SS/PBCH block is transmitted. The network configures the same pattern in this field as in the corresponding field in ServingCellConfigCommonSIB. For operation with shared spectrum channel access, only mediumBitmap is used and the UE assumes that one or more SS/PBCH blocks indicated by ssb-PositionsInBurst may be transmitted within the discovery burst transmission window and have candidate SS/PBCH blocks indexes corresponding to SS/PBCH block indexes provided by ssb-PositionsInBurst (see TS 38.213 [13], clause 4.1). If the k-th bit of ssb-PositionsInBurst is set to 1, the UE assumes that one or more SS/PBCH blocks within the discovery burst transmission window with candidate SS/PBCH block indexes corresponding to SS/PBCH block index equal to k – 1 may be transmitted; if the kt-th bit is set to 0, the UE assumes that the corresponding SS/PBCH block(s) are not transmitted. The k-th bit is set to 0, where k > ssb-PositionQCL and the number of actually transmitted SS/PBCH blocks is not larger than the number of 1's in the bitmap. The network configures the same pattern in this field as in the corresponding field in ServingCellConfigCommonSIB. |
ssbSubcarrierSpacing Subcarrier spacing of SSB. Only the values 15 kHz or 30 kHz (FR1), and 120 kHz or 240 kHz (FR2) are applicable. |
supplementaryUplinkConfig The network configures this field only if uplinkConfigCommon is configured. If this field is absent, the UE shall release the supplementaryUplinkConfig and the supplementaryUplink configured in ServingCellConfig of this serving cell, if configured. |
tdd-UL-DL-ConfigurationCommon A cell-specific TDD UL/DL configuration, see TS 38.213 [13], clause 11.1. |
Conditional Presence | Explanation |
---|---|
AbsFreqSSB | The field is absent when absoluteFrequencySSB in frequencyInfoDL is absent, otherwise the field is mandatory present. |
HOAndServCellAdd | This field is mandatory present upon SpCell change and upon serving cell (PSCell/SCell) addition. Otherwise, the field is absent. |
HOAndServCellWithSSB | This field is mandatory present upon SpCell change and upon serving cell (SCell with SSB or PSCell) addition. Otherwise, the field is absent. |
SharedSpectrum | This field is mandatory present if this cell operates with shared spectrum channel access. Otherwise, it is absent, Need R. |
TDD | The field is optionally present, Need R, for TDD cells; otherwise it is absent. |
The IE ServingCellConfigCommonSIB is used to configure cell specific parameters of a UE's serving cell in SIB1.
-- ASN1START -- TAG-SERVINGCELLCONFIGCOMMONSIB-START ServingCellConfigCommonSIB ::= SEQUENCE { downlinkConfigCommon DownlinkConfigCommonSIB, uplinkConfigCommon UplinkConfigCommonSIB OPTIONAL, -- Need R supplementaryUplink UplinkConfigCommonSIB OPTIONAL, -- Need Rn-TimingAdvanceOffsetThe N_TA-Offset to be applied for random access on this serving cell. If the field is absent, the UE applies the value defined for the duplex mode and frequency range of this serving cell. See TS 38.133 [14], table 7.1.2-2.ENUMERATED { n0, n25600, n39936 } OPTIONAL, -- Need Sssb-PositionsInBurstTime domain positions of the transmitted SS-blocks in an SS-burst as defined in TS 38.213 [13], clause 4.1. For operation with shared spectrum channel access, only inOneGroupis used and the UE interprets this field same as mediumBitmap in ServingCellConfigCommon. The UE assumes that a bit at position k > is 0, where is obtained from MIB as specified in TS 38.213 [13], clause 4.1.SEQUENCE {inOneGroupWhen maximum number of SS/PBCH blocks per half frame equals to 4 as defined in TS 38.213 [13], clause 4.1, only the 4 leftmost bits are valid; the UE ignores the 4 rightmost bits. When maximum number of SS/PBCH blocks per half frame equals to 8 as defined in TS 38.213 [13], clause 4.1, all 8 bits are valid. The first/ leftmost bit corresponds to SS/PBCH block index 0, the second bit corresponds to SS/PBCH block index 1, and so on. When maximum number of SS/PBCH blocks per half frame equals to 64 as defined in TS 38.213 [13], clause 4.1, all 8 bit are valid; The first/ leftmost bit corresponds to the first SS/PBCH block index in the group (i.e., to SSB index 0, 8, and so on); the second bit corresponds to the second SS/PBCH block index in the group (i.e., to SSB index 1, 9, and so on), and so on. Value 0 in the bitmap indicates that the corresponding SS/PBCH block is not transmitted while value 1 indicates that the corresponding SS/PBCH block is transmitted.BIT STRING (SIZE (8)),groupPresenceThis field is present when maximum number of SS/PBCH blocks per half frame equals to 64 as defined in TS 38.213 [13], clause 4.1. The first/leftmost bit corresponds to the SS/PBCH index 0-7, the second bit corresponds to SS/PBCH block 8-15, and so on. Value 0 in the bitmap indicates that the SSBs according to inOneGroup are absent. Value 1 indicates that the SS/PBCH blocks are transmitted in accordance with inOneGroup.BIT STRING (SIZE (8)) OPTIONAL -- Cond FR2-Only }, ssb-PeriodicityServingCell ENUMERATED {ms5, ms10, ms20, ms40, ms80, ms160}, tdd-UL-DL-ConfigurationCommon TDD-UL-DL-ConfigCommon OPTIONAL, -- Cond TDDss-PBCH-BlockPowerAverage EPRE of the resources elements that carry secondary synchronization signals in dBm that the NW used for SSB transmission, see TS 38.213 [13], clause 7.INTEGER (-60..50), ..., [[channelAccessMode-r16If present, this field indicates which channel access procedures to apply for operation with shared spectrum channel access as defined in TS 37.213 [48]. If the field is configured as "semiStatic", the UE shall apply the channel access procedures for semi-static channel occupancy as described in clause 4.3 in TS 37.213. If the field is configured as "dynamic", the UE shall apply the channel access procedures in TS 37.213, with the exception of clause 4.3 of TS 37.213.CHOICE { dynamic NULL, semiStatic SemiStaticChannelAccessConfig-r16 } OPTIONAL, -- Cond SharedSpectrumdiscoveryBurstWindowLength-r16Indicates the window length of the discovery burst in ms (see TS 37.213 [48]).ENUMERATED {ms0dot5, ms1, ms2, ms3, ms4, ms5} OPTIONAL, -- Need R highSpeedConfig-r16 HighSpeedConfig-r16 OPTIONAL -- Need R ]] } -- TAG-SERVINGCELLCONFIGCOMMONSIB-STOP -- ASN1STOP
ServingCellConfigCommonSIB field descriptions |
---|
channelAccessMode If present, this field indicates which channel access procedures to apply for operation with shared spectrum channel access as defined in TS 37.213 [48]. If the field is configured as "semiStatic", the UE shall apply the channel access procedures for semi-static channel occupancy as described in clause 4.3 in TS 37.213. If the field is configured as "dynamic", the UE shall apply the channel access procedures in TS 37.213, with the exception of clause 4.3 of TS 37.213. |
discoveryBurstWindowLength Indicates the window length of the discovery burst in ms (see TS 37.213 [48]). |
groupPresence This field is present when maximum number of SS/PBCH blocks per half frame equals to 64 as defined in TS 38.213 [13], clause 4.1. The first/leftmost bit corresponds to the SS/PBCH index 0-7, the second bit corresponds to SS/PBCH block 8-15, and so on. Value 0 in the bitmap indicates that the SSBs according to inOneGroup are absent. Value 1 indicates that the SS/PBCH blocks are transmitted in accordance with inOneGroup. |
inOneGroup When maximum number of SS/PBCH blocks per half frame equals to 4 as defined in TS 38.213 [13], clause 4.1, only the 4 leftmost bits are valid; the UE ignores the 4 rightmost bits. When maximum number of SS/PBCH blocks per half frame equals to 8 as defined in TS 38.213 [13], clause 4.1, all 8 bits are valid. The first/ leftmost bit corresponds to SS/PBCH block index 0, the second bit corresponds to SS/PBCH block index 1, and so on. When maximum number of SS/PBCH blocks per half frame equals to 64 as defined in TS 38.213 [13], clause 4.1, all 8 bit are valid; The first/ leftmost bit corresponds to the first SS/PBCH block index in the group (i.e., to SSB index 0, 8, and so on); the second bit corresponds to the second SS/PBCH block index in the group (i.e., to SSB index 1, 9, and so on), and so on. Value 0 in the bitmap indicates that the corresponding SS/PBCH block is not transmitted while value 1 indicates that the corresponding SS/PBCH block is transmitted. |
n-TimingAdvanceOffset The N_TA-Offset to be applied for random access on this serving cell. If the field is absent, the UE applies the value defined for the duplex mode and frequency range of this serving cell. See TS 38.133 [14], table 7.1.2-2. |
ssb-PositionsInBurst Time domain positions of the transmitted SS-blocks in an SS-burst as defined in TS 38.213 [13], clause 4.1. For operation with shared spectrum channel access, only inOneGroupis used and the UE interprets this field same as mediumBitmap in ServingCellConfigCommon. The UE assumes that a bit at position k > is 0, where is obtained from MIB as specified in TS 38.213 [13], clause 4.1. |
ss-PBCH-BlockPower Average EPRE of the resources elements that carry secondary synchronization signals in dBm that the NW used for SSB transmission, see TS 38.213 [13], clause 7. |
Conditional Presence | Explanation |
---|---|
FR2-Only | This field is mandatory present for an FR2 carrier frequency. It is absent otherwise and UE releases any configured value. |
SharedSpectrum | This field is mandatory present if this cell operates with shared spectrum channel access. Otherwise, it is absent, Need R. |
TDD | The field is optionally present, Need R, for TDD cells; otherwise it is absent. |
The IE ShortI-RNTI-Value is used to identify the suspended UE context of a UE in RRC_INACTIVE using fewer bits compared to I-RNTI-Value.
The IE ShortMAC-I is used to identify and verify the UE at RRC connection re-establishment. The 16 least significant bits of the MAC-I calculated using the AS security configuration of the source PCell, as specified in 5.3.7.4.
The IE SINR-Range specifies the value range used in SINR measurements and thresholds. For measurements, integer value for SINR measurements is according to Table 10.1.16.1-1 in TS 38.133 [14]. For thresholds, the actual value is (IE value – 46) / 2 dB.
The IE SI-RequestConfig contains configuration for Msg1 based SI request.
-- ASN1START -- TAG-SI-REQUESTCONFIG-START SI-RequestConfig ::= SEQUENCE {rach-OccasionsSIConfiguration of dedicated RACH Occasions for SI. If the field is absent, the UE uses the corresponding parameters configured in rach-ConfigCommon of the initial uplink BWP.SEQUENCE { rach-ConfigSI RACH-ConfigGeneric, ssb-perRACH-Occasion ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen} } OPTIONAL, -- Need Rsi-RequestPeriodPeriodicity of the SI-Request configuration in number of association periods.ENUMERATED {one, two, four, six, eight, ten, twelve, sixteen} OPTIONAL, -- Need Rsi-RequestResourcesIf there is only one entry in the list, the configuration is used for all SI messages for which si-BroadcastStatusor posSI-BroadcastStatusis set to notBroadcasting. Otherwise, when the SI-RequestConfig is used for on-demand SI request in SI-SchedulingInfo or PosSI-SchedulingInfo, the 1st entry in the list corresponds to the first SI message in schedulingInfoList/posSchedulingInfoList for which si-BroadcastStatus/posSI-BroadcastStatus is set to notBroadcasting, 2nd entry in the list corresponds to the second SI message in schedulingInfoList/posSchedulingInfoList for which si-BroadcastStatus/posSI-BroadcastStatus is set to notBroadcasting and so on. Change of si-RequestResources should not result in system information change notification.SEQUENCE (SIZE (1..maxSI-Message)) OF SI-RequestResources } SI-RequestResources ::= SEQUENCE {ra-PreambleStartIndexIf N SSBs are associated with a RACH occasion, where N > = 1, for the i-th SSB (i=0, …, N-1) the preamble with preamble index = ra-PreambleStartIndex + i is used for SI request; For N < 1, the preamble with preamble index = ra-PreambleStartIndex is used for SI request.INTEGER (0..63),ra-AssociationPeriodIndexIndex of the association period in the si-RequestPeriod in which the UE can send the SI request for SI message(s) corresponding to this SI-RequestResources, using the preambles indicated by ra-PreambleStartIndex and rach occasions indicated by ra-ssb-OccasionMaskIndex.INTEGER (0..15) OPTIONAL, -- Need R ra-ssb-OccasionMaskIndex INTEGER (0..15) OPTIONAL -- Need R } -- TAG-SI-REQUESTCONFIG-STOP -- ASN1STOP
SI-RequestConfig field descriptions |
---|
rach-OccasionsSI Configuration of dedicated RACH Occasions for SI. If the field is absent, the UE uses the corresponding parameters configured in rach-ConfigCommon of the initial uplink BWP. |
si-RequestPeriod Periodicity of the SI-Request configuration in number of association periods. |
si-RequestResources If there is only one entry in the list, the configuration is used for all SI messages for which si-BroadcastStatusor posSI-BroadcastStatusis set to notBroadcasting. Otherwise, when the SI-RequestConfig is used for on-demand SI request in SI-SchedulingInfo or PosSI-SchedulingInfo, the 1st entry in the list corresponds to the first SI message in schedulingInfoList/posSchedulingInfoList for which si-BroadcastStatus/posSI-BroadcastStatus is set to notBroadcasting, 2nd entry in the list corresponds to the second SI message in schedulingInfoList/posSchedulingInfoList for which si-BroadcastStatus/posSI-BroadcastStatus is set to notBroadcasting and so on. Change of si-RequestResources should not result in system information change notification. |
SI-RequestResources field descriptions |
---|
ra-AssociationPeriodIndex Index of the association period in the si-RequestPeriod in which the UE can send the SI request for SI message(s) corresponding to this SI-RequestResources, using the preambles indicated by ra-PreambleStartIndex and rach occasions indicated by ra-ssb-OccasionMaskIndex. |
ra-PreambleStartIndex If N SSBs are associated with a RACH occasion, where N > = 1, for the i-th SSB (i=0, …, N-1) the preamble with preamble index = ra-PreambleStartIndex + i is used for SI request; For N < 1, the preamble with preamble index = ra-PreambleStartIndex is used for SI request. |
The IE SI-SchedulingInfo contains information needed for acquisition of SI messages.
-- ASN1START -- TAG-SI-SCHEDULINGINFO-START SI-SchedulingInfo ::= SEQUENCE { schedulingInfoList SEQUENCE (SIZE (1..maxSI-Message)) OF SchedulingInfo,si-WindowLengthThe length of the SI scheduling window. Value s5 corresponds to 5 slots, value s10 corresponds to 10 slots and so on. The network always configures si-WindowLength to be shorter than or equal to the si-Periodicity.ENUMERATED {s5, s10, s20, s40, s80, s160, s320, s640, s1280},si-RequestConfigConfiguration of Msg1 resources that the UE uses for requesting SI-messages for which si-BroadcastStatus is set to notBroadcasting.SI-RequestConfig OPTIONAL, -- Cond MSG-1si-RequestConfigSULConfiguration of Msg1 resources that the UE uses for requesting SI-messages for which si-BroadcastStatus is set to notBroadcasting.SI-RequestConfig OPTIONAL, -- Cond SUL-MSG-1systemInformationAreaIDIndicates the system information area that the cell belongs to, if any. Any SIB with areaScope within the SI is considered to belong to this systemInformationAreaID. The systemInformationAreaID is unique within a PLMN/SNPN.BIT STRING (SIZE (24)) OPTIONAL, -- Need R ... } SchedulingInfo ::= SEQUENCE {si-BroadcastStatusIndicates if the SI message is being broadcasted or not. Change of si-BroadcastStatus should not result in system information change notifications in Short Message transmitted with P-RNTI over DCI (see clause 6.5). The value of the indication is valid until the end of the BCCH modification period when set to broadcasting.ENUMERATED {broadcasting, notBroadcasting},si-PeriodicityPeriodicity of the SI-message in radio frames. Value rf8 corresponds to 8 radio frames, value rf16 corresponds to 16 radio frames, and so on.ENUMERATED {rf8, rf16, rf32, rf64, rf128, rf256, rf512}, sib-MappingInfo SIB-Mapping } SIB-Mapping ::= SEQUENCE (SIZE (1..maxSIB)) OF SIB-TypeInfo SIB-TypeInfo ::= SEQUENCE { type ENUMERATED {sibType2, sibType3, sibType4, sibType5, sibType6, sibType7, sibType8, sibType9, sibType10-v1610, sibType11-v1610, sibType12-v1610, sibType13-v1610, sibType14-v1610, spare3, spare2, spare1,... }, valueTag INTEGER (0..31) OPTIONAL, -- Cond SIB-TYPEareaScopeIndicates that a SIB is area specific. If the field is absent, the SIB is cell specific.ENUMERATED {true} OPTIONAL -- Need S } -- TAG-SI-SCHEDULINGINFO-STOP -- ASN1STOP
SchedulingInfo field descriptions |
---|
areaScope Indicates that a SIB is area specific. If the field is absent, the SIB is cell specific. |
si-BroadcastStatus Indicates if the SI message is being broadcasted or not. Change of si-BroadcastStatus should not result in system information change notifications in Short Message transmitted with P-RNTI over DCI (see clause 6.5). The value of the indication is valid until the end of the BCCH modification period when set to broadcasting. |
si-Periodicity Periodicity of the SI-message in radio frames. Value rf8 corresponds to 8 radio frames, value rf16 corresponds to 16 radio frames, and so on. |
SI-SchedulingInfo field descriptions |
---|
si-RequestConfig Configuration of Msg1 resources that the UE uses for requesting SI-messages for which si-BroadcastStatus is set to notBroadcasting. |
si-RequestConfigSUL Configuration of Msg1 resources that the UE uses for requesting SI-messages for which si-BroadcastStatus is set to notBroadcasting. |
si-WindowLength The length of the SI scheduling window. Value s5 corresponds to 5 slots, value s10 corresponds to 10 slots and so on. The network always configures si-WindowLength to be shorter than or equal to the si-Periodicity. |
systemInformationAreaID Indicates the system information area that the cell belongs to, if any. Any SIB with areaScope within the SI is considered to belong to this systemInformationAreaID. The systemInformationAreaID is unique within a PLMN/SNPN. |
Conditional presence | Explanation |
---|---|
MSG-1 | The field is optionally present, Need R, if si-BroadcastStatus is set to notBroadcastingfor any SI-message included in schedulingInfoList. It is absent otherwise. |
SIB-TYPE | The field is mandatory present if the SIB type is different from SIB6, SIB7 or SIB8. For SIB6, SIB7 and SIB8 it is absent. |
SUL-MSG-1 | The field is optionally present, Need R, if supplementaryUplink is configured in ServingCellConfigCommonSIB and if si-BroadcastStatus is set to notBroadcasting for any SI-message included in schedulingInfoList. It is absent otherwise. |
The IE SK-Counter is a counter used upon initial configuration of SN security for NR-DC and NE-DC, as well as upon refresh of S-KgNB or S-KeNB based on the current or newly derived KgNB during RRC Resume or RRC Reconfiguration, as defined in TS 33.501 [11].
The IE SlotFormatCombinationsPerCell is used to configure the SlotFormatCombinations applicable for one serving cell (see TS 38.213 [13], clause 11.1.1).
-- ASN1START -- TAG-SLOTFORMATCOMBINATIONSPERCELL-START SlotFormatCombinationsPerCell ::= SEQUENCE {servingCellIdThe ID of the serving cell for which the slotFormatCombinations are applicable.ServCellIndex,subcarrierSpacingReference subcarrier spacing for this Slot Format Combination. The network configures a value that is smaller than or equal to any SCS of configured BWPs of the serving cell that the command applies to. And the network configures a value that is smaller than or equal to the SCS of the serving cell which the UE monitors for SFI indications (see TS 38.213 [13], clause 11.1.1).SubcarrierSpacing,subcarrierSpacing2Reference subcarrier spacing for a Slot Format Combination on an FDD or SUL cell (see TS 38.213 [13], clause 11.1.1). For FDD, subcarrierSpacing (SFI-scs) is the reference SCS for DL BWP and subcarrierSpacing2 (SFI-scs2) is the reference SCS for UL BWP. For SUL, subcarrierSpacing (SFI-scs) is the reference SCS for non-SUL carrier and subcarrierSpacing2 (SFI-scs2) is the reference SCS for SUL carrier. The network configures a value that is smaller than or equal to any SCS of configured BWPs of the serving cell that the command applies to. And the network configures a value that is smaller than or equal to the SCS of the serving cell which the UE monitors for SFI indications.SubcarrierSpacing OPTIONAL, -- Need RslotFormatCombinationsA list with SlotFormatCombinations. Each SlotFormatCombination comprises of one or more SlotFormats (see TS 38.211 [16], clause 4.3.2). The total number of slotFormats in the slotFormatCombinations list does not exceed 512.SEQUENCE (SIZE (1..maxNrofSlotFormatCombinationsPerSet)) OF SlotFormatCombination OPTIONAL, -- Need MpositionInDCIThe (starting) position (bit) of the slotFormatCombinationId (SFI-Index) for this serving cell (servingCellId) within the DCI payload (see TS 38.213 [13], clause 11.1.1).INTEGER(0..maxSFI-DCI-PayloadSize-1) OPTIONAL, -- Need M ..., [[enableConfiguredUL-r16If configured, the UE is allowed to transmit uplink signals/channels (SRS, PUCCH, CG-PUSCH) in the set of symbols of the slot when the UE does not detect a DCI format 2_0 providing a slot format for the set of symbols (see TS 38.213 [13], 11.1.1).ENUMERATED {enabled} OPTIONAL -- Need R ]] } SlotFormatCombination ::= SEQUENCE {slotFormatCombinationIdThis ID is used in the DCI payload to dynamically select this SlotFormatCombination (see TS 38.213 [13], clause 11.1.1).SlotFormatCombinationId,slotFormatsSlot formats that occur in consecutive slots in time domain order as listed here (see TS 38.213 [13], clause 11.1.1 and TS 38.213 [13], clause 14 for IAB-MT).SEQUENCE (SIZE (1..maxNrofSlotFormatsPerCombination)) OF INTEGER (0..255) } SlotFormatCombinationId ::= INTEGER (0..maxNrofSlotFormatCombinationsPerSet-1) -- TAG-SLOTFORMATCOMBINATIONSPERCELL-STOP -- ASN1STOP
SlotFormatCombination field descriptions |
---|
slotFormatCombinationId This ID is used in the DCI payload to dynamically select this SlotFormatCombination (see TS 38.213 [13], clause 11.1.1). |
slotFormats Slot formats that occur in consecutive slots in time domain order as listed here (see TS 38.213 [13], clause 11.1.1 and TS 38.213 [13], clause 14 for IAB-MT). |
SlotFormatCombinationsPerCell field descriptions |
---|
enableConfiguredUL If configured, the UE is allowed to transmit uplink signals/channels (SRS, PUCCH, CG-PUSCH) in the set of symbols of the slot when the UE does not detect a DCI format 2_0 providing a slot format for the set of symbols (see TS 38.213 [13], 11.1.1). |
positionInDCI The (starting) position (bit) of the slotFormatCombinationId (SFI-Index) for this serving cell (servingCellId) within the DCI payload (see TS 38.213 [13], clause 11.1.1). |
servingCellId The ID of the serving cell for which the slotFormatCombinations are applicable. |
slotFormatCombinations A list with SlotFormatCombinations. Each SlotFormatCombination comprises of one or more SlotFormats (see TS 38.211 [16], clause 4.3.2). The total number of slotFormats in the slotFormatCombinations list does not exceed 512. |
subcarrierSpacing2 Reference subcarrier spacing for a Slot Format Combination on an FDD or SUL cell (see TS 38.213 [13], clause 11.1.1). For FDD, subcarrierSpacing (SFI-scs) is the reference SCS for DL BWP and subcarrierSpacing2 (SFI-scs2) is the reference SCS for UL BWP. For SUL, subcarrierSpacing (SFI-scs) is the reference SCS for non-SUL carrier and subcarrierSpacing2 (SFI-scs2) is the reference SCS for SUL carrier. The network configures a value that is smaller than or equal to any SCS of configured BWPs of the serving cell that the command applies to. And the network configures a value that is smaller than or equal to the SCS of the serving cell which the UE monitors for SFI indications. |
subcarrierSpacing Reference subcarrier spacing for this Slot Format Combination. The network configures a value that is smaller than or equal to any SCS of configured BWPs of the serving cell that the command applies to. And the network configures a value that is smaller than or equal to the SCS of the serving cell which the UE monitors for SFI indications (see TS 38.213 [13], clause 11.1.1). |
The IE SlotFormatIndicator is used to configure monitoring a Group-Common-PDCCH for Slot-Format-Indicators (SFI).
-- ASN1START -- TAG-SLOTFORMATINDICATOR-START SlotFormatIndicator ::= SEQUENCE {sfi-RNTIRNTI used for SFI on the given cell (see TS 38.213 [13], clause 11.1.1).RNTI-Value,dci-PayloadSizeTotal length of the DCI payload scrambled with SFI-RNTI (see TS 38.213 [13], clause 11.1.1).INTEGER (1..maxSFI-DCI-PayloadSize),slotFormatCombToAddModListA list of SlotFormatCombinations for the UE's serving cells (see TS 38.213 [13], clause 11.1.1).SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF SlotFormatCombinationsPerCell OPTIONAL, -- Need N slotFormatCombToReleaseList SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF ServCellIndex OPTIONAL, -- Need N ..., [[availableRB-SetsToAddModList-r16A list of AvailableRB-SetsPerCell objects (see TS 38.213 [13], clause 11.1.1).SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF AvailableRB-SetsPerCell-r16 OPTIONAL, -- Need N availableRB-SetsToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF ServCellIndex OPTIONAL, -- Need N switchTriggerToAddModList-r16 SEQUENCE (SIZE(1..4)) OF SearchSpaceSwitchTrigger-r16 OPTIONAL, -- Need N switchTriggerToReleaseList-r16 SEQUENCE (SIZE(1..4)) OF ServCellIndex OPTIONAL, -- Need Nco-DurationsPerCellToAddModList-r16A list of CO-DurationsPerCell objects. If not configured, the UE uses the slot format indicator (SFI), if available, to determine the channel occupancy duration (see TS 38.213 [13], clause 11.1.1).SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF CO-DurationsPerCell-r16 OPTIONAL, -- Need N co-DurationsPerCellToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroup)) OF ServCellIndex OPTIONAL -- Need N ]], [[ switchTriggerToAddModListSizeExt-r16 SEQUENCE (SIZE(1..maxNrofAggregatedCellsPerCellGroupMinus4-r16)) OF SearchSpaceSwitchTrigger-r16 OPTIONAL, -- Need N switchTriggerToReleaseListSizeExt-r16 SEQUENCE (SIZE(1.. maxNrofAggregatedCellsPerCellGroupMinus4-r16)) OF ServCellIndex OPTIONAL -- Need N ]] } CO-DurationsPerCell-r16 ::= SEQUENCE {servingCellId-r16The ID of the serving cell for which the configuration is applicable or the group of serving cells as indicated by CellGroupsForSwitch-r16 containing this servingCellId.ServCellIndex,positionInDCI-r16The position of the bit within DCI payload containing a search space switching flag (see TS 38.213 [13], clause 11.1.1).INTEGER(0..maxSFI-DCI-PayloadSize-1),subcarrierSpacing-r16Reference subcarrier spacing for the list of Channel Occupancy durations (see TS 38.213 [13], clause 11.1.1).SubcarrierSpacing,co-DurationList-r16A list of Channel Occupancy duration in symbols.SEQUENCE (SIZE(1..64)) OF CO-Duration-r16 } CO-Duration-r16 ::= INTEGER (0..1120) AvailableRB-SetsPerCell-r16 ::= SEQUENCE {servingCellId-r16The ID of the serving cell for which the configuration is applicable or the group of serving cells as indicated by CellGroupsForSwitch-r16 containing this servingCellId.ServCellIndex,positionInDCI-r16The position of the bit within DCI payload containing a search space switching flag (see TS 38.213 [13], clause 11.1.1).INTEGER(0..maxSFI-DCI-PayloadSize-1) } SearchSpaceSwitchTrigger-r16 ::= SEQUENCE {servingCellId-r16The ID of the serving cell for which the configuration is applicable or the group of serving cells as indicated by CellGroupsForSwitch-r16 containing this servingCellId.ServCellIndex,positionInDCI-r16The position of the bit within DCI payload containing a search space switching flag (see TS 38.213 [13], clause 11.1.1).INTEGER(0..maxSFI-DCI-PayloadSize-1) } -- TAG-SLOTFORMATINDICATOR-STOP -- ASN1STOP
SlotFormatIndicator field descriptions |
---|
availableRB-SetsToAddModList A list of AvailableRB-SetsPerCell objects (see TS 38.213 [13], clause 11.1.1). |
co-DurationsPerCellToAddModList A list of CO-DurationsPerCell objects. If not configured, the UE uses the slot format indicator (SFI), if available, to determine the channel occupancy duration (see TS 38.213 [13], clause 11.1.1). |
dci-PayloadSize Total length of the DCI payload scrambled with SFI-RNTI (see TS 38.213 [13], clause 11.1.1). |
sfi-RNTI RNTI used for SFI on the given cell (see TS 38.213 [13], clause 11.1.1). |
slotFormatCombToAddModList A list of SlotFormatCombinations for the UE's serving cells (see TS 38.213 [13], clause 11.1.1). |
switchTriggerToAddModList, switchTriggerToAddModListSizeExt A list of SearchSpaceSwitchTrigger objects. Each SearchSpaceSwitchTrigger object provides position in DCI of the bit field indicating search space switching flag for a serving cell or, if cellGroupsForSwitchList is configured, group of serving cells (see TS 38.213 [13], clause 10.4). If cellGroupsForSwitchList is configured, only one of the cells belonging to the same cell group is added/modified, and the configuration applies to all cells belonging to the cellGroupsForSwitchList (see TS 38.213 [13], clause 10.4).The network configures more than 4 SearchSpaceSwitchTrigger objects only if cellGroupsForSwitchList is not configured. The UE shall consider entries in switchTriggerToAddModList and in switchTriggerToAddModListSizeExt as a single list, i.e. an entry created using switchTriggerToAddModList can be modifed using switchTriggerToAddModListSizeExt and vice-versa. |
switchTriggerToReleaseModList, switchTriggerToReleaseListSizeExt A list of SearchSpaceSwitchTriggers to be released. If cellGroupsForSwitchList is configured, the SearchSpaceSwitchTrigger is released for all serving cells belonging to the same CellGroupForSwitch. The UE shall consider entries in switchTriggerToReleaseList and in switchTriggerToReleaseListSizeExt as a single list, i.e. an entry created using switchTriggerToAddModList or switchTriggerToAddModListSizeExt can be deleted using switchTriggerToReleaseList or switchTriggerToReleaseListSizeExt. |
AvailableRB-SetsPerCell field descriptions |
---|
positionInDCI The (starting) position of the bits within DCI payload indicating the availability of the RB sets of a serving cell (see TS 38.213 [13], clause 11.1.1). |
servingCelIId The ID of the serving cell for which the configuration is applicable. |
CO-DurationsPerCell field descriptions |
---|
co-DurationList A list of Channel Occupancy duration in symbols. |
positionInDCI Position in DCI of the bit field indicating Channel Occupancy duration for UE's serving cells (see TS 38.213 [13], clause 11.1.1). |
servingCelIId The ID of the serving cell for which the configuration is applicable. |
subcarrierSpacing Reference subcarrier spacing for the list of Channel Occupancy durations (see TS 38.213 [13], clause 11.1.1). |
SearchSpaceSwitchTrigger field descriptions |
---|
positionInDCI The position of the bit within DCI payload containing a search space switching flag (see TS 38.213 [13], clause 11.1.1). |
servingCellId The ID of the serving cell for which the configuration is applicable or the group of serving cells as indicated by CellGroupsForSwitch-r16 containing this servingCellId. |
The IE S-NSSAI (Single Network Slice Selection Assistance Information) identifies a Network Slice end to end and comprises a slice/service type and a slice differentiator, see TS 23.003 [21].
-- ASN1START -- TAG-S-NSSAI-START S-NSSAI ::= CHOICE{sstIndicates the S-NSSAI consisting of Slice/Service Type, see TS 23.003 [21].BIT STRING (SIZE (8)),sst-SDIndicates the S-NSSAI consisting of Slice/Service Type and Slice Differentiator, see TS 23.003 [21].BIT STRING (SIZE (32)) } -- TAG-S-NSSAI-STOP -- ASN1STOP
S-NSSAI field descriptions |
---|
sst Indicates the S-NSSAI consisting of Slice/Service Type, see TS 23.003 [21]. |
sst-SD Indicates the S-NSSAI consisting of Slice/Service Type and Slice Differentiator, see TS 23.003 [21]. |
The IE SpeedStateScaleFactors concerns factors, to be applied when the UE is in medium or high speed state, used for scaling a mobility control related parameter.
-- ASN1START -- TAG-SPEEDSTATESCALEFACTORS-START SpeedStateScaleFactors ::= SEQUENCE {sf-MediumThe concerned mobility control related parameter is multiplied with this factor if the UE is in Medium Mobility state as defined in TS 38.304 [20]. Value oDot25 corresponds to 0.25, value oDot5 corresponds to 0.5, value oDot75 corresponds to 0.75, and so on.ENUMERATED {oDot25, oDot5, oDot75, lDot0},sf-HighThe concerned mobility control related parameter is multiplied with this factor if the UE is in High Mobility state as defined in TS 38.304 [20]. Value oDot25 corresponds to 0.25, value oDot5 corresponds to 0.5, oDot75 corresponds to 0.75 and so on.ENUMERATED {oDot25, oDot5, oDot75, lDot0} } -- TAG-SPEEDSTATESCALEFACTORS-STOP -- ASN1STOP
SpeedStateScaleFactors field descriptions |
---|
sf-High The concerned mobility control related parameter is multiplied with this factor if the UE is in High Mobility state as defined in TS 38.304 [20]. Value oDot25 corresponds to 0.25, value oDot5 corresponds to 0.5, oDot75 corresponds to 0.75 and so on. |
sf-Medium The concerned mobility control related parameter is multiplied with this factor if the UE is in Medium Mobility state as defined in TS 38.304 [20]. Value oDot25 corresponds to 0.25, value oDot5 corresponds to 0.5, value oDot75 corresponds to 0.75, and so on. |
The IE SPS-Config is used to configure downlink semi-persistent transmission. Multiple Downlink SPS configurations may be configured in one BWP of a serving cell.
-- ASN1START -- TAG-SPS-CONFIG-START SPS-Config ::= SEQUENCE {periodicityPeriodicity for DL SPS (see TS 38.214 [19] and TS 38.321 [3], clause 5.8.1).ENUMERATED {ms10, ms20, ms32, ms40, ms64, ms80, ms128, ms160, ms320, ms640, spare6, spare5, spare4, spare3, spare2, spare1},nrofHARQ-ProcessesNumber of configured HARQ processes for SPS DL (see TS 38.321 [3], clause 5.8.1).INTEGER (1..8),n1PUCCH-ANHARQ resource for PUCCH for DL SPS. The network configures the resource either as format0 or format1. The actual PUCCH-Resource is configured in PUCCH-Config and referred to by its ID. See TS 38.213 [13], clause 9.2.3.PUCCH-ResourceId OPTIONAL, -- Need Mmcs-TableIndicates the MCS table the UE shall use for DL SPS (see TS 38.214 [19],clause 5.1.3.1. If present, the UE shall use the MCS table of low-SE 64QAM table indicated in Table 5.1.3.1-3 of TS 38.214 [19]. If this field is absent and field mcs-table in PDSCH-Config is set to 'qam256' and the activating DCI is of format 1_1, the UE applies the 256QAM table indicated in Table 5.1.3.1-2 of TS 38.214 [19]. Otherwise, the UE applies the non-low-SE 64QAM table indicated in Table 5.1.3.1-1 of TS 38.214 [19].ENUMERATED {qam64LowSE} OPTIONAL, -- Need S ..., [[sps-ConfigIndex-r16Indicates the index of one of multiple SPS configurations.SPS-ConfigIndex-r16 OPTIONAL, -- Cond SPS-Listharq-ProcID-Offset-r16Indicates the offset used in deriving the HARQ process IDs, see TS 38.321 [3], clause 5.3.1.INTEGER (0..15) OPTIONAL, -- Need RperiodicityExt-r16This field is used to calculate the periodicity for DL SPS (see TS 38.214 [19] and see TS 38.321 [3], clause 5.8.1). If this field is present, the field periodicity is ignored. The following periodicities are supported depending on the configured subcarrier spacing [ms]: 15 kHz:periodicityExt, where periodicityExt has a value between 1 and 640. 30 kHz:0.5 x periodicityExt, where periodicityExt has a value between 1 and 1280. 60 kHz with normal CP.0.25 x periodicityExt, where periodicityExt has a value between 1 and 2560. 60 kHz with ECP:0.25 x periodicityExt, where periodicityExt has a value between 1 and 2560. 120 kHz:0.125 x periodicityExt, where periodicityExt has a value between 1 and 5120.INTEGER (1..5120) OPTIONAL, -- Need Rharq-CodebookID-r16Indicates the HARQ-ACK codebook index for the corresponding HARQ-ACK codebook for SPS PDSCH and ACK for SPS PDSCH release.INTEGER (1..2) OPTIONAL, -- Need Rpdsch-AggregationFactor-r16Number of repetitions for SPS PDSCH (see TS 38.214 [19], clause 5.1.2.1). When the field is absent, the UE applies PDSCH aggregation factor of PDSCH-Config.ENUMERATED {n1, n2, n4, n8 } OPTIONAL -- Need S ]] } -- TAG-SPS-CONFIG-STOP -- ASN1STOP
SPS-Config field descriptions |
---|
harq-CodebookID Indicates the HARQ-ACK codebook index for the corresponding HARQ-ACK codebook for SPS PDSCH and ACK for SPS PDSCH release. |
harq-ProcID-Offset Indicates the offset used in deriving the HARQ process IDs, see TS 38.321 [3], clause 5.3.1. |
mcs-Table Indicates the MCS table the UE shall use for DL SPS (see TS 38.214 [19],clause 5.1.3.1. If present, the UE shall use the MCS table of low-SE 64QAM table indicated in Table 5.1.3.1-3 of TS 38.214 [19]. If this field is absent and field mcs-table in PDSCH-Config is set to 'qam256' and the activating DCI is of format 1_1, the UE applies the 256QAM table indicated in Table 5.1.3.1-2 of TS 38.214 [19]. Otherwise, the UE applies the non-low-SE 64QAM table indicated in Table 5.1.3.1-1 of TS 38.214 [19]. |
n1PUCCH-AN HARQ resource for PUCCH for DL SPS. The network configures the resource either as format0 or format1. The actual PUCCH-Resource is configured in PUCCH-Config and referred to by its ID. See TS 38.213 [13], clause 9.2.3. |
nrofHARQ-Processes Number of configured HARQ processes for SPS DL (see TS 38.321 [3], clause 5.8.1). |
pdsch-AggregationFactor Number of repetitions for SPS PDSCH (see TS 38.214 [19], clause 5.1.2.1). When the field is absent, the UE applies PDSCH aggregation factor of PDSCH-Config. |
periodicity Periodicity for DL SPS (see TS 38.214 [19] and TS 38.321 [3], clause 5.8.1). |
periodicityExt This field is used to calculate the periodicity for DL SPS (see TS 38.214 [19] and see TS 38.321 [3], clause 5.8.1). If this field is present, the field periodicity is ignored. The following periodicities are supported depending on the configured subcarrier spacing [ms]: 15 kHz:periodicityExt, where periodicityExt has a value between 1 and 640. 30 kHz:0.5 x periodicityExt, where periodicityExt has a value between 1 and 1280. 60 kHz with normal CP.0.25 x periodicityExt, where periodicityExt has a value between 1 and 2560. 60 kHz with ECP:0.25 x periodicityExt, where periodicityExt has a value between 1 and 2560. 120 kHz:0.125 x periodicityExt, where periodicityExt has a value between 1 and 5120. |
sps-ConfigIndex Indicates the index of one of multiple SPS configurations. |
Conditional Presence | Explanation |
---|---|
SPS-List | The field is mandatory present when included in sps-ConfigToAddModList-r16, otherwise the field is absent. |
The IE SPS-ConfigIndex is used to indicate the index of one of multiple DL SPS configurations in one BWP.
The IE SPS-PUCCH-AN is used to indicate a PUCCH resource for HARQ ACK and configure the corresponding maximum payload size for the PUCCH resource.
-- ASN1START -- TAG-SPS-PUCCH-AN-START SPS-PUCCH-AN-r16 ::= SEQUENCE {sps-PUCCH-AN-ResourceID-r16Indicates the PUCCH resource IDPUCCH-ResourceId,maxPayloadSize-r16Indicates the maximum payload size for the corresponding PUCCH resource ID.INTEGER (4..256) OPTIONAL -- Need R } -- TAG-SPS-PUCCH-AN-STOP -- ASN1STOP
SPS-PUCCH-AN field descriptions |
---|
maxPayloadSize Indicates the maximum payload size for the corresponding PUCCH resource ID. |
sps-PUCCH-AN-ResourceID Indicates the PUCCH resource ID |
The IE SPS-PUCCH-AN-List is used to configure the list of PUCCH resources per HARQ ACK codebook
-- ASN1START -- TAG-SPS-PUCCH-AN-LIST-START SPS-PUCCH-AN-List-r16 ::= SEQUENCE (SIZE(1..4)) OF SPS-PUCCH-AN-r16 -- TAG-SPS-PUCCH-AN-LIST-STOP -- ASN1STOP
The IE SRB-Identity is used to identify a Signalling Radio Bearer (SRB) used by a UE.
The IE SRS-CarrierSwitching is used to configure for SRS carrier switching when PUSCH is not configured and independent SRS power control from that of PUSCH.
-- ASN1START -- TAG-SRS-CARRIERSWITCHING-START SRS-CarrierSwitching ::= SEQUENCE {srs-SwitchFromServCellIndexIndicates the serving cell whose UL transmission may be interrupted during SRS transmission on a PUSCH-less SCell. During SRS transmission on a PUSCH-less SCell, the UE may temporarily suspend the UL transmission on a serving cell with PUSCH in the same CG to allow the PUSCH-less SCell to transmit SRS. (see TS 38.214 [19], clause 6.2.1.3).INTEGER (0..31) OPTIONAL, -- Need M srs-SwitchFromCarrier ENUMERATED {sUL, nUL},srs-TPC-PDCCH-GroupNetwork configures the UE with either typeA-SRS-TPC-PDCCH-Group or typeB-SRS-TPC-PDCCH-Group, if any.CHOICE {typeAType A trigger configuration for SRS transmission on a PUSCH-less SCell (see TS 38.213 [13], clause 11.4). In this release, the network configures at most one entry (the first entry) of typeA, and the first entry corresponds to the serving cell in which the SRS-CarrierSwitching field is configured. SRS carrier switching to SUL carrier is not supported in this version of the specification.SEQUENCE (SIZE (1..32)) OF SRS-TPC-PDCCH-Config,typeBType B trigger configuration for SRS transmission on a PUSCH-less SCell (see TS 38.213 [13], clause 11.4).SRS-TPC-PDCCH-Config } OPTIONAL, -- Need MmonitoringCellsA set of serving cells for monitoring PDCCH conveying SRS DCI format with CRC scrambled by TPC-SRS-RNTI (see TS 38.212 [17], TS 38.213 [13], clause 7.3.1, 11.3).SEQUENCE (SIZE (1..maxNrofServingCells)) OF ServCellIndex OPTIONAL, -- Need M ... } SRS-TPC-PDCCH-Config ::= SEQUENCE {srs-CC-SetIndexlistA list of pairs of [cc-SetIndex; cc-IndexInOneCC-Set] (see TS 38.212 [17], TS 38.213 [13], clause 7.3.1, 11.4). The network does not configure this field for typeB.SEQUENCE (SIZE(1..4)) OF SRS-CC-SetIndex OPTIONAL -- Need M } SRS-CC-SetIndex ::= SEQUENCE {cc-SetIndexIndicates the CC set index for Type A associated (see TS 38.212 [17], TS 38.213 [13], clause 7.3.1, 11.4). The network always includes this field when the srs-TPC-PDCCH-Group is set to typeA. The network does not configure this field to 3 in this release of specification.INTEGER (0..3) OPTIONAL, -- Need Mcc-IndexInOneCC-SetIndicates the CC index in one CC set for Type A (see TS 38.212 [17], TS 38.213 [13], clause 7.3.1, 11.4). The network always includes this field when the srs-TPC-PDCCH-Group is set to typeA.INTEGER (0..7) OPTIONAL -- Need M } -- TAG-SRS-CARRIERSWITCHING-STOP -- ASN1STOP
SRS-CC-SetIndex field descriptions |
---|
cc-IndexInOneCC-Set Indicates the CC index in one CC set for Type A (see TS 38.212 [17], TS 38.213 [13], clause 7.3.1, 11.4). The network always includes this field when the srs-TPC-PDCCH-Group is set to typeA. |
cc-SetIndex Indicates the CC set index for Type A associated (see TS 38.212 [17], TS 38.213 [13], clause 7.3.1, 11.4). The network always includes this field when the srs-TPC-PDCCH-Group is set to typeA. The network does not configure this field to 3 in this release of specification. |
SRS-CarrierSwitching field descriptions |
---|
monitoringCells A set of serving cells for monitoring PDCCH conveying SRS DCI format with CRC scrambled by TPC-SRS-RNTI (see TS 38.212 [17], TS 38.213 [13], clause 7.3.1, 11.3). |
srs-SwitchFromServCellIndex Indicates the serving cell whose UL transmission may be interrupted during SRS transmission on a PUSCH-less SCell. During SRS transmission on a PUSCH-less SCell, the UE may temporarily suspend the UL transmission on a serving cell with PUSCH in the same CG to allow the PUSCH-less SCell to transmit SRS. (see TS 38.214 [19], clause 6.2.1.3). |
srs-TPC-PDCCH-Group Network configures the UE with either typeA-SRS-TPC-PDCCH-Group or typeB-SRS-TPC-PDCCH-Group, if any. |
typeA Type A trigger configuration for SRS transmission on a PUSCH-less SCell (see TS 38.213 [13], clause 11.4). In this release, the network configures at most one entry (the first entry) of typeA, and the first entry corresponds to the serving cell in which the SRS-CarrierSwitching field is configured. SRS carrier switching to SUL carrier is not supported in this version of the specification. |
typeB Type B trigger configuration for SRS transmission on a PUSCH-less SCell (see TS 38.213 [13], clause 11.4). |
SRS-TPC-PDCCH-Config field descriptions |
---|
srs-CC-SetIndexlist A list of pairs of [cc-SetIndex; cc-IndexInOneCC-Set] (see TS 38.212 [17], TS 38.213 [13], clause 7.3.1, 11.4). The network does not configure this field for typeB. |
The IE SRS-Config is used to configure sounding reference signal transmissions. The configuration defines a list of SRS-Resources, a list of SRS-PosResources, a list of SRS-PosResourceSets and a list of SRS-ResourceSets. Each resource set defines a set of SRS-Resources or SRS-PosResources. The network triggers the transmission of the set of SRS-Resources or SRS-PosResources using a configured aperiodicSRS-ResourceTrigger (L1 DCI).
-- ASN1START -- TAG-SRS-CONFIG-START SRS-Config ::= SEQUENCE { srs-ResourceSetToReleaseList SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSetId OPTIONAL, -- Need N srs-ResourceSetToAddModList SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSet OPTIONAL, -- Need N srs-ResourceToReleaseList SEQUENCE (SIZE(1..maxNrofSRS-Resources)) OF SRS-ResourceId OPTIONAL, -- Need N srs-ResourceToAddModList SEQUENCE (SIZE(1..maxNrofSRS-Resources)) OF SRS-Resource OPTIONAL, -- Need Ntpc-AccumulationIf the field is absent, UE applies TPC commands via accumulation. If disabled, UE applies the TPC command without accumulation (this applies to SRS when a separate closed loop is configured for SRS) (see TS 38.213 [13], clause 7.3).ENUMERATED {disabled} OPTIONAL, -- Need S ..., [[srs-RequestDCI-1-2-r16Indicate the number of bits for "SRS request" in DCI format 1_2. When the field is absent, then the value of 0 bit for "SRS request" in DCI format 1_2 is applied. When the UE is configured with supplementaryUplink, an extra bit (the first bit of the SRS request field) is used for the non-SUL/SUL indication (see TS 38.214 [19], clause 6.1.1.2).INTEGER (1..2) OPTIONAL, -- Need Ssrs-RequestDCI-0-2-r16Indicate the number of bits for "SRS request"in DCI format 0_2. When the field is absent, then the value of 0 bit for "SRS request" in DCI format 0_2 is applied. If the parameter srs-RequestDCI-0-2 is configured to value 1, 1 bit is used to indicate one of the first two rows of Table 7.3.1.1.2-24 in TS 38.212 [17] for triggered aperiodic SRS resource set. If the value 2 is configured, 2 bits are used to indicate one of the rows of Table 7.3.1.1.2-24 in TS 38.212 [17]. When UE is configured with supplementaryUplink, an extra bit (the first bit of the SRS request field) is used for the non-SUL/SUL indication.INTEGER (1..2) OPTIONAL, -- Need Ssrs-ResourceSetToAddModListDCI-0-2-r16List of SRS resource set to be added or modified for DCI format 0_2 (see TS 38.212 [17], clause 7.3.1).SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSet OPTIONAL, -- Need Nsrs-ResourceSetToReleaseListDCI-0-2-r16List of SRS resource set to be released for DCI format 0_2 (see TS 38.212 [17], clause 7.3.1).SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSetId OPTIONAL, -- Need N srs-PosResourceSetToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResourceSets-r16)) OF SRS-PosResourceSetId-r16 OPTIONAL, -- Need N srs-PosResourceSetToAddModList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResourceSets-r16)) OF SRS-PosResourceSet-r16 OPTIONAL,-- Need N srs-PosResourceToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResources-r16)) OF SRS-PosResourceId-r16 OPTIONAL,-- Need N srs-PosResourceToAddModList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResources-r16)) OF SRS-PosResource-r16 OPTIONAL -- Need N ]] } SRS-ResourceSet ::= SEQUENCE { srs-ResourceSetId SRS-ResourceSetId, srs-ResourceIdList SEQUENCE (SIZE(1..maxNrofSRS-ResourcesPerSet)) OF SRS-ResourceId OPTIONAL, -- Cond SetupresourceTypeTime domain behavior of SRS resource configuration, see TS 38.214 [19], clause 6.2.1. The network configures SRS resources in the same resource set with the same time domain behavior on periodic, aperiodic and semi-persistent SRS.CHOICE { aperiodic SEQUENCE {aperiodicSRS-ResourceTriggerThe DCI "code point" upon which the UE shall transmit SRS according to this SRS resource set configuration (see TS 38.214 [19], clause 6).INTEGER (1..maxNrofSRS-TriggerStates-1),csi-RSID of CSI-RS resource associated with this SRS resource set. (see TS 38.214 [19], clause 6.1.1.2).NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebookslotOffsetAn offset in number of slots between the triggering DCI and the actual transmission of this SRS-ResourceSet. If the field is absent the UE applies no offset (value 0).INTEGER (1..32) OPTIONAL, -- Need S ..., [[aperiodicSRS-ResourceTriggerListAn additional list of DCI "code points" upon which the UE shall transmit SRS according to this SRS resource set configuration (see TS 38.214 [19], clause 6). When the field is not included during a reconfiguration of SRS-ResourceSet of resourceType set to aperiodic, UE maintains this value based on the Need M; that is, this list is not considered as an extension of aperiodicSRS-ResourceTrigger for purpose of applying the general rule for extended list in clause 6.1.3.SEQUENCE (SIZE(1..maxNrofSRS-TriggerStates-2)) OF INTEGER (1..maxNrofSRS-TriggerStates-1) OPTIONAL -- Need M ]] }, semi-persistent SEQUENCE {associatedCSI-RSID of CSI-RS resource associated with this SRS resource set in non-codebook based operation (see TS 38.214 [19], clause 6.1.1.2).NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook ... }, periodic SEQUENCE {associatedCSI-RSID of CSI-RS resource associated with this SRS resource set in non-codebook based operation (see TS 38.214 [19], clause 6.1.1.2).NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook ... } },usageIndicates if the SRS resource set is used for beam management, codebook based or non-codebook based transmission or antenna switching. See TS 38.214 [19], clause 6.2.1. Reconfiguration between codebook based and non-codebook based transmission is not supported.ENUMERATED {beamManagement, codebook, nonCodebook, antennaSwitching},alphaalpha value for SRS power control (see TS 38.213 [13], clause 7.3). When the field is absent the UE applies the value 1.Alpha OPTIONAL, -- Need Sp0P0 value for SRS power control. The value is in dBm. Only even values (step size 2) are allowed (see TS 38.213 [13], clause 7.3).INTEGER (-202..24) OPTIONAL, -- Cond SetuppathlossReferenceRSA reference signal (e.g. a CSI-RS config or a SS block) to be used for SRS path loss estimation (see TS 38.213 [13], clause 7.3).PathlossReferenceRS-Config OPTIONAL, -- Need Msrs-PowerControlAdjustmentStatesIndicates whether hsrs,c(i) = fc(i,1) or hsrs,c(i) = fc(i,2) (if twoPUSCH-PC-AdjustmentStates are configured) or separate close loop is configured for SRS. This parameter is applicable only for Uls on which UE also transmits PUSCH. If absent or release, the UE applies the value sameAs-Fci1 (see TS 38.213 [13], clause 7.3).ENUMERATED { sameAsFci2, separateClosedLoop} OPTIONAL, -- Need S ..., [[pathlossReferenceRSList-r16Multiple candidate pathloss reference RS(s) for SRS power control, where one candidate RS can be mapped to SRS Resource Set via MAC CE (clause 6.1.3.27 in TS 38.321 [3]). The network can only configure this field if pathlossReferenceRS is not configured in the same SRS-ResourceSet.SetupRelease { PathlossReferenceRSList-r16} OPTIONAL -- Need M ]] } PathlossReferenceRS-Config ::= CHOICE { ssb-Index SSB-Index, csi-RS-Index NZP-CSI-RS-ResourceId } PathlossReferenceRSList-r16 ::= SEQUENCE (SIZE (1..maxNrofSRS-PathlossReferenceRS-r16)) OF PathlossReferenceRS-r16 PathlossReferenceRS-r16 ::= SEQUENCE { srs-PathlossReferenceRS-Id-r16 SRS-PathlossReferenceRS-Id-r16,pathlossReferenceRS-r16A reference signal (e.g. a CSI-RS config or a SS block) to be used for SRS path loss estimation (see TS 38.213 [13], clause 7.3).PathlossReferenceRS-Config } SRS-PathlossReferenceRS-Id-r16 ::= INTEGER (0..maxNrofSRS-PathlossReferenceRS-1-r16) SRS-PosResourceSet-r16 ::= SEQUENCE { srs-PosResourceSetId-r16 SRS-PosResourceSetId-r16, srs-PosResourceIdList-r16 SEQUENCE (SIZE(1..maxNrofSRS-ResourcesPerSet)) OF SRS-PosResourceId-r16 OPTIONAL, -- Cond SetupresourceType-r16Time domain behavior of SRS resource configuration, see TS 38.214 [19], clause 6.2.1. The network configures SRS resources in the same resource set with the same time domain behavior on periodic, aperiodic and semi-persistent SRS.CHOICE { aperiodic-r16 SEQUENCE {aperiodicSRS-ResourceTriggerList-r16An additional list of DCI "code points" upon which the UE shall transmit SRS according to this SRS resource set configuration (see TS 38.214 [19], clause 6). When the field is not included during a reconfiguration of SRS-ResourceSet of resourceType set to aperiodic, UE maintains this value based on the Need M; that is, this list is not considered as an extension of aperiodicSRS-ResourceTrigger for purpose of applying the general rule for extended list in clause 6.1.3.SEQUENCE (SIZE(1..maxNrofSRS-TriggerStates-1)) OF INTEGER (1..maxNrofSRS-TriggerStates-1) OPTIONAL, -- Need M ... }, semi-persistent-r16 SEQUENCE { ... }, periodic-r16 SEQUENCE { ... } },alpha-r16alpha value for SRS power control (see TS 38.213 [13], clause 7.3). When the field is absent the UE applies the value 1.Alpha OPTIONAL, -- Need Sp0-r16P0 value for SRS power control. The value is in dBm. Only even values (step size 2) are allowed (see TS 38.213 [13], clause 7.3).INTEGER (-202..24) OPTIONAL, -- Cond SetuppathlossReferenceRS-Pos-r16A reference signal (e.g. a SS block or a DL-PRS config) to be used for SRS path loss estimation (see TS 38.213 [13], clause 7.3).CHOICE {ssb-IndexServing-r16Indicates SSB index belonging to a serving cell.SSB-Index,ssb-Ncell-r16This field indicates a SSB configuration from neighboring cell.SSB-InfoNcell-r16,dl-PRS-r16This field indicates a PRS configuration.DL-PRS-Info-r16 } OPTIONAL, -- Need M ... } SRS-ResourceSetId ::= INTEGER (0..maxNrofSRS-ResourceSets-1) SRS-PosResourceSetId-r16 ::= INTEGER (0..maxNrofSRS-PosResourceSets-1-r16) SRS-Resource ::= SEQUENCE { srs-ResourceId SRS-ResourceId,nrofSRS-PortsNumber of ports. For CLI SRS-RSRP measurement, the network always configures this parameter to 'port1'.ENUMERATED {port1, ports2, ports4},ptrs-PortIndexThe PTRS port index for this SRS resource for non-codebook based UL MIMO. This is only applicable when the corresponding PTRS-UplinkConfig is set to CP-OFDM. The ptrs-PortIndex configured here must be smaller than the maxNrofPorts configured in the PTRS-UplinkConfig (see TS 38.214 [19], clause 6.2.3.1). This parameter is not applicable to CLI SRS-RSRP measurement.ENUMERATED {n0, n1 } OPTIONAL, -- Need RtransmissionCombComb value (2 or 4 or 8) and comb offset (0..combValue-1) (see TS 38.214 [19], clause 6.2.1).CHOICE { n2 SEQUENCE { combOffset-n2 INTEGER (0..1),cyclicShift-n2Cyclic shift configuration (see TS 38.214 [19], clause 6.2.1).INTEGER (0..7) }, n4 SEQUENCE { combOffset-n4 INTEGER (0..3),cyclicShift-n4Cyclic shift configuration (see TS 38.214 [19], clause 6.2.1).INTEGER (0..11) } },resourceMappingOFDM symbol location of the SRS resource within a slot including nrofSymbols (number of OFDM symbols), startPosition (value 0 refers to the last symbol, value 1 refers to the second last symbol, and so on) and repetitionFactor (see TS 38.214 [19], clause 6.2.1 and TS 38.211 [16], clause 6.4.1.4). The configured SRS resource does not exceed the slot boundary. If resourceMapping-r16 is signalled, UE shall ignore the resourceMapping (without suffix). For CLI SRS-RSRP measurement, the network always configures nrofSymbols and repetitionFactor to 'n1'.SEQUENCE { startPosition INTEGER (0..5), nrofSymbols ENUMERATED {n1, n2, n4}, repetitionFactor ENUMERATED {n1, n2, n4} }, freqDomainPosition INTEGER (0..67), freqDomainShift INTEGER (0..268),freqHoppingIncludes parameters capturing SRS frequency hopping (see TS 38.214 [19], clause 6.2.1). For CLI SRS-RSRP measurement, the network always configures this field such that b-hop > b-SRS.SEQUENCE { c-SRS INTEGER (0..63), b-SRS INTEGER (0..3), b-hop INTEGER (0..3) },groupOrSequenceHoppingParameter(s) for configuring group or sequence hopping (see TS 38.211 [16], clause 6.4.1.4.2). For CLI SRS-RSRP measurement, the network always configures this parameter to 'neither'.ENUMERATED { neither, groupHopping, sequenceHopping },resourceTypeTime domain behavior of SRS resource configuration, see TS 38.214 [19], clause 6.2.1. The network configures SRS resources in the same resource set with the same time domain behavior on periodic, aperiodic and semi-persistent SRS.CHOICE { aperiodic SEQUENCE { ... }, semi-persistent SEQUENCE { periodicityAndOffset-sp SRS-PeriodicityAndOffset, ... }, periodic SEQUENCE { periodicityAndOffset-p SRS-PeriodicityAndOffset, ... } },sequenceIdSequence ID used to initialize pseudo random group and sequence hopping (see TS 38.214 [19], clause 6.2.1).INTEGER (0..1023),spatialRelationInfoConfiguration of the spatial relation between a reference RS and the target SRS. Reference RS can be SSB/CSI-RS/SRS (see TS 38.214 [19], clause 6.2.1). This parameter is not applicable to CLI SRS-RSRP measurement.SRS-SpatialRelationInfo OPTIONAL, -- Need R ..., [[resourceMapping-r16OFDM symbol location of the SRS resource within a slot including nrofSymbols (number of OFDM symbols), startPosition (value 0 refers to the last symbol, value 1 refers to the second last symbol, and so on) and repetitionFactor (see TS 38.214 [19], clause 6.2.1 and TS 38.211 [16], clause 6.4.1.4). The configured SRS resource does not exceed the slot boundary. If resourceMapping-r16 is signalled, UE shall ignore the resourceMapping (without suffix). For CLI SRS-RSRP measurement, the network always configures nrofSymbols and repetitionFactor to 'n1'.SEQUENCE { startPosition-r16 INTEGER (0..13), nrofSymbols-r16 ENUMERATED {n1, n2, n4}, repetitionFactor-r16 ENUMERATED {n1, n2, n4} } OPTIONAL -- Need R ]] } SRS-PosResource-r16::= SEQUENCE { srs-PosResourceId-r16 SRS-PosResourceId-r16,transmissionComb-r16Comb value (2 or 4 or 8) and comb offset (0..combValue-1) (see TS 38.214 [19], clause 6.2.1).CHOICE { n2-r16 SEQUENCE { combOffset-n2-r16 INTEGER (0..1),cyclicShift-n2-r16Cyclic shift configuration (see TS 38.214 [19], clause 6.2.1).INTEGER (0..7) }, n4-r16 SEQUENCE { combOffset-n4-r16 INTEGER (0..3),cyclicShift-n4-r16Cyclic shift configuration (see TS 38.214 [19], clause 6.2.1).INTEGER (0..11) }, n8-r16 SEQUENCE { combOffset-n8-r16 INTEGER (0..7),cyclicShift-n8-r16Cyclic shift configuration (see TS 38.214 [19], clause 6.2.1).INTEGER (0..5) }, ... },resourceMapping-r16OFDM symbol location of the SRS resource within a slot including nrofSymbols (number of OFDM symbols), startPosition (value 0 refers to the last symbol, value 1 refers to the second last symbol, and so on) and repetitionFactor (see TS 38.214 [19], clause 6.2.1 and TS 38.211 [16], clause 6.4.1.4). The configured SRS resource does not exceed the slot boundary. If resourceMapping-r16 is signalled, UE shall ignore the resourceMapping (without suffix). For CLI SRS-RSRP measurement, the network always configures nrofSymbols and repetitionFactor to 'n1'.SEQUENCE { startPosition-r16 INTEGER (0..13), nrofSymbols-r16 ENUMERATED {n1, n2, n4, n8, n12} }, freqDomainShift-r16 INTEGER (0..268),freqHopping-r16Includes parameters capturing SRS frequency hopping (see TS 38.214 [19], clause 6.2.1). For CLI SRS-RSRP measurement, the network always configures this field such that b-hop > b-SRS.SEQUENCE { c-SRS-r16 INTEGER (0..63), ... },groupOrSequenceHopping-r16Parameter(s) for configuring group or sequence hopping (see TS 38.211 [16], clause 6.4.1.4.2). For CLI SRS-RSRP measurement, the network always configures this parameter to 'neither'.ENUMERATED { neither, groupHopping, sequenceHopping },resourceType-r16Time domain behavior of SRS resource configuration, see TS 38.214 [19], clause 6.2.1. The network configures SRS resources in the same resource set with the same time domain behavior on periodic, aperiodic and semi-persistent SRS.CHOICE { aperiodic-r16 SEQUENCE {slotOffset-r16An offset in number of slots between the triggering DCI and the actual transmission of this SRS-ResourceSet. If the field is absent the UE applies no offset (value 0).INTEGER (1..32) OPTIONAL, -- Need S ... }, semi-persistent-r16 SEQUENCE { periodicityAndOffset-sp-r16 SRS-PeriodicityAndOffset-r16, ..., [[ periodicityAndOffset-sp-Ext-r16 SRS-PeriodicityAndOffsetExt-r16 OPTIONAL -- Need R ]] }, periodic-r16 SEQUENCE { periodicityAndOffset-p-r16 SRS-PeriodicityAndOffset-r16, ..., [[ periodicityAndOffset-p-Ext-r16 SRS-PeriodicityAndOffsetExt-r16 OPTIONAL -- Need R ]] } },sequenceId-r16Sequence ID used to initialize pseudo random group and sequence hopping (see TS 38.214 [19], clause 6.2.1).INTEGER (0..65535),spatialRelationInfoPos-r16Configuration of the spatial relation between a reference RS and the target SRS. Reference RS can be SSB/CSI-RS/SRS/DL-PRS (see TS 38.214 [19], clause 6.2.1). If the IE srs-ResourceId-Ext is present, the IE srs-ResourceId in spatialRelationInfoPos represents the index from 0 to 63. Otherwise the IE srs-ResourceId in spatialRelationInfoPos represents the index from 0 to 31.SRS-SpatialRelationInfoPos-r16 OPTIONAL, -- Need R ... } SRS-SpatialRelationInfo ::= SEQUENCE {servingCellIdThe serving Cell ID of the source SSB, CSI-RS, or SRS for the spatial relation of the target SRS resource. If this field is absent the SSB, the CSI-RS, or the SRS is from the same serving cell where the SRS is configured.ServCellIndex OPTIONAL, -- Need S referenceSignal CHOICE { ssb-Index SSB-Index, csi-RS-Index NZP-CSI-RS-ResourceId, srs SEQUENCE { resourceId SRS-ResourceId, uplinkBWP BWP-Id } } } SRS-SpatialRelationInfoPos-r16 ::= CHOICE { servingRS-r16 SEQUENCE {servingCellIdThe serving Cell ID of the source SSB, CSI-RS, or SRS for the spatial relation of the target SRS resource. If this field is absent the SSB, the CSI-RS, or the SRS is from the same serving cell where the SRS is configured.ServCellIndex OPTIONAL, -- Need S referenceSignal-r16 CHOICE {ssb-IndexServing-r16Indicates SSB index belonging to a serving cell.SSB-Index,csi-RS-IndexServing-r16Indicates CSI-RS index belonging to a serving cell.NZP-CSI-RS-ResourceId, srs-SpatialRelation-r16 SEQUENCE {resourceSelection-r16Indicates whether the configured SRS spatial relation resource is a SRS-Resource or SRS-PosResource.CHOICE { srs-ResourceId-r16 SRS-ResourceId, srs-PosResourceId-r16 SRS-PosResourceId-r16 }, uplinkBWP-r16 BWP-Id } } },ssb-Ncell-r16This field indicates a SSB configuration from neighboring cell.SSB-InfoNcell-r16,dl-PRS-r16This field indicates a PRS configuration.DL-PRS-Info-r16 } SSB-Configuration-r16 ::= SEQUENCE {ssb-Freq-r16Indicates the frequency of the SSB.ARFCN-ValueNR,halfFrameIndex-r16Indicates whether SSB is in the first half or the second half of the frame.Value zero indicates the first half and value 1 indicates the second half.ENUMERATED {zero, one},ssbSubcarrierSpacing-r16Subcarrier spacing of SSB. Only the values 15 kHz or 30 kHz (FR1), and 120 kHz or 240 kHz (FR2) are applicable.SubcarrierSpacing,ssb-Periodicity-r16Indicates the periodicity of the SSB. If the field is absent, the UE applies the value ms5. (see TS 38.213 [13], clause 4.1)ENUMERATED { ms5, ms10, ms20, ms40, ms80, ms160, spare2,spare1 } OPTIONAL, -- Need Ssfn0-Offset-r16Indiactes the time offset of the SFN0 slot 0 for the cell with respect to SFN0 slot 0 of serving cell.SEQUENCE {sfn-Offset-r16Specifies the SFN offsetbetween the cell in which SSB is transmited and serving cell.The offset corresponds to the number of full radio frames counted from the beginning of a radio frame #0 of serving cell to the beginning of the closest subsequent radio frame #0 of the cell in which SSB is transmitted.INTEGER (0..1023),integerSubframeOffset-r16Indicates the subframe boundary offset of the cell in which SSB is transmited.INTEGER (0..9) OPTIONAL -- Need R } OPTIONAL, -- Need Rsfn-SSB-Offset-r16Indicates the SFN offset of the transmitted SSB relative to the start of the SSB period. Value 0 indicates that the SSB is transmitted in the first system frame, value 1 indicates that SSB is transmitted in the second system frame and so on. The network configures this field according to the field ssb-Periodicity such that the indicated system frame does not exceed the configured SSB periodicity.INTEGER (0..15),ss-PBCH-BlockPower-r16Average EPRE of the resources elements that carry secondary synchronization signals in dBm that the NW used for SSB transmission, see TS 38.213 [13], clause 7.INTEGER (-60..50) OPTIONAL -- Cond Pathloss } SSB-InfoNcell-r16 ::= SEQUENCE {physicalCellId-r16This field specifies the physical cell ID of the neighbour cell for which SSB configuration is provided.PhysCellId,ssb-IndexNcell-r16This field specifies the index of the SSB for a neighbour cell. See TS 38.213 [13]. If this field is absent, the UE determines the ssb-IndexNcell of the physicalCellId based on its SSB measurement from the cell.SSB-Index OPTIONAL, -- Need Sssb-Configuration-r16This field specifies the full configuration of the SSB. If this field is absent, the UE obtains the configuration for the SSB from nr-SSB-Config received as part of DL-PRS assistance data in LPP, see TS 37.355 [49], by looking up the corresponding SSB configuration using the field physicalCellId.SSB-Configuration-r16 OPTIONAL -- Need S } DL-PRS-Info-r16 ::= SEQUENCE {dl-PRS-ID-r16This field specifies the UE specific TRP ID (see TS 37.355 [49]) for which PRS configuration is provided.INTEGER (0..255),dl-PRS-ResourceSetId-r16This field specifies the PRS-ResourceSet ID of a PRS resourceSet.INTEGER (0..7),dl-PRS-ResourceId-r16This field specifies the PRS-Resource ID of a PRS resource. If this field is absent, the UE determines the dl-PRS-ResourceID based on its PRS measurement from the TRP (see TS 37.355 [49]) and DL-PRS Resource Set.INTEGER (0..63) OPTIONAL -- Need S } SRS-ResourceId ::= INTEGER (0..maxNrofSRS-Resources-1) SRS-PosResourceId-r16 ::= INTEGER (0..maxNrofSRS-PosResources-1-r16) SRS-PeriodicityAndOffset ::= CHOICE { sl1 NULL, sl2 INTEGER(0..1), sl4 INTEGER(0..3), sl5 INTEGER(0..4), sl8 INTEGER(0..7), sl10 INTEGER(0..9), sl16 INTEGER(0..15), sl20 INTEGER(0..19), sl32 INTEGER(0..31), sl40 INTEGER(0..39), sl64 INTEGER(0..63), sl80 INTEGER(0..79), sl160 INTEGER(0..159), sl320 INTEGER(0..319), sl640 INTEGER(0..639), sl1280 INTEGER(0..1279), sl2560 INTEGER(0..2559) } SRS-PeriodicityAndOffset-r16 ::= CHOICE { sl1 NULL, sl2 INTEGER(0..1), sl4 INTEGER(0..3), sl5 INTEGER(0..4), sl8 INTEGER(0..7), sl10 INTEGER(0..9), sl16 INTEGER(0..15), sl20 INTEGER(0..19), sl32 INTEGER(0..31), sl40 INTEGER(0..39), sl64 INTEGER(0..63), sl80 INTEGER(0..79), sl160 INTEGER(0..159), sl320 INTEGER(0..319), sl640 INTEGER(0..639), sl1280 INTEGER(0..1279), sl2560 INTEGER(0..2559), sl5120 INTEGER(0..5119), sl10240 INTEGER(0..10239), sl40960 INTEGER(0..40959), sl81920 INTEGER(0..81919), ... } SRS-PeriodicityAndOffsetExt-r16 ::= CHOICE { sl128 INTEGER(0..127), sl256 INTEGER(0..255), sl512 INTEGER(0..511), sl20480 INTEGER(0..20479) } -- TAG-SRS-CONFIG-STOP -- ASN1STOP
SRS-Config field descriptions |
---|
tpc-Accumulation If the field is absent, UE applies TPC commands via accumulation. If disabled, UE applies the TPC command without accumulation (this applies to SRS when a separate closed loop is configured for SRS) (see TS 38.213 [13], clause 7.3). |
SRS-Resource, SRS-PosResourcefield descriptions |
---|
cyclicShift-n2 Cyclic shift configuration (see TS 38.214 [19], clause 6.2.1). |
cyclicShift-n4 Cyclic shift configuration (see TS 38.214 [19], clause 6.2.1). |
cyclicShift-n8 Cyclic shift configuration (see TS 38.214 [19], clause 6.2.1). |
freqHopping Includes parameters capturing SRS frequency hopping (see TS 38.214 [19], clause 6.2.1). For CLI SRS-RSRP measurement, the network always configures this field such that b-hop > b-SRS. |
groupOrSequenceHopping Parameter(s) for configuring group or sequence hopping (see TS 38.211 [16], clause 6.4.1.4.2). For CLI SRS-RSRP measurement, the network always configures this parameter to 'neither'. |
nrofSRS-Ports Number of ports. For CLI SRS-RSRP measurement, the network always configures this parameter to 'port1'. |
periodicityAndOffset-p, periodicityAndOffset-p-Ext Periodicity and slot offset for this SRS resource. All values are in "number of slots". Value sl1 corresponds to a periodicity of 1 slot, value sl2 corresponds to a periodicity of 2 slots, and so on. For each periodicity the corresponding offset is given in number of slots. For periodicity sl1 the offset is 0 slots (see TS 38.214 [19], clause 6.2.1). For CLI SRS-RSRP measurement, sl1280 and sl2560 cannot be configured. For SRS-PosResource, sl20480, sl40960 and sl81920 cannot be configured for SCS=15kHz, sl40960 and sl81920 cannot be configured for SCS=30kHz, and sl81920 cannot be configured for SCS=60kHz. When the field periodicityAndOffset-p-Ext is present, the field periodicityAndOffset-p shall be ignored by the UE. |
periodicityAndOffset-sp, periodicityAndOffset-sp-Ext Periodicity and slot offset for this SRS resource. All values are in "number of slots". Value sl1 corresponds to a periodicity of 1 slot, value sl2 corresponds to a periodicity of 2 slots, and so on. For each periodicity the corresponding offset is given in number of slots. For periodicity sl1 the offset is 0 slots (see TS 38.214 [19], clause 6.2.1). For SRS-PosResource, sl20480,sl40960 and sl81920 cannot be configured for SCS=15kHz, sl40960 and sl81920 cannot be configured for SCS=30kHz, and sl81920 cannot be configured for SCS=60kHz. When the field periodicityAndOffset-sp-Ext is present, the field periodicityAndOffset-sp shall be ignored by the UE. |
ptrs-PortIndex The PTRS port index for this SRS resource for non-codebook based UL MIMO. This is only applicable when the corresponding PTRS-UplinkConfig is set to CP-OFDM. The ptrs-PortIndex configured here must be smaller than the maxNrofPorts configured in the PTRS-UplinkConfig (see TS 38.214 [19], clause 6.2.3.1). This parameter is not applicable to CLI SRS-RSRP measurement. |
resourceMapping OFDM symbol location of the SRS resource within a slot including nrofSymbols (number of OFDM symbols), startPosition (value 0 refers to the last symbol, value 1 refers to the second last symbol, and so on) and repetitionFactor (see TS 38.214 [19], clause 6.2.1 and TS 38.211 [16], clause 6.4.1.4). The configured SRS resource does not exceed the slot boundary. If resourceMapping-r16 is signalled, UE shall ignore the resourceMapping (without suffix). For CLI SRS-RSRP measurement, the network always configures nrofSymbols and repetitionFactor to 'n1'. |
resourceType Periodicity and offset for semi-persistent and periodic SRS resource, or slot offset for aperiodic SRS resourcefor positioning (see TS 38.214 [19], clause 6.2.1). For CLI SRS-RSRP measurement, only 'periodic' is applicable for resourceType. |
sequenceId Sequence ID used to initialize pseudo random group and sequence hopping (see TS 38.214 [19], clause 6.2.1). |
spatialRelationInfo Configuration of the spatial relation between a reference RS and the target SRS. Reference RS can be SSB/CSI-RS/SRS (see TS 38.214 [19], clause 6.2.1). This parameter is not applicable to CLI SRS-RSRP measurement. |
spatialRelationInfoPos Configuration of the spatial relation between a reference RS and the target SRS. Reference RS can be SSB/CSI-RS/SRS/DL-PRS (see TS 38.214 [19], clause 6.2.1). If the IE srs-ResourceId-Ext is present, the IE srs-ResourceId in spatialRelationInfoPos represents the index from 0 to 63. Otherwise the IE srs-ResourceId in spatialRelationInfoPos represents the index from 0 to 31. |
srs-RequestDCI-0-2 Indicate the number of bits for "SRS request"in DCI format 0_2. When the field is absent, then the value of 0 bit for "SRS request" in DCI format 0_2 is applied. If the parameter srs-RequestDCI-0-2 is configured to value 1, 1 bit is used to indicate one of the first two rows of Table 7.3.1.1.2-24 in TS 38.212 [17] for triggered aperiodic SRS resource set. If the value 2 is configured, 2 bits are used to indicate one of the rows of Table 7.3.1.1.2-24 in TS 38.212 [17]. When UE is configured with supplementaryUplink, an extra bit (the first bit of the SRS request field) is used for the non-SUL/SUL indication. |
srs-RequestDCI-1-2 Indicate the number of bits for "SRS request" in DCI format 1_2. When the field is absent, then the value of 0 bit for "SRS request" in DCI format 1_2 is applied. When the UE is configured with supplementaryUplink, an extra bit (the first bit of the SRS request field) is used for the non-SUL/SUL indication (see TS 38.214 [19], clause 6.1.1.2). |
srs-ResourceSetToAddModListDCI-0-2 List of SRS resource set to be added or modified for DCI format 0_2 (see TS 38.212 [17], clause 7.3.1). |
srs-ResourceSetToReleaseListDCI-0-2 List of SRS resource set to be released for DCI format 0_2 (see TS 38.212 [17], clause 7.3.1). |
transmissionComb Comb value (2 or 4 or 8) and comb offset (0..combValue-1) (see TS 38.214 [19], clause 6.2.1). |
SRS-ResourceSet, SRS-PosResourceSetfield descriptions |
---|
alpha alpha value for SRS power control (see TS 38.213 [13], clause 7.3). When the field is absent the UE applies the value 1. |
aperiodicSRS-ResourceTriggerList An additional list of DCI "code points" upon which the UE shall transmit SRS according to this SRS resource set configuration (see TS 38.214 [19], clause 6). When the field is not included during a reconfiguration of SRS-ResourceSet of resourceType set to aperiodic, UE maintains this value based on the Need M; that is, this list is not considered as an extension of aperiodicSRS-ResourceTrigger for purpose of applying the general rule for extended list in clause 6.1.3. |
aperiodicSRS-ResourceTrigger The DCI "code point" upon which the UE shall transmit SRS according to this SRS resource set configuration (see TS 38.214 [19], clause 6). |
associatedCSI-RS ID of CSI-RS resource associated with this SRS resource set in non-codebook based operation (see TS 38.214 [19], clause 6.1.1.2). |
csi-RS ID of CSI-RS resource associated with this SRS resource set. (see TS 38.214 [19], clause 6.1.1.2). |
dl-PRS This field indicates a PRS configuration. |
p0 P0 value for SRS power control. The value is in dBm. Only even values (step size 2) are allowed (see TS 38.213 [13], clause 7.3). |
pathlossReferenceRS A reference signal (e.g. a CSI-RS config or a SS block) to be used for SRS path loss estimation (see TS 38.213 [13], clause 7.3). |
pathlossReferenceRS-Pos A reference signal (e.g. a SS block or a DL-PRS config) to be used for SRS path loss estimation (see TS 38.213 [13], clause 7.3). |
pathlossReferenceRSList Multiple candidate pathloss reference RS(s) for SRS power control, where one candidate RS can be mapped to SRS Resource Set via MAC CE (clause 6.1.3.27 in TS 38.321 [3]). The network can only configure this field if pathlossReferenceRS is not configured in the same SRS-ResourceSet. |
resourceType Time domain behavior of SRS resource configuration, see TS 38.214 [19], clause 6.2.1. The network configures SRS resources in the same resource set with the same time domain behavior on periodic, aperiodic and semi-persistent SRS. |
slotOffset An offset in number of slots between the triggering DCI and the actual transmission of this SRS-ResourceSet. If the field is absent the UE applies no offset (value 0). |
srs-PowerControlAdjustmentStates Indicates whether hsrs,c(i) = fc(i,1) or hsrs,c(i) = fc(i,2) (if twoPUSCH-PC-AdjustmentStates are configured) or separate close loop is configured for SRS. This parameter is applicable only for Uls on which UE also transmits PUSCH. If absent or release, the UE applies the value sameAs-Fci1 (see TS 38.213 [13], clause 7.3). |
srs-ResourceIdList, srs-PosResourceIdList The IDs of the SRS-Resources/SRS-PosResource used in this SRS-ResourceSet/SRS-PosResourceSet. If this SRS-ResourceSet is configured with usage set to codebook, the srs-ResourceIdList contains at most 2 entries. If this SRS-ResourceSet is configured with usage set to nonCodebook, the srs-ResourceIdList contains at most 4 entries. |
srs-ResourceSetId, srs-PosResourceSetId The ID of this resource set. It is unique in the context of the BWP in which the parent SRS-Config is defined. |
ssb-IndexServing Indicates SSB index belonging to a serving cellwhere the SRS is configured. |
ssb-Ncell This field indicates a SSB configuration from neighboring cell. |
usage Indicates if the SRS resource set is used for beam management, codebook based or non-codebook based transmission or antenna switching. See TS 38.214 [19], clause 6.2.1. Reconfiguration between codebook based and non-codebook based transmission is not supported. |
SRS-SpatialRelationInfoPosfield descriptions |
---|
csi-RS-IndexServing Indicates CSI-RS index belonging to a serving cell. |
dl-PRS This field indicates a PRS configuration. |
resourceSelection Indicates whether the configured SRS spatial relation resource is a SRS-Resource or SRS-PosResource. |
servingCellId The serving Cell ID of the source SSB, CSI-RS, or SRS for the spatial relation of the target SRS resource. If this field is absent the SSB, the CSI-RS, or the SRS is from the same serving cell where the SRS is configured. |
ssb-IndexServing Indicates SSB index belonging to a serving cell. |
ssb-Ncell This field indicates a SSB configuration from neighboring cell. |
SSB-InfoNCell field descriptions |
---|
physicalCellId This field specifies the physical cell ID of the neighbour cell for which SSB configuration is provided. |
ssb-IndexNcell This field specifies the index of the SSB for a neighbour cell. See TS 38.213 [13]. If this field is absent, the UE determines the ssb-IndexNcell of the physicalCellId based on its SSB measurement from the cell. |
ssb-Configuration This field specifies the full configuration of the SSB. If this field is absent, the UE obtains the configuration for the SSB from nr-SSB-Config received as part of DL-PRS assistance data in LPP, see TS 37.355 [49], by looking up the corresponding SSB configuration using the field physicalCellId. |
DL-PRS-Info field descriptions |
---|
dl-PRS-ID This field specifies the UE specific TRP ID (see TS 37.355 [49]) for which PRS configuration is provided. |
dl-PRS-ResourceSetId This field specifies the PRS-ResourceSet ID of a PRS resourceSet. |
dl-PRS-ResourceId This field specifies the PRS-Resource ID of a PRS resource. If this field is absent, the UE determines the dl-PRS-ResourceID based on its PRS measurement from the TRP (see TS 37.355 [49]) and DL-PRS Resource Set. |
SSB-Configuration field descriptions |
---|
halfFrameIndex Indicates whether SSB is in the first half or the second half of the frame.Value zero indicates the first half and value 1 indicates the second half. |
integerSubframeOffset Indicates the subframe boundary offset of the cell in which SSB is transmited. |
sfn0-Offset Indiactes the time offset of the SFN0 slot 0 for the cell with respect to SFN0 slot 0 of serving cell. |
sfn-Offset Specifies the SFN offsetbetween the cell in which SSB is transmited and serving cell.The offset corresponds to the number of full radio frames counted from the beginning of a radio frame #0 of serving cell to the beginning of the closest subsequent radio frame #0 of the cell in which SSB is transmitted. |
sfn-SSB-Offset Indicates the SFN offset of the transmitted SSB relative to the start of the SSB period. Value 0 indicates that the SSB is transmitted in the first system frame, value 1 indicates that SSB is transmitted in the second system frame and so on. The network configures this field according to the field ssb-Periodicity such that the indicated system frame does not exceed the configured SSB periodicity. |
ss-PBCH-BlockPower Average EPRE of the resources elements that carry secondary synchronization signals in dBm that the NW used for SSB transmission, see TS 38.213 [13], clause 7. |
ssb-Freq Indicates the frequency of the SSB. |
ssb-Periodicity Indicates the periodicity of the SSB. If the field is absent, the UE applies the value ms5. (see TS 38.213 [13], clause 4.1) |
ssbSubcarrierSpacing Subcarrier spacing of SSB. Only the values 15 kHz or 30 kHz (FR1), and 120 kHz or 240 kHz (FR2) are applicable. |
Conditional Presence | Explanation |
---|---|
Setup | This field is mandatory present upon configuration of SRS-ResourceSet or SRS-Resource and optionally present, Need M, otherwise. |
NonCodebook | This field is optionally present, Need M, in case of non-codebook based transmission, otherwise the field is absent. |
Pathloss | The field is mandatory present if the IE SSB-InfoNcell is included in pathlossReferenceRS-Pos; otherwise it is optionally present, Need R |
The IE SRS-RSRP-Range specifies the value range used in SRS-RSRP measurements and thresholds. The integer value for SRS-RSRP measurements is according to Table 10.1.22.1.2-1 in TS 38.133 [14]. For thresholds, the actual value is (IE value –140) dBm, except for the IE value 98, in which case the actual value is infinity.
The IE SRS-TPC-CommandConfig is used to configure the UE for extracting TPC commands for SRS from a group-TPC messages on DCI
-- ASN1START -- TAG-SRS-TPC-COMMANDCONFIG-START SRS-TPC-CommandConfig ::= SEQUENCE {startingBitOfFormat2-3The starting bit position of a block within the group DCI with SRS request fields (optional) and TPC commands. The value 1 of the field corresponds to the first/left most bit of format2-3. The value 2 of the field corresponds to the second bit format2-3, and so on (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 11.3).INTEGER (1..31) OPTIONAL, -- Need RfieldTypeFormat2-3The type of a field within the group DCI with SRS request fields (optional), which indicates how many bits in the field are for SRS request (0 or 2). Note that for Type A, there is a common SRS request field for all SCells in the set, but each SCell has its own TPC command bits. See TS 38.212 [17] clause 7.3.1 and , TS 38.213 [13], clause 11.3.INTEGER (0..1) OPTIONAL, -- Need R ..., [[startingBitOfFormat2-3SULThe starting bit position of a block within the group DCI with SRS request fields (optional) and TPC commands for SUL carrier (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 11.3).INTEGER (1..31) OPTIONAL -- Need R ]] } -- TAG-SRS-TPC-COMMANDCONFIG-STOP -- ASN1STOP
SRS-TPC-CommandConfig field descriptions |
---|
fieldTypeFormat2-3 The type of a field within the group DCI with SRS request fields (optional), which indicates how many bits in the field are for SRS request (0 or 2). Note that for Type A, there is a common SRS request field for all SCells in the set, but each SCell has its own TPC command bits. See TS 38.212 [17] clause 7.3.1 and , TS 38.213 [13], clause 11.3. |
startingBitOfFormat2-3 The starting bit position of a block within the group DCI with SRS request fields (optional) and TPC commands. The value 1 of the field corresponds to the first/left most bit of format2-3. The value 2 of the field corresponds to the second bit format2-3, and so on (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 11.3). |
startingBitOfFormat2-3SUL The starting bit position of a block within the group DCI with SRS request fields (optional) and TPC commands for SUL carrier (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13], clause 11.3). |
The IE SSB-Index identifies an SS-Block within an SS-Burst. See TS 38.213 [13], clause 4.1.
The IE SSB-MTC is used to configure measurement timing configurations, i.e., timing occasions at which the UE measures SSBs.
-- ASN1START -- TAG-SSB-MTC-START SSB-MTC ::= SEQUENCE {periodicityAndOffsetPeriodicity and offset of the measurement window in which to receive SS/PBCH blocks, see 5.5.2.10. Periodicity and offset are given in number of subframes.CHOICE { sf5 INTEGER (0..4), sf10 INTEGER (0..9), sf20 INTEGER (0..19), sf40 INTEGER (0..39), sf80 INTEGER (0..79), sf160 INTEGER (0..159) },durationDuration of the measurement window in which to receive SS/PBCH blocks. It is given in number of subframes (see TS 38.213 [13], clause 4.1).ENUMERATED { sf1, sf2, sf3, sf4, sf5 } } SSB-MTC2 ::= SEQUENCE {pci-ListPCIs that are known to follow this SMTC, used for IAB-node discovery.SEQUENCE (SIZE (1..maxNrofPCIsPerSMTC)) OF PhysCellId OPTIONAL, -- Need M periodicity ENUMERATED {sf5, sf10, sf20, sf40, sf80, spare3, spare2, spare1} } SSB-MTC2-LP-r16 ::= SEQUENCE {pci-ListPCIs that are known to follow this SMTC, used for IAB-node discovery.SEQUENCE (SIZE (1..maxNrofPCIsPerSMTC)) OF PhysCellId OPTIONAL, -- Need R periodicity ENUMERATED {sf10, sf20, sf40, sf80, sf160, spare3, spare2, spare1} } SSB-MTC3-r16 ::= SEQUENCE {periodicityAndOffset-r16Periodicity and offset of the measurement window in which to receive SS/PBCH blocks, see 5.5.2.10. Periodicity and offset are given in number of subframes.CHOICE { sf5-r16 INTEGER (0..4), sf10-r16 INTEGER (0..9), sf20-r16 INTEGER (0..19), sf40-r16 INTEGER (0..39), sf80-r16 INTEGER (0..79), sf160-r16 INTEGER (0..159), sf320-r16 INTEGER (0..319), sf640-r16 INTEGER (0..639), sf1280-r16 INTEGER (0..1279) },duration-r16Duration of the measurement window in which to receive SS/PBCH blocks. It is given in number of subframes (see TS 38.213 [13], clause 4.1).ENUMERATED {sf1, sf2, sf3, sf4, sf5},pci-List-r16PCIs that are known to follow this SMTC, used for IAB-node discovery.SEQUENCE (SIZE (1..maxNrofPCIsPerSMTC)) OF PhysCellId OPTIONAL, -- Need Mssb-ToMeasure-r16The set of SS blocks to be measured within the SMTC measurement duration. The first/leftmost bit corresponds to SS block index 0, the second bit corresponds to SS block index 1, and so on. Value 0 in the bitmap indicates that the corresponding SS block is not to be measured while value 1 indicates that the corresponding SS block is to be measured (see TS 38.215 [9]). When the field is not configured the IAB-MT measures on all SS blocks. Regardless of the value of this field, SS blocks outside of the applicable smtc are not to be measured. See TS 38.215 [9] clause 5.1.1.SetupRelease { SSB-ToMeasure } OPTIONAL -- Need M } -- TAG-SSB-MTC-STOP -- ASN1STOP
SSB-MTC field descriptions |
---|
duration Duration of the measurement window in which to receive SS/PBCH blocks. It is given in number of subframes (see TS 38.213 [13], clause 4.1). |
periodicityAndOffset Periodicity and offset of the measurement window in which to receive SS/PBCH blocks, see 5.5.2.10. Periodicity and offset are given in number of subframes. |
SSB-MTC2 field descriptions |
---|
pci-List PCIs that are known to follow this SMTC. |
SSB-MTC3 field descriptions |
---|
duration Duration of the measurement window in which to receive SS/PBCH blocks. It is given in number of subframes (see TS 38.213 [13], clause 4.1). |
pci-List PCIs that are known to follow this SMTC, used for IAB-node discovery. |
periodicityAndOffset Periodicity and offset of the measurement window in which to receive SS/PBCH blocks, see 5.5.2.10. Periodicity and offset are given in number of subframes. |
ssb-ToMeasure The set of SS blocks to be measured within the SMTC measurement duration. The first/leftmost bit corresponds to SS block index 0, the second bit corresponds to SS block index 1, and so on. Value 0 in the bitmap indicates that the corresponding SS block is not to be measured while value 1 indicates that the corresponding SS block is to be measured (see TS 38.215 [9]). When the field is not configured the IAB-MT measures on all SS blocks. Regardless of the value of this field, SS blocks outside of the applicable smtc are not to be measured. See TS 38.215 [9] clause 5.1.1. |
The IE SSB-PositionQCL-Relation is used to indicate the QCL relationship between SSB positions on the frequency indicated by ssbFrequency (see TS 38.213 [13], clause 4.1) for operation with shared spectrum channel access. Value n1 corresponds to 1, value n2 corresponds to 2 and so on.
The IE SSB-ToMeasure is used to configure a pattern of SSBs. For operation with shared spectrum channel access, only mediumBitmap is used.
-- ASN1START -- TAG-SSB-TOMEASURE-START SSB-ToMeasure ::= CHOICE {shortBitmapBitmap when maximum number of SS/PBCH blocks per half frame equals to 4 as defined in TS 38.213 [13], clause 4.1.BIT STRING (SIZE (4)),mediumBitmapBitmap when maximum number of SS/PBCH blocks per half frame equals to 8 as defined in TS 38.213 [13], clause 4.1. For operation with shared spectrum channel access, if the k-th bit is set to 1, the UE assumes that one or more SS/PBCH blocks within the SMTC measurement duration with candidate SS/PBCH block indexes corresponding to SS/PBCH block index equal to k – 1 may be transmitted; if the kt-th bit is set to 0, the UE assumes that the corresponding SS/PBCH block(s) are not transmitted. The k-th bit is set to 0, where k > ssb-PositionQCL-Commonand the number of actually transmitted SS/PBCH blocks is not larger than the number of 1's in the bitmap. If ssb-PositionQCL is configured with a value smaller than ssb-PositionQCL-Common, only the leftmost K bits (K = ssb-PositionQCL) are applicable for the corresponding cell.BIT STRING (SIZE (8)),longBitmapBitmap when maximum number of SS/PBCH blocks per half frame equals to 64 as defined in TS 38.213 [13], clause 4.1.BIT STRING (SIZE (64)) } -- TAG-SSB-TOMEASURE-STOP -- ASN1STOP
SSB-ToMeasure field descriptions |
---|
longBitmap Bitmap when maximum number of SS/PBCH blocks per half frame equals to 64 as defined in TS 38.213 [13], clause 4.1. |
mediumBitmap Bitmap when maximum number of SS/PBCH blocks per half frame equals to 8 as defined in TS 38.213 [13], clause 4.1. For operation with shared spectrum channel access, if the k-th bit is set to 1, the UE assumes that one or more SS/PBCH blocks within the SMTC measurement duration with candidate SS/PBCH block indexes corresponding to SS/PBCH block index equal to k – 1 may be transmitted; if the kt-th bit is set to 0, the UE assumes that the corresponding SS/PBCH block(s) are not transmitted. The k-th bit is set to 0, where k > ssb-PositionQCL-Commonand the number of actually transmitted SS/PBCH blocks is not larger than the number of 1's in the bitmap. If ssb-PositionQCL is configured with a value smaller than ssb-PositionQCL-Common, only the leftmost K bits (K = ssb-PositionQCL) are applicable for the corresponding cell. |
shortBitmap Bitmap when maximum number of SS/PBCH blocks per half frame equals to 4 as defined in TS 38.213 [13], clause 4.1. |
The IE SS-RSSI-Measurement is used to configure RSSI measurements based on synchronization reference signals.
-- ASN1START -- TAG-SS-RSSI-MEASUREMENT-START SS-RSSI-Measurement ::= SEQUENCE {measurementSlotsIndicates the slots in which the UE can perform RSSI measurements. The length of the BIT STRING is equal to the number of slots in the configured SMTC window (determined by the duration and by the subcarrierSpacing). The first (left-most / most significant) bit in the bitmap corresponds to the first slot in the SMTC window, the second bit in the bitmap corresponds to the second slot in the SMTC window, and so on. The UE measures in slots for which the corresponding bit in the bitmap is set to 1. In case this field is configured for a SCell with ca-SlotOffset-r16, the bits in the bitmap corresponds to the slots that are fully contained in the SMTC window.BIT STRING (SIZE (1..80)),endSymbolWithin a slot that is configured for RSSI measurements (see measurementSlots) the UE measures the RSSI from symbol 0 to symbol endSymbol. This field identifies the entry in Table 5.1.3-1 in TS 38.215 [9], which determines the actual end symbol.INTEGER(0..3) } -- TAG-SS-RSSI-MEASUREMENT-STOP -- ASN1STOP
SS-RSSI-Measurement field descriptions |
---|
endSymbol Within a slot that is configured for RSSI measurements (see measurementSlots) the UE measures the RSSI from symbol 0 to symbol endSymbol. This field identifies the entry in Table 5.1.3-1 in TS 38.215 [9], which determines the actual end symbol. |
measurementSlots Indicates the slots in which the UE can perform RSSI measurements. The length of the BIT STRING is equal to the number of slots in the configured SMTC window (determined by the duration and by the subcarrierSpacing). The first (left-most / most significant) bit in the bitmap corresponds to the first slot in the SMTC window, the second bit in the bitmap corresponds to the second slot in the SMTC window, and so on. The UE measures in slots for which the corresponding bit in the bitmap is set to 1. In case this field is configured for a SCell with ca-SlotOffset-r16, the bits in the bitmap corresponds to the slots that are fully contained in the SMTC window. |
The IE SubcarrierSpacing determines the subcarrier spacing. Restrictions applicable for certain frequencies, channels or signals are clarified in the fields that use this IE.
The IE TAG-Config is used to configure parameters for a time-alignment group.
-- ASN1START -- TAG-TAG-CONFIG-START TAG-Config ::= SEQUENCE { tag-ToReleaseList SEQUENCE (SIZE (1..maxNrofTAGs)) OF TAG-Id OPTIONAL, -- Need N tag-ToAddModList SEQUENCE (SIZE (1..maxNrofTAGs)) OF TAG OPTIONAL -- Need N } TAG ::= SEQUENCE {tag-IdIndicates the TAG of the SpCell or an SCell, see TS 38.321 [3]. Uniquely identifies the TAG within the scope of a Cell Group (i.e. MCG or SCG).TAG-Id,timeAlignmentTimerThe timeAlignmentTimer for TAG with ID tag-Id, as specified in TS 38.321 [3].TimeAlignmentTimer, ... } TAG-Id ::= INTEGER (0..maxNrofTAGs-1) -- TAG-TAG-CONFIG-STOP -- ASN1STOP
TAG field descriptions |
---|
tag-Id Indicates the TAG of the SpCell or an SCell, see TS 38.321 [3]. Uniquely identifies the TAG within the scope of a Cell Group (i.e. MCG or SCG). |
timeAlignmentTimer The timeAlignmentTimer for TAG with ID tag-Id, as specified in TS 38.321 [3]. |
The IE TCI-State associates one or two DL reference signals with a corresponding quasi-colocation (QCL) type.
-- ASN1START -- TAG-TCI-STATE-START TCI-State ::= SEQUENCE { tci-StateId TCI-StateId, qcl-Type1 QCL-Info, qcl-Type2 QCL-Info OPTIONAL, -- Need R ... } QCL-Info ::= SEQUENCE {cellThe UE's serving cell in which the referenceSignal is configured. If the field is absent, the referenceSignal is configured in the serving cell in which the TCI-State is configured. The RS can be located on a serving cell other than the serving cell in which the TCI-State is configured only if the qcl-Type is configured as typeC or typeD. See TS 38.214 [19] clause 5.1.5.ServCellIndex OPTIONAL, -- Need Rbwp-IdThe DL BWP which the RS is located in.BWP-Id OPTIONAL, -- Cond CSI-RS-IndicatedreferenceSignalReference signal with which quasi-collocation information is provided as specified in TS 38.214 [19] clause 5.1.5.CHOICE { csi-rs NZP-CSI-RS-ResourceId, ssb SSB-Index },qcl-TypeQCL type as specified in TS 38.214 [19] clause 5.1.5.ENUMERATED {typeA, typeB, typeC, typeD}, ... } -- TAG-TCI-STATE-STOP -- ASN1STOP
QCL-Info field descriptions |
---|
bwp-Id The DL BWP which the RS is located in. |
cell The UE's serving cell in which the referenceSignal is configured. If the field is absent, the referenceSignal is configured in the serving cell in which the TCI-State is configured. The RS can be located on a serving cell other than the serving cell in which the TCI-State is configured only if the qcl-Type is configured as typeC or typeD. See TS 38.214 [19] clause 5.1.5. |
referenceSignal Reference signal with which quasi-collocation information is provided as specified in TS 38.214 [19] clause 5.1.5. |
qcl-Type QCL type as specified in TS 38.214 [19] clause 5.1.5. |
Conditional Presence | Explanation |
---|---|
CSI-RS-Indicated | This field is mandatory present if csi-rs is included, absent otherwise |
The IE TCI-StateId is used to identify one TCI-State configuration.
The IE TDD-UL-DL-ConfigCommon determines the cell specific Uplink/Downlink TDD configuration.
-- ASN1START -- TAG-TDD-UL-DL-CONFIGCOMMON-START TDD-UL-DL-ConfigCommon ::= SEQUENCE { referenceSubcarrierSpacing SubcarrierSpacing, pattern1 TDD-UL-DL-Pattern, pattern2 TDD-UL-DL-Pattern OPTIONAL, -- Need R ... } TDD-UL-DL-Pattern ::= SEQUENCE { dl-UL-TransmissionPeriodicity ENUMERATED {ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms5, ms10}, nrofDownlinkSlots INTEGER (0..maxNrofSlots), nrofDownlinkSymbols INTEGER (0..maxNrofSymbols-1), nrofUplinkSlots INTEGER (0..maxNrofSlots), nrofUplinkSymbols INTEGER (0..maxNrofSymbols-1), ..., [[ dl-UL-TransmissionPeriodicity-v1530 ENUMERATED {ms3, ms4} OPTIONAL -- Need R ]] } -- TAG-TDD-UL-DL-CONFIGCOMMON-STOP -- ASN1STOP
The IE TDD-UL-DL-ConfigDedicated determines the UE-specific Uplink/Downlink TDD configuration.
-- ASN1START -- TAG-TDD-UL-DL-CONFIGDEDICATED-START TDD-UL-DL-ConfigDedicated ::= SEQUENCE {slotSpecificConfigurationsToAddModListThe slotSpecificConfigurationToAddModList allows overriding UL/DL allocations provided in tdd-UL-DL-configurationCommon, see TS 38.213 [13], clause 11.1.SEQUENCE (SIZE (1..maxNrofSlots)) OF TDD-UL-DL-SlotConfig OPTIONAL, -- Need N slotSpecificConfigurationsToReleaseList SEQUENCE (SIZE (1..maxNrofSlots)) OF TDD-UL-DL-SlotIndex OPTIONAL, -- Need N ... } TDD-UL-DL-ConfigDedicated-IAB-MT-r16::= SEQUENCE {slotSpecificConfigurationsToAddModList-IAB-MT-r16The slotSpecificConfigurationToAddModList-IAB-MT allows overriding UL/DL allocations provided in tdd-UL-DL-configurationCommon with a limitation that effectively only flexible symbols can be overwritten in Rel-16.SEQUENCE (SIZE (1..maxNrofSlots)) OF TDD-UL-DL-SlotConfig-IAB-MT-r16 OPTIONAL, -- Need NslotSpecificConfigurationsToReleaseList-IAB-MT-r16The slotSpecificConfigurationsToReleaseList-IAB-MT allows release of a set of slot configuration previously add with slotSpecificConfigurationToAddModList-IAB-MT.SEQUENCE (SIZE (1..maxNrofSlots)) OF TDD-UL-DL-SlotIndex OPTIONAL, -- Need N ... } TDD-UL-DL-SlotConfig ::= SEQUENCE {slotIndexIdentifies a slot within a slot configuration periodgiven in tdd-UL-DL-configurationCommon, see TS 38.213 [13], clause 11.1.TDD-UL-DL-SlotIndex,symbolsThe direction (downlink or uplink) for the symbols in this slot. Value allDownlink indicates that all symbols in this slot are used for downlink; value allUplink indicates that all symbols in this slot are used for uplink; value explicit indicates explicitly how many symbols in the beginning and end of this slot are allocated to downlink and uplink, respectively.CHOICE { allDownlink NULL, allUplink NULL, explicit SEQUENCE {nrofDownlinkSymbolsNumber of consecutive DL symbols in the beginning of the slot identified by slotIndex. If the field is absent the UE assumes that there are no leading DL symbols. (see TS 38.213 [13], clause 11.1).INTEGER (1..maxNrofSymbols-1) OPTIONAL, -- Need SnrofUplinkSymbolsNumber of consecutive UL symbols in the end of the slot identified by slotIndex. If the field is absent the UE assumes that there are no trailing UL symbols. (see TS 38.213 [13], clause 11.1).INTEGER (1..maxNrofSymbols-1) OPTIONAL -- Need S } } } TDD-UL-DL-SlotConfig-IAB-MT-r16::= SEQUENCE {slotIndex-r16Identifies a slot within a slot configuration periodgiven in tdd-UL-DL-configurationCommon, see TS 38.213 [13], clause 11.1.TDD-UL-DL-SlotIndex,symbols-IAB-MT-r16The symbols-IAB-MTis used to configure an IAB-MT with the SlotConfig applicable for one serving cell. Value allDownlink indicates that all symbols in this slot are used for downlink; value allUplink indicates that all symbols in this slot are used for uplink; value explicit indicates explicitly how many symbols in the beginning and end of this slot are allocated to downlink and uplink, respectively; value explicit-IAB-MTindicates explicitly how many symbols in the beginning and end of this slot are allocated to uplink and downlink, respectively.CHOICE { allDownlink-r16 NULL, allUplink-r16 NULL, explicit-r16 SEQUENCE {nrofDownlinkSymbols-r16Number of consecutive DL symbols in the beginning of the slot identified by slotIndex. If the field is absent the UE assumes that there are no leading DL symbols. (see TS 38.213 [13], clause 11.1).INTEGER (1..maxNrofSymbols-1) OPTIONAL, -- Need SnrofUplinkSymbols-r16Number of consecutive UL symbols in the end of the slot identified by slotIndex. If the field is absent the UE assumes that there are no trailing UL symbols. (see TS 38.213 [13], clause 11.1).INTEGER (1..maxNrofSymbols-1) OPTIONAL -- Need S }, explicit-IAB-MT-r16 SEQUENCE {nrofDownlinkSymbols-r16Number of consecutive DL symbols in the beginning of the slot identified by slotIndex. If the field is absent the UE assumes that there are no leading DL symbols. (see TS 38.213 [13], clause 11.1).INTEGER (1..maxNrofSymbols-1) OPTIONAL, -- Need SnrofUplinkSymbols-r16Number of consecutive UL symbols in the end of the slot identified by slotIndex. If the field is absent the UE assumes that there are no trailing UL symbols. (see TS 38.213 [13], clause 11.1).INTEGER (1..maxNrofSymbols-1) OPTIONAL -- Need S } } } TDD-UL-DL-SlotIndex ::= INTEGER (0..maxNrofSlots-1) -- TAG-TDD-UL-DL-CONFIGDEDICATED-STOP -- ASN1STOP
TDD-UL-DL-ConfigCommon field descriptions |
---|
referenceSubcarrierSpacing Reference SCS used to determine the time domain boundaries in the UL-DL pattern which must be common across all subcarrier specific carriers, i.e., independent of the actual subcarrier spacing using for data transmission. Only the values 15, 30 or 60 kHz (FR1), and 60 or 120 kHz (FR2) are applicable. The network configures a not larger than any SCS of configured BWPs for the serving cell. The network or SL-PreconfigGeneralconfigures a not larger than the SCS of (pre-)configured SL BWP.See TS 38.213 [13], clause 11.1. |
TDD-UL-DL-Pattern field descriptions |
---|
dl-UL-TransmissionPeriodicity Periodicity of the DL-UL pattern, see TS 38.213 [13], clause 11.1.If the dl-UL-TransmissionPeriodicity-v1530 is signalled, UE shall ignore the dl-UL-TransmissionPeriodicity (without suffix). |
nrofDownlinkSlots Number of consecutive full DL slots at the beginning of each DL-UL pattern, see TS 38.213 [13], clause 11.1. In this release, the maximum value for this field is 80. |
nrofDownlinkSymbols Number of consecutive DL symbols in the beginning of the slot following the last full DL slot (as derived from nrofDownlinkSlots). The value 0 indicates that there is no partial-downlink slot. (see TS 38.213 [13], clause 11.1). |
nrofUplinkSlots Number of consecutive full UL slots at the end of each DL-UL pattern, see TS 38.213 [13], clause 11.1. In this release, the maximum value for this field is 80. |
nrofUplinkSymbols Number of consecutive UL symbols in the end of the slot preceding the first full UL slot (as derived from nrofUplinkSlots). The value 0 indicates that there is no partial-uplink slot. (see TS 38.213 [13], clause 11.1). |
TDD-UL-DL-ConfigDedicated field descriptions |
---|
slotSpecificConfigurationsToAddModList The slotSpecificConfigurationToAddModList allows overriding UL/DL allocations provided in tdd-UL-DL-configurationCommon, see TS 38.213 [13], clause 11.1. |
TDD-UL-DL-ConfigDedicated-IAB-MT field descriptions |
---|
slotSpecificConfigurationsToAddModList-IAB-MT The slotSpecificConfigurationToAddModList-IAB-MT allows overriding UL/DL allocations provided in tdd-UL-DL-configurationCommon with a limitation that effectively only flexible symbols can be overwritten in Rel-16. |
slotSpecificConfigurationsToReleaseList-IAB-MT The slotSpecificConfigurationsToReleaseList-IAB-MT allows release of a set of slot configuration previously add with slotSpecificConfigurationToAddModList-IAB-MT. |
TDD-UL-DL-SlotConfig field descriptions |
---|
nrofDownlinkSymbols Number of consecutive DL symbols in the beginning of the slot identified by slotIndex. If the field is absent the UE assumes that there are no leading DL symbols. (see TS 38.213 [13], clause 11.1). |
nrofUplinkSymbols Number of consecutive UL symbols in the end of the slot identified by slotIndex. If the field is absent the UE assumes that there are no trailing UL symbols. (see TS 38.213 [13], clause 11.1). |
slotIndex Identifies a slot within a slot configuration periodgiven in tdd-UL-DL-configurationCommon, see TS 38.213 [13], clause 11.1. |
symbols The direction (downlink or uplink) for the symbols in this slot. Value allDownlink indicates that all symbols in this slot are used for downlink; value allUplink indicates that all symbols in this slot are used for uplink; value explicit indicates explicitly how many symbols in the beginning and end of this slot are allocated to downlink and uplink, respectively. |
TDD-UL-DL-SlotConfig-IAB-MT field descriptions |
---|
symbols-IAB-MT The symbols-IAB-MTis used to configure an IAB-MT with the SlotConfig applicable for one serving cell. Value allDownlink indicates that all symbols in this slot are used for downlink; value allUplink indicates that all symbols in this slot are used for uplink; value explicit indicates explicitly how many symbols in the beginning and end of this slot are allocated to downlink and uplink, respectively; value explicit-IAB-MTindicates explicitly how many symbols in the beginning and end of this slot are allocated to uplink and downlink, respectively. |
The IE TrackingAreaCode is used to identify a tracking area within the scope of a PLMN/SNPN, see TS 24.501 [23].
The IE T-Reselection concerns the cell reselection timer TreselectionRAT for NR and E-UTRA. Value in seconds. For value 0, behaviour as specified in 7.1.2 applies.
The IE TimeAlignmentTimer is used to configure the time alignment timer as specified in TS 38.321 [3]. The values are in ms.
The IE TimeToTrigger specifies the value range used for time to trigger parameter, which concerns the time during which specific criteria for the event needs to be met in order to trigger a measurement report. Value ms0 corresponds to 0 ms and behaviour as specified in 7.1.2 applies, value ms40 corresponds to 40 ms, and so on.
The IE UAC-BarringInfoSetIndex provides the index of the entry in uac-BarringInfoSetList. Value 1 corresponds to the first entry in uac-BarringInfoSetList, value 2 corresponds to the second entry in this list and so on. An index value referring to an entry not included in uac-BarringInfoSetList indicates no barring.
The IE UAC-BarringInfoSetList provides a list of access control parameter sets. An access category can be configured with access parameters according to one of the sets.
-- ASN1START -- TAG-UAC-BARRINGINFOSETLIST-START UAC-BarringInfoSetList ::= SEQUENCE (SIZE(1..maxBarringInfoSet)) OF UAC-BarringInfoSet UAC-BarringInfoSet ::= SEQUENCE {uac-BarringFactorRepresents the probability that access attempt would be allowed during access barring check.ENUMERATED {p00, p05, p10, p15, p20, p25, p30, p40, p50, p60, p70, p75, p80, p85, p90, p95},uac-BarringTimeThe average time in seconds before a new access attempt is to be performed after an access attempt was barred at access barring check for the same access category, see 5.3.14.5.ENUMERATED {s4, s8, s16, s32, s64, s128, s256, s512},uac-BarringForAccessIdentityIndicates whether access attempt is allowed for each Access Identity. The leftmost bit, bit 0 in the bit string corresponds to Access Identity 1, bit 1 in the bit string corresponds to Access Identity 2, bit 2 in the bit string corresponds to Access Identity 11, bit 3 in the bit string corresponds to Access Identity 12, bit 4 in the bit string corresponds to Access Identity 13, bit 5 in the bit string corresponds to Access Identity 14, and bit 6 in the bit string corresponds to Access Identity 15. Value 0 means that access attempt is allowed for the corresponding access identity.BIT STRING (SIZE(7)) } -- TAG-UAC-BARRINGINFOSETLIST-STOP -- ASN1STOP
UAC-BarringInfoSetList field descriptions |
---|
uac-BarringInfoSetList List of access control parameter sets. Each access category can be configured with access parameters corresponding to a particular set by uac-barringInfoSetIndex. Association of an access category with an index that has no corresponding entry in the uac-BarringInfoSetList is valid configuration and indicates no barring. |
uac-BarringForAccessIdentity Indicates whether access attempt is allowed for each Access Identity. The leftmost bit, bit 0 in the bit string corresponds to Access Identity 1, bit 1 in the bit string corresponds to Access Identity 2, bit 2 in the bit string corresponds to Access Identity 11, bit 3 in the bit string corresponds to Access Identity 12, bit 4 in the bit string corresponds to Access Identity 13, bit 5 in the bit string corresponds to Access Identity 14, and bit 6 in the bit string corresponds to Access Identity 15. Value 0 means that access attempt is allowed for the corresponding access identity. |
uac-BarringFactor Represents the probability that access attempt would be allowed during access barring check. |
uac-BarringTime The average time in seconds before a new access attempt is to be performed after an access attempt was barred at access barring check for the same access category, see 5.3.14.5. |
The IE UAC-BarringPerCatList provides access control parameters for a list of access categories.
-- ASN1START -- TAG-UAC-BARRINGPERCATLIST-START UAC-BarringPerCatList ::= SEQUENCE (SIZE (1..maxAccessCat-1)) OF UAC-BarringPerCat UAC-BarringPerCat ::= SEQUENCE {accessCategoryThe Access Category according to TS 22.261 [25].INTEGER (1..maxAccessCat-1), uac-barringInfoSetIndex UAC-BarringInfoSetIndex } -- TAG-UAC-BARRINGPERCATLIST-STOP -- ASN1STOP
UAC-BarringPerCatList field descriptions |
---|
accessCategory The Access Category according to TS 22.261 [25]. |
The IE UAC-BarringPerPLMN-List provides access category specific access control parameters, which are configured per PLMN/SNPN.
-- ASN1START -- TAG-UAC-BARRINGPERPLMN-LIST-START UAC-BarringPerPLMN-List ::= SEQUENCE (SIZE (1.. maxPLMN)) OF UAC-BarringPerPLMN UAC-BarringPerPLMN ::= SEQUENCE {plmn-IdentityIndexIndex of the PLMN or SNPN across the plmn-IdentityInfoList and npn-IdentityInfoList fields included in SIB1.INTEGER (1..maxPLMN),uac-ACBarringListTypeAccess control parameters for each access category valid only for a specific PLMN or SNPN. UE behaviour upon absence of this field is specified in clause 5.3.14.2.CHOICE{ uac-ImplicitACBarringList SEQUENCE (SIZE(maxAccessCat-1)) OF UAC-BarringInfoSetIndex, uac-ExplicitACBarringList UAC-BarringPerCatList } OPTIONAL -- Need S } -- TAG-UAC-BARRINGPERPLMN-LIST-STOP -- ASN1STOP
UAC-BarringPerPLMN-List field descriptions |
---|
uac-ACBarringListType Access control parameters for each access category valid only for a specific PLMN or SNPN. UE behaviour upon absence of this field is specified in clause 5.3.14.2. |
plmn-IdentityIndex Index of the PLMN or SNPN across the plmn-IdentityInfoList and npn-IdentityInfoList fields included in SIB1. |
The IE UE-TimersAndConstants contains timers and constants used by the UE in RRC_CONNECTED, RRC_INACTIVE and RRC_IDLE.
-- ASN1START -- TAG-UE-TIMERSANDCONSTANTS-START UE-TimersAndConstants ::= SEQUENCE { t300 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000}, t301 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000}, t310 ENUMERATED {ms0, ms50, ms100, ms200, ms500, ms1000, ms2000}, n310 ENUMERATED {n1, n2, n3, n4, n6, n8, n10, n20}, t311 ENUMERATED {ms1000, ms3000, ms5000, ms10000, ms15000, ms20000, ms30000}, n311 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10}, t319 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000}, ... } -- TAG-UE-TIMERSANDCONSTANTS-STOP -- ASN1STOP
The IE UL-DelayValueConfig specifies the configuration of the UL PDCP Packet Delay value per DRB measurement specified in TS 38.314 [53].
-- ASN1START -- TAG-ULDELAYVALUECONFIG-START UL-DelayValueConfig-r16 ::= SEQUENCE {delay-DRBlist-r16Indicates the DRB IDs used by UE to provide results of UL PDCP Packet Delay value per DRB measurement as specified in TS 38.314 [53].SEQUENCE (SIZE(1..maxDRB)) OF DRB-Identity } -- TAG-ULDELAYVALUECONFIG-STOP -- ASN1STOP
UL-DelayValueConfig field descriptions |
---|
delay-DRBlist Indicates the DRB IDs used by UE to provide results of UL PDCP Packet Delay value per DRB measurement as specified in TS 38.314 [53]. |
The IE UplinkCancellation is used to configure the UE to monitor PDCCH for the CI-RNTI.
-- ASN1START -- TAG-UPLINKCANCELLATION-START UplinkCancellation-r16 ::= SEQUENCE {ci-RNTI-r16RNTI used for indication cancellation in UL (see TS 38.212 [17] clause 7.3.1 and TS 38.213 [13], clause 11.2A).RNTI-Value,dci-PayloadSizeForCI-r16Total length of the DCI payload scrambled with CI-RNTI (see TS 38.213 [13], clause 11.2A).INTEGER (0..maxCI-DCI-PayloadSize-r16),ci-ConfigurationPerServingCell-r16Indicates (per serving cell) the position of the ci-PaylaodSize bit CI values inside the DCI payload (see TS 38.213 [13], clause 11.2A).SEQUENCE (SIZE (1..maxNrofServingCells)) OF CI-ConfigurationPerServingCell-r16, ... } CI-ConfigurationPerServingCell-r16 ::= SEQUENCE { servingCellId ServCellIndex,positionInDCI-r16Starting position (in number of bit) of the ci-PayloadSize bit CI value applicable for this serving cell (servingCellId) within the DCI payload (see TS 38.213 [13], clause 11.2A).INTEGER (0..maxCI-DCI-PayloadSize-1-r16),positionInDCI-ForSUL-r16Starting position (in number of bit) of the ci-PayloadSize bit CI value applicable for SUL of this serving cell (servingCellId) within the DCI payload (see TS 38.213 [13], clause 11.2A).INTEGER (0..maxCI-DCI-PayloadSize-1-r16) OPTIONAL, -- Cond SUL-Onlyci-PayloadSize-r16Configures the field size for each UL cancelation indicator of this serving cell (servingCellId) (see TS 38.213 [13], clause 11.2A).ENUMERATED {n1, n2, n4, n5, n7, n8, n10, n14, n16, n20, n28, n32, n35, n42, n56, n112},timeFrequencyRegion-r16Configures the reference time and frequency region where a detected UL CI is applicable of this serving cell (servingCellId) (see TS 38.213 [13], clause 11.2A).SEQUENCE {timeDurationForCI-r16Configures the duration of the reference time region in symbols where a detected UL CI is applicable of this serving cell (servingCellId) (see TS 38.213 [13], clause 11.2A). If the field is absent, i.e., the configured UL CI monitoring periodicity indicated by monitoringSlotPeriodicityAndOffset for DCI format 2_4 is larger than 1 slot or 1 slot with only one monitoring occasion, the UE applies the value of the configured UL CI monitoring periodicity,ENUMERATED {n2, n4, n7, n14} OPTIONAL, -- Cond SymbolPeriodicitytimeGranularityForCI-r16Configures the number of partitions within the time region of this serving cell (servingCellId) (see TS 38.213 [13], clause 11.2A).ENUMERATED {n1, n2, n4, n7, n14, n28},frequencyRegionForCI-r16Configures the reference frequency region where a detected UL CI is applicable (see TS 38.213 [13], clause 11.2A). It is defined in the same way as locationAndBandwidth.INTEGER (0..37949),deltaOffset-r16Configures the additional offset from the end of a PDCCH reception where the UE detects the DCI format 2_4 and the first symbol of the T_"CI" symbols, in the unit of OFDM symbols (see TS 38.213 [13], clause 11.2A).INTEGER (0..2), ... }, uplinkCancellationPriority-v1610 ENUMERATED {enabled} OPTIONAL -- Need S } -- TAG-UPLINKCANCELLATION-STOP -- ASN1STOP
UplinkCancellation field descriptions |
---|
ci-ConfigurationPerServingCell Indicates (per serving cell) the position of the ci-PaylaodSize bit CI values inside the DCI payload (see TS 38.213 [13], clause 11.2A). |
ci-RNTI RNTI used for indication cancellation in UL (see TS 38.212 [17] clause 7.3.1 and TS 38.213 [13], clause 11.2A). |
dci-PayloadSizeForCI Total length of the DCI payload scrambled with CI-RNTI (see TS 38.213 [13], clause 11.2A). |
CI-ConfigurationPerServingCell field descriptions |
---|
ci-PayloadSize Configures the field size for each UL cancelation indicator of this serving cell (servingCellId) (see TS 38.213 [13], clause 11.2A). |
deltaOffset Configures the additional offset from the end of a PDCCH reception where the UE detects the DCI format 2_4 and the first symbol of the T_"CI" symbols, in the unit of OFDM symbols (see TS 38.213 [13], clause 11.2A). |
frequencyRegionForCI Configures the reference frequency region where a detected UL CI is applicable (see TS 38.213 [13], clause 11.2A). It is defined in the same way as locationAndBandwidth. |
positionInDCI Starting position (in number of bit) of the ci-PayloadSize bit CI value applicable for this serving cell (servingCellId) within the DCI payload (see TS 38.213 [13], clause 11.2A). |
positionInDCI-ForSUL Starting position (in number of bit) of the ci-PayloadSize bit CI value applicable for SUL of this serving cell (servingCellId) within the DCI payload (see TS 38.213 [13], clause 11.2A). |
timeDurationForCI Configures the duration of the reference time region in symbols where a detected UL CI is applicable of this serving cell (servingCellId) (see TS 38.213 [13], clause 11.2A). If the field is absent, i.e., the configured UL CI monitoring periodicity indicated by monitoringSlotPeriodicityAndOffset for DCI format 2_4 is larger than 1 slot or 1 slot with only one monitoring occasion, the UE applies the value of the configured UL CI monitoring periodicity, |
timeFrequencyRegion Configures the reference time and frequency region where a detected UL CI is applicable of this serving cell (servingCellId) (see TS 38.213 [13], clause 11.2A). |
timeGranularityForCI Configures the number of partitions within the time region of this serving cell (servingCellId) (see TS 38.213 [13], clause 11.2A). |
uplinkCancellationPriority Configures uplink cancellation behavior if both UL CI and intra-UE priority indicator are configured for a given UE. If the field is present, then UL CI is only applicable to the UL transmissions indicated/configured as low priority level. If the field is absent, UL CI is applicable to UL transmission irrespective of its priority level (see TS 38.213 [13], clause 11.2A). |
Conditional Presence | Explanation |
---|---|
SUL-Only | The field is optionally present, Need R, if supplementaryUplink is configured in ServingCellConfig. It is absent otherwise. |
SymbolPeriodicity | This field is mandatory present if the configured UL CI monitoring periodicity indicated by monitoringSlotPeriodicityAndOffset for DCI format 2_4 is 1 slot with more than one monitoring occasion, otherwise absent. |
The IE UplinkConfigCommon provides common uplink parameters of a cell.
-- ASN1START -- TAG-UPLINKCONFIGCOMMON-START UplinkConfigCommon ::= SEQUENCE {frequencyInfoULAbsolute uplink frequency configuration and subcarrier specific virtual carriers.FrequencyInfoUL OPTIONAL, -- Cond InterFreqHOAndServCellAddinitialUplinkBWPThe initial uplink BWP configuration for a serving cell (see TS 38.213 [13], clause 12).BWP-UplinkCommon OPTIONAL, -- Cond ServCellAdd dummy TimeAlignmentTimer } -- TAG-UPLINKCONFIGCOMMON-STOP -- ASN1STOP
UplinkConfigCommon field descriptions |
---|
frequencyInfoUL Absolute uplink frequency configuration and subcarrier specific virtual carriers. |
initialUplinkBWP The initial uplink BWP configuration for a serving cell (see TS 38.213 [13], clause 12). |
Conditional Presence | Explanation |
---|---|
InterFreqHOAndServCellAdd | This field is mandatory present for inter-frequency handover and upon serving cell (PSCell/SCell) addition. Otherwise, the field is optionally present, Need M. |
ServCellAdd | This field is mandatory present upon serving cell addition (for PSCell and SCell) and upon handover from E-UTRA to NR. It is optionally present, Need M otherwise. |
The IE UplinkConfigCommonSIB provides common uplink parameters of a cell.
-- ASN1START -- TAG-UPLINKCONFIGCOMMONSIB-START UplinkConfigCommonSIB ::= SEQUENCE {frequencyInfoULAbsolute uplink frequency configuration and subcarrier specific virtual carriers.FrequencyInfoUL-SIB, initialUplinkBWP BWP-UplinkCommon, timeAlignmentTimerCommon TimeAlignmentTimer } -- TAG-UPLINKCONFIGCOMMONSIB-STOP -- ASN1STOP
UplinkConfigCommonSIB field descriptions |
---|
frequencyInfoUL Absolute uplink frequency configuration and subcarrier specific virtual carriers. |
InitialUplinkBWP The initial uplink BWP configuration for a PCell (see TS 38.213 [13], clause 12). |
The IE UplinkTxDirectCurrentList indicates the Tx Direct Current locations per serving cell for each configured UL BWP in the serving cell, based on the BWP numerology and the associated carrier bandwidth.
-- ASN1START -- TAG-UPLINKTXDIRECTCURRENTLIST-START UplinkTxDirectCurrentList ::= SEQUENCE (SIZE (1..maxNrofServingCells)) OF UplinkTxDirectCurrentCell UplinkTxDirectCurrentCell ::= SEQUENCE {servCellIndexThe serving cell ID of the serving cell corresponding to the uplinkDirectCurrentBWP.ServCellIndex,uplinkDirectCurrentBWPThe Tx Direct Current locations for all the uplink BWPs configured at the corresponding serving cell.SEQUENCE (SIZE (1..maxNrofBWPs)) OF UplinkTxDirectCurrentBWP, ..., [[uplinkDirectCurrentBWP-SULThe Tx Direct Current locations for all the supplementary uplink BWPs configured at the corresponding serving cell.SEQUENCE (SIZE (1..maxNrofBWPs)) OF UplinkTxDirectCurrentBWP OPTIONAL ]] } UplinkTxDirectCurrentBWP ::= SEQUENCE {bwp-IdThe BWP-Id of the corresponding uplink BWP.BWP-Id,shift7dot5kHzIndicates whether there is 7.5 kHz shift or not. 7.5 kHz shift is applied if the field is set to true. Otherwise 7.5 kHz shift is not applied.BOOLEAN,txDirectCurrentLocationThe uplink Tx Direct Current location for the carrier. Only values in the value range of this field between 0 and 3299, which indicate the subcarrier index within the carrier corresponding to the numerology of the corresponding uplink BWP and value 3300, which indicates "Outside the carrier" and value 3301, which indicates "Undetermined position within the carrier" are used in this version of the specification.INTEGER (0..3301) } -- TAG-UPLINKTXDIRECTCURRENTLIST-STOP -- ASN1STOP
UplinkTxDirectCurrentBWP field descriptions |
---|
bwp-Id The BWP-Id of the corresponding uplink BWP. |
shift7dot5kHz Indicates whether there is 7.5 kHz shift or not. 7.5 kHz shift is applied if the field is set to true. Otherwise 7.5 kHz shift is not applied. |
txDirectCurrentLocation The uplink Tx Direct Current location for the carrier. Only values in the value range of this field between 0 and 3299, which indicate the subcarrier index within the carrier corresponding to the numerology of the corresponding uplink BWP and value 3300, which indicates "Outside the carrier" and value 3301, which indicates "Undetermined position within the carrier" are used in this version of the specification. |
UplinkTxDirectCurrentCell field descriptions |
---|
servCellIndex The serving cell ID of the serving cell corresponding to the uplinkDirectCurrentBWP. |
uplinkDirectCurrentBWP The Tx Direct Current locations for all the uplink BWPs configured at the corresponding serving cell. |
uplinkDirectCurrentBWP-SUL The Tx Direct Current locations for all the supplementary uplink BWPs configured at the corresponding serving cell. |
The IE UplinkTxDirectCurrentTwoCarrierList indicates the Tx Direct Current locations when uplink intra-band CA with two carriers is configured, based on the configured carriers and BWP numerology and the associated carrier bandwidth of the carriers. The UE does not report the uplink Direct Current location information for SUL carrier(s).
-- ASN1START -- TAG-UPLINKTXDIRECTCURRENTTWOCARRIERLIST-START UplinkTxDirectCurrentTwoCarrierList-r16 ::= SEQUENCE (SIZE (1..maxNrofTxDC-TwoCarrier-r16)) OF UplinkTxDirectCurrentTwoCarrier-r16 UplinkTxDirectCurrentTwoCarrier-r16 ::= SEQUENCE {carrierOneInfo-r16The serving cell ID and BWP ID of the first carrier of the uplink carrier aggregation for which the uplink Tx Direct Current location(s) are being reported.UplinkTxDirectCurrentCarrierInfo-r16,carrierTwoInfo-r16The serving cell ID and BWP ID of the second carrier of the uplink carrier aggregation for which the uplink Tx Direct Current location(s) are being reported.UplinkTxDirectCurrentCarrierInfo-r16,singlePA-TxDirectCurrent-r16The uplink Tx Direct Current location for the UE which support single PA for this uplink carrier aggregation. For the UEs which support dual PA for this uplink carrier aggregation, this field is for reporting the uplink Tx Direct Current location of the first PA.UplinkTxDirectCurrentTwoCarrierInfo-r16,secondPA-TxDirectCurrent-r16The uplink Tx Direct Current location used by the UE with the second PA for the UEs which support dual PA for this uplink carrier aggregation. This field shall be absent for the UplinkTxDirectCurrentTwoCarrier entity where deactivatedCarrier of carrierOneInfo or carrierTwoInfo is set to deactivated.UplinkTxDirectCurrentTwoCarrierInfo-r16 OPTIONAL } UplinkTxDirectCurrentCarrierInfo-r16 ::= SEQUENCE {servCellIndex-r16The serving cell ID of the serving cell which is part of the two carrier uplink carrier aggregation.ServCellIndex, servCellInfo-r16 CHOICE {bwp-Id-r16The BWP ID of the serving cell which is part of the two carrier uplink carrier aggregation. The UE shall not report this field if the serving cell is reported as deactivated using deactivatedCarrier-r16.BWP-Id,deactivatedCarrier-r16For the reported uplink Tx Direct Current location(s) corresponding to singlePA-TxDirectCurrent-r16, indicates whether the carrier is deactivated or not for this serving cell. If the carrier refers to the PCell, the UE shall not set this field to deactivated.ENUMERATED {deactivated} } } UplinkTxDirectCurrentTwoCarrierInfo-r16 ::= SEQUENCE {referenceCarrierIndex-r16The serving cell ID of the carrier which is to be used as the reference for interpreting the Tx Direction Current location as reported using txDirectCurrentLocation-r16. The numerology of the uplink BWP ID reported with bwp-Id-r16 for this serving cell is the numerology used for interpreting the reported subcarrier location.ServCellIndex,shift7dot5kHz-r16Indicates whether there is 7.5 kHz shift or not. 7.5 kHz shift is applied if the field is set to true. Otherwise 7.5 kHz shift is not applied.BOOLEAN,txDirectCurrentLocation-r16The uplink Tx Direct Current location for the two carrier uplink CA with the serving cells reported using carrierOneInfo-r16 and carrierTwoInfo-r16. Values in the range of this field between 0 and 3299 indicate the subcarrier index of the uplink Tx Direct Current location with the subcarrier taken from the serving cell with ID referenceCarrierIndex and the numerology of the corresponding uplink BWP reported for this serving cell. Value 3300 indicates "Outside the carrier" and value 3301 indicates "Undetermined position within the carrier".INTEGER (0..3301) } -- TAG-UPLINKTXDIRECTCURRENTTWOCARRIERLIST-STOP -- ASN1STOP
UplinkTxDirectCurrentTwoCarrierInfo field descriptions |
---|
referenceCarrierIndex The serving cell ID of the carrier which is to be used as the reference for interpreting the Tx Direction Current location as reported using txDirectCurrentLocation-r16. The numerology of the uplink BWP ID reported with bwp-Id-r16 for this serving cell is the numerology used for interpreting the reported subcarrier location. |
shift7dot5kHz Indicates whether there is 7.5 kHz shift or not. 7.5 kHz shift is applied if the field is set to true. Otherwise 7.5 kHz shift is not applied. |
txDirectCurrentLocation The uplink Tx Direct Current location for the two carrier uplink CA with the serving cells reported using carrierOneInfo-r16 and carrierTwoInfo-r16. Values in the range of this field between 0 and 3299 indicate the subcarrier index of the uplink Tx Direct Current location with the subcarrier taken from the serving cell with ID referenceCarrierIndex and the numerology of the corresponding uplink BWP reported for this serving cell. Value 3300 indicates "Outside the carrier" and value 3301 indicates "Undetermined position within the carrier". |
UplinkTxDirectCurrentCarrierInfo field descriptions |
---|
bwp-Id The BWP ID of the serving cell which is part of the two carrier uplink carrier aggregation. The UE shall not report this field if the serving cell is reported as deactivated using deactivatedCarrier-r16. |
deactivatedCarrier For the reported uplink Tx Direct Current location(s) corresponding to singlePA-TxDirectCurrent-r16, indicates whether the carrier is deactivated or not for this serving cell. If the carrier refers to the PCell, the UE shall not set this field to deactivated. |
servCellIndex The serving cell ID of the serving cell which is part of the two carrier uplink carrier aggregation. |
UplinkTxDirectCurrentTwoCarrier field descriptions |
---|
carrierOneInfo The serving cell ID and BWP ID of the first carrier of the uplink carrier aggregation for which the uplink Tx Direct Current location(s) are being reported. |
carrierTwoInfo The serving cell ID and BWP ID of the second carrier of the uplink carrier aggregation for which the uplink Tx Direct Current location(s) are being reported. |
singlePA-TxDirectCurrent The uplink Tx Direct Current location for the UE which support single PA for this uplink carrier aggregation. For the UEs which support dual PA for this uplink carrier aggregation, this field is for reporting the uplink Tx Direct Current location of the first PA. |
secondPA-TxDirectCurrent The uplink Tx Direct Current location used by the UE with the second PA for the UEs which support dual PA for this uplink carrier aggregation. This field shall be absent for the UplinkTxDirectCurrentTwoCarrier entity where deactivatedCarrier of carrierOneInfo or carrierTwoInfo is set to deactivated. |
The IE ZP-CSI-RS-Resource is used to configure a Zero-Power (ZP) CSI-RS resource (see TS 38.214 [19], clause 5.1.4.2). Reconfiguration of a ZP-CSI-RS-Resource between periodic or semi-persistent and aperiodic is not supported.
-- ASN1START -- TAG-ZP-CSI-RS-RESOURCE-START ZP-CSI-RS-Resource ::= SEQUENCE {zp-CSI-RS-ResourceIdZP CSI-RS resource configuration ID (see TS 38.214 [19], clause 5.1.4.2).ZP-CSI-RS-ResourceId,resourceMappingOFDM symbol and subcarrier occupancy of the ZP-CSI-RS resource within a slot.CSI-RS-ResourceMapping,periodicityAndOffsetPeriodicity and slot offset for periodic/semi-persistent ZP-CSI-RS (see TS 38.214 [19], clause 5.1.4.2). Network always configures the UE with a value for this field for periodic and semi-persistent ZP-CSI-RS resource (as indicated in PDSCH-Config).CSI-ResourcePeriodicityAndOffset OPTIONAL, --Cond PeriodicOrSemiPersistent ... } ZP-CSI-RS-ResourceId ::= INTEGER (0..maxNrofZP-CSI-RS-Resources-1) -- TAG-ZP-CSI-RS-RESOURCE-STOP -- ASN1STOP
ZP-CSI-RS-Resource field descriptions |
---|
periodicityAndOffset Periodicity and slot offset for periodic/semi-persistent ZP-CSI-RS (see TS 38.214 [19], clause 5.1.4.2). Network always configures the UE with a value for this field for periodic and semi-persistent ZP-CSI-RS resource (as indicated in PDSCH-Config). |
resourceMapping OFDM symbol and subcarrier occupancy of the ZP-CSI-RS resource within a slot. |
zp-CSI-RS-ResourceId ZP CSI-RS resource configuration ID (see TS 38.214 [19], clause 5.1.4.2). |
Conditional Presence | Explanation |
---|---|
PeriodicOrSemiPersistent | The field is optionally present, Need M, for periodic and semi-persistent ZP-CSI-RS-Resources (as indicated in PDSCH-Config). The field is absent otherwise. |
The IE ZP-CSI-RS-ResourceSet refers to a set of ZP-CSI-RS-Resources using their ZP-CSI-RS-ResourceIds.
-- ASN1START -- TAG-ZP-CSI-RS-RESOURCESET-START ZP-CSI-RS-ResourceSet ::= SEQUENCE { zp-CSI-RS-ResourceSetId ZP-CSI-RS-ResourceSetId,zp-CSI-RS-ResourceIdListThe list of ZP-CSI-RS-ResourceId identifying the ZP-CSI-RS-Resource elements belonging to this set.SEQUENCE (SIZE(1..maxNrofZP-CSI-RS-ResourcesPerSet)) OF ZP-CSI-RS-ResourceId, ... } -- TAG-ZP-CSI-RS-RESOURCESET-STOP -- ASN1STOP
ZP-CSI-RS-ResourceSet field descriptions |
---|
zp-CSI-RS-ResourceIdList The list of ZP-CSI-RS-ResourceId identifying the ZP-CSI-RS-Resource elements belonging to this set. |
The IE ZP-CSI-RS-ResourceSetId identifies a ZP-CSI-RS-ResourceSet.
The IE AccessStratumRelease indicates the release supported by the UE.
The IE BandCombinationList contains a list of NR CA,NR non-CA and/or MR-DC band combinations (also including DL only or UL only band).
-- ASN1START -- TAG-BANDCOMBINATIONLIST-START BandCombinationList ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination BandCombinationList-v1540 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1540 BandCombinationList-v1550 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1550 BandCombinationList-v1560 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1560 BandCombinationList-v1570 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1570 BandCombinationList-v1580 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1580 BandCombinationList-v1590 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1590 BandCombinationList-v15g0 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v15g0 BandCombinationList-v15n0 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v15n0 BandCombinationList-v1610 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1610 BandCombinationList-v1630 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1630 BandCombinationList-v1640 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1640 BandCombinationList-v1650 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1650 BandCombinationList-v1680 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1680 BandCombinationList-v1690 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v1690 BandCombinationList-v16a0 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-v16a0 BandCombinationList-UplinkTxSwitch-r16 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-r16 BandCombinationList-UplinkTxSwitch-v1630 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1630 BandCombinationList-UplinkTxSwitch-v1640 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1640 BandCombinationList-UplinkTxSwitch-v1650 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1650 BandCombinationList-UplinkTxSwitch-v1670 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1670 BandCombinationList-UplinkTxSwitch-v1690 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v1690 BandCombinationList-UplinkTxSwitch-v16a0 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v16a0 BandCombinationList-UplinkTxSwitch-v16e0 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombination-UplinkTxSwitch-v16e0 BandCombination ::= SEQUENCE { bandList SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParameters, featureSetCombination FeatureSetCombinationId, ca-ParametersEUTRA CA-ParametersEUTRA OPTIONAL, ca-ParametersNR CA-ParametersNR OPTIONAL, mrdc-Parameters MRDC-Parameters OPTIONAL, supportedBandwidthCombinationSet BIT STRING (SIZE (1..32)) OPTIONAL, powerClass-v1530 ENUMERATED {pc2} OPTIONAL } BandCombination-v1540::= SEQUENCE { bandList-v1540 SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParameters-v1540, ca-ParametersNR-v1540 CA-ParametersNR-v1540 OPTIONAL } BandCombination-v1550 ::= SEQUENCE { ca-ParametersNR-v1550 CA-ParametersNR-v1550 } BandCombination-v1560::= SEQUENCE {ne-DC-BCIf the field is included for a band combination in the MR-DC capability container, the field indicates support of NE-DC. Otherwise, the field is absent.ENUMERATED {supported} OPTIONAL,ca-ParametersNRDCIf the field is included for a band combination in the NR capability container, the field indicates support of NR-DC. Otherwise, the field is absent.CA-ParametersNRDC OPTIONAL, ca-ParametersEUTRA-v1560 CA-ParametersEUTRA-v1560 OPTIONAL, ca-ParametersNR-v1560 CA-ParametersNR-v1560 OPTIONAL } BandCombination-v1570 ::= SEQUENCE { ca-ParametersEUTRA-v1570 CA-ParametersEUTRA-v1570 } BandCombination-v1580 ::= SEQUENCE { mrdc-Parameters-v1580 MRDC-Parameters-v1580 } BandCombination-v1590::= SEQUENCE { supportedBandwidthCombinationSetIntraENDC BIT STRING (SIZE (1..32)) OPTIONAL, mrdc-Parameters-v1590 MRDC-Parameters-v1590 } BandCombination-v15g0::= SEQUENCE { ca-ParametersNR-v15g0 CA-ParametersNR-v15g0 OPTIONAL, ca-ParametersNRDC-v15g0 CA-ParametersNRDC-v15g0 OPTIONAL, mrdc-Parameters-v15g0 MRDC-Parameters-v15g0 OPTIONAL } BandCombination-v15n0::= SEQUENCE { mrdc-Parameters-v15n0 MRDC-Parameters-v15n0 } BandCombination-v1610 ::= SEQUENCE { bandList-v1610 SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParameters-v1610 OPTIONAL, ca-ParametersNR-v1610 CA-ParametersNR-v1610 OPTIONAL, ca-ParametersNRDC-v1610 CA-ParametersNRDC-v1610 OPTIONAL, powerClass-v1610 ENUMERATED {pc1dot5} OPTIONAL, powerClassNRPart-r16 ENUMERATED {pc1, pc2, pc3, pc5} OPTIONAL,featureSetCombinationDAPS-r16If this field is present for a band combination, it reports the feature set combination supported for the band combination when any DAPS bearer is configured.FeatureSetCombinationId OPTIONAL, mrdc-Parameters-v1620 MRDC-Parameters-v1620 OPTIONAL } BandCombination-v1630 ::= SEQUENCE { ca-ParametersNR-v1630 CA-ParametersNR-v1630 OPTIONAL, ca-ParametersNRDC-v1630 CA-ParametersNRDC-v1630 OPTIONAL, mrdc-Parameters-v1630 MRDC-Parameters-v1630 OPTIONAL, supportedTxBandCombListPerBC-Sidelink-r16 BIT STRING (SIZE (1..maxBandComb)) OPTIONAL, supportedRxBandCombListPerBC-Sidelink-r16 BIT STRING (SIZE (1..maxBandComb)) OPTIONAL, scalingFactorTxSidelink-r16 SEQUENCE (SIZE (1..maxBandComb)) OF ScalingFactorSidelink-r16 OPTIONAL, scalingFactorRxSidelink-r16 SEQUENCE (SIZE (1..maxBandComb)) OF ScalingFactorSidelink-r16 OPTIONAL } BandCombination-v1640 ::= SEQUENCE { ca-ParametersNR-v1640 CA-ParametersNR-v1640 OPTIONAL, ca-ParametersNRDC-v1640 CA-ParametersNRDC-v1640 OPTIONAL } BandCombination-v1650 ::= SEQUENCE { ca-ParametersNRDC-v1650 CA-ParametersNRDC-v1650 OPTIONAL } BandCombination-v1680 ::= SEQUENCE { intrabandConcurrentOperationPowerClass-r16 SEQUENCE (SIZE (1..maxBandComb)) OF IntraBandPowerClass-r16 OPTIONAL } BandCombination-v1690 ::= SEQUENCE { ca-ParametersNR-v1690 CA-ParametersNR-v1690 OPTIONAL } BandCombination-v16a0 ::= SEQUENCE { ca-ParametersNR-v16a0 CA-ParametersNR-v16a0 OPTIONAL, ca-ParametersNRDC-v16a0 CA-ParametersNRDC-v16a0 OPTIONAL } BandCombination-UplinkTxSwitch-r16 ::= SEQUENCE { bandCombination-r16 BandCombination, bandCombination-v1540 BandCombination-v1540 OPTIONAL, bandCombination-v1560 BandCombination-v1560 OPTIONAL, bandCombination-v1570 BandCombination-v1570 OPTIONAL, bandCombination-v1580 BandCombination-v1580 OPTIONAL, bandCombination-v1590 BandCombination-v1590 OPTIONAL, bandCombination-v1610 BandCombination-v1610 OPTIONAL, supportedBandPairListNR-r16 SEQUENCE (SIZE (1..maxULTxSwitchingBandPairs)) OF ULTxSwitchingBandPair-r16, uplinkTxSwitching-OptionSupport-r16 ENUMERATED {switchedUL, dualUL, both} OPTIONAL, uplinkTxSwitching-PowerBoosting-r16 ENUMERATED {supported} OPTIONAL, ..., [[ uplinkTxSwitching-PUSCH-TransCoherence-r16 ENUMERATED {nonCoherent, fullCoherent} OPTIONAL ]] } BandCombination-UplinkTxSwitch-v1630 ::= SEQUENCE { bandCombination-v1630 BandCombination-v1630 OPTIONAL } BandCombination-UplinkTxSwitch-v1640 ::= SEQUENCE { bandCombination-v1640 BandCombination-v1640 OPTIONAL } BandCombination-UplinkTxSwitch-v1650 ::= SEQUENCE { bandCombination-v1650 BandCombination-v1650 OPTIONAL } BandCombination-UplinkTxSwitch-v1670 ::= SEQUENCE { bandCombination-v15g0 BandCombination-v15g0 OPTIONAL } BandCombination-UplinkTxSwitch-v1690 ::= SEQUENCE { bandCombination-v1690 BandCombination-v1690 OPTIONAL } BandCombination-UplinkTxSwitch-v16a0 ::= SEQUENCE { bandCombination-v16a0 BandCombination-v16a0 OPTIONAL } BandCombination-UplinkTxSwitch-v16e0 ::= SEQUENCE { bandCombination-v15n0 BandCombination-v15n0 OPTIONAL } ULTxSwitchingBandPair-r16 ::= SEQUENCE { bandIndexUL1-r16 INTEGER(1..maxSimultaneousBands), bandIndexUL2-r16 INTEGER(1..maxSimultaneousBands), uplinkTxSwitchingPeriod-r16 ENUMERATED {n35us, n140us, n210us}, uplinkTxSwitching-DL-Interruption-r16 BIT STRING (SIZE(1..maxSimultaneousBands)) OPTIONAL } BandParameters ::= CHOICE { eutra SEQUENCE { bandEUTRA FreqBandIndicatorEUTRA, ca-BandwidthClassDL-EUTRA CA-BandwidthClassEUTRA OPTIONAL, ca-BandwidthClassUL-EUTRA CA-BandwidthClassEUTRA OPTIONAL }, nr SEQUENCE { bandNR FreqBandIndicatorNR, ca-BandwidthClassDL-NR CA-BandwidthClassNR OPTIONAL, ca-BandwidthClassUL-NR CA-BandwidthClassNR OPTIONAL } } BandParameters-v1540 ::= SEQUENCE { srs-CarrierSwitch CHOICE { nr SEQUENCE {srs-SwitchingTimesListNRIndicates, for a particular pair of NR bands, the RF retuning time when switching between a NR carrier corresponding to this band entry and another (PUSCH-less) NR carrier corresponding to the band entry in the order indicated below: -For the first NR band, the UE shall include the same number of entries for NR bands as in bandList, i.e. first entry corresponds to first NR band in bandList and so on, -For the second NR band, the UE shall include one entry less, i.e. first entry corresponds to the second NR band in bandList and so on -And so onSEQUENCE (SIZE (1..maxSimultaneousBands)) OF SRS-SwitchingTimeNR }, eutra SEQUENCE {srs-SwitchingTimesListEUTRAIndicates, for a particular pair of E-UTRA bands, the RF retuning time when switching between an E-UTRA carrier corresponding to this band entry and another (PUSCH-less) E-UTRA carrier corresponding to the band entry in the order indicated below: -For the first E-UTRA band, the UE shall include the same number of entries for E-UTRA bands as in bandList, i.e. first entry corresponds to first E-UTRA band in bandList and so on, -For the second E-UTRA band, the UE shall include one entry less, i.e. first entry corresponds to the second E-UTRA band in bandList and so on -And so onSEQUENCE (SIZE (1..maxSimultaneousBands)) OF SRS-SwitchingTimeEUTRA } } OPTIONAL,srs-TxSwitchIndicates supported SRS antenna switch capability for the associated band. If the UE indicates support of SRS-SwitchingTimeNR, the UE is allowed to set this field for a band with associated FeatureSetUplinkId set to 0 for SRS carrier switching.SEQUENCE { supportedSRS-TxPortSwitch ENUMERATED {t1r2, t1r4, t2r4, t1r4-t2r4, t1r1, t2r2, t4r4, notSupported}, txSwitchImpactToRx INTEGER (1..32) OPTIONAL, txSwitchWithAnotherBand INTEGER (1..32) OPTIONAL } OPTIONAL } BandParameters-v1610 ::= SEQUENCE { srs-TxSwitch-v1610 SEQUENCE { supportedSRS-TxPortSwitch-v1610 ENUMERATED {t1r1-t1r2, t1r1-t1r2-t1r4, t1r1-t1r2-t2r2-t2r4, t1r1-t1r2-t2r2-t1r4-t2r4, t1r1-t2r2, t1r1-t2r2-t4r4} } OPTIONAL } ScalingFactorSidelink-r16 ::= ENUMERATED {f0p4, f0p75, f0p8, f1} IntraBandPowerClass-r16 ::= ENUMERATED {pc2, pc3, spare6, spare5, spare4, spare3, spare2, spare1} -- TAG-BANDCOMBINATIONLIST-STOP -- ASN1STOP
BandCombination field descriptions |
---|
BandCombinationList-v1540, BandCombinationList-v1550, BandCombinationList-v1560, BandCombinationList-v1570, BandCombinationList-v1580, BandCombinationList-v1590, BandCombinationList-v15g0,BandCombinationList-v15n0,BandCombinationList-v1610, BandCombinationList-v1630, BandCombinationList-v1640, BandCombinationList-v1650, BandCombinationList-v1680, BandCombinationList-v1690, BandCombinationList-v16a0 The UE shall include the same number of entries, and listed in the same order, as in BandCombinationList (without suffix).If the field is included in supportedBandCombinationListNEDC-Only-v1610, the UE shall include the same number of entries, and listed in the same order, as in BandCombinationList of supportedBandCombinationListNEDC-Only (without suffix) field. If the field is included in supportedBandCombinationListNEDC-Only-v15a0, the UE shall include the same number of entries, and listed in the same order, as in BandCombinationList(without suffix) of supportedBandCombinationListNEDC-Only(without suffix) field. |
ca-ParametersNRDC If the field is included for a band combination in the NR capability container, the field indicates support of NR-DC. Otherwise, the field is absent. |
featureSetCombinationDAPS If this field is present for a band combination, it reports the feature set combination supported for the band combination when any DAPS bearer is configured. |
ne-DC-BC If the field is included for a band combination in the MR-DC capability container, the field indicates support of NE-DC. Otherwise, the field is absent. |
srs-SwitchingTimesListNR Indicates, for a particular pair of NR bands, the RF retuning time when switching between a NR carrier corresponding to this band entry and another (PUSCH-less) NR carrier corresponding to the band entry in the order indicated below: -For the first NR band, the UE shall include the same number of entries for NR bands as in bandList, i.e. first entry corresponds to first NR band in bandList and so on, -For the second NR band, the UE shall include one entry less, i.e. first entry corresponds to the second NR band in bandList and so on -And so on |
srs-SwitchingTimesListEUTRA Indicates, for a particular pair of E-UTRA bands, the RF retuning time when switching between an E-UTRA carrier corresponding to this band entry and another (PUSCH-less) E-UTRA carrier corresponding to the band entry in the order indicated below: -For the first E-UTRA band, the UE shall include the same number of entries for E-UTRA bands as in bandList, i.e. first entry corresponds to first E-UTRA band in bandList and so on, -For the second E-UTRA band, the UE shall include one entry less, i.e. first entry corresponds to the second E-UTRA band in bandList and so on -And so on |
srs-TxSwitch Indicates supported SRS antenna switch capability for the associated band. If the UE indicates support of SRS-SwitchingTimeNR, the UE is allowed to set this field for a band with associated FeatureSetUplinkId set to 0 for SRS carrier switching. |
The IE BandCombinationListSidelinkEUTRA-NR contains a list of V2X sidelink and NR sidelink band combinations.
-- ASN1START -- TAG-BANDCOMBINATIONLISTSIDELINKEUTRANR-START BandCombinationListSidelinkEUTRA-NR-r16 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombinationParametersSidelinkEUTRA-NR-r16 BandCombinationListSidelinkEUTRA-NR-v1630 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombinationParametersSidelinkEUTRA-NR-v1630 BandCombinationParametersSidelinkEUTRA-NR-r16 ::= SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParametersSidelinkEUTRA-NR-r16 BandCombinationParametersSidelinkEUTRA-NR-v1630 ::= SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParametersSidelinkEUTRA-NR-v1630 BandParametersSidelinkEUTRA-NR-r16 ::= CHOICE { eutra SEQUENCE { bandParametersSidelinkEUTRA1-r16 OCTET STRING OPTIONAL, bandParametersSidelinkEUTRA2-r16 OCTET STRING OPTIONAL }, nr SEQUENCE { bandParametersSidelinkNR-r16 BandParametersSidelink-r16 } } BandParametersSidelinkEUTRA-NR-v1630 ::= CHOICE { eutra NULL, nr SEQUENCE { tx-Sidelink-r16 ENUMERATED {supported} OPTIONAL, rx-Sidelink-r16 ENUMERATED {supported} OPTIONAL, sl-CrossCarrierScheduling-r16 ENUMERATED {supported} OPTIONAL } } BandParametersSidelink-r16 ::= SEQUENCE { freqBandSidelink-r16 FreqBandIndicatorNR } -- TAG-BANDCOMBINATIONLISTSIDELINKEUTRANR-STOP -- ASN1STOP
BandParametersSidelinkEUTRA-NR field descriptions |
---|
bandParametersSidelinkEUTRA1,bandParametersSidelinkEUTRA2 This field includes the V2X-BandParameters-r14 and V2X-BandParameters-v1530 IE as specified in 36.331 [10]. It is used for reporting the per-band capability for V2X sidelink communication. |
The IE CA-BandwidthClassEUTRA indicates the E-UTRA CA bandwidth class as defined in TS 36.101 [22], table 5.6A-1.
The IE CA-BandwidthClassNR indicates the NR CA bandwidth class as defined in TS 38.101-1 [15], table 5.3A.5-1 and TS 38.101-2 [39], table 5.3A.4-1.
The IE CA-ParametersEUTRA contains the E-UTRA part of band combination parameters for a given MR-DC band combination.
-- ASN1START -- TAG-CA-PARAMETERSEUTRA-START CA-ParametersEUTRA ::= SEQUENCE { multipleTimingAdvance ENUMERATED {supported} OPTIONAL, simultaneousRx-Tx ENUMERATED {supported} OPTIONAL, supportedNAICS-2CRS-AP BIT STRING (SIZE (1..8)) OPTIONAL, additionalRx-Tx-PerformanceReq ENUMERATED {supported} OPTIONAL, ue-CA-PowerClass-N ENUMERATED {class2} OPTIONAL, supportedBandwidthCombinationSetEUTRA-v1530 BIT STRING (SIZE (1..32)) OPTIONAL, ... } CA-ParametersEUTRA-v1560 ::= SEQUENCE { fd-MIMO-TotalWeightedLayers INTEGER (2..128) OPTIONAL } CA-ParametersEUTRA-v1570 ::= SEQUENCE { dl-1024QAM-TotalWeightedLayers INTEGER (0..10) OPTIONAL } -- TAG-CA-PARAMETERSEUTRA-STOP -- ASN1STOP
The IE CA-ParametersNR contains carrier aggregation and inter-frequency DAPS handover related capabilities that are defined per band combination.
-- ASN1START -- TAG-CA-PARAMETERSNR-START CA-ParametersNR ::= SEQUENCE { dummy ENUMERATED {supported} OPTIONAL, parallelTxSRS-PUCCH-PUSCH ENUMERATED {supported} OPTIONAL, parallelTxPRACH-SRS-PUCCH-PUSCH ENUMERATED {supported} OPTIONAL, simultaneousRxTxInterBandCA ENUMERATED {supported} OPTIONAL, simultaneousRxTxSUL ENUMERATED {supported} OPTIONAL, diffNumerologyAcrossPUCCH-Group ENUMERATED {supported} OPTIONAL, diffNumerologyWithinPUCCH-GroupSmallerSCS ENUMERATED {supported} OPTIONAL, supportedNumberTAG ENUMERATED {n2, n3, n4} OPTIONAL, ... } CA-ParametersNR-v1540 ::= SEQUENCE { simultaneousSRS-AssocCSI-RS-AllCC INTEGER (5..32) OPTIONAL, csi-RS-IM-ReceptionForFeedbackPerBandComb SEQUENCE { maxNumberSimultaneousNZP-CSI-RS-ActBWP-AllCC INTEGER (1..64) OPTIONAL, totalNumberPortsSimultaneousNZP-CSI-RS-ActBWP-AllCC INTEGER (2..256) OPTIONAL } OPTIONAL, simultaneousCSI-ReportsAllCC INTEGER (5..32) OPTIONAL, dualPA-Architecture ENUMERATED {supported} OPTIONAL } CA-ParametersNR-v1550 ::= SEQUENCE { dummy ENUMERATED {supported} OPTIONAL } CA-ParametersNR-v1560 ::= SEQUENCE { diffNumerologyWithinPUCCH-GroupLargerSCS ENUMERATED {supported} OPTIONAL } CA-ParametersNR-v15g0 ::= SEQUENCE { simultaneousRxTxInterBandCAPerBandPair SimultaneousRxTxPerBandPair OPTIONAL, simultaneousRxTxSULPerBandPair SimultaneousRxTxPerBandPair OPTIONAL } CA-ParametersNR-v1610 ::= SEQUENCE { -- R1 9-3: Parallel MsgA and SRS/PUCCH/PUSCH transmissions across CCs in inter-band CA parallelTxMsgA-SRS-PUCCH-PUSCH-r16 ENUMERATED {supported} OPTIONAL, -- R1 9-4: MsgA operation in a band combination including SUL msgA-SUL-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-9c: Joint search space group switching across multiple cells jointSearchSpaceSwitchAcrossCells-r16 ENUMERATED {supported} OPTIONAL, -- R1 14-5: Half-duplex UE behaviour in TDD CA for same SCS half-DuplexTDD-CA-SameSCS-r16 ENUMERATED {supported} OPTIONAL, -- R1 18-4: SCell dormancy within active time scellDormancyWithinActiveTime-r16 ENUMERATED {supported} OPTIONAL, -- R1 18-4a: SCell dormancy outside active time scellDormancyOutsideActiveTime-r16 ENUMERATED {supported} OPTIONAL, -- R1 18-6: Cross-carrier A-CSI RS triggering with different SCS crossCarrierA-CSI-trigDiffSCS-r16 ENUMERATED {higherA-CSI-SCS,lowerA-CSI-SCS,both} OPTIONAL, -- R1 18-6a: Default QCL assumption for cross-carrier A-CSI-RS triggering defaultQCL-CrossCarrierA-CSI-Trig-r16 ENUMERATED {diffOnly, both} OPTIONAL, -- R1 18-7: CA with non-aligned frame boundaries for inter-band CA interCA-NonAlignedFrame-r16 ENUMERATED {supported} OPTIONAL, simul-SRS-Trans-BC-r16 ENUMERATED {n2} OPTIONAL, interFreqDAPS-r16 SEQUENCE { interFreqAsyncDAPS-r16 ENUMERATED {supported} OPTIONAL, interFreqDiffSCS-DAPS-r16 ENUMERATED {supported} OPTIONAL, interFreqMultiUL-TransmissionDAPS-r16 ENUMERATED {supported} OPTIONAL, interFreqSemiStaticPowerSharingDAPS-Mode1-r16 ENUMERATED {supported} OPTIONAL, interFreqSemiStaticPowerSharingDAPS-Mode2-r16 ENUMERATED {supported} OPTIONAL, interFreqDynamicPowerSharingDAPS-r16 ENUMERATED {short, long} OPTIONAL, interFreqUL-TransCancellationDAPS-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL,codebookParametersPerBC-r16For a given supported band combination, this field indicates the alternative list of SupportedCSI-RS-Resource supported for each codebook type, amongst the supported CSI-RS resources included in codebookParametersPerBand in MIMO-ParametersPerBand.CodebookParameters-v1610 OPTIONAL, -- R1 16-2a-10 Value of R for BD/CCE blindDetectFactor-r16 INTEGER (1..2) OPTIONAL, -- R1 11-2a: Capability on the number of CCs for monitoring a maximum number of BDs and non-overlapped CCEs per span when configured -- with DL CA with Rel-16 PDCCH monitoring capability on all the serving cells pdcch-MonitoringCA-r16 SEQUENCE { maxNumberOfMonitoringCC-r16 INTEGER (2..16), supportedSpanArrangement-r16 ENUMERATED {alignedOnly, alignedAndNonAligned} } OPTIONAL, -- R1 11-2c: Number of carriers for CCE/BD scaling with DL CA with mix of Rel. 16 and Rel. 15 PDCCH monitoring capabilities on -- different carriers pdcch-BlindDetectionCA-Mixed-r16 SEQUENCE { pdcch-BlindDetectionCA1-r16 INTEGER (1..15), pdcch-BlindDetectionCA2-r16 INTEGER (1..15), supportedSpanArrangement-r16 ENUMERATED {alignedOnly, alignedAndNonAligned} } OPTIONAL, -- R1 11-2d: Capability on the number of CCs for monitoring a maximum number of BDs and non-overlapped CCEs per span for MCG and for -- SCG when configured for NR-DC operation with Rel-16 PDCCH monitoring capability on all the serving cells pdcch-BlindDetectionMCG-UE-r16 INTEGER (1..14) OPTIONAL, pdcch-BlindDetectionSCG-UE-r16 INTEGER (1..14) OPTIONAL, -- R1 11-2e: Number of carriers for CCE/BD scaling for MCG and for SCG when configured for NR-DC operation with mix of Rel. 16 and -- Rel. 15 PDCCH monitoring capabilities on different carriers pdcch-BlindDetectionMCG-UE-Mixed-r16 SEQUENCE { pdcch-BlindDetectionMCG-UE1-r16 INTEGER (0..15), pdcch-BlindDetectionMCG-UE2-r16 INTEGER (0..15) } OPTIONAL, pdcch-BlindDetectionSCG-UE-Mixed-r16 SEQUENCE { pdcch-BlindDetectionSCG-UE1-r16 INTEGER (0..15), pdcch-BlindDetectionSCG-UE2-r16 INTEGER (0..15) } OPTIONAL, -- R1 18-5 cross-carrier scheduling with different SCS in DL CA crossCarrierSchedulingDL-DiffSCS-r16 ENUMERATED {low-to-high, high-to-low, both} OPTIONAL, -- R1 18-5a Default QCL assumption for cross-carrier scheduling crossCarrierSchedulingDefaultQCL-r16 ENUMERATED {diff-only, both} OPTIONAL, -- R1 18-5b cross-carrier scheduling with different SCS in UL CA crossCarrierSchedulingUL-DiffSCS-r16 ENUMERATED {low-to-high, high-to-low, both} OPTIONAL, -- R1 13.19a Simultaneous positioning SRS and MIMO SRS transmission for a given BC simul-SRS-MIMO-Trans-BC-r16 ENUMERATED {n2} OPTIONAL, -- R1 16-3a, 16-3a-1, 16-3b, 16-3b-1: New Individual Codebook codebookParametersAdditionPerBC-r16 CodebookParametersAdditionPerBC-r16 OPTIONAL, -- R1 16-8: Mixed codebook codebookComboParametersAdditionPerBC-r16 CodebookComboParametersAdditionPerBC-r16 OPTIONAL } CA-ParametersNR-v1630 ::= SEQUENCE { -- R1 22-5b: Simultaneous transmission of SRS for antenna switching and SRS for CB/NCB /BM for inter-band UL CA -- R1 22-5d: Simultaneous transmission of SRS for antenna switching for inter-band UL CA simulTX-SRS-AntSwitchingInterBandUL-CA-r16 SimulSRS-ForAntennaSwitching-r16 OPTIONAL, -- R4 8-5: supported beam management type for inter-band CA beamManagementType-r16 ENUMERATED {ibm, cbm} OPTIONAL, -- R4 7-3a: UL frequency separation class with aggregate BW and Gap BW intraBandFreqSeparationUL-AggBW-GapBW-r16 ENUMERATED {classI, classII, classIII} OPTIONAL, -- RAN 89: Case B in case of Inter-band CA with non-aligned frame boundaries interCA-NonAlignedFrame-B-r16 ENUMERATED {supported} OPTIONAL } CA-ParametersNR-v1640 ::= SEQUENCE { -- R4 7-5: Support of reporting UL Tx DC locations for uplink intra-band CA. uplinkTxDC-TwoCarrierReport-r16 ENUMERATED {supported} OPTIONAL, -- RAN 22-6: Support of up to 3 different numerologies in the same NR PUCCH group for NR part of EN-DC, NGEN-DC, NE-DC and NR-CA -- where UE is not configured with two NR PUCCH groups maxUpTo3Diff-NumerologiesConfigSinglePUCCH-grp-r16 PUCCH-Grp-CarrierTypes-r16 OPTIONAL, -- RAN 22-6a: Support of up to 4 different numerologies in the same NR PUCCH group for NR part of EN-DC, NGEN-DC, NE-DC and NR-CA -- where UE is not configured with two NR PUCCH groups maxUpTo4Diff-NumerologiesConfigSinglePUCCH-grp-r16 PUCCH-Grp-CarrierTypes-r16 OPTIONAL, -- RAN 22-7: Support two PUCCH groups for NR-CA with 3 or more bands with at least two carrier types twoPUCCH-Grp-ConfigurationsList-r16 SEQUENCE (SIZE (1..maxTwoPUCCH-Grp-ConfigList-r16)) OF TwoPUCCH-Grp-Configurations-r16 OPTIONAL, -- R1 22-7a: Different numerology across NR PUCCH groups diffNumerologyAcrossPUCCH-Group-CarrierTypes-r16 ENUMERATED {supported} OPTIONAL, -- R1 22-7b: Different numerologies across NR carriers within the same NR PUCCH group, with PUCCH on a carrier of smaller SCS diffNumerologyWithinPUCCH-GroupSmallerSCS-CarrierTypes-r16 ENUMERATED {supported} OPTIONAL, -- R1 22-7c: Different numerologies across NR carriers within the same NR PUCCH group, with PUCCH on a carrier of larger SCS diffNumerologyWithinPUCCH-GroupLargerSCS-CarrierTypes-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-2f: add the replicated FGs of 11-2a/c with restriction for non-aligned span case -- with DL CA with Rel-16 PDCCH monitoring capability on all the serving cells pdcch-MonitoringCA-NonAlignedSpan-r16 INTEGER (2..16) OPTIONAL, -- R1 11-2g: add the replicated FGs of 11-2a/c with restriction for non-aligned span case pdcch-BlindDetectionCA-Mixed-NonAlignedSpan-r16 SEQUENCE { pdcch-BlindDetectionCA1-r16 INTEGER (1..15), pdcch-BlindDetectionCA2-r16 INTEGER (1..15) } OPTIONAL } CA-ParametersNR-v1690 ::= SEQUENCE { csi-ReportingCrossPUCCH-Grp-r16 SEQUENCE { computationTimeForA-CSI-r16 ENUMERATED {sameAsNoCross, relaxed}, additionalSymbols-r16 SEQUENCE { scs-15kHz-additionalSymbols-r16 ENUMERATED {sl4, s28} OPTIONAL, scs-30kHz-additionalSymbols-r16 ENUMERATED {sl4, s28} OPTIONAL, scs-60kHz-additionalSymbols-r16 ENUMERATED {sl4, s28, s56} OPTIONAL, scs-120kHz-additionalSymbols-r16 ENUMERATED {sl4, s28, s56} OPTIONAL } OPTIONAL, sp-CSI-ReportingOnPUCCH-r16 ENUMERATED {supported} OPTIONAL, sp-CSI-ReportingOnPUSCH-r16 ENUMERATED {supported} OPTIONAL, carrierTypePairList-r16 SEQUENCE (SIZE (1..maxCarrierTypePairList-r16)) OF CarrierTypePair-r16 } OPTIONAL } CA-ParametersNR-v16a0 ::= SEQUENCE { pdcch-BlindDetectionMixedList-r16 SEQUENCE(SIZE(1..maxNrofPdcch-BlindDetectionMixed-1-r16))OF PDCCH-BlindDetectionMixedList-r16 } SimulSRS-ForAntennaSwitching-r16 ::= SEQUENCE { supportSRS-xTyR-xLessThanY-r16 ENUMERATED {supported} OPTIONAL, supportSRS-xTyR-xEqualToY-r16 ENUMERATED {supported} OPTIONAL, supportSRS-AntennaSwitching-r16 ENUMERATED {supported} OPTIONAL } TwoPUCCH-Grp-Configurations-r16 ::= SEQUENCE { pucch-PrimaryGroupMapping-r16 TwoPUCCH-Grp-ConfigParams-r16, pucch-SecondaryGroupMapping-r16 TwoPUCCH-Grp-ConfigParams-r16 } TwoPUCCH-Grp-ConfigParams-r16 ::= SEQUENCE { pucch-GroupMapping-r16 PUCCH-Grp-CarrierTypes-r16, pucch-TX-r16 PUCCH-Grp-CarrierTypes-r16 } CarrierTypePair-r16 ::= SEQUENCE { carrierForCSI-Measurement-r16 PUCCH-Grp-CarrierTypes-r16, carrierForCSI-Reporting-r16 PUCCH-Grp-CarrierTypes-r16 } PUCCH-Grp-CarrierTypes-r16 ::= SEQUENCE { fr1-NonSharedTDD-r16 ENUMERATED {supported} OPTIONAL, fr1-SharedTDD-r16 ENUMERATED {supported} OPTIONAL, fr1-NonSharedFDD-r16 ENUMERATED {supported} OPTIONAL, fr2-r16 ENUMERATED {supported} OPTIONAL } PDCCH-BlindDetectionMixedList-r16::= SEQUENCE { pdcch-BlindDetectionCA-MixedExt-r16 CHOICE { pdcch-BlindDetectionCA-Mixed-v16a0 PDCCH-BlindDetectionCA-MixedExt-r16, pdcch-BlindDetectionCA-Mixed-NonAlignedSpan-v16a0 PDCCH-BlindDetectionCA-MixedExt-r16 } OPTIONAL, pdcch-BlindDetectionCG-UE-MixedExt-r16 SEQUENCE{ pdcch-BlindDetectionMCG-UE-Mixed-v16a0 PDCCH-BlindDetectionCG-UE-MixedExt-r16, pdcch-BlindDetectionSCG-UE-Mixed-v16a0 PDCCH-BlindDetectionCG-UE-MixedExt-r16 } OPTIONAL } PDCCH-BlindDetectionCA-MixedExt-r16 ::= SEQUENCE { pdcch-BlindDetectionCA1-r16 INTEGER (1..15), pdcch-BlindDetectionCA2-r16 INTEGER (1..15) } PDCCH-BlindDetectionCG-UE-MixedExt-r16 ::= SEQUENCE { pdcch-BlindDetectionCG-UE1-r16 INTEGER (0..15), pdcch-BlindDetectionCG-UE2-r16 INTEGER (0..15) } -- TAG-CA-PARAMETERSNR-STOP -- ASN1STOP
CA-ParametersNR field description |
---|
codebookParametersPerBC For a given supported band combination, this field indicates the alternative list of SupportedCSI-RS-Resource supported for each codebook type, amongst the supported CSI-RS resources included in codebookParametersPerBand in MIMO-ParametersPerBand. |
The IE CA-ParametersNRDC contains dual connectivity related capabilities that are defined per band combination.
-- ASN1START -- TAG-CA-PARAMETERS-NRDC-START CA-ParametersNRDC ::= SEQUENCE { ca-ParametersNR-ForDC CA-ParametersNR OPTIONAL, ca-ParametersNR-ForDC-v1540 CA-ParametersNR-v1540 OPTIONAL, ca-ParametersNR-ForDC-v1550 CA-ParametersNR-v1550 OPTIONAL, ca-ParametersNR-ForDC-v1560 CA-ParametersNR-v1560 OPTIONAL,featureSetCombinationDCIf this field is present for a band combination, it reports the feature set combination supported for the band combination when NR-DC is configured. If this field is absent for a band combination, the featureSetCombination in BandCombination (without suffix) is applicable to the UE configured with NR-DC for the band combination.FeatureSetCombinationId OPTIONAL } CA-ParametersNRDC-v15g0 ::= SEQUENCE { ca-ParametersNR-ForDC-v15g0 CA-ParametersNR-v15g0 OPTIONAL } CA-ParametersNRDC-v1610 ::= SEQUENCE { -- R1 18-1: Semi-static power sharing mode1 between MCG and SCG cells of same FR for NR dual connectivity intraFR-NR-DC-PwrSharingMode1-r16 ENUMERATED {supported} OPTIONAL, -- R1 18-1a: Semi-static power sharing mode 2 between MCG and SCG cells of same FR for NR dual connectivity intraFR-NR-DC-PwrSharingMode2-r16 ENUMERATED {supported} OPTIONAL, -- R1 18-1b: Dynamic power sharing between MCG and SCG cells of same FR for NR dual connectivity intraFR-NR-DC-DynamicPwrSharing-r16 ENUMERATED {short, long} OPTIONAL, asyncNRDC-r16 ENUMERATED {supported} OPTIONAL } CA-ParametersNRDC-v1630 ::= SEQUENCE { ca-ParametersNR-ForDC-v1610 CA-ParametersNR-v1610 OPTIONAL, ca-ParametersNR-ForDC-v1630 CA-ParametersNR-v1630 OPTIONAL } CA-ParametersNRDC-v1640 ::= SEQUENCE { ca-ParametersNR-ForDC-v1640 CA-ParametersNR-v1640 OPTIONAL } CA-ParametersNRDC-v1650 ::= SEQUENCE { supportedCellGrouping-r16 BIT STRING (SIZE (1..maxCellGroupings-r16)) OPTIONAL } CA-ParametersNRDC-v16a0 ::= SEQUENCE { ca-ParametersNR-ForDC-v16a0 CA-ParametersNR-v16a0 OPTIONAL } -- TAG-CA-PARAMETERS-NRDC-STOP -- ASN1STOP
CA-ParametersNRDC field descriptions |
---|
ca-ParametersNR-forDC (with and without suffix) If this field is present for a band combination, it reports the UE capabilities when NR-DC is configured with the band combination. If a version of this field (i.e., with or without suffix) is absent for a band combination, the corresponding ca-ParametersNR field version in BandCombinationis applicable to the UE configured with NR-DC for the band combination. If a version of this field (i.e., with or without suffix) is present for a band combination but does not contain any parameters, the UE does not support the corresponding field version when configured with NR-DC for the band combination. |
featureSetCombinationDC If this field is present for a band combination, it reports the feature set combination supported for the band combination when NR-DC is configured. If this field is absent for a band combination, the featureSetCombination in BandCombination (without suffix) is applicable to the UE configured with NR-DC for the band combination. |
The IE CarrierAggregationVariant informs the network about supported "placement" of the SpCell in an NR cell group.
-- ASN1START -- TAG-CARRIERAGGREGATIONVARIANT-START CarrierAggregationVariant ::= SEQUENCE { fr1fdd-FR1TDD-CA-SpCellOnFR1FDD ENUMERATED {supported} OPTIONAL, fr1fdd-FR1TDD-CA-SpCellOnFR1TDD ENUMERATED {supported} OPTIONAL, fr1fdd-FR2TDD-CA-SpCellOnFR1FDD ENUMERATED {supported} OPTIONAL, fr1fdd-FR2TDD-CA-SpCellOnFR2TDD ENUMERATED {supported} OPTIONAL, fr1tdd-FR2TDD-CA-SpCellOnFR1TDD ENUMERATED {supported} OPTIONAL, fr1tdd-FR2TDD-CA-SpCellOnFR2TDD ENUMERATED {supported} OPTIONAL, fr1fdd-FR1TDD-FR2TDD-CA-SpCellOnFR1FDD ENUMERATED {supported} OPTIONAL, fr1fdd-FR1TDD-FR2TDD-CA-SpCellOnFR1TDD ENUMERATED {supported} OPTIONAL, fr1fdd-FR1TDD-FR2TDD-CA-SpCellOnFR2TDD ENUMERATED {supported} OPTIONAL } -- TAG-CARRIERAGGREGATIONVARIANT-STOP -- ASN1STOP
The IE CodebookParameters is used to convey codebook related parameters.
-- ASN1START -- TAG-CODEBOOKPARAMETERS-START CodebookParameters ::= SEQUENCE { type1 SEQUENCE { singlePanel SEQUENCE { supportedCSI-RS-ResourceList SEQUENCE (SIZE (1.. maxNrofCSI-RS-Resources)) OF SupportedCSI-RS-Resource, modes ENUMERATED {mode1, mode1andMode2}, maxNumberCSI-RS-PerResourceSet INTEGER (1..8) }, multiPanel SEQUENCE { supportedCSI-RS-ResourceList SEQUENCE (SIZE (1.. maxNrofCSI-RS-Resources)) OF SupportedCSI-RS-Resource, modes ENUMERATED {mode1, mode2, both}, nrofPanels ENUMERATED {n2, n4}, maxNumberCSI-RS-PerResourceSet INTEGER (1..8) } OPTIONAL }, type2 SEQUENCE { supportedCSI-RS-ResourceList SEQUENCE (SIZE (1.. maxNrofCSI-RS-Resources)) OF SupportedCSI-RS-Resource, parameterLx INTEGER (2..4), amplitudeScalingType ENUMERATED {wideband, widebandAndSubband}, amplitudeSubsetRestriction ENUMERATED {supported} OPTIONAL } OPTIONAL, type2-PortSelection SEQUENCE { supportedCSI-RS-ResourceList SEQUENCE (SIZE (1.. maxNrofCSI-RS-Resources)) OF SupportedCSI-RS-Resource, parameterLx INTEGER (2..4), amplitudeScalingType ENUMERATED {wideband, widebandAndSubband} } OPTIONAL } CodebookParameters-v1610 ::= SEQUENCE {supportedCSI-RS-ResourceListAlt-r16This field indicates the alternative list of SupportedCSI-RS-Resource supported for each codebook type. The supported CSI-RS resource is indicated by an integer value which pinpoints SupportedCSI-RS-Resource defined in CodebookVariantsList. The value 0 corresponds to the first entry of CodebookVariantsList. The value 1 corresponds to the second entry of CodebookVariantsList, and so on. For each codebook type, the field shall be included in both codebookParametersPerBC(but optional for single CC) and codebookParametersPerBand.SEQUENCE { type1-SinglePanel-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-Resources)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1-MultiPanel-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-Resources)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type2-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-Resources)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type2-PortSelection-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-Resources)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL } OPTIONAL } CodebookParametersAddition-r16 ::= SEQUENCE { etype2-r16 SEQUENCE { -- R1 16-3a Regular eType 2 R=1 etype2R1-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) }, -- R1 16-3a-1 Regular eType 2 R=2 etype2R2-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, -- R1 16-3a-2: Support of parameter combinations 7-8 paramComb7-8-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-3a-3: Support of rank 3,4 rank3-4-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-3a-4: CBSR with soft amplitude restriction amplitudeSubsetRestriction-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, etype2-PS-r16 SEQUENCE { -- R1 16-3b Regular eType 2 R=1 PortSelection etype2R1-PortSelection-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) }, -- R1 16-3b-1 Regular eType 2 R=2 PortSelection etype2R2-PortSelection-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, -- R1 16-3b-2: Support of rank 3,4 rank3-4-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL } CodebookComboParametersAddition-r16 ::= SEQUENCE { -- R1 16-8 Mixed codebook types type1SP-Type2-null-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1SP-Type2PS-null-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1SP-eType2R1-null-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1SP-eType2R2-null-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1SP-eType2R1PS-null-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1SP-eType2R2PS-null-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1SP-Type2-Type2PS-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1MP-Type2-null-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1MP-Type2PS-null-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1MP-eType2R1-null-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1MP-eType2R2-null-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1MP-eType2R1PS-null-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1MP-eType2R2PS-null-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1MP-Type2-Type2PS-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL } CodebookParametersAdditionPerBC-r16::= SEQUENCE { -- R1 16-3a Regular eType 2 R=1 etype2R1-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, -- R1 16-3a-1 Regular eType 2 R=2 etype2R2-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, -- R1 16-3b Regular eType 2 R=1 PortSelection etype2R1-PortSelection-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, -- R1 16-3b-1 Regular eType 2 R=2 PortSelection etype2R2-PortSelection-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL } CodebookComboParametersAdditionPerBC-r16::= SEQUENCE { -- R1 16-8 Mixed codebook types type1SP-Type2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1SP-Type2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1SP-eType2R1-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1SP-eType2R2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1SP-eType2R1PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1SP-eType2R2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1SP-Type2-Type2PS-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-Type2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-Type2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-eType2R1-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-eType2R2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-eType2R1PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-eType2R2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-Type2-Type2PS-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL } CodebookVariantsList-r16 ::= SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesAlt-r16)) OF SupportedCSI-RS-Resource SupportedCSI-RS-Resource ::= SEQUENCE { maxNumberTxPortsPerResource ENUMERATED {p2, p4, p8, p12, p16, p24, p32}, maxNumberResourcesPerBand INTEGER (1..64), totalNumberTxPortsPerBand INTEGER (2..256) } -- TAG-CODEBOOKPARAMETERS-STOP -- ASN1STOP
CodebookParameters field descriptions |
---|
supportedCSI-RS-ResourceListAlt This field indicates the alternative list of SupportedCSI-RS-Resource supported for each codebook type. The supported CSI-RS resource is indicated by an integer value which pinpoints SupportedCSI-RS-Resource defined in CodebookVariantsList. The value 0 corresponds to the first entry of CodebookVariantsList. The value 1 corresponds to the second entry of CodebookVariantsList, and so on. For each codebook type, the field shall be included in both codebookParametersPerBC(but optional for single CC) and codebookParametersPerBand. |
The IE FeatureSetCombination is a two-dimensional matrix of FeatureSet entries. Each FeatureSetsPerBand contains a list of feature sets applicable to the carrier(s) of one band entry of the associated band combination. Across the associated bands, the UE shall support the combination of FeatureSets at the same position in the FeatureSetsPerBand. All FeatureSetsPerBand in one FeatureSetCombination must have the same number of entries. The number of FeatureSetsPerBand in the FeatureSetCombination must be equal to the number of band entries in an associated band combination. The first FeatureSetPerBand applies to the first band entry of the band combination, and so on. Each FeatureSet contains either a pair of NR or E-UTRA feature set IDs for UL and DL. In case of NR,the actual feature sets for UL and DL are defined in the FeatureSets IE and referred to from here by their ID,i.e., their position in the featureSetsUplink / featureSetsDownlink list in the FeatureSet IE. In case of E-UTRA, the feature sets referred to from this list are defined in TS 36.331 [10] and conveyed as part of the UE-EUTRA-Capability container. The FeatureSetUplink and FeatureSetDownlink referred to from the FeatureSet comprise, among other information, a set of FeatureSetUplinkPerCC-Ids and FeatureSetDownlinkPerCC-Ids. The number of these per-CC IDs determines the number of carriers that the UE is able to aggregate contiguously in frequency domain in the corresponding band. The number of carriers supported by the UE is also restricted by the bandwidth class indicated in the associated BandCombination, if present. In feature set combinations the UE shall exclude entries with same or lower capabilities, since the network may anyway assume that the UE supports those.
-- ASN1START -- TAG-FEATURESETCOMBINATION-START FeatureSetCombination ::= SEQUENCE (SIZE (1..maxSimultaneousBands)) OF FeatureSetsPerBand FeatureSetsPerBand ::= SEQUENCE (SIZE (1..maxFeatureSetsPerBand)) OF FeatureSet FeatureSet ::= CHOICE { eutra SEQUENCE { downlinkSetEUTRA FeatureSetEUTRA-DownlinkId, uplinkSetEUTRA FeatureSetEUTRA-UplinkId }, nr SEQUENCE { downlinkSetNR FeatureSetDownlinkId, uplinkSetNR FeatureSetUplinkId } } -- TAG-FEATURESETCOMBINATION-STOP -- ASN1STOP
The IE FeatureSetCombinationId identifies a FeatureSetCombination. The FeatureSetCombinationId of a FeatureSetCombination is the position of the FeatureSetCombination in the featureSetCombinations list (in UE-NR-Capability or UE-MRDC-Capability). The FeatureSetCombinationId = 0 refers to the first entry in the featureSetCombinations list (in UE-NR-Capability or UE-MRDC-Capability).
The IE FeatureSetDownlink indicates a set of features that the UE supports on the carriers corresponding to one band entry in a band combination.
-- ASN1START -- TAG-FEATURESETDOWNLINK-START FeatureSetDownlink ::= SEQUENCE {featureSetListPerDownlinkCCIndicates which features the UE supports on the individual DL carriers of the feature set (and hence of a band entry that refer to the feature set). The UE shall hence include at least as many FeatureSetDownlinkPerCC-Id in this list as the number of carriers it supports according to the ca-BandwidthClassDL, except if indicating additional functionality by reducing the number of FeatureSetDownlinkPerCC-Id in the feature set (see NOTE 1 in FeatureSetCombination IE description). The order of the elements in this list is not relevant, i.e., the network may configure any of the carriers in accordance with any of the FeatureSetDownlinkPerCC-Id in this list.SEQUENCE (SIZE (1..maxNrofServingCells)) OF FeatureSetDownlinkPerCC-Id, intraBandFreqSeparationDL FreqSeparationClass OPTIONAL, scalingFactor ENUMERATED {f0p4, f0p75, f0p8} OPTIONAL, dummy8 ENUMERATED {supported} OPTIONAL, scellWithoutSSB ENUMERATED {supported} OPTIONAL, csi-RS-MeasSCellWithoutSSB ENUMERATED {supported} OPTIONAL, dummy1 ENUMERATED {supported} OPTIONAL, type1-3-CSS ENUMERATED {supported} OPTIONAL, pdcch-MonitoringAnyOccasions ENUMERATED {withoutDCI-Gap, withDCI-Gap} OPTIONAL, dummy2 ENUMERATED {supported} OPTIONAL, ue-SpecificUL-DL-Assignment ENUMERATED {supported} OPTIONAL, searchSpaceSharingCA-DL ENUMERATED {supported} OPTIONAL, timeDurationForQCL SEQUENCE { scs-60kHz ENUMERATED {s7, s14, s28} OPTIONAL, scs-120kHz ENUMERATED {s14, s28} OPTIONAL } OPTIONAL, pdsch-ProcessingType1-DifferentTB-PerSlot SEQUENCE { scs-15kHz ENUMERATED {upto2, upto4, upto7} OPTIONAL, scs-30kHz ENUMERATED {upto2, upto4, upto7} OPTIONAL, scs-60kHz ENUMERATED {upto2, upto4, upto7} OPTIONAL, scs-120kHz ENUMERATED {upto2, upto4, upto7} OPTIONAL } OPTIONAL, dummy3 DummyA OPTIONAL, dummy4 SEQUENCE (SIZE (1.. maxNrofCodebooks)) OF DummyB OPTIONAL, dummy5 SEQUENCE (SIZE (1.. maxNrofCodebooks)) OF DummyC OPTIONAL, dummy6 SEQUENCE (SIZE (1.. maxNrofCodebooks)) OF DummyD OPTIONAL, dummy7 SEQUENCE (SIZE (1.. maxNrofCodebooks)) OF DummyE OPTIONAL } FeatureSetDownlink-v1540 ::= SEQUENCE { oneFL-DMRS-TwoAdditionalDMRS-DL ENUMERATED {supported} OPTIONAL, additionalDMRS-DL-Alt ENUMERATED {supported} OPTIONAL, twoFL-DMRS-TwoAdditionalDMRS-DL ENUMERATED {supported} OPTIONAL, oneFL-DMRS-ThreeAdditionalDMRS-DL ENUMERATED {supported} OPTIONAL, pdcch-MonitoringAnyOccasionsWithSpanGap SEQUENCE { scs-15kHz ENUMERATED {set1, set2, set3} OPTIONAL, scs-30kHz ENUMERATED {set1, set2, set3} OPTIONAL, scs-60kHz ENUMERATED {set1, set2, set3} OPTIONAL, scs-120kHz ENUMERATED {set1, set2, set3} OPTIONAL } OPTIONAL, pdsch-SeparationWithGap ENUMERATED {supported} OPTIONAL, pdsch-ProcessingType2 SEQUENCE { scs-15kHz ProcessingParameters OPTIONAL, scs-30kHz ProcessingParameters OPTIONAL, scs-60kHz ProcessingParameters OPTIONAL } OPTIONAL, pdsch-ProcessingType2-Limited SEQUENCE { differentTB-PerSlot-SCS-30kHz ENUMERATED {upto1, upto2, upto4, upto7} } OPTIONAL, dl-MCS-TableAlt-DynamicIndication ENUMERATED {supported} OPTIONAL } FeatureSetDownlink-v15a0 ::= SEQUENCE {supportedSRS-ResourcesIndicates supported SRS resources for SRS carrier switching to the band associated with this FeatureSetDownlink. The UE is only allowed to set this field for a band with associated FeatureSetUplinkId set to 0.SRS-Resources OPTIONAL } FeatureSetDownlink-v1610 ::= SEQUENCE { -- R1 22-4e/4f/4g/4h: CBG based reception for DL with unicast PDSCH(s) per slot per CC with UE processing time Capability 1 cbgPDSCH-ProcessingType1-DifferentTB-PerSlot-r16 SEQUENCE { scs-15kHz-r16 ENUMERATED {one, upto2, upto4, upto7} OPTIONAL, scs-30kHz-r16 ENUMERATED {one, upto2, upto4, upto7} OPTIONAL, scs-60kHz-r16 ENUMERATED {one, upto2, upto4, upto7} OPTIONAL, scs-120kHz-r16 ENUMERATED {one, upto2, upto4, upto7} OPTIONAL } OPTIONAL, -- R1 22-3e/3f/3g/3h: CBG based reception for DL with unicast PDSCH(s) per slot per CC with UE processing time Capability 2 cbgPDSCH-ProcessingType2-DifferentTB-PerSlot-r16 SEQUENCE { scs-15kHz-r16 ENUMERATED {one, upto2, upto4, upto7} OPTIONAL, scs-30kHz-r16 ENUMERATED {one, upto2, upto4, upto7} OPTIONAL, scs-60kHz-r16 ENUMERATED {one, upto2, upto4, upto7} OPTIONAL, scs-120kHz-r16 ENUMERATED {one, upto2, upto4, upto7} OPTIONAL } OPTIONAL, intraFreqDAPS-r16 SEQUENCE { intraFreqDiffSCS-DAPS-r16 ENUMERATED {supported} OPTIONAL, intraFreqAsyncDAPS-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, intraBandFreqSeparationDL-v1620 FreqSeparationClassDL-v1620 OPTIONAL, intraBandFreqSeparationDL-Only-r16 FreqSeparationClassDL-Only-r16 OPTIONAL, -- R1 11-2: Rel-16 PDCCH monitoring capability pdcch-Monitoring-r16 SEQUENCE { pdsch-ProcessingType1-r16 SEQUENCE { scs-15kHz-r16 PDCCH-MonitoringOccasions-r16 OPTIONAL, scs-30kHz-r16 PDCCH-MonitoringOccasions-r16 OPTIONAL } OPTIONAL, pdsch-ProcessingType2-r16 SEQUENCE { scs-15kHz-r16 PDCCH-MonitoringOccasions-r16 OPTIONAL, scs-30kHz-r16 PDCCH-MonitoringOccasions-r16 OPTIONAL } OPTIONAL } OPTIONAL, -- R1 11-2b: Mix of Rel. 16 PDCCH monitoring capability and Rel. 15 PDCCH monitoring capability on different carriers pdcch-MonitoringMixed-r16 ENUMERATED {supported} OPTIONAL, -- R1 18-5c: Processing up to X unicast DCI scheduling for DL per scheduled CC crossCarrierSchedulingProcessing-DiffSCS-r16 SEQUENCE { scs-15kHz-120kHz-r16 ENUMERATED {n1,n2,n4} OPTIONAL, scs-15kHz-60kHz-r16 ENUMERATED {n1,n2,n4} OPTIONAL, scs-30kHz-120kHz-r16 ENUMERATED {n1,n2,n4} OPTIONAL, scs-15kHz-30kHz-r16 ENUMERATED {n2} OPTIONAL, scs-30kHz-60kHz-r16 ENUMERATED {n2} OPTIONAL, scs-60kHz-120kHz-r16 ENUMERATED {n2} OPTIONAL } OPTIONAL, -- R1 16-2b-1: Support of single-DCI based SDM scheme singleDCI-SDM-scheme-r16 ENUMERATED {supported} OPTIONAL } PDCCH-MonitoringOccasions-r16 ::= SEQUENCE { period7span3-r16 ENUMERATED {supported} OPTIONAL, period4span3-r16 ENUMERATED {supported} OPTIONAL, period2span2-r16 ENUMERATED {supported} OPTIONAL } DummyA ::= SEQUENCE { maxNumberNZP-CSI-RS-PerCC INTEGER (1..32), maxNumberPortsAcrossNZP-CSI-RS-PerCC ENUMERATED {p2, p4, p8, p12, p16, p24, p32, p40, p48, p56, p64, p72, p80, p88, p96, p104, p112, p120, p128, p136, p144, p152, p160, p168, p176, p184, p192, p200, p208, p216, p224, p232, p240, p248, p256}, maxNumberCS-IM-PerCC ENUMERATED {n1, n2, n4, n8, n16, n32}, maxNumberSimultaneousCSI-RS-ActBWP-AllCC ENUMERATED {n5, n6, n7, n8, n9, n10, n12, n14, n16, n18, n20, n22, n24, n26, n28, n30, n32, n34, n36, n38, n40, n42, n44, n46, n48, n50, n52, n54, n56, n58, n60, n62, n64}, totalNumberPortsSimultaneousCSI-RS-ActBWP-AllCC ENUMERATED {p8, p12, p16, p24, p32, p40, p48, p56, p64, p72, p80, p88, p96, p104, p112, p120, p128, p136, p144, p152, p160, p168, p176, p184, p192, p200, p208, p216, p224, p232, p240, p248, p256} } DummyB ::= SEQUENCE { maxNumberTxPortsPerResource ENUMERATED {p2, p4, p8, p12, p16, p24, p32}, maxNumberResources INTEGER (1..64), totalNumberTxPorts INTEGER (2..256), supportedCodebookMode ENUMERATED {mode1, mode1AndMode2}, maxNumberCSI-RS-PerResourceSet INTEGER (1..8) } DummyC ::= SEQUENCE { maxNumberTxPortsPerResource ENUMERATED {p8, p16, p32}, maxNumberResources INTEGER (1..64), totalNumberTxPorts INTEGER (2..256), supportedCodebookMode ENUMERATED {mode1, mode2, both}, supportedNumberPanels ENUMERATED {n2, n4}, maxNumberCSI-RS-PerResourceSet INTEGER (1..8) } DummyD ::= SEQUENCE { maxNumberTxPortsPerResource ENUMERATED {p4, p8, p12, p16, p24, p32}, maxNumberResources INTEGER (1..64), totalNumberTxPorts INTEGER (2..256), parameterLx INTEGER (2..4), amplitudeScalingType ENUMERATED {wideband, widebandAndSubband}, amplitudeSubsetRestriction ENUMERATED {supported} OPTIONAL, maxNumberCSI-RS-PerResourceSet INTEGER (1..8) } DummyE ::= SEQUENCE { maxNumberTxPortsPerResource ENUMERATED {p4, p8, p12, p16, p24, p32}, maxNumberResources INTEGER (1..64), totalNumberTxPorts INTEGER (2..256), parameterLx INTEGER (2..4), amplitudeScalingType ENUMERATED {wideband, widebandAndSubband}, maxNumberCSI-RS-PerResourceSet INTEGER (1..8) } -- TAG-FEATURESETDOWNLINK-STOP -- ASN1STOP
FeatureSetDownlinkfield descriptions |
---|
featureSetListPerDownlinkCC Indicates which features the UE supports on the individual DL carriers of the feature set (and hence of a band entry that refer to the feature set). The UE shall hence include at least as many FeatureSetDownlinkPerCC-Id in this list as the number of carriers it supports according to the ca-BandwidthClassDL, except if indicating additional functionality by reducing the number of FeatureSetDownlinkPerCC-Id in the feature set (see NOTE 1 in FeatureSetCombination IE description). The order of the elements in this list is not relevant, i.e., the network may configure any of the carriers in accordance with any of the FeatureSetDownlinkPerCC-Id in this list. |
supportedSRS-Resources Indicates supported SRS resources for SRS carrier switching to the band associated with this FeatureSetDownlink. The UE is only allowed to set this field for a band with associated FeatureSetUplinkId set to 0. |
The IE FeatureSetDownlinkId identifies a downlink feature set. The FeatureSetDownlinkId of a FeatureSetDownlink is the index position of the FeatureSetDownlink in the featureSetsDownlink list in the FeatureSets IE. The first element in that list is referred to by FeatureSetDownlinkId = 1. The FeatureSetDownlinkId=0 is not used by an actual FeatureSetDownlink but means that the UE does not support a carrier in this band of a band combination.
The IE FeatureSetDownlinkPerCC indicates a set of features that the UE supports on the corresponding carrier of one band entry of a band combination.
-- ASN1START -- TAG-FEATURESETDOWNLINKPERCC-START FeatureSetDownlinkPerCC ::= SEQUENCE { supportedSubcarrierSpacingDL SubcarrierSpacing, supportedBandwidthDL SupportedBandwidth, channelBW-90mhz ENUMERATED {supported} OPTIONAL, maxNumberMIMO-LayersPDSCH MIMO-LayersDL OPTIONAL, supportedModulationOrderDL ModulationOrder OPTIONAL } FeatureSetDownlinkPerCC-v1620 ::= SEQUENCE { -- R1 16-2a: Mulit-DCI based multi-TRP multiDCI-MultiTRP-r16 MultiDCI-MultiTRP-r16 OPTIONAL, -- R1 16-2b-3: Support of single-DCI based FDMSchemeB supportFDM-SchemeB-r16 ENUMERATED {supported} OPTIONAL } MultiDCI-MultiTRP-r16 ::= SEQUENCE { maxNumberCORESET-r16 ENUMERATED {n2, n3, n4, n5}, maxNumberCORESETPerPoolIndex-r16 INTEGER (1..3), maxNumberUnicastPDSCH-PerPool-r16 ENUMERATED {n1, n2, n3, n4, n7} } -- TAG-FEATURESETDOWNLINKPERCC-STOP -- ASN1STOP
The IE FeatureSetDownlinkPerCC-Id identifies a set of features applicable to one carrier of a feature set. The FeatureSetDownlinkPerCC-Id of a FeatureSetDownlinkPerCC is the index position of the FeatureSetDownlinkPerCC in the featureSetsDownlinkPerCC. The first element in the list is referred to by FeatureSetDownlinkPerCC-Id = 1, and so on.
The IE FeatureSetEUTRA-DownlinkId identifies a downlink feature set in E-UTRA list (see TS 36.331 [10]. The first element in that list is referred to by FeatureSetEUTRA-DownlinkId = 1. The FeatureSetEUTRA-DownlinkId=0 is used when the UE does not support a carrier in this band of a band combination.
The IE FeatureSetEUTRA-UplinkId identifies an uplink feature set in E-UTRA list (see TS 36.331 [10]. The first element in that list is referred to by FeatureSetEUTRA-UplinkId = 1. The FeatureSetEUTRA-UplinkId =0 is used when the UE does not support a carrier in this band of a band combination.
The IE FeatureSets is used to provide pools of downlink and uplink features sets. A FeatureSetCombination refers to the IDs of the feature set(s) that the UE supports in that FeatureSetCombination. The BandCombination entries in the BandCombinationList then indicate the ID of the FeatureSetCombination that the UE supports for that band combination. The entries in the lists in this IE are identified by their index position. For example, the FeatureSetUplinkPerCC-Id = 4 identifies the 4th element in the featureSetsUplinkPerCC list.
-- ASN1START -- TAG-FEATURESETS-START FeatureSets ::= SEQUENCE { featureSetsDownlink SEQUENCE (SIZE (1..maxDownlinkFeatureSets)) OF FeatureSetDownlink OPTIONAL, featureSetsDownlinkPerCC SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetDownlinkPerCC OPTIONAL, featureSetsUplink SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink OPTIONAL, featureSetsUplinkPerCC SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetUplinkPerCC OPTIONAL, ..., [[ featureSetsDownlink-v1540 SEQUENCE (SIZE (1..maxDownlinkFeatureSets)) OF FeatureSetDownlink-v1540 OPTIONAL, featureSetsUplink-v1540 SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink-v1540 OPTIONAL, featureSetsUplinkPerCC-v1540 SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetUplinkPerCC-v1540 OPTIONAL ]], [[ featureSetsDownlink-v15a0 SEQUENCE (SIZE (1..maxDownlinkFeatureSets)) OF FeatureSetDownlink-v15a0 OPTIONAL ]], [[ featureSetsDownlink-v1610 SEQUENCE (SIZE (1..maxDownlinkFeatureSets)) OF FeatureSetDownlink-v1610 OPTIONAL, featureSetsUplink-v1610 SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink-v1610 OPTIONAL, featureSetDownlinkPerCC-v1620 SEQUENCE (SIZE (1..maxPerCC-FeatureSets)) OF FeatureSetDownlinkPerCC-v1620 OPTIONAL ]], [[ featureSetsUplink-v1630 SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink-v1630 OPTIONAL ]], [[ featureSetsUplink-v1640 SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink-v1640 OPTIONAL ]] } FeatureSets-v16d0 ::= SEQUENCE { featureSetsUplink-v16d0 SEQUENCE (SIZE (1..maxUplinkFeatureSets)) OF FeatureSetUplink-v16d0 OPTIONAL } -- TAG-FEATURESETS-STOP -- ASN1STOP
The IE FeatureSetUplink is used to indicate the features that the UE supports on the carriers corresponding to one band entry in a band combination.
-- ASN1START -- TAG-FEATURESETUPLINK-START FeatureSetUplink ::= SEQUENCE {featureSetListPerUplinkCCIndicates which features the UE supports on the individual UL carriers of the feature set (and hence of a band entry that refers to the feature set). The UE shall hence include at least as many FeatureSetUplinkPerCC-Id in this list as the number of carriers it supports according to the ca-BandwidthClassUL, except if indicating additional functionality by reducing the number of FeatureSetUplinkPerCC-Id in the feature set (see NOTE 1 in FeatureSetCombination IE description). The order of the elements in this list is not relevant, i.e., the network may configure any of the carriers in accordance with any of the FeatureSetUplinkPerCC-Id in this list.SEQUENCE (SIZE (1.. maxNrofServingCells)) OF FeatureSetUplinkPerCC-Id, scalingFactor ENUMERATED {f0p4, f0p75, f0p8} OPTIONAL, dummy3 ENUMERATED {supported} OPTIONAL, intraBandFreqSeparationUL FreqSeparationClass OPTIONAL, searchSpaceSharingCA-UL ENUMERATED {supported} OPTIONAL, dummy1 DummyI OPTIONAL, supportedSRS-Resources SRS-Resources OPTIONAL, twoPUCCH-Group ENUMERATED {supported} OPTIONAL, dynamicSwitchSUL ENUMERATED {supported} OPTIONAL, simultaneousTxSUL-NonSUL ENUMERATED {supported} OPTIONAL, pusch-ProcessingType1-DifferentTB-PerSlot SEQUENCE { scs-15kHz ENUMERATED {upto2, upto4, upto7} OPTIONAL, scs-30kHz ENUMERATED {upto2, upto4, upto7} OPTIONAL, scs-60kHz ENUMERATED {upto2, upto4, upto7} OPTIONAL, scs-120kHz ENUMERATED {upto2, upto4, upto7} OPTIONAL } OPTIONAL, dummy2 DummyF OPTIONAL } FeatureSetUplink-v1540 ::= SEQUENCE { zeroSlotOffsetAperiodicSRS ENUMERATED {supported} OPTIONAL, pa-PhaseDiscontinuityImpacts ENUMERATED {supported} OPTIONAL, pusch-SeparationWithGap ENUMERATED {supported} OPTIONAL, pusch-ProcessingType2 SEQUENCE { scs-15kHz ProcessingParameters OPTIONAL, scs-30kHz ProcessingParameters OPTIONAL, scs-60kHz ProcessingParameters OPTIONAL } OPTIONAL, ul-MCS-TableAlt-DynamicIndication ENUMERATED {supported} OPTIONAL } FeatureSetUplink-v1610 ::= SEQUENCE { -- R1 11-5: PUsCH repetition Type B pusch-RepetitionTypeB-r16 SEQUENCE { maxNumberPUSCH-Tx-r16 ENUMERATED {n2, n3, n4, n7, n8, n12}, hoppingScheme-r16 ENUMERATED {interSlotHopping, interRepetitionHopping, both} } OPTIONAL, -- R1 11-7: UL cancelation scheme for self-carrier ul-CancellationSelfCarrier-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-7a: UL cancelation scheme for cross-carrier ul-CancellationCrossCarrier-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-5c: The maximum number of SRS resources in one SRS resource set with usage set to 'codebook' for Mode 2 ul-FullPwrMode2-MaxSRS-ResInSet-r16 ENUMERATED {n1, n2, n4} OPTIONAL, -- R1 22-4a/4b/4c/4d: CBG based transmission for UL with unicast PUSCH(s) per slot per CC with UE processing time Capability 1 cbgPUSCH-ProcessingType1-DifferentTB-PerSlot-r16 SEQUENCE { scs-15kHz-r16 ENUMERATED {one-pusch, upto2, upto4, upto7} OPTIONAL, scs-30kHz-r16 ENUMERATED {one-pusch, upto2, upto4, upto7} OPTIONAL, scs-60kHz-r16 ENUMERATED {one-pusch, upto2, upto4, upto7} OPTIONAL, scs-120kHz-r16 ENUMERATED {one-pusch, upto2, upto4, upto7} OPTIONAL } OPTIONAL, -- R1 22-3a/3b/3c/3d: CBG based transmission for UL with unicast PUSCH(s) per slot per CC with UE processing time Capability 2 cbgPUSCH-ProcessingType2-DifferentTB-PerSlot-r16 SEQUENCE { scs-15kHz-r16 ENUMERATED {one-pusch, upto2, upto4, upto7} OPTIONAL, scs-30kHz-r16 ENUMERATED {one-pusch, upto2, upto4, upto7} OPTIONAL, scs-60kHz-r16 ENUMERATED {one-pusch, upto2, upto4, upto7} OPTIONAL, scs-120kHz-r16 ENUMERATED {one-pusch, upto2, upto4, upto7} OPTIONAL } OPTIONAL, supportedSRS-PosResources-r16 SRS-AllPosResources-r16 OPTIONAL, intraFreqDAPS-UL-r16 SEQUENCE { dummy ENUMERATED {supported} OPTIONAL, intraFreqTwoTAGs-DAPS-r16 ENUMERATED {supported} OPTIONAL, dummy1 ENUMERATED {supported} OPTIONAL, dummy2 ENUMERATED {supported} OPTIONAL, dummy3 ENUMERATED {short, long} OPTIONAL } OPTIONAL, intraBandFreqSeparationUL-v1620 FreqSeparationClassUL-v1620 OPTIONAL, -- R1 11-3: More than one PUCCH for HARQ-ACK transmission within a slot multiPUCCH-r16 SEQUENCE { sub-SlotConfig-NCP-r16 ENUMERATED {set1, set2} OPTIONAL, sub-SlotConfig-ECP-r16 ENUMERATED {set1, set2} OPTIONAL } OPTIONAL, -- R1 11-3c: 2 PUCCH of format 0 or 2 for a single 7*2-symbol subslot based HARQ-ACK codebook twoPUCCH-Type1-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-3d: 2 PUCCH of format 0 or 2 for a single 2*7-symbol subslot based HARQ-ACK codebook twoPUCCH-Type2-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-3e: 1 PUCCH format 0 or 2 and 1 PUCCH format 1, 3 or 4 in the same subslot for a single 2*7-symbol HARQ-ACK codebooks twoPUCCH-Type3-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-3f: 2 PUCCH transmissions in the same subslot for a single 2*7-symbol HARQ-ACK codebooks which are not covered by 11-3d and -- 11-3e twoPUCCH-Type4-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-3g: SR/HARQ-ACK multiplexing once per subslot using a PUCCH (or HARQ-ACK piggybacked on a PUSCH) when SR/HARQ-ACK -- are supposed to be sent with different starting symbols in a subslot mux-SR-HARQ-ACK-r16 ENUMERATED {supported} OPTIONAL, dummy1 ENUMERATED {supported} OPTIONAL, dummy2 ENUMERATED {supported} OPTIONAL, -- R1 11-4c: 2 PUCCH of format 0 or 2 for two HARQ-ACK codebooks with one 7*2-symbol sub-slot based HARQ-ACK codebook twoPUCCH-Type5-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-4d: 2 PUCCH of format 0 or 2 in consecutive symbols for two HARQ-ACK codebooks with one 2*7-symbol sub-slot based HARQ-ACK -- codebook twoPUCCH-Type6-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-4e: 2 PUCCH of format 0 or 2 for two subslot based HARQ-ACK codebooks twoPUCCH-Type7-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-4f: 1 PUCCH format 0 or 2 and 1 PUCCH format 1, 3 or 4 in the same subslot for HARQ-ACK codebooks with one 2*7-symbol -- subslot based HARQ-ACK codebook twoPUCCH-Type8-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-4g: 1 PUCCH format 0 or 2 and 1 PUCCH format 1, 3 or 4 in the same subslot for two subslot based HARQ-ACK codebooks twoPUCCH-Type9-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-4h: 2 PUCCH transmissions in the same subslot for two HARQ-ACK codebooks with one 2*7-symbol subslot which are not covered -- by 11-4c and 11-4e twoPUCCH-Type10-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-4i: 2 PUCCH transmissions in the same subslot for two subslot based HARQ-ACK codebooks which are not covered by 11-4d and -- 11-4f twoPUCCH-Type11-r16 ENUMERATED {supported} OPTIONAL, -- R1 12-1: UL intra-UE multiplexing/prioritization of overlapping channel/signals with two priority levels in physical layer ul-IntraUE-Mux-r16 SEQUENCE { pusch-PreparationLowPriority-r16 ENUMERATED {sym0, sym1, sym2}, pusch-PreparationHighPriority-r16 ENUMERATED {sym0, sym1, sym2} } OPTIONAL, -- R1 16-5a: Supported UL full power transmission mode of fullpower ul-FullPwrMode-r16 ENUMERATED {supported} OPTIONAL, -- R1 18-5d: Processing up to X unicast DCI scheduling for UL per scheduled CC crossCarrierSchedulingProcessing-DiffSCS-r16 SEQUENCE { scs-15kHz-120kHz-r16 ENUMERATED {n1,n2,n4} OPTIONAL, scs-15kHz-60kHz-r16 ENUMERATED {n1,n2,n4} OPTIONAL, scs-30kHz-120kHz-r16 ENUMERATED {n1,n2,n4} OPTIONAL, scs-15kHz-30kHz-r16 ENUMERATED {n2} OPTIONAL, scs-30kHz-60kHz-r16 ENUMERATED {n2} OPTIONAL, scs-60kHz-120kHz-r16 ENUMERATED {n2} OPTIONAL } OPTIONAL, -- R1 16-5b: Supported UL full power transmission mode of fullpowerMode1 ul-FullPwrMode1-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-5c-2: Ports configuration for Mode 2 ul-FullPwrMode2-SRSConfig-diffNumSRSPorts-r16 ENUMERATED {p1-2, p1-4, p1-2-4} OPTIONAL, -- R1 16-5c-3: TPMI group for Mode 2 ul-FullPwrMode2-TPMIGroup-r16 SEQUENCE { twoPorts-r16 BIT STRING(SIZE(2)) OPTIONAL, fourPortsNonCoherent-r16 ENUMERATED{g0, g1, g2, g3} OPTIONAL, fourPortsPartialCoherent-r16 ENUMERATED{g0, g1, g2, g3, g4, g5, g6} OPTIONAL } OPTIONAL } FeatureSetUplink-v1630 ::= SEQUENCE { -- R1 22-8: For SRS for CB PUSCH and antenna switching on FR1 with symbol level offset for aperiodic SRS transmission offsetSRS-CB-PUSCH-Ant-Switch-fr1-r16 ENUMERATED {supported} OPTIONAL, -- R1 22-8a: PDCCH monitoring on any span of up to 3 consecutive OFDM symbols of a slot and constrained timeline for SRS for CB -- PUSCH and antenna switching on FR1 offsetSRS-CB-PUSCH-PDCCH-MonitorSingleOcc-fr1-r16 ENUMERATED {supported} OPTIONAL, -- R1 22-8b: For type 1 CSS with dedicated RRC configuration, type 3 CSS, and UE-SS, monitoring occasion can be any OFDM symbol(s) -- of a slot for Case 2 and constrained timeline for SRS for CB PUSCH and antenna switching on FR1 offsetSRS-CB-PUSCH-PDCCH-MonitorAnyOccWithoutGap-fr1-r16 ENUMERATED {supported} OPTIONAL, -- R1 22-8c: For type 1 CSS with dedicated RRC configuration, type 3 CSS, and UE-SS, monitoring occasion can be any OFDM symbol(s) -- of a slot for Case 2 with a DCI gap and constrained timeline for SRS for CB PUSCH and antenna switching on FR1 offsetSRS-CB-PUSCH-PDCCH-MonitorAnyOccWithGap-fr1-r16 ENUMERATED {supported} OPTIONAL, dummy ENUMERATED {supported} OPTIONAL, -- R1 22-9: Cancellation of PUCCH, PUSCH or PRACH with a DCI scheduling a PDSCH or CSI-RS or a DCI format 2_0 for SFI partialCancellationPUCCH-PUSCH-PRACH-TX-r16 ENUMERATED {supported} OPTIONAL } FeatureSetUplink-v1640 ::= SEQUENCE { -- R1 11-4: Two HARQ-ACK codebooks with up to one sub-slot based HARQ-ACK codebook (i.e. slot-based + slot-based, or slot-based + -- sub-slot based) simultaneously constructed for supporting HARQ-ACK codebooks with different priorities at a UE twoHARQ-ACK-Codebook-type1-r16 SubSlot-Config-r16 OPTIONAL, -- R1 11-4a: Two sub-slot based HARQ-ACK codebooks simultaneously constructed for supporting HARQ-ACK codebooks with different -- priorities at a UE twoHARQ-ACK-Codebook-type2-r16 SubSlot-Config-r16 OPTIONAL, -- R1 22-8d: All PDCCH monitoring occasion can be any OFDM symbol(s) of a slot for Case 2 with a span gap and constrained timeline -- for SRS for CB PUSCH and antenna switching on FR1 offsetSRS-CB-PUSCH-PDCCH-MonitorAnyOccWithSpanGap-fr1-r16 SEQUENCE { scs-15kHz-r16 ENUMERATED {set1, set2, set3} OPTIONAL, scs-30kHz-r16 ENUMERATED {set1, set2, set3} OPTIONAL, scs-60kHz-r16 ENUMERATED {set1, set2, set3} OPTIONAL } OPTIONAL } FeatureSetUplink-v16d0 ::= SEQUENCE { pusch-RepetitionTypeB-v16d0 SEQUENCE { maxNumberPUSCH-Tx-Cap1-r16 ENUMERATED {n2, n3, n4, n7, n8, n12}, maxNumberPUSCH-Tx-Cap2-r16 ENUMERATED {n2, n3, n4, n7, n8, n12} } OPTIONAL } SubSlot-Config-r16 ::= SEQUENCE { sub-SlotConfig-NCP-r16 ENUMERATED {n4,n5,n6,n7} OPTIONAL, sub-SlotConfig-ECP-r16 ENUMERATED {n4,n5,n6} OPTIONAL } SRS-AllPosResources-r16 ::= SEQUENCE { srs-PosResources-r16 SRS-PosResources-r16, srs-PosResourceAP-r16 SRS-PosResourceAP-r16 OPTIONAL, srs-PosResourceSP-r16 SRS-PosResourceSP-r16 OPTIONAL } SRS-PosResources-r16 ::= SEQUENCE { maxNumberSRS-PosResourceSetPerBWP-r16 ENUMERATED {n1, n2, n4, n8, n12, n16}, maxNumberSRS-PosResourcesPerBWP-r16 ENUMERATED {n1, n2, n4, n8, n16, n32, n64}, maxNumberSRS-ResourcesPerBWP-PerSlot-r16 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14}, maxNumberPeriodicSRS-PosResourcesPerBWP-r16 ENUMERATED {n1, n2, n4, n8, n16, n32, n64}, maxNumberPeriodicSRS-PosResourcesPerBWP-PerSlot-r16 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14} } SRS-PosResourceAP-r16 ::= SEQUENCE { maxNumberAP-SRS-PosResourcesPerBWP-r16 ENUMERATED {n1, n2, n4, n8, n16, n32, n64}, maxNumberAP-SRS-PosResourcesPerBWP-PerSlot-r16 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14} } SRS-PosResourceSP-r16 ::= SEQUENCE { maxNumberSP-SRS-PosResourcesPerBWP-r16 ENUMERATED {n1, n2, n4, n8, n16, n32, n64}, maxNumberSP-SRS-PosResourcesPerBWP-PerSlot-r16 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14} } SRS-Resources ::= SEQUENCE { maxNumberAperiodicSRS-PerBWP ENUMERATED {n1, n2, n4, n8, n16}, maxNumberAperiodicSRS-PerBWP-PerSlot INTEGER (1..6), maxNumberPeriodicSRS-PerBWP ENUMERATED {n1, n2, n4, n8, n16}, maxNumberPeriodicSRS-PerBWP-PerSlot INTEGER (1..6), maxNumberSemiPersistentSRS-PerBWP ENUMERATED {n1, n2, n4, n8, n16}, maxNumberSemiPersistentSRS-PerBWP-PerSlot INTEGER (1..6), maxNumberSRS-Ports-PerResource ENUMERATED {n1, n2, n4} } DummyF ::= SEQUENCE { maxNumberPeriodicCSI-ReportPerBWP INTEGER (1..4), maxNumberAperiodicCSI-ReportPerBWP INTEGER (1..4), maxNumberSemiPersistentCSI-ReportPerBWP INTEGER (0..4), simultaneousCSI-ReportsAllCC INTEGER (5..32) } -- TAG-FEATURESETUPLINK-STOP -- ASN1STOP
FeatureSetUplink field descriptions |
---|
featureSetListPerUplinkCC Indicates which features the UE supports on the individual UL carriers of the feature set (and hence of a band entry that refers to the feature set). The UE shall hence include at least as many FeatureSetUplinkPerCC-Id in this list as the number of carriers it supports according to the ca-BandwidthClassUL, except if indicating additional functionality by reducing the number of FeatureSetUplinkPerCC-Id in the feature set (see NOTE 1 in FeatureSetCombination IE description). The order of the elements in this list is not relevant, i.e., the network may configure any of the carriers in accordance with any of the FeatureSetUplinkPerCC-Id in this list. |
The IE FeatureSetUplinkId identifies an uplink feature set. The FeatureSetUplinkId of a FeatureSetUplink is the index position of the FeatureSetUplink in the featureSetsUplink list in the FeatureSets IE. The first element in the list is referred to by FeatureSetUplinkId = 1, and so on. The FeatureSetUplinkId =0 is not used by an actual FeatureSetUplink but means that the UE does not support a carrier in this band of a band combination.
The IE FeatureSetUplinkPerCC indicates a set of features that the UE supports on the corresponding carrier of one band entry of a band combination.
-- ASN1START -- TAG-FEATURESETUPLINKPERCC-START FeatureSetUplinkPerCC ::= SEQUENCE { supportedSubcarrierSpacingUL SubcarrierSpacing, supportedBandwidthUL SupportedBandwidth, channelBW-90mhz ENUMERATED {supported} OPTIONAL, mimo-CB-PUSCH SEQUENCE { maxNumberMIMO-LayersCB-PUSCH MIMO-LayersUL OPTIONAL, maxNumberSRS-ResourcePerSet INTEGER (1..2) } OPTIONAL, maxNumberMIMO-LayersNonCB-PUSCH MIMO-LayersUL OPTIONAL, supportedModulationOrderUL ModulationOrder OPTIONAL } FeatureSetUplinkPerCC-v1540 ::= SEQUENCE { mimo-NonCB-PUSCH SEQUENCE { maxNumberSRS-ResourcePerSet INTEGER (1..4), maxNumberSimultaneousSRS-ResourceTx INTEGER (1..4) } OPTIONAL } -- TAG-FEATURESETUPLINKPERCC-STOP -- ASN1STOP
The IE FeatureSetUplinkPerCC-Id identifies a set of features applicable to one carrier of a feature set. The FeatureSetUplinkPerCC-Id of a FeatureSetUplinkPerCC is the index position of the FeatureSetUplinkPerCC in the featureSetsUplinkPerCC. The first element in the list is referred to by FeatureSetUplinkPerCC-Id = 1, and so on.
The IE FreqBandList is used by the network to request NR CA,NR non-CA and/or MR-DC band combinations for specific NR and/or E-UTRA frequency bands and/or up to a specific number of carriers and/or up to specific aggregated bandwidth. This is also used to request feature sets (for NR) and feature set combinations (for NR and MR-DC). For NR sidelink communication, this is used by the initiating UE to request sidelink UE radio access capabilities from the peer UE.
-- ASN1START -- TAG-FREQBANDLIST-START FreqBandList ::= SEQUENCE (SIZE (1..maxBandsMRDC)) OF FreqBandInformation FreqBandInformation ::= CHOICE { bandInformationEUTRA FreqBandInformationEUTRA, bandInformationNR FreqBandInformationNR } FreqBandInformationEUTRA ::= SEQUENCE { bandEUTRA FreqBandIndicatorEUTRA, ca-BandwidthClassDL-EUTRA CA-BandwidthClassEUTRA OPTIONAL, -- Need N ca-BandwidthClassUL-EUTRA CA-BandwidthClassEUTRA OPTIONAL -- Need N } FreqBandInformationNR ::= SEQUENCE { bandNR FreqBandIndicatorNR, maxBandwidthRequestedDL AggregatedBandwidth OPTIONAL, -- Need N maxBandwidthRequestedUL AggregatedBandwidth OPTIONAL, -- Need N maxCarriersRequestedDL INTEGER (1..maxNrofServingCells) OPTIONAL, -- Need N maxCarriersRequestedUL INTEGER (1..maxNrofServingCells) OPTIONAL -- Need N } AggregatedBandwidth ::= ENUMERATED {mhz50, mhz100, mhz150, mhz200, mhz250, mhz300, mhz350, mhz400, mhz450, mhz500, mhz550, mhz600, mhz650, mhz700, mhz750, mhz800} -- TAG-FREQBANDLIST-STOP -- ASN1STOP
The IE FreqSeparationClass is used for an intra-band non-contiguous CA band combination to indicate frequency separation between lower edge of lowest CC and upper edge of highest CC in a frequency band.
-- ASN1START -- TAG-FREQSEPARATIONCLASS-START FreqSeparationClass ::= ENUMERATED { mhz800, mhz1200, mhz1400, ..., mhz400-v1650, mhz600-v1650} FreqSeparationClassDL-v1620 ::= ENUMERATED {mhz1000, mhz1600, mhz1800, mhz2000, mhz2200, mhz2400} FreqSeparationClassUL-v1620 ::= ENUMERATED {mhz1000} -- TAG-FREQSEPARATIONCLASS-STOP -- ASN1STOP
The IE FreqSeparationClassDL-Only is used to indicate the frequency separation between lower edge of lowest CC and upper edge of highest CC of DL only frequency spectrum in a frequency band.
The IE HighSpeedParameters is used to convey capabilities related to high speed scenarios.
-- ASN1START -- TAG-HIGHSPEEDPARAMETERS-START HighSpeedParameters-r16 ::= SEQUENCE { measurementEnhancement-r16 ENUMERATED {supported} OPTIONAL, demodulationEnhancement-r16 ENUMERATED {supported} OPTIONAL } HighSpeedParameters-v1650 ::= CHOICE { intraNR-MeasurementEnhancement-r16 ENUMERATED {supported}, interRAT-MeasurementEnhancement-r16 ENUMERATED {supported} } -- TAG-HIGHSPEEDPARAMETERS-STOP -- ASN1STOP
The IE IMS-Parameters is used to convey capabilities related to IMS.
-- ASN1START -- TAG-IMS-PARAMETERS-START IMS-Parameters ::= SEQUENCE { ims-ParametersCommon IMS-ParametersCommon OPTIONAL, ims-ParametersFRX-Diff IMS-ParametersFRX-Diff OPTIONAL, ... } IMS-ParametersCommon ::= SEQUENCE { voiceOverEUTRA-5GC ENUMERATED {supported} OPTIONAL, ..., [[ voiceOverSCG-BearerEUTRA-5GC ENUMERATED {supported} OPTIONAL ]], [[ voiceFallbackIndicationEPS-r16 ENUMERATED {supported} OPTIONAL ]] } IMS-ParametersFRX-Diff ::= SEQUENCE { voiceOverNR ENUMERATED {supported} OPTIONAL, ... } -- TAG-IMS-PARAMETERS-STOP -- ASN1STOP
The IE InterRAT-Parameters is used convey UE capabilities related to the other RATs.
-- ASN1START -- TAG-INTERRAT-PARAMETERS-START InterRAT-Parameters ::= SEQUENCE { eutra EUTRA-Parameters OPTIONAL, ..., [[ utra-FDD-r16 UTRA-FDD-Parameters-r16 OPTIONAL ]] } EUTRA-Parameters ::= SEQUENCE { supportedBandListEUTRA SEQUENCE (SIZE (1..maxBandsEUTRA)) OF FreqBandIndicatorEUTRA, eutra-ParametersCommon EUTRA-ParametersCommon OPTIONAL, eutra-ParametersXDD-Diff EUTRA-ParametersXDD-Diff OPTIONAL, ... } EUTRA-ParametersCommon ::= SEQUENCE { mfbi-EUTRA ENUMERATED {supported} OPTIONAL, modifiedMPR-BehaviorEUTRA BIT STRING (SIZE (32)) OPTIONAL, multiNS-Pmax-EUTRA ENUMERATED {supported} OPTIONAL, rs-SINR-MeasEUTRA ENUMERATED {supported} OPTIONAL, ..., [[ ne-DC ENUMERATED {supported} OPTIONAL ]], [[ nr-HO-ToEN-DC-r16 ENUMERATED {supported} OPTIONAL ]] } EUTRA-ParametersXDD-Diff ::= SEQUENCE { rsrqMeasWidebandEUTRA ENUMERATED {supported} OPTIONAL, ... } UTRA-FDD-Parameters-r16 ::= SEQUENCE { supportedBandListUTRA-FDD-r16 SEQUENCE (SIZE (1..maxBandsUTRA-FDD-r16)) OF SupportedBandUTRA-FDD-r16, ... } SupportedBandUTRA-FDD-r16 ::= ENUMERATED { bandI, bandII, bandIII, bandIV, bandV, bandVI, bandVII, bandVIII, bandIX, bandX, bandXI, bandXII, bandXIII, bandXIV, bandXV, bandXVI, bandXVII, bandXVIII, bandXIX, bandXX, bandXXI, bandXXII, bandXXIII, bandXXIV, bandXXV, bandXXVI, bandXXVII, bandXXVIII, bandXXIX, bandXXX, bandXXXI, bandXXXII} -- TAG-INTERRAT-PARAMETERS-STOP -- ASN1STOP
The IE MAC-Parameters is used to convey capabilities related to MAC.
-- ASN1START -- TAG-MAC-PARAMETERS-START MAC-Parameters ::= SEQUENCE { mac-ParametersCommon MAC-ParametersCommon OPTIONAL, mac-ParametersXDD-Diff MAC-ParametersXDD-Diff OPTIONAL } MAC-Parameters-v1610 ::= SEQUENCE { mac-ParametersFRX-Diff-r16 MAC-ParametersFRX-Diff-r16 OPTIONAL } MAC-ParametersCommon ::= SEQUENCE { lcp-Restriction ENUMERATED {supported} OPTIONAL, dummy ENUMERATED {supported} OPTIONAL, lch-ToSCellRestriction ENUMERATED {supported} OPTIONAL, ..., [[ recommendedBitRate ENUMERATED {supported} OPTIONAL, recommendedBitRateQuery ENUMERATED {supported} OPTIONAL ]], [[ recommendedBitRateMultiplier-r16 ENUMERATED {supported} OPTIONAL, preEmptiveBSR-r16 ENUMERATED {supported} OPTIONAL, autonomousTransmission-r16 ENUMERATED {supported} OPTIONAL, lch-PriorityBasedPrioritization-r16 ENUMERATED {supported} OPTIONAL, lch-ToConfiguredGrantMapping-r16 ENUMERATED {supported} OPTIONAL, lch-ToGrantPriorityRestriction-r16 ENUMERATED {supported} OPTIONAL, singlePHR-P-r16 ENUMERATED {supported} OPTIONAL, ul-LBT-FailureDetectionRecovery-r16 ENUMERATED {supported} OPTIONAL, -- R4 8-1: MPE tdd-MPE-P-MPR-Reporting-r16 ENUMERATED {supported} OPTIONAL, lcid-ExtensionIAB-r16 ENUMERATED {supported} OPTIONAL ]], [[ spCell-BFR-CBRA-r16 ENUMERATED {supported} OPTIONAL ]], [[ srs-ResourceId-Ext-r16 ENUMERATED {supported} OPTIONAL ]] } MAC-ParametersFRX-Diff-r16 ::= SEQUENCE { directMCG-SCellActivation-r16 ENUMERATED {supported} OPTIONAL, directMCG-SCellActivationResume-r16 ENUMERATED {supported} OPTIONAL, directSCG-SCellActivation-r16 ENUMERATED {supported} OPTIONAL, directSCG-SCellActivationResume-r16 ENUMERATED {supported} OPTIONAL, -- R1 19-1: DRX Adaptation drx-Adaptation-r16 SEQUENCE { non-SharedSpectrumChAccess-r16 MinTimeGap-r16 OPTIONAL, sharedSpectrumChAccess-r16 MinTimeGap-r16 OPTIONAL } OPTIONAL, ... } MAC-ParametersXDD-Diff ::= SEQUENCE { skipUplinkTxDynamic ENUMERATED {supported} OPTIONAL, logicalChannelSR-DelayTimer ENUMERATED {supported} OPTIONAL, longDRX-Cycle ENUMERATED {supported} OPTIONAL, shortDRX-Cycle ENUMERATED {supported} OPTIONAL, multipleSR-Configurations ENUMERATED {supported} OPTIONAL, multipleConfiguredGrants ENUMERATED {supported} OPTIONAL, ..., [[ secondaryDRX-Group-r16 ENUMERATED {supported} OPTIONAL ]], [[ enhancedSkipUplinkTxDynamic-r16 ENUMERATED {supported} OPTIONAL, enhancedSkipUplinkTxConfigured-r16 ENUMERATED {supported} OPTIONAL ]] } MinTimeGap-r16 ::= SEQUENCE { scs-15kHz-r16 ENUMERATED {sl1, sl3} OPTIONAL, scs-30kHz-r16 ENUMERATED {sl1, sl6} OPTIONAL, scs-60kHz-r16 ENUMERATED {sl1, sl12} OPTIONAL, scs-120kHz-r16 ENUMERATED {sl2, sl24} OPTIONAL } -- TAG-MAC-PARAMETERS-STOP -- ASN1STOP
The IE MeasAndMobParameters is used to convey UE capabilities related to measurements for radio resource management (RRM), radio link monitoring (RLM) and mobility (e.g. handover).
-- ASN1START -- TAG-MEASANDMOBPARAMETERS-START MeasAndMobParameters ::= SEQUENCE { measAndMobParametersCommon MeasAndMobParametersCommon OPTIONAL, measAndMobParametersXDD-Diff MeasAndMobParametersXDD-Diff OPTIONAL, measAndMobParametersFRX-Diff MeasAndMobParametersFRX-Diff OPTIONAL } MeasAndMobParametersCommon ::= SEQUENCE { supportedGapPattern BIT STRING (SIZE (22)) OPTIONAL, ssb-RLM ENUMERATED {supported} OPTIONAL, ssb-AndCSI-RS-RLM ENUMERATED {supported} OPTIONAL, ..., [[ eventB-MeasAndReport ENUMERATED {supported} OPTIONAL, handoverFDD-TDD ENUMERATED {supported} OPTIONAL, eutra-CGI-Reporting ENUMERATED {supported} OPTIONAL, nr-CGI-Reporting ENUMERATED {supported} OPTIONAL ]], [[ independentGapConfig ENUMERATED {supported} OPTIONAL, periodicEUTRA-MeasAndReport ENUMERATED {supported} OPTIONAL, handoverFR1-FR2 ENUMERATED {supported} OPTIONAL, maxNumberCSI-RS-RRM-RS-SINR ENUMERATED {n4, n8, n16, n32, n64, n96} OPTIONAL ]], [[ nr-CGI-Reporting-ENDC ENUMERATED {supported} OPTIONAL ]], [[ eutra-CGI-Reporting-NEDC ENUMERATED {supported} OPTIONAL, eutra-CGI-Reporting-NRDC ENUMERATED {supported} OPTIONAL, nr-CGI-Reporting-NEDC ENUMERATED {supported} OPTIONAL, nr-CGI-Reporting-NRDC ENUMERATED {supported} OPTIONAL ]], [[ reportAddNeighMeasForPeriodic-r16 ENUMERATED {supported} OPTIONAL, condHandoverParametersCommon-r16 SEQUENCE { condHandoverFDD-TDD-r16 ENUMERATED {supported} OPTIONAL, condHandoverFR1-FR2-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, nr-NeedForGap-Reporting-r16 ENUMERATED {supported} OPTIONAL, supportedGapPattern-NRonly-r16 BIT STRING (SIZE (10)) OPTIONAL, supportedGapPattern-NRonly-NEDC-r16 ENUMERATED {supported} OPTIONAL, maxNumberCLI-RSSI-r16 ENUMERATED {n8, n16, n32, n64} OPTIONAL, maxNumberCLI-SRS-RSRP-r16 ENUMERATED {n4, n8, n16, n32} OPTIONAL, maxNumberPerSlotCLI-SRS-RSRP-r16 ENUMERATED {n2, n4, n8} OPTIONAL, mfbi-IAB-r16 ENUMERATED {supported} OPTIONAL, dummy ENUMERATED {supported} OPTIONAL, nr-CGI-Reporting-NPN-r16 ENUMERATED {supported} OPTIONAL, idleInactiveEUTRA-MeasReport-r16 ENUMERATED {supported} OPTIONAL, idleInactive-ValidityArea-r16 ENUMERATED {supported} OPTIONAL, eutra-AutonomousGaps-r16 ENUMERATED {supported} OPTIONAL, eutra-AutonomousGaps-NEDC-r16 ENUMERATED {supported} OPTIONAL, eutra-AutonomousGaps-NRDC-r16 ENUMERATED {supported} OPTIONAL, pcellT312-r16 ENUMERATED {supported} OPTIONAL, supportedGapPattern-r16 BIT STRING (SIZE (2)) OPTIONAL ]] } MeasAndMobParametersXDD-Diff ::= SEQUENCE { intraAndInterF-MeasAndReport ENUMERATED {supported} OPTIONAL, eventA-MeasAndReport ENUMERATED {supported} OPTIONAL, ..., [[ handoverInterF ENUMERATED {supported} OPTIONAL, handoverLTE-EPC ENUMERATED {supported} OPTIONAL, handoverLTE-5GC ENUMERATED {supported} OPTIONAL ]], [[ sftd-MeasNR-Neigh ENUMERATED {supported} OPTIONAL, sftd-MeasNR-Neigh-DRX ENUMERATED {supported} OPTIONAL ]], [[ dummy ENUMERATED {supported} OPTIONAL ]] } MeasAndMobParametersFRX-Diff ::= SEQUENCE { ss-SINR-Meas ENUMERATED {supported} OPTIONAL, csi-RSRP-AndRSRQ-MeasWithSSB ENUMERATED {supported} OPTIONAL, csi-RSRP-AndRSRQ-MeasWithoutSSB ENUMERATED {supported} OPTIONAL, csi-SINR-Meas ENUMERATED {supported} OPTIONAL, csi-RS-RLM ENUMERATED {supported} OPTIONAL, ..., [[ handoverInterF ENUMERATED {supported} OPTIONAL, handoverLTE-EPC ENUMERATED {supported} OPTIONAL, handoverLTE-5GC ENUMERATED {supported} OPTIONAL ]], [[ maxNumberResource-CSI-RS-RLM ENUMERATED {n2, n4, n6, n8} OPTIONAL ]], [[ simultaneousRxDataSSB-DiffNumerology ENUMERATED {supported} OPTIONAL ]], [[ nr-AutonomousGaps-r16 ENUMERATED {supported} OPTIONAL, nr-AutonomousGaps-ENDC-r16 ENUMERATED {supported} OPTIONAL, nr-AutonomousGaps-NEDC-r16 ENUMERATED {supported} OPTIONAL, nr-AutonomousGaps-NRDC-r16 ENUMERATED {supported} OPTIONAL, dummy ENUMERATED {supported} OPTIONAL, cli-RSSI-Meas-r16 ENUMERATED {supported} OPTIONAL, cli-SRS-RSRP-Meas-r16 ENUMERATED {supported} OPTIONAL, interFrequencyMeas-NoGap-r16 ENUMERATED {supported} OPTIONAL, simultaneousRxDataSSB-DiffNumerology-Inter-r16 ENUMERATED {supported} OPTIONAL, idleInactiveNR-MeasReport-r16 ENUMERATED {supported} OPTIONAL, -- R4 6-2: Support of beam level Early Measurement Reporting idleInactiveNR-MeasBeamReport-r16 ENUMERATED {supported} OPTIONAL ]], [[ increasedNumberofCSIRSPerMO-r16 ENUMERATED {supported} OPTIONAL ]] } -- TAG-MEASANDMOBPARAMETERS-STOP -- ASN1STOP
The IE MeasAndMobParametersMRDC is used to convey capability parameters related to RRM measurements and RRC mobility.
-- ASN1START -- TAG-MEASANDMOBPARAMETERSMRDC-START MeasAndMobParametersMRDC ::= SEQUENCE { measAndMobParametersMRDC-Common MeasAndMobParametersMRDC-Common OPTIONAL, measAndMobParametersMRDC-XDD-Diff MeasAndMobParametersMRDC-XDD-Diff OPTIONAL, measAndMobParametersMRDC-FRX-Diff MeasAndMobParametersMRDC-FRX-Diff OPTIONAL } MeasAndMobParametersMRDC-v1560 ::= SEQUENCE { measAndMobParametersMRDC-XDD-Diff-v1560 MeasAndMobParametersMRDC-XDD-Diff-v1560 OPTIONAL } MeasAndMobParametersMRDC-v1610 ::= SEQUENCE { measAndMobParametersMRDC-Common-v1610 MeasAndMobParametersMRDC-Common-v1610 OPTIONAL, interNR-MeasEUTRA-IAB-r16 ENUMERATED {supported} OPTIONAL } MeasAndMobParametersMRDC-Common ::= SEQUENCE { independentGapConfig ENUMERATED {supported} OPTIONAL } MeasAndMobParametersMRDC-Common-v1610 ::= SEQUENCE { condPSCellChangeParametersCommon-r16 SEQUENCE { condPSCellChangeFDD-TDD-r16 ENUMERATED {supported} OPTIONAL, condPSCellChangeFR1-FR2-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, pscellT312-r16 ENUMERATED {supported} OPTIONAL } MeasAndMobParametersMRDC-XDD-Diff ::= SEQUENCE { sftd-MeasPSCell ENUMERATED {supported} OPTIONAL, sftd-MeasNR-Cell ENUMERATED {supported} OPTIONAL } MeasAndMobParametersMRDC-XDD-Diff-v1560 ::= SEQUENCE { sftd-MeasPSCell-NEDC ENUMERATED {supported} OPTIONAL } MeasAndMobParametersMRDC-FRX-Diff ::= SEQUENCE { simultaneousRxDataSSB-DiffNumerology ENUMERATED {supported} OPTIONAL } -- TAG-MEASANDMOBPARAMETERSMRDC-STOP -- ASN1STOP
The IE MIMO-Layers is used to convey the number of supported MIMO layers.
The IE MIMO-ParametersPerBand is used to convey MIMO related parameters specific for a certain band (not per feature set or band combination).
-- ASN1START -- TAG-MIMO-PARAMETERSPERBAND-START MIMO-ParametersPerBand ::= SEQUENCE { tci-StatePDSCH SEQUENCE { maxNumberConfiguredTCIstatesPerCC ENUMERATED {n4, n8, n16, n32, n64, n128} OPTIONAL, maxNumberActiveTCI-PerBWP ENUMERATED {n1, n2, n4, n8} OPTIONAL } OPTIONAL, additionalActiveTCI-StatePDCCH ENUMERATED {supported} OPTIONAL, pusch-TransCoherence ENUMERATED {nonCoherent, partialCoherent, fullCoherent} OPTIONAL, beamCorrespondenceWithoutUL-BeamSweeping ENUMERATED {supported} OPTIONAL, periodicBeamReport ENUMERATED {supported} OPTIONAL, aperiodicBeamReport ENUMERATED {supported} OPTIONAL, sp-BeamReportPUCCH ENUMERATED {supported} OPTIONAL, sp-BeamReportPUSCH ENUMERATED {supported} OPTIONAL, dummy1 DummyG OPTIONAL, maxNumberRxBeam INTEGER (2..8) OPTIONAL, maxNumberRxTxBeamSwitchDL SEQUENCE { scs-15kHz ENUMERATED {n4, n7, n14} OPTIONAL, scs-30kHz ENUMERATED {n4, n7, n14} OPTIONAL, scs-60kHz ENUMERATED {n4, n7, n14} OPTIONAL, scs-120kHz ENUMERATED {n4, n7, n14} OPTIONAL, scs-240kHz ENUMERATED {n4, n7, n14} OPTIONAL } OPTIONAL, maxNumberNonGroupBeamReporting ENUMERATED {n1, n2, n4} OPTIONAL, groupBeamReporting ENUMERATED {supported} OPTIONAL, uplinkBeamManagement SEQUENCE { maxNumberSRS-ResourcePerSet-BM ENUMERATED {n2, n4, n8, n16}, maxNumberSRS-ResourceSet INTEGER (1..8) } OPTIONAL, maxNumberCSI-RS-BFD INTEGER (1..64) OPTIONAL, maxNumberSSB-BFD INTEGER (1..64) OPTIONAL, maxNumberCSI-RS-SSB-CBD INTEGER (1..256) OPTIONAL, dummy2 ENUMERATED {supported} OPTIONAL, twoPortsPTRS-UL ENUMERATED {supported} OPTIONAL, dummy5 SRS-Resources OPTIONAL, dummy3 INTEGER (1..4) OPTIONAL, beamReportTiming SEQUENCE { scs-15kHz ENUMERATED {sym2, sym4, sym8} OPTIONAL, scs-30kHz ENUMERATED {sym4, sym8, sym14, sym28} OPTIONAL, scs-60kHz ENUMERATED {sym8, sym14, sym28} OPTIONAL, scs-120kHz ENUMERATED {sym14, sym28, sym56} OPTIONAL } OPTIONAL, ptrs-DensityRecommendationSetDL SEQUENCE { scs-15kHz PTRS-DensityRecommendationDL OPTIONAL, scs-30kHz PTRS-DensityRecommendationDL OPTIONAL, scs-60kHz PTRS-DensityRecommendationDL OPTIONAL, scs-120kHz PTRS-DensityRecommendationDL OPTIONAL } OPTIONAL, ptrs-DensityRecommendationSetUL SEQUENCE { scs-15kHz PTRS-DensityRecommendationUL OPTIONAL, scs-30kHz PTRS-DensityRecommendationUL OPTIONAL, scs-60kHz PTRS-DensityRecommendationUL OPTIONAL, scs-120kHz PTRS-DensityRecommendationUL OPTIONAL } OPTIONAL, dummy4 DummyH OPTIONAL, aperiodicTRS ENUMERATED {supported} OPTIONAL, ..., [[ dummy6 ENUMERATED {true} OPTIONAL, beamManagementSSB-CSI-RS BeamManagementSSB-CSI-RS OPTIONAL, beamSwitchTiming SEQUENCE { scs-60kHz ENUMERATED {sym14, sym28, sym48, sym224, sym336} OPTIONAL, scs-120kHz ENUMERATED {sym14, sym28, sym48, sym224, sym336} OPTIONAL } OPTIONAL, codebookParameters CodebookParameters OPTIONAL, csi-RS-IM-ReceptionForFeedback CSI-RS-IM-ReceptionForFeedback OPTIONAL, csi-RS-ProcFrameworkForSRS CSI-RS-ProcFrameworkForSRS OPTIONAL, csi-ReportFramework CSI-ReportFramework OPTIONAL, csi-RS-ForTracking CSI-RS-ForTracking OPTIONAL, srs-AssocCSI-RS SEQUENCE (SIZE (1.. maxNrofCSI-RS-Resources)) OF SupportedCSI-RS-Resource OPTIONAL, spatialRelations SpatialRelations OPTIONAL ]], [[ -- R1 16-2b-0: Support of default QCL assumption with two TCI states defaultQCL-TwoTCI-r16 ENUMERATED {supported} OPTIONAL,codebookParametersPerBand-r16For a given frequency band, this field this field indicates the alternative list of SupportedCSI-RS-Resource supported for each codebook type. The supported CSI-RS resources indicated by this field are referred by codebookParametersperBC in CA-ParametersNR to indicate the supported CSI-RS resource per band combination.CodebookParameters-v1610 OPTIONAL, -- R1 16-1b-3: Support of PUCCH resource groups per BWP for simultaneous spatial relation update simul-SpatialRelationUpdatePUCCHResGroup-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-1f: Maximum number of SCells configured for SCell beam failure recovery simultaneously maxNumberSCellBFR-r16 ENUMERATED {n1,n2,n4,n8} OPTIONAL, -- R1 16-2c: Supports simultaneous reception with different Type-D for FR2 only simultaneousReceptionDiffTypeD-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-1a-1: SSB/CSI-RS for L1-SINR measurement ssb-csirs-SINR-measurement-r16 SEQUENCE { maxNumberSSB-CSIRS-OneTx-CMR-r16 ENUMERATED {n8, n16, n32, n64}, maxNumberCSI-IM-NZP-IMR-res-r16 ENUMERATED {n8, n16, n32, n64}, maxNumberCSIRS-2Tx-res-r16 ENUMERATED {n0, n4, n8, n16, n32, n64}, maxNumberSSB-CSIRS-res-r16 ENUMERATED {n8, n16, n32, n64, n128}, maxNumberCSI-IM-NZP-IMR-res-mem-r16 ENUMERATED {n8, n16, n32, n64, n128}, supportedCSI-RS-Density-CMR-r16 ENUMERATED {one, three, oneAndThree}, maxNumberAperiodicCSI-RS-Res-r16 ENUMERATED {n2, n4, n8, n16, n32, n64}, supportedSINR-meas-r16 ENUMERATED {ssbWithCSI-IM, ssbWithNZP-IMR, csirsWithNZP-IMR, csi-RSWithoutIMR} OPTIONAL } OPTIONAL, -- R1 16-1a-2: Non-group based L1-SINR reporting nonGroupSINR-reporting-r16 ENUMERATED {n1, n2, n4} OPTIONAL, -- R1 16-1a-3: Non-group based L1-SINR reporting groupSINR-reporting-r16 ENUMERATED {supported} OPTIONAL, multiDCI-multiTRP-Parameters-r16 SEQUENCE { -- R1 16-2a-0: Overlapping PDSCHs in time and fully overlapping in frequency and time overlapPDSCHsFullyFreqTime-r16 INTEGER (1..2) OPTIONAL, -- R1 16-2a-1: Overlapping PDSCHs in time and partially overlapping in frequency and time overlapPDSCHsInTimePartiallyFreq-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-2a-2: Out of order operation for DL outOfOrderOperationDL-r16 SEQUENCE { supportPDCCH-ToPDSCH-r16 ENUMERATED {supported} OPTIONAL, supportPDSCH-ToHARQ-ACK-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, -- R1 16-2a-3: Out of order operation for UL outOfOrderOperationUL-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-2a-5: Separate CRS rate matching separateCRS-RateMatching-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-2a-6: Default QCL enhancement for multi-DCI based multi-TRP defaultQCL-PerCORESETPoolIndex-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-2a-7: Maximum number of activated TCI states maxNumberActivatedTCI-States-r16 SEQUENCE { maxNumberPerCORESET-Pool-r16 ENUMERATED {n1, n2, n4, n8}, maxTotalNumberAcrossCORESET-Pool-r16 ENUMERATED {n2, n4, n8, n16} } OPTIONAL } OPTIONAL, singleDCI-SDM-scheme-Parameters-r16 SEQUENCE { -- R1 16-2b-1b: Single-DCI based SDM scheme - Support of new DMRS port entrysupportNewDMRS-Port-r16Presence of this field set to supported1, supported2 or supported3 indicates that the UE supports the new DMRS port entry {0,2,3}.ENUMERATED {supported1, supported2, supported3} OPTIONAL, -- R1 16-2b-1a: Support of s-port DL PTRS supportTwoPortDL-PTRS-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, -- R1 16-2b-2: Support of single-DCI based FDMSchemeA supportFDM-SchemeA-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-2b-3a: Single-DCI based FDMSchemeB CW soft combining supportCodeWordSoftCombining-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-2b-4: Single-DCI based TDMSchemeA supportTDM-SchemeA-r16 ENUMERATED {kb3, kb5, kb10, kb20, noRestriction} OPTIONAL, -- R1 16-2b-5: Single-DCI based inter-slot TDM supportInter-slotTDM-r16 SEQUENCE { supportRepNumPDSCH-TDRA-r16 ENUMERATED {n2, n3, n4, n5, n6, n7, n8, n16}, maxTBS-Size-r16 ENUMERATED {kb3, kb5, kb10, kb20, noRestriction}, maxNumberTCI-states-r16 INTEGER (1..2) } OPTIONAL, -- R1 16-4: Low PAPR DMRS for PDSCH lowPAPR-DMRS-PDSCH-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-6a: Low PAPR DMRS for PUSCH without transform precoding lowPAPR-DMRS-PUSCHwithoutPrecoding-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-6b: Low PAPR DMRS for PUCCH lowPAPR-DMRS-PUCCH-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-6c: Low PAPR DMRS for PUSCH with transform precoding & pi/2 BPSK lowPAPR-DMRS-PUSCHwithPrecoding-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-7: Extension of the maximum number of configured aperiodic CSI report settings csi-ReportFrameworkExt-r16 CSI-ReportFrameworkExt-r16 OPTIONAL, -- R1 16-3a, 16-3a-1, 16-3b, 16-3b-1, 16-8: Individual new codebook types codebookParametersAddition-r16 CodebookParametersAddition-r16 OPTIONAL, -- R1 16-8: Mixed codebook types codebookComboParametersAddition-r16 CodebookComboParametersAddition-r16 OPTIONAL, -- R4 8-2: SSB based beam correspondence beamCorrespondenceSSB-based-r16 ENUMERATED {supported} OPTIONAL, -- R4 8-3: CSI-RS based beam correspondence beamCorrespondenceCSI-RS-based-r16 ENUMERATED {supported} OPTIONAL, beamSwitchTiming-r16 SEQUENCE { scs-60kHz-r16 ENUMERATED {sym224, sym336} OPTIONAL, scs-120kHz-r16 ENUMERATED {sym224, sym336} OPTIONAL } OPTIONAL ]], [[ -- R1 16-1a-4: Semi-persistent L1-SINR report on PUCCH semi-PersistentL1-SINR-Report-PUCCH-r16 SEQUENCE { supportReportFormat1-2OFDM-syms-r16 ENUMERATED {supported} OPTIONAL, supportReportFormat4-14OFDM-syms-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, -- R1 16-1a-5: Semi-persistent L1-SINR report on PUSCH semi-PersistentL1-SINR-Report-PUSCH-r16 ENUMERATED {supported} OPTIONAL ]], [[ -- R1 16-1h: Support of 64 configured PUCCH spatial relations spatialRelations-v1640 SEQUENCE { maxNumberConfiguredSpatialRelations-v1640 ENUMERATED {n96, n128, n160, n192, n224, n256, n288, n320} } OPTIONAL, -- R1 16-1i: Support of 64 configured candidate beam RSs for BFR support64CandidateBeamRS-BFR-r16 ENUMERATED {supported} OPTIONAL ]], [[ -- R1 16-2a-9: Interpretation of maxNumberMIMO-LayersPDSCH for multi-DCI based mTRP maxMIMO-LayersForMulti-DCI-mTRP-r16 ENUMERATED {supported} OPTIONAL ]], [[ supportedSINR-meas-v1670 BIT STRING (SIZE (4)) OPTIONAL ]] } DummyG ::= SEQUENCE { maxNumberSSB-CSI-RS-ResourceOneTx ENUMERATED {n8, n16, n32, n64}, maxNumberSSB-CSI-RS-ResourceTwoTx ENUMERATED {n0, n4, n8, n16, n32, n64}, supportedCSI-RS-Density ENUMERATED {one, three, oneAndThree} } BeamManagementSSB-CSI-RS ::= SEQUENCE { maxNumberSSB-CSI-RS-ResourceOneTx ENUMERATED {n0, n8, n16, n32, n64}, maxNumberCSI-RS-Resource ENUMERATED {n0, n4, n8, n16, n32, n64}, maxNumberCSI-RS-ResourceTwoTx ENUMERATED {n0, n4, n8, n16, n32, n64}, supportedCSI-RS-Density ENUMERATED {one, three, oneAndThree} OPTIONAL, maxNumberAperiodicCSI-RS-Resource ENUMERATED {n0, n1, n4, n8, n16, n32, n64} } DummyH ::= SEQUENCE { burstLength INTEGER (1..2), maxSimultaneousResourceSetsPerCC INTEGER (1..8), maxConfiguredResourceSetsPerCC INTEGER (1..64), maxConfiguredResourceSetsAllCC INTEGER (1..128) } CSI-RS-ForTracking ::= SEQUENCE { maxBurstLength INTEGER (1..2), maxSimultaneousResourceSetsPerCC INTEGER (1..8), maxConfiguredResourceSetsPerCC INTEGER (1..64), maxConfiguredResourceSetsAllCC INTEGER (1..256) } CSI-RS-IM-ReceptionForFeedback ::= SEQUENCE { maxConfigNumberNZP-CSI-RS-PerCC INTEGER (1..64), maxConfigNumberPortsAcrossNZP-CSI-RS-PerCC INTEGER (2..256), maxConfigNumberCSI-IM-PerCC ENUMERATED {n1, n2, n4, n8, n16, n32}, maxNumberSimultaneousNZP-CSI-RS-PerCC INTEGER (1..64), totalNumberPortsSimultaneousNZP-CSI-RS-PerCC INTEGER (2..256) } CSI-RS-ProcFrameworkForSRS ::= SEQUENCE { maxNumberPeriodicSRS-AssocCSI-RS-PerBWP INTEGER (1..4), maxNumberAperiodicSRS-AssocCSI-RS-PerBWP INTEGER (1..4), maxNumberSP-SRS-AssocCSI-RS-PerBWP INTEGER (0..4), simultaneousSRS-AssocCSI-RS-PerCC INTEGER (1..8) } CSI-ReportFramework ::= SEQUENCE { maxNumberPeriodicCSI-PerBWP-ForCSI-Report INTEGER (1..4), maxNumberAperiodicCSI-PerBWP-ForCSI-Report INTEGER (1..4), maxNumberSemiPersistentCSI-PerBWP-ForCSI-Report INTEGER (0..4), maxNumberPeriodicCSI-PerBWP-ForBeamReport INTEGER (1..4), maxNumberAperiodicCSI-PerBWP-ForBeamReport INTEGER (1..4), maxNumberAperiodicCSI-triggeringStatePerCC ENUMERATED {n3, n7, n15, n31, n63, n128}, maxNumberSemiPersistentCSI-PerBWP-ForBeamReport INTEGER (0..4), simultaneousCSI-ReportsPerCC INTEGER (1..8) } CSI-ReportFrameworkExt-r16 ::= SEQUENCE { maxNumberAperiodicCSI-PerBWP-ForCSI-ReportExt-r16 INTEGER (5..8) } PTRS-DensityRecommendationDL ::= SEQUENCE { frequencyDensity1 INTEGER (1..276), frequencyDensity2 INTEGER (1..276), timeDensity1 INTEGER (0..29), timeDensity2 INTEGER (0..29), timeDensity3 INTEGER (0..29) } PTRS-DensityRecommendationUL ::= SEQUENCE { frequencyDensity1 INTEGER (1..276), frequencyDensity2 INTEGER (1..276), timeDensity1 INTEGER (0..29), timeDensity2 INTEGER (0..29), timeDensity3 INTEGER (0..29), sampleDensity1 INTEGER (1..276), sampleDensity2 INTEGER (1..276), sampleDensity3 INTEGER (1..276), sampleDensity4 INTEGER (1..276), sampleDensity5 INTEGER (1..276) } SpatialRelations ::= SEQUENCE { maxNumberConfiguredSpatialRelations ENUMERATED {n4, n8, n16, n32, n64, n96}, maxNumberActiveSpatialRelations ENUMERATED {n1, n2, n4, n8, n14}, additionalActiveSpatialRelationPUCCH ENUMERATED {supported} OPTIONAL, maxNumberDL-RS-QCL-TypeD ENUMERATED {n1, n2, n4, n8, n14} } DummyI ::= SEQUENCE { supportedSRS-TxPortSwitch ENUMERATED {t1r2, t1r4, t2r4, t1r4-t2r4, tr-equal}, txSwitchImpactToRx ENUMERATED {true} OPTIONAL } -- TAG-MIMO-PARAMETERSPERBAND-STOP -- ASN1STOP
MIMO-ParametersPerBand field descriptions |
---|
codebookParametersPerBand For a given frequency band, this field this field indicates the alternative list of SupportedCSI-RS-Resource supported for each codebook type. The supported CSI-RS resources indicated by this field are referred by codebookParametersperBC in CA-ParametersNR to indicate the supported CSI-RS resource per band combination. |
csi-RS-IM-ReceptionForFeedback/ csi-RS-ProcFrameworkForSRS/ csi-ReportFramework CSI related capabilities which the UE supports on each of the carriers operated on this band. If the network configures the UE with serving cells on both FR1 and FR2 bands these values may be further limited by the corresponding fields in fr1-fr2-Add-UE-NR-Capabilities. |
supportNewDMRS-Port Presence of this field set to supported1, supported2 or supported3 indicates that the UE supports the new DMRS port entry {0,2,3}. |
The IE ModulationOrder is used to convey the maximum supported modulation order.
The IE MRDC-Parameters contains the band combination parameters specific to MR-DC for a given MR-DC band combination.
-- ASN1START -- TAG-MRDC-PARAMETERS-START MRDC-Parameters ::= SEQUENCE { singleUL-Transmission ENUMERATED {supported} OPTIONAL, dynamicPowerSharingENDC ENUMERATED {supported} OPTIONAL, tdm-Pattern ENUMERATED {supported} OPTIONAL, ul-SharingEUTRA-NR ENUMERATED {tdm, fdm, both} OPTIONAL, ul-SwitchingTimeEUTRA-NR ENUMERATED {type1, type2} OPTIONAL, simultaneousRxTxInterBandENDC ENUMERATED {supported} OPTIONAL, asyncIntraBandENDC ENUMERATED {supported} OPTIONAL, ..., [[ dualPA-Architecture ENUMERATED {supported} OPTIONAL, intraBandENDC-Support ENUMERATED {non-contiguous, both} OPTIONAL, ul-TimingAlignmentEUTRA-NR ENUMERATED {required} OPTIONAL ]] } MRDC-Parameters-v1580 ::= SEQUENCE { dynamicPowerSharingNEDC ENUMERATED {supported} OPTIONAL } MRDC-Parameters-v1590 ::=SEQUENCE { interBandContiguousMRDC ENUMERATED {supported} OPTIONAL } MRDC-Parameters-v15g0 ::= SEQUENCE { simultaneousRxTxInterBandENDCPerBandPair SimultaneousRxTxPerBandPair OPTIONAL } MRDC-Parameters-v15n0 ::= SEQUENCE { intraBandENDC-Support-UL ENUMERATED {non-contiguous, both} OPTIONAL } MRDC-Parameters-v1620 ::= SEQUENCE { maxUplinkDutyCycle-interBandENDC-TDD-PC2-r16 SEQUENCE{ eutra-TDD-Config0-r16 ENUMERATED {n20, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, eutra-TDD-Config1-r16 ENUMERATED {n20, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, eutra-TDD-Config2-r16 ENUMERATED {n20, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, eutra-TDD-Config3-r16 ENUMERATED {n20, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, eutra-TDD-Config4-r16 ENUMERATED {n20, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, eutra-TDD-Config5-r16 ENUMERATED {n20, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, eutra-TDD-Config6-r16 ENUMERATED {n20, n40, n50, n60, n70, n80, n90, n100} OPTIONAL } OPTIONAL, -- R1 18-2 Single UL TX operation for TDD PCell in EN-DC tdm-restrictionTDD-endc-r16 ENUMERATED {supported} OPTIONAL, -- R1 18-2a Single UL TX operation for FDD PCell in EN-DC tdm-restrictionFDD-endc-r16 ENUMERATED {supported} OPTIONAL, -- R1 18-2b Support of HARQ-offset for SUO case1 in EN-DC with LTE TDD PCell for type 1 UE singleUL-HARQ-offsetTDD-PCell-r16 ENUMERATED {supported} OPTIONAL, -- R1 18-3 Dual Tx transmission for EN-DC with FDD PCell(TDM pattern for dual Tx UE) tdm-restrictionDualTX-FDD-endc-r16 ENUMERATED {supported} OPTIONAL } MRDC-Parameters-v1630 ::=SEQUENCE { -- R4 2-20 Maximum uplink duty cycle for FDD+TDD EN-DC power class 2 maxUplinkDutyCycle-interBandENDC-FDD-TDD-PC2-r16 SEQUENCE { maxUplinkDutyCycle-FDD-TDD-EN-DC1-r16 ENUMERATED {n30, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, maxUplinkDutyCycle-FDD-TDD-EN-DC2-r16 ENUMERATED {n30, n40, n50, n60, n70, n80, n90, n100} OPTIONAL } OPTIONAL, -- R4 2-19 FDD-FDD or TDD-TDD inter-band MR-DC with overlapping or partially overlapping DL spectrum interBandMRDC-WithOverlapDL-Bands-r16 ENUMERATED {supported} OPTIONAL } -- TAG-MRDC-PARAMETERS-STOP -- ASN1STOP
The IE NRDC-Parameters contains parameters specific to NR-DC, i.e., which are not applicable to NR SA.
-- ASN1START -- TAG-NRDC-PARAMETERS-START NRDC-Parameters ::= SEQUENCE { measAndMobParametersNRDC MeasAndMobParametersMRDC OPTIONAL, generalParametersNRDC GeneralParametersMRDC-XDD-Diff OPTIONAL, fdd-Add-UE-NRDC-Capabilities UE-MRDC-CapabilityAddXDD-Mode OPTIONAL, tdd-Add-UE-NRDC-Capabilities UE-MRDC-CapabilityAddXDD-Mode OPTIONAL, fr1-Add-UE-NRDC-Capabilities UE-MRDC-CapabilityAddFRX-Mode OPTIONAL, fr2-Add-UE-NRDC-Capabilities UE-MRDC-CapabilityAddFRX-Mode OPTIONAL, dummy2 OCTET STRING OPTIONAL, dummy SEQUENCE {} OPTIONAL } NRDC-Parameters-v1570 ::= SEQUENCE { sfn-SyncNRDC ENUMERATED {supported} OPTIONAL } NRDC-Parameters-v15c0 ::= SEQUENCE { pdcp-DuplicationSplitSRB ENUMERATED {supported} OPTIONAL, pdcp-DuplicationSplitDRB ENUMERATED {supported} OPTIONAL } NRDC-Parameters-v1610 ::= SEQUENCE { measAndMobParametersNRDC-v1610 MeasAndMobParametersMRDC-v1610 OPTIONAL } -- TAG-NRDC-PARAMETERS-STOP -- ASN1STOP
The IE OLPC-SRS-Pos is used to convey OLPC SRS positioning related parameters specific for a certain band.
-- ASN1START -- TAG-OLPC-SRS-POS-START OLPC-SRS-Pos-r16 ::= SEQUENCE { olpc-SRS-PosBasedOnPRS-Serving-r16 ENUMERATED {supported} OPTIONAL, olpc-SRS-PosBasedOnSSB-Neigh-r16 ENUMERATED {supported} OPTIONAL, olpc-SRS-PosBasedOnPRS-Neigh-r16 ENUMERATED {supported} OPTIONAL, maxNumberPathLossEstimatePerServing-r16 ENUMERATED {n1, n4, n8, n16} OPTIONAL } --TAG-OLPC-SRS-POS-STOP -- ASN1STOP
The IE PDCP-Parameters is used to convey capabilities related to PDCP.
-- ASN1START -- TAG-PDCP-PARAMETERS-START PDCP-Parameters ::= SEQUENCE { supportedROHC-Profiles SEQUENCE { profile0x0000 BOOLEAN, profile0x0001 BOOLEAN, profile0x0002 BOOLEAN, profile0x0003 BOOLEAN, profile0x0004 BOOLEAN, profile0x0006 BOOLEAN, profile0x0101 BOOLEAN, profile0x0102 BOOLEAN, profile0x0103 BOOLEAN, profile0x0104 BOOLEAN }, maxNumberROHC-ContextSessions ENUMERATED {cs2, cs4, cs8, cs12, cs16, cs24, cs32, cs48, cs64, cs128, cs256, cs512, cs1024, cs16384, spare2, spare1}, uplinkOnlyROHC-Profiles ENUMERATED {supported} OPTIONAL, continueROHC-Context ENUMERATED {supported} OPTIONAL, outOfOrderDelivery ENUMERATED {supported} OPTIONAL, shortSN ENUMERATED {supported} OPTIONAL, pdcp-DuplicationSRB ENUMERATED {supported} OPTIONAL, pdcp-DuplicationMCG-OrSCG-DRB ENUMERATED {supported} OPTIONAL, ..., [[ drb-IAB-r16 ENUMERATED {supported} OPTIONAL, non-DRB-IAB-r16 ENUMERATED {supported} OPTIONAL, extendedDiscardTimer-r16 ENUMERATED {supported} OPTIONAL, continueEHC-Context-r16 ENUMERATED {supported} OPTIONAL, ehc-r16 ENUMERATED {supported} OPTIONAL, maxNumberEHC-Contexts-r16 ENUMERATED {cs2, cs4, cs8, cs16, cs32, cs64, cs128, cs256, cs512, cs1024, cs2048, cs4096, cs8192, cs16384, cs32768, cs65536} OPTIONAL, jointEHC-ROHC-Config-r16 ENUMERATED {supported} OPTIONAL, pdcp-DuplicationMoreThanTwoRLC-r16 ENUMERATED {supported} OPTIONAL ]] } -- TAG-PDCP-PARAMETERS-STOP -- ASN1STOP
The IE PDCP-ParametersMRDC is used to convey PDCP related capabilities for MR-DC.
-- ASN1START -- TAG-PDCP-PARAMETERSMRDC-START PDCP-ParametersMRDC ::= SEQUENCE { pdcp-DuplicationSplitSRB ENUMERATED {supported} OPTIONAL, pdcp-DuplicationSplitDRB ENUMERATED {supported} OPTIONAL } PDCP-ParametersMRDC-v1610 ::= SEQUENCE { scg-DRB-NR-IAB-r16 ENUMERATED {supported} OPTIONAL } -- TAG-PDCP-PARAMETERSMRDC-STOP -- ASN1STOP
The IE Phy-Parameters is used to convey the physical layer capabilities.
-- ASN1START -- TAG-PHY-PARAMETERS-START Phy-Parameters ::= SEQUENCE { phy-ParametersCommon Phy-ParametersCommon OPTIONAL, phy-ParametersXDD-Diff Phy-ParametersXDD-Diff OPTIONAL, phy-ParametersFRX-Diff Phy-ParametersFRX-Diff OPTIONAL, phy-ParametersFR1 Phy-ParametersFR1 OPTIONAL, phy-ParametersFR2 Phy-ParametersFR2 OPTIONAL } Phy-Parameters-v16a0 ::= SEQUENCE { phy-ParametersCommon-v16a0 Phy-ParametersCommon-v16a0 OPTIONAL } Phy-ParametersCommon ::= SEQUENCE { csi-RS-CFRA-ForHO ENUMERATED {supported} OPTIONAL, dynamicPRB-BundlingDL ENUMERATED {supported} OPTIONAL, sp-CSI-ReportPUCCH ENUMERATED {supported} OPTIONAL, sp-CSI-ReportPUSCH ENUMERATED {supported} OPTIONAL, nzp-CSI-RS-IntefMgmt ENUMERATED {supported} OPTIONAL, type2-SP-CSI-Feedback-LongPUCCH ENUMERATED {supported} OPTIONAL, precoderGranularityCORESET ENUMERATED {supported} OPTIONAL, dynamicHARQ-ACK-Codebook ENUMERATED {supported} OPTIONAL, semiStaticHARQ-ACK-Codebook ENUMERATED {supported} OPTIONAL, spatialBundlingHARQ-ACK ENUMERATED {supported} OPTIONAL, dynamicBetaOffsetInd-HARQ-ACK-CSI ENUMERATED {supported} OPTIONAL, pucch-Repetition-F1-3-4 ENUMERATED {supported} OPTIONAL, ra-Type0-PUSCH ENUMERATED {supported} OPTIONAL, dynamicSwitchRA-Type0-1-PDSCH ENUMERATED {supported} OPTIONAL, dynamicSwitchRA-Type0-1-PUSCH ENUMERATED {supported} OPTIONAL, pdsch-MappingTypeA ENUMERATED {supported} OPTIONAL, pdsch-MappingTypeB ENUMERATED {supported} OPTIONAL, interleavingVRB-ToPRB-PDSCH ENUMERATED {supported} OPTIONAL, interSlotFreqHopping-PUSCH ENUMERATED {supported} OPTIONAL, type1-PUSCH-RepetitionMultiSlots ENUMERATED {supported} OPTIONAL, type2-PUSCH-RepetitionMultiSlots ENUMERATED {supported} OPTIONAL, pusch-RepetitionMultiSlots ENUMERATED {supported} OPTIONAL, pdsch-RepetitionMultiSlots ENUMERATED {supported} OPTIONAL, downlinkSPS ENUMERATED {supported} OPTIONAL, configuredUL-GrantType1 ENUMERATED {supported} OPTIONAL, configuredUL-GrantType2 ENUMERATED {supported} OPTIONAL, pre-EmptIndication-DL ENUMERATED {supported} OPTIONAL, cbg-TransIndication-DL ENUMERATED {supported} OPTIONAL, cbg-TransIndication-UL ENUMERATED {supported} OPTIONAL, cbg-FlushIndication-DL ENUMERATED {supported} OPTIONAL, dynamicHARQ-ACK-CodeB-CBG-Retx-DL ENUMERATED {supported} OPTIONAL, rateMatchingResrcSetSemi-Static ENUMERATED {supported} OPTIONAL, rateMatchingResrcSetDynamic ENUMERATED {supported} OPTIONAL, bwp-SwitchingDelay ENUMERATED {type1, type2} OPTIONAL, ..., [[ dummy ENUMERATED {supported} OPTIONAL ]], [[ maxNumberSearchSpaces ENUMERATED {n10} OPTIONAL, rateMatchingCtrlResrcSetDynamic ENUMERATED {supported} OPTIONAL, maxLayersMIMO-Indication ENUMERATED {supported} OPTIONAL ]], [[ spCellPlacement CarrierAggregationVariant OPTIONAL ]], [[ -- R1 9-1: Basic channel structure and procedure of 2-step RACH twoStepRACH-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-1: Monitoring DCI format 1_2 and DCI format 0_2 dci-Format1-2And0-2-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-1a: Monitoring both DCI format 0_1/1_1 and DCI format 0_2/1_2 in the same search space monitoringDCI-SameSearchSpace-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-10: Type 2 configured grant release by DCI format 0_1 type2-CG-ReleaseDCI-0-1-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-11: Type 2 configured grant release by DCI format 0_2 type2-CG-ReleaseDCI-0-2-r16 ENUMERATED {supported} OPTIONAL, -- R1 12-3: SPS release by DCI format 1_1 sps-ReleaseDCI-1-1-r16 ENUMERATED {supported} OPTIONAL, -- R1 12-3a: SPS release by DCI format 1_2 sps-ReleaseDCI-1-2-r16 ENUMERATED {supported} OPTIONAL, -- R1 14-8: CSI trigger states containing non-active BWP csi-TriggerStateNon-ActiveBWP-r16 ENUMERATED {supported} OPTIONAL, -- R1 20-2: Support up to 4 SMTCs configured for an IAB node MT per frequency location, including IAB-specific SMTC window periodicities separateSMTC-InterIAB-Support-r16 ENUMERATED {supported} OPTIONAL, -- R1 20-3: Support RACH configuration separately from the RACH configuration for UE access, including new IAB-specific offset and scaling factors separateRACH-IAB-Support-r16 ENUMERATED {supported} OPTIONAL, -- R1 20-5a: Support semi-static configuration/indication of UL-Flexible-DL slot formats for IAB-MT resources ul-flexibleDL-SlotFormatSemiStatic-IAB-r16 ENUMERATED {supported} OPTIONAL, -- R1 20-5b: Support dynamic indication of UL-Flexible-DL slot formats for IAB-MT resources ul-flexibleDL-SlotFormatDynamics-IAB-r16 ENUMERATED {supported} OPTIONAL, dft-S-OFDM-WaveformUL-IAB-r16 ENUMERATED {supported} OPTIONAL, -- R1 20-6: Support DCI Format 2_5 based indication of soft resource availability to an IAB node dci-25-AI-RNTI-Support-IAB-r16 ENUMERATED {supported} OPTIONAL, -- R1 20-7: Support T_delta reception. t-DeltaReceptionSupport-IAB-r16 ENUMERATED {supported} OPTIONAL, -- R1 20-8: Support of Desired guard symbol reporting and provided guard symbok reception. guardSymbolReportReception-IAB-r16 ENUMERATED {supported} OPTIONAL, -- R1 18-8 HARQ-ACK codebook type and spatial bundling per PUCCH group harqACK-CB-SpatialBundlingPUCCH-Group-r16 ENUMERATED {supported} OPTIONAL, -- R1 19-2: Cross Slot Scheduling crossSlotScheduling-r16 SEQUENCE { non-SharedSpectrumChAccess-r16 ENUMERATED {supported} OPTIONAL, sharedSpectrumChAccess-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, maxNumberSRS-PosPathLossEstimateAllServingCells-r16 ENUMERATED {n1, n4, n8, n16} OPTIONAL, extendedCG-Periodicities-r16 ENUMERATED {supported} OPTIONAL, extendedSPS-Periodicities-r16 ENUMERATED {supported} OPTIONAL, codebookVariantsList-r16 CodebookVariantsList-r16 OPTIONAL, -- R1 11-6: PUSCH repetition Type A pusch-RepetitionTypeA-r16 SEQUENCE { sharedSpectrumChAccess-r16 ENUMERATED {supported} OPTIONAL, non-SharedSpectrumChAccess-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, -- R1 11-4b: DL priority indication in DCI with mixed DCI formats dci-DL-PriorityIndicator-r16 ENUMERATED {supported} OPTIONAL, -- R1 12-1a: UL priority indication in DCI with mixed DCI formats dci-UL-PriorityIndicator-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-1e: Maximum number of configured pathloss reference RSs for PUSCH/PUCCH/SRS by RRC for MAC-CE based pathloss reference RS update maxNumberPathlossRS-Update-r16 ENUMERATED {n4, n8, n16, n32, n64} OPTIONAL, -- R1 18-9: Usage of the PDSCH starting time for HARQ-ACK type 2 codebook type2-HARQ-ACK-Codebook-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-1g-1: Resources for beam management, pathloss measurement, BFD, RLM and new beam identification across frequency ranges maxTotalResourcesForAcrossFreqRanges-r16 SEQUENCE { maxNumberResWithinSlotAcrossCC-AcrossFR-r16 ENUMERATED {n2, n4, n8, n12, n16, n32, n64, n128} OPTIONAL, maxNumberResAcrossCC-AcrossFR-r16 ENUMERATED {n2, n4, n8, n12, n16, n32, n40, n48, n64, n72, n80, n96, n128, n256} OPTIONAL } OPTIONAL, -- R1 16-2a-4: HARQ-ACK for multi-DCI based multi-TRP - separate harqACK-separateMultiDCI-MultiTRP-r16 SEQUENCE { maxNumberLongPUCCHs-r16 ENUMERATED {longAndLong, longAndShort, shortAndShort} OPTIONAL } OPTIONAL, -- R1 16-2a-4: HARQ-ACK for multi-DCI based multi-TRP - joint harqACK-jointMultiDCI-MultiTRP-r16 ENUMERATED {supported} OPTIONAL, -- R4 9-1: BWP switching on multiple CCs RRM requirements bwp-SwitchingMultiCCs-r16 CHOICE { type1-r16 ENUMERATED {us100, us200}, type2-r16 ENUMERATED {us200, us400, us800, us1000} } OPTIONAL ]], [[ targetSMTC-SCG-r16 ENUMERATED {supported} OPTIONAL, supportRepetitionZeroOffsetRV-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-12: in-order CBG-based re-transmission cbg-TransInOrderPUSCH-UL-r16 ENUMERATED {supported} OPTIONAL ]], [[ -- R4 6-3: Dormant BWP switching on multiple CCs RRM requirements bwp-SwitchingMultiDormancyCCs-r16 CHOICE { type1-r16 ENUMERATED {us100, us200}, type2-r16 ENUMERATED {us200, us400, us800, us1000} } OPTIONAL, -- R1 16-2a-8: Indicates that retransmission scheduled by a different CORESETPoolIndex for multi-DCI multi-TRP is not supported. supportRetx-Diff-CoresetPool-Multi-DCI-TRP-r16 ENUMERATED {notSupported} OPTIONAL, -- R1 22-10: Support of pdcch-MonitoringAnyOccasionsWithSpanGap in case of cross-carrier scheduling with different SCSs pdcch-MonitoringAnyOccasionsWithSpanGapCrossCarrierSch-r16 ENUMERATED {mode2, mode3} OPTIONAL ]], [[ -- R1 16-1j-1: Support of 2 port CSI-RS for new beam identification newBeamIdentifications2PortCSI-RS-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-1j-2: Support of 2 port CSI-RS for pathloss estimation pathlossEstimation2PortCSI-RS-r16 ENUMERATED {supported} OPTIONAL ]], [[ mux-HARQ-ACK-withoutPUCCH-onPUSCH-r16 ENUMERATED {supported} OPTIONAL ]] } Phy-ParametersCommon-v16a0 ::= SEQUENCE { srs-PeriodicityAndOffsetExt-r16 ENUMERATED {supported} OPTIONAL } Phy-ParametersXDD-Diff ::= SEQUENCE { dynamicSFI ENUMERATED {supported} OPTIONAL, twoPUCCH-F0-2-ConsecSymbols ENUMERATED {supported} OPTIONAL, twoDifferentTPC-Loop-PUSCH ENUMERATED {supported} OPTIONAL, twoDifferentTPC-Loop-PUCCH ENUMERATED {supported} OPTIONAL, ..., [[ dl-SchedulingOffset-PDSCH-TypeA ENUMERATED {supported} OPTIONAL, dl-SchedulingOffset-PDSCH-TypeB ENUMERATED {supported} OPTIONAL, ul-SchedulingOffset ENUMERATED {supported} OPTIONAL ]] } Phy-ParametersFRX-Diff ::= SEQUENCE { dynamicSFI ENUMERATED {supported} OPTIONAL, dummy1 BIT STRING (SIZE (2)) OPTIONAL, twoFL-DMRS BIT STRING (SIZE (2)) OPTIONAL, dummy2 BIT STRING (SIZE (2)) OPTIONAL, dummy3 BIT STRING (SIZE (2)) OPTIONAL, supportedDMRS-TypeDL ENUMERATED {type1, type1And2} OPTIONAL, supportedDMRS-TypeUL ENUMERATED {type1, type1And2} OPTIONAL, semiOpenLoopCSI ENUMERATED {supported} OPTIONAL, csi-ReportWithoutPMI ENUMERATED {supported} OPTIONAL, csi-ReportWithoutCQI ENUMERATED {supported} OPTIONAL, onePortsPTRS BIT STRING (SIZE (2)) OPTIONAL, twoPUCCH-F0-2-ConsecSymbols ENUMERATED {supported} OPTIONAL, pucch-F2-WithFH ENUMERATED {supported} OPTIONAL, pucch-F3-WithFH ENUMERATED {supported} OPTIONAL, pucch-F4-WithFH ENUMERATED {supported} OPTIONAL, pucch-F0-2WithoutFH ENUMERATED {notSupported} OPTIONAL, pucch-F1-3-4WithoutFH ENUMERATED {notSupported} OPTIONAL, mux-SR-HARQ-ACK-CSI-PUCCH-MultiPerSlot ENUMERATED {supported} OPTIONAL, uci-CodeBlockSegmentation ENUMERATED {supported} OPTIONAL, onePUCCH-LongAndShortFormat ENUMERATED {supported} OPTIONAL, twoPUCCH-AnyOthersInSlot ENUMERATED {supported} OPTIONAL, intraSlotFreqHopping-PUSCH ENUMERATED {supported} OPTIONAL, pusch-LBRM ENUMERATED {supported} OPTIONAL, pdcch-BlindDetectionCA INTEGER (4..16) OPTIONAL, tpc-PUSCH-RNTI ENUMERATED {supported} OPTIONAL, tpc-PUCCH-RNTI ENUMERATED {supported} OPTIONAL, tpc-SRS-RNTI ENUMERATED {supported} OPTIONAL, absoluteTPC-Command ENUMERATED {supported} OPTIONAL, twoDifferentTPC-Loop-PUSCH ENUMERATED {supported} OPTIONAL, twoDifferentTPC-Loop-PUCCH ENUMERATED {supported} OPTIONAL, pusch-HalfPi-BPSK ENUMERATED {supported} OPTIONAL, pucch-F3-4-HalfPi-BPSK ENUMERATED {supported} OPTIONAL, almostContiguousCP-OFDM-UL ENUMERATED {supported} OPTIONAL, sp-CSI-RS ENUMERATED {supported} OPTIONAL, sp-CSI-IM ENUMERATED {supported} OPTIONAL, tdd-MultiDL-UL-SwitchPerSlot ENUMERATED {supported} OPTIONAL, multipleCORESET ENUMERATED {supported} OPTIONAL, ..., [[ csi-RS-IM-ReceptionForFeedback CSI-RS-IM-ReceptionForFeedback OPTIONAL, csi-RS-ProcFrameworkForSRS CSI-RS-ProcFrameworkForSRS OPTIONAL, csi-ReportFramework CSI-ReportFramework OPTIONAL, mux-SR-HARQ-ACK-CSI-PUCCH-OncePerSlot SEQUENCE { sameSymbol ENUMERATED {supported} OPTIONAL, diffSymbol ENUMERATED {supported} OPTIONAL } OPTIONAL, mux-SR-HARQ-ACK-PUCCH ENUMERATED {supported} OPTIONAL, mux-MultipleGroupCtrlCH-Overlap ENUMERATED {supported} OPTIONAL, dl-SchedulingOffset-PDSCH-TypeA ENUMERATED {supported} OPTIONAL, dl-SchedulingOffset-PDSCH-TypeB ENUMERATED {supported} OPTIONAL, ul-SchedulingOffset ENUMERATED {supported} OPTIONAL, dl-64QAM-MCS-TableAlt ENUMERATED {supported} OPTIONAL, ul-64QAM-MCS-TableAlt ENUMERATED {supported} OPTIONAL, cqi-TableAlt ENUMERATED {supported} OPTIONAL, oneFL-DMRS-TwoAdditionalDMRS-UL ENUMERATED {supported} OPTIONAL, twoFL-DMRS-TwoAdditionalDMRS-UL ENUMERATED {supported} OPTIONAL, oneFL-DMRS-ThreeAdditionalDMRS-UL ENUMERATED {supported} OPTIONAL ]], [[ pdcch-BlindDetectionNRDC SEQUENCE { pdcch-BlindDetectionMCG-UE INTEGER (1..15), pdcch-BlindDetectionSCG-UE INTEGER (1..15) } OPTIONAL, mux-HARQ-ACK-PUSCH-DiffSymbol ENUMERATED {supported} OPTIONAL ]], [[ -- R1 11-1b: Type 1 HARQ-ACK codebook support for relative TDRA for DL type1-HARQ-ACK-Codebook-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-8: Enhanced UL power control scheme enhancedPowerControl-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-1b-1: TCI state activation across multiple CCs simultaneousTCI-ActMultipleCC-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-1b-2: Spatial relation update across multiple CCs simultaneousSpatialRelationMultipleCC-r16 ENUMERATED {supported} OPTIONAL, cli-RSSI-FDM-DL-r16 ENUMERATED {supported} OPTIONAL, cli-SRS-RSRP-FDM-DL-r16 ENUMERATED {supported} OPTIONAL, -- R1 19-3: Maximum MIMO Layer Adaptation maxLayersMIMO-Adaptation-r16 ENUMERATED {supported} OPTIONAL, -- R1 12-5: Configuration of aggregation factor per SPS configuration aggregationFactorSPS-DL-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-1g: Resources for beam management, pathloss measurement, BFD, RLM and new beam identification maxTotalResourcesForOneFreqRange-r16 SEQUENCE { maxNumberResWithinSlotAcrossCC-OneFR-r16 ENUMERATED {n2, n4, n8, n12, n16, n32, n64, n128} OPTIONAL, maxNumberResAcrossCC-OneFR-r16 ENUMERATED {n2, n4, n8, n12, n16, n32, n40, n48, n64, n72, n80, n96, n128, n256} OPTIONAL } OPTIONAL, -- R1 16-7: Extension of the maximum number of configured aperiodic CSI report settings csi-ReportFrameworkExt-r16 CSI-ReportFrameworkExt-r16 OPTIONAL ]], [[ twoTCI-Act-servingCellInCC-List-r16 ENUMERATED {supported} OPTIONAL ]], [[ -- R1 22-11: Support of 'cri-RI-CQI' report without non-PMI-PortIndication cri-RI-CQI-WithoutNon-PMI-PortInd-r16 ENUMERATED {supported} OPTIONAL ]] } Phy-ParametersFR1 ::= SEQUENCE { pdcch-MonitoringSingleOccasion ENUMERATED {supported} OPTIONAL, scs-60kHz ENUMERATED {supported} OPTIONAL, pdsch-256QAM-FR1 ENUMERATED {supported} OPTIONAL, pdsch-RE-MappingFR1-PerSymbol ENUMERATED {n10, n20} OPTIONAL, ..., [[ pdsch-RE-MappingFR1-PerSlot ENUMERATED {n16, n32, n48, n64, n80, n96, n112, n128, n144, n160, n176, n192, n208, n224, n240, n256} OPTIONAL ]], [[ -- R1 22-12: PDCCH monitoring with a single span of three contiguous OFDM symbols that is within the first four OFDM symbols in a -- slot pdcch-MonitoringSingleSpanFirst4Sym-r16 ENUMERATED {supported} OPTIONAL ]] } Phy-ParametersFR2 ::= SEQUENCE { dummy ENUMERATED {supported} OPTIONAL, pdsch-RE-MappingFR2-PerSymbol ENUMERATED {n6, n20} OPTIONAL, ..., [[ pCell-FR2 ENUMERATED {supported} OPTIONAL, pdsch-RE-MappingFR2-PerSlot ENUMERATED {n16, n32, n48, n64, n80, n96, n112, n128, n144, n160, n176, n192, n208, n224, n240, n256} OPTIONAL ]], [[ -- R1 16-1c: Support of default spatial relation and pathloss reference RS for dedicated-PUCCH/SRS and PUSCH defaultSpatialRelationPathlossRS-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-1d: Support of spatial relation update for AP-SRS via MAC CE spatialRelationUpdateAP-SRS-r16 ENUMERATED {supported} OPTIONAL, maxNumberSRS-PosSpatialRelationsAllServingCells-r16 ENUMERATED {n0, n1, n2, n4, n8, n16} OPTIONAL ]] } -- TAG-PHY-PARAMETERS-STOP -- ASN1STOP
Phy-ParametersFRX-Diff field descriptions |
---|
csi-RS-IM-ReceptionForFeedback/ csi-RS-ProcFrameworkForSRS/ csi-ReportFramework These fields are optionally present in fr1-fr2-Add-UE-NR-Capabilities in UE-NR-Capability. They shall not be set in any other instance of the IE Phy-ParametersFRX-Diff. If the network configures the UE with serving cells on both FR1 and FR2 bands, these parameters, if present, limit the corresponding parameters in MIMO-ParametersPerBand. |
The IE Phy-ParametersMRDC is used to convey physical layer capabilities for MR-DC.
-- ASN1START -- TAG-PHY-PARAMETERSMRDC-START Phy-ParametersMRDC ::= SEQUENCE {naics-Capability-ListIndicates that UE in MR-DC supports NAICS as defined in TS 36.331 [10].SEQUENCE (SIZE (1..maxNrofNAICS-Entries)) OF NAICS-Capability-Entry OPTIONAL, ..., [[ spCellPlacement CarrierAggregationVariant OPTIONAL ]], [[ -- R1 18-3b: Semi-statically configured LTE UL transmissions in all UL subframes not limited to tdm-pattern in case of TDD PCell tdd-PCellUL-TX-AllUL-Subframe-r16 ENUMERATED {supported} OPTIONAL, -- R1 18-3a: Semi-statically configured LTE UL transmissions in all UL subframes not limited to tdm-pattern in case of FDD PCell fdd-PCellUL-TX-AllUL-Subframe-r16 ENUMERATED {supported} OPTIONAL ]] } NAICS-Capability-Entry ::= SEQUENCE { numberOfNAICS-CapableCC INTEGER(1..5), numberOfAggregatedPRB ENUMERATED {n50, n75, n100, n125, n150, n175, n200, n225, n250, n275, n300, n350, n400, n450, n500, spare}, ... } -- TAG-PHY-PARAMETERSMRDC-STOP -- ASN1STOP
PHY-ParametersMRDC field descriptions |
---|
naics-Capability-List Indicates that UE in MR-DC supports NAICS as defined in TS 36.331 [10]. |
The IE Phy-ParametersSharedSpectrumChAccess is used to convey the physical layer capabilities specific for shared spectrum channel access.
-- ASN1START -- TAG-PHY-PARAMETERSSHAREDSPECTRUMCHACCESS-START Phy-ParametersSharedSpectrumChAccess-r16 ::= SEQUENCE { -- 10-32 (1-2): SS block based SINR measurement (SS-SINR) for unlicensed spectrum ss-SINR-Meas-r16 ENUMERATED {supported} OPTIONAL, -- 10-33 (2-32a): Semi-persistent CSI report on PUCCH for unlicensed spectrum sp-CSI-ReportPUCCH-r16 ENUMERATED {supported} OPTIONAL, -- 10-33a (2-32b): Semi-persistent CSI report on PUSCH for unlicensed spectrum sp-CSI-ReportPUSCH-r16 ENUMERATED {supported} OPTIONAL, -- 10-34 (3-6): Dynamic SFI monitoring for unlicensed spectrum dynamicSFI-r16 ENUMERATED {supported} OPTIONAL, -- 10-35c (4-19c): SR/HARQ-ACK/CSI multiplexing once per slot using a PUCCH (or HARQ-ACK/CSI piggybacked on a PUSCH) when SR/HARQ- -- ACK/CSI are supposed to be sent with different starting symbols in a slot for unlicensed spectrum -- 10-35 (4-19): SR/HARQ-ACK/CSI multiplexing once per slot using a PUCCH (or HARQ-ACK/CSI piggybacked on a PUSCH) when SR/HARQ- -- ACK/CSI are supposed to be sent with the same starting symbol on the PUCCH resources in a slot for unlicensed spectrum mux-SR-HARQ-ACK-CSI-PUCCH-OncePerSlot-r16 SEQUENCE { sameSymbol-r16 ENUMERATED {supported} OPTIONAL, diffSymbol-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, -- 10-35a (4-19a): Overlapping PUCCH resources have different starting symbols in a slot for unlicensed spectrum mux-SR-HARQ-ACK-PUCCH-r16 ENUMERATED {supported} OPTIONAL, -- 10-35b (4-19b): SR/HARQ-ACK/CSI multiplexing more than once per slot using a PUCCH (or HARQ-ACK/CSI piggybacked on a PUSCH) when -- SR/HARQ ACK/CSI are supposed to be sent with the same or different starting symbol in a slot for unlicensed spectrum mux-SR-HARQ-ACK-CSI-PUCCH-MultiPerSlot-r16 ENUMERATED {supported} OPTIONAL, -- 10-36 (4-28): HARQ-ACK multiplexing on PUSCH with different PUCCH/PUSCH starting OFDM symbols for unlicensed spectrum mux-HARQ-ACK-PUSCH-DiffSymbol-r16 ENUMERATED {supported} OPTIONAL, -- 10-37 (4-23): Repetitions for PUCCH format 1, 3, and 4 over multiple slots with K = 2, 4, 8 for unlicensed spectrum pucch-Repetition-F1-3-4-r16 ENUMERATED {supported} OPTIONAL, -- 10-38 (5-14): Type 1 configured PUSCH repetitions over multiple slots for unlicensed spectrum type1-PUSCH-RepetitionMultiSlots-r16 ENUMERATED {supported} OPTIONAL, -- 10-39 (5-16): Type 2 configured PUSCH repetitions over multiple slots for unlicensed spectrum type2-PUSCH-RepetitionMultiSlots-r16 ENUMERATED {supported} OPTIONAL, -- 10-40 (5-17): PUSCH repetitions over multiple slots for unlicensed spectrum pusch-RepetitionMultiSlots-r16 ENUMERATED {supported} OPTIONAL, -- 10-40a (5-17a): PDSCH repetitions over multiple slots for unlicensed spectrum pdsch-RepetitionMultiSlots-r16 ENUMERATED {supported} OPTIONAL, -- 10-41 (5-18): DL SPS downlinkSPS-r16 ENUMERATED {supported} OPTIONAL, -- 10-42 (5-19): Type 1 Configured UL grant configuredUL-GrantType1-r16 ENUMERATED {supported} OPTIONAL, -- 10-43 (5-20): Type 2 Configured UL grant configuredUL-GrantType2-r16 ENUMERATED {supported} OPTIONAL, -- 10-44 (5-21): Pre-emption indication for DL pre-EmptIndication-DL-r16 ENUMERATED {supported} OPTIONAL, ... } -- TAG-PHY-PARAMETERSSHAREDSPECTRUMCHACCESS-STOP -- ASN1STOP
The IE PowSav-Parameters is used to convey the capabilities supported by the UE for the power saving preferences.
-- ASN1START -- TAG-POWSAV-PARAMETERS-START PowSav-Parameters-r16 ::= SEQUENCE { powSav-ParametersCommon-r16 PowSav-ParametersCommon-r16 OPTIONAL, powSav-ParametersFRX-Diff-r16 PowSav-ParametersFRX-Diff-r16 OPTIONAL, ... } PowSav-ParametersCommon-r16 ::= SEQUENCE { drx-Preference-r16 ENUMERATED {supported} OPTIONAL, maxCC-Preference-r16 ENUMERATED {supported} OPTIONAL, releasePreference-r16 ENUMERATED {supported} OPTIONAL, -- R1 19-4a: UE assistance information minSchedulingOffsetPreference-r16 ENUMERATED {supported} OPTIONAL, ... } PowSav-ParametersFRX-Diff-r16 ::= SEQUENCE { maxBW-Preference-r16 ENUMERATED {supported} OPTIONAL, maxMIMO-LayerPreference-r16 ENUMERATED {supported} OPTIONAL, ... } -- TAG-POWSAV-PARAMETERS-STOP -- ASN1STOP
The IE ProcessingParameters is used to indicate PDSCH/PUSCH processing capabilities supported by the UE.
-- ASN1START -- TAG-PROCESSINGPARAMETERS-START ProcessingParameters ::= SEQUENCE { fallback ENUMERATED {sc, cap1-only}, differentTB-PerSlot SEQUENCE { upto1 NumberOfCarriers OPTIONAL, upto2 NumberOfCarriers OPTIONAL, upto4 NumberOfCarriers OPTIONAL, upto7 NumberOfCarriers OPTIONAL } OPTIONAL } NumberOfCarriers ::= INTEGER (1..16) -- TAG-PROCESSINGPARAMETERS-STOP -- ASN1STOP
The IE RAT-Type is used to indicate the radio access technology (RAT), including NR,of the requested/transferred UE capabilities.
The IE RF-Parameters is used to convey RF-related capabilities for NR operation.
-- ASN1START -- TAG-RF-PARAMETERS-START RF-Parameters ::= SEQUENCE {supportedBandListNRA list of NR bands supported by the UE. If supportedBandListNR-v16c0 is included, the UE shall include the same number of entries, and listed in the same order, as in supportedBandListNR (without suffix).SEQUENCE (SIZE (1..maxBands)) OF BandNR,supportedBandCombinationListA list of band combinations that the UE supports for NR (and NR-DC, if requested). The FeatureSetCombinationId:s in this list refer to the FeatureSetCombination entries in the featureSetCombinations list in the UE-NR-Capability IE. The UE does not include this field if the UE capability is requested by E-UTRAN and the network request includes the field eutra-nr-only [10].BandCombinationList OPTIONAL,appliedFreqBandListFilterIn this field the UE mirrors the FreqBandList that the NW provided in the capability enquiry, if any. The UE filtered the band combinations in the supportedBandCombinationList in accordance with this appliedFreqBandListFilter. The UE does not include this field if the UE capability is requested by E-UTRAN and the network request includes the field eutra-nr-only [10].FreqBandList OPTIONAL, ..., [[ supportedBandCombinationList-v1540 BandCombinationList-v1540 OPTIONAL, srs-SwitchingTimeRequested ENUMERATED {true} OPTIONAL ]], [[ supportedBandCombinationList-v1550 BandCombinationList-v1550 OPTIONAL ]], [[ supportedBandCombinationList-v1560 BandCombinationList-v1560 OPTIONAL ]], [[ supportedBandCombinationList-v1610 BandCombinationList-v1610 OPTIONAL,supportedBandCombinationListSidelinkEUTRA-NR-r16A list of band combinations that the UE supports for NR sidelink communication only, for joint NR sidelink communication and V2X sidelink communication, or for V2X sidelink communication only. The UE does not include this field if the UE capability is requested by E-UTRAN (see TS 36.331[10]) and the network request includes the field eutra-nr-only.BandCombinationListSidelinkEUTRA-NR-r16 OPTIONAL,supportedBandCombinationList-UplinkTxSwitch-r16A list of band combinations that the UE supports dynamic uplink Tx switching for NR UL CA and SUL. The FeatureSetCombinationId:s in this list refer to the FeatureSetCombination entries in the featureSetCombinations list in the UE-NR-Capability IE. The UE does not include this field if the UE capability is requested by E-UTRAN and the network request includes the field eutra-nr-only [10].BandCombinationList-UplinkTxSwitch-r16 OPTIONAL ]], [[ supportedBandCombinationList-v1630 BandCombinationList-v1630 OPTIONAL, supportedBandCombinationListSidelinkEUTRA-NR-v1630 BandCombinationListSidelinkEUTRA-NR-v1630 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1630 BandCombinationList-UplinkTxSwitch-v1630 OPTIONAL ]], [[ supportedBandCombinationList-v1640 BandCombinationList-v1640 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1640 BandCombinationList-UplinkTxSwitch-v1640 OPTIONAL ]], [[ supportedBandCombinationList-v1650 BandCombinationList-v1650 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1650 BandCombinationList-UplinkTxSwitch-v1650 OPTIONAL ]], [[ extendedBand-n77-r16 ENUMERATED {supported} OPTIONAL ]], [[ supportedBandCombinationList-UplinkTxSwitch-v1670 BandCombinationList-UplinkTxSwitch-v1670 OPTIONAL ]], [[ supportedBandCombinationList-v1680 BandCombinationList-v1680 OPTIONAL ]], [[ supportedBandCombinationList-v1690 BandCombinationList-v1690 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1690 BandCombinationList-UplinkTxSwitch-v1690 OPTIONAL ]] } RF-Parameters-v15g0 ::= SEQUENCE { supportedBandCombinationList-v15g0 BandCombinationList-v15g0 OPTIONAL } RF-Parameters-v16a0 ::= SEQUENCE { supportedBandCombinationList-v16a0 BandCombinationList-v16a0 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v16a0 BandCombinationList-UplinkTxSwitch-v16a0 OPTIONAL } RF-Parameters-v16c0 ::= SEQUENCE { supportedBandListNR-v16c0 SEQUENCE (SIZE (1..maxBands)) OF BandNR-v16c0 } BandNR ::= SEQUENCE { bandNR FreqBandIndicatorNR, modifiedMPR-Behaviour BIT STRING (SIZE (8)) OPTIONAL, mimo-ParametersPerBand MIMO-ParametersPerBand OPTIONAL, extendedCP ENUMERATED {supported} OPTIONAL, multipleTCI ENUMERATED {supported} OPTIONAL, bwp-WithoutRestriction ENUMERATED {supported} OPTIONAL, bwp-SameNumerology ENUMERATED {upto2, upto4} OPTIONAL, bwp-DiffNumerology ENUMERATED {upto4} OPTIONAL, crossCarrierScheduling-SameSCS ENUMERATED {supported} OPTIONAL, pdsch-256QAM-FR2 ENUMERATED {supported} OPTIONAL, pusch-256QAM ENUMERATED {supported} OPTIONAL, ue-PowerClass ENUMERATED {pc1, pc2, pc3, pc4} OPTIONAL, rateMatchingLTE-CRS ENUMERATED {supported} OPTIONAL, channelBWs-DL CHOICE { fr1 SEQUENCE { scs-15kHz BIT STRING (SIZE (10)) OPTIONAL, scs-30kHz BIT STRING (SIZE (10)) OPTIONAL, scs-60kHz BIT STRING (SIZE (10)) OPTIONAL }, fr2 SEQUENCE { scs-60kHz BIT STRING (SIZE (3)) OPTIONAL, scs-120kHz BIT STRING (SIZE (3)) OPTIONAL } } OPTIONAL, channelBWs-UL CHOICE { fr1 SEQUENCE { scs-15kHz BIT STRING (SIZE (10)) OPTIONAL, scs-30kHz BIT STRING (SIZE (10)) OPTIONAL, scs-60kHz BIT STRING (SIZE (10)) OPTIONAL }, fr2 SEQUENCE { scs-60kHz BIT STRING (SIZE (3)) OPTIONAL, scs-120kHz BIT STRING (SIZE (3)) OPTIONAL } } OPTIONAL, ..., [[ maxUplinkDutyCycle-PC2-FR1 ENUMERATED {n60, n70, n80, n90, n100} OPTIONAL ]], [[ pucch-SpatialRelInfoMAC-CE ENUMERATED {supported} OPTIONAL, powerBoosting-pi2BPSK ENUMERATED {supported} OPTIONAL ]], [[ maxUplinkDutyCycle-FR2 ENUMERATED {n15, n20, n25, n30, n40, n50, n60, n70, n80, n90, n100} OPTIONAL ]], [[ channelBWs-DL-v1590 CHOICE { fr1 SEQUENCE { scs-15kHz BIT STRING (SIZE (16)) OPTIONAL, scs-30kHz BIT STRING (SIZE (16)) OPTIONAL, scs-60kHz BIT STRING (SIZE (16)) OPTIONAL }, fr2 SEQUENCE { scs-60kHz BIT STRING (SIZE (8)) OPTIONAL, scs-120kHz BIT STRING (SIZE (8)) OPTIONAL } } OPTIONAL, channelBWs-UL-v1590 CHOICE { fr1 SEQUENCE { scs-15kHz BIT STRING (SIZE (16)) OPTIONAL, scs-30kHz BIT STRING (SIZE (16)) OPTIONAL, scs-60kHz BIT STRING (SIZE (16)) OPTIONAL }, fr2 SEQUENCE { scs-60kHz BIT STRING (SIZE (8)) OPTIONAL, scs-120kHz BIT STRING (SIZE (8)) OPTIONAL } } OPTIONAL ]], [[ asymmetricBandwidthCombinationSet BIT STRING (SIZE (1..32)) OPTIONAL ]], [[ -- R1 10: NR-unlicensed sharedSpectrumChAccessParamsPerBand-r16 SharedSpectrumChAccessParamsPerBand-r16 OPTIONAL, -- R1 11-7b: Independent cancellation of the overlapping PUSCHs in an intra-band UL CA cancelOverlappingPUSCH-r16 ENUMERATED {supported} OPTIONAL, -- R1 14-1: Multiple LTE-CRS rate matching patterns multipleRateMatchingEUTRA-CRS-r16 SEQUENCE { maxNumberPatterns-r16 INTEGER (2..6), maxNumberNon-OverlapPatterns-r16 INTEGER (1..3) } OPTIONAL, -- R1 14-1a: Two LTE-CRS overlapping rate matching patterns within a part of NR carrier using 15 kHz overlapping with a LTE carrier overlapRateMatchingEUTRA-CRS-r16 ENUMERATED {supported} OPTIONAL, -- R1 14-2: PDSCH Type B mapping of length 9 and 10 OFDM symbols pdsch-MappingTypeB-Alt-r16 ENUMERATED {supported} OPTIONAL, -- R1 14-3: One slot periodic TRS configuration for FR1 oneSlotPeriodicTRS-r16 ENUMERATED {supported} OPTIONAL, olpc-SRS-Pos-r16 OLPC-SRS-Pos-r16 OPTIONAL, spatialRelationsSRS-Pos-r16 SpatialRelationsSRS-Pos-r16 OPTIONAL, simulSRS-MIMO-TransWithinBand-r16 ENUMERATED {n2} OPTIONAL, channelBW-DL-IAB-r16 CHOICE { fr1-100mhz SEQUENCE { scs-15kHz ENUMERATED {supported} OPTIONAL, scs-30kHz ENUMERATED {supported} OPTIONAL, scs-60kHz ENUMERATED {supported} OPTIONAL }, fr2-200mhz SEQUENCE { scs-60kHz ENUMERATED {supported} OPTIONAL, scs-120kHz ENUMERATED {supported} OPTIONAL } } OPTIONAL, channelBW-UL-IAB-r16 CHOICE { fr1-100mhz SEQUENCE { scs-15kHz ENUMERATED {supported} OPTIONAL, scs-30kHz ENUMERATED {supported} OPTIONAL, scs-60kHz ENUMERATED {supported} OPTIONAL }, fr2-200mhz SEQUENCE { scs-60kHz ENUMERATED {supported} OPTIONAL, scs-120kHz ENUMERATED {supported} OPTIONAL } } OPTIONAL, rasterShift7dot5-IAB-r16 ENUMERATED {supported} OPTIONAL, ue-PowerClass-v1610 ENUMERATED {pc1dot5} OPTIONAL, condHandover-r16 ENUMERATED {supported} OPTIONAL, condHandoverFailure-r16 ENUMERATED {supported} OPTIONAL, condHandoverTwoTriggerEvents-r16 ENUMERATED {supported} OPTIONAL, condPSCellChange-r16 ENUMERATED {supported} OPTIONAL, condPSCellChangeTwoTriggerEvents-r16 ENUMERATED {supported} OPTIONAL, mpr-PowerBoost-FR2-r16 ENUMERATED {supported} OPTIONAL, -- R1 11-9: Multiple active configured grant configurations for a BWP of a serving cell activeConfiguredGrant-r16 SEQUENCE { maxNumberConfigsPerBWP-r16 ENUMERATED {n1, n2, n4, n8, n12}, maxNumberConfigsAllCC-r16 INTEGER (2..32) } OPTIONAL, -- R1 11-9a: Joint release in a DCI for two or more configured grant Type 2 configurations for a given BWP of a serving cell jointReleaseConfiguredGrantType2-r16 ENUMERATED {supported} OPTIONAL, -- R1 12-2: Multiple SPS configurations sps-r16 SEQUENCE { maxNumberConfigsPerBWP-r16 INTEGER (1..8), maxNumberConfigsAllCC-r16 INTEGER (2..32) } OPTIONAL, -- R1 12-2a: Joint release in a DCI for two or more SPS configurations for a given BWP of a serving cell jointReleaseSPS-r16 ENUMERATED {supported} OPTIONAL, -- R1 13-19: Simultaneous positioning SRS and MIMO SRS transmission within a band across multiple CCs simulSRS-TransWithinBand-r16 ENUMERATED {n2} OPTIONAL, trs-AdditionalBandwidth-r16 ENUMERATED {trs-AddBW-Set1, trs-AddBW-Set2} OPTIONAL, handoverIntraF-IAB-r16 ENUMERATED {supported} OPTIONAL ]], [[ -- R1 22-5a: Simultaneous transmission of SRS for antenna switching and SRS for CB/NCB /BM for intra-band UL CA -- R1 22-5c: Simultaneous transmission of SRS for antenna switching and SRS for antenna switching for intra-band UL CA simulTX-SRS-AntSwitchingIntraBandUL-CA-r16 SimulSRS-ForAntennaSwitching-r16 OPTIONAL, -- R1 10: NR-unlicensed sharedSpectrumChAccessParamsPerBand-v1630 SharedSpectrumChAccessParamsPerBand-v1630 OPTIONAL ]], [[ handoverUTRA-FDD-r16 ENUMERATED {supported} OPTIONAL, -- R4 7-4: Report the shorter transient capability supported by the UE: 2, 4 or 7us enhancedUL-TransientPeriod-r16 ENUMERATED {us2, us4, us7} OPTIONAL, sharedSpectrumChAccessParamsPerBand-v1640 SharedSpectrumChAccessParamsPerBand-v1640 OPTIONAL ]], [[ type1-PUSCH-RepetitionMultiSlots-v1650 ENUMERATED {supported} OPTIONAL, type2-PUSCH-RepetitionMultiSlots-v1650 ENUMERATED {supported} OPTIONAL, pusch-RepetitionMultiSlots-v1650 ENUMERATED {supported} OPTIONAL, configuredUL-GrantType1-v1650 ENUMERATED {supported} OPTIONAL, configuredUL-GrantType2-v1650 ENUMERATED {supported} OPTIONAL, sharedSpectrumChAccessParamsPerBand-v1650 SharedSpectrumChAccessParamsPerBand-v1650 OPTIONAL ]], [[ enhancedSkipUplinkTxConfigured-v1660 ENUMERATED {supported} OPTIONAL, enhancedSkipUplinkTxDynamic-v1660 ENUMERATED {supported} OPTIONAL ]], [[ maxUplinkDutyCycle-PC1dot5-MPE-FR1-r16 ENUMERATED {n10, n15, n20, n25, n30, n40, n50, n60, n70, n80, n90, n100} OPTIONAL, txDiversity-r16 ENUMERATED {supported} OPTIONAL ]] } BandNR-v16c0 ::= SEQUENCE { pusch-RepetitionTypeA-v16c0 ENUMERATED {supported} OPTIONAL, ... } -- TAG-RF-PARAMETERS-STOP -- ASN1STOP
RF-Parameters field descriptions |
---|
appliedFreqBandListFilter In this field the UE mirrors the FreqBandList that the NW provided in the capability enquiry, if any. The UE filtered the band combinations in the supportedBandCombinationList in accordance with this appliedFreqBandListFilter. The UE does not include this field if the UE capability is requested by E-UTRAN and the network request includes the field eutra-nr-only [10]. |
supportedBandCombinationList A list of band combinations that the UE supports for NR (and NR-DC, if requested). The FeatureSetCombinationId:s in this list refer to the FeatureSetCombination entries in the featureSetCombinations list in the UE-NR-Capability IE. The UE does not include this field if the UE capability is requested by E-UTRAN and the network request includes the field eutra-nr-only [10]. |
supportedBandCombinationListSidelinkEUTRA-NR A list of band combinations that the UE supports for NR sidelink communication only, for joint NR sidelink communication and V2X sidelink communication, or for V2X sidelink communication only. The UE does not include this field if the UE capability is requested by E-UTRAN (see TS 36.331[10]) and the network request includes the field eutra-nr-only. |
supportedBandCombinationList-UplinkTxSwitch A list of band combinations that the UE supports dynamic uplink Tx switching for NR UL CA and SUL. The FeatureSetCombinationId:s in this list refer to the FeatureSetCombination entries in the featureSetCombinations list in the UE-NR-Capability IE. The UE does not include this field if the UE capability is requested by E-UTRAN and the network request includes the field eutra-nr-only [10]. |
supportedBandListNR A list of NR bands supported by the UE. If supportedBandListNR-v16c0 is included, the UE shall include the same number of entries, and listed in the same order, as in supportedBandListNR (without suffix). |
The IE RF-ParametersMRDC is used to convey RF related capabilities for MR-DC.
-- ASN1START -- TAG-RF-PARAMETERSMRDC-START RF-ParametersMRDC ::= SEQUENCE {supportedBandCombinationListA list of band combinations that the UE supports for (NG)EN-DC, or both (NG)EN-DC and NE-DC. The FeatureSetCombinationId:s in this list refer to the FeatureSetCombination entries in the featureSetCombinations list in the UE-MRDC-Capability IE.BandCombinationList OPTIONAL,appliedFreqBandListFilterIn this field the UE mirrors the FreqBandList that the NW provided in the capability enquiry, if any. The UE filtered the band combinations in the supportedBandCombinationList in accordance with this appliedFreqBandListFilter.FreqBandList OPTIONAL, ..., [[ srs-SwitchingTimeRequested ENUMERATED {true} OPTIONAL, supportedBandCombinationList-v1540 BandCombinationList-v1540 OPTIONAL ]], [[ supportedBandCombinationList-v1550 BandCombinationList-v1550 OPTIONAL ]], [[ supportedBandCombinationList-v1560 BandCombinationList-v1560 OPTIONAL, supportedBandCombinationListNEDC-Only BandCombinationList OPTIONAL ]], [[ supportedBandCombinationList-v1570 BandCombinationList-v1570 OPTIONAL ]], [[ supportedBandCombinationList-v1580 BandCombinationList-v1580 OPTIONAL ]], [[ supportedBandCombinationList-v1590 BandCombinationList-v1590 OPTIONAL ]], [[ supportedBandCombinationListNEDC-Only-v15a0 SEQUENCE { supportedBandCombinationList-v1540 BandCombinationList-v1540 OPTIONAL, supportedBandCombinationList-v1560 BandCombinationList-v1560 OPTIONAL, supportedBandCombinationList-v1570 BandCombinationList-v1570 OPTIONAL, supportedBandCombinationList-v1580 BandCombinationList-v1580 OPTIONAL, supportedBandCombinationList-v1590 BandCombinationList-v1590 OPTIONAL } OPTIONAL ]], [[ supportedBandCombinationList-v1610 BandCombinationList-v1610 OPTIONAL, supportedBandCombinationListNEDC-Only-v1610 BandCombinationList-v1610 OPTIONAL,supportedBandCombinationList-UplinkTxSwitch-r16A list of band combinations that the UE supports dynamic UL Tx switching for (NG)EN-DC. The FeatureSetCombinationId:s in this list refer to the FeatureSetCombination entries in the featureSetCombinations list in the UE-MRDC-Capability IE.BandCombinationList-UplinkTxSwitch-r16 OPTIONAL ]], [[ supportedBandCombinationList-v1630 BandCombinationList-v1630 OPTIONAL, supportedBandCombinationListNEDC-Only-v1630 BandCombinationList-v1630 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1630 BandCombinationList-UplinkTxSwitch-v1630 OPTIONAL ]], [[ supportedBandCombinationList-v1640 BandCombinationList-v1640 OPTIONAL, supportedBandCombinationListNEDC-Only-v1640 BandCombinationList-v1640 OPTIONAL, supportedBandCombinationList-UplinkTxSwitch-v1640 BandCombinationList-UplinkTxSwitch-v1640 OPTIONAL ]], [[ supportedBandCombinationList-UplinkTxSwitch-v1670 BandCombinationList-UplinkTxSwitch-v1670 OPTIONAL ]] } RF-ParametersMRDC-v15g0 ::= SEQUENCE { supportedBandCombinationList-v15g0 BandCombinationList-v15g0 OPTIONAL, supportedBandCombinationListNEDC-Only-v15g0 BandCombinationList-v15g0 OPTIONAL } RF-ParametersMRDC-v15n0 ::= SEQUENCE { supportedBandCombinationList-v15n0 BandCombinationList-v15n0 OPTIONAL } RF-ParametersMRDC-v16e0 ::= SEQUENCE { supportedBandCombinationList-UplinkTxSwitch-v16e0 BandCombinationList-UplinkTxSwitch-v16e0 OPTIONAL } -- TAG-RF-PARAMETERSMRDC-STOP -- ASN1STOP
RF-ParametersMRDC field descriptions |
---|
appliedFreqBandListFilter In this field the UE mirrors the FreqBandList that the NW provided in the capability enquiry, if any. The UE filtered the band combinations in the supportedBandCombinationList in accordance with this appliedFreqBandListFilter. |
supportedBandCombinationList A list of band combinations that the UE supports for (NG)EN-DC, or both (NG)EN-DC and NE-DC. The FeatureSetCombinationId:s in this list refer to the FeatureSetCombination entries in the featureSetCombinations list in the UE-MRDC-Capability IE. |
supportedBandCombinationListNEDC-Only, supportedBandCombinationListNEDC-Only-v1610 A list of band combinations that the UE supports only for NE-DC. The FeatureSetCombinationId:s in this list refer to the FeatureSetCombination entries in the featureSetCombinations list in the UE-MRDC-Capability IE. |
supportedBandCombinationList-UplinkTxSwitch A list of band combinations that the UE supports dynamic UL Tx switching for (NG)EN-DC. The FeatureSetCombinationId:s in this list refer to the FeatureSetCombination entries in the featureSetCombinations list in the UE-MRDC-Capability IE. |
The IE RLC-Parameters is used to convey capabilities related to RLC.
-- ASN1START -- TAG-RLC-PARAMETERS-START RLC-Parameters ::= SEQUENCE { am-WithShortSN ENUMERATED {supported} OPTIONAL, um-WithShortSN ENUMERATED {supported} OPTIONAL, um-WithLongSN ENUMERATED {supported} OPTIONAL, ..., [[ extendedT-PollRetransmit-r16 ENUMERATED {supported} OPTIONAL, extendedT-StatusProhibit-r16 ENUMERATED {supported} OPTIONAL ]] } -- TAG-RLC-PARAMETERS-STOP -- ASN1STOP
The IE SDAP-Parameters is used to convey capabilities related to SDAP.
The IE SidelinkParameters is used to convey capabilities related to NR and V2X sidelink communications.
-- ASN1START -- TAG-SIDELINKPARAMETERS-START SidelinkParameters-r16 ::= SEQUENCE { sidelinkParametersNR-r16 SidelinkParametersNR-r16 OPTIONAL, sidelinkParametersEUTRA-r16 SidelinkParametersEUTRA-r16 OPTIONAL } SidelinkParametersNR-r16 ::= SEQUENCE { rlc-ParametersSidelink-r16 RLC-ParametersSidelink-r16 OPTIONAL, mac-ParametersSidelink-r16 MAC-ParametersSidelink-r16 OPTIONAL, fdd-Add-UE-Sidelink-Capabilities-r16 UE-SidelinkCapabilityAddXDD-Mode-r16 OPTIONAL, tdd-Add-UE-Sidelink-Capabilities-r16 UE-SidelinkCapabilityAddXDD-Mode-r16 OPTIONAL, supportedBandListSidelink-r16 SEQUENCE (SIZE (1..maxBands)) OF BandSidelink-r16 OPTIONAL, ... } SidelinkParametersEUTRA-r16 ::= SEQUENCE { sl-ParametersEUTRA1-r16 OCTET STRING OPTIONAL, sl-ParametersEUTRA2-r16 OCTET STRING OPTIONAL, sl-ParametersEUTRA3-r16 OCTET STRING OPTIONAL, supportedBandListSidelinkEUTRA-r16 SEQUENCE (SIZE (1..maxBandsEUTRA)) OF BandSidelinkEUTRA-r16 OPTIONAL, ... } RLC-ParametersSidelink-r16 ::= SEQUENCE { am-WithLongSN-Sidelink-r16 ENUMERATED {supported} OPTIONAL, um-WithLongSN-Sidelink-r16 ENUMERATED {supported} OPTIONAL, ... } MAC-ParametersSidelink-r16 ::= SEQUENCE { mac-ParametersSidelinkCommon-r16 MAC-ParametersSidelinkCommon-r16 OPTIONAL, mac-ParametersSidelinkXDD-Diff-r16 MAC-ParametersSidelinkXDD-Diff-r16 OPTIONAL, ... } UE-SidelinkCapabilityAddXDD-Mode-r16 ::= SEQUENCE { mac-ParametersSidelinkXDD-Diff-r16 MAC-ParametersSidelinkXDD-Diff-r16 OPTIONAL } MAC-ParametersSidelinkCommon-r16 ::= SEQUENCE { lcp-RestrictionSidelink-r16 ENUMERATED {supported} OPTIONAL, multipleConfiguredGrantsSidelink-r16 ENUMERATED {supported} OPTIONAL, ... } MAC-ParametersSidelinkXDD-Diff-r16 ::= SEQUENCE { multipleSR-ConfigurationsSidelink-r16 ENUMERATED {supported} OPTIONAL, logicalChannelSR-DelayTimerSidelink-r16 ENUMERATED {supported} OPTIONAL, ... } BandSidelinkEUTRA-r16 ::= SEQUENCE { freqBandSidelinkEUTRA-r16 FreqBandIndicatorEUTRA, -- R1 15-7: Transmitting LTE sidelink mode 3 scheduled by NR Uu gnb-ScheduledMode3SidelinkEUTRA-r16 SEQUENCE { gnb-ScheduledMode3DelaySidelinkEUTRA-r16 ENUMERATED {ms0, ms0dot25, ms0dot5, ms0dot625, ms0dot75, ms1, ms1dot25, ms1dot5, ms1dot75, ms2, ms2dot5, ms3, ms4, ms5, ms6, ms8, ms10, ms20} } OPTIONAL, -- R1 15-9: Transmitting LTE sidelink mode 4 configured by NR Uu gnb-ScheduledMode4SidelinkEUTRA-r16 ENUMERATED {supported} OPTIONAL } BandSidelink-r16 ::= SEQUENCE { freqBandSidelink-r16 FreqBandIndicatorNR, --15-1 sl-Reception-r16 SEQUENCE { harq-RxProcessSidelink-r16 ENUMERATED {n16, n24, n32, n48, n64}, pscch-RxSidelink-r16 ENUMERATED {value1, value2}, scs-CP-PatternRxSidelink-r16 CHOICE { fr1-r16 SEQUENCE { scs-15kHz-r16 BIT STRING (SIZE (16)) OPTIONAL, scs-30kHz-r16 BIT STRING (SIZE (16)) OPTIONAL, scs-60kHz-r16 BIT STRING (SIZE (16)) OPTIONAL }, fr2-r16 SEQUENCE { scs-60kHz-r16 BIT STRING (SIZE (16)) OPTIONAL, scs-120kHz-r16 BIT STRING (SIZE (16)) OPTIONAL } } OPTIONAL, extendedCP-RxSidelink-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, --15-2 sl-TransmissionMode1-r16 SEQUENCE { harq-TxProcessModeOneSidelink-r16 ENUMERATED {n8, n16}, scs-CP-PatternTxSidelinkModeOne-r16 CHOICE { fr1-r16 SEQUENCE { scs-15kHz-r16 BIT STRING (SIZE (16)) OPTIONAL, scs-30kHz-r16 BIT STRING (SIZE (16)) OPTIONAL, scs-60kHz-r16 BIT STRING (SIZE (16)) OPTIONAL }, fr2-r16 SEQUENCE { scs-60kHz-r16 BIT STRING (SIZE (16)) OPTIONAL, scs-120kHz-r16 BIT STRING (SIZE (16)) OPTIONAL } }, extendedCP-TxSidelink-r16 ENUMERATED {supported} OPTIONAL, harq-ReportOnPUCCH-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, --15-4 sync-Sidelink-r16 SEQUENCE { gNB-Sync-r16 ENUMERATED {supported} OPTIONAL, gNB-GNSS-UE-SyncWithPriorityOnGNB-ENB-r16 ENUMERATED {supported} OPTIONAL, gNB-GNSS-UE-SyncWithPriorityOnGNSS-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, --15-10 sl-Tx-256QAM-r16 ENUMERATED {supported} OPTIONAL, --15-11 psfch-FormatZeroSidelink-r16 SEQUENCE { psfch-RxNumber ENUMERATED {n5, n15, n25, n32, n35, n45, n50, n64}, psfch-TxNumber ENUMERATED {n4, n8, n16} } OPTIONAL, --15-12 lowSE-64QAM-MCS-TableSidelink-r16 ENUMERATED {supported} OPTIONAL, --15-15 enb-sync-Sidelink-r16 ENUMERATED {supported} OPTIONAL, ..., [[ --15-3 sl-TransmissionMode2-r16 SEQUENCE { harq-TxProcessModeTwoSidelink-r16 ENUMERATED {n8, n16}, scs-CP-PatternTxSidelinkModeTwo-r16 ENUMERATED {supported} OPTIONAL, dl-openLoopPC-Sidelink-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, --15-5 congestionControlSidelink-r16 SEQUENCE { cbr-ReportSidelink-r16 ENUMERATED {supported} OPTIONAL, cbr-CR-TimeLimitSidelink-r16 ENUMERATED {time1, time2} } OPTIONAL, --15-22 fewerSymbolSlotSidelink-r16 ENUMERATED {supported} OPTIONAL, --15-23 sl-openLoopPC-RSRP-ReportSidelink-r16 ENUMERATED {supported} OPTIONAL, --13-1 sl-Rx-256QAM-r16 ENUMERATED {supported} OPTIONAL ]], [[ ue-PowerClassSidelink-r16 ENUMERATED {pc2, pc3, spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL ]] } -- TAG-SIDELINKPARAMETERS-STOP -- ASN1STOP
The IE SimultaneousRxTxPerBandPair contains the simultaneous Rx/Tx UE capability for each band pair in a band combination. SimultaneousRxTxPerBandPair information element
The IE SON-Parameters contains SON related parameters.
SidelinkParametersEUTRA field descriptions |
---|
sl-ParametersEUTRA1, sl-ParametersEUTRA2, sl-ParametersEUTRA3 This field includes IE of SL-Parameters-v1430 (where v2x-eNB-Scheduled-r14 and V2X-SupportedBandCombination-r14 shall not be included), SL-Parameters-v1530 (where V2X-SupportedBandCombination-r1530 shall not be included) and SL-Parameters-v1540 respectively defined in 36.331 [10]. It is used for reporting the per-UE capability for V2X sidelink communication. |
The IE SpatialRelationsSRS-Pos is used to convey spatial relation for SRS for positioning related parameters.
-- ASN1START -- TAG-SPATIALRELATIONSSRS-POS-START SpatialRelationsSRS-Pos-r16 ::= SEQUENCE { spatialRelation-SRS-PosBasedOnSSB-Serving-r16 ENUMERATED {supported} OPTIONAL, spatialRelation-SRS-PosBasedOnCSI-RS-Serving-r16 ENUMERATED {supported} OPTIONAL, spatialRelation-SRS-PosBasedOnPRS-Serving-r16 ENUMERATED {supported} OPTIONAL, spatialRelation-SRS-PosBasedOnSRS-r16 ENUMERATED {supported} OPTIONAL, spatialRelation-SRS-PosBasedOnSSB-Neigh-r16 ENUMERATED {supported} OPTIONAL, spatialRelation-SRS-PosBasedOnPRS-Neigh-r16 ENUMERATED {supported} OPTIONAL } --TAG-SPATIALRELATIONSSRS-POS-STOP -- ASN1STOP
The IE SRS-SwitchingTimeNR is used to indicate the SRS carrier switching time supported by the UE for one NR band pair.
-- ASN1START -- TAG-SRS-SWITCHINGTIMENR-START SRS-SwitchingTimeNR ::= SEQUENCE { switchingTimeDL ENUMERATED {n0us, n30us, n100us, n140us, n200us, n300us, n500us, n900us} OPTIONAL, switchingTimeUL ENUMERATED {n0us, n30us, n100us, n140us, n200us, n300us, n500us, n900us} OPTIONAL } -- TAG-SRS-SWITCHINGTIMENR-STOP -- ASN1STOP
The IE SRS-SwitchingTimeEUTRA is used to indicate the SRS carrier switching time supported by the UE for one E-UTRA band pair.
-- ASN1START -- TAG-SRS-SWITCHINGTIMEEUTRA-START SRS-SwitchingTimeEUTRA ::= SEQUENCE { switchingTimeDL ENUMERATED {n0, n0dot5, n1, n1dot5, n2, n2dot5, n3, n3dot5, n4, n4dot5, n5, n5dot5, n6, n6dot5, n7} OPTIONAL, switchingTimeUL ENUMERATED {n0, n0dot5, n1, n1dot5, n2, n2dot5, n3, n3dot5, n4, n4dot5, n5, n5dot5, n6, n6dot5, n7} OPTIONAL } -- TAG-SRS-SWITCHINGTIMEEUTRA-STOP -- ASN1STOP
The IE SupportedBandwidth is used to indicate the maximum channel bandwidth supported by the UE on one carrier of a band of a band combination.
The IE UE-BasedPerfMeas-Parameters contains UE-based performance measurement parameters.
-- ASN1START -- TAG-UE-BASEDPERFMEAS-PARAMETERS-START UE-BasedPerfMeas-Parameters-r16 ::= SEQUENCE { barometerMeasReport-r16 ENUMERATED {supported} OPTIONAL, immMeasBT-r16 ENUMERATED {supported} OPTIONAL, immMeasWLAN-r16 ENUMERATED {supported} OPTIONAL, loggedMeasBT-r16 ENUMERATED {supported} OPTIONAL, loggedMeasurements-r16 ENUMERATED {supported} OPTIONAL, loggedMeasWLAN-r16 ENUMERATED {supported} OPTIONAL, orientationMeasReport-r16 ENUMERATED {supported} OPTIONAL, speedMeasReport-r16 ENUMERATED {supported} OPTIONAL, gnss-Location-r16 ENUMERATED {supported} OPTIONAL, ulPDCP-Delay-r16 ENUMERATED {supported} OPTIONAL, ... } -- TAG-UE-BASEDPERFMEAS-PARAMETERS-STOP -- ASN1STOP
The IE UE-CapabilityRAT-ContainerList contains a list of radio access technology specific capability containers.
-- ASN1START -- TAG-UE-CAPABILITYRAT-CONTAINERLIST-START UE-CapabilityRAT-ContainerList ::= SEQUENCE (SIZE (0..maxRAT-CapabilityContainers)) OF UE-CapabilityRAT-Container UE-CapabilityRAT-Container ::= SEQUENCE { rat-Type RAT-Type,ue-CapabilityRAT-ContainerContainer for the UE capabilities of the indicated RAT. The encoding is defined in the specification of each RAT: For rat-Type set to nr: the encoding of UE capabilities is defined in UE-NR-Capability. For rat-Type set to eutra-nr: the encoding of UE capabilities is defined in UE-MRDC-Capability. For rat-Type set to eutra: the encoding of UE capabilities is defined in UE-EUTRA-Capability specified in TS 36.331 [10]. For rat-Type set to utra-fdd: the octet string contains the INTER RAT HANDOVER INFO message defined in TS 25.331 [45].OCTET STRING } -- TAG-UE-CAPABILITYRAT-CONTAINERLIST-STOP -- ASN1STOP
UE-CapabilityRAT-ContainerList field descriptions |
---|
ue-CapabilityRAT-Container Container for the UE capabilities of the indicated RAT. The encoding is defined in the specification of each RAT: For rat-Type set to nr: the encoding of UE capabilities is defined in UE-NR-Capability. For rat-Type set to eutra-nr: the encoding of UE capabilities is defined in UE-MRDC-Capability. For rat-Type set to eutra: the encoding of UE capabilities is defined in UE-EUTRA-Capability specified in TS 36.331 [10]. For rat-Type set to utra-fdd: the octet string contains the INTER RAT HANDOVER INFO message defined in TS 25.331 [45]. |
The IE UE-CapabilityRAT-RequestList is used to request UE capabilities for one or more RATs from the UE.
-- ASN1START -- TAG-UE-CAPABILITYRAT-REQUESTLIST-START UE-CapabilityRAT-RequestList ::= SEQUENCE (SIZE (1..maxRAT-CapabilityContainers)) OF UE-CapabilityRAT-Request UE-CapabilityRAT-Request ::= SEQUENCE {rat-TypeThe RAT type for which the NW requests UE capabilities.RAT-Type,capabilityRequestFilterInformation by which the network requests the UE to filter the UE capabilities. For rat-Type set to nr or eutra-nr: the encoding of the capabilityRequestFilter is defined in UE-CapabilityRequestFilterNR. For rat-Type set to eutra: the encoding of the capabilityRequestFilter is defined by UECapabilityEnquiry message defined in TS36.331 [10], in which RAT-Type in UE-CapabilityRequest includes only 'eutra'.OCTET STRING OPTIONAL, -- Need N ... } -- TAG-UE-CAPABILITYRAT-REQUESTLIST-STOP -- ASN1STOP
UE-CapabilityRAT-Request field descriptions |
---|
capabilityRequestFilter Information by which the network requests the UE to filter the UE capabilities. For rat-Type set to nr or eutra-nr: the encoding of the capabilityRequestFilter is defined in UE-CapabilityRequestFilterNR. For rat-Type set to eutra: the encoding of the capabilityRequestFilter is defined by UECapabilityEnquiry message defined in TS36.331 [10], in which RAT-Type in UE-CapabilityRequest includes only 'eutra'. |
rat-Type The RAT type for which the NW requests UE capabilities. |
The IE UE-CapabilityRequestFilterCommon is used to request filtered UE capabilities. The filter is common for all capability containers that are requested.
-- ASN1START -- TAG-UE-CAPABILITYREQUESTFILTERCOMMON-START UE-CapabilityRequestFilterCommon ::= SEQUENCE { mrdc-Request SEQUENCE {omitEN-DCOnly if this field is present, the UE shall omit band combinations and feature set combinations which are only applicable to (NG)EN-DC.ENUMERATED {true} OPTIONAL, -- Need NincludeNR-DCOnly if this field is present, the UE supporting NR-DC shall indicate support for NR-DC in band combinations and include feature set combinations which are applicable to NR-DC.ENUMERATED {true} OPTIONAL, -- Need NincludeNE-DCOnly if this field is present, the UE supporting NE-DC shall indicate support for NE-DC in band combinations and include feature set combinations which are applicable to NE-DC. Band combinations supporting both NE-DC and (NG)EN-DC shall be included in supportedBandCombinationList, band combinations supporting only NE-DC shall be included in supportedBandCombinationListNEDC-Only.ENUMERATED {true} OPTIONAL -- Need N } OPTIONAL, -- Need N ..., [[codebookTypeRequest-r16Only if this field is present, the UE includes SupportedCSI-RS-Resource supported for the codebook type(s) requested within this field (i.e. type I single/multi-panel, type II and type II port selection) into codebookVariantsList, codebookParametersPerBand and codebookParametersPerBC. If this field is present and none of the codebook types is requested within this field (i.e. empty field), the UE includes SupportedCSI-RS-Resource supported for all codebook types into codebookVariantsList, codebookParametersPerBand and codebookParametersPerBC.SEQUENCE { type1-SinglePanel-r16 ENUMERATED {true} OPTIONAL, -- Need N type1-MultiPanel-r16 ENUMERATED {true} OPTIONAL, -- Need N type2-r16 ENUMERATED {true} OPTIONAL, -- Need N type2-PortSelection-r16 ENUMERATED {true} OPTIONAL -- Need N } OPTIONAL, -- Need NuplinkTxSwitchRequest-r16Only if this field is present, the UE supporting dynamic UL Tx switching shall indicate support for UL Tx switching in band combinations which are applicable to inter-band UL CA, SUL and (NG)EN-DC.ENUMERATED {true} OPTIONAL -- Need N ]], [[requestedCellGrouping-r16The NR-DC cell groupings that the NW is interested in, i.e., the bands that it might use in an MCG and the bands that it might use in an SCG. Only if this field is present, the UE indicates NR-DC support for band combinations for which it supports the requested cell grouping, i.e., in which it supports at least one of the mcg bands on MCG and at least one of the scg bands on the SCG. In its supportedBandCombinationList, the UE indicates which of its NR-DC band combinations supports which of the requested cell groupings. The first element in this list is referred to by ID#0, the second by ID#1 and so on. If this field is absent, the UE only includes band combinations for which it supports NR-DC with only FR1 bands in MCG and only FR2 bands in SCG. Example 1: requestedCellGrouping is set to mcg=[n1, n7, n41, n66] and scg=[n78, n261]. This assumes that the NW would always use CA among n1, n7, n41 and n66 (depending on which are deployed on a given site) whereas with n78 and/or n261 the NW may need to use DC. With this filter a UE may report a band combination n1A-n7A-n78A for NR-DC only if it supports that serving cells for n1 and n7 are in the MCG and a serving cell for n78 is in the SCG. The UE may also report a band combination n41C-n261M for NR-DC provided that it supports a serving cell for n41 in the MCG and a serving cell for n261 in the SCG. Example 2: One requestedCellGrouping is set to mcg=[n1, n7, n41, n66] and scg=[n78, n261] and another requestedCellGrouping is set to mcg=[n1, n7, n66] and scg=[ n41, n78, n261]. This assumes that the NW uses sometimes CA among n1, n7, n41 and n66 (as in example 1) and sometimes CA among n1, n7 and n66 but DC towards one or several of n41, n78, n261. If a UE supports n1A-n41A-n78A only if n41A and n78A are in the same cell group, this UE may only indicate cell grouping ID#1 (not #0) in its BC.SEQUENCE (SIZE (1..maxCellGroupings-r16)) OF CellGrouping-r16 OPTIONAL -- Cond NRDC ]] } CellGrouping-r16 ::= SEQUENCE { mcg-r16 SEQUENCE (SIZE (1..maxBands)) OF FreqBandIndicatorNR, scg-r16 SEQUENCE (SIZE (1..maxBands)) OF FreqBandIndicatorNR,mode-r16The mode of NR-DC operation that the NW is interested in for this cell grouping. The value sync means that the UE only indicates NR-DC support for band combinations for which it supports synchronous NR-DC with the requested cell grouping. The value async means that the UE only indicates NR-DC support for band combinations for which it supports asynchronous NR-DC with the requested cell grouping.ENUMERATED {sync, async} } -- TAG-UE-CAPABILITYREQUESTFILTERCOMMON-STOP -- ASN1STOP
UE-CapabilityRequestFilterCommon field descriptions |
---|
codebookTypeRequest Only if this field is present, the UE includes SupportedCSI-RS-Resource supported for the codebook type(s) requested within this field (i.e. type I single/multi-panel, type II and type II port selection) into codebookVariantsList, codebookParametersPerBand and codebookParametersPerBC. If this field is present and none of the codebook types is requested within this field (i.e. empty field), the UE includes SupportedCSI-RS-Resource supported for all codebook types into codebookVariantsList, codebookParametersPerBand and codebookParametersPerBC. |
includeNE-DC Only if this field is present, the UE supporting NE-DC shall indicate support for NE-DC in band combinations and include feature set combinations which are applicable to NE-DC. Band combinations supporting both NE-DC and (NG)EN-DC shall be included in supportedBandCombinationList, band combinations supporting only NE-DC shall be included in supportedBandCombinationListNEDC-Only. |
includeNR-DC Only if this field is present, the UE supporting NR-DC shall indicate support for NR-DC in band combinations and include feature set combinations which are applicable to NR-DC. |
mode The mode of NR-DC operation that the NW is interested in for this cell grouping. The value sync means that the UE only indicates NR-DC support for band combinations for which it supports synchronous NR-DC with the requested cell grouping. The value async means that the UE only indicates NR-DC support for band combinations for which it supports asynchronous NR-DC with the requested cell grouping. |
omitEN-DC Only if this field is present, the UE shall omit band combinations and feature set combinations which are only applicable to (NG)EN-DC. |
requestedCellGrouping The NR-DC cell groupings that the NW is interested in, i.e., the bands that it might use in an MCG and the bands that it might use in an SCG. Only if this field is present, the UE indicates NR-DC support for band combinations for which it supports the requested cell grouping, i.e., in which it supports at least one of the mcg bands on MCG and at least one of the scg bands on the SCG. In its supportedBandCombinationList, the UE indicates which of its NR-DC band combinations supports which of the requested cell groupings. The first element in this list is referred to by ID#0, the second by ID#1 and so on. If this field is absent, the UE only includes band combinations for which it supports NR-DC with only FR1 bands in MCG and only FR2 bands in SCG. Example 1: requestedCellGrouping is set to mcg=[n1, n7, n41, n66] and scg=[n78, n261]. This assumes that the NW would always use CA among n1, n7, n41 and n66 (depending on which are deployed on a given site) whereas with n78 and/or n261 the NW may need to use DC. With this filter a UE may report a band combination n1A-n7A-n78A for NR-DC only if it supports that serving cells for n1 and n7 are in the MCG and a serving cell for n78 is in the SCG. The UE may also report a band combination n41C-n261M for NR-DC provided that it supports a serving cell for n41 in the MCG and a serving cell for n261 in the SCG. Example 2: One requestedCellGrouping is set to mcg=[n1, n7, n41, n66] and scg=[n78, n261] and another requestedCellGrouping is set to mcg=[n1, n7, n66] and scg=[ n41, n78, n261]. This assumes that the NW uses sometimes CA among n1, n7, n41 and n66 (as in example 1) and sometimes CA among n1, n7 and n66 but DC towards one or several of n41, n78, n261. If a UE supports n1A-n41A-n78A only if n41A and n78A are in the same cell group, this UE may only indicate cell grouping ID#1 (not #0) in its BC. |
uplinkTxSwitchRequest Only if this field is present, the UE supporting dynamic UL Tx switching shall indicate support for UL Tx switching in band combinations which are applicable to inter-band UL CA, SUL and (NG)EN-DC. |
Conditional Presence | Explanation |
---|---|
NRDC | The field is optionally present, Need N, if includeNR-DC is included. It is absent otherwise. |
The IE UE-CapabilityRequestFilterNR is used to request filtered UE capabilities.
-- ASN1START -- TAG-UE-CAPABILITYREQUESTFILTERNR-START UE-CapabilityRequestFilterNR ::= SEQUENCE { frequencyBandListFilter FreqBandList OPTIONAL, -- Need N nonCriticalExtension UE-CapabilityRequestFilterNR-v1540 OPTIONAL } UE-CapabilityRequestFilterNR-v1540 ::= SEQUENCE { srs-SwitchingTimeRequest ENUMERATED {true} OPTIONAL, -- Need N nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-UE-CAPABILITYREQUESTFILTERNR-STOP -- ASN1STOP
The IE UE-MRDC-Capability is used to convey the UE Radio Access Capability Parameters for MR-DC, see TS 38.306 [26].
-- ASN1START -- TAG-UE-MRDC-CAPABILITY-START UE-MRDC-Capability ::= SEQUENCE { measAndMobParametersMRDC MeasAndMobParametersMRDC OPTIONAL, phy-ParametersMRDC-v1530 Phy-ParametersMRDC OPTIONAL, rf-ParametersMRDC RF-ParametersMRDC, generalParametersMRDC GeneralParametersMRDC-XDD-Diff OPTIONAL, fdd-Add-UE-MRDC-Capabilities UE-MRDC-CapabilityAddXDD-Mode OPTIONAL, tdd-Add-UE-MRDC-Capabilities UE-MRDC-CapabilityAddXDD-Mode OPTIONAL, fr1-Add-UE-MRDC-Capabilities UE-MRDC-CapabilityAddFRX-Mode OPTIONAL, fr2-Add-UE-MRDC-Capabilities UE-MRDC-CapabilityAddFRX-Mode OPTIONAL,featureSetCombinationsA list of FeatureSetCombination:s for supportedBandCombinationList and supportedBandCombinationListNEDC-Only in UE-MRDC-Capability. The FeatureSetDownlink:s and FeatureSetUplink:s referred to from these FeatureSetCombination:s are defined in the featureSets list in UE-NR-Capability.SEQUENCE (SIZE (1..maxFeatureSetCombinations)) OF FeatureSetCombination OPTIONAL, pdcp-ParametersMRDC-v1530 PDCP-ParametersMRDC OPTIONAL, lateNonCriticalExtension OCTET STRING (CONTAINING UE-MRDC-Capability-v15g0) OPTIONAL, nonCriticalExtension UE-MRDC-Capability-v1560 OPTIONAL } -- Regular non-critical extensions: UE-MRDC-Capability-v1560 ::= SEQUENCE { receivedFilters OCTET STRING (CONTAINING UECapabilityEnquiry-v1560-IEs) OPTIONAL, measAndMobParametersMRDC-v1560 MeasAndMobParametersMRDC-v1560 OPTIONAL, fdd-Add-UE-MRDC-Capabilities-v1560 UE-MRDC-CapabilityAddXDD-Mode-v1560 OPTIONAL, tdd-Add-UE-MRDC-Capabilities-v1560 UE-MRDC-CapabilityAddXDD-Mode-v1560 OPTIONAL, nonCriticalExtension UE-MRDC-Capability-v1610 OPTIONAL } UE-MRDC-Capability-v1610 ::= SEQUENCE { measAndMobParametersMRDC-v1610 MeasAndMobParametersMRDC-v1610 OPTIONAL, generalParametersMRDC-v1610 GeneralParametersMRDC-v1610 OPTIONAL, pdcp-ParametersMRDC-v1610 PDCP-ParametersMRDC-v1610 OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- Late non-critical extensions: UE-MRDC-Capability-v15g0 ::= SEQUENCE { rf-ParametersMRDC-v15g0 RF-ParametersMRDC-v15g0 OPTIONAL, nonCriticalExtension UE-MRDC-Capability-v15n0 OPTIONAL } UE-MRDC-Capability-v15n0 ::= SEQUENCE { rf-ParametersMRDC-v15n0 RF-ParametersMRDC-v15n0 OPTIONAL, -- Following field is only for REL-15 late non-critical extensions lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension UE-MRDC-Capability-v16e0 OPTIONAL } UE-MRDC-Capability-v16e0 ::= SEQUENCE { rf-ParametersMRDC-v16e0 RF-ParametersMRDC-v16e0 OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } UE-MRDC-CapabilityAddXDD-Mode ::= SEQUENCE { measAndMobParametersMRDC-XDD-Diff MeasAndMobParametersMRDC-XDD-Diff OPTIONAL, generalParametersMRDC-XDD-Diff GeneralParametersMRDC-XDD-Diff OPTIONAL } UE-MRDC-CapabilityAddXDD-Mode-v1560 ::= SEQUENCE { measAndMobParametersMRDC-XDD-Diff-v1560 MeasAndMobParametersMRDC-XDD-Diff-v1560 OPTIONAL } UE-MRDC-CapabilityAddFRX-Mode ::= SEQUENCE { measAndMobParametersMRDC-FRX-Diff MeasAndMobParametersMRDC-FRX-Diff } GeneralParametersMRDC-XDD-Diff ::= SEQUENCE { splitSRB-WithOneUL-Path ENUMERATED {supported} OPTIONAL, splitDRB-withUL-Both-MCG-SCG ENUMERATED {supported} OPTIONAL, srb3 ENUMERATED {supported} OPTIONAL, dummy ENUMERATED {supported} OPTIONAL, ... } GeneralParametersMRDC-v1610 ::= SEQUENCE { f1c-OverEUTRA-r16 ENUMERATED {supported} OPTIONAL } -- TAG-UE-MRDC-CAPABILITY-STOP -- ASN1STOP
UE-MRDC-Capability field descriptions |
---|
featureSetCombinations A list of FeatureSetCombination:s for supportedBandCombinationList and supportedBandCombinationListNEDC-Only in UE-MRDC-Capability. The FeatureSetDownlink:s and FeatureSetUplink:s referred to from these FeatureSetCombination:s are defined in the featureSets list in UE-NR-Capability. |
The IE UE-NR-Capability is used to convey the NR UE Radio Access Capability Parameters, see TS 38.306 [26].
-- ASN1START -- TAG-UE-NR-CAPABILITY-START UE-NR-Capability ::= SEQUENCE { accessStratumRelease AccessStratumRelease, pdcp-Parameters PDCP-Parameters, rlc-Parameters RLC-Parameters OPTIONAL, mac-Parameters MAC-Parameters OPTIONAL, phy-Parameters Phy-Parameters, rf-Parameters RF-Parameters, measAndMobParameters MeasAndMobParameters OPTIONAL, fdd-Add-UE-NR-Capabilities UE-NR-CapabilityAddXDD-Mode OPTIONAL, tdd-Add-UE-NR-Capabilities UE-NR-CapabilityAddXDD-Mode OPTIONAL, fr1-Add-UE-NR-Capabilities UE-NR-CapabilityAddFRX-Mode OPTIONAL, fr2-Add-UE-NR-Capabilities UE-NR-CapabilityAddFRX-Mode OPTIONAL, featureSets FeatureSets OPTIONAL,featureSetCombinationsA list of FeatureSetCombination:s for supportedBandCombinationList in UE-NR-Capability. The FeatureSetDownlink:s and FeatureSetUplink:s referred to from these FeatureSetCombination:s are defined in the featureSets list in UE-NR-Capability.SEQUENCE (SIZE (1..maxFeatureSetCombinations)) OF FeatureSetCombination OPTIONAL, lateNonCriticalExtension OCTET STRING (CONTAINING UE-NR-Capability-v15c0) OPTIONAL, nonCriticalExtension UE-NR-Capability-v1530 OPTIONAL } -- Regular non-critical Rel-15 extensions: UE-NR-Capability-v1530 ::= SEQUENCE { fdd-Add-UE-NR-Capabilities-v1530 UE-NR-CapabilityAddXDD-Mode-v1530 OPTIONAL, tdd-Add-UE-NR-Capabilities-v1530 UE-NR-CapabilityAddXDD-Mode-v1530 OPTIONAL, dummy ENUMERATED {supported} OPTIONAL, interRAT-Parameters InterRAT-Parameters OPTIONAL, inactiveState ENUMERATED {supported} OPTIONAL, delayBudgetReporting ENUMERATED {supported} OPTIONAL, nonCriticalExtension UE-NR-Capability-v1540 OPTIONAL } UE-NR-Capability-v1540 ::= SEQUENCE { sdap-Parameters SDAP-Parameters OPTIONAL, overheatingInd ENUMERATED {supported} OPTIONAL, ims-Parameters IMS-Parameters OPTIONAL, fr1-Add-UE-NR-Capabilities-v1540 UE-NR-CapabilityAddFRX-Mode-v1540 OPTIONAL, fr2-Add-UE-NR-Capabilities-v1540 UE-NR-CapabilityAddFRX-Mode-v1540 OPTIONAL, fr1-fr2-Add-UE-NR-Capabilities UE-NR-CapabilityAddFRX-Mode OPTIONAL, nonCriticalExtension UE-NR-Capability-v1550 OPTIONAL } UE-NR-Capability-v1550 ::= SEQUENCE { reducedCP-Latency ENUMERATED {supported} OPTIONAL, nonCriticalExtension UE-NR-Capability-v1560 OPTIONAL } UE-NR-Capability-v1560 ::= SEQUENCE { nrdc-Parameters NRDC-Parameters OPTIONAL, receivedFilters OCTET STRING (CONTAINING UECapabilityEnquiry-v1560-IEs) OPTIONAL, nonCriticalExtension UE-NR-Capability-v1570 OPTIONAL } UE-NR-Capability-v1570 ::= SEQUENCE { nrdc-Parameters-v1570 NRDC-Parameters-v1570 OPTIONAL, nonCriticalExtension UE-NR-Capability-v1610 OPTIONAL } -- Late non-critical Rel-15 extensions: UE-NR-Capability-v15c0 ::= SEQUENCE { nrdc-Parameters-v15c0 NRDC-Parameters-v15c0 OPTIONAL, partialFR2-FallbackRX-Req ENUMERATED {true} OPTIONAL, nonCriticalExtension UE-NR-Capability-v15g0 OPTIONAL } UE-NR-Capability-v15g0 ::= SEQUENCE { rf-Parameters-v15g0 RF-Parameters-v15g0 OPTIONAL, nonCriticalExtension UE-NR-Capability-v15j0 OPTIONAL } UE-NR-Capability-v15j0 ::= SEQUENCE { -- Following field is only for REL-15 late non-critical extensions lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension UE-NR-Capability-v16a0 OPTIONAL } -- Regular non-critical Rel-16 extensions: UE-NR-Capability-v1610 ::= SEQUENCE { inDeviceCoexInd-r16 ENUMERATED {supported} OPTIONAL, dl-DedicatedMessageSegmentation-r16 ENUMERATED {supported} OPTIONAL, nrdc-Parameters-v1610 NRDC-Parameters-v1610 OPTIONAL, powSav-Parameters-r16 PowSav-Parameters-r16 OPTIONAL, fr1-Add-UE-NR-Capabilities-v1610 UE-NR-CapabilityAddFRX-Mode-v1610 OPTIONAL, fr2-Add-UE-NR-Capabilities-v1610 UE-NR-CapabilityAddFRX-Mode-v1610 OPTIONAL, bh-RLF-Indication-r16 ENUMERATED {supported} OPTIONAL, directSN-AdditionFirstRRC-IAB-r16 ENUMERATED {supported} OPTIONAL, bap-Parameters-r16 BAP-Parameters-r16 OPTIONAL, referenceTimeProvision-r16 ENUMERATED {supported} OPTIONAL, sidelinkParameters-r16 SidelinkParameters-r16 OPTIONAL, highSpeedParameters-r16 HighSpeedParameters-r16 OPTIONAL, mac-Parameters-v1610 MAC-Parameters-v1610 OPTIONAL, mcgRLF-RecoveryViaSCG-r16 ENUMERATED {supported} OPTIONAL, resumeWithStoredMCG-SCells-r16 ENUMERATED {supported} OPTIONAL, resumeWithStoredSCG-r16 ENUMERATED {supported} OPTIONAL, resumeWithSCG-Config-r16 ENUMERATED {supported} OPTIONAL, ue-BasedPerfMeas-Parameters-r16 UE-BasedPerfMeas-Parameters-r16 OPTIONAL, son-Parameters-r16 SON-Parameters-r16 OPTIONAL, onDemandSIB-Connected-r16 ENUMERATED {supported} OPTIONAL, nonCriticalExtension UE-NR-Capability-v1640 OPTIONAL } UE-NR-Capability-v1640 ::= SEQUENCE { redirectAtResumeByNAS-r16 ENUMERATED {supported} OPTIONAL, phy-ParametersSharedSpectrumChAccess-r16 Phy-ParametersSharedSpectrumChAccess-r16 OPTIONAL, nonCriticalExtension UE-NR-Capability-v1650 OPTIONAL } UE-NR-Capability-v1650 ::= SEQUENCE { mpsPriorityIndication-r16 ENUMERATED {supported} OPTIONAL, highSpeedParameters-v1650 HighSpeedParameters-v1650 OPTIONAL, nonCriticalExtension UE-NR-Capability-v1690 OPTIONAL } UE-NR-Capability-v1690 ::= SEQUENCE { ul-RRC-Segmentation-r16 ENUMERATED {supported} OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } -- Late non-critical Rel-16 extensions: UE-NR-Capability-v16a0 ::= SEQUENCE { phy-Parameters-v16a0 Phy-Parameters-v16a0 OPTIONAL, rf-Parameters-v16a0 RF-Parameters-v16a0 OPTIONAL, nonCriticalExtension UE-NR-Capability-v16c0 OPTIONAL } UE-NR-Capability-v16c0 ::= SEQUENCE { rf-Parameters-v16c0 RF-Parameters-v16c0 OPTIONAL, nonCriticalExtension UE-NR-Capability-v16d0 OPTIONAL } UE-NR-Capability-v16d0 ::= SEQUENCE { featureSets-v16d0 FeatureSets-v16d0 OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } UE-NR-CapabilityAddXDD-Mode ::= SEQUENCE { phy-ParametersXDD-Diff Phy-ParametersXDD-Diff OPTIONAL, mac-ParametersXDD-Diff MAC-ParametersXDD-Diff OPTIONAL, measAndMobParametersXDD-Diff MeasAndMobParametersXDD-Diff OPTIONAL } UE-NR-CapabilityAddXDD-Mode-v1530 ::= SEQUENCE { eutra-ParametersXDD-Diff EUTRA-ParametersXDD-Diff } UE-NR-CapabilityAddFRX-Mode ::= SEQUENCE { phy-ParametersFRX-Diff Phy-ParametersFRX-Diff OPTIONAL, measAndMobParametersFRX-Diff MeasAndMobParametersFRX-Diff OPTIONAL } UE-NR-CapabilityAddFRX-Mode-v1540 ::= SEQUENCE { ims-ParametersFRX-Diff IMS-ParametersFRX-Diff OPTIONAL } UE-NR-CapabilityAddFRX-Mode-v1610 ::= SEQUENCE { powSav-ParametersFRX-Diff-r16 PowSav-ParametersFRX-Diff-r16 OPTIONAL, mac-ParametersFRX-Diff-r16 MAC-ParametersFRX-Diff-r16 OPTIONAL } BAP-Parameters-r16 ::= SEQUENCE { flowControlBH-RLC-ChannelBased-r16 ENUMERATED {supported} OPTIONAL, flowControlRouting-ID-Based-r16 ENUMERATED {supported} OPTIONAL } -- TAG-UE-NR-CAPABILITY-STOP -- ASN1STOP
UE-NR-Capability field descriptions |
---|
featureSetCombinations A list of FeatureSetCombination:s for supportedBandCombinationList in UE-NR-Capability. The FeatureSetDownlink:s and FeatureSetUplink:s referred to from these FeatureSetCombination:s are defined in the featureSets list in UE-NR-Capability. |
The IE SharedSpectrumChAccessParamsPerBand is used to convey shared channel access related parameters specific for a certain frequency band (not per feature set or band combination).
-- ASN1START -- TAG-SHAREDSPECTRUMCHACCESSPARAMSPERBAND-START SharedSpectrumChAccessParamsPerBand-r16 ::= SEQUENCE { -- R1 10-1: UL channel access for dynamic channel access mode ul-DynamicChAccess-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-1a: UL channel access for semi-static channel access mode ul-Semi-StaticChAccess-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-2: SSB-based RRM for dynamic channel access mode ssb-RRM-DynamicChAccess-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-2a: SSB-based RRM for semi-static channel access mode ssb-RRM-Semi-StaticChAccess-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-2b: MIB reading on unlicensed cell mib-Acquisition-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-2c: SSB-based RLM for dynamic channel access mode ssb-RLM-DynamicChAccess-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-2d: SSB-based RLM for semi-static channel access mode ssb-RLM-Semi-StaticChAccess-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-2e: SIB1 reception on unlicensed cell sib1-Acquisition-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-2f: Support monitoring of extended RAR window extRA-ResponseWindow-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-2g: SSB-based BFD/CBD for dynamic channel access mode ssb-BFD-CBD-dynamicChannelAccess-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-2h: SSB-based BFD/CBD for semi-static channel access mode ssb-BFD-CBD-semi-staticChannelAccess-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-2i: CSI-RS-based BFD/CBD for NR-U csi-RS-BFD-CBD-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-7: UL channel access for 10 MHz SCell ul-ChannelBW-SCell-10mhz-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-10: RSSI and channel occupancy measurement and reporting rssi-ChannelOccupancyReporting-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-11:SRS starting position at any OFDM symbol in a slot srs-StartAnyOFDM-Symbol-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-20: Support search space set configuration with freqMonitorLocation-r16 searchSpaceFreqMonitorLocation-r16 INTEGER (1..5) OPTIONAL, -- R1 10-20a: Support coreset configuration with rb-Offset coreset-RB-Offset-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-23:CGI reading on unlicensed cell for ANR functionality cgi-Acquisition-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-25: Enable configured UL transmissions when DCI 2_0 is configured but not detected configuredUL-Tx-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-27: Wideband PRACH prach-Wideband-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-29: Support available RB set indicator field in DCI 2_0 dci-AvailableRB-Set-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-30: Support channel occupancy duration indicator field in DCI 2_0 dci-ChOccupancyDuration-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-8: Type B PDSCH length {3, 5, 6, 8, 9, 10, 11, 12, 13} without DMRS shift due to CRS collision typeB-PDSCH-length-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-9: Search space set group switching with explicit DCI 2_0 bit field trigger or with implicit PDCCH decoding with DCI 2_0 monitoring searchSpaceSwitchWithDCI-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-9b: Search space set group switching with implicit PDCCH decoding without DCI 2_0 monitoring searchSpaceSwitchWithoutDCI-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-9d: Support Search space set group switching capability 2 searchSpaceSwitchCapability2-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-14: Non-numerical PDSCH to HARQ-ACK timing non-numericalPDSCH-HARQ-timing-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-15: Enhanced dynamic HARQ codebook enhancedDynamicHARQ-codebook-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-16: One-shot HARQ ACK feedback oneShotHARQ-feedback-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-17: Multi-PUSCH UL grant multiPUSCH-UL-grant-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-26: CSI-RS based RLM for NR-U csi-RS-RLM-r16 ENUMERATED {supported} OPTIONAL, dummy ENUMERATED {supported} OPTIONAL, -- R1 10-31: Support of P/SP-CSI-RS reception with CSI-RS-ValidationWith-DCI-r16 configured periodicAndSemi-PersistentCSI-RS-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-3: PRB interlace mapping for PUSCH pusch-PRB-interlace-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-3a: PRB interlace mapping for PUCCH pucch-F0-F1-PRB-Interlace-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-12: OCC for PRB interlace mapping for PF2 and PF3 occ-PRB-PF2-PF3-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-13a: Extended CP range of more than one symbol for CG-PUSCH extCP-rangeCG-PUSCH-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-18: Configured grant with retransmission in CG resources configuredGrantWithReTx-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-21a: Support using ED threshold given by gNB for UL to DL COT sharing ed-Threshold-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-21b: Support UL to DL COT sharing ul-DL-COT-Sharing-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-24: CG-UCI multiplexing with HARQ ACK mux-CG-UCI-HARQ-ACK-r16 ENUMERATED {supported} OPTIONAL, -- R1 10-28: Configured grant with Rel-16 enhanced resource configuration cg-resourceConfig-r16 ENUMERATED {supported} OPTIONAL } SharedSpectrumChAccessParamsPerBand-v1630 ::= SEQUENCE { -- R4 4-1: DL reception in intra-carrier guardband dl-ReceptionIntraCellGuardband-r16 ENUMERATED {supported} OPTIONAL, -- R4 4-2: DL reception when gNB does not transmit on all RB sets of a carrier as a result of LBT dl-ReceptionLBT-subsetRB-r16 ENUMERATED {supported} OPTIONAL } SharedSpectrumChAccessParamsPerBand-v1640 ::= SEQUENCE { -- 10-26b(1-4): CSI-RS based RRM measurement with associated SS-block csi-RSRP-AndRSRQ-MeasWithSSB-r16 ENUMERATED {supported} OPTIONAL, -- 10-26c(1-5): CSI-RS based RRM measurement without associated SS-block csi-RSRP-AndRSRQ-MeasWithoutSSB-r16 ENUMERATED {supported} OPTIONAL, -- 10-26d(1-6): CSI-RS based RS-SINR measurement csi-SINR-Meas-r16 ENUMERATED {supported} OPTIONAL, -- 10-26e(1-8): RLM based on a mix of SS block and CSI-RS signals within active BWP ssb-AndCSI-RS-RLM-r16 ENUMERATED {supported} OPTIONAL, -- 10-26f(1-9): CSI-RS based contention free RA for HO csi-RS-CFRA-ForHO-r16 ENUMERATED {supported} OPTIONAL } SharedSpectrumChAccessParamsPerBand-v1650 ::= SEQUENCE { -- Extension of R1 10-9 capability to configure up to 16 instead of 4 cells or cell groups, respectively extendedSearchSpaceSwitchWithDCI-r16 ENUMERATED {supported} OPTIONAL } -- TAG-SHAREDSPECTRUMCHACCESSPARAMSPERBAND-STOP -- ASN1STOP
UE-NR-Capability-v1540 field descriptions |
---|
fr1-fr2-Add-UE-NR-Capabilities This instance of UE-NR-CapabilityAddFRX-Mode does not include any other fields than csi-RS-IM-ReceptionForFeedback/ csi-RS-ProcFrameworkForSRS/ csi-ReportFramework. |
The IE AbsoluteTimeInfo indicates an absolute time in a format YY-MM-DD HH:MM:SS and using BCD encoding. The first/ leftmost bit of the bit string contains the most significant bit of the most significant digit of the year and so on.
The AreaConfiguration indicates area for which UE is requested to perform measurement logging. If not configured, measurement logging is not restricted to specific cells or tracking areas but applies as long as the RPLMN is contained in plmn-IdentityList stored in VarLogMeasReport.
-- ASN1START -- TAG-AREACONFIGURATION-START AreaConfiguration-r16 ::= SEQUENCE { areaConfig-r16 AreaConfig-r16, interFreqTargetList-r16 SEQUENCE(SIZE(1..maxFreq)) OF InterFreqTargetInfo-r16 OPTIONAL -- Need R } AreaConfig-r16 ::= CHOICE { cellGlobalIdList-r16 CellGlobalIdList-r16, trackingAreaCodeList-r16 TrackingAreaCodeList-r16, trackingAreaIdentityList-r16 TrackingAreaIdentityList-r16 } InterFreqTargetInfo-r16 ::= SEQUENCE { dl-CarrierFreq-r16 ARFCN-ValueNR, cellList-r16 SEQUENCE (SIZE (1..32)) OF PhysCellId OPTIONAL -- Need R } CellGlobalIdList-r16 ::= SEQUENCE (SIZE (1..32)) OF CGI-Info-Logging-r16 TrackingAreaCodeList-r16 ::= SEQUENCE (SIZE (1..8)) OF TrackingAreaCode TrackingAreaIdentityList-r16 ::= SEQUENCE (SIZE (1..8)) OF TrackingAreaIdentity-r16 TrackingAreaIdentity-r16 ::= SEQUENCE { plmn-Identity-r16 PLMN-Identity, trackingAreaCode-r16 TrackingAreaCode } -- TAG-AREACONFIGURATION-STOP -- ASN1STOP
The IE BT-NameList is used to indicate the names of the Bluetooth beacon which the UE is configured to measure.
-- ASN1START -- TAG-BTNAMELIST-START BT-NameList-r16 ::= SEQUENCE (SIZE (1..maxBT-Name-r16)) OF BT-Name-r16 BT-Name-r16 ::= OCTET STRING (SIZE (1..248)) -- TAG-BTNAMELIST-STOP -- ASN1STOP
The IE EUTRA-AllowedMeasBandwidth is used to indicate the maximum allowed measurement bandwidth on a carrier frequency as defined by the parameter Transmission Bandwidth Configuration "NRB" in TS 36.104 [33]. The values mbw6, mbw15, mbw25, mbw50, mbw75, mbw100 indicate 6, 15, 25, 50, 75 and 100 resource blocks, respectively.
AreaConfigurationfield descriptions |
---|
InterFreqTargetInfo If configured, it indicates the neighbouring frequency and cells for which UE is requested to perform measurement logging. |
BT-NameListfield descriptions |
---|
bt-Name If configured, the UE only performs Bluetooth measurements according to the names identified. For each name, it refers to LOCAL NAME defined in Bluetooth specification [51]. |
The IE EUTRA-MBSFN-SubframeConfigList is used to define an E-UTRA MBSFN subframe pattern (for the purpose of NR rate matching).
-- ASN1START -- TAG-EUTRA-MBSFN-SUBFRAMECONFIGLIST-START EUTRA-MBSFN-SubframeConfigList ::= SEQUENCE (SIZE (1..maxMBSFN-Allocations)) OF EUTRA-MBSFN-SubframeConfig EUTRA-MBSFN-SubframeConfig ::= SEQUENCE {radioframeAllocationPeriodField as defined in MBSFN-SubframeConfig in TS 36.331 [10],where SFN refers to the SFN of the NR serving cell.ENUMERATED {n1, n2, n4, n8, n16, n32},radioframeAllocationOffsetField as defined in MBSFN-SubframeConfig in TS 36.331 [10].INTEGER (0..7),subframeAllocation1Field as defined in MBSFN-SubframeConfig in TS 36.331 [10], where the UE assumes the duplex mode (FDD or TDD) of the NR cell for which the E-UTRA-MBSFN-SubframeConfig is provided.CHOICE { oneFrame BIT STRING (SIZE(6)), fourFrames BIT STRING (SIZE(24)) },subframeAllocation2Field as defined in MBSFN-SubframeConfig-v1430 in TS 36.331 [10], where the UE assumes the duplex mode (FDD or TDD) of the NR cell for which the E-UTRA-MBSFN-SubframeConfig is provided.CHOICE { oneFrame BIT STRING (SIZE(2)), fourFrames BIT STRING (SIZE(8)) } OPTIONAL, -- Need R ... } -- TAG-EUTRA-MBSFN-SUBFRAMECONFIGLIST-STOP -- ASN1STOP
EUTRA-MBSFN-SubframeConfig field descriptions |
---|
radioframeAllocationOffset Field as defined in MBSFN-SubframeConfig in TS 36.331 [10]. |
radioframeAllocationPeriod Field as defined in MBSFN-SubframeConfig in TS 36.331 [10],where SFN refers to the SFN of the NR serving cell. |
subframeAllocation1 Field as defined in MBSFN-SubframeConfig in TS 36.331 [10], where the UE assumes the duplex mode (FDD or TDD) of the NR cell for which the E-UTRA-MBSFN-SubframeConfig is provided. |
subframeAllocation2 Field as defined in MBSFN-SubframeConfig-v1430 in TS 36.331 [10], where the UE assumes the duplex mode (FDD or TDD) of the NR cell for which the E-UTRA-MBSFN-SubframeConfig is provided. |
The IE EUTRA-MultiBandInfoList indicates the list of frequency bands in addition to the band represented by CarrierFreq for which cell reselection parameters are common, and a list of additionalPmax and additionalSpectrumEmission.
-- ASN1START -- TAG-EUTRA-MULTIBANDINFOLIST-START EUTRA-MultiBandInfoList ::= SEQUENCE (SIZE (1..maxMultiBands)) OF EUTRA-MultiBandInfo EUTRA-MultiBandInfo ::= SEQUENCE { eutra-FreqBandIndicator FreqBandIndicatorEUTRA, eutra-NS-PmaxList EUTRA-NS-PmaxList OPTIONAL -- Need R } -- TAG-EUTRA-MULTIBANDINFOLIST-STOP -- ASN1STOP
The IE EUTRA-NS-PmaxList concerns a list of additionalPmax and additionalSpectrumEmission, as defined in TS 36.101 [22], table 6.2.4-1 for UEs neither in CE nor BL UEs and TS 36.101 [22], table 6.2.4E-1 for UEs in CE or BL UEs, for a given frequency band.
-- ASN1START -- TAG-EUTRA-NS-PMAXLIST-START EUTRA-NS-PmaxList ::= SEQUENCE (SIZE (1..maxEUTRA-NS-Pmax)) OF EUTRA-NS-PmaxValue EUTRA-NS-PmaxValue ::= SEQUENCE { additionalPmax INTEGER (-30..33) OPTIONAL, -- Need R additionalSpectrumEmission INTEGER (1..288) OPTIONAL -- Need R } -- TAG-EUTRA-NS-PMAXLIST-STOP -- ASN1STOP
The IE EUTRA-PhysCellId is used to indicate the physical layer identity of the cell, as defined in TS 36.211 [31].
The IE EUTRA-PhysCellIdRange is used to encode either a single or a range of physical cell identities. The range is encoded by using a start value and by indicating the number of consecutive physical cell identities (including start) in the range. For fields comprising multiple occurrences of EUTRA-PhysCellIdRange, NW may configure overlapping ranges of physical cell identities.
-- ASN1START -- TAG-EUTRA-PHYSCELLIDRANGE-START EUTRA-PhysCellIdRange ::= SEQUENCE { start EUTRA-PhysCellId, range ENUMERATED {n4, n8, n12, n16, n24, n32, n48, n64, n84, n96, n128, n168, n252, n504, spare2, spare1} OPTIONAL -- Need N } -- TAG-EUTRA-PHYSCELLIDRANGE-STOP -- ASN1STOP
The IE EUTRA-PresenceAntennaPort1 is used to indicate whether all the neighbouring cells use Antenna Port 1. When set to true, the UE may assume that at least two cell-specific antenna ports are used in all neighbouring cells.
The IE EUTRA-Q-OffsetRange is used to indicate a cell, or frequency specific offset to be applied when evaluating triggering conditions for measurement reporting. The value in dB. Value dB-24 corresponds to -24 dB, value dB-22 corresponds to -22 dB and so on.
-- ASN1START -- TAG-EUTRA-Q-OFFSETRANGE-START EUTRA-Q-OffsetRange ::= ENUMERATED { dB-24, dB-22, dB-20, dB-18, dB-16, dB-14, dB-12, dB-10, dB-8, dB-6, dB-5, dB-4, dB-3, dB-2, dB-1, dB0, dB1, dB2, dB3, dB4, dB5, dB6, dB8, dB10, dB12, dB14, dB16, dB18, dB20, dB22, dB24} -- TAG-EUTRA-Q-OFFSETRANGE-STOP -- ASN1STOP
The IE IAB-IP-Address is used to indicate the IP address/prefix.
The IE IAB-IP-AddressIndex is used to identify a configuration of an IP address.
The IE IAB-IP-Usage is used to indicate the usage of the assigned IP address/prefix.
The LoggingDuration indicates the duration for which UE is requested to perform measurement logging. Value min10 corresponds to 10 minutes, value min20 corresponds to 20 minutes and so on.
The LoggingInterval indicates the periodicity for logging measurement results. Value ms1280 corresponds to 1.28s, value ms2560 corresponds to 2.56s and so on. Value infinity means it is equal to the configured value of the LoggingDuration IE.
The IE LogMeasResultListBT covers measured results for Bluetooth.
-- ASN1START -- TAG-LOGMEASRESULTLISTBT-START LogMeasResultListBT-r16 ::= SEQUENCE (SIZE (1..maxBT-IdReport-r16)) OF LogMeasResultBT-r16 LogMeasResultBT-r16 ::= SEQUENCE { bt-Addr-r16 BIT STRING (SIZE (48)), rssi-BT-r16 INTEGER (-128..127) OPTIONAL, ... } -- TAG-LOGMEASRESULTLISTBT-STOP -- ASN1STOP
The IE LogMeasResultListWLAN covers measured results for WLAN.
-- ASN1START -- TAG-LOGMEASRESULTLISTWLAN-START LogMeasResultListWLAN-r16 ::= SEQUENCE (SIZE (1..maxWLAN-Id-Report-r16)) OF LogMeasResultWLAN-r16 LogMeasResultWLAN-r16 ::= SEQUENCE { wlan-Identifiers-r16 WLAN-Identifiers-r16,rssiWLAN-r16Measured WLAN RSSI result in dBm.The IE WLAN-RSSI-Range specifies the value range used in WLAN RSSI measurements and thresholds. Integer value for WLAN RSSI measurements is according to mapping table in TS 36.133 [40]. Value 0 corresponds to –infinity, value 1 to -100dBm, value 2 to -99dBm, and so on (i.e. in steps of 1dBm) until value 140, which corresponds to 39dBm, while value 141 corresponds to +infinity.WLAN-RSSI-Range-r16 OPTIONAL,rtt-WLAN-r16This field provides the measured roundtrip time between the target device and WLAN AP and optionally the accuracy expressed as the standard deviation of the delay. Units for each of these are 1000ns, 100ns, 10ns, 1ns, and 0.1ns as defined in TS 37.355 [49].WLAN-RTT-r16 OPTIONAL, ... } WLAN-Identifiers-r16 ::= SEQUENCE { ssid-r16 OCTET STRING (SIZE (1..32)) OPTIONAL, bssid-r16 OCTET STRING (SIZE (6)) OPTIONAL, hessid-r16 OCTET STRING (SIZE (6)) OPTIONAL, ... } WLAN-RSSI-Range-r16 ::= INTEGER(0..141) WLAN-RTT-r16 ::= SEQUENCE {rttValue-r16This field specifies the Round Trip Time (RTT) measurement between the target device and WLAN AP in units given by the field rttUnits as defined in TS 37.355 [49].INTEGER (0..16777215),rttUnits-r16This field specifies the Units for the fields rttValue and rttAccuracy. The available Units are 1000ns, 100ns, 10ns, 1ns, and 0.1ns as defined in TS 37.355 [49].ENUMERATED { microseconds, hundredsofnanoseconds, tensofnanoseconds, nanoseconds, tenthsofnanoseconds, ...},rttAccuracy-r16This field provides the estimated accuracy of the provided rttValue expressed as the standard deviation in units given by the field rttUnits as defined in TS 37.355 [49].INTEGER (0..255) OPTIONAL, ... } -- TAG-LOGMEASRESULTLISTWLAN-STOP -- ASN1STOP
IAB-IP-Address field descriptions |
---|
iPv4-Address This field is used to provide the allocated IPv4 address. |
iPv6-Address This field is used to provide the allocated IPv6 address. |
iPv6-Prefix This field is used to provide the allocated IPv6 prefix. |
LogMeasResultListBTfield descriptions |
---|
bt-Addr This field indicates the Bluetooth public address of the Bluetooth beacon as defined in TS 37.355 [49]. |
rssi-BT This field provides the beacon received signal strength indicator (RSSI) in dBm as defined in TS 37.355 [49]. |
LogMeasResultListWLANfield descriptions |
---|
Bssid Basic Service Set Identifier (BSSID) defined in IEEE 802.11-2012 [50]. |
Hessid Homogenous Extended Service Set Identifier (HESSID) defined in IEEE 802.11-2012 [50]. |
rssiWLAN Measured WLAN RSSI result in dBm.The IE WLAN-RSSI-Range specifies the value range used in WLAN RSSI measurements and thresholds. Integer value for WLAN RSSI measurements is according to mapping table in TS 36.133 [40]. Value 0 corresponds to –infinity, value 1 to -100dBm, value 2 to -99dBm, and so on (i.e. in steps of 1dBm) until value 140, which corresponds to 39dBm, while value 141 corresponds to +infinity. |
rtt-WLAN This field provides the measured roundtrip time between the target device and WLAN AP and optionally the accuracy expressed as the standard deviation of the delay. Units for each of these are 1000ns, 100ns, 10ns, 1ns, and 0.1ns as defined in TS 37.355 [49]. |
rttValue This field specifies the Round Trip Time (RTT) measurement between the target device and WLAN AP in units given by the field rttUnits as defined in TS 37.355 [49]. |
rttUnits This field specifies the Units for the fields rttValue and rttAccuracy. The available Units are 1000ns, 100ns, 10ns, 1ns, and 0.1ns as defined in TS 37.355 [49]. |
rttAccuracy This field provides the estimated accuracy of the provided rttValue expressed as the standard deviation in units given by the field rttUnits as defined in TS 37.355 [49]. |
Ssid Service Set Identifier (SSID) defined in IEEE 802.11-2012 [50]. |
Wlan-Identifiers Indicates the WLAN parameters used for identification of the WLAN for which the measurement results are applicable. |
The IE OtherConfig contains configuration related to miscellaneous other configurations.
-- ASN1START -- TAG-OTHERCONFIG-START OtherConfig ::= SEQUENCE { delayBudgetReportingConfig CHOICE{ release NULL, setup SEQUENCE{delayBudgetReportingProhibitTimerProhibit timer for delay budget reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot4 means prohibit timer is set to 0.4 seconds, and so on.ENUMERATED {s0, s0dot4, s0dot8, s1dot6, s3, s6, s12, s30} } } OPTIONAL -- Need M } OtherConfig-v1540 ::= SEQUENCE {overheatingAssistanceConfigConfiguration for the UE to report assistance information to inform the gNB about UE detected internal overheating.SetupRelease {OverheatingAssistanceConfig} OPTIONAL, -- Need M ... } OtherConfig-v1610 ::= SEQUENCE {idc-AssistanceConfig-r16Configuration for the UE to report assistance information to inform the gNB about UE detected IDC problem.SetupRelease {IDC-AssistanceConfig-r16} OPTIONAL, -- Need Mdrx-PreferenceConfig-r16Configuration for the UE to report assistance information to inform the gNB about the UE's DRX preferences for power saving.SetupRelease {DRX-PreferenceConfig-r16} OPTIONAL, -- Need MmaxBW-PreferenceConfig-r16Configuration for the UE to report assistance information to inform the gNB about the UE's preferred bandwidth for power saving.SetupRelease {MaxBW-PreferenceConfig-r16} OPTIONAL, -- Need MmaxCC-PreferenceConfig-r16Configuration for the UE to report assistance information to inform the gNB about the UE's preferred number of carriers for power saving.SetupRelease {MaxCC-PreferenceConfig-r16} OPTIONAL, -- Need MmaxMIMO-LayerPreferenceConfig-r16Configuration for the UE to report assistance information to inform the gNB about the UE's preferred number of MIMO layers for power saving.SetupRelease {MaxMIMO-LayerPreferenceConfig-r16} OPTIONAL, -- Need MminSchedulingOffsetPreferenceConfig-r16Configuration for the UE to report assistance information to inform the gNB about the UE's preferred minimumSchedulingOffset value for cross-slot scheduling for power saving.SetupRelease {MinSchedulingOffsetPreferenceConfig-r16} OPTIONAL, -- Need MreleasePreferenceConfig-r16Configuration for the UE to report assistance information to inform the gNB about the UE's preference to leave RRC_CONNECTED state.SetupRelease {ReleasePreferenceConfig-r16} OPTIONAL, -- Need MreferenceTimePreferenceReporting-r16If present, the field indicates the UE is configured to provide reference time assistance information.ENUMERATED {true} OPTIONAL, -- Need RbtNameList-r16Configuration for the UE to report measurements from specific Bluetooth beacons. NG-RAN configures the field if includeBT-Meas is configured for one or more measurements.SetupRelease {BT-NameList-r16} OPTIONAL, -- Need MwlanNameList-r16Configuration for the UE to report measurements from specific WLAN APs. NG-RAN configures the field if includeWLAN-Meas is configured for one or more measurements.SetupRelease {WLAN-NameList-r16} OPTIONAL, -- Need MsensorNameList-r16Configuration for the UE to report measurements from specific sensors.NG-RAN configures the field if includeSensor-Meas is configured for one or more measurements.SetupRelease {Sensor-NameList-r16} OPTIONAL, -- Need MobtainCommonLocation-r16Requests the UE to attempt to have detailed location information available using GNSS. NR configures the field if includeCommonLocationInfo is configured for one or more measurements.ENUMERATED {true} OPTIONAL, -- Need Rsl-AssistanceConfigNR-r16Indicate whether UE is configured to provide configured grant assistance information for NR sidelink communication.ENUMERATED{true} OPTIONAL -- Need R } CandidateServingFreqListNR-r16 ::= SEQUENCE (SIZE (1..maxFreqIDC-r16)) OF ARFCN-ValueNR OverheatingAssistanceConfig ::= SEQUENCE {overheatingIndicationProhibitTimerProhibit timer for overheating assistance information reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on.ENUMERATED {s0, s0dot5, s1, s2, s5, s10, s20, s30, s60, s90, s120, s300, s600, spare3, spare2, spare1} } IDC-AssistanceConfig-r16 ::= SEQUENCE {candidateServingFreqListNR-r16Indicates for each candidate NR serving cells, the center frequency around which UE is requested to report IDC issues.CandidateServingFreqListNR-r16 OPTIONAL, -- Need R ... } DRX-PreferenceConfig-r16 ::= SEQUENCE {drx-PreferenceProhibitTimer-r16Prohibit timer for DRX preferences assistance information reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on.ENUMERATED { s0, s0dot5, s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s20, s30, spare2, spare1} } MaxBW-PreferenceConfig-r16 ::= SEQUENCE {maxBW-PreferenceProhibitTimer-r16Prohibit timer for preferred bandwidth assistance information reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on.ENUMERATED { s0, s0dot5, s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s20, s30, spare2, spare1} } MaxCC-PreferenceConfig-r16 ::= SEQUENCE {maxCC-PreferenceProhibitTimer-r16Prohibit timer for preferred number of carriers assistance information reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on.ENUMERATED { s0, s0dot5, s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s20, s30, spare2, spare1} } MaxMIMO-LayerPreferenceConfig-r16 ::= SEQUENCE {maxMIMO-LayerPreferenceProhibitTimer-r16Prohibit timer for preferred number of number of MIMO layers assistance information reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on.ENUMERATED { s0, s0dot5, s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s20, s30, spare2, spare1} } MinSchedulingOffsetPreferenceConfig-r16 ::= SEQUENCE {minSchedulingOffsetPreferenceProhibitTimer-r16Prohibit timer for preferred minimumSchedulingOffset assistance information reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on.ENUMERATED { s0, s0dot5, s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s20, s30, spare2, spare1} } ReleasePreferenceConfig-r16 ::= SEQUENCE {releasePreferenceProhibitTimer-r16Prohibit timer for release preference assistance information reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on. Value infinity means that once a UE has reported a release preference, the UE cannot report a release preference again during the RRC connection.ENUMERATED { s0, s0dot5, s1, s2, s3, s4, s5, s6, s7, s8, s9, s10, s20, s30, infinity, spare1},connectedReportingIndicates that the UE can report a preference to remain in RRC_CONNECTED state following a report to leave RRC_CONNECTED state. If absent, the UE cannot report a preference to stay in RRC_CONNECTED state.ENUMERATED {true} OPTIONAL -- Need R } -- TAG-OTHERCONFIG-STOP -- ASN1STOP
OtherConfig field descriptions |
---|
btNameList Configuration for the UE to report measurements from specific Bluetooth beacons. NG-RAN configures the field if includeBT-Meas is configured for one or more measurements. |
candidateServingFreqListNR Indicates for each candidate NR serving cells, the center frequency around which UE is requested to report IDC issues. |
connectedReporting Indicates that the UE can report a preference to remain in RRC_CONNECTED state following a report to leave RRC_CONNECTED state. If absent, the UE cannot report a preference to stay in RRC_CONNECTED state. |
delayBudgetReportingProhibitTimer Prohibit timer for delay budget reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot4 means prohibit timer is set to 0.4 seconds, and so on. |
drx-PreferenceConfig Configuration for the UE to report assistance information to inform the gNB about the UE's DRX preferences for power saving. |
drx-PreferenceProhibitTimer Prohibit timer for DRX preferences assistance information reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on. |
idc-AssistanceConfig Configuration for the UE to report assistance information to inform the gNB about UE detected IDC problem. |
maxBW-PreferenceConfig Configuration for the UE to report assistance information to inform the gNB about the UE's preferred bandwidth for power saving. |
maxBW-PreferenceProhibitTimer Prohibit timer for preferred bandwidth assistance information reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on. |
maxCC-PreferenceConfig Configuration for the UE to report assistance information to inform the gNB about the UE's preferred number of carriers for power saving. |
maxCC-PreferenceProhibitTimer Prohibit timer for preferred number of carriers assistance information reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on. |
maxMIMO-LayerPreferenceConfig Configuration for the UE to report assistance information to inform the gNB about the UE's preferred number of MIMO layers for power saving. |
maxMIMO-LayerPreferenceProhibitTimer Prohibit timer for preferred number of number of MIMO layers assistance information reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on. |
minSchedulingOffsetPreferenceConfig Configuration for the UE to report assistance information to inform the gNB about the UE's preferred minimumSchedulingOffset value for cross-slot scheduling for power saving. |
minSchedulingOffsetPreferenceProhibitTimer Prohibit timer for preferred minimumSchedulingOffset assistance information reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on. |
obtainCommonLocation Requests the UE to attempt to have detailed location information available using GNSS. NR configures the field if includeCommonLocationInfo is configured for one or more measurements. |
overheatingAssistanceConfig Configuration for the UE to report assistance information to inform the gNB about UE detected internal overheating. |
overheatingIndicationProhibitTimer Prohibit timer for overheating assistance information reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on. |
referenceTimePreferenceReporting If present, the field indicates the UE is configured to provide reference time assistance information. |
releasePreferenceConfig Configuration for the UE to report assistance information to inform the gNB about the UE's preference to leave RRC_CONNECTED state. |
releasePreferenceProhibitTimer Prohibit timer for release preference assistance information reporting. Value in seconds. Value s0 means prohibit timer is set to 0 seconds, value s0dot5 means prohibit timer is set to 0.5 seconds, value s1 means prohibit timer is set to 1 second and so on. Value infinity means that once a UE has reported a release preference, the UE cannot report a release preference again during the RRC connection. |
sensorNameList Configuration for the UE to report measurements from specific sensors.NG-RAN configures the field if includeSensor-Meas is configured for one or more measurements. |
sl-AssistanceConfigNR Indicate whether UE is configured to provide configured grant assistance information for NR sidelink communication. |
wlanNameList Configuration for the UE to report measurements from specific WLAN APs. NG-RAN configures the field if includeWLAN-Meas is configured for one or more measurements. |
The IE PhysCellIdUTRA-FDD is used to indicate the physical layer identity of the cell, i.e. the primary scrambling code, as defined in TS 25.331 [45].
The IE RRC-TransactionIdentifier is used, together with the message type, for the identification of an RRC procedure (transaction).
The IE Sensor-NameList is used to indicate the names of the sensors which the UE is configured to measure.
-- ASN1START -- TAG-SENSORNAMELIST-START Sensor-NameList-r16 ::= SEQUENCE {measUncomBarPre-r16If configured, the UE reports the uncompensated Barometeric pressure measurement as defined in TS 37.355 [49].ENUMERATED {true} OPTIONAL, -- Need RmeasUeSpeedIf configured, the UE reports the UE speed measurement as defined in TS 37.355 [49].ENUMERATED {true} OPTIONAL, -- Need RmeasUeOrientationIf configured, the UE reports the UE orientation information as defined in TS 37.355 [49].ENUMERATED {true} OPTIONAL -- Need R } -- TAG-SENSORNAMELIST-STOP -- ASN1STOP
Sensor-NameList field descriptions |
---|
measUncomBarPre If configured, the UE reports the uncompensated Barometeric pressure measurement as defined in TS 37.355 [49]. |
measUeSpeed If configured, the UE reports the UE speed measurement as defined in TS 37.355 [49]. |
measUeOrientation If configured, the UE reports the UE orientation information as defined in TS 37.355 [49]. |
The TraceReference contains parameter Trace Reference as defined in TS 32.422 [52].
-- ASN1START -- TAG-TRACEREFERENCE-START TraceReference-r16 ::= SEQUENCE { plmn-Identity-r16 PLMN-Identity, traceId-r16 OCTET STRING (SIZE (3)) } -- TAG-TRACEREFERENCE-STOP -- ASN1STOP
The IE UE-MeasurementsAvailable is used to indicate all relevant available indicators for UE measurements.
-- ASN1START -- TAG-UE-MeasurementsAvailable-START UE-MeasurementsAvailable-r16 ::= SEQUENCE { logMeasAvailable-r16 ENUMERATED {true} OPTIONAL, logMeasAvailableBT-r16 ENUMERATED {true} OPTIONAL, logMeasAvailableWLAN-r16 ENUMERATED {true} OPTIONAL, connEstFailInfoAvailable-r16 ENUMERATED {true} OPTIONAL, rlf-InfoAvailable-r16 ENUMERATED {true} OPTIONAL, ... } -- TAG-UE-MeasurementsAvailable-STOP -- ASN1STOP
The IE UTRA-FDD-Q-OffsetRange is used to indicate a frequency specific offset to be applied when evaluating triggering conditions for measurement reporting. The value is in dB. Value dB-24 corresponds to -24 dB, value dB-22 corresponds to -22 dB and so on.
-- ASN1START -- TAG-UTRA-FDD-Q-OFFSETRANGE-START UTRA-FDD-Q-OffsetRange-r16 ::= ENUMERATED { dB-24, dB-22, dB-20, dB-18, dB-16, dB-14, dB-12, dB-10, dB-8, dB-6, dB-5, dB-4, dB-3, dB-2, dB-1, dB0, dB1, dB2, dB3, dB4, dB5, dB6, dB8, dB10, dB12, dB14, dB16, dB18, dB20, dB22, dB24} -- TAG-UTRA-FDD-Q-OFFSETRANGE-STOP -- ASN1STOP
The IE VisitedCellInfoList includes the mobility history information of maximum of 16 most recently visited cells or time spent in any cell selection state and/or camped on any cell state in NR or E-UTRA. The most recently visited cell is stored first in the list. The list includes cells visited in RRC_IDLE, RRC_INACTIVE and RRC_CONNECTED states for NR and RRC_IDLE and RRC_CONNECTED for E-UTRA.
-- ASN1START -- TAG-VISITEDCELLINFOLIST-START VisitedCellInfoList-r16 ::= SEQUENCE (SIZE (1..maxCellHistory-r16)) OF VisitedCellInfo-r16 VisitedCellInfo-r16 ::= SEQUENCE { visitedCellId-r16 CHOICE { nr-CellId-r16 CHOICE { cgi-Info CGI-Info-Logging-r16, pci-arfcn-r16 PCI-ARFCN-NR-r16 }, eutra-CellId-r16 CHOICE { cellGlobalId-r16 CGI-InfoEUTRA, pci-arfcn-r16 PCI-ARFCN-EUTRA-r16 } } OPTIONAL, timeSpent-r16 INTEGER (0..4095), ... } -- TAG-VISITEDCELLINFOLIST-STOP -- ASN1STOP
The IE WLAN-NameList is used to indicate the names of the WLAN AP for which the UE is configured to measure.
-- ASN1START -- TAG-WLANNAMELIST-START WLAN-NameList-r16 ::= SEQUENCE (SIZE (1..maxWLAN-Name-r16)) OF WLAN-Name-r16 WLAN-Name-r16 ::= OCTET STRING (SIZE (1..32)) -- ASN1STOP -- TAG-WLANNAMELIST-STOP
VisitedCellInfoListfield descriptions |
---|
timeSpent This field indicates the duration of stay in the cell or in any cell selection state and/or camped on any cell state in NR or E-UTRA approximated to the closest second. If the duration of stay exceeds 4095s, the UE shall set it to 4095s. |
visitedCellId This field indicates the visited cell id including NR and E-UTRA cells. |
WLAN-NameListfield descriptions |
---|
WLAN-Name If configured, the UE only performs WLAN measurements according to the names identified. For each name, it refers to Service Set Identifier (SSID) defined in IEEE 802.11-2012 [50]. |
The IE SL-BWP-Config is used to configure the UE specific NR sidelink communication on one particular sidelink bandwidth part.
-- ASN1START -- TAG-SL-BWP-CONFIG-START SL-BWP-Config-r16 ::= SEQUENCE {sl-BWP-IdAn identifier for this sidelink bandwidth part.BWP-Id,sl-BWP-Generic-r16This field indicates the generic parameters on the configured sidelink BWP.SL-BWP-Generic-r16 OPTIONAL, -- Need Msl-BWP-PoolConfig-r16This field indicates the resource pool configurations on the configured sidelink BWP.SL-BWP-PoolConfig-r16 OPTIONAL, -- Need M ... } SL-BWP-Generic-r16 ::= SEQUENCE { sl-BWP-r16 BWP OPTIONAL, -- Need Msl-LengthSymbols-r16This field indicates the number of symbols used for sidelink in a slot without S-SSB. A single value can be (pre)configured per sidelink bandwidth part.ENUMERATED {sym7, sym8, sym9, sym10, sym11, sym12, sym13, sym14} OPTIONAL, -- Need Msl-StartSymbol-r16This field indicates the starting symbol used for sidelink in a slot without S-SSB. A single value can be (pre)configured per sidelink bandwidth part.ENUMERATED {sym0, sym1, sym2, sym3, sym4, sym5, sym6, sym7} OPTIONAL, -- Need M sl-PSBCH-Config-r16 SetupRelease {SL-PSBCH-Config-r16} OPTIONAL, -- Need Msl-TxDirectCurrentLocation-r16The sidelink Tx/Rx Direct Current location for the carrier. Only values in the value range of this field between 0 and 3299, which indicate the subcarrier index within the carrier corresponding to the numerology of the corresponding sidelink BWP and value 3300, which indicates "Outside the carrier" and value 3301, which indicates "Undetermined position within the carrier" are used in this version of the specification.INTEGER (0..3301) OPTIONAL, -- Need M ... } -- TAG-SL-BWP-CONFIG-STOP -- ASN1STOP
SL-BWP-Config field descriptions |
---|
sl-BWP-Generic This field indicates the generic parameters on the configured sidelink BWP. |
sl-BWP-PoolConfig This field indicates the resource pool configurations on the configured sidelink BWP. |
sl-BWP-Id An identifier for this sidelink bandwidth part. |
SL-BWP-Generic field descriptions |
---|
sl-LengthSymbols This field indicates the number of symbols used for sidelink in a slot without S-SSB. A single value can be (pre)configured per sidelink bandwidth part. |
sl-StartSymbol This field indicates the starting symbol used for sidelink in a slot without S-SSB. A single value can be (pre)configured per sidelink bandwidth part. |
sl-TxDirectCurrentLocation The sidelink Tx/Rx Direct Current location for the carrier. Only values in the value range of this field between 0 and 3299, which indicate the subcarrier index within the carrier corresponding to the numerology of the corresponding sidelink BWP and value 3300, which indicates "Outside the carrier" and value 3301, which indicates "Undetermined position within the carrier" are used in this version of the specification. |
The IE SL-BWP-ConfigCommon is used to configure the cell-specific configuration information on one particular sidelink bandwidth part.
-- ASN1START -- TAG-SL-BWP-CONFIGCOMMON-START SL-BWP-ConfigCommon-r16 ::= SEQUENCE { sl-BWP-Generic-r16 SL-BWP-Generic-r16 OPTIONAL, -- Need R sl-BWP-PoolConfigCommon-r16 SL-BWP-PoolConfigCommon-r16 OPTIONAL, -- Need R ... } -- TAG-SL-BWP-CONFIGCOMMON-STOP -- ASN1STOP
The IE SL-BWP-PoolConfig is used to configure NR sidelink communication resource pool.
-- ASN1START -- TAG-SL-BWP-POOLCONFIG-START SL-BWP-PoolConfig-r16 ::= SEQUENCE { sl-RxPool-r16 SEQUENCE (SIZE (1..maxNrofRXPool-r16)) OF SL-ResourcePool-r16 OPTIONAL, -- Cond HO sl-TxPoolSelectedNormal-r16 SL-TxPoolDedicated-r16 OPTIONAL, -- Need M sl-TxPoolScheduling-r16 SL-TxPoolDedicated-r16 OPTIONAL, -- Need N sl-TxPoolExceptional-r16 SL-ResourcePoolConfig-r16 OPTIONAL -- Need M } SL-TxPoolDedicated-r16 ::= SEQUENCE { sl-PoolToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofTXPool-r16)) OF SL-ResourcePoolID-r16 OPTIONAL, -- Need N sl-PoolToAddModList-r16 SEQUENCE (SIZE (1..maxNrofTXPool-r16)) OF SL-ResourcePoolConfig-r16 OPTIONAL -- Need N } SL-ResourcePoolConfig-r16 ::= SEQUENCE { sl-ResourcePoolID-r16 SL-ResourcePoolID-r16, sl-ResourcePool-r16 SL-ResourcePool-r16 OPTIONAL -- Need M } SL-ResourcePoolID-r16 ::= INTEGER (1..maxNrofPoolID-r16) -- TAG-SL-BWP-POOLCONFIG-STOP -- ASN1STOP
SL-BWP-ConfigCommon field descriptions |
---|
sl-BWP-Generic This field indicates the generic parameters on the configured sidelink BWP. |
sl-BWP-PoolConfigCommon This field indicates the resource pool configurations on the configured sidelink BWP. |
The IE SL-BWP-PoolConfigCommon is used to configure the cell-specific NR sidelink communication resource pool.
-- ASN1START -- TAG-SL-BWP-POOLCONFIGCOMMON-START SL-BWP-PoolConfigCommon-r16 ::= SEQUENCE { sl-RxPool-r16 SEQUENCE (SIZE (1..maxNrofRXPool-r16)) OF SL-ResourcePool-r16 OPTIONAL, -- Need R sl-TxPoolSelectedNormal-r16 SEQUENCE (SIZE (1..maxNrofTXPool-r16)) OF SL-ResourcePoolConfig-r16 OPTIONAL, -- Need R sl-TxPoolExceptional-r16 SL-ResourcePoolConfig-r16 OPTIONAL -- Need R } -- TAG-SL-BWP-POOLCONFIGCOMMON-STOP -- ASN1STOP
The IE SL-CBR-PriorityTxConfigList indicates the mapping between PSSCH transmission parameter (such as MCS,PRB number, retransmission number, CR limit) sets by using the indexes of the configurations provided in sl-CBR-PSSCH-TxConfigList, CBR ranges by an index to the entry of the CBR range configuration in sl-CBR-RangeConfigList, and priority ranges. It also indicates the default PSSCH transmission parameters to be used when CBR measurement results are not available, and MCS range for the MCS tables used in the resource pool.
-- ASN1START -- TAG-SL-CBR-PRIORITYTXCONFIGLIST-START SL-CBR-PriorityTxConfigList-r16 ::= SEQUENCE (SIZE (1..8)) OF SL-PriorityTxConfigIndex-r16 SL-CBR-PriorityTxConfigList-v1650 ::= SEQUENCE (SIZE (1..8)) OF SL-PriorityTxConfigIndex-v1650 SL-PriorityTxConfigIndex-r16 ::= SEQUENCE {sl-PriorityThreshold-r16Indicates the upper bound of priority range which is associated with the configurations in sl-CBR-ConfigIndex and in sl-Tx-ConfigIndexList. The upper bounds of the priority ranges are configured in ascending order for consecutive entries of SL-PriorityTxConfigIndex in SL-CBR-PriorityTxConfigList. For the first entry of SL-PriorityTxConfigIndex, the lower bound of the priority range is 1.INTEGER (1..8) OPTIONAL, -- Need Msl-DefaultTxConfigIndex-r16Indicates the PSSCH transmission parameters to be used by the UEs which do not have available CBR measurement results, by means of an index to the corresponding entry insl-Tx-ConfigIndexList. Value 0 indicates the first entry in sl-Tx-ConfigIndexList. The field is ignored if the UE has available CBR measurement results.INTEGER (0..maxCBR-Level-1-r16) OPTIONAL, -- Need Msl-CBR-ConfigIndex-r16Indicates the CBR ranges to be used by an index to the entry of the CBR range configuration in sl-CBR-RangeConfigList.INTEGER (0..maxCBR-Config-1-r16) OPTIONAL, -- Need M sl-Tx-ConfigIndexList-r16 SEQUENCE (SIZE (1.. maxCBR-Level-r16)) OF SL-TxConfigIndex-r16 OPTIONAL -- Need M } SL-PriorityTxConfigIndex-v1650 ::= SEQUENCE {sl-MCS-RangeList-r16Indicates the minimum MCS value and maximum MCS value for the associated MCS table(s).UE shall ignore the minimum MCS value and maximum MCS value used for table of 64QAM indicated inSL-CBR-PriorityTxConfigList-r16 if SL-CBR-PriorityTxConfigList-v1650 is present.SEQUENCE (SIZE (1..maxCBR-Level-r16)) OF SL-MinMaxMCS-List-r16 OPTIONAL -- Need M } SL-TxConfigIndex-r16 ::= INTEGER (0..maxTxConfig-1-r16) -- TAG-SL-CBR-PRIORITYTXCONFIGLIST-STOP -- ASN1STOP
SL-BWP-PoolConfig field descriptions |
---|
sl-RxPool Indicates the receiving resource pool on the configured BWP. For the PSFCH related configuration, if configured, will be used for PSFCH transmission/reception.If the field is included, it replaces any previous list, i.e. all the entries of the list are replaced and each of the SL-ResourcePool entries is considered to be newly created. |
sl-TxPoolExceptional Indicates the resources by which the UE is allowed to transmit NR sidelink communication in exceptional conditions on the configured BWP. For the PSFCH related configuration, if configured, will be used for PSFCH transmission/reception. |
sl-TxPoolScheduling Indicates the resources by which the UE is allowed to transmit NR sidelink communication based on network scheduling on the configured BWP. For the PSFCH related configuration, if configured, will be used for PSFCH transmission/reception. |
sl-TxPoolSelectedNormal Indicates the resources by which the UE is allowed to transmit NR sidelink communication by UE autonomous resource selection on the configured BWP. For the PSFCH related configuration, if configured, will be used for PSFCH transmission/reception. |
Conditional Presence | Explanation |
---|---|
HO | This field is optionally present, need M, in an RRCReconfiguration message including reconfigurationWithSync; otherwise it is absent, Need M. |
SL-BWP-PoolConfigCommon field descriptions |
---|
sl-TxPoolExceptional Indicates the resources by which the UE is allowed to transmit NR sidelink communication in exceptional conditions on the configured BWP. For the PSFCH related configuration, if configured, will be used for PSFCH transmission/reception. This field is not present when SL-BWP-PoolConfigCommon is included in SidelinkPreconfigNR. |
SL-CBR-PriorityTxConfigList field descriptions |
---|
sl-CBR-ConfigIndex Indicates the CBR ranges to be used by an index to the entry of the CBR range configuration in sl-CBR-RangeConfigList. |
sl-DefaultTxConfigIndex Indicates the PSSCH transmission parameters to be used by the UEs which do not have available CBR measurement results, by means of an index to the corresponding entry insl-Tx-ConfigIndexList. Value 0 indicates the first entry in sl-Tx-ConfigIndexList. The field is ignored if the UE has available CBR measurement results. |
sl-MCS-RangeList Indicates the minimum MCS value and maximum MCS value for the associated MCS table(s).UE shall ignore the minimum MCS value and maximum MCS value used for table of 64QAM indicated inSL-CBR-PriorityTxConfigList-r16 if SL-CBR-PriorityTxConfigList-v1650 is present. |
sl-PriorityThreshold Indicates the upper bound of priority range which is associated with the configurations in sl-CBR-ConfigIndex and in sl-Tx-ConfigIndexList. The upper bounds of the priority ranges are configured in ascending order for consecutive entries of SL-PriorityTxConfigIndex in SL-CBR-PriorityTxConfigList. For the first entry of SL-PriorityTxConfigIndex, the lower bound of the priority range is 1. |
SL-CBR-PriorityTxConfigList-v1650 If included, it includes the same number of entries, and listed in the same order, as in SL-CBR-PriorityTxConfigList-r16. |
The IE SL-CBR-CommonTxConfigList indicates the list of PSSCH transmission parameters (such as MCS,sub-channel number, retransmission number, CR limit) in sl-CBR-PSSCH-TxConfigList, and the list of CBR ranges in sl-CBR-RangeConfigList, to configure congestion control to the UE for sidelink communication.
-- ASN1START -- TAG-SL-CBR-COMMONTXCONFIGLIST-START SL-CBR-CommonTxConfigList-r16 ::= SEQUENCE {sl-CBR-RangeConfigList-r16Indicates the list of CBR ranges. Each entry of the list indicates in SL-CBR-LevelsConfig the upper bound of the CBR range for the respective entry. The upper bounds of the CBR ranges are configured in ascending order for consecutive entries of sl-CBR-RangeConfigList. For the first entry of sl-CBR-RangeConfigList the lower bound of the CBR range is 0. Value 0 corresponds to 0, value 1 to 0.01, value 2 to 0.02, and so on.SEQUENCE (SIZE (1..maxCBR-Config-r16)) OF SL-CBR-LevelsConfig-r16 OPTIONAL, -- Need Msl-CBR-PSSCH-TxConfigList-r16Indicates the list of available PSSCH transmission parameters (such as MCS, sub-channel number, retransmission number and CR limit) configurations.SEQUENCE (SIZE (1.. maxTxConfig-r16)) OF SL-CBR-PSSCH-TxConfig-r16 OPTIONAL -- Need M } SL-CBR-LevelsConfig-r16 ::= SEQUENCE (SIZE (1..maxCBR-Level-r16)) OF SL-CBR-r16 SL-CBR-PSSCH-TxConfig-r16 ::= SEQUENCE {sl-CR-Limit-r16Indicates the maximum limit on the occupancy ratio. Value 0 corresponds to 0, value 1 to 0.0001, value 2 to 0.0002, and so on (i.e. in steps of 0.0001) until value 10000, which corresponds to 1.INTEGER(0..10000) OPTIONAL, -- Need Msl-TxParameters-r16Indicates PSSCH transmission parameters.SL-PSSCH-TxParameters-r16 OPTIONAL -- Need M } SL-CBR-r16 ::= INTEGER (0..100) -- TAG-SL-CBR-COMMONTXCONFIGLIST-STOP -- ASN1STOP
SL-CBR-CommonTxConfigList field descriptions |
---|
sl-CBR-RangeConfigList Indicates the list of CBR ranges. Each entry of the list indicates in SL-CBR-LevelsConfig the upper bound of the CBR range for the respective entry. The upper bounds of the CBR ranges are configured in ascending order for consecutive entries of sl-CBR-RangeConfigList. For the first entry of sl-CBR-RangeConfigList the lower bound of the CBR range is 0. Value 0 corresponds to 0, value 1 to 0.01, value 2 to 0.02, and so on. |
sl-CR-Limit Indicates the maximum limit on the occupancy ratio. Value 0 corresponds to 0, value 1 to 0.0001, value 2 to 0.0002, and so on (i.e. in steps of 0.0001) until value 10000, which corresponds to 1. |
sl-CBR-PSSCH-TxConfigList Indicates the list of available PSSCH transmission parameters (such as MCS, sub-channel number, retransmission number and CR limit) configurations. |
sl-TxParameters Indicates PSSCH transmission parameters. |
The IE SL-ConfigDedicatedNR specifies the dedicated configuration information for NR sidelink communication.
-- ASN1START -- TAG-SL-CONFIGDEDICATEDNR-START SL-ConfigDedicatedNR-r16 ::= SEQUENCE {sl-PHY-MAC-RLC-Config-r16This field indicates the lower layer sidelink radio bearer configurations.SL-PHY-MAC-RLC-Config-r16 OPTIONAL, -- Need Msl-RadioBearerToReleaseList-r16This field indicates one or multiple sidelink radio bearer configurations to remove.SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SLRB-Uu-ConfigIndex-r16 OPTIONAL, -- Need Nsl-RadioBearerToAddModList-r16This field indicates one or multiple sidelink radio bearer configurationsto add and/or modify.SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SL-RadioBearerConfig-r16 OPTIONAL, -- Need Nsl-MeasConfigInfoToReleaseList-r16This field indicates the RSRP measurement configurations for unicast destinations to remove.SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-DestinationIndex-r16 OPTIONAL, -- Need Nsl-MeasConfigInfoToAddModList-r16This field indicates the RSRP measurement configurations for unicast destinations to add and/or modify.SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-MeasConfigInfo-r16 OPTIONAL, -- Need N t400-r16 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000} OPTIONAL, -- Need M ... } SL-DestinationIndex-r16 ::= INTEGER (0..maxNrofSL-Dest-1-r16) SL-PHY-MAC-RLC-Config-r16::= SEQUENCE {sl-ScheduledConfig-r16Indicates the configuration for UE to transmit NR sidelink communication based on network scheduling.This field is not configured simultaneously with sl-UE-SelectedConfig.SetupRelease { SL-ScheduledConfig-r16 } OPTIONAL, -- Need Msl-UE-SelectedConfig-r16Indicates the configuration used for UE autonomous resource selection. This field is not configured simultaneously with sl-ScheduledConfig.SetupRelease { SL-UE-SelectedConfig-r16 } OPTIONAL, -- Need Msl-FreqInfoToReleaseList-r16This field indicates the NR sidelink communication configuration on some carrier frequency (ies) to remove. In this release, only one entry can be configured in the list.SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-Freq-Id-r16 OPTIONAL, -- Need Nsl-FreqInfoToAddModList-r16This field indicates the NR sidelink communication configuration on some carrier frequency (ies) to add and/or modify. In this release, only one entry can be configured in the list.SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-FreqConfig-r16 OPTIONAL, -- Need Nsl-RLC-BearerToReleaseList-r16This field indicates one or multiple sidelink RLC bearer configurations to remove.SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-BearerConfigIndex-r16 OPTIONAL, -- Need Nsl-RLC-BearerToAddModList-r16This field indicates one or multiple sidelink RLC bearer configurations to add and/or modify.SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-BearerConfig-r16 OPTIONAL, -- Need Nsl-MaxNumConsecutiveDTX-r16This field indicates the maximum number of consecutive HARQ DTX before triggering sidelink RLF. Value n1 corresponds to 1, value n2 corresponds to 2, and so on.ENUMERATED {n1, n2, n3, n4, n6, n8, n16, n32} OPTIONAL, -- Need Msl-CSI-Acquisition-r16Indicates whether CSI reporting is enabled in sidelink unicast. If the field is absent, sidelink CSI reporting is disabled.ENUMERATED {enabled} OPTIONAL, -- Need Rsl-CSI-SchedulingRequestId-r16If present, it indicates the scheduling request configuration applicable for sidelink CSI report MAC CE, as specified in TS 38.321 [3].SetupRelease {SchedulingRequestId} OPTIONAL, -- Need Msl-SSB-PriorityNR-r16This field indicates the priority of NR sidelink SSB transmission and reception.INTEGER (1..8) OPTIONAL, -- Need RnetworkControlledSyncTx-r16This field indicates whether the UE shall transmit synchronisation information (i.e. become synchronisation source). Value on indicates the UE to transmit synchronisation information while value off indicates the UE to not transmit such information.ENUMERATED {on, off} OPTIONAL -- Need M } -- TAG-SL-CONFIGDEDICATEDNR-STOP -- ASN1STOP
SL-ConfigDedicatedNRfield descriptions |
---|
sl-MeasConfigInfoToAddModList This field indicates the RSRP measurement configurations for unicast destinations to add and/or modify. |
sl-MeasConfigInfoToReleaseList This field indicates the RSRP measurement configurations for unicast destinations to remove. |
sl-PHY-MAC-RLC-Config This field indicates the lower layer sidelink radio bearer configurations. |
sl-RadioBearerToAddModList This field indicates one or multiple sidelink radio bearer configurationsto add and/or modify. |
sl-RadioBearerToReleaseList This field indicates one or multiple sidelink radio bearer configurations to remove. |
SL-PHY-MAC-RLC-Configfield descriptions |
---|
networkControlledSyncTx This field indicates whether the UE shall transmit synchronisation information (i.e. become synchronisation source). Value on indicates the UE to transmit synchronisation information while value off indicates the UE to not transmit such information. |
sl-MaxNumConsecutiveDTX This field indicates the maximum number of consecutive HARQ DTX before triggering sidelink RLF. Value n1 corresponds to 1, value n2 corresponds to 2, and so on. |
sl-FreqInfoToAddModList This field indicates the NR sidelink communication configuration on some carrier frequency (ies) to add and/or modify. In this release, only one entry can be configured in the list. |
sl-FreqInfoToReleaseList This field indicates the NR sidelink communication configuration on some carrier frequency (ies) to remove. In this release, only one entry can be configured in the list. |
sl-RLC-BearerToAddModList This field indicates one or multiple sidelink RLC bearer configurations to add and/or modify. |
sl-RLC-BearerToReleaseList This field indicates one or multiple sidelink RLC bearer configurations to remove. |
sl-ScheduledConfig Indicates the configuration for UE to transmit NR sidelink communication based on network scheduling.This field is not configured simultaneously with sl-UE-SelectedConfig. |
sl-UE-SelectedConfig Indicates the configuration used for UE autonomous resource selection. This field is not configured simultaneously with sl-ScheduledConfig. |
sl-CSI-Acquisition Indicates whether CSI reporting is enabled in sidelink unicast. If the field is absent, sidelink CSI reporting is disabled. |
sl-CSI-SchedulingRequestId If present, it indicates the scheduling request configuration applicable for sidelink CSI report MAC CE, as specified in TS 38.321 [3]. |
sl-SSB-PriorityNR This field indicates the priority of NR sidelink SSB transmission and reception. |
The IE SL-ConfiguredGrantConfig specifies the configured grant configuration information for NR sidelink communication.
-- ASN1START -- TAG-SL-CONFIGUREDGRANTCONFIG-START SL-ConfiguredGrantConfig-r16 ::= SEQUENCE {sl-ConfigIndexCG-r16This field indicates the ID to identify configured grant for sidelink.SL-ConfigIndexCG-r16,sl-PeriodCG-r16This field indicates the period of sidelink configured grantin the unit of ms.SL-PeriodCG-r16 OPTIONAL, -- Need Msl-NrOfHARQ-Processes-r16This field indicates the number of HARQ processes configured for a specific configured grant. It applies for both Type 1 and Type 2.INTEGER (1..16) OPTIONAL, -- Need M sl-HARQ-ProcID-offset-r16 INTEGER (0..15) OPTIONAL, -- Need Msl-CG-MaxTransNumList-r16This field indicates the maximum number of times that a TB can be transmitted using the resources provided by the configured grant. sl-Priority corresponds to the logical channel priority.SL-CG-MaxTransNumList-r16 OPTIONAL, -- Need M rrc-ConfiguredSidelinkGrant-r16 SEQUENCE {sl-TimeResourceCG-Type1-r16This field indicates the time resource location of sidelink configured grant Type 1. An index giving valid combinations of up to two slot positions (jointly encoded) as time resource indicator value (TRIV),as defined in TS 38.212 [17].INTEGER (0..496) OPTIONAL, -- Need Msl-StartSubchannelCG-Type1-r16This field indicates the starting sub-channel of sidelink configured grant Type 1. An index giving valid sub-channel index.INTEGER (0..26) OPTIONAL, -- Need Msl-FreqResourceCG-Type1-r16Indicates the frequency resource location of sidelink configured grant type 1. An index giving valid combinations of one or two starting sub-channel and length (jointly encoded) as resource indicator value (RIV), as defined in TS 38.214 [19].INTEGER (0..6929) OPTIONAL, -- Need Msl-TimeOffsetCG-Type1-r16This field indicates the slot offset with respect to logical slot defined by sl-TimeReferenceSFN-Type1, as specified in TS 38.321 [3].INTEGER (0..7999) OPTIONAL, -- Need Rsl-N1PUCCH-AN-r16This field indicates the PUCCH resource for HARQ feedback for sidelink configured grant type 1. The actual PUCCH-Resource is configured in sl-PUCCH-Config and referred to by its ID.PUCCH-ResourceId OPTIONAL, -- Need Msl-PSFCH-ToPUCCH-CG-Type1-r16This field,for configured grant type 1, indicates slot offset between the PSFCH associated with the last PSSCH resource of each period and the PUCCH occasion used for reporting sidelink HARQ.INTEGER (0..15) OPTIONAL, -- Need Msl-ResourcePoolID-r16Indicates the resource pool in which the configured sidelink grant Type 1 is applied.SL-ResourcePoolID-r16 OPTIONAL, -- Need Msl-TimeReferenceSFN-Type1-r16Indicates SFN used for determination of the offset of a resource in time domain. If it is present, the UE uses the 1st logical slot of associated resource pool after the starting time of the closest SFN with the indicated number preceding the reception of the sidelink configured grant configuration Type 1 as reference logical slot, see TS 38.321 [3], clause 5.8.3. If it is not present, the reference SFN is 0.ENUMERATED {sfn512} OPTIONAL -- Need S } OPTIONAL, -- Need M ..., [[sl-N1PUCCH-AN-Type2-r16This field indicates the PUCCH resource for HARQ feedback for PSCCH/PSSCH transmissions without a corresponding PDCCH on sidelink configured grant type 2. The actual PUCCH-Resource is configured in sl-PUCCH-Config and referred to by its ID.PUCCH-ResourceId OPTIONAL -- Need M ]] } SL-ConfigIndexCG-r16 ::= INTEGER (0..maxNrofCG-SL-1-r16) SL-CG-MaxTransNumList-r16 ::= SEQUENCE (SIZE (1..8)) OF SL-CG-MaxTransNum-r16 SL-CG-MaxTransNum-r16 ::= SEQUENCE { sl-Priority-r16 INTEGER (1..8), sl-MaxTransNum-r16 INTEGER (1..32) } SL-PeriodCG-r16 ::= CHOICE{ sl-PeriodCG1-r16 ENUMERATED {ms100, ms200, ms300, ms400, ms500, ms600, ms700, ms800, ms900, ms1000, spare6, spare5, spare4, spare3, spare2, spare1}, sl-PeriodCG2-r16 INTEGER (1..99) } -- TAG-SL-CONFIGUREDGRANTCONFIG-STOP -- ASN1STOP
SL-ConfiguredGrantConfigfield descriptions |
---|
sl-ConfigIndexCG This field indicates the ID to identify configured grant for sidelink. |
sl-CG-MaxTransNumList This field indicates the maximum number of times that a TB can be transmitted using the resources provided by the configured grant. sl-Priority corresponds to the logical channel priority. |
sl-FreqResourceCG-Type1 Indicates the frequency resource location of sidelink configured grant type 1. An index giving valid combinations of one or two starting sub-channel and length (jointly encoded) as resource indicator value (RIV), as defined in TS 38.214 [19]. |
sl-HARQ-ProcID-Offset Indicates the offset used in deriving the HARQ process ID for SL configured grant type 1 or SL configured type 2, see TS 38.321 [3], clause 5.8.3. |
sl-N1PUCCH-AN This field indicates the PUCCH resource for HARQ feedback for sidelink configured grant type 1. The actual PUCCH-Resource is configured in sl-PUCCH-Config and referred to by its ID. |
sl-N1PUCCH-AN-Type2 This field indicates the PUCCH resource for HARQ feedback for PSCCH/PSSCH transmissions without a corresponding PDCCH on sidelink configured grant type 2. The actual PUCCH-Resource is configured in sl-PUCCH-Config and referred to by its ID. |
sl-NrOfHARQ-Processes This field indicates the number of HARQ processes configured for a specific configured grant. It applies for both Type 1 and Type 2. |
sl-PeriodCG This field indicates the period of sidelink configured grantin the unit of ms. |
sl-PSFCH-ToPUCCH-CG-Type1 This field,for configured grant type 1, indicates slot offset between the PSFCH associated with the last PSSCH resource of each period and the PUCCH occasion used for reporting sidelink HARQ. |
sl-ResourcePoolID Indicates the resource pool in which the configured sidelink grant Type 1 is applied. |
sl-StartSubchannelCG-Type1 This field indicates the starting sub-channel of sidelink configured grant Type 1. An index giving valid sub-channel index. |
sl-TimeOffsetCG-Type1 This field indicates the slot offset with respect to logical slot defined by sl-TimeReferenceSFN-Type1, as specified in TS 38.321 [3]. |
sl-TimeReferenceSFN-Type1 Indicates SFN used for determination of the offset of a resource in time domain. If it is present, the UE uses the 1st logical slot of associated resource pool after the starting time of the closest SFN with the indicated number preceding the reception of the sidelink configured grant configuration Type 1 as reference logical slot, see TS 38.321 [3], clause 5.8.3. If it is not present, the reference SFN is 0. |
sl-TimeResourceCG-Type1 This field indicates the time resource location of sidelink configured grant Type 1. An index giving valid combinations of up to two slot positions (jointly encoded) as time resource indicator value (TRIV),as defined in TS 38.212 [17]. |
The IE SL-DestinationIdentity is used to identify a destination of a NR sidelink communication.
The IE SL-FreqConfig specifies the dedicated configuration information on one particular carrier frequency for NR sidelink communication.
-- ASN1START -- TAG-SL-FREQCONFIG-START SL-FreqConfig-r16 ::= SEQUENCE { sl-Freq-Id-r16 SL-Freq-Id-r16, sl-SCS-SpecificCarrierList-r16 SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier, sl-AbsoluteFrequencyPointA-r16 ARFCN-ValueNR OPTIONAL, -- Need M sl-AbsoluteFrequencySSB-r16 ARFCN-ValueNR OPTIONAL, -- Need R frequencyShift7p5khzSL-r16 ENUMERATED {true} OPTIONAL, -- Cond V2X-SL-Shared valueN-r16 INTEGER (-1..1), sl-BWP-ToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofSL-BWPs-r16)) OF BWP-Id OPTIONAL, -- Need N sl-BWP-ToAddModList-r16 SEQUENCE (SIZE (1..maxNrofSL-BWPs-r16)) OF SL-BWP-Config-r16 OPTIONAL, -- Need N sl-SyncConfigList-r16 SL-SyncConfigList-r16 OPTIONAL, -- Need M sl-SyncPriority-r16 ENUMERATED {gnss, gnbEnb} OPTIONAL -- Need M } SL-Freq-Id-r16 ::= INTEGER (1.. maxNrofFreqSL-r16) -- TAG-SL-FREQCONFIG-STOP -- ASN1STOP
The IE FreqConfigCommon specifies the cell-specific configuration information on one particular carrier frequency for NR sidelink communication.
-- ASN1START -- TAG-SL-FREQCONFIGCOMMON-START SL-FreqConfigCommon-r16 ::= SEQUENCE {sl-SCS-SpecificCarrierList-r16A set of UE specific channel bandwidth and location configurations for different subcarrier spacings (numerologies). Defined in relation to Point A. The UE uses the configuration provided in this field only for the purpose of channel bandwidth and location determination. In this release, only one SCS-SpecificCarrier is allowed to be configured for NR sidelink communication.SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier,sl-AbsoluteFrequencyPointA-r16Absolute frequency of the reference resource block (Common RB 0). Its lowest subcarrier is also known as Point A.ARFCN-ValueNR,sl-AbsoluteFrequencySSB-r16Indicates the frequency location of sidelink SSB. The transmission bandwidth for sidelink SSB is within the bandwidth of this sidelink BWP.ARFCN-ValueNR OPTIONAL, -- Need RfrequencyShift7p5khzSL-r16Enable the NR SL transmission with a 7.5 kHz shift to the LTE raster. If the field is absent, the frequency shift is disabled.ENUMERATED {true} OPTIONAL, -- Cond V2X-SL-SharedvalueN-r16Indicate the NR SL transmission with a valueN *5kHz shift to the LTE raster (see TS 38.101-1 [15], clause 5.4E.2).INTEGER (-1..1),sl-BWP-List-r16This field indicates the list of sidelink BWP(s) on which the NR sidelink communication configuration. In this release, only one BWP is allowed to be configured for NR sidelink communication.SEQUENCE (SIZE (1..maxNrofSL-BWPs-r16)) OF SL-BWP-ConfigCommon-r16 OPTIONAL, -- Need Rsl-SyncPriority-r16This field indicates synchronization priority order, as specified in clause 5.8.6..ENUMERATED {gnss, gnbEnb} OPTIONAL, -- Need Rsl-NbAsSync-r16This field indicates whether the network can be selected as synchronization reference directly/indirectly only, if sl-SyncPriority is set to gnss. If this field is set to TRUE, the network is enabled to be selected as synchronization reference directly/indirectly. The field is only present in SidelinkPreconfigNR. Otherwise it is absent.BOOLEAN OPTIONAL, -- Need Rsl-SyncConfigList-r16This field indicates the configuration by which the UE is allowed to receive and transmit synchronisation information for NR sidelink communication.Network configures sl-SyncConfig including txParameters when configuring UEs to transmit synchronisation information.If this field is configured in SL-PreconfigurationNR-r16, only one entry is configured in sl-SyncConfigList.SL-SyncConfigList-r16 OPTIONAL, -- Need R ... } -- TAG-SL-FREQCONFIGCOMMON-STOP -- ASN1STOP
SL-FreqConfig field descriptions |
---|
frequencyShift7p5khzSL Enable the NR SL transmission with a 7.5 kHz shift to the LTE raster. If the field is absent, the frequency shift is disabled. |
sl-AbsoluteFrequencyPointA Absolute frequency of the reference resource block (Common RB 0). Its lowest subcarrier is also known as Point A. |
sl-AbsoluteFrequencySSB Indicates the frequency location of sidelink SSB. The transmission bandwidth for sidelink SSB is within the bandwidth of this sidelink BWP. |
sl-BWP-ToAddModList This field indicates the list of sidelink BWP(s) on which the NR sidelink communication configuration is to be added or reconfigured. In this release, only one BWP is allowed to be configured for NR sidelink communication. |
sl-BWP-ToReleaseList This field indicates the list of sidelink BWP(s) on which the NR sidelink communication configuration is to be released. |
sl-Freq-Id This field indicates the identity of the dedicated configuration information on the carrier frequency for NR sidelink communication. |
sl-SCS-SpecificCarrierList A set of UE specific channel bandwidth and location configurations for different subcarrier spacings (numerologies). Defined in relation to Point A. The UE uses the configuration provided in this field only for the purpose of channel bandwidth and location determination. In this release, only one SCS-SpecificCarrier is allowed to be configured for NR sidelink communication. |
sl-SyncPriority This field indicates synchronization priority order, as specified in clause 5.8.6. |
valueN Indicate the NR SL transmission with a valueN *5kHz shift to the LTE raster. (see TS 38.101-1 [15], clause 5.4E.2). |
Conditional Presence | Explanation |
---|---|
V2X-SL-Shared | This field is mandatory present if the carrier frequency configured for NR sidelink communication is shared by V2X sidelink communication. It is absent, Need R, otherwise. |
SL-FreqConfigCommonfield descriptions |
---|
frequencyShift7p5khzSL Enable the NR SL transmission with a 7.5 kHz shift to the LTE raster. If the field is absent, the frequency shift is disabled. |
sl-AbsoluteFrequencyPointA Absolute frequency of the reference resource block (Common RB 0). Its lowest subcarrier is also known as Point A. |
sl-AbsoluteFrequencySSB Indicates the frequency location of sidelink SSB. The transmission bandwidth for sidelink SSB is within the bandwidth of this sidelink BWP. |
sl-BWP-List This field indicates the list of sidelink BWP(s) on which the NR sidelink communication configuration. In this release, only one BWP is allowed to be configured for NR sidelink communication. |
sl-NbAsSync This field indicates whether the network can be selected as synchronization reference directly/indirectly only, if sl-SyncPriority is set to gnss. If this field is set to TRUE, the network is enabled to be selected as synchronization reference directly/indirectly. The field is only present in SidelinkPreconfigNR. Otherwise it is absent. |
sl-SyncPriority This field indicates synchronization priority order, as specified in clause 5.8.6.. |
sl-SyncConfigList This field indicates the configuration by which the UE is allowed to receive and transmit synchronisation information for NR sidelink communication.Network configures sl-SyncConfig including txParameters when configuring UEs to transmit synchronisation information.If this field is configured in SL-PreconfigurationNR-r16, only one entry is configured in sl-SyncConfigList. |
valueN Indicate the NR SL transmission with a valueN *5kHz shift to the LTE raster (see TS 38.101-1 [15], clause 5.4E.2). |
Conditional Presence | Explanation |
---|---|
V2X-SL-Shared | This field is mandatory present if the carrier frequency configured for NR sidelink communication is shared by V2X sidelink communication. It is absent, Need R, otherwise. |
The IE SL-LogicalChannelConfig is used to configure the sidelink logical channel parameters.
-- ASN1START -- TAG-SL-LOGICALCHANNELCONFIG-START SL-LogicalChannelConfig-r16 ::= SEQUENCE { sl-Priority-r16 INTEGER (1..8), sl-PrioritisedBitRate-r16 ENUMERATED {kBps0, kBps8, kBps16, kBps32, kBps64, kBps128, kBps256, kBps512, kBps1024, kBps2048, kBps4096, kBps8192, kBps16384, kBps32768, kBps65536, infinity}, sl-BucketSizeDuration-r16 ENUMERATED {ms5, ms10, ms20, ms50, ms100, ms150, ms300, ms500, ms1000, spare7, spare6, spare5, spare4, spare3,spare2, spare1}, sl-ConfiguredGrantType1Allowed-r16 ENUMERATED {true} OPTIONAL, -- Need R sl-HARQ-FeedbackEnabled-r16 ENUMERATED {enabled, disabled } OPTIONAL, -- Need R sl-AllowedCG-List-r16 SEQUENCE (SIZE (0.. maxNrofCG-SL-1-r16)) OF SL-ConfigIndexCG-r16 OPTIONAL, -- Need R sl-AllowedSCS-List-r16 SEQUENCE (SIZE (1..maxSCSs)) OF SubcarrierSpacing OPTIONAL, -- Need R sl-MaxPUSCH-Duration-r16 ENUMERATED {ms0p02, ms0p04, ms0p0625, ms0p125, ms0p25, ms0p5, spare2, spare1} OPTIONAL, -- Need R sl-LogicalChannelGroup-r16 INTEGER (0..maxLCG-ID) OPTIONAL, -- Need R sl-SchedulingRequestId-r16 SchedulingRequestId OPTIONAL, -- Need R sl-LogicalChannelSR-DelayTimerApplied-r16 BOOLEAN OPTIONAL, -- Need R ... } -- TAG-SL-LOGICALCHANNELCONFIG-STOP -- ASN1STOP
The IE SL-MeasConfigCommon is used to set the cell specific SL RSRP measurement configurations for unicast destinations.
-- ASN1START -- TAG-SL-MEASCONFIGCOMMON-START SL-MeasConfigCommon-r16 ::= SEQUENCE { sl-MeasObjectListCommon-r16 SL-MeasObjectList-r16 OPTIONAL, -- Need R sl-ReportConfigListCommon-r16 SL-ReportConfigList-r16 OPTIONAL, -- Need R sl-MeasIdListCommon-r16 SL-MeasIdList-r16 OPTIONAL, -- Need R sl-QuantityConfigCommon-r16 SL-QuantityConfig-r16 OPTIONAL, -- Need R ... } -- TAG-SL-MEASCONFIGCOMMON-STOP -- ASN1STOP
The IE SL-MeasConfigInfo is used to set RSRP measurement configurations for unicast destinations.
-- ASN1START -- TAG-SL-MEASCONFIGINFO-START SL-MeasConfigInfo-r16 ::= SEQUENCE { sl-DestinationIndex-r16 SL-DestinationIndex-r16, sl-MeasConfig-r16 SL-MeasConfig-r16, ... } SL-MeasConfig-r16 ::= SEQUENCE { sl-MeasObjectToRemoveList-r16 SL-MeasObjectToRemoveList-r16 OPTIONAL, -- Need N sl-MeasObjectToAddModList-r16 SL-MeasObjectList-r16 OPTIONAL, -- Need N sl-ReportConfigToRemoveList-r16 SL-ReportConfigToRemoveList-r16 OPTIONAL, -- Need N sl-ReportConfigToAddModList-r16 SL-ReportConfigList-r16 OPTIONAL, -- Need N sl-MeasIdToRemoveList-r16 SL-MeasIdToRemoveList-r16 OPTIONAL, -- Need N sl-MeasIdToAddModList-r16 SL-MeasIdList-r16 OPTIONAL, -- Need N sl-QuantityConfig-r16 SL-QuantityConfig-r16 OPTIONAL, -- Need M ... } SL-MeasObjectToRemoveList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-ObjectId-r16)) OF SL-MeasObjectId-r16 SL-ReportConfigToRemoveList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-ReportConfigId-r16)) OF SL-ReportConfigId-r16 SL-MeasIdToRemoveList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-MeasId-r16)) OF SL-MeasId-r16 -- TAG-SL-MEASCONFIGINFO-STOP -- ASN1STOP
The IE SL-MeasIdList concerns a list of SL measurement identities to add or modify for a destination, with for each entry the sl-MeasId, the associated sl-MeasObjectId and the associated sl-ReportConfigId.
-- ASN1START -- TAG-SL-MEASIDLIST-START SL-MeasIdList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-MeasId-r16)) OF SL-MeasIdInfo-r16 SL-MeasIdInfo-r16 ::= SEQUENCE { sl-MeasId-r16 SL-MeasId-r16, sl-MeasObjectId-r16 SL-MeasObjectId-r16, sl-ReportConfigId-r16 SL-ReportConfigId-r16, ... } SL-MeasId-r16 ::= INTEGER (1..maxNrofSL-MeasId-r16) -- TAG-SL-MEASIDLIST-STOP -- ASN1STOP
The IE SL-MeasObjectList concerns a list of SL measurement objects to add or modify for a destination.
-- ASN1START -- TAG-SL-MEASOBJECTLIST-START SL-MeasObjectList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-ObjectId-r16)) OF SL-MeasObjectInfo-r16 SL-MeasObjectInfo-r16 ::= SEQUENCE { sl-MeasObjectId-r16 SL-MeasObjectId-r16, sl-MeasObject-r16 SL-MeasObject-r16, ... } SL-MeasObjectId-r16 ::= INTEGER (1..maxNrofSL-ObjectId-r16) SL-MeasObject-r16 ::= SEQUENCE { frequencyInfoSL-r16 ARFCN-ValueNR, ... } -- TAG-SL-MEASOBJECTLIST-STOP -- ASN1STOP
The IE SL-PDCP-Config is used to set the configurable PDCP parameters for a sidelink radio bearer. –SL-PSBCH-Config The IE SL-PSBCH-Config indicates PSBCH transmission parameters on each sidelink bandwidth part. SL-PSBCH-Config information element
-- ASN1START -- TAG-SL-PDCP-CONFIG-START SL-PDCP-Config-r16 ::= SEQUENCE { sl-DiscardTimer-r16 ENUMERATED {ms3, ms10, ms20, ms25, ms30, ms40, ms50, ms60, ms75, ms100, ms150, ms200, ms250, ms300, ms500, ms750, ms1500, infinity} OPTIONAL, -- Cond Setup sl-PDCP-SN-Size-r16 ENUMERATED {len12bits, len18bits} OPTIONAL, -- Cond Setup2 sl-OutOfOrderDelivery ENUMERATED { true } OPTIONAL, -- Need R ... } -- TAG-SL-PDCP-CONFIG-STOP -- ASN1STOP -- ASN1START -- TAG-SL-PSBCH-CONFIG-START SL-PSBCH-Config-r16 ::= SEQUENCE { dl-P0-PSBCH-r16 INTEGER (-16..15) OPTIONAL, -- Need M dl-Alpha-PSBCH-r16 ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} OPTIONAL, -- Need M ... } -- TAG-SL-PSBCH-CONFIG-STOP -- ASN1STOP
The IE SL-PSSCH-TxConfigList indicates PSSCH transmission parameters. When lower layers select parameters from the range indicated in IE SL-PSSCH-TxConfigList, the UE considers both configurations in IE SL-PSSCH-TxConfigList and the CBR-dependent configurations represented in IE SL-CBR-PriorityTxConfigList. Only one IE SL-PSSCH-TxConfig is provided per SL-TypeTxSync.
-- ASN1START -- TAG-SL-PSSCH-TXCONFIGLIST-START SL-PSSCH-TxConfigList-r16 ::= SEQUENCE (SIZE (1..maxPSSCH-TxConfig-r16)) OF SL-PSSCH-TxConfig-r16 SL-PSSCH-TxConfig-r16 ::= SEQUENCE { sl-TypeTxSync-r16 SL-TypeTxSync-r16 OPTIONAL, -- Need R sl-ThresUE-Speed-r16 ENUMERATED {kmph60, kmph80, kmph100, kmph120, kmph140, kmph160, kmph180, kmph200}, sl-ParametersAboveThres-r16 SL-PSSCH-TxParameters-r16, sl-ParametersBelowThres-r16 SL-PSSCH-TxParameters-r16, ..., [[ sl-ParametersAboveThres-v1650 SL-MinMaxMCS-List-r16 OPTIONAL, -- Need R sl-ParametersBelowThres-v1650 SL-MinMaxMCS-List-r16 OPTIONAL -- Need R ]] } SL-PSSCH-TxParameters-r16 ::= SEQUENCE { sl-MinMCS-PSSCH-r16 INTEGER (0..27), sl-MaxMCS-PSSCH-r16 INTEGER (0..31), sl-MinSubChannelNumPSSCH-r16 INTEGER (1..27), sl-MaxSubchannelNumPSSCH-r16 INTEGER (1..27), sl-MaxTxTransNumPSSCH-r16 INTEGER (1..32), sl-MaxTxPower-r16 SL-TxPower-r16 OPTIONAL -- Cond CBR } -- TAG-SL-PSSCH-TXCONFIGLIST-STOP -- ASN1STOP
The IE SL-QoS-FlowIdentity is used to identify a sidelink QoS flow.
SL-LogicalChannelConfig field descriptions |
---|
sl-AllowedCG-List This restriction applies only when the SL grant is a configured grant. If present, SL MAC SDUs from this logical channel can only be mapped to the indicated configured grant configuration. If the size of the sequence is zero, then SL MAC SDUs from this logical channel cannot be mapped to any configured grant configurations. If the field is not present, SL MAC SDUs from this logical channel can be mapped to any configured grant configurations. If the field sl-ConfiguredGrantType1Allowed is present, only those sidelink configured grant type 1 configurations indicated in this sequence are allowed for use by this sidelink logical channel; otherwise, this sequence shall not include any sidelink configured grant type 1 configuration. Corresponds to "sl-AllowedCG-List" as specified in TS 38.321 [3]. |
sl-AllowedSCS-List If present, indicate the numerology of UL-SCH resourcesthat this sidelink logical channel is mapped to, when checking the SR trigger condition. Corresponds to 'sl-AllowedSCS-List' in TS 38.321 [3]. |
sl-BucketSizeDuration Value in ms. ms5 corresponds to 5 ms, value ms10 corresponds to 10 ms, and so on. |
sl-ConfiguredGrantType1Allowed If present and set to true, or if the capability lcp-RestrictionSidelink as specified in TS 38.306 [26] is not indicated, SL MAC SDUs from this sidelink logical channel can be transmitted on a sidelink configured grant type 1. Otherwise, SL MAC SDUs from this logical channel cannot be transmitted on a sidelink configured grant type 1. Corresponds to 'sl-configuredGrantType1Allowed' in TS 38.321 [3]. |
sl-HARQ-FeedbackEnabled Network always includes this field.It indicates the HARQ feedback enabled/disabled restriction in LCP for this sidelink logical channel. If set to enabled, the sidelink logical channel will be multiplexed only with a logical channel which enabling the HARQ feedback. If set to disabled, the sidelink logical channel cannot be multiplexed with a logical channel which enabling the HARQ feedback. Corresponds to 'sl-HARQ-FeedbackEnabled' in TS 38.321 [3].If this field of at least one sidelink logical channel for the UE is set to enabled, sl-PSFCH-Config should be mandatory present in configuration SL-ResourcePool of at least one of the sidelink resource pools. |
sl-LogicalChannelGroup ID of the sidelink logical channel group, as specified in TS 38.321 [3], which the sidelink logical channel belongs to. |
sl-LogicalChannelSR-DelayTimerApplied Indicates whether to apply the delay timer for SR transmission for this sidelink logical channel. Set to false if logicalChannelSR-DelayTimer is not included in sl-BSR-Config. |
sl-MaxPUSCH-Duration If present, indicate the maximum PUSCH duration of UL-SCH resources that this sidelink logical channel is mapped to, when checking the SR trigger condition. Corresponds to "sl-MaxPUSCH-Duration" in TS 38.321 [3]. |
sl-PrioritisedBitRate Value in kiloBytes/s. Value kBps0 corresponds to 0 kiloBytes/s, value kBps8 corresponds to 8 kiloBytes/s, value kBps16 corresponds to 16 kiloBytes/s, and so on. |
sl-Priority Sidelink logical channel priority, as specified in TS 38.321 [3]. |
sl-SchedulingRequestId If present, it indicates the scheduling request configuration applicable for this sidelink logical channel, as specified in TS 38.321 [3]. |
SL-MeasConfigCommon field descriptions |
---|
sl-MeasIdListCommon List of sidelink measurement identities |
sl-MeasObjectListCommon List of sidelink measurement objects. |
sl-QuantityConfigCommon Indicates the layer 3 filtering coefficient for sidelink measurement. |
sl-ReportConfigListCommon List of sidelink measurement reporting configurations. |
SL-MeasConfigInfo field descriptions |
---|
sl-MeasIdToAddModList List of sidelink measurement identities to add and/or modify. |
sl-MeasIdToRemoveList List of sidelink measurement identities to remove. |
sl-MeasObjectToAddModList List of sidelink measurement objects to add and/or modify. |
sl-MeasObjectToRemoveList List of sidelink measurement objects to remove. |
sl-QuantityConfig Indicates the layer 3 filtering coefficient for sidelink measurement. |
sl-ReportConfigToAddModList List of sidelink measurement reporting configurations to add and/or modify. |
sl-ReportConfigToRemoveList List of sidelink measurement reporting configurations to remove. |
SL-MeasObjectList field descriptions |
---|
sl-MeasObjectId It is used to identify a sidelink measurement object configuration. |
sl-MeasObject It specifies information applicable for sidelink DMRS measurement. |
SL-PDCP-Config field descriptions |
---|
sl-DiscardTimer Value in ms of discardTimer specified in TS 38.323 [5]. Value ms50 corresponds to 50 ms, value ms100 corresponds to 100 ms and so on. |
sl-OutOfOrderDelivery Indicates whether or not outOfOrderDelivery specified in TS 38.323 [5] is configured. This field should be either always present or always absent, after the radio bearer is established. |
sl-PDCP-SN-Size PDCP sequence number size for unicast NR sidelink communication, 12 or 18 bits, as specified in TS 38.323 [5]. For groupcast and broadcast NR sidelink communication, only 12 bits is applicable, as specified in 9.1.1.5. |
Conditional Presence | Explanation |
---|---|
Setup | The field is mandatory present in case of sidelink DRB setup via dedicated signaling and in case of sidelink DRB configuration via system information and pre-configuration; otherwise the field is optionally present, need M. |
Setup2 | The field is mandatory present in case of sidelink DRB setup via dedicated signaling and in case of sidelink DRB configuration via system information and pre-configuration for RLC-AM and RLC-UM for unicast NR sidelink communication; otherwise the field is not present, Need M. |
SL-PSBCH-Configfield descriptions |
---|
dl-Alpha-PSBCH Indicates alpha value for DL pathloss based power control for PSBCH. When the field is not configured the UE applies the value 1 |
dl-P0-PSBCH Indicates P0 value for DL pathloss based power control for PSBCH. If not configured, DL pathloss based power control is disabled for PSBCH. |
SL-PSSCH-TxConfigListfield descriptions |
---|
sl-MaxTxTransNumPSSCH Indicates the maximum transmission number (including new transmission and retransmission) for PSSCH. |
sl-MaxTxPower This field indicates the maximum transmission power for transmission on PSSCH and PSCCH. |
sl-MinMCS-PSSCH, sl-MaxMCS-PSSCH This field indicates the minimum and maximum MCS values used for transmissions on PSSCH. The UE shall ignore the minimum and maximum MCS values used for the associated MCS table(s)in sl-ParametersAboveThres-r16 and sl-ParametersBelowThres-r16 if sl-ParametersAboveThres-v1650 and sl-ParametersBelowThres-v1650are present, respectively. |
sl-MinSubChannelNumPSSCH, sl-MaxSubChannelNumPSSCH This field indicates the minimum and maximum number of sub-channels which may be used for transmissions on PSSCH. |
sl-TypeTxSync This field indicates the synchronization reference type. For configurations by the eNB/gNB, only gnbEnb can be configured; and for pre-configuration or when this field is absent, the configuration is applicable for all synchronization reference types. |
sl-ThresUE-Speed This field indicates a UE absolute speed threshold. |
Conditional Presence | Explanation |
---|---|
CBR | The field is optionally present, Need R, when the IE SL-PSSCH-TxParameters is present in SL-CBR-CommonTxConfigList,SL-UE-SelectedConfig,SIB12 or SidelinkPreconfigNR; otherwise the field is not present, need R. |
The IE SL-QoS-Profile is used to give the QoS parameters for a sidelink QoS flow. Need codes or conditions specified for SL-QoS-Profile do not apply, in case SL-QoS-Profile is included in SidelinkUEInformationNR.
-- ASN1START -- TAG-SL-QOS-PROFILE-START SL-QoS-Profile-r16 ::= SEQUENCE { sl-PQI-r16 SL-PQI-r16 OPTIONAL, -- Need R sl-GFBR-r16 INTEGER (0..4000000000) OPTIONAL, -- Need R sl-MFBR-r16 INTEGER (0..4000000000) OPTIONAL, -- Need R sl-Range-r16 INTEGER (1..1000) OPTIONAL, -- Need R ... } SL-PQI-r16 ::= CHOICE { sl-StandardizedPQI-r16 INTEGER (0..255), sl-Non-StandardizedPQI-r16 SEQUENCE { sl-ResourceType-r16 ENUMERATED {gbr, non-GBR, delayCriticalGBR, spare1} OPTIONAL, -- Need R sl-PriorityLevel-r16 INTEGER (1..8) OPTIONAL, -- Need R sl-PacketDelayBudget-r16 INTEGER (0..1023) OPTIONAL, -- Need R sl-PacketErrorRate-r16 INTEGER (0..9) OPTIONAL, -- Need R sl-AveragingWindow-r16 INTEGER (0..4095) OPTIONAL, -- Need R sl-MaxDataBurstVolume-r16 INTEGER (0..4095) OPTIONAL, -- Need R ... } } -- TAG-SL-QOS-PROFILE-STOP -- ASN1STOP
The IE SL-QuantityConfig specifies the layer 3 filtering coefficients for NR SL RSRP measurement for a destination.
-- ASN1START -- TAG-SL-QUANTITYCONFIG-START SL-QuantityConfig-r16 ::= SEQUENCE { sl-FilterCoefficientDMRS-r16 FilterCoefficient DEFAULT fc4, ... } -- TAG-SL-QuantityConfig-STOP -- ASN1STOP
The IE SL-RadioBearerConfig specifies the sidelink DRB configuration information for NR sidelink communication.
-- ASN1START -- TAG-SL-RADIOBEARERCONFIG-START SL-RadioBearerConfig-r16 ::= SEQUENCE { slrb-Uu-ConfigIndex-r16 SLRB-Uu-ConfigIndex-r16, sl-SDAP-Config-r16 SL-SDAP-Config-r16 OPTIONAL, -- Cond SLRBSetup sl-PDCP-Config-r16 SL-PDCP-Config-r16 OPTIONAL, -- Cond SLRBSetup sl-TransRange-r16 ENUMERATED {m20, m50, m80, m100, m120, m150, m180, m200, m220, m250, m270, m300, m350, m370, m400, m420, m450, m480, m500, m550, m600, m700, m1000, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL, -- Need R ... } -- TAG-SL-RADIOBEARERCONFIG-STOP -- ASN1STOP
The IE SL-ReportConfigList concerns a list of SL measurement reporting configurations to add or modify for a destination.
-- ASN1START -- TAG-SL-REPORTCONFIGLIST-START SL-ReportConfigList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-ReportConfigId-r16)) OF SL-ReportConfigInfo-r16 SL-ReportConfigInfo-r16 ::= SEQUENCE { sl-ReportConfigId-r16 SL-ReportConfigId-r16, sl-ReportConfig-r16 SL-ReportConfig-r16, ... } SL-ReportConfigId-r16 ::= INTEGER (1..maxNrofSL-ReportConfigId-r16) SL-ReportConfig-r16 ::= SEQUENCE { sl-ReportType-r16 CHOICE { sl-Periodical-r16 SL-PeriodicalReportConfig-r16, sl-EventTriggered-r16 SL-EventTriggerConfig-r16, ... }, ... } SL-PeriodicalReportConfig-r16 ::= SEQUENCE { sl-ReportInterval-r16 ReportInterval, sl-ReportAmount-r16 ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}, sl-ReportQuantity-r16 SL-MeasReportQuantity-r16, sl-RS-Type-r16 SL-RS-Type-r16, ... } SL-EventTriggerConfig-r16 ::= SEQUENCE { sl-EventId-r16 CHOICE { eventS1-r16 SEQUENCE { s1-Threshold-r16 SL-MeasTriggerQuantity-r16, sl-ReportOnLeave-r16 BOOLEAN, sl-Hysteresis-r16 Hysteresis, sl-TimeToTrigger-r16 TimeToTrigger, ... }, eventS2-r16 SEQUENCE { s2-Threshold-r16 SL-MeasTriggerQuantity-r16, sl-ReportOnLeave-r16 BOOLEAN, sl-Hysteresis-r16 Hysteresis, sl-TimeToTrigger-r16 TimeToTrigger, ... }, ... }, sl-ReportInterval-r16 ReportInterval, sl-ReportAmount-r16 ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}, sl-ReportQuantity-r16 SL-MeasReportQuantity-r16, sl-RS-Type-r16 SL-RS-Type-r16, ... } SL-MeasReportQuantity-r16 ::= CHOICE { sl-RSRP-r16 BOOLEAN, ... } SL-MeasTriggerQuantity-r16 ::= CHOICE { sl-RSRP-r16 RSRP-Range, ... } SL-RS-Type-r16 ::= ENUMERATED {dmrs, spare3, spare2, spare1} -- TAG-SL-REPORTCONFIGLIST-STOP -- ASN1STOP
The IE SL-ResourcePool specifies the configuration information for NR sidelink communication resource pool.
-- ASN1START -- TAG-SL-RESOURCEPOOL-START SL-ResourcePool-r16 ::= SEQUENCE { sl-PSCCH-Config-r16 SetupRelease { SL-PSCCH-Config-r16 } OPTIONAL, -- Need M sl-PSSCH-Config-r16 SetupRelease { SL-PSSCH-Config-r16 } OPTIONAL, -- Need M sl-PSFCH-Config-r16 SetupRelease { SL-PSFCH-Config-r16 } OPTIONAL, -- Need M sl-SyncAllowed-r16 SL-SyncAllowed-r16 OPTIONAL, -- Need M sl-SubchannelSize-r16 ENUMERATED {n10, n12, n15, n20, n25, n50, n75, n100} OPTIONAL, -- Need M dummy INTEGER (10..160) OPTIONAL, -- Need M sl-StartRB-Subchannel-r16 INTEGER (0..265) OPTIONAL, -- Need M sl-NumSubchannel-r16 INTEGER (1..27) OPTIONAL, -- Need M sl-Additional-MCS-Table-r16 ENUMERATED {qam256, qam64LowSE, qam256-qam64LowSE } OPTIONAL, -- Need M sl-ThreshS-RSSI-CBR-r16 INTEGER (0..45) OPTIONAL, -- Need M sl-TimeWindowSizeCBR-r16 ENUMERATED {ms100, slot100} OPTIONAL, -- Need M sl-TimeWindowSizeCR-r16 ENUMERATED {ms1000, slot1000} OPTIONAL, -- Need M sl-PTRS-Config-r16 SL-PTRS-Config-r16 OPTIONAL, -- Need M sl-UE-SelectedConfigRP-r16 SL-UE-SelectedConfigRP-r16 OPTIONAL, -- Need M sl-RxParametersNcell-r16 SEQUENCE { sl-TDD-Configuration-r16 TDD-UL-DL-ConfigCommon OPTIONAL, -- Need M sl-SyncConfigIndex-r16 INTEGER (0..15) } OPTIONAL, -- Need M sl-ZoneConfigMCR-List-r16 SEQUENCE (SIZE (16)) OF SL-ZoneConfigMCR-r16 OPTIONAL, -- Need M sl-FilterCoefficient-r16 FilterCoefficient OPTIONAL, -- Need M sl-RB-Number-r16 INTEGER (10..275) OPTIONAL, -- Need M sl-PreemptionEnable-r16 ENUMERATED {enabled, pl1, pl2, pl3, pl4, pl5, pl6, pl7, pl8} OPTIONAL, -- Need R sl-PriorityThreshold-UL-URLLC-r16 INTEGER (1..9) OPTIONAL, -- Need M sl-PriorityThreshold-r16 INTEGER (1..9) OPTIONAL, -- Need M sl-X-Overhead-r16 ENUMERATED {n0,n3, n6, n9} OPTIONAL, -- Need S sl-PowerControl-r16 SL-PowerControl-r16 OPTIONAL, -- Need M sl-TxPercentageList-r16 SL-TxPercentageList-r16 OPTIONAL, -- Need M sl-MinMaxMCS-List-r16 SL-MinMaxMCS-List-r16 OPTIONAL, -- Need M ..., [[ sl-TimeResource-r16 BIT STRING (SIZE (10..160)) OPTIONAL -- Need M ]] } SL-ZoneConfigMCR-r16 ::= SEQUENCE { sl-ZoneConfigMCR-Index-r16 INTEGER (0..15), sl-TransRange-r16 ENUMERATED {m20, m50, m80, m100, m120, m150, m180, m200, m220, m250, m270, m300, m350, m370, m400, m420, m450, m480, m500, m550, m600, m700, m1000, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL, -- Need M sl-ZoneConfig-r16 SL-ZoneConfig-r16 OPTIONAL, -- Need M ... } SL-SyncAllowed-r16 ::= SEQUENCE { gnss-Sync-r16 ENUMERATED {true} OPTIONAL, -- Need R gnbEnb-Sync-r16 ENUMERATED {true} OPTIONAL, -- Need R ue-Sync-r16 ENUMERATED {true} OPTIONAL -- Need R } SL-PSCCH-Config-r16 ::= SEQUENCE { sl-TimeResourcePSCCH-r16 ENUMERATED {n2, n3} OPTIONAL, -- Need M sl-FreqResourcePSCCH-r16 ENUMERATED {n10,n12, n15, n20, n25} OPTIONAL, -- Need M sl-DMRS-ScrambleID-r16 INTEGER (0..65535) OPTIONAL, -- Need M sl-NumReservedBits-r16 INTEGER (2..4) OPTIONAL, -- Need M ... } SL-PSSCH-Config-r16 ::= SEQUENCE { sl-PSSCH-DMRS-TimePatternList-r16 SEQUENCE (SIZE (1..3)) OF INTEGER (2..4) OPTIONAL, -- Need M sl-BetaOffsets2ndSCI-r16 SEQUENCE (SIZE (4)) OF SL-BetaOffsets-r16 OPTIONAL, -- Need M sl-Scaling-r16 ENUMERATED {f0p5, f0p65, f0p8, f1} OPTIONAL, -- Need M ... } SL-PSFCH-Config-r16 ::= SEQUENCE { sl-PSFCH-Period-r16 ENUMERATED {sl0, sl1, sl2, sl4} OPTIONAL, -- Need M sl-PSFCH-RB-Set-r16 BIT STRING (SIZE (10..275)) OPTIONAL, -- Need M sl-NumMuxCS-Pair-r16 ENUMERATED {n1, n2, n3, n6} OPTIONAL, -- Need M sl-MinTimeGapPSFCH-r16 ENUMERATED {sl2, sl3} OPTIONAL, -- Need M sl-PSFCH-HopID-r16 INTEGER (0..1023) OPTIONAL, -- Need M sl-PSFCH-CandidateResourceType-r16 ENUMERATED {startSubCH, allocSubCH} OPTIONAL, -- Need M ... } SL-PTRS-Config-r16 ::= SEQUENCE { sl-PTRS-FreqDensity-r16 SEQUENCE (SIZE (2)) OF INTEGER (1..276) OPTIONAL, -- Need M sl-PTRS-TimeDensity-r16 SEQUENCE (SIZE (3)) OF INTEGER (0..29) OPTIONAL, -- Need M sl-PTRS-RE-Offset-r16 ENUMERATED {offset01, offset10, offset11} OPTIONAL, -- Need M ... } SL-UE-SelectedConfigRP-r16 ::= SEQUENCE { sl-CBR-PriorityTxConfigList-r16 SL-CBR-PriorityTxConfigList-r16 OPTIONAL, -- Need M sl-Thres-RSRP-List-r16 SL-Thres-RSRP-List-r16 OPTIONAL, -- Need M sl-MultiReserveResource-r16 ENUMERATED {enabled} OPTIONAL, -- Need M sl-MaxNumPerReserve-r16 ENUMERATED {n2, n3} OPTIONAL, -- Need M sl-SensingWindow-r16 ENUMERATED {ms100, ms1100} OPTIONAL, -- Need M sl-SelectionWindowList-r16 SL-SelectionWindowList-r16 OPTIONAL, -- Need M sl-ResourceReservePeriodList-r16 SEQUENCE (SIZE (1..16)) OF SL-ResourceReservePeriod-r16 OPTIONAL, -- Need M sl-RS-ForSensing-r16 ENUMERATED {pscch, pssch}, ..., [[ sl-CBR-PriorityTxConfigList-v1650 SL-CBR-PriorityTxConfigList-v1650 OPTIONAL -- Need M ]] } SL-ResourceReservePeriod-r16 ::= CHOICE { sl-ResourceReservePeriod1-r16 ENUMERATED {ms0, ms100, ms200, ms300, ms400, ms500, ms600, ms700, ms800, ms900, ms1000}, sl-ResourceReservePeriod2-r16 INTEGER (1..99) } SL-SelectionWindowList-r16 ::= SEQUENCE (SIZE (8)) OF SL-SelectionWindowConfig-r16 SL-SelectionWindowConfig-r16 ::= SEQUENCE { sl-Priority-r16 INTEGER (1..8), sl-SelectionWindow-r16 ENUMERATED {n1, n5, n10, n20} } SL-TxPercentageList-r16 ::= SEQUENCE (SIZE (8)) OF SL-TxPercentageConfig-r16 SL-TxPercentageConfig-r16 ::= SEQUENCE { sl-Priority-r16 INTEGER (1..8), sl-TxPercentage-r16 ENUMERATED {p20, p35, p50} } SL-MinMaxMCS-List-r16 ::= SEQUENCE (SIZE (1..3)) OF SL-MinMaxMCS-Config-r16 SL-MinMaxMCS-Config-r16 ::= SEQUENCE { sl-MCS-Table-r16 ENUMERATED {qam64, qam256, qam64LowSE}, sl-MinMCS-PSSCH-r16 INTEGER (0..27), sl-MaxMCS-PSSCH-r16 INTEGER (0..31) } SL-BetaOffsets-r16 ::= INTEGER (0..31) SL-PowerControl-r16 ::= SEQUENCE { sl-MaxTransPower-r16 INTEGER (-30..33), sl-Alpha-PSSCH-PSCCH-r16 ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} OPTIONAL, -- Need M dl-Alpha-PSSCH-PSCCH-r16 ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} OPTIONAL, -- Need S sl-P0-PSSCH-PSCCH-r16 INTEGER (-16..15) OPTIONAL, -- Need S dl-P0-PSSCH-PSCCH-r16 INTEGER (-16..15) OPTIONAL, -- Need M dl-Alpha-PSFCH-r16 ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} OPTIONAL, -- Need S dl-P0-PSFCH-r16 INTEGER (-16..15) OPTIONAL, -- Need M ... } -- TAG-SL-RESOURCEPOOL-STOP -- ASN1STOP
The IE SL-RLC-BearerConfig specifies the SL RLC bearer configuration information for NR sidelink communication.
-- ASN1START -- TAG-SL-RLC-BEARERCONFIG-START SL-RLC-BearerConfig-r16 ::= SEQUENCE { sl-RLC-BearerConfigIndex-r16 SL-RLC-BearerConfigIndex-r16, sl-ServedRadioBearer-r16 SLRB-Uu-ConfigIndex-r16 OPTIONAL, -- Cond LCH-SetupOnly sl-RLC-Config-r16 SL-RLC-Config-r16 OPTIONAL, -- Cond LCH-Setup sl-MAC-LogicalChannelConfig-r16 SL-LogicalChannelConfig-r16 OPTIONAL, -- Cond LCH-Setup ... } -- TAG-SL-RLC-BEARERCONFIG-STOP -- ASN1STOP
The IE SL-RLC-BearerConfigIndex is used to identify a SL RLC bearer configuration.
The IE SL-RLC-Config is used to specify the RLC configuration of sidelink DRB. RLC AM configuration is only applicable to the unicast NR sidelink communication.
-- ASN1START -- TAG-SL-RLC-CONFIG-START SL-RLC-Config-r16 ::= CHOICE { sl-AM-RLC-r16 SEQUENCE { sl-SN-FieldLengthAM-r16 SN-FieldLengthAM OPTIONAL, -- Cond SLRBSetup sl-T-PollRetransmit-r16 T-PollRetransmit, sl-PollPDU-r16 PollPDU, sl-PollByte-r16 PollByte, sl-MaxRetxThreshold-r16 ENUMERATED { t1, t2, t3, t4, t6, t8, t16, t32 }, ... }, sl-UM-RLC-r16 SEQUENCE { sl-SN-FieldLengthUM-r16 SN-FieldLengthUM OPTIONAL, -- Cond SLRBSetup ... }, ... } -- TAG-SL-RLC-CONFIG-STOP -- ASN1STOP
The IE SL-ScheduledConfig specifies sidelink communication configurations used for network scheduled NR sidelink communication.
-- ASN1START -- TAG-SL-SCHEDULEDCONFIG-START SL-ScheduledConfig-r16 ::= SEQUENCE { sl-RNTI-r16 RNTI-Value, mac-MainConfigSL-r16 MAC-MainConfigSL-r16 OPTIONAL, -- Need M sl-CS-RNTI-r16 RNTI-Value OPTIONAL, -- Need M sl-PSFCH-ToPUCCH-r16 SEQUENCE (SIZE (1..8)) OF INTEGER (0..15) OPTIONAL, -- Need M sl-ConfiguredGrantConfigList-r16 SL-ConfiguredGrantConfigList-r16 OPTIONAL, -- Need M ..., [[ sl-DCI-ToSL-Trans-r16 SEQUENCE (SIZE (1..8)) OF INTEGER (1..32) OPTIONAL -- Need M ]] } MAC-MainConfigSL-r16 ::= SEQUENCE { sl-BSR-Config-r16 BSR-Config OPTIONAL, -- Need M ul-PrioritizationThres-r16 INTEGER (1..16) OPTIONAL, -- Need M sl-PrioritizationThres-r16 INTEGER (1..8) OPTIONAL, -- Need M ... } SL-ConfiguredGrantConfigList-r16 ::= SEQUENCE { sl-ConfiguredGrantConfigToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofCG-SL-r16)) OF SL-ConfigIndexCG-r16 OPTIONAL, -- Need N sl-ConfiguredGrantConfigToAddModList-r16 SEQUENCE (SIZE (1..maxNrofCG-SL-r16)) OF SL-ConfiguredGrantConfig-r16 OPTIONAL -- Need N } -- TAG-SL-SCHEDULEDCONFIG-STOP -- ASN1STOP
SL-QoS-Profile field descriptions |
---|
sl-GFBR Indicate the guaranteed bit rate for a GBR QoS flow.The unit is: Kbit/s |
sl-MFBR Indicate the maximum bit rate for a GBR QoS flow. The unit is: Kbit/s |
sl-PQI This field indicates either the PQI for standardized PQI or non-standardized QoS parameters. |
sl-Range This field indicates the range parameter of the Qos flow, as defined in clause 5.4.1.1.1, TS 23.287 [55]. It is present only for groupcast. The unit is meter. |
SL-PQI field descriptions |
---|
sl-AveragingWindow Indicates the Averaging Window for a QoS flow, and applies to GBR QoS flows only.Unit: ms. The default value of the IE is 2000ms. |
sl-MaxDataBurstVolume Indicates the Maximum Data Burst Volume for a QoS flow, and applies to delay critical GBR QoS flows only. Unit: byte. |
sl-PacketDelayBudget Indicates the Packet Delay Budget for a QoS flow. Upper bound value for the delay that a packet may experience expressed in unit of 0.5ms. |
sl-PacketErrorRate Indicates the Packet Error Rate for a QoS flow. The packet error rate is expressed as Scalar x 10-k where k is the Exponent. |
sl-PriorityLevel Indicates the Priority Level for a QoS flow.Values ordered in decreasing order of priority, i.e. with 1 as the highest priority and 8 as the lowest priority. |
sl-StandardizedPQI Indicate the PQI for standardized PQI. |
SL-QuantityConfig field descriptions |
---|
sl-FilterCoefficientDMRS DMRS based L3 filter configuration: Specifies L3 filter configuration for sidelink RSRP measurement result from the L1 fiter(s), as defined in TS 38.215 [9]. |
SL-RadioBearerConfig field descriptions |
---|
sl-PDCP-Config This field indicates the PDCP parameters for the sidelink DRB. |
sl-SDAP-Config This field indicates how to map sidelink QoS flows to sidelink DRB. |
slrb-Uu-ConfigIndex This field indicates the index of sidelink DRB configuration. |
sl-TransRange This field indicates the transmission range of the sidelink DRB. The unit is meter. |
Conditional Presence | Explanation |
---|---|
SLRBSetup | The field is mandatory present in case of sidelink DRB setup via the dedicated signalling and in case of sidelink DRB configuration via system information and pre-configuration; otherwise the field is optionally present, need M. |
SL-ReportConfig field descriptions |
---|
sl-ReportType Type of the configured sidelink measurement report. |
SL-EventTriggerConfig field descriptions |
---|
sl-EventId Choice of sidelink measurement event triggered reporting criteria. |
sl-ReportAmount Number of sidelink measurement reports applicable for sl-EventTriggered report type. |
sl-ReportInterval Indicates the interval between periodical reports (i.e., when sl-ReportAmount exceeds 1) for sl-EventTriggered report type. |
sl-ReportOnLeave indicates whether or not the UE shall initiate the sidelink measurement reporting procedure when the leaving condition is met for a frequency in sl-FrequencyTriggeredList, as specified in 5.8.10.4.1. |
sl-ReportQuantity The sidelink measurement quantities to be included in the sidelink measurement report. |
sl-TimeToTrigger Time during which specific criteria for the event needs to be met in order to trigger a sidelink measurement report. |
sN-Threshold Threshold used for events S1 and S2 specified in clauses 5.8.10.4.2 and 5.8.10.4.3, respectively. |
SL-PeriodicalReportConfig field descriptions |
---|
sl-ReportAmount Number of sidelink measurement reports applicable for sl-Periodical report type. |
sl-ReportInterval Indicates the interval between periodical reports (i.e., when sl-ReportAmount exceeds 1) for sl-Periodical report type. |
sl-ReportQuantity The sidelink measurement quantities to be included in the sidelink measurement report. |
SL-ZoneConfigMCR field descriptions |
---|
sl-TransRange Indicates the communication range requirement for the corresponding sl-ZoneConfigMCR-Index. |
sl-ZoneConfig Indicates the zone configuration for the corresponding sl-ZoneConfigMCR-Index. |
sl-ZoneConfigMCR-Index Indicates the codepoint of the communication range requirement field in SCI. |
SL-ResourcePool field descriptions |
---|
dummy This field is not used in the specification. If received it shall be ignored by the UE. |
sl-FilterCoefficient This field indicates the filtering coefficient for long-term measurement and reference signal power derivation used for sidelink open-loop power control. |
sl-Additional-MCS-Table Indicates the MCS table(s) additionally used in the resource pool.64QAM table is (pre-)configured as default. Zero, one or two can be additionally (pre-)configured using the 256QAM and/or low-SE MCS tables. If two MCS tables are indicated, 256QAM MCS table is the 1st table and qam64lowSE MCS table is the 2ndtable as specified in TS 38.214 [19], clause 8.1.3.1. |
sl-NumSubchannel Indicates the number of subchannels in the corresponding resource pool, which consists of contiguous PRBs only. |
sl-PreemptionEnable Indicates whether pre-emption is disabled or enabled in a resource pool. If the field is present and the value is pl1, pl2, and so on (but not enabled), it means that pre-emption is enabled and a priority level p_preemption is configured. If the field is present and the value is enabled, the pre-emption is enabled (but p_preemption is not configured) and pre-emption is applicable to all levels. |
sl-PriorityThreshold-UL-URLLC Indicates the threshold used to determine whether NR sidelink transmission is prioritized over uplink transmission of priority index 1 as specified in TS 38.213[13], clause 16.2.4.3, or whether PUCCH transmission carrying SL HARQ is prioritized over PUCCH transmission carrying UCI of priority index 1 if they overlap in time as specified in TS 38.213[13], clause 9.2.5.0. |
sl-PriorityThreshold Indicates the threshold used to determine whether NR sidelink transmission is prioritized over uplink transmission of priority index 0 as specified in TS 38.213[13], clause 16.2.4.3, or whether PUCCH transmission carrying SL HARQ is prioritized over PUCCH transmission carrying UCI of priority index 0 if they overlap in time as specified in TS 38.213[13], clause 9.2.5.0. |
sl-RB-Number Indicates the number of PRBs in the corresponding resource pool, which consists of contiguous PRBs only. The remaining RB cannot be used (See TS 38.214[19], clause 8). |
sl-StartRB-Subchannel Indicates the lowest RB index of the subchannel with the lowest index in the resource poolwith respect to the lowest RB index of a SL BWP. |
sl-SubchannelSize Indicates the minimum granularity in frequency domain for the sensing for PSSCH resource selection in the unit of PRB. |
sl-SyncAllowed Indicates the allowed synchronization reference(s) which is (are) allowed to use the configured resource pool. |
sl-SyncConfigIndex Indicates the synchronisation configuration that is associated with a reception pool, by means of an index to the corresponding entry SL-SyncConfigList of in SIB12 for NR sidelink communication. |
sl-TDD-Configuration Indicates the TDD configuration associated with the reception pool of the cell indicated by sl-SyncConfigIndex. |
sl-ThreshS-RSSI-CBR Indicates the S-RSSI threshold for determining the contribution of a sub-channel to the CBR measurement. Value 0 corresponds to -112 dBm, value 1 to -110 dBm, value n to (-112 + n*2) dBm, and so on. |
sl-TimeResource Indicates the bitmap of the resource pool, which is defined by repeating the bitmap with a periodicity during a SFN or DFN cycle. |
sl-TimeWindowSizeCBR Indicates the time window size for CBR measurement. |
sl-TimeWindowSizeCR Indicates the time window size for CR evaluation. |
sl-TxPercentageList Indicates the portion of candidate single-slot PSSCH resources over the total resources. Value p20 corresponds to 20%, and so on. |
sl-X-Overhead Accounts for overhead from CSI-RS, PT-RS. If the field is absent, the UE applies value n0 (see TS 38.214 [19], clause 5.1.3.2). |
SL-SyncAllowed field descriptions |
---|
gnbEnb-Sync If configured, the (pre-) configured resources can be used if the UE is directly or indirectly synchronized to eNB or gNB (i.e., synchronized to a reference UE which is directly synchronized to eNB or gNB). |
gnss-Sync If configured, the (pre-) configured resources can be used if the UE is directly or indirectly synchronized to GNSS (i.e., synchronized to a reference UE which is directly synchronized to GNSS). |
ue-Sync If configured, the (pre-) configured resources can be used if the UE is synchronized to a reference UE which is not synchronized to eNB, gNB and GNSS directly or indirectly. |
SL-PSCCH-Configfield descriptions |
---|
sl-FreqResourcePSCCH Indicates the number of PRBs for PSCCH in a resource pool where it is not greater than the number PRBs of the subchannel. |
sl-DMRS-ScrambleID Indicates the initialization value for PSCCH DMRS scrambling. |
sl-NumReservedBits Indicates the number of reserved bits in first stage SCI. |
sl-TimeResourcePSCCH Indicates the number of symbols of PSCCH in a resource pool. |
SL-PSSCH-Configfield descriptions |
---|
sl-BetaOffsets2ndSCI Indicates candidates of beta-offset values to determine the number of coded modulation symbols for second stage SCI.The value indicates the index of Table 9.3-2 of TS 38.213 [13]. |
sl-PSSCH-DMRS-TimePatternList Indicates the set of PSSCH DMRS time domain patterns in terms of PSSCH DMRS symbols in a slot that can be used in the resource pool. |
sl-Scaling Indicates a scaling factor to limit the number of resource elements assigned to the second stage SCI on PSSCH. Value f0p5 corresponds to 0.5, value f0p65 corresponds to 0.65, and so on. |
SL-PSFCH-Configfield descriptions |
---|
sl-MinTimeGapPSFCH The minimum time gap between PSFCH and the associated PSSCH in the unit of slots. |
sl-NumMuxCS-Pair Indicates the number of cyclic shift pairs used for a PSFCH transmission that can be multiplexed in a PRB. |
sl-PSFCH-CandidateResourceType Indicates the number of PSFCH resources available for multiplexing HARQ-ACK information in a PSFCH transmission (see TS 38.213 [13], clause 16.3). |
sl-PSFCH-HopID Scrambling ID for sequence hopping of the PSFCH used in the resource pool. |
sl-PSFCH-Period Indicates the period of PSFCH resource in the unit of slots within this resource pool. If set to sl0, no resource for PSFCH, and HARQ feedback for all transmissions in the resource pool is disabled. |
sl-PSFCH-RB-Set Indicates the set of PRBs that are actually used for PSFCH transmission and reception. The leftmost bit of the bitmap refers to the lowest RB index in the resource pool, and so on. Value 0 in the bitmap indicates that the corresponding PRB is not used for PSFCH transmission and reception while value 1 indicates that the corresponding PRB is used for PSFCH transmission and reception (see TS 38.213 [13]). |
SL-PTRS-Config field descriptions |
---|
sl-PTRS-FreqDensity Presence and frequency density of SL PT-RS as a function of scheduled BW. If the field is not configured, the UE uses K_PT-RS = 2 |
sl-PTRS-TimeDensity Presence and time density of SL PT-RS as a function of MCS. If the field is not configured, the UE uses L_PT-RS = 1 |
sl-PTRS-RE-Offset Indicates the subcarrier offset for SL PT-RS . If the field is not configured, the UE applies the value offset00(see TS 38.211 [16], clause 8.4.1.2.2). |
SL-UE-SelectedConfigRPfield descriptions |
---|
sl-CBR-PriorityTxConfigList Indicates the mapping between PSSCH transmission parameter (such as MCS, PRB number, retransmission number, CR limit) sets by using the indexes of the configurations in sl-CBR-PSSCH-TxConfigList, CBR ranges by using the indexes to the entry of the CBR range configurations in sl-CBR-RangeConfigList, and priority ranges. It also indicates the default PSSCH transmission parameters to be used when CBR measurement results are not available, and MCS range for the MCS tables used in the resource pool. The field sl-CBR-PriorityTxConfigList-v1650 is present only when sl-CBR-PriorityTxConfigList-r16 is configured. |
sl-MaxNumPerReserve Indicates the maximum number of reserved PSCCH/PSSCH resources that can be indicated by an SCI. |
sl-MultiReserveResource Indicates if it is allowed to reserve a sidelink resource for an initial transmission of a TB by an SCI associated with a different TB, based on sensing and resource selection procedure. |
sl-ResourceReservePeriodList Set of possible resource reservation period allowed in the resource pool in the unit of ms. Up to 16 values can be configured per resource pool.The value ms0 is always configured. |
sl-RS-ForSensing Indicates whether DMRS of PSCCH or PSSCH is used for L1 RSRP measurement in the sensing operation. |
sl-SensingWindow Parameter that indicates the start of the sensing window. |
sl-SelectionWindowList Parameter that determines the end of the selection window in the resource selection for a TB with respect to priority indicated in SCI. Value n1 corresponds to 1*2µ, value n5 corresponds to 5*2µ, and so on, where µ = 0,1,2,3 refers to SCS 15,30,60,120 kHz respectively. |
sl-Thres-RSRP-List Indicates a list of 64 thresholds, and the threshold should be selected based on the priority in the decoded SCI and the priority in the SCI to be transmitted. A resource is excluded if it is indicated or reserved by a decoded SCI and PSSCH/PSCCH RSRP in the associated data resource is above a threshold. |
SL-PowerControl field descriptions |
---|
sl-MaxTransPower Indicates the maximum value of the UE's sidelink transmission power on this resource poolwhen the sidelink transmission is performed only on this resource pool. The unit is dBm. If the sidelink transmission is PSFCH, and multiple resource pools are used, the maximum transmission power for PSFCH is configured as sum of fields sl-maxTransPower over multiple resource pools, as specified in TS 38.101-1 [15]. |
sl-Alpha-PSSCH-PSCCH Indicates alpha value for sidelink pathloss based power control for PSCCH/PSSCH when sl-P0-PSSCH-PSCCH is configured. When the field is absent the UE applies the value 1. |
sl-P0-PSSCH-PSCCH Indicates P0 value for sidelink pathloss based power control for PSCCH/PSSCH. If not configured, sidelink pathloss based power control is disabled for PSCCH/PSSCH. |
dl-Alpha-PSSCH-PSCCH Indicates alpha value for downlink pathloss based power control for PSCCH/PSSCH when dl-P0-PSSCH-PSCCH is configured. When the field is absent the UE applies the value 1. |
dl-P0-PSSCH-PSCCH Indicates P0 value for downlink pathloss based power control for PSCCH/PSSCH. If not configured, downlink pathloss based power control is disabled for PSCCH/PSSCH. |
dl-Alpha-PSFCH Indicates alpha value for downlink pathloss based power control for PSFCH when dl-P0-PSFCH is configured. When the field is absent the UE applies the value 1. For resource pools configured with PSFCH resources overlapping in time, this field is either not configured in any of the resource pools or configured with the same value for all the resource pools. |
dl-P0-PSFCH Indicates P0 value for downlink pathloss based power control for PSFCH. If not configured, downlink pathloss based power control is disabled for PSFCH. For resource pools configured with PSFCH resources overlapping in time, this field is either not configured in any of the resource pools or configured with the same value for all the resource pools. |
SL-MinMaxMCS-Configfield descriptions |
---|
sl-MaxMCS-PSSCH Indicates the maximum MCS value when using the associated MCS table. If no MCS is configured, UE autonomously selects MCS from the full range of values. |
sl-MinMCS-PSSCH Indicates the minimum MCS value when using the associated MCS table. If no MCS is configured, UE autonomously selects MCS from the full range of values. |
SL-RLC-BearerConfig field descriptions |
---|
sl-MAC-LogicalChannelConfig The field is used to configure MAC SL logical channel paramenters. |
sl-RLC-BearerConfigIndex The index of the RLC bearer configuration. |
sl-RLC-Config Determines the RLC mode (UM, AM) and provides corresponding parameters. |
sl-ServedRadioBearer Associates the sidelink RLC Bearer with a sidelink DRB. It indicates the index of SL radio bearer configuration, which is corresponding to the RLC bearer configuration. |
Conditional Presence | Explanation |
---|---|
LCH-Setup | The field is mandatory present upon creation of a new sidelink logical channel via the dedicated signalling and in case of sidelink DRB configuration via system information and pre-configuration; otherwise the field is optionally present, Need M. |
LCH-SetupOnly | This field is mandatory present upon creation of a newsidelink logical channel via the dedicated signalling and in case of sidelink DRB configuration via system information and pre-configuration. Otherwise, it is absent, Need M. |
SL-RLC-Config field descriptions |
---|
sl-MaxRetxThreshold Parameter value of maxRetxThresholdfor RLC AM for NR sidelink communications, see TS 38.322 [4]. Value t1 corresponds to 1 retransmission, value t2 corresponds to 2 retransmissions and so on. |
sl-PollByte Parameter value of pollBytefor RLC AM for NR sidelink communications, see TS 38.322 [4]. Value kB25 corresponds to 25 kBytes, value kB50 corresponds to 50 kBytes and so on. infinity corresponds to an infinite amount of kBytes. |
sl-PollPDU Parameter value of pollPDUfor RLC AM for NR sidelink communications, seeTS 38.322 [4]. Value p4 corresponds to 4 PDUs, value p8 corresponds to 8 PDUs and so on. infinity corresponds to an infinite number of PDUs. |
sl-SN-FieldLength This field indicates the RLC SN field size for NR sidelink communication, see TS 38.322 [4]. For groupcast and broadcast, only value size6 (6 bits) is configured for the field sl-SN-FieldLengthUM. |
sl-T-PollRetransmit Timer value of t-PollRetransmitfor RLC AM for NR sidelink communications, see TS 38.322 [4], in milliseconds. Value ms5 means 5 ms, value ms10 means 10 ms and so on. |
Conditional Presence | Explanation |
---|---|
SLRBSetup | The field is mandatory present in case of sidelink DRB setup via the dedicated signalling and in case of sidelink DRB configuration via system information and pre-configuration; otherwise the field is optionally present, need M. |
The IE SL-SDAP-Config is used to set the configurable SDAP parameters for a Sidelink DRB.
-- ASN1START -- TAG-SL-SDAP-CONFIG-START SL-SDAP-Config-r16 ::= SEQUENCE { sl-SDAP-Header-r16 ENUMERATED {present, absent}, sl-DefaultRB-r16 BOOLEAN, sl-MappedQoS-Flows-r16 CHOICE { sl-MappedQoS-FlowsList-r16 SEQUENCE (SIZE (1..maxNrofSL-QFIs-r16)) OF SL-QoS-Profile-r16, sl-MappedQoS-FlowsListDedicated-r16 SL-MappedQoS-FlowsListDedicated-r16 } OPTIONAL, -- Need M sl-CastType-r16 ENUMERATED {broadcast, groupcast, unicast, spare1} OPTIONAL, -- Need M ... } SL-MappedQoS-FlowsListDedicated-r16 ::= SEQUENCE { sl-MappedQoS-FlowsToAddList-r16 SEQUENCE (SIZE (1..maxNrofSL-QFIs-r16)) OF SL-QoS-FlowIdentity-r16 OPTIONAL, -- Need N sl-MappedQoS-FlowsToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofSL-QFIs-r16)) OF SL-QoS-FlowIdentity-r16 OPTIONAL -- Need N } -- TAG-SL-SDAP-CONFIG-STOP -- ASN1STOP
The IE SL-SyncConfig specifies the configuration information concerning reception of synchronisation signals from neighbouring cells as well as concerning the transmission of synchronisation signals for sidelink communication.
-- ASN1START -- TAG-SL-SYNCCONFIG-START SL-SyncConfigList-r16 ::= SEQUENCE (SIZE (1..maxSL-SyncConfig-r16)) OF SL-SyncConfig-r16 SL-SyncConfig-r16 ::= SEQUENCE { sl-SyncRefMinHyst-r16 ENUMERATED {dB0, dB3, dB6, dB9, dB12} OPTIONAL, -- Need R sl-SyncRefDiffHyst-r16 ENUMERATED {dB0, dB3, dB6, dB9, dB12, dBinf} OPTIONAL, -- Need R sl-filterCoefficient-r16 FilterCoefficient OPTIONAL, -- Need R sl-SSB-TimeAllocation1-r16 SL-SSB-TimeAllocation-r16 OPTIONAL, -- Need R sl-SSB-TimeAllocation2-r16 SL-SSB-TimeAllocation-r16 OPTIONAL, -- Need R sl-SSB-TimeAllocation3-r16 SL-SSB-TimeAllocation-r16 OPTIONAL, -- Need R sl-SSID-r16 INTEGER (0..671) OPTIONAL, -- Need R txParameters-r16 SEQUENCE { syncTxThreshIC-r16 SL-RSRP-Range-r16 OPTIONAL, -- Need R syncTxThreshOoC-r16 SL-RSRP-Range-r16 OPTIONAL, -- Need R syncInfoReserved-r16 BIT STRING (SIZE (2)) OPTIONAL -- Need R }, gnss-Sync-r16 ENUMERATED {true} OPTIONAL, -- Need R ... } SL-RSRP-Range-r16 ::= INTEGER (0..13) SL-SSB-TimeAllocation-r16 ::= SEQUENCE { sl-NumSSB-WithinPeriod-r16 ENUMERATED {n1, n2, n4, n8, n16, n32, n64} OPTIONAL, -- Need R sl-TimeOffsetSSB-r16 INTEGER (0..1279) OPTIONAL, -- Need R sl-TimeInterval-r16 INTEGER (0..639) OPTIONAL -- Need R } -- TAG-SL-SYNCCONFIG-STOP -- ASN1STOP
IE SL-Thres-RSRP-List indicates a threshold used for sensing based UE autonomous resource selection (see TS 38.215 [9]). A resource is excluded if it is indicated or reserved by a decoded SCI and PSSCH/PSCCH RSRP in the associated data resource is above the threshold defined by IE SL-Thres-RSRP-List. Value 0 corresponds to minus infinity dBm, value 1 corresponds to -128dBm, value 2 corresponds to -126dBm, value n corresponds to (-128 + (n-1)*2) dBm and so on, value 66 corresponds to infinity dBm.
-- ASN1START -- TAG-SL-THRES-RSRP-LIST-START SL-Thres-RSRP-List-r16 ::= SEQUENCE (SIZE (64)) OF SL-Thres-RSRP-r16 SL-Thres-RSRP-r16 ::= INTEGER (0..66) -- TAG-SL-THRES-RSRP-LIST-STOP -- ASN1STOP
The IE SL-TxPower is used to limit the UE's sidelink transmission power on a carrier frequency. The unit is dBm. Value minusinfinity corresponds to –infinity.
SL-ScheduledConfigfield descriptions |
---|
sl-CS-RNTI Indicate the RNTI used to scramble CRC of DCI format 3_0, see TS 38.321 [3]. |
sl-DCI-ToSL-Trans Indicate the time gap between DCI reception and the first sidelink transmission scheduled by the DCI (see TS 38.214 [19], clause 8.1.2.1). Value 1 included in this field corresponds to 1 slot, value 2 corresponds to 2 slots and so on, based on the numerology of sidelink BWP. |
sl-PSFCH-ToPUCCH For dynamic grant and configured grant type 2, this field configures the values (in number of slot lengths) of the PSFCH to PUCCH gap. The field PSFCH-to-HARQ_feedback timing indicator in DCI format 3_0 selects one of the configured values of the PSFCH to PUCCH gap. |
sl-RNTI Indicate the SL-RNTI used for monitoring the network scheduling to transmit NR sidelink communication (i.e. the mode 1). |
MAC-MainConfigSL field descriptions |
---|
sl-BSR-Config This field is to configure the sidelink buffer status report. |
sl-PrioritizationThres Indicates the SL priority threshold, which is used to determine whether SL TX is prioritized over UL TX, as specified in TS 38.321 [3]. Network does not configure the sl-PrioritizationThres and the ul-PrioritizationThres to the UE separately. |
ul-PrioritizationThres Indicates the UL priority threshold, which is used to determine whether SL TX is prioritized over UL TX, as specified in TS 38.321 [3]. Network does not configure the sl-PrioritizationThres and the ul-PrioritizationThres to the UE separately. |
SL-SDAP-Config field descriptions |
---|
sl-DefaultRB Indicates whether or not this is the default sidelink DRB for this NR sidelink communication transmission destination. Among all configured instances of SL-SDAP-Configfor this destination, this field shall be set to true in at most one instance of SL-SDAP-Config and to false in all other instances. |
sl-MappedQoS-Flows Indicates QoS flows to be mapped to the sidelink DRB. If the field is included in dedicated signalling, it is set to sl-MappedQoS-FlowsListDedicated; otherwise, it is set to sl-MappedQoS-FlowsList. |
sl-MappedQoS-FlowsList Indicates the list of QoS profilesof the NR sidelink communication transmission destination mapped to this sidelink DRB. |
sl-MappedQoS-FlowsToAddList Indicates the list of SL QoS flows ID of the NR sidelink communication transmission destination to be additionally mapped to this sidelink DRB. |
sl-MappedQoS-FlowsToReleaseList Indicates the list of SL QoS flows ID of the NR sidelink communication transmission destination to be released from existing QoS flow to SLRB mapping of this sidelink DRB. |
sl-SDAP-Header Indicates whether or not a SDAP header is present on this sidelink DRB. The field cannot be changed after a sidelink DRB is established. This field is set to present if the field sl-DefaultRB is set to true. |
SL-SyncConfig field descriptions |
---|
gnss-Sync If configured, the synchronization configuration is used for SLSS transmission/reception when the UE is synchronized to GNSS. If not configured, the synchronization configuration is used for SLSS transmission/reception when the UE is synchronized to eNB/gNB. |
sl-SyncRefMinHyst Hysteresis when evaluating a SyncRef UE using absolute comparison. |
sl-SyncRefDiffHyst Hysteresis when evaluating a SyncRef UE using relative comparison. |
sl-NumSSB-WithinPeriod Indicates the number of sidelink SSB transmissions within one sidelink SSB period. The applicable values are related to the subcarrier spacing and frequency as follows: FR1, SCS = 15 kHz: 1 FR1, SCS = 30 kHz: 1, 2 FR1, SCS = 60 kHz: 1, 2, 4 FR2, SCS = 60 kHz: 1, 2, 4, 8, 16, 32 FR2, SCS = 120 kHz: 1, 2, 4, 8, 16, 32, 64 |
sl-TimeOffsetSSB Indicates the slot offset from the start of sidelink SSB period to the first sidelink SSB. |
sl-TimeInterval Indicates the slot interval between neighboring sidelink SSBs. This value is applicable when there are more than one sidelink SSBs within one sidelink SSB period. |
sl-SSID Indicates the ID of sidelink synchronization signal associated with different synchronization priorities. |
syncInfoReserved Reserved for future use. |
syncTxThreshIC, syncTxThreshOoC Indicates the thresholds used while in coverage and out of coverage, respectively. Value 0 corresponds to -infinity, value 1 to -115 dBm, value 2 to -110 dBm, and so on (i.e. in steps of 5 dBm) until value 12, which corresponds to -60 dBm, while value 13 corresponds to +infinity. |
The IE SL-TypeTxSync indicates the synchronization reference type.
IE SL-UE-SelectedConfig specifies sidelink communication configurations used for UE autonomous resource selection.
-- ASN1START -- TAG-SL-UE-SELECTEDCONFIG-START SL-UE-SelectedConfig-r16 ::= SEQUENCE {sl-PSSCH-TxConfigList-r16Indicates PSSCH TX parameters such as MCS, sub-channel number, retransmission number, associated to different UE absolute speeds anddifferent synchronization reference types for UE autonomous resource selection.SL-PSSCH-TxConfigList-r16 OPTIONAL, -- Need Rsl-ProbResourceKeep-r16Indicates the probability with which the UE keeps the current resource when the resource reselection counter reaches zero for sensing based UE autonomous resource selection (see TS 38.321 [3]).ENUMERATED {v0, v0dot2, v0dot4, v0dot6, v0dot8} OPTIONAL, -- Need Rsl-ReselectAfter-r16Indicates the number of consecutive skipped transmissions before triggering resource reselection for sidelink communication (see TS 38.321 [3]).ENUMERATED {n1, n2, n3, n4, n5, n6, n7, n8, n9} OPTIONAL, -- Need R sl-CBR-CommonTxConfigList-r16 SL-CBR-CommonTxConfigList-r16 OPTIONAL, -- Need Rul-PrioritizationThres-r16Indicates the UL priority threshold, which is used to determine whether SL TX is prioritized over UL TX, as specified in TS 38.321 [3]. Network does not configure the sl-PrioritizationThres and the ul-PrioritizationThres to the UE separately.INTEGER (1..16) OPTIONAL, -- Need Rsl-PrioritizationThres-r16Indicates the SL priority threshold, which is used to determine whether SL TX is prioritized over UL TX, as specified in TS 38.321 [3]. Network does not configure the sl-PrioritizationThres and the ul-PrioritizationThres to the UE separately.INTEGER (1..8) OPTIONAL, -- Need R ... } -- TAG-SL-UE-SELECTEDCONFIG-STOP -- ASN1STOP
SL-UE-SelectedConfig field descriptions |
---|
sl-PrioritizationThres Indicates the SL priority threshold, which is used to determine whether SL TX is prioritized over UL TX, as specified in TS 38.321 [3]. Network does not configure the sl-PrioritizationThres and the ul-PrioritizationThres to the UE separately. |
sl-ProbResourceKeep Indicates the probability with which the UE keeps the current resource when the resource reselection counter reaches zero for sensing based UE autonomous resource selection (see TS 38.321 [3]). |
sl-PSSCH-TxConfigList Indicates PSSCH TX parameters such as MCS, sub-channel number, retransmission number, associated to different UE absolute speeds anddifferent synchronization reference types for UE autonomous resource selection. |
sl-ReselectAfter Indicates the number of consecutive skipped transmissions before triggering resource reselection for sidelink communication (see TS 38.321 [3]). |
ul-PrioritizationThres Indicates the UL priority threshold, which is used to determine whether SL TX is prioritized over UL TX, as specified in TS 38.321 [3]. Network does not configure the sl-PrioritizationThres and the ul-PrioritizationThres to the UE separately. |
The IE SL-ZoneConfig is used to configure the zone ID related parameters.
SL-ZoneConfig field descriptions |
---|
sl-ZoneLength Indicates the length of each geographic zone. |
The IE SLRB-Uu-ConfigIndex is used to identify a sidelink DRB configuration from the network side.
maxAI-DCI-PayloadSize-r16 INTEGER ::= 128 --Maximum size of the DCI payload scrambled with ai-RNTI |
maxAI-DCI-PayloadSize-1-r16 INTEGER ::= 127 --Maximum size of the DCI payload scrambled with ai-RNTI minus 1 |
maxBandComb INTEGER ::= 65536 -- Maximum number of DL band combinations |
maxBandsUTRA-FDD-r16 INTEGER ::= 64 -- Maximum number of bands listed in UTRA-FDD UE caps |
maxBH-RLC-ChannelID-r16 INTEGER ::= 65536 -- Maximum value of BH RLC Channel ID |
maxBT-IdReport-r16 INTEGER ::= 32 -- Maximum number of Bluetooth IDs to report |
maxBT-Name-r16 INTEGER ::= 4 -- Maximum number of Bluetooth name |
maxCAG-Cell-r16 INTEGER ::= 16 -- Maximum number of NR CAG cell ranges in SIB3, SIB4 |
maxTwoPUCCH-Grp-ConfigList-r16 INTEGER ::= 32 -- Maximum number of supported configuration(s) of {primary PUCCH group |
-- config, secondary PUCCH group config} |
maxCBR-Config-r16 INTEGER ::= 8 -- Maximum number of CBR range configurations for sidelink communication |
-- congestion control |
maxCBR-Config-1-r16 INTEGER ::= 7 -- Maximum number of CBR range configurations for sidelink communication |
-- congestion control minus 1 |
maxCBR-Level-r16 INTEGER ::= 16 -- Maximum number of CBR levels |
maxCBR-Level-1-r16 INTEGER ::= 15 -- Maximum number of CBR levels minus 1 |
maxCellBlack INTEGER ::= 16 -- Maximum number of NR blacklisted cell ranges in SIB3, SIB4 |
maxCellGroupings-r16 INTEGER ::= 32 -- Maximum number of cell groupings for NR-DC |
maxCellHistory-r16 INTEGER ::= 16 -- Maximum number of visited cells reported |
maxCellInter INTEGER ::= 16 -- Maximum number of inter-Freq cells listed in SIB4 |
maxCellIntra INTEGER ::= 16 -- Maximum number of intra-Freq cells listed in SIB3 |
maxCellMeasEUTRA INTEGER ::= 32 -- Maximum number of cells in E-UTRAN |
maxCellMeasIdle-r16 INTEGER ::= 8 -- Maximum number of cells per carrier for idle/inactive measurements |
maxCellMeasUTRA-FDD-r16 INTEGER ::= 32 -- Maximum number of cells in FDD UTRAN |
maxCarrierTypePairList-r16 INTEGER ::= 16 -- Maximum number of supported carrier type pair of {carrier type on which |
-- CSI measurement is performed, carrier type on which CSI reporting is |
-- performed} for CSI reporting cross PUCCH group |
maxCellWhite INTEGER ::= 16 -- Maximum number of NR whitelisted cell ranges in SIB3, SIB4 |
maxEARFCN INTEGER ::= 262143 -- Maximum value of E-UTRA carrier frequency |
maxEUTRA-CellBlack INTEGER ::= 16 -- Maximum number of E-UTRA blacklisted physical cell identity ranges |
-- in SIB5 |
maxEUTRA-NS-Pmax INTEGER ::= 8 -- Maximum number of NS and P-Max values per band |
maxLogMeasReport-r16 INTEGER ::= 520 -- Maximum number of entries for logged measurements |
maxMultiBands INTEGER ::= 8 -- Maximum number of additional frequency bands that a cell belongs to |
maxNARFCN INTEGER ::= 3279165 -- Maximum value of NR carrier frequency |
maxNR-NS-Pmax INTEGER ::= 8 -- Maximum number of NS and P-Max values per band |
maxFreqIdle-r16 INTEGER ::= 8 -- Maximum number of carrier frequencies for idle/inactive measurements |
maxNrofServingCells INTEGER ::= 32 -- Max number of serving cells (SpCells + SCells) |
maxNrofServingCells-1 INTEGER ::= 31 -- Max number of serving cells (SpCells + SCells) minus 1 |
maxNrofAggregatedCellsPerCellGroup INTEGER ::= 16 |
maxNrofAggregatedCellsPerCellGroupMinus4-r16 INTEGER ::= 12 |
maxNrofDUCells-r16 INTEGER ::= 512 -- Max number of cells configured on the collocated IAB-DU |
maxNrofAvailabilityCombinationsPerSet-r16 INTEGER ::= 512 -- Max number of AvailabilityCombinationId used in the DCI format 2_5 |
maxNrofAvailabilityCombinationsPerSet-1-r16 INTEGER ::= 511 -- Max number of AvailabilityCombinationId used in the DCI format 2_5 minus 1 |
maxNrofSCells INTEGER ::= 31 -- Max number of secondary serving cells per cell group |
maxNrofCellMeas INTEGER ::= 32 -- Maximum number of entries in each of the cell lists in a measurement object |
maxNrofCG-SL-r16 INTEGER ::= 8 -- Max number of sidelink configured grant |
maxNrofCG-SL-1-r16 INTEGER ::= 7 -- Max number of sidelink configured grant minus 1 |
maxNrofSS-BlocksToAverage INTEGER ::= 16 -- Max number for the (max) number of SS blocks to average to determine cell measurement |
maxNrofCondCells-r16 INTEGER ::= 8 -- Max number of conditional candidate SpCells |
maxNrofCSI-RS-ResourcesToAverage INTEGER ::= 16 -- Max number for the (max) number of CSI-RS to average to determine cell measurement |
maxNrofDL-Allocations INTEGER ::= 16 -- Maximum number of PDSCH time domain resource allocations |
maxNrofSR-ConfigPerCellGroup INTEGER ::= 8 -- Maximum number of SR configurations per cell group |
maxLCG-ID INTEGER ::= 7 -- Maximum value of LCG ID |
maxLC-ID INTEGER ::= 32 -- Maximum value of Logical Channel ID |
maxLC-ID-Iab-r16 INTEGER ::= 65855 -- Maximum value of BH Logical Channel ID extension |
maxLTE-CRS-Patterns-r16 INTEGER ::= 3 -- Maximum number of additional LTE CRS rate matching patterns |
maxNrofTAGs INTEGER ::= 4 -- Maximum number of Timing Advance Groups |
maxNrofTAGs-1 INTEGER ::= 3 -- Maximum number of Timing Advance Groups minus 1 |
maxNrofBWPs INTEGER ::= 4 -- Maximum number of BWPs per serving cell |
maxNrofCombIDC INTEGER ::= 128 -- Maximum number of reported MR-DC combinations for IDC |
maxNrofSymbols-1 INTEGER ::= 13 -- Maximum index identifying a symbol within a slot (14 symbols, indexed from 0..13) |
maxNrofSlots INTEGER ::= 320 -- Maximum number of slots in a 10 ms period |
maxNrofSlots-1 INTEGER ::= 319 -- Maximum number of slots in a 10 ms period minus 1 |
maxNrofPhysicalResourceBlocks INTEGER ::= 275 -- Maximum number of PRBs |
maxNrofPhysicalResourceBlocks-1 INTEGER ::= 274 -- Maximum number of PRBs minus 1 |
maxNrofPhysicalResourceBlocksPlus1 INTEGER ::= 276 -- Maximum number of PRBs plus 1 |
maxNrofControlResourceSets INTEGER ::= 12 -- Max number of CoReSets configurable on a serving cell |
maxNrofControlResourceSets-1 INTEGER ::= 11 -- Max number of CoReSets configurable on a serving cell minus 1 |
maxNrofControlResourceSets-1-r16 INTEGER ::= 15 -- Max number of CoReSets configurable on a serving cell extended in minus 1 |
maxNrofCoresetPools-r16 INTEGER ::= 2 -- Maximum number of CORESET pools |
maxCoReSetDuration INTEGER ::= 3 -- Max number of OFDM symbols in a control resource set |
maxNrofSearchSpaces-1 INTEGER ::= 39 -- Max number of Search Spaces minus 1 |
maxSFI-DCI-PayloadSize INTEGER ::= 128 -- Max number payload of a DCI scrambled with SFI-RNTI |
maxSFI-DCI-PayloadSize-1 INTEGER ::= 127 -- Max number payload of a DCI scrambled with SFI-RNTI minus 1 |
maxIAB-IP-Address-r16 INTEGER ::= 32 -- Max number of assigned IP addresses |
maxINT-DCI-PayloadSize INTEGER ::= 126 -- Max number payload of a DCI scrambled with INT-RNTI |
maxINT-DCI-PayloadSize-1 INTEGER ::= 125 -- Max number payload of a DCI scrambled with INT-RNTI minus 1 |
maxNrofRateMatchPatterns INTEGER ::= 4 -- Max number of rate matching patterns that may be configured |
maxNrofRateMatchPatterns-1 INTEGER ::= 3 -- Max number of rate matching patterns that may be configured minus 1 |
maxNrofRateMatchPatternsPerGroup INTEGER ::= 8 -- Max number of rate matching patterns that may be configured in one group |
maxNrofCSI-ReportConfigurations INTEGER ::= 48 -- Maximum number of report configurations |
maxNrofCSI-ReportConfigurations-1 INTEGER ::= 47 -- Maximum number of report configurations minus 1 |
maxNrofCSI-ResourceConfigurations INTEGER ::= 112 -- Maximum number of resource configurations |
maxNrofCSI-ResourceConfigurations-1 INTEGER ::= 111 -- Maximum number of resource configurations minus 1 |
maxNrofAP-CSI-RS-ResourcesPerSet INTEGER ::= 16 |
maxNrOfCSI-AperiodicTriggers INTEGER ::= 128 -- Maximum number of triggers for aperiodic CSI reporting |
maxNrofReportConfigPerAperiodicTrigger INTEGER ::= 16 -- Maximum number of report configurations per trigger state for aperiodic reporting |
maxNrofNZP-CSI-RS-Resources INTEGER ::= 192 -- Maximum number of Non-Zero-Power (NZP) CSI-RS resources |
maxNrofNZP-CSI-RS-Resources-1 INTEGER ::= 191 -- Maximum number of Non-Zero-Power (NZP) CSI-RS resources minus 1 |
maxNrofNZP-CSI-RS-ResourcesPerSet INTEGER ::= 64 -- Maximum number of NZP CSI-RS resources per resource set |
maxNrofNZP-CSI-RS-ResourceSets INTEGER ::= 64 -- Maximum number of NZP CSI-RS resource sets per cell |
maxNrofNZP-CSI-RS-ResourceSets-1 INTEGER ::= 63 -- Maximum number of NZP CSI-RS resource sets per cell minus 1 |
maxNrofNZP-CSI-RS-ResourceSetsPerConfig INTEGER ::= 16 -- Maximum number of resource sets per resource configuration |
maxNrofNZP-CSI-RS-ResourcesPerConfig INTEGER ::= 128 -- Maximum number of resources per resource configuration |
maxNrofZP-CSI-RS-Resources INTEGER ::= 32 -- Maximum number of Zero-Power (ZP) CSI-RS resources |
maxNrofZP-CSI-RS-Resources-1 INTEGER ::= 31 -- Maximum number of Zero-Power (ZP) CSI-RS resources minus 1 |
maxNrofZP-CSI-RS-ResourceSets-1 INTEGER ::= 15 |
maxNrofZP-CSI-RS-ResourcesPerSet INTEGER ::= 16 |
maxNrofZP-CSI-RS-ResourceSets INTEGER ::= 16 |
maxNrofCSI-IM-Resources INTEGER ::= 32 -- Maximum number of CSI-IM resources |
maxNrofCSI-IM-Resources-1 INTEGER ::= 31 -- Maximum number of CSI-IM resources minus 1 |
maxNrofCSI-IM-ResourcesPerSet INTEGER ::= 8 -- Maximum number of CSI-IM resources per set |
maxNrofCSI-IM-ResourceSets INTEGER ::= 64 -- Maximum number of NZP CSI-IM resource sets per cell |
maxNrofCSI-IM-ResourceSets-1 INTEGER ::= 63 -- Maximum number of NZP CSI-IM resource sets per cell minus 1 |
maxNrofCSI-IM-ResourceSetsPerConfig INTEGER ::= 16 -- Maximum number of CSI IM resource sets per resource configuration |
maxNrofCSI-SSB-ResourcePerSet INTEGER ::= 64 -- Maximum number of SSB resources in a resource set |
maxNrofCSI-SSB-ResourceSets INTEGER ::= 64 -- Maximum number of CSI SSB resource sets per cell |
maxNrofCSI-SSB-ResourceSets-1 INTEGER ::= 63 -- Maximum number of CSI SSB resource sets per cell minus 1 |
maxNrofCSI-SSB-ResourceSetsPerConfig INTEGER ::= 1 -- Maximum number of CSI SSB resource sets per resource configuration |
maxNrofFailureDetectionResources INTEGER ::= 10 -- Maximum number of failure detection resources |
maxNrofFailureDetectionResources-1 INTEGER ::= 9 -- Maximum number of failure detection resources minus 1 |
maxNrofFreqSL-r16 INTEGER ::= 8 -- Maximum number of carrier frequency for NR sidelink communication |
maxNrofSL-BWPs-r16 INTEGER ::= 4 -- Maximum number of BWP for NR sidelink communication |
maxFreqSL-EUTRA-r16 INTEGER ::= 8 -- Maximum number of EUTRA anchor carrier frequency for NR sidelink communication |
maxNrofSL-MeasId-r16 INTEGER ::= 64 -- Maximum number of sidelink measurement identity (RSRP) per destination |
maxNrofSL-ObjectId-r16 INTEGER ::= 64 -- Maximum number of sidelink measurement objects (RSRP) per destination |
maxNrofSL-ReportConfigId-r16 INTEGER ::= 64 -- Maximum number of sidelink measurement reporting configuration(RSRP) per destination |
maxNrofSL-PoolToMeasureNR-r16 INTEGER ::= 8 -- Maximum number of resource pool for NR sidelink measurement to measure for |
-- each measurement object (for CBR) |
maxFreqSL-NR-r16 INTEGER ::= 8 -- Maximum number of NR anchor carrier frequency for NR sidelink communication |
maxNrofSL-QFIs-r16 INTEGER ::= 2048 -- Maximum number of QoS flow for NR sidelink communication per UE |
maxNrofSL-QFIsPerDest-r16 INTEGER ::= 64 -- Maximum number of QoS flow per destination for NR sidelink communication |
maxNrofObjectId INTEGER ::= 64 -- Maximum number of measurement objects |
maxNrofPageRec INTEGER ::= 32 -- Maximum number of page records |
maxNrofPCI-Ranges INTEGER ::= 8 -- Maximum number of PCI ranges |
maxPLMN INTEGER ::= 12 -- Maximum number of PLMNs broadcast and reported by UE at establishment |
maxNrofCSI-RS-ResourcesRRM INTEGER ::= 96 -- Maximum number of CSI-RS resources per cell for an RRM measurement object |
maxNrofCSI-RS-ResourcesRRM-1 INTEGER ::= 95 -- Maximum number of CSI-RS resources per cell for an RRM measurement object minus 1 |
maxNrofMeasId INTEGER ::= 64 -- Maximum number of configured measurements |
maxNrofQuantityConfig INTEGER ::= 2 -- Maximum number of quantity configurations |
maxNrofCSI-RS-CellsRRM INTEGER ::= 96 -- Maximum number of cells with CSI-RS resources for an RRM measurement object |
maxNrofSL-Dest-r16 INTEGER ::= 32 -- Maximum number of destination for NR sidelink communication |
maxNrofSL-Dest-1-r16 INTEGER ::= 31 -- Highest index of destination for NR sidelink communication |
maxNrofSLRB-r16 INTEGER ::= 512 -- Maximum number of radio bearer for NR sidelink communication per UE |
maxSL-LCID-r16 INTEGER ::= 512 -- Maximum number of RLC bearer for NR sidelink communication per UE |
maxSL-SyncConfig-r16 INTEGER ::= 16 -- Maximum number of sidelink Sync configurations |
maxNrofRXPool-r16 INTEGER ::= 16 -- Maximum number of Rx resource pool for NR sidelink communication |
maxNrofTXPool-r16 INTEGER ::= 8 -- Maximum number of Tx resource pool for NR sidelink communication |
maxNrofPoolID-r16 INTEGER ::= 16 -- Maximum index of resource pool for NR sidelink communication |
maxNrofSRS-PathlossReferenceRS-r16 INTEGER ::= 64 -- Maximum number of RSs used as pathloss reference for SRS power control. |
maxNrofSRS-PathlossReferenceRS-1-r16 INTEGER ::= 63 -- Maximum number of RSs used as pathloss reference for SRS power control minus 1. |
maxNrofSRS-ResourceSets INTEGER ::= 16 -- Maximum number of SRS resource sets in a BWP. |
maxNrofSRS-ResourceSets-1 INTEGER ::= 15 -- Maximum number of SRS resource sets in a BWP minus 1. |
maxNrofSRS-PosResourceSets-r16 INTEGER ::= 16 -- Maximum number of SRS Positioning resource sets in a BWP. |
maxNrofSRS-PosResourceSets-1-r16 INTEGER ::= 15 -- Maximum number of SRS Positioning resource sets in a BWP minus 1. |
maxNrofSRS-Resources INTEGER ::= 64 -- Maximum number of SRS resources. |
maxNrofSRS-Resources-1 INTEGER ::= 63 -- Maximum number of SRS resources minus 1. |
maxNrofSRS-PosResources-r16 INTEGER ::= 64 -- Maximum number of SRS Positioning resources. |
maxNrofSRS-PosResources-1-r16 INTEGER ::= 63 -- Maximum number of SRS Positioning resources minus 1. |
maxNrofSRS-ResourcesPerSet INTEGER ::= 16 -- Maximum number of SRS resources in an SRS resource set |
maxNrofSRS-TriggerStates-1 INTEGER ::= 3 -- Maximum number of SRS trigger states minus 1, i.e., the largest code point. |
maxNrofSRS-TriggerStates-2 INTEGER ::= 2 -- Maximum number of SRS trigger states minus 2. |
maxRAT-CapabilityContainers INTEGER ::= 8 -- Maximum number of interworking RAT containers (incl NR and MRDC) |
maxSimultaneousBands INTEGER ::= 32 -- Maximum number of simultaneously aggregated bands |
maxULTxSwitchingBandPairs INTEGER ::= 32 -- Maximum number of band pairs supporting dynamic UL Tx switching in a band combination |
maxNrofSlotFormatCombinationsPerSet INTEGER ::= 512 -- Maximum number of Slot Format Combinations in a SF-Set. |
maxNrofSlotFormatCombinationsPerSet-1 INTEGER ::= 511 -- Maximum number of Slot Format Combinations in a SF-Set minus 1. |
maxNrofTrafficPattern-r16 INTEGER ::= 8 -- Maximum number of Traffic Pattern for NR sidelink communication. |
maxNrofPUCCH-Resources INTEGER ::= 128 |
maxNrofPUCCH-Resources-1 INTEGER ::= 127 |
maxNrofPUCCH-ResourceSets INTEGER ::= 4 -- Maximum number of PUCCH Resource Sets |
maxNrofPUCCH-ResourceSets-1 INTEGER ::= 3 -- Maximum number of PUCCH Resource Sets minus 1. |
maxNrofPUCCH-ResourcesPerSet INTEGER ::= 32 -- Maximum number of PUCCH Resources per PUCCH-ResourceSet |
maxNrofPUCCH-P0-PerSet INTEGER ::= 8 -- Maximum number of P0-pucch present in a p0-pucch set |
maxNrofPUCCH-PathlossReferenceRSs INTEGER ::= 4 -- Maximum number of RSs used as pathloss reference for PUCCH power control. |
maxNrofPUCCH-PathlossReferenceRSs-1 INTEGER ::= 3 -- Maximum number of RSs used as pathloss reference for PUCCH power control minus 1. |
maxNrofPUCCH-PathlossReferenceRSs-r16 INTEGER ::= 64 -- Maximum number of RSs used as pathloss reference for PUCCH power control extended. |
maxNrofPUCCH-PathlossReferenceRSs-1-r16 INTEGER ::= 63 -- Maximum number of RSs used as pathloss reference for PUCCH power control |
-- minus 1 extended. |
maxNrofPUCCH-PathlossReferenceRSsDiff-r16 INTEGER ::= 60 -- Difference between the extended maximum and the non-extended maximum |
maxNrofPUCCH-ResourceGroups-r16 INTEGER ::= 4 -- Maximum number of PUCCH resources groups. |
maxNrofPUCCH-ResourcesPerGroup-r16 INTEGER ::= 128 -- Maximum number of PUCCH resources in a PUCCH group. |
maxNrofMultiplePUSCHs-r16 INTEGER ::= 8 -- Maximum number of multiple PUSCHs in PUSCH TDRA list |
maxNrofP0-PUSCH-AlphaSets INTEGER ::= 30 -- Maximum number of P0-pusch-alpha-sets (see TS 38.213 [13], clause 7.1) |
maxNrofP0-PUSCH-AlphaSets-1 INTEGER ::= 29 -- Maximum number of P0-pusch-alpha-sets minus 1 (see TS 38.213 [13], clause 7.1) |
maxNrofPUSCH-PathlossReferenceRSs INTEGER ::= 4 -- Maximum number of RSs used as pathloss reference for PUSCH power control. |
maxNrofPUSCH-PathlossReferenceRSs-1 INTEGER ::= 3 -- Maximum number of RSs used as pathloss reference for PUSCH power control minus 1. |
maxNrofPUSCH-PathlossReferenceRSs-r16 INTEGER ::= 64 -- Maximum number of RSs used as pathloss reference for PUSCH power control extended |
maxNrofPUSCH-PathlossReferenceRSs-1-r16 INTEGER ::= 63 -- Maximum number of RSs used as pathloss reference for PUSCH power control |
-- extended minus 1 |
maxNrofPUSCH-PathlossReferenceRSsDiff-r16 INTEGER ::= 60 -- Difference between maxNrofPUSCH-PathlossReferenceRSs-r16 and |
-- maxNrofPUSCH-PathlossReferenceRSs |
maxNrofNAICS-Entries INTEGER ::= 8 -- Maximum number of supported NAICS capability set |
maxBands INTEGER ::= 1024 -- Maximum number of supported bands in UE capability. |
maxBandsMRDC INTEGER ::= 1280 |
maxBandsEUTRA INTEGER ::= 256 |
maxCellReport INTEGER ::= 8 |
maxDRB INTEGER ::= 29 -- Maximum number of DRBs (that can be added in DRB-ToAddModList). |
maxFreq INTEGER ::= 8 -- Max number of frequencies. |
maxFreqLayers INTEGER ::= 4 -- Max number of frequency layers. |
maxFreqIDC-r16 INTEGER ::= 128 -- Max number of frequencies for IDC indication. |
maxCombIDC-r16 INTEGER ::= 128 -- Max number of reported UL CA for IDC indication. |
maxFreqIDC-MRDC INTEGER ::= 32 -- Maximum number of candidate NR frequencies for MR-DC IDC indication |
maxNrofCandidateBeams INTEGER ::= 16 -- Max number of PRACH-ResourceDedicatedBFR in BFR config. |
maxNrofCandidateBeams-r16 INTEGER ::= 64 -- Max number of candidate beam resources in BFR config. |
maxNrofCandidateBeamsExt-r16 INTEGER ::= 48 -- Max number of PRACH-ResourceDedicatedBFR in the CandidateBeamRSListExt |
maxNrofPCIsPerSMTC INTEGER ::= 64 -- Maximum number of PCIs per SMTC. |
maxNrofQFIs INTEGER ::= 64 |
maxNrofResourceAvailabilityPerCombination-r16 INTEGER ::= 256 |
maxNrOfSemiPersistentPUSCH-Triggers INTEGER ::= 64 -- Maximum number of triggers for semi persistent reporting on PUSCH |
maxNrofSR-Resources INTEGER ::= 8 -- Maximum number of SR resources per BWP in a cell. |
maxNrofSlotFormatsPerCombination INTEGER ::= 256 |
maxNrofSpatialRelationInfos INTEGER ::= 8 |
maxNrofSpatialRelationInfos-plus-1 INTEGER ::= 9 |
maxNrofSpatialRelationInfos-r16 INTEGER ::= 64 |
maxNrofSpatialRelationInfosDiff-r16 INTEGER ::= 56 -- Difference between maxNrofSpatialRelationInfos-r16 and maxNrofSpatialRelationInfos |
maxNrofIndexesToReport INTEGER ::= 32 |
maxNrofIndexesToReport2 INTEGER ::= 64 |
maxNrofSSBs-r16 INTEGER ::= 64 -- Maximum number of SSB resources in a resource set. |
maxNrofSSBs-1 INTEGER ::= 63 -- Maximum number of SSB resources in a resource set minus 1. |
maxNrofS-NSSAI INTEGER ::= 8 -- Maximum number of S-NSSAI. |
maxNrofTCI-StatesPDCCH INTEGER ::= 64 |
maxNrofTCI-States INTEGER ::= 128 -- Maximum number of TCI states. |
maxNrofTCI-States-1 INTEGER ::= 127 -- Maximum number of TCI states minus 1. |
maxNrofUL-Allocations INTEGER ::= 16 -- Maximum number of PUSCH time domain resource allocations. |
maxQFI INTEGER ::= 63 |
maxRA-CSIRS-Resources INTEGER ::= 96 |
maxRA-OccasionsPerCSIRS INTEGER ::= 64 -- Maximum number of RA occasions for one CSI-RS |
maxRA-Occasions-1 INTEGER ::= 511 -- Maximum number of RA occasions in the system |
maxRA-SSB-Resources INTEGER ::= 64 |
maxSCSs INTEGER ::= 5 |
maxSecondaryCellGroups INTEGER ::= 3 |
maxNrofServingCellsEUTRA INTEGER ::= 32 |
maxMBSFN-Allocations INTEGER ::= 8 |
maxNrofMultiBands INTEGER ::= 8 |
maxCellSFTD INTEGER ::= 3 -- Maximum number of cells for SFTD reporting |
maxReportConfigId INTEGER ::= 64 |
maxNrofCodebooks INTEGER ::= 16 -- Maximum number of codebooks supported by the UE |
maxNrofCSI-RS-ResourcesExt-r16 INTEGER ::= 16 -- Maximum number of codebook resources supported by the UE for eType2/Codebook combo |
maxNrofCSI-RS-Resources INTEGER ::= 7 -- Maximum number of codebook resources supported by the UE |
maxNrofCSI-RS-ResourcesAlt-r16 INTEGER ::= 512 -- Maximum number of alternative codebook resources supported by the UE |
maxNrofCSI-RS-ResourcesAlt-1-r16 INTEGER ::= 511 -- Maximum number of alternative codebook resources supported by the UE minus 1 |
maxNrofSRI-PUSCH-Mappings INTEGER ::= 16 |
maxNrofSRI-PUSCH-Mappings-1 INTEGER ::= 15 |
maxSIB INTEGER::= 32 -- Maximum number of SIBs |
maxSI-Message INTEGER::= 32 -- Maximum number of SI messages |
maxPO-perPF INTEGER ::= 4 -- Maximum number of paging occasion per paging frame |
maxAccessCat-1 INTEGER ::= 63 -- Maximum number of Access Categories minus 1 |
maxBarringInfoSet INTEGER ::= 8 -- Maximum number of access control parameter sets |
maxCellEUTRA INTEGER ::= 8 -- Maximum number of E-UTRA cells in SIB list |
maxEUTRA-Carrier INTEGER ::= 8 -- Maximum number of E-UTRA carriers in SIB list |
maxPLMNIdentities INTEGER ::= 8 -- Maximum number of PLMN identities in RAN area configurations |
maxDownlinkFeatureSets INTEGER ::= 1024 -- (for NR DL) Total number of FeatureSets (size of the pool) |
maxUplinkFeatureSets INTEGER ::= 1024 -- (for NR UL) Total number of FeatureSets (size of the pool) |
maxEUTRA-DL-FeatureSets INTEGER ::= 256 -- (for E-UTRA) Total number of FeatureSets (size of the pool) |
maxEUTRA-UL-FeatureSets INTEGER ::= 256 -- (for E-UTRA) Total number of FeatureSets (size of the pool) |
maxFeatureSetsPerBand INTEGER ::= 128 -- (for NR) The number of feature sets associated with one band. |
maxPerCC-FeatureSets INTEGER ::= 1024 -- (for NR) Total number of CC-specific FeatureSets (size of the pool) |
maxFeatureSetCombinations INTEGER ::= 1024 -- (for MR-DC/NR)Total number of Feature set combinations (size of the pool) |
maxInterRAT-RSTD-Freq INTEGER ::= 3 |
maxHRNN-Len-r16 INTEGER ::= 48 -- Maximum length of HRNNs |
maxNPN-r16 INTEGER ::= 12 -- Maximum number of NPNs broadcast and reported by UE at establishment |
maxNrOfMinSchedulingOffsetValues-r16 INTEGER ::= 2 -- Maximum number of min. scheduling offset (K0/K2) configurations |
maxK0-SchedulingOffset-r16 INTEGER ::= 16 -- Maximum number of slots configured as min. scheduling offset (K0) |
maxK2-SchedulingOffset-r16 INTEGER ::= 16 -- Maximum number of slots configured as min. scheduling offset (K2) |
maxDCI-2-6-Size-r16 INTEGER ::= 140 -- Maximum size of DCI format 2-6 |
maxDCI-2-6-Size-1-r16 INTEGER ::= 139 -- Maximum DCI format 2-6 size minus 1 |
maxNrofUL-Allocations-r16 INTEGER ::= 64 -- Maximum number of PUSCH time domain resource allocations |
maxNrofP0-PUSCH-Set-r16 INTEGER ::= 2 -- Maximum number of P0 PUSCH set(s) |
maxOnDemandSIB-r16 INTEGER ::= 8 -- Maximum number of SIB(s) that can be requested on-demand |
maxOnDemandPosSIB-r16 INTEGER ::= 32 -- Maximum number of posSIB(s) that can be requested on-demand |
maxCI-DCI-PayloadSize-r16 INTEGER ::= 126 -- Maximum number of the DCI size for CI |
maxCI-DCI-PayloadSize-1-r16 INTEGER ::= 125 -- Maximum number of the DCI size for CI minus 1 |
maxWLAN-Id-Report-r16 INTEGER ::= 32 -- Maximum number of WLAN IDs to report |
maxWLAN-Name-r16 INTEGER ::= 4 -- Maximum number of WLAN name |
maxRAReport-r16 INTEGER ::= 8 -- Maximum number of RA procedures information to be included in the RA report |
maxTxConfig-r16 INTEGER ::= 64 -- Maximum number of sidelink transmission parameters configurations |
maxTxConfig-1-r16 INTEGER ::= 63 -- Maximum number of sidelink transmission parameters configurations minus 1 |
maxPSSCH-TxConfig-r16 INTEGER ::= 16 -- Maximum number of PSSCH TX configurations |
maxNrofCLI-RSSI-Resources-r16 INTEGER ::= 64 -- Maximum number of CLI-RSSI resources for UE |
maxNrofCLI-RSSI-Resources-1-r16 INTEGER ::= 63 -- Maximum number of CLI-RSSI resources for UE minus 1 |
maxNrofCLI-SRS-Resources-r16 INTEGER ::= 32 -- Maximum number of SRS resources for CLI measurement for UE |
maxCLI-Report-r16 INTEGER ::= 8 |
maxNrofConfiguredGrantConfig-r16 INTEGER ::= 12 -- Maximum number of configured grant configurations per BWP |
maxNrofConfiguredGrantConfig-1-r16 INTEGER ::= 11 -- Maximum number of configured grant configurations per BWP minus 1 |
maxNrofCG-Type2DeactivationState INTEGER ::= 16 -- Maximum number of deactivation state for type 2 configured grants per BWP |
maxNrofConfiguredGrantConfigMAC-1-r16 INTEGER ::= 31 -- Maximum number of configured grant configurations per MAC entity minus 1 |
maxNrofSPS-Config-r16 INTEGER ::= 8 -- Maximum number of SPS configurations per BWP |
maxNrofSPS-Config-1-r16 INTEGER ::= 7 -- Maximum number of SPS configurations per BWP minus 1 |
maxNrofSPS-DeactivationState INTEGER ::= 16 -- Maximum number of deactivation state for SPS per BWP |
maxNrofPUCCH-ResourceGroups-1-r16 INTEGER ::= 3 |
maxNrofServingCellsTCI-r16 INTEGER ::= 32 -- Maximum number of serving cells in simultaneousTCI-UpdateList |
maxNrofTxDC-TwoCarrier-r16 INTEGER ::= 64 -- Maximum number of UL Tx DC locations reported by the UE for 2CC uplink CA |
maxNrofPdcch-BlindDetectionMixed-1-r16 INTEGER ::= 7 -- Maximum number of combinations of mixed Rel-16 and Rel-15 PDCCH |
-- monitoring capabilities minus 1 |