User equipment capability update during mobility operations

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) can receive, from a first type of network, an indication of whether a first UE capability container associated with the first type of network is stored after a first handover from the first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network and the other of the first type of network and the second type of network is a non-terrestrial network. The UE can transmit a mobility operation message during a mobility operation associated with a second handover from the second type of network to the first type of network. Numerous other aspects are described.

Description

Cross-references to related applications

[0001] This patent application claims priority to Greek Patent Application No. 20240100062, filed on January 31, 2024, entitled “USER EQUIPMENT CAPABILITY UPDATE DURING MOBILITY OPERATIONS”, assigned to the assignee of this application. The disclosure of the earlier application is considered part of this patent application and is incorporated herein by reference. Background Technology

[0002] All aspects of this disclosure relate to wireless communication in general, and more particularly to techniques, apparatus and methods for user equipment (UE) to perform mobility operations.

[0003] Wireless communication systems are widely deployed to provide a variety of services, including voice, text, messaging, video, data, and / or other services. Services may include unicast, multicast, and / or broadcast services, etc. Typical wireless communication systems employ multiple access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (e.g., time-domain resources, frequency-domain resources, spatial-domain resources, and / or device transmit power, etc.). Examples of such multiple access RATs include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0004] The aforementioned Multiple Access RATs have been adopted in various telecommunications standards to provide a common protocol enabling different wireless communication devices to communicate at the city, national, regional, or global level. An example telecommunications standard is New Radio (NR). NR (also known as 5G) is part of the continuous evolution of mobile broadband announced by the 3rd Generation Partnership Project (3GPP). NR (and other mobile broadband evolutions beyond NR) can be designed to better support the Internet of Things (IoT) and reduced-capacity device deployments, industrial connectivity, millimeter-wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployments, sidelinks and other device-to-device direct communication technologies (e.g., cellular vehicle-to-everything (CV2X) communications), massive MIMO, decomposed network architectures and network topology expansion, multi-subscriber implementations, high-precision positioning and / or radio frequency (RF) sensing, and more. As the demand for mobile broadband access continues to grow, further improvements to NR can be implemented, and other radio access technologies (such as 6G) can be introduced to further advance mobile broadband evolution. Summary of the Invention

[0005] Some aspects described herein relate to a method of wireless communication performed by a User Equipment (UE). The method may include: receiving from a first type of network an indication of whether a first UE capability container associated with the first type of network was stored after a first handover from the first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network. The method may include: transmitting a mobility operation message during a mobility operation associated with a second handover from the second type of network to the first type of network, wherein the mobility operation message includes a UE capability update indicator based on the indication of whether the first UE capability container was stored after the first handover.

[0006] Some aspects described herein relate to a method for wireless communication performed by a UE. The method may include: sending a mobility operation message including an indication that a UE capability indicator identifies either a change to a UE capability or a mobility scenario of a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network. The method may also include: selectively sending a UE capability report to identify the change to the UE capability based on whether the UE capability indicator identifies a change to the UE capability or a mobility scenario.

[0007] Some aspects described herein relate to a method for wireless communication performed by a network node. The method may include: transmitting an indication, in conjunction with a first type of network, of whether a first UE capability container associated with the first type of network is stored after a first handover from the first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network. The method may also include: receiving a mobility operation message during a mobility operation associated with a second handover from the second type of network to the first type of network, wherein the mobility operation message includes a UE capability update indicator based on the indication of whether the first UE capability container was stored after the first handover.

[0008] Some aspects described herein relate to a method for wireless communication performed by a network node. The method may include: receiving a mobility operation message including an indication of whether a UE capability indicator identifies a change to a UE capability or a mobility scenario of a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network. The method may also include: based on whether the UE capability indicator identifies a change to the UE capability or a mobility scenario, sending the mobility operation message using a received UE capability report indicating the change to the UE capability or using stored UE capabilities.

[0009] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions enables the UE to: receive from a first-type network an indication of whether a first UE capability container associated with the first-type network was stored after a first handover from the first-type network associated with the first UE capability to a second-type network associated with a second UE capability container, wherein one of the first-type network and the second-type network is a terrestrial network, and the other of the first-type network and the second-type network is a non-terrestrial network. When executed by one or more processors of the UE, the set of instructions enables the UE to: transmit a mobility operation message during a mobility operation associated with a second handover from the second-type network to the first-type network, wherein the mobility operation message includes a UE capability update indicator based on the indication of whether the first UE capability container was stored after the first handover.

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication when executed by one or more processors of a UE. When executed by one or more processors of the UE, the set of instructions may cause the one or more instructions to: transmit a mobility operation message including an indication of whether a UE capability indicator identifies a change in UE capability or a mobility scenario of a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network. When executed by one or more processors of the UE, the set of instructions may also cause the one or more instructions to: selectively transmit a UE capability report to identify the change in UE capability, based on whether the UE capability indicator identifies a change in UE capability or a mobility scenario.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. When executed by one or more processors of the network node, the set of instructions enables the network node to: transmit an indication, in conjunction with a first type of network, whether a first UE capability container associated with the first type of network is stored after a first handover from the first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network. When executed by one or more processors of the network node, the set of instructions enables the network node to: receive a mobility operation message during a mobility operation associated with a second handover from the second type of network to the first type of network, wherein the mobility operation message includes a UE capability update indicator based on the indication of whether the first UE capability container was stored after the first handover.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network node. When executed by one or more processors of the network node, the set of instructions enables the network node to: receive a mobility operation message including an indication of whether a UE capability indicator identifies a change in UE capability or a mobility scenario of a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network. When executed by one or more processors of the network node, the set of instructions enables the network node to: based on whether the UE capability indicator identifies a change in UE capability or a mobility scenario, send a mobility operation message using a received UE capability report indicating a change in UE capability or using stored UE capabilities.

[0013] Some aspects described herein relate to a UE for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to receive from a first type of network an indication of whether a first UE capability container associated with the first type of network is stored after a first handover from the first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network. The one or more processors may be configured to send a mobility operation message during mobility operations associated with a second handover from the second type of network to the first type of network, wherein the mobility operation message includes a UE capability update indicator based on the indication of whether the first UE capability container was stored after the first handover.

[0014] Some aspects described herein relate to a UE for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to send a mobility operation message including an indication of whether a UE capability indicator identifies a change in UE capability or a mobility scenario of a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network. The one or more processors may be configured to selectively send a UE capability report to identify the change in UE capability based on whether the UE capability indicator identifies a change in UE capability or a mobility scenario.

[0015] Some aspects described herein relate to a network node for wireless communication. The network node may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to, in conjunction with a first type of network, transmit an indication of whether a first UE capability container associated with the first type of network is stored after a first handover from the first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network. The one or more processors may be configured to receive a mobility operation message during mobility operations associated with a second handover from the second type of network to the first type of network, wherein the mobility operation message includes a UE capability update indicator based on the indication of whether the first UE capability container was stored after the first handover.

[0016] Some aspects described herein relate to a network node for wireless communication. The network node may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to receive a mobility operation message including an indication of whether a UE capability indicator identifies a change in UE capability or a mobility scenario of a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network. The one or more processors may be configured to send the mobility operation message based on whether the UE capability indicator identifies a change in UE capability or a mobility scenario, using a received UE capability report indicating a change in UE capability or using stored UE capabilities.

[0017] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: means for receiving from a first type of network an indication of whether a first UE capability container associated with the first type of network is stored after a first handover from the first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network. The apparatus may also include: means for transmitting a mobility operation message during mobility operation associated with a second handover from the second type of network to the first type of network, wherein the mobility operation message includes a UE capability update indicator based on the indication of whether the first UE capability container was stored after the first handover.

[0018] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: components for transmitting a mobility operation message, the mobility operation message including an indication of whether a UE capability indicator identifies a change in UE capability or a mobility scenario of a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network. The apparatus may also include: components for selectively transmitting a UE capability report to identify the change in UE capability based on whether the UE capability indicator identifies a change in UE capability or an identification of a mobility scenario.

[0019] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: means for transmitting an indication, in conjunction with a first type of network, whether a first UE capability container associated with the first type of network is stored after a first handover from the first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network. The apparatus may also include: means for receiving a mobility operation message during mobility operation associated with a second handover from the second type of network to the first type of network, wherein the mobility operation message includes a UE capability update indicator based on the indication of whether the first UE capability container was stored after the first handover.

[0020] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include: components for receiving a mobility operation message, the mobility operation message including an indication of whether a UE capability indicator identifies a change in UE capabilities or a mobility scenario involving a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network. The apparatus may also include: components for transmitting the mobility operation message based on whether the UE capability indicator identifies a change in UE capabilities or an indication of a mobility scenario, using a received UE capability report indicating the change in UE capabilities or using stored UE capabilities.

[0021] Various aspects of this disclosure may be implemented or be implemented as described in whole by or embodied in the methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices and / or processing systems as fully described in the specification and drawings and illustrated in the specification and drawings.

[0022] The preceding paragraphs of this section have broadly summarized some aspects of this disclosure. These and additional aspects will be described below. The disclosed aspects may serve as the basis for modifying or designing other aspects for performing the same or similar purposes of this disclosure. Such equivalent aspects do not depart from the scope of the appended claims. The characteristics, organization, and methods of operation of the aspects disclosed herein will be better understood from the following description taken in conjunction with the accompanying drawings. Attached Figure Description

[0023] The accompanying drawings illustrate some aspects of this disclosure but do not limit its scope, as other aspects can be achieved by this description. Each drawing in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims. Identical or similar reference numerals in different drawings may identify identical or similar elements.

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

[0025] Figure 2 This is an illustration of an example network node communicating with an example user equipment (UE) in a wireless network according to the present disclosure.

[0026] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.

[0027] Figure 4A and Figure 4BThese are illustrations of examples of regenerative satellite deployment and transparent satellite deployment in a non-terrestrial network according to this disclosure.

[0028] Figure 5A and Figure 5B This is a diagram illustrating examples of mobility operations in terrestrial and non-terrestrial networks according to this disclosure.

[0029] Figure 6 This is a diagram illustrating an example of maintaining a UE capability container during mobility operations according to this disclosure.

[0030] Figure 7 This is a diagram illustrating an example of a UE capability change indication according to this disclosure.

[0031] Figure 8 This is a diagram illustrating an example process performed, for example, at the UE or a device of the UE, according to this disclosure.

[0032] Figure 9 This is a diagram illustrating an example process performed, for example, at the UE or a device of the UE, according to this disclosure.

[0033] Figure 10 This is a diagram illustrating an example process performed, for example, at a network node or a device of a network node, according to the present disclosure.

[0034] Figure 11 This is a diagram illustrating an example process performed, for example, at a network node or a device of a network node, according to the present disclosure.

[0035] Figure 12 This is a diagram of an example device for wireless communication according to the present disclosure.

[0036] Figure 13 This is a diagram illustrating an example of a hardware implementation of a device employing a processing system according to the present disclosure.

[0037] Figure 14 The diagram illustrates an example of a specific implementation of the code and circuitry for a device according to this disclosure.

[0038] Figure 15 This is a diagram of an example device for wireless communication according to the present disclosure.

[0039] Figure 16 This is a diagram illustrating an example of a hardware implementation of a device employing a processing system according to the present disclosure.

[0040] Figure 17 The diagram illustrates an example of a specific implementation of the code and circuitry for a device according to this disclosure. Detailed Implementation

[0041] Terrestrial networks (TN) comprise wireless communication networks supported by terrestrial network nodes. In contrast, non-terrestrial networks (NTN) comprise wireless communication networks supported by non-terrestrial network nodes, such as satellite-based or airborne network nodes. NTN network nodes (such as satellite-based network nodes) can communicate with terrestrial gateways and one or more terrestrial core network entities (such as Mobility Management Entities (MMEs)). In some deployments, TN network nodes and associated TN cells can share an MME with NTN network nodes and associated NTN cells. In other deployments, TN network nodes can be associated with a first MME (such as a TN MME), and NTN network nodes can be associated with a second MME (such as an NTN MME).

[0042] In this example, the User Equipment (UE) can be configured to access both the TN and NTN. In this example, the UE can enter a Radio Link Failure (RLF) state or a suspended state when transitioning between the TN and NTN. In other words, the UE can connect to the TN, enter the RLF state, and then switch to the NTN. Similarly, the UE can connect to the NTN, enter the RLF state, and then switch to the TN. When the UE switches between networks, it sends a Tracking Area Update (TAU) message with UE capability information to register with the cell of the network node to which it is switching. The TAU message conveys information about the UE, which the network node can use to switch the UE between the network and associated core network entities, such as between the TN MME and the NTN MME.

[0043] UE capability information, which can be transmitted via a UE capability indicator or a UE capability update indicator, is a message identifying the capabilities of the UE. For example, UE capability information may include the demodulation reference signal (DMRS) supported by the UE, the subcarrier spacing (SCS) supported by the UE, the maximum number of bandwidth portions (BWPs) that the UE can support, or the UE's BWP handover delay, etc. Network nodes and / or one or more core network entities associated with them can use the UE capability update indicator to configure one or more communication parameters for registering the UE with the cell. The MME can store UE capability information in information elements called UE capability containers. A UE capability container may include information elements (IEs) with a configuration format having a set of fields containing a set of values ​​that identify UE capability information, such as antenna capabilities, frequency switching capabilities, or another capability. For example, one type of UE capability container may include a UE-EUTRA-Capability IE, which includes a set of fields for transmitting UE capability information.

[0044] A UE capability container is maintained on a per-network-type basis, such that a first UE capability container is maintained for a first-type UE capability indicator signaled to a first-type network, and a second UE capability container is maintained for a second-type UE capability indicator signaled to a second-type network. In other words, the UE can signal a first UE capability indicator for TN stored in the first UE capability container by the MME and a second UE capability indicator for NTN stored in the second UE capability container by the MME (the same MME or a different MME).

[0045] Therefore, a UE can send a first UE capability indicator when registering with a first-type network (such as an NTN) and a second UE capability indicator when registering with a second-type network (such as a TN). When the UE switches back from a second-type network to a first-type network, it can again send the first UE capability indicator via a UE capability update indicator message to register with the first-type network. However, after the UE switches away from the first-type network, the MME associated with the first-type network may have already stored a UE capability container containing the UE capability information. In other words, when the UE sends a TAU message with a UE capability update indicator to transmit UE capability information, the MME may have already stored the UE capability information, but the UE may lack the information indicating that the MME has continued to store a UE capability container containing the UE capability information. Therefore, network resources may be unnecessarily used to transmit UE capability information.

[0046] The various aspects collectively relate to UE capability updates during mobility operations such as cell selection, cell reselection, or cell registration procedures. Some aspects more specifically concern whether the UE receives an indication of whether the UE capability indicator is maintained after the UE switches from a first-type network (such as NTN) to a second-type network (such as TN) (or vice versa). The UE capability container and associated UE capability information can be maintained when the MME (such as an NTN MME or a TN MME) does not remove the UE capability container after the UE switches to another MME. The MME can remove the UE capability container by reallocating memory used to store UE capability information, reallocating the index value pointing to the memory used to store UE capability information, or through another procedure. For example, the UE can receive a System Information Block (SIB) message with a field indicating whether the UE capability indicator was stored in TN or NTN after the UE switched network types.

[0047] In some aspects, by receiving an indication of whether to maintain the UE capability indicator, the UE can send a mobility operation message that does not include the UE capability update indicator when switching back from a second-type network to a first-type network. The mobility operation message may include a TAU message associated with triggering a mobility operation (such as cell selection, cell reselection, or cell registration procedures). In other words, the UE suppresses the transmission of the UE capability update indicator when it has already signaled to the MME that it continues to store the UE capability update indicator. In some aspects, the UE can receive an indication of the time period for which the MME will continue to store the UE capability container containing UE capability information. In such aspects, the UE can determine whether to include the UE capability update indicator in the TAU message based on whether the time period has elapsed.

