Backhaul link connection information

Abstract

The wireless device communicates with the first network node through the second network node. The wireless device transmits a wireless link failure report to the third network node. The wireless link failure report indicates a backhaul link failure between the first network node and the second network node.

Description

Technology Field

[0001] 관련 출원의 교차 참조

[0002] This application claims the benefit of U.S. Provisional Application No. 62 / 728,782 filed September 8, 2018, the entirety of which is incorporated herein by reference. Brief explanation of the drawing

[0003] Some examples of the various embodiments of the present disclosure are described herein with reference to the drawings. FIG. 1 is a diagram of an exemplary RAN architecture according to one aspect of one embodiment of the present disclosure. FIG. 2a is a diagram of an exemplary user plane protocol stack according to one aspect of one embodiment of the present disclosure. FIG. 2b is a diagram of an exemplary control plane protocol stack according to one aspect of one embodiment of the present disclosure. FIG. 3 is a diagram of an exemplary wireless device and two base stations according to one aspect of one embodiment of the present disclosure. FIGS. 4a, FIGS. 4b, FIGS. 4c and FIGS. 4d are exemplary diagrams for uplink and downlink signal transmission according to one aspect of one embodiment of the present disclosure. FIG. 5a is a diagram of exemplary uplink channel mapping and exemplary uplink physical signals according to one aspect of one embodiment of the present disclosure. FIG. 5b is a diagram of exemplary downlink channel mapping and exemplary downlink physical signals according to one aspect of one embodiment of the present disclosure. FIG. 6 is a diagram illustrating an exemplary frame structure according to one aspect of one embodiment of the present disclosure. FIGS. 7a and 7b are diagrams illustrating exemplary OFDM subcarrier sets according to one aspect of one embodiment of the present disclosure. FIG. 8 is a diagram illustrating exemplary OFDM radio resources according to one aspect of one embodiment of the present disclosure. FIG. 9a is a diagram illustrating exemplary CSI-RS and / or SS block transmission in a multi-beam system. FIG. 9b is a diagram illustrating an exemplary downlink beam management procedure according to one aspect of one embodiment of the present disclosure. FIG. 10 is an exemplary diagram of a BWP configured according to one aspect of one embodiment of the present disclosure. FIGS. 11a and FIGS. 11b are diagrams of exemplary multi-connectivity according to one aspect of one embodiment of the present disclosure. FIG. 12 is a diagram of an exemplary random access procedure according to one aspect of one embodiment of the present disclosure. FIG. 13 is a structure of exemplary MAC entities according to one aspect of one embodiment of the present disclosure. FIG. 14 is a diagram of an exemplary RAN architecture according to one aspect of one embodiment of the present disclosure. FIG. 15 is a diagram of an exemplary RRC state according to one aspect of one embodiment of the present disclosure. FIG. 16 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 17 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 18 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 19 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 20 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 21 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 22 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 23 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 24 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 25 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 26 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 27 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 28 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 29 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 30 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 31 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 32 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 33 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 34 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 35 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 36 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 37 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 38 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 39 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 40 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 41 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 42 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 43 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 44 is a diagram of one aspect of an exemplary embodiment of the present disclosure. FIG. 45 is a flowchart of one aspect of an exemplary embodiment of the present disclosure. FIG. 46 is a flowchart of one aspect of an exemplary embodiment of the present disclosure. Specific details for implementing the invention

[0004] Exemplary embodiments of the present disclosure enable the operation of wireless systems. Embodiments of the technology disclosed herein may be used in the field of technology for multi-carrier communication systems. More specifically, embodiments of the technology disclosed herein may relate to wireless access technology in multi-carrier communication systems.

[0005] The following acronyms are used throughout the present disclosure.

[0006]

[0007]

[0008]

[0009]

[0010]

[0011] Exemplary embodiments of the present disclosure may be implemented using various physical layer modulation and transmission mechanisms. Exemplary 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 technology, etc. Hybrid transmission mechanisms such as TDMA / CDMA and OFDM / CDMA may also be used. Various modulation techniques may be applied to signal transmission at the physical layer. Examples of modulation techniques include, but are not limited to, phase, amplitude, code, and combinations thereof. An exemplary wireless transmission method 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 wireless transmission can be enhanced by dynamically or reactively changing modulation and encoding methods according to transmission requirements and wireless conditions.

[0012] FIG. 1 is an exemplary radio access network (RAN) architecture according to one aspect of an embodiment of the present disclosure. As illustrated in this example, a RAN node may be a next-generation node B (gNB) (e.g., 120A, 120B) providing New Radio (NR) user plane and control plane protocol endpoints toward a first radio device (e.g., 110A). In one example, a RAN node may be a next-generation evolution node B (ng-eNB) (e.g., 124A, 124B) providing evolved UMTS terrestrial radio access (E-UTRA) user plane and control plane protocol endpoints toward a second radio device (e.g., 110B). The first radio device may communicate with the gNB via a Uu interface. The second radio device may communicate with the ng-eNB via a Uu interface. In the present disclosure, the wireless devices (110A and 110B) are structurally similar to the wireless device (110). The base station (120A and / or 120B) may be structurally similar to the 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 similar ones.

[0013] A gNB or ng-eNB can host functions such as wireless resource management and scheduling, IP header compression, encryption and integrity protection of data, selection of Access and Mobility Management Function (AMF) at User Equipment (UE) attachment, routing of user plane and control plane data, connection setup and release, scheduling and transmission of paging messages (originating from AMF), scheduling and transmission of system broadcast information (originating from AMF or Operation and Maintenance (O&M)), measurement and measurement reporting configuration, transport-level packet marking within the uplink, session management, support for network slicing, Quality of Service (QoS) flow management and mapping for data wireless bearers, support for UE in RRC_INACTIVE state, distribution function for Non-Access Layer (NAS) messages, RAN sharing, and dual connection or strict interworking between NR and E-UTRA.

[0014] In one example, one or more gNBs and / or one or more ng-eNBs may be interconnected via an Xn interface. A gNB or ng-eNB may be connected to a 5G core network (5GC) via an NG interface. In one example, the 5GC may include one or more AMF / UPF (User Plan Function) functions (e.g., 130A or 130B). A gNB or ng-eNB may be connected to a UPF via an NG-U (NG-User plane) interface. The NG-U interface may provide delivery (e.g., non-guaranteed delivery) of User Plane Protocol Data Units (PDUs) between a RAN node and a UPF. A gNB or ng-eNB may be connected to an AMF via an NG-Control plane (NG-C) interface. The NG-C interface can provide, for example, NG interface management, UE context management, UE movement management, NAS message transmission, paging, PDU session management, configuration transmission and / or alert message transmission, combinations thereof, and / or etc.

[0015] In one example, the UPF may host functions such as an anchor point for intra- / inter-RAT (Radio Access Technology) movement (where applicable), an external PDU session point for interconnection to a data network, packet routing and forwarding, packet inspection and user plane portions for policy rule enforcement, traffic usage reporting, an uplink classifier to support routing traffic flows to a data network, a branching point to support multi-homed PDU sessions, QoS handling for the user plane, e.g., packet filtering, gating, uplink (UL) / downlink (DL) rate enforcement, uplink traffic verification (e.g., Service Data Flow (SDF) to QoS flow mapping), downlink packet buffering and / or downlink data notification triggering.

[0016] In one example, the AMF may host support for functions such as NAS signaling termination, NAS signaling security, access layer (AS) security control, inter-core network (CN) node signaling for movement between 3GPP access networks, idle mode UE accessibility (e.g., control and execution of paging retransmission), registration area management, support for intra-system and inter-system movement, access authentication including checking roaming rights, movement management control (subscription and policy), network slicing and / or selection of Session Management Function (SMF).

[0017] FIG. 2a is an exemplary user plane protocol stack, wherein the Service Data Adaptation Protocol (SDAP) (e.g., 211, 221), Packet Data Convergence Protocol (PDCP) (e.g., 212, 222), Radio Link Control (RLC) (e.g., 213, 223), Media Access Control (MAC) (e.g., 214 and 224), sublayers, and the Physical Layer (PHY) (e.g., 215 and 225) may be terminated at a network-side radio device (e.g., 110) and a gNB (e.g., 120). In one example, the PHY layer provides transport services to the upper layers (e.g., MAC, RRC, etc.). In one example, the services and functions of the MAC sublayer may include mapping between logical channels and transport channels, multiplexing / demultiplexing of MAC service data units (SDUs) belonging to one or different logical channels in / from transport blocks (TBs) transmitted to / from the PHY layer, reporting scheduling information, error correction via Hybrid Automatic Repeat Request (HARQ) (e.g., one HARQ entity per carrier in the case of Carrier Aggregation (CA)), priority handling between UEs using dynamic scheduling, priority handling between logical channels of a single UE using logical channel prioritization, and / or padding. A MAC entity may support one or more numerologies and / or transport timings. In one example, a mapping restriction in logical channel prioritization may control the numerologies and / or transport timings available to the logical channel. In one example, the RLC partial layer can support transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM) transmission modes.RLC configuration can be performed per logical channel without relying on numerology and / or Transmission Time Interval (TTI) durations. In one example, an Automatic Repeat Request (ARQ) may operate based on any of the numerology and / or TTI durations for which the logical channel is configured. In one example, services and functions of the PDCP layer for the user plane may include sequence numbering, header compression and decompression, transmission of user data, reordering and duplicate detection, PDCP PDU routing (e.g., for split bearers), retransmission of PDCP SDUs, encryption, deciphering, integrity protection, discarding of PDCP SDUs, PDCP re-establishment and data recovery for RLC AM, and / or duplication of PDCP PDUs. In one example, services and functions of the SDAP may include mapping between QoS flows and data radio bearers. In one example, SDAP services and functions may include mapping Quality of Service Indicators (QFIs) in DL and UL packets. In one example, SDAP protocol entities may be configured for individual PDU sessions.

[0018] FIG. 2b is a control plane protocol stack, wherein PDCP (e.g., 233 and 242), RLC (e.g., 234 and 243), MAC (e.g., 235 and 244) partial layers and PHY layers (e.g., 236, 245) can be terminated at a wireless device (e.g., 110) and a gNB (e.g., 120) on the network side and can perform the services and functions described above. In one example, RRC (e.g., 232 and 241) can be terminated at a wireless device and a gNB on the network side. In one example, the services and functions of the RRC may include broadcasting system information related to the AS and NAS, paging initiated by the 5GC or RAN, establishing, maintaining, and releasing an RRC connection between the UE and the RAN, security functions including key management, establishing, configuring, maintaining, and releasing a signaling radio bearer (SRB) and a data radio bearer (DRB), mobility functions, QoS management functions, control of UE measurement reporting and reporting, detection of radio link failures and recovery from failures, and / or transmission of NAS messages to / from the NAS, from / to the UE. In one example, the NAS control protocol (e.g., 231 and 251) may be terminated at the network side at the radio device and AMF (e.g., 130) and may perform functions such as session management between the UE and the SMF for 3GPP access and non-3GPP access, and authentication and mobility management between the UE and the AMF for 3GPP access and non-3GPP access.

[0019] In one example, a base station may configure multiple logical channels for a wireless device. A logical channel within the multiple logical channels may correspond to a radio bearer, and the radio bearer may be associated with QoS requirements. In one example, a base station may configure a logical channel to be mapped to one or more TTI / numericals from a plurality of TTI / numericals. The wireless device may receive Downlink Control Information (DCI) through a Physical Downlink Control Channel (PDCCH) indicating an uplink grant. In one example, the uplink grant may be for a first TTI / numerical and may indicate uplink resources for the transmission of a transmission block. The base station may configure each logical channel within the multiple logical channels with one or more parameters to be used by a logical channel prioritization procedure at the MAC layer of the wireless device. One or more parameters may include priority, a prioritized bit rate, etc. A logical channel of the multiple logical channels may correspond to one or more buffers containing data associated with the logical channel. A logical channel prioritization procedure may allocate uplink resources to one or more first logical channels and / or one or more MAC control elements (CEs) within a plurality of logical channels. One or more first logical channels may be mapped to a first TTI / numericology. In a wireless device, the MAC layer may multiplex one or more MAC CEs and / or one or more MAC SDUs (e.g., logical channels) within a MAC PDU (e.g., a transmission block). In one example, the MAC PDU may include a MAC header containing a plurality of MAC subheaders. A MAC subheader within the plurality of MAC subheaders may correspond to a MAC CE or MAC SUD (logical channel) within one or more MAC CEs and / or one or more MAC SDUs.In one example, a Logical Channel IDentifier (LCID) may be configured on a MAC CE or a logical channel. In one example, the LCID for the logical channel or MAC CE may be fixed or pre-configured. In one example, the LCID for the logical channel or MAC CE may be configured for a wireless device by a base station. A MAC subheader corresponding to a MAC CE or MAC SDU may include an LCID associated with the MAC CE or MAC SDU.

[0020] In one example, a base station may enable and / or disable and / or affect one or more processes in a wireless device by employing one or more MAC commands (e.g., may set the value of one or more parameters of one or more processes or start and / or stop one or more timers of one or more processes). One or more MAC commands may include one or more MAC control elements. In one example, one or more processes may include enabling and / or disabling PDCP packet replication for one or more wireless bearers. The base station may transmit a MAC CE containing one or more fields, the values ​​of which indicate the enabling and / or disabling of PDCP replication for one or more wireless bearers. In one example, one or more processes may include transmitting Channel State Information (CSI) for one or more cells. The base station may transmit one or more MAC CEs indicating the enabling and / or disabling of CSI transmission in one or more cells. In one example, one or more processes may include enabling or disabling one or more secondary cells. In one example, the base station may transmit a MAC CE indicating the activation or deactivation of one or more secondary cells. In one example, the base station may transmit one or more MAC CEs indicating the start and / or stop of one or more Discontinuous Reception (DRX) timers in a wireless device. In one 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).

[0021] FIG. 3 is a block diagram of base stations (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 an NB, eNB, gNB, and / or ng-eNB. In one example, the wireless device and / or base station may operate 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) executable by at least one processor (321A) and stored in non-transient memory (322A). 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) executable by at least one processor (321B) and stored in non-transient memory (322B).

[0022] A base station may include many sectors, such as, for example, 1, 2, 3, 4, or 6 sectors. A base station may include many cells, for example, ranging from 1 to 50 or more. Cells may be classified, for example, as primary cells or secondary cells. In Radio Resource Control (RRC) connection establishment / re-establishment / handover, one serving cell may provide NAS (Non-Access Layer) mobility information (e.g., TAI (Tracking Area Identifier)). In RRC access re-establishment / handover, one serving cell may provide security input. 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 an UL PCC. Depending on the wireless device performance, the 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.

[0023] A cell containing a downlink carrier and optionally an uplink carrier may be assigned a physical cell ID and a cell index. A carrier (downlink or uplink) may belong to a single cell. A cell ID or a cell index may also identify the downlink carrier or uplink carrier of a cell (depending on the context in which it is used). In this disclosure, a cell ID may likewise be referred to as a carrier ID, 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 cell ID may be determined using a synchronization signal transmitted from a downlink carrier. A cell index may be determined using an RRC message. For example, when this disclosure refers to a first physical cell ID for a first downlink carrier, this disclosure may mean that the first physical cell ID is for a cell containing the first downlink carrier. The same concept may apply, for example, to carrier activation. Where the present disclosure indicates that the first carrier is activated, the specification may likewise mean that the cell containing the first carrier is activated.

[0024] A base station may transmit one or more messages (e.g., RRC messages) containing multiple configuration parameters for one or more cells to a wireless device. One or more cells may include at least one primary cell and at least one secondary cell. In one example, the RRC message may be broadcast or unitcast to the wireless device. In one example, the configuration parameters may include common parameters and dedicated parameters.

[0025] Services and / or functions of the RRC sublayer may include: broadcasting of system information related to AS and NAS; paging initiated by 5GC and / or NG-RAN; establishment, maintenance, and / or release of RRC connections between a radio device and NG-RAN, which may include the addition, modification, and release of carrier aggregation; or at least one of the addition, modification, and / or release of duplex connections in NR or between E-UTRA and NR. Services and / or functions of the RRC sublayer may further include: security functions including key management; establishment, configuration, maintenance, and / or release of signaling radio bearers (SRB) and / or data radio bearers (DRB); handover (e.g., intra-NR movement or inter-RAT movement) and context transmission; or at least one of mobility functions including at least one of radio device cell selection and reselection and control of cell selection and reselection. Services and / or functions of the RRC sublayer may include QoS management functions; radio device measurement configuration / reporting; Detection of wireless link failure and / or recovery from failure; or transmission of NAS messages to / from a wireless device to / from a core network entity (e.g., AMF, Mobility Management Entity (MME)), at least one of which may be further included.

[0026] The RRC sublayer may support an RRC_idle state, an RRC_inactive state, and / or an RRC_connected state for a wireless device. In the RRC_idle state, the wireless device may perform at least one of Public Land Mobile Network (PLMN) selection; reception of broadcasted system information; cell selection / reselection; monitoring / reception of paging for mobile end-of-the-world data initiated by 5GC; paging for mobile end-of-the-world data regions 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 receiving broadcasted system information; cell selection / reselection; monitoring / reception of RAN / CN paging initiated by NG-RAN / 5GC; RAN-based notification regions (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) to the wireless device and / or save the 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 establishing a 5GC-NG-RAN connection (both C / U-planes) to the wireless device; saving the UE AS context for the wireless device; transmitting / receiving unicast data to / from the wireless device; or moving network control 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.

[0027] System information (SI) may be divided into a minimum SI and other SIs. The minimum SI may be broadcast periodically. The minimum SI may include basic information required for initial access and information provided in an order, i.e., scheduling information, intended for periodically obtaining any other SI broadcasts. Other SIs may be broadcast or provided in a dedicated manner, triggered by the network or upon a request from a wireless device. The minimum SI contains different messages (e.g., MasterInformationBlock and SystemInformationBlockType1 It can be transmitted through two different downlink channels using ). The other SI is SystemInformationBlockType2 It can be transmitted via. For a wireless device in the RRC_connected state, dedicated RRC signaling may be used for requests and delivery of other SIs. For a wireless device in the RRC_idle state and / or RRC_inactive state, a request may trigger a random access procedure.

[0028] A wireless device may report wireless access capability information, which may be static. A base station may request certain capabilities for a wireless device to report based on band information. If permitted by the network, a request for a temporary capability limitation may be transmitted by the wireless device 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 acknowledge or deny the request. Temporary capability limitations may be transparent to the 5GC (e.g., static capabilities may be stored in the 5GC).

[0029] When CA is configured, the wireless device can establish an RRC connection with the network. During the RRC connection establishment / reconfiguration / handover procedure, one serving cell can provide NAS mobility information, and during the RRC connection re-establishment / handover, one serving cell can provide security input. This cell may be referred to as a PCell. Depending on the capabilities of the wireless device, the SCell may be configured to form a set of serving cells together with the PCell. The configured set of serving cells for the wireless device may include one PCell and one or more SCells.

[0030] The reconfiguration, addition, and removal of SCells can be performed by RRC. During intra-NR handover, RRC can also add, remove, or reconfigure SCells for use with the target PCell. When adding a new SCell, dedicated RRC signaling can be used to transmit all required system information of the SCell; that is, while in connection mode, the wireless device may not need to acquire system information broadcast directly from the SCell.

[0031] The purpose of the RRC connection reconfiguration procedure may be to modify the RRC connection (e.g., to establish, modify, and / or release an RB, perform a handover, set up, modify, and / or release measurements, and add, modify, and / or release SCells and cell groups). As part of the RRC connection reconfiguration procedure, NAS-specific information may be transmitted from the network to the wireless device. RRCConnectionReconfiguration The message may be a command to modify the RRC connection. It may convey information regarding measurement configuration, motion control, and radio resource configuration (e.g., RB, MAC main configuration, and physical channel configuration), including any associated dedicated NAS information and security configuration. The received RRC connection reconfiguration message sCellToReleaseList If it includes, the wireless device can perform SCell release. The received RRC connection reconfiguration message sCellToAddModList If it includes, the wireless device can perform SCell addition or modification.

[0032] The RRC connection establishment (or re-establish, resume) procedure may establish (or re-establish, resume) an RRC connection. The RRC connection establishment procedure may include SRB1 establishment. The RRC connection establishment procedure may be used to transmit initial NAS-specific information / messages from a wireless device to the E-UTRAN. RRCConnectionReestablishment The message can be used to re-establish SRB1.

[0033] The measurement reporting procedure may involve transmitting measurement results from a wireless device to the NG-RAN. The wireless device may initiate the measurement reporting procedure after successful security activation. A measurement report message may be used to transmit the measurement results.

[0034] A 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) executable by at least one processor (314) and stored in non-transient memory (315). The wireless device (110) may further include 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).

[0035] The processor (314) of the wireless device (110), the processor (321A) of base station 1 (120A) and / or the processor (321B) of 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 device, discrete gate and / or transistor logic, discrete hardware components, etc. The processor (314) of the wireless device (110), the processor (321A) of base station 1 (120A) and / or the processor (321B) of base station 2 (120B) may perform at least one of signal coding / processing, data processing, power control, input / output processing, and / or any other function that enables the wireless device (110), base station 1 (120A) and / or base station 2 (120B) to operate in a wireless environment.

[0036] The processor (314) of the wireless device (110) may be connected to a speaker / microphone (311), a keypad (312), and / or a 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) within the wireless device (110) may receive power from a power source (317) and / or be configured to distribute power to other components of the wireless device (110). The power source (317) may include at least one of one or more batteries, solar cells, fuel cells, etc. The processor (314) may be connected to a GPS chipset (318). The GPS chipset (318) may be configured to provide geographic location information of the wireless device (110).

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

[0038] 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 individually with the communication interface (310) of the wireless device (110) via the wireless link (330A) and / or the wireless link (330B). In one 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.

