From a5bd4f0fadf60a6e1f68721c5b139e44affd3613 Mon Sep 17 00:00:00 2001 From: josilo Date: Wed, 26 Feb 2025 13:58:09 +0000 Subject: [PATCH 1/6] abbreviation and missing comma --- .../05_Idle_and_Inactive_Mode/05.02 System Information.md | 4 ++-- .../stage-3/06_Connection_Control/06.01 Connection Setup.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/specification/stage-3/05_Idle_and_Inactive_Mode/05.02 System Information.md b/specification/stage-3/05_Idle_and_Inactive_Mode/05.02 System Information.md index c541131..83f636c 100644 --- a/specification/stage-3/05_Idle_and_Inactive_Mode/05.02 System Information.md +++ b/specification/stage-3/05_Idle_and_Inactive_Mode/05.02 System Information.md @@ -40,8 +40,8 @@ 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\]. diff --git a/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md b/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md index 6aa1fa2..678dbc1 100644 --- a/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md +++ b/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. +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 SI. -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: -- GitLab From 60db1604e01296f4e13e16cff53d1845dd9238ac Mon Sep 17 00:00:00 2001 From: Lian Araujo Date: Mon, 17 Mar 2025 09:30:39 +0000 Subject: [PATCH 2/6] Added further editorial aspects --- .../05_Idle_and_Inactive_Mode/05.02 System Information.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specification/stage-3/05_Idle_and_Inactive_Mode/05.02 System Information.md b/specification/stage-3/05_Idle_and_Inactive_Mode/05.02 System Information.md index 83f636c..210e96c 100644 --- a/specification/stage-3/05_Idle_and_Inactive_Mode/05.02 System Information.md +++ b/specification/stage-3/05_Idle_and_Inactive_Mode/05.02 System Information.md @@ -43,7 +43,7 @@ The UE shall ensure having a valid version of the posSIB requested by upper laye 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. -- GitLab From fc6223323f6841513307d527dc7bccb776ea09b1 Mon Sep 17 00:00:00 2001 From: Lian Araujo Date: Tue, 18 Mar 2025 07:55:59 +0000 Subject: [PATCH 3/6] initial-changes-for-success-wi --- .../05_Idle_and_Inactive_Mode/05.02 System Information.md | 2 +- .../stage-3/06_Connection_Control/06.01 Connection Setup.md | 6 ++++++ .../06_Connection_Control/asn1/Uu-6G-ConnectionControl.asn | 6 ++++++ 3 files changed, 13 insertions(+), 1 deletion(-) diff --git a/specification/stage-3/05_Idle_and_Inactive_Mode/05.02 System Information.md b/specification/stage-3/05_Idle_and_Inactive_Mode/05.02 System Information.md index 35b0f83..1bba694 100644 --- a/specification/stage-3/05_Idle_and_Inactive_Mode/05.02 System Information.md +++ b/specification/stage-3/05_Idle_and_Inactive_Mode/05.02 System Information.md @@ -49,7 +49,7 @@ A L2 U2N Remote UE in RRC_IDLE or RRC_INACTIVE can inform the interested SIB(s) *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; diff --git a/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md b/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md index 3b05bf2..b6543cd 100644 --- a/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md +++ b/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md @@ -46,4 +46,10 @@ 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 diff --git a/specification/stage-3/06_Connection_Control/asn1/Uu-6G-ConnectionControl.asn b/specification/stage-3/06_Connection_Control/asn1/Uu-6G-ConnectionControl.asn index 909cfb5..9906bac 100644 --- a/specification/stage-3/06_Connection_Control/asn1/Uu-6G-ConnectionControl.asn +++ b/specification/stage-3/06_Connection_Control/asn1/Uu-6G-ConnectionControl.asn @@ -27,6 +27,12 @@ EstablishmentCause ::= ENUMERATED { ConnectionFailure ::= SEQUENCE { failureReason ENUMERATED {congestion, spare7, spare6, spare5, spare4, spare3, spare2, spare1 }, + nonCriticalExtensions ConnectionFailure-r19 OPTIONAL +} + + +ConnectionFailure-r19 ::= SEQUENCE { + successReason ENUMERATED {nocongestion, spare7, spare6, spare5, spare4, spare3, spare2, spare1 }, nonCriticalExtensions SEQUENCE { } OPTIONAL } -- GitLab From 7ef32dbbdbd37888a1dfe62fc31d1fca47a22d36 Mon Sep 17 00:00:00 2001 From: Lian Araujo Date: Tue, 18 Mar 2025 08:14:41 +0000 Subject: [PATCH 4/6] Update file 06.01 Connection Setup.md --- .../stage-3/06_Connection_Control/06.01 Connection Setup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md b/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md index b6543cd..cb93415 100644 --- a/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md +++ b/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md @@ -20,7 +20,7 @@ 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. +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 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. -- GitLab From ad715ad4979a04ccf975f588fdbcc510f928dd3a Mon Sep 17 00:00:00 2001 From: Lian Araujo Date: Tue, 18 Mar 2025 20:37:31 +0000 Subject: [PATCH 5/6] Update 2 files - /specification/stage-3/06_Connection_Control/asn1/Uu-6G-ConnectionControl.asn - /specification/stage-3/06_Connection_Control/06.01 Connection Setup.md --- .../stage-3/06_Connection_Control/06.01 Connection Setup.md | 2 +- .../06_Connection_Control/asn1/Uu-6G-ConnectionControl.asn | 6 ++++++ 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md b/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md index 3b05bf2..e728cbd 100644 --- a/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md +++ b/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md @@ -20,7 +20,7 @@ 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. +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 shall ensure having valid and up to date essential system information as specified in clause 5.2.2.2 before initiating this procedure. diff --git a/specification/stage-3/06_Connection_Control/asn1/Uu-6G-ConnectionControl.asn b/specification/stage-3/06_Connection_Control/asn1/Uu-6G-ConnectionControl.asn index 909cfb5..451e4bb 100644 --- a/specification/stage-3/06_Connection_Control/asn1/Uu-6G-ConnectionControl.asn +++ b/specification/stage-3/06_Connection_Control/asn1/Uu-6G-ConnectionControl.asn @@ -27,6 +27,12 @@ EstablishmentCause ::= ENUMERATED { ConnectionFailure ::= SEQUENCE { failureReason ENUMERATED {congestion, spare7, spare6, spare5, spare4, spare3, spare2, spare1 }, + nonCriticalExtensions ConnectionFailure-r19 OPTIONAL +} + + +ConnectionFailure-r19 ::= SEQUENCE { + anotherFeature ENUMERATED {anotherParameter, spare7, spare6, spare5, spare4, spare3, spare2, spare1 }, nonCriticalExtensions SEQUENCE { } OPTIONAL } -- GitLab From d78f285e6b18e50f96c8e39ab96960dd3a55f8c8 Mon Sep 17 00:00:00 2001 From: Lian Araujo Date: Tue, 18 Mar 2025 21:32:57 +0000 Subject: [PATCH 6/6] Update 2 files - /specification/stage-3/06_Connection_Control/06.01 Connection Setup.md - /specification/stage-3/05_Idle_and_Inactive_Mode/05.02 System Information.md --- .../05_Idle_and_Inactive_Mode/05.02 System Information.md | 2 +- .../stage-3/06_Connection_Control/06.01 Connection Setup.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/specification/stage-3/05_Idle_and_Inactive_Mode/05.02 System Information.md b/specification/stage-3/05_Idle_and_Inactive_Mode/05.02 System Information.md index 35b0f83..b30c9bb 100644 --- a/specification/stage-3/05_Idle_and_Inactive_Mode/05.02 System Information.md +++ b/specification/stage-3/05_Idle_and_Inactive_Mode/05.02 System Information.md @@ -4,7 +4,7 @@ System Information (SI) is divided into the *MIB* and a number of SIBs and posSIBs where: -- the *MIB* is always transmitted on the BCH with a periodicity of 80 ms and repetitions made within 80 ms (TS 38.212 \[17\], clause 7.1) and it includes parameters that are needed to acquire *SIB1* from the cell. The first transmission of the *MIB* is scheduled in subframes as defined in TS 38.213 \[13\], clause 4.1 and repetitions are scheduled according to the period of SSB; +- the *MIB* is always transmitted on the BCH with a periodicity of 80 ms and repetitions made within 80 ms (TS 38.212 \[17\], clause 7.1) and it includes parameters that are needed to acquire *SIB1* from the cell. The first transmission of the *MIB* is scheduled in subframes as defined in TS 38.213 \[13\], clause 4.1 and repetitions are re-scheduled according to the period of SSB; **NOTE** 1: If the period of SSB is larger than 20 ms, the MIB is transmitted with the same periodicity as that of SSB. diff --git a/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md b/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md index e728cbd..3da0347 100644 --- a/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md +++ b/specification/stage-3/06_Connection_Control/06.01 Connection Setup.md @@ -24,7 +24,7 @@ The UE initiates the procedure when upper layers request establishment of an RRC 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. -Upon initiation of the procedure, the UE shall: +Upon initiation of the procedure, the UE shall also: - perform the unified access control procedure as specified in 5.3.14 using the Access Category and Access Identities provided by upper layers; -- GitLab