Backhaul link connection information

By adopting a new radio access network architecture in a multi-carrier communication system, managing and scheduling backhaul links, and using multi-carrier aggregation and transmission of CSI-RS/SS blocks, the problem of low efficiency in backhaul link connection information management is solved, and the problem of low backhaul link connection information management is realized. More efficient resource utilization and service quality improvement.

CN118972871APending Publication Date: 2024-11-15OFINNO LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410705950.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2018-09-08
Filing Date
2019-09-09
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

In the prior art, in a multi-carrier communication system, the management and scheduling efficiency of backhaul link connection information is low, resulting in insufficient resource utilization of radio access networks, difficulty in obtaining channel state information, and affecting the mobility management and service quality of user equipment.

Method used

Adopting a new radio access network architecture, managing radio resources through gNB or ng-eNB nodes, realizing multi-carrier aggregation and dynamic provisioning of bandwidth parts, combining the transmission of CSI-RS and SS blocks, optimizing uplink channel mapping and downlink Beam management supports multiple connectivity and random access programs to improve the accuracy of link quality measurement and resource allocation.

Benefits of technology

It improves the resource utilization rate of the backhaul link and the efficiency of channel state information acquisition, enhances the mobility management and service quality of user equipment, and improves the flexibility and reliability of the network.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118972871A_ABST
    Figure CN118972871A_ABST
Patent Text Reader

Abstract

A wireless device communicates with a first network node via a second network node. The wireless device transmits a radio link failure report to a third network node. The radio link failure report indicates a backhaul link failure between the first network node and the second network node.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Divisional application

[0002] This application is a divisional application of the invention application with application date of September 9, 2019, application number 201980058462.X, and title “Return Link Connection Information”.

[0003] CROSS-REFERENCE TO RELATED APPLICATIONS

[0004] This application claims the benefit of U.S. Provisional Application No. 62 / 728,782, filed on September 8, 2018, which is hereby incorporated by reference in its entirety. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Examples of several of the various embodiments of the present disclosure are described herein with reference to the accompanying drawings.

[0006] Figure 1 is a diagram of an example RAN architecture according to aspects of an embodiment of the present disclosure;

[0007] Figure 2A is a diagram of an example user plane protocol stack according to aspects of an embodiment of the present disclosure;

[0008] Figure 2B is a diagram of an example control plane protocol stack according to aspects of an embodiment of the present disclosure;

[0009] Figure 3 is a diagram of an example wireless device and two base stations in accordance with aspects of an embodiment of the present disclosure;

[0010] Figure 4A , Figure 4B , Figure 4C and Figure 4D is an example diagram of uplink and downlink signal transmission according to aspects of an embodiment of the present disclosure;

[0011] Figure 5A is a diagram of an example uplink channel map and example uplink physical signals according to aspects of an embodiment of the present disclosure;

[0012] Figure 5B is a diagram of an example downlink channel map and example downlink physical signals according to aspects of an embodiment of the present disclosure;

[0013] Figure 6 is a diagram depicting an example frame structure in accordance with aspects of an embodiment of the present disclosure;

[0014] Fig. 7A and Figure 7B is a diagram depicting an example set of OFDM subcarriers according to aspects of an embodiment of the present disclosure;

[0015] Figure 8 is a diagram depicting example OFDM radio resources in accordance with aspects of an embodiment of the present disclosure;

[0016] Fig. 9A is a diagram depicting example CSI-RS and / or SS block transmissions in a multi-beam system;

[0017] Fig. 9B is a diagram depicting an example downlink beam management procedure in accordance with aspects of an embodiment of the present disclosure;

[0018] Fig.10 is an example diagram of a configured BWP in accordance with aspects of an embodiment of the present disclosure;

[0019] Fig.11A and Fig. 11B is a diagram of example multiple connectivity according to aspects of an embodiment of the present disclosure;

[0020] Fig.12 is a diagram of an example random access procedure according to aspects of an embodiment of the present disclosure;

[0021] Fig.13 is a structure of an example MAC entity according to aspects of an embodiment of the present disclosure;

[0022] Fig.14 is a diagram of an example RAN architecture according to aspects of an embodiment of the present disclosure;

[0023] Fig.15 is a diagram of example RRC states according to aspects of an embodiment of the present disclosure;

[0024] Fig.16 are diagrams of aspects of example embodiments of the present disclosure;

[0025] Fig.17 are diagrams of aspects of example embodiments of the present disclosure;

[0026] Fig.18 are diagrams of aspects of example embodiments of the present disclosure;

[0027] Fig.19 are diagrams of aspects of example embodiments of the present disclosure;

[0028] Fig. 20 are diagrams of aspects of example embodiments of the present disclosure;

[0029] Fig.21 are diagrams of aspects of example embodiments of the present disclosure;

[0030] Fig. 22 are diagrams of aspects of example embodiments of the present disclosure;

[0031] Fig.23 are diagrams of aspects of example embodiments of the present disclosure;

[0032] Fig.24 are diagrams of aspects of example embodiments of the present disclosure;

[0033] Fig.25 are diagrams of aspects of example embodiments of the present disclosure;

[0034] Fig.26 are diagrams of aspects of example embodiments of the present disclosure;

[0035] Fig. 27 are diagrams of aspects of example embodiments of the present disclosure;

[0036] Fig.28 are diagrams of aspects of example embodiments of the present disclosure;

[0037] Fig.29 are diagrams of aspects of example embodiments of the present disclosure;

[0038] Fig.30 are diagrams of aspects of example embodiments of the present disclosure;

[0039] Fig.31 are diagrams of aspects of example embodiments of the present disclosure;

[0040] Fig.32 are diagrams of aspects of example embodiments of the present disclosure;

[0041] Fig.33 are diagrams of aspects of example embodiments of the present disclosure;

[0042] Fig.34 are diagrams of aspects of example embodiments of the present disclosure;

[0043] Fig.35 are diagrams of aspects of example embodiments of the present disclosure;

[0044] Fig.36 are diagrams of aspects of example embodiments of the present disclosure;

[0045] Fig.37 are diagrams of aspects of example embodiments of the present disclosure;

[0046] Fig.38 are diagrams of aspects of example embodiments of the present disclosure;

[0047] Fig.39 are diagrams of aspects of example embodiments of the present disclosure;

[0048] Fig.40 are diagrams of aspects of example embodiments of the present disclosure;

[0049] Fig.41are diagrams of aspects of example embodiments of the present disclosure;

[0050] Fig.42 are diagrams of aspects of example embodiments of the present disclosure;

[0051] Fig.43 are diagrams of aspects of example embodiments of the present disclosure;

[0052] Fig.44 are diagrams of aspects of example embodiments of the present disclosure;

[0053] Fig.45 is a flow chart of one aspect of an embodiment of the present disclosure;

[0054] Fig.46 is a flow chart of one aspect of an embodiment of the present disclosure. DETAILED DESCRIPTION

[0055] Example embodiments of the present disclosure implement the operation of a wireless system. Embodiments of the technology disclosed herein may be employed in the technical field of multi-carrier communication systems. More specifically, embodiments of the technology disclosed herein may relate to radio access technologies in multi-carrier communication systems.

[0056] The following abbreviations are used throughout this disclosure:

[0057] 3GPP 3rd Generation Partnership Project

[0058] 5GC 5G Core Network

[0059] ACK

[0060] AMF Access and Mobility Management Function

[0061] ARQ Automatic Repeat Request

[0062] AS access layer

[0063] ASIC Application-Specific Integrated Circuit

[0064] BA Bandwidth Adaptation

[0065] BCCH Broadcast Control Channel

[0066] BCH Broadcast Channel

[0067] BPSK Binary Phase Shift Keying

[0068] BWP Bandwidth Part

[0069] CA Carrier Aggregation

[0070] CC Component Carrier

[0071] CCCH Common Control Channel

[0072] CDMA Code Division Multiple Access

[0073] CN Core Network

[0074] CP Cyclic Prefix

[0075] CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplexing

[0076] C-RNTI Cell-Radio Network Temporary Identifier

[0077] CS Configured Scheduling

[0078] CSI Channel State Information

[0079] CSI-RS Channel State Information-Reference Signal

[0080] CQI Channel Quality Indicator

[0081] CSS Common Search Space

[0082] CU Central Unit

[0083] DC Dual Connectivity

[0084] DCCH Dedicated Control Channel

[0085] DCI Downlink Control Information

[0086] DL Downlink

[0087] DL-SCH Downlink Shared Channel

[0088] DM-RS Demodulation Reference Signal

[0089] DRB Data Radio Bearer

[0090] DRX Discontinuous Reception

[0091] DTCH Dedicated Traffic Channel

[0092] DU Distributed Unit

[0093] EPC Evolved Packet Core

[0094] E-UTRA Evolved UMTS Terrestrial Radio Access

[0095] E-UTRAN Evolved Universal Terrestrial Radio Access Network

[0096] FDD Frequency Division Duplex

[0097] FPGA Field Programmable Gate Array

[0098] F1-C F1-Control Plane

[0099] F1-U F1-User Plane

[0100] gNB Next Generation Node B

[0101] HARQ Hybrid Automatic Repeat Request

[0102] HDL Hardware Description Language

[0103] IAB Integrated Access and Backhaul

[0104] IE Information Elements

[0105] IP Internet Protocol

[0106] LCID Logical Channel Identifier

[0107] LTE Long Term Evolution

[0108] MAC Media Access Control

[0109] MCG Master Cell Group

[0110] MCS Modulation and Coding Scheme

[0111] MeNB Leading Node B

[0112] MIB Master Information Block

[0113] MME Mobility Management Entity

[0114] MN Master Node

[0115] NACK Negative Acknowledgement

[0116] NAS Non-Access Layer

[0117] NG CP Next Generation Control Plane

[0118] NGC Next Generation Core

[0119] NG-C NG-Control Plane

[0120] ng-eNB Next Generation Evolved Node B

[0121] NG-U NG-User Plane

[0122] NR New Radio

[0123] NR MAC New Radio MAC

[0124] NR PDCP New Radio PDCP

[0125] NR PHY New Radio Physics

[0126] NR RLC New Radio RLC

[0127] NR RRC New Radio RRC

[0128] NSSAI Network Slice Selection Assistant Information

[0129] O&M Operation and Maintenance

[0130] OFDM Orthogonal Frequency Division Multiplexing

[0131] PBCH Physical Broadcast Channel

[0132] PCC Primary Component Carrier

[0133] PCCH Paging Control Channel

[0134] PCell Primary Community

[0135] PCH Paging Channel

[0136] PDCCH Physical Downlink Control Channel

[0137] PDCP Packet Data Convergence Protocol

[0138] PDSCH Physical Downlink Shared Channel

[0139] PDU Protocol Data Unit

[0140] PHICH Physical HARQ Indicator Channel

[0141] PHY

[0142] PLMN Public Land Mobile Network

[0143] PMI Precoding matrix indicator

[0144] PRACH Physical Random Access Channel

[0145] PRB Physical Resource Block

[0146] PSCell Primary Secondary Cell

[0147] PSS Primary Synchronization Signal

[0148] pTAG Primary Timing Advance Group

[0149] PT-RS Phase Tracking Reference Signal

[0150] PUCCH Physical Uplink Control Channel

[0151] PUSCH Physical Uplink Shared Channel

[0152] QAM Quadrature Amplitude Modulation

[0153] QFI Quality of Service Indicator

[0154] QoS Quality of Service

[0155] QPSK Quadrature Phase Shift Keying

[0156] RA Random Access

[0157] RACH Random Access Channel

[0158] RAN Radio Access Network

[0159] RAT Radio Access Technology

[0160] RA-RNTI Random Access-Radio Network Temporary Identifier

[0161] RB Resource Block

[0162] RBG Resource Block Group

[0163] RI Rank Indicator

[0164] RLC Radio Link Control

[0165] RRC Radio Resource Control

[0166] RS reference signal

[0167] RSRP Reference Signal Received Power

[0168] SCC Secondary Component Carrier

[0169] SCell Secondary Cell

[0170] SCG Secondary Cell Group

[0171] SC-FDMA Single Carrier Frequency Division Multiple Access

[0172] SDAP Service Data Adaptation Protocol

[0173] SDU Service Data Unit

[0174] SeNB Secondary Evolved Node B

[0175] SFN System Frame Number

[0176] S-GW Service Gateway

[0177] SI System Information

[0178] SIB System Information Block

[0179] SMF session management functions

[0180] SN Secondary Node

[0181] SpCell Special Cell

[0182] SRB Signalling Radio Bearer

[0183] SRS Sounding Reference Signal

[0184] SS Sync Signal

[0185] SSS Secondary Sync Signal

[0186] sTAG Secondary Timing Advance Group

[0187] TA Timing Advance

[0188] TAG Timing Advance Group

[0189] TAI Tracking Area Identifier

[0190] TAT Time Alignment Timer

[0191] TB Transfer Block

[0192] TC-RNTI Temporary Cell-Radio Network Temporary Identifier

[0193] TDD Time Division Duplex

[0194] TDMA Time Division Multiple Access

[0195] TTI Transmit Time Interval

[0196] UCI Uplink Control Information

[0197] UE User Equipment

[0198] UL Uplink

[0199] UL-SCH Uplink Shared Channel

[0200] UPF User Plane Function

[0201] UPGW User Plane Gateway

[0202] VHDL VHSIC Hardware Description Language

[0203] Xn-C Xn-Control Plane

[0204] Xn-U Xn-User Plane

[0205] Various physical layer modulation and transmission mechanisms may be used to implement the example embodiments of the present disclosure. Example transmission mechanisms may include, but are not limited to, code division multiple access (CDMA), orthogonal frequency division multiple access (OFDMA), time division multiple access (TDMA), wavelet techniques, etc. Hybrid transmission mechanisms such as TDMA / CDMA and OFDM / CDMA may also be used. Various modulation schemes may be applied to signal transmission in the physical layer. Examples of modulation schemes include, but are not limited to, phase, amplitude, code, combinations of these, etc. Example radio transmission methods may implement quadrature amplitude modulation (QAM) using binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), 16-QAM, 64-QAM, 256-QAM, etc. Physical radio transmission may be enhanced by dynamically or semi-dynamically changing the modulation and coding schemes according to the transmission requirements and radio conditions.

[0206] Figure 1 is an example radio access network (RAN) architecture in accordance with aspects of an embodiment of the present disclosure. As shown in this example, the RAN node may be a next generation node B (gNB) (e.g., 120A, 120B) that provides a new radio (NR) user plane and control plane protocol termination to a first wireless device (e.g., 110A). In an example, the RAN node may be a next generation evolved node B (ng-eNB) (e.g., 124A, 124B) that provides an evolved UMTS terrestrial radio access (E-UTRA) user plane and control plane protocol termination to a second wireless device (e.g., 110B). The first wireless device may communicate with the gNB via a Uu interface. The second wireless device may communicate with the ng-eNB via a Uu interface. In the present disclosure, wireless devices 110A and 110B are structurally similar to wireless device 110. Base stations 120A and / or 120B may be structurally similar to base station 120. The base station 120 may include at least one of a gNB (e.g., 122A and / or 122B), an ng-eNB (e.g., 124A and / or 124B), and the like.

[0207] The gNB or ng-eNB may host functions such as radio resource management and scheduling, IP header compression, encryption and integrity protection of data, selection of the access and mobility management function (AMF) at which the user equipment (UE) attaches, routing of user plane and control plane data, connection setup and release, scheduling and transmission of paging messages (originated from the AMF), scheduling and transmission of system broadcast information (originated from the AMF or operation and maintenance (O&M)), measurements and measurement report configuration, transport layer packet marking in the uplink, session management, network slicing support, Quality of Service (QoS) flow management and mapping to data radio bearers, support for UEs in RRC_INACTIVE state, distribution functions for non-access stratum (NAS) messages, RAN sharing, and dual connectivity or tight interworking between NR and E-UTRA.

[0208] In an instance, one or more gNBs and / or one or more ng-eNBs may be interconnected to each other via an Xn interface. A gNB or ng-eNB may be connected to a 5G core network (5GC) via an NG interface. In an instance, a 5GC may include one or more AMF / User Planning Function (UPF) functions (e.g., 130A or 130B). A gNB or ng-eNB may be connected to the UPF via an NG user plane (NG-U) interface. The NG-U interface may provide delivery of user plane protocol data units (PDUs) (e.g., non-guaranteed delivery) between the RAN node and the UPF. A gNB or ng-eNB may be connected to the AMF via an NG control plane (NG-C) interface. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, transmission of NAS messages, paging, PDU session management, configuration delivery and / or warning message transmission, combinations thereof, and the like.

[0209] In an instance, the UPF may host functions such as an anchor point for intra / inter-radio access technology (RAT) mobility (when applicable), an external PDU session point for interconnection to a data network, packet routing and forwarding, user plane portion of packet inspection and policy rule enforcement, service usage reporting, an uplink classifier to support routing of service flows to the data network, a branch point to support multi-host PDU sessions, QoS processing for the user plane (e.g., packet filtering, gating), uplink (UL) / downlink (DL) rate enforcement, uplink service verification (e.g., service data flow (SDF) to QoS flow mapping), downlink packet buffering and / or downlink data notification triggering.

[0210] In an instance, the AMF may host functions such as NAS signaling termination, NAS signaling security, access layer (AS) security control, core network (CN) inter-node signaling for mobility between 3rd Generation Partnership Project (3GPP) access networks, idle mode UE reachability (e.g., control and execution of paging retransmissions), registration area management, support for intra-system and inter-system mobility, access authentication, access authorization including roaming rights check, mobility management control (subscription and policy), support for network slice and / or session management function (SMF) selection, etc.

[0211] Figure 2Ais an example user plane protocol stack, in which service data adaptation protocol (SDAP) (e.g., 211 and 221), packet data convergence protocol (PDCP) (e.g., 212 and 222), radio link control (RLC) (e.g., 213 and 223), and medium access control (MAC) (e.g., 214 and 224) sublayers and physical (PHY) (e.g., 215 and 225) layers may be terminated in a wireless device (e.g., 110) and a gNB (e.g., 120) on the network side. In an example, the PHY layer provides transport services to higher layers (e.g., MAC, RRC, etc.). In an example, the services and functions of the MAC sublayer may include mapping between logical channels and transport channels, multiplexing of MAC service data units (SDUs) belonging to one or different logical channels into / demultiplexing of transport blocks (TBs) delivered to / from the PHY layer, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA)), priority handling between UEs through dynamic scheduling, priority handling between logical channels of a UE through logical channel prioritization and / or padding. The MAC entity may support one or more parameter sets and / or transmission timings. In an example, mapping restrictions in logical channel prioritization may control which parameter set and / or transmission timing a logical channel may use. In an example, the RLC sublayer may support transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM) transmission modes. The RLC configuration may be based on each logical channel, independent of the parameter set and / or transmission time interval (TTI) duration. In an instance, the automatic repeat request (ARQ) may operate on any parameter set and / or TTI duration configured for the logical channel. In an instance, the services and functions of the PDCP layer for the user plane may include sequence numbering, header compression and decompression, delivery, reordering and duplication detection of user data, PDCP PDU routing (e.g., in the case of split bearers), retransmission, encryption, decryption and integrity protection of PDCP SDUs, PDCP SDU discards, PDCP reconstruction and data recovery of RLC AM, and / or duplication of PDCP PDUs. In an instance, the services and functions of SDAP may include mapping between QoS flows and data radio bearers. In an instance, the services and functions of SDAP may include mapping quality of service indicators (QFIs) in DL and UL packets. In an instance, the protocol entities of SDAP may be configured for separate PDU sessions.

[0212] Figure 2Bis an example control plane protocol stack, in which PDCP (e.g., 233 and 242), RLC (e.g., 234 and 243) and MAC (e.g., 235 and 244) sublayers and PHY (e.g., 236 and 245) layers may be terminated in a wireless device (e.g., 110) and a gNB (e.g., 120) on the network side and perform the above services and functions. In an example, RRC (e.g., 232 and 241) may be terminated in a wireless device and a gNB on the network side. In an example, the services and functions of RRC may include: broadcasting system information related to AS and NAS, paging initiated by 5GC or RAN, establishment, maintenance and release of an RRC connection between a UE and a RAN, security functions including key management, establishment, configuration, maintenance and release of signaling radio bearers (SRBs) and data radio bearers (DRBs), mobility functions, QoS management functions, UE measurement reporting and control of reporting, detection of radio link failure and recovery of radio link failure, and / or delivery of NAS messages from UE to NAS / from NAS to UE. In an example, the NAS control protocol (e.g., 231 and 251) can be terminated in the wireless device and AMF (e.g., 130) on the network side, and can perform functions such as authentication, mobility management between UE and AMF for 3GPP access and non-3GPP access, and session management between UE and SMF for 3GPP access and non-3GPP access.

[0213] In an example, a base station may configure a plurality of logical channels for a wireless device. A logical channel in the plurality of logical channels may correspond to a radio bearer, and the radio bearer may be associated with a QoS requirement. In an example, the base station may configure a logical channel to be mapped to one or more TTIs / parameter sets in a plurality of TTIs / parameter sets. The wireless device may receive downlink control information (DCI) indicating an uplink grant via a physical downlink control channel (PDCCH). In an example, the uplink grant may be for a first TTI / parameter set and may indicate an uplink resource for transmission of a transport block. The base station may configure each of the plurality of logical channels, wherein one or more parameters will be used by a logical channel prioritization procedure at a MAC layer of the wireless device. The one or more parameters may include a priority, a prioritized bit rate, and the like. A logical channel in the plurality of logical channels may correspond to one or more buffers including data associated with the logical channel. The logical channel prioritization procedure may allocate uplink resources to one or more first logical channels and / or one or more MAC control elements (CEs) in the plurality of logical channels. One or more first logical channels may be mapped to a first TTI / parameter set. The MAC layer at the wireless device may multiplex one or more MAC CEs and / or one or more MAC SDUs (e.g., logical channels) in a MAC PDU (e.g., a transport block). In an example, the MAC PDU may include a MAC header, which includes multiple MAC subheaders. A MAC subheader in the multiple MAC subheaders may correspond to a MAC CE or MAC SUD (logical channel) in one or more MAC CEs and / or one or more MAC SDUs. In an example, a MAC CE or a logical channel may be configured with a logical channel identifier (LCID). In an example, the LCID for a logical channel or MAC CE may be fixed / preconfigured. In an example, the LCID for a logical channel or MAC CE may be configured for the wireless device by the base station. The MAC subheader corresponding to the MAC CE or MAC SDU may include an LCID associated with the MAC CE or MAC SDU.

[0214] In an example, a base station may activate and / or deactivate and / or affect one or more processes (e.g., setting the value of one or more parameters of one or more processes or starting and / or stopping one or more timers of one or more processes) at a wireless device by using one or more MAC commands. The one or more MAC commands may include one or more MAC control elements. In an example, one or more processes may include activation and / or deactivation of PDCP packet duplication for one or more radio bearers. The base station may transmit a MAC CE including one or more fields, the value of the field indicating activation and / or deactivation of PDCP duplication for one or more radio bearers. In an example, one or more processes may include channel state information (CSI) transmission on one or more cells. The base station may transmit one or more MAC CEs indicating activation and / or deactivation of CSI transmission on one or more cells. In an example, one or more processes may include activation or deactivation of one or more secondary cells. In an example, the base station may transmit a MACE indicating activation or deactivation of one or more secondary cells. In an example, the base station may transmit one or more MAC CEs indicating starting and / or stopping one or more discontinuous reception (DRX) timers at the wireless device. In an example, the base station may transmit one or more MAC CEs indicating one or more timing advance values ​​for one or more timing advance groups (TAGs).

[0215] Figure 3 1 is a block diagram of a base station (base station 1, 120A and base station 2, 120B) and a wireless device 110. The wireless device may be referred to as a UE. The base station may be referred to as a NB, an eNB, a gNB, and / or an ng-eNB. In an example, the wireless device and / or the base station may act as a relay node. Base station 1, 120A may include at least one communication interface 320A (e.g., a wireless modem, an antenna, a wired modem, etc.), at least one processor 321A, and at least one set of program code instructions 323A, which are stored in a non-transitory memory 322A and can be executed by at least one processor 321A. Base station 2, 120B may include at least one communication interface 320B, at least one processor 321B, and at least one set of program code instructions 323B, which are stored in a non-transitory memory 322B and can be executed by at least one processor 321B.

[0216] A base station may include many sectors, for example: 1, 2, 3, 4 or 6 sectors. A base station may include many cells, for example, ranging from 1 to 50 cells or more. Cells may be classified as, for example, primary cells or secondary cells. A serving cell may provide NAS (non-access layer) mobility information (e.g., tracking area identifier (TAI)) during radio resource control (RRC) connection establishment / reconstruction / switching. A serving cell may provide security input during RRC connection reconstruction / switching. This cell may be referred to as a primary cell (PCell). In the downlink, the carrier corresponding to the PCell may be a DL primary component carrier (PCC), and in the uplink, the carrier may be a UL PCC. Depending on the wireless device capabilities, a secondary cell (SCell) may be configured to form a serving cell set together with the PCell. In the downlink, the carrier corresponding to the SCell may be a downlink secondary component carrier (DL SCC), and in the uplink, the carrier may be an uplink secondary component carrier (UL SCC). The SCell may or may not have an uplink carrier.

[0217] A physical cell ID and a cell index may be assigned to a cell including a downlink carrier and an optional uplink carrier. A carrier (downlink or uplink) may belong to a cell. A cell ID or a cell index may also identify a downlink carrier or an uplink carrier of a cell (depending on the context in which it is used). In the present disclosure, a cell ID may refer to a carrier ID equivalently, and a cell index may be referred to as a carrier index. In an embodiment, a physical cell ID or a cell index may be assigned to a cell. A synchronization signal transmitted on a downlink carrier may be used to determine the cell ID. An RRC message may be used to determine the cell index. For example, when the present disclosure relates to a first physical cell ID of a first downlink carrier, the present disclosure may mean that the first physical cell ID is used for a cell including a first downlink carrier. The same concept may be applied, for example, to carrier activation. When the present disclosure indicates that a first carrier is activated, the present specification may also mean activating a cell including the first carrier.

[0218] The base station may transmit one or more messages (e.g., RRC messages) including multiple configuration parameters of one or more cells to the wireless device. The one or more cells may include at least one primary cell and at least one secondary cell. In an example, the RRC message may be broadcast or unicast to the wireless device. In an example, the configuration parameters may include common parameters and dedicated parameters.

[0219] The services and / or functions of the RRC sublayer may include at least one of the following: broadcasting system information related to AS and NAS; paging initiated by 5GC and / or NG-RAN; establishment, maintenance and / or release of an RRC connection between a wireless device and NG-RAN, which may include at least one of the addition, modification and release of carrier aggregation; or the addition, modification and / or release of dual connectivity in NR or between E-UTRA and NR. The services and / or functions of the RRC sublayer may further include at least one of the following security functions: key management; establishment, configuration, maintenance and / or release of signaling radio bearers (SRBs) and / or data radio bearers (DRBs); mobility functions, which may include at least one of handover (e.g., intra-NR mobility or inter-RAT mobility) and context transfer; or wireless device cell selection and reselection and control of cell selection and reselection. The services and / or functions of the RRC sub-device may further include at least one of the following: QoS management functions; wireless device measurement configuration / reporting; detection of radio link failure and / or recovery of radio link failure; or delivery of NAS messages from the wireless device to a core network entity (e.g., AMF, Mobility Management Entity (MME)) / from a core network entity to the wireless device.

[0220] The RRC sublayer may support the RRC_Idle state, RRC_Inactive state, and / or RRC_Connected state of the wireless device. In the RRC_Idle state, the wireless device may perform at least one of the following: public land mobile network (PLMN) selection; receiving broadcast system information; cell selection / reselection; monitoring / receiving paging of mobile terminated data initiated by 5GC; paging of mobile terminated data area managed by 5GC; or DRX for CN paging configured via NAS. In the RRC_Inactive state, the wireless device may perform at least one of the following: receiving broadcast system information; cell selection / reselection; monitoring / receiving RAN / CN paging initiated by NG-RAN / 5GC; RAN-based Notification Area (RNA) managed by NG-RAN; or DRX for RAN / CN paging configured by NG-RAN / NAS. In the RRC_Idle state of the wireless device, the base station (e.g., NG-RAN) may maintain a 5GC-NG-RAN connection (both C / U planes) for the wireless device; and / or store a UE AS context for the wireless device. In the RRC_Connected state of the wireless device, the base station (e.g., NG-RAN) may perform at least one of the following: establishing a 5GC-NG-RAN connection (both C / U planes) for the wireless device; storing a UE AS context for the wireless device; transmitting / receiving unicast data to / from the wireless device; or network-controlled mobility based on measurement results received from the wireless device. In the RRC_Connected state of the wireless device, the NG-RAN may know the cell to which the wireless device belongs.