[0039] 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 base station 1 (120A) and / or the communication interface (320B) of base station 2 (120B). Base station 1 (120A) and the wireless device (110) and / or base station 2 (120B) and the wireless device (110) may each be configured to transmit and receive transmission blocks through the wireless link (330A) and / or the wireless link (330B). The wireless link (330A) and / or the wireless link (330B) may use at least one frequency carrier. According to some of the various aspects of the embodiment, transceiver(s) may be used. The transceiver may be a device comprising both a transmitter and a receiver. The transceiver may be used in devices such as wireless devices, base stations, relay nodes, and / or others. Exemplary embodiments of wireless technology implemented in communication interfaces (310, 320A, 320B) and wireless links (330A, 330B) are illustrated in FIG. 4a, 4b, 4c, 4d, 6, 7a, 7b, 8 and the accompanying text.

[0040] In one example, other nodes of the wireless network (e.g., AMF, UPF, SMF, etc.) may include one or more communication interfaces, one or more processors, and memory for storing instructions.

[0041] A node (e.g., a wireless device, a base station, an AMF, an SMF, a UPF, servers, switches, antennas, and / or others) may include one or more processors, and memory that stores instructions that cause the node to perform specific processes and / or functions when executed by one or more processors. Exemplary embodiments may enable operation of single-carrier and / or multi-carrier communication. Other exemplary embodiments may include a non-transient type computer-readable medium containing instructions executable by one or more processors to induce operation of single-carrier and / or multi-carrier communication. Yet another exemplary embodiment may include a non-transient type computer-readable machine-accessible medium having encoded instructions to enable programmable hardware to enable the node to operate of single-carrier and / or multi-carrier communication. The node may include a processor, memory, interfaces, etc.

[0042] 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 electronic devices such as connectors, wires, drivers, amplifiers, and / or others. The software interface may include code stored in a memory device to implement protocol(s), a protocol layer, a communication driver, a device driver, a combination thereof, and / or others. The firmware interface may include a combination of embedded hardware and code stored in a memory device and / or communicating with the memory device to implement connections, electronic device operation, protocol(s), a protocol layer, a communication driver, a device driver, hardware operation, a combination thereof, and / or others.

[0043] FIGS. 4a, 4b, 4c, and 4d are exemplary diagrams for uplink and downlink signal transmission according to one aspect of one embodiment of the present disclosure. FIG. 4a illustrates an exemplary uplink transmitter for at least one physical channel. A baseband signal representing a physical uplink shared channel may perform one or more functions. One or more functions include scrambling; modulation of scrambling bits to generate complex-valued symbols; mapping of complex-valued modulation symbols to one or more transport layers; transform precoding to generate complex-valued symbols; precoding of complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generation of a complex-valued time-domain single carrier-frequency division multiple access (SC-FDMA) or CP-OFDM signal for an antenna port; It may include at least one of and / or others. In one example, when conversion precoding is enabled, an SC-FDMA signal for uplink transmission may be generated. In one example, when conversion precoding is not enabled, a CP-OFDM signal for uplink transmission may be generated by FIG. 4a. These functions are illustrated as examples, and it is expected that various mechanisms may be implemented in various embodiments.

[0044] An exemplary structure for modulation and up-conversion of complex value SC-FDMA or CP-OFDM baseband signals to carrier frequencies for antenna port and / or physical random access channel (PRACH) baseband signals of complex values ​​is illustrated in FIG. 4b. Filtering may be used before transmission.

[0045] An exemplary structure for downlink transmission is illustrated in FIG. 4c. A baseband signal representing a downlink physical channel may perform one or more functions. One or more functions may include: scrambling of bits coded within a codeword to be transmitted over the physical channel; modulation of the scrambling bits to generate modulation symbols of complex values; mapping of modulation symbols of complex values ​​onto one or several transport layers; precoding of modulation symbols of complex values ​​onto a layer for transmission over an antenna port; mapping of modulation symbols of complex values ​​to resource elements for the antenna port; generation of a time-domain OFDM signal of complex values ​​for the antenna port; and / or other such functions. These functions are illustrated by example, and it is expected that various mechanisms may be implemented in various embodiments.

[0046] In one example, a gNB can transmit a first symbol and a second symbol on an antenna port to a wireless device. The wireless device can estimate a channel for transmitting a second symbol on an antenna port (e.g., fading gain, multipath delay, etc.) from a channel for transmitting a first symbol on an antenna port. In one example, if one or more large-scale characteristics of the channel for transmitting a first symbol on a first antenna port can be estimated from the channel for transmitting a second symbol on a second antenna port, the first antenna port and the second antenna port may be placed in quasi-same locations. One or more large-scale characteristics may include at least one of delay spread; Doppler spread; Doppler shift; average gain; average delay; and / or spatial receive (Rx) parameters.

[0047] Exemplary modulation and upconversion of a complex OFDM baseband signal for an antenna port with respect to the carrier frequency are illustrated in FIG. 4d. Filtering may be used before transmission.

[0048] FIG. 5a is a diagram of an exemplary uplink channel mapping and exemplary uplink physical signals. FIG. 5b is a diagram of an exemplary downlink channel mapping and exemplary downlink physical signals. In one example, the physical layer may provide one or more information transmission services to the MAC and / or one or more upper layers. For example, the physical layer may provide one or more information transmission services to the MAC through one or more transmission channels. An information transmission service may indicate how and with what characteristics data is transmitted through a wireless interface.

[0049] In an exemplary embodiment, the wireless network may include one or more downlink and / or uplink transmission channels. For example, the diagram in FIG. 5a illustrates an exemplary uplink transmission channel including an uplink shared channel (UL-SCH) (501) and a random access channel (RACH) (502). The diagram in FIG. 5b illustrates an exemplary downlink transmission channel including a downlink shared channel (DL-SCH) (511), a paging channel (PCH) (512), and a broadcast channel (BCH) (513). The transmission 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) can be mapped to a physical broadcast channel (PBCH) (516).

[0050] There may be one or more physical channels that do not have a corresponding transmission channel. 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 the UCI (509) from the UE to the base station. For example, a physical downlink control channel (PDCCH) (515) may carry the DCI (517) from the base station to the UE. NR may support multiplexing of the UCI (509) in PUSCH (503) if the transmission of the UCI (509) and PUSCH (503) can match at least partially in a slot. The UCI (509) may include at least one of a CSI, an ACK (acknowledgment) / NACK (negative acknowledgment), and / or a scheduling request. The DCI (517) on the PDCCH (515) may indicate at least one of one or more downlink allocations and / or one or more uplink scheduling grants.

[0051] In the uplink, the UE may transmit one or more reference signals (RS) to the base station. For example, 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 one or more RSs to the UE (e.g., unicast, multicast, and / or broadcast). For example, 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).

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

[0053] In one example, whether an uplink PT-RS (507) exists may depend on the RRC configuration. For example, the presence of an uplink PT-RS may be configured specifically for the UE. For example, the presence and / or pattern of an uplink PT-RS (507) within a scheduled resource may be configured specifically for the UE by a combination of associations with one or more parameters used for RRC signaling and / or other purposes indicated by DCI (e.g., Modulation and Coding Scheme (MCS)). If configured, the dynamic presence of an uplink PT-RS (507) may be associated with at least one DCI parameter including an MCS. The wireless network may support multiple uplink PT-RS densities defined in the time / frequency domain. The frequency domain densities may be associated with at least one configuration of the scheduled bandwidth, if present. The UE may assume the same precoding for the DMRS port and the PT-RS port. The number of PT-RS ports may be fewer than the number of DM-RS ports of the scheduled resources. For example, the uplink PT-RS (507) may be limited to the scheduled time / frequency duration for the UE.

[0054] In one example, the UE may transmit an SRS (508) to the 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 allocate one or more blocks of good quality resources for uplink PUSCH transmissions from the UE. The base station may semi-statistically configure one or more sets of SRS resources for the UE. For an SRS resource set, the base station may configure one or more SRS resources for the UE. The applicability of an SRS resource set may be configured by upper-level (e.g., RRC) parameters. For example, if the upper-level parameter indicates beam management, the SRS resources within each of one or more SRS resource sets may be transmitted at once. The UE may transmit one or more SRS resources within different SRS resource sets simultaneously. The new radio access technology network may support non-periodic, periodic, and / or semi-continuous SRS transmissions. The UE may transmit SRS resources based on one or more trigger types, wherein one or more trigger types may include upper layer signaling (e.g., RRC) and / or one or more DCI formats (e.g., at least one DCI format may be used by the UE to select at least one of one or more configured sets of SRS resources). SRS trigger type 0 may represent an SRS triggered based on upper layer signaling. SRS trigger type 1 may represent an SRS triggered based on one or more DCI formats. In one example, when PUSCH (503) and SRS (508) are transmitted in the same slot, the UE may be configured to transmit SRS (508) after the transmission of PUSCH (503) and the corresponding uplink DM-RS (506).

[0055] In one example, the base station may semi-statistically configure one or more SRS configuration parameters representing at least one of the following to the UE: an SRS resource configuration identifier, a plurality of SRS ports, time domain behavior of the SRS resource configuration (e.g., indication of periodic, semi-continuous, or non-periodic SRS), slot (mini-slot, and / or subframe) level periodicity and / or offset for periodic and / or non-periodic SRS resources, a plurality of OFDM symbols within the SRS resource, the start OFDM symbol of the SRS resource, SRS bandwidth, frequency hopping bandwidth, cyclic shift, and / or SRS sequence ID.

[0056] In one example, in the time domain, the SS / PBCH block may contain one or more OFDM symbols within the SS / PBCH block (e.g., four OFDM symbols numbered in ascending order from 0 to 3). The SS / PBCH block may contain a PSS / SSS (521) and a PBCH (516). In one example, in the frequency domain, the SS / PBCH block may contain one or more contiguous subcarriers within the SS / PBCH block (e.g., 240 contiguous subcarriers having subcarriers numbered in ascending order from 0 to 239). For example, the PSS / SSS (521) may occupy one OFDM symbol and 127 subcarriers. For example, the PBCH (516) may span three OFDM symbols and 240 subcarriers. A UE may assume that one or more SS / PBCH blocks transmitted with the same block index may be quasi-colocated with respect to, for example, Doppler spread, Doppler shift, mean gain, mean delay, and spatial Rx parameters. A UE may not assume quasi-colocation for the transmission of other SS / PBCH blocks. The periodicity of the SS / PBCH blocks may be configured by a wireless network (e.g., by RRC signaling), and one or more time positions in which the SS / PBCH blocks may be transmitted may be determined by subcarrier intervals. In one example, unless the wireless network configures the UE to take different subcarrier intervals, the UE may take a band-specific subcarrier interval for the SS / PBCH blocks.

[0057] In one example, the downlink CSI-RS (522) may be used by the UE to obtain channel state information. The wireless network may support periodic, non-periodic, and / or semi-continuous transmission of the downlink CSI-RS (522). For example, a base station may semi-statistically configure and / or reconfigure the periodic transmission of the downlink CSI-RS (522) to the UE. The configured CSI-RS resources may be enabled and / or disabled. For semi-continuous transmission, the activation and / or deactivation of the CSI-RS resources may be dynamically triggered. In one example, the CSI-RS configuration may include one or more parameters representing at least a number of antenna ports. For example, the base station may configure 32 ports for the UE. The base station may semi-statistically configure one or more sets of CSI-RS resources for the UE. One or more CSI-RS resources may be assigned to one or more UEs from one or more sets of CSI-RS resources. For example, a base station may semi-statistically configure one or more parameters representing CSI-RS resource mapping, such as the time-domain location of one or more CSI-RS resources, the bandwidth of the CSI-RS resources, and / or periodicity. In one example, the UE may be configured to use the same OFDM symbols for the downlink CSI-RS (522) and the control resource set (core set) when the downlink CSI-RS (522) and the core set are spatially quasi-co-located and the resource element associated with the downlink CSI-RS (522) is outside the PRB configured for the core set. In one example, the UE may be configured to use the same OFDM symbols for the downlink CSI-RS (522) and SSB / PBCH when the downlink CSI-RS (522) and SSB / PBCH are spatially quasi-collocated and the resource element associated with the downlink CSI-RS (522) is outside the PRB configured for the SSB / PBCH.

[0058] In one example, the UE may transmit one or more downlink DM-RS (523) to the base station for channel estimation, for example, for coherent demodulation of one or more downlink physical channels (e.g., PDSCH (514)). For example, the wireless 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-loaded DM-RS pattern. A front-loaded DM-RS may be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station may semi-statistically configure up to a maximum number of front-loaded DM-RS symbols for the PDSCH (514) to the UE. For example, a DM-RS configuration may support one or more DM-RS ports. For example, for single-user MIMO, a DM-RS configuration may support at least eight orthogonal downlink DM-RS ports. For example, in the case of multi-user MIMO, the DM-RS configuration may support 12 orthogonal downlink DM-RS ports. The wireless network may support a common DM-RS structure for DL ​​and UL at least for CP-OFDM, where the DM-RS location, DM-RS pattern and / or scrambling sequence may be the same or different.

[0059] In one example, whether a downlink PT-RS (524) exists may depend on the RRC configuration. For example, the presence of the downlink PT-RS (524) may be configured specifically by the UE. For example, the presence and / or pattern of the downlink PT-RS (524) within a scheduled resource may be configured specifically by the UE by a combination of associations with one or more parameters used for RRC signaling and / or other purposes (e.g., MCS) that may be indicated by DCI. If configured, the dynamic presence of the downlink PT-RS (524) may be associated with at least one DCI parameter including MCS. The wireless network may support multiple PT-RS densities defined in the time / frequency domain. The frequency domain density may be associated with at least one configuration of the scheduled bandwidth, if present. The UE may assume the same precoding for the DMRS ports and PT-RS ports. Multiple PT-RS ports may be fewer than the number of DM-RS ports in the scheduled resource. For example, the downlink PT-RS (524) may be limited to a scheduled time / frequency duration for the UE.

[0060] FIG. 6 is a diagram of an exemplary frame structure for a carrier according to one aspect of one embodiment of the present disclosure. A multi-carrier OFDM communication system may include one or more carriers, for example, ranging from 1 to 32 in the case of carrier aggregation, or from 1 to 64 in the case of duplex connection. Different radio frame structures may be supported (e.g., FDD and TDD duplex mechanisms). FIG. 6 illustrates an example of a frame structure. Downlink and uplink transmissions may be structured into a radio frame (601). In this example, the radio frame duration is 10 ms. In this example, the 10 ms radio frame (601) may be divided into 10 subframes (602) of equal size having a duration of 1 ms. The subframe(s) may include one or more slots (e.g., slots (603 and 605)) according to the subcarrier interval and / or CP length. For example, subframes having subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, and 480 kHz may each contain 1, 2, 4, 8, 16, and 32 slots, respectively. In FIG. 6, a subframe may be divided into two slots (603) of the same size having a duration of 0.5 ms. For example, 10 subframes may be available for downlink transmission, and 10 subframes may be available for uplink transmission at 10 ms intervals. Uplink and downlink transmissions may be separated in the frequency domain. The slot(s) may contain a plurality of OFDM symbols (604). The number of OFDM symbols (604) within a slot (605) may depend on the cyclic prefix length. For example, the slot can be 14 OFDM symbols for the same subcarrier spacing of up to 480 kHz with normal CP.A slot may be 12 OFDM symbols for the same subcarrier spacing of 60 kHz with an extended CP. A slot may include a downlink, an uplink, or a downlink portion and an uplink portion and / or other.

[0061] FIG. 7a is a graph illustrating sets of exemplary OFDM subcarriers according to one aspect of one embodiment of the present disclosure. In this example, a gNB may communicate with a wireless device with a carrier having an exemplary channel bandwidth (700). In this graph, arrow(s) may illustrate subcarriers in a multi-carrier OFDM system. The OFDM system may use technologies such as OFDM technology, SC-FDMA technology, etc. In one example, an arrow (701) indicates a subcarrier transmitting information symbols. In one example, the subcarrier spacing (702) between two adjacent subcarriers within a carrier may be any one of 15KHz, 30KHz, 60KHz, 120KHz, 240KHz, etc. In one example, different subcarrier spacings may correspond to different transmission numerologies. In one example, the transmission numerology comprises, at least, a numerology index; Value of the subcarrier spacing; may include a periodic prefix (CP) of a predetermined type. In one example, the gNB may transmit to / receive from the UE on a plurality of subcarriers (703) within the carrier. In one example, the bandwidth occupied by the plurality of subcarriers (703) (transmission bandwidth) may be smaller than the channel bandwidth (700) of the carrier due to guard bands (704 and 705). In one example, the guard bands (704 and 705) may be used to reduce interference to and from one or more adjacent carriers. The plurality of subcarriers (transmission bandwidth) within the carrier may depend on the channel bandwidth and subcarrier spacing of the carrier. For example, for a carrier having a 20 MHz channel bandwidth and a 15 kHz subcarrier spacing, the number of subcarriers may be 1024.

[0062] In one example, the gNB and the wireless device may communicate with multiple CCs if CA is configured therein. In one example, if CA is supported, different component carriers may have different bandwidths and / or subcarrier spacings. In one example, the gNB may transmit a first type of service to the UE via the first component carrier. The gNB may transmit a second type of service to the UE via the second component carrier. Different types of services may have different service requirements (e.g., data rate, latency, reliability) suitable for transmission via different component carriers having different subcarrier spacings and / or bandwidths. FIG. 7b illustrates an exemplary embodiment. 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 interval (710). The third component carrier may include a third number of subcarriers (708) having a third subcarrier interval (711). The carriers of the multi-carrier OFDM communication system may be adjacent carriers, non-adjacent carriers, or a combination of both adjacent and non-adjacent carriers.

[0063] FIG. 8 is a diagram illustrating OFDM radio resources according to one aspect of one embodiment of the present disclosure. In one example, the carrier may have a transmission bandwidth (801). In one example, the resource grid may have a structure in the frequency domain (802) and the time domain (803). In one example, the resource grid may include a first number of OFDM symbols in a subframe and a second number of resource blocks starting from a common resource block indicated by transmission numerology and upper-level signaling for the carrier (e.g., RRC signaling). In one example, in the resource grid, the resource unit identified by the subcarrier index and the symbol index may be a resource element (805). In one example, the subframe may include a first number of OFDM symbols (807) according to the numerology associated with the carrier. For example, if the subcarrier spacing of the carrier's numerology is 15 kHz, the subframe may have 14 OFDM symbols for the carrier. If the subcarrier spacing of the numerology is 30 kHz, the subframe may have 28 OFDM symbols. If the subcarrier spacing of the numerology is 60 kHz, the subframe may have 56 OFDM symbols. In one example, the second number of resource blocks included in the carrier's resource grid may depend on the carrier's bandwidth and numerology.

[0064] As illustrated in FIG. 8, a resource block (806) may include 12 subcarriers. In one example, a plurality of resource blocks may be grouped into a Resource Block Group (RBG) (804). In one example, the size of the RBG may depend on at least one of an RRC message indicating the RBG size configuration; the size of the carrier bandwidth; or the size of a portion of the carrier bandwidth. In one example, the carrier may include a plurality of bandwidth portions. A first bandwidth portion of the carrier may have a frequency position and / or bandwidth different from a second bandwidth portion of the carrier.

[0065] In one example, the gNB may transmit downlink control information, including downlink or uplink resource block allocation, to a wireless device. The base station may transmit to or receive from the wireless device data packets (e.g., transmission blocks) scheduled and transmitted through one or more resource blocks and one or more slots according to the parameters of the downlink control information and / or RRC message(s). In one example, a start symbol for the first slot of one or more slots may be indicated to the wireless device. In one example, the gNB may transmit to or receive from the wireless device data packets scheduled in one or more RBGs and one or more slots.

[0066] In one example, the gNB may transmit downlink control information, including downlink allocation, to a wireless device via one or more PDCCHs. The downlink allocation may include parameters representing at least modulation and coding formats; resource allocation; and / or HARQ information related to DL-SCH. In one example, the resource allocation may include parameters for resource block allocation; and / or slot allocation. In one example, the gNB may dynamically allocate resources to a wireless device via a Cell-to-Wireless Network Temporary Identifier (C-RNTI) on one or more PDCCHs. The wireless device may monitor the PDCCH(s) to discover available allocations when its downlink reception is enabled. When the wireless device successfully detects one or more PDCCHs, it may receive one or more downlink data packages on one or more PDSCHs scheduled by the one or more PDCCHs.

[0067] In one example, the gNB may allocate a scheduling (CS) resource configured for downlink transmission to a wireless device. The gNB may transmit one or more RRC messages indicating the periodicity of the CS acknowledgment. The gNB may transmit a DCI via a PDCCH addressed to a configured scheduling-RNTI (CS-RNTI) that enables the CS resource. The DCI may include a parameter indicating whether the downlink acknowledgment is a CS acknowledgment. The CS acknowledgment may be implicitly reused according to a period defined by one or more RRC messages until it is disabled.

[0068] In one example, the gNB may transmit downlink control information, including uplink acknowledgments, to a wireless device via one or more PDCCHs. The uplink acknowledgments may include parameters representing at least modulation and coding formats; resource allocation; and / or HARQ information related to UL-SCHs. In one example, resource allocation may include parameters for resource block allocation; and / or slot allocation. In one example, the gNB may dynamically allocate resources to a wireless device via C-RNTIs on one or more PDCCHs. The wireless device may monitor one or more PDCCHs to discover available resource allocations. When the wireless device successfully detects one or more PDCCHs, it may transmit one or more uplink data packages via one or more PUSCHs scheduled by the one or more PDCCHs.

[0069] In one example, the gNB may allocate a CS resource to a wireless device for uplink data transmission. The gNB may transmit one or more RRC messages indicating the periodicity of the CS acknowledgment. The gNB may transmit a DCI via a PDCCH addressed to a CS-RNTI that enables the CS resource. The DCI may include a parameter indicating that the uplink acknowledgment is a CS acknowledgment. The CS acknowledgment may be implicitly reused according to a period defined by one or more RRC messages until it is disabled.