[0048] In some aspects, the UE can include an indicator in the TAU message that indicates whether the TAU message includes changes to the UE capability information. When the UE indicates that the TAU message includes changes to the UE capability information, the network node and / or MME can use the changes to the UE capability information indicated in the TAU message to update the UE capability container. In contrast, when the UE indicates that the TAU message does not include changes to the UE capability information, the network node and / or MME can use the stored UE capability information in the stored UE capability container to register the UE with the network in conjunction with mobility operations.

[0049] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential improvements. In some examples, the described techniques can be used to improve the resource utilization efficiency of signaling associated with the UE sending a UE capability update indicator by providing the UE with an indication that the MME maintains the UE capability container after the UE leaves the network type associated with the UE capability container. Additionally or alternatively, by providing the network node with an indication of whether the TAU message includes an update to the UE capability, the network node can determine whether to register the UE with the network cell using the new UE capability or the stored UE capability, thereby enabling the UE to successfully complete mobility operations. Furthermore, by providing the network node with an indication of whether the TAU message includes an update to the UE capability, the UE can abandon sending UE capability information if no update is available, thereby improving the resource utilization efficiency of signaling.

[0050] Various aspects of this disclosure are described below with reference to the accompanying drawings. However, aspects of this disclosure may be embodied in many different forms and should not be construed as limited to any specific aspect illustrated or described with reference to the drawings or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of protection of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, various combinations or numbers of aspects set forth herein may be used to implement an apparatus or a practice. Furthermore, the scope of this disclosure is intended to cover apparatuses having structures and / or functionalities other than those available for practicing the various aspects of this disclosure set forth herein, or methods practiced using these other structures and / or functionalities. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.

[0051] Various methods, operations, apparatuses, and techniques will now be presented with reference to them. These methods, operations, apparatuses, and techniques will be described in detail below and illustrated in the accompanying drawings by various boxes, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0052] Multiple access radio access technology (RAT) has been adopted in various telecommunications standards to provide a common protocol that enables wireless communication devices to communicate at the city, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of the continuous mobile broadband evolution announced by the 3rd Generation Partnership Project (3GPP). 5G NR supports a variety of technologies and use cases, including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV).

[0053] With increasing demand for broadband access and the evolution of technologies supported by wireless communication networks, further technological improvements can be adopted in or implemented for 5G NR or future RATs (such as 6G) to further advance the evolution of wireless communication for a variety of existing and new use cases and applications. These technological improvements can be associated with new frequency band extensions, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, decomposed network architectures and network topology extensions, device aggregation, advanced duplex communication, sidelinks and other device-to-device direct communication, IoT (including passive or ambient IoT) networks, reduced-capacity (RedCap) UE functionality, industrial connectivity, multi-subscriber implementations, high-precision positioning, radio frequency (RF) sensing and / or artificial intelligence or machine learning (AI / ML), and more. Such technological improvements can support use cases such as wireless backhaul, wireless data centers, extended reality (XR) and metaverse applications, meta-services for supporting vehicle connectivity, holographic and mixed reality communications, autonomous and collaborative robots, vehicle platooning and collaborative manipulation, sensor networks, posture monitoring, brain-computer interfaces, digital twin applications, asset management, and general coverage applications using off-ground and / or aerial platforms, etc. The methods, operations, apparatuses, and techniques described herein can implement one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0054] Figure 1 This is a diagram illustrating an example of a wireless communication network 100 according to the present disclosure. The wireless communication network 100 may be a 5G (or NR) network or a 6G network, or may include elements of a 5G (or NR) network or elements of a 6G network, etc. The wireless communication network 100 may include a plurality of network nodes 110, shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d. Network nodes 110 may support communication with a plurality of UEs 120 (shown as UE120a, UE 120b, UE 120c, UE 120d, and UE 120e).

[0055] Network nodes 110 and UEs 120 of wireless communication network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, carriers, and / or channels according to frequency or wavelength. For example, devices of wireless communication network 100 can communicate using one or more operating bands. In some aspects, multiple wireless communication networks 100 can be deployed in a given geographical area. Each wireless communication network 100 can support a specific RAT (which may also be referred to as an air interface) and can operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include 4G RATs, 5G / NR RATs, and / or 6G RATs, etc. In some examples, when multiple RATs are deployed in a given geographical area, each RAT in that geographical area can operate on a different frequency to avoid interference with each other.

[0056] Various operating bands have been defined by frequency range designations: FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Although a portion of FR1 is greater than 6 GHz, in some documents and articles, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band. Similarly, in some documents and articles, FR2 is often (interchangeably) referred to as the “millimeter wave” band, but this is distinct from the Extremely High Frequency (EHF) band (30 GHz to 300 GHz) designated as the “millimeter wave” band by the International Telecommunication Union (ITU). The frequencies between FR1 and FR2 are generally referred to as the midband frequencies, including FR3. Frequency bands falling within FR3 can inherit FR1 or FR2 characteristics, thereby effectively extending the characteristics of FR1 or FR2 into the midband frequency range. Therefore, "below 6 GHz" (if used herein) can broadly refer to frequencies less than 6 GHz, within FR1, and / or included in the midband frequency range. Similarly, the term "millimeter wave" (if used herein) can broadly refer to frequencies included in the midband frequency range, within FR2, FR4, FR4-a, FR4-1, or FR5, and / or within the EHF band. Higher frequency bands can extend 5G NR operation, 6G operation, and / or other RATs above 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 can implement dynamic spectrum sharing (DSS), where multiple RATs (e.g., 4G / LTE and 5G / NR) are implemented within a single frequency band using dynamic bandwidth allocation (e.g., based on user demand). It is conceivable 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.

[0057] Network node 110 may include one or more devices, components, or systems that enable communication between UE 120 and one or more devices, components, or systems of wireless communication network 100. Network node 110 may be, may include, or may also be referred to as an NR network node, 5G network node, 6G network node, node B, eNB, gNB, access point (AP), transmit / receive point (TRP), mobility element, core, network entity, network element, network equipment, and / or another type of device, component, or system included in a radio access network (RAN).

[0058] Network node 110 may be implemented as a single physical node (e.g., a single physical structure) or as two or more physical nodes (e.g., two or more different physical structures). For example, network node 110 may be a device or system implementing a portion of a radio protocol stack, a device or system implementing a complete radio protocol stack (such as a complete gNB protocol stack), or a collection of devices or systems collectively implementing a complete radio protocol stack. For example, and as shown, network node 110 may be an aggregated network node (with an aggregated architecture), meaning that network node 110 can implement a complete radio protocol stack physically and logically integrated within a single node (e.g., a single physical structure) in the wireless communication network 100. For example, aggregated network node 110 may consist of a single standalone base station or a single TRP that uses the complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless communication network 100.

[0059] Alternatively, and also as shown in the figure, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 can realize a radio protocol stack that is physically distributed and / or logically distributed among two or more nodes in the same or different geographic locations. For example, a decomposed network node may have a decomposed architecture. In some deployments, decomposed network node 110 may be used in integrated access and backhaul (IAB) networks, in open radio access networks (O-RAN) (such as network configurations compliant with the O-RAN Alliance), or in virtualized radio access networks (vRAN) (also referred to as cloud radio access networks (C-RAN)) to facilitate scaling by decomposing base station functionality into multiple units that can be deployed independently.

[0060] Network nodes 110 of the wireless communication network 100 may include one or more central units (CUs), one or more distributed units (DUs), and / or one or more radio units (RUs). CUs may host one or more higher-layer control functions, such as Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, and / or Service Data Adaptation Protocol (SDAP) functions, etc. DUs may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and / or one or more higher physical (PHY) layers, at least in part, according to functional splits (such as functional splits defined by 3GPP). In some examples, DUs may also host one or more lower PHY layer functions, such as Fast Fourier Transform (FFT), Inverse FFT (iFFT), beamforming, Physical Random Access Channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, etc. RUs may host RF processing functions or lower PHY layer functions, such as FFT, iFFT, beamforming, or PRACH extraction and filtering, etc., according to functional splits (such as lower-layer functional splits). In this type of architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UE 120s.

[0061] In some aspects, a single network node 110 may include a combination of one or more CUs, one or more DUs, and / or one or more RUs. Additionally or alternatively, network node 110 may include one or more near real-time (near RT) RAN Intelligent Controllers (RICs) and / or one or more non-real-time (non-RT) RICs. In some examples, CUs, DUs, and / or RUs may be implemented as virtual units, such as Virtual Central Units (VCUs), Virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs), etc. Virtual units may be implemented as virtual network functions, such as those associated with cloud deployments.

[0062] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for specific geographic areas. In 3GPP, the term "cell" can refer to the coverage area of ​​network node 110 or to network node 110 itself, depending on the context in which the term is used. Network node 110 can support one or more (e.g., three) cells. In some examples, network node 110 can provide communication coverage for macro cells, pico cells, femto cells, or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femto cell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UE 120 associated with that femto cell (e.g., UE 120 in a Closed Subscriber Group (CSG)). A network node 110 used for a macro cell may be referred to as a macro network node. Network node 110 used for a picocell may be referred to as a pico network node. Network node 110 used for a femtocell may be referred to as a femto network node or a home network node. In some examples, the cell may not necessarily be stationary. For example, the geographical area of ​​the cell may move depending on the location of the associated mobile network node 110 (e.g., a train, satellite base station, drone, or NTN network node).

[0063] The wireless communication network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, piconet nodes, femtonet nodes, relay network nodes, aggregation network nodes, and / or decomposition network nodes, etc. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 130a, network node 110b can be a pico network node for pico cell 130b, and network node 110c can be a femto network node for femto cell 130c. Compared to other types of network nodes 110, the various types of network nodes 110 typically transmit at different power levels, serve different coverage areas, and / or have different effects on interference in the wireless communication network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0064] In some examples, network node 110 may be, may include, or operate as a RU, TRP, or base station communicating with one or more UEs 120 via a radio access link (which may be referred to as a "Uu" link). The radio access link may include a downlink and an uplink. A "downlink" (or "DL") refers to the communication direction from network node 110 to UE 120, and an "uplink" (or "UL") refers to the communication direction from UE 120 to network node 110. Downlink channels may include one or more control channels and one or more data channels. Downlink control channels may be used to transmit downlink control information (DCI) (e.g., scheduling information, reference signals, and / or configuration information) from network node 110 to UE 120. Downlink data channels may be used to transmit downlink data (e.g., user data associated with UE 120) from network node 110 to UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCH), and downlink data channels may include one or more physical downlink shared channels (PDSCH). The uplink channel may similarly include one or more control channels and one or more data channels. The uplink control channel can be used to transmit uplink control information (UCI) from UE 120 to network node 110 (e.g., transmitting corresponding reference signals and / or feedback with one or more downlinks). The uplink data channel can be used to transmit uplink data (e.g., user data associated with UE 120) from UE 120 to network node 110. The uplink control channel may include one or more physical uplink control channels (PUCCH), and the uplink data channel may include one or more physical uplink shared channels (PUSCH). The downlink and uplink may each include a set of resources on which network node 110 and UE 120 can communicate.

[0065] Downlink and uplink resources may include time-domain resources (frames, subframes, time slots, and / or symbols), frequency-domain resources (bands, component carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial-domain resources (specific transmission directions and / or beam parameters). Frequency-domain resources in some bands may be subdivided into bandwidth portions (BWPs). A BWP may be a contiguous block of frequency-domain resources allocated to one or more UEs 120 (e.g., a contiguous block of resource blocks). A UE 120 may be configured with both an uplink BWP and a downlink BWP (where the uplink BWP and downlink BWP may be the same BWP or different BWPs). BWPs may be dynamically configured and / or reconfigured (e.g., by sending DCI configuration to one or more UEs 120 via network node 110), meaning that BWPs may be adjusted in real-time (or near real-time) based on changing network conditions in the wireless communication network 100 and / or based on the specific requirements of one or more UEs 120. This allows for more efficient use of available frequency domain resources in the wireless communication network 100, as fewer frequency domain resources can be allocated to the BWP for UE 120 (which reduces the number of frequency domain resources that UE 120 needs to monitor), thus allowing more frequency domain resources to be distributed across multiple UE 120s. Therefore, the BWP can also assist in the implementation of such UE 120s by facilitating the configuration of smaller bandwidths for communications performed by lower-capacity UE 120s.

[0066] As described above, in some aspects, the wireless communication network 100 may be an IAB network, may include an IAB network, or may be included in an IAB network. In an IAB network, at least one network node 110 is an anchor network node communicating with a core network. The anchor network node 110 may also be referred to as an IAB donor (or "IAB donor"). The anchor network node 110 may be connected to the core network via a wired backhaul link. For example, the Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, the anchor network node 110 may be connected to one or more devices in the core network that provide core access and mobility management functions (AMF). An IAB network typically also includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply IAB nodes (or "IAB-nodes"). Each non-anchor network node 110 can directly communicate with the anchor network node 110 via a wireless backhaul link to access the core network, or can indirectly communicate with the anchor network node 110 via one or more other non-anchor network nodes 110 and an associated wireless backhaul link forming a backhaul path to the core network. Some anchor network nodes 110 or other non-anchor network nodes 110 can also directly communicate with one or more UEs 120 via a wireless access link carrying access services. In some examples, network resources used for wireless communication (such as time resources, frequency resources, and / or spatial resources) can be shared between the access link and the backhaul link.

[0067] In some examples, any network node 110 relaying communication may be referred to as a relay network node, a relay station, or simply a repeater. A repeater may receive communications from an upstream station (e.g., another network node 110 or UE 120) and transmit communications to a downstream station (e.g., UE 120 or another network node 110). In this case, the wireless communication network 100 may include or be referred to as a "multi-hop network." Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. Additionally or alternatively, UE 120 can be a relay station capable of relaying transmissions to or from other UE 120s, or can operate as such a relay station. UE 120 relaying communication can be referred to as a UE repeater or relay UE, etc.

[0068] UE 120 may be physically distributed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. UE 120 may be, may include, an access terminal, another terminal, a mobile station, or a subscriber unit, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. UE 120 may be, or may include, a cellular phone (e.g., a smartphone), 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 smartwatch, smart clothing, smart glasses, a smart wristband and / or smart jewelry (such as a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), an XR device, a vehicle component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that can communicate via a wireless medium, or may be coupled to them.

[0069] UE 120 and / or network node 110 may include one or more chips, system-on-a-chip (SoC), chipsets, packages, or devices that individually or collectively constitute or include a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs), and / or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). Processors may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, a combination of one or more microprocessors with a DSP core, or any other such configuration. One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. A processor group that can be configured or configured to perform a set of functions may include a first processor that can be configured or configured to perform a first function in the set, and a second processor that can be configured or configured to perform a second function in the set, or may include the entire processor group that is configured or configured to perform the set of functions.

[0070] The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuits, each of which may include tangible storage media such as random access memory (RAM) or read-only memory (ROM) or combinations thereof (all of which are generally referred to herein individually as "memory" or collectively as "memory" or "memory circuitry"). One or more of these memories may be coupled to one or more processors in the processor (e.g., operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) and may store processor-executable code (such as software) individually or collectively, which, when executed by one or more processors in the processor, may configure one or more processors in the processor to perform the various functions or operations described herein. Additionally or alternatively, in some examples, one or more processors in the processor may be pre-configured to perform the various functions or operations described herein without being configured by software. The processing system may also include or be coupled to one or more modems (such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modems). In some embodiments, one or more processors of the processing system include or implement one or more modems among the modems. The processing system may also include, or be coupled to, multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas among multiple antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers. UE 120 may be included or may be contained in a housing that houses components associated with UE 120, including the processing system.

