Wireless communication session for relay entity operating in visited public land mobile network

By establishing a wireless communication session between the relay entity and the network entity and configuring the relay entity to perform access node and UE functions, the problem of low efficiency and insufficient coverage of the relay entity in different public land mobile networks is solved, and the problem of low efficiency and insufficient coverage of wireless communication in different public land mobile networks is realized. Continuity and service stability of wireless communications.

CN118901276APending Publication Date: 2024-11-05QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380028835.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-28
Filing Date
2023-02-14
Publication Date
2024-11-05

AI Technical Summary

Technical Problem

In the interviewed public land mobile networks, the wireless communication session management of the relay entity has problems of inefficiency and insufficient coverage, especially when the relay entity spans different public land mobile networks, it is difficult to maintain continuous wireless communication services.

Method used

The relay entity establishes a wireless communication session with the associated network entity, configures the relay entity to perform access node functions and user equipment functions, and enables relay services to ensure that the relay entity can establish and maintain wireless in different public land mobile networks. Communication connection, including enabling access node functions and UE functions in VPLMN, performing relay services.

Benefits of technology

The wireless communication continuity and coverage expansion of relay entities in different public land mobile networks is realized, and the service stability of the mobile network and the communication quality of user equipment is improved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118901276A_ABST
    Figure CN118901276A_ABST
Patent Text Reader

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a relay entity may establish a wireless communication session with a network entity associated with a visited public land mobile network (VPLMN), where the relay entity is configured to perform an access node function and a user equipment (UE) function, and wherein establishing the wireless communication session comprises enabling wireless communication for both the access node function and the UE function via the VPLMN. The relay entity may perform a relay service via the access node function. Numerous other aspects are described.
Need to check novelty before this filing date? Find Prior Art

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This patent application claims priority to Greek patent application No. 20220100266, entitled "WIRELESS COMMUNICATION SESSIONS FOR RELAY ENTITIES OPERATING IN A VISITED PUBLIC LAND MOBILE NETWORK" filed on March 28, 2022 and assigned to the assignee of this patent application. The disclosure of the prior application is considered a part of this patent application and is incorporated by reference into this patent application. Technical Field

[0002] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for wireless communication sessions for a relay entity operating in a visited public land mobile network. Background Art

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). 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, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0004] A wireless network may include one or more base stations that support communications for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink communications and uplink communications. A "downlink" (or "DL") refers to the communication link from a base station to a UE, and an "uplink" (or "UL") refers to the communication link from a UE to a base station.

[0005] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better integrate with other open standards by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, using CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation, so as to better support mobile broadband Internet access. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0006] Some aspects described herein relate to a method of wireless communication performed by a relay entity. The method may include establishing a wireless communication session with a network entity associated with a visited public land mobile network (VPLMN), wherein the relay entity is configured to perform an access node function and a user equipment (UE) function, and wherein establishing the wireless communication session includes enabling wireless communication for both the access node function and the UE function via the VPLMN. The method may include performing a relay service via the access node function.

[0007] Some aspects described herein relate to a method of wireless communication performed by a network entity associated with a VPLMN. The method may include: establishing a wireless communication session with a relay entity, wherein the relay entity is configured to perform an access node function and a UE function, and wherein establishing the wireless communication session includes: enabling wireless communication for both the access node function and the UE function via the VPLMN. The method may include: receiving, from the relay entity, a communication associated with the access node function of the relay entity.

[0008] Some aspects described herein relate to an apparatus for wireless communication at a relay entity. The apparatus may include: a memory and one or more processors, the one or more processors coupled to the memory. The one or more processors may be configured to: establish a wireless communication session with a network entity associated with a VPLMN, wherein the relay entity is configured to perform an access node function and a UE function, and wherein establishing the wireless communication session includes: enabling wireless communication for both the access node function and the UE function via the VPLMN. The one or more processors may be configured to: perform relay services via the access node function.

[0009] Some aspects described herein relate to an apparatus for wireless communication at a network entity associated with a VPLMN. The apparatus may include: a memory and one or more processors, the one or more processors coupled to the memory. The one or more processors may be configured to: establish a wireless communication session with a relay entity, wherein the relay entity is configured to perform access node functions and UE functions, and wherein establishing the wireless communication session includes: enabling wireless communication for both the access node function and the UE function via the VPLMN. The one or more processors may be configured to: receive communications associated with the access node function of the relay entity from the relay entity.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a relay entity. The set of instructions, when executed by one or more processors of the relay entity, may cause the relay entity to establish a wireless communication session with a network entity associated with a VPLMN, wherein the relay entity is configured to perform access node functionality and UE functionality, and wherein establishing the wireless communication session includes: enabling wireless communication for both the access node functionality and the UE functionality via the VPLMN. The set of instructions, when executed by one or more processors of the relay entity, may cause the relay entity to perform relay services via the access node functionality.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network entity associated with a VPLMN. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to establish a wireless communication session with a relay entity, wherein the relay entity is configured to perform access node functions and UE functions, and wherein establishing the wireless communication session includes: enabling wireless communication for both the access node function and the UE function via the VPLMN. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to receive communications associated with the access node function of the relay entity from the relay entity.

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for establishing a wireless communication session with a network entity associated with a VPLMN, wherein the apparatus is configured to perform an access node function and a UE function, and wherein establishing the wireless communication session includes enabling wireless communication for both the access node function and the UE function via the VPLMN. The apparatus may include means for performing a relay service via the access node function.

[0013] Some aspects described herein relate to an apparatus for wireless communications associated with a VPLMN. The apparatus may include means for establishing a wireless communications session with a relay entity, wherein the relay entity is configured to perform an access node function and a UE function, and wherein establishing the wireless communications session includes enabling wireless communications for both the access node function and the UE function via the VPLMN. The apparatus may include means for receiving communications associated with the access node function of the relay entity from the relay entity.

[0014] The various aspects generally include methods, apparatuses, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices and / or processing systems as fully described herein with reference to the drawings and description and as illustrated in the drawings and description.

[0015] The features and technical advantages of examples according to the present disclosure have been outlined quite extensively above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0016] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] In order to fully understand the above-mentioned features of the present disclosure, a more specific description of the invention briefly summarized above can be obtained by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0018] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0019] Figure 2 is a diagram illustrating an example of a base station communicating with a user equipment (UE) in a wireless network according to the present disclosure.

[0020] Figure 3 is a diagram illustrating an example of a radio access network according to the present disclosure.

[0021] Figure 4 is a diagram illustrating an example of an integrated access and backhaul network architecture according to the present disclosure.

[0022] Figure 5 is a diagram illustrating an example of an open radio access network (O-RAN) architecture according to the present disclosure.

[0023] Figure 6 is a diagram illustrating an example of side link communication according to the present disclosure.

[0024] Figure 7 is a diagram illustrating an example of side link communication and access link communication according to the present disclosure.

[0025] Figure 8 is a diagram of an example associated with establishing a wireless communication session of a relay entity operating in a visited public land mobile network according to the present disclosure.

[0026] Fig. 9 is a diagram illustrating an example process performed, for example, by a relay entity according to the present disclosure.

[0027] Fig.10 is a diagram illustrating an example process performed, for example, by a network entity according to the present disclosure.

[0028] Fig.11 is an illustration of an example apparatus for wireless communications.

[0029] Fig.12 is an illustration of an example apparatus for wireless communications. Summary of the invention

[0030] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be interpreted as being limited to any specific structure or function presented throughout the present disclosure. On the contrary, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods implemented using other structures, functions, or structures and functions in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0031] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a 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.

[0032] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT, and / or post-5G RATs (e.g., 6G).

[0033] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network or may include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more base stations 110 (shown as BS110a, BS110b, BS110c, and BS110d), a user equipment (UE) 120 or a plurality of UEs 120 (shown as UE 120a, UE120b, UE120c, UE120d, and UE120e), and / or other network entities. The base station 110 is an entity that communicates with the UE 120. The base station 110 (sometimes referred to as a BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). In addition, although the base station 110 Figure 1 , but aspects of the present disclosure are not limited thereto. In some aspects, the Figure 3 and Figure 4 A more detailed description of the integrated access and backhaul (IAB) architecture and / or in accordance with the combined Figure 5 The functions of base station 110 are decomposed by referring to the open radio access network (O-RAN) architecture described in more detail. Each base station 110 can provide communication coverage for a specific geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" can refer to the coverage area of ​​base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

[0034] Base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UE 120 associated with the femto cell (e.g., UE 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or a home base station. In Figure 1In the example shown, BS 110a may be a macro base station for macrocell 102a, BS 110b may be a pico base station for picocell 102b, and BS 110c may be a femto base station for femtocell 102c. A base station may support one or more (eg, three) cells.

[0035] In some examples, the cell may not necessarily be stationary, and the geographic area of ​​the cell may move depending on the location of the mobile base station 110 (e.g., a mobile base station). In some examples, the base stations 110 may be interconnected with each other and / or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 using any suitable transport network through various types of backhaul interfaces (such as direct physical connections or virtual networks).

[0036] The wireless network 100 may include one or more relay stations. A relay station is an entity that can receive transmissions of data from an upstream station (e.g., a base station 110 or a UE 120) and transmit transmissions of data to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown, BS 110d (eg, a relay base station) may communicate with BS 110a (eg, a macro base station) and UE 120d to facilitate communication between BS 110a and UE 120d. A base station 110 that relays communications may be referred to as a relay station, relay base station, relay, or the like.

[0037] The wireless network 100 may be a heterogeneous network including different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico base station, a femto base station, and a relay base station may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0038] A network controller 130 may be coupled to or in communication with a set of base stations 110 and may provide coordination and control for the base stations 110. The network controller 130 may communicate with the base stations 110 via backhaul communication links. The base stations 110 may also communicate directly with each other or indirectly via wireless or wired backhaul communication links.

[0039] UE 120 may be distributed throughout wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. UE 120 may be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate via a wireless medium.

[0040] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0041] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a specific RAT and may operate on one or more frequencies. RAT may be referred to as a radio technology, air interface, etc. Frequency may be referred to as a carrier, frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks may be deployed.

[0042] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary to communicate with each other) using one or more side link channels. For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0043] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz–7.125 GHz) and FR2 (24.25 GHz–52.6 GHz). It should be understood that, although portions of FR1 are greater than 6 GHz, FR1 is often (interchangeably) referred to as the “below 6 GHz” band in various documents and articles. Similar naming issues sometimes occur with respect to FR2, which is often (interchangeably) referred to as the “millimeter wave” band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the “millimeter wave” band by the International Telecommunication Union (ITU).

[0044] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz–24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, and therefore can effectively extend the features of FR1 and / or FR2 to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations beyond 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz–71GHz), FR4 (52.6GHz–114.25GHz), and FR5 (114.25GHz–300GHz). Each of these higher frequency bands falls within the EHF band.

[0045] In view of the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be lower than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0046] In some aspects, a relay entity described elsewhere herein may correspond to UE 120. In such aspects, the relay entity may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may establish a wireless communication session with a network entity associated with a visited public land mobile network (VPLMN), wherein the relay entity is configured to perform an access node function and a UE function, and wherein establishing the wireless communication session includes: enabling wireless communication for both the access node function and the UE function via the VPLMN; and performing relay services via the access node function. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0047] In some aspects, the network entity described elsewhere herein may correspond to the base station 110. In such aspects, the network entity may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may establish a wireless communication session with a relay entity, wherein the relay entity is configured to perform access node functionality and UE functionality, and wherein establishing the wireless communication session includes: enabling wireless communication for both the access node functionality and the UE functionality via the VPLMN; and receiving communications from the relay entity associated with the access node functionality of the relay entity. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0048] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 Different than described.