[0070] In one example, the base station may transmit DCI / control signaling via PDCCH. The DCI may take a format in multiple formats. The DCI may include downlink and / or uplink scheduling information (e.g., resource allocation information, HARQ-related parameters, MCS), CSI requests (e.g., non-periodic CQI reports), SRS requests, uplink power control commands for one or more cells, and one or more timing information (e.g., TB transmit / receive timing, HARQ feedback timing, etc.). In one example, the DCI may indicate an uplink acknowledgment containing transmission parameters for one or more transmission blocks. In one example, the DCI may indicate a downlink allocation indicating parameters for receiving one or more transmission blocks. In one example, the DCI may be used by the base station to initiate contention-free random access from a wireless device. In one example, the base station may transmit a DCI including a Slot Format Indicator (SFI) that notifies a slot format. In one example, the base station may transmit a DCI containing a pre-emption indication that notifies PRB(s) and / or OFDM symbol(s) when the UE does not take any transmission intended for that UE. In one example, the base station may transmit a DCI for group power control of PUCCH, PUSCH, or SRS. In one example, the DCI may correspond to an RNTI. In one example, the radio device may acquire an RNTI in response to completing an initial access (e.g., C-RNTI). In one example, the base station may configure an RNTI for the radio (e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI).In one example, the radio device can calculate an RNTI (e.g., the radio device can calculate an RA-RNTI based on the resources used for transmitting the preamble). In one example, the RNTI may have a pre-configured value (e.g., P-RNTI or SI-RNTI). In one example, the radio device can monitor a group common search space that may be used by a base station to transmit DCIs intended for a group of UEs. In one example, the group common DCI may correspond to an RNTI commonly configured for a group of UEs. In one example, the radio device can monitor a UE-specific search space. In one example, the UE-specific DCI may correspond to an RNTI configured for the radio device.

[0071] 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 blocks, which may include at least a PSS, SSS, and / or PBCH. A radio device may measure the quality of a beam-pair link using one or more RSs. 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 a PBCH may be used as RSs to measure the quality of a beam-pair link. The quality of a beam-pair link may be defined by a Reference Signal Received Output (RSRP) value, or a Reference Signal Received Quality (RSRQ) value and / or a CSI value measured on the RS resources. The base station may indicate whether the RS resources used to measure the quality of the beam-pair link are quasi-co-located (QCLed) with the DM-RS of the control channel. The RS resources and DM-RS of the control channel may be referred to as quasi-collocated (QCLed) when the channel characteristics from the transmission to the wireless device on the RS and the channel characteristics from the transmission to the wireless device on the control channel are similar or identical under configured criteria. In multi-beam operation, the wireless device may perform uplink beam sweeping to access the cell.

[0072] In one example, a wireless device may be configured to simultaneously monitor a PDCCH on one or more beam pair 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 the wireless device to monitor a PDCCH on one or more beam pair links at different PDCCH OFDM symbols. For example, the base station may transmit upper-layer signaling (e.g., RRC signaling) or MAC CE containing parameters related to the wireless device's Rx beam settings to monitor a PDCCH on one or more beam pair links. The base station may transmit an indication of the spatial QCL assumption between the DL RS antenna port(s) (e.g., cell-specific CSI-RS, or wireless device-specific CSI-RS, or SS block, or PBCH with or without DM-RS) and the DL RS antenna port(s) of the PBCH for demodulation of the DL control channel. Signaling for beam indication to PDCCH may be MAC CE signaling, or RRC signaling, or DCI signaling, or specification-transparent and / or implicit methods, and combinations of these signaling methods.

[0073] For reception of a unicast DL data channel, a base station may indicate spatial QCL parameters between the DL RS antenna port(s) and the DM-RS antenna port(s) of the DL data channel. The base station may transmit a DCI (e.g., downlink acknowledgment) containing information indicating the RS antenna port(s). The information may indicate the RS antenna port(s) that can be QCLed with the DM-RS antenna port(s). Different sets of DM-RS antenna port(s) for the DL data channel may be indicated as QCLs together with different sets of RS antenna port(s).

[0074] FIG. 9a is an example of beam sweeping in a DL channel. In the RRC_INACTIVE or 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 the SS beam to multiple beams along with forming the SS burst (940). One or more SS blocks may be transmitted on a single beam. When multiple SS bursts (940) are transmitted to multiple beams, the SS bursts may together form an SS burst set (950).

[0075] A 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 CSI-RS. For example, based on RSRP measurements for CSI-RS, the wireless device may report a beam index associated with the RSRP value of the beam, as indicated in the CRI, for downlink beam selection. CSI-RS may be transmitted over a CSI-RS resource comprising at least one antenna port and at least one time or frequency radio resource. The CSI-RS resource 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 the cell-specific CSI-RS resource. A dedicated subset of wireless devices covered by a cell may measure the wireless device-specific CSI-RS resource.

[0076] CSI-RS resources can be transmitted periodically using non-periodic transmission or multi-shot or semi-continuous transmission. For example, in the periodic transmission of FIG. 9a, the base station (120) can periodically transmit the configured CSI-RS resources (940) using periodicity configured in the time domain. In non-periodic transmission, the configured CSI-RS resources can be transmitted in a dedicated time slot. In multi-shot or semi-continuous transmission, the configured CSI-RS resources can be transmitted within a configured period. The beam used for CSI-RS transmission may have a different beam width than the beam used for SS-block transmission.

[0077] FIG. 9b is an example of a beam management procedure in an exemplary new wireless access technology network. A base station (120) and / or a 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 the wireless device (110) and one or more base stations (120). In one example, the P-1 procedure (910) may be used to enable the wireless device (110) to measure one or more transmission (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). For beam forming at the base station (120), the base station (120) may sweep a set of different TX beams. For beamforming in the wireless device (110), the wireless device (110) may sweep a set of different Rx beams. In one 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) in order to enable the wireless device (110) to change a first set of Tx beams associated with the base station (120). The P-2 procedure (920) may be performed on a beam set for smaller beam refinement than in the P-1 procedure (910). The P-2 procedure (920) may be a special case of the P-1 procedure (910). In one 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) in order to change a first set of Rx beams associated with the wireless device (110).

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

[0079] In an exemplary embodiment, the new wireless access technology network may support Bandwidth Adaptation (BA). In one example, the receiving and / or transmitting bandwidth configured by a UE using BA may not be large. For example, the receiving and / or transmitting bandwidth may not be as large as the cell bandwidth. The receiving and / or transmitting bandwidth may be adjustable. For example, the UE may change the receiving and / or transmitting bandwidth to contract, for example, during periods of low activity, to save power. For example, the UE may change the position of the receiving and / or transmitting bandwidth in the frequency domain, for example, to increase scheduling flexibility. For example, the UE may change the subcarrier spacing to allow for different services.

[0080] In an exemplary embodiment, a subset of the cell's total cell bandwidth may be referred to as a Bandwidth Part (BWP). A base station may configure one or more BWPs to achieve BA for a UE. For example, the base station may indicate to the UE which of the one or more (configured) BWPs is the active BWP.

[0081] FIG. 10 is an exemplary diagram of three BWPs configured, namely BWP1 (1010 and 1050) with a width of 40 MHz and a subcarrier spacing of 15 kHz; BWP2 (1020 and 1040) with a width of 10 MHz and a subcarrier spacing of 15 kHz; and BWP3 (1030) with a width of 20 MHz and a subcarrier spacing of 60 kHz.

[0082] In one example, a UE configured to operate on one or more BWPs of a cell may be configured by one or more upper layers (e.g., RRC layer) for the cell, such as a set of one or more BWPs (e.g., up to 4 BWPs) for transmission by the UE in the UL bandwidth by at least one parameter UL-BWP for the cell (UL BWP set) and a set of one or more BWPs (e.g., up to 4 BWPs) for reception by the UE in the DL bandwidth by at least one parameter DL-BWP.

[0083] To enable BA on a PCell, the base station may configure one or more UL and DL BWP pairs on the UE. To enable BA on a SCell (e.g., for CA), the base station may configure at least one DL BWP on the UE (e.g., there may be nothing on the UL).

[0084] In one example, the initial active DL BWP may be defined by at least one of the location and number of adjacent PRBs for a set of control resources for at least one common search space, subcarrier spacing, or periodic prefix code. For operation on a PCell, one or more upper-level parameters may represent at least one initial UL BWP for a random access procedure. When a secondary carrier on a primary cell is configured in a UE, an initial BWP for a random access procedure on the secondary carrier may be configured in the UE.

[0085] In one example, for unpaired spectrum operation, the UE can expect the center frequency for the DL BWP to be the same as the center frequency for the UL BWP.

[0086] For example, for each DL BWP or UL BWP within a set of one or more DL BWPs or one or more UL BWPs, the base station may semi-statistically configure a specific UE for a specific cell with one or more parameters representing at least one of the following: subcarrier spacing; periodic prefix code; a plurality of adjacent PRBs; an index within 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 the configured set of DL BWPs and UL BWPs; DCI sensing for PDSCH reception timing; PDSCH reception for HARQ-ACK transmission timing value; DCI sensing for PUSCH transmission timing value; an offset of the first PRB of each DL bandwidth or UL bandwidth related to the first PRB of the bandwidth.

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

[0088] For a UL BWP within one or more UL BWP sets, the base station may configure one or more resource sets for one or more PUCCH transmissions to the UE.

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

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

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

[0092] In one example, the base station may semi-statistically configure one or more BWPs for the UE. The UE may switch the active BWP from the first BWP to the second BWP in response to receiving a DCI indicating the second BWP as the active BWP and / or in response to the expiration of a BWP inactivity timer (e.g., the second BWP may be the default BWP). For example, FIG. 10 is an exemplary diagram of three BWPs configured, namely BWP1 (1010 and 1050), BWP2 (1020 and 1040), and BWP3 (1030). BWP2 (1020 and 1040) may be the default BWP. BWP1 (1010) may be the initial active BWP. In one example, the UE may switch the active BWP from BWP1 (1010) to BWP2 (1020) in response to the 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 occur in response to receiving a DCI indicating the active BWP and / or in response to the expiration of a BWP inactive timer.

[0093] In one example, if the UE is configured to have a default DL BWP and a timer value among the configured DL BWPs for the secondary cell, the UE procedure for the secondary cell may be the same as that for the primary cell using the default DL BWP and the timer value for the secondary cell.

[0094] In one example, when a base station configures a first active DL BWP and a first active UL BWP on a secondary cell or carrier for a UE, the UE may use the indicated DL BWP and indicated UL BWP on the secondary cell as individual first active DL BWP and first active UL BWP on the secondary cell or carrier.

[0095] FIGS. 11a and 11b illustrate packet flow using multiple connections (e.g., dual connection, multiple connection, strict interoperability, and / or others). FIG. 11a is an exemplary diagram of the protocol structure of a wireless device (110) (e.g., UE) having CA and / or multiple connections according to one aspect of an embodiment. FIG. 11b is an exemplary diagram of the protocol structure of a plurality of base stations having CA and / or multiple connections according to one aspect of an embodiment. The plurality of base stations may include a master node, MN (1130) (e.g., master node, master base station, master gNB, master eNB, similar) and secondary nodes, SN (1150) (e.g., secondary base station, secondary gNB, secondary eNB, and / or others). The master node (1130) and the secondary nodes (1150) may cooperate to communicate with the wireless device (110).

[0096] When multiple connections are configured for a wireless device (110), the wireless device (110), capable of supporting multiple receive / transmit functions in an RRC connection state, may be configured to utilize wireless resources provided by multiple schedulers of multiple base stations. Multiple base stations may be interconnected via non-ideal or ideal backhaul (e.g., Xn interface, X2 interface, etc.). A base station associated with multiple connections for a specific wireless device may perform at least one of two different roles: the base station may operate as a master base station or a secondary base station. In multiple connections, the wireless device may be connected to one master base station and one or more secondary base stations. In one example, the master base station (e.g., MN (1130)) may provide a master cell group (MCG) comprising a primary cell and / or one or more secondary cells for the wireless device (e.g., wireless device (110)). A secondary base station (e.g., SN (1150)) may provide a secondary cell group (SCG) comprising a first secondary cell (PSCell) and / or one or more secondary cells for a wireless device (e.g., wireless device (110)).

[0097] In a multiple connection, the wireless protocol architecture used by the bearer depends on how the bearer is configured. In one example, three different types of bearer setup options may be supported: an MCG bearer, an SCG bearer, and / or a split bearer. A wireless device may receive / transmit packets from an MCG bearer through one or more cells of an MCG and / or receive / transmit packets from an SCG bearer through one or more cells of an SCG. A multiple connection may also be described as having at least one bearer configured to use wireless resources provided by a secondary base station. A multiple connection may not be configured or implemented in some of the exemplary embodiments.

[0098] In one example, a wireless device (e.g., wireless device (110)) can transmit and / or receive packets of an MCG bearer through 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)); Packets of a split bearer can be transmitted and / or received through an SDAP layer (e.g., SDAP (1110)), a PDCP layer (e.g., NR PDCP (1112)), one of a master or secondary RLC layer (e.g., MN RLC (1115, SN RLC (1116)), and one of a master or secondary MAC layer (e.g., MN MAC (1118, SN MAC (1119))); and / or packets of an SCG bearer can be transmitted and / or received through 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)).

[0099] In one example, a master base station (e.g., MN (1130)) and / or a secondary base station (e.g., SN (1150)) may transmit / receive packets of an MCG bearer through a master or secondary node SDAP layer (e.g., SDAP (1120), SDAP (1140)), a master or secondary node PDCP layer (e.g., NR PDCP (1121), NR PDCP (1142)), a master node RLC layer (e.g., MN RLC (1124), MN RLC (1125)), and a master node MAC layer (e.g., MN MAC (1128)); and a master or secondary node SDAP layer (e.g., SDAP (1120), SDAP (1140)), a master or secondary node PDCP layer (e.g., NR PDCP (1122), NR PDCP (1143)), a secondary node RLC layer (e.g., SN Packets of the SCG bearer can be transmitted / received through the RLC (1146), SN RLC (1147)), and secondary node MAC layer (e.g., SN MAC (1148)); packets of the split bearer can be transmitted / received through the master or secondary node SDAP layer (e.g., SDAP (1120), SDAP (1140)), master or secondary node PDCP layer (e.g., NR PDCP (1123), NR PDCP (1141)), master or secondary node RLC layer (e.g., MN RLC (1126), SN RLC (1144), SN RLC (1145), MN RLC (1127)), and master or secondary node MAC layer (e.g., MN MAC (1128), SN MAC (1148)).

[0100] In a multiple connection, the wireless device may be configured with multiple MAC entities: one MAC entity for the master base station (e.g., MN MAC (1118)) and another MAC entity for the secondary base station (e.g., SN MAC 1119). In a multiple connection, the configured set of serving cells for the wireless device may include two subsets: an MCG comprising the serving cells of the master base station and an SCG comprising the serving cells of the secondary base station. For the SCG, one or more of the following configurations may apply: at least one cell of the SCG has a configured UL CC, and PUCCH resources are configured in at least one cell of the SCG designated as a primary secondary cell (PSCcell, PCell of the SCG, or sometimes so-called PCell); when the SCG is configured, there may be at least one SCG bearer or one split bearer; When a physical layer problem or random access problem is detected on the PSCell, or when multiple NR RLC retransmissions associated with the SCG arrive, or when an access problem is detected on the PSCell during an SCG addition or SCG change: the RRC connection re-establishment procedure may not be triggered, UL transmissions toward the cell of the SCG may be stopped, the master base station may be notified by the radio device of the type of SCG failure for the split bearer, and DL data transmission through the master base station may be maintained; an NR RLC acknowledged mode (AM) bearer may be configured for the split bearer; the PCell and / or PSCell may not be disabled; the PSCell may be changed by an SCG change procedure (e.g., by a security key change and RACH procedure); and / or a change in bearer type between the split bearer and the SCG bearer or simultaneous configuration of the SCG and the split bearer may be supported or not supported.

[0101] Regarding the interaction between a master base station and secondary base stations for multiple connections, one or more of the following may apply: the master base station and / or secondary base stations may maintain RRM measurement configurations of the radio device; the master base station may determine whether to request the secondary base station to provide additional resources (e.g., serving cells) for the radio device (based on, e.g., received measurement reports, traffic states, and / or bearer types); upon receiving a request from the master base station, the secondary base station may create / modify a container that results in the configuration of additional serving cells for the radio device (or determine that the secondary base station does not have any resources available to do so); for UE performance tuning, the master base station may provide AS configurations and UE performances (parts thereof) to the secondary base station; the master base station and secondary base stations may exchange information regarding UE configurations by using RRC containers (inter-node messages) returned via Xn messages; The secondary base station may initiate the reconfiguration of the secondary base station present in the serving cells (e.g., PUCCH toward the secondary base station); the secondary base station may determine which cell is the PSCell within the SCG; the master base station may change or not change the contents of the RRC configurations provided by the secondary base station; in the case of SCG addition and / or SCG SCell addition, the master base station may provide the most recent (or most up-to-date) measurement results for the SCG cell(s); the master base station and the secondary base station may receive information of each other's SFN and / or subframe offsets from the OAM and / or through the Xn interface (e.g., for the purpose of DRX alignment and / or identification of measurement gaps).In one example, when adding a new SCG SCell, dedicated RRC signaling can be used to transmit necessary system information of the cell, such as CA, excluding the SFN obtained from the MIB of the SCG's PSCell.

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

[0103] In an exemplary 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 Msg1 (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 Msg1 (1220) transmissions and one or more Msg2 (1230) transmissions.

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

[0105] In one example, Msg1 (1220) may be one or more transmissions of random access preambles. In a contention-based random access procedure, the UE may select an SS block having an RSRP higher than the RSRP threshold. If a random access preamble group B exists, the UE may select one or more random access preambles from group A or group B according to the potential Msg3 (1240) size. If a random access preamble group B does not exist, the UE may select one or more random access preambles from group A. The UE may randomly select a random access preamble index from one or more random access preambles associated with the selected group (e.g., with equal probability or a normal distribution). If the base station constructs the association between the random access preambles and the SS blocks for the UE semi-statistically, 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.

[0106] 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 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-RSs for the UE. If at least one of the associated SS blocks having an RSRP higher than a first RSRP threshold, or at least one of the associated CSI-RSs having an RSRP higher than a second RSRP threshold, 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 a beam failure recovery request.

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

[0108] The UE can perform one or more Msg1 (1220) transmissions by transmitting a selected random access preamble. For example, if the UE is configured to select an SS block and have an association between one or more PRACH occasions and one or more SS blocks, the UE can determine a PRACH occasion from one or more PRACH occasions corresponding to the selected SS block. For example, if the UE is configured to select a CSI-RS and have an association between one or more PRACH occasions and one or more CSI-RSs, the UE can determine a PRACH occasion from one or more PRACH occasions corresponding to the selected CSI-RSs. The UE can transmit the selected random access preamble to the base station through the selected PRACH occasions. The UE can determine a transmission output for the transmission of the selected random access preamble based on at least an initial preamble power and a power-ramping factor. The UE can determine an RA-RNTI associated with the selected PRACH occasion in which the selected random access preamble is transmitted. For example, the UE cannot determine the RA-RNTI for a beam failure recovery request. The UE can determine the RA-RNTI based on at least the index of the first OFDM symbol and the index of the first slot of the selected PRACH time and / or the uplink carrier index for the transmission of Msg1 (1220).

[0109] In one example, the UE can receive a random access response, Msg2 (1230), from the base station. To monitor the random access response, the UE can use a time window (e.g., ra-ResponseWindow ) can be initiated. For a beam failover request, the base station can provide the UE with different time windows (e.g.,) to monitor the response to the beam failover request. bfr-ResponseWindow...can be configured. For example, the UE may start a time window (e.g., ra-ResponseWindow or bfr-ResponseWindow) at the beginning of the first PDCCH period 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 a time window at the beginning of the first PDCCH period after a fixed duration of one or more symbols from the end of the first preamble transmission. The UE may monitor the cell's PDCCH for at least one random access response identified by the RA-RNTI or for at least one response to a beam failure recovery request identified by the C-RNTI while a timer for the time window is running.

[0110] In one example, if at least one random access response contains a random access preamble identifier corresponding to a random access preamble transmitted by the UE, the UE may consider the reception of the random access response successful. If the reception of the random access response is successful, the UE may consider it a successfully completed contentless random access procedure. If a contentless random access procedure is triggered for a beam failure recovery request, the UE may consider the contentless random access procedure to be successfully completed if the PDCCH transmission is addressed to C-RNTI. In one example, if at least one random access response contains a random access preamble identifier, the UE may consider the random access procedure to be successfully completed and may indicate the reception of an acknowledgment for a system information request to a higher layer. If the UE has signaled multiple preamble transmissions, the UE may stop the transmission of any remaining preambles (if any) in response to the successful reception of the corresponding random access response.

[0111] In one example, the UE may perform one or more Msg3 (1240) transmissions in response to the successful reception of a random access response (e.g., for a contention-based random access procedure). The UE may adjust the uplink transmission timing based on the timing advanced command indicated by the random access response and transmit one or more transmission blocks based on the uplink acknowledgment indicated by the random access response. The subcarrier interval for the PUSCH transmission of Msg3 (1240) may be provided by at least one upper layer (e.g., RRC) parameter. The UE may transmit a random access preamble via PRACH and Msg3 (1240) through the PUSCH of the same cell. The base station may indicate the UL BWP for the PUSCH transmission of Msg3 (1240) through a system information block. The UE may use HARQ for the retransmission of Msg3 (1240).

[0112] In one example, multiple UEs can perform Msg1 (1220) by transmitting the same preamble to a base station and receiving the same random access response from the base station containing an identity (e.g., TC-RNTI). Contention resolution (1250) can ensure that a UE does not incorrectly use another UE's identity. For example, contention resolution (1250) can be based on a C-RNTI on the PDCCH or a UE contention resolution identity on the DL-SCH. For example, if the base station assigns a C-RNTI to a UE, the UE can perform contention resolution (1250) based on the reception of a PDCCH transmission addressed to the C-RNTI. In response to the detection of the C-RNTI on the PDCCH, the UE can consider the contention resolution (1250) successful and the random access procedure to be successfully completed. If the UE does not have a valid C-RNTI, contention resolution can be handled by using a TC-RNTI. For example, if the MAC PDU is successfully decoded and the MAC PDU contains a UE contention resolution identity MAC CE that matches the CCCH SDU transmitted in Msg3 (1250), the UE can be considered to have successfully resolved the contention (1250) and the random access procedure can be considered to have been successfully completed.

[0113] FIG. 13 is an exemplary structure for MAC entities according to one aspect of one embodiment. In one example, a wireless device may be configured to operate in a multiple connection mode. A wireless device in an RRC_CONNECTED state having multiple RX / TX may be configured to use wireless resources provided by multiple schedulers located at multiple base stations. Multiple base stations may be connected via an Xn interface through a non-ideal or ideal backhaul. In one example, a base station within the multiple base stations may operate as a master base station or a secondary base station. The wireless device may be connected to one master base station and one or more secondary base stations. Multiple MAC entities may be configured on the wireless device, for example, one MAC entity for the master base station and one or more other MAC entities for the secondary base station(s). In one example, a configured set of serving cells for the wireless device may include two subsets: an MCG comprising serving cells of the master base station and one or more SCGs comprising serving cells of the secondary base station(s). FIG. 13 illustrates an exemplary structure for a MAC entity when the MCG and SCG are configured for a wireless device.

[0114] In one example, at least one cell within the SCG may have a configured UL CC, wherein the cell of at least one cell may be referred to as the PSCell or PCell of the SCG, or sometimes simply as the PCell. PUCCH resources may be configured in the PSCell. In one example, when the SCG is configured, there may be at least one SCG bearer or one split bearer. In one example, upon detection of a physical layer problem or random access problem on the PSCell, or upon reaching multiple RLC retransmissions associated with the SCG, or upon detection of an access problem on the PSCell during SCG addition or SCG change: the RRC access re-establishment procedure may not be triggered, UL transmission to the cells of the SCG may be stopped, the master base station may be notified of the SCG failure type by the UE, and DL data transmission through the master base station may be maintained.

[0115] In one example, the MAC sublayer may provide services such as data transmission and wireless resource allocation to upper layers (e.g., 1310 or 1320). The MAC sublayer may include multiple MAC entities (e.g., 1350 and 1360). The MAC sublayer may provide data transmission services over a logical channel. Multiple types of logical channels may be defined to accommodate different types of data transmission services. A logical channel may support the transmission of a specific type of information. Logical channel types may be defined according to what type of information (e.g., control or data) is transmitted. For example, BCCH, PCCH, CCCH, and DCCH may be control channels, and DTCH may be a traffic channel. In one example, the first MAC entity (e.g., 1310) may provide services to PCCH, BCCH, CCCH, DCCH, DTCH, and MAC control elements. In one example, a second MAC entity (e.g., 1320) can provide services to BCCH, DCCH, DTCH, and MAC control elements.

[0116] The MAC sublayer may anticipate physical layer services (e.g., 1330 or 1340), such as data transmission services, HARQ feedback signaling, scheduling requests, or measurement (e.g., CQI) signaling. In one example, in a duplex connection, two MAC entities may be configured for a wireless device, one for the MCG and one for the SCG. The MAC entities of the wireless device may handle multiple transmission channels. In one example, the first MAC entity may handle a first transmission channel comprising the PCCH of the MCG, the 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 one example, the second MAC entity can handle a second transmission channel comprising 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.

[0117] In one example, if one or more SCells are configured in a MAC entity, multiple DL-SCHs may exist, and multiple RACHs as well as multiple UL-SCHs may exist for each MAC entity. In one example, one DL-SCH and one UL-SCH may exist on an SpCell. In one example, for a SCell, one DL-SCH, or zero or one UL-SCH, and zero or one RACH may exist. A DL-SCH may support reception using different numerologies and / or TTI durations within a MAC entity. Additionally, a UL-SCH may support transmission using different numerologies and / or TTI durations within a MAC entity.

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

[0119] FIG. 14 is an exemplary diagram of a RAN architecture including one or more base stations. In one example, protocol stacks (e.g., RRC, SDAP, PDCP, RLC, MAC, and PHY) may be supported at the nodes. 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-DU (1430A, 1430B, 1430C, 1430D)), where a functional split 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 within the base station DU. An F1 interface connecting the base station CU and the base station DU (e.g., a CU-DU interface) may be an ideal or ideal backhaul. F1-C can provide control plane connectivity through the F1 interface, and F1-U can provide user plane connectivity through the F1 interface. In one example, the Xn interface can be configured between base station CUs.