[0071] Some UEs 120 may be considered Machine Type Communication (MTC) UEs, Evolved or Enhanced Machine Type Communication (eMTC) UEs, Further Enhanced eMTC (feMTC) UEs, or Enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be collectively referred to as "MTC UEs". MTC UEs may be, may include, or may be included in or coupled with the following: robots, unmanned aerial vehicles, remote devices, sensors, instruments, monitors, and / or location tags. Some UEs 120 may be considered IoT devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. IoT UEs or NB-IoT devices may be, may include, or may be included in or coupled with the following: industrial machines, appliances, refrigerators, doorbell camera devices, home automation devices, and / or lighting fixtures, etc. Some UEs 120 may be considered customer premises equipment, which may include telecommunications equipment installed at a customer location (such as a home or office) to enable access to a service provider’s network (such as being included in or communicating with the wireless communication network 100).

[0072] Some UEs 120 can be categorized according to different categories associated with varying levels of complexity and / or capabilities. UEs 120 in the first category facilitate large-scale IoT within the wireless communication network 100 and offer lower complexity and / or lower cost compared to UEs 120 in the second category. UEs 120 in the second category may include mission-critical IoT devices capable of URLLC, enhanced mobile broadband (eMBB), and / or precise positioning within the wireless communication network 100, legacy UEs, baseline UEs, high-level UEs, advanced UEs, full-capability UEs, and / or premium UEs. UEs 120 in the third category may possess intermediate-level complexity and / or capabilities (e.g., capabilities between first-category UEs 120 and second-capability UEs 120). UEs 120 in the third category may be referred to as reduced-capacity UEs (“RedCap UEs”), intermediate-level UEs, NR lightweight UEs, and / or NR simplified UEs, etc. RedCap UEs bridge the gap in capabilities and complexity between NB-IoT devices and / or eMTC UEs and mission-critical IoT devices and / or premium UEs. RedCap UEs can include, for example, wearable devices, IoT devices, industrial sensors, and / or cameras associated with limited bandwidth, power capacity, and / or transmission range. RedCap UEs can support healthcare environments, building automation, power distribution, process automation, transportation and logistics, and / or smart city deployments, among others.

[0073] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly with each other using sidelink communication (e.g., without communicating through a network node 110 acting as an intermediary). As an example, UE 120a can send data, control information, or other signaling directly to UE 120e as sidelink communication. This contrasts with, for example, UE 120a first sending data to network node 110 in UL communication, and then that network node sending data to UE 120e in DL communication. In various examples, UE 120 can use peer-to-peer (P2P) communication protocols, device-to-device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and / or vehicle-to-pedestrian (V2P) protocols), and / or mesh network communication protocols to send and receive sidelink communication. In some deployments and configurations, network node 110 may schedule and / or allocate resources for sidelink communication between UEs 120 in the wireless communication network 100. In some other deployments and configurations, UE 120 (instead of network node 110) may perform or cooperate with or negotiate with one or more other UEs to perform scheduling operations, resource selection operations, and / or other operations for sidelink communication.

[0074] In various examples, in addition to half-duplex operation, some network nodes and UEs in the wireless communication network 100, including network node 110 and UE 120, can also be configured for full-duplex operation. Network node 110 or UE 120 operating in half-duplex mode can perform only one of transmission or reception during a specific time resource period (such as a specific time slot, symbol, or other time period). Half-duplex operation may involve time division duplex (TDD), where the DL transmission of network node 110 and the UL transmission of UE 120 do not occur in the same time resource (i.e., the transmissions do not overlap in time). In contrast, network node 110 or UE 120 operating in full-duplex mode can transmit and receive communications concurrently (e.g., within the same time resource). By operating in full-duplex mode, network node 110 and / or UE 120 can generally increase the capacity of the network and radio access links. In some examples, full-duplex operation may involve frequency division duplex (FDD), in which network node 110 performs DL transmission in a first frequency band or on a first component carrier, and UE 120 performs transmission in a second frequency band or on a second component carrier, the second frequency band or the second component carrier being different from the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for UE 120 but not for network node 110. For example, UE 120 may simultaneously transmit UL to the first network node 110 and receive DL transmissions from the second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for network node 110 but not for UE 120. For example, network node 110 may simultaneously transmit DL to the first UE 120 and receive UL transmissions from the second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both network node 110 and UE 120.

[0075] In some examples, UE 120 and network node 110 can perform MIMO communication. "MIMO" generally refers to the simultaneous transmission or reception of multiple signals (such as multiple layers or multiple data streams) using the same time and frequency resources. MIMO techniques typically utilize multipath propagation. MIMO can be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO can support simultaneous transmission to multiple receivers, which is called multi-user MIMO (MU-MIMO). Some RATs can employ advanced MIMO techniques such as mTRP operations (including redundant transmission or reception on multiple TRPs), reciprocity in the time or frequency domain, single-frequency network (SFN) transmission, or noncoherent joint transmission (NC-JT).

[0076] In this example, UE 120 can operate in different types of networks. For example, network node 110a can provide TN, and network node 110e can provide NTN. In this example, UE 120a can be able to receive connectivity and network services via network node 110a and / or network node 110e. In some examples, UE 120 can perform mobility operations to handover between a first cell associated with network node 110a and a second cell associated with network node 110e. In this example, network node 110a and network node 110e can share one or more core network devices, such as MMEs. In another example, network node 110a can be associated with a first set of core network devices (such as TN MMEs), and network node 110e can be associated with a second set of core network devices (such as NTN MMEs).

[0077] In some aspects, UE 120 may include a communications manager 140. As described in more detail elsewhere herein, communications manager 140 may receive from a first type of network an indication of whether a first UE capability container associated with the first type of network is stored after a first handover from the first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network and the other of the first type of network and the second type of network is a non-terrestrial network; and transmit a mobility operation message during a mobility operation associated with a second handover from the second type of network to the first type of network, wherein the mobility operation message includes a UE capability update indicator based on the indication of whether the first UE capability container was stored after the first handover. In some aspects, the communication manager 140 may send a mobility operation message including an indication of whether the UE capability indicator identifies a change in UE capabilities or a mobility scenario of a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network and the other is a non-terrestrial network; and selectively sending a UE capability report to identify a change in UE capabilities based on whether the UE capability indicator identifies a change in UE capabilities or a mobility scenario. A mobility scenario may include triggering cell selection, cell reselection, or cell registration procedures, etc. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0078] In some aspects, network node 110 may include communication manager 150. As described in more detail elsewhere herein, communication manager 150 may, in conjunction with a first type of network, send an indication as to whether a first UE capability container associated with the first type of network is stored after a first handover from the first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network and the other of the first type of network and the second type of network is a non-terrestrial network; and receive a mobility operation message during a mobility operation associated with a second handover from the second type of network to the first type of network, wherein the mobility operation message includes a UE capability update indicator based on the indication as to whether the first UE capability container was stored after the first handover. In some aspects, the communication manager 150 can receive a mobility operation message including an indication of whether the UE capability indicator identifies a change in UE capabilities or a mobility scenario of a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network and the other of the first type of network and the second type of network is a non-terrestrial network; and based on whether the UE capability indicator identifies a change in UE capabilities or a mobility scenario, send the mobility operation message using a received UE capability report indicating a change in UE capabilities or using stored UE capabilities. Additionally or alternatively, the communication manager 150 can perform one or more other operations described herein.

[0079] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.

[0080] Figure 2 This is an illustration of an example network node 110 communicating with an example UE 120 in a wireless network according to the present disclosure.

[0081] like Figure 2As shown, network node 110 (such as TN network node 110, NTN network node 110, or core network equipment, etc.) may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a to 232t, where t≥1), a set of antennas 234 (shown as 234a to 234v, where v≥1), a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, a scheduler 246, and / or a communication manager 150, etc. In some configurations, one or a combination of antennas 234, modems 232, MIMO detectors 236, receive processors 238, transmit processors 214, and / or TX MIMO processors 216 may be included in the transceiver of network node 110. The transceiver may be under the control of and used by one or more processors (such as controller / processor 240), and in some respects, may perform aspects of the methods, procedures and / or operations described herein in conjunction with processor-readable code stored in memory 242. In some respects, network node 110 may include one or more interfaces, communication components and / or other components that facilitate communication with UE 120 or another network node.

[0082] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, references to “a / the processor,” “a / the controller / processor,” etc. (in the singular) should be understood as referring to a combination of… Figure 2 The processor described refers to any one or more processors, such as a single processor or a combination of multiple different processors. The reference to "one or more processors" should be understood as a combination of references. Figure 2 Any one or more processors described herein. For example, one or more processors of network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280.

[0083] In some aspects, a single processor can perform all operations described as being performed by one or more processors. In some aspects, a first set of one or more processors can perform a first operation described as being performed by that one or more processors, and a second set of one or more processors can perform a second operation described as being performed by that one or more processors. The first set of processors and the second set of processors can be the same set of processors or can be different sets of processors. The reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as combined... Figure 2 The memory described. For example, an operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0084] For downlink communication from network node 110 to UE 120, transmit processor 214 may receive data (“downlink data”) intended for use by UE 120 (or a set of UEs including UE 120) from data source 212 (such as a data pipeline or data queue). In some examples, transmit processor 214 may select one or more MCSs for UE 120 based on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 may process the data (e.g., including encoding the data) according to the MCS selected for UE 120 for transmission to UE 120 on the downlink, thereby generating data symbols. Transmit processor 214 may process system information (e.g., semi-static resource partitioning information (SRPI)) and / or control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and / or control symbols. The transmitting processor 214 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), or channel state information (CSI) reference signals (CSI-RS)) and / or synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)).

[0085] The TX MIMO processor 216 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, where applicable, and can provide a set of output symbol streams (e.g., T output symbol streams) to a set of modems 232. For example, each output symbol stream can be provided to a corresponding modulator component (shown as MOD) of modem 232. Each modem 232 can use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for Orthogonal Frequency Division Multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 can further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or up-convert) the output sample stream to obtain a time-domain downlink signal. Modems 232a to 232t can transmit a set of downlink signals (e.g., T downlink signals) together via a set of corresponding antennas 234.

[0086] Downlink signals may include DCI communication, MAC control element (MAC-CE) communication, RRC communication, downlink reference signals, or another type of downlink communication. Downlink signals may be transmitted on the PDCCH, PDSCH, and / or another downlink channel. Downlink signals may carry one or more transport blocks (TBs) of data. A TB may be a data unit transmitted via the air interface in the wireless communication network 100. A data stream (e.g., from data source 212) may be encoded into multiple TBs for transmission via the air interface. The number of TBs used to carry data associated with a particular data stream may be associated with a TB size shared by multiple TBs. The TB size may be based on the radio channel conditions of the air interface, the MCS used to encode the data, downlink resources allocated for transmitting data, and / or other parameters, or otherwise associated with them. Generally, a larger TB size allows for a larger amount of data to be transmitted in a single transmission, reducing signaling overhead. However, a larger TB size may be more prone to transmission and / or reception errors than a smaller TB size, but such errors can be mitigated through more robust error correction techniques.

[0087] For uplink communication from UE 120 to network node 110, the uplink signal from UE 120 may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected where applicable by MIMO detector 236 (e.g., receive (Rx) MIMO processor), and / or further processed by receive processor 238 to obtain decoded data and / or control information. Receive processor 238 may provide the decoded data to data sink 239 (which may be a data pipeline, data queue, and / or another type of data sink) and provide the decoded control information to processors such as controller / processor 240.

[0088] Network node 110 may use scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some aspects, scheduler 246 may use DCI to dynamically schedule DL transmissions to and / or UL transmissions from UE 120. In some examples, scheduler 246 may allocate repetitive time-domain and / or frequency-domain resources that UE 120 may use for transmitting and / or receiving communication with RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 120.

[0089] One or more of the following may be included in the RF chain of network node 110: transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, and / or controller / processor 240. The RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and / or other devices for converting analog signals (such as those used for transmission or reception via an air interface) to digital signals (such as those used for processing by one or more processors of network node 110). In some aspects, the RF chain may be a transceiver of network node 110, or may be included in such a transceiver.

[0090] In some examples, network node 110 may use communication unit 244 to communicate with the core network and / or other network nodes. Communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, fiber optic, Common Public Radio Interface (CPRI), and / or wired or wireless backhaul, etc. Network node 110 may use communication unit 244 to send and / or receive data associated with UE 120, or to execute network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.

[0091] UE 120 may include a collection of antennas 252 (shown as antennas 252a to 252r, where r ≥ 1), a collection of modems 254 (shown as modems 254a to 254u, where u ≥ 1), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a memory 282, and / or a communication manager 140, etc. One or more components of UE 120 may be included in housing 284. In some aspects, one or a combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266 may be included in a transceiver included in UE 120. The transceiver may be under the control of and used by one or more processors (such as controller / processor 280), and in some respects, may perform aspects of the methods, procedures, or operations described herein in conjunction with processor-readable code stored in memory 282. In some respects, UE 120 may include another interface, another communication component, and / or another component that facilitates communication with network node 110 and / or another UE 120.

[0092] For downlink communication from network node 110 to UE 120, the set of antennas 252 can receive downlink communication or signals from network node 110 and can provide a set of received downlink signals (e.g., R received signals) to a set of modems 254. For example, each received signal can be provided to a corresponding demodulator component (shown as DEMOD) of modem 254. Each modem 254 can use the corresponding demodulator component to condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal to obtain an input sample. Each modem 254 can use the corresponding demodulator component to further demodulate or process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 can obtain the received symbols from the set of modems 254, can perform MIMO detection on the received symbols where applicable, and can provide the detected symbols. The receiver processor 258 can process (e.g., decode) the detected symbols, provide the decoded data for the UE 120 to the data sink 260 (which may include a data pipeline, a data queue, and / or an application running on the UE 120), and provide the decoded control information and system information to the controller / processor 280.

[0093] For uplink communication from UE 120 to network node 110, the transmitting processor 264 may receive and process data (“uplink data”) from data source 262 (such as data pipelines, data queues, and / or applications running on UE 120) and control information from controller / processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and / or other types of control information. In some aspects, the receiving processor 258 and / or controller / processor 280 may determine one or more parameters related to the transmission of uplink communication for received signals (such as those received from network node 110 or another UE). One or more parameters may include a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, a CQI parameter, or a Transmit Power Control (TPC) parameter, etc. The control information may include indications of RSRP, RSSI, RSRQ, CQI, TPC, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 120 by network node 110.

[0094] Transmit processor 264 can generate reference symbols for one or more reference signals, such as uplink DMRS, uplink sounding reference signal (SRS), and / or another type of reference signal. Symbols from transmit processor 264 can be pre-decoded by TX MIMO processor 266 where applicable, and further processed by an assembly of modems 254 (e.g., for DFT-s-OFDM or CP-OFDM). TX MIMO processor 266 can perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can provide an assembly of output symbol streams (e.g., U output symbol streams) to the assembly of modems 254. For example, each output symbol stream can be provided to a corresponding modulator component (shown as MOD) of modem 254. Each modem 254 can use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 254 may further use a corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0095] Modems 254a to 254u can transmit a set of uplink signals (e.g., R uplink signals or U uplink symbols) via a set of corresponding antennas 252. Uplink signals may include UCI communication, MAC-CE communication, RRC communication, or another type of uplink communication. Uplink signals can be transmitted on PUSCH, PUCCH, and / or another type of uplink channel. Uplink signals can carry one or more TBs of data. Sidelink data and control transmission (i.e., transmission directly between two or more UEs 120) typically uses techniques similar to those described for uplink data and control transmission and may use sidelink-specific channels such as the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Feedback Channel (PSFCH).

