Application of time gap offset to non-terrestrial networks

Abstract

To provide an apparatus and method for determining a slot for an uplink reception for a non-terrestrial network link between a base station and user equipment.SOLUTION: A wireless communication system comprises a base station that determines a timing advance based on at least a random access preamble reception and determines an uplink offset based on the timing advance. The base station may further determine a candidate slot for an uplink reception based on at least the offset. In addition, the base station may determine if the candidate slot is available for the uplink reception. The base station may use the candidate slot for the uplink reception when the candidate uplink slot is available and may use the next available slot for the uplink reception when the candidate uplink slot is not available.SELECTED DRAWING: Figure 8A

Description

[Technical Field]

[0001] This invention relates in general to wireless technology, and more specifically to the application of timing improvement to links in non-terrestrial networks. [Background of the Invention]

[0002] In 5G New Radio (NR), several different timing relationships exist that are defined for terrestrial networks (TN). For example, K0 is the time gap between Downlink Control Information (DCI) and the Physical Downlink Shared Channel (PDSCH). In addition, K1 is the time gap between PDSCH reception and Physical Uplink Control Channel (PUCCH) transmission, and K2 is the time gap between DCI and the Physical Uplink Shared Channel (PUSCH). In NR Release 16, for non-terrestrial networks (NTN), these timing relationships may change due to the greater communication distance involved in NTN, as radio links are traversed from terrestrial-based User Equipment (UE) to satellite and back to terrestrial-based networks (and vice versa). The challenge is to determine how these timing relationships may change for NTN. [Overview of the Initiative]

[0003] A user equipment (UE) is described that includes a processor configured to perform an operation to determine an uplink (UL) slot. In an exemplary embodiment, the UE receives a scaling factor from a base station via a first radio resource control (RRC) signal. The UE may further determine an offset via a second RRC signal. In addition, the UE may receive downlink control information (DCI) from the base station, including an instruction for the initial time gap. Furthermore, the UE may calculate a new time gap by applying the scaling factor to at least the initial time gap and determine an uplink transmission slot based on at least the new time gap and the offset. The scaling factor depends on at least one of the cell size, beam size, and user equipment capability. For a high-capacity UE, the scaling factor is 1, and for a low-capacity UE, the scaling factor is greater than 1. In addition, the scaling factor is in the range of 1 to 16.

[0004] Furthermore, the initial time gap is a set of time gaps including K1 and K2, where K1 represents the time gap between physical downlink shared channel (PDSCH) reception and physical uplink control channel (PUCCH) transmission, and K2 represents the time gap between physical downlink control channel (PDCCH) reception and physical uplink shared channel (PUSCH) transmission. Furthermore, different scaling factors may exist for different K values ​​or different UEs. In addition, the same scaling factor may exist for different K values. The initial time gap includes K4, which represents the time gap between physical sidelink feedback channel (PSFCH) reception and physical uplink control channel (PUCCH) transmission.

[0005] In another embodiment, a UE is described comprising a processor configured to perform an operation to determine an uplink (UL) slot using a scaling factor set. In one embodiment, the UE receives a scaling factor set from a base station via a first radio resource control (RRC) signal. The UE may further determine an offset via a second RRC signal. In addition, the UE may receive downlink control information (DCI) from the base station, including an instruction for an initial time gap and an instruction for a selected scaling factor, which is one of the scaling factor sets. The UE may further calculate a new time gap by applying the selected scaling factor to at least the initial time gap and determine an uplink transmission slot based on at least the new time gap and the offset. The scaling factor may depend on at least one of the cell size, beam size, and user equipment capability.

[0006] Furthermore, the initial time gap is a set of time gaps including K1 and K2, where K1 represents the time gap between physical downlink shared channel (PDSCH) reception and physical uplink control channel (PUCCH) transmission, and K2 represents the time gap between physical downlink control channel (PDCCH) reception and physical uplink shared channel (PUSCH) transmission. Furthermore, different scaling factors may exist for different K values ​​or different UEs. In addition, the same scaling factor may exist for different K values. The initial time gap includes K4, which represents the time gap between physical sidelink feedback channel (PSFCH) reception and physical uplink control channel (PUCCH) transmission.

[0007] In another embodiment, a baseband processor configured to perform an operation to determine an uplink (UL) slot is described. In an exemplary embodiment, the baseband processor receives a scaling factor from a base station via a first radio resource control (RRC) signal. The baseband processor may further determine an offset via a second RRC signal. In addition, the baseband processor may receive downlink control information (DCI) from the base station, including an instruction for the initial time gap. Furthermore, the baseband processor may calculate a new time gap by applying the scaling factor to at least the initial time gap and determine an uplink transmission slot based on at least the new time gap and offset.

[0008] In another embodiment, a baseband processor configured to perform an operation to determine an uplink (UL) slot using a scaling factor set is described. In one embodiment, the baseband processor receives a scaling factor set from a base station via a first radio resource control (RRC) signal. The baseband processor may further determine an offset via a second RRC signal. In addition, the baseband processor may receive downlink control information (DCI) from the base station, which includes an instruction for an initial time gap and an instruction for a selected scaling factor, which is one of the scaling factor sets. The baseband processor may further calculate a new time gap by applying the selected scaling factor to at least the initial time gap and determine an uplink transmission slot based on at least the new time gap and the offset.

[0009] A base station method and apparatus is described, comprising a processor configured to perform an operation to determine a slot for uplink reception for a non-terrestrial network link between the base station and user equipment. In an exemplary embodiment, the base station determines a timing advance based on at least a random access preamble reception and determines an uplink offset based on the timing advance. The base station may further determine candidate slots for uplink reception based on at least the offset. In addition, the base station may determine whether a candidate slot is available for uplink reception. When a candidate uplink slot is available, the base station may use the candidate slot for uplink reception; when a candidate uplink slot is not available, the base station may use the next available slot for uplink reception.

[0010] In addition, uplink reception includes a physical uplink shared channel (PUSCH), random access responses (RAR) scheduled by PUSCH, a physical uplink control channel (PUCCH), or aperiodic SRS. The base station may further determine whether a candidate slot is an uplink slot, a downlink slot, a hybrid slot, or a flexible slot, based at least on the time-division duplex (TDD) configuration of the candidate slot format. If the candidate slot is one of the uplink slots or hybrid slots and the uplink reception corresponds to an uplink symbol in a hybrid slot, the candidate slot is available. If the candidate slot is one of the downlink slots, a hybrid slot with an uplink reception that does not correspond to an uplink symbol in a hybrid slot, or a flexible slot, the candidate slot is unavailable.

[0011] Furthermore, the uplink offset is a measure of the delay of a non-terrestrial network link. The base station may further calculate the uplink offset based on at least the timing advance of one or more satellite links in the non-terrestrial network. In addition, the uplink offset is set to be equal to the sum of the service link timing advance and the feeder link timing advance divided by the slot duration. The base station may further calculate the medium access control (MAC) control element (CE) action timing using at least the uplink offset. The base station may further calculate the time gap between the last physical sidelink feedback channel (PSFCH) reception and the physical uplink control channel (PUCCH) transmission using the sidelink offset, and the sidelink offset may have a different value from the uplink offset. The base station may further calculate the time-domain offset for a Type 1 configured authorization configuration using at least the uplink offset.

[0012] In further embodiments, a user device (UE) is described comprising a processor configured to perform an operation to determine a slot for a channel status information (CSI) reference resource. In one embodiment, the UE receives timing advance information from a base station. The UE may further determine an offset based on the timing advance information. The UE further determines candidate slots for a channel status information (CSI) reference resource based on at least the offset. In addition, the UE may determine whether a candidate slot is available for a CSI reference resource. Furthermore, if a candidate slot is available, the UE may use the candidate slot for the CSI reference resource, and if the candidate slot is not available, it may use another slot for the CSI reference resource. In addition, another available CSI reference resource may be the slot before or after the candidate slot.

[0013] The UE can further determine whether a candidate slot is an uplink slot, a downlink slot, a hybrid slot, or a flexible slot, based at least on the time-division duplex (TDD) configuration of the candidate slot format. If a candidate slot is an uplink slot, a downlink slot, a hybrid slot, or a flexible slot, based at least on the time-division duplex (TDD) configuration of the candidate slot format, the candidate slot is available. If a candidate slot is a downlink slot, or one of the hybrid slots where the downlink receive corresponds to a downlink symbol within a hybrid slot, the candidate slot is available. If a candidate slot is an uplink slot, a hybrid slot where the downlink receive does not correspond to a downlink symbol within a hybrid slot, or one of the flexible slots, the candidate slot is unavailable.

