Buffer release for inter-satellite link transitions

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a wireless communication device may obtain, at an access stratum (AS) layer, an indication of inter-satellite link (ISL) activation that will occur at an activation time. The wireless communication device may receive a communication. The wireless communication device may buffer the communications in a buffer at the AS layer. The wireless communication device may release the communications from the buffer to an upper protocol layer at a release rate that changes between a transition start time and the activation time. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. Patent Application No. 17 / 932,951, filed on September 16, 2022, entitled “BUFFER RELEASE FOR INTER-SATELLITE LINK TRANSITION” and assigned to the assignee of this application. The disclosure of the prior application is considered a part of and incorporated by reference into this patent application. Background Art

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for communications involving inter-satellite links.

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth or transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

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

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

[0007] Some aspects described herein relate to a method of wireless communication performed by a wireless communication device. The method may include obtaining, at an access stratum (AS) layer, an indication of an inter-satellite link (ISL) activation that will occur at an activation time. The method may include receiving the communications. The method may include buffering the communications in a buffer at the AS layer. The method may include releasing the communications from the buffer to an upper protocol layer at a release rate that varies between a transition start time and the activation time.

[0008] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include obtaining, at an AS layer, an indication of an ISL deactivation that will occur at a deactivation time. The method may include buffering communications in a buffer. The method may include releasing the communications from the buffer at a release rate that varies between the deactivation time and a transition end time. The method may include sending the communications.

[0009] Some aspects described herein relate to a wireless communication device for wireless communication. The wireless communication device may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to obtain an indication of the ISL activation that will occur at the activation time at the AS layer. The one or more processors may be configured to receive communications. The one or more processors may be configured to buffer these communications in a buffer at the AS layer. The one or more processors may be configured to release these communications from the buffer to an upper protocol layer at a release rate that will change between the transition start time and the activation time.

[0010] Some aspects described herein relate to a UE for wireless communication. The UE may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to obtain an indication of the ISL deactivation that will occur during the deactivation time at the AS layer. The one or more processors may be configured to buffer communications in a buffer. The one or more processors may be configured to release these communications from the buffer at a release rate that will change between the deactivation time and the transition end time. The one or more processors may be configured to send these communications.

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a wireless communication device. The instruction set, when executed by one or more processors of the wireless communication device, enables the wireless communication device to obtain an indication of ISL activation that will occur at an activation time at the AS layer. The instruction set, when executed by one or more processors of the wireless communication device, enables the wireless communication device to receive communications. The instruction set, when executed by one or more processors of the wireless communication device, enables the wireless communication device to cache these communications in a buffer at the AS layer. The instruction set, when executed by one or more processors of the wireless communication device, enables the wireless communication device to release these communications from the buffer to an upper protocol layer at a release rate that will change between a transition start time and the activation time.

[0012] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication by a UE. The instruction set, when executed by one or more processors of the UE, may cause the UE to obtain an indication of an ISL deactivation that will occur at a deactivation time at the AS layer. The instruction set, when executed by one or more processors of the UE, may cause the UE to buffer communications in a buffer. The instruction set, when executed by one or more processors of the UE, may cause the UE to release these communications from the buffer at a release rate that will change between the deactivation time and the transition end time. The instruction set, when executed by one or more processors of the UE, may cause the UE to send these indications.

[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for obtaining, at an AS layer, an indication of an ISL activation that will occur at an activation time. The apparatus may include means for receiving communications. The apparatus may include means for buffering the communications in a buffer at the AS layer. The apparatus may include means for releasing the communications from the buffer to an upper protocol layer at a release rate that varies between a transition start time and the activation time.

[0014] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for obtaining an indication of an ISL deactivation that will occur at a deactivation time at an AS layer. The apparatus may include means for buffering communications in a buffer. The apparatus may include means for releasing the communications from the buffer at a release rate that varies between the deactivation time and a transition end time. The apparatus may include means for sending the communications.

[0015] Aspects collectively include methods, apparatus, systems, computer program products, non-transitory computer-readable media, UEs, base stations, network entities, non-terrestrial network (NTN) entities, wireless communication devices, and / or processing systems as fully described herein with reference to the accompanying drawings and description and as illustrated in the accompanying drawings and description.

[0016] The foregoing has been quite extensively summarized the features and technical advantages of examples according to the present disclosure so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for the same purpose of achieving the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (both their organization and methods of operation) and the associated advantages will be better understood according to the following description. Each of the drawings provided is for illustration and description purposes, and not as a definition of the limitations of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

[0021] FIG. 4A to FIG. 4C is a diagram illustrating an example of satellite deployment in a non-terrestrial network according to the present disclosure.

[0022] Figure 5A is a diagram illustrating an example of inter-satellite link (ISL) activation according to the present disclosure.

[0023] Figure 5B is a diagram illustrating an example ISL deactivation according to the present disclosure.

[0024] Figure 6 is a diagram illustrating an example of a change in propagation delay associated with an ISL according to the present disclosure.

[0025] Figure 7 is a diagram illustrating an example of a user plane protocol stack and a control plane protocol stack of a network entity (eg, a base station) and a core network for communicating with a UE according to the present disclosure.

[0026] Figure 8 is a diagram illustrating an example of a gradual increase in a delay of receiving communications according to the present disclosure.

[0027] Fig. 9 is a diagram illustrating an example of a gradual increase in a delay of receiving communications according to the present disclosure.

[0028] Fig.10 is a diagram illustrating an example process performed, for example, by a wireless communication device according to the present disclosure.

[0029] Fig.11 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0030] Fig.12 is a diagram of an example apparatus for wireless communications according to the present disclosure.

[0031] Fig.13 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system according to the present disclosure.

[0032] Fig.14 is a diagram illustrating an example of a specific implementation of code and circuits for an apparatus according to the present disclosure.

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

[0034] Fig.16 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system according to the present disclosure.

[0035] Fig.17 is a diagram illustrating an example of a specific implementation of code and circuits for an apparatus according to the present disclosure. DETAILED DESCRIPTION

[0036] A user equipment (UE) may communicate with a network entity (e.g., a base station, a gateway) using one or more satellites, unmanned aerial vehicles (UAVs), or high altitude platform stations (HAPS). According to one or more examples, a satellite may include a network entity. In some examples, a satellite may be referred to as a non-terrestrial base station, a regenerative repeater, an onboard processing repeater, and / or a non-terrestrial network (NTN) entity. A UE may be stationary or mobile and may be served by a satellite via a service link. A service link may include a link between a satellite and a UE and may include one or more of an uplink or a downlink. A satellite may relay a signal received from a gateway (e.g., a ground station) via a feeder link. A feeder link may include a link between a satellite and a gateway and may include one or more of an uplink or a downlink.

[0037] Inter-satellite links (ISLs) or links between satellites can be used to support coverage extension in NTNs (networks involving non-terrestrial entities). For example, in one example, if a gateway is deployed with certain restrictions and a first satellite does not have a direct feeder link connection to the gateway, a second satellite with a feeder link can be communicatively connected to the first satellite using an ISL. In this way, the first satellite has access to the feeder link and service availability is improved.

[0038] In one example, when the current feeder link of the first satellite degrades (e.g., the signal propagation distance increases and / or the radio conditions degrade), the first satellite may apply an ISL to connect with the second satellite. The second satellite may utilize its feeder link connection and the ISL to facilitate communication between the first satellite and a network (e.g., a gateway). According to one or more examples, the process of switching the connection of the first satellite by applying the ISL may be referred to as "ISL activation" for the first satellite. ISL activation may help improve connectivity between the first satellite and the network. As another example, when the feeder link of the first satellite improves (e.g., the propagation distance decreases and / or the radio conditions improve), the first satellite may turn off the ISL and / or disconnect from the second satellite. The first satellite may apply the feeder link to communicate with the network without requiring the traffic of the first satellite to pass through the second satellite. According to one or more examples, the process of disconnecting from the second satellite and applying a feeder link connection with the network may be referred to as "ISL deactivation" for the first satellite. ISL deactivation may reduce the signal propagation distance and / or signal propagation travel time between the first satellite and the network.

[0039] In some examples, the satellite may be located in a geostationary orbit (GSO) or a geosynchronous equatorial orbit (GEO), which may be located, for example, 36,000 kilometers (km) above the earth. The satellite has a negligible velocity relative to the earth, but has a round-trip propagation delay of greater than 500 ms, compared to 25 milliseconds (ms) for a low earth orbit (LEO) satellite at 600 km above the earth and 100 ms for a medium earth orbit (MEO) satellite. In an NTN, where the distance between the UE 120 and the satellite may be greater than 600 km, a change in the path loss of the signal may not directly correspond to a change in the propagation distance of the signal. In addition, if the satellite is in a non-geostationary orbit (NGSO), the satellite may not always be available to the UE 120 because the satellite may be moving in a place without line of sight.

[0040] In another example, a first satellite may have a feeder link, but in the event that there is a change in the communication path (the way the communication links are arranged between the communication entities) in the NTN topology, a topology change event may occur. This may include a change in the use of the communication link or a change in the operation of the NTN entity (e.g., activation, deactivation, no line of sight, out of range). In one example, a topology change event may be an ISL activation, where the first satellite no longer uses the feeder link between the first satellite and the gateway and switches to using the ISL between the first satellite and the second satellite, which in turn may use the corresponding feeder link to the gateway. A topology change event may also include an ISL deactivation, where the first satellite switches from using the ISL to using the feeder link.

[0041] According to one or more examples, when the ISL is activated or deactivated, the signal propagation delay between the UE and the gateway changes because the time for signal propagation through one satellite is shorter than the time for signal propagation through two satellites separated by a significant distance. Therefore, the communication service will experience a sudden change in delay. The amount of delay change is related to the propagation delay change. The sudden change in delay (if large) may affect the communication service of the UE because the communication service of the UE may not be aware of the cause of such a sudden change. If it is sudden, even smaller changes in delay may also affect the communication service of the UE. The sudden change in delay may cause unexpected communication service behavior, such as suspension of communication service, triggering of congestion control algorithms, or changes in the quality of communication service experience.