[0221] System information (SI) can be divided into minimum SI and other SI. Minimum SI can be broadcast periodically. Minimum SI can include basic information required for initial access and information for obtaining any other SI that is broadcast periodically or provided on demand, i.e., scheduling information. Other SI can be broadcast, or provided in a dedicated manner, or triggered by the network, or upon request of a wireless device. Minimum SI can be transmitted via two different downlink channels using different messages (e.g., MasterInformationBlock and SystemInformationBlockType1). Another SI can be transmitted via SystemInformationBlockType2. For wireless devices in the RRC_Connected state, dedicated RRC signaling can be used for the request and delivery of other SI. For wireless devices in the RRC_Idle state and / or the RRC_Inactive state, the request can trigger a random access procedure.

[0222] The wireless device may report radio access capability information which may be static. The base station may request what capabilities the wireless device reports based on the frequency band information. When the network allows, the wireless device may send a temporary capability restriction request to signal the limited availability of certain capabilities to the base station (e.g., due to hardware sharing, interference, or overheating). The base station may confirm or deny the request. Temporary capability restrictions may be transparent to the 5GC (e.g., static capabilities may be stored in the 5GC).

[0223] When CA is configured, the wireless device may have an RRC connection with the network. During the RRC connection establishment / reestablishment / handover procedures, one serving cell may provide NAS mobility information, and upon RRC connection establishment / handover, one serving cell may provide security input. This cell may be referred to as a PCell. Depending on the capabilities of the wireless device, an SCell may be configured to form a serving cell set together with the PCell. The configured serving cell set for the wireless device may include one PCell and one or more SCells.

[0224] Reconfiguration, addition and removal of SCells may be performed by RRC. RRC may also add, remove or reconfigure SCells for use with the target PCell when switching within NR. When adding a new SCell, dedicated RRC signaling may be used to send all required system information for the SCell, i.e., when in connected mode, the wireless device may not need to obtain broadcast system information directly from the SCell.

[0225] The purpose of the RRC connection reconfiguration procedure may be to modify the RRC connection, (e.g., establish, modify and / or release RBs, perform handovers, set up, modify and / or release measurements, add, modify and / or release SCells and cell groups). As part of the RRC connection reconfiguration procedure, NAS-specific information may be delivered from the network to the wireless device. The RRCConnectionReconfiguration message may be a command to modify the RRC connection. It may convey information for measurement configuration, mobility control, radio resource configuration (e.g., RBs, MAC primary configuration, and physical channel configuration), including any associated dedicated NAS information and security configuration. If the received RRC connection reconfiguration message contains sCellToReleaseList, the wireless device may perform an SCell release. If the received RRC connection reconfiguration message contains sCellToAddModList, the wireless device may perform an SCell addition or modification.

[0226] The RRC connection establishment (or reestablishment, restoration) procedure may be to establish (or reestablish, restore) an RRC connection. The RRC connection establishment procedure may include SRB1 establishment. The RRC connection establishment procedure may be used to transfer initial NAS dedicated information / messages from the wireless device to the E-UTRAN. The RRCConnectionReestablishment message may be used to reestablish SRB1.

[0227] The measurement report procedure may be to transfer the measurement results from the wireless device to the NG-RAN. After successful security activation, the wireless device may initiate the measurement report procedure. The measurement results may be transmitted using a measurement report message.

[0228] The wireless device 110 may include at least one communication interface 310 (e.g., a wireless modem, an antenna, etc.), at least one processor 314, and at least one set of program code instructions 316 stored in a non-transitory memory 315 and executable by the at least one processor 314. The wireless device 110 may additionally include at least one of at least one speaker / microphone 311, at least one keypad 312, at least one display / touchpad 313, at least one power supply 317, at least one global positioning system (GPS) chipset 318, and other peripherals 319.

[0229] The processor 314 of the wireless device 110, the processor 321A of the base station 1 120A, and / or the processor 321B of the base station 2 120B may include at least one of a general purpose processor, a digital signal processor (DSP), a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), and / or other programmable logic devices, discrete gate and / or transistor logic, discrete hardware components, etc. The processor 314 of the wireless device 110, the processor 321A in the base station 1 120A, and / or the processor 321B in the base station 2 120B may perform at least one of signal coding / processing, data processing, power control, input / output processing, and / or any other functionality that may enable the wireless device 110, the base station 1 120A, and / or the base station 2 120B to operate in a wireless environment.

[0230] The processor 314 of the wireless device 110 may be connected to the speaker / microphone 311, the keypad 312, and / or the display / touchpad 313. The processor 314 may receive user input data from the speaker / microphone 311, the keypad 312, and / or the display / touchpad 313, and / or provide user output data to them. The processor 314 in the wireless device 110 may receive power from the power supply 317, and / or may be configured to distribute power to other components in the wireless device 110. The power supply 317 may include at least one of one or more dry cells, solar cells, fuel cells, etc. The processor 314 may be connected to the GPS chipset 318. The GPS chipset 318 may be configured to provide geographic location information of the wireless device 110.

[0231] The processor 314 of the wireless device 110 may be additionally connected to other peripherals 319, which may include one or more software and / or hardware modules that provide additional features and / or functionality. For example, the peripherals 319 may include at least one of an accelerometer, a satellite transceiver, a digital camera, a universal serial bus (USB) port, a hands-free headset, a frequency modulation (FM) radio unit, a media player, an Internet browser, etc.

[0232] The communication interface 320A of base station 1, 120A and / or the communication interface 320B of base station 2, 120B may be configured to communicate with the communication interface 310 of the wireless device 110 via the wireless link 330A and / or the wireless link 330B, respectively. In an example, the communication interface 320A of base station 1, 120A may communicate with the communication interface 320B of base station 2 and other RAN and core network nodes.

[0233] The wireless link 330A and / or the wireless link 330B may include at least one of a bidirectional link and / or a directional link. The communication interface 310 of the wireless device 110 may be configured to communicate with the communication interface 320A of the base station 1 120A and / or with the communication interface 320B of the base station 2 120B. The base station 1 120A and the wireless device 110 and / or the base station 2 120B and the wireless device 110 may be configured to send and receive transport blocks via the wireless link 330A and / or via the wireless link 330B, respectively. The wireless link 330A and / or the wireless link 330B may employ at least one frequency carrier. According to some different aspects of the embodiments, one or more transceivers may be employed. A transceiver may be a device that includes both a transmitter and a receiver. A transceiver may be used in devices such as wireless devices, base stations, relay nodes, etc. In Figure 4A , Figure 4B , Figure 4C , Figure 4D , Figure 6 , Fig. 7A , Figure 7B , Figure 8 Example embodiments of radio technologies implemented in the communication interfaces 310, 320A, 320B and wireless links 330A, 330B are shown in EMBODIMENTS and the associated text.

[0234] In an example, other nodes in the wireless network (eg, AMF, UPF, SMF, etc.) may include one or more communication interfaces, one or more processors, and a memory for storing instructions.

[0235] A node (e.g., a wireless device, a base station, an AMF, an SMF, an UPF, a server, a switch, an antenna, etc.) may include one or more processors and a memory storing instructions that, when executed by one or more processors, cause the node to perform certain processes and / or functions. Example embodiments may implement operations of single carrier and / or multi-carrier communications. Other example embodiments may include a non-transitory tangible computer-readable medium that includes instructions that can be executed by one or more processors to enable operations of single carrier and / or multi-carrier communications. Other example embodiments may include an article of manufacture that includes a non-transitory tangible computer-readable machine-accessible medium on which instructions are encoded for enabling programmable hardware to enable a node to implement operations of single carrier and / or multi-carrier communications. A node may include a processor, a memory, an interface, etc.

[0236] The interface may include at least one of a hardware interface, a firmware interface, a software interface, and / or a combination thereof. The hardware interface may include connectors, wires, electronic devices such as drivers, amplifiers, etc. The software interface may include code stored in a memory device to implement one or more protocols, protocol layers, communication devices, device drivers, combinations thereof, etc. The firmware interface may include a combination of embedded hardware and code stored in and / or in communication with a memory device to implement connections, electronic device operations, one or more protocols, protocol layers, communication drivers, device drivers, hardware operations, combinations thereof, etc.

[0237] Figure 4A , Figure 4B , Figure 4C and Figure 4D is an example diagram of uplink and downlink signal transmission according to aspects of an embodiment of the present disclosure. Figure 4AAn example uplink transmitter for at least one physical channel is shown. A baseband signal representing a physical uplink shared channel may perform one or more functions. The one or more functions may include at least one of: scrambling; modulating scrambled bits to generate complex-valued symbols; mapping complex-valued modulated symbols onto one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generating a complex-valued time-domain single carrier frequency division multiple access (SC-FDMA) or CP-OFDM signal for an antenna port; and the like. In an example, when transform precoding is enabled, an SC-FDMA signal for uplink transmission may be generated. In an example, when transform precoding is not enabled, the uplink transmission may be performed by Figure 4A Generate a CP-OFDM signal for uplink transmission. These functions are shown as examples, and it is contemplated that other mechanisms may be implemented in various embodiments.

[0238] An example structure for modulation and up-conversion of the carrier frequency of a complex-valued SC-FDMA or CP-OFDM baseband signal and / or a complex-valued physical random access channel (PRACH) baseband signal for an antenna port is shown in Figure 4B In. Filtering can be applied before transmission.

[0239] Figure 4C An example structure for downlink transmission is shown in . A baseband signal representing a downlink physical channel may perform one or more functions. The one or more functions may include: scrambling coded bits in a codeword to be transmitted on a physical channel; modulating scrambled bits to generate complex-valued modulation symbols; mapping complex-valued modulation symbols to one or several transmission layers; precoding of complex-valued modulation symbols on layers for transmission on antenna ports; mapping complex-valued modulation symbols for antenna ports to resource elements; generating complex-valued time-domain OFDM signals for antenna ports; and the like. These functions are shown as examples, and it is contemplated that other mechanisms may be implemented in various embodiments.

[0240] In an example, a gNB may transmit a first symbol and a second symbol to a wireless device on an antenna port. The wireless device may infer a channel (e.g., fading gain, multipath delay, etc.) used to communicate the second symbol on the antenna port from the channel used to communicate the first symbol on the antenna port. In an example, the first antenna port and the second antenna port may be quasi-co-located if one or more large-scale properties of a channel on which the first symbol on the first antenna port is communicated may be inferred from a channel on which the second symbol on the second antenna port is communicated. The one or more large-scale properties may include at least one of: delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial receive (Rx) parameters.

[0241] An example modulation and up-conversion of the carrier frequency of a complex-valued OFDM baseband signal for an antenna port is shown in Figure 4D Filtering can be applied before transmission.

[0242] Figure 5A is a diagram of an example uplink channel map and example uplink physical signals. Figure 5B is a diagram of an example downlink channel mapping and downlink physical signals. In an example, the physical layer may provide one or more information transfer services to the MAC and / or one or more higher layers. For example, the physical layer may provide the one or more information transfer services to the MAC via one or more transport channels. The information transfer service may indicate the manner and characteristics of transferring data over the radio interface.

[0243] In an example embodiment, the radio network may include one or more downlink and / or uplink transmission channels. Figure 5A The figure in shows example uplink transport channels including an uplink shared channel (UL-SCH) 501 and a random access channel (RACH) 502. Figure 5B 5 shows an example downlink transport channel including a downlink shared channel (DL-SCH) 511, a paging channel (PCH) 512, and a broadcast channel (BCH) 513. The transport channels may be mapped to one or more corresponding physical channels. For example, UL-SCH 501 may be mapped to a physical uplink shared channel (PUSCH) 503. RACH 502 may be mapped to PRACH 505. DL-SCH 511 and PCH 512 may be mapped to a physical downlink shared channel (PDSCH) 514. BCH 513 may be mapped to a physical broadcast channel (PBCH) 516.

[0244] There may be one or more physical channels without corresponding transport channels. The one or more physical channels may be used for uplink control information (UCI) 509 and / or downlink control information (DCI) 517. For example, a physical uplink control channel (PUCCH) 504 may carry UCI 509 from a UE to a base station. For example, a physical downlink control channel (PDCCH) 515 may carry DCI 517 from a base station to a UE. When UCI 509 and PUSCH 503 transmissions may overlap at least partially in a time slot, NR may support UCI 509 multiplexing in PUSCH 503. UCI 509 may include at least one of CSI, acknowledgment (ACK) / negative acknowledgment (NACK), and / or a scheduling request. DCI 517 on PDCCH 515 may indicate at least one of: one or more downlink assignments and / or one or more uplink scheduling grants.

[0245] In the uplink, the UE may transmit one or more reference signals (RS) to the base station. For example, the one or more RSs may be at least one of a demodulation-RS (DM-RS) 506, a phase tracking-RS (PT-RS) 507, and / or a sounding RS (SRS) 508. In the downlink, the base station may transmit (e.g., unicast, multicast, and / or broadcast) one or more RSs to the UE. For example, the one or more RSs may be at least one of a primary synchronization signal (PSS) / secondary synchronization signal (SSS) 521, a CSI-RS 522, a DM-RS 523, and / or a PT-RS 524.

[0246] In an example, the UE may transmit one or more uplink DM-RS 506 to the base station for channel estimation, for example, for coherent demodulation of one or more uplink physical channels (e.g., PUSCH 503 and / or PUCCH 504). For example, the UE may transmit at least one uplink DM-RS 506 to the base station using PUSCH 503 and / or PUCCH 504, wherein the at least one uplink DM-RS 506 may span the same frequency range as the corresponding physical channel. In an example, the base station may configure the UE using one or more uplink DM-RS configurations. At least one DM-RS configuration may support a front-loaded DM-RS pattern. The front-loaded DM-RS may be mapped on one or more OFDM symbols (e.g., 1 or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may be configured to be transmitted at one or more symbols of PUSCH and / or PUCCH. The base station may semi-statistically configure the UE using the maximum number of front-loaded DM-RS symbols for PUSCH and / or PUCCH. For example, the UE may schedule single-symbol DM-RS and / or double-symbol DM-RS based on the maximum number of front-loaded DM-RS symbols, wherein the base station may configure the UE with one or more additional uplink DM-RS for PUSCH and / or PUCCH. The new radio network may, for example, support a common DM-RS structure for DL ​​and UL at least for CP-OFDM, wherein the DM-RS position, DM-RS pattern and / or scrambling sequence may be the same or different.

[0247] In an example, whether the uplink PT-RS 507 is present may depend on the RRC configuration. For example, the presence of the uplink PT-RS may be UE-specifically configured. For example, the presence and / or pattern of the uplink PT-RS 507 in the scheduled resources may be UE-specifically configured by a combination of RRC signaling and / or an association with one or more parameters (e.g., modulation and coding scheme (MCS)) for other purposes that may be indicated by the DCI. When configured, the dynamic presence of the uplink PT-RS 507 may be associated with one or more DCI parameters including at least the MCS. The radio network may support multiple uplink PT-RS densities defined in the time / frequency domain. When present, the frequency domain density may be associated with at least one configuration of the scheduled bandwidth. The UE may use the same precoding for the DMRS port and the PT-RS port. The number of PT-RS ports may be less than the number of DM-RS ports in the scheduled resources. For example, the uplink PT-RS 507 may be limited to the scheduled time / frequency duration of the UE.

[0248] In an example, the UE may transmit SRS 508 to a base station for channel state estimation to support uplink channel-dependent scheduling and / or link adaptation. For example, the SRS 508 transmitted by the UE may allow the base station to estimate the uplink channel state at one or more different frequencies. The base station scheduler may use the uplink channel state to assign one or more resource blocks of high quality for uplink PUSCH transmission from the UE. The base station may semi-statistically configure the UE using one or more SRS resource sets. For the SRS resource set, the base station may configure the UE using one or more SRS resources. The SRS resource set applicability may be configured by a higher layer (e.g., RRC) parameter. For example, when the higher layer parameter indicates beam management, the SRS resources in each of the one or more SRS resource sets may be transmitted at a certain moment. The UE may transmit one or more SRS resources in different SRS resource sets at the same time. The new radio network may support non-periodic, periodic, and / or semi-persistent SRS transmissions. The UE may transmit SRS resources based on one or more trigger types, wherein the one or more trigger types may include higher layer signaling (e.g., RRC) and / or one or more DCI formats (e.g., at least one DCI format may be used for the UE to select at least one of one or more configured SRS resource sets. SRS trigger type 0 may refer to SRS triggered based on higher layer signaling. SRS trigger type 1 may refer to SRS triggered based on one or more DCI formats. In an example, when PUSCH 503 and SRS 508 are transmitted in the same time slot, the UE may be configured to transmit SRS 508 after transmission of PUSCH 503 and corresponding uplink DM-RS 506.

[0249] In an instance, the base station may semi-statistically configure the UE using one or more SRS configuration parameters indicating at least one of: an SRS resource configuration identifier, a number of SRS ports, a time domain behavior of the SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS), a slot (mini-slot and / or subframe) level periodicity and / or offset of periodic and / or aperiodic SRS resources, a number of OFDM symbols in an SRS resource, a starting OFDM symbol for an SRS resource, an SRS bandwidth, a frequency hopping bandwidth, a cyclic shift, and / or an SRS sequence ID.

[0250] In an example, in the time domain, the SS / PBCH block may include one or more OFDM symbols within the SS / PBCH block (e.g., 4 OFDM symbols numbered in increasing order from 0 to 3). The SS / PBCH block may include a PSS / SSS 521 and a PBCH 516. In an example, in the frequency domain, the SS / PBCH block may include one or more consecutive subcarriers within the SS / PBCH block (e.g., 240 consecutive subcarriers, the subcarriers are numbered in increasing order from 0 to 239). For example, the PSS / SSS 521 may occupy 1 OFDM symbol and 127 subcarriers. For example, the PBCH 516 may span 3 OFDM symbols and 240 subcarriers. The UE may assume that one or more SS / PBCH blocks transmitted using the same block index may be quasi-co-located, for example, with respect to Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. The UE may not assume quasi-co-location of other SS / PBCH block transmissions. The periodicity of the SS / PBCH blocks may be configured by the radio network (e.g., via RRC signaling), and the subcarrier spacing may determine the one or more time locations at which the SS / PBCH blocks may be sent. In an example, the UE may assume a band-specific subcarrier spacing for the SS / PBCH blocks unless the radio network has configured the UE to assume a different subcarrier spacing.

[0251] In an example, a downlink CSI-RS 522 may be used for the UE to obtain channel state information. The radio network may support periodic, aperiodic and / or semi-persistent transmission of the downlink CSI-RS 522. For example, the base station may semi-statistically configure and / or reconfigure the UE using the periodic transmission of the downlink CSI-RS 522. The configured CSI-RS resources may be activated / deactivated. For semi-persistent transmission, the activation and / or deactivation of the CSI-RS resources may be dynamically triggered. In an example, the CSI-RS configuration may include one or more parameters indicating the number of at least antenna ports. For example, the base station may configure the UE using 32 ports. The base station may semi-statistically configure the UE using one or more CSI-RS resource sets. One or more CSI-RS resources may be allocated to one or more UEs from one or more CSI-RS resource sets. For example, the base station may semi-statistically configure one or more parameters indicating CSI RS resource mapping, such as the time domain position of one or more CSI-RS resources, the bandwidth of the CSI-RS resources, and / or periodicity. In an example, the UE may be configured to use the same OFDM symbol for the downlink CSI-RS 522 and the control resource set (core set) when the downlink CSI-RS 522 and the core set are quasi-co-located in space and the resource elements associated with the downlink CSI-RS 522 are outside the PRB configured for the core set. In an example, the UE may be configured to use the same OFDM symbol for the downlink CSI-RS 522 and the SSB / PBCH when the downlink CSI-RS 522 and the SSB / PBCH are quasi-co-located in space and the resource elements associated with the downlink CSI-RS 522 are outside the PRB configured for the SSB / PBCH.

[0252] In an example, the UE may transmit one or more downlink DM-RS 523 to a base station for channel estimation, e.g., for coherent demodulation of one or more downlink physical channels (e.g., PDSCH 514). For example, the radio network may support one or more variable and / or configurable DM-RS patterns for data demodulation. At least one downlink DM-RS configuration may support a front-load DM-RS pattern. The front-load DM-RS may be mapped on one or more OFDM symbols (e.g., 1 or 2 adjacent OFDM symbols). The base station may semi-statistically configure the UE with a maximum number of front-load DM-RS symbols for PDSCH 514. For example, the DM-RS configuration may support one or more DM-RS ports. For example, for single-user-MIMO, the DM-RS configuration may support at least 8 orthogonal downlink DM-RS ports. For example, for multi-user-MIMO, the DM-RS configuration may support 12 orthogonal downlink DM-RS ports. The radio network may support a common DM-RS structure for DL ​​and UL, for example, at least for CP-OFDM, where the DM-RS positions, DM-RS patterns and / or scrambling sequences may be the same or different.

[0253] In an example, whether a downlink PT-RS 524 is present may depend on an RRC configuration. For example, the presence of a downlink PT-RS 524 may be UE-specifically configured. For example, the presence and / or pattern of a downlink PT-RS 524 in a scheduled resource may be UE-specifically configured by a combination of RRC signaling and / or an association with one or more parameters (e.g., MCS) for other purposes that may be indicated by a DCI. When configured, the dynamic presence of a downlink PT-RS 524 may be associated with one or more DCI parameters including at least an MCS. A radio network may support multiple PT-RS densities defined in a time / frequency domain. When present, a frequency domain density may be associated with at least one configuration of a scheduled bandwidth. The UE may use the same precoding for a DMRS port and a PT-RS port. The number of PT-RS ports may be less than the number of DM-RS ports in the scheduled resources. For example, a downlink PT-RS 524 may be limited to a scheduled time / frequency duration of the UE.

[0254] Figure 6 is a diagram depicting an example frame structure of a carrier according to aspects of an embodiment of the present disclosure. A multi-carrier OFDM communication system may contain one or more carriers, for example, ranging from 1 to 32 carriers in the case of carrier aggregation, or ranging from 1 to 64 carriers in the case of dual connectivity. Different radio frame structures (e.g., for FDD and for TDD duplexing schemes) may be supported. Figure 6An example frame structure is shown. Downlink and uplink transmissions may be organized into radio frames 601. In this example, the radio frame duration is 10 milliseconds. In this example, the 10 millisecond radio frame 601 may be divided into ten equally sized subframes 602 having a duration of 1 millisecond. One or more subframes may include one or more time slots (e.g., time slots 603 and 605), depending on the subcarrier spacing and / or CP length. For example, subframes with 15kHz, 30kHz, 60kHz, 120kHz, 240kHz, and 480kHz subcarrier spacing may include one, two, four, eight, sixteen, and thirty-two time slots, respectively. Figure 6 In the embodiment of the present invention, a subframe can be divided into two equally sized time slots 603 with a duration of 0.5 milliseconds. For example, at an interval of 10 milliseconds, 10 subframes can be used for downlink transmission and 10 subframes can be used for uplink transmission. Uplink and downlink transmissions can be split in the frequency domain. One or more time slots can contain multiple OFDM symbols 604. The number of OFDM symbols 604 in a time slot 605 can depend on the cyclic prefix length. For example, for the same subcarrier spacing of up to 480kHz with normal CP, a time slot can be 14 OFDM symbols. For the same subcarrier spacing of 60kHz with extended CP, a time slot can be 12 OFDM symbols. A time slot can contain a downlink, an uplink, or a downlink part and an uplink part, etc.

[0255] Fig. 7A700. The diagram depicts an example set of OFDM subcarriers according to aspects of an embodiment of the present disclosure. In an example, a gNB may communicate with a wireless device using a carrier having an example channel bandwidth 700. One or more arrows in the diagram may depict subcarriers in a multi-carrier OFDM system. The OFDM system may use, for example, OFDM technology, SC-FDMA technology, and the like. In an example, arrow 701 shows a subcarrier transmitting an information symbol. In an example, a subcarrier spacing 702 between two consecutive subcarriers in a carrier may be any one of 15KHz, 30KHz, 60KHz, 120KHz, 240KHz, and the like. In an example, different subcarrier spacings may correspond to different transmission parameter sets. In an example, a transmission parameter set may include at least: a parameter set index; a value of a subcarrier spacing; a type of cyclic prefix (CP). In an example, a gNB may transmit to / receive from a UE on several subcarriers 703 in a carrier. In an example, due to guard bands 704 and 705, the bandwidth occupied by several subcarriers 703 (transmission bandwidth) may be less than the channel bandwidth 700 of the carrier. In an example, guard bands 704 and 705 may be used to reduce interference to and from one or more adjacent carriers. The number of subcarriers in a carrier (transmit bandwidth) may depend on the channel bandwidth and subcarrier spacing of the carrier. For example, for a carrier with a 20 MHz channel bandwidth and a 15 KHz subcarrier spacing, the transmit bandwidth may be the number of 1024 subcarriers.

[0256] In an example, when CA configuration is utilized, the gNB and wireless device may communicate with multiple CCs. In an example, if CA is supported, different component carriers may have different bandwidths and / or subcarrier spacings. In an example, the gNB may transmit a first type of service to the UE on a first component carrier. The gNB may transmit a second type of service to the UE on a second component carrier. Different types of services may have different service requirements (e.g., data rate, latency, reliability), which may be suitable for transmission via different component carriers with different subcarrier spacings and / or bandwidths. Figure 7B An example embodiment is shown. The first component carrier may include a first number of subcarriers 706 having a first subcarrier spacing 709. The second component carrier may include a second number of subcarriers 707 having a second subcarrier spacing 710. The third component carrier may include a third number of subcarriers 708 having a third subcarrier spacing 711. The carriers in the multi-carrier OFDM communication system may be contiguous carriers, non-contiguous carriers, or a combination of contiguous and non-contiguous carriers.

[0257] Figure 8801. In an example, a carrier may have a transmission bandwidth 801. In an example, a resource grid may be in a frequency domain 802 and a time domain 803 structure. In an example, a resource grid may include a first number of OFDM symbols and a second number of resource blocks in a subframe, starting from a common resource block for transmitting a parameter set and a carrier indicated by higher layer signaling (e.g., RRC signaling). In an example, in a resource grid, a resource unit identified by a subcarrier index and a symbol index may be a resource element 805. In an example, depending on a parameter set associated with a carrier, a subframe may include a first number of OFDM symbols 807. For example, when the subcarrier spacing of the parameter set of the carrier is 15KHz, the subframe may have 14 OFDM symbols for the carrier. When the subcarrier spacing of the parameter set is 30KHz, the subframe may have 28 OFDM symbols. When the subcarrier spacing of the parameter set is 60Khz, the subframe may have 56 OFDM symbols, etc. In an example, the second number of resource blocks included in the resource grid of the carrier may depend on the bandwidth and the numerology of the carrier.

[0258] like Figure 8 As shown, resource block 806 may include 12 subcarriers. In an example, multiple resource blocks may be grouped into resource block groups (RBGs) 804. In an example, the size of the RBG may depend on at least one of: an RRC message indicating an RBG size configuration; the size of the carrier bandwidth; or the size of a bandwidth portion of the carrier. In an example, the carrier may include multiple bandwidth portions. A first bandwidth portion of the carrier may have a different frequency location and / or bandwidth than a second bandwidth portion of the carrier.

[0259] In an example, the gNB may transmit downlink control information including downlink or uplink resource block assignments to the wireless device. The base station may transmit to or receive from the wireless device a data packet (e.g., a transport block) scheduled and transmitted via one or more resource blocks and one or more time slots according to the downlink control information and / or parameters in one or more RRC messages. In an example, a start symbol of a first time slot relative to the one or more time slots may be indicated to the wireless device. In an example, the gNB may transmit to or receive from the wireless device a data packet scheduled on one or more RBGs and one or more time slots.

[0260] In an example, the gNB may transmit downlink control information including a downlink assignment to the wireless device via one or more PDCCHs. The downlink assignment may include parameters indicating at least a modulation and coding format; a resource allocation; and / or HARQ information related to the DL-SCH. In an example, the resource allocation may include parameters of a resource block allocation; and / or a time slot allocation. In an example, the gNB may dynamically allocate resources to the wireless device via a cell-radio network temporary identifier (C-RNTI) on one or more PDCCHs. The wireless device may monitor the one or more PDCCHs to find possible allocations when its downlink reception is enabled. Upon successful detection of the one or more PDCCHs, the wireless device may receive one or more downlink data packets on one or more PDSCHs scheduled by the one or more PDCCHs.

[0261] In an example, the gNB may allocate configured scheduling (CS) resources for downlink transmission to the wireless device. The gNB may transmit one or more RRC messages indicating the periodicity of the CS grant. The gNB may transmit the DCI via a PDCCH addressed to a configured scheduling-RNTI (CS-RNTI) that activates the CS resources. The DCI may include a parameter indicating that the downlink grant is a CS grant. The CS grant may be implicitly reused according to the periodicity defined by the one or more RRC messages until deactivated.

[0262] In an example, the gNB may transmit downlink control information including an uplink grant to the wireless device via one or more PDCCHs. The uplink grant may include parameters indicating at least a modulation and coding format; a resource allocation; and / or HARQ information related to the UL-SCH. In an example, the resource allocation may include parameters for resource block allocation; and / or time slot allocation. In an example, the gNB may dynamically allocate resources to the wireless device via the C-RNTI on one or more PDCCHs. The wireless device may monitor the one or more PDCCHs for possible resource allocations. Upon successful detection of the one or more PDCCHs, the wireless device may transmit one or more uplink data packets via one or more PUSCHs scheduled by the one or more PDCCHs.

[0263] In an example, the gNB may allocate CS resources for uplink data transmission to the wireless device. The gNB may transmit one or more RRC messages indicating the periodicity of the CS grant. The gNB may transmit a DCI via a PDCCH addressed to the CS-RNTI that activated the CS resources. The DCI may include a parameter indicating that the uplink grant is a CS grant. The CS grant may be implicitly reused according to the periodicity defined by the one or more RRC messages until deactivated.

[0264] In an example, a base station may transmit DCI / control signaling via PDCCH. DCI may adopt a format in a variety of formats. DCI may include downlink and / or uplink scheduling information (e.g., resource allocation information, HARQ related parameters, MCS), a request for CSI (e.g., aperiodic CQI report), a request for SRS, an uplink power control command for one or more cells, one or more timing information (e.g., TB transmission / reception timing, HARQ feedback timing, etc.), etc. In an example, DCI may indicate an uplink grant including transmission parameters for one or more transport blocks. In an example, DCI may indicate a downlink assignment indicating parameters for receiving one or more transport blocks. In an example, a base station may use DCI to initiate contention-free random access at a wireless device. In an example, a base station may transmit a DCI including a slot format indicator (SFI) that notifies a slot format. In an example, a base station may transmit a DCI including a preemptive indication notifying one or more PRBs and / or one or more OFDM symbols, wherein the UE may assume that there is no transmission intended for the UE. In an example, a base station may transmit a DCI for group power control of a PUCCH or PUSCH or SRS. In an example, the DCI may correspond to an RNTI. In an example, a wireless device may obtain an RNTI (e.g., C-RNTI) in response to completing initial access. In an example, a base station may configure an RNTI (e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI) for wireless. In an example, a wireless device may calculate an RNTI (e.g., a wireless device may calculate an RA-RNTI based on resources used to transmit a preamble). In an example, the RNTI may have a preconfigured value (e.g., P-RNTI or SI-RNTI). In an example, a wireless device may monitor a group common search space, which may be used by a base station to transmit a DCI intended for a group of UEs. In an example, the group-common DCI may correspond to a RNTI configured commonly for a group of UEs. In an example, the wireless device may monitor a UE-specific search space. In an example, the UE-specific DCI may correspond to a RNTI configured for the wireless device.

[0265] The NR system may support single beam operation and / or multi-beam operation. In multi-beam operation, the base station may perform downlink beam sweeping to provide coverage for a common control channel and / or downlink SS block that may include at least PSS, SSS and / or PBCH. The wireless device may use one or more RSs to measure the quality of the beam to the link. One or more SS blocks, or one or more CSI-RS resources associated with a CSI-RS resource index (CRI), or one or more DM-RSs of the PBCH may be used as RSs for measuring the quality of the beam to the link. The quality of the beam to the link may be defined as a reference signal received power (RSRP) value, or a reference signal received quality (RSRQ) value, and / or a CSI value measured on the RS resource. The base station may indicate whether the RS resource used to measure the quality of the beam to the link is quasi-co-located (QCL) with the DM-RS of the control channel. When the channel characteristics of the transmission from the RS to the wireless device and the transmission from the control channel to the wireless device are similar or identical under the configured criteria, the RS resources and DM-RS of the control channel may be referred to as QCL. In multi-beam operation, a wireless device may perform uplink beam sweeping to access a cell.

[0266] In an example, a wireless device may be configured to simultaneously monitor the PDCCH on one or more beam pairs of links depending on the capabilities of the wireless device. This can increase robustness against beam pair link blocking. A base station may transmit one or more messages to configure a wireless device to monitor the PDCCH on one or more beam pairs of links in different PDCCH OFDM symbols. For example, a base station may transmit higher layer signaling (e.g., RRC signaling) or MAC CE, which includes parameters for the Rx beam settings of a wireless device for monitoring the PDCCH on one or more beam pairs of links. A base station may transmit one or more DL RS antenna ports (e.g., cell-specific CSI-RS, or wireless device-specific CSI-RS, or SS blocks, or PBCH with or without DM-RS of PBCH) and an indication of the spatial QCL assumption between one or more DL RS antenna ports for demodulating a DL control channel. Signaling for beam indication for PDCCH may be MAC CE signaling, or RRC signaling, or DCI signaling, or a standardized transparent and / or implicit method, and a combination of these signaling methods.

[0267] For reception of unicast DL data channels, the base station may indicate spatial QCL parameters between one or more DL RS antenna ports and one or more DM-RS antenna ports of the DL data channel. The base station may transmit a DCI (e.g., a downlink grant) including information indicating the RS antenna ports. The information may indicate the RS antenna ports that may be QCLed with the DM-RS antenna ports. Different sets of DM-RS antenna ports for DL ​​data channels may be indicated as different sets of QCLed with the RS antenna ports.

[0268] Fig. 9A is an example of beam sweeping in a DL channel. In the RRC_INACTIVE state or the RRC_IDLE state, the wireless device may assume that the SS blocks form an SS burst 940 and an SS burst set 950. The SS burst set 950 may have a given periodicity. For example, in multi-beam operation, the base station 120 may transmit SS blocks in multiple beams, thereby forming an SS burst 940 together. One or more SS blocks may be transmitted on one beam. If multiple SS bursts 940 are transmitted with multiple beams, then the SS bursts together may form an SS burst set 950.

[0269] The wireless device may additionally use CSI-RS in multi-beam operation to estimate the beam quality of the link between the wireless device and the base station. A beam may be associated with a CSI-RS. For example, the wireless device may report a beam index as indicated in the CRI for downlink beam selection and associated with the RSRP value of the beam based on an RSRP measurement report on the CSI-RS. The CSI-RS may be transmitted on a CSI-RS resource that includes at least one of one or more antenna ports, one or more time or frequency radio resources. The CSI-RS resources may be configured in a cell-specific manner by common RRC signaling or in a wireless device-specific manner by dedicated RRC signaling and / or L1 / L2 signaling. Multiple wireless devices covered by a cell may measure cell-specific CSI-RS resources. A dedicated subset of wireless devices covered by a cell may measure wireless device-specific CSI-RS resources.

[0270] The CSI-RS resources may be transmitted periodically or using aperiodic transmission or using multiple or semi-continuous transmission. Fig. 9A In periodic transmission in the time domain, the base station 120 may periodically transmit the configured CSI-RS resources 940 using the configured periodicity. In aperiodic transmission, the configured CSI-RS resources may be transmitted in a dedicated time slot. In multiple or semi-continuous transmission, the configured CSI-RS resources may be transmitted within a configured period. The beam used for CSI-RS transmission may have a different beamwidth than the beam used for SS block transmission.

[0271] Fig. 9B is an example of a beam management procedure in an example new radio network. The base station 120 and / or the wireless device 110 may perform a downlink L1 / L2 beam management procedure. One or more of the following downlink L1 / L2 beam management procedures may be performed within one or more wireless devices 110 and one or more base stations 120. In an example, the P-1 procedure 910 may be used to enable the wireless device 110 to measure one or more transmit (Tx) beams associated with the base station 120 to support the selection of a first set of Tx beams associated with the base station 120 and a first set of Rx beams associated with the wireless device 110. In order to perform beamforming at the base station 120, the base station 120 may sweep a set of different TX beams. In order to perform beamforming at the wireless device 110, the wireless device 110 may sweep a set of different Rx beams. In an example, the P-2 procedure 920 may be used to enable the wireless device 110 to measure one or more Tx beams associated with the base station 120 to possibly change the first set of Tx beams associated with the base station 120. The P-2 procedure 920 may be performed on a potentially smaller set of beams for beam optimization than in the P-1 procedure 910. The P-2 procedure 920 may be a special case of the P-1 procedure 910. In an example, the P-3 procedure 930 may be used to enable the wireless device 110 to measure at least one Tx beam associated with the base station 120 to change a first set of Rx beams associated with the wireless device 110.

[0272] The wireless device 110 may transmit one or more beam management reports to the base station 120. In the one or more beam management reports, the wireless device 110 may indicate some beam pair quality parameters, including at least: one or more beam identities of a subset of configured beams; RSRP; precoding matrix indicator (PMI) / channel quality indicator (CQI) / rank indicator (RI). Based on the one or more beam management reports, the base station 120 may transmit a signal to the wireless device 110 indicating that the one or more beam pair links are one or more service beams. The base station 120 may transmit PDCCH and PDSCH for the wireless device 110 using one or more service beams.

[0273] In an example embodiment, the new radio network may support bandwidth adaptation (BA). In an example, the receive and / or transmit bandwidth configured by a UE employing BA may not be large. For example, the receive and / or transmit bandwidth may not be as large as the bandwidth of the cell. The receive and / or transmit bandwidth may be adjustable. For example, the UE may change the receive and / or transmit bandwidth, for example, shrink during low activity periods to save power. For example, the UE may change the location of the receive and / or transmit bandwidth in the frequency domain, for example, to increase scheduling flexibility. For example, the UE may change the subcarrier spacing, for example, to allow different services.

[0274] In an example embodiment, a subset of the total cell bandwidth of a cell may be referred to as a bandwidth part (BWP). The base station may configure the UE with one or more BWPs to implement BA. For example, the base station may indicate to the UE which of the one or more (configured) BWPs is the active BWP.

[0275] Fig.10 : is an example diagram of 3 configured BWPs: BWP1 (1010 and 1050) with a width of 40MHz and a subcarrier spacing of 15kHz; BWP2 (1020 and 1040) with a width of 10MHz and a subcarrier spacing of 15kHz; BWP3 1030 with a width of 20MHz and a subcarrier spacing of 60kHz.

[0276] In an instance, a UE configured to operate in one or more BWPs of a cell may be configured by one or more higher layers (e.g., an RRC layer) of the cell with a set of one or more BWPs (e.g., up to four BWPs) for the UE (DL BWP set) to receive in a DL bandwidth via at least one parameter DL-BWP, and a set of one or more BWPs (e.g., up to four BWPs) for the UE (UL BWP set) to transmit in a UL bandwidth via at least one parameter UL-BWP for the cell.

[0277] To enable BA on PCell, the base station may configure the UE with one or more UL and DL BWP pairs. To enable BA on SCell (e.g., in case of CA), the base station may configure the UE with at least one or more DL BWPs (e.g., possibly none in UL).

[0278] In an example, the initial active DL BWP may be defined by at least one of the position and number of consecutive PRBs of a control resource set for at least one common search space, a subcarrier spacing, or a cyclic prefix. For operation on a PCell, one or more higher layer parameters may indicate at least one initial UL BWP for a random access procedure. If the UE is configured with a secondary carrier on a primary cell, the UE may be configured with an initial BWP for a random access procedure on the secondary carrier.

[0279] In an example, for unpaired spectrum operation, the UE may expect that the center frequency of the DL BWP may be the same as the center frequency of the UL BWP.

[0280] For example, for a DL BWP or ULBWP in a set of one or more DL BWPs or one or more UL BWPs, respectively, the base station can semi-statistically configure the UE for the cell using one or more parameters, wherein the one or more parameters indicate at least one of the following: subcarrier spacing; cyclic prefix; the number of consecutive PRBs; an index in a set of one or more DL BWPs and / or one or more UL BWPs; a link between a DL BWP and an UL BWP from a set of configured DL BWPs and UL BWPs; DCI detection of PDSCH reception timing; PDSCH reception of HARQ-ACK transmission timing value; DCI detection of PUSCH transmission timing value; and an offset of the first PRB of the DL bandwidth or the UL bandwidth relative to the first PRB of the bandwidth, respectively.

[0281] In an example, for a DL BWP in a set of one or more DL BWPs on a PCell, the base station may configure the UE with one or more control resource sets for at least one type of common search space and / or one UE-specific search space. For example, the base station may not configure the UE without a common search space on a PCell or on a PSCell in an active DL BWP.

[0282] For a UL BWP in a set of one or more UL BWPs, the base station may configure the UE with one or more resource sets for one or more PUCCH transmissions.

[0283] In an example, if the DCI includes a BWP indicator field, the BWP indicator field value may indicate an active DL BWP from a configured DL BWP set for one or more DL receptions. If the DCI includes a BWP indicator field, the BWP indicator field value may indicate an active UL BWP from a configured UL BWP set for one or more UL transmissions.

[0284] In an example, for PCell, the base station may semi-statistically configure the UE with a default DL BWP among the configured DL BWPs. If a default DL BWP is not provided to the UE, the default BWP may be the initial active DL BWP.

[0285] In an example, the base station may configure the UE with a timer value for the PCell. For example, when the UE detects a DCI indicating an active DL BWP other than the default DL BWP for paired spectrum operation or when the UE detects a DCI indicating an active DL BWP or UL BWP other than the default DL BWP for unpaired spectrum operation, the UE may start a timer called a BWP inactivity timer. If the UE does not detect a DCI during an interval for paired spectrum operation or for unpaired spectrum operation, the UE may increment the timer by an interval of a first value (e.g., the first value may be 1 millisecond or 0.5 milliseconds). In an example, the timer may expire when the timer is equal to the timer value. When the timer expires, the UE may switch from the active DL BWP to the default DL BWP.

[0286] In an example, the base station may semi-statistically configure the UE with one or more BWPs. The UE may switch the active BWP from the first BWP to the second BWP (e.g., the second BWP may be the default BWP) in response to receiving a DCI indicating that the second BWP is the active BWP and / or in response to expiration of a BWP inactivity timer. For example, Fig.10 1040 and 1050). BWP2 (1020 and 1040) may be the default BWP. BWP1 (1010) may be the initial active BWP. In an example, the UE may switch the active BWP from BWP1 1010 to BWP2 1020 in response to expiration of a BWP inactivity timer. For example, the UE may switch the active BWP from BWP2 1020 to BWP3 1030 in response to receiving a DCI indicating BWP3 1030 as the active BWP. Switching the active BWP from BWP3 1030 to BWP2 1040 and / or from BWP2 1040 to BWP1 1050 may be in response to receiving a DCI indicating an active BWP and / or in response to expiration of a BWP inactivity timer.

