Mobility in sidelink-assisted access link connectivity

Abstract

This document discloses apparatus, methods, and computer-readable media for facilitating mobility in sidelink-assisted access link connectivity. An example method for wireless communication at a user equipment (UE) includes establishing a sidelink connection with a first auxiliary node (AN) and an access link connection with a first primary node (PN), the first AN and the first PN communicating via a first network interface. The example method further includes determining the occurrence of a node change triggering event associated with at least one of the first AN and the first PN. The example method further includes executing a node change procedure based on the occurrence of the node change triggering event. The example method further includes communicating with at least one of a second AN or a second PN based on the node change procedure, the second AN and the second PN communicating via a second network interface.

Description

Background Technology Technical Field

[0002] This disclosure generally relates to communication systems, and more particularly to mobility protocols within wireless communication systems.

[0003] introduction

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable 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.

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the city, country, region, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the continuous evolution of mobile broadband, promulgated by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the 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 can be based on the 4G Long Term Evolution (LTE) standard. There is a need for further improvements to 5G NR technology. These improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them.

[0006] Overview

[0007] The following provides a brief overview of one or more aspects to offer a basic understanding of such aspects. This overview is not an exhaustive summary of all conceived aspects, nor is it intended to identify the key or decisive elements of all aspects, nor to define 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 an introduction to the more detailed description that follows.

[0008] In one aspect of this disclosure, a method, computer-readable medium, and apparatus for wireless communication for a user equipment (UE) are provided. An example apparatus establishes a sidelink connection with a first auxiliary node (AN) and an access link connection with a first master node (PN), the first AN and the first PN communicating via a first network interface. The example apparatus also determines the occurrence of a node change triggering event associated with at least one of the first AN and the first PN. Additionally, the example apparatus executes a node change procedure based on the occurrence of the node change triggering event. The example apparatus also communicates with at least one of a second AN or a second PN based on the node change procedure, the second AN and the second PN communicating via a second network interface.

[0009] In another aspect of this disclosure, a method, computer-readable medium, and apparatus for wireless communication for a first master node are provided. An example apparatus receives a node change trigger event notification. The example apparatus also performs a node change procedure based on the node change trigger event notification.

[0010] In another aspect of this disclosure, a method, computer-readable medium, and apparatus for wireless communication for a first master node are provided. An example apparatus receives a node change trigger event notification. The example apparatus also performs a node change procedure based on the node change trigger event notification. Additionally, the example apparatus transmits data to a user equipment (UE) via an access link connection based on communication in the millimeter-wave (mmW) frequency range. The example apparatus also transmits control signaling to the UE via a first auxiliary node (AN), and the first PN and the first AN communicate via a first network interface connection.

[0011] To achieve the foregoing and related objectives, these one or more aspects include the features fully described below and specifically pointed out in the claims. Certain illustrative features of these one or more aspects are set forth in detail in the following description and drawings. However, these features merely indicate a few of the various ways in which the principles of these various aspects may be employed, and this description is intended to cover all such aspects and their equivalents. Brief description of the attached diagram

[0013] Figure 1 This is a diagram illustrating an example of a wireless communication system and access network.

[0014] Figure 2A This is an example illustration of the first frame explaining various aspects of this disclosure.

[0015] Figure 2B This is a diagram illustrating an example of a DL channel within a subframe according to various aspects of this disclosure.

[0016] Figure 2C This is an example illustration of the second frame explaining various aspects of this disclosure.

[0017] Figure 2D This is a diagram illustrating an example of a UL channel within a subframe according to various aspects of this disclosure.

[0018] Figure 3 This is a diagram illustrating an example of a base station and a UE in an access network.

[0019] Figure 4 The various examples of sidelink time slot structures were explained.

[0020] Figure 5 This is an example diagram illustrating wireless communication between devices based on sidelink-assisted access link connectivity, in accordance with the teachings disclosed herein.

[0021] Figure 6 This is another example illustration illustrating wireless communication between devices based on sidelink-assisted access link connectivity, in accordance with the teachings disclosed herein.

[0022] Figure 7 This is a diagram illustrating an example system based on sidelink and access link communication, in accordance with the teachings disclosed herein.

[0023] Figure 8 This is an example communication flow between the UE, source auxiliary node (AN), source master node (PN), target AN, and target PN, which performs changes between PNs in accordance with the teachings disclosed herein.

[0024] Figure 9 This is an example communication flow between the UE, source AN, source PN, and target AN, which is performed according to the teachings disclosed herein and changes made between ANs and within PNs.

[0025] Figure 10 This is an example communication flow between the UE, source AN, source PN, target AN, and target PN, which performs changes between ANs and PNs according to the teachings disclosed herein.

[0026] Figure 11 This is an example communication flow between the UE, source AN, source PN, and target PN for performing fast primary cell group recovery in accordance with the teachings disclosed herein.

[0027] Figure 12 This is a flowchart of a method for performing wireless communication at a UE based on the teachings disclosed herein.

[0028] Figure 13 This is another flowchart of a method for performing wireless communication at the UE based on the teachings disclosed in this document.

[0029] Figure 14This is another flowchart of a method for performing wireless communication at the UE based on the teachings disclosed in this document.

[0030] Figure 15 This is another flowchart of a method for performing wireless communication at the UE based on the teachings disclosed in this document.

[0031] Figure 16 This is a diagram illustrating an example of a hardware implementation of the example device based on the teachings disclosed herein.

[0032] Figure 17 This is a flowchart of a method for wireless communication at a source PN based on the teachings disclosed herein.

[0033] Figure 18 This is a flowchart of a method for wireless communication at a target PN based on the teachings disclosed herein.

[0034] Figure 19 This is a diagram illustrating an example of a hardware implementation of the example device based on the teachings disclosed herein.

[0035] Detailed description

[0036] In some examples, user equipment (UE) can establish a connection with a base station to facilitate communication. For example, the UE can establish an access link connection with the base station (sometimes referred to as a "Uu link" or "cellular link"). The base station can be configured to operate at millimeter-wave and / or near-millimeter-wave frequencies in communication with the UE. Communication within millimeter-wave frequencies can provide high throughput and is therefore advantageous for transmitting data between the UE and the base station. However, communication within millimeter-wave frequencies can also be susceptible to service disruptions (e.g., due to congestion).

[0037] In some such examples, the UE can also establish a connection with a sidelink device. For example, the UE can establish a sidelink connection (sometimes referred to as a "PC5 link") with a sidelink device. The sidelink device can connect to the base station via a network interface. Sidelink communication enables a first UE to communicate directly with another UE. For example, the first UE and the second UE can communicate without routing through the base station. As an example, sidelinks can be beneficial for vehicle-based communication, allowing a vehicle UE to communicate directly with another UE associated with, for example, another vehicle, vulnerable road users (e.g., pedestrians, cyclists, etc.), network nodes, infrastructure nodes, etc. The sidelinks and aspects presented herein are not limited to vehicle applications and can be applied to other types of sidelink devices.

[0038] In some examples, sidelink devices can be configured to operate in the sub-6 GHz spectrum. Communication in the sub-6 GHz spectrum is more robust than communication in millimeter-wave frequencies. By establishing a sidelink connection with a sidelink device, the sidelink device can act as an anchor node for millimeter-wave communication over that sidelink connection. For example, the sidelink connection can provide a reliable control plane to manage the access link connection between the UE and the base station. The sidelink connection can also provide a fallback user plane to reduce service interruptions. That is, the UE can communicate control signaling to and / or receive control signaling from the base station via the sidelink device, while simultaneously communicating data directly with the base station via the access link connection. In some such examples, the control signaling may include encapsulated messages to make the control signaling transparent to the sidelink device. For example, the sidelink device can forward control signaling to and / or from the UE while relinquishing processing of that control signaling.

[0039] In some examples, the characteristics of a sidelink connection and / or access link connection can trigger the UE to execute mobility procedures, whereby the UE establishes a new connection with a new sidelink device and / or a new base station. For example, triggering the UE to execute mobility procedures can be based on measurements of the sidelink connection and / or access link connection. In some examples, triggering the UE to execute mobility procedures can be based on the detection of a radio link failure (RLF) associated with that sidelink connection and / or access link connection.

[0040] The aspects disclosed herein provide techniques for enabling a UE to perform mobility procedures. In some examples, performing mobility procedures may include performing an inter-PN change, wherein the UE establishes an access link connection with a new base station. For example, the UE may release an access link connection with the serving (or current) base station and establish a new access link connection with a target (or new) base station. In some examples, the UE may also establish a new sidelink connection with a target sidelink device. It will be understood that in some examples, the serving sidelink device and the target sidelink device may include the same sidelink device, but aspects of the sidelink connection with the serving sidelink device and the new sidelink connection with the target sidelink device may differ, for example, because the serving base station and the target base station are different base stations.

[0041] In some examples, performing mobility procedures may include performing inter-AN changes, whereby the UE establishes a sidelink connection with a new sidelink device. For example, when the sidelink connection with the serving sidelink device does not meet a sidelink connection threshold, the UE may detect the presence of another sidelink device (e.g., a target sidelink device) that meets the threshold. In some examples, performing inter-AN changes may also enable the UE to determine whether the serving sidelink device and the target sidelink device are communicating with the same base station or different base stations. For example, when the serving sidelink device and the target sidelink device are communicating with the same base station, the UE may send a notification to the target sidelink device regarding the same base station communicating with both the serving sidelink device and the target sidelink device (e.g., intra-PN and inter-AN changes). In some such examples, this notification may trigger the target sidelink device to exchange configuration information with the base station so that the target sidelink device can operate as an auxiliary node for communication between the base station and the UE.

[0042] In an example where the serving sidelink device and the target sidelink device are communicating with different base stations, the UE can release the access link connection with the serving base station after establishing a sidelink connection with the target sidelink device. Then, the UE can establish an access link connection with the target base station via the sidelink connection with the target sidelink device.

[0043] The detailed description that follows, taken in conjunction with the accompanying drawings, is intended as a description of various configurations and is not intended to represent only the configurations in which the concepts described herein can be practiced. This detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0044] Several aspects of a telecommunications system will now be described with reference to various apparatuses and methods. These apparatuses and methods will be described in detail below and explained in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0045] As an example, an element, or any part of an element, or any combination of elements, may be implemented as a "processing system" including one or more processors. 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, system-on-a-chip (SoCs), 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 functionalities described throughout this disclosure. One or more processors in a processing system can execute software. Software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms.

[0046] Accordingly, in one or more example aspects, the described functionality can be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality can be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media can be any available medium accessible to a computer. By way of example and not limitation, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disc storage, magnetic disk storage, other magnetic storage devices, combinations of computer-readable media of the types described above, or any other medium capable of being used to store computer-executable code in the form of instructions or data structures accessible to a computer.

[0047] Figure 1This diagram illustrates an example of a wireless communication system and access network 100 in which base station 102 or 180 can wirelessly communicate with UE 104. Examples of device-to-device (D2D) communication may include vehicle-based communication devices that can communicate from vehicle to vehicle (V2V), vehicle to infrastructure (V2I) (e.g., from a vehicle-based communication device to a road infrastructure node, such as a roadside unit (RSU)), vehicle to network (V2N) (e.g., from a vehicle-based communication device to one or more network nodes, such as a base station), vehicle to pedestrian (V2P), cellular vehicle-to-everything (C-V2X), and / or combinations thereof and / or with other devices; these can be collectively referred to as vehicle-to-everything (V2X) communication. Sidelink communication may be based on V2X or other D2D communication, such as proximity services (ProSe). Besides the UE, sidelink communication can also be transmitted and received by other transmitting and receiving devices (such as RSU 107). The PC5 interface can be used to exchange sidelink communication, such as in combination with... Figure 4 The example described in [the document / reference] is as follows.

[0048] In some examples, a UE (e.g., such as UE 104) may be communicating with a base station (e.g., such as base station 180) and with a sidelink device (e.g., such as RSU 107). For example, the sidelink device may operate as an anchor node for communication between the UE and the base station. For instance, the UE may communicate data with the base station via a connection between the UE and the base station, and the UE may communicate control signaling with the base station via a connection between the UE and the sidelink device. In such examples, the sidelink device may act as a relay and forward control signaling to and / or from the UE and the base station.

[0049] In some examples, a UE (such as UE 104) can be configured to manage one or more aspects of wireless communication by executing mobility procedures for handover from a serving device to a target device. As an example, in Figure 1 In this configuration, UE 104 may include UE mobility component 198, which is configured to establish a sidelink connection with a first auxiliary node (AN) and an access link connection with a first primary node (PN), the first AN and the first PN communicating via a first network interface. Example UE mobility component 198 may also be configured to determine the occurrence of a node change triggering event associated with at least one of the first AN and the first PN. Example UE mobility component 198 may also be configured to execute a node change procedure based on the occurrence of the node change triggering event. Example UE mobility component 198 may also be configured to communicate with at least one of a second AN or a second PN based on the node change procedure, the second AN and the second PN communicating via a second network interface.

[0050] Still referencing Figure 1 Base stations (such as base station 102 / 180) can be configured to manage one or more aspects of wireless communication by facilitating the execution of mobility procedures by the UE. As an example, in Figure 1 In this configuration, base station 102 / 180 may include base station mobility component 199. In some examples, base station mobility component 199 may be configured to facilitate a UE performing a PN change from base station 102 / 180 to a target base station. For example, base station mobility component 199 may be configured to receive a PN change trigger event notification. Example base station mobility component 199 may also be configured to perform a PN change procedure based on a PN change trigger event notification.

[0051] In some examples, base station mobility component 199 may be configured to facilitate a PN change by the UE from the serving base station to base station 102 / 180. For example, base station mobility component 199 may be configured to receive a PN change trigger event notification. Example base station mobility component 199 may also be configured to perform a PN change procedure based on a PN change trigger event notification. Example base station mobility component 199 may also be configured to communicate data with the user equipment (UE) via an access link connection based on millimeter wave (mmW) frequency range communication. Example base station mobility component 199 may also be configured to communicate control signaling with the UE via a first auxiliary node (AN), the first PN and the first AN communicating via a first network interface connection.

[0052] While the following description provides examples for 5G NR (and specifically for mobility in sidelink-assisted 5G NR connectivity), the concepts described herein can be applied to other similar domains such as LTE, LTE-A, CDMA, GSM and / or other wireless technologies, where wireless communication devices can employ sidelink devices to assist UEs in 5G NR communication with base stations.

[0053] The wireless communication system (also known as a wireless wide area network (WWAN)) includes base station 102, UE 104, evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). Base station 102 may include macrocells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macrocells include base stations. Small cells include femtocells, picocells, and microcells.

[0054] Base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can interface with core network 190 via a second backhaul link 184. Among other functions, base station 102 can also perform one or more of the following functions: user data delivery, radio channel cryptography and cryptography decoding, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of Non-Access Stratum (NAS) messages, NAS node selection, synchronization, Radio Access Network (RAN) sharing, Multimedia Broadcast Multicast Service (MBMS), subscriber and equipment tracking, RAN Information Management (RIM), paging, location, and delivery of alarm messages. Base station 102 can communicate with each other directly or indirectly (e.g., via EPC 160 or core network 190) on third backhaul link 134 (e.g., X2 interface). First backhaul link 132, second backhaul link 184 and third backhaul link 134 can be wired or wireless.

[0055] Base station 102 can wirelessly communicate with UE 104. Each base station 102 can provide communication coverage for its respective geographical coverage area 110. Overlapping geographical coverage areas 110 may exist. For example, small cell 102' may have coverage areas 110' that overlap with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include a Home Evolved B Node (eNB) (HeNB) that can provide services to a restricted group referred to as a Closed Subscriber Group (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also known as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity. These communication links may use one or more carriers. For each carrier allocated in a total of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum with a bandwidth of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.). These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell), and the secondary component carrier may be referred to as the secondary cell (SCell).

[0056] Some UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 may use DL / UL WWAN spectrum. D2D communication link 158 may use one or more sidelink channels, such as the Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be achieved through a wide variety of wireless D2D communication systems, such as, for example, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0057] The wireless communication system may further include a Wi-Fi access point (AP) 150 communicating with a Wi-Fi station (STA) 152 via a communication link 154, for example, in an unlicensed spectrum such as 5 GHz. When communicating in unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) before communication to determine whether the channel is available.

[0058] Small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 102' can employ NR and use the same unlicensed spectrum (e.g., 5 GHz, etc.) used by Wi-Fi AP 150. Small cell 102' employing NR in unlicensed spectrum can enhance access network coverage and / or increase access network capacity.

[0059] The electromagnetic spectrum is typically subdivided into various classes, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz–7.125GHz) and FR2 (24.25GHz–52.6GHz). The frequencies between FR1 and FR2 are generally referred to as the mid-band frequencies. Although a portion of FR1 is greater than 6GHz, FR1 is often (interchangeably) referred to as the “sub-6GHz” band in various documents and articles. Similar naming issues sometimes arise regarding FR2; although different from the Very High Frequency (EHF) band (30GHz–300GHz) designated as the “millimeter wave” band by the International Telecommunication Union (ITU), FR2 is often (interchangeably) referred to as the “millimeter wave” band in various documents and articles.

[0060] In light of the above, unless otherwise stated, the term "sub-6GHz" as used herein may broadly refer to frequencies less than 6GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise stated, the term "millimeter wave" as used herein may broadly refer to frequencies including intermediate frequency band frequencies, within FR2, or within the EHF band.

[0061] Whether it is a small cell 102' or a large cell (e.g., a macro base station), base station 102 may include and / or be referred to as an eNB, gB node (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in conventional sub-6 GHz spectrum, millimeter wave frequencies, and / or near-millimeter wave frequencies to communicate with UE 104. When gNB 180 operates in millimeter wave frequencies or near-millimeter wave frequencies, gNB 180 may be referred to as a millimeter wave base station. Millimeter wave base station 180 may utilize beamforming 182 with UE 104 to compensate for path loss and short range. Base station 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.

[0062] Base station 180 may transmit beamformed signals to UE 104 in one or more transmission directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more reception directions 182'. UE 104 may also transmit beamformed signals to base station 180 in one or more transmission directions. Base station 180 may receive beamformed signals from UE 104 in one or more reception directions. Base station 180 / UE 104 may perform beam training to determine the optimal reception and transmission directions for each of base station 180 / UE 104. The transmission and reception directions of base station 180 may be the same or different. The transmission and reception directions of UE 104 may be the same or different.