[0049] Figure 22 is a diagram illustrating an example 200 of base station 110 communicating with UE 120 in wireless network 100 according to the present disclosure. Base station 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1).

[0050] At the base station 110, the transmit processor 220 may receive data intended for the UE 120 (or a set of UEs 120) from the data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCS) for the UE 120 based at least in part on one or more channel quality indicators (CQI) received from the UE 120. The base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS selected for the UE 120, and provide data symbols for the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource allocation information (SRPI)) and control information (e.g., CQI requests, grants, and / or upper layer signaling), and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signals (PSS) or secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., pre-coding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modulators) (shown as modems 232a to 232t). For example, each output symbol stream may be provided to a modulator component (shown as MOD) of the modem 232. Each modem 232 may process a corresponding output symbol stream (e.g., for OFDM) using a corresponding modulator component to obtain an output sample stream. Each modem 232 may also process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a to 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0051] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the base station 110 and / or other base stations 110, and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal may be provided to a demodulator component (shown as DEMOD) of the modem 254. Each modem 254 may use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain input samples. Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modem 254, may perform MIMO detection on the received symbols where applicable, and may provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260, and may provide decoded control information and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other things. In some examples, one or more components of the UE 120 may be included in the housing 284.

[0052] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base station 110 via the communication unit 294.

[0053] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0054] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, reference Figures 8 to 12 ) any aspects of any of the methods described herein.

[0055] At the base station 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component of the modem 232 shown as DEMOD), detected by the MIMO detector 236 where applicable, and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some examples, the modem 232 of the base station 110 may include a modulator and a demodulator. In some examples, the base station 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to execute the instructions described herein (e.g., reference 2 Figures 8 to 12 ) any aspects of any of the methods described herein.

[0056] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other components of the VPLMN may perform one or more techniques associated with wireless communication sessions with relay entities operating in the VPLMN, as described in more detail elsewhere herein. In some aspects, the network entity described herein is a base station 110, is included in a base station 110, or includes Figure 2 In some aspects, the relay entity described herein is a UE 120, is included in a UE 120, or includes Figure 2 One or more components of the UE 120 are shown. The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Fig. 9 The process of 900 Fig.10 1000 and / or other processes described herein. Memory 242 and memory 282 may store data and program codes for base station 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed (e.g., directly or after compilation, conversion, and / or interpretation) by one or more processors of base station 110 and / or UE 120, may cause the one or more processors, UE 120, and / or base station 110 to perform or direct, for example Fig. 9 The process of 900 Fig.10 The operations of process 1000 and / or other processes described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0057] In some aspects, the relay entity includes means for establishing a wireless communication session with a network entity associated with a VPLMN, wherein the relay entity is configured to perform an access node function and a UE function, and wherein establishing the wireless communication session includes: enabling wireless communication for both the access node function and the UE function via the VPLMN; and / or means for performing relay services via the access node function. In some aspects, the means for the relay entity to perform operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0058] In some aspects, the network entity includes means for establishing a wireless communication session with a relay entity, wherein the relay entity is configured to perform an access node function and a UE function, and wherein establishing the wireless communication session includes: enabling wireless communication for both the access node function and the UE function via a VPLMN; and / or means for receiving communications associated with the access node function of the relay entity from the relay entity. In some aspects, the means for the network entity to perform operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0059] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0060] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 Different than described.

[0061] Figure 3 is a diagram illustrating an example 300 of a radio access network according to the present disclosure.

[0062] As shown by reference numeral 305, a conventional (e.g., 3G, 4G, or LTE) radio access network may include multiple base stations 310 (e.g., access nodes (ANs)), each of which communicates with a core network via a wired backhaul link 315 (such as a fiber optic connection). The base stations 310 may communicate with UEs 320 via access links 325 (which may be wireless links). In some aspects, Figure 3 The base station 310 shown may be Figure 1 The base station 110 is shown. In some aspects, Figure 3 The UE 320 shown may be Figure 1 UE 120 is shown.

[0063] As shown by reference numeral 330, the radio access network may include a wireless backhaul network, sometimes referred to as an IAB network. In an IAB network, at least one base station is an anchor base station 335, which communicates with the core network via a wired backhaul link 340 (such as a fiber optic connection). The anchor base station 335 may also be referred to as an IAB donor (or IAB-donor). The IAB network may include one or more non-anchor base stations 345, sometimes referred to as relay base stations or IAB nodes (or IAB-nodes). The non-anchor base station 345 may communicate directly or indirectly with the anchor base station 335 via one or more backhaul links 350 (e.g., via one or more non-anchor base stations 345) to form a backhaul path to the core network for carrying backhaul traffic. The backhaul link 350 may be a wireless link. The anchor base station 335 and / or the non-anchor base station 345 may communicate with one or more UEs 355 via an access link 360 (which may be a wireless link for carrying access traffic). In some aspects, Figure 3 The anchor base station 335 and / or the non-anchor base station 345 shown may be Figure 1 The base station 110 is shown. In some aspects, Figure 3 The UE 355 shown may be Figure 1 UE 120 is shown.

[0064] As shown by reference numeral 365, in some aspects, a radio access network including an IAB network may use millimeter wave technology and / or directional communication (e.g., beamforming) for communication between base stations and / or UEs (e.g., between two base stations, between two UEs, and / or between a base station and a UE). For example, a wireless backhaul link 370 between base stations may use millimeter wave signals to carry information and / or may use beamforming to be directed toward a target base station. Similarly, a wireless access link 375 between a UE and a base station may use millimeter wave signals and / or may be directed toward a target wireless node (e.g., a UE and / or a base station). In this way, inter-link interference may be reduced.

[0065] Figure 3 The configuration of the base station and UE in is shown as an example, and other examples are also contemplated. For example, Figure 3 The illustrated one or more base stations may be replaced by one or more UEs that communicate via a UE-to-UE access network (e.g., a peer-to-peer network or a device-to-device network). In this case, an anchor node may refer to a UE that communicates directly with a base station (e.g., an anchor base station or a non-anchor base station).

[0066] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 Different than described.

[0067] Figure 4is a diagram illustrating an example 400 of an IAB network architecture according to the present disclosure.

[0068] like Figure 4 As shown, the IAB network may include an IAB donor 405 (shown as an IAB-donor) connected to the core network via a wired connection (shown as a wired backhaul). For example, the Ng interface of the IAB donor 405 may terminate at the core network. Additionally or alternatively, the IAB donor 405 may be connected to one or more devices of the core network that provide a core access and mobility management function (AMF). In some aspects, the IAB donor 405 may include a base station 110, such as an anchor base station, as described above in conjunction with Figure 3 As described. As shown in the figure, the IAB donor 405 may include a control unit (CU) that may perform access node controller (ANC) functions and / or AMF functions. The CU may configure a distributed unit (DU) of the IAB donor 405 and / or may configure one or more IAB nodes 410 (e.g., a mobile terminal (MT) and / or DU of the IAB node 410), which are connected to the core network via the IAB donor 405. Therefore, the CU of the IAB donor 405 may control and / or configure the entire IAB network, which is connected to the core network via the IAB donor 405, such as by using control messages and / or configuration messages (e.g., radio resource control (RRC) configuration messages or F1 application protocol (F1-AP) messages).

[0069] like Figure 4As further shown, the IAB network may include an IAB node 410 (shown as IAB-node 1, IAB-node 2, and IAB-node 3), which is connected to the core network via an IAB donor 405. As shown, the IAB node 410 may include an MT function (sometimes also referred to as a UE function (UEF)) and may include a DU function (sometimes also referred to as an access node function (ANF)). The MT function of an IAB node 410 (e.g., a child node) may be controlled and / or scheduled by another IAB node 410 (e.g., a parent node of the child node) and / or by an IAB donor 405. The DU function of an IAB node 410 (e.g., a parent node) may control and / or schedule other IAB nodes 410 (e.g., a child node of the parent node) and / or UE 120. Therefore, the DU may be referred to as a scheduling node or a scheduling component, and the MT may be referred to as a scheduled node or a scheduled component. In some aspects, the IAB donor 405 may include the DU function but not the MT function. That is, the IAB donor 405 may configure, control and / or schedule the communication of the IAB node 410 and / or the UE 120. The UE 120 may include only the MT function and not the DU function. That is, the communication of the UE 120 may be controlled and / or scheduled by the IAB donor 405 and / or the IAB node 410 (e.g., the parent node of the UE 120).

[0070] When a first node controls and / or schedules communications for a second node (e.g., when the first node provides a DU function for the MT function of the second node), the first node may be referred to as the parent node of the second node, and the second node may be referred to as the child node of the first node. The child node of the second node may be referred to as the grandchild node of the first node. Thus, the DU function of the parent node may control and / or schedule communications for the child node of the parent node. The parent node may be an IAB donor 405 or an IAB node 410, and the child node may be an IAB node 410 or a UE 120. Communications of the MT function of the child node may be controlled and / or scheduled by the parent node of the child node.

[0071] like Figure 4 As further shown, the link between UE 120 (e.g., which has only MT functionality but not DU functionality) and IAB donor 405 or between UE 120 and IAB node 410 may be referred to as access link 415. Access link 415 may be a wireless access link that provides UE 120 with radio access to the core network via IAB donor 405 and optionally via one or more IAB nodes 410. Thus, Figure 4 The illustrated network may be referred to as a multi-hop network or a wireless multi-hop network.

[0072] like Figure 4As further shown, the link between the IAB donor 405 and the IAB node 410 or between two IAB nodes 410 may be referred to as a backhaul link 420. The backhaul link 420 may be a wireless backhaul link that provides radio access to the core network to the IAB node 410 via the IAB donor 405 and optionally via one or more other IAB nodes 410. In the IAB network, network resources (e.g., time resources, frequency resources, and / or space resources) for wireless communication may be shared between the access link 415 and the backhaul link 420. In some aspects, the backhaul link 420 may be a primary backhaul link or an auxiliary backhaul link (e.g., a backup backhaul link). In some aspects, if the primary backhaul link fails, becomes congested and / or becomes overloaded, etc., the auxiliary backhaul link may be used. For example, if the primary backhaul link between the IAB-node 2 and the IAB-node 1 fails, the backup link 425 between the IAB-node 2 and the IAB-node 3 may be used for backhaul communication. As used herein, a node or wireless node may be referred to as an IAB donor 405 or an IAB node 410 .

[0073] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 Different than described.

[0074] Figure 5 5 is a diagram illustrating an example of an O-RAN architecture according to the present disclosure. In some aspects, one or more of the wireless networks and / or radio access networks described herein (e.g., the wireless network 100, the radio access network shown by reference numeral 305, the IAB network shown by reference numerals 330, 365, and 400, or similar wireless networks) may be based on Figure 5 The O-RAN architecture shown is further broken down.

[0075] like Figure 5 As shown, the O-RAN architecture may include a CU 510 that communicates with a core network 520 via a backhaul link. In addition, the CU 510 may communicate with one or more DUs 530 via corresponding midhaul links. The DUs 530 may each communicate with one or more radio units (RUs) 540 via corresponding fronthaul links, and the RUs 540 may each communicate with corresponding UEs 120 via radio frequency (RF) access links. The DUs 530 and RUs 540 may also be referred to as O-RAN DUs (O-DUs) 530 and O-RAN RUs (O-RUs) 540, respectively.