[0287] In an example, if the UE is configured with a default DL BWP and timer value among the configured DL BWPs for the secondary cell, the UE procedure on the secondary cell may be the same as the UE procedure on the primary cell using the timer value for the secondary cell and the default DL BWP for the secondary cell.

[0288] In an example, if the base station configures the UE with a first active DL BWP and a first active UL BWP on a secondary cell or carrier, the UE may use the indicated DL BWP and the indicated UL BWP on the secondary cell as the respective first active DL BWP and first active UL BWP on the secondary cell or carrier.

[0289] Fig.11A and Fig. 11B Packet flows employing multiple connectivity (eg, dual connectivity, multiple connectivity, tight interworking, etc.) are shown. Fig.11A is an example diagram of a protocol structure of a wireless device 110 (eg, UE) with CA and / or multiple connectivity according to aspects of the embodiments. Fig. 11B 1 is an example diagram of a protocol structure of multiple base stations with CA and / or multiple connectivity according to aspects of an embodiment. The multiple base stations may include a master node MN 1130 (e.g., a master node, a master base station, a master gNB, a master eNB, etc.) and a secondary node SN 1150 (e.g., a secondary node, a secondary base station, a secondary gNB, a secondary eNB, etc.). The master node 1130 and the secondary node 1150 may work together to communicate with the wireless device 110.

[0290] When multiple connections are configured for the wireless device 110, the wireless device 110 that can support multiple receive / transmit functions in the RRC connection state can be configured to utilize radio resources provided by multiple schedulers of multiple base stations. Multiple base stations can be interconnected through non-ideal or ideal backhauls (e.g., Xn interface, X2 interface, etc.). The base stations involved in the multiple connectivity for a certain wireless device can perform at least one of two different roles: the base station can act as a primary base station or a secondary base station. In multiple connectivity, the wireless device can be connected to a primary base station and one or more secondary base stations. In an example, a primary base station (e.g., MN 1130) can provide a wireless device (e.g., wireless device 110) with a primary cell group (MCG) including a primary cell and / or one or more secondary cells. A secondary base station (e.g., SN 1150) can provide a secondary cell group (SCG) including a primary secondary cell (PSCell) and / or one or more secondary cells for a wireless device (e.g., wireless device 110).

[0291] In multiple connectivity, the radio protocol architecture adopted by the bearer may depend on how the bearer is set up. In an example, three different types of bearer setting options can be supported: MCG bearer, SCG bearer and / or split bearer. The wireless device can receive / transmit packets of the MCG bearer via one or more cells of the MCG, and / or can receive / transmit packets of the SCG bearer via one or more cells of the SCG. Multiple connectivity can also be described as having at least one bearer that is configured to use radio resources provided by a secondary base station. In some example embodiments, multiple connectivity may or may not be configured / implemented.

[0292] In an example, a wireless device (e.g., wireless device 110) may: transmit and / or receive packets of an MCG bearer via an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1111), an RLC layer (e.g., MN RLC 1114), and a MAC layer (e.g., MN MAC 1118); transmit and / or receive packets of a split bearer via an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1112), one of a primary or secondary RLC layer (e.g., MN RLC 1115, SN RLC 1116), and one of a primary or secondary MAC layer (e.g., MN MAC 1118, SN MAC 1119); and / or transmit and / or receive packets of a split bearer via an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1113), an RLC layer (e.g., SN RLC 1117), and a MAC layer (e.g., MN MAC 1119) to transmit and / or receive packets carried by the SCG.

[0293] In an example, a primary base station (e.g., MN 1130) and / or a secondary base station (e.g., SN 1150) may: transmit / receive packets carried by the MCG via a primary or secondary node SDAP layer (e.g., SDAP 1120, SDAP 1140), a primary or secondary node PDCP layer (e.g., NR PDCP 1121, NR PDCP 1142), a primary node RLC layer (e.g., MN RLC 1124, MN RLC 1125), and a primary node MAC layer (e.g., MN MAC 1128); transmit / receive packets carried by the MCG via a primary or secondary node SDAP layer (e.g., SDAP 1120, SDAP 1140), a primary or secondary node PDCP layer (e.g., NR PDCP 1122, NR PDCP 1143), a secondary node RLC layer (e.g., SN RLC 1146, SN RLC 1147), and a secondary node MAC layer (e.g., SN MAC 1128); 1148) transmits / receives packets carried by the SCG; transmits / receives packets carried by the split bearer via the primary or secondary node SDAP layer (e.g., SDAP 1120, SDAP 1140), the primary or secondary node PDCP layer (e.g., NR PDCP 1123, NR PDCP 1141), the primary or secondary node RLC layer (e.g., MN RLC 1126, SN RLC 1144, SN RLC 1145, MN RLC 1127) and the primary or secondary node MAC layer (e.g., MN MAC 1128, SN MAC 1148).

[0294] In multiple connectivity, the wireless device may configure multiple MAC entities: one MAC entity for the primary base station (e.g., MN MAC 1118), and other MAC entities for the secondary base stations (e.g., SN MAC 1119). In multiple connectivity, the configured service cell set for the wireless device may include two subsets: an MCG including service cells of the primary base station, and an SCG including service cells of the secondary base stations. For SCG, one or more of the following configurations may apply: at least one cell of the SCG has a configured UL CC, and at least one cell of the SCG, referred to as a primary secondary cell (PSCell, PCell of the SCG, or sometimes referred to as PCell) is configured with PUCCH resources; when the SCG is configured, there may be at least one SCG bearer or one split bearer; after a physical layer problem or a random access problem is detected on the PSCell, or after a number of NR RLC retransmissions associated with the SCG have been reached, or after an access problem is detected on the PSCell during SCG addition or SCG change: the RRC connection reestablishment procedure may not be triggered, UL transmission to the cells of the SCG may be stopped, the primary base station may be notified of the SCG failure type by the wireless device, and for a split bearer, DL data delivery on the primary base station may be maintained; NR may be configured for the split bearer RLC Acknowledged Mode (AM) bearer; PCell and / or PSCell cannot be deactivated; SCG change procedure can be used to change PSCell (for example, using security key change and RACH procedure); and / or bearer type change between split bearer and SCG bearer, or simultaneous configuration of SCG and split bearers may or may not be supported.

[0295] Regarding the interaction between the primary base station and the secondary base station for multiple connectivity, one or more of the following may be applied: the primary base station and / or the secondary base station may maintain the RRM measurement configuration of the wireless device; the primary base station may decide (for example, based on the received measurement report, traffic conditions and / or bearer type) to request the secondary base station to provide additional resources (for example, service cells) for the wireless device; upon receiving the request from the primary base station, the secondary base station may create / modify a container, which may result in the configuration of additional service cells for the wireless device (or determine that the secondary base station does not have available resources to do so); for UE capability coordination, the primary base station may provide (partial) AS configuration and UE capabilities to the secondary base station; the primary base station and the secondary base station may exchange information about UE configuration by adopting an RRC container (inter-node message) carried via an Xn message; the secondary base station may initiate reconfiguration of an existing service cell of the secondary base station (for example, towards the PUCCH of the secondary base station); the secondary base station may decide which cell is the PSCell within the SCG; the primary base station may change or not change the content of the RRC configuration provided by the secondary base station; adding and / or re-adding a secondary base station to the SCG In the case of adding an SCell, the primary base station can provide the most recent (or latest) measurement results for one or more SCG cells; the primary base station and the secondary base station can receive information about SFN and / or each other's subframe offsets from OAM and / or via the Xn interface (for example, for the purpose of DRX alignment and / or identification of measurement gaps). In an example, when a new SCG SCell is added, dedicated RRC signaling can be used to send the required system information of the cell of the CA, except for the SFN obtained from the MIB of the PSCell of the SCG.

[0296] Fig.12 is an example diagram of a random access procedure. One or more events may trigger the random access procedure. For example, the one or more events may be at least one of: initial access from RRC_IDLE, an RRC connection reestablishment procedure, a handover, DL or UL data arrival during RRC_CONNECTED when the UL synchronization state is asynchronous, a transition from RRC_Inactive, and / or a request for other system information. For example, a PDCCH command, a MAC entity, and / or a beam failure indication may initiate the random access procedure.

[0297] In an example embodiment, the random access procedure may be at least one of a contention-based random access procedure and a contention-free random access procedure. For example, the contention-based random access procedure may include one or more Msg 1 1220 transmissions, one or more Msg2 1230 transmissions, one or more Msg3 1240 transmissions, and contention resolution 1250. For example, the contention-free random access procedure may include one or more Msg 1 1220 transmissions and one or more Msg2 1230 transmissions.

[0298] In an example, the base station may transmit (e.g., unicast, multicast, or broadcast) a RACH configuration 1210 to the UE via one or more beams. The RACH configuration 1210 may include one or more parameters indicating at least one of: a set of available PRACH resources for transmission of a random access preamble, an initial preamble power (e.g., a random access preamble initial reception target power), an RSRP threshold for selecting an SS block and a corresponding PRACH resource, a power ramp factor (e.g., a random access preamble power ramp step size), a random access preamble index, a maximum number of preamble transmissions, preamble groups A and B, a threshold (e.g., a message size) for determining a random access preamble group, a set of one or more random access preambles and corresponding PRACH resources (if any) for a system information request, a set of one or more random access preambles and corresponding PRACH resources (if any) for a beam failure recovery request, a time window for monitoring a RA response, a time window for monitoring a response to a beam failure recovery request, and / or a contention resolution timer.

[0299] In an example, Msg1 1220 may be one or more transmissions of a random access preamble. For a contention-based random access procedure, the UE may select an SS block with an RSRP above an RSRP threshold. If there is a random access preamble group B, the UE may select one or more random access preambles from group A or group B based on the potential Msg3 1240 size. If there is no random access preamble group B, the UE may select one or more random access preambles from group A. The UE may randomly (e.g., with equal probability or normal distribution) select a random access preamble index from one or more random access preambles associated with the selected group. If the base station semi-statistically configures the UE with an association between the random access preamble and the SS block, the UE may randomly select a random access preamble index from one or more random access preambles associated with the selected SS block and the selected group with equal probability.

[0300] For example, the UE may initiate a contention-free random access procedure based on a beam failure indication from a lower layer. For example, the base station may semi-statistically configure the UE with one or more contention-free PRACH resources for a beam failure recovery request associated with at least one of the SS blocks and / or CSI-RS. If at least one of the SS blocks having an RSRP higher than a first RSRP threshold among the associated SS blocks or at least one of the CSI-RS having an RSRP higher than a second RSRP threshold among the associated CSI-RS is available, the UE may select a random access preamble index corresponding to the selected SS block or CSI-RS from a set of one or more random access preambles for the beam failure recovery request.

[0301] For example, the UE may receive a random access preamble index from the base station via PDCCH or RRC for a contention-free random access procedure. If the base station does not configure the UE with at least one contention-free PRACH resource associated with an SS block or CSI-RS, the UE may select a random access preamble index. If the base station configures the UE with one or more contention-free PRACH resources associated with an SS block, and at least one SS block with an RSRP higher than a first RSRP threshold is available among the associated SS blocks, the UE may select the at least one SS block and select a random access preamble corresponding to the at least one SS block. If the base station configures the UE with one or more contention-free PRACH resources associated with a CSI-RS, and at least one CSI-RS with an RSRP higher than a second RSPR threshold is available among the associated CSI-RS, the UE may select the at least one CSI-RS and select a random access preamble corresponding to the at least one CSI-RS.

[0302] The UE may perform one or more Msg1 1220 transmissions by transmitting a selected random access preamble. For example, if the UE selects an SS block and is configured with an association between one or more PRACH opportunities and one or more SS blocks, the UE may determine a PRACH opportunity from one or more PRACH opportunities corresponding to the selected SS block. For example, if the UE selects a CSI-RS and is configured with an association between one or more PRACH opportunities and one or more CSI-RS, the UE may determine a PRACH opportunity from one or more PRACH opportunities corresponding to the selected CSI-RS. The UE may transmit the selected random access preamble to the base station via the selected PRACH opportunity. The UE may determine a transmit power for transmitting the selected random access preamble based at least on an initial preamble power and a power ramp factor. The UE may determine a RA-RNTI associated with the selected PRACH opportunity in which the selected random access preamble is transmitted. For example, the UE may not determine a RA-RNTI for a beam failure recovery request. The UE may determine the RA-RNTI based at least on an index of the first OFDM symbol and an index of a first slot of a selected PRACH opportunity and / or an uplink carrier index used for transmission of Msg11220.

[0303] In an example, the UE may receive a random access response Msg 2 1230 from the base station. The UE may start a time window (e.g., ra-ResponseWindow) to monitor the random access response. For a beam failure recovery request, the base station may configure the UE with a different time window (e.g., bfr-ResponseWindow) to monitor the response to the beam failure recovery request. For example, the UE may start the time window (e.g., ra-ResponseWindow or bfr-ResponseWindow) at the start of the first PDCCH opportunity after a fixed duration of one or more symbols from the end of the preamble transmission. If the UE transmits multiple preambles, the UE may start the time window at the start of the first PDCCH opportunity after a fixed duration of one or more symbols from the end of the first preamble transmission. The UE may monitor the PDCCH of the cell for at least one random access response identified by the RA-RNTI or for at least one response to the beam failure recovery request identified by the C-RNTI while the timer of the time window is running.

