Repeated transmissions for non-terrestrial networks

Abstract

Methods, systems, and devices for wireless communications are described. A core network node may send a transmission request message to a first network entity, which may forward the transmission request message to another network entity. The first network entity may forward the transmission request message to the second network entity immediately upon reception, after transmitting a threshold quantity of repetition of the message, after a timer has expired, or upon receiving a request to do so. Additionally, or alternatively, the core network node may send the transmission request message to a buffering node (e.g., a geosynchronous orbit (GSO) satellite), which may then forward the transmission request message to a next the core network node may send the transmission request message to a buffering node (e.g., a stationary GSO satellite), which may then forward the transmission request message to a next network entity.

Description

REPEATED TRANSMISSIONS FOR NON-TERRESTRIAL NETWORKSCROSS REFERENCE

[0001] The present Application for Patent claims the benefit of India Provisional Patent Application No. 202421019087 by UCHINO et al., entitled “REPEATED TRANSMISSIONS FOR NON-TERRESTRIAL NETWORKS,” filed March 15, 2024, assigned to the assignee hereof, and expressly incorporated by reference in its entirety herein.FIELD OF TECHNOLOGY

[0002] The following relates to wireless communications, including repeated transmissions for non-terrestrial networks.BACKGROUND

[0003] Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE- Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems. These systems may employ technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE).SUMMARY

[0004] The described techniques relate to improved methods, systems, devices, and apparatuses that support repeated transmissions (e.g., of messages) for non-terrestrialnetworks (NTNs). For example, a core network node may send a transmission request message to a first network entity, which may forward the transmission request message to another network entity. The first network entity may forward the transmission request message to the second network entity immediately upon reception, after transmitting a threshold quantity of repetition of the message, after a timer has expired, or upon receiving a request to do so. The first network entity may include, with the forwarded transmission request message, an indication of how many repetition of the message have already been transmitted (e.g., so that the next network entity knows how many repetitions remain before the transmission request message is satisfied). In some examples, each network entity may transmit a status message including a completion status to the core network entity. In some examples, each network entity may forward, along with the transmission request message, network entity identification information and an updated completion status, and the last or assigned network entity may transmit a status message including a list of network entity identifiers and a list of completion statuses across the various network entities (e.g., indicating whether the requested transmission by the multiple network entities has been successfully completed). Additionally, or alternatively, the core network node may send the transmission request message to a buffering node (e.g., a geosynchronous orbit (GSO) satellite), which may then forward the transmission request message to a next the core network node may send the transmission request message to a buffering node (e.g., a stationary GSO satellite), which may then forward the transmission request message to a next network entity.

[0005] A method for wireless communications by a first network entity is described. The method may include obtaining, by the first network entity, a transmission request message from a core network node indicating a message for transmission within a first coverage area and forwarding, by the first network entity, the transmission request message to a second network entity based on the second network entity being scheduled to serve the first coverage area.

[0006] A first network entity for wireless communications is described. The first network entity may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause thefirst network entity to obtain, by the first network entity, a transmission request message from a core network node indicating a message for transmission within a first coverage area and forwarding, by the first network entity, the transmission request message to a second network entity based on the second network entity being scheduled to serve the first coverage area.

[0007] Another first network entity for wireless communications is described. The first network entity may include means for obtaining, by the first network entity, a transmission request message from a core network node indicating a message for transmission within a first coverage area and means for forwarding, by the first network entity, the transmission request message to a second network entity based on the second network entity being scheduled to serve the first coverage area.

[0008] A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to obtain, by the first network entity, a transmission request message from a core network node indicating a message for transmission within a first coverage area and forwarding, by the first network entity, the transmission request message to a second network entity based on the second network entity being scheduled to serve the first coverage area.

[0009] Some examples of the method, first network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for obtaining, from the second network entity, a response message indicating that the second network entity may have received the forwarded transmission request message.

[0010] Some examples of the method, first network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for changing a coverage area served by the first network entity from the first coverage area to a second coverage area, where forwarding the transmission request message to the second network entity may be based on changing the coverage area served by the first network entity.

[0011] Some examples of the method, first network entities, and non-transitory computer-readable medium described herein may further include operations, features,means, or instructions for outputting, within the first coverage area, a threshold quantity of repetitions of the message according to the transmission request message, where forwarding the transmission request message to the second network entity may be based on transmitting the threshold quantity of repetitions of the message.

[0012] Some examples of the method, first network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for initiating a timer upon obtaining the transmission request message, where forwarding the transmission request message to the second network entity may be based on expiration of the timer.

[0013] Some examples of the method, first network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for obtaining a request for the transmission request message from the second network entity, where forwarding the transmission request message to the second network entity may be based at least in part obtaining the request for the transmission request message.

[0014] Some examples of the method, first network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting, within the first coverage area, a first quantity of repetitions of a set of multiple repetitions of the message indicated by the transmission request message and outputting, in the forwarded transmission request message, an indication of the first quantity of repetitions of the set of multiple repetitions of the message, an indication of a second quantity of remaining repetitions of the set of multiple repetitions of the message, an indication of a total quantity of the set of multiple repetitions indicated by the transmission request message, or any combination thereof.

[0015] Some examples of the method, first network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting, to the core network node, a status message indicating a completion status of the message.

[0016] Some examples of the method, first network entities, and non-transitory computer-readable medium described herein may further include operations, features,means, or instructions for outputting, in the forwarded transmission request message, identifier information corresponding to the first network entity and a completion status of the message.

[0017] A method for wireless communications by a second network entity is described. The method may include changing a coverage area served by the second network entity to a first coverage area from a second coverage area, obtaining, from a first network entity and based on the second network entity being scheduled to serve the first coverage area, a forwarded transmission request message indicating a message for transmission within the first coverage area, and outputting, within the first coverage area, one or more repetitions of the message according to the forwarded transmission request message.

[0018] A second network entity for wireless communications is described. The second network entity may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the second network entity to change a coverage area served by the second network entity to a first coverage area from a second coverage area, obtain, from a first network entity and based on the second network entity being scheduled to serve the first coverage area, a forwarded transmission request message indicating a message for transmission within the first coverage area, and output, within the first coverage area, one or more repetitions of the message according to the forwarded transmission request message.

[0019] Another second network entity for wireless communications is described. The second network entity may include means for changing a coverage area served by the second network entity to a first coverage area from a second coverage area, means for obtaining, from a first network entity and based on the second network entity being scheduled to serve the first coverage area, a forwarded transmission request message indicating a message for transmission within the first coverage area, and means for outputting, within the first coverage area, one or more repetitions of the message according to the forwarded transmission request message.

[0020] A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to change a coverage area served by the second network entity to a first coverage area from a second coverage area, obtain, from a first network entity and based on the second network entity being scheduled to serve the first coverage area, a forwarded transmission request message indicating a message for transmission within the first coverage area, and output, within the first coverage area, one or more repetitions of the message according to the forwarded transmission request message.

[0021] Some examples of the method, second network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting, to the first network entity, a response message indicating that the second network entity may have received the forwarded transmission request message.

[0022] Some examples of the method, second network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for obtaining, in the forwarded transmission request message, an indication of a first quantity of repetitions of a set of multiple repetitions of the message output by the first network entity, an indication of a second quantity of remaining repetitions of the set of multiple repetitions of the message, an indication of a total quantity of the set of multiple repetitions indicated by the forwarded transmission request message, or any combination thereof, and where outputting the one or more repetitions of the message includes outputting one or more additional repetitions of the message based on the first quantity of repetitions, the second quantity of remaining repetitions, the total quantity of the set of multiple repetitions, or any combination thereof.

[0023] Some examples of the method, second network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting, to a core network node, a status message indicating identifier information corresponding to the second network entity and a completion status of the message, the completion status including an indication of a portion of the total quantity of the set of multiple repetitions including the first quantity of repetitions and the one or more additional repetitions.

[0024] Some examples of the method, second network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting, to a core network node, a status message indicating identifier information corresponding to the second network entity and a completion status of the message, the completion status including an indication of a failure to transmit one or more repetitions of the message.

[0025] Some examples of the method, second network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for outputting a message to a third network entity, the message including the transmission request message, identifier information corresponding to the second network entity, and an indication of a completion status of the message, the completion status including an indication of a portion of the total quantity of the set of multiple repetitions including the first quantity of repetitions and the one or more additional repetitions.

[0026] Some examples of the method, second network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for obtaining, in the forwarded transmission request message, an indication of a first quantity of repetitions of a set of multiple repetitions of the message output by the first network entity, an indication of a second quantity of remaining repetitions of the set of multiple repetitions of the message, an indication of a total quantity of the set of multiple repetitions indicated by the forwarded transmission request message, or any combination thereof, where outputting the one or more repetitions of the message includes outputting the second quantity of remaining repetitions of the set of multiple repetitions of the message and outputting, to a core network node, a status message indicating identifier information corresponding to a set of multiple network entities including the first network entity and the second network entity and further indicating a completion status of the message, the completion status including an indication of successful transmission of the total quantity of the set of multiple repetitions of the message.

[0027] Some examples of the method, second network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for obtaining, from a core network node, control signalingindicating endpoint information corresponding to a geostationary buffering node, where the second network entity includes a geostationary buffering node, the forwarded transmission request message may be received from the core network node via the buffering node, and where obtaining the forwarded transmission request message may be based on the endpoint information.

[0028] A method for wireless communications by a third network entity is described. The method may include obtaining a transmission request message from a core network node indicating a message for transmission within a first coverage area, buffering the transmission request message while a first network entity is scheduled to serve the first coverage area, and forwarding the transmission request message to a second network entity based on the second network entity being scheduled to serve the first coverage area.

[0029] A third network entity for wireless communications is described. The third network entity may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the third network entity to obtain a transmission request message from a core network node indicating a message for transmission within a first coverage area, buffer the transmission request message while a first network entity is scheduled to serve the first coverage area, and forward the transmission request message to a second network entity based on the second network entity being scheduled to serve the first coverage area.

[0030] Another third network entity for wireless communications is described. The third network entity may include means for obtaining a transmission request message from a core network node indicating a message for transmission within a first coverage area, means for buffering the transmission request message while a first network entity is scheduled to serve the first coverage area, and means for forwarding the transmission request message to a second network entity based on the second network entity being scheduled to serve the first coverage area.

[0031] A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to obtain a transmission request message from a core network nodeindicating a message for transmission within a first coverage area, buffer the transmission request message while a first network entity is scheduled to serve the first coverage area, and forward the transmission request message to a second network entity based on the second network entity being scheduled to serve the first coverage area.

[0032] Some examples of the method, third network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for obtaining satellite movement information associated with the second network entity from an Operations, Administration and Maintenance node , where buffering the transmission request message and forwarding the transmission request message may be based on the satellite movement information.

[0033] Some examples of the method, third network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for obtaining a request message from the second network entity requesting the transmission request message, where forwarding the transmission request message may be based on obtaining the request message.BRIEF DESCRIPTION OF THE DRAWINGS

[0034] FIG. 1 shows an example of a wireless communications system that supports repeated transmissions for non-terrestrial networks (NTNs) in accordance with one or more aspects of the present disclosure.

[0035] FIG. 2 shows an example of a wireless communications system that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure.

[0036] FIG. 3 shows an example of a process flow that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure.

[0037] FIG. 4 shows an example of a process flow that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure.

[0038] FIG. 5 shows an example of a process flow that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure.

[0039] FIG. 6 shows an example of a process flow that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure.

[0040] FIG. 7 shows an example of a wireless communications system that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure.

[0041] FIGs. 8 and 9 show block diagrams of devices that support repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure.

[0042] FIG. 10 shows a block diagram of a communications manager that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure.

[0043] FIG. 11 shows a diagram of a system including a device that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure.

[0044] FIGs. 12 and 13 show block diagrams of devices that support repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure.

[0045] FIG. 14 shows a block diagram of a communications manager that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure.

[0046] FIG. 15 shows a diagram of a system including a device that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure.

[0047] FIGs. 16 and 17 show block diagrams of devices that support repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure.

[0048] FIG. 18 shows a block diagram of a communications manager that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure.

[0049] FIG. 19 shows a diagram of a system including a device that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure.

[0050] FIGs. 20 through 22 show flowcharts illustrating methods that support repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure.DETAILED DESCRIPTION

[0051] Some wireless networks may support non-terrestrial network (NTN) devices (e.g., satellites with network entities on-board). Such network entities may orbit over multiple coverage areas for various user equipments (UEs), such that over time the network entities may serve different geographic areas. In some cases, a core network node (e.g., an access and mobility function (AMF)) may trigger broadcast or other signaling by a network entity. For example, the AMF may send a transmission request message (e.g., requesting transmission of one or more repetitions of a message, such as a broadcast message or a multicast message) to one or more NTN network entities indicating a message to be send to a target coverage area served by the recipient network entity. However, that network entity may orbit out of or away from a coverage area for the scheduled message. If a feeder link between the AMF and a subsequent NTN network entity (e.g., that orbits into the target coverage area) is unavailable, the AMF may be unable to send another transmission request message to the next NTN network entity that orbits into the intended coverage area of the scheduled transmission. The mobile NTN network entity may therefore fail to deliver the message to the UEs in the coverage area. In some cases, such scenarios may result in failed messages or incomplete transmitting, one or more users that fail to receive a message, decreased user experience, and increased system delays. In some cases (e.g., if the message is anemergency notification), failure to transmit (e.g., broadcast) the message may result in a failure to indicate danger to various users, and an increased risk of physical danger.

[0052] The AMF may send the transmission request message to a first NTN network entity, which may forward the transmission request message to another NTN network entity. The first NTN network entity may forward the transmission request message to the second NTN network entity immediately upon reception, after transmitting a threshold quantity of repetition of the message, after a timer has expired, or upon receiving a request to do so. The first network entity may include, with the forwarded transmission request message, an indication of how many repetition of the message have already been transmitted (e.g., so that the next NTN network entity knows how many repetitions remain before the transmission request message is satisfied). In some examples, each NTN network entity may transmit a status message including a completion status to the AMF. In some examples, each NTN network entity may forward, along with the transmission request message, network entity identification information and an updated completion status, and the last or assigned NTN network entity may transmit a status message including a list of network entity identifiers and a list of completion statuses across the various NTN network entities (e.g., indicating whether the requested transmission by the multiple NTN network entities has been successfully completed). Additionally, or alternatively, the AMF may send the transmission request message to a buffering node (e.g., a geosynchronous orbit (GSO) satellite), which may then forward the transmission request message to a next NTN the AMF may send the transmission request message to a buffering node (e.g., a stationary GSO satellite), which may then forward the transmission request message to a next NTN network entity.

[0053] Aspects of the disclosure are initially described in the context of wireless communications systems and process flows. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to repeated transmissions for NTNs.

[0054] FIG. 1 shows an example of a wireless communications system 100 that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure. The wireless communications system 100 may include one or more devices, such as one or more network devices (e.g., network entities 105), one or moreUEs 115, and a core network 130. In some examples, the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE- Advanced (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0055] The network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities. In various examples, a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature. In some examples, network entities 105 and UEs 115 may wirelessly communicate via communication link(s) 125 (e.g., a radio frequency (RF) access link). For example, a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish the communication link(s) 125. The coverage area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs).

