Systems and methods for throughput enhancement using orthogonal cover code spreading in non-terrestrial networks

Abstract

Systems and methods for throughput enhancement using orthogonal cover code (OCC) spread spectrum in non-terrestrial networks (NTNs) are discussed. A user equipment (UE) of the NTN communicating with a base station over a serving link of the NTN receives downlink control information (DCI) from the base station indicating a dynamic uplink grant for a physical uplink shared channel (PUSCH), wherein the DCI conveys an OCC sequence index; identifying, using the OCC sequence index, a first OCC sequence for the first PUSCH from an OCC sequence set having an OCC size corresponding to the OCC sequence index; using the first OCC sequence to spread spectrum of data used for the PUSCH into the PUSCH; and transmitting the PUSCH to the base station over the serving link according to the dynamic uplink grant. Various situations in which configuration information for the configured uplink grant is used are also discussed. Corresponding base station behavior is discussed.

Description

Technical Field

[0001] The present application generally relates to wireless communication systems, including wireless communication systems that support non-terrestrial network (NTN) communication. Background Art

[0002] Wireless mobile communication technology uses various standards and protocols to send data between a base station and a wireless communication device. For example, wireless communication system standards and protocols can include, for example, the 3rd Generation Partnership Project (3GPP) Long-Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard for wireless local area networks (WLAN) (commonly referred to as Wi- ) within the industry organization.

[0003] As envisioned by 3GPP, different wireless communication system standards and protocols can use various radio access networks (RANs) for communication between a base station (sometimes also referred to as a RAN node, network node, or simply a node) of the RAN and a wireless communication device called a user equipment (UE). 3GPP RAN can include, for example, Global System for Mobile Communications (GSM), Enhanced Data Rate for GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next Generation Radio Access Network (NG-RAN).

[0004] Each RAN can use one or more radio access technologies (RATs) for communication between the base station and the UE. For example, GERAN implements GSM and / or EDGE RAT, UTRAN implements Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RAT, E-UTRAN implements LTE RAT (sometimes simply referred to as LTE), and NG-RAN implements NR RAT (this NR RAT is sometimes referred to as 5G RAT, 5G NR RAT, or simply NR in this document). In some deployments, E-UTRAN can also implement NR RAT. In some deployments, NG-RAN can also implement LTE RAT.

[0005] The base station used by the RAN can correspond to that RAN. An example of an E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (commonly also denoted as an Evolved Node B, Enhanced Node B, eNodeB, or eNB). An example of an NG-RAN base station is a Next Generation Node B (sometimes also referred to as a gNodeB or gNB).

[0006] RAN provides communication services together with external entities through its connection to the core network (CN). For example, E-UTRAN can utilize the evolved packet core (EPC), while NG-RAN can utilize the 5G core network (5GC). Description of the Drawings

[0007] To easily identify the discussion of any specific element or action, one or more of the most significant digits in the reference numerals refer to the drawing number in which the element was first introduced.

[0008] Figure 1 Illustrates the NTN architecture of a wireless communication system according to an embodiment.

[0009] Figure 2 Illustrates the NTN architecture of a wireless communication system according to an embodiment.

[0010] Figure 3 Illustrates a flowchart corresponding to the use of uplink multiplexing using OCC spreading according to various embodiments discussed herein.

[0011] Figure 4 Illustrates a diagram of PRBs on a symbol.

[0012] Figure 5 Illustrates a table showing a first configuration, a second configuration, and a third configuration corresponding to the use of resource allocation type 0.

[0013] Figure 6 Illustrates a table showing a first configuration, a second configuration, a third configuration, and a fourth configuration corresponding to the use of resource allocation type 0.

[0014] Figure 7 Illustrates a flowchart corresponding to the use of sub-PRB-based uplink multiplexing in the frequency domain according to various embodiments discussed herein.

[0015] Figure 8 Illustrates a method for a UE in an NTN to communicate with a base station through a service link of the NTN according to an embodiment of the present disclosure.

[0016] Figure 9 Illustrates a method for a UE in an NTN to communicate with a base station through a service link of the NTN according to an embodiment of the present disclosure.

[0017] Figure 10 Illustrates a method for a base station in an NTN to communicate with a first UE through a service link of the NTN according to an embodiment of the present disclosure.

[0018] Figure 11Illustrated is a method for a base station in an NTN according to an embodiment herein to communicate with a first UE via a service link of the NTN.

[0019] Figure 12 Illustrated is a method for a UE in an NTN according to an embodiment herein to communicate with a base station via a service link of the NTN.

[0020] Figure 13 Illustrated is a method for a base station in an NTN according to an embodiment herein to communicate with a UE via a service link of the NTN.

[0021] Figure 14 Illustrated is a method for a UE in an NTN according to an embodiment herein to communicate with a base station via a service link of the NTN.

[0022] Figure 15 Illustrated is a method for a base station in an NTN according to an embodiment herein to communicate with a first UE via a service link of the NTN.

[0023] Figure 16 Illustrated is an example architecture of a wireless communication system according to an embodiment disclosed herein.

[0024] Figure 17 Illustrated is a system for performing signaling between a wireless device and a RAN device connected to a CN of a core network device according to an embodiment disclosed herein. Detailed Description

[0025] Various embodiments are described with respect to a UE. However, the reference to the UE is provided for illustrative purposes only. Example embodiments can be used with any electronic component that can establish a connection with a network and is configured with hardware, software, and / or firmware for exchanging information and data with the network. Thus, the UE as described herein is used to represent any suitable electronic component.

[0026] Embodiments for Non-Terrestrial Networks (NTN)

[0027] Figure 1 Illustrated is an NTN architecture 100 of a wireless communication system according to an embodiment. The NTN architecture 100 includes a core network (CN) 102, a terrestrial base station 104, a satellite gateway 106, a satellite 108, and a UE 110. The terrestrial base station 104, the satellite gateway 106, and the satellite 108 can be included in a RAN 112.

[0028] In some embodiments, the RAN 112 includes an E-UTRAN, the CN 102 includes an EPC, and the terrestrial base station 104 includes an eNB. In these cases, the CN link 114 connecting the CN 102 and the terrestrial base station 104 can include an S1 interface.

[0029] In some embodiments, RAN 112 includes NG-RAN, CN 102 includes 5GC, and the terrestrial base station 104 includes a gNB or a next-generation eNB (ng-eNB). In such a case, the CN link 114 connecting CN 102 and the terrestrial base station 104 may include an NG interface.

[0030] The NTN architecture 100 illustrates an architecture based on a "bent pipe" or "transparent" satellite. In such a bent pipe system, the terrestrial base station 104 communicates with the satellite 108 via a feeder link 116 using a satellite gateway 106. The satellite 108 may be equipped with one or more antennas capable of broadcasting a cell according to RAN 112, and the UE 110 may be equipped with one or more antennas capable of communicating with the satellite 108 via the Uu interface on the cell (e.g., a mobile parabolic antenna, an omnidirectional phased array antenna, etc.) (such communication can be said to use the illustrated service link 118). Then, the payload disposed on the satellite 108 transparently forwards data between the satellite gateway 106 and the UE 110 using the feeder link 116 between the satellite gateway 106 and the satellite 108 and the service link 118 between the satellite 108 and the UE 110. The payload may perform radio frequency (RF) conversion and / or amplification in both the uplink (UL) and the downlink (DL) to enable such communication.

[0031] In Figure 1 the illustrated embodiment, the terrestrial base station 104 is illustrated as not having the ability to directly perform terrestrial wireless communication with the UE. However, it is conceivable that in other embodiments, such a terrestrial base station that communicates with the satellite 108 using the satellite gateway 106 may (also) have this function (i.e., as in the terrestrial base stations 1612 and 1614 described below). Figure 16

[0032] It is understood that in Figure 1 an alternative embodiment, the satellite 108 may alternatively be a non-satellite NTN vehicle (e.g., an airplane, an unmanned aerial vehicle (UAV), an unmanned aerial vehicle system (UAS), a dirigible, a balloon, etc.). Additionally, it is understood that in such alternative embodiments, the satellite gateway 106 may alternatively be a gateway for or corresponding to the applicable NTN vehicle type.

[0033] Figure 2 Illustrated is an NTN architecture 200 of a wireless communication system according to an embodiment. The NTN architecture 200 includes a CN 202, a satellite gateway 204, a satellite base station 206, and a UE 208. The satellite gateway 204 and the satellite base station 206 may be included in a RAN 210.

[0034] In some embodiments, RAN 210 includes E-UTRAN, and CN 202 includes EPC. In these cases, the CN link 212 connecting CN 202 and the satellite gateway 204 may include the S1 interface.

[0035] In some embodiments, RAN 210 includes NG-RAN, and CN 202 includes 5GC. In such cases, the CN link 212 connecting CN 202 and the satellite gateway 204 may include the NG interface.

[0036] The NTN architecture 100 implements a "regenerative" satellite-based architecture. In such a regenerative system, the functions of the base stations are provided on the satellite base station 206, and the communication between these base station functions and CN 202 occurs via the interfaces found on the CN link 212 (e.g., the S1 interface and / or the NG interface) forwarded via the satellite gateway 204 and the feeder link 214 to the satellite base station 206. The satellite base station 206 may be equipped with one or more antennas capable of broadcasting cells according to RAN 210, and the UE 208 may be equipped with one or more antennas (e.g., a mobile parabolic antenna, an omnidirectional phased array antenna, etc.) capable of communicating with the satellite base station 206 via the Uu interface on the cell (such communication can be said to use the illustrated service link 216). Then, the payload provided on the satellite base station 206 forwards data between the satellite gateway 204 and the UE 208 using the feeder link 214 between the satellite gateway 204 and the satellite base station 206 and the service link 216 between the satellite base station 206 and the UE 208. The payload may perform RF conversion and / or amplification in both the uplink (UL) and the downlink (DL) to enable this communication, as well as implement the functions of the base station (e.g., as an eNB, ng-eNB, or gNB, as appropriate for the type of RAN 210) as if these were provided on the satellite base station 206.

[0037] In embodiments of the NTN architecture including NG-RAN that also uses integrated access and backhaul (IAB), it may be possible that the gNB control unit function (CU) may be provided on the ground and may communicate with the satellite carrying the corresponding gNB donor unit function (DU) using the satellite gateway, where the F1 interface between the CU and the DU is supported by the feeder link 214. In such cases, the CU and the DU may each be understood as part of the NG-RAN.

[0038] It will be understood that in Figure 2 an alternative embodiment, the satellite base station 206 may alternatively be a non-satellite NTN base station (e.g., an aircraft, UAV, UAS, airship, balloon, etc.). Additionally, it will be understood that in such alternative embodiments, the satellite gateway 204 may alternatively be a gateway for or corresponding to the applicable NTN vehicle type.

[0039] Wireless communication systems can benefit from uplink capacity and throughput enhancements in the NTN context.

[0040] In addition, mechanisms for using multiplexing to enhance uplink capacity and throughput in the NTN context can improve uplink capacity and / or enhance throughput.

[0041] In some embodiments, orthogonal cover codes (OCCs) can be used in the NTN context to achieve multiplexing via orthogonal spreading.

[0042] In some embodiments, an allocation of sub - physical resource blocks (sub - PRBs) can be used in the NTN context, where a sub - PRB is a frequency - domain resource that is less than 12 sub - carriers used for a full physical resource block (PRB). The sub - PRB allocation can occur on a per - UE basis. Such sub - PRB allocations can be used to achieve frequency - domain multiplexing.

[0043] For example, embodiments of the multiplexing mechanisms disclosed herein discuss procedures for using OCCs for uplink multiplexing in the NTN context, including, for example, signaling details for uplink grant - to - transmit using OCCs (e.g., downlink control information (DCI) format modifications for dynamic grants and / or configured grant configuration modifications) and details for OCC sequence index determination in various scenarios (such as cases where there are multiple PRBs in the physical uplink shared channel (PUSCH), cases where there is frequency hopping for the PUSCH, and / or cases where a single DCI is used to schedule multiple PUSCHs).

[0044] Other examples disclosed herein correspond to multiplexing mechanisms that support / use sub - PRB allocations (e.g., on a per - UE basis). Some such embodiments discuss a resource indication bitmap for sub - PRB resource allocation (e.g., for the physical uplink shared channel (PUSCH)) in the context of resource allocation type 0, which uses a resource block group (RBG) configuration that has components understood / represented as fractional numbers of PRBs. As another example, some such embodiments discuss resource allocation type 1, which uses a frequency resource indicator value (FRIV) calculation / formula for / according to sub - PRB operation. For either / both of such resource allocation type 0 or type 1 cases, other embodiments disclosed herein discuss the use of transport block size (TBS) determination, which utilizes an understanding of the total number of resource elements (REs) (e.g., for the PUSCH).