[0304] In an example, if at least one random access response includes a random access preamble identifier corresponding to the random access preamble transmitted by the UE, the UE may consider that the reception of the random access response is successful. If the reception of the random access response is successful, the UE may consider that the contention-free random access procedure is successfully completed. If the contention-free random access procedure for a beam failure recovery request is triggered, the UE may consider that the contention-free random access procedure is successfully completed in the case where the PDCCH transmission is addressed to the C-RNTI. In an example, if at least one random access response includes a random access preamble identifier, the UE may consider that the random access procedure is successfully completed and may indicate receipt of an acknowledgment of the system information request of the upper layer. If the UE has signaled multiple preamble transmissions, the UE may stop transmitting the remaining preambles (if any) in response to successfully receiving the corresponding random access responses.

[0305] In an example, the UE may perform one or more Msg 3 1240 transmissions (e.g., for a contention-based random access procedure) in response to successful reception of a random access response. The UE may adjust the uplink transmission timing based on a timing advance command indicated by the random access response, and may transmit one or more transport blocks based on an uplink grant indicated by the random access response. The subcarrier spacing for PUSCH transmission of Msg3 1240 may be provided by at least one higher layer (e.g., RRC) parameter. The UE may transmit a random access preamble via PRACH and Msg3 1240 via PUSCH on the same cell. The base station may indicate the UL BWP for PUSCH transmission of Msg3 1240 via a system information block. The UE may retransmit Msg 3 1240 using HARQ.

[0306] In an example, multiple UEs may perform Msg 1 1220 by transmitting the same preamble to the base station and receiving the same random access response including an identity (e.g., TC-RNTI) from the base station. Contention resolution 1250 may ensure that the UE does not mistakenly use the identity of another UE. For example, contention resolution 1250 may be based on a C-RNTI on a PDCCH or a UE contention resolution identity on a DL-SCH. For example, if the base station assigns a C-RNTI to the UE, the UE may perform contention resolution 1250 based on the reception of a PDCCH transmission addressed to the C-RNTI. In response to detecting the C-RNTI on the PDCCH, the UE may deem contention resolution 1250 successful and may deem the random access procedure to have been successfully completed. If the UE does not have a valid C-RNTI, contention resolution may be addressed by adopting the TC-RNTI. For example, if the MAC PDU is successfully decoded and the MAC PDU includes a UE contention resolution identity MAC CE that matches the CCCH SDU transmitted in Msg3 1250, then the UE may consider contention resolution 1250 to be successful and the random access procedure to be successfully completed.

[0307] Fig.13 is an example structure of a MAC entity according to aspects of an embodiment. In an example, a wireless device may be configured to operate in a multiple connectivity mode. A wireless device in RRC_CONNECTED with multiple RX / TX may be configured to utilize radio resources provided by multiple schedulers located in multiple base stations. Multiple base stations may be connected via a non-ideal or ideal backhaul on an Xn interface. In an example, a base station among multiple base stations may act as a primary base station or a secondary base station. The wireless device may be connected to a primary base station and one or more secondary base stations. The wireless device may be configured with multiple MAC entities, for example, one MAC entity for a primary base station, and one or more other MAC entities for one or more secondary base stations. In an example, a configured service cell set for a wireless device may include two subsets: an MCG, which includes a service cell of a primary base station; and one or more SCGs, which include service cells of one or more secondary base stations. Fig.13 An example structure of a MAC entity is shown when MCG and SCG are configured for a wireless device.

[0308] In an instance, at least one cell in an SCG may have a configured UL CC, where the cell of at least one cell may be referred to as a PSCell or a PCell of the SCG, or sometimes simply referred to as a PCell. The PSCell may be configured with PUCCH resources. In an instance, when an SCG is configured, there may be at least one SCG bearer or one split bearer. In an instance, after a physical layer problem or a random access problem is detected on the PSCell, or after the number of RLC retransmissions associated with the SCG is reached, or after an access problem is detected on the PSCell during an SCG addition or an SCG change: the RRC connection reestablishment procedure may not be triggered, UL transmission to the cells of the SCG may be stopped, the UE may notify the primary base station of the SCG failure type, and DL data delivery on the primary base station may be maintained.

[0309] In an example, the MAC sublayer may provide services such as data transfer and radio resource allocation to an upper layer (e.g., 1310 or 1320). The MAC sublayer may include multiple MAC entities (e.g., 1350 and 1360). The MAC sublayer may provide data transfer services on logical channels. In order to accommodate different types of data transfer services, multiple types of logical channels may be defined. Logical channels may support the transfer of specific types of information. The type of logical channel may be defined by what type of information (e.g., control or data) is transferred. For example, BCCH, PCCH, CCCH, and DCCH may be control channels, and DTCH may be a traffic channel. In an example, a first MAC entity (e.g., 1310) may provide services on PCCH, BCCH, CCCH, DCCH, DTCH, and MAC control elements. In an example, a second MAC entity (e.g., 1320) may provide services on BCCH, DCCH, DTCH, and MAC control elements.

[0310] The MAC sublayer may anticipate services from the physical layer (e.g., 1330 or 1340), such as data transfer services, signaling of HARQ feedback, scheduling requests, or signaling of measurement values ​​(e.g., CQI). In an example, in dual connectivity, two MAC entities may be configured for the wireless device: one for the MCG and one for the SCG. The MAC entity of the wireless device may process multiple transport channels. In an example, a first MAC entity may process a first transport channel, including a PCCH of the MCG, a first BCH of the MCG, one or more first DL-SCHs of the MCG, one or more first UL-SCHs of the MCG, and one or more first RACHs of the MCG. In an example, a second MAC entity may process a second transport channel, including a second BCH of the SCG, one or more second DL-SCHs of the SCG, one or more second UL-SCHs of the SCG, and one or more second RACHs of the SCG.

[0311] In an example, if a MAC entity is configured with one or more SCells, there may be multiple DL-SCHs per MAC entity, and there may be multiple UL-SCHs as well as multiple RACHs. In an example, there may be one DL-SCH and UL-SCH on a SpCell. In an example, for a SCell, there may be one DL-SCH, zero or one UL-SCH, and zero or one RACH. The DL-SCH may support reception using different parameter sets and / or TTI durations within the MAC entity. The UL-SCH may also support transmission using different parameter sets and / or TTI durations within the MAC entity.

[0312] In an example, the MAC sublayer may support different functions and these functions may be controlled using control (e.g., 1355 or 1365) elements. Functions performed by the MAC entity may include mapping between logical channels and transport channels (e.g., in uplink or downlink), multiplexing (e.g., 1352 or 1362) MAC SDUs from one or different logical channels to a transport block (TB) to be delivered to a physical layer on a transport channel (e.g., in uplink), demultiplexing (e.g., 1352 or 1362) MAC SDUs from a transport block (TB) delivered from a physical layer on a transport channel to one or different logical channels (e.g., in downlink), scheduling information reporting (e.g., in uplink), error correction by HARQ in uplink or downlink (e.g., 1363), and logical channel prioritization in uplink (e.g., 1351 or 1361). The MAC entity may handle a random access procedure (e.g., 1354 or 1364).

[0313] Fig.14 is an example diagram of a RAN architecture including one or more base stations. In an instance, a protocol stack (e.g., RRC, SDAP, PDCP, RLC, MAC, and PHY) can be supported at the node. A base station (e.g., 120A or 120B) may include a base station central unit (CU) (e.g., gNB-CU 1420A or 1420B) and at least one base station distributed unit (DU) (e.g., gNB-DU1430A, 1430B, 1430C, or 1430D) (if functional division is configured). The upper protocol layers of the base station may be located in the base station CU, and the lower layers of the base station may be located in the base station DU. The F1 interface (e.g., CU-DU interface) connecting the base station CU and the base station DU may be an ideal or non-ideal backhaul. F1-C may provide a control plane connection via the F1 interface, and F1-U may provide a user plane connection via the F1 interface. In an instance, an Xn interface may be configured between the base station CUs.

[0314] In an example, the base station CU may include an RRC function, an SDAP layer, and a PDCP layer, and the base station DU may include an RLC layer, a MAC layer, and a PHY layer. In an example, various functional splitting options between the base station CU and the base station DU are possible by locating different combinations of upper protocol layers (RAN functions) in the base station CU and different combinations of lower protocol layers (RAN functions) in the base station DU. The functional splitting may support the flexibility of moving protocol layers between the base station CU and the base station DU according to service requirements and / or network environment.

[0315] In an instance, the functional splitting options can be configured for each base station, each base station CU, each base station DU, each UE, each bearer, each slice layer, or at other granularity. In each base station CU split, the base station CU can have a fixed splitting option, and the base station DU can be configured to match the splitting option of the base station CU. In each base station DU split, the base station DU can be configured with different splitting options, and the base station CU can provide different splitting options for different base station DUs. In the per-UE split, the base station (base station CU and at least one base station DU) can provide different splitting options for different wireless devices. In each bearer split, different splitting options can be used for different bearers. In each slice layer splicing, different splitting options can be applied to different slice layers.

[0316] Fig.15is an example diagram showing RRC state transitions of a wireless device. In an example, the wireless device may be in at least one of an RRC connected state (e.g., RRC connected 1530, RRC_Connected), an RRC idle state (e.g., RRC idle 1510, RRC_Idle), and / or an RRC inactive state (e.g., RRC inactive 1520, RRC_Inactive). In an example, in the RRC connected state, the wireless device may have at least one RRC connection with at least one base station (e.g., gNB and / or eNB), and the base station may have a UE context of the wireless device. The UE context (e.g., wireless device context) may include at least one of an access layer context, one or more radio link configuration parameters, bearer (e.g., data radio bearer (DRB), signaling radio bearer (SRB), logical channel, QoS flow, PDU session, etc.) configuration information, security information, PHY / MAC / RLC / PDCP / SDAP layer configuration information, and / or similar configuration information for the wireless device. In an example, in the RRC idle state, the wireless device may not have an RRC connection with the base station, and the UE context of the wireless device may not be stored in the base station. In an example, in the RRC inactive state, the wireless device may not have an RRC connection with the base station. The UE context of the wireless device may be stored in the base station, which may be referred to as an anchor base station (e.g., a last serving base station).

[0317] In an example, the wireless device may transition the UE RRC state between the RRC idle state and the RRC connected state in two ways (e.g., connection release 1540 or connection establishment 1550; or connection reestablishment) and / or between the RRC inactive state and the RRC connected state in two ways (e.g., connection deactivation 1570 or connection recovery 1580). In an example, the wireless device may transition its RRC state from the RRC inactive state to the RRC idle state (e.g., connection release 1560).

[0318] In an example, an anchor base station may be a base station that maintains a UE context (wireless device context) of a wireless device at least during a time period that the wireless device stays in a RAN notification area (RNA) of the anchor base station and / or the wireless device stays in an RRC inactive state. In an example, an anchor base station may be a base station to which a wireless device in an RRC inactive state was last connected in the latest RRC connected state, or a base station where the wireless device last performed an RNA update procedure. In an example, an RNA may include one or more cells operated by one or more base stations. In an example, a base station may belong to one or more RNAs. In an example, a cell may belong to one or more RNAs.

[0319] In an example, the wireless device may transition the UE RRC state from the RRC connected state to the RRC inactive state in the base station. The wireless device may receive RNA information from the base station. The RNA information may include at least one of an RNA identifier, one or more cell identifiers of one or more cells of the RNA, a base station identifier, an IP address of the base station, an AS context identifier of the wireless device, a recovery identifier, etc.

[0320] In an instance, an anchor base station may broadcast a message (e.g., a RAN paging message) to a base station of the RNA to reach a wireless device in an RRC inactive state, and / or a base station receiving a message from the anchor base station may broadcast and / or multicast another message (e.g., a paging message) over an air interface to wireless devices in its coverage area, a cell coverage area, and / or a beam coverage area associated with the RNA.

[0321] In an example, when a wireless device in an RRC inactive state moves to a new RNA, the wireless device may perform an RNA update (RNAU) procedure, which may include a random access procedure and / or a UE context retrieval procedure for the wireless device. The UE context retrieval may include: a base station receiving a random access preamble from the wireless device; and the base station extracting a UE context of the wireless device from an old anchor base station. The extraction may include: sending a retrieve UE context request message including a recovery identifier to the old anchor base station, and receiving a retrieve UE context response message including the UE context of the wireless device from the old anchor base station.

[0322] In an example embodiment, a wireless device in an RRC inactive state may select a cell to camp on based on measurement results of at least one or more cells, cells that the wireless device may monitor RNA paging messages, and / or core network paging messages from a base station. In an example, a wireless device in an RRC inactive state may select a cell to perform a random access procedure to restore an RRC connection and / or transmit one or more packets to a base station (e.g., to a network). In an example, if the selected cell belongs to an RNA different from the RNA of the wireless device in an RRC inactive state, the wireless device may initiate a random access procedure to perform an RNA update procedure. In an example, if the wireless device in an RRC inactive state has one or more packets in a buffer to transmit to the network, the wireless device may initiate a random access procedure to transmit one or more packets to a base station of a cell selected by the wireless device. The random access procedure may be performed using two messages (e.g., level 2 random access) and / or four messages (e.g., level 4 random access) between the wireless device and the base station.

[0323] In an example embodiment, a base station receiving one or more uplink packets from a wireless device in an RRC inactive state may extract a UE context for the wireless device based on at least one of an AS context identifier, an RNA identifier, a base station identifier, a recovery identifier, and / or a cell identifier received from the wireless device by transmitting a retrieve UE context request message for the wireless device to an anchor base station of the wireless device. In response to extracting the UE context, the base station may transmit a path switch request for the wireless device to a core network entity (e.g., AMF, MME, etc.). The core network entity may update a downlink tunnel endpoint identifier of one or more bearers established for the wireless device between a user plane core network entity (e.g., UPF, S-GW, etc.) and a RAN node (e.g., a base station), for example, changing the downlink tunnel endpoint identifier from an address of the anchor base station to an address of the base station.

[0324] In the prior art, the IAB donor has an RRC function that serves the wireless device. When a backhaul link failure occurs between the serving IAB node and the serving IAB donor, the wireless device may experience an RRC connection failure. In the implementation of the prior art, when the base station receives a wireless device report of an RRC connection failure due to a backhaul link failure, the base station may misunderstand the RRC connection failure as an access link problem between the wireless device and the IAB node. When the IAB node backhaul link fails, the implementation of the prior art may increase incorrect radio parameter configuration. The prior art may reduce the radio access reliability of the wireless device.

[0325] Example embodiments support a radio link failure reporting mechanism that provides backhaul link information for wireless devices. Example embodiments may support radio communication parameters configured based on status information of a radio backhaul link. Implementation of example embodiments may improve communication reliability and mobility of wireless devices.

[0326] In an example, an IAB node may be interpreted as at least one of an intermediate network node, an IAB donor, a base station, a gNB, a gNB-DU, an eNB, a relay node, a wireless device, a UE, an access point, etc. In an example, an IAB donor may be interpreted as at least one of a base station, a gNB, a gNB-CU, an eNB, a relay donor node, an IAB node, an access point, etc. In an example, a wireless device may be interpreted as a user equipment (UE), an IAB node, an IAB donor, a relay node, a base station, a gNB, etc.

[0327] In an example, an integrated access and backhaul (IAB) may support wireless backhaul connectivity for access network nodes (e.g., distributed units, gNB-DUs, base stations, gNBs, IAB nodes, relay nodes, mobile relay nodes, RAN nodes, etc.). In an example, an IAB node may indicate a RAN node that may support wireless access and / or wireless backhaul access services to a UE. In an example, an IAB provider may indicate a RAN node that may provide an interface for a UE to a core network and / or provide wireless backhaul functionality to an IAB node.

[0328] In an example, IAB can enable flexible and / or very dense cell deployments without proportionally increasing the density of the transmission network. A wide variety of deployment scenarios can be envisioned, including support for outdoor small cell deployments, indoor and / or even mobile relays (e.g., on buses and / or trains). IAB can support physically fixed relays and / or mobile relays.

[0329] In an example IAB deployment, in-band and / or out-of-band backhaul with respect to an access link may be supported. In-band backhaul may include scenarios where the access and backhaul links at least partially overlap in frequency, thereby forming a half-duplex constraint or an interference constraint. The half-duplex constraint and / or interference constraint of the in-band backhaul may imply that the IAB node may not transmit and receive on both links simultaneously. In an example, an out-of-band scenario may not constitute a half-duplex constraint and / or an interference constraint. In an in-band backhaul deployment, tighter intercommunication between access and backhaul may be required in compliance with the half-duplex and interference constraints.

[0330] In an example, the in-band IAB scenario can support TDM / FDM / SDM for access and backhaul links subject to half-duplex constraints at the IAB node. In an example, the in-band IAB scenario can support a full-duplex solution. In an example, the same set of RAN features designed for the in-band scenario can be used to support the out-of-band IAB scenario.

[0331] In an example, IAB may support access and backhaul for spectrum above 6 GHz and / or below 6 GHz. Backhaul for access services over the same RAT backhaul link may be supported. Inter-RAT operations for backhaul and access may be supported.

[0332] The UE may transparently connect to the IAB node over the same RAT.The IAB architecture required for first RAT access over a second RAT backhaul may be supported.

[0333] In an example, IAB can support standalone (SA) and / or non-standalone (NSA) deployments. For NSA, IAB-based relaying of a UE's secondary cell group (SCG) path can be supported. IAB-based relaying of a UE's primary cell group (MCG) path is supported.

[0334] The IAB node may operate in SA and / or NSA mode. In an example, EN-DC and SA option 2 may be supported. In an example, EN-DC and SA option 2 for UE and IAB node may be supported. NSA deployment option and / or a combination of SA and NSA may be supported.

[0335] In an example, the access link may support SA and / or NSA. For an NSA access link, a relay may be applied to a RAN node. In an example, the backhaul link may support both NSA and SA. Backhaul services over a radio interface may be supported. In an example, EN-DC may be supported for NSA access and backhaul links.

[0336] In an example, multi-hop backhaul can provide more range extension than a single hop. Multi-hop backhaul may be beneficial for frequencies above 6 GHz due to limited range. Multi-hop backhaul can enable backhaul around obstacles, such as cluttered buildings in an urban environment. In an example, it can be expected that the number of hops in an IAB deployment depends on many factors, such as frequency, cell density, propagation environment, and / or traffic load. These factors may change over time. From an architectural perspective, flexibility in the number of hops may be desired.

[0337] In an example, as the number of hops increases, scalability issues may limit performance and / or increase signaling load. Capturing scalability to the number of hops may impact system performance. The IAB design may support multiple backhaul hops. In an example, the IAB architecture may not limit the number of backhaul hops. Scalability of the number of hops may be supported. In an example, a single hop may be considered (e.g., interpreted) as a special case of multiple backhaul hops.

[0338] In examples, wireless backhaul links may be susceptible to congestion, for example, due to moving objects such as vehicles, due to seasonal changes (foliage), and / or due to infrastructure changes (e.g., new buildings). Vulnerability of wireless backhaul links may apply to physically fixed IAB nodes. In examples, traffic changes may create uneven load distribution on wireless backhaul links, resulting in local link and / or node congestion.

[0339] In an example, topology adaptation (e.g., adaptive routing) can refer to the procedure of autonomously reconfiguring the backhaul network without interrupting service to UEs in situations such as blocking and / or local congestion. In an example, topology adaptation for physically fixed relays can be supported to achieve robust operation, for example, to mitigate blocking and / or load variations on the backhaul link.

[0340] In an example, for an IAB implementation, both Layer 2 (L2) and Layer 3 (L3) relay architectures may be supported.

[0341] In examples, IAB-related features such as IAB node integration and / or topology adaptation may impact core network operations. In examples, IAB functionality may create additional core network signaling load. The amount of signaling load on core network nodes may vary between various designs of IAB architectures.

[0342] In an example, time synchronization between IAB nodes may be implemented, for example to support TDD systems and / or some potential features that may require network synchronization. The IAB may support additional implementations regarding network synchronization, which may include in-band wireless backhaul and / or multi-hop backhaul.

[0343] In an example, the IAB architecture may include a mobile terminal (MT), gNB-DU, gNB-CU, UPF, AMF, and SMF and corresponding interfaces NR Uu (between MT and gNB), F1, NG, X2, and N4. The IAB architecture may be configured based on modifications or enhancements to these functions and interfaces. A mobile terminal (MT) function may be defined as a component of a mobile device (e.g., user equipment, UE). In an example, an MT may be referred to as a function located on an IAB node that terminates the radio interface layer of a backhaul Uu interface toward an IAB donor and / or other IAB nodes.

[0344] Fig.16 An example diagram of an IAB in standalone mode is shown, which may contain an IAB donor body and multiple IAB nodes. The IAB donor body may be viewed as a single logical node, which may include a set of functions, such as gNB-DU, gNB-CU-CP, gNB-CU-UP, and / or possible other functions. In a deployment, the IAB donor body may be divided according to these functions, which may be collocated and / or non-collocated. The IAB architecture may operate separately from these functions. In an example, in some cases, some of the functions associated with the IAB donor body may be moved outside the donor body.

[0345] In an example, the IAB node can operate in SA mode and / or NSA mode. When operating in NSA, the IAB node can use other links for backhaul. In an example, a UE connected to an IAB node can select an operating mode different from that of the IAB node. The UE can be connected to a core network of a different type than the IAB node to which the UE is connected. In this case, (e)Decor or slices can be used for core network selection. An IAB node operating in NSA mode can be connected to the same or different base stations (e.g., gNB, eNB). A UE operating in an NSA node can be connected to the same or different base station as the IAB node to which it is connected. Fig.17 Examples of SA mode and NSA mode with one or more core networks are shown.

[0346] In an example, IAB multi-hop designs may differ in terms of modifications required on interfaces and / or additional functionality required to accomplish multi-hop forwarding, for example. The example architectures may be divided into two architecture groups.

[0347] In an instance, architecture group 1 may include architecture 1a and / or 1b. Architecture 1a and / or 1b may utilize a CU / DU split architecture. Architecture 1a may include backhauling F1-U using an adaptation layer and / or GTP-U in conjunction with an adaptation layer. Architecture 1a may use an adaptation layer for operation with a core network and / or a PDN connection layer for operation with other core networks to route across intermediate nodes with hop-by-hop forwarding (e.g., other RATs, EPC). In an instance, architecture 1b may include backhauling F1-U on an access node using GTP-U / UDP / IP. Architecture 1b may use an adaptation layer to employ hop-by-hop forwarding across intermediate nodes.

[0348] In an instance, architecture group 2 may include architectures 2a, 2b, and / or 2c. Architecture 2a may include backhauling F1-U or NG-U on an access node using GTP-U / UDP / IP. Architecture 2a may employ hop-by-hop forwarding across intermediate nodes using PDU session layer routing. Architecture 2b may include backhauling F1-U or NG-U on an access node using GTP-U / UDP / IP. Architecture 2b may employ hop-by-hop forwarding across intermediate nodes using GTP-U / UDP / IP nested tunnels. Architecture 2c may include backhauling F1-U or NG-U on an access node using GTP-U / UDP / IP. Architecture 2c may employ hop-by-hop forwarding across intermediate nodes using GTP-U / UDP / IP nested tunnels.

[0349] In an example, architecture 1a may utilize a CU / DU split architecture. Fig.18An example diagram of a dual-hop chain of IAB nodes below an IAB donor body is shown, where the IAB node and the UE are connected to a core network node (e.g., AMF, UPF, SMF, MME, SGW) in SA mode. In architecture 1a, the IAB node may hold a DU and / or MT. Via the MT, the IAB node may be connected to an upstream IAB node and / or an IAB donor body. Via the DU, the IAB node may establish an RLC channel to the UE and / or to the MT of a downstream IAB node. For the MT, the RLC channel may refer to a modified RLC*. The IAB node may be connected to more than one upstream IAB node and / or IAB donor body.

[0350] In an example of architecture 1a, a donor (IAB donor) may maintain DUs to support UEs and / or MTs of downstream IAB nodes. An IAB donor may maintain CUs for DUs of IAB nodes and / or its own DUs. Different CUs may serve DUs of IAB nodes. DUs on IAB nodes may be connected to CUs in IAB donors using a modified form of F1 (referred to as F1*). F1*-U may run on an RLC channel on a wireless backhaul between an MT on a serving IAB node and a DU on a donor. F1*-U transmission between an MT and a DU on a serving IAB node and / or between a DU and a CU on a donor may be configured. In an example, an adaptation layer may be added that may maintain routing information to enable hop-by-hop forwarding. The adaptation layer may replace the IP functionality of the F1 stack. F1*-U may carry a GTP-U header for end-to-end association between a CU and a DU. In an example, the information carried by the GTP-U header may be included in the adaptation layer.

[0351] In the example of architecture 1a, the RLC may apply ARQ on an end-to-end connection and / or on a hop-by-hop basis. Fig.18 An example of an F1*-U protocol stack is shown. RLC* may refer to an enhancement of RLC. The MT of an IAB node may maintain a connection between NAS and a core network node (e.g., AMF, SMF, MME, and / or similar core nodes), for example, for authentication of the IAB node. The MT of an IAB node may maintain a PDU session via a core network node (e.g., UPF, SGW, PGW, and / or similar core nodes), for example, to provide the IAB node with a connection to operations and management (OAM). In an example, for NSA operation with a core network, the MT may be dual-connected to the network (e.g., gNB, eNB, RNC, core network). The MT of an IAB node may maintain a PDN connection with the core network, for example, to provide the IAB node with a connection to OAM. Protocol conversion between F1* and F1 may be supported when the IAB donor body is split.

[0352] In an example, architecture 1b may utilize a CU / DU split architecture. Fig.19 An example diagram of a two-hop chain of IAB nodes below an IAB donor body is shown. An IAB donor body may hold one logical CU. An IAB node may be connected to more than one upstream IAB node and / or IAB donor body. In an example of architecture 1b, an IAB node and / or IAB donor body may hold the same functionality as architecture 1a. In an example, as in architecture 1a, a backhaul link may establish an RLC channel. In architecture 1b, an adaptation layer may be inserted to enable hop-by-hop forwarding of F1*.

[0353] In the example of architecture 1b, the MT on the IAB node can establish a PDU session with the UPF located on the donor body (IAB donor body). The MT's PDU session can carry F1* for the collocated DU. In the example, the PDU session can provide a point-to-point link between the CU and the DU. Regarding the intermediate hops, the PDCP-PDU of F1* can be forwarded via the adaptation layer. Fig.19 An example of the F1*-U protocol stack is shown. For NSA operation with a core network, the MT can be dual-connected to the network (e.g., gNB, eNB, RNC, core network). The MT of the IAB node can maintain a PDN connection with the local gateway (L-GW) located on the donor body.

[0354] Fig. 20 An example diagram of architecture 2a is shown in which the UE and / or IAB node can use SA mode with the core network. In an instance of architecture 2a, the IAB node can maintain an MT to establish a Uu link with a gNB (base station) on a parent IAB node and / or an IAB donor. Via the Uu link, the MT can maintain a PDU session with the UPF, which can be collocated with the gNB. Independent PDU sessions can be created on a backhaul link (e.g., hop by hop). The IAB node can support routing functions to forward data between PDU sessions on adjacent links. The routing function can create a forwarding plane across the wireless backhaul. Based on the PDU session type, the forwarding plane can support IP and / or Ethernet. If the PDU session type is Ethernet, an IP layer can be established on top. The IAB node can obtain an IP connection to the wired backhaul network. The IAB node can be connected to more than one upstream IAB node and / or IAB donor.

[0355] In the example of architecture 2a, IP-based interfaces (e.g., NG, Xn, F1, N4, etc.) may be carried on the forwarding plane. In the case of F1, the UE-serving IAB node may contain a DU for the access link in addition to the gNB and / or UPF for the backhaul link. The CU for the access link may be located in the IAB donor body or outside the IAB donor body. Fig. 20An example of an NG-U protocol stack for IP-based and / or Ethernet-based PDU session types is shown. If the IAB node maintains the DU for UE access, PDCP-based protection on the hop may not be required because the end-to-end PDCP between the UE and the CU can be used to protect the end-user data. For NSA operation with a core network, the MT can be dual-connected to the network (e.g., gNB, eNB, RNC, core network). The MT of the IAB node can maintain a PDN connection with the L-GW, which is located on the parent IAB node and / or the IAB donor. IP-based interfaces (e.g., NG, Xn, S1, S5, X2, etc.) can be carried on the forwarding plane.