[0056] The UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times. The UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices in the wireless communications system 100 (e.g., other wireless communication devices, including UEs 115 or network entities 105), as shown in FIG. 1.

[0057] As described herein, a node of the wireless communications system 100, which may be referred to as a network node, or a wireless node, may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be a UE 115. As another example, a node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of thisexample, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.

[0058] In some examples, network entities 105 may communicate with a core network 130, or with one another, or both. For example, network entities 105 may communicate with the core network 130 via backhaul communication link(s) 120 (e.g., in accordance with an SI, N2, N3, or other interface protocol). In some examples, network entities 105 may communicate with one another via backhaul communication link(s) 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via the core network 130). In some examples, network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol), or any combination thereof. The backhaul communication link(s) 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) or one or more wireless links (e.g., a radio link, a wireless optical link), among other examples or various combinations thereof. A UE 115 may communicate with the core network 130 via a communication link 155.

[0059] One or more of the network entities 105 or network equipment described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next-generation NodeB or giga-NodeB (either of which may be referred to as a gNB), a 5GNB, a next-generation eNB (ng-eNB), a Home NodeB, a Home eNodeB, or other suitable terminology). In some examples, a networkentity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within one network entity (e.g., a network entity 105 or a single RAN node, such as a base station 140).

[0060] In some examples, a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture), which may be configured to utilize a protocol stack that is physically or logically distributed among multiple network entities (e.g., network entities 105), such as an integrated access and backhaul (IAB) network, an open RAN (0-RAN) (e.g., a network configuration sponsored by the 0-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, a network entity 105 may include one or more of a central unit (CU), such as a CU 160, a distributed unit (DU), such as a DU 165, a radio unit (RU), such as an RU 170, a RAN Intelligent Controller (RIC), such as an RIC 175 (e.g., a Near-Real Time RIC (Near-RT RIC), a Non-Real Time RIC (Non-RT RIC)), a Service Management and Orchestration (SMO) system, such as an SMO system 180, or any combination thereof. An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmission reception point (TRP). One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more of the network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0061] The split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170. For example, a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack. In some examples, the CU 160 may host upper protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), service dataadaptation protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 (e.g., one or more CUs) may be connected to a DU 165 (e.g., one or more DUs) or an RU 170 (e.g., one or more RUs), or some combination thereof, and the DUs 165, RUs 170, or both may host lower protocol layers, such as layer 1 (LI) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or multiple different cells (e.g., via one or multiple different RUs, such as an RU 170). In some cases, a functional split between a CU 160 and a DU 165 or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170). A CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU 160 may be connected to a DU 165 via a midhaul communication link 162 (e.g., Fl, Fl-c, Fl-u), and a DU 165 may be connected to an RU 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities (e.g., one or more of the network entities 105) that are in communication via such communication links.

[0062] In some wireless communications systems (e.g., the wireless communications system 100), infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130). In some cases, in an IAB network, one or more of the network entities 105 (e.g., network entities 105 or IAB node(s) 104) may be partially controlled by each other. The IAB node(s) 104 may be referred to as a donor entity or an IAB donor. A DU 165 or an RU 170 may be partially controlled by a CU 160 associated with a network entity 105 or base station 140 (such as a donor network entity or a donor base station). The one or more donorentities (e.g., IAB donors) may be in communication with one or more additional devices (e.g., IAB node(s) 104) via supported access and backhaul links (e.g., backhaul communication link(s) 120). IAB node(s) 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DUs 165) of a coupled IAB donor. An IAB-MT may be equipped with an independent set of antennas for relay of communications with UEs 115 or may share the same antennas (e.g., of an RU 170) of IAB node(s) 104 used for access via the DU 165 of the IAB node(s) 104 (e.g., referred to as virtual IAB-MT (vIAB-MT)). In some examples, the IAB node(s) 104 may include one or more DUs (e.g., DUs 165) that support communication links with additional entities (e.g., IAB node(s) 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream). In such cases, one or more components of the disaggregated RAN architecture (e.g., the IAB node(s) 104 or components of the IAB node(s) 104) may be configured to operate according to the techniques described herein.

[0063] For instance, an access network (AN) or RAN may include communications between access nodes (e.g., an IAB donor), IAB node(s) 104, and one or more UEs 115. The IAB donor may facilitate connection between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node with a wired or wireless connection to the core network 130. The IAB donor may include one or more of a CU 160, a DU 165, and an RU 170, in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node(s) 104 may communicate via an Fl interface according to a protocol that defines signaling messages (e.g., an Fl AP protocol). Additionally, or alternatively, the CU 160 may communicate with the core network 130 via an interface, which may be an example of a portion of a backhaul link, and may communicate with other CUs (e.g., including a CU 160 associated with an alternative IAB donor) via an Xn-C interface, which may be an example of another portion of a backhaul link.

[0064] IAB node(s) 104 may refer to RAN nodes that provide IAB functionality (e.g., access for UEs 115, wireless self-backhauling capabilities). A DU 165 may act as a distributed scheduling node towards child nodes associated with the IAB node(s) 104, and the IAB-MT may act as a scheduled node towards parent nodes associated with IABnode(s) 104. That is, an IAB donor may be referred to as a parent node in communication with one or more child nodes (e.g., an IAB donor may relay transmissions for UEs through other IAB node(s) 104). Additionally, or alternatively, IAB node(s) 104 may also be referred to as parent nodes or child nodes to other IAB node(s) 104, depending on the relay chain or configuration of the AN. The IAB-MT entity of IAB node(s) 104 may provide a Uu interface for a child IAB node (e.g., the IAB node(s) 104) to receive signaling from a parent IAB node (e.g., the IAB node(s) 104), and a DU interface (e.g., a DU 165) may provide a Uu interface for a parent IAB node to signal to a child IAB node or UE 115.

[0065] For example, IAB node(s) 104 may be referred to as parent nodes that support communications for child IAB nodes, or may be referred to as child IAB nodes associated with IAB donors, or both. An IAB donor may include a CU 160 with a wired or wireless connection (e.g., backhaul communication link(s) 120) to the core network 130 and may act as a parent node to IAB node(s) 104. For example, the DU 165 of an IAB donor may relay transmissions to UEs 115 through IAB node(s) 104, or may directly signal transmissions to a UE 115, or both. The CU 160 of the IAB donor may signal communication link establishment via an Fl interface to IAB node(s) 104, and the IAB node(s) 104 may schedule transmissions (e.g., transmissions to the UEs 115 relayed from the IAB donor) through one or more DUs (e.g., DUs 165). That is, data may be relayed to and from IAB node(s) 104 via signaling via an NR Uu interface to MT of IAB node(s) 104 (e.g., other IAB node(s)). Communications with IAB node(s) 104 may be scheduled by a DU 165 of the IAB donor or of IAB node(s) 104.

[0066] In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support test as described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., components such as an IAB node, a DU 165, a CU 160, an RU 170, an RIC 175, an SMO system 180).

[0067] A UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, aterminal, or a client, among other examples. A UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (loT) device, an Internet of Everything (loE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, vehicles, or meters, among other examples.

[0068] The UEs 115 described herein may be able to communicate with various types of devices, such as UEs 115 that may sometimes operate as relays, as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.

[0069] The UEs 115 and the network entities 105 may wirelessly communicate with one another via the communication link(s) 125 (e.g., one or more access links) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined PHY layer structure for supporting the communication link(s) 125. For example, a carrier used for the communication link(s) 125 may include a portion of an RF spectrum band (e.g., a bandwidth part (BWP)) that is operated according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105. For example, the terms “transmitting,” “receiving,” or “communicating,” when referring to a network entity 105, may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RANcommunicating with another device (e.g., directly or via one or more other network entities, such as one or more of the network entities 105).

[0070] In some examples, such as in a carrier aggregation configuration, a carrier may have acquisition signaling or control signaling that coordinates operations for other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute RF channel number (EARFCN)) and may be identified according to a channel raster for discovery by the UEs 115. A carrier may be operated in a standalone mode, in which case initial acquisition and connection may be conducted by the UEs 115 via the carrier, or the carrier may be operated in a non- standalone mode, in which case a connection is anchored using a different carrier (e.g., of the same or a different RAT).

[0071] The communication link(s) 125 of the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network entity 105 to a UE 115, uplink transmissions (e.g., return link transmissions) from a UE 115 to a network entity 105, or both, among other configurations of transmissions. Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode).

[0072] A carrier may be associated with a particular bandwidth of the RF spectrum and, in some examples, the carrier bandwidth may be referred to as a “system bandwidth” of the carrier or the wireless communications system 100. For example, the carrier bandwidth may be one of a set of bandwidths for carriers of a particular RAT (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of the wireless communications system 100 (e.g., the network entities 105, the UEs 115, or both) may have hardware configurations that support communications using a particular carrier bandwidth or may be configurable to support communications using one of a set of carrier bandwidths. In some examples, the wireless communications system 100 may include network entities 105 or UEs 115 that support concurrent communications using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured for operating using portions (e.g., a sub-band, a BWP) or all of a carrier bandwidth.

[0073] Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication. A wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam), and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.

[0074] One or more numerologies for a carrier may be supported, and a numerology may include a subcarrier spacing (A ) and a cyclic prefix. A carrier may be divided into one or more BWPs having the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time and communications for the UE 115 may be restricted to one or more active BWPs.

[0075] The time intervals for the network entities 105 or the UEs 115 may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts= l / (A / mflx■ Ay) seconds, for which fmaxmay represent a supported subcarrier spacing, and Ay may represent a supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0076] Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may befurther divided into a quantity of slots. Alternatively, each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing. Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period). In some wireless communications systems, such as the wireless communications system 100, a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., Ay) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.

[0077] A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., a quantity of symbol periods in a TTI) may be variable. Additionally, or alternatively, the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0078] Physical channels may be multiplexed for communication using a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs 115. For example, one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control informationto UEs 115 (e.g., one or more UEs) or may include UE-specific search space sets for sending control information to a UE 115 (e.g., a specific UE).

[0079] A network entity 105 may provide communication coverage via one or more cells, for example a macro cell, a small cell, a hot spot, or other types of cells, or any combination thereof. The term “cell” may refer to a logical communication entity used for communication with a network entity 105 (e.g., using a carrier) and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), a mapped cell identifier (mapped CID)). In some examples, a cell also may refer to a coverage area 110 or a portion of a coverage area 110 (e.g., a sector) over which the logical communication entity operates. Such cells may range from smaller areas (e.g., a structure, a subset of structure) to larger areas depending on various factors such as the capabilities of the network entity 105. For example, a cell may be or include a building, a subset of a building, or exterior spaces between or overlapping with coverage areas 110, among other examples.

[0080] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by the UEs 115 with service subscriptions with the network provider supporting the macro cell. A small cell may be associated with a network entity 105 operating with lower power (e.g., a base station 140 operating with lower power) relative to a macro cell, and a small cell may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to the UEs 115 with service subscriptions with the network provider or may provide restricted access to the UEs 115 having an association with the small cell (e.g., the UEs 115 in a closed subscriber group (CSG), the UEs 115 associated with users in a home or office). A network entity 105 may support one or more cells and may also support communications via the one or more cells using one or multiple component carriers.

[0081] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband loT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access for different types of devices.

[0082] In some examples, a network entity 105 (e.g., a base station 140, an RU 170) may be movable and therefore provide communication coverage for a moving coverage area, such as the coverage area 110. In some examples, coverage areas 110 (e.g., different coverage areas) associated with different technologies may overlap, but the coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., a network entity 105). In some other examples, overlapping coverage areas, such as a coverage area 110, associated with different technologies may be supported by different network entities (e.g., the network entities 105). The wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 support communications for coverage areas 110 (e.g., different coverage areas) using the same or different RATs.

[0083] The wireless communications system 100 may support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base stations 140) may have similar frame timings, and transmissions from different network entities (e.g., different ones of the network entities 105) may be approximately aligned in time. For asynchronous operation, network entities 105 may have different frame timings, and transmissions from different network entities (e.g., different ones of network entities 105) may, in some examples, not be aligned in time. The techniques described herein may be used for either synchronous or asynchronous operations.

[0084] Some UEs 115, such as MTC or loT devices, may be relatively low cost or low complexity devices and may provide for automated communication between machines (e.g., via Machine-to-Machine (M2M) communication). M2M communication or MTC may refer to data communication technologies that allow devices to communicate with one another or a network entity 105 (e.g., a base station 140) without human intervention. In some examples, M2M communication or MTC may include communications from devices that integrate sensors or meters to measure or capture information and relay such information to a central server or application program that uses the information or presents the information to humans interacting with the application program. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather andgeological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.

[0085] Some UEs 115 may be configured to employ operating modes that reduce power consumption, such as half-duplex communications (e.g., a mode that supports one-way communication via transmission or reception, but not transmission and reception concurrently). In some examples, half-duplex communications may be performed at a reduced peak rate. Other power conservation techniques for the UEs 115 may include entering a power saving deep sleep mode when not engaging in active communications, operating using a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured for operation using a narrowband protocol type that is associated with a defined portion or range (e.g., set of subcarriers or resource blocks (RBs)) within a carrier, within a guard-band of a carrier, or outside of a carrier.

[0086] The wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC). The UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communications may include private communication or group communication and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0087] In some examples, a UE 115 may be configured to support communicating directly with other UEs (e.g., one or more of the UEs 115) via a device-to-device (D2D) communication link, such as a D2D communication link 135 (e.g., in accordance with a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170), which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network entity 105. In some examples, one or more UEs 115 of such a group may beoutside the coverage area 110 of a network entity 105 or may be otherwise unable to or not configured to receive transmissions from a network entity 105. In some examples, groups of the UEs 115 communicating via D2D communications may support a one-to- many (1 :M) system in which each UE 115 transmits to one or more of the UEs 115 in the group. In some examples, a network entity 105 may facilitate the scheduling of resources for D2D communications. In some other examples, D2D communications may be carried out between the UEs 115 without an involvement of a network entity 105.

[0088] In some systems, a D2D communication link 135 may be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UEs 115). In some examples, vehicles may communicate using vehicle-to- everything (V2X) communications, vehicle-to-vehicle (V2V) communications, or some combination of these. A vehicle may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information relevant to a V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure, such as roadside units, or with the network via one or more network nodes (e.g., network entities 105, base stations 140, RUs 170) using vehicle-to- network (V2N) communications, or with both.

[0089] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or 5G core (5GC), which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet,Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet-Switched Streaming Service.

[0090] The wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

[0091] The wireless communications system 100 may also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz, also known as the centimeter band, or using an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz), also known as the millimeter band. In some examples, the wireless communications system 100 may support millimeter wave (mmW) communications between the UEs 115 and the network entities 105 (e.g., base stations 140, RUs 170), and EHF antennas of the respective devices may be smaller and more closely spaced than UHF antennas. In some examples, such techniques may facilitate using antenna arrays within a device. The propagation of EHF transmissions, however, may be subject to even greater attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions that use one or more different frequency regions, and designated use of bands across these frequency regions may differ by country or regulating body.

[0092] The wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system 100 may employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, devicessuch as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA). Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

[0093] A network entity 105 (e.g., a base station 140, an RU 170) or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network entity 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations. A network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115. Likewise, a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.