[0076] In some aspects, the DU 530 and the RU 540 may be implemented according to a functional split architecture in which the functionality of a base station 110 (e.g., an eNB or gNB) is provided by the DU 530 and one or more RUs 540 that communicate via a fronthaul link. Thus, as described herein, the base station 110 may include a DU 530 and one or more RUs 540 that may be co-located or geographically distributed. In some aspects, the DU 530 and the associated RU 540 may communicate via the fronthaul link to exchange real-time control plane information via a lower layer split (LLS) control plane (LLS-C) interface, non-real-time management information via an LLS management plane (LLS-M) interface, and / or user plane information via an LLS user plane (LLS-U) interface.

[0077] Thus, the DU 530 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 540. For example, in some aspects, the DU 530 may host a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (e.g., forward error correction (FEC) encoding and decoding, scrambling and / or modulation and demodulation) based at least in part on the lower layer functional split. Higher layer control functions such as packet data convergence protocol (PDCP), RRC, and / or service data adaptation protocol (SDAP) may be hosted by the CU 510. The RU 540 controlled by the DU 530 may correspond to a logical node that hosts RF processing functions and low PHY layer functions (e.g., fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, and / or physical random access channel (PRACH) extraction and filtering) based at least in part on the lower layer functional split. Thus, in the O-RAN architecture, the RU 540 handles all over-the-air (OTA) communications with the UE 120, and the real-time and non-real-time aspects of the control plane and user plane communications with the RU 540 are controlled by the corresponding DU 530, which enables the DU 530 and the CU 510 to be implemented in a cloud-based RAN architecture.

[0078] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 Different than described.

[0079] Figure 6 is a diagram illustrating an example 600 of sidelink communications according to the present disclosure.

[0080] According to some aspects, one or more of the wireless networks and / or radio access network architectures described herein (e.g., wireless network 100, the radio access network illustrated by reference numeral 305, the IAB network illustrated by reference numerals 330, 365, and 400, the wireless network described in conjunction with reference numeral 500, or similar wireless networks) may be implemented by two UEs (e.g., UE 120) communicating in a sidelink. For example, Figure 6 As shown, the first UE 605-1 can communicate with the second UE 605-2 (and one or more other UEs 605) via one or more side link channels 610. UEs 605-1 and 605-2 can communicate using one or more side link channels 610 for P2P communication, D2D communication, V2X communication (e.g., which may include V2V communication, V2I communication and / or V2P communication) and / or mesh networks. In some aspects, UE 605 (e.g., UE 605-1 and / or UE 605-2) may correspond to one or more other UEs described elsewhere herein, such as UE 120. In some aspects, one or more side link channels 610 may use a PC5 interface and / or may operate in a high frequency band (e.g., a 5.9 GHz band). Additionally or alternatively, UE 605 may use global navigation satellite system (GNSS) timing to synchronize the timing of a transmit time interval (TTI) (e.g., a frame, subframe, time slot, or symbol).

[0081] like Figure 6As further shown, the one or more sidelink channels 610 may include a physical sidelink control channel (PSCCH) 615, a physical sidelink shared channel (PSSCH) 620, and / or a physical sidelink feedback channel (PSFCH) 625. The PSCCH 615 may be used to communicate control information, similar to a physical downlink control channel (PDCCH) and / or a physical uplink control channel (PUCCH) used for cellular communication with the base station 110 via an access link or access channel. The PSSCH 620 may be used to communicate data, similar to a physical downlink shared channel (PDSCH) and / or a physical uplink shared channel (PUSCH) used for cellular communication with the base station 110 via an access link or access channel. For example, the PSCCH 615 may carry sidelink control information (SCI) 630, which may indicate various control information for sidelink communication, such as one or more resources (e.g., time resources, frequency resources, and / or space resources), wherein a transport block (TB) 635 may be carried on the PSSCH 620. TB 635 may include data. PSFCH 625 may be used to communicate sidelink feedback 640, such as hybrid automatic repeat request (HARQ) feedback (eg, acknowledgement or negative acknowledgement (ACK / NACK) information), transmit power control (TPC), and / or scheduling request (SR).

[0082] Although shown on PSCCH 615, in some aspects, SCI 630 may include multiple communications in different levels, such as a first level SCI (SCI-1) and a second level SCI (SCI-2). SCI-1 may be sent on PSCCH 615. SCI-2 may be sent on PSSCH 620. SCI-1 may include, for example, an indication of one or more resources (e.g., time resources, frequency resources, and / or space resources) on PSSCH 620, information for decoding sidelink communications on PSSCH, quality of service (QoS) priority value, resource reservation period, PSSCH DMRS mode, SCI format for SCI-2, beta offset for SCI-2, number of PSSCH DMRS ports, and / or MCS. SCI-2 may include information associated with data transmission on PSSCH 620, such as a HARQ process ID, a new data indicator (NDI), a source identifier, a destination identifier, and / or a channel state information (CSI) report trigger.

[0083] In some aspects, one or more sidelink channels 610 may use a resource pool. For example, a scheduling assignment (e.g., included in SCI 630) may be sent in a subchannel across time using specific resource blocks (RBs). In some aspects, data transmissions associated with a scheduling assignment (e.g., on PSSCH 620) may occupy adjacent RBs in the same subframe as the scheduling assignment (e.g., using frequency division multiplexing). In some aspects, the scheduling assignment and the associated data transmission are not sent on adjacent RBs.

[0084] In some aspects, UE 605 may operate using a sidelink transmission mode (e.g., Mode 1) in which resource selection and / or scheduling is performed by base station 110. For example, UE 605 may receive a grant (e.g., in downlink control information (DCI) or in an RRC message, such as for a configured grant) from base station 110 for sidelink channel access and / or scheduling. In some aspects, UE 605 may operate using a transmission mode (e.g., Mode 2) in which resource selection and / or scheduling is performed by UE 605 (e.g., instead of base station 110). In some aspects, UE 605 may perform resource selection and / or scheduling by sensing channel availability for transmission. For example, UE 605 may measure RSSI parameters associated with various side link channels (e.g., sidelink-RSSI (S-RSSI) parameters), may measure RSRP parameters associated with various side link channels (e.g., PSSCH-RSRP parameters), and / or may measure RSRQ parameters associated with various side link channels (e.g., PSSCH-RSRQ parameters); and may select a channel for sending side link communications based at least in part on the measurement results.

[0085] Additionally or alternatively, the UE 605 may perform resource selection and / or scheduling using the SCI 630 received in the PSCCH 615, which may indicate occupied resources and / or channel parameters. Additionally or alternatively, the UE 605 may perform resource selection and / or scheduling by determining a channel busy rate (CBR) associated with each sidelink channel, which may be used for rate control (e.g., by indicating a maximum number of resource blocks that the UE 605 may use for a particular set of subframes).

[0086] In a transmission mode in which resource selection and / or scheduling is performed by the UE 605, the UE 605 may generate a sidelink grant and may transmit the grant in the SCI 630. The sidelink grant may indicate, for example, one or more parameters (e.g., transmission parameters) to be used for an upcoming sidelink transmission, such as one or more resource blocks (e.g., for TB 635) to be used for an upcoming sidelink transmission on the PSSCH 620, one or more subframes to be used for an upcoming sidelink transmission, and / or an MCS to be used for an upcoming sidelink transmission. In some aspects, the UE 605 may generate a sidelink grant that indicates one or more parameters (such as the periodicity of the sidelink transmission) for semi-persistent scheduling (SPS). Additionally or alternatively, the UE 605 may generate a sidelink grant for event-driven scheduling, such as for an on-demand sidelink message.

[0087] As indicated above, Figure 6 are provided as examples. Other examples can be found in Figure 6 Different than described.

[0088] Figure 7 is a diagram illustrating an example 700 of side link communications and access link communications according to the present disclosure.

[0089] like Figure 7 As shown, the relay entity 705 and the UE 710 can communicate with each other via a side link, as described above in conjunction with Figure 6 As further shown in the figure, in some sidelink modes, the base station 110 can communicate with one or both of the relay entity 705 or the UE 710 via an access link. For example, in Figure 7 In the example, the base station communicates with the relay entity 705 via an access link. The relay entity 705 and / or the UE 710 may correspond to one or more UEs described elsewhere herein, such as Figure 1 120. Thus, a direct link between UEs 120 (e.g., via a PC5 interface) may be referred to as a side link, and a direct link between base station 110 and UE 120 (e.g., via a Uu interface) may be referred to as an access link. Side link communications may be sent via a side link, and access link communications may be sent via an access link. Access link communications may be downlink communications (from base station 110 to UE 120) or uplink communications (from UE 120 to base station 110).

[0090] In some aspects, a UE operating in a sidelink may act as a base station or similar network entity to relay communications from other UEs to enable the other UEs to communicate with a core network, etc. In some aspects, when a UE operating in a sidelink acts as a base station or similar network entity to relay communications from other UEs, the UE may be referred to as a mobile base station relay (MBSR). For example, Figure 7 As shown, the relay entity 705 communicates with the base station 110 (e.g., via an access link (e.g., Uu interface) for the UE function (sometimes referred to as IAB-UE function) of the relay entity 705 and / or via a backhaul / midhaul link (e.g., F1 interface) for the access node function (sometimes referred to as IAB-DU function) of the relay entity 705), but the UE 710 does not communicate directly with the base station (e.g., there is no access link or other link between the UE 710 and the base station 110). Therefore, in some aspects, the relay entity 705 may act as a relay between the base station 110 and the UE 710 or other UEs. That is, the relay entity 705 may receive communications intended for the base station 110 from the UE 710 and relay the communications to the base station 110. Additionally or alternatively, the relay entity 705 may receive communications intended for the UE 710 from the base station 110 and relay the communications to the UE 710.

[0091] For example, the relay entity 705 may be a vehicle mounted relay (VMR) that may be installed in a vehicle with a known path (such as a bus, tram, or train, etc.), or may be installed in a vehicle with a variable path (such as a taxi, an end-user car, etc.). VMRs and similar relay entities may be able to communicate with a fixed network entity (such as a Figure 7 In the embodiment of the present invention, the base station 110 shown, or a similar entity such as CU 510, DU 530, RU 540, etc.) receives wireless communication coverage, the stationary network entity may be referred to as a donor base station and / or donor gNB and may provide coverage to neighboring UEs such as UE 710. In aspects where the relay entity is a VMR, the VMR may provide coverage to end-user UEs located within a corresponding transport (e.g., a bus, tram, train, taxi, end-user car, etc.) and / or other UEs in the vicinity of the VMR.

