12.2.1 Inter-carrier concurrent operation / Sidelink communication

38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification

12.2.1.1

12.2.1.2 Inter-carrier concurrent operation / Sidelink communication / RRC_IDLE / Reception

12.2.1.2.1 Test Purpose (TP)

(1)

with { UE being in RRC_IDLE state and the cell on which UE camps broadcasting SIB12 including no sl-FreqInfoList but anchor carrier configuration }

ensure that {

when { A neighbour cell on anchor carrier starts broadcasting SIB12 which includes sl-RxPool and UE is configured by upper layer to perform NR sidelink reception }

then { UE considers the anchor carrier to be the highest priority, reselects to neighbour cell on anchor carrier and is able to monitor NR sidelink transmission using the resource pool indicated by sl-RxPool in SIB12 }

}

(2)

with { UE being in RRC_IDLE state and the cell on which UE camps not broadcasting SIB12 }

ensure that {

when { UE is configured by upper layer to perform NR sidelink reception }

then { UE is able to monitor NR sidelink transmission using the resource pool indicated by sl-RxPool in pre-configuration }

}

12.2.1.2.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.304, subclause 5.2.4.1 and 5.8.2, TS 38.331 [22], subclause 5.8.7. Unless otherwise stated these are Rel-16 requirements.

[TS 38.304, clause 5.2.4.1]

Absolute priorities of different NR frequencies or inter-RAT frequencies may be provided to the UE in the system information, in the RRCRelease message, or by inheriting from another RAT at inter-RAT cell (re)selection. In the case of system information, an NR frequency or inter-RAT frequency may be listed without providing a priority (i.e. the field cellReselectionPriority is absent for that frequency). If priorities are provided in dedicated signalling, the UE shall ignore all the priorities provided in system information. If UE is in camped on any cell state, UE shall only apply the priorities provided by system information from current cell, and the UE preserves priorities provided by dedicated signalling and deprioritisationReq received in RRCRelease unless specified otherwise. When the UE in camped normally state, has only dedicated priorities other than for the current frequency, the UE shall consider the current frequency to be the lowest priority frequency (i.e. lower than any of the network configured values). If the UE is configured to perform both NR sidelink communication and V2X sidelink communication, the UE may consider the frequency providing both NR sidelink communication configuration and V2X sidelink communication configuration to be the highest priority. If the UE is configured to perform NR sidelink communication and not perform V2X communication, the UE may consider the frequency providing NR sidelink communication configuration to be the highest priority. If the UE is configured to perform V2X sidelink communication and not perform NR sidelink communication, the UE may consider the frequency providing V2X sidelink communication configuration to be the highest priority.

NOTE 1: The frequency only providing the anchor frequency configuration should not be prioritized for V2X service during cell reselection, as specified in TS 38.331[3].

NOTE 2: When UE is configured to perform NR sidelink communication or V2X sidelink communication performs cell reselection, it may consider the frequencies providing the intra-carrier and inter-carrier configuration have equal priority in cell reselection.

NOTE 3: The prioritization among the frequencies which UE considers to be the highest priority frequency is left to UE implementation.

NOTE 4: The UE is configured to perform V2X sidelink communication or NR sidelink communication, if it has the capability and is authorized for the corresponding sidelink operation.

NOTE 5: When UE is configured to perform both NR sidelink communication and V2X sidelink communication, but cannot find a frequency which can provide both NR sidelink communication configuration and V2X sidelink communication configuration, UE may consider the frequency providing either NR sidelink communication configuration or V2X sidelink communication configuration to be the highest priority.

The UE shall only perform cell reselection evaluation for NR frequencies and inter-RAT frequencies that are given in system information and for which the UE has a priority provided.

…

[TS 38.304, clause 8.2]

The requirements defined in this clause for sidelink operation apply for UEs in RRC_IDLE, RRC_INACTIVE and in RRC_CONNECTED.

When UE is interested to perform NR sidelink communication on non-serving frequency, it may perform measurements on that frequency or the frequencies which can provide inter carrier NR sidelink configuration for that frequency for cell selection and reselection purpose in accordance with TS 38.133[8]. When UE is interested to perform V2X sidelink communication on non-serving frequency, it may perform measurements on that frequency or the frequencies which can provide inter carrier V2X sidelink configuration for that frequency for cell selection and intra-frequency reselection purpose in accordance with TS 38.133[8].

If the UE detects at least one cell on the frequency which UE is configured to perform NR sidelink communication on fulfilling the S criterion in accordance with clause 8.2.1, it shall consider itself to be in-coverage for NR sidelink communication on that frequency. If the UE cannot detect any cell on that frequency meeting the S criterion, it shall consider itself to be out-of-coverage for NR sidelink communication on that frequency.

If the UE detects at least one cell on the frequency which UE is configured to perform V2X sidelink communication on fulfilling the S criterion in accordance with clause 8.2.1, it shall consider itself to be in-coverage for V2X sidelink communication on that frequency. If the UE cannot detect any cell on that frequency meeting the S criterion, it shall consider itself to be out-of-coverage for V2X sidelink communication on that frequency.

If the UE has selected a cell on a non-serving frequency for V2X sidelink communication, it shall perform additional intra-frequency reselection process to select a better cell for sidelink operation on that frequency in accordance with clause 8.2.1.

If the UE has selected a cell on a non-serving frequency for NR sidelink communication, it shall perform additional reselection process to select a better cell for sidelink operation in accordance with clause 8.2.1.

[TS 38.331, clause 5.8.7]

A UE capable of NR sidelink communication that is configured by upper layers to receive NR sidelink communication shall:

1> if the conditions for NR sidelink communication operation as defined in 5.8.2 are met:

2> if the frequency used for NR sidelink communication is included in sl-FreqInfoToAddModList in RRCReconfiguration message or sl-FreqInfoList included in SIB12:

3> if the UE is configured with sl-RxPool included in RRCReconfiguration message with reconfigurationWithSync (i.e. handover):

4> configure lower layers to monitor sidelink control information and the corresponding data using the pool of resources indicated by sl-RxPool;

3> else if the cell chosen for NR sidelink communication provides SIB12:

4> configure lower layers to monitor sidelink control information and the corresponding data using the pool of resources indicated by sl-RxPool in SIB12;

2> else:

3> configure lower layers to monitor sidelink control information and the corresponding data using the pool of resources that were preconfigured by sl-RxPool in SL-PreconfigurationNR, as defined in sub-clause 9.3;

12.2.1.2.3 Test description

12.2.1.2.3.1 Pre-test conditions

System Simulator:

– SS-NW

– NR Cell 1, NR Cell 12.

– System information combination NR-4 as defined in TS 38.508-1 [4] clause 4.4.3.1 is used in NR Cell 1 and NR Cell 12.

– NR-SS-UE

– NR-SS-UE1 operating as NR sidelink communication transmitting device on the resources that UE is expected to use for transmission.

– NR-SS-UE1 is synchronised on NR Cell 1.

UE:

  • UE is authorised to perform NR sidelink communication.
  • The UE is equipped with a USIM containing default values as per TS 38.508-1 [4] clause 4.8.3.3.3 except for those listed in Table 12.2.1.2.3.1-1.
  • UE is synchronised on NR Cell 1.

Table 12.2.1.2.3.1-1: UE/ USIM configuration

USIM field

Priority

Value

Access Technology Identifier

EFUST

service no. 119 is available

EFVST

Service no.2 V2X policy configuration data over PC5 is supported, i.e. value is ’01 02′ HEX

EFV2XP_PC5

SL-PreconfigurationNR field as defined in TS 38.508-1 [4], table 4.10.1-1, except SL-BWP-PoolConfigCommon field as defined in Table 12.2.1.2.3.3-1

Preamble:

– The UE is in state 1N-A as defined in TS 38.508-1 [4], subclause 4.4A on NR Cell 1.

12.2.1.2.3.2 Test procedure sequence

Table 12.2.1.2.3.2-1 and 12.2.1.2.3.2-2 illustrate the downlink power levels to be applied for NR Cell 1 and NR Cell 12 at various time instants of the test execution for FR1 and FR2 respectively. Row marked "T0" denotes the conditions after the preamble, while rows marked "T1" is to be applied subsequently. The exact instants on which these values shall be applied are described in the texts in this clause.

Table 12.2.1.2.3.2-1: Time instances of cell power level and parameter changes in FR1

Parameter

Unit

NR Cell 1

NR Cell 12

Remark

T0

SS/PBCH

SSS EPRE

dBm/SCS

-88

Off

T1

SS/PBCH

SSS EPRE

dBm/SCS

-88

-80

Table 12.2.1.2.3.2-2: Time instances of cell power level and parameter changes in FR2

Parameter

Unit

NR Cell 1

NR Cell 12

Remark

T0

SS/PBCH

SSS EPRE

dBm/SCS

-82

Off

T1

SS/PBCH

SSS EPRE

dBm/SCS

-82

-72

Table 12.2.1.2.3.2-3: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Check: Does the test result of generic test procedure in TS 38.508-1 [4] Table 4.9.23.2.2-1 indicate that the UE has established sidelink communication using the pool of resources indicated by sl-RxPool in pre-configuration?

–

–

2

P

2

The UE is switched off by executing generic procedure in Table 4.9.6.1-1 in TS 38.508-1 [4].

–

–

–

–

3

The SS-NW adds SIB12 on NR Cell 1 and NR Cell 12, system information combination NR-14 as defined in TS 38.508-1 [4] clause 4.4.3.1 is used.

–

–

–

–

4

The UE is Switched ON.

–

–

–

–

5-24a1

Steps 1 to 20a1 of the generic test procedure described in TS 38.508-1 [4] table 4.5.2.2-2 are performed on NR Cell 1.

–

–

–

–

25

The SS adjusts cell levels according to row T1 of table 12.2.1.2.3.2-1/2.

–

–

–

–

26

Upper layers of the UE configure the UE to perform sidelink transmission.

Note: This step is triggered by MMI or AT command

–

–

–

–

–

EXCEPTION: In parallel with step 27, parallel behaviour defined in table 12.2.1.2.3.2-4 is executed.

–

–

–

–

27

Check: Does the test result of generic test procedure in TS 38.508-1 [4] Table 4.9.5.2.2-1 indicate that the UE is camped on NR Cell 12.

NOTE: The UE performs a registration for mobility procedure and the RRC connection is not released.

–

–

1

P

28

The NR-SS-UE1 transmits a DIRECT LINK ESTABLISHMENT REQUEST message using the pool of resources indicated by sl-RxPool in SIB12 of NR Cell 12.

<–

PC5-S: DIRECT LINK ESTABLISHMENT REQUEST

–

–

29

Check: Does the UE transmit a DIRECT LINK SECURITY MODE COMMAND message.

–>

PC5-S: DIRECT LINK SECURITY MODE COMMAND

1

P

30

The NR-SS-UE1 transmits a DIRECT LINK SECURITY MODE COMPLETE message.

<–

PC5-S: DIRECT LINK SECURITY MODE COMPLETE

–

–

31

The UE transmits a DIRECT LINK ESTABLISHMENT ACCEPT message.

–>

PC5-S: DIRECT LINK ESTABLISHMENT ACCEPT

–

–

32

The NR-SS-UE1 transmits an RRCReconfigurationSidelink message.

<–

PC5-RRC: RRCReconfigurationSidelink

–

–

33

Check: Does the UE transmit an RRCReconfigurationCompleteSidelink message?

–>

PC5-RRC: RRCReconfigurationCompleteSidelink

1

P

Table 12.2.1.2.3.2-4: Parallel behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

The UE sends a SidelinkUEInformationNR message.

–>

NR RRC: SidelinkUEInformationNR

–

–

12.2.1.2.3.3 Specific message contents

Table 12.2.1.2.3.3-1: SL-BWP-PoolConfigCommon (Preamble)

Derivation Path: TS 38.508-1 [4], Table 4.6.6-4 with condition RXPOOL and SELECTED