[0094] The network entities 105 or the UEs 115 may use MIMO communications to exploit multipath signal propagation and increase spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques may be referred to as spatial multiplexing. The multiple signals may, for example, be transmitted by the transmitting device via different antennas or different combinations of antennas. Likewise, the multiple signals may be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), for which multiple spatial layers are transmitted to the same receivingdevice, and multiple-user MIMO (MU-MIMO), for which multiple spatial layers are transmitted to multiple devices.

[0095] Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation).

[0096] A network entity 105 or a UE 115 may use beam sweeping techniques as part of beamforming operations. For example, a network entity 105 (e.g., a base station 140, an RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to conduct beamforming operations for directional communications with a UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by a network entity 105 multiple times along different directions. For example, the network entity 105 may transmit a signal according to different beamforming weight sets associated with different directions of transmission. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device, such as a network entity 105, or by a receiving device, such as a UE 115) a beam direction for later transmission or reception by the network entity 105.

[0097] Some signals, such as data signals associated with a particular receiving device, may be transmitted by a transmitting device (e.g., a network entity 105 or a UE 115) along a single beam direction (e.g., a direction associated with the receivingdevice, such as another network entity 105 or UE 115). In some examples, the beam direction associated with transmissions along a single beam direction may be determined based on a signal that was transmitted along one or more beam directions. For example, a UE 115 may receive one or more of the signals transmitted by the network entity 105 along different directions and may report to the network entity 105 an indication of the signal that the UE 115 received with a highest signal quality or an otherwise acceptable signal quality.

[0098] In some examples, transmissions by a device (e.g., by a network entity 105 or a UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from a network entity 105 to a UE 115). The UE 115 may report feedback that indicates precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more sub-bands. The network entity 105 may transmit a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI- RS)), which may be precoded or unprecoded. The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). Although these techniques are described with reference to signals transmitted along one or more directions by a network entity 105 (e.g., a base station 140, an RU 170), a UE 115 may employ similar techniques for transmitting signals multiple times along different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE 115) or for transmitting a signal along a single direction (e.g., for transmitting data to a receiving device).

[0099] A receiving device (e.g., a UE 115) may perform reception operations in accordance with multiple receive configurations (e.g., directional listening) when receiving various signals from a transmitting device (e.g., a network entity 105), such as synchronization signals, reference signals, beam selection signals, or other control signals. For example, a receiving device may perform reception in accordance with multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets (e.g., different directional listening weightsets) applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as “listening” according to different receive configurations or receive directions. In some examples, a receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal). The single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to- noise ratio (SNR), or otherwise acceptable signal quality based on listening according to multiple beam directions).

[0100] The wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP -based. An RLC layer may perform packet segmentation and reassembly to communicate via logical channels. A MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer also may implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency. In the control plane, an RRC layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network entity 105 or a core network 130 supporting radio bearers for user plane data. A PHY layer may map transport channels to physical channels.