[0014] In another embodiment, a baseband processor is described that determines a slot for a channel status information (CSI) reference resource. In one embodiment, the baseband processor receives timing advance information from a base station. The baseband processor may further determine an offset based on the timing advance information. The baseband processor further determines candidate slots for the CSI reference resource based on at least the offset. In addition, the baseband processor may determine whether a candidate slot is available for the CSI reference resource. Furthermore, if a candidate slot is available, the baseband processor may use the candidate slot for the CSI reference resource, and if the candidate slot is not available, it may use another slot for the CSI reference resource. In addition, another available CSI reference resource may be the slot before or after the candidate slot. In addition, the offset is a measure of the delay of a non-terrestrial network link.

[0015] In another embodiment, a non-temporary machine-readable medium is described having executable instructions that, when executed by one or more processing units, perform a method for determining a slot for uplink reception for a non-terrestrial network link between a base station and user equipment. In one embodiment, the method determines a timing advance based on at least a random access preamble reception and determines an uplink offset based on the timing advance. The method may further determine candidate slots for uplink reception based on at least the offset. In addition, the method may determine whether a candidate slot is available for uplink reception. If a candidate uplink slot is available, the method may use the candidate slot for uplink reception; if a candidate uplink slot is not available, the method may use the next available slot for uplink reception.

[0016] In a further embodiment, a non-transient machine-readable medium is described having executable instructions that, when executed by one or more processing units, perform a method for determining a slot for a channel status information (CSI) reference resource. In one embodiment, the method receives timing advance information from a base station. The method may further determine an offset based on the timing advance information. The method further determines candidate slots for the CSI reference resource based on at least the offset. In addition, the method may determine whether a candidate slot is available for the CSI reference resource. Furthermore, if a candidate slot is available, the method may use the candidate slot for the CSI reference resource, and if a candidate slot is not available, another slot may be used for the CSI reference resource.

[0017] Other methods and apparatus will also be described.

[0018] This disclosure is provided as an example only and is not limited to what is shown in the accompanying drawings, where similar reference numerals indicate similar elements. [Brief explanation of the drawing]

[0019] [Figure 1] This figure shows an exemplary wireless communication system according to several embodiments. [Figure 2A] This figure shows a base station (BS) that communicates with user equipment (UE) devices via a non-terrestrial network (NTN), according to several embodiments. [Figure 2B] This figure shows a base station (BS) that communicates with user equipment (UE) devices via a non-terrestrial network (NTN), according to several embodiments. [Figure 3] This is an exemplary block diagram of a UE according to several embodiments. [Figure 4] This is an exemplary block diagram of BS according to several embodiments. [Figure 5] This is an illustrative block diagram of a cellular communication circuit according to several embodiments. [Figure 6] This diagram illustrates several embodiments of the receiving and transmitting timing. [Figure 7] This is a diagram illustrating several embodiments of the NTN timing relationship. [Figure 8A] This is a flowchart of several embodiments of a process that determines Koffset and uses Koffset to determine different timings. [Figure 8B] This is a flowchart of several embodiments of a process that determines Koffset and uses Koffset to determine different timings. [Figure 9A] This is a flowchart of several embodiments of a process for extending one or more time gaps between downlink (DL) and uplink (UL). [Figure 9B]This is a flowchart of several embodiments of a process for extending one or more time gaps between downlink (DL) and uplink (UL). [Figure 9C] This is a flowchart of several embodiments of a process for extending one or more time gaps between downlink (DL) and uplink (UL). [Figure 9D] This is a flowchart of several embodiments of a process for extending one or more time gaps between downlink (DL) and uplink (UL). [Figure 10] This is an illustrative block diagram of the timing relationship of side links in NTN, according to several embodiments. [Figure 11A] This is an illustrative block diagram of timing relationships for a Type 1 configured authorization configuration at NTN. [Figure 11B] This is an illustrative block diagram of timing relationships for a Type 1 configured authorization configuration at NTN. [Figure 12] This is a flowchart of several embodiments of the process for determining and applying scaling to K4. [Modes for carrying out the invention]

[0020] A method and apparatus for a device that extends the time between downlink and uplink transmissions for a non-terrestrial network link between a base station and user equipment is described. The following description includes numerous specific details to provide a complete description of embodiments of the invention. However, it will be apparent to those skilled in the art that embodiments of the invention can be practiced without these specific details. In other examples, well-known components, structures, and techniques are not shown in detail so as not to hinder the understanding of this description.

[0021] Any reference in this specification to “several embodiments” or “embodiments” means that certain mechanisms, structures, or characteristics described in relation to those embodiments may be included in at least one embodiment of the present invention. The phrase “in some embodiments” appearing in various parts of this specification does not necessarily refer to the same embodiment in all instances.

[0022] In the following descriptions and claims, the terms “joined” and “connected” may be used together with their derivatives. It should be understood that these terms are not intended to be synonymous with one another. “Joined” is used to indicate that two or more elements, which may or may not be in direct physical or electrical contact with each other, work together or interact with each other. “Connected” is used to indicate the establishment of communication between two or more elements that are joined together.

[0023] The processes shown in the following diagrams are executed by processing logic, which may include hardware (e.g., circuitry, dedicated logic), software (such as that running on a general-purpose computer system or dedicated machine), or a combination of both. These processes are described below in terms of several sequential operations, but it should be understood that some of the operations described can be executed in a different order. Furthermore, some operations can be executed in parallel rather than sequentially.

[0024] The terms "server," "client," and "device" are intended to refer to a data processing system in general, rather than to a specific form factor for a server, client, and / or device.

[0025] Methods and apparatus for devices that extend the time between downlink and uplink transmissions for a non-terrestrial network link between a base station and user equipment are described. In some embodiments, a non-terrestrial network (NTN) is a type of wireless communication system that utilizes a satellite system as part of a wireless communication system between user equipment (UE) and a base station (BS). For timing in an NTN system, the timing relationship differs due to the longer delays involved when communicating data over a satellite-based system. In some embodiments, and in NR Release 16 NTN study, the timing relationship is offset K offset This is achieved by introducing, where the PUSCH timing is,

[0026]

number

[0027] In some embodiments, the time offset K offset is introduced for NTN and added on top of the existing timings of UE transmission types (e.g., DCI-scheduled PUSCH, RAR-scheduled PUSCH, PUCCH, MAC CE action timing, aperiodic SRS, and CRI-RS reference resources). For example, and in some embodiments, the time offset K offset is calculated based on the sum of the service link full TA and the feeder link TA of the transparent satellite. As another example, and in some embodiments,

[0028]

Number

[0029] In some embodiments, the existing K1 value may be in the range of 0 to 15 slots, and the existing K2 value may be in the range of 0 to 32 slots. For example, and in some embodiments, NTN may have a large cell size and / or a large differential TA value. In this example, an inaccurate differential TA value may be due to the capabilities of the UE. In some embodiments, a scaling factor may be applied to the K1 and K2 values, which are single scaling factor values ​​for each UE, and different scaling factors may exist for K1 and K2. In addition, the selected scaling factor may depend on the capabilities of the UE. For example, and in some embodiments, for a high-capacity UE, no scaling configuration is required, or the configured scaling factor may be 1. Alternatively, for a low-capacity UE, the configuration may include a single scaling factor greater than 1. In another embodiment, a scaling factor may be applied to K4.

[0030] Figure 1 shows a simplified, exemplary wireless communication system according to several embodiments. Note that the system in Figure 1 is merely one example of a possible system, and the features of this disclosure may be implemented in any of the various systems as desired.

[0031] As shown in the figure, the exemplary wireless communication system includes a base station 102A, which communicates with one or more user devices 106A, 106B, etc. ~ 106N via a transmission medium. Each of the user devices may be referred to herein as a “user equipment” (UE). Thus, user device 106 is referred to as a UE or UE device.

[0032] Base station (BS) 102A may be a base transceiver station (BTS) or a cellular base station ("cellular base station"), and may include hardware that enables wireless communication with UE106A~106N.

[0033] The communication area (or coverage area) of a base station may be referred to as a “cell.” Base stations 102A and UE106 may be configured to communicate over a medium using one of various radio access technologies (RATs), also known as wireless communication technologies or telecommunications standards, such as GSM, UMTS, LTE, LTE-Advanced (LTE-A), 5G New Radio (5G NR), HSPA, and 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), (e.g., associated with a WCDMA or TD-SCDMA air interface). Note that when base station 102A is implemented in the context of LTE, base station 102A may be referred to as an “eNodeB” or “eNB” instead. Note that when base station 102A is implemented in the context of 5G NR, base station 102A may be referred to as an “gNodeB” or “gNB” instead.

[0034] As shown in the figure, the base station 102A may also be equipped to communicate with the network 100 (for example, among various possibilities, the core network of a cellular service provider, a telecommunications network such as the Public Switched Telephone Network (PSTN), and / or the Internet). Thus, the base station 102A can facilitate communication between user devices and / or between user devices and the network 100. In particular, the cellular base station 102A can provide the UE 106 with various telecommunications capabilities such as voice, SMS, and / or data services.