[0096] One or more antennas in the set of antennas 252 or the set of antennas 234 may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc., or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or with one or more transmitting or receiving components (such as...) Figure 2 An antenna module is a combination of one or more antenna elements coupled to one or more components. As used herein, "antenna" can mean one or more antennas, one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays. "Antenna panel" can mean a group of antennas (such as antenna elements) arranged in an array or panel that can facilitate beamforming by manipulating the parameters of that group of antennas. "Antenna module" can mean a circuit that includes one or more antennas, and may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.

[0097] In some examples, each antenna element of antenna 234 or antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element that can be used to independently transmit cross-polarized signals. Antenna elements may include patch antennas, dipole antennas, and / or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between antenna elements can allow signals transmitted individually by antenna elements at desired wavelengths to interact or interfere with each other constructively and destructively in various directions (such as to form a desired beam). For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half a wavelength, or another fraction of the wavelength between adjacent antenna elements to allow desired constructive and destructive interference patterns of signals transmitted by individual antenna elements within that desired range.

[0098] The amplitude and / or phase of signals transmitted via antenna elements and / or sub-elements can be modulated and (e.g., by manipulating phase shifts, phase offsets, and / or amplitudes) shifted relative to each other to generate one or more beams; this is known as beamforming. The term "beam" can refer to the directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. "Beam" can also generally refer to the direction associated with such directional signal transmission, the set of directional resources associated with the signal transmission (e.g., angle of arrival, horizontal direction, and / or vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal. In some implementations, antenna elements can be individually selected or deselected for the directional transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers and / or the phase of the signal to form one or more beams. The shape of the beam (such as amplitude, width, and / or the presence of sidelobes) and / or the direction of the beam (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of multiple signals relative to each other.

[0099] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or different numbers of antenna elements. As another example, network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or different numbers of antenna elements. Generally speaking, a larger number of antenna elements provides increased control over the parameters used for beamforming compared to a smaller number of antenna elements, while a smaller number of antenna elements may be less complex to implement and can use less power. Multiple antenna elements can support multi-layer transmission, in which the same time and frequency resources are used to utilize spatial multiplexing to transmit a first layer of communication (which may include a first data stream) and a second layer of communication (which may include a second data stream).

[0100] In some aspects, UE 120 includes components for receiving from a first type of network an indication of whether a first UE capability container associated with the first type of network was stored after a first handover from the first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network and the other of the first type of network and the second type of network is a non-terrestrial network; and / or for sending a mobility operation message during a mobility operation associated with a second handover from the second type of network to the first type of network, wherein the mobility operation message includes a UE capability update indicator based on the indication of whether the first UE capability container was stored after the first handover. In some aspects, UE 120 includes components for transmitting a mobility operation message, the mobility operation message including an indication of whether a UE capability indicator identifies a change in UE capability or a mobility scenario of a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network and the other of the first type of network and the second type of network is a non-terrestrial network; and / or components for selectively transmitting a UE capability report to identify a change in UE capability based on whether the UE capability indicator identifies a change in UE capability or a mobility scenario. Components for UE 120 to perform the operations described herein may include, for example, one or more of a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0101] In some aspects, network node 110 includes: components for transmitting an indication, in conjunction with a first type of network, whether a first UE capability container associated with the first type of network is stored after a first handover from the first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network and the other of the first type of network and the second type of network is a non-terrestrial network; and / or components for receiving a mobility operation message during a mobility operation associated with a second handover from the second type of network to the first type of network, wherein the mobility operation message includes a UE capability update indicator based on the indication of whether the first UE capability container was stored after the first handover. In some aspects, network node 110 includes components for receiving mobility operation messages, which include indications of whether a UE capability indicator identifies a change in UE capabilities or a mobility scenario of a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network and the other of the first type of network and the second type of network is a non-terrestrial network; and / or components for sending mobility operation messages using a received UE capability report indicating a change in UE capabilities or using stored UE capabilities based on whether the UE capability indicator identifies a change in UE capabilities or a mobility scenario. Components for the network node to perform the operations described herein may include, for example, one or more of the following: a communication manager 150, a transmit processor 214, a TXMIMO processor 216, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0102] Although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0103] Figure 3This is an illustration of an example decomposed base station architecture 300 according to the present disclosure. One or more components of the example decomposed base station architecture 300 may be, may include, or may be included in one or more network nodes (such as one or more network nodes 110). The decomposed base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or may communicate indirectly with the core network 320 via one or more decomposed control units (such as non-RT RIC 350 and / or near-RT RIC 370 associated with a Service Management and Orchestration (SMO) framework 360 (e.g., via an E2 link)). The CU 310 may communicate with one or more DU 330s via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RU 340s via a corresponding fronthaul link. Each RU 340 may communicate with one or more UE 120s via a corresponding RF access link. In some deployments, a UE 120 may be served simultaneously by multiple RU 340s. In some examples, different RU 340s (or other components, such as CU 310 or DU 330) may be associated with different types of networks. In these examples, the first RU may be an NTN-RU associated with an NTN cell, and the second RU may be a TN-RU associated with a TN cell. In these examples, the UE 120 may perform mobility operations (such as cell reselection) to move between NTN-RUs (and NTN cells) and TN-RUs (and TN cells).

[0104] Each component of the disassembled base station architecture 300 (including CU 310, DU 330, RU 340, near-RT RIC 370, non-RT RIC 350, and SMO frame 360) may include one or more interfaces or may be coupled to one or more interfaces for receiving or transmitting signals, such as data or information, via wired or wireless transmission media.

[0105] In some respects, the CU 310 can be logically divided into one or more CU user plane (CU-UP) units and one or more CU control plane (CU-CP) units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be deployed to communicate with one or more DU 330s for network control and signaling, as needed. 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 RU 340s. For example, the DU 330 may host various layers, such as the RLC layer, MAC layer, or one or more PHY layers (such as one or more high PHY layers or one or more low PHY layers). Each layer (which may also be referred to as a module) can be implemented using an interface for signaling to other layers (and modules) hosted by the DU 330, or for signaling to control functions hosted by the CU 310. Each RU 340 may implement lower-layer functionality. In some respects, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 340 can be controlled by the corresponding DU 330.

[0106] The SMO framework 360 supports RAN deployment and provisioning for both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 360 supports the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 360 can interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 350, and / or near-RT RIC 370. In some aspects, the SMO framework 360 can communicate with hardware aspects of the 4G RAN, 5G NR RAN, and / or 6G RAN (such as the Open eNB (O-eNB) 380) via the O1 interface. Additionally or alternatively, the SMO framework 360 can communicate directly with each of one or more RUs 340 via the corresponding O1 interface. In some deployments, this configuration enables each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0107] The non-RT RIC 350 may include or implement logic functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, and / or policy-based guidance of applications and / or features in the near-RT RIC 370. The non-RT RIC 350 may be coupled to or communicate with the near-RT RIC 370, such as via an A1 interface. The near-RT RIC 370 may include or implement logic functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 310s, one or more DU 330s, and / or O-eNBs to the near-RT RIC 370.

[0108] In some respects, to generate AI / ML models to be deployed in the near-RT RIC 370, the non-RT RIC 350 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 370 and may be received from non-network data sources or network functions at the SMO framework 360 or the non-RT RIC 350. In some examples, the non-RT RIC 350 or near-RT RIC 370 may modulate RAN behavior or performance. For example, the non-RT RIC 350 may monitor long-term trends and patterns of performance and may employ AI / ML models to perform corrective actions via the SMO framework 360 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0109] Figure 1 , Figure 2 or Figure 3 Network node 110, its controller / processor 240, UE 120, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies associated with UE capability updates during mobility operations or perform one or more operations associated with UE capability updates during mobility operations, as described in more detail elsewhere herein. For example, network node 110's controller / processor 240, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies associated with UE capability updates during mobility operations or perform one or more operations associated with UE capability updates during mobility operations, as described in more detail elsewhere herein. Figure 2 Any other component, CU 310, DU 330, or RU 340 may (alone or in combination with one or more other processors) perform or direct, for example... Figure 8 The process 800 Figure 9 The process 900 Figure 10 Process 1000 Figure 11The operation of process 1100 or other processes as described herein. Memory 242 may store data and program code for network node 110, CU 310, DU 330, or RU 340. Memory 282 may store data and program code for UE 120. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing a set of instructions (e.g., code or program code) for wireless communication. Memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). Memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). For example, the set of instructions may be executed by one or more processors of network node 110, UE 120, CU 310, DU 330, or RU 340 (e.g., directly, or after compilation, transformation, or interpretation). Figure 8 The process 800 Figure 9 The process 900 Figure 10 Process 1000 Figure 11 The process 1100 or other processes as described herein. In some examples, the execution instructions may include run instructions, transform instructions, compile instructions, and / or interpret instructions, etc.

[0110] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.

[0111] Figure 4A and Figure 4B These are illustrations of example 400, which illustrates regenerative satellite deployment in a non-terrestrial network, and example 410, which illustrates transparent satellite deployment.

[0112] like Figure 4A As shown, Example 400 illustrates a regenerative satellite deployment. In Example 400, UE 120 is served by satellite 420 via serving link 430. For example, satellite 420 may include network node 110 (e.g., network node 110a) or gNB. In some aspects, satellite 420 may be referred to as a non-terrestrial base station, a regenerative repeater, or an onboard processing repeater. In some aspects, satellite 420 may demodulate uplink radio frequency signals and may modulate baseband signals derived from uplink radio signals to generate downlink radio frequency transmissions. Satellite 420 may transmit downlink radio frequency signals over serving link 430. Satellite 420 may provide cell coverage for UE 120.

[0113] like Figure 4BAs shown, Example 410 illustrates a transparent satellite deployment, which may also be referred to as a bend-tube satellite deployment. In Example 410, UE 120 is served by satellite 440 via serving link 430. Satellite 440 may be a transparent satellite. Satellite 440 may relay signals received from gateway 450 via feeder link 460. For example, the satellite may receive uplink RF transmissions and may transmit downlink RF transmissions without demodulating the uplink RF transmissions. In some aspects, the satellite may convert the frequency of the uplink RF transmissions received on serving link 430 to the frequency of the uplink RF transmissions on feeder link 460, and may amplify and / or filter the uplink RF transmissions. In some aspects, UE 120 shown in Examples 400 and 410 may be associated with Global Navigation Satellite System (GNSS) capability or Global Positioning System (GPS) capability, but not all UEs have such capabilities. Satellite 440 may provide cell coverage for UE 120.

[0114] Serving link 430 may include a link between satellite 440 and UE 120, and may include one or more uplinks or downlinks. Feeder link 460 may include a link between satellite 440 and gateway 450, and may include one or more uplinks (e.g., from UE 120 to gateway 450) or downlinks (e.g., from gateway 450 to UE 120). Due to the movement of satellites 420 and 440 and the potential movement of UE 120, feeder link 460 and serving link 430 may each experience Doppler effects. These Doppler effects may be significantly greater than those in terrestrial networks. The Doppler effects on feeder link 460 may be compensated to some extent, but may still be associated with a certain amount of uncompensated frequency error. In addition, gateway 450 may be associated with residual frequency errors, and / or satellites 420 / 440 may be associated with onboard frequency errors. These sources of frequency errors may cause the downlink frequency received at UE 120 to deviate from the target downlink frequency.

[0115] As indicated above, Figure 4A and Figure 4B This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4A and Figure 4B The examples described are different.

[0116] Figure 5A and Figure 5B This is a diagram illustrating example 500 / 500' of mobility operations in terrestrial and non-terrestrial networks according to this disclosure. Figure 5AAs shown, a deployment 500 with both NTN and TN cells may include a first network node 110 providing TN cells and a second network node 110 providing NTN cells. In some examples, the first network node 110 and the second network node 110 may share a single MME 502 serving both TN and NTN cells. In some other examples, the first network node 110 may be associated with a first MME 502, and the second network node 110 may be associated with a second MME 504. In some examples, the second network node 110 may communicate with either MME 502 or MME 504 via a gateway (GW) 506 and / or a third network node 110. For example, the second network node 110 may be a non-terrestrial RU, and the third network node 110 may be a terrestrial DU or CU communicating with a non-terrestrial RU via GW 506.

[0117] like Figure 5B As shown, Example 500' includes UE 120, network node 110 (e.g., a TN network node), MME 504 (e.g., an NTN MME), and MME 502 (e.g., a TN MME). As indicated by reference numeral 520, UE 120 can perform mobility operations to move to network node 110 (e.g., from an NTN cell to a TN cell). For example, UE 120 can perform cell selection procedures, cell reselection procedures, radio link failure (RLF) procedures, or transitions between radio resource control (RRC) states (e.g., RRC inactive and RRC active), etc. While UE 120 is being transferred to network node 110, the MME 504 associated with the NTN cell can have UE capabilities for NTN Radio Access Technology (RAT), as indicated by reference numeral 522. For example, MME 504 can store a UE capability container associated with UE capability information for NTN RAT (e.g., the contents of a UE capability indicator or UE capability update indicator).

[0118] As in Figure 5BAs further illustrated by reference numeral 524, UE 120 can send a Tracking Area Update (TAU) message with UE capability updates. For example, UE 120 can trigger mobility operations for TN RAT by sending a TAU message with UE capability updates. As shown by reference numeral 526, network node 110 can send an indication of UE initialization to MME 502. MME 502 can determine whether MME 502 stores a UE capability container for UE 120, and based on the determination that MME 502 does not store a UE capability container for UE 120, MME 502 can send an initial context establishment request, as shown by reference numeral 528. For example, MME 502 can indicate to network node 110 that UE capability information does not exist at MME 502.

[0119] As in Figure 5B As further shown by reference numeral 530, network node 110 can send a context establishment response message to MME 502 in response to receiving an initial context establishment request message. Additionally or alternatively, as shown by reference numerals 532 and 534, network node 110 can request a UE capability report from UE 120 and receive the UE capability report from that UE. For example, UE 120 can send a UE capability update indicator identifying UE capabilities for TN RAT. As shown by reference numeral 536, the network node sends information identifying UE capability information to MME 502. MME 502 can use the UE capability information to establish a UE capability container for UE 120, as shown by reference numeral 538. Based on the UE capability container and associated UE context established by MME 502 for UE 120, UE 120 can (e.g., via network node 110) communicate uplink or downlink data with MME 502, as shown by reference numeral 540.

[0120] As in Figure 5BAs further illustrated by reference numeral 542, at a later time, UE 120 may determine to perform a mobility operation to move back to the NTN RAT. For example, UE 120 may determine to perform a cell reselection procedure, an RLF procedure, or an RRC state change procedure. As shown by reference numeral 544, UE 120 may send a TAU message with UE capability updates. For example, UE 120 may send a TAU message to trigger a mobility operation from the TN RAT to the NTN RAT. As shown by reference numeral 546, MME 504 may replace stored UE capabilities (e.g., UE capability information stored in the UE capability container for the NTN RAT by MME 504, as described with respect to reference numeral 522) with the UE capability information indicated in the TAU message. However, when the UE does not have any changes to the UE capabilities for the NTN RAT, the TAU message is conveying information already stored by MME 504. Furthermore, MME 504 is replacing existing UE capability information with new UE capability information that has not yet been changed.

[0121] As indicated above, Figure 5A and Figure 5B This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5A and Figure 5B The examples described are different.