[0101] The UEs 115 and the network entities 105 may support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly via a communication link (e.g., the communication link(s) 125, a D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer in relatively poor radio conditions (e.g., low signal -to-noise conditions). In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data receivedvia a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.

[0102] NTN architecture may support broadcast signaling. Some broadcast signaling may be high priority signaling, such as warning message transfer (e.g., a warning message for various users in a coverage area 225 indicating imminent danger, inclement weather, etc.) and multi-cast and broadcast services (MBS). In case of a warning message transfer, a cell broadcast entity (CBE) may transmit a broadcast request (e.g., an emergency broadcast request) to another node, such as a cell broadcast center function (CBCF) / public warning system (PWS)-interworking function (IWF). The node may send a message transfer (e.g., a NonUeN2Mesage transfer such as a write-Replace Warning Request for next generation radio access network (NG-RAN)) to a core network node (e.g., an AMF). The AMF may respond with a response message (e.g., a NonUeN2MessageTransfer such as a Write-Replace Warning Confirm for NG-RAN). The CBS / PWS-IWF may transmit an Emergency Broadcast Response to the CBE. The AMF may send the warning request (e.g., the Write-Replace Warning Request message) to a network node (e.g., an NG-RAN node such as a network entity 105). The network entity 105 may perform cell broadcast delivery, including alerting one or more users (e.g., transmitting the warning message to one or more UEs 115 located within a coverage area served by the network entity). The network entity 105 may transmit a response message (e.g., a Write-Replace Warning Response message) to the AMF, which may send a notification message (e.g., a NonUeN2InfoNotify message such as a Write-Replace Warning Indication for NG-RAN) to the CBCF / PWS-IWF. The AMF may record a success or failure indication of the message delivery (e.g., in a trace record. However, as described in greater detail with reference to FIG. 2, in some examples, the network entity may be an NTN entity, such as a satellite, in which case the network entity may be mobile and may change coverage areas over time (e.g., potentially interrupting the broadcast of the warning message).

[0103] In some examples, for MBS transmitting, various devices may perform an MBS session establishment for broadcast procedure. For instance, a radio access network (RAN) may advertise a fronthaul slicing architecture (FSA) identifier to a UE 115 (e.g., via a network entity 105). The UE 115, the network entity 105, an AMF, a multicast and broadcast-session management function (MB-SMF), an MB-UPF, anetwork exposure function (NEF) / (multicast broadcast service function (MBSF)), an AMF, or any combination thereof, may perform a temporary mobile group identity (TMGI) allocation, an MBS session creation session, and a service announcement. The MB-SMF may send a request message (e.g., anNamf MBSBroadcast ContextCreateRequest message) to the AMF. The AMF may send a request message (e.g., an N2 message request) to the network entity 105. The network entity 105 may create an MBS session context, and may send a join message (e.g., an internet group management protocol (IGMP) / maximum likelihood detector (MLD) join) to the MB-user plane function (UPF). The network entity 105 may allocate a unicast downlink tunnel, and may send a response message (e.g., an N2 response message ) to the AMF. The AMF may send a response message (e.g., anNamf MBSBroadcast ContextCreate Response) to the MB-SMF. The MB-SM and the MB-UPF may exchange session modification information (e.g., TMGI, N3mb, downlink tunnel information, etc.), the MB-SMF and the NEF / MBSF may exchange session status information, and the NEF / MBSF and the AF may exchange the MBS session status information. In some examples (e.g., after sending the response message to the AMF), the network entity 105 may advertise a TMGI, and may send another response message (e.g., N2 message Response) to the AMF. The AMF may send the MBS broadcast context status notification request to the MB-SMF, which may exchange session modification information with the MB-UPF. The AF may send a media stream to the MB-UPF, which may send the media stream to the network entity 105, and the network entity 105 may send the media transmission to one or more UEs.

[0104] As described herein, a core network node (e.g., an AMF) may send a transmission request message to a first network entity 105, which may forward the transmission request message to another network entity 105. The first network entity 105 may forward the transmission request message to the second network entity 105 immediately upon reception, after transmitting a threshold quantity of repetition of the message, after a timer has expired, or upon receiving a request to do so. The first network entity 105 may include, with the forwarded transmission request message, an indication of how many repetition of the message have already been transmitted (e.g., so that the next network entity 105 knows how many repetitions remain before the transmission request message is satisfied). In some examples, each network entity 105may transmit a status message including a completion status to the core network entity 105. In some examples, each network entity 105 may forward, along with the transmission request message, network entity 105 identification information and an updated completion status, and the last or assigned network entity 105 may transmit a status message including a list of network entity 105 identifiers and a list of completion statuses across the various network entities (e.g., indicating whether the requested transmission by the multiple network entities has been successfully completed). Additionally, or alternatively, the core network node may send the transmission request message to a buffering node (e.g., a geosynchronous orbit (GSO) satellite), which may then forward the transmission request message to a next the core network node may send the transmission request message to a buffering node (e.g., a stationary GSO satellite), which may then forward the transmission request message to a next network entity 105.

[0105] FIG. 2 shows an example of a wireless communications system 200 that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure. The wireless communications system 200 may implement, or be implemented by, aspects of the wireless communications system 100. For example, the wireless communications system 200 may include one or more upper layer node 210 (e.g., such as a CBCF, PWS-IWS, among other examples), a core network node 205 (e.g., such as an AMF), and one or more network entities 105. The network entities 105 may be NTN entities (e.g., satellites). The upper layer node 210, the core network node 205, and the network entities 105, may be examples of corresponding devices described with reference to FIG. 1.

[0106] NTN architecture may support broadcast signaling, among other possible signaling types. Some broadcast signaling may be high priority signaling, such as warning message transfer (e.g., a warning message for various users in a coverage area 225 indicating imminent danger, inclement weather, etc.) and MBS transmitting. In a terrestrial network, a communication relationship between one or more UEs 115 and the network entities 105 may be fixed geographically (e.g., each network entity 105 may be fixed geographically, and may serve a fixed coverage area 225). In such examples (e.g., as described in greater detail with reference to FIG. 1), once a network entity 105 receives a broadcast request from a core network node 205 (e.g., such as an AMF), thestationary network entity 105 may ensure successful broadcast to the geographical area served by the stationary network entity 105. Further, if broadcast is for any reason unsuccessful, another transmission request message can be sent to the network entity 105, which may continue to broadcast to the UEs within the coverage area 225.

[0107] However, in NTN deployments (e.g., a satellite with a network entity on board), a network entity 105 may leave a geographical area due to satellite movement. For example (e.g., at a first instance in time) the network entity 105-a many serve the coverage are 225. Both the network entity 105-a and the network entity 105-b may be in motion, may change coverage areas. For example (e.g., at a second instance in time), the network entity 105-a may have moved away from the coverage area 225 and may no longer be serving the coverage area 225. The network entity 105-b (e.g., which, during the first instance in time was not serving the coverage area 225) may have also changed its position, and may subsequently serve the coverage area 225. One or more additional network entities 105 (e.g., the network entity 105-c) may also be mobile, and may subsequently serve the coverage area 225 (e.g., when the network entity 105-b has also changed its position). Changing position may result in partial or failed broadcasts. For example, the upper layer node 210 may send a transmission request message 215 to the core network node 205. The core network node 205 may send the transmission request message 215 to the network entity 105-a. In some examples, the network entity 105-a may begin to broadcast the message 220. For example, the transmission request message may indicate that network entity 105-a is to send the message 220 a certain number of times (e.g., a threshold quantity of repetitions of the message 220, such as 1, 5, 10, 100, etc.). The network entity 105-a may send a first subset of the repetition of the message 220 (e.g.., 10 of 100), but may subsequently leave the coverage area 225. In such examples, the message 220 may not have been successfully received by some or many UEs 115 located within the coverage area 225. In the case of an emergency message 220, such failure could lead to increased danger and exposure of multiple users, failure to take adequate precautions or to evacuate the area in case of inclement weather or disasters, risks to health or life of users, etc.

[0108] In some examples, to alleviate such risk of failed broadcast, one or more nodes (e.g., the core network node 205, the upper layer node 210, or both) may re-send the transmission request message 215, triggering another message or a continuedbroadcast, of the message 220 by the network entity 105-b. Such resending of the transmission request message 215 may be triggered by movement of the satellites (e.g., triggered by the network entity 105-a leaving the coverage area 225. However, in some cases, a communication link (e.g., a feeder link) between the core network node 205 and one or more network entities 105 (e.g., the network entity 105-b) may be unavailable (e.g., due to temporary interruption, mobility of the network entities 105, interference, technical issues, or the like). In such examples, a high priority message (e.g., a PWS message, an earthquake and tsunami warning system (ETWS), etc.) may not be successfully transmitted to the UEs in the coverage area 225.

[0109] Techniques described herein facilitate forwarding of the transmission request message 215 between network entities 105 to increase the likelihood of successful completion of the message 220 delivery as requested by the transmission request message 215. For example, when a network entity 105 receives a transmission request message 215, the network entity 105 may forward the transmission request message 215 to neighboring (e.g., other) network entities 105. The recipient network entity 105 may then perform transmitting of the message 220 based on the forwarded transmission request message 215. For instance, the transmission request message 215 may indicate a repetitive message, such as a warning message. The core network node 205 may send the transmission request message 215 to the network entity 105. In some examples, the network entity 105-a may initiate broadcast of the message 220 (e.g., may send one or more repetitions of the message 220). The network entity 105-a may also forward the transmission request message 215 to the network entity 105-b (e.g., which may subsequently serve the coverage area 225). The network entity 105-b may then continue (e.g., or begin) to transmit the message 220 to the UEs 115 in the coverage area 225. Such techniques are described in greater detail with reference to FIG. 3. Techniques described herein are applicable for various wireless communications systems (e.g., any radio access technology (RAT), any orbit type, or any type or format of message (e.g., for any type of message 220).

[0110] Techniques described herein are applicable to various types of signaling. For example, techniques described herein may be implemented for broadcast signaling, multicast signaling, or unicast signaling. For example, the upper layer node 210, the core network node 205, or both, may trigger one or more repetitions of a message,among other examples, via a transmission request message for the message to be provided to the coverage area 225. Thus, techniques described herein in the context of one example type of signaling (e.g., broadcast signaling) may be similarly applied to any type of signaling, including multicast signaling (e.g., any signaling generated by a network or upper layer node to be provided by network entities 105 to be provided to a coverage area 225 may be forwarded between network entities 105 to increase the likelihood of successful transmission to the target coverage area) or unicast signaling.

[0111] FIG. 3 shows an example of a process flow 300 that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure. The process flow 300 may implement, or be implemented by, aspects of the wireless communications system 100, and the wireless communications system 200. For example, the process flow may include one or more network entities (e.g., the network entity 105-a, 105-b, and 105-c), and the core network node 305, which may be examples of corresponding devices described with reference to FIGs. 1-2.

[0112] At 310, the core network node 305 may send a transmission request message to a network entity (e.g., the network entity 105-a, currently serving the coverage area 225). At 315, the network entity 105-a may start transmitting the message indicated by the transmission request message received at 310. At 320, the network entity 105-a may forward the transmission request message to another (e.g., neighboring) network entity 105-b. The network entity 105-b may enter the coverage area 225. In some examples, at 325 the network entity 105-b may transmit (e.g., to the network entity 105-a) a response message (e.g., a feedback message, such as an acknowledgment (ACK) message indicating successful receipt of the transmission request message). At 330, the network entity 105-b may start transmitting the message indicated by the forwarded transmission request message.

[0113] In some examples, the network entity 105-b may also forward the transmission request message to another (e.g., neighboring) network entity 105-c. For instance, the transmission request message may indicate 100 repetitions of the message. The network entity 105-a may transmit a first portion of the total quantity of repetitions (e.g., 30 out of the 100 requested repetitions), and the network entity 105-b may also transmit a portion of the total quantity of repetitions (e.g., another 30 out of the 100 requested repetitions). At 335, the network entity 105-b may forward the transmissionrequest message to the network entity 105-c. In some examples, at 340 the network entity 105-c may also transmit a response message (e.g., a feedback message, such as an ACK) to the network entity 105-b. At 345, the network entity 105-c may begin transmitting the message indicated by the forwarded transmission request message at 335.

[0114] In some examples, the network entity 105-c may forward the transmission request message to another network entity 105. For instance, if the network entity 105-c transmits an additional 30 repetitions of the message, then the total quantity of repetitions may still not have been successfully transmitted by the time the network entity 105-c leaves the coverage area 225. In such examples, the network entity 105-c may forward the transmission request message to another network entity 105. In some examples, an initial network entity (e.g., the network entity 105-a that received the transmission request message from the core network node 305) may eventually receive the transmission request message again, and continue transmitting the message. For example, if three satellites in orbit were to maintain coverage of the coverage area 225, then the network entity 105-c may forward the transmission request message to the network entity 105-a (e.g., at 350). In such examples, the network entity 105-a may continue to transmit (e.g., broadcast) the message upon receiving the forwarded transmission request message from the network entity 105-c. For instance, the network entity 105-a may send the final 10 repetition of the message, such that all 100 repetitions of the message have been successfully transmitted (e.g., by the network entity 105-a, the network entity 105-b, and the network entity 105-c) according to the transmission request message.

[0115] Each network entity 105 may determine when to forward the transmission request message to a next network entity 105. Forwarding of the transmission request message to neighboring network entities 105 may be based on one or more rules, one or more triggering conditions, or instructions (e.g., control signaling received from the core network node 305 or from another network entity 105, among other examples). For instance, such rules or triggering conditions may be indicated by the core network node 305, or may be indicated via an Operations, Administration and Maintenance (0AM) node. For instance, the core network node 305 or the 0AM node may indicate ifforwarding is needed, and what triggering conditions, timing, etc., is to be used by the forwarding network entity 105.

[0116] In some examples, the network entity 105-a may forward the transmission request message to another network entity 105 when the transmission request message is received (e.g., immediately upon receipt, or automatically based upon having received the transmission request message).

[0117] In some examples, a network entity 105 may forward the transmission request message to another network entity 105 when a period of time has elapsed after receiving the transmission request message (e.g., when a timer expires). The timer may be separately configured at the network entity, may be indicated in the transmission request message, or otherwise determined by the network entity 105. For instance, upon receiving the transmission request message at 310, the network entity 105-a may initiate a timer, and upon expiration of the timer (e.g., at 320) the network entity 105-a may forward the transmission request message to the network entity 105-b.

[0118] In some examples, the network entity 105 may forward the transmission request message to another network entity when the network entity 105 has transmit the message a threshold quantity of times, or for a threshold amount of time. For instance, the network entity 105-a may forward the transmission request message to the network entity 105-b upon transmission of the message (e.g., at 315) a threshold quantity of times (e.g., after 10 repetitions of the message) or after having transmitted the message for a threshold amount of time.

[0119] In some examples, a network entity 105 may forward the transmission request message to another network entity if the network entity 105 is leaving a service area (e.g., when it does not serve a geographical area such as the coverage area 225). For instance, the network entity 105-a may begin transmitting the message at 315 while serving the coverage area 225. Upon leaving the coverage area (e.g., or just prior to leaving the coverage area, or immediately upon leaving the coverage area) the network entity 105-a may forward the transmission request message to the network entity 105-b (e.g., leaving the coverage area may serve as a trigger for forwarding the transmission request message to another network entity 105).

[0120] In some examples, a network entity 105 may forward the transmission request message to another network entity based on having received a request to perform the forwarding (e.g., from the core network node 305, or from another network entity. For example, the core network node 305 may transmit (e.g., at 310 via the transmission request message, or via separate signaling) a request for the network entity 105-a to froward the transmission request message to the network entity 105-b. In some examples, the network entity 105-a may receive a request (e.g., from the network entity 105-b) to forward the transmission request message to the network entity 105-b. For instance, the network entity 105-b may enter the coverage area 225, and may request any pending or previously indicated transmission request message be forwarded to the network entity 105-b from the previously serving network entity 105-a.

[0121] In some examples, a forwarded transmission request message may be an Xn- AP message. In some examples, a network entity 105 may receive the transmission request message from the core network node 305 (e.g., the AMF), and may copy the message into another message for forwarding to the next network entity. For instance, the transmission request message may be an NG message (e.g., a broadcast request sent by a first NG-RAN node, such as the network entity 105-a, to a second NG-RAN node, such as the network entity 105-b). The network entity 105-a may copy and paste the contents of the transmission request message into a new transmission request message, which may be sent at 320 to the network entity 105-b. In some examples, the transmission request message (e.g., an NG message) may be forwarded in its own NG message (e.g., an NP-message forward, which is sent from the first NG-RAN node to the second NG-RAN node, forwarding an NG-AP message). In either case, the message used to transmit the transmission request message may include an lE / group name, a presence indicator, a range indicator, an IE type and reference indicator, a semantics description, a criticality indicator, and an assigned criticality.

[0122] The message carrying the forwarded transmission request message may include information (e.g., name, endpoint information) corresponding to the core network node 305 (e.g., the AMF) which sends the request message (e.g., at 310). In some examples, the message carrying the forwarded transmission request message may include information (e.g., name, endpoint information) for an AMF to which a response message is to be transmitted (e.g., as described in greater detail with reference to FIGs.4-5). In some examples, as described in greater detail with reference to FIGs. 4-5, the forwarding message including the transmission request message may include information indicating a quantity of transmissions (e.g., a quantity of transmissions completed or remaining). For instance, the message carrying the transmission request message may also indicate a quantity of transmissions (e.g., repetitions of the message) which the forwarding network entity 105 has already completed, an indication of a quantity of transmissions (e.g., repetitions of the message) which the forwarding network entity 105 plans to perform at the point of message forwarding (e.g., a remaining quantity of repetitions of a total quantity of repetitions of the message), an indication of a quantity of transmissions requested (e.g., a quantity of repetitions requested) to the recipient network entity, or any combination thereof. For instance, the network entity 105-a core network node 305 may request that the network entity 105-a perform 100 transmissions of the message, and the network entity 105-a may perform 30 transmissions of the message prior to forwarding the transmission request message to the network entity 105-b at 320. In such examples, the message carrying the forwarded transmission request message may include an indication of 70 remaining repetitions of the message (e.g., an indication of 30 completed repetitions, an indication of 70 remaining repetitions, an indication of the 100 requested repetitions, or any combination thereof).

[0123] In some examples, the core network node 305 may monitor for one or more response messages (e.g., indicating completion or progress towards transmission of the message). For example, a response message may correspond to the transmission request message. In some examples, the transmission request message may include target area information, such as an indication of a cell, an emergency area, a geographic region, or other destination information. The corresponding response message may include identifier information of the transmission request message and a completion status of the message being transmitted (e.g., broadcast) to the requested area (e.g., to a target area, cell, emergency area, or coverage area 225, which may be indicated in the transmission request message).

[0124] One transmission request message (e.g., received by the network entity 105- a at 310) may trigger transmissions by multiple network entities 105 (e.g., by the network entity 105-a, the network entity 105-b, and the network entity 105-c). Thus, thecompletion status at a given target area (e.g., the coverage area 225) may be different over time (e.g., some network entities 105 may successfully transmit the message, and others may not).

[0125] In some examples (e.g., as described in greater detail with reference to FIG. 4), each network entity that receives a transmission request message (e.g., directly from the core network node 305 or forwarded from another network entity 105) may transmit a status message. In some examples (e.g., as described in greater detail with reference to FIG. 5), each network entity 105 may forward, to a next network entity 105 along with the forwarded transmission request message, completion status information, and a last network entity 105 to complete the transmitting of the message may send a status message to the core network node 305. In some examples, an indication of whether each network entity 105 transmits a respective response message, or whether a single (e.g., last) network entity 105 transmits a response message, may be indicated by the core network node 305 (e.g., along with or in the transmission request message 310 or via separate signaling), may be indicated in the transmission request message forwarded across network entities or separately configured (e.g., by the core network node 305) at each network entity 105, may be determined autonomously by the network entities 105 based on one or more conditions, or may be otherwise indicated (e.g., via an 0AM node).

[0126] FIG. 4 shows an example of a process flow 400 that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure. The process flow 400 may implement, or be implemented by, aspects of the wireless communications system 100, the wireless communications system 200, and the process flow 300. For example, the process flow may include one or more network entities (e.g., the network entity 105-a, 105-b, and 105-c), and the core network node 405, which may be examples of corresponding devices described with reference to FIGs. 1-3.

[0127] In some examples, when a network entity 105 receives a request message from the core network node 405, the network entity 105 may send a status message to the core network node 405. The status message may be a Write-Replace Warning Response message (e.g., for PWS). The core network node 405 may expect (e.g., monitor for) responses from multiple network entities 105, and thus may use a longertimer to wait for status message in the case of satellite network entities 105 (e.g., gNB on board moving satellites). If a network entity 105 is unable to send the status message to the core network node 405 (e.g., due to temporary feeder link blockage), then the network entity 105 may forward the status message to another network entity 105.

[0128] At 410, the core network node 405 may send a transmission request message to a network entity (e.g., the network entity 105-a, currently serving the coverage area 225). At 415, the network entity 105-a may start transmitting the message indicated by the transmission request message received at 410. At 420, the network entity 105-a may transmit a status message to the core network node 405. The status message may include a completion status (e.g., such as a success status, indicating partial or entirely successful transmission, an indication of a quantity of repetitions transmitted thus far, or the like). At 425, the network entity 105-a may forward the transmission request message to another (e.g., neighboring) network entity 105-b. The network entity 105-b may enter the coverage area 225. At 430, the network entity 105-b may start transmitting the message indicated by the forwarded transmission request message.

[0129] At 435, the network entity 105-b may transmit a status message with a completion status (e.g., completion status success) to the core network node 405. At 440, the network entity 105-b may forward the transmission request message to the network entity 105-c. At 450 the network entity 105-c may begin transmitting the message as indicated in the forwarded transmission request message. At 455, the network entity 105-c may transmit a status message to the core network node 405 (e.g., indicating a completion status, such as success). At 460, the network entity 105-c may forward the status message to another network entity (e.g., back to the network entity 105-a in the case of three satellites providing service to the coverage area 225).

[0130] In some examples, the completion status in one or more transmission request message s may indicate a failure or a partial success. For example, the status message transmitted by the network entity 105-a at 420 may include an indication of a successful transmission (e.g., completion status: success). However, the network entity 105-b may not successfully perform one or more transmissions, or may fail to receive, decode, or read the forwarded transmission request message (e.g., transmitted by the network entity 105-a at 425). In such examples, the status message transmitted at 435 may indicate a failure status (e.g., completion status: unsuccessful or completion status: partiallysuccessful). In some examples, in response to the indication of failure received at 435, the core network node 405 may transmit the transmission request message to the network entity 105-c (e.g., increasing the likelihood that the network entity 105-c will successfully begin transmitting at 450, because the network entity 105-c may not successfully receive the transmission request message transmitted by the network entity 105-b at 440, or the network entity 105-b may not forward the transmission request message at 440 based on the failure). In such examples, at 450 the network entity 105-c may begin transmitting the message based on the transmission request message received at 445. In some examples, after sending the status message indicating unsuccessful or partially successful transmitting, the network entity 105-b may forward the transmission request message to the network entity 105-c at 440.

[0131] In some examples, as described in greater detail with reference to FIG. 5, a single network entity 105 may transmit a transmission request message to the core network node 405.

[0132] FIG. 5 shows an example of a process flow 500 that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure. The process flow 500 may implement, or be implemented by, aspects of the wireless communications system 100, the wireless communications system 200, the process flow 300, and the process flow 400. For example, the process flow may include one or more network entities (e.g., the network entity 105-a, 105-b, and 105-c), and the core network node 505, which may be examples of corresponding devices described with reference to FIGs. 1-4.

[0133] In some examples, when a network entity 105 forwards the transmission request message, the forwarding network entity 105 may also forward completion information, network entity information, or a combination thereof, in the forwarded transmission request message. The completion information (e.g., completion status information) may include a list of network entities and completion information compiled across multiple forwarding network entities 105. Such information may be included in each transmission request message (e.g., in response to the transmission request message received by the network entity 105-a at 510).

[0134] One network entity 105 may transmit completion status information to the core network node 505 (e.g., and may be referred to as a reporting network entity 105). The reporting network entity 105 may be the network entity that receives the request from the core network node 505 (e.g., the network entity 105-a), may be a network entity 105 that orbits into or out of the coverage area 225 just before the network entity 105 that receives the transmission request message from the core network node 505 at 510 (e.g., the network entity 105-c). The reporting network entity 105 may be the network entity that is indicated by the network node 505 (e.g., or indicated via an 0AM node), or the network entity 105 that detects that a message has become invalid (e.g., a validity timer that has expired).

[0135] For example, at 510, the network entity 105-a may receive the transmission request message from the core network node 505, and at 515 the network entity 105-a may begin transmitting the message 515. In some examples, the network entity 105-a may be configured as the reporting network entity 105 (e.g., via the core network node 505 or an 0AM node). At 520, the network entity 105-a may forward the transmission request message (e.g., including network entity information, completion information, or both). For example, the network entity 105-a may include, in the transmission request message, an indication of an identifier associated with the network entity 105-a, endpoint information (e.g., indicating the network entity 105-a as the reporting network entity), destination information satellite information, a name of the network entity, or any combination thereof. The network entity 105-a may also include a completion status information in the transmission request message (e.g., whether the transmitting was successful, a failure, or partially successful, a quantity of repetitions successfully transmitted, etc.).

[0136] The network entity 105-b may begin transmitting the message at 525, and may forward the transmission request message to the network entity 105-b at 530. The transmission request message may also include network entity information (e.g., identifier, name, endpoint, etc. for the network entity 105-b), completion information, or both. At 535, the network entity 105-c may begin transmitting the message, and at 540 the network entity 105-c may forward the message (e.g., including completion information and network entity information for the network entity 105-c) to the network entity 105-a.

[0137] At 545, the network entity 105-a may transmit a reporting message including completion status information to the core network node 505. The completion status information may include a list of network entity information (e.g., network identifier or name for each of the network entity 105-a, the network entity 105-b, and the network entity 105-c), and a list of completion information (e.g., a list of completion statuses for each of the network entities 105 that attempted to transmit the message according to the received transmission request message), or both.

[0138] FIG. 6 shows an example of a process flow 600 that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure. The process flow 600 may implement, or be implemented by, aspects of the wireless communications system 100, the wireless communications system 200, the process flow 300, the process flow 400, and the process flow 500. For example, the process flow 600 may include one or more network entities (e.g., the network entity 105-a, 105-b, and 105-c), and the core network node 605, which may be examples of corresponding devices described with reference to FIGs. 1-5.

[0139] In some examples, a network entity 105 may experience an error case (e.g., may not be able to receive, decode, or comprehend a forwarded transmission request message). In such examples, network entity 105 may indicate the error to the core network node 605, another network entity 105, or both.

[0140] At 610, the core network node 605 may transmit the transmission request message to the network entity 105-a. The network entity 105-a may begin transmitting the message at 615, and may forward the transmission request message to the network entity 105-b at 620 (e.g., as described in greater detail with reference to FIGs. 2-5).

[0141] At 625, the network entity 105-b may detect a failure (e.g., may experience an error case). For instance, the network entity 105-b may not comprehend some or all of the forwarded transmission request message, or the network entity 105-b may not be able forward the transmission request message to the network entity 105-c, among other examples.

[0142] At 630, the network entity 105-b may transmit an error indication to the network entity 105-a, the network entity 105-c, or both. In some examples, the network entity 105-b may not forward the transmission request message. In some examples, at640, the core network node 605 may transmit the transmission request message to the network entity 105-c, such that the network entity 105-c may begin transmitting the message at 635 and may forward the transmission request message to the network entity 105-a at 645. The core network node 605 may transmit the transmission request message at 640 based on a timer expiring (e.g., based on failing to receive one or more status messages within a given time period, as described in greater detail with reference to FIGs. 4-5), based on a request message from the network entity 105-a or the network entity 105-c, or both (e.g., which may be transmitted responsive to receiving the error indication), or based on a request message (e.g., or error indication) transmitted by the network entity 105-b.

[0143] In some examples, the core network node 605 may transmit the transmission request message to a buffering node, which may forward the transmission request message to one or more additional network entities 105, as described in greater detail with reference to FIG. 7.

[0144] FIG. 7 shows an example of a wireless communications system 700 that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure. The wireless communications system 700 may implement, or be implemented by, aspects of the wireless communications system 100, the wireless communications system 200, the process flow 300, the process flow 400, the process flow 500, and the process flow 600. For example, the wireless communications system 700 may include one or more network entities (e.g., the network entity 105-a, 105-b, and 105-c), and the core network node 605, which may be examples of corresponding devices described with reference to FIGs. 1-5.

[0145] In some examples, as described in greater detail with reference to FIG. 2, an upper layer node 710 may send a message 715 to the core network node 705. The core network node 705 (e.g., and AMF) may transmit the transmission request message 715 to the network entity 105-d, which may send a message 720 (e.g., one or more repetitions of the message 720) to one or more UEs 115 located in the coverage area 725. However, the network entity 105-d may move out of the coverage area 725 (e.g., may change its physical location via orbit such that it no longer serves the coverage area 725) and the network entity 105-e may enter the coverage area 725 (e.g., may change its position such that it now serves the coverage area 725). In such examples, the networkentity 105-d may not successfully complete transmission of the message 720. For instance, the network entity 105-d may transmit a first set of repetitions of the message 720, but may not be able to complete transmission of the total quantity of transmissions indicated by the transmission request message 715. If a feeder link from the core network node 705 is unavailable, then the network entity 105-e may not have access to the transmission request message from the core network node 705.

[0146] In such examples, the core network node 705 may also transmit the transmission request message 715 to a buffering node (e.g., the network entity 105-f). In some examples, the network entity 105-f may be a GSO satellite (e.g., may orbit at the same rotational speed of the earth, thus appearing stationary with reference to the coverage area 725). While the network entity 105-e and the network entity 105-d may change coverage areas over time, the network entity 105-f may maintain its position relative to the coverage area 725, and may thus be able to forward the transmission request message 715 to the network entity 105-e (e.g., in case the network entity 105-d leaves the coverage area 725 prior to completion of the all repetitions of the message 720 b y the network entity 105-d.

[0147] The buffering node (e.g., the network entity 105-f) may receive the transmission request message 715 from the core network node 705. In some examples, the buffering node may receive the transmission request message 715 from another network entity 105 (e.g., the network entity 105-d may transmit the transmission request message to the network entity 105-f, and the network entity 105-f may forward the transmission request message to the network entity 105-e according to the procedures described with reference to FIGs. 2-6).

[0148] The network entity 105-e may receive the transmission request message 715 from the buffering node (e.g., the network entity 105-f). In some examples, the network entity 105-f may forward the transmission request message 715 the network entity 105-e based on satellite movement information (e.g., which may be indicated via an 0AM node), or based on a request message received from a network entity 105 (e.g., a request message from the network entity 105-d to forward the transmission request message 715 to the network entity 105-e, or a request from the network entity 105-e to provide the transmission request message 715 to the network entity 105-e). In some examples, endpoint information of the buffering node may be indicated to one or more networkentities 105, or may be indicated by the core network node 705 to one or more network entities 105.

[0149] FIG. 8 shows a block diagram 800 of a device 805 that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure. The device 805 may be an example of aspects of a network entity as described herein. The device 805 may include a receiver 810, a transmitter 815, and a communications manager 820. The device 805, or one or more components of the device 805 (e.g., the receiver 810, the transmitter 815, the communications manager 820), may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0150] The receiver 810 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). Information may be passed on to other components of the device 805. In some examples, the receiver 810 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 810 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0151] The transmitter 815 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 805. For example, the transmitter 815 may output information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). In some examples, the transmitter 815 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 815 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or anycombination thereof. In some examples, the transmitter 815 and the receiver 810 may be co-located in a transceiver, which may include or be coupled with a modem.

[0152] The communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be examples of means for performing various aspects of repeated transmissions for NTNs as described herein. For example, the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

[0153] In some examples, the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include at least one of a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory).

[0154] Additionally, or alternatively, the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code). If implemented in code executed by at least one processor, the functions of the communications manager 820, the receiver 810, the transmitter 815, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure).