[0045] Embodiments for Uplink Multiplexing Using OCC

[0046] Figure 3 FIG. 300 illustrates a flow chart corresponding to the use of uplink multiplexing using OCC spreading according to various embodiments discussed herein.

[0047] Flow chart 300 illustrates the communication between UE 302 and base station 304. This communication can be the service link communication between UE 302 and base station 304 via NTN. Additionally, although flow chart 300 only illustrates a single UE 302, it should be understood that, for example, base station 304 performs communications similar to those described in connection with UE 302 and multiple UEs (other than UE 302), with the end result that each of these multiple UEs is configured with a different OCC sequence such that spatial domain multiplexing occurs / is prepared to occur with respect to UL transmissions across each of these multiple UEs.

[0048] This communication can be that UE 302 transmits 306 a capability message to base station 304 reporting one or more capabilities of UE 302. Using the information in this capability message, the UE can indicate its capability to perform uplink transmissions to base station 304 using OCC spreading over the service link. In some cases, there can be separate capability reports within the capability message for each of the physical uplink shared channel (PUSCH) and the physical uplink control channel (PUCCH) (e.g., UE 302 can report that it can transmit one of PUSCH and PUCCH using OCC spreading over the service link, but not report that it can transmit (or can affirmatively report that it cannot transmit) the other of PUSCH and PUCCH).

[0049] Then, base station 304 decides 308 to configure one or more of the UEs (e.g., including UE 302) to use spread OCC over the service link. This decision regarding the one or more UEs can depend on one or more factors.

[0050] For example, if the network congestion level is high, then base station 304 can decide 308 to configure the UEs (e.g., including UE 302) to use OCC spreading.

[0051] Alternatively and / or additionally, if the UE (e.g., UE 302) has reported (e.g., using the capability message as described) its ability to use OCC spreading, then base station 304 can decide 308 to configure that UE to use OCC spreading.

[0052] Alternatively and / or additionally, base station 304 can decide 308 whether to configure the UE (e.g., UE 302) to use OCC spreading based on the number of physical resource blocks (PRBs) used for the uplink transmission of the UE.

[0053] Alternatively and / or additionally, the base station 304 may determine 308 whether to configure the UE (e.g., UE 302) to use OCC spreading based on the number of retransmissions of the uplink transmission for the UE (e.g., UE 302).

[0054] Alternatively and / or additionally, the base station 304 may determine 308 whether to configure the UE (e.g., UE 302) to use OCC spreading based on the starting time slot of the uplink transmission of the UE (e.g., UE 302).

[0055] Alternatively and / or additionally, the base station 304 may determine 308 to configure the UE to use OCC spreading based on the timing advance (TA) value reported by the UE (e.g., UE 302). For example, in the case where two UEs report similar TA values, the two UEs may be configured to share the same time-frequency resources for the corresponding UL transmission, where each UE uses a separate OCC spreading code.

[0056] Alternatively and / or additionally, the base station 304 may determine 308 whether to configure the UE (e.g., UE 302) to use OCC spreading based on whether demodulation reference signal (DMRS) bundling is applied at the UE (e.g., UE 302). For example, the determination may be that if the UE uses DMRS bundling, the base station 304 determines not to use OCC spreading for uplink multiplexing at the UE.

[0057] Then, in the first case 310, the base station 304 transmits 312 to the UE 302 a dynamic uplink grant indicating that the UE 302 will use OCC spreading. In the first case 310, the dynamic uplink grant may be DCI format 0_1 or DCI format 0_2 indicating an OCC sequence index that identifies the OCC sequence to be used by the UE 302 for OCC spreading. Then, the UE transmits 314 a PUSCH with data spread by the identified OCC sequence.

[0058] In some examples of the first case 310, the applicable OCC size is configured for the UE 302 via radio resource control (RRC) signaling. In such cases, the identification of the OCC sequence to be used for OCC spreading is performed by applying the OCC sequence index indicated in the DCI to the set of OCC sequences with the configured size. For example, if the RRC signaling configures an OCC size of N occ = 12, the OCC sequence index provided in the DCI (i.e., e.g., represented using bits) is indexed into the set of OCC sequences with an OCC size of 12 known to the UE.

[0059] In an alternative example of the first scenario 310, both the OCC size to be used and the OCC sequence index are indicated in the DCI. For example, in addition to the OCC sequence index just described, the DCI also includes an indication of the OCC size (e.g., an indication that N occ = 12). Then, the OCC sequence index provided in the DCI is indexed into a set of OCC sequences with an OCC size of 12 known to the UE.

[0060] According to the first scenario 310, the scenario can be that the DCI has a dedicated field for indicating the OCC sequence index as described. The scenario can also be that the DCI has a dedicated field for indicating the OCC size as described (e.g., in the case where the DCI will indicate the OCC size).

[0061] Note that in some instances where a single such DCI schedules multiple PUSCHs, the OCC sequence to be used for spreading the second PUSCH can be understood to be the same as the OCC sequence identified for spreading the first PUSCH (e.g., as indicated by the OCC sequence index in the DCI).

[0062] In other instances where a single such DCI schedules multiple PUSCHs, the OCC sequence to be used for spreading the second PUSCH can be the OCC sequence identified by adding 1 to the OCC sequence index corresponding to the first PUSCH (e.g., such that the next OCC sequence in the applicable OCC sequence set is used for spreading the second PUSCH).

[0063] Alternatively, the OCC sequence to be used for spreading a retransmission of the PUSCH can be identified by adding some other offset value to the OCC sequence index corresponding to the first PUSCH (with wrapping around) (e.g., such that the UE 302 "jumps" in a determinable / definable manner to another OCC sequence in the applicable OCC sequence set and then is used for spreading the second PUSCH).

[0064] As an alternative to the first scenario 310, in the second scenario 316, the base station 304 transmits 318 to the UE 302 an uplink grant indicating the configuration for which the UE 302 will use OCC spreading. Note that similar to the first scenario 310, the second scenario 316 contemplates using an OCC sequence index to identify the OCC index used in the OCC spreading operation from a set of OCC sequences corresponding to the OCC size. Then, the UE transmits 320 a PUSCH with data spread by the identified OCC sequence.

[0065] In some examples of the second case 316, a configured grant of type 1 (a configured grant configured by RRC signaling and implicitly activated by RRC signaling) may be used. Such type 1 grants may use a configured grant configuration that includes fields for both the OCC size and the OCC sequence index. The following is an example (a part) of such a configured grant configuration of type 1:

[0066] ConfiguredGrantConfig::=SEQUENCE{

[0067] rrc-ConfiguredUplinkGrant SEQUENCE{

[0068] OCC-size ENUMERATED{1,2,4,6,12}

[0069] OCC-sequence

[0070] …

[0071] where "OCC-size" is the OCC size and "OCC-sequence" is the OCC sequence index.

[0072] In other examples of the second case 316, a configured grant of type 2 (a configured grant configured by RRC signaling and then activated / deactivated by DCI) may be used.

[0073] In some cases of the configured grant of type 2, both the OCC size and the OCC sequence index may be present in such a configured grant configuration (e.g., similar to that discussed above for the configured grant configuration of type 1).

[0074] In some cases of the configured grant of type 2, the OCC size may be configured in the configured grant configuration, and then the indication of the OCC sequence index used for the corresponding OCC size may arrive in the activation DCI for the configured grant configuration.

[0075] In some cases of the configured grant of type 2, both the indication of the OCC size and the indication of the OCC sequence index used for the corresponding OCC size may arrive in the activation DCI for the configured grant configuration.

[0076] Note that in various embodiments (e.g., according to the first case 310 for dynamic grants or the second case 316 for configured grants), PUSCH retransmission may be used. Such cases may implement OCC spreading for PUSCH retransmission in one of multiple possible ways.

[0077] In a first such manner, all instances of the PUSCH use the same OCC sequence as indicated in the applicable DCI / configuration grant configuration.

[0078] In a second such manner, an OCC sequence cycling is used. Under the OCC sequence cycling, the OCC sequence indicated in the applicable DCI / configuration grant configuration can be used to spread the initial instance of the PUSCH. Then, the OCC sequence to be used to spread the retransmission of the PUSCH can be the OCC sequence identified by adding 1 to the OCC sequence index corresponding to the initial instance of the PUSCH (e.g., such that the next OCC sequence in the applicable OCC sequence set is used to spread the retransmission of the PUSCH). Alternatively, the OCC sequence to be used to spread the retransmission of the PUSCH can be identified by adding some other offset value to the OCC sequence index corresponding to the initial instance of the PUSCH (with wrap-around) (e.g., such that the UE 302 "jumps" in a determinable / definable manner to another OCC sequence in the applicable OCC sequence set which is then used to spread the retransmission of the PUSCH).

[0079] Note that in various embodiments (e.g., according to the first case 310 for dynamic grant or the second case 316 for configured grant), multiple PRBs can be scheduled for PUSCH use. Such cases can be implemented in one of several possible ways for OCC spreading across these multiple PRBs.

[0080] In a first such manner, all PRBs scheduled for the PUSCH use the same OCC sequence as indicated in the applicable DCI / configuration grant configuration.

[0081] In a second such manner, an OCC sequence cycling is used. Under the OCC sequence cycling, the OCC sequence to be used to spread on the first (lowest) PRB is the OCC sequence as indicated in the applicable DCI / configuration grant configuration. Then, the OCC sequence to be used to spread on the second (second lowest) PRB can be the OCC sequence identified by adding 1 to the OCC sequence index corresponding to the first PRB (e.g., such that the next OCC sequence in the applicable OCC sequence set is used to spread the second lowest PRB). Alternatively, the OCC sequence to be used to spread on the second PRB can be identified by adding some other offset value to the OCC sequence index corresponding to the first PRB (with wrap-around) (e.g., such that the UE 302 "jumps" in a determinable / definable manner to another OCC sequence in the applicable OCC sequence set which is then used to spread the second PRB).

[0082] Note that in various embodiments (e.g., according to the first case 310 for dynamic grant or the second case 316 for configured grant), frequency hopping may be applied to the PUSCH. Such cases may implement OCC spreading for frequency hopping in one of a variety of possible ways.

[0083] In a first such way, the same OCC sequence as indicated in the applicable DCI / configured grant configuration is used for each of no frequency hopping, the first hop, and the second hop of the PUSCH.

[0084] In a second such way, an OCC sequence cycle is used. Under the OCC sequence cycle, the OCC sequence indicated in the applicable DCI / configured grant configuration is used to spread no frequency hopping. Then, the OCC sequence used to spread the first hop may be the OCC sequence identified by incrementing the OCC sequence index for no frequency hopping by 1, and the OCC sequence used to spread the second hop may be the OCC sequence identified by incrementing the OCC sequence index for no frequency hopping by 2 (e.g., such that the progressively next OCC sequence in the applicable OCC sequence set is used to spread subsequent hops). Alternatively, the OCC sequence used to spread on the first hop may be identified by adding a certain first offset value to the OCC sequence index corresponding to no frequency hopping (with wrap-around), and the OCC sequence used to spread on the second hop may be identified by adding a certain second offset value to the OCC sequence index corresponding to no frequency hopping (with wrap-around) (e.g., such that the UE 302 "hops" in a determinable / definable way to other OCC sequences in the applicable OCC sequence set that are then used to spread the first hop and the second hop).

[0085] Embodiments for Uplink Multiplexing Using Sub-PRB Resource Allocation

[0086] In some embodiments, a frequency allocation mechanism that can allocate sub-PRB resources in the frequency domain (e.g., on a per-UE basis) may be used.

[0087] Figure 4 An illustration 400 of PRB 402 on a symbol 404 is shown. As illustrated, PRB 402 consists of 12 REs 406. Additionally, as also illustrated, according to one type of sub-PRB scheme, it can be understood that PRB 402 consists of two sub-PRBs (first sub-PRB 408 and second sub-PRB 410) each having six REs.

[0088] The use of two PRBs each having six REs is given here by way of example and not limitation. Note that in other sub-PRB schemes, a PRB may alternatively consist of, for example, three sub-PRBs each having four REs or four sub-PRBs each having three REs.

[0089] Note that in this document, even when the continuous size of the final allocation is equal to or greater than the PRB size, for example, the resource allocation that occurs on a sub - PRB basis can also be referred to as "sub - PRB resource allocation" (or similar expressions).

[0090] For various reasons, the ability to allocate uplink resources to a UE on a sub - PRB basis in the NTN context may be beneficial. For example, the situation can be that frequency - domain transmission resources are relatively more limited in the NTN context than in the terrestrial access context. Therefore, the ability to allocate uplink resources to a UE on a sub - PRB basis can allow the base station to fit more UEs into the available frequency - domain transmission resources.

[0091] Note that in various NTN contexts, the uplink transmission requirements of the UE may be less (e.g., according to the user's expectation that the coverage in the NTN case is not as robust as in the terrestrial coverage case). The allocation of sub - PRBs in such contexts (e.g., as just discussed, to achieve a more efficient per - UE use of the limited frequency - domain resources) can reflect the understanding that for the NTN context, the desired UE uplink speed may be relatively low, and thus any degradation in the quality of service at each UE associated with the uplink resource allocation on a sub - PRB basis will be acceptable / expected.

[0092] Now discuss type 0 resource allocation.

[0093] In the mechanism for resource allocation type 0, a bitmap is used to indicate the transmission resources to the UE. The bits in the bitmap are understood to correspond to resource block groups (RBGs). A "1" in the bitmap indicates to the UE that the UE is allocated the use of that RBG (e.g., the corresponding RBG can be used for uplink transmission and / or for downlink reception, as the case may be), while a "0" in the bitmap indicates to the UE that the UE has not been allocated the use of that RBG (e.g., the UE cannot use the corresponding RBG for uplink transmission and / or for downlink reception, as the case may be).

[0094] The size (in PRBs) of each RBG represented in the incoming type 0 resource allocation bitmap can be understood at the UE according to the configuration. Figure 5Table 500 illustrates the first configuration 502, the second configuration 504, and the third configuration 506 showing the use corresponding to resource allocation type 0. As illustrated in Table 500, for any one of the first configuration 502, the second configuration 504, and the third configuration 506 configured at the UE, the incoming type 0 resource allocation bitmap can be determined by the UE as a function of the RBG size (denoted by P) in terms of the number of PRBs for the applicable / active bandwidth part (BWP) size 508. For example, according to Table 500, when the UE is configured to use the second configuration 504 and the applicable frequency-domain BWP size is between 73 PRBs and 144 PRBs, the UE will understand that each bit of any incoming resource allocation type 0 bitmap corresponds to an RBG (P = 16) with 16 PRBs each.

[0095] For example, refer to Table 6.1.2.2.1-1 and more generally to Section 6.1.2.2.1 (uplink case) of 3GPP Technical Specification (TS) 38.214 version 18.0.0 (September 2023) (hereinafter referred to as 3GPP TS 38.214), and Table 5.1.2.2.1-1 and more generally to Section 5.1.2.2.1 (downlink case) of 3GPP TS 38.214.

[0096] Then, note that for the uplink case, for an uplink BWP of size PRBs, the total number N of RBGs in the uplink BWP RBG can be understood at the UE by using the following formula:

[0097] Where:

[0098] P is the RBG size determined in terms of the number of PRBs, and is the starting PRB index of the BWP relative to the common resource block (CRB) of the channel where the BWP resides.

[0099] The embodiments discussed herein relate to using resource allocation type 0 to provide the UE with an uplink allocation in terms of sub-PRB resources. In such cases, to support per-UE sub-PRB allocation, a new RBG configuration type can be introduced.

[0100] Figure 6 Table 600 illustrates the first configuration 602, the second configuration 604, the third configuration 606, and the fourth configuration 608 showing the use corresponding to the use of resource allocation type 0. The first configuration 602, the second configuration 604, and the third configuration 606 can respectively correspond to as combined with Figure 5The first configuration 502, second configuration 504, and third configuration 506 discussed in Table 500. Then, the fourth configuration 608 corresponds to the new RBG configuration type discussed herein.

[0101] Such a new RBG configuration type may use a nominal RBG size P as the RBG size, where the nominal RBG size represents a fraction of a PRB (sub-PRB). For example, in some such configurations, P may be equal to 1 / 2 of a PRB (e.g., 6 REs), 1 / 3 (e.g., 4 REs), or 1 / 4 (e.g., 3 REs).

[0102] The fourth configuration 608 represents a first example of the new RBG configuration type. The fourth configuration 608 corresponds to a case where, for example, the value of P depends on the BWP size 610. For example, for a BWP size from 1 to 36, P = 1 / 4 (corresponding to the case where each bit of the bitmap corresponds to a sub-PRB with three REs); for a BWP size from 37 to 72, P = 1 / 2 (corresponding to the case where each bit of the bitmap corresponds to a sub-PRB with six REs); for a BWP size from 73 to 144, P = 1 (corresponding to the case where each bit of the bitmap corresponds to a single PRB); and for a BWP size from 145 to 275, P = 2 (corresponding to the case where each bit of the bitmap corresponds to two PRBs). Thus, when configured to use the fourth configuration 608, whenever the BWP size is less than or equal to 72 PRBs, the UE will understand that the bits in the incoming type 0 resource allocation bitmap allocate resources in terms of sub-PRBs.

[0103] The fourth configuration 608 is given by way of example and not limitation. It is contemplated that in similar configurations, various values (fractional and / or non-fractional) of P corresponding to various (modifiable) quantities and combinations of P depending on the BWP size may be used.

[0104] In a second example of the new RBG configuration type, the value of P may be a fractional value as discussed and may be fixed relative to / independent of the BWP size.

[0105] In the case of using sub-PRBs (where P is a fractional value), the total number N of RBGs represented in the resource allocation type 0 bitmap RBG is given by the following formula:

[0106]

[0107] Corresponding to some such cases, P may be equal to, for example, 1 / 2 (for 6 REs in an RBG), 1 / 3 (for 4 REs in an RBG), or 1 / 4 (for 3 REs in an RBG). Then, each bit in the type 0 resource allocation bitmap indicates whether a particular sub-PRB of the quantity of REs controlled by P within the allocation range is allocated for use by the UE.

[0108] The use of the new RBG configuration type can be indicated to the UE in the configured grant configuration for the grant mechanism used by the UE (e.g., in the "ConfiguredGrantConfig" information element (IE)). Alternatively, the use of the new RBG configuration type can be indicated to the UE in the UE-specific PUSCH configuration (e.g., in the "PUSCH-Config" IE).

[0109] Now, type 1 resource allocation is discussed.

[0110] In some mechanisms for resource allocation type 1, the resource unit (e.g., the allocation unit) is a PRB, and the FRIV is correspondingly used to indicate to the UE the allocation of uplink transmission resources in such units (PRBs). The FRIV value (sometimes denoted as RIV) finally calculated and provided to the UE depends on the starting RB (RB start ), the length (L RB ) of consecutive RBs in the frequency-domain resources to be allocated to the UE, and the size of the uplink BWP in terms of PRBs For example:

[0111] If Then

[0112]

[0113] Otherwise,

[0114] Where

[0115] L RBs ≥ 1 and should not exceed

[0116] Upon receiving the FRIV (RIV), the UE applies its independent information to reverse the procedure to determine the RB start and L RBs , thereby identifying the uplink frequency-domain allocation. Generally refer to section 6.1.2.2.2 of 3GPP TS 38.214.

[0117] The embodiments discussed herein relate to using resource allocation type 0 to provide the UE with uplink allocation in units of sub-PRB resources (instead of in units of full PRBs).

[0118] For such cases, to support per-UE sub-PRB allocation, the granularity of the resource unit is understood to be in terms of sub-PRBs rather than PRBs. For such cases, the number of sub-PRBs in a single PRB can be denoted as (e.g., where It means that each PRB has 2 sub - PRBs, and each sub - PRB has 6 REs; It means that each PRB has 3 sub - PRBs, and each sub - PRB has four REs; and among them It means that each PRB has 4 sub - PRBs, and each sub - PRB has 3 REs).

[0119] Then, the FRIV (RIV) finally calculated and provided to the UE depends on the starting sub - PRB (subRB start ), the length (L subRBs ) of the consecutive sub - PRBs in the frequency - domain resources to be allocated to the UE, and the size of the uplink BWP in terms of PRBs For example:

[0120] If Then

[0121]

[0122] Otherwise,

[0123]

[0124] Among them

[0125] L subRBs ≥1 and should not exceed

[0126] Now discuss the determination of the transport block size (TBS) in the context of the allocation in sub - PRBs.

[0127] However, resources are allocated to the UE (e.g., regardless of whether resource allocation type 0 or resource allocation type 1 is used), and the UE may also need to determine the appropriate / expected TBS to be used within the allocated uplink resources. The appropriate TBS may depend on the number of REs allocated in the PUSCH (denoted as N RE ). Therefore, now describe the mechanism for determining the number of REs allocated in the PUSCH.

[0128] Now discuss the mechanism for determining the number of REs allocated in the PUSCH under the type 0 resource allocation mechanism as described herein.

[0129] The UE first determines the number of REs allocated for the PUSCH within a fractional - sized RBG (sub - PRB). This value can be denoted as N′ RE , which is calculated using the following formula:

[0130] Where:

[0131] N′ REis the first number of REs allocated for PUSCH within each RBG among one or more RBGs;

[0132] is the number of subcarriers per PRB in the frequency domain;

[0133] is the number of symbols for PUSCH;

[0134] is the number of REs per PRB for the demodulation reference signal (DM-RS);

[0135] is the overhead per PRB configuration in terms of the number of REs; and

[0136] P is the RBG size for PUSCH expressed in PRBs.

[0137] Then, for N′ RE floor, ceiling, and / or rounding operations may be used to keep N′ RE as an integer.

[0138] Using N′ RE , the UE then determines the total number of REs (N RE ) allocated for PUSCH. For the case of using a single time slot for TBS calculation, N RE can be calculated using the following formula:

[0139] N RE = min(156·P, N′ RE )·n subPRB ,

[0140] where nsub PRB is the number of sub-PRBs allocated to the UE.

[0141] For the case of transmitting the transport block through multiple time slots, N RE can be calculated using the following formula:

[0142] N RE = N·min(156P, N′ RE )·n subPRB ,

[0143] where N is the number of time slots for TBS.

[0144] Then, floor, ceiling, and / or rounding operations may be used for N RE to keep N RE as an integer.

[0145] Now discuss the mechanism for determining the number of REs allocated within the PUSCH under the type 1 resource allocation mechanism as described herein.

[0146] The UE first determines N′ using the following formula RE :

[0147] where:

[0148] is the number of sub - carriers per PRB in the frequency domain;

[0149] is the number of symbols for the PUSCH;

[0150] is the number of REs per PRB for the demodulation reference signal (DM - RS);

[0151] is the overhead per PRB configuration in terms of the number of REs; and

[0152] is the number of sub - PRBs in a single PRB.

[0153] Then, for N′ RE round - down, round - up, and / or rounding operations can be used to keep N′ RE as an integer.

[0154] Using N′ RE , the UE then determines the total number of REs (N RE ) allocated for the PUSCH. For the case where a single time - slot is used for TBS calculation, N RE can be calculated using the following formula:

[0155]

[0156] where n subPRB is the number of sub - PRBs allocated to the UE.

[0157] For the case where the transport block is processed over multiple time - slots, N RE can be calculated using the following formula:

[0158]

[0159] where N is the number of time - slots for the TBS.

[0160] Then, for N RE round - down, round - up, and / or rounding operations can be used to keep N RE as an integer.

[0161] Once NRE Known to the UE (e.g., according to the type 0 allocation pattern formula or the type 1 allocation formula, as appropriate) for using N RE The remaining steps for inferring the TBS determination can follow existing / known mechanisms (e.g., refer to the second, third, and fourth steps in Section 5.1.3.2 of 3GPP TS 38.214).

[0162] Figure 7 Illustrated is a flowchart 700 corresponding to the use of uplink multiplexing on a per-sub-PRB basis in the frequency domain according to various embodiments discussed herein.

[0163] Flowchart 700 illustrates the communication between UE 702 and base station 704. This communication can be the communication between UE 702 and base station 704 via the service link of NTN. In addition, although flowchart 700 only illustrates a single UE 702, it should be understood that, for example, base station 704 performs communications similar to those described in connection with UE 702 and multiple UEs (other than UE 702), and the end result is that each of these multiple UEs is configured with a different sub-PRB configuration such that frequency domain multiplexing occurs / is prepared to occur with respect to UL transmissions made by each of these multiple UEs.

[0164] This communication can be that UE 702 transmits 706 a capability message reporting one or more capabilities of UE 702 to base station 704. Using the information in this capability message, the UE can indicate its capability to perform uplink transmissions with base station 704 via the service link using sub-PRB frequency domain allocation. In some cases, there may be separate capability reports within the capability message for each of the physical uplink shared channel (PUSCH) and the physical uplink control channel (PUCCH) (e.g., UE 702 can report that it can use sub-PRB frequency domain allocation to transmit one of PUSCH and PUCCH via the service link, but does not report that it can use sub-PRB frequency domain allocation to transmit (or can definitely report that it cannot transmit) the other of PUSCH and PUCCH).

[0165] Then, base station 704 decides 708 to configure one or more of the UEs (e.g., including UE 702) to use sub-PRB-based frequency domain allocation via the service link.

[0166] For example, if the network congestion level is high, base station 704 can decide 708 to configure the UEs (e.g., including UE 302) to use sub-PRB-based frequency domain allocation via the service link.

[0167] Alternatively and / or additionally, if the UE (e.g., UE 702) has reported (e.g., using the capabilities message as described) that it is capable of using sub - PRB - based frequency domain allocation over the serving link, then the base station 704 may decide 708 to configure the UE to use sub - PRB - based frequency domain allocation over the serving link.

[0168] Alternatively and / or additionally, the base station 704 may decide 708 whether to configure the UE (e.g., UE 702) to use sub - PRB - based frequency domain allocation over the serving link based on the number of PRBs used for the UE's (e.g., UE 702) uplink transmission.

[0169] Alternatively and / or additionally, the base station 704 may decide 708 whether to configure the UE (e.g., UE 702) to use sub - PRB - based frequency domain allocation over the serving link based on the number of re - transmissions of the UE's (e.g., UE 702) uplink transmission.

[0170] Alternatively and / or additionally, the base station 704 may decide 708 whether to configure the UE (e.g., UE 702) to use sub - PRB - based frequency domain allocation over the serving link based on the starting time slot of the UE's (e.g., UE 702) uplink transmission.

[0171] Alternatively and / or additionally, the base station 704 may decide 708 whether to configure the UE (e.g., UE 702) to use sub - PRB - based frequency domain allocation over the serving link based on the timing advance (TA) reported by the UE (e.g., UE 702). For example, in the case where two UEs report similar TA values, the two UEs may be configured to share the same time resources for the corresponding UL transmission, where each UE uses a separate sub - PRB frequency resource.

[0172] Alternatively and / or additionally, the base station 704 may decide 708 whether to configure the UE (e.g., UE 702) to use sub - PRB - based frequency domain allocation over the serving link based on whether demodulation reference signal (DMRS) bundling is applied at the UE (e.g., UE 702). For example, the decision may be that if the UE uses DMRS bundling, the base station 704 determines not to multiplex sub - PRB - based frequency domain allocation over the serving link for the uplink at the UE.

[0173] The base station 704 may also configure 710 the UE 702 for any desired UL BWP switch, as illustrated.

[0174] Then, in the first case 712, the base station 704 transmits 714 to the UE 702 a dynamic uplink grant providing sub - PRB resource allocation for the PUSCH. The UE 702 accordingly transmits 716 a PUSCH to the base station 704 using the sub - PRB - based resource allocation according to the dynamic uplink grant.

[0175] As an alternative to the first case 712, in the second case 718, the base station 704 transmits 720 to the UE 702 an uplink grant indicating that the UE 702 will use a configuration of sub - PRB resource allocation for the PUSCH. The UE 702 accordingly transmits 722 the PUSCH to the base station 704 using the sub - PRB - based resource allocation according to the configured uplink grant.

[0176] Figure 8 Illustrated is a method 800 for a UE in an NTN according to an embodiment herein to communicate with a base station via a serving link of the NTN. The illustrated method 800 includes receiving 802 from the base station a DCI indicating a dynamic uplink grant for a first PUSCH, where the DCI includes an OCC sequence index. The method 800 further includes using the OCC sequence index to identify 804 a first OCC sequence for the first PUSCH from an OCC sequence set having an OCC size corresponding to the OCC sequence index. The method 800 further includes spreading 806 first data for the first PUSCH into the first PUSCH using the first OCC sequence. The method 800 further includes transmitting 808 the first PUSCH to the base station via the serving link according to the dynamic uplink grant.

[0177] In some embodiments, the method 800 further includes transmitting to the base station a capability message indicating that the UE is capable of performing OCC spreading for uplink transmissions on the serving link.

[0178] In some embodiments of the method 800, the DCI further includes an indication of the OCC size corresponding to the first OCC sequence.

[0179] In some embodiments, the method 800 further includes receiving from the base station RRC signaling indicating the OCC size corresponding to the first OCC sequence index.

[0180] In some embodiments of the method 800, the dynamic uplink grant is also used for a second PUSCH, and the method 800 further includes spreading second data for the second PUSCH into the second PUSCH using the first OCC sequence and transmitting the second PUSCH to the base station via the serving link.

[0181] In some embodiments of method 800, the dynamic uplink grant is also used for a second PUSCH, and method 800 further includes: identifying a second OCC sequence for the second PUSCH from the set of OCC sequences having the OCC size, spreading second data for the second PUSCH into the second PUSCH using the second OCC sequence, and transmitting the second PUSCH to the base station over the serving link. In some such embodiments, the second OCC sequence is the next OCC sequence in the set of OCC sequences having the OCC size after the first OCC sequence. In some other such embodiments, the second OCC sequence is identified from the set of OCC sequences having the OCC size by applying an offset relative to the first OCC sequence in the set of OCC sequences having the OCC size.

[0182] In some embodiments of method 800, the UE is configured for PUSCH retransmission, and method 800 further includes: spreading the first data into a retransmission of the first PUSCH using the first OCC sequence, and transmitting the retransmission of the first PUSCH to the base station over the serving link.

[0183] In some embodiments of method 800, the UE is configured for PUSCH retransmission, and method 800 further includes: identifying a second OCC sequence for a retransmission of the first PUSCH from the set of OCC sequences having the OCC size, spreading the first data into the retransmission of the first PUSCH using the second OCC sequence, and transmitting the retransmission of the first PUSCH to the base station over the serving link. In some such embodiments, the second OCC sequence is the next OCC sequence in the set of OCC sequences having the OCC size after the first OCC sequence. In some other such embodiments, the second OCC sequence is identified from the set of OCC sequences having the OCC size by applying an offset relative to the first OCC sequence in the set of OCC sequences having the OCC size.

[0184] In some embodiments of method 800, multiple PRBs are used for the first PUSCH, and the first data for the first PUSCH is spread into a first PRB among the multiple PRBs using the first OCC sequence, and method 800 further includes spreading second data for the first PUSCH into a second PRB among the multiple PRBs using the first OCC sequence.

[0185] In some embodiments of method 800, multiple PRBs are used for the first PUSCH, and the first data for the first PUSCH is spread to the first PRB among the multiple PRBs using the first OCC sequence. Method 800 further includes: identifying a second OCC sequence for a second PRB among the multiple PRBs from an OCC sequence set having the OCC size, and spreading second data for the first PUSCH to the second PRB using the second OCC sequence. In some such embodiments, the second OCC sequence is the next OCC sequence in the OCC sequence set having the OCC size after the first OCC sequence. In some other such embodiments, the second OCC sequence is identified from the OCC sequence set having the OCC size by applying an offset relative to the first OCC sequence in the OCC sequence set having the OCC size.

[0186] In some embodiments of method 800, the UE is configured to use frequency hopping for the first PUSCH and spread the first data for the first PUSCH to the no-hopping of the frequency hopping using the first OCC sequence. Method 800 further includes: spreading second data for the first PUSCH to the first hop of the frequency hopping using the first OCC sequence, and spreading third data for the first PUSCH to the second hop of the frequency hopping using the first OCC sequence.

[0187] In some embodiments of method 800, the UE is configured to use frequency hopping for the first PUSCH and spread the first data for the first PUSCH to the no-frequency-hopping of the frequency hopping using the first OCC sequence; and method 800 further includes: identifying a second OCC sequence for the first hop of the frequency hopping from an OCC sequence set having the OCC size, spreading the second data for the first PUSCH to the first hop using the second OCC sequence, identifying a third OCC sequence for the second hop of the frequency hopping from the OCC sequence set having the OCC size, and spreading the third data for the first PUSCH to the second hop using the third OCC sequence. In some such embodiments, the second OCC sequence is the first next OCC sequence in the OCC sequence set having the OCC size after the first OCC sequence, and the third OCC sequence is the second next OCC sequence in the OCC sequence set having the OCC size after the second OCC sequence. In some other such embodiments, the second OCC sequence is identified from the OCC sequence set having the OCC size by applying a first offset relative to the first OCC sequence in the OCC sequence set having the OCC size, and the third OCC sequence is identified from the OCC sequence set having the OCC size by applying a second offset relative to the first OCC sequence in the OCC sequence set having the OCC size.

[0188] Figure 9 Method 900, which illustrates a method for a UE in NTN according to an embodiment herein to communicate with a base station via a serving link of the NTN, is illustrated. The illustrated method 900 includes receiving 902 RRC signaling from the base station, the RRC signaling including configuration information for a configured uplink grant for a first PUSCH. Method 900 further includes identifying 904 a first OCC sequence for the first PUSCH from an OCC sequence set having an OCC size corresponding to the OCC sequence index using the OCC sequence index. Method 900 further includes spreading 906 the first data for the first PUSCH to the first PUSCH using the first OCC sequence. Method 900 further includes transmitting 908 the first PUSCH to the base station via the serving link according to the configured uplink grant.

[0189] In some embodiments, method 900 further includes transmitting a capability message to the base station, the capability message indicating that the UE is capable of performing OCC spreading for uplink transmission on the serving link.

[0190] In some embodiments of method 900, the configuration information for the configured uplink grant includes the OCC sequence index and the OCC size.

[0191] In some embodiments, method 900 further includes receiving DCI from the base station, the DCI activating the configured uplink grant for use according to the configuration information. In some such embodiments, the configuration information for the configured uplink grant includes the OCC size, and the DCI includes the OCC sequence index. In some other such embodiments, the DCI includes the OCC sequence index and the OCC size.

[0192] In some embodiments of method 900, the UE is configured for PUSCH retransmission, and method 900 further includes: spreading the first data into the retransmission of the first PUSCH using the first OCC sequence; and transmitting the retransmission of the first PUSCH to the base station via the serving link.

[0193] In some embodiments of method 900, the UE is configured for PUSCH retransmission, and method 900 further includes: identifying a second OCC sequence from the set of OCC sequences having the OCC size for the retransmission of the first PUSCH, spreading the first data into the retransmission of the first PUSCH using the second OCC sequence, and transmitting the retransmission of the first PUSCH to the base station via the serving link. In some such embodiments, the second OCC sequence is the next OCC sequence in the set of OCC sequences having the OCC size after the first OCC sequence. In some other such embodiments, the second OCC sequence is identified from the set of OCC sequences having the OCC size by applying an offset relative to the first OCC sequence in the set of OCC sequences having the OCC size.

[0194] In some embodiments of method 900, multiple PRBs are used for the first PUSCH, and the first data for the first PUSCH is spread into the first PRB among the multiple PRBs using the first OCC sequence, and method 900 further includes spreading the second data for the first PUSCH into the second PRB among the multiple PRBs using the first OCC sequence.

[0195] In some embodiments of method 900, multiple PRBs are used for the first PUSCH, and the first data for the first PUSCH is spread to the first PRB among the multiple PRBs using the first OCC sequence. Method 900 further includes: identifying a second OCC sequence for a second PRB among the multiple PRBs from an OCC sequence set having the OCC size, and spreading second data for the first PUSCH to the second PRB using the second OCC sequence. In some such embodiments, the second OCC sequence is the next OCC sequence in the OCC sequence set having the OCC size after the first OCC sequence. In some other such embodiments, the second OCC sequence is identified from the OCC sequence set having the OCC size by applying an offset relative to the first OCC sequence in the OCC sequence set having the OCC size.

[0196] In some embodiments of method 900, the UE is configured to use frequency hopping for the first PUSCH and spread the first data for the first PUSCH to the no-frequency-hopping of the frequency hopping using the first OCC sequence. Method 900 further includes: spreading second data for the first PUSCH to the first hop of the frequency hopping using the first OCC sequence, and spreading third data for the first PUSCH to the second hop of the frequency hopping using the first OCC sequence.

[0197] In some embodiments of method 900, the UE is configured to use frequency hopping for the first PUSCH and spread the first data for the first PUSCH to the no-frequency-hopping of the frequency hopping using the first OCC sequence; and method 900 further includes: identifying, from an OCC sequence set having the OCC size, a second OCC sequence for the first hop of the frequency hopping, spreading the second data for the first PUSCH to the first hop using the second OCC sequence, identifying, from the OCC sequence set having the OCC size, a third OCC sequence for the second hop of the frequency hopping, and spreading the third data for the first PUSCH to the second hop using the third OCC sequence. In some such embodiments, the second OCC sequence is the first next OCC sequence in the OCC sequence set having the OCC size after the first OCC sequence, and the third OCC sequence is the second next OCC sequence in the OCC sequence set having the OCC size after the second OCC sequence. In some other such embodiments, the second OCC sequence is identified from the OCC sequence set having the OCC size by applying a first offset relative to the first OCC sequence in the OCC sequence set having the OCC size, and the third OCC sequence is identified from the OCC sequence set having the OCC size by applying a second offset relative to the first OCC sequence in the OCC sequence set having the OCC size.

[0198] Figure 10 Method 1000 is illustrated for a base station in NTN according to an embodiment herein to communicate with a first UE via a serving link of the NTN. The illustrated method 1000 includes determining 1002 that the UE will use an OCC sequence to spread data of a PUSCH based on an OCC spreading usage factor. Method 1000 further includes transmitting 1004 to the UE a DCI indicating a dynamic uplink grant for the PUSCH, where the DCI includes an OCC sequence index identifying the OCC sequence. Method 1000 further includes: in response to the dynamic uplink grant, receiving 1006 from the UE the PUSCH having the data spread by the OCC sequence.

[0199] In some embodiments, method 1000 further includes receiving from the first UE a capability message indicating that the first UE is capable of performing OCC spreading for uplink transmissions on the serving link.

[0200] In some embodiments of method 1000, the DCI further includes an indication of the OCC size corresponding to the first OCC sequence.

[0201] In some embodiments, method 1000 further includes transmitting RRC signaling to the UE indicating the OCC size corresponding to the first OCC sequence index.

[0202] In some embodiments of method 1000, the OCC spreading factor includes the network congestion level.

[0203] In some embodiments of method 1000, the OCC spreading factor includes determining that the first UE is capable of performing OCC spreading.

[0204] In some embodiments of method 1000, the OCC spreading factor includes the number of PRBs for the PUSCH.

[0205] In some embodiments of method 1000, the OCC spreading factor includes the number of PUSCH retransmissions for the PUSCH.

[0206] In some embodiments of method 1000, the OCC spreading factor includes the starting time slot of the PUSCH.

[0207] In some embodiments of method 1000, the OCC spreading factor includes a comparison between a first TA report from the first UE and a second TA report from a second UE.

[0208] In some embodiments of method 1000, the OCC spreading factor includes determining that DMRS bundling across multiple time slots is not used for communication with the first UE.

[0209] Figure 11 Method 1100 is illustrated for a base station in an NTN according to an embodiment herein to communicate with a first UE via a serving link of the NTN. The illustrated method 1100 includes determining 1102, based on an OCC spreading factor, that the UE will use an OCC sequence to spread data of a PUSCH. Method 1100 further includes transmitting 1104 RRC signaling to the UE, the RRC signaling including configuration information for a configured uplink grant for the first PUSCH. Method 1100 further includes: receiving 1106 from the UE the PUSCH having the data spread by the OCC sequence corresponding to the configured uplink grant.

[0210] In some embodiments, method 1100 further includes receiving a capability message from the first UE, the capability message indicating that the first UE is capable of performing OCC spreading for uplink transmissions on the serving link.

[0211] In some embodiments of method 1100, the configuration information for the configured uplink grant includes an OCC sequence index and an OCC size.

[0212] In some embodiments, method 1100 further includes transmitting DCI to the first UE, the DCI activating the configured uplink grant for use according to the configuration information. In some such embodiments, the configuration information for the configured uplink grant includes the OCC size, and the DCI includes the OCC sequence index. In some other such embodiments, the DCI includes the OCC sequence index and the OCC size.

[0213] In some embodiments of method 1100, the OCC spreading factor includes the network congestion level.

[0214] In some embodiments of method 1100, the OCC spreading factor includes determining that the first UE is capable of performing OCC spreading.

[0215] In some embodiments of method 1100, the OCC spreading factor includes the number of PRBs for the PUSCH.

[0216] In some embodiments of method 1100, the OCC spreading factor includes the number of PUSCH retransmissions for the PUSCH.

[0217] In some embodiments of method 1100, the OCC spreading factor includes the starting time slot of the PUSCH.

[0218] In some embodiments of method 1100, the OCC spreading factor includes a comparison between a first TA report from the first UE and a second TA report from a second UE.

[0219] In some embodiments of method 1100, the OCC spreading factor includes determining that DMRS bundling across multiple time slots is not used for communication with the first UE.

[0220] Figure 12 Method 1200 is illustrated in which a UE in an NTN according to an embodiment herein communicates with a base station via a service link of the NTN. The illustrated method 1200 includes receiving 1202 from the base station DCI indicating an uplink grant for a first PUSCH, where the DCI includes a resource allocation bitmap for the uplink grant. Method 1200 further includes determining 1204, using a resource allocation configuration, that the RBG size for the PUSCH is less than or equal to one PRB. Method 1200 further includes identifying 1206, based on the resource allocation bitmap, one or more RBGs of the RBG size for the PUSCH. Method 1200 further includes transmitting 1208 the PUSCH to the base station using the one or more RBGs.

[0221] In some embodiments, method 1200 further includes transmitting a capability message to the base station, the capability message indicating that the UE is capable of using an RBG size less than or equal to one PRB.

[0222] In some embodiments, method 1200 further includes: determining a BWP size of a BWP for the uplink grant, wherein using the resource allocation configuration to determine that the RBG size for the PUSCH is less than or equal to one PRB includes applying the BWP size of the BWP to the resource allocation configuration.

[0223] In some embodiments of method 1200, the RBG size for the PUSCH is one half of one PRB.

[0224] In some embodiments of method 1200, the RBG size for the PUSCH is one third of one PRB.

[0225] In some embodiments of method 1200, the RBG size for the PUSCH is one quarter of one PRB.

[0226] In some embodiments of method 1200, the RBG size for the PUSCH is one PRB.

[0227] In some embodiments of method 1200, the uplink grant is a configured uplink grant, and method 1200 further includes receiving, from the base station, a configured grant configuration for the configured uplink grant, the configured grant configuration indicating the use of the resource allocation configuration.

[0228] In some embodiments, method 1200 further includes receiving, from the base station, a UE-specific PUSCH configuration for the PUSCH, the UE-specific PUSCH configuration indicating the use of the resource.

[0229] In some embodiments, method 1200 further includes: determining a first number of REs allocated for the PUSCH within each of the one or more RBGs based on the RBG size for the PUSCH that is less than or equal to one PRB, determining a total number of REs allocated for the PUSCH based on the first number of REs allocated for the PUSCH within each of the one or more RBGs, and determining a TBS for the PUSCH based on the total number of REs allocated for the PUSCH. In some such embodiments, the first number of REs allocated for the PUSCH within each of the one or more RBGs is determined according to the following formula: where: N′ REis the first quantity of REs allocated for the PUSCH within each of the one or more RBGs; is the number of subcarriers per PRB in the frequency domain; is the number of symbols for the PUSCH; is the second quantity of REs, where the second quantity of REs is the number of REs per PRB for DM-RS; is the third quantity of REs, where the third quantity of REs is the overhead configured per PRB; and P is the RBG size for the PUSCH, expressed in terms of PRBs, where the RBG size is less than or equal to one PRB. In some other such embodiments, the UE is instructed to use multiple time slots for transport block size calculation, and where the second quantity of REs, which is the total number of REs allocated for the PUSCH, is determined according to the following formula: N RE = N · min(156 · P, N′ RE ) · n subPRB where N RE is the total number of REs allocated for the PUSCH; N is the number of the multiple time slots for the transport block size calculation; P is the RBG size for the PUSCH, expressed in terms of PRBs, where the RBG size is less than or equal to one PRB; N' RE is the first quantity of REs allocated for the PUSCH within each of the one or more RBGs; and n subPRB is the number of sub-PRBs allocated for the UE. In some other such embodiments, the second quantity of REs, which is the total number of REs allocated for the PUSCH, is determined according to the following formula: N RE = min(156 · P, N′ RE ) · n subPRB where N RE is the total number of REs allocated for the PUSCH; P is the RBG size for the PUSCH, expressed in terms of PRBs, where the RBG size is less than or equal to one PRB; N' RE is the first quantity of REs allocated for the PUSCH within each of the one or more RBGs; and n subPRB is the number of sub-PRBs allocated for the UE.

[0230] Figure 13Illustrated is a method 1300 for a base station in NTN according to an embodiment herein to communicate with a UE via a serving link of the NTN. The illustrated method 1300 includes transmitting 1302 to the UE DCI indicating an uplink grant for a first PUSCH, where the DCI includes a resource allocation bitmap for the uplink grant, and the resource allocation bitmap is configured to indicate that one or more resource block groups (RBGs) having an RBG size less than or equal to one physical resource block (PRB) for the PUSCH. The method 1300 further includes receiving 1304 the PUSCH from the UE on the one or more RBGs.

[0231] In some embodiments, the method 1300 further includes receiving a capability message from the UE, the capability message indicating that the UE is capable of using an RBG size less than or equal to one PRB.

[0232] In some embodiments of the method 1300, the RBG size for the PUSCH is one - half of one PRB.

[0233] In some embodiments of the method 1300, the RBG size for the PUSCH is one - third of one PRB.

[0234] In some embodiments of the method 1300, the RBG size for the PUSCH is one - quarter of one PRB.

[0235] In some embodiments of the method 1300, the RBG size for the PUSCH is one PRB.

[0236] In some embodiments of the method 1300, the uplink grant is a configured uplink grant, and the method further includes transmitting to the UE a configured grant configuration for the configured uplink grant, the configured grant configuration indicating the use of the resource allocation configuration.

[0237] In some embodiments, the method 1300 further includes transmitting to the UE a UE - specific PUSCH configuration for the PUSCH, the UE - specific PUSCH configuration indicating the use of the resource allocation configuration.

[0238] Figure 14Illustrated is a method 1400 for a UE in NTN according to an embodiment herein to communicate with a base station via a service link of the NTN. The illustrated method 1400 includes receiving 1402 from the base station a FRIV configured to allocate transmission resources for a PUSCH according to one or more sub - PRBs, where each of the one or more sub - PRBs has a sub - PRB size less than one PRB. The method 1400 further includes identifying 1404 the transmission resources using the FRIV according to the one or more sub - PRBs. The method 1400 further includes transmitting 1406 the PUSCH to the base station using the transmission resources.

[0239] In some embodiments of method 1400, the FRIV corresponds to the formula: where: RIV is the FRIV; is the size of the bandwidth part (BWP) for the PUSCH; is the ratio of the PRB size to the sub - PRB size; L subRBs is the length of the transmission resources in units of sub - PRBs; and subRB start is the position of the first sub - PRB of the transmission resources.

[0240] In some embodiments of method 1400, the FRIV corresponds to the formula:

[0241] where: RIV is the FRIV; is the size of the bandwidth part (BWP) for the PUSCH; is the ratio of the PRB size to the sub - PRB size; L subRBs is the length of the transmission resources in units of sub - PRBs; and subRB start is the position of the first sub - PRB of the transmission resources.

[0242] In some embodiments of method 1400, the sub - PRB size is one - half of one PRB.

[0243] In some embodiments of method 1400, the sub - PRB size is one - third of one PRB.

[0244] In some embodiments of method 1400, the sub - PRB size is one - fourth of one PRB.

[0245] In some embodiments, method 1400 further includes: determining a first number of resource elements (REs) allocated for the PUSCH within each of the one or more sub - physical resource blocks (PRBs) based on a ratio of the PRB size to the sub - PRB size; determining a total number of REs allocated for the PUSCH based on the first number of REs allocated for the PUSCH within each of the one or more sub - PRBs; and determining the transport block size (TBS) of the PUSCH based on the total number of REs allocated for the PUSCH. In one such embodiment, the first number of REs allocated for the PUSCH within each of the one or more sub - PRBs is determined according to the following formula: where: N′ RE is the first number of REs allocated for the PUSCH within each of the one or more sub - PRBs; is the number of sub - carriers per PRB in the frequency domain; is the number of symbols for the PUSCH; is a second number of REs, where the second number of REs is the number of REs per PRB for demodulation reference signals (DM - RS); is a third number of REs, where the third number of REs is the overhead configured per PRB; and is the ratio of the PRB size to the sub - PRB size. In some other such embodiments, the UE is instructed to use multiple time slots for transport block size calculation, and where the second number of REs, which is the total number of REs allocated for the PUSCH, is determined according to the following formula: where N RE is the total number of REs allocated for the PUSCH; N is the number of the multiple time slots used for the transport block size calculation; is the ratio of the PRB size to the sub - PRB size; N' RE is the first number of REs allocated for the PUSCH within each of the one or more resource block groups (RBGs); and n subPRB is the number of sub - PRBs allocated for the UE. In some other such embodiments, the second number of REs, which is the total number of REs allocated for the PUSCH, is determined according to the following formula: where N RE is the total number of REs allocated for the PUSCH; is the ratio of the PRB size to the sub - PRB size; N' RE is the first number of REs allocated for the PUSCH within each of the one or more RBGs; and n subPRB is the number of sub - PRBs allocated for the UE.

[0246] Figure 15 Method 1500 is illustrated for a base station in NTN according to an embodiment herein to communicate with a first UE via a serving link of the NTN. The illustrated method 1500 includes calculating 1502 a FRIV that is configured to allocate transmission resources for a PUSCH in one or more sub-PRBs, where each PRB in the one or more sub-PRBs has a sub-PRB size less than one PRB. Method 1500 further includes transmitting 1504 the FRIV to the UE. Method 1500 further includes receiving 1506 the PUSCH from the UE on the transmission resources.

[0247] In some embodiments of method 1500, the FRIV is calculated according to the following formula: where: RIV is the FRIV; is the size of the BWP for the PUSCH; is the ratio of the PRB size to the sub-PRB size; L subRBs is the length of the transmission resources in sub-PRBs, and subRB start is the position of the first sub-PRB of the transmission resources.

[0248] In some embodiments of method 1500, the FRIV is calculated according to the following formula:

[0249] where: RIV is the FRIV; is the size of the bandwidth part (BWP) for the PUSCH; is the ratio of the PRB size to the sub-PRB size; L subRBs is the length of the transmission resources in sub-PRBs; and subRB start is the position of the first sub-PRB of the transmission resources.

[0250] In some embodiments of method 1500, the sub-PRB size is one half of one PRB.

[0251] In some embodiments of method 1500, the sub-PRB size is one third of one PRB.

[0252] In some embodiments of method 1500, the sub-PRB size is one quarter of one PRB.

[0253] Figure 16 An example architecture of a wireless communication system 1600 according to an embodiment disclosed herein is illustrated. The description provided below is for an exemplary wireless communication system 1600 operating in conjunction with LTE system standards and / or 5G or NR system standards provided in 3GPP technical specifications and other 3GPP documents.

[0254] As shown Figure 16 in FIG. 1600, the wireless communication system 1600 includes UEs 1602 and 1604 (although any number of UEs may be used). In this example, UEs 1602 and 1604 are illustrated as smart phones (e.g., handheld touchscreen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing device configured for wireless communication.

[0255] UEs 1602 and 1604 may be configured to communicatively couple with RAN 1606. In an embodiment, RAN 1606 may be an NG-RAN, an E-UTRAN, etc. UEs 1602 and 1604 utilize connections (or channels) with RAN 1606 (shown as connections 1608 and 1610, respectively), where each connection (or channel) includes a physical communication interface. RAN 1606 may include one or more base stations (such as terrestrial base stations 1612, 1614, satellite base stations 1636, and 1638) and / or other entities enabling connections 1608 and 1610 (e.g., satellite 1642, which may not have base station functionality). One or more satellite gateways 1634 may integrate satellite base stations 1636, 1638, and / or satellite 1642 into RAN 1606 in a manner described in conjunction with Figure 1 the NTN architecture 100 of Figure 2 and

[0256] It will be understood that in Figure 16 an alternative embodiment of

[0257] the NTN architecture 200 (and with appropriate elements). Satellite base stations 1636, 1638, and / or satellite 1642 may alternatively include non-satellite NTN vehicles (e.g., airplanes, UAVs, UASs, airships, balloons, etc.). Additionally, it will be understood that in such alternative embodiments, any satellite gateway 1634 may be a gateway for or corresponding to the applicable NTN vehicle type.

[0258] In some embodiments, UEs 1602 and 1604 may also directly exchange communication data via sidelink interface 1616.

[0259] UE 1604 is shown as being configured to access an access point (shown as AP 1618) via connection 1620. By way of example, connection 1620 may include a local wireless connection, such as a connection compliant with any IEEE 802.11 protocol, where AP 1618 may include a router. In this example, AP 1618 may be connected to another network (e.g., the Internet) without passing through CN 1624.

[0260] In an embodiment, UE 1602 and UE 1604 may be configured to communicate with each other over a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication technologies, such as but not limited to orthogonal frequency division multiple access (OFDMA) communication technology (e.g., for downlink communication) or single-carrier frequency division multiple access (SC-FDMA) communication technology (e.g., for uplink and ProSe or sidelink communication), communicate with terrestrial base stations 1612, terrestrial base stations 1614, satellite base stations 1636, satellite base stations 1638, and / or satellite 1642, although the scope of the embodiment is not limited in this regard. The OFDM signal may include a plurality of orthogonal subcarriers.

[0261] In some embodiments, all or part of terrestrial base stations 1612, terrestrial base stations 1614, satellite base stations 1636, and / or satellite base stations 1638 may be implemented as one or more software entities operating on a server computer as part of a virtual network.

[0262] In addition or in other embodiments, terrestrial base station 1612 or terrestrial base station 1614 may be configured to communicate with each other via interface 1622. In an embodiment where wireless communication system 1600 is an LTE system (e.g., when CN 1624 is an EPC), interface 1622 may be an X2 interface. The X2 interface may be defined between two or more base stations connected to the EPC (e.g., two or more eNBs, etc.) and / or between two eNBs connected to the EPC. It is envisioned that an inter-satellite link (ISL) may carry the X2 interface therebetween in the case of two satellite base stations.

[0263] In an implementation where the wireless communication system 1600 is an NR system (e.g., when CN 1624 is 5GC), the interface 1622 can be an Xn interface. The Xn interface is defined between two or more base stations connected to 5GC (e.g., CN 1624). For example, the Xn interface can be between two or more gNBs connected to 5GC, between a gNB connected to 5GC and an eNB, between two eNBs connected to 5GC, and / or between two or more satellite base stations via an ISL (such as in interface 1640 between satellite base station 1636 and satellite base station 1638).

[0264] RAN 1606 is shown communicatively coupled to CN 1624. CN 1624 can include one or more network elements 1626 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UEs 1602 and 1604) connected to CN 1624 via RAN 1606. The components of CN 1624 can be implemented in one physical device or separate physical devices including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). For example, the components of CN 1624 can be implemented in one or more processors and / or one or more associated memories.

[0265] In an implementation, CN 1624 can be an EPC, and RAN 1606 can be connected to CN 1624 via the S1 interface 1628. In an implementation, the S1 interface 1628 can be divided into two parts: the S1 user plane (S1-U) interface, which carries traffic data between the terrestrial base stations 1612, 1614, satellite base station 1636, or interface 1640 and the serving gateway (S-GW); and the S1-MME interface, which is a signaling interface between the terrestrial base stations 1612, 1614, satellite base station 1636, or interface 1640 and the mobility management entity (MME).

[0266] In an implementation, CN 1624 can be 5GC, and RAN 1606 can be connected to CN 1624 via the NG interface 1628. In an implementation, the NG interface 1628 can be divided into two parts: the NG user plane (NG-U) interface, which carries traffic data between the terrestrial base stations 1612, 1614, satellite base station 1636, or satellite base station 1638 and the user plane function (UPF); and the S1 control plane (NG-C) interface, which is a signaling interface between the terrestrial base stations 1612, 1614, satellite base station 1636, or satellite base station 1638 and the access and mobility management function (AMF).

[0267] Generally speaking, the application server 1630 can be an element that provides an application using Internet Protocol (IP) bearer resources for use with CN 1624 (e.g., packet switched data services). The application server 1630 can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for the UEs 1602 and 1604 via the CN 1624. The application server 1630 can communicate with the CN 1624 through the IP communication interface 1632.

[0268] Figure 17 Illustrated is a system 1700 for performing signaling 1734 between a wireless device 1702 and a RAN device 1718 according to embodiments disclosed herein. The system 1700 can be part of a wireless communication system as described herein. The wireless device 1702 can be, for example, a UE of a wireless communication system. The RAN device 1718 can be, for example, a base station (e.g., an eNB or a gNB) located on an NTN vehicle as a terrestrial base station or as a non-terrestrial base station. In the case where the RAN device 1718 is a terrestrial base station, the RAN device 1718 can communicate with an NTN vehicle that provides a radio access connection directly to the wireless device 1702 via a serving link in the manner described herein.

[0269] The wireless device 1702 can include one or more processors 1704. The processors 1704 can execute instructions to cause various operations of the wireless device 1702 to be performed as described herein. The processors 1704 can include one or more baseband processors implemented using, for example, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0270] The wireless device 1702 can include a memory 1706. The memory 1706 can be a non-transitory computer-readable storage medium that stores instructions 1708 (which can include, for example, instructions executed by the processors 1704). The instructions 1708 can also be referred to as program code or a computer program. The memory 1706 can also store data used by the processors 1704 and results calculated by the processors.

[0271] The wireless device 1702 may include one or more transceivers 1710 that may include RF transmitter and / or receiver circuitry that uses an antenna 1712 of the wireless device 1702 to facilitate transmitted or received signaling (e.g., signaling 1734) between the wireless device 1702 and other devices (e.g., RAN device 1718) according to a corresponding RAT. In some embodiments, the antenna 1712 may include a mobile parabolic antenna, an omnidirectional phased array antenna, or some other antenna suitable for communicating with an NTN vehicle (e.g., as described above in connection with Figure 1 UE 110 and Figure 2 UE 208).

[0272] For a RAN device 1718 that is a terrestrial base station, network device signaling 1734 may occur on a serving link between the wireless device 1702 and the NTN vehicle and on a feeder link between the NTN vehicle and the RAN device 1718 (e.g., as described in connection with Figure 1 ). For a RAN device 1718 that is a base station located on an NTN vehicle, signaling 1734 may occur on a serving link between the wireless device 1702 and the RAN device 1718 (e.g., as described in connection with Figure 2 ).

[0273] The wireless device 1702 may include one or more antennas 1712 (e.g., one, two, four, or more). For embodiments with multiple antennas 1712, the wireless device 1702 may utilize spatial diversity of such multiple antennas 1712 to transmit and / or receive multiple different data streams on the same time-frequency resources. This behavior may be referred to as, for example, multiple-input multiple-output (MIMO) behavior (referring to the multiple antennas used at each of the transmitting and receiving devices to achieve this aspect). MIMO transmissions performed by the wireless device 1702 may be implemented according to precoding (or digital beamforming) applied at the wireless device 1702, which multiplexes data streams across the antennas 1712 based on known or assumed channel characteristics such that each data stream is received with an appropriate signal strength relative to the other streams and at a desired location in the spatial domain (e.g., the location of the receiver associated with that data stream). Certain embodiments may use single-user MIMO (SU-MIMO) methods (where the data streams are all directed to a single receiver) and / or multi-user MIMO (MU-MIMO) methods (where individual data streams may be directed to separate (different) receivers at different locations in the spatial domain).

[0274] In some embodiments with multiple antennas, the wireless device 1702 may implement analog beamforming techniques, whereby the phases of the signals transmitted by the antennas 1712 are relatively adjusted such that the (combined) transmission of the steerable antennas 1712 (which is sometimes referred to as beam steering) is possible.

[0275] The wireless device 1702 may include one or more interfaces 1714. The interfaces 1714 may be used to provide input to or output from the wireless device 1702. For example, the wireless device 1702, as a UE, may include interfaces 1714 such as a microphone, a speaker, a touch screen, buttons, etc., to allow a user of the UE to provide input to and / or output from the UE. Other interfaces of such UEs may consist of transmitters, receivers, and other circuitry (e.g., other than the transceiver 1710 / antenna 1712 already described) that allow communication between the UE and other devices and may operate according to known protocols (e.g., Wi- etc.).

[0276] The wireless device 1702 may include a multiplexing module 1716. The multiplexing module 1716 may be implemented via hardware, software, or a combination thereof. For example, the multiplexing module 1716 may be implemented as a processor, circuitry, and / or instructions 1708 stored in the memory 1706 and executed by the processor 1704. In some examples, the multiplexing module 1716 may be integrated within the processor 1704 and / or the transceiver 1710. For example, the multiplexing module 1716 may be implemented by a combination of software components (e.g., executed by a DSP or a general-purpose processor) and hardware components (e.g., logic gates and circuitry) within the processor 1704 or the transceiver 1710.

[0277] The multiplexing module 1716 may be used for various aspects of the present disclosure, for example, Figure 8 、 Figure 9 、 Figure 12 and / or Figure 14Aspects of one or more of the figures. The multiplexing module 1716 may configure the wireless device 1702 to, for example, receive via a serving link a dynamic grant from the RAN device 1718 that triggers the use of OCC spreading at the wireless device 1702, receive configuration information for a configured grant for the wireless device 1702 using OCC spreading, perform OCC spreading (e.g., of the PUSCH), and / or transmit the result to the RAN device 1718 via the serving link, as discussed herein. The multiplexing module 1716 may additionally / alternatively configure the wireless device 1702 to, for example, receive via a serving link from the RAN device 1718 a grant (e.g., a bitmap) for a type 0 resource allocation that allocates frequency domain resources on a sub-PRB basis and transmit corresponding signaling (e.g., PUSCH) to the RAN device 1718 on the frequency domain resources so allocated on the serving link; and / or receive via a serving link from the RAN device 1718 a grant (e.g., a FRIV) for a type 1 resource allocation that allocates frequency domain resources on a sub-PRB basis and transmit corresponding signaling (e.g., PUSCH) to the RAN device 1718 on the frequency domain resources so allocated on the serving link, as discussed herein.

[0278] The RAN device 1718 may include one or more processors 1720. The processors 1720 may execute instructions to perform the various operations of the RAN device 1718 as described herein. The processor 1704 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0279] The RAN device 1718 may include a memory 1722. The memory 1722 may be a non-transitory computer-readable storage medium storing instructions 1724 (which may include, for example, instructions executed by the processor 1720). The instructions 1724 may also be referred to as program code or a computer program. The memory 1722 may further store data used by the processor 1720 and results computed by the processor.