[0120] In one example, the base station CU may include RRC functions, SDAP layers, and PDCP layers, and the base station DU may include RLC layers, MAC layers, and PHY layers. In one example, various functional partitioning options between the base station CU and the base station DU may be possible by locating different combinations of upper protocol layers (RAN functions) within the base station CU and lower protocol layers (RAN functions) within the base station DU. Functional partitioning can support the flexibility to move protocol layers between the base station CU and the base station DU depending on service requirements and / or network environments.

[0121] In one example, the functional splitting option may be configured per base station, per base station CU, per base station DU, per UE, per bearer, per slice, or other granularities. In each base station CU split, the base station CU may have a fixed splitting option, and the base station DU may be configured to match the splitting option of the base station CU. In each base station DU split, different splitting options may be configured in the base station DU, and the base station CU may provide different splitting options for different base station DUs. In each UE split, the base station (base station CU and at least one base station DU) may provide different splitting options for different radio devices. In each bearer split, different splitting options may be available for different bearers. In each slice splice, different splitting options may be applied to different slices.

[0122] FIG. 15 is an example diagram illustrating an RRC state transition of a wireless device. In one example, the wireless device may be in at least one RRC state among 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 one 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) that can have UE status information of the wireless device. UE context information (e.g., wireless device context information) may include access layer context information, one or more wireless link configuration parameters, bearer configuration information (e.g., data radio bearer (DRB), signaling radio bearer (SRB), logical channel, QoS flow, PDU session, and / or others), security information, PHY / MAC / RLC / PDCP / SDAP layer configuration information, and / or similar configuration information for the wireless device. In one example, in an RRC idle state, the wireless device may not have an RRC connection with the base station, and the wireless device's UE context information may not be stored at the base station. In one example, in an RRC inactive state, the wireless device may not have an RRC connection with the base station. The wireless device's UE context information may be stored at a base station that may be called an anchor base station (e.g., end-serving base station).

[0123] In one example, the wireless device may switch the UE RRC state in two ways between the RRC idle state and the RRC connected state (e.g., disconnect (1540) or establish connection (1550) or re-establish connection) and / or in two ways between the RRC inactive state and the RRC connected state (e.g., disable connection (1570) or resume connection (1580)). In one example, the wireless device may switch its RRC state from the RRC inactive state to the RRC idle state (e.g., disconnect (1560)).

[0124] In one example, the anchor base station may be a base station capable of maintaining the wireless device's UE status information (wireless device status information) during the time period when the wireless device remains in the anchor base station's RAN notification area (RNA) and / or when the wireless device remains in an RRC inactive state. In one example, the anchor base station may be the base station where the wireless device in an RRC inactive state was last connected in the latest RRC connection state or where the wireless device last performed the RNA update procedure. In one example, the RNA may include one or more cells operated by one or more base stations. In one example, a base station may belong to one or more RNAs. In one example, a cell may belong to one or more RNAs.

[0125] In one example, the wireless device can switch the UE RRC state at the base station from an RRC connected state to an RRC inactive state. The wireless device can 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, the IP address of the base station, an AS status information identifier of the wireless device, a resumption identifier, and / or other such identifiers.

[0126] In one example, an anchor base station may broadcast a message (e.g., a RAN paging message) to base stations of RNA to reach radio devices in an RRC-inactive state, and / or base stations capable of receiving a message from the anchor base station may broadcast and / or multicast other messages (e.g., paging messages) to radio devices within their coverage area, cell coverage area, and / or beam coverage area associated with RNA via an air interface.

[0127] In one example, when a radio device in an RRC-inactive state moves to a new RNA, the radio device may perform an RNA update (RNAU) procedure that may include a random access procedure and / or a UE situation information retrieval procedure by the radio device. UE situation information retrieval may include receiving a random access preamble from the radio device by the base station; and fetching the radio device's UE situation information from the old anchor base station by the base station. Fetching may include transmitting a retrieval UE situation information request message containing a resumption identifier to the old anchor base station, and receiving a retrieval UE situation information response message containing the radio device's UE situation information from the old anchor base station.

[0128] In an exemplary embodiment, a wireless device in an RRC-inactive state may select a cell to camp on based on at least one measurement result for a cell, where the wireless device can monitor RNA paging messages and / or core network paging messages from a base station. In one example, the wireless device in an RRC-inactive state may select a cell to perform a random access procedure to resume the RRC connection or to transmit one or more packets to a base station (e.g., a network). In one example, if the selected cell belongs to an RNA different from the RNA for the wireless device in an RRC-inactive state, the wireless device may initiate a random access procedure to perform an RNA update procedure. In one example, if the wireless device in an RRC-inactive state transmits one or more packets to a network in a buffer, the wireless device may initiate a random access procedure to transmit one or more packets to the base station of the cell selected by the wireless device. The random access procedure may be performed with two messages (e.g., two-stage random access) and / or four messages (e.g., four-stage random access) between the wireless device and the base station.

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

[0130] In existing technology, the IAB donor possesses RRC capabilities to provide services to wireless devices. Wireless devices may experience RRC connectivity failures when a backhaul link failure occurs between the serving IAB node and the serving IAB donor. In implementations of existing technology, when a base station receives a report from a wireless device regarding an RRC connectivity failure caused by a backhaul link failure, it may misinterpret the RRC connectivity failure as an access link issue between the wireless device and the IAB node. Implementing existing technology can lead to an increase in improper wireless parameter configurations when the IAB node backhaul link is in a failure state. Existing technology can degrade the reliability of wireless access for wireless devices.

[0131] An exemplary embodiment supports a wireless link failure reporting mechanism that provides backhaul link information of a wireless device. An exemplary embodiment may support wireless communication parameters configured based on status information of the wireless backhaul link. Implementation of the exemplary embodiment may increase the communication reliability and mobility performance of the wireless device.

[0132] In one 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, and / or the like. In one 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, and / or the like. In one example, a wireless device may be interpreted as a user device (UE), an IAB node, an IAB donor, a relay node, a base station, a gNB, and / or the like.

[0133] In one example, the Integrated Access and Backhaul (IAB) may support wireless backhaul connections for access network nodes (e.g., distributed unit, gNB-DU, base station, gNB, IAB node, relay node, mobile relay node, RAN node, and / or etc.). In one example, the IAB node may represent a RAN node capable of supporting wireless access and / or wireless backhaul access traffic to the UE. In one example, the IAB donor may represent a RAN node capable of providing the UE's interface to the core network and / or wireless backhauling capabilities to the IAB node.

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

[0135] In an exemplary IAB deployment, in-band and / or out-of-band backhauling for the access link may be supported. In-band backhauling may include scenarios where the access and backhaul links may overlap at least partially at frequencies that cause half-duplexing constraints or interference constraints. Half-duplexing constraints and / or interference constraints of in-band backhauling may mean that an IAB node cannot transmit and receive simultaneously on both links. In one example, the out-of-band scenario may not impose half-duplexing constraints and / or interference constraints. In an in-band backhaul deployment, close interaction between the access and backhaul may be required to comply with half-duplexing constraints and interference constraints.

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

[0137] In one example, the IAB can support access and backhaul for frequency bands (spectrum) above and / or below 6 GHz. Backhauling of access traffic through the same RAT backhaul link can be supported. Inter-RAT operation for backhauling and access can be supported.

[0138] The UE can connect transparently to the IAB node through the same RAT. An IAB architecture required for accessing the first RAT through the second RAT backhaul can be supported.

[0139] In one example, the IAB can support standalone (SA) and / or non-standalone (NSA) deployments. For NSA, IAB-based relay of the UE's secondary cell group (SCG) path can be supported. IAB-based relay of the UE's master cell group (MCG) path is supported.

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

[0141] In one example, SA and / or NSA may be supported for the access link. For the NSA access link, relaying may be applied to the RAN node. In one example, both NSA and SA may be supported for the backhaul link. Backhaul traffic through the wireless interface may be supported. In one example, EN-DC may be supported for the NSA access and backhaul links.

[0142] In one example, multi-hop backhauling can provide a greater range extension than a single hop. For frequencies above 6 GHz, multi-hop backhauling can be beneficial due to the limited range of these frequencies. Multi-hop backhauling can enable backhauling for non-congested deployments around obstacles, for example, around buildings in urban environments. In one example, the number of hops within an IAB deployment can be expected to vary depending on many factors, such as frequency, cell density, propagation environment, and / or traffic load. These factors can be expected to change over time. From an architectural perspective, flexibility in hop counting may be desirable.

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

[0144] In one example, a wireless backhaul link may be vulnerable to blockage caused by moving objects, such as vehicles, seasonal changes (leafing), and / or changes in infrastructure (e.g., new buildings). The vulnerability of a wireless backhaul link can apply to physically fixed IAB nodes. In one example, traffic fluctuations can cause uneven load distribution on the wireless backhaul link, leading to local link and / or node congestion.

[0145] In one example, terrain adaptation (e.g., adaptive routing) may refer to a procedure for autonomously reconfiguring a backhaul network without interrupting service to the UE in situations such as failures and / or local congestion. In one example, terrain adaptation for physically fixed relays may be supported to enable robust operation, for example, to mitigate failures and / or load fluctuations on backhaul links.

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

[0147] In one example, IAB-related functions, such as IAB node integration and / or terrain adaptation, can affect core network operations. In one example, IAB functions can cause additional core network signaling load. The amount of signaling load on core network nodes may vary among different designs of the IAB architecture.

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

[0149] In one example, the IAB architecture may include mobile-termination (MT), gNB-DU, gNB-CU, UPF, AMF, and SMF, as well as the 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. The MT (Mobile-termination) function may be defined as a component of mobile equipment (e.g., User Equipment (UE)). In one example, MT may be referred to as a function in an IAB node that terminates the radio interface layers of the backhaul Uu interfaces for IAB donors and / or other IAB nodes.

[0150] FIG. 16 shows an exemplary diagram of an IAB in self-supporting mode that may include a single IAB donor and multiple IAB nodes. The IAB donor may be treated as a single logical node that may include a set of functions such as gNB-DU, gNB-CU-CP, gNB-CU-UP, and / or other potential functions. In a given configuration, the IAB donor may be partitioned according to these functions and may be co-located and / or not co-located. The IAB architecture may operate with the partitioning of these functions. In one example, some functions associated with the IAB donor may be moved outside the donor in some cases.

[0151] In one example, an IAB node may operate in SA mode and / or NSA mode. When an IAB node operates in NSA mode, it may use a different link for backhauling. In one example, a UE connecting to an IAB node may select a different operating mode than the IAB node. The UE may be connected to a different type of core network than the IAB node to which it is connected. In this case, (e)Decor or slicing may be used for core network selection. IAB nodes operating in NSA mode may be connected to the same or different base stations (e.g., gNB, eNB). UEs operating in NSA nodes may be connected to the same or different base stations as the IAB node to which they are connected. Figure 17 shows examples of SA mode and NSA mode with core network(s).

[0152] In one example, the IAB multi-hop design may differ in terms of modifications required for the interface and / or additional features required, for example, for multi-hop forwarding. Exemplary architectures can be divided into two groups of architectures.

[0153] In one example, Architecture Group 1 may include Architecture 1a and / or 1b. Architecture 1a and / or 1b may utilize a CU / DU partitioning architecture. Architecture 1a may include backhauling of F1-U using an adaptation layer and / or GTP-U combined with an adaptation layer. Architecture 1a may use hop-by-hop forwarding across intermediate nodes using an adaptation layer for operation with the core network and / or PDN-link-layer routing for operation with other core networks (e.g., other RATs, EPCs). In one example, Architecture 1b may include backhauling of F1-U at access nodes using GTP-U / UDP / IP. Architecture 1b may use hop-by-hop forwarding across intermediate nodes using an adaptation layer.

[0154] In one example, Architecture Group 2 may include Architectures 2a, 2b, and / or 2c. Architecture 2a may include backhauling of F1-U or NG-U at access nodes using GTP-U / UDP / IP. Architecture 2a may use hop-by-hop forwarding across intermediate nodes using PDU session layer routing. Architecture 2b may include backhauling of F1-U or NG-U at access nodes using GTP-U / UDP / IP. Architecture 2b may use hop-by-hop forwarding across intermediate nodes using GTP-U / UDP / IP nested tunneling. Architecture 2c may include backhauling of F1-U or NG-U at access nodes using GTP-U / UDP / IP. Architecture 2c may use hop-by-hop forwarding across intermediate nodes using GTP-U / UDP / IP / PDCP nested tunneling.

[0155] In one example, Architecture 1a may utilize a CU / DU partitioned architecture. Fig. 18 shows an exemplary diagram of a 2-hop chain of IAB nodes under an IAB donor, 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. The IAB node may be connected to an upstream IAB node and / or IAB donor via the MT. The IAB node may establish an RLC channel to the UE and / or to the MT of the downstream IAB node via the DU. In the case of 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.

[0156] In the example of Architecture 1a, the donor (IAB donor) may hold DUs to support UEs and / or MTs of downstream IAB nodes. The IAB donor may hold CUs for the IAB nodes' DUs and / or its own DUs. Different CUs may serve as the DUs for the IAB nodes. The DUs of the IAB nodes may be connected to the IAB donor's CUs using a modified form of F1 called F1*. F1*-U may be executed over an RLC channel in the wireless backhaul between the MT on the serving IAB node and the DU on the donor. F1*-U transmission may be configured between the MT and DU on the serving IAB node and / or between the DU and CU on the donor. In one example, an adaptation layer capable of holding routing information may be added to enable hop-by-hop forwarding. The adaptation layer may replace the IP functions of the F1 stack. F1*-U can return a GTP-U header for end-to-end coupling between CU and DU. In one example, the information returned via the GTP-U header may be included in the adaptation layer.

[0157] In the example of Architecture 1a, RLC can apply ARQ to end-to-end connections and / or per hop. Figure 18 shows an example of the F1*-U protocol stack. RLC* may refer to an enhancement of RLC. The MT of the IAB node can maintain a NAS connection to a core network (e.g., AMF, SMF, MME, and / or other core networks) for, for example, to authenticate the IAB node. The MT of the IAB node can maintain a PDU session through a core network node (e.g., UPF, SGW, PGW, and / or other core network nodes) to, for example, provide the IAB node with a connection to Operations and Management (OAM). In one example, for NSA operation with the 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 core network to, for example, provide the IAB node with a connection to the OAM. If the IAB donor is split, protocol conversion between F1* and F1 can be supported.

[0158] In one example, Architecture 1b may utilize a CU / DU partitioned architecture. Fig. 19 shows an exemplary diagram of a 2-hop chain of IAB nodes under an IAB donor. An IAB donor may hold one logical CU. An IAB node may be connected to more than one upstream IAB node and / or IAB donor. In the example of Architecture 1b, the IAB node and / or IAB donor may have the same functions as in Architecture 1a. In one 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*.

[0159] In the example of Architecture 1b, the MT of the IAB node can establish a PDU session with the UPF in the donor (IAB donor). The MT's PDU session can return F1* for the co-located DU. In one example, the PDU session can provide a point-to-point link between the CU and the DU. At an intermediate hop, the PDCP-PDU of F1* can be forwarded through the adaptation layer. Figure 19 shows an example of the F1*-U protocol stack. For NSA operation with the core network, the MT can be duplex-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) in the donor.

[0160] Figure 20 shows an exemplary diagram of Architecture 2a, in which UE and / or IAB nodes can use SA- mode with the core network. In the example of Architecture 2a, the IAB node may possess an MT to establish a Uu link with a gNB (base station) on the parent IAB node and / or IAB donor. Through the Uu link, the MT can maintain a PDU session with a UPF that can be co-located with the gNB. Independent PDU sessions can be created on backhaul links (e.g., per hop). The IAB node may support a routing function that forwards data between PDU sessions on adjacent links. The routing function may create a forwarding plane across the wireless backhaul. The forwarding plane may support IP and / or Ethernet based on the PDU session type. If the PDU session type is Ethernet, an IP layer may be established on top. The IAB node may secure an IP connection to the wired backhaul network. An IAB node can be connected to one or more upstream IAB nodes and / or IAB donors.

[0161] In the example of Architecture 2a, IP-based interfaces (e.g., NG, Xn, F1, N4, etc.) can be returned via the forwarding plane. For F1, the UE-serving IAB node may include a DU for the access link in addition to a gNB and / or UPF for the backhaul link. The CU for the access link may be located within or beyond the IAB donor. Figure 20 shows an example of the NG-U protocol stack for IP-based and / or Ethernet-based PDU session types. If the IAB node holds a DU for UE access, end-user data can be protected using end-to-end PDCP between the UE and the CU, so PDCP-based protection for the hops may not be required. For NSA operation with the core network, the MT may be duplex-connected to the network (e.g., gNB, eNB, RNC, core network). The MT of the IAB node may maintain PDN connections with the L-GW in the parent IAB node and / or IAB donor. IP-based interfaces (e.g., NG, Xn, S1, S5, X2, etc.) can be returned through the forwarding plane.

[0162] In the example of Architecture 2b, as illustrated in FIG. 21, the IAB node may possess an MT to establish a Uu link with a gNB (base station) on the parent IAB node and / or IAB donor. Through the Uu link, the MT may maintain a PDU session with a UPF. The UPF may be located on the IAB donor. PDU forwarding across upstream IAB nodes can be achieved through tunneling. Forwarding across multiple hops can create a stack of nested tunnels. The IAB node may secure an IP connection to the wired backhaul network. IP-based interfaces (e.g., NG, Xn, F1, N4, etc.) can be routed through the forwarding IP plane. FIG. 21 shows an example of a protocol stack for NG-U (e.g., S1-U). The IAB node may be connected to more than one upstream IAB node and / or IAB donor. For NSA operation with the 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 in the IAB donor.