[0122] The various aspects collectively relate to UE capability updates during mobility operations such as cell selection, cell reselection, or cell registration procedures. Some aspects more specifically involve the UE receiving an indication of whether the UE capability indicator is maintained after the UE switches from a first-type network (such as NTN) to a second-type network (such as TN) (and vice versa). In some aspects, by receiving an indication of whether the UE capability indicator is maintained, the UE can send a TAU message excluding the UE capability update indicator when switching back from a second-type network to a first-type network. In other words, the UE suppresses the transmission of the UE capability update indicator when it has already signaled to the MME that it continues to store the UE capability update indicator.

[0123] In some aspects, the UE can include an indicator in the TAU message that indicates whether the TAU message includes changes to UE capability information. When the UE indicates that the TAU message includes changes to UE capability information, the network node and / or MME can use the changes to UE capability information indicated in the TAU message to update the UE capability container. In contrast, when the UE indicates that the TAU message does not include changes to UE capability information, the network node and / or MME can use the UE capability information stored in the stored UE capability container to register the UE with the network in conjunction with mobility operations. In this example, the UE can include other information in the TAU message (e.g., in a field reserved for the UE capability update indicator), such as other control information that the UE will signal to the network node and / or MME.

[0124] Specific aspects of the subject matter described in this disclosure may be implemented to achieve one or more of the following potential improvements. In some examples, the described techniques can be used to reduce the signaling overhead associated with the UE sending UE capability update indicators by providing the UE with an indication that the MME maintains the UE capability container after the UE leaves the network type associated with the UE capability container. Additionally or alternatively, by providing the network node with an indication of whether the TAU message includes an update to the UE capability, the network node can determine whether to register the UE with the network cell using new UE capabilities or stored UE capabilities, thereby enabling the UE to successfully complete mobility operations.

[0125] Figure 6 This is an illustration of example 600 associated with maintaining a UE capability container during mobility operations according to this disclosure. Figure 6 As shown, Example 600 includes communication between network node 110, UE 120, and MME 605. In some aspects, network node 110 and MME 605 are associated with a TN. In other aspects, network node 110 and MME 605 are associated with an NTN. For example, when a transition occurs between a first-type network and a second-type network, the transition can be from TN to NTN or from NTN to TN.

[0126] In some respects, MME 605 can be specific to a particular type of network. For example, in an inter-MME mobility scenario, MME 605 can be specific to a first type of network (e.g., one of a TN or NTN), and another MME can be specific to a second type of network (e.g., the other of a TN or NTN). In other respects, MME 605 can be associated with multiple types of networks. For example, in an intra-MME mobility scenario, MME 605 can be associated with both a first type of network (e.g., one of a TN or NTN) and a second type of network (e.g., the other of a TN or NTN).

[0127] As in Figure 6 As further shown by reference numeral 650, UE 120 can receive an indication to MME 605 whether to store a UE capability container after a first mobility operation. For example, network node 110 can send an indication to MME 605 whether to maintain a UE capability container after UE 120 switches from a first-type network associated with a first-type UE capability container to a second-type network associated with a second-type UE capability container. In other words, when UE 120 is connected to the TN, UE 120 can receive an indication to MME 605 whether to maintain UE capability information for UE 120 for the TN after UE 120 is transferred to the NTN. Similarly, when UE 120 is connected to the NTN, UE 120 can receive an indication to MME 605 whether to maintain UE capability information for UE 120 for the NTN after UE 120 is transferred to the TN. The UE capability container can have a configured or specified format for storing UE capability information. For example, a UE capability container may include an information element ueCapabilityRAT-Container, which includes one or more fields for conveying UE capability information for an associated RAT (such as an NR RAT or any other RAT).

[0128] Although this document describes some aspects based on the UE capability container, it is conceivable that after UE 120 changes between network types, UE 120 may receive instructions from MME 605 to maintain UE capability information (or other information that may be signaled in mobility operation messages) in a format different from the UE capability container. For example, UE 120 may receive instructions from MME 605 to maintain values ​​of UE capabilities in a data structure.

[0129] In some respects, network node 110 can send an indication to MME 605 as to whether MME 605 maintains the UE capability container based on signaling received from MME 605. For example, MME 605 can instruct network node 110 to maintain the UE capability container, and network node 110 can send the indication to UE 120.

[0130] In some aspects, UE 120 may receive information instructing MME 605 to continue storing the UE capability container until UE 120 is disconnected. For example, when UE 120 is operating in an inter-MME mobility scenario, UE 120 may receive information instructing MME 605 to continue storing the UE capability container for a first-type network (e.g., TN) after the UE transitions to another MME associated with a second-type network (e.g., NTN). In some aspects, this instruction is network type specific. For example, UE 120 may receive a System Information (SIB) message (e.g., SIB Type 1 (SIB1)) indicating whether the UE capability container is stored for a specific type of network (e.g., NTN) across PLMNs. Additionally or alternatively, UE 120 may receive a per-PLMN instruction. For example, UE 120 may receive an instruction regarding whether a UE capability container is stored for a specific PLMN (and associated MME 605) after mobility operations. Additionally or alternatively, UE 120 may receive a per mobility operation message indication. For example, when UE 120 receives an attach accept message or TAU accept message associated with a particular mobility operation, as described below, the attach accept message or TAU accept message may include an indication that MME 605 will store the UE capability container after the particular mobility operation.

[0131] In some aspects, UE 120 can receive information instructing MME 605 to continue storing UE capability indicators for different types of RATs. For example, in an MME-based mobility scenario, network node 110 can provide an indication of whether MME 605 stores UE capability containers for TN RAT, NTN RAT, or both after a network type change. In other words, MME 605 can store UE capabilities used only for TN-to-NTN handovers, only for NTN-to-TN handovers, or for both types of handovers. In some aspects, UE 120 can receive this indication via bit indications in an SIB (e.g., SIB1), attach accept messages, or TAU accept messages, etc. For example, regarding SIB1, SIB1 may include option or non-critical information element extensions that may identify whether UE capabilities are retained and / or the period for which UE capabilities are retained.

[0132] In some respects, UE 120 may receive information indicating the time period associated with MME 605 maintaining the UE capability container. For example, network node 110 may instruct MME 605 to maintain the UE capability container for a specific number of seconds, time slots, frames, or another time interval after a mobility operation. In this example, UE 120 may initiate a timer in conjunction with a mobility operation (e.g., when UE 120 sends a TAU message to initiate a mobility operation) to determine whether MME 605 will still maintain the UE capability container when UE 120 attempts to switch back to a first-type network.

[0133] As in Figure 6 As further illustrated by reference numeral 652, UE 120 can transition from a first-type network to a second-type network. For example, UE 120 can transition from a TN to an NTN or vice versa. In some aspects, UE 120 can perform specific types of mobility operations, such as cell selection, cell reselection, cell registration, RLF or RRC state change, to transition between a first-type network and a second-type network. In some aspects, UE 120 can send a TAU message with a UE capability update indicator to trigger the transition. For example, as described in more detail above, UE 120 can send a TAU message to another network node 110 (e.g., a network node associated with a second-type network) to initiate a transition from a first-type network to a second-type network. In some aspects, MME 605 can set a timer associated with the UE capability container for UE 120. For example, after UE 120 disconnects from MME 605 (e.g., in an inter-MME mobility scenario) or changes between network types (e.g., in an intra-MME mobility scenario), MME 605 may start a timer associated with the UE capability container. After the timer expires and UE 120 does not return to MME 605 using an attach request or TAU request, MME 605 may delete the UE capability container (e.g., and the data storage resources may be reused to store other information, such as a UE capability container for another UE).

[0134] As in Figure 6As further illustrated by reference numeral 654, UE 120 may send a TAU message. For example, UE 120 may send a TAU message to network node 110 to trigger a transition from a second-type network back to a first-type network. In this example, UE 120 may transition from NTN back to TN or from TN back to NTN, etc. In some aspects, UE 120 may send a TAU message with a UE capability update indicator. For example, when UE 120 has not yet received an indication from MME 605 to store a UE capability container after mobility operations, UE 120 may send a UE capability update indicator. In this example, UE 120 sends a UE capability update indicator to network node 110 (e.g., to provide UE capability information to MME 605 to establish a UE context with the UE capability container from the first-type network). Additionally or alternatively, when UE 120 determines that the duration associated with MME 605 maintaining the UE capability container has expired, UE 120 may provide a UE capability update indicator in the TAU message.

[0135] In contrast, in some respects, UE 120 may send a TAU message that does not include the UE capability update indicator. For example, when UE 120 has received an indication from MME 605 to store the UE capability container after mobility operations, UE 120 may send a TAU message without including the UE capability update indicator. In this example, UE 120 may omit one or more bits from the TAU message, or may include other information in the TAU message (e.g., reusing one or more bits from the TAU message to transmit other control information). Additionally or alternatively, when UE 120 determines that the duration associated with MME 605 maintaining the UE capability container has not yet expired, UE 120 may omit including the UE capability update indicator in the TAU message. In some respects, UE 120 may use a timer to track the duration. For example, UE 120 may start a timer when leaving a Type 1 network transition. Additionally or alternatively, UE 120 may store an indicator of the time when UE 120 leaves a first type of network transition, and may use the current time to determine whether the amount of time elapsed exceeds a configured threshold.

[0136] As in Figure 6As further illustrated by reference numeral 654, UE 120 can switch back from a second type of network to a first type of network. For example, UE 120, network node 110, and / or MME 605 can use a TAU message to trigger mobility operations associated with switching UE 120 from NTN to TN or from TN to NTN. When UE 120 waives the inclusion of a UE capability update indicator in the TAU message, MME 605 can use the UE capability information stored in the maintained UE capability container to establish a UE context and / or enable network services for UE 120 on the first type of network. Additionally or alternatively, when UE 120 includes a UE capability update indicator in the TAU message, MME 605 can use the updated UE capability information to establish a UE context and / or enable network services for UE 120 on the first type of network.

[0137] As indicated above, Figure 6 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 6 The examples described are different.

[0138] Figure 7 This is a diagram illustrating example 700 associated with a UE capability change indication according to this disclosure. (See diagram for example...) Figure 7 As shown, Example 700 includes communication between UE 120, network node 110 and MME 705.

[0139] As in Figure 7 As further illustrated by reference numeral 750, UE 120, network node 110, and MME 705 can perform mobility operations. For example, UE 120 can send a TAU message to trigger a mobility operation, as shown by reference numeral 752. In some aspects, UE 120 may include a capability change indicator in the TAU message. For example, UE 120 may include an indication of whether the TAU message includes a UE capability update indication for identifying a change in the capabilities of UE 120. UE 120 may change its capabilities based on changes to power states (e.g., entering a power-saving mode or having a battery level below a threshold), changes to connectivity states (e.g., having a received or transmitted signal strength below a threshold), or software changes (e.g., a user selection to enable or disable capabilities), etc.

[0140] UE 120 may include an indication of whether the TAU message includes a UE capability update indication to identify a change relative to a stored UE capability. For example, when MME 705 stores a UE capability container (e.g., after a transition between network types, as described above), UE 120 may indicate whether UE 120 has changed its UE capability from previously reported and stored UE capabilities. In other words, UE 120 may report a UE capability, and MME 705 may store that UE capability after the UE transitions from a first-type network to a second-type network. When UE 120 returns from a second-type network to a first-type network, UE 120 may indicate whether the UE has changed its capability since reporting the UE capability. Network node 110 and / or MME 705 may interpret the TAU message based on a capability change indicator. For example, when a capability change indicator indicates that the UE capability has not changed, network node 110 and / or MME 705 may determine that UE 120 sent a TAU with a UE capability update indicator to trigger mobility operation (and did not update the UE capability container). Alternatively, when a capability change indicator indicates a change to a UE capability, network node 110 and / or MME 705 may determine to update the UE capability container using the new UE capability.

[0141] As in Figure 7 As further illustrated by reference numerals 754 and 756, UE 120 may selectively receive and send UE capability update indications. For example, when the TAU message includes an indication that the UE capability has changed, network node 110 may request an updated UE capability indicator, and UE 120 may send a UE capability report to network node 110. In this example, network node 110 and / or MME 705 may use the updated UE capability indicator to perform mobility operations and connect UE 120 to network services. Alternatively, when the capability change indicator indicates that the UE capability has not changed, network node 110 and UE 120 may discard the UE capability report, and MME 705 may use the stored UE capability to connect UE 120 to network services.

[0142] As indicated above, Figure 7 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 7 The examples described are different.

[0143] Figure 8 This is a diagram illustrating an example process 800 performed, for example, at a UE or a device of a UE, according to this disclosure. Example process 800 is an example in which a device or UE (e.g., UE 120) performs operations associated with a UE capability update (user equipment capability update during mobility operation) during mobility operation.

[0144] like Figure 8 As shown, in some aspects, process 800 may include: receiving from a first type of network an indication of whether a first UE capability container associated with the first type of network is stored after a first handover from a first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network (block 810). For example, a UE (e.g., using...) Figure 12 The communication manager 140 and / or receiving component 1202 depicted herein may receive from a first type of network an indication of whether a first UE capability container associated with the first type of network is stored after a first handover from a first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network and the other of the first type of network and the second type of network is a non-terrestrial network, as described above.

[0145] like Figure 8 As further shown, in some aspects, process 800 may include: receiving information identifying the duration for which the UE capability container is stored (box 820). For example, the UE (e.g., using...) Figure 12 The communication manager 140 and / or receiving component 1202 depicted herein can receive information identifying the duration for storing the UE capability container, as described above.

[0146] like Figure 8 As further shown, in some aspects, process 800 may include: selecting a cell for mobility operations (box 830). For example, the UE (e.g., using...) Figure 12 The communication manager 140 and / or selection component 1208 depicted herein may include: selecting a cell for mobility operations, as described above.

[0147] like Figure 8 Further, in some aspects, process 800 may include: sending a mobility operation message during a mobility operation associated with a second handover from a second type of network to a first type of network, wherein whether the mobility operation message includes a UE capability update indicator is based on an indication of whether a first UE capability container was stored after the first handover (box 840). For example, the UE (e.g., using...) Figure 12The communication manager 140 and / or the transmitting component 1204 depicted herein may transmit a mobility operation message during a mobility operation associated with a second handover from a second type of network to a first type of network, wherein whether the mobility operation message includes a UE capability update indicator is based on an indication of whether the first UE capability container was stored after the first handover, as described above.

[0148] 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 in this document.

[0149] In the first aspect, the mobility operation message is a tracking area update message.

[0150] In the second aspect, either alone or in combination with the first aspect, the instruction is received via at least one of the following: a system information block message; a network type-specific message; a public land mobile network-specific message; a tracking area update response message; or a combination thereof.

[0151] In a third aspect, receiving an indication of whether the first UE capability container is stored after the first handover, either alone or in combination with one or more of the first and second aspects, includes: receiving information identifying the duration for which the first UE capability container is stored, and whether the mobility operation message includes the first UE capability container based on the duration for which the first UE capability container is stored.

[0152] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, process 800 includes: selecting a cell for the mobility operation; identifying whether the duration has been exceeded for the cell; and generating a mobility operation message for the cell based on whether the duration has been exceeded for the cell, selectively including the UE capability indicator.

[0153] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the first type of network is associated with a first core network entity storing the first UE capability container, and the second type of network is associated with a second core network entity storing the second UE capability container, wherein the mobility operation is associated with a handover from the first core network entity to the second core network entity.

[0154] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the first type of network is associated with a core network entity storing the first UE capability container, and the second type of network is associated with the same core network entity storing the second UE capability container, wherein the mobility operation is associated with a handover of radio access technology associated with the same core network entity.