Table 12.2.1.2.3.3-2: SIB12 for NR Cell 12 (Step 3, Table 12.2.1.2.3.2-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.2-14

Information Element

Value/remark

Comment

Condition

SIB12-r16 ::= SEQUENCE {

segmentContainer-r16

OCTET STRING (CONTAINING SIB12-IEs-r16 or segment of SIB12-IEs-r16)

}

Table 12.2.1.2.3.3-3: SIB12-IEs-r16 (Table 12.2.1.2.3.3-2)

Derivation Path: TS 38.508-1 [4], Table 4.6.2-14A

Information Element

Value/remark

Comment

Condition

SIB12-IEs-r16 ::= SEQUENCE {

sl-ConfigCommonNR-r16 SEQUENCE {

sl-FreqInfoList-r16 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-FreqConfigCommon-r16{

1 entry

SL-FreqConfigCommon-r16[1]

SL-FreqConfigCommon

}

}

}

Table 12.2.1.2.3.3-4: SL-FreqConfigCommon (Table 12.2.1.2.3.3-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.6-11

Information Element

Value/remark

Comment

Condition

SL-FreqConfigCommon-r16 ::= SEQUENCE {

sl-ConfigCommonNR-r16 SEQUENCE {

sl-BWP-List-r16 SEQUENCE (SIZE (1..maxNrofSL-BWPs-r16)) OF SL-BWP-ConfigCommon-r16 {

1 entry

SL-BWP-ConfigCommon-r16[1]

SL-BWP-ConfigCommon

}

}

}

Table 12.2.1.2.3.3-5: SL-BWP-ConfigCommon (Table 12.2.1.2.3.3-4)

Derivation Path: TS 38.508-1 [4], Table 4.6.6-2

Information Element

Value/remark

Comment

Condition

SL-BWP-ConfigCommon-r16 ::= SEQUENCE {

sl-BWP-PoolConfigCommon-r16

SL-BWP-PoolConfigCommon

}

Table 12.2.1.2.3.3-6: SL-BWP-PoolConfigCommon (Table 12.2.1.2.3.3-5)

Derivation Path: TS 38.508-1 [4], Table 4.6.6-4 with condition RXPOOL and SELECTED

Table 12.2.1.2.3.3-7: SL-ResourcePool (Table 12.2.1.2.3.3-6)

Derivation Path: TS 38.508-1 [4], Table 4.6.6-25

Information Element

Value/remark

Comment

Condition

SL-ResourcePool-r16 ::= SEQUENCE {

sl-TimeResource-r16

0000000011

}

Table 12.2.1.2.3.3-8: SIB12 for NR Cell 1 (Step 3, Table 12.2.1.2.3.2-3)

Derivation Path: TS 38.508-1 [4], Table 4.6.2-14

Table 12.2.1.2.3.3-9: SIB12-IEs-r16 (Table 12.2.1.2.3.3-8)

Derivation Path: TS 38.508-1 [4], Table 4.6.2-14A

Information Element

Value/remark

Comment

Condition

SIB12-IEs-r16 ::= SEQUENCE {

sl-ConfigCommonNR-r16 SEQUENCE {

sl-FreqInfoList-r16

Not present

sl-NR-AnchorCarrierFreqList-r16 SEQUENCE (SIZE (1.. maxFreqSL-NR-r16)) OF ARFCN-ValueNR {

1 entry

ARFCN-ValueNR[1]

ARFCN-ValueNR of NR Cell 12

}

}

}

Table 12.2.1.2.3.3-10: SidelinkUEInformationNR (Step 1, Table 12.2.1.2.3.2-4)

Derivation Path: TS 38.508-1 [4], Table 4.6.1-28A with condition SIDELINK_TX

12.2.1.3 Inter-carrier concurrent operation / Sidelink communication / RRC_CONNECTED / Transmission / Network scheduling

12.2.1.3.1 Test Purpose (TP)

(1)

with { UE is in RRC_CONNECTED state and its serving cell broadcasts SIB12 including sl-ConfigCommonNR }

ensure that {

when { UE is configured by upper layers to perform sidelink transmission on the frequency included in sl-FreqInfoList }

then { UE sends a SidelinkUEInfomationNR message to indicate it requires sidelink transmission resources }

}

(2)

with { UE is in RRC_CONNECTED state and is configured by upper layers to perform sidelink transmission }

ensure that {

when { UE receives an RRCReconfiguration message which includes sl-ScheduledConfig and no sl-ConfiguredGrantConfigList }

then { UE performs sidelink transmission based on dynamic scheduling }

}

(3)

with { UE is in RRC_CONNECTED state }

ensure that {

when { UE is configured by upper layers to provide configured grant assistance information for NR sidelink communication }

then { UE sends a UEAssistanceInformation message including sl-UE-AssistanceInformationNR }

}

(4)

with { UE is in RRC_CONNECTED state and is configured by upper layers to perform sidelink transmission }

ensure that {

when { UE receives an RRCReconfiguration message which includes sl-ConfiguredGrantConfigList }

then { UE performs sidelink transmission using the configured grant included in sl-ConfiguredGrantConfigList }

}

(5)

with { UE is in RRC_CONNECTED state and is configured by upper layer to perform sidelink transmission }

ensure that {

when { UE is no longer configured by upper layers to perform sidelink transmission }

then { UE sends a SidelinkUEInfomationNR message to indicate it no longer requires sidelink transmission resources }

}

12.2.1.3.2 Conformance requirements

References: The conformance requirements covered in the current TC are specified in: TS 38.331, clause 5.3.5.3, 5.5.2, 5.5.4.1, 5.5.4.2, 5.5.4.3 and 5.5.5. Unless otherwise stated these are Rel-16 requirements.

[TS 38.331, clause 5.3.5.3]

The UE shall perform the following actions upon reception of the RRCReconfiguration, or upon execution of the conditional reconfiguration (CHO or CPC):

…

1> if the RRCReconfiguration message includes the otherConfig:

2> perform the other configuration procedure as specified in 5.3.5.9;

…

1> if the RRCReconfiguration message includes the sl-ConfigDedicatedNR:

2> perform the sidelink dedicated configuration procedure as specified in 5.3.5.14;

…

1> else (RRCReconfiguration was received via SRB1):

2> submit the RRCReconfigurationComplete message via SRB1 to lower layers for transmission using the new configuration;

…

[TS 38.331, clause 5.3.5.14]

Upon initiating the procedure, the UE shall:

…

1> if sl-FreqInfoToAddModList is included in sl-ConfigDedicatedNR within RRCReconfiguration:

…

2> if configured to transmit NR sidelink communication:

3> use the resource pool(s) indicated by sl-TxPoolSelectedNormal, sl-TxPoolScheduling or sl-TxPoolExceptional for NR sidelink communication transmission, as specified in 5.8.8;

2> perform CBR measurement on the transmission resource pools indicated by sl-TxPoolSelectedNormal, sl-TxPoolScheduling or sl-TxPoolExceptional for NR sidelink communication transmission, as specified in 5.5.3;

2> use the synchronization configuration parameters for NR sidelink communication on frequencies included in sl-FreqInfoToAddModList, as specified in 5.8.5;

…

1> if sl-RadioBearerToAddModList or sl-RLC-BearerToAddModList is included in sl-ConfigDedicatedNR within RRCReconfiguration:

2> perform sidelink DRB addition/modification as specified in 5.8.9.1a.2;

1> if sl-ScheduledConfig is included in sl-ConfigDedicatedNR within RRCReconfiguration:

2> configure the MAC entity parameters, which are to be used for NR sidelink communication, in accordance with the received sl-ScheduledConfig;

…

[TS 38.331, clause 5.7.4.2]

…

A UE capable of providing configured grant assistance information for NR sidelink communication in RRC_CONNECTED may initiate the procedure in several cases, including upon being configured to provide traffic pattern information and upon change of traffic patterns.

…

Upon initiating the procedure, the UE shall:

…

1> if configured to provide configured grant assistance information for NR sidelink communication:

2> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide configured grant assistance information for NR sidelink communication;

…

[TS 38.331, clause 5.7.4.3]

…

The UE shall set the contents of the UEAssistanceInformation message for configured grant assistance information for NR sidelink communication:

1> if configured to provide configured grant assistance information for NR sidelink communication:

2> include the sl-UE-AssistanceInformationNR;

…

1> else:

2> submit the UEAssistanceInformation message to lower layers for transmission.

[TS 38.331, clause 5.8.3.2]

Upon initiating this procedure, the UE shall:

1> if SIB12 including sl-ConfigCommonNR is provided by the PCell:

2> ensure having a valid version of SIB12 for the PCell;

…

2> if configured by upper layers to transmit NR sidelink communication on the frequency included in sl-FreqInfoList in SIB12 of the PCell:

3> if the UE did not transmit a SidelinkUEInformationNR message since last entering RRC_CONNECTED state; or

3> if since the last time the UE transmitted a SidelinkUEInformationNR message the UE connected to a PCell not providing SIB12 including sl-ConfigCommonNR; or

3> if the last transmission of the SidelinkUEInformationNR message did not include sl-TxResourceReqList; or if the information carried by the sl-TxResourceReqList has changed since the last transmission of the SidelinkUEInformationNR message:

4> initiate transmission of the SidelinkUEInformationNR message to indicate the NR sidelink communication transmission resources required by the UE in accordance with 5.8.3.3;

2> else:

3> if the last transmission of the SidelinkUEInformationNR message included sl-TxResourceReqList:

4> initiate transmission of the SidelinkUEInformationNR message to indicate it no longer requires NR sidelink communication transmission resources in accordance with 5.8.3.3.

[TS 38.331, clause 5.8.3.3]

The UE shall set the contents of the SidelinkUEInformationNR message as follows:

1> if the UE initiates the procedure to indicate it is (no more) interested to receive NR sidelink communication or to request (configuration/ release) of NR sidelink communication transmission resources or to report to the network that a sidelink radio link failure or sidelink RRC reconfiguration failure has been declared (i.e. UE includes all concerned information, irrespective of what triggered the procedure):

2> if SIB12 including sl-ConfigCommonNR is provided by the PCell:

…

3> if configured by upper layers to transmit NR sidelink communication:

4> include sl-TxResourceReqList and set its fields (if needed) as follows for each destination for which it requests network to assign NR sidelink communication resource:

5> set sl-DestinationIdentity to the destination identity configured by upper layer for NR sidelink communication transmission;

5> set sl-CastType to the cast type of the associated destination identity configured by the upper layer for the NR sidelink communication transmission;

…

5> set sl-QoS-InfoList to include QoS profile(s) of the sidelink QoS flow(s) of the associated destination configured by the upper layer for the NR sidelink communication transmission;

5> set sl-InterestedFreqList to indicate the frequency of the associated destination for NR sidelink communication transmission;

5> set sl-TypeTxSyncList to the current synchronization reference type used on the associated sl-InterestedFreqList for NR sidelink communication transmission.

…

…

1> else:

2> submit the SidelinkUEInformationNR message to lower layers for transmission;

[TS 38.331, clause 5.8.8]

A UE capable of NR sidelink communication that is configured by upper layers to transmit NR sidelink communication and has related data to be transmitted shall:

1> if the conditions for NR sidelink communication operation as defined in 5.8.2 are met:

2> if the frequency used for NR sidelink communication is included in sl-FreqInfoToAddModList in sl-ConfigDedicatedNR within RRCReconfiguration message or included in sl-ConfigCommonNR within SIB12:

3> if the UE is in RRC_CONNECTED and uses the frequency included in sl-ConfigDedicatedNR within RRCReconfiguration message:

4> if the UE is configured with sl-ScheduledConfig:

…

5> else:

6> configure lower layers to perform the sidelink resource allocation mode 1 for NR sidelink communication;

…

[TS 38.321, clause 5.22.1.1]

…

If the MAC entity has been configured with Sidelink resource allocation mode 1 as indicated in TS 38.331 [5], the MAC entity shall for each PDCCH occasion and for each grant received for this PDCCH occasion:

1> if a sidelink grant has been received on the PDCCH for the MAC entity’s SL-RNTI:

…

2> else:

3> use the received sidelink grant to determine PSCCH duration(s) and PSSCH duration(s) for initial transmission and, if available, retransmission(s) of a single MAC PDU according to clause 8.1.2 of TS 38.214 [7].

…

1> else if a sidelink grant has been received on the PDCCH for the MAC entity’s SLCS-RNTI:

2> if PDCCH contents indicate retransmission(s) for the identified HARQ process ID that has been set for an activated configured sidelink grant identified by sl-ConfigIndexCG:

3> use the received sidelink grant to determine PSCCH duration(s) and PSSCH duration(s) for one or more retransmissions of a single MAC PDU according to clause 8.1.2 of TS 38.214 [7].

…

The MAC entity shall for each PSSCH duration:

1> for each sidelink grant occurring in this PSSCH duration:

2> if the MAC entity has been configured with Sidelink resource allocation mode 1:

3> select a MCS which is, if configured, within the range that is configured by RRC between sl-MinMCS-PSSCH and sl-MaxMCS-PSSCH included in sl-ConfigDedicatedNR;

3> set the resource reservation interval to 0ms.

…

2> if the configured sidelink grant has been activated and this PSSCH duration corresponds to the first PSSCH transmission opportunity within this sl-PeriodCG of the configured sidelink grant:

3> set the HARQ Process ID to the HARQ Process ID associated with this PSSCH duration and, if available, all subsequent PSSCH duration(s) occurring in this sl-PeriodCG for the configured sidelink grant;

3> determine that this PSSCH duration is used for initial transmission;

3> if a dynamic sidelink grant associated to the HARQ Process ID has been received on the PDCCH for the MAC entity’s SLCS-RNTI:

4> clear the dynamic sidelink grant.

2> deliver the sidelink grant, the selected MCS, and the associated HARQ information to the Sidelink HARQ Entity for this PSSCH duration.

…

[TS 38.321, clause 5.22.1.1]

…

A SL-BSR shall be triggered if any of the following events occur:

1> if the MAC entity has been configured with Sidelink resource allocation mode 1:

2> SL data, for a logical channel of a Destination, becomes available to the MAC entity; and either

3> this SL data belongs to a logical channel with higher priority than the priorities of the logical channels containing available SL data which belong to any LCG belonging to the same Destination; or

3> none of the logical channels which belong to an LCG belonging to the same Destination contains any available SL data.

in which case the SL-BSR is referred below to as ‘Regular SL-BSR’;

…

1> else:

2> Sidelink resource allocation mode 1 is configured by RRC and SL data is available for transmission in the RLC entity or in the PDCP entity, in which case the Sidelink BSR is referred below to as "Regular SL-BSR".

For Regular SL-BSR, the MAC entity shall:

1> if the SL-BSR is triggered for a logical channel for which sl-logicalChannelSR-DelayTimerApplied with value true is configured by RRC:

2> start or restart the sl-logicalChannelSR-DelayTimer.

1> else:

2> if running, stop the sl-logicalChannelSR-DelayTimer.

For Regular and Periodic SL-BSR, the MAC entity shall:

1> if sl-PrioritizationThres is configured and the value of the highest priority of the logical channels that belong to any LCG and contain SL data for any Destination is lower than sl-PrioritizationThres; and

1> if either ul-PrioritizationThres is not configured or ul-PrioritizationThres is configured and the value of the highest priority of the logical channels that belong to any LCG and contain UL data is equal to or higher than ul-PrioritizationThres according to clause 5.4.5:

2> prioritize the LCG(s) for the Destination(s).

1> if the Buffer Status reporting procedure determines that at least one BSR has been triggered and not cancelled according to clause 5.4.5 and the UL grant cannot accommodate a SL-BSR MAC CE containing buffer status only for all prioritized LCGs having data available for transmission plus the subheader of the SL-BSR according to clause 5.4.3.1.3, in case the SL-BSR is considered as not prioritized:

2> prioritize the SL-BSR for logical channel prioritization specified in clause 5.4.3.1;

2> report Truncated SL-BSR containing buffer status for as many prioritized LCGs having data available for transmission as possible, taking the number of bits in the UL grant into consideration.

1> else if the number of bits in the UL grant is expected to be equal to or larger than the size of a SL-BSR containing buffer status for all LCGs having data available for transmission plus the subheader of the SL-BSR according to clause 5.4.3.1.3:

2> report SL-BSR containing buffer status for all LCGs having data available for transmission.

1> else:

2> report Truncated SL-BSR containing buffer status for as many LCGs having data available for transmission as possible, taking the number of bits in the UL grant into consideration.

…

The MAC entity shall:

1> if the sidelink Buffer Status reporting procedure determines that at least one SL-BSR has been triggered and not cancelled:

2> if UL-SCH resources are available for a new transmission and the UL-SCH resources can accommodate the SL-BSR MAC CE plus its subheader as a result of logical channel prioritization according to clause 5.4.3.1:

3> instruct the Multiplexing and Assembly procedure in clause 5.4.3 to generate the SL-BSR MAC CE(s);

3> start or restart sl-periodicBSR-Timer except when all the generated SL-BSRs are Truncated SL-BSRs;

3> start or restart sl-retxBSR-Timer.

…

12.2.1.3.3 Test description

12.2.1.3.3.1 Pre-test conditions

System Simulator:

– SS-NW

– NR Cell 1

– System information combination FFS as defined in TS 38.508-1 [4] clause 4.4.3.1 is used in NR Cell 1.

– SS-UE

– Operating as NR sidelink communication receiving device on the resources that UE is expected to use for transmission.

UE:

  • UE is authorised to perform NR sidelink communication.

Preamble:

– The UE is in state 3N-A as defined in TS 38.508-1 [4], subclause 4.4A on NR Cell 1 and Test Loop Function (On) with UE test loop mode FFS defined in 38.509 [6], subclause FFS.

12.2.1.3.3.2 Test procedure sequence

FFS

Table 12.2.1.3.3.2-1: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Upper layers of the UE configures the UE to perform sidelink transmission.

Note: This step is triggered by MMI or AT command

–

–

–

–

2

Check: Does the UE send a SidelinkUEInformationNR message to request sidelink transmission resource?

–>

NR RRC: SidelinkUEInformationNR

1

P

3

SS-NW transmits an RRCReconfiguration message with sl-ConfigDedicatedNR to configure transmission resources and to configure the UE to perform network scheduling-based sidelink transmission

<–

NR RRC: RRCReconfiguration

–

–

4

The UE transmits an RRCReconfigurationComplete message.

–>

NR RRC: RRCReconfigurationComplete

5

Check: Does the UE send a Sidelink BSR MAC-CE?

–>

MAC CE (sidelink BSR)

2

P

5

SS-NW sends a DCI format 3_0 to configure sidelink grant for the UE

<–

DCI format 3_0

–

–

6

Check: Does the UE transmit one STCH PDCP SDU over the PC5 interface using the resources scheduled by SS-NW?

–>

STCH PDCP SDU

2

P

7

Upper layers of the UE configures the UE to send a UEAssistanceInformation message.

Note: This step is triggered by MMI or AT command

–

–

–

–

8

Check: Does the UE send a UEAssistanceInformation message to provide configured grant assistance information?

–>

NR RRC: UEAssistanceInformation

3

P

9

SS-NW transmits an RRCReconfiguration message with sl-ConfiguredGrantConfigList to provide a Type 2 configure grant for the UE.

<–

NR RRC: RRCReconfiguration

–

–

10

The UE transmits an RRCReconfigurationComplete message.

–>

NR RRC: RRCReconfigurationComplete

–

–

11

SS-NW transmits an DCI format 3_0 to activate the configured grant.

<–

DCI format 3_0

–

–

12

The UE sends a Sidelink Configured Grant Confirmation MAC CE

–>

MAC CE (Sidelink Configured Grant Confirmation)

–

–

13

Check: Does the UE transmit one STCH PDCP SDU over the PC5 interface using the resources indicated by the configured grant?

–>

STCH PDCP SDU

4

P

14

Upper layer of the UE configures the UE to stop sidelink transmission.

–

–

–

–

15

Check: Does the UE send a SidelinkUEInformationNR message to indicate that sidelink transmission resource is not needed?

–>

NR RRC: SidelinkUEInformationNR

1

P

12.2.1.3.3.3 Specific message contents

FFS

12.2.1.4

12.2.1.5

12.2.1.6 Inter-carrier concurrent operation / Sidelink communication / RRC_CONNECTED / Reception

12.2.1.6.1 Test Purpose (TP)

(1)

with { UE being in RRC_CONNECTED state and its serving cell not broadcasting SIB12 }

ensure that {

when { UE is configured by upper layer to perform NR sidelink reception}

then { UE is able to monitor NR sidelink reception using sl-RxPool included in pre-configuration}

}

(2)

with { UE being in RRC_CONNECTED state and its serving cell broadcasting SIB12 }

ensure that {

when { UE is configured by upper layer to perform NR sidelink reception}

then { UE is able to monitor NR sidelink reception using sl-RxPool included in SIB12}

}

(3)

with { UE being in RRC_CONNECTED state and having received a RRCReconfiguration including sl-RxPool }

ensure that {

when { UE is configured by upper layer to perform NR sidelink reception}

then { UE is able to monitor NR sidelink reception using sl-RxPool included in sl-ConfigDedicatedNR}

}

(4)

with { UE being in RRC_CONNECTED state and being configured by upper layer to perform NR sidelink reception }

ensure that {

when { UE receives a RRCReconfiguration including reconfigurationWithSync and sl-RxPool}

then { UE is able to monitor NR sidelink reception using sl-RxPool included in the received RRCReconfiguration message during handover procedure}

}

12.2.1.6.2 Conformance requirements

References: The conformance requirements covered in the present TC are specified in: TS 38.331, clause 5.8.1, clause 5.8.7. Unless otherwise stated these are Rel-16 requirements.

[TS 38.331, clause 5.8.1]

The PC5-RRC signalling, as specified in sub-clause 5.8.9, can be initiated after its corresponding PC5 unicast link establishment (TS 23.287 [55]).

[TS 38.331, clause 5.8.7]

A UE capable of NR sidelink communication that is configured by upper layers to receive NR sidelink communication shall:

1> if the conditions for NR sidelink communication operation as defined in 5.8.2 are met:

2> if the frequency used for NR sidelink communication is included in sl-FreqInfoToAddModList in RRCReconfiguration message or sl-FreqInfoList included in SIB12:

3> if the UE is configured with sl-RxPool included in RRCReconfiguration message with reconfigurationWithSync (i.e. handover):

4> configure lower layers to monitor sidelink control information and the corresponding data using the pool of resources indicated by sl-RxPool;

3> else if the cell chosen for NR sidelink communication provides SIB12:

4> configure lower layers to monitor sidelink control information and the corresponding data using the pool of resources indicated by sl-RxPool in SIB12;

2> else:

3> configure lower layers to monitor sidelink control information and the corresponding data using the pool of resources that were preconfigured by sl-RxPool in SL-PreconfigurationNR, as defined in sub-clause 9.3;

12.2.1.6.3 Test description

12.2.1.6.3.1 Pre-test conditions

System Simulator:

– SS-NW

– NR Cell 1 is the serving cell and NR Cell 3 is the inter-frequency neighbour cell of NR Cell 1.

– System information combination NR-4 as defined in TS 38.508-1 [4] clause 4.4.3.1.

– NR-SS-UE

– NR-SS-UE1 operating as NR sidelink communication receiving and transmitting device on the resources that UE is expected to use for transmission and reception via PC5 interface.

– NR-SS-UE1 is synchronised on NR Cell 1.

UE:

– UE is authorised to perform NR sidelink communication.

– The UE is equipped with below information in UE or in a USIM containing default values (as per TS 38.508-1 [4] clause 4.8.3.3.3) except for those listed in Table 12.2.1.6.3.1-1.

– UE is synchronised on NR Cell 1.

Table 12.2.1.6.3.1-1: UE/ USIM configuration

USIM field

Priority

Value

Access Technology Identifier

EFUST

service no. 119 is available

EFVST

Service no.2 V2X policy configuration data over PC5 is supported, i.e. value is ’01 02′ HEX

EFV2XP_PC5

SL-PreconfigurationNR field as defined in TS 38.508-1 [4], table 4.10.1-1, except SL-BWP-PoolConfigCommon field as defined in Table 12.2.1.6.3.3-1 with condition SL-PRECONFIG

Preamble:

– The UE is in state 3N-B RRC_CONNECTED_with_SL and Test Loop Function (On) with UE test loop mode E as defined in TS 38.508-1 [4] subclause 4.4A on NR Cell 1, using generic parameters Sidelink (On), Cast Type (Unicast) using UE initiated unicast mode NR sidelink communication procedure in subclause 4.9.22.

– NR-SS-UE1 initiated unicast mode NR sidelink communication.

12.2.1.6.3.2 Test procedure sequence

Tables 12.2.1.6.3.2-1 and 12.2.1.6.3.2-2 illustrate the downlink power levels to be applied for NR Cell 1 and NR Cell 3 at various time instants of the test execution. Row marked "T0" denotes the conditions after the preamble, while the configuration marked "T1" is applied at the point indicated in the Main behaviour description in Table 12.2.1.6.3.2-3.

Table 12.2.1.6.3.2-1: Power levels in FR1

Parameter

Unit

NR Cell 1

NR

Cell 3

Remark

T0

SS/PBCH SSS EPRE

dBm/

SCS

-85

-91

Power levels are such that entry condition for event A3 is not satisfied for NR Cell 3

T1

SS/PBCH SSS EPRE

dBm/

SCS

-85

-79

Power levels are such that entry condition for event A3 is satisfied for NR Cell 3

Table 12.2.1.6.3.2-2: Power levels in FR2

Parameter

Unit

NR

Cell 1

NR

Cell 3

Remark

T0

SS/PBCH SSS EPRE

dBm/ SCS

FFS

FFS

Power levels are such that entry condition for event A3 is not satisfied for NR Cell 3

T1

SS/PBCH SSS EPRE

dBm/ SCS

FFS

FFS

Power levels are such that entry condition for event A3 is satisfied for NR Cell 3

Table 12.2.1.6.3.2-3: Main behaviour

St

Procedure

Message Sequence

TP

Verdict

U – S

Message

1

Check: Does the test result of generic test procedure in TS 38.508-1[4] subclause 4.9.31 indicate that the UE monitors NR sidelink reception using sl-RxPool included in pre-configuration?

–>

1

–

2

SS starts broadcasting SIB12 in NR-Cell 1 using system information combination NR-14

–

–

–

3

NR Cell 1 transmits a Short message on PDCCH using P-RNTI indicating a systemInfoModification.

–

PDCCH (DCI 1_0): Short Message

–

4

Wait for 2.1* modification period to allow the new system information to take effect.

–

–

–

–

5

The UE transmits a SidelinkUEInformationNR message to indicate it is (interested in) receiving NR sidelink communication.

–>

NR RRC: SidelinkUEInformationNR

–

–

6

Check: Does the test result of generic test procedure in TS 38.508-1[4] subclause 4.9.31 indicate that the UE monitors NR sidelink reception using sl-RxPool included in SIB12?

–

–

2

–

7

SS-NW sends an RRCReconfiguration message including sl-RxPool.

<–

NR RRC: RRCReconfiguration

–

–

8

UE sends an RRCReconfigurationComplete message

–>

NR RRC: RRCReconfigurationComplete

–

–

9

Check: Does the test result of generic test procedure in TS 38.508-1[4] subclause 4.9.31 indicate that the UE monitors NR sidelink reception using sl-RxPool included in sl-ConfigDedicatedNR?

–

–

3

–

10

The SS changes NR Cell 3 parameters according to the row "T1" in Table 12.2.1.6.3.2-1/2.

–

–

–

–

11

SS-NW sends an RRCReconfiguration message including reconfigurationWithSync and sl-RxPool on NR Cell 1 to order the UE to perform intra handover to NR Cell 3.

<–

NR RRC: RRCReconfiguration

–

–

12

UE sends an RRCReconfigurationComplete message on NR Cell 3 to confirm the successful handover.

–>

NR RRC: RRCReconfigurationtComplete

–

–

13

Check: Does the test result of generic test procedure in TS 38.508-1[4] subclause 4.9.31 indicate that the UE monitors NR sidelink reception using sl-RxPool included in the received RRCReconfiguration?

–

–

4

–

12.2.1.6.3.3 Specific message contents

Table 12.2.1.6.3.3-1: SL-BWP-PoolConfigCommon (Preamble, Table 12.2.1.6.3.1-1 and Table 12.2.1.6.3.3-5)

Derivation Path: TS 38.508-1 [4], Table 4.6.6-4

Information Element

Value/remark

Comment

Condition

SL-BWP-PoolConfigCommon-r16 ::= SEQUENCE {

sl-RxPool-r16 SEQUENCE (SIZE (1..maxNrofRXPool-r16)) OF SL-ResourcePool-r16 {

1 entry

SL-ResourcePool-r16[1]

SL-ResourcePool with condition RX_TX1 as defined in Table 12.2.1.6.3.3-13

entry 1

SL-PRECONFIG

SL-ResourcePool-r16[1]

SL-ResourcePool with condition RX_TX2 as defined in Table 12.2.1.6.3.3-13

SIB-12

}

sl-TxPoolSelectedNormal-r16 SEQUENCE (SIZE (1..maxNrofTXPool-r16)) OF SL-ResourcePoolConfig-r16 {

1 entry

SL-ResourcePoolConfig-r16[1] SEQUENCE {

entry 1

sl-ResourcePoolID-r16

1

Index of the resource pool for normal case

sl-ResourcePool-r16

SL-ResourcePool with condition RX_TX1 as defined in Table 12.2.1.6.3.3-13

SL-PRECONFIG

sl-ResourcePool-r16

SL-ResourcePool with condition RX_TX2 as defined in Table 12.2.1.6.3.3-13

SIB-12

}

}

}

Table 12.2.1.6.3.3-2: SIB12 (step 2, Table 12.2.1.6.3.2-3)

Derivation path: TS 38.508-1 [4], Table 4.6.2-14 with condition LAST_SEG

Information Element

Value/Remark

Comment

Condition

SIB12-r16 ::= SEQUENCE {

segmentContainer-r16

OCTET STRING (CONTAINING SIB12-RESOURCEPOOL)

}

Table 12.2.1.6.3.3-3: SIB12-RESOURCEPOOL (Table 12.2.1.6.3.3-2)

Derivation path: TS 38.508-1 [4], Table 4.6.2-14A

Information Element

Value/Remark

Comment

Condition

SIB12-IEs-r16 ::= SEQUENCE {

sl-ConfigCommonNR-r16 SEQUENCE {

sl-FreqInfoList-r16 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-FreqConfigCommon-r16{

SL-FreqConfigCommon-r16[1]

SL-FreqConfigCommon

}

}

}

Table 12.2.1.6.3.3-4: SL-FreqConfigCommon (Table 12.2.1.6.3.3-3)

Derivation path: TS 38.508-1 [4], Table 4.6.6-11

Information Element

Value/Remark

Comment

Condition

SL-FreqConfigCommon-r16 ::= SEQUENCE {

sl-BWP-List-r16 SEQUENCE (SIZE (1..maxNrofSL-BWPs-r16)) OF SL-BWP-ConfigCommon-r16 {

SL-BWP-ConfigCommon-r16[1]

SL-BWP-ConfigCommon

}

}

Table 12.2.1.6.3.3-5: SL-BWP-ConfigCommon (Table 12.2.1.6.3.3-4)

Derivation path: TS 38.508-1 [4], Table 4.6.6-2

Information Element

Value/Remark

Comment

Condition

SL-BWP-ConfigCommon-r16 ::= SEQUENCE {

sl-BWP-PoolConfigCommon-r16

SL-BWP-PoolConfigCommon with condition SIB-12 as defined in Table 12.2.1.6.3.3-1

}

Table 12.2.1.6.3.3-6: RRCReconfiguration (step 7, Table 12.2.1.6.3.2-3)

Derivation path: TS 38.508-1 [4], Table 4.6.1-13

Information Element

Value/Remark

Comment

Condition

RRCReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

rrcReconfiguration SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

sl-ConfigDedicatedNR-r16

SL-ConfigDedicatedNR with condition SCHEDULING as defined in Table 12.2.1.6.3.3-7

}

}

}

}

}

}

}

