Network node migration and tracking area management

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a source node may forward a first message between a user equipment (UE) and a core node via a distributed node, where the first message is a non-access stratum message. The source node may send to a target node a second message associated with a migration of the distributed node from the source node to the target node, where the second message identifies the forwarding of the first message. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 366,301, filed on June 13, 2022, entitled “NETWORK NODE MIGRATION AND TRACKING AREA MANAGEMENT” and U.S. Non-Provisional Patent Application No. 18 / 329,209, filed on June 5, 2023, entitled “NETWORK NODEMIGRATION AND TRACKING AREA MANAGEMENT” and assigned to the assignee of this application. The disclosures of these prior applications are considered part of and incorporated by reference into this patent application. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for network node and tracking area management. Background Art

[0004] 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).

[0005] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, among other examples).

[0006] 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

[0007] Some aspects described herein relate to a method of wireless communication performed by a source node. The method may include forwarding a first message between a user equipment (UE) and a core node via a distributed node, wherein the first message is a non-access stratum message. The method may include sending a second message associated with a migration of the distributed node from the source node to the target node to a target node, wherein the second message identifies the forwarding of the first message.

[0008] Some aspects described herein relate to a method of wireless communication performed by a target node. The method may include receiving, from a source node, a request to establish a connection with a distributed node connected to the source node. The method may include receiving, from the source node and based at least in part on receiving the request, a second message associated with migration of the distributed node from the source node to the target node, wherein the second message identifies forwarding of a first message between a core node and a UE via the distributed node, wherein the first message is a non-access stratum message.

[0009] Some aspects described herein relate to a method of wireless communication performed by a core node. The method may include receiving an indication of support for a tracking area from a target node, wherein the tracking area is included in a registration area configured for a UE associated with a source node. The method may include sending a request for the target node to page the UE using the tracking area.

[0010] Some aspects described herein relate to a source node for wireless communication. The source node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to forward a first message between a UE and a core node via a distributed node, wherein the first message is a non-access stratum message. The one or more processors may be configured to send a second message associated with the migration of the distributed node from the source node to the target node to a target node, wherein the second message identifies the forwarding of the first message.

[0011] Some aspects described herein relate to a target node for wireless communication. The target node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a request from a source node to establish a connection with a distributed node connected to the source node. The one or more processors may be configured to receive, from the source node and at least partially based on receiving the request, a second message associated with the migration of the distributed node from the source node to the target node, wherein the second message identifies a first message forwarded between a core node and a UE via the distributed node, wherein the first message is a non-access layer message.

[0012] Some aspects described herein relate to a core node for wireless communication. The core node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive an indication of support for a tracking area from a target node, wherein the tracking area is included in a registration area configured for a UE associated with a source node. The one or more processors may be configured to send a request for the target node to page the UE using the tracking area.

[0013] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a source node. When executed by one or more processors of the source node, the instruction set may cause the source node to forward a first message between a UE and a core node via a distributed node, wherein the first message is a non-access stratum message. When executed by one or more processors of the source node, the instruction set may cause the source node to send a second message associated with a migration of the distributed node from the source node to the target node to a target node, wherein the second message identifies the forwarding of the first message.

[0014] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a target node. When executed by one or more processors of the target node, the instruction set may cause the target node to receive a request from a source node to establish a connection with a distributed node connected to the source node. When executed by one or more processors of the target node, the instruction set may cause the target node to receive a second message associated with migration of the distributed node from the source node to the target node from the source node and at least partially based on receiving the request, wherein the second message identifies forwarding a first message between a core node and a UE via the distributed node, wherein the first message is a non-access layer message.

[0015] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a core node. When executed by one or more processors of the core node, the instruction set may cause the core node to receive an indication of support for a tracking area from a target node, wherein the tracking area is included in a registration area configured for a UE associated with a source node. When executed by one or more processors of the core node, the instruction set may cause the core node to send a request for the target node to page the UE using the tracking area.

[0016] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for forwarding a first message between a UE and a core node via a distributed node, wherein the first message is a non-access stratum message. The apparatus may include means for sending a second message associated with migration of the distributed node from the apparatus to the target node to a target node, wherein the second message identifies the forwarding of the first message.

[0017] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, from a source node, a request to establish a connection with a distributed node connected to the source node. The apparatus may include means for receiving, from the source node and based at least in part on receiving the request, a second message associated with migration of the distributed node from the source node to the apparatus, wherein the second message identifies forwarding of a first message between a core node and a UE via the distributed node, wherein the first message is a non-access stratum message.

[0018] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving an indication of support for a tracking area from a target node, wherein the tracking area is included in a registration area configured for a UE associated with a source node. The apparatus may include means for sending a request for the target node to page the UE using the tracking area.

[0019] The various aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, 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.

[0020] The features and technical advantages of examples according to the present disclosure have been outlined quite broadly 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.

[0021] 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 (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers) for analog and digital purposes. 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

[0022] 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.

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

[0024] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0025] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

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

[0027] Figure 5 is a diagram illustrating an example of an integrated access and backhaul (IAB) network architecture according to the present disclosure.

[0028] FIG. 6A to FIG. 6C is a diagram illustrating an example of mobility in an IAB deployment according to the present disclosure.

[0029] 7A to 7C is a diagram illustrating an example associated with network node migration and tracking area management according to the present disclosure.

[0030] Figure 8 is a diagram illustrating an example process performed, for example, by a source node according to the present disclosure.

[0031] Fig. 9 is a diagram illustrating an example process performed, for example, by a target node according to the present disclosure.

[0032] Fig.10 is a diagram illustrating an example process performed, for example, by a core node according to the present disclosure.

[0033] Fig.11 is a diagram of an example apparatus for wireless communications according to the present disclosure. DETAILED DESCRIPTION

[0034] In an integrated access and backhaul (IAB) network architecture, an IAB distributed unit (DU) (IAB-DU) camped by a user equipment (UE) may be migrated from a first central processing unit (CU) to a second CU. In a partial migration scenario, F1 interface traffic is routed via a topology including the first CU. In a full migration scenario, F1 traffic is routed via a topology including the second CU. When a channel of a first cell is deactivated and powered down as part of the migration, the UE camped on the first cell and other idle UEs reselect to the second cell.

[0035] When the first cell and the second cell are associated with different tracking areas (TAs), and if the different tracking areas are not configured as part of the registration area of ​​the reselected idle UE, the reselected idle UE is caused to attempt to perform a mobility registration update. Since the reselected idle UE is performing reselection and mobility registration update concurrently, the amount of signaling (e.g., random access channel (RACH) signaling, radio resource control (RRC) signaling, or non-access stratum (NAS) signaling) may be excessive for the network. This problem may be particularly severe in mobility deployments where a DU and a group of UEs are deployed on a moving vehicle, resulting in relatively frequent migration of the DU between different CUs.