[0163] In one example, as illustrated in FIG. 22, architecture 2c can utilize DU-CU splitting. An IAB node may possess an MT capable of maintaining an RLC channel to a DU on a parent IAB node and / or an IAB donor. An IAB donor may possess a CU and / or UPF for the DU of the IAB node. The MT of the IAB node may maintain a PDU session to a Uu link with the CU and / or a UPF on the donor (IAB donor). Forwarding across intermediate nodes can be achieved through tunneling. Forwarding across multiple hops can create a stack of nested tunnels. An IAB node can secure an IP connection to a wired backhaul network. The tunnel may include an SDAP / PDCP layer. IP-based interfaces (e.g., NG, Xn, F1, N4, etc.) can be returned through the forwarding plane. Figure 22 shows an example of a protocol stack for NG-U (e.g., S1-U). An IAB node may be connected to one or more upstream IAB nodes and / or IAB donors. For NSA operation with the core network, the MT may be dual-connected to the network (e.g., gNB, eNB, RNC, core network). The MT of the IAB node may maintain a PDN connection with the L-GW in the IAB donor.

[0164] In one example, an IAB node may follow the same initial access procedure as a UE (e.g., a wireless device), including cell discovery, acquisition of system information (SI), and / or random access, to initially establish a connection to a parent IAB node and / or an IAB donor. SSB / CSI-RS-based RRM measurements may be supported for IAB node discovery and / or measurements. In one example, an inter-IAB node discovery procedure involving half-repeated constraints and / or multiple hop terrain may be supported, including methods to prevent SSB configurations from conflicting between IAB nodes and / or the feasibility of CSI-RS-based IAB node discovery. Given the cell ID used by a given IAB node, the IAB donor and the IAB node may share the same cell ID and / or maintain separate cell IDs. The feasibility of the IAB donor and the IAB node sharing the same cell ID may depend on the IAB architecture. A mechanism for multiplexing RACH transmissions from the UE and RACH transmissions from the IAB node may be supported.

[0165] In one example, measurements for multiple backhaul links for link management and / or path selection may be supported. To support half-replication constraints at the IAB node, the IAB may support the detection and / or measurement of candidate backhaul links—which may utilize resources temporally orthogonal to the resources used by the access UE for cell detection and / or measurement—(e.g., after initial access). To support the measurement, the IAB may support at least one of the following: TDM of the SSB (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 search signals that may be TDM using off-raster SSBs and SSB transmission (e.g., CSI-RS); transmission periodicity for backhaul link detection and / or measurement that is different from the periodicity used by the access UEs; and / or other. Coordination mechanisms for various solutions may be supported, including mechanisms for coordinating reference signal (RS) transmission and / or measurement situations for IAB nodes. Enhancements to the SMTC and / or CSI-RS configurations to support RRM measurements for IAB nodes may be considered.

[0166] In one example, the IAB node may support a mechanism for detecting / recovering backhaul link failures. Enhancements to the RLM RS and / or related procedures for the IAB may be supported.

[0167] In one example, a mechanism for simultaneous path switching and / or transmission / reception over multiple backhaul links (e.g., multiple TRP operation and / or intra-frequency duplexing) may be supported. The feasibility of such a mechanism may vary depending on the IAB architecture.

[0168] In one example, downlink IAB node transfers (e.g., transfers on backhaul links from an IAB node to a child IAB node serviced by the IAB node, and transfers on access links from an IAB node to a UE serviced by the IAB node) may be scheduled by the IAB node. In one example, uplink IAB transfers (e.g., transfers on backhaul links from an IAB node to its parent IAB node and / or IAB donor) may be scheduled by the parent IAB node or the IAB donor.

[0169] In one example, the IAB may support Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), and / or Spatial Division Multiplexing (SDM) between the access link and the backhaul link at the IAB node, for example, subject to half-double constraints. Mechanisms for TDM / FDM / SDM multiplexing of access / backhaul traffic across multiple hops may account for IAB node half-double constraints. In one example, the IAB may support mechanisms for orthogonal partitioning of time slots and / or frequency resources between the access link and the backhaul link across one or more hops. The IAB may provide the utilization of different DL / UL slot configurations for the access link and the backhaul link. The IAB may allow intra-panel FDM and / or SDM of the backhaul link and the access link by supporting DL and / or UL output control enhancements and / or timing requirements. In one example, the IAB may provide interference management, including cross-link interference.

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

[0171] In one example, over-the-air (OTA) synchronization may be configured for the IAB. In one example, the IAB may support a mechanism for coordinating the timing alignment of IAB nodes. The IAB may support the detection and management of timing misalignment (e.g., depending on the number of hops). In one example, the IAB may implement a mechanism for timing alignment across multi-hop IAB networks. The IAB may support TA-based synchronization between IAB nodes, including that occurring across multiple backhaul hops. In one example, the IAB may support the following 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 an IAB node; DL and UL reception timing aligned within an IAB node; timing alignment within an IAB node when transmitting and receiving DL and UL; DL transmission timing alignment across IAB nodes and / or IAB donors for access links; and / or timing alignment within IAB nodes when transmitting and receiving DL and UL for backhaul link timing in different time slots.

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

[0173] In one example, by providing an interference measurement and management mechanism, the IAB can control cross-link interference (CLI) occurring on access links and backhaul links (including those occurring across multiple hops).

[0174] In one example, IAB CLI mitigation technology can support advanced receiver and transmitter coordination. CLI mitigation technology can support interference mitigation mechanisms for inter-IAB node interference scenarios, e.g., a scenario where a victim IAB node receives from the DL via its MT and an interfering IAB node transmits from the UL via its MT; a scenario where a victim IAB node receives from the DL via its MT and an interfering IAB node transmits from the DL via its DU; a scenario where a victim IAB node receives from the UL via its DU and an interfering IAB node transmits from the UL via its MT; and / or a scenario where a victim IAB node receives from the UL via its DU and an interfering IAB node transmits from the DL via its DU. The IAB can implement a mechanism to resolve interference experienced at the IAB node when there is FDM / SDM reception between the access link and the backhaul link at the IAB node. In one example, the IAB can support CLI measurements, e.g., short-term / long-term measurements, and / or multi-antenna and beamforming-based measurements, and can support CLI relaxation at IAB nodes and / or IAB donors.

[0175] IAB can support wireless backhaul links with high frequency band efficiency. In one example, IAB can support 1024QAM for backhaul links.

[0176] In one example, the UE can establish an RLC channel to a DU on the UE's access IAB node. The RLC channel can be extended between the UE's access DU and the IAB donor through a modified form of F1-U called F1*-U. Information embedded in the F1*-U can be returned via RLC channels across backhaul links. The transmission of F1*-U over the wireless backhaul can be enabled by an adaptation layer that can be integrated with the RLC channel. The IAB donor (referred to as the fronthaul) can use an F1-U stack. The IAB donor DU can relay between the F1-U on the fronthaul and / or the F1*-U on the wireless backhaul.

[0177] In the example of Architecture 1a, the information returned on the adaptation layer supports one or more of the following functions: UE bearer identification for PDUs, routing across wireless backhaul terrain, QoS enforcement by a scheduler on the DL and a UL on the wireless backhaul link, mapping UE user plane PDUs to backhaul RLC channels, and / or etc.

[0178] In the example of architecture 1b, the information returned on the adaptation layer supports one or more of the following functions: routing across the wireless backhaul terrain, QoS enforcement by the scheduler on the DL and the UL on the wireless backhaul link, mapping UE user plane PDUs to backhaul RLC channels, and / or etc.

[0179] In one example, information returned through the adaptation layer header may include one or more of a UE bearer-specific ID, a UE-specific ID, a route ID, an IAB node, an IAB donor address, QoS information, and / or the like.

[0180] In one example, information on the adaptation layer is processed to support adaptation layer functions on IAB nodes on the path (e.g., per hop) and / or UE's access IAB nodes and IAB donors (e.g., end-to-end).

[0181] In one example, the adaptation layer may be integrated with the MAC layer or integrated on top of the MAC layer, as shown in FIG. 23 (e.g., a, b). In one example, the adaptation layer may be integrated with the RLC layer or integrated on top of the RLC layer, as shown in FIG. 23 (e.g., c, d, e) and / or FIG. 24.

[0182] In one example, FIG. 23 and / or FIG. 24 shows an exemplary protocol stack. The RLC channel for backhauling includes an adaptation layer, but the adaptation layer may be included in the IAB node access link.

[0183] In one example, the adaptation layer may include lower layers. The GTP-U header may be part of the adaptation layer. In one example, the GTP-U header may be returned from the top of the adaptation layer to return the end-to-end coupling between the IAB node DU and CU (see, for example, as illustrated in FIG. 23d).

[0184] In one example, the IP header may be part of the adaptation layer and / or may be returned from above the adaptation layer (see, for example, as illustrated in FIG. 23e). In one example, the IAB donor DU may possess an IP routing function to extend the IP routing plane of the fronthall to the IP layer returned by the adaptation in the wireless backhall. This allows native F1-U to be established end-to-end, for example, between the IAB node DU and the IAB donor CU-UP. The IAB node may possess an IP address that can be routed from the fronthall via the IAB donor DU. The IP address of the IAB node may be used for routing on the wireless backhall. The IP layer above the adaptation may not represent a PDU session. The first-hop router of the MT on the IP layer may not possess a UPF.

[0185] In one example, the upper RLC adaptation layer can support per-hop ARQ. The upper MAC adaptation layer can support both per-hop and end-to-end ARQ. In one example, the arrangement of the two adaptation layers can support aggregated routing, for example, by inserting IAB node addresses into the adaptation header. In one example, the arrangement of the two adaptation layers can support per-UE bearer QoS for multiple UE bearers. In one example, for the upper RLC adaptation layer, the LCID space can be improved because UE bearers can be mapped to independent logical channels. In one example, for the upper MAC adaptation layer, UE bearer-related information can be returned on the adaptation header. In one example, the arrangement of the two adaptation layers can support aggregated QoS processing, for example, by inserting aggregated QoS IDs into the adaptation header. In one example, aggregated QoS processing can reduce the number of queues. Aggregated QoS processing may be independent of the arrangement of the adaptation layers. In one example, where two adaptation layers are deployed, the aggregation of routing and / or QoS processing may allow for the pre-configuration of IAB nodes on intermediate paths. That is, the configuration may be independent of UE bearer enable / disable. In one example, where two adaptation layers are deployed, RLC ARQ may be pre-processed on the TX side.

[0186] In one example, for RLC AM, ARQ can be performed hop-by-hop along access links and backhaul links. ARQ can be supported end-to-end between the UE and the IAB donor. RLC segmentation can be a just-in-time process and / or can be performed hop-by-hop.

[0187] A certain type of multi-hop RLC ARQ and adaptation layer placement may have interdependencies: that is, for end-to-end ARQ, the adaptation layer may be integrated with the MAC layer or placed on top of the MAC layer; and / or per-hop ARQ may or may not have interdependencies.

[0188] In one example, different IAB architecture options can affect scheduling and / or QoS in the direction of downlink and / or uplink. In one example, the adaptation layer can be placed on top of the RLC and / or MAC.

[0189] In one example, control plane (CP) signaling across a wireless backhaul link may use the same routing and / or QoS enforcement mechanisms as for user plane (UP) traffic. The priority and / or QoS requirements for CP signaling may differ from those for UP traffic.

[0190] In one example, signaling between the MT on the IAB node and the central unit control plane (CU-CP) on the IAB donor may use the RRC protocol. Signaling between the DU on the IAB node and the CU-CP on the IAB donor may use the F1-AP protocol. IAB-specific enhancements for RRC and F1-AP may be supported.

[0191] In one example, the RRC and F1-AP connections may be protected via a wireless backhaul link. The RRC connection may provide protection over the wireless backhaul link at least at the same level as protection over the access link. In one example, the F1-AP connection may provide protection over the wireless backhaul link at at least at the same level as the RRC connection. In one example, protection for the F1-AP at the same level as protection for the RRC may be supported.

[0192] In one 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 can be supported based on the use of NDS.

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

[0194] In one example, in Alternative 1 of Architecture 1a, FIG. 25 illustrates the protocol stack for the UE's RRC, the MT's RRC, and / or the DU's F1-AP. In one example, an adaptation layer may be placed on top of the RLC. The access link of the IAB node may or may not include an adaptation layer. In the example of Alternative 1 of Architecture 1a, the RRC of the UE and / or MT may be carried through the SRB. In the access link of the UE and / or MT, the SRB may use an RLC channel. In the radio backhaul link, the PDCP layer of the SRB may be carried through the RLC channels containing the adaptation layer. Placing the adaptation layer within the RLC channel may be the same for the C plane as for the U plane. The information carried by the adaptation layer may differ in the case of a signaling radio bearer (SRB) as in the case of a data radio bearer (DRB). The DU's F1-AP can be encapsulated in the co-deployed MT's RRC. The F1-AP can be protected by the PDCP of the underlying SRB. The IAB donor can use the native F1-C stack.

[0195] In one example, in Alternative 2 of Architecture 1a, FIG. 26 illustrates the protocol stack for the UE's RRC, the MT's RRC, and / or the DU's F1-AP. In one example, an adaptation layer may be located on top of the RLC. The access link of the IAB node may or may not include an adaptation layer. In the example of Alternative 2 of Architecture 1a, the RRC of the UE and / or MT may be returned via an SRB. In the access link of the UE and / or MT, the SRB may use an RLC channel. In the wireless backhaul link, the PDCP of the RRC's SRB may be encapsulated into the F1-AP. The DU's F1-AP may be returned via the co-located MT's SRB. The F1-AP may be protected by the PDCP of this SRB. In the wireless backhaul link, the PDCP layer of the F1-AP's SRB may be returned via RLC channels containing the adaptation layer. Placing the adaptation layer within the RLC channel can be the same for the C plane as it is for the U plane. The information returned by the adaptation layer may differ in the case of an SRB compared to a DRB. The IAB donor can use the native F1-C stack.

[0196] In one example, for Alternative 3 of Architecture 1a, FIG. 27 illustrates the protocol stack for the UE's RRC, the MT's RRC, and / or the DU's F1-AP. In one example, the adaptation layer may be located on top of the RLC. The access link of the IAB node may or may not include an adaptation layer. In the example of Alternative 3 of Architecture 1a, the RRC of the UE and / or MT may be returned via an SRB. In the access link of the UE and / or MT, the SRB of the RRC may use an RLC channel. In the wireless backhaul link, the PDCP layer of the SRB may be returned via RLC channels containing the adaptation layer. Placing the adaptation layer within the RLC channel may be the same for the C plane as for the U plane. The information returned from the adaptation layer may differ in the case of the SRB compared to the case of the DRB. The DU's F1-AP may be returned via the co-located MT's SRB. The F1-AP can be protected by this SRB's PDCP. In the wireless backhaul link, the SRB's PDCP can be carried over RLC channels with an adaptation layer. The IAB donor can use the native F1-C stack.

[0197] In one example, in Alternative 4 of Architecture 1a, FIG. 28 illustrates the protocol stack for the UE's RRC, the MT's RRC, and / or the DU's F1-AP. In one example, an adaptation layer may be on top of the RLC and / or may return the IP layer. In the example of Alternative 4 of Architecture 1a, the IP layer returned by the adaptation may be connected to the IP plane of the fronthall via a routing function from the IAB donor DU. At the IP layer, IAB nodes may hold IP addresses that can be routed from the IAB donor CU-CP. The extended IP plane may enable the use of native F1-C between the IAB node DU and the IAB donor CU-CP. Signaling traffic may be prioritized using DSCP indications in the IP routing plane. F1-C may be protected via NDS, for example, via D-TLS. The RRC of the UE and / or MT can use an SRB that can be returned via F1-C.

[0198] In one example, as an alternative to Architecture 1a, FIG. 29 illustrates the protocol stack for the UE's RRC, the MT's RRC, and / or the DU's F1-AP. In one example, an adaptation layer that returns the PDCP of the DRB may be located on top of the RRC. The access link of the IAB node may or may not include an adaptation layer. In an example of an alternative to Architecture 1b, the RRC of the UE and / or MT may be returned via the SRB. In the wireless backhaul, the PDCP of the SRB may be returned via the native F1-C. The DU on the IAB node and / or IAB donor may use the native F1-C stack. Over the wireless backlink, the IP layer of the native F1-C stack may be provided by the PDU session. The PDU session may be established between the DU and the co-located MT and / or UPF. The PDU session may be returned by the DRB between the MT and the CU-UP. Between CU-UP and UPF, PDU sessions can be returned via NG-U. IP transmission between UPF and CU-CP can be provided by the DN of the PDU session. IP transmission can be protected. Protection for F1-C transmission across the DN between UPF and CU-CP can be supported.

[0199] In one example, the IAB terrain may include a spanning tree (ST) and / or a directed acyclic graph (DAG). The directionality of the Uu backhaul links, defined by uplinks and downlinks, may align with the hierarchical structure of the ST and / or DAG. In the case of an ST, an IAB node may have one parent node that can be an IAB node and / or an IAB donor. In the case of an ST, an IAB node may be connected to and / or one IAB donor at a time, or there may be one path between the IAB node and the IAB donor. In the case of a DAG, an IAB node may be multiconnected; that is, an IAB node may have links to multiple parent nodes. In the case of a DAG, an IAB node may have multiple paths to a single node, for example, a single IAB donor. In the case of a DAG, an IAB node may have redundant paths through multiple parents to a single node. In one example, multiconnection (e.g., duplex connection) and / or path redundancy may be used. For example, redundant paths can be used simultaneously to achieve load balancing, reliability, etc.

[0200] In one example, for architecture group 1, as illustrated in FIG. 30, paths for IAB nodes may be related to the following: the same IAB donor DU and the same IAB donor CU-CP and CU-UP (Fig. 30a); different IAB donor DUs and the same IAB donor CU-CP and CU-UP (Fig. 30b); different IAB donor DUs and the same IAB donor CU-UP (Fig. 30c); different IAB donor DUs, CU-CP, and CU-UP (Fig. 30d).

[0201] In one example, for architecture group 2, as illustrated in FIG. 31, the paths for the IAB nodes may be related to the same IP domain and / or different IP domains. For at least some of these terrains, IP address management and / or procedures for terrain adaptation may be supported.

[0202] In one example, the IAB node may establish an IP connection to authenticate to the operator's network and / or to reach OAM functions for OAM configuration. The authentication step may include the discovery and / or selection of a serving node, which may be an IAB donor and / or an IAB node. The IAB node may retrieve IAB information, for example, from the OAM and / or through RAN signaling such as OSI or RRC. The authentication step may include establishing a connection to a RAN node and / or a core network (CN). The authentication step may include the MT functions of the IAB node.

[0203] In one example, the DU, gNB, and / or UPF of the IAB node may be configured along with interfaces to the RAN node and / or CN. The interface configuration step may be performed before the IAB node begins to provide services to the UE and / or before the IAB node is connected. In one example, for architectures 1a and 1b, the interface configuration step may include the configuration of the IAB node's DU and / or the configuration of the IAB donor's F1 establishment to the CU-CP and / or CU-UP. In one example, for architecture 2a, the interface configuration step may include the configuration of the IAB node's gNB and / or UPF, and / or integration to the PDU session forwarding layer across the wireless backhaul. In one example, the interface configuration step may include the integration of the IAB node into terrain and / or route management.

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

[0205] In one example, the IAB architecture of the IAB donor DU and / or IAB donor CU may be based on the CU / DU architecture of the gNB (e.g., RAN). Modifications for IAB node DUs supporting F1*-U via wireless backhaul may be supported.

[0206] In one example, as illustrated in FIG. 32, an IAB node is connected to a parent node, a child node, and / or a wireless device (e.g., a UE). The IAB node may be connected to an IAB donor (e.g., the parent node of the IAB node) via a downlink parent backhaul (e.g., F1 interface, NG interface, S1 interface, Uu interface, Xn interface) and / or an uplink parent backhaul (e.g., F1 interface, NG interface, S1 interface, Uu interface, Xn interface). The IAB node may be connected to the child node of the IAB node via a downlink child backhaul (e.g., F1 interface, NG interface, S1 interface, Uu interface, Xn interface) and / or an uplink child backhaul (e.g., F1 interface, NG interface, S1 interface, Uu interface, Xn interface). The IAB node may be connected to a wireless device via downlink access (e.g., Uu interface) and / or uplink access (e.g., Uu interface).

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

[0208] In one example, a wireless device may determine an RLF when one of the following criteria is met: the expiration of a timer started after a wireless problem from the physical layer (e.g., out of sync) is indicated (if the wireless problem is resolved 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), and / or other. In one example, after an RLF is declared, the wireless device may remain in the RRC_CONNECTED state (e.g., RRC connected state); may select an appropriate cell to initiate an RRC reset; enter the RRC_IDLE state (e.g., RRC idle state) if no suitable cell is found within a specific time after the RLF is declared; or remain in the RRC_INACTIVE state (e.g., RRC inactive state) if no suitable cell is found within a specific time after the RLF is declared.

[0209] In one example, the operation of a wireless device associated with RLF may include two steps. The first step may be initiated upon detection of a wireless problem; may lead to detection of an RLF; may not initiate UE-based mobility; may be based on a timer (e.g., T1) or other criteria (e.g., counting); and / or other. The second step may be initiated upon RLF or HOF; may lead to an RRC idle state of the wireless device; may initiate UE-based mobility; may be based on a timer (e.g., T2); and / or other. In one example, a wireless device in a normal operating RRC connection state may experience the first step, which includes detection of a wireless problem and failure to recover during T1, and / or experience the second step, which includes failure to recover during T2. The second step may be followed by an RRC idle state (e.g., the wireless device may enter an RRC idle state). During normal operation, Phase 1 and / or Phase 2, the wireless device may be considered to be in an RRC connection state. In one example, RLF may be considered to occur between Phase 1 and Phase 2 (e.g., at the end time of Phase 1 and / or at the start time of Phase 2).

[0210] In one example, when a physical layer problem regarding the PCell is detected, that is, when a continuous N310 asynchronous indication is received from lower layers, the wireless device may start timer T310. When a continuous N311 synchronous indication is received from lower layers regarding the PCell, and / or when triggering a handover procedure and starting a connection re-establishment procedure, the wireless device may stop T310. In one example, when timer T310 expires, if security is not enabled, the wireless device may enter the RRC_IDLE state; and / or if security is enabled, the wireless device may start a connection re-establishment procedure.