Table 12.2.1.6.3.3-7: SL-ConfigDedicatedNR (Table 12.2.1.6.3.3-6 and Table 12.2.1.6.3.3-11)

Derivation path: TS 38.508-1 [4], Table 4.6.6-7 with condition SCHEDULING

Information Element

Value/Remark

Comment

Condition

SL-ConfigDedicatedNR-r16 ::= SEQUENCE {

sl-FreqInfoToAddModList-r16 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-FreqConfig-r16 {

one entry

SL-FreqConfig-r16[1]

SL-FreqConfig with condition SCHEDULING as defined in Table 12.2.1.6.3.3-8

SCHEDULING

SL-FreqConfig-r16[1]

SL-FreqConfig with condition EXCEPTIONAL as defined in Table 12.2.1.6.3.3-8

EXCEPTIONAL

}

}

Table 12.2.1.6.3.3-8: SL-FreqConfig (Table 12.2.1.6.3.3-7)

Derivation path: TS 38.508-1 [4], Table 4.6.6-10

Information Element

Value/Remark

Comment

Condition

SL-FreqConfig-r16 ::= SEQUENCE {

sl-BWP-ToAddModList-r16 SEQUENCE (SIZE (1..maxNrofSL-BWPs-r16)) OF SL-BWP-Config-r16 {

one entry

SL-BWP-Config-r16[1]

SL-BWP-Config with condition RX_ SCHEDULINGTX as defined in Table 12.2.1.6.3.3-9

SCHEDULING

SL-BWP-Config-r16[1]

SL-BWP-Config with condition RX_ EXCEPTIONALTX as defined in Table 12.2.1.6.3.3-9

EXCEPTIONAL

}

}