[0280] The RAN device 1718 may include one or more transceivers 1726 that may include RF transmitter and / or receiver circuitry that uses the antennas 1728 of the RAN device 1718 to facilitate transmitted or received signaling (e.g., signaling 1734) between the RAN device 1718 and other devices (e.g., the wireless device 1702) according to a corresponding RAT.

[0281] The RAN device 1718 may include one or more antennas 1728 (e.g., one, two, four, or more). In embodiments with multiple antennas 1728, the RAN device 1718 may perform MIMO, digital beamforming, analog beamforming, beam control, etc., as described above.

[0282] For the RAN device 1718 that is a terrestrial base station, one or more of the transceiver 1726 and / or the antenna 1728 may alternatively be present on a satellite gateway associated with the base station (or a gateway for another applicable NTN vehicle type) (e.g., as shown for the terrestrial base station 104 and satellite gateway 106 in reference Figure 1 . For the RAN device 1718 that is a base station located on an NTN vehicle, the transceiver 1726 and / or the antenna 1728 may be present on the NTN vehicle, and one or more of these antennas 1728 may be antennas suitable for non-terrestrial communication (such as mobile parabolic antennas, omnidirectional phased array antennas, etc.).

[0283] The RAN device 1718 may include one or more interfaces 1730. The interface 1730 may be used to provide input to the RAN device 1718 or output from the RAN device. For example, the RAN device 1718 that is a base station may include an interface 1730 composed of a transmitter, a receiver, and other circuitry (e.g., in addition to the transceiver 1726 / antenna 1728 already described), which enables the base station to communicate with other equipment in the CN and / or enables the base station to communicate with an external network, computer, database, etc., for the purpose of operating, managing, and maintaining the base station or other equipment operably connected to the base station.

[0284] The RAN device 1718 may include a multiplexing module 1732. The multiplexing module 1732 may be implemented via hardware, software, or a combination thereof. For example, the multiplexing module 1732 may be implemented as a processor, circuitry, and / or instructions 1724 stored in the memory 1722 and executed by the processor 1720. In some examples, the multiplexing module 1732 may be integrated within the processor 1720 and / or the transceiver 1726. For example, the multiplexing module 1732 may be implemented by a combination of software components (e.g., executed by a DSP or a general-purpose processor) and hardware components (e.g., logic gates and circuitry) within the processor 1720 or the transceiver 1726.

[0285] The multiplexing module 1732 may be used for various aspects of the present disclosure, such as Figure 10 , Figure 11 , Figure 13 and / or Figure 15Aspects of one or more of the figures. The multiplexing module 1732 may configure the RAN device 1718 to, for example, transmit, via a serving link, a dynamic grant that triggers the use of OCC spreading at the wireless device 1702, receive configuration information for a grant for the configuration of the wireless device 1702 using OCC spreading, and / or receive corresponding signaling from the wireless device 1702 via the serving link, as discussed herein. The multiplexing module 1716 may additionally / alternatively configure the RAN device 1718 to, for example, transmit, via a serving link, a grant for a type 0 resource allocation (e.g., a bitmap) to the wireless device 1702, which allocates frequency domain resources on a sub-PRB basis, and receive corresponding signaling (e.g., PUSCH) from the wireless device 1702 on the frequency domain resources so allocated on the serving link; and / or transmit, via a serving link, a grant for a type 1 resource allocation (e.g., FRIV) to the wireless device 1702, which allocates frequency domain resources on a sub-PRB basis, and receive corresponding signaling (e.g., PUSCH) from the wireless device 1702 on the frequency domain resources so allocated on the serving link, as discussed herein.

[0286] Implementations contemplated herein include an apparatus that includes means for performing one or more elements of any one or more of method 800, method 900, method 1200, and / or method 1400. The apparatus may be, for example, an apparatus of a UE (such as the wireless device 1702 that is a UE, as described herein).

[0287] Implementations contemplated herein include one or more non-transitory computer-readable media that include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of any one or more of method 800, method 900, method 1200, and / or method 1400. The non-transitory computer-readable media may be, for example, a memory of a UE (such as the memory 1706 of the wireless device 1702 that is a UE, as described herein).

[0288] Implementations contemplated herein include an apparatus that includes logic components, modules, or circuitry for performing one or more elements of any one or more of method 800, method 900, method 1200, and / or method 1400. The apparatus may be, for example, an apparatus of a UE (such as the wireless device 1702 that is a UE, as described herein).

[0289] The embodiments contemplated herein include an apparatus that includes: one or more processors; and one or more computer-readable media that include instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of any one or more of Method 800, Method 900, Method 1200, and / or Method 1400. The apparatus can be, for example, an apparatus of a UE (such as the wireless device 1702 that is a UE, as described herein).

[0290] The embodiments contemplated herein include a signal that is described in or related to one or more elements of any one or more of Method 800, Method 900, Method 1200, and / or Method 1400.

[0291] The embodiments contemplated herein include a computer program or computer program product that includes instructions that, when executed by a processor, cause the processor to implement one or more elements of any one or more of Method 800, Method 900, Method 1200, and / or Method 1400. The processor can be a processor of a UE (such as the processor 1704 of the wireless device 1702 that is a UE, as described herein). These instructions can be located, for example, in the processor and / or in the memory of the UE (such as the memory 1706 of the wireless device 1702 that is a UE, as described herein).

[0292] The embodiments contemplated herein include an apparatus that includes means for performing one or more elements of any one or more of Method 1000, Method 1100, Method 1300, and / or Method 1500. The apparatus can be, for example, an apparatus of a base station (such as the RAN device 1718 that is a base station, as described herein).

[0293] The embodiments contemplated herein include one or more non-transitory computer-readable media that include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of any one or more of Method 1000, Method 1100, Method 1300, and / or Method 1500. This non-transitory computer-readable media can be, for example, the memory of a base station (such as the memory 1722 of the RAN device 1718 that is a base station, as described herein).

[0294] Implementations contemplated herein include an apparatus that includes logic components, modules, or circuitry for performing one or more elements of any one or more of Method 1000, Method 1100, Method 1300, and / or Method 1500. The apparatus can be, for example, an apparatus of a base station (such as RAN device 1718 as a base station, as described herein).

[0295] Implementations contemplated herein include an apparatus that includes: one or more processors; and one or more computer-readable media that include instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of any one or more of Method 1000, Method 1100, Method 1300, and / or Method 1500. The apparatus can be, for example, an apparatus of a base station (such as RAN device 1718 as a base station, as described herein).

[0296] Implementations contemplated herein include a signal that is described in or related to one or more elements of any one or more of Method 1000, Method 1100, Method 1300, and / or Method 1500.

[0297] Implementations contemplated herein include a computer program or computer program product that includes instructions, where execution of the program by a processing element causes the processing element to implement one or more elements of any one or more of Method 1000, Method 1100, Method 1300, and / or Method 1500. The processor can be a processor of a base station (such as processor 1720 of RAN device 1718 as a base station, as described herein). The instructions can be, for example, located in the processor and / or on a memory of the base station (such as memory 1722 of RAN device 1718 as a base station, as described herein).

[0298] For one or more implementations, at least one component among the components stated in one or more of the foregoing figures can be configured to perform one or more operations, techniques, processes, and / or methods as described herein. For example, a baseband processor as described herein in connection with one or more of the foregoing figures can be configured to operate according to one or more of the examples stated herein. As another example, circuitry associated with a UE, a base station, a network element, etc., as described above in connection with one or more of the foregoing figures can be configured to operate according to one or more of the examples stated herein.

[0299] Unless otherwise expressly stated, any one of the above-described embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. Modifications and variations are possible in light of the above teachings, or may be acquired from practice of various embodiments.

[0300] Embodiments and specific implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system. The computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components that include specific logic components for performing the operations; or may include a combination of hardware, software, and / or firmware.

[0301] It should be recognized that the systems described herein include a description of specific embodiments. These embodiments may be combined into a single system, partially combined into other systems, divided into multiple systems, or otherwise partitioned or combined. In addition, it is contemplated that the parameters, properties, aspects, etc. of one embodiment may be used in another embodiment. For clarity, these parameters, properties, aspects, etc. are described in only one or more embodiments, and it should be recognized that, unless expressly stated herein, these parameters, properties, aspects, etc. may be combined with or substituted for the parameters, properties, aspects, etc. of another embodiment.

[0302] It is well known that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of inadvertent or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0303] Although the foregoing has been described in considerable detail for purposes of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways of implementing both the processes and apparatus described herein. Accordingly, the embodiments of the invention should be regarded as illustrative rather than restrictive, and the specification is not limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1. A method for a user equipment (UE) in a non-terrestrial network (NTN), wherein the UE communicates with a base station via a service link of the NTN, the method comprising: receiving downlink control information (DCI) from the base station indicating a dynamic uplink grant for a first physical uplink shared channel (PUSCH), wherein the DCI includes an orthogonal cover code (OCC) sequence index; using the OCC sequence index, identifying a first OCC sequence for the first PUSCH from an OCC sequence set having an OCC size corresponding to the OCC sequence index; spreading first data for the first PUSCH into the first PUSCH using the first OCC sequence; as well as The first PUSCH is transmitted to the base station over the serving link according to the dynamic uplink grant.