[0356] In the example of architecture 2b, if Fig.21 As shown, the IAB node can maintain the MT to establish a Uu link with the gNB (base station) on the parent IAB node and / or the IAB donor body. Via the Uu link, the MT can maintain a PDU session with the UPF. The UPF can be located at the IAB donor body. Forwarding PDUs across upstream IAB nodes can be achieved via tunnels. Forwarding across multiple hops can create a stack of nested tunnels. The IAB node can obtain an IP connection with the wired backhaul network. IP-based interfaces (e.g., NG, Xn, F1, N4, etc.) can be carried on the forwarding IP plane. Fig.21 An example protocol stack for NG-U (e.g., S1-U) is shown. An IAB node may be connected to more than one upstream IAB node and / or IAB donor. For NSA operation with a core network, the MT may be dual connected to the network (e.g., gNB, eNB, RNC, core network). The MT of an IAB node may maintain a PDN connection with an L-GW located on the IAB donor.

[0357] In the example, Fig. 22 As shown, architecture 2c can utilize DU-CU splitting. The IAB node can maintain an MT, which can maintain an RLC channel with a DU on a parent IAB node and / or an IAB donor. The IAB donor can maintain a CU and / or UPF for the DU of the IAB node. The MT on the IAB node can maintain a Uu link with the CU and / or a PDU session with the UPF on the donor (IAB donor). Forwarding on intermediate nodes can be achieved via tunnels. Forwarding across multiple hops can create a stack of nested tunnels. The IAB node can obtain an IP connection with a wired backhaul network. The tunnel can contain an SDAP / PDCP layer. IP-based interfaces (e.g., NG, Xn, F1, N4, etc.) can be carried on the forwarding plane. Fig. 22An example protocol stack for NG-U (e.g., S1-U) is shown. An IAB node may be connected to more than one upstream IAB node and / or IAB donor. For NSA operation with a core network, the MT may be dual connected to the network (e.g., gNB, eNB, RNC, core network). The MT of an IAB node may maintain a PDN connection with an L-GW located on the IAB donor.

[0358] In an example, the IAB node may follow the same initial access procedure as the UE (e.g., wireless device), including cell search, system information (SI) acquisition and / or random access, to initially establish a connection to the parent IAB node and / or IAB donor. For IAB node discovery and / or measurement, SSB / CSI-RS-based RRM measurements may be supported. In an example, an IAB node discovery procedure subject to half-duplex constraints and / or multi-hop topology may be supported, including how to avoid conflicting SSB configurations between IAB nodes and / or the feasibility of CSI-RS-based IAB node discovery. When considering the cell ID used by a given IAB node, the IAB donor and the IAB node may share the same cell ID, and / or the IAB donor and the IAB node may maintain separate cell IDs. The feasibility of sharing the same cell ID by the IAB donor and the IAB node may depend on the IAB architecture. Mechanisms for multiplexing RACH transmissions from the UE and RACH transmissions from the IAB node may be supported.

[0359] In an instance, measurements for link management and / or routing selection may be supported on multiple backhaul links. To support half-duplex constraints in an IAB node, the IAB may support detection and / or measurement of candidate backhaul links (e.g., after initial access), which may utilize resources that are temporally orthogonal to the resources used by the access UE for cell detection and / or measurement. To support measurements, the IAB may support at least one of: TDM of SSBs (e.g., depending on hop order, cell ID, etc.); SSB muting across IAB nodes; multiplexing of SSBs for access UEs and IABs within and / or across half frames; additional IAB node discovery signals, which may be TDM with SSB transmissions (e.g., CSI-RS) using non-grid SSBs; a different transmission period for backhaul link detection and / or measurement than the period used by the access UE; and the like. Coordination mechanisms for different solutions may be supported, including coordination mechanisms for reference signal (RS) transmission and / or measurement timing for IAB nodes. Enhancements to SMTC and / or CSI-RS configuration may be considered to support RRM measurements of IAB nodes.

[0360] In an example, the IAB node may support mechanisms for detecting / recovering from backhaul link failures. Enhancements to the RLM RS and / or associated procedures of the IAB may be supported.

[0361] In an example, mechanisms for simultaneous route switching and / or transmission / reception on multiple backhaul links (e.g., multi-TRP operation and / or intra-frequency dual connectivity) may be supported. The feasibility of these mechanisms may depend on the IAB architecture.

[0362] In an example, downlink IAB node transmissions (e.g., transmissions on a backhaul link from an IAB node to a child IAB node served by the IAB node and transmissions on an access link from an IAB node to a UE served by the IAB node) may be scheduled by the IAB node. In an example, uplink IAB transmissions (e.g., transmissions on a backhaul link from an IAB node to its parent IAB node and / or IAB donor) may be scheduled by a parent IAB node or an IAB donor.

[0363] In an example, the IAB may support time division multiplexing (TDM), frequency division multiplexing (FDM) and / or space division multiplexing (SDM) between an access link and a backhaul link, for example, at an IAB node subject to a half-duplex constraint. The TDM / FDM / SDM multiplexing mechanism for access / backhaul services across multiple hops may take into account the IAB node half-duplex constraint. In an example, the IAB may support an orthogonal partitioning mechanism for time slots and / or frequency resources between an access link and a backhaul link across one or more hops. The IAB may use different DL / UL time slot configurations for the access link and the backhaul link. The IAB may support DL and / or UL power control enhancements and / or timing requirements to allow intra-panel FDM and / or SDM for backhaul and access links. In an example, the IAB may provide interference management including cross-link interference.

[0364] In an example, the IAB may provide scheduling coordination, resource allocation, and / or routing mechanisms across IAB nodes / IAB donors and / or multiple backhaul hops. Semi-static (e.g., on the time scale of RRC signaling) coordination of resources (e.g., frequency, time represented in slot / slot format, etc.) between IAB nodes may be supported. In an example, the IAB may support distributed and / or centralized resource coordination mechanisms. The IAB may support various resource granularities (e.g., TDD configuration modes) for required signaling. The IAB nodes and / or IAB donors may exchange L1 and / or L3 measurement result information. In an example, the IAB nodes and / or IAB donors may exchange topology related information (e.g., hop order) based on the backhaul link physical layer design. The IAB may support resource (e.g., frequency, time represented in slot / slot format, etc.) coordination that may be faster than semi-static coordination.

[0365] In an example, over-the-air (OTA) synchronization may be configured for the IAB. In an example, the IAB may support a timing alignment mechanism for adjusting the IAB nodes. The IAB may support detection and management of timing misalignment (e.g., based on the number of hops). In an example, the IAB may implement a timing alignment mechanism across a multi-hop IAB network. The IAB may support TA-based synchronization between IAB nodes (including across multiple backhaul hops). In an example, the IAB may support various cases of transmission timing alignment across IAB nodes and / or IAB donors: DL transmission timing alignment across IAB nodes and / or IAB donors; DL and UL transmission timing aligned within the IAB node; DL and UL reception timing aligned within the IAB node; timing alignment within the IAB node when transmitting DL and UL and receiving DL and UL; DL transmission timing alignment across IAB nodes and / or IAB donors for access links; and / or timing alignment within the IAB node when transmitting DL and UL and receiving DL and UL in different time slots for backhaul link timing.

[0366] In an example, the timing alignment level between IAB nodes / IAB donors and / or within an IAB node may include slot-level alignment, symbol-level alignment, and / or misalignment. IAB implementations for TDM / FDM / SDM multiplexing of access links and backhaul links, cross-link interference, and / or access UEs may be supported.

[0367] In an example, the IAB may control cross-link interference (CLI) on access and backhaul links (including across multiple hops) by providing interference measurement and management mechanisms.

[0368] In an instance, the IAB CLI mitigation technique may support advanced receiver and transmitter coordination. The CLI mitigation technique may support interference mitigation mechanisms for IAB inter-node interference scenarios, such as: the victim IAB node receives in DL via its MT, and the interfering IAB node transmits in UL via its MT; the victim IAB node receives in DL via its MT, and the interfering IAB node transmits in DL via its DU; the victim IAB node receives in UL via its DU, and the interfering IAB node transmits in UL via its MT; and / or the victim IAB node receives in UL via its DU, and the interfering IAB node transmits in DL via its DU. If FDM / SDM reception is performed between the access link and the backhaul link at the IAB node, the IAB may implement a mechanism for resolving interference experienced at the IAB node. In an instance, the IAB may support CLI measurement results, such as short-term / long-term measurement results, and / or measurement results based on multiple antennas and beamforming, and may support CLI mitigation in the IAB node and / or IAB donor.

[0369] IAB can support high spectrum efficiency wireless backhaul links. In an example, IAB can support 1024QAM for the backhaul link.

[0370] In an example, the UE may establish an RLC channel to the DU on the UE's access IAB node. The RLC channel may be extended between the UE's access DU and the IAB donor via a modified form of F1-U (referred to as F1*-U). The information embedded in the F1*-U may be carried across the backhaul link through the RLC channel. The transmission of F1*-U on the wireless backhaul may be achieved through an adaptation layer, which may be integrated with the RLC channel. The IAB donor (referred to as the fronthaul) may use the F1-U stack. The IAB donor DU may be relayed between the F1-U on the fronthaul and / or the F1*-U on the wireless backhaul.

[0371] In an instance of architecture 1a, the information carried on the adaptation layer can support one or more of the following functions: identification of UE bearers for PDUs, routing across wireless backhaul topology, implementation of QoS by the scheduler on DL and UL on the wireless backhaul link, mapping of UE user plane PDUs to backhaul RLC channels, etc.

[0372] In the example of architecture 1b, the information carried on the adaptation layer can support one or more of the following functions: routing across wireless backhaul topology, implementation of QoS by the scheduler on DL and UL on the wireless backhaul link, mapping of UE user plane PDUs to backhaul RLC channels, etc.

[0373] In an example, the information to be carried on the adaptation layer header may include one or more of the following: UE bearer specific Id, UE specific Id, routing Id, IAB node, IAB donor address, QoS information, etc.

[0374] In an example, information about the adaptation layer can be processed to support adaptation layer functions at IAB nodes on a path (eg, hop-by-hop) and / or at an access IAB node and an IAB donor (eg, end-to-end) of a UE.

[0375] In an example, the adaptation layer may be integrated with or above the MAC layer, such as Fig.23 (e.g. a, b) as shown. In an example, the adaptation layer can be integrated with the upper RLC layer, such as Fig.23 (e.g. c, d, e) and / or Fig.24 shown.

[0376] In the example, Fig.23 and / or Fig.24 An example protocol stack is shown. Although the RLC channel serving the backhaul contains the adaptation layer, the adaptation layer may be contained in the IAB node access link.

[0377] In an example, the adaptation layer may include sublayers. The GTP-U header may become part of the adaptation layer. In an example, the GTP-U header may be carried on top of the adaptation layer to carry the end-to-end association between the IAB node DU and the CU (e.g., Fig.23 d).

[0378] In an example, the IP header may be part of and / or carried on top of the adaptation layer (e.g., as Fig.23 e). In an example, the IAB donor DU may maintain IP routing functionality to extend the IP routing plane of the fronthaul to the IP layer carried by the adaptation on the wireless backhaul. This may allow, for example, a local F1-U to be established end-to-end between the IAB node DU and the IAB donor CU-UP. The IAB node may maintain an IP address that may be routed from the fronthaul via the IAB donor DU. The IP address of the IAB node may be used for routing on the wireless backhaul. The IP layer on top of the adaptation may not represent a PDU session. The first hop router of the MT on the IP layer may not maintain the UPF.

[0379] In an example, the adaptation layer above RLC can support hop-by-hop ARQ. The adaptation layer above MAC can support hop-by-hop and end-to-end ARQ. In an example, both adaptation layer placements can support aggregate routing, for example, by inserting the IAB node address into the adaptation header. In an example, both adaptation layer placements can support QoS for each UE bearer for a large number of UE bearers. In an example, for the adaptation layer above RLC, the LCID space can be enhanced because the UE bearer can be mapped to an independent logical channel. In an example, for the adaptation layer above MAC, information related to the UE bearer can be carried on the adaptation header. In an example, both adaptation layer placements can support aggregated QoS processing, for example, by inserting the aggregated QoS Id into the adaptation header. In an example, the aggregated QoS processing can reduce the number of queues. The aggregated QoS processing can be independent of the location where the adaptation layer is placed. In an example, for both adaptation layer placements, the aggregation of routing and / or QoS processing can allow active configuration of the IAB node on the intermediate path, that is, the configuration can be independent of the UE bearer establishment / release. In an example, for both adaptation layer placements, RLC ARQ can be pre-processed on the TX side.

[0380] In an example, for RLC AM, ARQ may be performed hop-by-hop along the access link and the backhaul link. ARQ may be supported end-to-end between the UE and the IAB donor. RLC segmentation may be an on-the-fly process and / or may be performed in a hop-by-hop manner.

[0381] One type of multi-hop RLC ARQ and adaptation layer placement may have interdependencies: for end-to-end ARQ, the adaptation layer may be integrated with or placed above the MAC layer; and / or hop-by-hop ARQ may or may not be interdependent.

[0382] In an example, different IAB architecture options may have an impact on scheduling and / or QoS in the downlink and / or uplink directions.In an example, the adaptation layer may be placed above the RLC and / or above the MAC.

[0383] In an example, control plane (CP) signaling across wireless backhaul links may use the same routing and / or QoS enforcement mechanisms as user plane (UP) traffic. The priority and / or QoS requirements of CP signaling may be different from those of UP traffic.

[0384] In an example, signaling between an MT on an IAB node and a Central Unit Control Plan (CU-CP) on an IAB donor body may use the RRC protocol. Signaling between a DU on an IAB node and a CU-CP on an IAB donor body may use the F1-AP protocol. IAB-specific enhancements to RRC and F1-AP may be supported.

[0385] In an example, the RRC and F1-AP connections may be protected over the wireless backhaul link. The RRC connection may have at least the same level of protection over the wireless backhaul link as over the access link. In an example, the F1-AP connection may have at least the same level of protection over the wireless backhaul link as the RRC connection. In an example, the same level of protection for the F1-AP as for the RRC may be supported.

[0386] In an example, for CP signaling protection: PDCP can be used to protect RRC; and / or PDCP can be used to protect F1-AP through wireless backhaul. CP signaling protection based on the use of NDS can be supported.

[0387] In the example of architecture 1a, UP and / or RRC traffic of UE and / or MT may be protected via PDCP over the wireless backhaul. A CP protection mechanism may be defined to protect F1-AP traffic over the wireless backhaul.

[0388] In the example, for alternative 1 of architecture 1a, Fig.25The protocol stack for the RRC of the UE, the RRC of the MT, and / or the F1-AP of the DU is shown. In an example, the adaptation layer can be placed on top of the RLC. On the access link of the IAB node, the adaptation layer may or may not be included. In an example of alternative scheme 1 of architecture 1a, the RRC of the UE and / or the MT can be carried on the SRB. On the access link of the UE and / or the MT, the SRB can use the RLC channel. On the wireless backhaul link, the PDCP layer of the SRB can be carried on the RLC channel with the adaptation layer. The placement of the adaptation layer in the RLC channel can be the same for the C-plane as for the U-plane. The information carried on the adaptation layer can be different for the signaling radio bearer (SRB) than for the data radio bearer (DRB). The F1-AP of the DU can be encapsulated in the RRC of the juxtaposed MT. The F1-AP can be protected by the PDCP of the SRB below. The IAB donor can use the native F1-C stack.

[0389] In the example, for alternative 2 of architecture 1a, Fig.26 The protocol stack for the RRC of the UE, the RRC of the MT, and / or the F1-AP of the DU is shown. In an example, the adaptation layer may be located on top of the RLC. On the access link of the IAB node, the adaptation layer may or may not be included. In an example of alternative 2 of architecture 1a, the RRC of the UE and / or the MT may be carried on the SRB. On the access link of the UE and / or the MT, the SRB may use the RLC channel. On the wireless backhaul link, the PDCP of the SRB of the RRC may be encapsulated in the F1-AP. The F1-AP of the DU may be carried on the SRB of the juxtaposed MT. The F1-AP may be protected by the PDCP of this SRB. On the wireless backhaul link, the PDCP of the SRB of the F1-AP may be carried on the RLC channel with the adaptation layer. The placement of the adaptation layer in the RLC channel may be the same for the C-plane as for the U-plane. The information carried on the adaptation layer may be different for the SRB than for the DRB. The IAB donor may use the native F1-C stack.

[0390] In the example, for alternative 3 of architecture 1a, Fig. 27The protocol stack for the RRC of the UE, the RRC of the MT, and / or the F1-AP of the DU is shown. In an example, the adaptation layer may be located on top of the RLC. On the access link of the IAB node, the adaptation layer may or may not be included. In an example of alternative 3 of architecture 1a, the RRC of the UE and / or the MT may be carried on the SRB. On the access link of the UE and / or the MT, the SRB of the RRC may use the RLC channel. On the wireless backhaul link, the PDCP layer of the SRB may be carried on the RLC channel with the adaptation layer. The placement of the adaptation layer in the RLC channel may be the same for the C-plane as for the U-plane. The information carried on the adaptation layer may be different for the SRB than for the DRB. The F1-AP of the DU may be carried on the SRB of the juxtaposed MT. The F1-AP may be protected by the PDCP of the SRB. On the wireless backhaul link, the PDCP of the SRB may be carried on the RLC channel with the adaptation layer. The IAB donor may use the native F1-C stack.

[0391] In the example, for alternative 4 of architecture 1a, Fig.28 The protocol stack for the RRC of the UE, the RRC of the MT and / or the F1-AP of the DU is shown. In an example, the adaptation layer can be located on top of the RLC and / or can carry the IP layer. In the example of alternative 4 of architecture 1a, the IP layer carried by the adaptation can be connected to the IP plane of the fronthaul through the routing function at the IAB donor DU. On the IP layer, the IAB node can maintain an IP address, which can be routed from the IAB donor CU-CP. The extended IP plane can allow the use of native F1-C between the IAB node DU and the IAB donor CU-CP. Signaling services can be prioritized on the IP routing plane using DSCP markings. F1-C can be protected via NDS (e.g., via D-TLS). The RRC of the UE and / or MT can use SRB, which can be carried on F1-C.

[0392] In the example, for the alternative to architecture 1b, Fig.29The protocol stack for the RRC of the UE, the RRC of the MT and / or the F1-AP of the DU is shown. In an example, the adaptation layer of the PDCP carrying the DRB can be located on top of the RLC. On the access link of the IAB node, the adaptation layer may or may not be included. In an example of an alternative to architecture 1b, the RRC of the UE and / or the MT can be carried on the SRB. On the wireless backhaul, the PDCP of the SRB can be carried on the local F1-C. The DU on the IAB node and / or the IAB donor can use the native F1-C stack. Through the wireless reverse link, the PDU session can provide the IP layer of the native F1-C stack. A PDU session can be established between MTs co-located with the DU and / or UPF. The PDU session can be carried by the DRB between the MT and the CU-UP. Between the CU-UP and the UPF, the PDU session can be carried via the NG-U. The IP transmission between the UPF and the CU-CP can be provided by the DN of the PDU session. The IP transmission can be protected. DN protected F1-C transmission between UPF and CU-CP can be supported.

[0393] In an example, the IAB topology may include a spanning tree (ST) and / or a directed acyclic graph (DAG). The directionality of the Uu backhaul link defined by the uplink and the downlink may be aligned with the hierarchy of the ST and / or the DAG. For the ST, the IAB node may have a parent node, which may be an IAB node and / or an IAB donor body. For the ST, the IAB node may be connected to one IAB donor body at a time, and / or there may be a route between the IAB node and the IAB donor body. For the DAG, the IAB node may be multi-connected, that is, the IAB node may have links to multiple parent nodes. For the DAG, the IAB node may have multiple routes to a node (e.g., an IAB donor body). For the DAG, the IAB node may have redundant routes to the node via multiple parent nodes. In an example, multiple connectivity (e.g., dual connectivity) and / or route redundancy may be used. Redundant routes may be used simultaneously, for example, to achieve load balancing, reliability, and the like.

[0394] In the example, for architecture group 1, Fig.30 As shown, the routes of the IAB nodes may belong to: the same IAB donor DU, and the same IAB donor CU-CP and CU-UP ( Fig.30 a); different IAB donors DU, and the same IAB donors CU-CP and CU-UP ( Fig.30 b); different IAB donors DU, different IAB donors CU-UP and the same IAB donor CU-CP ( Fig.30 c); Different IAB donors DU, CU-CP and CU-UP ( Fig.30 d).

[0395] In the example, for architecture group 2, Fig.31 As shown, the routes of the IAB nodes may belong to the same IP domain and / or different IP domains. For at least some of these topologies, IP address management and / or for topology adaptation procedures may be supported.

[0396] In an example, the IAB node may be authenticated by the operator's network and / or may establish an IP connection to reach the OAM functions of the OAM configuration. The authentication phase may include the discovery and / or selection of a service node, which may be an IAB donor and / or an IAB node. The IAB node may retrieve IAB information, for example, from OAM and / or via RAN signaling such as OSI or RRC. The authentication phase may include establishing a connection with a RAN node and / or a core network (CN). The authentication phase may involve MT functions on the IAB node.

[0397] In an instance, the DU, gNB and / or UPF of the IAB node may be established together with an interface to the RAN node and / or CN. The interface establishment phase may be performed before the IAB node starts serving the UE and / or before the IAB node is connected. In an instance, for architectures 1a and 1b, the interface establishment phase may include the setup of the DU of the IAB node and / or the establishment of F1 of the CU-CP and / or CU-UP of the IAB body. In an instance, for architecture 2a, the interface establishment phase may include the setup of the gNB and / or UPF of the IAB node, and / or integration into the PDU session forwarding layer across the wireless backhaul. In an instance, the interface establishment phase may include integrating the IAB node into the topology and / or routing management.

[0398] In an example, the IAB node may provide services to the UE and / or the integrated IAB node. The UE may or may not distinguish between access to the IAB node and access to the gNB (e.g., eNB, RAN).

[0399] In an example, the IAB architecture of the IAB donor DU and / or IAB donor CU can be based on the CU / DU architecture of the gNB (e.g., RAN). Modifications to the IAB node DU that supports F1*-U over wireless backhaul can be supported.

[0400] In the example, Fig.32As shown, the IAB node is connected to a parent node, a child node and / or a wireless device (e.g., a UE). The IAB node can be connected to the IAB donor (e.g., the parent node of the IAB node) via a downlink parent backhaul (e.g., an F1 interface, an NG interface, an S1 interface, an Uu interface, an Xn interface) and / or an uplink parent backhaul (e.g., an F1 interface, an NG interface, an S1 interface, an Uu interface, an Xn interface). The IAB node can be connected to the child node of the IAB node via a downlink sub-backhaul (e.g., an F1 interface, an NG interface, an S1 interface, an Uu interface, an Xn interface) and / or an uplink sub-backhaul (e.g., an F1 interface, an NG interface, an S1 interface, an Uu interface, an Xn interface). The IAB node can be connected to a wireless device via a downlink access (e.g., a Uu interface) and / or an uplink access (e.g., a Uu interface).

[0401] In an example, a wireless device in an RRC connected state may experience (and / or determine) a connection failure from at least one cell in a base station. The connection failure may include a radio link failure (RLF) and / or a handover failure (HOF).

[0402] In an example, the wireless device may determine RLF when one of the following criteria is met: expiration of a timer started after a radio problem (e.g., out-of-sync) is indicated from the physical layer (if the radio problem recovers before the timer expires, the UE may stop the timer); a random access procedure failure; an RLC failure (e.g., the number of retransmissions exceeds a threshold); etc. In an example, after asserting RLF, the wireless device may: maintain an RRC_CONNECTED state (e.g., an RRC connected state); select a suitable cell and initiate RRC reestablishment; enter an RRC_IDLE state (e.g., an RRC idle state) if a suitable cell is not found within a certain time after asserting RLF; maintain an RRC_INACTIVE state (e.g., an RRC inactive state) if a suitable cell is not found within a certain time after asserting RLF; etc.

[0403] In an example, the behavior of a wireless device associated with RLF may include two phases. The first phase may start after a radio problem is detected; may result in RLF detection; may not initiate UE-based mobility; may be based on a timer (e.g., T1) or other criteria (e.g., count); etc. The second phase may start after RLF or HOF; may result in an RRC idle state of the wireless device; may initiate UE-based mobility; may be based on a timer (e.g., T2); etc. In an example, a wireless device in normal operation in an RRC connected state may experience a first phase including radio problem detection and no recovery during T1, and / or may experience a second phase including no recovery during T2. The second phase may be followed by an RRC idle state (e.g., the wireless device may enter an RRC idle state). During normal operation, the first phase, and / or the second phase, the wireless device may be considered to be in an RRC connected state. In an example, the RLF may be considered to occur between the first phase and the second phase (e.g., at the end time of the first phase and / or at the start time of the second phase).

[0404] In an example, upon detecting a physical layer problem of the PCell, i.e., upon receiving N310 consecutive out-of-sync indications from lower layers, the wireless device may start timer T310. After receiving N311 consecutive in-sync indications for the PCell from lower layers, and / or after triggering a handover procedure and after initiating a connection reestablishment procedure, the wireless device may stop T310. In an example, when timer T310 expires, the wireless device may enter the RRC_IDLE state if security is not activated; and / or the wireless device may initiate a connection reestablishment procedure if security is activated.

[0405] In an example, after initiating the RRC connection reestablishment procedure, the wireless device may start timer T311. After selecting a suitable cell of LTE / 5G / another RAT, the wireless device may stop T311. If T311 expires, the wireless device may enter the RRC_IDLE state.

[0406] In an example, the wireless device may detect a HOF that may occur due to a too-early handover, too-late handover, handover to a wrong cell, etc. In the case of a too-early handover, a radio link failure may occur shortly after a successful handover from a source cell to a target cell, and / or a handover failure may occur during a handover procedure. In the case of a too-early handover, the wireless device may attempt to reestablish a radio link connection in the source cell. In the case of a too-late handover, a radio link failure may occur after the wireless device may have stayed in the cell for a long time (e.g., a radio link failure may occur because the serving base station may not initiate a handover for the wireless device when the radio link quality is not sufficient to serve the wireless device in the current cell), and / or the wireless device may attempt to reestablish a radio link connection in a different cell. In the case of a handover to a wrong cell, a radio link failure may occur shortly after a successful handover from a source cell to a target cell, and / or a handover failure may occur during a handover procedure. In the case of a handover to a wrong cell, the UE may attempt to reestablish a radio link connection in a cell other than the source cell and the target cell. In an example, "successful handover" may refer to a state in which the wireless device successfully completes a random access (RA) procedure.

[0407] In an example, in order to solve the problem of connection failure (e.g., RLF and / or HOF), the wireless device and / or the network (e.g., base station, base station CU, base station DU, gNB, eNB, core network, etc.) may trigger one or more of the following functions: detection of connection failure after RRC reestablishment attempt; detection of connection failure after RRC connection setup; retrieval of information required for problem analysis; etc. The triggering of each of the functions may be optional and / or may depend on the situation and / or implementation.

[0408] In an example embodiment, a wireless device may be served via an intermediate network node (e.g., an integrated access and backhaul (IAB) node, an IAB donor, a base station, a gNB, a base station distributed unit (gNB-DU), a relay node), which may be connected to a radio access network (e.g., a gNB, a gNB-CU, an IAB donor, an eNB, a base station, a RAN node) via a radio backhaul link. The radio access network connected to the intermediate network node may be wired to a core network node (e.g., an AMF, an SMF, an UPF, an MME, an SGW, a PGW). The wireless device may be served by the radio access network and / or the core network node via the intermediate network node. When serving the wireless device via the intermediate network node, the link quality of the radio backhaul link of the intermediate network node may affect the serving wireless device. In an example, a blocking / failure / problem of the radio backhaul link may cause a failure of packet transmission and / or service of the wireless device. In an example, a blocking / failure / problem of the radio backhaul link may cause a connection failure (e.g., a radio link failure / switching failure) of the wireless device. Implementations of existing communication mechanisms for radio link failure (RLF) reporting may increase inefficiencies in configuring radio resource configuration parameters depending on the status of a radio backhaul link. Due to improper radio parameter configuration, existing techniques may increase connection latency and packet transmission delays for wireless devices. Existing techniques may reduce access reliability for wireless devices.

[0409] Implementations of example embodiments may enhance cellular communication reliability by providing an RLF reporting mechanism that takes into account backhaul link information of wireless devices that experience connection failures when served by an IAB node. Example embodiments may support communication of network nodes and / or wireless devices of status information of radio backhaul links. Example embodiments may support radio configuration of network nodes and / or wireless devices based on status information of radio backhaul links. Implementations of example embodiments may reduce connection latency and / or packet transmission delays for wireless devices. Implementations of example embodiments may increase access / communication reliability and / or mobility for wireless devices.