[0155] In some examples, the communications manager 820 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 810, the transmitter 815, or both. For example, the communications manager 820 may be configured to receive or transmit messages or other signaling as described herein via the transmitter 815, the receiver, 810, or both. For example, the communications manager 820 may receive information from the receiver 810, send information to the transmitter 815, or be integrated in combination with the receiver 810, the transmitter 815, or both to obtain information, output information, or perform various other operations as described herein.

[0156] The communications manager 820 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 820 is capable of, configured to, or operable to support a means for obtaining, by the first network entity, a transmission request message from a core network node indicating a message for transmission within a first coverage area. The communications manager 820 is capable of, configured to, or operable to support a means for forwarding, by the first network entity, the transmission request message to a second network entity based on the second network entity being scheduled to serve the first coverage area.

[0157] By including or configuring the communications manager 820 in accordance with examples as described herein, the device 805 (e.g., at least one processor controlling or otherwise coupled with the receiver 810, the transmitter 815, the communications manager 820, or a combination thereof) may support techniques for increasing the likelihood of successful messages by network entities (e.g., NTN network entities), resulting in reduced latency, improved likelihood of successful delivery of transmitting, improved health and safety for users, more efficient utilization of communication resources, and improved user experiences.

[0158] FIG. 9 shows a block diagram 900 of a device 905 that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure. The device 905 may be an example of aspects of a device 805 or a network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communications manager 920. The device 905, or one of more componentsof the device 905 (e.g., the receiver 910, the transmitter 915, the communications manager 920), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0159] The receiver 910 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). Information may be passed on to other components of the device 905. In some examples, the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0160] The transmitter 915 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 905. For example, the transmitter 915 may output information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). In some examples, the transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include or be coupled with a modem.

[0161] The device 905, or various components thereof, may be an example of means for performing various aspects of repeated transmissions for NTNs as described herein. For example, the communications manager 920 may include a transmission request manager 925 a transmission request message forwarding manager 930, or any combination thereof. The communications manager 920 may be an example of aspects of a communications manager 820 as described herein. In some examples, thecommunications manager 920, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 910, the transmitter 915, or both. For example, the communications manager 920 may be configured to receive or transmit messages or other signaling as described herein via the transmitter 915, the receiver, 910, or both For example, the communications manager 920 may receive information from the receiver 910, send information to the transmitter 915, or be integrated in combination with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0162] The communications manager 920 may support wireless communications in accordance with examples as disclosed herein. The transmission request manager 925 is capable of, configured to, or operable to support a means for obtaining, by the first network entity, a transmission request message from a core network node indicating a message for transmission within a first coverage area. The transmission request message forwarding manager 930 is capable of, configured to, or operable to support a means for forwarding, by the first network entity, the transmission request message to a second network entity based on the second network entity being scheduled to serve the first coverage area.

[0163] FIG. 10 shows a block diagram 1000 of a communications manager 1020 that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure. The communications manager 1020 may be an example of aspects of a communications manager 820, a communications manager 920, or both, as described herein. The communications manager 1020, or various components thereof, may be an example of means for performing various aspects of repeated transmissions for NTNs as described herein. For example, the communications manager 1020 may include a transmission request manager 1025, a transmission request message forwarding manager 1030, a response message manager 1035, a transmission manager 1040, a timer manager 1045, a forwarding request manager 1050, a repetition manager 1055, an identification manager 1060, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors,one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses).

[0164] The communications manager 1020 may support wireless communications in accordance with examples as disclosed herein. The transmission request manager 1025 is capable of, configured to, or operable to support a means for obtaining, by the first network entity, a transmission request message from a core network node indicating a message for transmission within a first coverage area. The transmission request message forwarding manager 1030 is capable of, configured to, or operable to support a means for forwarding, by the first network entity, the transmission request message to a second network entity based on the second network entity being scheduled to serve the first coverage area.

[0165] In some examples, the response message manager 1035 is capable of, configured to, or operable to support a means for obtaining, from the second network entity, a response message indicating that the second network entity has received the forwarded transmission request message.

[0166] In some examples, the transmission request message forwarding manager 1030 is capable of, configured to, or operable to support a means for changing a coverage area served by the first network entity from the first coverage area to a second coverage area, where forwarding the transmission request message to the second network entity is based on changing the coverage area served by the first network entity.

[0167] In some examples, the transmission manager 1040 is capable of, configured to, or operable to support a means for outputting, within the first coverage area, a threshold quantity of repetitions of the message according to the transmission request message, where forwarding the transmission request message to the second network entity is based on transmitting the threshold quantity of repetitions of the message.

[0168] In some examples, the timer manager 1045 is capable of, configured to, or operable to support a means for initiating a timer upon obtaining the transmission request message, where forwarding the transmission request message to the second network entity is based on expiration of the timer.

[0169] In some examples, the forwarding request manager 1050 is capable of, configured to, or operable to support a means for obtaining a request for the transmission request message from the second network entity, where forwarding the transmission request message to the second network entity is based at least in part obtaining the request for the transmission request message.

[0170] In some examples, the transmission manager 1040 is capable of, configured to, or operable to support a means for outputting, within the first coverage area, a first quantity of repetitions of a set of multiple repetitions of the message indicated by the transmission request message. In some examples, the repetition manager 1055 is capable of, configured to, or operable to support a means for outputting, in the forwarded transmission request message, an indication of the first quantity of repetitions of the set of multiple repetitions of the message, an indication of a second quantity of remaining repetitions of the set of multiple repetitions of the message, an indication of a total quantity of the set of multiple repetitions indicated by the transmission request message, or any combination thereof.

[0171] In some examples, the response message manager 1035 is capable of, configured to, or operable to support a means for outputting, to the core network node, a status message indicating a completion status of the message.

[0172] In some examples, the identification manager 1060 is capable of, configured to, or operable to support a means for outputting, in the forwarded transmission request message, identifier information corresponding to the first network entity and a completion status of the message.

[0173] FIG. 11 shows a diagram of a system 1100 including a device 1105 that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure. The device 1105 may be an example of or include components of a device 805, a device 905, or a network entity as described herein. The device 1105 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 1120, a transceiver 1110, one or more antennas 1115, at least one memory 1125, code 1130, and at least one processor 1135. These components may be inelectronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1140).

[0174] The transceiver 1110 may support bi-directional communications via wired links, wireless links, or both as described herein. In some examples, the transceiver 1110 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1110 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1105 may include one or more antennas 1115, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver 1110 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1115, by a wired transmitter), to receive modulated signals (e.g., from one or more antennas 1115, from a wired receiver), and to demodulate signals. In some implementations, the transceiver 1110 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1115 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1115 that are configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1110 may include or be configured for coupling with one or more processors or one or more memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof. In some implementations, the transceiver 1110, or the transceiver 1110 and the one or more antennas 1115, or the transceiver 1110 and the one or more antennas 1115 and one or more processors or one or more memory components (e.g., the at least one processor 1135, the at least one memory 1125, or both), may be included in a chip or chip assembly that is installed in the device 1105. In some examples, the transceiver 1110 may be operable to support communications via one or more communications links (e.g., communication link(s) 125, backhaul communication link(s) 120, a midhaul communication link 162, a fronthaul communication link 168).

[0175] The at least one memory 1125 may include RAM, ROM, or any combination thereof. The at least one memory 1125 may store computer-readable, computer-executable, or processor-executable code, such as the code 1130. The code 1130 may include instructions that, when executed by one or more of the at least one processor 1135, cause the device 1105 to perform various functions described herein. The code 1130 may be stored in a non -transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1130 may not be directly executable by a processor of the at least one processor 1135 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 1125 may include, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices. In some examples, the at least one processor 1135 may include multiple processors and the at least one memory 1125 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories which may, individually or collectively, be configured to perform various functions herein (for example, as part of a processing system).

[0176] The at least one processor 1135 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs), one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, the at least one processor 1135 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into one or more of the at least one processor 1135. The at least one processor 1135 may be configured to execute computer-readable instructions stored in a memory (e.g., one or more of the at least one memory 1125) to cause the device 1105 to perform various functions (e.g., functions or tasks supporting repeated transmissions for NTNs). For example, the device 1105 or a component of the device 1105 may include at least one processor 1135 and at least one memory 1125 coupled with one or more of the at least one processor 1135, the at least one processor 1135 and the at least one memory 1125 configured to perform various functions described herein. The at least one processor 1135 may be an example of a cloud-computing platform (e.g., one or morephysical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1130) to perform the functions of the device 1105. The at least one processor 1135 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1105 (such as within one or more of the at least one memory 1125). In some examples, the at least one processor 1135 may include multiple processors and the at least one memory 1125 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein. In some examples, the at least one processor 1135 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1135) and memory circuitry (which may include the at least one memory 1125)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1135 or a processing system including the at least one processor 1135 may be configured to, configurable to, or operable to cause the device 1105 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory 1125 or otherwise, to perform one or more of the functions described herein.

[0177] In some examples, a bus 1140 may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus 1140 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of the device 1105, or between different components of the device 1105 that may be co-located or located in different locations (e.g., where the device 1105 may refer to a system in which one or more of the communications manager 1120, the transceiver 1110, the at least one memory 1125, the code 1130, and the at least oneprocessor 1135 may be located in one of the different components or divided between different components).

[0178] In some examples, the communications manager 1120 may manage aspects of communications with a core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communications manager 1120 may manage the transfer of data communications for client devices, such as one or more UEs 115. In some examples, the communications manager 1120 may manage communications with one or more other network devices (e.g., network entities 105), and may include a controller or scheduler for controlling communications with UEs 115 (e.g., in cooperation with the one or more other network entities). In some examples, the communications manager 1120 may support an X2 interface within an LTE / LTE-A wireless communications network technology to provide communication between network entities 105.

[0179] The communications manager 1120 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1120 is capable of, configured to, or operable to support a means for obtaining, by the first network entity, a transmission request message from a core network node indicating a message for transmission within a first coverage area. The communications manager 1120 is capable of, configured to, or operable to support a means for forwarding, by the first network entity, the transmission request message to a second network entity based on the second network entity being scheduled to serve the first coverage area.

[0180] By including or configuring the communications manager 1120 in accordance with examples as described herein, the device 1105 may support techniques for increasing the likelihood of successful messages by network entities (e.g., NTN network entities), resulting in reduced system latency, improved likelihood of successful delivery of transmitting, improved coordination between devices, improved health and safety for users, more efficient utilization of communication resources, and improved user experiences.