2. The method of claim 1, further comprising transmitting a capability message to the base station, the capability message indicating that the UE is capable of performing OCC spreading for uplink transmissions on the serving link. 3 . The method of claim 1 , wherein the DCI further comprises an indication of the OCC size corresponding to the first OCC sequence. 4 . The method of claim 1 , further comprising receiving radio resource configuration (RRC) signaling from the base station indicating the OCC size corresponding to the first OCC sequence index.

5. The method of claim 1 , wherein the dynamic uplink grant is also used for a second PUSCH, and the method further comprises: spreading second data for the second PUSCH into the second PUSCH using the first OCC sequence; as well as The second PUSCH is transmitted to the base station through the serving link.

6. The method of claim 1, wherein the dynamic uplink grant is also used for a second PUSCH, and the method further comprises: identifying a second OCC sequence for the second PUSCH from the OCC sequence set having the OCC size; spreading second data for the second PUSCH into the second PUSCH using the second OCC sequence; as well as The second PUSCH is transmitted to the base station through the serving link. 7 . The method of claim 6 , wherein the second OCC sequence is a next OCC sequence after the first OCC sequence in the concentration of the OCC sequences having the OCC size.

8. The method of claim 6, wherein the second OCC sequence is identified from the set of OCC sequences having the OCC size by applying an offset relative to the first OCC sequence in the set of OCC sequences having the OCC size.

