From 5ac965abd286a6f05712321b76fa49e94f401c78 Mon Sep 17 00:00:00 2001 From: "doyou89.jung" Date: Thu, 13 Dec 2018 15:36:16 +0900 Subject: [PATCH] update the text file of F1AP spec to v15.3.0 --- .../{38473-f11.txt => 38473-f30.txt} | 5655 +++++++++++++++-- 1 file changed, 5134 insertions(+), 521 deletions(-) rename pycrate_asn1dir/3GPP_NR_F1AP_38473/{38473-f11.txt => 38473-f30.txt} (52%) diff --git a/pycrate_asn1dir/3GPP_NR_F1AP_38473/38473-f11.txt b/pycrate_asn1dir/3GPP_NR_F1AP_38473/38473-f30.txt similarity index 52% rename from pycrate_asn1dir/3GPP_NR_F1AP_38473/38473-f11.txt rename to pycrate_asn1dir/3GPP_NR_F1AP_38473/38473-f30.txt index 93af751..8473fdb 100644 --- a/pycrate_asn1dir/3GPP_NR_F1AP_38473/38473-f11.txt +++ b/pycrate_asn1dir/3GPP_NR_F1AP_38473/38473-f30.txt @@ -5,160 +5,265 @@ Contents -Foreword 6 -1 Scope 7 -2 References 7 -3 Definitions and abbreviations 8 -3.1 Definitions 8 -3.2 Abbreviations 9 -4 General 9 -4.1 Procedure specification principles 9 -4.2 Forwards and backwards compatibility 9 -4.3 Specification notations 10 -5 F1AP services 10 -6 Services expected from signalling transport 10 -7 Functions of F1AP 10 -8 F1AP procedures 10 -8.1 List of F1AP Elementary procedures 10 -8.2 Interface Management procedures 11 -8.2.1 Reset 11 -8.2.1.1 General 11 -8.2.1.2 Successful Operation 12 -8.2.1.2.1 Reset Procedure Initiated from the gNB-CU 12 -8.2.1.2.2 Reset Procedure Initiated from the gNB-DU 13 -8.2.1.3 Abnormal Conditions 13 -8.2.2 Error Indication 14 -8.2.2.1 General 14 -8.2.2.2 Successful Operation 14 -8.2.2.3 Abnormal Conditions 14 -8.2.3 F1 Setup 14 -8.2.3.1 General 14 -8.2.3.2 Successful Operation 15 -8.2.3.3 Unsuccessful Operation 15 -8.2.3.4 Abnormal Conditions 15 -8.2.4 gNB-DU Configuration Update 16 -8.2.4.1 General 16 -8.2.4.2 Successful Operation 16 -8.2.4.3 Unsuccessful Operation 17 -8.2.4.4 Abnormal Conditions 17 -8.2.5 gNB-CU Configuration Update 17 -8.2.5.1 General 17 -8.2.5.2 Successful Operation 17 -8.2.5.3 Unsuccessful Operation 18 -8.2.5.4 Abnormal Conditions 18 -8.3 UE Context Management procedures 18 -8.3.1 UE Context Setup 18 -8.3.1.1 General 18 -8.3.1.2 Successful Operation 18 -8.3.1.3 Unsuccessful Operation 19 -8.3.1.4 Abnormal Conditions 20 -8.3.2 UE Context Release Request (gNB-DU initiated) 20 -8.3.2.1 General 20 -8.3.2.2 Successful Operation 20 -8.3.2.3 Abnormal Conditions 20 -8.3.3 UE Context Release (gNB-CU initiated) 20 -8.3.3.1 General 20 -8.3.3.2 Successful Operation 21 -8.3.3.4 Abnormal Conditions 21 -8.3.4 UE Context Modification (gNB-CU initiated) 21 -8.3.4.1 General 21 -8.3.4.2 Successful Operation 21 -8.3.4.3 Unsuccessful Operation 23 -8.3.4.4 Abnormal Conditions 23 -8.3.5 UE Context Modification Required (gNB-DU initiated) 23 -8.3.5.1 General 23 -8.3.5.2 Successful Operation 23 -8.3.5.3 Abnormal Conditions 24 -8.4 RRC Message Transfer procedures 24 -8.4.1 Void 24 -8.4.2 DL RRC Message Transfer 24 -8.4.2.1 General 24 -8.4.2.2 Successful operation 24 -8.4.2.3 Abnormal Conditions 24 -8.4.3 UL RRC Message Transfer 25 -8.4.3.1 General 25 -8.4.3.2 Successful operation 25 -8.4.3.3 Abnormal Conditions 25 -9 Elements for F1AP Communication 25 -9.1 General 25 -9.2 Message Functional Definition and Content 26 -9.2.1 Interface Management messages 26 -9.2.1.1 RESET 26 -9.2.1.2 RESET ACKNOWLEDGE 26 -9.2.1.3 ERROR INDICATION 27 -9.2.1.4 F1 SETUP REQUEST 27 -9.2.1.5 F1 SETUP RESPONSE 27 -9.2.1.6 F1 SETUP FAILURE 28 -9.2.1.7 GNB-DU CONFIGURATION UPDATE 28 -9.2.1.8 GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE 29 -9.2.1.9 GNB-DU CONFIGURATION UPDATE FAILURE 30 -9.2.1.10 GNB-CU CONFIGURATION UPDATE 30 -9.2.1.11 GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE 30 -9.2.1.12 GNB-CU CONFIGURATION UPDATE FAILURE 31 -9.2.2 UE Context Management messages 31 -9.2.2.1 UE CONTEXT SETUP REQUEST 31 -9.2.2.2 UE CONTEXT SETUP RESPONSE 33 -9.2.2.3 UE CONTEXT SETUP FAILURE 35 -9.2.2.4 UE CONTEXT RELEASE REQUEST 35 -9.2.2.5 UE CONTEXT RELEASE COMMAND 35 -9.2.2.6 UE CONTEXT RELEASE COMPLETE 36 -9.2.2.7 UE CONTEXT MODIFICATION REQUEST 36 -9.2.2.8 UE CONTEXT MODIFICATION RESPONSE 38 -9.2.2.9 UE CONTEXT MODIFICATION FAILURE 40 -9.2.2.10 UE CONTEXT MODIFICATION REQUIRED 40 -9.2.2.11 UE CONTEXT MODIFICATION CONFIRM 41 -9.2.3 RRC Message Transfer messages 43 -9.2.3.1 Void 43 -9.2.3.2 DL RRC MESSAGE TRANSFER 43 -9.2.3.3 UL RRC MESSAGE TRANSFER 43 -9.3 Information Element Definitions 43 -9.3.1 Radio Network Layer Related IEs 43 -9.3.1.1 Message Type 43 -9.3.1.2 Cause 43 -9.3.1.3 Criticality Diagnostics 45 -9.3.1.4 gNB-CU UE F1AP ID 46 -9.3.1.5 gNB-DU UE F1AP ID 46 -9.3.1.6 RRC-Container 47 -9.3.1.7 SRB ID 47 -9.3.1.8 DRB ID 47 -9.3.1.9 gNB-DU ID 47 -9.3.1.10 Served Cell Information 47 -9.3.1.11 Transmission Stop Indicator 48 -9.3.1.12 NR CGI 48 -9.3.1.13 Time To wait 49 -9.3.1.14 PLMN Identity 49 -9.3.1.15 Transmission Bandwidth 49 -9.3.1.16 Void 49 -9.3.1.17 NR ARFCN 49 -9.3.1.18 gNB-DU System Information 50 -9.3.1.19 E-UTRAN QoS 50 -9.3.1.20 Allocation and Retention Priority 50 -9.3.1.21 GBR QoS Information 51 -9.3.1.22 Bit Rate 52 -9.3.1.23 Transaction ID 52 -9.3.1.24 DRX Cycle 52 -9.3.1.25 CU to DU RRC Information 53 -9.3.1.26 DU to CU RRC Information 53 -9.3.1.27 RLC Mode 53 -9.3.1.28 SUL Information 53 -9.3.1.29 Extended-TAC 54 -9.3.1.30 RRC Reconfiguration Complete Indicator 54 -9.3.1.31 UL Configuration 54 -9.3.2 Transport Network Layer Related IEs 54 -9.3.2.1 GTP Tunnel Endpoint 54 -9.4 Message and Information Element Abstract Syntax (with ASN.1) 55 -9.4.1 General 55 -9.4.2 Usage of private message mechanism for non-standard use 55 -9.4.3 Elementary Procedure Definitions 56 -9.4.4 PDU Definitions 60 -9.4.5 Information Element Definitions 81 -9.4.6 Common Definitions 97 -9.4.7 Constant Definitions 97 -9.4.8 Container Definitions 101 -9.5 Message Transfer Syntax 105 -9.6 Timers 105 -10 Handling of unknown, unforeseen and erroneous protocol data 105 -Annex A (informative): Change History 106 +Foreword 8 +1 Scope 9 +2 References 9 +3 Definitions and abbreviations 10 +3.1 Definitions 10 +3.2 Abbreviations 11 +4 General 11 +4.1 Procedure specification principles 11 +4.2 Forwards and backwards compatibility 12 +4.3 Specification notations 12 +5 F1AP services 12 +6 Services expected from signalling transport 12 +7 Functions of F1AP 12 +8 F1AP procedures 13 +8.1 List of F1AP Elementary procedures 13 +8.2 Interface Management procedures 14 +8.2.1 Reset 14 +8.2.1.1 General 14 +8.2.1.2 Successful Operation 14 +8.2.1.2.1 Reset Procedure Initiated from the gNB-CU 14 +8.2.1.2.2 Reset Procedure Initiated from the gNB-DU 15 +8.2.1.3 Abnormal Conditions 16 +8.2.2 Error Indication 16 +8.2.2.1 General 16 +8.2.2.2 Successful Operation 16 +8.2.2.3 Abnormal Conditions 16 +8.2.3 F1 Setup 16 +8.2.3.1 General 16 +8.2.3.2 Successful Operation 17 +8.2.3.3 Unsuccessful Operation 17 +8.2.3.4 Abnormal Conditions 18 +8.2.4 gNB-DU Configuration Update 18 +8.2.4.1 General 18 +8.2.4.2 Successful Operation 18 +8.2.4.3 Unsuccessful Operation 19 +8.2.4.4 Abnormal Conditions 19 +8.2.5 gNB-CU Configuration Update 19 +8.2.5.1 General 19 +8.2.5.2 Successful Operation 19 +8.2.5.3 Unsuccessful Operation 21 +8.2.5.4 Abnormal Conditions 21 +8.2.6 gNB-DU Resource Coordination 21 +8.2.6.1 General 21 +8.2.6.2 Successful Operation 21 +8.2.7 gNB-DU Status Indication 22 +8.2.7.1 General 22 +8.2.7.2 Successful Operation 22 +8.2.7.3 Abnormal Conditions 22 +8.3 UE Context Management procedures 22 +8.3.1 UE Context Setup 22 +8.3.1.1 General 22 +8.3.1.2 Successful Operation 23 +8.3.1.3 Unsuccessful Operation 25 +8.3.1.4 Abnormal Conditions 25 +8.3.2 UE Context Release Request (gNB-DU initiated) 25 +8.3.2.1 General 25 +8.3.2.2 Successful Operation 25 +8.3.2.3 Abnormal Conditions 26 +8.3.3 UE Context Release (gNB-CU initiated) 26 +8.3.3.1 General 26 +8.3.3.2 Successful Operation 26 +8.3.3.4 Abnormal Conditions 26 +8.3.4 UE Context Modification (gNB-CU initiated) 26 +8.3.4.1 General 26 +8.3.4.2 Successful Operation 27 +8.3.4.3 Unsuccessful Operation 29 +8.3.4.4 Abnormal Conditions 29 +8.3.5 UE Context Modification Required (gNB-DU initiated) 30 +8.3.5.1 General 30 +8.3.5.2 Successful Operation 30 +8.3.5.3 Abnormal Conditions 30 +8.3.6 UE Inactivity Notification 30 +8.3.6.1 General 30 +8.3.6.2 Successful Operation 31 +8.3.6.3 Abnormal Conditions 31 +8.3.7 Notify 31 +8.3.7.1 General 31 +8.3.7.2 Successful Operation 31 +8.3.7.3 Abnormal Conditions 31 +8.4 RRC Message Transfer procedures 32 +8.4.1 Initial UL RRC Message Transfer 32 +8.4.1.1 General 32 +8.4.1.2 Successful operation 32 +8.4.1.3 Abnormal Conditions 32 +8.4.2 DL RRC Message Transfer 32 +8.4.2.1 General 32 +8.4.2.2 Successful operation 32 +8.4.2.3 Abnormal Conditions 33 +8.4.3 UL RRC Message Transfer 33 +8.4.3.1 General 33 +8.4.3.2 Successful operation 33 +8.4.3.3 Abnormal Conditions 33 +8.5 Warning Message Transmission Procedures 34 +8.5.1 Write-Replace Warning 34 +8.5.1.1 General 34 +8.5.1.2 Successful Operation 34 +8.5.1.3 Unsuccessful Operation 34 +8.5.1.4 Abnormal Conditions 34 +8.5.2 PWS Cancel 34 +8.5.2.1 General 34 +8.5.2.2 Successful Operation 35 +8.5.1.3 Unsuccessful Operation 35 +8.5.3 PWS Restart Indication 35 +8.5.3.1 General 35 +8.5.3.2 Successful Operation 35 +8.5.3.3 Abnormal Conditions 35 +8.5.4 PWS Failure Indication 36 +8.5.4.1 General 36 +8.5.4.2 Successful Operation 36 +8.5.4.3 Abnormal Conditions 36 +8.6 System Information Procedures 36 +8.6.1 System Information Delivery 36 +8.6.1.1 General 36 +8.6.1.2 Successful Operation 36 +8.6.1.3 Abnormal Conditions 37 +8.7 Paging procedures 37 +8.7.1 Paging 37 +8.7.1.1 General 37 +8.7.1.2 Successful Operation 37 +8.7.1.3 Abnormal Conditions 37 +9 Elements for F1AP Communication 37 +9.1 General 37 +9.2 Message Functional Definition and Content 38 +9.2.1 Interface Management messages 38 +9.2.1.1 RESET 38 +9.2.1.2 RESET ACKNOWLEDGE 38 +9.2.1.3 ERROR INDICATION 39 +9.2.1.4 F1 SETUP REQUEST 39 +9.2.1.5 F1 SETUP RESPONSE 40 +9.2.1.6 F1 SETUP FAILURE 41 +9.2.1.7 GNB-DU CONFIGURATION UPDATE 41 +9.2.1.8 GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE 42 +9.2.1.9 GNB-DU CONFIGURATION UPDATE FAILURE 43 +9.2.1.10 GNB-CU CONFIGURATION UPDATE 43 +9.2.1.11 GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE 45 +9.2.1.12 GNB-CU CONFIGURATION UPDATE FAILURE 46 +9.2.1.13 GNB-DU RESOURCE COORDINATION REQUEST 46 +9.2.1.14 GNB-DU RESOURCE COORDINATION RESPONSE 47 +9.2.1.15 GNB-DU STATUS INDICATION 47 +9.2.2 UE Context Management messages 48 +9.2.2.1 UE CONTEXT SETUP REQUEST 48 +9.2.2.2 UE CONTEXT SETUP RESPONSE 51 +9.2.2.3 UE CONTEXT SETUP FAILURE 53 +9.2.2.4 UE CONTEXT RELEASE REQUEST 53 +9.2.2.5 UE CONTEXT RELEASE COMMAND 53 +9.2.2.6 UE CONTEXT RELEASE COMPLETE 54 +9.2.2.7 UE CONTEXT MODIFICATION REQUEST 54 +9.2.2.8 UE CONTEXT MODIFICATION RESPONSE 58 +9.2.2.9 UE CONTEXT MODIFICATION FAILURE 60 +9.2.2.10 UE CONTEXT MODIFICATION REQUIRED 61 +9.2.2.11 UE CONTEXT MODIFICATION CONFIRM 62 +9.2.2.12 UE INACTIVITY NOTIFCATION 63 +9.2.2.13 NOTIFY 64 +9.2.3 RRC Message Transfer messages 64 +9.2.3.1 INITIAL UL RRC MESSAGE TRANSFER 64 +9.2.3.2 DL RRC MESSAGE TRANSFER 65 +9.2.3.3 UL RRC MESSAGE TRANSFER 66 +9.2.4 Warning Message Transmission Messages 66 +9.2.4.1 WRITE-REPLACE WARNING REQUEST 66 +9.2.4.2 WRITE-REPLACE WARNING RESPONSE 66 +9.2.4.3 PWS CANCEL REQUEST 67 +9.2.4.4 PWS CANCEL RESPONSE 67 +9.2.4.5 PWS RESTART INDICATION 68 +9.2.4.6 PWS FAILURE INDICATION 68 +9.2.5 System Information messages 69 +9.2.5.1 SYSTEM INFORMATION DELIVERY COMMAND 69 +9.2.6 Paging messages 69 +9.2.6.1 PAGING 69 +9.3 Information Element Definitions 70 +9.3.1 Radio Network Layer Related IEs 70 +9.3.1.1 Message Type 70 +9.3.1.2 Cause 70 +9.3.1.3 Criticality Diagnostics 73 +9.3.1.4 gNB-CU UE F1AP ID 73 +9.3.1.5 gNB-DU UE F1AP ID 73 +9.3.1.6 RRC-Container 74 +9.3.1.7 SRB ID 74 +9.3.1.8 DRB ID 74 +9.3.1.9 gNB-DU ID 74 +9.3.1.10 Served Cell Information 74 +9.3.1.11 Transmission Stop Indicator 75 +9.3.1.12 NR CGI 75 +9.3.1.13 Time To wait 76 +9.3.1.14 PLMN Identity 76 +9.3.1.15 Transmission Bandwidth 76 +9.3.1.16 Void 76 +9.3.1.17 NR Frequency Info 77 +9.3.1.18 gNB-DU System Information 77 +9.3.1.19 E-UTRAN QoS 78 +9.3.1.20 Allocation and Retention Priority 78 +9.3.1.21 GBR QoS Information 78 +9.3.1.22 Bit Rate 79 +9.3.1.23 Transaction ID 79 +9.3.1.24 DRX Cycle 79 +9.3.1.25 CU to DU RRC Information 80 +9.3.1.26 DU to CU RRC Information 80 +9.3.1.27 RLC Mode 81 +9.3.1.28 SUL Information 81 +9.3.1.29 5GS TAC 82 +9.3.1.29a Configured EPS TAC 82 +9.3.1.30 RRC Reconfiguration Complete Indicator 82 +9.3.1.31 UL Configuration 82 +9.3.1.32 C-RNTI 82 +9.3.1.33 Cell UL Configured 83 +9.3.1.34 RAT-Frequency Priority Information 83 +9.3.1.35 LCID 83 +9.3.1.36 Duplication activation 83 +9.3.1.37 Slice Support List 83 +9.3.1.38 S-NSSAI 84 +9.3.1.39 UE Identity Index value 84 +9.3.1.40 Paging DRX 84 +9.3.1.41 Paging Priority 84 +9.3.1.42 gNB-CU System Information 84 +9.3.1.43 RAN UE Paging identity 85 +9.3.1.44 CN UE Paging Identity 85 +9.3.1.45 QoS Flow Level QoS Parameters 85 +9.3.1.46 GBR QoS Flow Information 86 +9.3.1.47 Dynamic 5QI Descriptor 87 +9.3.1.48 NG-RAN Allocation and Retention Priority 88 +9.3.1.49 Non Dynamic 5QI Descriptor 88 +9.3.1.50 Maximum Packet Loss Rate 89 +9.3.1.51 Packet Delay Budget 89 +9.3.1.52 Packet Error Rate 89 +9.3.1.53 Averaging Window 89 +9.3.1.54 Maximum Data Burst Volume 90 +9.3.1.55 Masked IMEISV 90 +9.3.1.56 Notification Control 90 +9.3.1.57 RAN Area Code 90 +9.3.1.58 PWS System Information 90 +9.3.1.59 Repetition Period 91 +9.3.1.60 Number of Broadcasts Requested 91 +9.3.1.61 Void 91 +9.3.1.62 SIType List 91 +9.3.1.63 QoS Flow Indicator 91 +9.3.1.64 Served E-UTRA Cell Information 92 +9.3.1.65 Available PLMN List 92 +9.3.1.66 RLC Failure Indication 92 +9.3.1.67 Uplink TxDirectCurrentList Information 92 +9.3.1.68 Cell Status 93 +9.3.1.69 RLC Status 93 +9.3.1.70 RRC Version 93 +9.3.2 Transport Network Layer Related IEs 94 +9.3.2.1 UP Transport Layer Information 94 +9.3.2.2 GTP-TEID 94 +9.3.2.3 Transport Layer Address 94 +9.3.2.4 CP Transport Layer Information 94 +9.4 Message and Information Element Abstract Syntax (with ASN.1) 95 +9.4.1 General 95 +9.4.2 Usage of private message mechanism for non-standard use 95 +9.4.3 Elementary Procedure Definitions 96 +9.4.4 PDU Definitions 103 +9.4.5 Information Element Definitions 133 +9.4.6 Common Definitions 163 +9.4.7 Constant Definitions 164 +9.4.8 Container Definitions 169 +9.5 Message Transfer Syntax 173 +9.6 Timers 173 +10 Handling of unknown, unforeseen and erroneous protocol data 173 +Annex A (informative): Change History 174 Foreword This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). @@ -195,6 +300,13 @@ The following documents contain provisions which, through reference in this text [15] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP)". [16] 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification". [17] 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception". +[18] 3GPP TS 29.281: "General Packet Radio System (GPRS); Tunnelling Protocol User Plane (GTPv1-U) ". +[19] 3GPP TS 38.414: "NG-RAN; NG data transport". +[20] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2". +[21] 3GPP TS 23.501: "System Architecture for the 5G System". +[22] 3GPP TS 38.472: "NG-RAN; F1 signalling transport". +[23] 3GPP TS 23.003: "Numbering, addressing and identification". +[24] 3GPP TS 38.304: " NR; User Equipment (UE) procedures in Idle mode and RRC Inactive state ". 3 Definitions and abbreviations 3.1 Definitions elementary procedure: F1AP consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of interaction between gNB-CU and gNB-DU. These Elementary Procedures are defined separately and are intended to be used to build up complete sequences in a flexible manner. If the independence between some EPs is restricted, it is described under the relevant EP description. Unless otherwise stated by the restrictions, the EPs may be invoked independently of each other as standalone procedures, which can be active in parallel. The usage of several F1AP EPs together is specified in stage 2 specifications (e.g., TS 38.470 [2]). @@ -210,28 +322,36 @@ Unsuccessful: Successful and Unsuccessful: - One signalling message reports both successful and unsuccessful outcome for the different included requests. The response message used is the one defined for successful outcome. Class 2 EPs are considered always successful. -gNB: as defined in TS 38.300 [6] -gNB-CU: as defined in TS 38.401 [4] -gNB-CU UE F1AP ID: as defined in TS 38.401 [4]. -gNB-DU: as defined in TS 38.401 [4] +EN-DC operation: Used in this specification when the F1AP is applied for gNB-CU and gNB-DU in E-UTRAN. +gNB: as defined in TS 38.300 [6]. +gNB-CU: as defined in TS 38.401 [4]. +gNB-CU UE F1AP ID: as defined in TS 38.401 [4]. +gNB-DU: as defined in TS 38.401 [4]. gNB-DU UE F1AP ID: as defined in TS 38.401 [4]. -en-gNB: as defined in TS 37.340 [7] +en-gNB: as defined in TS 37.340 [7]. UE-associated signalling: When F1AP messages associated to one UE uses the UE-associated logical F1-connection for association of the message to the UE in gNB-DU and gNB-CU. UE-associated logical F1-connection: The UE-associated logical F1-connection uses the identities GNB-CU UE F1AP ID and GNB-DU UE F1AP ID according to the definition in TS 38.401 [4]. For a received UE associated F1AP message the gNB-CU identifies the associated UE based on the GNB-CU UE F1AP ID IE and the gNB-DU identifies the associated UE based on the GNB-DU UE F1AP ID IE. The UE-associated logical F1-connection may exist before the F1 UE context is setup in gNB-DU. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. +5GC 5G Core Network +5QI 5G QoS Identifier +AMF Access and Mobility Management Function CN Core Network -GTP GPRS Tunnelling Protocol -IE Information Element -NR CGI NR Cell Global Identifier +CG Cell Group +CGI Cell Global Identifier +CP Control Plane +DL Downlink +EN-DC E-UTRA-NR Dual Connectivity +EPC Evolved Packet Core +IMEISV International Mobile station Equipment Identity and Software Version number +NSSAI Network Slice Selection Assistance Information +RANAC RAN Area Code RRC Radio Resource Control -SCTP Stream Control Transmission Protocol +S-NSSAI Single Network Slice Selection Assistance Information SUL Supplementary Uplink -TEID Tunnel Endpoint Identifier -UE User Equipment -UL Uplink - +TAC Tracking Area Code +TAI Tracking Area Identity 4 General 4.1 Procedure specification principles The principle for specifying the procedure logic is to specify the functional behaviour of the terminating node exactly and completely. Any rule that specifies the behaviour of the originating node shall be possible to be verified with information that is visible within the system. @@ -303,6 +423,18 @@ UE Context Modification Required (gNB-DU initiated) UE CONTEXT MODIFICATION REQUIRED UE CONTEXT MODIFICATION CONFIRM +Write-Replace Warning +WRITE-REPLACE WARNING REQUEST +WRITE-REPLACE WARNING RESPONSE + +PWS Cancel +PWS CANCEL REQUEST +PWS CANCEL RESPONSE + +GNB-DU RESOURCE COORDINATION +GNB-DU RESOURCE COORDINATION REQUEST +GNB-DU RESOURCE COORDINATION RESPONSE + Table 2: Class 2 procedures Elementary Procedure @@ -311,10 +443,26 @@ Error Indication ERROR INDICATION UE Context Release Request (gNB-DU initiated) UE CONTEXT RELEASE REQUEST +Initial UL RRC Message Transfer +INITIAL UL RRC MESSAGE TRANSFER DL RRC Message Transfer DL RRC MESSAGE TRANSFER UL RRC Message Transfer UL RRC MESSAGE TRANSFER +UE Inactivity Notification +UE INACTIVITY NOTIFICATION +System Information Delivery +SYSTEM INFORMATION DELIVERY COMMAND +Paging +PAGING +Notify +NOTIFY +PWS Restart Indication +PWS RESTART INDICATION +PWS Failure Indication +PWS FAILURE INDICATION +gNB-DU Status Indication +GNB-DU STATUS INDICATION 8.2 Interface Management procedures 8.2.1 Reset @@ -366,15 +514,20 @@ The ERROR INDICATION message shall contain at least either the Cause IE or the C Not applicable. 8.2.3 F1 Setup 8.2.3.1 General -The purpose of the F1 Setup procedure is to exchange application level data needed for the gNB-DU and the gNB-CU to correctly interoperate on the F1 interface. This procedure shall be the first F1AP procedure triggered after the TNL association has become operational. The procedure uses non-UE associated signalling. +The purpose of the F1 Setup procedure is to exchange application level data needed for the gNB-DU and the gNB-CU to correctly interoperate on the F1 interface. This procedure shall be the first F1AP procedure triggered after a TNL association has become operational. The procedure uses non-UE associated signalling. This procedure erases any existing application level configuration data in the two nodes and replaces it by the one received. This procedure also re-initialises the F1AP UE-related contexts (if any) and erases all related signalling connections in the two nodes like a Reset procedure would do. 8.2.3.2 Successful Operation Figure 8.2.3.2-1: F1 Setup procedure: Successful Operation The gNB-DU initiates the procedure by sending a F1 SETUP REQUEST message including the appropriate data to the gNB-CU. The gNB-CU responds with a F1 SETUP RESPONSE message including the appropriate data. -If the F1 SETUP REQUEST message contains the gNB-DU Name IE the gNB-CU may use this IE as a human readable name of the gNB-DU. +If the F1 SETUP REQUEST message contains the gNB-DU Name IE, the gNB-CU may use this IE as a human readable name of the gNB-DU. +If the F1 SETUP REQUEST message contains the gNB-DU Served Cells List IE, the gNB-CU shall take into account as specified in TS 38.401 [4]. +For NG-RAN, the gNB-DU shall include the gNB-DU System Information IE and the TAI Slice Support List IE. The gNB-CU may include the Cells to be Activated List IE in the F1 SETUP RESPONSE message. The Cells to be Activated List IE includes a list of cells that the gNB-CU requests the gNB-DU to activate. The gNB-DU shall activate the cells included in the Cells to be Activated List IE and reconfigure the physical cell identity for cells for which the NR PCI IE is included. -The exchanged data shall be stored in respective node and used for the duration of the TNL association. When this procedure is finished, the F1 interface is operational and other F1 messages can be exchanged. +For NG-RAN, the gNB-CU shall include the gNB-CU System Information IE in the F1 SETUP RESPONSE message. +The exchanged data shall be stored in respective node and used as long as there is an operational TNL association. When this procedure is finished, the F1 interface is operational and other F1 messages may be exchanged. +For NG-RAN, the gNB-DU may include the RAN Area Code IE in the F1 SETUP REQUEST message. The gNB-CU may use it according to TS 38.300 [6]. +For NG-RAN, the gNB-CU may include Available PLMN List IE if the available PLMN(s) are different from what gNB-DU has provided in F1 SETUP REQUEST message, gNB-DU shall take this into account and only broadcast the PLMN(s) included in this received Available PLMN List IE. 8.2.3.3 Unsuccessful Operation Figure 8.2.3.3-1: F1 Setup procedure: Unsuccessful Operation @@ -384,18 +537,21 @@ If the F1 SETUP FAILURE message includes the Time To Wait IE, the gNB-DU shall w If the gNB-DU cannot activate cell(s) indicated by Cells to be Activated List Item IE in the F1 SETUP RESPONSE message, the gNB-DU shall initiate gNB-DU Configuration Update procedure to indicate the cell(s) that are currently active. 8.2.4 gNB-DU Configuration Update 8.2.4.1 General -The purpose of the gNB-DU Configuration Update procedure is to update application level configuration data needed for the gNB-DU and the gNB-CU to interoperate correctly on the F1 interface. This procedure does not affect existing UE-related contexts, if any. +The purpose of the gNB-DU Configuration Update procedure is to update application level configuration data needed for the gNB-DU and the gNB-CU to interoperate correctly on the F1 interface. This procedure does not affect existing UE-related contexts, if any. The procedure uses non-UE associated signalling. 8.2.4.2 Successful Operation Figure 8.2.4.2-1: gNB-DU Configuration Update procedure: Successful Operation The gNB-DU initiates the procedure by sending a GNB-DU CONFIGURATION UPDATE message to the gNB-CU including an appropriate set of updated configuration data that it has just taken into operational use. The gNB-CU responds with GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message to acknowledge that it successfully updated the configuration data. -The updated configuration data shall be stored in both nodes and used for the duration of the TNL association or until any further update is performed. -If Served Cells To Add Item IE is contained in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU shall add cell information according to the information in the Served Cell Information IE. +The updated configuration data shall be stored in both nodes and used as long as there is an operational TNL association or until any further update is performed. +If Served Cells To Add Item IE is contained in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU shall add cell information according to the information in the Served Cell Information IE. For NG-RAN, the gNB-DU shall include the gNB-DU System Information IE. If Served Cells To Modify Item IE is contained in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU shall modify information of cell indicated by Old NR CGI IE according to the information in the Served Cell Information IE. Further, if the gNB-DU System Information IE is present the gNB-CU shall store and replace any previous information received. If Served Cells To Delete Item IE is contained in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU shall delete information of cell indicated by Old NR CGI IE. -If Active Cells Item IE is contained in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU shall update the information about the cells that are currently active. If the Active Cells List is present and does not contain any cells, the gNB-CU shall assume that there are currently no active cells. +If Cells Status Item IE is contained in the GNB-DU CONFIGURATION UPDATE message, the gNB-CU shall update the information about the cells. If Cells to be Activated Item IE is contained in the GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message, the gNB-DU shall activate the cell indicated by NR CGI IE and reconfigure the physical cell identity for cells for which the NR PCI IE is included. If Cells to be Activated List Item IE is contained in the GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message and the indicated cells are already activated, the gNB-DU shall update the cell information received in Cells to be Activated List Item IE. +For NG-RAN, the gNB-CU shall include the gNB-CU System Information IE in the GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message. +For NG-RAN, the gNB-DU may include the RAN Area Code IE in the GNB-DU CONFIGURATION UPDATE message. The gNB-CU shall store and replace any previously provided RAN Area Code IE by the received RAN Area Code IE. +If Available PLMN List IE is contained in GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message, the gNB-DU shall update the available PLMN list and the corresponding system information. 8.2.4.3 Unsuccessful Operation Figure 8.2.4.3-1: gNB-DU Configuration Update procedure: Unsuccessful Operation @@ -405,15 +561,26 @@ If the GNB-DU CONFIGURATION UPDATE FAILURE message includes the Time To Wait IE, If the gNB-DU cannot activate cell(s) indicated by Cells to be Activated List Item IE in the GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message, the gNB-DU shall initiate gNB-DU Configuration Update procedure to indicate the cell(s) that are currently active. 8.2.5 gNB-CU Configuration Update 8.2.5.1 General -The purpose of the gNB-CU Configuration Update procedure is to update application level configuration data needed for the gNB-DU and gNB-CU to interoperate correctly on the F1 interface. This procedure does not affect existing UE-related contexts, if any. +The purpose of the gNB-CU Configuration Update procedure is to update application level configuration data needed for the gNB-DU and gNB-CU to interoperate correctly on the F1 interface. This procedure does not affect existing UE-related contexts, if any. The procedure uses non-UE associated signalling. 8.2.5.2 Successful Operation Figure 8.2.5.2-1: gNB-CU Configuration Update procedure: Successful Operation The gNB-CU initiates the procedure by sending a GNB-CU CONFIGURATION UPDATE message including the appropriate updated configuration data to the gNB-DU. The gNB-DU responds with a GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message to acknowledge that it successfully updated the configuration data. -The updated configuration data shall be stored in the respective node and used for the duration of the TNL association or until any further update is performed. +The updated configuration data shall be stored in the respective node and used as long as there is an operational TNL association or until any further update is performed. If Cells to be Activated List Item IE is contained in the GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall activate the cell indicated by NR CGI IE and reconfigure the physical cell identity for which the NR PCI IE is included. If Cells to be Deactivated List Item IE is contained in the GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall deactivate the cell indicated by NR CGI IE. If Cells to be Activated List Item IE is contained in the GNB-CU CONFIGURATION UPDATE message and the indicated cells are already activated, the gNB-DU shall update the cell information received in Cells to be Activated List Item IE. +If the gNB-CU TNL Association To Add List IE is contained in the gNB-CU CONFIGURATION UPDATE message, the gNB-DU shall, if supported, use it to establish the TNL association(s) with the gNB-CU. The gNB-DU shall report to the gNB-CU, in the gNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message, the successful establishment of the TNL association(s) with the gNB-CU as follows: +- A list of TNL address(es) with which the gNB-DU successfully established the TNL association shall be included in the gNB-CU TNL Association Setup List IE; +- A list of TNL address(es) with which the gNB-DU failed to establish the TNL association shall be included in the gNB-CU TNL Association Failed To Setup List IE. +If the gNB-CU TNL Association To Remove List IE is contained in the gNB-CU CONFIGURATION UPDATE message the gNB-DU shall, if supported, initiate removal of the TNL association(s) indicated by the received gNB-CU Transport Layer Address towards the gNB-CU. +If the gNB-CU TNL Association To Update List IE is contained in the gNB-CU CONFIGURATION UPDATE message the gNB-DU shall, if supported, overwrite the previously stored information for the related TNL Association. +If the TNL usage IE or the TNL Association Weight Factor IE is included in the gNB-CU TNL Association To Add List IE or the gNB-CU TNL Association To Update List IE, the gNB-DU node shall, if supported, use it as described in TS 38.472 [22]. +For NG-RAN, the gNB-CU shall include the gNB-CU System Information IE in the GNB-CU CONFIGURATION UPDATE message. +If Protected E-UTRA Resources List IE is contained in the GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall protect the corresponding resource of the cells indicated by List of E-UTRA Cells IE for spectrum sharing between E-UTRA and NR. +If the GNB-CU CONFIGURATION UPDATE message contains the Protected E-UTRA Resource Indication IE, the receiving gNB-DU should forward it to lower layers and use it for cell-level resource coordination. The gNB-DU shall consider the received Protected E-UTRA Resource Indication IE when expressing its desired resource allocation during gNB-DU Resource Coordination procedure. The gNB-DU shall consider the received Protected E-UTRA Resource Indication IE content valid until reception of a new update of the IE for the same gNB-DU. +If Available PLMN List IE is contained in GNB-CU CONFIGURATION UPDATE message, the gNB-DU shall update the available PLMN list and the corresponding system information. +If Cells Failed to be Activated Item IE is contained in the GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message, the gNB-CU shall consider that the indicated cells are inactive as defined in TS 38.401 [4]. 8.2.5.3 Unsuccessful Operation Figure 8.2.5.3-1: gNB-CU Configuration Update: Unsuccessful Operation @@ -421,6 +588,25 @@ If the gNB-DU cannot accept the update, it shall respond with a GNB-CU CONFIGURA If the GNB-CU CONFIGURATION UPDATE FAILURE message includes the Time To Wait IE, the gNB-CU shall wait at least for the indicated time before reinitiating the GNB-CU CONFIGURATION UPDATE message towards the same gNB-DU. 8.2.5.4 Abnormal Conditions Not applicable. +8.2.6 gNB-DU Resource Coordination +8.2.6.1 General +The purpose of the gNB-DU Resource Coordination procedure is to enable coordination of radio resource allocation between a gNB-CU and a gNB-DU for the purpose of spectrum sharing between E-UTRA and NR. This procedure is to be used only for the purpose of spectrum sharing between E-UTRA and NR. +The procedure uses non-UE-associated signalling. +8.2.6.2 Successful Operation + +Figure 8.2.6.2-1: gNB-DU Resource Coordination, successful operation +A gNB-CU initiates the procedure by sending the GNB-DU RESOURCE COORDINATION REQUEST message to a gNB-DU over the F1 interface. The gNB-DU extracts the E-UTRA – NR Cell Resource Coordination Request Container IE and it replies by sending the GNB-DU RESOURCE COORDINATION RESPONSE message. In case of E-UTRA-initiated gNB-DU Resource Coordination procedure, the E-UTRA – NR Cell Resource Coordination Request Container in the GNB-DU RESOURCE COORDINATION REQUEST message and the E-UTRA – NR Cell Resource Coordination Response Container in the GNB-DU RESOURCE COORDINATION RESPONSE message shall be included. +In case of NR-initiated gNB-DU Resource Coordination procedure, the E-UTRA – NR Cell Resource Coordination Response Container in the GNB-DU RESOURCE COORDINATION RESPONSE message shall be included. +8.2.7 gNB-DU Status Indication +8.2.7.1 General +The purpose of the gNB-DU Status Indication procedure is informing the gNB-CU that the gNB-DU is overloaded so that overload reduction actions can be applied. The procedure uses non-UE associated signalling. +8.2.7.2 Successful Operation + +Figure 8.2.7.2-1: gNB-DU Status Indication procedure +If the gNB-DU Overload Information IE in the GNB-DU STATUS INDICATION message indicates that the gNB-DU is overloaded, the gNB-CU shall apply overload reduction actions until informed, with a new GNB-DU STATUS INDICATION message, that the overload situation has ceased. +The detailed overload reduction policy is up to gNB-CU implementation. +8.2.7.3 Abnormal Conditions +Void. 8.3 UE Context Management procedures 8.3.1 UE Context Setup 8.3.1.1 General @@ -428,30 +614,47 @@ The purpose of the UE Context Setup procedure is to establish the UE Context inc 8.3.1.2 Successful Operation Figure 8.3.1.2-1: UE Context Setup Request procedure: Successful Operation -The gNB-CU initiates the procedure by sending UE CONTEXT SETUP REQUEST message to the gNB-DU. If the gNB-DU succeeds to establish the UE context, it replies to the gNB-CU with UE CONTEXT SETUP RESPONSE. -If the SCell To Be Setup List IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall act as specified in TS 38.401 [4]. +The gNB-CU initiates the procedure by sending UE CONTEXT SETUP REQUEST message to the gNB-DU. If the gNB-DU succeeds to establish the UE context, it replies to the gNB-CU with UE CONTEXT SETUP RESPONSE. If no UE-associated logical F1-connection exists, the UE-associated logical F1-connection shall be established as part of the procedure. +If the SpCell UL Configured IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall configure UL for the indicated SpCell accordingly. +If the SCell To Be Setup List IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall act as specified in TS 38.401 [4]. If the SCell UL Configured IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall configure UL for the indicated SCell accordingly. If the DRX Cycle IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall use the provided value from the gNB-CU. If the UL Configuration IE in DRB to Be Setup Item IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall take it into account for UL scheduling. -If the SRB To Be Setup List IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall act as specified in TS 38.401 [4]. -If two UL GTP Tunnel Endpoint IEs are included in UE CONTEXT SETUP REQUEST message for a DRB, gNB-DU shall include two DL GTP Tunnel Endpoint IEs in UE CONTEXT SETUP RESPONSE message. gNB-CU and gNB-DU use the UL GTP Tunnel Endpoint IEs and DL GTP Tunnel Endpoint IEs to support packet duplication for intra-gNB-DU CA as defined in TS 38.470 [2]. +If the SRB To Be Setup List IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall act as specified in TS 38.401 [4]. If Duplication Indication IE is contained in the SRB To Be Setup List IE, the gNB-DU shall, if supported, setup two RLC entities for the indicated SRB. +If the DRB To Be Setup List IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall act as specified in TS 38.401 [4]. +If two UL UP TNL Information IEs are included in UE CONTEXT SETUP REQUEST message for a DRB, gNB-DU shall include two DL UP TNL Information IEs in UE CONTEXT SETUP RESPONSE message. gNB-CU and gNB-DU use the UL UP TNL Information IEs and DL UP TNL Information IEs to support packet duplication for intra-gNB-DU CA as defined in TS 38.470 [2]. +If Duplication Activation IE is included in the UE CONTEXT SETUP REQUEST message for a DRB, gNB-DU should take it into account when activing/deactiving CA based PDCP duplication for the DRB. +If DC Based Duplication Configured IE is included in the UE CONTEXT SETUP REQUEST message for a DRB, gNB-DU shall regard that DC based PDCP duplication is configured for this DRB and it should take the responsibility of PDCP duplication activation/deactivation. If DC Based Duplication Activation IE is included in the UE CONTEXT SETUP REQUEST message for a DRB, gNB-DU should take it into account when activing/deactiving DC based PDCP duplication for this DRB. +For EN-DC operation, and if the Subscriber Profile ID for RAT/Frequency priority IE is received from an MeNB, the UE CONTEXT SETUP REQUEST message shall contain the Subscriber Profile ID for RAT/Frequency priority IE. The gNB-DU shall store the received Subscriber Profile ID for RAT/Frequency priority in the UE context and use it as defined in TS 36.300 [20]. +If the Index to RAT/Frequency Selection Priority IE is available at the gNB-CU, the Index to RAT/Frequency Selection Priority IE shall be included in the UE CONTEXT SETUP REQUEST. The gNB-DU may use it for RRM purposes. The gNB-DU shall report to the gNB-CU, in the UE CONTEXT SETUP RESPONSE message, the result for all the requested DRBs and SRBs in the following way: - A list of DRBs which are successfully established shall be included in the DRB Setup List IE; - A list of DRBs which failed to be established shall be included in the DRB Failed to Setup List IE; - A list of SRBs which failed to be established shall be included in the SRB Failed to Setup List IE. When the gNB-DU reports the unsuccessful establishment of a DRB or SRB, the cause value should be precise enough to enable the gNB-CU to know the reason for the unsuccessful establishment. -For EN-DC operation, the gNB-CU shall include the E-UTRAN QoS IE. The allocation of resources according to the values of the Allocation and Retention Priority IE included in the E-UTRAN QoS IE shall follow the principles described for the E-RAB Setup procedure in TS 36.413 [15]. -For EN-DC operation, the CG-ConfigInfo IE shall be included in the CU to DU RRC Information IE. +For EN-DC operation, the gNB-CU shall include in the UE CONTEXT SETUP REQUEST the E-UTRAN QoS IE. The allocation of resources according to the values of the Allocation and Retention Priority IE included in the E-UTRAN QoS IE shall follow the principles described for the E-RAB Setup procedure in TS 36.413 [15]. +For NG-RAN operation, the gNB-CU shall include in the UE CONTEXT SETUP REQUEST the DRB Information IE. +For DC operation, the CG-ConfigInfo IE shall be included in the CU to DU RRC Information IE. +For EN-DC operation, if the gNB-CU includes the SMTC information of the measured frequency(ies) in the MeasurementTimingConfiguration IE of the CU to DU RRC Information IE that is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall generate the measurement gaps based on the received SMTC information. Then the gNB-DU shall send the measurement gaps information to the gNB-CU in the MeasGapConfig IE of the DU to CU RRC Information IE that is included in the UE CONTEXT SETUP RESPONSE message. If the gNB-CU received the MeNB Resource Coordination Information as defined in TS 36.423 [9], it shall transparently transfer it to the gNB-DU via the Resource Coordination Transfer Container IE in the UE CONTEXT SETUP REQUEST message. The gNB-DU shall use the information received in the Resource Coordination Transfer Container IE for reception of MeNB Resource Coordination Information at the gNB acting as secondary node as described in TS 36.423 [9]. If the Resource Coordination Transfer Container IE is included in the UE CONTEXT SETUP RESPONSE, the gNB-CU shall transparently transfer this information for the purpose of resource coordination as described in TS 36.423 [9]. +If the Masked IMEISV IE is contained in the UE CONTEXT SETUP REQUEST message the gNB-DU shall, if supported, use it to determine the characteristics of the UE for subsequent handling. If the SCell Failed To Setup List IE is contained in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall regard the corresponding SCell(s) failed to be established with an appropriate cause value for each SCell failed to setup. +If the Inactivity Monitoring Request IE is contained in the UE CONTEXT SETUP REQUEST message, gNB-DU may consider that the gNB-CU has requested the gNB-DU to perform UE inactivity monitoring. If the Inactivity Monitoring Response IE is contained in the UE CONTEXT SETUP RESPONSE message and set to "Not-supported", the gNB-CU shall consider that the gNB-DU does not support UE inactivity monitoring for the UE. +If the Full Configuration IE is contained in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall consider that the gNB-DU has generated the CellGroupConfig IE using full configuration. +If the C-RNTI IE is included in the UE CONTEXT SETUP RESPONSE, the gNB-CU shall consider that the C-RNTI has been allocated by the gNB-DU for this UE context. +The UE Context Setup Procedure is not used to configure SRB0. +If the UE CONTEXT STEUP REQUEST message contains the RRC-Container IE, the gNB-DU shall send the corresponding RRC message to the UE via SRB1. +If the Notification Control IE is included in the DRB to Be Setup List IE and it is set to active, the gNB-DU shall, if supported, monitor the QoS of the DRB and notify the gNB-CU if the QoS cannot be fulfilled any longer or if the QoS can be fulfilled again. The Notification Control IE can only be applied to GBR bearers. +If the UL PDU Session Aggregate Maximum Bit Rate IE is included in the QoS Flow Level QoS Parameters IE containded in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall store the received UL PDU Session Aggregate Maximum Bit Rate and use it for non-GBR Bearers for the concerned PDU sessions and the concerned UE as specified in TS 23.501 [21]. +The gNB-CU shall inlcude the gNB-DU UE Aggregate Maximum Bit Rate Uplink IE in the UE CONTEXT SETUP REQUEST message. The gNB-DU shall use the received gNB-DU UE Aggregate Maximum Bit Rate Uplink for non-GBR Bearers for the concerned UE. 8.3.1.3 Unsuccessful Operation Figure 8.3.1.3-1: UE Context Setup Request procedure: unsuccessful Operation If the gNB-DU is not able to establish an F1 UE context, or cannot even establish one bearer it shall consider the procedure as failed and reply with the UE CONTEXT SETUP FAILURE message. -If the gNB-DU is not able to accept the SpCell ID IE in UE CONTEXT SETUP REQUEST message, it shall reply with the UE CONTEXT SETUP FAILURE message with an appropriate cause value. Further, if the Candidate SpCell List IE is included in the UE CONTEXT SETUP REQUEST message and the gNB-DU is not able to accept the SpCell ID IE, the gNB-DU shall, if supported, include the Potential SpCell List IE in the UE CONTEXT SETUP FAILURE message and the gNB-CU should take this into account for selection of an opportune SpCell. If the Potential SpCell List IE is present but no Potential SpCell Item IE is present, the gNB-CU should assume that none of the cells in the Candidate SpCell List IE are acceptable for the gNB-DU. +If the gNB-DU is not able to accept the SpCell ID IE in UE CONTEXT SETUP REQUEST message, it shall reply with the UE CONTEXT SETUP FAILURE message with an appropriate cause value. Further, if the Candidate SpCell List IE is included in the UE CONTEXT SETUP REQUEST message and the gNB-DU is not able to accept the SpCell ID IE, the gNB-DU shall, if supported, include the Potential SpCell List IE in the UE CONTEXT SETUP FAILURE message and the gNB-CU should take this into account for selection of an opportune SpCell. The gNB-DU shall include the cells in the Potential SpCell List IE in a priority order, where the first cell in the list is the one most desired and the last one is the one least desired (e.g., based on load conditions). If the Potential SpCell List IE is present but no Potential SpCell Item IE is present, the gNB-CU should assume that none of the cells in the Candidate SpCell List IE are acceptable for the gNB-DU. 8.3.1.4 Abnormal Conditions Not applicable. -8.3.2 UE Context Release Request (gNB-DU initiated) +8.3.2 UE Context Release Request (gNB-DU initiated) 8.3.2.1 General The purpose of the UE Context Release Request procedure is to enable the gNB-DU to request the gNB-CU to release the UE-associated logical F1-connection. The procedure uses UE-associated signalling. 8.3.2.2 Successful Operation @@ -471,6 +674,10 @@ The purpose of the UE Context Release procedure is to enable the gNB-CU to order Figure 8.3.3.2-1: UE Context Release (gNB-CU initiated) procedure. Successful operation The gNB-CU initiates the procedure by sending the UE CONTEXT RELEASE COMMAND message to the gNB-DU. Upon reception of the UE CONTEXT RELEASE COMMAND message, the gNB-DU shall release all related signalling and user data transport resources and reply with the UE CONTEXT RELEASE COMPLETE message. +If the old gNB-DU UE F1AP ID IE is included in the UE CONTEXT RELEASE COMMAND message, the gNB-DU shall additionally release the UE context associated with the old gNB-DU UE F1AP ID. +If the UE CONTEXT RELEASE COMMAND message includes the Execute Duplication IE, the gNB-DU shall perform CA based duplication, if configured, for the SRB for the included RRC-Container IE. +Interactions with UE Context Setup procedure: +The UE Context Release procedure may be performed before the UE Context Setup procedure to release an existing UE-associated logical F1-connection and related resources in the gNB-DU, e.g. when gNB-CU rejects UE access it shall trigger UE Context Release procedure with the cause value of UE rejection. 8.3.3.4 Abnormal Conditions Not applicable. 8.3.4 UE Context Modification (gNB-CU initiated) @@ -480,16 +687,23 @@ The purpose of the UE Context Modification procedure is to modify the establishe Figure 8.3.4.2-1: UE Context Modification procedure. Successful operation The F1AP UE CONTEXT MODIFICATION REQUEST message is initiated by the gNB-CU. -If the SpCell ID IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall replace any previously received value and act as specified in TS 38.401 [4]. -If the SCell To Be Setup List IE or SCell To Be Removed List IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall act as specified in TS 38.401 [4]. -If the DRX Cycle IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall use the provided value from the gNB-CU. -If the SRB To Be Setup List IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall act as specified in the TS 38.401 [4]. +If the SpCell ID IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall replace any previously received value and regard it as a reconfiguration with sync as defined in TS 38.331 [8]. If the ServCellIndex IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall take this into account for the indicated SpCell. If the SpCell UL Configured IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall configure UL for the indicated SpCell accordingly. +If the SCell To Be Setup List IE or SCell To Be Removed List IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall act as specified in TS 38.401 [4]. If the SCell To Be Setup List IE is included in the UE CONTEXT MODIFICATION REQUEST message and the indicated SCell(s) are already setup, the gNB-DU shall replace any previously received value. If the SCell UL Configured IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall configure UL for the indicated SCell accordingly. +If the DRX Cycle IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall use the provided value from the gNB-CU. If the DRX configuration indicator IE is contained in the UE CONTEXT MODIFICATION REQUEST message and set to "release", the gNB-DU shall release DRX configuration. +If the SRB To Be Setup List IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall act as specified in the TS 38.401 [4], and replace any previously received value. If Duplication Indication IE is contained in the SRB To Be Setup List IE, the gNB-DU shall, if supported, setup two RLC entities for the indicated SRB. If the DRB To Be Setup List IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall act as specified in the TS 38.401 [4]. -If two UL GTP Tunnel Endpoint IEs are included in UE CONTEXT MODIFICATION REQUEST message for a DRB, gNB-DU shall include two DL GTP Tunnel Endpoint IEs in UE CONTEXT MODIFICATION RESPONSE message. gNB-CU and gNB-DU use the UL GTP Tunnel Endpoint IEs and DL GTP Tunnel Endpoint IEs to support packet duplication for intra-gNB-DU CA as defined in TS 38.470 [2]. -If the UL Configuration IE in DRB to Be Setup Item IE or DRB to Be Modified Item IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall take it into account for UL scheduling. The gNB-CU may include the RRC Reconfiguration Complete Indicator IE in the UE CONTEXT MODIFICATION REQUEST message to inform the gNB-DU that the ongoing reconfiguration procedure has been successfully performed by the UE. The gNB-DU does not need to wait for this confirmation for using the new UE configuration or taking other actions towards the UE. It is up to gNB-DU implementation when to use the new UE configuration configured. -If the UE CONTEXT MODIFICATION REQUEST message contains the RRC-Container IE, the gNB-DU shall send the corresponding RRC message to the UE. -If the UE CONTEXT MODIFICATION REQUEST message contains the Transmission Stop Indicator IE, the gNB-DU shall stop data transmission for the UE. It is up to gNB-DU implementation when to stop the UE scheduling. +If two UL UP TNL Information IEs are included in UE CONTEXT MODIFICATION REQUEST message for a DRB, gNB-DU shall include two DL UP TNL Information IEs in UE CONTEXT MODIFICATION RESPONSE message. gNB-CU and gNB-DU use the UL UP TNL Information IEs and DL UP TNL Information IEs to support packet duplication for intra-gNB-DU CA as defined in TS 38.470 [2]. +If Duplication Activation IE is included in the UE CONTEXT MODIFICATION REQUEST message for a DRB, gNB-DU should take it into account when activing/deactiving CA based PDCP duplication for the DRB. +If DC Based Duplication Configured IE is included in the UE CONTEXT MODIFICATION REQUEST message for a DRB, gNB-DU shall regard that DC based PDCP duplication is configured for this DRB and it should take the responsibility of PDCP duplication activation/deactivation. If DC Based Duplication Activation IE is included in the UE CONTEXT MODIFICATION REQUEST message for a DRB, gNB-DU should take it into account when activing/deactiving DC based PDCP duplication for this DRB. +If the UL Configuration IE in DRB to Be Setup Item IE or DRB to Be Modified Item IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall take it into account for UL scheduling. The gNB-CU may include the RRC Reconfiguration Complete Indicator IE in the UE CONTEXT MODIFICATION REQUEST message to inform the gNB-DU that the ongoing reconfiguration procedure has been successfully performed by the UE. The gNB-DU does not need to wait for this confirmation for using the new UE configuration or taking other actions towards the UE. It is up to gNB-DU implementation when to use the new UE configuration configured. +If the RLC Failure Indication IE is included in UE CONTEXT MODIFICATION REQUEST message, the gNB-DU should consider that the RLC entity indicated by such IE needs to be re-established when the CA-based packet duplication is active. +If the UE CONTEXT MODIFICATION REQUEST message contains the RRC-Container IE, the gNB-DU shall send the corresponding RRC message to the UE via SRB1. If the UE CONTEXT MODIFICATION REQUEST message includes the Execute Duplication IE, the gNB-DU shall perform CA based duplication, if configured, for the SRB for the included RRC-Container IE. +If the UE CONTEXT MODIFICATION REQUEST message contains the Transmission Stop Indicator IE, the gNB-DU shall stop or restart (if already stopped) data transmission for the UE, according to the value of this IE. It is up to gNB-DU implementation when to stop or restart the UE scheduling. +For EN-DC operation, if the DRB to Be Setup List IE is present in the UE CONTEXT MODIFICATION REQUEST message the gNB-CU shall include the E-UTRAN QoS IE. The allocation of resources according to the values of the Allocation and Retention Priority IE included in the E-UTRAN QoS IE shall follow the principles described for the E-RAB Setup procedure in TS 36.413 [15]. For NG-RAN operation, the gNB-CU shall include the DRB Information IE in the UE CONTEXT MODIFICATION REQUEST message. If the gNB-CU received the MeNB Resource Coordination Information as defined in TS 36.423 [9], after completion of UE Context Setup procedures, the gNB-CU shall transparently transfer it to the gNB-DU via the Resource Coordination Transfer Container IE in the UE CONTEXT MODIFICATION REQUEST message. The gNB-DU shall use the information received in the Resource Coordination Transfer Container IE for reception of MeNB Resource Coordination Information at the gNB acting as secondary node as described in TS 36.423 [9]. +For EN-DC operation, and if the Subscriber Profile ID for RAT/Frequency priority IE is received from an MeNB, the UE CONTEXT MODIFICTION REQUEST message shall contain the Subscriber Profile ID for RAT/Frequency priority IE. The gNB-DU shall store the received Subscriber Profile ID for RAT/Frequency priority in the UE context and use it as defined in TS 36.300 [20]. +If the Index to RAT/Frequency Selection Priority IE is modified at the gNB-CU, the Index to RAT/Frequency Selection Priority IE shall be included in the UE CONTEXT MODIFICATION REQUEST. The gNB-DU may use it for RRM purposes. +If the UE CONTEXT MODIFICATION REQUEST message contains the Uplink TxDirectCurrentList Information IE, the gNB-DU may take that into account when selecting L1 configuration. Upon reception of the UE Context Modification Request message, the gNB-DU shall perform the modifications, and if successful reports the update in the UE CONTEXT MODIFICATION RESPONSE message. The gNB-DU shall report to the gNB-CU, in the UE CONTEXT MODIFICATION RESPONSE message, the result for all the requested or modified DRBs and SRBs in the following way: - A list of DRBs which are successfully established shall be included in the DRB Setup List IE; @@ -501,6 +715,16 @@ When the gNB-DU reports the unsuccessful establishment of a DRB or SRB, the caus If the Resource Coordination Transfer Container IE is included in the UE CONTEXT MODIFICATION RESPONSE, the gNB-CU shall transparently transfer this information for the purpose of resource coordination as described in TS 36.423 [9]. If the UE CONTEXT MODIFICATION RESPONSE message contains the DU To CU RRC Information IE, the gNB-CU shall take this into account. If the SCell Failed To Setup List IE is contained in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall regard the corresponding SCell(s) failed to be established with an appropriate cause value for each SCell failed to setup. +If the C-RNTI IE is included in the UE CONTEXT MODIFICATION RESPONSE, the gNB-CU shall consider that the C-RNTI has been allocated by the gNB-DU for this UE context. +If the Inactivity Monitoring Request IE is contained in the UE CONTEXT MODIFICATION REQUEST message, gNB-DU may consider that the gNB-CU has requested the gNB-DU to perform UE inactivity monitoring. If the Inactivity Monitoring Response IE is contained in the UE CONTEXT MODIFICATION RESPONSE message and set to “Not-supported”, the gNB-CU shall consider that the gNB-DU does not support UE inactivity monitoring for the UE. +The UE Context Setup Procedure is not used to configure SRB0. +If the Notification Control IE is included in the DRB to Be Setup List IE or the DRB to Be Modified List IE and it is set to active, the gNB-DU shall, if supported, monitor the QoS of the DRB and notify the gNB-CU if the QoS cannot be fulfilled any longer or if the QoS can be fulfilled again. The Notification Control IE can only be applied to GBR bearers. +If the UL PDU Session Aggregate Maximum Bit Rate IE is included in the QoS Flow Level QoS Parameters IE containded in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall replace the received UL PDU Session Aggregate Maximum Bit Rate and use it as specified in TS 23.501 [21]. +If the gNB-DU UE Aggregate Maximum Bit Rate Uplink IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall: +- replace the previously provided gNB-DU UE Aggregate Maximum Bit Rate Uplink with the new received gNB-DU UE Aggregate Maximum Bit Rate Uplink; +- use the received gNB-DU UE Aggregate Maximum Bit Rate Uplink for non-GBR Bearers for the concerned UE. +If the RLC Status IE is included in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall assume that RLC has been reestablished at the gNB-DU and may trigger PDCP data recovery. +If the GNB-DU Configuration Query IE is contained in the UE CONTEXT MODIFICATION REQUEST message, gNB-DU shall include the CellGroupConfig IE in the DU To CU RRC Information IE in the UE CONTEXT MODIFICATION RESPONSE message. 8.3.4.3 Unsuccessful Operation Figure 8.3.4.3-1: UE Context Modification procedure. Unsuccessful operation @@ -516,34 +740,137 @@ The purpose of the UE Context Modification Required procedure is to modify the e Figure 8.3.5.2-1: UE Context Modification Required procedure. Successful operation The F1AP UE CONTEXT MODIFICATION REQUIRED message is initiated by the gNB-DU. The gNB-CU reports the successful update of the UE context in the UE CONTEXT MODIFICATION CONFIRM message. -If two DL GTP Tunnel Endpoint IEs are included in UE CONTEXT MODIFICATION REQUIRED message for a DRB, gNB-CU shall include two UL GTP  Tunnel Endpoint IEs in UE CONTEXT MODIFICATION CONFIRM message. gNB-CU and gNB-DU use the UL GTP Tunnel Endpoint IEs and DL GTP Tunnel Endpoint IEs to support packet duplication for intra-gNB-DU CA as defined in TS 38.470 [2]. +If two DL UP TNL Information IEs are included in UE CONTEXT MODIFICATION REQUIRED message for a DRB, gNB-CU shall include two UL UP TNL Information IEs in UE CONTEXT MODIFICATION CONFIRM message. gNB-CU and gNB-DU use the UL UP TNL Information IEs and DL UP TNL Information IEs to support packet duplication for intra-gNB-DU CA as defined in TS 38.470 [2]. If the Resource Coordination Transfer Container IE is included in the UE CONTEXT MODIFICATION REQUIRED, the gNB-CU shall transparently transfer this information for the purpose of resource coordination as described in TS 36.423 [9]. If the gNB-CU received the MeNB Resource Coordination Information as defined in TS 36.423 [9], after completion of UE Context Modification Required procedures, the gNB-CU shall transparently transfer it to the gNB-DU via the Resource Coordination Transfer Container IE in the UE CONTEXT MODIFICATION CONFIRM message. The gNB-DU shall use the information received in the Resource Coordination Transfer Container IE for reception of MeNB Resource Coordination Information at the gNB acting as secondary node as described in TS 36.423 [9]. If the UE CONTEXT MODIFICATION REQUIRED message contains the DU To CU RRC Information IE, the gNB-CU shall take this into account. +If the UE CONTEXT MODIFICATION CONFIRM message includes the Execute Duplication IE, the gNB-DU shall perform CA based duplication, if configured, for the SRB for the included RRC-Container IE. +If the UE CONTEXT MODIFICATION REQUIRED message contains the RLC Status IE, the gNB-CU shall assume that RLC has been reestablished at the gNB-DU and may trigger PDCP data recovery. 8.3.5.3 Abnormal Conditions Not applicable. +8.3.6 UE Inactivity Notification +8.3.6.1 General +This procedure is initiated by the gNB-DU to indicate the UE activity event. +The procedure uses UE-associated signalling. +8.3.6.2 Successful Operation + +Figure 8.3.6.2-1: UE Inactivity Notification procedure. +The gNB-DU initiates the procedure by sending the UE INACTIVITY NOTIFICATION message to the gNB-CU. +8.3.6.3 Abnormal Conditions +Not applicable. +8.3.7 Notify +8.3.7.1 General +The purpose of the Notify procedure is to enable the gNB-DU to inform the gNB-CU that the QoS of an already established GBR DRB cannot by fulfilled any longer or that it can be fulfilled again. The procedure uses UE-associated signalling. +8.3.7.2 Successful Operation + +Figure 8.3.7.2-1: Notify procedure. Successful operation. +The gNB-DU initiates the procedure by sending a NOTIFY message. +The NOTIFY message shall contain the list of the GBR DRBs associated with notification control for which the QoS is not fulfilled anymore or for which the QoS is fulfilled again by the gNB-DU. +Upon reception of the NOTIFY message, the gNB-CU may identify which are the affected PDU sessions and QoS flows. The gNB-CU may inform the 5GC that the QoS for these PDU sessions or QoS flows is not fulfilled any longer or it is fulfilled again. +8.3.7.3 Abnormal Conditions +Not applicable. 8.4 RRC Message Transfer procedures -8.4.1 Void -Reserved for future use. +8.4.1 Initial UL RRC Message Transfer +8.4.1.1 General +The purpose of the Initial UL RRC Message Transfer procedure is to transfer the initial RRC message to the gNB-CU. +8.4.1.2 Successful operation + +Figure 8.4.1.2-1: Initial UL RRC Message Transfer procedure. +The establishment of the UE-associated logical F1-connection shall be initiated as part of the procedure. +If the DU to CU RRC Information IE is not included in the INITIAL UL RRC MESSAGE TRANSFER the gNB-CU should reject the UE under the assumption that the gNB-DU is not able to serve such UE. If the gNB-DU is able to serve the UE, the gNB-DU shall include the DU to CU RRC Information IE. +If the SUL Access Indication IE is included in the INITIAL UL RRC MESSAGE TRANSFER, the gNB-CU shall consider that the UE has performed access on SUL carrier. +8.4.1.3 Abnormal Conditions +Not applicable. 8.4.2 DL RRC Message Transfer 8.4.2.1 General -The purpose of the DL RRC Message Transfer procedure is to transfer an RRC message as a DL PDCP-PDU to the gNB-DU. +The purpose of the DL RRC Message Transfer procedure is to transfer an RRC message The procedure uses UE-associated signalling. 8.4.2.2 Successful operation Figure 8.4.2.2-1: DL RRC Message Transfer procedure -If a UE-associated logical F1-connection exists, the DL RRC MESSAGE TRANSFER message shall contain the gNB-DU UE F1AP ID IE, which should be used by gNB-DU to lookup the stored UE context. -The DL RRC MESSAGE TRANSFER message shall include, if available, the old gNB-DU UE F1AP ID IE so that the gNB-DU can retrieve the existing UE context in RRC connection reestablishment procedure. +If a UE-associated logical F1-connection exists, the DL RRC MESSAGE TRANSFER message shall contain the gNB-DU UE F1AP ID IE, which should be used by gNB-DU to lookup the stored UE context.If no UE-associated logical F1-connection exists, the UE-associated logical F1-connection shall be established at reception of the DL RRC MESSAGE TRANSFER message. +If the Index to RAT/Frequency Selection Priority IE is included in the DL RRC MESSAGE TRANSFER, the gNB-DU may use it for RRM purposes. +The DL RRC MESSAGE TRANSFER message shall include, if available, the old gNB-DU UE F1AP ID IE so that the gNB-DU can retrieve the existing UE context in RRC connection reestablishment procedure, as defined in TS 38.401 [4]. +The DL RRC MESSAGE TRANSFER message shall include, if SRB duplication is activated, the Execute Duplication IE, so that the gNB-DU can perform CA based duplication for the SRB. +If the gNB-DU identifies the UE-associated logical F1-connection by the gNB-DU UE F1AP ID IE in the DL RRC MESSAGE TRANSFER message and the old gNB-DU UE F1AP ID IE is included, it shall release the old gNB-DU UE F1AP ID and the related configurations associated with the old gNB-DU UE F1AP ID. 8.4.2.3 Abnormal Conditions Not applicable. 8.4.3 UL RRC Message Transfer 8.4.3.1 General -The purpose of the UL RRC Message Transfer procedure is to transfer an RRC message as an UL PDCP-PDU to the gNB-CU. +The purpose of the UL RRC Message Transfer procedure is to transfer an RRC message as an UL PDCP-PDU to the gNB-CU. The procedure uses UE-associated signalling. 8.4.3.2 Successful operation Figure 8.4.3.2-1: UL RRC Message Transfer procedure When the gNB-DU has received from the radio interface an RRC message to which a UE-associated logical F1-connection for the UE exists, the gNB-DU shall send the UPLINK RRC TRANSFER message to the gNB-CU including the RRC message as a RRC-Container IE. 8.4.3.3 Abnormal Conditions Not applicable. +8.5 Warning Message Transmission Procedures +8.5.1 Write-Replace Warning +8.5.1.1 General +The purpose of Write-Replace Warning procedure is to start or overwrite the broadcasting of warning messages. The procedure uses non UE-associated signalling. +8.5.1.2 Successful Operation + +Figure 8.5.1.2-1: Write-Replace Warning procedure: successful operation +The gNB-CU initiates the procedure by sending a WRITE-REPLACE WARNING REQUEST message to the gNB-DU. +Upon receipt of the WRITE-REPLACE WARNING REQUEST message, the gNB-DU shall prioritise its resources to process the warning message. +The gNB-DU acknowledges the WRITE-REPLACE WARNING REQUEST message by sending a WRITE-REPLACE WARNING RESPONSE message to the gNB-CU. +8.5.1.3 Unsuccessful Operation +Not applicable. +8.5.1.4 Abnormal Conditions +Not applicable. +8.5.2 PWS Cancel +8.5.2.1 General +The purpose of the PWS Cancel procedure is to cancel an already ongoing broadcast of a warning message. The procedure uses non UE-associated signalling. +8.5.2.2 Successful Operation + +Figure 8.5.2.2-1: PWS Cancel procedure: successful operation +The gNB-CU initiates the procedure by sending a PWS CANCEL REQUEST message to the gNB-DU. +The gNB-DU shall acknowledge the PWS CANCEL REQUEST message by sending the PWS CANCEL RESPONSE message. +8.5.1.3 Unsuccessful Operation +Not applicable. +8.5.1.4 Abnormal Conditions +Not applicable. +8.5.3 PWS Restart Indication +8.5.3.1 General +The purpose of PWS Restart Indication procedure is to inform the gNB-CU that PWS information for some or all cells of the gNB-DU are available for reloading from the CBC if needed. The procedure uses non UE-associated signalling. +8.5.3.2 Successful Operation + +Figure 8.5.3.2-1: PWS restart indication +The gNB-DU initiates the procedure by sending a PWS RESTART INDICATION message to the gNB-CU. +8.5.3.3 Abnormal Conditions +Not applicable. +8.5.4 PWS Failure Indication +8.5.4.1 General +The purpose of the PWS Failure Indication procedure is to inform the gNB-CU that ongoing PWS operation for one or more cells of the gNB-DU has failed. The procedure uses non UE-associated signalling. +8.5.4.2 Successful Operation + +Figure 8.5.4.2-1: PWS failure indication +The gNB-DU initiates the procedure by sending a PWS FAILURE INDICATION message to the gNB-CU. +8.5.4.3 Abnormal Conditions +Not applicable. +8.6 System Information Procedures +8.6.1 System Information Delivery +8.6.1.1 General +The purpose of the System Information Delivery procedure is to command the gNB-DU to broadcast the requested Other SI. The procedure uses non-UE associated signalling. +8.6.1.2 Successful Operation + +Figure 8.6.1.2-1: System Information Delivery procedure. Successful operation. +The gNB-CU initiates the procedure by sending a SYSTEM INFORMATION DELIVERY COMMAND message to the gNB-DU. +Upon reception of the SYSTEM INFORMATION DELIVERY COMMAND message, the gNB-DU shall broadcast the requested Other SI, and delete the UE context corresponding to the Confirmed UE ID IE, if any. +8.6.1.3 Abnormal Conditions +Not applicable. +8.7 Paging procedures +8.7.1 Paging +8.7.1.1 General +The purpose of the Paging procedure is used to provide the paging information to enable gNB-DU to page a UE. The procedure uses non-UE associated signalling. +8.7.1.2 Successful Operation + +Figure 8.7.1.2-1: Paging procedure. Successful operation. +The gNB-CU initiates the procedure by sending a PAGING message. +The Paging DRX IE may be included in the PAGING message, and if present the gNB-DU may use it to determine the final paging cycle for the UE. +The Paging Priority IE may be included in the PAGING message, and if present the gNB-DU may use it according to TS 23.501 [21]. +At the reception of the PAGING message, the gNB-DU shall perform paging of the UE in cells which belong to cells as indicated in the Paging Cell List IE. +8.7.1.3 Abnormal Conditions +Not applicable. 9 Elements for F1AP Communication 9.1 General Subclauses 9.2 and 9.3 present the F1AP message and IE definitions in tabular format. The corresponding ASN.1 definition is presented in subclause 9.4. In case there is contradiction between the tabular format and the ASN.1 definition, the ASN.1 shall take precedence, except for the definition of conditions for the presence of conditional IEs, where the tabular format shall take precedence. @@ -603,7 +930,7 @@ reject >>Reset All M -ENUMERATED (Reset all,…) +ENUMERATED (Reset all,...) - @@ -800,13 +1127,13 @@ reject gNB-DU Name O -PrintableString(SIZE(1..150,…)) +PrintableString(SIZE(1..150,...)) YES ignore gNB-DU Served Cells List -1 +0.. 1 List of cells configured in the gNB-DU YES @@ -832,6 +1159,13 @@ O RRC container with system information owned by gNB-DU - - +gNB-DU RRC version +M + +RRC version 9.3.1.70 + +YES +reject Range bound Explanation @@ -865,7 +1199,7 @@ reject gNB-CU Name O -PrintableString(SIZE(1..150,…)) +PrintableString(SIZE(1..150,...)) Human readable name of the gNB-CU. YES ignore @@ -874,14 +1208,14 @@ Cells to be Activated List 0.. 1 - - +YES +reject >Cells to be Activated List Item 1.. List of cells to be activated -YES +EACH reject >> NR CGI M @@ -897,6 +1231,27 @@ INTEGER (0..1007) Physical Cell ID - - +>>gNB-CU System Information +O + +9.3.1.42 +RRC container with system information owned by gNB-CU +- +- +>>Available PLMN List +O + +9.3.1.65 + +YES +ignore +gNB-CU RRC version +M + +RRC version 9.3.1.70 + +YES +reject Range bound Explanation @@ -1057,14 +1412,14 @@ M - - -Active Cells List +Cells Status List 0..1 Complete list of active cells YES reject ->Active Cells Item +> Cells Status Item 0 .. @@ -1076,6 +1431,13 @@ M 9.3.1.12 +- +- +>>Cell Status +M + +9.3.1.68 + - - @@ -1136,6 +1498,20 @@ INTEGER (0..1007) Physical Cell ID - - +>> gNB-CU System Information +O + +9.3.1.42 +RRC container with system information owned by gNB-CU +- +- +>>Available PLMN List +O + +9.3.1.65 + +YES +ignore Criticality Diagnostics O @@ -1247,6 +1623,20 @@ INTEGER (0..1007) Physical Cell ID - - +>> gNB-CU System Information +O + +9.3.1.42 +RRC container with system information owned by gNB-CU + + +>>Available PLMN List +O + +9.3.1.65 + +YES +ignore Cells to be Deactivated List 0..1 @@ -1268,11 +1658,179 @@ M - - +gNB-CU TNL Association To Add List + +0..1 + + +YES +ignore +>gNB-CU TNL Association To Add Item IEs + +1.. + + +EACH +ignore +>>TNL Association Transport Layer Information +M + +CP Transport Layer Address +9.3.2.4 +Transport Layer Address of the gNB-CU. +YES +ignore +>>TNL Association Usage +M + +ENUMERATED (ue, non-ue, both, ...) +Indicates whether the TNL association is only used for UE-associated signalling, or non-UE-associated signalling, or both. For usage of this IE, refer to TS 38.472 [22]. +YES +ignore +gNB-CU TNL Association To Remove List + +0..1 + + +YES +ignore +>gNB-CU TNL Association To Remove Item IEs + +1.. + + +EACH +ignore +>>TNL Association Transport Layer Address +M + +CP Transport Layer Address +9.3.2.4 +Transport Layer Address of the gNB-CU. +YES +ignore +gNB-CU TNL Association To Update List + +0..1 + + +YES +ignore +>gNB-CU TNL Association To Update Item IEs + +1.. + + +EACH +ignore +>>TNL Association Transport Layer Address +M + +CP Transport Layer Address +9.3.2.4 +Transport Layer Address of the gNB-CU. +YES +ignore +>>TNL Association Usage +O + +ENUMERATED (ue, non-ue, both, ...) +Indicates whether the TNL association is only used for UE-associated signalling, or non-UE-associated signalling, or both. For usage of this IE, refer to TS 38.472 [22]. +YES +ignore +Cells to be barred List + +0..1 + +List of cells to be barred. + +YES +ignore +>Cells to be barred List Item + +1.. + + +EACH +ignore +>>NR CGI +M + +9.3.1.12 + +- +- +>> Cell Barred +M + +ENUMERATED (barred, not-barred, ...) + +- +- +Protected E-UTRA Resources List + +0..1 + +List of Protected E-UTRA Resources. +YES +reject +>Protected E-UTRA Resources List Item + +1.. + + +EACH +reject +>>Spectrum Sharing Group ID +M + +INTEGER (1.. maxCellineNB) +Indicates the E-UTRA cells involved in resource coordination with the NR cells affiliated with the same Spectrum Sharing Group ID. + + + +- + + + +- +>> E-UTRA Cells List + +1 + +List of applicable E-UTRA cells. +- +- +>>> E-UTRA Cells List Item + +1 .. + + +- +- +>>>>EUTRA Cell ID +M + +BIT STRING (SIZE(28)) +Indicates the E-UTRAN Cell Global Identifier as defined in subclause 9.2.14 in TS 36.423 [9]. +– +– +>>>>Served E-UTRA Cell Information +M + +9.3.1.64 + +– +– Range bound Explanation maxCellingNBDU -Maximum no. cells that can be served by a gNB-DU. Value is 512. +Maximum nunmerbs of cells that can be served by a gNB-DU. Value is 512. +maxnoofTNLAssociations +Maximum numbers of TNL Associations between the gNB-CU and the gNB-CU. Value is 32. +maxCellineNB +Maximum no. cells that can be served by an eNB. Value is 256. 9.2.1.11 GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE This message is sent by a gNB-DU to a gNB-CU to acknowledge update of information for a TNL association. @@ -1333,11 +1891,64 @@ O YES ignore +gNB-CU TNL Association Setup List + +0..1 + + +YES +ignore +>gNB-CU TNL Association Setup Item IEs + +1.. + + +EACH +ignore +>>TNL Association Transport Layer Address +M + +CP Transport Layer Address +9.3.2.4 +Transport Layer Address of the gNB-CU +YES +ignore +gNB-CU TNL Association Failed to Setup Lis + +0..1 + + +YES +ignore +>gNB-CU TNL Association Failed To Setup Item IEs + +1.. + + +EACH +ignore +>>TNL Association Transport Layer Address +M + +CP Transport Layer Address +9.3.2.4 +Transport Layer Address of the gNB-CU +YES +ignore +>>Cause +M + +9.3.1.2 + + + Range bound Explanation maxCellingNBDU Maximum no. cells that can be served by a gNB-DU. Value is 512. +maxnoofTNLAssociations +Maximum no. of TNL Associations between the gNB-CU and the gNB-CU. Value is 32. 9.2.1.12 GNB-CU CONFIGURATION UPDATE FAILURE This message is sent by the gNB-DU to indicate gNB-CU Configuration Update failure. @@ -1385,6 +1996,110 @@ O YES ignore +9.2.1.13 GNB-DU RESOURCE COORDINATION REQUEST +This message is sent by a gNB-CU to a gNB-DU, to express the desired resource allocation for data traffic, for the sake of resource coordination. The message triggers gNB-DU resource coordination (for NR-initiated resource coordination), to indicate an initial resource offer by the E-UTRA node (for E-UTRA-initiated gNB-DU Resource Coordination), or to indicate the agreed resource allocation that is to be executed. +Direction: gNB-CU  gNB-DU +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Criticality +Assigned Criticality +Message Type +M + +9.3.1.1 + +YES +reject +Transaction ID +M + +9.3.1.23 + +YES +reject +Request type +M + +ENUMERATED (offer, execution, ...) + +YES +reject +E-UTRA – NR Cell Resource Coordination Request Container +O + +OCTET STRING +Includes the X2AP E-UTRA – NR CELL RESOURCE COORDINATION REQUEST message as defined in subclause 9.1.4.24 in TS 36.423 [9]. +YES +reject + +9.2.1.14 GNB-DU RESOURCE COORDINATION RESPONSE +This message is sent by a gNB-DU to a gNB-CU, to express the desired resource allocation for data traffic, as a response to the GNB-DU RESOURCE COORDINATION REQUEST. +Direction: gNB-DU  gNB-CU + +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Criticality +Assigned Criticality +Message Type +M + +9.3.1.1 + +YES +reject +Transaction ID +M + +9.3.1.23 + +YES +reject +E-UTRA – NR Cell Resource Coordination Response Container +M + +OCTET STRING +Includes the X2AP E-UTRA – NR CELL RESOURCE COORDINATION RESPONSE message as defined in subclause 9.1.4.25 in TS 36.423 [9]. +YES +reject + +9.2.1.15 GNB-DU STATUS INDICATION +This message is sent by the gNB-DU to indicate to the gNB-CU its status of overload. +Direction: gNB-DU  gNB-CU +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Criticality +Assigned Criticality +Message Type +M + +9.3.1.1 + +YES +reject +Transaction ID +M + +9.3.1.23 + +YES +reject +gNB-DU Overload Information +M + +ENUMERATED (overloaded, not-overloaded) + +YES +reject + 9.2.2 UE Context Management messages 9.2.2.1 UE CONTEXT SETUP REQUEST This message is sent by the gNB-CU to request the setup of a UE context. @@ -1422,9 +2137,24 @@ M NR CGI 9.3.1.12 -Special Cell as defined in TS 38.321 [16] +Special Cell as defined in TS 38.321 [16]. For handover case, this IE shall be considered as target cell. YES reject +ServCellIndex +M + +INTEGER (0..31) + + + +SpCell UL Configured +O + +Cell UL Configured +9.3.1.33 + +YES +ignore Candidate SpCell List 0..1 @@ -1437,16 +2167,16 @@ ignore 1 .. - - +EACH +ignore >>Candidate SpCell ID M NR CGI 9.3.1.12 Special Cell as defined in TS 38.321 [16] - - +- +- CU to DU RRC Information M @@ -1494,7 +2224,15 @@ SCell Identifier in gNB >>SCellIndex M -INTEGER (0..63) +INTEGER (1..31) + + + +>>SCell UL Configured +O + +Cell UL Configured +9.3.1.33 @@ -1503,25 +2241,32 @@ SRB to Be Setup List 0..1 - - +YES +reject >SRB to Be Setup Item IEs 1 .. - - ->SRB ID +EACH +reject +>>SRB ID M 9.3.1.7 +>>Duplication Indication +O + +ENUMERATED (true, ..., false) +If included, it should be set to true. +YES +ignore DRB to Be Setup List -1 +0..1 YES @@ -1540,31 +2285,87 @@ M - ->>E-UTRAN QoS -O +>>CHOICE QoS Information +M + + + +YES +reject +>>>E-UTRAN QoS +M 9.3.1.19 Shall be used for EN-DC case to convey E-RAB Level QoS Parameters ->>UL Tunnels to be setup List +>>>DRB Information + +1 + +Shall be used for NG-RAN cases + + +>>>>DRB QoS +M + +9.3.1.45 + + + +>>>>S-NSSAI +M + +9.3.1.38 + + + +>>>>Notification Control +O + +9.3.1.56 + +- +- +>>>>Flows Mapped to DRB Item + +1 .. + + + + +>>>>>QoS Flow Indicator +M + +9.3.1.63 + + + +>>>>>QoS Flow Level QoS Parameters +M + +9.3.1.45 + + + +>>UL UP TNL Information to be setup List 1 ->>> UL Tunnels to Be Setup Item IEs +>>> UL UP TNL Information to Be Setup Item IEs -1 .. +1 .. ->>>>UL GTP Tunnel Endpoint +>>>>UL UP TNL Information M -GTP Tunnel Endpoint +UP Transport Layer Information 9.3.2.1 gNB-CU endpoint of the F1 transport bearer. For delivery of UL PDUs. - @@ -1584,19 +2385,92 @@ UL Configuraiton Information about UL usage in gNB-DU. +>>Duplication Activation +O + +9.3.1.36 +Information on the initial state of CA based UL PDCP duplication + + +>> DC Based Duplication Configured +O + +ENUMERATED (true, ...) +Indication on whether DC based PDCP duplication is configured or not. +YES +reject +>>DC Based Duplication Activation +O + +9.3.1.36 +Information on the initial state of DC basedUL PDCP duplication +YES +reject +>>PDCP SN length +M + +ENUMERATED (12bits, 18bits, ...) + +YES +ignore +Inactivity Monitoring Request +O + +ENUMERATED (true, ...) + +YES +reject +RAT-Frequency Priority Information +O + +9.3.1.34 + +YES +reject +RRC-Container +O + +9.3.1.6 +Includes the DL-DCCH-Message IE as defined in subclause 6.2 of TS 38.331 [8], encapsulated in a PDCP PDU. +YES +ignore +Masked IMEISV +O + +9.3.1.55 + +YES +ignore +Serving PLMN +O + +PLMN ID +9.3.1.14 +Indicates the PLMN serving the UE. +YES +ignore +gNB-DU UE Aggregate Maximum Bit Rate Uplink +M + +Bit Rate 9.3.1.22 +The gNB-DU UE Aggregate Maximum Bit Rate Uplink is to be enforced by the gNB-DU. +YES +ignore Range bound Explanation maxnoofSCells -Maximum no. of SCells allowed towards one UE, the maximum value is 64. +Maximum no. of SCells allowed towards one UE, the maximum value is 32. maxnoofSRBs Maximum no. of SRB allowed towards one UE, the maximum value is 8. maxnoofDRBs Maximum no. of DRB allowed towards one UE, the maximum value is 64. -maxnoofULTunnels -Maximum no. of tunnels allowed towards one DRB, the maximum value is 2. +maxnoofULUPTNLInformation +Maximum no. of ULUP TNL Information allowed towards one DRB, the maximum value is 2. maxnoofCandidateSpCells Maximum no. of SpCells allowed towards one UE, the maximum value is 64. +maxnoofQoSFlows +Maximum no. of flows allowed to be mapped to one DRB, the maximum value is 64. 9.2.2.2 UE CONTEXT SETUP RESPONSE This message is sent by the gNB-DU to confirm the setup of a UE context. @@ -1630,13 +2504,19 @@ M YES reject DU To CU RRC Information - M 9.3.1.26 YES reject +C-RNTI +O + +9.3.1.32 +C-RNTI allocated at the gNB-DU +YES +ignore Resource Coordination Transfer Container O @@ -1644,9 +2524,16 @@ OCTET STRING Includes the SgNB Resource Coordination Information IE as defined in subclause 9.2.117 of TS 36.423 [9]. YES ignore +Full Configuration +O + +ENUMERATED (full, ...) + +YES +reject DRB Setup List -1 +0..1 The List of DRBs which are successfully established. YES @@ -1665,24 +2552,31 @@ M - ->>DL Tunnels to be setup List +>>LCID +O + +9.3.1.35 +LCID for the primary path if PDCP duplication is applied + + +>>DL UP TNL Information to be setup List 1 ->>> DL Tunnels to Be Setup Item IEs +>>> DL UP TNL Information to Be Setup Item IEs -1 .. +1 .. ->>>>DL GTP Tunnel Endpoint +>>>>DL UP TNL Information M -GTP Tunnel Endpoint +UP Transport Layer Information 9.3.2.1 gNB-DU endpoint of the F1 transport bearer. For delivery of DL PDUs. @@ -1772,6 +2666,13 @@ O +Inactivity Monitoring Response +O + +ENUMERATED (not-supported, ...) + +YES +reject Criticality Diagnostics O @@ -1788,8 +2689,8 @@ maxnoofSRBs Maximum no. of SRB allowed towards one UE, the maximum value is 8. maxnoofDRBs Maximum no. of DRB allowed towards one UE, the maximum value is 64. -maxnoofDLTunnels -Maximum no. of tunnels allowed towards one DRB, the maximum value is 2. +maxnoofDLUPTNLInformation +Maximum no. of DL UP TNL Information allowed towards one DRB, the maximum value is 2. 9.2.2.3 UE CONTEXT SETUP FAILURE This message is sent by the gNB-DU to indicate that the setup of the UE context was unsuccessful. @@ -1848,8 +2749,8 @@ ignore 0 .. - - +EACH +ignore >>Potential SpCell ID M @@ -1941,6 +2842,34 @@ M YES ignore +RRC-Container +O + +9.3.1.6 +Includes the DL-DCCH-Message IE as defined in subclause 6.2 of TS 38.331 encapsulated in a PDCP PDU, or the DL-CCCH-Message IE as defined in subclause 6.2 of TS 38.331 [8]. +YES +ignore +SRB ID +O + +9.3.1.7 +It shall be included if the RRC-Container IE is present. The gNB-DU shall send the RRC message on the indicated SRB. +YES +ignore +old gNB-DU UE F1AP ID +O + +9.3.1.5 +Include it if RRCReestablishmentRequest is not accepted +YES +ignore +Execute Duplication +O + +ENUMERATED (true, ...) +This IE may be sent only if duplication has been configured for the UE. +YES +Ignore 9.2.2.6 UE CONTEXT RELEASE COMPLETE This message is sent by the gNB-DU to confirm the release of the UE-associated logical F1 connection. @@ -2017,9 +2946,24 @@ O NR CGI 9.3.1.12 -Special Cell as defined in TS 38.321 [16] +Special Cell as defined in TS 38.321 [16]. For handover case, this IE shall be considered as target cell. YES Ignore +ServCellIndex +O + +INTEGER (0..31) + + + +SpCell UL Configured +O + +Cell UL Configured +9.3.1.33 + +YES +ignore DRX Cycle O @@ -2062,7 +3006,7 @@ RRC-Container O 9.3.1.6 -Includes the RRCConnectionReconfiguration message as defined in TS 38.331 [8]. +Includes the RRCConnectionReconfiguration message as defined in TS 38.331 [8], encapsulated in a PDCP PDU. YES ignore SCell To Be Setup List @@ -2090,7 +3034,15 @@ SCell Identifier in gNB >>SCellIndex M -INTEGER (0..15) +INTEGER (1..31) + + + +>>SCell UL Configured +O + +Cell UL Configured +9.3.1.33 @@ -2121,15 +3073,15 @@ SRB to Be Setup List 0..1 - - +YES +reject >SRB to Be Setup Item IEs 1.. - - +EACH +reject >>SRB ID M @@ -2137,6 +3089,13 @@ M +>>Duplication Indication +O + +ENUMERATED (true, ..., false) + +YES +ignore DRB to Be Setup List 0..1 @@ -2158,31 +3117,87 @@ M - ->>E-UTRAN QoS -O +>>CHOICE QoS Information +M + + + +YES +reject +>>>E-UTRAN QoS +M 9.3.1.19 Shall be used for EN-DC case to convey E-RAB Level QoS Parameters ->> UL Tunnels to be setup List +>>>DRB Information + +1 + +Shall be used for NG-RAN cases + + +>>>>DRB QoS +M + +9.3.1.45 + + + +>>>>S-NSSAI +M + +9.3.1.38 + + + +>>>>Notification Control +O + +9.3.1.56 + +- +- +>>>>Flows Mapped to DRB Item + +1 .. + + + + +>>>>>QoS Flow Indicator +M + +9.3.1.63 + + + +>>>>>QoS Flow Level QoS Parameters +M + +9.3.1.45 + + + +>>UL UP TNL Information to be setup List 1 ->>>UL Tunnels to Be Setup Item IEs +>>>UL UP TNL Information to Be Setup Item IEs -1 .. +1 .. ->>>>UL GTP Tunnel Endpoint +>>>>UL UP TNL Information M -GTP Tunnel Endpoint +UP Transport Layer Information 9.3.2.1 gNB-CU endpoint of the F1 transport bearer. For delivery of UL PDUs. - @@ -2202,6 +3217,34 @@ UL Configuration Information about UL usage in gNB-DU. +>>Duplication Activation +O + +9.3.1.36 +Information on the initial state of CA based UL PDCP duplication + + +>> DC Based Duplication Configured +O + +ENUMERATED (true, ...) +Indication on whether DC based PDCP duplication is configured or not. +YES +reject +>>DC Based Duplication Activation +O + +9.3.1.36 +Information on the initial state of DC based UL PDCP duplication +YES +reject +>>PDCP SN length +M + +ENUMERATED (12bits, 18bits, ...) + +YES +ignore DRB to Be Modified List 0..1 @@ -2223,31 +3266,87 @@ M - ->>E-UTRAN QoS +>>CHOICE QoS Information O + + +YES +reject +>>>E-UTRAN QoS +M + 9.3.1.19 Shall be used for EN-DC case to convey E-RAB Level QoS Parameters ->> UL Tunnels to be setup List +>>>DRB Information + +1 + +Shall be used for NG-RAN cases + + +>>>>DRB QoS +M + +9.3.1.45 + + + +>>>>S-NSSAI +M + +9.3.1.38 + + + +>>>>Notification Control +O + +9.3.1.56 + +- +- +>>>>Flows Mapped to DRB Item + +1 .. + + + + +>>>>>QoS Flow Indicator +M + +9.3.1.63 + + + +>>>>>QoS Flow Level QoS Parameters +M + +9.3.1.45 + + + +>> UL UP TNL Information to be setup List 0..1 ->>> UL Tunnels to Be Setup Item IEs +>>> UL UP TNL Information to Be Setup Item IEs -1 .. +1 .. ->>>>UL GTP Tunnel Endpoint +>>>>UL UP TNL Information M -GTP Tunnel Endpoint +UP Transport Layer Information 9.3.2.1 gNB-CU endpoint of the F1 transport bearer. For delivery of UL PDUs. - @@ -2260,20 +3359,27 @@ UL Configuration Information about UL usage in gNB-DU. -SRB TO Be Released List +>>PDCP SN length +O + +ENUMERATED(12bits,18bits , ...) + +YES +ignore +SRB To Be Released List 0..1 - - +YES +reject >SRB To Be Released Item IEs 1.. - - +EACH +reject >>SRB ID M @@ -2302,17 +3408,73 @@ M - +Inactivity Monitoring Request +O + +ENUMERATED (true, ...) + +YES +reject +RAT-Frequency Priority Information +O + +9.3.1.34 + +YES +reject +DRX configuration indicator +O + +ENUMERATED(release,...) + +YES +ignore +RLC Failure Indication +O + +9.3.1.66 + +YES +ignore +Uplink TxDirectCurrentList Information +O + +9.3.1.67 + +YES +ignore +GNB-DU Configuration Query +O + +ENUMERATED (true, ...) +Used to request the gNB-DU to provide its configuration. +YES +reject +gNB-DU UE Aggregate Maximum Bit Rate Uplink +O + +Bit Rate 9.3.1.22 +The gNB-DU UE Aggregate Maximum Bit Rate Uplink is to be enforced by the gNB-DU. +YES +ignore +Execute Duplication +O + +ENUMERATED (true, ...) +This IE may be sent only if duplication has been configured for the UE. +YES +Ignore Range bound Explanation maxnoofSCells -Maximum no. of SCells allowed towards one UE, the maximum value is 64. +Maximum no. of SCells allowed towards one UE, the maximum value is 32. maxnoofSRBs Maximum no. of SRB allowed towards one UE, the maximum value is 8. maxnoofDRBs Maximum no. of DRB allowed towards one UE, the maximum value is 64. -maxnoofULTunnels -Maximum no. of tunnels allowed towards one DRB, the maximum value is 2. +maxnoofULUPTNLInformation +Maximum no. of UL UP TNL Information allowed towards one DRB, the maximum value is 2. 9.2.2.8 UE CONTEXT MODIFICATION RESPONSE This message is sent by the gNB-DU to confirm the modification of a UE context. @@ -2381,24 +3543,31 @@ M - ->>DL Tunnels to be setup List +>>LCID +O + +9.3.1.35 +LCID for primary path if PDCP duplication is applied + + +>>DL UP TNL Information to be setup List 1 ->>>DL Tunnels to Be Setup Item IEs +>>>DL UP TNL Information to Be Setup Item IEs -1 .. +1 .. ->>>>DL GTP Tunnel Endpoint +>>>>DL UP TNL Information M -GTP Tunnel Endpoint +UP Transport Layer Information 9.3.2.1 gNB-DU endpoint of the F1 transport bearer. For delivery of DL PDUs. @@ -2424,28 +3593,42 @@ M - ->>DL Tunnels to be setup List +>>LCID +O + +9.3.1.35 +LCID for primary path if PDCP duplication is applied + + +>>DL UP TNL Information to be setup List 1 ->>>DL Tunnels to Be Setup Item IEs +>>>DL UP TNL Information to Be Setup Item IEs -1 .. +1 .. ->>>>DL GTP Tunnel Endpoint +>>>>DL UP TNL Information M -GTP Tunnel Endpoint +UP Transport Layer Information 9.3.2.1 gNB-DU endpoint of the F1 transport bearer. For delivery of DL PDUs. +>>RLC Status +O + +9.3.1.69 +Indicates the RLC has been re-established at the gNB-DU. + + SRB Failed to be Setup List 0..1 @@ -2535,15 +3718,15 @@ SCell Failed To Setup List 0..1 - - +YES +ignore >SCell Failed to Setup Item 1 .. - - +EACH +ignore >>SCell ID M @@ -2559,11 +3742,25 @@ O +Inactivity Monitoring Response +O + +ENUMERATED (Not-supported, ...) + +YES +reject Criticality Diagnostics O 9.3.1.3 +YES +ignore +C-RNTI +O + +9.3.1.32 +C-RNTI allocated at the gNB-DU YES ignore @@ -2573,8 +3770,8 @@ maxnoofSRBs Maximum no. of SRB allowed towards one UE, the maximum value is 8. maxnoofDRBs Maximum no. of DRB allowed towards one UE, the maximum value is 64. -maxnoofDLTunnels -Maximum no. of tunnels allowed towards one DRB, the maximum value is 2. +maxnoofDLUPTNLInformation +Maximum no. of DL UP TNL Information allowed towards one DRB, the maximum value is 2. 9.2.2.9 UE CONTEXT MODIFICATION FAILURE This message is sent by the gNB-DU to indicate a context modification failure. @@ -2673,7 +3870,7 @@ DRB Required to Be Modified List 0..1 -EACH +YES reject >DRB Required to Be Modified Item IEs @@ -2689,34 +3886,41 @@ M - ->>DL Tunnels to be setup List +>>DL UP TNL Information to be setup List 0..1 ->>>DL Tunnels to Be Setup Item IEs +>>>DL UP TNL Information to Be Setup Item IEs -1 .. +1 .. ->>>>DL GTP Tunnel Endpoint +>>>>DL UP TNL Information M -GTP Tunnel Endpoint +UP Transport Layer Information 9.3.2.1 gNB-CU endpoint of the F1 transport bearer. For delivery of DL PDUs. - - +>>RLC Status +O + +9.3.1.69 +Indicates the RLC has been re-established at the gNB-DU. +- +- SRB Required to be Released List 0..1 -EACH +YES reject >SRB Required to be Released List Item IEs @@ -2737,7 +3941,7 @@ DRB Required to be Released List 0..1 -EACH +YES reject >DRB Required to be Released List Item IEs @@ -2767,8 +3971,8 @@ maxnoofSRBs Maximum no. of SRB allowed towards one UE, the maximum value is 8. maxnoofDRBs Maximum no. of DRB allowed towards one UE, the maximum value is 64. -maxnoofDLTunnels -Maximum no. of tunnels allowed towards one DRB, the maximum value is 2. +maxnoofDLUPTNLInformation +Maximum no. of DL UP TNL Information allowed towards one DRB, the maximum value is 2. 9.2.2.11 UE CONTEXT MODIFICATION CONFIRM This message is sent by the gNB-CU to inform the gNB-DU the successful modification. @@ -2829,56 +4033,35 @@ M - ->>UL Tunnels to be setup List +>>UL UP TNL Information to be setup List 1 ->>>UL Tunnels to Be Setup Item IEs +>>>UL UP TNL Information to Be Setup Item IEs -1 .. +1 .. ->>>>UL GTP Tunnel Endpoint +>>>>UL UP TNL Information M -GTP Tunnel Endpoint +UP Transport Layer Information 9.3.2.1 gNB-DU endpoint of the F1 transport bearer. For delivery of UL PDUs. -DRB Failed to be Modified List - -0..1 - -The list of DRBs which are failed to be modified. -YES -ignore ->DRB Failed to be Modified Item IEs - -1 .. - - -EACH -ignore ->>DRB ID -M - -9.3.1.8 - -- - ->>Cause +RRC-Container O -9.3.1.2 - -- -- +9.3.1.6 +Includes the RRCConnectionReconfiguration message as defined in TS 38.331 [8], encapsulated in a PDCP PDU. +YES +ignore Criticality Diagnostics O @@ -2886,19 +4069,207 @@ O YES ignore +Execute Duplication +O + +ENUMERATED (true, ...) +This IE may be sent only if duplication has been configured for the UE. +YES +Ignore Range bound Explanation -maxnoofSRBs -Maximum no. of SRB allowed towards one UE, the maximum value is 8. maxnoofDRBs Maximum no. of DRB allowed towards one UE, the maximum value is 64. -maxnoofULTunnels -Maximum no. of tunnels allowed towards one DRB, the maximum value is 2. +maxnoofULUPTNLInformation +Maximum no. of UL UP TNL Information allowed towards one DRB, the maximum value is 2. + +9.2.2.12 UE INACTIVITY NOTIFCATION +This message is sent by the gNB-DU to provide information about the UE activity to the gNB-CU. +Direction: gNB-DU  gNB-CU +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Criticality +Assigned Criticality +Message Type +M + +9.3.1.1 + +YES +reject +gNB-CU UE F1AP ID +M + +9.3.1.4 + +YES +reject +gNB-DU UE F1AP ID +M + +9.3.1.5 + +YES +reject +DRB Activity List + +1 + + +YES +reject +>DRB Activity Item + +1 .. + + +EACH +reject +>>DRB ID +M + +9.3.1.8 + +- +- +>>DRB Activity +M + +ENUMERATED (Active, Not active, ...) + +- +- + +Range bound +Explanation +maxnoofDRBs +Maximum no. of DRB allowed towards one UE, the maximum value is 64. + +9.2.2.13 NOTIFY +This message is sent by the gNB-DU to notify the gNB-CU that the QoS for already established DRBs associated with notification control is not fulfilled any longer or it is fulfilled again. +Direction: gNB-DU  gNB-CU +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Criticality +Assigned Criticality +Message Type +M + +9.3.1.1 + +YES +ignore +gNB-CU UE F1AP ID +M + +9.3.1.4 + +YES +reject +gNB-DU UE F1AP ID +M + +9.3.1.5 + +YES +reject +DRB Notify List + +1 + + +YES +reject +>DRB Notify Item IEs + +<1 .. maxnoofDRBs> + + +EACH +reject +>>DRB ID +M + +9.3.1.8 + +- +- +>>Notification Cause +M + +ENUMERATED(Fulfilled, Not-Fulfilled, ...) + +- +- 9.2.3 RRC Message Transfer messages -9.2.3.1 Void -Reserved for future use. +9.2.3.1 INITIAL UL RRC MESSAGE TRANSFER +This message is sent by the gNB-DU to transfer the initial layer 3 message to the gNB-CU over the F1 interface. +Direction: gNB-DU gNB-CU +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Criticality +Assigned Criticality +Message Type +M + +9.3.1.1 + +YES +ignore +gNB-DU UE F1AP ID +M + +9.3.1.5 + +YES +reject +NR CGI +M + +9.3.1.12 +NG-RAN Cell Global Identifier (NR CGI) +YES +reject +C-RNTI +M + +9.3.1.32 +C-RNTI allocated at the gNB-DU +YES +reject +RRC-Container +M + +9.3.1.6 +Includes the UL-CCCH-Message IE as defined in subclause 6.2 of TS 38.331 [8]. +YES +reject +DU to CU RRC Container +O + +OCTET STRING +CellGroupConfig IE as defined in subclause 6.3.2 in TS 38.331. Required at least to carry SRB1 configuration +YES +reject +SUL Access Indication +O + +ENUMERATED (true, ...) + +YES +ignore + 9.2.3.2 DL RRC MESSAGE TRANSFER This message is sent by the gNB-CU to transfer the layer 3 message to the gNB-DU over the F1 interface. Direction: gNB-CU gNB-DU @@ -2944,10 +4315,24 @@ M YES reject +Execute Duplication +O + +ENUMERATED (true, ...) + +YES +ignore RRC-Container M 9.3.1.6 +Includes the DL-DCCH-Message IE as defined in subclause 6.2 of TS 38.331 encapsulated in a PDCP PDU, or the DL-CCCH-Message IE as defined in subclause 6.2 of TS 38.331 [8]. +YES +reject +RAT-Frequency Priority Information +O + +9.3.1.34 YES reject @@ -2994,9 +4379,462 @@ RRC-Container M 9.3.1.6 +Includes the UL-DCCH-Message IE as defined in subclause 6.2 of TS 38.331 [8], encapsulated in a PDCP PDU. +YES +reject + +9.2.4 Warning Message Transmission Messages +9.2.4.1 WRITE-REPLACE WARNING REQUEST +This message is sent by the gNB-CU to request the start or overwrite of the broadcast of a warning message. +Direction: gNB-CU  gNB-DU +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Criticality +Assigned Criticality +Message Type +M + +9.3.1.1 YES reject +Transaction ID +M + +9.3.1.23 + +YES +reject +PWS System Information +M + +9.3.1.58 +This IE includes the system information for public warning, as defined in TS 38.331 [8]. +YES +reject +Cell To Be Broadcast List + +0..1 + + +YES +reject +>Cell to Be Broadcast Item IEs + +1.. + + +EACH +reject +>>NR CGI +M + +9.3.1.12 + +- +- +Repetition Period +M + +9.3.1.59 + +YES +reject +Number of Broadcasts Requested +M + +9.3.1.60 + +YES +reject + + +9.2.4.2 WRITE-REPLACE WARNING RESPONSE +This message is sent by the gNB-DU to acknowledge the gNB-CU on the start or overwrite request of a warning message. +Direction: gNB-DU  gNB-CU +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Criticality +Assigned Criticality +Message Type +M + +9.3.1.1 + +YES +reject +Transaction ID +M + +9.3.1.23 + +YES +reject +Cell Broadcast Completed List + +0..1 + + +YES +reject +>Cell Broadcast Completed Item IEs + +1.. + + +EACH +reject +>>NR CGI +M + +9.3.1.12 + +- +- +Criticality Diagnostics +O + +9.3.1.3 + +YES +ignore + + +9.2.4.3 PWS CANCEL REQUEST +This message is forwarded by the gNB-CU to gNB-DU to cancel an already ongoing broadcast of a warning message +Direction: gNB-CU  gNB-DU +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Criticality +Assigned Criticality +Message Type +M + +9.3.1.1 + +YES +reject +Transaction ID +M + +9.3.1.23 + +YES +reject +Cell Broadcast To Be Cancelled List + +0..1 + + +YES +reject +>Cell Broadcast to Be Cancelled Item IEs + +1.. + + +EACH +reject +>>NR CGI +M + +9.3.1.12 + +- +- +Cancel-all Warning Messages Indicator +O + +9.3.1.55 +ENUMERATED (true, ...) +YES +reject + + +9.2.4.4 PWS CANCEL RESPONSE +This message is sent by the gNB-DU to indicate the list of warning areas where cancellation of the broadcast of the identified message was successful and unsuccessful. +Direction: gNB-DU  gNB-CU +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Criticality +Assigned Criticality +Message Type +M + +9.3.1.1 + +YES +reject +Transaction ID +M + +9.3.1.23 + +YES +reject +Cell Broadcast Cancelled List + +0..1 + + +YES +reject +>Cell Broadcast Cancelled Item IEs + +1.. + + +EACH +reject +>>NR CGI +M + +9.3.1.12 + +- +- +>>Number of Broadcasts +M + +INTEGER (0..65535) +This IE is set to ‘0’ if valid results are not known or not available. It is set to 65535 if the counter results have overflowed. +- +- +Criticality Diagnostics +O + +9.3.1.3 + +YES +ignore + +9.2.4.5 PWS RESTART INDICATION +This message is sent by the gNB-DU to inform the gNB-CU that PWS information for some or all cells of the gNB-DU are available if needed. +Direction: gNB-DU gNB-CU +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Criticality +Assigned Criticality +Message Type +M + +9.3.1.1 + +YES +ignore +NR CGI List for Restart List + +0..1 + + +YES +reject +>NR CGI List for Restart Item IEs + +1.. + + +EACH +reject +>>NR CGI +M + +9.3.1.12 + +- +- + +Range bound +Explanation +maxnoofCellsingNBDU +Maximum no. of cells that can be served by an gNB-DU. Value is 512. + +9.2.4.6 PWS FAILURE INDICATION +This message is sent by the gNB-DU to inform the gNB-CU that ongoing PWS operation for one or more cells of the gNB-DU has failed. +Direction: gNB-DU  gNB-CU +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Criticality +Assigned Criticality +Message Type +M + +9.3.1.1 + +YES +ignore +PWS failed NR CGI List + +0..1 + + +YES +reject +>PWS failed NR CGI Item IEs + +1.. + + +EACH +reject +>>NR CGI +M + +9.3.1.12 + +- +- + +Range bound +Explanation +maxnoofCellsingNBDU +Maximum no. of cells that can be served by an gNB-DU. Value is 512. + +9.2.5 System Information messages +9.2.5.1 SYSTEM INFORMATION DELIVERY COMMAND +This message is sent by the gNB-CU and is used to enable the gNB-DU to broadcast the requested other SI. +Direction: gNB-CU  gNB-DU +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Criticality +Assigned Criticality +Message Type +M + +9.3.1.1 + +YES +reject +NR CGI +M + +9.3.1.12 +NR cell identifier +- + +SIType List +M + +9.3.1.62 + + + +Confirmed UE ID +M + +gNB-DU UE F1AP ID +9.3.1.5 + +YES +reject + +9.2.6 Paging messages +9.2.6.1 PAGING +This message is sent by the gNB-CU and is used to request the gNB-DU to page UEs. +Direction: gNB-CU  gNB-DU +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Criticality +Assigned Criticality +Message Type +M + +9.3.1.1 + +YES +reject +UE Identity Index value +M + +9.3.1.39 + +YES +reject +Choice Paging Identity +M + + + + + +>RAN UE Paging identity + + +9.3.1.43 + +YES +reject +>CN UE paging identity + + +9.3.1.44 + +YES +reject +Paging DRX +O + +9.3.1.40 +It is defined as the minimum between the RAN UE Paging DRX and CN UE Paging DRX +YES +ignore +Paging Priority +O + +9.3.1.41 + +YES +ignore +Paging Cell List + +1 + + +YES +ignore +>Paging Cell Item IEs + +1 .. + + +EACH +ignore +>>NR CGI +M + +9.3.1.12 + +- + + +Range bound +Explanation +maxnoofPagingCells +Maximum no. of paging cells, the maximum value is 512. 9.3 Information Element Definitions 9.3.1 Radio Network Layer Related IEs @@ -3020,7 +4858,7 @@ INTEGER (0..255) >Type of Message M -CHOICE (Initiating Message, Successful Outcome, Unsuccessful Outcome, …) +CHOICE (Initiating Message, Successful Outcome, Unsuccessful Outcome, ...) 9.3.1.2 Cause @@ -3044,14 +4882,14 @@ M M ENUMERATED -(Unspecified, RLC failure, Unknown or already allocated gNB-CU UE F1AP ID, +(Unspecified, RL failure-RLC, Unknown or already allocated gNB-CU UE F1AP ID, Unknown or already allocated gNB-DU UE F1AP ID, Unknown or inconsistent pair of UE F1AP ID, Interaction with other procedure, Not supported QCI Value, Action Desirable for Radio Reasons, No Radio Resources Available, -Procedure cancelled, Normal Release, …) +Procedure cancelled, Normal Release, ..., Cell not available, RL failure-others, UE rejection, Resources not available for the slice) >Transport Layer @@ -3062,7 +4900,7 @@ Procedure cancelled, Normal Release, …) M ENUMERATED -(Unspecified, Transport Resource Unavailable, …) +(Unspecified, Transport Resource Unavailable, ...) >Protocol @@ -3078,7 +4916,7 @@ Abstract Syntax Error (Reject), Abstract Syntax Error (Ignore and Notify), Message not Compatible with Receiver State, Semantic Error, -Abstract Syntax Error (Falsely Constructed Message), Unspecified, …) +Abstract Syntax Error (Falsely Constructed Message), Unspecified, ...) >Misc @@ -3092,7 +4930,7 @@ ENUMERATED (Control Processing Overload, Not enough User Plane Processing Resources, Hardware Failure, O&M Intervention, -Unspecified, …) +Unspecified, ...) The meaning of the different cause values is described in the following table. In general, "not supported" cause values indicate that the related capability is missing. On the other hand, "not available" cause values indicate that the related capability is present, but insufficient resources were available to perform the requested action. @@ -3100,8 +4938,8 @@ Radio Network Layer cause Meaning Unspecified Sent for radio network layer cause when none of the specified cause values applies. -RLC Failure -The action is due to an RLC failure. +RL Failure-RLC +The action is due to an RL failure caused by exceeding the maximum number of ARQ retransmissions. Unknown or already allocated gNB-CU UE F1AP ID The action failed because the gNB-CU UE F1AP ID is either unknown, or (for a first message received at the gNB-CU) is known and already allocated to an existing context. Unknown or already allocated gNB-DU UE F1AP ID @@ -3119,7 +4957,15 @@ The cell(s) in the requested node don’t have sufficient radio resources availa Procedure cancelled The sending node cancelled the procedure due to other urgent actions to be performed. Normal Release -The action is due to a normal release of the UE (e.g. because of mobility) and does not indicate an error +The action is due to a normal release of the UE (e.g. because of mobility) and does not indicate an error. +Cell Not Available +The action failed due to no cell available in the requested node. +RL Failure-others +The action is due to an RL failure caused by other radio link failures than exceeding the maximum number of ARQ retransmissions. +UE rejection +The action is due to gNB-CU’s rejection of a UE access request. +Resources not available for the slice +The requested resources are not available for the slice. Transport Layer cause Meaning @@ -3204,7 +5050,7 @@ The IE ID of the not understood or missing IE. >Type of Error M -ENUMERATED(not understood, missing, …) +ENUMERATED(not understood, missing, ...) Range bound @@ -3262,7 +5108,7 @@ Semantics description SRB ID M -INTEGER (1..3, ...) +INTEGER (0..3, ...) Corresponds to the SRB-Identity defined in TS 38.331 [8]. 9.3.1.8 DRB ID @@ -3314,14 +5160,21 @@ INTEGER (0..1007) Physical Cell ID -Extended-TAC -M +5GS TAC +O 9.3.1.29 -Tracking Area Code -YES -reject -Broadcast PLMNs +5GS Tracking Area Code +- +- +Configured EPS TAC +O + +9.3.1.29a + +– + +Served PLMNs 1.. @@ -3333,6 +5186,14 @@ M 9.3.1.14 +- +- +>TAI Slice Support List +O + +Slice Support List +9.3.1.37 +Supported S-NSSAIs per TA. - - CHOICE NR-Mode-Info @@ -3356,18 +5217,18 @@ M - - ->>>UL ARFCN +>>>UL FreqInfo M -NR ARFCN +NR Frequency Info 9.3.1.17 – – ->>>DL ARFCN +>>>DL FreqInfo M -NR ARFCN +NR Frequency Info 9.3.1.17 – @@ -3402,10 +5263,10 @@ NR Transmission Bandwidth - - ->>>ARFCN +>>> NR FreqInfo M -NR ARFCN +NR Frequency Info 9.3.1.17 – @@ -3418,20 +5279,20 @@ NR Transmission Bandwidth – – -SUL Information -O - -9.3.1.28 - -- -- Measurement Timing Configuration M OCTET STRING -Contains the MeasurementTimingConfiguration IE defined in TS 38.331 [8]. +Contains the MeasurementTimingConfiguration inter-node message defined in TS 38.331 [8]. – – +RANAC +O + +9.3.1.57 +RAN Area Code +YES +ignore 9.3.1.11 Transmission Stop Indicator @@ -3445,7 +5306,7 @@ Transmission Stop Indicator M ENUMERATED -(true, …) +(stop, ..., restart) 9.3.1.12 NR CGI @@ -3510,7 +5371,7 @@ Semantics Description NR SCS M -ENUMERATED (scs15, scs30, scs60, scs120, …) +ENUMERATED (scs15, scs30, scs60, scs120, ...) The values scs15, scs30, scs60 and scs120 corresponds to the sub carrier spacing in TS 38.104 [17]. NRB M @@ -3520,8 +5381,8 @@ This IE is used to indicate the UL or DL transmission bandwidth expressed in uni 9.3.1.16 Void Reserved for future use. -9.3.1.17 NR ARFCN -The NR Absolute Radio Frequency Channel Number defines the carrier frequency used in a cell for a given direction (UL or DL) in FDD or for both UL and DL directions in TDD or for an SUL carrier. +9.3.1.17 NR Frequency Info +The NR Frequency Info defines the carrier frequency used in a cell for a given direction (UL or DL) in FDD or for both UL and DL directions in TDD or for an SUL carrier. IE/Group Name Presence Range @@ -3531,12 +5392,46 @@ NR ARFCN M INTEGER (0.. maxNRARFCN) +RF Reference Frequency as defined in TS 38.104 [17] section 5.4.2.1. The frequency provided in this IE identifies the absolute frequency position of the reference resource block (Common RB 0) of the carrier. Its lowest subcarrier is also known as Point A. +SUL Information +O +9.3.1.28 + +Frequency Band List + +1 + + +>Frequency Band Item + +1.. + + +>>NR Frequency Band +M + +INTEGER (1.. 1024 ...) +Operating Band as defined in TS 38.104 [17] section 5.4.2.3. +The value 1 corresponds to NR operating band n1, value 2 corresponds to NR operating band n2, etc. +>>Supported SUL band List + +0.. + + +>>>Supported SUL band Item +M + +INTEGER (1.. 1024, ...) +Supplementary NR Operating Band as defined in TS 38.104 [17] section 5.4.2.3 that can be used for SUL duplex mode as per TS 38.101-1 table 5.2.-1. +The value 80 corresponds to NR operating band n80, value 81 corresponds to NR operating band n81, etc. Range bound Explanation maxNRARFCN -Maximum value of NR ARFCNs. Value is 3266667. +Maximum value of NR ARFCNs. Value is 3279165. +maxnoofNrCellBands +Maximum no. of frequency bands supported for a NR cell. Value is 32. 9.3.1.18 gNB-DU System Information This IE contains the system information generated by the gNB-DU. @@ -3571,7 +5466,7 @@ QCI M INTEGER (0..255) -QoS Class Identifier defined in TS 23.401[10]. +QoS Class Identifier defined in TS 23.401 [10]. Logical range and coding specified in TS 23.203 [11]. – – @@ -3679,7 +5574,7 @@ Semantics description Bit Rate M -INTEGER (0.. 4,000,000,000,000,…) +INTEGER (0.. 4,000,000,000,000,...) The unit is: bit/s 9.3.1.23 Transaction ID @@ -3692,7 +5587,7 @@ Semantics description Transaction ID M -INTEGER (0..255, …) +INTEGER (0..255, ...) 9.3.1.24 DRX Cycle @@ -3706,7 +5601,7 @@ Long DRX Cycle Length M ENUMERATED -(ms10, ms20, ms32, ms40, ms60, ms64, ms70, ms80, ms128, ms160, ms256, ms320, ms512, ms640, ms1024, ms1280, ms2048, ms2560, ms5120, ms10240, …) +(ms10, ms20, ms32, ms40, ms60, ms64, ms70, ms80, ms128, ms160, ms256, ms320, ms512, ms640, ms1024, ms1280, ms2048, ms2560, ms5120, ms10240, ...) This IE is defined in TS 38.331 [8] Short DRX Cycle Length O @@ -3736,6 +5631,29 @@ O OCTET STRING UE-CapabilityRAT-ContainerList, as defined in TS 38.331 [8]. +MeasConfig +O + +OCTET STRING +MeasConfig, as defined in TS 38.331 (without MeasGapConfig). +For EN-DC operation, includes the list of FR2 frequencies for which the gNB-CU requests the gNB-DU to generate gaps. +For NG-RAN, includes the list of FR1 and/or FR2 frequencies for which the gNB-CU requests the gNB-DU to generate gaps and the gap type (per-UE or per-FR). +Handover Preparation Information +O + +OCTET STRING +HandoverPreparationInformation, as defined in TS 38.331 [8]. +CellGroupConfig +O + +OCTET STRING +CellGroupConfig, as defined in TS 38.331 [8]. +Measurement Timing Configuration +O + +OCTET STRING +Contains the MeasurementTimingConfiguration inter-node message defined in TS 38.331 [8]. +In EN-DC, it is included when the gaps for FR2 are requested to be configured by the MeNB. 9.3.1.26 DU to CU RRC Information This IE contains the RRC Information that are sent from the gNB-DU to the gNB-CU. @@ -3749,11 +5667,20 @@ M OCTET STRING CellGroupConfig, as defined in TS 38.331 [8]. -Gap Offset +MeasGapConfig O OCTET STRING -Gapoffset to be defined in TS 38.331 [8]. +MeasGapConfig as defined in TS 38.331 [8]. +For EN-DC operation, includes the gap for FR2, as requested by the gNB-CU via MeasConfig IE. + +For NG-RAN, includes the gap(s) for FR1 and/or FR2, as requested by the gNB-CU via MeasConfig IE and according to the requested gap type (per-UE or per-FR). +Requested P-MaxFR1 +O + +OCTET STRING +requestedP-MaxFR1, as defined in TS 38.331 [8]. +For EN-DC operation, this IE should be included, as requested by the gNB-CU via CG-ConfigInfo IE. 9.3.1.27 RLC Mode The RLC Mode IE indicates the RLC Mode used for a DRB. @@ -3766,7 +5693,7 @@ RLC Mode ENUMERATED ( -RLC-AM, RLC-UM,…) +RLC-AM, RLC-UM-Bidirectional, RLC-UM-Unidirectional-UL, RLC-UM-Unidirectionall-DL, ...) 9.3.1.28 SUL Information @@ -3779,9 +5706,8 @@ Semantics description SUL ARFCN M -NR ARFCN -9.3.1.17 - +INTEGER (0.. maxNRARFCN) +RF Reference Frequency as defined in TS 38.104 [17] section 5.4.2.1. The frequency provided in this IE identifies the absolute frequency position of the reference resource block (Common RB 0) of the SUL carrier. Its lowest subcarrier is also known as Point A. SUL Transmission Bandwidth M @@ -3789,19 +5715,37 @@ NR Transmission Bandwidth 9.3.1.15 -9.3.1.29 Extended-TAC +Range bound +Explanation +maxNRARFCN +Maximum value of NR ARFCNs. Value is 3279165. + +9.3.1.29 5GS TAC This information element is used to identify Tracking Area Code. IE/Group Name Presence Range IE type and reference Semantics description -Extended-TAC +5GS TAC M OCTET STRING (SIZE (3)) +9.3.1.29a Configured EPS TAC +This information element is used to identify a configured EPS Tracking Area Code in order to enable application of Roaming and Access Restrictions for EN-DC as specified in TS 37.340 [7]. This IE is configured for the cell, but not broadcast. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Configured EPS TAC +M + +OCTET STRING (SIZE (2)) + + 9.3.1.30 RRC Reconfiguration Complete Indicator This IE indicates the successful reconfiguration performed in the UE. IE/Group Name @@ -3812,7 +5756,7 @@ Semantics description RRC Reconfiguration Complete Indicator M -ENUMERATED (true, …) +ENUMERATED (true, ...) 9.3.1.31 UL Configuration @@ -3828,9 +5772,94 @@ M ENUMERATED (no-data, shared, only, ..) Indicates how the UE uses the UL at gNB-DU, for which “no-data” indicates that the UL scheduling is not performed at gNB-DU, “shared” indicates that the UL scheduling is performed at both gNB-DU and another node, and “only” indicates that the UL scheduling is only performed at the gNB-DU. -9.3.2 Transport Network Layer Related IEs -9.3.2.1 GTP Tunnel Endpoint -The GTP Tunnel Endpoint IE identifies an F1 transport bearer associated to a DRB. It contains a Transport Layer Address and a GTP Tunnel Endpoint Identifier. The Transport Layer Address is an IP address to be used for the F1 user plane transport. The GTP Tunnel Endpoint Identifier is to be used for the user plane transport between gNB-CU and gNB-DU. +9.3.1.32 C-RNTI +This IE contains the C-RNTI information. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +C-RNTI +M + +INTEGER (0..65535, ...) +C-RNTI as defined in TS 38.331 [8]. + +9.3.1.33 Cell UL Configured +This IE indicates whether the gNB-CU requests the gNB-DU to configure the uplink as no UL, UL, SUL or UL+SUL for the indicated cell for the UE. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Cell UL Configured +M + +ENUMERATED (none, UL, SUL, UL and SUL, ...) +Further details are defined in TS 38.331 [8] + +9.3.1.34 RAT-Frequency Priority Information +The RAT-Frequency Priority Information contains either the Subscriber Profile ID for RAT/Frequency priority IE or the Index to RAT/Frequency Selection Priority IE. These parameters are used to define local configuration for RRM strategies. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +CHOICE RAT-Frequency Priority Information +M + + + +>EN-DC + + + + +>>Subscriber Profile ID for RAT/Frequency priority +O + +INTEGER (1.. 256, ...) + +>NG-RAN + + + + +>> Index to RAT/Frequency Selection Priority +O + +INTEGER (1.. 256, ...) + + +9.3.1.35 LCID +This IE uniquely identifies a LCID for the associated SRB or DRB. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +LCID +M + +INTEGER (1..32, ...) +Corresponds to the LogicalChannelIdentity defined in TS 38.331 [8]. + +9.3.1.36 Duplication activation +The Duplication Activation IE indicates whether UL PDCP Duplication is activated or not. +IE/Group Name +Presence +Range +IE Type and Reference +Semantics Description +Duplication Activation +M + +ENUMERATED ( +Active, Inactive, ...) + + +9.3.1.37 Slice Support List +This IE indicates the list of supported slices. IE/Group Name Presence Range @@ -3838,20 +5867,856 @@ IE type and reference Semantics description Criticality Assigned Criticality +Slice Support Item IEs + +1.. + + +- +- +>S-NSSAI +M + +9.3.1.38 + +- + + +Range bound +Explanation +maxnoofSliceItems +Maximum no. of signalled slice support items. Value is 1024. + +9.3.1.38 S-NSSAI +This IE indicates the S-NSSAI. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +SST +M + +OCTET STRING (SIZE(1)) + +SD +O + +OCTET STRING (SIZE(3)) + + +9.3.1.39 UE Identity Index value +This IE is used by the gNB-DU to calculate the Paging Frame. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +CHOICE UE Identity Index Value +M + + + +>Length-10 + + + + +>>Index Length 10 +M + +BIT STRING (SIZE(10)) +Coded as specified in TS 38.304 [24]. + +9.3.1.40 Paging DRX +This IE indicates the Paging DRX as defined in TS 38.304 [24]. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Paging DRX +M + +ENUMERATED(32, 64, 128, 256, ...) +Unit in radio frame. + +9.3.1.41 Paging Priority +This IE indicates the paging priority for paging a UE. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Paging Priority +M + +ENUMERATED (PrioLevel1, PrioLevel2, PrioLevel3, PrioLevel4, PrioLevel5, PrioLevel6, PrioLevel7, PrioLevel8, ...) +Lower value codepoint indicates higher priority. + +9.3.1.42 gNB-CU System Information +This IE contains the system information encoded by the gNB-CU. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +SIB type to Be Updated List + +1 + + +>SIB type to Be Updated Item IEs + +1... + + +>>SIB type +M + +INTEGER (2..32, ...) +Indicates a certain SIB block, e.g. 2 means sibType2, 3 for sibType3, etc. +>>SIB message +M + +OCTET STRING +SIB message containing SIB as defined in TS 38.331 [8]. +>>Value Tag +M + +INTEGER (0..31) + + +Range bound +Explanation +maxnoofSIBTypes +Maximum no. of SIB types, the maximum value is 32. + +9.3.1.43 RAN UE Paging identity +This IE indicates the RAN UE Paging identity. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +I-RNTI +M + +BIT STRING (SIZE(40)) + + +9.3.1.44 CN UE Paging Identity +The 5G-S-TMSI is used as UE identifier for CN paging. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +CHOICE CN UE paging identity +M + + + +>5G-S-TMSI + + + + +>>5G-S-TMSI +M + +BIT STRING (SIZE(48)) +Details defined in TS 38.413 [3] + +9.3.1.45 QoS Flow Level QoS Parameters +This IE defines the QoS to be applied to a QoS flow or to a DRB. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Criticality +Assigned Criticality +CHOICE QoS Characteristics +M + + + +YES +reject +>Non-dynamic 5QI + + + + +- + +>>Non Dynamic 5QI Descriptor +M + +9.3.1.49 + +- + +>Dynamic 5QI + + + + +- + +>>Dynamic 5QI Descriptor +M + +9.3.1.47 + +- + +NG-RAN Allocation and Retention Priority +M + +9.3.1.48 + +- + +GBR QoS Flow Information +O + +9.3.1.46 +This IE shall be present for GBR QoS Flows only. +- + +Reflective QoS Attribute +O + +ENUMERATED (subject to, ...) +Details in TS 23.501 [21]. This IE applies to non-GBR flows only and shall be ignored otherwise. +- + +PDU Session ID +O + +INTEGER (0 ..255) +As specified in TS 23.501 [21]. +- + +UL PDU Session Aggregate Maximum Bit Rate +O + +Bit Rate +9.3.1.22 +The gNB-DU PDU session Aggregate Maximum Bit Rate Uplink which is to be enforced by the gNB-DU +- + + +9.3.1.46 GBR QoS Flow Information +This IE indicates QoS parameters for a GBR QoS flow or GBR bearer for downlink and uplink. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Criticality +Assigned Criticality +Maximum Flow Bit Rate Downlink +M + +Bit Rate +9.3.1.22 +Maximum Bit Rate in DL. Details in TS 23.501 [21]. +- +- +Maximum Flow Bit Rate Uplink +M + +Bit Rate +9.3.1.22 +Maximum Bit Rate in UL. Details in TS 23.501 [21]. +- +- +Guaranteed Flow Bit Rate Downlink +M + +Bit Rate +9.3.1.22 +Guaranteed Bit Rate (provided there is data to deliver) in DL. Details in TS 23.501 [21]. +- +- +Guaranteed Flow Bit Rate Uplink +M + +Bit Rate +9.3.1.22 +Guaranteed Bit Rate (provided there is data to deliver). Details in TS 23.501 [21]. +- +- +Maximum Packet Loss Rate Downlink +O + +Maximum Packet Loss Rate +9.3.1.50 +Indicates the maximum rate for lost packets that can be tolerated in the downlink direction. Details in TS 23.501 [21]. +- +- +Maximum Packet Loss Rate Uplink +O + +Maximum Packet Loss Rate +9.3.1.50 +Indicates the maximum rate for lost packets that can be tolerated in the uplink direction. Details in TS 23.501 [21]. +- +- + +9.3.1.47 Dynamic 5QI Descriptor +This IE indicates the QoS Characteristics for a Non-standardised or not pre-configured 5QI for downlink and uplink. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +QoS Priority Level +M + +INTEGER (1..127) +For details see TS 23.501 [21]. +Packet Delay Budget +M + +9.3.1.51 +For details see TS 23.501 [21]. +Packet Error Rate +M + +9.3.1.52 +For details see TS 23.501 [21]. +5QI +O + +INTEGER (0..255,...) +This IE contains the dynamically assigned 5QI as specified in TS 23.501 [21]. +Delay Critical +C-ifGBRflow + +ENUMERATED (delay critical, non-delay critical) +For details see TS 23.501 [21]. +Averaging Window +C-ifGBRflow + +9.3.1.53 +For details see TS 23.501 [21]. +Maximum Data Burst Volume +O + +9.3.1.54 +For details see TS 23.501 [21]. This IE shall be included if the Delay Critical IE is set to “delay critical” and shall be ignored otherwise. + +Condition +Explanation +ifGBRflow +This IE shall be present if the GBR QoS Flow Information IE is present in the QoS Flow Level QoS Parameters IE. + +9.3.1.48 NG-RAN Allocation and Retention Priority +This IE specifies the relative importance of a QoS flow or a DRB compared to other QoS flows or DRBs for allocation and retention of NG-RAN resources. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +NG-RAN Allocation and Retention Priority + + + + +>Priority Level +M + +INTEGER (1..15) +Desc.: This IE defines the relative importance of a resource request (see TS 23.501 [21]). +Usage: Values are ordered in decreasing order of priority, i.e., with 1 as the highest priority and 15 as the lowest priority. Further usage is defined in TS 23.501 [21]. +>Pre-emption Capability +M + +ENUMERATED (shall not trigger pre-emption, may trigger pre-emption) +Desc.: This IE indicates the pre-emption capability of the request on other QoS flows. +Usage: The QoS flow shall not pre-empt other QoS flows or, the QoS flow may pre-empt other QoS flows. +The Pre-emption Capability indicator applies to the allocation of resources for a QoS flow and as such it provides the trigger to the pre-emption procedures/processes of the NG-RAN node. +>Pre-emption Vulnerability +M + +ENUMERATED (not pre-emptable, pre-emptable) +Desc.: This IE indicates the vulnerability of the QoS flow to pre-emption of other QoS flows. +Usage: The QoS flow shall not be pre-empted by other QoS flows or the QoS flow may be pre-empted by other QoS flows. The Pre-emption Vulnerability indicator applies for the entire duration of the QoS flow, unless modified and as such indicates whether the QoS flow is a target of the pre-emption procedures/processes of the NG-RAN node. + +9.3.1.49 Non Dynamic 5QI Descriptor +This IE indicates the QoS Characteristics for a standardized or pre-configured 5QI for downlink and uplink. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +5QI +M + +INTEGER (0..255,...) +This IE contains the standardized or pre-configured 5QI as specified in TS 23.501 [21] +Priority Level +O + +INTEGER (1..127) +For details see TS 23.501 [21]. When included overrides standardized or pre-configured value. +Averaging Window +O + +9.3.1.53 +This IE applies to GBR QoS Flows only. For details see TS 23.501 [21]. When included overrides standardized or pre-configured value. +Maximum Data Burst Volume +O + +9.3.1.54 +For details see TS 23.501 [21]. When included overrides standardized or pre-configured value. If the 5QI refers to a non-delay critical QoS flow the IE shall be ignored. + +9.3.1.50 Maximum Packet Loss Rate +This IE indicates the Maximum Packet Loss Rate. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Maximum Packet Loss Rate +M + +INTEGER(0..1000) +Ratio of lost packets per number of packets sent, expressed in tenth of percent. + +9.3.1.51 Packet Delay Budget +This IE indicates the Packet Delay Budget for a QoS flow. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Packet Delay Budget +M + +INTEGER (0..1023, ...) +Upper bound value for the delay that a packet may experience expressed in unit of 0.5ms. + +9.3.1.52 Packet Error Rate +This IE indicates the Packet Error Rate for a QoS flow. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Scalar +M + +INTEGER (0..9, ...) +The packet error rate is expressed as Scalar x 10-k where k is the Exponent. +Exponent +M + +INTEGER (0..9, ...) + + +9.3.1.53 Averaging Window +This IE indicates the Averaging Window for a QoS flow. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Averaging Window +M + +INTEGER (0..4095, ...) +Unit: ms. The default value is 2000ms. + + +9.3.1.54 Maximum Data Burst Volume +This IE indicates the Maximum Data Burst Volume for a QoS flow. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Maximum Data Burst Volume +M + +INTEGER (0..4095, ...) +Unit: byte. + +9.3.1.55 Masked IMEISV +This information element contains the IMEISV value with a mask, to identify a terminal model without identifying an individual Mobile Equipment. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Masked IMEISV +M + +BIT STRING (SIZE (64)) +Coded as the International Mobile station Equipment Identity and Software Version Number (IMEISV) defined in TS 23.003 [23] with the last 4 digits of the SNR masked by setting the corresponding bits to 1. +The first to fourth bits correspond to the first digit of the IMEISV, the fifth to eighth bits correspond to the second digit of the IMEISV, and so on. + +9.3.1.56 Notification Control +The Notification Control IE indicates whether the notification control for a given DRB is active or not-active. If the notification control is set to active, the gNB-DU shall, if supported, monitor the QoS of the DRB and notify the gNB-CU. +IE/Group Name +Presence +Range +IE Type and Reference +Semantics Description +Notification Control +M + +ENUMERATED(Active, Not-Active, ...) + + +9.3.1.57 RAN Area Code +This information element is used to uniquely identify a RAN Area Code. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +RANAC +M + +INTEGER (0..255) +RAN Area Code + +9.3.1.58 PWS System Information +This IE contains the system information used for pubic warning. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +SI message +M + +OCTET STRING +SI message containing only the SIBs for public warning, as defined in TS 38.331 [8]. + +This IE may be re-defined. + + +9.3.1.59 Repetition Period +This IE indicates the periodicity of the warning message to be broadcast. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Repetition Period +M + +INTEGER (0..217-1) +The unit of value 1 to 217-1 is [second]. + +9.3.1.60 Number of Broadcasts Requested +This IE indicates the number of times a message is to be broadcast. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Number of Broadcasts Requested +M + +INTEGER (0..65535) + + +9.3.1.61 Void +9.3.1.62 SIType List +This IE is used by gNB-CU to provide SI list of other SI for gNB-DU. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +SI type item IEs + +1.. + + +>SI Type +M + + +INTEGER (1..32, ...) +Indicates a certain SI type required to be broadcasted by the gNB-DU. + +Range bound +Explanation +maxnoofSITypes +Maximum no. of SI types, the maximum value is 32. + +9.3.1.63 QoS Flow Indicator +This IE identifies a QoS Flow within a PDU Session. The definition and use of the QoS Flow Indicator is specified in TS 23.501 [21]. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +QoS Flow Indicator +M + +INTEGER (0 ..63) + + +9.3.1.64 Served E-UTRA Cell Information +This IE contains served cell information of an E-UTRA cell for spectrum sharing between E-UTRA and NR. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Criticality +Assigned Criticality +CHOICE EUTRA-Mode-Info +M + + + +– +– +>FDD + + + + + + +>>FDD Info + +1 + + +– +– +>>>UL Offset to Point A +M + +INTEGER (0..2199,...) +Indicates the offset to the center of the NR carrier for UL. +– +– +>>>DL Offset to Point A +M + +INTEGER (0..2199,...) +Indicates the offset to the center of the NR carrier for DL. +– +– +>TDD + + + + +– +– +>>TDD Info + +1 + + +– +– +>>>Offset to Point A +M + +INTEGER (0..2199,...) +Indicates the offset to the center of the NR carrier. +– +– +Protected E-UTRA Resource Indication +O + +OCTET STRING +Indicates the Protected E-UTRA Resource Indication as defined in subclause 9.2.125 of TS 36.423 [9]. +YES +ignore + +9.3.1.65 Available PLMN List +This IE indicates the list of available PLMN. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Criticality +Assigned Criticality +Available PLMN Item IEs + +1..< maxnoofBPLMNs > + + +- +- +>PLMN Identity +M + +9.3.1.14 + +- + + +Range bound +Explanation +maxnoofBPLMNs +Maximum no. of Broadcast PLMN Ids. Value is 6. + +9.3.1.66 RLC Failure Indication +This IE indicates the LCID associated with the RLC entity needing re-establishment. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Associated LCID +M + +9.3.1.35 + + +9.3.1.67 Uplink TxDirectCurrentList Information +This IE contains the Uplink TxDirectCurrentList information that is configured by the UE. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Uplink TxDirectCurrentList Information +M + +OCTET STRING +UplinkTxDirectCurrentList as defined in TS 38.331 [8]. + +9.3.1.68 Cell Status +This IE indicates the status of a cell served by the gNB-DU. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Cell State +M + +ENUMERATED (Active, Inactive, ...) +Indicates the state of the cell. Active and Inactive cell states are defined in TS 38.401 [4]. The gNB-CU shall not activate a cell that is reported Inactive using this IE. +Switching Off Ongoing +O + +ENUMERATED (True, ...) +This IE indicates that the gNB-DU will delete the cell after some time using a new gNB-DU Configuration Update procedure. When this IE is set to “True” the Cell State IE shall be set to “Active”. + +9.3.1.69 RLC Status +This IE indicates about the RLC configuration change included in the container towards the UE. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Reestablishment Indication +O + +ENUMERATED (reestablished, ...) +Indicates that following a change in the radio status, the RLC has been re-established. + +9.3.1.70 RRC Version +This information element is used to identify RRC version corresponding to TS 38.331 [8]. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +Latest RRC Version +M + +OCTET STRING (SIZE (3)) +Latest supported RRC version in the release corresponding to TS 38.331 [8]. For a 3GPP specification version x.y.z, x is encoded by the leftmost byte, y by the middle byte, and z by the rightmost byte. + + +9.3.2 Transport Network Layer Related IEs +9.3.2.1 UP Transport Layer Information +The UP Transport Layer Information IE identifies an F1 transport bearer associated to a DRB. It contains a Transport Layer Address and a GTP Tunnel Endpoint Identifier. The Transport Layer Address is an IP address to be used for the F1 user plane transport. The GTP Tunnel Endpoint Identifier is to be used for the user plane transport between gNB-CU and gNB-DU. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +CHOICE Transport Layer Information +M + + + +>GTP Tunnel + + + + +>>Transport Layer Address +M + +9.3.2.3 + +>>GTP-TEID +M + +9.3.2.2 + + +9.3.2.2 GTP-TEID +The GTP-TEID IE is the GTP Tunnel Endpoint Identifier to be used for the user plane transport between the gNB-CU and gNB-DU. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +GTP-TEID +M + +OCTET STRING (SIZE(4)) +For details and range, see TS 29.281 [18]. + +9.3.2.3 Transport Layer Address +This Transport Layer Address IE is an IP address. +IE/Group Name +Presence +Range +IE type and reference +Semantics description Transport Layer Address M -BIT STRING (1..160, ...) +BIT STRING (SIZE(1..160, ...)) +The Radio Network Layer is not supposed to interpret the address information. It should pass it to the Transport Layer for interpretation. +For details, see TS 38.414 [19]. -– -– -GTP TEID +9.3.2.4 CP Transport Layer Information +This IE is used to provide the NG control plane transport layer information associated with an NG-RAN node – AMF pair. +IE/Group Name +Presence +Range +IE type and reference +Semantics description +CHOICE CP Transport Layer Information + + + + +>Endpoint-IP-address + + + + +>> Endpoint IP address M -OCTET STRING (4) +Transport Layer Address 9.3.2.3 -– -– 9.4 Message and Information Element Abstract Syntax (with ASN.1) 9.4.1 General @@ -3917,7 +6782,21 @@ FROM F1AP-CommonDataTypes UEContextReleaseRequest, DLRRCMessageTransfer, ULRRCMessageTransfer, - PrivateMessage + GNBDUResourceCoordinationRequest, + GNBDUResourceCoordinationResponse, + PrivateMessage, + UEInactivityNotification, + InitialULRRCMessageTransfer, + SystemInformationDeliveryCommand, + Paging, + Notify, + WriteReplaceWarningRequest, + WriteReplaceWarningResponse, + PWSCancelRequest, + PWSCancelResponse, + PWSRestartIndication, + PWSFailureIndication, + GNBDUStatusIndication FROM F1AP-PDU-Contents id-Reset, @@ -3932,10 +6811,26 @@ FROM F1AP-PDU-Contents id-UEContextReleaseRequest, id-DLRRCMessageTransfer, id-ULRRCMessageTransfer, - id-privateMessage + id-GNBDUResourceCoordination, + id-privateMessage, + id-UEInactivityNotification, + id-InitialULRRCMessageTransfer, + id-SystemInformationDeliveryCommand, + id-Paging, + id-Notify, + id-WriteReplaceWarning, + id-PWSCancel, + id-PWSRestartIndication, + id-PWSFailureIndication, + id-GNBDUStatusIndication -FROM F1AP-Constants; +FROM F1AP-Constants + + ProtocolIE-SingleContainer{}, + F1AP-PROTOCOL-IES + +FROM F1AP-Containers; -- ************************************************************** @@ -3968,7 +6863,11 @@ WITH SYNTAX { F1AP-PDU ::= CHOICE { initiatingMessage InitiatingMessage, successfulOutcome SuccessfulOutcome, - unsuccessfulOutcome UnsuccessfulOutcome, + unsuccessfulOutcome UnsuccessfulOutcome, + choice-extension ProtocolIE-SingleContainer { { F1AP-PDU-ExtIEs} } +} + +F1AP-PDU-ExtIEs F1AP-PROTOCOL-IES ::= { ... } @@ -4011,7 +6910,10 @@ F1AP-ELEMENTARY-PROCEDURES-CLASS-1 F1AP-ELEMENTARY-PROCEDURE ::= { uEContextSetup | uEContextRelease | uEContextModification | - uEContextModificationRequired , + uEContextModificationRequired | + writeReplaceWarning | + pWSCancel | + gNBDUResourceCoordination , ...} F1AP-ELEMENTARY-PROCEDURES-CLASS-2 F1AP-ELEMENTARY-PROCEDURE ::= { @@ -4019,7 +6921,15 @@ F1AP-ELEMENTARY-PROCEDURES-CLASS-1 F1AP-ELEMENTARY-PROCEDURE ::= { uEContextReleaseRequest | dLRRCMessageTransfer | uLRRCMessageTransfer | - privateMessage , + uEInactivityNotification | + privateMessage | + initialULRRCMessageTransfer | + systemInformationDelivery | + paging | + notify | + pWSRestartIndication | + pWSFailureIndication | + gNBDUStatusIndication , ... } -- ************************************************************** @@ -4089,6 +6999,19 @@ uEContextModificationRequired F1AP-ELEMENTARY-PROCEDURE ::= { CRITICALITY reject } +writeReplaceWarning F1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE WriteReplaceWarningRequest + SUCCESSFUL OUTCOME WriteReplaceWarningResponse + PROCEDURE CODE id-WriteReplaceWarning + CRITICALITY reject +} + +pWSCancel F1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PWSCancelRequest + SUCCESSFUL OUTCOME PWSCancelResponse + PROCEDURE CODE id-PWSCancel + CRITICALITY reject +} errorIndication F1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE ErrorIndication @@ -4103,6 +7026,12 @@ uEContextReleaseRequest F1AP-ELEMENTARY-PROCEDURE ::= { } +initialULRRCMessageTransfer F1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE InitialULRRCMessageTransfer + PROCEDURE CODE id-InitialULRRCMessageTransfer + CRITICALITY ignore +} + dLRRCMessageTransfer F1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE DLRRCMessageTransfer PROCEDURE CODE id-DLRRCMessageTransfer @@ -4116,12 +7045,61 @@ uLRRCMessageTransfer F1AP-ELEMENTARY-PROCEDURE ::= { } +uEInactivityNotification F1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE UEInactivityNotification + PROCEDURE CODE id-UEInactivityNotification + CRITICALITY ignore +} + +gNBDUResourceCoordination F1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE GNBDUResourceCoordinationRequest + SUCCESSFUL OUTCOME GNBDUResourceCoordinationResponse + PROCEDURE CODE id-GNBDUResourceCoordination + CRITICALITY reject +} + privateMessage F1AP-ELEMENTARY-PROCEDURE ::= { INITIATING MESSAGE PrivateMessage PROCEDURE CODE id-privateMessage CRITICALITY ignore } +systemInformationDelivery F1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE SystemInformationDeliveryCommand + PROCEDURE CODE id-SystemInformationDeliveryCommand + CRITICALITY ignore +} + + +paging F1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Paging + PROCEDURE CODE id-Paging + CRITICALITY ignore +} + +notify F1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE Notify + PROCEDURE CODE id-Notify + CRITICALITY ignore +} + +pWSRestartIndication F1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PWSRestartIndication + PROCEDURE CODE id-PWSRestartIndication + CRITICALITY ignore +} + +pWSFailureIndication F1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE PWSFailureIndication + PROCEDURE CODE id-PWSFailureIndication + CRITICALITY ignore +} + +gNBDUStatusIndication F1AP-ELEMENTARY-PROCEDURE ::= { + INITIATING MESSAGE GNBDUStatusIndication + PROCEDURE CODE id-GNBDUStatusIndication + CRITICALITY ignore +} END @@ -4148,19 +7126,22 @@ BEGIN -- ************************************************************** IMPORTS - Active-Cells-Item, Candidate-SpCell-Item, Cause, Cells-Failed-to-be-Activated-List-Item, + Cells-Status-Item, Cells-to-be-Activated-List-Item, - Cells-to-be-Deactivated-List-Item, - CriticalityDiagnostics, - CUtoDURRCInformation, + Cells-to-be-Deactivated-List-Item, + CellULConfigured, + CriticalityDiagnostics, + C-RNTI, + CUtoDURRCInformation, + DRB-Activity-Item, DRBID, - DRBs-FailedToBeModifiedConf-Item, DRBs-FailedToBeModified-Item, DRBs-FailedToBeSetup-Item, DRBs-FailedToBeSetupMod-Item, + DRB-Notify-Item, DRBs-ModifiedConf-Item, DRBs-Modified-Item, DRBs-Required-ToBeModified-Item, @@ -4172,8 +7153,11 @@ IMPORTS DRBs-ToBeSetup-Item, DRBs-ToBeSetupMod-Item, DRXCycle, + DRXConfigurationIndicator, DUtoCURRCInformation, EUTRANQoS, + ExecuteDuplication, + FullConfiguration, GNB-CU-UE-F1AP-ID, GNB-DU-UE-F1AP-ID, GNB-DU-ID, @@ -4181,10 +7165,13 @@ IMPORTS GNB-DU-System-Information, GNB-CU-Name, GNB-DU-Name, - GTPTunnelEndpoint, + InactivityMonitoringRequest, + InactivityMonitoringResponse, + NotificationControl, NRCGI, NRPCI, Potential-SpCell-Item, + RAT-FrequencyPriorityInformation, ResourceCoordinationTransferContainer, RRCContainer, RRCRconfigurationCompleteIndicator, @@ -4193,7 +7180,8 @@ IMPORTS SCell-ToBeSetup-Item, SCell-ToBeSetupMod-Item, SCell-FailedtoSetup-Item, - SCell-FailedtoSetupMod-Item, + SCell-FailedtoSetupMod-Item, + ServCellIndex, Served-Cell-Information, Served-Cells-To-Add-Item, Served-Cells-To-Delete-Item, @@ -4209,7 +7197,42 @@ IMPORTS TransactionID, TransmissionStopIndicator, UE-associatedLogicalF1-ConnectionItem, - ULTunnels-ToBeSetup-Item + DUtoCURRCContainer, + PagingCell-Item, + SItype-List, + UEIdentityIndexValue, + GNB-CU-TNL-Association-Setup-Item, + GNB-CU-TNL-Association-Failed-To-Setup-Item, + GNB-CU-TNL-Association-To-Add-Item, + GNB-CU-TNL-Association-To-Remove-Item, + GNB-CU-TNL-Association-To-Update-Item, + MaskedIMEISV, + PagingDRX, + PagingPriority, + PagingIdentity, + Cells-to-be-Barred-Item, + PWSSystemInformation, + Broadcast-To-Be-Cancelled-Item, + Cells-Broadcast-Cancelled-Item, + NR-CGI-List-For-Restart-Item, + PWS-Failed-NR-CGI-Item, + RepetitionPeriod, + NumberofBroadcastRequest, + Cells-To-Be-Broadcast-Item, + Cells-Broadcast-Completed-Item, + Cancel-all-Warning-Messages-Indicator, + EUTRA-NR-CellResourceCoordinationReq-Container, + EUTRA-NR-CellResourceCoordinationReqAck-Container, + RequestType, + PLMN-Identity, + RLCFailureIndication, + UplinkTxDirectCurrentListInformation, + SULAccessIndication, + Protected-EUTRA-Resources-Item, + GNB-DUConfigurationQuery, + BitRate, + RRC-Version, + GNBDUOverloadInformation FROM F1AP-IEs @@ -4225,21 +7248,24 @@ FROM F1AP-IEs FROM F1AP-Containers - id-Active-Cells-Item, - id-Active-Cells-List, id-Candidate-SpCell-Item, id-Candidate-SpCell-List, id-Cause, + id-Cancel-all-Warning-Messages-Indicator, id-Cells-Failed-to-be-Activated-List, - id-Cells-Failed-to-be-Activated-List-Item, + id-Cells-Failed-to-be-Activated-List-Item, + id-Cells-Status-Item, + id-Cells-Status-List, id-Cells-to-be-Activated-List, id-Cells-to-be-Activated-List-Item, id-Cells-to-be-Deactivated-List, id-Cells-to-be-Deactivated-List-Item, + id-ConfirmedUEID, id-CriticalityDiagnostics, + id-C-RNTI, id-CUtoDURRCInformation, - id-DRBs-FailedToBeModifiedConf-Item, - id-DRBs-FailedToBeModifiedConf-List, + id-DRB-Activity-Item, + id-DRB-Activity-List, id-DRBs-FailedToBeModified-Item, id-DRBs-FailedToBeModified-List, id-DRBs-FailedToBeSetup-Item, @@ -4250,6 +7276,8 @@ FROM F1AP-Containers id-DRBs-ModifiedConf-List, id-DRBs-Modified-Item, id-DRBs-Modified-List, + id-DRB-Notify-Item, + id-DRB-Notify-List, id-DRBs-Required-ToBeModified-Item, id-DRBs-Required-ToBeModified-List, id-DRBs-Required-ToBeReleased-Item, @@ -4268,16 +7296,21 @@ FROM F1AP-Containers id-DRBs-ToBeSetupMod-List, id-DRXCycle, id-DUtoCURRCInformation, - id-gNB-CU-UE-F1AP-ID, + id-ExecuteDuplication, + id-FullConfiguration, + id-gNB-CU-UE-F1AP-ID, id-gNB-DU-UE-F1AP-ID, id-gNB-DU-ID, id-GNB-DU-Served-Cells-Item, id-gNB-DU-Served-Cells-List, id-gNB-CU-Name, id-gNB-DU-Name, + id-InactivityMonitoringRequest, + id-InactivityMonitoringResponse, id-oldgNB-DU-UE-F1AP-ID, id-Potential-SpCell-Item, id-Potential-SpCell-List, + id-RAT-FrequencyPriorityInformation, id-ResetType, id-ResourceCoordinationTransferContainer, id-RRCContainer, @@ -4298,7 +7331,9 @@ FROM F1AP-Containers id-Served-Cells-To-Delete-List, id-Served-Cells-To-Modify-Item, id-Served-Cells-To-Modify-List, + id-ServCellndex, id-SpCell-ID, + id-SpCellULConfigured, id-SRBID, id-SRBs-FailedToBeSetup-Item, id-SRBs-FailedToBeSetup-List, @@ -4317,6 +7352,58 @@ FROM F1AP-Containers id-TransmissionStopIndicator, id-UE-associatedLogicalF1-ConnectionItem, id-UE-associatedLogicalF1-ConnectionListResAck, + id-DUtoCURRCContainer, + id-NRCGI, + id-PagingCell-Item, + id-PagingCell-List, + id-PagingDRX, + id-PagingPriority, + id-SItype-List, + id-UEIdentityIndexValue, + id-GNB-CU-TNL-Association-Setup-List, + id-GNB-CU-TNL-Association-Setup-Item, + id-GNB-CU-TNL-Association-Failed-To-Setup-List, + id-GNB-CU-TNL-Association-Failed-To-Setup-Item, + id-GNB-CU-TNL-Association-To-Add-Item, + id-GNB-CU-TNL-Association-To-Add-List, + id-GNB-CU-TNL-Association-To-Remove-Item, + id-GNB-CU-TNL-Association-To-Remove-List, + id-GNB-CU-TNL-Association-To-Update-Item, + id-GNB-CU-TNL-Association-To-Update-List, + id-MaskedIMEISV, + id-PagingIdentity, + id-Cells-to-be-Barred-List, + id-Cells-to-be-Barred-Item, + id-PWSSystemInformation, + id-RepetitionPeriod, + id-NumberofBroadcastRequest, + id-Cells-To-Be-Broadcast-List, + id-Cells-To-Be-Broadcast-Item, + id-Cells-Broadcast-Completed-List, + id-Cells-Broadcast-Completed-Item, + id-Broadcast-To-Be-Cancelled-List, + id-Broadcast-To-Be-Cancelled-Item, + id-Cells-Broadcast-Cancelled-List, + id-Cells-Broadcast-Cancelled-Item, + id-NR-CGI-List-For-Restart-List, + id-NR-CGI-List-For-Restart-Item, + id-PWS-Failed-NR-CGI-List, + id-PWS-Failed-NR-CGI-Item, + id-EUTRA-NR-CellResourceCoordinationReq-Container, + id-EUTRA-NR-CellResourceCoordinationReqAck-Container, + id-Protected-EUTRA-Resources-List, + id-RequestType, + id-ServingPLMN, + id-DRXConfigurationIndicator, + id-RLCFailureIndication, + id-UplinkTxDirectCurrentListInformation, + id-SULAccessIndication, + id-Protected-EUTRA-Resources-Item, + id-GNB-DUConfigurationQuery, + id-GNB-DU-UE-AMBR-UL, + id-GNB-CU-RRC-Version, + id-GNB-DU-RRC-Version, + id-GNBDUOverloadInformation, maxCellingNBDU, maxnoofCandidateSpCells, maxnoofDRBs, @@ -4324,7 +7411,10 @@ FROM F1AP-Containers maxnoofIndividualF1ConnectionsToReset, maxnoofPotentialSpCells, maxnoofSCells, - maxnoofSRBs + maxnoofSRBs, + maxnoofPagingCells, + maxnoofTNLAssociations, + maxCellineNB FROM F1AP-Constants; @@ -4355,7 +7445,11 @@ ResetIEs F1AP-PROTOCOL-IES ::= { ResetType ::= CHOICE { f1-Interface ResetAll, - partOfF1-Interface UE-associatedLogicalF1-ConnectionListRes, + partOfF1-Interface UE-associatedLogicalF1-ConnectionListRes, + choice-extension ProtocolIE-SingleContainer { { ResetType-ExtIEs} } +} + +ResetType-ExtIEs F1AP-PROTOCOL-IES ::= { ... } @@ -4373,8 +7467,6 @@ UE-associatedLogicalF1-ConnectionItemRes F1AP-PROTOCOL-IES ::= { } - - -- ************************************************************** -- -- Reset Acknowledge @@ -4447,7 +7539,8 @@ F1SetupRequestIEs F1AP-PROTOCOL-IES ::= { { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| { ID id-gNB-DU-ID CRITICALITY reject TYPE GNB-DU-ID PRESENCE mandatory }| { ID id-gNB-DU-Name CRITICALITY ignore TYPE GNB-DU-Name PRESENCE optional }| - { ID id-gNB-DU-Served-Cells-List CRITICALITY reject TYPE GNB-DU-Served-Cells-List PRESENCE mandatory }, + { ID id-gNB-DU-Served-Cells-List CRITICALITY reject TYPE GNB-DU-Served-Cells-List PRESENCE optional }| + { ID id-GNB-DU-RRC-Version CRITICALITY reject TYPE RRC-Version PRESENCE mandatory }, ... } @@ -4475,7 +7568,8 @@ F1SetupResponse ::= SEQUENCE { F1SetupResponseIEs F1AP-PROTOCOL-IES ::= { { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| { ID id-gNB-CU-Name CRITICALITY ignore TYPE GNB-CU-Name PRESENCE optional }| - { ID id-Cells-to-be-Activated-List CRITICALITY reject TYPE Cells-to-be-Activated-List PRESENCE optional }, + { ID id-Cells-to-be-Activated-List CRITICALITY reject TYPE Cells-to-be-Activated-List PRESENCE optional }| + { ID id-GNB-CU-RRC-Version CRITICALITY reject TYPE RRC-Version PRESENCE mandatory }, ... } @@ -4531,13 +7625,13 @@ GNBDUConfigurationUpdateIEs F1AP-PROTOCOL-IES ::= { { ID id-Served-Cells-To-Add-List CRITICALITY reject TYPE Served-Cells-To-Add-List PRESENCE optional }| { ID id-Served-Cells-To-Modify-List CRITICALITY reject TYPE Served-Cells-To-Modify-List PRESENCE optional }| { ID id-Served-Cells-To-Delete-List CRITICALITY reject TYPE Served-Cells-To-Delete-List PRESENCE optional }| - { ID id-Active-Cells-List CRITICALITY reject TYPE Active-Cells-List PRESENCE optional }, + { ID id-Cells-Status-List CRITICALITY reject TYPE Cells-Status-List PRESENCE optional }, ... } Served-Cells-To-Add-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { Served-Cells-To-Add-ItemIEs } } Served-Cells-To-Modify-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { Served-Cells-To-Modify-ItemIEs } } Served-Cells-To-Delete-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { Served-Cells-To-Delete-ItemIEs } } -Active-Cells-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { Active-Cells-ItemIEs } } +Cells-Status-List ::= SEQUENCE (SIZE(0.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { Cells-Status-ItemIEs } } Served-Cells-To-Add-ItemIEs F1AP-PROTOCOL-IES ::= { { ID id-Served-Cells-To-Add-Item CRITICALITY reject TYPE Served-Cells-To-Add-Item PRESENCE mandatory }, @@ -4554,8 +7648,8 @@ Served-Cells-To-Delete-ItemIEs F1AP-PROTOCOL-IES ::= { ... } -Active-Cells-ItemIEs F1AP-PROTOCOL-IES ::= { - { ID id-Active-Cells-Item CRITICALITY reject TYPE Active-Cells-Item PRESENCE mandatory }, +Cells-Status-ItemIEs F1AP-PROTOCOL-IES ::= { + { ID id-Cells-Status-Item CRITICALITY reject TYPE Cells-Status-Item PRESENCE mandatory }, ... } @@ -4618,17 +7712,49 @@ GNBCUConfigurationUpdate ::= SEQUENCE { GNBCUConfigurationUpdateIEs F1AP-PROTOCOL-IES ::= { { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| { ID id-Cells-to-be-Activated-List CRITICALITY reject TYPE Cells-to-be-Activated-List PRESENCE optional }| - { ID id-Cells-to-be-Deactivated-List CRITICALITY reject TYPE Cells-to-be-Deactivated-List PRESENCE optional }, + { ID id-Cells-to-be-Deactivated-List CRITICALITY reject TYPE Cells-to-be-Deactivated-List PRESENCE optional }| + { ID id-GNB-CU-TNL-Association-To-Add-List CRITICALITY ignore TYPE GNB-CU-TNL-Association-To-Add-List PRESENCE optional }| + { ID id-GNB-CU-TNL-Association-To-Remove-List CRITICALITY ignore TYPE GNB-CU-TNL-Association-To-Remove-List PRESENCE optional }| + { ID id-GNB-CU-TNL-Association-To-Update-List CRITICALITY ignore TYPE GNB-CU-TNL-Association-To-Update-List PRESENCE optional }| + { ID id-Cells-to-be-Barred-List CRITICALITY ignore TYPE Cells-to-be-Barred-List PRESENCE optional }| + { ID id-Protected-EUTRA-Resources-List CRITICALITY reject TYPE Protected-EUTRA-Resources-List PRESENCE optional }, ... } Cells-to-be-Deactivated-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { Cells-to-be-Deactivated-List-ItemIEs } } +GNB-CU-TNL-Association-To-Add-List ::= SEQUENCE (SIZE(1.. maxnoofTNLAssociations)) OF ProtocolIE-SingleContainer { { GNB-CU-TNL-Association-To-Add-ItemIEs } } +GNB-CU-TNL-Association-To-Remove-List ::= SEQUENCE (SIZE(1.. maxnoofTNLAssociations)) OF ProtocolIE-SingleContainer { { GNB-CU-TNL-Association-To-Remove-ItemIEs } } +GNB-CU-TNL-Association-To-Update-List ::= SEQUENCE (SIZE(1.. maxnoofTNLAssociations)) OF ProtocolIE-SingleContainer { { GNB-CU-TNL-Association-To-Update-ItemIEs } } +Cells-to-be-Barred-List ::= SEQUENCE(SIZE(1.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { Cells-to-be-Barred-ItemIEs } } + Cells-to-be-Deactivated-List-ItemIEs F1AP-PROTOCOL-IES ::= { { ID id-Cells-to-be-Deactivated-List-Item CRITICALITY reject TYPE Cells-to-be-Deactivated-List-Item PRESENCE mandatory }, ...} +GNB-CU-TNL-Association-To-Add-ItemIEs F1AP-PROTOCOL-IES ::= { + { ID id-GNB-CU-TNL-Association-To-Add-Item CRITICALITY ignore TYPE GNB-CU-TNL-Association-To-Add-Item PRESENCE mandatory }, +...} + +GNB-CU-TNL-Association-To-Remove-ItemIEs F1AP-PROTOCOL-IES ::= { + { ID id-GNB-CU-TNL-Association-To-Remove-Item CRITICALITY ignore TYPE GNB-CU-TNL-Association-To-Remove-Item PRESENCE mandatory }, +...} + +GNB-CU-TNL-Association-To-Update-ItemIEs F1AP-PROTOCOL-IES ::= { + { ID id-GNB-CU-TNL-Association-To-Update-Item CRITICALITY ignore TYPE GNB-CU-TNL-Association-To-Update-Item PRESENCE mandatory }, +...} + +Cells-to-be-Barred-ItemIEs F1AP-PROTOCOL-IES ::= { + { ID id-Cells-to-be-Barred-Item CRITICALITY ignore TYPE Cells-to-be-Barred-Item PRESENCE mandatory }, + ... +} + +Protected-EUTRA-Resources-List ::= SEQUENCE (SIZE(1.. maxCellineNB)) OF ProtocolIE-SingleContainer { { Protected-EUTRA-Resources-ItemIEs } } +Protected-EUTRA-Resources-ItemIEs F1AP-PROTOCOL-IES ::= { + { ID id-Protected-EUTRA-Resources-Item CRITICALITY reject TYPE Protected-EUTRA-Resources-Item PRESENCE mandatory}, + ...} + -- ************************************************************** -- -- GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE @@ -4644,17 +7770,30 @@ GNBCUConfigurationUpdateAcknowledge ::= SEQUENCE { GNBCUConfigurationUpdateAcknowledgeIEs F1AP-PROTOCOL-IES ::= { { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| { ID id-Cells-Failed-to-be-Activated-List CRITICALITY reject TYPE Cells-Failed-to-be-Activated-List PRESENCE optional}| - { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }| + { ID id-GNB-CU-TNL-Association-Setup-List CRITICALITY ignore TYPE GNB-CU-TNL-Association-Setup-List PRESENCE optional }| + { ID id-GNB-CU-TNL-Association-Failed-To-Setup-List CRITICALITY ignore TYPE GNB-CU-TNL-Association-Failed-To-Setup-List PRESENCE optional }, ... } Cells-Failed-to-be-Activated-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { Cells-Failed-to-be-Activated-List-ItemIEs } } +GNB-CU-TNL-Association-Setup-List ::= SEQUENCE (SIZE(1.. maxnoofTNLAssociations)) OF ProtocolIE-SingleContainer { { GNB-CU-TNL-Association-Setup-ItemIEs } } +GNB-CU-TNL-Association-Failed-To-Setup-List ::= SEQUENCE (SIZE(1.. maxnoofTNLAssociations)) OF ProtocolIE-SingleContainer { { GNB-CU-TNL-Association-Failed-To-Setup-ItemIEs } } Cells-Failed-to-be-Activated-List-ItemIEs F1AP-PROTOCOL-IES ::= { { ID id-Cells-Failed-to-be-Activated-List-Item CRITICALITY reject TYPE Cells-Failed-to-be-Activated-List-Item PRESENCE mandatory }, ... } +GNB-CU-TNL-Association-Setup-ItemIEs F1AP-PROTOCOL-IES ::= { + { ID id-GNB-CU-TNL-Association-Setup-Item CRITICALITY ignore TYPE GNB-CU-TNL-Association-Setup-Item PRESENCE mandatory }, +...} + + +GNB-CU-TNL-Association-Failed-To-Setup-ItemIEs F1AP-PROTOCOL-IES ::= { + { ID id-GNB-CU-TNL-Association-Failed-To-Setup-Item CRITICALITY ignore TYPE GNB-CU-TNL-Association-Failed-To-Setup-Item PRESENCE mandatory }, +...} + -- ************************************************************** -- @@ -4675,6 +7814,43 @@ GNBCUConfigurationUpdateFailureIEs F1AP-PROTOCOL-IES ::= { ... } + +-- ************************************************************** +-- +-- GNB-DU RESOURCE COORDINATION REQUEST +-- +-- ************************************************************** + +GNBDUResourceCoordinationRequest ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{GNBDUResourceCoordinationRequest-IEs}}, + ... +} + +GNBDUResourceCoordinationRequest-IEs F1AP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-RequestType CRITICALITY reject TYPE RequestType PRESENCE mandatory }| + { ID id-EUTRA-NR-CellResourceCoordinationReq-Container CRITICALITY reject TYPE EUTRA-NR-CellResourceCoordinationReq-Container PRESENCE mandatory}, + ... +} + + +-- ************************************************************** +-- +-- GNB-DU RESOURCE COORDINATION RESPONSE +-- +-- ************************************************************** + +GNBDUResourceCoordinationResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{GNBDUResourceCoordinationResponse-IEs}}, + ... +} + +GNBDUResourceCoordinationResponse-IEs F1AP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-EUTRA-NR-CellResourceCoordinationReqAck-Container CRITICALITY reject TYPE EUTRA-NR-CellResourceCoordinationReqAck-Container PRESENCE mandatory}, + ... +} + -- ************************************************************** -- -- UE Context Setup ELEMENTARY PROCEDURE @@ -4696,13 +7872,21 @@ UEContextSetupRequestIEs F1AP-PROTOCOL-IES ::= { { ID id-gNB-CU-UE-F1AP-ID CRITICALITY reject TYPE GNB-CU-UE-F1AP-ID PRESENCE mandatory }| { ID id-gNB-DU-UE-F1AP-ID CRITICALITY ignore TYPE GNB-DU-UE-F1AP-ID PRESENCE optional }| { ID id-SpCell-ID CRITICALITY reject TYPE NRCGI PRESENCE mandatory }| + { ID id-ServCellndex CRITICALITY reject TYPE ServCellIndex PRESENCE mandatory }| + { ID id-SpCellULConfigured CRITICALITY ignore TYPE CellULConfigured PRESENCE optional }| { ID id-CUtoDURRCInformation CRITICALITY reject TYPE CUtoDURRCInformation PRESENCE mandatory}| { ID id-Candidate-SpCell-List CRITICALITY ignore TYPE Candidate-SpCell-List PRESENCE optional }| { ID id-DRXCycle CRITICALITY ignore TYPE DRXCycle PRESENCE optional }| { ID id-ResourceCoordinationTransferContainer CRITICALITY ignore TYPE ResourceCoordinationTransferContainer PRESENCE optional }| { ID id-SCell-ToBeSetup-List CRITICALITY ignore TYPE SCell-ToBeSetup-List PRESENCE optional }| { ID id-SRBs-ToBeSetup-List CRITICALITY reject TYPE SRBs-ToBeSetup-List PRESENCE optional }| - { ID id-DRBs-ToBeSetup-List CRITICALITY reject TYPE DRBs-ToBeSetup-List PRESENCE mandatory }, + { ID id-DRBs-ToBeSetup-List CRITICALITY reject TYPE DRBs-ToBeSetup-List PRESENCE optional }| + { ID id-InactivityMonitoringRequest CRITICALITY reject TYPE InactivityMonitoringRequest PRESENCE optional }| + { ID id-RAT-FrequencyPriorityInformation CRITICALITY reject TYPE RAT-FrequencyPriorityInformation PRESENCE optional }| + { ID id-RRCContainer CRITICALITY ignore TYPE RRCContainer PRESENCE optional }| + { ID id-MaskedIMEISV CRITICALITY ignore TYPE MaskedIMEISV PRESENCE optional }| + { ID id-ServingPLMN CRITICALITY ignore TYPE PLMN-Identity PRESENCE optional }| + { ID id-GNB-DU-UE-AMBR-UL CRITICALITY ignore TYPE BitRate PRESENCE mandatory }, ... } @@ -4751,11 +7935,14 @@ UEContextSetupResponseIEs F1AP-PROTOCOL-IES ::= { { ID id-gNB-CU-UE-F1AP-ID CRITICALITY reject TYPE GNB-CU-UE-F1AP-ID PRESENCE mandatory }| { ID id-gNB-DU-UE-F1AP-ID CRITICALITY reject TYPE GNB-DU-UE-F1AP-ID PRESENCE mandatory }| { ID id-DUtoCURRCInformation CRITICALITY reject TYPE DUtoCURRCInformation PRESENCE mandatory }| + { ID id-C-RNTI CRITICALITY ignore TYPE C-RNTI PRESENCE optional }| { ID id-ResourceCoordinationTransferContainer CRITICALITY ignore TYPE ResourceCoordinationTransferContainer PRESENCE optional }| - { ID id-DRBs-Setup-List CRITICALITY ignore TYPE DRBs-Setup-List PRESENCE mandatory}| + { ID id-FullConfiguration CRITICALITY reject TYPE FullConfiguration PRESENCE optional }| + { ID id-DRBs-Setup-List CRITICALITY ignore TYPE DRBs-Setup-List PRESENCE optional }| { ID id-SRBs-FailedToBeSetup-List CRITICALITY ignore TYPE SRBs-FailedToBeSetup-List PRESENCE optional }| { ID id-DRBs-FailedToBeSetup-List CRITICALITY ignore TYPE DRBs-FailedToBeSetup-List PRESENCE optional }| { ID id-SCell-FailedtoSetup-List CRITICALITY ignore TYPE SCell-FailedtoSetup-List PRESENCE optional }| + { ID id-InactivityMonitoringResponse CRITICALITY reject TYPE InactivityMonitoringResponse PRESENCE optional }| { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, ... } @@ -4858,7 +8045,11 @@ UEContextReleaseCommand ::= SEQUENCE { UEContextReleaseCommandIEs F1AP-PROTOCOL-IES ::= { { ID id-gNB-CU-UE-F1AP-ID CRITICALITY reject TYPE GNB-CU-UE-F1AP-ID PRESENCE mandatory }| { ID id-gNB-DU-UE-F1AP-ID CRITICALITY reject TYPE GNB-DU-UE-F1AP-ID PRESENCE mandatory }| - { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }, + { ID id-Cause CRITICALITY ignore TYPE Cause PRESENCE mandatory }| + { ID id-RRCContainer CRITICALITY ignore TYPE RRCContainer PRESENCE optional }| + { ID id-SRBID CRITICALITY ignore TYPE SRBID PRESENCE optional }| + { ID id-oldgNB-DU-UE-F1AP-ID CRITICALITY ignore TYPE GNB-DU-UE-F1AP-ID PRESENCE optional }| + { ID id-ExecuteDuplication CRITICALITY ignore TYPE ExecuteDuplication PRESENCE optional}, ... } @@ -4901,6 +8092,8 @@ UEContextModificationRequestIEs F1AP-PROTOCOL-IES ::= { { ID id-gNB-CU-UE-F1AP-ID CRITICALITY reject TYPE GNB-CU-UE-F1AP-ID PRESENCE mandatory }| { ID id-gNB-DU-UE-F1AP-ID CRITICALITY reject TYPE GNB-DU-UE-F1AP-ID PRESENCE mandatory }| { ID id-SpCell-ID CRITICALITY ignore TYPE NRCGI PRESENCE optional }| + { ID id-ServCellndex CRITICALITY reject TYPE ServCellIndex PRESENCE optional }| + { ID id-SpCellULConfigured CRITICALITY ignore TYPE CellULConfigured PRESENCE optional }| { ID id-DRXCycle CRITICALITY ignore TYPE DRXCycle PRESENCE optional }| { ID id-CUtoDURRCInformation CRITICALITY reject TYPE CUtoDURRCInformation PRESENCE optional }| { ID id-TransmissionStopIndicator CRITICALITY ignore TYPE TransmissionStopIndicator PRESENCE optional }| @@ -4913,7 +8106,15 @@ UEContextModificationRequestIEs F1AP-PROTOCOL-IES ::= { { ID id-DRBs-ToBeSetupMod-List CRITICALITY reject TYPE DRBs-ToBeSetupMod-List PRESENCE optional }| { ID id-DRBs-ToBeModified-List CRITICALITY reject TYPE DRBs-ToBeModified-List PRESENCE optional }| { ID id-SRBs-ToBeReleased-List CRITICALITY reject TYPE SRBs-ToBeReleased-List PRESENCE optional }| - { ID id-DRBs-ToBeReleased-List CRITICALITY reject TYPE DRBs-ToBeReleased-List PRESENCE optional }, + { ID id-DRBs-ToBeReleased-List CRITICALITY reject TYPE DRBs-ToBeReleased-List PRESENCE optional }| + { ID id-InactivityMonitoringRequest CRITICALITY reject TYPE InactivityMonitoringRequest PRESENCE optional }| + { ID id-RAT-FrequencyPriorityInformation CRITICALITY reject TYPE RAT-FrequencyPriorityInformation PRESENCE optional }| + { ID id-DRXConfigurationIndicator CRITICALITY ignore TYPE DRXConfigurationIndicator PRESENCE optional }| + { ID id-RLCFailureIndication CRITICALITY ignore TYPE RLCFailureIndication PRESENCE optional }| + { ID id-UplinkTxDirectCurrentListInformation CRITICALITY ignore TYPE UplinkTxDirectCurrentListInformation PRESENCE optional }| + { ID id-GNB-DUConfigurationQuery CRITICALITY reject TYPE GNB-DUConfigurationQuery PRESENCE optional }| + { ID id-GNB-DU-UE-AMBR-UL CRITICALITY ignore TYPE BitRate PRESENCE optional }| + { ID id-ExecuteDuplication CRITICALITY ignore TYPE ExecuteDuplication PRESENCE optional}, ... } @@ -4987,7 +8188,9 @@ UEContextModificationResponseIEs F1AP-PROTOCOL-IES ::= { { ID id-DRBs-FailedToBeSetupMod-List CRITICALITY ignore TYPE DRBs-FailedToBeSetupMod-List PRESENCE optional }| { ID id-SCell-FailedtoSetupMod-List CRITICALITY ignore TYPE SCell-FailedtoSetupMod-List PRESENCE optional }| { ID id-DRBs-FailedToBeModified-List CRITICALITY ignore TYPE DRBs-FailedToBeModified-List PRESENCE optional }| - { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + { ID id-InactivityMonitoringResponse CRITICALITY reject TYPE InactivityMonitoringResponse PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }| + { ID id-C-RNTI CRITICALITY ignore TYPE C-RNTI PRESENCE optional }, ... } @@ -5119,24 +8322,190 @@ UEContextModificationConfirmIEs F1AP-PROTOCOL-IES ::= { { ID id-gNB-DU-UE-F1AP-ID CRITICALITY reject TYPE GNB-DU-UE-F1AP-ID PRESENCE mandatory }| { ID id-ResourceCoordinationTransferContainer CRITICALITY ignore TYPE ResourceCoordinationTransferContainer PRESENCE optional }| { ID id-DRBs-ModifiedConf-List CRITICALITY ignore TYPE DRBs-ModifiedConf-List PRESENCE optional}| - { ID id-DRBs-FailedToBeModifiedConf-List CRITICALITY ignore TYPE DRBs-FailedToBeModifiedConf-List PRESENCE optional }| - { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, + { ID id-RRCContainer CRITICALITY ignore TYPE RRCContainer PRESENCE optional }| + { ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }| + { ID id-ExecuteDuplication CRITICALITY ignore TYPE ExecuteDuplication PRESENCE optional}, ... } DRBs-ModifiedConf-List::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF ProtocolIE-SingleContainer { { DRBs-ModifiedConf-ItemIEs } } -DRBs-FailedToBeModifiedConf-List ::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF ProtocolIE-SingleContainer { { DRBs-FailedToBeModifiedConf-ItemIEs} } DRBs-ModifiedConf-ItemIEs F1AP-PROTOCOL-IES ::= { { ID id-DRBs-ModifiedConf-Item CRITICALITY ignore TYPE DRBs-ModifiedConf-Item PRESENCE mandatory}, ... } -DRBs-FailedToBeModifiedConf-ItemIEs F1AP-PROTOCOL-IES ::= { - { ID id-DRBs-FailedToBeModifiedConf-Item CRITICALITY ignore TYPE DRBs-FailedToBeModifiedConf-Item PRESENCE mandatory}, + + +-- ************************************************************** +-- +-- WRITE-REPLACE WARNING ELEMENTARY PROCEDURE +-- +-- ************************************************************** + +-- ************************************************************** +-- +-- Write-Replace Warning Request +-- +-- ************************************************************** + +WriteReplaceWarningRequest ::= SEQUENCE { +protocolIEs ProtocolIE-Container { {WriteReplaceWarningRequestIEs} }, +... +} +WriteReplaceWarningRequestIEs F1AP-PROTOCOL-IES ::= { +{ ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| +{ ID id-PWSSystemInformation CRITICALITY reject TYPE PWSSystemInformation PRESENCE mandatory }| +{ ID id-RepetitionPeriod CRITICALITY reject TYPE RepetitionPeriod PRESENCE mandatory }| +{ ID id-NumberofBroadcastRequest CRITICALITY reject TYPE NumberofBroadcastRequest PRESENCE mandatory }| +{ ID id-Cells-To-Be-Broadcast-List CRITICALITY reject TYPE Cells-To-Be-Broadcast-List PRESENCE optional }, +... +} +Cells-To-Be-Broadcast-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { Cells-To-Be-Broadcast-List-ItemIEs } } + +Cells-To-Be-Broadcast-List-ItemIEs F1AP-PROTOCOL-IES ::= { + { ID id-Cells-To-Be-Broadcast-Item CRITICALITY reject TYPE Cells-To-Be-Broadcast-Item PRESENCE mandatory }, ... } +-- ************************************************************** +-- +-- Write-Replace Warning Response +-- +-- ************************************************************** + +WriteReplaceWarningResponse ::= SEQUENCE { +protocolIEs ProtocolIE-Container { {WriteReplaceWarningResponseIEs} }, +... +} +WriteReplaceWarningResponseIEs F1AP-PROTOCOL-IES ::= { +{ ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| +{ ID id-Cells-Broadcast-Completed-List CRITICALITY reject TYPE Cells-Broadcast-Completed-List PRESENCE optional }| +{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, +... +} +Cells-Broadcast-Completed-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { Cells-Broadcast-Completed-List-ItemIEs } } + +Cells-Broadcast-Completed-List-ItemIEs F1AP-PROTOCOL-IES ::= { + { ID id-Cells-Broadcast-Completed-Item CRITICALITY reject TYPE Cells-Broadcast-Completed-Item PRESENCE mandatory }, + ... +} + + +-- ************************************************************** +-- +-- PWS CANCEL ELEMENTARY PROCEDURE +-- +-- ************************************************************** + +-- ************************************************************** +-- +-- PWS Cancel Request +-- +-- ************************************************************** + +PWSCancelRequest ::= SEQUENCE { +protocolIEs ProtocolIE-Container { {PWSCancelRequestIEs} }, +... +} +PWSCancelRequestIEs F1AP-PROTOCOL-IES ::= { +{ ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| +{ ID id-NumberofBroadcastRequest CRITICALITY reject TYPE NumberofBroadcastRequest PRESENCE mandatory }| +{ ID id-Broadcast-To-Be-Cancelled-List CRITICALITY reject TYPE Broadcast-To-Be-Cancelled-List PRESENCE optional }| +{ ID id-Cancel-all-Warning-Messages-Indicator CRITICALITY reject TYPE Cancel-all-Warning-Messages-Indicator PRESENCE optional } +, +... +} +Broadcast-To-Be-Cancelled-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { Broadcast-To-Be-Cancelled-List-ItemIEs } } + +Broadcast-To-Be-Cancelled-List-ItemIEs F1AP-PROTOCOL-IES ::= { + { ID id-Broadcast-To-Be-Cancelled-Item CRITICALITY reject TYPE Broadcast-To-Be-Cancelled-Item PRESENCE mandatory }, + ... +} + +-- ************************************************************** +-- +-- PWS Cancel Response +-- +-- ************************************************************** + +PWSCancelResponse ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {PWSCancelResponseIEs} }, +... +} + +PWSCancelResponseIEs F1AP-PROTOCOL-IES ::= { +{ ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| +{ ID id-Cells-Broadcast-Cancelled-List CRITICALITY reject TYPE Cells-Broadcast-Cancelled-List PRESENCE optional }| +{ ID id-CriticalityDiagnostics CRITICALITY ignore TYPE CriticalityDiagnostics PRESENCE optional }, +... +} +Cells-Broadcast-Cancelled-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { Cells-Broadcast-Cancelled-List-ItemIEs } } + +Cells-Broadcast-Cancelled-List-ItemIEs F1AP-PROTOCOL-IES ::= { + { ID id-Cells-Broadcast-Cancelled-Item CRITICALITY reject TYPE Cells-Broadcast-Cancelled-Item PRESENCE mandatory }, + ... +} + +-- ************************************************************** +-- +-- UE Inactivity Notification ELEMENTARY PROCEDURE +-- +-- ************************************************************** + +-- ************************************************************** +-- +-- UE Inactivity Notification +-- +-- ************************************************************** + +UEInactivityNotification ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ UEInactivityNotificationIEs}}, + ... +} + +UEInactivityNotificationIEs F1AP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-F1AP-ID CRITICALITY reject TYPE GNB-CU-UE-F1AP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-F1AP-ID CRITICALITY reject TYPE GNB-DU-UE-F1AP-ID PRESENCE mandatory }| + { ID id-DRB-Activity-List CRITICALITY reject TYPE DRB-Activity-List PRESENCE mandatory } , + ... +} + +DRB-Activity-List::= SEQUENCE (SIZE(1..maxnoofDRBs)) OF ProtocolIE-SingleContainer { { DRB-Activity-ItemIEs } } + +DRB-Activity-ItemIEs F1AP-PROTOCOL-IES ::= { + { ID id-DRB-Activity-Item CRITICALITY reject TYPE DRB-Activity-Item PRESENCE mandatory}, + ... +} + +-- ************************************************************** +-- +-- Initial UL RRC Message Transfer ELEMENTARY PROCEDURE +-- +-- ************************************************************** + +-- ************************************************************** +-- +-- INITIAL UL RRC Message Transfer +-- +-- ************************************************************** + +InitialULRRCMessageTransfer ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ InitialULRRCMessageTransferIEs}}, + ... +} + +InitialULRRCMessageTransferIEs F1AP-PROTOCOL-IES ::= { + { ID id-gNB-DU-UE-F1AP-ID CRITICALITY reject TYPE GNB-DU-UE-F1AP-ID PRESENCE mandatory }| + { ID id-NRCGI CRITICALITY reject TYPE NRCGI PRESENCE mandatory }| + { ID id-C-RNTI CRITICALITY reject TYPE C-RNTI PRESENCE mandatory }| + { ID id-RRCContainer CRITICALITY reject TYPE RRCContainer PRESENCE mandatory }| + { ID id-DUtoCURRCContainer CRITICALITY reject TYPE DUtoCURRCContainer PRESENCE optional }| + { ID id-SULAccessIndication CRITICALITY ignore TYPE SULAccessIndication PRESENCE optional }, + ... +} + + -- ************************************************************** -- -- DL RRC Message Transfer ELEMENTARY PROCEDURE @@ -5159,7 +8528,9 @@ DLRRCMessageTransferIEs F1AP-PROTOCOL-IES ::= { { ID id-gNB-DU-UE-F1AP-ID CRITICALITY reject TYPE GNB-DU-UE-F1AP-ID PRESENCE mandatory }| { ID id-oldgNB-DU-UE-F1AP-ID CRITICALITY reject TYPE GNB-DU-UE-F1AP-ID PRESENCE optional }| { ID id-SRBID CRITICALITY reject TYPE SRBID PRESENCE mandatory }| - { ID id-RRCContainer CRITICALITY reject TYPE RRCContainer PRESENCE mandatory }, + { ID id-ExecuteDuplication CRITICALITY ignore TYPE ExecuteDuplication PRESENCE optional}| + { ID id-RRCContainer CRITICALITY reject TYPE RRCContainer PRESENCE mandatory }| + { ID id-RAT-FrequencyPriorityInformation CRITICALITY reject TYPE RAT-FrequencyPriorityInformation PRESENCE optional }, ... } -- ************************************************************** @@ -5202,6 +8573,172 @@ PrivateMessage-IEs F1AP-PRIVATE-IES ::= { ... } + +-- ************************************************************** +-- +-- System Information ELEMENTARY PROCEDURE +-- +-- ************************************************************** + +-- ************************************************************** +-- +-- System information Delivery Command +-- +-- ************************************************************** + +SystemInformationDeliveryCommand ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ SystemInformationDeliveryCommandIEs}}, + ... +} + +SystemInformationDeliveryCommandIEs F1AP-PROTOCOL-IES ::= { + { ID id-NRCGI CRITICALITY reject TYPE NRCGI PRESENCE mandatory }| + { ID id-SItype-List CRITICALITY reject TYPE SItype-List PRESENCE mandatory }| + { ID id-ConfirmedUEID CRITICALITY reject TYPE GNB-DU-UE-F1AP-ID PRESENCE mandatory }, + ... +} + + +-- ************************************************************** +-- +-- Paging PROCEDURE +-- +-- ************************************************************** + +-- ************************************************************** +-- +-- Paging +-- +-- ************************************************************** + +Paging ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ PagingIEs}}, + ... +} + +PagingIEs F1AP-PROTOCOL-IES ::= { + { ID id-UEIdentityIndexValue CRITICALITY reject TYPE UEIdentityIndexValue PRESENCE mandatory }| + { ID id-PagingIdentity CRITICALITY reject TYPE PagingIdentity PRESENCE optional }| + { ID id-PagingDRX CRITICALITY ignore TYPE PagingDRX PRESENCE optional }| + { ID id-PagingPriority CRITICALITY ignore TYPE PagingPriority PRESENCE optional }| + { ID id-PagingCell-List CRITICALITY ignore TYPE PagingCell-list PRESENCE optional }, + ... +} + +PagingCell-list::= SEQUENCE (SIZE(1.. maxnoofPagingCells)) OF ProtocolIE-SingleContainer { { PagingCell-ItemIEs } } + +PagingCell-ItemIEs F1AP-PROTOCOL-IES ::= { + { ID id-PagingCell-Item CRITICALITY ignore TYPE PagingCell-Item PRESENCE mandatory} , + ... +} + + + +-- ************************************************************** +-- +-- Notify +-- +-- ************************************************************** + +Notify ::= SEQUENCE { + protocolIEs ProtocolIE-Container {{ NotifyIEs}}, + ... +} + +NotifyIEs F1AP-PROTOCOL-IES ::= { + { ID id-gNB-CU-UE-F1AP-ID CRITICALITY reject TYPE GNB-CU-UE-F1AP-ID PRESENCE mandatory }| + { ID id-gNB-DU-UE-F1AP-ID CRITICALITY reject TYPE GNB-DU-UE-F1AP-ID PRESENCE mandatory }| + { ID id-DRB-Notify-List CRITICALITY reject TYPE DRB-Notify-List PRESENCE mandatory }, + ... +} + +DRB-Notify-List::= SEQUENCE (SIZE(1)) OF ProtocolIE-SingleContainer { { DRB-Notify-ItemIEs } } + +DRB-Notify-ItemIEs F1AP-PROTOCOL-IES ::= { + { ID id-DRB-Notify-Item CRITICALITY reject TYPE DRB-Notify-Item PRESENCE mandatory}, + ... +} + + + +-- ************************************************************** +-- +-- PWS RESTART INDICATION ELEMENTARY PROCEDURE +-- +-- ************************************************************** + +-- ************************************************************** +-- +-- PWS Restart Indication +-- +-- ************************************************************** + +PWSRestartIndication ::= SEQUENCE { +protocolIEs ProtocolIE-Container { { PWSRestartIndicationIEs} }, +... +} +PWSRestartIndicationIEs F1AP-PROTOCOL-IES ::= { +{ ID id-NR-CGI-List-For-Restart-List CRITICALITY reject TYPE NR-CGI-List-For-Restart-List PRESENCE optional }, +... +} +NR-CGI-List-For-Restart-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { NR-CGI-List-For-Restart-List-ItemIEs } } + +NR-CGI-List-For-Restart-List-ItemIEs F1AP-PROTOCOL-IES ::= { + { ID id-NR-CGI-List-For-Restart-Item CRITICALITY reject TYPE NR-CGI-List-For-Restart-Item PRESENCE mandatory }, + ... +} + +-- ************************************************************** +-- +-- PWS FAILURE INDICATION ELEMENTARY PROCEDURE +-- +-- ************************************************************** + +-- ************************************************************** +-- +-- PWS Failure Indication +-- +-- ************************************************************** + +PWSFailureIndication ::= SEQUENCE { +protocolIEs ProtocolIE-Container { { PWSFailureIndicationIEs} }, +... +} +PWSFailureIndicationIEs F1AP-PROTOCOL-IES ::= { +{ ID id-PWS-Failed-NR-CGI-List CRITICALITY reject TYPE PWS-Failed-NR-CGI-List PRESENCE optional }, +... +} +PWS-Failed-NR-CGI-List ::= SEQUENCE (SIZE(1.. maxCellingNBDU)) OF ProtocolIE-SingleContainer { { PWS-Failed-NR-CGI-List-ItemIEs } } + +PWS-Failed-NR-CGI-List-ItemIEs F1AP-PROTOCOL-IES ::= { + { ID id-PWS-Failed-NR-CGI-Item CRITICALITY reject TYPE PWS-Failed-NR-CGI-Item PRESENCE mandatory }, + ... +} + + +-- ************************************************************** +-- +-- gNB-DU STATUS INDICATION ELEMENTARY PROCEDURE +-- +-- ************************************************************** + +-- ************************************************************** +-- +-- gNB-DU Status Indication +-- +-- ************************************************************** + +GNBDUStatusIndication ::= SEQUENCE { + protocolIEs ProtocolIE-Container { {GNBDUStatusIndicationIEs} }, + ... +} + +GNBDUStatusIndicationIEs F1AP-PROTOCOL-IES ::= { + { ID id-TransactionID CRITICALITY reject TYPE TransactionID PRESENCE mandatory }| + { ID id-GNBDUOverloadInformation CRITICALITY reject TYPE GNBDUOverloadInformation PRESENCE mandatory }, + ... +} + END 9.4.5 Information Element Definitions @@ -5220,11 +8757,31 @@ DEFINITIONS AUTOMATIC TAGS ::= BEGIN IMPORTS + id-gNB-CUSystemInformation, + id-HandoverPreparationInformation, + id-TAISliceSupportList, + id-RANAC, + id-CellGroupConfig, + id-AvailablePLMNList, + id-PDUSessionID, + id-ULPDUSessionAggregateMaximumBitRate, + id-DC-Based-Duplication-Configured, + id-DC-Based-Duplication-Activation, + id-PDCPSNLength, + id-RLC-Status, + id-MeasurementTimingConfiguration, + id-DRB-Information, maxNRARFCN, maxnoofErrors, maxnoofBPLMNs, - maxnoofDLTunnels, - maxnoofULTunnels + maxnoofDLUPTNLInformation, + maxnoofNrCellBands, + maxnoofULUPTNLInformation, + maxnoofQoSFlows, + maxnoofSliceItems, + maxnoofSIBTypes, + maxnoofSITypes, + maxCellineNB FROM F1AP-Constants @@ -5244,17 +8801,6 @@ FROM F1AP-Containers; -- A -Active-Cells-Item ::= SEQUENCE { - nRCGI NRCGI , - iE-Extensions ProtocolExtensionContainer { { Active-Cells-ItemExtIEs } } OPTIONAL, - ... -} - -Active-Cells-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { - ... -} - - AllocationAndRetentionPriority ::= SEQUENCE { priorityLevel PriorityLevel, pre-emptionCapability Pre-emptionCapability, @@ -5266,14 +8812,42 @@ AllocationAndRetentionPriority ::= SEQUENCE { AllocationAndRetentionPriority-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { ... } + +AvailablePLMNList ::= SEQUENCE (SIZE(1..maxnoofBPLMNs)) OF AvailablePLMNList-Item + +AvailablePLMNList-Item ::= SEQUENCE { + pLMNIdentity PLMN-Identity, + iE-Extensions ProtocolExtensionContainer { { AvailablePLMNList-Item-ExtIEs} } OPTIONAL +} + +AvailablePLMNList-Item-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +AveragingWindow ::= INTEGER (0..4095, ...) + -- B BitRate ::= INTEGER (0..4000000000000,...) -BroadcastPLMNs-Item ::= SEQUENCE (SIZE(1..maxnoofBPLMNs)) OF PLMN-Identity +BroadcastPLMNs-List ::= SEQUENCE (SIZE(1..maxnoofBPLMNs)) OF BroadcastPLMNs-Item + +BroadcastPLMNs-Item ::= SEQUENCE { + pLMN-Identity PLMN-Identity, + iE-Extensions ProtocolExtensionContainer { { BroadcastPLMNs-ItemExtIEs} } OPTIONAL, + ... +} + +BroadcastPLMNs-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { +{ ID id-TAISliceSupportList CRITICALITY ignore EXTENSION SliceSupportList PRESENCE optional }, + ... +} + -- C +Cancel-all-Warning-Messages-Indicator ::= ENUMERATED {true, ...} + Candidate-SpCell-Item ::= SEQUENCE { candidate-SpCell-ID NRCGI , iE-Extensions ProtocolExtensionContainer { { Candidate-SpCell-ItemExtIEs } } OPTIONAL, @@ -5289,6 +8863,10 @@ Cause ::= CHOICE { transport CauseTransport, protocol CauseProtocol, misc CauseMisc, + choice-extension ProtocolIE-SingleContainer { { Cause-ExtIEs} } +} + +Cause-ExtIEs F1AP-PROTOCOL-IES ::= { ... } @@ -5314,7 +8892,7 @@ CauseProtocol ::= ENUMERATED { CauseRadioNetwork ::= ENUMERATED { unspecified, - rlc-failure, + rl-failure-rlc, unknown-or-already-allocated-gnb-cu-ue-f1ap-id, unknown-or-already-allocated-gnd-du-ue-f1ap-id, unknown-or-inconsistent-pair-of-ue-f1ap-id, @@ -5324,7 +8902,11 @@ CauseRadioNetwork ::= ENUMERATED { no-radio-resources-available, procedure-cancelled, normal-release, - ... + ..., + cell-not-available, + rl-failure-others, + ue-rejection, + resources-not-available-for-the-slice } CauseTransport ::= ENUMERATED { @@ -5333,10 +8915,25 @@ CauseTransport ::= ENUMERATED { ... } - - CellGroupConfig ::= OCTET STRING +Cell-State ::= ENUMERATED { + active, + inactive, + ... +} + +Cell-Status ::= SEQUENCE { + cell-state Cell-State, + switchingOffOngoing ENUMERATED {true, ...} OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Cell-Status-ExtIEs } } OPTIONAL, + ... +} + +Cell-Status-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + Cells-Failed-to-be-Activated-List-Item ::= SEQUENCE { nRCGI NRCGI, cause Cause, @@ -5348,6 +8945,59 @@ Cells-Failed-to-be-Activated-List-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { ... } +Cells-Status-Item ::= SEQUENCE { + nRCGI NRCGI, + cell-status Cell-Status, + iE-Extensions ProtocolExtensionContainer { { Cells-Status-ItemExtIEs } } OPTIONAL, + ... +} + +Cells-Status-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +Cells-To-Be-Broadcast-Item ::= SEQUENCE { + nRCGI NRCGI, + iE-Extensions ProtocolExtensionContainer { { Cells-To-Be-Broadcast-ItemExtIEs } } OPTIONAL, + ... +} + +Cells-To-Be-Broadcast-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +Cells-Broadcast-Completed-Item ::= SEQUENCE { + nRCGI NRCGI, + iE-Extensions ProtocolExtensionContainer { { Cells-Broadcast-Completed-ItemExtIEs } } OPTIONAL, + ... +} + +Cells-Broadcast-Completed-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +Broadcast-To-Be-Cancelled-Item ::= SEQUENCE { + nRCGI NRCGI, + iE-Extensions ProtocolExtensionContainer { { Broadcast-To-Be-Cancelled-ItemExtIEs } } OPTIONAL, + ... +} + +Broadcast-To-Be-Cancelled-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + + +Cells-Broadcast-Cancelled-Item ::= SEQUENCE { + nRCGI NRCGI, + numberOfBroadcasts NumberOfBroadcasts, + iE-Extensions ProtocolExtensionContainer { { Cells-Broadcast-Cancelled-ItemExtIEs } } OPTIONAL, + ... +} + +Cells-Broadcast-Cancelled-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + Cells-to-be-Activated-List-Item ::= SEQUENCE { nRCGI NRCGI, nRPCI NRPCI OPTIONAL, @@ -5356,6 +9006,8 @@ Cells-to-be-Activated-List-Item ::= SEQUENCE { } Cells-to-be-Activated-List-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { +{ ID id-gNB-CUSystemInformation CRITICALITY reject EXTENSION GNB-CUSystemInformation PRESENCE optional }| +{ ID id-AvailablePLMNList CRITICALITY ignore EXTENSION AvailablePLMNList PRESENCE optional }, ... } @@ -5369,6 +9021,40 @@ Cells-to-be-Deactivated-List-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { ... } +Cells-to-be-Barred-Item::= SEQUENCE { + nRCGI NRCGI , + cellBarred CellBarred, + iE-Extensions ProtocolExtensionContainer { { Cells-to-be-Barred-Item-ExtIEs } } OPTIONAL +} + +Cells-to-be-Barred-Item-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +CellBarred ::= ENUMERATED {barred, not-barred, ...} + +CellULConfigured ::= ENUMERATED {none, ul, sul, ul-and-sul, ...} + +CNUEPagingIdentity ::= CHOICE { + fiveG-S-TMSI BIT STRING (SIZE(48)), + choice-extension ProtocolIE-SingleContainer { { CNUEPagingIdentity-ExtIEs } } +} + +CNUEPagingIdentity-ExtIEs F1AP-PROTOCOL-IES ::= { + ... +} + + +CP-TransportLayerAddress ::= CHOICE { + endpoint-IP-address TransportLayerAddress, + endpoint-IP-address-and-port Endpoint-IP-address-and-port, + choice-extension ProtocolIE-SingleContainer { { CP-TransportLayerAddress-ExtIEs } } +} + +CP-TransportLayerAddress-ExtIEs F1AP-PROTOCOL-IES ::= { + ... +} + CriticalityDiagnostics ::= SEQUENCE { procedureCode ProcedureCode OPTIONAL, triggeringMessage TriggeringMessage OPTIONAL, @@ -5397,31 +9083,52 @@ CriticalityDiagnostics-IE-Item-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { ... } +C-RNTI ::= INTEGER (0..65535, ...) + CUtoDURRCInformation ::= SEQUENCE { cG-ConfigInfo CG-ConfigInfo OPTIONAL, uE-CapabilityRAT-ContainerList UE-CapabilityRAT-ContainerList OPTIONAL, + measConfig MeasConfig OPTIONAL, iE-Extensions ProtocolExtensionContainer { { CUtoDURRCInformation-ExtIEs} } OPTIONAL, ... } CUtoDURRCInformation-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { +{ ID id-HandoverPreparationInformation CRITICALITY ignore EXTENSION HandoverPreparationInformation PRESENCE optional }| +{ ID id-CellGroupConfig CRITICALITY ignore EXTENSION CellGroupConfig PRESENCE optional }| +{ ID id-MeasurementTimingConfiguration CRITICALITY ignore EXTENSION MeasurementTimingConfiguration PRESENCE optional }, ... } -- D -DLTunnels-ToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofDLTunnels)) OF DLTunnels-ToBeSetup-Item +DCBasedDuplicationConfigured::= ENUMERATED{true,... } -DLTunnels-ToBeSetup-Item ::= SEQUENCE { - dL-GTP-Tunnel-EndPoint GTPTunnelEndpoint , - iE-Extensions ProtocolExtensionContainer { { DLTunnels-ToBeSetup-ItemExtIEs } } OPTIONAL, +DLUPTNLInformation-ToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofDLUPTNLInformation)) OF DLUPTNLInformation-ToBeSetup-Item + +DLUPTNLInformation-ToBeSetup-Item ::= SEQUENCE { + dLUPTNLInformation UPTransportLayerInformation , + iE-Extensions ProtocolExtensionContainer { { DLUPTNLInformation-ToBeSetup-ItemExtIEs } } OPTIONAL, ... } -DLTunnels-ToBeSetup-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { +DLUPTNLInformation-ToBeSetup-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { ... } +DRB-Activity-Item ::= SEQUENCE { + dRBID DRBID, + dRB-Activity DRB-Activity OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { DRB-Activity-ItemExtIEs } } OPTIONAL, + ... +} + +DRB-Activity-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +DRB-Activity ::= ENUMERATED {active, not-active} + DRBID ::= INTEGER (1..32, ...) DRBs-FailedToBeModified-Item ::= SEQUENCE { @@ -5435,17 +9142,6 @@ DRBs-FailedToBeModified-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { ... } -DRBs-FailedToBeModifiedConf-Item ::= SEQUENCE { - dRBID DRBID , - cause Cause OPTIONAL, - iE-Extensions ProtocolExtensionContainer { { DRBs-FailedToBeModifiedConf-ItemExtIEs } } OPTIONAL, - ... -} - -DRBs-FailedToBeModifiedConf-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { - ... -} - DRBs-FailedToBeSetup-Item ::= SEQUENCE { dRBID DRBID, cause Cause OPTIONAL, @@ -5469,20 +9165,34 @@ DRBs-FailedToBeSetupMod-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { ... } +DRB-Information ::= SEQUENCE { + dRB-QoS QoSFlowLevelQoSParameters, + sNSSAI SNSSAI, + notificationControl NotificationControl OPTIONAL, + flows-Mapped-To-DRB-List Flows-Mapped-To-DRB-List, + iE-Extensions ProtocolExtensionContainer { { DRB-Information-ItemExtIEs } } OPTIONAL +} + +DRB-Information-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + DRBs-Modified-Item ::= SEQUENCE { dRBID DRBID, - dLTunnels-ToBeSetup-List DLTunnels-ToBeSetup-List, + lCID LCID OPTIONAL, + dLUPTNLInformation-ToBeSetup-List DLUPTNLInformation-ToBeSetup-List, iE-Extensions ProtocolExtensionContainer { { DRBs-Modified-ItemExtIEs } } OPTIONAL, ... } DRBs-Modified-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { + { ID id-RLC-Status CRITICALITY ignore EXTENSION RLC-Status PRESENCE optional }, ... } DRBs-ModifiedConf-Item ::= SEQUENCE { dRBID DRBID, - uLTunnels-ToBeSetup-List ULTunnels-ToBeSetup-List , + uLUPTNLInformation-ToBeSetup-List ULUPTNLInformation-ToBeSetup-List , iE-Extensions ProtocolExtensionContainer { { DRBs-ModifiedConf-ItemExtIEs } } OPTIONAL, ... } @@ -5491,14 +9201,26 @@ DRBs-ModifiedConf-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { ... } +DRB-Notify-Item ::= SEQUENCE { + dRBID DRBID, + notification-Cause Notification-Cause, + iE-Extensions ProtocolExtensionContainer { { DRB-Notify-ItemExtIEs } } OPTIONAL, + ... +} + +DRB-Notify-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + DRBs-Required-ToBeModified-Item ::= SEQUENCE { dRBID DRBID, - dLTunnels-ToBeSetup-List DLTunnels-ToBeSetup-List , + dLUPTNLInformation-ToBeSetup-List DLUPTNLInformation-ToBeSetup-List , iE-Extensions ProtocolExtensionContainer { { DRBs-Required-ToBeModified-ItemExtIEs } } OPTIONAL, ... } DRBs-Required-ToBeModified-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { + { ID id-RLC-Status CRITICALITY ignore EXTENSION RLC-Status PRESENCE optional }, ... } @@ -5514,7 +9236,8 @@ DRBs-Required-ToBeReleased-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { DRBs-Setup-Item ::= SEQUENCE { dRBID DRBID, - dLTunnels-ToBeSetup-List DLTunnels-ToBeSetup-List , + lCID LCID OPTIONAL, + dLUPTNLInformation-ToBeSetup-List DLUPTNLInformation-ToBeSetup-List , iE-Extensions ProtocolExtensionContainer { { DRBs-Setup-ItemExtIEs } } OPTIONAL, ... } @@ -5525,7 +9248,8 @@ DRBs-Setup-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { DRBs-SetupMod-Item ::= SEQUENCE { dRBID DRBID, - dLTunnels-ToBeSetup-List DLTunnels-ToBeSetup-List , + lCID LCID OPTIONAL, + dLUPTNLInformation-ToBeSetup-List DLUPTNLInformation-ToBeSetup-List , iE-Extensions ProtocolExtensionContainer { { DRBs-SetupMod-ItemExtIEs } } OPTIONAL, ... } @@ -5537,14 +9261,15 @@ DRBs-SetupMod-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { DRBs-ToBeModified-Item ::= SEQUENCE { dRBID DRBID, - eUTRANQoS EUTRANQoS OPTIONAL, - uLTunnels-ToBeSetup-List ULTunnels-ToBeSetup-List , + qoSInformation QoSInformation OPTIONAL, + uLUPTNLInformation-ToBeSetup-List ULUPTNLInformation-ToBeSetup-List , uLConfiguration ULConfiguration OPTIONAL, iE-Extensions ProtocolExtensionContainer { { DRBs-ToBeModified-ItemExtIEs } } OPTIONAL, ... } DRBs-ToBeModified-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { + { ID id-PDCPSNLength CRITICALITY ignore EXTENSION PDCPSNLength PRESENCE optional }, ... } @@ -5560,30 +9285,38 @@ DRBs-ToBeReleased-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { DRBs-ToBeSetup-Item ::= SEQUENCE { dRBID DRBID, - eUTRANQoS EUTRANQoS OPTIONAL, - uLTunnels-ToBeSetup-List ULTunnels-ToBeSetup-List , + qoSInformation QoSInformation, + uLUPTNLInformation-ToBeSetup-List ULUPTNLInformation-ToBeSetup-List , rLCMode RLCMode, uLConfiguration ULConfiguration OPTIONAL, + duplicationActivation DuplicationActivation OPTIONAL, iE-Extensions ProtocolExtensionContainer { { DRBs-ToBeSetup-ItemExtIEs } } OPTIONAL, ... } DRBs-ToBeSetup-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { + { ID id-DC-Based-Duplication-Configured CRITICALITY reject EXTENSION DCBasedDuplicationConfigured PRESENCE optional }| + { ID id-DC-Based-Duplication-Activation CRITICALITY reject EXTENSION DuplicationActivation PRESENCE optional }| + { ID id-PDCPSNLength CRITICALITY ignore EXTENSION PDCPSNLength PRESENCE mandatory }, ... } DRBs-ToBeSetupMod-Item ::= SEQUENCE { dRBID DRBID, - eUTRANQoS EUTRANQoS OPTIONAL, + qoSInformation QoSInformation, + uLUPTNLInformation-ToBeSetup-List ULUPTNLInformation-ToBeSetup-List, rLCMode RLCMode, uLConfiguration ULConfiguration OPTIONAL, - uLTunnels-ToBeSetup-List ULTunnels-ToBeSetup-List, + duplicationActivation DuplicationActivation OPTIONAL, iE-Extensions ProtocolExtensionContainer { { DRBs-ToBeSetupMod-ItemExtIEs } } OPTIONAL, ... } DRBs-ToBeSetupMod-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { + { ID id-DC-Based-Duplication-Configured CRITICALITY reject EXTENSION DCBasedDuplicationConfigured PRESENCE optional }| + { ID id-DC-Based-Duplication-Activation CRITICALITY reject EXTENSION DuplicationActivation PRESENCE optional }| + { ID id-PDCPSNLength CRITICALITY ignore EXTENSION PDCPSNLength PRESENCE optional }, ... } @@ -5598,9 +9331,15 @@ DRXCycle ::= SEQUENCE { DRXCycle-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { ... } + +DRXConfigurationIndicator ::= ENUMERATED{ release, ...} + +DUtoCURRCContainer ::= OCTET STRING + DUtoCURRCInformation ::= SEQUENCE { cellGroupConfig CellGroupConfig, - gapOffset GapOffset OPTIONAL, + measGapConfig MeasGapConfig OPTIONAL, + requestedP-MaxFR1 OCTET STRING OPTIONAL, iE-Extensions ProtocolExtensionContainer { { DUtoCURRCInformation-ExtIEs} } OPTIONAL, ... } @@ -5608,8 +9347,52 @@ DUtoCURRCInformation ::= SEQUENCE { DUtoCURRCInformation-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { ... } + +DuplicationActivation ::= ENUMERATED{active,inactive,... } + +DuplicationIndication ::= ENUMERATED {true, ... , false } + +Dynamic5QIDescriptor ::= SEQUENCE { + qoSPriorityLevel INTEGER (1..127), + packetDelayBudget PacketDelayBudget, + packetErrorRate PacketErrorRate, + fiveQI INTEGER (0..255, ...) OPTIONAL, + delayCritical ENUMERATED {delay-critical, non-delay-critical} OPTIONAL, + averagingWindow AveragingWindow OPTIONAL, + maxDataBurstVolume MaxDataBurstVolume OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { Dynamic5QIDescriptor-ExtIEs } } OPTIONAL +} + +Dynamic5QIDescriptor-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + -- E +Endpoint-IP-address-and-port ::=SEQUENCE { + endpointIPAddress TransportLayerAddress, + iE-Extensions ProtocolExtensionContainer { { Endpoint-IP-address-and-port-ExtIEs} } OPTIONAL +} + +Endpoint-IP-address-and-port-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +EUTRACellsinGNBDUCoordination-List ::= SEQUENCE (SIZE (1.. maxCellineNB)) OF EUTRACellsinGNBDUCoordination-List-item + +EUTRACellsinGNBDUCoordination-List-item ::= SEQUENCE { + eUTRA-Cell-ID EUTRA-Cell-ID, + served-EUTRA-Cells-Information Served-EUTRA-Cells-Information, + iE-Extensions ProtocolExtensionContainer { { EUTRACellsinGNBDUCoordination-List-itemExtIEs } } OPTIONAL +} + +EUTRACellsinGNBDUCoordination-List-itemExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + + +EUTRA-Cell-ID ::= BIT STRING (SIZE(28)) + EUTRANQoS ::= SEQUENCE { qCI QCI, allocationAndRetentionPriority AllocationAndRetentionPriority, @@ -5622,13 +9405,48 @@ EUTRANQoS-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { ... } -Extended-TAC ::= OCTET STRING (SIZE(3)) +ExecuteDuplication ::= ENUMERATED{true,...} + +EUTRA-Mode-Info ::= CHOICE { + eUTRAFDD EUTRA-FDD-Info, + eUTRATDD EUTRA-TDD-Info, + choice-extension ProtocolIE-SingleContainer { { EUTRA-Mode-Info-ExtIEs} } +} + +EUTRA-Mode-Info-ExtIEs F1AP-PROTOCOL-IES ::= { + ... +} + +EUTRA-NR-CellResourceCoordinationReq-Container ::= OCTET STRING + +EUTRA-NR-CellResourceCoordinationReqAck-Container ::= OCTET STRING + +EUTRA-FDD-Info ::= SEQUENCE { + uL-offsetToPointA OffsetToPointA, + dL-offsetToPointA OffsetToPointA, + iE-Extensions ProtocolExtensionContainer { {EUTRA-FDD-Info-ExtIEs} } OPTIONAL, + ... +} + +EUTRA-FDD-Info-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +EUTRA-TDD-Info ::= SEQUENCE { + offsetToPointA OffsetToPointA, + iE-Extensions ProtocolExtensionContainer { {EUTRA-TDD-Info-ExtIEs} } OPTIONAL, + ... +} + +EUTRA-TDD-Info-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} -- F FDD-Info ::= SEQUENCE { - uL-NRARFCN NRARFCN, - dL-NRARFCN NRARFCN, + uL-NRFreqInfo NRFreqInfo, + dL-NRFreqInfo NRFreqInfo, uL-Transmission-Bandwidth Transmission-Bandwidth, dL-Transmission-Bandwidth Transmission-Bandwidth, iE-Extensions ProtocolExtensionContainer { {FDD-Info-ExtIEs} } OPTIONAL, @@ -5639,9 +9457,34 @@ FDD-Info-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { ... } + +Flows-Mapped-To-DRB-List ::= SEQUENCE (SIZE(1.. maxnoofQoSFlows)) OF Flows-Mapped-To-DRB-Item + +Flows-Mapped-To-DRB-Item ::= SEQUENCE { + qoSFlowIndicator QoSFlowIndicator, + qoSFlowLevelQoSParameters QoSFlowLevelQoSParameters, + iE-Extensions ProtocolExtensionContainer { { Flows-Mapped-To-DRB-ItemExtIEs} } OPTIONAL +} + +Flows-Mapped-To-DRB-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +FreqBandNrItem ::= SEQUENCE { + freqBandIndicatorNr INTEGER (1..1024,...), + supportedSULBandList SEQUENCE (SIZE(0..maxnoofNrCellBands)) OF SupportedSULFreqBandItem, + iE-Extensions ProtocolExtensionContainer { {FreqBandNrItem-ExtIEs} } OPTIONAL, + ... +} + +FreqBandNrItem-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +FullConfiguration ::= ENUMERATED {full, ...} + -- G -GapOffset ::= OCTET STRING GBR-QosInformation ::= SEQUENCE { e-RAB-MaximumBitrateDL BitRate, @@ -5656,8 +9499,81 @@ GBR-QosInformation-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { ... } +GBR-QoSFlowInformation::= SEQUENCE { + maxFlowBitRateDownlink BitRate, + maxFlowBitRateUplink BitRate, + guaranteedFlowBitRateDownlink BitRate, + guaranteedFlowBitRateUplink BitRate, + maxPacketLossRateDownlink MaxPacketLossRate OPTIONAL, + maxPacketLossRateUplink MaxPacketLossRate OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { GBR-QosFlowInformation-ExtIEs} } OPTIONAL, + ... +} + +GBR-QosFlowInformation-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} +GNB-CUSystemInformation::= SEQUENCE { + sibtypetobeupdatedlist SEQUENCE (SIZE(1.. maxnoofSIBTypes)) OF SibtypetobeupdatedListItem, + iE-Extensions ProtocolExtensionContainer { { GNB-CUSystemInformation-ExtIEs} } OPTIONAL, + ... +} + +GNB-CUSystemInformation-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +GNB-CU-TNL-Association-Setup-Item::= SEQUENCE { + tNLAssociationTransportLayerAddress CP-TransportLayerAddress , + iE-Extensions ProtocolExtensionContainer { { GNB-CU-TNL-Association-Setup-Item-ExtIEs} } OPTIONAL +} + +GNB-CU-TNL-Association-Setup-Item-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +GNB-CU-TNL-Association-Failed-To-Setup-Item ::= SEQUENCE { + tNLAssociationTransportLayerAddress CP-TransportLayerAddress , + cause Cause, + iE-Extensions ProtocolExtensionContainer { { GNB-CU-TNL-Association-Failed-To-Setup-Item-ExtIEs} } OPTIONAL +} + +GNB-CU-TNL-Association-Failed-To-Setup-Item-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + + +GNB-CU-TNL-Association-To-Add-Item ::= SEQUENCE { + tNLAssociationTransportLayerAddress CP-TransportLayerAddress , + tNLAssociationUsage TNLAssociationUsage, + iE-Extensions ProtocolExtensionContainer { { GNB-CU-TNL-Association-To-Add-Item-ExtIEs} } OPTIONAL +} + +GNB-CU-TNL-Association-To-Add-Item-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +GNB-CU-TNL-Association-To-Remove-Item::= SEQUENCE { + tNLAssociationTransportLayerAddress CP-TransportLayerAddress , + iE-Extensions ProtocolExtensionContainer { { GNB-CU-TNL-Association-To-Remove-Item-ExtIEs} } OPTIONAL +} + +GNB-CU-TNL-Association-To-Remove-Item-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + + +GNB-CU-TNL-Association-To-Update-Item::= SEQUENCE { + tNLAssociationTransportLayerAddress CP-TransportLayerAddress , + tNLAssociationUsage TNLAssociationUsage OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { GNB-CU-TNL-Association-To-Update-Item-ExtIEs} } OPTIONAL +} + +GNB-CU-TNL-Association-To-Update-Item-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} GNB-CU-UE-F1AP-ID ::= INTEGER (0..4294967295) @@ -5691,23 +9607,30 @@ GNB-DU-System-Information-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { ... } +GNB-DUConfigurationQuery ::= ENUMERATED {true, ...} + +GNBDUOverloadInformation ::= ENUMERATED {overloaded, not-overloaded} + GTP-TEID ::= OCTET STRING (SIZE (4)) -GTPTunnelEndpoint ::= SEQUENCE { - transportLayerAddress TransportLayerAddress, - gTP-TEID GTP-TEID, - iE-Extensions ProtocolExtensionContainer { { GTPTunnelEndpoint-ExtIEs} } OPTIONAL, +GTPTunnel ::= SEQUENCE { + transportLayerAddress TransportLayerAddress, + gTP-TEID GTP-TEID, + iE-Extensions ProtocolExtensionContainer { { GTPTunnel-ExtIEs } } OPTIONAL, ... } - -GTPTunnelEndpoint-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { +GTPTunnel-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { ... } -- H +HandoverPreparationInformation ::= OCTET STRING + -- I +InactivityMonitoringRequest ::= ENUMERATED { true,...} +InactivityMonitoringResponse ::= ENUMERATED { not-supported,...} -- J @@ -5715,16 +9638,77 @@ GTPTunnelEndpoint-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { -- L +LCID ::= INTEGER (1..32, ...) + + LongDRXCycleLength ::= ENUMERATED {ms10, ms20, ms32, ms40, ms60, ms64, ms70, ms80, ms128, ms160, ms256, ms320, ms512, ms640, ms1024, ms1280, ms2048, ms2560, ms5120, ms10240, ...} -- M +MaskedIMEISV ::= BIT STRING (SIZE (64)) + +MaxDataBurstVolume ::= INTEGER (0..4095, ...) +MaxPacketLossRate ::= INTEGER (0..1000) + MIB-message ::= OCTET STRING +MeasConfig ::= OCTET STRING + +MeasGapConfig ::= OCTET STRING + +MeasurementTimingConfiguration ::= OCTET STRING + -- N -NRARFCN ::= INTEGER (0..maxNRARFCN) +NGRANAllocationAndRetentionPriority ::= SEQUENCE { + priorityLevel PriorityLevel, + pre-emptionCapability Pre-emptionCapability, + pre-emptionVulnerability Pre-emptionVulnerability, + iE-Extensions ProtocolExtensionContainer { {NGRANAllocationAndRetentionPriority-ExtIEs} } OPTIONAL +} + +NGRANAllocationAndRetentionPriority-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +NR-CGI-List-For-Restart-Item ::= SEQUENCE { + nRCGI NRCGI, + iE-Extensions ProtocolExtensionContainer { { NR-CGI-List-For-Restart-ItemExtIEs } } OPTIONAL, + ... +} + +NR-CGI-List-For-Restart-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +NonDynamic5QIDescriptor ::= SEQUENCE { + fiveQI INTEGER (0..255, ...), + qoSPriorityLevel INTEGER (1..127) OPTIONAL, + averagingWindow AveragingWindow OPTIONAL, + maxDataBurstVolume MaxDataBurstVolume OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { NonDynamic5QIDescriptor-ExtIEs } } OPTIONAL +} + +NonDynamic5QIDescriptor-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +Notification-Cause ::= ENUMERATED {fulfilled, not-fulfilled, ...} + +NotificationControl ::= ENUMERATED {active, not-active, ...} + +NRFreqInfo ::= SEQUENCE { + nRARFCN INTEGER (0..maxNRARFCN), + sul-Information SUL-Information OPTIONAL, + freqBandListNr SEQUENCE (SIZE(1..maxnoofNrCellBands)) OF FreqBandNrItem, + iE-Extensions ProtocolExtensionContainer { { NRFreqInfoExtIEs} } OPTIONAL, + ... +} + +NRFreqInfoExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} NRCGI ::= SEQUENCE { pLMN-Identity PLMN-Identity, @@ -5740,9 +9724,13 @@ NRCGI-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { NR-Mode-Info ::= CHOICE { fDD FDD-Info, tDD TDD-Info, - ... + choice-extension ProtocolIE-SingleContainer { { NR-Mode-Info-ExtIEs} } } +NR-Mode-Info-ExtIEs F1AP-PROTOCOL-IES ::= { ... +} + + NRCellIdentity ::= BIT STRING (SIZE(36)) NRNRB ::= ENUMERATED { nrb11, nrb18, nrb24, nrb25, nrb31, nrb32, nrb38, nrb51, nrb52, nrb65, nrb66, nrb78, nrb79, nrb93, nrb106, nrb107, nrb121, nrb132, nrb133, nrb135, nrb160, nrb162, nrb189, nrb216, nrb217, nrb245, nrb264, nrb270, nrb273, ...} @@ -5751,10 +9739,65 @@ NRPCI ::= INTEGER(0..1007) NRSCS ::= ENUMERATED { scs15, scs30, scs60, scs120, ...} +NumberOfBroadcasts ::= INTEGER (0..65535) + +NumberofBroadcastRequest ::= INTEGER (0..65535) + -- O +OffsetToPointA ::= INTEGER (0..2199,...) + + -- P +PacketDelayBudget ::= INTEGER (0..1023, ...) + +PacketErrorRate ::= SEQUENCE { + pER-Scalar PER-Scalar, + pER-Exponent PER-Exponent, + iE-Extensions ProtocolExtensionContainer { {PacketErrorRate-ExtIEs} } OPTIONAL, + ... +} + +PacketErrorRate-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +PER-Scalar ::= INTEGER (0..9, ...) +PER-Exponent ::= INTEGER (0..9, ...) + +PagingCell-Item ::= SEQUENCE { + nRCGI NRCGI , + iE-Extensions ProtocolExtensionContainer { { PagingCell-ItemExtIEs } } OPTIONAL +} + +PagingCell-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +PagingDRX ::= ENUMERATED { + v32, + v64, + v128, + v256, + ... + } +PagingIdentity ::= CHOICE { + rANUEPagingIdentity RANUEPagingIdentity, + cNUEPagingIdentity CNUEPagingIdentity, + choice-extension ProtocolIE-SingleContainer { { PagingIdentity-ExtIEs } } +} + +PagingIdentity-ExtIEs F1AP-PROTOCOL-IES::= { + ... +} + +PagingPriority ::= ENUMERATED { priolevel1, priolevel2, priolevel3, priolevel4, priolevel5, priolevel6, priolevel7, priolevel8,...} + +PDCPSNLength ::= ENUMERATED { twelve-bits,eighteen-bits,...} + +PDUSessionID ::= INTEGER (0..255) + PLMN-Identity ::= OCTET STRING (SIZE(3)) Pre-emptionCapability ::= ENUMERATED { @@ -5769,6 +9812,18 @@ Pre-emptionVulnerability ::= ENUMERATED { PriorityLevel ::= INTEGER { spare (0), highest (1), lowest (14), no-priority (15) } (0..15) +ProtectedEUTRAResourceIndication ::= OCTET STRING + +Protected-EUTRA-Resources-Item ::= SEQUENCE { + spectrumSharingGroupID SpectrumSharingGroupID, + eUTRACellsinGNBDUCoordination-List EUTRACellsinGNBDUCoordination-List, + iE-Extensions ProtocolExtensionContainer { { Protected-EUTRA-Resources-ItemExtIEs } } OPTIONAL +} + +Protected-EUTRA-Resources-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + Potential-SpCell-Item ::= SEQUENCE { potential-SpCell-ID NRCGI , iE-Extensions ProtocolExtensionContainer { { Potential-SpCell-ItemExtIEs } } OPTIONAL, @@ -5779,28 +9834,138 @@ Potential-SpCell-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { ... } +PWS-Failed-NR-CGI-Item ::= SEQUENCE { + nRCGI NRCGI, + numberOfBroadcasts NumberOfBroadcasts, + iE-Extensions ProtocolExtensionContainer { { PWS-Failed-NR-CGI-ItemExtIEs } } OPTIONAL, + ... +} + +PWS-Failed-NR-CGI-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +PWSSystemInformation ::= OCTET STRING + -- Q QCI ::= INTEGER (0..255) +QoS-Characteristics ::= CHOICE { + non-Dynamic-5QI NonDynamic5QIDescriptor, + dynamic-5QI Dynamic5QIDescriptor, + choice-extension ProtocolIE-SingleContainer { { QoS-Characteristics-ExtIEs } } +} + +QoS-Characteristics-ExtIEs F1AP-PROTOCOL-IES ::= { + ... +} + +QoSFlowIndicator ::= INTEGER (0..63) + +QoSFlowLevelQoSParameters ::= SEQUENCE { + qoS-Characteristics QoS-Characteristics, + nGRANallocationRetentionPriority NGRANAllocationAndRetentionPriority, + gBR-QoS-Flow-Information GBR-QoSFlowInformation OPTIONAL, + reflective-QoS-Attribute ENUMERATED {subject-to, ...} OPTIONAL, + iE-Extensions ProtocolExtensionContainer { { QoSFlowLevelQoSParameters-ExtIEs } } OPTIONAL +} + +QoSFlowLevelQoSParameters-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + { ID id-PDUSessionID CRITICALITY ignore EXTENSION PDUSessionID PRESENCE optional}| + { ID id-ULPDUSessionAggregateMaximumBitRate CRITICALITY ignore EXTENSION BitRate PRESENCE optional}, + ... +} + +QoSInformation ::= CHOICE { + eUTRANQoS EUTRANQoS, + choice-extension ProtocolIE-SingleContainer { { QoSInformation-ExtIEs} } +} + +QoSInformation-ExtIEs F1AP-PROTOCOL-IES ::= { + { ID id-DRB-Information CRITICALITY ignore TYPE DRB-Information PRESENCE optional}, + ... +} + -- R +RANAC ::= INTEGER (0..255) + +RANUEPagingIdentity ::= SEQUENCE { + iRNTI BIT STRING (SIZE(40)), + iE-Extensions ProtocolExtensionContainer { { RANUEPagingIdentity-ExtIEs } } OPTIONAL} + +RANUEPagingIdentity-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +RAT-FrequencyPriorityInformation::= CHOICE { + subscriberProfileIDforRFP SubscriberProfileIDforRFP, + rAT-FrequencySelectionPriority RAT-FrequencySelectionPriority, + choice-extension ProtocolIE-SingleContainer { { RAT-FrequencyPriorityInformation-ExtIEs} } +} + +RAT-FrequencyPriorityInformation-ExtIEs F1AP-PROTOCOL-IES ::= { + ... +} + +RAT-FrequencySelectionPriority::= INTEGER (1.. 256, ...) + +Reestablishment-Indication ::= ENUMERATED { + reestablished, + ... +} + +RequestType ::= ENUMERATED {offer, execution, ...} + ResourceCoordinationTransferContainer ::= OCTET STRING +RepetitionPeriod ::= INTEGER (0..131071, ...) + +RLCFailureIndication ::= SEQUENCE { + assocatedLCID LCID, + iE-Extensions ProtocolExtensionContainer { {RLCFailureIndication-ExtIEs} } OPTIONAL +} + +RLCFailureIndication-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + RLCMode ::= ENUMERATED { rlc-am, - rlc-um + rlc-um-bidirectional, + rlc-um-unidirectional-ul, + rlc-um-unidirectional-dl, + ... +} + +RLC-Status ::= SEQUENCE { + reestablishment-Indication Reestablishment-Indication, + iE-Extensions ProtocolExtensionContainer { { RLC-Status-ExtIEs } } OPTIONAL, + ... +} + +RLC-Status-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... } RRCContainer ::= OCTET STRING RRCRconfigurationCompleteIndicator ::= ENUMERATED {true, ...} +RRC-Version ::= SEQUENCE { + latest-RRC-Version BIT STRING (SIZE(3)), + iE-Extensions ProtocolExtensionContainer { { RRC-Version-ExtIEs } } OPTIONAL} + +RRC-Version-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + -- S SCell-FailedtoSetup-Item ::= SEQUENCE { sCell-ID NRCGI , - cause Cause OPTIONAL , + cause Cause OPTIONAL , iE-Extensions ProtocolExtensionContainer { { SCell-FailedtoSetup-ItemExtIEs } } OPTIONAL, ... } @@ -5832,7 +9997,8 @@ SCell-ToBeRemoved-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { SCell-ToBeSetup-Item ::= SEQUENCE { sCell-ID NRCGI , - sCellIndex SCellIndex, + sCellIndex SCellIndex, + sCellULConfigured CellULConfigured OPTIONAL, iE-Extensions ProtocolExtensionContainer { { SCell-ToBeSetup-ItemExtIEs } } OPTIONAL, ... } @@ -5844,6 +10010,7 @@ SCell-ToBeSetup-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { SCell-ToBeSetupMod-Item ::= SEQUENCE { sCell-ID NRCGI , sCellIndex SCellIndex, + sCellULConfigured CellULConfigured OPTIONAL, iE-Extensions ProtocolExtensionContainer { { SCell-ToBeSetupMod-ItemExtIEs } } OPTIONAL, ... } @@ -5852,23 +10019,26 @@ SCell-ToBeSetupMod-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { ... } -SCellIndex ::=INTEGER (0..31, ...) +SCellIndex ::=INTEGER (1..31, ...) CG-ConfigInfo ::= OCTET STRING +ServCellIndex ::= INTEGER (0..31, ...) + Served-Cell-Information ::= SEQUENCE { nRCGI NRCGI, nRPCI NRPCI, - extended-TAC Extended-TAC, - broadcastPLMNs BroadcastPLMNs-Item, + fiveGS-TAC FiveGS-TAC OPTIONAL, + configured-EPS-TAC Configured-EPS-TAC OPTIONAL, + servedPLMNs BroadcastPLMNs-List, nR-Mode-Info NR-Mode-Info, - sUL-Information SUL-Information OPTIONAL, measurementTimingConfiguration OCTET STRING, iE-Extensions ProtocolExtensionContainer { {Served-Cell-Information-ExtIEs} } OPTIONAL, ... } Served-Cell-Information-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + { ID id-RANAC CRITICALITY ignore EXTENSION RANAC PRESENCE optional }, ... } @@ -5905,13 +10075,72 @@ Served-Cells-To-Modify-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { ... } +Served-EUTRA-Cells-Information::= SEQUENCE { + eUTRA-Mode-Info EUTRA-Mode-Info, + protectedEUTRAResourceIndication ProtectedEUTRAResourceIndication, + iE-Extensions ProtocolExtensionContainer { {Served-EUTRA-Cell-Information-ExtIEs} } OPTIONAL, + ... +} + +Served-EUTRA-Cell-Information-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + ShortDRXCycleLength ::= ENUMERATED {ms2, ms3, ms4, ms5, ms6, ms7, ms8, ms10, ms14, ms16, ms20, ms30, ms32, ms35, ms40, ms64, ms80, ms128, ms160, ms256, ms320, ms512, ms640, ...} ShortDRXCycleTimer ::= INTEGER (1..16) SIB1-message ::= OCTET STRING -SRBID ::= INTEGER (1..3, ...) +SItype ::= INTEGER (1..32, ...) + +SItype-List ::= SEQUENCE (SIZE(1.. maxnoofSITypes)) OF SItype-Item + +SItype-Item ::= SEQUENCE { + sItype SItype , + iE-Extensions ProtocolExtensionContainer { { SItype-ItemExtIEs } } OPTIONAL +} + +SItype-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +SibtypetobeupdatedListItem ::= SEQUENCE { + sIBtype INTEGER (2..32,...), + sIBmessage OCTET STRING, + valueTag INTEGER (0..31,...), + iE-Extensions ProtocolExtensionContainer { { SibtypetobeupdatedListItem-ExtIEs } } OPTIONAL, + ... +} + +SibtypetobeupdatedListItem-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +SliceSupportList ::= SEQUENCE (SIZE(1.. maxnoofSliceItems)) OF SliceSupportItem + +SliceSupportItem ::= SEQUENCE { + sNSSAI SNSSAI, + iE-Extensions ProtocolExtensionContainer { { SliceSupportItem-ExtIEs } } OPTIONAL +} + +SliceSupportItem-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +SNSSAI ::= SEQUENCE { + sST OCTET STRING (SIZE(1)), + sD OCTET STRING (SIZE(3)) OPTIONAL , + iE-Extensions ProtocolExtensionContainer { { SNSSAI-ExtIEs } } OPTIONAL +} + +SNSSAI-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + +SpectrumSharingGroupID ::= INTEGER (1..maxCellineNB) + +SRBID ::= INTEGER (0..3, ...) SRBs-FailedToBeSetup-Item ::= SEQUENCE { sRBID SRBID , @@ -5957,7 +10186,8 @@ SRBs-ToBeReleased-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { } SRBs-ToBeSetup-Item ::= SEQUENCE { - sRBID SRBID , + sRBID SRBID , + duplicationIndication DuplicationIndication OPTIONAL, iE-Extensions ProtocolExtensionContainer { { SRBs-ToBeSetup-ItemExtIEs } } OPTIONAL, ... } @@ -5968,6 +10198,7 @@ SRBs-ToBeSetup-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { SRBs-ToBeSetupMod-Item ::= SEQUENCE { sRBID SRBID, + duplicationIndication DuplicationIndication OPTIONAL, iE-Extensions ProtocolExtensionContainer { { SRBs-ToBeSetupMod-ItemExtIEs } } OPTIONAL, ... } @@ -5977,7 +10208,7 @@ SRBs-ToBeSetupMod-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { } SUL-Information ::= SEQUENCE { - sUL-NRARFCN NRARFCN, + sUL-NRARFCN INTEGER (0..maxNRARFCN), sUL-transmission-Bandwidth Transmission-Bandwidth, iE-Extensions ProtocolExtensionContainer { { SUL-InformationExtIEs} } OPTIONAL, ... @@ -5987,10 +10218,29 @@ SUL-InformationExtIEs F1AP-PROTOCOL-EXTENSION ::= { ... } +SubscriberProfileIDforRFP ::= INTEGER (1..256, ...) + +SULAccessIndication ::= ENUMERATED {true,...} + + +SupportedSULFreqBandItem ::= SEQUENCE { + freqBandIndicatorNr INTEGER (1..1024,...), + iE-Extensions ProtocolExtensionContainer { { SupportedSULFreqBandItem-ExtIEs} } OPTIONAL, + ... +} + +SupportedSULFreqBandItem-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { + ... +} + -- T +FiveGS-TAC ::= OCTET STRING (SIZE(3)) + +Configured-EPS-TAC ::= OCTET STRING (SIZE(2)) + TDD-Info ::= SEQUENCE { - nRARFCN NRARFCN, + nRFreqInfo NRFreqInfo, transmission-Bandwidth Transmission-Bandwidth, iE-Extensions ProtocolExtensionContainer { {TDD-Info-ExtIEs} } OPTIONAL, ... @@ -6002,6 +10252,13 @@ TDD-Info-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { TimeToWait ::= ENUMERATED {v1s, v2s, v5s, v10s, v20s, v60s, ...} +TNLAssociationUsage ::= ENUMERATED { + ue, + non-ue, + both, +... +} + TransportLayerAddress ::= BIT STRING (SIZE(1..160, ...)) TransactionID ::= INTEGER (0..255, ...) @@ -6017,7 +10274,7 @@ Transmission-Bandwidth-ExtIEs F1AP-PROTOCOL-EXTENSION ::= { ... } -TransmissionStopIndicator ::= ENUMERATED {true, ...} +TransmissionStopIndicator ::= ENUMERATED {stop, ..., restart } TypeOfError ::= ENUMERATED { not-understood, @@ -6040,6 +10297,15 @@ UE-associatedLogicalF1-ConnectionItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { UE-CapabilityRAT-ContainerList::= OCTET STRING +UEIdentityIndexValue ::= CHOICE { + indexLength10 BIT STRING (SIZE (10)), + choice-extension ProtocolIE-SingleContainer { {UEIdentityIndexValueChoice-ExtIEs} } +} + +UEIdentityIndexValueChoice-ExtIEs F1AP-PROTOCOL-IES ::= { + ... +} + ULConfiguration ::= SEQUENCE { uLUEConfiguration ULUEConfiguration, iE-Extensions ProtocolExtensionContainer { { ULConfigurationExtIEs } } OPTIONAL, @@ -6052,18 +10318,28 @@ ULConfigurationExtIEs F1AP-PROTOCOL-EXTENSION ::= { ULUEConfiguration ::= ENUMERATED {no-data, shared, only, ...} -ULTunnels-ToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofULTunnels)) OF ULTunnels-ToBeSetup-Item +ULUPTNLInformation-ToBeSetup-List ::= SEQUENCE (SIZE(1..maxnoofULUPTNLInformation)) OF ULUPTNLInformation-ToBeSetup-Item -ULTunnels-ToBeSetup-Item ::=SEQUENCE { - uL-GTP-Tunnel-EndPoint GTPTunnelEndpoint, - iE-Extensions ProtocolExtensionContainer { { ULTunnels-ToBeSetup-ItemExtIEs } } OPTIONAL, +ULUPTNLInformation-ToBeSetup-Item ::=SEQUENCE { + uLUPTNLInformation UPTransportLayerInformation, + iE-Extensions ProtocolExtensionContainer { { ULUPTNLInformation-ToBeSetup-ItemExtIEs } } OPTIONAL, ... } -ULTunnels-ToBeSetup-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { +ULUPTNLInformation-ToBeSetup-ItemExtIEs F1AP-PROTOCOL-EXTENSION ::= { ... } +UplinkTxDirectCurrentListInformation ::= OCTET STRING + +UPTransportLayerInformation ::= CHOICE { + gTPTunnel GTPTunnel, + choice-extension ProtocolIE-SingleContainer { { UPTransportLayerInformation-ExtIEs} } +} + +UPTransportLayerInformation-ExtIEs F1AP-PROTOCOL-IES ::= { + ... + } -- V -- W @@ -6157,6 +10433,16 @@ id-InitialULRRCMessageTransfer ProcedureCode ::= 11 id-DLRRCMessageTransfer ProcedureCode ::= 12 id-ULRRCMessageTransfer ProcedureCode ::= 13 id-privateMessage ProcedureCode ::= 14 +id-UEInactivityNotification ProcedureCode ::= 15 +id-GNBDUResourceCoordination ProcedureCode ::= 16 +id-SystemInformationDeliveryCommand ProcedureCode ::= 17 +id-Paging ProcedureCode ::= 18 +id-Notify ProcedureCode ::= 19 +id-WriteReplaceWarning ProcedureCode ::= 20 +id-PWSCancel ProcedureCode ::= 21 +id-PWSRestartIndication ProcedureCode ::= 22 +id-PWSFailureIndication ProcedureCode ::= 23 +id-GNBDUStatusIndication ProcedureCode ::= 24 -- ************************************************************** -- @@ -6173,18 +10459,27 @@ maxProtocolIEs INTEGER ::= 65535 -- -- ************************************************************** -maxNRARFCN INTEGER ::= 3266667 +maxNRARFCN INTEGER ::= 3279165 maxnoofErrors INTEGER ::= 256 maxnoofIndividualF1ConnectionsToReset INTEGER ::= 65536 maxCellingNBDU INTEGER ::= 512 -maxnoofSCells INTEGER ::= 64 +maxnoofSCells INTEGER ::= 32 maxnoofSRBs INTEGER ::= 8 maxnoofDRBs INTEGER ::= 64 -maxnoofULTunnels INTEGER ::= 2 -maxnoofDLTunnels INTEGER ::= 2 +maxnoofULUPTNLInformation INTEGER ::= 2 +maxnoofDLUPTNLInformation INTEGER ::= 2 maxnoofBPLMNs INTEGER ::= 6 maxnoofCandidateSpCells INTEGER ::= 64 maxnoofPotentialSpCells INTEGER ::= 64 +maxnoofNrCellBands INTEGER ::= 32 +maxnoofSIBTypes INTEGER ::= 32 +maxnoofSITypes INTEGER ::= 32 +maxnoofPagingCells INTEGER ::= 512 +maxnoofTNLAssociations INTEGER ::= 32 +maxnoofQoSFlows INTEGER ::= 64 +maxnoofSliceItems INTEGER ::= 1024 +maxCellineNB INTEGER ::= 256 + -- ************************************************************** -- @@ -6201,8 +10496,6 @@ id-Cells-to-be-Deactivated-List ProtocolIE-ID ::= 5 id-Cells-to-be-Deactivated-List-Item ProtocolIE-ID ::= 6 id-CriticalityDiagnostics ProtocolIE-ID ::= 7 id-CUtoDURRCInformation ProtocolIE-ID ::= 9 -id-DRBs-FailedToBeModifiedConf-Item ProtocolIE-ID ::= 10 -id-DRBs-FailedToBeModifiedConf-List ProtocolIE-ID ::= 11 id-DRBs-FailedToBeModified-Item ProtocolIE-ID ::= 12 id-DRBs-FailedToBeModified-List ProtocolIE-ID ::= 13 id-DRBs-FailedToBeSetup-Item ProtocolIE-ID ::= 14 @@ -6279,13 +10572,93 @@ id-SCell-FailedtoSetup-Item ProtocolIE-ID ::= 84 id-SCell-FailedtoSetupMod-List ProtocolIE-ID ::= 85 id-SCell-FailedtoSetupMod-Item ProtocolIE-ID ::= 86 id-RRCRconfigurationCompleteIndicator ProtocolIE-ID ::= 87 -id-Active-Cells-Item ProtocolIE-ID ::= 88 -id-Active-Cells-List ProtocolIE-ID ::= 89 +id-Cells-Status-Item ProtocolIE-ID ::= 88 +id-Cells-Status-List ProtocolIE-ID ::= 89 id-Candidate-SpCell-List ProtocolIE-ID ::= 90 id-Candidate-SpCell-Item ProtocolIE-ID ::= 91 id-Potential-SpCell-List ProtocolIE-ID ::= 92 id-Potential-SpCell-Item ProtocolIE-ID ::= 93 - +id-FullConfiguration ProtocolIE-ID ::= 94 +id-C-RNTI ProtocolIE-ID ::= 95 +id-SpCellULConfigured ProtocolIE-ID ::= 96 +id-InactivityMonitoringRequest ProtocolIE-ID ::= 97 +id-InactivityMonitoringResponse ProtocolIE-ID ::= 98 +id-DRB-Activity-Item ProtocolIE-ID ::= 99 +id-DRB-Activity-List ProtocolIE-ID ::= 100 +id-EUTRA-NR-CellResourceCoordinationReq-Container ProtocolIE-ID ::= 101 +id-EUTRA-NR-CellResourceCoordinationReqAck-Container ProtocolIE-ID ::= 102 +id-Protected-EUTRA-Resources-List ProtocolIE-ID ::= 105 +id-RequestType ProtocolIE-ID ::= 106 +id-ServCellndex ProtocolIE-ID ::= 107 +id-RAT-FrequencyPriorityInformation ProtocolIE-ID ::= 108 +id-ExecuteDuplication ProtocolIE-ID ::= 109 +id-NRCGI ProtocolIE-ID ::= 111 +id-PagingCell-Item ProtocolIE-ID ::= 112 +id-PagingCell-List ProtocolIE-ID ::= 113 +id-PagingDRX ProtocolIE-ID ::= 114 +id-PagingPriority ProtocolIE-ID ::= 115 +id-SItype-List ProtocolIE-ID ::= 116 +id-UEIdentityIndexValue ProtocolIE-ID ::= 117 +id-gNB-CUSystemInformation ProtocolIE-ID ::= 118 +id-HandoverPreparationInformation ProtocolIE-ID ::= 119 +id-GNB-CU-TNL-Association-To-Add-Item ProtocolIE-ID ::= 120 +id-GNB-CU-TNL-Association-To-Add-List ProtocolIE-ID ::= 121 +id-GNB-CU-TNL-Association-To-Remove-Item ProtocolIE-ID ::= 122 +id-GNB-CU-TNL-Association-To-Remove-List ProtocolIE-ID ::= 123 +id-GNB-CU-TNL-Association-To-Update-Item ProtocolIE-ID ::= 124 +id-GNB-CU-TNL-Association-To-Update-List ProtocolIE-ID ::= 125 +id-MaskedIMEISV ProtocolIE-ID ::= 126 +id-PagingIdentity ProtocolIE-ID ::= 127 +id-DUtoCURRCContainer ProtocolIE-ID ::= 128 +id-Cells-to-be-Barred-List ProtocolIE-ID ::= 129 +id-Cells-to-be-Barred-Item ProtocolIE-ID ::= 130 +id-TAISliceSupportList ProtocolIE-ID ::= 131 +id-GNB-CU-TNL-Association-Setup-List ProtocolIE-ID ::= 132 +id-GNB-CU-TNL-Association-Setup-Item ProtocolIE-ID ::= 133 +id-GNB-CU-TNL-Association-Failed-To-Setup-List ProtocolIE-ID ::= 134 +id-GNB-CU-TNL-Association-Failed-To-Setup-Item ProtocolIE-ID ::= 135 +id-DRB-Notify-Item ProtocolIE-ID ::= 136 +id-DRB-Notify-List ProtocolIE-ID ::= 137 +id-NotficationControl ProtocolIE-ID ::= 138 +id-RANAC ProtocolIE-ID ::= 139 +id-PWSSystemInformation ProtocolIE-ID ::= 140 +id-RepetitionPeriod ProtocolIE-ID ::= 141 +id-NumberofBroadcastRequest ProtocolIE-ID ::= 142 +id-Cells-To-Be-Broadcast-List ProtocolIE-ID ::= 144 +id-Cells-To-Be-Broadcast-Item ProtocolIE-ID ::= 145 +id-Cells-Broadcast-Completed-List ProtocolIE-ID ::= 146 +id-Cells-Broadcast-Completed-Item ProtocolIE-ID ::= 147 +id-Broadcast-To-Be-Cancelled-List ProtocolIE-ID ::= 148 +id-Broadcast-To-Be-Cancelled-Item ProtocolIE-ID ::= 149 +id-Cells-Broadcast-Cancelled-List ProtocolIE-ID ::= 150 +id-Cells-Broadcast-Cancelled-Item ProtocolIE-ID ::= 151 +id-NR-CGI-List-For-Restart-List ProtocolIE-ID ::= 152 +id-NR-CGI-List-For-Restart-Item ProtocolIE-ID ::= 153 +id-PWS-Failed-NR-CGI-List ProtocolIE-ID ::= 154 +id-PWS-Failed-NR-CGI-Item ProtocolIE-ID ::= 155 +id-ConfirmedUEID ProtocolIE-ID ::= 156 +id-Cancel-all-Warning-Messages-Indicator ProtocolIE-ID ::= 157 +id-GNB-DU-UE-AMBR-UL ProtocolIE-ID ::= 158 +id-DRXConfigurationIndicator ProtocolIE-ID ::= 159 +id-RLC-Status ProtocolIE-ID ::= 160 +id-PDCPSNLength ProtocolIE-ID ::= 161 +id-GNB-DUConfigurationQuery ProtocolIE-ID ::= 162 +id-MeasurementTimingConfiguration ProtocolIE-ID ::= 163 +id-DRB-Information ProtocolIE-ID ::= 164 +id-ServingPLMN ProtocolIE-ID ::= 165 +id-Protected-EUTRA-Resources-Item ProtocolIE-ID ::= 168 +id-GNB-CU-RRC-Version ProtocolIE-ID ::= 170 +id-GNB-DU-RRC-Version ProtocolIE-ID ::= 171 +id-GNBDUOverloadInformation ProtocolIE-ID ::= 172 +id-CellGroupConfig ProtocolIE-ID ::= 173 +id-RLCFailureIndication ProtocolIE-ID ::= 174 +id-UplinkTxDirectCurrentListInformation ProtocolIE-ID ::= 175 +id-DC-Based-Duplication-Configured ProtocolIE-ID ::= 176 +id-DC-Based-Duplication-Activation ProtocolIE-ID ::= 177 +id-SULAccessIndication ProtocolIE-ID ::= 178 +id-AvailablePLMNList ProtocolIE-ID ::= 179 +id-PDUSessionID ProtocolIE-ID ::= 180 +id-ULPDUSessionAggregateMaximumBitRate ProtocolIE-ID ::= 181 END 9.4.8 Container Definitions @@ -6479,9 +10852,9 @@ F1AP shall use the ASN.1 Basic Packed Encoding Rules (BASIC-PER) Aligned Variant 9.6 Timers 10 Handling of unknown, unforeseen and erroneous protocol data -Clause 10 of TS 38.413 [3] is applicable for the purposes of the present document, with the following additions: +Clause 10 of TS 38.413 [3] is applicable for the purposes of the present document, with the following additions for non-UE-associated procedures: - In case of Abstract Syntax Error, when reporting the Criticality Diagnostics IE for not comprehended IE/IEgroups or missing IE/IE groups, the Transaction ID IE shall also be included; -- In case of Logical Error, when reporting the Criticality Diagnostics IE, the Transaction ID IE shall also be included. +- In case of Logical Error, when reporting the Criticality Diagnostics IE, the Transaction ID IE shall also be included; - In case of Logical Error in a response message of a Class 1 procedure, or failure to comprehend Transaction ID IE from a received message, the procedure shall be considered as unsuccessfully terminated or not terminated (e.g., transaction ID unknown in response message), and local error handling shall be initiated. Annex A (informative): @@ -6568,4 +10941,244 @@ Baseline CR for March version of TS 38.473 covering agreements of RAN3#99 Editorial correction to ASN.1 (correction to id-TimeToWait ProtocolIE-ID) 15.1.1 +2018-06 +RP-80 +RP-181237 +0011 +6 +B +Introduction of SA NR (38.473 Baseline CR covering RAN3 agreements) +15.2.0 +2018-06 +RP-80 +RP-181239 +0043 +3 +F +Essential corrections of EN-DC for NSA NR (38.473 Baseline CR covering RAN3 agreements) +15.2.0 +2018-06 +RP-80 +RP-181237 +0045 +- +B +F1 support for LTE - NR coexistence +15.2.0 +2018-06 +RP-80 + + + + +Correction to ASN.1 and to Change History table +15.2.1 +2018-09 +RP-81 +RP-181920 +0055 +2 +F +Introduction of DU Configuration Query +15.3.0 +2018-09 +RP-81 +RP-181921 +0056 +4 +F +CR to 38.473 on further clarifications on System information transfer over F1 +15.3.0 +2018-09 +RP-81 +RP-181921 +0058 +4 +F +CR to 38.473 on corrections to System information delivery +15.3.0 +2018-09 +RP-81 +RP-181920 +0059 +1 +F +CR to 38.473 on corrections to PWS transfer over F1 +15.3.0 +2018-09 +RP-81 +RP-181921 +0063 +3 +F +CR to 38.473 on PDCP SN over F1 interface +15.3.0 +2018-09 +RP-81 +RP-181922 +0064 +3 +F +NR Corrections (38.473 Baseline CR covering RAN3-101 agreements) +15.3.0 +2018-09 +RP-81 +RP-181997 +0068 +- +F +Introduction of UL AMBR on F1 +15.3.0 +2018-09 +RP-81 +RP-181921 +0072 +3 +F +Correction on cell management +15.3.0 +2018-09 +RP-81 +RP-181921 +0073 +2 +F +RLC Mode Indication over F1 +15.3.0 +2018-09 +RP-81 +RP-181921 +0076 +3 +F +CR to 38.473 on UE Identity Index value +15.3.0 +2018-09 +RP-81 +RP-181920 +0077 +1 +F +Correction for UE Context Modification on presence of ServCellIndex IE +15.3.0 +2018-09 +RP-81 +RP-181920 +0078 +- +F +Executing duplication for RRC-container +15.3.0 +2018-09 +RP-81 +RP-181921 +0079 +1 +F +Indication of RLC re-establishment at the gNB-DU +15.3.0 +2018-09 +RP-81 +RP-181920 +0080 +- +F +Exchange of SMTC over F1 +15.3.0 +2018-09 +RP-81 +RP-181920 +0081 +- +F +Solving remaining issues with QoS parameters – TS 38.473 +15.3.0 +2018-09 +RP-81 +RP-181921 +0090 + +F +Correction of 5GS TAC +15.3.0 +2018-09 +RP-81 +RP-181921 +0095 +1 +F +Extend the RANAC size to 8bits +15.3.0 +2018-09 +RP-81 +RP-181921 +0097 +- +F +Corrections of Choice +15.3.0 +2018-09 +RP-81 +RP-181921 +0098 +1 +F +Correction of TNL criticality +15.3.0 +2018-09 +RP-81 +RP-181921 +0099 +1 +F +Corrections of usage of single container +15.3.0 +2018-09 +RP-81 +RP-181921 +0105 +2 +B +RRC version handling +15.3.0 +2018-09 +RP-81 +RP-181921 +0106 +1 +B +Introduction of Overload Handling in F1-C +15.3.0 +2018-09 +RP-81 +RP-181921 +0113 +- +F +CR to 38.473 on presence of QoS information +15.3.0 +2018-09 +RP-81 +RP-181921 +0114 +1 +F +Correction C-RNTI format +15.3.0 +2018-09 +RP-81 +RP-181921 +0115 +- +F +Correction of QoS Parameters +15.3.0 +2018-09 +RP-81 +RP-181921 +0116 +1 +F +Correction on F1 Setup Request +15.3.0