[0092] In some aspects, the relay entity 705 may be configured according to the IAB architecture and may therefore include a combination of Figures 3 to 5In such aspects, the relay entity may be configured to perform access node functions (e.g., IAB-DU functions) and UE functions (e.g., IAB-UE functions), and thus may include an MT portion that performs UE functions (sometimes referred to as IAB-MT) and may include a DU portion that performs access node functions (sometimes referred to as IAB-DU). For example, the relay entity 705 may be configured as a first relay 715, which may include an IAB-MT 720 and an IAB-DU 725. In addition, in some aspects, the donor base station (e.g., Figure 7 The base station 110 in FIG. 1 may also be a DU and thus communicates with the CU ( Figure 7 In such aspects, the first repeater 715 may also communicate with the CU via an F1 interface, and more specifically, the IAB-DU 725 may communicate with the CU via an F1 interface.

[0093] In some other aspects, the relay entity 705 may be configured according to a Velcro architecture in which the relay entity acts as an independent base station and UE. In other words, the relay entity 705 may also include additional functions (such as functions performed by the CU of the IAB architecture) rather than just acting as a DU as described in conjunction with the IAB architecture. In such aspects, the relay entity 705 may be configured to perform access node functions and UE functions. Thus, the relay entity 705 may include: a UE portion that performs UE functions; and may include a base station portion that performs access node functions. For example, the relay entity 705 may be configured as a second relay 730, which may include a UE portion 735 and a base station portion 740. In such aspects, the N2 / N3 interface between the relay and the macro cell may operate on the user plane of a packet data unit (PDU) session established by the UE portion 735 of the relay entity to a core network, which may be the core network of a public land mobile network (PLMN) used by the UE portion 735 of the relay entity, or may be the core network of a different PLMN (e.g., a PLMN not used by the UE portion 735).

[0094] Because the relay entity 705 can perform access node functions and UE functions, the relay entity 705 can establish a Uu interface and / or a PC5 interface with another UE. Figure 7In the example shown, the relay entity 705 may establish a PC5 interface with the UE 710 via the IAB-MT 720 or the UE portion 735, respectively, and the relay entity 705 may establish a Uu interface with the UE 710 via the IAB-DU 725 or the base station portion 740, respectively. If the relay entity 705 then leaves the coverage of the home PLMN (HPLMN) and enters the coverage of the VPLMN, the UE function of the relay entity 705 may use certain legacy roaming procedures to connect to the VPLMN, and thus continue to perform wireless communications. However, the access node function of the relay entity 705 cannot use such legacy roaming procedures to connect to the VPLMN. Therefore, when outside the HPLMN, the access node function may not continue to work, resulting in reduced coverage for any UE connected to the relay entity 705 via the Uu interface, and even causing radio link failures for such UEs.

[0095] Some techniques and apparatuses described herein enable access node functions (e.g., IAB-DU 725, base station portion 740, etc.) of a relay entity (e.g., relay entity 705) to roam so that the access node functions can establish wireless communication sessions within a VPLMN and thus continue to provide coverage to one or more UEs over a Uu interface. More specifically, in some aspects, the relay entity can communicate with network entities (e.g., Figure 7The relay entity 705 may be configured to perform access node functions (e.g., via the IAB-DU 725 and / or the base station portion 740) and UE functions (e.g., via the IAB-MT 720 and / or the UE portion 735), and establishing the wireless communication session may include enabling wireless communication for both the access node function and the UE function via the VPLMN. In aspects where the access node function is performed by the IAB-DU as part of the IAB architecture, the IAB-DU may connect to a donor base station in the VPLMN and may begin operating as an IAB-DU in the VPLMN, and / or the IAB-DU may maintain an F1 interface to the CU in the HPLMN using Internet Protocol (IP) connectivity provided by a link between the IAB-MT and the donor base station. And in aspects where access node functionality is performed by a base station portion of the relay entity as part of a Velcro architecture, the base station portion may connect to an AMF associated with a donor base station in a VPLMN and may begin operating as a base station in the VPLMN, and / or the base station portion of the relay entity may maintain an N2 interface to an AMF associated with an HPLMN using IP connectivity provided by a link between a UE portion of the relay entity and the donor base station. Thus, the relay entity may provide increased coverage, including coverage outside of the HPLMN, thereby improving link quality and reducing radio link failures for UEs connected to the relay entity.

[0096] As indicated above, Figure 7 are provided as examples. Other examples can be found in Figure 7 Different than described.

[0097] Figure 8 8 is a diagram of an example 800 associated with establishing a wireless communication session with a relay entity operating in a VPLMN according to the present disclosure. Figure 8 As shown, a relay entity 805 (e.g., relay entity 705) and a network entity 810 (e.g., base station 110, CU, DU, and / or RU) may communicate with each other. In addition, the relay entity 805 may also communicate with a UE 815 (e.g., UE 120, UE 320, UE 355, UE 710, etc.), and the relay entity 805 may relay communications from the network entity 810 to the UE 815 and / or from the UE 815 to the network entity 810, as in conjunction with Figure 7As described. That is, the relay entity 805 may be configured to perform both access node functionality and UE functionality, as described. In some aspects, the network entity 810 may be a donor base station or a donor gNB. In some aspects, the relay entity 805 and the network entity 810 may be part of a wireless network (e.g., the wireless network 100, the radio access network shown by reference numeral 305, the IAB network shown by reference numerals 330, 365, and 400, or a similar wireless network). The relay entity 805 and the network entity 810 may be part of a wireless network 100, such as the wireless network 100, the radio access network shown by reference numerals 305, the IAB network shown by reference numerals 330, 365, and 400, or a similar wireless network. Figure 8 The wireless connection has been established before the operations shown. For example, in some aspects, the UE functionality of the relay entity 805 (e.g., the IAB-MT 720 and / or the UE portion 735 of the second relay 730) may be Figure 8 The operations shown have previously established a wireless connection with the network entity 810 (such as via legacy roaming procedures, etc.).

[0098] As indicated by reference numeral 825, in some aspects, upon entering the VPLMN 820 or other VPLMNs, the relay entity 805 may determine whether the access node function is permitted to operate in the VPLMN 820. In some aspects, the relay entity 805 may determine whether the access node function is permitted to operate in the VPLMN 820 based at least in part on a preset list of preferred PLMNs and / or geographic regions. For example, the access node function may be permitted to operate in some PLMNs (e.g., the VPLMN 820 and / or other PLMNs) but not in other PLMNs, and thus the relay entity 805 may be preset with a list indicating which PLMNs the access node function is permitted to operate in. Furthermore, in some aspects, each of the preferred PLMNs and / or geographic regions included in the list may include a corresponding priority value, and when the relay entity 805 is within the coverage of multiple PLMNs, the relay entity 805 may select a PLMN based at least in part on these priority values. For example, relay entity 805 may select VPLMN 820 based at least in part on a priority value associated with VPLMN 820. In some aspects, relay entity 805 (e.g., a UE function of relay entity 805) may select a PLMN for wireless communication that is associated with a highest priority value (e.g., VPLMN 820) and / or may select a PLMN for wireless communication based at least in part on whether an access node function is permitted to operate in VPLMN 820 (e.g., when IAB-DU 725 is permitted to operate as an IAB-node in VPLMN 820 and / or whether base station portion 740 is permitted to operate as a base station in VPLMN 820).

[0099] In some aspects, the determination indicated by reference numeral 825 may be based at least in part on signaling from the network entity 810, such as signaling received during registration of the UE functionality of the relay entity 805 with the VPLMN 820. More specifically, during registration, the relay entity 805 may send a request to the network entity 810 for the access node functionality to operate in the VPLMN 820, the request being associated with the UE functionality; and the relay entity 805 may then determine whether to permit the access node functionality to operate in the VPLMN 820 based at least in part on the indication received from the network entity 810. In some aspects, the indication received from the network entity 810 may be received in response to a request sent by the relay entity 805 for the access node functionality to operate in the VPLMN 820, while in some other aspects, the network entity 810 may provide the indication without an explicit request from the relay entity (e.g., of course, during a registration process associated with the UE functionality, etc.).

[0100] In addition, in aspects where the relay entity 805 sends a request for the access node function to operate in the VPLMN 820, an AMF, etc. associated with the VPLMN 820 may accept the request and permit the access node function to register with the VPLMN 820. Alternatively, the AMF, etc. associated with the VPLMN 820 may reject the request for the access node function to operate in the VPLMN 820, such as by sending a 5G Mobility Management (5GMM) cause value, etc. In some aspects, the 5GMM cause value may indicate that the relay entity 805 is "not allowed to operate as an IAB-node in this PLMN" or that the relay entity 805 is "not allowed to operate as a relay in this PLMN", etc. In such aspects, the rejection from the network entity 810 may trigger PLMN selection at the UE function (e.g., IAB-MT 720 or UE portion 735) of the relay entity 805 to find another VPLMN that allows operation as an IAB-node and / or as a relay node. In this regard, in some aspects, establishing a wireless communication session with a network entity 810 associated with a VPLMN 820 (as described in more detail below in conjunction with reference number 840) may be based at least in part on another VPLMN's rejection of a request for an access node functionality to operate in the other VPLMN, which request is associated with the UE functionality of the relay entity 805.

[0101] As described in more detail below in conjunction with reference numeral 840, establishing a wireless communication session between the relay entity 805 and the network entity 810 may include an access node function of the relay entity connecting to the network entity 810, or the access node function communicating with the HPLMN via a link between the UE function of the relay entity 805 and the network entity 810 (e.g., maintaining an interface to the HPLMN using IP connectivity provided by the link between the UE function of the relay entity 805 and the network entity 810). In aspects of the access node function communicating with the HPLMN via the link between the UE function and the network entity 810, the relay entity may first require permission from the network entity 810 and / or the VPLMN 820 to operate on the radio resources of the HPLMN within the coverage of the VPLMN 820. Therefore, as indicated by reference numeral 830, the relay entity 805 (more specifically, the IAB-MT 720 and / or the UE portion 735) may send a request to the network entity 810 to operate on the radio resources of the HPLMN within the VPLMN 820. Additionally or alternatively, as indicated by reference numeral 835, the relay entity 805 (more specifically, the IAB-MT 720 and / or the UE portion 735) may receive an indication from the network entity 810 as to whether the access node function is permitted to operate on the radio resources of the HPLMN within the VPLMN 820.

[0102] As indicated by reference numeral 840, the relay entity 805 may establish a wireless communication session with a network entity 810 associated with the VPLMN 820. Furthermore, as described above, the relay entity 805 may be configured to perform access node functionality (e.g., via the IAB-DU 725 and / or the base station portion 740) and UE functionality (e.g., via the IAB-MT 720 and / or the UE portion 735), and establishing the wireless communication session may include enabling wireless communication for both the access node functionality and the UE functionality via the VPLMN 820. In this manner, the relay entity 805 may continue to serve other UEs (e.g., UE 815) even though the relay entity 805 is within the VPLMN 820 (e.g., even though the relay entity 805 may be roaming).

[0103] As described above in conjunction with reference numerals 830 and 835, in some aspects, establishing a wireless communication session with a network entity 810 associated with a VPLMN 820 includes: the access node function communicating with the HPLMN via a link between the UE function and the network entity 810. In such aspects, the network entity 810 and / or the VPLMN 820 can effectively provide coverage extension for the HPLMN. Again, this may require that the relay entity 805 be permitted to operate on the radio resources of the HPLMN within the coverage of the VPLMN 820, which in some aspects can be established via the communications described above in conjunction with reference numerals 835 and 840.

[0104] In some other aspects, establishing a wireless communication session with a network entity 810 associated with a VPLMN 820 may include establishing a connection between an access node function and the network entity 810. For example, in some aspects, the relay entity 805 may correspond to a Figure 7 The described first relay 715, and thus the UE functionality, may correspond to the IAB-MT 720, and the access node functionality may correspond to the IAB-DU 725. In such aspects, establishing a wireless communication session with a network entity associated with the VPLMN may include establishing a connection between the IAB-DU and the network entity 810 (e.g., the IAB-DU may begin to operate as an IAB-DU in the VPLMN 820). For example, establishing a connection between the IAB-DU and the network entity 810 may include performing an IAB node integration procedure in the VPLMN 820. For example, the relay entity 805 may perform the IAB node integration procedure specified in 3GPP Technical Specification (TS) 38.401 subclause 8.12.1 in the VPLMN 820.

[0105] In some aspects, a list of certain parameters for performing the IAB node integration procedure may be preset for the relay entity 805. More specifically, in some aspects, performing the IAB node integration procedure in the VPLMN 820 may be based at least in part on a preset list, which includes, for each of a plurality of preferred PLMNs or geographic regions: a data network name (DNN) and a single network slice selection assistance information (S-NSSAI) pair associated with an operation and maintenance (OAM) PDU session, and a fully qualified domain name (FQDN) associated with the OAM server. Advantageously, the IAB node integration procedure (e.g., the IAB node integration procedure specified in 3GPP TS 38.401 subclause 8.12.1, etc.) may not require an inter-PLMN connection (e.g., a connection between the HPLMN and the VPLMN 820).

[0106] In some other aspects, establishing a connection between the IAB-DU of the relay entity 805 and the network entity 810 may include performing an inter-donor full migration procedure. For example, a wireless communication session associated with the IAB-DU may be fully migrated from a donor base station or other network entity associated with the HPLMN to a network entity 810 associated with the VPLMN 820. In such aspects, there may be an established link (e.g., IP connectivity) between the donor base station or other network entity associated with the HPLMN and the network entity 810 associated with the VPLMN 820 in order to perform the inter-donor full migration procedure. Advantageously, the inter-donor full migration procedure may enable service continuity for a UE (e.g., UE 815) that moves with the relay entity 805.

[0107] In some other aspects, the relay entity 805 may correspond to a Figure 7 The depicted second relay 730, and thus the UE functionality, may correspond to the UE portion 735 of the second relay 730, and the access node functionality may correspond to the base station portion 740 of the second relay. In such aspects, establishing a wireless communication session with a network entity 810 associated with the VPLMN 820 may include establishing a connection between a base station portion of the relay entity 805 and an AMF associated with the VPLMN 820 (e.g., the base station portion may begin operating as a base station in the VPLMN 820).

[0108] In some aspects, establishing a connection between the base station portion and the AMF associated with the VPLMN 820 may include: performing a bootstrapping procedure in the VPLMN 820. In some aspects, the bootstrapping procedure in the VPLMN 820 may be based at least in part on a preset list of bootstrapping parameters. More specifically, performing the bootstrapping procedure in the VPLMN 820 may be based at least in part on a preset list, and for each of a plurality of preferred PLMNs or geographic regions, the preset list includes: a DNN and S-NSSAI pair associated with an OAM PDU session, a FQDN associated with an OAM server, and a DNN and S-NSSAI pair to be used to establish a backhaul link. In such aspects, the UE function of the relay entity 805 may use the DNN and S-NSSAI associated with the VPLMN 820 to establish the OAM PDU session. Once the OAM PDU session is established, the UE portion of the relay entity 805 may receive a configuration associated with the base station portion of the relay entity 805 from the OAM server associated with the VPLMN 820 (in other words, the relay entity 805 connects to the OAM server and downloads the base station configuration to operate in the VPLMN 820). Once the configuration is complete, the relay entity 805 may establish an N2 interface between the base station portion of the relay entity 805 and the AMF associated with the VPLMN 820. Advantageously, the bootstrapping procedure in the VPLMN 820 may not require an inter-PLMN connection (e.g., a connection between the HPLMN and the VPLMN 820).

[0109] In some other aspects, establishing a wireless communication session with a network entity 810 associated with a VPLMN 820 may include performing an inter-PLMN handover procedure associated with a base station portion of a relay entity 805. In such aspects, a persistent UE PDU session for backhaul may be handed over by the HPLMN to the VPLMN 820, wherein the relay entity 805 (more specifically, the base station portion of the relay entity 805) continues to operate as a base station of the HPLMN. The inter-PLMN handover procedure may be based at least in part on a preset list of handover parameters. More specifically, performing the inter-PLMN handover procedure may be based at least in part on a preset list, which includes, for each of a plurality of preferred PLMNs or geographic regions, a DNN and S-NSSAI pair associated with an OAM PDU session, a FQDN associated with an OAM server, and a DNN and S-NSSAI pair to be used to establish a backhaul link. Relay entity 805 (and more specifically, the UE functionality of relay entity 805) may therefore establish an OAM PDU session using the DNN and S-NSSAI associated with VPLMN 820. Once the OAM PDU session is established, the UE portion of relay entity 805 may receive a configuration associated with the base station portion of relay entity 805 from an OAM server associated with VPLMN 820 (in other words, relay entity 805 may connect to the OAM server and download the base station configuration to operate in VPLMN 820).

[0110] Once configured, the relay entity 805 may establish a PDU session for backhaul in the VPLMN 820 based at least in part on the preset list of handover parameters, and may establish an N2 interface between the base station portion of the relay entity 805 and the AMF associated with the VPLMN 820. Thus, the base station portion of the relay entity 805 may simultaneously act as a base station of the HPLMN and a base station of the VPLMN 820. Thus, any UE (e.g., UE 815) connected to the relay entity 805 may be handed over by the relay entity 805 from the HPLMN to the VPLMN 820 (e.g., the UE connected to the relay entity 805 is handed over from a base station instance operating for the HPLMN to a base station instance operating for the VPLMN 820). After the UE handover is completed, the relay entity 805 may cease to operate as a base station of the HPLMN. That is, the relay entity 805 may end the wireless communication session with the HPLMN based at least in part on handing over the UE connected to the relay entity 805 from the HPLMN to the VPLMN 820. Additionally or alternatively, the relay entity 805 may also release the PDU session for backhaul of the HPLMN. Advantageously, the inter-PLMN handover procedure may enable service continuity for UEs (e.g., UE 815) that move with the relay entity 805.

[0111] As shown by reference numeral 845, once the relay entity 805 establishes a wireless communication session with the network entity 810, the relay entity 805 may perform relay services via the access node function of the relay entity 805 (e.g., via the IAB-DU or the base station portion of the relay entity 805). For example, the network entity 810 may receive communications associated with the access node function of the relay entity 805 from the relay entity 805. Figure 7 As described, in some aspects, performing relay services via access node functionality may include receiving communications intended for network entity 810 from UE 815 and relaying the communications to network entity 810. Additionally or alternatively, performing relay services via access node functionality may include receiving communications intended for UE 815 from network entity 810 and relaying the communications to UE 815. In this regard, a relay entity such as a VMR may advantageously continue to provide relay services within the VPLMN, thereby increasing coverage for connected UEs and reducing radio link failures.

[0112] As indicated above, Figure 8 are provided as examples. Other examples can be found in the Figure 8 Different than described.

[0113] Fig. 9 is a diagram illustrating an example process 900 performed, for example, by a relay entity in accordance with the present disclosure. Example process 900 is an example of a relay entity (eg, relay entity 805) performing operations associated with a wireless communication session of the relay entity operating in a VPLMN.

[0114] like Fig. 9 As shown, in some aspects, process 900 may include: establishing a wireless communication session with a network entity (e.g., network entity 810) associated with a VPLMN (e.g., VPLMN 820), wherein the relay entity is configured to perform access node functionality and UE functionality, and wherein establishing the wireless communication session includes: enabling wireless communication for both the access node functionality and the UE functionality via the VPLMN (block 910). For example, the relay entity (e.g., using Fig.11 The depicted communication manager 1108 and / or registration component 1110) may establish a wireless communication session with a network entity associated with a VPLMN, wherein the relay entity is configured to perform access node functionality and UE functionality, and wherein establishing the wireless communication session includes enabling wireless communication for both the access node functionality and the UE functionality via the VPLMN, as described above.

[0115] like Fig. 9 As further shown, in some aspects, process 900 may include: performing relay services via access node functionality (block 920). For example, the relay entity (e.g., using Fig.11 The depicted communications manager 1108 and / or relay component 1112) can perform relay services via access node functionality, as described above.

[0116] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0117] In a first aspect, process 900 includes determining whether an access node function is permitted to operate in a VPLMN.

[0118] In a second aspect, alone or in combination with the first aspect, whether the access node function is permitted to operate in the VPLMN is determined based at least in part on at least one of: a preset list of preferred PLMNs or a preset list of PLMNs in which the access node function is not permitted to operate.

[0119] In a third aspect, either alone or in combination with one or more of the first and second aspects, each preferred PLMN of at least one of the preferred PLMNs comprises a corresponding priority value.

[0120] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 900 includes selecting the VPLMN based at least in part on a priority value associated with the VPLMN.

[0121] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, determining whether to permit the access node function to operate in the VPLMN is based at least in part on an indication received from the network entity.

[0122] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the indication received from the network entity is received in response to a request for the access node function to operate in the VPLMN, the request being associated with the UE function.

[0123] In a seventh aspect, either alone or in combination with one or more of aspects 1 to 6, establishing the wireless communication session with the network entity associated with the VPLMN is based at least in part on another VPLMN's rejection of a request for the access node function to operate in the other VPLMN, the request being associated with the UE function.

[0124] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, establishing the wireless communication session with the network entity associated with the VPLMN includes: the access node function communicating with the HPLMN via a link between the UE function and the network entity.

[0125] In a ninth aspect, either alone or in combination with one or more of aspects one to eight, the relay entity determines whether the access node function is permitted to operate the radio resources of the HPLMN within the VPLMN based at least in part on at least one of: a preset list of preferred PLMNs or a preset list of PLMNs in which the access node function is not permitted to operate.

[0126] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, each of the preferred PLMNs comprises a corresponding priority value.

[0127] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, process 900 includes selecting the VPLMN based at least in part on a priority value associated with the VPLMN.

[0128] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, the process 900 includes: sending a request to the network entity to operate radio resources of the HPLMN within the VPLMN.

[0129] In a thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, determining whether to allow the access node function to operate radio resources of the HPLMN within the VPLMN is based at least in part on an indication received from the network entity.

[0130] In a fourteenth aspect, either alone or in combination with one or more of the first to thirteenth aspects, the indication received from the network entity is received in response to the request to operate radio resources of the HPLMN within the VPLMN.

[0131] In the fifteenth aspect, either alone or in combination with one or more of the first to fourteenth aspects, establishing the wireless communication session with the network entity associated with the VPLMN is based at least in part on another VPLMN's rejection of a request by the access node function to operate radio resources of the HPLMN within the other VPLMN, the request being associated with the UE function.

[0132] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the access node function is associated with an IAB-DU.

[0133] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, establishing the wireless communication session with the network entity associated with the VPLMN includes: establishing a connection between the IAB-DU and the network entity.

[0134] In an eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, establishing the wireless communication session with the network entity associated with the VPLMN includes: performing an IAB node integration procedure in the VPLMN associated with the IAB-DU.

[0135] In a nineteenth aspect, either alone or in combination with one or more of the first to eighteenth aspects, the IAB node integration procedure is performed in the VPLMN at least in part based on a preset list, for each preferred PLMN in a plurality of preferred PLMNs, the preset list comprising: a DNN and S-NSSAI pair associated with an OAM PDU session, and a FQDN associated with an OAM server.

[0136] In a twentieth aspect, alone or in combination with one or more of the first to nineteenth aspects, establishing the wireless communication session with the network entity associated with the VPLMN comprises: performing an inter-donor full migration procedure associated with the IAB-DU.

[0137] In a twenty-first aspect, either alone or in combination with one or more of the first to twentieth aspects, the access node functionality is associated with a base station portion of the relay entity.

[0138] In the twenty-second aspect, alone or in combination with one or more of the first to twenty-first aspects, establishing the wireless communication session with the network entity associated with the VPLMN includes: establishing a connection between the base station part of the relay entity and the AMF associated with the VPLMN.

[0139] In a twenty-third aspect, either alone or in combination with one or more of aspects one to twenty-second, establishing the wireless communication session with the network entity associated with the VPLMN includes executing a bootstrapping procedure in the VPLMN associated with the base station portion of the relay entity.

[0140] In the twenty-fourth aspect, alone or in combination with one or more of the first to twenty-third aspects, the bootstrapping procedure is performed in the VPLMN at least in part based on a preset list, and for each preferred PLMN in a plurality of preferred PLMNs, the preset list includes: a DNN and S-NSSAI pair associated with an OAM PDU session, an FQDN associated with an OAM server, and a DNN and S-NSSAI pair to be used to establish a backhaul link.

[0141] In a twenty-fifth aspect, alone or in combination with one or more of the first to twenty-fourth aspects, performing the bootstrapping procedure in the VPLMN establishes an OAM PDU session based at least in part on the UE function using a DNN and S-NSSAI associated with the VPLMN.

[0142] In a twenty-sixth aspect, alone or in combination with one or more of the first to twenty-fifth aspects, process 900 includes receiving a configuration associated with the base station portion of the relay entity from an OAM server associated with the VPLMN.

[0143] In the twenty-seventh aspect, alone or in combination with one or more of aspects one to twenty-six, process 900 includes establishing an N2 interface between the base station portion of the relay entity and the AMF associated with the VPLMN based at least in part on receiving the configuration associated with the base station portion of the relay entity.

[0144] In the twenty-eighth aspect, either alone or in combination with one or more of the first to twenty-seventh aspects, establishing the wireless communication session with the network entity associated with the VPLMN includes executing an inter-PLMN handover procedure associated with the base station portion of the relay entity.

[0145] In a twenty-ninth aspect, alone or in combination with one or more of the first to twenty-eighth aspects, performing the inter-PLMN handover procedure comprises: handing over the UE PDU session from the HPLMN to the VPLMN.

[0146] In the thirtieth aspect, alone or in combination with one or more of the first to twenty-ninth aspects, the inter-PLMN handover procedure is performed at least in part based on a preset list, which, for each preferred PLMN among multiple preferred PLMNs, includes: a DNN and S-NSSAI pair associated with an OAM PDU session, an FQDN associated with an OAM server, and a DNN and S-NSSAI pair to be used to establish a backhaul link.

[0147] In the thirty-first aspect, alone or in combination with one or more of the first to thirtieth aspects, performing the inter-PLMN handover procedure is at least partially based on the UE function establishing an OAM PDU session using the DNN and S-NSSAI associated with the VPLMN.

[0148] In a thirty-second aspect, alone or in combination with one or more of the first to thirty-first aspects, process 900 includes receiving a configuration associated with the base station portion of the relay entity from an OAM server associated with the VPLMN.

[0149] In a thirty-third aspect, either alone or in combination with one or more of the first to thirty-second aspects, process 900 includes establishing a PDU session for backhaul in the VPLMN based at least in part on the preset list.

[0150] In aspect thirty-four, alone or in combination with one or more of aspects one to thirty-three, process 900 includes establishing an N2 interface between the base station portion of the relay entity and the AMF associated with the VPLMN based at least in part on receiving the configuration associated with the base station portion of the relay entity.

[0151] In a thirty-fifth aspect, alone or in combination with one or more of the first to thirty-fourth aspects, the process 900 includes: handing over, by the relay entity, a UE connected to the relay entity from the HPLMN to the VPLMN.

[0152] In a thirty-sixth aspect, either alone or in combination with one or more of aspects one to thirty-fifth, process 900 includes ending a wireless communication session with the HPLMN based at least in part on handing over the UE connected to the relay entity from the HPLMN to the VPLMN.

[0153] although Fig. 9 An example block diagram of process 900 is shown, but in some aspects, process 900 may include Fig. 9 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 900. Additionally or alternatively, two or more blocks of the blocks of process 900 may be performed in parallel.

[0154] Fig.10 is a diagram illustrating an example process 1000 performed, for example, by a network entity in accordance with the present disclosure. Example process 1000 is an example of a network entity (eg, network entity 810) performing operations associated with a wireless communication session for a relay entity operating in a VPLMN.

[0155] like Fig.10 As shown, in some aspects, process 1000 may include: establishing a wireless communication session with a relay entity (e.g., relay entity 805), wherein the relay entity is configured to perform access node functionality and UE functionality, and wherein establishing the wireless communication session includes: enabling wireless communication for both the access node functionality and the UE functionality via a VPLMN (block 1010). For example, the network entity (e.g., using Fig.12The depicted communication manager 1208 and / or registration component 1210) may establish a wireless communication session with a relay entity, wherein the relay entity is configured to perform access node functions and UE functions, and wherein establishing the wireless communication session includes: enabling wireless communication for both the access node function and the UE function via the VPLMN, as described above.

[0156] like Fig.10 As further shown, in some aspects, process 1000 may include receiving, from a relay entity, a communication associated with an access node function of the relay entity (block 1020). Fig.12 The depicted communications manager 1208 and / or receiving component 1202) can receive communications from the network entity associated with the access node functionality of the relay entity, as described above.

[0157] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0158] In a first aspect, process 1000 includes sending an indication to the relay entity of whether the access node function is permitted to operate in the VPLMN.