[0035] Base stations 102 and other similar base stations (such as base stations 102B...102N) operating according to the same or different cellular communication standards can therefore be provided as a network of cells, capable of providing continuous or nearly continuous overlapping services to UE106A~106N and similar devices over a geographical area via one or more cellular communication standards.

[0036] Therefore, as shown in Figure 1, base station 102A can function as a “serving cell” for UEs 106A to 106N, and each UE 106 can also receive signals from one or more other cells (which may be provided by base stations 102B to 102N and / or any other base stations) (within their communication range, if possible). Such cells can also facilitate communication between user devices and / or between user devices and the network 100. Such cells may include “macro” cells, “micro” cells, “pico” cells, and / or cells that provide any other granularity of service area size. For example, base stations 102A to 102B shown in Figure 1 may be macrocells, and base station 102N may be a microcell. Other configurations are also possible.

[0037] In some embodiments, base station 102A may be a next-generation base station, such as a 5G New Radio (5G NR) base station, or a "gNB". In some embodiments, the gNB may be connected to a conventional evolved packet core (EPC) network and / or an NR core (NRC) network. In addition, a gNB cell may include one or more transition and reception points (TRPs). In addition, UEs capable of operating in accordance with 5G NR may be connected to one or more TRPs in one or more gNBs.

[0038] It should be noted that UE106 may be capable of communicating using multiple wireless communication standards. For example, UE106 may be configured to communicate using at least one cellular communication protocol (e.g., GSM, UMTS (associated with WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD)) in addition to wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth, Wi-Fi peer-to-peer). In addition, or alternatively, UE106 may be configured to communicate using one or more Global Navigational Satellite Systems (GNSS, e.g., GPS or GLONASS), one or more mobile television broadcasting standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocols, if desired. Other combinations of wireless communication standards (including three or more wireless communication standards) are also possible.

[0039] Figures 2A and 2B show a base station (BS) communicating with a user equipment (UE) device via a non-terrestrial network (NTN) according to several embodiments. Figure 2A shows user equipment 206A that can communicate with the 5G core network 210A, or another user equipment 206B in direct communication (also known as device-to-device or sidelink). In some embodiments, UE 206A can communicate with satellite 202 via service link 204A, and satellite 202 communicates with the 5G core network 210A via feeder link 208A and next-generation node B (gnB) 212A.

[0040] In some embodiments, sidelink communication can utilize dedicated sidelink channels and sidelink protocols to facilitate direct communication between devices. For example, a sidelink control channel (PSCCH) can be used for actual data transmission between devices, a physical sidelink shared channel (PSSCH) can be used to carry sidelink control information (SCI), a physical sidelink feedback channel (PSFCH) can be used for HARQ feedback information, and a physical sidelink broadcast channel (PSBCH) can be used for synchronization.

[0041] In another embodiment, Figure 2B shows a UE206C that can communicate with the 5G core network 210B, or another UE206D that communicates directly with it. In some embodiments, the UE206C can communicate with a satellite which is gnB212B via service link 204B, and gnB212B communicates with the 5G core network 210B via feeder link 208B.

[0042] In addition, side-link communication can be used for vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-human (V2P), vehicle-to-network (V2N), and other types of direct communication.

[0043] Returning to Figure 1, according to several embodiments, any of UE106A-N can also communicate with base station 102A via uplink and downlink communications. Each UE may be a cellular communication-capable device such as a mobile phone, handheld device, computer, or tablet, or substantially any type of wireless device. UE106A-N may include a processor configured to execute program instructions stored in memory. By executing such stored instructions, UE106A-N can perform any of the embodiments of the method described herein. Alternatively or in addition, UE106A-N may include programmable hardware elements such as a field-programmable gate array (FPGA) configured to perform any of the embodiments of the method described herein, or any part of any of the embodiments of the method described herein.

[0044] UE106A~N may include one or more antennas for communication using one or more wireless communication protocols or technologies. In some embodiments, UE106A~N may be configured to communicate, for example, using CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD) or LTE using a single shared radio, and / or using GSM or LTE using a single shared radio. The shared radio may be coupled to a single antenna or (for example, for MIMO) to multiple antennas for performing wireless communication. Generally, the radio may include any combination of a baseband processor, analog RF signal processing circuits (including, for example, filters, mixers, oscillators, amplifiers, etc.), or digital processing circuits (for, for example, digital modulation and other digital processing). Similarly, the radio may implement one or more receive and transmit chains using the above hardware. For example, UE106A~N may share one or more parts of the receive and / or transmit chains among multiple wireless communication technologies, such as the technologies described above.

[0045] In some embodiments, UE106A-N may include separate transmit and / or receive chains (e.g., separate antennas and other radio components) for each radio communication protocol that the UE is configured to use for communication. Further possibilities include one or more radios shared among multiple radio communication protocols and one or more radios used exclusively by a single radio communication protocol. For example, UE106A-N may include a shared radio for communication using either LTE or 5G NR (or LTE or 1xRTT, or LTE or GSM), and separate radios for communication using Wi-Fi and Bluetooth, respectively. Other configurations are also possible. Block diagram of Figure 3-UE

[0046] Figure 3 shows an exemplary simplified block diagram of a communication device 106 according to several embodiments. Note that the block diagram of the communication device in Figure 3 is only one example of a possible communication device. According to embodiments, the communication device 106 may be, among other devices, a user equipment (UE) device, a mobile device or mobile station, a radio device or radio station, a desktop computer or computing device, a mobile computing device (e.g., a laptop computer, notebook computer, or portable computing device), a tablet, and / or a combination of devices. As shown in the figure, the communication device 106 may include a set of components 300 configured to perform core functions. For example, this set of components may be implemented as a system on a chip (SOC) which may include parts for various purposes. Alternatively, this set of components 300 may be implemented as separate components or groups of components for various purposes. The set of components 300 may be coupled (e.g., directly or indirectly so as to communicate) to various other circuits of the communication device 106.

[0047] For example, the communication device 106 may include various types of memory (including, for example, NAND flash 310), an input / output interface such as a connector I / F 320 (for connecting to, for example, a computer system, a dock, a charging station, an input device such as a microphone, a camera, a keyboard, or a speaker), a display 360 which may be integrated with or outside the communication device 106, a cellular communication circuit 330 for 5G NR, LTE, GSM, etc., and a short-to-medium range wireless communication circuit 329 (for example, Bluetooth® and WLAN circuit). In some embodiments, the communication device 106 may include a wired communication circuit (not shown), such as a network interface card for Ethernet.

[0048] The cellular communication circuit 330 may be coupled (e.g., directly or indirectly, in a communicative manner) to one or more antennas, such as antennas 335 and 336, as shown in the figure. The short-to-medium range wireless communication circuit 329 may also be coupled (e.g., directly or indirectly, in a communicative manner) to one or more antennas, such as antennas 337 and 338, as shown in the figure. Alternatively, the short-to-medium range wireless communication circuit 329 may be coupled (e.g., directly or indirectly, in a communicative manner) to antennas 335 and 336, in addition to or instead of coupling (e.g., directly or indirectly, in a communicative manner) to antennas 337 and 338. The short-to-medium range wireless communication circuit 329 and / or the cellular communication circuit 330 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams in a multiple-input multiple output (MIMO) configuration, such as.

[0049] In some embodiments, as further described below, the cellular communication circuit 330 may include dedicated receiving chains (e.g., a first receiving chain for LTE and a second receiving chain for 5G NR) for multiple radio access technologies (RATs) (e.g., communicating directly or indirectly including and / or coupled with dedicated processors and / or radios). In addition, in some embodiments, the cellular communication circuit 330 may include a single transmitting chain that can be switched between radios dedicated to a particular RAT. For example, a first radio may be dedicated to a first RAT, e.g., LTE, and communicate with a dedicated receiving chain and a transmitting chain shared with an additional radio, e.g., a second radio, and a second radio may be dedicated to a second RAT, e.g., 5G NR, and communicate with a dedicated receiving chain and a shared transmitting chain.

[0050] The communication device 106 may also include and / or be configured for use with one or more user interface elements. The user interface elements may include any of a variety of elements, such as a display 360 (which may be a touchscreen display), a keyboard (which may be a separate keyboard or implemented as part of a touchscreen display), a mouse, a microphone and / or a speaker, one or more cameras, one or more buttons, and / or any of a variety of other elements capable of providing information to the user and / or receiving or interpreting user input.

[0051] The communication device 106 may further include one or more smart cards 345, such as one or more UICC (Universal Integrated Circuit Card) cards 345, which include SIM (Subscriber Identity Module) functionality.