[0036] Mobile tracking areas may be implemented to reduce the likelihood of excessive signaling caused by DU migration. In a mobile tracking area scenario, DUs associated with different topologies may have the same tracking area. Therefore, and as described in detail below, the UE does not need to perform a mobility registration update, thereby preventing the generation of excessive signaling. When paging is to be performed, a revised tracking area list may be used to determine that the UE's registration area includes a mobile tracking area, so that the paging request can be directed to the UE. However, in some scenarios, as described in detail below, the revised supported tracking area list including the UE's mobile tracking area is updated so that the mobile tracking area list does not include the UE's mobile tracking area. For example, when a DU migrates between different CUs associated with different access and mobility functions (AMFs), the use of mobile tracking areas may result in any CU being unable to successfully page the UE associated with the DU. In this case, when paging is to be performed, the paging cannot be directed to the UE and the paging may fail.

[0037] Some aspects described herein provide network node migration and tracking area management. For example, a source node (e.g., IAB-donor 1) provides an AMF identifier to a target node (e.g., IAB-donor 2) of an AMF, for which the source node is able to communicate (e.g., paging) with one or more UEs. In this case, the target node can update the identified AMF (e.g., which may include an AMF that does not serve the target node or an AMF that has not been selected by the target node for update) with the mobile tracking area of ​​the one or more UEs. In this way, when the one or more UEs register with one or more AMFs via a node different from the target node, the one or more AMFs can direct paging to the one or more UEs via the target node. In this way, mobile tracking area functionality is utilized, thereby reducing network signaling relative to DU migration without mobile tracking area functionality. In addition, relative to other technologies for DU migration with mobile tracking area functionality, the possibility of paging and / or other signaling drops associated with the utilization of mobile tracking area functionality is reduced.

[0038] 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 present disclosure disclosed herein, whether it is implemented independently or in combination with any other aspect of the present 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 a device or method that is practiced 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.

[0039] 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 can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0040] 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 applied to other RATs, such as 3G RAT, 4G RAT and / or post-5G (e.g., 6G) RAT.

[0041] Figure 1 1 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 elements of a 4G (e.g., Long Term Evolution (LTE)) network, as well as other examples. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), one UE 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0042] In some examples, the network node 110 is or includes a network node (such as an RU) that communicates with the UE 120 via a radio access link. In some examples, the network node 110 is or includes a network node (such as a DU) that communicates with other network nodes 110 via a fronthaul link or a midhaul link. In some examples, the network node 110 is or includes a network node (such as a CU) that communicates with other network nodes 110 via a midhaul link or communicates with the core network via a backhaul link. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. For example, the network node 110 may include 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, a transmit receive point (TRP), a DU, a RU, a CU, a mobility element of a network, a core network node, a network element, a network equipment, a RAN node, or a combination thereof. In some examples, network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in wireless network 100 via various types of fronthaul, midhaul, and / or backhaul interfaces, such as direct physical connections, air interfaces, or virtual networks, using any suitable transport network.

[0043] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​the network node 110 and / or the network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 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 a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a 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 a UE 120 associated with a femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1In the example shown in , network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0044] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions, but not another base station function. In this way, a single device may include more than one base station.

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

[0046] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 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 network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0047] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless backhaul link or a wired backhaul link. In some aspects, the network controller 130 may be or may include a CU or a core network device.

[0048] UE 120 can be distributed throughout the wireless network 100, and each UE 120 can be stationary or mobile. UE 120 can include, for example, an access terminal, a terminal, a mobile station and / or a subscriber unit. UE 120 can 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, a UE function of a network node and / or any other suitable device configured to communicate via a wireless or wired medium.

[0049] Some UE 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UE. MTC UE and / or eMTC UE may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor and / or a location tag, which may communicate with a network node, another device (e.g., a remote device) or some other entity. Some UE 120 may be considered as an Internet of Things (IoT) device and / or may be implemented as a NB-IoT (narrowband IoT) device. Some UE 120 may be considered as customer premises equipment. UE 120 may be included in 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 operationally coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0050] 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, an air interface, etc. Frequency may be referred to as a carrier, a 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.

[0051] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more side link channels (e.g., without using network node 110 as an intermediary to communicate with each other). 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 network node 110.

[0052] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which 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).

[0053] 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 the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 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.

[0054] In view of the above examples, unless otherwise explicitly stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term can be broadly referred to as a frequency that can be lower than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise explicitly stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term can be broadly referred to as a frequency that can include mid-band frequencies, can be within FR2, FR4, FR4-a or FR4-1 and / or FR5, or can 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) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0055] In some aspects, a source node (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may forward a first message between a UE and a core node via a distributed node, wherein the first message is a non-access stratum message; and send a second message associated with a migration of the distributed node from the source node to the target node to a target node, wherein the second message identifies the forwarding of the first message. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0056] In some aspects, the target node (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive a request from a source node to establish a connection with a distributed node connected to the source node; and receive, from the source node and based at least in part on receiving the request, a second message associated with migration of the distributed node from the source node to the target node, wherein the second message identifies forwarding a first message between a core node and a UE via the distributed node, wherein the first message is a non-access stratum message. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0057] In some aspects, a core node (e.g., network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive an indication of support for a tracking area from a target node, wherein the tracking area is included in a registration area configured for a UE associated with the source node; and send a request for the target node to page the UE using the tracking area. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0058] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0059] Figure 22 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 232. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0060] At the network node 110, a transmit processor 220 may receive data intended for a UE 120 (or a set of UEs 120) from a 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 (CQIs) received from the UE 120. The network node 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 partitioning 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 modems) (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 further process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream using a corresponding modulator component to obtain a downlink signal. The modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) (shown as antennas 234a through 234t).

[0061] At the UE 120, a set of antennas 252 (shown as antennas 252a to 252r) may receive downlink signals from the network node 110 and / or other network nodes 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.

[0062] 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 network node 110 via the communication unit 294.

[0063] 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 (within a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or 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.

[0064] 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 sent to the network node 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, with reference to FIG. 7A to FIG. 11 ) or any aspects of any of the methods described herein.

[0065] At the network node 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 network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 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 network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of an antenna 234, a modem 232, a MIMO detector 236, a receive processor 238, a transmit processor 220, and / or a TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any method described herein (e.g., reference 2 FIG. 7A to FIG. 11 ).