[0181] In some examples, the communications manager 1120 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting,transmitting) using or otherwise in cooperation with the transceiver 1110, the one or more antennas 1115 (e.g., where applicable), or any combination thereof. For example, the communications manager 1120 may be configured to receive or transmit messages or other signaling as described herein via a transceiver 1110. Although the communications manager 1120 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1120 may be supported by or performed by the transceiver 1110, one or more of the at least one processor 1135, one or more of the at least one memory 1125, the code 1130, or any combination thereof (for example, by a processing system including at least a portion of the at least one processor 1135, the at least one memory 1125, the code 1130, or any combination thereof). For example, the code 1130 may include instructions executable by one or more of the at least one processor 1135 to cause the device 1105 to perform various aspects of repeated transmissions for NTNs as described herein, or the at least one processor 1135 and the at least one memory 1125 may be otherwise configured to, individually or collectively, perform or support such operations.

[0182] FIG. 12 shows a block diagram 1200 of a device 1205 that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure. The device 1205 may be an example of aspects of a network entity as described herein. The device 1205 may include a receiver 1210, a transmitter 1215, and a communications manager 1220. The device 1205, or one or more components of the device 1205 (e.g., the receiver 1210, the transmitter 1215, the communications manager 1220), may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0183] The receiver 1210 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). Information may be passed on to other components of the device 1205. In some examples, the receiver 1210may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1210 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0184] The transmitter 1215 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1205. For example, the transmitter 1215 may output information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). In some examples, the transmitter 1215 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1215 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1215 and the receiver 1210 may be co-located in a transceiver, which may include or be coupled with a modem.

[0185] The communications manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be examples of means for performing various aspects of repeated transmissions for NTNs as described herein. For example, the communications manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

[0186] In some examples, the communications manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include at least one of a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of thefunctions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory).

[0187] Additionally, or alternatively, the communications manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code). If implemented in code executed by at least one processor, the functions of the communications manager 1220, the receiver 1210, the transmitter 1215, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure).

[0188] In some examples, the communications manager 1220 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1210, the transmitter 1215, or both. For example, the communications manager 1220 may receive information from the receiver 1210, send information to the transmitter 1215, or be integrated in combination with the receiver 1210, the transmitter 1215, or both to obtain information, output information, or perform various other operations as described herein.

[0189] The communications manager 1220 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1220 is capable of, configured to, or operable to support a means for changing a coverage area served by the second network entity to a first coverage area from a second coverage area. The communications manager 1220 is capable of, configured to, or operable to support a means for obtaining, from a first network entity and based on the second network entity being scheduled to serve the first coverage area, a forwarded transmission request message indicating a message for transmission within the first coverage area. The communications manager 1220 is capable of, configured to, or operable to support a means for outputting, within the first coverage area, one or more repetitions of the message according to the forwarded transmission request message.

[0190] By including or configuring the communications manager 1220 in accordance with examples as described herein, the device 1205 (e.g., at least one processor controlling or otherwise coupled with the receiver 1210, the transmitter 1215, the communications manager 1220, or a combination thereof) may support techniques for increasing the likelihood of successful messages by network entities (e.g., NTN network entities), resulting in reduced latency, improved likelihood of successful delivery of transmitting, improved health and safety for users, more efficient utilization of communication resources, and improved user experiences.

[0191] FIG. 13 shows a block diagram 1300 of a device 1305 that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure. The device 1305 may be an example of aspects of a device 1205 or a network entity 105 as described herein. The device 1305 may include a receiver 1310, a transmitter 1315, and a communications manager 1320. The device 1305, or one of more components of the device 1305 (e.g., the receiver 1310, the transmitter 1315, the communications manager 1320), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0192] The receiver 1310 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). Information may be passed on to other components of the device 1305. In some examples, the receiver 1310 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1310 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0193] The transmitter 1315 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1305. For example, the transmitter 1315 may output information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g.,control channels, data channels, information channels, channels associated with a protocol stack). In some examples, the transmitter 1315 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1315 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1315 and the receiver 1310 may be co-located in a transceiver, which may include or be coupled with a modem.

[0194] The device 1305, or various components thereof, may be an example of means for performing various aspects of repeated transmissions for NTNs as described herein. For example, the communications manager 1320 may include a coverage area manager 1325, a transmission request message manager 1330, a transmission manager 1335, or any combination thereof. The communications manager 1320 may be an example of aspects of a communications manager 1220 as described herein. In some examples, the communications manager 1320, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1310, the transmitter 1315, or both. For example, the communications manager 1320 may receive information from the receiver 1310, send information to the transmitter 1315, or be integrated in combination with the receiver 1310, the transmitter 1315, or both to obtain information, output information, or perform various other operations as described herein.

[0195] The communications manager 1320 may support wireless communications in accordance with examples as disclosed herein. The coverage area manager 1325 is capable of, configured to, or operable to support a means for changing a coverage area served by the second network entity to a first coverage area from a second coverage area. The transmission request message manager 1330 is capable of, configured to, or operable to support a means for obtaining, from a first network entity and based on the second network entity being scheduled to serve the first coverage area, a forwarded transmission request message indicating a message for transmission within the first coverage area. The transmission manager 1335 is capable of, configured to, or operableto support a means for outputting, within the first coverage area, one or more repetitions of the message according to the forwarded transmission request message.

[0196] FIG. 14 shows a block diagram 1400 of a communications manager 1420 that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure. The communications manager 1420 may be an example of aspects of a communications manager 1220, a communications manager 1320, or both, as described herein. The communications manager 1420, or various components thereof, may be an example of means for performing various aspects of repeated transmissions for NTNs as described herein. For example, the communications manager 1420 may include a coverage area manager 1425, a transmission request message manager 1430, a transmission manager 1435, a response message manager 1440, a repetition manager 1445, an endpoint information manager 1450, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses).

[0197] The communications manager 1420 may support wireless communications in accordance with examples as disclosed herein. The coverage area manager 1425 is capable of, configured to, or operable to support a means for changing a coverage area served by the second network entity to a first coverage area from a second coverage area. The transmission request message manager 1430 is capable of, configured to, or operable to support a means for obtaining, from a first network entity and based on the second network entity being scheduled to serve the first coverage area, a forwarded transmission request message indicating a message for transmission within the first coverage area. The transmission manager 1435 is capable of, configured to, or operable to support a means for outputting, within the first coverage area, one or more repetitions of the message according to the forwarded transmission request message.

[0198] In some examples, the response message manager 1440 is capable of, configured to, or operable to support a means for outputting, to the first network entity, a response message indicating that the second network entity has received the forwarded transmission request message.

[0199] In some examples, the repetition manager 1445 is capable of, configured to, or operable to support a means for obtaining, in the forwarded transmission request message, an indication of a first quantity of repetitions of a set of multiple repetitions of the message output by the first network entity, an indication of a second quantity of remaining repetitions of the set of multiple repetitions of the message, an indication of a total quantity of the set of multiple repetitions indicated by the forwarded transmission request message, or any combination thereof. In some examples, the transmission manager 1435 is capable of, configured to, or operable to support a means for outputting the one or more repetitions of the message including outputting one or more additional repetitions of the message based on the first quantity of repetitions, the second quantity of remaining repetitions, the total quantity of the set of multiple repetitions, or any combination thereof.

[0200] In some examples, the response message manager 1440 is capable of, configured to, or operable to support a means for outputting, to a core network node, a status message indicating identifier information corresponding to the second network entity and a completion status of the message, the completion status including an indication of a portion of the total quantity of the set of multiple repetitions including the first quantity of repetitions and the one or more additional repetitions.

[0201] In some examples, the response message manager 1440 is capable of, configured to, or operable to support a means for outputting, to a core network node, a status message indicating identifier information corresponding to the second network entity and a completion status of the message, the completion status including an indication of a failure to transmit one or more repetitions of the message.

[0202] In some examples, the transmission request message manager 1430 is capable of, configured to, or operable to support a means for outputting a message to a third network entity, the message including the transmission request message, identifier information corresponding to the second network entity, and an indication of a completion status of the message, the completion status including an indication of a portion of the total quantity of the set of multiple repetitions including the first quantity of repetitions and the one or more additional repetitions.

[0203] In some examples, the repetition manager 1445 is capable of, configured to, or operable to support a means for obtaining, in the forwarded transmission request message, an indication of a first quantity of repetitions of a set of multiple repetitions of the message output by the first network entity, an indication of a second quantity of remaining repetitions of the set of multiple repetitions of the message, an indication of a total quantity of the set of multiple repetitions indicated by the forwarded transmission request message, or any combination thereof, where outputting the one or more repetitions of the message includes outputting the second quantity of remaining repetitions of the set of multiple repetitions of the message. In some examples, the response message manager 1440 is capable of, configured to, or operable to support a means for outputting, to a core network node, a status message indicating identifier information corresponding to a set of multiple network entities including the first network entity and the second network entity and further indicating a completion status of the message, the completion status including an indication of successful transmission of the total quantity of the set of multiple repetitions of the message.

[0204] In some examples, the endpoint information manager 1450 is capable of, configured to, or operable to support a means for obtaining, from a core network node, control signaling indicating endpoint information corresponding to a geostationary buffering node, where the second network entity includes a geostationary buffering node, the forwarded transmission request message is received from the core network node via the buffering node, and where obtaining the forwarded transmission request message is based on the endpoint information.

[0205] FIG. 15 shows a diagram of a system 1500 including a device 1505 that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure. The device 1505 may be an example of or include components of a device 1205, a device 1305, or a network entity as described herein. The device 1505 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 1520, a transceiver 1510, one or more antennas 1515, at least one memory 1525, code 1530, and at least one processor 1535. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1540).

[0206] The transceiver 1510 may support bi-directional communications via wired links, wireless links, or both as described herein. In some examples, the transceiver 1510 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1510 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1505 may include one or more antennas 1515, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver 1510 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1515, by a wired transmitter), to receive modulated signals (e.g., from one or more antennas 1515, from a wired receiver), and to demodulate signals. In some implementations, the transceiver 1510 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1515 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1515 that are configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1510 may include or be configured for coupling with one or more processors or one or more memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof. In some implementations, the transceiver 1510, or the transceiver 1510 and the one or more antennas 1515, or the transceiver 1510 and the one or more antennas 1515 and one or more processors or one or more memory components (e.g., the at least one processor 1535, the at least one memory 1525, or both), may be included in a chip or chip assembly that is installed in the device 1505. In some examples, the transceiver 1510 may be operable to support communications via one or more communications links (e.g., communication link(s) 125, backhaul communication link(s) 120, a midhaul communication link 162, a fronthaul communication link 168).

[0207] The at least one memory 1525 may include RAM, ROM, or any combination thereof. The at least one memory 1525 may store computer-readable, computerexecutable, or processor-executable code, such as the code 1530. The code 1530 may include instructions that, when executed by one or more of the at least one processor1535, cause the device 1505 to perform various functions described herein. The code 1530 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1530 may not be directly executable by a processor of the at least one processor 1535 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 1525 may include, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices. In some examples, the at least one processor 1535 may include multiple processors and the at least one memory 1525 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories which may, individually or collectively, be configured to perform various functions herein (for example, as part of a processing system).

[0208] The at least one processor 1535 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs), one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, the at least one processor 1535 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into one or more of the at least one processor 1535. The at least one processor 1535 may be configured to execute computer-readable instructions stored in a memory (e.g., one or more of the at least one memory 1525) to cause the device 1505 to perform various functions (e.g., functions or tasks supporting repeated transmissions for NTNs). For example, the device 1505 or a component of the device 1505 may include at least one processor 1535 and at least one memory 1525 coupled with one or more of the at least one processor 1535, the at least one processor 1535 and the at least one memory 1525 configured to perform various functions described herein. The at least one processor 1535 may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1530) toperform the functions of the device 1505. The at least one processor 1535 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1505 (such as within one or more of the at least one memory 1525). In some examples, the at least one processor 1535 may include multiple processors and the at least one memory 1525 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein. In some examples, the at least one processor 1535 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1535) and memory circuitry (which may include the at least one memory 1525)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1535 or a processing system including the at least one processor 1535 may be configured to, configurable to, or operable to cause the device 1505 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory 1525 or otherwise, to perform one or more of the functions described herein.

[0209] In some examples, a bus 1540 may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus 1540 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of the device 1505, or between different components of the device 1505 that may be co-located or located in different locations (e.g., where the device 1505 may refer to a system in which one or more of the communications manager 1520, the transceiver 1510, the at least one memory 1525, the code 1530, and the at least one processor 1535 may be located in one of the different components or divided between different components).

[0210] In some examples, the communications manager 1520 may manage aspects of communications with a core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communications manager 1520 may manage the transfer of data communications for client devices, such as one or more UEs 115. In some examples, the communications manager 1520 may manage communications with one or more other network entities 105 and may include a controller or scheduler for controlling communications with UEs 115 (e.g., in cooperation with the one or more other network devices). In some examples, the communications manager 1520 may support an X2 interface within an LTE / LTE-A wireless communications network technology to provide communication between network entities 105.

[0211] The communications manager 1520 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1520 is capable of, configured to, or operable to support a means for changing a coverage area served by the second network entity to a first coverage area from a second coverage area. The communications manager 1520 is capable of, configured to, or operable to support a means for obtaining, from a first network entity and based on the second network entity being scheduled to serve the first coverage area, a forwarded transmission request message indicating a message for transmission within the first coverage area. The communications manager 1520 is capable of, configured to, or operable to support a means for outputting, within the first coverage area, one or more repetitions of the message according to the forwarded transmission request message.

[0212] By including or configuring the communications manager 1520 in accordance with examples as described herein, the device 1505 may support techniques for increasing the likelihood of successful messages by network entities (e.g., NTN network entities), resulting in reduced system latency, improved likelihood of successful delivery of transmitting, improved coordination between devices, improved health and safety for users, more efficient utilization of communication resources, and improved user experiences.

[0213] In some examples, the communications manager 1520 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1510, the one or more antennas 1515 (e.g., where applicable), or any combination thereof. For example,the communications manager 1520 may be configured to receive or transmit messages or other signaling as described herein via a transceiver 1510. Although the communications manager 1520 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1520 may be supported by or performed by the transceiver 1510, one or more of the at least one processor 1535, one or more of the at least one memory 1525, the code 1530, or any combination thereof (for example, by a processing system including at least a portion of the at least one processor 1535, the at least one memory 1525, the code 1530, or any combination thereof). For example, the code 1530 may include instructions executable by one or more of the at least one processor 1535 to cause the device 1505 to perform various aspects of repeated transmissions for NTNs as described herein, or the at least one processor 1535 and the at least one memory 1525 may be otherwise configured to, individually or collectively, perform or support such operations.

[0214] FIG. 16 shows a block diagram 1600 of a device 1605 that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure. The device 1605 may be an example of aspects of a network entity as described herein. The device 1605 may include a receiver 1610, a transmitter 1615, and a communications manager 1620. The device 1605, or one or more components of the device 1605 (e.g., the receiver 1610, the transmitter 1615, the communications manager 1620), may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0215] The receiver 1610 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). Information may be passed on to other components of the device 1605. In some examples, the receiver 1610 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1610 may support obtaining information byreceiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0216] The transmitter 1615 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1605. For example, the transmitter 1615 may output information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). In some examples, the transmitter 1615 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1615 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1615 and the receiver 1610 may be co-located in a transceiver, which may include or be coupled with a modem.

[0217] The communications manager 1620, the receiver 1610, the transmitter 1615, or various combinations or components thereof may be examples of means for performing various aspects of repeated transmissions for NTNs as described herein. For example, the communications manager 1620, the receiver 1610, the transmitter 1615, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