[0052] As shown in the figure, the SOC 300 may include one or more processors 302 capable of executing program instructions for the communication device 106, and a display circuit 304 capable of performing graphics processing and providing display signals to the display 360. The one or more processors 302 may be coupled to a Memory Management Unit (MMU) 340, which may be configured to receive addresses from the one or more processors 302 and to translate these addresses to locations in memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310), and / or other circuits or devices such as the display circuit 304, the short-range wireless communication circuit 229, the cellular communication circuit 330, the connector I / F 320, and / or the display 360. The MMU 340 may be configured to perform memory protection and page table conversion or setup. In some embodiments, the MMU 340 may be included as part of a processor(s) 302.

[0053] As described above, the communication device 106 may be configured to communicate using wireless and / or wired communication circuits. The communication device 106 may also be configured to determine physical downlink shared channel scheduling resources for user equipment devices and base stations. Furthermore, the communication device 106 may be configured to group and select CCs from a wireless link and determine virtual CCs from the selected group of CCs. The wireless device may also be configured to perform physical downlink resource mapping based on aggregate resource matching patterns of the group of CCs.

[0054] As described herein, the communication device 106 may include hardware and software components for implementing the above-described features for determining physical downlink shared channel scheduling resources for the communication device 106 and the base station. The processor 302 of the communication device 106 may be configured to implement some or all of the features described herein by executing program instructions stored in a memory medium (e.g., a non-temporary computer-readable memory medium). Alternatively (or in addition), the processor 302 may be configured as a programmable hardware element such as a field-programmable gate array (FPGA) or as an application-specific integrated circuit (ASIC). Alternatively (or in addition), the processor 302 of the communication device 106 may be configured to implement some or all of the features described herein together with any one or more of the other components 300, 304, 306, 310, 320, 329, 330, 340, 345, 350, 360.

[0055] In addition, as described herein, the processor 302 may include one or more processing elements. Thus, the processor 302 may include one or more integrated circuits (ICs) configured to perform the functions of the processor 302. In addition, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the processor(s) 302.

[0056] Furthermore, as described herein, the cellular communication circuit 330 and the short-range wireless communication circuit 329 may each include one or more processing elements. In other words, one or more processing elements may be included in the cellular communication circuit 330, and similarly, one or more processing elements may be included in the short-range wireless communication circuit 329. Thus, the cellular communication circuit 330 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuit 330. In addition, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the cellular communication circuit 230. Similarly, the short-range wireless communication circuit 329 may include one or more ICs configured to perform the functions of the short-range wireless communication circuit 32. In addition, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the short-range wireless communication circuit 329. Figure 4 - Block diagram of a base station

[0057] Figure 4 shows an exemplary block diagram of a base station 102 according to several embodiments. Note that the base station in Figure 4 is merely an example of a possible base station. As shown in the figure, the base station 102 may include one or more processors 404 capable of executing program instructions for the base station 102. The processors 404 may also be coupled to a memory management unit (MMU) 440, which may be configured to receive addresses from the processors 404 and translate those addresses to locations in memory (e.g., memory 460 and read-only memory (ROM) 450) or other circuits or devices.

[0058] The base station 102 may include at least one network port 470. The network port 470 may be connected to a telephone network and configured to provide access to the telephone network to multiple devices, such as the UE device 106, as shown above in Figures 1 and 2.

[0059] Network port 470 (or additional network ports) may also, or alternatively, be configured to connect to a cellular network, such as the core network of a cellular service provider. The core network can provide mobility-related services and / or other services to multiple devices, such as UE device 106. In some cases, network port 470 may connect to a telephone network via the core network, and / or the core network may provide a telephone network (for example, between other UE devices serviced by the cellular service provider).

[0060] In some embodiments, base station 102 may be a next-generation base station, for example, a 5G New Radio (5G NR) base station, or a "gNB". In such embodiments, base station 102 may be connected to a conventional evolved packet core (EPC) network and / or an NR core (NRC) network. In addition, base station 102 may be considered a 5G NR cell and may include one or more transition and receive points (TRPs). In addition, UEs capable of operating in accordance with 5G NR may be connected to one or more TRPs in one or more gNBs.

[0061] The base station 102 may include at least one antenna 434, and possibly more antennas. At least one antenna 434 may be configured to operate as a radio transceiver and may be further configured to communicate with the UE device 106 via a radio 430. The antenna 434 communicates with the radio 430 via a communication chain 432. The communication chain 432 may be a receive chain, a transmit chain, or both. The radio 430 may be configured to communicate via a variety of radio communication standards, including but not limited to 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, and Wi-Fi.

[0062] Base station 102 can be configured to communicate using multiple wireless communication standards. In some cases, base station 102 may include multiple radios, which may enable base station 102 to communicate according to multiple wireless communication technologies. For example, one possibility is that base station 102 may include an LTE radio for performing communication according to LTE, and a 5G NR radio for performing communication according to 5G NR. In such a case, base station 102 may be capable of operating as both an LTE base station and a 5G NR base station. Another possibility is that base station 102 may include a multimode radio, which may be capable of performing communication according to any of several wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0063] As further described below in this specification, BS102 may include hardware and software components for implementing or supporting the implementations of the features described herein. The processor 404 of the base station 102 may be configured to implement or support some or all of the methods described herein by executing program instructions stored in a memory medium (e.g., a non-temporary computer-readable memory medium), for example. Alternatively, the processor 404 may be configured as a programmable hardware element such as a field-programmable gate array (FPGA), or as an application-specific integrated circuit (ASIC), or a combination thereof. Alternatively (or in addition), the processor 404 of BS102 may be configured to implement or support some or all of the features described herein, together with one or more of the other components 430, 432, 434, 440, 450, 460, and 470.

[0064] In addition, as described herein, the processor(s) 404 may consist of one or more processing elements. In other words, one or more processing elements may be contained within the processor(s) 404. Thus, the processor(s) 404 may include one or more integrated circuits (ICs) configured to perform the functions of the processor(s) 404. In addition, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the processor(s) 404.

[0065] Furthermore, as described herein, the radio 430 may consist of one or more processing elements. In other words, one or more processing elements may be included within the radio 430. Thus, the radio 430 may include one or more integrated circuits (ICs) configured to perform the functions of the radio 430. In addition, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the radio 430. Figure 5: Block diagram of a cellular communication circuit

[0066] Figure 5 shows an exemplary simplified block diagram of a cellular communication circuit according to several embodiments. Note that the block diagram of the cellular communication circuit in Figure 5 is just one example of a possible cellular communication circuit. According to the embodiments, the cellular communication circuit 330 may be included in a communication device such as the communication device 106 described above. As described above, the communication device 106 may be, among other devices, a user equipment (UE) device, a mobile device or mobile station, a radio device or radio base station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet, and / or a combination of devices.

[0067] The cellular communication circuit 330 may be coupled (for example, directly or indirectly so as to communicate) to one or more antennas, such as antennas 335a-b and 336, as shown (in Figure 3). In some embodiments, the cellular communication circuit 330 may include dedicated receiving chains for multiple RATs (e.g., a first receiving chain for LTE and a second receiving chain for 5G NR) (e.g., including dedicated processors and / or radios and / or being directly or indirectly so as to communicate with the dedicated processors and / or radios). For example, as shown in Figure 5, the cellular communication circuit 330 may include modems 510 and 520. Modem 510 may be configured for communication according to a first RAT, such as LTE or LTE-A, and modem 520 may be configured for communication according to a second RAT, such as 5G NR.

[0068] As shown in the figure, the modem 510 may include one or more processors 512 and a memory 516 that communicates with the processors 512. The modem 510 may also communicate with a radio frequency (RF) front end 530. The RF front end 530 may include circuits for transmitting and receiving radio signals. For example, the RF front end 530 may include a receive circuitry (RX) 532 and a transmit circuitry (TX) 534. In some embodiments, the receive circuitry 532 may communicate with a downlink (DL) front end 550 that may include circuits for receiving radio signals via an antenna 335a.

[0069] Similarly, the modem 520 may include one or more processors 522 and a memory 526 that communicates with the processors 522. The modem 520 may also communicate with an RF front end 540. The RF front end 540 may include circuits for transmitting and receiving radio signals. For example, the RF front end 540 may include a receiving circuit 542 and a transmitting circuit 544. In some embodiments, the receiving circuit 542 may communicate with a DL front end 560 which may include circuits for receiving radio signals via an antenna 335b.