[0042] The UE may obtain an indication of an ISL activation to be performed at an activation time or an ISL deactivation to be performed at a deactivation time at an access stratum (AS) layer (e.g., a physical protocol layer). According to various aspects described herein, instead of an immediate change in propagation delay, the UE may gradually increase or decrease a delay between a first propagation delay before a topology change event (e.g., satellite switching, activation of an ISL, deactivation of an ISL) and / or a second propagation delay after a topology change event. This may include changing the rate at which communications are released from a buffer of the UE so that the change in propagation delay experienced by a service application of the UE gradually transitions from a first propagation delay to a second propagation delay, rather than immediately. The buffer may be a storage (a repository or temporary repository for later release) of buffered communications. For a UE that receives communications in association with an ISL activation, the UE may buffer the received communications and release the communications from the buffer at the AS layer to an upper protocol layer (e.g., a layer above the AS layer, an application layer for an application providing a service) at a release rate that changes between a transition start time and an ISL activation time. The transition start time may be an estimated time to begin changing the release rate. For a UE that sends communications in association with ISL deactivation, the UE may release communications from the buffer at a release rate that changes between the ISL deactivation time and the transition end time. The transition end time may be an estimated time to stop changing the release rate. For example, the release rate may be changed based at least in part on a configured function (e.g., a linear function, a step function, a nonlinear function). In this way, the UE may avoid sudden changes in latency and thus avoid communication pauses, triggering of traffic congestion algorithms, unexpected changes in communication experience, or other results that may be attributed to sudden changes in latency and discard services or consume additional resources when reconnecting services. Therefore, the UE may reduce latency and save processing resources and signaling resources.

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

[0044] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms, etc. (collectively referred to as "elements"). These elements can be implemented using hardware, software, or a combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

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

[0046] Figure 1 1 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include a UE 120 or a plurality of UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e). The wireless network 100 may also include one or more network entities, such as a base station 110 (shown as BS110a, BS110b, BS110c, and BS110d) and / or other network entities. The base station 110 is a network entity that communicates with the UE 120. Base station 110 (sometimes referred to as BS) may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and / or a transmit receive point (TRP). Each base station 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to a coverage area of ​​a base station 110 and / or a base station subsystem serving the coverage area, depending on the context in which the term is used.

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

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

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

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

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

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

[0053] In some aspects, as shown, the cell may be provided by a network entity (e.g., base station 110) of the NTN. As used herein, a "non-terrestrial network" may refer to a network provided with access by a non-terrestrial base station (such as a base station carried by a satellite, balloon, airship, aircraft, unmanned aerial vehicle, and / or a high-altitude platform station). The network entity (NTN entity) in the NTN may use polarization. For example, the network entity (NTN entity) in the satellite 135 may use circular polarization 136 or linear polarization 138 to send communications to the UE 120. Circular polarization occurs when the electric field tip of an electromagnetic wave at a fixed point in space moves around a circle, and the electromagnetic wave may be formed by superimposing two orthogonal linearly polarized waves of equal amplitude and a phase difference of 90 degrees. Circular polarization may be right-hand circular polarization (RHCP) or left-hand circular polarization (LHCP). Linear polarization occurs when the electric field tip of an electromagnetic wave at a fixed point in space oscillates along a straight line over time.

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

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

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

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

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

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

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

[0061] In some aspects, a wireless communication device (e.g., UE 120, network entity) may include a communication manager 140 or 150. As described in more detail elsewhere herein, the communication manager 140 or 150 may obtain an indication of ISL activation that will occur at the activation time at the AS layer. The communication manager 140 or 150 may receive communications and buffer the communications in a buffer at the AS layer. The communication manager 140 or 150 may release communications from the buffer to an upper protocol layer at a release rate that changes between the transition start time and the activation time. Additionally or alternatively, the communication manager 140 or 150 may perform one or more other operations described herein.

[0062] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may obtain an indication of an ISL deactivation that will occur at the deactivation time at the AS layer. The communication manager 140 may buffer the communication in a buffer and release the communication from the buffer at a release rate that will change between the deactivation time and the transition end time; and send the communication. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

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

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

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

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

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

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

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

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

[0071] As described in more detail elsewhere herein, a controller / processor of a network entity (e.g., controller / processor 240 of base station 110), controller / processor 280 of UE 120, and / or Figure 2 Any other component of the NTN may perform one or more techniques associated with the gradual release rate of the buffer in association with the ISL transition. In some aspects, the NTN entity is a network entity at the surface or at a satellite (e.g., 135). For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component that can execute or guide e.g. Fig.10 The process of 1000 Fig.11 1100 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for a network entity and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed (e.g., directly or after compilation, conversion, and / or interpretation) by one or more processors of a network entity and / or UE 120, may cause one or more processors, UE 120, and / or a network entity to perform or direct, for example, Fig.10 The process of 1000 Fig.11 The process 1100 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0072] In some aspects, a wireless communication device (e.g., UE 120, network entity) includes: a component for obtaining an indication of ISL activation to occur at an activation time at the AS layer; a component for receiving a communication; a component for buffering the communication in a buffer at the AS layer; and / or a component for releasing the communication from the buffer to an upper protocol layer at a release rate that changes between the transition start time and the activation time. In some aspects, the components for the wireless communication device to perform the operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246. In some aspects, components for the wireless communication device to perform the operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0073] In some aspects, the UE 120 includes means for obtaining an indication of the ISL deactivation to occur at the deactivation time at the AS layer; means for buffering the communication in the buffer; means for releasing the communication from the buffer at a release rate that varies between the deactivation time and the transition end time; and / or means for sending the communication. The means for the UE 120 to perform the operations described herein may include, for example, one or more of the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

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

[0075] Figure 3 is a diagram illustrating an example of a decomposed base station 300 according to the present disclosure.

[0076] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station, or one or more units (or one or more components) that perform base station functionality) can be implemented in an aggregated architecture or a decomposed architecture. For example, a BS (such as a Node B, an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0077] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit (e.g., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU)).

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

[0079] The decomposed base station 300 architecture may include one or more CUs 310 that may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 through one or more decomposed base station units (such as a near-RT RIC 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via corresponding midhaul links, such as an F1 interface. The DU 330 may communicate with one or more RUs 340 via corresponding fronthaul links. Fronthaul links, midhaul links, and backhaul links may generally be referred to as "communication links." The RU 340 may communicate with a corresponding UE 120 via one or more RF access links. In some aspects, a UE 120 may be served simultaneously by multiple RUs 340. The DU 330 and the RU 340 may also be referred to as "O-RAN DU (O-DU)" and "O-RAN RU (O-RU)", respectively. The network entity may include a CU, DU, RU, or any combination of CU, DU, and RU. The network entity may include a decomposed base station or one or more components of a decomposed base station, such as a CU, DU, RU, or any combination of CU, DU, and RU. The network entity may also include one or more of the following: a TRP, a relay station, a passive device, an intelligent reflective surface (IRS), or other components that may provide a network interface or service for a UE, a mobile station, a sensor / actuator, or other wireless device.

[0080] Each of the units (i.e., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, the unit may include a wired interface configured to receive or send signals to one or more of the other units on a wired transmission medium. Additionally, the unit may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive or send signals or both to one or more of the other units on a wireless transmission medium.

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

[0082] 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 340. In some aspects, DU 330 may host one or more of the following depending at least in part on a functional split such as that defined by 3GPP: a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.). In some aspects, DU 330 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU 310.

[0083] The lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of communicating with the control plane and user plane of the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and the CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).

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

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

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

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

[0088] FIG. 4A to FIG. 4C is a diagram illustrating an example of satellite deployment in an NTN according to the present disclosure.

[0089] Figure 4A Example 400 in shows a regenerative satellite deployment. In example 400, UE 120 is served by satellite 420 (e.g., satellite 135) via service link 430. For example, satellite 420 may include a network entity (e.g., base station 110, BS110a, gNB). In some examples, satellite 420 may be referred to as a non-terrestrial base station, a regenerative repeater, an onboard processing repeater, and / or an NTN entity. In some examples, satellite 420 may demodulate uplink radio frequency signals and may modulate baseband signals derived from uplink radio signals to produce downlink radio frequency transmissions. Satellite 420 may send downlink radio frequency signals on service link 430. Satellite 420 may provide a cell covering UE 120. In some examples, satellite 420 may further communicate with a ground gateway via a feeder link. Satellite 420 may be connected to a RAN, a core network, and / or a data network via a gateway.

[0090] Figure 4BThe example 410 in FIG. 4 shows a transparent satellite deployment, which may also be referred to as a bent-pipe satellite deployment. In the example 410, the UE 120 is served by the satellite 440 via the service link 430. The satellite 440 may also be considered as an NTN entity. The NTN entity may include a CU, one or more DUs, and / or one or more RUs, depending on the deployment with other NTN entities and ground stations. The satellite 440 may be a transparent satellite. The satellite 440 may relay the signal received from the UE 120 via the service link 430 to the gateway 450 via the feeder link 460. In another example, the satellite 440 may receive an uplink radio frequency transmission from the service link 430, and may send an uplink radio frequency transmission to the feeder link 460 without demodulating the uplink radio frequency transmission. In some examples, the satellite may convert the frequency of the uplink radio frequency transmission received on the service link 430 to the frequency of the uplink radio frequency transmission on the feeder link 460, and may amplify and / or filter the uplink radio frequency transmission. In some examples, similar to in the uplink direction, satellite 440 may relay downlink signals received from gateway 450 via feeder link 460 to UE 120 via service link 430. In some examples, UE 120 shown in examples 400 and 410 may be associated with global navigation satellite system (GNSS) capabilities, global positioning system (GPS) capabilities, etc., although not all UEs have such capabilities. Satellite 440 may provide a cell covering UE 120.

[0091] The service link 430 may include a link between the satellite 440 and the UE 120, and may include one or more of an uplink or a downlink. The feeder link 460 may include a link between the satellite 440 and the gateway 450, and may include one or more of an uplink (e.g., from the UE 120 to the gateway 450) or a downlink (e.g., from the gateway 450 to the UE 120).

[0092] Due to the movement of satellites 420 and 440 and the potential movement of UE 120, feeder link 460 and service link 430 may each experience Doppler effects. These Doppler effects may be significantly greater than the Doppler effects in the ground network. The Doppler effect on feeder link 460 can be compensated to a certain extent, but may still be associated with a certain amount of uncompensated frequency error. In addition, gateway 450 may be associated with residual frequency error, and / or satellite 420 / 440 may be associated with onboard frequency error. These frequency error sources may cause the downlink frequency received at UE 120 to deviate from the target downlink frequency.