[0063] EPC 160 may include Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 may communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Generally, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. The BM-SC 170 provides functionality for MBMS user service provisioning and delivery. The BM-SC 170 can serve as an entry point for content provider MBMS transmissions, authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and schedule MBMS transmissions. The MBMS gateway 168 can be used to distribute MBMS traffic to base station 102 within a Broadcast-Specific Service Single Frequency Network (MBSFN) area, and can be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0064] The core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that handles signaling between UE 104 and the core network 190. Generally, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP services 197. IP services 197 may include the Internet, intranet, IP Multimedia Subsystem (IMS), Packet Switched (PS) Streaming (PSS) services, and / or other IP services.

[0065] Base stations may include and / or be referred to as gNB, B-node, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit / receive point (TRP), or some other suitable term. Base station 102 provides UE 104 with access to EPC 160 or core network 190. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptop devices, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similar functional devices. Some UE 104 may be referred to as IoT devices (e.g., parking timers, oil pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile client, client, or some other suitable term.

[0066] Figure 2A This is a diagram 200 illustrating an example of the first subframe within the 5G NR frame structure. Figure 2B Figure 230 is an example illustrating the DL channel within a 5G NR subframe. Figure 2C This is a diagram 250 illustrating an example of the second subframe within the 5G NR frame structure. Figure 2D Figure 280 illustrates an example of the UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD), where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL; or it can be Time Division Duplex (TDD), where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL. Figure 2A , 2CIn the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (mostly DL) and subframe 3 is configured with slot format 1 (all UL), where D is DL, U is UL, and F is for flexible use between DL and UL. Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and all UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured to have a slot format via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to 5G NR frame structures for TDD.

[0067] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10ms) can be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. Subframes may also include mini-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, while for time slot configuration 1, each time slot may include 7 symbols. Symbols on the DL can be Cyclic Prefix (CP) Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the time slot configuration and parameter design. For slot configuration 0, different parameter designs μ of 0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different parameter designs 0 to 2 allow 2, 4, and 8 slots per subframe, respectively. Correspondingly, for slot configuration 0 and parameter design μ, there are 14 symbols per slot and 2 symbols per subframe. μ Each time slot. The subcarrier spacing and symbol length / duration vary depending on the design parameters. The subcarrier spacing can be equal to 2. μ *15kHz, where μ is the parameter design from 0 to 4. Thus, parameter design μ = 0 has a subcarrier spacing of 15kHz, while parameter design μ = 4 has a subcarrier spacing of 240kHz. Symbol length / duration is inversely correlated with subcarrier spacing. Figures 2A to 2DAn example is provided with a slot configuration of 0 (14 symbols per slot) and a parameter design of μ=2 (4 slots per subframe). The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, there may be one or more different bandwidth portions (BWPs) that are frequency-division multiplexed (see [link to relevant documentation]). Figure 2B Each BWP can have specific parameter designs.

[0068] A resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) extending 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0069] like Figure 2A As explained in the text, some REs carry reference (pilot) signals (RS) for the UE. RSs may include demodulation RS (DM-RS) for channel estimation at the UE (indicated as R for a particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS). RSs may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

[0070] Figure 2BExamples of various DL channels within a subframe of a frame are explained. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising 6 RE Groups (REGs), each REG comprising 12 coherent REs in the OFDM symbols of the RB. A PDCCH within a BWP may be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a shared search space, a UE-specific search space) during PDCCH monitoring on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies spanning the channel bandwidth. The Primary Synchronization Signal (PSS) may be located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identity. The Secondary Synchronization Signal (SSS) may be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identity Group Number and radio frame timing. Based on the Physical Layer Identity and the Physical Layer Cell Identity Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Block (SIB)), and paging messages.

[0071] As in Figure 2C As explained, some REs carry DM-RS for channel estimation at the base station (indicated as R for a specific configuration, but other DM-RS configurations are possible). The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or first two symbols of the PUSCH. The PUCCH DM-RS can be transmitted in different configurations depending on whether a short or long PUCCH is being transmitted and on the specific PUCCH format used. The UE can transmit a probe reference signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the combs. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0072] Figure 2DExamples of various UL channels within a subframe of a frame are explained. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) information (ACK / NACK (NACK)) feedback. The PUCCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCI.

[0073] Figure 4 Examples 400 and 410 illustrate example time slot structures that can be used for wireless communication (e.g., for sidelink communication) between UE 104 and UE 104'. The time slot structure can be within a 5G / NR frame structure. While the following description may focus on 5G NR, the concepts described herein are applicable to other similar domains such as LTE, LTE-A, CDMA, GSM, and other wireless technologies. This is merely an example, and other wireless communication technologies may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include mini-time slots, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, while for time slot configuration 1, each time slot may include 7 symbols. Figure 400 illustrates a single timeslot transmission, which may correspond to a 0.5ms transmission time interval (TTI). Figure 410 illustrates Example 2 timeslot aggregation, for example, the aggregation of two 0.5ms TTIs. Figure 400 illustrates a single RB, while Figure 410 illustrates N RBs. In Figure 410, the 10 RBs used for control are merely an example. The number of RBs can vary.

[0074] A resource grid can be used to represent the frame structure. Each time slot may include a resource block (RB) extending for 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme. Figure 4 As explained in the text, some REs may include control information, for example, along with demodulation RS (DMRS). Figure 4 It also explains that (various) symbols may include CSI-RS. Figure 4Symbols dedicated to DMRS or CSI-RS indicate that the symbol includes a DMRS or CSI-RS RE. Such symbols may also include REs containing data. For example, if the number of ports for DMRS or CSI-RS is 1 and comb-2 mode is used for DMRS / CSI-RS, half of the REs may include the RS, while the other half may include data. CSI-RS resources may begin with any symbol in a time slot and may occupy 1, 2, or 4 symbols, depending on the configured number of ports. CSI-RS may be periodic, semi-persistent, or aperiodic (e.g., triggered based on control information). For time / frequency tracking, CSI-RS may be periodic or aperiodic. CSI-RS may be transmitted in bursts of two or four symbols spread across one or two time slots. Control information may include sidelink control information (SCI). At least one symbol may be used for feedback, as described herein. Symbols before and / or after feedback may be used to transition between data reception and feedback transmission. Although symbol 12 is interpreted as being used for data, it can be modified to be a gap symbol to allow for feedback in symbol 13. Another symbol (e.g., at the end of a time slot) can be used as a gap. This gap allows the device to (e.g., in a subsequent time slot) switch from operating as a transmitting device to preparing to operate as a receiving device. As explained, data can be transmitted in the remaining REs. This data may include the data message described herein. The position of any of the SCI, feedback, and LBT symbols may be related to... Figure 4 The examples described in the text are different. Multiple time slots can be aggregated together. Figure 4 An example aggregation of two time slots is also explained. The number of time slots aggregated can also be greater than two. When time slots are aggregated, the symbols and / or gap symbols used for feedback can be different from the symbols and / or gap symbols used for feedback in a single time slot. Although feedback is not explained for this aggregation example, symbols(s) in a multi-time-slot aggregation can also be assigned for feedback, as explained in the single-slot example.

[0075] Figure 3 This is a block diagram showing a first communication device 310 and a second communication device 350 communicating. In some examples, communication between communication devices 310 and 350 may be based on a side link. For example, the first communication device may include a transmitting device (e.g., Figure 1 UE 104), which uses a second communication device 350 (e.g., Figure 1 The first communication device 310 (RSU 107) communicates with one or more target devices. The first communication device 310 can communicate with the second communication device 350 using sidelink communication. The first communication device 310 and / or the second communication device 350 may include UE, access point, base station, roadside unit (RSU), etc.

[0076] In some examples, communication between communication devices 310 and 350 can occur within an access network. For example, the first communication device 310 may include a base station (e.g., Figure 1 The base station 102 or 180), and the second communication device 350 may include a UE (e.g., Figure 1 (UE 104).

[0077] In the DL, IP packets from EPC 160 can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration of UE measurement reports; PDCP layer functionality associated with header compression / decompression, security (cryptography, cryptographic decoding, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with upper-layer packet data unit (PDU) delivery, error correction via ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto transport blocks (TBs), demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority differentiation.

[0078] Transmit (TX) processors (e.g., TX processor 316) and receive (RX) processors (e.g., RX processor 370) implement Layer 1 functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation 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 decoded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and subsequently combined using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM streams are spatially precoded to generate multiple spatial streams. The channel estimate from the channel estimator 374 can be used to determine the coding and modulation scheme and for spatial processing. This channel estimate can be derived from the reference signal and / or channel condition feedback transmitted by the second communication device 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can modulate an RF carrier with the corresponding spatial stream for transmission.

[0079] At the second communication device 350, each receiver 354RX receives signals via its corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides this information to the 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 can perform spatial processing on the information to recover any spatial stream destined for the second communication device 350. If multiple spatial streams are destined for the second communication device 350, they can be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the signal constellation points most likely to have been transmitted by the first communication device 310. These soft decisions can be based on a channel estimate calculated by the channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the original data and control signals transmitted by the first communication device 310 over the physical channel. This data and control signals are then provided to the controller / processor 359 that implements layer 3 and layer 2 functionality.

[0080] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The 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, cipher decoding, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0081] Similar to the functionality described in conjunction with DL transmissions performed by the first communication device 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) capture, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (cryptography, cryptographic decoding, integrity protection, integrity verification); RLC layer functionality associated with the transmission of upper-layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto TBs, demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority differentiation.

[0082] The channel estimate derived by the channel estimator 358 from the reference signal or feedback transmitted by the first communication device 310 can be used by the TX processor 368 to select appropriate coding and modulation schemes and to facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX can use its respective spatial stream to modulate an RF carrier for transmission.

[0083] UL transmission is processed at the first communication device 310 in a manner similar to that described in conjunction with the receiver function at the second communication device 350. Each receiver 318RX receives signals via its respective antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides that information to the RX processor 370.

[0084] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between the transport and logical channels, packet reassembly, cipher decoding, header decompression, and control signal processing to recover IP packets from the second communication device 350. IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0085] In the aspect where the first communication device 310 is communicating with the second communication device 350 via a sidelink, at least one of the TX processor 316 or 368, the RX processor 356 or 370, and the controller / processor 359 or 375 can be configured to perform combined operations. Figure 1 The various aspects of the UE mobility component 198.

[0086] In the aspect of the first communication device 310 including a base station, at least one of the TX processor 316, the RX processor 370, and the controller / processor 375 can be configured to perform combined Figure 1 The various aspects of the base station mobility component 199.

[0087] In some examples, the UE can establish a connection with the base station to facilitate communication, and can establish a sidelink connection with a sidelink device to operate as an auxiliary node to facilitate the communication. Figure 5 This is an example diagram illustrating wireless communication 500 between devices based on sidelink-assisted access link connectivity, according to the teachings disclosed herein. The example wireless communication 500 implements non-autonomous millimeter-wave (“mmW”) communication without a RAT-specific anchor (such as an LTE anchor or a 5G NR anchor).

[0088] like Figure 5 As shown, the wireless communication 500 includes a UE 504 communicating with a base station 502 and a side link device 506. The base station 502 and the side link device 506 are in communication with a control unit 508. Various aspects of the base station 502 can be... Figure 1 This is achieved using base stations 102 / 180. Various aspects of UE 504 can be implemented by... Figure 1 This is implemented by UE 104. Various aspects of the sidelink device 506 can be achieved by sidelink devices (such as...) Figure 1 This can be achieved using UE 104' and / or RSU 107). Various aspects of the control unit 508 can be implemented by... Figure 1 The core network 190 is used to achieve this.

[0089] exist Figure 5In the illustrated example, base station 502 is configured to operate at mmW frequencies and / or near-mmW frequencies. UE 504 can establish an access link connection 510 (sometimes referred to as a "Uu link") with base station 502. Base station 502 can communicate with control unit 508 via a first network interface 512. Communication within mmW frequencies can provide high throughput and is therefore advantageous for transmitting data between UE 504 and base station 502. However, communication within mmW frequencies may also be susceptible to service interruptions (e.g., due to congestion).

[0090] In some examples, to reduce service interruptions, UE 504 may also establish a connection with sidelink device 506. For example, UE 504 may establish a sidelink connection 514 (sometimes referred to as a "PC5 link") with sidelink device 506. Sidelink device 506 may communicate with control unit 508 via a second network interface 516.

[0091] Sidelink communication enables UE 504 to communicate directly with another UE. For example, UE 504 and sidelink device 506 can communicate without routing through base station 502. As an example, sidelinks can facilitate vehicle-based communication, allowing a vehicle UE to communicate directly with another UE associated with, for example, another vehicle, vulnerable road users (e.g., pedestrians, cyclists), network nodes, infrastructure nodes, etc. The sidelinks and aspects presented herein are not limited to vehicle applications and can be applied to other types of sidelink devices.

[0092] In the illustrated example, sidelink device 506 is configured to operate in sub-6 GHz frequencies. Communication in the sub-6 GHz spectrum is more robust than communication in mmW frequencies. By establishing a sidelink connection 514 with sidelink device 506, sidelink device 506 can act as an anchor node for UE 504 to perform mmW communication on that sidelink connection 514. For example, sidelink connection 514 can provide a reliable control plane to manage access link connection 510 between UE 504 and base station 502. Sidelink connection 514 can also provide a fallback user plane to reduce service interruptions. That is, UE 504 can communicate control signaling (e.g., send and / or receive control signaling from) base station 502 via sidelink device 506, while simultaneously communicating data directly with base station 502 via access link connection 510. In some such examples, control signaling may include encapsulated messages so that the control signaling is transparent to sidelink device 506. For example, side link device 506 may forward control signaling to and / or from side link device 506 while abandoning the processing of such control signaling.

[0093] Figure 6 This is another example illustration of wireless communication 600 between devices based on sidelink-assisted access link connectivity, according to the teachings disclosed herein. In the illustrated example, wireless communication 600 includes a UE 604, a base station 602, an RSU 606, and a control unit 608. The example control unit 608 includes a control plane component 610 in communication with a user plane component 612. The control plane component 610 can be configured to perform control plane functions. The user plane component 612 can be configured to perform user plane functions, such as routing and forwarding user plane packets. Aspects of the base station 602 can be... Figure 1 Base stations 102 / 180 and / or Figure 5 This is achieved through base station 602. Various aspects of UE 604 can be implemented by... Figure 1 UE 104, and / or Figure 5 This is implemented using UE 504. Various aspects of RSU 606 can be achieved by sidelink devices (such as...). Figure 1 UE 104' and / or RSU 107, and / or Figure 5 This is achieved through the side link device 506. Various aspects of the control unit 608 can be implemented by... Figure 1 Core network 190, and / or Figure 5 It is implemented using the core unit 508.

[0094] like Figure 6 As shown, UE 604 is in communication with base station 602 and sidelink devices (e.g., RSU 606). UE 604 may communicate with base station 602 via a Uu link facilitating communication in mmW (or near mmW) frequencies. UE 604 may communicate with RSU 606 via a PC5 link facilitating sub-6 GHz frequencies.

[0095] RSU 606 communicates with base station 602 via network interface 620. In some examples, network interface 620 may be implemented via IP tunneling, such as an Xn (or Xn-like) interface, or any other network interface with IP. In some examples, network interface 620 may be implemented via a shared interface.

[0096] Base station 602 can communicate with control unit 608 via N2 and N3 interfaces. For example, base station 602 can communicate control plane packets with control plane component 610 via N2 interface. Base station 602 can communicate user plane packets with user plane component 612 via N3 interface. In some examples, control unit 608 can communicate with UE 604. For example, control plane component 610 of control unit 608 can communicate with UE 604 via N1 interface.

[0097] In the illustrated example, RSU 606 is configured to operate as an auxiliary node (AN), while base station 602 is configured to operate as a primary node (PN) relative to UE 604. In some such examples, UE 604 can transmit and / or receive control signaling from base station 602 via RSU 606. UE 604 can transmit and / or receive data from base station 602 via the Uu link. In some examples, UE 604 can transmit and / or receive data from base station 602 via RSU 606. For example, RSU 606 can operate as a data backoff mechanism.

[0098] In the illustrated example, control signaling communication can be transparent to the RSU 606. For example, control signaling may be encapsulated in messages, and the RSU 606 may not be able to determine what information is encapsulated.

[0099] Figure 7 This is a diagram illustrating an example system 700 based on sidelink communication and access link communication, according to the teachings disclosed herein. Sidelink communication can be based on, but is not limited to, a combination of... Figure 4 The time slot structure is described in various aspects. For example, the first UE 702 can transmit transmission 714, including, for example, a control channel (e.g., PSCCH) and / or a corresponding data channel (e.g., PSSCH), which can be received directly from the first UE 702 by the second UE 704, the third UE 706, the fourth UE 708, and / or the RSU 710, for example, without transmission through a base station. In addition to operating as receiving devices, UEs 702, 704, 706, 708, and RSU 710 can also each operate as transmitting devices. Therefore, the second UE 704 is interpreted as transmitting transmission 722, the third UE 706 as transmitting transmission 716, the fourth UE 708 as transmitting transmission 718, and the RSU 710 as transmitting transmission 720. Transmissions 714, 716, 718, 720, and 722 can be broadcast or multicast to nearby devices. For example, the first UE 702 may transmit communications intended to be received by other UEs within the range 701 of the first UE 702.

[0100] The first UE 702 can provide sidelink control information (SCI) containing information for decoding the corresponding data channel. The SCI may also include information that the receiving device can use to avoid interference. For example, the SCI may indicate the time-frequency resources occupied by the data transmission and may be indicated in a control message from the transmitting device.

[0101] In some examples, a base station can communicate with one or more communication devices within its range. For example, Figure 7Examples include a first base station 730, which can communicate 734 with communication devices (such as a first UE 702, a third UE 706, a fourth UE 708 and / or an RSU 710) within a range 740 of the first base station 730. Figure 7 Examples also include a second base station 732, which can communicate 736 with communication devices (such as the first UE 702, the second UE 704, the fourth UE 708 and / or the RSU 710) within the range 742 of the second base station 732.