[0159] In a second aspect, either alone or in combination with the first aspect, the indication is sent in response to a request for the access node function to operate in the VPLMN, the request being associated with the UE function of the relay entity.

[0160] In a third aspect, alone or in combination with one or more of the first and second aspects, establishing the wireless communication session with the relay entity comprises: the access node function communicating with the HPLMN via a link between the UE function and the network entity.

[0161] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the process 1000 includes: receiving a request from the relay entity to operate radio resources of the HPLMN within the VPLMN.

[0162] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the process 1000 includes: sending an indication to the relay entity of whether the access node function is permitted to operate on the radio resources of the HPLMN within the VPLMN.

[0163] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the access node function is associated with an IAB-DU.

[0164] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, establishing the wireless communication session with the relay entity includes: establishing a connection between the IAB-DU and the network entity.

[0165] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, establishing the wireless communication session with the relay entity includes: performing an IAB node integration procedure in the VPLMN associated with the IAB-DU.

[0166] In a ninth aspect, either alone or in combination with one or more of the first to eighth aspects, the IAB node integration procedure is performed in the VPLMN at least in part based on a preset list, for each preferred PLMN in a plurality of preferred PLMNs, the preset list comprising: a DNN and S-NSSAI pair associated with an OAM PDU session, and a FQDN associated with an OAM server.