[0070] In some embodiments, switch 570 may couple a transmitting circuit 534 to an uplink (UL) front end 572. In addition, switch 570 may couple a transmitting circuit 544 to an UL front end 572. The UL front end 572 may include a circuit for transmitting a radio signal via an antenna 336. Thus, when the cellular communication circuit 330 receives a command to transmit according to a first RAT (e.g., supported via a modem 510), switch 570 may be switched to a first state that enables the modem 510 to transmit a signal according to the first RAT (e.g., via a transmission chain including transmitting circuit 534 and the UL front end 572). Similarly, when the cellular communication circuit 330 receives a command to transmit according to a second RAT (e.g., supported via a modem 520), switch 570 may be switched to a second state that enables the modem 520 to transmit a signal according to a second RAT (e.g., via a transmission chain including transmitting circuit 544 and the UL front end 572).

[0071] As described herein, the modem 510 may include hardware and software components that implement the above-described features, or for selecting periodic resource portions for user equipment devices and base stations, and various other techniques described herein. The processor 512 may be configured to implement some or all of the features described herein by executing program instructions stored in a memory medium (e.g., a non-temporary computer-readable memory medium). Alternatively (or in addition), the processor 512 may be configured as a programmable hardware element such as a field-programmable gate array (FPGA), or as an application-specific integrated circuit (ASIC). Alternatively (or in addition), the processor 512 may be configured to implement some or all of the features described herein in conjunction with one or more of the other components 530, 532, 534, 550, 570, 572, 335, and 336.

[0072] In addition, as described herein, the processor 512 may include one or more processing elements. Thus, the processor 512 may include one or more integrated circuits (ICs) configured to perform the functions of the processor 512. In addition, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the processor 512.

[0073] As described herein, the modem 520 may include hardware and software components for implementing the above-described functions for selecting periodic resources on a radio link between the UE and the base station, as well as various other techniques described herein. The processor 522 may be configured to implement some or all of the features described herein by executing program instructions stored in a memory medium (e.g., a non-temporary computer-readable memory medium). Alternatively (or in addition), the processor 522 may be configured as a programmable hardware element such as a field-programmable gate array (FPGA) or as an application-specific integrated circuit (ASIC). Alternatively (or in addition), the processor 522 may be configured to implement some or all of the features described herein together with one or more of the other components 540, 542, 544, 550, 570, 572, 335, and 336.

[0074] In addition, as described herein, the processor 522 may include one or more processing elements. Therefore, the processor 522 may include one or more integrated circuits (ICs) configured to perform the functions of the processor 522. In addition, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the processor 522. Timing relationships at NTN

[0075] In terrestrial networks (TN), timing may differ compared to NTN. For example, in the case of TN, at the timing of receiving a physical downlink shared channel (PDSCH), the downlink control information (DCI) indicates slot offset K0, where the slot assigned to the PDSCH is:

[0076]

number

[0077]

number

[0078] Furthermore, a Random Access Response (RAR) allows a scheduled PUSCH transmission timing (e.g., Msg3), and the RAR message ends in slot n, which is the slot allocated for the PUSCH, where n + K2 + Δ, and the value of Δ is μ PUSCH This may depend on (see Table 1 below).

[0079] [Table 1]

[0080] Furthermore, in the DCI-scheduled PUCCH transmission timing, DCI indicates the slot offset K1. Therefore, in the case of PDSCH reception in slot n, the slot assigned to PUCCH is n+K1. Figure 6 shows some embodiments of the reception and transmission timings. In Figure 6, the PDSCH reception timing 600 shows that K0608 is the time gap between DCI 602 and PDSCH 604, and K1610 is the time gap between PDSCH 604 reception and PUCCH 606 ​​transmission. Furthermore, the PUCCH transmission timing 614 shows that K2 is the time gap between DCI 602 and PUCCH 616.

[0081] In addition, in the TN system, the HARQ-ACK corresponding to the PDSCH that carries the MAC-CE command in response to the media access control (MAC) control element (CE) action timing is transmitted in slot n. The corresponding operating time is

[0082]

number

[0083]

number

[0084] In further embodiments, K0 and K1 are looked up in DCI format 1_0, 1_1, or 1_2, where K0 is the time gap between DCI and PDSCH, and K1 is the time gap between PDSCH reception and PUCCH transmission. In some embodiments, in DCI format 1_0, K1 is between slots 1 and 8; in DCI format 1_1, K1 is one of the values ​​between slots 0 and 15 in PUCCH SCS ("dl-DataToUL-ACK" IE); and in DCI format 1_2, K1 is one of the values ​​between slots 0 and 15 in PUCCH SCS ("dl-DataToUL-ACK-ForDCIFormat1_2" IE). Furthermore, the maximum gap between PDSCH reception and PUCCH transmission is 15 slots. In another embodiment, K2 is looked up in DCI format 0_0, 0_1, or 0_2, where K2 is the time gap between DCI and PUCCH. In some embodiments, in DCI formats 0_0, 0_1, and 0_2, K2 is one of the values ​​from slots 0 to 32 in PUCCH SCS ("PUSCH-TimeDomainResourceAllocation" or "PUSCH-TimeDomainResourceAllocationNew" IE).

[0085] Regarding timing in NTN systems, timing relationships differ due to the longer delays involved when communicating data over satellite-based systems. In some embodiments, as in NR Release 16 NTN study, the timing relationship is offset K offset This is achieved by introducing, where the PUSCH timing is,

[0086]

number

[0087]

number

number

[0088]

number

[0089]

number

[0090]

number

[0091] In some embodiments, in an NTN system, the challenge may be determining time relationships based on timing advance (TA). In some embodiments, timing advance means that in uplink transmission, the UE transmits data earlier to compensate for propagation delay so that the gNB receives the uplink data on time. For example, and in some embodiments, K offset It is necessary to calculate and ensure appropriate UL resources after the additional slot offset. In addition, in NTN systems with UEs that have a low ability to derive accurate differential TAs, there is a challenge in ensuring that PUCCH / PUSCH scheduled via K1 and K2 can be received at the next-generation NodeB (gNB) at the appropriate time. In some embodiments, a highly capable UE can derive an accurate differential TA, but a less capable UE cannot. In this embodiment, the existing K1 and K2 value range may be small, and small K1 and K2 values ​​may not be suitable for UEs with a low ability to obtain accurate differential TAs. With the introduction of UE-specific time offsets, the slot for uplink transmission of PUSCH or PUCCH is not guaranteed to be an uplink slot within the existing range of K1 and K2. Therefore, in some embodiments, the UE can extend the range of K1 and K2 for NTN. Furthermore, it may be useful to increase the K1 and K2 value range without increasing DCI signaling overhead. In addition, in NTN, the system is K offset This can be applied to sidelink transmission, and parameters can be configured in permission type 1 configured for NTN.

[0092] In further embodiments, a scaling factor (S) for K4 may be applied. In some embodiments, the possible scaling factors may be {1, 2, 4, 8, 16} or one of different values. Similar to the scaling factors for K1, K2, or K4, the value of the scaling factor may depend on the cell / beam size and / or UE capability. In some embodiments, the network configures and / or selects a single scaling factor value for each UE. In further embodiments, the network (e.g., a base station) signals the scaling factor to the UE. For example, and in some embodiments, the signaling may be dedicated RRC signaling, e.g., "SL-ConfigDedicatedNR-r16". In another embodiment, the actual time gap between PDSCH reception and PUCCH transmission may be S·K1 slot.

[0093] Figure 7 is a diagram of several embodiments of the NTN timing relationship 700. In Figure 7, the timing relationship includes slot timings 702A to D. In some embodiments, gnB DL702A includes a scheduled PUSCH704 for TN, which is K offset 708 is used to shift to NTN-scheduled PUSCH706 for NTN. In addition, UL DL702B starts after TA710. In slot 0 of UE DL702B, DCI is received and the scheduled PUSCH starts after a delay of 2 slots from K2. UE UL702C has a propagation delay of 4 slots from slots 10 to 13. Furthermore, gnB UL702D is a PUSCH received in slot 10 due to a large propagation delay of 716.

[0094] In some embodiments, Additional time offset K offsetThis was introduced for NTN, where this time offset is in slot units. In addition, this time offset is on top of the existing timing of UE transmission types (e.g., DCI scheduled PUSCH, RAR scheduled PUSCH, PUCCH, MAC CE action timing, aperiodic SRS, and CRI-RS reference resource). Figures 8A and 8B show K offset To determine the different timings for UL and DL, K offset This is a flowchart of several embodiments of a process that uses [the specified method / tool].

[0095] In some embodiments, the base station performs process 800 as shown in Figure 8A. In Figure 8A, process 800 determines the timing advance based on the random access preamble reception in block 802. In one embodiment, process 800 performs K offset Information used to calculate is collected. In this embodiment, K offset This is derived from the timing advance (TA). The base station can calculate the TA from the received PRACH. In block 804, process 800 calculates K based on the determined TA. offset Determine. In some embodiments, K offset The determination is based on the type of NTN architecture. In some embodiments, the time offset K offset This is calculated based on the sum of the service link full TA and feeder link TA of the ground-based transmission satellite gnB. For example, and in some embodiments, when gNB is on the ground,