[0102] In the examples disclosed herein, the UE can establish a sidelink connection with a sidelink device and an access link connection with a base station, for example, as in combination with Figure 5 And / or as described in 6. For example, the first UE 702 can establish a sidelink connection with RSU 710 (e.g., Figure 6 Example PC5 link) and establish an access link connection with the first base station 730 (e.g., Figure 6 (Example Uu link). In some such examples, the first UE 702 and the first base station 730 can directly communicate data via an access link connection between the first UE 702 and the first base station 730. The first UE 702 and the first base station 730 can communicate control signaling via RSU 710. For example, the first UE 702 can transmit control signaling to RSU 710 via a sidelink connection, and RSU 710 can transmit control signaling via the network interface between RSU 710 and the first base station 730 (e.g., ...). Figure 6 Example network interface 620 in the document forwards the control signaling to the first base station 730. As used herein, when a UE establishes a connection with a device, the device may be referred to as a "serving" device or a "source" device. For example, the first base station 730 may be referred to as a serving base station or a source base station, and the RSU 710 may be referred to as a serving RSU or a source RSU.

[0103] In some respects, the characteristics of sidelink and / or access link connections can trigger a UE to execute mobility procedures, whereby the UE establishes a new connection with a new sidelink device and / or a new base station. For example, triggering a UE to execute mobility procedures can be based on measurements of the sidelink and / or access link connections. In some examples, triggering a UE to execute mobility procedures can be based on the detection of a radio link failure (RLF) associated with that sidelink and / or access link connection.

[0104] The aspects disclosed herein provide techniques for enabling a UE to perform mobility procedures. In some examples, performing mobility procedures may include performing an inter-PN change, wherein the UE establishes an access link connection with a new base station. For example, a first UE 702 may release its access link connection with a first base station 730 and establish a new access link connection with a target (or new) base station (e.g., a second base station 732). In some examples, the first UE 702 may determine to perform an inter-PN change based on Radio Resource Management (RRM) measurements associated with the access link connection between the first base station 730 and the first UE 702. For example, the first UE 702 may determine that RRM measurements associated with the access link connection (e.g., Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), etc.) have failed to meet thresholds. The first UE 702 may perform the inter-PN change from the first base station 730 to the target base station (e.g., the second base station 732) via a handover procedure.

[0105] In some examples, the first UE 702 may also establish a new sidelink connection with the target sidelink device when performing an inter-PN change. It will be understood that in some examples, the serving sidelink device and the target sidelink device may include the same sidelink device, but aspects of the sidelink connection with the serving sidelink device and the new sidelink connection with the target sidelink device may differ, for example, because the serving base station and the target base station are different base stations.

[0106] In some examples, performing mobility procedures may include performing inter-AN changes, whereby the UE establishes a sidelink connection with a new sidelink device. For example, when the sidelink connection with the serving sidelink device (e.g., RSU 710) does not meet the sidelink connection threshold, the first UE 702 may detect the presence of a set of sidelink devices (e.g., such as the second UE 704, the third UE 706, and / or the fourth UE 708) that meet the sidelink connection threshold. The first UE 702 may select a target sidelink device from the set of sidelink devices and establish a new sidelink connection with that target sidelink device. In some examples, the sidelink connection threshold may be pre-configured. In some examples, the first UE 702 may receive the sidelink connection threshold from the base station, for example, via a System Information Block (SIB) or via RRC signaling.

[0107] In some examples, performing an inter-AN change can also enable the UE to determine whether the serving side link device and the target side link device are communicating with the same base station or different base stations. For example, when the serving side link device and the target side link device are communicating with the same base station, the UE can send a notification to the target side link device regarding the communication between the same base station and both the serving side link device and the target side link device (e.g., in the case of intra-PN and inter-AN changes). In some such examples, this notification can trigger the target side link device to exchange configuration information with the base station so that the target side link device can operate as an auxiliary node for communication between the base station and the UE.

[0108] For example, the first UE 702 can determine to perform an inter-AN change by executing a UE-controlled RSU (re)selection procedure and switch from RSU 710 to the third UE 706. The first UE 702 can establish a sidelink connection with the third UE 706. The first UE 702 can also determine that RSU 710 and the third UE 706 are associated with the same base station (e.g., the first base station 730). In some such examples, the first UE 702 can transmit to the third UE 706 a notification that the inter-AN change from RSU 710 to the third UE 706 satisfies both intra-PN and inter-AN changes. The third UE 706 can then notify the first base station 730 of the inter-AN change, which can cause the first base station 730 to reconfigure the third UE 706 to operate as an auxiliary node for both the first UE 702 and the first base station 730.

[0109] In an example where the serving sidelink device and the target sidelink device are communicating with different base stations, the UE can release the access link connection with the serving base station after establishing a sidelink connection with the target sidelink device. Then, the UE can establish an access link connection with the target base station via the sidelink connection with the target sidelink device.

[0110] For example, the first UE 702 can determine to perform an inter-AN change by executing a UE-controlled RSU (re)selection procedure and switch from the third UE 706 to the second UE 704. The first UE 702 can establish a sidelink connection with the second UE 704. The first UE 702 can also determine that the third UE 706 and the second UE 704 are associated with different base stations. For example, the third UE 706 is communicating with the first base station 730, and the second UE 704 is communicating with the second base station 732. In some such examples, after establishing a new sidelink connection with the second base station 732, the first UE 702 can release the access link connection with the first base station 730 and transmit an access link connection request to the second base station 732 via the second UE 704. For example, the first UE 702 can transmit an RRC reconstruction request to the second UE 704 via the new sidelink connection, and the second UE 704 can forward (or relay) the RRC reconstruction request to the second base station 732. In some examples, the second UE 704 and the second base station 732 can exchange messages to configure the second UE 704 to operate as an auxiliary node to the first UE 702 and the second base station 732. The second base station 732 can also exchange messages with the first base station 730 to obtain UE context information associated with the first UE 702. Obtaining UE context information from the first base station 730 can reduce UE signaling overhead by foregoing the request for UE context information from the first UE 702. The second base station 732 and the first UE 702 can then establish an access link connection by exchanging RRC reconstruction messages via the second UE 704.

[0111] In some examples, when performing an inter-AN change, the UE can determine whether the serving sidelink device and the target sidelink device are associated with the same base station or different base stations based on a discovery message broadcast by the sidelink device. This discovery message may include the PN identifier of the base station communicating with the sidelink device. For example, a third UE 706 may broadcast a discovery message including a PN identifier corresponding to a first base station 730. A second UE 704 may broadcast a discovery message including a PN identifier corresponding to a second base station 732. A fourth UE 708 and RSU 710 may broadcast a discovery message including a first PN identifier corresponding to the first base station 730 and a second PN identifier corresponding to the second base station 732.

[0112] In some examples, the UE may determine to execute mobility procedures based on a detected RLF associated with a sidelink connection and / or access link connection. For example, the UE may detect an RLF associated with the Uu link between the UE and the base station (e.g., a primary cell group (PCG) failure). It will be understood that aspects of a primary cell group can be similar to a primary cell group (MCG). In some examples where the UE detects an RLF associated with the Uu link, the UE may attempt to perform a fast PCG recovery. For example, the UE may abandon the initialization of an RRC reconstruction procedure based on the detected Uu link RLF. In some such examples, the UE may transmit a PCG failure indication to the serving base station via the serving sidelink device and the corresponding PC5 connection. The PCG failure indication may include one or more of the following: access link measurements associated with an available base station and an identifier associated with the corresponding base station; sidelink measurements associated with an available sidelink device and an identifier associated with the corresponding sidelink device and its corresponding base station (e.g., a PN identifier); and failure cause information. Examples of access link measurements include RRM measurements such as RSRP, RSRQ, etc. Examples of identifiers associated with a corresponding base station include the Physical Cell Identifier (PCI) or the Cell Global Identity (CGI). Examples of sidelink measurements include the RSRP of a discovery message and / or the Sidelink Synchronization Signal (SLSS) broadcast by a sidelink device. Examples of faults caused by information include RLF, handover failure, IP check failure, and RRC reconfiguration failure.

[0113] Based on the PCG fault indication, the serving base station can determine the handover procedure to be executed with the target base station. For example, the serving base station can transmit a handover request to the target base station. Then, the target base station can exchange message transmissions with the serving side link device to configure the serving side link device to operate as an auxiliary node for both the UE and the target base station. Based on the handover confirmation message from the target base station, the serving base station can transmit a target node configuration message to the UE, enabling the UE to establish an access link connection with the target base station.

[0114] In some examples, after the UE transmits a PCG fault indication to the serving base station via the source-side link device, the UE can initiate a timer. If the UE does not receive a target node configuration message from the serving base station before the timer expires, the UE can initiate an RRC reconstruction procedure to establish an access link connection with the base station.

[0115] In some examples, the UE can detect an RLF (e.g., a secondary cell group (ACG) failure) associated with the PC5 link between the UE and the sidelink device. It will be understood that aspects of a secondary cell group can be similar to a sub-cell group (SCG). In examples where the UE detects an RLF associated with the PC5 link between the UE and the sidelink device, the UE can perform an inter-AN change.

[0116] In some examples, if the UE detects an RLF associated with the Uu link between the base station and the UE, and an RLF associated with the PC5 link between the UE and the sidelink device, the UE may abandon the fast PCG recovery and initiate an RRC reconstruction procedure.

[0117] Figure 8 An example communication flow 800 between UE 804, source AN 806, source PN 808, target AN 810, and target PN 812, as presented herein, is described. In the described example, source AN 806 and source PN 808 are communicating (e.g., via a first network interface 807), and target AN 810 and target PN 810 are communicating (e.g., via a second network interface 811). In the described example, UE 804 and source AN 806 are connected via a sidelink (such as...). Figure 5 Side link connection 514 and / or Figure 6 The PC5 link is in communication. Example UE 804 and source PN 808 are connected via an access link (such as...). Figure 4 Access link connection 510 and / or Figure 6 The Uu link is in communication.

[0118] Various aspects of UE 804 can be derived from Figure 1 UE 104 Figure 5 UE 504 Figure 6 UE 604, and / or Figure 7 The first UE 702 is used for implementation. Various aspects of the source AN 806 and the target AN 810 can be implemented by sidelink devices, such as... Figure 1 Example RSU 107 Figure 5 Side link device 506, Figure 6 RSU 606, and / or Figure 7 UEs 704, 706, 708, and / or RSU 710. Various aspects of the source PN 808 and target PN 812 can be implemented by the base station, such as... Figure 1 Base station 102 / 180 Figure 5 Base station 502 Figure 6 Base station 602, and / or Figure 7The first base station 730 and / or the second base station 732. Various aspects of network interfaces 807 and 811 can be provided by... Figure 6 It is implemented using the network interface 620.

[0119] In the illustrated example, communication flow 800 facilitates UE 804 to perform an inter-PN change. For example, regarding Figure 7 For example, communication flow 800 can facilitate the first UE 702 to perform mobility procedures to switch from communication with the first base station 730 to communication with the second base station 732.

[0120] exist Figure 8 In the illustrated example, at 820, UE 804 detects the occurrence of a measurement report trigger. UE 804 can detect the occurrence of a measurement report trigger based on measurements associated with the access link connection between UE 804 and source PN 808. For example, UE 804 can perform RRM measurements on the access link connection with source PN 808 and determine that the RRM measurement (e.g., RSRP, RSRQ, etc.) does not meet a threshold (e.g., the RRM measurement is worse than the threshold). In some examples, this threshold can be pre-configured. In some examples, UE 804 can receive this threshold from the base station (e.g., source PN 808), for example, via SIB or via RRC signaling.

[0121] In some examples, UE 804 can be configured with measurement gaps associated with performing measurements related to the occurrence of detection measurement reports. For example, source PN 808 can configure per-UE gaps or per-frequency-range gaps for UE 804. Source PN 808 can configure this measurement gap for UE 804 via a sidelink connection between UE 804 and source AN 806. Per-UE gaps can configure UE 804 to apply the same gap pattern when performing measurements regarding the access link connection between UE 804 and source PN 808 and when performing measurements regarding the sidelink connection between UE 804 and source AN 806. Per-frequency-range gaps can configure UE 804 to apply a first gap pattern when performing measurements regarding the access link connection between UE 804 and source PN 808, and a second gap pattern when performing measurements regarding the sidelink connection between UE 804 and source AN 806.

[0122] UE 804 transmits measurement report 822 to source PN 808. (For example...) Figure 8As shown, UE 804 transmits measurement report 822 to source PN 808 via source AN 806. For example, UE 804 can transmit measurement report 822 to source AN 806 via a sidelink connection between UE 804 and source AN 806, and source AN 806 can forward measurement report 822 to source PN 808 via first network interface 807.

[0123] Measurement report 822 may include available access link measurements and corresponding cell identifiers. Examples of access link measurements include RRM measurements associated with source PN 808 and any additional available base stations (e.g., target PN 812). Examples of cell identifiers include PCI and CGI. Measurement report 822 may additionally or alternatively include any available sidelink measurements for serving and neighboring sidelink devices, identifiers associated with the respective serving and neighboring sidelink devices, and the PN identifier of the master node associated with each of the respective serving and neighboring sidelink devices. Examples of sidelink measurements include RSRP measurements based on discovery messages (e.g., sidelink discovery-RSRP (SD-RSRP) measurements) or RSRP measurements based on SLSS received from serving and neighboring sidelink devices (such as source AN 806 and target AN 810). Examples of PN identifiers include cell identifier, PCI and frequency, or CGI.

[0124] At 824, source PN 808 determines that a switchover needs to be performed. For example, source PN 808 may determine that one or more measurements included in measurement report 822 are eligible to perform an inter-PN change from source PN 808 to a new PN (e.g., target PN 812).

[0125] Source PN 808 transmits a handover request 826, which is received by target PN 812. For example... Figure 8 As shown, the handover request 826 may include sidelink measurements. For example, the handover request 826 may include sidelink measurements for the serving and adjacent sidelink devices included in the measurement report 822.

[0126] In step 828, target PN 812 selects a sidelink device to operate as an auxiliary node for both UE 804 and target PN 812. For example, target PN 812 may select the sidelink device based on sidelink measurements included in handover request 826. Figure 8As shown, target PN 812 selects target AN 810 at 828 to operate as an auxiliary node for UE 804 and target PN 812. For example, target PN 812 transmits an AN add request 830, which is received by target AN 810. Target PN 812 may transmit the AN add request 830 via a second network interface 811. The AN add request 830 may include information associated with UE 804 to configure target AN 810 to operate as an auxiliary node for UE 804 and target PN 812. Target AN 810 transmits an AN add acknowledgment (ACK) 832, which is received by target PN 812. Target AN 810 may transmit the AN add ACK 832 via the second network interface 811. The AN add ACK 832 may indicate that target AN 810 is configured to operate as an auxiliary node for UE 804 and target PN 812.

[0127] In the illustrated example, target PN 812 transmits a handover ACK message 834, which is received by source PN 808. The handover ACK message 834 includes configuration information for target PN 812 and target AN 810. For example, this configuration information enables UE 804 to establish a sidelink connection with target AN 810 and an access link connection with target PN 812.

[0128] Source PN 808 transmits RRC reconfiguration message 836, which is received by UE 804. In the illustrated example, source PN 808 transmits RRC reconfiguration message 836 to UE 804 via source AN 806. For example, source PN 808 may transmit RRC reconfiguration message 836 to source AN 806 via first network interface 807, and source AN 806 may forward RRC reconfiguration message 836 to UE 804 via a sidelink connection between UE 804 and source AN 806. In the illustrated example, RRC reconfiguration message 836 includes configuration information for target PN 812 and target AN 810 received by source PN 808 from target PN 812 via handover ACK message 834. This configuration information enables UE 804 to establish a sidelink connection with target AN 810 and an access link connection with target PN 812.

[0129] At 838, UE 804 establishes a sidelink connection 839 with the target AN 810. The sidelink connection 839 may include a PC5 unicast link, such as a PC5-RRC link or a PC5-S link. UE 804 may use the configuration information for the target AN 810 included in the RRC reconfiguration message 836 to establish the sidelink connection 839.

[0130] UE 804 executes the Random Access Channel (RACH) procedure 840 to establish an access link connection with target PN 812. UE 804 can use the configuration information for target PN 812 included in RRC reconfiguration message 836 to establish the access link connection.

[0131] UE 804 transmits an RRC reconfiguration complete message 842, which is received by target PN 812. In the illustrated example, UE 804 transmits the RRC reconfiguration complete message 842 to target PN 812 via target AN 810. For example, UE 804 may transmit the RRC reconfiguration complete message 842 to target AN 810 via sidelink connection 839, and target AN 810 may forward the RRC reconfiguration complete message 842 to target PN 810 via the second network interface 811.

[0132] Then, UE 804 and target PN 812 can continue to transmit data via the access link connection between UE 804 and target PN 812.

[0133] In the illustrated example, target PN 812 selects target AN 810 as an auxiliary node between UE 804 and target PN 812 for operation. For example... Figure 8 As shown, target AN 810 and source AN 806 are different auxiliary nodes. In other examples, target PN 812 may select the same sidelink device as source AN 806 to operate as an auxiliary node. For example, target PN 812 may select source AN 806 as an auxiliary node based on sidelink measurements included in handover request 826. In some such examples, UE 804 may abandon establishing sidelink connection 839 because UE 804 is already in a connection with the selected sidelink device (e.g., source AN 806).

[0134] In the illustrated example, after executing RACH procedure 840, UE 804 transmits an RRC reconfiguration complete message 842 to target PN 812 via target AN 810. However, it can be understood that UE 804 may transmit the RRC reconfiguration complete message 842 to target PN 812 before or as part of executing RACH procedure.

[0135] Figure 9An example communication flow 900 between UE 904, source AN 906, source PN 908, and target AN 910, as presented herein, is described. In the described example, source AN 906 and source PN 908 are communicating (e.g., via a first network interface 907), and target AN 910 and source PN 908 are communicating (e.g., via a second network interface 911). Source PN 908 may communicate with control unit 912 (such as...). Figure 5 Example control unit 508 and / or Figure 6 The control unit 608 is in communication. In the illustrated example, UE 904 and source AN 906 are in communication via side link connection 905. Example UE 904 and source PN 908 are in communication via access link connection 909.

[0136] UE 904's various aspects can be derived from Figure 1 UE 104 Figure 5 UE 504 Figure 6 UE 604, and / or Figure 7 The first UE 702 is used for implementation. Various aspects of the source AN 906 and the target AN 910 can be implemented by sidelink devices, such as... Figure 1 Example RSU 107 Figure 5 Side link device 506, Figure 6 RSU 606, and / or Figure 7 UEs 704, 706, 708 and / or RSU 710. Various aspects of the source PN 908 can be implemented by the base station, such as... Figure 1 Base station 102 / 180 Figure 5 Base station 502 Figure 6 Base station 602, and / or Figure 7 The first base station 730 and / or the second base station 732. The various aspects of the side link connection 905 can be provided by... Figure 5 Side link connection 514 and / or Figure 6 This is achieved through the PC5 link. The various aspects of the access link connecting to the 909 can be handled by... Figure 5 Access link connection 510 and / or Figure 6 This is achieved through the Uu link. Various aspects of the network interfaces 907 and 911 can be implemented by... Figure 6 It is implemented using the network interface 620.