[0211] In one example, when initiating the RRC connection re-establishment procedure, the wireless device may start timer T311. When selecting an appropriate cell of LTE / 5G / other RAT, the wireless device may stop T311. When T311 expires, the wireless device may enter the RRC_IDLE state.

[0212] In one example, a wireless device can detect a HOF that may occur due to a handover that is too early, a handover that is too late, a handover to the wrong cell, and / or the like. If the handover is too early, a wireless link failure may occur immediately after the handover from the source cell to the target cell is successful, or a handover failure may occur during the handover procedure. If the handover is too early, the wireless device may attempt to re-establish a wireless link connection from the source cell. If the handover is too late, a wireless link failure may occur after the wireless device has remained in the cell for an extended period (for example, a wireless link failure may occur because the service base station may not initiate a handover for the wireless device when the wireless link quality in the current cell is insufficient to service the wireless device); and / or the wireless device may attempt to re-establish a wireless link connection in another cell. If the handover is to the wrong cell, a wireless link failure may occur immediately after the handover from the source cell to the target cell is successful, or a handover failure may occur during the handover procedure. In the event of a handover to the wrong cell, the UE may attempt to re-establish a wireless link connection in a cell other than the source and target cells. In one example, "successful handover" may refer to the successful completion of a random access (RA) procedure by a wireless device.

[0213] In one example, to resolve a connection failure problem (e.g., RLF and / or HOF), a wireless device and / or network (e.g., base station, base station CU, base station DU, gNB, eNB, core network, and / or etc.) may trigger one or more of the following functions: detecting a connection failure after attempting to re-establish RRC; detecting a connection failure after establishing an RRC connection; retrieving information necessary for problem analysis; and / or other. The triggering of each of the above functions may be optional and / or may vary depending on the situation and / or implementation.

[0214] In an exemplary embodiment, a wireless device may receive service through an intermediate network node (e.g., Integrated Access and Backhaul (IAB) node, IAB donor, base station, gNB, base station distributed unit (gNB-DU), relay node) that can be connected to a wireless access network (e.g., gNB, gNB-CU, IAB donor, eNB, base station, RAN node) via a wireless backhaul link. The wireless access network connected to the intermediate network node may be wired to a core network node (e.g., AMF, SMF, UPF, MME, SGW, PGW). The wireless device may receive service from the wireless access network and / or the core network node through the intermediate network node. When service is provided to the wireless device through the intermediate network node, the link quality of the wireless backhaul link of the intermediate network node may affect the provision of service to the wireless device. In one example, a failure / failure / problem with the wireless backhaul link may cause a disability in packet transmission and / or service provision to the wireless device. In one example, a failure or problem with a wireless backhaul link can cause connection failures (e.g., wireless link failures or handover failures) in wireless devices. The implementation of existing communication mechanisms for reporting Wireless Link Failures (RLF) can lead to inefficient operation in configuring wireless resource configuration parameters depending on the state of the wireless backhaul link. Existing technologies can increase connection delays and packet transmission delays in wireless devices due to improper wireless parameter configuration. Existing technologies can degrade the access reliability of wireless devices.

[0215] The implementation of exemplary embodiments can improve cellular communication reliability by providing an RLF reporting mechanism that takes into account backhaul link information of wireless devices experiencing connection failures when serviced by an IAB node. The exemplary embodiments can support communication between network nodes and / or wireless devices for wireless backhaul link status information. The exemplary embodiments can support wireless configuration of network nodes and / or wireless devices based on wireless backhaul link status information. The implementation of exemplary embodiments can reduce connection delay and / or packet transmission delay of wireless devices. The implementation of exemplary embodiments can increase access / communication reliability and / or mobility performance of wireless devices.

[0216] In an exemplary embodiment, as illustrated in FIG. 33 and / or FIG. 34, a wireless device (e.g., UE, IAB node) may be serviced 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 may be connected to the first network node via a first wireless link (e.g., Link 1, wireless backhaul link, backhaul link, Uu interface, F1 interface, NG interface, S1 interface) to provide at least service to the wireless device. In one example, the first wireless link may include one or more wireless links connected via one or more network nodes (e.g., one or more IAB donor / IAB nodes). In one example, a failure of the first wireless link may include a failure of at least one of the one or more wireless links. In one example, the wireless device may be connected to a second network node via a second wireless link (e.g., Link 2, Uu interface). In one example, the second network node may provide a primary cell for the wireless device. In one example, the second network node may be an intermediate network node between the first network node and the wireless device.

[0217] In one 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 one example, the second network node may include at least one of a base station (e.g., gNB, eNB), a base station distribution unit (e.g., gNB-DU), and / or an IAB node (e.g., a relay node).

[0218] In one example, the third network node (e.g., second base station, gNB2, gNB, eNB) may or may not be a neighbor 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 through an Xn interface (e.g., X2 interface) and / or through one or more NG interfaces (e.g., through 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.

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

[0220] In one 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 one 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 one 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 one example, the wireless device may include at least one of user equipment, an integrated access and backhaul node (IAB node), and / or an integrated access and backhaul donor (IAB donor).

[0221] In one example, a downlink packet of a wireless device may be transmitted from a first network node to the wireless device through a 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 one example, an uplink packet of a wireless device may be transmitted from the wireless device to the first network node through a second network node. The uplink packet may be a PDCP layer packet. The first network node may forward data of the uplink packet to one or more UPFs and / or one or more IAB donors.

[0222] In one example, as illustrated in FIG. 35, 36, 37, 38, 39, 40, 41, 42, 43, and / or FIG. 44, 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) containing configuration parameters of a first cell of a second network node. In one example, the first cell may be a primary cell of the wireless device. In one example, the first cell may be a SpCell / PSCell of the wireless device.

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

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

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

[0226] In one example, at least one RRC message may include at least one rrc-transactionidentifier information element (IE), one or more radio resource configuration parameters, measurement configuration parameters, mobility control information parameters, one or more NAS layer parameters, security parameters, antenna information parameters, secondary cell add / modify parameters, secondary cell release parameters, WLAN configuration parameters, WLAN offloading configuration parameters, LWA configuration parameters, LWIP configuration parameters, RCLWI configuration parameters, sidelink configuration parameters, V2X configuration parameters, uplink transmission output configuration parameters (e.g., p-MAX, p-MeNB, p-SeNB), output control mode information element, a radio resource configuration-only IE including secondary cell group configuration parameters, and / or at least one of the above.

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

[0228] At least one acknowledgment / response message may include at least one RRC acknowledgment / response message. In one example, at least one acknowledgment / response message may include at least one of an uplink RRC message, a relay node reconfiguration completion message, an RRC connection reconfiguration completion message, an RRC connection re-establishment completion message, an RRC connection resumption completion message, an RRC connection setup completion message, and / or the like. At least one acknowledgment / response message may indicate whether one or more elements of at least one RRC message (e.g., one or more of the configuration parameters of the first cell) have been successfully configured by the wireless device. At least one acknowledgment / response message may indicate whether the bearer has been successfully established by the wireless device.

[0229] In one example, a wireless device may transmit a packet (e.g., through a first cell and / or at least one cell) to a second network node based on configuration parameters and / or one or more elements of at least one RRC message received from a first network node and / or a second network node (e.g., transmitted to an output level corresponding to p-MAX, based on RLC / PDCP / MAC configuration parameters and / or physical layer configuration received via at least one RRC message). The second network node may forward / transmit the packet to the first network node. The first network node may forward / transmit the packet (data of the packet) to one or more UPFs and / or one or more serving gateways. In one example, the wireless device may transmit a packet to the second network node via a bearer, for example, 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.

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

[0231] In one 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., backhaul link problem, backhaul link failure). In one example, the connection failure may include at least one of a wireless link failure and / or a handover failure. In one example, the connection failure may include a backhaul link failure. In one example, the backhaul link failure may include a failure of a first wireless link established between the first network node and the second network node (e.g., problem, failure, inability, unavailability, disconnection, outage). In one example, the first wireless link may include one or more wireless links connected through one or more network nodes. In one example, a failure of the first wireless link (e.g., problem, failure, inability, unavailability, disconnection, outage) may indicate at least one failure of one or more wireless links.

[0232] Backhaul link failure may include a connection failure of the second network node (e.g., wireless link failure, handover failure) (e.g., and / or may occur due to such connection failure). Backhaul link failure may include a failure of the second network node (e.g., failure, problem, inability, unavailability, disconnection, shutdown) [e.g., temporary failure of signaling with the first network node] (e.g., and / or may occur due to such failure). A failure of the first wireless 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); the expiration of a time alignment timer of a cell (e.g., a cell serving the second network node); a situation in which a first number of wireless link control (RLC) packet retransmissions (and / or HARQ retransmissions) of the second network node is greater than or equal to a first count value; A situation in which the reference signal reception output / quality (RSRP / RSRQ) of the second network node from a cell (e.g., a cell serving the second network node) is less than or equal to the first output / quality value; expiration of the fault timer (e.g., the time of the fault timer elapses after the fault is determined by the second network node); and / or other.

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

[0234] In one example, the wireless device may determine a backhaul link failure based on indications from a second network node and / or based on upper layer packet transmission status (e.g., RLC packet transmission failure, failure to receive ACKs from transmitted RLC packets, reception of NACKs for transmitted RLC packets, and / or a situation where the number of RLC packet retransmissions is greater than a configured value).

[0235] In one example, a wireless device may receive backhaul link failure information from a second network node indicating a failure (e.g., problem, fault) of a first wireless link established between a first network node and a second network node. In one example, the wireless device may determine a connection failure based on the backhaul link failure information. In one example, the wireless device may receive a disconnection indication from the second network node. The disconnection indication may include backhaul link failure information. The disconnection indication may be a command / indication to the wireless device to disconnect from the second network node (e.g., first cell) and / or the first network node. The second network node may transmit a disconnection indication in response to determining a backhaul link failure (e.g., problem) indicated by the backhaul link failure information.

[0236] In one example, a wireless device may receive a disconnection indication and / or backhaul link failure information through at least one of a physical layer command including a Media Access Control Element (MAC CE) and Downlink Control Information (DCI), an Adaptation Layer Indication, one or more User Plane packets, and / or a wireless resource control message (e.g., an RRC disconnection message, a Downlink RRC message, an RRC connection reconfiguration message). In one example, the Adaptation Layer Indication may include at least one of the following: at least one of one or more (e.g., Adaptation Layer) packets (e.g., containing data of packets); and / or the header of at least one of one or more (e.g., Adaptation Layer) packets (e.g., containing data of packets).

[0237] In one example, backhaul link failure information may include at least one of the following: a first node identifier of a first network node; a second node identifier of a second network node; a type of failure (e.g., failure, problem) of the backhaul link failure (e.g., transient failure, failure of at least one of a plurality of backhaul links of the second network node, and / or at least one of failures of all backhaul links of the second network node); a timer value for determining integrated access and backhaul node failure (e.g., a wireless device may determine the backhaul link failure in response to the timer expiration of the timer value; the timer may start in response to receiving backhaul link failure information); an indicator parameter indicating a state transition to a sleep state of one or more cells of the second network node; an indicator parameter indicating the release of one or more cells of the second network node; a cause value of a failure of the first wireless link (e.g., RLF cause, RLC retransmission count, failure timer expiration, beam failure recovery failure, random access failure, time alignment timer expiration); and a bearer identifier of a bearer affected by the failure of the first wireless link. One or more beam identifiers for one or more beams of a cell (e.g., used by a second network node) (e.g., a cell of a first network node) (e.g., a cell causing failure of a first wireless link); one or more bandwidth portion (BWP) identifiers for one or more bandwidth portions (BWP) of a cell (e.g., used by a second network node) (e.g., a cell of a first network node) (e.g., a cell causing failure of a first wireless link); and / or a cell identifier of a cell (e.g., used by a second network node) (e.g., a cell of a first network node) (e.g., causing failure of a first wireless link).

[0238] In one example, backhaul link failure information may include a node identifier of one of one or more network nodes between a first network node and a second network node (e.g., an access wireless link of the network node that has failed / failed / problematic; e.g., the access wireless link of the network node is one of one or more wireless links (in a failed state) connected through one or more network nodes between the first network node and the second network node and / or includes one such link).

[0239] In one example, the indication of backhaul link failure information may include an indication parameter (e.g., via MAC CE) indicating a transition of one or more cells of a second network node into a sleep state. In one example, if the indication parameter indicates that all cells or part of all cells of the second network node for the wireless device have transitioned into a sleep state, the wireless device may consider that the first wireless link is experiencing a failure (e.g., a failure).

[0240] In one example, the indication of backhaul link failure information may include an indication parameter indicating the inactivity of one or more cells of a second network node (e.g., via MAC CE). In one example, if the indication parameter indicates that all cells or part of all cells of the second network node for the wireless device are inactive, the wireless device may consider that the first wireless link is experiencing a failure (e.g., a failure).

[0241] In one example, the second network node may determine a failure (e.g., failure) of the first wireless link based on at least one of the following: a wireless link failure (e.g., a wireless link failure 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 through a cell (e.g., a cell serving the second network node; e.g., a cell of the first network node); the 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 situation in which a first number of wireless link control (RLC) packet retransmissions (or HARQ retransmissions) to the first network node exceeds a first value; A reference signal reception output / quality of a cell (e.g., a cell serving a second network node; e.g., a cell of a first network node) and / or a situation in which one or more beams of a cell (e.g., a cell serving a second network node; e.g., a cell of a first network node) are less than or equal to a predetermined output / quality value; a fault timer expiration; and / or other such things.

[0242] In one example, when the second network node determines a beam failure of one or more serving 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 failure (e.g., a failure) of the first wireless link. In one example, when the second network node determines a beam failure of one or more serving 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 failure timer and / or determine a failure (e.g., a failure) of the first wireless link in response to the expiration of the failure timer.

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

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

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

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

[0247] In one example, if the second network node determines that the reference signal reception output / 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) is less than or equal to a predetermined output / quality value, the second network node may determine a failure (e.g., a failure) of the first wireless link. In one example, if the second network node determines that the 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) is less than or equal to a predetermined output / quality value, the second network node may start a failure timer and / or determine a failure (e.g., a failure) of the first wireless link in response to the expiration of the failure timer.

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

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

[0250] In one example, the wireless device may clear (e.g., stop or release) the configured uplink acknowledgment type 2 of the cell of the second network node in response to determining a backhaul link failure. In one example, the wireless device may stop (e.g., stop) the bandwidth portion inactive timer of one or more bandwidth portions of the cell of the second network node in response to determining a backhaul link failure (e.g., considering that the cell is stopped and / or transitions to a sleep / inactive state). In one example, the wireless device may start (e.g. restart) the bandwidth portion inactive timer of the cell of the second network node in response to determining a backhaul link failure (e.g., considering that receiving backhaul link failure information is receiving a downlink indication through the cell and / or the corresponding bandwidth portion).

[0251] In one example, in response to determining a backhaul link failure, the wireless device may stop (e.g., abort) a random access procedure (e.g., an ongoing random access procedure) on the cell of the second network node (e.g., stop transmitting a random access preamble and / or stop monitoring a random access response). In one example, in response to determining a backhaul link failure, the wireless device may stop (e.g., stop) the secondary cell inactive timer of the cell of the second network node (e.g., considering that the cell is stopped and / or transitions to a sleep / inactive state). In one example, in response to determining a backhaul link failure, the wireless device may start (e.g. restart) the secondary cell inactive timer of the cell of the second network node (e.g. considering that receiving backhaul link failure information is receiving a downlink indication through the cell). In one example, the wireless device may switch the cell of the second network node to a sleep state in response to determining a backhaul link failure. In one example, the wireless device may disable the cell of the second network node in response to determining a backhaul link failure.

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

[0253] In one example, the wireless device may stop transmitting a sounding reference signal (SRS) through one or more cells to a second network node in response to a backhaul link failure determination (e.g., considering that one or more cells are stopped and / or transition to a sleep / inactive state). In one example, the wireless device may transmit a sounding reference signal (SRS) through one or more cells to a second network node (e.g., for a second network node to monitor an access link) in response to a backhaul link failure determination.

[0254] In one example, the wireless device may stop transmitting channel state information (e.g., CSI) to a second network node in response to determining a backhaul link failure (e.g., considering that a cell of the second network node is paused and / or transitions to a sleep / inactive state). In one example, the wireless device may transmit transmission channel state information (e.g., CSI) to a second network node in response to determining a backhaul link failure (e.g., for a cell transitioned to a sleep state; and / or for a second network node to monitor an access link).

[0255] In one example, the wireless device may stop transmitting a transmission block to a second network node via an uplink shared channel (e.g., SCH, PUSCH) in response to a backhaul link failure determination. In one example, the wireless device may stop transmitting a preamble to a second network node via a random access channel (e.g., RACH) in response to a backhaul link failure determination.

[0256] In one example, the wireless device may stop monitoring the physical downlink control channel (PDCCH) of the cell of the second network node in response to a backhaul link failure determination (e.g., when recovery and / or failure indication for the first wireless link is transmitted through another link (e.g., through the first network node and / or the third network node) or through a cell different from said cell). In one example, the wireless device may monitor the physical downlink control channel (PDCCH) of the cell of the second network node in response to a backhaul link failure determination (e.g., to receive recovery and / or failure indication for the first wireless link).

[0257] In one example, the wireless device may stop monitoring the physical downlink control channel (PDCCH) for the cell of the second network node in response to determining a backhaul link failure (e.g., considering that the cell of the second network node is paused and / or transitions to a sleep / inactive state). In one example, the wireless device may monitor the physical downlink control channel (PDCCH) for the cell of the second network node in response to determining a backhaul link failure (e.g., to receive a recovery and / or failure indication for the first wireless link).

[0258] In one example, the wireless device may stop transmitting the physical uplink control channel (PUCCH) through the cell of the second network node in response to determining a backhaul link failure. In one example, the wireless device may transmit the physical uplink control channel (PUCCH) through the cell of the second network node (e.g., to indicate a transition of the cell of the second network node to an off / deactivated / sleep state) in response to determining a backhaul link failure.

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

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

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

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

[0263] In one example, the measurement results may include the reference signal reception output (RSRP) and / or reference signal reception quality (RSRQ) of one or more cells, the RSRP / RSRQ of one or more beams of one or more cells, and / or the RSRP / RSRQ of a group of multiple beams of one or more cells. In one example, the wireless device may select a second cell in response that the RSRP / RSRQ of the second cell and / or one or more beams (or a group of beams) of the second cell is equal to and / or greater than a predetermined output value (e.g., delta dB) and / or quality value (e.g., gamma dB). In one example, the wireless device may select a second cell in response that the RSRP / RSRQ of the second cell and / or one or more beams (or a group of beams) of the second cell is 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 one or more neighboring cells of the second cell.

[0264] In one example, the wireless device may select the second cell in response to the second cell not belonging to a list of non-accessible cells (e.g., blacklisted cells) and / or belonging to a list of allowed access cells (e.g., whitelisted cells). The wireless device may select the second cell in response to at least one of the following: the second cell belonging to an allowed closed subscriber group; the second cell supporting a required network slice (e.g., based on NSSAI / S-NSSAI / network slice information broadcast through 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., the RAN capability of the third network node and / or the second cell); numerology / TTI supported by the second cell; and the congestion level of the second cell and / or one or more neighboring cells (e.g., the congestion level received through one or more system information blocks of the second cell). The backhaul link capacity of the third network node (e.g., backhaul link capacity information received through one or more system information blocks of the second cell); the backhaul link reliability of the third network node (e.g., backhaul link reliability information received through one or more system information blocks of the second cell); the backhaul link congestion of the third network node (e.g., backhaul link congestion information received through one or more system information blocks of the second cell); and / or other.

[0265] In one example, the wireless device may camp on the second cell in response to selecting the second cell of the third network node. In one example, the wireless device may initiate a random access procedure in response to selecting the second cell of the third network node by transmitting one or more random access preambles through the second cell to the third network node, for example, to establish an RRC connection with the third network node through the second cell. In one example, the wireless device may transmit one or more random access preambles through the second cell. The wireless device may receive a random access response for one or more random access preambles from the third network node. In one example, a wireless device may, based on a random access response, transmit a wireless resource control (RRC) connection (e.g., re-establish and / or establish) request message (e.g., RRC connection re-establish / establish / resume request message, and / or RRC connection re-establish / establish / resume completion message) to a third network node to, for example, request an RRC connection reset / establish / resume. In one 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 / failure / problem, other failure, and / or etc.). The indication field may indicate the cause of the RRC connection re-establish / establish / resume request (e.g., cause of establishment). In one example, an RRC connection request message (e.g., an RRC connection re-establishment / establishment / resumption request message, and / or an RRC connection re-establishment / establishment / resumption completion message) may include a report indication that the wireless device has a report related to a connection failure (e.g., an event to report, an RLF report, a connection failure report) to transmit to a base station (e.g., a third network node).

[0266] In one example, the wireless device may transmit a wireless link failure (RLF) report (e.g., connection failure report, backhaul link failure report) to a 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 connection failure occurred due to a backhaul link failure.

[0267] In one example, an RRC connection request message (e.g., an RRC connection re-establishment / establishment / resumption request message, and / or an RRC connection re-establishment / establishment / resumption completion message) may include an RLF report. In one example, a report message (e.g., a UE information message) transmitted from a wireless device to a third network node may include an RLF report.

[0268] In one example, a wireless device may receive a report request message (e.g., a UE information request message) from a third network node 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) the report indication of an RRC connection request message (e.g., an RRC connection re-establishment / establishment / resumption request message, and / or an RRC connection re-establishment / establishment / resumption completion message) received from the wireless device. In one 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) containing an RLF report to the third network node. In one 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 RRC messages. In one example, the wireless device may transmit an RLF report (e.g., a report message and / or a UE information message) to the third network node in response to receiving a report request message (e.g., a UE information request message) from the third network node.

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