[0093] Satellites 420 and 440 may be satellites in GSO or GEO, which may be located, for example, 36,000 kilometers (km) above the earth. The satellite has a negligible speed relative to the earth, but has a round-trip propagation delay of greater than 500 ms, compared to a round-trip propagation delay of 25 milliseconds (ms) for a LEO satellite 600 km above the earth. In NTNs where the distance between UE 120 and the satellite may be greater than 600 km, path loss changes may not be properly reflected in propagation delay changes. It is expected that UE 120 can autonomously pre-compensate for propagation delays up to a reference point, and therefore timing advance (TA) verification may be performed more directly, rather than relying on indirect parameters such as RSRP. Due to propagation delays, UE 120 may use TA for timing alignment of communications. TA may inform UE 120 to send communications in the uplink earlier than the reference downlink time slot timing by the TA amount. In the event of a change in the propagation distance between UE 120 and a network entity, TA may need to be verified. Furthermore, in the case where the satellite is in an NGSO, the satellite may not always be available for use by the UE 120 .

[0094] Some satellite operators may deploy satellite access with intentional coverage gaps or discontinuous coverage (DC). DC may involve LEO satellites, IoT networks, UAVs, HAPS, or satellite constellations that do not always cover a specific location on the earth. Some services may be delay tolerant and can use DC. Such services may include services for IoT devices and networks, services for utility meters, or services using sensors. DC can be used to address service availability and power consumption. In addition to DC, the feeder link 460 may have an intermittent connection to a ground station (such as gateway 450). Due to deployment design and / or cost, there may be some areas where it is not feasible to deploy ground stations (e.g., in remote geographical locations with sparse populations).

[0095] In order to handle the unavailability of the feeder link 460, the satellite transmitter may include a network element at the satellite 420 / 440. Both the radio network and the core network aspects may be installed on the satellite 420 / 440. In one scenario, the entire control plane and user plane path may be installed on the satellite 420 / 440. For example, the control plane management entity (e.g., the mobile management entity (MME) in 4G or the access and mobility management function (AMF) and session management function (SMF) in NR) and the user plane path (e.g., the service gateway (GW) and the packet data network GW for 4G or the user plane function in NR) may be installed on the satellite 420 / 440. In this scenario, the ground station (e.g., the gateway 450) may include a home subscriber service (HSS), which includes subscription management, user authentication and authorization. In addition, in this scenario, some parts of the control plane path may be at the ground station (e.g., coordination between control plane management entities in different satellites, buffering of user data and control plane data when the feeder link is unavailable). In this scenario, there may also be user data plane and control plane data buffering at the satellite due to DC. Finally, the Internet connection for the data plane may be at the ground station. Other functional splits between the satellite transmitter and the ground station may be employed.

[0096] Figure 4C Example 470 in FIG. 4 shows the use of ISL 480 between satellite 440 and satellite 490. ISL 480 can be used to support coverage extension in NTN. For example, if gateway 450 is deployed with certain restrictions and satellite 440 does not have a direct feeder link connection to gateway 450, satellite 440 can be connected to satellite 490 having feeder link 460 through ISL 480. In this way, satellite 440 has access to gateway 450 and service availability is improved.

[0097] In some aspects, the network functions of the decomposed base station can be split between satellites. For example, satellite 440 can perform the functions of a DU and satellite 490 can perform the functions of a CU.

[0098] As indicated above, FIG. 4A to FIG. 4C Some examples are provided. Other examples can be found in the FIG. 4A to FIG. 4C Different than described.

[0099] Figure 5A and Figure 5B 5 are diagrams illustrating an example 500 of ISL activation and an example 502 of ISL deactivation, respectively, according to the present disclosure.

[0100] Figure 5AThe example 500 in FIG. 5 shows that a satellite 440 may have a feeder link 510. However, a topology change event may occur where there is a change in the communication path in the NTN topology. This may include a change in the link used or a change in the operation of the NTN entity. In the example 500, the topology change event is an ISL activation where the satellite 440 no longer uses the feeder link 510 and switches to using the ISL 480 to the peer satellite 490. This may be due to the satellite 440 moving to a location where there is no line of sight to the gateway 450. From the perspective of the UE, the connection or communication path between the satellite 440 and the gateway 450 may be an extended feeder link, even though the communication path advances through the ISL 480 and the satellite 490.

[0101] Figure 5B Example 502 in Figure 5 shows that a topology change event may be an ISL deactivation, where the satellite switches from using ISL 480 to using feeder link 510. For example, satellite 440 or the network may determine that satellite 440 has or will have line of sight with gateway 450. In other words, satellite 440 may activate use of ISL 480 as it moves further away from gateway 450, and deactivate use of ISL 480 as it moves closer to gateway 450.

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

[0103] Figure 6 is a diagram illustrating an example 600 of changes in propagation delay associated with an ISL according to the present disclosure.

[0104] When ISL 480 is activated or deactivated, the signal propagation delay between UE 120 and gateway 450 changes because the first propagation delay 602 (T1+T2) of the signal propagation through satellite 440 is less than the second propagation delay 604 (T1+T3+T4) of the signal propagation through both satellite 440 and satellite 490 via ISL 480. Therefore, the communication service will experience a sudden change in latency. The delay change 606 (time t0) when the ISL is activated is the difference between the first propagation delay 602 and the second propagation delay 604. According to one or more examples, if satellite 440 is a LEO satellite and satellite 490 is a GEO satellite, the delay change 606 may exceed 200ms. The sudden change in latency may affect the communication service of the UE because the communication service of the UE is unaware of the cause of the sudden change. Sudden changes in latency may result in unexpected communication service behavior, such as communication service pauses (e.g., Transmission Control Protocol (TCP) spurious pauses when the round-trip time (RTT) exceeds the retransmission timer), triggering of congestion control algorithms (e.g., web real-time communication (WebRTC) algorithms that follow the WebRTC framework for browsers and video calls to control congestion), or changes in the quality of the communication service experience (e.g., changes in Quality of Experience (QoE)).

[0105] According to one or more aspects described herein, instead of an immediate change in propagation delay, a UE (e.g., UE 120) may gradually increase or decrease a delay between a first propagation delay before a topology change event (e.g., satellite switching, activation of an ISL, deactivation of an ISL) and a second propagation delay after the topology change event. This may include buffering communications in a buffer in a memory (e.g., memory 282), and changing a rate at which communications are released from the UE's buffer, such that a change in propagation delay experienced by a service application of the UE gradually transitions from a first propagation delay to a second propagation delay, rather than immediately. For a UE receiving communications associated with an ISL activation, the UE may release communications from the buffer at a release rate that changes between a transition start time and an ISL activation time. The transition start time may be an estimated time to start changing the release rate. For a UE sending communications associated with an ISL deactivation, the UE may release communications from the buffer at a release rate that changes between an ISL deactivation time and a transition end time. The transition end time may be an estimated time to stop changing the release rate. In this way, the UE can avoid communication pauses, triggering of traffic congestion algorithms, unexpected changes in communication experience, or other results that may drop service or consume additional resources when reconnecting to service. Therefore, the UE can reduce latency and save processing resources and signaling resources.

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

[0107] Figure 7 700 is a diagram illustrating an example of a user plane protocol stack and a control plane protocol stack of a network entity (e.g., a base station 110) and a core network for communicating with a UE 120 according to the present disclosure. In some aspects, the network entity may include multiple network nodes. In some aspects, the protocol stack functions of the network entity may be distributed across multiple network nodes. For example, a first network entity may implement a first layer of a protocol stack, and a second network entity may implement a second layer of the protocol stack. The distribution of the protocol stack across network nodes (in an example where the protocol stack is distributed across network nodes) may be based at least in part on functional partitioning, as described elsewhere herein. It should be understood that in some aspects, references to "network node" or "the network node" may refer to multiple network nodes.

[0108] On the user plane, the UE 120 and the network entity may include a corresponding PHY layer, a MAC layer, an RLC layer, a PDCP layer, and an SDAP layer. The user plane function may handle the transmission of user data between the UE 120 and the network entity. On the control plane, the UE 120 and the network entity may include a corresponding RRC layer. In addition, the UE 120 may include a non-access stratum (NAS) layer that communicates with the AMF. The NAS layer may be a functional layer for managing the establishment of a communication session and maintaining continuous communication (as opposed to the AS layer responsible for carrying information on the wireless part of the network). NAS uses a set of protocols to convey non-radio signaling between the UE and the 5G core. The AMF may be associated with a core network associated with the network entity, such as a 5G core network (5GC) or a next generation radio access network (NG-RAN). The control plane function may handle the transmission of control information between the UE and the core network and / or between the UE and the NG-RAN. Generally speaking, if the first layer is farther away from the PHY layer than the second layer, the first layer is referred to as being higher than the second layer. For example, the PHY layer may be referred to as the lowest layer, and the SDAP / PDCP / RLC / MAC layer may be referred to as being higher than the PHY layer and lower than the RRC layer. The AS layer 702 may be any one of the SDAP / PDCP / RLC / MAC layers. The AS layer 702 may be a layer involving radio operations. The application (APP) layer may be an upper protocol layer 704 higher than the SDAP / PDCP / RLC / MAC layer. The upper protocol layer 704 may be a layer for managing applications or services. In some examples, the APP layer may reside in an entity belonging to a data network, rather than in a network entity (e.g., a base station 110). In some examples, an entity may handle services and functions of a given layer (e.g., a PDCP entity may handle services and functions of a PDCP layer), although the description herein mentions that the layer itself handles these services and functions.

[0109] The RRC layer may handle communications related to configuring and operating the UE 120, such as: broadcasting of system information related to the AS and NAS; paging initiated by the 5GC or NG-RAN; establishment, maintenance, and release of an RRC connection between the UE and the NG-RAN, including the addition, modification, and release of carrier aggregation, and the addition, modification, and release of dual connectivity; security functions, including key management; establishment, configuration, maintenance, and release of signaling radio bearers (SRBs) and data radio bearers (DRBs); mobility functions (e.g., handover and context transfer, UE cell selection and reselection and control of cell selection and reselection, inter-RAT mobility); quality of service (QoS) management functions; UE measurement reporting and control of reporting; detection of and recovery from radio link failures; and NAS messaging between the NAS layer and lower layers of the UE 120. The RRC layer is often referred to as Layer 3 (L3).