[0137] In the illustrated example, communication flow 1000 facilitates UE 1004 to perform intra-PN and inter-AN changes. For example, regarding Figure 7For example, a first UE 702 may be communicating with an RSU 710 via a sidelink connection and with a first base station 730 via an access link connection. Communication flow 1000 may enable the first UE 702 to perform mobility procedures to switch from communicating with the RSU 710 to communicating with a third UE 706, wherein the RSU 710 and the third UE 706 are each communicating with the first base station 730.

[0138] Source AN 906 transmits discovery message 920 via sidelink connection 905, which is received by UE 904. Source AN 906 may broadcast discovery message 920 periodically, aperiodically, and / or as a one-off event. Discovery message 920 enables UE 904 to perform sidelink measurements on sidelink connection 905 (e.g., for measuring RSRP). In some examples, discovery message 920 may include SLSS and UE 904 may measure the RSRP of SLSS. In some examples, discovery message 920 may include a sidelink discovery (SD) message broadcast via a dedicated logical channel and UE 904 may measure the RSRP of the SD message (e.g., SD-RSRP).

[0139] In the illustrated example, discovery message 920 includes a PN identifier 921 that identifies the master node communicating with the source AN 906. For example, the PN identifier 921 may include an identifier associated with the source PN 908. The PN identifier 921 may include one or more of the following: cell identifier, PCI and frequency, or CGI.

[0140] In step 922, UE 904 determines that the sidelink connection with the source AN fails to meet a threshold (e.g., a quality threshold). For example, UE 904 may perform an RSRP measurement based on discovery message 920 and determine that the measured RSRP is below (or worse than) a threshold. In some examples, this threshold may be pre-configured. In some examples, UE 904 may receive this threshold from the base station (e.g., source PN 908), for example, via SIB or via RRC signaling.

[0141] In the illustrated example, UE 904 receives discovery message 924 from target AN 910. Aspects of discovery message 924 may be similar to discovery message 920. Example discovery message 924 includes a PN identifier 925 that identifies the master node communicating with target AN 910. In the illustrated example, PN identifier 925 indicates that target AN 910 is communicating with source PN 908.

[0142] although Figure 9The example illustrates that UE 904 receives discovery message 920 before the determination at 922 and discovery message 924 after the determination at 922. However, it can be understood that in other examples, UE 904 may receive discovery message 924 before or during the determination at 922. Additionally, it can be understood that UE 904 may receive discovery messages from a set of sidelink devices, such as source AN 906, target AN 910, and one or more adjacent sidelink devices. For example, regarding... Figure 7 For example, the first UE 702 can receive discovery messages from one or more of RSU 710 and UEs 704, 706, and 708.

[0143] In 926, UE 904 selects a sidelink device to operate as an auxiliary node. UE 904 can select the sidelink device based on the sidelink measurement performed on the received discovery message. In some examples, UE 904 can select the sidelink device associated with the strongest sidelink measurement. In some examples, UE 904 can select the sidelink device by first identifying which sidelink devices meet higher-level criteria, and then selecting the sidelink device with the strongest sidelink measurement (e.g., best RSRP) from the identified sidelink devices. For example, regarding... Figure 7 For example, the first UE 702 can receive discovery messages from one or more of RSU 710 and UEs 704, 706, and 708. Then, the first UE 702 can identify that the third UE 706 and the fourth UE 708 meet higher-level criteria, and that the third UE 706 is associated with the strongest sidelink measurement.

[0144] Return to Figure 9 For example, in 928, UE 904 determines that the serving AN and the target AN are associated with the same master node. For instance, UE 904 can compare PN identifier 921 and PN identifier 925 and determine that they both correspond to the same master node (e.g., source PN 908).

[0145] At 930, UE 904 establishes a sidelink connection with target AN 910. The sidelink connection 931 may include a PC5 unicast link, such as a PC5-RRC link or a PC5-S link. In some examples, UE 904 may use the configuration information for target AN 910 included in discovery message 924 to establish the sidelink connection 931.

[0146] In the illustrated example, UE 904 transmits an intra-PN change notification 932, which is received by target AN 910. UE 904 can transmit the intra-PN change notification 932 via a sidelink connection 931. For example... Figure 9As shown, the PN change notification 932 includes a source PN identifier 933. The source PN identifier 933 may include the same identifier as the PN identifier 925 and identify the source PN 908.

[0147] Target AN 910 and source PN 908 execute intra-PN change procedure 934. Intra-PN change procedure 934 enables source PN 908 to configure target AN 910 to operate as an auxiliary node for UE 904 and source PN 908. For example, target AN 910 may send a notification to source PN 908 indicating that UE 904 has selected target AN 910. Source PN 908 may send an ACK to target AN 910, indicating that source PN 908 has received notification from target AN 910 that target AN 910 has been selected.

[0148] Source PN 908 transmits RRC reconfiguration message 936, which is received by UE 904. In the illustrated example, source PN 908 transmits RRC reconfiguration message 936 to UE 904 via target PN 910. For example, source PN 908 may transmit RRC reconfiguration message 936 to target AN 910 via second network interface 911, and target AN 910 may forward RRC reconfiguration message 936 to UE 904 via sidelink connection 931. Example RRC reconfiguration message 936 can configure UE 904 to use target AN 910 as an auxiliary node for UE 904 and source PN 908. In some examples, RRC reconfiguration message 936 can reconfigure AN counters (e.g., for security purposes).

[0149] like Figure 9 As shown, UE 904 and source PN 908 can then begin transmitting control signaling 938 via target AN 910. For example, UE 904 can transmit control signaling 938 to target AN 910 using sidelink connection 931, and target AN 920 can forward control signaling 938 to source PN 908 via second network interface 911. In a similar manner, target AN 910 can forward control signaling received from source PN 908 to UE 904.

[0150] As can be understood, in some examples, the target AN 910 can operate as a fallback user plane. For example, the target AN 910 can act as a relay for data transmission between UE 904 and source PN 908.