Table 12.2.1.6.3.3-9: SL-BWP-Config (Table 12.2.1.6.3.3-8)

Derivation path: TS 38.508-1 [4], Table 4.6.6-1

Information Element

Value/Remark

Comment

Condition

SL-BWP-Config-r16 ::= SEQUENCE {

sl-BWP-PoolConfig-r16 SEQUENCE {

sl-RxPool-r16 SEQUENCE (SIZE (1..maxNrofRXPool-r16)) OF SL-ResourcePool-r16 {

1 entry

RX_ SCHEDULINGTX, RX_ EXCEPTIONALTX

SL-ResourcePool-r16[1]

SL-ResourcePool with condition RX_TX2 as defined in Table 12.2.1.6.3.3-13

entry 1

SL-ResourcePool-r16[1]

SL-ResourcePool with condition RX as defined in Table 12.2.1.6.3.3-13

RX_ EXCEPTIONALTX

}

sl-TxPoolScheduling-r16

Not Present

sl-TxPoolScheduling-r16 SEQUENCE {

RX_ SCHEDULINGTX

sl-PoolToAddModList-r16 SEQUENCE (SIZE (1..maxNrofTXPool-r16)) OF SL-ResourcePoolConfig-r16 {

1 entry

SL-ResourcePoolConfig-r16[1] SEQUENCE {

entry 1

sl-ResourcePoolID-r16

1

sl-ResourcePool-r16

SL-ResourcePool with condition RX_TX2 as defined in Table 12.2.1.6.3.3-13

}

}

}

sl-TxPoolExceptional-r16

Not Present

sl-TxPoolExceptional-r16 SEQUENCE {

RX_ EXCEPTIONALTX

sl-ResourcePoolID-r16

2

sl-ResourcePool-r16

SL-ResourcePool with condition EXCEPTIONAL as defined in Table 12.2.1.6.3.3-13

}

}

}

