specification/stage-3/05_Idle_and_Inactive_Mode/05.02 System Information.md

@@ -40,16 +40,16 @@ The UE shall ensure having a valid version of the posSIB requested by upper laye
 
 ##### 5.2.2.2.1 SIB validity
 
-The UE shall apply the SI acquisition procedure as defined in clause 5.2.2.3 upon cell selection (e.g. upon power on), cell-reselection, return from out of coverage, after reconfiguration with sync completion, after entering the network from another RAT, upon receiving an indication that the system information has changed, upon receiving a PWS notification, upon receiving request (e.g., a positioning request) from upper layers; and whenever the UE does not have a valid version of a stored SIB or posSIB or a valid version of a requested SIB.
-The UE shall apply the SI acquisition procedure as defined in clause  upon cell selection (e.g. upon power on), cell-reselection, return from out of coverage, after reconfiguration with sync completion, after entering the network from another RAT, upon receiving an indication that the system information has changed, upon receiving a PWS notification, upon receiving request (e.g., a positioning request) from upper layers; and whenever the UE does not have a valid version of a stored SIB or posSIB or a valid version of a requested SIB.
+The UE shall apply the SI acquisition procedure as defined in clause 5.2.2.3 upon cell selection (e.g., upon power on), cell-reselection, return from out of coverage, after reconfiguration with sync completion, after entering the network from another RAT, upon receiving an indication that the system information has changed, upon receiving a PWS notification, upon receiving request (e.g., a positioning request) from upper layers; and whenever the UE does not have a valid version of a stored SIB or posSIB or a valid version of a requested SIB.
+The UE shall apply the SI acquisition procedure as defined in clause  upon cell selection (e.g., upon power on), cell-reselection, return from out of coverage, after reconfiguration with sync completion, after entering the network from another RAT, upon receiving an indication that the system information has changed, upon receiving a PWS notification, upon receiving request (e.g., a positioning request) from upper layers; and whenever the UE does not have a valid version of a stored SIB or posSIB or a valid version of a requested SIB.
 
-When the UE acquires a *MIB* or a *SIB1* or an SI message in a serving cell as described in clause 5.2.2.3, and if the UE stores the acquired SIB, then the UE shall store the associated *areaScope*, if present, the first *PLMN-Identity* in the *PLMN-IdentityInfoList* for non-NPN-only cells or the first NPN identity (SNPN identity in case of SNPN, or PNI-NPN identity in case of PNI-NPN) in the *NPN-IdentityInfoList* for NPN-only cells, the *cellIdentity*, the *systemInformationAreaID*, if present, and the *valueTag*, if present, as indicated in the *si-SchedulingInfo* for the SIB. If the UE stores the acquired posSIB, then the UE shall store the associated *areaScope*, if present, the *cellIdentity*, the *systemInformationAreaID*, if present, the *valueTag*, if provided in *assistanceDataSIB-Element*, and the *expirationTime* if provided in *assistanceDataSIB-Element*. The UE may use a valid stored version of the SI except *MIB*, *SIB1*, *SIB6*, *SIB7* or *SIB8* e.g. after cell re-selection, upon return from out of coverage or after the reception of SI change indication. The *valueTag* and *expirationTime* for posSIB is optionally provided in *assistanceDataSIB-Element*, as specified in TS 37.355 \[49\].
+When the UE acquires a *MIB*, a *SIB1* or an SI message in a serving cell as described in clause 5.2.2.3, and if the UE stores the acquired SIB, then the UE shall store the associated *areaScope*, if present, the first *PLMN-Identity* in the *PLMN-IdentityInfoList* for non-NPN-only cells or the first NPN identity (SNPN identity in case of SNPN, or PNI-NPN identity in case of PNI-NPN) in the *NPN-IdentityInfoList* for NPN-only cells, the *cellIdentity*, the *systemInformationAreaID*, if present, and the *valueTag*, if present, as indicated in the *si-SchedulingInfo* for the SIB. If the UE stores the acquired posSIB, then the UE shall store the associated *areaScope*, if present, the *cellIdentity*, the *systemInformationAreaID*, if present, the *valueTag*, if provided in *assistanceDataSIB-Element*, and the *expirationTime* if provided in *assistanceDataSIB-Element*. The UE may use a valid stored version of the SI except *MIB*, *SIB1*, *SIB6*, *SIB7* or *SIB8* e.g. after cell re-selection, upon return from out of coverage or after the reception of SI change indication. The *valueTag* and *expirationTime* for posSIB is optionally provided in *assistanceDataSIB-Element*, as specified in TS 37.355 \[49\].
 
 A L2 U2N Remote UE in RRC_IDLE or RRC_INACTIVE can inform the interested SIB(s) to the connected L2 U2N Relay UE as defined in clause 5.8.9.8.2 and receive the SIB(s) from the L2 U2N Relay UE as defined in clause 5.8.9.9.3. A L2 U2N Remote UE in RRC_CONNECTED receives SIB1 and other SIB(s) in *RRCReconfiguration* message and performs on-demand SI request if required, as defined in clause 5.2.2.3.5 and 5.2.2.3.6. The L2 U2N Remote UE in RRC_IDLE or RRC_INACTIVE or RRC_CONNECTED (when MP is not configured) is not required to obtain SI over Uu interface, but it may decide to perform the SI acquisition procedure over Uu interface as defined in clause 5.2.2.3 by UE implementation.
 
 *NOTE*: The storage and management of the stored SIBs in addition to the SIBs valid for the current serving cell is left to UE implementation.
 
-The UE shall:
+The UE shall (including in case of success failure):
 
 - delete any stored version of a SIB after 3 hours from the moment it was successfully confirmed as valid;
 

specification/stage-3/06_Connection_Control/06.01 Connection Setup.md

@@ -20,9 +20,9 @@ The purpose of this procedure is to establish an RRC connection between the UE a
 
 #### 6.1.1.2 Initiation
 
-The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in RRC_IDLE and it has acquired essential system information (or when it performs the procedures for another feature).
+The UE initiates the procedure when upper layers request establishment of an RRC connection while the UE is in RRC_IDLE and it has acquired essential system information (or when it performs the procedures for another feature or when it performs successful failure).
 
-The UE shall ensure having valid and up to date essential system information as specified in clause 5.2.2.2 before initiating this procedure.
+The UE shall ensure having valid and up to date essential SI as specified in clause 5.2.2.2 before initiating this procedure.
 
 Upon initiation of the procedure, the UE shall also:
 
@@ -47,3 +47,9 @@ Upon reception of the [*ConnectionFailure*](../06_Connection_Control/asn1/Uu-6G-
 - stop timer T300;
 - reset MAC;
 - continue operation in RRC_IDLE, upon which the procedure ends.
+
+Upon reception of the [*ConnectionFailure*](../06_Connection_Control/asn1/Uu-6G-ConnectionControl.asn) message including successFailure, the UE shall:
+
+- start timer T300;
+- reset MAC;
+- continue operation in RRC_IDLE, upon which the procedure ends.
\ No newline at end of file

specification/stage-3/06_Connection_Control/asn1/Uu-6G-ConnectionControl.asn

@@ -32,7 +32,7 @@ ConnectionFailure ::= SEQUENCE {
 
 
 ConnectionFailure-r19 ::= SEQUENCE {
-    anotherFeature ENUMERATED {anotherParameter, spare7, spare6, spare5, spare4, spare3, spare2, spare1 },
+    successReason ENUMERATED {nocongestion, spare7, spare6, spare5, spare4, spare3, spare2, spare1 },
     nonCriticalExtensions SEQUENCE { } OPTIONAL
 }