[0151] Figure 10An example communication flow 1000 between UE 1004, source AN 1006, source PN 1008, target AN 1010, and target PN 1012, as presented herein, is described. In the described example, source AN 1006 and source PN 1008 are communicating (e.g., via a first network interface 1007), and target AN 1010 and source PN 1012 are communicating (e.g., via a second network interface 1011). Source PN 1008 may communicate with a first control unit (such as...). Figure 5 Example control unit 508 and / or Figure 6 The control unit 608 is in communication, and the target PN 1012 may be in communication with a second control unit different from the first control unit. In the illustrated example, UE 1004 and source AN 1006 are connected via a side link (such as...). Figure 5 Side link connection 514, Figure 6 PC5 links, and / or Figure 9 The side link connection (905) is in communication. Example UE 1004 and source PN 1008 are connected via an access link (such as... Figure 5 Access link connection 510, Figure 6 Uu links, and / or Figure 9 The access link connection (909) is in communication.

[0152] Various aspects of UE 1004 can be obtained from Figure 1 UE 104 Figure 5 UE 504 Figure 6 UE 604, and / or Figure 7 The first UE 702 is used for implementation. Various aspects of the source AN 1006 and the target AN 1010 can be implemented by sidelink devices, such as... Figure 1 Example RSU 107 Figure 5 Side link device 506, Figure 6 RSU 606, and / or Figure 7 UEs 704, 706, 708, and / or RSU710. Various aspects of the source PN 1008 and target PN 1012 can be implemented by the base station, such as... Figure 1 Base station 102 / 180 Figure 5 Base station 502 Figure 6 Base station 602, and / or Figure 7 The first base station 730 and / or the second base station 732. Various aspects of network interfaces 1007 and 1011 can be provided by... Figure 6 It is implemented using the network interface 620.

[0153] In the illustrated example, communication flow 1000 facilitates UE 1004 to perform inter-PN and inter-AN changes. For example, regarding Figure 7 For example, a first UE 702 may be communicating with a third UE 706 via a sidelink connection and with a first base station 730 via an access link connection. Communication flow 1000 may cause the first UE 702 to perform mobility procedures to switch from communicating with the third UE 706 to communicating with the second UE 704 (e.g., inter-AN change). However, since the third UE 706 and the second UE 704 are communicating with different base stations, the inter-AN change also triggers an inter-PN change, whereby the first UE 702 releases its access link connection with the first base station 730 and establishes an access link connection with the second base station 732.

[0154] Source AN 1006 transmits discovery message 1020 via the sidelink connection between UE 1004 and source AN 1006, which is received by UE 1004. Source AN 1006 may broadcast discovery message 1020 periodically, aperiodically, and / or as a one-off event. Discovery message 1020 enables UE 1004 to perform sidelink measurements (e.g., to measure RSRP) of the sidelink connection between UE 1004 and source AN 1006. In some examples, discovery message 1020 may include SLSS and UE 1004 may measure the RSRP of SLSS. In some examples, discovery message 1020 may include SD message broadcast via a dedicated logical channel and UE 1004 may measure the RSRP of SD message (e.g., SD-RSRP).

[0155] In the illustrated example, discovery message 1020 includes a PN identifier 1021 that identifies the master node communicating with source AN 1006. For example, PN identifier 1021 may include an identifier associated with source PN 1008. PN identifier 1021 may include one or more of the following: cell identifier, PCI and frequency, or CGI.

[0156] In step 1022, UE 1004 determines that the sidelink connection with the source AN fails to meet a threshold (e.g., a quality threshold). For example, UE 1004 may perform an RSRP measurement based on discovery message 1020 and determine that the measured RSRP is below (or worse than) a threshold. In some examples, this threshold may be pre-configured. In some examples, UE 1004 may receive this threshold from the base station (e.g., source PN 1008), for example, via SIB or via RRC signaling.

[0157] In the illustrated example, UE 1004 receives discovery message 1024 from target AN 1010. Aspects of discovery message 1024 may be similar to discovery message 1020. Example discovery message 1024 includes a PN identifier 1025 that identifies the master node communicating with target AN 1010. In the illustrated example, PN identifier 1025 indicates that target AN 1010 is communicating with target PN 1012.

[0158] although Figure 10 The example illustrates that UE 1004 receives discovery message 1020 before the determination at 1022 and discovery message 1024 after the determination at 1022. However, it can be understood that in other examples, UE 1004 may receive discovery message 1024 before or during the determination at 1022. Additionally, it can be understood that UE 1004 may receive discovery messages from a set of sidelink devices (such as source AN 1006, target AN 1010, and one or more adjacent sidelink devices). For example, regarding... Figure 7 For example, the first UE 702 can receive discovery messages from one or more of RSU 710 and UEs 704, 706, and 708.

[0159] In 1026, UE 1004 selects a sidelink device to operate as an auxiliary node. UE 1004 can select the sidelink device based on the sidelink measurement performed on the received discovery message. In some examples, UE 1004 can select the sidelink device associated with the strongest sidelink measurement. In some examples, UE 1004 can select the sidelink device by first identifying which sidelink devices meet higher-level criteria, and then selecting the sidelink device with the strongest sidelink measurement (e.g., best RSRP) from the identified sidelink devices. For example, regarding... Figure 7 For example, the first UE 702 can receive discovery messages from one or more of RSU 710 and UEs 704, 706, and 708. Then, the first UE 702 can identify that the second UE 704 and the fourth UE 708 meet higher-level criteria, and that the second UE 704 is associated with the strongest sidelink measurement.

[0160] Return to Figure 10 For example, in 1028, UE 1004 determines that the serving AN and the target AN are associated with different master nodes. For example, UE 1004 can compare PN identifier 1021 and PN identifier 1025 and determine that the corresponding master nodes are different (e.g., PN identifier 1021 identifies the source AN 1006 and PN identifier 1025 identifies the target AN 1012).

[0161] At 1030, UE 1004 establishes a sidelink connection 1031 with target AN 1010. Sidelink connection 1031 may include a PC5 unicast link, such as a PC5-RRC link or a PC5-S link. In some examples, UE 1004 may use configuration information for target AN 1010 included in discovery message 1024 to establish sidelink connection 1031.

[0162] At 1032, UE 1004 releases the connection with the source PN. For example, UE 1004 can release the access link connection between UE 1004 and the source PN 1008. Then, UE 1004 can attempt to establish an access link connection with the master node indicated by PN identifier 1025. For example, UE 1004 can transmit an RRC rebuild request message 1034, which is received by the target PN 1012. Figure 10 As shown, UE 1004 transmits RRC reconstruction request message 1034 to target PN 1012 via target AN 1010. For example, UE 1004 can transmit RRC reconstruction request message 1034 to target AN 1010 via sidelink connection 1031, and target AN 1010 can forward RRC reconstruction request message 1034 to target PN 1012 via second network interface 1011.

[0163] Target PN 1012 and target AN 1010 execute AN reselection procedure 1036. For example, target PN 1012 may transmit an AN addition request, which is received by target AN 1010. Target PN 1012 may transmit the AN addition request via the second network interface 1011. Target AN 1010 may transmit an AN addition ACK message, which is received by target PN 1012. Target AN 1010 may transmit the AN addition ACK message via the second network interface 1011. The AN addition ACK message may instruct target AN 1010 to operate as an auxiliary node for UE 1004 and target PN 1012.

[0164] To reduce signaling overhead from UE 1004, target PN 1012 can perform UE context exchange procedure 1038 with source PN 1008. For example, UE context exchange procedure 1038 can enable target PN 1012 to obtain context information related to UE 1004 from source PN 1008 and waive the right to request such information from UE 1004. The UE context information provides target PN 1012 with information about the PDU session to be relocated from source PN 1008 to target PN 1012. Examples of UE context information may include one or more of the following: signaling reference associated with Next Generation Control (NG-C) UE, signaling transport network layer (TNL) associated address on the source NG-C side, UE security capabilities, access layer (AS) security information, index of RAT / frequency selection priority, UE aggregation maximum bit rate, list of PDU session resources to be established, RRC context information, location reporting information, and mobility restriction list.

[0165] In the illustrated example, after executing UE context exchange procedure 1038, target PN 1012 transmits RRC reconstruction completion message 1040, which is received by UE 1004. For example... Figure 10 As shown, target PN 1012 transmits RRC reconstruction completion message 1040 to UE 1004 via target AN 1010. For example, target AN 1010 can receive RRC reconstruction completion message 1040 from target PN 1012 via second network interface 1011, and target AN 1010 can forward RRC reconstruction completion message 1040 to UE 1004 via side link connection 1031.

[0166] UE 1004 transmits RRC reconstruction complete message 1042, which is received by target PN 1012. For example... Figure 10 As shown, UE1004 transmits an RRC reconstruction complete message 1042 to target PN1012 via target AN1010. For example, UE1004 can transmit the RRC reconstruction complete message 1042 to target AN1010 via sidelink connection 1031, and target AN1010 can forward the RRC reconstruction complete message 1042 to target PN1012 via the second network interface 1011.

[0167] Target PN 1012 transmits RRC reconfiguration message 1044, which is received by UE 1004. In the illustrated example, target PN 1012 transmits RRC reconfiguration message 1044 to UE 1004 via target AN 1010. For example, target PN 1012 may transmit RRC reconfiguration message 1044 to target AN 1010 via second network interface 1011, and target AN 1010 may forward RRC reconfiguration message 1044 to UE 1004 via sidelink connection 1031. In the illustrated example, RRC reconfiguration message 1044 includes configuration information for target PN 1012 and target AN 1010.

[0168] UE 1004 executes RACH procedure 1046 to establish an access link connection with target PN 1012. UE 1004 can use the configuration information for target PN 1012 included in RRC reconfiguration message 1044 to establish the access link connection.

[0169] UE 1004 transmits an RRC reconfiguration complete message 1048, which is received by target PN 1012. In the illustrated example, UE 1004 transmits the RRC reconfiguration complete message 1048 to target PN 1012 via target AN 1010. For example, UE 1004 may transmit the RRC reconfiguration complete message 1048 to target AN 1010 via sidelink connection 1031, and target AN 810 may forward the RRC reconfiguration complete message 842 to target PN 810 via the second network interface 811.

[0170] Then, UE 1004 and target PN 1012 can continue to transmit data 1050 via the access link connection between UE 1004 and target PN 1012.

[0171] In the illustrated example, after executing RACH procedure 1046, UE 1004 transmits an RRC reconfiguration complete message 1048 to target PN 1010 via target AN 1010. However, it can be understood that UE 1004 may transmit the RRC reconfiguration complete message 1048 to target PN 1012 before or as part of executing RACH procedure.

[0172] Figure 11An example communication flow 1100 between UE 1104, source AN 1106, source PN 1108, and target PN 1112, as presented herein, is described. In the described example, source AN 1106 and source PN 1108 are communicating (e.g., via network interface 1107). In the described example, UE 1104 and source AN 1106 are communicating via sidelink connection 1105. Example UE 1104 and source PN 1108 are communicating via access link connection 1109.

[0173] Various aspects of UE 1104 can be derived from Figure 1 UE 104 Figure 5 UE 504 Figure 6 UE 604, and / or Figure 7 The first UE 702 is used for implementation. Various aspects of the source AN 1106 can be implemented by sidelink devices, such as... Figure 1 Example RSU 107 Figure 5 Side link device 506, Figure 6 RSU 606, and / or Figure 7 UEs 704, 706, 708, and / or RSU 710. Various aspects of the source PN 1108 and target PN 1112 can be implemented by the base station, such as... Figure 1 Base station 102 / 180 Figure 5 Base station 502 Figure 6 Base station 602, and / or Figure 7 The first base station 730 and / or the second base station 732. The aspects of the side link connection 1105 can be provided by... Figure 5 Side link connection 514 and / or Figure 6 This is achieved via the PC5 link. The various aspects of the access link connecting 1109 can be implemented by... Figure 5 Access link connection 510 and / or Figure 6 This is achieved through the Uu link. Various aspects of network interface 1107 can be implemented by... Figure 6 It is implemented using the network interface 620.

[0174] In the illustrated example, communication flow 1100 facilitates UE 1104 to perform mobility procedures in response to an RLF. UE 1104 may detect an RLF associated with source PN 1108 and / or source AN 1106. Upon detecting an RLF associated with source PN 1108, UE 1104 may attempt to perform a fast PCG recovery to establish an access link connection with another master node (e.g., target PN 1112). As described below, when performing a fast PCG recovery, UE 1104 abandons the initialization of the RRC reconstruction procedure. However, if the fast PCG recovery is unsuccessful, UE 1104 may initialize the RRC reconstruction procedure. In some examples, the fast PCG recovery may fail if UE 1104 does not receive a response from the network before the timer expires. For example, in response to initiating a fast PCG recovery, UE 1104 can initiate a timer, and if UE 1104 does not receive a response from the network (e.g., source PN 1108) before the timer expires, UE 1104 can initiate the execution of an RRC reconstruction procedure.

[0175] In some respects, UE 1104 can detect RLFs associated with source PN 1108 and source AN 1106. In some such examples, UE 1104 can abandon performing fast PCG recovery and instead initiate the execution of RRC reconstruction procedures.

[0176] In some respects, UE 1104 can detect RLF associated with source AN 1106. In some such examples, UE 1104 can trigger the execution of inter-AN changes, such as in conjunction with... Figure 9 And / or as described in 10.

[0177] Return to Figure 11 In communication flow 1100, at 1120, UE 1104 detects the occurrence of an RLF. In this example, the RLF is associated with source PN 1108 and may be based on access link connection 1109 (e.g., PCG failure). Based on the RLF associated with access link connection 1109, UE 1104 can trigger a fast PCG recovery. For example, UE 1104 transmits a PCG failure indication 1122, which is received by source PN 1108. Figure 11As shown, UE 1104 transmits PCG fault indication 1122 via source AN 1106. For example, UE 1104 may transmit PCG fault indication 1122 to source AN 1106 via sidelink connection 1105, and source AN 1106 may forward PCG fault indication 1122 to source PN 1108 via network interface 1107. In some examples, UE 1104 may transmit PCG fault indication 1122 to source AN 1106 via split signaling radio bearer (SRB) (e.g., SRB1) or PC5 bearer (when available).

[0178] In the illustrated example, PCG fault indication 1122 includes fault information 1123. Fault information 1123 may include access link measurements and corresponding cell identifiers. For example, fault information 1123 may include access link measurements of source PN 1108 and any additional available access link measurements associated with neighboring base stations. Examples of access link measurements include RRM measurements associated with source PN 1108 and any additional available base stations (e.g., target PN 1112). Examples of cell identifiers include PCI and CGI. Fault information 1123 may additionally or alternatively include any available sidelink measurements for serving and neighboring sidelink devices, identifiers associated with the respective serving and neighboring sidelink devices, and the PN identifier of the master node associated with each of the respective serving and neighboring sidelink devices. Examples of sidelink measurements include RSRP measurements based on discovery messages (e.g., SD-RSRP measurements) or RSRP measurements based on SLSS received from serving and neighboring sidelink devices (such as source AN 1106). Examples of PN identifiers include cell identifier, PCI and frequency, or CGI. Fault information 1123 may additionally or alternatively include fault causes such as RLF, handover failure, IP check failure, and / or RRC reconfiguration failure.

[0179] In the illustrated example, at 1124, UE 1104 initiates a timer after transmitting PCG fault indication 1122. UE 1104 can use the timer to determine whether the fast PCG recovery was successful or unsuccessful.

[0180] At 1126, source PN 1108 determines that an inter-PN change needs to be performed. For example, source PN 1108 can use fault information 1123 to determine that PCG fault indication 1122 corresponds to an RLF and that there is another available base station that UE 1104 can connect to. For example, RRM measurements included in fault information 1123 can indicate that there is at least one base station that UE 1104 can connect to.

[0181] Source PN 1108 transmits handover request 1128, which is received by target PN 1112. For example... Figure 11 As shown, the handover request 1128 includes sidelink measurements 1129. For example, the handover request 1128 may include sidelink measurements for the serving and adjacent sidelink devices included in the fault report 1123.

[0182] Target PN 1112 transmits AN Add Request 1130, which is received by source AN 1106. AN Add Request 1130 may include information associated with UE 1104 to configure source AN 1106 to operate as an auxiliary node for UE 1104 and target PN 1112. Source AN 1110 transmits AN Add ACK 1132, which is received by target PN 1112. AN Add ACK 1132 may indicate that source AN 1106 is configured to operate as an auxiliary node for UE 1104 and target PN 1112.

[0183] In some examples, AN Add-on Request 1130 and AN Add-on ACK 1132 can facilitate the establishment of a network interface between source AN 1106 and target PN 1112. For example, AN Add-on Request 1130 and AN Add-on ACK 1132 can establish network interface 1133 between source AN 1106 and target PN 1112. It can be understood that in other examples, a network interface between source AN 1106 and target PN 1112 may already exist, and therefore the exchange of AN Add-on Request 1130 and AN Add-on ACK 1132 may not require establishing a new network interface between source AN 1106 and target PN 1112.

[0184] In the illustrated example, target PN 1112 transmits a handover ACK message 1134, which is received by source PN 1108. The handover ACK message 1134 includes configuration information 1135 for target PN 1112 and source AN 1106. For example, configuration information 1135 enables UE 1104 to establish an access link connection with target PN 1112.

[0185] Source PN 1108 transmits RRC reconfiguration message 1136, which is received by UE 1104. In the illustrated example, source PN 1108 transmits RRC reconfiguration message 1136 to UE 1104 via source AN 1106. For example, source PN 1108 may transmit RRC reconfiguration message 1136 to source AN 1106 via network interface 1107, and source AN 1106 may forward RRC reconfiguration message 1136 to UE 1104 via sidelink connection 1105. In the illustrated example, RRC reconfiguration message 1136 includes configuration information 1137 for target PN 1112 and source AN 1106. Configuration 1137 may correspond to configuration 1135 received by source AN 1106 from target PN 1112 via handover ACK message 1134. This configuration information enables UE 1104 to establish an access link connection with target PN 1112.

[0186] In the illustrated example, UE 1104 and target PN 1112 execute RACH procedure 1140 to establish an access link connection between UE 1104 and target PN 1112. UE 1104 can use the configuration information for target PN 1112 included in RRC reconfiguration message 1136 to establish the access link connection.

[0187] UE 1104 transmits an RRC reconfiguration complete message 1142, which is received by target PN 1112. In the illustrated example, UE 1104 transmits the RRC reconfiguration complete message 1142 to target PN 1112 via source AN 1106. For example, UE 1104 may transmit the RRC reconfiguration complete message 1142 to source AN 1106 via sidelink connection 1105, and source AN 1106 may forward the RRC reconfiguration complete message 1142 to target PN 1110 via network interface 1133.

[0188] Then, UE 1104 and target PN 1112 can continue to transmit data 1144 via the access link connection between UE 1104 and target PN 1112.

[0189] In the illustrated example, after executing RACH procedure 1140, UE 1104 transmits an RRC reconfiguration complete message 1142 to target PN 1112 via source AN 1106. However, it can be understood that UE 1104 may transmit the RRC reconfiguration complete message 1142 to target PN 1112 before or as part of executing RACH procedure.

[0190] like Figure 11As shown, UE 1104 receives a response (e.g., RRC reconfiguration message 1136) from the network before the timer expires (e.g., at 1138). As a result, UE 1104 can determine that the fast PCG recovery was successful and continue to abandon the execution of the RRC reconstruction procedure.

[0191] However, in an example where UE 1104 does not receive a response from the network before the timer expires (e.g., does not receive RRC reconfiguration message 1136), at 1138, UE 1104 can initiate the execution of RRC reconstruction procedure 1150. In some examples, executing RRC reconstruction procedure 1150 may include UE 1104 sending an RRC reconstruction request message to target PN 1112, receiving an RRC reconstruction completion message from target PN 1112, and sending an RRC reconstruction completion message to target PN 1112. The aspects of the RRC reconstruction request message to target PN 1112 can be similar to... Figure 10 The RRC Reconstruction Request message 1034. The aspects of the RRC Reconstruction Completion message can be similar to... Figure 10 The RRC reconstruction completion message 1040. The aspects of the RRC reconstruction completion message can be similar to... Figure 10 The RRC reconstruction completion message 1042. In some examples, UE 1104 and target PN 1112 can exchange RRC reconstruction procedure 1150 messages via source AN 1106, such as in combination. Figure 10 The example described.

[0192] In the illustrated example, UE 1104 detects an RLF associated with source PN 1108 based on the access link connection 1109 between UE 1104 and source PN 1108 (e.g., at 1120). In some examples, UE 1104 may detect an RLF associated with both source PN 1108 and source AN 1106. In some such examples, UE 1104 may forgo performing a fast PCG recovery and instead initiate an RRC reconstruction procedure. For example, UE 1104 may initiate an RRC reconstruction procedure 1150 after detecting an RLF (e.g., at 1120).

[0193] In some examples, UE 1104 can detect the RLF associated with source AN 1106 based on the sidelink connection 1105 between UE 1104 and source AN 1106. In some such examples, UE 1104 can trigger the execution of inter-AN changes, such as in conjunction with... Figure 9 And / or as described in 10.

[0194] Although Figure 11The example illustrates that source PN 1108 determines to perform an inter-PN change (e.g., in 1126), but it can be understood that in some examples, source PN 1108 may determine that the target PN is unavailable. In some such examples, source PN 1108 may instruct UE 1104 to release source PN 1108 (e.g., to release the access link connection between UE 1104 and source PN 1108).

[0195] although Figure 11 Although not shown, it can be understood that in some examples, target PN 1112 may select a sidelink device to operate as an auxiliary node for both UE 1104 and target PN 1112. The selection of a sidelink device can be similar to... Figure 8 828.

[0196] Figure 12 This is a flowchart 1200 of a wireless communication method. The method can be performed by a UE (e.g., UE 104, a second communication device 350, and / or...). Figure 16 The device (1602) is used to execute this procedure. Optionally, aspects are illustrated with dashed lines. This method enables the UE to execute mobility procedures while communicating with auxiliary and primary nodes.

[0197] At 1202, the UE establishes a sidelink connection with the first AN and an access link connection with the first PN, such as combining... Figure 5 This is described by the sidelink connection 514 with sidelink device 506 and the access link connection 510 with base station 502. For example, 1202 may be... Figure 16 The connection management component 1640 of device 1602 performs this function. The first AN and the first PN can be connected via a first network interface (such as...). Figure 6 Communicate via the network interface 620.

[0198] In some examples, a sidelink connection may correspond to a PC5 link between the UE and the first AN. The sidelink connection to the first AN may be based on communication within the sub-6 GHz frequency range. The sidelink connection to the first AN can facilitate the transmission of control signaling between the UE and the first PN.

[0199] In some examples, the access link connection may correspond to the Uu link between the UE and the first PN. The access link connection with the first PN may be based on communication within the mmW frequency range. The access link connection with the first PN can facilitate the transmission of data between the UE and the first PN.

[0200] In step 1204, the UE determines that a node change triggering event associated with at least one of the first AN and the first PN has occurred, such as in combination with Figure 8 820 Figure 9 922, Figure 10 1022, and / or Figure 11 As described in 1120. For example, 1204 can be described by Figure 16 The node change of device 1602 triggers the event component 1642 to execute.

[0201] In some examples, the UE can determine the occurrence of node change trigger events based on measurements. Combined with... Figures 8 to 10 This describes the various aspects of how a node change triggers an event.

[0202] In some examples, the UE can determine the occurrence of node change trigger events based on RLF. Combined with Figure 11 This describes the various aspects of how the RLF triggering occurs when a node changes.

[0203] In 1206, the UE executes the node change procedure based on the occurrence of a node change trigger event, such as in conjunction with... Figure 8 Changes between PN Figure 9 Changes within PN and between AN Figure 10 Changes between PN and AN, and / or Figure 11 The rapid PCG recovery described. For example, 1206 can be... Figure 16 The node of device 1602 changes component 1644 to execute.

[0204] Combination Figure 13 and 14 This describes the various aspects of executing node change procedures based on the measurement triggering of node change trigger events.

[0205] Combination Figure 15 This describes the various aspects of executing node change procedures based on the occurrence of RLF triggering events that trigger node change events.

[0206] In 1208, the UE communicates with at least one of the second AN or the second PN based on the node change procedure, such as in combination with Figure 8 Data 844 Figure 9 Control signaling 938 Figure 10 Data 1050, and / or Figure 11 The data described by 1144. For example, 1208 can be derived from... Figure 16 The communication component 1646 of device 1602 performs this function. The second AN and the second PN can communicate via the second network interface.

[0207] In some examples, the UE can determine the occurrence of node change trigger events based on measurements. Figure 13 and 14 The document explains various aspects of executing node change procedures based on the measurement triggering of node change triggering events.

[0208] Figure 13 This is a flowchart 1300 of a wireless communication method. The method can be performed by a UE (e.g., UE 104, a second communication device 350, and / or...). Figure 16 The method is implemented using device 1602. Optionally, aspects are illustrated with dashed lines. This method enables the UE to perform PN changes while communicating with auxiliary and primary nodes.

[0209] At 1302, the UE can transmit a measurement report to the first AN via the first PN based on measurements of at least one of the sidelink connection or the access link connection, such as in combination with... Figure 8 As described in measurement report 822. For example, 1302 can be made by... Figure 16 The measurement report is performed by the measurement component 1648 of device 1602. The measurement report may include one or more of the following: RRM measurement associated with the second PN, the second PN identifier, the first AN sidelink measurement, the second AN identifier, the master node identifier associated with the second AN, and the second AN sidelink measurement. In some examples, the first AN sidelink measurement and / or the second AN sidelink measurement may be based on at least one of the SLSS and sidelink discovery messages associated with the corresponding AN.

[0210] In some examples, the UE can perform the measurement based on a measurement gap configuration that includes an AN gap mode and a PN gap mode. In some examples, the measurement gap configuration can correspond to a per-UE gap, where the AN gap mode and the PN gap mode are associated with the same gap time period. In some examples, the measurement gap configuration can correspond to a per-FR gap, where the AN gap mode is associated with a first gap time period, and the PN gap mode is associated with a second gap time period different from the first gap time period.

[0211] At 1304, the UE can receive target node configuration associated with the second AN and the second PN via a sidelink connection with the first AN, such as in combination with Figure 8 The target PN and AN configurations described in RRC reconfiguration message 836. For example, 1304 can be... Figure 16 The target node configuration component 1650 of device 1602 is used to execute.

[0212] In 1306, the UE can establish a second-side link connection with the second AN based on the target node configuration, such as combining... Figure 8 The side link connection described in 839. For example, 1306 can be... Figure 16 The connection management of device 1602 is performed by device 1640.

[0213] In 1308, the UE can establish a second access link connection with the second PN based on the target node configuration, such as combining... Figure 8As described in RACH specification 840. For example, 1308 can be derived from... Figure 16 The connection management component 1640 of device 1602 is used to perform this.

[0214] In 1310, the UE can communicate with at least one of the second AN or the second PN when establishing the second side link connection and the second access link connection, such as in combination. Figure 8 The data communication described in 844. For example, 1310 can be... Figure 16 The communication component 1646 of device 1602 is used to perform this. In some examples, the second AN and the first AN may correspond to the same auxiliary node.

[0215] Figure 14 This is a flowchart 1400 of a wireless communication method. The method can be performed by a UE (e.g., UE 104, a second communication device 350, and / or...). Figure 16 The device (1602) is used to perform this. Optionally, aspects are illustrated with dashed lines. This method enables the UE to perform inter-AN changes while communicating with auxiliary and primary nodes.

[0216] In 1402, the UE can determine that the sidelink connection with the first AN is unreliable based on measurements of the sidelink connection, such as in combination with... Figure 9 922 and / or Figure 10 As described in 1022. For example, 1402 can be... Figure 16 The node change trigger event component 1642 of device 1602 performs the action. In some examples, when the measurement is below a threshold, the UE can determine that the sidelink connection with the first AN is unreliable. In some examples, the threshold may be pre-configured. In some examples, the UE may receive the threshold from the base station, for example, via SIB or via RRC signaling.

[0217] In step 1404, the UE can select a second AN from the AN set based on one or more measurements performed against the AN set, such as in combination. Figure 9 926 and / or Figure 10 As described in 1026. For example, 1404 can be... Figure 16 The node selection component 1652 of device 1602 performs the measurement. In some examples, the measurement performed on the AN set may include RSRP measurement for SLSS or RSRP measurement for SD messages.

[0218] At 1406, the UE can establish a second-side link connection with the second AN, such as in combination with... Figure 9 Side link connection 931 and / or Figure 10 The side link connection 1031 is described. For example, 1406 can be provided by... Figure 16 The connection management component 1640 of device 1602 is used to perform this.

[0219] In step 1408, the UE can determine whether the second AN and the first AN are associated with the same priority node, such as by combining... Figure 9 928 and / or Figure 10 As described by 1028. For example, 1408 can be described by Figure 16 The node of device 1602 changes component 1644 to execute.

[0220] In some examples, the UE can determine at 1410 that the second AN and the first AN are associated with the same master node based on the corresponding master node identifiers associated with the second AN and the first AN, such as in combination with Figure 9 As described in 928. For example, 1410 can be... Figure 16 The node change component 1644 of device 1602 performs the change. For example, the corresponding master node identifier can indicate that the second PN and the first PN correspond to the same master node.

[0221] In step 1412, the UE can use this determination to transmit a change request within the PN to the second AN, such as in combination with... Figure 9 The PN internal change notification 932 is described. For example, 1412 may be generated by... Figure 16 The communication component 1646 of the device 1602 is used to perform this.

[0222] In 1414, the UE can receive an RRC configuration message from the second AN based on the intra-PN change request, such as in combination with Figure 9 The RRC reconfiguration message 936 describes this. For example, 1414 can be generated by... Figure 16 The connection management component 1640 of device 1602 is used to perform this.

[0223] In some examples, the UE can determine at 1416 that the second AN and the first AN are associated with different master nodes based on the corresponding master node identifiers associated with the second AN and the first AN, such as by combining Figure 10 As described in 1028. For example, 1416 can be derived from... Figure 16 The node change component 1644 of device 1602 performs this change. For example, the corresponding master node identifier can indicate that the second PN and the first PN correspond to different master nodes.

[0224] In 1418, the UE can establish a connection with the second PN via the second AN based on this determination, such as in combination. Figure 10 As described in RACH specification 1046. For example, 1418 can be derived from... Figure 16 The connection management component 1640 of device 1602 performs this function. The UE and the second PN can use the established connection to, for example, communicate... Figure 10 Example data 1050.

[0225] In some examples, the UE can determine the occurrence of node change trigger events based on RLF. Figure 15 This section explains various aspects of executing node change procedures based on the occurrence of RLF triggering events that trigger node change events.

[0226] Figure 15 This is a flowchart 1500 of a wireless communication method. The method can be performed by a UE (e.g., UE 104, a second communication device 350, and / or...). Figure 16 The method is implemented using device 1602. Optionally, aspects are illustrated with dashed lines. This method enables the UE to perform fast PCG recovery while communicating with auxiliary and primary nodes.

[0227] In 1502, the UE can identify the RLF associated with the access link connection to the first PN, such as in combination with Figure 11 As described in 1120. For example, 1502 can be... Figure 16 The node change of device 1602 triggers the event component 1642 to execute.

[0228] At 1506, the UE can transmit a fault indication message to the first PN via the first AN, such as in combination with Figure 11 The PCG fault indication 1122 is described. For example, 1506 can be described by Figure 16 The communication component 1646 of device 1602 performs this function. The UE may use a split SRB1 or PC5 bearer to transmit the fault indication message. In some examples, the fault indication message may include one or more of the following: RRM measurement associated with the second PN, second PN identifier, first AN sidelink measurement, second AN identifier, master node identifier associated with the second AN, second AN sidelink measurement, and fault cause identifier.

[0229] In 1510, the UE can receive the target node configuration associated with the second AN and the second PN, such as in combination with Figure 11 The RRC reconfiguration message 1136 describes this. For example, 1510 can be generated by... Figure 16 The target node configuration component 1650 of device 1602 is used to execute.

[0230] In 1516, the UE can establish a second-side link connection with the second AN based on the target node configuration, such as combining... Figure 8 The side link connection described in 839. For example, 1516 can be... Figure 16 The connection management component 1640 of device 1602 is used to perform this.

[0231] In 1518, the UE can establish a second access link connection with the second PN based on the target node configuration, such as combining... Figure 11As described in RACH specification 1140. For example, 1518 can be derived from... Figure 16 The connection management component 1640 of device 1602 is used to perform this.

[0232] In 1520, the UE can communicate with at least one of the second AN and the second PN when establishing the second side link connection and the second access link connection, such as in combination. Figure 11 The data communication described in 1144. For example, 1520 may be... Figure 16 The communication component 1646 of the device 1602 is used to perform this.

[0233] At 1508, the UE can initiate a timer after transmitting a fault indication message to the first PN via the first AN, as combined with Figure 11 As described in 1124. For example, 1508 can be derived from... Figure 16 The timer component 1654 of device 1602 is used to execute.

[0234] In some examples, the UE can receive the target node configuration associated with the second AN and the second PN before the timer expires. In some such examples, the UE can abandon the execution of the RRC reconstruction procedure, for example, as in combination with Figure 11 As described in RRC Reconstruction Procedure 1150.

[0235] In some examples, the UE may not receive the target node configuration associated with the second AN and the second PN before the timer expires. For example, in 1512, when the timer expires, the UE may execute the RRC reconstruction procedure, such as in conjunction with... Figure 11 The RRC reconstruction procedure described in 1150. For example, 1512 can be derived from... Figure 16 The connection management component 1640 of device 1602 performs this function. In some such examples, the UE can receive the target node configuration while performing the RRC reconstruction procedure.

[0236] In some examples, the UE can identify RLFs associated with access link connections and RLFs associated with sidelink connections. For example, in 1504, the UE can identify RLFs associated with a sidelink connection to the first AN, such as in combination with... Figure 11 As described in 1120. For example, 1504 can be... Figure 16The node change trigger event component 1642 of device 1602 is executed. In some such examples, the UE may abandon the attempt to perform a fast PCG recovery and instead initiate an RRC reconstruction procedure. For example, after identifying an RLF associated with an access link connection to the first PN (e.g., at 1502) and an RLF associated with a side link connection to the first AN (e.g., at 1504), the UE may perform an RRC reconstruction procedure at 1512. In some such examples, the UE may receive target node configuration while performing the RRC reconstruction procedure.

[0237] In some examples, the UE may identify (e.g., in 1504) an RLF associated with a sidelink connection to the first AN, but not an RLF associated with an access link connection to the first PN. In some such examples, in 1514, the UE may perform an inter-AN change based on the identified RLF. For example, 1514 may be... Figure 16 The node of device 1602 changes component 1644 to execute. Combined Figure 13 And / or 14 to describe the aspects of implementing changes between ANs.

[0238] Figure 16Figure 1600 illustrates an example of the hardware implementation of device 1602. Device 1602 is a UE and includes a cellular baseband processor 1604 (also referred to as a modem) coupled to a cellular RF transceiver 1622 and one or more Subscriber Identity Module (SIM) cards 1620, an application processor 1606 coupled to a Secure Digital Card (SD) card 1608 and a screen 1610, a Bluetooth module 1612, a Wireless Local Area Network (WLAN) module 1614, a Global Positioning System (GPS) module 1616, and a power supply 1618. Cellular baseband processor 1604 communicates with UE 104 and / or base station 102 / 180 via cellular RF transceiver 1622. Cellular baseband processor 1604 may include computer-readable media / memory. The computer-readable media / memory may be non-transient. Cellular baseband processor 1604 is responsible for general processing, including the execution of software stored on the computer-readable media / memory. When executed by the cellular baseband processor 1604, the software causes the cellular baseband processor 1604 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1604 during software execution. The cellular baseband processor 1604 further includes a receiving component 1630, a communication manager 1632, and a transmission component 1634. The communication manager 1632 includes the one or more of the described components. The components within the communication manager 1632 may be stored in a computer-readable medium / memory and / or configured as hardware within the cellular baseband processor 1604. The cellular baseband processor 1604 may be a component of a second communication device 350 and may include a memory 360 and / or at least one of the following: a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, the device 1602 may be a modem chip and include only the baseband processor 1604, and in another configuration, the device 1602 may be the entire UE (e.g., see...). Figure 3 The second communication device 350) and includes an additional module of device 1602.