Table 12.2.1.6.3.3-10: RRCReconfigurationComplete (step 8 and step 12, Table 12.2.1.6.3.2-3)

Derivation path: TS 38.508-1 [4], Table 4.6.1-14

Table 12.2.1.6.3.3-11: RRCReconfiguration-HO (step 11, Table 12.2.1.6.3.2-3)

Derivation path: TS 38.508-1 [4], Table 4.8.1-1A with condition RBConfig_KeyChange

Information Element

Value/Remark

Comment

Condition

RRCReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

rrcReconfiguration SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

nonCriticalExtension SEQUENCE {

sl-ConfigDedicatedNR-r16

SL-ConfigDedicatedNR with condition EXCEPTIONAL as defined in Table 12.2.1.6.3.3-7

}

}

}

}

}

}

}

Table 12.2.1.6.3.3-12: SidelinkUEInformationNR (step 5, Table 12.2.1.6.3.2-3)

Derivation path: TS 38.508-1 [4], Table 4.6.1-28A with condition SIDELINK_RX

Table 12.2.1.6.3.3-13: sl-ResourcePool (Table 12.2.1.6.3.3-7)

Derivation path: TS 38.508-1 [4], Table 4.6.6-25

Information Element

Value/Remark

Comment

Condition

SL-ResourcePool-r16 ::= SEQUENCE {

sl-TimeResource-r16

1100000000

RX_TX1

sl-TimeResource-r16

0011000000

RX_TX2

sl-TimeResource-r16

0000110000

RX

sl-TimeResource-r16

0000000011

EXCEPTIONAL

}