[0167] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, establishing the wireless communication session with the relay entity includes: performing an inter-donor full migration procedure associated with the IAB-DU.

[0168] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the access node functionality is associated with a base station portion of the relay entity.

[0169] In the twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, establishing the wireless communication session with the relay entity includes: establishing a connection between the base station part of the relay entity and the AMF associated with the VPLMN.

[0170] In a thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, establishing the wireless communication session with the relay entity comprises: performing a bootstrapping procedure in the VPLMN associated with the base station portion of the relay entity.

[0171] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the bootstrapping procedure is performed in the VPLMN at least in part based on a preset list, and for each preferred PLMN in a plurality of preferred PLMNs, the preset list includes: a DNN and S-NSSAI pair associated with an OAM PDU session, an FQDN associated with an OAM server, and a DNN and S-NSSAI pair to be used to establish a backhaul link.

[0172] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, performing the bootstrapping procedure in the VPLMN establishes an OAM PDU session based at least in part on the UE function using a DNN and S-NSSAI associated with the VPLMN.

[0173] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, process 1000 includes: sending a configuration associated with the base station portion of the relay entity to the relay entity.

[0174] In the seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, process 1000 includes: establishing an N2 interface between the base station part of the relay entity and the AMF associated with the VPLMN based at least in part on sending the configuration associated with the base station part of the relay entity.

[0175] In an eighteenth aspect, either alone or in combination with one or more of the first to seventeenth aspects, establishing the wireless communication session with the relay entity comprises performing an inter-PLMN handover procedure associated with the base station portion of the relay entity.

[0176] In a nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, performing the inter-PLMN handover procedure comprises: handing over the UE PDU session from the HPLMN to the VPLMN.

[0177] In the twentieth aspect, either alone or in combination with one or more of the first to nineteenth aspects, the inter-PLMN handover procedure is performed at least in part based on a preset list, which, for each preferred PLMN among a plurality of preferred PLMNs, comprises: a DNN and S-NSSAI pair associated with an OAM PDU session, an FQDN associated with an OAM server, and a DNN and S-NSSAI pair associated with a backhaul link.

[0178] In a twenty-first aspect, alone or in combination with one or more of the first to twentieth aspects, performing the inter-PLMN handover procedure is based at least in part on the UE function establishing an OAM PDU session using the DNN and S-NSSAI associated with the VPLMN.

[0179] In a twenty-second aspect, alone or in combination with one or more of the first to twenty-first aspects, process 1000 includes: sending a configuration associated with the base station portion of the relay entity to the relay entity.

[0180] In a twenty-third aspect, alone or in combination with one or more of the first to twenty-second aspects, process 1000 includes: establishing a PDU session for backhaul in the VPLMN based at least in part on the preset list.

[0181] In aspect twenty-four, alone or in combination with one or more of aspects one to twenty-three, process 1000 includes establishing an N2 interface between the base station portion of the relay entity and the AMF associated with the VPLMN based at least in part on sending the configuration associated with the base station portion of the relay entity.

[0182] although Fig.10 An example block diagram of process 1000 is shown, but in some aspects, process 1000 may include Fig.10 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1000. Additionally or alternatively, two or more of the blocks in the process 1000 may be performed in parallel.

[0183] Fig.11 1 is a diagram of an example apparatus 1100 for wireless communication. Apparatus 1100 may be a relay entity (e.g., relay entity 805), or a relay entity may include apparatus 1100. In some aspects, apparatus 1100 includes a receiving component 1102 and a sending component 1104, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a base station, or another wireless communication device) using receiving component 1102 and sending component 1104. As further shown, apparatus 1100 may include a communication manager 1108 (e.g., communication manager 140). Communication manager 1108 may include one or more of registration component 1110, relay component 1112, or determination component 1114, etc.

[0184] In some aspects, the apparatus 1100 may be configured to perform Figure 8 Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as Fig. 9 The process 900. In some aspects, Fig.11 The device 1100 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.11 One or more of the components shown may be combined with Figure 2Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0185] The receiving component 1102 may receive communications from the device 1106, such as reference signals, control information, data communications, or combinations thereof. The receiving component 1102 may provide the received communications to one or more other components of the device 1100. In some aspects, the receiving component 1102 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1100. In some aspects, the receiving component 1102 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE 120 .

[0186] The transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1106. In some aspects, one or more other components of the device 1100 may generate communications and may provide the generated communications to the transmitting component 1104 for transmission to the device 1106. In some aspects, the transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1106. In some aspects, the transmitting component 1104 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the depicted UE 120. In some aspects, the transmit component 1104 can be co-located with the receive component 1102 in a transceiver.

[0187] The registration component 1110 can establish a wireless communication session with a network entity associated with the VPLMN, wherein the relay entity is configured to perform access node functionality and UE functionality, and wherein establishing the wireless communication session includes enabling wireless communication for both the access node functionality and the UE functionality via the VPLMN. The relay component 1112 can perform relay services via the access node functionality.

[0188] Determining component 1114 can determine whether to permit access node functionality to operate in a VPLMN. Determining component 1114 can select a VPLMN based at least in part on a priority value associated with the VPLMN. Determining component 1114 can select a VPLMN based at least in part on a priority value associated with the VPLMN.