[0239] Communication manager 1632 includes connection management component 1640, which is configured to establish a sidelink connection with the first AN and an access link connection with the first PN, for example, as in combination with Figure 12 As described in 1202. In some examples, the connection management component 1640 is configured to establish a second side link connection with the second AN based on the target node configuration, for example, as in combination with Figure 13 As described in 1306; and / or configured to establish a second access link connection with the second PN based on the target node configuration, for example, as in combination with Figure 13 As described in 1308. In some examples, the connection management component 1640 is configured to establish a second-side link connection with the second AN, for example, as in conjunction with Figure 14 As described in 1406; configured to receive RRC configuration messages from a second AN based on a change request within the PN, for example, as in combination Figure 14 As described in 1414; and / or configured to establish a connection with the second PN via the second AN based on that determination, for example, as in combination Figure 14 As described in 1418. In some examples, the connection management component 1640 is configured to perform an RRC rebuild procedure, for example, as in conjunction with Figure 15 As described in 1512; configured to establish a second side link connection with the second AN based on the target node configuration, for example, as in combination Figure 15 As described in 1516; and / or configured to establish a second access link connection with the second PN based on the target node configuration, for example, as in combination with Figure 15 As described in 1518.

[0240] Communication manager 1632 also includes node change triggering event component 1642, which is configured to determine the occurrence of a node change triggering event associated with at least one of the first AN and the first PN, for example, as in combination Figure 12 As described in 1204. In some examples, the node change triggering event component 1642 is configured to identify the RLF associated with the access link connection to the first PN, for example, as in conjunction with Figure 15 As described in 1502; and / or configured to identify an RLF associated with a side link connection to the first AN, for example, as in combination Figure 15 As described in 1504.

[0241] Communication manager 1632 also includes node change component 1644, which is configured to execute node change procedures based on the occurrence of node change trigger events, for example, as in combination with Figure 12 As described in 1206. In some examples, the node change component 1644 is configured to determine whether the second AN and the first AN are associated with the same priority node, for example, as in combination. Figure 14 As described in 1408; configured to determine that the second AN and the first AN are associated with the same master node based on the corresponding master node identifiers associated with the second AN and the first AN, for example, as in combination Figure 14 As described in 1410; and / or configured to determine, based on that determination, the establishment of a connection between the second AN and the second PN, as in combination Figure 14 As described in 1416. In some examples, the node change component 1644 is configured to perform inter-AN changes based on the identified RLF, for example, as in conjunction with Figure 15 As described in 1514.

[0242] Communication manager 1632 also includes communication component 1646, which is configured to communicate with at least one of the second AN or second PN based on node change procedures, for example, as in combination Figure 12 As described in 1208. In some examples, communication component 1646 is configured to communicate with at least one of the second AN or second PN during the establishment of the second side link connection and the second access link connection, for example, as in combination Figure 13 As described in 1310. In some examples, communication component 1646 is configured to transmit a change request within the PN to the second AN based on this determination, for example, as in combination with Figure 14 As described in 1412. In some examples, communication component 1646 is configured to transmit a fault indication message to the first PN via the first AN, for example, as in combination with Figure 15 As described in 1506; and / or configured to communicate with at least one of the second AN or second PN during the establishment of the second side link connection and the second access link connection, for example, as in combination Figure 15 As described in 1520.

[0243] Communication manager 1632 also includes measurement component 1648, which is configured to transmit measurement reports to first AN via first PN based on measurements of at least one of the peer link connection or access link connection, for example, as combined with Figure 13 As described in 1302. In some examples, the measurement component 1648 is configured to determine if the side link connection with the first AN is unreliable based on measurements of the side link connection, for example, as in combination with Figure 14 As described in 1402.

[0244] Communication manager 1632 also includes target node configuration component 1650, which is configured to receive target node configuration associated with second AN and second PN via a side link connection with first AN, for example, as in combination Figure 13 As described in 1304. In some examples, the target node configuration component 1650 is configured to receive target node configurations associated with the second AN and the second PN, for example, as in conjunction with Figure 15 As described in 1510.

[0245] Communication manager 1632 also includes node selection component 1652, which is configured to select a second AN from the AN set based on one or more measurements performed on the AN set, for example, as in combination Figure 14 As described in 1404.

[0246] Communication manager 1632 also includes timer component 1654, which is configured to initiate a timer after a fault indication message is transmitted from the first AN to the first PN, for example, as in combination with Figure 15As described in 1508.

[0247] The device may include execution Figures 12 to 15 The additional components of each block of the algorithm in the aforementioned flowchart. Thus, Figures 12-15 Each block in the aforementioned flowchart can be executed by a component, and the device may include one or more of those components. These components may be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0248] In one configuration, device 1602, and specifically cellular baseband processor 1604, includes means for establishing a sidelink connection with a first AN and an access link connection with a first PN, the first AN and the first PN communicating via a first network interface. Example device 1602 also includes means for determining the occurrence of a node change triggering event associated with at least one of the first AN and the first PN. Example device 1602 also includes means for executing a node change procedure based on the occurrence of the node change triggering event. Example device 1602 also includes means for communicating with at least one of a second AN or a second PN based on the node change procedure, the second AN and the second PN communicating via a second network interface. Example device 1602 also includes means for transmitting a measurement report to the first AN via the first PN based on measurements of at least one of the sidelink connection or the access link connection. Example device 1602 also includes means for receiving a target node configuration associated with the second AN and the second PN via a sidelink connection with the first AN. Example device 1602 also includes means for establishing a second sidelink connection with the second AN based on the target node configuration. Example device 1602 further includes means for establishing a second access link connection with a second PN based on a target node configuration. Example device 1602 also includes means for communicating with at least one of a second AN or a second PN during the establishment of the second sidelink connection and the second access link connection. Example device 1602 further includes means for determining, based on measurements of the sidelink connection, that a sidelink connection with a first AN is unreliable. Example device 1602 further includes means for selecting a second AN from a set of ANs based on one or more measurements performed on the set of ANs, the set of ANs including at least the second AN. Example device 1602 further includes means for establishing a second sidelink connection with the second AN. Example device 1602 further includes means for determining, based on corresponding master node identifiers associated with the second AN and the first AN, that the second AN and the first AN are associated with the same master node. Example device 1602 further includes means for transmitting an intra-PN change request to the second AN based on this determination. Example device 1602 further includes means for receiving an RRC configuration message from the second AN based on the intra-PN change request. Example device 1602 also includes means for determining that the second AN and the first AN are associated with different master nodes based on corresponding master node identifiers associated with the second AN and the first AN. Example device 1602 also includes means for establishing a connection with the second PN via the second AN based on this determination. Example device 1602 also includes means for identifying an RLF associated with an access link connection to the first PN. Example device 1602 also includes means for transmitting a fault indication message to the first PN via the first AN. Example device 1602 also includes means for receiving target node configurations associated with the second AN and the second PN.Example device 1602 further includes means for establishing a second sidelink connection with a second AN based on a target node configuration. Example device 1602 also includes means for establishing a second access link connection with a second PN based on a target node configuration. Example device 1602 further includes means for communicating with at least one of the second AN and the second PN during the establishment of the second sidelink connection and the second access link connection. Example device 1602 further includes means for initiating a timer after transmitting a fault indication message to the first PN via the first AN, wherein the UE receives a target node configuration from the first PN via the sidelink connection with the first AN before the timer expires. Example device 1602 further includes means for initiating a timer after transmitting a fault indication message to the first PN via the first AN. Example device 1602 further includes means for performing an RRC reconstruction procedure when the timer expires. Example device 1602 further includes means for identifying an RLF associated with the sidelink connection with the first AN. Example device 1602 further includes means for performing an RRC reconstruction procedure based on the RLF associated with the access link connection and the RLF associated with the sidelink connection. Example device 1602 also includes means for identifying an RLF associated with a side link connection to the first AN. Example device 1602 also includes means for performing inter-AN changes based on the RLF.

[0249] The aforementioned apparatus may be one or more of the aforementioned components in device 1602 configured to perform the functions described by the aforementioned apparatus. As described above, device 1602 may include TX processor 368, RX processor 356, and controller / processor 359. Thus, in one configuration, the aforementioned apparatus may be TX processor 368, RX processor 356, and controller / processor 359 configured to perform the functions described by the aforementioned apparatus.

[0250] Figure 17 This is a flowchart 1700 of a wireless communication method. This method can be executed by a source master node, such as a base station (e.g., base station 102 / 180, first communication device 310, and / or...). Figure 19 (Device 1902). Optional aspects are illustrated with dashed lines. This method can facilitate improved coverage by enabling the UE to execute mobility procedures.

[0251] In some examples, the master node communicates with the UE via an access link based on the mmW frequency range, and the master node communicates control signaling with the UE via a first AN. The master node and the first AN communicate via a first network interface.

[0252] At position 1702, the master node receives a notification of a node change triggering event, such as in conjunction with... Figure 8 Measurement report 822 Figure 9PN Internal Change Procedure 934 Figure 10 UE Context Exchange Procedure 1038, and / or Figure 11 The PCG fault indication 1122 is described. For example, 1702 can be described by... Figure 19 The node change notification component 1940 of device 1902 is used to execute the change notification.

[0253] In 1704, the master node executes node change procedures based on node change trigger event notifications. For example, 1704 can be... Figure 19 The node of device 1902 changes component 1942 to perform the change.

[0254] In some examples, the master node can receive node change trigger event notifications from the UE via the first AN, such as in combination with Figure 8 The measurement report described in measurement report 822 may include one or more of the following: RRM measurements associated with the second PN, the second PN identifier, the first AN sidelink measurement, the second AN identifier, the master node identifier associated with the second AN, and the second AN sidelink measurement. In some such examples, the master node may facilitate the execution of an inter-PN change based on a node change trigger event notification. For example, in 1706, the master node may determine to perform a handover procedure from the master node to the second PN based on at least one measurement included in the measurement report, such as in combination with... Figure 8 As described in 824. For example, 1706 can be derived from... Figure 19 The device 1902 uses the PN inter-component 1944 to perform this function.

[0255] In 1708, the master node can send a handover request to the second PN, such as in combination with Figure 8 The switching request 826 describes this. For example, 1708 can be made by... Figure 19 The switching request is performed by the switching component 1946 of device 1902. This switching request may include a second AN-side link measurement report.

[0256] In 1710, the master node receives the handover ACK message from the second PN, as combined with... Figure 8 The switching ACK message 834 describes this. For example, 1710 can be... Figure 19 The switching component 1946 of device 1902 performs the switching. The switching ACK message may include the target node configuration associated with the second PN and the second AN.

[0257] At 1712, the master node transmits an RRC reconfiguration message to the UE via the first AN, as combined with... Figure 8 The RRC reconfiguration message 836 describes this. For example, 1712 can be generated by... Figure 19The RRC reconfiguration message is executed by the RRC component 1948 of device 1902. The RRC reconfiguration message may include the target node configuration.

[0258] In some examples, the master node can change the triggering event notification from a second AN receiving node that is communicating with the master node via a second network interface, such as in combination with... Figure 9 This is described in PN intra-change procedure 934. A node change triggering event notification may include an intra-PN change request. In some such examples, the master node may facilitate intra-PN and inter-AN changes based on the node change triggering event notification. For example, in 1714, the master node may configure a second AN to operate as an auxiliary node for control signaling communication between the UE and the master node, such as in conjunction with... Figure 9 The PN internal change procedure 934 is described. For example, 1714 can be made by Figure 19 The AN configuration component 1950 of device 1902 is used to execute.

[0259] In 1716, the master node can transmit an RRC reconfiguration message to the UE via the second AN, such as in combination with... Figure 9 The RRC reconfiguration message 936 describes this. For example, 1716 can be generated by... Figure 19 The device 1902 uses the RRC component 1948 to perform this.

[0260] In some examples, the master node can receive notifications of node changes to triggering events from the second PN, such as in combination with... Figure 10 This is described in UE context exchange procedure 1038. A node change triggering event notification may include a UE context exchange request. In some such examples, the master node may facilitate inter-PN and inter-AN changes based on the node change triggering event notification. For example, in 1718, the master node may transmit UE context information associated with the UE to a second PN, such as in conjunction with... Figure 10 The UE context exchange procedure 1038 is described. For example, 1718 can be described by... Figure 19 The UE context component 1952 of device 1902 is used to perform this.

[0261] At 1720, the master node can release the access link connection with the UE, such as in combination with Figure 10 As described in 1032. For example, 1720 can be derived from... Figure 19 The connection management component of device 1902 is used to perform this function in 1954.