[0110] The SDAP layer, the PDCP layer, the RLC layer, and the MAC layer may be collectively referred to as Layer 2 (L2). Therefore, in some cases, the SDAP, PDCP, RLC, and MAC layers are referred to as sublayers of Layer 2. On the transmitting side (e.g., if the UE 120 is sending uplink communications or the network node 110 is sending downlink communications), the SDAP layer may receive a data stream in the form of a QoS flow. The QoS flow is associated with a QoS identifier and a QoS flow identifier (QFI), which identifies the QoS parameters associated with the QoS flow, and the QoS flow identifier (QFI) identifies the QoS flow. Policy and charging parameters are implemented based on the QoS flow granularity. The QoS flow may include one or more service data flows (SDFs), as long as each SDF of the QoS flow is associated with the same policy and charging parameters. In some aspects, the RRC / NAS layer may generate control information to be sent, and may map the control information to one or more radio bearers to provide to the PDCP layer.

[0111] The SDAP layer or the RRC / NAS layer may map the QoS flow or control information to the radio bearer. Therefore, it can be said that the SDAP layer handles the QoS flow on the sending side. The SDAP layer may provide the QoS flow to the PDCP layer via the corresponding radio bearer. The PDCP layer may map the radio bearer to the RLC channel. The PDCP layer may handle various services and functions on the user plane, including sequence numbering, header compression and decompression (if robust header compression is enabled), delivery, reordering and duplication detection of user data (if in-order delivery to the layer above the PDCP layer is required), PDCP protocol data unit (PDU) routing (in the case of split bearers), retransmission, encryption and decryption of PDCP service data unit (SDU), PDCP SDU discard (e.g., according to a timer, as described elsewhere in this document), PDCP re-establishment and data recovery for RLC acknowledgement mode (AM), and duplication of PDCP PDUs. The PDCP layer may handle similar services and functions on the control plane, including sequence numbering, encryption, decryption, integrity protection, delivery of control plane data, duplication detection, and duplication of PDCP PDUs.

[0112] The PDCP layer may provide data in the form of PDCP PDUs to the RLC layer via an RLC channel. The RLC layer may handle delivery of upper layer PDUs to the MAC and / or PHY layers, sequence numbering independent of the PDCP sequence numbering, error correction via automatic repeat request (ARQ), segmentation and re-segmentation, reassembly of SDUs, RLC SDU discard, and RLC reestablishment.

[0113] The RLC layer can provide the MAC layer with data mapped to logical channels. The services and functions of the MAC layer include mapping between logical channels and transport channels (used by the PHY layer as described below), multiplexing MAC SDUs belonging to one or different logical channels into a transport block (TB) delivered to / from the physical layer on the transport channel, scheduling information reporting, error correction by hybrid ARQ (HARQ), priority handling between UEs by means of dynamic scheduling, priority handling between logical channels of a UE by means of logical channel prioritization, and padding.

[0114] The MAC layer can encapsulate data from logical channels into TBs and provide the TBs to the PHY layer on one or more transport channels. The PHY layer can handle various operations related to the transmission of data signals, such as combining Figure 2 The PHY layer is often referred to as Layer 1 (L1).

[0115] On the receiving side (e.g., if the UE 120 is receiving downlink communications or the network entity is receiving uplink communications), operations may be similar to those described for the transmitting side, but in the opposite direction. For example, the PHY layer may receive TBs and may provide TBs to the MAC layer on one or more transport channels. The MAC layer may map transport channels to logical channels and may provide data to the RLC layer via the logical channels. The RLC layer may map logical channels to RLC channels and may provide data to the PDCP layer via the RLC channels. The PDCP layer may map RLC channels to radio bearers and may provide data to the SDAP layer or the RRC / NAS layer via the radio bearers.

[0116] Data may be passed between layers in the form of PDUs and SDUs. An SDU is a unit of data that has been passed from a layer or sublayer to a lower layer. For example, a PDCP layer may receive a PDCP SDU. A given layer may then encapsulate the data unit into a PDU and may pass the PDU to a lower layer. For example, a PDCP layer may encapsulate a PDCP SDU into a PDCP PDU and may pass the PDCP PDU to an RLC layer. An RLC layer may receive a PDCP PDU as an RLC SDU, may encapsulate the RLC SDU into an RLC PDU, and so on. In effect, a PDU carries an SDU as a payload.

[0117] In some aspects, the UE may operate one or more buffers at the AS layer 702. One or more buffers may be included in the memory 282. For example, a buffer 706 in the memory 282 of the UE (e.g., UE 120) may buffer (e.g., store in the memory for later release from the buffer) received communications and release these communications later. The buffer 706 may exist or operate at the AS layer 702 (e.g., at the RLC layer), and the buffer 706 may release the communication to the upper protocol layer 704. The application providing the communication service may exit or operate at the upper protocol layer 704 (e.g., application layer, service layer, transport layer). The application may determine whether there is a problem with the feeder link or the service link (e.g., signal loss, excessive delay, congestion), and take action to remedy the problem (e.g., reestablish the link). The buffer 706 may release the communication to the upper protocol layer 704 for use by the application.

[0118] In some aspects, the buffer 706 may store communications to be sent. The buffer may exist or operate at the AS layer 702. The buffer 706 may release communications to a lower protocol layer (such as a MAC layer or a PHY layer) for transmission.

[0119] In some aspects, buffer 706 can be used to store communications at a rate that helps gradually increase or decrease latency (buffering rate). The buffering rate can be based at least in part on the difference in propagation delays, a configured function, and / or latency sensitivity of a service or quality of service flow.

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

[0121] Figure 8 is a diagram illustrating an example 800 of a gradual increase in latency of receiving communications in accordance with the present disclosure.

[0122] Example 800 shows a gradual transition of a UE 820 from a transition start time 802 (t0) to an ISL activation time 804 (t1). The gradual transition may be part of a transition phase that occurs prior to ISL activation. The gradual transition involves a delay change 806 from a first propagation delay 808 prior to ISL activation (communication via NTN entity 810) to a second propagation delay 812 after ISL activation (communication via NTN entity 810 and NTN entity 840).

[0123] Example 800 also shows that NTN entity 810 (e.g., base station 110, network entity, satellite 420, satellite 440) and UE 820 (e.g., UE 120) can communicate with each other. UE 820 and ground network entity (e.g., ground station 830) can communicate via NTN entity 810. Ground station 830 can be a base station (e.g., base station 110) or a gateway (e.g., gateway 450). There can be another NTN entity 840 (e.g., base station 110, network entity, satellite 420, satellite 490) with a feeder link (e.g., feeder link 460) to the ground network entity, and there can be an ISL (e.g., ISL 480) activated or deactivated between NTN entity 810 and NTN entity 840.

[0124] As indicated by reference numeral 845, the UE 820 and the NTN entity 810 may communicate via the service link 430. As indicated by reference numeral 850, the NTN entity 810 and the ground station 830 may communicate via the feeder link 510. This communication precedes a topology change event such as ISL activation.

[0125] As shown by reference numeral 855, the NTN entity 810 may send an indication of ISL activation. The indication may be received in a SIB, which may be NTN specific or dedicated to the NTN. The indication may be received in a downlink control information (DCI), a MAC CE, or an RRC message. The indication may be received via a short message on a physical downlink control channel (PDCCH) in a paging occasion (e.g., for an RRC inactive or RRC idle UE). The indication may be received in a dedicated RRC message for an RRC connected UE. For example, the indication may be a handover command, wherein the target cell identifier (ID) contained in the handover command indicates the same cell ID as the current serving cell of the UE 820 on the serving link 430 before the topology change event. Therefore, if the UE 820 receives a handover command requesting the UE 820 to hand over to the current serving cell, the UE 820 may detect the indication. The indication may be broadcast in a system information block (SIB). The indication may activate a buffer for gradually increasing or decreasing latency.

[0126] In some aspects, the UE 820 may obtain the indication through scheduling, calculation, or another communication. The indication may include the ISL activation time 804. The UE 820 may also receive an indication of a transition start time 802. Alternatively, the UE 820 may calculate the transition start time 802 based at least in part on the indication or calculated estimate of the delay variation 806. The UE 820 may calculate the transition start time 802 based at least in part on the indication of the change of the serving link or the feeder link.

[0127] As indicated by reference numeral 860, the UE 820 may buffer or may have buffered communications received from the NTN entity 810. The UE 820 may buffer communications in a buffer (e.g., buffer 706) at the AS layer 702. The buffer may be an additional buffer between the AS layer 702 and the upper protocol layer 704. The additional buffer may be a dedicated buffer that is activated only for a gradual increase or decrease in latency.

[0128] As shown by reference numeral 865, UE 820 can release communication at a release rate 866 that changes between transition start time 802 and ISL activation time 804. For example, the release rate can be reduced, and therefore the delay can be increased. The buffer can release communication to the upper protocol layer (e.g., upper protocol layer 704, application layer, service layer, transport layer). In some aspects, the release rate 866 of the communication from the buffer can be based on a function of time, wherein the time instance or other time information (e.g., ISL activation time 804, transition start time 802, first propagation delay 808, second propagation delay 812, delay variation 806) is input, and the delay amount and / or release rate 866 is output. The function can be a linear function that increases gradually at a stable rate. The function can be a step function, wherein the delay increases a specified amount at an instance of time. The function can be a nonlinear function or any other function for changing the release rate 866 between transition start time 802 and ISL activation time 804. The UE 820 may change the release rate by changing the timer 708 of the buffer or otherwise adjusting the buffering time. The UE 820 may change the release rate or buffering rate (e.g., t-reassembly timer, t-reordering timer) by adjusting the timer 708 for the buffer at a specific layer (e.g., at the RLC layer or the PDCP layer).

[0129] As shown by reference numeral 870, NTN entity 810 may perform ISL activation (shown by ISL activation 872) at ISL activation time 804. By this time, the gradual increase in latency may have been completed. Therefore, there is no sudden change in latency, and communications are not interrupted. This reduces latency and saves processing resources and signaling resources.

[0130] While example 800 illustrates that latency increases based on release rate 866 due to first propagation delay 808 before ISL activation being less than second propagation delay 812 after ISL activation, in some aspects latency may decrease if first propagation delay 808 before ISL activation is greater than second propagation delay 812 after ISL activation.

[0131] As indicated by reference numeral 880, UE 820 and NTN entity 810 may communicate using service link 430 shown in FIG5. As indicated by reference numeral 885, NTN entity 810 may communicate with NTN entity 840 via ISL 480. As indicated by reference numeral 890, NTN entity 840 may communicate with ground station 830 using feeder link 510 shown in FIG5.

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

[0133] Fig. 9 is a diagram illustrating an example 900 of a gradual increase in latency of receiving communications according to the present disclosure.