[0189] The sending component 1104 can send a request to the network entity to operate radio resources of the HPLMN within the VPLMN.The receiving component 1102 can receive a configuration associated with a base station portion of the relay entity from an OAM server associated with the VPLMN.

[0190] The registering component 1110 can handover the UE connected to the relay entity from the HPLMN to the VPLMN.The registering component 1110 can end the wireless communication session with the HPLMN based at least in part on handing over the UE connected to the relay entity from the HPLMN to the VPLMN.

[0191] Fig.11 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.11 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.11 Two or more components shown may be implemented in a single component, or Fig.11 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.11 The component set (one or more components) shown may be described as being executable by Fig.11 Another component shown may be a collection of components that perform one or more functions.

[0192] Fig.12 1 is a diagram of an example apparatus 1200 for wireless communication. Apparatus 1200 may be a network entity (e.g., network entity 810), or a network entity may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a sending component 1204, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using receiving component 1202 and sending component 1204. As further shown, apparatus 1200 may include a communication manager 1208. Communication manager 1208 may include registration component 1210, etc.

[0193] In some aspects, the apparatus 1200 may be configured to perform Figure 8Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Fig.10 In some aspects, the apparatus 1200 and / or Fig.12 One or more of the components shown may include a combination of Figure 2 Additionally or alternatively, Fig.12 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or codes stored in a non-transitory computer-readable medium and may be executed by a controller or processor to perform the function or operation of the component.

[0194] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1206. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to one or more other components of the device 1200. In some aspects, the receiving component 1202 may include combining Figure 2 The base station 110 is depicted as having one or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof.

[0195] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1206. In some aspects, the transmitting component 1204 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the depicted base station 110. In some aspects, the transmit component 1204 can be co-located with the receive component 1202 in a transceiver.

[0196] The registering component 1210 can establish a wireless communication session with a relay entity, wherein the relay entity is configured to perform an access node function and a UE function, and wherein establishing the wireless communication session includes enabling wireless communication for both the access node function and the UE function via a VPLMN. The receiving component 1202 can receive a communication associated with the access node function of the relay entity from the relay entity.

[0197] The sending component 1204 can send an indication to the relay entity whether the access node function is permitted to operate in the VPLMN. The receiving component 1202 can receive a request from the relay entity to operate on the radio resources of the HPLMN within the VPLMN. The sending component 1204 can send an indication to the relay entity whether the access node function is permitted to operate on the radio resources of the HPLMN within the VPLMN.

[0198] Transmitting component 1204 can transmit, to the relay entity, a configuration associated with a base station portion of the relay entity.

[0199] Fig.12 The number and arrangement of components shown are provided as examples. In practice, there may be Fig.12 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.12 Two or more components shown may be implemented in a single component, or Fig.12 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.12 The component set (one or more components) shown may be described as being executable by Fig.12 Another component shown may be a collection of components that perform one or more functions.

[0200] The following provides an overview of some aspects of the disclosure:

[0201] Aspect 1: A method for performing wireless communication by a relay entity, the method comprising: establishing a wireless communication session with a network entity associated with a VPLMN, wherein the relay entity is configured to perform an access node function and a UE function, and wherein establishing the wireless communication session comprises: enabling wireless communication for both the access node function and the UE function via the VPLMN; and performing relay services via the access node function.

[0202] Aspect 2: The method according to aspect 1 further comprises: determining whether the access node function is permitted to operate in the VPLMN.

[0203] Aspect 3: A method according to aspect 2, wherein whether to allow the access node function to operate in the VPLMN is determined at least in part based on at least one of the following: a preset list of preferred PLMNs or a preset list of PLMNs in which the access node function is not allowed to operate.

[0204] Aspect 4: The method according to aspect 3, wherein each of the preferred PLMNs comprises a corresponding priority value.

[0205] Aspect 5: The method according to aspect 4, further comprising: selecting the VPLMN based at least in part on a priority value associated with the VPLMN.

[0206] Aspect 6: The method according to any one of aspects 2 to 5, wherein determining whether to permit the access node function to operate in the VPLMN is based at least in part on an indication received from the network entity.

[0207] Aspect 7: The method according to aspect 6, wherein the indication received from the network entity is received in response to a request for the access node function to operate in the VPLMN, the request being associated with the UE function.

[0208] Aspect 8: A method according to any one of Aspects 6 to 7, wherein establishing the wireless communication session with the network entity associated with the VPLMN is at least partially based on another VPLMN's rejection of a request for the access node function to operate in another VPLMN, the request being associated with the UE function.

[0209] Aspect 9: The method according to any one of Aspects 1 to 8, wherein establishing the wireless communication session with the network entity associated with the VPLMN comprises: the access node function communicating with the HPLMN via a link between the UE function and the network entity.

[0210] Aspect 10: A method according to Aspect 9, wherein the relay entity determines whether to allow the access node function to operate on the radio resources of the HPLMN within the VPLMN based at least in part on at least one of: a preset list of preferred PLMNs or a preset list of PLMNs in which the access node function is not allowed to operate.

[0211] Aspect 11: The method according to aspect 10, wherein each of the preferred PLMNs comprises a corresponding priority value.

[0212] Aspect 12: The method according to aspect 11, further comprising: selecting the VPLMN based at least in part on a priority value associated with the VPLMN.

[0213] Aspect 13: The method according to any one of aspects 9 to 12, further comprising: sending a request to the network entity to operate radio resources of the HPLMN within the VPLMN.

[0214] Aspect 14: The method of aspect 13, wherein determining whether to allow the access node function to operate on the radio resources of the HPLMN within the VPLMN is based at least in part on an indication received from the network entity.

[0215] Aspect 15: The method according to aspect 14, wherein the indication received from the network entity is received in response to the request to operate radio resources of the HPLMN within the VPLMN.

[0216] Aspect 16: A method according to any one of Aspects 14 to 15, wherein establishing the wireless communication session with the network entity associated with the VPLMN is at least partly based on another VPLMN's rejection of a request for the access node function to operate on the radio resources of the HPLMN within the other VPLMN, the request being associated with the UE function.

[0217] Aspect 17: The method according to any one of aspects 1 to 16, wherein the access node function is associated with an IAB-DU.

[0218] Aspect 18: The method according to Aspect 17, wherein establishing the wireless communication session with the network entity associated with the VPLMN comprises: establishing a connection between the IAB-DU and the network entity.

[0219] Aspect 19: The method according to any one of aspects 17 to 18, wherein establishing the wireless communication session with the network entity associated with the VPLMN comprises: performing an IAB node integration procedure in the VPLMN associated with the IAB-DU.

[0220] Aspect 20: A method according to Aspect 19, wherein the execution of the IAB node integration procedure in the VPLMN is at least partially based on a preset list, and for each preferred PLMN in a plurality of preferred PLMNs, the preset list includes: a DNN and S-NSSAI pair associated with an OAM PDU session, and a FQDN associated with an OAM server.

[0221] Aspect 21: The method according to any one of aspects 17 to 18, wherein establishing the wireless communication session with the network entity associated with the VPLMN comprises: performing an inter-donor full migration procedure associated with the IAB-DU.

[0222] Aspect 22: The method according to any one of aspects 1 to 16, wherein the access node function is associated with a base station part of the relay entity.

[0223] Aspect 23: The method according to Aspect 22, wherein establishing the wireless communication session with the network entity associated with the VPLMN comprises: establishing a connection between the base station part of the relay entity and the AMF associated with the VPLMN.

[0224] Aspect 24: The method according to any one of Aspects 22 to 23, wherein establishing the wireless communication session with the network entity associated with the VPLMN comprises: performing a bootstrapping procedure in the VPLMN associated with the base station part of the relay entity.

[0225] Aspect 25: A method according to Aspect 24, wherein the bootstrapping procedure performed in the VPLMN is at least partially based on a preset list, and for each preferred PLMN in a plurality of preferred PLMNs, the preset list includes: a DNN and S-NSSAI pair associated with an OAM PDU session, an FQDN associated with an OAM server, and a DNN and S-NSSAI pair to be used to establish a backhaul link.

[0226] Aspect 26: The method of aspect 25, wherein performing the bootstrapping procedure in the VPLMN is based at least in part on the UE functionality establishing an OAM PDU session using a DNN and S-NSSAI associated with the VPLMN.

[0227] Aspect 27: The method according to aspect 26, the method further comprising: receiving a configuration associated with the base station part of the relay entity from an OAM server associated with the VPLMN.

[0228] Aspect 28: According to the method of Aspect 27, the method also includes: establishing an N2 interface between the base station part of the relay entity and the AMF associated with the VPLMN based at least in part on receiving the configuration associated with the base station part of the relay entity.

[0229] Aspect 29: The method according to any one of Aspects 22 to 23, wherein establishing the wireless communication session with the network entity associated with the VPLMN comprises: performing an inter-PLMN handover procedure associated with the base station portion of the relay entity.

[0230] Aspect 30: The method according to aspect 29, wherein performing the inter-PLMN handover procedure includes: handing over the UE PDU session from the HPLMN to the VPLMN.

[0231] Aspect 31: A method according to Aspect 30, wherein the execution of the inter-PLMN handover procedure is at least partially based on a preset list, and for each preferred PLMN in a plurality of preferred PLMNs, the preset list includes: a DNN and S-NSSAI pair associated with an OAM PDU session, an FQDN associated with an OAM server, and a DNN and S-NSSAI pair to be used to establish a backhaul link.

[0232] Aspect 32: The method of aspect 31, wherein performing the inter-PLMN handover procedure is based at least in part on the UE functionality establishing an OAM PDU session using the DNN and S-NSSAI associated with the VPLMN.

[0233] Aspect 33: The method according to aspect 32, the method further comprising: receiving a configuration associated with the base station part of the relay entity from an OAM server associated with the VPLMN.

[0234] Aspect 34: The method according to aspect 33, the method further comprising: establishing a PDU session for backhaul in the VPLMN based at least in part on the preset list.

[0235] Aspect 35: According to the method of Aspect 34, the method also includes: establishing an N2 interface between the base station part of the relay entity and the AMF associated with the VPLMN based at least in part on receiving the configuration associated with the base station part of the relay entity.

[0236] Aspect 36: The method according to aspect 35, further comprising: handing over, by the relay entity, a UE connected to the relay entity from the HPLMN to the VPLMN.

[0237] Aspect 37: The method according to aspect 36, the method further comprising: ending the wireless communication session with the HPLMN based at least in part on handing over the UE connected to the relay entity from the HPLMN to the VPLMN.

[0238] Aspect 38: A method for performing wireless communications by a network entity associated with a VPLMN, the method comprising: establishing a wireless communication session with a relay entity, wherein the relay entity is configured to perform an access node function and a UE function, and wherein establishing the wireless communication session comprises: enabling wireless communications for both the access node function and the UE function via the VPLMN; and receiving communications associated with the access node function of the relay entity from the relay entity.

[0239] Aspect 39: The method according to aspect 38, the method further comprising: sending an indication to the relay entity as to whether the access node function is permitted to operate in the VPLMN.

[0240] Aspect 40: The method according to aspect 39, wherein the indication is sent in response to a request for the access node function to operate in the VPLMN, the request being associated with the UE function of the relay entity.

[0241] Aspect 41: A method according to any one of aspects 38 to 40, wherein establishing the wireless communication session with the relay entity comprises: the access node function communicating with the HPLMN via a link between the UE function and the network entity.

[0242] Aspect 42: The method according to aspect 41, further comprising: receiving a request from the relay entity to operate radio resources of the HPLMN within the VPLMN.