[0218] In some examples, the communications manager 1620, the receiver 1610, the transmitter 1615, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include at least one of a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory).

[0219] Additionally, or alternatively, the communications manager 1620, the receiver 1610, the transmitter 1615, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code). If implemented in code executed by at least one processor, the functions of the communications manager 1620, the receiver 1610, the transmitter 1615, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure).

[0220] In some examples, the communications manager 1620 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1610, the transmitter 1615, or both. For example, the communications manager 1620 may receive information from the receiver 1610, send information to the transmitter 1615, or be integrated in combination with the receiver 1610, the transmitter 1615, or both to obtain information, output information, or perform various other operations as described herein.

[0221] The communications manager 1620 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1620 is capable of, configured to, or operable to support a means for obtaining a transmission request message from a core network node indicating a message for transmission within a first coverage area. The communications manager 1620 is capable of, configured to, or operable to support a means for buffing the transmission request message while a first network entity is scheduled to serve the first coverage area. The communications manager 1620 is capable of, configured to, or operable to support a means for forwarding the transmission request message to a second network entity based on the second network entity being scheduled to serve the first coverage area.

[0222] By including or configuring the communications manager 1620 in accordance with examples as described herein, the device 1605 (e.g., at least one processor controlling or otherwise coupled with the receiver 1610, the transmitter 1615,the communications manager 1620, or a combination thereof) may support techniques for increasing the likelihood of successful messages by network entities (e.g., NTN network entities), resulting in reduced latency, improved likelihood of successful delivery of transmitting, improved health and safety for users, more efficient utilization of communication resources, and improved user experiences.

[0223] FIG. 17 shows a block diagram 1700 of a device 1705 that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure. The device 1705 may be an example of aspects of a device 1605 or a network entity 105 as described herein. The device 1705 may include a receiver 1710, a transmitter 1715, and a communications manager 1720. The device 1705, or one of more components of the device 1705 (e.g., the receiver 1710, the transmitter 1715, the communications manager 1720), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0224] The receiver 1710 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). Information may be passed on to other components of the device 1705. In some examples, the receiver 1710 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1710 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0225] The transmitter 1715 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1705. For example, the transmitter 1715 may output information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). In some examples, the transmitter 1715 may support outputting information by transmitting signals via one or more antennas. Additionally, oralternatively, the transmitter 1715 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1715 and the receiver 1710 may be co-located in a transceiver, which may include or be coupled with a modem.

[0226] The device 1705, or various components thereof, may be an example of means for performing various aspects of repeated transmissions for NTNs as described herein. For example, the communications manager 1720 may include a transmission request message manager 1725, a buffering manager 1730, a forwarding manager 1735, or any combination thereof. The communications manager 1720 may be an example of aspects of a communications manager 1620 as described herein. In some examples, the communications manager 1720, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1710, the transmitter 1715, or both. For example, the communications manager 1720 may receive information from the receiver 1710, send information to the transmitter 1715, or be integrated in combination with the receiver 1710, the transmitter 1715, or both to obtain information, output information, or perform various other operations as described herein.

[0227] The communications manager 1720 may support wireless communications in accordance with examples as disclosed herein. The transmission request message manager 1725 is capable of, configured to, or operable to support a means for obtaining a transmission request message from a core network node indicating a message for transmission within a first coverage area. The buffering manager 1730 is capable of, configured to, or operable to support a means for buffering the transmission request message while a first network entity is scheduled to serve the first coverage area. The forwarding manager 1735 is capable of, configured to, or operable to support a means for forwarding the transmission request message to a second network entity based on the second network entity being scheduled to serve the first coverage area.

[0228] FIG. 18 shows a block diagram 1800 of a communications manager 1820 that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure. The communications manager 1820 may be an example ofaspects of a communications manager 1620, a communications manager 1720, or both, as described herein. The communications manager 1820, or various components thereof, may be an example of means for performing various aspects of repeated transmissions for NTNs as described herein. For example, the communications manager 1820 may include a transmission request message manager 1825, a buffering manager 1830, a forwarding manager 1835, a satellite movement manager 1840, a request message manager 1845, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses).

[0229] The communications manager 1820 may support wireless communications in accordance with examples as disclosed herein. The transmission request message manager 1825 is capable of, configured to, or operable to support a means for obtaining a transmission request message from a core network node indicating a message for transmission within a first coverage area. The buffering manager 1830 is capable of, configured to, or operable to support a means for buffering the transmission request message while a first network entity is scheduled to serve the first coverage area. The forwarding manager 1835 is capable of, configured to, or operable to support a means for forwarding the transmission request message to a second network entity based on the second network entity being scheduled to serve the first coverage area.

[0230] In some examples, the satellite movement manager 1840 is capable of, configured to, or operable to support a means for obtaining satellite movement information associated with the second network entity from an 0AM node , where buffering the transmission request message and forwarding the transmission request message are based on the satellite movement information.

[0231] In some examples, the request message manager 1845 is capable of, configured to, or operable to support a means for obtaining a request message from the second network entity requesting the transmission request message, where forwarding the transmission request message is based on obtaining the request message.

[0232] FIG. 19 shows a diagram of a system 1900 including a device 1905 that supports repeated transmissions for NTNs in accordance with one or more aspects of thepresent disclosure. The device 1905 may be an example of or include components of a device 1605, a device 1705, or a network entity as described herein. The device 1905 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 1920, a transceiver 1910, one or more antennas 1915, at least one memory 1925, code 1930, and at least one processor 1935. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1940).

[0233] The transceiver 1910 may support bi-directional communications via wired links, wireless links, or both as described herein. In some examples, the transceiver 1910 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1910 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1905 may include one or more antennas 1915, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver 1910 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1915, by a wired transmitter), to receive modulated signals (e.g., from one or more antennas 1915, from a wired receiver), and to demodulate signals. In some implementations, the transceiver 1910 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1915 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1915 that are configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1910 may include or be configured for coupling with one or more processors or one or more memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof. In some implementations, the transceiver 1910, or the transceiver 1910 and the one or more antennas 1915, or the transceiver 1910 and the one or more antennas 1915 and one or more processors or one or more memory components (e.g., the at least one processor 1935, the at least one memory 1925, or both), may be included in a chip or chipassembly that is installed in the device 1905. In some examples, the transceiver 1910 may be operable to support communications via one or more communications links (e.g., communication link(s) 125, backhaul communication link(s) 120, a midhaul communication link 162, a fronthaul communication link 168).

[0234] The at least one memory 1925 may include RAM, ROM, or any combination thereof. The at least one memory 1925 may store computer-readable, computerexecutable, or processor-executable code, such as the code 1930. The code 1930 may include instructions that, when executed by one or more of the at least one processor 1935, cause the device 1905 to perform various functions described herein. The code 1930 may be stored in a non -transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1930 may not be directly executable by a processor of the at least one processor 1935 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 1925 may include, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices. In some examples, the at least one processor 1935 may include multiple processors and the at least one memory 1925 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories which may, individually or collectively, be configured to perform various functions herein (for example, as part of a processing system).

[0235] The at least one processor 1935 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more central processing units (CPUs), one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, the at least one processor 1935 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into one or more of the at least one processor 1935. The at least one processor 1935 may be configured to execute computer-readable instructions stored in a memory (e.g., one or more of the at least one memory 1925) to cause the device 1905 toperform various functions (e.g., functions or tasks supporting repeated transmissions for NTNs). For example, the device 1905 or a component of the device 1905 may include at least one processor 1935 and at least one memory 1925 coupled with one or more of the at least one processor 1935, the at least one processor 1935 and the at least one memory 1925 configured to perform various functions described herein. The at least one processor 1935 may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1930) to perform the functions of the device 1905. The at least one processor 1935 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1905 (such as within one or more of the at least one memory 1925). In some examples, the at least one processor 1935 may include multiple processors and the at least one memory 1925 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein. In some examples, the at least one processor 1935 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1935) and memory circuitry (which may include the at least one memory 1925)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1935 or a processing system including the at least one processor 1935 may be configured to, configurable to, or operable to cause the device 1905 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory 1925 or otherwise, to perform one or more of the functions described herein.

[0236] In some examples, a bus 1940 may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus 1940 may support communications associated with a logical channel of a protocol stack (e.g., betweenprotocol layers of a protocol stack), which may include communications performed within a component of the device 1905, or between different components of the device 1905 that may be co-located or located in different locations (e.g., where the device 1905 may refer to a system in which one or more of the communications manager 1920, the transceiver 1910, the at least one memory 1925, the code 1930, and the at least one processor 1935 may be located in one of the different components or divided between different components).

[0237] In some examples, the communications manager 1920 may manage aspects of communications with a core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communications manager 1920 may manage the transfer of data communications for client devices, such as one or more UEs 115. In some examples, the communications manager 1920 may manage communications with one or more other network entities 105 and may include a controller or scheduler for controlling communications with UEs 115 (e.g., in cooperation with the one or more other network devices). In some examples, the communications manager 1920 may support an X2 interface within an LTE / LTE-A wireless communications network technology to provide communication between network entities 105.

[0238] The communications manager 1920 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1920 is capable of, configured to, or operable to support a means for obtaining a transmission request message from a core network node indicating a message for transmission within a first coverage area. The communications manager 1920 is capable of, configured to, or operable to support a means for buffing the transmission request message while a first network entity is scheduled to serve the first coverage area. The communications manager 1920 is capable of, configured to, or operable to support a means for forwarding the transmission request message to a second network entity based on the second network entity being scheduled to serve the first coverage area.

[0239] By including or configuring the communications manager 1920 in accordance with examples as described herein, the device 1905 may support techniques for increasing the likelihood of successful messages by network entities (e.g., NTN network entities), resulting in reduced latency, improved likelihood of successfuldelivery of transmitting, improved health and safety for users, more efficient utilization of communication resources, and improved user experiences.

[0240] In some examples, the communications manager 1920 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1910, the one or more antennas 1915 (e.g., where applicable), or any combination thereof. For example, the communications manager 1920 may be configured to receive or transmit messages or other signaling as described herein via a transceiver 1910. Although the communications manager 1920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1920 may be supported by or performed by the transceiver 1910, one or more of the at least one processor 1935, one or more of the at least one memory 1925, the code 1930, or any combination thereof (for example, by a processing system including at least a portion of the at least one processor 1935, the at least one memory 1925, the code 1930, or any combination thereof). For example, the code 1930 may include instructions executable by one or more of the at least one processor 1935 to cause the device 1905 to perform various aspects of repeated transmissions for NTNs as described herein, or the at least one processor 1935 and the at least one memory 1925 may be otherwise configured to, individually or collectively, perform or support such operations.

[0241] FIG. 20 shows a flowchart illustrating a method 2000 that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure. The operations of the method 2000 may be implemented by a network entity or its components as described herein. For example, the operations of the method 2000 may be performed by a network entity as described with reference to FIGs. 1 through 11. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

[0242] At 2005, the method may include obtaining, by the first network entity, a transmission request message from a core network node indicating a message for transmission within a first coverage area. The operations of 2005 may be performed inaccordance with examples as disclosed herein. In some examples, a message may be broadcast if the message is intended for UEs in the first coverage area. Additionally or alternatively, a message may be multicast if the message is intended only for a subset of all UEs in the first coverage area. For example, depending on a service or a UE capability, all UEs in the first coverage area may be intended or only a subset of UEs in the first coverage area. For example, a given service may only wish to transmit the message to UEs having a certain capability, e.g., certain reliability capabilities (e.g., ACK / NACK capability), in which case the service may prefer a multicast message. In some examples, aspects of the operations of 2005 may be performed by a transmission request manager 1025 as described with reference to FIG. 10. Additionally or alternatively, means for performing 2005 may, but not necessarily, include, for example, antenna 1115, transceiver 1110, communications manager 1120, memory 1125 (including code 1130), processor 1135 and / or bus 1140.

[0243] At 2010, the method may include forwarding, by the first network entity, the transmission request message to a second network entity based on the second network entity being scheduled to serve the first coverage area. The operations of 2010 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2010 may be performed by a transmission request message forwarding manager 1030 as described with reference to FIG. 10. Additionally or alternatively, means for performing 2010 may, but not necessarily, include, for example, antenna 1115, transceiver 1110, communications manager 1120, memory 1125 (including code 1130), processor 1135 and / or bus 1140.

[0244] FIG. 21 shows a flowchart illustrating a method 2100 that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure. The operations of the method 2100 may be implemented by a network entity or its components as described herein. For example, the operations of the method 2100 may be performed by a network entity as described with reference to FIGs. 1 through 7 and 12 through 15. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

[0245] At 2105, the method may include changing a coverage area served by a second network entity to a first coverage area from a second coverage area. The operations of 2105 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2105 may be performed by a coverage area manager 1425 as described with reference to FIG. 14. Additionally or alternatively, means for performing 2105 may, but not necessarily, include, for example, antenna 1515, transceiver 1510, communications manager 1520, memory 1525 (including code 1530), processor 1535 and / or bus 1540.

[0246] At 2110, the method may include obtaining, from a first network entity and based on the second network entity being scheduled to serve the first coverage area, a forwarded transmission request message indicating a message for transmission within the first coverage area. The operations of 2110 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2110 may be performed by a transmission request message manager 1430 as described with reference to FIG. 14. Additionally or alternatively, means for performing 2110 may, but not necessarily, include, for example, antenna 1515, transceiver 1510, communications manager 1520, memory 1525 (including code 1530), processor 1535 and / or bus 1540.

[0247] At 2115, the method may include outputting, within the first coverage area, one or more repetitions of the message according to the forwarded transmission request message. The operations of 2115 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2115 may be performed by a transmission manager 1435 as described with reference to FIG. 14. Additionally or alternatively, means for performing 2115 may, but not necessarily, include, for example, antenna 1515, transceiver 1510, communications manager 1520, memory 1525 (including code 1530), processor 1535 and / or bus 1540.

[0248] FIG. 22 shows a flowchart illustrating a method 2200 that supports repeated transmissions for NTNs in accordance with one or more aspects of the present disclosure. The operations of the method 2200 may be implemented by a network entity or its components as described herein. For example, the operations of the method 2200 may be performed by a network entity as described with reference to FIGs. 1 through 7 and 16 through 19. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the describedfunctions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

[0249] At 2205, the method may include obtaining a transmission request message from a core network node indicating a message for transmission within a first coverage area. The operations of 2205 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2205 may be performed by a transmission request message manager 1825 as described with reference to FIG. 18. Additionally or alternatively, means for performing 2205 may, but not necessarily, include, for example, antenna 1915, transceiver 1910, communications manager 1920, memory 1925 (including code 1930), processor 1935 and / or bus 1940.

[0250] At 2210, the method may include buffering the transmission request message while a first network entity is scheduled to serve the first coverage area. The operations of 2210 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2210 may be performed by a buffering manager 1830 as described with reference to FIG. 18. Additionally or alternatively, means for performing 2210 may, but not necessarily, include, for example, antenna 1915, transceiver 1910, communications manager 1920, memory 1925 (including code 1930), processor 1935 and / or bus 1940.