9. The method according to claim 1, wherein the UE is configured for PUSCH retransmission, and the method further comprises: Spreading the first data to a retransmission of the first PUSCH using the first OCC sequence; as well as The retransmission of the first PUSCH is transmitted to the base station over the serving link.

10. The method according to claim 1, wherein the UE is configured for PUSCH retransmission, and the method further comprises: identifying a second OCC sequence for retransmission of the first PUSCH from the OCC sequence set having the OCC size; spreading the first data to the retransmission of the first PUSCH using the second OCC sequence; as well as The retransmission of the first PUSCH is transmitted to the base station over the serving link. 11 . The method of claim 10 , wherein the second OCC sequence is a next OCC sequence after the first OCC sequence in the OCC sequence set having the OCC size.

12. The method of claim 10, wherein the second OCC sequence is identified from the set of OCC sequences having the OCC size by applying an offset relative to the first OCC sequence in the set of OCC sequences having the OCC size.

13. The method of claim 1, wherein: A plurality of physical resource blocks (PRBs) are used for the first PUSCH, and The first data for the first PUSCH is spread into a first PRB of the plurality of PRBs using the first OCC sequence; as well as The method also includes spreading second data for the first PUSCH into a second PRB of the plurality of PRBs using the first OCC sequence.

14. The method of claim 1, wherein: A plurality of physical resource blocks (PRBs) are used for the first PUSCH, and The first data for the first PUSCH is spread into a first PRB of the plurality of PRBs using the first OCC sequence; as well as The method further comprises: identifying, from the set of OCC sequences having the OCC size, a second OCC sequence for a second PRB in the plurality of PRBs; as well as Second data for the first PUSCH is spread into the second PRB using the second OCC sequence. 15 . The method of claim 14 , wherein the second OCC sequence is a next OCC sequence after the first OCC sequence in the OCC sequence set having the OCC size.