[0410] In an example embodiment, if Fig.33 and / or Fig.34As shown, a wireless device (e.g., UE, IAB node) can be served by a first network node (e.g., IAB donor, gNB-CU and / or gNB, eNB) and / or a second network node (e.g., IAB node 1, gNB-DU and / or gNB, eNB). The second network node can be connected to the first network node at least via a first radio link (e.g., link 1, radio backhaul link, backhaul link, Uu interface, F1 interface, NG interface, S1 interface) to serve the wireless device. In an example, the first radio link may include one or more radio links connected via one or more network nodes (e.g., one or more IAB donors / IAB nodes). In an example, a failure of the first radio link may include at least one failure of the one or more radio links. In an example, the wireless device can be connected to the second network node via a second radio link (e.g., link 2, Uu interface). In an example, the second network node can provide a primary cell for the wireless device. In an example, the second network node can be an intermediate network node between the first network node and the wireless device.

[0411] In an example, the first network node may include at least one of a base station, a base station (e.g., gNB, eNB), a central unit (e.g., gNB-CU), and / or an IAB donor (e.g., a relay donor node). In an example, the second network node may include at least one of a base station (e.g., gNB, eNB), a base station distributed unit (e.g., gNB-DU), and / or an IAB node (e.g., a relay node).

[0412] In an example, the third network node (e.g., second base station, gNB2, gNB, eNB) may or may not be a neighboring base station of the first network node and / or the second network node. The third network node may be connected to the first network node via an Xn interface (e.g., X2 interface) and / or via one or more NG interfaces (e.g., via one or more AMFs, S1 interfaces, one or more MMEs, one or more core network nodes). The third network node may include one or more IAB nodes and / or one or more IAB donors. The third network node may include one or more gNB-CUs and / or one or more gNB-DUs.

[0413] In an example, depending on the implementation of the IAB architecture group, the IAB donor (e.g., the first network node) may include gNB functionality (e.g., PHY / MAC / RLC / PDCP / SDAP layers), gNB-CU functionality (e.g., at least PDCP / SDAP layers), and / or UPF functionality for the wireless device and / or IAB node. In an example, depending on the implementation of the IAB architecture group, the IAB node (e.g., the second network node) may include gNB functionality (e.g., PHY / MAC / RLC / PDCP / SDAP layers) and / or gNB-DU functionality (e.g., at least MAC / PHY layers) for the wireless device. In an example, the wireless device may be an IAB node (or IAB donor) serving one or more wireless devices and / or one or more IAB nodes.

[0414] In an example, the first network node may include at least one of a base station, an integrated access and backhaul donor (IAB donor), and / or an integrated access and backhaul node (IAB node). In an example, the second network node may include at least one of an integrated access and backhaul donor (IAB donor) and / or an integrated access and backhaul node (IAB node). In an example, the third network node may include at least one of an integrated access and backhaul donor (IAB donor) and / or an integrated access and backhaul node (IAB node). In an example, the wireless device may include at least one of a user equipment, an integrated access and backhaul node (IAB node), and / or an integrated access and backhaul donor (IAB donor).

[0415] In an example, a downlink packet of the wireless device may be transmitted from the first network node to the wireless device via the second network node. The downlink packet may be a PDCP layer packet. The first network node may receive data of the downlink packet from one or more UPFs and / or one or more IAB donors. In an example, an uplink packet of the wireless device may be transmitted from the wireless device to the first network node via the second network node. The uplink packet may be a PDCP layer packet. The first network node may forward the data of the uplink packet to one or more UPFs and / or one or more IAB donors.

[0416] In the example, Fig.35 , Fig.36 , Fig.37 , Fig.38 , Fig.39 , Fig.40 , Fig.41 , Fig.42 , Fig.43 and / or Fig.44As shown, the wireless device may receive at least one radio resource control (RRC) message from a first network node (e.g., and / or from a second network node), the message including configuration parameters of a first cell of the second network node. In an example, the first cell may be a primary cell of the wireless device. In an example, the first cell may be a SpCell / PSCell of the wireless device.

[0417] In an example, if a first network node (e.g., IAB donor, gNB-CU) provides an RRC layer for a wireless device (e.g., in the case of IAB architecture group 1 and / or IAB architecture 2c), at least one RRC message may be transmitted by the first network node to a second network node (e.g., IAB node, gNB-DU) via a first radio link, and / or the second network node may forward / transmit at least one RRC message to the wireless device via a second radio link. In an example, if a second network node (e.g., IAB node, gNB) provides an RRC layer for a wireless device (e.g., in the case of IAB architecture group 2), at least one RRC message may be transmitted by the second network node to the wireless device via a second radio link.

[0418] In an example, the at least one RRC message may include at least one of the following: an RRC reconfiguration message, an RRC connection reconfiguration message, an RRC connection reestablishment message, an RRC connection setup message, an RRC connection recovery message, a downlink RRC message, a relay node reconfiguration message, etc. In an example, the at least one RRC message may include at least one of the following: a UE identifier of the wireless device (e.g., TMSI, C-RNTI, F1 UE identifier, NG UE identifier, IMSI), a cell identifier of the first cell (e.g., a physical cell identifier, PCI, a global cell identifier, GCI, CGI), cell information of the first cell (e.g., a cell index, a cell group configuration, a radio link failure timer and constant, an RLM synchronization / desynchronization threshold, synchronization reconfiguration including a t304 value, RACH configuration parameters including a preamble index and / or RACH resources, carrier frequency information, bandwidth part configuration parameters, beam configuration parameters of an SS beam and / or a CSI-RS beam, transmit power configuration parameters including p-MAX / p-MgNB / p-SgNB, etc.), a cell identifier of at least one cell (e.g., a physical cell identifier, PCI, a global cell identifier, GCI, CGI), cell information of at least one cell (e.g., cell index, cell group configuration, radio link failure timer and constant, RLM synchronization / desynchronization threshold, synchronization reconfiguration including t304 value, RACH configuration parameters including preamble index and / or RACH resource, carrier frequency information, bandwidth part configuration parameters, beam configuration parameters of SS beam and / or CSI-RS beam, transmit power configuration parameters including p-MAX / p-MgNB / p-SgNB, etc.), bearer identifier of the bearer, logical channel identifier (index) of the bearer, PDU session identifier of the bearer, QoS flow identifier of the bearer, IAB node identifier of the second network node, IAB donor identifier of the first network node, etc. In an example, the configuration parameters of the first cell (e.g., at least one RRC message) may include the cell identifier of the first cell and / or the cell information of the first cell.

[0419] In an example, the at least one RRC message may include one or more system information blocks (e.g., primary information block, system information block type 1, system information block type 2, system information block type 3, etc.). In an example, the one or more system information blocks may include a cell identifier of a first cell, cell information of the first cell, a cell identifier of at least one cell, cell information of at least one cell, etc. In an example, the at least one cell may include one or more secondary cells (e.g., of a primary cell group and / or a secondary cell group) of the wireless device.

[0420] In an example, at least one RRC message may include at least one of the following: an rrc transaction identifier information element (IE), a radio resource configuration dedicated IE including one or more radio resource configuration parameters, a measurement configuration parameter, a mobility control information parameter, one or more NAS layer parameters, a security parameter, an antenna information parameter, a secondary cell addition / modification parameter, a secondary cell release parameter, a WLAN configuration parameter, a WLAN offload configuration parameter, a LWA configuration parameter, a LWIP configuration parameter, an RCLWI configuration parameter, a side link configuration parameter, a V2X configuration parameter, an uplink transmit power configuration parameter (e.g., p-MAX, p-MeNB, p-SeNB), a power control mode information element, a secondary cell group configuration parameter, etc.

[0421] In an example, in response to receiving at least one RRC message, the wireless device may transmit at least one confirmation / response message (e.g., at least one RRC confirmation / response message) to the first network node (e.g., in the case of IAB architecture group 1 and / or IAB architecture group 2c) and / or to the second network node (e.g., in the case of IAB architecture group 2) via the second network node.

[0422] The at least one confirmation / response message may include at least one RRC confirmation / response message. In an example, the at least one confirmation / response message may include at least one of the following: an uplink RRC message, a relay node reconfiguration complete message, an RRC connection reconfiguration complete message, an RRC connection reestablishment complete message, an RRC connection recovery complete message, an RRC connection setup complete message, etc. The at least one confirmation / response message may indicate whether the wireless device successfully configured one or more elements of the at least one RRC message (e.g., one or more of the configuration parameters of the first cell). The at least one confirmation / response message may indicate whether the wireless device successfully established a bearer.

[0423] In an example, the wireless device may transmit a packet to the second network node based on configuration parameters received from the first network node and / or the second network node (e.g., via the first cell and / or via at least one cell) and / or one or more elements of at least one RRC message (e.g., based on RLC / PDCP / MAC configuration parameters and / or physical layer configuration received via at least one RRC message, e.g., transmitting at a power level corresponding to p-MAX). The second network node may forward / transmit the packet to the first network node. The first network node may forward / transmit the packet (e.g., data of the packet) to one or more UPFs and / or one or more serving gateways. In an example, the wireless device may transmit the packet to the second network node via a bearer, e.g., based on at least one RRC message. The second network node may forward the packet (or data of the packet) (e.g., an uplink packet) to the first network node via a bearer.

[0424] In an example, the wireless device may receive a packet from the second network node based on configuration parameters received from the first network node and / or the second network node (e.g., via the first cell and / or via at least one cell) and / or one or more elements of at least one RRC message (e.g., based on RLC / PDCP / MAC configuration parameters and / or physical layer configuration received via at least one RRC message, e.g., receiving the packet via resources allocated based on resource coordination parameters configured by at least one RRC message). The second network node may receive the packet from the first network node. The first network node may receive the packet (e.g., data of the packet) from one or more UPFs and / or from one or more serving gateways. In an example, the wireless device may receive the packet from the second network node via a bearer, e.g., based on at least one RRC message. The second network node may receive the packet (or data of the packet) (e.g., a downlink packet) from the first network node via a bearer.

[0425] In an example, the wireless device may determine a connection failure from a first network node (e.g., and / or a second network node) based on a backhaul link failure (e.g., a backhaul link problem, a backhaul link congestion). In an example, the connection failure may include at least one of a radio link failure and / or a handover failure. In an example, the connection failure may include a backhaul link failure. In an example, the backhaul link failure may include a failure (e.g., a problem, a congestion, a failure, an unavailability, a disconnection, an interruption) of a first radio link established between the first network node and the second network node. In an example, the first radio link may include one or more radio links connected via one or more network nodes. The failure (e.g., a problem, a congestion, a failure, an unavailability, a disconnection, an interruption) of the first radio link may indicate at least one failure of the one or more radio links.

[0426] The backhaul link failure may include (e.g. and / or may be attributed to) a connection failure (e.g., radio link failure, handover failure) of the second network node. The backhaul link failure may include (e.g. and / or may be attributed to) a congestion (e.g., failure, problem, failure, unavailability, disconnection, interruption) of the second network node (e.g., temporary failure of signaling with the first network node). The congestion of the first radio link (e.g. and / or backhaul link failure) may include at least one of the following: a beam failure of a cell (e.g., a cell serving the second network node); a beam failure recovery failure of a cell (e.g., a cell serving the second network node); expiration of a time alignment timer of a cell (e.g., a cell serving the second network node); a first value of a radio link control (RLC) packet retransmission (and / or HARQ retransmission) of the second network node is equal to or greater than a first count value; a reference signal received power / quality (RSRP / RSRQ) of the second network node from a cell (e.g., a cell serving the second network node) is equal to or less than a first power / quality value; expiration of a congestion timer (e.g., the time of the congestion timer has passed due to congestion determined by the second network node); and the like.

[0427] In an example, in the case of IAB architecture group 1 and / or IAB architecture group 2c (e.g., the RRC function is located at the IAB donor (e.g., located at the first network node)), the connection failure of the wireless device from the first network node may include an RRC connection failure (e.g., and / or an RLC / MAC layer connection failure, an F1 connection failure). In an example, in the case of IAB architecture group 2 (e.g., the RRC function is located at the IAB node (e.g., at the second network node)), the connection failure of the wireless device from the first network node may include a backhaul link problem (and / or failure) (e.g., an NG connection failure, a backhaul link failure).

[0428] In an example, the wireless device may determine a backhaul link failure based on an indication from the second network node and / or based on an upper layer packet transmission status (e.g., RLC packet transmission failure, no ACK received from a transmitted RLC packet, NACK received for a transmitted RLC packet, and / or the number of RLC packet retransmissions is equal to or greater than a configured value).

[0429] In an example, the wireless device may receive backhaul link failure information indicating a failure (e.g., a problem, a blockage) of a first radio link established between the first network node and the second network node from the second network node. In an example, the wireless device may determine a connection failure based on the backhaul link failure information. In an example, the wireless device may receive a connection release indication from the second network node. The connection release indication may include the backhaul link failure information. The connection release indication may command / instruct the wireless device to release the connection from the second network node (e.g., the first cell) and / or from the first network node. The second network node may transmit a connection release indication in response to determining a backhaul link failure (e.g., a problem) indicated via the backhaul link failure information.

[0430] In an example, the wireless device may receive a connection release indication and / or backhaul link failure information via at least one of a medium access control control element (MAC CE), a physical layer command including downlink control information (DCI), an adaptation layer indication, one or more user plane packets, and / or a radio resource control message (e.g., an RRC connection release message, a downlink RRC message, an RRC connection reconfiguration message). In an example, the adaptation layer indication may include at least one of: at least one of the one or more (e.g., adaptation layer) packets (e.g., including data of the packets); and / or a header of at least one of the one or more (e.g., adaptation layer) packets (e.g., including data of the packets).

[0431] In an example, the backhaul link failure information may include at least one of the following: a first node identifier of the first network node; a second node identifier of the second network node; a failure (e.g., congestion, problem) type of the backhaul link failure (e.g., including at least one of the following: temporary congestion; failure of at least one backhaul link among multiple backhaul links of the second network node; and / or failure of all backhaul links of the second network node); a timer value, the timer value being used to determine an integrated access and backhaul node failure (e.g., the wireless device may determine the backhaul link failure in response to expiration of a timer of the timer value; the timer may be started in response to receiving the backhaul link failure information); an indication parameter indicating that the state of one or more cells of the second network node is transitioned to a dormant state; an indication parameter indicating the release of one or more cells of the second network node; a first radio link the cause value of the failure of the first radio link (e.g., RLF cause, number of RLC retransmissions, failure timer expiration, beam failure recovery failure, random access failure, time alignment timer expiration); bearer identifiers of bearers affected by the failure of the first radio link; one or more beam identifiers of one or more beams of a cell (e.g., a cell employed by the second network node) (e.g., a cell of the first network node) (e.g., a cell causing the first radio link failure); one or more bandwidth part (BWP) identifiers of one or more BWPs of a cell (e.g., a cell employed by the second network node) (e.g., a cell of the first network node) (e.g., a cell causing the first radio link failure); and / or a cell identifier of a cell (e.g., a cell employed by the second network node) (e.g., a cell of the first network node) (e.g., a cell causing the first radio link failure).

[0432] In an instance, the backhaul link failure information may include a node identifier of a network node of one or more network nodes between the first network node and the second network node (e.g., an access radio link of the network node experienced a failure / blockage / problem; e.g., the access radio link of the network node is / includes one of the (faulty) one or more radio links connected via one or more network nodes between the first network node and the second network node).

[0433] In an example, the indication of the backhaul link failure information may include (e.g., via a MAC CE) an indication parameter indicating that a state transition is made to a dormant state of one or more cells of the second network node. In an example, if the indication parameter indicates that all cells or a portion of all cells of the second network node of the wireless device transition to a dormant state, the wireless device may consider that the first radio link has experienced congestion (e.g., failure).

[0434] In an example, the indication of the backhaul link failure information may include (e.g., via a MAC CE) an indication parameter indicating deactivation of one or more cells of the second network node. In an example, if the indication parameter indicates that all cells or a portion of all cells of the second network node of the wireless device are deactivated, the wireless device may consider that the first radio link has experienced congestion (e.g., failure).

[0435] In an instance, the second network node may determine a failure (e.g., blocking) of the first radio link based on at least one of the following: a radio link failure (e.g., from the first network node and / or from one or more network nodes connecting the first network node and the second network node), a handover failure, a beam failure of a cell serving the second network node; a beam failure recovery failure of a cell (e.g., a cell serving the second network node; e.g., a cell of the first network node); a random access failure via a cell (e.g., a cell serving the second network node; e.g., a cell of the first network node); expiration of a time alignment timer of a cell (e.g., a cell serving the second network node; e.g., a cell of the first network node); a first value of radio link control (RLC) packet retransmissions (or HARQ retransmissions) to the first network node exceeds a first value; a reference signal reception power / quality of a cell (e.g., a cell serving the second network node; e.g., a cell of the first network node) and / or one or more beams of a cell (e.g., a cell serving the second network node; e.g., a cell of the first network node) is (becomes) less than or equal to a power / quality value; expiration of a blocking timer; and the like.

[0436] In an example, if the second network node determines a beam failure of one or more service beams of the cell of the first network node (and / or a cell serving the second network node), the second network node may determine a blocking (e.g., failure) of the first radio link. In an example, when the second network node determines a beam failure of one or more service beams of the cell of the first network node (and / or a cell serving the second network node), the second network node may start a blocking timer and / or may determine a blocking (e.g., failure) of the first radio link in response to expiration of the blocking timer.

[0437] In an example, if the second network node determines a beam failure recovery failure of one or more beam failure recovery procedures for one or more service beams of a cell of the first network node (and / or a cell serving the second network node), the second network node may determine a blocking (e.g., failure) of the first radio link. In an example, when the second network node determines a beam failure recovery failure of one or more beam failure recovery procedures for one or more service beams of a cell of the first network node (and / or a cell serving the second network node), the second network node may start a blocking timer in response to expiration of the blocking timer and / or may determine a blocking (e.g., failure) of the first radio link.

[0438] In an example, if the second network node determines a random access failure of a cell of the first network node (and / or a cell serving the second network node), the second network node may determine a blocking (e.g., failure) of the first radio link. In an example, when the second network node determines a random access failure of a cell of the first network node (and / or a cell serving the second network node), the second network node may start a blocking timer and / or may determine a blocking (e.g., failure) of the first radio link in response to expiration of a blocking timer.

[0439] In an example, if the second network node determines that a time alignment timer of a cell of the first network node (and / or a cell serving the second network node) expires, the second network node may determine a blocking (e.g., failure) of the first radio link. In an example, when the second network node determines that a time alignment timer of a cell of the first network node (and / or a cell serving the second network node) expires, the second network node may start a blocking timer and / or may determine a blocking (e.g., failure) of the first radio link in response to the expiration of the blocking timer. In an example, when the second network node receives a timing advance command (TAC) from the first network node, the second network node may determine recovery from the blocking of the first radio link.

[0440] In an example, if the second network node determines that a first value of radio link control packet retransmissions (or HARQ retransmissions) to the first network node becomes / is equal to or greater than a count value, the second network node may determine a blocking (e.g., failure) of the first radio link. In an example, when the second network node determines that a first value of radio link control packet retransmissions (or HARQ retransmissions) to the first network node becomes / is equal to or greater than the count value, the second network node may start a blocking timer and / or may determine a blocking (e.g., failure) of the first radio link in response to expiration of a blocking timer.

[0441] In an example, if the second network node determines that a reference signal received power / quality (RSRP / RSRQ) of one or more beams of a cell of the first network node (and / or a cell serving the second network node) and / or the RSRP / RSRQ of the cell of the first network node (and / or a cell serving the second network node) becomes / is equal to or is less than a power / quality value, the second network node may determine a blocking (e.g., failure) of the first radio link. In an example, when the second network node determines that the RSRP / RSRQ of one or more beams of the cell of the first network node (and / or a cell serving the second network node) and / or the RSRP / RSRQ of the cell of the first network node (and / or a cell serving the second network node) becomes / is equal to or is less than a power / quality value, the second network node may start a blocking timer and / or may determine a blocking (e.g., failure) of the first radio link in response to expiration of the blocking timer.

[0442] In an example, in response to determining a backhaul link failure, the wireless device may release a bearer established via the second network node and / or via the first network node. In an example, in response to determining a backhaul link failure, the wireless device may release a first cell of the second network node. In an example, in response to determining a backhaul link failure, the wireless device may release the first network node and / or the second network node. In an example, in response to determining a backhaul link failure, the wireless device may release a configuration (e.g., RRC configuration, MAC configuration, PDCP configuration, RLC configuration, SDAP configuration, PHY configuration, bearer configuration, security configuration, UL / DL resource configuration, power configuration, cell configuration, beam configuration, etc.) of the second network node and / or the first network node.

[0443] In an example, the wireless device may stop transmitting a scheduling request for a bearer and / or for one or more bearers (e.g., a resource request for an uplink transmission) to the second network node in response to determining a backhaul link failure. In an example, in response to determining a backhaul link failure, the wireless device may flush a hybrid automatic repeat request buffer of a cell (e.g., a first cell) of the second network node. In an example, in response to determining a backhaul link failure, the wireless device may suspend (e.g., clear, release) a configured uplink grant type 1 of the cell of the second network node. In an example, in response to determining a backhaul link failure, the wireless device may clear a configured downlink allocation of the cell of the second network node.

[0444] In an example, in response to determining the backhaul link failure, the wireless device may clear (e.g., suspend, release) a configured uplink grant type 2 for the cell of the second network node. In an example, in response to determining the backhaul link failure, the wireless device may stop (e.g., suspend) a bandwidth portion inactivity timer for one or more bandwidth portions of the cell of the second network node (e.g., considering that the cell is suspended and / or transitioned to a dormant / deactivated state). In an example, in response to determining the backhaul link failure, the wireless device may start (e.g., restart) a bandwidth portion inactivity timer for the cell of the second network node (e.g., considering receiving backhaul link blocking information as receiving a downlink indication via the cell and / or the corresponding bandwidth portion).

[0445] In an example, in response to determining a backhaul link failure, the wireless device may stop (e.g., terminate) a random access procedure (e.g., an ongoing random access procedure) on a cell of the second network node (e.g., stop transmitting a random access preamble and / or stop monitoring a random access response). In an example, in response to determining a backhaul link failure, the wireless device may stop (e.g., pause) a secondary cell deactivation timer of a cell of the second network node (e.g., considering that the cell is suspended and / or transitioned to a dormant / deactivated state). In an example, in response to determining a backhaul link failure, the wireless device may start (e.g., restart) a secondary cell deactivation timer of a cell of the second network node (e.g., considering receiving backhaul link blocking information via the cell as receiving a downlink indication). In an example, in response to determining a backhaul link failure, the wireless device may transition the cell of the second network node to a dormant state. In an example, in response to determining a backhaul link failure, the wireless device may deactivate the cell of the second network node.

[0446] In an example, in response to determining the backhaul link failure, the wireless device may stop transmitting transport blocks to the second network node (e.g., via the configured grant type 1 and / or type 2 resources). In an example, in response to determining the backhaul link failure, the wireless device may stop transmitting a buffer status report (BSR) (e.g., of the first bearer and / or a logical channel of the first bearer) to the second network node. In an example, in response to determining the backhaul link failure, the wireless device may stop transmitting a power headroom report (PHR) to the second network node.

[0447] In an example, in response to determining a backhaul link failure, the wireless device may stop transmitting a sounding reference signal (SRS) to the second network node via one or more cells (e.g., considering that the one or more cells are suspended and / or transitioned to a dormant / deactivated state). In an example, in response to determining a backhaul link failure, the wireless device may transmit a sounding reference signal (SRS) to the second network node via one or more cells (e.g., for the second network node to monitor an access link).

[0448] In an example, in response to determining a backhaul link failure, the wireless device may stop transmitting channel state information (e.g., CSI) to the second network node (e.g., considering that a cell of the second network node is suspended and / or transitioned to a dormant / deactivated state). In an example, in response to determining a backhaul link failure, the wireless device may transmit channel state information (e.g., CSI) to the second network node (e.g., for a cell transitioning to a dormant state; and / or the second network node monitoring an access link).

[0449] In an example, in response to determining the backhaul link failure, the wireless device may stop transmitting transport blocks to the second network node via an uplink shared channel (e.g., SCH, PUSCH). In an example, in response to determining the backhaul link failure, the wireless device may stop transmitting preambles to the second network node via a random access channel (e.g., RACH).

[0450] In an example, in response to determining the backhaul link failure, the wireless device may stop monitoring a physical downlink control channel (PDCCH) of a cell of the second network node (e.g., if a recovery and / or failure indication of the first radio link is transmitted via other links (e.g., via the first network node and / or the third network node) or via other cells than the cell). In an example, in response to determining the backhaul link failure, the wireless device may monitor a physical downlink control channel (PDCCH) of a cell of the second network node (e.g., to receive a recovery and / or failure indication for the first radio link).

[0451] In an example, in response to determining the backhaul link failure, the wireless device may stop monitoring a physical downlink control channel (PDCCH) of the cell of the second network node (e.g., considering that the cell of the second network node is suspended and / or transitioned to a dormant / deactivated state). In an example, in response to determining the backhaul link failure, the wireless device may monitor a physical downlink control channel (PDCCH) of the cell of the second network node (e.g., to receive a recovery and / or failure indication for the first radio link).

[0452] In an example, in response to determining the backhaul link failure, the wireless device may stop transmitting a physical uplink control channel (PUCCH) via the cell of the second network node. In an example, in response to determining the backhaul link failure, the wireless device may transmit a physical uplink control channel (PUCCH) via the cell of the second network node (e.g., to indicate release / deactivation / transition to a dormant state of the cell of the second network node).

[0453] In an example, in response to determining a backhaul link failure, the wireless device may transmit at least one of: channel quality information (e.g., CQI) of a cell of a second network node; a precoding matrix index (PMI) of the cell of the second network node; a rank indicator (RI) of the cell of the second network node; a precoding type indicator of the cell of the second network node; a channel state information reference signal (CSI-RS) resource indicator of the cell of the second network node; and / or channel state information (e.g., CSI) of the cell of the second network node.

[0454] In an example, in response to determining a backhaul link failure and / or a connection failure (e.g., and / or in response to releasing the first cell, the second network node, and / or the first network node), the wireless device may transition the RRC state from an RRC connected state to an RRC idle state or an RRC inactive state.

[0455] In an example, in response to determining a backhaul link failure and / or a connection failure (e.g., and / or in response to releasing the first cell, the second network node, and / or the first network node), the wireless device may select a second cell of the third network node for radio resource control connection (e.g., RRC connection establishment and / or RRC connection reestablishment). In an example, the wireless device may select the second cell based on measurement results of one or more cells. The one or more cells may include at least one of the first cell, the second cell, and / or one or more neighboring cells of the second cell and / or the first cell.

[0456] In an example, the third network node may be the first network node. In an example, the third network node may be the second network node. In an example, the third network node may include the first network node and the second network node. In an example, the first cell may be the second cell. In an example, the first cell may be a cell different from the second cell.

[0457] In an example, the measurement results may include reference signal received power (RSRP) and / or reference signal received quality (RSRQ) of the one or more cells, RSRP / RSRQ of one or more beams of the one or more cells, and / or RSRP / RSRQ of a group of multiple beams of the one or more cells. In an example, in response to the RSRP / RSRQ of the second cell and / or one or more beams (or a group of beams) of the second cell being equal to and / or greater than a power value (e.g., δdB) and / or a quality value (e.g., γdB), the wireless device may select the second cell. In an example, in response to the RSRP / RSRQ of the second cell and / or one or more beams (or a group of beams) of the second cell being equal to and / or greater than the RSRP / RSRQ of one or more neighboring cells of the second cell and / or one or more beams (or a group of beams) of the one or more neighboring cells, the wireless device may select the second cell.

[0458] In an example, in response to the second cell not belonging to a list of cells not allowed to be accessed (eg, blacklist cells) and / or belonging to a list of cells allowed to be accessed (eg, whitelist cells), the wireless device may select the second cell. The wireless device may select the second cell in response to at least one of the following: the second cell is an allowed closed user group; the second cell supports necessary network slices (e.g., based on NSSAI / S-NSSAI / network slice information broadcast via the system information block of the second cell and / or based on NSSAI / S-NSSAI required by the application layer of the wireless device); network capability information (e.g., RAN capabilities of the third network node and / or the second cell); parameter sets / TTIs supported by the second cell; congestion levels of the second cell and / or the one or more neighboring cells (e.g., congestion levels received via one or more system information blocks of the second cell); backhaul link capacity of the third network node (e.g., information on backhaul link capacity received via one or more system information blocks of the second cell); backhaul link reliability of the third network node (e.g., information on backhaul link reliability received via one or more system information blocks of the second cell); backhaul link congestion of the third network node (e.g., information on backhaul link congestion received via one or more system information blocks of the second cell); and the like.