[0066] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component in the network node 110 may perform one or more techniques associated with network node migration and tracking area management, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the Figure 8 The process of 800 Fig. 9 The process of 900 Fig.10 1000 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 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, one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of network node 110 and / or UE 120, may cause the one or more processors, UE 120, and / or network node 110 to perform or direct, for example Figure 8 The process of 800 Fig. 9 The process of 900 Fig.10 The process 1000 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0067] In some aspects, the source node (e.g., network node 110) includes a component for forwarding a first message between a UE and a core node via a distributed node, wherein the first message is a non-access layer message; and / or a component for sending a second message associated with a migration of the distributed node from the source node to the target node to a target node, wherein the second message identifies the forwarding of the first message. In some aspects, the component for the source node to perform the operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0068] In some aspects, the target node (e.g., network node 110) includes a component for receiving a request from a source node to establish a connection with a distributed node connected to the source node; and / or a component for receiving, from the source node and at least in part based on receiving the request, a second message associated with the migration of the distributed node from the source node to the target node, wherein the second message identifies the forwarding of a first message between the core node and the UE via the distributed node, wherein the first message is a non-access stratum message. In some aspects, the component for the target node to perform the operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0069] In some aspects, a core node (e.g., network node 110) includes means for receiving an indication of support for a tracking area from a target node, wherein the tracking area is included in a registration area configured for a UE associated with the source node; and / or means for sending a request for the target node to page the UE using the tracking area. In some aspects, means for the core node to perform operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0070] Although Figure 2 The blocks in the 200 and 210 are illustrated as distinct components, but the functionality described above with respect to these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to 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.

[0071] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0072] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node or a core node, a source node, a target node, a network element, a base station or a network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a Node B (NB), an evolved NB (eNB), an NR base station, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) performing base station functionality can be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. A "network entity" or a "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0073] An aggregated base station (e.g., an aggregated network node) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) can be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU can be implemented within a network node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed across one or more other network nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0074] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0075] Figure 33 is a diagram illustrating an example decomposed base station architecture 300 according to the present disclosure. The decomposed base station architecture 300 may include a CU 310, which may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed control units (such as a near RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via corresponding midhaul links, such as through an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via corresponding fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via corresponding radio frequency (RF) access links. In some specific implementations, the CU 310, DU 330, or RU 340 may correspond to a network node described herein. For example, in a mobility scenario, the DU 330 or RU 340 may be a source node or a target node. In some implementations, a UE 120 can be served simultaneously by multiple RUs 340. In some implementations, a core network 320 can include one or more core nodes (CNs) 322. For example, a core network 320 can include an access and mobility management function (AMF) implemented by one or more CNs 322.

[0076] Each of the units (including CU 310, DU 330, RU 340) and near-RT RIC 325, non-RT RIC 315, SMO framework 305, and CN 322 may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of these units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium, and the wireless interface being configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium, or both.

[0077] In some aspects, CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 310. CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, CU 310 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface such as an E1 interface. As needed, CU 310 may be implemented to communicate with DU 330 for network control and signaling.

[0078] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers, at least in part according to a functional split (such as a functional split defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0079] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions based on functional splits (e.g., functional splits defined by 3GPP) such as lower layer functional splits, or low PHY layer functions such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control plane communications and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture such as a vRAN architecture.

[0080] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RT RIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0081] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or in communication with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

[0082] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0083] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0084] Figure 4 is a diagram illustrating an example 400 of a radio access network according to the present disclosure.

[0085] As shown by reference numeral 405, a conventional (e.g., 3G, 4G, or LTE) radio access network may include a plurality of base stations 410 (e.g., access nodes (ANs)), each of which communicates with a core network via a wired backhaul link 415 (such as a fiber optic connection). In some implementations, the base stations 410 may have a decomposed base station architecture and may correspond to one or more of the CU 310, DU 330, or RU 340. The base stations 410 may communicate with the UE 420 via an access link 425 (which may be a wireless link). In some aspects, Figure 4 The base station 410 shown may be Figure 1 The network node 110 or one or more components thereof shown. In some aspects, Figure 4 The UE 420 shown may be Figure 1 UE 120 is shown.

[0086] As shown by reference numeral 430, the RAN may include a wireless backhaul network, sometimes referred to as an IAB network. In the IAB network, at least one base station is an anchor base station 435, which communicates with the core network via a wired backhaul link 440 (such as a fiber connection). The core network may include a core node that implements one or more core network functionalities (such as AMF functionality). The anchor base station 435 may also be referred to as an IAB donor (or IAB-donor). The IAB network may include one or more non-anchor base stations 445, sometimes referred to as relay base stations or IAB nodes (or IAB-nodes). The non-anchor base station 445 may communicate directly or indirectly with the anchor base station 435 via one or more backhaul links 450 (for example, via one or more non-anchor base stations 445) to form a backhaul path to the core network for carrying backhaul traffic. The backhaul link 450 may be a wireless link. The anchor base station 435 and / or the non-anchor base station 445 may communicate with one or more UEs 455 via an access link 460 (which may be a wireless link for carrying access traffic). In some aspects, Figure 4 The anchor base station 435 and / or the non-anchor base station 445 shown may be Figure 1 The base station 110 is shown. In some aspects, Figure 4 The UE 455 shown may be Figure 1 UE 120 is shown.

[0087] As shown by reference numeral 465, in some aspects, a RAN including an IAB network may use millimeter wave (mmWave) 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 470 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 475 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.

[0088] Figure 4 The configuration of the base station and UE in is shown as an example, and other examples are also contemplated. For example, Figure 4 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).

[0089] As indicated above, Figure 4 are provided as examples. Other examples can be found in the Figure 4 The examples described are different.

[0090] Figure 5 is a diagram illustrating an example 500 of an IAB network architecture according to the present disclosure.