16. The method of claim 14, wherein the second OCC sequence is identified from the set of OCC sequences having the OCC size by applying an offset relative to the first OCC sequence in the set of OCC sequences having the OCC size.

17. The method of claim 1, wherein: The UE is configured to use frequency hopping for the first PUSCH, and The first data for the first PUSCH is spread into a non-hopping frequency of the hopping frequency using the first OCC sequence; as well as The method further comprises: Spreading second data for the first PUSCH into a first hop of the frequency hopping using the first OCC sequence; as well as Third data for the first PUSCH is spread into a second hop of the frequency hopping using the first OCC sequence.

18. The method of claim 1, wherein: The UE is configured to use frequency hopping for the first PUSCH, and The first data for the first PUSCH is spread into a non-hopping frequency of the hopping frequency using the first OCC sequence; as well as The method further comprises: identifying a second OCC sequence for a first hop of the frequency hopping from the set of OCC sequences having the OCC size; spreading second data for the first PUSCH into the first hop using the second OCC sequence; identifying a third OCC sequence for a second hop of the frequency hopping from the set of OCC sequences having the OCC size; Third data for the first PUSCH is spread into the second hop using the third OCC sequence.

19. The method of claim 18, wherein: The second OCC sequence is a first next OCC sequence in the OCC sequence set having the OCC size after the first OCC sequence; and The third OCC sequence is a second next OCC sequence after the second OCC sequence among the OCC sequences having the OCC size.