[0155] In the seventh aspect, receiving the indication of whether the first UE capability container is stored after the first handover, either alone or in combination with one or more of the first to sixth aspects, includes: receiving information identifying whether the indication is applied to the first type of network, the second type of network, or a combination thereof, and whether the mobility operation message includes the UE capability update indicator based on the information identifying whether the indication is applied to the first type of network, the second type of network, or a combination thereof, and based on the network type targeted by the mobility operation.

[0156] although Figure 8 An example box of process 800 is shown, but in some respects, process 800 may include... Figure 8 The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 800 may be executed in parallel.

[0157] Figure 9 This is a diagram illustrating an example process 900 performed, for example, at a UE or a device of a UE, according to this disclosure. Example process 900 is an example in which a device or UE (e.g., UE 120) performs an operation associated with a UE capability change indication.

[0158] like Figure 9 As shown, in some aspects, process 900 may include: sending a mobility operation message, the mobility operation message including an indication of whether the UE capability indicator identifies a change in UE capability or a mobility scenario of a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network (box 910). For example, the UE (e.g., using...) Figure 12The communication manager 140 and / or the transmitting component 1204 described herein can transmit a mobility operation message that includes an indication of whether the UE capability indicator identifies a change in UE capability or a mobility scenario of a configuration type between a first type network and a second type network, wherein one of the first type network and the second type network is a terrestrial network and the other of the first type network and the second type network is a non-terrestrial network, as described above.

[0159] like Figure 9 As further shown, in some aspects, process 900 may include: receiving a request for an update to the UE's capabilities (box 920). For example, the UE (e.g., using...) Figure 12 The communication manager 140 and / or receiving component 1202 depicted herein can receive information identifying the duration for storing the UE capability container, as described above.

[0160] like Figure 9 As further shown, in some aspects, process 900 may include: selectively sending a UE capability report to identify a change in UE capabilities based on whether the UE capability indicator identifies a change in UE capabilities or a mobility scenario (box 930). For example, the UE (e.g., using...) Figure 12 The communication manager 140 and / or the transmitting component 1204 described herein may selectively transmit a UE capability report to identify a change in UE capability, as described above, based on whether the UE capability indicator identifies a change in UE capability or a mobility scenario.

[0161] 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 in this document.

[0162] In a first aspect, process 900 includes: communicating via a target radio access technology associated with the mobility operation without sending a UE capability report, based on the UE capability indicator of the mobility scenario of the type of identification configuration.

[0163] In a second aspect, either alone or in combination with the first aspect, process 900 includes: receiving a request for a UE capability update based on a UE capability indicator that identifies the change in the UE capability; and sending the UE capability update to identify the change in the UE capability based on receiving the request.

[0164] although Figure 9 An example box of process 900 is shown, but in some respects, process 900 may include... Figure 9The boxes depicted in the diagram may be fewer, different, or arranged differently than additional boxes. Alternatively, two or more boxes in the process 900 may be executed in parallel.

[0165] Figure 10 This is a diagram illustrating an example process 1000 performed, for example, at a network node or a device of a network node, according to this disclosure. Example process 1000 is an example in which a device or network node (e.g., network node 110) performs operations associated with a UE capability update (user equipment capability update during mobility operation) during mobility operation.

[0166] like Figure 10 As shown, in some aspects, process 1000 may include: combining a first type of network to send an indication of whether a first UE capability container associated with the first type of network is stored after a first handover from a first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network (box 1010). For example, network nodes (e.g., using...) Figure 15 The communication manager 150 and / or the transmitting component 1504 described herein may be combined with a first type of network to transmit an indication of whether a first UE capability container associated with the first type of network is stored after a first handover from a first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network and the other of the first type of network and the second type of network is a non-terrestrial network, as described above.

[0167] like Figure 10 Further, in some aspects, process 1000 may include: sending information identifying the duration for storing the UE capability container (box 1020). For example, a network node (e.g., using...) Figure 15 The communication manager 150 and / or the transmitting component 1504 depicted herein can transmit information identifying the duration of the storage of the UE capability container, as described above.

[0168] like Figure 10 Further shown, in some aspects, process 1000 may include: receiving a mobility operation message during a mobility operation associated with a second handover from a second type of network to a first type of network, wherein whether the mobility operation message includes a UE capability update indicator is based on an indication of whether a first UE capability container was stored after the first handover (box 1030). For example, a network node (e.g., using...) Figure 15 The communication manager 150 and / or receiving component 1502 depicted herein may receive a mobility operation message during a mobility operation associated with a second handover from a second type of network to a first type of network, wherein whether the mobility operation message includes a UE capability update indicator is based on an indication of whether the first UE capability container was stored after the first handover, as described above.

[0169] 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 in this document.

[0170] In the first aspect, the mobility operation message is a tracking area update message.

[0171] In the second aspect, either alone or in combination with the first aspect, the instruction is sent via at least one of the following: a system information block message; a network type-specific message; a public land mobile network-specific message; a tracking area update response message; or a combination thereof.

[0172] In a third aspect, sending the indication of whether the first UE capability container is stored after the first handover, either alone or in combination with one or more of the first and second aspects, includes: sending information identifying the duration for which the first UE capability container is stored, and whether the mobility operation message includes the first UE capability container based on the duration for which the first UE capability container is stored.

[0173] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the first type of network is associated with a first core network entity storing the first UE capability container, and the second type of network is associated with a second core network entity storing the second UE capability container, wherein the mobility operation is associated with a handover from the first core network entity to the second core network entity.

[0174] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the first type of network is associated with a core network entity storing the first UE capability container, and the second type of network is associated with the same core network entity storing the second UE capability container, wherein the mobility operation is associated with the handover of radio access technology associated with the same core network entity.

[0175] In the sixth aspect, sending the indication of whether the first UE capability container is stored after the first handover, either alone or in combination with one or more of the first to fifth aspects, includes: sending information identifying whether the indication is applied to the first type of network, the second type of network, or a combination thereof, and whether the mobility operation message includes the UE capability update indicator based on the information identifying whether the indication is applied to the first type of network, the second type of network, or a combination thereof, and based on the network type targeted by the mobility operation.

[0176] although Figure 10 An example box of process 1000 is shown, but in some respects, process 1000 may include... Figure 10 The boxes depicted in the diagram are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in the process 1000 may be executed in parallel.

[0177] Figure 11 This is a diagram illustrating an example process 1100 performed, for example, at a network node or a device of a network node, according to this disclosure. Example process 1100 is an example in which a device or network node (e.g., network node 110) performs an operation associated with a UE capability change indication.

[0178] like Figure 11 As shown, in some aspects, process 1100 may include: receiving a mobility operation message, the mobility operation message including an indication of whether the UE capability indicator identifies a change in UE capability or a mobility scenario of a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network (box 1110). For example, network nodes (e.g., using...) Figure 15 The communication manager 150 and / or receiving component 1502 described herein can receive a mobility operation message that includes an indication of whether the UE capability indicator identifies a change in UE capability or a mobility scenario of a configuration type between a first type network and a second type network, wherein one of the first type network and the second type network is a terrestrial network and the other of the first type network and the second type network is a non-terrestrial network, as described above.

[0179] like Figure 11 As further shown, in some aspects, process 1100 may include: determining whether the UE capability indicator identifies a change to UE capabilities or a mobility scenario that identifies a type of configuration (box 1120). For example, a network node (e.g., using...) Figure 15The communication manager 150 and / or determination component 1508 described herein can determine whether the UE capability indicator identifies a change to the UE capability or a mobility scenario of a configuration type, as described above.

[0180] like Figure 11 As further shown, in some aspects, process 1100 may include: sending a request for an update to the UE's capabilities (box 1130). For example, a network node (e.g., using...) Figure 15 The communication manager 150 and / or receiving component 1504 depicted herein can send requests for UE capability updates, as described above.

[0181] like Figure 11 As further shown, in some aspects, process 1100 may include: receiving UE capability updates (box 1140). For example, a network node (e.g., using...) Figure 15 The communication manager 150 and / or receiving component 1502 depicted herein can receive UE capability updates, as described above.

[0182] like Figure 11 Further, in some aspects, process 1100 may include: based on whether the UE capability indicator identifies a change in UE capabilities or a mobility scenario, sending a mobility operation message using a received UE capability report identifying a change in UE capabilities or using stored UE capabilities (box 1150). For example, a network node (e.g., using...) Figure 15 The communication manager 150 and / or the transmitting component 1504 described herein can transmit a mobility operation message based on whether the UE capability indicator identifies a change to the UE capability or a mobility scenario, using a received UE capability report that identifies a change to the UE capability or using stored UE capabilities, as described above.

[0183] Process 1100 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 in this document.

[0184] In a first aspect, process 1100 includes: using a stored UE capability report to communicate via a target radio access technology associated with the mobility operation, based on a UE capability indicator for a mobility scenario of a type of identification configuration.

[0185] In a second aspect, either alone or in combination with the first aspect, process 1100 includes: sending a request for a UE capability update based on a UE capability indicator that identifies the change in the UE capability; and receiving the UE capability update based on sending the request to identify the change in the UE capability.

[0186] although Figure 11 An example box of process 1100 is shown, but in some respects, process 1100 may include... Figure 11 The boxes depicted herein are compared to additional boxes, fewer boxes, different boxes, or boxes arranged in a different manner. Additionally or alternatively, two or more boxes in the process 1100 may be executed in parallel.

[0187] Figure 12 This is a diagram of an example device 1200 for wireless communication according to the present disclosure. Device 1200 may be a UE, or a UE may include device 1200. In some aspects, device 1200 includes a receiving component 1202 and a transmitting component 1204 that can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1200 may use the receiving component 1202 and the transmitting component 1204 to communicate with another device 1206 (such as a UE, a base station, or another wireless communication device). As further shown, device 1200 may include a communication manager 140. Communication manager 140 may include one or more of a selection component 1208, an identification component 1210, or a generation component 1212, etc.

[0188] In some respects, device 1200 can be configured to perform the functions described herein. Figures 6 to 7 One or more operations described herein. Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein, such as Figure 8 The process 800 Figure 9 The process 900 or a combination thereof. In some respects, Figure 12 The illustrated device 1200 and / or one or more components may include a combination Figure 2 One or more components of the described UE. Additionally or alternatively, Figure 12 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

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

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

[0191] The receiving component 1202 can receive from a first-type network an indication of whether a first UE capability container associated with the first-type network was stored after a first handover from the first-type network associated with the first UE capability to a second-type network associated with a second UE capability container, wherein one of the first-type network and the second-type network is a terrestrial network, and the other of the first-type network and the second-type network is a non-terrestrial network. The transmitting component 1204 can transmit a mobility operation message during a mobility operation associated with a second handover from the second-type network to the first-type network, wherein whether the mobility operation message includes a UE capability update indicator is based on the indication of whether the first UE capability container was stored after the first handover.

[0192] Selection component 1208 can select the cell for mobility operation. Identification component 1210 can identify whether the duration for the cell has been exceeded. Generation component 1212 can generate a mobility operation message for the cell based on whether the duration for the cell has been exceeded, selectively including a UE capability indicator.

[0193] The transmitting component 1204 can transmit a mobility operation message, which includes an indication of whether the UE capability indicator identifies a change in UE capabilities or a mobility scenario involving a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network. The transmitting component 1204 can selectively transmit a UE capability report to identify a change in UE capabilities based on whether the UE capability indicator identifies a change in UE capabilities or a mobility scenario.

[0194] The receiving component 1202 and / or the transmitting component 1204 can communicate via a target radio access technology associated with mobility operations without sending a UE capability report, based on a UE capability indicator that identifies the type of mobility scenario configured. The receiving component 1202 can receive a request for a UE capability update based on a UE capability indicator that identifies a change in UE capabilities.

[0195] The sending component 1204 can send a UE capability update based on a received request to identify changes to the UE capabilities.

[0196] Figure 12 The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 12 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 12 The two or more components shown can be implemented within a single component, or Figure 12 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 12 The collection of (one or more) components shown is executable and described as being composed of Figure 12 The other set of components shown performs one or more functions.

[0197] Figure 13 This is an illustration of an example 1300 of a hardware implementation of a device 1305 employing a processing system 1310 according to the present disclosure. The device 1305 may be a UE or may be located at a UE (e.g., included in a UE).

[0198] Processing system 1310 can be implemented using a bus architecture represented overall by bus 1315. Bus 1315 may include any number of interconnect buses and bridges, depending on the specific application of processing system 1310 and overall design constraints. Bus 1315 links together various circuits including one or more processors and / or hardware components represented by processor 1320, illustrated components, and computer-readable medium / memory 1325. Bus 1315 may also link various other circuits, such as timing sources, peripheral devices, voltage regulators, and / or power management circuits.

[0199] Processing system 1310 may be coupled to one or more transceivers 1330. Transceiver 1330 is coupled to one or more antennas 1335. Transceiver 1330 provides components for communicating with various other devices via a transmission medium. Transceiver 1330 receives signals from one or more antennas 1335, extracts information from the received signals, and provides the extracted information to processing system 1310 (specifically, receiving component 1202). Furthermore, transceiver 1330 receives information from processing system 1310 (specifically, transmitting component 1204) and generates signals to be applied to one or more antennas 1335, at least in part, based on the received information.

[0200] Processing system 1310 includes one or more processors 1320 coupled to computer-readable medium / memory 1325. Processor 1320 is responsible for general processing, including executing software stored on computer-readable medium / memory 1325. When executed by processor 1320, the software causes processing system 1310 to perform the various functions described herein with respect to any particular device. Computer-readable medium / memory 1325 can also be used to store data manipulated by processor 1320 during software execution. Processing system also includes at least one of the illustrated components. These components may be software modules running in processor 1320, residing in / stored on computer-readable medium / memory 1325, one or more hardware modules coupled to processor 1320, or some combination thereof.

[0201] In some aspects, the processing system 1310 may be a component of the UE 120 and may include one or more memories (such as memory 282), and / or may include one or more processors (such as at least one of a TX MIMO processor 266, a receive (RX) processor 258, and / or a controller / processor 280). In some aspects, the apparatus 1305 for wireless communication includes: means for receiving from a first type of network an indication of whether a first UE capability container associated with the first type of network was stored after a first handover from the first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network; and means for transmitting a mobility operation message during a mobility operation associated with a second handover from the second type of network to the first type of network, wherein whether the mobility operation message includes a UE capability update indicator is based on the indication of whether the first UE capability container was stored after the first handover. In some aspects, the apparatus 1305 includes: components for receiving information identifying the duration for storing a first UE capability container; components for selecting a cell for mobility operation; components for identifying whether the duration for the cell has been exceeded; components for generating a mobility operation message for the cell based on whether the duration for the cell has been exceeded to selectively include a UE capability indicator; and / or components for receiving information identifying whether it is applied to a first type of network, a second type of network, or a combination thereof.

[0202] In some aspects, apparatus 1305 includes: components for transmitting a mobility operation message, the mobility operation message including an indication of whether a UE capability indicator identifies a change in UE capability or a mobility scenario of a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network and the other of the first type of network and the second type of network is a non-terrestrial network; and components for selectively transmitting a UE capability report to identify a change in UE capability based on whether the UE capability indicator identifies a change in UE capability or a mobility scenario. In some aspects, apparatus 1305 includes: components for communicating via a target radio access technology associated with mobility operation without transmitting a UE capability report based on a UE capability indicator identifying a mobility scenario of a configuration type; components for receiving a request for a UE capability update based on a UE capability indicator identifying a change in UE capability; and / or components for transmitting a UE capability update to identify a change in UE capability based on receiving a request.