[0243] Aspect 43: The method according to any one of aspects 41 to 42, further comprising: sending an indication to the relay entity as to whether the access node function is permitted to operate on the radio resources of the HPLMN within the VPLMN.

[0244] Aspect 44: The method according to any one of aspects 38 to 43, wherein the access node function is associated with an IAB-DU.

[0245] Aspect 45: The method according to aspect 44, wherein establishing the wireless communication session with the relay entity includes: establishing a connection between the IAB-DU and the network entity.

[0246] Aspect 46: The method according to any one of aspects 44 to 45, wherein establishing the wireless communication session with the relay entity comprises: performing an IAB node integration procedure in the VPLMN associated with the IAB-DU.

[0247] Aspect 47: A method according to Aspect 46, wherein the execution of the IAB node integration procedure in the VPLMN is at least partially based on a preset list, and for each preferred PLMN in a plurality of preferred PLMNs, the preset list includes: a DNN and S-NSSAI pair associated with an OAM PDU session, and a FQDN associated with an OAM server.

[0248] Aspect 48: The method according to any one of aspects 44 to 45, wherein establishing the wireless communication session with the relay entity comprises: performing an inter-donor full migration procedure associated with the IAB-DU.

[0249] Aspect 49: A method according to any one of aspects 38 to 43, wherein the access node functionality is associated with a base station portion of the relay entity.

[0250] Aspect 50: The method according to aspect 49, wherein establishing the wireless communication session with the relay entity includes: establishing a connection between the base station part of the relay entity and an AMF associated with the VPLMN.

[0251] Aspect 51: The method according to any one of aspects 49 to 50, wherein establishing the wireless communication session with the relay entity comprises: performing a bootstrapping procedure in the VPLMN associated with the base station portion of the relay entity.

[0252] Aspect 52: A method according to Aspect 51, wherein the bootstrapping procedure performed in the VPLMN is at least partially based on a preset list, and for each preferred PLMN in a plurality of preferred PLMNs, the preset list includes: a DNN and S-NSSAI pair associated with an OAM PDU session, an FQDN associated with an OAM server, and a DNN and S-NSSAI pair to be used to establish a backhaul link.

[0253] Aspect 53: The method of aspect 52, wherein performing the bootstrapping procedure in the VPLMN is based at least in part on the UE functionality establishing an OAM PDU session using a DNN and S-NSSAI associated with the VPLMN.

[0254] Aspect 54: The method according to aspect 53, the method further comprising: sending a configuration associated with the base station part of the relay entity to the relay entity.

[0255] Aspect 55: According to the method of Aspect 54, the method also includes: establishing an N2 interface between the base station part of the relay entity and the AMF associated with the VPLMN based at least in part on sending the configuration associated with the base station part of the relay entity.

[0256] Aspect 56: The method according to any one of aspects 49 to 50, wherein establishing the wireless communication session with the relay entity includes: performing an inter-PLMN handover procedure associated with the base station portion of the relay entity.

[0257] Aspect 57: The method according to aspect 56, wherein performing the inter-PLMN handover procedure includes: handing over the UE PDU session from the HPLMN to the VPLMN.

[0258] Aspect 58: A method according to Aspect 57, wherein the execution of the inter-PLMN handover procedure is at least partially based on a preset list, and for each preferred PLMN in a plurality of preferred PLMNs, the preset list includes: a DNN and S-NSSAI pair associated with an OAM PDU session, an FQDN associated with an OAM server, and a DNN and S-NSSAI pair associated with a backhaul link.

[0259] Aspect 59: The method of aspect 58, wherein performing the inter-PLMN handover procedure is based at least in part on the UE functionality establishing an OAM PDU session using the DNN and S-NSSAI associated with the VPLMN.

[0260] Aspect 60: The method according to aspect 59, the method further comprising: sending a configuration associated with the base station part of the relay entity to the relay entity.

[0261] Aspect 61: The method according to aspect 60 further comprises: establishing a PDU session for backhaul in the VPLMN based at least in part on the preset list.

[0262] Aspect 62: According to the method of Aspect 61, the method also includes: establishing an N2 interface between the base station part of the relay entity and the AMF associated with the VPLMN based at least in part on sending the configuration associated with the base station part of the relay entity.

[0263] Aspect 63: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 37.

[0264] Aspect 64: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 37.

[0265] Aspect 65: An apparatus for wireless communication, the apparatus comprising: at least one means for performing the method according to one or more of aspects 1 to 37.

[0266] Aspect 66: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 37.

[0267] Aspect 67: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 1 to 37.

[0268] Aspect 68: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 38 to 62.

[0269] Aspect 69: A device for wireless communication, the device comprising: a memory; and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 38 to 62.

[0270] Aspect 70: An apparatus for wireless communication, the apparatus comprising: at least one means for performing the method according to one or more of aspects 38 to 62.

[0271] Aspect 71: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 38 to 62.

[0272] Aspect 72: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 38 to 62.

[0273] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the various aspects.

[0274] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0275] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0276] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the item list refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (for example, a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other sorting of a, b and c).

[0277] Any element, action or instruction used herein should not be interpreted as key or necessary unless clearly stated. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If you only want to refer to an item, the phrase "only one" or similar terms will be used. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "at least partially based on", unless explicitly stated otherwise. In addition, as used herein, the term "or" is intended to be open when used in a series, and can be used interchangeably with "and / or", unless otherwise explicitly stated (for example, if used in combination with "any" or "only one").

Claims

1. An apparatus for wireless communication at a relay entity, the apparatus comprising: Memory; and one or more processors coupled to the memory and configured to: establishing a wireless communication session with a network entity associated with a visited public land mobile network (VPLMN), wherein the relay entity is configured to perform an access node function and a user equipment (UE) function, and wherein establishing the wireless communication session comprises: enabling wireless communication for both the access node function and the UE function via the VPLMN; as well as Relay services are performed via the access node functionality.

2. The apparatus of claim 1, wherein the one or more processors are further configured to determine whether the access node function is permitted to operate in the VPLMN.

3. The apparatus of claim 2, wherein the one or more processors are further configured to determine whether the access node function is permitted to operate in the VPLMN based at least in part on at least one of: a preset list of preferred public land mobile networks (PLMNs) or a preset list of PLMNs in which the access node function is not permitted to operate.

4. The apparatus of claim 3, wherein each of the preferred PLMNs comprises a corresponding priority value.

5. The apparatus of claim 4, wherein the one or more processors are further configured to select the VPLMN based at least in part on a priority value associated with the VPLMN.

6. The apparatus of claim 2, wherein determining whether to permit the access node function to operate in the VPLMN is based at least in part on an indication received from the network entity.

7. The apparatus of claim 6, wherein the indication received from the network entity is received in response to a request for the access node function to operate in the VPLMN, the request being associated with the UE function.

8. The apparatus of claim 6, wherein establishing the wireless communication session with the network entity associated with the VPLMN is based at least in part on another VPLMN rejecting a request for the access node function to operate in another VPLMN, the request being associated with the UE function.

9. The apparatus of claim 1, wherein the access node function is associated with an integrated access and backhaul (IAB) distributed unit (IAB-DU).

10. The apparatus of claim 9, wherein the one or more processors are further configured to establish a connection between the IAB-DU and the network entity.

11. The apparatus of claim 9, wherein the one or more processors are further configured to perform an IAB node integration procedure in the VPLMN associated with the IAB-DU.

12. The apparatus of claim 11, wherein the one or more processors are further configured to: perform the IAB node integration procedure in the VPLMN based at least in part on a preset list, the preset list comprising, for each preferred public land mobile network (PLMN) in a plurality of preferred public land mobile networks (PLMNs): A Data Network Name (DNN) and Single Network Slice Selection Assistance Information (S-NSSAI) pair associated with an Operation and Maintenance (OAM) Packet Data Unit (PDU) session, and a Fully Qualified Domain Name (FQDN) associated with the OAM server.

13. The apparatus of claim 9, wherein the one or more processors are further configured to perform an inter-donor full migration procedure associated with the IAB-DU.

14. An apparatus for wireless communications at a network entity associated with a visited public land mobile network (VPLMN), the apparatus comprising: Memory; and one or more processors coupled to the memory and configured to: establishing a wireless communication session with a relay entity, wherein the relay entity is configured to perform an access node function and a user equipment (UE) function, and wherein establishing the wireless communication session includes enabling wireless communication for both the access node function and the UE function via the VPLMN; as well as Communications associated with the access node functionality of the relay entity are received from the relay entity.

15. The apparatus of claim 14, wherein the one or more processors are further configured to send an indication to the relay entity of whether the access node function is permitted to operate in the VPLMN.

16. The apparatus of claim 15, wherein the one or more processors are further configured to send the indication in response to a request for the access node function to operate in the VPLMN, the request being associated with the UE function of the relay entity.

17. The apparatus of claim 14, wherein the access node function is associated with an integrated access and backhaul (IAB) distributed unit (IAB-DU).

18. The apparatus of claim 17, wherein the one or more processors are further configured to establish a connection between the IAB-DU and the network entity.

19. The apparatus of claim 17, wherein the one or more processors are further configured to perform an IAB node integration procedure in the VPLMN associated with the IAB-DU.

20. The apparatus of claim 19, wherein the one or more processors are further configured to: perform the IAB node integration procedure in the VPLMN based at least in part on a preset list, the preset list comprising, for each preferred public land mobile network (PLMN) in a plurality of preferred public land mobile networks (PLMNs): A Data Network Name (DNN) and Single Network Slice Selection Assistance Information (S-NSSAI) pair associated with an Operation and Maintenance (OAM) Packet Data Unit (PDU) session, and a Fully Qualified Domain Name (FQDN) associated with the OAM server.

21. The apparatus of claim 17, wherein the one or more processors are further configured to perform an inter-donor full migration procedure associated with the IAB-DU.

22. A method for performing wireless communication by a relay entity, the method comprising: establishing a wireless communication session with a network entity associated with a visited public land mobile network (VPLMN), wherein the relay entity is configured to perform an access node function and a user equipment (UE) function, and wherein establishing the wireless communication session comprises: enabling wireless communication for both the access node function and the UE function via the VPLMN; and Relay services are performed via the access node functionality.

23. The method according to claim 22, further comprising: A determination is made as to whether the access node function is permitted to operate in the VPLMN.

24. The method of claim 23, wherein determining whether the access node function is permitted to operate in the VPLMN is based at least in part on at least one of: a preset list of preferred public land mobile networks (PLMNs) or a preset list of PLMNs in which the access node function is not permitted to operate.

25. The method of claim 23, wherein determining whether to permit the access node function to operate in the VPLMN is based at least in part on an indication received from the network entity.

26. The method of claim 22, wherein the access node function is associated with an integrated access and backhaul (IAB) distributed unit (IAB-DU).

27. The method of claim 26, wherein establishing the wireless communication session with the network entity associated with the VPLMN comprises: A connection is established between the IAB-DU and the network entity.

28. A method of performing wireless communications by a network entity associated with a Visited Public Land Mobile Network (VPLMN), the method comprising: establishing a wireless communication session with a relay entity, wherein the relay entity is configured to perform an access node function and a user equipment (UE) function, and wherein establishing the wireless communication session includes enabling wireless communication for both the access node function and the UE function via the VPLMN; as well as Communications associated with the access node functionality of the relay entity are received from the relay entity.

29. The method of claim 28, wherein the access node function is associated with an integrated access and backhaul (IAB) distributed unit (IAB-DU).

30. The method of claim 29, wherein establishing the wireless communication session with the relay entity comprises: A connection is established between the IAB-DU and the network entity.