[0270] In one example, the cause value may include one or more fields representing at least one of the following: beam failure of a cell serving a second network node (and / or cell identifier of the cell; one or more beam identifiers of one or more beams of the beam failure); beam failure recovery failure of a cell serving a second network node (and / or cell identifier of the cell; one or more beam identifiers of one or more beams of the beam failure recovery failure); expiration of a time alignment timer (TAT) of a cell serving a second network node (and / or cell identifier of the cell that has expired TAT); that a first number of radio link control (RLC) packet retransmissions (and / or HARQ retransmissions) of the second network node is greater than or equal to a first count value; and that the reference signal reception output / quality (RSRP / RSRQ) from the cell to the second network node is less than or equal to a first output / quality value (and / or cell identifier of the cell of the RSRP / RSRQ). The RSRP / RSRQ of a second network node from one or more beams of a cell is less than or equal to a second output / quality value (and / or the cell identifier of the cell, and / or the beam identifier of one or more beams of the RSRP / RSRQ); the expiration of a fault timer (e.g., the elapsed time of the fault timer after a fault is determined by the second network node); and / or other.

[0271] In one example, the cause value may indicate that the wireless device has determined a backhaul link failure based on indications from the second network node and / or based on upper layer packet transmission status (e.g., RLC packet transmission failure, failure to receive ACKs from transmitted RLC packets, reception of NACKs for transmitted RLC packets, and / or a situation where the number of RLC packet retransmissions is greater than or equal to a configured value). In one example, the cause value may indicate a failure (e.g., problem, failure) of the first wireless link established between the first network node and the second network node.

[0272] In one example, the cause value may indicate / include at least one of the following: a first node identifier of a first network node; a second node identifier of a second network node; a type of failure (e.g., failure, problem) of a backhaul link failure (e.g., transient failure, failure of at least one of a number of backhaul links of the second network node, and / or at least one of a failure of all backhaul links of the second network node); a timer value for determining integrated access and backhaul node failure (e.g., a wireless device may determine a backhaul link failure in response to the timer expiration of the timer value; the timer may start in response to receiving backhaul link failure information); an indicator parameter indicating a transition to a sleep state of one or more cells of the second network node; an indicator parameter indicating the release of one or more cells of the second network node; a cause value of a failure / problem / failure (e.g., backhaul link failure) of the first wireless link (e.g., RLF cause, RLC retransmission count, failure timer expiration, beam failure recovery failure, random access failure, time alignment timer expiration); Bearer identifier of a bearer affected by a failure of the first wireless link; one or more beam identifiers for one or more beams of a cell (e.g., used by a second network node) (e.g., a cell of the first network node) (e.g., a cell causing the failure of the first wireless link); one or more bandwidth portion (BWP) identifiers for one or more bandwidth portions (BWP) of a cell (e.g., used by a second network node) (e.g., a cell of the first network node) (e.g., a cell causing the failure of the first wireless link); and / or cell identifier of a cell (e.g., used by a second network node) (e.g., a cell of the first network node) (e.g., causing the failure of the first wireless link).

[0273] In one example, the cause value may include a node identifier of one of one or more network nodes between a first network node and a second network node (e.g., an access wireless link of the network node that has failed / failed / problematic; e.g., the access wireless link of the network node is one of one or more wireless links (in a failed state) connected through one or more network nodes between the first network node and the second network node and / or includes such one).

[0274] In one example, the cause value may include one or more fields indicating that the second network node has determined a failure (e.g., failure) of the first wireless link based on at least one of the following: a wireless link failure (e.g., a wireless link failure 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 through a cell (e.g., a cell serving the second network node; e.g., a cell of the first network node); the 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 situation in which a first number of wireless link control (RLC) packet retransmissions (or HARQ retransmissions) to the first network node exceeds a first value; A reference signal reception output / quality of a cell (e.g., a cell serving a second network node; e.g., a cell of a first network node) and / or a situation in which one or more beams of a cell (e.g., a cell serving a second network node; e.g., a cell of a first network node) are less than or equal to a predetermined output / quality value; a fault timer expiration; and / or other such things.

[0275] In one example, the RLF report may include at least one of the following: an identifier of a first network node; an identifier of a 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 / receive point identifier of the second network node; a cell identifier of a first cell; a beam identifier of a first cell; a beam group identifier of one or more beams of the first cell; an F1 radio device identifier of a radio device; an information element indicating that a connection failure has occurred due to a backhaul link failure; a type of failure (e.g., failure, problem) (e.g., transient failure; failure of at least one of a plurality of backhaul links of the second network node; and / or including at least one of failures of all backhaul links of the second network node); a timer value for determining an integrated access and backhaul node failure; a value for the cause 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 used by the second network node) (e.g., a cell causing the failure of the first radio link).

[0276] In one example, the RLF report may include at least one of the cell identifier of the first cell, the BWP index of the BWP (e.g., the BWP index of the active BWP at the time the connection failure is determined), and / or the like. In one example, the RLF report may include one or more elements of BWP configuration parameters. The RLF report may include parameters (of BWP configuration parameters) representing at least one of the following: 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 inactive timer; an initial BWP index of an initial BWP (e.g., an initial active BWP) of a plurality of BWPs; a subcarrier interval for a plurality of BWPs; a periodic prefix; a plurality of consecutive PRBs; an index within 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; DCI detection for a PDSCH receive timing value; PDSCH reception for HARQ-ACK transmission timing value; DCI detection up to PUSCH transmission timing value; offset of the first PRB of each DL bandwidth or UL bandwidth for the first PRB of the bandwidth; and / or other.

[0277] In one example, an RLF report may include one or more reported IEs indicating information associated with a connection failure of a wireless device. One or more reported IEs may indicate at least one of the following: a fault cell identifier of the faulty cell (e.g., a cell and / or a first cell that provided service to a second network node at the time of a backhaul link failure / failure / problem and / or connection failure), wherein the wireless device experienced a connection failure while using the faulty cell; the RLF cause of the connection failure, wherein the RLF indicates at least one of a t310 expiration, a random access problem, a maximum number of radio link control (RLC) retransmissions, or a t312 expiration; a network node identifier of the second network node in the faulty cell (e.g., an IAB node identifier, a gNB identifier, a UE identifier, a gNB-DU identifier, a C-RNTI) and / or a wireless device identifier of the wireless device (e.g., a C-RNTI, IMEI, a TMSI); and a carrier frequency value of the faulty cell. A first time value (e.g., timeConnFailure) indicating the time elapsed since the last handover initialization for the wireless device until the connection failure; a second time value (e.g., timeSinceFailure) indicating the time elapsed since the connection failure (or configuration failure); a connection failure type indicating whether the connection failure and / or backhaul link failure is due to an RLF or handover failure; a measurement result including at least one of the RSRP or RSRQ of the cell in a failure state; a measurement result including at least one of the RSRP or RSRQ of one or more neighboring cells of the cell in a failure state; a quality classification indicator 1 bearer indicating the connection failure and / or backhaul link failure that occurred while a bearer having the same QCI value as 1 was configured; the C-RNTI of the wireless device in the first cell; and / or other.

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

[0279] In one example, the cause value of the connection failure may indicate that the cause determining the connection failure of the wireless device includes at least one of t310 expiration, a random access problem (e.g., failure), a maximum number of retransmissions of the wireless link control (RLC), t312 expiration, and / or the like. In one example, the cause value of the backhaul link failure may indicate that the cause determining the backhaul link failure of the wireless device (e.g., access link failure of the second network node) includes at least one of t310 expiration, a random access problem (e.g., failure), a maximum number of retransmissions of the wireless link control (RLC), t312 expiration, and / or the like.

[0280] In one example, t310 expiration may indicate that timer t310 of the wireless device and / or second network node has expired in a cell in a failed state when a connection failure (e.g., backhaul link failure) occurs. Timer t310 may start when the wireless device and / or second network node detects a physical layer-related problem (e.g., for a primary cell) (e.g., when the wireless device and / or second network node receives a specific number (e.g., N310) of consecutive asynchronous indications from the lower layer). In one example, timer t310 may stop in the following cases: when the wireless device and / or second network node receives a specific number (e.g., N311) of consecutive synchronous indications from the lower layer (e.g., for a primary cell); when a handover procedure is triggered; when an RRC connection re-establishment procedure is initiated; and / or other. In one example, when timer t310 expires and security is not enabled, the wireless device and / or the second network node may enter an RRC idle state. In one example, when timer t310 expires and security is enabled, the wireless device and / or the second network node may initiate an RRC connection re-establishment procedure.

[0281] In one example, t312 expiration may indicate that timer t312 of the wireless device and / or the second network node has expired in the cell in the failure state when a connection failure (e.g., backhaul link failure) occurs. Timer t312 may start when a measurement report for the measurement identity configured for timer t312 is triggered while timer t310 is running. In one example, timer t312 may stop in the following cases: when receiving a certain number (e.g., N311) of consecutive synchronization indications from a lower layer; when a handover procedure is triggered; when a connection reset procedure is initiated; upon the expiration of timer t310; and / or other. In one example, upon the expiration of timer t312, if security is not enabled, the wireless device and / or the second network node may enter an idle state. In one example, when timer t312 expires, if security is enabled, the wireless device and / or the second network node may initiate an RRC connection re-establishment procedure.

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

[0283] In one example, the wireless device identifier of the wireless device may include a C-RNTI, Temporary Mobile Subscriber Identity (TMSI), International Mobile Subscriber Identity (IMSI), Global Unique Temporary Identifier (GUTI), and / or the like in the cell in a state of failure (e.g., the first cell). In one example, the carrier frequency value may represent the carrier frequency value of the cell in a state of failure. In one example, the carrier frequency value may include at least one of EARFCN, ARFCN, and / or the like, for example, along with the maximum value of maxEARFCN. In one example, the carrier frequency value may be determined according to the band used when obtaining the relevant measurement result.

[0284] In one example, the network node identifier of the second network node may include a C-RNTI, Temporary Mobile Subscriber Identity (TMSI), International Mobile Subscriber Identity (IMSI), Global Unique Temporary Identifier (GUTI), and / or the like in the cell in a failed state (e.g., the cell that provided service to the second network node during a backhaul link failure and / or connection failure (e.g., the primary cell of the second network node)). In one example, the carrier frequency value may represent the carrier frequency value of the cell in a failed state. In one example, the carrier frequency value may include at least one of EARFCN, ARFCN, and / or the like, for example, along with the maximum value of maxEARFCN. In one example, the carrier frequency value may be determined according to the band used when obtaining the relevant measurement result.

[0285] In one example, the measurement result may include at least one of a Reference Signal Receive Output result (RSRP) or a Reference Signal Receive Quality (RSRQ) of at least one of a cell in a failed state (e.g., a cell and / or first cell that provided service to the second network node at the time of a backhaul link failure / failure / problem and / or connection failure), the last serving cell of the wireless device and / or second network node, one or more serving cells of the wireless device and / or second network node, one or more neighbor cells of the cell in a failed state (of the wireless device and / or second network node), and / or one or more secondary cells of the wireless device and / or second network node. In one example, the wireless device and / or second network node may determine one or more elements of the measurement result by measuring when (or before / after) the wireless device experienced a connection failure and / or when (or before / after) the second network node experienced a backhaul link failure (e.g., an access link failure of the second network node). In one example, a quality classification indicator 1 bearer (e.g., drb-EstablishedWithQCI-1) may indicate that a connection failure and / or backhaul link failure occurred while a bearer with a QCI value of 1 was being configured.

[0286] In one example, the first network node may receive one or more elements of a wireless link failure report from the third network node. In one example, the first network node may receive RLF information (containing one or more elements) including one or more elements of an RLF report from the third network node. In one example, the first network node may receive RLF information through 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 network node(s)) (e.g., through a handover report message and / or an RLF indication message). In one example, the first network node may receive RLF information through one or more NG interfaces and / or one or more S1 interfaces (e.g., through one or more core network nodes between the first network node and the third network node (e.g., one or more AMFs, one or more MMEs, one or more SGSNs, one or more GGSNs)) (e.g., through gNB / eNB / NODE configuration transmission messages and / or AMF / MME configuration transmission messages; e.g., the SON information of the gNB / eNB / NODE configuration transmission messages and / or AMF / MME configuration transmission messages may include RLF information). In one example, the first network node may receive RLF information through 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 network node(s)) (e.g., through one or more F1 interface messages).

[0287] In one example, as illustrated in FIG. 34, if the first network node is the third network node, the first network node can receive an RLF report from a wireless device. In one example, if the second network node is the third network node, the first network node can receive RLF information and / or an RLF report from the second network node. In one example, if the IAB node receiving service from the first network node is the third network node, the first network node can receive RLF information and / or an RLF report from the IAB node receiving service from the first network node.

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

[0289] In one example, the first network node may determine at least one cell configuration parameter (e.g., radio resource configuration parameters) of one or more cells of one or more IAB nodes based on the first network node and / or RLF information for one or more radio devices based on one or more elements of a radio link failure report and / or RLF information. One or more cells may include a cell in a failure state (e.g., a first cell of the second network node, and / or a cell that provided service to the second network node during a connection failure and / or backhaul link failure). In one example, the one or more cell configuration parameters may include one or more of the following: at least one BWP configuration parameter; at least one transmission output 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 radio devices; at least one system information; at least one interference control parameter; and / or others.

[0290] In one example, at least one BWP configuration parameter may be for one or more wireless devices. At least one BWP configuration parameter may include one or more parameters representing at least one of the following: 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 inactive timer; an initial BWP index of an initial BWP (e.g., an initial active BWP) of a plurality of BWPs; a subcarrier interval for a plurality of BWPs; a periodic prefix code; a plurality of consecutive PRBs; an index within 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; DCI sensing up to a PDSCH receive timing value; PDSCH reception up to a HARQ-ACK transmit timing value; DCI sensing up to a PUSCH transmit timing value; an offset of the first PRB of each of the DL bandwidth or UL bandwidth with respect to the first PRB of the bandwidth; and / or other.

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

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

[0293] In one example, at least one transmission output configuration parameter may include a maximum downlink / uplink cell transmission output, a physical downlink control channel (PDCCH) transmission output, one or more output control parameters for the uplink and / or downlink, a TPC configuration parameter, an SRS configuration parameter, and / or the like, for one or more wireless devices and / or a first network node. In one example, if the first network node determines that a connection failure has occurred due to a low transmission output of the PDCCH (e.g., based on measurement results from an RLF report), the first network node may increase the transmission output of the PDCCH. In one example, if a connection failure has occurred due to significant interference to the PDCCH, the first network node may reschedule the PDCCH to be located in a different subframe.

[0294] In one example, when a wireless device and / or an IAB node (e.g., a second network node) experiences a connection failure during the time when the first BWP among the multiple BWPs of a cell is an active BWP, the base station (e.g., a first network node) may increase the uplink / downlink output level (e.g., an increase of 0.1 dB) for one or more wireless devices (e.g., a UE serviced in the first cell) when one or more wireless devices use the first BWP as an active BWP.

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

[0296] In one example, if the cause of the connection failure of a wireless device and / or IAB node (e.g., a second network node) is a maximum number of RLC retransmissions (e.g., an uplink transmission problem; the number of RLC retransmissions exceeds a threshold value), and the wireless device and / or IAB node (e.g., a second network node) experiences a connection failure during the time when the first BWP among the multiple BWPs of the cell is an active BWP, the base station (e.g., a first network node) may increase the uplink output level for one or more wireless devices when one or more wireless devices use the first BWP as an active BWP.

[0297] In one example, at least one frequency configuration parameter may include a carrier frequency, a bandwidth, one or more bandwidth portion configuration parameters, and / or the like. In one example, if a cell of a first network node receives significant interference from neighboring cells, the first network node may change the operating frequency to another frequency. In one example, if a specific bandwidth portion of a serving cell of the first network node receives significant interference from neighboring cells or other technologies, the first network node may change the default bandwidth portion and / or active bandwidth portion of one or more wireless devices to another bandwidth portion.

[0298] In one example, at least one beamforming configuration parameter may include one or more beamforming direction configuration parameters, one or more beam sweeping 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 of one or more beams, and / or the like. In one example, if a connection failure occurs due to a random access failure or a beam recovery procedure failure (e.g., unsynchronized), the base station (e.g., a first network node) may reschedule random access resources and / or BRACH resources, and / or reconfigure the preamble to reduce random access contention.

[0299] In one 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, and / or the like. In one example, at least one antenna configuration parameter may include a default antenna configuration parameter, an antenna port configuration parameter, a plurality of CRS antenna port parameters, and / or the like. In one example, at least one cell selection or reselection configuration parameter for one or more wireless devices may include one or more output / 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, and / or the like. In one example, if a connection failure occurs due to a random access failure of a wireless device and / or a second network node, the first network node may increase one or more output / time threshold parameters to allow the wireless device to avoid a cell in a failure state if the wireless device and / or IAB node (e.g., the second network node) does not satisfy an increased threshold.

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

[0301] In one example, the first network node may transmit at least one system information block containing 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., the second network node).

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

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

[0304] In one example, a second network node and / or a first network node may determine at least one cell configuration parameter (e.g., radio resource configuration parameters) of one or more cells of the second network node based on one or more elements of a radio link failure report and / or RLF information, so that one or more IAB nodes are serviced (e.g., serviced by the second network node) and / or one or more radio devices are serviced (e.g., serviced by the second network node) based on the RLF information. One or more cells may include a cell in a failure state (e.g., the first cell of the second network node). In one example, one or more cell configuration parameters may include one or more of the following: at least one BWP configuration parameter; at least one transmission output 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 radio devices; at least one system information; at least one interference control parameter; and / or others.

[0305] In one example, at least one BWP configuration parameter may be for one or more wireless devices. At least one BWP configuration parameter may include one or more parameters representing at least one of the following: 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 inactive timer; an initial BWP index of an initial BWP (e.g., an initial active BWP) of a plurality of BWPs; a subcarrier interval for a plurality of BWPs; a periodic prefix code; a plurality of consecutive PRBs; an index within 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; DCI sensing up to a PDSCH receive timing value; PDSCH reception up to a HARQ-ACK transmit timing value; DCI sensing up to a PUSCH transmit timing value; an offset of the first PRB of each of the DL bandwidth or UL bandwidth with respect to the first PRB of the bandwidth; and / or other.

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

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

[0308] In one example, at least one transmission output configuration parameter may include a maximum downlink / uplink cell transmission output, a physical downlink control channel (PDCCH) transmission output, one or more output control parameters for the uplink and / or downlink, a TPC configuration parameter, an SRS configuration parameter, and / or the like, for one or more wireless devices and / or a second network node. In one example, if the second network node and / or the first network node determines that a connection failure has occurred due to a low transmission output of the PDCCH (e.g., based on measurement results from an RLF report), the second network node and / or the first network node may increase the transmission output of the PDCCH. In one example, if a connection failure has occurred due to significant interference to the PDCCH, the first network node may reschedule the PDCCH to be located in a different subframe.

[0309] In one example, if a wireless device experiences a connection failure during the time when the first BWP among the multiple BWPs of a cell is an active BWP, the base station (e.g., a second network node and / or a first network node) may increase the uplink / downlink output level (e.g., an increase of 0.1 dB) for one or more wireless devices (e.g., a UE serviced in the first cell) when one or more wireless devices use the first BWP as an active BWP.

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

[0311] In one example, if the cause of the wireless device's connection failure is a maximum number of RLC retransmissions (e.g., an uplink transmission problem; the number of RLC retransmissions exceeds a threshold value) and the wireless device experiences a connection failure during the time when the first BWP among the cell's multiple BWPs is an active BWP, the base station (e.g., a second network node and / or a first network node) may increase the uplink output level for one or more wireless devices when one or more wireless devices use the first BWP as an active BWP.

[0312] In one example, at least one frequency configuration parameter may include a carrier frequency, a bandwidth, one or more bandwidth portion configuration parameters, and / or the like. In one example, if a cell of a second network node receives significant interference from neighboring cells, the second network node and / or the first network node may change the operating frequency to a different frequency. In one example, if a specific bandwidth portion of a serving cell of the second network node receives significant interference from neighboring cells or other technologies, the second network node and / or the first network node may change the default bandwidth portion and / or active bandwidth portion of one or more wireless devices to a different bandwidth portion.

[0313] In one example, at least one beamforming configuration parameter may include one or more beamforming direction configuration parameters, one or more beam sweeping 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 of one or more beams, and / or the like. In one example, if a connection failure occurs due to a random access failure or a beam recovery procedure failure (e.g., lack of synchronization), the base station (e.g., a second network node and / or a first network node) may reschedule random access resources and / or BRACH resources, or reconfigure the preamble to reduce random access contention.

[0314] In one 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, and / or the like. In one example, at least one antenna configuration parameter may include a default antenna configuration parameter, an antenna port configuration parameter, a plurality of CRS antenna port parameters, and / or the like. In one example, at least one cell selection or reselection configuration parameter for one or more wireless devices may include one or more output / 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, and / or the like. In one example, if a connection failure occurs due to a random access failure of a wireless device, the second network node and / or the first network node may increase one or more output / time threshold parameters to allow the wireless device to avoid a cell in a failure state if the wireless device fails to satisfy the increased threshold.

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

[0316] In one example, a second network node and / or a first network node may transmit at least one system information block containing 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 wireless devices.

[0317] In one example, the second network node and / or the first network node may configure handover parameters based on one or more elements of an RLF report and / or RLF information. In one example, if the backhaul link connection is unstable (e.g., the determination that it is "unstable" is based on RLF information and / or one or more elements of an RLF report), the second network node and / or the first network node may initiate the handover of the serving wireless device (and / or serving IAB node) earlier than when the backhaul link connection becomes stable, for example, to avoid connection failure due to a backhaul link failure. In one example, if the RSRP / RSRQ of a second network node relative to a first network node (e.g., RSRP / RSRQ measured from the first network node by the second network node; e.g., backhaul link RSRP / RSRQ) is lower than a predetermined updated value (e.g., determined based on one or more elements of an RLF report and / or RLF information; e.g., if a backhaul link failure occurs when the RSRP / RSRQ of the second network node relative to the first network node is X dB, the updated value may be configured to X dB or a value higher than X dB), the second network node and / or the first network node initiate a handover of a wireless device having a stable access link connection with the second network node (serviced by the second network node) (e.g., a wireless device having an RSRP / RSRQ higher from the cell of the second network node than the handover threshold RSRP / RSRQ used in the case of a stable backhaul link connection (e.g., an updated value and / or a backhaul link RSRP / RSRQ higher than X dB)). It is possible.