[0134] Example 900 shows a gradual transition of UE 820 from ISL deactivation time 902 (t0) to transition end time 904 (t1). The gradual transition may be part of a transition phase that occurs after ISL deactivation. The gradual transition involves a delay change 906 from a first propagation delay 908 (communication via NTN entity 810 and NTN entity 840) before ISL deactivation to a second propagation delay 910 (communication via NTN entity 810) after ISL deactivation. The delay may be decreasing at a release rate 912 that is increasing.

[0135] As shown by reference numeral 915, UE 820 and NTN entity 810 may communicate using service link 430 shown in Figure 5. As shown by reference numeral 920, NTN entity 810 may communicate with NTN entity 840 via ISL 480. As shown by reference numeral 925, NTN entity 840 may communicate with ground station 830 using feeder link 510 shown in Figure 5. This is prior to a topology change event such as ISL deactivation.

[0136] As indicated by reference numeral 930, the NTN entity 810 may send an indication of ISL deactivation. In some aspects, the UE 820 may obtain the indication by scheduling, calculation, or another communication. The indication may include the ISL deactivation time 902. The indication may include the transition end time 904. Alternatively, the UE 820 may calculate the transition end time based at least in part on the indication or calculated estimate of the delay variation 906.

[0137] As shown by reference numeral 935, NTN entity 810 may perform ISL deactivation (shown by ISL deactivation 936) at ISL deactivation time 902. As shown by reference numeral 940, UE 820 may buffer or may have buffered communications for transmission. Communications may be received from upper protocol layer 704. UE 820 may buffer communications in a buffer (e.g., buffer 706) at upper protocol layer 704 or AS layer 702. As shown by reference numeral 945, UE 820 may release communications at a release rate 912 that changes between ISL deactivation time 902 and transition end time 904. Release rate 912 may be increasing, and therefore latency is reduced. Buffer may release communications to lower protocol layers (e.g., MAC layer and / or PHY layer) for transmission. UE 820 may send them when communications are released from buffer. In some aspects, the release rate 912 of the communication from the buffer can be based on a time function, wherein the time instance is input, and the time delay and / or the release rate 912 is output. The function can be a linear function that gradually decreases at a stable rate. The function can be a step function, wherein the time delay increases a specified amount at the instance of time. The function can be a nonlinear function or any other function for changing the release rate 912 between the ISL dead time 902 and the transition end time 904. The UE 820 can change the release rate by changing the timer of the buffer. By the transition end time 904, the gradual reduction of the time delay may have been completed. Therefore, there is no sudden change in the time delay, and the communication is not interrupted. This reduces the time delay and saves processing resources and signaling resources.

[0138] As indicated by reference numeral 950, the UE 820 and the NTN entity 810 may communicate via the service link 430. As indicated by reference numeral 955, the NTN entity 810 and the ground station 830 may communicate via the feeder link 510.

[0139] While example 800 illustrates that latency is reduced based on release rate 912 due to first propagation delay 908 before ISL activation being greater than second propagation delay 910 after ISL deactivation, in some aspects latency may increase if first propagation delay 908 before ISL deactivation is less than second propagation delay 910 after ISL deactivation.

[0140] In some aspects, the UE 820 may determine to perform a gradual increase or decrease in delay based at least in part on a change in propagation delay, service type, service characteristic, QoS flow, or any combination thereof. For example, if the delay variation 806 or 906 meets a threshold (e.g., a minimum delay variation, an amount of time), the UE 820 may use a gradual increase or decrease in delay. If the delay variation 806 or 906 does not meet the threshold, the UE 820 may not use a gradual increase or decrease in delay. The determination may be based on a relative change in propagation delay, such as a delay variation 806 or 906 that is proportional to (e.g., divided by) a first propagation delay 808 or 908. In some aspects, the UE 820 may trigger a gradual increase or decrease in delay based at least in part on a service or QoS that is sensitive to sudden delay variations.

[0141] In some aspects, the indication of ISL activation or ISL deactivation may include other information about the transition, such as the duration of the transition phase. The duration may be larger or smaller based at least in part on the size of the delay change 806 or 906. The indication may include parameters to be used during the transition phase. For example, these parameters may include functions to be used by the UE 820 to gradually adjust the delay during the transition phase. These parameters may include how the UE 820 should use the current buffer at a specific layer (such as an RLC or PDCP layer). These parameters may identify the affected QoS flows or services so that only UEs with the affected QoS flows or services can apply the gradual increase or decrease in delay.

[0142] In some aspects, the gradual delay operation described for UE 820 may be performed by a network entity such as a network entity adjacent to or near UE 820. In some aspects, the network entity may be one or more of NTN entity 810, NTN entity 840, and ground station 830. In some aspects, the gradual delay operation performed by UE 820 and the progressive delay operation performed by the network entity may be applied to transmissions in different directions. For example, when ISL is to be activated, UE 820 may release received downlink data with an increased delay, and the network entity may release received uplink data with an increased delay.

[0143] As indicated above, Fig. 9 are provided as examples. Other examples can be found in the Fig. 9 The examples described are different.

[0144] Fig.10 is a diagram illustrating an example process 1000 performed, for example, by a wireless communication device in accordance with the present disclosure. Example process 1000 is an example of a wireless communication device (eg, UE 820, network entity) performing operations associated with buffer release of received communications in association with an ISL transition.

[0145] like Fig.10 As shown, in some aspects, process 1000 may include obtaining, at the AS layer, an indication of an ISL activation that will occur at an activation time (block 1010). Fig.12 or Fig.15 The communication manager 1208 or 1508 and / or the transition component 1210 or 1510 depicted in FIG. 10A may obtain an indication of an ISL activation that will occur at the activation time at the AS layer, as described above.