20. The method of claim 18, wherein: the second OCC sequence is identified from the set of OCC sequences having the OCC size by applying a first offset relative to the first OCC sequence in the set of OCC sequences having the OCC size; as well as The third OCC sequence is identified from the set of OCC sequences having the OCC size by applying a second offset relative to the first OCC sequence in the set of OCC sequences having the OCC size.

21. A method for a user equipment (UE) in a non-terrestrial network (NTN), the UE communicating with a base station via a service link of the NTN, the method comprising: receiving radio resource control (RRC) signaling from the base station, the RRC signaling comprising configuration information for a configured uplink grant for a first physical uplink shared channel (PUSCH); using an orthogonal cover code (OCC) sequence index, identifying a first OCC sequence for the first PUSCH from an OCC sequence set having an OCC size corresponding to the OCC sequence index; spreading first data for the first PUSCH into the first PUSCH using the first OCC sequence; as well as The first PUSCH is transmitted to the base station through the serving link according to the configured uplink grant.

22. The method of claim 21, further comprising transmitting a capability message to the base station, the capability message indicating that the UE is capable of performing OCC spreading for uplink transmissions on the serving link.

23. The method of claim 21, wherein the configuration information for the configured uplink grant comprises the OCC sequence index and the OCC size.

24. The method of claim 21, further comprising receiving downlink control information (DCI) from the base station, the downlink control information (DCI) activating the configured uplink grant for use according to the configuration information.

25. The method of claim 24, wherein the configuration information for the configured uplink grant comprises the OCC size, and the DCI comprises the OCC sequence index.

26. The method of claim 24, wherein the DCI comprises the OCC sequence index and the OCC size.

27. The method of claim 21, wherein the UE is configured for PUSCH retransmission, and the method further comprises: Spreading the first data to a retransmission of the first PUSCH using the first OCC sequence; as well as The retransmission of the first PUSCH is transmitted to the base station over the serving link.

28. The method of claim 21, wherein the UE is configured for PUSCH retransmission, and the method further comprises: identifying a second OCC sequence for retransmission of the first PUSCH from the OCC sequence set having the OCC size; spreading the first data to the retransmission of the first PUSCH using the second OCC sequence; as well as The retransmission of the first PUSCH is transmitted to the base station over the serving link.

29. The method of claim 28, wherein the second OCC sequence is a next OCC sequence after the first OCC sequence in the set of OCC sequences having the OCC size.

30. The method of claim 28, wherein the second OCC sequence is identified from the set of OCC sequences having the OCC size by applying an offset relative to the first OCC sequence in the set of OCC sequences having the OCC size.

31. The method of claim 21, wherein: A plurality of physical resource blocks (PRBs) are used for the first PUSCH, and The first data for the first PUSCH is spread into a first PRB of the plurality of PRBs using the first OCC sequence; as well as The method also includes spreading second data for the first PUSCH into a second PRB of the plurality of PRBs using the first OCC sequence.

32. The method of claim 21, wherein: A plurality of physical resource blocks (PRBs) are used for the first PUSCH, and The first data for the first PUSCH is spread into a first PRB of the plurality of PRBs using the first OCC sequence; as well as The method further comprises: identifying, from the set of OCC sequences having the OCC size, a second OCC sequence for a second PRB in the plurality of PRBs; as well as Second data for the first PUSCH is spread into the second PRB using the second OCC sequence.

33. The method of claim 32, wherein the second OCC sequence is a next OCC sequence after the first OCC sequence in the set of OCC sequences having the OCC size.

34. The method of claim 32, wherein the second OCC sequence is identified from the set of OCC sequences having the OCC size by applying an offset relative to the first OCC sequence in the set of OCC sequences having the OCC size.

35. The method of claim 21, wherein: The UE is configured to use frequency hopping for the first PUSCH, and The first data for the first PUSCH is spread into a non-hopping frequency of the hopping frequency using the first OCC sequence; as well as The method further comprises: Spreading second data for the first PUSCH into a first hop of the frequency hopping using the first OCC sequence; as well as Third data for the first PUSCH is spread into a second hop of the frequency hopping using the first OCC sequence.

36. The method of claim 21, wherein: The UE is configured to use frequency hopping for the first PUSCH, and The first data for the first PUSCH is spread into a non-hopping frequency of the hopping frequency using the first OCC sequence; as well as The method further comprises: identifying a second OCC sequence for a first hop of the frequency hopping from the set of OCC sequences having the OCC size; spreading second data for the first PUSCH into the first hop using the second OCC sequence; identifying a third OCC sequence for a second hop of the frequency hopping from the set of OCC sequences having the OCC size; Third data for the first PUSCH is spread into the second hop using the third OCC sequence.

37. The method of claim 36, wherein: The second OCC sequence is a first next OCC sequence in the OCC sequence set having the OCC size after the first OCC sequence; and The third OCC sequence is a second next OCC sequence after the second OCC sequence among the OCC sequences having the OCC size.

38. The method of claim 36, wherein: the second OCC sequence is identified from the set of OCC sequences having the OCC size by applying a first offset relative to the first OCC sequence in the set of OCC sequences having the OCC size; as well as The third OCC sequence is identified from the set of OCC sequences having the OCC size by applying a second offset relative to the first OCC sequence in the set of OCC sequences having the OCC size.

39. A method of a base station in a non-terrestrial network (NTN), the base station communicating with a first user equipment (UE) via a serving link of the NTN, the method comprising: Determining, based on an orthogonal cover code (OCC) spreading utilization factor, that the first UE will use an OCC sequence to spread data of a physical uplink shared channel (PUSCH); transmitting downlink control information (DCI) indicating a dynamic uplink grant for the PUSCH to the first UE, wherein the DCI includes an OCC sequence index identifying the OCC sequence; as well as Corresponding to the dynamic uplink grant, the PUSCH having the data spread by the OCC sequence is received from the first UE.

40. The method of claim 39, further comprising receiving a capability message from the first UE, the capability message indicating that the first UE is capable of performing OCC spreading for uplink transmissions on the serving link.

41. The method of claim 39, wherein the DCI further comprises an indication of an OCC size corresponding to the first OCC sequence.

42. The method of claim 39, further comprising transmitting, to the first UE, radio resource configuration (RRC) signaling indicating the OCC size corresponding to the first OCC sequence index.

43. The method of claim 39, wherein the OCC spreading utilization factor comprises a network congestion level.

44. The method of claim 39, wherein the OCC spreading utilization factor comprises determining that the first UE is capable of performing OCC spreading.

45. The method of claim 39, wherein the OCC spreading utilization factor comprises a number of physical resource blocks (PRBs) to be used for the PUSCH.

46. ​​The method of claim 39, wherein the OCC spreading utilization factor comprises a number of PUSCH retransmissions to be used for the PUSCH.

47. The method of claim 39, wherein the OCC spreading utilization factor comprises a starting time slot of the PUSCH.

48. The method of claim 39, wherein the OCC spreading utilization factor comprises a comparison between a first timing advance (TA) report from the first UE and a second TA report from a second UE.

49. The method of claim 39, wherein the OCC spreading utilization factor comprises determining that demodulation reference signal (DMRS) bundling across multiple time slots is not used for communication with the first UE.

50. A method of a base station in a non-terrestrial network (NTN), the base station communicating with a first user equipment (UE) via a serving link of the NTN, the method comprising: Determining, based on an orthogonal cover code (OCC) spreading utilization factor, that the first UE will use an OCC sequence to spread data of a physical uplink shared channel (PUSCH); transmitting radio resource control (RRC) signaling to the first UE, the RRC signaling comprising configuration information for a configured uplink grant for the first PUSCH; as well as Corresponding to the configured uplink grant, the PUSCH having the data spread by the OCC sequence is received from the first UE.

51. The method of claim 50, further comprising receiving a capability message from the first UE, the capability message indicating that the first UE is capable of performing OCC spreading for uplink transmissions on the serving link.

52. The method of claim 50, wherein the configuration information for the configured uplink grant comprises an OCC sequence index and an OCC size.

53. The method of claim 50, further comprising transmitting downlink control information (DCI) to the first UE, the downlink control information (DCI) activating the configured uplink grant for use according to the configuration information.

54. The method of claim 53, wherein the configuration information for the configured uplink grant comprises an OCC size, and the DCI comprises an OCC sequence index.

55. The method of claim 53, wherein the DCI comprises an OCC sequence index and an OCC size.

56. The method of claim 50, wherein the OCC spreading utilization factor comprises a network congestion level.

57. The method of claim 50, wherein the OCC spreading utilization factor comprises determining that the first UE is capable of performing OCC spreading.

58. The method of claim 50, wherein the OCC spreading utilization factor comprises a number of physical resource blocks (PRBs) to be used for the PUSCH.

59. The method of claim 50, wherein the OCC spreading utilization factor comprises a number of PUSCH retransmissions to be used for the PUSCH.

60. The method of claim 50, wherein the OCC spreading factor comprises a starting time slot of the PUSCH.

61. The method of claim 50, wherein the OCC spreading utilization factor comprises a comparison between a first timing advance (TA) report from the first UE and a second TA report from a second UE.

62. The method of claim 50, wherein the OCC spreading utilization factor comprises determining that demodulation reference signal (DMRS) bundling across multiple time slots is not used for communication with the first UE.

63. An apparatus comprising means for performing the method of any one of claims 1 to 62.

64. A computer-readable medium comprising instructions which, when executed by one or more processors of an electronic device, cause the electronic device to perform the method of any one of claims 1 to 62.

65. An apparatus comprising logic components, modules or circuit systems for performing the method of any one of claims 1 to claim 62.

Images