[0096]

number

[0097]

number

[0098] Process 800, in block 806, K offset Candidate slots for UL reception are determined based on the following formula. In some embodiments, candidate slots for UL reception are determined by the formula

[0099]

number

[0100] Process 800, in block 814, K offset The MAC CE action timing is further adjusted using the formula. In some embodiments, process 800 is used.

[0101]

number

[0102]

number

[0103] In Figure 8B, process 850 is executed by the UE. In block 852, process 850 starts by receiving timing advance information from the base station. In some embodiments, K offset The determination is based on the type of NTN architecture. In some embodiments, process 850 is K offset Information is collected to calculate K. offset This is derived from the TA command in the RAR (Random Access Response) message from the NW. In block 854, process 850 determines K based on the determined TA. offset Determine the time offset K. In some embodiments, offset This is calculated based on the sum of the service link full TA and feeder link TA of the ground-based transmission satellite gnB. For example, and in some embodiments, when gNB is on the ground,

[0104]

number

[0105]

number

[0106] Process 850, in block 856, CSI-RS reference resource timing and K offset Candidate slots are determined based on the following. In some embodiments, the CSI reference resource timing, the CSI reference resource in the downlink slot,

[0107]

number

[0108]

number

[0109] Figures 9A to 9D are flowcharts of several embodiments of a process for extending one or more time gaps between the downlink (DL) and the uplink (UL). Figure 9A shows the scaling factor and K offsetThis is a flowchart of several embodiments of determining a slot for UL transmission using [a specific method / tool]. In some embodiments, the UE performs process 900. In Figure 9, process 900 begins in block 902 by receiving a scaling factor for a K value via a Radio Resource Control (RRC) signal. In some embodiments, the scaling factor may be for one or more of K1, K2, or K4. In some embodiments, the existing K1, K2 values ​​may independently be in the range of 0 to 15 slots (K1) or 0 to 32 slots (K2). In some embodiments, the scaling factor is one of {1, 2, 4, 8, 16}, but the scaling factor may contain different values. For example, and in some embodiments, NTN may have a large cell size and / or a large differential TA value. In this example, an inaccurate differential TA value may be due to the UE's ability to derive an accurate or inaccurate differential TA. In some embodiments, the value of the scaling factor(s) may depend on the cell and / or beam size. For example, and in some embodiments, the larger the cell size, the larger the scaling factor value. In addition, there may be a single scaling factor value for each UE, or different scaling factors for different K values. Furthermore, the selected scaling factor may depend on the UE capability. For example, and in some embodiments, for high-capacity UEs, no scaling configuration is required, or the configured scaling factor may be 1. Alternatively, for low-capacity UEs, the configuration may include a single scaling factor greater than 1.

[0110] In block 904, process 900 uses the RRC signal to send K offset Determines K by signaling from the network via a dedicated RRC signal. In some embodiments, process 900 determines K offsetUpon receiving the dedicated RRC signal, the dedicated RRC signal may be the same as or different from the RRC signal used to communicate the scaling factor. In block 906, process 900 receives a DCI with an indication of a K value. In this embodiment, the DCI includes an indication of which of the K values ​​(e.g., K1, K2, or K4) should be scaled by the scaling factor. In block 908, process 900 calculates a new K value using the scaling factor and the indicated K value. In some embodiments, process 900 calculates a new K value by multiplying an existing K value by the scaling factor. For example, and in one embodiment, if the K value is K1, process 900 calculates K1 ’ =S * Calculate K1. The new K values ​​can be similarly calculated for K2 and / or K4. In block 910, the process calculates the new K values ​​and K offset Use this to determine the slot for UL transmission.

[0111] In Figure 9A, process 900 applies a scaling factor transmitted using an RRC message. In an alternative embodiment, the applied scaling factor may be more dynamic if the scaling factor is communicated to the UE via DCI as well as RRC signals. Figure 9B shows the scaling factor and K offsetThis is a flowchart of several embodiments of determining a slot for UL transmission using the scaling factor shown here, which is communicated via DCI. In some embodiments, the UE performs process 920. In Figure 9B, process 920 begins in block 922 by receiving a scaling factor set for K values ​​via a Radio Resource Control (RRC) signal. In some embodiments, the scaling factor set may be used for one or more of K1, K2, or K4. In some embodiments, the existing K1, K2 values ​​may independently be in the range of 0 to 15 slots (K1) or 0 to 32 slots (K2). In some embodiments, the scaling factor set may be a scaling factor set such as {1, 2, 4, 8, 16}, but the scaling factor set may contain different values. In block 924, process 920 receives the K via the RRC signal offset Determines K by signaling from the network via a dedicated RRC signal. In some embodiments, process 920 determines K offset Upon receiving the dedicated RRC signal, the dedicated RRC signal may be the same as or different from the RRC signal used to communicate the scaling factor.

[0112] In block 926, process 920 receives a DCI containing instructions for K values ​​and scaling factors. In some embodiments, the DCI includes instructions on which of the K values ​​(e.g., K1, K2, or K4) should be scaled using the scaling factor. In addition, the DCI may include instructions on which scaling factor should be used with this K value, where the scaling factor is selected from a set of scaling factors sent to the UE, as described in block 922 above. Different K values ​​and / or different scaling factors may exist for different UEs. For example, and in some embodiments, NTN may have a large cell size and / or a large differential TA value. In this example, an inaccurate differential TA value may be due to the UE's ability to derive an accurate or inaccurate differential TA. In some embodiments, the values ​​of the scaling factor(s) for the scaling factor set may depend on the cell and / or beam size. For example, and in some embodiments, the larger the cell size, the larger the scaling factor value. In addition, the selected scaling factor may depend on the UE's capabilities. For example, and in some embodiments, for high-capacity UEs, a scaling configuration may not be required, or the configured scaling factor may be 1. Alternatively, for low-capacity UEs, the configuration may include a single scaling factor greater than 1.

[0113] Process 920 calculates a new K value in block 928 using the indicated scaling factor and the indicated K value. In some embodiments, process 920 calculates a new K value by multiplying the existing K value by the scaling factor. For example, in one embodiment, if the K value is K1, process 920 calculates K1 ’ =S * Calculate K1. The new K values ​​can be similarly calculated for K2 and / or K4. In block 930, the process calculates the new K values ​​and K offset Use this to determine the slot for UL transmission.

[0114] In Figures 9A and 9B, processes 900 and 920 represent UE processes that determine UL slots based on information transmitted from the base station to the UE. At the base station, the corresponding processes determine UL slot information for receiving UL communication. Figure 9C shows the scaling factor and K offset This is a flowchart of several embodiments of determining a slot for UL transmission for a base station using the scaling factor and K in block 942. offset The process begins by determining the scaling factor. In some embodiments, the process 940 determines the scaling factor based on the NTN characteristics and UE characteristics, as described in Figure 9A above. In block 944, the process 940 sends the scaling factor and K to the UE via one or more RRC signals. offset The process transmits the scaling factor and K in the same or different RRC signals. In some embodiments, process 940 transmits the scaling factor and K in the same or different RRC signals. offset It can be sent.

[0115] Process 940 transmits a DCI with a K value indication in block 946. In some embodiments, process 940 selects which K value to choose for scaling. In some embodiments, which K values ​​are included depends on the DCI format. For example, and in one embodiment, if a base station transmits a DCI with a DCI format for DL ​​scheduling, the DCI will include K1. For UL scheduling, the DCI format may include K2. In these embodiments, process 940 selects one or more of K1, K2, or K4 to indicate in the DCI. In block 948, process 940 includes at least the scaling factor, the K value, and / or K offsetBased on this, the slot for receiving UL transmissions from the UE is determined. In one embodiment, the determination of the UL slot depends on the type of UL transmission (e.g., PUCCH, PUSCH, and / or another type of UL transmission). For example, and in one embodiment, in the case of PUCCH, the UL slot is given by equation n+K1 ’ Determined using, where K1 ’ This is the scaled value of K1. Alternatively, in the case of PUSCH, the UL slot is formula

[0116]

number

[0117] In Figure 9B above, the UE receives the scaling factor set, and which factor is used by the UE is indicated in the DCI transmitted from the base station. Figure 9D shows the scaling factor and K offset This is a flowchart of several embodiments of determining slots for UL transmission for a base station using the scaling factor shown, which is communicated via DCI. In some embodiments, the base station performs process 960. In Figure 9D, process 960 begins in block 962 by determining a scaling factor set and transmitting it from the base station to the UE via an RRC signal. In some embodiments, the scaling factor set may be used for one or more of K1, K2, or K4. In some embodiments, the existing K1, K2 values ​​may independently be in the range of 0 to 15 slots (K1) or 0 to 32 slots (K2). In some embodiments, the scaling factor set may be a scaling factor set such as {1, 2, 4, 8, 16}, but the scaling factor set may contain different values.