[0318] In one example, a wireless device may receive at least one radio resource control (RRC) message from a first network node (e.g., and / or a second network node) containing configuration parameters of a first cell of a second network node. The wireless device may transmit a packet to the second network node based on the configuration parameters (described herein). The wireless device may determine a connection failure from the first network node (e.g., and / or a second network node) based on a backhaul link failure (e.g., backhaul link problem, backhaul link failure). In response to the connection failure, the wireless device may select a second cell of a third network node for a radio resource control connection (e.g., establishment and / or re-establishment). The wireless device may transmit a radio link failure report to the third network node containing a cause value of the connection failure. The cause value may indicate that the connection failure occurred due to a backhaul link failure.

[0319] In one example, the wireless device may receive backhaul link failure information from a second network node indicating a failure (e.g., problem, failure) of a first wireless link established between a first network node and a second network node. In one example, the wireless device may determine a connection failure based on the backhaul link failure information. In one example, the wireless device may receive backhaul link failure information through at least one of a Media Access Control Element (MAC CE), a physical layer command including downlink control information, an adaptation layer indication, and / or a wireless resource control message (e.g., an RRC disconnection message).

[0320] In one example, backhaul link failure information may include at least one of the following: a first node identifier of a first network node; a second node identifier of a second network node; a type of failure (e.g., failure, problem) (e.g., transient failure, failure of at least one of a plurality of backhaul links of the second network node, and / or at least one of failure of all backhaul links of the second network node); a timer value for determining integrated access and backhaul node failure; an indicator parameter indicating a transition to a sleep state of one or more cells of the second network node; an indicator parameter indicating the release of one or more cells of the second network node; a cause value of a failure of the first wireless link (e.g., RLF cause); a bearer identifier of a bearer affected by the failure of the first wireless link; and / or a cell identifier of a cell of the first network node (e.g., one used by the second network node) (e.g., a cell causing the failure of the first wireless link).

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

[0322] In one example, the wireless device may transmit one or more random access preambles through a second cell. The wireless device may receive random access responses for one or more random access preambles from a third network node. In one example, the wireless device may transmit a request message for a wireless resource control connection (e.g., re-establishment and / or establishment) based on the random access responses.

[0323] In one example, the connection failure may include at least one of a wireless link failure and / or a handover failure. The first cell may be a primary cell of a wireless device. The first network node may include a third network node. The second network node may include a third network node. In one example, the first cell may be a second cell. In one example, the wireless 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 transmission and reception 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 connection failure has occurred due to a backhaul link failure; Type of failure (e.g., failure, problem) (e.g., transient failure; failure of at least one of a plurality of backhaul links of the second network node; and / or including at least one of a failure of all backhaul links of the second network node); timer value for determining integrated access and backhaul node failure; cause value of failure of the first wireless link (e.g., RLF cause); and / or cell identifier of a cell of the first network node (e.g., used by the second network node) (e.g., cell causing failure of the first wireless link).

[0324] In one 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 donor. In one 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 donor.

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

[0326] In one example, a wireless device may receive at least one wireless resource control message from a first network node that includes configuration parameters of a first cell of a second network node. The wireless device may transmit a packet to the second network node based on the configuration parameters. The wireless device may receive backhaul link failure information from the second network node indicating a failure of a first wireless 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. In response to the connection failure, the wireless device may select a second cell of the first network node for a wireless resource control connection. The wireless device may transmit a wireless link failure report to the first network node that includes a cause value of the connection failure, wherein the cause value indicates that the backhaul link failure caused the connection failure.

[0327] In one example, a wireless device may receive at least one wireless resource control message from a first network node that includes configuration parameters of a first cell of a second network node. The wireless device may transmit a packet to the second network node based on the configuration parameters. The wireless device may receive backhaul link failure information from the second network node indicating a failure of a first wireless 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. In response to the connection failure, the wireless device may select a second cell of the second network node for a wireless resource control connection. The wireless device may transmit a wireless link failure report to the second network node that includes a cause value of the connection failure, wherein the cause value indicates that the backhaul link failure caused the connection failure.

[0328] In one example, a wireless device may receive at least one wireless resource control message from a first network node through a second network node, the message including configuration parameters of a first cell of a second network node. The wireless device may transmit a packet to the second network node through the first cell. The wireless device may determine a failure in the connection to the first network node based on a backhaul link failure between the first network node and the second network node. Based on the connection failure determination, the wireless device may select a second cell of a third network node for the wireless resource control connection. The wireless device may transmit a wireless link failure report indicating a backhaul link failure to the third network node.

[0329] In one example, a wireless device may receive backhaul link failure information from a second network node indicating a failure of a first wireless link established between a first network node and a second network node. The wireless device may receive backhaul link failure information through at least one of a media access control element, a physical layer command including downlink control information, an adaptation layer indication, a wireless resource control message, and / or the like. In one example, the wireless device may determine a connection failure based on the backhaul link failure information. 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 type of failure (e.g., including at least one of a transient failure, a failure of at least one of a plurality of backhaul links of the second network node, a failure of all backhaul links of the second network node, etc.); a timer value for determining integrated access and backhaul node failures; an indication parameter indicating a transition to a sleep state of one or more cells of the second network node; an indication parameter indicating the release of one or more cells of the second network node; Value of the cause of the failure of the first wireless link; bearer identifier of the bearer affected by the failure of the first wireless link; cell identifier of the cell of the first network node - which is the cell causing the failure of the first wireless link - and / or other.

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

[0331] In one example, a wireless device may transmit one or more random access preambles through a second cell. The wireless device may receive a random access response for one or more random access preambles from a third network node. Based on the random access response, the wireless device may transmit a wireless resource control connection request message to the third network node. Connection failures may include at least one of a wireless link failure, a handover failure, and / or the like. 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. A wireless link failure report may include at least one of the following: an identifier of a first network node, an identifier of a second network node, a base station identifier of the second network node, an integrated access and backhaul identifier of the second network node, a transmission and reception point identifier of the second network node, a cell identifier of a 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 a wireless device, an information element indicating that a connection failure has occurred due to a backhaul link failure, a type of failure (e.g., including at least one of a transient failure, a failure of at least one of a plurality of backhaul links of the second network node, a failure of all backhaul links of the second network node, etc.), a timer value for determining an integrated access and backhaul node failure, a value for the cause of the failure of the first wireless link, a cell identifier of the cell of the first network node (e.g., this cell may cause the failure of the first wireless link), and / or other etc.

[0332] In one example, the first network node may include at least one of a base station, a base station central unit, an integrated access and backhaul donor, and / or the like. The second network node may include at least one of a base station, a base station distributed unit, an integrated access and backhaul donor, and / or the like.

[0333] In one example, a first network node may receive one or more elements of a wireless link failure report from a third network node. The first network node may configure wireless resource configuration parameters based on said one or more elements. The wireless resource configuration parameters may include beam configuration parameters for the second network node. The wireless resource configuration parameters may include handover triggering parameters for an integrated access and backhaul node. The handover triggering parameters may include at least one of a wireless signal reception quality value, a wireless signal reception output value, and / or the like. The first network node may transmit one or more elements of the wireless link failure report to the second network node.

[0334] In one example, as illustrated in FIG. 45, the wireless device can communicate with the first network node through the second network node (4510). The wireless device can transmit a wireless link failure report indicating a backhaul link failure between the first network node and the second network node to the third network node (4520).

[0335] In one example, as illustrated in FIG. 46, a third network node may receive a wireless link failure report from a wireless device indicating a backhaul link failure between a first network node and a second network node (4610). A failure in the connection between the wireless device and the first network node through the second network node may be due to a backhaul link failure (4620). The third network node may transmit one or more elements of the wireless link failure report to a first access node.

[0336] In one example, the wireless device may transmit a wireless link failure report indicating that the connection failure between the wireless device and the first network node through the second network node is due to a backhaul link failure between the first network node and the second network node.

[0337] In one example, the wireless device may transmit a wireless link failure report indicating a backhaul link failure between a first network node and a second network node. A failure in the connection between the wireless device and the first network node through the second network node may be due to a backhaul link failure.

[0338] In one example, the wireless device may transmit a wireless link failure report indicating a backhaul link failure between a first network node and a second network node. The wireless device may communicate with the first network node through the second network node prior to the backhaul link failure.

[0339] In one example, the wireless device can transmit a wireless link failure report to a third network node indicating a backhaul link failure between a first network node and a second network node. The wireless device can communicate with the first network node through the second network node prior to the backhaul link failure.

[0340] In one example, the wireless device can determine a failure in the connection between the wireless device and the first network node through the second network node based on a backhaul link failure between the first network node and the second network node. The wireless device can transmit a wireless link failure report indicating a backhaul link failure to the third network node.

[0341] In one example, a wireless device may receive at least one wireless resource control message from a first network node that includes configuration parameters of a first cell of a second network node. The wireless device may transmit a packet to the second network node based on the configuration parameters. The wireless device may receive backhaul link failure information from the second network node indicating a failure of a first wireless 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. Based on the connection failure, the wireless device may select a second cell of a third network node for a wireless resource control connection. The wireless device may transmit a wireless link failure report to the third network node that includes a cause value of the connection failure. The cause value may indicate that a connection failure occurred due to a backhaul link failure.

[0342] The embodiments may be configured to operate when necessary. The disclosed mechanism may be performed when certain criteria are met, for example, in a wireless device, a base station, a wireless environment, a network, a combination thereof, and / or others. The exemplary criteria may be based at least partially, for example, the configuration of the wireless device or network node, traffic load, initial system setup, packet size, traffic characteristics, a combination thereof, and / or others. When one or more criteria are met, various exemplary embodiments may be applied. Thus, it may be possible to implement exemplary embodiments that optionally implement the disclosed protocol.

[0343] A base station may communicate with a mix of wireless devices. Wireless devices and / or base stations may support multiple technologies and / or multiple releases of the same technology. Wireless devices may have some specific performance(s) depending on the wireless device class and / or performance(s). A base station may include multiple sectors. When the present disclosure refers to a base station communicating with multiple wireless devices, it may refer to a subset of all wireless devices within a coverage area. The present disclosure may refer, for example, to a given sector of a base station and multiple wireless devices of a given LTE or 5G release having a given performance. The multiple wireless devices in the present disclosure may refer to a selected plurality of wireless devices and / or a subset of all wireless devices within a coverage area performing according to the disclosed methods, etc. For example, since such wireless devices or base stations perform based on older releases of LTE or 5G technology, there may be multiple base stations or multiple wireless devices in a coverage area that may not follow the disclosed methods.

[0344] In the present disclosure, singular notations (“a” and “an”) and similar phrases shall be interpreted as “at least one” and “one or more.” Similarly, any term ending in the suffix “(s”) shall be interpreted as “at least one” and “one or more.” In the present disclosure, the term “may” shall be interpreted as “e.g. may”. In other words, the term “may” indicates that the phrase following this term is an example of one of a number of suitable possibilities that may or may not be used in one or more of the various embodiments.

[0345] If A and B are sets and every element of A is also an element of B, A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {cell1, cell2} are {cell1}, {cell2}, and {cell1, cell2}. The phrase "based on" (or likewise "at least based on") indicates that the phrase following the term "based on" is an example of one of a number of appropriate possibilities that may or may not be used in one or more various embodiments. The phrase "responding to" (or likewise "at least responding to") indicates that the phrase following the term "responding" is an example of one of a number of appropriate possibilities that may or may not be used in one or more various embodiments. The phrase "depending on" (or likewise "at least dependent on") indicates that the phrase following the term "depending" is an example of one of a number of appropriate possibilities that may or may not be used in one or more various embodiments. The phrase "using / using" (or "at least using / using") indicates that the phrase following the term "using / using" is an example of one of a number of suitable possibilities that may or may not be used in one or more various embodiments.

[0346] The term "configured" may relate to the capacity of a device regardless of whether the device is in an operating or non-operating state. Being configured may refer to specific settings of a device that affect the operating characteristics of the device, regardless of whether the device is in an operating or non-operating state. In other words, hardware, software, firmware, registers, memory values, and / or others may be "configured" within the device to provide specific characteristics to the device, regardless of whether the device is in an operating or non-operating state. Terms such as "control messages generated by the device" may mean that, regardless of whether the device is in an operating or non-operating state, the control messages contain parameters that can be used to configure specific characteristics or to implement specific behaviors of the device.

[0347] Various embodiments are disclosed in this disclosure. Limitations, features, and / or components from the disclosed exemplary embodiments may be combined to create other embodiments within the scope of this disclosure.

[0348] In the present disclosure, parameters (or equivalently so-called, fields or information elements: IE) may include one or more information objects, and an information object may include one or more other objects. For example, parameter (IE) N includes parameter (IE) M, parameter (IE) M includes parameter (IE) K, and parameter (IE) K includes parameter (information element) J. In this case, for example, N includes K, and N includes J. In an exemplary embodiment, if one or more (or at least one) message(s) include a plurality of parameters, it means that one of the plurality of parameters is present in at least one of the one or more messages but is not required to be present in each of the one or more messages. In an exemplary embodiment, if one or more (or at least one) message(s) represent a value, event, and / or condition, it means that the value, event, and / or condition is indicated by at least one of the one or more messages but is not required to be indicated by each of the one or more messages.

[0349] In addition, many of the features presented above are described as optional through the use of “can” or parentheses. For the sake of brevity and readability, this disclosure does not explicitly specify every permutation that can be obtained by selecting from the set of optional features. However, this disclosure should be interpreted as explicitly disclosing all such permutations. For example, a system described as having three optional features can be implemented in seven different ways, namely, by only one of the three possible features, by any two of the three possible features, or by all three of the three possible features.

[0350] Many of the elements described in the disclosed embodiments may be implemented as modules. A module is defined herein as an element that performs a defined function and has a defined interface to another element. The modules described in this disclosure may be implemented as hardware, software combined with hardware, firmware, wetware (e.g., hardware having biological elements), or a combination thereof, all of which are operationally equivalent. For example, a module may be implemented as a hardware machine (e.g., C, C++, Fortran, Java, Basic, Matlab, etc.) or as a software routine written in a computer language configured to be executed by a modeling / simulation program, such as Simulink, Stateflow, GNU Octave, or LabVIEW MathScript. Additionally, a module may be implemented using physical hardware that incorporates 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 synthetic programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, and C++. FPGAs, ASICs, and CPLDs are programmed using hardware description languages ​​(HDLs) such as VHSIC Hardware Description Language (VHDL) or Verilog to configure connections between internal hardware modules with fewer functions in programmable devices. The aforementioned techniques are often combined to achieve the results of functional modules.

[0351] The disclosure of this patent document includes copyrighted material. The copyright owner does not object to facsimile reproduction of the patent document or patent disclosure as set forth in the patent file or records of the Patent Office for limited purposes required by law, but reserves all copyright in any case otherwise.

[0352] Although various embodiments have been described above, it should be understood that these examples are presented as examples and not as limitations. Those skilled in the art will clearly understand that various changes in form and detail may be made without departing from the spirit and scope of the disclosure. In fact, after reading the description above, methods for implementing alternative embodiments will be apparent to those skilled in the art. Accordingly, the embodiments should not be limited by any of the exemplary embodiments described above.

[0353] Additionally, any drawings highlighting functions and benefits should be understood as being provided for illustrative purposes only. The disclosed architecture is sufficiently flexible and configurable and may be used in ways different from those depicted. For example, actions listed in any flowchart may be rearranged or used optionally in only some embodiments.

[0354] Furthermore, the purpose of the summary of the disclosure is to enable the United States Patent and Trademark Office and the public, in general, and in particular scientists, technicians, and practitioners in the relevant field who are not familiar with patent or legal terminology or grammar, to determine the nature and essence of the technical disclosure of the present application through a quick examination. The summary of the disclosure is not intended to limit the scope in any way.

[0355] Finally, it is the applicant's intent that only claims containing the explicit language of "means" or "steps" should be interpreted under 35 USC 112. Claims that do not explicitly include the phrases "means" or "steps" should not be interpreted under 35 USC 112.

Claims

Claim 1 A method comprising: communicating with a first network node through a second network node by means of a wireless device; receiving backhaul link failure information from the second network node by means of the wireless device, indicating a failure of a wireless link established between the first network node and the second network node; determining a failure of the connection between the wireless device and the first network node based on the backhaul link failure information; and transmitting a wireless link failure report to a third network node by means of the wireless device, indicating that a backhaul link failure between the first network node and the second network node causes a failure of the connection between the wireless device and the first network node. Claim 2 A method according to claim 1, wherein the communicating step comprises: receiving, by the wireless device, at least one wireless resource control message including configuration parameters of a first cell of a second network node from a first network node through a second network node; and transmitting a packet to the second network node through the first cell by the wireless device. Claim 3 A method according to claim 1, wherein the wireless link failure report comprises at least one of: an information element indicating that a failure of the connection has occurred due to the backhaul link failure; or a cell identifier of a cell causing the failure of the wireless link, as a cell of the first network node. Claim 4 A method according to claim 1, wherein the wireless link failure report includes a cell identifier of a first cell. Claim 5 delete Claim 6 A method according to claim 1, wherein the backhaul link failure information comprises: a temporary failure; a failure of at least one of a plurality of backhaul links of the second network node; or a failure of at least one of all backhaul links of the second network node. Claim 7 A method according to claim 1, wherein the backhaul link failure information includes a cell identifier of a cell that causes a failure of the wireless link, as a cell of the first network node. Claim 8 delete Claim 9 A method according to claim 1, further comprising the step of selecting a second cell of the third network node for a wireless resource control connection based on the determination of a failure of the connection by the wireless device. Claim 10 A method according to claim 1, wherein the backhaul link failure information is received through at least one of a media access control element; a physical layer command including downlink control information; an adaptive layer indication; or a wireless resource control message. Claim 11 A method according to claim 1, further comprising the step of releasing a bearer established through the second network node in response to receiving backhaul link failure information by the wireless device. Claim 12 A method according to claim 1, further comprising the step of stopping the transmission of a scheduling request to the second network node in response to receiving the backhaul link failure information by the wireless device. Claim 13 A method according to claim 1, wherein the wireless link comprises one or more wireless links connected through one or more network nodes, and the failure of the wireless link represents a failure of at least one of the one or more wireless links. Claim 14 A method according to claim 1, further comprising: transmitting one or more random access preambles through a second cell by the wireless device; receiving a random access response for the one or more random access preambles from a third network node by the wireless device; and transmitting a wireless resource control connection request message to the third network node based on the random access response by the wireless device. Claim 15 A method according to claim 1, wherein the wireless link failure report comprises an information element indicating that the connection failure occurred due to the backhaul link failure; or at least one cell identifier of a cell that causes the failure of the wireless link established between the first network node and the second network node, as a cell of the first network node. Claim 16 A non-transient computer-readable storage medium comprising instructions, wherein the instructions, when executed by a processor, cause the processor to perform the method of any one of claims 1 through 4, 6, 7, and 9 through 15. Claim 17 A wireless device comprising one or more processors and a memory in which instructions are stored, wherein the instructions, when executed by the one or more processors, cause the wireless device to perform the method of any one of claims 1 to 4, 6, 7, and 9 to 15. Claim 18 A method comprising the step of receiving, by a third network node, a wireless link failure report from a wireless device indicating that a backhaul link failure between a first network node and a second network node causes a failure in the connection between the wireless device and the first network node through the second network node, wherein the backhaul link failure is determined by the wireless device based on backhaul link failure information transmitted to the wireless device by the second network node, and the backhaul link failure information indicates a failure in the wireless link established between the first network node and the second network node; and the step of transmitting one or more elements of the wireless link failure report to the first network node by the third network node. Claim 19 A method according to claim 18, further comprising the step of determining the first network node based on the wireless link failure report by the third network node. Claim 20 delete Claim 21 A third network node comprising: one or more processors; and a memory in which instructions are stored, wherein the instructions cause the one or more processors to perform the method of claim 18 or 19 when the instructions are executed by the one or more processors. Claim 22 delete Claim 23 delete Claim 24 delete Claim 25 delete Claim 26 delete Claim 27 delete Claim 28 delete Claim 29 delete Claim 30 delete Claim 31 delete Claim 32 delete Claim 33 delete Claim 34 delete Claim 35 delete Claim 36 delete Claim 37 delete Claim 38 delete Claim 39 delete Claim 40 delete Claim 41 delete Claim 42 delete Claim 43 delete Claim 44 delete Claim 45 delete Claim 46 delete Claim 47 delete Claim 48 delete Claim 49 delete Claim 50 delete Claim 51 delete Claim 52 delete Claim 53 delete Claim 54 delete Claim 55 delete Claim 56 delete Claim 57 delete Claim 58 delete Claim 59 delete Claim 60 delete Claim 61 delete Claim 62 delete Claim 63 delete Claim 64 delete Claim 65 delete Claim 66 delete Claim 67 delete Claim 68 delete Claim 69 delete Claim 70 delete Claim 71 delete Claim 72 delete Claim 73 delete Claim 74 delete Claim 75 delete Claim 76 delete Claim 77 delete Claim 78 delete Claim 79 delete Claim 80 delete Claim 81 delete Claim 82 delete Claim 83 delete Claim 84 delete Claim 85 delete Claim 86 delete Claim 87 delete Claim 88 delete Claim 89 delete Claim 90 delete Claim 91 delete Claim 92 delete Claim 93 delete Claim 94 delete Claim 95 delete Claim 96 delete Claim 97 delete Claim 98 delete Claim 99 delete Claim 100 delete Claim 101 delete Claim 102 delete Claim 103 delete Claim 104 delete Claim 105 delete Claim 106 delete Claim 107 delete Claim 108 delete Claim 109 delete Claim 110 delete Claim 111 delete Claim 112 delete Claim 113 delete Claim 114 delete

Images