[0459] In an example, in response to selecting a second cell of a third network node, the wireless device may be located on the second cell. In an example, in response to selecting the second cell of the third network node, the wireless device may initiate a random access procedure by transmitting one or more random access preambles to the third network node via the second cell, for example, to establish an RRC connection with the third network node via the second cell. In an example, the wireless device may transmit one or more random access preambles via the second cell. The wireless device may receive a random access response to the one or more random access preambles from the third network node. In an example, the wireless device may transmit a radio resource control (RRC) connection (e.g., reestablishment and / or establishment) request message (e.g., RRC connection establishment / setting / recovery request message and / or RRC connection establishment / setting / recovery complete message) to the third network node based on the random access response, for example, to request RRC connection establishment / setting / recovery. In an example, the RRC connection request message may include an indication field indicating that the wireless device has experienced a connection failure (e.g., RLF, HOF, reconfiguration failure, backhaul link failure / blocking / problem, other failures, etc.). The indication field may indicate a reason (e.g., establishment reason) for the RRC connection reestablishment / setup / recovery request. In an example, the RRC connection request message (e.g., an RRC connection reestablishment / setup / recovery request message and / or an RRC connection reestablishment / setup / recovery complete message) may include a report indication indicating that the wireless device has a report about a connection failure to be transmitted to the base station (e.g., a third network node) (e.g., an event to be reported, an RLF report, a connection failure report).

[0460] In an example, the wireless device may transmit a radio link failure (RLF) report (e.g., a connection failure report, a backhaul link failure report) to the third network node. The RLF report may include a cause value for the connection failure (e.g., and / or backhaul link failure). The cause value may indicate that the backhaul link failure caused the connection failure.

[0461] In an example, an RRC connection request message (e.g., an RRC connection reestablishment / setup / recovery request message and / or an RRC connection reestablishment / setup / recovery complete message) may include an RLF report. In an example, a report message (e.g., a UE information message) transmitted from the wireless device to the third network node may include an RLF report.

[0462] In an example, the wireless device may receive a report request message (e.g., a UE information request message) from a third network node, the report request message indicating a request to transmit an RLF report to the third network node. The third network node may transmit the report request message based on (and / or in response to) a report indication of an RRC connection request message (e.g., an RRC connection reestablishment / setup / recovery request message and / or an RRC connection reestablishment / setup / recovery complete message) received from the wireless device. In an example, in response to receiving the report request message (e.g., a UE information request message), the wireless device may transmit a report message (e.g., a UE information message) including the RLF report to the third network node. In an example, the report request message (e.g., a UE information request message) and / or the report message (e.g., a UE information message) may be an RRC message. In an example, the wireless device may transmit the RLF report (e.g., a report message and / or a UE information message) to the third network node in response to receiving the report request message (e.g., a UE information request message) from the third network node.

[0463] In an example, the cause value of the connection failure (e.g., transmitted by the wireless device to the third network node via the RLF report) may indicate a reason / reason why the wireless device determined a connection failure and / or a backhaul link failure when served by the second network node and / or the first network node. In an example, the cause value of the connection failure (e.g., transmitted by the wireless device to the third network node via the RLF report) may indicate a reason / reason why the second network node determined a backhaul link failure when the second network node served the wireless device. In an example, the cause value may include backhaul link failure information received by the wireless device from the second network node.

[0464] In an example, the cause value may include one or more fields indicating at least one of: a beam failure of a cell serving the second network node (and / or a cell identifier of the cell; one or more beam identifiers of one or more beams of the beam failure); a beam failure recovery failure of a cell serving the second network node (and / or a cell identifier of the cell; one or more beam identifiers of one or more beams of the beam failure recovery failure); an expiration of a time alignment timer (TAT) of the cell serving the second network node (and / or a cell identifier of the cell whose TAT expired); a radio link control (RLC) packet retransmission of the second network node (and / or a cell identifier of the cell whose TAT expired); or HARQ retransmission) is equal to or greater than a first count value; a reference signal received power / quality (RSRP / RSRQ) of a second network node from the cell is equal to or less than a first power / quality value (and / or a cell identifier of the cell of the RSRP / RSRQ); RSRP / RSRQ of the second network node from one or more beams of the cell is equal to or less than a second power / quality value (and / or a cell identifier of the cell and / or one or more beam identifiers of the one or more beams of the RSRP / RSRQ); expiration of a blocking timer (e.g., the blocking timer expires due to blocking determined by the second network node); and the like.

[0465] In an example, the cause value may indicate that the wireless device determines a backhaul link failure based on an indication from the second network node and / or based on an upper layer packet transmission status (e.g., RLC packet transmission failure, no ACK received from a transmitted RLC packet, NACK received for a transmitted RLC packet, and / or the number of RLC packet retransmissions is equal to or greater than a configured value). In an example, the cause value may indicate a failure (e.g., problem, congestion) of a first radio link established between the first network node and the second network node.

[0466] In an example, the cause value may indicate / include at least one of the following: a first node identifier of the first network node; a second node identifier of the second network node; a failure (e.g., congestion, problem) type of the backhaul link failure (e.g., including at least one of the following: temporary congestion; failure of at least one backhaul link among multiple backhaul links of the second network node; and / or failure of all backhaul links of the second network node); a timer value, the timer value being used to determine an integrated access and backhaul node failure (e.g., the wireless device may determine a backhaul link failure in response to expiration of a timer of the timer value; the timer may be started in response to receiving backhaul link failure information); an indication parameter indicating that the state of one or more cells of the second network node is transitioned to a dormant state; an indication parameter indicating the release of one or more cells of the second network node; a failure / problem / blockage of the first radio link; the cause value (e.g. RLF cause, number of RLC retransmissions, failure timer expiration, beam failure recovery failure, random access failure, time alignment timer expiration) of the congestion (e.g. backhaul link failure); bearer identifiers of bearers affected by the failure of the first radio link; one or more beam identifiers of one or more beams of a cell (e.g. a cell employed by the second network node) (e.g. a cell of the first network node) (e.g. a cell causing the first radio link failure); one or more bandwidth part (BWP) identifiers of one or more BWPs of a cell (e.g. a cell employed by the second network node) (e.g. a cell of the first network node) (e.g. a cell causing the first radio link failure); and / or a cell identifier of a cell (e.g. a cell employed by the second network node) (e.g. a cell of the first network node) (e.g. a cell causing the first radio link failure).

[0467] In an instance, the cause value may include a node identifier of a network node of one or more network nodes between the first network node and the second network node (e.g., an access radio link of the network node experienced a failure / blockage / problem; e.g., the access radio link of the network node is / includes one of the (faulty) one or more radio links connected via one or more network nodes between the first network node and the second network node).

[0468] In an instance, the cause value may include one or more fields indicating that the second network node determines a failure (e.g., blocking) of the first radio link based on at least one of the following: a radio link failure (e.g., from the first network node and / or from one or more network nodes connecting the first network node and the second network node), a handover failure, a beam failure of a cell serving the second network node; a beam failure recovery failure of a cell (e.g., a cell serving the second network node; e.g., a cell of the first network node); a random access failure via a cell (e.g., a cell serving the second network node; e.g., a cell of the first network node); an expiration of a time alignment timer of a cell (e.g., a cell serving the second network node; e.g., a cell of the first network node); a first value of radio link control (RLC) packet retransmissions (or HARQ retransmissions) to the first network node exceeds a first value; a reference signal reception power / quality of a cell (e.g., a cell serving the second network node; e.g., a cell of the first network node) and / or one or more beams of a cell (e.g., a cell serving the second network node; e.g., a cell of the first network node) is (becomes) less than or equal to a power / quality value; an expiration of a blocking timer; and the like.

[0469] In an instance, the RLF report may include at least one of the following: an identifier of the first network node; an identifier of the second network node; a base station identifier of the second network node; an integrated access and backhaul identifier of the second network node; a transmit and receive point identifier of the second network node; a cell identifier of the first cell; a beam identifier of the first cell; a beam group identifier of one or more beams of the first cell; an F1 wireless device identifier of the wireless device; an information element indicating that a backhaul link failure caused a connection failure; a failure (e.g., congestion, problem) type (e.g., including at least one of the following: temporary congestion; failure of at least one of multiple backhaul links of the second network node; and / or failure of all backhaul links of the second network node); a timer value, the timer value being used to determine an integrated access and backhaul node failure; a cause value of the failure of the first radio link; and / or a cell identifier of a cell (e.g., a cell of the first network node and / or a cell employed by the second network node) (e.g., a cell that caused the first radio link failure).

[0470] In an example, the RLF report may include at least one of a cell identifier of the first cell, a BWP index of a BWP (e.g., a BWP index of an active BWP when determining a connection failure), etc. In an example, the RLF report may include one or more elements of a BWP configuration parameter. The RLF report may include parameters (of the BWP configuration parameter) indicating at least one of: a plurality of BWP indices of a plurality of BWPs; a plurality of BWP bandwidths of a plurality of BWPs; a default BWP index of a default BWP of a plurality of BWPs; a BWP inactivity timer; an initial BWP index of an initial BWP of a plurality of BWPs (e.g., an initial active BWP); a subcarrier spacing of a plurality of BWPs; a cyclic prefix; a number of consecutive PRBs; an index in a set of one or more DL BWPs and / or one or more UL BWPs; a link between a DL BWP and a UL BWP from a set of configured DL BWPs and UL BWPs; a DCI detection of a PDSCH reception timing value; a PDSCH reception of a HARQ-ACK transmission timing value; a DCI detection of a PUSCH transmission timing value; a first PRB of a DL bandwidth or a UL bandwidth relative to a first PRB of a bandwidth, respectively; etc.

[0471] In an example, the RLF report may include one or more report IEs indicating information associated with a connection failure of the wireless device. The one or more report IEs may indicate at least one of: a faulty cell identifier of a faulty cell (e.g., a first cell and / or a cell serving a second network node at the time of a backhaul link failure / blockage / problem and / or a connection failure), wherein the wireless device experienced a connection failure during use of the faulty cell; an RLF cause of the connection failure, wherein the RLF cause indicates at least one of t310 expiration, a random access problem, a maximum number of radio link control (RLC) retransmissions, or t312 expiration; a wireless device identifier of the wireless device (e.g., C-RNTI, IMEI, TMSI) and / or a network node identifier of a second network node at the faulty cell (e.g., IAB-node identifier, gNB identifier, UE identifier, gNB-DU identifier, C-RNTI); a carrier frequency value of the faulty cell; A first time value (e.g., timeConnFailure), which indicates the time elapsed from the last handover initialization of the wireless device to the connection failure; a second time value (e.g., timeSinceFailure), which indicates the time elapsed since the connection failure (or establishment failure); a connection failure type, which indicates whether the connection failure and / or the backhaul link failure is caused by RLF or a handover failure; a measurement result, which includes at least one of the RSRP or RSRQ of the failed cell; a measurement result, which includes at least one of the RSRP or RSRQ of one or more neighboring cells of the failed cell; a quality classification indication 1 bearer, which indicates that a connection failure and / or a backhaul link failure occurred when a bearer with a QCI value equal to 1 is configured; a C-RNTI of the wireless device at the first cell; and the like.

[0472] In an example, a fault cell identifier of a faulty cell (e.g., a first cell and / or a cell serving a second network node when a backhaul link failure / blockage / problem occurs) may include a global cell identifier (e.g., NCGI, ECGI, CGI, etc.), a physical cell identifier (e.g., PCI), etc. In an example, when a connection failure occurs, the faulty cell may be a primary cell of a wireless device. In an example, when a connection failure occurs, the faulty cell may be a primary cell of a second network node.

[0473] In an example, the cause value of the connection failure may indicate that the cause of determining the connection failure of the wireless device includes at least one of t310 expiration, random access problem (e.g., failure), maximum number of radio link control (RLC) retransmissions, t312 expiration, etc. In an example, the cause value of the backhaul link failure may indicate that the cause of determining the backhaul link failure of the wireless device (e.g., access link failure of the second network node) includes at least one of the following: t310 expiration, random access problem (e.g., failure), maximum number of radio link control (RLC) retransmissions, t312 expiration, etc.

[0474] In an example, the expiration of t310 may indicate that the timer t310 of the wireless device and / or the second network node expires at the faulty cell when a connection failure (e.g., a backhaul link failure) occurs. When the wireless device and / or the second network node detects a physical layer-related problem (e.g., for a primary cell) (e.g., when the wireless device and / or the second network node receives a certain number (e.g., N310) of consecutive out-of-sync indications from a lower layer), the timer t310 may be started. In an example, the timer t310 may be stopped: when the wireless device and / or the second network node receives a certain number (e.g., N311) of consecutive in-sync indications from a lower layer (e.g., of a primary cell); after a handover procedure is triggered; after an RRC connection reestablishment procedure is initiated; and so on. In an example, when the timer t310 expires, if security is not activated, the wireless device and / or the second network node may enter an RRC idle state. In an example, when the timer t310 expires, if security is activated, the wireless device and / or the second network node may initiate an RRC connection reestablishment procedure.

[0475] In an example, the expiration of t312 may indicate that the timer t312 of the wireless device and / or the second network node expires at the fault cell when a connection failure (e.g., a backhaul link failure) occurs. When the timer t310 is running, the timer t312 may be started after triggering a measurement report of a measurement identifier for which the timer t312 has been configured. In an example, the timer t312 may be stopped: after receiving a certain number (e.g., N311) of consecutive synchronization indications from a lower layer; after triggering a handover procedure; after initiating a connection reestablishment procedure; after the expiration of the timer t310; and so on. In an example, when the timer t312 expires, if security is not activated, the wireless device and / or the second network node may enter an idle state. In an example, when the timer t312 expires, if security is activated, the wireless device and / or the second network node may initiate an RRC connection reestablishment procedure.

[0476] In an example, the random access problem (e.g., failure) may indicate that the wireless device and / or the second network node experienced one or more random access problems (e.g., random access failure) at the failed cell when the connection failure occurred. In an example, the RLC maximum number of retransmissions may indicate that the RLC layer of the wireless device and / or the second network node attempted a maximum number of packet retransmissions when the connection failure occurred.

[0477] In an example, the wireless device identifier of the wireless device may include a C-RNTI, a temporary mobile subscriber identity (TMSI), an international mobile subscriber identity (IMSI), a global unique temporary identifier (GUTI), etc. at a faulty cell (e.g., a first cell). In an example, the carrier frequency value may indicate a carrier frequency value of the faulty cell. In an example, the carrier frequency value may include at least one of EARFCN, ARFCN, etc., for example, the maximum value is maxEARFCN. In an example, the carrier frequency value may be determined according to a frequency band used when obtaining relevant measurement results.

[0478] In an example, the network node identifier of the second network node may include a C-RNTI, a temporary mobile user identity (TMSI), an international mobile user identity (IMSI), a global unique temporary identifier (GUTI), etc. at a fault cell (e.g., a cell serving the second network node at the time of a backhaul link failure and / or a connection failure (e.g., a primary cell of the second network node)). In an example, the carrier frequency value may indicate a carrier frequency value of the faulty cell. In an example, the carrier frequency value may include at least one of EARFCN, ARFCN, etc., for example, the maximum value is maxEARFCN. In an example, the carrier frequency value may be determined according to a frequency band used when obtaining relevant measurement results.

[0479] In an example, the measurement result may include at least one of the following: a reference signal received power result (RSRP) or a reference signal received quality (RSRQ) of at least one of the failed cells (e.g., the first cell and / or the cell serving the second network node at the time of the backhaul link failure / blockage / problem and / or the connection failure), the last serving cell of the wireless device and / or the second network node, one or more serving cells of the wireless device and / or the second network node, one or more neighboring cells (of the wireless device and / or the second network node) of the failed cell, and / or one or more secondary cells of the wireless device and / or the second network node. In an example, the wireless device and / or the second network node may determine one or more elements of the measurement result by measuring when (or before / after) the wireless device experiences a connection failure and / or when (or before / after) the second network node experiences a backhaul link failure (e.g., an access link failure of the second network node). In an example, a quality classification indication 1 bearer (e.g., drb-EstablishedWithQCI-1) may indicate that a connection failure and / or a backhaul link failure occurs when a bearer with a QCI value of 1 is configured.