[0203] The aforementioned components may be one or more of the aforementioned components of the processing system 1310 of the apparatus 1200 and / or apparatus 1305, which are configured to perform the functions stated by the aforementioned components. As described elsewhere herein, the processing system 1310 may include a TX MIMO processor 266, an RX processor 258, and / or a controller / processor 280. In one configuration, the aforementioned components may be the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280, which are configured to perform the functions and / or operations stated herein.

[0204] Figure 13 This is provided as an example. Other examples can be combined with it. Figure 13 The examples described are different.

[0205] Figure 14 This is an illustration of an example 1400 of a specific implementation of code and circuitry for device 1405 according to the present disclosure. Device 1405 may be a UE, or a UE may include device 1405.

[0206] like Figure 14 As shown, device 1405 may include circuitry (circuit 1420) for receiving an indication of whether a first UE capability container is stored after a mobility operation. For example, circuitry 1420 may enable device 1405 to receive an indication from a first type of network whether a first UE capability container associated with the first type of network is stored after a first handover from the first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network.

[0207] like Figure 14 As shown, apparatus 1405 may include code (code 1425) stored in computer-readable medium 1325 for receiving an indication of whether a first UE capability container has been stored after a mobility operation. For example, when executed by processor 1320, code 1425 may cause processor 1320 to cause transceiver 1330 to receive from a first type of network an indication of whether a first UE capability container associated with the first type of network has been stored after a first handover from the first type of network associated with the first UE capability to a second type of network associated with the second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network.

[0208] like Figure 14As shown, device 1405 may include circuitry (circuit 1430) for transmitting mobility operation messages. For example, circuitry 1430 may enable device 1405 to transmit mobility operation messages during a mobility operation associated with a second handover from a second type of network to a first type of network, wherein whether the mobility operation message includes a UE capability update indicator is based on an indication of whether a first UE capability container was stored after the first handover.

[0209] like Figure 14 As shown, apparatus 1405 may include code (code 1435) stored in computer-readable medium 1325 for transmitting mobility operation messages. For example, when executed by processor 1320, code 1435 may cause processor 1320 to cause transceiver 1330 to transmit a mobility operation message during a mobility operation associated with a second handover from a second type of network to a first type of network, wherein whether the mobility operation message includes a UE capability update indicator is based on an indication of whether a first UE capability container was stored after the first handover.

[0210] like Figure 14 As shown, device 1405 may include circuitry (circuit 1440) for sending an indication of whether a UE capability indicator identifies a change in UE capability. For example, circuitry 1440 may enable device 1405 to send a mobility operation message that includes an indication of whether the UE capability indicator identifies a change in UE capability or a mobility scenario of a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network.

[0211] like Figure 14 As shown, apparatus 1405 may include code (code 1445) stored in computer-readable medium 1325 for sending an indication of whether a UE capability indicator identifies a change in UE capability. For example, when executed by processor 1320, code 1445 may cause processor 1320 to cause transceiver 1330 to send a mobility operation message, which includes an indication of whether the UE capability indicator identifies a change in UE capability or a mobility scenario of a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network.

[0212] like Figure 14As shown, device 1405 may include circuitry (circuit 1450) for selectively sending UE capability reports. For example, circuitry 1450 may enable device 1405 to selectively send UE capability reports to identify changes in UE capabilities based on whether the UE capability indicator identifies a change in UE capabilities or a mobility scenario.

[0213] like Figure 14 As shown, apparatus 1405 may include code (code 1455) stored in computer-readable medium 1325 for selectively transmitting UE capability reports. For example, when executed by processor 1320, code 1455 may cause processor 1320 to cause transceiver 1330 to selectively transmit UE capability reports to identify changes in UE capabilities based on whether the UE capability indicator identifies a change in UE capability or a mobility scenario.

[0214] Figure 14 This is provided as an example. Other examples can be combined with it. Figure 14 The examples described are different.

[0215] Figure 15 This is a diagram of an example device 1500 for wireless communication according to the present disclosure. Device 1500 may be a network node, or a network node may include device 1500. In some aspects, device 1500 includes a receiving component 1502 and a transmitting component 1504 that can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1500 can use the receiving component 1502 and the transmitting component 1504 to communicate with another device 1506 (such as a UE, a base station, or another wireless communication device). As further shown, device 1500 may include a communication manager 150. The communication manager 150 may include a determining component 1508, etc.

[0216] In some respects, device 1500 can be configured to perform the functions described herein. Figures 6 to 7 One or more operations described herein. Additionally or alternatively, the apparatus 1500 may be configured to perform one or more processes described herein, such as Figure 10 Process 1000 Figure 11 The process 1100 or a combination thereof. In some respects, Figure 15 The illustrated device 1500 and / or one or more components may include a combination Figure 2 One or more components of the described network node. Additionally or alternatively, Figure 15 One or more components shown can be combined Figure 2Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0217] Receiver 1502 may receive communications from device 1506, such as reference signals, control information, data communications, or combinations thereof. Receiver 1502 may provide the received communications to one or more other components of device 1500. In some aspects, receiver 1502 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 1500. In some aspects, receiver 1502 may include combinations of... Figure 2 The described network node includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0218] Transmitting component 1504 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1506. In some aspects, one or more other components of device 1500 may generate communications and provide the generated communications to transmitting component 1504 for transmission to device 1506. In some aspects, transmitting component 1504 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 device 1506. In some aspects, transmitting component 1504 may include combinations of... Figure 2 The described network node includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1504 may co-located with the receive component 1502 in one or more transceivers.

[0219] The transmitting component 1504 can transmit an indication, in conjunction with a first type of network, of whether a first UE capability container associated with the first type of network was stored after a first handover from the first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network. The receiving component 1502 can receive a mobility operation message during a mobility operation associated with a second handover from the second type of network to the first type of network, wherein whether the mobility operation message includes a UE capability update indicator is based on the indication of whether the first UE capability container was stored after the first handover.

[0220] The receiving component 1502 can receive a mobility operation message, which includes an indication of whether the UE capability indicator identifies a change in UE capabilities or a mobility scenario involving a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network. The sending component 1504 can send the mobility operation message based on whether the UE capability indicator identifies a change in UE capabilities or a mobility scenario, using a received UE capability report indicating a change in UE capabilities or using stored UE capabilities.

[0221] The transmitting component 1504 and / or the receiving component 1502 can communicate via a target radio access technology associated with mobility operations, based on a UE capability indicator that identifies the type of mobility scenario configured.

[0222] The transmitting component 1504 can send a request for a UE capability update based on a UE capability indicator that identifies a change in UE capabilities. The receiving component 1502 can receive a UE capability update that identifies a change in UE capabilities based on the sending request. The determining component 1508 can determine whether the UE capability update indicator identifies a change in UE capabilities.

[0223] Figure 15 The number and arrangement of components shown are provided as an example. In reality, they can exist in... Figure 15 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 15 The two or more components shown can be implemented within a single component, or Figure 15 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 15 The collection of (one or more) components shown is executable and described as being composed of Figure 15The other set of components shown performs one or more functions.

[0224] Figure 16 This is an illustration of an example 1600 of a hardware implementation of a device 1605 employing a processing system 1610 according to the present disclosure. Device 1605 may be a network node or may be located at a network node (e.g., included in a network node).

[0225] Processing system 1610 can be implemented using a bus architecture represented overall by bus 1615. Bus 1615 may include any number of interconnect buses and bridges, depending on the specific application of processing system 1610 and overall design constraints. Bus 1615 links together various circuits including one or more processors and / or hardware components represented by processor 1620, illustrated components, and computer-readable medium / memory 1625. Bus 1615 may also link various other circuits, such as timing sources, peripheral devices, voltage regulators, and / or power management circuits.

[0226] The processing system 1610 may be coupled to one or more transceivers 1630. The transceiver 1630 is coupled to one or more antennas 1635. The transceiver 1630 provides components for communicating with various other devices via a transmission medium. The transceiver 1630 receives signals from the one or more antennas 1635, extracts information from the received signals, and provides the extracted information to the processing system 1610 (specifically, the receiving component 1502). Furthermore, the transceiver 1630 receives information from the processing system 1610 (specifically, the transmitting component 1504) and generates signals to be applied to the one or more antennas 1635, at least in part, based on the received information.

[0227] Processing system 1610 includes one or more processors 1620 coupled to computer-readable medium / memory 1625. Processor 1620 is responsible for general processing, including executing software stored on computer-readable medium / memory 1625. When executed by processor 1620, the software causes processing system 1610 to perform the various functions described herein with respect to any particular device. Computer-readable medium / memory 1625 can also be used to store data manipulated by processor 1620 during software execution. Processing system also includes at least one of the illustrated components. These components may be software modules running in processor 1620, residing in / stored on computer-readable medium / memory 1625, one or more hardware modules coupled to processor 1620, or some combination thereof.

[0228] In some aspects, the processing system 1610 may be a component of the network node 110 and may include one or more memories (such as memory 242), and / or may include one or more processors (such as at least one of TX MIMO processor 216, RX processor 238, and / or controller / processor 240). In some aspects, the apparatus 1605 for wireless communication includes: components for transmitting an indication, in conjunction with a first type of network, whether a first UE capability container associated with the first type of network is stored after a first handover from the first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network; and components for receiving a mobility operation message during mobility operation associated with a second handover from the second type of network to the first type of network, wherein whether the mobility operation message includes a UE capability update indicator is based on the indication of whether the first UE capability container was stored after the first handover. In some aspects, the apparatus 1605 includes: a component for transmitting information identifying the duration for storing the first UE capability container; and / or a component for transmitting information identifying whether it is applied to a first type of network, a second type of network, or a combination thereof.

[0229] In some aspects, apparatus 1605 includes: components for receiving a mobility operation message, the mobility operation message including an indication that a UE capability indicator identifies either a change in UE capabilities or a mobility scenario of a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network; and components for transmitting the mobility operation message using a received UE capability report indicating a change in UE capabilities or using stored UE capabilities based on whether the UE capability indicator identifies a change in UE capabilities or a mobility scenario. In some aspects, apparatus 1605 includes: components for communicating via a target radio access technology associated with mobility operation using a stored UE capability report based on a UE capability indicator indicating a mobility scenario of a configuration type; components for transmitting a request for a UE capability update based on a UE capability indicator indicating a change in UE capabilities; and / or components for receiving a UE capability update based on the transmission request to indicate a change in UE capabilities.

[0230] The aforementioned components may be one or more of the aforementioned components of the processing system 1610 of the apparatus 1500 and / or apparatus 1605, which are configured to perform the functions stated by the aforementioned components. As described elsewhere herein, the processing system 1610 may include a TX MIMO processor 216, a receiver processor 238, and / or a controller / processor 240. In one configuration, the aforementioned components may be the TX MIMO processor 216, the receiver processor 238, and / or the controller / processor 240, which are configured to perform the functions and / or operations stated herein.

[0231] Figure 16 This is provided as an example. Other examples can be combined with it. Figure 16 The examples described are different.

[0232] Figure 17 This is a diagram illustrating an example 1700 of a specific implementation of the code and circuitry for device 1705 according to the present disclosure. Device 1705 may be a network node, or a network node may include device 1705.

[0233] like Figure 17 As shown, apparatus 1705 may include circuitry (circuit 1720) for transmitting an indication of whether a first UE capability container is stored after a mobility operation. For example, circuitry 1720 may enable apparatus 1705 to transmit an indication of whether a first UE capability container associated with a first type of network is stored after a first handover from a first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network.

[0234] like Figure 17 As shown, apparatus 1705 may include code (code 1725) stored in computer-readable medium 1625 for transmitting an indication of whether a first UE capability container has been stored after a mobility operation. For example, when executed by processor 1620, code 1725 may cause processor 1620 to cause transceiver 1630 to transmit an indication of whether a first UE capability container associated with a first type of network has been stored after a first handover from a first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network.

[0235] like Figure 17As shown, device 1705 may include circuitry (circuit 1730) for receiving mobility operation messages. For example, circuitry 1730 may enable device 1705 to receive mobility operation messages during a mobility operation associated with a second handover from a second type of network to a first type of network, wherein whether the mobility operation message includes a UE capability update indicator is based on an indication of whether a first UE capability container was stored after the first handover.

[0236] like Figure 17 As shown, apparatus 1705 may include code (code 1735) stored in computer-readable medium 1625 for receiving mobility operation messages. For example, when executed by processor 1620, code 1735 may cause processor 1620 to cause transceiver 1630 to receive mobility operation messages during a mobility operation associated with a second handover from a second type of network to a first type of network, wherein whether the mobility operation message includes a UE capability update indicator is based on an indication of whether a first UE capability container was stored after the first handover.

[0237] like Figure 17 As shown, device 1705 may include circuitry (circuit 1740) for receiving an indication of whether a UE capability indicator identifies a change in UE capability. For example, circuitry 1740 may enable device 1705 to receive a mobility operation message that includes an indication of whether the UE capability indicator identifies a change in UE capability or a mobility scenario of a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network.

[0238] like Figure 17 As shown, apparatus 1705 may include code (code 1745) stored in computer-readable medium 1625 for receiving an indication of whether a UE capability indicator identifies a change in UE capability. For example, when executed by processor 1620, code 1745 may cause processor 1620 to cause transceiver 1630 to receive a mobility operation message, which includes an indication of whether the UE capability indicator identifies a change in UE capability or a mobility scenario of a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network.

[0239] like Figure 17As shown, device 1705 may include circuitry (circuit 1750) for sending mobility operation messages. For example, circuitry 1750 may enable device 1705 to send mobility operation messages based on whether the UE capability indicator identifies a change in UE capability or a mobility scenario, using a received UE capability report that identifies a change in UE capability or using stored UE capabilities.

[0240] like Figure 17 As shown, apparatus 1705 may include code (code 1755) stored in computer-readable medium 1625 for transmitting mobility operation messages. For example, when executed by processor 1620, code 1755 may cause processor 1620 to cause transceiver 1630 to transmit mobility operation messages based on whether the UE capability indicator identifies a change in UE capability or a mobility scenario, using a received UE capability report indicating a change in UE capability or using stored UE capabilities.

[0241] Figure 17 This is provided as an example. Other examples can be combined with it. Figure 17 The examples described are different.

[0242] The following provides an overview of some aspects of this disclosure:

[0243] Aspect 1: A method of wireless communication performed by a user equipment (UE), the method comprising: receiving from a first type of network an indication of whether a first UE capability container associated with the first type of network is stored after a first handover from the first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network; and transmitting a mobility operation message during a mobility operation associated with a second handover from the second type of network to the first type of network, wherein the mobility operation message includes a UE capability update indicator based on the indication of whether the first UE capability container was stored after the first handover.

[0244] Aspect 2: According to the method of aspect 1, the mobility operation message is a tracking area update message.

[0245] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the indication is received via at least one of the following: a system information block message; a network type specific message; a public land mobile network specific message; a tracking area update response message; or a combination thereof.

[0246] Aspect 4: The method according to any one of Aspects 1 to 3, wherein receiving the indication of whether the first UE capability container is stored after the first handover includes: receiving information identifying the duration for which the first UE capability container is stored, and wherein whether the mobility operation message includes the first UE capability container is based on the duration for which the first UE capability container is stored.

[0247] Aspect 5: According to the method of aspect 4, the method further includes: selecting a cell for the mobility operation; identifying whether the duration has been exceeded for the cell; and generating the mobility operation message for the cell based on whether the duration has been exceeded for the cell to selectively include the UE capability indicator.

[0248] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the first type of network is associated with a first core network entity storing the first UE capability container, and the second type of network is associated with a second core network entity storing the second UE capability container, and wherein the mobility operation is associated with a handover from the first core network entity to the second core network entity.