[0118] In block 964, process 960 is K offset The process determines this and transmits it to the UE via the RRC signal. In some embodiments, process 960 determines the type of NTN architecture as described above in Figure 8A. offset The value of is determined. In some embodiments, process 960 signals K from the network via a dedicated RRC signal. offset The process transmits a dedicated RRC signal, which may be the same as or different from the RRC signal used to communicate the scaling factor. In block 966, process 960 determines the scaling factor and K value for the UE's UL transmission. In some embodiments, process 960 selects which K value should be chosen for scaling. Which K values ​​are included in the DCI depends on the DCI formatting, as described in Figure 9A above. In these embodiments, process 960 selects one or more of K1, K2, or K4 to be shown in the DCI. In addition, the scaling factor may be selected from a scaling factor set and adjusted to the determined K value and / or the receiving UE. In block 968, process 960 transmits an instruction for the K value and the determined scaling factor. In block 970, process 960 transmits at least the scaling factor, the K value, and / or K offset Based on this, the slot for receiving UL transmissions from the UE is determined. In one embodiment, the determination of the UL slot depends on the type of UL transmission (e.g., PUCCH, PUSCH, and / or another type of UL transmission). For example, and in one embodiment, in the case of PUCCH, the UL slot is given by equation n+K1 ’ Determined using, where K1 ’ This is the scaled value of K1. Alternatively, in the case of PUSCH, the UL slot is formula

[0119]

number

[0120] In some embodiments, DCI format 3_0 includes time gaps K3 and K4, where time gap K_3 is the time gap between DCI 3_0 reception and the first PSCCH / PSSCH transmission, and time gap K4 is the time gap between the last PSFCH reception and PUCCH transmission. NTN has an additional K above K3. offset It is not necessary for K to exist, offset This can be applied to K4. Figure 10 is an exemplary block diagram of the side link timing relationship 1000 in NTN according to some embodiments. In Figure 10, the timing relationship shows the time gaps between DCI 3_0 1002 and PSCCH / PSSCH 1004, and between PSFCH 1006 and PUCCH 1008. In some embodiments, the time gap K31010 is not adjusted for NTN because this time gap is sufficient for the gap between DCI 3_0 1002 and PSCCH / PSSCH 1004. Alternatively, the time gap K41012 between PSFCH 1006 and PUCCH 1008 is adjusted for NTN. offset It is increased by only that much. In addition, K offset This may be the same as or different from the case of PUSCH transmission in NTN.

[0121] In a further embodiment, the UE has a timing relationship for a Type 1 configured permission configuration K offset This can be used. Figures 11A and 11B are illustrative block diagrams of timing relationships for a Type 1 enabled configuration in NTN. In Figure 11A, the time-domain offset 1104 is K offsetcan include, where the time domain offset is an offset from a reference time 1102 (e.g., SFN = 0) to a grant 1108. In some embodiments, the configured grant 1108 is separated by a periodic value 1106. In some embodiments, K offset is included in the configured grant configuration. In another embodiment, a separate K offset parameter is within the configured grant configuration. For example, and in some embodiments, K offset is included, and the following formula is used to determine the slot number for the configured grant. [(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot)+(slot number in the frame × numberOfSymbolsPerSlot)+symbol number in the slot]=(timeReferenceSFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot + timeDomainOffset × numberOfSymbolsPerSlot + K offset × numberOfSymbolsPerSlot + S + N × periodicity) modulo (1024 × numberOfSlotsPerFrame × numberOfSymbolsPerSlot).

[0122] In a further embodiment, the network combines K offset with "TimeDomainOffset" in the configured grant configuration. For example, and in some embodiments, for the "timeDomainOffset" range, the lower limit depends on the satellite type (e.g., LEO, GEO, HAPS). For example, and in some embodiments, in a type 1 configured grant configuration, there is a field for "timeDomainOffset" to indicate the time gap between the configured grant time and the reference time (e.g., SFN = 0). The time gap may be larger for NTN than it is for including K offset .

[0123] In another embodiment, the network can include K in each transmission. offset In FIG. 11B, the time domain offset 1112 can include K as a separate value in each transmission, where the time domain offset is the offset from the reference time 1114 (e.g., SFN = 0) when added to the configured permission 1118 that constitutes K1120. In some embodiments, the configured permission 1118 is separated by the periodic value 1116. offset In FIG. 11B, the time domain offset 1112 can include K as a separate value in each transmission, where the time domain offset is the offset from the reference time 1114 (e.g., SFN = 0) when added to the configured permission 1118 that constitutes K1120. In some embodiments, the configured permission 1118 is separated by the periodic value 1116. offset In FIG. 11B, the time domain offset 1112 can include K as a separate value in each transmission, where the time domain offset is the offset from the reference time 1114 (e.g., SFN = 0) when added to the configured permission 1118 that constitutes K1120. In some embodiments, the configured permission 1118 is separated by the periodic value 1116.

[0124] FIG. 12 is a flowchart of some embodiments of a process 1300 for determining and applying scaling for a type 1 configured permission configuration for K. In some embodiments, the UE executes process 1200. In FIG. 13, at block 1202, process 1200 receives timing information, where the timing information does not include K. In some embodiments, process 1200 receives K by signaling from the network via a dedicated RRC message. Process 1200 applies K to the type 1 configured permission configuration as described in FIG. 11B at block 1204. offset FIG. 12 is a flowchart of some embodiments of a process 1300 for determining and applying scaling for a type 1 configured permission configuration for K. In some embodiments, the UE executes process 1200. In FIG. 13, at block 1202, process 1200 receives timing information, where the timing information does not include K. In some embodiments, process 1200 receives K by signaling from the network via a dedicated RRC message. Process 1200 applies K to the type 1 configured permission configuration as described in FIG. 11B at block 1204. offset FIG. 12 is a flowchart of some embodiments of a process 1300 for determining and applying scaling for a type 1 configured permission configuration for K. In some embodiments, the UE executes process 1200. In FIG. 13, at block 1202, process 1200 receives timing information, where the timing information does not include K. In some embodiments, process 1200 receives K by signaling from the network via a dedicated RRC message. Process 1200 applies K to the type 1 configured permission configuration as described in FIG. 11B at block 1204. offset FIG. 12 is a flowchart of some embodiments of a process 1300 for determining and applying scaling for a type 1 configured permission configuration for K. In some embodiments, the UE executes process 1200. In FIG. 13, at block 1202, process 1200 receives timing information, where the timing information does not include K. In some embodiments, process 1200 receives K by signaling from the network via a dedicated RRC message. Process 1200 applies K to the type 1 configured permission configuration as described in FIG. 11B at block 1204. offset FIG. 12 is a flowchart of some embodiments of a process 1300 for determining and applying scaling for a type 1 configured permission configuration for K. In some embodiments, the UE executes process 1200. In FIG. 13, at block 1202, process 120 receive timing information, where the timing information does not include K. In some embodiments, process 1200 receives K by signaling from the network via a dedicated RRC message.Process 1200 applies K to the type 1 configured permission configuration as described in FIG. 11B at block 1204.

[0125] The parts of those described above can be executed by logic circuits, such as dedicated logic circuits, or by microcontrollers or other forms of processing cores that execute program code instructions. Thus, the processes taught by the above discussion can be executed by program code, such as machine-executable instructions, which cause a machine to perform specific functions. In this context, “machine” can refer to a machine that translates intermediate (or “abstract”) instructions into processor-specific instructions (e.g., an “abstract execution environment” such as a “virtual machine” (e.g., a Java Virtual Machine), an interpreter, a common language runtime, or a high-level language virtual machine), and / or electronic circuits (e.g., “logic circuits” implemented with transistors) located on a semiconductor chip designed to execute instructions, such as general-purpose processors and / or dedicated processors. The processes taught by the above considerations can also be executed (in place of or in combination with a machine) by electronic circuits designed to execute those processes (or parts of the processes) without executing program code.

[0126] The present invention also relates to an apparatus for performing the operations described herein. This apparatus may include a general-purpose computer that can be specifically constructed for a required purpose or that is selectively started or reconfigured by a computer program stored within the computer. Such computer programs may be stored in computer-readable storage media, each coupled to a computer system bus, including, but not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magneto-optical disks, read-only memory (ROM), RAM, EPROM, EEPROM, magnetic or optical cards, or any type of medium suitable for storing electronic instructions.

[0127] Machine-readable media include any method for storing or transferring information in a format readable by a machine (e.g., a computer). For example, machine-readable media include read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash memory devices, and the like.