[0480] In an example, the first network node may receive one or more elements of a radio link failure report from the third network node. In an example, the first network node may receive RLF information (including the one or more elements) including one or more elements of a RLF report from the third network node. In an example, the first network node may receive the RLF information via one or more Xn interfaces and / or one or more X2 interfaces (e.g., a direct interface between the first network node and the third network node, or an indirect interface between the first network node and the third network node and / or one or more network nodes), e.g., via a handover report message and / or via a RLF indication message. In an instance, the first network node may receive RLF information via one or more NG interfaces and / or one or more S1 interfaces (e.g., via one or more core network nodes (e.g., one or more AMFs, one or more MMEs, one or more SGSNs, one or more GGSNs) between the first network node and the third network node (e.g., via gNB / eNB / NODE configuration delivery message and / or AMF / MME configuration delivery message; for example, SON information of the gNB / eNB / NODE configuration delivery message and / or AMF / MME configuration delivery message may include RLF information). In an instance, the first network node may receive RLF information via one or more F1 interfaces (e.g., a direct interface between the first network node and the third network node, or an indirect interface between the first network node and the third network node and / or one or more network nodes) (e.g., via one or more F1 interface messages).

[0481] In the example, Fig.34 As shown, if the first network node is a third network node, the first network node may receive an RLF report from the wireless device. In an example, if the second network node is a third network node, the first network node may receive RLF information and / or an RLF report from the second network node. In an example, if the IAB node served by the first network node is a third network node, the first network node may receive RLF information and / or an RLF report from the IAB node served by the first network node.

[0482] In an example, the first network node may configure a radio resource configuration parameter based on one or more elements of the RLF information and / or the radio link failure report. In an example, the radio resource configuration parameter may include a beam configuration parameter of the second network node. In an example, the radio resource configuration parameter may include a handover trigger parameter of the integrated access and backhaul node. The handover trigger parameter may include at least one of a radio signal reception quality value (e.g., a threshold quality value) and / or a radio signal reception power value (e.g., a threshold power value).

[0483] In an example, based on the RLF information and / or one or more elements of the radio link failure report, the first network node may determine at least one cell configuration parameter (e.g., radio resource configuration parameter) of one or more cells of the first network node of one or more wireless devices and / or one or more IAB nodes based on the RLF information. The one or more cells may include a failed cell (e.g., a first cell of a second network node, and / or a cell serving the second network node at the time of a connection failure and / or a backhaul link failure). In an example, the at least one cell configuration parameter may include at least one of the following: at least one BWP configuration parameter; at least one transmit power configuration parameter; at least one frequency configuration parameter; at least one beamforming configuration parameter; at least one physical control channel scheduling parameter; at least one antenna configuration parameter; at least one cell selection or reselection configuration parameter of one or more wireless devices; at least one system information; at least one interference control parameter; and the like.

[0484] In an example, at least one BWP configuration parameter may be used for one or more wireless devices. The at least one BWP configuration parameter may include one or more parameters indicating at least one of: a plurality of BWP indices of a plurality of BWPs; a plurality of BWP bandwidths of a plurality of BWPs; a default BWP index of a default BWP of the plurality of BWPs; a BWP inactivity timer; an initial BWP index of an initial BWP (e.g., an initial active BWP) of a plurality of BWPs; a subcarrier spacing of a plurality of BWPs; a cyclic prefix; a number of consecutive PRBs; an index in a set of one or more DL BWPs and / or one or more UL BWPs; a link between a DL BWP and a UL BWP from a set of configured DL BWPs and UL BWPs; a DCI detection of a PDSCH reception timing value; a PDSCH reception of a HARQ-ACK transmission timing value; a DCI detection of a PUSCH transmission timing value; a first PRB of a DL bandwidth or a UL bandwidth relative to a first PRB of a bandwidth, respectively; and the like.

[0485] In an example, if a wireless device and / or an IAB node (e.g., a second network node) experiences a connection failure during a period when a first BWP of multiple BWPs in a cell is an active BWP, the base station (e.g., the first network node) may not configure the first BWP as a default BWP (and / or initial BWP) for one or more wireless devices.

[0486] In an example, if the channel quality (e.g., RSRP, RSRQ) of a second BWP of multiple BWPs of a cell is good (e.g., better than the channel quality of the active BWP) when the wireless device and / or the IAB node (e.g., the second network node) experiences a connection failure during a period when the first BWP of the multiple BWPs is the active BWP, the base station (e.g., the first network node) can configure the second BWP as the default BWP (and / or initial BWP) for one or more wireless devices.

[0487] In an example, at least one transmit power configuration parameter may include a maximum downlink / uplink cell transmit power of one or more wireless devices and / or the first network node, a physical downlink control channel (PDCCH) transmit power, one or more power control parameters of uplink and / or downlink, TPC configuration parameters, SRS configuration parameters, etc. In an example, if the first network node (e.g., based on the measurement results of the RLF report) determines that the connection failure occurs due to the low transmit power of the PDCCH, the first network node may increase the transmit power of the PDCCH. In an example, if the connection failure occurs due to greater interference to the PDCCH, the first network node may reschedule the PDCCH to be located at other subframes.

[0488] In an example, if a wireless device and / or an IAB node (e.g., a second network node) experiences a connection failure during a period when a first BWP of multiple BWPs in a cell is an active BWP, the base station (e.g., a first network node) may increase the uplink / downlink power level (e.g., by 0.1 dB) of one or more wireless devices (e.g., a UE served in the first cell) when the one or more wireless devices adopt the first BWP as the active BWP.

[0489] In an example, if the cause of a connection failure of a wireless device and / or an IAB node (e.g., a second network node) is a random access problem and the wireless device and / or the IAB node (e.g., a second network node) experiences the connection failure during a period in which a first BWP among multiple BWPs in a cell is an active BWP, the base station (e.g., the first network node) may not configure the first BWP for random access preamble transmission of one or more wireless devices.

[0490] In an instance, if the cause of the connection failure of the wireless device and / or the IAB node (e.g., the second network node) is the RLC maximum retransmission number (e.g., uplink transmission problem; the number of RLC retransmissions exceeds a threshold) and the wireless device and / or the IAB node (e.g., the second network node) experiences the connection failure during a period when a first BWP among multiple BWPs in a cell is an active BWP, then when the one or more wireless devices adopt the first BWP as the active BWP, the base station (e.g., the first network node) can increase the uplink power level of one or more wireless devices.

[0491] In an example, the at least one frequency configuration parameter may include a carrier frequency, a bandwidth, one or more bandwidth part configuration parameters, etc. In an example, if a cell of the first network node experiences greater interference from a neighboring cell, the first network node may change the operating frequency to another frequency. In an example, if a certain bandwidth part of a serving cell of the first network node experiences greater interference from a neighboring cell or other technology, the first network node may change the default bandwidth part and / or active bandwidth part of one or more wireless devices to another bandwidth part.

[0492] In an example, at least one beamforming configuration parameter may include one or more beamforming direction configuration parameters, one or more beam sweep configuration parameters, one or more synchronization signal (SS) / reference signal (e.g., CSI-RS) configuration parameters, one or more beam recovery related parameters, one or more BRACH parameters, one or more preamble configuration parameters for beam recovery, one or more random access configuration parameters for one or more beams, etc. In an example, if a connection failure occurs due to a random access failure or a beam recovery procedure failure (e.g., asynchronization), the base station (e.g., the first network node) may reschedule random access resources and / or BRACH resources, and / or may reconfigure the preamble to reduce random access contention.

[0493] In an example, at least one physical control channel scheduling parameter may include a subframe pattern configuration parameter, a measurement subframe pattern configuration parameter, a transmission type parameter indicating local transmission and / or distributed transmission, a resource block allocation configuration parameter, a CSI-RS configuration parameter, etc. In an example, at least one antenna configuration parameter may include a default antenna configuration parameter, an antenna port configuration parameter, a value of a CRS antenna port parameter, etc. In an example, at least one cell selection or reselection configuration parameter of one or more wireless devices may include one or more power / time threshold parameters for cell selection / reselection of at least one wireless device of the first network node, one or more cell priority configuration parameters for cell selection / reselection, etc. In an example, a connection failure occurs due to a random access failure of the wireless device and / or the second network node, and if the wireless device and / or the IAB node (e.g., the second network node) does not meet the increased threshold, the first network node may increase the value of the one or more power / time threshold parameters to avoid the failure of the wireless device.

[0494] In an example, the first network node may reconfigure one or more IEs in at least one system information including at least one of system information type block types 1 to 21 based on the RLF report. In an example, the at least one interference control parameter may include one or more almost blank subframe configuration parameters, one or more CoMP interference management related parameters, etc. In an example, if a connection failure and / or a backhaul link failure occurs due to interference from a neighboring cell of the failed cell, the first network node may schedule resource blocks for the neighboring cell and the failed cell so that they do not use the resource blocks simultaneously.

[0495] In an example, the first network node may transmit at least one system information block including at least one cell configuration parameter. The at least one system information block may be at least one of system information block types 1 to 21. The first network node may transmit at least one of the at least one cell configuration parameter to one or more wireless devices, for example, via an RRC message. The one or more wireless devices may include a wireless device and / or an IAB node (e.g., a second network node).

[0496] In an example, the first network node may transmit RLF information and / or one or more elements of an RLF report to the second network node (e.g., via an F1 interface, a Uu interface, an NG interface; e.g., via an F1 information message, an RRC message, an NG configuration message). In an example, if the second network node is a third network node, the second network node may receive the RLF report from the wireless device.

[0497] In an example, the second network node and / or the first network node may configure a radio resource configuration parameter of the second network node based on one or more elements of the RLF information and / or the radio link failure report. In an example, the radio resource configuration parameter may include a beam configuration parameter of the second network node serving one or more wireless devices and / or one or more IAB nodes. In an example, the radio resource configuration parameter may include a handover trigger parameter of the integrated access and backhaul node. The handover trigger parameter may include at least one of a radio signal reception quality value (e.g., a threshold quality value) and / or a radio signal reception power value (e.g., a threshold power value).

[0498] In an example, based on the RLF information and / or one or more elements of the radio link failure report, the second network node and / or the first network node may determine at least one cell configuration parameter (e.g., radio resource configuration parameter) of one or more cells of the second network node serving one or more wireless devices (e.g., served by the second network node) and / or one or more IAB nodes (e.g., served by the second network node) based on the RLF information. The one or more cells may include a failed cell (e.g., a first cell of the second network node). In an example, the at least one cell configuration parameter may include at least one of the following: at least one BWP configuration parameter; at least one transmit power configuration parameter; at least one frequency configuration parameter; at least one beamforming configuration parameter; at least one physical control channel scheduling parameter; at least one antenna configuration parameter; at least one cell selection or reselection configuration parameter for one or more wireless devices; at least one system information; at least one interference control parameter; and the like.

[0499] In an example, at least one BWP configuration parameter may be used for one or more wireless devices. The at least one BWP configuration parameter may include one or more parameters indicating at least one of: a plurality of BWP indices of a plurality of BWPs; a plurality of BWP bandwidths of a plurality of BWPs; a default BWP index of a default BWP of the plurality of BWPs; a BWP inactivity timer; an initial BWP index of an initial BWP (e.g., an initial active BWP) of a plurality of BWPs; a subcarrier spacing of a plurality of BWPs; a cyclic prefix; a number of consecutive PRBs; an index in a set of one or more DL BWPs and / or one or more UL BWPs; a link between a DL BWP and a UL BWP from a set of configured DL BWPs and UL BWPs; a DCI detection of a PDSCH reception timing value; a PDSCH reception of a HARQ-ACK transmission timing value; a DCI detection of a PUSCH transmission timing value; a first PRB of a DL bandwidth or a UL bandwidth relative to a first PRB of a bandwidth, respectively; and the like.

[0500] In an example, if a wireless device experiences a connection failure during a period in which a first BWP among multiple BWPs in a cell is an active BWP, the base station (e.g., the first network node and / or the second network node) may not configure the first BWP as a default BWP (and / or initial BWP) for one or more wireless devices.

[0501] In an example, if the channel quality (e.g., RSRP, RSRQ) of a second BWP of multiple BWPs of a cell is good (e.g., better than the channel quality of the active BWP) when the wireless device experiences a connection failure during a period when a first BWP of the multiple BWPs is an active BWP, the base station (e.g., the first network node and / or the second network node) can configure the second BWP as the default BWP (and / or initial BWP) for one or more wireless devices.

[0502] In an example, at least one transmit power configuration parameter may include a maximum downlink / uplink cell transmit power of one or more wireless devices and / or a second network node, a physical downlink control channel (PDCCH) transmit power, one or more power control parameters of an uplink and / or downlink, a TPC configuration parameter, an SRS configuration parameter, etc. In an example, if the second network node and / or the first network node (e.g., based on a measurement result of an RLF report) determines that a connection failure occurs due to a low transmit power of the PDCCH, the second network node and / or the first network node may increase the transmit power of the PDCCH. In an example, if a connection failure occurs due to greater interference to the PDCCH, the first network node may reschedule the PDCCH to be located at another subframe.

[0503] In an example, if a wireless device experiences a connection failure during a period when a first BWP of multiple BWPs in a cell is an active BWP, a base station (e.g., a second network node and / or a first network node) may increase the uplink / downlink power level (e.g., by 0.1 dB) of one or more wireless devices (e.g., a UE served in the first cell) when the one or more wireless devices adopt the first BWP as the active BWP.

[0504] In an example, if the cause of a connection failure of a wireless device is a random access problem and the wireless device experienced a connection failure during a period when a first BWP among multiple BWPs in a cell is an active BWP, the base station (e.g., the second network node and / or the first network node) may not configure the first BWP for random access preamble code transmission of one or more wireless devices.

[0505] In an instance, if the cause of the connection failure of the wireless device is the maximum number of RLC retransmissions (e.g., uplink transmission problem; the number of RLC retransmissions exceeds a threshold) and the wireless device experienced the connection failure during a period when a first BWP among multiple BWPs in a cell is an active BWP, then when the one or more wireless devices adopt the first BWP as the active BWP, the base station (e.g., the second network node and / or the first network node) can increase the uplink power level of one or more wireless devices.

[0506] In an example, the at least one frequency configuration parameter may include a carrier frequency, a bandwidth, one or more bandwidth part configuration parameters, etc. In an example, if the cell of the second network node experiences greater interference from neighboring cells, the second network node and / or the first network node may change the operating frequency to another frequency. In an example, if a certain bandwidth part of the serving cell of the second network node experiences greater interference from neighboring cells or other technologies, the second network node and / or the first network node may change the default bandwidth part and / or the active bandwidth part of one or more wireless devices to another bandwidth part.

[0507] In an example, at least one beamforming configuration parameter may include one or more beamforming direction configuration parameters, one or more beam sweep configuration parameters, one or more synchronization signal (SS) / reference signal (e.g., CSI-RS) configuration parameters, one or more beam recovery related parameters, one or more BRACH parameters, one or more preamble configuration parameters for beam recovery, one or more random access configuration parameters for one or more beams, etc. In an example, if a connection failure occurs due to a random access failure or a beam recovery procedure failure (e.g., asynchronization), the base station (e.g., the second network node and / or the first network node) may reschedule random access resources and / or BRACH resources, and / or may reconfigure the preamble to reduce random access contention.

[0508] In an example, at least one physical control channel scheduling parameter may include a subframe pattern configuration parameter, a measurement subframe pattern configuration parameter, a transmission type parameter indicating local transmission and / or distributed transmission, a resource block allocation configuration parameter, a CSI-RS configuration parameter, etc. In an example, at least one antenna configuration parameter may include a default antenna configuration parameter, an antenna port configuration parameter, a value of a CRS antenna port parameter, etc. In an example, at least one cell selection or reselection configuration parameter of one or more wireless devices may include one or more power / time threshold parameters for cell selection / reselection of at least one wireless device of the second network node, one or more cell priority configuration parameters for cell selection / reselection, etc. In an example, a connection failure occurs due to a random access failure of the wireless device, and if the wireless device does not meet the increased threshold, the second network node and / or the first network node may increase the value of the one or more power / time threshold parameters to enable the wireless device to avoid the failure.

[0509] In an example, the second network node and / or the first network node may reconfigure one or more IEs in at least one system information including at least one of system information type block types 1 to 21 based on the RLF report. In an example, the at least one interference control parameter may include one or more almost blank subframe configuration parameters, one or more CoMP interference management related parameters, etc. In an example, if a connection failure and / or a backhaul link failure occurs due to interference from a neighboring cell of a failed cell (e.g., the first cell), the second network node and / or the first network node may schedule resource blocks for the neighboring cell and the failed cell so that they do not use the resource blocks simultaneously.

[0510] In an example, the second network node and / or the first network node may transmit at least one system information block including at least one cell configuration parameter. The at least one system information block may be at least one of system information block types 1 to 21. The first network node may transmit at least one of the at least one cell configuration parameter to one or more wireless devices, for example, via an RRC message. The one or more wireless devices may include a wireless device.

[0511] In an example, the second network node and / or the first network node may configure the switching parameters based on the RLF information and / or one or more elements of the RLF report. In an example, if the backhaul link connection is unstable (e.g., "unstable" is determined based on the RLF information and / or one or more elements of the RLF report), the second network node and / or the first network node may initiate switching of the serving wireless device (and / or serving IAB node) before the backhaul link connection is stable, e.g., to avoid a connection failure caused by the backhaul link failure. In an example, if the RSRP / RSRQ of the second network node of the first network node (e.g., RSRP / RSRQ measured by the second network node from the first network node; e.g., backhaul link RSRP / RSRQ) is lower than an updated value (e.g., determined based on one or more elements of the RLF information and / or RLF report; e.g., if a backhaul link failure occurs when the RSRP / RSRQ of the second network node of the first network node is X dB, the updated value may be configured to be X dB or a value higher than X dB), the second network node and / or the first network node may initiate handover of a wireless device (served by the second network node) having a stable access link connection with the second network node (e.g., a wireless device having a cell from the second network node that has a higher RSRP / RSRQ than a handover threshold RSRP / RSRQ adopted in the case of a stable backhaul link connection (e.g., a backhaul link RSRP / RSRQ higher than the updated value and / or X dB)).

[0512] In an example, the wireless device may receive at least one radio resource control (RRC) message from a first network node (e.g., and / or from a second network node), the message including configuration parameters of a first cell of the second network node. The wireless device may transmit a packet to the second network node based on the configuration parameters (explained in the specification). The wireless device may determine a connection failure from the first network node (e.g., and / or the second network node) based on a backhaul link failure (e.g., backhaul link problem, backhaul link congestion). The wireless device may select a second cell of a third network node for a radio resource control connection (e.g., establishment and / or reestablishment) in response to the connection failure. The wireless device may transmit a radio link failure report including a cause value of the connection failure to the third network node. The cause value may indicate that the backhaul link failure caused the connection failure.

[0513] In an example, the wireless device may receive backhaul link failure information from the second network node indicating a failure (e.g., problem, blockage) of a first radio link established between the first network node and the second network node. In an example, the wireless device may determine a connection failure based on the backhaul link failure information. In an example, the wireless device may receive the backhaul link failure information via at least one of a media access control control element (MAC Ce), a physical layer command including downlink control information, an adaptation layer indication, and / or a radio resource control message (e.g., an RRC connection release message).

[0514] In an example, the backhaul link failure information may include at least one of the following: a first node identifier of the first network node; a second node identifier of the second network node; a failure (e.g., congestion, problem) type (e.g., including at least one of the following: temporary congestion; failure of at least one backhaul link among multiple backhaul links of the second network node; and / or failure of all backhaul links of the second network node); a timer value, the timer value being used to determine an integrated access and backhaul node failure; an indication parameter indicating that the state of one or more cells of the second network node is transitioned to a dormant state; an indication parameter indicating the release of one or more cells of the second network node; a cause value of the failure of the first radio link (e.g., RLF cause); a bearer identifier of a bearer affected by the failure of the first radio link; and / or a cell identifier of a cell of the first network node (e.g., the cell causing the first radio link failure) (e.g., the cell adopted by the second network node).

[0515] In an example, the wireless device may release a bearer established via the second network node in response to receiving the backhaul link failure information. In an example, the wireless device may stop transmitting a scheduling request to the second network node in response to receiving the backhaul link failure information. In an example, the first radio link may include one or more radio links connected via one or more network nodes. The failure of the first radio link may indicate at least one failure of the one or more radio links.

[0516] In an example, the wireless device may transmit one or more random access preambles via the second cell. The wireless device may receive a random access response to the one or more random access preambles from the third network node. The wireless device may transmit a radio resource control connection (e.g., reestablishment and / or establishment) request message based on the random access response.

[0517] In an example, the connection failure may include at least one of a radio link failure and / or a handover failure. The first cell may be a primary cell of the wireless device. The first network node may include a third network node. The second network node may include a third network node. In an example, the first cell may be a second cell. In an instance, the radio link failure report may include at least one of the following: an identifier of the first network node; an identifier of the second network node; a base station identifier of the second network node; an integrated access and backhaul identifier of the second network node; a transmit and receive point identifier of the second network node; a cell identifier of the first cell; a beam identifier of the first cell; a beam group identifier of one or more beams of the first cell; an F1 wireless device identifier of the wireless device; an information element indicating that a backhaul link failure caused a connection failure; a failure (e.g., congestion, problem) type (e.g., including at least one of the following: temporary congestion; failure of at least one of the multiple backhaul links of the second network node; and / or failure of all backhaul links of the second network node); a timer value, the timer value being used to determine the integrated access and backhaul node failure; a cause value of the failure of the first radio link (e.g., RLF cause); and / or a cell identifier of a cell of the first network node (e.g., the cell that caused the first radio link failure) (e.g., the cell used by the second network node).

[0518] In an example, the first network node may include at least one of: a base station; a base station central unit; and / or an integrated access and backhaul provider. In an example, the second network node may include at least one of: a base station; a base station distributed unit; and / or an integrated access and backhaul node.

[0519] In an example, the first network node may receive one or more elements of a radio link failure report from a third network node. The first network node may configure a radio resource configuration parameter based on the one or more elements of the radio link failure report. In an example, the radio resource configuration parameter may include a beam configuration parameter of the second network node. In an example, the radio resource configuration parameter may include a handover trigger parameter of the integrated access and backhaul node. The handover trigger parameter may include at least one of a radio signal reception quality value (e.g., a threshold quality value) and / or a radio signal reception power value (e.g., a threshold power value). In an example, the first network node may transmit one or more elements of the radio link failure report to the second network node.

[0520] In an example, the wireless device may receive at least one radio resource control message from the first network node, the radio resource control message including a configuration parameter of a first cell of the second network node. The wireless device may transmit a packet to the second network node based on the configuration parameter. The wireless device may receive backhaul link failure information from the second network node, the backhaul link failure information indicating a failure of a first radio link established between the first network node and the second network node. The wireless device may determine a connection failure from the first network node based on the backhaul link failure information. The wireless device may select a second cell of the first network node for a radio resource control connection in response to the connection failure. The wireless device may transmit a radio link failure report including a cause value of the connection failure to the first network node, wherein the cause value indicates that the backhaul link failure caused the connection failure.

[0521] In an example, the wireless device may receive at least one radio resource control message from the first network node, the radio resource control message including a configuration parameter of a first cell of the second network node. The wireless device may transmit a packet to the second network node based on the configuration parameter. The wireless device may receive backhaul link failure information from the second network node, the backhaul link failure information indicating a failure of a first radio link established between the first network node and the second network node. The wireless device may determine a connection failure from the first network node based on the backhaul link failure information. The wireless device may select a second cell of the second network node for a radio resource control connection in response to the connection failure. The wireless device may transmit a radio link failure report including a cause value of the connection failure to the second network node, wherein the cause value indicates that the backhaul link failure caused the connection failure.

[0522] In an example, the wireless device may receive at least one radio resource control message from the first network node via the second network node, the radio resource control message including a configuration parameter of a first cell of the second network node. The wireless device may send a packet to the second network node via the first cell. The wireless device may determine a failure of a connection to the first network node based on a backhaul link failure between the first network node and the second network node. The wireless device may select a second cell of a third network node for a radio resource control connection based on determining the failure of the connection. The wireless device may transmit a radio link failure report indicating the backhaul link failure to the third network node.

[0523] In an example, the wireless device may receive backhaul link failure information from the second network node, the backhaul link failure information indicating a failure of a first radio link established between the first network node and the second network node. The wireless device may receive the backhaul link failure information via at least one of: a media access control control element, a physical layer command including downlink control information, an adaptation layer indication, a radio resource control message, etc. In an example, the wireless device may determine a failure of the connection based on the backhaul link failure information. The backhaul link failure information includes at least one of the following: a first node identifier of the first network node; a second node identifier of the second network node; a failure type (for example, including at least one of the following: temporary blocking, failure of at least one backhaul link among multiple backhaul links of the second network node, failure of all backhaul links of the second network node, etc.); a timer value, the timer value being used to determine an integrated access and backhaul node failure; an indication parameter indicating that the state of one or more cells of the second network node is transitioned to a dormant state; an indication parameter indicating the release of one or more cells of the second network node; a cause value of the failure of the first radio link; a bearer identifier of a bearer affected by the failure of the first radio link; a cell identifier of a cell of the first network node, the cell causing the failure of the first radio link; and the like.

[0524] In an example, the wireless device may release a bearer established via the second network node in response to receiving the backhaul link failure information. The wireless device may stop transmitting a scheduling request to the second network node in response to receiving the backhaul link failure information. The first radio link may include one or more radio links connected via one or more network nodes. The failure of the first radio link may indicate at least one failure of the one or more radio links.

[0525] In an example, the wireless device may transmit one or more random access preambles via the second cell. The wireless device may receive a random access response to the one or more random access preambles from a third network node. The wireless device may transmit a radio resource control connection request message to the third network node based on the random access response. The failure of the connection may include at least one of the following: a radio link failure, a handover failure, etc. The first cell may be a primary cell of the wireless device. The first cell may be a second cell. The first network node may be a third network node. The second network node may be a third network node. The radio link failure report may include at least one of the following: an identifier of the first network node, an identifier of the second network node, a base station identifier of the second network node, an integrated access and backhaul identifier of the second network node, a transmitting and receiving point identifier of the second network node, a cell identifier of the first cell, a beam identifier of the first cell, a beam group identifier of one or more beams of the first cell, an F1 wireless device identifier of the wireless device, an information element indicating that a backhaul link failure caused a failure of the connection, a failure type (for example, including at least one of the following: temporary congestion, failure of at least one of the multiple backhaul links of the second network node, failure of all backhaul links of the second network node, etc.), a timer value for determining an integrated access and backhaul node failure, a cause value for the failure of the first radio link, a cell identifier of the cell of the first network node (for example, the cell may cause the failure of the first radio link), etc.

[0526] In an example, the first network node may include at least one of: a base station, a base station central unit, an integrated access and backhaul provider, etc. The second network node may include at least one of: a base station, a base station distributed unit, an integrated access and backhaul node, etc.

[0527] In an example, the first network node may receive one or more elements of a radio link failure report from the third network node. The first network node may configure a radio resource configuration parameter based on the one or more elements. The radio resource configuration parameter may include a beam configuration parameter of the second network node. The radio resource configuration parameter may include a handover trigger parameter of the integrated access and backhaul node. The handover trigger parameter may include at least one of the following: a radio signal reception quality value, a radio signal reception power value, etc. The first network node may transmit one or more elements of the radio link failure report to the second network node.

[0528] In the example, Fig.45 As shown, the wireless device may communicate with the first network node via the second network node, 4510. The wireless device may send a radio link failure report to a third network node, the radio link failure report indicating a backhaul link failure between the first network node and the second network node, 4520.

[0529] In the example, Fig.46 As shown, the third network node may receive a radio link failure report from the wireless device, the radio link failure report indicating a backhaul link failure between the first network node and the second network node, 4610. A failure of a connection between the wireless device and the first network node via the second network node may be based on the backhaul link failure, 4620. The third network node may send one or more elements of the radio link failure report to the first access node.

[0530] In an example, the wireless device may send a radio link failure report indicating that a connection failure between the wireless device and the first network node via the second network node is based on a backhaul link failure between the first network node and the second network node.

[0531] In an example, the wireless device may send a radio link failure report indicating a backhaul link failure between the first network node and the second network node.The connection failure between the wireless device and the first network node via the second network node may be based on the backhaul link failure.

[0532] In an example, the wireless device may send a radio link failure report indicating a backhaul link failure between the first network node and the second network node. Prior to the backhaul link failure, the wireless device may communicate with the first network node via the second network node.

[0533] In an example, the wireless device may send a radio link failure report to the third network node, the radio link failure report indicating a backhaul link failure between the first network node and the second network node. Prior to the backhaul link failure, the wireless device may communicate with the first network node via the second network node.

[0534] In an example, the wireless device may determine a failure of a connection between the wireless device and the first network node via the second network node based on a backhaul link failure between the first network node and the second network node. The wireless device may send a radio link failure report indicating the backhaul link failure to a third network node.

[0535] In an example, the wireless device may receive at least one radio resource control message from the first network node, the radio resource control message including a configuration parameter of a first cell of the second network node. The wireless device may transmit a packet to the second network node based on the configuration parameter. The wireless device may receive backhaul link failure information from the second network node, the backhaul link failure information indicating a failure of a first radio link established between the first network node and the second network node. The wireless device may determine a connection failure from the first network node based on the backhaul link failure information. The wireless device may select a second cell of a third network node for a radio resource control connection based on the connection failure. The wireless device may transmit a radio link failure report including a cause value of the connection failure to the third network node. The cause value may indicate that the backhaul link failure caused the connection failure.

[0536] Embodiments may be configured to operate as desired. When certain criteria are met, such as in a wireless device, a base station, a radio environment, a network, a combination of the above, etc., the disclosed mechanisms may be performed. Example criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system settings, packet size, traffic characteristics, a combination of the above, etc. When one or more criteria are met, various example embodiments may be applied. Therefore, it is possible to implement example embodiments that selectively implement the disclosed protocol.

[0537] A base station may communicate with a mixture of wireless devices. A wireless device and / or a base station may support multiple technologies and / or multiple versions of the same technology. A wireless device may have certain specific capabilities, depending on the wireless device category and / or capabilities. A base station may include multiple sectors. When the present disclosure refers to a base station communicating with multiple wireless devices, the present disclosure may refer to a subset of the total wireless devices in the coverage area. For example, the present disclosure may refer to multiple wireless devices of a given LTE or 5G version with a given capability and in a given sector of a base station. The multiple wireless devices in the present disclosure may refer to a selected plurality of wireless devices, and / or a subset of the total wireless devices in the coverage area that perform according to the disclosed method, etc. There may be multiple base stations or multiple wireless devices in the coverage area that do not comply with the disclosed method because, for example, these wireless devices or base stations perform based on older versions of LTE or 5G technology.

[0538] In the present disclosure, "a" and "a / an" and similar phrases will be interpreted as "at least one" and "one or more". Similarly, any term ending with the suffix "(s)" will be interpreted as "at least one" and "one or more". In the present disclosure, the term "may" will be interpreted as "may, for example". In other words, the term "may" indicates that the phrase following the term "may" is an example of one of a variety of suitable possibilities that may or may not be used for one or more of the various embodiments.

[0539] If A and B are sets, and each element of A is also an element of B, then A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, the possible subsets of B = {cell1, cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase "based on" (or equivalently "at least based on") indicates that the phrase after the term "based on" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments. The phrase "in response to" (or equivalently "at least in response to") indicates that the phrase after the phrase "in response to" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments. The phrase "depends on" (or equivalently "at least depends on") indicates that the phrase after the phrase "depends on" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments. The phrase "adopt / use" (or equivalently "at least adopt / use") indicates that the phrase after the phrase "adopt / use" is an example of one of multiple suitable possibilities that may or may not be used for one or more different embodiments.

[0540] The term configured may relate to the capabilities of a device, whether the device is in an operational state or a non-operational state. "Configured" may also mean a specific setting in a device that affects the operational characteristics of the device, whether the device is in an operational state or a non-operational state. In other words, hardware, software, firmware, registers, memory values, etc. may be "configured" within a device to provide specific characteristics to the device, whether the device is in an operational state or a non-operational state. For example, a term such as "a control message caused in a device" may mean that the control message has parameters that can be used to configure specific characteristics in the device or parameters that can be used to implement certain actions in the device, whether the device is in an operational state or a non-operational state.

[0541] In the present disclosure, various embodiments are disclosed. Limitations, features and / or elements from the disclosed example embodiments may be combined to create additional embodiments within the scope of the present disclosure.

[0542] In the present disclosure, a parameter (or equivalently referred to as a field or information element (IE)) may include one or more information objects, and an information object may include one or more other objects. For example, if parameter (IE) N includes parameter (IE) M, and parameter (IE) M includes parameter (IE) K, and parameter (IE) K includes parameter (information element) J, then, for example, N includes K and N includes J. In an exemplary embodiment, when one or more (or at least one) messages include multiple parameters, this means that one of the multiple parameters is in at least one of the one or more messages, but not necessarily in each of the one or more messages. In an exemplary embodiment, when one or more (or at least one) messages indicate a value, event, and / or condition, this means that the value, event, and / or condition is indicated by at least one of the one or more messages, but not necessarily by each of the one or more messages.

[0543] In addition, most of the features presented above are described as being optional, either by using "may" or by using parentheses. For the sake of brevity and readability, the present disclosure does not explicitly recite every permutation that can be obtained by selecting from the set of optional features. However, the present disclosure should be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features can be embodied in seven different ways, i.e., having only one of the three possible features, having any two of the three possible features, or having all three of the three possible features.

[0544] Many elements described in the disclosed embodiments can be implemented as modules. Modules are defined here as elements that perform defined functions and have defined interfaces to other elements. The modules described in this disclosure can be implemented with hardware, software combined with hardware, firmware, wetware (i.e., hardware with biological elements), or a combination thereof, all of which can be equivalent in behavior. For example, a module can be implemented as a software routine written in a computer language, which is configured to be executed by a hardware machine (e.g., C, C++, Fortran, Java, Basic, Matlab, etc.) or a modeling / simulation program (e.g., Simulink, Stateflow, GNU Octave, or LabVIEW MathScript). In addition, it is possible to implement a module using physical hardware incorporating discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include: computers, microcontrollers, microprocessors, application specific integrated circuits (ASICs); field programmable gate arrays (FPGAs); and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, C++, etc. FPGAs, ASICs, and CPLDs are often programmed using a hardware description language (HDL), such as VHSIC Hardware Description Language (VHDL) or Verilog, which configures the connections between the internal hardware blocks with fewer functions on the programmable device. The above mentioned techniques are often used in combination to achieve the results of the functional blocks.

[0545] The disclosure of this patent document incorporates material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, for the limited purpose of requiring by law, but otherwise reserves all copyright rights whatsoever.

[0546] Although various embodiments have been described above, it should be understood that they are presented by way of example and not limitation. It will be apparent to those skilled in the relevant art that various changes in form and detail may be made therein without departing from the scope of the present invention. Indeed, after reading the above description, it will be apparent to those skilled in the relevant art how to implement alternative embodiments. Therefore, the present embodiments should not be limited by any of the above exemplary embodiments.

[0547] In addition, it should be understood that any diagrams highlighting functionality and advantages are provided for example purposes only. The disclosed architecture is flexible and configurable enough that it can be utilized in a manner other than that shown. For example, the actions listed in any flow chart may be reordered or only optionally used in certain embodiments.

[0548] In addition, the purpose of the Abstract of the Disclosure is to generally enable the U.S. Patent and Trademark Office and the public, especially scientists, engineers, and practitioners in the field who are not familiar with patent or legal terms or phraseology, to quickly determine the nature and substance of the technical disclosure of the application through a cursory review. The Abstract of the Disclosure is not intended to limit the scope in any way.

[0549] Finally, it is Applicant's intent that only claims containing the express language "means for" or "step for" be interpreted under 35 USC 112. Claims that do not expressly contain the phrase "means for" or "step for" should not be interpreted under 35 USC 112.

Claims

1. A method comprising: communicating, by the wireless device, with the IAB donor node via the integrated access and backhaul IAB node; receiving, by the wireless device, backhaul link failure information from the IAB node, the backhaul link failure information indicating a roadblock of a radio link established between the IAB donor node and the IAB node; determining a failure of a connection between the wireless device and the IAB donor node based on the backhaul link failure information; and A radio link failure report is sent by the wireless device to a third network node, the radio link failure report indicating that a backhaul link failure between the IAB donor node and the IAB node is a cause of the failure of the connection between the wireless device and the IAB donor node.

2. The method of claim 1, wherein the wireless device receives the backhaul link failure information via at least one of: Media access control element; A physical layer command, the physical layer command comprising downlink control information; Adaptation layer indication; or Radio Resource Control Message.

3. The method according to claim 1, wherein the backhaul link fault information includes a fault type, which is at least one of the following fault types: Temporary blockage; A failure of at least one backhaul link among a plurality of backhaul links of the IAB node; or Failure of all backhaul links of the IAB node. 4 . The method of claim 1 , wherein the backhaul link failure information comprises a cell identifier of a cell of the IAB donor node, the cell causing the failure of the first radio link. 5 . The method of claim 1 , further comprising releasing, by the wireless device, a bearer established via the IAB node in response to receiving the backhaul link failure information. 6 . The method of claim 1 , further comprising ceasing, by the wireless device in response to receiving the backhaul link failure information, to transmit scheduling requests to the IAB node.

7. The method of claim 1, wherein the first radio link comprises one or more radio links connected via one or more network nodes, and the failure of the first radio link indicates at least one failure of the one or more radio links.

8. The method according to claim 1, further comprising: transmitting, by the wireless device via the second cell, one or more random access preambles; receiving, by the wireless device from the third network node, a random access response to the one or more random access preambles; as well as A radio resource control connection request message is transmitted by the wireless device to the third network node based on the random access response.

9. The method of claim 1 , wherein the radio link failure report comprises at least one of: An information element indicating that the backhaul link failure caused the failure of the connection; or A cell identifier of a cell of the IAB donor node, the cell causing the failure of the first radio link established between the IAB donor node and the IAB node.

10. The method according to claim 1, wherein: The radio link failure report includes a cell identifier of the first cell.

11. A wireless device comprising: one or more processors; as well as a memory storing instructions that, when executed by the one or more processors, cause the wireless device to: Communicate with the IAB donor node via the integrated access and backhaul IAB node; receiving backhaul link failure information from the IAB node, the backhaul link failure information indicating a roadblock of a radio link established between the IAB donor node and the IAB node; determining a failure of a connection between the wireless device and the IAB donor node based on the backhaul link failure information; and A radio link failure report is sent to a third network node, the radio link failure report indicating that a backhaul link failure between the IAB donor node and the IAB node is a cause of the failure of the connection between the wireless device and the IAB donor node.

12. The wireless device according to claim 11, wherein: The instructions, when executed by the one or more processors, further cause the wireless device to receive the backhaul link failure information via at least one of: Media access control element; A physical layer command, the physical layer command comprising downlink control information; Adaptation layer indication; or Radio Resource Control Message.

13. The wireless device of claim 11, wherein the backhaul link failure information comprises a failure type, and the failure type comprises at least one of the following: Temporary blockage; A failure of at least one backhaul link among a plurality of backhaul links of the IAB node; or Failure of all backhaul links of the IAB node.

14. The wireless device of claim 11, wherein the backhaul link failure information comprises a cell identifier of a cell of the IAB donor node, the cell causing the failure of the first radio link. 15 . The wireless device of claim 11 , wherein the first radio link comprises one or more radio links connected via one or more network nodes, and the failure of the first radio link indicates at least one failure of the one or more radio links.

16. The wireless device of claim 11, wherein the radio link failure report comprises at least one of: An information element indicating that the backhaul link failure caused the failure of the connection; or A cell identifier of a cell of the IAB donor node, the cell causing the failure of the first radio link.

17. The wireless device according to claim 11, wherein: The radio link failure report includes a cell identifier of the first cell.

18. A non-transitory computer-readable storage medium comprising instructions that, when executed by one or more processors, cause a wireless device to: Communicate with the IAB donor node via the integrated access and backhaul IAB node; receiving backhaul link failure information from the IAB node, the backhaul link failure information indicating a roadblock of a radio link established between the IAB donor node and the IAB node; determining a failure of a connection between the wireless device and the IAB donor node based on the backhaul link failure information; and A radio link failure report is sent to a third network node, the radio link failure report indicating that a backhaul link failure between the IAB donor node and the IAB node is a cause of the failure of the connection between the wireless device and the IAB donor node.