[0249] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the first type of network is associated with a core network entity storing the first UE capability container, and the second type of network is associated with the same core network entity storing the second UE capability container, and wherein the mobility operation is associated with the handover of a radio access technology associated with the same core network entity.

[0250] Aspect 8: The method according to any one of Aspects 1 to 7, wherein receiving the indication as to whether the first UE capability container is stored after the first handover comprises: receiving information identifying whether the indication is applied to a first type of network, a second type of network, or a combination thereof, and wherein whether the mobility operation message includes the UE capability update indicator is based on the information identifying whether the indication is applied to a first type of network, a second type of network, or a combination thereof, and based on the network type targeted by the mobility operation.

[0251] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the indication includes a value for indicating that the first UE capability container is stored after the first handover; and wherein the mobility operation message does not include the UE capability update indicator based on the indication including the value for indicating that the first UE capability container is stored.

[0252] Aspect 10: The method according to any one of Aspects 1 to 8, wherein the indication includes a value for indicating that the first UE capability container was not stored after the first handover; and wherein the mobility operation message includes the UE capability update indicator based on the indication including the value for indicating that the first UE capability container was stored.

[0253] Aspect 11: A method of wireless communication performed by a user equipment (UE), the method comprising: sending a mobility operation message, the mobility operation message including an indication of whether a UE capability indicator identifies a change to UE capabilities or a mobility scenario of a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network and the other of the first type of network and the second type of network is a non-terrestrial network; and selectively sending a UE capability report to identify the change to UE capabilities based on whether the UE capability indicator identifies a change to the UE capabilities or the mobility scenario.

[0254] Aspect 12: The method according to aspect 11, the method further comprising: communicating via a target radio access technology associated with the mobility operation without sending the UE capability report based on the UE capability indicator identifying the type of mobility scenario of the configuration.

[0255] Aspect 13: The method according to any one of Aspects 11 to 12, the method further comprising: receiving a request for a UE capability update based on a UE capability indicator that identifies the change to the UE capability; and sending the UE capability update to identify the change to the UE capability based on receiving the request.

[0256] Aspect 14: A method of wireless communication performed by a network node, the method comprising: transmitting an indication, in conjunction with a first type of network, whether a first UE capability container associated with the first type of network is stored after a first handover from the first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network; and receiving a mobility operation message during a mobility operation associated with a second handover from the second type of network to the first type of network, wherein the mobility operation message includes a UE capability update indicator based on the indication of whether the first UE capability container was stored after the first handover.

[0257] Aspect 15: According to the method of aspect 14, the mobility operation message is a tracking area update message.

[0258] Aspect 16: The method according to any one of Aspects 14 to 15, wherein the indication is sent via at least one of: a system information block message; a network type specific message; a public land mobile network specific message; a tracking area update response message; or a combination thereof.

[0259] Aspect 17: The method according to any one of Aspects 14 to 16, wherein sending the indication of whether the first UE capability container is stored after the first handover comprises: sending information identifying the duration for which the first UE capability container is stored, and wherein whether the mobility operation message includes the first UE capability container is based on the duration for which the first UE capability container is stored.

[0260] Aspect 18: The method according to any one of Aspects 14 to 17, wherein the first type of network is associated with a first core network entity storing the first UE capability container, and the second type of network is associated with a second core network entity storing the second UE capability container, and wherein the mobility operation is associated with a handover from the first core network entity to the second core network entity.

[0261] Aspect 19: The method according to any one of Aspects 14 to 18, wherein the first type of network is associated with a core network entity storing the first UE capability container, and the second type of network is associated with the same core network entity storing the second UE capability container, and wherein the mobility operation is associated with a handover of a radio access technology associated with the same core network entity.

[0262] Aspect 20: The method according to any one of Aspects 14 to 19, wherein sending the indication on whether the first UE capability container is stored after the first handover comprises: sending information identifying whether the indication is applied to a first type of network, a second type of network, or a combination thereof, and wherein whether the mobility operation message includes the UE capability update indicator is based on the information identifying whether the indication is applied to a first type of network, a second type of network, or a combination thereof, and based on the network type targeted by the mobility operation.

[0263] Aspect 21: The method according to any one of Aspects 14 to 20, wherein the indication includes a value for indicating that the first UE capability container is stored after the first handover; and wherein the mobility operation message does not include the UE capability update indicator based on the indication including the value for indicating that the first UE capability container is stored.

[0264] Aspect 22: The method according to any one of Aspects 14 to 20, wherein the indication includes a value for indicating that the first UE capability container was not stored after the first handover; and wherein the mobility operation message includes the UE capability update indicator based on the indication including the value for indicating that the first UE capability container was stored.

[0265] Aspect 23: A method for wireless communication performed by a network node, the method comprising: receiving a mobility operation message, the mobility operation message including an indication of whether a UE capability indicator identifies a change to a UE capability or a mobility scenario of a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network and the other of the first type of network and the second type of network is a non-terrestrial network; and, based on whether the UE capability indicator identifies a change to the UE capability or the mobility scenario, sending the mobility operation message using a received UE capability report indicating the change to the UE capability or using stored UE capabilities.

[0266] Aspect 24: According to the method of aspect 23, the method further includes: using a stored UE capability report to communicate via a target radio access technology associated with the mobility operation, based on the UE capability indicator that identifies the type of mobility scenario of the configuration.

[0267] Aspect 25: The method according to any one of Aspects 23 to 24, the method further comprising: sending a request for a UE capability update based on a UE capability indicator that identifies the change to the UE capability; and receiving the UE capability update based on sending the request to identify the change to the UE capability.

[0268] Aspect 26: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 1 to 25.

[0269] Aspect 27: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 1 to 25.

[0270] Aspect 28: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 25.

[0271] Aspect 29: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the methods described in one or more of aspects 1 to 25.

[0272] Aspect 30: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 25.

[0273] Aspect 31: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 25.

[0274] Aspect 32: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 25.

[0275] Aspect 33: A User Equipment (UE) comprising: a processing system including processor circuitry and memory circuitry storing code and coupled to the processor circuitry, the processing system being configured to cause the UE to: receive from a first type of network an indication of whether a first UE capability container associated with the first type of network was stored after a first handover from the first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network and the other of the first type of network and the second type of network is a non-terrestrial network; and transmit a mobility operation message during a mobility operation associated with a second handover from the second type of network to the first type of network, wherein the mobility operation message includes a UE capability update indicator based on the indication of whether the first UE capability container was stored after the first handover.

[0276] Aspect 34: A user equipment (UE) comprising: a processing system including processor circuitry and memory circuitry storing code and coupled to the processor circuitry, the processing system being configured to cause the UE to: send a mobility operation message including an indication of whether a UE capability indicator identifies a change in UE capability or a mobility scenario of a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network and the other of the first type of network and the second type of network is a non-terrestrial network; and selectively send a UE capability report to identify the change in UE capability based on whether the UE capability indicator identifies a change in UE capability or the mobility scenario.

[0277] Aspect 35: A network node comprising: a processing system including processor circuitry and memory circuitry storing code and coupled to the processor circuitry, the processing system being configured to cause the network node to: transmit an indication, in conjunction with a first type of network, whether a first UE capability container associated with the first type of network is stored after a first handover from the first type of network associated with the first UE capability to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network and the other of the first type of network and the second type of network is a non-terrestrial network; and receive a mobility operation message during a mobility operation associated with a second handover from the second type of network to the first type of network, wherein the mobility operation message includes a UE capability update indicator based on the indication of whether the first UE capability container was stored after the first handover.

[0278] Aspect 36: A network node comprising: a processing system including processor circuitry and memory circuitry storing code and coupled to the processor circuitry, the processing system being configured to cause the network node to: receive a mobility operation message, the mobility operation message including an indication of whether a UE capability indicator identifies a change to a UE capability or a mobility scenario of a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network and the other of the first type of network and the second type of network is a non-terrestrial network; and, based on whether the UE capability indicator identifies a change to the UE capability or the mobility scenario, send the mobility operation message using a received UE capability report indicating the change to the UE capability or using stored UE capabilities.

[0279] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made based on the foregoing disclosure, or from various forms of practice.

[0280] As used herein, the term "component" is intended to be broadly interpreted as hardware or a combination of hardware and at least one of software or firmware. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a "processor" is implemented in hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein may be implemented in various forms of hardware or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods is not limited in any way. Therefore, the operation and behavior of these systems or methods are described herein without reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed to implement these systems or methods, at least in part, based on the description herein. Unless otherwise stated, a component configured to perform a function means that the component has the capability to perform that function, but it is not required that the component actually performs that function.

[0281] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0282] As used in this article, the phrase “at least one of” in a list of items refers to any combination of these items, including a single member. As an example, “at least one of the following: a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with multiple of the same element (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).

[0283] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are used interchangeably with “one or more.” Similarly, as used herein, the article “the” is intended to include one or more items mentioned in connection with the article “the” and is used interchangeably with “one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and are used interchangeably with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Moreover, as used herein, the terms “having” and similar terms are intended as open-ended terms that do not limit the elements they modify (e.g., “having” A may also have B). Additionally, the phrase “based on” is intended to mean “based on or otherwise related to” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used consecutively and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “either of the two” or “only one of them”). It should be understood that “one or more” is equivalent to “at least one”.

[0284] Although specific combinations of features are set forth in the claims or disclosed in the description, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically stated in the claims or disclosed in the description. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors coupled to the one or more memories, the one or more processors being configured to cause the UE to: Receive an indication from a first type of network regarding whether a first UE capability container associated with the first type of network is stored after a first handover from the first type of network associated with the first UE capability container to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network; and A mobility operation message is sent during a mobility operation associated with a second handover from a network of the second type to a network of the first type, wherein the mobility operation message includes a UE capability update indicator based on an indication of whether the first UE capability container was stored after the first handover.

2. The apparatus of claim 1, wherein the mobility operation message is a tracking area update message.

3. The apparatus of claim 1, wherein the instruction is received via at least one of the following: System information block message, Network type specific messages, Public terrestrial mobile network specific messages, Track the region update response message, or Their combination.

4. The apparatus of claim 1, wherein, in order for the UE to receive the indication as to whether the first UE capability container was stored after the first handover, the one or more processors are configured to: The receiver identifies the duration of the first UE capability container and stores the information. Whether the mobility operation message includes the first UE capability container is based on the duration used to store the first UE capability container.

5. The apparatus of claim 4, wherein the one or more processors are further configured to cause the UE to: Select the cell for the mobility operation; The identifier indicates whether the duration has exceeded for the cell; and Based on whether the cell has exceeded the duration, the mobility operation message is generated for the cell to selectively include the UE capability update indicator.

6. The apparatus of claim 1, wherein the first type of network is associated with a first core network entity storing the first UE capability container, and the second type of network is associated with a second core network entity storing the second UE capability container, and wherein the mobility operation is associated with a handover from the first core network entity to the second core network entity.

7. The apparatus of claim 1, wherein the first type of network is associated with a core network entity storing the first UE capability container, and the second type of network is associated with the same core network entity storing the second UE capability container, and wherein the mobility operation is associated with a handover of a radio access technology associated with the same core network entity.

8. The apparatus of claim 1, wherein, in order for the UE to receive the indication as to whether the first UE capability container was stored after the first handover, the one or more processors are configured to cause the UE to: Receive information identifying whether the indication is applied to the first type of network, the second type of network, or a combination thereof, and Whether the mobility operation message includes the UE capability update indicator is based on the information used to identify whether the indicator is applied to the first type of network, the second type of network, or a combination thereof, and based on the network type targeted by the mobility operation.

9. The apparatus of claim 1, wherein the one or more processors are individually or jointly configured to cause the UE to: Receive, from the first type of network, an indication of whether the first UE capability container associated with the first type of network was stored after a first handover from the first type of network associated with the first UE capability container to the second type of network associated with the second UE capability container, wherein one of the first type of network and the second type of network is the terrestrial network, and the other of the first type of network and the second type of network is the non-terrestrial network; and The mobility operation message is sent during the mobility operation associated with the second handover from the second type of network to the first type of network, wherein the mobility operation message includes the UE capability update indicator based on the indication of whether the first UE capability container was stored after the first handover.

10. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors coupled to the one or more memories, the one or more processors being configured to cause the UE to: Send a mobility operation message, the mobility operation message including an indication of whether the UE capability indicator identifies a change in UE capability or a mobility scenario of a configuration type between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network; as well as Depending on whether the UE capability indicator identifies a change to the UE capability or a mobility scenario, a UE capability report is selectively sent to identify the change to the UE capability.

11. The apparatus of claim 10, wherein the one or more processors are further configured to cause the UE to: Based on the UE capability indicator that identifies the type of mobility scenario of the configuration, communication is conducted via a target radio access technology associated with mobility operations without sending the UE capability report.

12. The apparatus of claim 10, wherein the one or more processors are further configured to cause the UE to: The request for a UE capability update is received based on the UE capability indicator that identifies the change in the UE capability; and Upon receiving the request, the UE capability update is sent to identify the change to the UE capability.

13. The apparatus of claim 10, wherein the one or more processors are individually or jointly configured to cause the UE to: Send the mobility operation message, the mobility operation message including an indication of whether the UE capability indicator identifies a change to the UE capability or a mobility scenario of the type of configuration between a first type of network and a second type of network, wherein one of the first type of network and the second type of network is the terrestrial network, and the other of the first type of network and the second type of network is the non-terrestrial network; and Depending on whether the UE capability indicator identifies a change to the UE capability or a mobility scenario, the UE capability report is selectively sent to identify the change to the UE capability.

14. An apparatus for wireless communication at a network node, the apparatus comprising: One or more memory units; and One or more processors coupled to the one or more memories, the one or more processors being configured to cause the network node to: The system combines a first type of network to send an indication of whether a first UE capability container associated with the first type of network is stored after a first handover from the first type of network associated with the first UE capability container to a second type of network associated with a second UE capability container, wherein one of the first type of network and the second type of network is a terrestrial network, and the other of the first type of network and the second type of network is a non-terrestrial network; and A mobility operation message is received during a mobility operation associated with a second handover from a network of the second type to a network of the first type, wherein the mobility operation message includes a UE capability update indicator based on an indication of whether the first UE capability container was stored after the first handover.

15. The apparatus of claim 14, wherein the mobility operation message is a tracking area update message.

16. The apparatus of claim 14, wherein the instruction is transmitted via at least one of the following: System information block message, Network type specific messages, Public terrestrial mobile network specific messages, Track the region update response message, or Their combination.

17. The apparatus of claim 14, wherein, in order for the network node to send the indication as to whether the first UE capability container was stored after the first handover, the one or more processors are configured to cause the network entity to: Send information identifying the duration of the first UE capability container, and Whether the mobility operation message includes the first UE capability container is based on the duration used to store the first UE capability container.

18. The apparatus of claim 14, wherein the first type of network is associated with a first core network entity storing the first UE capability container, and the second type of network is associated with a second core network entity storing the second UE capability container, and wherein the mobility operation is associated with a handover from the first core network entity to the second core network entity.

19. The apparatus of claim 14, wherein the first type of network is associated with a core network entity storing the first UE capability container, and the second type of network is associated with the same core network entity storing the second UE capability container, and wherein the mobility operation is associated with a handover of a radio access technology associated with the same core network entity.

20. The apparatus of claim 14, wherein, in order for the network node to send the indication as to whether the first UE capability container was stored after the first handover, the one or more processors are configured to cause the network node to: Send information identifying whether the indication applies to the first type of network, the second type of network, or a combination thereof, and Whether the mobility operation message includes the UE capability update indicator is based on the information identifying whether the indicator is applied to the first type of network, the second type of network, or a combination thereof, and based on the network type targeted by the mobility operation.

Images