12.2.8 Inter-carrier concurrent operation / Sidelink failure
38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification
12.2.8.1 Inter-carrier concurrent operation / Sidelink CSI reporting / Reporting
12.2.8.1.1 Test Purpose (TP)
(1)
with { UE is in connected state. UE has established PC5 RRC connection with peer UE on unicast sidelink and has sent an RRCReconfigurationSidelink message to peer UE. }
ensure that {
when { UE receives an RRCReconfigurationFailureSidelink from peer UE. }
then { UE continues to use the configuration used prior to corresponding RRCReconfigurationSidelink message and sends a SidelinkUEInformation message to indicate sidelink reconfiguration failure. }
}
12.2.8.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 38.331 [22], subclause 5.8.9.1, 5.8.10.2, 5.8.10.3, 5.8.10.4 and 5.8.10.5. Unless otherwise stated these are Rel-16 requirements.
[TS 38.331, clause 5.8.9.1.1]
Figure 5.8.9.1.1-1: Sidelink RRC reconfiguration, successful
Figure 5.8.9.1.1-2: Sidelink RRC reconfiguration, failure
The purpose of this procedure is to modify a PC5-RRC connection, e.g. to establish/modify/release sidelink DRBs, to (re-)configure NR sidelink measurement and reporting, to (re-)configure sidelink CSI reference signal resources and CSI reporting latency bound.
The UE may initiate the sidelink RRC reconfiguration procedure and perform the operation in sub-clause 5.8.9.1.2 on the corresponding PC5-RRC connection in following cases:
– the release of sidelink DRBs associated with the peer UE, as specified in sub-clause 5.8.9.1a.1;
– the establishment of sidelink DRBs associated with the peer UE, as specified in sub-clause 5.8.9.1a.2;
– the modification for the parameters included in SLRB-Config of sidelink DRBs associated with the peer UE, as specified in sub-clause 5.8.9.1a.2;
– the (re-)configuration of the peer UE to perform NR sidelink measurement and report.
– the (re-)configuration of the sidelink CSI reference signal resources and CSI reporting latency bound.
In RRC_CONNECTED, the UE applies the NR sidelink communications parameters provided in RRCReconfiguration (if any). In RRC_IDLE or RRC_INACTIVE, the UE applies the NR sidelink communications parameters provided in system information (if any). For other cases, UEs apply the NR sidelink communications parameters provided in SidelinkPreconfigNR (if any). When UE performs state transition between above three cases, the UE applies the NR sidelink communications parameters provided in the new state, after acquisition of the new configurations. Before acquisition of the new configurations, UE continues applying the NR sidelink communications parameters provided in the old state.
[TS 38.331, clause 5.8.9.1.8]
The UE shall perform the following actions upon reception of the RRCReconfigurationFailureSidelink:
1> stop timer T400 for the destination, if running;
1> continue using the configuration used prior to corresponding RRCReconfigurationSidelink message;
1> if UE is in RRC_CONNECTED:
2> perform the sidelink UE information for NR sidelink communication procedure, as specified in 5.8.3.3 or sub-clause 5.10.15 in TS 36.331 [10];
[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> if a sidelink radio link failure or a sidelink RRC reconfiguration failure has been declared, according to clauses 5.8.9.3 and 5.8.9.1.8, respectively;
5> include sl-FailureList and set its fields as follows for each destination for which it reports the NR sidelink communication failure:
6> set sl-DestinationIdentity to the destination identity configured by upper layer for NR sidelink communication transmission;
…
6> else if RRCReconfigurationFailureSidelink is received:
7> set sl-Failure as configFailure for the associated destination for the NR sidelink communication transmission;
…
1> else:
2> submit the SidelinkUEInformationNR message to lower layers for transmission.
12.2.8.1.3 Test description
12.2.8.1.3.1 Pre-test conditions
System Simulator:
– NR Cell
– NR Cell 1 is the serving cell.
– System information combination NR-14 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used in NR cell 1.
– NR-SS-UE
– NR-SS-UE 1 operating as NR sidelink communication device on the resources (i.e. the frequency included in pre-configuration) that UE is expected to use for transmission and reception via PC5 interface.
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]) except for those listed in Table 12.2.8.1.3.1-1.
Table 12.2.8.1.3.1-1: UE/ USIM configuration
USIM field |
Priority |
Value |
Access Technology Identifier |
EFUST |
As per TS 36.508 [18] clause 4.9.3.4 |
||
EFVST |
Service n°119 is "available" |
||
EFV2XP_PC5 |
As per TS 38.508-1[4] clause 4.8.3.3.3 SL-PreconfigurationNR included in V2X data policy over PC5 is defined in Table 12.2.8.1.3.3-1 |
Preamble:
– The UE is in state 3N-B as defined in TS 38.508-1 [4], subclause 4.4A, using generic procedure parameter Sidelink (On), Unicast (On), and Test Mode (On) as defined in TS 38.508-1 [4], subclause 4.5.1.
12.2.8.1.3.2 Test procedure sequence
Table 12.2.8.1.3.2-1: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS transmits a CLOSE UE TEST LOOP message to close UE test loop mode E (Transmit Mode). |
<– |
NR RRC: DLInformationTransfer TC: CLOSE UE TEST LOOP |
– |
– |
2 |
The UE transmits a CLOSE UE TEST LOOP COMPLETE message |
–> |
NR RRC: ULInformationTransfer TC: CLOSE UE TEST LOOP COMPLETE |
– |
– |
3 |
The SS transmits an RRCReconfiguration message to reconfigure SDAP entity of the established SL DRB associated to the PC5 unicast link between the UE and the NR-SS-UE 1 to sl-SDAP-Header = absent. |
<– |
NR RRC: RRCReconfiguration |
– |
– |
4 |
The UE transmits an RRCReconfigurationComplete message |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
5 |
The UE transmits an RRCReconfigurationSidelink message to reconfigure the established SL DRB associated to the PC5 unicast link between the UE and the NR-SS-UE 1. |
–> |
NR PC5 RRC: RRCReconfigurationSidelink |
– |
– |
6 |
The NR-SS-UE transmits an RRCReconfigurationFailureSidelink message |
<– |
NR RRC: RRCReconfigurationFailureSidelink |
– |
– |
7 |
Check: Does the UE transmit a SidelinkUEInfomationNR message to inform NR Cell 1 the PC5 RRC reconfiguration failure? |
–> |
NR RRC: SidelinkUEInfomationNR |
1 |
P |
8 |
Check: Does the SDAP PDUs transmitted on the established SL DRB associated to the PC5 unicast link between the UE and the NR-SS-UE 1 without SDAP header? |
– |
– |
1 |
F |
9 |
The SS transmits an OPEN UE TEST LOOP message to open UE test loop mode E. |
<– |
NR RRC: DLInformationTransfer TC: OPEN UE TEST LOOP |
– |
– |
10 |
The UE transmits an OPEN UE TEST LOOP COMPLETE message |
–> |
NR RRC: ULInformationTransfer TC: OPEN UE TEST LOOP COMPLETE |
– |
– |
12.2.8.1.3.3 Specific message contents
Table 12.2.8.1.3.3-1: CLOSE UE TEST LOOP (Table 12.2.8.1.3.2-1, Step 1)
Derivation Path: 36.508 [7] Table 4.7A-3 with condition UE TEST LOOP MODE E(V2X Transmission) |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
UE test loop mode E LB setup |
||||
Communication Transmit or Receive |
0 0 0 0 0 0 0 1 |
‘01’ indicates V2X UE triggered to transmit NR sidelink communication with single spatial layer. |
Table 12.2.8.1.3.3-2: RRCReconfiguraion (Table 12.2.8.1.3.2-1, Step 3)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition SIDELINK |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
rrcReconfiguration SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
sl-ConfigDedicatedNR-r16 CHOICE { |
||||
setup |
SL-ConfigDedicatedNR |
Table 12.2.8.1.3.3-3 |
||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
Table 12.2.8.1.3.3-3: SL-ConfigDedicatedNR (Table 12.2.8.1.3.3-2)
Derivation Path: TS 38.508-1 [4], Table 4.6.6-7 with condition SL_DRB |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
SL-ConfigDedicatedNR-r16 ::= SEQUENCE { |
||||
sl-RadioBearerToAddModList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SL-RadioBearerConfig-r16 { |
1 entry |
|||
SL-RadioBearerConfig-r16[1] SEQUENCE { |
Entry 1 |
|||
slrb-Uu-ConfigIndex-r16 |
n |
n is the SLRB-Uu-ConfigIndex of the SL-DRB associated with the PC5 unicast link between the UE and NR-SS-UE 1 |
||
sl-SDAP-Config-r16 SEQUENCE { |
||||
sl-SDAP-Header-r16 |
absent |
|||
} |
||||
} |
||||
} |
||||
} |
Table 12.2.8.1.3.3-4: RRCReconfigurationSidelink (Table 12.2.8.1.3.2-1, Step 5)
Derivation Path: TS 38.508-1 [4], Table 4.6.1A-3 with condition TX and SL_DRB |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfigurationSidelink ::= SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
rrcReconfigurationSidelink-r16 SEQUENCE { |
||||
slrb-ConfigToAddModList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SLRB-Config-r16 { |
1 entry |
|||
SLRB-Config-r16[1] SEQUENCE { |
entry 1 |
|||
sl-SDAP-ConfigPC5-r16 SEQUENCE { |
||||
sl-MappedQoS-FlowsToAddList-r16 |
Not checked |
|||
sl-SDAP-Header-r16 |
absent |
|||
} |
||||
sl-PDCP-ConfigPC5-r16 |
Not checked |
|||
sl-RLC-ConfigPC5-r16 |
Not checked |
|||
sl-MAC-LogicalChannelConfigPC5-r16 |
Not checked |
|||
} |
||||
} |
||||
} |
||||
} |
||||
} |
Table 12.2.8.1.3.3-5: RRCReconfigurationFailureSidelink (Table 12.2.8.1.3.2-1, Step 5)
Derivation Path: TS 38.508-1 [4], Table 4.6.1A-5 with condition RX |
Table 12.2.8.1.3.3-6: SidelinkUEInformationNR (Table 12.2.8.1.3.2-1, Step 7)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-28A with condition SIDELINK_TX |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
SidelinkUEInformationNR-r16 ::= SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
sidelinkUEInformationNR-r16 SEQUENCE { |
||||
sl-FailureList-r16 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-Failure-r16 { |
1 entry |
|||
SL-Failure-r16[1] SEQUENCE { |
||||
sl-DestinationIdentity-r16 |
SL-DestinationIdentity of NR-SS-UE 1 |
|||
sl-Failure-r16 |
configFailure |
|||
} |
||||
} |
||||
} |
||||
} |
||||
} |
Table 12.2.8.1.3.3-7: RRCReconfigurationSidelink (Table 12.2.8.1.3.2-1, Step 3)
Derivation Path: TS 38.508-1 [4], Table 4.6.1A-3 with condition RX and SL_CSI |
Table 12.2.8.1.3.3-8: RRCReconfigurationCompleteSidelink (Table 12.2.8.1.3.2-1, Step 4)
Derivation Path: TS 38.508-1 [4], Table 4.6.1A-4 with condition TX |
12.2.8.2 Inter-carrier concurrent operation / Sidelink failure / PC5 RRC Reconfiguration Failure / Peer UE side
12.2.8.2.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED and having established PC5-RRC connection with peer UE on unicast sidelink }
ensure that {
when { UE receives an RRCReconfigurationSidelink that UE cannot comply from peer UE }
then { UE continues to use the configuration used prior to the reception of the RRCReconfigurationSidelink message and sends a RRCReconfigurationFailureSidelink message }
}
12.2.8.2.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 38.331, clause 5.8.9.1.3. Unless otherwise stated these are Rel-16 requirements.
[TS 38.331, clause 5.8.9.1.3]
The UE shall perform the following actions upon reception of the RRCReconfigurationSidelink:
…
1> if the UE is unable to comply with (part of) the configuration included in the RRCReconfigurationSidelink (i.e. sidelink RRC reconfiguration failure):
2> continue using the configuration used prior to the reception of the RRCReconfigurationSidelink message;
2> set the content of the RRCReconfigurationFailureSidelink message;
3> submit the RRCReconfigurationFailureSidelink message to lower layers for transmission;
…
NOTE 1: When the same logical channel is configured with different RLC mode by another UE, the UE handles the case as sidelink RRC reconfiguration failure.
12.2.8.2.3 Test description
12.2.8.2.3.1 Pre-test conditions
System Simulator:
– SS-NW
– NR Cell 1
– System information combination 14 as defined in TS 38.508-1 [4] clause 4.4.3.1 is used in NR Cell 1.
– NR-SS-UE
– NR-SS-UE1: Operating as NR sidelink communication transmitting and receiving device and uses GNSS as the synchronization reference source.
– GNSS simulator
– The GNSS simulator is started and configured for Scenario #1.
UE:
– UE is authorised to perform NR sidelink communication.
– The UE is equipped with a USIM Configuration FFS as defined in TS 38.508 [4] Table FFS.
– The UE uses GNSS as the synchronization reference source.
Preamble:
– The UE is in state 3N-B RRC_CONNECTED_with_SL as defined in TS 38.508-1 [4] subclause 4.4A on NR Cell 1, using generic parameters Sidelink (On), Cast Type (Unicast), GNSS Sync (On).
12.2.8.2.3.2 Test procedure sequence
Table 12.2.8.2.3.2-1: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The NR-SS-UE1 transmits a RRCReconfigurationSidelink message that UE cannot comply on SL-SRB3. |
<– |
PC5 RRC: RRCReconfigurationSidelink |
– |
– |
2 |
Check: Does the UE transmit a RRCReconfigurationFailureSidelink message on SL-SRB3? |
–> |
PC5 RRC: RRCReconfigurationFailureSidelink |
1 |
P |
12.2.8.2.3.3 Specific message contents
FFS
12.2.8.3 Inter-carrier concurrent operation / Sidelink failure / Sidelink radio link failure / transmission side
12.2.8.3.1 Test Purpose (TP)
(1)
with { UE is in connected state. UE has established PC5 RRC connection with peer UE on unicast sidelink and has sent an RRCReconfigurationSidelink message to peer UE }
ensure that {
when { UE doesn’t receive RRCReconfigurationCompleteSidelink or RRCReconfigurationFailure before T400 expires. }
then { UE releases PC5-RRC connection and indicates the release to upper layer and sends a SidelinkUEInformationNR message to indicate SL RLF. }
}
(2)
with { UE is in connected state. UE has established PC5 RRC connection with peer UE on unicast sidelink and has established a AM SL DRB }
ensure that {
when { Retransmission number of the AM SL DRB reaches the maximum number of retransmissions. }
then { UE releases PC5-RRC connection and indicates the release to upper layer and sends a SidelinkUEInformationNR message to indicate SL RLF. }
}
(3)
with { UE is in connected state. UE has established PC5 RRC connection with peer UE on unicast sidelink. }
ensure that {
when { MAC detects that maximum number of consecutive HARQ DTX has been reached. }
then { UE releases PC5-RRC connection and indicates the release to upper layer and sends a SidelinkUEInformationNR message to indicate SL RLF. }
}
12.2.8.3.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 38.331 [22], subclause 5.8.9.1, 5.8.10.2, 5.8.10.3, 5.8.10.4 and 5.8.10.5. Unless otherwise stated these are Rel-16 requirements.
[TS 38.331, clause 5.8.9.1.1]
Figure 5.8.9.1.1-1: Sidelink RRC reconfiguration, successful
Figure 5.8.9.1.1-2: Sidelink RRC reconfiguration, failure
The purpose of this procedure is to modify a PC5-RRC connection, e.g. to establish/modify/release sidelink DRBs, to (re-)configure NR sidelink measurement and reporting, to (re-)configure sidelink CSI reference signal resources and CSI reporting latency bound.
The UE may initiate the sidelink RRC reconfiguration procedure and perform the operation in sub-clause 5.8.9.1.2 on the corresponding PC5-RRC connection in following cases:
– the release of sidelink DRBs associated with the peer UE, as specified in sub-clause 5.8.9.1a.1;
– the establishment of sidelink DRBs associated with the peer UE, as specified in sub-clause 5.8.9.1a.2;
– the modification for the parameters included in SLRB-Config of sidelink DRBs associated with the peer UE, as specified in sub-clause 5.8.9.1a.2;
– the (re-)configuration of the peer UE to perform NR sidelink measurement and report.
– the (re-)configuration of the sidelink CSI reference signal resources and CSI reporting latency bound.
In RRC_CONNECTED, the UE applies the NR sidelink communications parameters provided in RRCReconfiguration (if any). In RRC_IDLE or RRC_INACTIVE, the UE applies the NR sidelink communications parameters provided in system information (if any). For other cases, UEs apply the NR sidelink communications parameters provided in SidelinkPreconfigNR (if any). When UE performs state transition between above three cases, the UE applies the NR sidelink communications parameters provided in the new state, after acquisition of the new configurations. Before acquisition of the new configurations, UE continues applying the NR sidelink communications parameters provided in the old state.
[TS 38.331, clause 5.8.9.1.2]
The UE shall set the contents of RRCReconfigurationSidelink message as follows:
…
1> start timer T400 for the destination associated with the sidelink DRB;
…
The UE shall submit the RRCReconfigurationSidelink message to lower layers for transmission.
[TS 38.331, clause 5.8.9.3]
The UE shall:
1> upon indication from sidelink RLC entity that the maximum number of retransmissions for a specific destination has been reached; or
1> upon T400 expiry for a specific destination; or
1> upon indication from MAC entity that the maximum number of consecutive HARQ DTX for a specific destination has been reached; or
1> upon integrity check failure indication from sidelink PDCP entity concerning SL-SRB2 or SL-SRB3 for a specific destination:
2> consider sidelink radio link failure to be detected for this destination;
2> release the DRBs of this destination, in according to sub-clause 5.8.9.1a.1;
2> release the SRBs of this destination, in according to sub-clause 5.8.9.1a.3;
2> discard the NR sidelink communication related configuration of this destination;
2> reset the sidelink specific MAC of this destination;
2> consider the PC5-RRC connection is released for the destination;
2> indicate the release of the PC5-RRC connection to the upper layers for this destination (i.e. PC5 is unavailable);
2> if UE is in RRC_CONNECTED:
3> perform the sidelink UE information for NR sidelink communication procedure, as specified in 5.8.3.3;
NOTE: It is up to UE implementation on whether and how to indicate to upper layers to maintain the keep-alive procedure [55].
[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> if a sidelink radio link failure or a sidelink RRC reconfiguration failure has been declared, according to clauses 5.8.9.3 and 5.8.9.1.8, respectively;
5> include sl-FailureList and set its fields as follows for each destination for which it reports the NR sidelink communication failure:
6> set sl-DestinationIdentity to the destination identity configured by upper layer for NR sidelink communication transmission;
6> if the sidelink RLF is detected as specified in sub-clause 5.8.9.3:
7> set sl-Failure as rlf for the associated destination for the NR sidelink communication transmission;
…
1> else:
2> submit the SidelinkUEInformationNR message to lower layers for transmission.
[TS 38.322, clause 5.3.2]
…
When an RLC SDU or an RLC SDU segment is considered for retransmission, the transmitting side of the AM RLC entity shall:
– if the RLC SDU or RLC SDU segment is considered for retransmission for the first time:
– set the RETX_COUNT associated with the RLC SDU to zero.
– else, if it (the RLC SDU or the RLC SDU segment that is considered for retransmission) is not pending for retransmission already and the RETX_COUNT associated with the RLC SDU has not been incremented due to another negative acknowledgment in the same STATUS PDU:
– increment the RETX_COUNT.
– if RETX_COUNT = maxRetxThreshold:
– indicate to upper layers that max retransmission has been reached.
…
[TS 38.321, clause 5.22.1.3.3]
The HARQ-based Sidelink RLF detection procedure is used to detect Sidelink RLF based on a number of consecutive DTX on PSFCH reception occasions for a PC5-RRC connection.
RRC configures the following parameter to control HARQ-based Sidelink RLF detection:
– sl-maxNumConsecutiveDTX.
The following UE variable is used for HARQ-based Sidelink RLF detection.
– numConsecutiveDTX, which is maintained for each PC5-RRC connection.
The Sidelink HARQ Entity shall (re-)initialize numConsecutiveDTX to zero for each PC5-RRC connection which has been established by upper layers, if any, upon establishment of the PC5-RRC connection or (re)configuration of sl-maxNumConsecutiveDTX.
The Sidelink HARQ Entity shall for each PSFCH reception occasion associated to the PSSCH transmission:
1> if PSFCH reception is absent on the PSFCH reception occasion:
2> increment numConsecutiveDTX by 1;
2> if numConsecutiveDTX reaches sl-maxNumConsecutiveDTX:
3> indicate HARQ-based Sidelink RLF detection to RRC.
1> else:
2> re-initialize numConsecutiveDTX to zero.
12.2.8.3.3 Test description
12.2.8.3.3.1 Pre-test conditions
System Simulator:
– NR Cell
– NR Cell 1 is the serving cell.
– System information combination NR-14 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used in NR cell 1.
– NR-SS-UE
– NR-SS-UE 1 operating as NR sidelink communication device on the resources (i.e. the frequency included in pre-configuration) that UE is expected to use for transmission and reception via PC5 interface.
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]) except for those listed in Table 12.2.8.3.3.1-1.
Table 12.2.8.3.3.1-1: UE/ USIM configuration
USIM field |
Priority |
Value |
Access Technology Identifier |
EFUST |
As per TS 36.508 [18] clause 4.9.3.4 |
||
EFVST |
Service n°119 is "available" |
||
EFV2XP_PC5 |
As per TS 38.508-1[4] clause 4.8.3.3.3 SL-PreconfigurationNR included in V2X data policy over PC5 is defined in Table 12.2.8.3.3.3-1 |
Preamble:
– The UE is in state 3N-B as defined in TS 38.508-1 [4], subclause 4.4A, using generic procedure parameter Sidelink (On), Unicast (On), and Test Mode (On) as defined in TS 38.508-1 [4], subclause 4.5.1.
12.2.8.3.3.2 Test procedure sequence
Table 12.2.8.3.3.2-1: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS transmits a CLOSE UE TEST LOOP message to close UE test loop mode E (Transmit Mode). |
<– |
NR RRC: DLInformationTransfer TC: CLOSE UE TEST LOOP |
– |
– |
2 |
The UE transmits a CLOSE UE TEST LOOP COMPLETE message |
–> |
NR RRC: ULInformationTransfer TC: CLOSE UE TEST LOOP COMPLETE |
– |
– |
3 |
The SS transmits an RRCReconfiguration message to reconfigure PC5 RRC connection between the UE and the NR-SS-UE 1 |
<– |
NR RRC: RRCReconfiguration |
– |
– |
4 |
The UE transmits an RRCReconfigurationComplete message |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
5 |
The UE transmits an RRCReconfigurationSidelink message to reconfigure PC5 RRC connection between the UE and the NR-SS-UE 1. |
–> |
NR PC5 RRC: RRCReconfigurationSidelink |
– |
– |
6 |
The NR-SS-UE waits until T400 expires. |
– |
– |
– |
– |
7 |
Check: Does the UE transmit a SidelinkUEInfomationNR message to inform NR Cell 1 the sidelink radio link failure? |
–> |
NR RRC: SidelinkUEInfomationNR |
1 |
P |
8 |
The SS transmits an OPEN UE TEST LOOP message to open UE test loop mode E. |
<– |
NR RRC: DLInformationTransfer TC: OPEN UE TEST LOOP |
– |
– |
9 |
The UE transmits an OPEN UE TEST LOOP COMPLETE message |
–> |
NR RRC: ULInformationTransfer TC: OPEN UE TEST LOOP COMPLETE |
– |
– |
10 |
Check: Does the test result of generic test procedure in TS 38.508-1 [4] subclause 4.9.31 indicate that the UE is capable of exchanging IP data on PC5 unicast link between the UE and the NR-SS-UE 1? |
– |
– |
1 |
F |
11 |
The SS performs the generic procedure specified in subclause 4.9.22 to establish PC5 unicast link between the UE and the NR-SS-UE 1. |
– |
– |
– |
– |
12 |
The SS transmits a CLOSE UE TEST LOOP message to close UE test loop mode E (Transmit Mode). |
<– |
NR RRC: DLInformationTransfer TC: CLOSE UE TEST LOOP |
– |
– |
13 |
The UE transmits a CLOSE UE TEST LOOP COMPLETE message |
–> |
NR RRC: ULInformationTransfer TC: CLOSE UE TEST LOOP COMPLETE |
– |
– |
14 |
The NR-SS-UE 1 stops transmitting RLC acknowledgments for the RLC PDUs transmitted by the UE |
– |
– |
– |
– |
15 |
Check: Does the UE transmit a SidelinkUEInfomationNR message to inform NR Cell 1 the sidelink radio link failure? |
–> |
NR RRC: SidelinkUEInfomationNR |
2 |
P |
16 |
The SS transmits an OPEN UE TEST LOOP message to open UE test loop mode E. |
<– |
NR RRC: DLInformationTransfer TC: OPEN UE TEST LOOP |
– |
– |
17 |
The UE transmits an OPEN UE TEST LOOP COMPLETE message. |
–> |
NR RRC: ULInformationTransfer TC: OPEN UE TEST LOOP COMPLETE |
– |
– |
18 |
Check: Does the test result of generic test procedure in TS 38.508-1 [4] subclause 4.9.31 indicate that the UE is capable of exchanging IP data on PC5 unicast link between the UE and the NR-SS-UE 1? |
– |
– |
2 |
F |
19 |
The SS performs the generic procedure specified in subclause 4.9.22 to establish PC5 unicast link between the UE and the NR-SS-UE 1. |
– |
– |
– |
– |
20 |
The SS transmits a CLOSE UE TEST LOOP message to close UE test loop mode E (Transmit Mode). |
<– |
NR RRC: DLInformationTransfer TC: CLOSE UE TEST LOOP |
– |
– |
21 |
The UE transmits a CLOSE UE TEST LOOP COMPLETE message |
–> |
NR RRC: ULInformationTransfer TC: CLOSE UE TEST LOOP COMPLETE |
– |
– |
22 |
The NR-SS-UE 1 stops transmitting HARQ ACK/NACK for the MAC PDUs transmitted by the UE. |
– |
– |
– |
– |
23 |
Check: Does the UE transmit a SidelinkUEInfomationNR message to inform NR Cell 1 the sidelink radio link failure? |
–> |
NR RRC: SidelinkUEInfomationNR |
3 |
P |
24 |
The SS transmits an OPEN UE TEST LOOP message to open UE test loop mode E. |
<– |
NR RRC: DLInformationTransfer TC: OPEN UE TEST LOOP |
– |
– |
25 |
The UE transmits an OPEN UE TEST LOOP COMPLETE message |
–> |
NR RRC: ULInformationTransfer TC: OPEN UE TEST LOOP COMPLETE |
– |
– |
26 |
Check: Does the test result of generic test procedure in TS 38.508-1 [4] subclause 4.9.31 indicate that the UE is capable of exchanging IP data on PC5 unicast link between the UE and the NR-SS-UE 1? |
– |
– |
3 |
F |
12.2.8.3.3.3 Specific message contents
Table 12.2.8.3.3.3-1: CLOSE UE TEST LOOP (Table 12.2.8.3.3.2-1, Step 1, 12 and 20)
Derivation Path: 36.508 [7] Table 4.7A-3 with condition UE TEST LOOP MODE E(V2X Transmission) |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
UE test loop mode E LB setup |
||||
Communication Transmit or Receive |
0 0 0 0 0 0 0 1 |
‘01’ indicates V2X UE triggered to transmit NR sidelink communication with single spatial layer. |
Table 12.2.8.3.3.3-2: RRCReconfiguraion (Table 12.2.8.3.3.2-1, Step 3)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition SIDELINK |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfiguration ::= SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
rrcReconfiguration SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
nonCriticalExtension SEQUENCE { |
||||
sl-ConfigDedicatedNR-r16 CHOICE { |
||||
setup |
SL-ConfigDedicatedNR |
Table 12.2.8.3.3.3-3 |
||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
||||
} |
Table 12.2.8.3.3.3-3: SL-ConfigDedicatedNR (Table 12.2.8.3.3.3-2)
Derivation Path: TS 38.508-1 [4], Table 4.6.6-7 with condition SL_DRB |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
SL-ConfigDedicatedNR-r16 ::= SEQUENCE { |
||||
sl-RadioBearerToAddModList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SL-RadioBearerConfig-r16 { |
1 entry |
|||
SL-RadioBearerConfig-r16[1] SEQUENCE { |
Entry 1 |
|||
slrb-Uu-ConfigIndex-r16 |
n |
n is the SLRB-Uu-ConfigIndex of the SL-DRB associated with the PC5 unicast link between the UE and NR-SS-UE 1 |
||
sl-SDAP-Config-r16 SEQUENCE { |
||||
sl-SDAP-Header-r16 |
absent |
|||
} |
||||
} |
||||
} |
||||
} |
Table 12.2.8.3.3.3-4: RRCReconfigurationSidelink (Table 12.2.8.3.3.2-1, Step 5)
Derivation Path: TS 38.508-1 [4], Table 4.6.1A-3 with condition TX and SL_DRB |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfigurationSidelink ::= SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
rrcReconfigurationSidelink-r16 SEQUENCE { |
||||
slrb-ConfigToAddModList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SLRB-Config-r16 { |
1 entry |
|||
SLRB-Config-r16[1] SEQUENCE { |
entry 1 |
|||
sl-SDAP-ConfigPC5-r16 SEQUENCE { |
||||
sl-MappedQoS-FlowsToAddList-r16 |
Not checked |
|||
sl-SDAP-Header-r16 |
absent |
|||
} |
||||
sl-PDCP-ConfigPC5-r16 |
Not checked |
|||
sl-RLC-ConfigPC5-r16 |
Not checked |
|||
sl-MAC-LogicalChannelConfigPC5-r16 |
Not checked |
|||
} |
||||
} |
||||
} |
||||
} |
||||
} |
Table 12.2.8.3.3.3-5: SidelinkUEInformationNR (Table 12.2.8.3.3.2-1, Step 7, 15 and 23)
Derivation Path: TS 38.508-1 [4], Table 4.6.1-28A with condition SIDELINK_TX |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
SidelinkUEInformationNR-r16 ::= SEQUENCE { |
||||
criticalExtensions CHOICE { |
||||
sidelinkUEInformationNR-r16 SEQUENCE { |
||||
sl-FailureList-r16 SEQUENCE (SIZE (1..maxNrofSL-Dest-r16)) OF SL-Failure-r16 { |
1 entry |
|||
SL-Failure-r16[1] SEQUENCE { |
||||
sl-DestinationIdentity-r16 |
SL-DestinationIdentity of NR-SS-UE 1 |
|||
sl-Failure-r16 |
rlf |
|||
} |
||||
} |
||||
} |
||||
} |
||||
} |