[0146] like Fig.10 As further shown, in some aspects, process 1000 may include receiving a communication (block 1020). For example, the wireless communication device (e.g., using Fig.12 or Fig.15 The communications manager 1208 or 1508 and / or receiving component 1202 or 1502 depicted in can receive communications as described above.

[0147] like Fig.10 As further shown, in some aspects, process 1000 may include buffering the communication in a buffer at the AS layer (block 1030). Fig.12 or Fig.15 The communication manager 1208 or 1508 and / or the buffer component 1212 or 1512 depicted in FIG. 10A may buffer communications in a buffer at the AS layer, as described above.

[0148] like Fig.10 As further shown, in some aspects, process 1000 may include releasing communications from the buffer to an upper protocol layer at a release rate that varies between the transition start time and the activation time (block 1040). Fig.12 or Fig.15 The communication manager 1208 or 1508 and / or buffer component 1212 or 1512 depicted in FIG. 10 may release communications from the buffer to upper protocol layers at a release rate that varies between the transition start time and the activation time, as described above.

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

[0150] In a first aspect, obtaining an indication includes receiving the indication.

[0151] In a second aspect, alone or in combination with the first aspect, process 1000 includes determining a transition start time based at least in part on the indication.

[0152] In a third aspect, alone or in combination with one or more of the first and second aspects, process 1000 includes determining a difference between a first propagation delay before ISL activation and a second propagation delay after ISL activation based at least in part on the indication.

[0153] In a fourth aspect, alone or in combination with one or more of the first to third aspects, process 1000 includes determining a transition start time based at least in part on the difference value.

[0154] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the buffering rate or the release rate is changed based at least in part on the difference satisfying a threshold.

[0155] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the release rate increases in response to the second propagation delay being greater than the first propagation delay.

[0156] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the release rate is reduced in response to the second propagation delay being less than the first propagation delay.

[0157] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the buffering rate or the release rate is varied based at least in part on a function of the configuration.

[0158] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the configured function is a linear function.

[0159] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the configured function is a non-linear function.

[0160] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the configured function is a step function.

[0161] In a twelfth aspect, alone or in combination with one or more of the first to eleventh aspects, process 1000 includes: changing the release rate by changing a timer associated with the buffer.

[0162] In a thirteenth aspect, either alone or in combination with one or more of the first to twelfth aspects, a buffering rate or a release rate is varied based at least in part on a delay sensitivity of a service or quality of service flow.

[0163] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, buffering communications includes buffering communications using a buffer activated based at least in part on the received indication of ISL activation.

[0164] In a fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the wireless communication device is a UE.

[0165] In a sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the wireless communication device is a network entity, such as a network entity adjacent to the UE.

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

[0167] Fig.11 is a diagram illustrating an example process 1100 performed, for example, by a UE according to the present disclosure. Example process 1100 is an example of a UE (eg, UE 120, UE 820) performing operations associated with buffer release for transmitted communications in association with an ISL transition.

[0168] like Fig.11 As shown, in some aspects, process 1100 may include obtaining, at the AS layer, an indication of ISL deactivation that will occur at a deactivation time (block 1110). For example, a UE (e.g., using Fig.12 The communication manager 1208 and / or transition component 1210 depicted in FIG. 12 may obtain an indication at the AS layer of an ISL deactivation that will occur at the deactivation time, as described above.

[0169] like Fig.11 As further shown, in some aspects, process 1100 may include buffering the communication in a buffer (block 1120). For example, a UE (e.g., using Fig.12 The communications manager 1208 and / or buffer component 1212 depicted in FIG. 10A may buffer communications in a buffer as described above.

[0170] like Fig.11 As further shown, in some aspects, process 1100 may include releasing communications from the buffer at a release rate that varies between the inactivity time and the transition end time (block 1130). Fig.12 The communication manager 1208 and / or buffer component 1212 depicted in FIG. 10A may release communications from the buffer at a release rate that varies between the inactivity time and the transition end time, as described above.

[0171] like Fig.11As further shown, in some aspects, process 1100 may include sending a communication (block 1140). For example, a UE (e.g., using Fig.12 The communication manager 1208 and / or the sending component 1204 depicted in can send communications as described above.

[0172] 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 herein.

[0173] In a first aspect, process 1100 includes determining a transition end time based at least in part on an indication.

[0174] In a second aspect, either alone or in combination with the first aspect, process 1100 includes determining, based at least in part on the indication, a difference between a first propagation delay before the ISL deactivation and a second propagation delay after the ISL deactivation.

[0175] In a third aspect, alone or in combination with one or more of the first and second aspects, process 1100 includes determining a transition end time based at least in part on the difference value.

[0176] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the buffering rate or the release rate is changed based at least in part on the difference satisfying a threshold.

[0177] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the buffering rate or the release rate is varied based at least in part on a function of the configuration.

[0178] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, process 1100 includes: changing the release rate by changing a timer associated with the buffer.

[0179] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, a buffering rate or a release rate is varied based at least in part on a delay sensitivity of a service or quality of service flow.

[0180] although Fig.11 Example blocks of process 1100 are shown, but in some aspects, process 1100 may include Fig.11 Additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted in the process 1100. Additionally or alternatively, two or more blocks of the blocks of process 1100 may be performed in parallel.

[0181] Fig.121 is a diagram of an example apparatus 1200 for wireless communication according to the present disclosure. Apparatus 1200 may be a UE (e.g., UE 120, UE 820), or a UE may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a transmitting component 1204, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using receiving component 1202 and transmitting component 1204. As further shown, apparatus 1200 may include a communication manager 1208. Communication manager 1208 may control and / or otherwise manage one or more operations of receiving component 1202 and / or transmitting component 1204. In some aspects, communication manager 1208 may include a communication manager 1208 in conjunction with Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the described UE. The communication manager 1208 may be or be similar to Figure 1 and Figure 2 For example, in some aspects, the communication manager 1208 can be configured to perform one or more of the functions described as being performed by the communication manager 140. In some aspects, the communication manager 1208 can include a receiving component 1202 and / or a sending component 1204. The communication manager 1208 can include a transforming component 1210 and / or a buffering component 1212, among others.

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

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

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

[0185] In some aspects, the transition component 1210 can obtain an indication of ISL activation that will occur at the activation time at the AS layer. The receiving component 1202 can receive the communication. The buffering component 1212 can buffer the communication in a buffer at the AS layer. The buffering component 1212 can release the communication from the buffer to the upper protocol layer at a release rate that changes between the transition start time and the activation time.

[0186] The transition component 1210 can determine a transition start time based at least in part on the indication. The transition component 1210 can determine a difference between a first propagation delay before the ISL activation and a second propagation delay after the ISL activation based at least in part on the indication. The transition component 1210 can determine a transition start time based at least in part on the difference. The buffer component 1212 can change a release rate by changing a timer associated with a buffer.

[0187] In some aspects, the transition component 1210 can obtain an indication of an ISL deactivation that will occur at the deactivation time at the AS layer. The buffer component 1212 can buffer the communication in a buffer. The buffer component 1212 can release the communication from the buffer at a release rate that changes between the deactivation time and the transition end time. The sending component 1204 can send the communication.

[0188] The transition component 1210 may determine a transition end time based at least in part on the indication. The transition component 1210 may determine a difference between a first propagation delay before the ISL is deactivated and a second propagation delay after the ISL is deactivated based at least in part on the indication. The transition component 1210 may determine a transition end time based at least in part on the difference. The buffer component 1212 may change a release rate by changing a timer associated with a buffer.

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

[0190] Fig.13 is a diagram illustrating an example 1300 of a hardware implementation for an apparatus 1305 employing a processing system 1310 according to the present disclosure. The apparatus 1305 may be a UE.

[0191] The processing system 1310 may be implemented using a bus architecture, generally represented by bus 1315. Bus 1315 may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the processing system 1310. Bus 1315 links together various circuits including one or more processors and / or hardware components (represented by processor 1320, illustrated components, and computer readable media / memory 1325). Bus 1315 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and / or power management circuits.

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

[0193] The processing system 1310 includes a processor 1320 coupled to a computer readable medium / memory 1325. The processor 1320 is responsible for general processing, including executing software stored on the computer readable medium / memory 1325. The software, when executed by the processor 1320, causes the processing system 1310 to perform the various functions described herein for any particular device. The computer readable medium / memory 1325 may also be used to store data manipulated by the processor 1320 when executing the software. The processing system also includes at least one of the illustrated components. A component may be a software module running in the processor 1320, resident / stored in the computer readable medium / memory 1325, one or more hardware modules coupled to the processor 1320, or some combination thereof.

[0194] In some aspects, the processing system 1310 may be a component of the UE 120 and may include the memory 282 and / or at least one of the TX MIMO processor 266, the receive (RX) processor 258, and / or the controller / processor 280. In some aspects, the apparatus 1305 for wireless communication includes: means for obtaining an indication of an ISL activation to occur at an activation time at the AS layer; means for receiving a communication; means for buffering the communication in a buffer at the AS layer; means for releasing the communication from the buffer to an upper protocol layer at a release rate that varies between a transition start time and an activation time. In some aspects, the apparatus 1305 for wireless communication includes: means for obtaining an indication of an ISL deactivation to occur at a deactivation time at the AS layer; means for buffering the communication in a buffer; means for releasing the communication from the buffer at a release rate that varies between a deactivation time and a transition end time; and / or means for sending the communication. The aforementioned means may be one or more of the aforementioned components of the processing system 1310 of the apparatus 1200 and / or the apparatus 1305 configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system 1310 may include the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In one configuration, the aforementioned means may be the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280 configured to perform the functions and / or operations recited herein.

[0195] In some aspects, the processing system 1310 may be a component of the base station 110 and may include the memory 242 and / or at least one of the TX MIMO processor 230, the RX processor 238, and / or the controller / processor 240. In some aspects, the apparatus 1305 for wireless communication includes: means for obtaining an indication of ISL activation to occur at an activation time at the AS layer; means for receiving a communication; means for buffering the communication in a buffer at the AS layer; means for releasing the communication from the buffer to an upper protocol layer at a release rate that varies between a transition start time and an activation time. In some aspects, the apparatus 1305 for wireless communication includes: means for obtaining an indication of ISL deactivation to occur at a deactivation time at the AS layer; means for buffering the communication in a buffer; means for releasing the communication from the buffer at a release rate that varies between a deactivation time and a transition end time; and / or means for sending the communication. The aforementioned means may be one or more of the aforementioned components of the processing system 1310 of the apparatus 1200 and / or the apparatus 1305 configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system 1310 may include the TX MIMO processor 230, the receive processor 238, and / or the controller / processor 240. In one configuration, the aforementioned means may be the TX MIMO processor 230, the receive processor 238, and / or the controller / processor 240 configured to perform the functions and / or operations recited herein.

[0196] Fig.13 are provided as examples. Other examples can be combined with Fig.13 The examples described are different.

[0197] Fig.14 is a diagram of an example 1400 illustrating a specific implementation of code and circuits for an apparatus 1405 according to the present disclosure. The apparatus 1405 may be a UE, or a UE may include the apparatus 1405.

[0198] like Fig.14 As shown, the device 1405 may include a circuit (circuit 1420) for obtaining an indication of an ISL transition (e.g., an activation that will occur at an activation time) at the AS layer. For example, the circuit 1420 may enable the device 1405 to obtain an indication of an ISL activation that will occur at the activation time at the AS layer.

[0199] like Fig.14As shown, the apparatus 1405 may include code (code 1425) stored in the computer-readable medium 1325 for obtaining an indication of an ISL transition (e.g., an activation that will occur at an activation time) at the AS layer. For example, the code 1425, when executed by the processor 1320, may cause the processor 1320 to cause the transceiver 1330 to obtain an indication of an ISL activation that will occur at the activation time at the AS layer.

[0200] like Fig.14 As shown, device 1405 may include circuitry for receiving communications (circuitry 1430). For example, circuitry 1430 may enable device 1405 to receive communications.

[0201] like Fig.14 As shown, the apparatus 1405 may include code (code 1435) for receiving a communication stored in the computer-readable medium 1325. For example, the code 1435, when executed by the processor 1320, may cause the processor 1320 to cause the transceiver 1330 to receive a communication.

[0202] like Fig.14 As shown, the device 1405 may include a circuit (circuit 1440) for buffering the communication in a buffer at the AS layer. For example, the circuit 1440 may enable the device 1405 to buffer the communication in a buffer at the AS layer.

[0203] like Fig.14 As shown, the device 1405 may include code (code 1445) for buffering communications in a buffer at the AS layer stored in the computer-readable medium 1325. For example, the code 1445, when executed by the processor 1320, may cause the processor 1320 to buffer communications in a buffer at the AS layer.

[0204] like Fig.14 As shown, the device 1405 may include a circuit (circuit 1450) for releasing communications from the buffer to the upper protocol layer at a release rate that changes between the transition start time and the activation time. For example, the circuit 1450 may enable the device 1405 to release communications from the buffer to the upper protocol layer at a release rate that changes between the transition start time and the activation time.

[0205] like Fig.14 As shown, the device 1405 may include code (code 1455) stored in the computer-readable medium 1325 for releasing communications from the buffer to the upper protocol layer at a release rate that changes between the transition start time and the activation time. For example, the code 1455, when executed by the processor 1320, may cause the processor 1320 to release communications from the buffer to the upper protocol layer at a release rate that changes between the transition start time and the activation time.

[0206] In some aspects, the device 1405 may include circuitry (circuitry 1420) for obtaining an indication of an ISL transition (e.g., a deactivation that will occur at a deactivation time) at the AS layer. For example, the circuitry 1420 may enable the device 1405 to obtain an indication of an ISL deactivation that will occur at a deactivation time at the AS layer.

[0207] like Fig.14 As shown, the apparatus 1405 may include code (code 1425) stored in the computer-readable medium 1325 for obtaining an indication of an ISL transition (e.g., a deactivation that will occur at a deactivation time) at the AS layer. For example, the code 1425, when executed by the processor 1320, may cause the processor 1320 to cause the transceiver 1330 to obtain an indication of an ISL transition (e.g., a deactivation that will occur at a deactivation time) at the AS layer.

[0208] like Fig.14 As shown, the device 1405 may include circuitry for buffering communications in a buffer (circuitry 1440). For example, the circuitry 1430 may enable the device 1405 to buffer communications in a buffer.

[0209] like Fig.14 As shown, the apparatus 1405 may include code (code 1445) for buffering communications in a buffer stored in the computer-readable medium 1325. For example, the code 1435, when executed by the processor 1320, may cause the processor 1320 to buffer communications in a buffer.

[0210] like Fig.14 As shown, the device 1405 may include a circuit (circuit 1450) for releasing communications from the buffer at a release rate that changes between the downtime and the transition end time. For example, the circuit 1440 may enable the device 1405 to release communications from the buffer at a release rate that changes between the downtime and the transition end time.

[0211] like Fig.14 As shown, the device 1405 may include code (code 1455) stored in the computer-readable medium 1325 for releasing communications from the buffer at a release rate that changes between the downtime and the transition end time. For example, when executed by the processor 1320, the code 1445 may cause the processor 1320 to release communications from the buffer at a release rate that changes between the downtime and the transition end time.

[0212] like Fig.14 As shown, the device 1405 may include circuitry for sending communications (circuitry 1460). For example, the circuitry 1450 may enable the device 1405 to send communications.

[0213] like Fig.14As shown, the apparatus 1405 may include code (code 1465) for sending a communication stored in the computer-readable medium 1325. For example, the code 1455, when executed by the processor 1320, may cause the processor 1320 to cause the transceiver 1330 to send a communication.

[0214] Fig.14 are provided as examples. Other examples can be combined with Fig.14 The examples described are different.

[0215] Fig.15 is a diagram of an example apparatus 1500 for wireless communication according to the present disclosure. Apparatus 1500 may be a network entity (e.g., base station 110, gateway 450, satellite 440, satellite 490), or a network entity may include apparatus 1500. In some aspects, apparatus 1500 includes a receiving component 1502 and a sending component 1504, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1500 may communicate with another apparatus 1506 (such as a UE, a base station, or another wireless communication device) using receiving component 1502 and sending component 1504. As further shown, apparatus 1500 may include a communication manager 1508. Communication manager 1508 may control and / or otherwise manage one or more operations of receiving component 1502 and / or sending component 1504. In some aspects, communication manager 1508 may include a communication manager 1508 in conjunction with Figure 2 One or more antennas, modems, controllers / processors, memories, or combinations thereof of the described network entities. The communications manager 1508 may be or be similar to Figure 1 and Figure 2 For example, in some aspects, the communication manager 1508 can be configured to perform one or more of the functions described as being performed by the communication manager 150. In some aspects, the communication manager 1508 can include a receiving component 1502 and / or a sending component 1504. The communication manager 1508 can include a transforming component 1510 and / or a buffering component 1512, among others.

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

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

[0218] Transmit 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 may provide the generated communications to transmit component 1504 for transmission to device 1506. In some aspects, transmit 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, transmit component 1504 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network entities. In some aspects, the transmit component 1504 can be co-located with the receive component 1502 in a transceiver.

[0219] In some aspects, the transition component 1510 can obtain an indication of ISL activation that will occur at the activation time at the AS layer. The receiving component 1502 can receive the communication. The buffering component 1512 can buffer the communication in a buffer at the AS layer. The buffering component 1512 can release the communication from the buffer to the upper protocol layer at a release rate that varies between the transition start time and the activation time.

[0220] The transition component 1510 can determine a transition start time based at least in part on the indication. The transition component 1510 can determine a difference between a first propagation delay before the ISL activation and a second propagation delay after the ISL activation based at least in part on the indication. The transition component 1510 can determine a transition start time based at least in part on the difference. The buffer component 1512 can change a release rate by changing a timer associated with a buffer.

[0221] In some aspects, the transition component 1510 can obtain an indication of an ISL deactivation that will occur at the deactivation time at the AS layer. The buffer component 1512 can buffer the communication in a buffer. The buffer component 1512 can release the communication from the buffer at a release rate that changes between the deactivation time and the transition end time. The sending component 1504 can send the communication.

[0222] The transition component 1510 can determine a transition end time based at least in part on the indication.The transition component 1510 can determine a difference between a first propagation delay before the ISL deactivation and a second propagation delay after the ISL deactivation based at least in part on the indication.

[0223] The transition component 1510 can determine a transition end time based at least in part on the difference.The buffer component 1512 can change the release rate by changing a timer associated with the buffer.

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

[0225] Fig.16 is a diagram illustrating an example 1600 of a hardware implementation for an apparatus 1605 employing a processing system 1610 according to the present disclosure. The apparatus 1605 may be a network entity.

[0226] The processing system 1610 may be implemented using a bus architecture, generally represented by bus 1615. Bus 1615 may include any number of interconnecting buses and bridges, depending on the specific application and overall design constraints of the processing system 1610. Bus 1615 links together various circuits including one or more processors and / or hardware components (represented by processor 1620, illustrated components, and computer readable media / memory 1625). Bus 1615 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and / or power management circuits.

[0227] The processing system 1610 may be coupled to a transceiver 1630. The transceiver 1630 is coupled to one or more antennas 1635. The transceiver 1630 provides components for communicating with various other devices through a transmission medium. The transceiver 1630 receives signals from 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). In addition, the transceiver 1630 receives information from the processing system 1610 (specifically, the transmitting component 1504) and generates a signal to be applied to the one or more antennas 1635 based at least in part on the received information.

[0228] The processing system 1610 includes a processor 1620 coupled to a computer readable medium / memory 1625. The processor 1620 is responsible for general processing, including executing software stored on the computer readable medium / memory 1625. The software, when executed by the processor 1620, causes the processing system 1610 to perform the various functions described herein for any particular device. The computer readable medium / memory 1625 may also be used to store data manipulated by the processor 1620 when executing the software. The processing system also includes at least one of the illustrated components. A component may be a software module running in the processor 1620, resident / stored in the computer readable medium / memory 1625, one or more hardware modules coupled to the processor 1620, or some combination thereof.

[0229] In some aspects, the processing system 1610 may be a component of the UE 120 and may include the memory 282 and / or at least one of the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In some aspects, the apparatus 1605 for wireless communication includes: a component for obtaining an indication of an ISL activation to occur at an activation time at the AS layer; a component for receiving a communication; a component for buffering the communication in a buffer at the AS layer; and / or a component for releasing the communication from the buffer to an upper protocol layer at a release rate that varies between a transition start time and an activation time. In some aspects, the apparatus 1605 for wireless communication includes: a component for obtaining an indication of an ISL deactivation to occur at a deactivation time at the AS layer; a component for buffering the communication in a buffer; a component for releasing the communication from the buffer at a release rate that varies between a deactivation time and a transition end time; and / or a component for sending the communication. The aforementioned means may be one or more of the aforementioned components of the processing system 1610 of the apparatus 1500 and / or the apparatus 1605 configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system 1610 may include the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280. In one configuration, the aforementioned means may be the TX MIMO processor 266, the RX processor 258, and / or the controller / processor 280 configured to perform the functions and / or operations recited herein.

[0230] In some aspects, the processing system 1610 may be a component of the base station 110 and may include the memory 242 and / or at least one of the TX MIMO processor 230, the RX processor 238, and / or the controller / processor 240. In some aspects, the apparatus 1605 for wireless communication includes: means for obtaining an indication of ISL activation to occur at an activation time at the AS layer; means for receiving a communication; means for buffering the communication in a buffer at the AS layer; and / or means for releasing the communication from the buffer to an upper protocol layer at a release rate that varies between a transition start time and an activation time. In some aspects, the apparatus 1605 for wireless communication includes: means for obtaining an indication of ISL deactivation to occur at a deactivation time at the AS layer; means for buffering the communication in a buffer; means for releasing the communication from the buffer at a release rate that varies between a deactivation time and a transition end time; and / or means for sending the communication. The aforementioned means may be one or more of the aforementioned components of the processing system 1610 of the apparatus 1500 and / or the apparatus 1605 configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system 1610 may include the TX MIMO processor 230, the receive processor 238, and / or the controller / processor 240. In one configuration, the aforementioned means may be the TX MIMO processor 230, the receive processor 238, and / or the controller / processor 240 configured to perform the functions and / or operations recited herein.

[0231] Fig.16 are provided as examples. Other examples can be combined with Fig.16 The examples described are different.

[0232] Fig.17 is a diagram of an example 1700 illustrating a specific implementation of code and circuits for an apparatus 1705 according to the present disclosure. The apparatus 1705 may be a network entity, or a network entity may include the apparatus 1705.

[0233] like Fig.17 As shown, the device 1705 may include a circuit (circuit 1720) for obtaining an indication of an ISL transition (e.g., an activation that will occur at an activation time) at the AS layer. For example, the circuit 1720 may enable the device 1705 to obtain an indication of an ISL activation that will occur at the activation time at the AS layer.

[0234] like Fig.17As shown, the apparatus 1705 may include code (code 1725) stored in the computer-readable medium 1625 for obtaining an indication of an ISL transition (e.g., an activation that will occur at an activation time) at the AS layer. For example, the code 1725, when executed by the processor 1620, may cause the processor 1620 to cause the transceiver 1630 to obtain an indication of an ISL activation that will occur at the activation time at the AS layer.

[0235] like Fig.17 As shown, device 1705 may include circuitry for receiving communications (circuitry 1730). For example, circuitry 1730 may enable device 1705 to receive communications.

[0236] like Fig.17 As shown, the apparatus 1705 may include code (code 1735) for receiving a communication stored in the computer-readable medium 1625. For example, the code 1735, when executed by the processor 1620, may cause the processor 1620 to cause the transceiver 1630 to receive a communication.

[0237] like Fig.17 As shown, the device 1705 may include a circuit (circuit 1740) for buffering the communication in a buffer at the AS layer. For example, the circuit 1740 may enable the device 1705 to buffer the communication in a buffer at the AS layer.

[0238] like Fig.17 As shown, the device 1705 may include code (code 1745) for buffering communications in a buffer at the AS layer stored in the computer-readable medium 1625. For example, the code 1745, when executed by the processor 1620, may cause the processor 1620 to buffer communications in a buffer at the AS layer.

[0239] like Fig.17 As shown, the device 1705 may include a circuit (circuit 1750) for releasing communications from the buffer to the upper protocol layer at a release rate that changes between the transition start time and the activation time. For example, the circuit 1750 may enable the device 1705 to release communications from the buffer to the upper protocol layer at a release rate that changes between the transition start time and the activation time.

[0240] like Fig.17 As shown, the device 1705 may include code (code 1755) stored in the computer-readable medium 1625 for releasing communications from the buffer to the upper protocol layer at a release rate that changes between the transition start time and the activation time. For example, the code 1755, when executed by the processor 1620, may cause the processor 1620 to release communications from the buffer to the upper protocol layer at a release rate that changes between the transition start time and the activation time.

[0241] In some aspects, device 1705 may be a network entity, or a network entity may include device 1705 .

[0242] like Fig.17 As shown, the device 1705 may include a circuit (circuit 1720) for obtaining an indication of an ISL transition (e.g., a deactivation that will occur at the deactivation time) at the AS layer. For example, the circuit 1720 may enable the device 1705 to obtain an indication of an ISL deactivation that will occur at the deactivation time at the AS layer.

[0243] like Fig.17 As shown, the apparatus 1705 may include code (code 1725) stored in the computer-readable medium 1625 for obtaining an indication of an ISL transition (e.g., a deactivation that will occur at a deactivation time) at the AS layer. For example, the code 1725, when executed by the processor 1620, may cause the processor 1620 to cause the transceiver 1630 to obtain an indication of an ISL transition (e.g., a deactivation that will occur at a deactivation time) at the AS layer.

[0244] like Fig.17 As shown, the device 1705 may include circuitry for buffering communications in a buffer (circuitry 1740). For example, the circuitry 1730 may enable the device 1705 to buffer communications in a buffer.

[0245] like Fig.17 As shown, the apparatus 1705 may include code (code 1745) for buffering communications in a buffer stored in the computer-readable medium 1625. For example, the code 1735, when executed by the processor 1620, may cause the processor 1620 to buffer communications in a buffer.

[0246] like Fig.17 As shown, the device 1705 may include a circuit (circuit 1750) for releasing communications from the buffer at a release rate that changes between the downtime and the transition end time. For example, the circuit 1740 may enable the device 1705 to release communications from the buffer at a release rate that changes between the downtime and the transition end time.

[0247] like Fig.17 As shown, the device 1705 may include code (code 1755) stored in the computer-readable medium 1625 for releasing communications from the buffer at a release rate that changes between the downtime and the transition end time. For example, when executed by the processor 1620, the code 1745 may cause the processor 1620 to release communications from the buffer at a release rate that changes between the downtime and the transition end time.

[0248] like Fig.17As shown, the device 1705 may include circuitry for sending communications (circuitry 1760). For example, the circuitry 1750 may enable the device 1705 to send communications.

[0249] like Fig.17 As shown, the apparatus 1705 may include code (code 1765) for sending a communication stored in the computer-readable medium 1625. For example, the code 1755, when executed by the processor 1620, may cause the processor 1620 to cause the transceiver 1630 to send a communication.

[0250] Fig.17 are provided as examples. Other examples can be combined with Fig.17 The examples described are different.

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

[0252] Aspect 1: A wireless communication method performed by a wireless communication device, the method comprising: obtaining an indication of an inter-satellite link (ISL) activation that will occur at an activation time at an access stratum (AS) layer; receiving communications; buffering the communications in a buffer at the AS layer; and releasing the communications from the buffer to an upper protocol layer at a release rate that changes between a transition start time and the activation time.

[0253] Aspect 2: The method according to aspect 1, wherein obtaining the indication comprises receiving the indication.

[0254] Aspect 3: The method according to aspect 1 or 2 further comprises: determining the transition start time based at least in part on the indication.

[0255] Aspect 4: The method according to any one of aspects 1 to 3, further comprising: determining a difference between a first propagation delay before the ISL activation and a second propagation delay after the ISL activation based at least in part on the indication.

[0256] Aspect 5: The method according to aspect 4, further comprising: determining the transition start time based at least in part on the difference.

[0257] Aspect 6: The method according to aspect 4 or 5, wherein the buffering rate or the release rate is changed at least in part based on the difference satisfying a threshold.

[0258] Aspect 7: The method according to any one of aspects 4 to 6, wherein the release rate increases in response to the second propagation delay being greater than the first propagation delay.

[0259] Aspect 8: The method according to any one of aspects 4 to 6, wherein the release rate decreases in response to the second propagation delay being less than the first propagation delay.

[0260] Aspect 9: The method according to any one of aspects 1 to 8, wherein the buffering rate or the release rate is changed at least in part based on a function of configuration.

[0261] Aspect 10: The method according to aspect 9, wherein the configured function is a linear function.

[0262] Aspect 11: The method according to aspect 9, wherein the configured function is a non-linear function.

[0263] Aspect 12: The method according to aspect 9, wherein the configured function is a step function.

[0264] Aspect 13: The method according to any one of aspects 1 to 12, further comprising: changing the release rate by changing a timer associated with the buffer.

[0265] Aspect 14: The method according to any one of aspects 1 to 13, wherein the buffering rate or the release rate is changed based at least in part on the delay sensitivity of the service or quality of service flow.

[0266] Aspect 15: The method of any one of aspects 1 to 4, wherein buffering the communication comprises buffering the communication using a buffer activated based at least in part on receiving the indication of activation of the ISL.

[0267] Aspect 16: The method according to any one of aspects 1 to 15, wherein the wireless communication device is a user equipment.

[0268] Aspect 17: The method according to any one of aspects 1 to 15, wherein the wireless communication device is a network entity.

[0269] Aspect 18: A method of wireless communication performed by a user equipment (UE), the method comprising: obtaining an indication of an inter-satellite link (ISL) deactivation that will occur at a deactivation time at an access stratum (AS) layer; buffering communications in a buffer; releasing the communications from the buffer at a release rate that varies between the deactivation time and a transition end time; and sending the communications.

[0270] Aspect 19: The method according to aspect 18, the method further comprising: determining the transition end time based at least in part on the indication.

[0271] Aspect 20: The method according to aspect 18 or 19, the method further comprising: determining a difference between a first propagation delay before the ISL is deactivated and a second propagation delay after the ISL is deactivated based at least in part on the indication.

[0272] Aspect 21: The method according to aspect 20, further comprising: determining the transition end time based at least in part on the difference.

[0273] Aspect 22: The method of aspect 20 or 21, wherein the buffering rate or the release rate is changed based at least in part on the difference satisfying a threshold.

[0274] Aspect 23: The method according to any one of aspects 20 to 22, wherein the buffering rate or the release rate is changed at least in part based on a function of configuration.

[0275] Aspect 24: The method according to any one of aspects 20 to 23, further comprising: changing the release rate by changing a timer associated with the buffer.

[0276] Aspect 25: The method according to any one of aspects 18 to 24, wherein the buffering rate or the release rate is changed based at least in part on the delay sensitivity of the service or quality of service flow.

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

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

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

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

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

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

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

[0284] As used herein, "satisfying a threshold" may mean that a value is greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, or not equal to a threshold, etc., depending on the context.

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

[0286] Any element, action or instruction used herein should not be interpreted as critical or necessary unless clearly stated. In addition, as used herein, the articles "one" and "a kind of" are intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only one item is intended to be referred to, the phrase "only one" or similar terms are used. Moreover, as used herein, the term "having" etc. is intended to be an open term, which does not limit the elements they modify (for example, "having" A elements can also have B). In addition, the phrase "based on" is intended to mean "based at least in part on", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless expressly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A wireless communication device for wireless communication, the wireless communication device comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: obtaining, at an access stratum (AS) layer, an indication of an inter-satellite link (ISL) activation to occur at an activation time; receiving communications; buffering the communication in a buffer at the AS layer; as well as The communications are released from the buffer to an upper protocol layer at a release rate that varies between a transition start time and the activation time. 2 . The wireless communication device of claim 1 , wherein to obtain the indication, the one or more processors are configured to receive the indication. 3 . The wireless communication device of claim 1 , wherein the one or more processors are further configured to determine the transition start time based at least in part on the indication.

4. The wireless communication device of claim 1 , wherein the one or more processors are further configured to determine a difference between a first propagation delay before the ISL activation and a second propagation delay after the ISL activation based at least in part on the indication. 5 . The wireless communication device of claim 4 , wherein the one or more processors are further configured to determine the transition start time based at least in part on the difference.

6. The wireless communication device of claim 4, wherein a buffering rate or the release rate is changed based at least in part on the difference satisfying a threshold.

7. The wireless communication device of claim 4, wherein the release rate increases in response to the second propagation delay being greater than the first propagation delay.

8. The wireless communication device of claim 4, wherein the release rate decreases in response to the second propagation delay being less than the first propagation delay.

9. The wireless communication device of claim 1, wherein a buffering rate or the release rate varies based at least in part on a configured function.

10. The wireless communication device of claim 9, wherein the configured function is a linear function. The wireless communication device of claim 9 , wherein the configured function is a non-linear function.

12. The wireless communication device of claim 9, wherein the configured function is a step function.

13. The wireless communication device of claim 1, wherein the one or more processors are further configured to change the release rate by changing a timer associated with the buffer.

14. The wireless communication device of claim 1, wherein a buffering rate or the release rate varies based at least in part on a delay sensitivity of a service or quality of service flow.

15. The wireless communication device of claim 1, wherein to buffer the communication, the one or more processors are configured to buffer the communication using a buffer activated based at least in part on the indication of the ISL activation.

16. The wireless communication device of claim 1, wherein the wireless communication device is user equipment.

17. The wireless communication device of claim 1, wherein the wireless communication device is a network entity.

18. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory, the one or more processors configured to: obtaining, at an access stratum (AS) layer, an indication of an inter-satellite link (ISL) deactivation to occur at a deactivation time; buffering the communication in a buffer; releasing the communications from the buffer at a release rate that varies between the inactivity time and a transition end time; and The communication is sent.

19. The UE of claim 18, wherein the one or more processors are further configured to determine the transition end time based at least in part on the indication.

20. The UE of claim 18, wherein the one or more processors are further configured to determine a difference between a first propagation delay before the ISL deactivation and a second propagation delay after the ISL deactivation based at least in part on the indication.

21. The UE of claim 20, wherein the one or more processors are further configured to determine the transition end time based at least in part on the difference.

22. The UE of claim 20, wherein a buffering rate or the release rate is changed based at least in part on the difference satisfying a threshold.

23. The UE of claim 20, wherein a buffering rate or the release rate varies based at least in part on a configured function.

24. The UE of claim 20, wherein the one or more processors are further configured to change the release rate by changing a timer associated with the buffer.

25. The UE of claim 18, wherein a buffering rate or the release rate is varied based at least in part on a delay sensitivity of a service or quality of service flow.

26. A method of wireless communication performed at a wireless communication device, the method comprising: obtaining, at an access stratum (AS) layer, an indication of an inter-satellite link (ISL) activation to occur at an activation time; receiving communications; buffering the communication in a buffer at the AS layer; as well as The communications are released from the buffer to an upper protocol layer at a release rate that varies between a transition start time and the activation time.

27. The method according to claim 26, further comprising: The transition start time is determined based at least in part on the indication.

28. The method of claim 26, wherein the buffering rate or the release rate is varied based at least in part on a configured function.

29. A method of performing wireless communications at a user equipment (UE), the method comprising: obtaining, at an access stratum (AS) layer, an indication of an inter-satellite link (ISL) deactivation to occur at a deactivation time; buffering the communication in a buffer; releasing the communication from the buffer at a release rate that varies between the inactivity time and a transition end time; and The communication is sent.

30. The method according to claim 29, further comprising: The transition end time is determined based at least in part on the indication.

Images