[0262] In some examples, the master node can receive node change trigger event notifications from the UE via the first AN, such as in combination with Figure 11The PCG fault indication 1122 describes this. The PCG fault indication may include one or more of the following: an RRM measurement associated with the second PN, a second PN identifier, a first AN sidelink measurement, a second AN identifier, a master node identifier associated with the second AN, a second AN sidelink measurement, and a fault cause identifier. In some such examples, the master node may facilitate the execution of a fast PCG recovery based on a node change trigger event notification. For example, in 1722, the master node may determine to perform a handover procedure from the master node to the second PN based on at least one measurement included in the fault indication, such as in conjunction with... Figure 11 As described in 1126. For example, 1722 can be derived from... Figure 19 The device 1902 uses the PN inter-component 1944 to perform this function.

[0263] At 1724, the master node can send a handover request to the second PN, such as in combination with Figure 11 The switching request 1128 is described. For example, 1724 can be generated by... Figure 19 The switching request is performed by the switching component 1946 of device 1902. This switching request may include a second AN-side link measurement indicating a fault.

[0264] At 1726, the master node receives a handover ACK message from the second PN, as shown in the following... Figure 11 The switching ACK message 1134 describes this. For example, 1726 can be described by... Figure 19 The switching component 1946 of device 1902 performs the switching. The switching ACK message may include the target node configuration 1135 associated with the second PN and the second AN.

[0265] At 1728, the master node transmits an RRC reconfiguration message to the UE via the first AN, as combined with... Figure 11 The RRC reconfiguration message 1136 describes this. For example, 1728 can be generated by... Figure 19 The device 1902 uses the RRC component 1948 to perform the reconfiguration. The RRC reconfiguration message may include the target node configuration 1137.

[0266] Figure 18 This is a flowchart 1800 of a wireless communication method. The method can be executed by a target master node, such as a base station (e.g., base station 102 / 180, first communication device 310, and / or...). Figure 19 (Device 1902). Optional aspects are illustrated with dashed lines. This method can facilitate improved coverage by enabling the UE to execute mobility procedures.

[0267] At position 1802, the master node receives a notification of a node change triggering event, such as in conjunction with... Figure 8 Switching request 826 Figure 10 RRC Reconstruction Request Message 1034, and / or Figure 11 The switching request 1128 describes this. For example, 1802 can be made by... Figure 19 The node change notification component 1940 of device 1902 is used to execute the change notification.

[0268] In 1804, the master node executes the node change procedure based on node change trigger event notifications. For example, 1804 can be... Figure 19 The node of device 1902 changes component 1942 to perform the change.

[0269] In 1806, the master node communicates with the UE via an access link based on the mmW frequency range, such as combining... Figure 8 Data 844 Figure 10 Data 1050, and / or Figure 11 The data described in 1144. For example, 1806 can be derived from... Figure 19 The communication components of the device 1902 were used to perform the operation in 1956.

[0270] In 1808, the master node communicates control signaling with the UE via the first AN, such as in combination. Figure 9 The control signaling 938 describes this. For example, 1808 can be generated by... Figure 19 The communication component 1956 of device 1902 is used to perform this function. The master node and the first AN can communicate via a first network interface.

[0271] In some examples, the master node can receive node change trigger event notifications from the second PN. For instance, a node change trigger event notification may include a handover request that includes sidelink measurements associated with a set of ANs that at least includes the first AN, such as in conjunction with... Figure 8 The switching request 826 describes this. For example, in 1810, the master node can select a first AN from the AN set based on sidelink measurements, as combined with... Figure 8 As described in 828. For example, 1810 can be derived from... Figure 19 The AN configuration component 1950 of device 1902 is used to execute.

[0272] In 1812, the master node can connect via the first network interface to add the first AN to operate as an auxiliary node for both the UE and the master node, such as in combination. Figure 8 The AN addition request 830 describes this. For example, 1812 can be made by Figure 19 The AN configuration component 1950 of device 1902 is used to execute.

[0273] At 1814, the master node can send a switchover ACK message to the second PN, as combined with... Figure 8 The switching ACK message 834 describes this. For example, 1814 can be described by... Figure 19The switching component 1946 of device 1902 performs the switching. The switching ACK message may include the target node configuration associated with the master node and the first AN.

[0274] In 1816, the master node can establish an access link connection with the UE, such as combining... Figure 8 As described in RACH specification 840. For example, 1816 can be derived from... Figure 19 The connection management component of device 1902 is used to perform this function in 1954.

[0275] In some examples, the master node can receive node change trigger event notifications from the UE via the first AN, such as in combination with Figure 10 This is described in RRC Reconstruction Request Message 1034. In some such examples, the master node can facilitate the execution of inter-PN and inter-AN changes based on node change trigger event notifications. For example, in 1818, the master node can execute an AN reselection procedure with the first AN, as in conjunction with... Figure 10 As described in AN reselection procedure 1036. For example, 1818 can be... Figure 19 The AN configuration component 1950 of device 1902 is used to execute.

[0276] At 1820, the master node can receive UE context information associated with the UE from the second PN, such as combining Figure 10 As described in UE context exchange procedure 1038. For example, 1820 can be... Figure 19 The UE context component 1952 of device 1902 performs this function. The second PN can communicate data with the UE via a second access link.

[0277] In 1822, the master node can transmit an RRC reconfiguration message to the UE via the first AN, such as in combination with Figure 10 The RRC reconfiguration message 1044 describes this. For example, 1822 can be generated by... Figure 19 The device 1902 uses the RRC component 1948 to perform the reconfiguration. The RRC reconfiguration message can include the target node configuration associated with the first node and the master node.

[0278] In 1824, the master node can establish an access link connection with the UE based on the target node configuration, such as combining... Figure 10 As described in RACH specification 1046. For example, 1824 can be derived from... Figure 19 The connection management component of device 1902 is used to perform this function in 1954.

[0279] In some examples, the master node can receive node change trigger event notifications from the second PN. For instance, a node change trigger event notification may include a handover request that includes sidelink measurements associated with a set of ANs that at least includes the first AN, such as in conjunction with... Figure 11 The handover request 1128 describes this. In some such examples, the master node can facilitate the execution of a fast PCG recovery based on a node change trigger event notification. For example, in 1826, the master node can add a first AN via a first network interface connection to operate as an auxiliary node for both the UE and the master node, such as in combination. Figure 11 The AN addition request 1130 described, for example, 1826, can be made by Figure 19 The AN configuration component 1950 of device 1902 is used to execute.

[0280] At 1828, the master node can send a switchover ACK message to the second PN, as combined with... Figure 11 The switching ACK message 1134 describes this. For example, 1828 can be described by... Figure 19 The switching component 1946 of device 1902 performs the switching. The switching ACK message may include the target node configuration 1135 associated with the master node and the first AN.

[0281] At 1830, the master node can establish an access link connection with the UE, such as combining... Figure 11 As described in RACH specification 1140. For example, 1830 can be derived from... Figure 19 The connection management component of device 1902 is used to perform this function in 1954.

[0282] Figure 19 Figure 1900 illustrates an example of the hardware implementation of device 1902. Device 1902 is a base station and includes a baseband unit 1904. Baseband unit 1904 can communicate with UE 104 via cellular RF transceiver 1922. Baseband unit 1904 may include computer-readable medium / memory. Baseband unit 1904 is responsible for general processing, including the execution of software stored on computer-readable medium / memory. When executed by baseband unit 1904, the software causes baseband unit 1904 to perform the various functions described above. Computer-readable medium / memory can also be used to store data manipulated by baseband unit 1904 during software execution. Baseband unit 1904 further includes a receiving component 1930, a communication manager 1932, and a transmitting component 1934. Communication manager 1932 includes one or more of the illustrated components. Components within communication manager 1932 may be stored in computer-readable medium / memory and / or configured as hardware within baseband unit 1904. The baseband unit 1904 may be a component of the first communication device 310 and may include a memory 376 and / or at least one of the following: a TX processor 316, an RX processor 370, and a controller / processor 375.

[0283] Communication manager 1932 includes node change notification component 1940, which is configured to receive node change trigger event notifications, for example, as in combination with Figure 17 As described in 1702. In some examples, the node change notification component 1940 is configured to receive node change trigger event notifications, for example, as in conjunction with Figure 18 As described in 1802.

[0284] The communication manager 1932 also includes a node change component 1942, which is configured to execute node change procedures based on node change trigger event notifications, for example, as in conjunction with Figure 17 As described in 1704. In some examples, the node change component 1942 is configured to execute node change procedures based on node change trigger event notifications, for example, as in conjunction with Figure 18 As described in 1804.

[0285] Communication manager 1932 also includes inter-PN component 1944, which is configured to determine the execution of a switching procedure from the first PN to the second PN based on at least one measurement included in the measurement report, for example, as in combination with Figure 17 As described in 1706; and / or configured to determine the execution of a switching procedure from the first PN to the second PN based on at least one measurement included in the fault indication, for example, as in combination with Figure 17 As described in 1722.

[0286] Communication manager 1932 also includes a switching component 1946 configured to transmit a switching request to the second PN, the switching request including second AN side link measurements from a measurement report, for example, as combined with Figure 17 As described in 1708; configured to receive a handover confirmation message from a second PN, for example, as in conjunction with Figure 17 As described in 1710; configured to transmit a handover request to a second PN, for example, as in combination Figure 17 As described in 1724; and / or configured to receive a handover confirmation message from a second PN, for example, as in conjunction with Figure 17 As described in 1726. In some examples, the handover component 1946 is configured to transmit a handover confirmation message to the second PN, for example, as in conjunction with Figure 18 As described in 1814; and / or configured to transmit a handover confirmation message to the second PN, for example, as in combination with Figure 18 As described in 1828.

[0287] Communication manager 1932 also includes RRC component 1948, which is configured to transmit RRC reconfiguration messages to the UE via the first AN, for example, as in combination with Figure 17 As described in 1712; configured to transmit RRC reconfiguration messages to the UE via a second AN, for example, as in combination Figure 17As described in 1716; and / or configured to transmit an RRC reconfiguration message to the UE via a first AN, for example, as in combination with Figure 17 As described in 1728. In some examples, RRC component 1948 is configured to transmit an RRC reconfiguration message to the UE via the first AN, for example, as in conjunction with Figure 18 As described in 1822.

[0288] Communication manager 1932 also includes AN configuration component 1950, which is configured to configure the second AN to operate as an auxiliary node for control signaling communication between the UE and the first PN, for example, as in combination with Figure 17 As described in 1714. In some examples, the AN configuration component 1950 is configured to select a first AN from the AN set based on sidelink measurements, for example, as in combination with Figure 18 As described in 1810; configured to add a first AN via a first network interface connection to operate as an auxiliary node for the UE and the first PN, for example, as in combination Figure 18 As described in 1812; configured to execute the AN reselection procedure with the first AN, for example, as in combination Figure 18 As described in 1818; and / or configured to add a first AN via a first network interface connection to operate as an auxiliary node for the UE and the first PN, for example, as in combination Figure 18 As described in 1826.

[0289] Communication manager 1932 also includes UE context component 1952, which is configured to transmit UE context information associated with the UE to a second PN, for example, as in combination with Figure 17 As described in 1718. In some examples, the UE context component 1952 is configured to receive UE context information associated with the UE from the second PN, for example, as in conjunction with Figure 18 As described in 1820.

[0290] Communication manager 1932 also includes connection management component 1954, which is configured to release access link connections with the UE, for example, as in combination with Figure 17 As described in 1720. In some examples, the connection management component 1954 is configured to establish an access link connection with the UE, for example, as in conjunction with Figure 18 As described in 1816; configured to establish an access link connection with the UE based on the target node configuration, for example, as in combination with Figure 18 As described in 1824; and / or configured to establish an access link connection with the UE based on the target node configuration, for example, as in combination with Figure 18 As described in 1830.

[0291] Communication manager 1932 also includes communication component 1956, which is configured to communicate with the UE via an access link connection based on mmW frequency range, for example, as in combination with Figure 18 As described in 1806; and / or configured to communicate control signaling to the UE via a first AN, wherein the first PN and the first AN communicate via a first network interface connection, for example, as in combination Figure 18 As described in 1808.

[0292] The device may include execution Figure 17 And / or additional components of each block of the algorithm in the aforementioned flowchart of 18. Therefore, Figure 17 and / or Figure 18 Each block in the aforementioned flowchart may be executed by a component, and the device may include one or more of these components. These components may be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0293] In one configuration, device 1902, and particularly baseband unit 1904, includes means for receiving a node change trigger event notification. Example device 1902 also includes means for performing a node change procedure based on the node change trigger event notification. Example device 1902 further includes means for determining, based on at least one measurement included in a measurement report, to perform a handover procedure from a first PN to a second PN. Example device 1902 further includes means for transmitting a handover request to the second PN, the handover request including second AN side-link measurements from the measurement report. Example device 1902 further includes means for receiving a handover confirmation message from the second PN, the handover confirmation message including a target node configuration associated with the second PN and the second AN. Example device 1902 further includes means for transmitting a Radio Resource Control (RRC) reconfiguration message to the UE via the first AN, the RRC reconfiguration message including the target node configuration. Example device 1902 further includes means for configuring the second AN to operate as an auxiliary node for control signaling communication between the UE and the first PN. Example device 1902 also includes means for transmitting a Radio Resource Control (RRC) reconfiguration message to a UE via a second AN. Example device 1902 also includes means for transmitting UE context information associated with the UE to a second PN. Example device 1902 also includes means for releasing an access link connection with the UE. Example device 1902 also includes means for determining to perform a handover procedure from a first PN to a second PN based on at least one measurement included in a fault indication. Example device 1902 also includes means for transmitting a handover request to the second PN, the handover request including the second AN-side link measurement of the fault indication. Example device 1902 also includes means for receiving a handover confirmation message from the second PN, the handover confirmation message including a target node configuration associated with the second PN and the second AN. Example device 1902 also includes means for transmitting a Radio Resource Control (RRC) reconfiguration message to a UE via a first AN, the RRC reconfiguration message including the target node configuration. Example device 1902 also includes means for receiving a node change trigger event notification. Example device 1902 also includes means for performing a node change procedure based on a node change trigger event notification. Example device 1902 also includes means for transmitting data to a user equipment (UE) via an access link connection based on millimeter-wave (mmW) frequency range communication. Example device 1902 also includes means for transmitting control signaling to the UE via a first auxiliary node (AN), wherein the first PN and the first AN communicate via a first network interface connection. Example device 1902 also includes means for selecting a first AN from a set of ANs based on sidelink measurements. Example device 1902 also includes means for adding a first AN via the first network interface connection to operate as an auxiliary node for the UE and the first PN.Example device 1902 further includes means for transmitting a handover confirmation message to a second PN, the handover confirmation message including a target node configuration associated with the first PN and the first AN. Example device 1902 further includes means for establishing an access link connection with the UE based on the target node configuration. Example device 1902 further includes means for performing an AN reselection procedure with the first AN. Example device 1902 further includes means for receiving UE context information associated with the UE from the second PN, the second PN communicating data with the UE via a second access link connection. Example device 1902 further includes means for transmitting an RRC reconfiguration message to the UE via the first AN, the RRC reconfiguration message including a target node configuration associated with the first AN and the first PN. Example device 1902 further includes means for establishing an access link connection with the UE based on the target node configuration. Example device 1902 further includes means for adding the first AN via a first network interface connection to operate as an auxiliary node for the UE and the first PN. Example device 1902 further includes means for transmitting a handover confirmation message to the second PN, the handover confirmation message including a target node configuration associated with the first PN and the first AN. Example device 1902 also includes means for establishing an access link connection with the UE based on the target node configuration.

[0294] The aforementioned apparatus may be one or more of the aforementioned components in device 1902 configured to perform the functions described by the aforementioned apparatus. As described above, device 1902 may include TX processor 316, RX processor 370, and controller / processor 375. Thus, in one configuration, the aforementioned apparatus may be TX processor 316, RX processor 370, and controller / processor 375 configured to perform the functions described by the aforementioned apparatus.

[0295] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowcharts is an explanation of exemplary methods. It should be understood that the specific order or hierarchy of the boxes in these process / flowcharts can be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of the various boxes in an exemplary order and are not intended to be limited to the specific order or hierarchy presented.

[0296] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will readily be understood by those skilled in the art, and the universal principles defined herein may be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are to be granted the full scope consistent with the language of the claims, wherein references to the singular form of an element, unless specifically stated otherwise, are not intended to mean “one and only one,” but rather “one or more.” Terms such as “if,” “when,” and “at the time of” should be interpreted as meaning “under this condition,” rather than implying a direct temporal relationship or reaction. That is, these phrases (e.g., “when”) do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but only imply that an action will occur when a condition is met, without requiring a specific or immediate temporal constraint for the action to occur. The term “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 superior to or overriding other aspects. Unless specifically stated otherwise, the term “some / a” 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 multiple A, multiple B, or multiple 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 only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. Elements of all aspects described throughout this disclosure that are presently or hereafter known to those skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended as a donation to the public, whether or not such disclosure is explicitly stated in the claims. Terms such as “module,” “mechanism,” “element,” and “device” are not necessarily substitutes for the term “apparatus.” Thus, no claim element should be interpreted as an apparatus plus a function unless the element is explicitly stated using the phrase “apparatus for…”.

[0297] The following aspects are illustrative only and may be combined with other aspects or teachings described herein without limitation.

[0298] Aspect 1 is a wireless communication method for a user equipment (UE), comprising: establishing a sidelink connection with a first auxiliary node (AN) and an access link connection with a first master node (PN), wherein the first AN and the first PN communicate via a first network interface; determining the occurrence of a node change triggering event associated with at least one of the first AN and the first PN; executing a node change procedure based on the occurrence of the node change triggering event; and communicating with at least one of a second AN or a second PN based on the node change procedure, wherein the second AN and the second PN communicate via a second network interface.

[0299] Aspect 2 is the method of aspect 1, further including a side link connection with the first AN based on communication in the sub-6 GHz frequency range, and an access link connection with the first PN based on communication in the millimeter wave (mmW) frequency range.

[0300] Aspect 3 is a method of either Aspect 1 or Aspect 2, further comprising a side link connection with the first AN facilitating the transmission of control signaling between the UE and the first PN, and an access link connection with the first PN facilitating the transmission of data between the UE and the first PN.

[0301] Aspect 4 is a method of any of Aspects 1 to 3, further including determining that the occurrence of a node change triggering event is measured to trigger it.