[0251] At 2215, the method may include forwarding the transmission request message to a second network entity based on the second network entity being scheduled to serve the first coverage area. The operations of 2215 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 2215 may be performed by a forwarding manager 1835 as described with reference to FIG. 18. Additionally or alternatively, means for performing 2215 may, but not necessarily, include, for example, antenna 1915, transceiver 1910, communications manager 1920, memory 1925 (including code 1930), processor 1935 and / or bus 1940.

[0252] The following provides an overview of aspects of the present disclosure:

[0253] Aspect 1 : A method for wireless communications at a first network entity, comprising: obtaining, by the first network entity, a transmission request message from a core network node indicating a message for transmission within a first coverage area; and forwarding, by the first network entity, the transmission request message to asecond network entity based at least in part on the second network entity being scheduled to serve the first coverage area.

[0254] Aspect 2: The method of aspect 1, further comprising: obtaining, from the second network entity, a response message indicating that the second network entity has received the forwarded transmission request message.

[0255] Aspect 3: The method of any of aspects 1 through 2, further comprising: changing a coverage area served by the first network entity from the first coverage area to a second coverage area, wherein forwarding the transmission request message to the second network entity is based at least in part on changing the coverage area served by the first network entity.

[0256] Aspect 4: The method of any of aspects 1 through 3, further comprising: outputting, within the first coverage area, a threshold quantity of repetitions of the message according to the transmission request message, wherein forwarding the transmission request message to the second network entity is based at least in part on transmitting the threshold quantity of repetitions of the message.

[0257] Aspect 5: The method of any of aspects 1 through 4, further comprising: initiating a timer upon obtaining the transmission request message, wherein forwarding the transmission request message to the second network entity is based at least in part on expiration of the timer.

[0258] Aspect 6: The method of any of aspects 1 through 5, further comprising: obtaining a request for the transmission request message from the second network entity, wherein forwarding the transmission request message to the second network entity is based at least in part obtaining the request for the transmission request message.

[0259] Aspect 7: The method of any of aspects 1 through 6, further comprising: outputting, within the first coverage area, a first quantity of repetitions of a plurality of repetitions of the message indicated by the transmission request message; and outputting, in the forwarded transmission request message, an indication of the first quantity of repetitions of the plurality of repetitions of the message, an indication of a second quantity of remaining repetitions of the plurality of repetitions of the message,an indication of a total quantity of the plurality of repetitions indicated by the transmission request message, or any combination thereof.

[0260] Aspect 8: The method of any of aspects 1 through 7, further comprising: outputting, to the core network node, a status message indicating a completion status of the message.

[0261] Aspect 9: The method of any of aspects 1 through 8, further comprising: outputting, in the forwarded transmission request message, identifier information corresponding to the first network entity and a completion status of the message.

[0262] Aspect 10: A method for wireless communications at a second network entity, comprising: changing a coverage area served by the second network entity to a first coverage area from a second coverage area; obtaining, from a first network entity and based at least in part on the second network entity being scheduled to serve the first coverage area, a forwarded transmission request message indicating a message for transmission within the first coverage area; and outputting, within the first coverage area, one or more repetitions of the message according to the forwarded transmission request message.

[0263] Aspect 11 : The method of aspect 10, further comprising: outputting, to the first network entity, a response message indicating that the second network entity has received the forwarded transmission request message.

[0264] Aspect 12: The method of any of aspects 10 through 11, further comprising: obtaining, in the forwarded transmission request message, an indication of a first quantity of repetitions of a plurality of repetitions of the message output by the first network entity, an indication of a second quantity of remaining repetitions of the plurality of repetitions of the message, an indication of a total quantity of the plurality of repetitions indicated by the forwarded transmission request message, or any combination thereof, wherein outputting the one or more repetitions of the message comprises outputting one or more additional repetitions of the message based at least in part on the first quantity of repetitions, the second quantity of remaining repetitions, the total quantity of the plurality of repetitions, or any combination thereof.

[0265] Aspect 13: The method of aspect 12, further comprising: outputting, to a core network node, a status message indicating identifier information corresponding to the second network entity and a completion status of the message, the completion status comprising an indication of a portion of the total quantity of the plurality of repetitions comprising the first quantity of repetitions and the one or more additional repetitions.

[0266] Aspect 14: The method of any of aspects 12 through 13, further comprising: outputting, to a core network node, a status message indicating identifier information corresponding to the second network entity and a completion status of the message, the completion status comprising an indication of a failure to transmit one or more repetitions of the message.

[0267] Aspect 15: The method of any of aspects 12 through 14, further comprising: outputting a message to a third network entity, the message comprising the transmission request message, identifier information corresponding to the second network entity, and an indication of a completion status of the message, the completion status comprising an indication of a portion of the total quantity of the plurality of repetitions comprising the first quantity of repetitions and the one or more additional repetitions.

[0268] Aspect 16: The method of any of aspects 10 through 15, further comprising: obtaining, in the forwarded transmission request message, an indication of a first quantity of repetitions of a plurality of repetitions of the message output by the first network entity, an indication of a second quantity of remaining repetitions of the plurality of repetitions of the message, an indication of a total quantity of the plurality of repetitions indicated by the forwarded transmission request message, or any combination thereof, wherein outputting the one or more repetitions of the message comprises outputting the second quantity of remaining repetitions of the plurality of repetitions of the message; and outputting, to a core network node, a status message indicating identifier information corresponding to a plurality of network entities comprising the first network entity and the second network entity and further indicating a completion status of the message, the completion status comprising an indication of successful transmission of the total quantity of the plurality of repetitions of the message.

[0269] Aspect 17: The method of any of aspects 10 through 16, further comprising: obtaining, from a core network node, control signaling indicating endpoint information corresponding to a geostationary buffering node, wherein the second network entity comprises a geostationary buffering node, the forwarded transmission request message is received from the core network node via the buffering node, and wherein obtaining the forwarded transmission request message is based at least in part on the endpoint information.

[0270] Aspect 18: A method for wireless communications at a third network entity, comprising: obtaining a transmission request message from a core network node indicating a message for transmission within a first coverage area; buffering the transmission request message while a first network entity is scheduled to serve the first coverage area; and forwarding the transmission request message to a second network entity based at least in part on the second network entity being scheduled to serve the first coverage area.

[0271] Aspect 19: The method of aspect 18, further comprising: obtaining satellite movement information associated with the second network entity from an Operations, Administration and Maintenance node , wherein buffering the transmission request message and forwarding the transmission request message are based at least in part on the satellite movement information.

[0272] Aspect 20: The method of any of aspects 18 through 19, further comprising: obtaining a request message from the second network entity requesting the transmission request message, wherein forwarding the transmission request message is based at least in part on obtaining the request message.

[0273] Aspect 21 : A first network entity for wireless communications, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the first network entity to perform a method of any of aspects 1 through 9.

[0274] Aspect 22: A first network entity for wireless communications, comprising at least one means for performing a method of any of aspects 1 through 9.

[0275] Aspect 23 : A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 9.

[0276] Aspect 24: A second network entity for wireless communications, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the second network entity to perform a method of any of aspects 10 through 17.

[0277] Aspect 25: A second network entity for wireless communications, comprising at least one means for performing a method of any of aspects 10 through 17.

[0278] Aspect 26: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 10 through 17.

[0279] Aspect 27: A third network entity for wireless communications, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the third network entity to perform a method of any of aspects 18 through 20.

[0280] Aspect 28: A third network entity for wireless communications, comprising at least one means for performing a method of any of aspects 18 through 20.

[0281] Aspect 29: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 18 through 20.

[0282] It should be noted that the methods described herein describe possible implementations. The operations and the steps may be rearranged or otherwise modified and other implementations are possible. Further, aspects from two or more of the methods may be combined.

[0283] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicablebeyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.

[0284] Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0285] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, a graphics processing unit (GPU), a neural processing unit (NPU), an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor but, in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration). Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.

[0286] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, orcombinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

[0287] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers. Combinations of the above are also included within the scope of computer-readable media. Any functions or operations described herein as being capable of being performed by a memory may be performed by multiple memories that, individually or collectively, are capable of performing the described functions or operations.

[0288] As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based onboth a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.”

[0289] As used herein, including in the claims, the article “a” before a noun is open- ended and understood to refer to “at least one” of those nouns or “one or more” of those nouns. Thus, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. For example, if a claim recites “a component” that performs one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “a component” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent reference to a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components,” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.” Similarly, subsequent reference to a component introduced as “one or more components” using the terms “the” or “said” may refer to any or all of the one or more components. For example, referring to “the one or more components” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.”

[0290] The term “determine” or “determining” encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database, or another data structure), ascertaining, and the like. Also, “determining” can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0291] In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, thedescription is applicable to any one of the similar components having the same first reference label irrespective of the second reference label or other subsequent reference label.

[0292] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some figures, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

[0293] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

CLAIMSWhat is claimed is:

1. A first network entity, comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the first network entity to: obtain, by the first network entity, a transmission request message from a core network node indicating a message for transmission within a first coverage area; and forward, by the first network entity, the transmission request message to a second network entity based at least in part on the second network entity being scheduled to serve the first coverage area.

2. The first network entity of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the first network entity to: obtain, from the second network entity, a response message indicating that the second network entity has received the forwarded transmission request message.

3. The first network entity of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the first network entity to: change a coverage area served by the first network entity from the first coverage area to a second coverage area, wherein the one or more processors are individually or collectively operable to execute the code to cause the first network entity to forward the transmission request message to the second network entity based at least in part on changing the coverage area served by the first network entity.

4. The first network entity of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the first network entity to: output, within the first coverage area, a threshold quantity of repetitions of the message according to the transmission request message, wherein the one or moreprocessors are individually or collectively operable to execute the code to cause the first network entity to forward the transmission request message to the second network entity based at least in part on transmitting the threshold quantity of repetitions of the message.

5. The first network entity of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the first network entity to: initiate a timer upon obtaining the transmission request message, wherein the one or more processors are individually or collectively operable to execute the code to cause the first network entity to forward the transmission request message to the second network entity based at least in part on expiration of the timer.

6. The first network entity of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the first network entity to: obtain a request for the transmission request message from the second network entity, wherein the one or more processors are individually or collectively operable to execute the code to cause the first network entity to forward the transmission request message to the second network entity based at least in part obtaining the request for the transmission request message.

7. The first network entity of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the first network entity to: output, within the first coverage area, a first quantity of repetitions of a plurality of repetitions of the message indicated by the transmission request message; and output, in the forwarded transmission request message, an indication of the first quantity of repetitions of the plurality of repetitions of the message, an indication of a second quantity of remaining repetitions of the plurality of repetitions of the message, an indication of a total quantity of the plurality of repetitions indicated by the transmission request message, or any combination thereof.

8. The first network entity of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the first network entity to: output, to the core network node, a status message indicating a completion status of the message.

9. The first network entity of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the first network entity to: output, in the forwarded transmission request message, identifier information corresponding to the first network entity and a completion status of the message.

10. A second network entity, comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the second network entity to: change a coverage area served by the second network entity to a first coverage area from a second coverage area; obtain, from a first network entity and based at least in part on the second network entity being scheduled to serve the first coverage area, a forwarded transmission request message indicating a message for transmission within the first coverage area; and output, within the first coverage area, one or more repetitions of the message according to the forwarded transmission request message.

11. The second network entity of claim 10, wherein the one or more processors are individually or collectively further operable to execute the code to cause the second network entity to: output, to the first network entity, a response message indicating that the second network entity has received the forwarded transmission request message.

12. The second network entity of claim 10, wherein the one or more processors are individually or collectively further operable to execute the code to cause the second network entity to: obtain, in the forwarded transmission request message, an indication of a first quantity of repetitions of a plurality of repetitions of the message output by the first network entity, an indication of a second quantity of remaining repetitions of the plurality of repetitions of the message, an indication of a total quantity of the plurality of repetitions indicated by the forwarded transmission request message, or any combination thereof, wherein, to output the one or more repetitions of the message, the one or more processors are individually or collectively operable to execute the code to cause the second network entity to output one or more additional repetitions of the message based at least in part on the first quantity of repetitions, the second quantity of remaining repetitions, the total quantity of the plurality of repetitions, or any combination thereof.

13. The second network entity of claim 12, wherein the one or more processors are individually or collectively further operable to execute the code to cause the second network entity to: output, to a core network node, a status message indicating identifier information corresponding to the second network entity and a completion status of the message, the completion status comprising an indication of a portion of the total quantity of the plurality of repetitions comprising the first quantity of repetitions and the one or more additional repetitions.

14. The second network entity of claim 12, wherein the one or more processors are individually or collectively further operable to execute the code to cause the second network entity to: output, to a core network node, a status message indicating identifier information corresponding to the second network entity and a completion status of the message, the completion status comprising an indication of a failure to transmit one or more repetitions of the message.

15. The second network entity of claim 12, wherein the one or more processors are individually or collectively further operable to execute the code to cause the second network entity to: output a message to a third network entity, the message comprising the transmission request message, identifier information corresponding to the second network entity, and an indication of a completion status of the message, the completion status comprising an indication of a portion of the total quantity of the plurality of repetitions comprising the first quantity of repetitions and the one or more additional repetitions.

16. The second network entity of claim 10, wherein the one or more processors are individually or collectively further operable to execute the code to cause the second network entity to: obtain, in the forwarded transmission request message, an indication of a first quantity of repetitions of a plurality of repetitions of the message output by the first network entity, an indication of a second quantity of remaining repetitions of the plurality of repetitions of the message, an indication of a total quantity of the plurality of repetitions indicated by the forwarded transmission request message, or any combination thereof, wherein, to output the one or more repetitions of the message, the one or more processors are individually or collectively operable to execute the code to cause the second network entity to output the second quantity of remaining repetitions of the plurality of repetitions of the message; and output, to a core network node, a status message indicating identifier information corresponding to a plurality of network entities comprising the first network entity and the second network entity and further indicating a completion status of the message, the completion status comprising an indication of successful transmission of the total quantity of the plurality of repetitions of the message.

17. The second network entity of claim 10, wherein the one or more processors are individually or collectively further operable to execute the code to cause the second network entity to: obtain, from a core network node, control signaling indicating endpoint information corresponding to a geostationary buffering node, wherein the second network entity comprises a geostationary buffering node, the forwarded transmissionrequest message is received from the core network node via the buffering node, and wherein the one or more processors are individually or collectively operable to execute the code to cause the second network entity to obtain the forwarded transmission request message based at least in part on the endpoint information.

18. A third network entity, comprising: one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the third network entity to: obtain a transmission request message from a core network node indicating a message for transmission within a first coverage area; buffer the transmission request message while a first network entity is scheduled to serve the first coverage area; and forward the transmission request message to a second network entity based at least in part on the second network entity being scheduled to serve the first coverage area.

19. The third network entity of claim 18, wherein the one or more processors are individually or collectively further operable to execute the code to cause the third network entity to: obtain satellite movement information associated with the second network entity from an Operations, Administration and Maintenance node, wherein the one or more processors are individually or collectively operable to execute the code to cause the third network entity to buffer the transmission request message and forward the transmission request message based at least in part on the satellite movement information.

20. The third network entity of claim 18, wherein the one or more processors are individually or collectively further operable to execute the code to cause the third network entity to: obtain a request message from the second network entity requesting the transmission request message, wherein the one or more processors are individually orcollectively operable to execute the code to cause the third network entity to forward the transmission request message based at least in part on obtaining the request message.

Images