Patent Application
20250048455
The present disclosure relates generally to communication systems, and more particularly, to link recovery associated with non-terrestrial networks (NTN).
Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.
These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.
The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. This summary neither identifies key or critical elements of all aspects nor delineates the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.
In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a wireless device such as a user equipment (UE) or component configured to receive a set of security parameters associated with one of a layer 1 (L1) link reestablishment procedure or a layer 2 (L2) link reestablishment procedure, detect a failure of a radio link at the wireless device. The apparatus may further be configured to transmit, for a network node, at least one of an L1 link recovery request or an L2 link recovery request, where at least one of the L1 link recovery request or the L2 link recovery request includes an authentication value based on the set of security parameters, and receive, based on at least one of the L1 link recovery request or the L2 link recovery request, a link recovery message.
In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a network node or network device such as a base station or component (e.g., a satellite-based distributed unit (DU)) configured to transmit, for a wireless device, a set of security parameters associated with one of an L1 link reestablishment procedure or an L2 link reestablishment procedure. The apparatus may further be configured to receive, from the wireless device experiencing a failure of a first radio link, at least one of an L1 link recovery request or an L2 link recovery request, where at least one the L1 link recovery request or the L2 link recovery request includes an authentication value based on the set of security parameters, and transmit, for the wireless device, a link recovery message associated with a reestablishment of a second radio link.
In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a network entity such as a central or centralized unit (CU) or CU component configured to output, for a network node, at least one of one or more indications of values associated with a set of security parameters associated with one of an L1 link reestablishment procedure or an L2 link reestablishment procedure or the set of security parameters and output, for a wireless device, the set of security parameters associated with one of the L1 link reestablishment procedure or the L2 link reestablishment procedure.
To the accomplishment of the foregoing and related ends, the one or more aspects may include the features hereinafter fully described and particularly pointed out in the claims. The following description and the drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.
In some aspects of wireless communication, a cell associated with an NTN cell (e.g., associated with a satellite-based base station and/or DU) may cover a (very) wide area and may be easily blocked, e.g., by buildings, tunnels, or other obstacles. Based on the wide coverage that is easily blocked, even if the UE temporarily loses contact with an NTN cell serving the UE, it may be likely that the UE will identify the same NTN cell again after passing through a blocked area. In some aspects, the UE may initiate a radio resource control (RRC) reestablishment procedure to connect to the same NTN cell. Because the RRC reestablishment procedure, in some aspects, includes RRC-level interaction (e.g., layer 3 (L3) communication) between the UE and a CU via the satellite-based base station and/or DU, the reestablishment procedure may involve long delays associated with transmissions to and from the satellite-based base station and/or DU. For example, the reestablishment procedure may, due to a radio link control (RLC) flush (e.g., a reset of RLC state or a reset of RLC parameters associated with the RLC state), involve control plane signaling and user plane retransmissions associated with a packet data convergence protocol (PDCP).
Various aspects relate generally to a novel link reestablishment for reestablishing a link with a same DU or, in some aspects, for establishing a link with a DU associated with a same CU that avoids resetting layer 3 parameters. Additionally, or alternatively, in some aspects, neither the PDCP (e.g., a state of the PDCP) or a service data adaptation protocol (SDAP) (e.g., a state of the SDAP) may be affected. For example, neither the PDCP nor the SDAP may be associated with a change in state (e.g., a change in parameters associated with a state of the PDCP or the SDAP) during the reestablishment procedure. The novel link reestablishment procedure, in some aspects, may reduce a link reestablishment time compared to an RRC reestablishment procedure associated with configuring L3 parameters, where the reduction may be larger for NTNs than for terrestrial networks. Some aspects more specifically relate to providing configuration information that may be used to enable a link reestablishment procedure that reconfigures L1 and/or L2 parameters while reusing L3 parameters (e.g., avoids configuring L3 parameters). In some examples, a CU may be configured to output, and a network node may be configured to receive, at least one of one or more indications of values associated with a set of security parameters associated with one of an L1 link reestablishment procedure or an L2 link reestablishment procedure or the set of security parameters (where the L1 and/or L2 link reestablishment, in some aspects, may not involve a change to a state of the PDCP and/or the SDAP). The CU may further be configured to output, for a wireless device, the set of security parameters associated with one of the L1 link reestablishment procedure or the L2 link reestablishment procedure. The set of security parameters, in some aspects, may be output by the CU for the DU to output for the wireless device. Accordingly, in some aspects, the DU may be configured to transmit, and the wireless device may be configured to receive, the set of security parameters associated with one of the L1 link reestablishment procedure or the L2 link reestablishment procedure. The wireless device may be configured to detect a radio link failure. Based on detecting the radio link failure, the wireless device may be configured to transmit, and the DU may be configured to receive, at least one of an L1 link recovery request or an L2 link recovery request. In some aspects, the at least one of the L1 link recovery request or the L2 link recovery request may include an authentication value based on the set of security parameters. In some aspects, the DU may be configured to verify, based on the authentication value, that at least one of the L1 link recovery request or the L2 link recovery request is valid. To verify that the at least one of the L1 link recovery request or the L2 link recovery request is valid, in some aspects, the DU may be configured to determine that the authentication value included in at least one of the L1 link recovery request or the L2 link recovery request matches a locally-stored authentication value. In some aspects, to verify that the at least one of the L1 link recovery request or the L2 link recovery request is valid, the DU may be configured to transmit, and the CU may be configured to receive, a verification request including the authentication value. Based on the verification request, the CU may be configured to output, and the DU may be configured to receive, a verification response verifying that the authentication value is valid. Based on verifying that at least one of the L1 link recovery request or the L2 link recovery request is valid, the DU may be configured to transmit, and the wireless device may be configured to receive, a link recovery message associated with a reestablishment of a second radio link.
Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by using the novel L1 link reestablishment procedure and/or the L2 link reestablishment procedure, the described techniques can be used to reduce a latency associated with link reestablishment and/or recovery, especially associated with an NTN.
The detailed description set forth below in connection with the drawings describes various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.
Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements”). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.
By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. When multiple processors are implemented, the multiple processors may perform the functions individually or in combination. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoC), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.
Accordingly, in one or more example aspects, implementations, and/or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, such computer-readable media can include a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.
While aspects, implementations, and/or use cases are described in this application by illustration to some examples, additional or different aspects, implementations and/or use cases may come about in many different arrangements and scenarios. Aspects, implementations, and/or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, implementations, and/or use cases may come about via integrated chip implementations and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described examples may occur. Aspects, implementations, and/or use cases may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques herein. In some practical settings, devices incorporating described aspects and features may also include additional components and features for implementation and practice of claimed and described aspect. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor(s), interleaver, adders/summers, etc.). Techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc. of varying sizes, shapes, and constitution.
Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent parts. In a 5G NR system, or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment, such as a base station (BS), or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), a transmission reception point (TRP), or a cell, etc.) may be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a disaggregated base station.
An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among two or more units (such as one or more CUs, one or more distributed units (DUs), or one or more radio units (RUs)). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU can be implemented as virtual units, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).
Base station operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as the network configuration sponsored by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Disaggregation may include distributing functionality across two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.
In some aspects, the CU 110 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), or the like. Each control function can be implemented with an interface configured to communicate signals with other control functions hosted by the CU 110. The CU 110 may be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 110 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as an E1 interface when implemented in an O-RAN configuration. The CU 110 can be implemented to communicate with the DU 130, as necessary, for network control and signaling.
The DU 130 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 140. In some aspects, the DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, or the like) depending, at least in part, on a functional split, such as those defined by 3GPP. In some aspects, the DU 130 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 130, or with the control functions hosted by the CU 110.
Lower-layer functionality can be implemented by one or more RUs 140. In some deployments, an RU 140, controlled by a DU 130, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like), or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU(s) 140 can be implemented to handle over the air (OTA) communication with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU(s) 140 can be controlled by the corresponding DU 130. In some scenarios, this configuration can enable the DU(s) 130 and the CU 110 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
The SMO Framework 105 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements that may be managed via an operations and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO Framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements can include, but are not limited to, CUs 110, DUs 130, RUs 140 and Near-RT RICs 125. In some implementations, the SMO Framework 105 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 111, via an O1 interface. Additionally, in some implementations, the SMO Framework 105 can communicate directly with one or more RUs 140 via an O1 interface. The SMO Framework 105 also may include a Non-RT RIC 115 configured to support functionality of the SMO Framework 105.
The Non-RT RIC 115 may be configured to include a logical function that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI)/machine learning (ML) (AI/ML) workflows including model training and updates, or policy-based guidance of applications/features in the Near-RT RIC 125. The Non-RT RIC 115 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 125. The Near-RT RIC 125 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 110, one or more DUs 130, or both, as well as an O-eNB, with the Near-RT RIC 125.
In some implementations, to generate AI/ML models to be deployed in the Near-RT RIC 125, the Non-RT RIC 115 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 125 and may be received at the SMO Framework 105 or the Non-RT RIC 115 from non-network data sources or from network functions. In some examples, the Non-RT RIC 115 or the Near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the Non-RT RIC 115 may monitor long-term trends and patterns for performance and employ AI/ML models to perform corrective actions through the SMO Framework 105 (such as reconfiguration via 01) or via creation of RAN management policies (such as A1 policies).
At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Accordingly, a base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component indicated with dotted lines to signify that each component may or may not be included in the base station 102). The base station 102 provides an access point to the core network 120 for a UE 104. The base station 102 may include macrocells (high power cellular base station) and/or small cells (low power cellular base station). The small cells include femtocells, picocells, and microcells. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs), which may provide service to a restricted group known as a closed subscriber group (CSG). The communication links between the RUs 140 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to an RU 140 and/or downlink (DL) (also referred to as forward link) transmissions from an RU 140 to a UE 104. The communication links may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be through one or more carriers. The base station 102/UEs 104 may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell).
Certain UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL/UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be through a variety of wireless D2D communications systems, such as for example, Bluetooth™ (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG)), Wi-Fi™ (Wi-Fi is a trademark of the Wi-Fi Alliance) based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.
The wireless communications system may further include a Wi-Fi AP 150 in communication with UEs 104 (also referred to as Wi-Fi stations (STAs)) via communication link 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the UEs 104/AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.
The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHZ-7.125 GHZ) and FR2 (24.25 GHZ-52.6 GHZ). Although a portion of FR1 is greater than 6 GHZ, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHZ-300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHZ-24.25 GHZ). Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHZ-71 GHZ), FR4 (71 GHZ-124.25 GHZ), and FR5 (114.25 GHZ-300 GHz). Each of these higher frequency bands falls within the EHF band.
With the above aspects in mind, unless specifically stated otherwise, the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHZ, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and/or FR5, or may be within the EHF band.
The base station 102 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and/or antenna arrays to facilitate beamforming. The base station 102 may transmit a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also transmit a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102/UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 102/UE 104. The transmit and receive directions for the base station 102 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.
The base station 102 may include and/or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP, network node, network entity, network equipment, or some other suitable terminology. The base station 102 can be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and an RU, or as a disaggregated base station including one or more of a CU, a DU, and/or an RU. The set of base stations, which may include disaggregated base stations and/or aggregated base stations, may be referred to as next generation (NG) RAN (NG-RAN).
The core network 120 may include an Access and Mobility Management Function (AMF) 161, a Session Management Function (SMF) 162, a User Plane Function (UPF) 163, a Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. The AMF 161 is the control node that processes the signaling between the UEs 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identification handling, access authorization, and subscription management. The one or more location servers 168 are illustrated as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, the one or more location servers 168 may include one or more location/positioning servers, which may include one or more of the GMLC 165, the LMF 166, a position determination entity (PDE), a serving mobile location center (SMLC), a mobile positioning center (MPC), or the like. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients/applications (e.g., emergency services) for accessing UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to compute the position of the UE 104. The NG-RAN may utilize one or more positioning methods in order to determine the position of the UE 104. Positioning the UE 104 may involve signal measurements, a position estimate, and an optional velocity computation based on the measurements. The signal measurements may be made by the UE 104 and/or the base station 102 serving the UE 104. The signals measured may be based on one or more of a satellite positioning system (SPS) 170 (e.g., one or more of a Global Navigation Satellite System (GNSS), global position system (GPS), non-terrestrial network (NTN), or other satellite position/location system), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR enhanced cell ID (NR E-CID) methods, NR signals (e.g., multi-round trip time (Multi-RTT), DL angle-of-departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle-of-arrival (UL-AoA) positioning), and/or other systems/signals/sensors.
Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor/actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc.). The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices such as in a device constellation arrangement. One or more of these devices may collectively access the network and/or individually access the network.
Referring again to
For normal CP (14 symbols/slot), different numerologies μ 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For extended CP, the numerology 2 allows for 4 slots per subframe. Accordingly, for normal CP and numerology μ, there are 14 symbols/slot and 2μ slots/subframe. The subcarrier spacing may be equal to 2μ*15 kHz, where μ is the numerology 0 to 4. As such, the numerology μ=0 has a subcarrier spacing of 15 kHz and the numerology μ=4 has a subcarrier spacing of 240 kHz. The symbol length/duration is inversely related to the subcarrier spacing.
A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs)) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.
As illustrated in
As illustrated in
The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a respective spatial stream for transmission.
At the UE 350, each receiver 354Rx receives a signal through its respective antenna 352. Each receiver 354Rx recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller/processor 359, which implements layer 3 and layer 2 functionality.
The controller/processor 359 can be associated with at least one memory 360 that stores program codes and data. The at least one memory 360 may be referred to as a computer-readable medium. In the UL, the controller/processor 359 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets. The controller/processor 359 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
Similar to the functionality described in connection with the DL transmission by the base station 310, the controller/processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a respective spatial stream for transmission.
The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318Rx receives a signal through its respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to a RX processor 370.
The controller/processor 375 can be associated with at least one memory 376 that stores program codes and data. The at least one memory 376 may be referred to as a computer-readable medium. In the UL, the controller/processor 375 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets. The controller/processor 375 is also responsible for error detection using an ACK and/or NACK protocol to support HARQ operations.
At least one of the TX processor 368, the RX processor 356, and the controller/processor 359 may be configured to perform aspects in connection with the fast link recovery for NTN component 198 of
At least one of the TX processor 316, the RX processor 370, and the controller/processor 375 may be configured to perform aspects in connection with the fast link recovery for NTN component 199 of
In some examples, a UE may communicate with a terrestrial network. In the illustrated example of
In some examples, a UE may transmit or receive communication via an NTN. As an example, the UE may transmit or receive satellite-based communication (e.g., via an Iridium-like satellite communication system or a satellite-based 3GPP NTN). For example, an aerial device 422 may provide coverage to one or more UEs, such as an example UE 404, located within a coverage area 420 for the aerial device 422. In some examples, the aerial device 422 may communicate with the network node 406 through a feeder link 426 established between the aerial device 422 and a gateway 428 in order to provide service to the UE 404 within the coverage area 420 of the aerial device 422 via a service link 430. The UE 404 may be within the coverage area 420 and the coverage area 410. The feeder link 426 may include a wireless link between the aerial device 422 and the gateway 428. The service link 430 may include a wireless link between the aerial device 422 and the UE 404. In some examples, the gateway 428 may communicate directly with the network node 406. In some examples, the gateway 428 may communicate with the network node 406 via the base station 402.
In some aspects, the aerial device 422 may be configured to communicate directly with the gateway 428 via the feeder link 426. The feeder link 426 may include a radio link that provides wireless communication between the aerial device 422 and the gateway 428.
In some aspects, the aerial device 422 may communicate with the gateway 428 via one or more other aerial devices. For example, the aerial device 422 and a second aerial device (not shown) may be part of a constellation of satellites (e.g., aerial devices) that communicate via inter-satellite links (ISLs). For example, the aerial device 422 may establish an ISL with the second aerial device. The ISL may be a radio interface or an optical interface and operate in the RF frequency or optical bands, respectively. The second aerial device may communicate with the gateway 428 via a second feeder link, similarly as the aerial device 422 communicates with the gateway 428.
In some examples, the aerial device 422 and/or the second aerial device may include an aerial device, such as, but not limited to, an unmanned aircraft system (UAS), a balloon, a drone, an unmanned aerial vehicle (UAV), or the like. Examples of a UAS platform that may be used for NTN communication include systems including Tethered UAS (TUAS), Lighter Than Air UAS (LTA), Heavier Than Air UAS (HTA), and High Altitude Platforms (HAPs). In some examples, the aerial device 422 and/or the second aerial device may include a satellite or a space-borne vehicle placed into Low-Earth Orbit (LEO), Medium-Earth Orbit (MEO), Geostationary Earth Orbit (GEO), or High Elliptical Orbit (HEO).
In some aspects, the aerial device 422 and/or the second aerial device may implement a transparent payload (sometimes referred to as a “bent pipe” payload). For example, after receiving a signal, a transparent aerial device may have the ability to change the frequency carrier of the signal, perform RF filtering on the signal, and amplify the signal before outputting the signal. In such aspects, the signal output by the transparent aerial device may be a repeated signal in which the waveform of the output signal is unchanged relative to the received signal.
In other aspects, the aerial device 422 and/or the second aerial device may implement a regenerative payload (e.g., associated with a DU). For example, a regenerative aerial device may have the ability to perform all of, or part of, the base station functions, such as transforming and amplifying a received signal via on-board processing before outputting a signal. In some such aspects, transformation of the received signal may refer to digital processing that may include demodulation, decoding, switching and/or routing, re-encoding, re-modulation, and/or filtering of the received signal.
In examples in which the aerial device implements a transparent payload, the transparent aerial device may communicate with the base station 402 via the gateway 428. In some such examples, the base station 402 may facilitate communication between the gateway 428 and the network node 406. In examples in which the aerial device implements a regenerative payload, the regenerative aerial device may have an on-board base station. In some such examples, the on-board base station may communicate with the network node 406 via the gateway 428. In some examples, the on-board base station may include a DU and a CU, such as the DU 130 and the CU 110 of
The network architecture 500 of
The base station 506 may be a network node that corresponds to the network node 406 of
Permitted connections in the network architecture 500 with transparent payloads illustrated in
The UE 505 is configured to communicate with the core network 510 via the NTN device 502, the NTN gateway 504, and the base station 506. As illustrated by the RAN 512, one or more RANs associated with the core network 510 may include one or more base stations. Access to the network may be provided to the UE 505 via wireless communication between the UE 505 and the base station 506 (e.g., a serving base station), via the NTN device 502 and the NTN gateway 504. The base station 506 may provide wireless communications access to the core network 510 on behalf of the UE 505, e.g., using 4G NR.
The base station 506 may be referred to by other names such as a gNB, a “satellite node,” a satellite NodeB (sNB), “satellite access node,” etc. The base station 506 may not be the same as terrestrial network gNBs, but may be based on a terrestrial network gNB with additional capability. For example, the base station 506 may terminate the radio interface and associated radio interface protocols to the UE 505 and may transmit DL signals to the UE 505 and receive UL signals from the UE 505 via the NTN device 502 and the NTN gateway 504. The base station 506 may also support signaling connections and voice and data bearers to the UE 505 and may support handover of the UE 505 between different radio cells for the NTN device 502, between different NTN devices and/or between different base stations. The base station 506 may be configured to manage moving radio beams (e.g., for airborne vehicles and/or non-geostationary (non-GEO) devices) and associated mobility of the UE 505. The base station 506 may assist in the handover (or transfer) of the NTN device 502 between different NTN gateways or different base stations. In some examples, the base station 506 may be separate from the NTN gateway 504, e.g., as illustrated in the example of
The NTN gateway 504 may be shared by more than one base station and may communicate with the UE 505 via the NTN device 502. The NTN gateway 504 may be dedicated to one associated constellation of NTN devices. The NTN gateway 504 may be included within the base station 506, e.g., as a base station-DU within the base station 506. The NTN gateway 504 may communicate with the NTN device 502 using control and user plane protocols. The control and user plane protocols between the NTN gateway 504 and the NTN device 502 may: (i) establish and release the NTN gateway 504 to the NTN device 502 communication links, including authentication and ciphering; (ii) update NTN device software and firmware; (iii) perform NTN device Operations and Maintenance (O&M); (iv) control radio beams (e.g., direction, power, on/off status) and mapping between radio beams and NTN gateway UL and DL payload; and/or (v) assist with handoff of the NTN device 502 or radio cell to another NTN gateway.
Support of transparent payloads with the network architecture 500 shown in
In the illustrated example of
An on-board base station may perform many of the same functions as the base station 506 as described previously. For example, the NTN device 502/base station may terminate the radio interface and associated radio interface protocols to the UE 505 and may transmit DL signals to the UE 505 and receive UL signals from the UE 505, which may include encoding and modulation of transmitted signals and demodulation and decoding of received signals. The NTN device 502/base station may also support signaling connections and voice and data bearers to the UE 505 and may support handover of the UE 505 between different radio cells for the NTN device 502/base station and between or among different NTN device/base stations. The NTN device 502/base station may assist in the handover (or transfer) of the UE 505 between different NTN gateways and different control networks. The NTN device 502/base station may hide or obscure specific aspects of the NTN device 502/base station from the core network 510, e.g., by interfacing to the core network 510 in the same way or in a similar way to a terrestrial network base station. The NTN device 502/base station may further assist in sharing of the NTN device 502/base station. The NTN device 502/base station may communicate with one or more NTN gateways and with one or more core networks via the NTN gateway 504. In some aspects, the NTN device 502/base station may communicate directly with other NTN device/base stations using Inter-Satellite Links (ISLs), which may support an Xn interface between any pair of NTN device/base stations.
With low Earth orbit (LEO) devices, the NTN device 502/base station may manage moving radio cells with coverage at different times. The NTN gateway 504 may be connected directly to the core network 510, as illustrated. The NTN gateway 504 may be shared by multiple core networks, for example, if NTN gateways are limited. In some examples the core network 510 may be aware of coverage area(s) of the NTN device 502/base station in order to page the UE 505 and to manage handover. Thus, as can be seen, the network architecture 525 with regenerative payloads may have more impact and complexity with respect to both the NTN device 502/base station and the core network 510 than the network architecture 500 including transparent payloads, as shown in
Support of regenerative payloads with the network architecture 525 shown in
In the illustrated example of
The NTN-DU 514 communicates with the NTN-CU 516 via the NTN gateway 504. The NTN-CU 516 together with the NTN-DU 514 perform functions, and may use internal communication protocols, which are similar to, or the same as, a gNB with a split architecture. In the example, the NTN-DU 514 may correspond to and perform functions similar to, or the same as, a gNB Distributed Unit (gNB-DU), while the NTN-CU 516 may correspond to and perform functions similar to, or the same as, a gNB Central Unit (gNB-CU). However, the NTN-CU 516 and the NTN-DU 514 may each include additional capability to support the UE 505 access using NTN devices.
The NTN-DU 514 and the NTN-CU 516 may communicate with one another using an F1 Application Protocol (F1AP), and together may perform some or all of the same functions as the base station 506 or the NTN device 502/base station as described in connection with
The NTN-DU 514 may terminate the radio interface and associated lower level radio interface protocols to the UE 505 and may transmit DL signals to the UE 505 and receive UL signals from the UE 505, which may include encoding and modulation of transmitted signals and demodulation and decoding of received signals. The operation of the NTN-DU 514 may be partly controlled by the NTN-CU 516. The NTN-DU 514 may support one or more NR radio cells for the UE 505. The NTN-CU 516 may also be split into separate control plane (CP) (NTN-CU-CP) and user plane (UP) (NTN-CU-UP) portions. The NTN-DU 514 and the NTN-CU 516 may communicate over an F1 interface to (a) support control plane signaling for the UE 505 using IP. Stream Control Transmission Protocol (SCTP) and F1 Application Protocol (F1AP) protocols, and (b) to support user plane data transfer for a UE using IP, User Datagram Protocol (UDP), PDCP, SDAP. GTP-U and NR User Plane Protocol (NRUPP) protocols.
The NTN-CU 516 may communicate with one or more other NTN-CUs and/or with one more other terrestrial base stations using terrestrial links to support an Xn interface between any pair of NTN-CUs and/or between the NTN-CU 516 and any terrestrial base station.
The NTN-DU 514 together with the NTN-CU 516 may: (i) support signaling connections and voice and data bearers to the UE 505; (ii) support handover of the UE 505 between different radio cells for the NTN-DU 514 and between different NTN-DUs; and (iii) assist in the handover (or transfer) of NTN devices between different NTN gateways or different core networks. The NTN-CU 516 may hide or obscure specific aspects of the NTN devices from the core network 510, e.g., by interfacing to the core network 510 in the same way or in a similar way to a terrestrial network base station.
In the network architecture 550 of
Support of regenerative payloads with a split base station architecture, as shown in
In some aspects of wireless communication, a cell associated with an NTN cell (e.g., associated with a satellite-based base station and/or DU) may cover a (very) wide area and may be easily blocked, e.g., by buildings, tunnels, or other obstacles. Based on the wide coverage that is easily blocked, even if the UE temporarily loses contact with an NTN cell serving the UE, it may be likely that the UE will identify the same NTN cell again after passing through a blocked area. In some aspects, the UE may initiate an RRC reestablishment procedure to connect to the same NTN cell. Because the RRC reestablishment procedure, in some aspects, includes RRC-level interaction (e.g., L3 communication) between the UE and a CU via the satellite-based base station and/or DU, the reestablishment procedure may involve long delays associated with transmissions to and from the satellite-based base station and/or DU. For example, the reestablishment procedure may, due to an RLC flush (e.g., a reset of RLC parameters), involve control plane signaling and user plane retransmissions associated with a PDCP due
Various aspects relate generally to a novel link reestablishment for reestablishing a link with a same DU or, in some aspects, for establishing a link with a DU associated with a same CU that avoids resetting L3 parameters. The novel link reestablishment procedure, in some aspects, may reduce a link reestablishment time compared to an RRC reestablishment procedure associated with configuring L3 parameters, where the reduction may be larger for NTNs than for terrestrial networks. Some aspects more specifically relate to providing configuration information that may be used to enable a link reestablishment procedure that avoids configuring L3 parameters. In some examples, a CU may be configured to output, and a network node may be configured to receive, at least one of one or more indications of values associated with a set of security parameters associated with one of an L1 link reestablishment procedure or an L2 link reestablishment procedure or the set of security parameters. The CU may further be configured to output, for a wireless device, the set of security parameters associated with one of the L1 link reestablishment procedure or the L2 link reestablishment procedure. The set of security parameters, in some aspects, may be output by the CU for the DU to output for the wireless device. Accordingly, in some aspects, the DU may be configured to transmit, and the wireless device may be configured to receive, the set of security parameters associated with one of the L1 link reestablishment procedure or the L2 link reestablishment procedure. The wireless device may be configured to detect a radio link failure. Based on detecting the radio link failure, the wireless device may be configured to transmit, and the DU may be configured to receive, at least one of an L1 link recovery request or an L2 link recovery request. In some aspects, the at least one of the L1 link recovery request or the L2 link recovery request may include an authentication value based on the set of security parameters. In some aspects, the DU may be configured to verify, based on the authentication value, that at least one of the L1 link recovery request or the L2 link recovery request is valid. To verify that the at least one of the L1 link recovery request or the L2 link recovery request is valid, in some aspects, the DU may be configured to determine that the authentication value included in at least one of the L1 link recovery request or the L2 link recovery request matches a locally-stored authentication value. In some aspects, to verify that the at least one of the L1 link recovery request or the L2 link recovery request is valid, the DU may be configured to transmit, and the CU may be configured to receive, a verification request including the authentication value. Based on the verification request, the CU may be configured to output, and the DU may be configured to receive, a verification response verifying that the authentication value is valid. Based on verifying that at least one of the L1 link recovery request or the L2 link recovery request is valid, the DU may be configured to transmit, and the wireless device may be configured to receive, a link recovery message associated with a reestablishment of a second radio link.
The UE 604, in some aspects, may initially operate in the coverage area 631 associated with a first cell and connect, via a first radio link, to the first cell associated with the first satellite-based DU 622 (or similar terrestrial DU). Based on a change to the environment (e.g., a movement of any of the UE 604, the first satellite-based DU 622, or one or more intervening objects), the first radio link may fail and the UE 604 may identify a cell for reestablishing a radio link to the network. The identified cell, in some aspects, may be based on one or more characteristics of the identified cells and other candidate cells and may be one of the first cell, the second cell, or an additional cell associated with the first satellite-based DU 622 or the second satellite-based DU 642 (or one of a set of cells associated with one or more RUs and/or DUs associated with a same CU of a similarly-configured TN or a network including both terrestrial and non-terrestrial components). The fast link recovery procedure (e.g., the L1 link reestablishment procedure and/or the L2 link reestablishment procedure) may then be used to more quickly reestablish a connection with the identified cell (and ultimately with the network entity 606 (e.g., a CU associated with the first cell and the identified cell). While
In some aspects, the CU 701, the first DU 702, and/or the UE 704 may exchange one or more indications 706 regarding a capability of the UE 704, the first DU 702, and/or the CU 701 to participate in a fast link recovery procedure. For example, the capability may be indicated at a plurality of granularities (e.g., per any unit). For example, the exchange one or more indications 706 may indicate a capability to participate in the fast link recovery procedure per UE (e.g., for a single UE such as UE 704, or for a plurality of UEs), per band, per band combination, per feature set, per RAT, per orbit, per system (TN, NTN), per 3GPP release. Such capability may be updated based on the state of the UE 704, the first DU 702, the second DU 703, and/or the CU 701. Based on a capability of each of the CU 701, the first DU 702, and the UE 704 to participate in (or use) the fast link recovery procedure indicated by the one or more indications 706, the CU 701, in some aspects, may transmit, and the first DU 702 and the second DU 703 may receive, information for the fast link recovery procedure (e.g., DU L1/L2 recovery configuration messages 708). The information for the fast link recovery procedure, in some aspects, may include (1) one or more indications of values associated with a set of security parameters associated with one of an L1 link reestablishment procedure or an L2 link reestablishment procedure or (2) the set of security parameters. In some aspects, the DU L1/L2 recovery configuration messages 708 may include response messages from the first DU 702 and the second DU 703. For example, the information for, or associated with, the fast link recovery procedure, in some aspects, may include one or more of an ID of the UE 704 such as a cell radio network temporary ID (C-RNTI) (e.g., assigned by a PCell associated with the DU L1/L2 recovery configuration messages 708), a tunnel endpoint ID (TEID), a source PCI, a satellite ID (or other data, e.g., an ephemeris, for identifying a satellite), at least one value used for a calculation of an authentication value, a security algorithm associated with at least one of the L1 link reestablishment procedure or the L2 link reestablishment procedure, L2 security parameters, or a duration for which the set of security parameters is valid.
In some aspects, the information for the fast link recovery procedure included in the DU L1/L2 recovery configuration messages 708, in some aspects, may relate to a MAC-I value used for the fast link recovery procedure.
In some aspects, the CU 701 may transmit, and the UE 704 may receive (e.g., via the first DU 702), information for the fast link recovery procedure (e.g., UE L1/L2 recovery configuration messages 710). The information for the fast link recovery procedure, in some aspects, may include a set of security parameters associated with at least one of an L1 link reestablishment procedure or an L2 link reestablishment procedure. In some aspects, the UE L1/L2 recovery configuration messages 710 may include response messages from the UE 704. For example, the information for, or associated with, the fast link recovery procedure, in some aspects, may include one or more of an ID of the UE 704, a cell radio network temporary ID (C-RNTI) (e.g., assigned by a PCell associated with the UE L1/L2 recovery configuration messages 710), a tunnel endpoint ID (TEID), a source PCI, at least one value (or algorithm) used for a calculation of an authentication value, a security algorithm associated with at least one of the L1 link reestablishment procedure or the L2 link reestablishment procedure, L2 security parameters (e.g., a MAC-I), or a duration for which the set of security parameters is valid. In some aspects, the UE L1/L2 recovery configuration messages 710 or other configuration messages may include a DU ID via one of system information or dedicated signaling. The DU ID, in some aspects, may be provided either explicitly or implicitly. For example, for explicit indication, the identity value can be included. For implicit indication, the UE 704 may receive position information including a DU ID as described below in relation to
The UE 704, at 712, may detect (and identify a reason for) a radio link failure and identify a (new) cell for a link reestablishment. The cell, in some aspects, may be the same (first) cell, a different cell associated with the first DU 702, or a cell associated with the second DU 703. As part of identifying the cell for the link reestablishment at 712, the UE 704 may determine that the new cell (e.g., the new cell identified at 712) is configured to use the fast link recovery procedure (e.g., is associated with the CU 701, the first DU 702, a satellite associated with the first DU 702, etc.). Based on the determination that the new cell is configured to use the fast link recovery procedure, the UE 704 may transmit, and the first DU 702 or the second DU 703 may receive, respectively, one of an L1/L2 recovery request 714A or an L1/L2 recovery request 714B (e.g., at least one of an L1 recovery request or an L2 recovery request) associated with the fast link recovery procedure.
The L1/L2 recovery request 714A or the L1/L2 recovery request 714B, in some aspects, may include an authentication value (e.g., a MAC-I value). In some aspects, the L1/L2 recovery request 714A or the L1/L2 recovery request 714B may include one or more of the ID of the UE 704, the C-RNTI, the TEID, the MAC-I value, a cause value indicating a type of failure associated with the failure of the radio link (e.g., T310 expiry, RACH failure, RLC failure, handover (HO) failure, etc.), an ID of a network node (e.g., the first DU 702 or the second DU 703 associated with at least one of the first radio link or the new cell), or an ID of a network entity (e.g., the CU 701) associated with the network node. In some aspects, the L1/L2 recovery request 714A or the L1/L2 recovery request 714B may be sent with a logical channel ID (LCID) that may be associated with (or identify the L1/L2 recovery request 714A or the L1/L2 recovery request 714B as being associated with) the fast link recovery procedure. In some aspects, the L1/L2 recovery request 714A or the L1/L2 recovery request 714B may sent with a RNTI that may be associated with (or identify the L1/L2 recovery request 714A or the L1/L2 recovery request 714B as being associated with) the fast link recovery procedure. In some aspects, the L1/L2 recovery request 714A or the L1/L2 recovery request 714B may trigger transmission of specific resources such as PRACH that may be associated with (or identify the L1/L2 recovery request 714A or the L1/L2 recovery request 714B as being associated with) the fast link recovery procedure.
To improve the security of the fast link recovery procedure, in some aspects, the authentication value (e.g., the MAC-I value) may be configured to be different for different L1/L2 recovery requests. In some aspects, the authentication value may be calculated based on one or more of a security key (or security key related parameter, e.g., a DU counter provided to, or known at, a DU and a UE related to the fast link recovery procedure), and/or data stream-specific information (e.g., a COUNT value, a BEARER value, and/or a DIRECTION value) for each L1/L2 recovery request (e.g., the L1/L2 recovery request 714A or the L1/L2 recovery request 714B). In some aspects, the network, e.g., the CU 701 and/or one of the first DU 702 or the second DU 703, may provide a set of new values (e.g., at least a subset of the information and/or parameters for the fast link recovery procedure) after an L1/L2 recovery request (e.g., as part of resuming the user plane communication at 720 and exchanging, and/or participating in, communication 722) to be used for a subsequent L1/L2 recovery request.
The set of new values and/or parameters, in some aspects, may be maintained in one of more of the CU 701, the first DU 702, and the second DU 703. If the set of new values and/or parameters is maintained at the CU 701, it may provide the first DU 702 and/or the second DU 703, with the new value or calculated MAC-I based on the new value and configure the UE 704 with the set of new values and/or parameters. In some aspects, the UE 704 and the network (e.g., the CU 701, the first DU 702, and the second DU 703) may use a configured (implicit) rule to derive the values used for an L1/L2 recovery request (e.g., the L1/L2 recovery request 714A or the L1/L2 recovery request 714B or for a subsequent L1/L2 recovery request). In some aspects, a first L1/L2 recovery request (e.g., the L1/L2 recovery request 714A or the L1/L2 recovery request 714B) may be based on a set of values (or security parameters) provided in the DU L1/L2 recovery configuration messages 708 and/or the UE L1/L2 recovery configuration messages 710 with subsequent L1/L2 recovery requests based on the configured rules. The configured rule, in some aspects, may (after one or more of a successfully, or unsuccessfully, completed recovery requests) indicate for the UE 704 and at least one associated DU (e.g., the first DU 702 and/or the second DU 703) to change, e.g., to increment, a current value (e.g., a value received by the UE 704 via the UE L1/L2 recovery configuration messages 710 used for the L1/L2 recovery request 714A or the L1/L2 recovery request 714B).
In some aspects, transmitting at least one of the L1 link recovery request or the L2 link recovery request (e.g., the L1/L2 recovery request 714A or the L1/L2 recovery request 714B) may include transmitting at least one of the L1 link recovery request or the L2 link recovery request to the new cell based on the determination that the new cell is associated with the CU or a CU sharing a same set of security parameters as the CU (or, generally, that the fast link recovery procedure is possible and/or enabled for the cell identified at 712). Determining that the fast link recovery procedure is possible for the cell identified at 712 (e.g., that the new cell is associated with the CU 701, the first DU 702, the satellite associated with the first DU 702, or the first cell), in some aspects, may include determining at least one of (1) that the new cell is associated with the CU 701 (e.g., with the second DU 703 as an example of any of a plurality of additional DUs (not shown), associated with the CU 701 or a similar CU sharing and/or using a same set of security parameters), (2) that the new cell is associated with the satellite associated with the first DU 702, (3) that the new cell is associated with the first DU 702, or (4) that the new cell belongs to a set of cells configured for at least one of the L1 link reestablishment procedure or the L2 link reestablishment procedure. In some aspects, the set of cells may be a configured set of cells indicated in the UE L1/L2 recovery configuration messages 710 received by the UE 704 as discussed above. The set of cells, in some aspects, may include at least one cell associated with each of the first satellite-based DU and an additional DU (e.g., a plurality of DUs associated with at least one of a same CU or one or more CUs (or network nodes) sharing a set of security parameters with the CU associated with the failed radio link) such as a set of cells associated with at least the first DU 702 and the second DU 703 that are associated with CU 701. In some aspects, the new cell may be associated with one of the first satellite-based DU and the additional DU (e.g., an additional DU configured for at least one of the L1 link reestablishment procedure or the L2 link reestablishment procedure in relation to the failed radio link). The determination that the new cell is associated with the CU 701, in some aspects, may be based on an ID of the CU associated with the first cell (e.g., a BS-CU ID 866 included in a CGI 860 associated with the first cell). In some aspects, the determination that the new cell is associated with the first satellite may be based on an ID of the first satellite associated with the first cell and associated with the new cell. The determination that the new cell is associated with the first DU 702 may be based on a DU ID included in one of a system information or a dedicated indication (e.g., included in the UE L1/L2 recovery configuration messages 710).
In some aspects, whether the L1/L2 recovery request 714A or the L1/L2 recovery request 714B includes an L1 link recovery request and/or an L2 link recovery request may be based on the new cell and whether any of the L1 or L2 parameters are able to be reused by the UE 704 for the new (e.g., reestablished) link. For example, an L2 recovery request may be able to reuse L1 (and/or some L2) parameters (if the new cell is the same cell associated with the failed radio link). The L1/L2 recovery request 714A or the L1/L2 recovery request 714B, in some aspects, may be associated with one or more of an RLC layer, a MAC layer, or a PHY layer. For example, the L1/L2 recovery request 714A or the L1/L2 recovery request 714B may be associated with one or more aspects of L1/L2 handling including a full or partial reset of MAC parameters (where a partial MAC reset may allow the UE 704 to retain an L1 configuration when reconnecting to a same cell), a suspension or resetting of timers associated with RLC, a canceling and/or suspension of a triggered behavior associated with RLC (e.g., RLC status reporting and/or RLC polling transmission), and/or a suspension of PDCP. A partial MAC reset, in some aspects, may reduce overhead associated with signaling new L1 and MAC configurations allow the UE 704 to retain (e.g., continue to use) PUCCH resources for scheduling requests and UCI. In some aspects, the L1/L2 recovery request 714A or the L1/L2 recovery request 714B may not impact one or more of the RLC or the PDCP and/or the SDAP.
Based on the L1/L2 recovery request 714A or the L1/L2 recovery request 714B, the first DU 702 or the second DU 703, respectively, may verify, at 716, that the recovery request is valid. In some aspects, the verification at 716 includes determining that the authentication value (e.g., a MAC-I) included in at least one of the L1 link recovery request or the L2 link recovery request is valid. To verify the validity of the recovery request at 716, in some aspects, one of the first DU 702 or the second DU 703 (e.g., a DU associated with the new cell identified at 712) may transmit, and the CU 701 may receive, a MAC-I request 716A including the authentication value (e.g., the MAC-I) received from the UE 704 to be verified by the CU 701. In response to the MAC-I request 716A, the CU 701 may verify, at 716B, the authentication value (e.g., the MAC-I). The verification at 716B, in some aspects, may include comparing the received authentication value to one of an authentication value stored at the CU 701 or to an authentication value calculated at CU 701 based on the MAC-I request 716A to determine if they are the same. Based on the verification at 716B, the CU 701 may transmit, and one of the first DU 702 or the second DU 703 (e.g., the DU associated with the new cell identified at 712 and/or having transmitted the MAC-I request 716A) may receive, a MAC-I result 716C indicating the results of the verification at 716B. If the authentication value is indicated to be the same in MAC-I result 716C, the first DU 702 or the second DU 703 (e.g., the DU associated with the new cell identified at 712 and/or having received the MAC-I result 716C), may verify, at 716D, the authentication value.
In some aspects, the verification at 716D may be performed by one of the first DU 702 or the second DU 703 (e.g., the DU associated with the new cell identified at 712) independently of the CU 701. The independent verification at 716D, in some aspects, may be based on the L1/L2 recovery request 714A or the L1/L2 recovery request 714B instead of the MAC-I result 716C. In some aspects for which the DU verifies the authentication value independently at 716D (e.g., without the transmission of MAC-I request 716A, the verification at 716B, or the MAC-I result 716C to the CU 701), the CU 701 may not transmit the information for the fast link recovery procedure in the DU L1/L2 recovery configuration messages 708 and the security parameters may be negotiated and/or indicated between the DU (e.g., the first DU 702 or the second DU 703) and the UE 704 within the UE L1/L2 recovery configuration messages 710. The independent verification at 716D, in some aspects, may include comparing the authentication value received in the L1/L2 recovery request 714A or the L1/L2 recovery request 714B to an authentication value stored at, or calculated by, the DU (e.g., the first DU 702 or the second DU 703 associated with the new cell identified at 712) to determine if they are the same. Based on the verification at 716D, the DU (e.g., the first DU 702 or the second DU 703 associated with verification at 716D) may transmit, and the UE 704 may receive, one of the L1/L2 recovery message 718A or the L1/L2 recovery message 718B. The L1/L2 recovery message 718A or the L1/L2 recovery message 718B, in some aspects, may include all, or part, of the contents of the L1/L2 recovery request 714A or the L1/L2 recovery request 714B (e.g., to perform content resolution). In some aspects, the L1/L2 recovery message 718A or the L1/L2 recovery message 718B may include a UE ID (e.g., UE-specific information) that identifies the L1/L2 recovery message 718A or the L1/L2 recovery message 718B as being responsive to the L1/L2 recovery request 714A or the L1/L2 recovery request 714B. the L1/L2 recovery message 718A or the L1/L2 recovery message 718B, in some aspects, may include new configuration information (L1 and/or L2 parameters and/or configurations for the reestablished link).
If the L1/L2 recovery message 718A or the L1/L2 recovery message 718B indicates that the authentication value (e.g., the MAC-I value) and the associated L1/L2 recovery request 714A or the associated L1/L2 recovery request 714B is valid, the UE 704, the DU associated with the L1/L2 recovery message 718A or the L1/L2 recovery message 718B (e.g., one of the first DU 702 or the second DU 703 associated with the new cell), and the CU 701 may resume user plane communication at 720 (e.g., may resume one or more L2 sublayers) and may exchange and/or participate in communication 722. In some aspects, resuming the user plane communication at 720 and/or exchanging, and/or participating in, communication 722 may include resuming one or more timers associated with an RLC or a PDCP. The user plane communication at 720 and/or exchanging, and/or participating in, communication 722, in some aspects, may include transmitting an indication of one or more aspects of the L1/L2 link recovery such as an RLC triggering a re-establishment, an RLC triggering a status report transmission, a related PDCP action (e.g., a PDCP data recovery and/or a PDCP status report) or an indication that an L1/L2 recovery and/or reestablishment procedure has occurred (e.g., for reporting to an operator of the network associated with the CU 701, the first DU 702, the second DU 703, and the UE 704).
However, if the L1/L2 recovery message 718A or the L1/L2 recovery message 718B indicates that the authentication value (e.g., the MAC-I value) and the associated L1/L2 recovery request 714A or the associated L1/L2 recovery request 714B are not valid, the UE 704 may initiate a reestablishment procedure associated with L3 parameters (e.g., an RRC reestablishment procedure (not shown)). Based on the reestablishment procedure associated with the L3 parameters, the UE 704, the DU associated with the L1/L2 recovery message 718A or the L1/L2 recovery message 718B (e.g., one of the first DU 702 or the second DU 703 associated with the new cell), and the CU 701 may resume user plane communication at 720 and may exchange and/or participate in communication 722.
After receiving the L1/L2 recovery message 718A or the L1/L2 recovery message 718B (or after detecting a subsequent radio link failure (not shown)), the UE 704 may update, at 724, an authentication value. The update at 724, in some aspects, may be based on the configured rule discussed above. Alternatively, or additionally, the update may be based on receiving updated security parameters (or information for the fast link recovery procedure) in association with one of resuming the user plane communication at 720 and/or exchanging, and/or participating in, communication 722.
In some aspects, the wireless may receive an indication of a set of cells configured for at least one of the L1 link reestablishment procedure or the L2 link reestablishment procedure along with the set of security parameters. In some aspects, the set of cells may include at least one cell associated with each of a plurality of network nodes, e.g., a plurality of DUs associated with at least one of a same CU or one or more CUs (or network nodes) sharing a set of security parameters with the CU associated with the failed radio link as described above in relation to
At 906, the wireless device may detect a failure of a first radio link. For example, 906 may be performed by application processor(s) 1506, cellular baseband processor(s) 1524, transceiver(s) 1522, antenna(s) 1580, and/or fast link recovery for NTN component 198 of
Based on detecting the failure at 906, the wireless device may identify a new cell to which to connect. In some aspects, the new cell may be one of the first cell or a second cell associated with a network node (e.g., the first network node or a second network node) for which the L1 link reestablishment procedure or the L2 link reestablishment procedure may be performed. For example, referring to
As part of identifying the new cell to which to connect, the wireless device may determine that the new cell is configured for one of the L1 link reestablishment procedure or the L2 link reestablishment procedure. In some aspects, the first cell may be associated with a first network node that may be a first satellite-based DU associated with a first satellite in an NTN. Determining that the new cell is configured for one of the L1 link reestablishment procedure or the L2 link reestablishment procedure, in some aspects, may include determining one of (1) that the new cell is associated with the first satellite, (2) that the new cell is associated with the first satellite-based DU, or (3) that the new cell belongs to the set of cells configured for at least one of the L1 link reestablishment procedure or the L2 link reestablishment procedure (e.g., based on the indication of the set of cells received at 902). The set of cells, in some aspects, may include at least one cell associated with each of the first satellite-based DU and an additional DU (e.g., a plurality of DUs associated with at least one of a same CU or one or more CUs (or network nodes) sharing a set of security parameters with the CU associated with the failed radio link) such as a set of cells associated with at least the first DU 702 (or first satellite-based DU 622) and the second DU 703 (or second satellite-based DU 642) that are associated with CU 701 (or network entity 606)). In some aspects, the new cell may be associated with one of the first satellite-based DU and the additional DU (e.g., an additional DU configured for at least one of the L1 link reestablishment procedure or the L2 link reestablishment procedure in relation to the failed radio link). For example, referring to
At 912, the wireless device may transmit, for a network node configured for at least one of the L1 link reestablishment procedure or the L2 link reestablishment procedure, an authentication value based on the set of security parameters included in at least one of an L1 link recovery request or an L2 link recovery request. For example, 912 may be performed by application processor(s) 1506, cellular baseband processor(s) 1524, transceiver(s) 1522, antenna(s) 1580, and/or fast link recovery for NTN component 198 of
At 914, the wireless device may receive, based on at least one of the L1 link recovery request or the L2 link recovery request transmitted at 912, a link recovery message. For example, 914 may be performed by application processor(s) 1506, cellular baseband processor(s) 1524, transceiver(s) 1522, antenna(s) 1580, and/or fast link recovery for NTN component 198 of
After transmitting the authentication value based on the set of security parameters included in at least one of an L1 link recovery request or an L2 link recovery request at 912 or after receiving the link recovery message, the wireless device may update the at least one parameter in the set of security parameters. In some aspects, the at least one parameter in the set of security parameters is updated for a calculation of a different authentication value to be used for a subsequent L1 link recovery request or a subsequent L2 link recovery request. The update at 916, in some aspects, may be based on a configured rule at the wireless device. Accordingly, in some aspects, a first authentication value for a first L1/L2 recovery request (e.g., the L1/L2 recovery request transmitted at 912) may be based on the set of values (or security parameters) received at 902 with subsequent authentication values for subsequent L1/L2 recovery requests based on the configured rules. In some aspects, updating the at least one parameter in the set of security parameters, may further include receiving an update to at least one parameter in the set of security parameters. The update, in some aspects, may be received from one of a network node (e.g., a DU) or from a network entity (e.g., a CU) based on the implementation of the verification procedure as described in relation to
At 1004, the wireless may receive an indication of a set of cells configured for at least one of the L1 link reestablishment procedure or the L2 link reestablishment procedure. For example, 1004 may be performed by application processor(s) 1506, cellular baseband processor(s) 1524, transceiver(s) 1522, antenna(s) 1580, and/or fast link recovery for NTN component 198 of
At 1006, the wireless device may detect a failure of a first radio link. For example, 1006 may be performed by application processor(s) 1506, cellular baseband processor(s) 1524, transceiver(s) 1522, antenna(s) 1580, and/or fast link recovery for NTN component 198 of
At 1008, the wireless device may identify a new cell to which to connect. For example, 1008 may be performed by application processor(s) 1506, cellular baseband processor(s) 1524, transceiver(s) 1522, antenna(s) 1580, and/or fast link recovery for NTN component 198 of
At 1010, the wireless device may determine that the new cell is configured for one of the L1 link reestablishment procedure or the L2 link reestablishment procedure. For example, 1010 may be performed by application processor(s) 1506, cellular baseband processor(s) 1524, and/or fast link recovery for NTN component 198 of
At 1012, the wireless device may transmit, for a network node configured for at least one of the L1 link reestablishment procedure or the L2 link reestablishment procedure, an authentication value based on the set of security parameters included in at least one of an L1 link recovery request or an L2 link recovery request. For example, 1012 may be performed by application processor(s) 1506, cellular baseband processor(s) 1524, transceiver(s) 1522, antenna(s) 1580, and/or fast link recovery for NTN component 198 of
At 1014, the wireless device may receive, based on at least one of the L1 link recovery request or the L2 link recovery request transmitted at 1012, a link recovery message. For example, 1014 may be performed by application processor(s) 1506, cellular baseband processor(s) 1524, transceiver(s) 1522, antenna(s) 1580, and/or fast link recovery for NTN component 198 of
At 1016, the wireless device may update the at least one parameter in the set of security parameters. For example, 1016 may be performed by application processor(s) 1506, cellular baseband processor(s) 1524, transceiver(s) 1522, antenna(s) 1580, and/or fast link recovery for NTN component 198 of
In some aspects, the network node may receive, from a network entity, one or more indications of values associated with a set of security parameters associated with one of an L1 link reestablishment procedure or an L2 link reestablishment procedure. The received one or more indications, in some aspects may relate to one or more of an ID of an associated wireless device, a C-RNTI, a TEID, at least one value used for a calculation of an authentication value (e.g., a MAC-I associated with one of the L1 link reestablishment procedure or the L2 link reestablishment procedure), a security algorithm associated with at least one of the L1 link reestablishment procedure or the L2 link reestablishment procedure, or a duration for which the set of security parameters is valid. In some aspects, one or more of the above values may be omitted if the network node can independently verify requests associated with one of the L1 link reestablishment procedure or the L2 link reestablishment procedure. In some aspects, the L1 link reestablishment procedure or the L2 link reestablishment procedure reuses (is configured to reuse) L3 parameters associated with the first radio link. For example, referring to
The network node, in some aspects may generate, based on the one or more indications, the set of security parameters. The set of security parameters, in some aspects, may include one or more of an ID of an associated wireless device, a C-RNTI, a TEID, at least one value used for a calculation of an authentication value (e.g., a MAC-I associated with one of the L1 link reestablishment procedure or the L2 link reestablishment procedure), a security algorithm associated with at least one of the L1 link reestablishment procedure or the L2 link reestablishment procedure, or a duration for which the set of security parameters is valid. For example, referring to
At 1106, the network node may transmit, for a wireless device, the set of security parameters associated with one of the L1 link reestablishment procedure or the L2 link reestablishment procedure. For example, 1106 may be performed by DU processor(s) 1632, RU processor(s) 1642, transceiver(s) 1646, antenna(s) 1680, and/or fast link recovery for NTN component 199 of
At 1108, the network node may receive, from the wireless device experiencing a failure of a first radio link, at least one of an L1 link recovery request or an L2 link recovery request. For example, 1108 may be performed by DU processor(s) 1632, RU processor(s) 1642, transceiver(s) 1646, antenna(s) 1680, and/or fast link recovery for NTN component 199 of
The network node, in some aspects, may verify, based on the authentication value, that at least one of the L1 link recovery request or the L2 link recovery request is valid. In some aspects, in order to perform the verification at 1110, the network node may determine that the authentication value included in at least one of the L1 link recovery request or the L2 link recovery request matches a locally-stored authentication value. The locally stored value, in some aspects, may be received from the network entity or may be calculated based on values received from the network entity and/or based on an algorithm indicated by the network entity. For example, referring to
In some aspects, in order to perform the verification, the network node may transmit, for a network entity associated with the first radio link, a verification request including the authentication value and receive, from the network entity, a verification response verifying that the authentication value is valid. In some aspects, the authentication value may be the MAC-I value received from the wireless device at 1108. Referring to
At 1114, the network node may transmit, for the wireless device, a link recovery message associated with a reestablishment of a second radio link. For example, 1114 may be performed by DU processor(s) 1632, RU processor(s) 1642, transceiver(s) 1646, antenna(s) 1680, and/or fast link recovery for NTN component 199 of
In some aspects, the network node may receive, from a network entity, an update to the at least one parameter in the set of security parameters. In some aspects, the updated at least one parameter may be for use for verifying a subsequent L1 link recovery request or a subsequent L2 link recovery request. For example, referring to
At 1202, the network node may receive, from a network entity, one or more indications of values associated with a set of security parameters associated with one of an L1 link reestablishment procedure or an L2 link reestablishment procedure. For example, 1202 may be performed by DU processor(s) 1632, RU processor(s) 1642, transceiver(s) 1646, antenna(s) 1680, and/or fast link recovery for NTN component 199 of
At 1204, the network node may generate, based on the one or more indications, the set of security parameters. For example, 1204 may be performed by DU processor(s) 1632, RU processor(s) 1642, transceiver(s) 1646, antenna(s) 1680, and/or fast link recovery for NTN component 199 of
At 1206, the network node may transmit, for a wireless device, the set of security parameters associated with one of the L1 link reestablishment procedure or the L2 link reestablishment procedure. For example, 1206 may be performed by DU processor(s) 1632, RU processor(s) 1642, transceiver(s) 1646, antenna(s) 1680, and/or fast link recovery for NTN component 199 of
At 1208, the network node may receive, from the wireless device experiencing a failure of a first radio link, at least one of an L1 link recovery request or an L2 link recovery request. For example, 1208 may be performed by DU processor(s) 1632, RU processor(s) 1642, transceiver(s) 1646, antenna(s) 1680, and/or fast link recovery for NTN component 199 of
At 1210 the network node may verify, based on the authentication value, that at least one of the L1 link recovery request or the L2 link recovery request is valid. In some aspects, in order to perform the verification at 1210, the network node may determine, at 1211, that the authentication value included in at least one of the L1 link recovery request or the L2 link recovery request matches a locally-stored authentication value. The locally stored value, in some aspects, may be received from the network entity or may be calculated based on values received from the network entity and/or based on an algorithm indicated by the network entity. For example, referring to
In some aspects, in order to perform the verification at 1210, the network node may, at 1212, transmit, for a network entity associated with the first radio link, a verification request including the authentication value and, at 1213, may receive a verification response verifying that the authentication value is valid. In some aspects, the authentication value may be the MAC-I value received from the wireless device at 1208. Referring to
At 1214, the network node may transmit, for the wireless device, a link recovery message associated with a reestablishment of a second radio link. For example, 1214 may be performed by DU processor(s) 1632, RU processor(s) 1642, transceiver(s) 1646, antenna(s) 1680, and/or fast link recovery for NTN component 199 of
At 1216, the network node may receive, from a network entity, an update to the at least one parameter in the set of security parameters. For example, 1216 may be performed by DU processor(s) 1632, RU processor(s) 1642, transceiver(s) 1646, antenna(s) 1680, and/or fast link recovery for NTN component 199 of
At 1218, the network node may transmit, for the wireless device, an update to at least one parameter in the set of security parameters. For example, 1218 may be performed by DU processor(s) 1632, RU processor(s) 1642, transceiver(s) 1646, antenna(s) 1680, and/or fast link recovery for NTN component 199 of
At 1302, the network node may output, for a network node, at least one of one or more indications of values associated with a set of security parameters associated with one of an L1 link reestablishment procedure or an L2 link reestablishment procedure or the set of security parameters. For example, 1302 may be performed by CU processor(s) 1612, transceiver(s) 1646, antenna(s) 1680, network processor 1712, network interface 1780, and/or fast link recovery for NTN component 199 of
At 1304, the network entity may output, for a wireless device, the set of security parameters associated with one of the L1 link reestablishment procedure or the L2 link reestablishment procedure. For example, 1304 may be performed by CU processor(s) 1612, transceiver(s) 1646, antenna(s) 1680, network processor 1712, network interface 1780, and/or fast link recovery for NTN component 199 of
Based on the at least one of one or more indications of values associated with a set of security parameters or the set of security parameters, in some aspects, the network entity may obtain, from a network node associated with a first radio link that has experienced a failure, a verification request including an authentication value based on the set of security parameters. The authentication value, in some aspects, may be a MAC-I value to be compared to a MAC-I value calculated, and/or stored at, the network entity and the network entity may verify the authentication value by performing the comparison. For example, referring to
The network entity, in some aspects, may output, for the network node, a verification response verifying that the authentication value is valid. The verification response, in some aspects, may indicate the results of a verification performed by the network node. While described for a valid verification request, in some aspects, the verification request may be invalid and the verification response will reflect the invalidity of the verification request and the fast link recovery procedure may be interrupted and/or terminated. For example, referring to
In some aspects, the network entity may output, for at least one of the network node or the wireless device, an update to at least one parameter in the set of security parameters. In some aspects, the updated at least one parameter may for verifying (at the network node), and/or generating (at the wireless device) a subsequent L1 link recovery request or a subsequent L2 link recovery request. For example, referring to
At 1402, the network node may output, for a network node, at least one of one or more indications of values associated with a set of security parameters associated with one of an L1 link reestablishment procedure or an L2 link reestablishment procedure or the set of security parameters. For example, 1402 may be performed by CU processor(s) 1612, transceiver(s) 1646, antenna(s) 1680, network processor 1712, network interface 1780, and/or fast link recovery for NTN component 199 of
At 1404, the network entity may output, for a wireless device, the set of security parameters associated with one of the L1 link reestablishment procedure or the L2 link reestablishment procedure. For example, 1404 may be performed by CU processor(s) 1612, transceiver(s) 1646, antenna(s) 1680, network processor 1712, network interface 1780, and/or fast link recovery for NTN component 199 of
At 1406, the network entity may obtain, from a network node associated with a first radio link that has experienced a failure, a verification request including an authentication value based on the set of security parameters. For example, 1406 may be performed by CU processor(s) 1612, transceiver(s) 1646, antenna(s) 1680, network processor 1712, network interface 1780, and/or fast link recovery for NTN component 199 of
At 1408, the network entity may output, for the network node, a verification response verifying that the authentication value is valid. For example, 1408 may be performed by CU processor(s) 1612, transceiver(s) 1646, antenna(s) 1680, network processor 1712, network interface 1780, and/or fast link recovery for NTN component 199 of
At 1410, the network entity may output, for at least one of the network node or the wireless device, an update to at least one parameter in the set of security parameters. For example, 1410 may be performed by CU processor(s) 1612, transceiver(s) 1646, antenna(s) 1680, network processor 1712, network interface 1780, and/or fast link recovery for NTN component 199 of
As discussed supra, the fast link recovery for NTN component 198 that may be configured to receive a set of security parameters associated with one of an L1 link reestablishment procedure or an L2 link reestablishment procedure, detect a failure of a radio link at the wireless device. The fast link recovery for NTN component 198 may further be configured to transmit, for a network node, at least one of an L1 link recovery request or an L2 link recovery request, where at least one of the L1 link recovery request or the L2 link recovery request includes an authentication value based on the set of security parameters, and receive, based on at least one of the L1 link recovery request or the L2 link recovery request, a link recovery message. The fast link recovery for NTN component 198 may be within the cellular baseband processor(s) 1524, the application processor(s) 1506, or both the cellular baseband processor(s) 1524 and the application processor(s) 1506. The fast link recovery for NTN component 198 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may perform the stated processes/algorithm individually or in combination. As shown, the apparatus 1504 may include a variety of components configured for various functions. In one configuration, the apparatus 1504, and in particular the cellular baseband processor(s) 1524 and/or the application processor(s) 1506, may include means for receiving a set of security parameters associated with one of an L1 link reestablishment procedure or an L2 link reestablishment procedure. The apparatus 1504, and in particular the cellular baseband processor(s) 1524 and/or the application processor(s) 1506, may further include means for detecting a failure of a radio link between the wireless device and a first network node. The apparatus 1504, and in particular the cellular baseband processor(s) 1524 and/or the application processor(s) 1506, may further include means for identifying a new cell to which to connect. The apparatus 1504, and in particular the cellular baseband processor(s) 1524 and/or the application processor(s) 1506, may further include means for determining that the new cell is associated with the network node. The apparatus 1504, and in particular the cellular baseband processor(s) 1524 and/or the application processor(s) 1506, may further include means for receiving an indication of the set of cells configured for at least one of the L1 link reestablishment procedure or the L2 link reestablishment procedure. The apparatus 1504, and in particular the cellular baseband processor(s) 1524 and/or the application processor(s) 1506, may further include means for transmitting, for a network node, at least one of an L1 link recovery request or an L2 link recovery request, where at least one of the L1 link recovery request or the L2 link recovery request includes an authentication value based on the set of security parameters. The apparatus 1504, and in particular the cellular baseband processor(s) 1524 and/or the application processor(s) 1506, may further include means for receiving, based on at least one of the L1 link recovery request or the L2 link recovery request, a link recovery message. The apparatus 1504, and in particular the cellular baseband processor(s) 1524 and/or the application processor(s) 1506, may further include means for receiving an update to at least one parameter in the set of security parameters. The apparatus 1504, and in particular the cellular baseband processor(s) 1524 and/or the application processor(s) 1506, may further include means for updating the at least one parameter in the set of security parameters. The means may be the fast link recovery for NTN component 198 of the apparatus 1504 configured to perform the functions recited by the means. As described supra, the apparatus 1504 may include the TX processor 368, the RX processor 356, and the controller/processor 359. As such, in one configuration, the means may be the TX processor 368, the RX processor 356, and/or the controller/processor 359 configured to perform the functions recited by the means or as described in relation to
As discussed supra, the fast link recovery for NTN component 199 that may be configured to transmit, for a wireless device, a set of security parameters associated with one of an L1 link reestablishment procedure or an L2 link reestablishment procedure. The fast link recovery for NTN component 199 may further be configured to receive, from the wireless device experiencing a failure of a first radio link, at least one of an L1 link recovery request or an L2 link recovery request, where at least one the L1 link recovery request or the L2 link recovery request includes an authentication value based on the set of security parameters, and transmit, for the wireless device, a link recovery message associated with a reestablishment of a second radio link. The fast link recovery for NTN component 199 may be within one or more processors of one or more of the CU 1610, DU 1630, and the RU 1640. The fast link recovery for NTN component 199 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may perform the stated processes/algorithm individually or in combination. The network entity 1602 may include a variety of components configured for various functions. In one configuration, the network entity 1602 may include means for transmitting, for a wireless device, a set of security parameters associated with one of an L1 link reestablishment procedure or an L2 link reestablishment procedure. The network entity 1602, in some aspects, may include means for receiving, from the wireless device experiencing a failure of a first radio link, at least one of an L1 link recovery request or an L2 link recovery request, where at least one of the L1 link recovery request or the L2 link recovery request includes an authentication value based on the set of security parameters. The network entity 1602, in some aspects, may include means for verifying, based on the authentication value, that at least one of the L1 link recovery request or the L2 link recovery request is valid. The network entity 1602, in some aspects, may include means for determining that the authentication value included in at least one of the L1 link recovery request or the L2 link recovery request matches a locally-stored authentication value. The network entity 1602, in some aspects, may include means for transmitting, for a network entity associated with the first radio link, a verification request including the authentication value. The network entity 1602, in some aspects, may include means for receiving a verification response verifying that the authentication value is valid. The network entity 1602, in some aspects, may include means for transmitting, for the wireless device, a link recovery message associated with a reestablishment of a second radio link. The network entity 1602, in some aspects, may include means for receiving, from a network entity, the update to the at least one parameter in the set of security parameters. The network entity 1602, in some aspects, may include means for transmitting, for the wireless device, an update to at least one parameter in the set of security parameters. The network entity 1602, in some aspects, may include means for receiving, from a network entity, one or more indications of values associated with the set of security parameters. The network entity 1602, in some aspects, may include means for generating, before the transmission of the set of security parameters and based on the one or more indications, the set of security parameters. The means may be the fast link recovery for NTN component 199 of the network entity 1602 configured to perform the functions recited by the means. As described supra, the network entity 1602 may include the TX processor 316, the RX processor 370, and the controller/processor 375. As such, in one configuration, the means may be the TX processor 316, the RX processor 370, and/or the controller/processor 375 configured to perform the functions recited by the means or as described in relation to
As discussed supra, the fast link recovery for NTN component 199 that may be configured to output, for a network node, at least one of one or more indications of values associated with a set of security parameters associated with one of an L1 link reestablishment procedure or an L2 link reestablishment procedure or the set of security parameters and output, for a wireless device, the set of security parameters associated with one of the L1 link reestablishment procedure or the L2 link reestablishment procedure. The fast link recovery for NTN component 199 may be within the network processor(s) 1712. The fast link recovery for NTN component 199 may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may perform the stated processes/algorithm individually or in combination. The network entity 1760 may include a variety of components configured for various functions. In one configuration, the network entity 1760 may include means for outputting, for a network node, at least one of one or more indications of values associated with a set of security parameters associated with one of an L1 link reestablishment procedure or an L2 link reestablishment procedure or the set of security parameters. The network entity 1760, in some aspects, may include means for outputting, for a wireless device, the set of security parameters associated with one of the L1 link reestablishment procedure or the L2 link reestablishment procedure. The network entity 1760, in some aspects, may include means for obtaining, from a network node associated with a first radio link that has experienced a failure, a verification request including an authentication value based on the set of security parameters. The network entity 1760, in some aspects, may include means for outputting a verification response verifying that the authentication value is valid. The network entity 1760, in some aspects, may include means for outputting, for at least one of the network node or the wireless device, an update to at least one parameter in the set of security parameters. The means may be the fast link recovery for NTN component 199 of the network entity 1760 configured to perform the functions recited by the means or as described in relation to
In some aspects of wireless communication, a cell associated with an NTN cell (e.g., associated with a satellite-based base station and/or DU) may cover a (very) wide area and may be easily blocked, e.g., by buildings, tunnels, or other obstacles. Based on the wide coverage that is easily blocked, even if the UE temporarily loses contact with an NTN cell serving the UE, it may be likely that the UE will identify the same NTN cell again after passing through a blocked area. In some aspects, the UE may initiate a radio resource control (RRC) reestablishment procedure to connect to the same NTN cell. Because the RRC reestablishment procedure, in some aspects, includes RRC-level interaction (e.g., layer 3 (L3) communication) between the UE and a CU via the satellite-based base station and/or DU, the reestablishment procedure may involve long delays associated with transmissions to and from the satellite-based base station and/or DU. For example, the reestablishment procedure may, due to a radio link control (RLC) flush (e.g., a reset of RLC parameters), involve control plane signaling and user plane retransmissions associated with a packet data convergence protocol (PDCP) due
Various aspects relate generally to a novel link reestablishment for reestablishing a link with a same DU or, in some aspects, for establishing a link with a DU associated with a same CU that avoids resetting layer 3 parameters. The novel link reestablishment procedure, in some aspects, may reduce a link reestablishment time compared to an RRC reestablishment procedure associated with configuring L3 parameters, where the reduction may be larger for NTNs than for terrestrial networks. Some aspects more specifically relate to providing configuration information that may be used to enable a link reestablishment procedure that avoids configuring L3 parameters. Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by using the novel L1 link reestablishment procedure and/or the L2 link reestablishment procedure, the described techniques can be used to reduce a latency associated with link reestablishment and/or recovery, especially associated with an NTN.
In an NTN, a UE may frequently lose connectivity with a satellite due to buildings, tunnels, or other obstructions. According to current procedures, a UE attempts RRC connection reestablishment with the same cell. In case of split DU-CU architecture with DU being in the satellite, this may take a very long time. After an RLF, when a UE attempts connection establishment again to the same cell (or DU), it may attempt to re-establish the connection with gNB-DU (not involving gNB-CU) using the fast link recovery process according to some aspects of the disclosure.
It is understood that the specific order or hierarchy of blocks in the processes/flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes/flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not limited to the specific order or hierarchy presented.
The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language claims. Reference to an element in the singular does not mean “one and only one” unless specifically so stated, but rather “one or more.” Terms such as “if,” “when,” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when,” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and/or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. Sets should be interpreted as a set of elements where the elements number one or more. Accordingly, for a set of X, X would include one or more elements. When at least one processor is configured to perform a set of functions, the at least one processor, individually or in any combination, is configured to perform the set of functions. Accordingly, each processor of the at least one processor may be configured to perform a particular subset of the set of functions, where the subset is the full set, a proper subset of the set, or an empty subset of the set. If a first apparatus receives data from or transmits data to a second apparatus, the data may be received/transmitted directly between the first and second apparatuses, or indirectly between the first and second apparatuses through a set of apparatuses. A device configured to “output” data, such as a transmission, signal, or message, may transmit the data, for example with a transceiver, or may send the data to a device that transmits the data. A device configured to “obtain” data, such as a transmission, signal, or message, may receive, for example with a transceiver, or may obtain the data from a device that receives the data. Information stored in a memory includes instructions and/or data. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. Moreover, nothing disclosed herein is dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module,” “mechanism,” “element,” “device,” and the like may not be a substitute for the word “means.” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for.”
As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A” (where “A” may be information, a condition, a factor, or the like) shall be construed as “based at least on A” unless specifically recited differently.
The following aspects are illustrative only and may be combined with other aspects or teachings described herein, without limitation.
Aspect 1 is a method for wireless communication for a wireless device, comprising: receiving a set of security parameters associated with one of a layer 1 (L1) link reestablishment procedure or a layer 2 (L2) link reestablishment procedure; detecting a failure of a radio link between the wireless device and a first network node; transmitting, for a network node configured for at least one of the L1 link reestablishment procedure or the L2 link reestablishment procedure, an authentication value based on the set of security parameters included in at least one of an L1 link recovery request or an L2 link recovery request; and receiving, based on at least one of the L1 link recovery request or the L2 link recovery request, a link recovery message.
Aspect 2 is the method of aspect 1, wherein the set of security parameters comprises one or more of a first identifier (ID) of the wireless device, a cell radio network temporary ID (C-RNTI), a tunnel endpoint ID (TEID), at least one value used for a calculation of the authentication value, a security algorithm associated with at least one of the L1 link reestablishment procedure or the L2 link reestablishment procedure, or a duration for which the set of security parameters is valid.
Aspect 3 is the method of aspect 2, wherein the authentication value comprises a message authentication code for integrity (MAC-I) value, and the L1 link recovery request or the L2 link recovery request comprises one or more of the ID of the wireless device, the C-RNTI, the TEID, the MAC-I value, a cause value indicating a type of failure associated with the failure of the radio link, a second ID of the first network node, or a third ID of a network entity associated with the first network node, and wherein the network entity comprises a centralized unit (CU).
Aspect 4 is the method of any of aspects 1 to 3, wherein the radio link is a first radio link with a first cell associated with the first network node, the method further comprising: identifying a new cell to which to connect, wherein the new cell is one of the first cell or a second cell associated with the network node configured for at least one of the L1 link reestablishment procedure or the L2 link reestablishment procedure; and determining that the new cell is configured for one of the L1 link reestablishment procedure or the L2 link reestablishment procedure, wherein transmitting at least one of the L1 link recovery request or the L2 link recovery request comprises transmitting at least one of the L1 link recovery request or the L2 link recovery request for the new cell based on the determination that the new cell is configured for one of the L1 link reestablishment procedure or the L2 link reestablishment procedure.
Aspect 5 is the method of aspect 4, wherein the first network node comprises a first satellite-based distributed unit (DU) associated with a first satellite in a non-terrestrial network (NTN), wherein the wireless device is a user equipment (UE), and wherein determining that the new cell is configured for at least one of the L1 link reestablishment procedure or the L2 link reestablishment procedure comprises determining one of (1) that the new cell is associated with the first satellite, (2) that the new cell is associated with the first satellite-based DU, or (3) that the new cell belongs to a set of cells configured for at least one of the L1 link reestablishment procedure or the L2 link reestablishment procedure, wherein the set of cells comprises at least one cell associated with an additional DU.
Aspect 6 is the method of aspect 5, wherein at least one of (1) the determination that the new cell is associated with the first satellite is based on an ID of the first satellite associated with the first cell and associated with the new cell, (2) the determination that the new cell is associated with the first satellite-based DU is based on a DU ID included in one of a system information or a dedicated indication, or (3) the method further comprises: receiving an indication of the set of cells configured for at least one of the L1 link reestablishment procedure or the L2 link reestablishment procedure.
Aspect 7 is the method of any of aspects 1 to 6, wherein the L1 link reestablishment procedure or the L2 link reestablishment procedure reuses layer 3 (L3) parameters associated with the radio link.
Aspect 8 is the method of any of the aspects 1 to 7, wherein after the reception of the link recovery message, the method further comprises one of: receiving an update to at least one parameter in the set of security parameters; or updating the at least one parameter in the set of security parameters, wherein the at least one parameter in the set of security parameters is updated for a calculation of a different authentication value to be used for a subsequent L1 link recovery request or a subsequent L2 link recovery request.
Aspect 9 is the method of any of aspects 1 to 8, wherein the L1 link recovery request or the L2 link recovery request is associated with one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, or a physical (PHY) layer.
Aspect 10 is a method for wireless communication for a network node, comprising: transmitting, for a wireless device, a set of security parameters associated with one of a layer 1 (L1) link reestablishment procedure or a layer 2 (L2) link reestablishment procedure; receiving, from the wireless device experiencing a failure of a first radio link, at least one of an L1 link recovery request or an L2 link recovery request, wherein at least one the L1 link recovery request or the L2 link recovery request includes an authentication value based on the set of security parameters; and transmitting, for the wireless device, a link recovery message associated with a reestablishment of a second radio link.
Aspect 11 is the method of aspect 10, further comprising: verifying, based on the authentication value, that at least one of the L1 link recovery request or the L2 link recovery request is valid, wherein transmitting the link recovery message is based on the verification that at least one of the L1 link recovery request or the L2 link recovery request is valid.
Aspect 12 is the method of aspect 11, wherein verifying that at least one of the L1 link recovery request or the L2 link recovery request is valid comprises determining that the authentication value included in at least one of the L1 link recovery request or the L2 link recovery request matches a locally-stored authentication value.
Aspect 13 is the method of aspect 11, wherein verifying that at least one of the L1 link recovery request or the L2 link recovery request is valid comprises: transmitting, for a network entity associated with the first radio link, a verification request including the authentication value; and receiving a verification response verifying that the authentication value is valid.
Aspect 14 is the method any of the aspects 10 to 13, wherein the set of security parameters comprises one or more of a first identifier (ID) of the wireless device, a cell radio network temporary ID (C-RNTI), a tunnel endpoint ID (TEID), at least one value used for a calculation of the authentication value, a security algorithm associated with at least one of the L1 link reestablishment procedure or the L2 link reestablishment procedure, or a duration for which the set of security parameters is valid.
Aspect 15 is the method of aspect 14, wherein the network node comprises a satellite-based distributed unit (DU) associated with a first satellite in a non-terrestrial network (NTN), wherein the wireless device is a user equipment (UE), and wherein at least one of the first satellite or the DU is associated with a plurality of cells associated with the L1 link reestablishment procedure or the L2 link reestablishment procedure.
Aspect 16 is the method of aspect 15, wherein the first radio link is associated with a first cell of the plurality of cells and at least one of the L1 link recovery request or the L2 link recovery request is associated with a second cell of the plurality of cells.
Aspect 17 is the method of any of aspects 14 to 16, wherein the authentication value comprises a message authentication code for integrity (MAC-I) value, and the L1 link recovery request or the L2 link recovery request comprises one or more of the first ID of the wireless device, the C-RNTI, the TEID, the MAC-I value, a cause value indicating a type of failure associated with the failure of the first radio link, a second ID of the network node, or a third ID of a network entity associated with the network node.
Aspect 18 is the method of any of the aspects 10 to 17, wherein the L1 link reestablishment procedure or the L2 link reestablishment procedure reuses layer 3 (L3) parameters associated with the first radio link.
Aspect 19 is the method of any of aspects 10 to 18, wherein after the transmission of the link recovery message, the method further comprising: transmitting, for the wireless device, an update to at least one parameter in the set of security parameters, wherein the at least one parameter in the set of security parameters is updated for a calculation of a different authentication value to be used for a subsequent L1 link recovery request or a subsequent L2 link recovery request.
Aspect 20 is the method of aspect 19, the method further comprising: receiving, from a network entity, the update to the at least one parameter in the set of security parameters.
Aspect 21 is the method of any of the aspects 10 to 20, wherein the L1 link recovery request or the L2 link recovery request is associated with one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, or a physical (PHY) layer.
Aspect 22 is the method of any of the aspects 10 to 21, further comprising: receiving, from a network entity, one or more indications of values associated with the set of security parameters; and generating, before the transmission of the set of security parameters and based on the one or more indications, the set of security parameters.
Aspect 23 is a method for wireless communication for a network entity, comprising: outputting, for a network node, at least one of one or more indications of values associated with a set of security parameters associated with one of a layer 1 (L1) link reestablishment procedure or a layer 2 (L2) link reestablishment procedure or the set of security parameters; and outputting, for a wireless device, the set of security parameters associated with one of the L1 link reestablishment procedure or the L2 link reestablishment procedure.
Aspect 24 is the method of aspect 23, further comprising: obtaining, from a network node associated with a first radio link that has experienced a failure, a verification request including an authentication value based on the set of security parameters; and outputting a verification response verifying that the authentication value is valid.
Aspect 25 is the method of aspect 24, wherein the set of security parameters comprises one or more of an identifier (ID) of the wireless device, a cell radio network temporary ID (C-RNTI), a tunnel endpoint ID (TEID), at least one value used for a calculation of the authentication value, a security algorithm associated with at least one of the L1 link reestablishment procedure or the L2 link reestablishment procedure, a security algorithm associated with at least one of the L1 link reestablishment procedure or the L2 link reestablishment procedure, or a duration for which the set of security parameters is valid.
Aspect 26 is the method of aspect 25, wherein the network node comprises a satellite-based distributed unit (DU) associated with a first satellite in a non-terrestrial network (NTN), wherein the wireless device is a user equipment (UE), and wherein at least one of the first satellite or the DU is associated with a plurality of cells associated with the L1 link reestablishment procedure or the L2 link reestablishment procedure.
Aspect 27 is the method of aspect 26, wherein the first radio link is associated with a first cell of the plurality of cells and the verification request is associated with a second cell of the plurality of cells.
Aspect 28 is the method of any of the aspects 24 to 28, wherein after the obtainment of the verification request, the method further comprising: outputting, for at least one of the network node or the wireless device, an update to at least one parameter in the set of security parameters, wherein the at least one parameter in the set of security parameters is updated for a calculation of a different authentication value to be used in association with a subsequent verification request.
Aspect 29 is the method of any of the aspects 23 to 27, wherein the L1 link reestablishment procedure or the L2 link reestablishment procedure reuses layer 3 (L3) parameters associated with a radio link for which failure was detected.
Aspect 30 is the method of any of the aspects 23 to 30, wherein the L1 link reestablishment procedure or the L2 link reestablishment procedure is associated with one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, or a physical (PHY) layer.
Aspect 31 is an apparatus for wireless communication at a device including a memory and at least one processor coupled to the memory and, based at least in part on information stored in the memory, the at least one processor is configured to implement any of aspects 1 to 9.
Aspect 32 is the apparatus of aspect 31, further including a transceiver or an antenna coupled to the at least one processor.
Aspect 33 is an apparatus for wireless communication at a device including means for implementing any of aspects 1 to 9.
Aspect 34 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 1 to 9.
Aspect 35 is an apparatus for wireless communication at a device including a memory and at least one processor coupled to the memory and, based at least in part on information stored in the memory, the at least one processor is configured to implement any of aspects 10 to 22.
Aspect 36 is the apparatus of aspect 35, further including a transceiver or an antenna coupled to the at least one processor.
Aspect 37 is an apparatus for wireless communication at a device including means for implementing any of aspects 10 to 22.
Aspect 38 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 10 to 22.
Aspect 39 is an apparatus for wireless communication at a device including a memory and at least one processor coupled to the memory and, based at least in part on information stored in the memory, the at least one processor is configured to implement any of aspects 23 to 30.
Aspect 40 is the apparatus of aspect 39, further including a transceiver or an antenna coupled to the at least one processor.
Aspect 41 is an apparatus for wireless communication at a device including means for implementing any of aspects 23 to 30.
Aspect 42 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 23 to 30.