[0091] like Figure 5 As shown, the IAB network may include an IAB donor 505 (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 505 may terminate at the core network. Additionally or alternatively, the IAB donor 505 may be connected to one or more devices of the core network that provide core access and mobility management functions (e.g., AMF). In some aspects, the IAB donor 505 may include a network node 110, such as an anchor base station, as described above in conjunction with Figure 4 As described. As shown in the figure, the IAB donor 505 may include a CU, and the CU may perform access node controller (ANC) functions and / or AMF functions. The CU may configure the DU of the IAB donor 505 and / or may configure one or more IAB nodes 510 (e.g., a mobile terminal (MT) and / or a DU of the IAB node 510) connected to the core network via the IAB donor 505. Therefore, the CU of the IAB donor 505 may control and / or configure the entire IAB network connected to the core network via the IAB donor 505, such as by using control messages and / or configuration messages (e.g., RRC configuration messages or F1 application protocol (F1-AP) messages).

[0092] like Figure 5As further shown, the IAB network may include IAB nodes 510 (shown as IAB-node 1, IAB-node 2, and IAB-node 3), which are connected to the core network via an IAB donor 505. As shown, the IAB node 510 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 510 (e.g., a child node) may be controlled and / or scheduled by another IAB node 510 (e.g., a parent node of the child node) and / or by an IAB donor 505. The DU function of an IAB node 510 (e.g., a parent node) may control and / or schedule other IAB nodes 510 (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 505 may include a DU function but not an MT function. That is, the IAB donor 505 may configure, control and / or schedule the communication of the IAB node 510 and / or the UE 120. The UE 120 may include only the MT function, but not the DU function. That is, the communication of the UE 120 may be controlled and / or scheduled by the IAB donor 505 and / or the IAB node 510 (e.g., the parent node of the UE 120).

[0093] When a first node controls and / or schedules the communication of 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. Therefore, the DU function of the parent node may control and / or schedule the communication of the child node for the parent node. The parent node may be an IAB donor 505 or an IAB node 510, and the child node may be an IAB node 510 or a UE 120. The communication of the MT function of the child node may be controlled and / or scheduled by the parent node of the child node.

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

[0095] like Figure 5As further shown, the link between the IAB donor 505 and the IAB node 510 or between two IAB nodes 510 may be referred to as a backhaul link 520. The backhaul link 520 may be a wireless backhaul link that provides radio access to the core network to the IAB node 510 via the IAB donor 505 and optionally via one or more other IAB nodes 510. 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 515 and the backhaul link 520. In some aspects, the backhaul link 520 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 525 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 505 or an IAB node 510 .

[0096] As indicated above, Figure 5 are provided as examples. Other examples can be found in the Figure 5 The examples described are different.

[0097] FIG. 6A to FIG. 6C is a diagram illustrating an example 600 of mobility in an IAB deployment according to the present disclosure.

[0098] like Fig. 6AAs shown, the IAB-DU (IAB-DU1) occupied by the UE can be migrated from the first CU (IAB-donor-CU1) to the second CU (IAB-donor-CU2). In partial migration, IAB-DU1 (and the IAB-MT associated with it) migrates from the connection to IAB-donor-CU1 to IAB-donor-CU2. In this case, the endpoint of the F1 connection is at IAB-donor-CU1, but the F1 traffic between IAB-DU1 and IAB-donor-CU1 is routed via IAB-donor-CU2 via the topology of IAB-donor-DU2. In full migration, the IAB-MT deactivates the first cell associated with IAB-donor-CU1 (e.g., the cell of IAB-DU1) and activates the second cell associated with IAB-donor-CU2 (e.g., the cell of IAB-DU2), instead of maintaining communication with IAB-donor-CU1. A new F1 connection is established to the IAB-donor-CU2, which instantiates the logical IAB-DU2 on the IAB node (which includes the IAB-MT). The cell associated with the IAB-donor-CU2 may be activated on the air interface. The previous F1 connection with the IAB-donor-CU1 may be maintained or released, and the cell associated with the IAB-donor-CU1 (and IAB-donor-DU1) may be deactivated. In this case, when the channels of the first cell are deactivated and powered down, the UEs camped on the first cell and other idle UEs reselect to the second cell.

[0099] When the first cell (of IAB-DU1) and the second cell (of IAB-DU2) are associated with different tracking areas (TAs), and if the different tracking areas are not configured as part of the registration area of ​​the reselected idle UE, the reselected idle UE is caused to attempt to perform a mobility registration update. Since the reselected idle UE is performing reselection and mobility registration update concurrently, the amount of signaling (e.g., random access channel (RACH) signaling, RRC signaling, or non-access stratum (NAS) signaling) may be excessive for the network. This problem may be particularly severe in mobility deployments where one DU and a group of UEs are deployed on a moving vehicle, resulting in relatively frequent migration of the DUs between different CUs.

[0100] Figure 6B The following illustrates a mobile tracking area scenario that can be implemented to reduce the possibility of excessive signaling caused by DU migration. Figure 6BAs shown, the UE can camp on IAB-DU1 and register with AMF (AMF-UE 1). AMF-UE 1 configures the tracking area of ​​the IAB-DU1 cell for the registration area of ​​the UE. When the IAB node (which includes IAB-DU1) performs a full migration, the new IAB-DU2 cell broadcasts the same tracking area as the IAB-DU1 cell. In other words, the IAB-DU2 cell is associated with the tracking area that is part of the registration area of ​​the UE. Therefore, the UE does not need to perform mobility registration updates, thereby preventing the generation of excessive signaling. In addition, the IAB-donor 2 to which the IAB-DU2 is connected updates the AMF-UE 1 with a revised supported tracking area list that includes the mobile tracking area of ​​the UE, and the IAB-donor 1 to which the IAB-DU1 may no longer be connected updates the AMF-UE 1 with a revised supported TA list that excludes the mobile tracking area of ​​the UE. The IAB-Donor 2 may indicate that the mobile tracking area is a tracking area associated with a mobile IAB-Node, or may provide an indication of the mobile tracking area (as a tracking area supported by the NG-RAN) without indicating that the tracking area is associated with a mobile IAB-Node. In this case, when paging, the AMF-UE1 uses the modified tracking area list to determine that the UE's registration area includes a mobile tracking area, which is being supported by the IAB-Donor 2. Therefore, the AMF-UE 1 requests the IAB-Donor 2 to page the UE via the cell of the IAB-DU2 or via the mobile tracking area.

[0101] However, if Figure 6C As shown, in some scenarios, the IAB-node (which includes IAB-DU1) migrates from IAB-donor 1 associated with AMF-UE1 to IAB-donor 2 associated with another AMF (AMF-UE 2), and IAB-DU2 is instantiated by establishing an F1 connection to IAB-donor 2. In this case, IAB-donor 2 updates AMF-UE 2 with a revised list of supported tracking areas that includes the mobile tracking area of ​​the UE (and IAB-donor 1 updates AMF-UE 1 with a revised list of supported tracking areas that does not include the mobile tracking area of ​​the UE). However, in this case, when paging is performed, the mobile tracking area has been deleted from AMF-UE 1, but the UE has not yet registered at AMF-UE2. Therefore, neither AMF-UE 1 nor AMF-UE 2 can direct paging to the UE, and paging may fail.

[0102] As indicated above, FIG. 6A to FIG. 6C are provided as examples. Other examples can be found in the FIG. 6A to FIG. 6C The examples described are different.

[0103] As described above, the introduction of mobile tracking areas can reduce the possibility of excessive signaling when the DU migrates between different CUs. However, when the DU migrates between different CUs associated with different AMFs, the use of mobile tracking areas may cause any CU to fail to successfully page the UE associated with the DU. Some aspects described herein provide network node migration and tracking area management. For example, a source node (e.g., IAB-donor 1) provides an AMF identifier to a target node (e.g., IAB-donor 2) of an AMF, for which the source node is able to communicate (e.g., paging) with one or more UEs. In this case, the target node can update the identified AMF (e.g., which may include an AMF that does not serve the target node or an AMF that has not been selected by the target node for update) with the mobile tracking area of ​​the one or more UEs. In this way, when the one or more UEs register with one or more AMFs via a node different from the target node, the one or more AMFs can direct paging to the one or more UEs via the target node. In this way, mobile tracking area functionality is utilized, thereby reducing network signaling relative to DU migration without mobile tracking area functionality. Furthermore, relative to other techniques for DU migration with mobile tracking area functionality, the likelihood of paging and / or other signaling drops associated with utilization of mobile tracking area functionality is reduced.

[0104] 7A to 7C 700 / 700' / 700" is a diagram illustrating an example associated with network node migration and tracking area management according to the present disclosure. 7A to 7C As shown, example 700 includes a set of core nodes 702 , a source node 704 , a target node 706 , a DU 708 , and a set of UEs 120 .

[0105] like Fig. 7A As shown, in the first state, DU 708 can provide a set of cells for the group of UEs 120 via a connection with source node 704. In this case, the group of UEs 120 can be associated with mobile tracking areas registered with core node 702a and core node 702b. Fig. 7A As further shown in FIG. 7 , in the second state, the DU 708 may migrate from the source node 704 to the target node 706 while still providing paging for the UE 120 via the target node 706.

[0106] like Fig. 7A And as shown by reference numeral 752, the source node 704 can forward NAS messages between the UE 120 and the core node 702a (e.g., AMF) via the connection of the UE 120 to the DU 708. In some aspects, the source node 704 can redirect NAS signaling (e.g., between the core nodes 702).

[0107] like Fig. 7A And as shown by reference numeral 754, the source node 704 may release the connection of the UE 120 to the DU 708. Based at least in part on the release of the connection, the UE 120 may transition to an idle mode. For example, the UE 120 may transition to an RRC idle mode or an RRC inactive mode based at least in part on the release of the connection of the UE 120 to the DU 708 by the source node 704. In some aspects, the DU 708 may migrate the RRC connection from the source node 704 to the target node 706. For example, in order to complete the migration from the source node 704 to the target node 706, the IAB-node serving the DU 708 may communicate with the target node 706 to migrate the RRC connection to the target node 706. In some aspects, the aforementioned NAS message is forwarded before the migration of the RRC connection. For example, the source node 704 may forward the NAS message between the UE 120 and the core node 702a before the RRC connection is migrated to the target node 706. Alternatively, the source node 704 may forward the NAS message after the migration of the RRC connection. For example, the source node 704 may forward the NAS message after the IAB-node portion serving the DU 708 migrates to the target node 706.

[0108] like Fig. 7A And as shown by reference numeral 756, the source node 704 may send an indication of the occurrence of the NAS message forwarded between the UE 120 and the core node 702a to the target node 706 (e.g., via an Xn interface or an NG interface). For example, the source node 704 may send an indication including an identifier to the core node 702a to enable the target node 706 to communicate with the core node 702a, thereby establishing paging for the UE 120 via the target node 706. In this case, the indication may include a globally unique AMF ID (GUAMI) of the core node 702a. Additionally or alternatively, the source node 704 may provide information that identifies the IAB-node serving the DU 708 with the indication of the occurrence of the NAS message, identifies the handover request associated with the IAB-node serving the DU 708, or identifies the tracking area or cell identifier of the cell provided by the DU 708, etc.

[0109] In some aspects, the source node 704 may include information indicating whether the amount of time elapsed from the occurrence of the NAS message satisfies a threshold in the indication of the occurrence of the NAS message. For example, the source node 704 may indicate whether the amount of time corresponding to the timer for performing the periodic registration update of the UE 120 to the core node 702 has elapsed. The NAS message may be the last message between the UE 120 and the core node 702a, and the UE is disconnected from the mobile IAB node and moves to the idle mode. Additionally or alternatively, the source node 704 may provide information identifying the timestamp of the last registration update of the UE 120 to the core node 702, and the target node 706 may determine whether the amount of time corresponding to the timer for performing the periodic registration update of the UE 120 to the core node 702 has elapsed based on the information. In some aspects, the source node 704 may provide information identifying the occurrence of NAS signaling with multiple core nodes 702, such as NAS signaling forwarded between the core node 702a and the first UE 120 and NAS signaling forwarded between the core node 702b and the second UE 120.

[0110] In some aspects, the source node 704 may send information identifying an identifier of the core node 702 (e.g., GUAMI identifying the AMF) to the target node 706 (or another target node 706 described in more detail herein) based at least in part on the timing of the NAS signaling. For example, for a UE 120 connected to the core node 702, the source node 704 may send information identifying the core node 702 based at least in part on the NAS signaling, which occurs within a threshold time period in which the source node 704 is triggered to send information identifying the identifier of the core node 702.

[0111] In some aspects, the target node 706 may receive a request to establish a connection with the IAB-node serving the DU 708. For example, the target node 706 may receive a request to establish a connection from the source node 704. In this case, the request may be included in a message indicating that NAS signaling has occurred. Additionally or alternatively, the request may be included in a separate signaling. In some aspects, the request is a handover request for the RRC connection of the IAB-node serving the DU 708.

[0112] like Fig. 7AAnd as further shown by reference numeral 758, the target node 706 may send tracking area information to the core node 702. For example, the target node 706 may send an indication that the target node 706 supports a tracking area associated with a cell of the DU 708 (and the UE 120 connected thereto). In some aspects, the indication may not include information indicating an association with the cell of the DU 708. In some aspects, the target node 706 may send the tracking area information after establishing a connection with the IAB-node serving the DU 708. Additionally or alternatively, the target node 706 may send the tracking area information after establishing an F1-C interface connection with the IAB-node serving the DU 708 and receiving an indication of the tracking area or the served cell from the IAB-node serving the DU 708. For example, the target node 706 may receive an indication of the tracking area or the served cell from the DU 708, establish a connection to the core node 702 based at least in part on the indication, and may send the tracking area information to the core node 702 to establish the connection.

[0113] Figure 7B An example 700' of multiple migrations of DU 708 is shown. Figure 7B As shown, DU 708 can migrate from source node 704 to first target node 706-1, and from first target node 706-1 to second target node 706-2. In this case, as shown by reference numerals 760 and 762, first target node 706-1 can forward an indication of NAS signaling (e.g., received from source node 704) to second target node 706-2, so that an IAB-node serving DU 708 can migrate to second target node 706-2 and register UE 120 to receive paging from core node 702. In some aspects, first target node 706-1 can forward the indication of NAS signaling based at least in part on the timing of NAS signaling. For example, first target node 706-1 can forward the indication to second target node 706-2 based at least in part on NAS signaling occurring within a threshold time period in which first target node 706-1 is triggered to forward the indication. In some aspects, the first target node 706-1 may include (or forward) a timestamp associated with the NAS signaling to enable the second target node 706-2 to determine whether the NAS signaling occurred within a threshold time period. Based at least in part on receiving an indication of the occurrence of the NAS signaling, the second target node 706-2 may communicate with the core node 702 to enable paging of the UE 120 via the second target node 706-2 and the DU 708.

[0114] Figure 7CAn example 700 of paging a UE is shown. For example, as shown by reference numeral 770, the core node 702a can configure a registration area for the UE 120. In this case, the registration area can include a tracking area supported by the source node 704. In some aspects, the tracking area can be associated with the DU 708 or a cell served by the DU 708. In some aspects, after configuring the registration area for the UE 120, the core node 702a can release the NAS connection with the UE 120. In some aspects, the core node 702a can receive an indication from the source node 704 that the source node 704 no longer supports the tracking area (e.g., after the DU 708 migrates to the target node 706). As shown by reference numeral 772, the core node 702a can receive an indication that the target node 706 supports the tracking area. In this case, the core node 702a can store information indicating that the target node 706 supports the tracking area, and when the core node 702a is to page the UE 120, the core node 702a can request the UE 120 to be paged via the target node 706. 120 paging, as shown by reference number 774.

[0115] As indicated above, 7A to 7C are provided as examples. Other examples can be found in the 7A to 7C The examples described are different.

[0116] Figure 8 is a diagram illustrating an example process 800 performed, for example, by a source node in accordance with the present disclosure. The example process 800 is an example in which a source node (eg, source node 704) performs operations associated with network node migration and tracking area management.

[0117] like Figure 8 As shown, in some aspects, process 800 may include forwarding a first message between a UE and a core node via a distributed node, wherein the first message is a non-access layer message (block 810). For example, a source node (e.g., using Fig.11 The communication manager 150 and / or forwarding component 1108 depicted in the figure can forward the first message between the UE and the core node via the distributed node, wherein the first message is a non-access stratum message, as described above.

[0118] like Figure 8 As further shown, in some aspects, process 800 may include sending a second message associated with the migration of the distributed node from the source node to the target node to the target node, wherein the second message identifies a forwarding of the first message (block 820). Fig.11The communication manager 150 and / or the sending component 1104 depicted in FIG. 1 may send a second message associated with the migration of the distributed node from the source node to the target node to the target node, wherein the second message identifies a forwarding of the first message, as described above.

[0119] Process 800 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.

[0120] In a first aspect, process 800 includes releasing a connection between the UE and the distributed node in conjunction with sending a second message.

[0121] In a second aspect, alone or in combination with the first aspect, releasing the connection is associated with transitioning the UE to an idle state or an inactive state.

[0122] In a third aspect, alone or in combination with one or more of the first and second aspects, releasing the connection is associated with migrating the distributed node to the target node.

[0123] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the second message includes at least one of an identifier of the distributed node, an indication of a handover request associated with the distributed node, an indication of a tracking area of ​​a cell served by the distributed node, or an indication of a cell identifier of the cell served by the distributed node.

[0124] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the second message comprises at least one of an identifier of a core node, an indication of an amount of elapsed time since the first message, an indication of an amount of elapsed time since signaling associated with the core node, an indication of the occurrence of signaling associated with the core node or another core node, an indication of signaling associated with registration of the UE with the core node, or an indication of redirection of signaling associated with the core node to another node.

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

[0126] Fig. 9 is a diagram illustrating an example process 900 performed, for example, by a target node in accordance with the present disclosure. The example process 900 is an example in which a target node (eg, target node 706) performs operations associated with network node migration and tracking area management.

[0127] like Fig. 9 As shown, in some aspects, process 900 may include receiving a request from a source node to establish a connection with a distributed node connected to the source node (block 910). Fig.11 The communication manager 150 and / or receiving component 1102 depicted in FIG. 10A may receive a request from a source node to establish a connection with a distributed node connected to the source node, as described above.

[0128] like Fig. 9 As further shown, in some aspects, process 900 may include receiving, from the source node and based at least in part on receiving the request, a second message associated with migration of the distributed node from the source node to the target node, wherein the second message identifies forwarding of the first message between the core node and the UE via the distributed node, wherein the first message is a non-access stratum message (block 920). For example, the target node (e.g., using Fig.11 The communication manager 150 and / or receiving component 1102 depicted in the figure may receive, from the source node and at least in part based on receiving the request, a second message associated with the migration of the distributed node from the source node to the target node, wherein the second message identifies forwarding of the first message between the core node and the UE via the distributed node, wherein the first message is a non-access stratum message, as described above.

[0129] 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.

[0130] In a first aspect, process 900 includes sending a third message to a core node indicating support for a tracking area associated with a cell of a distributed node.

[0131] In a second aspect, alone or in combination with the first aspect, the request is a handover request.

[0132] In a third aspect, alone or in combination with one or more of the first and second aspects, the request and the second message are conveyed in a single control message.

[0133] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the second message includes at least one of an identifier of the distributed node, an indication of a handover request associated with the distributed node, an indication of a tracking area of ​​a cell served by the distributed node, or an indication of a cell identifier of the cell served by the distributed node.

[0134] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the second message comprises at least one of an identifier of a core node, an indication of an amount of elapsed time since the first message, an indication of an amount of elapsed time since signaling associated with the core node, an indication of the occurrence of signaling associated with the core node or another core node, an indication of signaling associated with registration of the UE with the core node, or an indication of redirection of signaling associated with the core node to another node.

[0135] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, process 900 includes forwarding the second message to another target node in conjunction with migration of the distributed node and the UE to the another target node.

[0136] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, forwarding the second message comprises forwarding the second message based at least in part on an amount of elapsed time since signaling with the core node occurred at the source node or the target node.

[0137] 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.

[0138] Fig.10 is a diagram illustrating an example process 1000 performed, for example, by a core node in accordance with the present disclosure. The example process 1000 is an example in which a core node (eg, core node 702) performs operations associated with network node migration and tracking area management.

[0139] like Fig.10 As shown, in some aspects, process 1000 may include receiving an indication of support for a tracking area from a target node, wherein the tracking area is included in a registration area configured for a UE associated with a source node (block 1010). For example, a core node (e.g., using Fig.11 The communication manager 150 and / or receiving component 1102 depicted in FIG. 1 may receive an indication of support for a tracking area from a target node, wherein the tracking area is included in a registration area configured for a UE associated with the source node, as described above.

[0140] like Fig.10 As further shown, in some aspects, process 1000 may include sending a request for a target node to page the UE using a tracking area (block 1020). Fig.11The communication manager 150 and / or the sending component 1104 depicted in FIG. 10A may send a request for the target node to page the UE using the tracking area, as described above.

[0141] 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.

[0142] In a first aspect, process 1000 includes configuring a registration area for a UE, wherein the registration area includes a tracking area associated with a source node.

[0143] In a second aspect, alone or in combination with the first aspect, process 1000 includes releasing a non-access stratum connection of the UE based on configuring a registration area for the UE.

[0144] In a third aspect, alone or in combination with one or more of the first and second aspects, process 1000 includes receiving another indication from a source node that the source node no longer supports tracking areas, and sending a request for the target node to page the UE includes sending a request for the target node to page the UE based at least in part on receiving the other indication from the source node that the source node no longer supports tracking areas.

[0145] In a fourth aspect, alone or in combination with one or more of the first to third aspects, a tracking area is associated with a distributed node providing communication services for the UE or a cell served by a distributed node providing communication services for the UE.

[0146] 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.

[0147] Fig.111 is a diagram of an example apparatus 1100 for wireless communication according to the present disclosure. The apparatus 1100 may be a network node, or a network node may include the apparatus 1100. For example, the apparatus 1100 may be a source node, a target node, a core node, a UE, a CU, a DU, a RU, or an IAB node, etc. In some aspects, the apparatus 1100 includes a receiving component 1102 and a sending component 1104 that can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a network node, a base station, or another wireless communication device) using the receiving component 1102 and the sending component 1104. As further shown in the figure, the apparatus 1100 may include a communication manager 150. The communication manager 150 may include one or more of a forwarding component 1108, a connection management component 1110, or a registration component 1112, etc.

[0148] In some aspects, the apparatus 1100 may be configured to perform 7A to 7C Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as Figure 8 The process of 800 Fig. 9 The process of 900 Fig.10 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 in the figure may be combined with Figure 2 Additionally or alternatively, one or more components in the set of components 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 code 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.

[0149] 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 2One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described network nodes.

[0150] 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 described network nodes. In some aspects, the transmit component 1104 can be co-located with the receive component 1102 in a transceiver.

[0151] The forwarding component 1108 may forward a first message between the UE and the core node via the distributed node, wherein the first message is a non-access layer message. The sending component 1104 may send a second message associated with the migration of the distributed node from the source node to the target node to the target node, wherein the second message identifies the forwarding of the first message. The connection management component 1110 may release the connection between the UE and the distributed node in conjunction with sending the second message.

[0152] The receiving component 1102 may receive a request from a source node to establish a connection with a distributed node connected to the source node. The receiving component 1102 may receive, from the source node and based at least in part on receiving the request, a second message associated with the migration of the distributed node from the source node to the target node, wherein the second message identifies the forwarding of the first message between the core node and the UE via the distributed node, wherein the first message is a non-access layer message. The sending component 1104 may send a third message to the core node indicating support for a tracking area associated with a cell of the distributed node. The forwarding component 1108 may forward the second message to the other target node in conjunction with the migration of the distributed node and the UE to the other target node.

[0153] Receiving component 1102 can receive an indication of support for a tracking area from a target node, wherein the tracking area is included in a registration area configured for a UE associated with a source node. Sending component 1104 can send a request for the target node to page the UE using the tracking area. Registering component 1112 can configure a registration area for the UE, wherein the registration area includes a tracking area associated with the source node. Connection management component 1110 can release a non-access stratum connection of the UE based on configuring the registration area for the UE. Receiving component 1102 can receive from the source node another indication that the source node no longer supports the tracking area.

[0154] Fig.11 The number and arrangement of components shown are provided as examples. 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 illustrated set of component(s) may be described as being executable by Fig.11 Another component shown as a collection performs one or more functions.

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

[0156] Aspect 1: A method of wireless communication performed by a source node, the method comprising: forwarding a first message between a user equipment (UE) and a core node via a distributed node, wherein the first message is a non-access layer message; and sending a second message associated with the migration of the distributed node from the source node to the target node to a target node, wherein the second message identifies the forwarding of the first message.

[0157] Aspect 2: According to the method described in Aspect 1, the method further includes: releasing the connection between the UE and the distributed node in combination with sending the second message.

[0158] Aspect 3: The method according to aspect 2, wherein releasing the connection is associated with transitioning the UE to an idle state or an inactive state.

[0159] Aspect 4: The method according to any one of aspects 2 to 3, wherein releasing the connection is associated with migrating the distributed node to the target node.

[0160] Aspect 5: A method according to any one of Aspects 1 to 4, wherein the second message includes at least one of the following: an identifier of the distributed node, an indication of a handover request associated with the distributed node, an indication of a tracking area of ​​a cell served by the distributed node, or an indication of a cell identifier of the cell served by the distributed node.

[0161] Aspect 6: A method according to any one of Aspects 1 to 5, wherein the second message includes at least one of the following: an identifier of the core node, an indication of the amount of elapsed time that has occurred since the first message, an indication of the amount of elapsed time that has occurred since signaling associated with the core node, an indication of the occurrence of signaling associated with the core node or another core node, an indication of signaling associated with the UE's registration with the core node, or an indication of redirection of signaling associated with the core node to another node.

[0162] Aspect 7: A method of wireless communication performed by a target node, the method comprising: receiving a request from a source node to establish a connection with a distributed node connected to the source node; and receiving, from the source node and at least partially based on receiving the request, a second message associated with the migration of the distributed node from the source node to the target node, wherein the second message identifies a first message forwarded between a core node and a user equipment (UE) via the distributed node, wherein the first message is a non-access layer message.

[0163] Aspect 8: The method according to aspect 7, further comprising: sending a third message to the core node indicating support for a tracking area associated with a cell of the distributed node.

[0164] Aspect 9: The method according to any one of aspects 7 to 8, wherein the request is a handover request.

[0165] Aspect 10: The method according to any one of aspects 7 to 9, wherein the request and the second message are conveyed in a single control message.

[0166] Aspect 11: A method according to any one of Aspects 7 to 10, wherein the second message includes at least one of the following: an identifier of the distributed node, an indication of a handover request associated with the distributed node, an indication of a tracking area of ​​a cell served by the distributed node, or an indication of a cell identifier of the cell served by the distributed node.

[0167] Aspect 12: A method according to any one of Aspects 7 to 11, wherein the second message includes at least one of the following: an identifier of the core node, an indication of the amount of elapsed time that has occurred since the first message, an indication of the amount of elapsed time that has occurred since signaling associated with the core node, an indication of the occurrence of signaling associated with the core node or another core node, an indication of signaling associated with the UE's registration with the core node, or an indication of redirection of signaling associated with the core node to another node.

[0168] Aspect 13: According to the method according to any one of aspects 7 to 12, the method further includes: in conjunction with the migration of the distributed node and the UE to another target node, forwarding the second message to the another target node.

[0169] Aspect 14: A method according to any one of Aspects 7 to 13, wherein forwarding the second message includes: forwarding the second message based at least in part on an amount of elapsed time since signaling with the core node occurred at the source node or the target node.

[0170] Aspect 15: A method of wireless communication performed by a core node, the method comprising: receiving an indication of support for a tracking area from a target node, wherein the tracking area is included in a registration area configured for a user equipment (UE) associated with a source node; and sending a request for the target node to page the UE using the tracking area.

[0171] Aspect 16: The method according to aspect 15 further comprises: configuring the registration area for the UE, wherein the registration area includes the tracking area associated with the source node.

[0172] Aspect 17: According to the method according to any one of Aspects 15 to 16, the method further includes: releasing the non-access stratum connection of the UE based on configuring the registration area for the UE.

[0173] Aspect 18: According to the method described in any one of Aspects 15 to 17, the method also includes: receiving another indication from the source node that the source node no longer supports the tracking area; and wherein sending the request for the target node to page the UE includes: sending the request for the target node to page the UE based at least in part on receiving the other indication from the source node that the source node no longer supports the tracking area.

[0174] Aspect 19: The method according to any one of aspects 15 to 18, wherein the tracking area is associated with a distributed node providing communication services for the UE or a cell served by the distributed node providing communication services for the UE.

[0175] Aspect 20: 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 6.

[0176] Aspect 21: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 1 to 6.

[0177] Aspect 22: 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 6.

[0178] Aspect 23: 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 6.

[0179] Aspect 24: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set 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 6.

[0180] Aspect 25: 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 7 to 14.

[0181] Aspect 26: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 7 to 14.

[0182] Aspect 27: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 7 to 14.

[0183] Aspect 28: 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 7 to 14.

[0184] Aspect 29: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set 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 7 to 14.

[0185] Aspect 30: An apparatus for wireless communication 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 15 to 19.

[0186] Aspect 31: A device for wireless communication, the device comprising a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 15 to 19.

[0187] Aspect 32: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method according to one or more of aspects 15 to 19.

[0188] Aspect 33: 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 15 to 19.

[0189] Aspect 34: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set 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 15 to 19.

[0190] 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.

[0191] As used herein, the term "component" is intended to be broadly interpreted as hardware, and / or a combination of 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, execution threads, procedures and / or functions, etc. As used herein, "processor" is implemented by a combination of hardware and / or hardware and software. It will be apparent that the system and / or method 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, the operation and behavior of the system and / or method are not described herein with reference to specific software codes, because it will be understood by those skilled in the art that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

[0192] 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.

[0193] 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 listed 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 list of items refers to any combination of these items (which 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 (e.g., 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 ordering of a, b and c).

[0194] Any element, action or instruction used herein should not be interpreted as key or necessary, unless clearly stated so. In addition, as used herein, the article "one" is intended to include one or more projects, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more projects connected with 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 projects, and can be used interchangeably with "one or more". If only want to refer to a project, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to represent "based at least in part on", unless explicitly stated otherwise. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and can be used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").

Claims

1. A source node for wireless communication, the source node comprising: Memory; and one or more processors coupled to the memory and configured to: forwarding a first message between a user equipment (UE) and a core node via a distributed node, wherein the first message is a non-access stratum message; as well as A second message associated with migration of the distributed node from the source node to the target node is sent to a target node, wherein the second message identifies the forwarding of the first message.

2. The source node of claim 1, wherein the one or more processors are further configured to: In combination with sending the second message, the connection between the UE and the distributed node is released.

3. The source node of claim 2, wherein releasing the connection is associated with transitioning the UE to an idle state or an inactive state.

4. The source node of claim 2, wherein releasing the connection is associated with migrating the distributed node to the target node.

5. The source node of claim 1, wherein the second message comprises at least one of: an identifier of the distributed node, an indication of a handover request associated with the distributed node, an indication of a tracking area of ​​a cell served by the distributed node, or An indication of a cell identifier of a cell served by the distributed node.

6. The source node of claim 1, wherein the second message comprises at least one of: an identifier of the core node, an indication of the amount of elapsed time that has occurred since the first message, an indication of an amount of elapsed time that has occurred since signaling associated with the core node, an indication of the occurrence of signaling associated with the core node or another core node, an indication of signalling associated with registration of the UE with the core node, or An indication to redirect signaling associated with the core node to another node.

7. A target node for wireless communication, the target node comprising: Memory; and one or more processors coupled to the memory and configured to: receiving, from a source node, a request to establish a connection with a distributed node connected to the source node; as well as A second message associated with migration of the distributed node from the source node to the target node is received from the source node and based at least in part on receiving the request, wherein the second message identifies forwarding of a first message between a core node and a user equipment (UE) via the distributed node, wherein the first message is a non-access stratum message.

8. The target node of claim 7, wherein the one or more processors are further configured to: A third message is sent to the core node indicating support for a tracking area associated with the cell of the distributed node.

9. The target node of claim 7, wherein the request is a handover request.

10. The target node of claim 7, wherein the request and the second message are conveyed in a single control message.

11. The target node according to claim 7, wherein the second message comprises at least one of the following: an identifier of the distributed node, an indication of a handover request associated with the distributed node, an indication of a tracking area of ​​a cell served by the distributed node, or An indication of a cell identifier of a cell served by the distributed node.

12. The target node according to claim 7, wherein the second message comprises at least one of: an identifier of the core node, an indication of the amount of elapsed time that has occurred since the first message, an indication of an amount of elapsed time that has occurred since signaling associated with the core node, an indication of the occurrence of signaling associated with the core node or another core node, an indication of signalling associated with registration of the UE with the core node, or An indication to redirect signaling associated with the core node to another node.

13. The target node of claim 7, wherein the one or more processors are further configured to: In conjunction with the distributed node and the migration of the UE to another target node, the second message is forwarded to the another target node.

14. The target node of claim 7, wherein to forward the second message, the one or more processors are configured to: The second message is forwarded based at least in part on an amount of elapsed time since signaling with the core node occurred at the source node or the target node.

15. A core node for wireless communication, the core node comprising: Memory; and one or more processors coupled to the memory and configured to: receiving, from a target node, an indication of support for a tracking area, wherein the tracking area is included in a registration area configured for a user equipment (UE) associated with a source node; as well as A request is sent for the target node to page the UE using the tracking area.

16. The core node of claim 15, wherein the one or more processors are further configured to: The registration area is configured for the UE, wherein the registration area includes the tracking area associated with the source node.

17. The core node of claim 15, wherein the one or more processors are further configured to: Based on configuring the registration area for the UE, a non-access stratum connection of the UE is released.

18. The core node of claim 15, wherein the one or more processors are further configured to: receiving from the source node another indication that the source node no longer supports the tracking area; and Wherein, in order to send the request for the target node to page the UE, the one or more processors are configured to: Based at least in part on receiving the further indication from the source node that the source node no longer supports the tracking area, sending the request for the target node to page the UE.

19. The core node according to claim 15, wherein the tracking area is associated with a distributed node providing communication services for the UE or a cell served by the distributed node providing communication services for the UE.

20. A method of wireless communication performed by a source node, the method comprising: forwarding a first message between a user equipment (UE) and a core node via a distributed node, wherein the first message is a non-access stratum message; as well as A second message associated with migration of the distributed node from the source node to the target node is sent to a target node, wherein the second message identifies the forwarding of the first message.

21. The method according to claim 20, further comprising: In combination with sending the second message, the connection between the UE and the distributed node is released.

22. The method of claim 21, wherein releasing the connection is associated with transitioning the UE to an idle state or an inactive state.

23. The method of claim 21, wherein releasing the connection is associated with migrating the distributed node to the target node.

24. The method of claim 20, wherein the second message comprises at least one of: an identifier of the distributed node, an indication of a handover request associated with the distributed node, an indication of a tracking area of ​​a cell served by the distributed node, or An indication of a cell identifier of a cell served by the distributed node.

25. The method of claim 20, wherein the second message comprises at least one of: an identifier of the core node, an indication of the amount of elapsed time that has occurred since the first message, an indication of an amount of elapsed time that has occurred since signaling associated with the core node, an indication of the occurrence of signaling associated with the core node or another core node, An indication of signaling associated with registration of the UE with the core node, or an indication of redirection of signaling associated with the core node to another node.

Images