[0128] A manufactured product can be used to store program code. The manufactured product for storing program code may, but is not limited to, one or more memories (e.g., one or more flash memories, random access memories (static, dynamic, or otherwise)), optical discs, CD-ROMs, DVD-ROMs, EPROMs, EEPROMs, magnetic or optical cards, or other types of machine-readable media suitable for storing electronic instructions. Program code can also be downloaded from a remote computer (e.g., a server) to a requesting computer (e.g., a client) by data signals embodied in a propagation medium (e.g., via a communication link (e.g., a network connection)).

[0129] The above-described "modes for carrying out the invention" are presented in terms of algorithmic and symbolic representations of operations on data bits within computer memory. These descriptions and representations of algorithms are tools used by those skilled in the art to most effectively communicate the essence of the work to others skilled in the art. An algorithm, as used herein, is also generally considered to be a self-consistent sequence of operations that produces a desired result. These operations require the physical manipulation of physical quantities. While not usually necessary, these quantities take the form of electrical or magnetic signals that can be stored, transferred, combined, compared, and otherwise manipulated. For reasons of general use, it has proven convenient in some cases to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, etc.

[0130] However, it should be noted that these terms, and all similar terms, are associated with appropriate physical quantities and are merely convenient labels applied to those quantities. Unless otherwise specifically stated, as will be evident from the above discussion, discussions using terms such as “transmit,” “receive,” “detect,” “determine,” “communicate,” “transmit,” “assign,” “rank,” “decrement,” “select,” “apply,” and “signal” throughout the explanation will be understood to refer to the operations and processes of a computer system or similar electronic computing device that manipulate data represented as physical (electronic) quantities in the registers or memory of the computer system to convert it into other data similarly represented as physical quantities in the computer system memory or registers, or other such information storage devices, transmitting devices, or display devices.

[0131] The processes and representations presented herein are not specifically related to any particular computer or other device. Various general-purpose systems can be used with programs following the teachings herein, or it may be advantageous to construct more specialized devices for performing the operations described. The structures required for various such systems will be evident from the following description. Furthermore, the present invention is not described in relation to any particular programming language. It will be understood that it is possible to implement the teachings of the present invention as described herein using various programming languages.

[0132] It should be fully understood that the use of personally identifiable information should adhere to privacy policies and practices that are generally recognized as meeting or exceeding industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of authorized use should be clearly indicated to the user.

[0133] The foregoing description illustrates only some exemplary embodiments of the present invention. Those skilled in the art will readily recognize from this discussion, the accompanying drawings, and the claims that various modifications can be made without departing from the spirit and scope of the invention.

Claims

1. A base station comprising a processor configured to perform an operation, wherein the operation is At a minimum, the timing advance should be determined based on the reception of the random access preamble, The uplink offset is determined based on the aforementioned timing advance, wherein the uplink offset is set to be equal to the sum of the service link timing advance and the feeder link timing advance divided by the slot duration, and the service link timing advance includes the sum of the common timing advance and the differential timing advance. At least the uplink offset is used to determine a candidate slot for uplink reception, Determining whether the candidate slot is available for the uplink reception, When the candidate slot is available, use the candidate slot for uplink reception, When the aforementioned candidate slot is unavailable, the next available slot for uplink reception shall be used. Base stations, including

2. The base station according to claim 1, wherein the uplink reception includes a physical uplink shared channel (PUSCH), a random access response (RAR) scheduled PUSCH, a physical uplink control channel (PUCCH), or a non-periodic SRS.

3. Determining whether the candidate slot is available is The base station according to claim 1, comprising determining whether the candidate slot is an uplink slot, a downlink slot, a hybrid slot, or a flexible slot, based at least on the time-division duplex (TDD) configuration of the candidate slot format, wherein if the candidate slot is an uplink slot or one of the hybrid slots with uplink reception corresponding to an uplink symbol in the hybrid slot, the candidate slot is available, and if the candidate slot is a downlink slot, one of the hybrid slots with uplink reception not corresponding to an uplink symbol in the hybrid slot, or a flexible slot, the candidate slot is unavailable.

4. Determining the uplink offset is Calculating the uplink offset based on the timing advance of at least one satellite link in a non-terrestrial network, A base station according to claim 1, including the above.

5. The aforementioned processor, At least the uplink offset is used to calculate the media access control (MAC) control element (CE) action timing, The base station according to claim 1, further configured to perform the operations comprising the above.

6. The aforementioned processor, Using the sidelink offset, calculate the time gap between the last physical sidelink feedback channel (PSFCH) reception and the physical uplink control channel (PUCCH) transmission. The base station according to claim 1, further configured to perform the operations comprising the above.

7. The base station according to claim 6, wherein the side link offset has a different value from the up link offset.

8. The aforementioned processor, At least the time-domain offset for the Type 1 configured permission configuration is calculated using the uplink offset. The base station according to claim 1, further configured to perform the operations comprising the above.

9. Receiving timing advance information from the base station, The uplink offset is determined based on the aforementioned timing advance information, wherein the uplink offset is set to be equal to the sum of the service link timing advance and the feeder link timing advance divided by the slot duration, and the service link timing advance includes the sum of the common timing advance and the differential timing advance. At least the uplink offset is used to determine candidate slots for channel status information (CSI) reference resources, Determining whether the candidate slot is available for the CSI reference resource, When the candidate slot is available, use the candidate slot for the CSI reference resource, When the aforementioned candidate slot is unavailable, another slot for the CSI reference resource will be used. Methods that include...

10. The determination described above is The method according to claim 9, comprising determining whether the candidate slot is an uplink slot, a downlink slot, a hybrid slot, or a flexible slot, based at least on the time-division duplex (TDD) configuration of the candidate slot format, wherein if the candidate slot is a downlink slot or a hybrid slot with downlink reception corresponding to a downlink symbol in the hybrid slot, the candidate slot is available; and if the candidate slot is an uplink slot, a hybrid slot with downlink reception not corresponding to a downlink symbol in the hybrid slot, or a flexible slot, the candidate slot is unavailable.

11. The method according to claim 9, wherein the other available CSI reference resource is the slot preceding the candidate slot.

12. The method according to claim 9, wherein the other available CSI reference resource is the next slot in the candidate slot.

13. A baseband processor configured to perform an operation, wherein the operation is Receiving timing advance information from the base station, The uplink offset is determined based on the aforementioned timing advance information, wherein the uplink offset is set to be equal to the sum of the service link timing advance and the feeder link timing advance divided by the slot duration, and the service link timing advance includes the sum of the common timing advance and the differential timing advance. At least the uplink offset is used to determine candidate slots for the channel state information CSI reference resource, Determining whether the candidate slot is available for the CSI reference resource, When the candidate slot is available, use the candidate slot for the CSI reference resource, When the aforementioned candidate slot is unavailable, another slot for the CSI reference resource will be used. A baseband processor, including a baseband processor.

14. The determination described above is The baseband processor according to claim 13, comprising determining whether the candidate slot is an uplink slot, a downlink slot, a hybrid slot, or a flexible slot based on at least the time-division duplex (TDD) configuration of the candidate slot format, wherein if the candidate slot is one of the uplink slot or a hybrid slot, the candidate slot is available, and if the candidate slot is one of the downlink slot, a hybrid slot, or a flexible slot, the candidate slot is unavailable.

15. A non-temporary machine-readable medium having executable instructions, which, when executed by one or more processing units, the instructions At a minimum, the timing advance should be determined based on the reception of the random access preamble, The uplink offset is determined based on the aforementioned timing advance, wherein the uplink offset is set to be equal to the sum of the service link timing advance and the feeder link timing advance divided by the slot duration, and the service link timing advance includes the sum of the common timing advance and the differential timing advance. At least the uplink offset is used to determine a candidate slot for uplink reception, Determining whether the candidate slot is available for the uplink reception, When the candidate slot is available, use the candidate slot for uplink reception, When the aforementioned candidate slot is unavailable, the next available slot for uplink reception shall be used. A non-temporary machine-readable medium that performs a method including [specific method / function].

16. A non-temporary machine-readable medium having executable instructions, wherein when executed by one or more processing units, the executable instructions are: Receiving timing advance information from the base station, The uplink offset is determined based on the aforementioned timing advance information, wherein the uplink offset is set to be equal to the sum of the service link timing advance and the feeder link timing advance divided by the slot duration. At least the uplink offset is used to determine candidate slots for channel status information (CSI) reference resources, To determine whether the aforementioned candidate slot is available, When the candidate slot is available, use the candidate slot for the CSI reference resource, When the aforementioned candidate slot is unavailable, another slot for the CSI reference resource will be used. A non-temporary machine-readable medium that performs a method including [specific method / function].

Images