[0302] Aspect 5 is a method of any of Aspects 1 to 4, further comprising: transmitting a measurement report to a first AN via a first PN based on measurements of at least one of a side link connection or an access link connection, wherein the measurement report includes one or more of the following: radio resource management (RRM) measurements associated with a second PN, a second PN identifier, a first AN side link measurement, a second AN identifier, a master node identifier associated with the second AN, and a second AN side link measurement.

[0303] Aspect 6 is a method of any of Aspects 1 to 5, further comprising measuring the first AN sidelink based on at least one of a sidelink synchronization signal (SLSS) associated with the first AN and a sidelink discovery message associated with the first AN.

[0304] Aspect 7 is a method of any of Aspects 1 to 6, further comprising: receiving a target node configuration associated with a second AN and a second PN via a side link connection with a first AN; establishing a second side link connection with the second AN based on the target node configuration; establishing a second access link connection with the second PN based on the target node configuration; and communicating with at least one of the second AN or the second PN while establishing the second side link connection and the second access link connection.

[0305] Aspect 8 is a method of any of Aspects 1 to 7, further including that the second AN and the first AN correspond to the same auxiliary node.

[0306] Aspect 9 is a method of any of Aspects 1 to 8, further comprising: determining that a side link connection with a first AN is unreliable based on measurements of the side link connection; selecting a second AN from the set of ANs based on one or more measurements performed on the set of ANs, the set of ANs including at least the second AN; and establishing a second side link connection with the second AN.

[0307] Aspect 10 is a method of any of Aspects 1 to 9, further comprising: determining that the second AN and the first AN are associated with the same master node based on the corresponding master node identifiers associated with the second AN and the first AN; transmitting an intra-PN change request to the second AN based on the determination; and receiving a radio resource control (RRC) configuration message from the second AN based on the intra-PN change request.

[0308] Aspect 11 is a method of any of Aspects 1 to 10, further comprising a corresponding master node identifier indicating that the second PN and the first PN correspond to the same master node.

[0309] Aspect 12 is a method of any of Aspects 1 to 11, further comprising: determining that the second AN and the first AN are associated with different master nodes based on the corresponding master node identifiers associated with the second AN and the first AN; and establishing a connection with the second PN via the second AN based on the determination.

[0310] Aspect 13 is a method of any of Aspects 1 to 12, further comprising the UE performing a measurement of at least one of a peer link connection or an access link connection based on a measurement gap configuration including an AN gap mode and a PN gap mode, wherein the AN gap mode and the PN gap mode are associated with the same gap time period.

[0311] Aspect 14 is a method of any of Aspects 1 to 12, further comprising the UE performing a measurement of at least one of a peer link connection or an access link connection based on a measurement gap configuration including an AN gap mode and a PN gap mode, the AN gap mode being associated with a first gap period and the PN gap mode being associated with a second gap period different from the first gap period.

[0312] Aspect 15 is a method of any of Aspects 1 to 14, further comprising determining that the occurrence of a node change triggering event is triggered by a radio link failure.

[0313] Aspect 16 is a method of any of Aspects 1 to 15, further comprising: identifying a radio link fault (RLF) associated with an access link connection to a first PN; transmitting a fault indication message to the first PN via a first AN; receiving a target node configuration associated with a second AN and a second PN; establishing a second side link connection with the second AN based on the target node configuration; establishing a second access link connection with the second PN based on the target node configuration; and communicating with at least one of the second AN and the second PN while establishing the second side link connection and the second access link connection.

[0314] Aspect 17 is a method of any of Aspects 1 to 16, further comprising the fault indication message including one or more of the following: radio resource management (RRM) measurement associated with the second PN, second PN identifier, first AN side link measurement, second AN identifier, master node identifier associated with the second AN, second AN side link measurement, and fault cause identifier.

[0315] Aspect 18 is a method of any of Aspects 1 to 17, further comprising: initiating a timer after transmitting a fault indication message to a first PN via a first AN, and wherein the UE receives a target node configuration from the first PN via a side link connection with the first AN before the timer expires.

[0316] Aspect 19 is a method of any of Aspects 1 to 18, further comprising: initiating a timer after transmitting a fault indication message to a first PN via a first AN; and executing a radio resource control (RRC) reconstruction procedure when the timer expires, wherein the UE receives a target node configuration while executing the RRC reconstruction procedure.

[0317] Aspect 20 is a method of any of Aspects 1 to 19, further comprising: identifying an RLF associated with a sidelink connection to the first AN; and performing a Radio Resource Control (RRC) re-establishment procedure based on the RLF associated with the access link connection and the RLF associated with the sidelink connection, wherein the UE receives a target node configuration while performing the RRC re-establishment procedure.

[0318] Aspect 21 is a method of any of Aspects 1 to 20, further comprising: identifying a radio link fault (RLF) associated with a side link connection to a first AN; and performing an inter-AN change based on the RLF.

[0319] Aspect 22 is an apparatus for wireless communication, comprising: at least one processor coupled to a memory and configured to implement the method as described in any of aspects 1 to 21.

[0320] Aspect 23 is a device for wireless communication, including means for implementing the methods of any of aspects 1 to 21.

[0321] Aspect 24 is a non-transient computer-readable storage medium that stores computer-executable code, wherein the code, when executed, causes a processor to implement a method as described in any of aspects 1 to 21.

[0322] Aspect 25 is a wireless communication method for a first master node (PN), comprising: receiving a node change triggering event notification; and executing a node change procedure based on the node change triggering event notification.

[0323] Aspect 26 is the method of aspect 25, further comprising the first PN communicating with the user equipment (UE) via an access link in the millimeter wave (mmW) frequency range, and the first PN communicating with the UE via a first auxiliary node (AN), the first PN and the first AN communicating via a first network interface.

[0324] Aspect 27 is a method of either Aspect 25 or Aspect 26, further comprising the first PN receiving a node change triggering event notification from the UE via the first AN, the node change triggering event including a measurement report including one or more of the following: radio resource management (RRM) measurements associated with the second PN, the second PN identifier, the first AN sidelink measurement, the second AN identifier, the master node identifier associated with the second AN, and the second AN sidelink measurement.

[0325] Aspect 28 is a method of any of Aspects 25 to 27, further comprising performing a node change procedure based on a node change trigger event notification, including: determining, based on at least one measurement included in a measurement report, to perform a handover procedure from a first PN to a second PN; transmitting a handover request to the second PN, the handover request including second AN side-link measurements from the measurement report; receiving a handover confirmation message from the second PN, the handover confirmation message including a target node configuration associated with the second PN and the second AN; and transmitting a radio resource control (RRC) reconfiguration message to the UE via the first AN, the RRC reconfiguration message including the target node configuration.

[0326] Aspect 29 is a method of any of Aspects 25 to 28, further comprising a first PN receiving a node change triggering event notification from a second AN, the node change triggering event notification including an intra-PN change request, the first PN and the second AN communicating via a second network interface.

[0327] Aspect 30 is a method of any of Aspects 25 to 29, further comprising performing a node change procedure based on a node change trigger event notification, including: configuring the second AN to operate as an auxiliary node for control signaling communication between the UE and the first PN; and transmitting a radio resource control (RRC) reconfiguration message to the UE via the second AN.

[0328] Aspect 31 is a method of any of Aspects 25 to 30, further comprising the first PN receiving a node change triggering event notification from the second PN, the node change triggering event notification including a UE context exchange request.

[0329] Aspect 32 is a method of any of Aspects 25 to 31, further comprising performing a node change procedure based on a node change trigger notification, including: transmitting UE context information associated with the UE to a second PN; and releasing the access link connection with the UE.

[0330] Aspect 33 is a method of any of Aspects 25 to 32, further comprising the first PN receiving a node change triggering event notification from the UE via the first AN, the node change triggering event including a fault indication including one or more of the following: radio resource management (RRM) measurement associated with the second PN, the second PN identifier, the first AN sidelink measurement, the second AN identifier, the master node identifier associated with the second AN, the second AN sidelink measurement, and a fault cause identifier.

[0331] Aspect 34 is a method of any of Aspects 25 to 33, further comprising performing a node change procedure based on a node change trigger event notification, including: determining, based on at least one measurement included in a fault indication, to perform a handover procedure from a first PN to a second PN; transmitting a handover request to the second PN, the handover request including a second AN-side link measurement of the fault indication; receiving a handover confirmation message from the second PN, the handover confirmation message including a target node configuration associated with the second PN and the second AN; and transmitting a Radio Resource Control (RRC) reconfiguration message to the UE via the first AN, the RRC reconfiguration message including the target node configuration.

[0332] Aspect 35 is an apparatus for wireless communication, comprising: at least one processor coupled to a memory and configured to implement the methods of any of aspects 25 to 34.

[0333] Aspect 36 is a device for wireless communication, including means for implementing the methods of any of aspects 25 to 34.

[0334] Aspect 37 is a non-transitory computer-readable storage medium that stores computer-executable code, wherein, when executed, the code causes a processor to implement methods as described in any of aspects 25 to 34.

[0335] Aspect 38 is a wireless communication method for a first master node (PN), comprising: receiving a node change triggering event notification; executing a node change procedure based on the node change triggering event notification; transmitting data to a user equipment (UE) via an access link connection based on communication in the millimeter wave (mmW) frequency range; and transmitting control signaling to the UE via a first auxiliary node (AN), wherein the first PN and the first AN communicate via a first network interface connection.

[0336] Aspect 39 is a method of aspect 38, further comprising the first PN receiving a node change triggering event notification from the second PN, the node change triggering event including a handover request including a sidelink measurement associated with an AN set, the AN set including at least the first AN.

[0337] Aspect 40 is a method of either Aspect 38 or Aspect 39, further comprising performing a node change procedure based on a node change trigger event notification, including: selecting a first AN from a set of ANs based on sidelink measurements; adding the first AN via a first network interface connection to operate as an auxiliary node for the UE and the first PN; transmitting a handover confirmation message to a second PN, the handover confirmation message including a target node configuration associated with the first PN and the first AN; and establishing an access link connection with the UE based on the target node configuration.

[0338] Aspect 41 is a method of any of Aspects 38 to 40, further comprising the first PN receiving a node change triggering event notification from the UE via a first AN, the node change triggering event notification including a radio resource control (RRC) re-establishment request.

[0339] Aspect 42 is a method of any of Aspects 38 to 41, further comprising performing a node change procedure based on a node change trigger notification, including: performing an AN reselection procedure with a first AN; receiving UE context information associated with a UE from a second PN, the second PN being connected to the UE via a second access link and transmitting data; transmitting an RRC reconfiguration message to the UE via the first AN, the RRC reconfiguration message including a target node configuration associated with the first AN and the first PN; and establishing an access link connection with the UE based on the target node configuration.

[0340] Aspect 43 is a method of any of Aspects 38 to 42, further comprising the first PN receiving a node change triggering event notification from a second PN, the node change triggering event including a handover request including a sidelink measurement associated with an AN set, the AN set including at least the first AN.

[0341] Aspect 44 is a method of any of Aspects 38 to 43, further comprising performing a node change procedure based on a node change trigger event notification, including: adding a first AN via a first network interface connection to operate as an auxiliary node for the UE and the first PN; transmitting a handover confirmation message to a second PN, the handover confirmation message including a target node configuration associated with the first PN and the first AN; and establishing an access link connection with the UE based on the target node configuration.

[0342] Aspect 45 is an apparatus for wireless communication, comprising: at least one processor coupled to a memory and configured to implement the methods of any of aspects 38 to 44.

[0343] Aspect 46 is a device for wireless communication, including means for implementing the methods of any of aspects 38 to 44.

[0344] Aspect 47 is a non-transitory computer-readable storage medium that stores computer-executable code, wherein, when executed, the code causes a processor to implement a method as described in any of aspects 38 to 44.

Claims

1. A wireless communication method for a user equipment (UE), comprising: A side link connection is established with the first auxiliary node AN and an access link connection is established with the first master node PN. The first AN and the first PN communicate via the first network interface. Determine the occurrence of a node change triggering event associated with at least one of the first AN and the first PN, wherein the occurrence of the node change triggering event is determined to be triggered by a radio link failure; The node change procedure is executed based on the occurrence of the node change trigger event; as well as Based on the node change procedure, communication is established with at least one of the second AN or the second PN, wherein the second AN and the second PN communicate via a second network interface. The method further includes: Identify the radio link fault (RLF) associated with the access link connected to the first PN; A fault indication message is transmitted from the first AN to the first PN; Receive the target node configuration associated with the second AN and the second PN; A second-side link connection is established with the second AN based on the target node configuration; Based on the target node configuration, establish a second access link connection with the second PN; and During the establishment of the second side link connection and the second access link connection, communication is made with at least one of the second AN and the second PN.

2. The method of claim 1, wherein The side link connection with the first AN is based on communication in the sub-6 GHz frequency range, and The access link connection with the first PN is based on communication within the millimeter-wave (mmW) frequency range.

3. The method of claim 1, wherein The side link connection with the first AN facilitates the transmission of control signaling between the UE and the first PN, and The access link connection with the first PN facilitates the transmission of data between the UE and the first PN.

4. The method of claim 1, further comprising: A measurement report is transmitted from the first PN to the first AN based on measurements of at least one of the side link connection or the access link connection. The measurement report includes one or more of the following: Radio Resource Management (RRM) measurements associated with the second PN, the second PN identifier, the first AN sidelink measurement, the second AN identifier, the master node identifier associated with the second AN, and the second AN sidelink measurement.

5. The method of claim 4, wherein the first AN sidelink measurement is based on at least one of a sidelink synchronization signal SLSS associated with the first AN and a sidelink discovery message associated with the first AN.

6. The method of claim 1, wherein the second AN and the first AN correspond to the same auxiliary node.

7. The method of claim 1, further comprising: The side link connection with the first AN is determined to be unreliable based on measurements of the side link connection. The second AN is selected from the AN set based on one or more measurements performed on the AN set, the AN set including at least the second AN; and Establish a second side link connection with the second AN.

8. The method of claim 7, further comprising: The second AN and the first AN are associated with the same master node based on the corresponding master node identifiers associated with the second AN and the first AN. Based on the determination, a request to change within the PN is transmitted to the second AN; as well as Based on the change request within the PN, a Radio Resource Control (RRC) configuration message is received from the second AN.

9. The method of claim 8, wherein the corresponding master node identifier indicates that the second PN and the first PN correspond to the same master node.

10. The method of claim 7, further comprising: The second AN and the first AN are associated with different master nodes based on the corresponding master node identifiers associated with the second AN and the first AN. as well as Based on the determination, a connection is established between the second AN and the second PN.

11. The method of claim 1, wherein the UE performs measurements on at least one of the sidelink connection or the access link connection based on a measurement gap configuration including an AN gap mode and a PN gap mode, and wherein the AN gap mode and the PN gap mode are associated with the same gap time period.

12. The method of claim 1, wherein the UE performs measurements on at least one of the sidelink connection or the access link connection based on a measurement gap configuration including an AN gap mode and a PN gap mode, the AN gap mode being associated with a first gap period and the PN gap mode being associated with a second gap period different from the first gap period.

13. The method of claim 1, wherein the fault indication message includes one or more of the following: a radio resource management (RRM) measurement associated with the second PN, a second PN identifier, a first AN sidelink measurement, a second AN identifier, a master node identifier associated with the second AN, a second AN sidelink measurement, and a fault cause identifier.

14. The method of claim 1, further comprising: After transmitting the fault indication message to the first PN via the first AN, a timer is started, and The UE receives the target node configuration from the first PN via the side link connection with the first AN before the timer expires.

15. The method of claim 1, further comprising: A timer is initiated after the fault indication message is transmitted from the first AN to the first PN; as well as When the timer expires, the Radio Resource Control (RRC) reconstruction procedure is executed. The UE receives the target node configuration while executing the RRC reconstruction procedure.

16. The method of claim 1, further comprising: The identifier is associated with the RLF connected to the side link of the first AN; as well as The Radio Resource Control (RRC) re-establishment procedure is performed based on the RLF associated with the access link connection and the RLF associated with the side link connection. The UE receives the target node configuration while executing the RRC reconstruction procedure.

17. The method of claim 1, further comprising: Identify the radio link fault (RLF) associated with the side link connection of the first AN; as well as Changes between ANs are performed based on the RLF.

18. An apparatus for wireless communication of a user equipment (UE), comprising: Memory; as well as At least one processor, said at least one processor being coupled to the memory and configured to: A side link connection is established with the first auxiliary node AN and an access link connection is established with the first master node PN. The first AN and the first PN communicate via the first network interface. Determine the occurrence of a node change triggering event associated with at least one of the first AN and the first PN, wherein the occurrence of the node change triggering event is determined to be triggered by a radio link failure; The node change procedure is executed based on the occurrence of the node change trigger event; as well as Based on the node change procedure, communication is established with at least one of the second AN or the second PN, wherein the second AN and the second PN communicate via a second network interface. The at least one processor is further configured to: Identify the radio link fault (RLF) associated with the access link connected to the first PN; A fault indication message is transmitted from the first AN to the first PN; Receive the target node configuration associated with the second AN and the second PN; A second-side link connection is established with the second AN based on the target node configuration; Based on the target node configuration, establish a second access link connection with the second PN; as well as During the establishment of the second side link connection and the second access link connection, communication is made with at least one of the second AN and the second PN.

19. An apparatus for wireless communication of a user equipment (UE), comprising: Memory; as well as At least one processor, the at least one processor being coupled to the memory and configured to perform the method as described in any one of claims 2-17.

20. A wireless communication method for a first master node PN, comprising: Receive a node change trigger event notification, wherein the node change trigger event is triggered by a radio link failure; The node change procedure is executed based on the node change trigger event notification. Data is transmitted to the user equipment (UE) via an access link based on communication within the millimeter-wave (mmW) frequency range. as well as The first auxiliary node (AN) communicates control signaling with the UE, and the first PN and the first AN communicate via a first network interface. The method further includes: Receive a fault indication message from the UE via the first AN; as well as The target node configuration associated with the second AN and the second PN is transmitted to the UE.

21. An apparatus for wireless communication of a first master node PN, comprising: Memory; as well as At least one processor, said at least one processor being coupled to the memory and configured to: Receive a node change trigger event notification, wherein the node change trigger event is triggered by a radio link failure; The node change procedure is executed based on the node change trigger event notification. Communication based on the millimeter wave (mmW) frequency range transmits data to the user equipment (UE) via an access link connection; as well as The first auxiliary node (AN) communicates control signaling with the UE, and the first PN and the first AN communicate via a first network interface. The at least one processor is further configured to: Receive a fault indication message from the UE via the first AN; and The target node configuration associated with the second AN and the second PN is transmitted to the UE.

Images